Transcoding doesn't show correct transcoding reason

[Painkiller88 249]

or maybe something like that, thats how it is displayed directly in the plex dashboard, not as detailed as in tautulli but it tells much more than emby actually does (without looking into the logs)

Umwandeln = transcoding

[Carlo 4561]

I've always like that and it's clear if it's video, audio or subs that are being transcoded.

[pwhodges 2012]

1 hour ago, cayars said:

It doesn't help and adds to the confusion when the apps use different terminology from each other as well.

This is why the only justifiable usage is to have terms which are unambiguous and so app-agnostic. The usual complaint from the devs is that unambiguous terms are too long, but we have loads of screen-space which is not always efficiently used, and anyway: transcode-all, transcode-video, transcode-audio, remux aren't that long; or even: transcode-av, transcode-v, transcode-a, remux.

Paul

[Carlo 4561]

You could also just use the starting letter as well "V", "A", "S" so if you saw "Transcode VS" you would know both the video and subs were transcoded or "Transcode VA" would be both Video and Audio transcoded.

Besides the Transcoding mentioned above, I love to see:
Direct Play = Streamed from Emby Server
File Play = Played from the file system for those clients that can do this
Streaming (or Remux) for anything that's just a container swap of some kind.

No need for "Direct" part in the streaming and helps to separate Direct playing from streaming.

[Painkiller88 249]

Emby is still showing the wrong trascoding reasons.

Actually it tells me Direct Stream, but in the ffmpeg log i can see audio codec not supported

In Log:

http://192.168.1.14:8096/emby/videos/370799/hls1/main/90.ts?DeviceId=XXX&MediaSourceId=7ee5fac54cb02878cd8813234d33fe53&PlaySessionId=XXX&api_key=XXX&VideoCodec=h264,h265,hevc&AudioCodec=ac3,eac3,aac,mp3,opus&VideoBitrate=139360000&AudioBitrate=640000&MaxWidth=4096&AudioStreamIndex=1&TranscodingMaxAudioChannels=6&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=False&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=51&TranscodeReasons=AudioCodecNotSupported

 

Could you please improve this?

 

Thanks

 

Edited November 16, 2021 by Painkiller8818

[Happy2Play 9780]

3 minutes ago, Painkiller8818 said:

Emby is still showing the wrong trascoding reasons.

Actually it tells me Direct Stream, but in the ffmpeg log i can see audio codec not supported

In Log:

http://192.168.1.14:8096/emby/videos/370799/hls1/main/90.ts?DeviceId=XXX&MediaSourceId=7ee5fac54cb02878cd8813234d33fe53&PlaySessionId=XXX&api_key=XXX&VideoCodec=h264,h265,hevc&AudioCodec=ac3,eac3,aac,mp3,opus&VideoBitrate=139360000&AudioBitrate=640000&MaxWidth=4096&AudioStreamIndex=1&TranscodingMaxAudioChannels=6&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=False&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline,high10&h264-level=51&TranscodeReasons=AudioCodecNotSupported

 

Could you please improve this?

 

Thanks

 

Converting audio is not a Transcode to Emby only converting video is a Transcode.

 

[Painkiller88 249]

1 minute ago, Happy2Play said:

TranscodeReasons=AudioCodecNotSupported

Ok may be, this is what the log says but don't matter. Even if it is not transcoding.

The Text written in the info popup for Direct Streaming is also not correct as it tells me all codecs are supported but the container is not supported.

[Luke 42078]

Hi, this will be improved in the upcoming 4.7 release. Thanks.