Audacity Forum

1. What "Input" devices are shown in the "Sound" Preference? (see this post: viewtopic.php?p=411124#p411124)

2. What is the make and model of the cassette deck?

The key point here, is that my audio will have many clips (~hundred) and so manipulating manually makes no sense. If you are not manipulating them manually, what are you doing? It's near impossible to suggest a workflow without knowing exactly what the task is. My "tip" is essentially: Us...

steve, is there any policy on this? We have no specific policy on that, but I don't think it would be very effective as only a tiny minority of Fedora users visit this forum (possibly no more than a dozen or so in all the years that this forum has been running). For Ubuntu based distributions the a...

Do you mean: Once enabled, an effect can only be disabled (which removes it from the Effects Menu) or re-enabled. No, because plug-ins may be in the Effect, Generate, Analyze or Tools menus. It could of course say: Once enabled, an effect can only be disabled (which removes it from the Generate, Ef...

I can't reproduce that, or I misunderstand what you mean.
Please give exact step by step instructions to illustrate what you mean.

The "best" method is the method that works best for you. An "alternative" method is to use just a few tracks with multiple clips per track: 1. Split the track at the appropriate places (probably "command + i" on Mac) 2. Add a new empty track ("Tracks" menu) - ...

There is a known bug in Audacity 2.4.2 on macOS concerning sample rates of 32000. This has been fixed for the next Audacity release, but until then the workaround is to use other sample rates (such as 44100), and Resample tracks when necessary to avoid sample rates of 32000.

steve wrote: ↑

Fri Dec 11, 2020 10:22 am

Interestingly I see the same bug in Audacity 2.3.3.

and in Audacity 2.3.2, though in that version I'm also seeing additional weird selection values that don't occur in 2.4.2.

This issue is now logged on the Audacity bug tracker.
I'm surprised that no-one has reported this bug 'till now

Interestingly I see the same bug in Audacity 2.3.3.

How strange. The problem only appears to occur when the language is set to German. I shall log this bug.

As a work around you could select "hh:mm:ss + samples" as the time format.