Jump to content

JMCC

Members
  • Posts

    941
  • Joined

  • Last visited

Everything posted by JMCC

  1. Well, it is a well known problem, that audio in Linux sucks in general, not only Armbian. There are equalizer apps for Pulse audio, but you need to tweak it manually (there was a good one in Python 2 with excellent presets, but it probably won't work in modern distros). The good news is that, according to your findings, LE has already done the work of getting a good equalizer preset for your device. You only need to copy the Pulseaudio config from LE to your Armbian installation. And if you also want to make a PR, it is very welcome
  2. Kodi will use the system Pulseaudio config. You can use Pulseaudio Volume Control on the desktop session, and the settings will stick for Kodi.
  3. Decoding is done in software, but the video is displayed in a HW accelerated EGL layer. Otherwise it would not be possible to have vsync and smooth 1080p@60 AFAIK Chromium has no HW decoding support in Linux. There was some work going on for using v4l2, I am not sure if it made it into the release already
  4. We've gotten quite far, after plenty of work. You can check it by yourself by installing the multimedia framework as described in the first post Of course, LibreELEC is a multimedia-player-specific distro, and will always be the reference implementation on this field. But our multimedia framework is more than just video playing (which still does quite well, using several patches from LibreELEC and many from our own). Apart from that, it also includes HW encoding, ISP camera, OpenCL, 3D desktop acceleration, etc. Our intention is not to compete with LibreELEC, but to offer a more versatile option that maintains all the possibilities of a full-featured Linux desktop. We cannot help you if you don't provide more information, like "armbianmonitor -u" and kodi logs.
  5. The issue has been discussed and solved in a recent post for OPi PC, it should also work for Zero
  6. You failed to provide the necessary information that we need to help you.
  7. Moved to peer to peer support, since it is an unsupported board
  8. 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.
  9. If you are referring to the info that's necessary for us to help you, as @Werner stated above, you've got it in the forum rules and in the warning you receive when you are going to post. You need to provide that if you want any help from our side. My suggestion assumed that it was you who wanted to try the fix by yourself.
  10. It seems like images have not finished uploading yet, some of the links are broken. Just wait a few hours...
  11. My first suggestion is to isolate the patch that makes the changes you need. Right now, your link simply points to a list of zip files with whole kernel sources. Once you have the patch you need, applying it with the Armbian Build System is a piece of cake.
  12. You've got other RK3399 alternatives supported by Armbian, like NanopiM4, NanoPCT4, or Station P1
  13. Sorry, I was away. I'll try to fix it ASAP
  14. 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.
  15. I just tested it and it works for me as expected. Maybe some problem with the mirror sync?
  16. RK BSP kernel uses a special camera interface (RK-ISP1). The best way to make it work, in my experience, is with the RK GStreamer plugin. In the MM Framework documentation (1st post) you have a link to the TInkerBoard wiki, where they explain how to use it. The plugin is ready to go when you install the MM Framework. The media-buster-legacy-rk3399 package will install desktop. You have two options: 1. Disable desktop with "systemctl disable lightdm" 2. Install only the required packages manually without installing the media-buster-legacy-rk3399 metapackage, and probably do some manual config changes. Option 1. seems easier to me. Probably so, but I don't own the hardware, nor have developed for it. I am not sure if the necessary kernel configs and DT nodes are present in the kernel. If they are not, you can add them and make a PR.
  17. You need to use the legacy kernel for the camera to work, not current. And you also need to install the multimedia framework: Remember, you need an Armbian Buster Legacy Desktop image, and install the framework as described in the post. For last, you need to enable the camera using a overlay: $ sudo armbian-config Then select System > Hardware > rpi-cam-imx219 Please post the results of your tests. I have been looking for someone to test the imx219 for a while (I only have a ov5647)
  18. Sounds weird. And even more weird, the link to the armbianmonitor output is broken Can you post another one? That will increase the chances to figure out the problem. Also if you are using legacy kernel, try with current, or vice versa.
  19. Yes, that was my guess. That will require a kernel fix. No, it's the golden connector on the top right corner, next to the GPIO pins
  20. Try different ethernet cables. Or your network interface may be broken. Or many other things. The best option would be to use a UART to USB adapter, log into the machine and see what is happening.
  21. Can you test with a different monitor and/or source files? Try to downgrade. For example, if you are using a 4k monitor, try a 1080p one. Or if you are using HDR 10-bit, try 8-bit color.
  22. Okay. Since I saw the hostname is "hirsute", I thought you were using Hirsute instead of Buster. That is the reason why we ask for armbianmonitor -u Please post the console output of mpv and gst-play-1.0 (you may need to install gstreamer1.0-plugins-base-apps)
  23. Please re-read the first post carefully, I think you may find the answer there. Also, in order to get help, you need to provide some information, as indicated in the forum rules. Please provide that information if you still need help.
  24. 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.
  25. What you are trying to do is best achieved through DT overlays. Check the Armbian documentation about "DT Overlays", and also see if there is already an overlay that does what you want. BTW, before asking for further help, make sure you provide the necessary information, according to forum rules, like the output of "sudo armbianmonitor -u"
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines