Jump to content

Video delay with MPEG-4 and VC-1 videos


Richard Branches

Recommended Posts

Richard Branches

I was having transcoding issues I was able to resolved thanks to the great help of the developers and people in general in this forum.

 

But now I noticed all my mpeg-4 videos and VC-1 videos are delayed, the sound is heard first and after approximately 2 seconds the image follows, most of my videos have subtitles and they are in sync with the audio.

 

I checked all the settings in the device and emby app but I've been unable to find any solution.

 

It's important to clarify the videos are not transcoded, therefore I'm unable to attach log files for this issue.

 

On my android phone (Alcatel 4047A) this delay is absent.

Edited by delacosta78
Link to post
Share on other sites
  • 1 month later...
Richard Branches

Best advice I can give at this point would be to try the beta version to see if it is any different.

 

Thanks.

 

On the beta version, the MPEG-4 videos are not delayed but are getting transcoded, the reason of transcoding in dashboard says "video codec not supported" but I'm pretty sure it does, I tested this with MX player and Archos video player, they won't play a video if the codec is really not supported unless software decoding is activated, the video played without problems:

 

5ab163536844e_Screenshot_20180320143609.

5ab1636a70ffd_Screenshot_20180320143646.

Edited by delacosta78
Link to post
Share on other sites
Richard Branches

The VC-1 codec is really not supported, however emby plays the video by software decoding in the current version of the app and I suppose that's the reason why the video and audio were not in sync.

Link to post
Share on other sites
Richard Branches

Hi.  What, exactly is the problem here?

 

On the current version of emby app for android tv, mpeg-4 (divx and xvid) videos played with an audio delay, on the beta app they are getting transcoded because according to the server the codec is not supported, however, I tested the same files with mx player and archos video player (see screenshots above), they won't play any unsupported video unless software decoding is activated, I tested the same files and they played without problems with hardware decoding, which means the codec is indeed supported by the device.

 

VC-1 codec is not supported by the mi box, however, the current version of emby app direct plays the video with audio delay as well, although on the beta app the video is now transcoded because it's detecting correctly it's really not supported by the device.

Edited by delacosta78
Link to post
Share on other sites
Richard Branches

So, it sounds like everything is playing now in the beta version?

 

No, the mpeg-4 videos shouldn't be transcoded, they are supported by the device.

 

On my phone for example, they won't direct play at all, see my post about the issue here: 

 

https://emby.media/community/index.php?/topic/57140-problem-report-divx-5-videos-dont-start-to-play/

Link to post
Share on other sites

No, the mpeg-4 videos shouldn't be transcoded, they are supported by the device.

 

Your method of determining their "support on the device" does not guarantee they will play properly in our environment.  When this is the case, we switch to transcoding automatically.  From your description, it sounds like the system is working as it should.

 

If you can reproduce just one of these instances of an item you think shouldn't transcode that is, and send an app log from that one playback session, I can look and see what the player is having trouble with.

Link to post
Share on other sites

Looking in one of your logs from a different issue, I noticed this:

03-20 16:13:54.329  4652  4652 E EventLogger: internalError [10.21, loadError]
03-20 16:13:54.329  4652  4652 E EventLogger: com.google.android.exoplayer2.upstream.HttpDataSource$HttpDataSourceException: Unable to connect to http://192.168.1.20:8096/emby/videos/6999022f8d48199e1fe6d4a491cd8263/hls1/main/0.ts?DeviceId=84a6390ebc3fd238&MediaSourceId=6999022f8d48199e1fe6d4a491cd8263&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac,mp3&AudioStreamIndex=2&VideoBitrate=109616000&AudioBitrate=384000&PlaySessionId=3046faec710942b4a2e07438960f6f88&api_key=a1360396dff24359b403963e0209d3b6&CopyTimestamps=true&RequireAvc=false&Tag=dd3664b2c5c3c93da58aa95586195d4c&SegmentContainer=ts&MinSegments=2&BreakOnNonKeyFrames=True&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&hevc-profile=Main,Main10&audiochannels=8&TranscodeReasons=VideoCodecNotSupported
...
03-20 16:13:54.329  4652  4652 E EventLogger: Caused by: java.net.SocketTimeoutException

That could very well be why some of your items are falling over to transcode.

 

I suspect the wireless network.

Link to post
Share on other sites
Richard Branches

Looking in one of your logs from a different issue, I noticed this:

03-20 16:13:54.329  4652  4652 E EventLogger: internalError [10.21, loadError]
03-20 16:13:54.329  4652  4652 E EventLogger: com.google.android.exoplayer2.upstream.HttpDataSource$HttpDataSourceException: Unable to connect to http://192.168.1.20:8096/emby/videos/6999022f8d48199e1fe6d4a491cd8263/hls1/main/0.ts?DeviceId=84a6390ebc3fd238&MediaSourceId=6999022f8d48199e1fe6d4a491cd8263&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac,mp3&AudioStreamIndex=2&VideoBitrate=109616000&AudioBitrate=384000&PlaySessionId=3046faec710942b4a2e07438960f6f88&api_key=a1360396dff24359b403963e0209d3b6&CopyTimestamps=true&RequireAvc=false&Tag=dd3664b2c5c3c93da58aa95586195d4c&SegmentContainer=ts&MinSegments=2&BreakOnNonKeyFrames=True&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&hevc-profile=Main,Main10&audiochannels=8&TranscodeReasons=VideoCodecNotSupported
...
03-20 16:13:54.329  4652  4652 E EventLogger: Caused by: java.net.SocketTimeoutException

That could very well be why some of your items are falling over to transcode.

 

I suspect the wireless network.

 

I not using wireless, I'm using ethernet through an usb hub because the device lacks of an ethernet connector.

Link to post
Share on other sites
Richard Branches

Looking in one of your logs from a different issue, I noticed this:

03-20 16:13:54.329  4652  4652 E EventLogger: internalError [10.21, loadError]
03-20 16:13:54.329  4652  4652 E EventLogger: com.google.android.exoplayer2.upstream.HttpDataSource$HttpDataSourceException: Unable to connect to http://192.168.1.20:8096/emby/videos/6999022f8d48199e1fe6d4a491cd8263/hls1/main/0.ts?DeviceId=84a6390ebc3fd238&MediaSourceId=6999022f8d48199e1fe6d4a491cd8263&VideoCodec=h264,mpeg2video,hevc,h265&AudioCodec=aac,mp3&AudioStreamIndex=2&VideoBitrate=109616000&AudioBitrate=384000&PlaySessionId=3046faec710942b4a2e07438960f6f88&api_key=a1360396dff24359b403963e0209d3b6&CopyTimestamps=true&RequireAvc=false&Tag=dd3664b2c5c3c93da58aa95586195d4c&SegmentContainer=ts&MinSegments=2&BreakOnNonKeyFrames=True&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&hevc-profile=Main,Main10&audiochannels=8&TranscodeReasons=VideoCodecNotSupported
...
03-20 16:13:54.329  4652  4652 E EventLogger: Caused by: java.net.SocketTimeoutException

That could very well be why some of your items are falling over to transcode.

 

I suspect the wireless network.

 

I forgot to clarify, I'm using ethernet on the mi box, on the phone obviously wireless.

Link to post
Share on other sites
Richard Branches

server, ffmpeg log?

 

I can't provide with a log at this time because my trial on emby app for ATV already expired, I can't even play the minute you said once, however, I sent the log from emby app at 4:16 pm on 20/03/18. @@ebr

Link to post
Share on other sites
  • Richard Branches changed the title to Video delay with MPEG-4 and VC-1 videos

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...