6 ms·
Show HN: macOS native DAW with Git branching model
I am working on building (and have made my first prerelease) for a Digital Audio Workstation with git like branching version control.
It's free for local use and paid for cloud syncing or collaboration.
- delgaudm 8mo agoI'm a voice actor, and I live in Reaper -- it's my "IDE" as it were. I like the idea of the git branching metaphor. Would you say that your DAW is primarily for musicians, or for more general purpose recording (i.e. a voice actors workflow)
- hpen 8mo agoI have built it because I'm a musician. That being said I am interested in serving my customers / community and am open to what features would be needed / what user experience would be desired.
- brcmthrowaway 8mo agoHow has your business been affected by AI?
- MomsAVoxell 8mo agoYou can already use git with REAPER right now, plain and simple. REAPER’s project files are all very git friendly. Simple add/commit/push, etc. Of course, if you’re going to be sharing a REAPER project in a repo, you should enable LFS, and have a smart project structure for your works. If collaboration through a repo, with tagging and branching, is part of your setups workflow, this already works quite well with REAPER projects. However, I have to say that since REAPER allows full control over literally years of recording sessions, the whole concept of having the ability to go back and forth through different versions of the art—form being recorded (music, vocals, etc.) is already well provided in REAPERS sample-accurate ‘reflog’. ;)
- mslt 8mo agoI’d recommend providing a lot more screenshots and information about how the core DAW functionality works in comparison to other DAWs. As is I can’t see enough about what this would feel like to spend my time downloading and trying it
- hpen 8mo agonice feedback. I'll get on that! Thanks
- QuantumNomad_ 8mo agoSome video recordings would be extra nice also, that shows the software in use on an example audio project. Including showcasing of how you work with the revision history and branches, and how it enables collaboration.
- hpen 8mo agoAdded some screenshots to the website.
- inatreecrown2 8mo agoCool idea but 16bit audio? I would not recommend anybody record at 16bit.
- zahlman 8mo ago> with git like branching version control. Honestly, as long as it's based on open, text-based formats, I could handle the Git part myself.
- greenpizza13 8mo agoWas working on this same idea (*working = ideating over). Was really dissapointed to see after downloading the app does nothing without an account. This seems totally non-required for local "free" projects with this tool.
- hpen 8mo agoCheckout the latest version. I have removed accounts for local use.
- import 8mo agoI am curious why it’s called DAW. There are no screenshots so hard to say anything Does it support VST, AU? Any support for midi? Which OS’s supported? Is this just a multi tracker recorder that has a git style storage?
- scelerat 8mo agoDigital Audio Workstation in the context of computer-based recording it's pretty common jargon
- QuantumNomad_ 8mo agoI think what parent commenter is asking is, does it do the things one would expect a DAW to do? I’m not expecting a whole Ableton replacement, but things like hosting plugins and working with MIDI is IMO fair to expect from any piece of software that wants to call itself a DAW.
- scelerat 8mo agoOh yeah makes sense
- hpen 8mo agoSo it has the default AU plugins that are bundled with macOS. I'm adding additional support for loading plugins. Eventually, I would like to add VST support but that's down the road a bit. It has basic midi support, can use a controller, or edit with keyboard.
- gyomu 8mo agoYou charge $10/mo but all your links for Documentation/Privacy/Terms/Support are blank.
- sjtgraham 8mo agoYou get what you pay for.
- stephenhandley 8mo agoI cannot imagine anyone who works with audio regularly would realistically consider replacing Ableton/Logic/ProTools/Reaper/etc with whatever recording experience this provides (no screenshots doesn't help your pitch). The versioning idea is interesting and something many musicians have to contend with as they work on songs. Personally, I wouldn't want the complexity of take-level versioning, but pinning audio and mix automation to a given mixdown could be useful for tracking the history of a song. It might be more effective to approach this as version tracking / collaboration layer around existing DAW formats rather than a full replacement.
- dostick 8mo agoIs it really a problem that needs solving? Or more of a solution in search for a problem. DAWs allow “track alternatives” which I use more than project versions. But I can’t imagine what would be unsatisfactory about project versions to the point of changing to another DAW.
- cluckindan 8mo agoIt is hard to take this software seriously without one-button algorithmic equalization and brickwall limiting to maximize loudness. Those are what professionals would need to really make their track ”pop”.
- joshka 8mo agoIf you haven't already seen it, see if you can find some screenshots of the UX for what Splice.com looked like before it pivoted to just being a sample / instrument selling site. It was kind of a git + dropbox type interface for actual DAW projects (Ableton and Fruity were supported IIRC). This was really cool and something that someone should bring back.