Meadowlark, a DAW written in Rust
github.com
Meadowlark, a DAW written in Rust
1–10 of 124 posts
Re: Meadowlark, a DAW written in Rust
#2from the design doc:
>Non-Goals
...
Non-4/4 time signatures and time signature changes
...
Also I see nothing about OSC support, is that going to happen? Its definitely more something used for more experimental-minded musicians I guess, but it has huge support and makes things like interfacing with cv pretty simple, along with a million other things that are otherwise so fussy with midi.
Do love first class support for non 12-TET!
Overall a huge, exciting effort, can't imagine how hard this is.
Re: Meadowlark, a DAW written in Rust
#3from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
That is an odd "non-goal" indeed, and also unfortunate; it's like making a painting app but not giving users access to basic colors.
Re: Meadowlark, a DAW written in Rust
#4from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
They don't even have support for non-4/4 and you are asking about OSC? Is this you flexing that you know what OSC is or do you actually imagine that is on the road map at this stage?
Re: Meadowlark, a DAW written in Rust
#5from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
That is an odd "non-goal" indeed, and also unfortunate; it's like making a painting app but not giving users access to basic colors.
Or fixing headline widths to 60 characters plus "..."
Re: Meadowlark, a DAW written in Rust
#6from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
Doesn't this non-goal dooms the project to be an edm/"bedroom-producer"-driven one? Maybe the goal isn't a general purpose DAW. But that would otherwise contract with the claim "fully-featured".
Re: Meadowlark, a DAW written in Rust
#7from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
> Non-Goals
> To keep the scope manageable with such a small team, we will NOT focus on these features for the mvp
(emphasis added)
Re: Meadowlark, a DAW written in Rust
#8from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
That is an odd "non-goal" indeed, and also unfortunate; it's like making a painting app but not giving users access to basic colors.
The document states this is a non-goal for the MVP, not a non-goal for the final product.
Re: Meadowlark, a DAW written in Rust
#9"proudly written in Rust"
... what is it with this Rust guys? lol
but locks cool. are there actual screenshot available? the notes editor looks fun. loved the one from fruity loops A LOT (awesome profram)
Re: Meadowlark, a DAW written in Rust
#10from the design doc: >Non-Goals ... Non-4/4 time signatures and time signature changes ... Just curious from a software design perspective why this is the case. I would, naively, assume you build up software primitives that wouldn't assume a time signature, making it trivial to support whatever segmentation of time. Why not just have a pulse and divide it however is needed? Also I see nothing about OSC support, is th…
That is an odd "non-goal" indeed, and also unfortunate; it's like making a painting app but not giving users access to basic colors.
A closer analogy would be to only support static images instead of animations and to only support cartesian pixel grids with only 2 dimensions.