Page 2 of 2
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sat Feb 16, 2019 6:29 pm
by kozikowski
The work-around is open the curve you use all the time and change one point slightly or add one point somewhere it doesn't count. OK. That curve will now be default. If you then open it and delete the change, then the clean effect will get stuck.
Koz
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sat Feb 16, 2019 7:17 pm
by kozikowski
@KenRyan
We have a pre-baked Equalization for pops and rumble. Low Rolloff for Speech. It cuts off at about 100Hz. It's a cousin to the field recording filters that Hollywood uses.
Koz
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sat Feb 16, 2019 9:51 pm
by Trebor
waxcylinder wrote:Trebor wrote: ↑Fri Feb 15, 2019 11:05 pm
I get that too on Audacity 2.3.0,
Trebor, what OS are you on - it says Vista in your displayed info - is that still the case ?
Yes still Vista

I also have more than one version of Audacity on the Vista machine, that could be the cause.
Sometimes the repeated (Ctrl+R) equalization is just flat,
or some point on the EQ curve has moved a huge amount after the first application.
While we're on the subject ...
To me on 2.3.0
the equalizer GUI is still slow to appear when selected from the effect menu,
and there is a similar unnecessary delay (~3s) when equalization is previewed or applied.

Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sun Feb 17, 2019 4:37 pm
by waxcylinder
kozikowski wrote: ↑Sat Feb 16, 2019 6:16 pm
Got it. The rule is not
Last Curve Used. It's
Last Curve Modified. If you modify a curve and use it, that curve will get stuck there until the sun cools off.
It has nothing to do with Import or Export. The magic curve stuck from yesterday was simply the last curve I changed.
GREAT detective work Koz
and I confirm that finding testing on my W10 PC latop and on Mojave 10.14.3 on my Macbook Pro
I shall be logging this on Bugzilla as P3 or maybe P2 (P2 due to the fact that this can lead to Ctrl+R Cmd+R used with Equalization to applay the wrong curve - as indicated in te original post in this thread)
And many thanks to KenRyan for the original bug report
Peter.
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sun Feb 17, 2019 4:53 pm
by waxcylinder
Curiously this does not seem to happen when you switch Equalization into the non-default Graphic mode.
In graphic mode the last-used curve appears to be properly remembered, recalled and re-used.
Also note that when switching back from Graphic to Draw mode Equalization treat the last-used curve in Draw mode as if it was the "last-changed" curve (recalling and reusing that) even if it was a standard unmodified preset curve taht was used ij Graphic mode.
We need to remember that Equalization is really two sepatere effest mangle together (and not vert well) - it, or rtaher thay, need somke serios attention in the future.
And further testing shows that this is a regression on 2.2.2 - and thus will probably be a P1 bug.
Peter
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sun Feb 17, 2019 5:12 pm
by waxcylinder
BUT - when I test on the latest alpha builds on W10 and Mac for the upcoming 2.3.1 I do not see this bug - with Equalization remembering, recalling and re-using the last-used (and not the last-altered) curve.
I have no idea as to what might have changed - but there is little point in logging the bug only to close it off as FIXED (unknown fix).
So when 2.3.1 comes out (hopefully soon) all should be well again with Equalization remembering and reusing correctly.
In the meantime the workaround is to use EQ in non-default graphic mode.
Peter.
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Sun Feb 17, 2019 6:04 pm
by kozikowski
need somke serios attention in the future.
I struggle with it every time. The tool is one jump away from code.
If CURVE equals [unnamed] then RENAME [value] ..........
Koz
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Mon Feb 18, 2019 11:42 pm
by KenRyan
waxcylinder wrote: ↑Sat Feb 16, 2019 11:40 am
Or if you want to stay within Audacity ...
You could create a Macro with your favoured settings in the EQ command (inmcluding a custom curve of your own creation that the previously set up and saved in Equalization).
You can then , when working, keep the Macro Palette open on your desktop for ease of use - or simpler still, create a custom shortcut for the Macro.
WC
Hi WC. That would actually be preferable! I have not created a macro in Audacity before. I'll take a look through the manual for how to do that. I already have a saved curve of my own in the EQ effect.
Thanks for the tip!
Ken
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Mon Feb 18, 2019 11:46 pm
by KenRyan
waxcylinder wrote: ↑Sun Feb 17, 2019 4:37 pm
kozikowski wrote: ↑Sat Feb 16, 2019 6:16 pm
Got it. The rule is not
Last Curve Used. It's
Last Curve Modified. If you modify a curve and use it, that curve will get stuck there until the sun cools off.
It has nothing to do with Import or Export. The magic curve stuck from yesterday was simply the last curve I changed.
GREAT detective work Koz
and I confirm that finding testing on my W10 PC latop and on Mojave 10.14.3 on my Macbook Pro
I shall be logging this on Bugzilla as P3 or maybe P2 (P2 due to the fact that this can lead to Ctrl+R Cmd+R used with Equalization to applay the wrong curve - as indicated in te original post in this thread)
And many thanks to KenRyan for the original bug report
Peter.
Thanks for this tip!! I didn't know I was reporting a bug. But this will work. Woohoo!
Ken
Re: Repeat Last Command (Ctrl-R) Not Working Due to EQ Effect Changing?
Posted: Tue Feb 19, 2019 11:25 am
by waxcylinder
KenRyan wrote: ↑Mon Feb 18, 2019 11:46 pm
Thanks for this tip!! I didn't know I was reporting a bug. But this will work. Woohoo!
And even better news ken - Steve has fixed the bug for the upcoming 2.3.1 release - so all should be well after that.
I QA tested the fix on Q10 and Mac Mojave 10.14.3 and all looks to work properly now in this regard.
Peter