nov 17 jj updates: os1,2, xl and free

----------------------------------------------
Addition: OS2XL Ver1.20 17-NOV-2009
---------------------------------------------
Since there was a product with strange behavior of a data wheel, the measure against such a product was added.
The "Data Wheel Type" field was added to OTHER (MODE+PAD10).
Please select 2, when behavior of a DATA wheel is strange.


----------------------------------------------
Addition: OS2 Ver1.25 17-NOV-2009
---------------------------------------------
Since there was a product with strange behavior of a data wheel, the measure against such a product was added.
The "Data Wheel Type" field was added to OTHER (MODE+PAD10).
Please select 2, when behavior of a DATA wheel is strange.


----------------------------------------------
Addition: OS1 Ver4.99K 17-NOV-2009
---------------------------------------------
Since there was a product with strange behavior of a data wheel, the measure against such a product was added.
The "Data Wheel Type" field was added to OTHER (MODE+PAD10).
Please select 2, when behavior of a DATA wheel is strange.


----------------------------------------------
Addition: Ver3.09 17-NOV-2009
---------------------------------------------
1. Since there was a product with strange behavior of a data wheel, the measure against such a product was added.

The "Data Wheel Type" field was added to OTHER (MODE+PAD10).
Please select 2, when behavior of a DATA wheel is strange.


2. [OTHER]

The "Pad On Level" field was added to F4 (PAD).

Please refer to "Adjustment of Pad Sensitivity" of an on-line manual.

very cryptic, just like a lot of the manual

nothing for 2500 yet - wonder if this issue doesn't apply or if its just not been posted on the site yet

Sounds like he created a setting for people with skipping data wheels?

elevated wrote:Sounds like he created a setting for people with skipping data wheels?

with this I fully agree

Jandpoint wrote:

elevated wrote:Sounds like he created a setting for people with skipping data wheels?

with this I fully agree

Lol what is your deal with that sentence?

elevated wrote:
Lol what is your deal with that sentence?

means that meant the same as you,
but my English is so bad .... sorry. but I do understand what you say.

mine started skipping after 2 or 3 years of heavy use, i got a replacement from vst...it would be interesting to know if it'd would've made a difference,

i read it more like "a few mpc's are manufactured with slightly different data wheels that can cause OS problems."

although there doesnt seem to be a comparable setting on the akai os that i know of..hmmm

pad on for the free users is a good and needed addition though.

mikolo wrote:----------------------------------------------
Addition: OS2XL Ver1.20 17-NOV-2009
---------------------------------------------
Since there was a product with strange behavior of a data wheel, the measure against such a product was added.

It's pretty hard to understand this typically unintelligible grammer. I hope this means that the skipping jog-wheel is fixed.
It can take 8 clicks to alter a value by 1 sometimes. Sooo frustrating, lol. I wasn't sure that this was a software issue. It would be amazing if it was fixed!
I gotta wait for the 2500 version to find out.

Downloaded en updated my MPC 1000 with JJOS1....but i don't see it added in the menu....even though it says 4.99K in the "Other" menu.

elevated wrote:Sounds like he created a setting for people with skipping data wheels?

No he hasn't. I've begged him to add this feature.

I've got a brand new MPC1000, and after installing JJOS every step at the datawheel increased the selected value by 4 or 5. I could select all values between the grid of the rotary encoder.

The problem remains also after installing AKAI-OS 2.12 from the AKAI website. Me and JJ thought that this was a coincidence and I've just got an broken MPC.
The unit was exchanged by the dealer, AKAI-OS was running fine. After installing JJOS again I've got the same bug and it's remains also after reinstalling AKAI-OS 2.12.

Thats why I've dismantled the MPC and spot that the data wheel pcb has a newer date code (may 2009) than the other ones (xx 2006).

It seems that AKAI has changed the hardware a bit. Meanwhile I'm sure that the delivered OS was something different than the 2.12 at AKAIs website.

That means:
If your MPC1000 was working fine with JJOS before, leave the data wheel type setting at "1".
If you've got a new MPC and the data wheel increases the values like in the video at JJ's website use type "2".

The behaviour for the new units isn't 100% perfect, sometimes the datawheel lacks one step (feels a bit like a shlightly broken encoder). This is caused because JJ did the bugfix by email reports, he couldnt reproduce the bug at his "old" hardware.
The behaviour is really ok to work with, without the fix all JJOS-Versions the MPCs were nearly unusable.

ultraII wrote:I've got a brand new MPC1000, and after installing JJOS every step at the datawheel increased the selected value by 4 or 5.

Strange. Sometimes it takes 4 or 5 steps of the data wheel to increase the selected value by 1 on my machine, but not the other way around.

ultraII wrote:I could select all values between the grid of the rotary encoder.

ultraII wrote:The problem remains also after installing AKAI-OS 2.12 from the AKAI website. Me and JJ thought that this was a coincidence and I've just got an broken MPC.
The unit was exchanged by the dealer, AKAI-OS was running fine. After installing JJOS again I've got the same bug and it's remains also after reinstalling AKAI-OS 2.12.

Thats why I've dismantled the MPC and spot that the data wheel pcb has a newer date code (may 2009) than the other ones (xx 2006).

It seems that AKAI has changed the hardware a bit. Meanwhile I'm sure that the delivered OS was something different than the 2.12 at AKAIs website.

That means:
If your MPC1000 was working fine with JJOS before, leave the data wheel type setting at "1".
If you've got a new MPC and the data wheel increases the values like in the video at JJ's website use type "2".

So, what ya meant to do if you have an old mpc 2500 that was not working fine before *(
I've had my mpc2500 for nearly 3 years. Sometimes changing a value by 1 can take several steps on the rotary knob. This only started happening around the same time as I installed JJOS1. Coincidence? I always wondered whether it was a software or hardware fault, and I still don't know.

ultraII wrote:The behaviour is really ok to work with, without the fix all JJOS-Versions the MPCs were nearly unusable.

You mean with the new (may 2009) rotary encoder that moves 4/5 values at one click of the wheel?

interesting about akai installing the data wheel differently now... at least JJ is saving the day again in that matter.

jimmie wrote:You mean with the new (may 2009) rotary encoder that moves 4/5 values at one click of the wheel?

Correct, at least with AKAI-OS 2.12 and JJOS. But it worked fine with the AKAI-OS which was installed at my box (didnt look which version it was ).

jimmie wrote:

ultraII wrote:I could select all values between the grid of the rotary encoder.

Without the fix: If you move the datawheel for 1 step the value jumps from 1 to 5 for example. If you turn slowly from one step to the next you can select all the values 1-2-3-4-5. This behaviour is nearly unusable because its hard to select the correct value and if you release the data-wheel it mostly snapped back/forward to the next "click" and your setting is lost.

jimmie wrote:So, what ya meant to do if you have an old mpc 2500 that was not working fine before *(
I've had my mpc2500 for nearly 3 years. Sometimes changing a value by 1 can take several steps on the rotary knob. This only started happening around the same time as I installed JJOS1. Coincidence? I always wondered whether it was a software or hardware fault, and I still don't know.

Because the age of the unit I would think its a coincidence. This behaviour sounds like a broken/dirty encoder, I'd try to exchange it.

ultraII wrote:Because the age of the unit I would think its a coincidence. This behaviour sounds like a broken/dirty encoder, I'd try to exchange it.

But it started happening nearly 2 years ago. Would I have to buy the actual encoder and solder it to my pcb?

ultraII wrote:It seems that AKAI has changed the hardware a bit. Meanwhile I'm sure that the delivered OS was something different than the 2.12 at AKAIs website.

Very interesting, thanks for filling us in.