XL 1.44

genius.... thanks!!!!!

maanu wrote:Question: why is everyone referring to it as version 1.44 when it clearly says 1.43 ?

It's 1.44 version for the 2500 and 1.43 for the 1000.

Juggling between Track mute and Pad mute is really cool thanks to that active track button. Hope JJ will manage to make them recordable one day.

le rat wrote:When using MULTI in the pad move event to other track function you have to manually assign the program in the new tracks. Pretty time consuming.

seems a bit of a rush job unfortunately. the 'multi' option seems to suggest pads A1-D16 move to Tracks 1-64. What happens if you already have a load of tracks created?? And who actually has a program containing 64 hits that all get used? Better would be if you want to explode a track, JJOS looks at the individual pads actually used in the track itself, and only moves them to the next available unused tracks, renaming them and assigning the program as it goes.

I hope this isn't going to be like the arpeggiator. Give us a half-baked idea that could be a lot better

Yeah you're right.

Plus I think that pad event stuff goes against the efficient use of the MPC philosophy (which is one track = one program for me)

It would be better if PAD mutes were recordable and pad event moves were just used in special cases.

PEace

Some damn good additions here! Some of these have been requested for a long time... It would be grat if pad mutes were recorded, but with the explode it should be easy to work around. Great for Loop Edit option. Automatic program assignment would really come in handy though. Great job JJ!

Damn... and here I am still hanging on XL 1.40. Looks like I need to read up on the rest of the updates. Just glad that JJOS is still alive and coding

Hello,

I have some news and JJ is working on a way in order to take in consideration the PAD release
in order that PAD release can also send MIDI CC.

With that feature , it would be possible to use a PAD as a MOMENTARY button.

alamin

Anyone having the same problem as me with this new version (for MPC1000)?

My scroll wheel now takes 4 turns to do what should be just 1 turn. So if I'm trying to scroll through sequences, or samples, or whatever, I need to turn it 4 clicks to move just one place.

some where in MODE+ OTHER theres is an option to set the modwheel to act in 2 different ways,.

Balls wrote:some where in MODE+ OTHER theres is an option to set the modwheel to act in 2 different ways,.

Wow, never even spotted that before, that fixed it though. Don't know why it went to type 2, or who would want it working that way, but sorted now. Cheers.

dont know why i typed "modwheel" i meant ofcourse "jog wheel" option 1 and 2 is because of difference in hardware. For some, type 2 is normal behavior.

As alluded to, there are two different types of job wheels (geeze, now you've got me typing mod wheels that the MPC is shipped with. I forget when Akai switched over, but I think it was around the black -N's came out with the pad upgrade built in.

Anyway, JJOS2XL apparently cannot determine which type you have during boot up, so you have to specify in the options which you have to get it to work properly.

Sooty_G wrote:btw: i agree with this:

KNOB will send MIDI CC with value you set (as knobs do) thats how it work now.
BUTTON will send value 127 and after you press it again it will send value 0 (toggle button on/off)
MOMENTARY BTN will send value 127 and then value 0 after that within one keypress (simulates momentary button)

maybe better names for the modes would be STATIC, TOGGLE, and MOMENTARY or PUSH.

+1

and how about sending Program Change and SysEx-Messages by hitting a pad?

+1

and how about sending Program Change ...... by hitting a pad?

yeah id like that, id hope it to work on internal programs though. itd be really good for live work to switch between pgms by hitting a pad (the current methods are a bit clunky) so you could record something and switch to an alternative pgm - with different settings (e.g. q links, certain combos of pads silenced etc)