Universal Media Server | Forum

First of all: there's no renderer file included in the UMS setup for my media player (Sangean WFT-3). So I took some other renderer file (CambridgeAudio-AzurBD.conf) and changed some properties in it to match my media player. But I don't know it the created renderer file is fully compatible with my ...

I'm having the same issue here when playing FLAC files on my media player using UMS. When playing MP3 files, there's a progress slider in the app (e.g. BubbleUPnP) that shows the progress of the music and that I can tap to "jump" to another part of the music file. When playing FLAC files, ...

I am using UMS to play my music files and I've also divided my music library (with mp3 and flac files) in artist folders, with the artist albums as subfolders. As far as I know you don't have to put a separate album cover image in the music folder. If the audio files are properly tagged with cover a...

Yes, that did the trick.
Thanks!

Recently a search function has been added to UMS. I believe it's added in 11.4.0, where the Release Notes say "Enabled UPnP searching, with the ability to disable for problematic renderers". Besides the fact that this search does not work on my audio renderer (Sangean), it takes up a lot o...

Ok, thanks.

Will this workaround be a hardcoded fix, something like: if renderer is Sangean WFT-3 then don't send dc:date?
It's not possible to control this behaviour from the renderer .conf file? It's a pity that a workaround has to be programmed in code because of my buggy renderer.

Good news!

I installed the test build from the link and all works fine in this build. Browsing and playing; no empty folders as far as I can see now.

Hope this helps.

Thanks for the test build.
I will try this in the next days and let you know the result.

Update:

I downloaded and installed 11.1.0 today.
It was worth trying, but unfortunately still the same problem: several audio (FLAC and MP3) folders show "No results found" when browsing.

Went back to 10.19.0 and browsing works fine again.

Interesting development: Your suggestion to test this also with 10.21.1 was a good one. I repeated all of my previous tests, the same way, and it's obvious that the same problem is already in 10.21.1. So, I went back to 10.20.0 (clean install, no settings changed), and... the problem is also in this...