Leaderboard

Just to check back I have enabled throttling and that did exactly what I was hoping for. Big thanks to everyone for helping me with this.

Yeah, direct stream creates transcoding info, but there are "isVideoDirect" and "isAudioDirect" flags within the TranscodingInfo object to tell REMUX and DIRECT STREAM apart. The Direct Stream has both isVideoDirect and isAudioDirect as true. The web app has always called it "Direct Stream" when both video and audio are copied. I have no choice but to adopt the terms. I cannot debate. This is anarchy if debate happens. It has to be a council of wise elders who decide that fate. Not solitary individuals or any single whim. It must be a consensus to keep balance and harmony. No one group or individual can feel they are not heard. You cannot speak badly about those who do not get their way. They just made a bad choice. Do not be mad at those who may still vote Trump. They just do not know what it is like to be me. The "Trans" is actually a horrible term to use on the dashboard and the apps interfaces. For Gods sake use "Transcoding" do not make your own shortened words up to summarize anymore. You never know when that short word becomes something disparaging. Do not create short cuts or dumb tech words down so users can digest them. Stop treating users like they are not as smart as developers or even smarter. There are battles fought every day for some people to keep from feeling the world treats them like they are idiots. You shouldn't have to ask these types of question on these forums. This discussion should have been finished years ago. But here we are. Lets hope honesty lights the way in the future. Lets not mince words or abbreviate anything. Lets just put out the real information in its original format without the need to disseminate it into sound bites. Be nice. Be good. Be like E.T. was and have a big glowing heart. You do a good job Cayars. I admire the bullshit you put up with and the text floods you contribute. I do my part too but more information is always a good thing. You are jedi too. We fight for what is right. Also.. just for giggles.. The parser we use on Roku to handle all the various languages is ironically named "trans" and that is 100% my fault, but since it is removed before publishing and changed into byte-code pkg it is only offensive to my eyes (and possibly @ebr and team emby). No one else to suffer seeing that. Just thought I'd say even I am guilty of using it totally innocently and later notice how wrong it was to even do that. It is too late to go changing it now without hours of work and it only offends in code so it is ... history and left.. lol. Every time you have to translate a phrase in the Roku app it means wrapping it with Trans(" ") and I die a little bit inside each time... lol. Complete love Emby too do not take the post the wrong way. In the younger more wild days more things were acceptable. As Emby matures certain things need to be changed such as the use of "Trans" anywhere eyeballs may see it on their screens.

There are two issue going on here, but this may be of interest devs at Exoplayer are at least aware of the issue https://github.com/google/ExoPlayer/issues/7458

Would be great if can limit the device per users. The simultaneous streams don't prevent to user to login on another device and it will consume the space for the devices limits on Emby Premiere.

Your blog post completely agrees with what I said. This sums it up "Transcoding and encoding are often and incorrectly used interchangeably; encoding is the original compression of data and transcoding is the process of decoding, reformatting, and re-encoding data." Like I said to transcode you decode the stream and re-encode it. Nowhere does that blob post call a package change a transcode and they go out of their way to call it what it is a "transmux". A transmux in Emby speak is a "direct stream" with the exception of re-encoding audio. That's funny with the "TRANS" thing. Didn't even think of that and being PC. LOL Emby also incorrectly labels some "Direct Streaming" when in fact it's transcoded. In "Emby speak" it's the video that determines "stream" vs "transcoded" to differentiate between the two and it's done to make it easy to know how CPU BOUND the process is. Even when an audio track is transcoded it's very easy on the CPU compared to video so Emby uses the video to determine the difference. That's how a true transcode can still be marked in Emby as a "direct stream" even that it's technically not. I'm personally not a fan of this but it is what it is and I understand why they choose to label it this way. With that said I'm not sure if Emby Server still does this or not concerning only the audio conversion calling it a direct stream. In Emby speak "Trans" is a transcode and a Transmux is a "direct stream".

