There should be an option to "Make Draft Available Offline" which would work much like Google Drive services do (their methods of dealing with collaborative works’ conflicts can also be modeled). Once this is enabled, if Audiotool can't connect to the server, which Next already checks for, then save user changes locally. To avoid collaboration conflict, either this feature could only be for solo works or resolve to ask the user about conflicts when they're online again (have all collaborators confirm to reach a single, unanimous decision)
Comments (22)
Ooo, that will be great for me.
fun! c;
Sorry to bring this back up after such a long time, but would this be coming anytime soon...?
Especially for those of us who live in the US where the threat on net neutrality is very much a reality, it'd be a very beneficial implementation. What's more, is that there's still a large divide between those who have access to the internet and those who don't. And with the possible death of net neutrality, this is only expected to grow worse. I, even don't really have good access to the internet at the moment and haven't been able to use Audiotool as much as I'd like to because of it.
based on the implementation in Google Drive, I could imagine that this isn't a difficult feature to implement, but that's up to the real developers to dictate. Just a thought.
Pleaseee
Aww, fair enough. At least I'm getting internet this Friday.
But who knows how the FCC vote will turn out.
I can code it for the devs and for the community (with permission from Andre).
do it anyway. Andre (if I read correctly), said that the reason why it hasn't been done yet is because of some difficulties. Code it, and then try to get it approved by Andre and the other Admins.
You seem to be very proficient in coding, so I'm sure your version of it would be very appreciated by the community.
Yes, please, that would be incredibly helpful, especially right now.
If you can make a Chrome Extension that injects JavaScript into next.audiotool.com I think it'd work
I can help out a bit if you need it.
Oh, rip...
Well, there's that
Will it be nice to work offline... I don't know your backend but maybe now with html5... NodeJs and Electron (whatever) :P put some parts of the app on client side would be great...
@inspiration1738 @apollo try again now, after it's been released
Audiotool offline better come sometime couse i want to work anywhere anytime. You cant do that where you don't have WiFi .
A problem could be that having an accessible offline app means that it has a chance for direct sample copyright. Or on the flip side, no access to samples. Audiotool's Sample database is all online. The only possible way to allow for use of samples (even just drums) would be to enable uploading/linking samples directly from the computer. I'm not saying this problem couldn't be resolved, but simply that it's a large problem that so far, with the new sample rules, has been somewhat fixed.
I guess @apollo 's "Make Draft Available Online" would make the samples available that are already in use. That would be better than no samples.
I guess you mean to make the (Browser-)App offline-capable rather than creating a standalone application.
One major problem might be to handle updates on the server side. After re-connecting to the server the app might be incompatible.
Right-eo! If I understand correctly, unsaved drafts are saved in the browser cache/storage so that they can be reloaded without being accessed from the server. The only components needing to be accessed are device models, textures, and the basic Audiotool functionality.
This means that a user could feasibly have "branches" of projects that can be worked on offline and later merged/overwrite their online counterparts.
Samples would be also saved to the browser storage (ones loaded online, that is) and perhaps all user assets? Favourited and uploaded
Right, Chrome on platforms other than macOS already offers the functionality to "install" web applications to the computer through PWA (Progressive Web Applications), furthermore, if Audiotool ever decides to go the mobile route, the same would be true for the Add App to Home Screen, which is no longer a shortcut, but an integrated application using PWA principles.
As for updates, I'm not familiar with the inner functionality of Audiotool, but it would make sense for devices, their respective parameter settings and connections, to be future-proofed in a way that reduces frequent breakpoints. Perhaps agreeing on a fixed standard and parsing that data in JSON?
@andremichelle Ah, I see, that makes sense. I know that in order for Google Drive to be fully capable with offline support, you often have to run a Chrome extension. Perhaps that might be an option. Also, with sites that deliver offline content such as Netflix and other streaming platforms (even Google Drive for mobile) the user has to flag certain content they want available offline, then there is a download process. Also, I know that with Netflix (probably not for compatibility but for data consumption, however) offline content expires after a certain amount of time. This principle can feasibly be used to maintain compatibility.
Just some ideas to consider
Ah, you are completely right. I trust you all would give it its due diligence. Hopefully the discussion may have shed some light on potential implementations though c;
has anyone made even an unofficial offline version?
I'd be pretty surprised.