4.84 is up

thanks rinseout, you in the rolodex next to hereo now,

peace

ok, here's the video of the akai OS for the mpc2500 where mute/stop actually works as it's supposed to: http://www.youtube.com/watch?v=65A29std9ik.

youtube made it really hard to see, but here's what i do...

1) i set mute/stop to imediate.
2) i let the sequence play. the sample is set to mono and gets triggered at 02.01.00. the sample DOES NOT get cut off when the sequence loops back around to 01.01.00.
3) i continuously press mute and unmute to show that the sound cuts in and out because it's the sound that's being muted, and not the note events.
4) i mute the track for two whole loops.
5) i unmute the track and the sound comes back playing in the right spot.
6) i set mute/stop to through.
7) i let the sequence play. the sample is set to mono and gets triggered at 02.01.00. the sample DOES NOT get cut off when the sequence loops back around to 01.01.00.
8) i continuously press mute and unmute to show that the sound does not cut in and out because it's not the sound that's being muted, but rather the note events.
9) i mute the track for 3 whole loops, the sample continues to play through since the note events on the track are not being triggered.
10) i unmute the track and it cuts itself off the next time the note event is triggered.. since the sample doesn't have a perfect tempo (and because i didn't loop it perfectly), the sample cuts it off but not in beat.

i'm uploading the version i recorded with the JJ OS right now, but i can tell you that the only difference is step number 2 because the sample DOES get cut off when the sequence loops back to 01.01.00.

Update!!! here's what happens with mute/stop on the JJ OS: http://www.youtube.com/watch?v=JN1-C3ZOnyk .

I did everything the same, the only difference is like i said, number 2. the sample gets cut off at the end of the sequence before it loops back to 01.01.00.

Thank you Mike. That pretty much clarifies what's happening.

thanks mike! i hope this helps now:

1. record the sample again, play it on every 8th (on the 1000).
2. then mute the track.
3. now push the same pad
-> i gets cut off by the muted sample. and that's all i'm complaining about. a muted track should not send any information!

because if you're unsure about how you played a sample, you mute the track and think of a better way to play it. but here you can't play the sample anymore, unless you delete the track.

well done, guys, i finally understand the problem.

to me it looks like a programming dilemna.

you either get the audio muted, or the note informations muted.

if the audio is muted then the sample will not be cut at the end of the sequence, but for that the note events still need to be remembered/processed, hence the muted tracks in mono or mute groups will affect other tracks (which i agree sucks)

or the note information gets muted, then everything works fine but then long samples gets cut off at the end of the sequence (because the note info has been muted).

maybe the only way would be to have 2 IMMEDIATE settings, as having both looks like impossible.

personaly i will stick with THROUGH, which is the behaviour i expect from a sampling drum machine.

there is a bug i am a bit worried not to see being addressed (reported 2 months ago).

1: select a track with different pads recorded. some at the same time.
2: mode + [grid]
3: "6 pad" view
4: press [REC].
5: press [STOP].
6: hold [shift] + press [bar >] or [bar <] several times to go to the next or previous recorded events.
bug: behaviour is strange. sometimes go to next event (ok), but sometime jump events. sometimes stay to current event.
(but no bug if choose "16 pads" view)

JJ told me at some point that he was looking into it. But still no fix coming.
anybody fancy to report it also ?
cheers

ya you should upgrade. It will be pretty transparent to you. You did a smart thing in getting the jj os right away. Wish I woulda done that :/

Edit: oops wanted to quote