from:"onlineeagle"

Re: Has anyone observed this with Ivory?

2015-11-26 Thread &#x27;onlineeagle' via Pro Tools Accessibility

OK Christopher, I imported a 90 second midi file into ProTools and had it play 
with the Ivory italian grand. An offline bounce took about 20 to 30 seconds. 

Sent from my iPhone

> On 26 Nov 2015, at 12:04, Christopher-Mark Gilland  
> wrote:
> 
> I already did! try that, and it did absolutely no good.  Are you having this 
> issue?  Are you using a 7200RPM, or greater drive, or a solid state?
>  
> Chris.
>  
> - Original Message -
> From: 'onlineeagle' via Pro Tools Accessibility
> To: ptaccess@googlegroups.com
> Sent: Thursday, November 26, 2015 5:55 AM
> Subject: Re: Has anyone observed this with Ivory?
> 
> Hi Christopher. I was speaking to someone from Ivory a few months back, and 
> he recommended having the Ivory library on an external hard drive. You should 
> be able to just copy the library files over I think. Can't help with the 
> bounce slowness. Maybe try an online bounce. At least then it should only 
> take as long as the song. 
> 
> Sent from my iPhone
> 
>> On 26 Nov 2015, at 02:46, Christopher-Mark Gilland  
>> wrote:
>> 
>> Maybe it's just me, but I just did a session, which literally only have two 
>> tracks in it, not including the master fader.  Both had Ivery instantiated 
>> on them on insert A.  This is the Ivery American Concert D that I'm using.
>>  
>> When I went to offline bounce my session to a interleaved wave 24 bit 48K 
>> file, I noticed that it took for! freaking! ever! to bounce.  I mean, this 
>> thing must a been starting at around 2.2X speed on the bounce, but then 
>> rapidly decreased.  This 4 minute song wound up taking, again, offline, 
>> about 10 minutes to bounce!
>>  
>> I'm just using the default stocked 500GB drive in the mac mini late 2012 
>> model.  I'm running ProTools 12.3, all the session files, and the Ivory 
>> libraries all on the same volume/partition.  Probably not ideal, but it's 
>> all I can do for right now.  NO, this drive isn't a fusion, nor a solid 
>> state.  I'm not sure the RPM speed.  It's whatever the stock drive is that 
>> comes in those things.  I have 8GB ram, and an I5 processor.  El Capitan 
>> 10.11.1.
>>  
>> I've never seen this until I installed Ivory. Yes.  I definitely have 
>> rebooted since installing Ivory.  Still, it's taking this long.
>>  
>> I do! have a USB external hard drive I put move the libraries to, if someone 
>> can tell me how to do that, but I'm not sure how advisable that would be.
>>  
>> Has anyone else seen this after putting Ivory into a session?
>>  
>> 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: Has anyone observed this with Ivory?

2015-11-26 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Christopher. I was speaking to someone from Ivory a few months back, and he 
recommended having the Ivory library on an external hard drive. You should be 
able to just copy the library files over I think. Can't help with the bounce 
slowness. Maybe try an online bounce. At least then it should only take as long 
as the song. 

Sent from my iPhone

> On 26 Nov 2015, at 02:46, Christopher-Mark Gilland  
> wrote:
> 
> Maybe it's just me, but I just did a session, which literally only have two 
> tracks in it, not including the master fader.  Both had Ivery instantiated on 
> them on insert A.  This is the Ivery American Concert D that I'm using.
>  
> When I went to offline bounce my session to a interleaved wave 24 bit 48K 
> file, I noticed that it took for! freaking! ever! to bounce.  I mean, this 
> thing must a been starting at around 2.2X speed on the bounce, but then 
> rapidly decreased.  This 4 minute song wound up taking, again, offline, about 
> 10 minutes to bounce!
>  
> I'm just using the default stocked 500GB drive in the mac mini late 2012 
> model.  I'm running ProTools 12.3, all the session files, and the Ivory 
> libraries all on the same volume/partition.  Probably not ideal, but it's all 
> I can do for right now.  NO, this drive isn't a fusion, nor a solid state.  
> I'm not sure the RPM speed.  It's whatever the stock drive is that comes in 
> those things.  I have 8GB ram, and an I5 processor.  El Capitan 10.11.1.
>  
> I've never seen this until I installed Ivory. Yes.  I definitely have 
> rebooted since installing Ivory.  Still, it's taking this long.
>  
> I do! have a USB external hard drive I put move the libraries to, if someone 
> can tell me how to do that, but I'm not sure how advisable that would be.
>  
> Has anyone else seen this after putting Ivory into a session?
>  
> 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: confirmed plug-in automation issue

2015-08-28 Thread &#x27;onlineeagle' via Pro Tools Accessibility

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.

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

2015-08-28 Thread &#x27;onlineeagle' via Pro Tools Accessibility

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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-08-28 Thread &#x27;onlineeagle' via Pro Tools Accessibility

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

> 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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new accessibility fixes in Pro Tools version 12

2015-08-27 Thread &#x27;onlineeagle' via Pro Tools Accessibility

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.

Hopefully a basic, easy to solve plugin automation problem

2015-08-27 Thread &#x27;onlineeagle' via Pro Tools Accessibility

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.

Re: Revisiting control surfaces. Sorry, I know.

2015-07-31 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Great, thanks Slau.

Sent from my iPhone

> On 30 Jul 2015, at 12:59, Slau Halatyn  wrote:
> 
> For work with Pro Tools, any of the Avid surfaces will yield the best 
> results. While plug-in parameters are automatically mapped, it is possible to 
> create custom maps. The feature is not accessible in the current version of 
> Pro Tools but will be available in the next release. That said, it'll 
> probably take sighted assistance to actually create the custom map because 
> parameters on screen need to be clicked when assigning faders and buttons and 
> , because of the way plug-in parameters have been made accessible, VoiceOver 
> isn't seeing the actual UI element for each parameter but rather its 
> underlying data. Once the map is created, however, it's easy to switch maps 
> and set defaults.
> 
> It seems to me that the best surface for Pro Tools exclusively is either the 
> Artist series or perhaps the S3 which is considerably more expensive but 
> definitely the future of surface technology for Pro Tools.
> 
> 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: Revisiting control surfaces. Sorry, I know.

2015-07-30 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Thanks Martin, and have you found plugin automation fairly straight forward 
with it.

Sent from my iPhone

> On 30 Jul 2015, at 08:09, Martin (Punky) Sopart  wrote:
> 
> Hi!
> 
> In my opinion the Artist Mix has transport buttons when using the shift key 
> with other ones.
> 
> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> Sent: Wednesday, July 29, 2015 9:07 PM
>> To: ptaccess@googlegroups.com
>> Subject: Revisiting control surfaces. Sorry, I know.
>> 
>> So, I know we’ve done this lots before, but I’m back to thinking about 
>> control
>> surfaces. I really can’t work effectively without being able to automate
>> plugins with a control surface, and I really don’t want to abandon ProTools,
>> given that I’m getting pretty clued up about it, and I work pretty quickly 
>> with
>> it. So, I was thinking about the Artist Mix. I know it doesn’t have transport
>> buttons, which is a bit irritating, however I wonder if I am able to use the
>> artist Mix with my BCF control surface, then I could use the BCF2000 as a
>> transport control surface, and maybe even use it for fader and pan
>> automation, and I can use my Artist Mix for pluguin automation. Does that
>> sound plausible? Also, is it easy enough to choose what the faders and knobs
>> automate. In other words, is choosing what the faders do, and what plugin
>> controls easy to achieve with VoiceOver and PT?
>> 
>> Your thoughts are very welcome.
>> 
>> --
>> 
>> David Eagle
>> 
>> Website: http://www.davideagle.co.uk
>> 
>> Follow me on Twitter: http://www.twitter.com/thedavideagle";
>> 
>> --
>> 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: Ivory ii italian grand and uprights presets

