Ladies and Gentlemen, here are the results of Songwriting Competition 089
The winners podium consists of:
- @Strange (39 pts)
- @ThomC (37 pts)
- @Mellow Browne (37 pts)
Apologies for the waiting time, this is
not an automated process.
<4 participant rule is not in use (staff comments and votes, my vote would count as bonus)
We have
00 disqualifications (due to lack of feedback / a final vote)
We have
00 entries outside of competition (but counts as submission within the deadline, yet couldn't be voted for)
We have
01 withdrawn entry (but counts as submission within the deadline, yet couldn't be voted for - this participant also stepped away form the community)
We have several users still in the game that tied
- The following ties on the chart happened due to various reasons
- ThomC -- participation vote is 27pts -- the tie with Mellow Browne resulted due to losing out on bonus points (score is 37pts)
- Mellow Browne -- participation vote is 26pts -- the participant has -1pt deduction due to having a different song-key (score is 37pts)
- Blang -- participation vote is 16pts -- the tie with juhu resulted due to losing out on bonus points (score is 27pts)
- juhu -- particpation vote is 15pts -- the participant has all bonus points otherwise (score is 27pts)
- no (more) users that tied
"Sole (License) Winner" rule does not apply -
3-position Winners Podium (>= 9 participants prior to the deadline)
STATISTICS SHEET:
Overview of Submissions (PDF - updated: 25-MAR-2025, full sheet)
Overview of Submissions - loudness normalization comparison (PDF - updated: 08-APR-2025, full sheet)
! | Bonus Info | Short info:
I am using Wavelab 10 for batch analysis, then I manually port the CSV export to a Microsoft Excel/Open Office Calc sheet with custom layout (this is not an automated process). The "Loudness Penalty" readouts have been created with MeterPlugs Loudness Penalty Studio (build: FEB-2025), slightly altered screenshots (removed boarders, added annotation, exported as PDF).
As pointed out in this post from SWC047 / July 2021, Wavelab has different tolerances for dBTP max analysis compared to tools like iZotope RX, Youlean Loudness Meter, NUGEN Audio VisLM, etc. To find a common ground, I've implemented "allowed tolerances" (just like with the Mix Challenge). These are based upon allowed offsets mentioned in the technical papers for EBU R128 and ITU-R BS.1770-4. Since no measurement tool is the same, to be on the save side, please export at -14,1 LUFS ILk max, and -1,1 dBTP max.
As usual, I did list/analyze alternative releases (MP3s and FLAC). If you've submitted your entry in multiple file formats, the statistic sheet will focus on the uncompressed material first (WAV), then FLAC, then MP3. The higher the quality, the less possible loss on bonus points for "Loudness Specs" due to offsets introduced by a used CODEC. In this case, FLAC and MP3 are merely for information purposes. |

Here are the results as chart in image form:
INTRODUCING:
An additional source of information that will contribute to the learning aspect of our community. The following screenshot shows you a more visual representation of your entry. Additional screenshots (see the second PDF file available with this post, the "Loudness normalization comparison") show how your song/mix would behave if it were "loudness adjusted" (loudness normalized / "matched") on a streaming platform.
This is bonus information. Very dynamic material may not be able to be matched, and material that is mixed too tightly (dense) may result in a lifeless listening experience (due to lack of transients). Limiting dynamic range is a highly subjective topic - there is no right/wrong scenario. But hopefully this gives you a better idea of how complicated the "Modern Loudness War" still is.
Thank you so much for your participation.
⚠ | Moderation Message from Mister Fox | |
INFORMATION:
As of January 2023, we are using a "tiered points system" for the voting mechanic. An extensive Rule Book update with in-depth mechanic explanation is in the making (apologies for the waiting time).
Breaking up a tie:
There was no unbreakable tie that needed to be addressed. The fall-back mechanics were used.
An explanation on the bonus points and penalty points:
- Due to exceeding the loudness specs, the following users could not acquire all 4pts bonus -- @Chasey24 and @ThomC for either exceeding the maximum signal strength of -1,00 dBTP or the maximum loudness of -14 LUFS ILk
- I sadly had to withdraw 1pts bonus from @alphageeks, @Blang, @EatMe and @Strange for not using the filename template properly. Please check your white spaces and double-underscores in the future. In case of SoundCloud, you can name your songs different compared to the filename.
- I could sadly not award 2pts bonus for "feedback for everyone" to @alphageeks - as the feedback given was "the bare minimum" (by personal choice!). @EatMe only gave feedback to 8 participants. And I sadly had to withdraw -1pt from @Strange for only going with a points system instead of writing some words of encouragement (e.g. mix tips, pointing out certain possible arrangement issues, etc).
- I could sadly also not award 5pts bonus for "documentation" to @alphageeks. @juhu and @Chasey24 are also kindly asked to please provide more in terms of used instrumentation in the future.
On the topic of provided chords and declared song key.
- The score sheet will also see point deductions with the "Mister Fox" column. This is for participants where the song's analysis didn't result in a "F Lydian" song key analysis... or things were too offset. This applies to @APi_ZZ (the readout for the whole song was in A min with Scaler 2 and Amin with zplane's TONIC -- this was probably due to the used melodies shifting things a bit), @Mellow Browne (the readout of the whole song was in D min with strong tendencies to G Dorian with Scaler 2, and zplane TONIC gave me a readout of A min/D min -- the added suspended chords and certain chord changes were just too drastic) and @VCA-089 (the readout of the whole song was C maj/A min with Scaler 2, and zplane TONIC had a readout of D maj -- this was probably due to certain melody lines and instrumentation).
► Show Spoiler IMPORTANT ADDITION:
Please understand that my knowledge on harmony theory is very limited - which is why I used helper tools for analysis. From my understanding (from various articles including ones from Splice and Signature Sound), F Lydian is the 4th mode of C Major. It uses the same chords while the tonic is different. Similar goes for A minor (which most songs got as second declaration with zplane's TONIC). I was considering not commenting at all, if the overall analysis readout was F Lydian (which it wasn't for three entries - and I checked up to 5 times per entry). However, D min or G Dorian is shifted a bit too much IMHO -- and that can be clearly heard with one entry. It was still a creative endeavor - so I hope the -1pts deduction is fair.
Overall - this has no huge influence on the final score sheet.
And while some of you were very creative with adding to the given chord progression (e.g. ThomC, alphageeks, Marc Fey) - I have to point out that some of you went a bit too far with changing the rhythm, or re-arranging/repeating just parts you liked (e,g, VCA-089, efemgie, EatMe, ThomC). The general idea here was "somebody provided a chord progression, already with a certain base rhythm - your task was to build upon it". Even if it sounds weird or boring to you (some even mentioned something along the lines of "borderline unusable" -- well, it's not according to Hooktheory and various other places).
This in turn gives me feedback how to adjust parameters, should there be a future game with a similar task. 
Thank you.
BONUS COMMENTARY:
► Show Spoiler At least two entries were actually created at a way higher loudness, and then "pulled down" after finalizing in terms of volume to be within the given specs for this game. Those were from @EatMe and @efemgie, which can be clearly seen on both the "Loudness Penalty" readout, and the Statistic Sheet. The transients were just gone, sadly resulting in a bit of a lifeless listening experience.
For the future... even at such a "low loudness", you can still do summing bus compression to "compact" your song (stylistic choice), then turn down the signal strength (volume) before hitting a final limiter. This way you retain the transients, while still being within specs. Maybe give it a try. Even if you opt for a loudness target of -12 LUFS ILk.
I hope you all had fun and learned something new in the process. Please keep it up for future challenges throughout 2025.
See you folks in the next game.
|
License selection:
We will now perform with the usual. Selecting of licenses is handled in public. In order of the winners podium (top spot to lowest), and only if you want to, please select one license/company out of the pool and mention it in this thread within a timely manner, then (
important) please get in touch with me (
via PM) with your full name, email address and your license selection. Else, licenses can not be addressed.
As usual - you're
not forced to pick up anything. You can pass and therefore offer more to select for the next person in line (if there is a spot existing / not available for "sole winner" mechanic). Just let all participants/winners/the staff know in a timely manner (within 5 days of this post). Once one company has been selected, it's out of the pool for the next person on the podium.
Since SWC091 has a 3-position Winner's Podium, we can also continue to test a possible new game mechanic that offers "low placed participants" a chance to pick up a bonus license - if somebody from the Winners Podium passes on a selection. You can read more about this in
SWC083 - post #067.
The follow-up post will have a summary to that concept.
I re-open the field for talking some more about each others' productions. If things drift a bit too off-topic, please use the
General Gossip thread, or
Discord.
See you in in the next challenge!
Songwriting Competition 092 (April 2025) is still in full swing. There are currently no entries. There are 17 days left to participate.
Please have a look.
EDIT: 08-APR-2025 07:05 UTC+1/CET - initial post.