![]() | All Advertisers |
| |||||||
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UAD, still worthwhile? | Professor | High end | 125 | 31st August 2008 12:51 PM |
| is worthwhile the upgrade from 48 to 88.2 ? | Gabriel Sousa | So much gear, so little time! | 12 | 9th August 2008 01:20 AM |
| 32 bits floating point to 24 bits fixed point | 16/44.1 | Mastering forum | 39 | 22nd February 2007 08:15 PM |
| would this be worthwhile? | Stubacca | So much gear, so little time! | 35 | 4th July 2003 11:11 AM |
![]() |
| | Thread Tools | Search this Thread | Rate Thread | Display Modes |
| | #61 | |
| Gear maniac | Quote:
What I meant by my first question was, "Aren't you able to record in 32Bit / 384k with the Pyramix and Sadie systems ?"
__________________ As your dog says: "Hey barkeep, whose leg do you have to hump to get a Dry Martini around here?" | |
| | |
| | #62 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
It may serve you well to make a distinction between “conversion bits” and “processing bits”. The music itself (which is an electric signal all the way from the mic output to the speaker or headphone) can not be 32 bits, nor can it be 24 bits, nor should it be. The ear does not respond to 144dB dynamic range. That is a fact, regardless of the format. The concept of dynamic range and “conversion bits” are tied together. As was stated here, there is a limitation due to component and circuit self generated noise, which sets the limit of dynamic range. But one can “park” a 16 bits signal (or a 20 bits signal) in a DAW. Think of a number 62. One could write it as 062 and it is still the same number. Why do such a silly thing? Why should we allocate 3 digits for the expression of 2 digits? Say I want to “add a gain” of X10, so the number will become 620. But if you want to amplify 62 by 20, which is 1240 and that calls for one more digits. If all you have is 3 digits, the result 1240 will become 240. That is a huge error. So you need more digits (processing bits). Similarly, if you try to divide (attenuate) the number 62 by say 3, the result is 20.666666…. which calls for a lot more digits (or “space”). Say you have 16 channels, and you want to add them. That adds up to a bigger number, thus more “space” on the left side. Now take some of the channels and attenuate, which calls for more digits (space) on the right side… Also note that some processing (such as EQ boosts or reductions) call for more space… The DAW provides “a lot of digits” on both sides of the conversion digits (processing bits). The user does not have to worry about running out of digits on either side. The analogy for a DAW is a large “scratch pad”, providing a lot of area to insure that whatever you do (moving things around, blowing them up, merging and so on), you never run out of the page. The idea is to never get to the edge of the page. But when your processing is all done, you need to make a final product. You now need to get back to the real world of “limited size scratch pad”. You need to take what the ear can hear (certainly not 24 bits), and what real hardware can play (also not real 24 bits). If your final format is say a CD, you need to take the 16 most significant bits only. If your final product outcome (or archive) is 24 bits, you need to lop the DAW outcome to 24 bits… Doing so, it is best to look at dither with noise shaping, but that is another whole subject. So the answer is NO. You can take a signal, and pad it with zeros on both sides, for the sake of doing processing. But there is no way and no processing that will eliminate the noise that came into the DAW, and there is no point in feeding more bits to a DA then what is dictated by the limitation of the ear or the DA itself. I hope my examples help you understand it. Note that while my examples used common decimal digits (such as 62); the same concepts apply for binary numbers made out of 0’s and 1’s. Regards Dan Lavry | |
| | |
| | #63 |
| Gear nut Join Date: Dec 2007 Location: Audioland
Posts: 125
| Hey Dan (you rock of course and I loved the TapeOp interview), If someone has no boutique preamp (yet good ADs), would it be better to 1. Run a microphone (like K2 with power supply) straight into the AD converters at the low signal strength, or 2. Use a less boutique preamp so the ADs have more analog gain? It's obvious either way can have downer side effects, but I'd love to hear your take on the gains (no pun intended).
__________________ I've worked on all kinds of pop artists to rock artists... Sheryl Crow, all the Crows: Sheryl, Black, Counting - Jack Joseph Puig |
| | |
| | #64 | |
| Gear maniac | Quote:
![]() Seriously though, thanks for your time on this subject, and helping me understand this Bit thing more. Was wondering though... As this question of mine never seems to get addressed. Are they ever in the future (immediate or way down the road) - going to be able to "apply" Bits to something else in the audio besides dynamic range ? Then the reason for more bits would make sense (the "bottom 10" or whatever) could in theory be applied to some other attribute in audio to help the digital realm "interpolate" it better . Apply them to some other attribute in music that helps the digital realm "interpolate" it better ? I mean like EVER down the road ? Kinda like you know how at first video came out going to TV it was 3 RCA jacks right ? 1 was Video (lets say metaphor for bits), 1 was audio L and the other was audio R. At the time everyone probably thought that was it and the best it can get.... BUT then they figured out how to divide that SAME video signal (metaphor for bits here) into the component cable where now it is 3 video cables and 2 audio cables. So they learned how to divide the video signal into its 3 most important parts, and let them have their own dedicated cable and connection for signal. Then the video players had to get a "engine" in a sense for EACH of them important components of the video signal. The outcome was a far superior Video picture !! COULD ever in life that eventually happen with audio ? Break it down to it most important components, and THEN have each of those have their own bit engine or whatever to make up a FAR better capture... Do you understand what I am asking here ? Whats your take on that possibility ? And maybe its not even Bits that would be the "engine" for every component,, but something. So I am not stuck on bits here... but they do seem to always be the "engine" for interpolating things I notice. But the main point would be the possibility to break audio down farther than it is now, and give every one of them broken down components its own "engine" and cable and converter or whatever to give a end result of a way higher quality piece of audio capture. Complete other subject here, BUT lets switch from Bits to SR: I know the discussions about how 96k is already overkill, and 192k is unneeded. But then you got DAD converters going up to 384k !! I mean why would that be available and people use them regularly unless there was something they actually were getting out of the 384k ? Myself I like to use 192k when archiving stuff off of my ATR 1" stereo Reel to Reel tape machine. I do notice a difference I like between the capture comparisons of the 192k captures vs the 96k captures. And it is not a "additive" there of something that wasn't there in the first place (that would be a unhonest sound and I wouldn't like that) - but it is more of a "capturing the air around the audible frequencies causing them to sound like they do when I am listening to the tape". The 96k captures, seem like that "air" was no captured (because it is inaudible anyway) - BUT in turn that caused the AUDIBLE frequencies to sound different/be interpolated differently by the human ear. The old "residual effect" thing. Now in your professional opinion, what do you feel about that ? Totally impossible ? Plausible ? Because I said it here before, but no one addressed the possibility.... Do you believe the "Neighboring frequencies effect other frequencies" theory ? SO in turn, a INAUDIBLE neighboring frequency could in turn actually effect a AUDIBLE frequency. ?? Yes ? No ? Maybe so ? I would love to hear your thoughts on this. And thanks for your time.
__________________ As your dog says: "Hey barkeep, whose leg do you have to hump to get a Dry Martini around here?" | |
| | |
| | #65 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
You need to know the performance of the AD. Say the AD offers some internal gain. How much does such feature cost you in terms of distortion? How much does it cost you in terms of noise (dynamic range)? My LavryBlack AD has a built in 0-13dB worth of gain in 1dB steps. At maximum gain of 13dB you lose almost nothing in terms of distortions and noise (compared to 0dB gain). But say I wanted to push the gain to say 20 or more dB of gain, then the dynamic range (and possibly the distortions) limitations inside the AD would suffer. I just wanted the AD10 to be rock solid and clean, but that of course moves the gain issues elsewhere, to the micpre. So you now need to know the limitations of the micpre. Very often there is some tradeoff between dynamic range and distortions. As a rule, micpre's introduce less distortions when set to lower gain. Always, micpres introduce more noise as you set them to higher gain. So in some sense, from distortions and noise standpoint, it is best to use micpres at as low gain setting as possible. But that would defeat the purpose of a micpre, which is there to amplify the signals. What am I getting at? The third consideration (besides the AD and the micpre) has to do with how much signal you get from the microphone (mic type and mic distance from sound source). It is one thing to have a singer sing loudly into a hand held high efficiency condenser mic (the signal would be very strong). It is another thing to have say a ribbon located far away, yielding a weak signal... So there is no single answer to your questions. There are at least 4 variables (mic, mic location, micpre and AD) to consider. I can say that in the case of my converters (LavryBlack, LavryBlue and LavryGold AD's) I would tend to utilize the internal AD gain, thus making the life of the micpre easier by around 13dB. That would translate to an almost direct 13dB better overall dynamic range. The same is true for some AD gear on the market, but other AD gear may not follow that rule. Of course, there are many cases where it is advantageous to set the AD to minimum gain (0dB gain). For example, if you want to send a signal to the AD on a cable over long distance, having a 24dBu signal source (pro level), will serve you very well in terms of rejection of interference due to external noise (radio, AC hum and so on) as well as grounding issue. So noise and distance considerations may be the dictating factors in some cases, opposite to my previous comment.... Your question is not easy to answer, and I barely touch on it. A complete answer would take many pages and a lot of time, but I believe that my answer covers the main points. Regards Dan Lavry | |
| | |
| | #66 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
Lavry Engineering - Unsurpassed Excellence under support. It is a long paper, but I kept the math out of it, and included a lot of graphic plots. The idea is to explain the subject for people that are not into math and engineering. Regards Dan Lavry | |
| | |
| | #67 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
More bits are not only for higher dynamic range. More (good) bits are also for better sound (less distortions). The explanation is a “bit” complex -:) For a more detailed answer, go to my forum at Lavry Engineering - Unsurpassed Excellence I just posted a pretty long "intuitive" explanation titled "More (good) bits are not only for better dynamic range". I am not sure your question and my answer have much to do with the thread (32 bits), but it is OK with me if you (or anyone) wish to stir the conversation to "the reason for more bits". I think it is a good subject; there is whole lot that can be said about conversion other then the number of bits. Of course as a designer I keep much of my thoughts and findings to myself, but I can share some of the less proprietary information, such as the basic principles. I also realize that what interests me greatly may be boring for others. If you wish, you are welcome to post a copy of my comments here. A link will not work because reading my forum requires one to register. Regards Dan Lavry | |
| | |
| | #68 |
| Gear Head Join Date: Sep 2008 Location: Chicago
Posts: 31
| Seems to me that the simplistic analysis is, if the converter's only putting out a 24 bits in fixed format, accuracy questions aside, what advantage could there possibly be to write it to disk on the fly in some other larger format? To save your daw a conversion step later? I would think you'd want to square it away as quickly and efficiently as possible during the critical recording stage. Also, 32-bit floating point format isn't exactly state of the art for daw processing these days. It all makes me wonder how awful it might sound if a converter left off the decimation filter and accumulated all the junk bits to output a fully populated 32-bit (or higher) float? Howard |
| | |
| | #69 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
I do not write software for a DAW, but if I did I would certainly try NOT to write 24 bits of audio sample tracks as 48 bits, or as 64 bits. The need for the many extra bits is for processing, and that does not automatically mean that each track has to be stored as huge long words. Say you want to add 16 channels of 24 bits each. You can store them as 24 bits each. Now, when you do the addition, you call one sample from each track (each one is 24 bits), and add them. For that you do need more bits. But now that you are done, you may store the temporary OUTCOME on single extra wide track (2 tracks for stereo, 5-7 for surround), or in some cases you may even choose to reduce the outcomes back to 24 bits... Yes my explanation was simplistic, and it only touched the basic ideas. What do you expect from a single post? It can not be a substitute for a sets of operation manuals of the many DAW on the market. But your understanding of the explanation was a bit simplistic as well. No offense intended. You need more bits for processing, but that does not mean that each track must be padded with 24 additional bits prior to the processing. The "padding" is done "on the fly", as needed and when needed. You said: "It all makes me wonder how awful it might sound if a converter left off the decimation filter and accumulated all the junk bits to output a fully populated 32-bit (or higher) float?" That concept is pretty old. DSD "parked" a single bit at very high speed, and now DXD parks even more such data, in fact huge amount of data! There are many issues when doing so, and indeed the processing of such data requires huge amount of processing power. In fact, much of the DSD processing was done by converting the DSD to PCM, doing EQ and so on, and then converting it back to DSD. As far as I am concerned, all the objections against PCM and all the claims for the advantages of DSD fall down when one does that. Most often, the "marketing departments" forgot to mention that such is the case. Again, doing a direct EQ on DSD (or many other processing) takes HUGE amount of DSP power. I am yet to see any technical reason pointing to shortcomings of PCM. You can always find people that like the specific sound of one thing or another, but that is not how one should adopt a technical concept or a basic concept. Regards Dan Lavry | |
| | |
| | #70 |
| Gear Head Join Date: Sep 2008 Location: Chicago
Posts: 31
| Hi, Dan. I think you may have misunderstood my comment above. I was referring to my own analysis as simplistic, not yours. I really wouldn't be so bold as to characterize your analysis, most of which is way over my head, as simple. In fact, if what I said was in any way a restatement or summary of your analysis, that's a revelation to me all by itself. I was only kidding about an ADC outputting higher res with all the accumulated oversample error bits. DXD really does that with a little EQ? Kind of opens up another related can of worms.... the wisdom of tracking with one of the new DSD recorders. I gather you wouldn't consider that a good move compared to fixed format recording with a premium 24-bit converter either. Howard |
| | |
| | #71 | |
| Gear addict Join Date: May 2005
Posts: 370
| Quote:
Indeed I misunderstood your comment. Sorry about it. I am not saying that all the DSD and DXD gear converts the audio to PCM for processing, and convert it back to DSD or DXD. But MUCH of that gear does just that, which would be find if the same folks did not try to promote their format by bashing PCM while using it. When Sony and later Philips came out with DSD, one of the huge difficulties was the processing. I saw much of the hardware (some of it at Sony, some on display at AES conventions), and a simple EQ could require a very costly large size, dedicated hardware. Same for compressor, limiter and what not. I just did not see the point in being surrounded by "refrigerator size pieces of gear" for audio processing. I do understand why the hardware is so intensive. First, there is tons of data that needs to be stored and processed. A 1 bit at 5.6MHz you say? That is around .7 mega bytes of data per second for a single channel. Compare that to say 24bits at 96KHz, which is .288 mega bytes per second per channel. A 44.1KHz at 16 bits is only 0.088 megabytes per second. This is just the beginning. Now take DXD with 8 bits at 5.6MHz which calls for 5.6 megabytes per second... So say you agree to accommodate such a space hog. Say you have a DSD (1 bit) file, thus the samples are numerous, but each sample has a value of either 0 or 1. Now you want to do the simplest of operations - attenuate by say 1dB. That means you have to multiply each sample value by .891 and while each zero is still a zero, each one are now .981251, and your data is 6 times bigger. So let’s do it some justice and limit the resolution to 4 digits thus .9812. You really need at least 4 digits to have a .1dB resolution at say -20dB attenuation... Say you want to take another track (with 0's and 1's), and you want to boost it by 1dB. The second track is now made of zeros but each one is now substituted by 1.220. So where is the 1 bit DSD? The whole concept was supposed to be about 1 bit, and the vales .9812 and 1.220 is no longer a one bit. Now say you just wanted to add 2 DSD channels, no gain, and no attenuation. At each sample time you can have one of 3 possibilities: A. Both samples are 0 thus the sum is zero. 0+0=0 B. One sample is 0 and the other is 1 thus the outcome 0+1=1 C, both samples are 1 thus the outcome is 1+1=2 So again, we lost the DSD. Our data is no longer 0's and 1's. The examples hers are the simplest. Say you wanted to add the two tracks above, you end up with 0 or .981, or 1.220 or .981+1.220= 2.201. This is starting to look a lot more like multibit then DSD. In other words it is starting to look sort of like PCM but with huge data rates. And I did not even begin! Let’s take an example of a low frequency EQ. It is not easy to explain to a non mathematician, but I will try. I like the challenge of trying to make complex things more intuitive. Say you have a 100Hz sine wave. That wave changes very slowly. A whole cycle lasts 10 msec. The neighborhood of the peak of such sine wave is almost a constant (hardly changes) during a whole 1 msec time, thus there is not much information about the wave form. If you wanted to say "register" a whole cycle, you need to 10 msec of data. On the other hand, the same 1 msec of data will register 10 complete cycles of a 10KHz tone, thus plenty of information. Note that I did not yet mentioned sample rate. So far we are talking about an analog signal and the amount of information contained in some time slice (such as 1 msec in our example). Now let’s enter the sample rate variable into the discussion. A 1 msec time slice when sampling at say 96KHz means 96 samples. But when sampling at say 5.6MHz, the same 1msec calls for 5600 samples! That is around 58 times more samples, more multiply accumulate signal processing operations for handling the same time slice. Now, the initial knee jerk reaction would be to say: but the data is simpler, it is made out of 1's and 0's. Well, first, it is not! Remember the addition and the attenuation as explained above? Second, all 5600 of the filter coefficients must be very accurate. About as accurate as the 96 samples of the PCM 96 coefficients. That makes FIR filtering almost impossible, and with it goes the advantage of linear phase for audio... But you may need a compressor or a reverb, and the problem shows up again and again. Now, what does one do with such outcome? You want DSD? then you need to "reformat" it to a 1 bit at 64fs, or 1 bit at 128fs in the case of 5.6MHZ. So you send the data through a digital noise shaper that is emulating another DSD converter. That is, of course, another huge task, and with it additional reduction in dynamic range and some added distortions... Or you can convert the DSD to PCM, use standard PCM processing and then you still need to go through a final noise shaper (digital emulation of a DSD AD), with some performance degradation. It is true that DXD has less degradation, but at a huge price in terms of data size and required processing. Of course you could get the same or better results with PCM. So where did it all come from? The idea of single bit at high speed was done for hardware reasons. A single comparator offers some advantages to makers of AD and DA IC's. First there was the 1 bit at 64fs, converter front end, followed by "on chip" decimator, which immediately converted the data to PCM. But then, given some new technology methods, came the multibit AD IC's with the built in decimator (thus PCM output. It may be easier to design a converter by use of a LOCAL few bits at very high speed (such as 5 bits at 64-1024fs), but the IC makers include the decimation to PCM, and the output is 24bits at say 44.1 or 96KHz. Such a scheme certainly makes the design of anti aliasing filter much easier and better. A multibit AD at say 128fs (or 512fs or 1024fs) yields much better performance then a single bit, and that is exactly why the multibits took over. But setting aside the internal working of an AD or DA converter, which is the concern of the maker of conversion hardware, I do not see a single reason why the converted data should be anything other then PCM. PCM offers the most efficient coding scheme for digital data as we know it (a number scheme based on 2 states- 0 or 1, true or false. yes or no). Given a desired bandwidth, and a desired accuracy, the PCM code is 100% efficient; all the possible states have a meaning. 16 bits offer 65536 distinct states. 24 bits offer around 16.8 million states... DSD and DXD are a lot less efficient (as stated above). So is there a sonic advantage? I do not see why there would be. Certainly there is no conceptual reason for it. As I stated before, you can always find some folks that would swear that something sound better, and often other folks that would swear the opposite. I can not and do not want to get into what sounds better. The problem comes when a listener to a particular specific gear takes a huge leap to conclude that what they like has implications for all other cases. A poor analog front end on a DSD AD is no basis to conclude that DSD can not sound good. A great implementation of some class AB power amplifier is no reason to make statements about class AB amplifiers.... Unfortunately, with some advertizing money and some marketing, such practices are not too uncommon. Do you still think that we need a whole thread about DSD and DXD? I think I covered it pretty well. Some years ago, I was invited by Sony to show a DSD DA at their booth at AES and other shows. I wasted a lot of time learning about that stuff, and I did have a pretty good working prototype. It sure took a lot of time and effort, but I decided not to show it. Why? Very simple: My parallel efforts in the "PCM department" yielded much better results. Now that DSD is no longer a supported and promoted format by Sony (not for a number of years), I am glad I did not peruse it further. Long live PCM. Regards Dan Lavry | |
| | |
| | #72 | |
| Gear Head Join Date: Sep 2004 Location: Paris
Posts: 60
| Quote:
| |
| | |
| | #73 |
| Gear nut Join Date: Dec 2006 Location: Athens,Greece
Posts: 105
| I agree with jmarkham If the sound occupies the "higher" bits, it will have more accuracy in order to describe better the minute volume changes which happen all the time, isn't that the case? PS. It's more of a question rather than a solid opinion of mine. |
| | |
| | #74 | |||||||||||||
| Lives for gear Join Date: Jul 2002
Posts: 2,023
| Quote:
Just because there's no need for 32-bit converters doesn't mean that today's converters are "good enough"...they still can get better. It just doesn't have to happen by adding more bits. Even today's converters running at 16/44.1 sound much better than they did ten or fifteen years ago, don't they? Quote:
As for hearing past 96 kHz, nobody can (and nobody can hear past 48 kHz either). If a 96 kHz converter sounds better than a 48 kHz converter it's not because you're "sensing" things you can't hear. It's because something about the converters...probably their filters...affect the frequencies you can year differently. It's not hard to find converters that sound better at 48 kHz than 96 kHz...it's all about the implementation. Again, I don't think that anyone is saying that we wouldn't move forward...just that moving forward doesn't necessarily equate to adding more bits and raising sampling rates. Quote:
Inaudible neighboring frequencies do not affect what we can hear. However, electronically they may...which actually could be used as an argument against higher sampling rates. Quote:
Quote:
[quote]Same goes with 48k... Everyone knowledgeable in this field says 48k was/is beyond our audible detection, so 96k is just ridiculous overkill... well..... When I run my same tests I can hear a difference in my 96k recordings vs my 48k recordings.(and the difference is 96k sounds better). So WHY then if supposedly we can't detect past 16 bit 48k can I and others hear a difference when the ranges are upped past supposed "overkill" ?[/qoute] First off, I don't think anyone said we can't "detect" past 16 bits. We can. It's more than sufficient as a delivery format for most music, but it's not "perfect" (even theoretically). It is true that we can't hear frequencies higher than those that a 48kHz sampling rate can capture and reproduce, but that doesn't mean that, depending on the design of a converter, a 96 kHz converter can't sound better than a 48 kHz converter. But if it does, it's because of how it affects the frequencies you hear...not because of the presence of higher frequencies that you're somehow "sensing". There have been plenty of tests done to try to prove that higher-frequency content makes things sound "better" to us and they've all failed. If I hear a 48 kHz recording that sounds better than a 96 kHz recording of that same performance, what should I conclude from that? You can certainly say that 96 kHz recording can capture more frequencies than 48 kHz, and you can certainly say that one specific converter running at 96 kHz converter sounds better (subjectively, at least) than a specific converter 48 kHz converter, but you can't say that 96 kHz in and of itself sounds better than 48 kHz because there are too many variables involved. Quote:
Quote:
Quote:
As far as quantization in the amplitude domain is concerned, that's determined by the number of bits captured. Finer quantization (ie increasing the bit depth) manifests itself purely as increased dynamic range (as has been mentioned, it lowers distortion as well, but it's not really "as well", its the same thing...as the distortion decreases, dynamic range increases). If you capture that 440 Hz sine wave we mentioned earlier at, say, -6 dBFS at 8-bit resolution the sine wave itself it would be no more or less accurate than it would at 12, 16, 20, 24, or 32 bits. The noise would get lower and lower (and, again, once you got to about 20 bits would effectively not change at all because of the noise in the analog circuitry) but the sine wave itself wouldn't change. Quote:
Quote:
Quote:
Quote:
Quote:
Having said that, if I'm in the market for a converter and the best one I can find at the time sounds better at 96 kHz then that's the rate I'll record at. | |||||||||||||
| | |
| | #75 |
| Gear maniac | Duardo, Man, them are some GREAT replies you gave. Thanks for taking the time to throw your input in here, and mainly focusing on some of my questions I had in here that seemed to be getting ignored. I can see alot of what you are saying... just one thing. The neighboring frequency thing. As we seem to agree at one point of it in the audible realm (which to me is scientific proof of the others possibility), I still am sticking to the possibilities of a frequency close by the very last audible realm getting effected by a very close neighboring frequency that is just outside of the audible realm. BUT, that whole subject is technically askew of this main topic, because it relates to SR more than Bits... LOL - I don't know if I am spelling it right, and the spell checker just kept fixing it to that.... I am trying to use the word "interpret" and "interpreted" -- (I just finally looked it up - LOL) -- I was meaning how technically the entire digital realm is the converters "interpretation" of audio. So how do we make it "interpret" audio BETTER ? So yea, you can now go back up to my post(s) and know everytime you see that funny looking word in there, exchange it for "interpret", "interpreted", "interpretation", etc..... you get the idea...
__________________ As your dog says: "Hey barkeep, whose leg do you have to hump to get a Dry Martini around here?" |
| | |
| | #76 | |
| Gear Head Join Date: Sep 2008 Location: Chicago
Posts: 31
| Quote:
My suggestion... get the best 24-bit converter you can afford and increase your daw processing resolution. I use a 64-bit daw and track at 88.2k/24 for 44.1k projects. Howard | |
| | |