I have my Triton Studio as the main keyboard and I use another keyboard, TrinityV3, as a controller.
Only one midi cable out of the Trinity into the Triton.
Occasionally, at random, the Triton receives a "note off" signal. If I'm holding a chord down on the Triton, it just shuts off, just like I've taken my hands off the keyboard.
It never happens when the midi cable is unplugged.
I've tried swapping the Trinity for my Wavestation and it still happens.
I've tried using another midi cable, still happens.
I really need to get to the bottom of this as I'll be using this setup for live gigging.
Ideas?
What is silencing every sound?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
StephenKay
- KARMA Developer<br>Approved Merchant
- Posts: 2993
- Joined: Tue Jun 18, 2002 2:16 am
- Location: Scottsdale, AZ
- Contact:
There is an "all notes off" message in the MIDI spec. It would seem perhaps that the Triton is receiving one. However, I have no idea why either of those other keyboards would be sending one. I can see that it might occur if the other keyboard was in sequencer mode...
You may need to install some MIDI Monitoring software (in a computer) to try to see when and how such a message is being sent to the Triton.
Mac: MIDI Monitor by SNoize
PC: MIDI-OX
You may need to install some MIDI Monitoring software (in a computer) to try to see when and how such a message is being sent to the Triton.
Mac: MIDI Monitor by SNoize
PC: MIDI-OX
In my experience this was down to active sensing.
Some Korg boards if you connect to a keyboard that doesn't send active sensing at all, it will periodically cut off.
This is a feature of active sensing that it kills all sounding notes if it detects that a MIDI cable has been unplugged. I'm not sure exactly what is happening there though that might cause this.
Some Korg boards if you connect to a keyboard that doesn't send active sensing at all, it will periodically cut off.
This is a feature of active sensing that it kills all sounding notes if it detects that a MIDI cable has been unplugged. I'm not sure exactly what is happening there though that might cause this.
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Thanks for the advice above. The controller keyboard (Wavestation) cannot be sending note off signal in sequencer mode, as it's a synth only, no sequencer.
I'm going to try and make my own midi cable using high quality plugs and cable, and connect only the wires required. Also, will not connect pin 2 (GND) at the "IN" end of the cable (as per midi specs) in case it's a ground loop problem.
I'm hoping the current cable may be to blame as it maybe a standard 5pin din cable and not a proper midi cable. Perhaps not wired up correctly.
I'm going to try and make my own midi cable using high quality plugs and cable, and connect only the wires required. Also, will not connect pin 2 (GND) at the "IN" end of the cable (as per midi specs) in case it's a ground loop problem.
I'm hoping the current cable may be to blame as it maybe a standard 5pin din cable and not a proper midi cable. Perhaps not wired up correctly.