Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By trybtek Wed Feb 04, 2009 5:02 am
Hey all,
So whats happening with 'Old Simult' and OS2XL?
Are we getting it back?
Have people given up on it?
Work arounds?
Just traveling at the moment so i havent had a chance to get up to date on the issue.
Really hope we get it back!
Its the way simult should work!
Peace!
By dtaa pla muk Wed Feb 04, 2009 5:07 am
regarding old simult:

[old simult]tends to generate a bug.
DRUM/INST/CHORD/ARPEGITER/SIMULT PAD/SIMUTE SEQ./ Other .. [a user has] to test these.
When adding a new function, [a user has] to check that this always operates normally.
It is difficult to build without this also generating a bug.
Much time is spent on this.
I want to use time for a new function rather than I spend time on this.
JJ.


the method of old simult creates dozens of bugs in many other functions.
it slows development of the os as a whole and jj would rather move to something different (maybe something that makes simult obsolete) rather than continuously re-checking/re-fixing bugs created by the presence of old simult

consider it faulty foundations. old simult is a faulty foundation. rather than constantly build support structures to stabilize the faulty foundation, he'd rather allow a stronger foundation and move on to other things. this is simply the way it is - an issue of the code rather than wishes or capability.

as for a workaround, i've found something much much better than simult ever was.

http://ratsofnym.blogspot.com/
By dtaa pla muk Wed Feb 04, 2009 3:21 pm
haha sooty - this from the guy who wants jj to somehow add in a bunch of features from os2xl? it's not a copy and paste job.

while it works well as a function, from a developmental standpoint, something doesn't "Work fine" if it spawns a whole host of bugs in other features, requiring retesting of the same functions every time a variable is changed.

i remember you saying once that you didn't want the fancification of os2 to detract from the development of os2xl - i guess that's out the window?
By Sovereign Wed Feb 04, 2009 3:51 pm
If JJ could at least add a note linking function for editing or the ability to selectively chose pads in a GPE type way for the triggered pads, you would be able to better deal with how the pads are recorded into the sequencer.
Right now it's just too many events being generated to be useful.

Still don't get the headache of the old Simult, both Roland and Akai pull it off on 2 pretty complicated machines.
By dtaa pla muk Wed Feb 04, 2009 4:09 pm
If JJ could at least add a note linking function for editing or the ability to selectively chose pads in a GPE type way for the triggered pads


that's what we'd be more likely to see, an actual joining of 2 (preferably nonconsecutive) pads in GPE
User avatar
By Sooty_G Wed Feb 04, 2009 5:03 pm
Nym wrote:haha sooty - this from the guy who wants jj to somehow add in a bunch of features from os2xl? it's not a copy and paste job.


perhaps not for all of them, but i don't think it's nearly as complex as you make it out to be.

example: quantize strength? simult seq level in MAIN screen? those are dead easy additions.
they don't interact with any other parts of the OS, automation, sequencing, etc...


i remember you saying once that you didn't want the fancification of os2 to detract from the development of os2xl - i guess that's out the window?


i don't see how what i said contradicts that. just pointing out if you have something that already is solid, better to build on that as much as you can and take it to it's full potential before adding things that are going to destabilize it / cause the removal of functions.

os 2xl isn't going anywhere. after he fixes some of it's more critical bugs and gets it stable he can do the final additions for os 2 and get paid for it. there is plenty of time to do both. this isn't a race.
By dtaa pla muk Wed Feb 04, 2009 5:28 pm
just pointing out if you have something that already is solid, better to build on that as much as you can and take it to it's full potential before adding things that are going to destabilize it / cause the removal of functions.


that's just the point - you've heard it from the horse's mouth that old simult is a contributing factor to unstability in os2. any additional function - and that includes something as allegedly "dead easy" as quantize strength - will result in a bunch of bugs cropping up as a result. many of the bugs that we reported in os2 were due to the underlying unstable nature of os2's simult (which was different than os1's simult)

i'm not making anything out to be more complicated than it is, i'm just reporting what i'm told. if anything, my understanding of it is a simplification. you say certain things have no interaction with any other parts of the OS - that's simply not true, at all. the levels of interactivity are immense. even functions that have no end-user's logical connection may rely on the same underpinnings.
User avatar
By Sooty_G Wed Feb 04, 2009 5:43 pm
Nym wrote:t - you've heard it from the horse's mouth that old simult is a contributing factor to unstability in os2.


i took the JJ quote you posted to mean that old simult was triggering bugs in os 2xl, not os 2.

any additional function - and that includes something as allegedly "dead easy" as quantize strength - will result in a bunch of bugs cropping up as a result.

i'm not making anything out to be more complicated than it is, i'm just reporting what i'm told. if anything, my understanding of it is a simplification. you say certain things have no interaction with any other parts of the OS - that's simply not true, at all. the levels of interactivity are immense. even functions that have no end-user's logical connection may rely on the same underpinnings.


we'll see. you're doing a lot of speculating as well.

i've seen JJ contradict himself numerous times and change his mind regarding what was possible and not possible in the os. let's just wait and see.