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

Show HN: Wavvy – web-based audio editor (Audacity port)

wavvy.app

Post reply on HN
Print view View original

81–90 of 115 posts

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#81

Post by tuckerpo »

lukasb wrote: post #62
ClawsOnPaws wrote: post #38

Earlier quoted context omitted.

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

I'm surprised at the pushback against ClawsOnPaws here. Why would you not want to make your apps usable by as many people as possible?

I'd be interested to see the man-hours-needed : people-helped ratio when it comes to user accessibility. There's certainly a threshold where it simply doesn't make sense to put in a man year's worth of work to cater to a proportionally very small percentage of the population.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#82

Post by hutzlibu »

naet wrote: post #74
ClawsOnPaws wrote: post #38

Earlier quoted context omitted.

I feel like I should preemptively apologize and I'm really not trying to knock the project in any way, and the achievement is pretty epic, but those who have seen my username on this site before know what's coming, especially in regards to people seriously considering using WX Widgets on the web... This app is inaccessible. Audacity on its own is already a bit difficult to use with a screen reader, but sadly, this po…

This may sound insensitive, but accessibility isn't usually the #1 concern when developing new projects. It is usually tacked on later in an update because it isn't a core feature and it affects only a small subset of users. Rather than encourage everyone to never use WX widgets for any reason in a website, maybe you should be encouraging people (or working yourself) to add this accessibility feature.

". It is usually tacked on later in an update because it isn't a core feature and it affects only a small subset of users"

But thats not optimal, right? But most do not care, as long as they are not part if that subset.

I mean, I find it hard to care too much either, when my main concern are all the missing and buggy features, that needs fixing first..

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#84

Post by robocat »

mb7733 wrote: post #68
dspillett wrote: post #60

Earlier quoted context omitted.

Not the sort of safety issues I think you mean, but there have been some rather questionable behaviours from the current owners in the last year or so. A quick search for Audacity here or elsewhere will find the details.

I'll save everyone the quick search. They added really basic opt-in telemetry, and then removed it after an out-of-proportion outcry.

Good write-up here: https://arstechnica.com/gadgets/2021/07/no-open-source-audac...

It wasn’t clear it was opt-in (although maybe the code was clear?).

Either way, adding telemetry (especially to open source) is obviously going to cause a ruckus, so they obviously mishandled the situation.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#85

Post by km3r »

hutzlibu wrote: post #82
naet wrote: post #74

Earlier quoted context omitted.

This may sound insensitive, but accessibility isn't usually the #1 concern when developing new projects. It is usually tacked on later in an update because it isn't a core feature and it affects only a small subset of users. Rather than encourage everyone to never use WX widgets for any reason in a website, maybe you should be encouraging people (or working yourself) to add this accessibility feature.

". It is usually tacked on later in an update because it isn't a core feature and it affects only a small subset of users" But thats not optimal, right? But most do not care, as long as they are not part if that subset. I mean, I find it hard to care too much either, when my main concern are all the missing and buggy features, that needs fixing first..

Accessibility, like globalization, expands your market, and should be part of a long term strategy. But when building out new projects, its severely slows down feature development. Both should be seen as tech debt, but tech debt is not evil, just like debt is not even. You are borrowing from the future for present day benefits. Used wisely and you can create a successful project that can afford to spend time on accessibility. Waste too much time on accessibility to start and you may burn through all your resources before seeing any success.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#86

Post by hutzlibu »

km3r wrote: post #85
hutzlibu wrote: post #82

Earlier quoted context omitted.

". It is usually tacked on later in an update because it isn't a core feature and it affects only a small subset of users" But thats not optimal, right? But most do not care, as long as they are not part if that subset. I mean, I find it hard to care too much either, when my main concern are all the missing and buggy features, that needs fixing first..

Accessibility, like globalization, expands your market, and should be part of a long term strategy. But when building out new projects, its severely slows down feature development. Both should be seen as tech debt, but tech debt is not evil, just like debt is not even. You are borrowing from the future for present day benefits. Used wisely and you can create a successful project that can afford to spend time on acces…

I mainly agree, but does the numbers of blind people really justify it economic wise?

I allmost see accessibility as charity. I want to add it to my apps, mainly because it is not nice to ignore people needs(and who know, with bad luck I might end up in that group one day), but not because I expect great monetary returns.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#87

Post by zeandcode »

jijji wrote: post #53
kethinov wrote: post #21

Now we just need to wrap this in Electron so we can run it on desktop! ;)

The OP mentioned this is a part of Audacity, so hopefully you were being sarcastic, but you can already do apt install audacity if you want a desktop app, as it already exists in the form of Audacity

This can't be better, another level

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#89

Post by eurasiantiger »

swyx wrote: post #72
mb7733 wrote: post #68

Earlier quoted context omitted.

I'll save everyone the quick search. They added really basic opt-in telemetry, and then removed it after an out-of-proportion outcry.

i dont understand privacy maniacs. have telemetry in from the start, nobody bats an eye. add it later, everyone freaks.

In the first case, intentions are clear from the start, so user trust can be built.

In the second case, intentions have been hidden or they have changed, which obviously erodes user trust.

Re: Show HN: Wavvy – web-based audio editor (Audacity port)

#90

Post by radarsat1 »

qolop wrote: post #29

Are there terminal based keyboard first audio/video editors? Sort of like vim but for multimedia.

probably not what you're looking for but you might enjoy reading about Snd if you're not familiar [0].

side note, such a fun list of abandoned projects here [1] and here [2] to browse through.. many sadly broken links but i remember checking some of them out back in the day. there was so much activity in the open source audio sphere back in the early 2000s.

[0]: https://ccrma.stanford.edu/software/snd/snd/snd.html

[1]: http://www.linux-sound.org/one-page.html

[2]: https://wiki.linuxaudio.org/apps/daw_apps

Post reply on HN