[vdr] Re: vdr2dvd - sorry guys: one problem solved, already thenext arrives...

[Dirk Hartmann <dha@morticah.net>]

--On Freitag, Februar 07, 2003 18:17:53 +0100 Ulrich Gierschner 
<ug@teuto.de> wrote:

> Hi,
>
> After getting the Jave Runtime environment working,
Sorry, I only read the list from time to time. But after you found a 
apt-source for java, here is a interresting Site for the future:
http://www.apt-get.org ;-)

> the next problem
> arrives....
> After ds.jar is executed, transcode is not able to encode the file....
>
> Here's the output....
>
> ================================================
>
> ===> new File: /var/dvd/tmp/vdralltemp.mpv
> --> MPEG Audio (0xC0)
> Audio PTS: first packet 03:31:33.646, last packet 03:52:32.398
> Video PTS: start 1.GOP 03:31:33.953, end last GOP 03:52:32.473
> -> adjusting audio at video-timeline
> => src_audio: MPEG-1,Layer2,48kHz,jointstereo,160kbps,CRC @ 00:00:00.000
> -> 13 frame(s) (312ms) inserted @ 00:18:07.728.mp
> -> 6 frame(s) (144ms) inserted @ 00:18:09.288
> audio frames: wri/pre/skip/ins/add 52295/0/0/19/0  @ 00:20:55.080 done..
> -> 89 stereo/jointstereo change(s) detected...
> ===> new File: /var/dvd/tmp/vdralltemp.mp2
>
> Video:	31377 Frames	00:20:55.080		vdralltemp.mpv
> Audio 0:	52295 Frames	00:20:55.080	0/0/19/0	vdralltemp.mp2
> => 842743593 bytes written...

!!!---- Here is no output of mplex.
And that is the Problem. After demuxing the File with ds.jar and before 
transcoding it, it must be remuxed with mplex


> transcode v0.6.3.20030109 (C) 2001-2003 Thomas Östreich
> file read error: Success

> Why does he try to read from /dev/zero ??
Because there was no input file generated.

> I think I set up the perl script directly ... or Do I have to set up
> something depending on the output-File?
Yes you need to set up the path to mplex correctly. Mplex is part  of 
mjpegtools.
You can apt-get it from

deb http://marillat.free.fr/ stable main
or directly grab the original deb from mjpeg.sourceforge.net

> vdr2dvd.pl --help says
> vdr2dvd.pl [ options ] directory1 [ directory2, ...directoryN ]
> but nothing about any output files. These are definend statically in the
> script, aren't they?
They are, because they all are only used inside the script.

Didn't realize there is no output when the command fails, will change this 
in next Version.

Dirk

--
dha@morticah.net




--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.