JMCC

Members
  • Content Count

    592
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by JMCC

  1. When you are editing, you will see below the editor window a section with a paper-clip icon and the text "Drag files here to attach, or choose files..."
  2. 1) It has low latency, so I can use my laptop screen as an improvised monitor to test SBC's, for example. Useful when you don't have the space for setting up a proper "workbench". 2) Recording tutorials 3) Recording boot sequences, console output, etc. The good thing is that, in that store I linked, you get free shipping from within the EU and USA, with shorter delivery times.
  3. Heads up. Here is this HDMI to USB 2.0 capture card, 1080p@30. Very useful for posting captures, or using your laptop as an improvised HDMI monitor. It can be get for $5, shipping form the EU, USA and Russia. Here is the link: https://aliexpress.com/item/4001019746564.html?spm=a2g0s.9042311.0.0.613263c0C55RA2 It got very good reviews (unless the device looks identical on the outside but has different internals):
  4. Please post the output of the following commands: $ uname -r $ ls -l /dev/mali* $ ls -l /dev/rk* $ ls -l /dev/vpu*
  5. Maybe some update overwrote the config. Have you tried re-running the script?
  6. When you launch it from any terminal, the terminal you used must be active for the keyboard shortcuts to work. So, for example, if you launch it from an emulated terminal in a X11 session, keybuard shortcuts will work, unless you for example hit Alt+Tab, and therefore change the focus to another window. In that case, you would need to use Alt+Tab again, to bring the focus back to the terminal you used to launch mpv. So, if you want to use a desktop launcher to open video files with GBM mpv, then you must set that desktop launcher to open a virtual terminal for the process. Otherwise, you will have no way to control the player. That is the reason why in my media script mpv-gbm uses a different launcher. You can have a look at the launcher, by uncompressing the mpv-rockchip deb package.
  7. Try entering this command as root: iptables -t nat -A PREROUTING -i wlan0 -p tcp --destination-port 80 -j REDIRECT --to-port 3000 Replace "wlan0" with the name of your wireless interface. If the command works for your purpose, you can put it inside "/etc/rc.local" to auto run at boot.
  8. @martinayotte Does that kernel not have a framebuffer? Last time I checked, I could run a desktop on my Opi+2e
  9. Okay, thanks for the info. It will take a while to debug that problem, since we may change the kernel source for RK3328 in the near future, and I don't want to do any change before that. BTW, I can play Youtube videos just fine, by installing the latest version of youtube-dl form youtube-dl.org, and then just type "mpv-gbm <youtube URL>"
  10. Any client that works on a regular Debian/Ubuntu should work in Armbian. Just do a Google search for "Google drive client for Linux", and try the results.
  11. No idea what it could be. We would need logs to debug the problem. Have you tried using a UART adapter, to get the logs? And also, you can try another SD card, that could be the problem. For last, you can also try mainline, and post the results in this thread:
  12. Hi. Ii tried this on the Renegade Armbian 20.02, and no crash. It is also true that acceleration does not work, due to a permissions issue. We'll try to have it fixed for the upcoming next release. In the meantime, you can fix it by doing the following: sudo nano /etc/udev/rules.d/50-mali.rules (change "mali0" for "mali" and save the file)
  13. Please tell us which kernel you are using.
  14. Also, I noticed it has default subtitles. Did you try disabling them?
  15. Wow, you didn't mention that the file was in a rclone mount from google drive. That is relevant, since it can affect file access. Did you try the same file locally? [EDIT]: Also, I noticed it has default subtitles. Did you try disabling them?
  16. Did you try your original file, but manually setting a smaller bitrate? (4M for example) About your second file, the slow processing is not due to HW video encoding, but to so many other things that you are doing via software (converting 5.1 dts to stereo aac, burning subtitles into the video, re-scaling). Just have a look at htop while you are streaming the file, and you will probably see the CPU maxing out.
  17. It's a know issue. My research suggested it has to do with timing issues when it muxes video and audio, but never looked into it deeply. However, it does not affect jellyfin, because it uses separate mpegts for output
  18. I'm using version 10.4.3, using regular packages (not docker). And yes, HW encoding works. Okay, I see two weird things in your log: First, the message "frame= 0 fps=0.0 q=0.0 size=N/A time=-577014:32:22.77 bitrate=N/A speed=N/A" before the [h264_v4l2m2m] messages. No idea why it is there. Second the very high bitrate. Did you set it on purpose, or you just let it choose the default? I suggest you do two things: 1) Try some other source file; and 2) try to manually set a lower bitrate. Then post the results.
  19. I assume you want to use my ffmpeg, instead of the one included with jellyfin. In that case, you have two options: either install jellyfin debs in your main system instead of using docker, or if you want to keep using docker, then you need to install my debs inside the docker container. Personally, I prefer to use plain debs instead of docker, it makes everything easier (upgrading, database maintenance, custom ffmpeg, etc). In any case, remember you must also change the "ffmpeg path" in jellyfin control panel, to "/usr/bin/ffmpeg"
  20. Ir is just an information message. It tells you that the tool you can use for system configuration is "armbian-config", and it warms you that it is in beta stage, just so you are aware of it.
  21. Well, if that's the case, then we should probably first try to merge legacy too and "sort out the mali mess" as @chwe said above, and if we are not able to do it, then we can split. Regarding what I have been working on: I was preparing an extension for the build system, in order to build the multimedia packages that are on the media script. It was well advanced, but I stopped it since I am not so sure about the prospective for legacy kernels. The impression I get is that most members are willing to get rid of them and stick with Mainline. So I would like to hear some impressions about it, to see if it is worth integrating that into the build script or not.
  22. Well, once a board goes into a family, it shares legacy, current and dev with the others, doesn't it? I don't understand exactly what you mean.
  23. Not if we put all RK3399 boards in rk3399, and all RK3328 in rockchip64. In that case, we could just keep our current kernel config and that would work.
  24. You can try @balbes150's images: Or you can do like me, I just burn two SD cards and switch them at pleasure .
  25. If you want plain window managers with no other gadget or bar on the screen, there are quite a few of them: Openbox, Fluxbox or JWM are among the most popular. But they won't make a big difference with LXDE or Xfce in terms of usability in low-res, since in these you can just hide the panel/bar and you will have the full screen available too. What will really matter IMO is that you set low DPI, set a small font, and choose a compact widget theme (for GTK and Qt). And minimalistic window decorations, in case you use them (some window managers don't even use window decorations, see here: https://wiki.archlinux.org/index.php/window_manager ).