DanRad

Why don't you just move the movie location to the desired spot in the Project settings > movie position. This gets to the subframe level. I do this all the time,.

Jumping on this.. I am using the Samsung SSDs. Does anyone else find the USB connection kind of janky? I know it's a small interface, but I have two, and neither seem to make a solid feeling connection with the plug. It always feels like I'm about to get the "The drive was not ejected correctly..." etc. Is there a more robust connection we can use for SSD drives? Thanks DanRad

No.. the default Video Export is PCM... It's only one step, so, seems like a small inconvenience. d

Thanks... I'm traveling and can't try this... it certainly looks promising... BUT..what happens when a cycle is employed. In the old days, you'd create a cycle, go into record and the part of the region in the area would be highlighted, indicating that it would be erased. Or, for instance, if there was unwanted data at the beginning of a measure. With this setting, if I don't play, data is left. This is not how I would hope it would work... In a perfect world, simply go in record.. ERASE. That simple...

Oscarwilde, I know you're a long time Logic Black Belt. What settings do you use for MIDI recording? How about the MIDI erase button... I always used that in the past and it was a simple process to record MIDI just like audio on a tape machine... go into record, wipe old data...in>out. Accurate. No new tracks, no merging, just new regions where I record... are those days gone? Any input, advice or admonishing welcome DanRad

Thank you for your response. I've tried every combination of MIDI overlap options and none will behave with all of the following attributes: Replace only the new recording, including inside a measure Wipe only the new area recorded, including inside a measure Not merge regions before or after Not create "Takes" or new tracks Please prove me wrong with a setting that behaves like LP9. The current regime is a total groove killer for me. Also, when the orange (X) button is pushed, the descriptions of the behavior in the menu seem to not match up with performance. IMHO., it's a total mess. ANY input or suggestions welcome. I just want to be able to record MIDI easily like I used to. Thanks DanRad

Please excuse my continued confusion, frustration and downright anger about the way MIDI is now recorded in Logic. I will try and control myself. Maybe some of you long time users have the same feeling, or maybe I'm an outlier. Or just a liar... but, I digress. Here's what I want (as was possible pre 10.3) and can't seem to achieve with the new OVERLAPPING MIDI recording behavior regime. Record on the same lane as an existing region. Mark the area for recording with a cycle, or just start and have 1 measure preroll, or punch in while rolling. Have the old data eliminated IN THE AREA I'm recording. Have the new recording create a new region where previous data existed. Have that region accurately fill the area I've recorded in. (various setting wipe and or create regions outside the area I've designated to be recorded over, or join the new recording with previous or subsequent regions) Can anyone share their settings or if you are suffering the same issues and have created workarounds. My current workaround is to create 3 lanes for each instrument and alternate so that unwanted deleting and joining of regions doesn't happen. This uses screen space, unwanted controller overlaps and difficult editing feedback with so many regions scattered around. (other issues, too, but I won't get into it.) I apologize as I've ranted about this before.. but I my workflow has been slowed down by at least 20% dealing with this unneeded feature... Previously (Pre 10.4) it worked perfectly (Just like an analog tape machine). In LP9 and before, you would choose "Replace" (the orange button with an "X" in it) and it would behave just like an analog tape machine, only with an UNDO button. I know we just march forward, but my feet are getting very sore. Thanks Dan Rad

Thanks for the response. No, power to the computer is coming from somewhere else.

Thank you for your response. Yes, it's from a project originating in an older version... But I've been able to import from other similar projects from previous versions.

I'm trying to import project settings from a certain project and I get this message: Any ideas on the cause?

Thanks for the response. I've played around with the buffer... no change. I'm wondering if the fact that some of the projects I'm running originated with early versions. I'm going to try making new versions from older project with "Import Project" and see if that changes anything.. I'll report back.

I'm working on an M1 MBP. 32 Gg 2Tb internal drive. I'm using a Clarett 8pre interface. I've just updated to Sonoma, though I had this problem before the update. When using Logic 10.7.7, all is fine... When I use LP 10.7.9 or (now with update) 10.8.1, I often get "digital garbage" in the form of cracking and popping. This will happen with the same project. I'll be working in 10.7.9 or 10.8.1, and get the crackling and popping and then take the same project, open it in 10.7.7 and all is fine. This is driving me crazy and has me stuck at 10.7.7 Any help greatly appreciated. DanRad

If it's just for reference, I use AAC to make a smaller file to fit in eMail.

What a great tip!! I've now created a key command for remove overlap on repeated notes and I will save a lot of time!! Thank you!!

Thanks.. I'll try that and see what happens.