Log in

View Full Version : bbMPEG cannot write to output file problem

vpwsys
2nd January 2003, 21:41
Hi,

I've been trying out DVD2SVCD with a couple of DVD's but am getting a problem when cutting/muxing stage arrives -- bbMPEG is failing with a "cannot write output file" each time.

That's pretty much all I get - it just pops up, and once I hit OK, thats it, it just stops.

It seems to happen around 30-40% of multiplexing each time.

My Hardware:

- Win2000, Athlon XP 1800, 512MB, 100GB WD HardDisc
- DVD is a PAL Reg 2, 4:3 format and plays without issue

The dvd2svcd log:

--
WNASPI32.DLL 4.71.1.0
--------------------------------------------------------
- 02/01/2003 09:17:59
- DVD to SVCD Conversion
- DVD2SVCD ver. 1.1.0 build 1
--------------------------------------------------------
Initializing
Initializing finished.

--------------------------------------------------------
- 02/01/2003 09:18:03
- Free on drive T: 57064.37 mb
- Internal rip
--------------------------------------------------------
Preparing vobfiles to be ripped:
- D:\VIDEO_TS\VTS_03_1.vob
- D:\VIDEO_TS\VTS_03_2.vob
- D:\VIDEO_TS\VTS_03_3.vob
- D:\VIDEO_TS\VTS_03_4.vob

Ripping: D:\VIDEO_TS\VTS_03_1.vob
Ripping: D:\VIDEO_TS\VTS_03_2.vob
Ripping: D:\VIDEO_TS\VTS_03_3.vob
Ripping: D:\VIDEO_TS\VTS_03_4.vob
Ripping finished. Speed: 5360

--------------------------------------------------------
- 02/01/2003 09:29:01
- DVD2AVI
--------------------------------------------------------
Creating DVD2AVI INI file:
- C:\Program Files\DVD2SVCD\DVD2AVI\DVD2AVI.INI

Variable settings:
iDCT_Algorithm: 32-bit SSE MMX

Executing DVD2AVI.
Executing DVD2AVI. Commandline:
"C:\Program Files\DVD2SVCD\DVD2AVI\DVD2AVI.exe" -CS=2 -YR=1 -EXIT -OF=[T:\DVD2AVI_Project_file] -IF=[T:\VTS_03_1.vob,T:\VTS_03_2.vob,T:\VTS_03_3.vob,T:\VTS_03_4.vob]
Framerate: 25000
DVD2AVI processing done.

--------------------------------------------------------
- 02/01/2003 09:30:43
- Free on drive T: 53624.55 mb
- AUDIO Extraction
--------------------------------------------------------
Found AC3 stream id: 0x80
Filename: T:\Extracted_audio_1.ac3
Audio1 delay: -80 ms
Audio extraction finished.

--------------------------------------------------------
- 02/01/2003 09:32:57
- Free on drive T: 53497.82 mb
- AUDIO conversion
--------------------------------------------------------

Encoding Audio. Filename: T:\Extracted_audio_1.ac3
Executing BeSweet. Commandline:
"C:\Program Files\DVD2SVCD\BeSweet\BeSweet.exe" -core( -input "T:\Extracted_audio_1.ac3" -output "T:\Encoded_audio_1.mp2" -logfile "T:\Encoded_audio_1.log" ) -azid( -L -3db -c normal -s surround -g max ) -ota( -d -80 ) -shibatch( --rate 44100 ) -2lame( -e -b 192 -m s )
Audio conversion of T:\Extracted_audio_1.ac3 finished.

Audio conversion finished.

