[bug] LOOP turns off when you change bar length in MAIN

MPC2500 - issue with JJOSXLv3.08 and above (latest currently 3.25).

LOOP keeps turning itself off when you change the bar length.

On the MAIN page, if I turn 'Loop' on it is because I want 'Loop' on.
When I change the number of bars in my sequence, the mpc shouldn't turn 'Loop' off.

I just tested jjosxl v3.06 and it works fine. jjosxl v3.08 and above have this annoying issue. I don't have v3.07 to test.

Sadly it's a terrible limitation due to a specification change.

but can it be fixed? it's annoying me, too.

No. It has already been addressed that it can not be changed.

what about a button-mode style fix, where the cursor is moved and the value is changed as if manually?

if one were to write a macro that did this, and then jj just affixed it to the end of the add/remove bar function, it'd solve this.

bugs me, too

sciguy wrote:but can it be fixed? it's annoying me, too.

Yup, thats pretty annoying but I can live with it. I'd like to see something like a match BPM to tempo option (without time stretching). Not that I can't just tune the sample up/down but it would be more fun (and more fast) IMO...damn, even the s20 has an option like this

Regards,
Koncrete

P.S. this is my first post, so I'd like to say HELLO to all y'all

Errors like this can't be fixed without re-writing the OS from the beginning.

Which is one reason we have 128xL.

elektrik_muz wrote:Errors like this can't be fixed without re-writing the OS from the beginning.

Which is one reason we have 128xL.

I don't understand what you mean.
jjos hasn't had this issue for over 5 years.
This only started happening with jjosxl v3.07 or v3.08 and above. i.e. Nov 2011.

It probably happened because of some extra functionality that JJ added which broke this functionality.
Fair enough... JJ can't please all the people all the time... People have different priorities.
I personally see this as quite a high priority.... but that's just me.

I only waited for this long to kick up a fuss because I thought it was a given that JJ would have seen this as a priority and fixed it by now. I seem to have made an incorrect presumption.

It's just the nature of code.

Once a developer makes the decision to fork code in a paticular direction to gain new features, old features can get interfered with and it may not be possible to fix them without loosing the new features.

Assuming the hardware can handle both features and it's purely a problem of code, the only solution then is to start the whole thing over again with a software spec that incorporates both new and old features from the beginning.

Every JJos before 128xl has been based on a basic software spec that was laid out by Grande Holdings era Akai. If you understand just how far the JJ features have progressed compared to the way the clowns at G.H. originally envisioned the 1k feature set you start to appricate the fact that JJ has progressed as far as he has despite what's probably an enormous handicap.

coders have a joke, that goes like this.....
"It is just a simple case of programming!"
see its not that easy to do complex code, and JJOS is probably no different

I don't get it.. JJ has been changing more serious things in OS sometimes within hours.. for years.. now you are tellin me he can't fix that..

I can live with that.. but it's ALWAYS that extra step..