Re: paisting clips to different tracks

[Steve Sparrow]

ok, well i got this job done, but i’d be interested to know if there is a 
better way, all i did was send my track out to a different bus, and set the 
input of the track i wanted to paste to to receive audio from that bus. and job 
completed. How ever, is there not an simple way for future reference. 
Steve

> On 30 Aug 2015, at 7:44 am, Steve Sparrow  wrote:
> 
> Hi, can someone give some instruction on the best way of doing this. 
> I am wanting to paiste some audio from one track, on to another track. From 
> what i can see i can easily paist information around within one track, but i 
> can’t seem to just select another track and paste my audio from a different 
> track on to it. if this is not possible how do i do this quickly. or do i 
> have to go through the process of bouncing down the track and reimporting.
> Steve
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

paisting clips to different tracks

[Steve Sparrow]

Hi, can someone give some instruction on the best way of doing this. 
I am wanting to paiste some audio from one track, on to another track. From 
what i can see i can easily paist information around within one track, but i 
can’t seem to just select another track and paste my audio from a different 
track on to it. if this is not possible how do i do this quickly. or do i have 
to go through the process of bouncing down the track and reimporting.
Steve

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bohemian Rhapsody?

[Chris Smart]

It's even on youtube.
At 03:58 PM 8/29/2015, you wrote:
it's the actual multitrack from
the sessions. fun to play around with, hear parts isolated etc. There's
some Stevie Wonder floating around too, complete with hearing flipping
and rocking to the beat. LOL
At 10:50 AM 8/29/2015, you wrote:
Oh, ok, I thought
it was basically a demo session or something.
 
Sorry for the misunderstanding.
 
Chris.
 

- Original Message - 
From: Slau Halatyn 
To:
ptaccess@googlegroups.com 
Sent: Saturday, August 29, 2015 9:12 AM
Subject: Re: Bohemian Rhapsody?

The Bohemian Rhapsody multitracks have been circulating for at least
a decade. Google is your friend. 

On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland

wrote:

How do I get the Bohemian Rhapsody session for
PT12?  By the way Slau makes it sound in his recording, it's
something we all should have.
 
Chris.
 

-- 
You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.
---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use! 
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.

---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bohemian Rhapsody?

['ashley cox' via Pro Tools Accessibility]

There’s some beatles floating around too including most of SGT Pepper which is 
fascinating to play with.

> On 29 Aug 2015, at 20:58, Chris Smart  wrote:
> 
> it's the actual multitrack from the sessions. fun to play around with, hear 
> parts isolated etc. There's some Stevie Wonder floating around too, complete 
> with hearing flipping and rocking to the beat. LOL
> 
> At 10:50 AM 8/29/2015, you wrote:
>> Oh, ok, I thought it was basically a demo session or something.
>>  
>> Sorry for the misunderstanding.
>>  
>> Chris.
>>  
>> - Original Message - 
>> From: Slau Halatyn  
>> To: ptaccess@googlegroups.com  
>> Sent: Saturday, August 29, 2015 9:12 AM
>> Subject: Re: Bohemian Rhapsody?
>> 
>> The Bohemian Rhapsody multitracks have been circulating for at least a 
>> decade. Google is your friend. 
>> 
>> On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland 
>> mailto:clgillan...@gmail.com>> wrote:
>> 
>>> How do I get the Bohemian Rhapsody session for PT12?  By the way Slau makes 
>>> it sound in his recording, it's something we all should have.
>>>  
>>> Chris.
>>>  
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> .
>>> For more options, visit https://groups.google.com/d/optout 
>>> .
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
> --- Learn to meditate and train your brain with Muse, the first lab-grade EEG 
> biofeedback headband for home use! 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bohemian Rhapsody?

[Christopher-Mark Gilland]

Coolness!  I'll definitely have to Google it later today.  Right now, I am 
dealing with some personal matters which I'm not going to go into, but they've 
left me emotionally and even physically a little bit drained.  I'll be ok.  I 
just am trying to take today nice and easy, and try to calm down a bit.

Chris.

  - Original Message - 
  From: Chris Smart 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 3:58 PM
  Subject: Re: Bohemian Rhapsody?


  it's the actual multitrack from the sessions. fun to play around with, hear 
parts isolated etc. There's some Stevie Wonder floating around too, complete 
with hearing flipping and rocking to the beat. LOL

  At 10:50 AM 8/29/2015, you wrote:

Oh, ok, I thought it was basically a demo session or something.
 
Sorry for the misunderstanding.
 
Chris.
 

  - Original Message - 

  From: Slau Halatyn 

  To: ptaccess@googlegroups.com 

  Sent: Saturday, August 29, 2015 9:12 AM

  Subject: Re: Bohemian Rhapsody?


  The Bohemian Rhapsody multitracks have been circulating for at least a 
decade. Google is your friend. 


  On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland 
 wrote:


How do I get the Bohemian Rhapsody session for PT12?  By the way Slau 
makes it sound in his recording, it's something we all should have.



Chris.




-- 

You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


  -- 

  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.

  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

  For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  --- Learn to meditate and train your brain with Muse, the first lab-grade EEG 
biofeedback headband for home use! 


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

No, he wasn't.  I just wanted to be sure as today, I've seemed to be stepping 
on a lot of people's toes, go figure.  LOL!  Kind a one a those rotton days.  
Oh well, on the plus side, there's always tomorrow to look forward to.

Chris.

  - Original Message - 
  From: Chris Smart 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 3:56 PM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  he doesn't seem offended at all.

  At 10:50 AM 8/29/2015, you wrote:

And again, I genuinely hope that you're not offended.  If you are, then I 
really am sorry.  No, really, seriously, I am.  I only was trying to ascertain 
what the deal was with that.  Thank you for better explaining.

Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Saturday, August 29, 2015 9:10 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Only testers have beta licenses and pre-release licenses on their iLoks.
I revealed absolutely nothing about Pro Tools itself and spoke only of 
accessibility improvements so you needn't concern yourself with my NDA. I clear 
everything I reveal with the folks at Avid. Just wanted to show people in 
context rather than in a list of text.

Slau

On Aug 29, 2015, at 6:26 AM, Christopher-Mark Gilland 
 wrote:


  Can we get the release candidate then, or is that something only you have 
since you're a beta tester?  If the ladder, then may I ask something with all 
due respect?  I don't mean to make this sound like I'm cutting you down. I'm 
actually asking this totally as an ignorant question.  I really truely may be 
failing to realize something, and if that is the case, then I'd first like to 
apologize directly to you even before I make this assumption.  If we cannot get 
the release candidate, should we choose to run it, then wouldn't it be safe to 
say since you privately have it, that you kind a broke NDA by showing us those 
accessibility improvements?

  Again, I'm asking this more totally out of curiosity.  Believe me!  By no 
means is this a way to belittle, nor to chastise or put you down.  I truely do 
not know how this works, and am genuinely asking.  So I really hope that you 
don't take offense to this.  Yes, I trust you'd not break NDA, and I do know 
you better than that.  This is why I'm slightly shocked that you did show us 
this.  I thank you that you did, but I'm just wonderring.

  Chris.

  - Original Message - From: "Slau Halatyn" 
  To: 
  Sent: Friday, August 28, 2015 7:57 AM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  Avid hasn't indicated when it'll be released but it'll be soon.

  Slau

  On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:



  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.
  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 
-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  --- Learn to meditate and train your brain with Muse, the first lab-grade EEG 
biofeedback headband for home use! 


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bohemian Rhapsody?

[Chris Smart]

it's the actual multitrack from the sessions. fun to play around with,
hear parts isolated etc. There's some Stevie Wonder floating around too,
complete with hearing flipping and rocking to the beat. LOL
At 10:50 AM 8/29/2015, you wrote:
Oh, ok, I thought
it was basically a demo session or something.
 
Sorry for the misunderstanding.
 
Chris.
 


- Original Message - 

From: Slau Halatyn


To:
ptaccess@googlegroups.com


Sent: Saturday, August 29, 2015 9:12 AM

Subject: Re: Bohemian Rhapsody?

The Bohemian Rhapsody multitracks have been circulating for at least
a decade. Google is your friend. 

On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland

wrote:

How do I get the Bohemian Rhapsody session for
PT12?  By the way Slau makes it sound in his recording, it's
something we all should have.

 

Chris.

 

-- 

You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.

For more options, visit

https://groups.google.com/d/optout.

-- 

You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.

For more options, visit

https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.

---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Chris Smart]

he doesn't seem offended at all.
At 10:50 AM 8/29/2015, you wrote:
And again, I genuinely hope that
you're not offended.  If you are, then I really am sorry.  No,
really, seriously, I am.  I only was trying to ascertain what the
deal was with that.  Thank you for better explaining.
Chris.
- Original Message - From: "Slau Halatyn"

To: 
Sent: Saturday, August 29, 2015 9:10 AM
Subject: Re: new accessibility fixes in Pro Tools version 12

Only testers have beta licenses and pre-release licenses on their
iLoks.
I revealed absolutely nothing about Pro Tools itself and spoke only of
accessibility improvements so you needn't concern yourself with my NDA. I
clear everything I reveal with the folks at Avid. Just wanted to show
people in context rather than in a list of text.
Slau
On Aug 29, 2015, at 6:26 AM, Christopher-Mark Gilland
 wrote:
Can we get the release candidate
then, or is that something only you have since you're a beta
tester?  If the ladder, then may I ask something with all due
respect?  I don't mean to make this sound like I'm cutting you down.
I'm actually asking this totally as an ignorant question.  I really
truely may be failing to realize something, and if that is the case, then
I'd first like to apologize directly to you even before I make this
assumption.  If we cannot get the release candidate, should we
choose to run it, then wouldn't it be safe to say since you privately
have it, that you kind a broke NDA by showing us those accessibility
improvements?
Again, I'm asking this more totally out of curiosity.  Believe
me!  By no means is this a way to belittle, nor to chastise or put
you down.  I truely do not know how this works, and am genuinely
asking.  So I really hope that you don't take offense to this. 
Yes, I trust you'd not break NDA, and I do know you better than
that.  This is why I'm slightly shocked that you did show us
this.  I thank you that you did, but I'm just wonderring.
Chris.
- Original Message - From: "Slau Halatyn"

To: 
Sent: Friday, August 28, 2015 7:57 AM
Subject: Re: new accessibility fixes in Pro Tools version 12

Avid hasn't indicated when it'll be released but it'll be soon.
Slau
On Aug 28, 2015, at 7:06 AM, John André Lium-Netland
 wrote:

-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout. 
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.


---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: tempo is all fixed now thanks

[Chris Smart]

At 06:59 AM 8/29/2015, you wrote:
OK.  This is easy. 
Graham, A K A, The Recording Revolution, actually did a tutorial on this
very thing.
Basically, if I am understanding correctly how he did this, you want to
select the part of the song on your timeline ruler where you want the
tempo to change.  Then you're gonna go into your tempo window, and
move the tempo where you wish for it to be.  That's it. 
Provided you have a selection made, it should work.  I think the
conductor has to be on though.
Chris.
- Original Message - From: "Chad Baker"

To: 
Sent: Friday, August 28, 2015 12:21 PM
Subject: tempo is all fixed now thanks
Isn't Graham great?
His current six-week series, mixing as much of a song in an hour as
possible is really a great reminder to go with your gut, have a sonic
picture for a song in mind at the outset, and go for it. Also, he's great
at reminding us all about first principles, things like doing a lot of
the mixing in mono, especially EQ!
 

hi slau that worked thanks now
one quick question
i am recording a friend’s metal band and there tempos change measure to
measure
not sure what all those types of tempos like parabolic and linear
mean
i just want to input different tempos for the different measures that
they want
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout. 
-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.

---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Chris Smart]

LOL Where do you get your energy from and can I have some?
Translation of the below: Can we get the release candidate? Did you break
your NDA with Avid?
When I say energy, and this may be totally ignorant so I apologize in
advance because I honestly do not know, I mean manic.
At 06:26 AM 8/29/2015, you wrote:
Can we get the release candidate
then, or is that something only you have since you're a beta
tester?  If the ladder, then may I ask something with all due
respect?  I don't mean to make this sound like I'm cutting you down.
I'm actually asking this totally as an ignorant question.  I really
truely may be failing to realize something, and if that is the case, then
I'd first like to apologize directly to you even before I make this
assumption.  If we cannot get the release candidate, should we
choose to run it, then wouldn't it be safe to say since you privately
have it, that you kind a broke NDA by showing us those accessibility
improvements?
Again, I'm asking this more totally out of curiosity.  Believe
me!  By no means is this a way to belittle, nor to chastise or put
you down.  I truely do not know how this works, and am genuinely
asking.  So I really hope that you don't take offense to this. 
Yes, I trust you'd not break NDA, and I do know you better than
that.  This is why I'm slightly shocked that you did show us
this.  I thank you that you did, but I'm just wonderring.


---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Chris Smart]

people are using the stand-alone app, not plug-in
instantiations.
At 11:15 PM 8/28/2015, you wrote:
And, I hate to bust
people's bubble, but it must not be accessible, seeing that I brought the
d-noiser plugin up on an insert in PT 12.3, and no matter what I did,
regardless which control/parameter I moved, I heard absolutely no changed
result, and believe me, I may not have very sensitive ears, but I moved
each control individually to hear the effect, and buddy, when I say move,
damn it, I mean move!  I cranked the hell! outta those things and
also knocked them the other way, so far down they were practically way in
the negative values, and I mean way! in the negatives.  So
either I'm stupid, the plugin isn't working, or the thing's a piece of
crap.  Probably the second of the 3.
 
