|
Post by johneppstein on May 2, 2019 11:42:19 GMT -6
Since installing our EMT140 about a year ago it gets used on just about everything. It has kind of an organic depth that plugins don't quite nail. Even without pre-delay vocals still remain in front of the verb much more than plugins seem to. The 480L doesn't get as much use as it used to especially on vocal plate duties but still fills a role mostly for wood room and ambience. Never quite managed to warm to the Bricasti. It sounds a bit kind of too perfect and polished to me which I find almost distracting for some reason. I'm jealous!
|
|
|
Post by johneppstein on May 2, 2019 11:56:49 GMT -6
I have a bunch of reverbs, the main ones being theRelab XL480, UAD EMT-140, Sound Toys Little Plate, Ocean Way, Oxide and some others in a Waves bundle, plus the very nice Logic reverb. But since I got the Liquid Sonics 7th Heaven, I barely use the others. I prefer clean over deep and dark, and contrary to most mixer’s advice, found using mainly one reverb gets me better results, or using mostly one verb on all tracks and a very small amount of the Relab here and there to widen it a little. *Svart, when you say “thin out”, do you mean you automate the EQ on a reverb to change at different places on a track? Sometimes, but in this case I meant more like cut masking frequencies. Much like any other track you can get too much buildup of low and upper mids that make things cloudy. I'd cut some stuff back in those areas so I can have more apparent overall reverb, but not make it a muddy mess. You can also do tricks like cut the reverb highs to make the instruments "sink" into the mix and such without actually changing levels or cutting EQ on the instrument/vocal itself. But yeah, delving into a lot of "mix with the masters" type of educational media, I've found that most of the pros heavily automate and EQ their reverbs. The hardware guys will bring the hardware returns back to normal mixer channels and do it there while the ITB guys will bus it and automate/EQ just like any other track. HMMmmm.... Since I haven't yet got the automation on my console to chase tape properly or sync with the daw (when playing back from the box instead - Soundcraft's screwy variant of RS-232 doesn't seem to be working as advertised) I don't currently use automation but I do mix my verbs dynamically (hands on faders). However I never thought of using EQ on the verb in a dynamic manner, will have to try it.
Thanks!
|
|
|
Post by jacobamerritt on May 2, 2019 12:02:42 GMT -6
Don't sleep on the SoundToys Little Plate.
|
|
|
Post by Blackdawg on May 2, 2019 12:37:55 GMT -6
When I got to use a EMT140, eqing/filtering the sends was VERY important. and also the return. Doing it right you can make the plate sound like a lot of different spaces or things. By far the best reverb.
|
|
|
Post by guitfiddler on May 2, 2019 13:42:07 GMT -6
I love my pcm70 on guitar and have used it on a snare in a heavy rock song. I would drive the input into the red and there is beauty and brilliance in that unit when you drive that input just right!!! Bricasti M7...Exponential Audio verbs and H-Verb. I prefer hardware usually, but I do use some plugs and sometimes blend to taste.
|
|
|
Post by mrholmes on May 2, 2019 15:07:06 GMT -6
I worry about a lot of plug ins but not reverb!
With reverb its different for me. In most cases it is already digital. Why should it be a problem to port this into the computer?
Coding all possible reactions of an 1176 for example seems to me the harder task. Correct me if I am wrong.
|
|
|
Post by Blackdawg on May 2, 2019 16:50:16 GMT -6
I worry about a lot of plug ins but not reverb! With reverb its different for me. In most cases it is already digital. Why should it be a problem to port this into the computer? Coding all possible reactions of an 1176 for example seems to me the harder task. Correct me if I am wrong. Not really wrong. But for me the hardware digital units still have their own A/D and D/A chips and they usually...well suck. Which imparts a sound in its own way which often is a important to the sound. Even so, when i use my M7s in digital mode so their is no conversion happening...they still sound better than any plugin I have. But thats more of a not all code is the same comparison.
|
|
|
Post by mrholmes on May 2, 2019 17:43:52 GMT -6
I worry about a lot of plug ins but not reverb! With reverb its different for me. In most cases it is already digital. Why should it be a problem to port this into the computer? Coding all possible reactions of an 1176 for example seems to me the harder task. Correct me if I am wrong. Not really wrong. But for me the hardware digital units still have their own A/D and D/A chips and they usually...well suck. Which imparts a sound in its own way which often is a important to the sound. Even so, when i use my M7s in digital mode so their is no conversion happening...they still sound better than any plugin I have. But thats more of a not all code is the same comparison.
To get some shit happening on the verb return I often use Airwindows Busscolors 3...DONE. Sounds a lot like my hardware verbs...
|
|
|
Post by svart on May 2, 2019 18:36:35 GMT -6
I worry about a lot of plug ins but not reverb! With reverb its different for me. In most cases it is already digital. Why should it be a problem to port this into the computer? Coding all possible reactions of an 1176 for example seems to me the harder task. Correct me if I am wrong. It's a case of the hardware reverb having dedicated DSP hardware and algorithms that are efficiently coded for that hardware, but to run those algorithms on a general purpose CPU would be very time and resource intensive and wouldn't be practical as a plug-in that needs to run in near real-time.
|
|
|
Post by rowmat on May 2, 2019 19:04:41 GMT -6
Here’s our ‘plug-in’ EMT-140 reverb. It ‘plugs-in’ to the 240VAC wall socket.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 2, 2019 19:08:33 GMT -6
It's a case of the hardware reverb having dedicated DSP hardware and algorithms that are efficiently coded for that hardware, but to run those algorithms on a general purpose CPU would be very time and resource intensive and wouldn't be practical as a plug-in that needs to run in near real-time. I'm afraid that's simply not accurate. I worked on a lot of those dedicated DSP chips and while they were the best that could be made at the time, they were crap. You had 16-18 bit accumulators, you had--even in the mighty 480L--an 8-bit multiply coefficient. All of that vaunted depth is really quantization error. Just pop a 30 hz sine wave into one and listen to the grinding. Even the best of the bunch could only conjure up 256 steps per sample and that was halved every time the sample rate was doubled. The only advantage for chips of 30 years ago was address generators that could sort of get around the problems of DRAM. As soon as you got to SDRAM and DDRAM, that problem went away. A properly-coded plugin can beat an HSP or Lexichip by a couple of orders of magnitude. The only difference in then and now is the algorithms. Algorithms for the old DSPs were written around those limitations and the compromises are audible. They were audible (and undesirable) to David Griesenger and they had the same problem for Barry Blesser. I could have done a spot-on emulation of any of the old Lex verbs, but I never wanted to. I had sounds in mind that those older boxes could never get to. And somebody's going to say the same about my stuff in 20 years. It's perfectly acceptable if you prefer the sound of an older device. Whatever floats your boat. You don't even have to conjure a rationale for it. I give a huge amount of credit to Barry and Dave for their serious brainpower. But if they'd had better processors, there's no way those verbs would have sounded the way they did.
|
|
|
Post by Martin John Butler on May 2, 2019 19:51:04 GMT -6
Great post Michael. It’s good to hear it from one of the sources!
this is probably why I’m preferring the Liquid Sonics 7th. Heaven to the Relab XL480 and the UAD EMT-140. Those plug-ins are emulating those old converters. It’s a cool sound, but I’m digging cleaner reverb sounds lately.
|
|
|
Post by bluegrassdan on May 2, 2019 20:42:44 GMT -6
I had a real EMT 140’s left channel crap out mid mixing, and we didn’t catch it until after we got home. Was glad to have Altiverb to put verb back into the left side.
That one also buzzed and needed recapped.
But repeatability is where plugins are exceptional. I love hardware gear while recording, but it can be a pain when you have mix revisions.
|
|
|
Post by svart on May 2, 2019 21:41:52 GMT -6
It's a case of the hardware reverb having dedicated DSP hardware and algorithms that are efficiently coded for that hardware, but to run those algorithms on a general purpose CPU would be very time and resource intensive and wouldn't be practical as a plug-in that needs to run in near real-time. I'm afraid that's simply not accurate. I worked on a lot of those dedicated DSP chips and while they were the best that could be made at the time, they were crap. You had 16-18 bit accumulators, you had--even in the mighty 480L--an 8-bit multiply coefficient. All of that vaunted depth is really quantization error. Just pop a 30 hz sine wave into one and listen to the grinding. Even the best of the bunch could only conjure up 256 steps per sample and that was halved every time the sample rate was doubled. The only advantage for chips of 30 years ago was address generators that could sort of get around the problems of DRAM. As soon as you got to SDRAM and DDRAM, that problem went away. A properly-coded plugin can beat an HSP or Lexichip by a couple of orders of magnitude. The only difference in then and now is the algorithms. Algorithms for the old DSPs were written around those limitations and the compromises are audible. They were audible (and undesirable) to David Griesenger and they had the same problem for Barry Blesser. I could have done a spot-on emulation of any of the old Lex verbs, but I never wanted to. I had sounds in mind that those older boxes could never get to. And somebody's going to say the same about my stuff in 20 years. It's perfectly acceptable if you prefer the sound of an older device. Whatever floats your boat. You don't even have to conjure a rationale for it. I give a huge amount of credit to Barry and Dave for their serious brainpower. But if they'd had better processors, there's no way those verbs would have sounded the way they did. You're not even addressing what I said. Comparing yesteryear DSP with a modern algorithm isn't a valid argument. Compare yesterday's DSP with a CPU of the same day, or compare today's DSP with today's CPU. In either case, nobody said that there weren't drawbacks in implementation either, nor did anyone say that a proper algorithm couldn't be done to sound amazing. I work with high speed DSPs in complex mod/demod scenarios daily and there's no way a CPU based algorithm running as a plug-in with latency considerations could touch DSP based processing in terms of speed and efficiency, and that's why we use DSPs even when we have powerful CPUs available to us. That's all I'm saying, you can't possibly make a plug-in be as efficient as it could be when you have to run it on a CPU with a billion other processes taking up time and resources. A dedicated DSP system could run circles around it.
|
|
|
Post by mrholmes on May 3, 2019 3:27:14 GMT -6
Great post Michael. It’s good to hear it from one of the sources! this is probably why I’m preferring the Liquid Sonics 7th. Heaven to the Relab XL480 and the UAD EMT-140. Those plug-ins are emulating those old converters. It’s a cool sound, but I’m digging cleaner reverb sounds lately. True its always fun to read about someone elses work. I also love videos about it. Special if its explained in easy words. Exp-Audio verbs are too long on my shortlist. I like them on the other side I am overhlemed with too many options.
|
|
|
Post by Guitar on May 3, 2019 7:11:14 GMT -6
My only hardware reverb is a Pioneer SR-101 spring reverb designed for home stereos, apparently they used this one on Amy Winehouse.
I prefer reverbs with analog character rather than digital algorithm sounding stuff. That or realistic room sounds.
Plugins are more than adequate for me. High end hardware reverb is something that's not even on my radar for the most part.
Like svart says in a lot of situations it almost doesn't even matter what brand or model you use. Snobbiness disappears in a lot of mix applications.
Although I do have a fantasy of owning a high end Eventide multi FX box.
EDIT: Beck has a great album called Morning Phase with a ton of reverbs. Apparently a lot of them were D-Verb plugins! Whatever works.
|
|
|
Post by EmRR on May 3, 2019 7:11:27 GMT -6
But repeatability is where plugins are exceptional. I love hardware gear while recording, but it can be a pain when you have mix revisions. The crux of the problem here. I don't use my real plates as much as I used to because of client demand for 300 tweaky mix revisions. I've tried printing the reverb to separate tracks, but the asks are somehow always something that requires a reprint of the reverb return.
|
|
|
Post by mrholmes on May 3, 2019 7:51:00 GMT -6
But repeatability is where plugins are exceptional. I love hardware gear while recording, but it can be a pain when you have mix revisions. The crux of the problem here. I don't use my real plates as much as I used to because of client demand for 300 tweaky mix revisions. I've tried printing the reverb to separate tracks, but the asks are somehow always something that requires a reprint of the reverb return.
As long as you create something with taste - who cares if it was a real palte or a plug in? THe modern sound is diffrent form the one 5 decades ago.
|
|
|
Post by EmRR on May 3, 2019 8:06:14 GMT -6
The crux of the problem here. I don't use my real plates as much as I used to because of client demand for 300 tweaky mix revisions. I've tried printing the reverb to separate tracks, but the asks are somehow always something that requires a reprint of the reverb return.
As long as you create something with taste - who cares if it was a real palte or a plug in? THe modern sound is different form the one 5 decades ago.
Yes. Unfortunately/fortunately the real plate sounds obviously better. I can turn a lead vocal off and only use the reverb return if I want, and it still sounds real, non-artificial, non-cheesy. I haven’t encountered a digital version that doesn’t fall apart to my ear past a certain volume level.
|
|
|
Post by subspace on May 3, 2019 8:15:28 GMT -6
I'm a plug-in early adopter, been running NuVerb for my big Lexicon sounds for a couple decades now. Looks like my serial MIDI interface is dead so dynamic MIDI automation is offline until I splash out on a serial MIDI timepiece...
I like Space and Space Designer for real spaces, Little Plate and Eventide 2016 for more color, but still hit my LXP-5s hard for that dirty DrkChrsVerb...
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 3, 2019 11:50:05 GMT -6
You're not even addressing what I said. Comparing yesteryear DSP with a modern algorithm isn't a valid argument. Compare yesterday's DSP with a CPU of the same day, or compare today's DSP with today's CPU. In either case, nobody said that there weren't drawbacks in implementation either, nor did anyone say that a proper algorithm couldn't be done to sound amazing. I work with high speed DSPs in complex mod/demod scenarios daily and there's no way a CPU based algorithm running as a plug-in with latency considerations could touch DSP based processing in terms of speed and efficiency, and that's why we use DSPs even when we have powerful CPUs available to us. That's all I'm saying, you can't possibly make a plug-in be as efficient as it could be when you have to run it on a CPU with a billion other processes taking up time and resources. A dedicated DSP system could run circles around it. Then I'll be more specific. The latency of all of the Exponential Audio plugins is 32 samples at 44/48. 64 samples at 88/96. And so on. In all cases, round-trip latency is under a millisecond. When I consider conversion time and buffering in and out of a hardware box, it's pretty close to equivalent (hardware might be a little slower). And as far as efficiency goes, there are dub-stages all over the world that set up templates with 2-3 dozen surround/3D versions of the plugins. These are typically running on cheese grater Macs that are also running Pro Tools with hundreds of tracks. I had one tester with 256 copies of PhoenixVerb on a trashcan Mac. And latency was still under a millisecond for all of them. It's absolutely true that some plugins (those based on convolution) would be much slower. But a hardware convolver has the same issues. Could I have this efficiency running the same old algorithms with the DSP chopped down to emulate a 25-year old device? Sure, but why bother. I worked with a lot of high-speed DSP processors myself back in the day, going back to bitslice machines and array processors. There may be a few very specific algorithms that still benefit from standalone DSP, but that number is shrinking. I appreciate your experience with high-speed DSP, but I know those old algorithms inside and out. They're elegant in their own way, but they're not particularly demanding of resources. If you know how to code efficiently and if you know how modern desktop processors work, there's no problem at all running dozens of them in a modern machine.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 3, 2019 11:55:48 GMT -6
I'm a plug-in early adopter, been running NuVerb for my big Lexicon sounds for a couple decades now. Looks like my serial MIDI interface is dead so dynamic MIDI automation is offline until I splash out on a serial MIDI timepiece... I like Space and Space Designer for real spaces, Little Plate and Eventide 2016 for more color, but still hit my LXP-5s hard for that dirty DrkChrsVerb... I'm impressed. NuVerb! I knew one guy who kept an old NuBus Mac going for years past its sell-by date, just so he could keep using NuVerb. It was basically a Lex 300, which was roughly half of a 480. Glad you've still kept an LXP-5 alive. Had one myself. Dirty was a pretty good way to describe it 16-bits all the way!
|
|
|
Post by johneppstein on May 3, 2019 12:50:50 GMT -6
When I got to use a EMT140, eqing/filtering the sends was VERY important. and also the return. Doing it right you can make the plate sound like a lot of different spaces or things. By far the best reverb. I have a Scamp Parametric module in my rack that is seriously underutilized - sounds like a perfect application for it if I ever get my hands on an EMT.
|
|
|
Post by johneppstein on May 3, 2019 13:08:26 GMT -6
You're not even addressing what I said. Comparing yesteryear DSP with a modern algorithm isn't a valid argument. Compare yesterday's DSP with a CPU of the same day, or compare today's DSP with today's CPU. In either case, nobody said that there weren't drawbacks in implementation either, nor did anyone say that a proper algorithm couldn't be done to sound amazing. I work with high speed DSPs in complex mod/demod scenarios daily and there's no way a CPU based algorithm running as a plug-in with latency considerations could touch DSP based processing in terms of speed and efficiency, and that's why we use DSPs even when we have powerful CPUs available to us. That's all I'm saying, you can't possibly make a plug-in be as efficient as it could be when you have to run it on a CPU with a billion other processes taking up time and resources. A dedicated DSP system could run circles around it. Then I'll be more specific. The latency of all of the Exponential Audio plugins is 32 samples at 44/48. 64 samples at 88/96. And so on. In all cases, round-trip latency is under a millisecond. When I consider conversion time and buffering in and out of a hardware box, it's pretty close to equivalent (hardware might be a little slower). And as far as efficiency goes, there are dub-stages all over the world that set up templates with 2-3 dozen surround/3D versions of the plugins. These are typically running on cheese grater Macs that are also running Pro Tools with hundreds of tracks. I had one tester with 256 copies of PhoenixVerb on a trashcan Mac. And latency was still under a millisecond for all of them. It's absolutely true that some plugins (those based on convolution) would be much slower. But a hardware convolver has the same issues. Could I have this efficiency running the same old algorithms with the DSP chopped down to emulate a 25-year old device? Sure, but why bother. I worked with a lot of high-speed DSP processors myself back in the day, going back to bitslice machines and array processors. There may be a few very specific algorithms that still benefit from standalone DSP, but that number is shrinking. I appreciate your experience with high-speed DSP, but I know those old algorithms inside and out. They're elegant in their own way, but they're not particularly demanding of resources. If you know how to code efficiently and if you know how modern desktop processors work, there's no problem at all running dozens of them in a modern machine. It really has very little to do with latency or the speed of the processor. It has to do with the code running on the machine language level, which is something that very, very few coders understand anymore - people who program in assembler or ML are rarer than hen's teeth these days, complex tasks are so much easier to program in higher level languages. I don't program myself but I started messing with computers back in the days when the 6502 processor was king and EVERYTHING had to be programmed in assembler/ML if you didn't want it to execute like a turtle, so I do understand the differences and compromises that are inherent in all high level languages.
In this case it's not really the speed per se but what the differrence in execution path does to the sound. I know I'm not expressing this very well. I know it sounds like "magical thinking" but it's not magic - it's just a level of science that's way beyond most normal thinking people - machine language guys are often rather strange ducks.
|
|
|
Post by svart on May 3, 2019 13:46:56 GMT -6
You're not even addressing what I said. Comparing yesteryear DSP with a modern algorithm isn't a valid argument. Compare yesterday's DSP with a CPU of the same day, or compare today's DSP with today's CPU. In either case, nobody said that there weren't drawbacks in implementation either, nor did anyone say that a proper algorithm couldn't be done to sound amazing. I work with high speed DSPs in complex mod/demod scenarios daily and there's no way a CPU based algorithm running as a plug-in with latency considerations could touch DSP based processing in terms of speed and efficiency, and that's why we use DSPs even when we have powerful CPUs available to us. That's all I'm saying, you can't possibly make a plug-in be as efficient as it could be when you have to run it on a CPU with a billion other processes taking up time and resources. A dedicated DSP system could run circles around it. Then I'll be more specific. The latency of all of the Exponential Audio plugins is 32 samples at 44/48. 64 samples at 88/96. And so on. In all cases, round-trip latency is under a millisecond. When I consider conversion time and buffering in and out of a hardware box, it's pretty close to equivalent (hardware might be a little slower). And as far as efficiency goes, there are dub-stages all over the world that set up templates with 2-3 dozen surround/3D versions of the plugins. These are typically running on cheese grater Macs that are also running Pro Tools with hundreds of tracks. I had one tester with 256 copies of PhoenixVerb on a trashcan Mac. And latency was still under a millisecond for all of them. It's absolutely true that some plugins (those based on convolution) would be much slower. But a hardware convolver has the same issues. Could I have this efficiency running the same old algorithms with the DSP chopped down to emulate a 25-year old device? Sure, but why bother. I worked with a lot of high-speed DSP processors myself back in the day, going back to bitslice machines and array processors. There may be a few very specific algorithms that still benefit from standalone DSP, but that number is shrinking. I appreciate your experience with high-speed DSP, but I know those old algorithms inside and out. They're elegant in their own way, but they're not particularly demanding of resources. If you know how to code efficiently and if you know how modern desktop processors work, there's no problem at all running dozens of them in a modern machine. Ok. Maybe I'm just overthinking it then and it must be very different in the audio world than the RF world. There's no chance I could use a general purpose CPU for what we do. In fact, sometimes we have to boil down pieces into hardware processing via FPGA/ASIC to get fast enough throughput. Even the last Bitcoin mining craze showed the limitations where you'd need a high end CPU and GPU to crunch as much data as a single purpose-built DSP engine in FPGA could. I'd still like to know why a hardware M7 machine sounds tons better than the plug-in IR's do.
|
|