Conversation
Jarkko Sakkinen
jarkko
It has finally crystalized me what I'm really doing with my leisure time activity since early Fall :-)
"A Linux-focused DAW built from scratch around its own desktop-like UI, deterministic rendering and input handling, a CLAP-only plugin architecture, and persistent CoW snapshot-based history — all aimed at delivering extremely accurate low-latency behavior and eventually industry-leading audio/MIDI routing."
It makes total sense to me now that it is on paper.
#linux #audio #dsp #musicproduction
"A Linux-focused DAW built from scratch around its own desktop-like UI, deterministic rendering and input handling, a CLAP-only plugin architecture, and persistent CoW snapshot-based history — all aimed at delivering extremely accurate low-latency behavior and eventually industry-leading audio/MIDI routing."
It makes total sense to me now that it is on paper.
#linux #audio #dsp #musicproduction
1
3
8
I'm developing this like a proprietary product which ships when it is ready despite likely releasing it with one of the copyleft licenses.
This is to both allow me to fulfill my artistic vision and also maximize my abilities to defend intellectual property rights given a single data entity nature off the license protected object.
This is to both allow me to fulfill my artistic vision and also maximize my abilities to defend intellectual property rights given a single data entity nature off the license protected object.
0
0
4
@pinkforest
Recipes:
1. Have a local Git hosting.
2. Understand in detail your licensing framework.
3. Never publish until understanding both source code and licensing framework in-depth.
4. Learn about supplemental claims. Look examples of this. Plugin hosts is one of the examples where this needs special attention.
5. Learn not to publish because the opposite is preprogrammed feature of human psychology. We like to show our shit too eagerly and sometimes this causes troubles :-)
6. For the rest of your life, for better or worse, failing or not failing, you plan everything when it comes to:
6a. licensing
6b. releases (e.g. time line for initial publication)
7. Understand the source code. Don't push anything until you do. There are no ways to get around this. By doing this e.g., LLM becomes a tool, and you become a contributor.
There's stuff that Rust and also Cargo could do here and change the game a bit but enough is enough, let's save for another day :-)
Recipes:
1. Have a local Git hosting.
2. Understand in detail your licensing framework.
3. Never publish until understanding both source code and licensing framework in-depth.
4. Learn about supplemental claims. Look examples of this. Plugin hosts is one of the examples where this needs special attention.
5. Learn not to publish because the opposite is preprogrammed feature of human psychology. We like to show our shit too eagerly and sometimes this causes troubles :-)
6. For the rest of your life, for better or worse, failing or not failing, you plan everything when it comes to:
6a. licensing
6b. releases (e.g. time line for initial publication)
7. Understand the source code. Don't push anything until you do. There are no ways to get around this. By doing this e.g., LLM becomes a tool, and you become a contributor.
There's stuff that Rust and also Cargo could do here and change the game a bit but enough is enough, let's save for another day :-)
0
1
2