Page 29 of 42
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 08:33
by amet
cosmoxl wrote: 22 Mar 2018, 18:52
Anybody else lose the new user interface that came out in 3.5? Now I only get the old "expert" even though expert is disabled.
I deleted MrMC and set it up from scratch just to make sure.
I'd post a log but it seems gist won't let me without an account now.
you are not alone ... same here.. let us look into what caused it

Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 11:12
by davilla
brians wrote: 23 Mar 2018, 04:56
I always set MrMC to use AV Foundation (disabling Video Toolbox). Even though it is not as smooth when skipping forward/back and video may glitch doing this, I find it gives superior PQ for the most part. Most video with low-light scenes look very bad with Video Toolbox - lots of washed-out looking blacks/grays, things look dithered and/or pastel-like (does anyone else notice this?)
With new 3.5.1 I notice that I have very bad performance issues with stuttering and jerky playback using the new Plex add-on. Plex playback in native MrMC works fine. I discover that setting it back to use Video Toolbox makes it play much better with Plex add-on. Presuming that most people probably leave default to play using Video Toolbox they may not notice this. Can anyone else try and verify if they also get very back playback when using only AV Foundation? It seems to do this pretty much every time when skipping through video and pretty much all the time with HEVC.
The default settings are there for a reason, video content in h264 format can contain a lot of bad encoding with non-spec profiles/levels. h265 is less problematic. So VideoToolBox has much more robust error handling than AVFoundation.
Use
mediainfo to quality problem videos under VideToolBox and samples go a long way for us to understand issues. As mentioned elsewhere, setting brightness to 46 percent yields perfect match to test/calibration video content. Even so, if the test/calibration sources pass or are close, the content should look as it was intended to look.
One issue we just discovered is that some hevc encoded videos are posing as HDR while in-fact, they are SDR. Encoder abuse we call it

Looking into fixing this.
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 13:50
by jrcorwin
davilla wrote: 23 Mar 2018, 11:12
brians wrote: 23 Mar 2018, 04:56
I always set MrMC to use AV Foundation (disabling Video Toolbox). Even though it is not as smooth when skipping forward/back and video may glitch doing this, I find it gives superior PQ for the most part. Most video with low-light scenes look very bad with Video Toolbox - lots of washed-out looking blacks/grays, things look dithered and/or pastel-like (does anyone else notice this?)
With new 3.5.1 I notice that I have very bad performance issues with stuttering and jerky playback using the new Plex add-on. Plex playback in native MrMC works fine. I discover that setting it back to use Video Toolbox makes it play much better with Plex add-on. Presuming that most people probably leave default to play using Video Toolbox they may not notice this. Can anyone else try and verify if they also get very back playback when using only AV Foundation? It seems to do this pretty much every time when skipping through video and pretty much all the time with HEVC.
The default settings are there for a reason, video content in h264 format can contain a lot of bad encoding with non-spec profiles/levels. h265 is less problematic. So VideoToolBox has much more robust error handling than AVFoundation.
Use
mediainfo to quality problem videos under VideToolBox and samples go a long way for us to understand issues. As mentioned elsewhere, setting brightness to 46 percent yields perfect match to test/calibration video content. Even so, if the test/calibration sources pass or are close, the content should look as it was intended to look.
One issue we just discovered is that some hevc encoded videos are posing as HDR while in-fact, they are SDR. Encoder abuse we call it

Looking into fixing this.
Sorry, I am a little confused. I’ve tried using Video Toolbox and noticed the washed out appearance also. The solution to that is to adjust the MrMC brightness control to 46?
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 14:18
by cosmoxl
jrcorwin wrote: 23 Mar 2018, 13:50
davilla wrote: 23 Mar 2018, 11:12
brians wrote: 23 Mar 2018, 04:56
I always set MrMC to use AV Foundation (disabling Video Toolbox). Even though it is not as smooth when skipping forward/back and video may glitch doing this, I find it gives superior PQ for the most part. Most video with low-light scenes look very bad with Video Toolbox - lots of washed-out looking blacks/grays, things look dithered and/or pastel-like (does anyone else notice this?)
With new 3.5.1 I notice that I have very bad performance issues with stuttering and jerky playback using the new Plex add-on. Plex playback in native MrMC works fine. I discover that setting it back to use Video Toolbox makes it play much better with Plex add-on. Presuming that most people probably leave default to play using Video Toolbox they may not notice this. Can anyone else try and verify if they also get very back playback when using only AV Foundation? It seems to do this pretty much every time when skipping through video and pretty much all the time with HEVC.
The default settings are there for a reason, video content in h264 format can contain a lot of bad encoding with non-spec profiles/levels. h265 is less problematic. So VideoToolBox has much more robust error handling than AVFoundation.
Use
mediainfo to quality problem videos under VideToolBox and samples go a long way for us to understand issues. As mentioned elsewhere, setting brightness to 46 percent yields perfect match to test/calibration video content. Even so, if the test/calibration sources pass or are close, the content should look as it was intended to look.
One issue we just discovered is that some hevc encoded videos are posing as HDR while in-fact, they are SDR. Encoder abuse we call it

Looking into fixing this.
Sorry, I am a little confused. I’ve tried using Video Toolbox and noticed the washed out appearance also. The solution to that is to adjust the MrMC brightness control to 46?
No, he's saying that with VideoToolbox you can match what AVF gives with levels testing videos by adjusting contrast to 46. At least that's the adjustment that most people make.
If you're having other problems with VTB then perhaps it would be better to make a different thread showing the problems you see.
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 14:18
by cosmoxl
amet wrote: 23 Mar 2018, 08:33
cosmoxl wrote: 22 Mar 2018, 18:52
Anybody else lose the new user interface that came out in 3.5? Now I only get the old "expert" even though expert is disabled.
I deleted MrMC and set it up from scratch just to make sure.
I'd post a log but it seems gist won't let me without an account now.
you are not alone ... same here.. let us look into what caused it
OK, it had been several hours and no confirmation so I was a little worried.

Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 14:54
by davilla
(180323.1058 @20180323-d4ced22)
revert core: ignore window/dialog when making UIViews
darwin: fixed iOS mirroring
darwin: fixed iOS dim bug, screen scaling was wrong
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 15:07
by Itzme1234
Updated, really enjoyed the behavior on that first click on MrMc

Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 15:17
by cosmoxl
davilla wrote: 23 Mar 2018, 14:54
(180323.1058 @20180323-d4ced22)
revert core: ignore window/dialog when making UIViews
darwin: fixed iOS mirroring
darwin: fixed iOS dim bug, screen scaling was wrong
yay, all is well now.
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 16:06
by LePousson
davilla wrote:(180323.1058 @20180323-d4ced22)
revert core: ignore window/dialog when making UIViews
darwin: fixed iOS mirroring
darwin: fixed iOS dim bug, screen scaling was wrong
The drop down menu for the settings (pressing DOWN when video is paused) is now back ...
Thanks for this update !
LePousson
Re: Testing MrMC 3.5.1
Posted: 23 Mar 2018, 16:36
by davilla
Sorry for the snafu, in going after the crash (memory oinker) messed up tvOS focus engine handling, Opps.