--------------------------------------------------------
- 02/01/2003 09:49:36
- Free on drive T: 53371.08 mb
- Converting Pictures
--------------------------------------------------------
Converting: C:\Program Files\DVD2SVCD\DefaultTitlepicture.bmp
Converting: C:\Program Files\DVD2SVCD\DefaultChangeCD.bmp
Finished converting pictures
--------------------------------------------------------
- 02/01/2003 09:49:44
- Free on drive T: 53370.12 mb
- Video Encoding using TMPGEnc
--------------------------------------------------------
- Encoding T:\TitlePicture.bmp.avs
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding T:\ChangeCDPicture.bmp.avs
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1263353814 (1233744kb) Using CQ Value: 80.00
Calculated next CQ Value: 83.90
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1387719257 (1355195kb) Using CQ Value: 83.90
Calculated next CQ Value: 83.43
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1380363308 (1348011kb) Using CQ Value: 83.43
Calculated next CQ Value: 83.23
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1377025863 (1344752kb) Using CQ Value: 83.23
Calculated next CQ Value: 83.15
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1375628081 (1343387kb) Using CQ Value: 83.15
Calculated next CQ Value: 83.13
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1375221276 (1342990kb) Using CQ Value: 83.13
Calculated next CQ Value: 83.12
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1374992836 (1342766kb) Using CQ Value: 83.12
Calculated next CQ Value: 83.12
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1375006407 (1342780kb) Using CQ Value: 83.12
Calculated next CQ Value: 83.11
Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

- Encoding Test Clip T:\AviSynth_Script_file_CQ_TEST.avs
Wanted: 1374937102 (1342712kb) Predicted: 1374884428 (1342661kb) Using CQ Value: 83.11
Final CQ Value: 83.11
- Encoding T:\AviSynth_Script_file.avs
StreamSectors: 1539589576
AudioSectors: 134850100
VideoPAPO: 21760164
ScanOffsetBytes: 124578
SeqAligningBytes: 7917624
DVDBytes: 0
VideoEndHeader: 8
SubtitleSectors: 0
EmptySectors: 238.00
PictureSectors: 600.00
PureMPEGStream: 1374937102.00
Seconds: 5543.80
CalcMPEGStream: 1374937102.00
Frames: 138420
CDSize: 740.00
Number of CDs: 2
Cut point 735.00
Using CQ Value: 83.03
Aspect Ratio: 4:3 (No borders, encoded as 4:3)

---AVS Begin---
LoadPlugin("C:\PROGRA~1\DVD2SVCD\MPEG2Dec\mpeg2dec.dll")
mpeg2source("T:\DVD2AV~1.D2V")
BicubicResize(480,576,0.0,0.6)
AddBorders(0,0,0,0)
----AVS End----

Executing TMPGEnc. Commandline:
"C:\PROGRA~1\EAZYVC~1\TMPGEnc\TMPGEnc.exe" "T:\TMPGEnc_Project_file.tpr" /Encode /Close
Video Encoding finished.

--------------------------------------------------------
- 02/01/2003 18:34:48
- Free on drive T: 53370.07 mb
- Converting Pictures from ES to PS
--------------------------------------------------------
Saving bbMPEG settings: C:\Program Files\DVD2SVCD\bbMPEG\default.ini

Executing RunbbMPEG. Commandline:
"C:\Program Files\DVD2SVCD\bbMPEG\RunbbMPEG.exe" "T:\TitlePicture.bmp.mpg"
--------------------------------------------------------
- 02/01/2003 18:34:53
- Free on drive T: 53370.04 mb
- Converting Pictures from ES to PS
--------------------------------------------------------
Saving bbMPEG settings: C:\Program Files\DVD2SVCD\bbMPEG\default.ini

Executing RunbbMPEG. Commandline:
"C:\Program Files\DVD2SVCD\bbMPEG\RunbbMPEG.exe" "T:\ChangeCDPicture.bmp.mpg"
--------------------------------------------------------
- 02/01/2003 18:34:56
- Free on drive T: 53370.01 mb
- Converting Pictures from ES to PS
--------------------------------------------------------
Saving bbMPEG settings: C:\Program Files\DVD2SVCD\bbMPEG\default.ini
--------------------------------------------------------
- 02/01/2003 18:34:58
- Free on drive T: 53370.01 mb
- Multiplexing and cutting
--------------------------------------------------------
Saving bbMPEG settings: C:\Program Files\DVD2SVCD\bbMPEG\default.ini
Offset in Seconds: 2
Executing bbMPEG.
Variable Settings:
Movie offset: 2 seconds
Cut point: 735 mb

Executing RunbbMPEG. Commandline:
"C:\Program Files\DVD2SVCD\bbMPEG\RunbbMPEG.exe" "T:\bbMPEG_Muxed_File.mpg"
Length of T:\bbMPEG_Muxed_File00.mpg
--