Chris.
 


- Original Message - 

From: Steve Martin


To:
ptaccess@googlegroups.com


Sent: Thursday, August 27, 2015 10:54 PM

Subject: Re: Isotope RX4?

100% accessible? Are you able to work with the spectrogram and
etc?

On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso

wrote:

RX4 has his stand alone app 100% accessible. I use the advanced
version but for demonising purposes the standard will make the job.



On Aug 27, 2015, at 18:29, Christopher-Mark Gilland

wrote:

Guys,

 

I have a cassette tape that I'm trying to remove a
major! and I do mean major! hiss from.  It's me as a child, and it
has some of the worst quality tape recording audio I've ever heard. 
No doubt, my parents must a recorded this on a real el cheapo tape
recorder.  It's horriffic!  E Q isn't gonna get rid a
this.

 

Anyway, has anyone used either the Isotope RX4 Standard
or Advanced, preferably Standard plugins with PT?  If so, are they
even somewhat accessible?  I'm thinking I'll probably use the
D-Noise module.

 

If not that accessible, if I just wanna see, though
probably not advisable, if it just naturally with no tweaking would make
it a little better, do you think just popping it on an insert and being
done with it would possibly even get rid of the slightest bit, even if
not enough to be desirable?

 

If it's not accessible, does anyone have custom made
presets that'll help me?  If not, what other plugs would be
accessible that may help with this.  It's not really a hum type of
hiss.  It's more the type background air noise kind a hiss you heard
when recording on real cheap consumer grade little portable pocket tape
recorders with the built in mikes.  Like something you'd buy at
Radio Shaq or Circuit Shitty.

 

Chris.


-- 

You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.

For more options, visit

https://groups.google.com/d/optout.

-- 

You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.

For more options, visit

https://groups.google.com/d/optout.

-- 

You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.

To unsubscribe from this group and stop receiving emails from it,
send an email to

ptaccess+unsubscr...@googlegroups.com.

For more options, visit

https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to

ptaccess+unsubscr...@googlegroups.com.
For more options, visit

https://groups.google.com/d/optout.

---

Learn to meditate and train your brain with Muse, the first lab-grade EEG
biofeedback headband for home use!




-- 
You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compressor parameters reset back to defaults whenever I close the plugin window

[Christopher-Mark Gilland]

Matt, this table which you speak of... where in each plugin would one find 
it now that it is apparently accessible?


Chris.

- Original Message - 
From: "Matt Diemert" 

To: 
Sent: Saturday, August 29, 2015 12:57 PM
Subject: Re: Compressor parameters reset back to defaults whenever I close 
the plugin window



We are in the process of updating knots and bolts. However, in ProTools 10 
there was no access to the table within the plug-in to add parameters to be 
automated, so the only option at that point, was to ensure that every 
parameter was automated. Obviously, this meant checking that checkbox.


Sent from my iPhone


On Aug 29, 2015, at 11:17 AM, Robin Kipp  wrote:

Hello Slau and Chris,
thanks for that!
Yes, the problem here was in fact the ‚plugin controls default to 
auto-enabled‘ checkbox within the PT settings. I had turned this on 
because it was highly recommended by Matt and Rob in the PT With Speech 
tutorial, but I guess things have changed here in PT 11. Anyways, looks 
like I’m good to go now as all my settings are now being applied properly!

Many thanks,
Robin

Am 29.08.2015 um 01:30 schrieb Slau Halatyn :

Hi Robin,

The first thing I would check is under the Mixing tab of the Preferences 
dialog under the Setup menu. There's a checkbox to have plug-in 
automation default to the enabled state. The first thing I would do is 
make sure it's unchecked.


Second, I would make sure plug-in automation is not enabled in the 
Automation window. If it was enabled and, if at any point, your track was 
in Automation Write mode, you will have had some parameters written that 
will revert the plug-in parameters to their default or preset state.


To tell you the truth, I'm not sure if simply even having the checkbox 
checked once at the outset will screw up things for the current session. 
I've never had this issue but it's the kind of thing that, once you're 
aware of it, having that checkbox unchecked will help in the future.


To see if you do have any automation parameters written, go to the Edit 
window and interact with the track and go to the button that says 
"waveform." This is the track view display button. Pop it open and see if 
there's anything listed under "plug-in." If so, I'll chime in with 
further options.


best,

Slau


On Aug 28, 2015, at 6:49 PM, Robin Kipp  wrote:

Hi all!
So… By now I made it to the mixing module of the PRo Tools With Speech 
tutorials and up until this point everything went very smoothly! 
However, I’m now experiencing a rather frustrating problem… So, 
Basically I’ve got this vocal track to which I applied the BF-76 
compressor using inserts. Now, when I VO space on that insert to bring 
up the plugin window, I can tell that there’s quite a difference in how 
things are labeled from the tutorial, probably because Matt and Rob are 
using PT 10 whereas I’m on PT 11. Even though the labels are a little 
confusing, I could locate the relevant parameters without much trouble. 
Now, when I change the input and output values, I noticed that those 
parameters stay at whatever value I set them to even when I close that 
floating window. However, there is an annoying issue when I change 
either the attack, release or ratio parameters. I can interact with and 
modify them as usual, and if I stop interacting, move the focus 
elsewhere within the plugin window and then return they will still have 
the same values. However, and this is where it gets annoying, I’ve found 
that as soon as I move the VO focus out of the plugin window, either by 
closing the window or by simply selecting a different window, as soon as 
I move the VO focus back to the compressor I find that the parameters 
simply reverted back to their defaults, e.g. attack 3.0, release 5.1 and 
a ratio of 4:1… I’ve tried this a couple times now, relaunched PT, tried 
setting those parameters with cursor tracking disabled - yet I’m still 
seeing the same annoying behavior! I really really hope that there’s a 
simple solution for that, or maybe it’s just a case of me doing 
something wrong due to lack of experience!
Either way, if anyone of you could point me in the right direction I 
would greatly appreciate that!

Many thanks,
Robin

--
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send a

Re: Compressor parameters reset back to defaults whenever I close the plugin window

[Matt Diemert]

We are in the process of updating knots and bolts. However, in ProTools 10 
there was no access to the table within the plug-in to add parameters to be 
automated, so the only option at that point, was to ensure that every parameter 
was automated. Obviously, this meant checking that checkbox. 

Sent from my iPhone

> On Aug 29, 2015, at 11:17 AM, Robin Kipp  wrote:
> 
> Hello Slau and Chris,
> thanks for that!
> Yes, the problem here was in fact the ‚plugin controls default to 
> auto-enabled‘ checkbox within the PT settings. I had turned this on because 
> it was highly recommended by Matt and Rob in the PT With Speech tutorial, but 
> I guess things have changed here in PT 11. Anyways, looks like I’m good to go 
> now as all my settings are now being applied properly!
> Many thanks,
> Robin
>> Am 29.08.2015 um 01:30 schrieb Slau Halatyn :
>> 
>> Hi Robin,
>> 
>> The first thing I would check is under the Mixing tab of the Preferences 
>> dialog under the Setup menu. There's a checkbox to have plug-in automation 
>> default to the enabled state. The first thing I would do is make sure it's 
>> unchecked.
>> 
>> Second, I would make sure plug-in automation is not enabled in the 
>> Automation window. If it was enabled and, if at any point, your track was in 
>> Automation Write mode, you will have had some parameters written that will 
>> revert the plug-in parameters to their default or preset state.
>> 
>> To tell you the truth, I'm not sure if simply even having the checkbox 
>> checked once at the outset will screw up things for the current session. 
>> I've never had this issue but it's the kind of thing that, once you're aware 
>> of it, having that checkbox unchecked will help in the future.
>> 
>> To see if you do have any automation parameters written, go to the Edit 
>> window and interact with the track and go to the button that says 
>> "waveform." This is the track view display button. Pop it open and see if 
>> there's anything listed under "plug-in." If so, I'll chime in with further 
>> options.
>> 
>> best,
>> 
>> Slau
>> 
>>> On Aug 28, 2015, at 6:49 PM, Robin Kipp  wrote:
>>> 
>>> Hi all!
>>> So… By now I made it to the mixing module of the PRo Tools With Speech 
>>> tutorials and up until this point everything went very smoothly! However, 
>>> I’m now experiencing a rather frustrating problem… So, Basically I’ve got 
>>> this vocal track to which I applied the BF-76 compressor using inserts. 
>>> Now, when I VO space on that insert to bring up the plugin window, I can 
>>> tell that there’s quite a difference in how things are labeled from the 
>>> tutorial, probably because Matt and Rob are using PT 10 whereas I’m on PT 
>>> 11. Even though the labels are a little confusing, I could locate the 
>>> relevant parameters without much trouble. Now, when I change the input and 
>>> output values, I noticed that those parameters stay at whatever value I set 
>>> them to even when I close that floating window. However, there is an 
>>> annoying issue when I change either the attack, release or ratio 
>>> parameters. I can interact with and modify them as usual, and if I stop 
>>> interacting, move the focus elsewhere within the plugin window and then 
>>> return they will still have the same values. However, and this is where it 
>>> gets annoying, I’ve found that as soon as I move the VO focus out of the 
>>> plugin window, either by closing the window or by simply selecting a 
>>> different window, as soon as I move the VO focus back to the compressor I 
>>> find that the parameters simply reverted back to their defaults, e.g. 
>>> attack 3.0, release 5.1 and a ratio of 4:1… I’ve tried this a couple times 
>>> now, relaunched PT, tried setting those parameters with cursor tracking 
>>> disabled - yet I’m still seeing the same annoying behavior! I really really 
>>> hope that there’s a simple solution for that, or maybe it’s just a case of 
>>> me doing something wrong due to lack of experience!
>>> Either way, if anyone of you could point me in the right direction I would 
>>> greatly appreciate that!
>>> Many thanks,
>>> Robin
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googleg

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

Cool.

Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Saturday, August 29, 2015 11:26 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


No offense taken.

On Aug 29, 2015, at 10:50 AM, Christopher-Mark Gilland 
 wrote:


And again, I genuinely hope that you're not offended.  If you are, then I 
really am sorry.  No, really, seriously, I am.  I only was trying to 
ascertain what the deal was with that.  Thank you for better explaining.


Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Saturday, August 29, 2015 9:10 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Only testers have beta licenses and pre-release licenses on their iLoks.
I revealed absolutely nothing about Pro Tools itself and spoke only of 
accessibility improvements so you needn't concern yourself with my NDA. I 
clear everything I reveal with the folks at Avid. Just wanted to show 
people in context rather than in a list of text.


Slau

On Aug 29, 2015, at 6:26 AM, Christopher-Mark Gilland 
 wrote:


Can we get the release candidate then, or is that something only you have 
since you're a beta tester?  If the ladder, then may I ask something with 
all due respect?  I don't mean to make this sound like I'm cutting you 
down. I'm actually asking this totally as an ignorant question.  I really 
truely may be failing to realize something, and if that is the case, then 
I'd first like to apologize directly to you even before I make this 
assumption.  If we cannot get the release candidate, should we choose to 
run it, then wouldn't it be safe to say since you privately have it, that 
you kind a broke NDA by showing us those accessibility improvements?


Again, I'm asking this more totally out of curiosity.  Believe me!  By no 
means is this a way to belittle, nor to chastise or put you down.  I 
truely do not know how this works, and am genuinely asking.  So I really 
hope that you don't take offense to this.  Yes, I trust you'd not break 
NDA, and I do know you better than that.  This is why I'm slightly 
shocked that you did show us this.  I thank you that you did, but I'm 
just wonderring.


Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Friday, August 28, 2015 7:57 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Avid hasn't indicated when it'll be released but it'll be soon.

Slau

On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:






--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compressor parameters reset back to defaults whenever I close the plugin window

[Christopher-Mark Gilland]

You are more than welcome.  Please do let us know if you need any further 
help.


Chris.

- Original Message - 
From: "Robin Kipp" 

To: 
Sent: Saturday, August 29, 2015 11:17 AM
Subject: Re: Compressor parameters reset back to defaults whenever I close 
the plugin window



Hello Slau and Chris,
thanks for that!
Yes, the problem here was in fact the ‚plugin controls default to 
auto-enabled‘ checkbox within the PT settings. I had turned this on because 
it was highly recommended by Matt and Rob in the PT With Speech tutorial, 
but I guess things have changed here in PT 11. Anyways, looks like I’m good 
to go now as all my settings are now being applied properly!

Many thanks,
Robin

Am 29.08.2015 um 01:30 schrieb Slau Halatyn :

Hi Robin,

The first thing I would check is under the Mixing tab of the Preferences 
dialog under the Setup menu. There's a checkbox to have plug-in automation 
default to the enabled state. The first thing I would do is make sure it's 
unchecked.


Second, I would make sure plug-in automation is not enabled in the 
Automation window. If it was enabled and, if at any point, your track was 
in Automation Write mode, you will have had some parameters written that 
will revert the plug-in parameters to their default or preset state.


To tell you the truth, I'm not sure if simply even having the checkbox 
checked once at the outset will screw up things for the current session. 
I've never had this issue but it's the kind of thing that, once you're 
aware of it, having that checkbox unchecked will help in the future.


To see if you do have any automation parameters written, go to the Edit 
window and interact with the track and go to the button that says 
"waveform." This is the track view display button. Pop it open and see if 
there's anything listed under "plug-in." If so, I'll chime in with further 
options.


best,

Slau

On Aug 28, 2015, at 6:49 PM, Robin Kipp  wrote:


Hi all!
So… By now I made it to the mixing module of the PRo Tools With Speech 
tutorials and up until this point everything went very smoothly! However, 
I’m now experiencing a rather frustrating problem… So, Basically I’ve got 
this vocal track to which I applied the BF-76 compressor using inserts. 
Now, when I VO space on that insert to bring up the plugin window, I can 
tell that there’s quite a difference in how things are labeled from the 
tutorial, probably because Matt and Rob are using PT 10 whereas I’m on PT 
11. Even though the labels are a little confusing, I could locate the 
relevant parameters without much trouble. Now, when I change the input 
and output values, I noticed that those parameters stay at whatever value 
I set them to even when I close that floating window. However, there is 
an annoying issue when I change either the attack, release or ratio 
parameters. I can interact with and modify them as usual, and if I stop 
interacting, move the focus elsewhere within the plugin window and then 
return they will still have the same values. However, and this is where 
it gets annoying, I’ve found that as soon as I move the VO focus out of 
the plugin window, either by closing the window or by simply selecting a 
different window, as soon as I move the VO focus back to the compressor I 
find that the parameters simply reverted back to their defaults, e.g. 
attack 3.0, release 5.1 and a ratio of 4:1… I’ve tried this a couple 
times now, relaunched PT, tried setting those parameters with cursor 
tracking disabled - yet I’m still seeing the same annoying behavior! I 
really really hope that there’s a simple solution for that, or maybe it’s 
just a case of me doing something wrong due to lack of experience!
Either way, if anyone of you could point me in the right direction I 
would greatly appreciate that!

Many thanks,
Robin

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compressor parameters reset back to defaults whenever I close the plugin window

[Robin Kipp]

Hello Slau and Chris,
thanks for that!
Yes, the problem here was in fact the ‚plugin controls default to auto-enabled‘ 
checkbox within the PT settings. I had turned this on because it was highly 
recommended by Matt and Rob in the PT With Speech tutorial, but I guess things 
have changed here in PT 11. Anyways, looks like I’m good to go now as all my 
settings are now being applied properly!
Many thanks,
Robin
> Am 29.08.2015 um 01:30 schrieb Slau Halatyn :
> 
> Hi Robin,
> 
> The first thing I would check is under the Mixing tab of the Preferences 
> dialog under the Setup menu. There's a checkbox to have plug-in automation 
> default to the enabled state. The first thing I would do is make sure it's 
> unchecked.
> 
> Second, I would make sure plug-in automation is not enabled in the Automation 
> window. If it was enabled and, if at any point, your track was in Automation 
> Write mode, you will have had some parameters written that will revert the 
> plug-in parameters to their default or preset state.
> 
> To tell you the truth, I'm not sure if simply even having the checkbox 
> checked once at the outset will screw up things for the current session. I've 
> never had this issue but it's the kind of thing that, once you're aware of 
> it, having that checkbox unchecked will help in the future.
> 
> To see if you do have any automation parameters written, go to the Edit 
> window and interact with the track and go to the button that says "waveform." 
> This is the track view display button. Pop it open and see if there's 
> anything listed under "plug-in." If so, I'll chime in with further options.
> 
> best,
> 
> Slau
> 
> On Aug 28, 2015, at 6:49 PM, Robin Kipp  wrote:
> 
>> Hi all!
>> So… By now I made it to the mixing module of the PRo Tools With Speech 
>> tutorials and up until this point everything went very smoothly! However, 
>> I’m now experiencing a rather frustrating problem… So, Basically I’ve got 
>> this vocal track to which I applied the BF-76 compressor using inserts. Now, 
>> when I VO space on that insert to bring up the plugin window, I can tell 
>> that there’s quite a difference in how things are labeled from the tutorial, 
>> probably because Matt and Rob are using PT 10 whereas I’m on PT 11. Even 
>> though the labels are a little confusing, I could locate the relevant 
>> parameters without much trouble. Now, when I change the input and output 
>> values, I noticed that those parameters stay at whatever value I set them to 
>> even when I close that floating window. However, there is an annoying issue 
>> when I change either the attack, release or ratio parameters. I can interact 
>> with and modify them as usual, and if I stop interacting, move the focus 
>> elsewhere within the plugin window and then return they will still have the 
>> same values. However, and this is where it gets annoying, I’ve found that as 
>> soon as I move the VO focus out of the plugin window, either by closing the 
>> window or by simply selecting a different window, as soon as I move the VO 
>> focus back to the compressor I find that the parameters simply reverted back 
>> to their defaults, e.g. attack 3.0, release 5.1 and a ratio of 4:1… I’ve 
>> tried this a couple times now, relaunched PT, tried setting those parameters 
>> with cursor tracking disabled - yet I’m still seeing the same annoying 
>> behavior! I really really hope that there’s a simple solution for that, or 
>> maybe it’s just a case of me doing something wrong due to lack of experience!
>> Either way, if anyone of you could point me in the right direction I would 
>> greatly appreciate that!
>> Many thanks,
>> Robin
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Christopher-Mark Gilland]

Actually, I didn't see any.  I did try the stand alone app though, and though 
it contains basically the same exact controls which totally are accessible with 
Voiceover in PT, they actually do! work with the stand alone app.  This said, I 
really, with the trial version, wasn't able to really do much with it try as I 
may.  It's killing the noise, but it's also killing a lot of the frequencies of 
the voice as well, which is making my mom's voice on the thing sound really 
really flangy.  I tried for about 2 hours non stop to work with it, but even 
after reading the documentation of the thing, I just can't get it where it's 
satisfactory.  I got it somewhat better, but it's still not where I'd like it.  
LOL!

Chris.

  - Original Message - 
  From: Steve Martin 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 10:34 AM
  Subject: Re: Isotope RX4?


  did you try the presets and see if they work?

On Aug 29, 2015, at 7:13 AM, Christopher-Mark Gilland 
 wrote:


If nothing else, can you at least, even if not the result I need tell me 
something I can do that regardless what the recording is, regardless how much 
noise there is, I could way over exagerate to at least! test if it's even 
working at all?

Chris.

  - Original Message - 
  From: Steve Martin
  To: ptaccess@googlegroups.com
  Sent: Saturday, August 29, 2015 12:39 AM
  Subject: Re: Isotope RX4?


  May he may have overstepped by saying was 100% accessible its still quite 
useable and sufficient to resolve the issue chris wants to use it on as 
described here. I am not sure why you are not having any luck with it as a plug 
in as i have used it as an insert in Reaper and PT,However for best results you 
really want to use the standalone version for these task and then import the 
cleaned file into PT. the clean up process is very processor intensive and you 
wouldn’t want it running in a session the whole time. 

On Aug 28, 2015, at 11:21 PM, Daniel Contreras 
 wrote:


I think he was referring to the stand alone version chris. 

Daniel Contreras 

On Aug 28, 2015, at 10:15 PM, Christopher-Mark Gilland 
 wrote:


  And, I hate to bust people's bubble, but it must not be accessible, 
seeing that I brought the d-noiser plugin up on an insert in PT 12.3, and no 
matter what I did, regardless which control/parameter I moved, I heard 
absolutely no changed result, and believe me, I may not have very sensitive 
ears, but I moved each control individually to hear the effect, and buddy, when 
I say move, damn it, I mean move!  I cranked the hell! outta those things and 
also knocked them the other way, so far down they were practically way in the 
negative values, and I mean way! in the negatives.  So either I'm stupid, 
the plugin isn't working, or the thing's a piece of crap.  Probably the second 
of the 3.

  Chris.

- Original Message - 
From: Steve Martin
To: ptaccess@googlegroups.com
Sent: Thursday, August 27, 2015 10:54 PM
Subject: Re: Isotope RX4?


100% accessible? Are you able to work with the spectrogram and etc?

  On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso 
 wrote:


  RX4 has his stand alone app 100% accessible. I use the advanced 
version but for demonising purposes the standard will make the job.




On Aug 27, 2015, at 18:29, Christopher-Mark Gilland 
 wrote:


Guys,

I have a cassette tape that I'm trying to remove a major! and I 
do mean major! hiss from.  It's me as a child, and it has some of the worst 
quality tape recording audio I've ever heard.  No doubt, my parents must a 
recorded this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't 
gonna get rid a this.

Anyway, has anyone used either the Isotope RX4 Standard or 
Advanced, preferably Standard plugins with PT?  If so, are they even somewhat 
accessible?  I'm thinking I'll probably use the D-Noise module.

If not that accessible, if I just wanna see, though probably 
not advisable, if it just naturally with no tweaking would make it a little 
better, do you think just popping it on an insert and being done with it would 
possibly even get rid of the slightest bit, even if not enough to be desirable?

If it's not accessible, does anyone have custom made presets 
that'll help me?  If not, what other plugs would be accessible that may help 
with this.  It's not really a hum type of hiss.  It's more the type background 
air noise kind a hiss you heard when recording on real cheap consumer grade 
little portable pocket tape recorders with the built in mikes.  Like something 
you'd buy at Radio Shaq or Circuit Shitty.

Chris.


-- 
You received this message because you are subscribed to the 
G

Re: Hopefully a basic, easy to solve plugin automation problem

[Christopher-Mark Gilland]

OK, no worries, just wanted to help, if needed.

Take care.

Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Saturday, August 29, 2015 9:14 AM
Subject: Re: Hopefully a basic, easy to solve plugin automation problem


No need to test any further. It's been confirmed as an issue in both 11 and 
12. Static values can be written but nothing can be written in real time. 
It's in the system but won't be fixed for the upcoming release. At some 
point, though, it'll be fixed.


Slau

On Aug 29, 2015, at 6:30 AM, Christopher-Mark Gilland 
 wrote:


Slau, like I said, with Auto-Tune Native 7, and PT 10.0, yes.  I was 
definitely able to automate things with changing the key value, or the 
scale value, so yes.  I have with no surface done this very very 
effectively, and very consistently, and it worked like a dream.  It wasn't 
until I updated to both PT12 and then had to update to the AAX format of 
Auto-Tune, which is now Native 8, that I began to see this problem.  I 
confess I've not tested this with other plugs that I remember, so I don't 
know if this is A T specific, or if this issue would happen all the way 
across the board.


If you'd like to have me test this for your data collection further, then 
just tell me step by step what you'd like me to do, and I'll report back 
to you all my results.


Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Friday, August 28, 2015 8:06 AM
Subject: Re: Hopefully a basic, easy to solve plugin automation problem


Actually, it's conceivable that the VoiceOver interaction isn't working 
for automation and perhaps never worked. Has anyone successfully automated 
a plug-in parameter on the list? Let me say, and I've said this before, I 
can't fathom how any VoiceOver user can begin to use Pro tools in a 
serious fashion without a control surface. I've only used automation with 
with control surfaces and, of course, it works fine. There was a similar 
issue of VoiceOver changing fader values correctly but, when faders were 
grouped, things didn't work correctly when changing levels with VoiceOver. 
Again, with a control surface, it's been a non-issue. It's possible that 
we're seeing the same thing here. Needless to say, if that's the case 
here, that wouldn't be fixed in the upcoming release because there's no 
time.


As I mentioned, I've never attempted any plug-in automation without a 
control surface and, clearly, none of the beta testers have ever thought 
to try it either and there was never a bug report logged on this issue if, 
in fact, it is a current issue. Someone will need to reproduce the 
results. I know others without control surfaces have had difficulties but 
it'll have to be replicated in a controlled manner and logged. I'll see if 
I can do that in the near future.


Slau

On Aug 28, 2015, at 7:34 AM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


Sorry, pressed the wrong button and sent the previous email again. 
ProTools is playing with my sanity levels. Here's what I meant to send.
It seems impossible to automate plugins using the mac keyboard. My friend 
has just done it with the trackpad and it works, but doing it with 
Voice-Over completely fails.


If anyone feels saintly enough to have a go at recreating these steps and 
telling me what they experience, or helping to put me straight on this, 
then that would be great.


I put the track on autowrite, I enable the plugin control I want for 
automation. I change the control by interacting with it and using the 
arrow keys. The change occurs; I know this becuase I can hear it, and I’ve 
had sighted clarification. I then stop the project, put the track on 
read, and play the track at the point where the automation should be 
kicking in. Nothing happens. The plugin control just resets to where it 
was before I started, and there is no automation written.


My sighted friend manages to do exactly the same as I am doing only using 
the mouse to automate, and it works fine. Sickeningly, he is also able to 
make smoother changes simply with the mouse, but that’s another story.


I have the box unticked besides the auto enable plugins for automation 
option in the automation part of the mix tab in preferences.


I really don’t think ProTools wants me to have automation control over 
plugins. Surely this can’t be an accessibility issue, as it seems like a 
massive flaw. I tried this once a few months ago using PT11 and it didn’t 
work then either, but I was too busy to try anything at that time, and 
assumed I was diong something wrong.


Thanks folks. Let’s hope this isn’t another one to add the unsolved major 
problems list.



Sent from my iPhone


On 28 Aug 2015, at 03:18, Steve Martin  wrote:

do you change the automation status from write to read or something else 
before playing it back?
On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


OK friends, what am I doing wrong now? I’m trying to automate certain 
plugin paramet

