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
On 9/20/05, Lucian Muresan lucianm@users.sourceforge.net 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
Hi all!, And what about this error I asked in the list???? Anyone can help me?
I have compiled the 0.0.6h plugin version correctly with vdr-1.3.31 but when I try to use it fails. In dvd.log I see:
Parameter validation not complete yet Initialising and analysing the streams.... Can not open /video/Passatgers/2005-09-08.22:00.99.99.rec001.vdr: File not exists
The correct file is
/video/Passatgers/2005-09-08.22:00.99.99.rec/001.vdr Note the slash between .rec and 001
I supose it's a bug but I don't know where can I solve it. vdrburn.sh? If not is a bug, what is the problem?
Another question about vdr-burn. I have searched it but I see a lot of info in german, and not understand it. Is possible to burn a dvd-rw without have formatted it before? the plugin format the dvd or I have to use a blank dvd?
Thank you.
En/na Guy Roussin ha escrit:
Hi,
Anyone seen that before?
Yes, I also get the same with 0.0.6i-pre2.
Note that, even with only one big movie (>4,4Gb), the requant factor (-f) is too high. So, the iso image generated thus is compressed too much.
Guy
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
mike lewis wrote: [...]
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 ;-).
Alright Mick, please share your fix when you get to your PC :-). Was this old files issue discussed on this list? I surely replaced the vdrburn.sh script with the latest one, but maybe the bug resides in one of the other scripts? As for the plugin sources themselves, I'm pretty sure I've got no old files around and let gentoo compile them several times...
Lucian
On Tue, 2005-09-20 at 09:33 +0200, Leo Márquez wrote:
I have compiled the 0.0.6h plugin version correctly with vdr-1.3.31 but when I try to use it fails. In dvd.log I see:
Parameter validation not complete yet Initialising and analysing the streams.... Can not open /video/Passatgers/2005-09-08.22:00.99.99.rec001.vdr: File not exists
That error smells like it's coming from vdrsync.
All the examples in "vdrsync.pl --help" have trailing slashes in recording dir names and in fact in the 050322 version, at least get_file_list() (the latter in the file, in the VDRRECORDING package) looks like it'll break if the path to the recording dir does not end with a slash.
The attached patch could help (untested).
mike lewis wrote:
On 9/20/05, Lucian Muresan lucianm@users.sourceforge.net wrote:
[...]
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 ;-).
I found a patch which addresses this on the german VDR-portal forum. I will only get to test it later tonight, but if someone wants to give it a try... http://www.vdr-portal.de/board/attachment.php?attachmentid=7013 The thread for those who understand german: http://www.vdr-portal.de/board/thread.php?threadid=37768
Lucian
Lucian Muresan wrote: [...]
I found a patch which addresses this on the german VDR-portal forum. I will only get to test it later tonight, but if someone wants to give it a try... http://www.vdr-portal.de/board/attachment.php?attachmentid=7013 The thread for those who understand german: http://www.vdr-portal.de/board/thread.php?threadid=37768
For those interested, I applied that patch to 0.0.6h and it worked well!
Now, I have few patches for the burn plugin, I'd be ready to send later today, one of them adjusts the compression ratio to better fit requanted discs to the maximum DVD size, another one introducing a new "author only" store mode and another one related to i18n. I also might work on some more ideas I have, but my question is, who's maintaining this plugin right now actually, is it actively maintained? I'd like to know, because I'd like us to be effective with these patches and I don't know if someone is already working on other enhancements or bug fixes...
Lucian
On Mittwoch 21 September 2005 09:52, Lucian Muresan wrote:
[ ... ] but my question is, who's maintaining this plugin right now actually, is it actively maintained? I'd like to know, because I'd like us to be effective with these patches and I don't know if someone is already working on other enhancements or bug fixes...
This 0.0.6xy stuff is maintained by me. Actually I don't had too much time for it the last few month but I try to integrate fixes whenever possible. I will see if I will find some hours for it this weekend.
Regards Ralf