Missing F#2 MIDI note after a Metagrid install
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Missing F#2 MIDI note after a Metagrid install
Hey folks, here's a weird one. I've recently noticed a dead note on my M-Audio Keystation Pro 88 in my studio, the F# below middle C. No sounds being triggered, no MIDI recorded when I play that note. The keyboard is almost 10 years old, so not unexpected that there could be some issues in there. I did the usual things to try and troubleshoot, power cycling, restoring factory defaults, etc., the problem remains.
Now tonight, I'm at home, on a different computer, and using a different M-Audio keyboard...and there's the same problem, on the same note. If I transpose the keyboard up an octave, the missing F# also travels up the octave, and the original physical key plays the octave down. I close DP and open up Kontakt, and all notes are where they should be.
Now the only significant thing I've done lately is install Metagrid (which is awesome, btw), and imported their DP-specific command bindings.
...and this is where my cry for help turns into a solution for, because I figured it out as I was typing this. I looked in the Commands menu, and sure enough, way down the list, F#2 was listed as a MIDI event trigger for the current chunk. I deleted that assignment and everything's fine.
So there you have it. Hopefully that's of use if anyone else has a similar situation.
Now tonight, I'm at home, on a different computer, and using a different M-Audio keyboard...and there's the same problem, on the same note. If I transpose the keyboard up an octave, the missing F# also travels up the octave, and the original physical key plays the octave down. I close DP and open up Kontakt, and all notes are where they should be.
Now the only significant thing I've done lately is install Metagrid (which is awesome, btw), and imported their DP-specific command bindings.
...and this is where my cry for help turns into a solution for, because I figured it out as I was typing this. I looked in the Commands menu, and sure enough, way down the list, F#2 was listed as a MIDI event trigger for the current chunk. I deleted that assignment and everything's fine.
So there you have it. Hopefully that's of use if anyone else has a similar situation.
2019 MacPro, 10.15.5, 16 core 3.2 GHz, 384 GB RAM
DP 10.11
Kontakt 6.2.2, Spectrasonics, u-he, Arturia, NI Komplete 11, VE Pro
UAD, Waves, Soundtoys, Slate, FabFilter
DP 10.11
Kontakt 6.2.2, Spectrasonics, u-he, Arturia, NI Komplete 11, VE Pro
UAD, Waves, Soundtoys, Slate, FabFilter
Re: Missing F#2 MIDI note after a Metagrid install
A bad DP joke:
viewtopic.php?f=1&t=61814&p=525891&hili ... rs#p525891
viewtopic.php?f=1&t=61814&p=525891&hili ... rs#p525891
828x MacOS 14.7.6 M1 Studio Max 1TB 64G DP11.34
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Missing F#2 MIDI note after a Metagrid install
Why is is always F#2? Is that F/U in MOTUspeak? 

2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
Re: Missing F#2 MIDI note after a Metagrid install
I didn't even think to search that specifically. I'm just glad that it got figured out before I bought a new controller keyboard.
2019 MacPro, 10.15.5, 16 core 3.2 GHz, 384 GB RAM
DP 10.11
Kontakt 6.2.2, Spectrasonics, u-he, Arturia, NI Komplete 11, VE Pro
UAD, Waves, Soundtoys, Slate, FabFilter
DP 10.11
Kontakt 6.2.2, Spectrasonics, u-he, Arturia, NI Komplete 11, VE Pro
UAD, Waves, Soundtoys, Slate, FabFilter
Re: Missing F#2 MIDI note after a Metagrid install
I always thought of it as G♭.MIDI Life Crisis wrote:Why is is always F#2? Is that F/U in MOTUspeak?
828x MacOS 14.7.6 M1 Studio Max 1TB 64G DP11.34
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Missing F#2 MIDI note after a Metagrid install
Ha! I thought of it as the bottom of the three black keys. In reality, I don't think of note names much. I started out as a drummer.cuttime wrote:I always thought of it as G♭.MIDI Life Crisis wrote:Why is is always F#2? Is that F/U in MOTUspeak?
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
- stubbsonic
- Posts: 5166
- Joined: Fri Dec 22, 2006 12:56 pm
- Primary DAW OS: MacOS
- Contact:
Re: Missing F#2 MIDI note after a Metagrid install
I think the reason why this hasn't tripped me up is that I had some early (and formative) experiences where a MIDI controller note wouldn't play, but something else on the screen would happen (like cycle-record turned on, or something else) that I just learned that COMMANDS could not only involve MIDI keys, but that some keys could turn other command sets on.
M1 MBP; OS 15.3, FF800, DP 11.33, PC3K7, K2661, iPad6, Godin XTSA (w/ SY-1000), 2 Ibanez 5-string basses (1 fretted, 1 fretless), FX galore
http://www.jonstubbsmusic.com
http://www.jonstubbsmusic.com
- HCMarkus
- Posts: 10404
- Joined: Tue Jan 10, 2006 9:01 am
- Primary DAW OS: MacOS
- Location: Rancho Bohemia, California
- Contact:
Re: Missing F#2 MIDI note after a Metagrid install
MIDI Life Crisis wrote:Why is is always F#2? Is that F/U in MOTUspeak?
