[PC] SamyGO PVRDecoder for E/F/H series - Version 1.8.2.53

[Lordbyte]

Just remember that for some (50%) of "magic values" tv crashes/hangs And for some values it might even "finish" decoding but produced file might be incorrect

We really really need to document this slider in a very detailed way.
The user must understand that this is not just a linear allocation of buffers,
but something else .. something more sinister .. more spooky .. more wtf

[sectroyer]

Just remember that for some (50%) of "magic values" tv crashes/hangs And for some values it might even "finish" decoding but produced file might be incorrect

We really really need to document this slider in a very detailed way.
The user must understand that this is not just a linear allocation of buffers,
but something else .. something more sinister .. more spooky .. more wtf

Well to be honest it IS linear It just can cause "strange things" to happen

[leikli]

Just remember that for some (50%) of "magic values" tv crashes/hangs And for some values it might even "finish" decoding but produced file might be incorrect

For me, the worst problem is not that I have to serialize decoding and downloading, it is that I cannot decode and download more than one recording at a time. If I select more than one recording, the first one will be decoded and downloaded correctly, and then the TV will hang/crash. Also, after a successful decoding/download, I cannot select a new recording and start decoding without a hang or crash. It has worked correctly only once for me. Instead, I have to close down and restart PVRDecoder before I can decode the next recording.

[Lordbyte]

Still sounds like the decoding plugin leaves TV in an unstable state.
The decoding of multiple recordings have been tested extensively, and IF the PVRDecoder works at all,
it should be able to decode several recordings in batch-mode.

I suggest you fiddle with the "slider" some more

I hear users have success with values between 100 and 800 .. You should hunt for a good value in that range, I think (guess)

[leikli]

I suggest you fiddle with the "slider" some more

I don't think my problem with decoding in batch mode is related to the slider value. I think it is a separate problem, which maybe not occurs on all TV models.

[Lordbyte]

Well, according to sectroyers statement, the diagnosis is clear .. You currently use a "magic" value that ends up crashing your TV.
It seems that the decoder plugin has trouble "finishing" correctly, thus messing up when trying batchmode.
It simply crashes when the decoder is loaded the second time, batchmode or not
Try adding (or substracting) 1,2 or 10 from your current "magic" value, and try try try again
At this point, no other advice comes to mind

[sectroyer]

Well, according to sectroyers statement, the diagnosis is clear .. You currently use a "magic" value that ends up crashing your TV.
It seems that the decoder plugin has trouble "finishing" correctly, thus messing up when trying batchmode.
It simply crashes when the decoder is loaded the second time, batchmode or not
Try adding (or substracting) 1,2 or 10 from your current "magic" value, and try try try again
At this point, no other advice comes to mind

Well his magic value can be also COMPLETELY wrong. For instance He might be using now 400 and he needs to use 2400 or even 40. BTW did he had any problems with TV with (default?) value 10?

[Lordbyte]

@sectroyer, lets hope he will tell us .. after he has experimented some more

Would there be any way to produce a "benchmarking" plugin, where you could perform some
tests iteratively, and check for raised exceptions (or whatever those are called in the linux context) ?!

As things are now, users are basically left with a HUGE problem of experimenting with the value.
Something like the method you have used before ... Once TV has rebooted 3-5 times a good value is automatically found.
This value could then be stored/used by the PVRDecoder for future reference

[leikli]

Well his magic value can be also COMPLETELY wrong. For instance He might be using now 400 and he needs to use 2400 or even 40. BTW did he had any problems with TV with (default?) value 10?

I have not tried with very low values, since it would take too much time. I think the problem is more about what is done in the TV after the first decoding before the second decoding in batch mode. The first recording is almost always decoded and downloaded correctly. If I close down PVRDecoder, start it up again and select a new recording, it will almost always work correctly again. If PVRDecoder can reproduce all these steps even in batch mode, the TV should not hang/crash.

[Lordbyte]

I do believe sectroyer knows what he is talking about.
You are using a value that leave your TV unstable. Period.
You may discontinue the usage of the PVRDecoder, live with it as it is, or you may
go do the experiments that is needed with the decoderplugin in its current form and shape.

Start with a value of .. say .. 40 - as sectroyer mentioned ... And did you try 10, as sectroyer asks ?