Audiomass is an audio editor, meaning that it works with already existing files that might need to be cut, edited, cleaned, or filtered, or in case where one has multiple stems put together to be mixed.

Think of it a bit like vector vs pixel editing. OpenDAW is vectors (music info), audiomass is pixels (music data)

I 'll be heading off soon, so decided to write some features included in this release that might not be apparent right away (still working on improving the UX).

- Drag n drop multiple audio files into multitrack = multiple channels automatically created

- Double click on a waveform box in multitrack, opens it in the original audio editor (for more precise editing)

- Copying (command+c, or shift+c) works between multitrack and regular editor. So for example, you can open a file in original editor tweak it, and then copy all or part of it and paste it in multitrack in a specific channel.

- Most effects have already pre-made presets to make them easier to use

- You can make your own effect presets by clicking the 3 dots after having made a modification in an effect (stored in localstorage)

- Zero crossing selection is under "Edit"

- There is a tempo tools section in View. You can automatically detect tempo of a track, tap to guess a tempo and play with metronome

- There is also an id3 tag viewer (for mp3 files) there as well

- You can right click or press M to add markers (makes it easier to highlight sections of a track, especially when working with longer audio tracks)

- Seamless Loop tool (under Edit): crossfade preview, silence trim, repeat loop, open loop in a new editor tab.

- Offline/PWA support: Help > store offline version, will open a new page that will trigger a service worker that will make the site work offline as well.

- Session export as .amss file for multitrack. If you aren't done working on a session you can export all of its audiofiles and configuration in an LZMA compressed container file (will still be pretty big though). For single audio mode, mp3/wav/flac export is available.

- Pressing X in multitrack when 2 waveform boxes overlap, makes them crossfade smoothly (denoted by an "XF" label at the top right - undocumented behavior but can be quite useful, will keep improving it)

- You can open the menu by pressing the ~ key and then navigate it with arrow keys (left/right for sections, bottom up for selections, enter to trigger an action and esc to close) for a tiny bump in speed of getting things done. Similarly the time controls are clickable and open a mini menu where a time can be specified to jump quickly to it (arrow keys to go between minutes/s/ms)

And finally my favorite feature of them all (though not a new one per se),

- In "View" select "Frequency analyzer" or "Multitrack mixer" and then press the dock button. Audiomass supports the ability to extract elements of it into new pop up windows. So you could have parts of the application on a different monitor keeping the main app in the main tab. It's a very old trick, but I find it kinda cool :)

Thanks again and hope you enjoyed the sample music! (edit: formatting)

Did you load it into multitrack, or the regular editor? (in multitrack it does not scale currently, but working on it). On regular editor it should in theory try to zoom.

There is a pyramid cache mechanism for long files, basically it tries to optimize with simple heuristics how many peak-lines to show for every zoom level. The renderer is pretty dumb right now - just old-school 2d canvas "ctx.lineTo" calls - no gpu, so enormous files can really make it slow, this is the reason for the drops (to ease load). So it might be dropping way too many samples in this case and then not switching properly to the next cache level because the zoom to duration/length ratio is enormous.

I 'll look into it. Thanks again

When I started developing I was a little frustrated with how bloated the web felt back then so I took that direction, it's much better today though and it's no longer an issue, but I still find it fun to impose these constraints and try to work within or around them (there's this fascinating concept of constrained creativity)

Sorry still working on improving the UX :)

EDIT: There's a short video here - https://x.com/pkalogiros/status/2053492761350046032

For multitrack sessions, there is the ability to export to a .amss file that contains all the settings, markers, tracks etc. For single track edit... it would just crash right now. There is already a feature for caching audio tracks in indexeddb (it's under >File), but honestly it's not a web api I have found to be super reliable. I don't blame the browser developers, because I 'm sure if it was more reliable certain websites would put it to use storing gigabytes of trackers on the user's machine :). For this reason, I haven't made it auto-save the session automatically yet, trying to be a good citizen on the user's computer, maybe that will change in the future if there's a strong need for it.

Also, right now there is no backend, once it loads there are no more requests made to the server, so it's bound to frontend limitations. This is by design, I want it to be an app that respects users, doesn't upload or leak information, no ads, etc, even if it means getting a small hit in functionality in other areas.

I think of it like photopea/pixlr are to photoshop. Quick and easy to use, get you at 90% of the way. If somebody wants to do a serious operation, then by all means go for a paid desktop pro-daw solution :)

edit: reason

On an unrelated note, I'm a little surprised there is no good open source web audio tracker (like Renoise but for the web) out there yet...

It's using dom to render the multitrack waveform boxes currently so I would assume after a certain point it might start to slow down a bit. In the future might switch it all to be webgpu based to avoid such limits.

Comments URL: https://news.ycombinator.com/item?id=48258015

Points: 553

# Comments: 120