Bug Thread for Serious Beta Testers

[jdobbs]

All,

Ok it's getting down to crunch time and before I can get v1.00 out and I want to squash the remaining bugs. So I've lined up some time for the next couple of weeks to go on a hunt.... and for those who'd like to participate, I'd really appreciate your help.

I really want to avoid snipe hunts. This thread is for repeatable bugs you personally experience only. If you heard your uncle's neighbor got an error last week -- that doesn't qualify. I also don't want this to become a complaint thread. That's not the purpose. Be warned -- complaint posts will be removed.

Please post only once for your bug. Please DO NOT post if you have preprocessed at all. I'm looking for DVD-RB bugs only and just want to avoid spending time trying to find problems related to possible erroneous sources. If you see a bug report for something that you also have experienced -- reference the error and post a quote from the error post and a single line that says "I can confirm this error."

Please provide the following information and please number it like I have it below so I can tell where it belongs:

1. Description of the bug. What happened and how. Describe the exact wording of the error messages.
1.a. If the problem is related to playback, indicate specifically what player(s) you've tried it on.
2. When it happened exactly. Was it in PREPARE, ENCODE, or REBUILD? At what point in that phase? How much had completed? Identify the segment that was processing at the point of error.
3. What DVD were you processing? Is it commercial or homemade? Identify whether it is PAL or NTSC, and the Region.
4. Create a zip file containing the info below and send it to DVD-RB@COMCAST.NET -- identify your DOOM9 name and the error to which it relates in the e-mail:
4.a. The LOG file from the job.
4.b. The REBUILDER.INF file from the \D2VAVS directory.
4.c. The REBUILDER.INI file from the DVD-RB directory.
4.d. If possible include a text listing of the \D2VAVS directory and the VIDEO_TS directory at the time of failure.
4.e. REBUILDER.ECL file, if it exists
4.f. If it stops at a particular segment. Include the AVS.
5. Identify the encoder selected and it's version. If possible click on the "Display Versions" menu option before your job starts so it will be in the LOG file (4.a).
6. The filesize of the DGDECODE version you are using. That's the only sure way to know the version.
7. Do not post if you are not using DVD-RB v0.77 or above.

After you post -- please don't continually ask about the status. I will let you know...

Don't mean to make too much work for everyone. But it's time to get serious. I want to make this package solid as a rock before I release version 1.00. I appreciate all your help.

Thanks,
jdobbs

[rayvt]

This isn't really a bug, more like a heartburn that people will continually be surprized and puzzled and gripe about when they encounter it.
A movie that has large chunks of angles or interleaves comes out oversized and/or goofy.
It would be nice if Rebuilder would give a warning when the angle/interleave is so large that there will be trouble. At least then people would know why it came out oversized.


I just did Hannibal, Disk 2 (extras), which evidently has huge segments angle segements. As shown below, VTS7 doesn't get shrunk at all. Only one frame is given to CCE! DVD-RB v0.79

(I set ILVU_EXTRACT=1 just to see the sizes.)

Rebuilder.log has
- VTS_07: 995,445 sectors.
-- ANGLE and/or INTERLEAVING is present.
-- Scanning and writing .D2V file
-- Processed 85,186 frames.

[ILVU]
VTS_05=VTS_12
VTS_06=VTS_13
VTS_07=VTS_14
...
[V0700006]
Last_Sector=995445
[V07000000006001]
...
Frames=1

07000000006001.AVS has:
LoadPlugin("G:\dvd-rb\DGDecode.dll")
mpeg2source("F:\00-DVDRB\D2VAVS\V07.D2V",idct=7)
trim(85185,85185)
...

i:/DVD Rips/HANNIBAL2/VIDEO_TS has
3/19/2005 14:59 69,632 VTS_07_0.IFO
3/14/2005 19:24 10,240 VTS_07_0.VOB
3/14/2005 19:26 1,073,709,056 VTS_07_1.VOB
3/14/2005 19:27 964,962,304 VTS_07_2.VOB

f:/00-dvdrb/D2VAVS has
3/19/2005 16:05 326,496,256 VTS_12_1.VOB
3/19/2005 16:08 997,156,864 VTS_13_1.VOB
3/19/2005 16:15 1,073,739,776 VTS_14_1.VOB
3/19/2005 16:15 964,921,344 VTS_14_2.VOB

[jdobbs]

You're right. That isn't a bug.

[Craz]

