Guest
home
beatmaps
rankings
community
store
help
forum
  1. Forums
  2. osu!
  3. Development
  4. Feature Requests

Big Editor Update (Version History/AutoSave)

posted
Total Posts
6
This is a feature request. Feature requests can be voted up by supporters.
Current Priority: +591
PieInOblivion
124 posts
Joined November 2014
Topic Starter
PieInOblivion
Before A mod calls this a duplicate, my request is slightly different (From the ones I found)
The closest ones I found where:
t/23267
t/312710

My request Is similar of those but different and I thought needed its own post.

I sometimes make big changes to a map, then can't revert them because I forgot to save. That's where Auto-Save comes in at a set interval.

But what it you don't want it to save, because it's the most annoying thing in the world?
- That's ok! It's possible to disable it!
(I know that there are MANY autosave requests, but I'm just saying this to help paint a picture)


(This is the proper part of my request)
But what if you make some major changes and want to revert without having to re-do each note? What if you want to go back an Auto-Save? Well, with the new feature, YOU CAN! *Crowd Gasps*

This is a small snapshot I made in photoshop using the best base image I could find. Sorry it's Windows XP)
Here

That's pretty much the main part of my request.
Do you guys think this could work?
Roxy Lalonde
100 posts
Joined June 2014
Roxy Lalonde
I'd prefer this over other suggestions.

While a .osu text file is really efficient in terms of data usage (you can store hundreds of thousands of these before you come close to 1gb) you also need to consider storyboards, hitsound files, storyboard SFX/GFX, and skin elements.

For edit-heavy files (skin + SB + hitsound + video) autosave could quickly eat up a lot more memory than you'd expect.

Of course, for these EH maps you can implement the autosave versions to "stack onto eachother" which means that newer versions would only include any changes from the previous version, which means it wouldn't keep copying video/skin/sb if you're not making edits to such objects. Stacking, however would make any raw edits quite difficult seeing as you'd have to combine many stacks to create a proper version from X time. (osu! has been designed for easy raw editing, and this would make it harder)

If you decide not to implement the "stacking" system, versions would probably save around 12-13 video files which can cause catastrophic memory usage.

I have a computer with an 80 gb hard drive, and memory is precious when around 60gb of it is taken by development tools and games.
PieInOblivion
124 posts
Joined November 2014
Topic Starter
PieInOblivion

Proph Nobster wrote:

While a .osu text file is really efficient in terms of data usage (you can store hundreds of thousands of these before you come close to 1gb)
Actually, If the average size of an .osu text file is... say about 25kb, this would give us '41943.04' saves before you hit 1GB (In 1024 bit form). Thought I would just mention this for fun.

Proph Nobster wrote:

autosave versions to "stack onto eachother" which means that newer versions would only include any changes from the previous version
I was thinking more along the lines of generating a unique hash (Based on the file size and name) for each referenced file in a .osu. And then as you said:

Proph Nobster wrote:

which means it wouldn't keep copying video/skin/sb if you're not making edits to such objects.
Drum-Hitnormal
Beatmap Nominator
1,727 posts
Joined March 2011
Drum-Hitnormal
how about just a simple backup system where osu doesnt corrupt your beatmap (.osu) file when you encounter a blackout and PC gets shutdown unexpectedly?

the backup is just previous save.

Also pls dont make rate limit so low, i keep running into `429 too many requests` error while trying to upvote this...
Last edited by Drum-Hitnormal , edited 2 times in total.
DeletedUser_5153421
DeletedUser_5153421
Ooh you found the original, well of course. ctlr + s is ingrained in my muscle memory because as it is right now osu! editor could crash any minute. I wouldn't mind having to not have to be saving after each note placement, I don't see an issue in a backup either like Drum-hitnormal said cuz it barely take any effort/filesize to automatically save after each placement.
Last edited by DeletedUser_5153421 , edited 1 time in total.
McEndu
1,161 posts
Joined March 2019
McEndu
Initializing a git repository is a straightforward solution as I would say, but a lot of things would need to be done manually, and it could cause some trouble if you accidently uploaded without deleting the .git directory (like with lot of changes to storyboard)
Please sign in to reply.

New reply

0
1 / 6