jimmyk

NM - I restored version 10.6.1 from my old Mac and it now works great! Not sure what else is broken in 10.6.1 but I am happy for now.

Hello - I have not been mixing for a while but just recently got back into it. I bought a new M1 mac mini running Ventura13.1 and Logic 10.7.6 I am trying to sidechain Trackspacer on my bass track with my kick as the sidechain. I am experiencing the awful latency and timing issue described here. I am using the Trackspacer plugin on the bass audio track and using the sidechain input directly from the Logic Drummer instrument track. I really would like to get this project finished. I think I have read all of the posts in this topic but is there any workaround to this that doesn't completely wreck workflow? I thought I read something about using busses, but couldn't find a clear how-to. I would hate to have to bounce everything to stems for example and mix in a new file with no/zero latency plugins and then not be able to make more tweaks without bouncing every time I do. I would be grateful if someone could provide a reasonable workaround until this gets fixed.

A couple of things you could try since it seems to be some sort of latency calculation error: - Turn on Low latency mode - Disable software monitoring - Disable all-plugins in your session - Export the DI track and bring it into a brand new empty session, then try re-amping again with no plugins

Hey stuckpig, check to make sure you are looking at the midi instrument layer after you go into the MIDI Environment as David noted above. I thought mine were missing too, but after switching to the Midi instrument layer (in the top left pull down) they showed up and I could delete them.

Try setting your delay compensation to "Audio and Software Instrument Tracks".

Brilliant! I did not know that. Worked a treat! Thank you sir!

When I am editing my audio tracks, I will hold the Option and Shift keys to copy the audio region to a new audio track and this will make sure it is aligned with the same grid position as the original. But when I do the same thing for a midi track, it creates an alias. I am wondering if there is a way to make a true separate copy of the midi region that is aligned to the same position on the grid like the audio region. I know I can double click the midi alias afterwards and it will prompt me to convert it to a true copy, but this is inconvenient when editing many regions. Thanks!

Yes I agree. Assigning a key shortcut is the way to go. And that's free. I liked Batch Commander but its one more thing to pay for and keep updated. Now if only core audio would initialize faster...

Looks like I have to pay for the Logic version...Oh well the short cut above works good enough. Thanks again des99!

OMG..just found out they have a version of Batch Commander for Logic. Hope my license covers it...

Thanks des99. I used to use a plugin called Batch Commander back when I used ProTools and that had two buttons you could click while you were in your session. One for 128 and one for 1024. Made it super easy. I will definitely try your shortcut as that is quicker than how I do it now.

I often find myself changing the buffer size in a project. I will start off with 128 while tracking. Then as things start to progress, I will start adding plugins and need to change the buffer to 1024. As I start mixing and getting it to sound good, I will then want to track something new or re-track something. So I set it back to 128. The I will mix it again and back to 1024. So I have this see-saw between mixing and tracking going on. I find it cumbersome to go to the preferences each time to check/change the buffer size. Is there and easier way to do this? Some kind of script maybe? Thanks! -Jim

OK - really confused now... @48K sample rate means 1ms = 48 samples. Tempo =120 Using nudge 1ms it moves 60 samples (should be 48) Using nudge 10ms it moves 493 samples (Should be 480) @48K sample rate means 1ms = 48 samples. Tempo =240 Using nudge 1ms it moves 54 samples (should be 48) Using nudge 10ms it moves 486 samples (should be 480) @96K sample rate means 1ms = 96 samples. Tempo =120 Using nudge 1ms it moves 60 samples (should be 96) Using nudge 10ms it moves 492 samples (should be 960) Nudging by sample seems to be correct at least it matches visually with the step pattern in the waveform. Jeez, I just want to accurately nudge some audio, didn't realize I needed to be a math major!

I have run into an interesting observation. I was using the nudge tool to align some audio tracks and found that if I use the nudge tool on the menu bar to nudge an audio track, the results are inconsistent between using a 10m nudge value and a 1 ms nudge value. For example, I lined up the start of the audio track exactly on bar 2. I then used the nudge tool set to 10ms and clicked the right arrow. The region moved to the right as expected. But when I then changed the nudge value to 1 ms and clicked the left arrow 10 times, the region was now significantly before the start of bar 2. Shouldn't it have ended up at exactly the 2 bar position. It was closer to bar 2 with 8 clicks than 10. What am I missing? Is this a bug or (gasp) user error. MacOS Catalina 10.15.6 Logic Pro X 10.6.0 Project sample rate 48K I tried this with a brand new project. Opened the project, dragged in the 48k wav file and lined it up to bar 2 using smart align. Zoomed way in to be able to see a 1ms move. Nudge once right at 10ms, then 10x left at 1ms. Track no longer at bar 2. Any ideas? -Jim

OK, I just backed up my 10.5.1 version of Logic Pro X and updated Logic Pro X to version 10.6.0. Now everything is working as expected again. I must have had some corruption or something somewhere.