4 ms·

Audacity runs surprisingly well in the browser

20 points by em3rgent0rdr 3y ago

em3rgent0rdr 3y ago
https://wavacity.com https://wavacity.com
kelvie 3y ago
I swear this runs and loads faster than on my Linux desktop last I used it (I use ardour mainly now)
pvg 3y ago
Recent big discussion with author comments: https://news.ycombinator.com/item?id=37356497 https://news.ycombinator.com/item?id=37356497
dfabulich 3y ago
I tried to record audio in it with a nice microphone, and it was illegibly garbled. (It’s probably unfixable.) I believe you can use it to edit audio, but it doesn’t work with a microphone.
- solardev 3y ago
  Why unfixable?
  - ComputerGuru 3y ago
    Probably because of a lack of proper realtime audio due to how the audio input layer was ported, but that's hypothetically fixable by changing the architecture.
solardev 3y ago
I wonder if we'll ever see a move towards "headless" apps that have the business logic written in whatever language(s) shared as libraries and APIs, but each platform would then be able to write its own UI frontend in its native stacks. In the case of Audacity, that could mean all the audio processing stuff in WASM but the UI could be done as a traditional web app instead of a ported canvas. Just a thought.
- smogcutter 3y ago
  Wasn’t that essentially the original intention for x-windows?
  - solardev 3y ago
    Isn't that more like a VNC type thing where the server renders the bitmaps and sends them to the client? That's not really the same as a native Android app or a Javascript web app or a ios app being able to share the same libraries while having bespoke UIs. If anything X encourages the use of the same UI across different devices, which is the opposite of the way real users ended up using apps (with different interfaces for desktop, tablet, mobile, and watch).
  - jauntywundrkind 3y ago
    Debian's x11-apps has a collection of what I think of as pretty old-school-ish apps. They all feel monolithic: the app is both a backend and front end. There is no decoupling, where the same headless app has different possible front ends. An example of a popular headless app is neovim. You can run it in headless mode, and then connect different gui clients to neovim. A lot of the projects here are good examples of independent clients: https://github.com/topics/neovim-guis https://github.com/topics/neovim-guis
nxobject 3y ago
[dead]

20 points by em3rgent0rdr 3y ago

em3rgent0rdr 3y ago

https://wavacity.com https://wavacity.com

kelvie 3y ago

I swear this runs and loads faster than on my Linux desktop last I used it (I use ardour mainly now)

pvg 3y ago

Recent big discussion with author comments: https://news.ycombinator.com/item?id=37356497 https://news.ycombinator.com/item?id=37356497

dfabulich 3y ago

I tried to record audio in it with a nice microphone, and it was illegibly garbled. (It’s probably unfixable.) I believe you can use it to edit audio, but it doesn’t work with a microphone.

solardev 3y ago
Why unfixable?
- ComputerGuru 3y ago
  Probably because of a lack of proper realtime audio due to how the audio input layer was ported, but that's hypothetically fixable by changing the architecture.

solardev 3y ago

I wonder if we'll ever see a move towards "headless" apps that have the business logic written in whatever language(s) shared as libraries and APIs, but each platform would then be able to write its own UI frontend in its native stacks. In the case of Audacity, that could mean all the audio processing stuff in WASM but the UI could be done as a traditional web app instead of a ported canvas. Just a thought.

smogcutter 3y ago
Wasn’t that essentially the original intention for x-windows?
- solardev 3y ago
  Isn't that more like a VNC type thing where the server renders the bitmaps and sends them to the client? That's not really the same as a native Android app or a Javascript web app or a ios app being able to share the same libraries while having bespoke UIs. If anything X encourages the use of the same UI across different devices, which is the opposite of the way real users ended up using apps (with different interfaces for desktop, tablet, mobile, and watch).
- jauntywundrkind 3y ago
  Debian's x11-apps has a collection of what I think of as pretty old-school-ish apps. They all feel monolithic: the app is both a backend and front end. There is no decoupling, where the same headless app has different possible front ends. An example of a popular headless app is neovim. You can run it in headless mode, and then connect different gui clients to neovim. A lot of the projects here are good examples of independent clients: https://github.com/topics/neovim-guis https://github.com/topics/neovim-guis

nxobject 3y ago

[dead]