aww yeh. We excited? We excited.
Some things I'd like to bring up ahead of this and future comps. Artistic license, personal necessity, plain disagreement, etc. can of course override any advice.
Winning submissions will be included with future versions of the program. This means you have the opportunity to submit entries that would help new users
understand SunVox and the extent of its capabilities, especially in areas where other trackers may fall short! Clear organization and varied demonstrations of functions and techniques would be helpful!
It's more exciting for everyone if you try to present the peak of your ability! Submit something you can be proud of,
whether for the effort or elegance of execution.
There may end up being a large number of submissions to listen to, analyze, and rank.
Do your best to stand out, and keep in mind voters may be pressed for time! Disorganization and excessive length can impact judgements!
Sometimes people like to go the extra mile and give their projects unique visual aesthetics
. In case readability
would take a hit, something I did once was apply an aesthetic last, after loading the project into itself in its working state. That doubles the file size though! Attached it as an example. Module 84 contains the (rather opaque) raw project.
[edit: oop, the kill switch doesn't work now. ENJOY THE MUSIC INFINITELY.]
If file size is an issue, to start with, make sure you're using the maximum degree of zip compression!
What makes a file "organized" and "readable"?
There are different ways to arrange and color-code with internal consistency, and different ways may be better suited to different workflows, but I personally like:
• Sticking to the default module colors, as they should be the most familiar to the most users at a glance.
• Making important modules slightly larger - for example, the beginnings of chains.
• Spacing modules out, for clarity of connection routes. Note that on mobile, in portrait, the module view is more vertically stretched than it would be for a desktop or landscape user, so what looks spaced may be pretty squashed-up for others! Same for if you've turned your module scaling way down.
• Grouping chains that are related - for example, keeping percussion instruments near each other.
• Matching unique names between modules and patterns. (Do this before you need to copy and paste them!)
• Leaving pattern icons visible - setting your own icons can be useful, but even the generative defaults can provide decent indications of change and similarity.
This is a relatively small, tight-knit community for a music program, with a number of skilled musicians who are already mutually fans and friends of each other. Keep an eye on your biases!
Aaaaand finally, *pulls you aside and lowers voice*
here's the deal: if you're in it to win it, you'll have to play to the audience's tastes to some degree. Look to past competition entries' scores to get a feel for who's listening and what broadly appeals to them.
Anything else we should consider?