You wrote:
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.
Now wait a minute here! What part of the editor are you having problems
with? I see people like Kevin Reeves, or Slau etc. who use the editer
pretty much on a daily basis, who say it works fantasticly.
Can you give us more detail what parts are not working accessibly that these
modifications would allow us to do?
Rather than you shouting your dismay back at us, maybe for a change Mister,
smart butt, you could tell us what you all intend to do specifically to make
it better.
I know it would improve the editer window, but that doesn't say much. What,
specifically, are you all wanting to do to make the window better than it
already is.
If you have a numeric keypad, you're pretty much already set as far as
editting goes, for the most part.
You wrote:
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.
For one thing, quote: poor blind people? Is that how you see us? You
know, your response saddens me more than people giving their opinion, boss.
You asked our opinions, so don't you, dare! be offended at our responses.
If you didn't want to take the heat that possibly, there would be some
objections, then you shouldn't! have asked to start with. Furthermore, I
hate to bust your bubble, but it's amazing people like Slau, and Kevin, etc.
who have actually helped to shape the Pro tools environment, and make it
what it is today. Initially, it really wasn't accessible at all, then, when
Avid took over from Digidesign, things started improving, so this in my
book, is a direct slammed slanderization to Avid, which quite frankly, as
hard as that company has worked, I really don't appreciate.
You wrote:
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.
You know, again, you're taking completely out of context what we all said.
None of us ever! said we'd not be willing to pay. We only said that's a
very very high price, for not knowing if it really would help matters.
Perhaps what you need is to privately allow a few people, even if only 3 or
4, a free copy, and let them alpha, beta test it. If it works well, then
great, have them pay once the beta cycle is over.
This way everyone involved in development gets the feedback from users up
front. Bluntly Sir, I am not paying $50, $60, or $10 thousand! to a project
that hasn't even started yet, and where we don't know how it would work.
I'm sorry, but it's just not gonna happen!
It was made mention we could get a multi person license for everyone on the
list. How do we honestly know that would be what the money would be spent
for? It sounds like you're more concerned about our money than the time it
would take to make this, as all you're doing is bitching about how it's sad
we won't pay.
You wrote:
It's also unfair to ask if you will get back your
money if things don't work out.
Excuse us? WTF! So, if it doesn't work, you're just gonna eat our money
anyway, because it took time to make something that didn't wind up working?
Oh, that's real professional! That makes me real! comfortable about giving
you my money end of the bargain. I could see paying up front, but, realize
it would be a chance we'd be taking being you'd not let us test drive it, so
if we pay that much then don't like it, guess what, you still keep our
money? Think about what you're saying!
You wrote:
What about the long days and weeks
that needs to be invested to give this a good shot?
Well, first of all, you said you all wanted it ready by the end of
Christmas, if I remember what you all said.
Uh, sir, Christmas is not next Sunday, but the Sunday after that.
That's not a few weeks/months. So, quit using that lame excuse. Second of
all, I understand effort would be put into this, but that doesn't mean you
eat soemone's money just because your efforts didn't work.
You wrote:
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?
First of all, what even is! quote: Quick Keys, to start with? Second of
all, you're going right back to the money aspect. You may try defending
saying it's less, but the thing is, you want our money, like it or not,
others on the list may kill me, mods may ban me for being so down right
quote unquote, rude, to you, but I call it as I see it, and this is how I
see it. You, want, our, money! You don't have to like what I'm saying, and
I give you the leeway to not like it, but you let me say this, Buster, get
over it! Just as you have the right to form an opinion, so do we. You
asked, and now you're pissed off because you don't like our answers? Well,
excuse? us!
It may be a good project to take on, but you've been asked multiple times
not just by me, but by others, how it would benefit, what will it do better?
And you've been very vaigue. You can't say, we dono yet, we haven't gotten
that far.
pataintly, you're far enough to wanna do this, and you're far enough to have
some ideas, so, do tell! ¡Di me!
You wrote:
I really don't mean to
offend any one on this list, but I am really saddened by your
responces.
Well, that's your decision to be. No one's gonna stop you, and I respect
your opinion on the matter. But, you haven't given at least me enough
reason to see that this would be beneficial.
I need more info. The lack of info you're giving us makes this sound very
very, and did I mention, very! suspicious.
You wrote:
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.
OK, Jacen, then have the gift, as I'm done. BTW, Quantizing already is
accessible in PT, from what I can see.
Chris.