2015-07-23 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Scott, a dropbox folder might be a good idea. If there are no other Ivory 
precepts then I shall create some next week, and share them with the list. 
Obviously Matt is more than welcome to put them up on ProTools with speech to. 
Thanks.

Sent from my iPhone

> On 23 Jul 2015, at 05:47, Scott Chesworth  wrote:
> 
> A dropbox folder perhaps?
> 
> I can't recall seeing any Ivory presets floating around publicly other
> than the ones Slau made, which were the American Concert series.
> 
> Scott
> 
> On 7/22/15, 'onlineeagle' via Pro Tools Accessibility
>  wrote:
>> Hi, does anyone have presets for the Ivory ii italian grand and/or uprights?
>> I've had a look on the Protools with Speech presets page but it only seems
>> to have the American concert series. Also, the Protools with Speech presets
>> page doesn't seem to have all the presets provided on this list, given that
>> I and others have submitted a load of Waves presets and Stutter edit
>> presets. I'm wondering if there's a more effective way of sharing them that
>> doesn't rely on when Matt has time to upload them.
>> 
>> 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.

Ivory ii italian grand and uprights presets

2015-07-22 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi, does anyone have presets for the Ivory ii italian grand and/or uprights? 
I've had a look on the Protools with Speech presets page but it only seems to 
have the American concert series. Also, the Protools with Speech presets page 
doesn't seem to have all the presets provided on this list, given that I and 
others have submitted a load of Waves presets and Stutter edit presets. I'm 
wondering if there's a more effective way of sharing them that doesn't rely on 
when Matt has time to upload them. 

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.

A delightful Avid support experience

2015-07-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

I'm sure a lot of you have probably done this before, but today I called up 
Avid support because I didn't have anyone sighted to hand, I'd just formatted 
my computer, and I really could do with cracking on with a ProTools session. 
Without hesitation, they said they were happy to remotely control my comuter 
and do the Ilok activation for me. It took just a couple of minutes and now I'm 
up and running. Jupt thought I'd share this positive news with you all, in case 
you weren't aware of the possibility of this option.

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.

Re: Standing at a crossroads PT or logic in the future?

2015-07-04 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Thanks Scott, I'll give it a look.

Sent from my iPhone

> On 4 Jul 2015, at 03:27, Scott Chesworth  wrote:
> 
> Hi Dave,
> 
> Pitch 'N Time is a third party plugin from Serato. I prefer the audio
> results that gives over elastic audio, but seems the gap has somewhat
> narrowed nowadays, it's primarily just the habit of doing certain
> things certain ways here. Pretty sure Slau has written a post on its
> accessibility, so it'd be worth a search of the archives to uncover
> his wisdom. He is most wise.
> 
> Hth
> 
> Scott
> 
> 
> On 7/3/15, 'onlineeagle' via Pro Tools Accessibility
>  wrote:
>> Thanks Scott. Looks like a combination of Reaper and Protools is probably my
>> overall focus for now, but good to know that accessibility is reasonable in
>> Logic. When you say "pitch time" what exactly are you talking about? I ask
>> because my current solution for time stretching audio is making changes in
>> the tempo ruler. This works great, unless you want to time stretch different
>> tracks to different tempos. I am working on a crazy DJ project, and I'm
>> doing a lot of time stretching on multiple tracks. As for pitch changes, I
>> tend to do that by creating a region, then using the elastic audio window in
>> the clips menu.
>> 
>> Just making sure there itn't a more productive in doing time stretching iq
>> PT. Thanks for your help.
>> 
>> Sent from my iPhone
>> 
>>> On 3 Jul 2015, at 12:35, Scott Chesworth 
>>> wrote:
>>> 
>>> Hi Dave,
>>> 
>>> There's no native support for VST in Logic X. There are wrappers, but
>>> no idea of their accessibility. In any case, the stock synths are
>>> pretty sweet.
>>> 
>>> The MIDI events list isn't accessible yet in terms of VoiceOver
>>> talking, but there's a good walkthrough of how a chap called Gary
>>> Readfern-Grey tweaks his performances without requiring speech
>>> feedback in the archives of the Logic Accessibility Google group.
>>> 
>>> Time stretching sounds about the same in both DAWs from the little
>>> I've played with it. Pitch n Time is still your best bet here IMO.
>>> 
>>> On control surfaces, yes Logic supports a wider range of hardware via
>>> MIDI learn, although I don't think the MIDI learn process itself is
>>> accessible yet. I'd still say the surface integration goes deeper and
>>> is neater in PT, but that could just be me being an old dog being
>>> grumpy about new tricks. I guess once MIDI learn is accessible you'll
>>> be able to get a more definitive answer on that front.
>>> 
>>> Hth a bit
>>> 
>>> Scott
>>> 
>>> On 7/3/15, 'onlineeagle' via Pro Tools Accessibility
>>>  wrote:
>>>> Hi, thanks for all this information. I don't plan on leaving ProTools,
>>>> but
>>>> it might be nice to have another option. Perhaps Logic might work better
>>>> for
>>>> midi and time stretching. Plus, perhaps it also supports VST, and maybe
>>>> even
>>>> works better with a control surface, given that it probably has a midi
>>>> learn
>>>> feature. And I assume that Logic is likely to get more accessible over
>>>> time.
>>>> So perhaps I'll give Logic a spin, and use it in conjunction with
>>>> ProTools.
>>>> Thanks for this.
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 2 Jul 2015, at 22:53, Dionipher Presas Herrera 
>>>>> wrote:
>>>>> 
>>>>> i am interested in mainstage, please can you do a tutorial. thanks
>>>>>> On 02 Jul 2015, at 11:09 pm, 'ashley cox' via Pro Tools Accessibility
>>>>>>  wrote:
>>>>>> 
>>>>>> Perfect. The MainStage and Logic instrument sets are identical. I will
>>>>>> dig in next week and see how i get on. I may develop some tutorials
>>>>>> for
>>>>>> MainStage if anyone is interested.
>>>>>> 
>>>>>> 
>>>>>>> On 2 Jul 2015, at 21:30, Keith Reedy  wrote:
>>>>>>> 
>>>>>>> Ashley,
>>>>>>> 
>>>>>>> MainStage does have a learning curve but not a steep one.  I am told
>>>>>>> that it is pretty much accessible and all of the instruments
>>>>>>> downloaded
>

Re: Standing at a crossroads PT or logic in the future?

2015-07-03 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Thanks Scott. Looks like a combination of Reaper and Protools is probably my 
overall focus for now, but good to know that accessibility is reasonable in 
Logic. When you say "pitch time" what exactly are you talking about? I ask 
because my current solution for time stretching audio is making changes in the 
tempo ruler. This works great, unless you want to time stretch different tracks 
to different tempos. I am working on a crazy DJ project, and I'm doing a lot of 
time stretching on multiple tracks. As for pitch changes, I tend to do that by 
creating a region, then using the elastic audio window in the clips menu.

Just making sure there itn't a more productive in doing time stretching iq PT. 
Thanks for your help.

Sent from my iPhone