https://blog.stackpath.com/transcoding/ @cayars You know I love you. Cmon. But presently having done work on the stats for nerds side of the Roku app. It has always exposed "Transcoding Info" to users if present. Recently the server also adopted doing this too, as it is complete honesty. Now technically a remux is still TRANS-remuxing. So while we can ditch the "coding" side as obviously that confuses and means "codec" but we keep the "Trans" side and it doesn't mean anything deragatory. But you can see why we cannot simply call it "TRANS" in todays society right? It is not politically correct anymore. It is mean. (full disclosure: I have a son who wishes to become a girl who dresses trans right now and takes hormones. This is not acceptable term to use ever again.) Emby should never make light of religious, human rights, or any other issue or it fails as a leader. Lets say this anytime you see "Transcoding" type information on the stats for nerds it will not be direct playing. It will say in the play method what the proper play method is. Anytime you see transcoding info it could be for a directstream(both audio/video copied), remux(only video copied, audio is coverted), or transcode(both audio and video converted). The above is honestly how the web app terminology comes from. The Roku simply adopts these terms and follows the web app as if it is the preacher at the church of Emby. All apps do similar. There is only 1 band leader and it is the web app (on all its various platforms). Then Android TV is a close second. So forth and so on and etc. You honestly have the terms REMUX and DIRECTSTREAM backwards on what they actually do in the wiki. I am not joking. This is honestly what is causing confusion. A remux always has converted audio. A direct stream always copies both audio and video streams. I am not trying to confuse you. I am trying to elucidate you. Remember "Come, come, elucidate your thoughts" from the Eliza program back forever ago.. Elucidation is key to understanding.

i don't understand under what scenario this would ever be necessary. emby reads a file structure and assumes you know what you're doing. if you don't, neither does emby. thats like saying pressing the delete key should somehow anticipate an idiot user and not actually delete anything. just fix your mistake and move on.

If you disabled "throttle" for transcoding this is expected. It wants to finish ASAP. The reason it shows transcoding is because it is. When an item goes into a new container it spawns ffmpeg. The video and audio streams within your container can be copied. But they cannot be played in the original container. So in this case transcoding is used to directstream your copied audio and video streams into an HLS/m3u8 manifest with ts slices. It is basically a remux as mentioned earlier but is transcoding to get there. Any time ffmpeg is invoked is transcoding something: container or codec.

Direct Plays perfectly on a Shield Pro (up to 90Mbit/sec as that's all I have..) with HDR with TrueHD 7.1 Atmos sound - but there are many caveats. The main 'culprit' for 4K not playing well on system without HD audio decoders (ie Receivers) is actually the corresponding default True-HD audio track that then forces transcoding/streaming. If alternative non-HD tracks are available that can be direct played (AC3/DTS) - then emby has little problem playing 4K HDR tbh.

https://github.com/google/ExoPlayer/issues/7458

I think this thread is related to your problem :- https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/385967/plex-audio-issues-missing-channels-transcoding-i/ In short - unless the audio stream is EAC3 (not AC3), then the Dolby features of the Shield do not covert to 5.1 properly. Nvidia need to add this functionality - so there may be some hope to getting this resolved - but it appears to be a Shield issue rather than an Exo Player issue ?

That's not corruption. The player does not support dual-layer PGS subs. Use an external player or listen to the dub track. These are your options at this time.

here we go ! services are runnings but MONO-SGEN is up to 4,31 GB of RAM everything seems to be fine in emby server logs stop / start package and everything goes up and fine

PM me this evening and we can go though via whatapp

Bumping this - as I'm seeing many requests of failures caused by 4K REMUX's where the people simply do not have enough bandwidth (for whatever reason) to play the files. If as per @pir8radio requested a couple of years go - if you put the available client bandwidth on the dashboard (download a sample file when they first connect and store it ? But dynamic /live would be even better) then people can see how good/bad their connection is vs what they are trying to play..

It can be a plugin. You like it, install it otherwise leave it alone.

@mbarylski Sure, you're right, everything can be made better. But a lot of people, including me, are afraid that the claim "make a more modern UI" ends up in the PLEX bullshit. Yeah, PLEX may be look a bit more modern but modern must not mean better. The PLEX UI is a pain in the ass and it looks like "modern" crap. I love it to change my icons and so on.