Visit here:
https://www.m0plt.me.uk/qsstv.php
for QSSTV plus other software (FLDIGI, etc.)

Magnum Engergy MSH4024M Hybrid Mobile Inverter
EG4 24V LiFePo4 200AH Battery

* https://www.solar-electric.com/magnum-energy-msh4024m-hybrid-inverter.h…
* https://shop.signaturesolar.us/products/4v-200ah-battery-by-eg4

(further parts required like cables, fuses, high current switches, bus bars, etc.)

Remember that both jstest-gtk and evdev-joystick are important in tuning the the joystick behavior:

$ apt install jstest-gtk

and

sudo evdev-joystick --evdev /dev/input/by-id/{controller name} --d 0 # zero's out the dead zone that the hid "event" system inserts into that abstraction layer

Flow 8 Pulseaudio script (to create USB1-2 and USB3-4 and if in "Streaming" mode will create Mic1 & 2 + Main from the 10 input channels):

#!/bin/bash

pacmd unload-module module-remap-source
pacmd unload-module module-remap-sink
echo unloaded modules
sleep 2

It has gotten to the point where Pulseaudio in many ways is superior to the sound engine in Windows/Mac.

Interesting history and technical overview of USB audio:

http://thewelltemperedcomputer.com/KB/USB.html

Bookmarking URLs here:

* https://xlights.org/
* https://www.pixelcontroller.com/store/index.php
* https://www.holidaycoro.com/

Not that I used this recently, but saw an article on some commands that thought would be good to document here:

Most the examples don't list basic file globing for input... so here it is:

$ ffmpeg -pattern_type glob -i '*.png' -c:v libvpx-vp9 -pix_fmt yuva420p output.webm

When new enough ffmpeg can do vp8 with transparency that is backwards compatible with decoders that DON'T support alpha channel:

$ ffmpeg -pattern_type glob -i '*.png' -c:v libvpx -pix_fmt yuva420p -metadata:s:v:0 alpha_mode="1" output.webm

Most examples show something like this:

$ ffmpeg -framerate 25 -f image2 -i frames/%03d.png -c:v libvpx -pix_fmt yuva420p output.webm

I should have documented this (and other useful tools which I can't remember at this time) earlier:

/etc/udev/rules.d/99-CHProducts.rules:
KERNEL=="event*", ATTRS{idProduct}=="00f2", ATTRS{idVendor}=="068e", MODE="0666"
KERNEL=="event*", ATTRS{idProduct}=="00f3", ATTRS{idVendor}=="068e", MODE="0666"

There are some ways to scan input devices .. some "jstest" and another way -- can't remember because it would come in handy with previous post about NX6000D HID interface: