Steve found that if you preview an effect and, say, cancel it
before it finishes preparing, an apply will not modify all of
the originally selected audio...just up to the preview length.
This is very easy to reproduce using the Paulstretch on a 30
second clip...just click stop on the "Preparing preview"
dialog and the click apply.
We can't go to 3.0.1 yet as there are still build issues on
Linux and OSX. You can get Windows to build, but there's
still some display issues.
These changes should work with wxWidgets 2.8.12 as well, so
we can take our time to get things working properly before
switching over.
He also added a new Nyquist control header that gives each
effect the ability to control the presentation of the Preview
button. This will be used by effects are time based and, therefore,
do not produce the same results in preview as they do when applied.
I expect Steve will be committing changes to the effects that can
take advantage of this shortly.
Testing of this can be accomplished by adding:
;preview enabled
to the "tremelo.ny" effect, just after the ";action" line.
Adding that line will cause the "Preview" button to be shown and
you will then be able to preview, adjust, preview, apply...
This change is believed to be a direct refactoring that does not change functionality. It paves the way for more complex kinds of selection, such as selections involving frequency as well as time. It also reduces risk of left and right edges being swapped in future code using SelectedRegion, as the default is to swap on assignment if needed.
Adds a transition from green to yellow starting at -12 db
or (0.50 for linear) and ending at -6 (or .75). A transition
to red then occors to the end of the meter.
Meter preferences have been added and most of the context
menu items have been moved there.
In addition, you may now click the playback meter to reset
the peak level indicator instead of having to click the
record meter.
We do not now prompt about new modules at start up, unless you set a module to 'ask'. This means we can ship experimental modules with Audacity. Users can enable them if they want to, but aren't troubled by them otherwise.
I can't believe two things...
I can't believe I didn't test the textual display! I'm really ashamed about that.
And I can't believe that we've never had anyone report a crash when attempting to
using the textual display with plugins that do not supply textual parameters. Some
examples are the ones from BBE Sound.
I went back to Audacity 2.0 and they would crash there as well. I'd wager they
probably always caused Audacity to crash.
Not much can be done except to fall back to the graphical display.
The problem was the the splash window was displayed
when the FFmpeg warning dialog appeared. Just needed
to hide it before deleting the window since the actual
deletion is defered to some time later.
