It's great to know that it's not a dead issue. Frankly, I'd be willing to
chip in a few bucks to bring somebody onboard if they were going to be
dedicated to taking on this project and had the necessary access to source
code, which could be a problem.
Gord
-----Original Message-----
From: Slau Halatyn
Sent: Thursday, August 16, 2012 7:52 PM
To: ptaccess@googlegroups.com
Subject: a brief debriefing on Pro Tools
Folks,
I just wanted to briefly give you a little synopsis regarding accessibility
issues in Pro Tools. As most of you know, there have been some changes of
late. Actually, there are the changes in Pro Tools, of course, but more
importantly, there have been significant changes at Avid. If you keep up
with the business section of your paper, you'll have read about the
investments and divestments involving Avid, their staff, their affiliated
companies, etc. This is truly a difficult period for the company.
At any rate, I did speak with Bobby Lombardi and we talked about possible
solutions for the future. Part of it might involve taking on an intern, not
unlike the last time, and tackling the most pressing issues. There's another
possibility that involves a sort of "hackathon" where programmers take on
special projects and run with it to see how far they get and, if their work
seems successful enough, they incorporate it into the application. Without
delving into more details (because at this point, we know which is more
likely), we're going to touch base in a few more weeks and to see where we
stand. I'll be going out to San francisco at the end of October and will
have some face-to-face time with Bobby and others with whom I've kept in
touch.
There's another development that might potentially help push things along a
bit but it's too early to discuss. As soon as I have more information, I'll
share it here.
Best,
Slau
