For questions, answers and opinions
-1 from me. We would get way too many support requests of an Audacity "bug".waxcylinder wrote:+1 to thatsteve wrote:If that is the primary concern, then I venture to say that a better solution would be for "show clipping" to be enabled by default.The majority of users are importing music. And that music is usually compressed to death. It's as simple as that.
It would be virtually impossible for a sighted user to not notice that there is a problem with this recording: ...
AFAICT we are to record the following votes from cyrano:waxcylinder wrote:Is there a Feature Request to be teased out or voted for in this long thread?
Showing information about the imported file is quite a common request. Koz has voted for it many times but I try to remember to restrict him to 1 vote.cyrano wrote:Yes, Gale, that sums it up nicely.
Yes, but I was not meaning that. I was meaning, given you want to hide Audacity's potentially misleading file storage information and instead show the information about the original file, what do you do if you edit so that you have parts of different files in different tracks?cyrano wrote:Then it would need to be resampled to match the destination's sample rate, of course. Otherwise, you end up with a track that has different sample rates.
Yes all internal processing is in 32-bit. But I am not sure what point you're making. You can have multiple project windows in the same instance of Audacity. Tracks in a project can have different bit depths.cyrano wrote:I was lead to believe Audacity handled everything internally in 32 bit float. That would avoid the problem alltogether, since Audacity normally allows only one project opened anyway?
If you have Song_A.mp3 44100 Hz stereo 192 kbps MP3 and Song_B.wav 96000 Hz stereo 24-bit WAV in one track, what would you show in the Track Info above the Mute button? Suppose you imported those files into separate tracks, then Mixed and Rendered them to one track? What does the Track Info for the "Mix" track show?cyrano wrote:I'm still not sure what you mean exactly.
"Internal processing" means changing the sample values. Cut and paste does not change the sample values so does not change the sample format or require dither.cyrano wrote:If internal processing is 32 bit, all edits, as in cut and paste from one track to another are 32 bits, regardless of the source.
cyrano wrote:I don't think you need the info when cutting and pasting, but you do need the correct info after import.
Forgive me for being dense. Now I get it. That's a bit of a gotcha. But why would you put these on the same track? For me, one import = one track. I wouldn't even think about putting more than one item on a track, even if they had the same resolution. In fact, I think you can't do that in most daw's without automatic resampling or trouble (like running at the wrong speed).Gale Andrews wrote:If you have Song_A.mp3 44100 Hz stereo 192 kbps MP3 and Song_B.wav 96000 Hz stereo 24-bit WAV in one track, what would you show in the Track Info above the Mute button? Suppose you imported those files into separate tracks, then Mixed and Rendered them to one track? What does the Track Info for the "Mix" track show?cyrano wrote:I'm still not sure what you mean exactly.
I've been following that other thread* and noticed I didn't really understand Audacity's guts. IIUC, it isn't always treated and stored in 32 bit float. If the source is 24/48, the project will also be stored as 24/48, but once you start editing, it's 32 bit float. And when converting back after editing, dithering is applied.Gale Andrews wrote:"Internal processing" means changing the sample values. Cut and paste does not change the sample values so does not change the sample format or require dither.cyrano wrote:If internal processing is 32 bit, all edits, as in cut and paste from one track to another are 32 bits, regardless of the source.