Why is there a beep when I join videos with TMPGEnc?

[justified]

At the spots where the joining occurs I hear a little beep noise. Why is that?

I'm trying to put together segments of a TV show that was cut at odd spots (ie. while the sound was still playing), but even when I faded out the sound at the edges the beeping still occured.

[Hong Kong Phooey]

@Justified. I'm sure the more technically minded on this forum will give you a more detailed answer as to exactly why it happens, but I can tell you that it's more likely to happen in instances such as yours where there is sound in the 2 sequences you're joining.

When possible your better off joining the files when for example you get a "fade to commercial break" silent point. If you're really desperate, join the files with some overlap,(ie: some extra footage you don't need), between the offending audio "spike"/beep.

Then re-render the file using TMPGenc's Project wizard & use the "source editor". You'll see both the mpeg footage,frame nos. & also the audio beep via the sound display. simply cut out the footage with the beep & you'll get a clean version after the render. However, the downside is that you'll get a more pixelly mpeg file for rendering it twice.

[Bondiablo]

Actually, I've seen (or rather heard) this happen even when the two files are being joined at a commercial break. The only way I've been able to get rid of it is use the mpeg tools to cut off the tiniest possible bit from the very end of the original file in the sequence that comes right before the beep (even though you don't hear it in the original file) and then do the whole join over.

[pepegot1]

I have the same problem. I cut out the end of the first clip, but still the beep. It is retained in the final copy too. I also trimmed the second clip. Maybe joining the video and audio separately and then multiplex would work? any ideas?

[Bondiablo]

Are you sure you actually cut any off? You can only make cuts at certain increments. If you choose a point at which a cut can't be made it will just make the cut at the next available point, which in this case would likely be at the very end so no real cutting would be done. You can tell by watching as it's working, if it counts up to the exact same number of seconds as the original, you're not cutting any off.

PS: I've only seen this happen in Win98. I just recently installed Win2k as well and have yet to see it happen there.

[pepegot1]

Not knowing where to make the cut exactly, I chose to err on the side of too much. Still, no soap.

[pepegot1]

I just sent an email to TMPGenc and ask for their input. If I get a meaningful answer, I will pass it along.