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

41–50 of 124 posts

Re: Meadowlark, a DAW written in Rust

#41

Post by philipov »

royjacobs wrote: post #37
romwell wrote: post #30

Earlier quoted context omitted.

"Ability to make turns is a non-goal for the MVP of the car we're building" You can't record a cover of Queen's We Are The Champions or Somebody To Love without struggling with the UI if 3/4 is not supported. Or Blondie's Call Me. Or a plethora of other popular music. "Fully Featured (in our imagination)"

"Including a rear parking sensor is a non-goal for the MVP of the car we're building" seems to be a closer analogy. If you cannot use the MVP of the software for your use cases, that doesn't mean it cannot be worthwhile for anyone else.

Yes, as long as your use-case only includes driving straight forward, the MVP is fine. Supporting non-4/4 time is such a fundamental change that not being to turn is a good analogy.

The rule of thumb is that you need to design to support at least 3 different use cases from the start if you want to create something that can viably extend to being a generic product.

Re: Meadowlark, a DAW written in Rust

#42

Post by tayistay »

chillingeffect wrote: post #33
mpfundstein wrote: post #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)

Most technical developments only unconsciously reflect their social contexts. And in most cases those are the greater needs of corporations. E.g. C and Javascript. Rust is deliberate about tying its social context to its technical development. Much like open source, esp.the Linux kernel, used the social contract of legal licenses and information transmission to enable a cooperative world, except Rust foregrounds as a…

Can you ELI5 how the development of, say, C, reflects the needs of corporations?

Does every linux install mean less corporate power when, e.g. AWS runs on linux?

Can you explain what the rust code of conduct (which AFAICT can be summarized as "please be nice") has to do with competition and individualism? Can't I still be a competitive individual without being rude?

Re: Meadowlark, a DAW written in Rust

#43

Post by SOLAR_FIELDS »

tialaramex wrote: post #29
mpfundstein wrote: post #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)

One nice thing about Rust is that there's an excellent chance you can actually modify this code. That's enormously important for anybody who has even modest programming skills. For Free Software projects it's often under-estimated how much contribution you can get from the long tail of people who've got one small change they'd like to make. IF they can make the change. Otherwise you miss out. Let's give two extreme e…

Regarding #2, everyone has essentially moved over to LibreOffice several years ago, thanks to Oracle's shenanigans. I think Oracle eventually walked back whatever it was doing that made everyone fork and switch over, but by then it was too late. It seems like the only reason OpenOffice has continued its zombie-like path forward over the past few years is because of name recognition.

Re: Meadowlark, a DAW written in Rust

#44

Post by gmueckl »

royjacobs wrote: post #37
romwell wrote: post #30

Earlier quoted context omitted.

"Ability to make turns is a non-goal for the MVP of the car we're building" You can't record a cover of Queen's We Are The Champions or Somebody To Love without struggling with the UI if 3/4 is not supported. Or Blondie's Call Me. Or a plethora of other popular music. "Fully Featured (in our imagination)"

"Including a rear parking sensor is a non-goal for the MVP of the car we're building" seems to be a closer analogy. If you cannot use the MVP of the software for your use cases, that doesn't mean it cannot be worthwhile for anyone else.

No, being able to use different time signatures is essential in music. Time signatures are a basic building block required to define the vast majority of musical styles in the world. All of the western classical and popular music builds its rhythms and structure on a whole collection of time signatures (4/4, 3/4, 6/8, 2/4 are the more common ones). 4/4 is the most common time signature, but at least half of the music that follows any kind of time signature uses different ones. Also, a quite significant number of pieces use changes in time signatures throughout the piece to great effect.

To come back to your analogy, a feature that is akin to a rear parking sensor in a car would be something like retroactive recording.

Re: Meadowlark, a DAW written in Rust

#45

Post by sodality2 »

gmueckl wrote: post #36
rectang wrote: post #25

Earlier quoted context omitted.

It's aspirational, jeez. Their eventual goal is to be a "fully featured DAW" as opposed to some other kind of tool. At least that's how I interpret it.

Aspirations are fine, but you need to separate aspirations from the status quo in your communications. The HN headline fails in that regard.

It doesn't seem like the person who posted it is the repo owner/maintainer...

Re: Meadowlark, a DAW written in Rust

#46

Post by emerged »

rectang wrote: post #25
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 aspirational, jeez. Their eventual goal is to be a "fully featured DAW" as opposed to some other kind of tool. At least that's how I interpret it.

So is me landing on Mars, but the buzz killers always call me out for announcing that I’m a fully featured Mars astronaut.

Re: Meadowlark, a DAW written in Rust

#48

Post by [deleted] »

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?

[deleted]

Re: Meadowlark, a DAW written in Rust

#49

Post by [deleted] »

ZoomZoomZoom wrote: post #23

It's also a bit disappointing to see another project chooses proprietary service for the communication. I joined #rust-audio:matrix.org almost a year ago and just figured the project was dead since the room isn't bridged and it's completely quiet there. Turns out everyone's on Discord. If you're a musician, sound industry professional or just a hobbyist, I invite you to join the Mixing room on the Matrix.org server (…

[deleted]

Re: Meadowlark, a DAW written in Rust

#50

Post by bambax »

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…

This is quite weird and unfortunate.

Also, does the world need yet another DAW? There are dozens of DAWs, some free, some not. Most of them are excellent; all of them let you use non-4/4 time signatures.

Post reply on HN