The continuation of the replayEditorV2. Old software did not work properly, this one should be better.
Requires 64 bit Windows.
Requires Microsoft Visual C++ Redistributable 2015-2019
Download both if you don't already have:
x86: vc_redist.x86.exe
x64: vc_redist.x64.exe
You can find all the downloads on the releases page
Or use this direct link to .zip file: https://github.com/thebetioplane/osuReplayEditorV3/archive/beta.zip
Extract it and run the .exe. The first time it runs it will prompt you to edit your settings file. The settings file should be edited to point towards your osu! installation. The application will stay up to date with this repo unless the "update_url" setting is changed or deleted.
This repository is binaries only. For the source code please use this other repo:
https://github.com/thebetioplane/osuReplayEditorV3_SRC
Selections work off a starting frame (mark in) and an ending frame (mark out) shown by two triangles. There are two ways to get this selection. The first is to just click and drag while the tool is set to "select" which draws a box. Any frames inside this box are selected. The second is to scrub (A / D) until the cursor is where you want the mark to be and then press the "Mark In" or "Mark Out" buttons (or I / O keys). Changing the key presses will affect all marks in your selection -- all marks between mark in and mark out.
A middle mark (white) gets created automatically when both marks are set, but fine tune with with mark mid (M). This mark you can click and drag with your mouse to move the path of the cursor. The algorithm is a weighted average based on distance: mark in and mark out are locked in place while the marks in between are pulled depending on how close they are to mark mid.
If you encounter a bug then please tell me about it using the Github issues page. It is possible that your bug is already reported as well. If the program crashed then please also attach or copy/paste the contents of the "crash.log" file that was created.
If your bug is related to the accuracy analyzer, then also attaching the "accuracy_analyzer.log" file after running Help > Analyze Acc Trace will be a big help for diagnosis.
The replays produced are designed to be read and played back by osu! client successfully, but please advise that the .osr is not a 100% accurate representation of one that would be produced by the game. For example, the replay hash, online id, seed, etc. are not guaranteed to be correct for score submission. This is not designed to be cheat software.
Please see: https://github.com/thebetioplane/osuReplayEditorV3_SRC