Let me answer the following questions really quick.
cpsmusic wrote: ↑Fri Aug 02, 2024 04:45 CEST
In one of the previous challenges there was some "controversy" about the song length. Could we please have some guidelines on what's an acceptable range regarding song length?
Please check in with the bundled "TL;DR Rules.txt" and both
post #002 (Rule Summary) and
post #003.
My recommendation: If I mix a song, I usually add 1/4th a bar in front and back of a mix for any possible follow-up edits.
cpsmusic wrote: ↑Fri Aug 02, 2024 04:45 CEST
Also, in the source tracks folder there's a folder called "Guides" - could the song provider explain what these are?
I can explain that for you. As the name implies, these are sound "guides". In this particular case, they are remnants of the very first multi-tracks I got, showcasing how a certain instrument section "could" sound (which is why I turned them to "snippets"). Turns out, the drums were originally "just blended", resulting in this particular over-processed sound.
It is up to you which route you go in terms of mixing
cpsmusic wrote: ↑Fri Aug 02, 2024 04:45 CEST
And finally, there's a file called "Drums_Snare_SpringorPlate". I realise that this is the snare reverb but I'm curious about the naming. Why "SpringorPlate"?
I'm not sure that this is a "reverb track". Although, these are how the files were named originally.
I unfortunately can not further comment on that. Only our Song Provider can.
kombainera wrote: ↑Fri Aug 02, 2024 11:22 CEST
For me the only way to bypass this is to use the same software that @Mister Fox is using to check the mixes and its just one of endless "music programmers" nonsense that i see more more in every daw unfortunately.
I am not sure that you're using the signal analysis correctly in either of your DAW (Cubase, Reaper). I would make sure that there are no gain boosts or other alterations involved (e.g. Pan Law in Cubase, using the plugin pre-fader or post-fader, etc), that you use the analysis tool at the very last stage of your signal chain (on the summing bus), etc.
I am using Wavelab 10 for batch analysis, since this also offers me to create statistic sheets. Getting this DAW just to get "on the same page" is kind of silly. However, you mentioned Youlean Loudness Meter -- which is a great and "affordable" alternative.
If you're using the Free variant of Youlean LM2, use either the ITU-R BS.1770-4 or EBU R128 preset, then run the mix through the plugin in real-time. After that, check that your mix doesn't exceed -16,1 LKFS/LUFS ILk (Integrated), and neither -1,1 dBTP -- to keep tolerances in mind.
If you're using the Pro variant of Youlean LM2, use either the ITU-R BS.1770-4 or EBU R128 preset yet again. Now you got several options. Either run the mix through the plugin in real-time, use the "load" function, or drag-and-drop the WAV file on top of the LM2 user interface. The last two options are faster-than-real-time processing and also evade possible gain offsets while "streaming through" the analyzer. Else, the same rules apply: check that your mix doesn't exceed -16,1 LKFS/LUFS ILk (Integrated), and neither -1,1 dBTP -- to keep tolerances in mind.
If I check with Wavelab 10's Batch Analysis at the end of the game, I should not see any overshots. Although if I do, they might be within the allowed tolerances.
Please also check that there is no input gain offset set in LM2 (see settings), or anything that affects the analysis (as in: gain plugins or gain offsets of a file prior to real-time usage). Yes, Youlean LM2 does not show individual dBTP readouts for L/R, but a simplified/"combined" readout based on the highest peak. Else, every LUFS meter has certain tolerances - hence me mentioning -16,1 LUFS ILk and -1,1 dBTP. Unfortunately, Youlean LM2 does not show you the sampling rate and bitrate of the file. Either use a file inspector, or the "load WAV" function of your DAW, which usually also shows you the sampling rate and bitrate in an info box.
This should answer your question.
If not, please ping me on Discord, and we can figure something out.
![:thinking:](//cdn.jsdelivr.net/gh/twitter/twemoji@latest/assets/svg/1f914.svg)