|
Renderer specific transcoding
|
|
10-06-2015, 15:10
(This post was last modified: 10-06-2015 15:15 by n3mmr.)
Post: #14
|
|||
|
|||
RE: Renderer specific transcoding
(10-06-2015 14:47)simoncn Wrote:(10-06-2015 14:04)n3mmr Wrote: BubbleUPnP and plugplayer control points with renderer denon AVR1912 and Xbmc/kodi and WD TV Live HD. These appear to dö something like that when using serviio as a server. 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. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



