MIDI Controllers & BPM need improvement
Posted: Thu Mar 19, 2009 6:45 am
I'm hoping one of the developers of BPM reads this....
The way BPM is set-up to recieve MIDI controllers is very poor. I don't know about other users but I find it very disapointing....
Although I have a reasonable amount of controllers, I don't I want to assign the same thing for every single pad. That's just not practical. If I want to assign the decay filter for example to each sound on a pad, that's 16 controllers just for this 1 control and using only 1 bank!
Not only that, BPM can't memorise controller templates. I found this out the hardway by assigning 16 controllers only to realise that the settings only save when you save a kit. Not clever...!
Also, some settings like filter cut-off, (which is one of the main things to control hence the huge size!) need a filter to be activated 1st ie LPF etc. Great! So even if I assign a controller to cut-off, it doesn't work unless I choose a filter type (in fact it's not even possible). Basically, the controller has to be re-linked every single time I activate the filter type from an off position.
And in closing, could it be made possible to have 99% of things MIDI controller assignable? Right now it's very selective. For example I was hoping I could adjust sample start and end points using MIDI knobs and assign commands like normalize, trim & crop to MIDI controller buttons. As of yet, it's not possible and slows down workflow compared to units like the MPC.
VST instruments these days should work in complete harmony with MIDI hardware controllers as they (developers) have had long enough to adjust to the mentality. BPM is marketed as bridging the gap between software functionality & hardware features. It won't succeed until they realise that people don't want to use the mouse to control almost the entire UI interface. That's kinda why people opt for hardware in the first place...
I like BPM at the moment but that's only because I'm hoping they will fix alot of bugs I've come across aswell as include some of the functionality mentioned in this post. It's only just been released so I'm waiting to see how they respond to user feedback which so far has been pretty good.
Aplogies for the long post but it's really aimed at one of BPM's devevelopers/programmers who cruise the site from time to time.
Thnaks
40
The way BPM is set-up to recieve MIDI controllers is very poor. I don't know about other users but I find it very disapointing....
Although I have a reasonable amount of controllers, I don't I want to assign the same thing for every single pad. That's just not practical. If I want to assign the decay filter for example to each sound on a pad, that's 16 controllers just for this 1 control and using only 1 bank!
Not only that, BPM can't memorise controller templates. I found this out the hardway by assigning 16 controllers only to realise that the settings only save when you save a kit. Not clever...!
Also, some settings like filter cut-off, (which is one of the main things to control hence the huge size!) need a filter to be activated 1st ie LPF etc. Great! So even if I assign a controller to cut-off, it doesn't work unless I choose a filter type (in fact it's not even possible). Basically, the controller has to be re-linked every single time I activate the filter type from an off position.
And in closing, could it be made possible to have 99% of things MIDI controller assignable? Right now it's very selective. For example I was hoping I could adjust sample start and end points using MIDI knobs and assign commands like normalize, trim & crop to MIDI controller buttons. As of yet, it's not possible and slows down workflow compared to units like the MPC.
VST instruments these days should work in complete harmony with MIDI hardware controllers as they (developers) have had long enough to adjust to the mentality. BPM is marketed as bridging the gap between software functionality & hardware features. It won't succeed until they realise that people don't want to use the mouse to control almost the entire UI interface. That's kinda why people opt for hardware in the first place...
I like BPM at the moment but that's only because I'm hoping they will fix alot of bugs I've come across aswell as include some of the functionality mentioned in this post. It's only just been released so I'm waiting to see how they respond to user feedback which so far has been pretty good.
Aplogies for the long post but it's really aimed at one of BPM's devevelopers/programmers who cruise the site from time to time.
Thnaks
40
