|
Post by kcatthedog on Mar 5, 2024 18:11:34 GMT -6
I think hybrid, track with ob, mix with plugs, use OB on 2 bus, currently simple: just ssl clone, but a certain pultec stereo eq with mid is whispering sweet everythings !
|
|
|
Post by Quint on Mar 5, 2024 18:30:58 GMT -6
I recall reading that you have enough hardware where you're able to leave most of the settings as they are. Those 76s are set for a purpose, and if you need that purpose, you patch in. Is that right? Essentially yes. But it does get more convoluted than just that. I have enough gear to pretty much get what I want, and it not, I'll use a combo of hardware and plugins. All tracks in my sessions are in "input" until finalized. Where it gets tricky is stepping rearwards from the end product to : - Final Mix (at unity); to - Stems (at unity); to - Printed contiguous "Final" tracks all at unity with printed automation and hardware; to - Automated "Mix" tracks with non-printed (software) automation, inserts, FX, EQ, etc.; to - Pre automated mix, midi & VI tracks (if used); Once my mix is "finished", Ill print the printed final tracks, stems, and final mix all in one pass. For a recall : So a simple automation recall may only require me to go back one step, two steps or all the way 5 steps back. If a tweak on the stems won't get it, I can go back to my printed (post FX/Automation/etc) tracks. If it's a massive change that requires completely doing something radically different, then I go back to my automated mix tracks. If it's something like a re-write and remix, then I can go back all the way to Midi and VI tracks if used, or call back musicians. Where PTHDX rules in this scenario is it's incredibly robust. It's quite elegant once laid out, but requires a TON of DSP mixing power. This is why I need multiple hundreds of internal busses.... All of those busses have to eventually stack up on latency, no? A buss into a buss into a buss into a buss....
|
|
|
Post by geoff738 on Mar 5, 2024 18:35:01 GMT -6
If I had the budget and the space and the electrical outlets, and hvac to deal with the heat generated, yeah I’d go hardware all the way. But I don’t, so I don’t.
I guess I’m hybrid to an extent. I have some quality compressors, but mostly mono, and my singular eq is ok but not great, and I’m not sure my other outboard would beat out plugins (time based stuff).
Cheers, Geoff
|
|
|
Post by enlav on Mar 5, 2024 18:39:55 GMT -6
All of those busses have to eventually stack up on latency, no? A buss into a buss into a buss into a buss.... Never worked on a system of DrBills scale, but on some old HD cards with 192s or 96s, as long as you weren't running RTAS between the myriad of busses, the latency wasn't usually enough to go beyond what PTHD's delay comp could deal with. Not sure how that has changed in modern HDX, but bussing itself seemed efficient.
|
|
|
Post by seawell on Mar 5, 2024 18:46:11 GMT -6
It truly grieves me that our industry no longer uses the best tools available. At the same time, I don't blame anyone because the financials just usually don't make sense any longer. I think the greatest argument in the hardware vs plug-in debate is how many "A-List" mixers have sold off their outboard and went all ITB because they "finally figured it out"....their mixes from that point on would beg to differ 🤣. Don't get me wrong, a VERY good ITB mix can be done these days but something truly great, something that pushes me to want to figure it out and get better as an engineer myself...sorry but I haven't heard it and I've sought it out many times hoping to justify selling all this gear!
|
|
|
Post by drbill on Mar 5, 2024 18:56:51 GMT -6
Essentially yes. But it does get more convoluted than just that. I have enough gear to pretty much get what I want, and it not, I'll use a combo of hardware and plugins. All tracks in my sessions are in "input" until finalized. Where it gets tricky is stepping rearwards from the end product to : - Final Mix (at unity); to - Stems (at unity); to - Printed contiguous "Final" tracks all at unity with printed automation and hardware; to - Automated "Mix" tracks with non-printed (software) automation, inserts, FX, EQ, etc.; to - Pre automated mix, midi & VI tracks (if used); Once my mix is "finished", Ill print the printed final tracks, stems, and final mix all in one pass. For a recall : So a simple automation recall may only require me to go back one step, two steps or all the way 5 steps back. If a tweak on the stems won't get it, I can go back to my printed (post FX/Automation/etc) tracks. If it's a massive change that requires completely doing something radically different, then I go back to my automated mix tracks. If it's something like a re-write and remix, then I can go back all the way to Midi and VI tracks if used, or call back musicians. Where PTHDX rules in this scenario is it's incredibly robust. It's quite elegant once laid out, but requires a TON of DSP mixing power. This is why I need multiple hundreds of internal busses.... All of those busses have to eventually stack up on latency, no? A buss into a buss into a buss into a buss.... I never think about it. I just hit "delay compensation" and move on. It figures out if I have an insert on a path, native plugin, DSP plugin, whatever convoluted path I might have to come up with to get the job done. I have not seen anything else that gives me that kind of power and reliability. I will admit to pushing my DAW to the edge.
|
|
|
Post by Dan on Mar 5, 2024 18:57:06 GMT -6
It truly grieves me that our industry no longer uses the best tools available. At the same time, I don't blame anyone because the financials just usually don't make sense any longer. I think the greatest argument in the hardware vs plug-in debate is how many "A-List" mixers have sold off their outboard and went all ITB because they "finally figured it out"....their mixes from that point on would beg to differ 🤣. Don't get me wrong, a VERY good ITB mix can be done these days but something truly great, something that pushes me to want to figure it out and get better as an engineer myself...sorry but I haven't heard it and I've sought it out many times hoping to justify selling all this gear! The transients are so very wrong on every digital dynamics processor without a proper lookhead to smooth the attack or upsampling the detector to almost the mHz.
|
|
|
Post by Quint on Mar 5, 2024 19:12:17 GMT -6
All of those busses have to eventually stack up on latency, no? A buss into a buss into a buss into a buss.... I never think about it. I just hit "delay compensation" and move on. It figures out if I have an insert on a path, native plugin, DSP plugin, whatever convoluted path I might have to come up with to get the job done. I have not seen anything else that gives me that kind of power and reliability. I will admit to pushing my DAW to the edge. I get that it all gets delay compensated, and is still lined up with itself, but delay is still delay. So, for example, do you ever find that, when you're doing something like automation fader rides, that there is a discernible difference between what you're hearing and where the automation move actually is recorded on the timeline?
|
|
|
Post by Shadowk on Mar 5, 2024 19:54:24 GMT -6
It truly grieves me that our industry no longer uses the best tools available. At the same time, I don't blame anyone because the financials just usually don't make sense any longer. I think the greatest argument in the hardware vs plug-in debate is how many "A-List" mixers have sold off their outboard and went all ITB because they "finally figured it out"....their mixes from that point on would beg to differ 🤣. Don't get me wrong, a VERY good ITB mix can be done these days but something truly great, something that pushes me to want to figure it out and get better as an engineer myself...sorry but I haven't heard it and I've sought it out many times hoping to justify selling all this gear! In a roundabout way you pretty much said the exact same as me, even though I think we can get a bit too wrapped up in this stuff there's an annoying realisation that I've essentially gone back to where I were decades ago. The reason I gave that up is cost, convenience and all the benefits that a one interface solution brings but with the mini HDX and HW track I can't believe how easy it's become once again to get where I need to go. I had to spend the time and money to either finally disregard it, shrug my shoulders and say not worth it or stay the course.
You'd think after the journey I'd be happy now that it's all come together but actually I'm a bit miffed, IME it's either a lot of money or a good fight to get to the stage where sonic's aren't in question and it's purely down to talent.
|
|
|
Post by Johnkenn on Mar 5, 2024 20:08:49 GMT -6
Nice, but how do you handle recalls?
For me it's pretty simple. But to write it all out would kind of take a small book. I've got it dialed in after years of experimentation though. Recall for me is virtually as fast as an ITB recall. But you’re tracking your own stuff, right? It always stays set the same?
|
|
|
Post by nobtwiddler on Mar 5, 2024 20:27:03 GMT -6
Every few years, I do the ITB to mixer comparison test, just to do it, and see where things have come.
I usually use simple Americana rock tracks, (mostly what I do) that are 24 tracks or less. My guidelines are simply that I will use the exact same gear as inserts, on both the ITB box mix, and the Console mix!
If I don't have the same plugs, as my outboard, or vice a versa, then I don't use them. This way a direct (or close to it) comparison can be made.
As I said, these are very straight ahead mixes, with not a lot of junk on them.
I start with the ITB box mix, and I usually spend a day on it, and return to it in the morning, to make sure it's as good as I want it. And to be honest, I'm usually very happy with the results.
Once that's done, I'll start from scratch, buss everything out to the console (or my summing setup, which I've done both) insert the outboard as it was on the ITB mix, set all gear as it was in the other mix, and go....
Once again, no rush, I mix for a day, take my time, and return to it to print the next morning. I print it, and then do the comparisons.
As good as I thought the ITB mix sounded, once played against the Console version, there is NO COMPARISON! It's inevitable that the Console version, not only sounds bigger, wider, and just plain better, it also FEELS better! I think it's more visceral, emotional, makes ya wanna move, tap your feet, etc...
At least this is my findings, and I've done this almost every year for about 8 years now.
|
|
|
Post by robo on Mar 5, 2024 21:30:18 GMT -6
My solution is to run important busses and tracks through hardware, usually leaving the mixbus processing ITB. I print once the main elements are gelling, and then sometimes there’s some light processing after the analog printing. I find that’s enough for me to get the benefits while still having easy recalls.
My mixes usually start with a quick rough with plugins, which helps me decide what hardware to patch in. Maybe 20% of the time the plugins beat the analog chain and I just leave it. This is usually when I made bolder moves while tracking and not much is needed.
|
|
|
Post by copperx on Mar 5, 2024 21:58:10 GMT -6
I never think about it. I just hit "delay compensation" and move on. It figures out if I have an insert on a path, native plugin, DSP plugin, whatever convoluted path I might have to come up with to get the job done. I have not seen anything else that gives me that kind of power and reliability. I will admit to pushing my DAW to the edge. I get that it all gets delay compensated, and is still lined up with itself, but delay is still delay. So, for example, do you ever find that, when you're doing something like automation fader rides, that there is a discernible difference between what you're hearing and where the automation move actually is recorded on the timeline? I want to know this too. The most annoying thing about latency is that it makes writing automation so complicated. I need to hear my fader moves almost in real time, not 100 ms after. That's why I try to use 0 latency plugins everywhere and no plugins on buses. I'd love to know how this works on ProTools HDX. If there's no discernible delay, I might even consider switching to ProTools and buying an HDX card.
|
|
|
Post by wiz on Mar 5, 2024 22:18:40 GMT -6
Every few years, I do the ITB to mixer comparison test, just to do it, and see where things have come. I usually use simple Americana rock tracks, (mostly what I do) that are 24 tracks or less. My guidelines are simply that I will use the exact same gear as inserts, on both the ITB box mix, and the Console mix! If I don't have the same plugs, as my outboard, or vice a versa, then I don't use them. This way a direct (or close to it) comparison can be made. As I said, these are very straight ahead mixes, with not a lot of junk on them. I start with the ITB box mix, and I usually spend a day on it, and return to it in the morning, to make sure it's as good as I want it. And to be honest, I'm usually very happy with the results. Once that's done, I'll start from scratch, buss everything out to the console (or my summing setup, which I've done both) insert the outboard as it was on the ITB mix, set all gear as it was in the other mix, and go.... Once again, no rush, I mix for a day, take my time, and return to it to print the next morning. I print it, and then do the comparisons. As good as I thought the ITB mix sounded, once played against the Console version, there is NO COMPARISON! It's inevitable that the Console version, not only sounds bigger, wider, and just plain better, it also FEELS better! I think it's more visceral, emotional, makes ya wanna move, tap your feet, etc... At least this is my findings, and I've done this almost every year for about 8 years now. Would love to hear the comparison if possible... cheers Wiz
|
|
|
Post by seawell on Mar 5, 2024 22:19:17 GMT -6
I use a D-Control control surface with Pro Tools HDX and I don't notice any delay when writing automation/doing fader rides. I haven't thought about how that's compensated for, it just always worked so I never really noticed. Hopefully someone here can explain...I'm curious now haha.
|
|
|
Post by Quint on Mar 5, 2024 22:27:42 GMT -6
I use a D-Control control surface with Pro Tools HDX and I don't notice any delay when writing automation/doing fader rides. I haven't thought about how that's compensated for, it just always worked so I never really noticed. Hopefully someone here can explain...I'm curious now haha. Well it's probably not usually much of an issue, but DrBill said he had over 700 busses, so the thought had occurred to me that that amount of routing might actually create a noticeable latency offset for things like automation. So it made me curious how he was dealing with that.
|
|
|
Post by seawell on Mar 5, 2024 22:31:10 GMT -6
I use a D-Control control surface with Pro Tools HDX and I don't notice any delay when writing automation/doing fader rides. I haven't thought about how that's compensated for, it just always worked so I never really noticed. Hopefully someone here can explain...I'm curious now haha. Well it's probably not usually much of an issue, but DrBill said he had over 700 busses, so the thought had occurred to me that that amount of routing might actually create a noticeable latency offset for things like automation. So it made me curious how he was dealing with that. Gotcha…yeah I can’t say I get anywhere near that number of busses 😁. Let us know Dr. Bill!
|
|
|
Post by copperx on Mar 5, 2024 23:02:21 GMT -6
I use a D-Control control surface with Pro Tools HDX and I don't notice any delay when writing automation/doing fader rides. I haven't thought about how that's compensated for, it just always worked so I never really noticed. Hopefully someone here can explain...I'm curious now haha. Well it's probably not usually much of an issue, but DrBill said he had over 700 busses, so the thought had occurred to me that that amount of routing might actually create a noticeable latency offset for things like automation. So it made me curious how he was dealing with that. 700 buses? Now I'm really curious. My system begins to add latency with 5-10 buses, even with zero latency plugins. Some buses cascade into other buses, which I assume are processed in series, not parallel. I think I might need to move to Pro Tools. Maybe I've been suffering for no reason.
|
|
|
Post by Quint on Mar 5, 2024 23:13:12 GMT -6
Well it's probably not usually much of an issue, but DrBill said he had over 700 busses, so the thought had occurred to me that that amount of routing might actually create a noticeable latency offset for things like automation. So it made me curious how he was dealing with that. 700 buses? Now I'm really curious. My system begins to add latency with 5-10 buses, even with zero latency plugins. Some buses cascade into other buses, which I assume are processed in series, not parallel. I think I might need to move to Pro Tools. Maybe I've been suffering for no reason. Whether it's DSP or native, one buss into another is a process in series. If each step in that series incurs a latency hit, and if you do it enough times, it seems like it would add up, irrespective of whether or not you're doing this on DSP or native, so I have questions...
|
|
|
Post by wiz on Mar 6, 2024 0:02:21 GMT -6
700 busses……
How many tracks?
|
|
|
Post by vvvooojjj on Mar 6, 2024 1:42:12 GMT -6
Clients want revisions on mixes quite often, which is why I work ITB. And also I don't mind the sound. And I've been mastering ITB for some time and don't get any more revisions than with hardware (almost zero).
I compared ITB (various plugins into a limiter) and OTB 2-bus chain (2500 into Thermionic Swift and then into a limiter) for some electronic music I've been doing (techno). Yesterday ITB won and last week it was 50/50. I'm able to compress more with hardware and do more creative settings but that isn't always needed. The UAD 2500 shXt compared to the hardware, a completely different action and of course the sound. I'd like to test some super clean opamps for the 2500 at some point. I have the ones from API at the moment.
|
|
|
Post by Blackdawg on Mar 6, 2024 1:57:06 GMT -6
I never think about it. I just hit "delay compensation" and move on. It figures out if I have an insert on a path, native plugin, DSP plugin, whatever convoluted path I might have to come up with to get the job done. I have not seen anything else that gives me that kind of power and reliability. I will admit to pushing my DAW to the edge. I get that it all gets delay compensated, and is still lined up with itself, but delay is still delay. So, for example, do you ever find that, when you're doing something like automation fader rides, that there is a discernible difference between what you're hearing and where the automation move actually is recorded on the timeline? Nope. Always in line. Always works. Never think about it.
|
|
|
Post by Blackdawg on Mar 6, 2024 1:59:46 GMT -6
700 busses…… How many tracks? remember a bus isn't always a track. It might go to a track or multiple. You can mult outputs in Protools and sends as well and returns. It's basically anything with a voice. So you can quickly get over 100-200 of those in a biggish session plus all the matrixing to have his prints saved of each phase of the mix. I'm sure Bill was over joyed when folders became a thing ha
|
|
|
Post by thehightenor on Mar 6, 2024 2:59:07 GMT -6
Just as a theoretical question...In your opinions, can software "achieve the same results as HW - it just might take longer and more effort?" Or is it intrinsically inferior and the same results can't be achieved? I'm still a HW sounds better kinda guy, e.g. - While interface pres and software emus come close, I still prefer the HW pres. The complicating factor is the stacking of tracks. The modeled pres can sound really good, but I do think there are differences especially when you're stacking. But I guess that's not really sticking to my mixing question and more about tracking. Comps/EQ - there's still a more demonstrative attack with HW comps. Or at least that's what I think the issue is. But I have a much, much harder time telling a difference between HW and SW EQs. I have had the experience that HW EQ's sound more natural in the top end - like you can go to more extremes without it getting weird. Is that a Samplerate thing? Aliasing? IDK. It just occurred to me: Good is good. If a SW mix sounds inferior, why can't you just mix it until it doesn't sound inferior? They're supposedly the same tools, right? Here's an analogy (probably a convoluted one) I know when I first started using Luna, I was using the Neve "summing" and I felt like Luna might sound a little better than other daws. Once I heard that, I was able to work that into Pro Tools with a little more push with Slate VCC or Noise Ash N-Console. HW can be similar - sometimes you put something in the chain and it "just works." What I've found is that I can get plugins to be very similar...the advantage to HW being, I didn't have to futz with it as much. That's awesome - but brings me back to my original question: Can the same results be achieved? It makes me wonder about the most important thing in our whole chain - monitoring. If you can hear everything, why can't you mold it into the same result? Like - instead of hardware, why not invest in high end monitoring and DA instead of HW comps and EQs? I don't know the answer - just asking opinions. John, can you hear a difference? Can you get the same results? That’s all that’s going to count at the end of the day. For me personally, hardware is way way sonically superior. Just putting my Thermionic Phoenix MP Vari—mu and Swift tube EQ across the stereo mix bus and mixing into that, takes me into a sonic world of wonder plug-ins can’t even begin to enter imho So I use heaps of hardware (in growing number!) This subject is incredibly subjective, and then there’s space, money, power, heat, workflow. There’s a lot to consider in making this choice.
|
|
|
Post by niklas1073 on Mar 6, 2024 4:25:47 GMT -6
I think hybrid, track with ob, mix with plugs, use OB on 2 bus, currently simple: just ssl clone, but a certain pultec stereo eq with mid is whispering sweet everythings ! Yes I agree, this is exactly how I am set up. But I would not call it hybrid, I still consider myself as itb mixing when it’s eventually only the tracking and final print that passes hw. But i think this represents the best of both worlds in a way. You will achieve a very analog sound but have the full convenience of itb mxing. For clients it works too. When they hear the mix first and are happy and then you turn on the 2bus and the deal is sealed 🤣. Regarding recall that has been earlier mentioned in the thread. I’ve noticed pretty much all my hw despite a limited collection don’t change settings much at all. I mainly use the bypass on/off switch on them with minor tweaks at times. But then again, they are not the most versatile units but rather vintage inspired one trick ponies.
|
|