# After analyzing, load track into player again if it was previously loaded

**URL:** <https://discuss.lexicondj.com/t/after-analyzing-load-track-into-player-again-if-it-was-previously-loaded/3475>\
**Category:** Ideas & Feature Requests\
**Created:** [March 2, 2026, 2:23pm UTC](https://discuss.lexicondj.com/t/after-analyzing-load-track-into-player-again-if-it-was-previously-loaded/3475 "2026-03-02T14:23:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![t\_a](https://discuss.lexicondj.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@t\_a](https://discuss.lexicondj.com/u/t_a)\
**Post date:** [March 2, 2026, 2:23pm UTC](https://discuss.lexicondj.com/t/after-analyzing-load-track-into-player-again-if-it-was-previously-loaded/3475/1 "2026-03-02T14:23:14Z")

</div>

If the algorithm got something wrong I usually adjust the parameters and try again. At this point I always want to see how the new result looks like and load the track into the player. It would be great if this step could be done automatically. Even better would be if the track isn’t even unloaded.

---

<div class="post-metadata">

**Author:** ![Christiaan](https://discuss.lexicondj.com/user_avatar/discuss.lexicondj.com/christiaan/32/10_2.png) [@Christiaan](https://discuss.lexicondj.com/u/Christiaan)\
**Post date:** [March 2, 2026, 3:57pm UTC](https://discuss.lexicondj.com/t/after-analyzing-load-track-into-player-again-if-it-was-previously-loaded/3475/2 "2026-03-02T15:57:14Z")

</div>

There aren’t really many analysis settings to change though so not sure how useful this is. If it gets a grid wrong, it usually means manual adjusting is required

---

<div class="post-metadata">

**Author:** ![t\_a](https://discuss.lexicondj.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@t\_a](https://discuss.lexicondj.com/u/t_a)\
**Post date:** [July 4, 2026, 12:33pm UTC](https://discuss.lexicondj.com/t/after-analyzing-load-track-into-player-again-if-it-was-previously-loaded/3475/3 "2026-07-04T12:33:44Z")

</div>

I use adjustments in the BPM range quiet a lot to get accurate results. It happens regularly that I still have 68-135 in the analyser settings but my current track is faster or the other way around. Just re-loading the track after analysis can only make the UX better.