Re: Bohemian Rhapsody?

[Christopher-Mark Gilland]

Oh, ok, I thought it was basically a demo session or something.

Sorry for the misunderstanding.

Chris.

  - Original Message - 
  From: Slau Halatyn 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 9:12 AM
  Subject: Re: Bohemian Rhapsody?


  The Bohemian Rhapsody multitracks have been circulating for at least a 
decade. Google is your friend.


  On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland 
 wrote:


How do I get the Bohemian Rhapsody session for PT12?  By the way Slau makes 
it sound in his recording, it's something we all should have.

Chris.



-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

And again, I genuinely hope that you're not offended.  If you are, then I 
really am sorry.  No, really, seriously, I am.  I only was trying to 
ascertain what the deal was with that.  Thank you for better explaining.


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Saturday, August 29, 2015 9:10 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Only testers have beta licenses and pre-release licenses on their iLoks.
I revealed absolutely nothing about Pro Tools itself and spoke only of 
accessibility improvements so you needn't concern yourself with my NDA. I 
clear everything I reveal with the folks at Avid. Just wanted to show people 
in context rather than in a list of text.


Slau

On Aug 29, 2015, at 6:26 AM, Christopher-Mark Gilland 
 wrote:


Can we get the release candidate then, or is that something only you have 
since you're a beta tester?  If the ladder, then may I ask something with 
all due respect?  I don't mean to make this sound like I'm cutting you 
down. I'm actually asking this totally as an ignorant question.  I really 
truely may be failing to realize something, and if that is the case, then 
I'd first like to apologize directly to you even before I make this 
assumption.  If we cannot get the release candidate, should we choose to 
run it, then wouldn't it be safe to say since you privately have it, that 
you kind a broke NDA by showing us those accessibility improvements?


Again, I'm asking this more totally out of curiosity.  Believe me!  By no 
means is this a way to belittle, nor to chastise or put you down.  I 
truely do not know how this works, and am genuinely asking.  So I really 
hope that you don't take offense to this.  Yes, I trust you'd not break 
NDA, and I do know you better than that.  This is why I'm slightly shocked 
that you did show us this.  I thank you that you did, but I'm just 
wonderring.


Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Friday, August 28, 2015 7:57 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Avid hasn't indicated when it'll be released but it'll be soon.

Slau

On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:






--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Steve Martin]

As what seems at times the only other person around here that works with loops, 
there was not an easily accessible way to do this in pro tools since the 
workspace windows was inaccessible at one point. I since started using Reaper  
and haven’t looked at the v12 of pro tools yet to see how useable the Workspace 
window is. That being said, Not sure how it would work in ProTools First either 
as its a stripped down and in very little ways similar to the full version of 
pro tools. So unfortunately you will probably have to read the manual on this 
one.

> On Aug 28, 2015, at 10:50 PM, Dionipher Herrera  wrote:
> 
> i am using the pro tools 12 first, can somebody help me how to add loops?
> 
> On Friday, August 28, 2015 at 2:24:57 AM UTC+2, Slau Halatyn wrote:
> Since the folks over at the Logic Accessibility have a whole lot to be 
> excited about with the new Logic update, I figured it was time to share the 
> news about the significant progress made on the Pro Tools front. I thought it 
> might be helpful to outline the new accessibility fixes in the upcoming Pro 
> Tools version 12. We've had only a handful of fixes in the last 18 months or 
> so but this time it's more like around 40 bug fixes. Many of them are subtle 
> and simple things like fixing nomenclature but some are more significant. I'm 
> attaching an mp3 that gives some examples of the changes and I talk through 
> some of the stuff. I now realize that I didn't mention a couple of things in 
> the recording like, for example, the "create Session" dialog which has been 
> improved and the "Delete Unused Playlists" dialog which now reports the 
> status of selected playlists within the table.
> 
> Anyway, in addition to attaching the mp3, here's a Drop Box link 
> 
>  to the file in case the attachment gets screwed up in the posting.
> 
> Avid has made some incredible progress this time around and I'm really 
> thrilled with the way things have moved forward. We still face challenges, of 
> course, and there are still areas like the Applications Manager that need 
> attention but things are looking up.
> 
> Enjoy,
> 
> Slau
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Steve Martin]

did you try the presets and see if they work?
> On Aug 29, 2015, at 7:13 AM, Christopher-Mark Gilland  
> wrote:
> 
> If nothing else, can you at least, even if not the result I need tell me 
> something I can do that regardless what the recording is, regardless how much 
> noise there is, I could way over exagerate to at least! test if it's even 
> working at all?
>  
> Chris.
>  
>> - Original Message - 
>> From: Steve Martin 
>> To: ptaccess@googlegroups.com 
>> Sent: Saturday, August 29, 2015 12:39 AM
>> Subject: Re: Isotope RX4?
>> 
>> May he may have overstepped by saying was 100% accessible its still quite 
>> useable and sufficient to resolve the issue chris wants to use it on as 
>> described here. I am not sure why you are not having any luck with it as a 
>> plug in as i have used it as an insert in Reaper and PT,However for best 
>> results you really want to use the standalone version for these task and 
>> then import the cleaned file into PT. the clean up process is very processor 
>> intensive and you wouldn’t want it running in a session the whole time. 
>>> On Aug 28, 2015, at 11:21 PM, Daniel Contreras >> > wrote:
>>> 
>>> I think he was referring to the stand alone version chris. 
>>> 
>>> Daniel Contreras 
>>> 
>>> On Aug 28, 2015, at 10:15 PM, Christopher-Mark Gilland 
>>> mailto:clgillan...@gmail.com>> wrote:
>>> 
 And, I hate to bust people's bubble, but it must not be accessible, seeing 
 that I brought the d-noiser plugin up on an insert in PT 12.3, and no 
 matter what I did, regardless which control/parameter I moved, I heard 
 absolutely no changed result, and believe me, I may not have very 
 sensitive ears, but I moved each control individually to hear the effect, 
 and buddy, when I say move, damn it, I mean move!  I cranked the hell! 
 outta those things and also knocked them the other way, so far down they 
 were practically way in the negative values, and I mean way! in the 
 negatives.  So either I'm stupid, the plugin isn't working, or the thing's 
 a piece of crap.  Probably the second of the 3.
  
 Chris.
  
> - Original Message - 
> From: Steve Martin 
> To: ptaccess@googlegroups.com 
> Sent: Thursday, August 27, 2015 10:54 PM
> Subject: Re: Isotope RX4?
> 
> 100% accessible? Are you able to work with the spectrogram and etc?
>> On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso 
>> mailto:jpcula...@gmail.com>> wrote:
>> 
>> RX4 has his stand alone app 100% accessible. I use the advanced version 
>> but for demonising purposes the standard will make the job.
>> 
>> 
>>> On Aug 27, 2015, at 18:29, Christopher-Mark Gilland 
>>> mailto:clgillan...@gmail.com>> wrote:
>>> 
>>> Guys,
>>>  
>>> I have a cassette tape that I'm trying to remove a major! and I do mean 
>>> major! hiss from.  It's me as a child, and it has some of the worst 
>>> quality tape recording audio I've ever heard.  No doubt, my parents 
>>> must a recorded this on a real el cheapo tape recorder.  It's 
>>> horriffic!  E Q isn't gonna get rid a this.
>>>  
>>> Anyway, has anyone used either the Isotope RX4 Standard or Advanced, 
>>> preferably Standard plugins with PT?  If so, are they even somewhat 
>>> accessible?  I'm thinking I'll probably use the D-Noise module.
>>>  
>>> If not that accessible, if I just wanna see, though probably not 
>>> advisable, if it just naturally with no tweaking would make it a little 
>>> better, do you think just popping it on an insert and being done with 
>>> it would possibly even get rid of the slightest bit, even if not enough 
>>> to be desirable?
>>>  
>>> If it's not accessible, does anyone have custom made presets that'll 
>>> help me?  If not, what other plugs would be accessible that may help 
>>> with this.  It's not really a hum type of hiss.  It's more the type 
>>> background air noise kind a hiss you heard when recording on real cheap 
>>> consumer grade little portable pocket tape recorders with the built in 
>>> mikes.  Like something you'd buy at Radio Shaq or Circuit Shitty.
>>>  
>>> Chris.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to ptaccess+unsubscr...@googlegroups.com 
>>> .
>>> For more options, visit https://groups.google.com/d/optout 
>>> .
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google 
>>

Re: Hopefully a basic, easy to solve plugin automation problem

[Slau Halatyn]

No need to test any further. It's been confirmed as an issue in both 11 and 12. 
Static values can be written but nothing can be written in real time. It's in 
the system but won't be fixed for the upcoming release. At some point, though, 
it'll be fixed.

Slau

On Aug 29, 2015, at 6:30 AM, Christopher-Mark Gilland  
wrote:

> Slau, like I said, with Auto-Tune Native 7, and PT 10.0, yes.  I was 
> definitely able to automate things with changing the key value, or the scale 
> value, so yes.  I have with no surface done this very very effectively, and 
> very consistently, and it worked like a dream.  It wasn't until I updated to 
> both PT12 and then had to update to the AAX format of Auto-Tune, which is now 
> Native 8, that I began to see this problem.  I confess I've not tested this 
> with other plugs that I remember, so I don't know if this is A T specific, or 
> if this issue would happen all the way across the board.
> 
> If you'd like to have me test this for your data collection further, then 
> just tell me step by step what you'd like me to do, and I'll report back to 
> you all my results.
> 
> Chris.
> 
> - Original Message - From: "Slau Halatyn" 
> To: 
> Sent: Friday, August 28, 2015 8:06 AM
> Subject: Re: Hopefully a basic, easy to solve plugin automation problem
> 
> 
> Actually, it's conceivable that the VoiceOver interaction isn't working for 
> automation and perhaps never worked. Has anyone successfully automated a 
> plug-in parameter on the list? Let me say, and I've said this before, I can't 
> fathom how any VoiceOver user can begin to use Pro tools in a serious fashion 
> without a control surface. I've only used automation with with control 
> surfaces and, of course, it works fine. There was a similar issue of 
> VoiceOver changing fader values correctly but, when faders were grouped, 
> things didn't work correctly when changing levels with VoiceOver. Again, with 
> a control surface, it's been a non-issue. It's possible that we're seeing the 
> same thing here. Needless to say, if that's the case here, that wouldn't be 
> fixed in the upcoming release because there's no time.
> 
> As I mentioned, I've never attempted any plug-in automation without a control 
> surface and, clearly, none of the beta testers have ever thought to try it 
> either and there was never a bug report logged on this issue if, in fact, it 
> is a current issue. Someone will need to reproduce the results. I know others 
> without control surfaces have had difficulties but it'll have to be 
> replicated in a controlled manner and logged. I'll see if I can do that in 
> the near future.
> 
> Slau
> 
> On Aug 28, 2015, at 7:34 AM, 'onlineeagle' via Pro Tools Accessibility 
>  wrote:
> 
>> Sorry, pressed the wrong button and sent the previous email again. ProTools 
>> is playing with my sanity levels. Here's what I meant to send.
>> It seems impossible to automate plugins using the mac keyboard. My friend 
>> has just done it with the trackpad and it works, but doing it with 
>> Voice-Over completely fails.
>> 
>> If anyone feels saintly enough to have a go at recreating these steps and 
>> telling me what they experience, or helping to put me straight on this, then 
>> that would be great.
>> 
>> I put the track on autowrite, I enable the plugin control I want for 
>> automation. I change the control by interacting with it and using the arrow 
>> keys. The change occurs; I know this becuase I can hear it, and I’ve had 
>> sighted clarification. I then stop the project, put the track on read, and 
>> play the track at the point where the automation should be kicking in. 
>> Nothing happens. The plugin control just resets to where it was before I 
>> started, and there is no automation written.
>> 
>> My sighted friend manages to do exactly the same as I am doing only using 
>> the mouse to automate, and it works fine. Sickeningly, he is also able to 
>> make smoother changes simply with the mouse, but that’s another story.
>> 
>> I have the box unticked besides the auto enable plugins for automation 
>> option in the automation part of the mix tab in preferences.
>> 
>> I really don’t think ProTools wants me to have automation control over 
>> plugins. Surely this can’t be an accessibility issue, as it seems like a 
>> massive flaw. I tried this once a few months ago using PT11 and it didn’t 
>> work then either, but I was too busy to try anything at that time, and 
>> assumed I was diong something wrong.
>> 
>> Thanks folks. Let’s hope this isn’t another one to add the unsolved major 
>> problems list.
>> 
>> 
>> Sent from my iPhone
>> 
>>> On 28 Aug 2015, at 03:18, Steve Martin  wrote:
>>> 
>>> do you change the automation status from write to read or something else 
>>> before playing it back?
 On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
  wrote:
 
 OK friends, what am I doing wrong now? I’m trying to automate certain 
 plugin parameters but to no av

Re: Bohemian Rhapsody?

[Slau Halatyn]

The Bohemian Rhapsody multitracks have been circulating for at least a decade. 
Google is your friend.

On Aug 28, 2015, at 11:24 PM, Christopher-Mark Gilland  
wrote:

> How do I get the Bohemian Rhapsody session for PT12?  By the way Slau makes 
> it sound in his recording, it's something we all should have.
>  
> Chris.
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Slau Halatyn]

