midi controller issues in protools 11
hi i wrote yesterday i have sound i imported and playback is fine but my novation impulse 61 key midi controller there’s no sound when i play the keys i followed the novation instructions for auto map i get the following error the original device hui could not be found i’m not a advanced protools user i’m in the middle 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/groups/opt_out.
Digi003 questions
Hello good people. I’ve just bought me a Digi003 control surface since my Projectmix appears not to be supported with PT11.1 under Mavericks. This leads me to some questions: How is the accessibility of the 003 console? Does anyone have some documentation of the button layout from a blindness perspective and are there things one should look out for, like wrapping menus and the like? Thanks for any help. /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/groups/opt_out.
Re: midi controller issues in protools 11
Hi Chad, Did you go through the Intro to Pro Tools pdf to follow instructions on how to set up MIDI tracks for recording and playback? Also, did you have a look at the Audio MIDI Utility to see if your device is recognized and enabled? Just two things off the top of my head that I would try. Slau On Jan 4, 2014, at 5:35 AM, chad baker baker3...@gmail.com wrote: hi i wrote yesterday i have sound i imported and playback is fine but my novation impulse 61 key midi controller there’s no sound when i play the keys i followed the novation instructions for auto map i get the following error the original device hui could not be found i’m not a advanced protools user i’m in the middle 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Digi003 questions
Hi Krister, I'm attaching an rtf document of the layout but, just in case, I'm pasting it below. I bought the 003 for simple, remote projects a few years ago and I only used it in a basic way. Frankly, I never used it with plug-ins too much so I can't comment on how easy it is to operate in that sense but, if it's anything like other Avid surfaces with encoder knobs that are automatically mapped, it should be pretty straight-forward. best, Slau Digi 003 Layout Top Console Section The Digi 003 includes an LCD display across the top of its mixer section. To the right of the LCD display is a rectangular button labelled Display Modes. To the right, there are LEDs which are beneath the face of the surface so they're not at all tactile. These LEDs indicate: Host, WordClock, S/PDIF, ADAT, MIDI In, MIDI Out 1 and MIDI Out 2. Main Console right side master section Below the Display Modes button on the right side of the surface are 4 gain knobs which are: Preamps 1 through 4. Below each gain knob are a pair of buttons (for a total of 8 buttons in a single row). The left side button is the Mic/D.I. button and the right side buttons the HPF or High Pass Filter button. When the Mic/D.i. button is extinguished (it's default state), it's in mic mode and when lit, it's in D.I. mode. below the row of Mic/D.I. and HPF buttons is a row of 6 buttons. One button is set apart to the left and is labelled: Meter. This button toggles the function of the LEDs above each channel strip. The remaining 5 buttons in this row are: Aux In to 7-8, 3-4 to Headphone 2, Aux In, Alt Control Room and Mono. Below these buttons are three knobs (rightmost in a row of knobs) and are labelled: Phones 1, Phones 2 and Monitor. A button to the right of the Monitor knob is labelled Mute. Upon powering up the 003, the Mute button is automatically engaged. Below the Headphone and Control Room knobs are 4 rows of buttons. The first three rows contain 6 evenly spaced buttons. The buttons in the first row are: Record Arm, MIDI Map A, MIDI Map B, Save, Undo and Enter. The buttons in the second row are: Memory Locate, MIDI Recall, MIDI Edit, Utility, Fader Mute and Focus. The buttons in the third row are: Plug-in, Mix, Edit, Loop Play, Loop Record and Quick Punch. The fourth row contains 5 buttons. There's a gap between the first button and the remaining four buttons. The first button is labelled: Master Faders. The remaining four buttons are: Flip, Bank, Nudge and Zoom. Below these buttons are the Scrub/Shuttle wheel and the Up/Down/Previous/Next buttons oriented in a north, south, east, west fashion. The Scrub and Shuttle wheels are concentric with the Scrub wheel on the inner circle and the Shuttle on the outer circle. Below these controls are the Transport buttons which are (from left to right): Return To Zero, Rewind, Fast Forward, stop, Play and Record. Main Console Channel Section The main Channel strip section of the control surface occupies most of the control surface. beginning at the bottom, there are 8 touch-sensitive moving faders. Above each fader are 3 buttons. From bottom to top, they are:: Mute, Solo and Select. Above these buttons are the Encoder knobs. Above each encoder knob, there is a small column of 5 LEDs. These function both as level meters and automation mode indicators. In Automation mode, from top to bottom, the LEDs are labelled: Write, Touch, Latch and Read. The bottom LED is unlabeled. above the LEDs, in line with the 8 columns of channels, are 8 buttons labelled: EQ, Dynamics, Insert, Pan/send, Page Left, Page Right, Master Bypass and Escape. Along the left side of the surface are two columns of buttons arranged in several groups. The top two buttons in the first group are even with the row of 8 buttons along the top of the channel strips. The top group of buttons include 5 buttons in the left column and 3 buttons in the right column. Note that there are gaps between the 3 buttons in the right column. The left column buttons are labelled: A/F, B/G, C/H, D/I and E/J. The 3 buttons in the right column are labelled: Pan, Send and Insert. The next group of buttons is in line with the channel strips' Select buttons and consists of one button in each column. The left button is labelled: Default and the right button is labelled: Input. The group of buttons below this are the Automation Mode buttons. the left column buttons (from top to bottom) are labelled: Write, Touch and Latch. The right column buttons are labelled: Read, Off and Suspend. The bottom group of 4 buttons are the modifier buttons. The left column upper button is: Shift (Add). The lower button is: Control/Win. The right column upper button is: Opt/Alt (All). the lower button is: Cmd/Ctrl. Rear Panel The Digi 003's rear panel has an upper section and a lower section which is set in more deeply beneath the top panel of the control surface. On the left side of the upper section of the rear panel, from left to right are the Microphone
Re: midi controller issues in protools 11
hi yes i got a error saying original device hui cannot be found i ran it through pt10 and all is well and logic pro x controller works both in pt10 and logic pro x just not pt11 On Jan 4, 2014, at 12:22 PM, Slau Halatyn slauhala...@gmail.com wrote: Hi Chad, Did you go through the Intro to Pro Tools pdf to follow instructions on how to set up MIDI tracks for recording and playback? Also, did you have a look at the Audio MIDI Utility to see if your device is recognized and enabled? Just two things off the top of my head that I would try. Slau On Jan 4, 2014, at 5:35 AM, chad baker baker3...@gmail.com wrote: hi i wrote yesterday i have sound i imported and playback is fine but my novation impulse 61 key midi controller there’s no sound when i play the keys i followed the novation instructions for auto map i get the following error the original device hui could not be found i’m not a advanced protools user i’m in the middle 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: midi controller issues in protools 11
Hmm… I'm not sure what the problem might be. I had a similar experience, albeit with audio, going from an older MacBook Pro to a new MacBook Pro. Everything played back on the old system and, even though I had migrated my settings to the new computer, I wasn't getting playback. I thought the migration would be seamless but therein lay the problem: not all settings for audio are translatable between computers. The solution had to do with creating a new aggregate device. With MIDI, however, I suspect it might be similar but perhaps a bit different. I haven't worked with MIDI in PT 11 and even barely in version 10 so I'm not the person to troubleshoot it. However, if you purchased version 11, you're certainly entitled to technical support for at least 90 days. Hopefully, you've learned VoiceOver enough so that, when tech support asks you to navigate Pro Tools or the operating system, you'll be able to get around. Maybe somebody else on the list has some ideas. slau On Jan 4, 2014, at 12:27 PM, chad baker baker3...@gmail.com wrote: hi yes i got a error saying original device hui cannot be found i ran it through pt10 and all is well and logic pro x controller works both in pt10 and logic pro x just not pt11 On Jan 4, 2014, at 12:22 PM, Slau Halatyn slauhala...@gmail.com wrote: Hi Chad, Did you go through the Intro to Pro Tools pdf to follow instructions on how to set up MIDI tracks for recording and playback? Also, did you have a look at the Audio MIDI Utility to see if your device is recognized and enabled? Just two things off the top of my head that I would try. Slau On Jan 4, 2014, at 5:35 AM, chad baker baker3...@gmail.com wrote: hi i wrote yesterday i have sound i imported and playback is fine but my novation impulse 61 key midi controller there’s no sound when i play the keys i followed the novation instructions for auto map i get the following error the original device hui could not be found i’m not a advanced protools user i’m in the middle 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
a general observation about Pro Tools accessibility users
With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do the same. While it is certainly a simple matter to create a Pro Tools session, create a track and record-enable it, that is so much so only the tip of the iceberg. Need I point out the fact that Pro Tools is an enormously complex program and has features that many of us will never use? It should be no surprise then that everyone will encounter a steep learning curve at some point and that curve
Re: Digi003 questions
Hi and thanks for that info. this will surely come in handy once i’ve gotten the 003. /Krister 4 jan 2014 kl. 18:28 skrev Slau Halatyn slauhala...@gmail.com: Digi 003 Layout.rtf -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
On 1/4/2014 2:50 PM, Slau Halatyn wrote: With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do the same. While it is certainly a simple matter to create a Pro Tools session, create a track and record-enable it, that is so much so only the tip of the iceberg. Need I point out the fact that Pro Tools is an enormously complex program and has features that many of us will never use? It should be no surprise then that everyone will encounter a steep learning
Re: a general observation about Pro Tools accessibility users
Hi. While we are on the topic, in case anybody wasn't aware, You can download all of the pt11 documentation from the avid web site in a zip file, or, document by document if you wish. So, even if you don't own pt yet, you can start reading. Cameron. On 1/4/14, Jim Noseworthy jim.nosewor...@compuconference.com wrote: On 1/4/2014 2:50 PM, Slau Halatyn wrote: With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do the same. While it is certainly
Re: What are the new updates to pro tools 11.1 as it relates to working with Mavericks?
Hi David, I've interspersed my comments below. On Jan 4, 2014, at 12:14 AM, David Ingram dingram...@earthlink.net wrote: Hi list members, what are the new accessibility features of pro tools and do these new features and functions work well with mavericks? Apart from several fixes to issues with counter displays, the MIDI Event List is now accessible and AAX plug-ins are accessible. Mavericks is supported. There are many other things that have been improved but, if one hasn't really used Pro Tools in the past, it's somewhat irrelevant to list the changes since that person would be starting from scratch. What are the things that I might want to look forward to? Also what about plug-in support as it relates to eq, panning and things like reverb do we have access to those plug-ins where we can hear in real-time what the values of these different controls are or do we still need sighted assistance in order to go through to see where we are in a project. Well, for one, a stable operating system is something to look forward to. Also, if you know how to use VoiceOver and you know how to use Pro tools, there are no cryptic keyboard shortcuts to remember. Oh, yes, speaking of shortcuts, that's another thing you can look forward to: memorizing a ton of them that are used in Pro tools and it makes things very easy if you know them. Regarding plug-ins, when you say real time, I'm not sure what you mean by that. Plug-in parameters are readable and editable. If you want to monitor changes of a particular parameter, VoiceOver allows for that so it's not a function of Pro Tools. I'm not sure what you mean by sighted assistance to know where one is within a project. I've never heard of that. One can simply read the counter display to determine where they are within a project or just type in a location and you're there. The other thing is that when you start a project and you want to set whether you want eighth notes or quarter notes, can you do that first along with the key signature and tempo? It's possible to set tempo, meter, key signature, etc. at any point. There are a few issues with that right now. For starters, one can't necessarily edit those values once they've been set. However, it is possible to simply enter another tempo or meter event and the last event entered will be the current value. For example, if you create a tempo event of 121 beats per minute right at the start and then need to change it to 122 bpm, you currently can't edit the original tempo event but you can create a second tempo event of 122 bpm at the same location and, since it's technically the last tempo change in the list of events at the start of the session, the tempo will be 122. Same applies to all other ruler events. Avid is aware of the issue of ruler events and is already thinking of ways to solve the problem. We'll surely see a solution in the future. Hope that helps, 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/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
Well, I hope it does inspire some folks to undertake the herculean task that is the study of manuals. It's sort of like exercise: not terribly fun, necessarily, but you eventually really appreciate the effort. Slau On Jan 4, 2014, at 2:39 PM, Jim Noseworthy jim.nosewor...@compuconference.com wrote: Slau: Thanks for taking the time to post those thoughts: it's appreciated. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
Thank you for this sound advice Slau. I will try and put it into practice more often. I hope that you don't mind, but I am forwarding this message to the mag for those considering the prospect of venturing into PT as a general reminder that it is not a simple undertaking to transfer your whole workflow from say, Sonar to PT and expect everything to go smoothly without putting in the behind the seens work of getting your knowledge bass built up. - Original Message - From: Slau Halatyn slauhala...@gmail.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 9:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those
Re: a general observation about Pro Tools accessibility users
Thanks for pointing that out, Cameron. Good point for those who haven't yet purchased Pro Tools but know they want to go that route. Slau On Jan 4, 2014, at 2:44 PM, Cameron Strife came...@cameronstrife.com wrote: Hi. While we are on the topic, in case anybody wasn't aware, You can download all of the pt11 documentation from the avid web site in a zip file, or, document by document if you wish. So, even if you don't own pt yet, you can start reading. Cameron. On 1/4/14, Jim Noseworthy jim.nosewor...@compuconference.com wrote: On 1/4/2014 2:50 PM, Slau Halatyn wrote: With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the
Re: Digi003 questions
Hello Chris, I use the 002 and they both have the same lay out from what I remember. I may be able to do some face time stuff with you if you get into a pinch here and there. I used my pen friend labeler to mark the different rows of buttons, but I don't remember alot of the names of the buttons, just the location and functions. Either way, I figured I would put the invatation out there and as Slau has pointed out in his post today, RTF, LOL. - Original Message - From: Krister Ekstrom kris...@kristersplace.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 10:13 AM Subject: Re: Digi003 questions Hi and thanks for that info. this will surely come in handy once i’ve gotten the 003. /Krister 4 jan 2014 kl. 18:28 skrev Slau Halatyn slauhala...@gmail.com: Digi 003 Layout.rtf -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
By all means. Thanks, Slau On Jan 4, 2014, at 3:00 PM, Poppa Bear heavens4r...@gmail.com wrote: Thank you for this sound advice Slau. I will try and put it into practice more often. I hope that you don't mind, but I am forwarding this message to the mag for those considering the prospect of venturing into PT as a general reminder that it is not a simple undertaking to transfer your whole workflow from say, Sonar to PT and expect everything to go smoothly without putting in the behind the seens work of getting your knowledge bass built up. - Original Message - From: Slau Halatyn slauhala...@gmail.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 9:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around
Re: Digi003 questions
Ah, but the 003 has a different layout after all. I had purchased Gordon's 002 many years ago and upgraded to the 003 at some point and it was quite different. Just a heads up. Slau On Jan 4, 2014, at 3:08 PM, Poppa Bear heavens4r...@gmail.com wrote: Hello Chris, I use the 002 and they both have the same lay out from what I remember. I may be able to do some face time stuff with you if you get into a pinch here and there. I used my pen friend labeler to mark the different rows of buttons, but I don't remember alot of the names of the buttons, just the location and functions. Either way, I figured I would put the invatation out there and as Slau has pointed out in his post today, RTF, LOL. - Original Message - From: Krister Ekstrom kris...@kristersplace.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 10:13 AM Subject: Re: Digi003 questions Hi and thanks for that info. this will surely come in handy once i’ve gotten the 003. /Krister 4 jan 2014 kl. 18:28 skrev Slau Halatyn slauhala...@gmail.com: Digi 003 Layout.rtf -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Digi003 questions
Thanks for the clerification. - Original Message - From: Slau Halatyn slauhala...@gmail.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 11:11 AM Subject: Re: Digi003 questions Ah, but the 003 has a different layout after all. I had purchased Gordon's 002 many years ago and upgraded to the 003 at some point and it was quite different. Just a heads up. Slau On Jan 4, 2014, at 3:08 PM, Poppa Bear heavens4r...@gmail.com wrote: Hello Chris, I use the 002 and they both have the same lay out from what I remember. I may be able to do some face time stuff with you if you get into a pinch here and there. I used my pen friend labeler to mark the different rows of buttons, but I don't remember alot of the names of the buttons, just the location and functions. Either way, I figured I would put the invatation out there and as Slau has pointed out in his post today, RTF, LOL. - Original Message - From: Krister Ekstrom kris...@kristersplace.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 10:13 AM Subject: Re: Digi003 questions Hi and thanks for that info. this will surely come in handy once i’ve gotten the 003. /Krister 4 jan 2014 kl. 18:28 skrev Slau Halatyn slauhala...@gmail.com: Digi 003 Layout.rtf -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Digi003 questions
Thanks so much, perhaps i will take you up on the offer.:-) I’m too restless to rtfms, but i guess it pays off to do that so i’ll hunt for a manual. Is there by any chance a online documentation? /Krister 4 jan 2014 kl. 21:08 skrev Poppa Bear heavens4r...@gmail.com: Hello Chris, I use the 002 and they both have the same lay out from what I remember. I may be able to do some face time stuff with you if you get into a pinch here and there. I used my pen friend labeler to mark the different rows of buttons, but I don't remember alot of the names of the buttons, just the location and functions. Either way, I figured I would put the invatation out there and as Slau has pointed out in his post today, RTF, LOL. - Original Message - From: Krister Ekstrom kris...@kristersplace.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 10:13 AM Subject: Re: Digi003 questions Hi and thanks for that info. this will surely come in handy once i’ve gotten the 003. /Krister 4 jan 2014 kl. 18:28 skrev Slau Halatyn slauhala...@gmail.com: Digi 003 Layout.rtf -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
Slau, YOU ARE A GENTLEMEN, AND A SCHOLAR! Grin! - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 11:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do the same. While it is certainly a simple matter to create a Pro Tools session, create a track and record-enable it, that is so much so only the
Re: a general observation about Pro Tools accessibility users
I can't even imagine trying to learn something like that in a different language. Hats off to you and others who are attempting it. :)Slau On Jan 4, 2014, at 4:02 PM, Ronald van Rhijn pa...@xs4all.nl wrote: Hi Slau, Nicely written… your words affect me personally (be asured, not in a harmful manner). Reading the Reference guide is very useful, at least more than once. As I did, but there can also be things complicating matters. As a non native English speaking person, the English technical character of the guide can be hard to understand at times. And when you don’t have enough basic knowledge of such recording programs, its even more difficult. Both above mentioned are true for me and was quite overhwlming for me. As you could guess, audio recording isn’t muy daily job, but would like to be doing something with it very much. Unfortunately I am no technical wonder, but creative I certainly am. Before I went visually impaired I did graphic design. Now I struggle to transform my visual creativity into audio creativity, but it is so different and complex. I love sounds all around me, but stil have no clue how or where to start properly. best, Ronald Op 4 jan. 2014, om 19:50 heeft Slau Halatyn slauhala...@gmail.com het volgende geschreven: With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into
Re: a general observation about Pro Tools accessibility users
I try, sir. :) Slau On Jan 4, 2014, at 3:44 PM, Sean A. Cummins seanacumm...@gmail.com wrote: Slau, YOU ARE A GENTLEMEN, AND A SCHOLAR! Grin! - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 11:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to
Select/split notes window.
Hi everyone, I am having a fantastic time working in PT 11, with several things I have been waiting for now accessible. Thanks again Slau. However, I noticed that in the event options/select/split notes window, there are 2 pop up menus that is still not accessible, although the rest of the window now is. I am hoping that it is a mistake I am making. The way it works is, once you enter this window, the easiest way being option Y, there are 3 sections, the first being where you can select the note range you want to split, the second is where you can select velocity range, position etc, and the third section is the actions section where you have 2 radio buttons 1 for select notes and the other for split notes, then there is a check box to include all midi data. These are all accessible as well as the apply button. However, there are also 2 pop up menus which allow you to either cut or copy in the first menu, and choose between cut to the clip board, or create new track per pitch and 1 more option that I can't remember right now. These 2 important menus are not accessible. Can some one please have a look at this for me and hopefully tell me that I am indeed making a mistake? Thanks in advance for any help. Jason -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: a general observation about Pro Tools accessibility users
I try, sir. :) On Jan 4, 2014, at 3:44 PM, Sean A. Cummins seanacumm...@gmail.com wrote: Slau, YOU ARE A GENTLEMEN, AND A SCHOLAR! Grin! - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 11:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do
Re: a general observation about Pro Tools accessibility users
I try, sir. :) On Jan 4, 2014, at 3:44 PM, Sean A. Cummins seanacumm...@gmail.com wrote: Slau, YOU ARE A GENTLEMEN, AND A SCHOLAR! Grin! - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 11:50 AM Subject: a general observation about Pro Tools accessibility users With the recent strides forward in Pro Tools accessibility, I wanted to share some thoughts. This is absolutely not referring to anybody in particular but rather a trend that we've seen over the years. It first started way back when Pro Tools first became accessible under OS 9, happened again when Pro Tools 8.0.4 came out and now I see it's happening again. With each ramping up of usability, there has historically been an influx of new users. When I first began using Pro Tools in college back in 1994, I had some usable vision but, when I began using it full time in the studio at around 2002, I had spent no less than six months reading the manuals. The first time I read the manuals, I understood fairly little, even though I had used Pro tools in the past and was well-versed in Digital Performer. Things are different in Pro Tools than other dAWs and so my level of understanding, while high in DP, was starting off much lower in Pro Tools. The second time I read the manual (and it was only about 900 pages back then as opposed to today's 1,200 pages), I began to see patterns and understand certain concepts in a basic way. The third time I read the manual (and I'm referring to the Pro Tools Reference Guide, of course), I did it while sitting in front of Pro Tools with a control surface. As I read the manual, I attempted to follow along and perform the various tasks. It was only then that I truly learned Pro Tools. No, actually, I did do one more thing that really solidified my understanding of the editing modes and behavior of Pro Tools and that was to sit down with some sighted assistance and systematically go through editing functions while the person explained what was happening visually on screen. That, along with the audio feedback of what I was editing solidified my understanding. All told, I spent about three months before installing the Pro Tools system just reading manuals and nothing else. I did this while still having an analog multitrack and console in the control room. I read in the evenings at home and kept working full time with the old system while I learned about the new Pro Tools software and hardware I was about to use. For me, the stakes were high because I was about to transform my studio and workflow entirely. Not only had I invested untold thousands in my previous analog system, but my new Pro Tools HD investment was roughly $25,000. Again, the stakes were high because this was my day job. I was going to work with clients sitting beside me, paying for my time and failure was not an option. Others have similar stories and, in each case, the ones who succeeded were the ones that lived by the old RTFM principle which, for those few who may not know, stands for read the fucking manual. Naturally, I write those words with no malice whatsoever. It's just a figure of speech but a very poignant phrase in this case for such an undertaking is not for the faint of heart. Need I point out the fact that, apart from the weighty Reference guide, there are multiple tomes for various aspects of hardware and software related to using Pro Tools. A peek in the documentation folder will reveal the plethora of reading choices. Now, there are obviously people on this list who use Pro Tools on a daily basis with clients and there are those who just want to record their own projects. The requirements for either type of person will vary accordingly and the knowledge level of each will be commensurate to their stake in the game. That includes their investment and what they need to get out of their system. As one of the people who falls into the second category, I have to say that it's clearly in my best interest from a time management standpoint to help raise the proficiency level of everybody so that I can spend less time answering very basic questions. Of course, that's already happened over the years and there are more and more people gaining the knowledge necessary to help new users with these basic issues. To be honest, I'm finding myself in the same boat, albeit on a higher level, having to learn about new features that weren't around when I learned Pro Tools so many years ago. For a considerable amount of time, Pro Tools moved on and many of us were stuck on an old version, missing out on those new features. Suddenly, we're finding ourselves facing the prospect of revisiting the RTFM process. As with most endeavors, one reaps what one sews. I, for one, am embarking on yet another marathon of reading the Pro Tools manuals and I encourage others to do
Protools accessibility
Hi all, Have just registered with this group. I am just curious, how accessible is Protools now these days? I am using Sonar on Windows, but just interested. Many thanks! Christian -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Accessibility issues prior to 11.1
Hello all, I downloaded the Pro Tools 11.0.2 version in the hopes that I would be able to familiarize myself with the interface in the few weeks that I am waiting for the full 11.1 version and my new audio/control surface hardware. The only version available is this 11.0.2 version prior to the added accessibility of 11.1. I figured I would at least still be able to learn something from this version. However, I am noticing something that is preventing a lot of my navigating through the system. I remember from Pro Tools 9 that the different windows accessible from the main menu under setup were accessible. Now, for example when I go to something like hardware or IO I get the window but nothing in that window is accessible at all? Was the accessibility really this bad in 11 or am I missing something? The new session window is also not accessible...I open it up and I get nothing...if I press enter it selects whatever session is highlighted and I am then able to get into the project and move around through the edit window. This seems near impossible to use if these windows are all truly inaccessible ... am I going to have to wait until 11.1 to really get into this software? -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Protools 9 access
I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out.
Re: Select/split notes window.
Hi Jason, I'm not very familiar with the window you're looking at. It's entirely possible that those two menus have not yet been defined. If so, be assured that they will be at some point in the future. There were several people involved in testing this and it would be impossible to address everything at once, of course. As you can see for yourself, there's been an enormous amount of progress and, above all else, it's a process. I'm not saying those particular controls are inaccessible, I truly don't know myself but what I am saying is that, if they're not, they will be. Hang in there :) Slau On Jan 4, 2014, at 6:12 PM, studiojay overdriverecord...@gmail.com wrote: Hi everyone, I am having a fantastic time working in PT 11, with several things I have been waiting for now accessible. Thanks again Slau. However, I noticed that in the event options/select/split notes window, there are 2 pop up menus that is still not accessible, although the rest of the window now is. I am hoping that it is a mistake I am making. The way it works is, once you enter this window, the easiest way being option Y, there are 3 sections, the first being where you can select the note range you want to split, the second is where you can select velocity range, position etc, and the third section is the actions section where you have 2 radio buttons 1 for select notes and the other for split notes, then there is a check box to include all midi data. These are all accessible as well as the apply button. However, there are also 2 pop up menus which allow you to either cut or copy in the first menu, and choose between cut to the clip board, or create new track per pitch and 1 more option that I can't remember right now. These 2 important menus are not accessible. Can some one please have a look at this for me and hopefully tell me that I am indeed making a mistake? Thanks in advance for any help. Jason -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Accessibility issues prior to 11.1
Hi Jason, Yes, it was truly that bad when the first beta of 11 came out earlier this year. I was really flummoxed at the steps backward. It was a wake up call to the folks at Avid who were also surprised at how the rewrite to 64-bit affected accessibility. If I told you about how many set backs there were even up until a few weeks ago, your head would spin. We're on the right track. Slau On Jan 4, 2014, at 8:26 PM, Jason kistler.ja...@gmail.com wrote: Hello all, I downloaded the Pro Tools 11.0.2 version in the hopes that I would be able to familiarize myself with the interface in the few weeks that I am waiting for the full 11.1 version and my new audio/control surface hardware. The only version available is this 11.0.2 version prior to the added accessibility of 11.1. I figured I would at least still be able to learn something from this version. However, I am noticing something that is preventing a lot of my navigating through the system. I remember from Pro Tools 9 that the different windows accessible from the main menu under setup were accessible. Now, for example when I go to something like hardware or IO I get the window but nothing in that window is accessible at all? Was the accessibility really this bad in 11 or am I missing something? The new session window is also not accessible...I open it up and I get nothing...if I press enter it selects whatever session is highlighted and I am then able to get into the project and move around through the edit window. This seems near impossible to use if these windows are all truly inaccessible ... am I going to have to wait until 11.1 to really get into this software? -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools accessibility
Hi christian, Welcome to the list. In attempting to answer your question, for illustration purposes, allow me to turn the tables just a little bit. I've never used Sonar. If I asked you how accessible it is, you might have some of the same thoughts that I have when I see a question like this. For example, how accessible something is has largely to do with how a person feels about it. In other words, what's quite accessible to one person might not be very accessible to another. Further, I have absolutely no idea what your knowledge and experience is so it makes it really challenging to answer a general question like that. If I had to answer as best I could, to me, Pro Tools is very accessible. There are aspects of it that are not yet accessible so, depending on your specific needs, it might make sense or not. Until recently, the MIDI Event List was not readable. That didn't mean you couldn't create MIDI tracks and record and edit them but you couldn't do it with the control and detail that you could in Sonar. Now you can. If MIDI was your thing, it wasn't terribly accessible, that is, until now. The more specific you are with questions of what's possible or not, the better people on the list will be able to answer. Your question is really a big one, as simple as it sounds and I'm sure you'd get a better answer if you could be more specific and tell us about what your needs are, what you're looking to do and maybe even why you're interested in Pro Tools if you're already working in Sonar. Cheers, Slau On Jan 4, 2014, at 6:31 PM, Christian christia...@runbox.com wrote: Hi all, Have just registered with this group. I am just curious, how accessible is Protools now these days? I am using Sonar on Windows, but just interested. Many thanks! Christian -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools accessibility
Hi christian, Welcome to the list. In attempting to answer your question, for illustration purposes, allow me to turn the tables just a little bit. I've never used Sonar. If I asked you how accessible it is, you might have some of the same thoughts that I have when I see a question like this. For example, how accessible something is has largely to do with how a person feels about it. In other words, what's quite accessible to one person might not be very accessible to another. Further, I have absolutely no idea what your knowledge and experience is so it makes it really challenging to answer a general question like that. If I had to answer as best I could, to me, Pro Tools is very accessible. There are aspects of it that are not yet accessible so, depending on your specific needs, it might make sense or not. Until recently, the MIDI Event List was not readable. That didn't mean you couldn't create MIDI tracks and record and edit them but you couldn't do it with the control and detail that you could in Sonar. Now you can. If MIDI was your thing, it wasn't terribly accessible, that is, until now. The more specific you are with questions of what's possible or not, the better people on the list will be able to answer. Your question is really a big one, as simple as it sounds and I'm sure you'd get a better answer if you could be more specific and tell us about what your needs are, what you're looking to do and maybe even why you're interested in Pro Tools if you're already working in Sonar. Cheers, Slau On Jan 4, 2014, at 6:31 PM, Christian christia...@runbox.com wrote: Hi all, Have just registered with this group. I am just curious, how accessible is Protools now these days? I am using Sonar on Windows, but just interested. Many thanks! Christian -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools accessibility
Hi christian, Welcome to the list. In attempting to answer your question, for illustration purposes, allow me to turn the tables just a little bit. I've never used Sonar. If I asked you how accessible it is, you might have some of the same thoughts that I have when I see a question like this. For example, how accessible something is has largely to do with how a person feels about it. In other words, what's quite accessible to one person might not be very accessible to another. Further, I have absolutely no idea what your knowledge and experience is so it makes it really challenging to answer a general question like that. If I had to answer as best I could, to me, Pro Tools is very accessible. There are aspects of it that are not yet accessible so, depending on your specific needs, it might make sense or not. Until recently, the MIDI Event List was not readable. That didn't mean you couldn't create MIDI tracks and record and edit them but you couldn't do it with the control and detail that you could in Sonar. Now you can. If MIDI was your thing, it wasn't terribly accessible, that is, until now. The more specific you are with questions of what's possible or not, the better people on the list will be able to answer. Your question is really a big one, as simple as it sounds and I'm sure you'd get a better answer if you could be more specific and tell us about what your needs are, what you're looking to do and maybe even why you're interested in Pro Tools if you're already working in Sonar. Cheers, Slau On Jan 4, 2014, at 6:31 PM, Christian christia...@runbox.com wrote: Hi all, Have just registered with this group. I am just curious, how accessible is Protools now these days? I am using Sonar on Windows, but just interested. Many thanks! Christian -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
I have read that the 002 is not supported, but have also read a few stories about the 003 family drivers working with PT 11 on the 002. But as you no, , when it is chrunch time you can't afford to just hope it works. Now in regards to a new control surfase, I am stuck on what to do. I rairly record more than a few sources at once, but I like to use my surfase for muting and selecting tracks, but beyond this, I have many of my waves plugs set as presets now so don't even use the surfase for dialing in plugin settings. I have often considered a 003 rack with the Black Lion audio mod on the converters and the mic pre's, but I just don't know if the quality of pre's and AD's are too dated at this point. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:17 PM Subject: Re: Protools 9 access Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
I haven't heard of the drivers working with 11 but that's entirely possible. The questions of whether something works or not is an important one and I sympathize, we all do. I guess the important thing is to define what it is that you need, exactly, and figure out what truly fits that need. Regarding the pres, I found the stock 003 preamps to be quite useable, especially with condensers. If using dynamics, I'd probably use a cloud Lifter or some such in-line booster. My two cents. Slau On Jan 5, 2014, at 12:50 AM, Poppa Bear heavens4r...@gmail.com wrote: I have read that the 002 is not supported, but have also read a few stories about the 003 family drivers working with PT 11 on the 002. But as you no, , when it is chrunch time you can't afford to just hope it works. Now in regards to a new control surfase, I am stuck on what to do. I rairly record more than a few sources at once, but I like to use my surfase for muting and selecting tracks, but beyond this, I have many of my waves plugs set as presets now so don't even use the surfase for dialing in plugin settings. I have often considered a 003 rack with the Black Lion audio mod on the converters and the mic pre's, but I just don't know if the quality of pre's and AD's are too dated at this point. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:17 PM Subject: Re: Protools 9 access Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email toptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools accessibility
Christian, I have been a Sonar user up untill this last year or so when I got my PT set up. At this point I run my small scale home recording studio with Pro Tools. I have clients in weekly to record, mix and do a little mastering. I can do everything in PT in those three areas as well as I could in Sonar. I have found that some steps are a little quicker in Sonar IMO, but having the reliability of the Mac, just one built in screen reader and the ability to work along side with my sighted counterparts on a fairly equal playing field, using the same DAW as them and sharing and colaberating on the same DAW makes up for anything I may miss about Sonar. HTH - Original Message - From: Slau Halatyn slauhala...@gmail.com To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:44 PM Subject: Re: Protools accessibility Hi christian, Welcome to the list. In attempting to answer your question, for illustration purposes, allow me to turn the tables just a little bit. I've never used Sonar. If I asked you how accessible it is, you might have some of the same thoughts that I have when I see a question like this. For example, how accessible something is has largely to do with how a person feels about it. In other words, what's quite accessible to one person might not be very accessible to another. Further, I have absolutely no idea what your knowledge and experience is so it makes it really challenging to answer a general question like that. If I had to answer as best I could, to me, Pro Tools is very accessible. There are aspects of it that are not yet accessible so, depending on your specific needs, it might make sense or not. Until recently, the MIDI Event List was not readable. That didn't mean you couldn't create MIDI tracks and record and edit them but you couldn't do it with the control and detail that you could in Sonar. Now you can. If MIDI was your thing, it wasn't terribly accessible, that is, until now. The more specific you are with questions of what's possible or not, the better people on the list will be able to answer. Your question is really a big one, as simple as it sounds and I'm sure you'd get a better answer if you could be more specific and tell us about what your needs are, what you're looking to do and maybe even why you're interested in Pro Tools if you're already working in Sonar. Cheers, Slau On Jan 4, 2014, at 6:31 PM, Christian christia...@runbox.com wrote: Hi all, Have just registered with this group. I am just curious, how accessible is Protools now these days? I am using Sonar on Windows, but just interested. Many thanks! Christian -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
I haven't heard of the drivers working with 11 but that's entirely possible. The questions of whether something works or not is an important one and I sympathize, we all do. I guess the important thing is to define what it is that you need, exactly, and figure out what truly fits that need. Regarding the pres, I found the stock 003 preamps to be quite useable, especially with condensers. If using dynamics, I'd probably use a cloud Lifter or some such in-line booster. My two cents. Slau On Jan 5, 2014, at 12:50 AM, Poppa Bear heavens4r...@gmail.com wrote: I have read that the 002 is not supported, but have also read a few stories about the 003 family drivers working with PT 11 on the 002. But as you no, , when it is chrunch time you can't afford to just hope it works. Now in regards to a new control surfase, I am stuck on what to do. I rairly record more than a few sources at once, but I like to use my surfase for muting and selecting tracks, but beyond this, I have many of my waves plugs set as presets now so don't even use the surfase for dialing in plugin settings. I have often considered a 003 rack with the Black Lion audio mod on the converters and the mic pre's, but I just don't know if the quality of pre's and AD's are too dated at this point. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:17 PM Subject: Re: Protools 9 access Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email toptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
I haven't heard of the drivers working with 11 but that's entirely possible. On Jan 5, 2014, at 12:50 AM, Poppa Bear heavens4r...@gmail.com wrote: I have read that the 002 is not supported, but have also read a few stories about the 003 family drivers working with PT 11 on the 002. But as you no, , when it is chrunch time you can't afford to just hope it works. Now in regards to a new control surfase, I am stuck on what to do. I rairly record more than a few sources at once, but I like to use my surfase for muting and selecting tracks, but beyond this, I have many of my waves plugs set as presets now so don't even use the surfase for dialing in plugin settings. I have often considered a 003 rack with the Black Lion audio mod on the converters and the mic pre's, but I just don't know if the quality of pre's and AD's are too dated at this point. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:17 PM Subject: Re: Protools 9 access Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email toptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Protools 9 access
Thanks Slau, I just want to be able to work when it is time to work and not have to deal with the extra stress of trouble shooting gear. Again, thanks for your time and energy with all of this. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:56 PM Subject: Re: Protools 9 access I haven't heard of the drivers working with 11 but that's entirely possible. The questions of whether something works or not is an important one and I sympathize, we all do. I guess the important thing is to define what it is that you need, exactly, and figure out what truly fits that need. Regarding the pres, I found the stock 003 preamps to be quite useable, especially with condensers. If using dynamics, I'd probably use a cloud Lifter or some such in-line booster. My two cents. Slau On Jan 5, 2014, at 12:50 AM, Poppa Bear heavens4r...@gmail.com wrote: I have read that the 002 is not supported, but have also read a few stories about the 003 family drivers working with PT 11 on the 002. But as you no, , when it is chrunch time you can't afford to just hope it works. Now in regards to a new control surfase, I am stuck on what to do. I rairly record more than a few sources at once, but I like to use my surfase for muting and selecting tracks, but beyond this, I have many of my waves plugs set as presets now so don't even use the surfase for dialing in plugin settings. I have often considered a 003 rack with the Black Lion audio mod on the converters and the mic pre's, but I just don't know if the quality of pre's and AD's are too dated at this point. - Original Message - From: Slau Halatyn To: ptaccess@googlegroups.com Sent: Saturday, January 04, 2014 8:17 PM Subject: Re: Protools 9 access Yes, accessibility of 9 is the same as 8. BTW, ditch the 002 as soon as you can. It's long since been discontinued and you're not going to be able to use it with 11, fyI. Slau On Jan 4, 2014, at 9:53 PM, Poppa Bear heavens4r...@gmail.com wrote: I have stayed with PT 8 and wanted to upgrade to 11, but am still not sure, I don't know if I want to go through the battle of getting my 002 to work seemlessly and upgrade all of my Wave plugins to the aax V9 R14 64 bit versions. I have quite a bit of work coming into the studio and can't afford to be down for a week making tweeks. For these reasons I am thinking about just stepping up to V9 so I have the option to intagrate a new control surfase in and go on from there. So, with PT9, do all of the edit fields read as they did in the first 8.04 update? 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/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email toptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Pro Tools Accessibility group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
