MrMC

I'm currently using tvheadend in kodi and spmc for live tv viewing from my tv server. Both of these work well (on a shield, Chromebox and pi) with some quality deinterlacing.

I'd like to add another client and am thinking of getting a fire tv 1. When I previously had a fire tv it was shocking at deinterlacing SD mpeg2 and HD h.264.

How is MrMC at deinterlacing? I like the idea and ethos behind MrMC, but need a platform which is good for live tv.

Thanks in advance for any comments.

seems fine for me with 1080i usa content.

davilla wrote:seems fine for me with 1080i usa content.

You are not watching soccer games, right?
Btw. could you please comment on this question regarding deinterlacing http://mrmc.tv/forum/viewtopic.php?f=18&t=585#p4041?

Thanks again for your support here nd dat great Software

davilla wrote:seems fine for me with 1080i usa content.

Thanks for that - guess the only way I'm going to know for me is trying it...

vlaves wrote:

davilla wrote:seems fine for me with 1080i usa content.

You are not watching soccer games, right?
Btw. could you please comment on this question regarding deinterlacing http://mrmc.tv/forum/viewtopic.php?f=18&t=585#p4041?

Thanks again for your support here nd dat great Software

I do watch a lot of football - is it not good for fast moving videos?

Deinterlacing is like religion, every one has their preferred view

The thing to keep in mind is that no deinterlacer can perfect. They all have side effects due to their very nature of trying to combine two fields that are different in time. For the best 'fast motion', the best is line doubling which results in 'loss' of vertical resolution. But you will never see motion artifacts with line doubling. The others can introduce edge ringing and other strange artifacts like local blooming.

The more 'advanced' deinterlacers can take a large amount of CPU/GPU resources. On desktop, using something like a 6-8 core Intel I7, this usage does not matter. However on embedded arm like iOS/tvOS and fireOS, you just do not have the CPU/GPU resources available.

MrMC uses inverse bob for iOS/tvOS and fireOS. This seems to give the best balance between looking good and available CPU/GPU resources. We do keep aware of advances in FFMpeg, specifically when code is added to support asm/neon and such as this would be a performance boost for those functions.

davilla wrote:Deinterlacing is like religion, every one has their preferred view

The thing to keep in mind is that no deinterlacer can perfect. They all have side effects due to their very nature of trying to combine two fields that are different in time. For the best 'fast motion', the best is line doubling which results in 'loss' of vertical resolution. But you will never see motion artifacts with line doubling. The others can introduce edge ringing and other strange artifacts like local blooming.

The more 'advanced' deinterlacers can take a large amount of CPU/GPU resources. On desktop, using something like a 6-8 core Intel I7, this usage does not matter. However on embedded arm like iOS/tvOS and fireOS, you just do not have the CPU/GPU resources available.

MrMC uses inverse bob for iOS/tvOS and fireOS. This seems to give the best balance between looking good and available CPU/GPU resources. We do keep aware of advances in FFMpeg, specifically when code is added to support asm/neon and such as this would be a performance boost for those functions.

Thanks very much for that.

I believe the shield uses inverse Bob in spmc too. That works really well, so hopefully it will be as good with the fire tv