As you requested here (http://forum.doom9.org/showthread.php?s=&threadid=91363).

1. & 2.
Runtime error '6': overflow.
At 96.6% of the REBUILD phase.
DVDRB was processing the last m2v file (V01001400001015.m2v - 106mb)

3. DVD title was a Dutch Theatre DVD (Kommil Foo, commercial, PAL R2). Only 1 VTS, no extras, only main movie and menu (main menu + scene selection menu)

4. Emailed you a zipfile containing:
- dirlisting.d2vavs.txt
- dirlisting.video_ts.txt
- REBUILDER.ECL
- REBUILDER.INF
- rebuilder.ini
- rebuilder.log
- V01001400001015.AVS

5. Selected CCE (new), using CCE v2.66.01.07, DVDRB v0.78, AviSynth 2.5.2

6. Using MPEG2Dec3dg.dll, filesize 254.033 bytes

7. NOTE:
I did do some preprocessing. Like I've said in the thread mentioned earlier, the disc gave quiet some problems getting ripped to my hard disc. It worked in ISO mode but gave me an error on IFO patching. The iso however played perfect in powerdvd, but couldn't be processed using DVDShrink, DVDRB, Big 3 method (DIF4U, ReAuthorist, Scenarist). After doing a mock strip on the iso file, I was able to process it using DVDShrink only. DVDRB and Big 3 method still gave problems. Then I've ran the dvd folder from the mock strip through DVDremake pro (imported it, and exported it again without doing any further actions). After DVDremake I was able to process it using the Big 3 method as well, But still not using DVDRB.
The logs I'm providing here are the ones from using the DVDremake iso, since I'm sure the original iso file did have errors not related to DVDRB. But since I got DVDShrink and Big 3 method working now (especially the last one) I'm thinking there could be an error in the way DVDRB processes this.

Let me know if you find something, or choose not to search for this one (since it has been preprocessed).

[Rippraff]

Dear jdobbs,

this is a bug (or three ;)) concerning your new function build in version 0.78:
Originally posted by jdobbs
- Added a check after each encode to warn if the resulting .M2V file was not created. This is to counter some #0003 errors that may be experienced during the rebuild phase of the affected segment.
1. If CCE is crashing (for what reason ever ;)) RB (currently using DVD-RB 0.79 with CCE SP 2.70.02.00) gives an error message

http://www.rippraff.de/Pics/RB_M2V_error_message.jpg

and RB stops until you press the OK button. Afterwards RB/CCE restarts with the next segment.
So if you decide to Stop/Pause your encoding and reencode by resuming

http://www.rippraff.de/pics/RB_resume.jpg

you will get into a bad loop, after hitting "yes". => you'll get message 1 again and currently there's no way out of this.

Laserman of the german doom9 forum has found a hint: Before resuming decrease the number of Encode_Progress= in the REBUILDER.INF by one => missing segment will be reencodet.

2. "Suppress Warning Prompts" doesn't work with this check => RB stops allways.

3. The check works only if the CCE crash happens during build of .vaf but not during later passes.

IMHO I'ld prefer this check deletet until "Suppress Warning Prompts" works because I do all my encodings over night. If there's a m2v missing bad luck :sly: but I don't have any problem to reencode the missing segment by modifying the REBUILDER.ECL.

Nearly forgotten to say: I love your programme! :) :thanks:

Best regards
Rippraff

[b1ackmai1er]

