Configurar velocidad de video automática en servidor Emby

[ErikFlores123 0]

Saludos, e descargado e instalado un servidor Emby, quiero configurar que la calidad de video de los usuarios sea automática, me pueden ayudar como lo hago, o donde se encuentran las líneas de código para editar desde consola? @cayars

[Carlo 4561]

Hi, if you're referring to the resolution/bitrate all Emby clients are set to AUTO by default.

This is a client setting, not a user settings so multiple devices owned by the user could each be set different if needed.
This is a client setting so you can't control this from the server.

Hope that helps,
Carlo

[ErikFlores123 0]

Claro, pero debe haber la ubicación del archivo donde se configure este parámetro mediante comandos, es lo que necesito.

 

[Luke 42078]

The quality setting has to be set in each app individually.

[ErikFlores123 0]

La calidad de video adaptativa de los clientes, en que ubicación se encuentran dichos comanos desde el servido, necesito verificar programación 

 

[ErikFlores123 0]

@Luke Me puedes decir la ubicación del archivo donde pueda verificar las líneas de programación de la calidad adaptativa para los clientes ?

 

[Luke 42078]

Hi, you can set your playback quality setting by clicking your user icon in the top right and then selecting Playback settings.

[ErikFlores123 0]

@cayarsSi tiene la calidad adaptativa pero no funciona corractamente ya que tengo una topología en GNS3 bajéel ancho de banda y los videos se quedan cargando, ya que el atomático solo carga en la calidad carga del video y no dependiendo la calidad de la red, alguna solución @Luke

[Carlo 4561]

Just to be clear, this isn't an adaptive bitrate settings. It's the upper limit of what the client wants to receive. If the client is being used on a local area network and not the the Internet where you could have a limit you are normally better off adjusting this as high as you can make it that allows the client to play.  Otherwise having a limit set could cause cause files to transcode that wouldn't have needed to otherwise.

I'm not sure what you're trying to do with the network simulation software but if it's to test QOS or "adaptive streaming" being done by Emby that's not going to give you results you may be thinking about.

 

[ErikFlores123 0]

@cayars Eso quiere decir que EMby no es o utiliza DASH?

[Carlo 4561]

We could use DASH but it doesn't really gain us anything except a couple fringe cases.

The biggest issue for us is lack of support. HLS is the only format supported by Apple devices.
iPhones, iTablets, MacBooks, AppleTV as well as other Apple products cannot play video delivered over MPEG-DASH.

MPEG-DASH allows the use of any encoding standard. HLS, on the other hand, requires the use of H.264 or H.265.
When we transcode it's always to H.265 or H.264 so either works.
So we could take what's inside HLS and pretty painlessly put it in a DASH format but why?

I think what you really wanted to know about is adaptive bitrate streaming.  This can be done with DASH or HLS.

AB is great if you're a commercial streaming service because you prepare several different versions of each movie/show. You may have 10 versions of Top Gun (1986) from 480 up to 4K.
The "trick" to adaptive bitrate streaming is that the manifest sent to the client will contain usually 3 or more sets of streams with the size/bitrate marked from each. The client can start with the middle stream. If it has trouble keeping it's buffer full it needs to choose a smaller bitrate version.  If it's can keep the buffer filled easily it can move up to the next highest bitrate.

The player of course will watch for lost frames, skipped frames or other issues that could also lower the bitrate.  But you end up having a client controlled selection process that allows it to switch from stream to stream without pausing since the streams were prepared together frame by frame.

With the current approach of Emby it's much more complex and not super simple like Netflix and Amazon use. Emby can allow you to play the file direct, can repackaging it without changing the guts. It can transcode as well as tone-map and does this all in real-time for multiple clients.

Emby support different bitrates as well but the choice of stream bitrate/resolution is picked before starting.  If you want to switch resolutions it can with a small pause.
Each has an advantage over the other.

A commercial streaming service will trade storage for CPU/GPU all day long.  It's a far better use of resources to convert each piece 1 time into 10 slices.  That's probably will take 6 or 7x the space of the highest versions on average.  Once it's converts or "produced" it will get used over and over again and never have to transcode.

With Emby, everyone's not going to want to run out and buy 7big drives to hold the contents of your present single drive.  Right now you can take pretty much anything (in reason) add it to your library and it's available.  The AB way you would need to prepare each and ever media item into it's different streams and once complete can add that media item and start on the next.  It would take a while for your movies and shows to get added.

We could do full on adaptive bitrate on the fly where we on purpose transcode everything.  We use a manifest with (for sake of discussion) that included 10 streams the client can use just as if it were Netflix.  The backend could generate 3 streams at once trying to match any changes the client makes.  If the client drops down 1 stream the backend does as well for the next segment. That would allow switching streams to work as good as Netflix but means you're always doing transcoding x3 for each person.  We could also probably only process one string at a time with 9 bogus streams added to the manifest.  The client can still change streams as needed but there's a delay.  The backend will be a couple segments ahead of the client.  If the client changes bitrates the backend can shift the bitrate used to match.  It could even discard a segment or two already prepared and redo it.  But regardless there would be probably a 2 to 7 second delay from changing bitrate to it making it to you.  For a home Streaming server that might be fine.  The downside to most people is the fact you can't start out playing in direct play or direct  streaming format.

Some of us play with stuff like this. Because we allow so many  containers, codecs, different audio channel types, closed caption, subtitles we have more work to do on the fly compared to being able to prepare every video the same way making for consistent playback.

The thing is, if you can adjust the bitrate in the client setup to the highest setting the works it will produce a better quality video as you might completely avoid transcoding. You can almost always set this and have it work perfectly and not need adaptive bitrates.  But if using mobile data, wifi in the coffee shop or hotel where it's quite variable then adaptive bitrate will be quite helpful.

Some people solve that issue themselves as well.  Emby does allow you to have multiple versions of a file. IE 4K, 1080, 720, 560, 480 so you could do that or just one additional for mobile.  The client will try to "auto pick" the stream best for it.  Of course you could always manually pick a "mobile" profile version as well.

There's a ton of ways we could go like this if the customers wanted it.  Heck we could even build a true hybrid such that it takes your Top Gun movie never played and on first playback generates all the needed streams and writes them to disk as well as use them for this playback.  That way each movie only gets transcoded once in it's life and things never watch don't consume more than the original amount.

Lots of possibilities. But there nothing but ideas until you test to see how well it would work in the real-world.  The Nvidia 1050 and 1650 won't likely be up to the transcoding.  You're talking expensive-ish GPU in the RTX 3 or 4000 range or better possibly.  Honestly don't know as it would depend on how many people you support and how lucky you get with people playing back pre-converted vs first-conversion.  It would be hardest getting started when everything needs converting.