---OPi-One Owners: Please test and provide feedback.d
Jernej, Please replace the OPi-One fex file with the attached one. I also updated the script.bin files for 720p/1080p/2160p resolutions for all 4 boards at the below location.
You are right about the irrecord thing. The new method works eventhough in my case I have to use the -f option which created the conf file with raw codes. Other than that all good and as expected.
I'll upload the updated builds for other boards tomorrow.
This thread contains more resources
You need to Log in to download or view，No account?
Register
Ok, the Hauppauge HVR900 is recognized perfectly. Still have to find the cheap chinese DVB stick. Dodn't remember where I put it.
BTW: love the new IR driver (I haven't updated since beginning of January), it's so awesome!
Hmmm, the Hauppauge HVR900 is recognized (as em28xx), but the cheap one isn't. It's just shown in lsusb:
Bus 003 Device 003: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
But no actual further recognition like with the em28xx
Probably not supported by kernel.
As for the em28xx: it's recognized by the kernel (based on dmesg), but it doesn't show up in tvheadend. So that's unfortunate. I've tried everything what I could find, but no luck.
Interesting. I actually like the raw like now: I can now use ANY remote control, while on NEC I could only use a few. I highly doubt if these 2 commits would fix detection on NEC.
Dima replied at 2016-2-16 16:58
Hmmm, the Hauppauge HVR900 is recognized (as em28xx), but the cheap one isn't. It's just shown in ls ...
If you want to play, you can revert commit 292b76c18c59b597ac213aa68528dbe10b1fc8cd and try to build media_build package. You will need few kernel patches, but in the end, you should have latest dvb drivers. Technically, patches should not be needed, but some investigation must be performed to determine if it's script fault or some kernel patch is missing something.
Dima replied at 2016-2-16 23:58
Hmmm, the Hauppauge HVR900 is recognized (as em28xx), but the cheap one isn't. It's just shown in ls ...
With em28xx having default support is almost impossible. Eventhough the chipset is good and cheap at the time of it's release there are a 100-200 variations in the implementations which is impossible to detect from the driver unless you customize the driver yourselves. Most models present a generic uid-pid. In windows it is not a problem as with each device they ship the driver and you use that driver.
In your case the it's just the kernel detecting a em28xx device but the driver cannot complete the initialisation as a valid match is not found and so a device node is not created and so obviously tvheadend won't detect anything.
I used to struggle with couple of those devices, gadmei utv310,utv380 etc during 2007-2009 and each time I have to play around with v4l driver code making wildcard guesses and make it work. You still can find some reminiscences from that era at the below link.
I used to work with Markus Rechberger at that time and first Markus lost interest and then finally I stopped playing with those when analog tv and started disappearing in most countries.
The latest images has some issue with 4K display support. Tested screen modes 0x1c/0x1d/0x1e and I can see Openelec banner and after that TV displays "Invalid format". Did the screen mode definitions change with the patch re-organization. I didn't get time to test further and to look at the code.
With 1080p the refresh rate switching works flawlessly.
[Copy link]
Show IP Card
Radar Card
Published in 2016-2-16 19:33:11
Anonimous Post
Published in 2016-2-17 03:45:11