By dtaa pla muk
Tue Apr 07, 2009 8:54 pm
not missing the point, it's simply that i've talked to jj about this and know what the situation is. i've already detailed it fully on the forum and had hoped to not have to do the whole thing again, but here is the short of it:
OLD SIMULT behavior is excellent.
unfortunately, OLD SIMULT behavior causes bugs in many areas of the OS.
it caused these bugs in OS1, OS2, and OS2xl. users had to chase these down time and time again.
because of OLD SIMULT, changing one small thing in one area of the OS could cause problems in a number of many other parts of the OS.
this requires a LOT of continuous testing and a lot of bug-resurgence at every change.
as it was, OLD SIMULT was a shaky foundation that needed constant ramification.
if we could achieve the same behavior in some other way, this would be ideal. however, a return to the same programming used to implement OLD SIMULT would cause a LOT of problems. jj needs another way to skin this cat.
this entire poll is misleadingly worded and needs to have the entire premise edited. it shouldn't be "wat should we give in return for old simult LOL" it should be "who wants old simult type behavior back?"
in meantimes, it would be both confusing and ineffective to send this as it currently stands without some introduction like "forgive them, they know not what they ask for."
OLD SIMULT behavior is excellent.
unfortunately, OLD SIMULT behavior causes bugs in many areas of the OS.
it caused these bugs in OS1, OS2, and OS2xl. users had to chase these down time and time again.
because of OLD SIMULT, changing one small thing in one area of the OS could cause problems in a number of many other parts of the OS.
this requires a LOT of continuous testing and a lot of bug-resurgence at every change.
as it was, OLD SIMULT was a shaky foundation that needed constant ramification.
if we could achieve the same behavior in some other way, this would be ideal. however, a return to the same programming used to implement OLD SIMULT would cause a LOT of problems. jj needs another way to skin this cat.
SIMULT PAD.
In voice ON/OFF processing, an exception records Master PAD.
The software with an exception tends to generate a bug.
DRUM/INST/CHORD/ARPEGITER/SIMULT PAD/SIMUTE SEQ./ Other .. You have to test these [every time].
When adding a new function, you have to check that this always operates normally.
It is difficult to build without this also generating a bug.
Much time is spent on this.
this entire poll is misleadingly worded and needs to have the entire premise edited. it shouldn't be "wat should we give in return for old simult LOL" it should be "who wants old simult type behavior back?"
in meantimes, it would be both confusing and ineffective to send this as it currently stands without some introduction like "forgive them, they know not what they ask for."





