No products in the cart.
Jason Moore LAc
Participant
Topics Started: 3
Replies Created: 8
Has Thanked: 10
Been Thanked: 2
Section 9.4.1 in the user manual details how to do this. It even says “…..
Sounds like exactly what you’re looking for.
I’m unclear on if you can do everything on one channel or if you will have to create a separate channel for each cymbal and then create a cymbal BUS from there… but either way…. Looks like it can be done.
I like the Izotope exciter from Ozone better than the Waves one. But…. you can demo Waves and check for yourself risk free 😉
1
Thanked by: bobbyharlowI’m not sure (because I’ve never done it) but I would think you could use one of your user channels and just route which mics you want to to it (in your case just whichever cymbals you want). Or….. if you just want the cymbals and nothing else in the over heads you could just turn the bleeds off for all of the instruments in the overheads except the cymbals (that I know would work…. unless you specifically want both channels). I’m sure it can be done though…. try out routing specific mics to one of your 6 available user channels. 😉
I agree that the Tom’s are the most difficult to dial in. I also agree with Scott. Use Parallel compression!!!!!!
Also… I find that one of the biggest necessities for SD to sound real is to use your mic bleeds. ALL OF THEM, but especially ambient mics and surround mics (even if you’re not mixing surround sound). I had to buy a new MacBook so that I can properly use SD and it even pushes it to 120 degrees and runs the fan constantly because my tracks are running 7-8 gigs of data and 20-30 gb of RAM (luckily I got a machine with 64).
That and the right parallel compression (with an eq after the compressor) has everyone saying “damn, your drums sound amazing”. Also….. of course.. experimenting with lots of different drum sets / pieces
1
Thanked by: bobbyharlowI’ve noticed the same thing. Was just too lazy to post anything about it.
I just tried your suggestion of switching libraries. No…. it did not fix it.
Another thing I’ve noticed… If you switch to 16 bit when you close and then reopen it’s back to 24 bit and you have to switch it back again. Is it supposed to be that way? Yes, I press “save” on the preset prior to closing. I’m using Studio One. But it happens in stand alone too.
Thank you!
Thank you for this, Erik.
I just used it as an excuse to get a faster Macbook
I’ve already invested about $2,000 in EZD, SD3, EZX, SDX, MIDI Packs….. I’m not holding back now because of a RAM Issue 😛
Seriously though… Thanks again. I love the support and willingness to work with the user of Toontrack and the community in the forums. It’s great!
Cool. Thank you for doing that, Brad!
Unfortunately no. The machine I am using was upgradable to 16gb but only at purchase. They soldered the RAM to the logic board and it is forever 8 GB. I could theoretically get a new (used) logic board that has 16 GB on it but at that point I would rather just get a new computer.
It sucks….. but I’m a little comforted to have a good idea of what’s going on rather than keep chasing possibilities. I kind of figured that was it and have been pricing new MacBooks but I wanted to make sure it wasn’t something more simple.
Thank you again for all your help! This forum (and software) rocks!
Thank you both for replies.
On further inspection I am also now noticing this. FONTD issue is not there. Now it is Kernal Task. Looking further into it it is something that diverts resources away from CPU hogging programs as the computer heats up.
So…. I am using Studio One.
I am also looking in Activity monitor.
With this track running, CPU shows SD3 taking up about 12-20%, Studio one over 100% and the Kernal task over 100%. This is causing the glitching.
So…. I disabled VST, AU, etc…. in Studio One and turned them all on one at a time. The problem is in either (and both) VST and AU. Now….. SD is what is running on those. But why does it take the Studio One CPU usage from about 30% if I turn them off to over 100%. SD3 usage doesn’t change…. but I know for a fact the increase in Studio 1 usage is due to SD3.
I have installs in AU as well as VST but have read on Toontrack that that should not matter. I also tried running the track via only AU (with VST disabled) and vice versa. CPU usage was the same.
I have gone through Studio one advice as well… but the increased CPU usage is due to SD3. Why though does CPU usage of SD3 hover at around 20% but it increases Studio One usage from 30-40% to over 100%?
Again….. this is only on one track with bleeds and surrounds activated. Other tracks without surrounds do not have this problem.
This is a head scratcher. I’d hate to buy a new $3,000 computer just to use surrounds…. but if I have to I will.
It seems to me something is just not jiving that can be figured out.
Thanks again for earlier replies!
No products in the cart.