[bug] vdr-burn-0.0.6h - badly mixed up multiple recordings when requanting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/20/05, Lucian Muresan <lucianm@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi,
> 
> I managed to setup vdr-burn-0.0.6h and am actually very pleased of the
> comfort it offers compared to manually demux/cut recordings with
> ProjectX and then also manually (even with GUI programs) author them on
> DVD. However, I'm encountering a strange problem when trying to generate
> a DVD consisting of 2 recordings which need requanting: It ends up with
> the second movie muxed instead of the first one, so the DVD contains a
> menu with 2 different entries and descriptions and movie titles, but the
> actual movie is the same. See a dvd.log in which I only left the
> relevant stuff at:
> http://www.muresan.de/vdr-burn/burn-0.0.6h_dvd.log.1.txt
> It seems to me that even the REQUANT step uses the correct paths and
> tracks, but right after that, the MPLEX step muxes the tracks from the
> .../VDRSYNC.0/ directory into .../VDRSYNC.1/movie.mpg (it should have
> taken the tracks also from /VDRSYNC.1/, don't know why 1 before 0, but
> anyway, that shouldn't have mattered), and the next MPLEX muxes again
> (but this time correctly) the tracks from .../VDRSYNC.0/ into
> .../VDRSYNC.0/movie.mpg, so the 2 "movie.mpg" are absolutely identical.
> 
> I also made a test DVD structure with very small recordings, so they
> didn't need the REQUANT step, the result is as expected, and the log
> also looks OK.
> http://www.muresan.de/vdr-burn/burn-0.0.6h_dvd.log.2.txt
> 
> Anyone seen that before?
> Regards,
> Lucian
> 
Yes, I get the same using 6f.  What you will find if you scan trhough
the logs is that its actually calling requant on the same file each
time (the first or last in order or menu).

Apparantly its a bug which was old and was meant to have been fixed
(according to the author).  He recomended I do a full cleanout and
fresh download of vdr-burn...  maybe there are some old files
somewhere causing the issue..  I have not had time to do this yet, so
I've altered some settings in the bash script used when requant is
called.  My fix was very simple but i'm not at the PC to reverse
engineer and tell you ;-).


Mick


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux