Stuck D2 MIDI Note Happens Only In Logic

Question

Level 1

0 points

Stuck D2 MIDI Note Happens Only In Logic

I have a very strange problem happening that I can't seem to figure out. When I am in Logic and hit the D2 note on my M-Audio Ozone keyboard, no "note off" message is sent when I lift off the key. My keyboard is only two octaves so it has "octave up" and "octave down" keys. Even switching octaves, it is only the D2 note that is affected, not the physical key.

I have tried duplicating the problem in Garageband and in Mainstage, but everything works as expected in those two apps. I have also tried using the Caps Lock keyboard in Logic, but that works fine.

I tried looking in my Environment for anything strange, but I don't see duplicate devices or a midi filter that would prevent the D2 note off message.

I tried restarting both the MacBook and the interface. I also did a factory reset on the M-Audio Ozone. I'm at a loss on what to try next.

Crib notes:

- no "note off" message on D2 note only, and only from M-Audio Ozone, and only in Logic
- M-Audio Ozone works perfectly in Garageband and Mainstage
- Caps Lock keyboard D2 note works correctly in Logic

Message was edited by: DigitalRelay

MacBook 2Ghz Core 2 Duo, Mac OS X (10.5.5), M-Audio Ozone

Posted on Nov 16, 2008 6:44 AM

Reply

Answer 1

Nov 16, 2008 7:09 AM in response to DigitalRelay

You've probably undeliberately assigned a function in Logic to that D2 key so check your Controller/Keycommand menue.

Reply

Answer 2

Eriksimon

Level 6

15,428 points

Nov 16, 2008 7:23 AM in response to DigitalRelay

Hi,

Somehow your D2 note off message probably has become an +assigned message+ to one of Logics' commands. I just did that to test it, and it works: you can assign a note off to a command (Logic Pro>Preferences>Key Commands window, 'learn new assignment'). This message is consequently not sent on to it's intended Instrument, so D2 always hangs...
In the Key Commands window you must either track down which command the D2 note off is assigned to and select and delete the MIDI message from the assignments window, or you can initialize your key commands. Copied from the LP8UM:
*+Initializing Key Assignments+*
+You can reset all key commands to their default assignments. You will lose your existing+
+key command assignments, so ensure that you have created a copy of your key+
+commands file before doing so.+
+To initialize all key command assignments:+
+Choose Options > Initialize all Key Commands in the Key Commands window.+

regards, Erik.

Reply

Answer 3

Nov 16, 2008 9:25 AM in response to Sampleconstruct

Hello, a long time ago i posted something about trying to get L8 working on mac g4, and you tried your best to help me!
since then i have upgraded so much.
im using the new imac with Lepoard and logic pro 8 and i have various controlers, keyboard etc....
but i've got a really big problem
no one seems to have an answer!

this even happens when my control surface (bcf2000) is unplugged
bassicaly which ever track i'm on - on logic...when ever it decides to
the volume fader Jumps, so say i'm on -0.9 it will just decide to jump to +1.0 then back down again (even if im recording automation or just not playing the project) there's no automation on the track its nothing like that, sometimes this problem will happen lots!! then not as much other times
it only does it to the track i'm on
nothing is being moved no faders or nothings being sent (midi messages)
i think its the fader on logic its self because it does this with nothing plugged in atall !! (keyboard,controlers etc) its really driving me crazy, i cant do anything about it.

if anyone could help me please do ....thanks so much
James

Reply

Answer 4

DigitalRelay Author

Level 1

0 points

Nov 16, 2008 2:28 PM in response to Eriksimon

Thank you both for your suggestions. I tried as Erik suggested and initialized Key Assignments. Unfortunately, the problem persists. I also initialized all preferences from the menu, which did not fix the problem either. I have an old partition with L7 that I'm going to try, but I am really stumped. Thanks again for your suggestions.

Reply

Answer 5

DigitalRelay Author

Level 1

0 points

Nov 16, 2008 6:13 PM in response to Eriksimon

Update:

I did not have L7, but I do have a Tiger partition which I used to do a fresh instal of L8. D2 works fine. I went back to Leopard and tried reinstalling L8 and using the backup of L8 (8.0.1) that was created on the last update. All three versions of Logic Pro 8 exhibit the same weird behavior with D2. I also trashed preferences from within the app and manually deleting the file. I also tried using a Time Machine copy of the preference file from a week ago. I also paged through all the key commands (after re-initializing for the 10th time) with no affect. M-Audio Ozone driver has also been uninstalled and reinstalled. I'm running out of ideas and I really don't want to wipe the drive and start fresh.

Update: PROBLEM SOLVED!!!

After looking more closely for preference files, I found Home/Library/Preferences/com.apple.logic.pro.cs

I'm not sure what it is responsible for, but pulling it out of that folder, launching Logic and letting a new file be created fixed the problem.

Message was edited by: DigitalRelay

Reply

Answer 6

Eriksimon

Level 6

15,428 points

Nov 17, 2008 2:06 AM in response to DigitalRelay

The .cs file actually contains settings for control surfaces, so you had indeed assigned the D2 to a controller function somehow.
Anyway, glad you got it sorted.

regards, Erik.

Reply