Subsonic Forum

There should be a way to force transcoding to the client, regardless of client settings.

If this is implemented, it would be very beneficial for client apps like play:Sub to be able to know that it is not allowed to (try to) override transcoding settings.
Something like a new user-role could be used to communicate this to the client app ("userTranscodingOverrideRole" ?).

Or maybe the user's maximum bitrate could be communicated to the client in the result of the getUser REST endpoint:

Code: Select all

<subsonic-response xmlns="http://subsonic.org/restapi" status="ok" version="1.12.0">
<user username="sindre" email="..." scrobblingEnabled="true" ... maxBitRate="320">
<folder>1</folder>
<folder>3</folder>
</user>
</subsonic-response>


/M

Michael Bech Hansen wrote:If this is implemented, it would be very beneficial for client apps like play:Sub to be able to know that it is not allowed to (try to) override transcoding settings.
Something like a new user-role could be used to communicate this to the client app ("userTranscodingOverrideRole" ?).

Or maybe the user's maximum bitrate could be communicated to the client in the result of the getUser REST endpoint:

Code: Select all

<subsonic-response xmlns="http://subsonic.org/restapi" status="ok" version="1.12.0">
<user username="sindre" email="..." scrobblingEnabled="true" ... maxBitRate="320">
<folder>1</folder>
<folder>3</folder>
</user>
</subsonic-response>


/M

I would think this would be transparent. If I have transcoding to AAC enabled, and my user ID has a maximum bitrate of 256K, then the client should be told the file is a 256K m4a file and never even know there is a FLAC or ALAC on the server.

Sent from my Pixel C using Tapatalk