> On 3 Jul 2015, at 12:35, Scott Chesworth  wrote:
> 
> Hi Dave,
> 
> There's no native support for VST in Logic X. There are wrappers, but
> no idea of their accessibility. In any case, the stock synths are
> pretty sweet.
> 
> The MIDI events list isn't accessible yet in terms of VoiceOver
> talking, but there's a good walkthrough of how a chap called Gary
> Readfern-Grey tweaks his performances without requiring speech
> feedback in the archives of the Logic Accessibility Google group.
> 
> Time stretching sounds about the same in both DAWs from the little
> I've played with it. Pitch n Time is still your best bet here IMO.
> 
> On control surfaces, yes Logic supports a wider range of hardware via
> MIDI learn, although I don't think the MIDI learn process itself is
> accessible yet. I'd still say the surface integration goes deeper and
> is neater in PT, but that could just be me being an old dog being
> grumpy about new tricks. I guess once MIDI learn is accessible you'll
> be able to get a more definitive answer on that front.
> 
> Hth a bit
> 
> Scott
> 
> On 7/3/15, 'onlineeagle' via Pro Tools Accessibility
>  wrote:
>> Hi, thanks for all this information. I don't plan on leaving ProTools, but
>> it might be nice to have another option. Perhaps Logic might work better for
>> midi and time stretching. Plus, perhaps it also supports VST, and maybe even
>> works better with a control surface, given that it probably has a midi learn
>> feature. And I assume that Logic is likely to get more accessible over time.
>> So perhaps I'll give Logic a spin, and use it in conjunction with ProTools.
>> Thanks for this.
>> 
>> Sent from my iPhone
>> 
>>> On 2 Jul 2015, at 22:53, Dionipher Presas Herrera 
>>> wrote:
>>> 
>>> i am interested in mainstage, please can you do a tutorial. thanks
>>>> On 02 Jul 2015, at 11:09 pm, 'ashley cox' via Pro Tools Accessibility
>>>>  wrote:
>>>> 
>>>> Perfect. The MainStage and Logic instrument sets are identical. I will
>>>> dig in next week and see how i get on. I may develop some tutorials for
>>>> MainStage if anyone is interested.
>>>> 
>>>> 
>>>>> On 2 Jul 2015, at 21:30, Keith Reedy  wrote:
>>>>> 
>>>>> Ashley,
>>>>> 
>>>>> MainStage does have a learning curve but not a steep one.  I am told
>>>>> that it is pretty much accessible and all of the instruments downloaded
>>>>> with MainStage should work with Logic or GarageBand.
>>>>> HTH.
>>>>> kr
>>>>> We print the Bible in Braille,
>>>>> http://biblesfortheblind.org
>>>>> Keith Reedy
>>>>> God gives His best to those who leave the choice with Him.  J Hudson
>>>>> Taylor.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Jul 2, 2015, at 4:02 PM, 'ashley cox' via Pro Tools Accessibility
>>>>>>  wrote:
>>>>>> 
>>>>>> Thanks Keith, this looks great. I’ll definitely be checking this out.
>>>>>> 
>>>>>> On a somewhat related note, Does anyone use MainStage along with
>>>>>> ProTools or Logic? I’d quite like to use MainStage for live
>>>>>> performances. Are their any major accessibility issues there?
>>>>>> (apologies for the somewhat off-topic question)
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On 2 Jul 2015, at 19:15, Keith Reedy  wrote:
>>>>>>> 
>>>>>>> Ashley,
>>>>>>> 
>>>>>>> Here is a link for info that will give yo

Re: Standing at a crossroads PT or logic in the future?

2015-07-03 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi, thanks for all this information. I don't plan on leaving ProTools, but it 
might be nice to have another option. Perhaps Logic might work better for midi 
and time stretching. Plus, perhaps it also supports VST, and maybe even works 
better with a control surface, given that it probably has a midi learn feature. 
And I assume that Logic is likely to get more accessible over time. So perhaps 
I'll give Logic a spin, and use it in conjunction with ProTools. Thanks for 
this.

Sent from my iPhone

> On 2 Jul 2015, at 22:53, Dionipher Presas Herrera  wrote:
> 
> i am interested in mainstage, please can you do a tutorial. thanks
>> On 02 Jul 2015, at 11:09 pm, 'ashley cox' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Perfect. The MainStage and Logic instrument sets are identical. I will dig 
>> in next week and see how i get on. I may develop some tutorials for 
>> MainStage if anyone is interested.
>> 
>> 
>>> On 2 Jul 2015, at 21:30, Keith Reedy  wrote:
>>> 
>>> Ashley,
>>> 
>>> MainStage does have a learning curve but not a steep one.  I am told that 
>>> it is pretty much accessible and all of the instruments downloaded with 
>>> MainStage should work with Logic or GarageBand.
>>> HTH.
>>> kr
>>> We print the Bible in Braille,
>>> http://biblesfortheblind.org
>>> Keith Reedy
>>> God gives His best to those who leave the choice with Him.  J Hudson Taylor.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
 On Jul 2, 2015, at 4:02 PM, 'ashley cox' via Pro Tools Accessibility 
  wrote:
 
 Thanks Keith, this looks great. I’ll definitely be checking this out.
 
 On a somewhat related note, Does anyone use MainStage along with ProTools 
 or Logic? I’d quite like to use MainStage for live performances. Are their 
 any major accessibility issues there? (apologies for the somewhat 
 off-topic question)
 
 
 
> On 2 Jul 2015, at 19:15, Keith Reedy  wrote:
> 
> Ashley,
> 
> Here is a link for info that will give you a start with Logic,
> http://icanworkthisthing.com/docs/mac_with_voiceover/audio/Logic%20With%20Voiceover/
> HTH.
> Keith Reedy
> We print the Bible in Braille,
> http://biblesfortheblind.org
> Keith Reedy
> God gives His best to those who leave the choice with Him.  J Hudson 
> Taylor.
> 
> 
> 
> 
> 
> 
>> On Jul 2, 2015, at 9:03 AM, 'ashley cox' via Pro Tools Accessibility 
>>  wrote:
>> 
>> What’s the best resource for getting started with logic accessibility? I 
>> do have Logic Pro X, purely because i needed it to open some projects. 
>> I’d love to learn how to use it properly but unsure where is best to 
>> start. Any suggestions? Is there anything that we can’t do with logic 
>> that makes using it a deal breaker?
>> 
>> 
>>> On 2 Jul 2015, at 13:59, Krister Ekstrom  
>>> wrote:
>>> 
>>> Hello good people on both lists.
>>> Firstly i’m sorry for the cross post but as it pertains to both lists i 
>>> thought it best to post to both lists.
>>> I currently run Protools v11.3 with no problems, however v12 is now out 
>>> and when the next major upgrade comes, i’ve heard a rumor about the 
>>> Digi003 possibly not being supported by it,which leads me to wonder 
>>> should i take the plunge, sell off my Digi003 while there’s still time 
>>> and try learning logic? I’ve heard varying stories about how accessible 
>>> Logic is. It’s apparently got a truckload of soft synths and the 
>>> Drummer sounds cool to me but is the learning curve worth the struggle? 
>>> Much of the reason why i ask is that getting a new control surface that 
>>> is as good as the Digi003 is is way out of the question for me with my 
>>> budget so just wondering what to do.
>>> Thanks for taking the time to read this question that maybe just silly 
>>> but if anyone wants to give advise i’d be grateful.
>>> /Krister
>>> 
>>> -- 
>>> 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.

Re: switching mix to mono

2015-06-19 Thread &#x27;onlineeagle' via Pro Tools Accessibility

'Actually, I don't think my bus idea would work, as you'd have to choose 
between the left chanel or right channel being represented. You could however 
simply move both pan sliders on the master fader to the centre. That will do 
the trick.

Sent from my iPhone

> On 18 Jun 2015, at 19:18, byron harden  wrote:
> 
> got it
>> On Jun 18, 2015, at 1:06 PM, Chad Morrison  
>> wrote:
>> 
>> i think and please some body correct me if I’m wrong you could just insert 
>> The AIR Stereo width plug on your master fader and with out selecting any 
>> presets turn the master width to 0 and just bypass it when you want stereo 
>> again.
>>> On Jun 16, 2015, at 2:27 PM, Steve Sparrow  wrote:
>>> 
>>> Hi, is there any way of tgetting a stereo mix to play in mono in p t. I 
>>> would like to do a lot more mixing in mono at times to make sure things are 
>>> sitting nicely. This was very easy to do in sonar, But have not found a way 
>>> around this in p t. or is it possible i need another plugin to do this.
>>> I know some people start there mix with all the pan pots set in the centre. 
>>> I can do this, but it would be very usefull to be able to flick from stereo 
>>> to mono if possible.
>>> 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.
> 
> -- 
> 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: Artis mix control surface, or mackie or what?

2015-06-17 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Kevin, according to what I've read, the HUI mode of the BCF does not allow 
for plugin automation in ProTools, but only track pan, volume, mute, solo and 
transport controls, this includes busses, and possibly sends. If the XTouch 
uses a different HUI mode to the BCF then perhaps this is why the XTouch will 
allow plugin automation. If you've managed to achieve this with the XTouch then 
I'd be really interested to hear more, as lack of control surface pkugin 
automation is a bit limiting. I haven't managed to find anything on the 
Internet confirming that plugin automation is achievable with the XTouch. I 
suppose a call to Behringer might be the answer to determining this once and 
for all, unless we know of someone who is automating plugins with the XTouch. 
Here's hoping you're right though Kevin. 

Sent from my iPhone

> On 17 Jun 2015, at 15:05, Kevin Reeves  wrote:
> 
> The X touch runs on Mackie Hui, so plugin automation is definitely possible. 
> Not sure why the BCF won't let you automate plugs, except for the fact that 
> it doesn't have touch sensitive faders, which would allow you to override 
> automation moves.
> 
> Kevin
> 
> -- 
> 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: Artis mix control surface, or mackie or what?

2015-06-17 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Ramy, the limitation with he BCF seems to be that you can't automate plugins 
with it. I've done a Google search on the X Touch, and there is nothing to 
suggest that it will allow you to automate plugin controls. So I'm not sure 
whether you'd find much of an improvement between the XTouch and the BCF.

Sent from my iPhone

> On 17 Jun 2015, at 13:19, Kevin Reeves  wrote:
> 
> Woops. Sorry about that. My bad.
> 
> Kevin
>> On 6/17/2015 7:25 AM, Scott Chesworth wrote:
>> Just a slight correction, seems like the X 32 Producer has 17
>> motorized faders, not 8. I'm hoping that their next move will be an
>> X-touch sized thing with decent pre's and a few MIDI ports. That'd
>> probably be the point where I'd ditch having a separate surface and
>> I/O for mobile recording at least.
>> 
>> Has anybody taken a poke at the Behringer app that pairs up with the
>> X32 gear using VoiceOver?
>> 
>> Scott
>> 
>>> On 6/17/15, Kevin Reeves  wrote:
>>> The X touch is not a touch screen. It's a full 8 fader surface.
>>> Also, it has better components than the BCF. The BCF doesn't support
>>> touch automation, so you end up fighting with the fader if you're trying
>>> to rewrite automation moves.
>>> 
>>> The BCF was made at a time when Behrenger was known for making cheap
>>> hardware. There's been a shakeup at the company, and as a few years ago,
>>> the build quality of their products, especially anything related to the
>>> X32 series, which includes the X Touch control surface, has greatly
>>> improved.
>>> Speaking of the X32, that is another option for a control
>>> surface/interface combo. The X32 producer, which is the same price as 1
>>> of the artist mix surfaces, gives you 8 motorized faders, 16 xlr ins, a
>>> ton of routing options, ,effects, etc. As a guy who once advised folks
>>> to never let Behrenger become part of the signal chain, I'm actually
>>> considering this as my main studio board because of the feature set and
>>> Midas Mic Pres.
>>> Hope this helps.
>>> 
>>> Kevin
>>> 
>>> --
>>> 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: switching mix to mono

2015-06-16 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Or you could create a mono bus, and set the output of your master bus to that 
mono bus. I think should work.

Sent from my iPhone

> On 16 Jun 2015, at 22:22, Slau Halatyn  wrote:
> 
> Usually, control surfaces will feature a mono button for quick switching. I 
> believe there's a plug-in or two that'll do just mono switching but I don't 
> recall the names. Google will know.
> 
> Slau
> 
>> On Jun 16, 2015, at 3:27 PM, Steve Sparrow  wrote:
>> 
>> Hi, is there any way of tgetting a stereo mix to play in mono in p t. I 
>> would like to do a lot more mixing in mono at times to make sure things are 
>> sitting nicely. This was very easy to do in sonar, But have not found a way 
>> around this in p t. or is it possible i need another plugin to do this.
>> I know some people start there mix with all the pan pots set in the centre. 
>> I can do this, but it would be very usefull to be able to flick from stereo 
>> to mono if possible.
>> 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.

-- 
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: Artis mix control surface, or mackie or what?

2015-06-16 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Ramy, "built like a tank" is an English expression. It refers to the 
military vehicle called a tank that is built to be strong, sturdy, solid and 
durable. So when Kevin says the Macki controlers are built like a tank, he is 
saying that the Macki control surfaces are strong, sturdy, solid, durable and 
built to last. Hope this explanation helps.

Sent from my iPhone

> On 16 Jun 2015, at 21:31, Kevin Reeves  wrote:
> 
> I vote either Mackie or the new Behrenger X Touch control surface.
> The artist mix doesn't give you enough features for the huge price tag.
> The Mackie control is built like a tank, the Behrenger X touch has the same 
> faders found in the x32, which tons of pros are really happy with.
> I had to set up yet another artist mix for a client last week. Still hate it.
> 
> Kevin
> 
> -- 
> 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: C couple of queries about volume

2015-06-13 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Alas, it seems t:at the BCF isn't able to support plugin automation in 
ProTools, at least according to the many articles and forum threads I've looked 
at. i suppose when I talked about Protools not having a learn facility, I meant 
a Midi Learn facility, which is a big shame. My solution at the moment is to 
use Reaper souly for those times when I really need to use a control surface to 
do plugin automation. This isn't too much of an issue, given that Reaper also 
supports VST, whereas Protools doesn't. 
Anyway, thanks for all your help.

Sent from my iPhone

> On 13 Jun 2015, at 05:48, TheOreoMonster  wrote:
> 
> If memory serves correct, ProTOols supports the HUI protocol only and not 
> general midi. SO in order to have a control surface work in PT it has have 
> some sort of HUI mode. The avid surfaces usually come pretty much ready to 
> go, but in fader flip mode i believe  you should be able to map a HUI surface 
> to control things like a plug in. As scott said before if there is a way to 
> do  this with the BCF2000 google could probably get one pointed in the right 
> direction. 
> 
>> On Jun 12, 2015, at 9:51 AM, Slau Halatyn  wrote:
>> 
>> I've never had the need to do a custom map of controls but the process is 
>> quite straightforward, just as you've described. Now, you specifically 
>> mentioned Avid control surfaces in your previous message and that made me 
>> have a second thought about what I said. It's entirely possible that the 
>> custom mapping facility, which undoubtedly exists, is specific to supported 
>> control surfaces. I'm not certain whether that applies to generic MIDI 
>> controllers like keyboards with a bank of continuous controller sliders. 
>> Again, I've never had the need to set up anything along those lines so I 
>> might be mistaken about the current state of generic MIDI mapping. I should 
>> look into it for my own general knowledge.
>> 
>> Slau
>> 
>>> On Jun 12, 2015, at 8:30 AM, 'onlineeagle' via Pro Tools Accessibility 
>>>  wrote:
>>> 
>>> Now that is interesting Slau. From what I've gathered from researching on 
>>> the Internet that Midi Learn was discontinued after ProTools 9. So 
>>> apologies if I've been misinforming the list on this one. In Sonar, you 
>>> could essentially enter on a plugin control, select midi learn, and then 
>>> twiddle that knob, fader or press the button that you wish to assign to 
>>> that control. This seems like the most straight forward and logical 
>>> solution.
>>> 
>>> How, out of interest, do you tell the Avid control surfaces to control 
>>> plugin controls. Basically, is it easy to achieve?
>>> 
>>> Sent from my iPhone
>>> 
>>>> On 12 Jun 2015, at 00:55, Slau Halatyn  wrote:
>>>> 
>>>> Pro Tools does, in fact, have a MIDI learn function, for the record. The 
>>>> UI elements are not yet accessible. Even if they were, however, it would 
>>>> probably take some sighted assistance to set up a surface because the 
>>>> clues to what is being mapped is very visual.
>>>> 
>>>> Slau
>>>> 
>>>>> On Jun 11, 2015, at 7:47 PM, 'onlineeagle' via Pro Tools Accessibility 
>>>>>  wrote:
>>>>> 
>>>>> Hi Brian, I'd love to be able to help you more, but you're using the BCF 
>>>>> as much as I am. I only do panning and volume. I don't think it's 
>>>>> possible to minipulate plugin controls with it unfortunately, or at least 
>>>>> if there is then I've no idea how. Sadly Prrtools doesn't have a midi 
>>>>> learn function like every other DAW, which is a bit frustrating, and I 
>>>>> imagine is a restriction deliberately introduced to encourage people to 
>>>>> buy Avid's own control surfaces where plugin automation is possible. 
>>>>> 
>>>>> Sent from my iPhone
>>>>> 
>>>>>> On 11 Jun 2015, at 17:29, Brian Howerton  wrote:
>>>>>> 
>>>>>> I would love to get your thoughts on the BCF 2000.  I’ve just been using 
>>>>>> it for setting levels and panning in pro tools, but would love to dig in 
>>>>>> deeper to using this control surface with pro tools.  Feel free to write 
>>>>>> me off-list.  Thanks,
>>>>>> Brian
>>>>>>> On Jun 11, 2015, at 5:59 AM, 'onlineeagle' via Pro Tools Accessibility 
>>>

Re: C couple of queries about volume

2015-06-12 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Now that is interesting Slau. From what I've gathered from researching on the 
Internet that Midi Learn was discontinued after ProTools 9. So apologies if 
I've been misinforming the list on this one. In Sonar, you could essentially 
enter on a plugin control, select midi learn, and then twiddle that knob, fader 
or press the button that you wish to assign to that control. This seems like 
the most straight forward and logical solution.

How, out of interest, do you tell the Avid control surfaces to control plugin 
controls. Basically, is it easy to achieve?

Sent from my iPhone

> On 12 Jun 2015, at 00:55, Slau Halatyn  wrote:
> 
> Pro Tools does, in fact, have a MIDI learn function, for the record. The UI 
> elements are not yet accessible. Even if they were, however, it would 
> probably take some sighted assistance to set up a surface because the clues 
> to what is being mapped is very visual.
> 
> Slau
> 
>> On Jun 11, 2015, at 7:47 PM, 'onlineeagle' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Hi Brian, I'd love to be able to help you more, but you're using the BCF as 
>> much as I am. I only do panning and volume. I don't think it's possible to 
>> minipulate plugin controls with it unfortunately, or at least if there is 
>> then I've no idea how. Sadly Prrtools doesn't have a midi learn function 
>> like every other DAW, which is a bit frustrating, and I imagine is a 
>> restriction deliberately introduced to encourage people to buy Avid's own 
>> control surfaces where plugin automation is possible. 
>> 
>> Sent from my iPhone
>> 
>>> On 11 Jun 2015, at 17:29, Brian Howerton  wrote:
>>> 
>>> I would love to get your thoughts on the BCF 2000.  I’ve just been using it 
>>> for setting levels and panning in pro tools, but would love to dig in 
>>> deeper to using this control surface with pro tools.  Feel free to write me 
>>> off-list.  Thanks,
>>> Brian
>>>> On Jun 11, 2015, at 5:59 AM, 'onlineeagle' via Pro Tools Accessibility 
>>>>  wrote:
>>>> 
>>>> Hi Slau, I assume Flip Mode is a control surface specific thing? I'm just 
>>>> using a Beringer BCF at the moment. However, the clip gain feature seems 
>>>> to be perfect for my needs. I must give Keyboard maestro my attention at 
>>>> some point. Thanks.
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 10 Jun 2015, at 21:02, Slau Halatyn  wrote:
>>>>> 
>>>>> Ah, I'm sorry but I neglected to point out that you need to use a control 
>>>>> surface to change that value for now. It's possible to set a hot spot 
>>>>> with a program like Keyboard Maestro but I haven't gotten around to doing 
>>>>> that because I don't use the Trim plug-in. At any rate, it's likely to be 
>>>>> the very first encoder knob or fader if you're in flip mode.
>>>>> 
>>>>> HTH,
>>>>> 
>>>>> Slau
>>>>> 
>>>>>> On Jun 10, 2015, at 2:55 PM, 'onlineeagle' via Pro Tools Accessibility 
>>>>>>  wrote:
>>>>>> 
>>>>>> Hi Slau, it appears that there is a trim plugin, but I don't seem to be 
>>>>>> able to change the value of the paramiter which I assume is volume, 
>>>>>> given it's 0 DB reading. I can mute lept and right channels and invert 
>>>>>> the phaze, but the volume slider remains fixed. Asfor clip gain, I can't 
>>>>>> find a way to adjumt that anywhere. The only other solution could be to 
>>>>>> put each track I want to adjust on a seperate bus, and then I get a make 
>>>>>> shift work around. 
>>>>>> 
>>>>>> Sent from my iPhone
>>>>>> 
>>>>>>> On 10 Jun 2015, at 19:22, Slau Halatyn  wrote:
>>>>>>> 
>>>>>>> First of all, if you're dealing with tracks that contain multiple 
>>>>>>> clips, forget clip gain. The Trim plug-in does what you're looking to 
>>>>>>> do. Thing is, I could be mistaken but it might be an HD feature only. 
>>>>>>> It's been years since I've used Pro Tools vanilla so I honestly don't 
>>>>>>> know for sure. That said, the Trim plug-in allows you to trim each 
>>>>>>> track just as you would with a console with tape machine returns. If 
>>

Re: C couple of queries about volume

2015-06-11 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Brian, I'd love to be able to help you more, but you're using the BCF as 
much as I am. I only do panning and volume. I don't think it's possible to 
minipulate plugin controls with it unfortunately, or at least if there is then 
I've no idea how. Sadly Prrtools doesn't have a midi learn function like every 
other DAW, which is a bit frustrating, and I imagine is a restriction 
deliberately introduced to encourage people to buy Avid's own control surfaces 
where plugin automation is possible. 

Sent from my iPhone

> On 11 Jun 2015, at 17:29, Brian Howerton  wrote:
> 
> I would love to get your thoughts on the BCF 2000.  I’ve just been using it 
> for setting levels and panning in pro tools, but would love to dig in deeper 
> to using this control surface with pro tools.  Feel free to write me 
> off-list.  Thanks,
> Brian
>> On Jun 11, 2015, at 5:59 AM, 'onlineeagle' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Hi Slau, I assume Flip Mode is a control surface specific thing? I'm just 
>> using a Beringer BCF at the moment. However, the clip gain feature seems to 
>> be perfect for my needs. I must give Keyboard maestro my attention at some 
>> point. Thanks.
>> 
>> Sent from my iPhone
>> 
>>> On 10 Jun 2015, at 21:02, Slau Halatyn  wrote:
>>> 
>>> Ah, I'm sorry but I neglected to point out that you need to use a control 
>>> surface to change that value for now. It's possible to set a hot spot with 
>>> a program like Keyboard Maestro but I haven't gotten around to doing that 
>>> because I don't use the Trim plug-in. At any rate, it's likely to be the 
>>> very first encoder knob or fader if you're in flip mode.
>>> 
>>> HTH,
>>> 
>>> Slau
>>> 
>>>> On Jun 10, 2015, at 2:55 PM, 'onlineeagle' via Pro Tools Accessibility 
>>>>  wrote:
>>>> 
>>>> Hi Slau, it appears that there is a trim plugin, but I don't seem to be 
>>>> able to change the value of the paramiter which I assume is volume, given 
>>>> it's 0 DB reading. I can mute lept and right channels and invert the 
>>>> phaze, but the volume slider remains fixed. Asfor clip gain, I can't find 
>>>> a way to adjumt that anywhere. The only other solution could be to put 
>>>> each track I want to adjust on a seperate bus, and then I get a make shift 
>>>> work around. 
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On 10 Jun 2015, at 19:22, Slau Halatyn  wrote:
>>>>> 
>>>>> First of all, if you're dealing with tracks that contain multiple clips, 
>>>>> forget clip gain. The Trim plug-in does what you're looking to do. Thing 
>>>>> is, I could be mistaken but it might be an HD feature only. It's been 
>>>>> years since I've used Pro Tools vanilla so I honestly don't know for 
>>>>> sure. That said, the Trim plug-in allows you to trim each track just as 
>>>>> you would with a console with tape machine returns. If you want to adjust 
>>>>> a track's output across the board, so to speak, you can do that with the 
>>>>> volume parameter of the Trim plug-in.
>>>>> 
>>>>> HTH,
>>>>> 
>>>>> Slau
>>>>>  
>>>>>> On Jun 10, 2015, at 5:22 AM, 'onlineeagle' via Pro Tools Accessibility 
>>>>>>  wrote:
>>>>>> 
>>>>>>> 
>>>>>>> Hi, thanks for replying. I couldn't work out how to apply clip gain. 
>>>>>>> There's a gain plugin in the Audio Suite, but I dont think that's 
>>>>>>> accessible. Plus, I get a message about audio handles being disabled 
>>>>>>> due to how processing is set up apparently. As for a trim plugin, I've 
>>>>>>> not seen that. I'm going to ghave a full readup of the manual on a long 
>>>>>>> journey I've got coming up, but the manual often speaks in visual 
>>>>>>> language, so I'm not sure how useful that'll be. Any help 'on this is 
>>>>>>> very welcome. Thanks a lot. 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Pro Tools Accessibility" group.
>>>>>> To unsubscribe from t

Re: C couple of queries about volume

2015-06-11 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Slau, I assume Flip Mode is a control surface specific thing? I'm just using 
a Beringer BCF at the moment. However, the clip gain feature seems to be 
perfect for my needs. I must give Keyboard maestro my attention at some point. 
Thanks.

Sent from my iPhone

> On 10 Jun 2015, at 21:02, Slau Halatyn  wrote:
> 
> Ah, I'm sorry but I neglected to point out that you need to use a control 
> surface to change that value for now. It's possible to set a hot spot with a 
> program like Keyboard Maestro but I haven't gotten around to doing that 
> because I don't use the Trim plug-in. At any rate, it's likely to be the very 
> first encoder knob or fader if you're in flip mode.
> 
> HTH,
> 
> Slau
> 
>> On Jun 10, 2015, at 2:55 PM, 'onlineeagle' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Hi Slau, it appears that there is a trim plugin, but I don't seem to be able 
>> to change the value of the paramiter which I assume is volume, given it's 0 
>> DB reading. I can mute lept and right channels and invert the phaze, but the 
>> volume slider remains fixed. Asfor clip gain, I can't find a way to adjumt 
>> that anywhere. The only other solution could be to put each track I want to 
>> adjust on a seperate bus, and then I get a make shift work around. 
>> 
>> Sent from my iPhone
>> 
>>> On 10 Jun 2015, at 19:22, Slau Halatyn  wrote:
>>> 
>>> First of all, if you're dealing with tracks that contain multiple clips, 
>>> forget clip gain. The Trim plug-in does what you're looking to do. Thing 
>>> is, I could be mistaken but it might be an HD feature only. It's been years 
>>> since I've used Pro Tools vanilla so I honestly don't know for sure. That 
>>> said, the Trim plug-in allows you to trim each track just as you would with 
>>> a console with tape machine returns. If you want to adjust a track's output 
>>> across the board, so to speak, you can do that with the volume parameter of 
>>> the Trim plug-in.
>>> 
>>> HTH,
>>> 
>>> Slau
>>>  
>>>> On Jun 10, 2015, at 5:22 AM, 'onlineeagle' via Pro Tools Accessibility 
>>>>  wrote:
>>>> 
>>>>> 
>>>>> Hi, thanks for replying. I couldn't work out how to apply clip gain. 
>>>>> There's a gain plugin in the Audio Suite, but I dont think that's 
>>>>> accessible. Plus, I get a message about audio handles being disabled due 
>>>>> to how processing is set up apparently. As for a trim plugin, I've not 
>>>>> seen that. I'm going to ghave a full readup of the manual on a long 
>>>>> journey I've got coming up, but the manual often speaks in visual 
>>>>> language, so I'm not sure how useful that'll be. Any help 'on this is 
>>>>> very welcome. Thanks a lot. 
>>>> 
>>>> 
>>>> -- 
>>>> 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: C couple of queries about volume

2015-06-11 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Chuck' yes, I agree, Matt's Protools With Speech course is great. I assume 
this video is a fairly new edition to their training, as I don't remember 
seeing it a few months ago. Thanks for the link. It's going to be a great help.

Sent from my iPhone

> On 10 Jun 2015, at 21:49, CHUCK REICHEL  
> wrote:
> 
> Hi eagle,
> Glad that worked for you. :)
> I highly recommend Matt's course for anybody digging in to PT.
> As for trimming it looks like Clip Gain is the more eloquent method to get 
> the job done.
> When I had my 2 inch machine and Sound work shoppe desk, trim was the go to 
> for that but clip gain avoids automation for the most part.
> Talk soon
> Chuck
> 
> 
> CHUCK REICHEL
> soundpicturerecord...@gmail.com
> www.SoundPictureRecording.com
> 954-742-0019
> Isaiah 26 : 3
>  Thou wilt keep him in perfect peace, whose mind is stayed on thee: because 
> he trusteth in thee.
> 
> In GOD I Trust
> 
>> On Jun 10, 2015, at 3:32 PM, 'onlineeagle' via Pro Tools Accessibility wrote:
>> 
>> Wonderful, thanms so much for that Chuck. Works beautifully. 
>> 
>> Sent from my iPhone
>> 
>>> On 10 Jun 2015, at 19:59, CHUCK REICHEL  
>>> wrote:
>>> 
>>> Ahoy!
>>> Check out this video from Matt about clip gain below;
>>> https://www.youtube.com/watch?v=Sk7qGWUbWJ0
>>> Happy gain staging! :)
>>> Chuck
>>> 
>>>> On Jun 10, 2015, at 2:40 PM, John André Lium-Netland wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I assume that if you make a copy of the track in the playlist and 
>>>> consolidate this track, you will be able to use Clip gain to do minor 
>>>> adjustments for the whole track, and still have your automation intact…  
>>>> If you don't need the uncosolidated track, you can simply consolidate the 
>>>> actual track without creating a copy in the playlist.
>>>> 
>>>> Best,
>>>> John André
>>>> 
>>>> -- 
>>>> 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: C couple of queries about volume

2015-06-10 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Brian, I had the same problem. Go to system preferences, tab to mission 
control. There is a keyboard shortcut set to control and down arrow, which also 
sings to correspond to control shift and down arrow. VO Space on this shortcut 
and press down arrow until you hear, dash. That should solve the problem.

Sent from my iPhone

> On 10 Jun 2015, at 20:37, Brian Howerton  wrote:
> 
> When I try this, my mission control is being launched when I do the control 
> shift up error.  Any suggestions?
> Brian
>> On Jun 10, 2015, at 3:32 PM, 'onlineeagle' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Wonderful, thanms so much for that Chuck. Works beautifully. 
>> 
>> Sent from my iPhone
>> 
>>> On 10 Jun 2015, at 19:59, CHUCK REICHEL  
>>> wrote:
>>> 
>>> Ahoy!
>>> Check out this video from Matt about clip gain below;
>>> https://www.youtube.com/watch?v=Sk7qGWUbWJ0
>>> Happy gain staging! :)
>>> Chuck
>>> 
>>>> On Jun 10, 2015, at 2:40 PM, John André Lium-Netland wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I assume that if you make a copy of the track in the playlist and 
>>>> consolidate this track, you will be able to use Clip gain to do minor 
>>>> adjustments for the whole track, and still have your automation intact…  
>>>> If you don't need the uncosolidated track, you can simply consolidate the 
>>>> actual track without creating a copy in the playlist.
>>>> 
>>>> Best,
>>>> John André
>>>> 
>>>> -- 
>>>> 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: C couple of queries about volume

