Jump to content

Marcus Aurelius

Member
  • Posts

    167
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Marcus Aurelius's Achievements

Contributor

Contributor (5/14)

  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges

12

Reputation

  1. 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).
  2. 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).
  3. 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.
  4. 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/
  5. 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!
  6. 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!
  7. 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.
  8. 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?
  9. 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?
  10. 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.
  11. That still sounds like an immense amount of work! That is very generous of you. I hope you can automate the process as much as possible. Perhaps Apple should license your scripting inventions from you to incorporate into Logic!
  12. Thank you for looking into it. Yes, understood that it is a lot of data and work! If you find a way to automate the process, that would be wonderful. Otherwise, if your time allows and you have the motivation, perhaps just start with the "greatest hits" of most popular UAD plugins. Perhaps Apple could include this automatic creation of Logic presets from plug-in presets as a Logic feature. In fact, I am going to request that through the Apple feedback area. Apple should see this as another great Logic feature that improves workflow. The more people who request this, perhaps the more likely that Apple implements it. So others who value Logic presets for plugins, please voice your support to Apple for an automatic method of such creation to be added as a Logic feature: https://www.apple.com/feedback/logic-pro/
  13. Thank you for that. All sounds right. I believe there is a way to copy and paste individual settings between the two formats, but that doesn't help much with the creation of Logic presets, especially if the built-in factory presets are the same in both versions. It would allow one to copy custom/user presets back and forth. That still doesn't help much with the Logic presets question, though! Here is what I found in the UA manual: "Use Copy and Paste to copy settings from the plug-in and paste them to a different instance of the same plug-in. You can use this to copy and paste settings between instances of the same plug-in in a session, or to copy and paste settings between the UAD-2 and native (UADx) versions of a plug-in. Note: For plug-ins with narrow header bars (for example, Lexicon 224), the Copy and Paste functions are located in the ••• menu." https://help.uaudio.com/hc/en-us/articles/5085501350932-Using-Native-UAD-Plug-Ins-Manual#:~:text=Use Copy and Paste to,versions of a plug-in.
  14. Well, I was thinking to convert all the UADx Logic presets which you have generously created here to UAD presets for the same plugins in UAD format. That way one would have access to the same presets whether one uses the native UADx or hardware-hosted UAD plugins.
×
×
  • Create New...