Please note: I am not supporting any of the following programs. I have been notified numerous times that the osu! BPM Changer and AR11 Maker don't work and there are no current plans to fix them. I have removed most download links whose projects only remain here to serve as resources for future projects.
Forewords
A couple of months ago I deleted my forum posts containing my previous projects because there was an issue of the management of a few situations which caused my retaliation. I won't go into depth, but I think my b**ching should probably come to an end.
To everyone saddened, disgusted, or repulsed by the disappearance of my projects and the direction I took regarding this matter, I'm sorry. I know several people used the programs and I handed out the programs manually on request during this period of time.
This is my attempt at regaining the community's trust that I threw away.
I had planned for a long time (since the start of my deletion) that I would consolidate my re-released projects into one forum thread to not cloud the development forums with my programs and minimize the length of my posts.
All my projects will henceforth be released in this thread.
osu! Input Delay Remover
Borderless Windowed mode in osu! has some input lag issues. This program applies Microsoft's workaround detailed at http://support.microsoft.com/kb/2908279 .
I wanted to release this a long time ago but never found the time/motivation to build a program, so Avail took up the challenge and built it! I am releasing this application with his permission.
This application requires Administrator privileges to work properly (Right click -> Run As Administrator).
osu! Replay Analyzer (preview)
What fun would it be without first releasing preview of a project Dukambe and I have taken up for the past couple of months now? Keep in mind this is not a finished product - it's not even alpha yet and there's at least a couple more weeks of coding I want to put in before I release it, so I won't open source it just yet.
So why release a preview? To grab some feedback (mostly ideas) and invoke interest, so don't hesitate to give me your criticisms and ideas - at the very least they'll be added to our issues so we can work on them soon :-).
Expect unexpected results.
Special Thanks
Dukambe - Co-Founder? Co-Developer? Many commits were pushed :3
Interested in helping out? If you have Git and C# experience, PM me.
osu! AR11 Maker
- Decreases song tempo by 33.33%, inverse of the DT tempo gain.
- Recalculates beatmap bpm and hitobject timing to reflect this change.
osu! Replay API
This is for the developers out there itching to dip their hands into osu!'s replays. Allows you to load and save replays.
osu! Beatmap API
Yes, I am aware of the existence of the osu! SDK. Unfortunately, for the purposes of the osu! Replay Analyzer and a few other project, the osu! SDK was insufficient. This is a (mostly) complete Beatmap API supporting up to V12 and lazy V13 maps (osu! mode only). The goal is to completely emulate the osu! SDK (and yes, I have used it for TP calculation for o!RA with only minor required changes).
Allows you to load and save beatmaps without classifying your program as an osu! plugin.
osu! Beatmap BPM Changer
Many requested this to be re-released again, so here it is. I haven't worked on it, so .ogg song support is not currently implemented. Changes the BPM of the beatmap and song.
Extra Short Information
Just in case you couldn't follow the video, here's the most important thing you need to know:
When you input the BPM, you may input it as a function of the original BPM. For example:
If your original BPM is 200 and you wanted to change it to 300, you could input:
Which will be translated as new bpm = original bpm + 100.
Or, if you wanted to halve the BPM, you could input:
Which will be translated as new bpm = original bpm / 2
This is not required, however you may experience unexpected results with multi-bpm maps using a flat BPM value.
When you input the BPM, you may input it as a function of the original BPM. For example:
If your original BPM is 200 and you wanted to change it to 300, you could input:
+100
Which will be translated as new bpm = original bpm + 100.
Or, if you wanted to halve the BPM, you could input:
/2
Which will be translated as new bpm = original bpm / 2
This is not required, however you may experience unexpected results with multi-bpm maps using a flat BPM value.
If you have any program requests, let me know however I cannot guarantee that I'll work on them before 02/07/2014, at which point my time is going to be taken up by the replay analyzer (so make the requests small please :-) ).
I want to fix up my previous projects slightly before re-releasing them, but the post will be bumped when/if that happens. Do not expect a new forum post with every update I release, only for new projects (or project release transitions).