date:20150828

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.

Re: Isotope RX4?

2015-08-28 Thread Daniel Contreras

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 theGoogle 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

When will this version of PT12 be out?

Chris.

  - Original Message - 
  From: Slau Halatyn 
  To: ptaccess@googlegroups.com 
  Sent: Thursday, August 27, 2015 8:24 PM
  Subject: new accessibility fixes in Pro Tools version 12

  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?

Yeah, see my last message.

Chris.

  - Original Message - 
  From: Chris Smart 
  To: ptaccess@googlegroups.com 
  Sent: Friday, August 28, 2015 10:28 AM
  Subject: Re: Isotope RX4?

  yeah that was an exageration. Talk to Patrick or Derek about iZotope RX for a 
clear picture.

  At 10:54 PM 8/27/2015, you wrote:

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.
  --- 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: Isotope RX4?

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.

Re: new accessibility fixes in Pro Tools version 12

2015-08-28 Thread Dionipher Herrera

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.

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

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.

Re: Isotope RX4?

2015-08-28 Thread Steve Martin

i use RX plenty here. Probably no where near as much as patrick and derek does 
but i have an idea of what is doable with screen reader, Hence why i was 
curious to know just what they considered 100%. 
> On Aug 28, 2015, at 10:28 AM, Chris Smart  wrote:
> 
> yeah that was an exageration. Talk to Patrick or Derek about iZotope RX for a 
> clear picture.
> 
> At 10:54 PM 8/27/2015, you wrote:
>> 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 toptaccess+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 toptaccess+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 toptaccess+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.

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

2015-08-28 Thread Robin Kipp

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.

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.

Re: new accessibility fixes in Pro Tools version 12

2015-08-28 Thread Nickus de Vos

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.

Re: tempo is all fixed now thanks

If you're trying to create a tempo map rather than a static tempo throughout, 
then you'll have to use the conductor to create tempo changes. There's probably 
half a chapter on that somewhere and some of it will refer to tempo markers in 
the ruler which are not accessible right now but the point is, while it's not 
simple enough to outline in too much detail, I'll try to give a basic scenario:

Enable the Conductor.
Figure out what the starting tempo should be.
Go to the start of the session and, using the Static tempo dialog, enter the 
tempo value.
Go to the bar where a tempo change needs to happen and enter a new value and 
Apply it.
repeat this process.
Remember, since the individual tempo events are not accessible in the rulers 
yet, if you make a mistake, immediately undo it before moving on. In other 
words, simply don't make any mistakes. None of us do, right?

Otherwise, a different approach is to have the band track at their own tempo 
and create bar}beat markers after the fact by using the Identify beat command. 
In that scenario, you go to what would be bar 1, Identify the beat with 
command-i and type in what the bar number should be. Move to the next tempo 
change and repeat this and enter what the bar number should be. Double-check as 
you go along to make sure that you're truly getting the bar numbers right or 
else the grid won't line up. Again, make no mistake, literally.

That's the nut shell version. You won't really learn it until you've done it 
and experienced the process. reading the reference guide helps a lot so you 
know what the general procedure and expected results should be.

Hope that helps,

Slau

On Aug 28, 2015, at 12:21 PM, Chad Baker  wrote:

> 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.

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.

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.

Re: entering in tempo values

2015-08-28 Thread Matt Diemert

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.

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.

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.

Re: confirmed plug-in automation issue

2015-08-28 Thread Matt Diemert

Good morning, I will definitely check on this today! We had a few sections that 
we tracked for our tutorials that we actually omitted in the final product, and 
I believe this was one of them! Again, I will also go check on my machine 
running ProTools 10 today. Let you know this afternoon.

Sent from my iPhone

> On Aug 28, 2015, at 10:51 AM, Slau Halatyn  wrote:
> 
> 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

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.

Re: confirmed plug-in automation issue

You got it. Good luck.

On Aug 28, 2015, at 10:13 AM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:

> Thanks for looking into that Slau.
> 
> OK, I’ll continue to follow ProTools development with interest, but I think 
> I’m going to have to start thinking about windows and Reaper for audio work. 
> I am a proffessional musician, but I don’t use ProTools as part of my 
> money-making job, so after careful consideration I can’t justify £3000 on a 
> control surface, just to be able to automate plugins, which was something I 
> could do with any midi control surface using midi learn in sonar ten years 
> ago.
> 
> Thanks again for all your work on PT accessibility.
> Don’t cry folks, I’ll still be around to a
> 
> 
> 
> Sent from my iPhone
> 
>> On 28 Aug 2015, at 14:54, 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: question about click track creation

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.

question about click track creation

2015-08-28 Thread 'onlineeagle' via Pro Tools Accessibility

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.

RE: confirmed plug-in automation issue

2015-08-28 Thread Martin (Punky) Sopart

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.

yeah that was an exageration. Talk to Patrick or Derek about iZotope RX
for a clear picture.
At 10:54 PM 8/27/2015, you wrote:
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.

---

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: confirmed plug-in automation issue

2015-08-28 Thread Brian Howerton

Matt,
I have listened to your tutorial on automation.  I do have a control surface, 
but I do know that it worked for you during your tutorial.  Thanks,
Brian

-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Matt Diemert
Sent: Friday, August 28, 2015 9:18 AM
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.

Re: confirmed plug-in automation issue

2015-08-28 Thread Matt Diemert

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.

Re: confirmed plug-in automation issue

Thanks for looking into that Slau.

OK, I’ll continue to follow ProTools development with interest, but I think I’m 
going to have to start thinking about windows and Reaper for audio work. I am a 
proffessional musician, but I don’t use ProTools as part of my money-making 
job, so after careful consideration I can’t justify £3000 on a control surface, 
just to be able to automate plugins, which was something I could do with any 
midi control surface using midi learn in sonar ten years ago.

Thanks again for all your work on PT accessibility.
Don’t cry folks, I’ll still be around to a



Sent from my iPhone

> On 28 Aug 2015, at 14:54, 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.

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.

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 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...@googlegr

Re: new accessibility fixes in Pro Tools version 12