![]() If you had two tracks, a doubletrack, and did this with just one of them, your ‘track’ (that’s really two tracks) can shift 1.5 dB down, to the ear. You’ve losslessly cut one side 6dB while leaving the other one unaltered. But if you tick a track one step over to the side… that’s now 3dB down, not 6. ![]() 6dB increments are seemingly impossible to mix with, absurd, insulting to even consider. Mixing with BitShiftGain in mono is impossibly crude. You’re picking locations, but they’re not LCR locations, they’re a range of potential locations. No requantization, just like with BitShiftGain itself, but in full stereo (within these constraints). If you can construct a mix this way, you can construct a mix where every single gain setting, every pan position, every location in the mix, is Bit Shift Gain: utterly and completely lossless. If that was all it was, this would seem really pointless and arbitrary. Then, you have a succession of further-to-the-side positions that are progressively quieter, all the way to hard L and R. It’s not at all LCR panning, but if something’s center you know it, and if something’s to the side it’s WAY to the side. You’d get a pan where center was quite a bit louder than sides (there’s no 3 dB pan law from bit shifts), but the first steps to left and right are QUITE a lot to the side. But what would you get if you applied this to pan? ![]() On almost every video, I’m losslessly dropping 6dB using BitShiftGain. This is a request from YouTube comments, but I had no idea how well it’d work out! BitShiftGain is a long-standing secret weapon of mine. ![]() TL DW: BitShiftPan gives you a gain and a pan control that are ONLY done using bit shifts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |