Brian
Participant
Topics Started: 1
Replies Created: 16
Has Thanked: 2
Been Thanked: 1
Satellite to Apollo: one thunderbolt cable; Apollo to Mac: one thunderbolt cable with adapter. Works just fine.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
I’m already doing this, following your earlier posts. Just seems more complicated than having separate instances. However, the MIDI overdubbing discussed on the Avid DUC seems like a much better method, I’ll try that.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Just one thing – using my method of physically tapping the midi keyboard for each individual drum element in separate instances on SD3. I don’t see how this is possible using one instance of SD3 on an instrument track routed to separate aux tracks for each element. It works, obviously, using the MIDI editor, which records all three elements to the instrument track which then routes them out to the auxes. But I prefer to play along with the song, adding each element one by one. This isn’t possible using the latter method as each successive drum recording records over the previous one. Or am I totally missing something?!
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
I understand. I’ll try it to compare the results.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Got you, thanks. Just different ways of working I guess.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
As a related issue, this is useful: https://www.production-expert.com/production-expert-1/what-is-pro-tools-midi-live-mode-really-doing?
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
1
Thanked by: Scott EshlemanThree separate tracks so that I can have control over processing each element separately, just like miking a real drum kit.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Three separate instances, one for kick, one for snare, one for hihats. Only the kick has the problem! Even when I create a new track each time.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Thanks everyone, much appreciated.
It’s definitely not the keyboard, because every other instrument track in the session, and on all my other song sessions, are timing-perfect using the same keyboard.
I’m wondering about Jord’s comment on “some form of compensation”…quite possible, but difficult to isolate. I’ve tried switching delay compensation on and off, sample rate etc etc. Anyway, I think I’ll resort to using midi editor at least for now….
cheers,
BB
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Hammer action, yes (M-Audio Keystation88 Mk3).
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
But puzzlingly, the Superior Drummer 3 gui shows the drum impact earlier than the sound, even now that it’s recorded in the midi editor….
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
So….as you suggested, I recorded the kick track in Midi Editor rather than on midi keyboard, and all seems good. But when I try to record with the keyboard, the issue continues, so I guess there is a sink issue with my keyboard…more research needed.
Many thanks for your very helpful suggestion…Now I just have to “humanize” the midi kick track as it’s aligned to the grid!
cheers,
BB
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
Sorry, Question 1 – yes, the tracks are still midi, not rendered to audio.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
When you save the session are the tracks still MIDI or have you rendered them to audio?
YES.
Do you record the snare and hats using the click track like you do the kick?
YES.
What’s your audio buffer setting? Usually 256, but been advised to reduce to 64 when tracking.
I have never seen what you’re describing even on a relatively low-powered system like in my sig file.
Me neither! I’m using a Mac Mini M4 Pro (64GB unified memory, 1TB SSD), and UAD Apollo 8 DAW. All sessions etc. are on external Samsung SSDs.
Try this: manually enter using PT’s MIDI editor a string of notes for the kick – something like 4 notes per measure at whatever tempo you like. Then do a second line for snare and a third line for the hats. Then hit play and see what happens. Do this first with everything MIDI and if that’s okay then render the MIDI to audio and try again. If this passes then the problem is not specifically with SD3. What I’m trying to do here is take the human (you) out of the loop and give SD3 the best possible input.
Will do, I’ll report back. Thanks.
Are you using any effects in SD3? Multi-out or 2 channel stereo? What SDX? Do you have the problem with every kick drum in the library?
No effects, 2 channel stereo. No SDX. And I’ll check the other kicks…
cheers,
BB.
Mac Mini M4 Pro (2024: 64 GB), OSX 15 (Sequoia), Pro Tools 2025, UAD Apollo 8, UAD-2 Quad Satellite DSP Accelerator, 2 x Lacie Thunderbolt SSD (250GB), Seagate Backup Plus Drive (4TB), Samsung T7 (4TB).
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.

