Storing the event history of the project, so I could “undo” even if I reopen the project would also be good enough, but this would mean storing more data, so I don’t think this is a good solution for technical reasons. You can sell this internally by labeling it as an added feature rather than revering something.ģ. For me, this would be an even better solution than opting out. ![]() If turning the feature off is too hard for some reason, could you then add explicit snapshots or save points? Currently you can revert to earlier revisions, but the save points are pretty randomly chosen, and might not match a good place to revert to since you might lose important stuff, such as recording another track. Why not make this a choice when creating a project?Ģ. I didn’t do this enough times to know if it is always the case, though.Īlso, it seems that there is some a-b testing going on, as one of my collaborators swears that she still gets the old version when she creates a project.ġ. ![]() ![]() I don’t know if this also means I miss out on other features, but it seems that it at least is possible to create new projects with explicit save functionality. It seems that when I create my Soundtrap project by clicking “Open in Soundtrap” in Noteflight, I get the old style project with an explicit save button. But to be constructive I have some suggestions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |