Using a Yamaha BC3 breath controller w/M3?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Using a Yamaha BC3 breath controller w/M3?
I have a BC 3 breath controller and want to use it with the M3. What would be the best way to get this to work? Thanks for a reply in advance.
- philipgruver
- Posts: 24
- Joined: Thu May 29, 2008 7:39 pm
From reading the Midisolutions manual you would connect the BC3 to the input of the device, the M3 to the midi out of the device, and a separate keyboard controller to the midi in of the device. If I’m reading this right (which I probably am not) in order to send breath control messages to the M3 you would need to be playing the keyboard controller and not the M3’s keyboard. John Fast or someone else at Midisolutions could clear this up.
Alternately, if you have a BC3, does this mean that you already have a device that accepts the BC3 such as a VL70m or EX series tone generator? If so, the I would think the easiest path would be to connect the tone generator midi out to the M3 midi in so that any breath control would be passed as midi control changes from the tone generator to the M3.
Alternately, if you have a BC3, does this mean that you already have a device that accepts the BC3 such as a VL70m or EX series tone generator? If so, the I would think the easiest path would be to connect the tone generator midi out to the M3 midi in so that any breath control would be passed as midi control changes from the tone generator to the M3.
- BasariStudios
- Approved Merchant
- Posts: 6511
- Joined: Sun May 29, 2005 4:56 am
- Location: NYC, USA
- Contact:
Philli, the BC3A works directly on any Yamaha device or Device that has a
BreatController plug in but on most of all you need the MS box. When you
use an MS box you dont need a third device, in this example you connect
the BC3A to the MS and then to M3, thats it.
BreatController plug in but on most of all you need the MS box. When you
use an MS box you dont need a third device, in this example you connect
the BC3A to the MS and then to M3, thats it.
http://www.basaristudios.com
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
- philipgruver
- Posts: 24
- Joined: Thu May 29, 2008 7:39 pm
I emailed John Fast at Midisolutions and he has clarified that you do need to plug something into both midi in and out ports of the MS box. However, the midi input to the MS box does not need to be separate keyboard controller but instead could be M3 itself. He has allowed me to post his reponse. Here it is:
Hi Philip,
Something needs to be connected to the MIDI input of the Breath Controller in order to provide it with power, the MIDI Out or Thru of the M3 could be used for this purpose - if you don't want the MIDI messages from the M3 to be passed through the Breath Controller and back into the M3 then the Breath Controller's Echo parameter can be programmed to OFF.
Best regards,
John Fast, MIDI Solutions Inc.
www.midisolutions.com
Hi Philip,
Something needs to be connected to the MIDI input of the Breath Controller in order to provide it with power, the MIDI Out or Thru of the M3 could be used for this purpose - if you don't want the MIDI messages from the M3 to be passed through the Breath Controller and back into the M3 then the Breath Controller's Echo parameter can be programmed to OFF.
Best regards,
John Fast, MIDI Solutions Inc.
www.midisolutions.com
- philipgruver
- Posts: 24
- Joined: Thu May 29, 2008 7:39 pm
ditto
I'm curious about this, too.
philipgruver wrote:Sirgant1,
The manual for the MS box instructs the user to send sys ex messages to program the box. I was wondering if you planned to purchase the MS box and, if so, how you plan to send the sys ex messages.
M50-88, Kontact, Protools m-track 8x4, EWQLS library, 1920 Monarch upright
- BasariStudios
- Approved Merchant
- Posts: 6511
- Joined: Sun May 29, 2005 4:56 am
- Location: NYC, USA
- Contact:
I can clarify, confirm and Video demonstrate if you need, you buy the MS Box,
you buy the BC3A, i know a very cheap source for a Package where i bought
mine and all you have to do is Plug it in the M3 and turn Local Off.
You need 2 Standard MIDI cables, for IN and OUT, both have to be connected.
you buy the BC3A, i know a very cheap source for a Package where i bought
mine and all you have to do is Plug it in the M3 and turn Local Off.
You need 2 Standard MIDI cables, for IN and OUT, both have to be connected.
http://www.basaristudios.com
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Thanks, but still no dice.
Thanks for the ideas. Hooked up the MS Box/Yamaha BC3 to my Korg M50-88. Nothing. Tried unchecking "local control on" in the Midi setup. Also tried assigning CC# 2 to the footpedal. Still unsuccessful. Maybe the M50-88 has another step, or is incompatible.
---Mark
---Mark
BasariStudios wrote:I can clarify, confirm and Video demonstrate if you need, you buy the MS Box,
you buy the BC3A, i know a very cheap source for a Package where i bought
mine and all you have to do is Plug it in the M3 and turn Local Off.
You need 2 Standard MIDI cables, for IN and OUT, both have to be connected.
M50-88, Kontact, Protools m-track 8x4, EWQLS library, 1920 Monarch upright
- BasariStudios
- Approved Merchant
- Posts: 6511
- Joined: Sun May 29, 2005 4:56 am
- Location: NYC, USA
- Contact:
Why were you trying to assign CC#2 to FC? That has nothing with BC3A.
They are both just External Controllers and dont affect each other.
They are both just External Controllers and dont affect each other.
http://www.basaristudios.com
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
MS box
Have you tried every possible combination? For example -
First try it the most logical way. Connect the midi out of a different keyboard into the midi in of the MS box and then connect the midi out of the MS box into your M3 and try to see if you get sound using a controller and the M3 as a sound module. If you get a sound with that, then you can start to narrow down the problem. If you don't get a sound then there's a different problem.
If you get a sound, try all logical combinations. Create a midi loop using the midi out of the m3 into the midi in of the ms box and the midi out of the ms box into the m3's midi in and try with both local on and off on the M3. See if you get a sound with this before you start programming the ms box so it'll be easier to figure out where the problem is. Make sure to be using the BC3 all the while as well.
If this works, you can try programming the ms box then to get your desired result, although if you can get it to work by using the BC3 and a midi loop with local off so you don't get double triggered phasey sounding notes, I'd be content with that before screwing around with sys-ex programming.
Frank
First try it the most logical way. Connect the midi out of a different keyboard into the midi in of the MS box and then connect the midi out of the MS box into your M3 and try to see if you get sound using a controller and the M3 as a sound module. If you get a sound with that, then you can start to narrow down the problem. If you don't get a sound then there's a different problem.
If you get a sound, try all logical combinations. Create a midi loop using the midi out of the m3 into the midi in of the ms box and the midi out of the ms box into the m3's midi in and try with both local on and off on the M3. See if you get a sound with this before you start programming the ms box so it'll be easier to figure out where the problem is. Make sure to be using the BC3 all the while as well.
If this works, you can try programming the ms box then to get your desired result, although if you can get it to work by using the BC3 and a midi loop with local off so you don't get double triggered phasey sounding notes, I'd be content with that before screwing around with sys-ex programming.
Frank
- Rob Sherratt
- Platinum Member
- Posts: 4590
- Joined: Mon Apr 16, 2007 1:49 pm
Question: On the MidiSolutions controller box is the MIDI indicator LED lit up? Does it flash when you play the Yamaha BC?
If not, then the Korg M3 is probably supplying insufficient current over the MIDI IN port to the MS controller to power the MS box up. Try connecting MIDI IN on the MS box to a MIDI port connected to a computer. Otherwise, there is a stand alone power adapter available to correct this problem, see:
http://www.midisolutions.com/prodpwr.htm
See also Q&A about the LED here:
http://www.midisolutions.com/faqs.htm#LED
Best regards,
Rob
If not, then the Korg M3 is probably supplying insufficient current over the MIDI IN port to the MS controller to power the MS box up. Try connecting MIDI IN on the MS box to a MIDI port connected to a computer. Otherwise, there is a stand alone power adapter available to correct this problem, see:
http://www.midisolutions.com/prodpwr.htm
See also Q&A about the LED here:
http://www.midisolutions.com/faqs.htm#LED
Best regards,
Rob
in my experience, midislutions tools need to get power from their midi IN side.
I tried that with the "event programmer," which couldn't get power from a prophet08.
So, before buying a midisolutions POwer box, try this:
set M3 in "LOCAL OFF"
cable: M3 MIDI OUT ---> MIDISOLUTIONS BREATH IN ---> BREATH OUT [with merged BC message] ---> M3 MIDI IN.
If this doesn't work, try adding ANY cheap semi-vintage midi patchbay (e.g. a used nexus is far cheaper than the midisolutions power) BEFORE the midisolutions breath, not after.
powered PATCHBAY MIDI OUT ---> MIDISOLUTIONS BREATH IN --> BREATH OUT --> M3 MIDI IN.
I tried that with the "event programmer," which couldn't get power from a prophet08.
So, before buying a midisolutions POwer box, try this:
set M3 in "LOCAL OFF"
cable: M3 MIDI OUT ---> MIDISOLUTIONS BREATH IN ---> BREATH OUT [with merged BC message] ---> M3 MIDI IN.
If this doesn't work, try adding ANY cheap semi-vintage midi patchbay (e.g. a used nexus is far cheaper than the midisolutions power) BEFORE the midisolutions breath, not after.
powered PATCHBAY MIDI OUT ---> MIDISOLUTIONS BREATH IN --> BREATH OUT --> M3 MIDI IN.