posthorn1

Got it. Creating a Flex Marker at every Tempo makes sense, but doesn't quite comport with my working method. I devised a work around: I'll make a duplicate of my click track and delete all but the first beat of every bar. Then I'll base my Beat map on the bar rather than beat. I'll see how that goes...

It turns out the eraser tool works on these, so I guess I answered the first question myself. If someone could tell me how I could make it so these don't appear in the first place that would be great.

I recorded a live guitar part free time and then recorded my own midi click track to match. In order to conform the grid I used Beat mapping - designating each click a 1/4 note. When I go into Flex Time there are a lot of (what look like) Markers added on every beat. But they are something different since there is no X to delete them along the top of the track like usual. They also appear as blue lines on the beat mapping track. My guess is these are added because of the tempo changes. What are these markers and how do I delete them? Is there a setting so these won't appear?

Ah, thanks. I guess I inadvertently checked that somewhere along the way.

Recently I ended up with an Inspector column that includes a box for "Quick Help". I can't figure out how it got there, but I'd like to remove it. I assume there is a box to un-check somewhere but I can't find it. Thanks.

OK thanks. I tracked it down in the environment. Rather than deleting I just reassigned port 1 to my new device. Thanks! SOLVED

I recently changed my MIDI interface, but Logic appears to be still looking for the old one. I get the following message when I open a new file: "Instrument “GM Device” sends to a MIDI port named “Port 1” of MIDI interface “USB MIDI 1x1” which no longer exists. Please check if all MIDI interfaces are connected and switched on; otherwise adjust the instrument’s MIDI out port setting." I can't figure out how to remove the old midi interface ("USB MIDI 1x1"). The new interface is being seen and working fine. I'd just like to not have this message window keep appearing.

I use the iPads with TouchOSC and/or Lemur. For my purposes they only fire Key Commands. Takes a while to learn and set up, but helps workflow a lot.

This is what the setup window looks like. The "No Device" at the top seems strange. I don't recall ever creating a CS Group and I don't know what all of those parameters mean.

I have a Korg NanoKontrol Controller - just knobs and faders sending CC info connecting via USB. Logic recognizes the device and connects automatically but only responds to the "most popular" controls like #1 (Mod), #7 (Vol), #11 (Expr). In order to access the less common CC's like #21, #17, etc., (that I have assigned to faders on the Nano) I have to go to the Controller Assignments window (in Prefs) and change the MIDI input from "nanoKONTROL SLIDER/KNOB" to "USB MIDI Device." (see attached images) Unfortunately, this information is "forgotten" every time I quit Logic. Question: How can I have Logic remember these settings so I don't have to repeat this process all the time?

Thanks, those were great suggestions. Unfortunately the problem persists, but it did bring up another question: Is there any way to set the value of the MIDI Reset Messages, or does it always have to be zero?

There are certain midi tracks of mine that send a value of 0 on CC#1 (Mod) when I hit Play and/or Stop. I've tried to make sure there is no hidden CC info on the tracks. I have a work-around by creating a region at the top of the sequence with a CC#1 command value of 64 (my default volume for the instrument I'm playing). I'd rather have the instrument set at 64 and not have the track change it until it gets a command to do so. Interestingly, I have many tracks where this is not a problem, but I don't see any difference between them. Also, it seems that ONLY CC#1 is changing and none of the others. Is there a midi track setting I am missing? It's possible the problem is on the receiving end - in this case, a NI Kontakt (v5.8.1) instrument hosted in Vienna Ensemble Pro 7 - but I want to make sure Logic is not the problem before I investigate that. Thanks!

Thanks volovicg, this was indeed the issue. I had hidden modulation info in the region I was copying from - prior to the beginning of the region. The "lateness" of the paste corresponded exactly with the distance of the first hidden event. I'll keep an eye out for that and make a request that this be fixed for future updates. I can't seem to upload a .logicx file for this post. David Nahmani, if you'd like to see it please instruct me. SOLVED. Thanks!

Sorry I screwed up my commands...I meant the "Paste at Original Position" command isn't working. Not "Paste in Place."

I am finding that the "Paste in Place" command is not working properly. The material will paste on the track I selected, but it will not be in its original position...usually two bars and a couple of beats late (although it doesn't seem to be a consistent amount). Can anyone think of a reason why this would happen? I wonder if there is some kind of offset I don't know about on certain tracks. I've been using Logic for many years and this is the first time I've come across this problem.