olivluca

Members
  • Content Count

    118
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by olivluca

  1. It seems that @balbes150 's image works on the meecool ki pro
  2. I never thought you were in bad faith. Pity that my orange pi pc is in active use as my doorbell otherwise I could test it (though by reading the thread it seems there's still a lot of work to be done).
  3. I doubt it, probably it has the same tuner and it has worse specs (ddr3 vs ddr4 in the mecool, 100mb ethernet vs 1Gb), see https://www.cnx-software.com/2017/11/14/magicsee-c300-is-a-70-dvb-t2c-dvb-s2-android-set-top-box-powered-by-amlogic-s905d-soc/ Edit: no, it's not the same tuner but it seems there's no linux driver for it: https://discourse.coreelec.org/t/any-support-for-magicsee-c300-pro/837
  4. The slight problem with the meecool is that it's just one tuner, not two, i.e. it cannot tune at the same time a dvb-t and a dvb-s mux/transponder. Also it seems it cannot deliver the whole TS but it has to use hw pid filtering
  5. I think I found the perfect tv box, the MEECOOL KI Pro: it has integrated dvb-t2 and s2, supported by libreelec (and hopefully by armbian with a little work), WDYT? The only problem is that coming from China I could incur some customs' fees (14€ VAT plus 20€ managing fee), but even100€ would be a good price (considering it has dvb-t2 and s2 integrated).
  6. Please, don't transform this into an opinion war, I value contributions by both of you. It seems that both alternatives (a tv box with the s905x or an rpi3) are possible and working now, other options (h3, rk, etc.) are not so well developed, am I right?
  7. Did anybody try wireguard instead of openvpn? I theory it should be faster, in practice I don't know.
  8. Yes, but I have one already (a lacie network space 2 with debian) that I use as my home server. In fact I installed in it tvheadend with a dvb-t stick as a pvr server for the rpi zero running kodi. Maybe I could use it this way permanently and just use a tv box with android and kodi. Or perhaps replace my current nas with another sbc with linux (in that case I wouldn't need hw acceleration). I saw that topic, for the time being nobody is using a tv box for reproducing media but only as a server.... Can be enabled or is it actually enabled? Anyway, I'm not in a hurry.
  9. The GPIO is not a strict requirement (I have an arduino programmed to move the dish collecting dust in a drawer). The MXQ box seems interesting: with 4 usb I could use one for armbian, one to connect to the above mentioned arduino and the remaining two for dvb-t and dvb-s. The network is only 100Mbps but I don't think it's a problem. Do your armbian images for the S905X support media acceleration?
  10. My current tv is 1920x1080, I don't plan to change it until it breaks (but I doubt it will last many years, it's 8 years old already). I'm going to watch whatever content I can throw at it, mostly 720p/1080p. I also want to use it as a dvb receiver (dvb-t and dvb-s) as well as a motor controller to steer the dish (I'm currently using this but I can write a different custom solution to use the GPIOs or an arduino connected via serial). That's the reason I prefer a full-fledged linux system instead of libreelec, since I'll have to patch tvheadend/vdr as well as writing my custom software. The RPI3B can boot over the network and use nfs for storage, so no need for an expensive sd card. I'm currently using a pi zero w with a cheap card and it's working fine, but, as I said, it isn't suitable for the kodi addons I'm using. I ordered an usb otg cable to see how it performs with a dvb stick connected to it (currently I have the tvheadend server on another box, a lacie nas where I installed debian instead of the stock firmware and I've been using as a personal server for several years).
  11. I looked at the potato specifications and it says that it's supported upstream, open source, yadda, yadda, yadda, but then the linux image doesn't support hw acceleration, while libreelec (isn't that based on linux too?) does. Either something's fishy or it doesn't make sense.
  12. Here's a thread about kodi on the H3 It doesn't seem to work very well
  13. I really appreciate all the feedback but I'm getting confused (actually I was confused even before ) It seems that it's difficult to get the right tv box (if you want to use it with linux instead of android). If the best choice is H3 based, wouldn't, say, an orange pi pc perform equally well (and I can use the GPIOs that I wouldn't have with a tv box)? From what I read here it doesn't seem to be the best for video rendering, but maybe I just missed the relevant threads. I could also get a tv box, use the supplied android and install tvheadend/vdr on a different sbc, but I'd like to have just one box instead of two. After all it doesn't seem that the RPI3+ is such a bad option. Mmmh, decisions, decisions....
  14. Then which tv box can run linux (preferably mainline), has hardware decoding (under linux), has at least two usb slots and costs the same as a RPi3+usb stick+power supply[*], i.e. less than 50€? [*] I don't care about the remote: it can work with hdmi-cec and kore
  15. And other similar addons that get content from the web (wink wink nudge nudge )? AFAIK dvb channels are either mpeg-2 or h264, maybe the upcoming 4k channels are in h265, I don't know.
  16. Thank you @Igor_K If I may abuse your patience, how does the RPI3 performs with addons like Genesis Reborn? Regarding libreelec, yes, that may be the best option wrt resource usage, but it may be more difficult to customize: mind me, I never used it (I will with the x86_64 flavour), but I read the documentation and having to install tvheadend (or vdr if it is available) from the kodi menu is not my cup of tea. Besides, I'll probably have to add some piece of custom software to control a dish positioner with the GPIOs (though I've not been watching satellite tv for a long time). Should I worry about the h265 situation or is it a non-issue?
  17. Thank you, actually I don't know which hardware would be more suitable, so I was asking for advice. The rk3288 seems interesting, though the tinkerboard is too expensive (compared to a rpi 3) and the miqi page is currently under maintenance. Edit: btw, I don't want to just run kodi but also vdr/tvheadend with a couple of dvb-usb adapters.
  18. Hello, currently I have a rasperry pi zero w with raspbian and I installed kodi on it. Playback is fine (hardware acceleration is supported), the menus are responsive but most addons are sluggish (to say the least). I saw various threads about kodi on armbian (e.g. this and this) and all say that the problem is lack of support of hw acceleration. I assume the more powerful cpu would help with the addons but, unless something has changed, without hw acceleration it makes no sense to even try. Is the situation the same now or has it improved? Maybe I should just get a raspberry pi 3b+? (it should be far more powerful than the pi zero, right?).
  19. Did you try to put an external pull down resistor on the transistor base?
  20. Well, I didn't implement it, I just took what was already available. Maybe what doesn't work for me works for somebody else or vice-versa, I don't know. In theory the version supplied with armbian should be better (it should auto select the parameters at device opening time instead of determining them at module load time), in practice it doesn't work.
  21. In case it is useful for somebody else, I put the source and the module here: https://drive.google.com/open?id=1KM3AFoSJCpJ0RpafeKRmH8iZWr3waQlH There you'll find the binary module (I compiled for my current kernel which is 3.4.113-sun8i #68) and the tar.gz with the source I used to compile it. It's just the files from github (in the "device" directory), I added a Makefile and the files from the drivers/media/video/sunxi-vfe in the original kernel source (taken from the linux-source-default-sun8i_5.60_all.deb package...well, actually I don't remember where I took those files, but I have compared them to the one provided in the deb and they are the same). To compile it just cd to the device directory and issue a make (provided you have the linux-headers package installed for the current kernel, but IIRC that's installed by default in armbian). I don't understand why armbian supplies a worse implementation of the gc2035 module but since I can use the good (or at least not so bad) one I don't care.
  22. For me the version on github works better than the version included with armbian:
  23. To compile it as an out of tree module I had to borrow some files from the full kernel source (I don't remember the details though, it's been a while). However if by latest armbian you mean the one based on the 4.x kernel, I don't think it has the required csi driver.
  24. I use sunxi-pio (with the legacy kernel), from the sunxi-tools package #!/bin/bash #PA20, input, pull-up sunxi-pio -m 'PA20<0><1><0><0>'
  25. It's been discussed before: mainline kernel has no support for the CSI interface that the camera uses. If you want to use the camera you have to use legacy kernel.