magic144
16th March 2006, 20:52
Just sat down to watch my 1.08.1 Pro rebuilt version of Elizabethtown (R1) last night on the DVD player and noticed a video hiccup about 3 mins in (I'll confirm the exact location when I get back home tonight) - it's a scene where Orlando Bloom is sitting at his desk remembering working at the company, immediately before a scene change.
As usual my rebuild was movie-only mode, keeping only the DD5.1 soundtrack and the English subtitles.
Basically some erroneous "blocks" flash on the screen briefly - obviously this does not happen on the original source. This video is in the 2nd segment that Rebuilder submits to the encoder (the first segment is a very brief film logo). The error can also be seen by playing the individual .m2v segment file (i.e. it is inherent in the generated video before any reassembly/3rd-phase-rebuilder processing).
I thought it might have been a bad +R disc, but upon rebuilding, the same problem shows itself from the hard-drive files, repeatably at the same spot (using PowerDVD 6)
This build was done using DGDecode 1.4.5 (as is distributed with the newest versions of Rebuilder Pro). Rebuilder is set to use the default DCT mechanism with DGDecode (I've never bothered setting a specific algorithm, never needed to).
Out of curiousity, I re-ran the build using DGDecode 1.1.0 from older distributed versions of RB. The glitch still happens at the same place but is much less obvious on-screen - it's more of a "stuttering" in a couple of parts of the picture.
I've looked at the source VOB using DGIndex (with 1.4.5) and don't see the problem from within that tool (I don't know if it gives precise enough access to the frames, but I would have thought it did using the "<" and ">" on-screen buttons to skip between frames.
I also earlier tried reencoding the same segment using HC Enc 0.17 (I usually use CCE 2.70.02.04 SP Trial) but got the same result, hence my looking into DGDecode variations. I have the usual AviSynth 2.5.5 installed as ever it has been.
@jdobbs, can you reproduce this issue at all? I will confirm all the exact details tonight when I get back home. I'm wondering if there is a problem in DGDecode, or in the way Rebuilder is driving it...
Let me know if you find anything or if you want me to report some specific details or run some specific tests - as ever, I will oblige!
Thanks again,
m
As usual my rebuild was movie-only mode, keeping only the DD5.1 soundtrack and the English subtitles.
Basically some erroneous "blocks" flash on the screen briefly - obviously this does not happen on the original source. This video is in the 2nd segment that Rebuilder submits to the encoder (the first segment is a very brief film logo). The error can also be seen by playing the individual .m2v segment file (i.e. it is inherent in the generated video before any reassembly/3rd-phase-rebuilder processing).
I thought it might have been a bad +R disc, but upon rebuilding, the same problem shows itself from the hard-drive files, repeatably at the same spot (using PowerDVD 6)
This build was done using DGDecode 1.4.5 (as is distributed with the newest versions of Rebuilder Pro). Rebuilder is set to use the default DCT mechanism with DGDecode (I've never bothered setting a specific algorithm, never needed to).
Out of curiousity, I re-ran the build using DGDecode 1.1.0 from older distributed versions of RB. The glitch still happens at the same place but is much less obvious on-screen - it's more of a "stuttering" in a couple of parts of the picture.
I've looked at the source VOB using DGIndex (with 1.4.5) and don't see the problem from within that tool (I don't know if it gives precise enough access to the frames, but I would have thought it did using the "<" and ">" on-screen buttons to skip between frames.
I also earlier tried reencoding the same segment using HC Enc 0.17 (I usually use CCE 2.70.02.04 SP Trial) but got the same result, hence my looking into DGDecode variations. I have the usual AviSynth 2.5.5 installed as ever it has been.
@jdobbs, can you reproduce this issue at all? I will confirm all the exact details tonight when I get back home. I'm wondering if there is a problem in DGDecode, or in the way Rebuilder is driving it...
Let me know if you find anything or if you want me to report some specific details or run some specific tests - as ever, I will oblige!
Thanks again,
m