vltmrkls

no roadmap... maybe i should work on a space-map ;D given the feedback so far it might be a good idea focus on MIR and optimise audio analysis and don't fall for the audio plugin trap. thanks for your feedback, very much appreciated!

i love tackers but audionaut is not a tracker. it's a timeline-based multitrack editor in the Sound Designer II tradition: regions and playlists rather than patterns and pattern rows.

thanks for jumping in and clarifying. audiomass is very impressive and i don't dare to do web since i am a c++ dinosaur ;)

it's a personal preference, i have been using JUCE for decades and it's been very reliable and stable with a well maintained forum. To be honest, i didn't even look the other way.

thanks and agreed, the pipeline side is easy to miss.. i ll put it in a more prominent place in the README

Thanks! Regions yes, labels not yet.

Good idea on features.md. The manual has it all, but a one-page list is easier to find, for people and for LLMs. I'll add it.

thanks paul, i am very humbled to get a comment from you.

aight, flatpak is on the list.

let's hope audacity and audionaut will happily co-exist and learn form each other.

an interesting use case... the analysis could detect rhythmic or not and then edit the rhythmic parts away. i will look into, added to my backlog. thanks for your feedback!

to be honest i was not planning to add features like that but it's very tempting. Supporting OSC is easy but a proper and useful mapping of parameters will take more brain work. i used OSC way back with PD and Reaktor.. the network layer adds latency with is ok with video sync... i have to revisit, it's years back.

thanks for your feedback, i added this topic to my backlog.

the audio callback is lock free and the dsp is vectorised. i think you can expect very good performance. there is a dsp load meter implemented that displays spikes in the load. anyways... adding benchmarks is in my backlog.

thanks so much for your feedback!

- context menu file import is a no brainer, added to my backlog.

- keyboard shortcut for split is command+e

- automatic crossfade when dragging usually works with the shift modifier key, added to my backlog

- envelops: this feature was requested by another user already, so top of my backlog.

- effects... yes, of course. i will not implement the in place processing but insert and send effect like it's done regular DAW. so stay tuned.

you could edit anything automatically. import -> analyse -> auto edit -> assemble -> export. this what the prototype in python used to do. the result however often needs small edits and audionaut's UI is supposed to help with that.

i have a backlog but no roadmap. audionaut is very precise when it comes to timing if that's what you mean or what's your use case?

thanks. it's not a DAW just yet ... i need plugins for my own music so plugin support is on my backlog. experience tells me that it's not trivial, latency compensation is tedious and dealing with countless plugins and it's formats opens a box of worms.

i have not benchmarked the playback yet. the performance should be industry standard an not a concern.

Hi, i finally feel confident enough to announce Audionaut. It's been 3-4 years in the making and my initial motivation was to edit my own multi-channel recordings with the old Sound Designer II workflow (create regions, drop to a playlist, export playlist, done). It got a little bigger now and the most current feature is the agent editing, which is imho very useful since you have the UI which always provides transparency.

To try the agent part with Claude Code (app and Node 18+ installed):

  claude mcp add audionaut -- npx -y audionaut-mcp

Edits land in the open project as one undo step each, and saving stays with you. On macOS the app is sandboxed, so keep projects in ~/Music.

Downloads: https://audionaut.app/download.

any feedback is most appreciated