PC player crashes if transcoding wav24-192

[tgb]

Thanks for your input Simon.

So, I had a look at PC side : problem SOLVED ! (it seems... I'm looking for files that still can crash the player).
This is the solution if it can help someone.

As I said above, the trouble seems related to the length of the URL path, when it is too long, the player crashes.

I found info regarding the maximum length of file that Windows10 can manage. Before it was limited to 260 characters, now, IF you make a change in Win10, Win10 can manage longer files name.
So, I made the change in Win10 as described here : https://lifehacker.com/windows-10-allows...1785201032
Result : still crashes...

Then, I looked at the translation of folders & files names in URL encoded format.
The point is that I realized that on the URL path of the file streamed from the NAS, the paths are long because there are of lot of time the "%20" chain. As this chain is made of 3 characters, I was looking for a way to shorten it.
To understand translation of "standard" characters into URL encoded characters, I found & used this translator => https://www.urlencoder.org/
Using this translator , standard characters into URL encoded give :
space => %20
- => -
_ => _
etc...
So, as a start I made a very basic change. I renamed all folders & files names of my discog, changing the "space" by "_". By doing so, I saved 2 URL characters for each "space" I had previously in the folders & files names. And it works now, no more crashes !!!!!!
My discog is quite large, thus I didn't do it by hands, I used the freeware that enable renaming by batch : https://www.advancedrenamer.com/
This soft is really powerfull, thanks to the developers.
Now, with spaces replaced by _, names of folders & files aren't nice to read, but not a big deal since only the tags are really important and remain "clear & nice" to read.

I could find info regarding that kind of trouble, maybe I'm alone to face it :-)
Hope it helps
Rgds

PS : that trick works, but I still do not understand why these crashes occured...
transcoding in wav24;192 by Minim should be the reason, in combination with long paths names, because no issue without transcoding.
As least it works now & Minim is still the best server so far : everything is back to normal.