Skip to content

Add tip for using BeatTimer in basic audio mapping guides #635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

web-dev-sam
Copy link

@web-dev-sam web-dev-sam commented Jan 2, 2025

Some time ago I created a website that tries to take all the work out of syncing audio for mapping. I made the project for fun and to test my dev skills. Since then people loved it and some are using it regularly for new maps. For the future I also plan on adding audio normalization so that BeatTimer takes away step 4 aswell (see changes). (Edit: Volume Normalization was added)

The application works completely locally using ffmpeg-wasm so no login or hosting is needed on my part. It would be a shame if people don't know about it and lose the time benefit. Or for some installing Audacity could also be a challenge stopping them from mapping (audio-synced maps). So I propose to add that tip into the docs and would be happy if the work helps more people out there.

This is the repo of the website (also mentioned in help section on top left): GitHub Repository (Website). To test it you can simply use the example button on top right.

@bloodcloak
Copy link
Member

Hi again sorry for the delay, I tried using your tool but it seems like it hung up after the normalization progress bar completed.

If could also update the steps to 1-4 then Ill merge it in

@web-dev-sam
Copy link
Author

web-dev-sam commented Mar 7, 2025

Hey @bloodcloak, I updated the description to include step 4 and 5 (step 5 was added recently too (trimming, no adding silence at end though (yet))). For the hang up: After the normalization ended there is still other processing being done that I can't simply calculate the progress of and that takes a bit more time (for me ~10% of normalization duration with example song but it depends on your gpu). So depending on the song you tried it with (the bigger the longer it takes) you can wait for 10s to see if it really did hung up. If it did, click on help (top-left) and report the bug (top right bug icon), and hopefully I can find the issue. Otherwise try with a different browser/computer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants