• Content Count

  • Joined

  • Last visited

About JMCC

  • Rank
    Embedded member

Recent Profile Visitors

1927 profile views
  1. @tumbleweed2019 did you try the included "glrun" wrapper, as described in the documentation?
  2. Un the page you linked, there is a download of a Debian Stretch image. It looks like the official Rockchip Linaro image. I haven't tested that particular board because I don't have it, but at least you know that you have a working image to start from. Since Armbian supports already other Rockchip SoC's, there are good chances that you can make Armbian work in the board, if you know what you are doing, with a config based on some of the supported RK boards. But I cannot guarantee how hard it will be.
  3. I'm glad it worked. About the updates, use whichever version works best for you. This is all experimental stuff, the big companies like Google or Amazon will not bother to test and support their products in these platforms, with such a small user base. So, if you find a version of Chromium that works for you, while some other doesn't, then you can stick to that one. Or you can also try and reinstall the media packages after the upgrade, and see if that works.
  4. Just install the updated widevine, that you can find a few posts above. This is the download link
  5. IIRC, the camera is working just fine in recent versions of TinkerOS. That means they fixed it somehow in the ASUS kernel, and probably upstreamed the patch. It may be worth giving it another try, I'll put it in my to-do list.
  6. Hello. Sorry, I've been out for a while. Have you tried to play the videos with the Gstreamer GUI player? (the launcher labeled as "Rockchip Gst Player") And with MPV-GBM? Please try, and see if you experience the same video delay.
  7. Then everything is fine. 32 bit (streaming version) is not working well, it is just an experiment. That's why it is disabled by default.
  8. Just try with the default options: click "Accept", "Yes" or "OK" every time, and let it run.
  9. It should work on a fresh Default image (4.4 kernel), just with default options selected. I haven't tested it in a while, let's see if I can find some time and check whether recent updates broke the script.
  10. Correct me if I'm wrong, but I understand that the new V4L2 driver only supports HW decoding, not encoding, right? In that case, IMO the usefulness of an standalone FFmpeg is very limited. What I mean is that you won't get a noticeable benefit in transcoding with FFmpeg if you only accelerate the decoding. Not to mention possible colorspace conversion limitations etc (I think I bumped into some of those with the "old" RKMPP FFmpeg implementation). On the other hand, I see the real usefulness of that when FFmpeg is used as part of media players such as MPV or Kodi. And, in those cases, I always found it easier and more efficient to compile its own version of FFmpeg with the app, than link it against the system libs. So my opinion is that it is better to leave alone the system FFmpeg debs, and compile the new version on a separate directory; that way it will not break other FFmpeg-dependent apps, such as video editors etc.. And let the media players use their own FFmpeg (after all that is what they normally recommend in their compilation instructions), and apply the patch there when necessary.
  11. The following deb package should work for Armbian Bionic arm64 (RK3328/RK3399):!Aj0xDhqxX_nqoygqTuH8eoKnP3in
  12. In that case, mpv builds with V4L2 support by default. Just run on the TinkerBoard: $ sudo apt remove mpv $ git clone $ cd mpv-build $ ./rebuild -j4 $ sudo ./install This will install mpv in your local machine. If you also want to build a debian package, you can do the following additional steps: $ sudo apt-get install devscripts equivs fakeroot $ mk-build-deps -s sudo -i $ dpkg-buildpackage -uc -us -b -rfakeroot -j4 The resulting mpv package can later be installed on any machine running the same distro and architecture. In order to run mpv using the v4l2 support, this is the command line that I use: mpv -hwdec <filename>
  13. Does it need to have also RKMPP support, or just V4L2 is enough for the new driver?
  14. BTW, seems like the Lima driver has been accepted for 5.2. Looking forward to seeing it released
  15. But, just for the records, provided that you have root access, you can hard reboot a board running Armbian by issuing echo b > /proc/sysrq-trigger