Hear, hear.jmh wrote:Offset mode? ...but that's not what you were getting at.
you, you, and me...
There's simply too much to retain. And I find these forum discussions essential to learning.
Automation of Same Colored Controls In Same Area Challenge
Moderator: Bob L
- Dave Labrecque
- Posts: 12786
- Joined: Mon May 24, 2004 11:00 am
Re: Automation of Same Colored Controls In Same Area Challenge
Dave "it aint the heat, it's the humidity" Labrecque
Becket, Massachusetts
Becket, Massachusetts
- Dave Labrecque
- Posts: 12786
- Joined: Mon May 24, 2004 11:00 am
Re: Automation of Same Colored Controls In Same Area Challenge
I think you're right. There's no discussion (I don't think) in the help file of the individual view filters. But whoda thunk there would need to be? The only one that appears to need further explanation is that last one, which has multiple features that are unique unto itself so far as I know. I'm half wondering if Bob even knows about them! But that wouldn't make sense, right? Surely he coded all that granularity into it. That could not have spontaneously arisen on its own. Right?Todd R wrote:I think actually understanding the various functions of the Input FX Plugin is a black hole in the SAW User Manual, and that's where we started. And between us have revealed to ourselves what the "special feature"s of the Input FX Plugin is :-)
Sounds like AI has snuck in!
Dave "it aint the heat, it's the humidity" Labrecque
Becket, Massachusetts
Becket, Massachusetts
Re: Automation of Same Colored Controls In Same Area Challenge
oui, oui! je suis en France maintenant! Mon francais n'est pas terrible, tu sais...Dave Labrecque wrote:Todd, are you really in France? Polly voo frahnsay?
I've been living full time in France since 2020...and been working from my current residence since 2013
I have income property in the UK.
I moved to the UK in '96 and discovered SAW SE on the shelf at a computer store in '98.
I was born and raised in northern California; high school in Dallas, TX, then back to Cali.
Re: Automation of Same Colored Controls In Same Area Challenge
I'm going to say it is certainly a high order of difficulty to write any user manual. Something as complicated as a DAW is doubly difficult.Dave Labrecque wrote:I think you're right. There's no discussion (I don't think) in the help file of the individual view filters. But whoda thunk there would need to be? The only one that appears to need further explanation is that last one, which has multiple features that are unique unto itself so far as I know. I'm half wondering if Bob even knows about them! But that wouldn't make sense, right? Surely he coded all that granularity into it. That could not have spontaneously arisen on its own. Right?
Sounds like AI has snuck in!![]()
It might take users 20 years to discover certain functionalities! (sarc)
I should think the Input FX Plugin automation filtering is all by design; and it is smart, just have to arrive at a situation in which user is required to practice that functionality :-)
Is that Input FX Plugin functionality only relevant to an Input FX Plugin? Or does it also apply to Return and Output tracks? I haven't investigated that yet...surely, soon to come
Is it possible Mr Lentini left Return FX Plugin and Output FX Plugin filters out up until there was user outcry for said parameters? We do have FX sections on those channel types.
Or did the explanations just not make it in the Owners Manual? I'll be finding out, because I do have FX on Output tracks.
Re: Automation of Same Colored Controls In Same Area Challenge
Ha!
ok, I'm reading Understanding The Virtual Console section of the Owners Manual again
I realize reading this that I have used further confusing terminology.
for example: "The data next passes through the FX Post Fader Patch. This allows you to patch in SAWStudio native plug-ins, or DirectX or VST plug-ins."
OK, I have been referring to mixer channel automation as "native", and they are...so then the term "plug-in" is required to differentiate between native mixer channel parameters and native SS plug-ins; because they are different things
ok, I'm reading Understanding The Virtual Console section of the Owners Manual again
I realize reading this that I have used further confusing terminology.
for example: "The data next passes through the FX Post Fader Patch. This allows you to patch in SAWStudio native plug-ins, or DirectX or VST plug-ins."
OK, I have been referring to mixer channel automation as "native", and they are...so then the term "plug-in" is required to differentiate between native mixer channel parameters and native SS plug-ins; because they are different things
- Dave Labrecque
- Posts: 12786
- Joined: Mon May 24, 2004 11:00 am
Re: Automation of Same Colored Controls In Same Area Challenge
Cool! I mean... Frais! Froid?Todd R wrote:oui, oui! je suis en France maintenant! Mon francais n'est pas terrible, tu sais...
I've been living full time in France since 2020...and been working from my current residence since 2013
I have income property in the UK.
I moved to the UK in '96 and discovered SAW SE on the shelf at a computer store in '98.
I was born and raised in northern California; high school in Dallas, TX, then back to Cali.
Dave "it aint the heat, it's the humidity" Labrecque
Becket, Massachusetts
Becket, Massachusetts
- Dave Labrecque
- Posts: 12786
- Joined: Mon May 24, 2004 11:00 am
Re: Automation of Same Colored Controls In Same Area Challenge
Insofar as there seems to be consistent differentiation of all kinds between I-, R-, and O-type channels, I'd put money on that filter being input-channel-specific. I bet it's a case of Bob's practical nature deeming the usefulness R or O FX Plugin flilters as low--because: how often would anyone need to automate plugin parameters across a bus like that? Let alone how often would anyone need to filter for those automation entries?Todd R wrote:I'm going to say it is certainly a high order of difficulty to write any user manual. Something as complicated as a DAW is doubly difficult.
It might take users 20 years to discover certain functionalities! (sarc)
I should think the Input FX Plugin automation filtering is all by design; and it is smart, just have to arrive at a situation in which user is required to practice that functionality :-)
Is that Input FX Plugin functionality only relevant to an Input FX Plugin? Or does it also apply to Return and Output tracks? I haven't investigated that yet...surely, soon to come
Is it possible Mr Lentini left Return FX Plugin and Output FX Plugin filters out up until there was user outcry for said parameters? We do have FX sections on those channel types.
Or did the explanations just not make it in the Owners Manual? I'll be finding out, because I do have FX on Output tracks.
I'm thinking maybe the automatability of the native plugins came some time after the help file had been established--and relevant instructional text for that newer functionality's cool, new view filter never made it in. Just a guess.
Dave "it aint the heat, it's the humidity" Labrecque
Becket, Massachusetts
Becket, Massachusetts
Re: Automation of Same Colored Controls In Same Area Challenge
Ooh la...les francais utilise le mot anglais (Americain) "cool"Dave Labrecque wrote:Cool! I mean... Frais! Froid?![]()
Frais= "fresh";
froid="cold"
uh, in english, the French people (over-)use the american term "cool"
Re: Automation of Same Colored Controls In Same Area Challenge
Quoting myself, oh wellTodd R wrote: I have been using the F-Mixer a lot lately and pulling faders down on F-Mixer is about half the throw distance as Z-Mixer or W-Mixer (I never use W-Mixer)
I haven't used the F-Mixer much over the years, and what a mistake!
I hadn't grasped the concept very well, and last week I found myself digging into the user manual.
Holy Toledo, the F-Mixer is packed with info about your session at a glance and gives so many shortcuts; instant access to the Z-Mixer channel, etc.
F-Mixer is a wonderful thing
- Dave Labrecque
- Posts: 12786
- Joined: Mon May 24, 2004 11:00 am
Re: Automation of Same Colored Controls In Same Area Challenge
Sorry if this has already been covered (it's been a couple weeksTodd R wrote:I don't find the VST wrapper engage/bypass in that pop-up which was yesterday's point. Possibly that switch resides somewhere else than all the native controls?
Dave "it aint the heat, it's the humidity" Labrecque
Becket, Massachusetts
Becket, Massachusetts