[Bug]: Changing number of bars turns Sequence Loop Off

1. Turn on MPC 2500XL (OS128XL Ver 1.02)
2. Turn Sequence Loop ON
3. Change Bars to 4; Press F5[Do It]; notice Loop is now OFF
4. Turn Sequence Loop ON
5. Chang Bars to 8; Press F5[Do It]; notice Loop is OFF again

Expected - When Loop is turned ON, it should remain on until user turns it OFF. Changing the # of bars should not impact Loop param.

+1 this drives me NUTS and I keep forgetting to post it.
(edit: that is, this applies to MPC1k as well)

this is something i wrote to murai about, apparently this behavior is done to protect the system against a bug that would occur if the loop settings were left untouched.

the current specification is not ideal, for sure.

Yeah....no other MPC performs this way. And loop should be On by default IMO.

I can't check now but I think it was working fine with the old system (start looping bar - numbers of looping bars). I don't remember why he changed this by the way.

Do you have the F1 key customize option in os128XL?

I am also very angry about this feature! EVERY time I turn on the MPC I have to turn on Loop again and again. For every damn sequence. And as JAH wrote, it has to be turned on again after changing the number of bars. This is so annoying!

Dear JJ, it would be so great if you could change that behaviour as JAH proposed: Loop should be on by default (let's face it, it is a LOOP machine!) and should stay on even if changing bars. There is no reason to turn it off!

this is something i wrote to murai about, apparently this behavior is done to protect the system against a bug that would occur if the loop settings were left untouched.

Actually there is a simple way to solve this: In the background it can be automatically turned off and directly on again within milliseconds to avoid a potential bug! The user even won't realise it!

jakoby84 wrote:There is no reason to turn it off!

There can be.
A simple way to solve your problem is to save template project with every sequence looped, and then make that autoload. simple. Every time that you turn it on it will have every blank sequence looped, at whatever length, ready to go. God knows I would not bother myself like, each to their own of course. So it can be done easily enough. In some cases when I am recording MIDI data, it is very important that loop is OFF so that it does not loop back and overwrites the MIDI data I wrote beforehand. That is one reason so you understand that there are reasons to have the loop off. Just saying so you know, even though you might not do this your self. And because the loop on/off option is right next to the bar length, it is no big deal to me. As work flow wise its ok being next to each other. If it was on the other side of the screen or another window, I would be a bit annoyed, but as I said, as they are next to each other and it is quick, I feel it is fine. no big deal and quick to. And jakoby if that makes you really mad, then maybe you need to chill out a bit there. Use the autoload feature and you will not have a reason to be angry.

There are a number of work-arounds for many bugs. But that is not the point in a bug thread.

I think that is why SHIFT F1 LOOP on/off was added.