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.

native 24p video files problem.

tvOS Video playback support subforum
tml2k2
Posts: 2
Joined: 29 Dec 2017, 04:15

native 24p video files problem.

Post by tml2k2 »

Hello, Dev please support file playback with this type of video (24p) not 23.796fps. This file start out fine but after a while seem like the drop frames catching up the playback starts to judder the only way to fix it is to stop the video and play again. However after while thing will be the same.
User avatar
davilla
Team MrMC
Posts: 4377
Joined: 26 Oct 2015, 17:01

Re: native 24p video files problem.

Post by davilla »

Are you AppleTV 4K with display rate switching enabled ? tvOS needs to support pure 24Hz was well as the current 23.97Hz.

Regardless, 24Hz media content works here. Need to see a debuglog (<- click link).
tml2k2
Posts: 2
Joined: 29 Dec 2017, 04:15

Re: native 24p video files problem.

Post by tml2k2 »

Yes, on Apple TV 4k everything latest including your software, refresh rate matching set in MRMC, every frame rates I threw at it plays just fine including (23.796fps,25fps,30fps,60fps) except the pure 24p videos.
User avatar
davilla
Team MrMC
Posts: 4377
Joined: 26 Oct 2015, 17:01

Re: native 24p video files problem.

Post by davilla »

tml2k2 wrote: 29 Dec 2017, 16:50 Yes, on Apple TV 4k everything latest including your software, refresh rate matching set in MRMC, every frame rates I threw at it plays just fine including (23.796fps,25fps,30fps,60fps) except the pure 24p videos.
We will double check and verify. A debuglog would still be helpful
User avatar
costaud
Posts: 51
Joined: 27 May 2017, 22:28

Re: native 24p video files problem.

Post by costaud »

It seems that APPLE TV 4K doesn't support 24Hz.
I tested with many players and always the same issue, all 24Hz files are played at 23.976 :(
Sledgehamma
Posts: 1
Joined: 27 Feb 2018, 12:40

Re: native 24p video files problem.

Post by Sledgehamma »

I have the same issue:

-video with 24.000 fps gets outputted as 23.976
-video with 60.000 fps get outputted as 59.94

So is this an Apple limitation as they dont allow these HDMI refresh rates?
User avatar
davilla
Team MrMC
Posts: 4377
Joined: 26 Oct 2015, 17:01

Re: native 24p video files problem.

Post by davilla »

Please being this to the attention of Apple. There is nothing we can do.
Boulder
Posts: 18
Joined: 20 Mar 2018, 07:46

Re: native 24p video files problem.

Post by Boulder »

Is changing playback speed to 23.976 fps (while resampling audio to match) inside MrMC out of the question? Apple just basically told me that they are not going to implement support.
barong
Posts: 78
Joined: 07 Nov 2017, 07:33

Re: native 24p video files problem.

Post by barong »

I suggest posting feedback here:
https://www.apple.com/feedback/appletv.html

You can use something like this in the notes:
Currently Apple TV 4K uses frame rate approximation for 24.00hz content, it gets output by the Apple TV at 23.976hz.
This causes playback skips periodically throughout playback.
An example of this content includes Birdbox, IO, Close etc on Netflix, but this is not limited to Netflix as there are also movies on iTunes encoded at 24.00hz frame rate.
I believe that the Apple TV needs to support 24.00hz output, or add in an option to not match frame rates unless it is an exact match. Thanks in advance.
Boulder
Posts: 18
Joined: 20 Mar 2018, 07:46

Re: native 24p video files problem.

Post by Boulder »

I tried contacting them via problem reporting earlier, but maybe I'll also try to give feedback. It won't hurt the case at least. Funny thing is that based on the answer I got from them in the problem ticket, they didn't seem to understand the difference between native 24p and the much more common 24000/1001 fps content.
Post Reply