Bisecting the kernel will be a lot easier on x86 where the upstream kernel can be used untouched.
Bisecting kernel on Pi across the 4.8/4.9 boundary would need serious git skills due to the downstream patches changing.
Posts by popcornmix
-
-
I wonder if this issue is related:
Basically USB packets were getting dropped on 4.9 kernel and not on 4.4 kernel.
Interesting this bug has just been fixed upstream (this commit).
There was an overflow error in setting timer callbacks which may result in incoming packets not being serviced.
smp I wonder if you could try a recent 4.9 kernel that includes that commit.
-
Are you able to test a Milhouse nightly build?
That has a change to 3d subs that may help. Would be useful to know.
-
I don't believe so. If gui is duplicated for 3D then so will subs.
-
If i disable all 3D Funtions within Kodi the Subtitles are displayed like they should but this sucks very hard because of 2 issues.
That doesn't sound right. Have you produced subtitles with two copies of each subtitle (e.g. duplicated SBS or TAB).
You don't want to do that. When playing a 3D video kodi will automatically duplicate the subtitles in the correct manner
(may be Frame packed, SBS or TAB).
-
Always try to avoid using the calibration in Kodi.
Ideally when playing 1080p video on a 1080p display the pixels will be unscaled.
Using calibration will resize the video on the way out and then the TV will resize it back again resulting in a lower quality image.
Just disable overscan on your TV/monitor and calibration shouldn't be required resulting in a better quality image and no switching issues.
Check the menu options on TV (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1").
-
metaron - any further news on tracking down the kernel commit responsible?
-
If those MKV files contain 10bit versions of the H264 format, your Raspberry Pi is not equipped to handle those.
I believe @leposcaille reported the same file played from USB so it won't be that.
If a file plays from USB and not from network then it is most likely file permissions of the server that contains the files.
Information on the protocol used (e.g. smb/nfs) and what the OS the server is running would be useful.
As would the log file.
-
sdcard has a big effect on gui performance. You want high random access 4K read/writes.
Samsung EVO/EVO+ are good choices.
-
You can always switch to 720p in system/video settings.
That will prove if the issue is purely resolution dependent, or if something else in the update has caused it.
-
Do you have "adjust refresh rate to match video" enabled in system/video settings?
That is recommended for smoothest video.
-
I notice you are using omxplayer. That isn't the default (or recommended) on PI2/Pi3.
Do you have the problem with omxplayer disabled (leaving MMAL enabled)?
-
I see you have omxplayer enabled, which isn't the default (or recommended) on Pi2/Pi3.
Do you still have the issue if you disable this?
-
You can customise the filename tags used for 3d: Advancedsettings.xml#video
See:
Code<stereoscopicregex3d>[-. _]3d[-. _]</stereoscopicregex3d> <stereoscopicregexsbs>[-. _]h?sbs[-. _]</stereoscopicregexsbs> <stereoscopicregextab>[-. _]h?tab[-. _]</stereoscopicregextab> -
Is there a log somewhere I might be able to resurrect? (git bisect log obviously only shows the most recent bisect)
I think only the current git bisect log is saved.
-
You can run "git bisect log" to see what commits you reported as good/bad.
You might want to double check if you reported bad to 54a2ec67f1db62a763f57b7f8f2e82874f5f358b or an older commit.
-
54a2ec67f1db62a763f57b7f8f2e82874f5f358b is not going to be the commit that caused the problem (it only affects the
SOC_OMAP5 platform which isn't the Pi or PC).
If you ever report the wrong answer to git bisect good/bad then it will identify the wrong commit.
The occasional quick compiles are expected. Especially after a few iterations the number of commits jumped will be small and if these don't affect header files the amount of rebuilding may be small.
-
How are you naming the file?
You should add tags like: 3D#Video_filenames_flags
