Unwanted behaviour-Most recently clicked

[stefanboman]

The "most recently clicked feature" is a great start and has a lot of potential!
I have two expand knob zones, one for EQ and one for most recently clicked...

But I have this issue where if I press for example an amp sim plugin, then the amp plugin flashes by really quickly then it opens the first EQ plugin window instead.
Then you have to click the amp plugin one again to open it. Not ideal.

I still want the EQ window to open up when I select a track but not when i specifically press a different plugin.
Any way to get around that?

[creativecontrol]

Greetings,

A few things here...

(1) Does your amp sim plug-in have an EQ section in it and is it recognized as having dedicated EQ parameters? If you repeatedly press EQ on that channel do you get a magenta view for some of the params in that amp sim plug-in?

(2) 19.7 adds the ability to click on a Track Name and have the surface section as defined by the preference Display Knobs From Most Recently Clicked DAW Area fall back to showing the Primary and Backup Functions as set in the Home Page options: for Knobs: 1st Expand Knob Function and Backup Function Selection on Attention Change. Yeah, that's a mouthful. So much for brevity.

Basically if you explicitly click on a Pan, Plug-in or Send then the Clicked DAW prefs tell the surface to populate your module of choice with those functions. If you click on a Track Name, what to show? So, it reverts back to showing what you define in your on attention prefs for each module in the Home page local options.

(3) If your amp sim does have an EQ (or DYN) component then this brings up the initial concern which is the "auto" identification of a dedicated DYN or EQ plug-in. Let me know what you are observing and we can discuss further.


best,


Jeff

[stefanboman]

Thanks Jeff,

The amp sim doesn’t have an eq section and is not recognized as an eq plug by the console.
And I also noticed that this seems to happen to almost any type of plugin I press.

A scenario.
I have bx ssl channelstrip on all channels so that one pops up on my 1st expand knob module up as it’s the first eq no matter what channel I’m working on.
Let’s say I’m working on channel 1(kick) eq(BX ssl) then I realize I want to tweak the bass distortion on channel 15, so I click on that amp sim plugin on channel 15.
Then the amp plugin window flashes by for half a second then the BX ssl plugin for channel 15 replaces that window. Even thou I pressed the amp sim.
Not ideal.
I want the BX ssl window to open when I touch a knob on the expand zone module or clicking on that plugin.
But I can’t figure out why it opens when I’m clicking on a totally different plugin.

Makes sense? How do I avoid this?

[creativecontrol]

Understood. What version of PT and S6?


Jeff



Sent from my iPhone using Tapatalk Pro

[stefanboman]

Latest on both. PT 19.6, S6 19.7

[creativecontrol]

Thanks. Here's what I would check first...

Home page > Local Options:
Open Windows on Workstation When Knobs Assigned = Off.

Turn this off for now.

Next, from the Settings > User:

Open Windows When Editing Mode:

Choose what types of windows you want to have opened automatically. I would recommend at least doing plug-ins and perhaps Pan here.

Let me know if that addresses the specific odd behavior. I'm presuming your Open Windows on Workstation pref was overriding the thing you clicked on from Pro Tools.



Jeff

[stefanboman]

Thanks Jeff!
I’ll try that first thing on Monday.

Now, have a nice weekend!

[stefanboman]

Jeff,

turning "Open window on workstation..." did the trick. Thanks!!

But now I have to touch the knobs for the selected window to open up in Pro tools.
Workable, but can this be adressed in a future update?

It was nice before that the(channels trip in my setup)window opened directly upon selection without touching the knobs.

[creativecontrol]

Sorry, just getting back from vacation. I think we need to do a series of tips on workflow strategies for managing the various preferences. We fully realize these can be rather daunting for many users. I’ll kick this off on Monday.


Jeff



Sent from my iPhone using Tapatalk Pro

[creativecontrol]

Greetings,

Before I add a few TOD entries specific to window management and Attention workflows, let's discuss a few of the rules, limitations, constraints and behaviors when setting up your S6 Preferences. For this first discussion, we will be addressing preferences located in two different locations:

Settings > User (the majority of the operational preferences are here)
Home > Local (little gear icon, preferences specific to console modules & MTM)

Let's start by folding in the new workflows which arrived in S6 version 19.5.x. These are triggered by clicking in the DAW and can be enabled from this window which lives under Settings > User.



If I enable Track Name, clicking on a track from Pro Tools will trigger an Attention action. Likewise, if Plug-Ins is enabled, clicking on a Plug-In insert will trigger an Attention action.

Let's fold in another preference into the mix. These are located under Home > Local.



The first option - Open Windows on Workstation When Knobs Assigned can be set to any physical section on the surface including Master Module, 1st Expand Knob, 2nd Expand Knob, Expand Faders, etc. If it is set to Master Module for example, based on my current setting of the last option in this same window - Function and Knob Page Selected on Attention Change, when an Attention is triggered, the Master Module will display Pan parameters. This Attention can happen due to the above preference by clicking on a Track Name in Pro Tools, or by clicking a triangular Attention button on an S6 Channel Strip.

Let's add one last preference. This one is located back in the Settings > User preferences.



If Open Windows on Workstation Attention is enabled, when I click on a Track Name (because that was ticked as a way to Attention from the DAW) in Pro Tools this will trigger an Attention - which will default to bring up the Pan function on the Master Module and also open the associated Pan Window in Pro Tools. If Plug-Ins is ticked under the Clicked DAW Area pref, both the Plug-In and the Pan window for the clicked track will open in Pro Tools. If I disable the Open Windows on Workstation Attention preference, only the Plug-In window will open when I click on it.

A few details about windows in Pro Tools...

It is not possible currently to have S6 on Attention simultaneously display two different plug-in windows, for example dedicated EQ and DYN. It is certainly possible to jump back and forth between EQ and DYN using the Open Windows When Editing Mode preference when touching knobs contained within Knob Zones.

On Attention behaviors can display a Plug-In plus a Pan Window or a Plug-In plus a Send Window. For example, we can click on a PhoenixII plug-in which triggers an Attention and based on the above settings, the Pan window for the associated track will also open. Likewise, it is possible to click on a Send in Pro Tools using the same Attention DAW prefs to display that Send and then automatically open the associated Pan window. If we change the preference Open Windows on Workstation When Knobs Assigned to 1st Expand Knob Module, and set the option 1st Expand Knob Function and Backup Function on Attention Change to EQ, if we click on a Send in Pro Tools triggering an Attention this will also automatically bring up the first dedicated EQ window on this track.

Since only a single Plug-In window is currently possible as noted above, if we click on a Plug-In in Pro Tools with this workflow, the clicked Plug-In will immediately be closed for the higher priority EQ, invoked on Attention. This dual window concern is a workflow we still need to address in my opinion.

All of the workflows described thus far have assumed that all of the UI windows have active targets enabled. This is a windowing priority button that has been in Pro Tools for quite some time. From the console, it is always possible to hold SHIFT while touching parameters from any section on the console to turn off the target - which has the effect of keeping that window active until the user manually closes it.

Let's continue to discuss tweaking settings to get the best results based on your workflow as well as the possibility of future implementation to optimize these behaviors.




Jeff