VCDXBuild crashing

[idbirch2]

Hi,

Anybody else have problems with VCDXbuild crashing. My HDD light remains locked and the whole PC crashes. I can use the crash recovery and carry on and it works OK.
Doesn't seem to matter what film it is. Encoding the same film twice - first time might crash while building images, a 2nd attempt will go thru fine.
Is this version just increcibly unstable or is it my system

P4 2GHz NWood
512MB DDR
80GB HDD
Abit BD7 mobo
WinXP Corp SP1

[chainsaw135]

I myself have never had a problem with vcdxbuild crashing while using dvd2svcd, i did a search around the forum and didnt find anything that might help you either. You could check your hardware make sure its running properly i think there are a few torture tests on the net you could google for. Also you could do the images by hand after the dvd2svcd process see if you still have those problems as a test other then that i dont have any more ideas, maybe someone else will.

[markrb]

I have never had an issue with VCDXBuild. If I had some sort of computer problem it would crash long before that.

The only thing that I can think of is that VCDXBuild is very Hard Disk intensive and the most out of all the programs that run in DVD2SVCD. It could be an I/O issue or a hard drive issue.
Are you running a RAID? Are you sure there is enough free space on the partition?

Also do you have any hard disk utilities running like Norton and the like? If so before you encode shut them off. It could be causing an issue.

Just some random thoughts,
Mark

[idbirch2]

Thanks for the pointers :-)
Don't have much running in the backgroung (only eDonkey - is this a problem?) and if no-one else has a problem maybe its my HDD.
I always have enough free space as I rip to my D: drive which is 40GB in size and has about 30GB free
Its not RAID but its a Western Digital Caviar@7200RPM - are these crap? - I didn't think do till now as its really quiet and extremely quick in tests ie SiSoftSandra.

It never has problems with HDD intensive tasks like Defragging or hashing ED2K files - but is VCDXBuild more intensive than these?

Thanks again guys!

[UltimateDBZ]

The Caviar line from Western Digital are a great line, I'd be surprised if this was the cause of the problem. Unless, of course, the drive is just plain dying from age...

[winxi]

Hello!
If you have a non-standard sign in the output-folder of vcdxbuild (for example a "ö"), vcdxbuild will fail.

winxi

[markrb]

Why don't you post your log file using cut and paste so we can make sure nothing is out of the ordinary.

WD drives are just dandy. I put them near the top. Near the bottom would be Fuji or Samsung drives. Tons of failures on these guys when I was a reseller.

Mark

[idbirch2]

Sure, next time it does it I'll post the log file.
I really hope its not the HDD - its only about 6 months old - I run full checkdisks and defrags all the time to keep things running sweet.

I don't have problems with any other programs though - the rig i have is the most stable i have ever seen - its excellent - which is why I can't understand why no-one else has the same problem.

Oh yeah, I'm not using special characters - i saw that one when I searched the forum before I posted - although I thought that was related to BBMPEG.

Anyways, apart from this problem DVD2SVCD is the best damn program out there! Thanks again for the replies
:)

[chainsaw135]

before you do your next movie, maybe try to uninstall and reinstall dvd2svcd again.

[DarkFear_DK]

I have the exact same problem. My computer also just randomly stalls (completely) while running vcdxbuild. And it's just like you idbirch2 - its not movie related as it does this everytime I'm converting a movie. I've never had these problem until I updated my DVD2SVCD prog to 1.2.1 b2a.