Only testers have beta licenses and pre-release licenses on their iLoks.
I revealed absolutely nothing about Pro Tools itself and spoke only of 
accessibility improvements so you needn't concern yourself with my NDA. I clear 
everything I reveal with the folks at Avid. Just wanted to show people in 
context rather than in a list of text.

Slau

On Aug 29, 2015, at 6:26 AM, Christopher-Mark Gilland  
wrote:

> Can we get the release candidate then, or is that something only you have 
> since you're a beta tester?  If the ladder, then may I ask something with all 
> due respect?  I don't mean to make this sound like I'm cutting you down. I'm 
> actually asking this totally as an ignorant question.  I really truely may be 
> failing to realize something, and if that is the case, then I'd first like to 
> apologize directly to you even before I make this assumption.  If we cannot 
> get the release candidate, should we choose to run it, then wouldn't it be 
> safe to say since you privately have it, that you kind a broke NDA by showing 
> us those accessibility improvements?
> 
> Again, I'm asking this more totally out of curiosity.  Believe me!  By no 
> means is this a way to belittle, nor to chastise or put you down.  I truely 
> do not know how this works, and am genuinely asking.  So I really hope that 
> you don't take offense to this.  Yes, I trust you'd not break NDA, and I do 
> know you better than that.  This is why I'm slightly shocked that you did 
> show us this.  I thank you that you did, but I'm just wonderring.
> 
> Chris.
> 
> - Original Message - From: "Slau Halatyn" 
> To: 
> Sent: Friday, August 28, 2015 7:57 AM
> Subject: Re: new accessibility fixes in Pro Tools version 12
> 
> 
> Avid hasn't indicated when it'll be released but it'll be soon.
> 
> Slau
> 
> On Aug 28, 2015, at 7:06 AM, John André Lium-Netland  
> wrote:
> 
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout. 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: entering in tempo values

[Slau Halatyn]

Yes.
On Aug 29, 2015, at 6:56 AM, Christopher-Mark Gilland  
wrote:

> Aa!  Ow'w'w'w, Ka! Gotch ya!So, if it was on 120, and I wanted 120.3, 
> then I could ctrl+Option+Space, then because I already am to the right of the 
> decimal value, I would simply just type 3, then enter/return.  Am I following 
> you there correctly?  Because I'm already highlighted on the right part of 
> the decimal, and we already have the whole number set correctly to 120, there 
> is no need to hit the decimal key, as the left portion is set already 
> correctly.  Am I logically thinking this through correctly?
> 
> Chris.
> 
> - Original Message - From: "Slau Halatyn" 
> To: 
> Sent: Friday, August 28, 2015 11:46 AM
> Subject: Re: entering in tempo values
> 
> 
> Hi Chad,
> 
> As Matt mentioned, the Conductor needs to be turned off unless you're 
> entering tempo events using the Tempo changes through the Events menu. 
> Otherwise, to set a manual tempo do the following:
> Again, make sure the Conductor is turned off in the Transport window.
> 1. Navigate to the tempo field and press Control-Option-Space.
> 2. Press the decimal key once and type the tempo value you wish to use and 
> hit Enter or return.
> 
> That's it.
> 
> What happens when you first click on the field is that the section after the 
> decimal point becomes highlighted. Pressing the decimal key once cycles the 
> selection focus to the first field. If you wanted to type in a value of 
> 123.456, you would hit that decimal once at the beginning, type 123, press 
> the decimal again to get to the second field and type 456 and Enter.
> 
> Hope that helps.
> 
> Slau
> 
> On Aug 28, 2015, at 11:40 AM, Matt Diemert  wrote:
> 
>> Chad, did you turn off the conductor track? Also if you hit voiceover shift 
>> space perhaps try heading back space a few times first and then typing and 
>> 130. See if that helps at all
>> 
>> Sent from my iPhone
>> 
>>> On Aug 28, 2015, at 11:29 AM, Chad Baker  wrote:
>>> 
>>> hi i am having a heck of a time trying to enter in a tempo value
>>> i want 130 and its at 120
>>> i clicked in the edit field and typed 130 and enter and it put 120.1300
>>> i did vo shift space on the tempo field
>>> any suggestions to try
>>> thanks
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout. 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

What plugins are you trying to get?

Chris.

- Original Message - 
From: "Dionipher Presas Herrera" 

To: 
Sent: Saturday, August 29, 2015 7:04 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


hello, can somebody help me download the plug ins on pro tools first, i go 
to the martket place then plug ins but it is dis abled.
On 29 Aug 2015, at 1:02 PM, Christopher-Mark Gilland 
 wrote:


Aa, so you! even behind the scenes! don't know the exact date.  It's not 
an NDA thing, it's you! yourself, literally don't even know.  Gotcha.


Chris.

- Original Message - From: "Slau Halatyn" 
To: 
Sent: Friday, August 28, 2015 3:38 PM
Subject: Re: new accessibility fixes in Pro Tools version 12


Hi Nickus,

If the previous version was released the day after I said that, it was 
purely coincidence, I assure you :)
Since things are no longer boxed these days, the time from release 
candidate to actual drop date is very brief, of course. I'm hearing that 
we're probably looking at a september, perhaps a mid-September release. 
Whatever it is, it'll be a great update. I myself am still officially on 
version 11 at the studio and will wait until 12.2 is released before I do 
the upgrade. The whole subscription plan is at least somewhat confusing so 
I'll have to look into it before the end-of-the-year deadline at any rate 
so the upcoming update is a great incentive.


Cheers,

Slau

On Aug 28, 2015, at 3:01 PM, Nickus de Vos  wrote:

Slau, the last time you said that you don't know when but it will be 
soon, the update was released the very next day, haha.
I skipped version 12.1 even though I downloaded it when it was released, 
so I'm pritty keen on this update.


Slau once again thanks for your dedication and efforts.

Nickus

Sent from my iPhone


On 28 Aug 2015, at 13:57, Slau Halatyn  wrote:

Avid hasn't indicated when it'll be released but it'll be soon.

Slau

On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:




--
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Christopher-Mark Gilland]

If nothing else, can you at least, even if not the result I need tell me 
something I can do that regardless what the recording is, regardless how much 
noise there is, I could way over exagerate to at least! test if it's even 
working at all?

Chris.

  - Original Message - 
  From: Steve Martin 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 12:39 AM
  Subject: Re: Isotope RX4?


  May he may have overstepped by saying was 100% accessible its still quite 
useable and sufficient to resolve the issue chris wants to use it on as 
described here. I am not sure why you are not having any luck with it as a plug 
in as i have used it as an insert in Reaper and PT,However for best results you 
really want to use the standalone version for these task and then import the 
cleaned file into PT. the clean up process is very processor intensive and you 
wouldn’t want it running in a session the whole time. 

On Aug 28, 2015, at 11:21 PM, Daniel Contreras  
wrote:


I think he was referring to the stand alone version chris. 

Daniel Contreras 

On Aug 28, 2015, at 10:15 PM, Christopher-Mark Gilland 
 wrote:


  And, I hate to bust people's bubble, but it must not be accessible, 
seeing that I brought the d-noiser plugin up on an insert in PT 12.3, and no 
matter what I did, regardless which control/parameter I moved, I heard 
absolutely no changed result, and believe me, I may not have very sensitive 
ears, but I moved each control individually to hear the effect, and buddy, when 
I say move, damn it, I mean move!  I cranked the hell! outta those things and 
also knocked them the other way, so far down they were practically way in the 
negative values, and I mean way! in the negatives.  So either I'm stupid, 
the plugin isn't working, or the thing's a piece of crap.  Probably the second 
of the 3.

  Chris.

- Original Message - 
From: Steve Martin
To: ptaccess@googlegroups.com
Sent: Thursday, August 27, 2015 10:54 PM
Subject: Re: Isotope RX4?


100% accessible? Are you able to work with the spectrogram and etc?

  On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso 
 wrote:


  RX4 has his stand alone app 100% accessible. I use the advanced 
version but for demonising purposes the standard will make the job.




On Aug 27, 2015, at 18:29, Christopher-Mark Gilland 
 wrote:


Guys,

I have a cassette tape that I'm trying to remove a major! and I do 
mean major! hiss from.  It's me as a child, and it has some of the worst 
quality tape recording audio I've ever heard.  No doubt, my parents must a 
recorded this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't 
gonna get rid a this.

Anyway, has anyone used either the Isotope RX4 Standard or 
Advanced, preferably Standard plugins with PT?  If so, are they even somewhat 
accessible?  I'm thinking I'll probably use the D-Noise module.

If not that accessible, if I just wanna see, though probably not 
advisable, if it just naturally with no tweaking would make it a little better, 
do you think just popping it on an insert and being done with it would possibly 
even get rid of the slightest bit, even if not enough to be desirable?

If it's not accessible, does anyone have custom made presets 
that'll help me?  If not, what other plugs would be accessible that may help 
with this.  It's not really a hum type of hiss.  It's more the type background 
air noise kind a hiss you heard when recording on real cheap consumer grade 
little portable pocket tape recorders with the built in mikes.  Like something 
you'd buy at Radio Shaq or Circuit Shitty.

Chris.


-- 
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.





  -- 
  You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, 
send an email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.





-- 
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send a

Re: Isotope RX4?

[Christopher-Mark Gilland]

Well then, what control do I need to look at to get rid of tape hiss.  I moved 
all of the sliders, and all the other controls up and down majorly, one by one, 
both in the plug, and in the stand alone, and neither seem to be helping.

I know it depends, I'll have to just experiment, but what control for very bad 
tape hiss might I want to at least start with looking at, then branch out?

Chris.

  - Original Message - 
  From: Steve Martin 
  To: ptaccess@googlegroups.com 
  Sent: Saturday, August 29, 2015 12:39 AM
  Subject: Re: Isotope RX4?


  May he may have overstepped by saying was 100% accessible its still quite 
useable and sufficient to resolve the issue chris wants to use it on as 
described here. I am not sure why you are not having any luck with it as a plug 
in as i have used it as an insert in Reaper and PT,However for best results you 
really want to use the standalone version for these task and then import the 
cleaned file into PT. the clean up process is very processor intensive and you 
wouldn’t want it running in a session the whole time. 

On Aug 28, 2015, at 11:21 PM, Daniel Contreras  
wrote:


I think he was referring to the stand alone version chris. 

Daniel Contreras 

On Aug 28, 2015, at 10:15 PM, Christopher-Mark Gilland 
 wrote:


  And, I hate to bust people's bubble, but it must not be accessible, 
seeing that I brought the d-noiser plugin up on an insert in PT 12.3, and no 
matter what I did, regardless which control/parameter I moved, I heard 
absolutely no changed result, and believe me, I may not have very sensitive 
ears, but I moved each control individually to hear the effect, and buddy, when 
I say move, damn it, I mean move!  I cranked the hell! outta those things and 
also knocked them the other way, so far down they were practically way in the 
negative values, and I mean way! in the negatives.  So either I'm stupid, 
the plugin isn't working, or the thing's a piece of crap.  Probably the second 
of the 3.

  Chris.

- Original Message - 
From: Steve Martin
To: ptaccess@googlegroups.com
Sent: Thursday, August 27, 2015 10:54 PM
Subject: Re: Isotope RX4?


100% accessible? Are you able to work with the spectrogram and etc?

  On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso 
 wrote:


  RX4 has his stand alone app 100% accessible. I use the advanced 
version but for demonising purposes the standard will make the job.




On Aug 27, 2015, at 18:29, Christopher-Mark Gilland 
 wrote:


Guys,

I have a cassette tape that I'm trying to remove a major! and I do 
mean major! hiss from.  It's me as a child, and it has some of the worst 
quality tape recording audio I've ever heard.  No doubt, my parents must a 
recorded this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't 
gonna get rid a this.

Anyway, has anyone used either the Isotope RX4 Standard or 
Advanced, preferably Standard plugins with PT?  If so, are they even somewhat 
accessible?  I'm thinking I'll probably use the D-Noise module.

If not that accessible, if I just wanna see, though probably not 
advisable, if it just naturally with no tweaking would make it a little better, 
do you think just popping it on an insert and being done with it would possibly 
even get rid of the slightest bit, even if not enough to be desirable?

If it's not accessible, does anyone have custom made presets 
that'll help me?  If not, what other plugs would be accessible that may help 
with this.  It's not really a hum type of hiss.  It's more the type background 
air noise kind a hiss you heard when recording on real cheap consumer grade 
little portable pocket tape recorders with the built in mikes.  Like something 
you'd buy at Radio Shaq or Circuit Shitty.

Chris.


-- 
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.





  -- 
  You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, 
send an email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.





-- 
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



  -- 
  You received this message because you a

Re: Isotope RX4?

[Christopher-Mark Gilland]

Daniel,

I understand that, but I thought that he meant the whole way around, it was 
accessible, the stand-alone and! the plugin.  BTW, the stand alone isn't 
seeming to give any results either.

So, my initial findings still withold.

Chris.

  - Original Message - 
  From: Daniel Contreras 
  To: ptaccess@googlegroups.com 
  Sent: Friday, August 28, 2015 11:21 PM
  Subject: Re: Isotope RX4?


  I think he was referring to the stand alone version chris. 

  Daniel Contreras 

  On Aug 28, 2015, at 10:15 PM, Christopher-Mark Gilland 
 wrote:


