VCDEasy truncates my MPEG files

[ldavis]

When I select an MPEG file to be burned into a VCD for some reason VCDEasy ignores the vast majority of the file. (This does not happen with Nero). On every file that I try, it finds data that is not VCD compliant and truncates the file at that point. When I analyze the MPEG file (using VCDEasy) I get a message that some volume of data was not as expected and that the reast of the file will be ignored. I am using the MPEG encoder of Cyberlink's PowerVCRII. Thanks for your help

[Jürgen]

Dear Idaivs,

I have the same Problems.
In My Case I captured TV with Virtualdub (MPEG 4V2); then Make a Conversion to MPEG 2 with SVCD setting described under HowTo with TMPEGEnc 2.53.
All Files were fine.
But in Case of Burning with EasyVCD I have exacly the same Problems.

In the logfile was written:

mpeg user scan data: one or more BCD fields out of range for 'next_I_offset ': [00:01.0b]
mpeg user scan data: one or more BCD fields out of range for 'forward_I_offset ': [00:08.0c]
mpeg user scan data: one or more BCD fields out of range for 'previous_I_offset': [00:01.0b]
mpeg user scan data: one or more BCD fields out of range for 'next_I_offset ': [00:01.0d]
mpeg user scan data: one or more BCD fields out of range for 'forward_I_offset ': [00:08.0d]
mpeg user scan data: one or more BCD fields out of range for 'previous_I_offset': [00:01.0d]
mpeg user scan data: one or more BCD fields out of range for 'next_I_offset ': [00:01.0d]
mpeg user scan data: one or more BCD fields out of range for 'forward_I_offset ': [00:08.0d]
mpeg user scan data: from now on, scan information data errors will not be reported anymore---consider enabling the 'update scan offsets' option, if it is not enabled already!
mpeg scan: pack header code (0x000001ba) expected, but 0x6b2c76a8 found (buflen = 2324)
bad packet at packet #327799 (stream byte offset 761804876) -- remaining 14694652 bytes of stream will be ignored

Can anyone HELP us

Jürgen

[HillJack]

You've probably figured it out by now, but I'll comment anyway incase others have not.

I've had that happen twice now.

I don't know why it happened, but re-encoding the entire mpg made it go away -- must have been a hiccup in TMPGEnc