Transcoding... <<<<<<<<<<<<<<<<<<<<<<<<
-----------------
[23:14:45] Phase I, PREPARATION started.
- "One Pass VBR (w/analysis)" mode is enabled.
- VTS_01: 2,785,235 sectors.
-- Scanning and writing .D2V file
-- Processed 182,045 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 78.2%
- Overall Bitrate : 4,721Kbs
- Space for Video : 4,196,078KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):2,129,510
-- Sampling 3648 of 182045 frames.
-- Predicted size (sectors) at Q=22: 2,176,547
- Q Value selected: 22
- HIGH/LOW/AVERAGE Cell Bitrates: 8,808/3,492/4,721 Kbs
[23:29:58] Phase I, PREPARATION completed in 15 minutes.
[23:29:58] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
[02:38:21] Phase II ENCODING completed in 189 minutes.
[06:35:29] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 3 CELLID: 1
- Rebuilding segment 1 VOBID: 3 CELLID: 2
- Rebuilding segment 2 VOBID: 3 CELLID: 3
- Rebuilding segment 3 VOBID: 3 CELLID: 4
- Rebuilding segment 4 VOBID: 3 CELLID: 5
- Rebuilding segment 5 VOBID: 3 CELLID: 6
- Rebuilding segment 6 VOBID: 3 CELLID: 7
- Rebuilding segment 7 VOBID: 3 CELLID: 8
- Rebuilding segment 8 VOBID: 3 CELLID: 8
- Rebuilding segment 9 VOBID: 3 CELLID: 9
- Rebuilding segment 10 VOBID: 3 CELLID: 10
- Rebuilding segment 11 VOBID: 3 CELLID: 11
- Rebuilding segment 12 VOBID: 3 CELLID: 12
- Rebuilding segment 13 VOBID: 3 CELLID: 13
- Rebuilding segment 14 VOBID: 3 CELLID: 14
- Rebuilding segment 15 VOBID: 3 CELLID: 15
- Rebuilding segment 16 VOBID: 3 CELLID: 16
- Rebuilding segment 17 VOBID: 3 CELLID: 17
- Rebuilding segment 18 VOBID: 3 CELLID: 18
- Rebuilding segment 19 VOBID: 3 CELLID: 19
- Rebuilding segment 20 VOBID: 3 CELLID: 20
- Rebuilding segment 21 VOBID: 3 CELLID: 21
- Rebuilding segment 22 VOBID: 3 CELLID: 22
- Rebuilding segment 23 VOBID: 3 CELLID: 23
- Rebuilding segment 24 VOBID: 3 CELLID: 24
- Rebuilding segment 25 VOBID: 3 CELLID: 25
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
Correcting VTS Sectors...
[06:54:04] Phase III, REBUILD completed in 19 minutes.

Done.

[jdobbs]

IMHO I'ld prefer this check deletet until "Suppress Warning Prompts" works because I do all my encodings over night. If there's a m2v missing bad luck but I don't have any problem to reencode the missing segment by modifying the REBUILDER.ECL. That message will not be displayed if you are doing a batch encode. It will only be shown in the LOG.

As for the loop, I'll find out what's causing it.

Transcoding... <<<<<<<<<<<<<<<<<<<<<<<< In the true sense of the word DVD-RB is "transcoding" -- but that word has come to imply "within-the-compressed-domain" transcoding, so I changed it in v0.80

[Rippraff]

@jdobbs

I didn't know, that you were working on this stuff the last days. ;)
With version 0.80 nearly everything works fine now. :thanks:
Nr 1. solved now, because RB aborts after the third unsuccessful attempt => can be resumed now without problems. :)

Nr 2. Don't know but not so important now. IF CCE crashes three times in a row, there must be something wrong with your source material, your system or a complete overclocked machine. ;)

Nr 3. Still exists, when CCE crashs during m2v build DVD-RB continues with the next segment. Maybe you can implement a check comparing the frame numbers .avs/.ecl <=> .m2v ? Just an idea.

Nevertheless thanks again for your great work!

Cu Rippraff

Edit: That message will not be displayed if you are doing a batch encode
Okay, thanks for the advice, I didn't try it with batch encode.

[jdobbs]

I didn't know, that you were working on this stuff the last days. I always try to fix anything that is reported. :)

[wfn1]

Hi,

1. ERROR 0006: DVD-RB has found framecount differences between the prepare and rebuild phases. Aborting. Clicking OK closes the program.

2. Happens 69.8% into rebuld stage on file V01003200001033.M2V

3. Commercial, dual layer Rambo Extreme Edition R1 NTSC

4. Files on the way as I'm typing.

5. CCE SP 2.70.02.00, DGDecode 1.1.0 (01/21/2005 07:12PM 262,222 bytes)

a bit of extra information: disk image is mounted via Daemon Tools 3.47 via an .MDS file. the files being sent are from an OPV encode; multipass VBR encode yields the same exact error message on the same segment (segment 32 VOBID: 1 CELLID: 33)

[lamster]

Originally posted by jdobbs
As for the loop, I'll find out what's causing it.
I think I ran into the same thing when trying to set up a new machine. QuEnc wasn't working (don't know why).

After clicking "OK" on the "Encoder error" dialog, the next "Encoder error" dialog would pop up before I could click on the button to stop the attempt. One way to resolve this would be to have a button on the "Encoder error" dialog that would say to stop encoding.

[jdobbs]

Originally posted by lamster
I think I ran into the same thing when trying to set up a new machine. QuEnc wasn't working (don't know why).