And, I hate to bust people's bubble, but it must not be accessible, seeing 
that I brought the d-noiser plugin up on an insert in PT 12.3, and no matter 
what I did, regardless which control/parameter I moved, I heard absolutely no 
changed result, and believe me, I may not have very sensitive ears, but I moved 
each control individually to hear the effect, and buddy, when I say move, damn 
it, I mean move!  I cranked the hell! outta those things and also knocked them 
the other way, so far down they were practically way in the negative values, 
and I mean way! in the negatives.  So either I'm stupid, the plugin isn't 
working, or the thing's a piece of crap.  Probably the second of the 3.

Chris.

  - Original Message - 
  From: Steve Martin 
  To: ptaccess@googlegroups.com 
  Sent: Thursday, August 27, 2015 10:54 PM
  Subject: Re: Isotope RX4?


  100% accessible? Are you able to work with the spectrogram and etc?

On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso 
 wrote:


RX4 has his stand alone app 100% accessible. I use the advanced version 
but for demonising purposes the standard will make the job. 




  On Aug 27, 2015, at 18:29, Christopher-Mark Gilland 
 wrote:


  Guys,

  I have a cassette tape that I'm trying to remove a major! and I do 
mean major! hiss from.  It's me as a child, and it has some of the worst 
quality tape recording audio I've ever heard.  No doubt, my parents must a 
recorded this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't 
gonna get rid a this.

  Anyway, has anyone used either the Isotope RX4 Standard or Advanced, 
preferably Standard plugins with PT?  If so, are they even somewhat accessible? 
 I'm thinking I'll probably use the D-Noise module.

  If not that accessible, if I just wanna see, though probably not 
advisable, if it just naturally with no tweaking would make it a little better, 
do you think just popping it on an insert and being done with it would possibly 
even get rid of the slightest bit, even if not enough to be desirable?

  If it's not accessible, does anyone have custom made presets that'll 
help me?  If not, what other plugs would be accessible that may help with this. 
 It's not really a hum type of hiss.  It's more the type background air noise 
kind a hiss you heard when recording on real cheap consumer grade little 
portable pocket tape recorders with the built in mikes.  Like something you'd 
buy at Radio Shaq or Circuit Shitty.

  Chris.


  -- 
  You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, 
send an email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.





-- 
You received this message because you are subscribed to the Google 
Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

12 First?  What's that?

Chris.

  - Original Message - 
  From: Dionipher Herrera 
  To: Pro Tools Accessibility 
  Sent: Friday, August 28, 2015 10:50 PM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  i am using the pro tools 12 first, can somebody help me how to add loops?

  On Friday, August 28, 2015 at 2:24:57 AM UTC+2, Slau Halatyn wrote:
Since the folks over at the Logic Accessibility have a whole lot to be 
excited about with the new Logic update, I figured it was time to share the 
news about the significant progress made on the Pro Tools front. I thought it 
might be helpful to outline the new accessibility fixes in the upcoming Pro 
Tools version 12. We've had only a handful of fixes in the last 18 months or so 
but this time it's more like around 40 bug fixes. Many of them are subtle and 
simple things like fixing nomenclature but some are more significant. I'm 
attaching an mp3 that gives some examples of the changes and I talk through 
some of the stuff. I now realize that I didn't mention a couple of things in 
the recording like, for example, the "create Session" dialog which has been 
improved and the "Delete Unused Playlists" dialog which now reports the status 
of selected playlists within the table.


Anyway, in addition to attaching the mp3, here's a Drop Box link to the 
file in case the attachment gets screwed up in the posting.


Avid has made some incredible progress this time around and I'm really 
thrilled with the way things have moved forward. We still face challenges, of 
course, and there are still areas like the Applications Manager that need 
attention but things are looking up.


Enjoy,


Slau





  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Compressor parameters reset back to defaults whenever I close the plugin window

[Christopher-Mark Gilland]

Robin,

There is a sollution.  Matt and Rod unintentionally might a made a little 
booboo in their recording.  Maybe in V10 you could get away with this, but I 
don't think you could.  I had this same issue after following their nuts and 
bolts section on the web site.


Basically the problem is, they tell you to check the option for Plugin 
defaults to automation enabled in the ProTools Preferences.  You want to 
actually do the oppisit.  You actually want this to not! be checked.  I 
don't recall where that checkbox is exactly.  It's under the mix tab of PT's 
preferences, but I don't remember exactly which area then to interact with 
under that tab, and right now, I'm on my Windows PC, so I can't look.  It 
should be fairly obvious though once you get in there.


Try that though, and see if that helps.

Chris.

- Original Message - 
From: "Robin Kipp" 

To: 
Sent: Friday, August 28, 2015 6:49 PM
Subject: Compressor parameters reset back to defaults whenever I close the 
plugin window



Hi all!
So… By now I made it to the mixing module of the PRo Tools With Speech 
tutorials and up until this point everything went very smoothly! However, I’m 
now experiencing a rather frustrating problem… So, Basically I’ve got this 
vocal track to which I applied the BF-76 compressor using inserts. Now, when 
I VO space on that insert to bring up the plugin window, I can tell that 
there’s quite a difference in how things are labeled from the tutorial, 
probably because Matt and Rob are using PT 10 whereas I’m on PT 11. Even 
though the labels are a little confusing, I could locate the relevant 
parameters without much trouble. Now, when I change the input and output 
values, I noticed that those parameters stay at whatever value I set them to 
even when I close that floating window. However, there is an annoying issue 
when I change either the attack, release or ratio parameters. I can interact 
with and modify them as usual, and if I stop interacting, move the focus 
elsewhere within the plugin window and then return they will still have the 
same values. However, and this is where it gets annoying, I’ve found that as 
soon as I move the VO focus out of the plugin window, either by closing the 
window or by simply selecting a different window, as soon as I move the VO 
focus back to the compressor I find that the parameters simply reverted back 
to their defaults, e.g. attack 3.0, release 5.1 and a ratio of 4:1… I’ve 
tried this a couple times now, relaunched PT, tried setting those parameters 
with cursor tracking disabled - yet I’m still seeing the same annoying 
behavior! I really really hope that there’s a simple solution for that, or 
maybe it’s just a case of me doing something wrong due to lack of 
experience!
Either way, if anyone of you could point me in the right direction I would 
greatly appreciate that!

Many thanks,
Robin

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Dionipher Presas Herrera]

hello, can somebody help me download the plug ins on pro tools first, i go to 
the martket place then plug ins but it is dis abled.
> On 29 Aug 2015, at 1:02 PM, Christopher-Mark Gilland  
> wrote:
> 
> Aa, so you! even behind the scenes! don't know the exact date.  It's not an 
> NDA thing, it's you! yourself, literally don't even know.  Gotcha.
> 
> Chris.
> 
> - Original Message - From: "Slau Halatyn" 
> To: 
> Sent: Friday, August 28, 2015 3:38 PM
> Subject: Re: new accessibility fixes in Pro Tools version 12
> 
> 
> Hi Nickus,
> 
> If the previous version was released the day after I said that, it was purely 
> coincidence, I assure you :)
> Since things are no longer boxed these days, the time from release candidate 
> to actual drop date is very brief, of course. I'm hearing that we're probably 
> looking at a september, perhaps a mid-September release. Whatever it is, 
> it'll be a great update. I myself am still officially on version 11 at the 
> studio and will wait until 12.2 is released before I do the upgrade. The 
> whole subscription plan is at least somewhat confusing so I'll have to look 
> into it before the end-of-the-year deadline at any rate so the upcoming 
> update is a great incentive.
> 
> Cheers,
> 
> Slau
> 
> On Aug 28, 2015, at 3:01 PM, Nickus de Vos  wrote:
> 
>> Slau, the last time you said that you don't know when but it will be soon, 
>> the update was released the very next day, haha.
>> I skipped version 12.1 even though I downloaded it when it was released, so 
>> I'm pritty keen on this update.
>> 
>> Slau once again thanks for your dedication and efforts.
>> 
>> Nickus
>> 
>> Sent from my iPhone
>> 
>>> On 28 Aug 2015, at 13:57, Slau Halatyn  wrote:
>>> 
>>> Avid hasn't indicated when it'll be released but it'll be soon.
>>> 
>>> Slau
>>> 
 On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
  wrote:
 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout. 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

Aa, so you! even behind the scenes! don't know the exact date.  It's not an 
NDA thing, it's you! yourself, literally don't even know.  Gotcha.


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 3:38 PM
Subject: Re: new accessibility fixes in Pro Tools version 12


Hi Nickus,

If the previous version was released the day after I said that, it was 
purely coincidence, I assure you :)
Since things are no longer boxed these days, the time from release candidate 
to actual drop date is very brief, of course. I'm hearing that we're 
probably looking at a september, perhaps a mid-September release. Whatever 
it is, it'll be a great update. I myself am still officially on version 11 
at the studio and will wait until 12.2 is released before I do the upgrade. 
The whole subscription plan is at least somewhat confusing so I'll have to 
look into it before the end-of-the-year deadline at any rate so the upcoming 
update is a great incentive.


Cheers,

Slau

On Aug 28, 2015, at 3:01 PM, Nickus de Vos  wrote:

Slau, the last time you said that you don't know when but it will be soon, 
the update was released the very next day, haha.
I skipped version 12.1 even though I downloaded it when it was released, 
so I'm pritty keen on this update.


Slau once again thanks for your dedication and efforts.

Nickus

Sent from my iPhone


On 28 Aug 2015, at 13:57, Slau Halatyn  wrote:

Avid hasn't indicated when it'll be released but it'll be soon.

Slau

On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:




--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: tempo is all fixed now thanks

[Christopher-Mark Gilland]

OK.  This is easy.  Graham, A K A, The Recording Revolution, actually did a 
tutorial on this very thing.


Basically, if I am understanding correctly how he did this, you want to 
select the part of the song on your timeline ruler where you want the tempo 
to change.  Then you're gonna go into your tempo window, and move the tempo 
where you wish for it to be.  That's it.  Provided you have a selection 
made, it should work.  I think the conductor has to be on though.


Chris.

- Original Message - 
From: "Chad Baker" 

To: 
Sent: Friday, August 28, 2015 12:21 PM
Subject: tempo is all fixed now thanks


hi slau that worked thanks now one quick question
i am recording a friend’s metal band and there tempos change measure to 
measure

not sure what all those types of tempos like parabolic and linear mean
i just want to input different tempos for the different measures that they 
want


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: entering in tempo values

[Christopher-Mark Gilland]

Aa!  Ow'w'w'w, Ka! Gotch ya!So, if it was on 120, and I wanted 120.3, 
then I could ctrl+Option+Space, then because I already am to the right of 
the decimal value, I would simply just type 3, then enter/return.  Am I 
following you there correctly?  Because I'm already highlighted on the right 
part of the decimal, and we already have the whole number set correctly to 
120, there is no need to hit the decimal key, as the left portion is set 
already correctly.  Am I logically thinking this through correctly?


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 11:46 AM
Subject: Re: entering in tempo values


Hi Chad,

As Matt mentioned, the Conductor needs to be turned off unless you're 
entering tempo events using the Tempo changes through the Events menu. 
Otherwise, to set a manual tempo do the following:

Again, make sure the Conductor is turned off in the Transport window.
1. Navigate to the tempo field and press Control-Option-Space.
2. Press the decimal key once and type the tempo value you wish to use and 
hit Enter or return.


That's it.

What happens when you first click on the field is that the section after the 
decimal point becomes highlighted. Pressing the decimal key once cycles the 
selection focus to the first field. If you wanted to type in a value of 
123.456, you would hit that decimal once at the beginning, type 123, press 
the decimal again to get to the second field and type 456 and Enter.


Hope that helps.

Slau

On Aug 28, 2015, at 11:40 AM, Matt Diemert  wrote:

Chad, did you turn off the conductor track? Also if you hit voiceover 
shift space perhaps try heading back space a few times first and then 
typing and 130. See if that helps at all


Sent from my iPhone


On Aug 28, 2015, at 11:29 AM, Chad Baker  wrote:

hi i am having a heck of a time trying to enter in a tempo value
i want 130 and its at 120
i clicked in the edit field and typed 130 and enter and it put 120.1300
i did vo shift space on the tempo field
any suggestions to try
thanks

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: entering in tempo values

[Christopher-Mark Gilland]

Matthew, you are a genious!  I totally! totally! forgot about the conductor 
track!  Now, I just gotta remember where you go to turn that damn thing off.


Chris.

- Original Message - 
From: "Matt Diemert" 

To: 
Sent: Friday, August 28, 2015 11:40 AM
Subject: Re: entering in tempo values


Chad, did you turn off the conductor track? Also if you hit voiceover 
shift space perhaps try heading back space a few times first and then 
typing and 130. See if that helps at all


Sent from my iPhone


On Aug 28, 2015, at 11:29 AM, Chad Baker  wrote:

hi i am having a heck of a time trying to enter in a tempo value
i want 130 and its at 120
i clicked in the edit field and typed 130 and enter and it put 120.1300
i did vo shift space on the tempo field
any suggestions to try
thanks

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: entering in tempo values

[Christopher-Mark Gilland]

I'm, too, finding this very! very! problematic in PT 12.X.

I'm also having issues enterring time values into the start and end clusters 
within the edit window.  Same type of results as within the tempo window. 
Incredibly annoying!


Chris.

- Original Message - 
From: "Chad Baker" 

To: 
Sent: Friday, August 28, 2015 11:29 AM
Subject: entering in tempo values



hi i am having a heck of a time trying to enter in a tempo value
i want 130 and its at 120
i clicked in the edit field and typed 130 and enter and it put 120.1300
i did vo shift space on the tempo field
any suggestions to try
thanks

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: question about click track creation

