• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

Auto decrypt Slow?

Peso

Member
Hello and I hope everyone had a lovely Christmas.

I have a question about auto decrypt.

I have one T2 that decrypt likes this

[td]1.84 GiB in 6753.182 seconds - 286.05 KiB/s[/td][td][/td]

And another two T2’s like this

1.56 GiB in 251.433 seconds - 6.35 MiB/s

If I manually instigate a decrypt on the slow T2 it’s speed is in line the others.
Has anyone an idea why that might be?
 
It seems like the slow version must be using software decrypt instead of the hardware data path, but you say that doing it manually achieves hardware speeds so there is no obvious reason why auto-decrypt would not do the same. Did you reboot in between (to have reset something)? Did you have the network disconnected except when using the WebIF (no network = no hardware decryption)?
 
Hard v software. That’s interesting sense. Thank you Black Hole.

There had been a network failure to this machine in the month before I got back to it. I have fixed the network before Christmas Day. But it’s still slow.
Have deactivated auto decrypt. Will reboot it (when I can) and will re enable to auto decrypt. Hopefully that will be enough.
 
I did change the key (after fixing the network problem).
As far I could tell everything was decrypted. As it was so slow I did try manually starting decryption on recordings, which is how I discovered that worked so much quicker.
 
Hummm.
Having decrypted some manually there where some copies of the originals in sub “_orginal” folders still cheekily hanging around.
 
Having decrypted some manually there where some copies of the originals in sub “_orginal” folders still cheekily hanging around.
That's normal, in case something goes wrong. I presume you don't have undelete installed, or if you do (and it isn't working) you probably need to run fix-flash-packages.
 
The CFW workings are so well done that there are lots of things I’ve not had to touch for years. They’ve just served my parents.

When manually decrypting I’d forgotten the original the moved into a folder on the same level as the recording you’re decrypting.

So when I changed the decryption code on this box there were still some old undecrypted recordings tucked away.



Well, now there aren’t any undecrypted recordings, even in the undelete folder.

I’ve re-set the desired encryption code and seen it say new code set.

Network connection is constant and stable.

Waiting to see what speed it auto decrypts.
 
Still only 200 something kb/s when auto decrypting.

I had set out to make all three of my parents T2’s encrypt with the same code.

If there was a problem with one, as long as I could get a recording off, encrypted or not, I could just move it to another machine.

So if auto decrypt isn’t working very efficiently on one, I could just turn it off on that box. As the others can play it’s recordings.

To test, moved an encrypted recording from the “problem” T2 to another T2, but the auto decrypt reported “No matching key for decryption”.

So moved an unencrypted recording between the other two (happy) T2 boxes and the recording auto decrypted happily as if it was local recording.

So the “problem” T2 can’t be using the new encryption code I gave it when writing recordings.

Is Fix-Flash the next step? Does that encompass the encryption process?

If I run it do I need to reconfigure anything afterwards?


Sorry to bother people of New Years Eve.
 
So moved an unencrypted recording between the other two (happy) T2 boxes and the recording auto decrypted happily as if it was local recording.
What??! Typo?

It seems to me the most likely explanation is you are trying to decrypt recordings that were made before you changed the key. If you change the key (or if the key reverts to default – see below) then recordings made with a different key can't be decrypted in hardware.

Have you rebooted the machine lately? Overriding the OEM encryption key with the WebIF custom key can only happen at boot time.

Is Fix-Flash the next step? Does that encompass the encryption process?
fix-flash-packages repairs CF components which hook into the Humax code in Flash, so it's possible.

If I run it do I need to reconfigure anything afterwards?
No!
 
What??! Typo
Errr yeah! Whoops. Sorry.

It was a brand new recording just for testing.
I did re-enable the desired encryption code. Did I then reboot before making the recording? Not sure.

Will re perform the test making sure of the steps.

Thank you for response.
 
Result.
Fix-Flash has sorted out the slow decryption. Up to MB/s from KB/s.
Unencrypted recording moved to another T2 decrypted.

Thank you for all the help.
Happy New Year.
 
Back
Top