.flac_WPRX extension causes Web UI to hang for some audio-linux renderers

[storaid]

Dear Tiki san,

Thank you again for your continuous improvements to TuneBrowser.

I’d like to report a compatibility issue I’ve encountered when using the ProxyStream feature with on-the-fly transcoding enabled.

When a file is transcoded via ProxyStream, the streaming URL sometimes includes an extended file name like this:

http://10.1.1.160:29400/TuneID/00018967-RFH-83CE912B.flac_WPRX

While the content itself is a valid FLAC stream and plays correctly, the .flac_WPRX extension is not recognized as a valid audio file by some Linux-based renders, especially Web UI parsers.

For example, in Moode Audio (an audio-focused Linux distribution), this kind of URL causes the Web UI renderer to hang or become unresponsive.

It seems the UI fails when attempting to parse the file extension and does not expect anything beyond standard formats like .flac, .mp3, etc.

Since the actual content is FLAC, would it be possible to retain the original .flac extension, so that the URL remains compliant with what most renderers expect?

I understand the current naming may help with internal handling, but I wanted to share this issue from a cross-platform compatibility point of view.

Thank you again for your attention and excellent work!

[Tiki]

The content of “.flac_WPRX” is not FLAC. It is Wave. It may be “.flac_AL16” depending on the setting and situation. In this case, it is Raw PCM. Considering the Raw PCM case, I do not want to change the flac_WPRX extension to wav.

[storaid]

Hello,

Thank you for your explanation regarding the actual format being Wave or Raw PCM in ProxyStream.

I think –

some Linux-based audio renderer systems use MediaInfo or libmediainfo to parse track metadata in their Web UI.

When the file has a non-standard extension like .flac_WPRX, MediaInfo detects it as a valid FLAC internally, but still flags the extension as invalid (FileExtension_Invalid).

Because of this, the Web interface, which depends on MediaInfo, may fail to parse the file or even hang.

Thanks again for your attention and thoughtful response!

[投稿者]

投稿