CDRWin ERROR - PLEASE HELP!!!

[Medical]

HI !

I created a SVCD image with VCDImagerEasy and
wanted to burn this image with CDRWin.

Unfortunatly I get this ERROR:
ERROR: file length is not a multiple of the CDROM Sector Size.

What am I doing wrong???
Thanks,
Med.

[Auric]

Hvr might be able to answer this but he's busy contacting Ahead GmbH (humor intended) so here goes;

I suggest it's the encoded mpeg -file that's creating your problem. The file probably has wrong number of gop's or sector information or something that does not match. I'm not an expert so all I could do is to suggest that you try different encoder.

I did exactly what you tried to do and the disc came out fine. I use Ligos LSX-LE for encoding. I've mentioned this before but my Philips DVD711 started to ff and rew after I encoded with Ligos. It's also ten times faster than TMPG.

[HillJack]

It means the filesize of the .bin you created is not an exact multiple of the sector size as stated in the .cue file - Your .bin is invalid and short (or long) some bytes.

example:

If your have a .bin file of size 470,948,016 bytes
and its .cue file says "Mode 2/2352" then...

470,948,016 / 2352 = 200,233 (a whole number; a multiple of the 2,352 sector size)

If your .bin file was 470,948,013 and its .cue file said, "Mode 2/2352" then...

470,948,013 / 2352 = 200,232.99872 (NOT a whole number; NOT an exact multiple of the 2,352 sector size), thus the error.

[Auric]

Cool piece of information!

[Medical]

Hi HillJack !

Thanks for the information!
As Auric already said: this is
indeed a cool piece of info!

How do I correct this?

I simply made this cue/bin files with
VCDImagerEasy and never had any problem
burning with Nero but I want to use
CDRWin for testing purposes!!!

Thanks for your precise info !!!!!
Med.

[hvr]

for some reason vcdimager did not create a correct .bin file...
where there any warnings or errors reported?
does the filesize reported of vcdimager match the one of the generated .bin file?

...you really can't imagine how busy trying to contact ahead is... everytime you try to, you have to fill out that survey...

[Medical]

Hi !

My bin file size is:
499.877.616 bytes
my cue file says:
TRACK 01 MODE2/2352
INDEX 01 00:00:00
TRACK 02 MODE2/2352
INDEX 01 00:06:00

So: 499.877.616/2352 is 212.533
I didn't get any error messages with VCDImagerEasy.
If the file is exactly as big as VCDImager stated I
don't know because I didn't care when it was created...

Any suggestions?
Thanks a lot!
Med.

I don't like surveys even they are strictly
not shared with third parties...

[HillJack]

If you get the invalid filesize error, you could _try_ using a program called BINChunker - it will scan a .bin file and check it for corruption, and it will also convert a .bin to an .iso (which you can even use WinImage on later to extract the files without actually burning). Run your .bin through BINChunker and see what it says...

You can get a copy of BINChunker @ http://www.broadband.org.au/downloads/BINChunker160.ZIP

There is a v1.70, but it doesnt pick up as many errors as v1.60 would.

Other than that, I honestly don't know what else you could do - I've never created a bin with VCDImager before

Good luck,
HillJack


<font size=-1>[ This Message was edited by: HillJack on 2001-08-10 19:59:59 ]</font>

[hvr]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
My bin file size is:
499.877.616 bytes
...
If the file is exactly as big as VCDImager stated I
don't know because I didn't care when it was created...
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

well, the filesize is a whole multiple of 2352 bytes, so it should be ok...

in case you haven't got the original mpegs anymore, you could vcdxrip the image, and re-vcdxbuild it...

have you tried to burn it again? maybe the filesize was not finalized yet due to caching or something like that, when you first tried...?

[Medical]

@ hvr & hilljack

Thank you SO MUCH!!! for trying to help me out!!!
Even on this board effords like you made are hard to find.

I am now going on holiday for a week, so I relax from the
VCD/SVCD struggling. I will then see if anyone succeded
in ff/rew. long mpeg2 clips on a philips DVD player.

It all started with the topic named:
"more about SVCD ff and rew, expert commentary welcome"
Auric mentioned that SVCDs burnt with VCDImager images
play well and are able to ff/rew. So I wanted to try.
But till now we don't know if these clips are longer than
40 minutes (which is the point).

I made a new image with the same result, I checked with
BINChunker (who said everything is alright).

Well anyway, I am going on holiday
and I send you the best greetings
Med.

[Auric]

I tried to build longer SVCD using VCDimagerEasy to test on a Philips -player but the program does not generate the bin or cue files, it scans the mpeg -file and stops saying:

"GNU VCDImager 0.6.2 [cygwin/i586]
INFO: scanning mpeg track #0 for scanpoints...
assertion "_vcd_salloc_get_highest (obj->iso_bitmap) + 1 == 225" failed: file "vcd.c", line 612
0 [sig] vcdimager 232345 stackdump: Dumping stack trace to VCDIMAGER.EXE.stackdump"

The small files work ok. What gives?

[hvr]

...u used that ligos encoder... right?
seems as if the GOP timecodes are running fast...

well, please use the latest 0.7.x version of vcdimager, which uses PTS times for scantable calculation and does support bigger scandata tables...

[Auric]

Yep, Ligos was used.

It seems that the timecode now refers to the disc playtime and not the actual timecode of the track like version 0.6.x did.

Do you think if it is possible to get the best of both worlds, correct timecode from 0.6.x and the ability to create the bin from 0.7.9?

(Sorry to spread this subject on several threads)

[hvr]

@aric

I've tried to get into contact with you by email; but I got a mailer error back

anyway; what I'd suggest you to do, in order to find out what's happening here;

could you run 0.7.9's vcddebug on the bin files created, possibly using the same mpeg stream, once with 0.6.2 and once with 0.7.9?

then try to compare the information contained in the TRACKS.SVD file...
(and/or alternatively send me the output of both debugs)

I've just this feeling, that the ligos mpeg encoder might trigger this behaviour...

[TOMMO]

Auric,

i have a Philips 711 but I am having problems with SVCD. Perhaps you could let me know the secrets of your success, please.

[Auric]

I made some SVCD's first with TMPG and Nero, but they didn't scan at all, even if I added blank scandata.dat.

I started to encode using Ligos LSX-LE -encoder and I was surprised as the discs worked on Philips after burning with Nero as usual (no need to add blank scandata.dat).

Note: we are talkin about discs with less than 40 minutes. I haven't tested bigger discs yet.

If you want to see scan on Philips go download my zipped 3,7 mb Nero demoimage from: http://www.eurozoom.net/demo.htm

It's a complete SVCD with menu and some tracks encoded with Ligos. It scans on Philips and there's no scandata.dat added.

BTR: Auric

[Auric]

More bad news about Philips DVD711, today I authored my first DVD-R using Ligos LSX-LE for encoding and SpruceUp for authoring. The result was burnt on Pioneer DVR-A03.

The finished disc plays without hiccup on my Yelo 800 (and looks beautiful!) but Philips DVD711 spits the disc out without a moment of hesitation. Big surprise and not a pleasant one.