For questions, answers and opinions
This forum is for Audacity on Windows.Ok thanks.Gale Andrews wrote:Re-encoding at a higher sample rate never adds frequencies that were not there in the first place - it only provides the possibility that higher frequencies could be added.
Once again, those rates are non-standard. For maximum compatibility export as 11025 Hz by selecting that rate, not by typing in 11000 Hz (if you are doing that). By contrast, 16000 Hz is a standard rate.edwinn wrote:The issue happened aGaiN last night while exporting a 22 kHz FLAC to an 11 kHz MP3.
Do you mean those are the files that you exported, then re-imported into Audacity? If so the bug does not seem to be in Audacity.edwinn wrote:Here are FOUR files displayed in Audacity with a `fit vertically´ layout.
The FLAC file on top is on top, then 22k MP3 export, the 16k MP3, and 11k MP3 at bottom.
MP3's are lossy. They adjust encoded volume slightly according to what is thrown away and what retained. If you use the highest MP3 export bitrate (320 kbps CBR) the volume adjustment is less likely to happen. Audacity would have to intervene somehow to restore the original peak level if this was to be avoided.edwinn wrote:Notice minor clipping in MP3's
Thanks man, we can discontinue focusing on "non-standard rates." I'm using standard rates from the menu, or pull-down menu. You mean a custom sample rate can be entered? That sounds odd. What would it be used for?Gale Andrews wrote:Once again, those rates are non-standard. For maximum compatibility export as 11025 Hz by selecting that rate, not by typing in 11000 Hz (if you are doing that). By contrast, 16000 Hz is a standard rate.
Do you mean those are the files that you exported, then re-imported into Audacity? If so the bug does not seem to be in Audacity.
MP3's are lossy. They adjust encoded volume slightly according to what is thrown away and what retained. If you use the highest MP3 export bitrate (320 kbps CBR) the volume adjustment is less likely to happen. Audacity would have to intervene somehow to restore the original peak level if this was to be avoided.
Because Integer formats (16-bit and 24-bit) have an absolute ceiling of 0 dB, if Audacity looked for "over 0 dB", then it would never show clipping for integer format tracks. So what Audacity does is to show the warning indicators "at" 0 dB. Note that this means that the audio may not actually be clipped, but if sample values are at 0 dB, then the audio is dangerously high and "probably" clipped. Consider the red "clip indicators" to be a "warning" rather than anything else.edwinn wrote:What criteria does Audacity used to determine a RED clip indication? (this is going OT)
There will always be someone who needs some "non-standard" rate for some purpose. The only point I am making is that such non-standard rates, if used, could cause problems in some players. In my opinion, Winamp is being sloppy by displaying "11 kHz" when it is not.edwinn wrote:I'm using standard rates from the menu, or pull-down menu. You mean a custom sample rate can be entered? That sounds odd. What would it be used for?
Well, I imported a 22050 Hz FLAC (3 minutes 38 seconds) into Audacity, exported as 11025 Hz MP3 (64 kbps), opened it in Winamp 2.64 and it played the correct length in Winamp.edwinn wrote:Yes, those are the files exported from Audacity, then 'dropped' (drag and drop from file manager/explorer) onto a New Audacity window. I'd say there's a bug in Winamp, and am sure Audacity is strictly coded, seeing how precise it is. The problem with Winamp didn't appear until using Audacity in the last year. Been running it for 10-15 years prior and never had an issue.