In the dialogue that opens, click bus A, the channel one (for example) downarrow, then select Kong In (not Kong Mixer In)Īll of this is easier than it sounds. Go to the Hardware interface (at the top of the rack), click advanced midi. In Reason 7,go to preferences/synch, and set Bus A = Midipipe Output 1ġ0.
#MIDIPIPE MAC DOWNLOAD#
Or, just download the following link and open it in midipipe (will only be 'up' for a month or so):Ĩ. Key mapper (you will have to have 16 of these): change C 1 to C3, C#1 to C#2, and so forth until you have accounted for all the pads. Message Filter should be set to filter out all channel messages except Note Off/onĥ. (if you need more info, read the midi pipe website at Subtlesoft)Ĥ. Create the pipe with the following specs. I want to use the reason 5 sequence but the maschine mikro as a controller, and I also want to be able to use the maschine mikro sounds in reason.Ģ. I got my Maschine mikro almost 2 years ago and have been trying to figure this out on and off since. If anyone can give any advance or help it is greatly appreciated. I also tried going to "advanced" and setting the "External Control" "Bus A" to Maschine Mikro MK2 Input" and "MIDI Clock Sync" to Maschine Mikro MK2 Input as well. I set up the maschine in reason as "other" under "Keyboards and Control Surfaces" and when I open kong I can see the red light indicating "note on" but cannot get any sound out of kong using maschine.
I am aware that there is other threads on this same issue, and I have tried everything they have said many times, as well as the youtube videos. All i'm trying to do is use the maschine as midi controller for kong in reason, and I was also wondering how i can use the maschine sound library in reason. With MidiPipe you can use the Key Mapper plugin to make a single controller send on multiple channels, so this may not be necessary depending on what you need.I am using reason 5, OS X 10.9, and a maschine mikro mk2. This will open a new instance of MidiPipe where you can plug into it as many Midi Controllers as you want. Quick tip: you can open up Terminal and you can execute this command > open -n /Applications/MidiPipe.app
Pretty much when all else fails with my Midi Controller to DAW scenario I just hook up the MidiPipe and "force" the issue in a way. Then you can watch the A List to see what happens. You can then put a Key Mapper plugin above the A List and choose for all the notes to be mapped to a specific channel or a certain group of notes to be mapped to a specific channel. Now put the A List plugin in between the Midi In and Midi Out and click it and watch what messages you are sending. Set the Midi In to be one of the recognized Midi devices and set the Midi Out to be one of the MidiPipe Output # (1-8) for one of your controllers.
#MIDIPIPE MAC FULL#
This program basically unlocks your Midi Controller and allows you to have full control over what messages you send.Īt the very least, it will show you what Midi Messages you are sending through the A List plugin.įor a quick tutorial, just put a Midi In at top and a Midi Out at bottom. I can't link it because the forum censors it but a quick google search will show the site. I've had similar issues at times messing with VSTs and this program: MidiPipe by Subtlesoft (Mac only) solves everything for me.
#MIDIPIPE MAC PRO#
I have only ever “plugged and played” with MIDI in the simplest terms so I am probably just lacking understanding with multi-channel use.ĭoes anyone have any suggestions? Any help would be appreciated.įYI I'm using a 2015 Macbook Pro with a Focusrite Clarett 8Pre - attempting to control VST Synths in Logic Pro X. It seems like something is filtering / channeling data in a strange way. Even when all MIDI channels are set to “OFF” - the monitor still shows a stream of Ch1 data from track A when “Play” is pressed on the unit.Īlso, just as a test I set my Keylab 49 MKii keyboard to send on Ch2 as per the manual’s instructions and in the monitor the data keeps coming in on Ch1. My Digitakt is seemingly only able to send MIDI over Ch1 from track A.Ĭh2 data is not showing up on the monitor despite track B being set up to send on Ch2. I've done a bit of troubleshooting with a MIDI monitor both over USB and a Thunderbolt Audio/MIDI interface. I recently bought an Elektron Digitakt which is in part a sequencer designed to send parameter and note info via MIDI across 8 discrete channels (A-H).
0 kommentar(er)
