Testing MrMC 3.4.1

[wrxtasy]

Then a good default is 10 back / 30 forward, because this is the way alot of DVRs work. I think its the way MrMc worked before all this, too.

This is exactly the way I use TvHeadend on all devices. Particularily after recording sport. 30 seconds forward is perfect to Skip an Ad break after a Goal has been scored. Anything that removes user configured 30 seconds Skip forward is a big no no IMHO.

[sdsnyr94]

I received the update for my Shield last night. I am still having issues with HDR playback, it's hit or miss if HDR is triggered on the TV.

First things first - Are there recommended settings anywhere for MrMC and HDR? I want to rule out any settings I may have altered in the past.

I'm using Plex integration, but I have transcoding turned off in MrMC. In Plex for the Shield or Roku TV, I see a similar issue if video is transcoding - If I force Direct Play (or change to AC3 audio track for Direct Play), HDR works consistently. Changing the audio on the fly does not seem to help trigger HDR within MrMC.

Starting an HDR movie from the beginning will trigger HDR about 50% of the time (using the same movie as a test). If I RESUME a movie (again, using same movie as a test), HDR will trigger about 10% of the time.

I'm not home to get logs at the moment... I also have not tested directly playing any of the files (removing Plex from equation).

**Quick Edit*** I have tried multiple movies with the same results, however for testing purposes I used the same one repeatedly.

[davilla]

I received the update for my Shield last night. I am still having issues with HDR playback, it's hit or miss if HDR is triggered on the TV.

First things first - Are there recommended settings anywhere for MrMC and HDR? I want to rule out any settings I may have altered in the past.

I'm using Plex integration, but I have transcoding turned off in MrMC. In Plex for the Shield or Roku TV, I see a similar issue if video is transcoding - If I force Direct Play (or change to AC3 audio track for Direct Play), HDR works consistently. Changing the audio on the fly does not seem to help trigger HDR within MrMC.

Starting an HDR movie from the beginning will trigger HDR about 50% of the time (using the same movie as a test). If I RESUME a movie (again, using same movie as a test), HDR will trigger about 10% of the time.

I'm not home to get logs at the moment... I also have not tested directly playing any of the files (removing Plex from equation).

**Quick Edit*** I have tried multiple movies with the same results, however for testing purposes I used the same one repeatedly.

On Shield, not really. Only MediaCodec(Surface) understands HDR so you must use it. The rest is up to the Shield firmware. The only thing that I can think of which might influence would be the display rate change delay. It too short, we might be messing up any timing the firmware relies on.

[sdsnyr94]

On Shield, not really. Only MediaCodec(Surface) understands HDR so you must use it. The rest is up to the Shield firmware. The only thing that I can think of which might influence would be the display rate change delay. It too short, we might be messing up any timing the firmware relies on.

I had the display rate change up as high as 6 seconds last night. I did make sure that MediaCodec (Surface) was enabled.

I'll give it a test tonight or tomorrow with Plex out of the equation... Is it possible that something is still triggering Plex to transcode? (obviously, you cannot tell without a log file... unless you can duplicate).

[Ted377]

I would like to have more information displayed by pressing the OK button.
For example, what resolution the current TV station has and whether the sound in Dolby Digital, etc. is.
This is also displayed on MrMC Skin and unfortunately not on Opacity.
I miss this feature

[jabohn]

One thing I've been noticing is that scrolling up at the top of a list which used to just seamlessly bring you to the bottom of the list, now it does nothing the first time you try after starting the app. It makes the tvOS "boop" noise but doesn't actually go anywhere. But then if you scroll down a few notches and then back up to the top and try again, it now works and brings you to the bottom of the list. Every time after that then it works, until the app has been relaunched and you have to do it again.

[davilla]

One thing I've been noticing is that scrolling up at the top of a list which used to just seamlessly bring you to the bottom of the list, now it does nothing the first time you try after starting the app. It makes the tvOS "boop" noise but doesn't actually go anywhere. But then if you scroll down a few notches and then back up to the top and try again, it now works and brings you to the bottom of the list. Every time after that then it works, until the app has been relaunched and you have to do it again.

By design, lists will not autowrap to keep short lists from zipping round and round on a fast swipe. The behavior is you can fast swipe to the top/bottom, then the next swipe will wrap around. There's a timeout of 1/2 second.

[cosmoxl]

Several ATSC broadcast recordings are causing problems still. First visible symptom is that the scrubbing thumbnail isn't generated. When this happens I still get the time stamp, so that's fixed from previous builds. But, whenever I scrub and then click to select the new time, the video just starts over. For some reason I thought this was fixed too but it seems not.

https://gist.github.com/anonymous/8269f ... 1cfa9458bc

[jabohn]

One thing I've been noticing is that scrolling up at the top of a list which used to just seamlessly bring you to the bottom of the list, now it does nothing the first time you try after starting the app. It makes the tvOS "boop" noise but doesn't actually go anywhere. But then if you scroll down a few notches and then back up to the top and try again, it now works and brings you to the bottom of the list. Every time after that then it works, until the app has been relaunched and you have to do it again.

By design, lists will not autowrap to keep short lists from zipping round and round on a fast swipe. The behavior is you can fast swipe to the top/bottom, then the next swipe will wrap around. There's a timeout of 1/2 second.

Okay. I understand that, but I guess it's different when you're tapping and not swiping. It's not consistent. The delay only seems to happen the first time I do it. Then other times no matter how long I wait it will not wrap around until I tap down first and then back up.

I'm also hearing the boop noise sometimes not play after it wraps around. It seems to happen mostly on the side menu. If I tap to the top and then it wraps to the bottom and I keep tapping up, the noise stops until I tap down.

[davilla]

One thing I've been noticing is that scrolling up at the top of a list which used to just seamlessly bring you to the bottom of the list, now it does nothing the first time you try after starting the app. It makes the tvOS "boop" noise but doesn't actually go anywhere. But then if you scroll down a few notches and then back up to the top and try again, it now works and brings you to the bottom of the list. Every time after that then it works, until the app has been relaunched and you have to do it again.

By design, lists will not autowrap to keep short lists from zipping round and round on a fast swipe. The behavior is you can fast swipe to the top/bottom, then the next swipe will wrap around. There's a timeout of 1/2 second.

Okay. I understand that, but I guess it's different when you're tapping and not swiping. It's not consistent. The delay only seems to happen the first time I do it. Then other times no matter how long I wait it will not wrap around until I tap down first and then back up.

I'm also hearing the boop noise sometimes not play after it wraps around. It seems to happen mostly on the side menu. If I tap to the top and then it wraps to the bottom and I keep tapping up, the noise stops until I tap down.

Think of taps as a discrete event. There is one and only one. Easy to handle. With swipes, it's like a rubber band of events. At the code level, we have zero info about how many events are coming. While we are creating UIViews to get focus working right, some controls like group lists use boundary UIViews to handle swipes. The tvOS focus engine will not move focus unless there is something to go to. So we intercept when a boundary UIView is hit, re-adjust focus and send the move to core. This gets very tricky to get swipe scrolling working. This same imperfect handling is why focus can jump out of a view group and bounce around. WIP as they say.