So I have been using superior for years in protools and love it. I multi out raw drums in a custom kit I created all the time with no issues. Current protools 2020.11.0
Today, I loaded up a session that worked fine yesterday and as I armed the tracks to print I noticed a huge issue. I built this kit to have the shell bleed go to a oh cond track and cymbals (no shells) etc to a oh dynamic mic. Again I have had this build for months and never a issue.
I tried to deactivate all plugins (thinking it was latency), check routing disable routing, change to main output. I even made a new session…..I then noticed if everything in superior drummer goes out 1/2 no issue. When I multi out if I mute the oh condenser track where shells bleed is the kit sounds amazing. If that track(oh cond is not muted) is playing back god it sounds double hiton anything that is a shell and protools meter is showing two hits. (Checking a single snare hit with that mic channel unmuted it registers as two hits in master , when muted just one )
the funny thing once I print it into protools it plays back exactly how it should. I need to fix this sku I can properly monitor and build my kit with out the mute on the oh cond track (in protools or SD3)
I want to be clear I cleared all routing , checked for multi outputs etc( in superior and or protools). This randomly started in a session that was perfect yesterday. Any help would be nice sweetwater is calling toon track as they screen shared with me prior and can diagnose this either
What version of PT are you using? You may want to mention this over on the DUC if you haven’t already. You don’t have input monitoring on in PT by any chance? Is your MIDI coming from PT and if so check the MIDI event list for double hits or hits with a duration of zero.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Hey,
I am running protools studio 2020.11.0. Thank you for catching that I didn’t put that in. I updated my post!
Midi was written in protools like I always do. I usually always have input monitoring so I can hear the drums from superior in my multi out situation. I have never had this random issue it’s only the OH track causing the issue and I looked for double hits etc.
It’s a shame we can’t multi-quote posts but here’s some thoughts:
I run SD3 in PT 2021.6 in OSX 10.13.6 no problem. I know that theoretically that that combo of PT and OSX are not blessed by Avid but it works just fine. I use multi-out in SD3 but with a twist. I created a PT track preset that has SD3’s individual tracks routed to PT aux tracks that go to a drum bus. Also in the preset I have audio tracks that get routed to that same drum bus. When I’m done working on something and I want to render the audio I change the output of all those aux tracks that are getting SD3 outputs to the corresponding audio tracks. This way I don’t have to mess about with input monitoring or having audio tracks in record ready mode.
Let me get this straight – the MIDI in PT does not show double hits right? But you’re seeing doubles in PT’s track metering? What SD3 library are you using?
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Yes so the midi is perfect, work for this song 2 days ago no double hits etc. when I don’t have the ohs in n Superior muted the single shell hit shows as a double hit in protools metering
with oh muted I can print everything and it also sound fine on playbook after its rendered with it unmuted.
Something has changed and I don’t think it’s SD3 related. Do you have any sidechaining going on? Your version of PT doesn’t have delay compensation on sidechaining. Using any plugins that PT can’t handle regards delay compensation? What’s your buffer size? Again you may want to mention this on the DUC if you haven’t already. You haven’t answered another question I asked and that is which library are you using in SD3?
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
My protools has delay comp on, I also did completely kill every plug in on the session and re did all routing to ensure that was not the issue
to answer your question it happens with all libraries, and any preset if I use multi out
i am currently just in the fire library of superior drummer 3.
I use an apollo twin, buffer size I have changed multiple times to check that. I keep it at 512 no issues for the last year.
if you want to zoom lol I be happy to show you and it send you a small video clip ? I know this is a weird issue, I tried everything you mentioned as well because I was hoping I just bumped something.
Hi happy_5,
please zip your .ptx (just the session file, no audio) and attach to a post here, so we may have a look at it.
BR,
John
John Rammelt - Toontrack
Technical Advisor
1
Thanked by: happy_5To clarify you want me to send you a copy of my session and not include audio files correct? Would you also like me to send screenshots of my Kit I made and or share my preset? I use the multi out FT, the issue only happens when the Overhead mics are being monitored in multi out. The printing and playb back after committed is perfect.
I just want to give you all the info so you can see my routing in protools and also in SD3, I have never had this issue since I owned the plug in and the routing has not changed.
Thank you for helping me!
I’d like to attach the PT track preset I use to try and help the OP but the forum s/w won’t allow the .ptxp file extension. How do I remedy that?
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
To clarify you want me to send you a copy of my session and not include audio files correct? Would you also like me to send screenshots of my Kit I made and or share my preset? I use the multi out FT, the issue only happens when the Overhead mics are being monitored in multi out. The printing and playb back after committed is perfect.
I just want to give you all the info so you can see my routing in protools and also in SD3, I have never had this issue since I owned the plug in and the routing has not changed.
Thank you for helping me!
Yes, just the .ptx file zipped. In the Session, the SD3 Instrument track with all routing should be saved but if you wish to provide additional info like screenshots, please go ahead.
BR,
John
John Rammelt - Toontrack
Technical Advisor
I’d like to attach the PT track preset I use to try and help the OP but the forum s/w won’t allow the .ptxp file extension. How do I remedy that?
Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)
Hi, you have to ZIP archive it first, to be able to attach it.
BR,
John
John Rammelt - Toontrack
Technical Advisor
I’d like to attach the PT track preset I use to try and help the OP but the forum s/w won’t allow the .ptxp file extension. How do I remedy that?
Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)Hi, you have to ZIP archive it first, to be able to attach it.
BR,
John
Thanks but this should be notated somewheres on the website.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Here’s the PT track preset I use for SD3 and Death from Death and Darkness. I use PT 2021.6.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.1
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
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.