Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FTV 4K 3rd gen (pendant) erratic (but predictable) deinterlace error #90

Open
leone007 opened this issue Apr 27, 2019 · 3 comments
Open

Comments

@leone007
Copy link

leone007 commented Apr 27, 2019

Some interlaced H264 1080i streams won't be HW deinterlaced on FTV 4K 3rd gen.

Using a tvheadend server I'm streaming - source is HDHomerun, method is pass through, not enough HP for transcoding yet - H264 1080i channels to different clients, and the channels have 3 different behavior when watched in kodi/mrmc/vlc or dream player for tvheadend on FTV 4K 3gen (pendant).

  1. deinterlaceable (123 MB sample, channels will be automatically HW deinterlaced)
Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Bottom Field First
  1. un-deinterlaceable (92 MB sample, channels cannot be HW deinterlaced)
Scan type                                : MBAFF
Scan type, store method                  : Interleaved fields
Scan order                               : Top Field First
  1. hectic (234 MB sample, switches between deinterlaced/interlaced during playback)
Scan type                                : MBAFF
Scan type, store method                  : Separated fields
Scan order                               : Top Field First

The behaviour always pairs with the same channels, it isn't random. All channels are perfectly HW deinterlaced on x86 systems (LE or win10)

SW version: NS6260/1840
Fire TV Home Version 6.1.5.1-002

It appears that the problem is with MBAFF. Will gather more samples to solidify my theory.

@humiboy
Copy link

humiboy commented May 11, 2019

The FireTV Stick 4K have only bugs with not fixed after 6 month

@leone007
Copy link
Author

leone007 commented Jun 24, 2019

Since you guys from @amzn closed the other topic we might as well carry on here. If you don't understand that this small community of ppl wants to help you to make your product better (well, functional at least) and by closing down threads you think you can (and should) silence the voices of the few who spends their own time supporting you, and providing data and feedback, you are just simply wrong.

Obviously someone was reading this, so please can we have some answers?

Like is there and if there is what is the difference between ver. 1995 and 1996?

Do you need more files to provide further samples of MP crashing videos?

@rinoshs
Copy link
Contributor

rinoshs commented Jun 24, 2019

This issue is specific to the 4k pendant. Regarding 4k stick, I would suggest that you create a new issue for your specific issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants