Audacity Forum

Try running this in the Nyquist Prompt effect: ;version 4 (abs-env (setf pulse (pwlv 0 0 0 0 1 0.01 1 0.01 0))) Then zoom in very close on the resulting audio. If your selected track is at the default sample rate of 44100, you will see 22 samples each with an amplitude of 1.0. That is 0.01 seconds a...

Perhaps you could upload the project somewhere (such as dropbox or sendspace) so that we can check it. The easiest way to upload the entire project is to create a ZIP file containing both the project's "AUP" file and its "_data" folder, then upload the ZIP file somewhere. (There'...

The message is coming from Gatekeeper, which is intended to prevent you from accidentally running unknown software that may be unsafe. Gatekeeper is frequently over cautious, but can sometimes protect you from malware, so it shouldn't be turned off completely. The first thing to do is to ensure that...

I can see what you're doing with Equalization and Auto Duck, but what is DtBlkFx doing?

Had another look and it is looking increasingly like a bug in Microsoft Windows. It seems that Windows can only see the metadata in 24-bit WAV files if the length of the audio is an exact multiple of 3 samples. Try this: Before exporting as 24-bit WAV, set the Selection Toolbar to show the length in...

Thanks, got it. On Linux, (my usual machine), the tags show up correctly in all applications that I've tried (Audacity, Thunar, MediaInfo, Kid3 and VLC). On Windows 10, the tags show correctly in Audacity, MediaInfo and MP3Tag, but not File Explorer, Groove Music or Foobar2000. I don't see anything ...

The echo is because the effect is being applied twice - once when you clicked the "Apply" button, and again when you play again with the effect still enabled. After applying the effect (clicking the "Apply" button) you need to either: a) Close the effect b) Untick the "Enabl...

brettdonald wrote:We're starting to get annoyed by popups every time we run Audacity, telling us that this time is coming closer.

Yes we are aware that Apple have decided to harness "pester power" in their quest to drop 32-bit support. 64-bit Mac builds will be announced when they become available.

But why abandon them at all? It can't be that hard to build for both architectures. Because Audacity is developed and maintained by a small group of volunteers in their spare time, and we don't have the resources to maintain two architectures on Mac. If you you would like to get involved and help, ...

PiTeRr wrote:

Code: Select all

(setf pulse (pwlv 0 0 0 0 1 0.01 1 0.01 0)))

That gives you coordinates of: