Hi Gabe, Well, I think just about everybody here has been indignant at being perceived as not being able to perform a particular task or get something done as a blind person. Who here hasn't experienced that frustration? Sometimes it's just not worth needing to prove oneself. I don't solder cables. I'm sure I could if I had to. I'm capable of figuring out alternative means to achieve the desired result and, sure, that would probably be satisfying and I'd have a sense of accomplishment but you know what? I'd rather pay someone to do it and not waste my time to prove something. It's pointless unless that particular thing is my passion and it's not. Even with something like audio recording, which so many blind individuals are passionate about, some challenges are worth pursuing and perhaps others are not. I think we all need to choose our battles wisely because we're ultimately fighting them alone.
This all started with the idea of a blind person working in a studio. Now, every situation is unique and I'm not saying that it's inconceivable for a blind individual to somehow be gainfully employed by a commercial studio but it's highly improbable in general. Yes, there are exceptions and I'm not saying this is a rule to begin with but, in the grand scheme of things, a blind audio professional is, in my opinion, far better off competing as a sole proprietor or within their own production team. Slau Slau On Jan 9, 2014, at 10:46 PM, Gabe Vega <theblindt...@gmail.com> wrote: > hey buddy, you got to be the most on your game clear headed blind person I > have the pleasure to know. where most blind people try to be super man and do > all of end all, you just laid it out very clear. my thoughts exactly. thanks > so much to your contribution to this list and to the industry as a whole. > > Gabe Vega > CEO > Commtech LLC > Web: http://commtechusa.net > FaceBook: http://facebook.com/commtechllc > Twitter: http://twitter.com/commtechllc > Email: i...@commtechusa.net > Phone: (888) 351-5289 ext. 710 > Fax: (480) 535-7649 > > On Jan 9, 2014, at 2:31 PM, Slau Halatyn <slauhala...@gmail.com> wrote: > >> I think all capable blind individuals would argue that, in some ways, blind >> people are forced to adopt extremely streamlined and efficient workflows for >> all kinds of things in life in order to function. Yes, there are some tasks >> like mousing around that are slower but, to argue that point, most young >> computer operators are quite adept at using the keyboard and, apart from >> just being young genii, are super fast. I don't care how fast a blind user >> is on a computer, not being able to see is just flat out a game changer and, >> as I've said before, and I'm not saying it's fair, but there's no contest >> between a sighted employee and a blind employee when it comes to the >> all-around work in a studio. I'm not saying that an experienced engineer >> can't come into a studio and work but, they will have never climbed the >> ladder in such an establishment. There are simply too many obstacles, >> literally and figuratively, and the cons outweigh the pros. Lest you >> misconstrue my position, I contend that, while there are alternative means >> to perform a great number of tasks for a blind person, again, there's no >> contest when it comes to all things being equal and one person being sighted >> and the other being blind. >> >> Slau >> >> On Jan 9, 2014, at 3:37 PM, Poppa Bear <heavens4r...@gmail.com> wrote: >> >>> Slau, I do think that sighted people often do have the advantage in any >>> vocation, but at the same time, I do notice that it is easy for sighted >>> people to take for Granit certain tasks and grow complacent in the way that >>> they perform them. For instance, I am able to do certain tasks much quicker >>> through some shortcut keys that sighted folks just don’t realize are there. >>> I have even found some engineers that use shortcut keys as much as possible >>> because they are often direct and concise with each execution. Sometimes >>> people wave the mouse around just to click on one task, “chasing the >>> mouse,” is an annoyance for more than one engineer. Also, I think that as a >>> blind user I have an entirely different, if you will, an extra perspective >>> on trouble shooting difficulties. Never the less, I agree with you in a >>> macro since, but I also think that there can be variables that can change >>> the playing field. >>> >>> ----- Original Message ----- From: "Slau Halatyn" <slauhala...@gmail.com> >>> To: <ptaccess@googlegroups.com> >>> Sent: Thursday, January 09, 2014 10:12 AM >>> Subject: Re: working in a studio with pro tools? >>> >>> >>> Hi Blake, >>> >>> I did that episode maybe 7 years ago so it's long gone. >>> >>> Regarding sighted tasks, I can't even begin to list the things that would >>> require sight. Trust me, even something as mundane as jumping in a car to >>> drive to the nearest Radio Shack because you need an XLR gender switcher is >>> something that clearly requires sight. Between two candidates who might >>> even know Pro Tools equally well, the sighted person has the advantage, >>> hands down, every time, no question. >>> >>> Slau >>> >>> On Jan 8, 2014, at 11:31 PM, Blake Hardin <blakehardin5...@gmail.com> wrote: >>> >>>> Hi all, thanks for the feedback. Slau, d you have a link to your >>>> podcasts that you have done for pro tools? As far as getting the job, >>>> I have ran my own home studio for probably around 5 years now. So, I >>>> am very experienced in recording drums, horns, guitars, and vocals. I >>>> also have around 15 different mics and mix different projects in sonar >>>> as well. I can't really run this as a business because it's out of my >>>> house and I can't get a licens to do that. Anyway, so I could do >>>> everything needed for the job except run pro tools. Now, I am more >>>> than willing to learn pro tools so I guess I will have to see how it >>>> goes. They are a brand new studio, so I guess the question of using >>>> Sonar from my own computer probably wont fly with them. Any other >>>> ideas? What kind of things were you talking about that requires sight? >>>> Thanks >>>> >>>> On 1/8/14, TheOreoMonster <monkeypushe...@gmail.com> wrote: >>>>> Actually version 10 should be just accessible as version 9 provided you >>>>> remained on Lion and did not upgrade to mountain lion. Just remove the AAX >>>>> plugins after each install or update to force it to fall back to RTAS >>>>> plug >>>>> ins and you are good to go. >>>>> >>>>> >>>>> On Jan 8, 2014, at 3:32 PM, Nick Daniels <nick....@ntlbusiness.com> wrote: >>>>> >>>>>> Yeah i know that Sonar and PT are different daws. i have experience with >>>>>> both of them. >>>>>> >>>>>> and the fact that the key strokes are different comes down to the fact >>>>>> that 1 works well on windows, whilst the other works on the mac. so >>>>>> inevitably, they will be different. >>>>>> >>>>>> Is ProTools as accessible as sonar? i beg to differ. from past experience >>>>>> there are things that i was able to do in sonar with the cake talking >>>>>> scripts, that i wasn't able to do with PT with Voiceover. hence the 2 >>>>>> items I've mentioned to Slau earlier today. But if what i hear is true, >>>>>> then i'll certainly purchase an upgrade and check it out. >>>>>> >>>>>> And as for sonar falling behind on accessibility? That is true, but as >>>>>> other people who are on the cake talking list can confirm, the developer >>>>>> of the jaws scripts [cake talking] is working on updated scripts for the >>>>>> latest version of sonar. so yes they are behind at the moment, but with >>>>>> luck, they'll catch up. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -----Original Message----- From: Poppa Bear >>>>>> Sent: Wednesday, January 08, 2014 6:17 PM >>>>>> To: ptaccess@googlegroups.com >>>>>> Subject: Re: working in a studio with pro tools? >>>>>> >>>>>> Sonar and PT are both different so don't think that the steps that you >>>>>> would >>>>>> take in Sonar are the same in PT, all keystrokes are different, bus >>>>>> management is different, plugin implamentation is different, and on and >>>>>> on. >>>>>> Is PT is accessible as Sonar, I would say after almost a year and a half >>>>>> of >>>>>> using it, yes, is Sonar falling more and more behind on accessibility, >>>>>> yes, >>>>>> so all things being considered the ball is in your court now. I think >>>>>> Slau >>>>>> made a great point, as I paraphrase and add some of my own thoughts, if >>>>>> your >>>>>> a musician making your own music, almost any program you can get action >>>>>> in >>>>>> will work, but if you want an universal daw that is found behind almost >>>>>> every major album project and recording studio then PT is it. >>>>>> ----- Original Message ----- From: "Chris Smart" <csma...@cogeco.ca> >>>>>> To: <ptaccess@googlegroups.com> >>>>>> Sent: Wednesday, January 08, 2014 7:59 AM >>>>>> Subject: Re: working in a studio with pro tools? >>>>>> >>>>>> >>>>>> Yes, try learning it first, RTFM! >>>>>> At 08:17 AM 1/8/2014, you wrote: >>>>>>> Simple answer, Yes to all your questions. Though you won’t get a job at >>>>>>> that studio never using Pro Tools before no matter how accessible it >>>>>>> is. >>>>>>> >>>>>>> >>>>>>> On Jan 8, 2014, at 8:03 AM, Blake Hardin <blakehardin5...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> hi all there is a studio coming to my area that i sent in a resume >>>>>>>> for. However they are running pro tools. How usable is it at this >>>>>>>> point? I have never used it i am used to using sonar. So like can we >>>>>>>> move audio around and such? How about use compressers and eq? I have >>>>>>>> used a mac before but not pro tools. Thanks >>>>>>>> >>>>>>>> On 1/8/14, John André Lium-Netland <eml...@a-pro-studio.no> wrote: >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> I just have to join in and say thanks for all your efforts to Slau >>>>>>>>> and >>>>>>>>> others that have contributed to all the good things happening with PT >>>>>>>>>>> now. >>>>>>>>> So far, I have installed Source Talkback 1.2, Ozone 5 and AutoTune as >>>>>>>>>>> well >>>>>>>>> as the AIR Expansion Pack Upgrade 2.0 with PT 11.1.0. >>>>>>>>> >>>>>>>>> For Ozone 5, you have access to all those controls contained in the >>>>>>>>> >> >>>>>>>>> plugin >>>>>>>>> window, but none of the controls in the extra window where the Preset >>>>>>>>> Manager is located. But I have found a work-around for this. I have a >>>>>>>>>>> list >>>>>>>>> of all the presets in text format. When I want to select one of them >>>>>>>>>>> from >>>>>>>>> the Preset Manager, I move the VO cursor to the last item in the >>>>>>>>> plugin >>>>>>>>> window, the one where you can interact and edit settings, but do not >>>>>>>>> interact in this case. Only route your mouse >>>>>>> cursor to the same location and >>>>>>>>> click with shift-control-option-space. You will then be able to use >>>>>>>>> the >>>>>>>>> arrow up/down keys to select presets, but >>>>>>> you will not get any feedback from >>>>>>>>> VO. You just have to arrow up until you are >>>>>>> sure you're on the first choice, >>>>>>>>> and then press the arrow down key the number of times associated with >>>>>>>>>>> the >>>>>>>>> number in the Preset list. Not an ideal situation at all, but it works >>>>>>>>>>> for >>>>>>>>> now. I have of course asked the developer to make this window >> >>>>>>>>> accessible >>>>>>>>> with VO, and suggest others to write them as well. >>>>>>>>> >>>>>>>>> Source Talkback and AutoTune is pretty accessible as far as I have >> >>>>>>>>> tested >>>>>>>>> them yet, although I think there is still >>>>>>> things in AT that doesn't show up >>>>>>>>> with VO. >>>>>>>>> >>>>>>>>> The AIR instruments are a mixed experience, >>>>>>> since I have not found a way to >>>>>>>>> work with Structure yet. >>>>>>>>> >>>>>>>>> My main problem right now is that after >>>>>>> doing a totally default installation >>>>>>>>> both of PT11.1, the Creative Collection and the Expansion Pack 2.0, >>>>>>>>> the >>>>>>>>> presets for instruments like Strike, Valvet etc. does not show up in >>>>>>>>>>> the >>>>>>>>> menu in the plugin. If anyone has any ideas or similar experience >>>>>>>>> here, >>>>>>>>> please let me know. ;) >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> John André Lium-Netland >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *** >>>>>>>>> John André Lium-Netland - Voice/SMS/MMS (+47) 971 68 794 >>>>>>>>> Visit online at www.a-pro-studio.no >>>>>>>>> *** >>>>>>>>> >>>>>>>>> On 8. jan. 2014, at 07:44, chad baker wrote: >>>>>>>>> >>>>>>>>>> hi cameron i have ssd 4 platnium and a public release candidate got >>>>>>>>>> released to work with pt11 its a a justt login into your s s d >>>>>>>>>> account >>>>>>>>>> On Jan 7, 2014, at 9:44 PM, Cameron Strife >>>>>>>>>> <came...@cameronstrife.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I'm wondering about SSD4 platinum, Synthogy Ivory 2, and Omnisphere >>>>>>>>>>>>>>> in >>>>>>>>>>> particular... >>>>>>>>>>> >>>>>>>>>>> Cameron. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 1/7/14, Scott Chesworth <scottcheswo...@gmail.com> wrote: >>>>>>>>>>>> Hey folks, >>>>>>>>>>>> >>>>>>>>>>>> Having had a breif bit of time in front of PT 11.1, I'm pretty >>>>>>>>>>>> excited. Unfortunately the system I got to tinker with had only >>>>>>>>>>>>>>>>> stock >>>>>>>>>>>> plugs installed, so just wanted to start a thread on here to find >>>>>>>>>>>>>>>>> out >>>>>>>>>>>> how everyone is finding access to third party AAX plugins now? >>>>>>>>>>>> >>>>>>>>>>>> In particular, I was wondering whether anyone has tried the public >>>>>>>>>>>> beta of Slate SSD4 yet? Even if not, it'd be good to find out what >>>>>>>>>>>>>>>>> the >>>>>>>>>>>> new changes effect for as much third party stuff as possible, so >>>>>>>>>>>> if >>>>>>>>>>>> you've tried anything, let us all know. >>>>>>>>>>>> >>>>>>>>>>>> Cheers >>>>>>>>>>>> >>>>>>>>>>>> Scott >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>>>>> Groups >>>>>>>>>>>> "Pro Tools Accessibility" group. >>>>>>>>>>>> To unsubscribe from 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. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Looking to take your guitar playing to the next level? Go to >>>>>>>> http://onlineleadguitarlessons.com >>>>>>>> for tips and lessons! >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are >>>>>>> subscribed to the Google Groups "Pro Tools Accessibility" group. >>>>>>>> To unsubscribe from 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. >>>>>> -- >>>>>> You received this message because you are subscribed to the Google Groups >>>>>> "Pro Tools Accessibility" group. >>>>>> To unsubscribe from 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. >>>>> >>>> >>>> >>>> -- >>>> Looking to take your guitar playing to the next level? Go to >>>> http://onlineleadguitarlessons.com >>>> for tips and lessons! >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Pro Tools Accessibility" group. >>>> To unsubscribe from 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. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from 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.
