Jump to content

Logic Pro 10.7 Released


David Nahmani

Recommended Posts

The release notes posted won’t show a Remix FX related thing I had in more than one project: for eg. the filter+reso x/y pad works, draws automation (in touch mode) plays it back correct until at some point it doesn’t: Logic fails to follow the automation, no change in the sound, like it was just dry. If you duplicate the track, drag the audio + automation on the new track, it works again, until it doesn’t again. Sometimes saving and reopening the project works, often not. It also won’t bounce it correct when it stops working.

I've seen this issue posted several times.

 

When you say the release notes won't show this issue, do you mean this issue was resolved in 10.7.1?

Link to comment
Share on other sites

The release notes posted won’t show a Remix FX related thing I had in more than one project: for eg. the filter+reso x/y pad works, draws automation (in touch mode) plays it back correct until at some point it doesn’t: Logic fails to follow the automation, no change in the sound, like it was just dry. If you duplicate the track, drag the audio + automation on the new track, it works again, until it doesn’t again. Sometimes saving and reopening the project works, often not. It also won’t bounce it correct when it stops working.

I've seen this issue posted several times.

 

When you say the release notes won't show this issue, do you mean this issue was resolved in 10.7.1?

Nope, I mean I don't see it in the FIXED list. (so assuming it wasn't fixed; haven't had a chance to try it out yet)

Link to comment
Share on other sites

Such an advanced mix-focused update and we still don’t get basic functions like the ability to move tracks in the mixer and plug-in+I/O search… well, back to the feedback form i guess!

 

Yeah, it’s always struck me as odd that you can’t just move tracks around in the mixer. You have to use a roundabout way to get aux tracks to sit next to their respective instruments, for example.

Link to comment
Share on other sites

Are you guys having problems with flex time since the Logic 10.7 update? Specially when splitting regions - flex markers go crazy, many glitches are produced all the time, the regions aren’t splitted where I wanted (sometimes new tiny regions are created out of nowhere). Having a tough time editing my tracks since the update… thinking of reverting to Logic 10.6.3 till this gets more stable
Link to comment
Share on other sites

Hello gang.

 

