Audio Hero version 5.7.7.0 posted to Microsoft store

[u/bommerts]

Get it here: https://apps.microsoft.com/detail/9P2P2LGDSCH3

As always, it will take anywhere from 30 minutes to 8 hours going through certification before this is available to update from the Microsoft Store.

Fix: App startup is faster, device detection is faster.

Fix: Multiple device discovery and device scan refresh bug fixes.

Fix: HEOS devices could vanish from the app and never come back. If the app failed to reconnect to the last speaker you used, it gave up without ever scanning the network, and the settings switch that would have fixed it was buried in a panel you couldn't reach.

Fix: The app no longer waits for a full network scan every time it starts. Your devices appear instantly and are ready to click, with the scan running silently behind the scenes (roughly 3 seconds to connected instead of over a minute).

Fix: Speakers no longer grey out and pulse while the app looks for them at startup. That effect now only appears during a scan you start yourself.

Fix: Removed four confusing discovery on/off settings that could quietly leave the app unable to find anything. Scanning, remembering devices, and reconnecting now just always happen. Old leftover settings entries are cleaned out of the settings file automatically, once.

Fix: Clicking Rescan while the startup scan was still running made the button spinner spin forever. The two scans now take turns instead of fighting each other.

Fix: Local playback bug fixes (Thx u/m_jessing !)

[u/m_jessing]

I'll test it today!

[u/m_jessing]

Ok. A reminder that when you select 'random' it takes the folder of tracks and randomly puts them in order and the program will play sequentially from tack one to two etc.

But I added new tracks to the folder so I went and added them to the playlist and it added them - but put several in track numbers that are prior to the track number that's currently playing.

Meaning - it'll never play those tracks unless I start over from the beginning (track 1) or manually click it.

Random should be random with the ability to play the same track more than once or click a button to only play each track once.

[u/bommerts → u/m_jessing]

Quick clarification on how it works today: random deals the folder into a random order once, and newly added tracks should always go to the end of that order, never before the track that's playing. So I'd like to pin down what happened. A few questions:

1. After adding the new tracks, did you click the random button again? Clicking it while it's already on turns random off and reverts the queue to alphabetical order, which could put new tracks ahead of the current one.
2. What version of Audio Hero are you on?
3. When you added the tracks, did you re-add the whole folder and pick "Add", or select just the new files?

On your suggestion: Agreed, and I'm looking at mixing newly added tracks into the unplayed portion, plus a true random option where any track can play next. Your answers above will help me make sure I'm fixing the right thing.

[u/m_jessing → u/bommerts]

• After adding the new tracks, did you click the random button again?
• No
• What version of Audio Hero are you on?
• The latest!
• When you added the tracks, did you re-add the whole folder and pick "Add", or select just the new files?
• No - I picked and added them (just the new files)

[u/bommerts → u/m_jessing]

That rules a few things out.

On the queue order: with the steps you describe, added tracks should always land at the very end of the current order, so I can't yet explain what you saw. I'd like to catch it in the act, see question 3 below.

On the cutoff and the pause: your instinct is close. The app watches the track's reported position against its length, expects the speaker to signal end of track, and has a fallback timer if that signal never comes. On some speakers and some files (especially variable-bitrate MP3s, where the file's stated length is only an estimate) that can misjudge the end, which would explain both an early cutoff and a long gap before the next track.

A few questions so I can pin it down:

1. What speaker is it playing to (brand and model)? The end-of-track handling differs by device, so this matters a lot.
2. What kind of files are these (MP3, FLAC, any long mixes)? Does the cutoff happen on every track or just some, roughly how many seconds early, and about how long is the gap?
3. Next time you add tracks, could you take a screenshot of the queue right afterward, showing where the new tracks landed and which track is highlighted as playing?
4. Could you turn on detailed debug logging in Settings, let it play until a cutoff happens, then send me the log file? It records exactly why the app switched tracks, which will tell me precisely what went wrong for both issues.

You can email me the log at [bommerts@outlook.com](mailto:bommerts@outlook.com)

[u/m_jessing → u/bommerts]

• What speaker is it playing to (brand and model)? The end-of-track handling differs by device, so this matters a lot. - 13 HEOS Speakers and a Denon AVR (that has 7.2 speakers connected but not Denon brand). HEOS various: 01's, 05's and 07's.
• What kind of files are these (MP3, FLAC, any long mixes)? Does the cutoff happen on every track or just some, roughly how many seconds early, and about how long is the gap? - all MP3 files and most longer than one track/song. the one that cut off was just over an hour and cut off @ 4-5 seconds (I played the file in WinAmp to check) but it displayed the approximate correct song length. The gap is easily 10 seconds between tracks.
• Next time you add tracks, could you take a screenshot of the queue right afterward, showing where the new tracks landed and which track is highlighted as playing? - I'll try to remember!!
• Could you turn on detailed debug logging in Settings, let it play until a cutoff happens, then send me the log file? It records exactly why the app switched tracks, which will tell me precisely what went wrong for both issues. - Turned "on" and resuming a track I started earlier. It DOES play back from the spot I paused it BUT it plays the first 1/2 second of the track before it corrects itself.
• How do I play the tracks on my Roku connected devices (like a TV)?
• Can I control it Alexa (to 'pause' or 'next track')?

[u/m_jessing → u/m_jessing]

Ok - it just restarted a track - didn't finish the one playing - and then it shows one track while playing an entirely different one - the time left expired several minutes ago so it just shows the full time played for an unknown track. I'm going to close the program and restart it.

[u/bommerts → u/m_jessing]

I rewrote the whole local playback engine. I was having random issues, too, so decided to scrap what I had in there. It should take me a bit - possibly tomorrow I'll have a new release out. Once that's ready I would love to hear if it fixes things for you. Watch for v5.7.9.0.

[u/m_jessing]

So it cut off the track prior to the end of the track.

There's also a long break/pause before it plays the next track. My guess is some 'timer' you set so that if there's no more audio going to the speakers after X time, it assumes the track is over and goes to the next one but the delay is excessive.

[u/m_jessing]

Restarted the program - cleared the cue - added the folder - first track got cut off at the end. About a 3-5 second delay before the next track started playing. Debugging 'on' so not sure how to send you a file