After clicking "OK" on the "Encoder error" dialog, the next "Encoder error" dialog would pop up before I could click on the button to stop the attempt. One way to resolve this would be to have a button on the "Encoder error" dialog that would say to stop encoding. That should be gone now. Version 0.80 will reencode automatically if the .M2V is missing. If it happens 3 times in a row, it will stop and give you the error message. If that happens it's a bigger problem than the encoder just exiting prematurely.

[EDIT] Actually I think I missed the point of your post... Ok, I'll but an option to cancel/continue when if it fails after 3 retries.

[jdobbs]

Nr 3. Still exists, when CCE crashs during m2v build DVD-RB continues with the next segment. Maybe you can implement a check comparing the frame numbers .avs/.ecl <=> .m2v ? Just an idea. I guess I should just abort that encode, eh? It's going to be garbage anyway.

[jdobbs]

Originally posted by wfn1
Hi,

1. ERROR 0006: DVD-RB has found framecount differences between the prepare and rebuild phases. Aborting. Clicking OK closes the program.

2. Happens 69.8% into rebuld stage on file V01003200001033.M2V

3. Commercial, dual layer Rambo Extreme Edition R1 NTSC

4. Files on the way as I'm typing.

5. CCE SP 2.70.02.00, DGDecode 1.1.0 (01/21/2005 07:12PM 262,222 bytes)

a bit of extra information: disk image is mounted via Daemon Tools 3.47 via an .MDS file. the files being sent are from an OPV encode; multipass VBR encode yields the same exact error message on the same segment (segment 32 VOBID: 1 CELLID: 33) Well I finally got Rambo: First Blood Extreme Edition R1 NTSC yesterday and ran it overnight... it encoded and was rebuilt with no issues. I used CCE SP 2.70, DGDECODE 1.1.0 and DVD-RB v0.80...

I'll start comparing the files you sent me to what I have in my D2VAVS directory...

[jptheripper]

just to let you know

im using cce 2.50 with rockas latest installer and 0.80pr

0 errors, 0 glitches, 0 problems

rock solid and reliable for me, ty

course my last encode did take 3166 minutes (4 pass)

[wfn1]

Originally posted by jdobbs
Well I finally got Rambo: First Blood Extreme Edition R1 NTSC yesterday and ran it overnight... it encoded and was rebuilt with no issues. I used CCE SP 2.70, DGDECODE 1.1.0 and DVD-RB v0.80...

I'll start comparing the files you sent me to what I have in my D2VAVS directory...

Thank you for the update, did you use DVD Decrypter ISO mode + Daemon Tools 3.47 or File Mode? Also, whichever mode you used what do you have checked in DVDDecrypter under Tools > Settings > xxxx Mode > Options. Could stripping PUOs possibly have that effect?

[jdobbs]

I used DVD Decrypter ISO mode (v3.5.2.0) and mounted it with Daemon Tools. I don't think changing the PUOs would have any effect.

[jdobbs]

Originally posted by jptheripper
just to let you know

im using cce 2.50 with rockas latest installer and 0.80pr

0 errors, 0 glitches, 0 problems

rock solid and reliable for me, ty

course my last encode did take 3166 minutes (4 pass) 3166 minutes!!! Do you have to shovel coal into your computer to get it to run? What processor/memory/hard drive combination are you using?

[jptheripper]

7200 rpm hard drives on seperate ided channels

1.5gb pc133 ram

p3 1ghz processor (you think thats limiting ? lol)

doesnt help I added undot().deen() on a 4 pass

quality is amazing considering sourcee material sucks

source is collectors edition speedracer r1 complete series on 5 disks, 11 episodes per disk, so its bloated as hell to start. Final bitrates at 1800kbps . Realizing now I should have turned matrices on :(. Cce speed was .400

again thanx for everything.

Just ordered a new work computer, ,p4 3.73 HT extreme 1066 fsb with 4gb ram and 500 gb sata drives. Should be a slight increase in processing speed

[jdobbs]

p3 1ghz processor (you think thats limiting ? lol)
doesnt help I added undot().deen() on a 4 pass Thise both are very limiting. undot().deen() is a real slowdown -- but it can sure help clean up grainy source material.

[wfn1]

Originally posted by jdobbs
I used DVD Decrypter ISO mode (v3.5.2.0) and mounted it with Daemon Tools. I don't think changing the PUOs would have any effect.

eek.. well i was using 3.5.3.0 at the time but i doubt that it would make any difference. just by the looks of it as far as the dgdecode size, etc. is it pretty much kosher? i'll be awaiting the your conclusion after you analyse the files i sent you. thank you!

[Rockas]

doesnt help I added undot().deen() on a 4 pass

Do you really need that all the time?... have you ever tested using just undot() - I doesn't slow down... at least not much - on the other way I found that Deen() is a pain :)
Have you tried not to go above 3 passes? (I usually use 2 :))

