dbboy

Looking to purchase one once they become available again. For those of you who have had it for a while now, how is it working for you? I’ve heard of some issues concerning the fader being erratic and other little things, have these been ironed out? Any feedback would be appreciated, thanks!

Thanks. Ya, that’s what I figured. Really wish that would be an option though.

I would like to setup the count in click without hearing the audio along with it. As an example, I want to drop in somewhere in the middle of the project with a count in but just hear the click during the count in and then all the tracks at the record in point. I’ve looked everywhere but can’t find an option for this. Is it possible? Thanks!

Ah, not showing on my end. Updated.

That is not in my signature.

Latest Logic version running on an M2 running Sonoma. This is 100% reproducable. I’ll make a quick video in a bit. I also. checked the key commands and it is as it should,

Anyone else seeing this? Just wondering if I should send feedback to Apple. Thanks!

For some reason the return key is no longer working to launch a scene. All it does is start the transport from the beginning. It is supposed to override that function when key focus is on the Live Loops window. I used to be able to use the arrow keys to navigate through the scene triggers and hit return to launch that scene. Now this no longer works, looks like it is only controlling the tracks window. What am I missing? Is this a bug? I can reproduce this using any demo live loop song as well. At first it behaves as expected but, if you open the tracks window and then close it, the return key gets stuck back to starting the transport from the first bar. 100% repeatable.

I have tried this and have found that NO third party sequencers, locked to “follow daw” settings play the first note no matter where I start in the timeline. It’s as if there’s a delay for them to catch up, missing the first few beats when starting the Logic transport. I have verified this using the same plugin in Ableton Live and it starts exactly as expected. In this case it’s XLN’s XO but applies to all other third party sequencers. Copying the midi data from them onto the timeline fixes the problem so it’s some issue with the way Logic handles internal sync with AU instruments. Perhaps there’s a setting I’m missing or is this a bug?

Time will tell. You may very well be wrong. The devs at NI certainly think so. 😉

It’s an added feature that has been a long time coming. NI are working on it on their end as well as others. Ableton has had this for a long time, very handy to have.

From what I understand, the latest Logic update now supports midi out from software instruments. This is apparently causing some issues with notes being recorded twice (notably Native Instruments) From the forum: “ When using KK3 (3.0.0, 3.0.1 or 3.0.2) with Logic Pro 10.8, all MIDI notes are doubled. This issue reproduces with all MIDI controllers when using KK3. In other words, it is specific to KK3, and not to the Kontrol S MK3. This bug has been filed as a high priority, as soon as it was reported to us. We hope to fix it this month. Incredibly frustrating for all - I will keep you in the loop as this progresses. It appears Logic Pro 10.8 has silently introduced support for MIDI out from AU2 plug-ins. The impact of this is mostly positive: for instance, this means it is now possible for Komplete Kontrol's arpeggiator to send MIDI out of the plug-in, and into your timeline. This benefits all users of KK3 and Logic. At present, the value is limited due to the first issue. “ Whole thread here: https://community.native-instruments.com/discussion/18363/official-known-issues-with-and-features-of-komplete-kontrol-3-0-2-and-logic-pro-10-8/p1

@Anne22 I am a professional mix/mastering engineer with strong credits and demo reel. I would be happy to help you if needed. PM me with details. Thanks!

Will do later today. Can you tell me what 3rd party synths you have?That might help as well (but not necessary) PM if you want. Thanks!

This was happening before this latest version. Was hoping this update would fix it but no dice.