This version completely overhauls the File-Utils tab, where you can now:
* Automatically detect BPM and Offset, with visual sections
* This should hopefully be able to replace ArrowVortex. Looking for feedback on how well it works.
* If you have a map with multiple BPM sections, just apply one first, then save, then apply the next and save to a different file.
* Several plots of intermediate data, so you can verify onsets and fine-tune bpm, including:
* Detected note onsets
* Likely beat positions
* Beat positions according to determined BPM and offset
* Error margin for offset
* Quick buttons to double/halve BPM or shift offset
* Preview audio with clicks to verify alignment
* Create `.synth` directly from `.ogg`
* No more looking for where the editor saved the initial file
* No more issues with the editor writing over files with identical names
* Replace audio file, so hopefully no more issues with the editor not properly replacing it
* Edit other metadata (including cover image)
![edit section](https://github.com/adosikas/synth_mapping_helper/assets/3721366/764d7888-d42e-478e-a0bc-7cbe2e37726e)
![bpm section](https://github.com/adosikas/synth_mapping_helper/assets/3721366/15f544ee-c484-4390-87c9-bdd27393d8a8)
Zoomed in on the beginning:
![zoomed in on beats](https://github.com/adosikas/synth_mapping_helper/assets/3721366/f97976dc-bcb4-406b-96ae-e6c8581df15f)
Above you can see that while the detected 115 BPM work ok, if I override it to 76.667 (2/3 of 115), the major onsets line up better below (offset was automatically recalculated for the override BPM).
Note that this required working in 1/3 and 1/6 throughout the map instead of 1/2 and 1/4, so YMMV.
![with bpm override](https://github.com/adosikas/synth_mapping_helper/assets/3721366/32bf33ee-14ea-4a85-924a-a0c044a46544)
No need to suggest the following things:
* Coverting any audio to `.ogg` (planned)
* Adding or removing silence before/after the audio (planned)
* Automatically saving multiple files based on BPM sections, for later merging (planned)
* Automatic warping (looking into it)
* I think I already extract all the required information, let me know if you got _concrete_ ideas on how to actually do it
* Automatic (timing) note generation (never going to happen)
* While incredibly useful for veteran mappers (especially for maps with "weird" tempo), I unfortunately foresee this would eventually be abused to flood the community with low-effort maps. Sorry.