Jump to content

9u10m

Member
  • Posts

    76
  • Joined

  • Last visited

9u10m's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Indeed, deleting "Alchemy_Preset_Ratings_And_Tags.db" did the trick. So in my case selecting presets from Alchemy's GUI works fine, browsing them from the Logic plug-in frame will create duplicates.
  2. Reviving this thread as I'm having the same issue. While I go through presets Alchemy will also randomly add 5 stars to some of said duplicates. Surely we're not the only ones, although I can't find anything about this on google. If you or anyone else found a way to fix this I'm all ears!
  3. I'd also be happy to test them. If anyone is willing to share them, that'd be great!
  4. Funny thing, many Plug-In Settings folder are now empty but their corresponding plug-ins do show presets in Logic. Some Plug-In Settings folders contain a number of .pst files, which oddly add up to less presets than are actually displayed inside their corresponding plug-in menu. More problematic, the Space Designer folder is now empty and doesn't show any presets in Logic either.
  5. Hey there Matthew, would you be willing to tell me more about how you set up your workflow in that respect? I think I'm finding it very appealing for the same reasons as you did, and I'd appreciate it a lot if you would share some of your experience. How do you tackle dynamics processing on those stacks, for instance? How do you gel the whole mix? More generally, what were the biggest adjustments you had to make in that new scenario? Thanks a lot! All the best
  6. Yes I’ve always wondered why most sequencers don’t already have a batch export feature, would be so handy
  7. When I send stems for mastering most of the non dynamics processing in the mix chain gets to stay. In heavy projects bouncing stems separately takes longer than real-time printing in one pass. I need to try and see if said part of the mixing process could take place at stem level, but I’m not sure I find it practical.
  8. In any case, I was specifically trying to internally print my stems with mix bus processing. I’m familiar with the other methods already.
  9. You appeal to quantum physics
  10. Yes yes, you're right, that's the bottleneck. I needed to wrap my head around it. I also realize MikeRobinson and I were not talking about the same thing, now I see where he was going. That's too bad, thanks for the help though!
  11. I agree with your maths, so do the mastering engineers I work with. Yet they don't mind, and the difference is so small when the dynamics processing is bypassed that it doesn't matter much in the end. My question lies elsewhere
  12. I mean this: I'm not sure my scenario requires it. Actually I can manage sending the mix chain to each and every print bus, I'm only experiencing louder levels and I want to make sure they're not the result of some looping signal that can be fixed.
  13. Hi and thanks! Dynamics processing is bypassed on my mix bus when I export stems for the mastering engineers. I've always resorted to bouncing solo regions/tracks so far, but I often tend to find it less efficient than printing in many scenarios. So to make things clear: send track stacks to return busses > input return busses to audio tracks > internally record all tracks simultaneously works fine, but there is no way to print the mix processing along with it?
  14. Someone's grumpy. I understand you mean to say that what I'm suggesting is not possible?
  15. Well, I precisely want to avoid a bounce and print all stems in real time. It works fine, all I'm missing is the ability to apply the mix processing from my main stereo bus.
×
×
  • Create New...