I’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
Some 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.
I 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.
I 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.
Is 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.
I'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)
I 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.
Was 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.
It 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”.
I’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
nice feedback. I'll get on that! Thanks
Some 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.
I 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?
Digital Audio Workstation
in the context of computer-based recording it's pretty common jargon
I 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.
You charge $10/mo but all your links for Documentation/Privacy/Terms/Support are blank.
You get what you pay for.
I 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.
Is 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.
> 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.
I'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)
I 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.
How has your business been affected by AI?
Was 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.
Cool idea but 16bit audio? I would not recommend anybody record at 16bit.
Ah good catch! I'm adding 24 bit as we speak!
Are we talking to a bot?
It 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”.