Wolfie2112

Agreed! I submitted this request to Apple. In particular, I'd like to add a room correction plugin (like in Cubase control room) without affecting rendered files. I keep Sonarworks on the stereo output, but there's always that slim chance I forget to disable it. I have tried adding Sonarworks as the audio output in record options, but it introduces latency.

Thank you David!

Update: Apparently with 10.7.9 the sound triggered by the keyboard no longer changes when you change tracks so long as the R is highlighted with the red block on any track. I've reported this to Apple.

Hello, For the first time in several years, I'm actually having a major issue with Logic. Ever since updating to 10.7.9, I'm experiencing two issues.... 1) I can open a project from previous Logic versions no problem, and it actually plays back perfectly. However, when I select any track, I cannot play the instrument (for example, Kontakt doesn't even detect any controller input). This includes a variety of players and Apple itself. All of my input/outputs are correct. The weird thing is, Logic still detects the chords I am playing, and responds to my controller (NI S88), but that's about it. If I create a new project, it opens again just fine and works as expected. 2) In certain projects, I can play back the file no problem, but no matter what track I try and play, it only plays back one instrument from the project. For example, If I select any of the string tracks, I can only hear track 34 which is a synth patch. Just mind boggling. Anyone else experiencing this or have any insight? 2020 iMac, Ventura 13.4 Thank you!!

Fortunately, I was able to solve the issue... https://vi-control.net/community/threads/play-6-1-5-wont-work-with-latest-logic-version.88210/

Hi, I recently updated EW Play, and now I get an error message when launching Logic... Logic Pro X unexpectedly quit while trying to use the Audio Unit “Play” by “East West”. Has anyone else experienced this? I can load it up in VEPro no problem. Running Catalina 10.15.7 Thanks, and Merry Christmas.

I would consider completing your production at 44.1k, and then bounce your stems or mix in 48k for delivery. Whatever seems easier to you of course. I will try that! Might be easier that way. Thanks, David.

This is great, thank you!

Why? Unless you have a specific reason for working at 48k, I recommend you keep your original 44.1k sample rate for that project. The editors I work with require 24/48, it’s pretty much standard for film.

Sorry if this has been asked already...... I have a previous project that I need to deliver in a different sample rate. The original project setting is 44.1. I went into the audio settings and changed it to 48.....everything plays back correctly except for the audio (and Apple Loops), which all play back in a different tuning. Is there a step I missed? Thanks!

I have never compressed trailer music, even the epic stuff. Honestly though, I don't know what happens when I send the raw stems to the editors. But in general, even the lower budget stuff that I submit final tracks to, there is no compression (or very little). If anything, it's on the tracks that have huge percussion parts. For orchestral music in general, I would not compress.

Oh yes, good one! You mean like the "chunks" feature? That would be nice. Logic now has "track alternatives" which is similar, but the chunks thing is great. I also wish Apple would incorporate steamers, like in DP.

Oh yes, good one! You mean like the "chunks" feature? That would be nice. Logic now has "track alternatives" which is similar, but the chunks thing is great. I also wish Apple would incorporate steamers, like in DP.

I'd like to see some numbers about the first claim, seems dubious. Have you done any comparisons? I somehow doubt VSL forum is a good source for that kind of info. (Its like asking on Logic forums whether logic is great) As far as second workflow goes, could you describe it a little more? I dont think i understand correctly. What does this achieve compared to using logics templates, whats different? Ploki, regarding the core distribution...I have actually monitored this, and it distributes the loads across all cores as opposed to single core only. Based on my experience, sessions in Logic are much more smooth when hosting in VEPro. However, if I'm just using a modest track count, I don't usually bother. BTW- the VSL forum is a great resource, it's very informative and its members are users of pretty much all major DAW's. Plus, their support is very good, and a free trial is available upon request. Using a VEPro template is not like a Logic template. In a Logic template, everything needs to reload when you close and open/create a new project. With a VEPro template, you just load once....it all remains preserved until you close it. So if you were to close and start (or open) another project, all the VI's are already loaded. This is a HUGE timesaver when dealing with large templates and working with multiple projects (for example, 75 cues for a film). In a regular Logic template, you would need to sit there and wait for everything to load up every single time. I just wrapped up a big project, consisting of twelve tracks, each with three variations. My template (for the whole project) consisted of 98 tracks (Kontakt, Play, Omnisphere, etc), so imagine how much time would be wasted every time each cue was opened up (especially with an editor reminding you of a looming deadline ). With VEPro, it just a matter of seconds. But if you are only working with a handful of tracks at any given time, you may not find any benefit. All depends on your workflow.

I'd like to see some numbers about the first claim, seems dubious. Have you done any comparisons? I somehow doubt VSL forum is a good source for that kind of info. (Its like asking on Logic forums whether logic is great) As far as second workflow goes, could you describe it a little more? I dont think i understand correctly. What does this achieve compared to using logics templates, whats different? Ploki, regarding the core distribution...I have actually monitored this, and it distributes the loads across all cores as opposed to single core only. Based on my experience, sessions in Logic are much more smooth when hosting in VEPro. However, if I'm just using a modest track count, I don't usually bother. BTW- the VSL forum is a great resource, it's very informative and its members are users of pretty much all major DAW's. Plus, their support is very good, and a free trial is available upon request. Using a VEPro template is not like a Logic template. In a Logic template, everything needs to reload when you close and open/create a new project. With a VEPro template, you just load once....it all remains preserved until you close it. So if you were to close and start (or open) another project, all the VI's are already loaded. This is a HUGE timesaver when dealing with large templates and working with multiple projects (for example, 75 cues for a film). In a regular Logic template, you would need to sit there and wait for everything to load up every single time. I just wrapped up a big project, consisting of twelve tracks, each with three variations. My template (for the whole project) consisted of 98 tracks (Kontakt, Play, Omnisphere, etc), so imagine how much time would be wasted every time each cue was opened up (especially with an editor reminding you of a looming deadline ). With VEPro, it just a matter of seconds. But if you are only working with a handful of tracks at any given time, you may not find any benefit. All depends on your workflow.