Stephen PickeringMy new single “A Magic Lake” went live today on all digital platforms.
Spotify:
Apple Music:
Youtube Music: https://music.youtube.com/watch?v=blXM0cN8Zk0&feature=share
Regular Youtube:
This Hypeddit Landing page has links to most of the places it is available for streaming or purchase. The top two, Spotify and Apple Music, I think account for something like 90% of music consumption these days, but as I come across others, I’ll add them both to that page and this one.
Even if you’re keeping the same bit depth.
The short of it is, that the bounce down, say from 96khz/24bit to 44.1/24bit is going to raise your True Peak and integrated LUFS by .2-3 points. When you apply dithering, it tames that gain to only .1 point. There are technical reasons for this, but the short of it is, my last track I recorded in 96khz/24 bit in logic and for what ever reason when I googled about Dithering, the impression I got was that it was only necessary if you were reducing the bit depth, say from 24 to 16, which has been the common practice for years. But lately Spotify, Apple Music, and I assume the others are streaming in 24-bit, so I didn’t feel the need to dither. But then I noticed that jump after bouncing. Dithering solved the problem, or at least most of it. There still was a .1 jump both in True Peak and iLUFS, but not the .2-.3 point jump that you get otherwise. There are three Dithering options in Logic Pro X bouncing: Regular, and two different “Noise Shaping” ones. I tried all three, but at least for my song, they sounded the same and gave me the exact same readings on all the parameters of my Youlean Meter. So I just went with regular, the first choice.
Here’s a comment I just wrote on a Youtube video by the brilliant “In the Mix” channel that I will link to at the end:
Looking at those guidelines, does it mean if you keep your TP below 2.0 Spotify will let you get away with a little louder LUFS? The most recent song I uploaded had a TP of -2.1 and an integrated LUFS of -13.4. Since I kept it below -2 TP do you think they’ll let the .6db “slide” so to speak (as we say here in the States,hehhe) or will they reduce it still? The guidelines are a little obscure. They say if you are going to master louder than -14LUFS then make sure your TP is below -2. So I wasn’t quite sure how to interpret that. For sure with indies like myself, the holy grail as it were is to have a sonic quality and loudness that competes with the majors. Oh another think I’ve learned: You’ve got to employ dithering, even if you keep the same bit depth on the bounce or mixdown. I accepted the Youlean measurements within the mix because they were the very last on the stereo buss chain. But the mix down from 96/24 to 44.1/24 even keeping wave lossless bumped up the TP and iLUFS by .2-.3 points. Employing dithering tamed those losses to only .1 And the readouts were exactly the same whether using regular dithering or the two “Noise Shaping” varieties. Cheers!
Stephen Pickering
My latest single just dropped on Spotify, Apple Music, Youtube Music, Amazon Music, really every streaming platform on Earth by way of Distrokid. It’s also on regular old Youtube.
It’s called “Just for a Moment,” and the B-Side is “Union Street (Hold On).” Give me a listen, like, and follow if you’re a fan.
I have a track I’ve mastered. It’s -14.7 LUFS and -1.2 True Peak. I’m pretty happy with it other than I wish it were about a decibel louder. So I thought I’d try to go for -13.5 LUFS. But it seems whatever I do the true peak is more sensitive to than the LUFS. For instance, the first thing I did was raise the gain on the Multipressor in the master chain from 1.6 to 2.0. The overall LUFS integrated went to 14.4, but the True Peak went to 1.0 which I want to keep under. Should I increase the limiter then? Shorter version of the question: How to increase the LUFS without increasing the True Peak? Thanks! I bought a copy of Levels.
I do think I have figured out one thing: Just a small bit of audio or so can make your True Peak sky rocket out of the blue while 98% of the mix is well below your target, even though it’s not necessarily audible. Once you identify that bit, and it’s not hard with a metering plug-in like Levels or Youlean, you can create an identical track, cut and copy that bit to it and apply more processing to just it, whether that be a Limiter, faster attack time on your compressor, and then it frees up the majority of the track to breathe! [I made these comments to this video post: https://www.youtube.com/watch?v=BS07ChRkY4M ]
I recently made two different covers of the Josh Rouse song, “Michigan.” The first I made on the iPad with Garageband. I played the Spanish guitar and sang into the the little pinhole microphone. Then I added some “smart” instruments, bass, drums. So this one is done basically in “click” time, but I still think it came out sounding pretty good, considering the circumstances.
The second was done with more Professional mics and into Logic Pro on an iMac. I basically just played a steel acoustic and sang at the same time, no overdubs or click track. So it’s live and more natural.
So, two different sounds with the same song, but I kind of like them both for different reasons.
Now, if I could only do some of my own songs!
