Renderer specific transcoding

[n3mmr]

(10-06-2015 17:42)simoncn Wrote:  

(10-06-2015 15:10)n3mmr Wrote:  There's a standard set of profiles included in serviio. No need to write a new one.

If you download a standard free serviio, there's a complete and tested profiles file included. That file includes all tested and published transcoding and remuxing profiles. It's an XML file.

Then you can look thru that file and see if you have one or more of the renderers that actually need some real transcoding.available.

I can assist if needed.

Serviio does a discovery run at startup (and if you push a refresh button). It keeps ( and displays in a config tool) a table of what renderers are at what ip-addresses, and what transcoding profile will be used.

That table has columns for name, IP address and profile selected.
At discovery serviio decides on a profile for each renderer (or player), based on the type name the renderer responds with. The admin for the server can select a different profile in the config tool, and that tool knows about everything in the profiles file.

There are distris for Linux, windows and Mac.

Linux is just a tar file, extract that into a dir. Put a symlink to ffmpeg int serviios top dir. Start the server in the background and the config tool script. Make sure you have one or two renderers for serviio to discover, and things will seem clearer.

Thanks for explaining this in detail.

In the specific case of XBMC/Kodi as the renderer, did you use the default profile or did you select a custom profile? What was the original type of your music files and what was the transcoded type for these files in the profile that was selected for playing the files on XBMC/Kodi?

I have no idea at all any more, it's been two-three years.

Just look at the profiles. They're there because real people have used them..