What's new

Logic reloading Kontakt when project buffer size/audio device changed.

Billy Palmer

Active Member
In Logic I often need to change the project's 'io buffer size', 'output device' or 'input device' midway through a session.
The problem is that doing so forces every instance of kontakt to reload (which can take while)! Are there any workarounds please?

I often start on a low buffer to reduce input lag for my first few performances.
Once the session grows, I usually need a higher buffer to reduce CPU spikes.
 
In Logic I often need to change the project's io buffer size, output device or input device midway through a session.
The problem is that doing so forces every instance of kontakt to reload! Are there any workarounds please?
Not really. Hosting as much as possible in VEP might reduce the number of things that need to reload every time you change a setting, but really the best course of action is to find a way to have it stay the same throughout your whole process.

If you need to switch back and forth between two projects so that you can copy/paste data, turning Core Audio off is helpful.
 
Logic seriously needs to update its audio engine and get rid of this nonsense. It should be instant like Cubase and Studio One
 
I'm sure there is someone here who knows more about he Logic Audio Engine and may have the correct answer but I always assumed it was something integral to Logic's buffer/live playback system, because no other DAW I have seen does this. In that case it is just a price to pay for the extra efficiency Logic gives you over other DAWs. It can be a pain, I just go and make drink whenever I have to do this.

Logic seriously needs to update its audio engine and get rid of this nonsense. It should be instant like Cubase and Studio One

I think if Apple really wanted to get rid of it they would be able to find the funds in their 16.2 Billion Dollar annual research and development budget to get fix it
 
I've never seen Kontakt reload in ANY other app with a buffer size change. Cubase has had double buffers longer. Studio One has had them (I think?) from it's day one (as it's a newer app). So, they should be able to fix that. I'd bet it's more to do with the AU version of the Kontakt plug in. No other disk streaming instrument I own does that even IN Logic. Only Kontakt.

It's one of a million little things that informed that I didn't want to use LPX as my primary....and why I'm constantly amazed that there are people who use mostly Kontakt.
 
Rather 8 years with Cubase 7 and Asio guard. 2012... just saying!!

Input and instrument channels have used a fraction of the selected buffer further back. I used v4&6 for midi until last year. Previously, I used separate midi box vs sampling/VI box, because plug in VIs couldn’t get as low latency as gigastudio, so I don’t know at what point it got put there, but logic5 is what the plug ins were hosted in that couldn’t keep up with Giga.
 
I'm sure there is someone here who knows more about he Logic Audio Engine and may have the correct answer but I always assumed it was something integral to Logic's buffer/live playback system, because no other DAW I have seen does this. In that case it is just a price to pay for the extra efficiency Logic gives you over other DAWs. It can be a pain, I just go and make drink whenever I have to do this.



I think if Apple really wanted to get rid of it they would be able to find the funds in their 16.2 Billion Dollar annual research and development budget to get fix it
Logic has always behaved this way. Considering no other DAW does this it's not required in any way... Pretty sure this is just the result of either lazy coding, or more likely orders on high that more or less set the course for Logic development regardless of what the logic team might otherwise want to address...

People should take advantage of the feedback form more frequently... You can select any of these options below and send feedback about this..

Efficienty/workflow
Speed/perfofrmance
Connectivity/interoperability


 
Last edited:
Not even sure why this is an issue? Why would you ever change the master buffer in the middle of work? If you are short on horsepower then freeze some tracks, even if temporarily.
 
I occasionally have to use Logic, and this is rather frustrating.. but there are some work-arounds.

First, *in my limited experience* I have found that changing the buffer size in Logic is kind of pointless, since it only effects tracks that are record enabled.

Second, I set Logic audio output to System Setting. In practice, this has not caused the reloading thing - but again, I don't really use Logic much. I also use a program called LadioCast along with Soundflower to handle the routing of audio sources to my various output devices.
 
Not even sure why this is an issue? Why would you ever change the master buffer in the middle of work? If you are short on horsepower then freeze some tracks, even if temporarily.
Freezing's not helpful for me, I frequently change tempo/time signature or move tracks.
People should take advantage of the feedback form more frequently... You can select any of these options below and send feedback about this..

Efficienty/workflow
Speed/perfofrmance
Connectivity/interoperability


Done - cheers.
 
Old thread but thought it might be worth mentioning that I also observe this behaviour with Kontakt when changing the buffer size inside of Ableton Live so it's not something exclusive to Logic.
 
It occasionally happens when you undo/redo things.

I’ve reported this many years ago. It seems not so easy to change.
 
Yes, maybe with bigger Arm CPU's maybe it won’t be necessary to change the buffer, but even nicer would be to have it on the main page, not hidden.
Yes, Ive done the same, start mixing and near the end a new idea, having to disable plugs, change buffer, low latency and then redo once the idea is down. It is a flow kill for sure
 
Top Bottom