On Mon, Oct 15, 2007 at 9:57 AM, Joost Yervante Damad <[EMAIL PROTECTED]> wrote:
>
> You will have to provide an exact recipe how to make it crash as it doesn't
> happen for me with some simple tests.
(Apologies for not getting back to you for months.)
I believe this is all you have to do:
Fil
On 10/21/07, Thomas de Grivel <[EMAIL PROTECTED]> wrote:
> > Much more user-friendly behavior would be to remember the user's chosen
> > peak volume in decibels, and adjust the amplification factor to hit that
> > peak volume with each successive segment.
>
> I would call that "Normalize" but there
Package: audacity
Version: 1.3.3-1+b1
Severity: normal
Most of the operations in audacity's effects menu, if repeated with Ctrl-R
on a different segment of a track, do exactly the same thing as they would
have done if chosen again from the menu. The "Amplify..." plugin is a
glaring exception. If
Package: audacity
Version: 1.3.3-1+b1
Severity: normal
If audacity is already running and one tries to open a second project from
a file browser (e.g. Nautilus) you get an error dialog saying that it's not
safe to run two instances of audacity at the same time and one should use
File->Open from th
Package: audacity
Version: 1.3.3-1+b1
Severity: normal
If you create a project in any way (e.g. File->New, File->Open of a non-.aup
file) and make some changes without saving it, Audacity will crash instantly
if you attempt to undo a change. This does not happen if you save the project
in .aup fo
5 matches
Mail list logo
