Jump to content

Plugin windows behavior changed yet?


Danny Wyatt

Recommended Posts

Since the first days of using Logic back in 2007 I've always thought this feature makes no sense, because it has no purpose on working like this and in fact creates a broken workflow. That is:

 

Let's say I have a channel strip with an EQ, then a Compressor and then a Limiter. If I'm mixing a song and I have all of those windows open so I can work on everything at the same time on multiple open windows, if by any chance I decide to add a Gain plugin BEFORE the EQ, now all my open windows change, creating a visual mess. Now my workflow is broken and I need to open the plugin that eventually disappeared and reorder all the windows again.

 

Is this still working this way after 10.4.6?

I honestly don't understand how Apple thought this was a good workflow and what the purpose was...

 

I mean, if I add a new plugin, all the open windows should remain open and in place and it should only open the new plugin's window, if that option is selected (to open a new plugin on insertion)

Link to comment
Share on other sites

... now all my open windows change, creating a visual mess....

Could you share a screenshot or two ?

 

It's pretty simple and you can recreate this:

Create a new track and add 3 plugins (e.g. EQ, Comp, Limiter).

Open all of those plugins. Now you have 3 windows open, right?

Now before the EQ (your first plugin on the chain), add for example a Gain plugin. Once you do that, all the windows that were open, will change.

 

This is the initial state:

before.thumb.png.02028254032ec8da82d943bb7895389e.png

 

This is when I insert the EnVerb. Look at how the window with the limiter is gone and the other 2 plugins' windows changed without me doing anything.

The Enverb took the EQ's window. The EQ took the compressor's. The compressor took the Limiter's

after.thumb.png.943181acbaf5f165b19c1fb82c51157e.png

Link to comment
Share on other sites

I think the problem is that windows are referenced based on the plugin slots. If you open a window for plugin slot 1, then insert a new plugin before plugin slot 1, the plugin slots are reordered, and the window showing plugin slot 1 will change to show the new plugin on slot 1 (the old one is now in plugin slot 2)

 

This will always happen if you change the plugin order by inserted or rearranging, it's just how Logic has been implemented, nothing has changed in this regard afaik. I'd suggest filing a Feedback if you're prefer a different behaviour...

Link to comment
Share on other sites

I think the problem is that windows are referenced based on the plugin slots. If you open a window for plugin slot 1, then insert a new plugin before plugin slot 1, the plugin slots are reordered, and the window showing plugin slot 1 will change to show the new plugin on slot 1 (the old one is now in plugin slot 2)

 

This will always happen if you change the plugin order by inserted or rearranging, it's just how Logic has been implemented, nothing has changed in this regard afaik. I'd suggest filing a Feedback if you're prefer a different behaviour...

 

 

Yes I’ve sent them some feedback about this.

I mean I understand why it works like that based on their “logic”, but it doesn’t make sense. Do you have to change all your automation if you add a new plugin as well or you simply change the order of a plugin? No. Logic automatically knows that plugin A is unique and that automation belongs to that plugin. Why wouldn’t windows behave the same way?

 

When you say “if you prefer a different behavior”, do you mean you don’t feel that this is not a natural behavior and should be changed?

I mean, if I’m mastering a track and I have 3 meters open and other plugins and suddenly I add a new one, am I supposed to go back and open those windows again and position them where I want them to be? Not natural and not logical at all (to me at least)

Link to comment
Share on other sites

No, I'm simply saying, this is the way it's been implemented, for whatever reason, and if you think if could be improved, send them some feedback (as you have done.)

 

I made no comment on how I feel about the current implementation at all... it's a workflow thing really - I can't say in using Logic since the early 90s that I've ever been bothered by this, but if it's something that is sub-optimal to you, that's what Feedback is for.

 

Basically, you want a given window to stay showing a given plugin (ie, the window is associated with the *plugin*), but Logic's implementation is that a window is associated with a particular *plugin slot*, not a particular plugin.

 

Neither approach is right or wrong, just the result of implementation and design decisions. I can see why you feel the current implementation is sub-optimal though.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...