[thelsdj]

Thinking about this even more, I feel like the composition could be represented as a series of transformations that go from simple to complex. So you start out with:

  * Track in C#Maj, 124BPM, 4/4
  * Chord progression I–V–vi–IV over 4 bars.
  * OK but rhythm is that current chord repeats on every beat like a stab
  * Timing should be early by half beat so it would be | I I I V| V V V vi| vi vi vi IV| IV IV IV I|
  * another transformation to adjust the voicing, etc
  * Then you can create a bass track from this that mirrors the lowest note but changes the rhythm, etc, etc etc,.

Any change along the way doesn't affect something else unless it should and then you're given a notice that you should check what was affected.

[buzzybee]

You may want to try out RapidComposer, Sundog Song Studio, or Odesi to get a sense of what that workflow entails right now. I bought each of those (two of them on sales), hoping I would come to terms with them, but they just don't work for me. It's mix of "the UX could be better", in some cases, but also some underlying consequences for complexity that show up when you're given a blank piano roll and every possible axis of music theory exposed as an affordance in the UI.

What's working for me right now? ChordPulse [0] which contains arranger keyboard style presets, plus a few options for sequencing and detailing the arrangement. Export to MIDI, add melodies and tweaks on top, and the song is ready. There are much more complicated versions of this formula around like Band in a Box, but they both have things I don't need, and aren't quite as good at this basic workflow.

[0] http://chordpulse.com

[adamnemecek]

Haha this is a central part of the app.