There is no such thing as a bug that is not
reproduceable. Such is called human error ( and even that is reproduceable).
If there are timing issues, you *should* reproduce
them, record them, publish them and forward them to E-mu don't you
think?
In regard to the spurios notes that popped up live,
since you have a recording, can you make a small snippet mp3 of the negative
event and post it here?
These are the only things that can solve these
issues faster.
Ravi
----- Original Message -----From: Nick RothwellSent: Wednesday, October 02, 2002 10:38 AMSubject: Re: [xl7] rE: EMU "supporting" their products> What bugs does everyone keep talking about? I know Nick's Arp bug has
> been confirmed, but what other bugs is everyone so keen to see fixed?
There's a difference between confirmed, reproducible bugs and bugs
which are subtle, debateable, not totally reproducible, or downright
difficult to describe. My gut feeling is that there are a few lurkers
of the latter kind, which I could track down with time (but I've been
short of that lately).
Example: the sequencer timing is (for my purposes) sufficiently bad in
some circumstances as to make it unusable. I can post millisecond
timings, upload MP3's, whatever, but other people might not notice the
timing problems, and this kind of performance problem is arguably not
a functional bug anyway.
Example 2: in a recent live set, realtime control of the arpeggiation
timing interval generated spurious notes. I consider this a bug, but
it's going to be hard to track it down and describe the exact
circumstances, which might well be due to race conditions. (I do have
a recording of the set, so I will try to reproduce it.)
--
nick rothwell -- composition, systems, performance -- http://www.cassiel.com
To unsubscribe from this group, send an email to:
xl7-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.