Kernel is actually the same for ng-builds.
Yes. What i really like about Matrix (above average PVR user here) is
- integrated functions that required add-ons
- PVR gui changes
- PVR excellent integration of archive-iptv
- Better handling of multiple PVR clients
- Python3 / repo cleanup
- Better addon management and security
I have only one sacrifice which I still miss (the addon āsleepā which mimics the everyday, old-school sleep timer button that were found on older TVās perfectly).
I guess that it could work out differently if you use many pyhton2 add-ons that are not (yet) updated.
Sorry if this was already answered but couldnāt find a clear explanation.
I have a K1 Pro working fine with 9.2.6 from internal for years, mostly for DVB-S, but would like to try 19.
Is it possible, maybe by installing it on a USB pen? Will DVB-S still work (with tvheadend)?
If so, will it be possible to install to internal later on? And what distribution is needed (generic, -ng, whatever)?
Thanks
You can try. At least usb or sd card should not affect your internal installation. Internal DVB is very complicated because our main developer went MIA.
Thanks for your fast reply 
And what version should I try, Matrix or Matrix-Generic ?
Do you already use ng builds with 9.2? You need Generic with a matching dtb.
I am seeing issues with 25hz content being played at 60hz by Kodi 19. I knwo several commits when past towards the end of the Kodi 19 cycle to do with refresh rate choosingā¦I think there is an issue but not sure if it is CE or Kodi itself as such.
I need to be more testing but is anyone else seeing this?
As I understand it, 25hz material should play at 25, or at 50 (Iād have thought 50 normally?).
I donāt use a whitelist, and my Panasonic OLED definitely has 24,25,50 and 60 all available as refresh rates, and these are listed in disp_cap (which I am not actually using, just looking at).
480i60hz
576i50hz
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
2160p30hz
2160p25hz
2160p24hz
smpte24hz
smpte25hz
smpte30hz
smpte50hz
smpte60hz
2160p50hz
2160p60hz*
This can be seen happening in the logsā¦
2021-03-02 18:41:46.644 T:5201 INFO <general>: Loading skin file: VideoFullScreen.xml, load type: KEEP_IN_MEMORY
2021-03-02 18:41:46.644 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:23907 dts:6.400 pts:6.480 dur:40.000ms, clock:-0.206 level:74
2021-03-02 18:41:46.644 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:11928 dts:6.440 pts:6.440 dur:40.000ms, clock:-0.206 level:75
2021-03-02 18:41:46.646 T:5367 DEBUG <general>: CVideoPlayerVideo::OutputPicture - ttd:411ms pts:0.200 Clock:-0.212 Level:4
2021-03-02 18:41:46.646 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:13185 dts:6.480 pts:6.520 dur:40.000ms, clock:-0.205 level:75
2021-03-02 18:41:46.647 T:5367 DEBUG <general>: CVideoPlayerVideo::OutputPicture - ttd:451ms pts:0.240 Clock:-0.212 Level:5
2021-03-02 18:41:46.649 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:57692 dts:6.520 pts:6.720 dur:40.000ms, clock:-0.202 level:75
2021-03-02 18:41:46.649 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:22980 dts:6.560 pts:6.640 dur:40.000ms, clock:-0.202 level:76
2021-03-02 18:41:46.650 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:12600 dts:6.600 pts:6.600 dur:40.000ms, clock:-0.201 level:76
2021-03-02 18:41:46.650 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:11054 dts:6.640 pts:6.680 dur:40.000ms, clock:-0.201 level:77
2021-03-02 18:41:46.654 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:52326 dts:6.680 pts:6.880 dur:40.000ms, clock:-0.197 level:77
2021-03-02 18:41:46.654 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:19429 dts:6.720 pts:6.800 dur:40.000ms, clock:-0.197 level:77
2021-03-02 18:41:46.655 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:8905 dts:6.760 pts:6.760 dur:40.000ms, clock:-0.196 level:78
2021-03-02 18:41:46.655 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:8718 dts:6.800 pts:6.840 dur:40.000ms, clock:-0.196 level:78
2021-03-02 18:41:46.657 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:51209 dts:6.840 pts:7.040 dur:40.000ms, clock:-0.194 level:79
2021-03-02 18:41:46.658 T:5201 INFO <general>: [WHITELIST] Searching the whitelist for: width: 1280, height: 720, fps: 25.000, 3D: false
2021-03-02 18:41:46.658 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:17300 dts:6.880 pts:6.960 dur:40.000ms, clock:-0.193 level:79
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] Using the default whitelist because the user whitelist is empty
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] Searching for an exact resolution with an exact refresh rate
2021-03-02 18:41:46.658 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:7334 dts:6.920 pts:6.920 dur:40.000ms, clock:-0.193 level:80
2021-03-02 18:41:46.658 T:5364 DEBUG <general>: CVideoPlayer::ProcessVideoData size:7830 dts:6.960 pts:7.000 dur:40.000ms, clock:-0.193 level:80
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] No match for an exact resolution with an exact refresh rate
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] Searching for a desktop resolution with an exact refresh rate
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] No match for a desktop resolution with an exact refresh rate
2021-03-02 18:41:46.658 T:5201 DEBUG <general>: [WHITELIST] No resolution matched
2021-03-02 18:41:46.658 T:5201 INFO <general>: Display resolution ADJUST : 1920x1080 @ 60.00 - Full Screen (16) (weight: 0.000)
2021-03-02 18:41:46.659 T:5312 DEBUG <general>: OnAVChange: CApplication::OnAVChange
Anybody else experiencing this?
Yes I just wanted to get an idea if other folks were seeing it.
I need to test a few more files to rule out an issue with this file (I am pretty sure I have the issue on other files too but it only bugged me enough to dig into it last night).
Once I confirm itās a more general problem by more testing (and hopefully seeing others chime in (or not) here) - Iāll for sure post a full log.
You could start with ce-debug command outputā¦ May be answer will be fast.
I am seeing an issue with resolutions and refresh rates that are normally present not being detected properly and then not available to select in Display Settings. Once the fault occurs Kodi defaults to 1080p @ 59.94Hz. Refresh rate switching then does work. A reboot seems to clear the fault although I am not sure what triggers it. I am using a Samsung KS8000 4k TV.
Interesting. Initially I had an issue like that - I had a left over line in config.ini setting 1008p60Hz as the HDMI mode (from previously trying to solve an issue with black flickering with 4:4:4 signals).
With that in, I realised I was only seeing 60hz modes available (so playback at 60hz, and in the list of available resolutions in the Kodi GUI). Even the disp_cap was only showing 60hz options at that ppint.
I took that out and rebooted and then all was well again, with all those rates above visible by catting disp_cap and in the Kodi GUI.
One thing I didnāt do was check, when seeing this particular issue, that (for whatever reason) these refresh rates were still available in the Kodi GUI.
Like I said, more testing needed. And yep, a full logā¦
I am experiencing something similar. When I start my TV after my Y8 max, Settings, System, Display shows Resolution of 1280x720 and 60 Hz refresh rate. Instead 1920x1080/50Hz which is the usual setting. When this happens, sometimes 25 fps content is played with 60 Hz instead of 50 or content with 29,97 fps is played with 24 Hz. So it jitters.
If I correct Settings, System, Display to the usual 1080p50, frame rate switches to the correct value.
It took me a while to notice this. So I usually power on my tv first, then my box and everything is fine.
I use a Harmony remote, it starts TV, then amp, then Kodi box, in that orderā¦and has done for 15+ years or so (with a variety of TVs and amps along the way of course).
I will test more and experiment with actually saving a disp_cap in userdata which I believe is the fix for these sorts of thingsā¦giving the Kodi box (Odroid N2) - an explicit list of modes so it should therefore always pick that up I guess.
No, I use the regular 9.2. Where can I find that matching dtb? is it in my box?
Yes, this is correct. And it will solve the issue for most other users to.
The CE device does read the EDID form the TV and some TV do not provide it when turned off. So the CE device does set an default resolution as it does not have the TV EDID information.
So the rule is that the TV needs to be on before the CE device get booted!
I believe cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /storage/.kodi/userdata/disp_cap would deserve some GUI element for it in skin or something. Its just a MUST to everyone with box running 24/7, not only for those with AVR without offline passthrough.
I remember disp_cap was like a big relief, when I searching replacement for Rpiās exported EDID. Every basic restart (for update, or just some regular stuff like electric outtage) is really pain without stored EDID information for 24/7 boxes.
3 Likes
Is anyone running a setup with NFS connected video sources? It worked before but became unusable at least for me because of heavy stuttering.
1 Like
I have multiple NFS sources from multiple machines attached to my N2. I upgraded to the new stable 19 the other day. Iāve only watched some old SD resolution shows Iāve been binging. I havenāt noticed any issues. Iāll try some bigger heavier 4K type stuff tonight to test it out.
1 Like