SpruceUp - "Last Audio Frame Incomplete"

[lemmy999]

I have a large 8 hour mpeg file (1/2 DVD resolution) that I have cut up in to 8 1 hour segments, then cut the commercials out of each one. I used Womble MPEG-VCR for each one. The audio on these files is MP2. The files were recorded with an ILO DVD recorder. They play fine, but when I try to import them in to spruce up, toward the end of the importing process for the audio file I get the following error:

"The last audio frame is incomplete. Continue parsing will skip this frame and terminate the parsing normally. The stream will then be used with one frame lss from now on. Otherwise, abort the parsing to correct the problem. Do you want to continue parsing?"

If I click yes, it finishes and the audio plays ok in the beginning, but I haven't made it to the end of the video to see if there is a sync problem. So far I have imported 3 and they all have the same error at approximately the same point in the audio importing process (maybe 95% finished). How can I correct this error?

[BJ_M]

you would have to re-encode the audio segments separately is the only real way

[lemmy999]

What caused the problem in the first place? How can I avoid it in the future?

[mazinz]

it just happens (my reasoning) but seriously, dont even worry about it, your audio will still be fine. Its telling you the very last frame (which is roughly .001 of a second Kind of deal) is going to be cut at the END of your file. It would be nothing you notice/hear/or see wrong results in. --

[lemmy999]

You are right. I have played it and everything sounds fine. I was just curious why it was happening. I have never had this problem before, but this is the first time I have imported mp2. It has always been AC3 in the past.

[mazinz]

i have had this happen on ac3 files before and sometimes even wave files when i used soft encode to convert them to an ac3. Picture the last frame of a video which is virtually nothing, use this as an example of when the last frame of an audio file has to be cut--

[Marco33]

I get the same error, never was a problem... I just ignore it.