MAutoDynamicEQ Copy/Paste bug
-
- KVRer
- 18 posts since 26 May, 2023
When using the copy/paste buttons to copy settings between instances of MAutoDynamicEQ with different oversampling and channel mode settings, those settings are adjusted on the instance that I am pasting to despite the help menu stating that they should not be copied.
Can anyone else confirm this behaviour? Thanks
MAutoDynamicEQ V16.07
Operating System: MacOS 11.4
Host: Reaper V6.8
Can anyone else confirm this behaviour? Thanks
MAutoDynamicEQ V16.07
Operating System: MacOS 11.4
Host: Reaper V6.8
- KVRian
- 965 posts since 12 May, 2019
Yeah windows 11 reaper 6.81 madeq copy paste captures these settings. Maybe a mouse modifier would be in order for either capping or not capping these options.tingshuo wrote: Wed Jul 19, 2023 3:40 am When using the copy/paste buttons to copy settings between instances of MAutoDynamicEQ with different oversampling and channel mode settings, those settings are adjusted on the instance that I am pasting to despite the help menu stating that they should not be copied.
Can anyone else confirm this behaviour? Thanks
MAutoDynamicEQ V16.07
Operating System: MacOS 11.4
Host: Reaper V6.8
-
- KVRer
- Topic Starter
- 18 posts since 26 May, 2023
Thanks for confirming. I guess I'll lodge a ticket with the support page - I'm not sure if they monitor the forum?
Key modifier would be good, but my vote would be for the copy/paste function not to grab any 'settings', only the EQ band parameters. I just want to be able to grab the curve and dynamic band settings from one place and paste it to somewhere else in my session. I feel like settings etc. are better dealt with in presets.
Key modifier would be good, but my vote would be for the copy/paste function not to grab any 'settings', only the EQ band parameters. I just want to be able to grab the curve and dynamic band settings from one place and paste it to somewhere else in my session. I feel like settings etc. are better dealt with in presets.
- KVRian
- 965 posts since 12 May, 2019
There's a melda team member named martin on this forum and Vojtech comes here periodically. You can click through a few threads to see the various emails they've posted and send them one. I've never used their support page so idk how that goes. Melda is among the most responsive developers so I anticipate your request will be heard - though not necessarily implemented.tingshuo wrote: Wed Jul 19, 2023 2:02 pm Thanks for confirming. I guess I'll lodge a ticket with the support page - I'm not sure if they monitor the forum?
Key modifier would be good, but my vote would be for the copy/paste function not to grab any 'settings', only the EQ band parameters. I just want to be able to grab the curve and dynamic band settings from one place and paste it to somewhere else in my session. I feel like settings etc. are better dealt with in presets.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
I'll check!
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
So, it indeed does that. Now the question is if we want it, cos the more I think about it, it's actually what I DO want
. So I'll jsut fix the help.
-
- KVRer
- Topic Starter
- 18 posts since 26 May, 2023
Hi Vojtech,MeldaProduction wrote: Thu Aug 03, 2023 10:49 am So, it indeed does that. Now the question is if we want it, cos the more I think about it, it's actually what I DO want. So I'll jsut fix the help.
I want to present my use case to you which really needs a simple copy/paste of EQ band parameters between instances without other settings being impacted. Maybe this is a feature request then.
I work in audio post-production and often need to copy ‘static’ EQ automation ‘state’ from one place in the session to another. Usually this will be on the same track and so the current behaviour doesn’t cause a problem. On other occasions, I’m pasting to an instance on a different track, which may have a different channel count (for example a Dialogue Buss will be 6 channel, whereas a Dialogue track will be Mono). In those situation it’s really inconvenient to have the ‘higher level’ settings be changed when I only want the EQ band settings.
Any way to accommodate this? Melda seems to be unique (in my limited experience) in copying those types of settings - personally I think they would be better handled with presets. Thanks very much.
-
- KVRist
- 168 posts since 1 Dec, 2020
From a GUI perspective, my intuitive expectation to copy only the bands and not the settings would be to click and drag a rectangular marquee to highlight / select the bands, right click, and then choose copy from the context menu. Then press the paste button in a different instance.
- KVRian
- 965 posts since 12 May, 2019
Or, using conventional melda implementation, they could add a copy-paste button to the EQ Bands panel next to the Reset, Invert, Swap gains, and Band Graphs buttons. Something like the Copy analysis buttons above the analysis/puck/main area panel.
-
- KVRer
- Topic Starter
- 18 posts since 26 May, 2023
I quite like this idea, but to be clear, I'd be hoping for all 'automatable' parameters to copy, including things like Dry/Wet, Input & Output Gains, Saturation, etc. - not only the parameters directly viewable in the Bands panel. I just don't want non-automating settings like oversampling, channel count, etc. This is almost the way that the A-H presets, A/B button and Morph work, which are directly next to the existing Copy/Paste buttons.Hexspa wrote: Sat Aug 05, 2023 1:12 am Or, using conventional melda implementation, they could add a copy-paste button to the EQ Bands panel next to the Reset, Invert, Swap gains, and Band Graphs buttons. Something like the Copy analysis buttons above the analysis/puck/main area panel.
At risk of expanding this too far, I also find it annoying that display settings like UI size, panel views and Analyzer settings are linked to the A-H presets and the Copy/Paste. I don't want panels opening and closing and the UI resizing as I audition different EQ settings. To me, this group of functions should all be exclusively for parameters that can be automated. Perhaps there's a use-case different to mine that requires this?
- KVRian
- 965 posts since 12 May, 2019
We have two distinct behaviors already and this request makes three. Is there an opportunity for consolidation or clarification here?
I'm testing presets and they do change the GUI but they don't change the channel settings.
We have presets and copy paste now. I think it's strange that they behave differently: presets do not copy channel settings yet copy paste does. Now we have a request for yet another behavior.
What I say is that if we're going to have a new preset behavior, something gets merged. Is it in our best interests to have three separate gradations of 'preset/settings copying'? If so, it would be best to be clear about it. From what I've seen, nobody has mentioned this existing dual behavior; though I recall an MDrummer analysis that went into the intricacies of its preset system.
Maybe it comes down to documentation but all I'm saying is I want to know what is going to change, if anything, and how to use it. Basically, I'm following this thread.
As an idea, what about a popup which has checkboxes that lets you select what you copy to the preset or clipboard? Melda already has popups in the plugin so it's not a stretch. This way you could get granular about what you do and don't want and it could replace all three existing options. This wouldn't really affect backward compatibility because you could have a "legacy" checkbox which populates the checkbox list with what 'used to happen'. I sound like a checkbox fanatic. lol I'm just saying this is a little crazy so let's make it better if possible.
I'm testing presets and they do change the GUI but they don't change the channel settings.
We have presets and copy paste now. I think it's strange that they behave differently: presets do not copy channel settings yet copy paste does. Now we have a request for yet another behavior.
What I say is that if we're going to have a new preset behavior, something gets merged. Is it in our best interests to have three separate gradations of 'preset/settings copying'? If so, it would be best to be clear about it. From what I've seen, nobody has mentioned this existing dual behavior; though I recall an MDrummer analysis that went into the intricacies of its preset system.
Maybe it comes down to documentation but all I'm saying is I want to know what is going to change, if anything, and how to use it. Basically, I'm following this thread.
As an idea, what about a popup which has checkboxes that lets you select what you copy to the preset or clipboard? Melda already has popups in the plugin so it's not a stretch. This way you could get granular about what you do and don't want and it could replace all three existing options. This wouldn't really affect backward compatibility because you could have a "legacy" checkbox which populates the checkbox list with what 'used to happen'. I sound like a checkbox fanatic. lol I'm just saying this is a little crazy so let's make it better if possible.
-
- KVRAF
- 10367 posts since 2 Sep, 2003 from Surrey, UK
IMO ... Getting a pop-up with check boxes every time I copy would be a pain.
I would stick with the behaviour in the current info - do not copy oversampling, channel count etc. If you do want to use a certain oversampling level etc in the target plug-in then you would have changed it anyway.
Or, if you consider that copying oversampling etc is needed, then add a feature to use Shift+click on the "Copy to clipboard" button?
--------------------
PS: Dry/Wet, Input & Output Gains, etc are currently copied.
I would stick with the behaviour in the current info - do not copy oversampling, channel count etc. If you do want to use a certain oversampling level etc in the target plug-in then you would have changed it anyway.
Or, if you consider that copying oversampling etc is needed, then add a feature to use Shift+click on the "Copy to clipboard" button?
--------------------
PS: Dry/Wet, Input & Output Gains, etc are currently copied.
-
- KVRer
- Topic Starter
- 18 posts since 26 May, 2023
Seeing as Vojtech commented earlier on this thread and there hasn't been any further comment from Melda, would this be considered case closed? Just wondering if I should make a new thread that consolidates the suggestions made here after Vojtech's comment. Or perhaps an email to support. Cheers.
