Hey, feel free to send me an email. You can find my email on the About page of my KZbin Channel. I'd love to hear more about your project.

@@StephenOConnellCmdShiftNew Hey Stephen, I sent an email to you. I'm looking forward for your answer!

The problem was related to changing articulations on multiple tracks on the fly, causing samples to reload constantly. The answer was: open the task manager and watch the RAM chart. I had 30gB of samples in my 64gB of RAM. Making articulation changes was causing massive memory substitutions. If I waited until the RAM graph stabilized, there were no tuning issues at all. If I attempted playback before allowing the new articulations to be fully loaded, there were tuning problems. Just needed to be more patient. It was all related to disk data transfer speed as opposed to CPU load. Once all the samples needed for the piece were in RAM, no tuning issues at all.

Then by all means, please record the speaker ❤️ this is just a great way to get a realistic recreation of the speaker sound when you don't have either the time or the equipment/space to record a live guitar amp speaker.

I definitely want to do a video on this topic soon, I've been meaning to for a while now.

Hey Harry, I'm not quite sure what you mean, do you mean a label for the knob, as in "Filter Cutoff" for example? If so, you can use the same method here, but without the get_engine_par_disp commands. You can just use the set_text command and put the title in quotations, like set_text($label, "Filter Cutoff"). Otherwise, you can save it as an image and load it inside the label, something I'll share a video on soon I'm sure.

Great suggestion, I have now moved over to using Sublime Text Editor in my videos to help with the quality of the video and clarity of the text. VSCode is another great option though, I've used their KSP editor before and it also does a great job. I'm just more familiar and used to Sublime.

Hey, I released a video I think might help you with this question: kzbin.info/www/bejne/laaWh36qo7Kfj5I

Haha 😝 true that

Hey, sounds like it might not be in polyphonic mode. If it is in slicing mode, it would sound like it is skipping. Also, if it says (Automatic) next to it, change it specifically to polyphonic. Sometimes I've noticed that Logic says it is in poly mode but it is really in slicing, but setting it manually to poly mode helps correct that.

It could be that your advanced features aren't all turned on. Check out the Preferences in the Logic Pro menu and make sure all of your advanced tools are on and then set your LCD to custom display.

I used to do this, but duplicating a track that has a massive library on it, like the BBC SO Library or an OT library can really slow down the computer, not to mention take a long time to duplicate the track initially and then load the samples. Creating a track this way means it is still using the same instrument, so the workflow I find can be a little quicker.

There is a Logic Pro function that can detect the BPM of a track, so it will match the BPM to that track's detected BPM, which I believe you can set to sensitivity. So you could say try and match it close to every bar, then you could quantise the bar's beats with flex time.

Hey, you can indeed. The same principles apply, you would just be using a different set_engine_par command to target volume (which is easier because it doesn't have the find mod and target commands).