Need advice for K-meter, Ozone5, Tele Levels

Welcome to the forum!

I don't know how the levels in music libraries are in general, but if that -14 dB is the peak, not RMS level, then it souds low to me. For RMS (average) level it might be ok. I assume they are of 24 bit depth? Someone wiser than me will surely give you more precise info.

My understanding is that library submissions are supposed to be on the quiet side and lightly compressed, in order to give the end user more options. A highly squashed master might get passed over if squashed isn't what the buyer is looking for. So yeh, you're probably on the right track keeping it dynamic with lots of headroom. 14db of headroom is perhaps going a little too far in that direction, though. I'd think that limiting peaks to -6db would be more than adequate.

If you're looking for consistency, e.g. getting tracks from similar genres to match, you're going to want to look at RMS rather than peak values. Set the absolute limit in Ozone to -6db and let Ozone take care of it. All you have to do is make sure it's not pushed so hard that it sucks the dynamics out of it. 

If you find that the maximizer is working too hard, lower Ozone's Input fader. I've had mixes where I let fader-creep get the best of me, resulting in a too-hot mix that required lowering the input to Ozone by 6-8db in order to give it some room to do its magic. For example, if you're trying to limit peaks to -6db, but your levels going into the master bus are averaging -3db, then Ozone's going to have to be working constantly and you're at risk of losing dynamics.

I'm an Ozone fan myself, but I actually use the free Voxengo SPAN plugin for K-metering. Put it into Mastering mode and select K-14 for the meters. What I shoot for is to have the meters hovering around the zero mark, going no more than 4-6db below it on the quietest parts and no more than 4-6db above for the loudest parts. It's bouncing around, of course, so you're watching ballpark levels.

If the meter shows that the song is consistently below the 0 line, lower the threshold on Ozone's maximizer accordingly. If the meter shows it consistently 4 or more db above the line, raise Ozone's maximizer threshold. If the piece is extremely dynamic, it may even be necessary to automate the threshold in order to level out the overall volume.

How can the peak on the master bus be -14.2db and the peak input to Ozone is -0.4db? They should be the same.

How can the imported audio have an RMS of -5.8db but have no peak over -14.4db?

Maybe some pictures would help.

I have a number of tracks in several libraries.  I simply mixed the tracks so that none of them were compressed excessively .... there are no "flat tops" and no "brick" looking waves. Most have no, or very few overs. 

The libraries never specified a specific level requirement in their submission policy. So I mixed and polished to get a good sounding, clean track that could be used easily in the end user's project. 

This would be a good example of a typical song that might be submitted by me: From my Wavepad wave editor screen. Nothing's flat topped and very few places even come close to the top. The song is on my website music page for reference. It is currently submitted but not signed to any libraries.  Ozone is used on this tune. (O4)

Bitflipper: I’m not sure and am confused now.  Been checking into this and will start over.


Guitarhacker: my previous projects were like that, not overly compressed and brickwalled, but at about -6. Except for the last project, I think they may have been pushed too far; but limiting to just below 0 in projects was easier to grasp.   I wanted to try the K system this time.