I've had a quickish scour on the site but couldn't spot anything here about this problem - please point me in the right direction if i missed it though.

All help appreciated.

Vince
BizUser
4th January 2003, 09:56
The only thing that comes to mind is that your files are on drive 'T:' - which suggests a network, or otherwise non-local, and/or non-IDE/SCSI drive. Since the error relates to writing to file, and it's intermittent, then I'd suspect some kind of drive access issue.

However, all the other stages in the process aren't encountering this error, so why just the bbMPEG step? No idea... The only thing I can think of is that the muxing stage is the only stage where fast, constant access to multiple files is required (two inputs, one output). So there's a very small chance that only bbMPEG is stressing the disk drive subsystem to the point where errors are occurring.

Can you try running this on your 'C:' drive, or another local drive? Just as a test?

I have a question for you, unrelated to your problem ... I notice that your log shows that you encountered the situation where DVD2SVCD keeps re-running TMPGEnc, trying to determine the best CQ value. Is this normal? It seems like it takes forever to arrive at some value. I gave up before letting it complete, and switched to VBR. Curious to know if you always get this behavior.

Come to think of it, could your 'T:' drive be somehow overheating? That almost-endless search for a CQ value probably strains your drive. If it's a new drive, there are utilities to monitor it's temp.

Good Luck!

P.S. - I have a hardware background, and have built my own PCs for many years. Recently I've become obsessed with making my PC quiet, which requires reducing fan speed, etc, which in turn requires you to keep a real close eye on temperatures. My main PC is thus wired with temp sensors and I have utilities to monitor CPU, motherboard, and Hard Drive temps. I have never seen anything come close to this DVD/MPEG encoding stuff in terms of generating heat inside the PC - my CPU normally sits at around 34 C; when running dvd2svcd, it hits 60 C! My PSU temp rises, and my hard drive temp also. I've had to crank up fans to keep the box cool!
ux-3
4th January 2003, 10:12
I have seen this error too ... on the local HD. Once I recover, it goes smoothly.
vpwsys
4th January 2003, 12:54
Originally posted by BizUser
The only thing that comes to mind is that your files are on drive 'T:' - which suggests a network


Nope, T: is a Local Hard Disc.

However, all the other stages in the process aren't encountering this error, so why just the bbMPEG step? No idea... The only thing I can think of is that the muxing stage is the only stage where fast, constant access to multiple files is required (two inputs, one output). So there's a very small chance that only bbMPEG is stressing the disk drive subsystem to the point where errors are occurring.


Can you try running this on your 'C:' drive, or another local drive? Just as a test?


I will give it a go, bit of a long shot I reckon though & gonna have to free up some space first!


I have a question for you, unrelated to your problem ... I notice that your log shows that you encountered the situation where DVD2SVCD keeps re-running TMPGEnc, trying to determine the best CQ value. Is this normal?


*shrug* I have no idea, and right now I have no other logs to see! I tend to hit Go and leave the PC while I go to work :-)


Come to think of it, could your 'T:' drive be somehow overheating? That almost-endless search for a CQ value probably strains your drive. If it's a new drive, there are utilities to monitor it's temp.


Unlikely - the systems monitored like that, and it's pretty cool running as it goes - I've had lots of problems before with instability of systems because of heat and was determined this PC wouldn't be the same.

I'll give the C:\ drive a try... bit doubtful though :-(
vpwsys
4th January 2003, 12:55
Originally posted by ux-3
I have seen this error too ... on the local HD. Once I recover, it goes smoothly.

Unfortunately not for me - I've recovered several times, same result each time.
BizUser
4th January 2003, 19:24
So you have just one HD - 100 gig (I read your h/w specs, which I overlooked the first time - sorry). Yet you have a 'T' drive letter. So presumably, you partitioned that one HD into many logical partitions? I'm just puzzled by the letter 'T' although I realize you can assign any letter you like (my CD ROM drive is 'Z'). If your 'C' and 'T' are the same physical drive, then trying 'C' seems to be a waste. If, however, you have two physical drives, it's worth trying. And if you do have two physical drives, then how is the second one setup - slave on primary, or master on secondary? That could be an issue.

