How to Use Custom Tracks in My Music

One-Track Test Checklist

Before building a custom-track library, test one song in a controlled way. Keep the audio device, input device, and timing settings unchanged so you can tell whether the issue is the song or the setup.

• Pick one track with an obvious steady beat.
• Run one short attempt before changing any setting.
• Write down whether the issue is import, sync, combat feel, or audio delay.

Safe Custom-Track Setup Flow

Use a simple test flow before building a full custom-song library. Pick one stable track, keep the same audio device, test one import attempt, then compare timing feel before changing any other setting.

• Start with one stable-beat track instead of a whole folder.
• Keep audio output and input device unchanged during the first test.
• Write down what changed before trying a different format or timing setting.

Before Importing Songs

Choose tracks with a stable beat for early testing. Songs with heavy tempo changes may need more tuning before they feel good in combat.

What to check in a video

When a video shows custom tracks, look for the visible menu labels, the import screen, any BPM or offset controls, and whether the clip shows the result after importing.

When a tutorial is safe to follow

Treat a custom-music tutorial as useful when it shows the same job from start to finish: where the menu is, what setting changes, and what the player checks after the song loads. A thumbnail, a short success clip, or a tool page by itself is only a lead. It becomes practical when the steps line up with the current game screen you can see.

• Follow it when the video shows the My Music screen and the result after loading one song.
• Slow down when a guide jumps straight from a download link to a working result without showing the in-game check.
• Do not copy BPM or offset numbers from a tutorial unless it explains what track, device, and test those numbers belong to.
• If a tool or community guide changes files outside the game menu, keep it separate from normal My Music advice.

Helpful videos to compare against

The current import and calibration videos are useful for recognizing the My Music screen, song-import flow, and timing setup before you change anything yourself. Keep the page practical: test one song first, then decide whether the issue is import, sync, combat feel, or audio delay.

Check Tutorial Age Before Changing Your Library

Custom-music tutorials are useful only when their visible UI, platform, and patch window match what you are using. Current video examples include Steam Deck setup clips, song importing tutorials, review-context videos, and older calibration examples, so the safe habit is to watch for the menu shape first and copy no file path, BPM value, or shortcut until it matches your current build.

• Pause the tutorial where the My Music or import UI is visible and compare it with your screen.
• Ignore shortcuts that depend on old menu names until a current clip repeats them.
• Keep one test track separate from your real music library while checking import behavior.

Keep One Import Test Outside Your Library

Before you reorganize a real music folder, keep one throwaway test track for checking the current My Music flow. Use it to confirm the menu path, loading result, timing feel, and whether the setup still matches newer official update windows. If the test track behaves strangely, stop there instead of changing a whole library.

• Use one disposable test track before touching a full folder.
• Check menu shape and loading result before comparing timing.
• Do not copy old shortcuts until the current screen still matches them.

Treat Import Failures As Versioned Cases

Recent community reports describe different My Music failures after updates and on Linux or handheld setups: a file picker opens in the wrong place, an imported song appears but cannot load, or a library needs a fresh test. These are leads, not universal fixes. Record storefront, operating system, game build, file format, and whether a newly imported test track behaves differently from an older entry before touching the full library.

• Reproduce with one newly imported test track before repairing old entries.
• Keep unofficial repair tools separate from the normal in-game import flow.
• Back up the library before any bulk rename, move, or community-tool repair.