2015-06-10 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Wonderful, thanms so much for that Chuck. Works beautifully. 

Sent from my iPhone

> On 10 Jun 2015, at 19:59, CHUCK REICHEL  
> wrote:
> 
> Ahoy!
> Check out this video from Matt about clip gain below;
> https://www.youtube.com/watch?v=Sk7qGWUbWJ0
> Happy gain staging! :)
> Chuck
> 
>> On Jun 10, 2015, at 2:40 PM, John André Lium-Netland wrote:
>> 
>> Hi,
>> 
>> I assume that if you make a copy of the track in the playlist and 
>> consolidate this track, you will be able to use Clip gain to do minor 
>> adjustments for the whole track, and still have your automation intact…  If 
>> you don't need the uncosolidated track, you can simply consolidate the 
>> actual track without creating a copy in the playlist.
>> 
>> Best,
>> John André
>> 
>> -- 
>> 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: C couple of queries about volume

2015-06-10 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi John, I probably could get away with using clip gain, but I can't find out 
how to actually go about using it. Any ideas? Thanks. 

Sent from my iPhone

> On 10 Jun 2015, at 19:40, John André Lium-Netland  
> wrote:
> 
> Hi,
> 
> I assume that if you make a copy of the track in the playlist and consolidate 
> this track, you will be able to use Clip gain to do minor adjustments for the 
> whole track, and still have your automation intact…  If you don't need the 
> uncosolidated track, you can simply consolidate the actual track without 
> creating a copy in the playlist.
> 
> Best,
> John André
> 
> -- 
> 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: C couple of queries about volume

2015-06-10 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Slau, it appears that there is a trim plugin, but I don't seem to be able to 
change the value of the paramiter which I assume is volume, given it's 0 DB 
reading. I can mute lept and right channels and invert the phaze, but the 
volume slider remains fixed. Asfor clip gain, I can't find a way to adjumt that 
anywhere. The only other solution could be to put each track I want to adjust 
on a seperate bus, and then I get a make shift work around. 

Sent from my iPhone

> On 10 Jun 2015, at 19:22, Slau Halatyn  wrote:
> 
> First of all, if you're dealing with tracks that contain multiple clips, 
> forget clip gain. The Trim plug-in does what you're looking to do. Thing is, 
> I could be mistaken but it might be an HD feature only. It's been years since 
> I've used Pro Tools vanilla so I honestly don't know for sure. That said, the 
> Trim plug-in allows you to trim each track just as you would with a console 
> with tape machine returns. If you want to adjust a track's output across the 
> board, so to speak, you can do that with the volume parameter of the Trim 
> plug-in.
> 
> HTH,
> 
> Slau
>  
>> On Jun 10, 2015, at 5:22 AM, 'onlineeagle' via Pro Tools Accessibility 
>>  wrote:
>> 
>>> 
>>> Hi, thanks for replying. I couldn't work out how to apply clip gain. 
>>> There's a gain plugin in the Audio Suite, but I dont think that's 
>>> accessible. Plus, I get a message about audio handles being disabled due to 
>>> how processing is set up apparently. As for a trim plugin, I've not seen 
>>> that. I'm going to ghave a full readup of the manual on a long journey I've 
>>> got coming up, but the manual often speaks in visual language, so I'm not 
>>> sure how useful that'll be. Any help 'on this is very welcome. Thanks a 
>>> lot. 
>> 
>> 
>> -- 
>> 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: C couple of queries about volume

2015-06-10 Thread &#x27;onlineeagle' via Pro Tools Accessibility

> 
> Hi, thanks for replying. I couldn't work out how to apply clip gain. There's 
> a gain plugin in the Audio Suite, but I dont think that's accessible. Plus, I 
> get a message about audio handles being disabled due to how processing is set 
> up apparently. As for a trim plugin, I've not seen that. I'm going to ghave a 
> full readup of the manual on a long journey I've got coming up, but the 
> manual often speaks in visual language, so I'm not sure how useful that'll 
> be. Any help 'on this is very welcome. Thanks a lot. 

-- 
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: Having a bit of a struggle changing the tempo of audio

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi, here's what I did to finally get it working like I wanted. Conductor track 
is inabled it the midi cluster. I make sure that the audio track I want to  
time change is selected first. I also make sure that elastic audio is enabled 
on that track, and that that it's set to ticks. I then go to the ruler and 
select tempo. Now I can VO-space on the tempo ruler and change the time of the 
audio which will apply itself to my selection, from the chosen start to end 
time. And I can make as many changes as I like. Hope this description makes 
sense. Thanks for all your help.

Sent from my iPhone

> On 8 Jun 2015, at 19:48, Michael lockett  wrote:
> 
> Hi,
> 
> Hi,
> you can do this by changing  the desired track for editing  from sample to 
> ticks,
> set elastic audio to polyphonic,
> 
> under track view change the view to warp,
> go to the transport cluster, under  midi change the tempo, 
> Make sure the conductor track isn’t selected…
> Hope this helps
>> On Jun 8, 2015, at 12:42 PM, Poppa Bear  wrote:
>> 
>> If you have a chance, perhaps you can outline your steps for reference? It 
>> may be the same elastic audio steps that have been posted on the list 
>> before, but at the same time, you may have taken a slightly different 
>> approach. 
>> 
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
>> Sent: Monday, June 08, 2015 8:55 AM
>> To: ptaccess@googlegroups.com
>> Subject: Elastic audio revisited
>> 
>> Hi, I would ideally have added this to the thread I created, but I dn't know 
>> how to do that when no one else has yet replied. It seems as if the issue 
>> was that I had conductor selected in the midi cluster transport view. When 
>> that was unticked it' all worked fine. I am trying to alter the tempo of 
>> some classical music so that it aligns to a click track. I don't seem to be 
>> able to make the necessary changes to th audio's length while the click 
>> track remains constant, but I have mixed down the click track and should be 
>> able to import the audio of the click and alter the classical piece's tempo 
>> while the bounced down click track is playing unaltered. Hope that makes 
>> sense. Anyway, I think it's all solved. 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.

Sent from my iPhone

> On 8 Jun 2015, at 19:28, Michael lockett  wrote:
> 
> 
> Hi,
> you can do this by changing  the desired track for editing  from sample to 
> ticks,
> set elastic audio to polyphonic,
> 
> under track view change the view to warp,
> go to the transport cluster, under  midi change the tempo, 
> Make sure the conductor track isn’t selected…
> Hope this helps
>> On Jun 8, 2015, at 9:27 AM, onlineeagle  wrote:
>> 
>> 
>> Hi, I've managed to do this before but it was awhile ago and I can't seem to 
>> do it now. I want to change 
>> the speed of an audio track. In fact, I need to make multiple changes 
>> throughout the track. I select the track I want to change. I make a time 
>> selection. I make sure that I have an elastic plugin option listed, in this 
>> case Poliphony. I go to event, tempo operation, then choose constant. Change 
>> the tempo value, hit apply, close the window, and sit in bemused frustration 
>> upon hearing that absolutely nothing has happened. Any help would be very 
>> welcome. Thanks.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+un

Re: Elastic audio revisited

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi, here's what I did to finally get it working like I wanted. Conductor track 
is inabled it the midi cluster. I make sure that the audio track I want to  
time change is selected first. I also make sure that elastic audio is enabled 
on that track, and that that it's set to ticks. I then go to the ruler and 
select tempo. Now I can VO-space on the tempo ruler and change the time of the 
audio which will apply itself to my selection, from the chosen start to end 
time. And I can make as many changes as I like. Hope this description makes 
sense. Thanks for all your help.

Sent from my iPhone

