Marcus Aurelius

Thank you for the comments. I wish Apple would at least open it up in some way for third-party sampler developers (i.e. NI with Kontakt) to achieve the same functionality (or perhaps Apple have done so, but NI has not taken up the development of the desired feature). It's up to NI to get it right, and Apple is blameless if they fail to do so. Yes, it will work with identical Kontakt libraries. My concern is with specific instruments saved with the project; those instruments are not in any Kontakt library, and the samples may be from anywhere, so I want them stored with the project. But the project name and location on my hard drive will change over time, and that breaks the sample links. If I collaborate with another, it's the same problem. It seems I will be using Apple's Sampler a lot more for this kind of work, and just use Kontakt for built-in library instruments, unless I can find a way to make this work better.

It's spread across two drives, an external drive and the internal drive. The problem is not with the location of the library, and it will arise with any of those three sources. The problem arises when one wishes to save the Kontakt instruments and samples with the project. I want Logic to reference those samples, in the Logic project folder. Thus even if the other sample libraries are not available, or if the folder is moved or re-named within the same computer, or moved to a completely different computer, the project should still automatically reference and load those correct samples from within its own project folder. Maybe it's impossible. It does work with Logic's own Sampler, though, per my tests above, so it is technically possible.

Thank you for the reply. Do you mean the batch re-save function? Or the ability to relink with Native Access? The former would be inconvenient to re-do each time one moves or re-names a project. The latter only applies to libraries supported by Native Access, so it would not help for instruments and samples saved into the Logic project folder. I'm looking for a way to avoid the additional steps. That is, when a project opens, it should look for the instantiated Kontakt instruments' samples inside the Logic project folder, where I saved them. It should do that even if the project changes name (thus project folder changes name) or location, even if the project is moved to a different computer. That is, Kontakt instances should be save-able with project-relative paths. Logic Sampler Test 1: Failure Testing a bit with Logic's own Sampler instrument, and that seems to support the functionality I describe. I created an instrument in Sampler in a Logic project, saved it with its "audio content" into the Logic project folder, which created an .exs instrument file and a samples folder named after the instrument. However, this led to same problem as with Kontakt: re-naming or moving the Logic project folder led to missing samples error. Logic Sampler Test 1: Success A different method in Logic did seem to work, however: Instead of saving the individual Sampler instruments and samples, I saved the whole Logic project while checking, in the save dialog, under "Copy the following files into your project", "Sampler audio data". This created a sub-folder in the Logic project folder called "Samples". Inside that folder were sub-folders for each instrument, each containing the samples for its respective instrument. The instrument files, unfortunately, were not saved separately, but of course the Project remembers those. This approach worked, in that it achieved my goals: Moving or re-naming the entire Logic project folder did not break the sample links; Logic continued to automatically find and load the right samples from within the Samples folder inside the Logic project folder. So it seems that Sampler can do this whereas Kontakt cannot? Any further insights from others welcome and appreciated.

Hello - I'm revisiting this question, as I would like projects to be portable with their Kontakt instruments and samples. Thus, I save the Kontakt instruments and samples into the project folder. However, if I move or even just re-name the project folder, then the Kontakt instances in Logic fail to find the samples! Is there any resolution to this? It's also important for collaboration, to be able to move projects back and forth between collaborator computers (assuming there are no license restrictions on the samples which would forbid or prevent this; i.e. we both have licenses, or the samples are our own creations). Thank you for any suggestions.

P.P.P.S. Yet another bug? Volume/pan automation is not copying over into the bounced audio track. I was wondering why my mix levels sound wrong after bouncing some tracks and regions. Now I know why. I bounce with "Include Volume/Pan Automation" turned off. Per Apple's documentation, both for Bounce Regions in Place and Bounce Tracks in Place, leaving this unchecked should mean "the volume and pan automation is simply copied, not performed." Apple's documentation: Bounce a track in place in Logic Pro for Mac Bounce a region in place in Logic Pro for Mac See attached image. (Here I bounced the region, rather than the track, but result is the same with bouncing the track: the volume automation does not copy over).

