By Blinky-Live-
Wed Feb 06, 2008 10:46 pm
I'd have to say for me- this is one of the most exciting JJ prospects so far
By orgo
Sun Feb 10, 2008 11:23 am
Blinky-Live- wrote:I'd have to say for me- this is one of the most exciting JJ prospects so far
+1
Only other thing that really exits me is the new t.c. mode in the mpc 5000. if jj could bring this to the 1000 i would be more then willing to pay another 30 bucks. i wonder if software seq. are going to incorporate this soon?
By dtaa pla muk
Tue Feb 12, 2008 2:53 am
> Since MIDI CC needs much time, it is due to be added after Ver1.00.
> The time which clarified is not known yet.
By wax808
Fri Feb 15, 2008 11:28 pm
I know this has already been said. But the work you guys are doing on this project is much appreciated.
Just the thought of being able to use my MicroKontrol's 8 knobs and 8 sliders to potentially control ADSR, track volume and panning, FX, etc... just drives me insane.
Just the thought of being able to use my MicroKontrol's 8 knobs and 8 sliders to potentially control ADSR, track volume and panning, FX, etc... just drives me insane.
By 1000dB
Mon Feb 18, 2008 10:06 pm
No midi learn please. It's a pain in the ass unless you can save the midi-cc-setup you've made and load it later on a different project. If you can't save/load it, you'll have to make the midi cc assignments again EVERY time you start a new project. If you have lots of unfinished projects on your mem cards and you wish to use midi controller on those project, once again, set the midi CC#s up on each project...
This is why midi implementation should be done normal way. I would let jj decide what CC# controls which parameter. If it's done this way, all you have to do is to configure your midi controller to send the specific CC# message, and your done. All your old projects also work your midi controller, once it's set up.
Imo For the most part midi implementation should also be done in OMNI mode, which means that the CC#s mpc receives, affect only the track which is currently selected, moreover the LAST PAD you've hit...
omni mode explained:
Let's assume all parameters from "program mode" had their own CC's, (volume,adsr,filter type,filter adsr.......)
You would use your mpc the regular way, you hear that some sample needs editing. You find the track the sound is on, you hit some pads until you hear your sample playing. At this point you would normally open program editor and start finding the parameters... If CC#s work in omni mode,you wouldn't have to open the program editor, but to turn some knobs instead. the CC#s would be affecting only the sample(PAD) currently selected.
This is why midi implementation should be done normal way. I would let jj decide what CC# controls which parameter. If it's done this way, all you have to do is to configure your midi controller to send the specific CC# message, and your done. All your old projects also work your midi controller, once it's set up.
Imo For the most part midi implementation should also be done in OMNI mode, which means that the CC#s mpc receives, affect only the track which is currently selected, moreover the LAST PAD you've hit...
omni mode explained:
Let's assume all parameters from "program mode" had their own CC's, (volume,adsr,filter type,filter adsr.......)
You would use your mpc the regular way, you hear that some sample needs editing. You find the track the sound is on, you hit some pads until you hear your sample playing. At this point you would normally open program editor and start finding the parameters... If CC#s work in omni mode,you wouldn't have to open the program editor, but to turn some knobs instead. the CC#s would be affecting only the sample(PAD) currently selected.
By mkl...
Mon Feb 18, 2008 10:30 pm
No midi learn please. It's a pain in the ass unless you can save the midi-cc-setup you've made and load it later on a different project. If you can't save/load it, you'll have to make the midi cc assignments again EVERY time you start a new project. If you have lots of unfinished projects on your mem cards and you wish to use midi controller on those project, once again, set the midi CC#s up on each project...
This is why midi implementation should be done normal way. I would let jj decide what CC# controls which parameter. If it's done this way, all you have to do is to configure your midi controller to send the specific CC# message, and your done. All your old projects also work your midi controller, once it's set up.
i totally agree with that!
Imo For the most part midi implementation should also be done in OMNI mode, which means that the CC#s mpc receives, affect only the track which is currently selected, moreover the LAST PAD you've hit...
omni mode explained:
Let's assume all parameters from "program mode" had their own CC's, (volume,adsr,filter type,filter adsr.......)
You would use your mpc the regular way, you hear that some sample needs editing. You find the track the sound is on, you hit some pads until you hear your sample playing. At this point you would normally open program editor and start finding the parameters... If CC#s work in omni mode,you wouldn't have to open the program editor, but to turn some knobs instead. the CC#s would be affecting only the sample(PAD) currently selected.
i personnaly need dedicated track (i need the volume of each track for the less...)
By dtaa pla muk
Mon Feb 18, 2008 10:40 pm
No midi learn please. It's a pain in the ass unless you can save the midi-cc-setup you've made and load it later on a different project. If you can't save/load it, you'll have to make the midi cc assignments again EVERY time you start a new project. If you have lots of unfinished projects on your mem cards and you wish to use midi controller on those project, once again, set the midi CC#s up on each project...
This is why midi implementation should be done normal way. I would let jj decide what CC# controls which parameter. If it's done this way, all you have to do is to configure your midi controller to send the specific CC# message, and your done. All your old projects also work your midi controller, once it's set up.
though i'm remaining neutral in my explanation of what people want to jj, i agree with this, mkl.., and muz. though it's a nice touch, i think it offers a lot of room for nastiness
By mikolo
Tue Feb 19, 2008 1:37 am
i agree that midi learn would be nice but not if it makes things too complicated.Its right that we should be able to setup your midi controller and not have to reassign things everytime, if id understood that correctly that'd be a nightmare.
Control across different tracks though is infinitely preferable to me than just control of the active track- even if its just mixer level,pan,tempo and filter cutoff that'd be amazing. Id like it so you could set a midi recieve channel for each track, if your controller sends the CC on the correct channel then the volume or filter changes on tracks only assigned to that midi channel .
some degree of user assignment would be nice,(perhaps for the controllers that are "unassigned"in the midi protocol) especially if we could assign one controller to two parameters( im thinking it'd be cool to change the tempo whilst changing through the sample layers for instance)but i guess that might be too difficult.
Control across different tracks though is infinitely preferable to me than just control of the active track- even if its just mixer level,pan,tempo and filter cutoff that'd be amazing. Id like it so you could set a midi recieve channel for each track, if your controller sends the CC on the correct channel then the volume or filter changes on tracks only assigned to that midi channel .
some degree of user assignment would be nice,(perhaps for the controllers that are "unassigned"in the midi protocol) especially if we could assign one controller to two parameters( im thinking it'd be cool to change the tempo whilst changing through the sample layers for instance)but i guess that might be too difficult.
By Sooty_G
Tue Feb 19, 2008 4:16 am
1000dB wrote:No midi learn please. It's a pain in the ass unless you can save the midi-cc-setup you've made and load it later on a different project. If you can't save/load it, you'll have to make the midi cc assignments again EVERY time you start a new project.
i think that goes without saying. the idea behind midi learn is that your midi settings would be saved with the program file. you could also make an autoload program that loads your assignments every time you turn on your mpc.
want to talk about a pain in the a$$? some of these midi controllers are incredibly difficult to configure internally. some of them even lose their configuration when you power them down. this is why i proposed the midi learn idea: move the cursor over a parameter & move your controller - DONE. doesn't get much easier than that.