Other possibilities are - bad cabling to the HD. Bad drivers for HD susbsystem (Eg, wrong/buggy/out of date bus mastering drivers). Is this an off-the shelf, or home-built system? Who's motherboard/chipset? I had issues once with an Asus motherboard using VIA chipset. I had to download newer drivers from VIA's website to get bus mastering (DMA-related) to work properly.

Regarding cabling - newer, faster Hard Drives require 80-wire ribbon cables, while typical computers come with 40-wire cables. It was years before I realized this - I had my system all wired up with the 40-wire cables, then bought a new HD that came with an 80-wire cable, but I didn't spot the difference and continued to use the existing 40-wire cable as it was already in-place. The faster HDs transfer data at a faster rate, which causes interference on the ribbon cable; so the faster drives ship with an 80-wire cable; 40 data wires and 40 'ground' wires interspersed between the data lines to stop interference. Connectors at each end are the same - 40-pin - so they look the same and are physically interchangeable. The only difference is the visual 'pitch' of the wires in the cable.

I'm not totally surprized that this just happens with this one program. I have a wireless network at home (802.11) and it works great for browsing, and transferring small files. But if I try to transfer large files, I used to get errors. I had to apply all kinds of updates/patches, and also swapped a netgear NIC card for a linksys NIC card before I could get everything rock solid - the point being, there can be problems that only surface during large/heavy/sustained loads. Much of what is going on in the DVD2SVCD process requires 'thought' - lots of processing - so the data transfer rates may be slow. bbMPEG is just throwing two files together into one, so it may be running 'fast' (pure conjecture - maybe it's thinking hard too!).

Regarding that CQ stuff - There seems to be a bug in DVD2SVCD where it defaults to this CQ mode on first run. I think the docs say it should be VBR, and once I changed this, it's been that way forever. I don't think they expect you to run CQ (don't know enough about this yet to really say it's a bug - just an observation I had when I first ran dvd2svcd not long ago). It seems that dvd2svcd and tmpgenc get into this vicious circle of trying to find the optimal setting. Each run can take forever, and it never seems to converge (although I note that yours did eventually). The timestamp before this phase begins is circa 9am; the next timestamp is 6pm! So that's 9 hours of solid work. I suspect much of that was done encoding those test clips. It seems to encode a test clip, compare some actual setting with a desired setting; then re-run with new settings, and so on and so on ... Perhaps others can comment on this behavior of dvd2svcd (and I'll have a search of the formums too!).
vpwsys
5th January 2003, 11:19
Originally posted by BizUser
So you have just one HD - 100 gig (I read your h/w specs, which I overlooked the first time - sorry). Yet you have a 'T' drive letter. So presumably, you partitioned that one HD into many logical partitions? I'm just puzzled by the letter 'T' although I realize you can assign any letter you like (my CD ROM drive is 'Z').


Sorry Yes, it's a single 100GB Drive, 20GB C, remainder T:. The lettering is because I never use the first few letters (throwback from my Windows 9x moving CD-ROM letter days), and the fact the next few are network drives.


Other possibilities are - bad cabling to the HD.


Can rule that out for sure.


Is this an off-the shelf, or home-built system? Who's motherboard/chipset? I had issues once with an Asus motherboard using VIA chipset. I had to download newer drivers from VIA's website to get bus mastering (DMA-related) to work properly.


It's "home built" per se, but it was actually built by someone who is a professional in IT, (not a know it all, a proper Hardware specalist!). The boards an ASUS, non-VIA chipset (nothing in this world works with a VIA chipset from my experience!)


the point being, there can be problems that only surface during large/heavy/sustained loads. Much of what is going on in the DVD2SVCD process requires 'thought' - lots of processing - so the data transfer rates may be slow. bbMPEG is just throwing two files together into one, so it may be running 'fast' (pure conjecture - maybe it's thinking hard too!).


Again I doubt this purely because other applications (such as the Pinnacle Video Editing Suite) don't suffer, even when writing full DV Quality files which is stressing out the Disk system far more than bbMPEG seems to.

I'm pretty much sure it's a problem with bbMPEG itself, I've got zero other issues on this machine, even doing other very intensive stuff which really throttles the disk and processor to maximum.

On this CQ thing, I'll set it to VBR to do the next DVD anyhow just to see if it becomes quicker at this phase, although I've never noticed the time it takes purely cause I don't watch it!