keep it UP

[jptheripper]

sorry to side track thread. yeah i did need it but just on this disk. Usually i dont use it at all

[rayvt]

DVD-RB 0.80 PRO.
I did Led Zeppelin concert DVD. It has 3 audio tracks:
#1 is LPCM 2-ch size 1,189MB
#2 is AC3 5.1ch size 345MB
#3 is DTS 5-ch size 582MB
(as reported by dvdshrink--vobblanker reports similar)

IFOEdit show:
Title Set (Movie) attributes:
Video: MPEG-2 720x480 (NTSC) (NTSC 525/60) (4:3)
Audio 1: (Linear PCM) 2ch 48Kbps 16bps (ID: 0xa0)
Audio 2: (Dolby AC-3) 6ch 48Kbps DRC (ID: 0x81)
Audio 3: (DTS ) 5ch 48Kbps DRC (ID: 0x8a)
It shows the PGC as:
[0000000c] Audio stream 1 status 32768 [8000]
Audio stream 1 uses stream nr.: 0
[0000000e] Audio stream 2 status 33024 [8100]
Audio stream 2 uses stream nr.: 1
[00000010] Audio stream 3 status 33280 [8200]
Audio stream 3 uses stream nr.: 2
[00000012] Audio stream 4 status 0 [0000]
[

The DVD defaults to playing the LPCM track, but I didn't want to waste 1/4'th of the disk on the LPCM, so I unchecked that track in DVD-RB. When it's all done, Shrink shows the LPCM track still there, but size is 0MB. IFOedit shows same as above. When I play the DVD, I get no audio---because it is trying to play the empty track. I have to manually select a different audio to hear anything.

If I use shink (in no-compression mode) or vobedit (in keep everything mode), but de-select audio track #1, the DVD audio plays fine. It plays the AC3 track.
IFOedit shows:
Title Set (Movie) attributes:
Video: MPEG-2 720x480 (NTSC) (NTSC 525/60) (4:3)
Audio 2: (Dolby AC-3) 6ch 48Kbps DRC (ID: 0x81)
Audio 3: (DTS ) 5ch 48Kbps DRC (ID: 0x8a)
It shows the PGC as:
[0000000c] Audio stream 1 status 0 [0000]
[0000000e] Audio stream 2 status 33024 [8100]
Audio stream 2 uses stream nr.: 1
[00000010] Audio stream 3 status 33280 [8200]
Audio stream 3 uses stream nr.: 2
[00000012] Audio stream 4 status 0 [0000]


I believe that when the default track is non-existant, a player will just advance to the next track that isn't nonexistant.

Could you fix DVD-RB so that when you strip an audio track, that it will remove that stream from the PGC, in addition to skipping it?

[jdobbs]

Yes, I can do that. I've added it to the list.

[dannyv]

@JDOBBS

You may remember the problem I had on error 9 in rebuild on episodic disks caused by a single black frame. We worked on it in this thread starting about half way down.

http://forum.doom9.org/showthread.php?s=&threadid=75168&perpage=20&highlight=dannyv&pagenumber=6

I had not tested the previous 3 releases of RB on the projects I had saved but did so on the latest pro release.

All 3 problematic projects completed with out the error 9 and worked on PC and stand alone players.

The projects were

Star trek voyager season 7 disk 7

Star trek the original series season 3 I think it was disk 8 the last disk in the set

And Law & Order the first year the last disk in the set.

Great job

[jdobbs]

Cool. :cool: I was hoping that would be the case.

Still frame reencoding was causing too many problems. Encoders have a tendency to choke on them if the bandwith is limited at all. After giving it some thought I decided it was silly to reencode a single frame anyway, especially when I have to give it as much space as the original, and now the original I-FRAME just gets extracted and used.

[dannyv]

Originally posted by jdobbs
now the original I-FRAME just gets extracted and used.

I saw that change after reviewing the change logs for the last few releases and this is what prompted me to re-test. I'll keep the 3 projects for testing just in case any future changes or encoder updates affect RB.

[Sir Didymus]

Originally posted by dannyv
@JDOBBS
...
Great job

quoted, quoted. :)

[brashquido]

Originally posted by jdobbs

