Posts by smp
-
-
-
It should be tested on a current build of Kodi 18. I can check if it works on a current Milhouse LibreELEC 9 build if you upload a sample to Google Drive, Dropbox or something like that. Or you can install the latest Milhouse build (or v8.90.009 ALPHA build) and test yourself.
-
Can you upload a small sample?
-
Use DVI to HDMI. But how do I get audio?
Did you try it? Not sure about your Foxconn NT3700 but modern videocards can output audio over DVI as long as you use DVI to HDMI cable.
-
I'm currently using kernel 4.19.7 with the "MUTEX_FLAG_HANDOFF 0x00" hack on a Raspberry Pi3 and it works well. Kernels 4.8 and 4.9 also work fine.
-
Well, it didn't pass the antenna cable "hot unplug" test that I do to accelerate the tuner failure.
-
@jahutchi I get this build error
Code
Display MoreCC [M] drivers/media/usb/dvb-usb-v2/dvbsky.o drivers/media/usb/dvb-usb-v2/dvbsky.c: In function 'dvbsky_i2c_xfer': drivers/media/usb/dvb-usb-v2/dvbsky.c:117:27: error: expected ';' before 'if' mutex_lock(&d->i2c_mutex) ^ ; drivers/media/usb/dvb-usb-v2/dvbsky.c:119:2: if (num > 2) { ~~ drivers/media/usb/dvb-usb-v2/dvbsky.c:115:15: warning: unused variable 'obuf' [-Wunused-variable] u8 ibuf[64], obuf[64]; ^~~~ drivers/media/usb/dvb-usb-v2/dvbsky.c:115:5: warning: unused variable 'ibuf' [-Wunused-variable] u8 ibuf[64], obuf[64]; ^~~~ make[5]: *** [scripts/Makefile.build:304: drivers/media/usb/dvb-usb-v2/dvbsky.o] Error 1 make[4]: *** [scripts/Makefile.build:544: drivers/media/usb/dvb-usb-v2] Error 2 make[3]: *** [scripts/Makefile.build:544: drivers/media/usb] Error 2 make[2]: *** [scripts/Makefile.build:544: drivers/media] Error 2 make[2]: *** Waiting for unfinished jobs....
-
This looks suspiciously similar to this issue.
-
I found a workaround for the mutex issue. It seem to be impossible to revert commit 9d659ae14b545c4296e812c70493bfdc999b5c1c in kernel 4.19, so here's a solution:
Diff
Display Morediff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c index 3f8a351..5878d8f 100644 --- a/kernel/locking/mutex.c +++ b/kernel/locking/mutex.c @@ -59,7 +59,7 @@ EXPORT_SYMBOL(__mutex_init); * Bit2 indicates handoff has been done and we're waiting for pickup. */ #define MUTEX_FLAG_WAITERS 0x01 -#define MUTEX_FLAG_HANDOFF 0x02 +#define MUTEX_FLAG_HANDOFF 0x00 #define MUTEX_FLAG_PICKUP 0x04 #define MUTEX_FLAGS 0x07
After applying this patch the random tuner failures are gone. Tested with DVBSky S960, kernel 4.19.7.
-
What is your gpu_mem setting?
-
Kernel 4.19.2 did not solve the problem described in the original post, I can still easily reproduce it. In 4.19.2/4.20-rc2 they reverted commit 7d95fb74 that made DVBsky devices non-functional since kernel 4.18 but that issue is completely unrelated.
-
Use WinSCP.
Copy /usr/share/kodi/addons/skin.estuary folder to /storage/.kodi/addons/
Edit the xml file (/storage/.kodi/addons/skin.estuary/xml/DialogSeekBar.xml).
Restart Kodi.
-
Is this possible?
Yes. If you are using the default Estuary skin you will need to edit addons/skin.estuary/xml/DialogSeekBar.xml file.
Code<visible>Player.Seeking | Player.DisplayAfterSeek | [Player.Paused + !Player.Caching] | Player.Forwarding | Player.Rewinding | Player.ShowInfo | Window.IsActive(videoosd) | Window.IsActive(musicosd) | Window.IsActive(playerprocessinfo) | !String.IsEmpty(Player.SeekNumeric) | !String.IsEmpty(PVR.ChannelNumberInput)</visible>
Remove Player.DisplayAfterSeek | [Player.Paused + !Player.Caching].
-
"This patch causes a bad effect on RPi. I suspect that the root cause is at the USB out of tree RPi driver, with uses high priority interrupts instead of normal ones. Anyway, as this patch is mostly a cleanup, better to revert it."
Actually, it broke it for all platforms including x86,
-
There is a buggy commit in dvbsky.c driver in kernel 4.18. It should be reverted to make DVBSky devices work again.
-
It is unwatchable here too. Kodi falls back to software decode but Rpi3 is not fast enough to decode this in software.
-
Quote
Bit depth : 10 bits
Rpi does not hardware decode 10-bit video. You can still PM me the sample file so I will test it on my Pi.