> On 8 Jun 2015, at 19:48, Michael lockett  wrote:
> 
> Hi,
> 
> Hi,
> you can do this by changing  the desired track for editing  from sample to 
> ticks,
> set elastic audio to polyphonic,
> 
> under track view change the view to warp,
> go to the transport cluster, under  midi change the tempo, 
> Make sure the conductor track isn’t selected…
> Hope this helps
>> On Jun 8, 2015, at 12:42 PM, Poppa Bear  wrote:
>> 
>> If you have a chance, perhaps you can outline your steps for reference? It 
>> may be the same elastic audio steps that have been posted on the list 
>> before, but at the same time, you may have taken a slightly different 
>> approach. 
>> 
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
>> Sent: Monday, June 08, 2015 8:55 AM
>> To: ptaccess@googlegroups.com
>> Subject: Elastic audio revisited
>> 
>> Hi, I would ideally have added this to the thread I created, but I dn't know 
>> how to do that when no one else has yet replied. It seems as if the issue 
>> was that I had conductor selected in the midi cluster transport view. When 
>> that was unticked it' all worked fine. I am trying to alter the tempo of 
>> some classical music so that it aligns to a click track. I don't seem to be 
>> able to make the necessary changes to th audio's length while the click 
>> track remains constant, but I have mixed down the click track and should be 
>> able to import the audio of the click and alter the classical piece's tempo 
>> while the bounced down click track is playing unaltered. Hope that makes 
>> sense. Anyway, I think it's all solved. 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: Elastic audio revisited

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Thanks Michael, that works excellently, insomuch as I am able to make one tempo 
change using this method, but I am trying to make multiple tempo changes to one 
piece of audio. And this is proving a challenge.

Sent from my iPhone

> On 8 Jun 2015, at 19:48, Michael lockett  wrote:
> 
> Hi,
> 
> Hi,
> you can do this by changing  the desired track for editing  from sample to 
> ticks,
> set elastic audio to polyphonic,
> 
> under track view change the view to warp,
> go to the transport cluster, under  midi change the tempo, 
> Make sure the conductor track isn’t selected…
> Hope this helps
>> On Jun 8, 2015, at 12:42 PM, Poppa Bear  wrote:
>> 
>> If you have a chance, perhaps you can outline your steps for reference? It 
>> may be the same elastic audio steps that have been posted on the list 
>> before, but at the same time, you may have taken a slightly different 
>> approach. 
>> 
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
>> Sent: Monday, June 08, 2015 8:55 AM
>> To: ptaccess@googlegroups.com
>> Subject: Elastic audio revisited
>> 
>> Hi, I would ideally have added this to the thread I created, but I dn't know 
>> how to do that when no one else has yet replied. It seems as if the issue 
>> was that I had conductor selected in the midi cluster transport view. When 
>> that was unticked it' all worked fine. I am trying to alter the tempo of 
>> some classical music so that it aligns to a click track. I don't seem to be 
>> able to make the necessary changes to th audio's length while the click 
>> track remains constant, but I have mixed down the click track and should be 
>> able to import the audio of the click and alter the classical piece's tempo 
>> while the bounced down click track is playing unaltered. Hope that makes 
>> sense. Anyway, I think it's all solved. 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: Having a bit of a struggle changing the tempo of audio

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

> 
> Thanks Michael, that works really well, well sort of. However, I am not able 
> to make multiple tempo changes using this method, or at least it appears that 
> way. I'm trying to make multiple tempo changes, and I'm not having any luck 
> achieving this.

-- 
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: Elastic audio revisited

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi Chuck, ticks is selected. I had it working before, but it just won't work at 
all now. I've even started a new project but it's still not working. The audio 
will not change. If you could talk me through how you would go about then I can 
see if I've missed anything. Thanks for your help. I've spent the wrole day on 
this one.

Sent from my iPhone

> On 8 Jun 2015, at 19:06, CHUCK REICHEL  
> wrote:
> 
> Hi eagle,
> ,
> Make sure that all the tracks you want to change tempo are set to "Tic" based.
> HTH
> Chuck
> 
> 
>> On Jun 8, 2015, at 1:45 PM, 'onlineeagle' via Pro Tools Accessibility wrote:
>> 
>> I would do, but I seem to have broken it again, and can't work out how to do 
>> it. I will post something once I am more certain with what the heck is going 
>> on.
>> 
>> Sent from my iPhone
>> 
>>> On 8 Jun 2015, at 18:42, Poppa Bear  wrote:
>>> 
>>> If you have a chance, perhaps you can outline your steps for reference? It 
>>> may be the same elastic audio steps that have been posted on the list 
>>> before, but at the same time, you may have taken a slightly different 
>>> approach. 
>>> 
>>> -Original Message-
>>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
>>> Sent: Monday, June 08, 2015 8:55 AM
>>> To: ptaccess@googlegroups.com
>>> Subject: Elastic audio revisited
>>> 
>>> Hi, I would ideally have added this to the thread I created, but I dn't 
>>> know how to do that when no one else has yet replied. It seems as if the 
>>> issue was that I had conductor selected in the midi cluster transport view. 
>>> When that was unticked it' all worked fine. I am trying to alter the tempo 
>>> of some classical music so that it aligns to a click track. I don't seem to 
>>> be able to make the necessary changes to th audio's length while the click 
>>> track remains constant, but I have mixed down the click track and should be 
>>> able to import the audio of the click and alter the classical piece's tempo 
>>> while the bounced down click track is playing unaltered. Hope that makes 
>>> sense. Anyway, I think it's all solved. 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: Elastic audio revisited

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

I would do, but I seem to have broken it again, and can't work out how to do 
it. I will post something once I am more certain with what the heck is going on.

Sent from my iPhone

> On 8 Jun 2015, at 18:42, Poppa Bear  wrote:
> 
> If you have a chance, perhaps you can outline your steps for reference? It 
> may be the same elastic audio steps that have been posted on the list before, 
> but at the same time, you may have taken a slightly different approach. 
> 
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
> Sent: Monday, June 08, 2015 8:55 AM
> To: ptaccess@googlegroups.com
> Subject: Elastic audio revisited
> 
> Hi, I would ideally have added this to the thread I created, but I dn't know 
> how to do that when no one else has yet replied. It seems as if the issue was 
> that I had conductor selected in the midi cluster transport view. When that 
> was unticked it' all worked fine. I am trying to alter the tempo of some 
> classical music so that it aligns to a click track. I don't seem to be able 
> to make the necessary changes to th audio's length while the click track 
> remains constant, but I have mixed down the click track and should be able to 
> import the audio of the click and alter the classical piece's tempo while the 
> bounced down click track is playing unaltered. Hope that makes sense. Anyway, 
> I think it's all solved. 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.

Elastic audio revisited

2015-06-08 Thread &#x27;onlineeagle' via Pro Tools Accessibility

Hi, I would ideally have added this to the thread I created, but I dn't know 
how to do that when no one else has yet replied. It seems as if the issue was 
that I had conductor selected in the midi cluster transport view. When that was 
unticked it' all worked fine. I am trying to alter the tempo of some classical 
music so that it aligns to a click track. I don't seem to be able to make the 
necessary changes to th audio's length while the click track remains constant, 
but I have mixed down the click track and should be able to import the audio of 
the click and alter the classical piece's tempo while the bounced down click 
track is playing unaltered. Hope that makes sense. Anyway, I think it's all 
solved. 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.

Having a bit of a struggle changing the tempo of audio

2015-06-08 Thread onlineeagle


Hi, I've managed to do this before but it was awhile ago and I can't seem to do 
it now. I want to change 
the speed of an audio track. In fact, I need to make multiple changes 
throughout the track. I select the track I want to change. I make a time 
selection. I make sure that I have an elastic plugin option listed, in this 
case Poliphony. I go to event, tempo operation, then choose constant. Change 
the tempo value, hit apply, close the window, and sit in bemused frustration 
upon hearing that absolutely nothing has happened. Any help would be very 
welcome. Thanks.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.

38 matches

Mail list logo