JMCC

  • Content Count

    849
  • Joined

  • Last visited

Reputation Activity

  1. Like
    JMCC got a reaction from Werner in RK3288/RK3328 Legacy Multimedia Framework   
    Package update in the repos. It reverts back the addition of station-m1 and station-p1 kernels, to the previous state, when everything worked fine. We are keeping the "Depends" relationship to the legacy kernel, since the package actually depends on the legacy kernel: it won't work with a different kernel, and even more it will break the system if installed.
  2. Like
    JMCC got a reaction from balbes150 in RK3288/RK3328 Legacy Multimedia Framework   
    Sorry, I was away. I'll try to fix it ASAP
  3. Like
    JMCC got a reaction from MX10.AC2N in VPU Encoding (Transcoding) for RK3229 with Kernel4.4 (legacy) TVHEADEND   
    I have found a bit too hard to configure HW encoding with TVHeadend. It doesn't give you the possibility of specifying custom ffmpeg commands, so your only chance is creating a pipe in each mux, which AFAIK it can only be done with IPTV muxes. I haven't even tried this.
     
    What I do is using the Jellyfin TVHeadend plugin, so I let Jellyfin do the transcoding. That also gives me easy and secure access to my TV channels from outside my home.
     
    The device I am using is a Odroid HC1. XU4 and its derivatives (HC1/HC2/MC1) has always been my recommended device for anything requiring HW accelerated encoding, since it has a standard v4l2-m2m interface supported by ffmpeg. AFAIK, there is no other ARM board offering this feature as of today. Plus, since it is an older device, it's being sold for $50, a real bargain for what it offers IMO.
     
    If there is people interested in a tutorial on how to do this setup, I think I can do one.
  4. Like
    JMCC got a reaction from Werner in RK3288/RK3328 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 RK3288/3328 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-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --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 (RK3288 only): 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 (RK3288 only): 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 Light DM 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.
  5. Like
    JMCC got a reaction from balbes150 in RK3288/RK3328 Legacy Multimedia Framework   
    Search the forums. Don't expect official documents: as we have stated several times, Rock64 is not supported by Armbian, and therefore we won't put resources into it. If you, or any other community member, wants to work on documenting the problems or fixing them, feel free to do it. I don't even own the board.
     
    And please start a different thread on the "Peer-to-Peer Support" subforum. Any further post about the Rock64 problems will be deleted from this thread.
  6. Like
    JMCC got a reaction from mar in RK3288/RK3328 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 RK3288/3328 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-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --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 (RK3288 only): 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 (RK3288 only): 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 Light DM 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.
  7. Like
    JMCC got a reaction from manuti in RK3288/RK3328 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 RK3288/3328 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-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --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 (RK3288 only): 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 (RK3288 only): 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 Light DM 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.
  8. Like
    JMCC got a reaction from guybrushthreepwood in Orange Pi PC H3 Armbian Focal 5.10.4-sunxi av tv out cvbs enable   
    I created Kodi packages for v4l2-request, tested on Orange Pi+2e (Allwinner H3) running Armbian Bullseye with the current 5.10.y kernel.
     
    So far, HW video playing works fine with MPEG2 and h.264 up to 1080p. Kernel patches are needed to improve resolution and codec support. GUI performance is just enough, but it can probably be also improved with kernel patches.
     
    So the userspace part is now working, the kernel improvements remain in the TO-DO list.
     
    Packages can be found here: https://users.armbian.com/jmcc/packages/kodi-mainline/
     
    These should still be considered WIP, although fully functional already. Instructions:
    Download the packages for your architecture, and install them with "dpkg -i". Only kodi-mainline and kodi-mainline-bin are essential, the others are optional. Run "apt -f install" Make sure there is no X server running, and start kodi from console typing "kodi" @balbes150 you may be interested in this. They should also work in Rockchip, but I haven't tested yet.
  9. Like
    JMCC got a reaction from Technicavolous in RK3288/RK3328 Legacy Multimedia Framework   
    Essentialy, yes. VPU is identical in last generation SoC's RK3328 and RK3399, lacking VP9 capabilities in the older RK3288.
     
    GPU, on the other hand, is very similar in the high-end SoC's (RK3288 and RK3399), much faster and supporting OpenGLES 3 and OpenCL 1.2. The weaker one, RK3328, supports only GLES2 and no OpenCL, plus no ISP camera either.
     
    There is also a parallel solution for Odroid XU4, I will document it soon. In that case, VPU decoding capabilities are reduced (no 4K, only 1080p). But GPU is the strongest one, as well as VPU encoding.
  10. Like
    JMCC reacted to Heisath in Armbian Sites Status Page   
    Is there also a status page for the status page? Just to make sure, we know what to do, if the status page is not available
  11. Like
    JMCC reacted to lanefu in Armbian Sites Status Page   
    We have a realtime status page for primary Armbian web resources available here:
     
    https://status.armbian.com
     
  12. Like
    JMCC got a reaction from TRS-80 in RK3288/RK3328 Legacy Multimedia Framework   
    LOL No, man, I'm not that old!
  13. Like
    JMCC got a reaction from pro777 in RK3288/RK3328 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 RK3288/3328 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-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --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 (RK3288 only): 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 (RK3288 only): 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 Light DM 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.
  14. Like
    JMCC got a reaction from Dee Cheung in RK3399 Legacy Multimedia Framework   
    Okay, NanoPC-T4 can run now dual displays, and GPU 3D acceleration works flawlessly:
    https://users.armbian.com/jmcc/misc/nanopct4-dual-screen.mp4
     
    @TheGuv It seems like a problem specific to Helios64. @aprayoga Maybe you can shed some light on the problem? This is the post where the user reported failing GPU acceleration: https://forum.armbian.com/topic/16516-rk3399-legacy-multimedia-framework/?do=findComment&comment=116900
     
    [EDIT]: And this is the fix that enabled NanoPC-T4 DP, in case it is helpful to debug the Helios64 problem: https://github.com/armbian/build/pull/2647
     
     
  15. Like
    JMCC reacted to NicoD in RK3399 Legacy Multimedia Framework   
    Seems to work fine on the M4.
     
    Linux nanopim4 4.4.213-rk3399 #6 SMP Thu Feb 18 19:25:55 CET 2021 aarch64 aarch64 aarch64 GNU/Linux  
  16. Like
    JMCC reacted to Heisath in Jira   
    You need to assign a fix version. Compare yours https://armbian.atlassian.net/browse/AR-600 with this one from Igor: https://armbian.atlassian.net/browse/AR-630
  17. Like
    JMCC got a reaction from NicoD in RK3399 Legacy Multimedia Framework   
    Definitely, according to the picture, something went wrong. Can you do the installation again from scratch, and this time copy-paste the installation output? And also "armbianmonitor -u".
  18. Like
    JMCC reacted to TheGuv in RK3399 Legacy Multimedia Framework   
    Nice! Always helpful to have a working test device
     
  19. Like
    JMCC got a reaction from balbes150 in RK3288/RK3328 Legacy Multimedia Framework   
    @balbes150 This commit takes care of the issue. I built and tested a xfce-buster image, and everything seems OK.
     
    I also added the session selector to LightDM greeter, so people can choose Kodi or any other desktop of their choice.
  20. Like
    JMCC got a reaction from balbes150 in RK3288/RK3328 Legacy Multimedia Framework   
    I used master. From what you say, it looks like we need to put some "Provides: armbian-xxx-desktop" field in the package control files, to ensure backwards compatibility. I will look into it.
  21. Like
    JMCC got a reaction from balbes150 in RK3288/RK3328 Legacy Multimedia Framework   
    Last time I tried, it was working fine, but it was two weeks ago. Let me test when I get home.
  22. Like
    JMCC reacted to dpapavas in RK3399 Legacy Multimedia Framework   
    I never said it didn't, but one still has to read up on how it works, how to get it to compile just the kernel, after applying patches, how to use that kernel and handle unbootable systems etc.;  that sort of thing.  I'm very new to Armbian.
     
     
    I meant that, since you're currently working on getting the Media Framework to work based on the mainline kernel and asssuming that this HDR issue is, at least in part, due to something missing from the kernel, whether it might be better to troubleshoot this in the mainline version of the Media Framework.  But read also below.
     
     
    I sort of managed to do the reverse: find a libreelec setting that makes HDR output not work and exhibits the same behavior I get on Armbian.  As far as I can see, librelec for rockchip devices doesn't apply any KODI patches (although there is this).  I'm not sure if that means that the plain/unmodified source is used for KODI, or whether some patches are applied regardless of board, but on librelec, KODI has an extra option that lets you select the "HDMI output format".  This essentially sets the color space to RGB or YCbCr (4:2:2 or 4:4:4 ).  The display only switches to HDR with the (default) YCbCr mode, not with RGB.
     
    The Media Framework version of KODI is missing that option.  In fact I haven't found any reference to it, outside of libreelec.  Output seems to default to RGB colorspace, as can be seen with:
     
     
    In contranst in librelec, I get something like:
     
     
    I'm not sure of course, that getting KODI to switch to a YUV HDMI output mode will be enough to make the display switch to HDR, but it seems worth trying, especially since it should be easier than semi-blindly applying kernel patches.  That said, I can't seem to find much info on how to do so.  Let me know if you have any insight to share.
  23. Like
    JMCC reacted to balbes150 in RK3399 Legacy Multimedia Framework   
    You don't need to change anything. I found a solution-changed the patches so that can now use a common core for p1. 
  24. Like
    JMCC got a reaction from Werner in Board Bring Up Station P1 rk3399, M1 rk3328   
    I would like to bring something to attention. Right now, Station P1 and M1 legacy are being added as new kernel packages. I think ideally, the changes should be merged into some of the existing RK3399/Rockchip64 legacy kernels. We were aiming to reduce the multiplicity of RK kernels, but now we are introducing two new kernel packages, station-m1 and station-p1, one of each for a single device.
     
    Of course, I understand all the work involved on bringing up a new board, and how frustrating it is when new kernel configs or patches conflict with the existing one. But it is probably worth the effort to try and merge the changes for P1/M1 into Rockchip64, if that were possible.
     
     
    @piter75 @martinayotte @balbes150 @TonyMac32 @Igor What do you think?
  25. Like
    JMCC reacted to balbes150 in Board Bring Up Station P1 rk3399, M1 rk3328   
    The DTS patch is sufficient to enable NVMe. For the rest of the elements-I'm just now preparing patches for the current Legacy kernel (rockchip64), which is used to build the version for P1 in the official GIT.