1. Description of the bug. What happened and how. Describe the exact wording of the error messages.

Movie is K:19 Widowmaker (PAL region 4), and using DVD-RB 0.81 Pro the entire DVD-RB process goes through smootly (no error messages), but the end product has some serious audio and video stutter for a small section. The stutter exists only in chapter three of VTS 4 (that I've found) and the stuttering begins at 23:20 into the movie, becomes really bad at 23:35 and then at 24:43 just starts playing normally again.
Originally posted by jdobbs

2. When it happened exactly. Was it in PREPARE, ENCODE, or REBUILD? At what point in that phase? How much had completed? Identify the segment that was processing at the point of error.

As there aren't errors at all during the DVD-RB process, I suspect it is a problem during the REBUILD phase when bring the multiangle content back into the movie. As above, the stuttering exists only in chapter three of VTS 4 (that I've found) and the stuttering begins at 23:20 into the movie, becomes really bad at 23:35 and then at 24:43 just starts playing normally again.
Originally posted by jdobbs

3. What DVD were you processing? Is it commercial or homemade? Identify whether it is PAL or NTSC, and the Region.

Commercial K:19 Widowmaker (PAL region 4) ripped to ISO via DVDDecrypter and then mounted using Daemon Tools.

Originally posted by jdobbs

4. Create a zip file containing the info below and send it to DVD-RB@COMCAST.NET -- identify your DOOM9 name and the error to which it relates in the e-mail:
4.a. The LOG file from the job.
4.b. The REBUILDER.INF file from the \D2VAVS directory.
4.c. The REBUILDER.INI file from the DVD-RB directory.
4.d. If possible include a text listing of the \D2VAVS directory and the VIDEO_TS directory at the time of failure.
4.e. REBUILDER.ECL file, if it exists
4.f. If it stops at a particular segment. Include the AVS.
5. Identify the encoder selected and it's version. If possible click on the "Display Versions" menu option before your job starts so it will be in the LOG file (4.a).
6. The filesize of the DGDECODE version you are using. That's the only sure way to know the version.
7. Do not post if you are not using DVD-RB v0.77 or above.

Check you mail :-). I didn't include an answer for 4.a or 4.f as the DVD-RB process isn't actually stopping. I forgot to include my CCE version which is CCE SP 2.66.01.07

[Rockas]

@brashquido
I'll try to find that DVD but I can only test it on a Region 2 version... hope they're the same :)

By the way... is that a good film?

if it isn't ... I'll go out there searching for you :D

keep it UP

[jdobbs]

@brashquido

Thanks. I'll see what I can find in the ILVU reassembly code.

Just to be positive: is the section that is having problems definitely ILUV?

[lamster]

@jdobbs - perhaps it would be useful to add to the list of requested information:
1.a. If the problem is related to playback, indicate specifically what players you've tried it on.

[jdobbs]

Good idea. Maybe I should add "was it a Sony?"

[lamster]

I initially ran into this with 0.81, after doing a successful rebuild, renaming the output directory, and trying to repeat the same one-step rebuild (with no directory where the output directory was pointing). Just repeated it with 0.82 in 3-step mode, by renaming the output directory, restarting Rebuilder, and clicking Rebuild.

1. Get warning dialog saying "All contents of the working VIDEO_TS folder will be erased. Continue?" If I say Yes, it gives a run-time error '76': Path not found.

