sayr777

Velvet, you're not too late! I echo Velvet's sentiment in his #3 question. Actually, it would fall under the category of my first question about them fixing (fully implementing) Plugin Delay Compensation. The I/O Plugin should automatically compensate for any PDC playback latency and add that (number of samples) to soundcard latency so audio will be in time. You shouldn't have to pull up a 3rd party plugin (Expert Sleepers Latency Fixer) to make the I/O Helper work. Also, somehow they spaced out on making their own Pitch Shifter II plugin work with PDC. Not that you're going to wanna nit-pick on him tonight, but the point is they rushed it out the door and seemingly forgot to go back and finish it.

Hi David... got the link to this thread from your post at Sonikmatter. 1. I really, *really*, REALLY want to know if they're going to fix the Plugin Delay Compensation (PDC) issues once in for all in the next point release (7.1.2)! It's driving so many people crazy to have their outgoing audio compensated for latency-causing plugs, but incoming audio (recordings) are not compensated for and outgoing MIDI (to external hardware) is not compensated for. What you end up with is a bloody mess. Nothing is synchronized... and that reminds me... syncing with other devices and sequencers isn't really working with PDC because Logic isn't compensating its sync with PDC. They just made PDC work with outgoing audio. In 7.1.1 what I'm told is that they fixed the QT movie track (finally) so it aligns with PDC. My question is when are they going to fully implement PDC so it works right. David, I'm sure you already know about this, but if you want the lowdown (from the "horse's mouth"), read this article: http://docs.info.apple.com/article.html?artnum=301025 2. Grid-snapping for automation??? Wondering if/when they plan on making automation breakpoints able to snap (Smart Snap?) to the grid. I'm going to try and make it down tomorrow night, but I fly out early Sunday morn... might not happen. If you can, ask him these two questions. Question #1 will be speaking for MANY people though! It's a huge concern for so many people right now and it's REALLY hard to use Logic with PDC how it is right now. Hope it's a great and informative evening for you!! Will try to make it

I'm not in front of Logic to try this, but isn't there some form of Copy/Paste, Load/Save or Import/Export functionality within the Controller Assignments??? If so, you could have two songs open and perhaps open the Controller Assignments window for both songs and get 'em across somehow. I seem to remember that you can do something to get Controller Assignments into another song... I may just be mistaken. Will try later.

Hey silvercity-bob, I figured out what was causing my problem, but I don't know if yours is the same problem... sounds like it though. FIrst thing you should do is run "MIDI Monitor" before launching Logic. You can download it for free here: http://www.snoize.com/MIDIMonitor/ So start that up before Logic and it then do the Learn Controller Assignment thing in the Control Surfaces setup window (Expert mode would be fine). MIDI Monitor will filter out the excess MIDI data that Logic is receiving from your MIDI Controller's knobs & sliders. That excess MIDI Data is what prevents the learn from sticking. If you look in the "Value Change" box (In Expert mode of Controller Assignments setup) to see what input is coming from your knobs while it is Learning. It should look something like this: "B0 12 Lo7". It should not look like this "B0 12 Lo7 FF 00 00" or "B0 12 Lo7 FF 4A Hi7" or anything LONGER than the first one in quotations above. Although, I've seen that with MIDI Monitor running in the background, it never learns a longer string of characters than this "B0 4A Lo7" and that is all you want. If that doesn't help, then you are having a different problem to what I had. -Craig

Oops, above I meant to say: Sometimes turning off Learn Mode would remove the un-needed info, leaving just the proper info and other times, turning OFF Learn Mode would remove the proper info and leave the extra (FF 00 00 or FF 00 Hi7) un-needed info.

No worries! Well, MIDI Monitor not only told me what was being transmitted from my controllers, but it also trimmed off a bit of extra info (probably SysEx) that was confusing Logic's MIDI Learn function. The weird thing is that, without MIDI Monitor, both my Nord Lead and the Ozonic were sending this extra info that would appear after the basic CC info in the "Value Change" window, (example: "B0 11 Lo7 FF 00 00" instead of just "B0 11 Lo7" which is what Logic is expecting) and this extra info would prevent the parameter from being mapped to the knob or slider. Also, if I kept twisting the knob (being learned) even after it has been learned, it would add to the "Value Change" window's info - as long as "Learn Mode" was still enabled. Sometimes turning off Learn Mode would remove the un-needed info, leaving just the proper info and other times, turning OFF Learn Mode would remove the proper info and leave the extra (FF 00 00 or FF 00 Hi7) and remove the un-needed info. As soon as I launch MIDI Monitor, it is perfect every time. All of my controllers transmit just the proper info ("B0 4A Lo7" etc...) and it learns just fine. I've contemplated marking all of my controllers' knobs and sliders w/ labels that would tell me what the (decimal) CC# (and B0 ... Lo7#) is for that CC, but I think I'll just always launch MIDI Monitor while learning Controller Assignments. Now I just need to figure out what the "Zones" and "Modes" are used for. The manual has provided little help in describing common usages for these hierarchical controller setups. I understand the structure of it, but not why or how you should use the Zones and Modes instead of having all of your assignments in one BIG list that is Mode-less and Zone-less. And as for fixing the problem of the Ozonic and Nord transmitting extemporaneous CC info, I just have the work-around of using MIDI Monitor as the translater, but I haven't figured out where I can change a setting and make it filter out the extra info from within Logic. Just so you know, I've thoroughly tried everything I can find in Logic. 1. Turning on SysEx filtering, in Song Settings 2. Turning off SysEx in the MIDI-Chase Song Settings. 3. Switching around these Control Surfaces Prefs: A. Set "Multiple Controls Per Parameter" to "1" instead of "2", because it says "For longer labels and value displays". B. Unchecked "Only when all parameters fit on one page" Without MIDI Monitor running, I tried learning from Ozonic and Nord Lead and no matter which way any of these settings are set, it always does pretty much the same thing. Double, triple and quadruple length CC info adding more and more to the "Value Change" window as I twist the knob more. Gotta run MIDI Monitor all the time I guess.

