I prefer the way protools does this. In sonar the track arm state was
remembered. which was useful in some ways. But not so good for your speakers or
ears, if you load up a session with a mic connected to the input of the track
that was still armed. It used to get me a lot.
Steve
> On 2 May
Hi John and all:
then it must use windows machine.
Thanks so much
> On Apr 30, 2018, at 4:03 AM, John Gunn wrote:
>
> Hello Steve,
>
> Before my Windows machine went south, I did luck out, using CakeWalk had no
> issues importing the complete session in Pro Tools
>
> I think
I am interested in knowing more but not ready to buy yet.
-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of
Frank Carmickle
Sent: Wednesday, May 02, 2018 11:37 AM
To: ptaccess@googlegroups.com
Subject: Re: Console 1 & UAD
Vinny and I have
Hi Frank,
Contact this guy at UAD He should know.
Scott Greiner
Don't forget to mention VoiceOver full accessibility!
If every one on this list emails Scot I'll bet Bill will get er done!!! ;)
Scott Greiner is the product manager for Apollo!
OK?
Chuck
"God does not play
Vinny and I have been talking about this off list also. I am still wondering if
the console 1 plugin exposes the preamp trims as automatable parameters?
Maybe someone could ask Sweetwater to demo the console 1 who also has an apollo
with unison mic pres? I’m looking at you Chuck. Of course
Hi Vic,
Yeah, that's by design. The Input monitor status will be remembered but that
only pertains to audio tracks.
Slau
> On May 2, 2018, at 2:40 AM, Victor Tsaran wrote:
>
> Not sure if there is an option I'm missing, but I've been noticing that
> Protools, for example,
Hi,
I think this is by design, the track armed status will also change if you hide
a track. You might see this as a problem, or a security caution, but I haven’t
seen any preference to change the way it works by default.
Best,
John André
.
On 02 May 2018, at 08:40, Victor Tsaran
Not sure if there is an option I'm missing, but I've been noticing that
Protools, for example, does not remember the "armed" state of a track after
reloading a session.
Is there a reason for why this is so or is there a preference to change
this behavior?
Thanks.
Vic
--
You received this