[I don't think you need any of the other stuff; it's quite repeatable, and it doesn't matter which encoder was used.]

Note: This is clearly my error, since I neglected to recreate the output directory after renaming it. Nevertheless, the first warning dialog is bogus (and confusing). It would be better if it told me that the output directory didn't exist. (Better still if it asked if I wanted to have it created.)

You might also want to consider checking this at the start when in one-click mode, so I don't come back umpteen hours later thinking it will be all ready, only to find out that it still has to go through the rebuild phase.

Thanks.

[brashquido]

Originally posted by jdobbs
@brashquido

Thanks. I'll see what I can find in the ILVU reassembly code.

Just to be positive: is the section that is having problems definitely ILUV?

I wouldn't know a ILVU section if I fell over one :) . I just don't have the skills to know what I'm looking for. Maybe someone could point me to a guide on what to look for so I can edumicate myself? I used the rebuilder.log file to determine this, as VTS 4 is the only VTS in the log marked as having Interleaving/Multiangle, and it is the only one I've found when using PowerDVD to have this stuttering issue.

I don't know if this is relevant or not, but this stuttering occurs regardless of whether I'm playing in movie mode, or if I play the VOB file directly. To my layman understanding the IFO's are like a roadmap for the DVD players to play the VOB files, so if I bypass the IFO files by playing the VOB directly and the stuttering is still present, you would think that the problem lies in the VOB file itself. I did have a look at the rebuilt VTS 4 in vobedit, but I have no idea what I'm looking for.

Originally posted by Rockas
By the way... is that a good film?

if it isn't ... I'll go out there searching for you

It's an average kind of flick. There is just something about Harrison Fords thick American accent I find kind of ironic when he is playing the captain of a Soviet nuclear sub :).

[lamster]

Originally posted by brashquido
I wouldn't know a ILVU section if I fell over one :) . I just don't have the skills to know what I'm looking for. Maybe someone could point me to a guide on what to look for so I can edumicate myself? I used the rebuilder.log file to determine this, as VTS 4 is the only VTS in the log marked as having Interleaving/Multiangle
If you're sure that's the one, open VTS_04_0.IFO with IfoEdit. In the bottom panel, look for "Angle" or "ILVU". E.g.,
... [V/C Id: 2/ 1] (Angle 1): time: 00:01:34.04 ...
... [V/C Id: 3/ 1] (Angle 2): time: 00:01:34.04 ...
If you're not sure, open VIDEO_TS.IFO with IfoEdit and in the bottom panel see which title(s) are listed as having multiple angles. That will also tell you which VTS it's in. E.g.,
Title 1: VTS_04_*, TTN_1 (Angles: 3) (Chapters: 51) (Start Sector 14781)
(Note: This only works for angles; for ILVU you have to check each VTS_nn_0.)
it is the only one I've found when using PowerDVD to have this stuttering issue.
Have you seen the stuttering with a hardware player, or just software players? Just PowerDVD?

P.S. @jdobbs - this is what I was thinking of when I suggested 1.a.; the Sony issue was secondary.

[brashquido]

Thanks for the tips lamster, I'll have a look and confirm when I get home tonight :) .

I've tried 3 or 4 different software players on two seperate machines, all of which have crashed in the exact same point in the movie where PowerDVD gets the stutters. I only have 3 interleaved/multiangle movies, and I have not been able to sucessfully back up any of them with DVD-RB from version .74 onward (althoughI have not tried the other two since DVD-RB .76).

The reason I have not bothered to burn this to a DVD to test on a hardware player is that in 50+ movies I've backed up with DVD-RB, not one of them has displayed this stuttering before. Indeed the ISO of the original of K:19 that I am working from does not display this stuttering in PowerDVD, and doesn't crash any of the other software players. I will give it a try if jdobbs thinks it is worth it though.

[lamster]

I've experienced a few where I saw stuttering with IfoEdit's DVD playback, but when burned to DVD and played in a hardware player, it played fine.

If you've got DVD+/-RW, I'd say definitely try it out. If you don't have any rewritables, I think it's probably worth burning, but you can decide for yourself if you want to go for it or not.

[jdobbs]

To my layman understanding the IFO's are like a roadmap for the DVD players to play the VOB files, so if I bypass the IFO files by playing the VOB directly and the stuttering is still present, you would think that the problem lies in the VOB file itself. An ILVU section won't play correctly if not played through a DVD player using the IFOs. The sectors are interleaved switching from one stream to another. Trying to play it back directly will always look terrible...

[brashquido]

Originally posted by jdobbs
An ILVU section won't play correctly if not played through a DVD player using the IFOs. The sectors are interleaved switching from one stream to another. Trying to play it back directly will always look terrible...

Of course, that just make sense when you think about it :rolleyes:.

[jdobbs]

The reason I have not bothered to burn this to a DVD to test on a hardware player is that in 50+ movies I've backed up with DVD-RB, not one of them has displayed this stuttering before. Indeed the ISO of the original of K:19 that I am working from does not display this stuttering in PowerDVD, and doesn't crash any of the other software players. I will give it a try if jdobbs thinks it is worth it though. I think its worth it.

[brashquido]

Ok, will do. I only have one set top DVD player to test on though.

[NtegrA]

Cosmetic Bug (from status window):

- "Movie, Menus and Slideshoe Extras" mode is enabled.

[brashquido]

I burnt K-19 to DVD-RW Jdobbs and played it on my Pioneer DV-355, but I still get the same stutteringas I do with PowerDVD. The stuttering is nowhere near as pronounced in the video, more like watching it in slow motion rather than the slideshow PowerDVD was giving :) . The audio stuttering was just as bad if not worse.

