After reading the release notes, which are a bit scary.
Tested on Mavericks, with a lot of plugins, because I badly needed to weed out tests and expired demo’s from my plugin folder. Not one plugin crashed and everything worked! So, that’s good news as a few of those weren’t really stable in previous versions.
Several effects still have a “debug” button. Is this supposed to be there?
These effects have a debug button:
Adjustable fade
Crossfade tracks
Delay
High pass filter
Low pass filter
Notch filter
Tremolo
Vocal reduction and isolation
Vocal remover
Vocoder
When I closed an effect window with the red close button in the upper left corner of the effect’s window, I ended up with all menus grayed out and no way to get back to the effects window. Any way out, besides forced quitting Audacity?
Related to this?
The “Window” menu is not currently available.
From the release notes:
(Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: > You can try 1.3.10 Beta > or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Do you mean we should try Audacity 1.3.10 beta?
From the release notes:
Version 2.1.1 of Audacity for OS X does not have any accessibility or screen reader support due to a mistake in building. Version 2.1.2 doesn’t either, due to the transition to wx3 and the significant new work needed to support it. > VI users > can use 2.1.1vi for OS X whilst we sort this out for a future release.
Is this a typo? Should it be “VO” for Voice Over?
I hope you don’t mean the venerable Unix editor that’s called vi
Or is “Vi” something else?
They’re only a bit scary because they’re a bit long - and they’re only a bit long because Our buglist in Bugzilla has grown a bit.
But many/most of those bugs are issues that are seldom encountered in day to day use of Audacity .
And we are trying to have a big focus on bug-squishing for the next release of Audacity to reduce that bug-list
@Gale: maybe we could consider moving off the known issues to a sub-page of release notes to make them less scary and intimidating and TLDR? I read the whole of them (for editing purposes) and even I found them TLDR and intimidating. We do really want folk to read them - and to that end shorter is better.
In that case, wouldn’t it be better not to use an abbreviation, for search engine indexing and for the visually impaired, as they will probably be using a screen reader or a braille printer.
Gale generally avoids using abbreviations anywhere in the documentation (other than standard abbreviations like “dB”, “rms” and so on).
“VI” is a common abbreviation which is widely used by blind and partially sighted people (a variation of that David Skye used to use frequently was “VIP” meaning “visually impaired person”). Most probably its use in the release notes was an oversight when Gale was copy & pasting from his notes. I’d expect most VI users to understand the abbreviation.
Nah, the bug text has not been touched for four years.
I think the only remaining problem (Windows multi-channel devices won’t record more than stereo in Audacity) is now close to a WONTFIX. When that happens we would still keep the release note as help text. The text now says:
(Windows) Some devices that used to offer multiple recording channels in Audacity without ASIO may now only offer mono or stereo recording instead of the expected number of channels. Usually the multi or similar device only has 2 channels instead of the expected number. Occasionally the multi device is missing, leaving only two-channel devices to choose from. These devices have been reported:
Alesis Multimix-8 USB
DSP2000-CPort
M-Audio Delta 66
Motu 896 AD/DA FW
Tascam US 1641 and US 1800
** If you experience this issue please report make and model number of the device, your operating system (for example, Windows 7 Service Pack 1) and the device driver version number you are using. It is possible that more than stereo recording may be possible if you can find earlier drivers that are still compatible with your version of Windows, or if you try the Windows WASAPI host in > http://manual.audacityteam.org/o/man/device_toolbar.html> . See > http://wiki.audacityteam.org/wiki/Multichannel_Recording > for a list of devices reported to record multi-channels into Audacity without ASIO.
James has kindly prepared the last two Release Notes to reduce my workload. He was using his old version of that VI alert that said “VI” instead of the one that I had written.
The Release Notes are not included in the release - README.txt just contains a link to them. So changes to the Release Notes online are worth doing even after release.
And so do Clip Fix and Limiter for example have a Debug button. Most Nyquist effects should have a Debug button.
OK, thanks.
[quote=“cyrano”]
When I closed an effect window with the red close button in the upper left corner of the effect’s window, I ended up with all menus grayed out and no way to get back to the effects window. Any way out, besides forced quitting Audacity?
(Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: > You can try 1.3.10 Beta > or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Do you mean we should try Audacity 1.3.10 beta? > >
[/quote]
Nah, the bug text has not been touched for four years.
I think the only remaining problem (Windows multi-channel devices won’t record more than stereo in Audacity) is now close to a WONTFIX. When that happens we would still keep the release note as help text. The text now says:
(Windows) Some devices that used to offer multiple recording channels in Audacity without ASIO may now only offer mono or stereo recording instead of the expected number of channels. Usually the multi or similar device only has 2 channels instead of the expected number. Occasionally the multi device is missing, leaving only two-channel devices to choose from. These devices have been reported:
Alesis Multimix-8 USB
Hoontech DSP2000-CPort
M-Audio Delta 66
Motu 896 AD/DA FW
Tascam US 1641 and US 1800
[snip].
These are all older interfaces, with a less than perfect compatibility record. I wouldn’t bother either.
Also, I think it’s probably the “Alesis Multimix-8 USB II”, as the “Alesis Multimix-8 USB” is only capable if 2 I/O. Unless that ones shows up as mono, of course.
That would only reduce page length for the known issues by about 1/8th whereas the Changes and Improvements are already at the top. I doubt it would be that useful?
Would it be worth listing P2 separately? Then the user would more easily get a feel for what the most serious issues are.
I know we’re attacking P2’s right now, but suppose there were one or two P2’s that appeared inside the RC period that RM did not want to fix? For example the EQ bug in 2.1.1? Would it not be useful to have such a bug at the top?
