Transcoding stopped working

[bgowland]

I have Config set to auto-convert my dvr-ms recordings to mpeg-2 ASAP. A week or so ago I was experimenting with different Cyberlink mux versions on my system and since then (I think) the auto-conversion has been failing. The log says that it can't find a mux filter. Here's how it looks when I run it manually

Code:

17:34:47.884    INFO    Log started
17:34:47.884    VERBOSE    Supports modified audio connections...
17:34:47.884    VERBOSE    SOURCE:D:\GB-PVR\Little Voice\Little Voice_20070202_22002350.dvr-ms  DEST:D:\GB-PVR\Little Voice\Little Voice_20070202_22002350.mpg   TYPE:MPEG-2   RECORDING_OID:3808
17:34:47.884    VERBOSE    File is DVR-MS
17:34:47.916    VERBOSE    Converting .DVR-MS file to .MPG
17:34:47.916    VERBOSE    FindFilterByName(StreamBufferSource)
17:34:48.040    VERBOSE    FindFilterByName(GB-PVR Writer)
17:34:48.071    VERBOSE    FindFilterByName(3808)
17:34:48.087    ERROR    FindFilterByName failed to locate filter: 3808
17:34:48.087    ERROR    No mux filter found. Exiting...

But this is what I see if I use the BDA mux checker.

Code:

GB-PVR has detected the following multiplex filters on your machine:

Found: ATI MPEG Multiplexer
FILE: C:\Program Files\devnz\gbpvr\atidvcr.dll
VERSION: 9.12.0.60312

Found: CyberLink MPEG Muxer
FILE: c:\windows\system32\MpgMux.ax
VERSION: 5.0.0727

I've unregistered and re-registered the mux but no improvement. Any ideas.

Cheers,
Brian

[bgowland]

Doh! Don't worry - I know what's happened.

sub - you gave me a new version of the GBPVRConvert.exe that takes the name of a muxer as its 4th parameter. GBPVR is passing the recording oid as the fourth parameter (and I was copying this when doing it manually).

Hence what is being logged...

17:34:48.087 ERROR FindFilterByName failed to locate filter: 3808

I'll switch back to the original exe.

Cheers,
Brian

[sub]

Yeah, that'll be it. I'll fix it for the next release.

[bgowland]

Cheers.

It was probably more like 3 weeks ago now I think about it. That'll explain why I'd forgotten about the new exe. Things are back to normal now.