So whats the go with 'Old Simult' ?????

love readin whut y'all gotta say bout sunmtimes........ " no homo "

So i finally get to a computer again and i see now good news!?
Well I do have to say i'm a little pissed!
Simult should work the way it all ways has the way its allways worked on mpc's.
I know that this was an addition that jj added to the 1000 & 2500 but they should have had it from the get go too.
Now that "old Simult" is unstable in os2xl we really need to look at a new way for it to be intergrated into the os while keeping its "old" style of programing.
Now on a very basic level, simlut triggers a secondary pad/note and is only triggered when you hit the master pad/note.
So why cant jj code it to work the same way? it dosent have to be the same code used from os2. we just need it to trigger from the master pad and the secondary pad/note to be changed when ever regradless if the first selected pad is recored or not.

eg.
pad 1 (master)
push record and hit the pad.
push stop. Play back recoreding and select a pad.
pad 2 (simulted) now plays aswell as pad 1.
push overdub and now pad 2 will get added to the recording.
Change simulted pad to pad 3.
play back will now play recorded pads 1 & 2 plus the simulted pad 3.
dont like the simulted pad, change it. dont like the recored pads, delete it.

All we really need is for the simulted pads/notes to be changed freely. thats it. if the pad/notes get recored you can delete the pad/notes you dont want. we just need the creative freedom back.

Hope it makes sence.
Sitting in the heat after a few beers on holidays does mess with the brain.
Lets hope somthing gets sorted soon.
Peace.

Nym wrote:t - you've heard it from the horse's mouth that old simult is a contributing factor to unstability in os2.

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

I usually layer all of my sounds in Adobe Audition but recently I have been enjoying the "simult pad" function. Although I love Adobe Audition as a wave editor, the MPC's simult pad is more inspirational to me when layering drums in the sense that I'm relying more on my first impression of what my ears tell me than becoming obsessed with what the waveform looks like. It is definitely nice having both though.

Sorry if this is a bit dim of me to ask, but I am a bit confused now as to which OS is associated with having stability issues from using simult pad. OS2, or OS2XL?

eoneel wrote:Sorry if this is a bit dim of me to ask, but I am a bit confused now as to which OS is associated with having stability issues from using simult pad. OS2, or OS2XL?

who knows. you can already see my take on it up above there in the quote.

the way murai / jj writes sometimes it can be unclear exactly what they mean. a lot of times their statements can be interpreted a couple different ways due to the language issue.

the fact remains: OS 2 has the old fully-functional simult and is (mostly) bug-free. given that fact when i saw the quote from JJ that Nym posted i took it to mean that JJ was running into problems when developing new features for OS 2XL and the cause was usually simult pad.

this theory makes even more sense when if you recall that at one time ( when 2XL was still in development ) JJ had 'SIMULT PAD' listed as one of the removed features in the new OS on his site!! folks complained and a week or 2 later it was listed as being included ( tho as we can see it ended up in a less than ideal form in the new OS )

i personally am not too concerned about this. in my ideal OS i would completely remove both SIMULT PAD and MUTE GROUPS as i never use them. simult is a polyphony-killer and mute groups gets confusing when you have a bunch of events going on at once. i'd rather just put everything on it's own track and deal with it in TRACK MUTE.

nah, it is not unclear. OLD SIMULT resulted in underlying bugs in both os2 and os2xl. i know this both from a direct quote from email and from bugs I reported in os2 revisions.

Nym wrote:nah, it is not unclear. OLD SIMULT resulted in underlying bugs in both os2 and os2xl. i know this both from a direct quote from email and from bugs I reported in os2 revisions.

so what bugs is it causing in os 2 currently ?

causED.

i usually sample internally the 2 o more pad together and assign to a new pad... nothing more....
that is my simult pad

......Ok ...so I v been one of the dudes bitching about simult from day one ...when the 2500 came out I was so pissed akai didnt add the ability to trigger 2 pads from one was pushing the machine back in time ..... I mean imagine having to hit 2 kicks with 2 fingers at 1 time at a live show.....have fun......simult is a simple function and shouldn't be hard to replicate ...and if it is that hard to replicate then who ever programed the 60,3000,2000 and xl were on the ball....kind off.... on the other hand .....I use Battery now to trigger 2 pads from 1 all I gotta do is click learn on battery and press the pad that I want to trigger the sound ....anyhow I hope this all gets figured out

savilion wrote:......Ok ...so I v been one of the dudes bitching about simult from day one ...when the 2500 came out I was so pissed akai didnt add the ability to trigger 2 pads from one was pushing the machine back in time ..... I mean imagine having to hit 2 kicks with 2 fingers at 1 time at a live show.....have fun......simult is a simple function and shouldn't be hard to replicate ...and if it is that hard to replicate then who ever programed the 60,3000,2000 and xl were on the ball....kind off.... on the other hand .....I use Battery now to trigger 2 pads from 1 all I gotta do is click learn on battery and press the pad that I want to trigger the sound ....anyhow I hope this all gets figured out

Yes it is a needed aspect for live work but you still have to remember if you add the 60+3000+2000+2000xl all together they don't do stuff no where near as complicated as what JJ OS does.
It's not that it's hard to replicate it's the interacting affect it has on other functions that's the problem.
Best way to look at SIMULT is that JJ knows what people would like, he also knows the problems of doing it the way he did in the past.
Just give it a minute and wait to see what he can work out that will give the capability without causing him the debugging headache.