vessenes 39 minutes ago

Cool. My one concern with this is that it has no horizontally scannable note/chord mode. It’s super common for humans to read a sequence of notes left to right, or write it that way, but it’s also just more efficient in terms of scanning / reading.

Can I suggest a guarded mode that specifies how far apart each given note/chord is by the count, e.g.

  #1.0:verse1 
  Am - C - G - E - F F F F
  #
You could then repeat this or overlay a melody line like

  #0.25:melody1
  C4 - C4 - C4 D4 C4 - D4 - D4 - D4 E4 D4 -
  #
Etc. I think this would be easier to parse and produce for an LLM, and it’s would compile back to the original spec easily as well.
rock_artist 2 hours ago

Hey, the idea is nice, It would be great to know what pushed you to start this format.

Also, any apps that uses it would benefit from being add to the repo assuring usability in addition to readibility.

1313ed01 2 hours ago

I like the idea overall. Looks like something that would be fun to combine with music programming languages (SuperCollider/Of etc).

Not so sure how human-friendly the fractional beats are? Is that something that people more into music than I am are comfortable with? I would have expected something like MIDIs "24 ticks per quarter note" instead. And a format like bar.beat.tick. Maybe just because that is what I am used to.

  • bonzini 23 minutes ago

    It should be fine, but fractions (or both fractions and decimals) would be preferable in order to express triplets (3 over 2, effectively a duration of 0.3333...)

intrasight 2 hours ago

I think that for completeness it needs looping and conditional constructs

giladvdn 2 hours ago

Probably stating the obvious here, but this would be a good way for an LLM to attempt to write or modify music.