No idea what’s going on here.
This afternoon I cast music to my Google photo frame without any problems.
In one go the music and casting stopped.
Server appeared to be stuck.
After restart, I also have the same problem with playing and casting to the Google photo frame.
Give the tracks a kick before playing, even after each track.
debug-20210507_175142.zip (191.5 KB)
embyserver (4).txt (272.2 KB)
I really need to find out why and how to detect properly when devices stops to support auto play 
Just for additional information:
In my opinion, the problem is not only with the Xiaomi speaker.
(Since I also had the problem with the Google nest frame yesterday).
I remember the first time it happened I was only casting to the Google nest audio speaker.
Here I had the exact same problem.
I thought I would buy a set of Xiaomi speakers and get rid of the problem.
Unfortunately, this was not the case.
Only with the presence of the Xiaomi has the problem gotten worse.
There’s 3 different issues here 
- Wrong transcoding profile for wma: Fixed
- Xiaomi bug with urls without file extension: Fixed
- Sometimes the autoplay parameter for the load command of Chromecast is ignored: Unknown reason as it seems it’s spreading in your house. But pretty sure that if you reboot everything it will auto fix by magic at some point.
For that last one the logs shows that the device accept the load with auto play but just decide randomly to not auto play.
I did the same castings again with the Emby application.
With Emby I don’t have any playback problems that I do experience with Yatse.
I have no other option than to play with Emby for the time being.
Not even with audio groups that also contain the Xiaomi speaker.
I know things looks simple but it’s not
Telling me that another app that may not use the latest Google libraries and optimisations does not bring anything to the table.
Test attached APK that have the workaround enabled for all, it will probably work, but even if you still refuse to understand this is still a WORKAROUND that can introduce some small delays between tracks.
Yatse-beta-arm64-v8a-final.zip (5.6 MB)
I try to test this version tomorrow
I am happy with the latest file.
I got him cast to my audio group right away this morning with no problems.
The delay between the tracks is not too bad.
Only after my walk this morning I wanted to restart the playlist and got the following message.
(this is a message that I have seen before).
[Problem starting media.
Does your player support the chosen file format?]
After three attempts to activate the playlist it worked again.
Hopefully you can trace where this report came from.
embyserver (5).txt (2.2 MB)
debug-20210509_100605.zip (64.6 KB)
I see that the problem I describe when I stop the music via a voice command that it occurs only then.
If you stop the music and start via the app, it works fine for now.
I’m lost with your last comment?
You mean that it shows errors after you stop playing via voice commands?
Voice commands from where?
In all cases can you try with attached APK and provide logs starting from when it works then not works in the same session of logs ?
Yatse-beta-arm64-v8a-final.zip (5.6 MB)
Is this attached APK different then you sent me in message 46?
When I use Google assistant and I say google stop music then the whole list stops and I can’t just turn it on.
This probably has nothing to do with the operation of Yatse, but more with the operation of the way of giving commands.
When I say pause music, I can then play the music again with the command continue music.
The only problem I run into from time to time is my Emby android server crashing.
This also happens when I play videos in quick succession via Emby.
This is probably also more of a problem with the Himedia Q10 player in combination with Emby Android server
Of course it’s a different one why do you keep asking?
Please provide the asked logs with that version by reproducing the issue from working to non working in the same logs.
I may be able to detect the case and workaround it.
I ask for the different version because I see no version changes in description.
Since it also takes me time to test, I don’t want to do double work. 
I discovered something strange again.
During playback I noticed that the wrong album cover was displayed.
When I then click on the next number again, the correct case will be added to the next number.
It may take a while before I start testing again.
To be continued.
And so no logs will be provided So no fix in next release.
To be continued in a long time so.
After a long time i am back.
In the latest atached file I missing my album arts. 
And messages
debug-20210511_170240.zip (1.3 MB)
embyserver (6).txt (5.9 MB)
[Problem starting media.
Does your player support the chosen file format?] wen media wants to start.
I don’t know what’s going on, but my server has crashed again.
It makes me a little despondent.
Mus
embyserver (7).txt (59.3 KB)
t restart my server again
Ok so this one is completely unrelated and weird.
Due to the server crash Yatse was in half connected mode and did not properly recovered so did not transcode yet still play stuff.
That one will be hard to reproduce and understand
I have updated my android emby server to the latest software, am curious if there are still problems with the server crashing.
When I can produce a clear complaint description, I will report again.
In theory I’ve found the race condition for that last issue.
Please test attached APK. And yes it’s a proper new one.
Yatse-beta-arm64-v8a-final.zip (5.6 MB)