FrEEwilL
10th May 2003, 12:24
as far as i undertand, in besweet gui, green button calls beweet.exe and blue button calls lame.exe while encoding wav->mp3.
but besweet outputs are bigger by 50+kbps in averages, with the same lame_enc.dll and arguments.
i can't think besweet's floating process makes such differences. does it ? even if yes, i doubt it's worth that high bitrates. besweet gave out 220~300kbps while lame gave out 150~200kbps for a whole cd. any thoughts ?
btw i'm doing VBR with r3mix's recommended settings. (besweet 1.5b17+GUI 0.6b73 & lame 3.93)
[EDIT] it looks like that "--athtype" switch was the cause.
i have no idea if it's dll or besweet but anyway besweet and lame showed opposite results with and without --athtype.
but besweet outputs are bigger by 50+kbps in averages, with the same lame_enc.dll and arguments.
i can't think besweet's floating process makes such differences. does it ? even if yes, i doubt it's worth that high bitrates. besweet gave out 220~300kbps while lame gave out 150~200kbps for a whole cd. any thoughts ?
btw i'm doing VBR with r3mix's recommended settings. (besweet 1.5b17+GUI 0.6b73 & lame 3.93)
[EDIT] it looks like that "--athtype" switch was the cause.
i have no idea if it's dll or besweet but anyway besweet and lame showed opposite results with and without --athtype.