Vesari Stylus ← vesaristylus.com

Help  /  Troubleshooting

The seek bar or track time looks wrong

If the seek bar or the elapsed and remaining time misbehaves on an album that's stored as one big file split into tracks, this should now be fixed - update to the latest version of Vesari Stylus and it should track correctly. If it still looks wrong after updating, please report it and we'll take a look.

The short answer

On a single-file album - one large audio file that a companion track list splits into separate tracks - the seek bar could previously misbehave on any track after the first. You might have seen the handle jump back to the start when you let go, run backwards, sit pinned at the far right, or show the elapsed time stuck equal to the total (like 2:26 / 2:26).

This should now be fixed. Once you're on the latest version, the seek bar should:

Update Vesari Stylus, then play a track partway through one of these albums. The bar should behave normally.

What a single-file album actually is

Some albums - especially live sets, DJ mixes, and discs saved as one continuous recording - are stored as one long audio file plus a small companion list that marks where each track begins and ends. Vesari Stylus reads that list and shows you separate, playable tracks even though the audio itself is a single file.

That split is exactly where the timing used to get confused: the player was measuring your position from the start of the whole file while showing you the length of just one track. Now those two line up, so the time and the handle match the track you're actually hearing - no matter which track in the album you pick.

If it still looks wrong

If you're on the latest version and the seek bar or track time still misbehaves, let us know so we can look into it. When you report it, please include:

  1. The album and how it's stored - one file with a track list, or a separate file per track.
  2. Which track it happens on - the first track, later tracks, or all of them.
  3. Exactly what the bar does - jumps back, runs backwards, freezes, or shows the wrong total.

The more specific you can be, the faster we can pin it down.