jamsden

As far as I can see, there's no way for Logic Remote to create a new project from a template. Logic Remote as a New Empty Project key command, but no new from template, nor is there any way to change the default template for File > New. Am I missing something?

I just submitted defect FB12000311.

I've had this problem as well using side-chain inputs into AU MIDI-controlled plugins such as Helix Native. I solved it by using Ultrabeat instead of Drum Kit Designer on drum tracks. It seems the issue is some interaction between side-chain inputs and the new Logic Pro sampler that replaced EXS24. I get additional latency if the drum track uses Drum Kit Designer and some track has a side-chain input. No side-chain input, no additional latency. Or no Drum Kit Designer, no additional latency. I haven't tried using other samples in the Sampler plugin, but I suspect the problem is in the plugin, not the drum kit samples. Has anyone submitted a defect for this?

The issue with increased latency when using a bus side-chain input into an AU MIDI-Controlled plugin such as Helix Native was caused by record enabling a track that uses Drum Machine Designer. Using UltraBeat doesn't exhibit this behavior. Perhaps Drum Machine Designer's use of the recently introduced sampler is the source of the problem.

The issue was caused by record enabling a track with Drum Kit Designer. There's some interaction between Drum Kit Designer and side-chain inputs into a MIDI-controlled plugin that causes the additional latency. Replacing Drum Kit Designer with Ultrabeat fixed the problem.

And actually neither do I! I think I found the problem. The issue wasn't directly related to bus inputs to AU MIDI-controlled plugins. If I created an empty project with just a dry audio guitar track into a bus and then into the side-chain of Helix Native, I had no latency problems. But in my larger Logic project for the whole band I did. I stumbled on the cause of the problem. As soon as I record enabled the Drum track, which was using Drum Kit Designer, I would get the additional latency This happens with the regular and producer kits. I doesn't happen with Ultrabeat. So there's some interaction between Drum Kit Designer and side-chain inputs into MIDI-controlled plugins that causes the extra latency. With Ultrabeat I cannot reproduce the problem, even after Logic restart and having and about 16 tracks record enabled. I'm calling this solved!

Unfortunately due to a bug in Logic Pro, setting the side-chain input of an AU MIDI-controlled plugin results in much increased latency. So this simple solution is not usable. Sending audio into the side-chain input of a MIDI controlled plugin seems to have no counterpart for setting the MIDI side-chain of an audio plugin. A summing track stack can configure a MIDI input if at least one of its children tracks is a software instrument track. But audio plugins in the summing track stack don't receive that MIDI, instead it is sent to all the children tracks. Seems upside down.

I tried going guitar:input 2 > bus 34 > bus 35 > Helix Native side-chain input > stereo out. Initially it worked with no latency and turning on low latency mode gave no sound at all. But after Logic Pro re-opening the project, the latency is back and turning on low latency mode gives the dry sound routed to the stereo output, even through there is no path that I have configured that would do that. i.e., I deleted the aux track for bus 35 > Stereo Output. I was able to get no latency to work in a few other instances, hard to know exactly how. But again as soon as the project is closed and reopened, the latency is back. I'm moving to Reaper for this application. Its routing, especially for parent/child tracks and MIDI configuration is just much simpler and works perfectly. I love Logic's UI, workflow, instruments and plugins. But without side-chains into MIDI controlled plugins working, it's not useful for guitar plugins, which is a blocker for me. I'll file a bug with Apple, but don't have much hope it will be addressed anytime soon.

Yes, same issue. It doesn’t seem to matter what the input is. I’m going to try using and extra indirect bus today, someone said that might work.

Seems like side chaining from anything adds latency. And side chaining from an Audio track doesn't produce any sound unless the play head is moving, recording or playback. I reported that bug.

I have also seen the problem when using AU MIDI-controlled effects like Helix Native or Neural DSP plugins that you want to control with a MIDI foot controller such as Morningstar MC8. Once you set the side-chain input to a bus that feeds your dry guitar, the latency goes up. Clicking low latency mode disables the side-chain input. This limits controlling complex guitar plugins to using complex controller assignments and plugin parameter automation which is not nearly as convenient, reliable, or effective.

An unfortunate update on this technique for controlling guitar effects plugins. It appears that setting the side-chain input of MIDI Controlled AU Effects causes the latency to increase to what appears to be the maximum buffer size, if there are any tracks record enabled when you set the side-chain input. If you set all the side-chain inputs to none, and restart Logic, then set the side-chains with nothing record enabled or input monitoring, the the latency isn’t increased. But as soon as you record enable some tracks, the latency increases. It’s not clear how many tracks it takes for the latency to jump. Turning low latency mode on turns off the side-chain inputs. If you carefully set all the side-chain inputs with nothing record enabled, then there is no additional latency. But if you save and reopen the project, the latency comes back. Really to bad this technique isn't useful.

I also noticed that dragging files from Finder into the tracks also imports them in the wrong order. This is definitely a regression bug. I found a simple work around though. If you select all the files in the files browser, All Files tab, right click and select Add selected Audio Files to Project Audio. Then select the Project tab to see those imported regions, do Cmd-A to select all regions, right click and select Add to Tracks.... The regions are imported into the existing mono and stereo tracks in the right order.

Using Logic Pro 10.7.5 on macOS 13.0.1, open a project that was created from a template (i.e., has mono and stereo tracks, but no audio regions in the track. Open the Project Media browser and select All Files (there you have a folder that has a number of mono and stereo .wav files that are in the same track order as the loaded project template). Select all files and drag and drop to the first track, at location 1. See the prompt to add selected files to tracks, and select use existing tracks. What happens: Logic Pro prompts that there's a track format mismatch between stereo and mono tracks. Select Keep track format and the audio files are imported, but in the wrong order. The stereo tracks are moved to the first tracks and the mono tracks follow. What should happen: the audio files should be imported in file and track order. This works correctly in Logic 10.6.3 on Catalina. But it does not work correctly on 10.7.5. I use this a lot to get tracks recorded from live gigs on an X32-Core using X-Live cards. The Logic templates match the X32-Core scenes. This change/defect has broken this workflow.

Yes, this is how I'm doing it now. I let the summing folder stack choose the next available bus. Then configure the audio and software instrument side-chain tracks, then save the folder as a patch to reuse the setup. We can probably consider this resolved.