Baldrick,vitualis,Kwag>what do you think about this Nero BUG

[Pied-Piper]

I ask this question to know your opinion, because all of you always recommend Nero but never mentioned that it can't make vcds correctly.
I think Nero vcds are not perfect and the possibility of vcd video playback is not enough. seeing the vcd actual size while browsing by windows explorer always gives the viewer a better feeling and when the disk comes with a nice artwork and print on it, it could be thought as an original vcd but by Nero this is not possible because it writes an incorrect size on the disk.
Please read these topics:
http://forum.vcdhelp.com/viewtopic.php?t=90098
http://forum.vcdhelp.com/viewtopic.php?p=243839
Thanks in advance.

[adam]

I've had this happen to me with other burning programs also, not just Nero. I really don't see this as a problem since it only occurs on a pc and doesnt affect playback or compatibility at all. Windows misreports file sizes all the time, this may even be a windows bug and not a nero bug, but thats just speculation.

I definitely don't think Nero does a good job with svcds, but for vcds I think its fine. Actually I think its quite good. Like I said, this minor bug doesnt seem to affect playback or compatibility.

[kwag]

Actually I am recommending VCDEasy more than Nero.

The main reason I do is that you can make chapters with VCDEasy, but you can't with Nero.

I haven't used Nero for over 6 months now.

VCDEasy hasn't failed on me yet

That's my 2 cents.

kwag

[vitualis]

@ Pied-Piper,

This is not a bug at all.

The reported "filesize" of a VCD depends on the authoring program. I had a discussion with hvr at some point about this, but I don't quite remember the details.

The gist is, however, that the reported total size of the VCD can be either:
1. ONLY the physical files in track one (where the logical filesystem physically resides -- and thus, does not include the sequences --> ~2 MB in size)
2. OR it can include the sequences as well.

Nero does the former. This, again, is not a bug...

Of course, Nero does have other bugs (when it comes to authoring menus) and I don't recommend that you use it for anything other than a simple multitrack VCD (sans menus).

For good S/VCD authoring, I strongly suggest that you try VCDImager, by itself or with one of the now excellent GUI packages (e.g., VCD Easy or TSCV).

http://www.vcdimager.org
http://www.vcdimager.org/guides

Regards.

[Pied-Piper]

This is not a bug at all.

The reported total size of all original VCDs includes the sequences as well. So when an authoring program writes a vcd in a way that windows or any other OS can't report the video filesize what is it if it's not a bug?
Now I wonder why there is such a difference between burning programs,
some like NTI, WinOnCD and Ulead stuff make disks which include the sequences size and filesystem together but the size of nero vcds and some other programs' are misreported.
Now I think many of those who read this topic can ask this question:
What causes this and what's the exact disk structure difference?
Does it depend on when each track and filesystem is written?
or does this just happen when filesystem comes first and if it comes after video part the problem is solved?
I did not use Nero(due to this BuG or anything) till I started to burn some K(X)VCD, then I found other burning programs can't produce a proper DAT file of VBR MPEG so after months tried Nero!
I'm searching for a program that can burn XVCDs with a correct fiesize on them. If you know one it's very kind of you to mention its name here.

[vitualis]

The reported total size of all original VCDs includes the sequences as well.

I suppose that you know this because you own every single original VCD in existence?

I had the same disscussion about this with hvr (the author of VCDImager) and according to him the reported total size of a VCD can be either the two I posted before.

If you know the VCD specs better please enlighten us but don't push uninformed hypotheses (e.g., like in your other threads of the same topic).

So when an authoring program writes a vcd in a way that windows or any other OS can't report the video filesize what is it if it's not a bug?

As above.

Does it depend on when each track and filesystem is written?

Please actually read the responses people give to your previous threads! This has been answered before.

Regards.

[Pied-Piper]

I suppose that you know this because you own every single original VCD in existence?

I meant all original titles that I've seen so far and it's more than 1000 single disks. Can you please inform me if you know an original vcd with an incorrect size(like what nero does) on it.
Even the size of VCDs which have a text file that say they have made by Philips VideoCD 2.0 Toolkit, include the video filesize plus filesystem.

As above.

If it's not a bug, I'd better say it's a problem which some burning programs have. I don't know if there is a cue in whitebook specification about the disk total size, do you know what does it say on this topic?

Please actually read the responses people give to your previous threads! This has been answered before.

I answered this thread before reading your other post on "nero vcd size" or "lead in/out..."because I did not expect your response at the same time on my other topics. But I think it's very good if you can help and provide some technical information on the physical structure of a vcd which has written by the first method you described. what's the exact physical difference between the first method written disks and the second one's?
After all do you know a program which can burn K(X)VCDs with a correct size(the second method)? most of burning programs I've tried can't make a proper dat file out of VBR MPEG, for example when a VBR VCD MPEG is imported in WinOnCD it says it can't fit it on one disk and its dat filesize is bigger than usual!
If you remember, can you give a link to your discussion with hvr, please.

[vitualis]

Firstly, it is not the "incorrect" size. It is the "correct" size of the file contents of the filesystem in track one (which does not include the sequences -- the sequences are on subsequent tracks).

Secondly, there is no significant difference between (1) and (2) except for how the total disc size is reported. I do not know where this is located on the disc (perhaps you could ask hvr directly).

It does not have anything to do with how the CUE/BIN image is burnt. To convince yourself of this, you can mount the CUE/BIN image with daemon tools and see what it looks like then as a virtual CD.

You cannot "burn the filesystem after the video". The filesystem is physically located on track one and no matter what mode you burn in (TAO or DAO), track one is always burn before the other tracks.

As for your wish to have the total size reporting to include sequences (this is not necessarily "correct" or "incorrect" and hence not a bug), I don't know of any authoring program that does it for XVCDs. VCDImager as far as I recall only reports the "total disc size" as the contents of track 1 only (i.e., similar to Nero). Perhaps VideoPack 5 does it that way (but I've never used it).

I personally don't think that this is an issue at all and as long as you are getting functional XVCDs, you should be happy. However, if you want this to become an option (or the default) for VCDImager, you should contact hvr directly (by e-mail) and discuss with him. He knows the ins and outs of the VCD structure much better than I do.

Good luck.

Regards.