Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By bliprock Thu Feb 09, 2012 3:16 am
I missed this feature at first. Then tried it and nearly fell off my chair. Anyone here used this feature yet for your MIDI data. It is very useful and lets you be very exact. Select an area to enter data, and then use qlnk sliders to choose upper and lower value, hit auto and it then fills the area with the data. Amazing stuff for synth control. I have to admit to making some dubstep (yeah i know, its like crap drum&bass) and was recording and editing filter sweeps. usually i just record and edit but have to slow it down to get it accurate, but not anymore as this Auto data makes it a breeze. who else here has been using it? and what do you use it for?
User avatar
By m:t:c Thu Feb 09, 2012 10:17 am
Have to start using it more extensively, but agree that in Grid edit it's really fast and fun way to write and/or fix automation.
User avatar
By bliprock Thu Feb 09, 2012 11:05 am
yeah then track to pad on top of that. Good to see someone else getting into it m:t:c. i have gone from filter automation to trying LFO timing shifts and FX on synths. But a certain synth of mine is not playing ball. Well its a bit complicated and I think i am sending to wrong LFO, as it has two LFOs. Still figuring it out. I know how to set it up, but yeah Im not sure if the patching of LFO is right. but when it does work, at least i have a few saved templates in a sequence....... And i figured it can be cut then pasted in other MIDI CC channles. nice one.
By Emilie Thu Feb 09, 2012 1:58 pm
This is a great feature. Back in JJos2 you could laso automate volue, pitch, cutoff, resonanse and stuff like that. But that is gone in JJos2XL. I hope theese features comes back in JJos3 ;-)
User avatar
By bliprock Fri Feb 10, 2012 6:08 am
yep TYPO you need your MIDI implementation chart for the gear. I have a MIDI implementation chart printed of every piece of gear on that piece of gear. That way if i think to myself, hey I wanna have pad do this on a synth or FX, I read the MIDI implementation chart thats sitting on that piece of gear.
I have been using the Auto Data to program rhythmic things, then do as you do TYPO and use them to either write more sequences and tracks or trigger live to play around. With foots witch set to overdub+play and play, it means i can just record anytime as i bang away. Good fun.
I am thinking of different SETS. BUT there are so many things, I have to start writing it down and making templates for the pads. Just so i know what I programmed a few days ago, or conflicts in CC channels. Not so much for making stuff and mucking around, but for live sets for finished stuff. 128 CC addresses multiplied by 16 MIDI channels, just just for one workstation, then different synths on top of that. See so I have to write it down. It would take me a month to map every MIDI CC. I am seriously considering it, but am progressively just adding to what I got or start from scratch for each new song. So yeah I try and make a SET and use only BANK 4 for each different synth. Thats why I would like to be able to change sets from main screen or at least name those sets, that will make it easier for me to keep a lid on it. Not really needed. So in my setup I still have some MIDI notes or even Drum mode triggering but go to BANK 4 and have synth & FX controls you made, be it pattern to pad or CC control. This way works for me as long as I read MIDI implementation chart usually but some gear can be a head ache as it has assignable CCs so you really gotta know what ya doing or you can get lost, and *ahem loose control. Yeah thats why I have now resorted to carefully considering what I want to do, then reading MIDI implementation chart, then making SET then, making template that goes over pads maybe so i could go set 7 and know its turning the FX off, or will change LFO rate. Its kinda a pandoras box of hours of programming, as you can do anything with the AutoData thing and pattern to pad, and pad to CCs.
User avatar
By arebee Fri Feb 10, 2012 12:32 pm
@bliprock....



yeah this is a fly feature. born out of the Qlink edit in JJOS2 (nonXL) and was awesome, i like the new one too for its midi features here, shame JJ couldnt bring the Qlinks into his XL OS in the same way.
User avatar
By bliprock Fri Feb 10, 2012 2:16 pm
yeah i use CCs to MPC and it responds to 74 & 71, and that is the filter resonance one so thats good instead as long as you have external controller. Thats not in the MPC multi-timbral mode either or slaved. just normal mode