News for hackers. Stuff that matters.
Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @10:15AM (#32166079)
Do any of these browser projects support existing plug-ins?

A lot of people making music have spent $$$ on plugins, and just on the sheer R&D they've received, are going to sound considerably better than anything someone who is focused on writing a DAW can make.

Plus, from my own experience, I have 20+ years working with FLStudio and know the program inside and out. Abandoning that plus my investments in VSTs is simply a no-go.

So, good luck, but you've got some significant barriers to overcome.

Re:Show HN: I'm building a browser-based DAW by butwhywhyoh on Wednesday July 20, 2022 @12:23PM (#32168056)
Would you give this same critique to someone who was building a go-kart in their backyard for fun?

"Car companies like Honda and Ford have been around for decades, and those vehicles are going to drive considerably better than anything someone working in their backyard could make.

Plus, from my own experience, I've been driving these cars for the past 20 years, and abandoning that experience in how they feel and handle is a no-go.

So good luck, but you've got significant barriers to overcome"

[dead]
Re:Show HN: I'm building a browser-based DAW by tobr on Wednesday July 20, 2022 @03:20PM (#32170830)
https://news.ycombinator.com/showhn.html

“Show HN is for something you've made that other people can play with”. It doesn’t have to be a product, and I can’t see anything in the guidelines that precludes sharing “toy projects”. On the contrary, a “Show HN needn't be complicated or look slick.”

It’s up to the community to use upvotes to determine what’s interesting to the audience, not individual self-censorship of what might offend those “grognards”.

Re:Show HN: I'm building a browser-based DAW by RobbieGM on Wednesday July 20, 2022 @03:21PM (#32170853)
> "Do it in a browser" is not interesting enough.

I disagree. DAWs are huge pieces of software to begin with and doing high-performance audio work in the browser would be very impressive.

Re:Show HN: I'm building a browser-based DAW by ksm1717 on Wednesday July 20, 2022 @10:28AM (#32166241)
Yea what an idiot to not make this free proof of concept of a browser daw targeted at 20+ years power users
Re:Show HN: I'm building a browser-based DAW by lostgame on Wednesday July 20, 2022 @01:29PM (#32169225)
tomc1985 made an extremely valid point here, as any serious DAW user would agree - they did not imply the creator was an idiot, but that any DAW without plug-in support is, at best - a toy, and I will personally add that the concept of using a browser to record audio when latency and playback quality is already an issue with fully OS-native DAW’s.

Other than some side project just for fun, I absolutely see no practical use, application, or function the app can provide that Ardour (which is already open-source and free if you compile it) isn’t going to do infinitely better.

The author isn’t an idiot, quite the opposite, it takes a lot of effort to write even a simple DAW.

But the product makes no sense. The target platform is totally in opposition to the needs the tool requires to fulfill its purpose.

It’s like those people who run DOOM on their smart fridge. The creator isn’t an idiot, it’s just a waste of time outside of saying ‘I did this’ and nobody is ever actually going to choose to seriously play the game with that way.

There’s no need to be snarky like you’re being, it’s possible to make points without coming off like an asshole.

Re:Show HN: I'm building a browser-based DAW by Optimal_Persona on Wednesday July 20, 2022 @05:10PM (#32172365)
Thanks, you basically wrote what I was going to. In audio-production-land, the term DAW is generally understood to mean "real-time (single-digit ms latency) capable audio plugin host and audio/MIDI sequencer". Anything not checking all those boxes is interesting, but likely won't be "able to(n)" get a whole lot of "tracktion" from "avid" users. ;-D

I also need to note that users of free/cheap audio software can be some of the brattiest, most entitled and actively hostile users I've seen anywhere, based in my 20+ years on KVR, GearSpace, and other forums. Every dev in the space needs to have a thick skin and be ready for the "it would be great if only it..." to start rolling in.

Great to see people pushing the "envelope" of browser-based tech!

Re:Show HN: I'm building a browser-based DAW by lostgame on Thursday July 21, 2022 @04:57AM (#32177136)
>> Anything not checking all those boxes is interesting, but likely won't be "able to(n)" get a whole lot of "tracktion" from "avid" users. ;-D

They probably wouldn’t find that “Logic—al”…

(I couldn’t help myself, I’m a Logic user and you wrote it for me :P)

Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Wednesday July 20, 2022 @11:44PM (#32175527)
Have to applaud the Traktor reference in particular
Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @10:39AM (#32166383)
> Yea what an idiot

You are saying this, not me.

Re:Show HN: I'm building a browser-based DAW by ksm1717 on Wednesday July 20, 2022 @11:02AM (#32166738)
Yea I’m mocking you because if you couldn’t tell how annoying your obvious “constructive” criticism was going to sound, you’ve got some significant barriers to overcome
Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Wednesday July 20, 2022 @11:58AM (#32167632)
Not sure why you are being so hostile with this user, especially given his question/concern is valid (source: media production for over a decade).

Plug-ins are often the secret sauce for our workflows and styles, and prosumers/hobbyists dip into them as well. If your browser based DAW doesn't have, say, Izotope RX support, then that's a non-starter for a ton of people (especially podcasters). I'm not going to round trip between software on my computer and a browser based software, that's for sure. I don't have time for that nonsense.

Regardless of your opinion or how you feel about the above, your tone is needlessly hostile and unproductive.

Re:Show HN: I'm building a browser-based DAW by throwaway675309 on Wednesday July 20, 2022 @04:50PM (#32172137)
The difference is that you're coming across as needlessly aggressive and insulting... which is fine for Reddit but not so appropriate on hacker news.

Both they and I would both love to know if the developer behind this DAW has given any thought to how they might integrate with existing plug-ins such as VSTs, not an easy feat.

Re:Show HN: I'm building a browser-based DAW by cjaybo on Wednesday July 20, 2022 @11:18AM (#32167008)
If you know anything about music production, you'd know it's a very valid critique. Not sure why you took it so personally, though.
Re:Show HN: I'm building a browser-based DAW by thr0wawayf00 on Wednesday July 20, 2022 @12:04PM (#32167743)
It's also such an obvious question though, isn't it? You think that the developer pouring so much of their free time into a browser-based DAW wouldn't have considered the idea of supporting plug-ins at all?

People far too often approach projects like this with "this app is only useful for me if it does x..." and I think that framing is poor when someone is just exercising their passion on a project. I'd personally respond with "great, go build your own that supports your plug-ins. Have fun."

Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Thursday July 21, 2022 @08:25AM (#32178487)
> It's also such an obvious question though, isn't it?

Is it? I’m genuinely asking as someone who works in audio production. Plenty of people create tools for us in the podcast space, AI transcriptions for spoken word (premiere has a good one), new ways to automate typically manual processes for mastering, you name it. The thing is it is not a given that the person creating a solution has an audio production background and properly weighs the needs.

Plenty of engineers do work for or work directly for hospitals. Are you going to tell me that they might not overlook something a nurse or doctor might need? Because I assure you it happens in every industry when people come up with new tools and solutions, often because many actually don’t come from a strong background in the industry they’re making tools for. I value an outside perspective, don’t get me wrong. But it has its issues too.

It’s not uncommon and it’s fair for us technicians, the people these solutions are designed for, to ask questions.

Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @01:44PM (#32169480)
A lot of people have dropped their side-project in-browser "DAW" projects on HN, several of them did seem like they wanted to be taken seriously
Re:Show HN: I'm building a browser-based DAW by ksm1717 on Wednesday July 20, 2022 @11:35PM (#32175467)
Yea its obviously valid.. you think the dude just bossed up and made a daw for this crazy hostile build target without knowing how people use them?

I took it personally because all these hacker news retards want to nitpick a hobby project when a post like this (really cool, non-axios.com-tech-guy-libertarian-shit) shows up to feel like they have a big dick despite not being able to build something half as cool themselves

Re:Show HN: I'm building a browser-based DAW by zero_iq on Wednesday July 20, 2022 @12:47PM (#32168467)
tbf, it's pretty clear who he's calling an idiot, and it's not OP.
Re:Show HN: I'm building a browser-based DAW by micbuffa on Tuesday July 26, 2022 @05:21AM (#32236053)
Well, native vs Web, we already has this conversation about Word vs Google Docs ans now even Word is a web app built with web technologies, and can run in a browser. I'm part of the W3C WebAudio Working group, the core team that is making the WebAudio API at the heart of web apps that can do real time audio processing. Since 2011 we saw more and more impressive applications, and with ASM.js in 2015 and its successor, WASM in 2018, people started to port VST plugins, to compile very efficient DSP code written using some DSP like FAUST to WASM, etc. A Plugin format exists since 2015 (Web Audio Modules aka WAM), and some DAW that can record real time audio, support audio effects, instruments, etc. are now available. While they are not as feature complete as native DAWS, thousands of users record multitrack songs everyday and use many built in or external plugins. AmpedStudio can even use your native VSTs. I wrote some WAM plugins (guitar amp simulators) that are usable in AmpedStudio. It is possible to create very efficient WAM plugins in a minute using the FAUST IDE + some existing FAUST code (there are hundreds of examples on the IDE + on diverse open source GitHub Repos). You will find most effects, some instruments such as MOOG recreations etc.

Of course, the Web based DAWs and plugins are young, but some big actors like Roland (see https://roland50.studio/), Ableton (see https://learningsynths.ableton.com/), Propellerheads (they ported to the Web their VST synth Europa), Antares (the real autotune VST is available in the online DAW soundtrap.com).

Real time recording is operational without any hassle on Mac OS, and with some driver configs on Windows or Linux. You need to calibrate "latency compensation", that will automatically adjust the live recording audio to existing tracks.

Yes, online DAWs are close to GarageBand for example, in terms of features. But they also have some advantages : automatic sharing of projects, some DAWS even allow synchronous collaboration à la Google Docs, sharing a project is just sharing a link, and working together on the same project becomes really easy, no hassle for storing the audio files. Publication to spotify/deezer/youtube/apple Music is a click on a button. Most DAWS can be used for free. Etc. It's just the target user profile that is different: while Pro Tools/Logic/Ableton will target studios and pro users, these online DAWS are more for less exigent, more online connected people. Most projects are electronic music, etc.

I use Logic Audio, and I also use online DAWs. I heavily used ampedstudio during the covid lock down with remote friends... Then we roughly recorded / mixed some song projects, then I polished the final version by re-importing the tracks in LOGIC, but this was really for fine tuning things... AmpedStudio and soundtrap (I did not try bandlab) are very capable online DAWS.

Re:Show HN: I'm building a browser-based DAW by crubier on Wednesday July 20, 2022 @10:16AM (#32166089)
Let's make WASM VST plugins!
Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @10:19AM (#32166119)
My other thing is... why does something like this need to run in a browser? What's wrong with desktop apps?

I have FLStudio mobile and some other mobile DAW on my iphone and ipad. And to be honest, I never use them, other than as a tapping BPM counter. Do people actually feel productive tapping this stuff in on an iPad?

Re:Show HN: I'm building a browser-based DAW by mschuster91 on Wednesday July 20, 2022 @10:21AM (#32166148)
> What's wrong with desktop apps?

Shoddy support for platforms other than Windows, not to mention VSTs going out of support by the developers and then unusable when something changes (e.g. Apple dropping support for 32-bit x86 years ago).

WASM is at least a common denominator supported everywhere... basically Java just better.

Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @10:29AM (#32166253)
Bitwig's pretty good as a cross-platform DAW, from what I hear.

There's entire ecosystems of plugins out there. Yes they can be reimplemented but if the authors use the same quick algorithms as everyone else it's going to sound plastic-y and dull. IMO plugin dev is one of those things where every hour spent makes a cumulative difference in output quality.

WASM may be great, but unless they can run as their own binary in their own windows you're going to have browser overhead for each window, nevermind those of us that spread our DAWs out across multiple screens.

Re:Show HN: I'm building a browser-based DAW by stevenjgarner on Wednesday July 20, 2022 @12:49PM (#32168501)
Ummm ... Audacity is fully cross-platform (Windows, macOS, GNU/Linux and other operating systems) and open source [0]. ProTools (the elephant in the room) was originally developed (and still) on the Mac [1]

[0] https://www.audacityteam.org/

[1] https://www.avid.com/pro-tools

Re:Show HN: I'm building a browser-based DAW by cheschire on Wednesday July 20, 2022 @12:58PM (#32168676)
Audacity isn't available on iOS or iPadOS. This browser tool, however, is.
Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Thursday July 21, 2022 @08:31AM (#32178528)
Audacity isn’t a DAW. Powerful tool, been using it for ~15 years, but it isn’t a DAW and folks shouldn’t use it like one tbh.
Re:Show HN: I'm building a browser-based DAW by stevenjgarner on Friday July 22, 2022 @01:39PM (#32194802)
> folks shouldn’t use it like one tbh

I use Audacity like a DAW. Please clarify:

"Audacity is a free and open-source digital audio editor" [0]

"A digital audio workstation (DAW) is an electronic device or application software used for recording, editing and producing audio files." [1]

You can use Audacity to record, edit and produce audio files.

[0] https://en.wikipedia.org/wiki/Audacity_(audio_editor)

[1] https://en.wikipedia.org/wiki/Digital_audio_workstation

Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Friday July 22, 2022 @07:38PM (#32198451)
By the strictest/most literal definition yes, it is a DAW. But it does not do what people expect of DAW’s.

* no real time effects playback

* it doesn’t support VSTi’s (long standard and expected)

* no sequences

* can’t use MIDI controllers

It’s a fantastic platform for recording audio and post-processing, it is a terrible music production program, which even the most basic DAW’s can handle.

To make a video comparison, it’d an like an NLE that can’t sync audio/multi cam, has an unintuitive and semi-bloated UI, doesn’t support captions, and can’t support multiple timelines under one project.

Re:Show HN: I'm building a browser-based DAW by Arcanum-XIII on Wednesday July 20, 2022 @03:22PM (#32170858)
Except nearly all of them support both main desktop platform, so not exactly a valid critique. True Linux is often forgotten. But is there a real market there? And to my knowledge, Linux low level audio performance is quite bad, which doesn’t help.
Re:Show HN: I'm building a browser-based DAW by BizarroLand on Wednesday July 20, 2022 @04:41PM (#32172007)
The only thing I can think of would be that it would be great if you could easily record with people on the same interface over the internet. Maybe not live jamming or anything, since the delay would be murderous at best, but that it would be great to be able to have your drummer lay down a track at 3am and your guitarist lay down a rhythm to it at 7 and wake up and do vocals when you're ready instead of having to schedule time to all meet together.
Re:Show HN: I'm building a browser-based DAW by BolexNOLA on Friday July 22, 2022 @11:15AM (#32192834)
>why does something like this need to run in a browser?

Same reason I like Squadcast and other browser-based podcast recording software - works on (virtually) every machine, no one needs to download anything, cloud storage baked into it, easy for my other producers/colleagues to hop on and check things out, etc.

Re:Show HN: I'm building a browser-based DAW by virgil_disgr4ce on Wednesday July 20, 2022 @10:20AM (#32166135)
What's wrong with browser apps?
Re:Show HN: I'm building a browser-based DAW by fwsgonzo on Wednesday July 20, 2022 @10:35AM (#32166327)
Audio is real-time and performance is everything. Freezing tracks should take the least amount of time possible and no skipping should occur unless you are using the most complex modular VST out there. With WASM being like 1/3 of native and having extremely limited SIMD support I would probably expect it to not work at all for serious work.

Quite frankly, even native performance is often not enough.

That said, I can see it being relevant for learning audio, synthesis and how signal processing works. And of course, just for fun!

Source: Worked with DAWs for a decade. Also currently writing a paper on the role of native performance.

Re:Show HN: I'm building a browser-based DAW by awongh on Wednesday July 20, 2022 @11:22AM (#32167068)
I’ve played around with ableton before- im wondering what are the high-level aspects of a DAW that take up that compute? Off the top of my head if you have like 10 channels of synths, what in there is super intensive? What does freezing tracks mean and why is it so expensive?
Re:Show HN: I'm building a browser-based DAW by duped on Wednesday July 20, 2022 @12:21PM (#32168032)
It's not the high level aspects, but the low level ones.

Audio DSP is doing a lot of math. CPUs are good at it, sure, but modern synths and effects are legitimately pushing up against how much math a CPU core can evaluate in the few milliseconds you have to render (in the worst case, low latency realtime rendering time is actually dominated not by how much DSP you can do, but how long it takes to move audio from userland to kernel and out to the hardware and back).

Some of the DSP algorithms are really hard to optimize with SIMD, in fact most of the common audio DSP operations can't be trivially converted to SIMD forms (and when they are, they aren't N times faster for N more lanes). Filters are especially tricky because converting the math from one form to another changes the topology of the signal flow, which is only equivalent in the steady-state of non-linear and time-invariant filters. DAWs are using non-linear time variant filters that are being modulated in realtime, so your super fast SIMD optimized biquads might not sound as good as the converted SVF that can't be trivially optimized (there are tricks, but it's a game of tradeoffs).

And there's the other aspect of the scene that there's just a lot of bad or naive code out there. There is a lot of know-how floating around, but a lot of tools are designed by folks without it to begin with. That's a good thing because it makes a lot of interesting and cool tools, but it also means that institutional knowledge is kind of locked away. It doesn't help that some of the largest examples for newcomers (JUCE's DSP module, RAFX/Aspik with the accompanying text), as well as classic (and new!) textbooks teach people to do things in the least performant way possible, and those algorithms make it into production.

Re:Show HN: I'm building a browser-based DAW by logarhythmic on Wednesday July 20, 2022 @03:00PM (#32170570)
Thanks for the informative comment. Are there resources you would recommend for learning more about performant algorithms? At the moment I'm just messing around with JUCE
Re:Show HN: I'm building a browser-based DAW by tomc1985 on Wednesday July 20, 2022 @11:39AM (#32167333)
> you have like 10 channels of synths, what in there is super intensive

The synth itself. Samplers, hardware emulations, and effects can eat a lot of memory and CPU, to say nothing of a monster 100+ voice synth patch (very easy to achieve with unison, used in supersaw-type sounds)

> What does freezing tracks mean and why is it so expensive?

Freezing tracks means recording the output of that track to a WAV and using that output as a stand-in for the real thing. Freezing tracks isn't expensive, it's what you use when another plug-in is too expensive and you want to reduce your CPU load.

Re:Show HN: I'm building a browser-based DAW by mxmilkiib on Wednesday July 20, 2022 @12:19PM (#32168009)
The DPF framework is moving towards WASM build targets;

https://cardinal.kx.studio - web version of the VCV Rack wrapper Cardinal

https://github.com/DISTRHO/Cardinal/issues/287

Re:Show HN: I'm building a browser-based DAW by vnorilo on Wednesday July 20, 2022 @11:12AM (#32166894)
There's been some work on Web Audio Modules, including glue for prior native plugin frameworks like Juce.

https://www.webaudiomodules.org/

Re:Show HN: I'm building a browser-based DAW by lostgame on Thursday July 21, 2022 @05:00AM (#32177151)
Question; because I just don’t know - is it possible to wrap a VST host/bridge in WASM?