dukejames 3 Posted May 17, 2016 Share Posted May 17, 2016 Hello, Emby Version 3.0.5934.0 is installed on a Ubuntu system with Samba and Path Substitutions configured. For some reason when playing a video through Chrome, it always Transcodes. I don't understand why. Transcoding also doesn't allow for higher than 480p 4 Mbps. Why am I now having these issues? Please find a log attached. emby_Log.txt Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 17, 2016 Share Posted May 17, 2016 Hi, thank you for the report. A log is only one peice of the puzzle. Please see our wiki article on transcoding: https://github.com/MediaBrowser/Wiki/wiki/Transcoding Please supply the info requested in the bottom section "My Files Shouldn't Be Transcoding. How Do I Report This?" Thanks! Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 17, 2016 Author Share Posted May 17, 2016 I understand. Please find updated info attached. emby_Log.txt Transcoding_Log.txt Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 17, 2016 Author Share Posted May 17, 2016 I was trying to learn more about naively supported formats, but the Web Client page has not been updated. https://github.com/MediaBrowser/Wiki/wiki/Web%20Client Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 18, 2016 Share Posted May 18, 2016 Yes it is and I apologize that we haven't filled in that page yet, although in the case of the web client, it's just a matter of what each individual browser supports. To answer this question for the video you posted, there is currently no browser that supports mpeg2video, no browser that supports dvdsub format subtitles, and only Microsoft Edge supports AC3. So based on what browser you're using, that should give you an idea of what requires converting. Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 18, 2016 Author Share Posted May 18, 2016 I understand. Why are the trans-coding options so low? Hardware Acceleration and Thread Count are set as "Auto". The documentation says that there are a variety of factors and configurations settings to determine the playback experience. Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 18, 2016 Share Posted May 18, 2016 it's limited by the source material, in this case a 480p video. we don't do any upscaling at this time. Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 18, 2016 Author Share Posted May 18, 2016 That's what I find odd. I'm expecting 16:9 at 720p. It's a VOB file being trans-coded. Please see the screenshot of the Codec screen from VLC player attached. The video plays at greater quality through VLC. Other VOB titles seem to trans-code fine as well. Could Emby have identified the Media Info incorrectly, and then trans-code at lower quality? Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 18, 2016 Share Posted May 18, 2016 Looks like the transcoding log explains it. The source is 720*480 (480p). When we transcode we're not specifying an output resolution, which typically results in ffmpeg ouptutting the same resolution as the input. However, looking at the log, it says it is outputting as Output #0, matroska, to '/var/lib/emby-server/transcoding-temp/bedf2c706fcd6c136a6292e1cc3777ce.mkv': Metadata: encoder : Lavf57.25.100 Stream #0:0: Video: h264 (libx264) (H264 / 0x34363248), yuv420p, 426x318 [SAR 212:213 DAR 4:3], q=-1--1, 100 kb/s, 29.97 fps, 1k tbn, 29.97 tbc I'm not sure why it's outputting at 426*318, possibly due to being anamorphic. Since this is a folder rip structure, keep in mind that we consider all transcoding of these to be experimental. They are not officially supported by ffmpeg, therefore we can't call them fully supported either. Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 18, 2016 Share Posted May 18, 2016 I'm sorry, this is my mistake. we are actually specifying a resolution - a max width of 426. let me look at why it might be doing that. Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 18, 2016 Share Posted May 18, 2016 Ok, I see why. the ffmpeg media probe detected a source bitrate of 97kbps, which is obviously wrong, but unfortunately that's just our reality as they don't support folder rips. So then what happens during transcoding is we look at that really low value and we try to be smart and limit the output resolution to something that is appropriate for 97kbps. Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 22, 2016 Author Share Posted May 22, 2016 Sorry for the late response. Can this be manually repaired and if so how? Link to comment Share on other sites More sharing options...
Luke 37099 Posted May 22, 2016 Share Posted May 22, 2016 Unfortunately outside of modifying the database there is currently no way to do that. Link to comment Share on other sites More sharing options...
dukejames 3 Posted May 22, 2016 Author Share Posted May 22, 2016 I understand. I'll reference this thread and make a feature request. Thanks! 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now