MrMC

fixed, enable YADIF, YADIF_half for arm/arm64
fixed, h264/interlaced under MediaCodec
fixed, certain eac3/640kps fail under darwin/audiotoolbox. vector all 640kps to ffmpeg until fixed
fixed, skin.amber: fix lost focus on home screen
fixed, remove legacy read size clamps from libdsm/libsmbclient
fixed, mpeg2/interlaced under ffmpeg
added, unifont to all skin Font.xml
changed, read bandwidth limiter and increase our transfer buffer sizes.
backport, various upstream/sidestream fixes and changes
version bump, libnfs to 1.11.0

updated
3.0-1 Git:2017-03-03-0a983b4
fixed, WOA for amazon/droid
fixed, various crashing issues regarding buffer reading increases
fixed, recommended icon
changed, enable file caching for bluray m2ts files

Hi Davilla,

Unfortunately, the new deinterlace settings are not working for me. I am getting exactly the same behaviour as SPMC where i can't use a setting that works in all scenarios. Just so you are aware, im in the UK and we have a mixture of h264 and mpeg2 50hz. I've linked 2 clips from news channels that have the ticker along the bottom of the screen - its a good indicator to if deinterlace settings are working.

H264 - interlaced - https://drive.google.com/open?id=0BwR6Z ... zQyWm1zekk
MPEG2 - interlaced - https://drive.google.com/open?id=0BwR6Z ... GNQbFctV28

So, with these clips:

1) MPEG2 will only work with ffmpeg (to be expected - just thought i would get it out of the way!)
2) MediaCodec Surface is definitely not deinterlacing the H264 clip. You can clearly see the ticker is not smooth. No settings make any difference for me (off, on or auto) - video always looks the same.
3) If i use mediacodec (NOT surface) on the H264 clip, i have to use Bob, not Bob Inverted. MPEG2 (via FFmpeg) has to use Bob Inverted. If i set one setting as the default then it messes the other up.
4) MediaCodec (NOT surface) in H264 is fine on some channels, but drops frames like crazy on Channel 4. Just try the clip i sent the other day - https://drive.google.com/open?id=0BwR6Z ... WN2WDZZenc . Using Mediacode Surface this clip plays fine but I can clearly see that its not being deinterlaced and isn't smooth.

Only solution for me now is to disable all Hardware Acceleration. However, this means my HEVC files aren't working. I can live with that for now as i don't have many.

Let me know if you need any other info!

James

Will take another look at your samples this weekend. Just to be clear, firetv1 or firetv2 ?

firetv 2

did some testing/tweaks.

before:
MediaCodec(S) enable:
"H264 Interlaced.ts" looked fine for me, the ticker looks exactly the same as with MediaCodec(n_S) and Bob or FFmpeg and Bob Inverted
"Channel 4 Test.mkv" was fine.

MediaCodec(n_S) enabled:
"H264 Interlaced.ts" vs "MPEG2 Interlaced.ts", saw same Bob vs Bob Inverted behavior.
"Channel 4 Test.mkv" was dropping frames.

Interlaced is normally top field first (TFF), the other flavor is bottom field first (BFF). MediaInfo shows all your interlaced samples as TFF. FFMpeg returns which is detected. This info is not present under MediaCodec, in fact. it does not even flag it as interlaced so not even sure how it treats it Ideally, it should detect the field associated with the frame but this is rather difficult with h264. So I added brute forced flagging as interlaced/TFF and this gave me same behavior which means somewhere in our sea of code, it is flagged as interlaced/TFF. Next changed flagged to BFF and now it matches FFmpeg behavior. Odd but so be it.

Also dropped a frame render timeout from 50ms to 20ms. This fixed "Channel 4 Test.mkv" frame drops so now it plays identical under MediaCodec(S) or MediaCodec(n_S). This one is also odd, it's been 50ms since I authored MediCodec several years ago. Does not see to effect anything else and I'll poke deeper later.

after:
MediaCodec(S) enable:
"H264 Interlaced.ts" still looked fine for me.
"Channel 4 Test.mkv" was fine.

MediaCodec(n_S) enabled:
"H264 Interlaced.ts" with Bob Inverted is good.
"Channel 4 Test.mkv" with Bob Inverted is good.

MPEG2 Interlaced.ts with FFMpeg/Bob Inverted is good.

The codec pick order is MediaCodec(S) , MediaCodec(n_S) and fallback is FFmpeg.
What I can do is add an "exclude h264 interlaced" in MediaCodec(S) and MediaCodec(n_S), that way h264/interlaced can be set to fallback through MediaCodec(S) to MediaCodec(n_S) or all the way down to FFMpeg.

As always - thanks for looking into it!

Suppose the most surprising thing is that MediaCodec Surface is deinterlacing for you. I wondered if the settings of the device might influence this, so tried changing the device from auto to 60hz and 50hz, with and without audio passthrough. Nothing changed anything for me - there is no difference between setting deinterlacing to auto, off or on. I was hoping that MediaCodec surface was going to end the bouncy reds we see with Bob. There has to be a reason for this - is there any sort of log i can send you from my system that may help. I suppose that you probably don't get much logging back from MediaCodec.

Glad that some tweaks have helped MediaCodec though and you have a solution to the bob/bob inverted issue. Personally, i would rather some form of hardware acceleration was being used so just having a flag to "exclude h264 interlaced in MediaCodec(S)" would suit me, but having 2 options to exclude both would probably make sense as ffmpeg has proven to be pretty reliable.

Let me know if anything else will help, we use MrMc everyday in my house so much interested in its continued development!

how about a fresh debuglog , that might show me something about your setup.

Also what hdtv ? Mine is a samsung uhdtv and it's quite hard to see normal deinterlace artifacts as it is quite good at hiding them. But I know what to look for I have pretty much every picture handling feature 'off' already on it.

Hi,

Debug log here - https://drive.google.com/open?id=0BwR6Z ... 1FfTS1vNlE

For the log, I opened up MrMC and just played the h264 news clip. I have no idea how your software works, but located the following line in the log:

10:44:27 T:367335444944 DEBUG: CSettingsManager: requested setting (video.deinterlacemode) was not found.

Maybe a clue - maybe not!

In terms of my setup, my Amp and TV are a bit old. I have a Onkyo HTX-22HD AMP which supports Dolby + and DTS, and an ageing Toshiba LCD 40 inch HDTV. Fire TV is plugged into the Amp and the AMP plugged into the TV. All post processing on the TV is turned off (i am very sensitive to any of that crap!). I tried plugging the FireTV directly into the TV but the result was the same.

I took a much, much closer look at h264/interlaced behavior under both MediaCodec(S) and MediaCodec(no-S). On FireTV2 and Shield.

Well, just smack me silly with a fish but you are correct. On FireTV2, both flavors of MediaCodec just decode, they do not do any form of internal deinterlacing. With MediaCodec(no-S), we can to the deinterlace via GPU (Bob or Bob Invert). With MediaCodec(S), what we get is what we get.

On Shield, both flavors of MediaCodec do internal deinterlacing. You can see this via logcat, when starting playback. A deinterlacing thread is created. There does not seem to be a way to disable it. Doing MediaCodec(no-S) and adding a second level of deinterlacing is bad. And some forms of media content will actually playback bad as the framerate calculated wrong. Added clamps to prevent that.

FireTV2 is API 22, Shield is API 24. Not sure if this internal deinterlacing is a required property API 23+ or a property of the Nvidia decoder.

Interesting

Hi Davilla,

Thanks for all your hard work.

Will it be going back to the ffmpeg approach? I'm UK based as well, fire tv 2, V3.0.0 for me was perfect, no drops or skips.