Jump to content

frostym8

Member
  • Posts

    49
  • Joined

  • Last visited

frostym8's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done

Recent Badges

5

Reputation

  1. UPDATE: If anyone is experiencing this issue, I think I may have found a solution! - In standalone Kontakt, I made sure to turn off multiprocessor support - In VEP7, I enabled max available threads - previously it was set 1 per instance since I'm running about 80 instances with Logic's port limitation. I believe the reason was that all instances were set to a single thread which caused stuttering in Logic - In Logic, I'm running my project at max available threads, at 128 buffer no issues at all So far, that seems to be working for now, alleviating all the pain from that final core - no more stuttering!
  2. No system overload messages or errors from Logic
  3. Hi folks, I have spent quite a significant amount of time building a template within VEP7 and Logic and it seems that it's stuttering like crazy during playback. Specs: - M1 MBP 2021, 64GB RAM, 10 Core, Sonoma OS 14.0 - Logic Pro X 10.8.1 - VEP7 version 7.3.3610 - Kontakt 7 version 7.8.0 - Samples are running from external Samsung T5 SSD, libraries are batch resaved - Audient ID14 interface - 48kHz sample rate on my interface and project settings - Running VEP7 and Logic within the same computer What I've tried: - Played with using Multithreading settings within Logic for Playback Tracks and Playback & Live Tracks - Played with buffer size within Logic and Kontakt - Played with changing sample rate - Played the project back using my MBP speakers as opposed to interface, no difference here My template: - The template is clean and everything is saved as patches within Logic so I load things as I go, connect that instance to VEP7 and then set instruments' output to their bus (takes less than 10 seconds) - Reverbs and other send processing are set up per stem but these are disabled Examples: 1. I'm only runing 5 tracks from VEP7 in this example and CPU spikes within Logic are going up as soon as I hit playback - impossible to work with. When stutters happen, the playback returns to the beginning automatically so editing MIDI is not an option here: 2. In the example below, I have loaded exactly the same instruments as from VEP7 but they are distributed one instrument per instance within Logic - CPU spikes are significantly lower, playback is great, no stuttering and no spikes Could it be that this VEP7 template with a lot of instances is making Logic spike up the CPU and cause stuttering? What would be the workaround in this case? Any help would be really appreciated!
  4. Hi there folks, I have finally crafted a template of my dreams with all its pristine routing for stemming. The only issue I'm encountering now is that control+click for power button on Aux tracks such as reverbs, delays, parallel compression has not no affect. The reason why I want it is so I can load processing as I need with simple control+click for the current stem that it's in use. Having all of them bypassed is quite a pain to enable them one by one again. I will share my current discoveries. 1. control+click for power button does not disable plugins on aux tracks: 2. control+click for power button works on audo and MIDI tracks: 3. very surprising - control+click works for summed stack main track, audio, MIDI but not for aux track inside it: It seems any option here I can come up with, aux tracks themselves just simply ignore such a great function to unload unwanted CPU processing by one simple command... Any help would be appreciated!
  5. Hi there, I'm building an orchestral template using VEP7 within the same computer and I was wondering whether there's a way to save folder presets in Logic with all sends, plugins and routing? It seems on left side where library is, that the option to save folder is greyed out by some reason but for summing stacks it is allowed. I am trying to save auxes for multi-output instruments instead of using them for summing stacks. The purpose of what I'm trying to achieve is - build a big template with all the sends, plugins as well as routing and then depending on the project, load saved preset folders as needed for specific project, without wasting the time to look for specific patches and then spend time customising CC, adding plugins, etc. In that case, I would not need to worry about cluttered window with hundreds of tracks. Thanks!
  6. Hi guys, I just got amazing step sequencer called Stepic but I cannot figure out how can I export newly generated MIDI as a region? Is there a certain setting in Logic that's possible to use when using external sequencers as such?
  7. Yeah, that is weird. However, that track corresponds to the '005 Violins Shorts' as you can see on the picture so not sure if it would be a good idea deleting it:
  8. I never knew that window of automation existed so it's unlikely that I've messed with it deliberately. I created this template at March 2022 but I was keep updating it after every single project that I worked on. Since my template is quite expanded, I had to separate my composing and mixing templates into 2 separate sessions. Maybe importing tracks and their routing from one project to another could've caused this issue.
  9. Great, will give it a test and let you know how I get on.
  10. It's quite expanded template since I'm using tons of orchestral libraries and usually need to layer them to achieve realistic sound. I'm using 10.5.1 version of Logic VEP7 is hosted in the same computer, internally. Do you think it may be because of the overload? I never max out my RAM but I noticed that ports on activity monitor between VEP7 and Logic have immense numbers. Wondering if that may be the case...
  11. Lifesaver! Just tried it out and it works, thanks a lot for your help!
  12. Thank you, David! It works! How did you fix it? I'd like to know in case this happens in the future
  13. I've attached an empty project just with the specific track info. Track 1.logicx.zip
  14. Hi David, Sure, I've attached empty project to this message. Track Logic.zip
  15. I've stumbled upon a problem in my mixing session where only one track is not being affected by any automation at all. I have short violin track where it needs to come out a bit more - I used gain automation in case I'd need to adjust the balance again with volume fader. Automation is in read mode, but the gain amount does not move when I go over selected section. I tried deleting all automation from the track but it doesn't work. I also tried using other kinds of plugins but nothing seems to working either - any plugin that I use, Logic completely ignores any automation lane for selected track. There are no more automation lanes in selected track, only the one in the picture. This is not the first time I endure with this problem since I'm using empty ready to go templates with quite complex routings for smooth workflow. Any help with this is appreciated.
×
×
  • Create New...