[Christopher-Mark Gilland]

Chad, you're not the only one.

Also, I cannot seem to get it to work with the star and the slash keys.

I'm trying to remember which is which.  Wasn't it slash that moves between 
start, end, and length?  Then star was to move to a location, or do I have that 
backwards.

Also, on an apple keyboard I can't remember which key is star and which is 
slash.  I always get those confused.  Is Star on the left of the two keys, or 
is star the one on the right.

Say I wanted to move to 1 min and 24 seconds into the session.  I'm not trying 
to select anything, I just want to move to that time.  What would the syntax be 
of the keys I'd hit?

Chris.

  - Original Message - 
  From: Chad Baker 
  To: ptaccess@googlegroups.com 
  Sent: Friday, August 28, 2015 10:55 AM
  Subject: Re: question about click track creation


  hi slau thanks also another quick question i am having a heck of time 
entering numbers in the tempo field
  i did vo shift space on the edit field
  i can’t get a tempo typed in

On Aug 28, 2015, at 10:49 AM, Slau Halatyn  wrote:


Go to protoolswithspeech.com and download the presets I created and you'll 
be set.


Slau


On Aug 28, 2015, at 10:41 AM, Chad Baker  wrote:


  hi i created a click track but i can't change the preset clicks
  under factory default there's nothing anything i'm mussing
  thanks


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.





-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: confirmed plug-in automation issue

[Christopher-Mark Gilland]

It really did work, Slau.  I even just tested it again with 10 over here, 
and it definitely did work.


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 10:51 AM
Subject: Re: confirmed plug-in automation issue



Hi Matt,

It would be helpful to know whether it was truly working or whether it was 
volume or pan automation that worked. Let me know.


Slau

On Aug 28, 2015, at 10:28 AM, Martin (Punky) Sopart  
wrote:



Matt!

During your tutorials I think you only automated a fade by using the 
volume slider inside the master fader.


Best! / Martin

-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
On Behalf Of Matt Diemert
Sent: Friday, August 28, 2015 4:18 PM
To: ptaccess@googlegroups.com
Subject: Re: confirmed plug-in automation issue

Actually, I believe in ProTools 10.0 it was possible to automate 
plug-ins from

the keyboard. I vaguely remember doing a bid on it during the creation
process of our tutorials, and I think we decided against it for one 
reason or
another but I'm going to see if I can track down the audio and listen to 
it to
see if it worked. I also have an old machine around here that still has 
10 on it
maybe I will fire it up when I get home tonight and just make sure that 
I'm

right.

Sent from my iPhone

On Aug 28, 2015, at 9:54 AM, Slau Halatyn  
wrote:


I just got into the studio and confirmed the issue with trying to write

automation using only VoiceOver. Over the years where we've had no less
than 10 VoiceOver users beta test Pro Tools, not once has anybody 
reported
this issue. That, of course, is not surprising since most of the users 
have

control surfaces and would never dream of writing automation using only
VoiceOver. Those testers without a surface clearly never got around to
testing this specific aspect. From an accessibility standpoint, the 
knee-jerk
reaction is to look at things that are unlabeled or invisible, etc. 
Functionality
such as this is taking it a step further and so it's not inconceivable 
how this
could be the case. I've confirmed the behavior in both version 11 and 12 
and I

doubt it was any different going back to version 8.


Anyway, as I said earlier, this won't get fixed in the upcoming release 
but I'll

submit a bug report for the future.


Slau

--
You received this message because you are subscribed to the Google

Groups "Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an

email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google 
Groups

"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an

email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: confirmed plug-in automation issue

[Christopher-Mark Gilland]

Yeah, I think you're right.

I'll have to go listen to that section again, but I do remember him 
automating a fade.


Chris.

- Original Message - 
From: "Martin (Punky) Sopart" 

To: 
Sent: Friday, August 28, 2015 10:28 AM
Subject: RE: confirmed plug-in automation issue



Matt!

During your tutorials I think you only automated a fade by using the 
volume slider inside the master fader.


Best! / Martin

-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
On Behalf Of Matt Diemert
Sent: Friday, August 28, 2015 4:18 PM
To: ptaccess@googlegroups.com
Subject: Re: confirmed plug-in automation issue

Actually, I believe in ProTools 10.0 it was possible to automate plug-ins 
from

the keyboard. I vaguely remember doing a bid on it during the creation
process of our tutorials, and I think we decided against it for one 
reason or
another but I'm going to see if I can track down the audio and listen to 
it to
see if it worked. I also have an old machine around here that still has 
10 on it
maybe I will fire it up when I get home tonight and just make sure that 
I'm

right.

Sent from my iPhone

> On Aug 28, 2015, at 9:54 AM, Slau Halatyn  
> wrote:

>
> I just got into the studio and confirmed the issue with trying to write
automation using only VoiceOver. Over the years where we've had no less
than 10 VoiceOver users beta test Pro Tools, not once has anybody 
reported
this issue. That, of course, is not surprising since most of the users 
have

control surfaces and would never dream of writing automation using only
VoiceOver. Those testers without a surface clearly never got around to
testing this specific aspect. From an accessibility standpoint, the 
knee-jerk
reaction is to look at things that are unlabeled or invisible, etc. 
Functionality
such as this is taking it a step further and so it's not inconceivable 
how this
could be the case. I've confirmed the behavior in both version 11 and 12 
and I

doubt it was any different going back to version 8.
>
> Anyway, as I said earlier, this won't get fixed in the upcoming release 
> but I'll

submit a bug report for the future.
>
> Slau
>
> --
> You received this message because you are subscribed to the Google
Groups "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an

email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Discovery about PT10.

[Christopher-Mark Gilland]

So, after looking around more on my audio production system, I found that I 
actually have both PT10.0 and PT 12.1 installed.  Yes, PT10 is running 
perfectly, so bam, there went my automation issue with Auto-Tune down the 
drain.  At least I can use PT10 if I need to automate some plugs.  Now, here is 
the issue though.

I still see Auto-Tune 7 Native in my list of plugins when I go on an insert to 
plugins/pitch.  But, I don't see V 8 native in there.  Yes, I had it rescan all 
the plugins, but it's just not seeing it.  PT12 sees it, but not 10.  Although, 
12 doesn't see V7, only V8.  So here is my question.  Why would PT 10 not see 
Auto-Tune Native 8?  I thought that PT 10.0, not 10.1, not 10.2, etc.  I'm 
saying literally specifically exactly, 10.0.  I thought that it did! support 
the AAX format.  Did it not?  Was it still only using RTas?  If so, then that 
definitely! would explain why it's not seeing A T 8, as A T 8 Native is 
specifically AAX.

Chris.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: confirmed plug-in automation issue

[Christopher-Mark Gilland]

So... I still have my 10.0 DMG.  Apparently my current ILok asset, says 
Sweet Water, will still let me use V10.  So, could I install V10, and still 
also have V12 on this system as well?


Chris.

- Original Message - 
From: "Matt Diemert" 

To: 
Sent: Friday, August 28, 2015 10:17 AM
Subject: Re: confirmed plug-in automation issue


Actually, I believe in ProTools 10.0 it was possible to automate plug-ins 
from the keyboard. I vaguely remember doing a bid on it during the creation 
process of our tutorials, and I think we decided against it for one reason 
or another but I'm going to see if I can track down the audio and listen to 
it to see if it worked. I also have an old machine around here that still 
has 10 on it maybe I will fire it up when I get home tonight and just make 
sure that I'm right.


Sent from my iPhone


On Aug 28, 2015, at 9:54 AM, Slau Halatyn  wrote:

I just got into the studio and confirmed the issue with trying to write 
automation using only VoiceOver. Over the years where we've had no less 
than 10 VoiceOver users beta test Pro Tools, not once has anybody reported 
this issue. That, of course, is not surprising since most of the users 
have control surfaces and would never dream of writing automation using 
only VoiceOver. Those testers without a surface clearly never got around 
to testing this specific aspect. From an accessibility standpoint, the 
knee-jerk reaction is to look at things that are unlabeled or invisible, 
etc. Functionality such as this is taking it a step further and so it's 
not inconceivable how this could be the case. I've confirmed the behavior 
in both version 11 and 12 and I doubt it was any different going back to 
version 8.


Anyway, as I said earlier, this won't get fixed in the upcoming release 
but I'll submit a bug report for the future.


Slau

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: confirmed plug-in automation issue

[Christopher-Mark Gilland]

Actually Slau, in V10, it worked beautifully.

At least, for me it did.

Thank you for taking out your time to test this though.

Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 9:54 AM
Subject: confirmed plug-in automation issue


I just got into the studio and confirmed the issue with trying to write 
automation using only VoiceOver. Over the years where we've had no less than 
10 VoiceOver users beta test Pro Tools, not once has anybody reported this 
issue. That, of course, is not surprising since most of the users have 
control surfaces and would never dream of writing automation using only 
VoiceOver. Those testers without a surface clearly never got around to 
testing this specific aspect. From an accessibility standpoint, the 
knee-jerk reaction is to look at things that are unlabeled or invisible, 
etc. Functionality such as this is taking it a step further and so it's not 
inconceivable how this could be the case. I've confirmed the behavior in 
both version 11 and 12 and I doubt it was any different going back to 
version 8.


Anyway, as I said earlier, this won't get fixed in the upcoming release but 
I'll submit a bug report for the future.


Slau

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hopefully a basic, easy to solve plugin automation problem

[Christopher-Mark Gilland]

Slau, like I said, with Auto-Tune Native 7, and PT 10.0, yes.  I was 
definitely able to automate things with changing the key value, or the scale 
value, so yes.  I have with no surface done this very very effectively, and 
very consistently, and it worked like a dream.  It wasn't until I updated to 
both PT12 and then had to update to the AAX format of Auto-Tune, which is 
now Native 8, that I began to see this problem.  I confess I've not tested 
this with other plugs that I remember, so I don't know if this is A T 
specific, or if this issue would happen all the way across the board.


If you'd like to have me test this for your data collection further, then 
just tell me step by step what you'd like me to do, and I'll report back to 
you all my results.


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 8:06 AM
Subject: Re: Hopefully a basic, easy to solve plugin automation problem


Actually, it's conceivable that the VoiceOver interaction isn't working for 
automation and perhaps never worked. Has anyone successfully automated a 
plug-in parameter on the list? Let me say, and I've said this before, I 
can't fathom how any VoiceOver user can begin to use Pro tools in a serious 
fashion without a control surface. I've only used automation with with 
control surfaces and, of course, it works fine. There was a similar issue of 
VoiceOver changing fader values correctly but, when faders were grouped, 
things didn't work correctly when changing levels with VoiceOver. Again, 
with a control surface, it's been a non-issue. It's possible that we're 
seeing the same thing here. Needless to say, if that's the case here, that 
wouldn't be fixed in the upcoming release because there's no time.


As I mentioned, I've never attempted any plug-in automation without a 
control surface and, clearly, none of the beta testers have ever thought to 
try it either and there was never a bug report logged on this issue if, in 
fact, it is a current issue. Someone will need to reproduce the results. I 
know others without control surfaces have had difficulties but it'll have to 
be replicated in a controlled manner and logged. I'll see if I can do that 
in the near future.


Slau

On Aug 28, 2015, at 7:34 AM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


Sorry, pressed the wrong button and sent the previous email again. 
ProTools is playing with my sanity levels. Here's what I meant to send.
It seems impossible to automate plugins using the mac keyboard. My friend 
has just done it with the trackpad and it works, but doing it with 
Voice-Over completely fails.


If anyone feels saintly enough to have a go at recreating these steps and 
telling me what they experience, or helping to put me straight on this, 
then that would be great.


I put the track on autowrite, I enable the plugin control I want for 
automation. I change the control by interacting with it and using the 
arrow keys. The change occurs; I know this becuase I can hear it, and I’ve 
had sighted clarification. I then stop the project, put the track on read, 
and play the track at the point where the automation should be kicking in. 
Nothing happens. The plugin control just resets to where it was before I 
started, and there is no automation written.


My sighted friend manages to do exactly the same as I am doing only using 
the mouse to automate, and it works fine. Sickeningly, he is also able to 
make smoother changes simply with the mouse, but that’s another story.


I have the box unticked besides the auto enable plugins for automation 
option in the automation part of the mix tab in preferences.


I really don’t think ProTools wants me to have automation control over 
plugins. Surely this can’t be an accessibility issue, as it seems like a 
massive flaw. I tried this once a few months ago using PT11 and it didn’t 
work then either, but I was too busy to try anything at that time, and 
assumed I was diong something wrong.


Thanks folks. Let’s hope this isn’t another one to add the unsolved major 
problems list.



Sent from my iPhone


On 28 Aug 2015, at 03:18, Steve Martin  wrote:

do you change the automation status from write to read or something else 
before playing it back?
On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


OK friends, what am I doing wrong now? I’m trying to automate certain 
plugin parameters but to no avail. I insert an effect, I VO space on the 
automation enable button, I select a parameter then press on add, then 
OK. I set my track to automation write. I start playing the project and 
manipulating the enabled perimeter, and I hear the changes. Sounding 
good. I then play it back and there are no changes. All that happens is 
that the plugin parameter resorts back to the previous value that I 
started at.


Any help would be very welcome as I’m rather baffled.


Sent from my iPhone

--
You received this message because you are subscribed to the 

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

