AutoConvertTSCommand blues

[daneo]

Hi Sub,

I'm still worrying on the TS transcoding issues in the current build, and tried to see if an elegant work-around could be found. Unfortunately, I find more difficulties than solutions.

I've made a custom ffmpeg conversion string

[INDENT]<CustomFFmpegConversions>
<Conversion name="DanesTS" cmd="-y -i {SOURCE_FILE} -vcodec copy -acodec copy -f dvd {DEST_FILE}" targetExtension=".mpg" />
</CustomFFmpegConversions>[/INDENT]

and configured it for the automatic TS file conversion instead of the default "MPEG-2" option which is currently not useable.

[INDENT]<AutoConvertTSToFormat>DanesTS</AutoConvertTSToFormat>
<AutoConvertTSCommand>-y -i "{SOURCE_FILE}" -vcodec copy -acodec copy -f dvd "{DEST_FILE}"</AutoConvertTSCommand> [/INDENT]

I keep getting zero-length MPG files when I try to transcode this way, and see the following in my log file:

[INDENT]2008-12-27 23:02:27.276 VERBOSE [14] About to start transcode of: E:\Recordings\Manual Recordings\manual_1_20081227225800.ts
2008-12-27 23:02:27.276 VERBOSE [14] getValue cached value: /settings/AutoConvertTSToFormat : DanesTS
2008-12-27 23:02:27.276 VERBOSE [14] About to run transcode command: C:\Program Files\Devnz\GBPVR\Third Party\FFmpeg\ffmpeg.exe -y -i "E:\Recordings\Manual Recordings\manual_1_20081227225800.ts" -vcodec copy -acodec copy -f dvd "E:\Recordings\Manual Recordings\manual_1_20081227225800.mpg"
2008-12-27 23:03:27.416 INFO [14] File transcode has completed unsuccessfully...[/INDENT]

Any suggestions?

Thanks,
Dane

[sub]

What output do you get from ffmpeg when you run the transcode manually from a command prompt:

"C:\Program Files\Devnz\GBPVR\Third Party\FFmpeg\ffmpeg.exe" -y -i "E:\Recordings\Manual Recordings\manual_1_20081227225800.ts" -vcodec copy -acodec copy -f dvd "E:\Recordings\Manual Recordings\manual_1_20081227225800.mpg"

[daneo]

Hi Sub,

sorry, I planned to add this to the email but forgot to re-type it when I accidentally closed my browser..

The manual transcode works fine, but I need to quote the program name of course.

Regards,
Dane

[sub]

So whats the problem then?

[daneo]

Hi Sub,

the problem is simple -- when GBPVR does the transcode, I get an error message and a zero-byte file. When I run the transcode manually on a command line, it works.

Dane

[sub]

It should produce exactly the same results if you're running the same command line as shown in the GB-PVR logs. I'm not aware of any reason it'd be any different.

[daneo]

Hi Sub,

you're 100% correct -- it would do so if I were using the "GBPVR" version of ffmpeg -- but I've been working with a newer version to try and iron out timing glitches with the TS files (just realised this is the bug, tried it just now).

Soooo.....

Given that I've "caused" the problem in the first place -- how do I configure GBPVR to use a newer version of ffmepg?

Thanks,
Dane

[sub]

The easiest way is probably to replace the GB-PVR version of ffmpeg.exe with the updated file you have.

[daneo]

Hi Sub,

that's the rub -- when simply "drop in" the new version of ffmpeg.exe, I get the zero-byte files.

When I put the old version back, it works.

Any suggestions on debugging the command line?

Thanks,
Dane

[sub]

Sorry, I dont know what to tell you. You can see the command line GB-PVR is using in the logs.