Hi Yuma, I would be happy to work with you on the plug-ins. No payment required, but may be Rob will allow me to have a copy of the plug-ins so we could both work with him to make them accessible? If you think this is a good idea, please contact him about it. With Christmas being right around the corner, may be we could talk the first week in January? Merry Christmas. Jason
Yuma Decaux wrote: > HI Jason, > > No problem. It's always good to have something moving, even if it will be > overtaken by events such as the developers deciding to unlock accessibility > paradigms on seemingly difficult areas of an application such as pt or logic > for example. > > I was wondering about something else, if your brother in law would be > interested. > > I have a set of incredible plugins from rob papin, most importantly predator > and punch. > > I have tried some methods for accessing different areas of an interface voice > over can't read, simply by using terminal commands to place the mouse on an > xy coordinate and click on the element. > > This however is really not the best implementation as it requires a lot of > data punching for all the elements on the screen. > > I was wondering if your brother was interested in getting hired lol for a bit > to implement a quikeys accessibility frame for those plugins. Name the price > and i will consider it. > > My idea here is to showcase the accessibility to predator which can first > hand show them how it should work, and their engineers can then have all the > precognitive assets such as a working demo, my own research and articles on > implementing this with the coco framework, and other tidbits. > > They have already expressed interest in making this possible, but so far i > just need to be able to map certain paremeter sliders to my midi controller. > > Let me know if we can do something > > Best regards, > > Yuma > > > On 14/12/2011, at 4:33 PM, studiojay wrote: > > > Hi Yuma, Thanks for your message. I will be in touch soon. Kind > > regards. Jason > > > > > > Yuma Decaux wrote: > >> Hi, > >> > >> I have been following this thread since you posted it, as well as the > >> responses. I believe it's generally due to how much effort has already > >> been spent by everyone to make accessibility improvements, then life > >> takes over, things get sour and disenchanted. > >> > >> I am however not in that category, and am still activelysupporting > >> developers by providing feedback and other tools to make their > >> applications, plugins etc accessible.Sometimes it's a bit depressing as it > >> takes time, and a lot of developers are also restrained by bottom lines > >> which in turn affects their lifestyles. Bigger companies, though first > >> contact people are usually emphatic, have a policy of sending these > >> requests up the chain and it often gets lost somewhere, unless some > >> invidiual can pull strings either through medias or otherwise to make > >> things accessible. > >> > >> As for the quikeys thing, i'm cool participating just by principle, it > >> doesn't matter how far this project goes but if i can give an example to > >> my dedication to make things accessible, however the means, then it's > >> money well spent. > >> > >> Let me know how you want me to proceed. > >> > >> On a side note, there were talks to put such projects for logic pro for > >> example on kickstarter, however since i'm not in the US i can't register a > >> holding to get funds. > >> > >> Anyway, try that alternative if you feel you can, and otherwise if you are > >> fairly confident that your brother can provide a result soon, then just > >> let me know how i can help > >> > >> Best regards, > >> > >> Yuma > >> > >> > >> > >> On 13/12/2011, at 4:18 PM, studiojay wrote: > >> > >>> Hey guys, Due to the responces, I am going solo on this project. I > >>> refuse to accept that some functions in pro tools are not accessible. > >>> My clients really don't care weather or not the midi event editor is > >>> accessible. If I can't do the job, they will go to some one else. As > >>> far as I am concerned, a program that is %75 accessible, might as well > >>> be %0 accessible. I am not prepared to wait 3 more years untill some > >>> one at avid feels sorry for the pour blind people and decides to spend > >>> a few hours an makes 2 more windows accessible. It's very sad that > >>> some many people are contented with %75 accessibility. It's also sad > >>> that people find $50 or $60 is too much for a good shot at so much > >>> more accessibility. It's also unfair to ask if you will get back your > >>> money if things don't work out. What about the long days and weeks > >>> that needs to be invested to give this a good shot? And the quick keys > >>> licences that will cost so much less for every one if we move as a > >>> teem in persute of greater accessibility? I really don't mean to > >>> offend any one on this list, but I am really saddened by your > >>> responces. I am going to have an accessible midi event editor as a > >>> Christmas gift, so I can edit the tracks that I have input quantised. > >>> Best regards. Jason > >>> > >>>
