GBPVRConvert problems (again)

[bgowland]

I'm still seeing inconsistencies with the auto-transcode feature. I have it set to autoconvert dvr-ms -> mpeg2 using ASAP for the timing.

I just set 4 test recordings going on my Nova-t sources - one from 16:55 to 17:40 and the other three all from 17:00 to 17:30 (1/5 mins pre/post padding on all).

The GBPVRConvert.exe-native-3.log consists of just this and nothing else...

Code:

17:35:08.562    INFO    Log started
17:35:08.562    VERBOSE    SOURCE:D:\GB-PVR\8 Simple Rules for Dating My Teenage Daughter\8 Simple Rules for Dating My Teenage Daughter_20051026_17001730.dvr-ms  DEST:D:\GB-PVR\8 Simple Rules for Dating My Teenage Daughter\8 Simple Rules for Dating My Teenage Daughter_20051026_17001730.mpg   TYPE:MPEG-2   RECORDING_OID:4268

The mpg file didn't get created and the dvr-ms file still exists.

The -2 and -1 versions of the log show log started times of 17:37:08 and 17:39:08 respectively and show DB updates and successful transcode completion entries. In both cases the mpg files look OK and the dvr-ms files are deleted. Similarly the latest version of the log shows the 4th recording being successfully transcoded etc. starting at 17:45.

I checked Task Manager to see if there was a 'stuck' instance of the GBPVRConvert.exe running but there wasn't. I also opened the mdb to see if the programme oid was still in the [transcode_queue] table but it was gone.

This time I didn't see the C++ debug error box shown in this post http://forums.gbpvr.com/showpost.php?p=6...ostcount=1.

Do you think it might be worth trying a different version of the Cyberlink mux or is this more likely an internal error in GBPVRConvert.exe?

Cheers,
Brian

[sub]

I can only guess that GBPVRConvert.exe crashed on that file for some reason, but log doesnt give us much to go on.

If you manually try to run it on that same file with the arguments from the log, does it succeed or fail? If it fails consistantly, we'd at least have a good test case for me to supply you updated versions of GBPVRConvert.exe with more logging.

[bgowland]

Tried it 3 times now - failed each time with the same sort of log output as above (just the two lines).

Something occurs to me - is this a command-line length issue? The first time I tried it manually, I forgot to put the prog. oid at the end of the command line and got the same debug error as in the link to my previous thread. The same effect as if the command was being truncated???

I'll be happy to try with another GBPVRConvert.exe and send on the logs.

[sub]

Can you run it without the oid, but with source, dest and "MPEG2", then post the exact command line you used and the resulting GBPVRConvert.exe-native.log?

[bgowland]

Working things out here.

I tried without the oid and got the debug error. I've included a screenshot. On the command prompt window you'll see the command line used - also the same command (above it) WITH oid. When I provide the oid, nothing happens, except for the two lines in the log file.

Without the oid the log looks like the way I've included - this is the log 'as is' with the error box still on the screen and I have a 'stuck' GBPVRConvert.exe listed in Task Manager.

[sub]

I've just emailed you another version to try. I think the long file name was blowing the buffer of one of the debug messages.

[bgowland]

Tried it.

With the oid, it still does nothing - the log just has the two lines similar to previous attempts with a new one saying it supports modified audio connections.

Without the oid it runs and transcoding goes ahead but I see the debug error at the end of the process (not at the beginning this time though) - presumably because it's expecting to update the DB?

Clicking ignore closes it but dvr-ms file remains.

Log included.