[A6] Re: Request list - sorted...

[MelloT at aol.com]

>>>I believe a simple solution would be to create a  sysex command sequencers 
could be programmed with to instruct the a6 to do a  note-off command when a 
certain voice had finished playing its part in the  song?>>>




I agree with you about such a serious issue, BUT...
 
That's not really a simple solution. Many people do not write code  into 
sequencers, so if it is a problem that is defineable and repeatable,  it should be 
addressed and fixed IN the A6 code. It MAY NOT be an A6 problem at  all; not 
everyone gets hung notes, so it may be something else. That is why  Alesis has 
a serious bug-report format:
 
To report a bug, you need to show (in a repeatable, "this always happens"  
fashion) how to make the A6 hang a note from a sequencer. What hardware and  
software you use. Sometimes it is an incompatibility there. 
 
- Get it to happen - note which voice is holding (what sound, what note).  Do 
the same sequence again, does it repeat? If it does, play with other sounds  
on that sequence and see if they hang or not. Adjust the envelope of the sound 
 that hangs, maybe this affects it. Maybe the Release time affects it... If 
it  doesn't repeat, you neede to try and find out what MIGHT have made it 
happen.  Otherwise they may never find "the bug" and think it's all OK.
- Show what is used (does it only affect MIX mode?), how many voices might  
be affected (or maybe it is always Voice #13, for example). 
- Maybe it happens when you send TOO MANY notes to the A6. Check and  try.
- Maybe it happens when you send a program change to the A6, or other  
unrelated Sysex info from the Sequencer. 
- Can you get it to happen in MONO mode, do ALL the stacked notes hang  then?
- Does it happen with simple little sequences, or when many fast notes  
happen, or when you "use more than 6 sounds in a MIX", for example. 
 
This is stuff the WILL need to know, if they approach ANY bug. So far, no  
one's sent us test info on any of the reported bugs (exceot the square wave,  
which we know). (And the poly aftertouch, which we are calling a bug, but  
isn't.) 
 
BrianK