| Yeah, drop is probably a reserved sql keyword.
And I know at one point; I guess they were running different software;
drop did work as a keyword.
But the fallout from this co-incidence is that dozens apon dozens of users
have been fighting the same problem and can't see each others comments...
This does *not* however; get lynx off the hook; because supposedly
they read every message.
They knew about the problems alot time ago.
And what has been asked for; several times and not received is
an official response/dialog on the issue.
You can sticky it, but it in pauls comments thing or whatever.
A sticky or a absolutely unmistakably noticeable place on the website is needed.
the time for protecting intellectually property is long long.
The statement needs to cover the dropouts, the tineline of the issue and those
that compliment it.
It's not hard; and obviously; why isn't completely obvious is beyond me.
You're co-founder for #$%$% sake david. You can make that call.
It needs to discuss the time frame; what's been fixed ; like the gui memory leak,
in a straightforward english manner that all current and potential users can
follow.
The driver notes are not complete enough; they are vague; and you know
at least half of the users are computer savvy.. write it for them.
The music users just need know you're sugar coated summary.
The time frame needs to include where you're at; If you guys are still
under the honest impression that you're code is not at fault and 50%
of your users have dropout generating systems; then for #$%#%$ SAKE
get the approved configurations in that sticky. The time for being
"MB" agnostic is gone.
The users *MUST* have a reference system.. For that matter
( I can't remember if one exists in the PD yet.) but a #$%#$%ing
virtual driver for perfection situation testing should be offered then.
Give me a generic freaking host dummy driver I can stick in my system.
(Or suggest one that exists. that is ASIO)
And I'll test that; Don't continue to hide the statistics window; Tell people
about the reported issues with more than 1 card. Yes I know;
paul and "a couple other" people have 4 cards working. Fine;
but that was supposed to be in a 2895 and you have a user reporting
the issue on it.
You *MUST* come to grips with the fact that if this is truly (NOT) you're
problem (which is what was claimed *OVER* and *OVER* again but 50% of your customer base either mis configuring or having
what ends up being generally incompatible systems is going to be your
bad and your problem.
*SOMETHING* in the hardware/driver combination is *EXTREMELY* untolerable
to dropouts; You have admitted this with release of your beta driver;
BUT FOR $#%T#%^#%^ SAKE, make a STICKY AND EX PLAINT IT.
DONT CONTINUE TO BE ELUSIVE AND EXCLUSIVE; you are inconsistant between
even the two of you. COME CLEAN AND TAKE THE BLOWS AND SOLVE THE
#$^%#$% PROBLEM ONCE AND FOR ALL.
You know; IM CRAZY TO SAY THIS AFTER THE HUNDREDS of HOURS I've
spent on it. But I would actually consider trying them again if
you came clean and SAID WHAT WAS WRONG AND STICKY IT! |