Problem solved. Well sort of... I know how to work around it now and if anyone cares to know how. I guess you'll post a reply and I'll save myself going into details until then.

Yeah, I figured out I needed to click on the link you provided in your first message. That was right after I posted this last defeated message above. I just forgot to mention here that I started a new topic where you linked to. Ooops.

You can change the background in the Arrange in the Preferences under "Display". Then select the "Arrange" pane. You used to have more options in Logic 6... but now you can choose fancy colors. Whooohooo!!! Kidding, I leave mine grey.

I have been able to get my M-Audio Oxygen8 and Evolution UC-33 (MIDI knob & slider box) to work pretty well with Logic's MIDI Learn (in Controller Assignments). But, I am unable to get my M-Audio Ozonic to work with Logic's MIDI Learn. The same problem happens on my Nord Lead which is connected to my G5 via the MOTU Fastlane USB MIDI Interface. The same problem also happens with Logic's Automation Quick Access. Either in the Controller Assignments window or in Automation Quick access, when I activate MIDI Learn and move a knob on the Ozonic or Nord Lead, it appears to be Learning (it sees the knob and shows the CC # properly). Then it just doesn't work. When I MIDI Learn in Reaktor, it works immediately, everytime from both the Ozonic and the Nord. Same with Reason. When I Edit "Remote Override Mapping", it works perfect. That's how I know the Ozonic and Nord are in the proper mode and working as they should. Also, I know Logic is seeing the Ozonic and Nord Lead's CC knobs because the Ozonic's 1st knob and last slider automatically control the selected track's Pan & Volume (respectively). The Nord's Amp Gain also controls the selected track's Volume. No other CC's on either device -except obviously Pitch Bend and Mod Whl- are able to be mapped to Logic's MIDI Learn. When I Logic's Event List, I can see which CC is being received from the Ozonic and Nord, so I know, for example: The Nord's Filt Cutoff and Res are transmitting 71 & 74 (as they should) to Logic. I just downloaded MIDI Monitor and plan to use it tomorrow to see exactly which Controllers are being transmitted from the Ozonic/Nord and perhaps I'll figure out how to manually configure it. Even after reading the section of the manual over and over that shows how to do this, the Expert View of Logic's Controller Assignments has quite a few settings that are still over my head to some extent. I have been told it should work with any MIDI Controller (even "unsupported" ones), but I am not having any luck... anyone think I'm missing something???

I tried to post a New Topic and I got this message

Sure... thanks for your help David! I'll be back later on tonight and I'll create a new topic.

> Automationn Quick Access: it works fine with other devices, > but not with the Nord? Yeah, the Nord and Ozonic both don't work w/ either Automation Quick Access or MIDI Learn. It's the same for both of 'em. I'm not going to be able to connect my Ozonic via MIDI because I don't have the Power Supply (it's on loan from M-Audio) and right now it's receiving its power from the FireWire bus. Shouldn't my Nord work thru the MOTU Fastlane just the same though? Because I assume if the Nord isn't working through the Fastlane, then no other MIDI Controller will work through the Fastlane either. Whaddayou think about that? BTW: THANKS!!!

sorry for repeating myself. I couldn't see my original post so I didn't know I'd already said some of that stuff!

About your first question: I was trying to assign CC's to various parameters, but it was to basic things like EXS-24's Cutoff & Rez or the ES-2's Cutoffs & Rez's. Like I said, my Oxygen8 (connected via USB) worked fine and the Evolution UC33 (knob & fader box - also USB) worked fine. The Oxygen8 has a MIDI Driver installed, but the UC33 is Class Compliant, requiring NO driver. As for connecting the Ozonic to MIDI instead of thru FireWire. Thanks for the suggestion, but I can't do that (wouldn't want to) since it's being used as my Audio Interface as well. If I could afford to buy a MOTU PCI-424 to use my 2408 w/ the G5, I would much rather use IT! The Ozonic is an inferior Audio interface (doesn't even have balanced Ins). But either way, I don't think it'll make much difference since I'm having the same prob with my Nord Lead which is connected (via MOTU Fastlane USB) to MIDI. The Nord's knobs are transmitting MIDI just like they have for the last 10 years I've been using it. No settings have changed on it since it was working fine in Logic Pro 6 in Automation Quick Access. Now in Logic 7, I can't get Automation Quick Access to work with the Nord thru MIDI. Just like in the MIDI Learn Assignments, I'll move a knob (either on Nord or Ozonic) and it instantly responds that it's learned. If I'm in MIDI Learn's expert view, it will show the proper CC# and additional SysEx, so I know it's recognizing the proper CC, as are the Nord and Ozonic transmitting the proper CC messages. Another thing to consider is that both units work (as is - perfectly) with all other apps' MIDI Learn features. Weird, huh?