View Full Version : Why TooLAME/BeSweet and not TMPGEnc’s own audio?
nhope
14th February 2002, 17:32
Why are people saying to use TooLAME or BeSweet? What’s wrong with TMPGEnc’s built-in audio? Can anyone really hear the difference?
Doom9
14th February 2002, 18:29
first off.. you mostly have 48khz input that you want to convert to 44.1khz.. and tmpg's engine is terrible (and that's still a compliment).. so you have to set up external encoding tools anyways and why not take the best there is? in the case of besweet.. it does direct ac3 -> mp2 with max gain, no overflows and the best sampling rate conversion there is and all in floating point mode.. don't settle for less... you can definitely heard the difference between loading an ac3 in tmpg and encode this via ds filters and doing ac3 -> mp2 in besweet.
nhope
15th February 2002, 17:11
Thanks very much for the advice. Sorry to be stupid but what's an ac3? Is that the AVI audio component I am exporting from Premiere now? Shall download BeSweet right away.
nhope
15th February 2002, 17:15
Actually I mostly have 44.1khz. My videos are underwater so I bin the audio and put on a soundtrack of 44.1khz WAV's ripped off CD's and export from Premiere at 44.1. But I'll try BeSweet anyway.
nhope
15th February 2002, 17:58
Sorry, another question: Can Be-Sweet be used live during frameserving as an external encoder in TMPGEnc, as TooLAME can, or would I have to produce the audio as a separate process?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.