Moving to NPVR/NMT to NPVR+Fire TV/XBMC

[jt25741]

First, I'm glad it doesn't bother you and there are a lot of people that don't mind. Panning and all motion really annoy me maybe because of the I watch sports and action movies. I just turned it off and this is a capture with of 1080i interlacing on the Miami player running.

There's a lot of info on renaming for Kodi/XBMC around. I've been using my utility imageGrabLite for years to rename files to XBMC standards and there are a a couple of other utilities here that do renaming.

Martin

Hi Martin........wonder if you have given Bob deinterlacing a try on Kodi 15 Android. I would like to know what you think about the quality now, and if it is better.

http://kodi.wiki/view/New_features

[mvallevand]

Hi Martin........wonder if you have given Bob deinterlacing a try on Kodi 15 Android. I would like to know what you think about the quality now, and if it is better.

http://kodi.wiki/view/New_features

I don't use my FTV with Kodi since I like my Chromebox so much but that is probably the same as the beta version code that people commented on as being pretty good. It's more important if you are happy with it. Until little SoC boxes have PC CPU speed I won't recommend software decoding of anything that plays HD.

Martin

[jt25741]

If you get around to dusting off the FTV and trying it with NPVR, HD at least for now it seems Bob-Inverse works the best......Still not quite as smooth as the Sigma chip in PCH, but much better than the choppy panning scenes when watching live sports. Using Bob, not Bob-Inverse, causes lots of choppiness. My understanding is this uses HW support for deinterlacing, but I maybe misinformed.

[mvallevand]

If you get around to dusting off the FTV and trying it with NPVR, HD at least for now it seems Bob-Inverse works the best......Still not quite as smooth as the Sigma chip in PCH, but much better than the choppy panning scenes when watching live sports. Using Bob, not Bob-Inverse, causes lots of choppiness. My understanding is this uses HW support for deinterlacing, but I maybe misinformed.

It's still my preferred Netflix player it's not gathering dust. AFAIK still no h/w deinterlacing and with a new box due soon it probably won't happen.

Martin

[jt25741]

Didnt realize BOB support is SW interlacing? I have tried it with a bunch of sports channels last night -- since my cable provider is going all digital and I broke down and got a HDhomerun Prime with Cablecard -- so I have many more digital channels accessible now in my package. Kodi 15.1 (latest I could find). There is a big difference is panning....jittery playback with it off, vs on. But I was only able to get reasonably reliable/stable results with Bob-inverse mode... Bob mode actually made things worse. I dont know the difference between Bob and Bob Inverse mode...but it is big on the FireTV -- maybe cause these features are so new on Android. Interestingly, while setting it to Bob-Inverse and looking at the system resource utilization and CPU meters....... CPU utilization is no higher...perhaps even lower in this mode (using approximately 50% of each core leaving 1/2 system resources available). So it seems if SW deinterlacing is going on at 1080i, it is not taxing whatsoever to the CPUs. There is one channel I get that is H.264 1080 --- and for this one everything runs in slow-motion unless I disable mediacodec and select only libstagefright. So for now I just use libstagefright again for everything, set deinterlace to auto, and mode to bob-inverse.

[mvallevand]

You'd have to find a 720p station to see what the impact of deinterlacing is. Anyway glad it is working for you and just as glad Amazon fixed the stagefright vulnerability last week.

Martin