Hi Ardour maintainers,
Did someone of you already look into:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446597?
I ask because this is the only thing missing from fixing the
security flaw in ardour described on:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445889
Kind regards
Nico
--
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
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
2007/10/22, Zack Weinberg [EMAIL PROTECTED]:
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.
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 is already
Hi. I've been working on csound, and I think the package is going nice. I
would like, however, an independent review of the package. The debian/rules
file in the svn repo contains a get-orig-source rule to get and dfsg-clean
the upstream source. It will leave an appropriate tarball in the
6 matches
Mail list logo
