John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 12:47:48
(permalink)
Q is a dimensionless value. This means that it is always expressed as a value between 0 and 1 (inclusive). The idea that the Q *number* should change if the Q is variable width is utterly, utterly wrong. You could argue that some form of labelling that indicated the variation of the width would be good, but 1/ that wouldn't be Q, and 2/ the graph shows that, so it would be a bit redundant.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 12:56:16
(permalink)
I note that Sonar maps this to a scale between 0.1 and 16 or whatever reason, but the principle is the same. A Q of 1 (or 16) at Xdb is whatever it is. A Q of 1 (or 16) at Ydb is whatever it is, dependent on the rest of the system. If have max Q at +3db, and the I boost that +6db, I'm still at "max Q". Max Q doesn't get wider, the thing it's *describing* gets wider.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
Rimshot
Max Output Level: -29 dBFS
- Total Posts : 4625
- Joined: 2010/12/09 12:51:08
- Location: California
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 13:49:22
(permalink)
Mike, I see your point but if suddenly all Q values were as you would like to see them, it would make no difference to how I use it. I have to go by the the audio sound regardless. I wonder how many people would be helped if the Q value was normalized for all plugs? I really learn from your comments and suggestions so don't get me wrong it's just that there may be many like me that don't get into that level of detail by numbers compared to the sound itself. Rimshot
Rimshot Sonar Platinum 64 (Lifer), Studio One V3.5, Notion 6, Steinberg UR44, Zoom R24, Purrrfect Audio Pro Studio DAW (Case: Silent Mid Tower, Power Supply: 600w quiet, Haswell CPU: i7 4790k @ 4.4GHz (8 threads), RAM: 16GB DDR3/1600 , OS drive: 1TB HD, Audio drive: 1TB HD), Windows 10 x64 Anniversary, Equator D5 monitors, Faderport, FP8, Akai MPK261
|
Lanceindastudio
Max Output Level: -29 dBFS
- Total Posts : 4604
- Joined: 2004/01/22 02:28:30
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:04:36
(permalink)
Am I the only one that thinks this whole argument doesnt ******g matter? It will probably never effect anybody's mix ever, EVER, unless they get caught up in trying to follow something here over using their ears to make decisions. Lance
post edited by Lanceindastudio - 2012/03/11 14:53:25
Asus P8Z77-V LE PLUS Motherboard i7 3770k CPU 32 gigs RAM Presonus AudioBox iTwo Windows 10 64 bit, SONAR PLATINUM 64 bit Lots of plugins and softsynths and one shot samples, loops Gauge ECM-87, MCA SP-1, Alesis AM51 Presonus Eureka Mackie HR824's and matching subwoofer
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:07:05
(permalink)
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:32:20
(permalink)
OMG!!  Are you serious? Of course it matters. Being right on the internet always matters....
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:40:35
(permalink)
Heh, well possibly, but that *definitely* doesn't help anyone's mixes.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
Bub
Max Output Level: -3.5 dBFS
- Total Posts : 7196
- Joined: 2010/10/25 10:22:13
- Location: Sneaking up behind you!
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:40:44
(permalink)
FastBikerBoy OMG!! Are you serious? Of course it matters. Being right on the internet always matters.... Yeah, you've certainly proven that.
"I pulled the head off Elvis, filled Fred up to his pelvis, yaba daba do, the King is gone, and so are you."
|
Jind
Max Output Level: -73 dBFS
- Total Posts : 878
- Joined: 2007/09/08 16:14:48
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:41:39
(permalink)
FastBikerBoy OMG!! Are you serious? Of course it matters. Being right on the internet always matters.... Are you sure? If not, do you feel any less important? Some how a lesser man? I know when I paint by numbers and I mistake "Number 1 = Antique White" on my lighthouse for "Number 2 = Off White" I feel less of an artists than those that always choose the right color.
Jind Sonar X2 PE, Cakewalk V Studio 100; Intel i7 w/ 16 GB Ram, MS Windows 8.1
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:44:08
(permalink)
I think there should be more modern labelling on these threads. Why don't the threads indicate, using some abstract value - a Q factor, for example - that as you make the same wrong claim more times, the amount of wrongness decreases?
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
Bub
Max Output Level: -3.5 dBFS
- Total Posts : 7196
- Joined: 2010/10/25 10:22:13
- Location: Sneaking up behind you!
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 14:47:35
(permalink)
I completely understand what Mike is saying and it really doesn't have a whole lot to do with Q factors.
"I pulled the head off Elvis, filled Fred up to his pelvis, yaba daba do, the King is gone, and so are you."
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 15:02:10
(permalink)
You are dead right about that, yes. What he's saying really doesn't have anything much to do with Q factors.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
Sickvision
Max Output Level: -74 dBFS
- Total Posts : 841
- Joined: 2009/05/03 22:28:59
- Location: BOSTON, MASS
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/11 15:08:24
(permalink)
mike_mccue In physics and engineering Q factor means a very specific thing: Q is the bandwidth of a resonant circuit and it is measured at 3dB from Peak. In other words the Q parameter is not a number value that can mean many things... In engineering it means one thing, a specific bandwidth measured at a specific place. Why does ProChannel offer three different actual bandwidths for the very same Q parameter value? The way ProChannel EQ uses the Q parameter value seems like a perpetuation of a labeling mistake made when someone was building some old analog gear. Wouldn't it be more accurate to have the actual numeric Q parameter value switch in the text box to an accurate representation of the the actual Q value that we hear when we switch between Pro, Vintage, Modern, Hybrid? I don't understand why we are encountering a labeling mistake in 2012 when the actual underlying *digital* math is so accurate that a mistake like this has to be forced upon the transfer function in the form of some correction factor that forces Q to not mean what Q actually means. Surely, if the Q we are hearing is wider, or less wide, than the Q factor value shown in the ProChannel Gui then there must be some mathematics under the hood that represents what the actual Q we are hearing really is. Why can't we see the actual Q we are hearing, rather than have to view some arbitrarily assigned value? I suspect that if one really understands the idea that the Q in ProChannel is just some reference number, a number that is only accurate representation of Q for some of the EQ modes, that one will conclude that switching between the EQ types is a quick way to switch Q values. The next thought that may occur is that any of us ought to be able to adjust the Q by ear so that any EQ can sound Pure, Vintage, Or Modern. If you are seeking a good understanding of EQ it can be helpful to know what the actual real life Q value you are listening to is. Is there a real benefit to hiding the actual Q factor by leaving it at a fixed value as you actually switch through various widths? One benefit is that you can present a regular old EQ transfer function and pretend like it's actually 3 different EQs... which I guess makes it seem like more EQ. One downside is that the end user will have inconsistent experiences when listening and trying to relate what they hear to a Q factor, The lack of consistency, and inaccurate display of the parameter value as you switch through the various mis labeled Q factors will make it difficult to keep track of which Q actually is and which Q isn't really. So, it seems to that it would be great if the real Q factor was displayed as the parameter value. For example; If you switch modes and the Q gets wider or thinner then the Q number could reflect the change rather than the way the current display perpetuates, and even celebrates an inability of old analog circuits to be as accurate as digital circuits. In other words if the Q is 1.0 and I switch modes and now the Q is actually 1.5... I think the parameter value should switch out and read 1.5 rather than suggest that Q = 1.0 can mean different things. It's 2012 and control panel labeling mistakes and analog circuit compromises can be easily understood, accurately described, and easily represented using digital processes. It is 2012, and the easiest way to demystify some of this stuff would be too provide accurate labeling rather than indulge in the anachronistic practice of emulating mistakes made in the past. Simple? best regards, mike SEING THE VALUE THE # WOULD FOR SHURE HELP UNDERSTAND WHAT CHANGES YOUR MAKING ,AND HELP LEARN THE Q BY SEING THE VALUE>>. GREAT POST
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 13:08:24
(permalink)
Yes, What I am suggesting is that the most useful thing would be a circumstance where regardless of what type of gain dependency is running that the actual Q factor be shown in the dynamic text box. Any body who actually wants to learn about audio tech can easily learn that a Q of 1.0 equals q 1.41 octave bandwidth. We know that this is the case regardless of where the center lies on the frequency spectrum. In other words a Q of 1.41 at 6kHz is one octave wide AND a Q of 1.41 at 100Hz is one octave wide. I don't know how many guys resisting this idea and claiming I don't know what I am writing about are actually musicians, but I'm confident that any musician who is also interested in sound tech will realize that equating Q width to octaves can be useful when working with music. Guess what a Q of 0.667 equals? 2 Octaves. That means if you have a Q of 0.667 with a 6dB boost at 440Hz that you will boost everything from A3 to A5 a minimum of 3dB. I am suggesting that in the year 2012 that a EQ can both have gain dependency, and it can report the actual Q factor in the GUI. Analog hardware that wasn't designed as constant Q could never do this... the Q labels, if they were available, were simply meaningless. The development of constant Q designs in the 1970s were considered an achievement and a valuable upgrade... because they are the only analog EQs with accurate labeling in this regard. Some may also be curious to learn that when the E series was made constant Q designs were very popular... and difficult to achieve. It was considered an improvement in the 1970's when constant Q became available... because people had been looking forward to using gear with accurate labels. This is probably one reason the actual SSL G consoles doesn't have a label that says "Q" on it the way ProChannel does. It's easy to understand why the curves made by the G series with the gain dependency are useful for mixing... adjusting one knob is quicker than adjusting 2 knobs. On the E series if you want gain dependent response you need to turn 2 knobs. All I am suggesting is that if the Pro Channel gui is going to have a knob and a parameter value that is labeled as "Q" then maybe we should enjoy the possibility that the Q factor can be displayed so that it accurately describes what we are hearing. If I want a 3dB boost, one octave wide in the E series ProChannel I can just dial that in with a Q of 1.41. If I want a 3dB boost, one octave wide in the G series ProChannel I just have to guess what the Q factor should be. This suggestion can be implemented without changing anything about the sound or the way the level controls interact with the Q. This suggestion is merely an observation that, as it stands, ProChannel misrepresents the Q factor in it's GUI in several modes and that it doesn't have to be this way. I feel that everyone, even the people that have chosen to not want to understand anything I have written here, would be better served if we let technology help us. There is no good reason for the ProChannel to display a Q factor that doesn't reflect what we are hearing. I suspect that people would learn to enjoy having an accurate readout regardless of how they use the ProChannel today. best regards, mike
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:16:34
(permalink)
Hmmm... I may not agree with much of what Mike writes around these parts, but I guess I don't see any disadvantage to changing the Q readings as he's described? So, if the Q gets wider or narrower because that's what a specific QuadCurve EQ mode does when a frequency is boosted or cut, the Q value displayed would simply reflect that bell curve? If so, what does the value indicate as it stands today for anyone who's never used the hardware being emulated? Honestly, I usually just change what I need based on what I hear, but I'm not against precision input or visual feedback. The ability to directly enter values in the QuadCurve EQ is certainly a welcome addition. But will it matter in this particular case...
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:21:20
(permalink)
The Q does not get wider or narrower. There is no such thing as "actual Q".
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:21:53
(permalink)
However, for anyone who wants to see what is actually happening, the graph shows that.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:28:19
(permalink)
There's not even any such thing as a constant Q filter. You can build a constant Q EQ out of a series of filters, but that's not the same thing. Nothing wrong with wanting an EQ that has labels that show arguably more useful musical values, but the case is not helped by flinging around a load of flat out bad science. Especially when employing an "I'm the smartest guy in the room" schtick.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:43:14
(permalink)
However, for anyone who wants to see what is actually happening, the graph shows that. Right, that's what I meant. I'm just trying to better understand the correlation between the curve on the graph and the numerical value on the control. Frequency and boost/cut I get, always have, but "Q" is one of those things I've always done by ear. Not that there's anything wrong with that.
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:50:42
(permalink)
This is the real problem with the Q value. It doesn't really strongly correlate to what's actually happening, in a non-constant Q design. What Mike is actually after here is some other value that's not Q to be shown. Nothing wrong with that, it's a fine idea.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 14:51:46
(permalink)
I'm not sure I can personally think of a pithy numerical representation that's better than the graph, mind you.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 15:31:53
(permalink)
I'm not sure I can personally think of a pithy numerical representation that's better than the graph, mind you. Well, I figure there's something shown there now, so... I do like Mike's reference to the bell curve covering a set frequency range; e.g., an octave. I think that helps the correlation between the value, the curve and something musically meaningful. Of course, even that value can get a little weird when dealing with non-western tunings, like the Scala tunings now supported by Zeta 2 (one of my favorite features).
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 16:02:08
(permalink)
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 16:22:23
(permalink)
Seth Perlstein [Cakewalk ] Q is subjective. A Q of '1' on one EQ can be different from another, which is evident in the QuadCurve EQ and the hardware that it was modeled after. There is no labeling mistake as each of the modes has a different Q to Gain dependancy, hence the different curves at the same Q value. SP The variations from EQ to EQ plugin drives me nuts when it comes to Q settings. Once you learn what each plugin's Q actually is/does, fine; but there really seems to be this strange non-standard in a lot of the EQ plugins. I suppose there are reasons for some of that, as you point out (with Q to gain dependency, for example), but it does make it more difficult to bear in on some things when the pressure is on to accomplish a mix fast, for example. Oh well ;)
|
Guitarpima
Max Output Level: -34 dBFS
- Total Posts : 4125
- Joined: 2005/11/19 23:53:59
- Location: Terra 3
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 16:24:40
(permalink)
I was having trouble keeping my P's and Q's in order but somehow I lost my Qs. It appears they're in this thread. ;-) Nice blog.
Notation, the original DAW. Everything else is just rote. We are who we are and no more than another. Humans, you people are crazy. Win 7 x64 X2 Intel DX58SO, Intel i7 920 2.66ghz 12gb DDR3 ASUS ATI EAH5750 650w PSU 4x WD HDs 320gb DVD, DVD RW Eleven Rack, KRK Rokit 8s and 10s sub
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 16:57:18
(permalink)
http://www.sengpielaudio....lculator-bandwidth.htm Yeah, them sure is a lot of fine looking numbers. Fine, I say! I think I'll be taking my 1/80 octave, or 115.4 filter "Q"uality factor as it's known in some circles, and I'm off to dinner. Thanks, Ol Pal. Edit: BTW... It's better to temporarily lose your Q than your P. That stuff can really stink up a mix after a while.
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
congalocke
Max Output Level: -85 dBFS
- Total Posts : 252
- Joined: 2009/01/01 15:19:58
- Status: offline
Re:Cakewalk Blog: QuadCurve EQ Demystified
2012/03/12 20:23:09
(permalink)
Common Mike...who wants a Q that only goes to 10;-) I personally like having access to cool eq's modeled after cool consoles.
|