1. No user installed addons are supported, python or otherwise.
2. No, they really are not supported.
3. They are not coming back
4. Read from 1. again

Any mention of illegal streaming sites, addons or any pirated material will not be tolerated. This is not democracy and any offenders will be banned and posts deleted immediately without warning.

Other than that, we hope you enjoy MrMC so far and we welcome any input and feedback you might have.

Team MrMC.

Force refresh rate of our choosing at playback.

there is zero(0) promises that any of the requests will be fulfilled or even looked at
Post Reply
cosmoxl
Posts: 1759
Joined: 12 Dec 2015, 14:16

Force refresh rate of our choosing at playback.

Post by cosmoxl »

We got some new DVDs in from Amazon so I went about ripping them with makemkv. I wouldn't usually buy DVD but that's all there is. They are encoded as variable frame rate which is nice, but also can complicate things.

Playback on the shield tv with both MrMC (ffmpeg) and SPMC (mediacodec surface) looks fine but there are some weird things happening with the detection of the source video framerate and output refresh rate switching.

I've seen source framerate detected as 29.97 and 30 with MrMC and 29.97 or 59.94 by SPMC. Of course, the pulldown correction varies as they try to reconstruct the original framerate.

But, that's still not ideal because the refresh rate the TV is told to use is either 59.94 or 60. So, I'll never get the proper 24fps the original film used.

My request is that there be a way to force a refresh rate of our choosing (in this case 23.97fps) upon playing a video. If the output refresh rate is forced to 23.97 then I assume the decoder/renderer will do the proper pulldown correction to restore the film.

BTW, for DVD what deinterlacing method is best? I'm currently using bob-inverted, same as for 1080i TV.
cosmoxl
Posts: 1759
Joined: 12 Dec 2015, 14:16

Re: Force refresh rate of our choosing at playback.

Post by cosmoxl »

Any thoughts on this Davilla or Amet?
User avatar
davilla
Team MrMC
Posts: 4377
Joined: 26 Oct 2015, 17:01

Re: Force refresh rate of our choosing at playback.

Post by davilla »

Well if the source is detected at 29.97, then you should be fine with either 29.97 or 59.94. 30 or 60 would be not optimal.

Same for 30, it source is 30, then 30 or 60 is fine. 29.97 or 59.94 would not be optimal.

Then you start mentioning 23.97 and my head explodes :) It's possible to prompt for desired display frame rate but that gets real tricky as the point at which we know is rather critical in video startup. There are timeouts running and those would have to be delayed until the user selects something.

The other way is something in settings but then I would bet a dollar that despite the setting, there would always be some video that tricks it.

Are you saying MrMC does it wrong ? You know the drill, I'd need samples :)


Some deinterlace methods also depends on codec.

Bob and Bob Invert are GPU shaders so anything but Mediacodec (surface) works with them.

YADIF is coupled to FFMpeg codec.

For AppleTV4 and firetv, bob inverted. For shield, it has much more ponies so for SD content, FFMpeg and YADIF looks better for some people.

For HD content, then Shield and YADIF then depends on decoder flavor (h264, vc1, etc) as you are have to use FFMpeg(sw decode) to get YADIF.

The thing to remember is YADIF mean FFMpeg and that means software decode.
cosmoxl
Posts: 1759
Joined: 12 Dec 2015, 14:16

Re: Force refresh rate of our choosing at playback.

Post by cosmoxl »

davilla wrote: 27 Apr 2017, 19:57 Well if the source is detected at 29.97, then you should be fine with either 29.97 or 59.94. 30 or 60 would be not optimal.

Same for 30, it source is 30, then 30 or 60 is fine. 29.97 or 59.94 would not be optimal.

Then you start mentioning 23.97 and my head explodes :) It's possible to prompt for desired display frame rate but that gets real tricky as the point at which we know is rather critical in video startup. There are timeouts running and those would have to be delayed until the user selects something.

The other way is something in settings but then I would bet a dollar that despite the setting, there would always be some video that tricks it.

Are you saying MrMC does it wrong ? You know the drill, I'd need samples :)


Some deinterlace methods also depends on codec.

Bob and Bob Invert are GPU shaders so anything but Mediacodec (surface) works with them.

YADIF is coupled to FFMpeg codec.

For AppleTV4 and firetv, bob inverted. For shield, it has much more ponies so for SD content, FFMpeg and YADIF looks better for some people.

For HD content, then Shield and YADIF then depends on decoder flavor (h264, vc1, etc) as you are have to use FFMpeg(sw decode) to get YADIF.

The thing to remember is YADIF mean FFMpeg and that means software decode.
Bottom line is that playback isn't near as smooth as it should be on any device I have. I can play the rips with my oppo bdp, which was collecting dust, and they look awesome. I guess it's just tuned to know how to handle these files. In fact, if I play the actual DVD in the oppo it outputs them as 23.976 and they look great. If I play the DVD rips via DLNA the oppo just outputs 59.94fps. Apparently it can't do the DVD to 23.976 trick with ripped media.

Media Info has this to say about the video - it varies depending on the episode.

Video
ID : 1
ID in the original source medium : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Codec ID : V_MPEG2
Codec ID/Info : MPEG 1 or 2 Video
Duration : 1 h 31 min
Bit rate mode : Variable
Bit rate : 5 181 kb/s
Maximum bit rate : 9 800 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate mode : Variable
Frame rate : 24.565 FPS
Original frame rate : 29.970 (30000/1001) FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.610
Time code of first frame : 00:59:59;00
Time code source : Group of pictures header
Stream size : 3.33 GiB (92%)
Language : English
Default : No
Forced : No
Color primaries : BT.601 NTSC
Transfer characteristics : BT.601
Matrix coefficients : BT.601

OR

Video
ID : 1
ID in the original source medium : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Codec ID : V_MPEG2
Codec ID/Info : MPEG 1 or 2 Video
Duration : 43 min 58 s
Bit rate mode : Variable
Bit rate : 5 464 kb/s
Maximum bit rate : 9 800 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate mode : Variable
Frame rate : 24.670 FPS
Original frame rate : 23.976 (24000/1001) FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Scan order : 2:3 Pulldown
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.641
Time code of first frame : 00:59:58;00
Time code source : Group of pictures header
GOP, Open/Closed : Open
GOP, Open/Closed of first frame : Closed
Stream size : 1.68 GiB (92%)
Language : English
Default : No
Forced : No
Color primaries : BT.601 NTSC
Transfer characteristics : BT.601
Matrix coefficients : BT.601

OR

I'm sure I saw another ep somewhere where it said scan type was interlaced, TFF. I think it just depends on which part of the file mediainfo scans.
Post Reply