Hi folks. I discovered this quirk a month ago when I loaded Logic 8 again, this time on a new quad-core Mac tower, running OS 10.5.6. I use an M-Audio Firewire 410 interface, along with a Korg Triton Extreme keyboard. When I create and record on an instrument or midi track, all the regulars show up in the extended region parameters list (quantize, loop, transposition, etc.), but several are missing the drop-down menus that should be beside them. The ones affected are Velocity and all the "Q-" functions; no little double arrows for any of these (Quantize itself still works). Besides having a new tower, I'm also taking a Pro Tools class for the next few months, so I have an MBox Pro 2 with PT 7.4 LE on this system. Think that could be causing a conflict?

Continued.... Okay, now for the first time, a folder has appeared in my dock (Logic is currently running as described in the previous note). The folder is called CoreMIDIserver.framework, and nothing happens when I select it. Any thoughts?

Hi Sammy, I know that some Digi hardware drivers have been known to be a little odd at times with Logic & that Digidesign have traditionally been slow to support the latest versions of OS X, but this bug surprises me. You say that the selection bars are not there in the Extended parameters section... 1. Is this when you have MIDI thru selected on a SI track or a particular MIDI region selected? 2. Maybe it's a graphical error in Logic. What happens if you change to a different screenset & back again? 3. Does this behaviour happen in new projects too? 4. Are you sure you have selected Extended region parameters? 5. Have you tried selecting built-in audio as your interface? 6. Is PT 7.4.2 LE officially compatible with OS X 10.5.6? [url]http://www.digidesign.com/index.cfm?langid=51&navid=54&itemid=23639[/url] From the page above it seems that PT8.0 is compatible with 10.5.6 but that 7.4.2 is "not tested" on 10.5.6! Best Rounik

1. Is this when you have MIDI thru selected on a SI track or a particular MIDI region selected? [i]Seems to happen in either instance.[/i] 2. Maybe it's a graphical error in Logic. What happens if you change to a different screenset & back again? [i]No change.[/i] 3. Does this behaviour happen in new projects too? [i]Yes, new or old.[/i] 4. Are you sure you have selected Extended region parameters? [i]Yes.[/i] 5. Have you tried selecting built-in audio as your interface? [i]In Audio MIDI Setup or System Prefs?[/i] 6. Is PT 7.4.2 LE officially compatible with OS X 10.5.6? [i]I'll have to unplug the MBox and see if that makes a difference. I'll try a Digi forum too.[/i]

More than just disconnecting the Mbox, try deleting the Mbox drivers of your system... Cheers Rounik

Thanks for your ideas. I may wait until this PT course is over in two months, as it's a process to get the disk from school admin again (we're only meant to have it loaded on the provided loaner MacBooks, but I can't stand working on something so small). So far, this is the only glitch I've discovered, so hopefully I won't find any more problems. I can still do most things, but some of my MIDI work will have to be done manually for a while. And who knows, it may be something unrelated to PT, and perhaps I simply need to reload Logic...

[quote:30232]and perhaps I simply need to reload Logic...[/quote] Very true - could be completely unrelated to PT :) Are you running the latest version of Logic (8.0.2)? Cheers Rounik

Yeah, it's that version. This odd folder that appears in the dock has me scratching my head still... "coreMIDIserver.framework". I did a search and came up with nothing (my prefs are even set up to search the system). It now appears whenever Logic or PT are open, but never did before. My inner Sherlock Holmes suspects that it's a clue....

Good news! And in two parts... a. I discovered that by double clicking in the column immediately next to the Q- functions, an otherwise invisible window shows up, highlighted in blue. These windows have the numerical values of each function, and I can just drag up or down, or select the default number and type in a new one. As soon as a value is assigned, it becomes invisible again, but at least it's working. 2. I searched online and found references to the .framework thing I was seeing, and the advice was to go into Midi Drivers and delete all, then reload only the relevant ones, which I did. Got rid of that folder. However, on a minor note of defeat, I may be forced to use the laptop for Pro Tools, if I want each app to work properly... Oh well... Thanks for your help on this one.

Hi Sammydave, Thank You for sharing the Solutions/Answers... Cheers, Bj