P.P.S. One last odd behavior which happened a couple of times while trying to do the Bounce Tracks in Place. (I don't recall the exact combination of settings when this happened). All my Aux track levels got reset to 0dB! So I lost all the various level settings I had done for the drum mix of the Auxes. I had to recall a backup of the project to get them back. (Apparently Undo does not work for such a situation).

P.S. Another strange behavior I noticed. Even with "normalize" option, off, the "Normalizing" process bar appears multiple times. Seems to just be checking for overloads, but I have it set to "off", so it should not even be doing that. Odd.

Thank you again for your thoughts, Jordi; your guidance is much appreciated. Sorry for quoting out of context. If you do have a chance to further test, it would be interesting to see if you get different results than I did. For reference, I am using Logic 10.8.1 in non-Rosetta mode, on latest OS X Sonoma with all current updates applied, on Mac M1 Max. I'll submit a bug report to Apple now. If others wish to also report this (or other) Logic issues, here's the Apple form: https://www.apple.com/feedback/logic-pro/

Thank you for the detailed responses. Quick test shows this method works; I will test further. Thank you for this. Seems to be a bug then with the "as additional tracks" feature? The main instrument track (the one with the MIDI region in it, and hosting the actual software instrument track) seems to bounce -- if selected -- whether or not it is passing audio. If you have time, try as follows, with the Bounce Multiouts 2 project above. Test 1: Select only the instrument track, and try the Bounce Tracks in Place with Including Instrument Multi-Outs selected (try both with and without "As Additional Tracks" Here, I get one audio track with all the audio in it (i.e. output of both auxes) Test 2: Select all tracks, including the instrument track, and do the same as in Test 1. With "As Additional Tracks" selected, I get the same result as in Test 1: a single audio track merging all the audio (both Auxes). Without "As Additional Tracks" selected, I get 3 audio tracks: the same merged audio track, and the two auxes. Seems like a bug indeed. If so, we should all be reporting it to Apple's feedback area!

Any final consensus on this now? What's the proper way to bounce tracks in place, with multi-outputs, such that additional tracks are created for each output? My original method in past versions of Logic: Select just the instrument track with the MIDI in it (no need to select the Aux tracks or create blank regions in them), select Bounce Tracks in Place, Include Instrument Multi-Outputs, As Additional Tracks. Now, the method seems to require selecting the Aux tracks. HOWEVER: Problems still arise if any outputs are routed through the Main outputs (i.e. the track with the MIDI in it). That always worked fine for me. Now, this new method requires selecting that instrument track along with the other auxes. This leads to erratic results, like: - not all Auxes are bounced into tracks - a track is created which contains audio of multiple Auxes merged together (the name may be a concatenation. - one Aux is not bounced at all (i.e. missing), typically the output that was routed to the main output (i.e. that would come out of the main instrument track) If others have time, please test this. Try bouncing while selecting the main instrument track (either with or without selecting the other auxes, and either with or without actually routing any audio outputs of the instrument to the main instrument track outs). For example, with the Bounce Multiout 2 project above, select all 3 tracks and do the Bounce Tracks in Place (or just select the first track, the instrument track called "Multiout". The result here is a single audio track with a concatenated name (see image): Multiout_bip_Multiout Samp5-6_4 Maybe the problem can be avoided just by never routing anything through the main outputs 1-2. However, I have hundreds of multi-output presets I use which are set to route through 1-2. Why did the behavior change? Is this completely buggy? Is it documented anywhere by Apple? Any help much appreciated!

Understood. Thank you for clarifying. I'll probably do that also, using a "Factory" folder. (I do things a bit differently, though, and I put these presets in the system-level Presets folder, rather than the user-level Presets folder. My logic [sic] is that this is where the manufacturer would presumably install the presets if they included them with the plug-in installers.

This is fantastic. Thank you again for doing all this work! One question: The organization of these presets is different from the UADx ones you posted. The UADx ones have a sub-folder called "Factory" which contains all its presets, whereas these Apollo versions do not. Any reason for the difference? Should I put such a "Factory" sub-folder for these Apollo ones also, to differentiate easily from user-created presets?

Fantastic! Thank you for doing this. I will test these out next week.

Just tried it, and the presets work great! They load right up into the Logic plug-in instance! Ah, yes, you are correct; I forgot that. Were Logic presets ever created for that native one?

This is great! Thank you for doing this. I hope others (and perhaps you yourself) will find this useful. I will certainly spread the word to colleagues and friends who use UAD with Logic. For a test run, perhaps try with Galaxy Echo. There is no native version of that plug-in, only the hardware UAD one.