bin/cue File Size is Twice the Size of the Original MPEG?

[TeflonDon]

Hello,

I have been using TSCV to create the bin/cue files from an MPEG encoded by TMPGenc.

The file size of the MPEG is appx 642mb after encoding. When I create the bin/cue, the file size is almost doubled!

I have searched the forums for a while now, and I have been unable to find the answer.

Any help is greatly appreciated.

Thanks!

[TeflonDon]

Bump ^

[vitualis]

How did you encode your MPEGs exactly (what settings did you use... did you load a template)?

Regards.

[TeflonDon]

I captured a 30 second clip using Dazzle DVC at 720x480, the captured MPEG came out perfect. The Size of the MPEG is 5.01mb

I then encoded using TMPGEnc with the following settings:

Size: 352x240 pixels
Aspect Ratio: 4:3 525 Line
Frame Rate: 29.97 fps
Rate Control Mode: CBR
Bitrate: 1205 kbit/sec
Source Aspect: 1:1 (VGA)
Video Arrange Method: Center (Keep Aspect Ratio)
Audio Bit Rate: 128 kbit/sec

I then used TSCV v0.73 to create 2 menus and 5 chapters. This is a copy of the log:

Starting VCDxBuild process...

initializing libvcd 0.7.10 [cygwin/i686]

this is the UNSTABLE development branch!
use only if you know what you are doing
see http://www.hvrlab.org/~hvr/vcdimager/ for more information

front margin set smaller than recommended (0
rear margin set smaller than recommended (0
scanning mpeg segment item "menu-0" for scanpoints...
mpeg stream will be padded on the fly -- hope that's ok for you!
autopadding requires to insert additional 117852 zero bytes into MPEG stream (due to 427 unaligned packets of 428 total)
scanning mpeg segment item "menu-1" for scanpoints...
mpeg stream will be padded on the fly -- hope that's ok for you!
autopadding requires to insert additional 128064 zero bytes into MPEG stream (due to 464 unaligned packets of 465 total)
scanning mpeg sequence item "sequence-1" for scanpoints...
mpeg stream will be padded on the fly -- hope that's ok for you!
autopadding requires to insert additional 708768 zero bytes into MPEG stream (due to 2568 unaligned packets of 2569 total)
requested entry point (id=entry1-1) at 5.000000, closest possible entry point at 0.000000
requested entry point (id=entry1-2) at 10.000000, closest possible entry point at 0.000000
entry point 'entry1-2' falls into same sector as previous one!
requested entry point (id=entry1-3) at 15.000000, closest possible entry point at 0.000000
entry point 'entry1-3' falls into same sector as previous one!
requested entry point (id=entry1-4) at 20.000000, closest possible entry point at 0.000000
entry point 'entry1-4' falls into same sector as previous one!
requested entry point (id=entry1-5) at 25.000000, closest possible entry point at 0.000000
entry point 'entry1-5' falls into same sector as previous one!
writing track 1 (ISO9660)...
writing file `CDI/CDI_IMAG.RTF' (1315168 bytes, raw sectors file)
writing file `CDI/CDI_TEXT.FNT' (13616 bytes)
writing file `CDI/CDI_VCD.APP' (102400 bytes)
writing track 2, MPEG1, NTSC SIF (352x240/30fps), audio[0]: l2/44.1kHz/128kbps/stereo ...
writing track 3, MPEG1, NTSC SIF (352x240/30fps), audio[0]: l2/44.1kHz/128kbps/stereo ...
writing track 4, MPEG1, NTSC SIF (352x240/30fps), audio[0]: l2/44.1kHz/128kbps/stereo ...
finished ok, image created with 4790 sectors [01:03.65]


VCDxBuild finished

=end of log=
Here are the specs of the other menus I added:
the size of the first menu: 856kb
the size of the second menu: 930kb


The bin file is now 10.7mb.

Thanks for your help!!
TD

[Vejita-sama]

1) Can you burn it (did you even try)? Because the bin file will often be larger than the MPEG (although not 2x as large).

2) It's possible that your time points are messed up. I would de-mux the MPEG, then re-mux w/ bbMPEG, then try to make the bin/cue. This often happens when I cut w/ TMPGenc or use any bitrate other than 1150/224 in Nero.

[TeflonDon]

<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>
On 2001-10-21 17:33:52, Vejita-sama wrote:
1) Can you burn it (did you even try)? Because the bin file will often be larger than the MPEG (although not 2x as large).

2) It's possible that your time points are messed up. I would de-mux the MPEG, then re-mux w/ bbMPEG, then try to make the bin/cue. This often happens when I cut w/ TMPGenc or use any bitrate other than 1150/224 in Nero.
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

I have tried to burn the larger file with CDRWIN and it work fine.

I created the same bin/cue with out the entry points and recived the same size bin file.

I don't follow when you say "de-mux the MPEG", then "re-mux the MPEG" please explain.

Thanks!

[jvilhauer]

I'm having a similar problem. The original TMPGEnc 12j mpg is about 595K, the cue/bin file shows about 620K (in explorer) with chapter info using TSCV 0.74 - However, when I go to burn it in Nero 5.5.5.1, it wants to burn about a 1.2GB SVCD, and of course tells me there's not enough room on the CD-R.

I've used the exact same process with previous versions of all apps and templates (TMPGEnc 12j, TSCV 0.73, Nero 5.5.4.0) and it's worked just fine.

Any suggestions?

[vitualis]

For TeflonDon:

1. Encode using the VCD templates with TMPGEnc. Your settings are not VCD compliant.
2. If you are going to create an XVCD (i.e., non-compliant disc), you must remux your MPEGs before using them with VCDImager. You should remux with TMPGEnc using the setting "MPEG-1 Video-CD (non-standard)".

Regards.

[jvilhauer]

Went back to Nero 5.5.3.5 and the bin/cue burns correctly, no problems. Nice upgrades, Nero!!

[bskolb]

Yep, had the same problem, size was double of actual. Installed prior version and it works fine!

[vitualis]

Firstly, don't use Nero to burn CUE/BIN images. It doesn't do it properly.

Secondly, with all non-standard MPEG-1s for VCD, you MUST demultiplex it and the remultiplex it with TMPGEnc on the "MPEG-1 Video-CD (non-standard)" option first.

Regards.