As other comments suggest, this might be due to transcoding. There is tool Tdarr which transcodes media in advance. h264 could be the safest choice for mobile (hw support) and web.
I am full stack developer with "can do" attitude, leaning towards backend, devops with background in embedded electronics (IoT) and mechatronics (production systems). Interest in broad number of industrial fields will pay off in your project.
Actually LoRa is not a protocol but physical layer, way of modulating RF. LoRaWAN is probably that consumer protocol which you refer to.
There is also Symphony Link protocol (proprietary).
And I wouldn't use LoRaWAN protocol in industrial application, because you have limited way of ACKing every message (more like UDP for sending sensor data rather than TCP), no option for OTA, and Symphony Link claims to have it, so that I would call it more industrial.
I use node-red for Escape Room game high level automation. Gathering data from all the puzzles (over CANbus and mqtt), displaying game state for game masters, fallback control, audio+light sequences, etc
I am full stack developer with "can do" attitude, leaning towards backend, devops with background in embedded electronics (IoT) and mechatronics (production systems). Interest in broad number of industrial fields will pay off in your project.
But still data is stored in 8 bits. 9th bit holds information whether "byte" contains slave address or frame data. so that when slave listens and if it receives byte with 9th bit set and the rest is it's own address, then it can start to interpret following bytes. Otherwise it can ignore following data.
Maybe that comment is not so relevant to thread, but one may be curious how it works.
That limitation is not specific to LoRa but to anything transmitting in ISM band e.g. ~868 MHz in EU, ~900 MHz in US.
It limits single transmitters air time to 1% so that one can build radio communication with any modulation, any protocol and limits probability of collision with different devices in range.
I wonder if ISM band will provide dedicated spectrum for LoRa with unlimited airtime.
I did. I've been maintaining python+ncurses tool for configuring system: network, ntp, etc. If you don't have dhcp server running on your network, then ifup will block until it resolves address (ui freeze). If not, then you have to kill it and also dhcp reolver. After switching to systemd-networkd it just works in background.
All configuration is done with .ini style files so that no need to use special parser for /etc/network/interfaces.
Disclaimer: I jumped on linux few years ago when systemd already had some momentum, so that I wasn't used to either init or systemd. I found the later easier to pick up.