Jump to content

alsc

Members
  • Posts

    15
  • Joined

  • Last visited

Reputation Activity

  1. Like
    alsc reacted to JMCC in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    Arre you talking about the tweaked kernel I linked above? That was just for testing. Now, the relevant changes are merged into the build script. So, if you are still using the testing version, just install a recently built kernel: either build your own debs with the build script, download it from beta, or wait for the next stable release.
     
    The errors you show are not critical, it seems like probably EXT4 debug was enabled on that kernel. If after switching to the official kernel the problem persists, we'll look into it.
  2. Like
    alsc reacted to NicoD in RK3399 Legacy Multimedia Framework   
    I finished the video about the media script. 
    I had a lot of troubles with youtube because I used a few seconds of southpark and I got age restriction 18 years. Youtube doesn't like Southpark clearly. 
    Tried 3 times with different clips. In the end I cut it all out.. Thanks @JMCC for the awsome work. Without your scripts I wouldn't think of using an SBC as main desktop. 
     
  3. Like
    alsc reacted to JMCC in RK3399 Legacy Multimedia Framework   
    New packages uploaded to the repos (it may take some hours to synchronize).
    Bug fixes: X Desktop no longer restarted on package install, so it can be installed from a desktop session (NOTE: Since the old package is still going to restart X when uninstalled, it is recommended to do this update from console). MPV now is not failing when it cannot create EGL surface (it will just default to standard x11). CEC is now working on several boards (tested in RockPro64 and Rockpi 4B). New features: MPV is now RKMPP accelerated, and allows 4K YouTube Playback (see instructions here).
  4. Like
    alsc reacted to JMCC in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    That was the intention, and the purpose of all the testing we did 
  5. Like
    alsc reacted to JMCC in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    Good! We cleared out the libcec part.
     
    Now, let us try some kernel tweaks. Install these kernel+dtb packages, reboot and try kodi again: https://users.armbian.com/jmcc/packages/kernel-rk64/
  6. Like
    alsc reacted to TRS-80 in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    Beside your current problem, they are super cool, anyway!  I mean, if you are into SBC, maybe you are (or will get) into these, too.  Many of us are doing Home Automation stuff, as well, with our SBCs! 
     
    There is a whole world of different radios you can use, but for this the Wi-Fi based ones (searching Tasmota will get you started, but there are others, too) will probably fit your need best.
     
    Wi-Fi switches (Tasmota especially) are even quite easy to get working these days, there is a pretty big community around them, etc.
     
  7. Like
    alsc got a reaction from TRS-80 in RK3399 Legacy Multimedia Framework   
    Thank you very much for your work. I've been following your other thread once your tool's been one of the only ways I found to use Kodi on a RockPro64 in a server, without have to necessarily use LibreELEC.
     
    I really appreciate what you've been doing!
  8. Like
    alsc reacted to JMCC in RK3399 Legacy Multimedia Framework   
    IT'S FINALLY HERE...

    THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION
     
    After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).
     
    I. Installation
    Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".
     
    II. Features
    Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K).
            - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV.
    ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: 


    Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed.  
    III. Sources
    This is the list of the sources used for the packages:
     
    IV. FAQ
    ¿Why did you use Debian Buster as a base for this implementation?
    It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal.
      ¿Why Legacy instead of Mainline?
    This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels.
      ¿Will you add new features to this implementation?
    No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines