SVCD burning problems...

[Poke]

Hi, I am trying to burn the .bin and .cue of a SVCD I got and I have tried using Discjuggler, Fireburner, and CDRWIN.

Afer using Discjuggler to burn I tried to play it on my standalone DVD player and there would be a black screen and the inside of the DVD player would make a loud screeching sound.

Next I tried Fireburner and when I try to play it the picture is in black and white and is scrolling back and forth through the screen every 1/2 second (a problem I got with VCDs using Nero, but I figured that out but same kind of reaction from the player).

Next I tried CDRWIN. I got the EXACT same scrolling black as I did with Fireburner.

BTW, my Philips DVD player told me it could play SVCDs so unless I got a bitrate wrong or the wrong kind of CD-R I dont know what else to do.

Please help if you can.

Thanks,

Poke


<font size=-1>[ This Message was edited by: Poke on 2001-11-04 19:36:57 ]</font>

[vitualis]

You have a PAL/NTSC compatibility problem.

Your TV system one, your disc is the other.

If you live in North America or Japan, your TV system will be NTSC. If you live anywhere else, it will be PAL.

Have a look at the setup for your DVD player (get the manual out). There may be a way for you to force the player to out the signal as one or the other (this depends on your player though).

Regards.

[StudeBarc]

Poke, Apart from the NTSC/PAL probs Michael talks of, i'm curious as to what program has created the .bin and .cue files? Nero 5.x or better will burn bin/cue images. Go to file ..burn image..all file types...open the cue file and the write window should come up. If everythings OK just burn. I've used this several times from VCDXbuild and the process works well. The picture rolling etc does sound like an NTCS/PAL problem however.

[vitualis]

I strongly encourage you NOT to use Nero to burn CUE/BIN images for the reasons here: http://www.hvrlab.org./~hvr/vcdimager/nero_bug.html

Nero does not correctly burn CUE/BIN images.

CDRDAO, and CDRWin are the best CUE/BIN burners. Fireburner is probably fine.

Regards.

[vitualis]

Hmm... the site is down. Anyway, here is the text from that page... I don't have the screenshots. For all those Nero enthusiasts who think that Nero can correctly burn CUE/BIN images, read this CAREFULLY as it shows in precise detail how it doesn't:

---quotation from the above link---

Nero's BIN/CUE Bug
http://www.hvrlab.org./~hvr/vcdimager/nero_bug.html

Introduction
When several parties reported about the GNU VCDImager Demo VCD not working and various SVCD related problems, tracking down the cause lead to a serious bug in a common burning application.

This article has the purpose of explaining the bug and the experienced symptoms.

Source BIN/CUE Image
The sector data containing image file had a total length of 83477184 bytes, which gives 35492 (logical) sectors. Please note that the INDEX marks in .CUE files need to be added by the length of the lead-out, 00:02:00, in order to match the readings of the screenshots presented later. The video.CUE file is quoted below:

FILE "videocd.bin" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
TRACK 02 MODE2/2352
INDEX 01 04:19:38
TRACK 03 MODE2/2352
INDEX 01 04:34:54
TRACK 04 MODE2/2352
INDEX 01 05:15:36
TRACK 05 MODE2/2352
INDEX 01 05:23:52
TRACK 06 MODE2/2352
INDEX 01 05:31:68
TRACK 07 MODE2/2352
INDEX 01 05:40:09
TRACK 08 MODE2/2352
INDEX 01 05:57:38
TRACK 09 MODE2/2352
INDEX 01 06:13:72
TRACK 10 MODE2/2352
INDEX 01 06:29:67

Correct TOC
The following screenshot shows how the TOC should look like when burned correctly: sorry, no screenshot here

Bad TOC created by Nero Burning Rom
Below you can see how the broken TOC looks like, when burned with Nero Burning Rom. Most apparently 150 sectors are missing somewhere in the 2nd track. Notice also that the total disc length is 150 sectors shorter than the image file.

The version used was 5.5.2.4. As of today no version is known which does not exhibit this bug. If you should encounter such one, please notify me, so I can update this article.

sorry, no screenshot here

Caused problems
XA multitrack images are most commonly used for (Super) Video CD's, (S)VCD's for short. VCD's contain sector addresses in the first track which point to the following tracks recorded for addressing the track starts in addition to the redundant information recorded in the TOC of the CD-ROM. SVCD's also make use of scan point tables, which contain sector addresses for playing time related access to the VBR mpeg-2 streams.

Now, if the sector addresses become invalid, because the following tracks are not recorded as they were supposed to be, the following effects may be seen:

• entry points will point to wrong locations or even outside the MPEG stream
• fast forward/fast reverse operation may not work properly
• GOTO may not work properly
• MPEG tracks may not play at all
• MPEG synchronisation problems

Depending on your playing device (and how much use it makes use of the sector address references contained in the Video CD control structures) and the disc structure, you may notice more or less (or even none) of the mentioned problems. If you don't experience any problems it's ok, as long as you only use the discs with the same playing device (and the same firmware!), as any change may cause the track misplacements to become visible...

Links

• Related forum thread on VCDHelp.com (http://www.vcdhelp.com/phpBB/viewtopic.php?topic=51716&forum=1 )
• GNU VCDImager DEMO VCD (http://vcdimager.hvrlab.org/pub/vcdimager/examples/demovcd/ )
• CDRDAO (http://cdrdao.sourceforge.net/ ) - Free software multi-platform solution for burning bin/cue images properly

-----end quotation-----

Regards.

[StudeBarc]

Michael, Either that link is incorrect or something else but i can't get to that reccommend not to use Nero for cue/bin. Please enlighten me? I've used it on plenty of bin/cue with no probs at all? Nero v 5.5.1.8.

[StudeBarc]

Thanks for that, Michael. I'll get myself another burner like CDRwin or the like. OK