I did find something though. Thanks to my new found skill of actually being able to use IFOedit to locate the angles :roll:, I found that the problem section is not even ILVU. I found that only cells 2, 3, 5, 6, 8, 9, 24, 25, 27 and 28 are ILVU. The cell giving me all the problems is cell 11. Here is a screen shot of IFOedit with VTS_04_0.IFO opened;

http://download.it-hq.org/images/k-19.gif

Hope this helps, let me know if I should do anything else.

[brashquido]

Originally posted by jdobbs
1. Description of the bug. What happened and how. Describe the exact wording of the error messages.

PREPARE phase goes through no problems, but I get this CCE error no more than 5 seconds after starting the ENCODE phase.

http://download.it-hq.org/images/the-cell-1.gif

Originally posted by jdobbs
1.a. If the problem is related to playback, indicate specifically what player(s) you've tried it on.

Don't get that far.

Originally posted by jdobbs
2. When it happened exactly. Was it in PREPARE, ENCODE, or REBUILD? At what point in that phase? How much had completed? Identify the segment that was processing at the point of error.

Very start of the ENCODE phase. The error is produced while DVD-RB says it is creating the M2V for VTS_01 segment 0.

Originally posted by jdobbs
3. What DVD were you processing? Is it commercial or homemade? Identify whether it is PAL or NTSC, and the Region.

Movie is an ISO rip of a commercial version of The Cell, and is PAL region 4.

Originally posted by jdobbs
[B]4. Create a zip file containing the info below and send it to DVD-RB@COMCAST.NET -- identify your DOOM9 name and the error to which it relates in the e-mail:
4.a. The LOG file from the job.
4.b. The REBUILDER.INF file from the \D2VAVS directory.
4.c. The REBUILDER.INI file from the DVD-RB directory.
4.d. If possible include a text listing of the \D2VAVS directory and the VIDEO_TS directory at the time of failure.
4.e. REBUILDER.ECL file, if it exists
4.f. If it stops at a particular segment. Include the AVS.
5. Identify the encoder selected and it's version. If possible click on the "Display Versions" menu option before your job starts so it will be in the LOG file (4.a).
6. The filesize of the DGDECODE version you are using. That's the only sure way to know the version.
7. Do not post if you are not using DVD-RB v0.77 or above.


On it's way. Should also mention this is a detected as Interleaving / Multiangle by DVD-RB. I have a feeling this is a seamless branching movie. I opened up the IFO for VTS_01_0 which is where encoding crashed, and PGC 1 uses both VOB ID 1 & 2. This means it is seamless branching does it not? If so I guess this isn't a bug then.

I also have problems with a movie called Indentity (PAL region 4), and it also has PGC's with multiple VOB ID's in VTS 2. However I am going to wait to see if I am right about seamless branching before bothering with a bug report.

[Rippraff]

@jdobbs

This is not really a bug but maybe it helps to decrease the number of people reporting problems with undersized results.
I found out, that RB counts every file inside the Source Path. If it isn't to much work, could you change this please, that only valid files (*.vob *.ifo *.bup) will be counted.
Background: I confess I pre-process my sources! :) I can't think of one single DVD, where nothing should be blanked. There are always trailers or other extras which I do not want to have on my backups.
I know this is driving you nuts when people tell you in their 15th post of their problem description about pre-processing. ;)
I'm using DVD-Rebuilder nearly from the beginning on, a long time before you've implemented Video Segment Editor and to be quiet frank I don't need this tool because I can't blank still-frames for example.
Back to topic ;) I work with the freeware tools TitleSet Blanker (http://shh.sysh.de/titlesetblanker.html) in easy cases and with Vobblanker (http://www.videohelp.com/~jsoto/vobblanker.htm) if it's more complicated. The advantage of TitleSet Blanker is you can blank VTS within seconds, it's easy to use, backups of the original files will be created and you can check your blanked dvd immediately with a software player. If it doesn't work you can restore your original files also within seconds.
The disadvantage, DVD-RB counts the backup files (which are simply renamed by putting a tilde at the the end f. e. VIDEO_TS.VOB~) as well as the new blanked files. The result is a wrong Reduction Level for DVD-5 and an undersized result. :(
Maybe other blanker work in the same way or people rename their original files into *.backup or something else.
Counting only valid files would avoid this and maybe you will have a few less people reporting such problems. ;)

Cu Rippraff