A bug in JJOS free - MIDI sync slave bug?

Hi all,

Not sure if this is old news (tried searching, did not find existing info) - I noticed quite a nasty bug in the free JJOS (latest version):

If you set MIDI sync to slave (ie. MPC accepting ext clock), and start recording a sequence without MIDI clock running into the MPC, your sequence will disappear as soon as the MPC starts receiving MIDI clock from the external source!? This is 100% reproducible and quite annoying. Guess I'll have to use the MPC as the clock source from now on - lost quite a few beats already just 'cause I didn't have the ext clock running before I started recording :p

I know not to hope for any fix for this (as JJOS free is no longer supported), just wondering if it's a known issue? That is all.

Can you post a video?Sounds like user error.Is still supported?

I could post a video, but it would take me ages to make one. Let me explain steps to reproduce the bug

* Power up the MPC with the free JJOS and load any program
* Setup MIDI sync to SLAVE, but do not start the clock on the master yet
* Start recording a sequence with the loaded program
* Once a recorded sequence is running, start the MIDI clock on the master
* Your MPC should lock onto the external MIDI clock and your sequence should immediately clear itself (ie. recorded sequence erases itself)

tsutek wrote:Your MPC should lock onto the external MIDI clock and your sequence should immediately clear itself (ie. recorded sequence erases itself)

You mean Overdub?
Yeah user error. Never ever seen some one slave and wait for clock like that. I been around a bit to. So in normal practice the master sets the tempo, and as the MPC is slaved and NOT GETTING CLOCK till later then yeah welcome to user error.

So you have to use the master not slave to start/stop/record/OVERDUB (that is the one you want i believe here)

Master sends start and stop to, so why are you starting the slaved device, that is just not how it usually workd, and kinda defeates the whole purpose of doing it in the first place Get me, if you slave it, then you the master starts/stops ect.

In fact one little thing will make it work for you I think - Use count in of a bar or what ever when slaved. Use Record + stop buttons for standby.

I just reread your post and I think you do not want overdub right? You do not say the word overdub, just explain it above, but i guess you mean overdub that erases past recordings. So read the manual and learn how to record and not overdub. your post is a bit huh? so this should clear a few things up for you.

Perhaps this would make more sense if I explained the workflow that I'm using..

I have a hybrid setup involving a DAW and hardware devices. Sometimes I start making a song with the computer off and switch it on later when I feel like I have something going on in the hardware worth recording into the DAW. BTW I usually keep everything running all the time (ie. no pressing stop at any point).

Now, I have this nice sequence going on in the MPC, triggering internal samples and MIDI synths (playing all the time). I boot up the computer and open up my DAW (MIDI clock master), copy the BPM value from the MPC into the DAW and start up the DAW transport (in loop mode) -- BOOM. My MPC sequence that was basically the whole song, is gone. Nothing to record to the DAW remains..

ATM the only way around this would seem to be to keep the MPC as the MIDI clock master at all times. However, the way I'm routing MIDI / syncing things around makes this a less than ideal solution.

BTW what do you mean about overdub? I've recorded all my sequences so far with using overdub, and never before has this caused any troubles for me.. Sequences play back, load and save just as they should.. I use overdub because I like to program my sequences little by little, jumping between playback (auditioning stuff) and recording, without ever pressing stop. I guess you could say that I hate pressing stop (so 90's )