Skip to main content

Replies sorted oldest to newest

Yes sorry console window. And you have to map it. nothing in compu live comes pre mapped. The reason for this being if it is pre mapped it already has buttons pre made for you but you program them. Well with compu you have to create the button then program them. This is why you have to assign your scenes and switches or whatever to the midi buttons or faders. Make sense?
to assign a scene or switch to a midi button simply shift right click the button select assign to midi to midi controller and select the trigger type.
Sincerely,
yea i know that but when i go and do that then go and select which fader or button i want it to be assigned to it says the midi command hasent been assigned in the console window. it has no midi data assigned to the buttons unlike all the other profiles. am i missing a file or do i have to figure out all the midi and map out the actual midi in the console window before selecting scenes and stuff and trying to link them to the controller. it shows its hooked up but when i move faders on the apc40 they dont move on the virtual apc40 on the program
quote:
Originally posted by Roof Axis Pro:
yea i know that but when i go and do that then go and select which fader or button i want it to be assigned to it says the midi command hasent been assigned in the console window. it has no midi data assigned to the buttons unlike all the other profiles. am i missing a file or do i have to figure out all the midi and map out the actual midi in the console window before selecting scenes and stuff and trying to link them to the controller. it shows its hooked up but when i move faders on the apc40 they dont move on the virtual apc40 on the program


Roof,

So this may not be the best help but JC (wheresJC) sent me an email with some tips that I can probably forward to you. I just havent been in front of my board since he sent it to me a week ago (pathetic on my part, I know.). BUt anyway, he has had a lot of success with Akai controllers synced with Compulive. If youd like, I can send you his tips and see if they work for you, since I dont know the next time Ill be able to try it out. You can shoot me your email @ EppLeyBeN at G male dot com. The good news is that from what he tells me, this does work. So hopefully we can figure it out!
You guys make this too hard. I had my MIDI controller working in less than an hour.

It seems you've made it as far as getting the software to see the MIDI data so here's shortcut you don't need a custom MIDI map.

"This Midi Command has not yet been assigned in the Console...blah blah blah"

Open the Console Window.

Right-Click Header and choose Behringer_BCF2000_big_10presets.

Choose a page other than 1 (tabs on bottom of screen)

Right-Click a Button, Knob, or Fader in the console window. (Does not matter, they all work the same in the software)

The MIDI/Command Screen will open. If there is No Command in the Command line, then move the fader/knob/button/note you want to patch. (This will patch MIDI notes as MidiCC values so if they are not on different MIDI Channels, the Notes will be a flash value for the MIDI CC of the same number.)

Now you're patched.


A handful of MIDI CC values are patched into the big_10presets so you won't have to do this for every channel you patch.

Take advantage of creative Channel assignments. MIDI has 16 Channels of 127 CC and 127 Notes.

I have used Akai MPD32s where you can change the Channel and Note values onboard, providing another level of console patching, very useful.
Last edited by wheresjc

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×