Re: Solving "missing AAX" error when creating a new session
Yeah! That worked, so the session no longer pops up the error. Now I can start learning this thing properly. Thanks again. Best wishes. Tim Burgess > On 6 Aug 2017, at 22:38, Tim Burgess <t...@raisedbar.net> wrote: > > OK, I now see that Db-33 is part of the First Air offering. My application > Manager tells me that both the instrument and FX packs are installed, but it > does allow me to install them again, so that’s what I’m doing. I’ll report > back on success/failure. > > Best wishes. > > Tim Burgess > > > >> On 6 Aug 2017, at 22:24, Tim Burgess <t...@raisedbar.net >> <mailto:t...@raisedbar.net>> wrote: >> >> Hi Slau, >> >> OK, many thanks - that confirmed that “disabled” means “missing” in my >> context. I checked in my plugins folder and DB-33 is not installed. If I >> accept the button to go to the Avid Market Place to look at plugs that are >> not installed, I find that I can buy the plug. Is it really the case that I >> need to do an additional purchase? I’d have thought that any >> effects/instruments being used by the stock templates would be included in >> the purchase price? I feel like I’m missing something here:) >> >> Best wishes. >> >> Tim Burgess >> >> >> >>> On 6 Aug 2017, at 18:32, Slau Halatyn <slauhala...@gmail.com >>> <mailto:slauhala...@gmail.com>> wrote: >>> >>> Hi Tim, >>> >>> If you go to the insert selector on that track and click on it, if the >>> plug-in is old and/or missing, you should see within the menu something >>> like, "N/A because plug-in missing." This would certainly be the case if a >>> session template contains an instantiation of an old plug-in that is no >>> longer part of the stock plug-ins. A good example would be the older >>> Compressor plug-in that was replaced by the Dyn 3 Compressor and EQ 2 which >>> was replaced by EQ 3 1-Band and EQ 3 7-Band equalizers. If you create a >>> session using the template, go to that track and instantiate a more current >>> plug-in and save the session as a template again and you can overwrite the >>> old template or append to the name. >>> Hope that helps, >>> Slau >>> >>>> On Aug 6, 2017, at 11:41 AM, Tim Burgess <t...@raisedbar.net >>>> <mailto:t...@raisedbar.net>> wrote: >>>> >>>> Hi, >>>> >>>> I've just set up a Mac Mini with the latest PT and FT. However, if I >>>> create a new session from any of the stock templates, I get an error >>>> indicating that some required AAX plugs are missing. I've found an article >>>> that describes steps for solving this as a sighted user (i.e. check the >>>> inserts for each track to see what they're trying to use, then validate >>>> that the plug-in is where it is supposed to be), but I want to check that >>>> my FT method is correct. If I query the inserts for each track, I hear the >>>> name of the plug-in, which is great. However, I have one track using an >>>> organ instrument where the plug-in is described as "disabled". Obviously, >>>> this looks like my bad plug-in, but I wanted to check that "disabled" >>>> means that there's a problem and not that it means something like >>>> "frozen", etc.. I'd greatly appreciate any advice on this, so thanks in >>>> advance. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Pro Tools Accessibility" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to ptaccess+unsubscr...@googlegroups.com >>>> <mailto:ptaccess+unsubscr...@googlegroups.com>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Pro Tools Accessibility" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe >>> <https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe>. >>> To unsubscribe from this group and all its topics, send an email to >>> ptaccess+unsubscr...@googlegroups.com >>> <mailto:ptaccess+unsubscr...@goo
Re: Solving "missing AAX" error when creating a new session
OK, I now see that Db-33 is part of the First Air offering. My application Manager tells me that both the instrument and FX packs are installed, but it does allow me to install them again, so that’s what I’m doing. I’ll report back on success/failure. Best wishes. Tim Burgess > On 6 Aug 2017, at 22:24, Tim Burgess <t...@raisedbar.net> wrote: > > Hi Slau, > > OK, many thanks - that confirmed that “disabled” means “missing” in my > context. I checked in my plugins folder and DB-33 is not installed. If I > accept the button to go to the Avid Market Place to look at plugs that are > not installed, I find that I can buy the plug. Is it really the case that I > need to do an additional purchase? I’d have thought that any > effects/instruments being used by the stock templates would be included in > the purchase price? I feel like I’m missing something here:) > > Best wishes. > > Tim Burgess > > > >> On 6 Aug 2017, at 18:32, Slau Halatyn <slauhala...@gmail.com >> <mailto:slauhala...@gmail.com>> wrote: >> >> Hi Tim, >> >> If you go to the insert selector on that track and click on it, if the >> plug-in is old and/or missing, you should see within the menu something >> like, "N/A because plug-in missing." This would certainly be the case if a >> session template contains an instantiation of an old plug-in that is no >> longer part of the stock plug-ins. A good example would be the older >> Compressor plug-in that was replaced by the Dyn 3 Compressor and EQ 2 which >> was replaced by EQ 3 1-Band and EQ 3 7-Band equalizers. If you create a >> session using the template, go to that track and instantiate a more current >> plug-in and save the session as a template again and you can overwrite the >> old template or append to the name. >> Hope that helps, >> Slau >> >>> On Aug 6, 2017, at 11:41 AM, Tim Burgess <t...@raisedbar.net >>> <mailto:t...@raisedbar.net>> wrote: >>> >>> Hi, >>> >>> I've just set up a Mac Mini with the latest PT and FT. However, if I create >>> a new session from any of the stock templates, I get an error indicating >>> that some required AAX plugs are missing. I've found an article that >>> describes steps for solving this as a sighted user (i.e. check the inserts >>> for each track to see what they're trying to use, then validate that the >>> plug-in is where it is supposed to be), but I want to check that my FT >>> method is correct. If I query the inserts for each track, I hear the name >>> of the plug-in, which is great. However, I have one track using an organ >>> instrument where the plug-in is described as "disabled". Obviously, this >>> looks like my bad plug-in, but I wanted to check that "disabled" means that >>> there's a problem and not that it means something like "frozen", etc.. I'd >>> greatly appreciate any advice on this, so thanks in advance. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com >>> <mailto:ptaccess+unsubscr...@googlegroups.com>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Pro Tools Accessibility" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe >> <https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe>. >> To unsubscribe from this group and all its topics, send an email to >> ptaccess+unsubscr...@googlegroups.com >> <mailto:ptaccess+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Pro Tools Accessibility" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe > <https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > ptaccess+unsubscr...@googlegroups.com > <mailto:ptaccess+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <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: Solving "missing AAX" error when creating a new session
Hi Slau, OK, many thanks - that confirmed that “disabled” means “missing” in my context. I checked in my plugins folder and DB-33 is not installed. If I accept the button to go to the Avid Market Place to look at plugs that are not installed, I find that I can buy the plug. Is it really the case that I need to do an additional purchase? I’d have thought that any effects/instruments being used by the stock templates would be included in the purchase price? I feel like I’m missing something here:) Best wishes. Tim Burgess > On 6 Aug 2017, at 18:32, Slau Halatyn <slauhala...@gmail.com> wrote: > > Hi Tim, > > If you go to the insert selector on that track and click on it, if the > plug-in is old and/or missing, you should see within the menu something like, > "N/A because plug-in missing." This would certainly be the case if a session > template contains an instantiation of an old plug-in that is no longer part > of the stock plug-ins. A good example would be the older Compressor plug-in > that was replaced by the Dyn 3 Compressor and EQ 2 which was replaced by EQ 3 > 1-Band and EQ 3 7-Band equalizers. If you create a session using the > template, go to that track and instantiate a more current plug-in and save > the session as a template again and you can overwrite the old template or > append to the name. > Hope that helps, > Slau > >> On Aug 6, 2017, at 11:41 AM, Tim Burgess <t...@raisedbar.net >> <mailto:t...@raisedbar.net>> wrote: >> >> Hi, >> >> I've just set up a Mac Mini with the latest PT and FT. However, if I create >> a new session from any of the stock templates, I get an error indicating >> that some required AAX plugs are missing. I've found an article that >> describes steps for solving this as a sighted user (i.e. check the inserts >> for each track to see what they're trying to use, then validate that the >> plug-in is where it is supposed to be), but I want to check that my FT >> method is correct. If I query the inserts for each track, I hear the name of >> the plug-in, which is great. However, I have one track using an organ >> instrument where the plug-in is described as "disabled". Obviously, this >> looks like my bad plug-in, but I wanted to check that "disabled" means that >> there's a problem and not that it means something like "frozen", etc.. I'd >> greatly appreciate any advice on this, so thanks in advance. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com >> <mailto:ptaccess+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Pro Tools Accessibility" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe > <https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > ptaccess+unsubscr...@googlegroups.com > <mailto:ptaccess+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <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: Solving "missing AAX" error when creating a new session
Hi John, Here is the link to the article: https://www.sweetwater.com/sweetcare/articles/plugins-not-show-up-pro-tools/ Best wishes. Tim Burgess > On 6 Aug 2017, at 17:02, John Covici <cov...@ccs.covici.com> wrote: > > I have had this problem as well, can you point me to that article or > whatever the equivalent procedure should be used with vo? > > Thanks. > > On Sun, 06 Aug 2017 11:41:57 -0400, > Tim Burgess wrote: >> >> [1 ] >> [1.1 ] >> [1.2 ] >> Hi, >> >> I've just set up a Mac Mini with the latest PT and FT. However, if I create >> a new session from any of the stock templates, I get an error indicating >> that some required AAX plugs are missing. I've found an article that >> describes steps for >> solving this as a sighted user (i.e. check the inserts for each track to see >> what they're trying to use, then validate that the plug-in is where it is >> supposed to be), but I want to check that my FT method is correct. If I >> query the >> inserts for each track, I hear the name of the plug-in, which is great. >> However, I have one track using an organ instrument where the plug-in is >> described as "disabled". Obviously, this looks like my bad plug-in, but I >> wanted to check >> that "disabled" means that there's a problem and not that it means something >> like "frozen", etc.. I'd greatly appreciate any advice on this, so thanks in >> advance. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ptaccess+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Pro Tools Accessibility" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ptaccess/I8AVobVyuCU/unsubscribe. > To unsubscribe from this group and all its topics, 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.
Solving "missing AAX" error when creating a new session
Hi, I've just set up a Mac Mini with the latest PT and FT. However, if I create a new session from any of the stock templates, I get an error indicating that some required AAX plugs are missing. I've found an article that describes steps for solving this as a sighted user (i.e. check the inserts for each track to see what they're trying to use, then validate that the plug-in is where it is supposed to be), but I want to check that my FT method is correct. If I query the inserts for each track, I hear the name of the plug-in, which is great. However, I have one track using an organ instrument where the plug-in is described as "disabled". Obviously, this looks like my bad plug-in, but I wanted to check that "disabled" means that there's a problem and not that it means something like "frozen", etc.. I'd greatly appreciate any advice on this, so thanks in advance. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group 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: From joy to frustration - important tip
Hi, I've finally had a chance to play with this. Slau's Command+Option+1 made the difference for me. Enabling Link Track and Edit Selection just meant that the Shift+Letter combinations would only be applied to tracks that were actively selected. Unchecking this option allowed me to mute, solo, etc. whatever track I was positioned on within the table, regardless of its selection state. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gary Readfern-Gray Sent: 14 July 2011 00:36 To: ptaccess@googlegroups.com Subject: Re: From joy to frustration - important tip OK Guys I finally figured it out. Tim I think this will sort out your problem. with the Shift + r M or s keys. To get these keys to work, you have to go to the options menu and check the item labeled Link track and edit selection Enjoy. Gazza On 12 Jul 2011, at 21:28, Slau Halatyn wrote: In the Digidesign folder, go to the Documentation folder, then into the Pro Tools subfolder and you'll find a pdf document with all of the keyboard shortcuts. Also, right in the Help menu you'll find the same document. To copy an entire section across all tracks, enable the All Group. Then scrub anywhere in the song. Go to the beginning of your desired section and then select the range, copy, move to the place you wish to paste and press Command-v. Pro Tools will paste all the regions to their respective tracks. That's the short version of the story. Depending upon whether you're in bars/beats or minutes:seconds, your needs might be a little different. I'm not going to get into the minutiae without knowing precisely what you're doing but that's the idea. Remember to turn off the All group when you're done or else you might run into trouble. HTH, Slau On Jul 12, 2011, at 4:11 PM, Gary Readfern-Gray wrote: Hi, Thanks so much all for the help. I didn't quite get to the bottom of why it wasn't working before now but it's working great now regardless it seems of selecting or otherwise the keyboard focus buttons. maybe because I've shut and reopend the session since I last tried. So, back to joy again. I'm already more productive after 24 hours than I was in Logic after about 9 months and being able to find and set my EQ paramaters, at long last!! So, at risk of becoming boring with my enthusiasm, Where can I get a list of shortcut keys for PT 8? I particularly want to be ableto select and copy audio around. One question, is it possible accessibly to copy, let's say a verse of a song across all the tracks and paste it in the next verse along and have all the music placed in the correct tracks? I never figgured out how to do that in Sonar and doing that track by track gets very old, very quickly. P.S Kevin, I also have Superior drummer, so if there's anything I can help with on a preset front, just mail me, though of course, I'm still new to PT. Gazza, On 12 Jul 2011, at 19:38, Tim Burgess wrote: Hey Slau, I think you've stopped me going crazy - I was also having problems with the Shift+Letter combinations in the Mix window. I'll give this a try Shift+and see if I can do the mute, solo and arm functions now. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Slau Halatyn Sent: 12 July 2011 13:06 To: ptaccess@googlegroups.com Subject: Re: From joy to frustration! Hi Gazza, Use Command-Option-1 to use Commands focus mode. There are two other modes which are, if I remember correctly, Audio Regions and Groups focus mode and they are Command-Option-2 and Command-Option-3 respectively. There's also a keyboard focus button right in the window but, if the tracks list isn't displayed, you can't access that button. what Kevin mentioned about the Mix window display buttons should help you get it to be visible. I think there's also a menu item to display the tracks list. HTH, Slau On Jul 12, 2011, at 3:49 AM, Gary Readfern-Gray wrote: Hi Listers, Well, I bought a mac about a year ago because I wanted to start using Pro Tools, but when the accessible version finally arrived, I found getting around a session so clunky and horrible to use, I bought Logic and have been using that, I have a little sight so I was stumbling along with it. Then, after months and months of using Logic, I come across Keven's tutorial and discover that, once you've got more than one track in the session, the track list is usable by VO and that's what I wanted to do initally, quickly find a track, mute, solo
RE: From joy to frustration - important tip
OK, I'll do some more fiddling. I'm using V9, so that might be the difference. I have Omnisphere kicking around here on my PC rig, but haven't had time to install and try it on a Mac yet. Will report back as and when (grin). Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gary Readfern-Gray Sent: 15 July 2011 15:20 To: ptaccess@googlegroups.com Subject: Re: From joy to frustration - important tip Hi tim, well that's weird. Well, what happend for me was that I found that I was in the track list and regardless of the track I was on, even if I pressed vo space to select it, When I pressed shift m, for example, a seeming random track got muted and it was always that track, regardless of what I did with the keyboard focus buttons. I have some vision, so had been playing around with the selector tool and clicking on track ets. When I looked through the keyboard shortcuts manual, the shift +s m and r keys apply to the selected track. I'm not sure what Pro Tools classifies as being the selected track but here's what I noticed. When I uncheck link track and edit selection, If you click on a track, solo, mute and arming works for that track, however, if you select a different track by using vo in the track list, those keys will still apply to the previously selected track. If you select that menu option, When you select a different track in the track list, the insertion point moves to the newly selected track and the keys work correctly for that track. That's the long version of the polava I went through to get it working for me. I'm using the very first version that became accessible last June, so there may be a more recent update that works differently, but I'm glad we've both got it working. I was playing around with xpand 2 yesterday, that's very accessible as well, though not as good as Omnisphere which I really want to get, does anyone know if any of that is accessible with VO? Gazza On 7/15/11, Tim Burgess tim...@raisedbar.net wrote: Hi, I've finally had a chance to play with this. Slau's Command+Option+1 made the difference for me. Enabling Link Track and Edit Selection just meant that the Shift+Letter combinations would only be applied to tracks that were actively selected. Unchecking this option allowed me to mute, solo, etc. whatever track I was positioned on within the table, regardless of its selection state. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gary Readfern-Gray Sent: 14 July 2011 00:36 To: ptaccess@googlegroups.com Subject: Re: From joy to frustration - important tip OK Guys I finally figured it out. Tim I think this will sort out your problem. with the Shift + r M or s keys. To get these keys to work, you have to go to the options menu and check the item labeled Link track and edit selection Enjoy. Gazza On 12 Jul 2011, at 21:28, Slau Halatyn wrote: In the Digidesign folder, go to the Documentation folder, then into the Pro Tools subfolder and you'll find a pdf document with all of the keyboard shortcuts. Also, right in the Help menu you'll find the same document. To copy an entire section across all tracks, enable the All Group. Then scrub anywhere in the song. Go to the beginning of your desired section and then select the range, copy, move to the place you wish to paste and press Command-v. Pro Tools will paste all the regions to their respective tracks. That's the short version of the story. Depending upon whether you're in bars/beats or minutes:seconds, your needs might be a little different. I'm not going to get into the minutiae without knowing precisely what you're doing but that's the idea. Remember to turn off the All group when you're done or else you might run into trouble. HTH, Slau On Jul 12, 2011, at 4:11 PM, Gary Readfern-Gray wrote: Hi, Thanks so much all for the help. I didn't quite get to the bottom of why it wasn't working before now but it's working great now regardless it seems of selecting or otherwise the keyboard focus buttons. maybe because I've shut and reopend the session since I last tried. So, back to joy again. I'm already more productive after 24 hours than I was in Logic after about 9 months and being able to find and set my EQ paramaters, at long last!! So, at risk of becoming boring with my enthusiasm, Where can I get a list of shortcut keys for PT 8? I particularly want to be ableto select and copy audio around. One question, is it possible accessibly
RE: audio interface
Hi, I've got an on-going dialog with the Focusrite support guys over here, but their developers say that they've no time to make the necessary changes. Don't worry, I intend to keep pushing. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 17 June 2011 13:05 To: Pro Tools Accessibility Subject: Re: audio interface Does anyone know if the control pannel of the RME digital cards is accessible? Tim have you contacted Focusrite about the accessibility of their control pannels on mac? Focusrite has awesome interfaces and it shouldn't be to difficult for them to make it accessible.
RE: audio interface
Well, don't go for a Focusrite Saffire - we've got great accessibility on the Windows panel, but there's nothing except the menu bar that's workable on the Mac. I cheat and create my configurations under windows, save them as preset files then use Command+O to load them on the Mac, but this is a pain, even if you're lucky enough to have a couple of machines. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: 12 June 2011 18:10 To: ptaccess@googlegroups.com Subject: audio interface Hey Everyone, Was just curious what audio interface are you guys using on the mac that has an accessible control pannel? just curious since my MBox Pro's control pannel is completely inaccessible and there are a few changes i would have to make in there.So i am considering replaceing it if there is something thats also accessible but meets my needs I/O wise. Thanks.
RE: Control Surface
Hi Gord, I'm just about to get the 2.0GHz, 8GB RAM and 256GB SSD version (can't quite push it for the extra clock speed and SSD space). This machine will be used to get a Mac version of the Mackie Display Reader going. I'm interested that you've had some issues with using a PC keyboard - the only one I've found on my Mac Mini is that using Shift+M, Shift+S, etc. in the Track table doesn't mute, solo, etc.. Is that what you've experienced, please? Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gordon Kent Sent: 11 June 2011 06:11 To: ptaccess@googlegroups.com Subject: Re: Control Surface Well, I'm certainly going through quite a learning curve with both the mac os and pt. But I am really impressed with the interface of both, and the ss drive is really cool. I went whole hog with the macbook pro, the 500 gb drive, 8gb of ram, and the 2.3ghz quad i7 processor. Now if they would only get the thunderbolt supported with some hardware that would be it. I'm surprised it only has two usb ports, but I guess they expect you to use a hub. I do need to get an actual apple keyboard, the pc keyboards work but there are some incompatibilities. Anyway, I do have some issues but it's too late to get to that now. Gord -Original Message- From: Slau Halatyn Sent: Friday, June 10, 2011 7:59 PM To: ptaccess@googlegroups.com Subject: Re: Control Surface Hey Gord, Welcome to the list. Very cool. Slau On Jun 10, 2011, at 7:38 PM, Gord wrote: Hi: Well, I'm just on the list for the first time. Have a blown out macbook pro with pt9 now. I do have a project mix but also an alesis master control which I think has some form of hui compatibility. It does have an excellent jog wheel and the audio i/o is decent. I'm just getting strated with this whole setup, but like it so far. BTW, autotune 7 really shows up well with VO. Gord Tim Burgess wrote: Hi, I'm intending to add HUI and Logic Control protocol support, so I'm setting up a test rig with a Behringer BCF2000 right now with Baby HUI and PT9. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 03 June 2011 12:29 To: Pro Tools Accessibility Subject: Re: Control Surface Tim this sounds great and would be even better if you can create a mac version to work with pro tools. Monkey Pusher wrote: So this will allow any control surface that uses the mackie protocol to talk? or only the mackie ones? Does that mean it will speak the changs as you make them on the control surface? Like it will say the pan value as you make adjustments? On 5/31/11, Tim Burgess tim...@raisedbar.net wrote: Hi, Just to add that I'm currently developing an application to make Mackie-compliant surfaces talk. We currently have a proof of concept version working with Sonar on the PC, but we'll have a cross-platform build going in the next few months. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 31 May 2011 16:27 To: Pro Tools Accessibility Subject: Re: Control Surface Hi this question depends on your budget. If you can aford it go for the digi 003, just don't fall over if you here what the price is remember it's much more than a control serfice. The next level to look at would be the euphonix control, mix and transport however as far as I'd seen on forums the euphonix stuff has increased in price and decreased in build quality since avid baught the company. I would personally go for a mackie control universal pro, I have worked on these a lot. It's solid and has a great feel. think the main unit retails for round $1000. J. R. Westmoreland wrote: I'm using a command-8. I like it so far. The only thing it doesn't have that would be nice is a scrub wheel. -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: Monday, May 30, 2011 10:06 AM To: ptaccess Subject: Control Surface Hello Again, So as i said earlier new to this world. So after checking out some audio workshops/tutorials by Slau and Kevin Reeves, it became appearant that a control surface makes certain things alot easier. SO what are you guys out there using? Any reccomendations
RE: Control Surface
Hmmm, that's not what I'm experiencing. For instance, I can select a track that plays then press Shift+M and it won't mute. Those keystrokes don't seem to do anything at all. I'm going to steal the wired keyboard from my wife's iMac and see what happens. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gordon Kent Sent: 12 June 2011 17:20 To: ptaccess@googlegroups.com Subject: Re: Control Surface Well, that is certainly an issue. It seems that when I try to use one of those keystrokes it mutes or solos everything and when you unsolo or unmute certain tracks seem to not be in the state you want. I thought it had to do with having assigned tracks to groups and I tried deleting the groups but it didn't help. Gord -Original Message- From: Tim Burgess Sent: Sunday, June 12, 2011 3:28 AM To: ptaccess@googlegroups.com Subject: RE: Control Surface Hi Gord, I'm just about to get the 2.0GHz, 8GB RAM and 256GB SSD version (can't quite push it for the extra clock speed and SSD space). This machine will be used to get a Mac version of the Mackie Display Reader going. I'm interested that you've had some issues with using a PC keyboard - the only one I've found on my Mac Mini is that using Shift+M, Shift+S, etc. in the Track table doesn't mute, solo, etc.. Is that what you've experienced, please? Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Gordon Kent Sent: 11 June 2011 06:11 To: ptaccess@googlegroups.com Subject: Re: Control Surface Well, I'm certainly going through quite a learning curve with both the mac os and pt. But I am really impressed with the interface of both, and the ss drive is really cool. I went whole hog with the macbook pro, the 500 gb drive, 8gb of ram, and the 2.3ghz quad i7 processor. Now if they would only get the thunderbolt supported with some hardware that would be it. I'm surprised it only has two usb ports, but I guess they expect you to use a hub. I do need to get an actual apple keyboard, the pc keyboards work but there are some incompatibilities. Anyway, I do have some issues but it's too late to get to that now. Gord -Original Message- From: Slau Halatyn Sent: Friday, June 10, 2011 7:59 PM To: ptaccess@googlegroups.com Subject: Re: Control Surface Hey Gord, Welcome to the list. Very cool. Slau On Jun 10, 2011, at 7:38 PM, Gord wrote: Hi: Well, I'm just on the list for the first time. Have a blown out macbook pro with pt9 now. I do have a project mix but also an alesis master control which I think has some form of hui compatibility. It does have an excellent jog wheel and the audio i/o is decent. I'm just getting strated with this whole setup, but like it so far. BTW, autotune 7 really shows up well with VO. Gord Tim Burgess wrote: Hi, I'm intending to add HUI and Logic Control protocol support, so I'm setting up a test rig with a Behringer BCF2000 right now with Baby HUI and PT9. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 03 June 2011 12:29 To: Pro Tools Accessibility Subject: Re: Control Surface Tim this sounds great and would be even better if you can create a mac version to work with pro tools. Monkey Pusher wrote: So this will allow any control surface that uses the mackie protocol to talk? or only the mackie ones? Does that mean it will speak the changs as you make them on the control surface? Like it will say the pan value as you make adjustments? On 5/31/11, Tim Burgess tim...@raisedbar.net wrote: Hi, Just to add that I'm currently developing an application to make Mackie-compliant surfaces talk. We currently have a proof of concept version working with Sonar on the PC, but we'll have a cross-platform build going in the next few months. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 31 May 2011 16:27 To: Pro Tools Accessibility Subject: Re: Control Surface Hi this question depends on your budget. If you can aford it go for the digi 003, just
RE: Control Surface
OK, If you've still got a Windows/Sonar rig, I'd really appreciate you trying the Reader with the FW in Mackie mode, as it's something I haven't been able to test. If it has the same issue as the Project Mix, then it'll push the multiple message issue higher up my priority list for the next version. You can get the free Reader and required info from: http://www.raisedbar.net/MDR/mdr.htm Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Goldfinga Productions Sent: 07 June 2011 16:36 To: ptaccess@googlegroups.com Subject: Re: Control Surface I have an fw as well, and a project mix... I didn't know about the project mix and the multiple messages when pressing the mode buttons. Interesting.. On Jun 7, 2011, at 9:29 AM, Tim Burgess wrote: That's the idea. The application is protocol-based, so non-Mackie surfaces are potentially OK. Having said this, I'm aware that some surfaces out there do strange things with their button presses. For instance, the M-Audio Project Mix transmits more than one message when you press the mode buttons and this can cause problems with the Mackie Reader application. It may be possible to work around this kind of thing, but getting things working with equipment that behaves more correctly will be a definite priority. Testing so far has been with a Mackie Control Universal and a Behringer BCF2000 and all was well, given the limitations that the BCF doesn't have a jog wheel, scrub button or MBT/SMPTE time display button. I've got a Mackie C4 here, so I'll be adding support for that and I've got friends with Tascam FW1884 units that say they'll do some testing for me. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: 31 May 2011 23:51 To: ptaccess@googlegroups.com Subject: Re: Control Surface So this will allow any control surface that uses the mackie protocol to talk? or only the mackie ones? Does that mean it will speak the changs as you make them on the control surface? Like it will say the pan value as you make adjustments? On 5/31/11, Tim Burgess tim...@raisedbar.net wrote: Hi, Just to add that I'm currently developing an application to make Mackie-compliant surfaces talk. We currently have a proof of concept version working with Sonar on the PC, but we'll have a cross-platform build going in the next few months. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 31 May 2011 16:27 To: Pro Tools Accessibility Subject: Re: Control Surface Hi this question depends on your budget. If you can aford it go for the digi 003, just don't fall over if you here what the price is remember it's much more than a control serfice. The next level to look at would be the euphonix control, mix and transport however as far as I'd seen on forums the euphonix stuff has increased in price and decreased in build quality since avid baught the company. I would personally go for a mackie control universal pro, I have worked on these a lot. It's solid and has a great feel. think the main unit retails for round $1000. J. R. Westmoreland wrote: I'm using a command-8. I like it so far. The only thing it doesn't have that would be nice is a scrub wheel. -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: Monday, May 30, 2011 10:06 AM To: ptaccess Subject: Control Surface Hello Again, So as i said earlier new to this world. So after checking out some audio workshops/tutorials by Slau and Kevin Reeves, it became appearant that a control surface makes certain things alot easier. SO what are you guys out there using? Any reccomendations? Currently using PT 9 with an MBox Pro if that matters. Thanks. GF Check me out on twitter http://www.twitter.com/goldfingas
RE: Control Surface
Hi, I'm intending to add HUI and Logic Control protocol support, so I'm setting up a test rig with a Behringer BCF2000 right now with Baby HUI and PT9. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 03 June 2011 12:29 To: Pro Tools Accessibility Subject: Re: Control Surface Tim this sounds great and would be even better if you can create a mac version to work with pro tools. Monkey Pusher wrote: So this will allow any control surface that uses the mackie protocol to talk? or only the mackie ones? Does that mean it will speak the changs as you make them on the control surface? Like it will say the pan value as you make adjustments? On 5/31/11, Tim Burgess tim...@raisedbar.net wrote: Hi, Just to add that I'm currently developing an application to make Mackie-compliant surfaces talk. We currently have a proof of concept version working with Sonar on the PC, but we'll have a cross-platform build going in the next few months. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 31 May 2011 16:27 To: Pro Tools Accessibility Subject: Re: Control Surface Hi this question depends on your budget. If you can aford it go for the digi 003, just don't fall over if you here what the price is remember it's much more than a control serfice. The next level to look at would be the euphonix control, mix and transport however as far as I'd seen on forums the euphonix stuff has increased in price and decreased in build quality since avid baught the company. I would personally go for a mackie control universal pro, I have worked on these a lot. It's solid and has a great feel. think the main unit retails for round $1000. J. R. Westmoreland wrote: I'm using a command-8. I like it so far. The only thing it doesn't have that would be nice is a scrub wheel. -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: Monday, May 30, 2011 10:06 AM To: ptaccess Subject: Control Surface Hello Again, So as i said earlier new to this world. So after checking out some audio workshops/tutorials by Slau and Kevin Reeves, it became appearant that a control surface makes certain things alot easier. SO what are you guys out there using? Any reccomendations? Currently using PT 9 with an MBox Pro if that matters. Thanks.
RE: Control Surface
That's the idea. The application is protocol-based, so non-Mackie surfaces are potentially OK. Having said this, I'm aware that some surfaces out there do strange things with their button presses. For instance, the M-Audio Project Mix transmits more than one message when you press the mode buttons and this can cause problems with the Mackie Reader application. It may be possible to work around this kind of thing, but getting things working with equipment that behaves more correctly will be a definite priority. Testing so far has been with a Mackie Control Universal and a Behringer BCF2000 and all was well, given the limitations that the BCF doesn't have a jog wheel, scrub button or MBT/SMPTE time display button. I've got a Mackie C4 here, so I'll be adding support for that and I've got friends with Tascam FW1884 units that say they'll do some testing for me. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: 31 May 2011 23:51 To: ptaccess@googlegroups.com Subject: Re: Control Surface So this will allow any control surface that uses the mackie protocol to talk? or only the mackie ones? Does that mean it will speak the changs as you make them on the control surface? Like it will say the pan value as you make adjustments? On 5/31/11, Tim Burgess tim...@raisedbar.net wrote: Hi, Just to add that I'm currently developing an application to make Mackie-compliant surfaces talk. We currently have a proof of concept version working with Sonar on the PC, but we'll have a cross-platform build going in the next few months. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 31 May 2011 16:27 To: Pro Tools Accessibility Subject: Re: Control Surface Hi this question depends on your budget. If you can aford it go for the digi 003, just don't fall over if you here what the price is remember it's much more than a control serfice. The next level to look at would be the euphonix control, mix and transport however as far as I'd seen on forums the euphonix stuff has increased in price and decreased in build quality since avid baught the company. I would personally go for a mackie control universal pro, I have worked on these a lot. It's solid and has a great feel. think the main unit retails for round $1000. J. R. Westmoreland wrote: I'm using a command-8. I like it so far. The only thing it doesn't have that would be nice is a scrub wheel. -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Monkey Pusher Sent: Monday, May 30, 2011 10:06 AM To: ptaccess Subject: Control Surface Hello Again, So as i said earlier new to this world. So after checking out some audio workshops/tutorials by Slau and Kevin Reeves, it became appearant that a control surface makes certain things alot easier. SO what are you guys out there using? Any reccomendations? Currently using PT 9 with an MBox Pro if that matters. Thanks.
RE: Cubase accessibility
I'll definitely test this for you. Do you have a download URL for the trial V6, please? Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -Original Message- From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of Nickus de Vos Sent: 19 May 2011 12:42 To: Pro Tools Accessibility Subject: Cubase accessibility Hi all this is off topic but some might find it useful. I said a while back that I'm going to try cubase and neuendo on mac to check if one of the two is accessible. I have had the chance to test cubase 5 on a system but it had OS 5.8.3 obviously with a older version of voiceover so cubase didn't work. A couple of days ago I contacted steinberg who makes cubase and neuendo asking them if they tested one of their products for accessibility. I got a reply today, it's not as useful as I hoped but the guy told me that the new Cubase 6 is now a coco application where cubase 5 was only modified to work on mac, its core wasn't coco. Because of this he said, cubase6 might be accessible and that I should get the trail version and test it however my employers where I have access to macs would not allow me to install it on their machines to test. So if there's anybody with some time and willingness to test cubase 6 with voiceover, please do and let us know what results you get.
