31–40 of 41 posts
I played around with a similar idea on my own (very simple / poor) text music environment:
https://github.com/jasonjmcghee/vscode-extension-playground?...
in the middle of making an extension to allow making vs code extensions live because I wanted a faster development feedback loop.
Earlier quoted context omitted.
It's not the 19th Century. You don't need to punch holes in cards to help the machine "think" any more.
> You don't need to punch holes in cards to help the machine "think" any more. That's literally what "prompt engineering" is, though.
I feel that one challenge of programming languages is how to remember these rules, formats, and keywords. Even if you're using familiar formats like YAML or JSON, how do you match keywords?
When developing Glicol (http://glicol.org/), I found that if it's based on an audio graph, all node inputs and outputs are all signals, which at least reduces the matching problems. The remaining challenge is ensuring that reference documentation is available at the minimal cost.
I'm wondering if it can be used alongside strudal https://strudel.cc/ Either mtxt => strudal or strudal => mtxt
Heres strudal in action https://www.youtube.com/shorts/YFQm8Hk73ug
Earlier quoted context omitted.
Lilypond, too. Though it needs a full scheme interpreter to evaluate macros (provided by both the system and the user), it can emit midi files.
Lilypond isn't well-known enough! https://en.wikipedia.org/wiki/LilyPond#Integration_into_Medi... https://www.mutopiaproject.org https://lilypond.org/text-input.html \relative c' { \key d \major fis4 fis g a a g fis e d d e fis fis4. e8 e2 } ...but why is it so complicated? A novice interpretation of "music" is "a bunch of notes!" ... my amateur interpretation of "music" is "layers of notes". You can either spam 100…
For me it was coming from tracker notation (buzz), where i was wildly underwhelmed by all that whitespace for timing (well, empty cells for timing) and the lack of parameterizable macros. A seriously underexplored field, perhaps because almost everybody who ever started got pulled in by the lure of textually defined synthesis.
Count me in as another one with a longstanding mostly dream project aiming for human enjoyable notation grammar. For me it was coming from tracker notation (buzz), where i was wildly underwhelmed by all that whitespace for timing (well, empty cells for timing) and the lack of parameterizable macros. A seriously underexplored field, perhaps because almost everybody who ever started got pulled in by the lure of textual…
http://www.colinfraser.com/m5000/ample-nucleus-pg.pdf
For macros, see:
https://www.retro-kit.co.uk/user/custom/Acorn/3rdParty/Hybri...
To me it seems like files could get hard to understand if events that happen simultaneously aren't horizontally lined up like this: 2.0 voice1 | voice2 | ... Like a text version of old school tracker interfaces: https://youtu.be/eclMFa0mD1c POS | TRACK #1 | TRACK #2 | ...
2.0 note Cmaj7 ch=1
2.0 note D ch=1
2.0 note C dur=0.15 ch=2
2.1 note C ch=2
2.1 note Cmaj ch=1To me it seems like files could get hard to understand if events that happen simultaneously aren't horizontally lined up like this: 2.0 voice1 | voice2 | ... Like a text version of old school tracker interfaces: https://youtu.be/eclMFa0mD1c POS | TRACK #1 | TRACK #2 | ...
Aren't the notes adjacent enough on consecutive lines? 2.0 note Cmaj7 ch=1 2.0 note D ch=1 2.0 note C dur=0.15 ch=2 2.1 note C ch=2 2.1 note Cmaj ch=1
Earlier quoted context omitted.
> You don't need to punch holes in cards to help the machine "think" any more. That's literally what "prompt engineering" is, though.
"Transpose this MIDI file down a third" requires neither a specialized data format nor fancy prompt engineering. ChatGPT asked: "A) Major third up (+4 semitones) or B) Minor third up (+3 semitones)" then did it.
I also don't get how you can claim we don't have to 'punch holes in cards to help the machine "think"', and also mention a MIDI file in your next comment. MIDI is much closer to punch cards than the proposed file format in the post.