Can we get the release candidate then, or is that something only you have 
since you're a beta tester?  If the ladder, then may I ask something with 
all due respect?  I don't mean to make this sound like I'm cutting you down. 
I'm actually asking this totally as an ignorant question.  I really truely 
may be failing to realize something, and if that is the case, then I'd first 
like to apologize directly to you even before I make this assumption.  If we 
cannot get the release candidate, should we choose to run it, then wouldn't 
it be safe to say since you privately have it, that you kind a broke NDA by 
showing us those accessibility improvements?


Again, I'm asking this more totally out of curiosity.  Believe me!  By no 
means is this a way to belittle, nor to chastise or put you down.  I truely 
do not know how this works, and am genuinely asking.  So I really hope that 
you don't take offense to this.  Yes, I trust you'd not break NDA, and I do 
know you better than that.  This is why I'm slightly shocked that you did 
show us this.  I thank you that you did, but I'm just wonderring.


Chris.

- Original Message - 
From: "Slau Halatyn" 

To: 
Sent: Friday, August 28, 2015 7:57 AM
Subject: Re: new accessibility fixes in Pro Tools version 12


Avid hasn't indicated when it'll be released but it'll be soon.

Slau

On Aug 28, 2015, at 7:06 AM, John André Lium-Netland 
 wrote:






--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

Also, will it be a paid update?  I assume not being I'm still well within my 
yearly update subscription.

Chris.

  - Original Message - 
  From: Brian Howerton 
  To: ptaccess@googlegroups.com 
  Sent: Friday, August 28, 2015 6:05 AM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  Hi Slau,
  Thanks for this. When do you expect this update to be available?
  Brian

  Sent from my iPhone

  On Aug 27, 2015, at 8:24 PM, Slau Halatyn  wrote:


Since the folks over at the Logic Accessibility have a whole lot to be 
excited about with the new Logic update, I figured it was time to share the 
news about the significant progress made on the Pro Tools front. I thought it 
might be helpful to outline the new accessibility fixes in the upcoming Pro 
Tools version 12. We've had only a handful of fixes in the last 18 months or so 
but this time it's more like around 40 bug fixes. Many of them are subtle and 
simple things like fixing nomenclature but some are more significant. I'm 
attaching an mp3 that gives some examples of the changes and I talk through 
some of the stuff. I now realize that I didn't mention a couple of things in 
the recording like, for example, the "create Session" dialog which has been 
improved and the "Delete Unused Playlists" dialog which now reports the status 
of selected playlists within the table.


Anyway, in addition to attaching the mp3, here's a Drop Box link to the 
file in case the attachment gets screwed up in the posting.


Avid has made some incredible progress this time around and I'm really 
thrilled with the way things have moved forward. We still face challenges, of 
course, and there are still areas like the Applications Manager that need 
attention but things are looking up.


Enjoy,


Slau





-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

I echo Brian's question.

Chris.

  - Original Message - 
  From: Brian Howerton 
  To: ptaccess@googlegroups.com 
  Sent: Friday, August 28, 2015 6:05 AM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  Hi Slau,
  Thanks for this. When do you expect this update to be available?
  Brian

  Sent from my iPhone

  On Aug 27, 2015, at 8:24 PM, Slau Halatyn  wrote:


Since the folks over at the Logic Accessibility have a whole lot to be 
excited about with the new Logic update, I figured it was time to share the 
news about the significant progress made on the Pro Tools front. I thought it 
might be helpful to outline the new accessibility fixes in the upcoming Pro 
Tools version 12. We've had only a handful of fixes in the last 18 months or so 
but this time it's more like around 40 bug fixes. Many of them are subtle and 
simple things like fixing nomenclature but some are more significant. I'm 
attaching an mp3 that gives some examples of the changes and I talk through 
some of the stuff. I now realize that I didn't mention a couple of things in 
the recording like, for example, the "create Session" dialog which has been 
improved and the "Delete Unused Playlists" dialog which now reports the status 
of selected playlists within the table.


Anyway, in addition to attaching the mp3, here's a Drop Box link to the 
file in case the attachment gets screwed up in the posting.


Avid has made some incredible progress this time around and I'm really 
thrilled with the way things have moved forward. We still face challenges, of 
course, and there are still areas like the Applications Manager that need 
attention but things are looking up.


Enjoy,


Slau





-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

[Christopher-Mark Gilland]

Nick, you have a really valid point here.  I looked, and apparently I'm only on 
12.1.  I could a sworn it was 12.3, but maybe not.  When I look in my Avid 
Account under my Products and Downloads, the only thing that I see is PT 12.0, 
and PT 12.1.  Maybe I just read wrong initially.

Also, I found the PT 11 demo session up there, but not the demo session to PT 
12.  I think a while back Brian Howerton was also wanting this session, but 
couldn't find it either, so trust me.  It's not just him.  I confess I didn't 
yet listen to the whole recording Slau made with the accessibility 
improvements, so maybe I'm missing something here and you can't get this, but 
if I understood correctly, that multi-track session of the Bohemian Rhapsody he 
was working with is something all us should have.  I looked practically 
everywhere though and I can't find it.  It's not in my Avid account either.  
So, what gives?  Am I confused, or can someone point me to where to get it.  If 
nothing else, can someone zip it and send me a Dropbox link?

Chris.

  - Original Message - 
  From: Nick Gawronski 
  To: ptaccess@googlegroups.com 
  Sent: Thursday, August 27, 2015 11:55 PM
  Subject: Re: new accessibility fixes in Pro Tools version 12


  Hi, One thing I have always wondered is if there is a way to find out when 
the next release of Pro Tools is ready as the Avid application manager says 
updates are ready but when I login into my account just Pro Tools 12.0.2 is 
there?  Is there any email list or other pages that can let us know when 
updates are released?  Nick Gawronski


  On 8/27/2015 8:27 PM, 'onlineeagle' via Pro Tools Accessibility wrote:

Excellent, thanks for that run-through Slau. And thanks for the 
complimentary "inequality of lifh" pun.

Sent from my iPhone

On 28 Aug 2015, at 01:24, Slau Halatyn  wrote:


  Since the folks over at the Logic Accessibility have a whole lot to be 
excited about with the new Logic update, I figured it was time to share the 
news about the significant progress made on the Pro Tools front. I thought it 
might be helpful to outline the new accessibility fixes in the upcoming Pro 
Tools version 12. We've had only a handful of fixes in the last 18 months or so 
but this time it's more like around 40 bug fixes. Many of them are subtle and 
simple things like fixing nomenclature but some are more significant. I'm 
attaching an mp3 that gives some examples of the changes and I talk through 
some of the stuff. I now realize that I didn't mention a couple of things in 
the recording like, for example, the "create Session" dialog which has been 
improved and the "Delete Unused Playlists" dialog which now reports the status 
of selected playlists within the table. 


  Anyway, in addition to attaching the mp3, here's a Drop Box link to the 
file in case the attachment gets screwed up in the posting.


  Avid has made some incredible progress this time around and I'm really 
thrilled with the way things have moved forward. We still face challenges, of 
course, and there are still areas like the Applications Manager that need 
attention but things are looking up.


  Enjoy,


  Slau




  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




  -- 
  You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot start recording by pressing CMD + spacebar in PT 11

[Christopher-Mark Gilland]

Robin,

How about this.  Can you maybe use your numpad 3 key?  That also is record.

Chris.

- Original Message - 
From: "Dionipher Presas Herrera" 

To: 
Sent: Thursday, August 27, 2015 11:07 PM
Subject: Re: Cannot start recording by pressing CMD + spacebar in PT 11


cmd + space bar change language in my computer

On 28 Aug 2015, at 12:26 AM, Robin Kipp  wrote:

Hi Matt and Steve,
thanks a lot for your replies!
For the time being, I have decided against deleting the .plist file. The 
primary reason is that, while Googling the issue, I read some forum posts 
stating that deleting this file will remove custom shortcuts… Since I 
actually do have a lot of those for Automator scripts and such, I’m just 
gonna stick to F12 for now.
I’ll definitely keep this in mind though and might try deleting the file 
at a later time, since for now I’d prefer to focus on learning PT rather 
than having to redefine my shortcut commands! :-)

Thanks a lot for all the help,
Robin

Am 26.08.2015 um 20:27 schrieb mcdiemert . :

Sorry,
I touched cancel on my iPhone and apparently it thought I meant send!
TO be more clear, when I've done this in the past, I've deleted the
.plst file, and removed it from trash before rebooting. I suspect you
making a backup of the file prior to rebooting was the problem here.
In my experience, and I've probably done this a dozen times, the
symbolic hotkeys files is regenerated upon reboot.
If you're not comfortable with testing this, perhaps using f12 for now
would work.


On 8/26/15, Matt Diemert  wrote:
I have found that if I do not delete  the i'll, and empty the trash, it 
does
not work. So backing it up and have actually been a mistake because the 
file

does get regenerated want to reboot your computer.

Sent from my iPhone


On Aug 26, 2015, at 12:07 PM, Robin Kipp  wrote:

Hi,
thanks for pointing me in the right direction! After some Googling, I
found various posts by people having the exact same problem, however 
most
of them are quite dated (2007 and earlier). I found the tip about 
removing
~/Library/Preferences/com.apple.symbolichotkeys.plist so I backed up 
the

file and then removed it from that folder. Unfortunately, however, this
didn’t actually solve the problem for me… I tried rebooting, then 
creating

a new session but without any luck… So, in case you do have any more
details or an article that you could share I definitely would greatly
appreciate that!
All the best,
Robin

Am 26.08.2015 um 15:46 schrieb mcdiemert . :

I've had this happen to me at times when I switch keyboards, or use a
wireless/Bluetooth KB.
There is a symbolic hotkeys files that needs deleted and preferences
as far as spot light need reset. I'll try to dig the article up if I
can when I'm back today, but if you google the issue it should pop up.



On 8/26/15, Robin Kipp  wrote:
Hi Peter,
I’m on a 2013 Mac Pro using a Bluetooth keyboard.
HTH and thanks for the response!
Robin

--
You received this message because you are subscribed to the Google
Groups
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, 
send

an
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Warm Regards:
Matt Diemert
330-980-0046

--
You received this message because you are subscribed to the Google 
Groups

"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an

email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google 
Groups

"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send 
an

email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.





--
Warm Regards:
Matt Diemert
330-980-0046

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an e

Re: Hopefully a basic, easy to solve plugin automation problem

[Christopher-Mark Gilland]

Yes?  I have my preferences set after stopping from writing the automation, 
it then goes to latch, although I don't play anything back with it in latch 
mode.  I make sure first to set it back to read.


Chris.

- Original Message - 
From: "Steve Martin" 

To: 
Sent: Thursday, August 27, 2015 10:18 PM
Subject: Re: Hopefully a basic, easy to solve plugin automation problem


do you change the automation status from write to read or something else 
before playing it back?
On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


OK friends, what am I doing wrong now? I’m trying to automate certain 
plugin parameters but to no avail. I insert an effect, I VO space on the 
automation enable button, I select a parameter then press on add, then OK. 
I set my track to automation write. I start playing the project and 
manipulating the enabled perimeter, and I hear the changes. Sounding good. 
I then play it back and there are no changes. All that happens is that the 
plugin parameter resorts back to the previous value that I started at.


Any help would be very welcome as I’m rather baffled.


Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hopefully a basic, easy to solve plugin automation problem

[Christopher-Mark Gilland]

You're not the only one having this problem.  I made sure in the ProTools 
preferences to set plugin defaults to automate enabled, but even still! it's 
not working.


I can automate volume, or pans, or things of that nature, but in, say, 
Auto-Tune Native 8.  If I have the  scale set to major, key of C, then the 
song in the last chorus modulates up to the key of D, I want to obviously 
write automation so that Auto-Tune will automatically switch the key 
parameter from C over to D at that point.  It's not doing so though.


The other thing is, yes.  I did make sure to hit command+numpad 4 to open 
the automation window.  I made certain that the only thing selected was 
plugin automation.  Yes, I also did first start by writing a global pass 
automation event to the track.  Yes, I did make sure in my track list table 
that the track which I needed automation written to was indeed selected, and 
yes, I also further did make sure that the time range on my ruler was 
correctly selected.  Yes, I did let the entire audio selection play through, 
and write the automation to that whole selection.


So, yeah, I'm totally batheled.  In PT 10.0, with Auto-Tune Native V7, I 
didn't have this issue.  It worked perfectly over there.


Auto-Tune is on an insert on the actual vocal track itself, not an AUX track 
which is receiving the output through a send.


I'm totally with this poster.  I'm at a complete loss.

Chris.

- Original Message - 
From: "'onlineeagle' via Pro Tools Accessibility" 


To: 
Sent: Thursday, August 27, 2015 8:34 PM
Subject: Hopefully a basic, easy to solve plugin automation problem


OK friends, what am I doing wrong now? I’m trying to automate certain plugin 
parameters but to no avail. I insert an effect, I VO space on the automation 
enable button, I select a parameter then press on add, then OK. I set my 
track to automation write. I start playing the project and manipulating the 
enabled perimeter, and I hear the changes. Sounding good. I then play it 
back and there are no changes. All that happens is that the plugin parameter 
resorts back to the previous value that I started at.


Any help would be very welcome as I’m rather baffled.


Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups 
"Pro Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout. 


--
You received this message because you are subscribed to the Google Groups "Pro Tools 
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.