Jump to content


Photo
- - - - -

Error in rendering on Chrome top vs bottom half?

bug chrome webapp

Best Answer softworkz , 07 January 2020 - 02:29 AM

The frozen segments are of no concern.

 

I'm pretty sure that it's a Chrome issue.

Otherwise I can only speculate.

One thing that comes to my mind: It's not unusual to slice a video to parallellize the decoding operation. Maybe this is what happens and the two slices are getting out of sync

 

You might want to play with this:

 

chrome://flags/

 

and this:

 

chrome://media-internals/

 

 

But this is not an Emby issue.

Go to the full post


  • Please log in to reply
6 replies to this topic

#1 sebasmiles OFFLINE  

sebasmiles

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:53 AM

Posted 06 January 2020 - 10:03 PM

Browser: Chrome

App: Emby Web 4.3.1.0

 

Problem: This isn't a big deal for me, but its just odd and figured its best to report it. If you look at the Capture.jpg, you can see a bar across the middle where the screen and even the resolution seems offset. Its basically like the top and bottom half of the screen aren't rendering at the same time. I tried with Edge and didn't experience this problem (remux file attached). At first I thought it might be because I use Muximux, but opening the window direct yielded the same issue (btw. on a related note, if you use muximux it shows as transcoding but using a dedicated window actually goes as direct streaming, not sure what triggers the difference). What I think are both remux logs are included for those but I'm not 100% certain (so there are actually 3 that I found, probably hit refresh at some point).

Attached Files



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156602 posts
  • Local time: 01:53 AM

Posted 06 January 2020 - 10:09 PM

The red bar is The part that has been transcoded.

#3 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2693 posts
  • Local time: 07:53 AM

Posted 06 January 2020 - 10:48 PM

@sebasmiles - Do you mean the picture offset next to the lips of the right girl?

 

I'm not sure what that is, but at least it's not caused by the server because the video is stream-copied.

 

Although, it doesn't appear to be a continuous offset across the full with because the window borders are not affected (I mean the window in the video).

 

What's your client OS?

Are the screenshots taken from Chrome?

Did you operate the client computer locally or from remote?

What happens when make the Chrome Browser window smaller?

 

PS: Let's leave out any 3rd party stuff, no matter how funny the name might be..



#4 sebasmiles OFFLINE  

sebasmiles

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:53 AM

Posted 07 January 2020 - 12:22 AM

@sebasmiles - Do you mean the picture offset next to the lips of the right girl?

 

I'm not sure what that is, but at least it's not caused by the server because the video is stream-copied.

 

Although, it doesn't appear to be a continuous offset across the full with because the window borders are not affected (I mean the window in the video).

 

What's your client OS?

Are the screenshots taken from Chrome?

Did you operate the client computer locally or from remote?

What happens when make the Chrome Browser window smaller?

 

PS: Let's leave out any 3rd party stuff, no matter how funny the name might be..

Yep, I meant that offset near the lips. Weird right? The line does actually go all way across though its harder to see sometimes, or like the center effect is worse than the edges? The error also seems to be file dependent, I have attached a remux of a different file that doesn't have the issue. Maybe its something specific to the encoding type that is slightly different between both?

I am running Win 10. I took the screenshot of the Chrome client using the windows snipping tool.

I am sitting on the client computer, so operating locally.

Chrome Version 79.0.3945.88 (Official Build) (64-bit)

 

PS. The 3rd party stuff is one of those overlays that joins all my various app weblinks in the same place to make it easier to switch between. I guess its like a wrapper or something, just letting you know about it in case you get weird questions in the future about why its transcoding vs directplay, it might be also related to a wrapper like this. In any case, I'm testing without it right now to avoid other sources of error.

Attached Files



#5 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2693 posts
  • Local time: 07:53 AM

Posted 07 January 2020 - 12:35 AM

What happens when you make the browser window smaller?

 

During playback, go to Emby's transcoding-temp folder and copy one of the segments to another place. After stopping playback, play that copied segment in VLC media player to see how it looks like.



#6 sebasmiles OFFLINE  

sebasmiles

    Advanced Member

  • Members
  • 32 posts
  • Local time: 01:53 AM

Posted 07 January 2020 - 01:45 AM

What happens when you make the browser window smaller?

 

During playback, go to Emby's transcoding-temp folder and copy one of the segments to another place. After stopping playback, play that copied segment in VLC media player to see how it looks like.

Ah I know something got lost when it didn't save my full answer. When I resize the window its still there, windowed, full screen, smaller window, etc.

I tried opening a few of the TS files in VLC, doesn't seem to like doing that. Several will show a frozen image for like 5s, then it will play like a second or two with some corruption in the image some times, then it stops. Though the video doesn't show the middle line as far as I can see.

PS. Lowering the bitrate to force it to transcode gets rid of the line.



#7 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2693 posts
  • Local time: 07:53 AM

Posted 07 January 2020 - 02:29 AM   Best Answer

The frozen segments are of no concern.

 

I'm pretty sure that it's a Chrome issue.

Otherwise I can only speculate.

One thing that comes to my mind: It's not unusual to slice a video to parallellize the decoding operation. Maybe this is what happens and the two slices are getting out of sync

 

You might want to play with this:

 

chrome://flags/

 

and this:

 

chrome://media-internals/

 

 

But this is not an Emby issue.


  • sebasmiles likes this





Also tagged with one or more of these keywords: bug, chrome, webapp

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users