I'm experiencing Logic 10.7 no longer sending MIDI clock to any of my interfaces. 2 of them are fully recognized by Logic and Audio MIDI Setup (MOTU Micro Lite, Presonus Audiobox USB96), the other is my Intellijel MIDI Euro module. No problem with any of them receiving Note On/Off from Logic, but no clock is recognized. I've enabled the various devices to send out Clock in the MIDI section of the Synchronization section (as I've always done), but no go. Would love any ideas for a fix...

 

Thanks!

Link to comment
Share on other sites

The lights blink on my Emagic MT-4 when I enable MIDI clock in MIdi Sync Project settings. They turn off when I disable. I guess this means it works?

 

If I send clock to my Wavestate(hardware), the tempo of the sequenced sounds follows. So it works for me.

Link to comment
Share on other sites

What's the verdict on the new UI in 10.7?

 

I haven't tried Logic 10.7 yet as I'm stuck with 10.5.1 on my patched Mac Pro 2008.

 

I'm budgeting for a new M1 machine and wondering if I should invest in an external retina-capable screen to replace my current 2560x1440 external display? Or does the new UI look okay on a non-retina screen once you get used to it?

Link to comment
Share on other sites

What's the verdict on the new UI in 10.7? (...) does the new UI look okay on a non-retina screen once you get used to it?

I wasn't a fan at first, but in the end I love it, even though I'm not on a Retina screen. I feel like the new UI is much cleaner, more ... straight to the point if that means anything. Less rounded corners, easier to work with on a day to day basis.

Link to comment
Share on other sites

Yeah, it’s always struck me as odd that you can’t just move tracks around in the mixer. You have to use a roundabout way to get aux tracks to sit next to their respective instruments, for example.

The Mixer is designed to follow the track order in the Main Window.

You can use the Environment window as a mixer. That allows you to put channels wherever you like - I've done that for many years.

Link to comment
Share on other sites

What's the verdict on the new UI in 10.7? (...) does the new UI look okay on a non-retina screen once you get used to it?

I wasn't a fan at first, but in the end I love it, even though I'm not on a Retina screen. I feel like the new UI is much cleaner, more ... straight to the point if that means anything. Less rounded corners, easier to work with on a day to day basis.

 

same here. just seems very... solid, professional (really, that's how it looks to me)...

Link to comment
Share on other sites

Hi all, Based on positive comments here I upgraded to Logic 10.7.1 and...gulp...Monterey 12.0.1. Logic fires up okay and is fine when starting new projects. But most of my templates and previous work crash when trying to open. I've turned off all plug-ins etc but that makes no difference. I'm close to my wits' end—any ideas anyone?

Excuse the following, but this is what the crash report says:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

 

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [1758]

Link to comment
Share on other sites

Hi all, Based on positive comments here I upgraded to Logic 10.7.1 and...gulp...Monterey 12.0.1. Logic fires up okay and is fine when starting new projects. But most of my templates and previous work crash when trying to open. I've turned off all plug-ins etc but that makes no difference. I'm close to my wits' end—any ideas anyone?

Excuse the following, but this is what the crash report says:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

 

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [1758]

 

what did you upgrade from? (in terms of the OS, and logic). and what mac are you on? (year/processor/ram)...

 

try importing everything from a problem project into a virgin project in logic. does that work?

 

what happens if you open logic, then open a problem file from the 'file>open' window... and make sure all your 3rd-party plugins are up-to-date; very important.

 

just some ideas, for a start...

Link to comment
Share on other sites

Thanks very much Fisherking. From Mojave and Logic 10.6. Mac Pro 2013 Vader, 3.5 GHz 6-core, 128 ram. I'm trying your suggestions now.

 

are other apps ok? you could also try booting into safe mode (the shift key on startup), then rebooting normally. or you could try resetting the nvram (google these things, apple has info on their site).

 

what interface do you use for logic? make sure it's software (if any) is also up-to-date. but my guess is... it's a 3rd-party plugin... (that's just a guess)

Link to comment
Share on other sites

There is no rhyme or reason to this: sometimes items (aux etc) from templates that will not open WILL import to a blank new file; other times the same items will crash it. Also, when I disable ALL plugins in the Plugin Manager, I still get a warning saying I am using 2 AUs which did not pass validation. And one that I entirely deleted (Pulsar Smasher) still shows up, gah.

I reckon I'm just going to have to forego all those (life sucking and uber-complex) aux setups and start over a new batch of templates. C'est la vie :)

Fisherking, I do appreciate your advice—many thanks. I'm off for a drink.

 

(BTW I'm a longtime LPH user but somehow got locked out and had to rejoin under an alternative name; hence the "joined two hours ago" on my profile, lol.)

Link to comment
Share on other sites

There is no rhyme or reason to this: sometimes items (aux etc) from templates that will not open WILL import to a blank new file; other times the same items will crash it. Also, when I disable ALL plugins in the Plugin Manager, I still get a warning saying I am using 2 AUs which did not pass validation. And one that I entirely deleted (Pulsar Smasher) still shows up, gah.

I reckon I'm just going to have to forego all those (life sucking and uber-complex) aux setups and start over a new batch of templates. C'est la vie :)

Fisherking, I do appreciate your advice—many thanks. I'm off for a drink.

 

(BTW I'm a longtime LPH user but somehow got locked out and had to rejoin under an alternative name; hence the "joined two hours ago" on my profile, lol.)

 

make sure, if you disable plugins that are no longer working, you also delete them (in either HD>Library>Audio>Plugins>Components folder (or the equivalent folder in your User folder). reboot! try, too, copying your preferred template(s) to, say, the desktop; open one, see how it behaves, and if it's good, save as template (so it's a new file with the same parameters).

 

anyway, i've exhausted the ideas in my (small) brain. hope you sort it out, or perhaps others here have useful ideas...

Link to comment
Share on other sites

Success! After several deletions, the pesky Eventide Mangledverb plug-in was the culprit and now languishes in deletion limbo. All works now. Sorry to tax our collective brains, anyone who read this thread—and especial thanks to kingfisher. A rare victory! Cheers all.

 

fisherking, but... glad to help, and glad you got it sorted.

Link to comment
Share on other sites

(Logic Pro X 10.7.1) Audio Regions moving when cutting [bUG] NOT fixed 2021

I was able to reproduce this issue here. :(

 

I wasn't. Initially I thought that is because I used the current Cmd-R default "Repeat Regions/Cells" instead of the older function "Repeat Regions/Cells/Events Multiple Times…", which used to have issues with its Adjustment setting "Auto" (and bugs me by design with its need to confirm a superfluous dialog), but that didn't allow me to repro the issue either – all perfectly aligned here. Strange. Which step exactly does introduce the error?

Link to comment
Share on other sites

I wasn't. Initially I thought that is because I used the current Cmd-R default "Repeat Regions/Cells" instead of the older function "Repeat Regions/Cells/Events Multiple Times…", which used to have issues with its Adjustment setting "Auto" (and bugs me by design with its need to confirm a superfluous dialog), but that didn't allow me to repro the issue either – all perfectly aligned here. Strange. Which step exactly does introduce the error?

It's tempo dependent. Try this:

 

1. Set your tempo to 138 bpm.

2. Set your cycle to exactly 1 bar.

3. Record a region on one audio track.

4. Command-R to repeat.

5. Command-U to set the cycle to the repeated region.

6. Create a new audio track.

7. Record on the new audio track.

8. Select all regions in the locators (Shift-L).

9. Repeat....

 

Do this until you have 5 tracks, and zoom in on the region starts.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...