Difference between revisions of "Release Notes 2.2.1"
(added "most common and important issues"; set release date to 6 Dec)
|Line 72:||Line 72:|
Revision as of 17:25, 8 December 2017
|Audacity 2.2.1 was released on 6 December 2017.
- 1 Changes since previous version
- 2 Supported Platforms
- 3 Issues
- 4 Bugzilla
Changes since previous version
You can optionally change the colorway of the waveforms displayed in your project. The setting is per track and not per project so you can have multiple colorways in the same project as in the image below.
Four colorways are available with the color selection made from the dropdown menu in the track's Track Control Panel.
When we made the menu changes for 2.2.0 we introduced an entry into the File menu called "Save Other" which led to a sub-menu for exporting various audio formats.
Many users were confused by this change and found it hard to find where they could export audio from. So for 2.2.1 we have changed that menu entry to be.
We fixed a bug on Mac that caused Audacity to crash with certain Chain files. Plus we fixed another Mac bug whereby opening a second project from Mac's Finder produced a second inaccessible instance of Audacity.
- Audacity 2.2.1 requires the CPU to support the SSE2 instruction set which should be available on any Intel hardware produced after 2001 and any AMD hardware produced after 2003. To check what SSE levels your CPU supports, you can install CPU-Z. If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
- 2.2.0 does not officially support Windows XP.
macOS / Mac OS X
- Audacity 2.2.1 is for Intel Macs running OS X 10.6 and later and macOS. There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
- Linux support is tested on Ubuntu Linux.
- Audacity may compile on Gentoo, Debian, Mint.
- Audacity does not currently compile on SuSE Linux.
- Below are listed what we believe are the most common and important issues with 2.2.1 for most users.
- Timer Record may not reliably stop the recording on some machines. The Elapsed and Remaining Time counters may stop counting. In this case it will be necessary to force quit Audacity.
- On a few affected machines, the problem can be avoided if you leave focus on Audacity or ensure it has focus when recording is due to end.
(Linux) PULSE Audio
- PulseAudio is not reliable when used with Audacity on Linux. Playback or recording may freeze, recording dropouts or fast playback may occur when using PulseAudio.
- Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button).
- Workarounds: Try launching Audacity from the terminal with the pulse latency set to 30 ms in an environment variable:
- env PULSE_LATENCY_MSEC=30 audacity
- If you get underruns noted in the terminal, try a higher number in the PULSE_LATENCY_MSEC command. If the problem is unchanged, try a lower number.
- Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar. More help with this can be found here.
- The timing of notes during MIDI playback may sound erratic on some machines. Optimizing the system for low latency MIDI playback can help to reduce the inaccuracies.
- Far less of Audacity is properly accessible to visually impaired users than we would like. Currently the best supported platform for accessibility is Windows. We lost a lot of custom accessibility programming when we had to move to a more recent version of the wxWidgets library. A lot more detail about accessibility limitations can be found here
- Click on the bug numbers to see work done on these bugs.
|ID||Summary (3 tasks) ⇒||ID|
|42||Timer Record occasionally carries on recording past the scheduled end, requiring force quit||42|
|1726||Linux: MIDI playback timing / synchronisation problems||1726|
|276||Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams||276|