Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meadowlark, a DAW written in Rust

github.com

Post reply on HN
Print view View original

11–20 of 124 posts

Re: Meadowlark, a DAW written in Rust

#11

Post by ZoomZoomZoom »

The design doc looks promising. I like the limits set on the scope, as a contemporary DAW is a monstrous program and it's impossible to implement all the bits simultaneously.

I wish the project flourishes and attracts both users and developers. Reaper desperately needs a Free Software competitor, even an aspiring one!

- Are there any plans to have some user-facing API for plugins/scripting? Professional workflows vary widely and automation helps a lot.

- How flexible the UI is going to be? Multi-monitor setups of different configurations are very frequent in studios, free docks and/or floating windows are very important.

- I see you mention sidechain routing, but it's unclear what are the plans on multichannel audio and, more importantly, the routing possibilities. I'd love to see some kind of node editor for this where you can visualize and manage complex routing schemes for your projects just dragging nodes and noodles.

Re: Meadowlark, a DAW written in Rust

#12

Post by beepbooptheory »

open-paren wrote: post #7
beepbooptheory wrote: post #2

from 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)

I know, my question still stands though, I get that its not a goal right now, just seems like something you should be thinking about from the beginning

Re: Meadowlark, a DAW written in Rust

#13

Post by gmueckl »

How is this titled "fully featured" when it's still in its early stages with very little code in the repository (and most of what is there looking like an exercise in software architecture)?

Is the "it's in rust" hype so strong now that even a few lines of code covered in ambition are sufficient to make the front page of HN?

Re: Meadowlark, a DAW written in Rust

#15

Post by kierenj »

beepbooptheory wrote: post #2

from 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…

So strange! Very much add odds with the "full-featured" label. No Mission: Impossible theme (5/4)? No Pink Floyd - Money (7/4)? No Seal - Kiss from a rose? No Hey Ya!? Metallica - One / Nothing Else Matters? Fallin'?

Edit: This was under "non-goals" for the MVP. Completely understandable...

Re: Meadowlark, a DAW written in Rust

#16

Post by falcolas »

Who, developers aside, gives a single whit what language it's written in? Just give us something useful, expandable, and with ongoing support for when bugs do appear.

So much digital ink (and the associated mindshare) wasted in the design doc whinging on about how much Rust is better than C++ that they hardly talk about the DAW itself.

And for features, immediately canning MP3, 4/4 time signatures, and sidechain routing makes this little more than a toy when compared to existing offerings.

I'll watch this to see what this becomes, but I don't have high hopes, not with the current stated direction.

Re: Meadowlark, a DAW written in Rust

#17

Post by fxtentacle »

gmueckl wrote: post #13

How is this titled "fully featured" when it's still in its early stages with very little code in the repository (and most of what is there looking like an exercise in software architecture)? Is the "it's in rust" hype so strong now that even a few lines of code covered in ambition are sufficient to make the front page of HN?

It's in the GitHub description, too: "An open-source and fully-featured Digital Audio Workstation, made by musicians, for musicians"

Apparently, the authors drank their own cool-aid.

Re: Meadowlark, a DAW written in Rust

#18

Post by drogus »

falcolas wrote: post #16

Who, developers aside, gives a single whit what language it's written in? Just give us something useful, expandable, and with ongoing support for when bugs do appear. So much digital ink (and the associated mindshare) wasted in the design doc whinging on about how much Rust is better than C++ that they hardly talk about the DAW itself. And for features, immediately canning MP3, 4/4 time signatures, and sidechain rout…

This site is for developers, isn't it? For me this is interesting, cause I could see myself contributing to a Rust project, I'm guessing there's more people who think that way.

Re: Meadowlark, a DAW written in Rust

#19

Post by ehutch79 »

I feel like a lot of the 'non goals' are things that come from fundamental design qualities. plan for time signatures and tempo changes, make rendering audio pluggable from the start.

I feel like they're just going to be ripping out a lot of subsystems later due to poor planning

Re: Meadowlark, a DAW written in Rust

#20

Post by tekstar »

gmueckl wrote: post #13

How is this titled "fully featured" when it's still in its early stages with very little code in the repository (and most of what is there looking like an exercise in software architecture)? Is the "it's in rust" hype so strong now that even a few lines of code covered in ambition are sufficient to make the front page of HN?

In defence of the project, it doesn't look like the Github authors posted it to HN.
Post reply on HN