So to be able to create my imagefiles, I just have to retry until it finally goes all the way through with it. This can be the 2nd time or the 8th time (the most I've been punished with) :P - but never the first time (wierd).

[sandchar99]

Ditto:

I have had problems before with VCDXbuild randomly crashing the PC with this DVD2SVCD build AND previous versions. Although I am not sure, I noticed it beginning with versions 1.10. I have been always able to do crash recovery and complete the VCDXBuild process.

I do notice that some of the dlls (cygwin1.dll and cygz.dll) have changed in size from older versions. I do not think that this is the problem.

I might suspect the hard drive. I was previously using to WD 40 GB drives with the system and program on one drive [C:] and the output on the other [D:]. When I changed the output drive [D:] to a 160 GB Seagate with 8 MB cache the problem went away.

Who knows?

[DarkFear_DK]

It's actually quite funny... My harddrive is also a Western Digital harddrive. I've got the 120GB special edition w/8 MB cache.
It almost seems that there is a conflict with VCDXBuild and these WD harddrives. (that would be the firmware of the harddrives)

My first thought was "Oh no... Plz don't let it be bad blocks...", so I tried to run a surface scan of my harddrive using the software provided by WD - no errors found.

I hold my money on the conflict in VCDXBuild and the firmware of WD harddrives.

What do you guys think?

[Stapler]

I have a WD 40gb 8mb drive, and have the same problem...pain in the @$$.

dvd2svcd_log.txt:

...everything good so far...
Executing RunbbMPEG. Commandline:
"C:\Program Files\DVD2SVCD\bbMPEG\RunbbMPEG.exe" "C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File.mpg"
Multiplexing and cutting finished.

--------------------------------------------------------
- 11/20/2003 2:00:34 PM
- Free on drive C: 16162.69 mb
- Determining length of audio
--------------------------------------------------------
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
2980.049 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
3052.878 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
Analyzing finished.

--------------------------------------------------------
- 11/20/2003 2:01:27 PM
- Free on drive C: 16162.69 mb
- Creating CD-Images using VCDXBuild
--------------------------------------------------------
- No. of chapters to create: 49

CD image #1: CD_Image_File_CD1.bin

Executing VCDXBuild. Commandline:
"C:\Program Files\DVD2SVCD\VCDImager\VCDXBuild.exe" --verbose --cue-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.cue" --bin-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.bin" "C:\PROGRA~1\DVD2SVCD\Movie\VCDXBU~1.XML"
--------------------------------------------------------
- 11/20/2003 5:31:58 PM
- DVD to SVCD Conversion
- DVD2SVCD ver. 1.2.1 build 3
--------------------------------------------------------
Initializing
-
Initializing finished.

--------------------------------------------------------
- 11/20/2003 5:32:00 PM
- Free on drive C: 15984.50 mb
- Crash Recovery
- Restarting from: SVCD Authoring
--------------------------------------------------------
- 11/20/2003 5:32:01 PM
- Free on drive C: 15984.50 mb
- Determining length of audio
--------------------------------------------------------
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
2980.049 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
3052.878 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
Analyzing finished.

--------------------------------------------------------
- 11/20/2003 5:33:31 PM
- Free on drive C: 15984.47 mb
- Creating CD-Images using VCDXBuild
--------------------------------------------------------
- No. of chapters to create: 49

CD image #1: CD_Image_File_CD1.bin

Executing VCDXBuild. Commandline:
"C:\Program Files\DVD2SVCD\VCDImager\VCDXBuild.exe" --verbose --cue-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.cue" --bin-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.bin" "C:\PROGRA~1\DVD2SVCD\Movie\VCDXBU~1.XML"
--------------------------------------------------------
- 11/20/2003 5:53:10 PM
- DVD to SVCD Conversion
- DVD2SVCD ver. 1.2.1 build 3
--------------------------------------------------------
Initializing
-
Initializing finished.

--------------------------------------------------------
- 11/20/2003 5:53:12 PM
- Free on drive C: 15786.24 mb
- Crash Recovery
- Restarting from: SVCD Authoring
--------------------------------------------------------
- 11/20/2003 5:53:13 PM
- Free on drive C: 15786.23 mb
- Determining length of audio
--------------------------------------------------------
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
2980.049 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File00.mpg
Analyzing: C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
3052.878 seconds C:\Program Files\DVD2SVCD\Movie\bbMPEG_Muxed_File01.mpg
Analyzing finished.

--------------------------------------------------------
- 11/20/2003 5:54:17 PM
- Free on drive C: 15786.20 mb
- Creating CD-Images using VCDXBuild
--------------------------------------------------------
- No. of chapters to create: 49

CD image #1: CD_Image_File_CD1.bin

Executing VCDXBuild. Commandline:
"C:\Program Files\DVD2SVCD\VCDImager\VCDXBuild.exe" --verbose --cue-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.cue" --bin-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD1.bin" "C:\PROGRA~1\DVD2SVCD\Movie\VCDXBU~1.XML"
--------------------------------------------------------
- 11/20/2003 5:57:10 PM
- Free on drive C: 15355.85 mb
- Creating CD-Images using VCDXBuild
--------------------------------------------------------
- No. of chapters to create: 50

CD image #2: CD_Image_File_CD2.bin

Executing VCDXBuild. Commandline:
"C:\Program Files\DVD2SVCD\VCDImager\VCDXBuild.exe" --verbose --cue-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD2.cue" --bin-file="C:\PROGRA~1\DVD2SVCD\Movie\CD_Image_File_CD2.bin" "C:\PROGRA~1\DVD2SVCD\Movie\VCDXBU~2.XML"






VCXBuilder_log.txt:

--DEBUG: EEL sysid=[C:\PROGRA~1\DVD2SVCD\Movie\VCDXBU~1.XML] pubid=[(null)]
--DEBUG: EEL sysid=[http://www.gnu.org/software/vcdimager/videocd.dtd] pubid=[-//GNU//DTD VideoCD//EN]
++ WARN: initializing libvcd 0.7.12 [cygwin/i686]
++ WARN:
++ WARN: this is the UNSTABLE development branch!
++ WARN: use only if you know what you are doing
++ WARN: see http://www.hvrlab.org/~hvr/vcdimager/ for more information
++ WARN:
--DEBUG: changed volume number to 1
--DEBUG: changed volume count to 2
--DEBUG: changed restriction number to 0
--DEBUG: changing 'next volume use sequence 2' to 0
--DEBUG: changing 'next volume use lid 2' to 0
--DEBUG: changing 'relaxed aps' to 0
--DEBUG: changing 'update scan offsets' to 0
--DEBUG: adding pbc (chapter-00/2)
--DEBUG: adding pbc (chapter-01/2)
--DEBUG: adding pbc (chapter-02/2)
--DEBUG: adding pbc (chapter-03/2)
--DEBUG: adding pbc (chapter-04/2)
--DEBUG: adding pbc (chapter-05/2)
--DEBUG: adding pbc (chapter-06/2)
--DEBUG: adding pbc (chapter-07/2)
--DEBUG: adding pbc (chapter-08/2)
--DEBUG: adding pbc (chapter-09/2)
--DEBUG: adding pbc (chapter-10/2)
--DEBUG: adding pbc (chapter-11/2)
--DEBUG: adding pbc (chapter-12/2)
--DEBUG: adding pbc (chapter-13/2)
--DEBUG: adding pbc (chapter-14/2)
--DEBUG: adding pbc (chapter-15/2)
--DEBUG: adding pbc (chapter-16/2)
--DEBUG: adding pbc (chapter-17/2)
--DEBUG: adding pbc (chapter-18/2)
--DEBUG: adding pbc (chapter-19/2)
--DEBUG: adding pbc (chapter-20/2)
--DEBUG: adding pbc (chapter-21/2)
--DEBUG: adding pbc (chapter-22/2)
--DEBUG: adding pbc (chapter-23/2)
--DEBUG: adding pbc (chapter-24/2)
--DEBUG: adding pbc (chapter-25/2)
--DEBUG: adding pbc (chapter-26/2)
--DEBUG: adding pbc (chapter-27/2)
--DEBUG: adding pbc (chapter-28/2)
--DEBUG: adding pbc (chapter-29/2)
--DEBUG: adding pbc (chapter-30/2)
--DEBUG: adding pbc (chapter-31/2)
--DEBUG: adding pbc (chapter-32/2)
--DEBUG: adding pbc (chapter-33/2)
--DEBUG: adding pbc (chapter-34/2)
--DEBUG: adding pbc (chapter-35/2)
--DEBUG: adding pbc (chapter-36/2)
--DEBUG: adding pbc (chapter-37/2)
--DEBUG: adding pbc (chapter-38/2)
--DEBUG: adding pbc (chapter-39/2)
--DEBUG: adding pbc (chapter-40/2)
--DEBUG: adding pbc (chapter-41/2)
--DEBUG: adding pbc (chapter-42/2)
--DEBUG: adding pbc (chapter-43/2)
--DEBUG: adding pbc (chapter-44/2)
--DEBUG: adding pbc (chapter-45/2)
--DEBUG: adding pbc (chapter-46/2)
--DEBUG: adding pbc (chapter-47/2)
--DEBUG: adding pbc (chapter-48/2)
--DEBUG: adding pbc (chapter-49/2)
--DEBUG: adding pbc (ChangeCD/2)
--DEBUG: adding pbc (end/3)
--DEBUG: adding segment #0, C:\PROGRA~1\DVD2SVCD\Movie\TITLEP~1.MPG
--DEBUG: strange (possibly non-compliant) user_data seen...
--DEBUG: pts start offset 0.213367 (max pts = 0.246733)
--DEBUG: playing time 0.033367
INFO: scanning mpeg segment item #0 for scanpoints...
--DEBUG: already scanned... not rescanning
--DEBUG: SPI length is 8 sector(s), allocated 1 segment(s)
--DEBUG: adding segment #1, C:\PROGRA~1\DVD2SVCD\Movie\CHANGE~1.MPG
--DEBUG: strange (possibly non-compliant) user_data seen...
--DEBUG: pts start offset 0.213367 (max pts = 0.246733)
--DEBUG: playing time 0.033367
INFO: scanning mpeg segment item #1 for scanpoints...
--DEBUG: already scanned... not rescanning
--DEBUG: SPI length is 6 sector(s), allocated 1 segment(s)
--DEBUG: sequence count 1
--DEBUG: adding sequence #0, C:\PROGRA~1\DVD2SVCD\Movie\BBMPEG~1.MPG
--DEBUG: pts start offset 0.213367 (max pts = 2980.240411)
--DEBUG: playing time 2980.027044
INFO: scanning mpeg sequence item #0 for scanpoints...
--DEBUG: already scanned... not rescanning
--DEBUG: pbc: psd size 17400 (extended psd 0)
--DEBUG: iso9660: highest alloced sector is 586 (using 587 as isosize)
--DEBUG: requested entry point (id=entry-chapt-02) at 60.000000, closest possible entry point at 60.276878
--DEBUG: requested entry point (id=entry-chapt-03) at 120.000000, closest possible entry point at 119.669544
--DEBUG: requested entry point (id=entry-chapt-04) at 180.000000, closest possible entry point at 180.013167
--DEBUG: requested entry point (id=entry-chapt-05) at 240.000000, closest possible entry point at 239.739500
--DEBUG: requested entry point (id=entry-chapt-06) at 300.000000, closest possible entry point at 299.799500
--DEBUG: requested entry point (id=entry-chapt-07) at 360.000000, closest possible entry point at 360.026333
--DEBUG: requested entry point (id=entry-chapt-08) at 420.000000, closest possible entry point at 420.219800
--DEBUG: requested entry point (id=entry-chapt-09) at 480.000000, closest possible entry point at 479.645833
--DEBUG: requested entry point (id=entry-chapt-10) at 540.000000, closest possible entry point at 540.339800
--DEBUG: requested entry point (id=entry-chapt-11) at 600.000000, closest possible entry point at 599.599000
--DEBUG: requested entry point (id=entry-chapt-12) at 660.000000, closest possible entry point at 659.909244
--DEBUG: requested entry point (id=entry-chapt-13) at 720.000000, closest possible entry point at 719.635578
--DEBUG: requested entry point (id=entry-chapt-14) at 780.000000, closest possible entry point at 780.029244
--DEBUG: requested entry point (id=entry-chapt-15) at 840.000000, closest possible entry point at 839.755578
--DEBUG: requested entry point (id=entry-chapt-16) at 900.000000, closest possible entry point at 900.399500
--DEBUG: requested entry point (id=entry-chapt-17) at 960.000000, closest possible entry point at 959.591967
--DEBUG: requested entry point (id=entry-chapt-18) at 1020.000000, closest possible entry point at 1020.102411
--DEBUG: requested entry point (id=entry-chapt-19) at 1080.000000, closest possible entry point at 1079.745333
--DEBUG: requested entry point (id=entry-chapt-20) at 1140.000000, closest possible entry point at 1140.272467
--DEBUG: requested entry point (id=entry-chapt-21) at 1200.000000, closest possible entry point at 1200.082211
--DEBUG: requested entry point (id=entry-chapt-22) at 1260.000000, closest possible entry point at 1260.008744
--DEBUG: requested entry point (id=entry-chapt-23) at 1320.000000, closest possible entry point at 1320.402411
--DEBUG: requested entry point (id=entry-chapt-24) at 1380.000000, closest possible entry point at 1379.795078
--DEBUG: requested entry point (id=entry-chapt-25) at 1440.000000, closest possible entry point at 1439.988544
--DEBUG: requested entry point (id=entry-chapt-26) at 1500.000000, closest possible entry point at 1499.881711
--DEBUG: requested entry point (id=entry-chapt-27) at 1560.000000, closest possible entry point at 1559.891667
--DEBUG: requested entry point (id=entry-chapt-28) at 1620.000000, closest possible entry point at 1619.868244
--DEBUG: requested entry point (id=entry-chapt-29) at 1680.000000, closest possible entry point at 1680.345333
--DEBUG: requested entry point (id=entry-chapt-30) at 1740.000000, closest possible entry point at 1739.788044
--DEBUG: requested entry point (id=entry-chapt-31) at 1800.000000, closest possible entry point at 1800.265133
--DEBUG: requested entry point (id=entry-chapt-32) at 1860.000000, closest possible entry point at 1859.941411
--DEBUG: requested entry point (id=entry-chapt-33) at 1920.000000, closest possible entry point at 1919.751167
--DEBUG: requested entry point (id=entry-chapt-34) at 1980.000000, closest possible entry point at 1980.061411
--DEBUG: requested entry point (id=entry-chapt-35) at 2040.000000, closest possible entry point at 2040.004633
--DEBUG: requested entry point (id=entry-chapt-36) at 2100.000000, closest possible entry point at 2099.931167
--DEBUG: requested entry point (id=entry-chapt-37) at 2160.000000, closest possible entry point at 2160.324833
--DEBUG: requested entry point (id=entry-chapt-38) at 2220.000000, closest possible entry point at 2219.934378
--DEBUG: requested entry point (id=entry-chapt-39) at 2280.000000, closest possible entry point at 2280.194578
--DEBUG: requested entry point (id=entry-chapt-40) at 2340.000000, closest possible entry point at 2339.754078
--DEBUG: requested entry point (id=entry-chapt-41) at 2400.000000, closest possible entry point at 2400.398000
--DEBUG: requested entry point (id=entry-chapt-42) at 2460.000000, closest possible entry point at 2460.124333
--DEBUG: requested entry point (id=entry-chapt-43) at 2520.000000, closest possible entry point at 2520.351167
--DEBUG: requested entry point (id=entry-chapt-44) at 2580.000000, closest possible entry point at 2579.827244
--DEBUG: requested entry point (id=entry-chapt-45) at 2640.000000, closest possible entry point at 2639.970667
--DEBUG: requested entry point (id=entry-chapt-46) at 2700.000000, closest possible entry point at 2699.947244
--DEBUG: requested entry point (id=entry-chapt-47) at 2760.000000, closest possible entry point at 2760.340911
--DEBUG: requested entry point (id=entry-chapt-48) at 2820.000000, closest possible entry point at 2819.783633
--DEBUG: requested entry point (id=entry-chapt-49) at 2880.000000, closest possible entry point at 2880.260711
++ WARN: generated image (359492 sectors [79:53.17]) may not fit on 74min CDRs (333000 sectors)
--DEBUG: OGT streams available: 0 0 0 0
--DEBUG: OGT streams available: 0 0 0 0
--DEBUG: OGT streams available: 0 0 0 0
INFO: writing track 1 (ISO9660)...
--DEBUG: setting EOR for SeqEnd at packet# 6 ('segment-titlepicture')
--DEBUG: setting EOR for SeqEnd at packet# 4 ('segment-changecd')
INFO: writing file `EXTRA/DVD2SVCD.XML' (104503 bytes)
INFO: writing file `EXTRA/SVCDINFO.TXT' (1949 bytes)
INFO: writing track 2, MPEG2, NTSC 2/3 D-1 (480x480/30fps), audio[0]: l2/44.1kHz/192kbps/stereo ...
--DEBUG: MPEG packet statistics: 327412 video, 31192 audio, 0 zero, 0 ogt, 1 unknown
--DEBUG: writting post-gap ('leadout pregap')...
INFO: finished ok, image created with 359492 sectors [79:53.17]

[DarkFear_DK]

I've finally come up with a "half-solution" for this problem.

All you have to do is: When VXCDXBuild is running you have to load your CPU so much that eventually VCDXBuild will slow down (but not stop).

This is, of course, only a half-solution and it will slow the process down. But at least your computer won't crash (my computer hasn't crashed since I've been doing this ackward trick)

The way I do it is, that once VCDXBuild starts I manually lauch up for a little program called Toast (It's a CPU loader program - the best one in my mind) and manually set the priority of the program to High - Remember to KEEP Toast as the highlighted program.

Thats it...
I hope this helps just a little bit until we find a better way...

-- DarkFear_DK

[MarkP]

Hi

I noticed from the VCXBuilder log posted by Stapler that each CD created has 50 chapters, is there a reason for this? seems a bit excessive to me that will be close on to a chapter every minute or so of play time.

Promark
:)

[DarkFear_DK]

If you look in DVD2SVCD under "CD Image" on the bottom right, then you'll see that you have two choices regarding chapters - one of them equals the same amount of chapters as there is on the original DVD, the other one does chapters manually (default is one chapter per minute)... There ya' go :)

[MarkP]

Thanks for that but I was aware of that, and fot your info my default is 600 seconds but my point was the default can be changed and a Chapter a minute seems excessive, and was wondering if there was a reason for it that I wasn't aware of. :D