Multi out issue with OH

[happy_5]

So I have been using superior for years in protools...

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

Superior Drummer 3 version: 3.3.6
Operating system: macOS Mojave (10.14)

• This post was modified 1 year, 12 months ago by happy_5.

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

Superior Drummer 3 version: 3.3.6
Operating system: macOS Mojave (10.14)

• This post was modified 1 year, 12 months ago by happy_5.

Topic

[happy_5]

Here you go I deleted everything but the Drums, please let me know what you find!

[happy_5]

John as I review the session it is the oh and all the rooms that are having issue on play back,

[drumjack52]

happy_5 wrote:

Here you go I deleted everything but the Drums, please let me know what you find!

I’m seeing routings in the SD3 mixer that aren’t all that straightforward. What you sent is not in multi-out but in 1/2. Not to mention all the errors that kick up because of PT routings because of I/O I don’t have. Then there’s that business with virtual outputs – what’s that all about? I’m not surprised you’re having issues. Try a PT session with just SD3 and nothing else then report back what you get. Also did you try the track preset I posted?

Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)

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

[happy_5]

the routing is straight forward example kick in 3/4( SD3) is routed to the input of kick in in protools 3/4 etc. The superior Drummer tracks in solo are the only things multi out that all have the corresponding input in protools. Unless when you open the session it didn’t save the routing in superior Ill send a screen shot to demo its so weird I made a new session for a new client and it works but the other sessions are broken…. Also virtual is probably the default routing for the UA apollo.

[happy_5]

your attachment just opened a text file when I downloaded it.

[drumjack52]

happy_5 wrote:

your attachment just opened a text file when I downloaded it.

Did you expand it? Double click on it to expand it.

Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)

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

[drumjack52]

happy_5 wrote:

the routing is straight forward example kick in 3/4( SD3) is routed to the input of kick in in protools 3/4 etc. The superior Drummer tracks in solo are the only things multi out that all have the corresponding input in protools. Unless when you open the session it didn’t save the routing in superior Ill send a screen shot to demo its so weird I made a new session for a new client and it works but the other sessions are broken…. Also virtual is probably the default routing for the UA apollo.

The session you sent did not open with SD3 in multi-out. It opened in stereo output. Then I noticed you have two instances of SD3 – why? You don’t know what the virtual outputs are? There’s something definitely wrong in this session and it isn’t the fault of SD3 if a new session works just fine.

Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)

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

[happy_5]

That’s weird Deff is multiout and printed through pt. The virtual outputs are part of universal audio outputs they are not needed. It’s hard to explain unless you know about the Apollo twin or x units. Nothing routes there unless you set it up

 

the other superior drummer was there when I was trying to diagnose the problem but the plug in is off and killed it has nothing to do with the issue and is not valid in the session just didn’t delete the track(the plug in inactive

 

it works in a random sessions but sometimes it does not Deff a issue but again for years this method has worked something else is at fault here

[drumjack52]

happy_5 wrote:

That’s weird Deff is multiout and printed through pt. The virtual outputs are part of universal audio outputs they are not needed. It’s hard to explain unless you know about the Apollo twin or x units. Nothing routes there unless you set it up

 

the other superior drummer was there when I was trying to diagnose the problem but the plug in is off and killed it has nothing to do with the issue and is not valid in the session just didn’t delete the track(the plug in inactive

 

it works in a random sessions but sometimes it does not Deff a issue but again for years this method has worked something else is at fault here

That things work in other sessions and the newly created one you did for a client means (and I repeat) that it’s not a fault of SD3. And I repeat again – create a session with nothing but SD3 in it maybe using the track preset I posted here. To clarify on the track preset I posted you do NOT open it like you would a normal PT session. Do you know how to use track presets? It’s mentioned in the user’s guide aka The Manual. Here’s a link to one of many articles that describes track presets and their use: https://www.protoolstraining.com/blog-help/pro-tools-blog/tips-and-tricks/471-track-presets-in-pro-tools.html  and here’s a YouTube video on track presets: https://www.youtube.com/watch?v=OVt11H07b5I

You’re going to have to deconstruct your session on your own. The simplest though is to start a new session using only the bare necessities and go from there.

Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)

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

[happy_5]

John any word ?

[drumjack52]

happy_5 wrote:

John any word ?

I don’t think John can do any more than I did. I already gave you ideas on how to figure out where the problem really is. One of the mantras when troubleshooting is: simplify simplify simplify. Start with a basic session with SD3 and nothing else and go from there adding bits and bobs and see where it barfs.

I’ve asked this many times and you haven’t answered it: have you posted about this on the DUC? Also have you really tried the track preset I posted? I gave you info on how to use it with a couple of links.

Superior Drummer 3 version: 3.3.6
Operating system: macOS High Sierra (10.13)

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

[John]

Hi,

apologies for the delay but I initially missed your reply, I must have missed the notify box.

I am not sure why you have all those channels Solo’ed in the SD3 mixer and a bunch of unused X-channels hidden in your mixer?
If I’m not mistaken, the stacked snare is not routed to any microphone channel?
Anyways, I digress, the problem lies with the Delay Compensation in Pro Tools and how you have routed the signals. As it is now, the ‘oh shells’ audio arrives earlier than the rest of the kit.
Just select the ‘oh shells’ channel in the PT mixer, right-click the ‘cmp’ text below the fader and click ‘Auto Low Latency Off’.
If you don’t see it, Enable Delay Compensation in the Mix Window View Selector. This should solve the problem monitoring while building the song.

I hope this helps,
John

John Rammelt - Toontrack
Technical Advisor

2

Thanked by: Brad and drumjack52

[Author]

Replies