-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
Yep! It glues ffmpeg, str0m[0] and SDL together. I hope bitwhip doesn’t need to exist someday. When WHIP/WHEP has enough traction it will be easier to land in FFMPEG
[0] https://github.com/algesten/str0m
-
My first thought was that that was dropping one of the main features of make.
On reflection though, the timestamp dependant part isn't really something used much nowadays apart from compiling C.
It'd be cool if it was an opt-in feature for just files so that it could actually function as a replacement for make in all cases.
I went looking in the docs and found this[0] which I'd missed last time I looked into justfiles.
[0] https://github.com/casey/just?tab=readme-ov-file#what-are-th...
-
As someone who setup a discord streaming like service to use alongside Mumble, this is very exciting. I couldn’t get anything involving webrtc working reliably, but the only broadcasting clients I found were web browsers and OBS, so I am interested to see how this compares!
What I eventually settled on was https://github.com/Edward-Wu/srt-live-server with OBS and VLC player, which gives robust streaming at high bitrate 4k60, but latency is only 1-2 seconds
-
I recently switched my (small) company over to using just files within our codebases and it's been going over very well thus far.
We're building a set of apps that need to run on Linux, MacOS, and Windows so having a consistent solution for each is better than shell scripting and I personally have never felt great about make and it's weirdness.
It also helps that we have a pretty big monorepo so that anyone can bounce from one app to another and `just run` to use any of them, no matter the platform.
Either way the justification for me came from COSMIC[0].
[0] https://github.com/pop-os/cosmic-epoch/blob/master/justfile
-
E.g. "Low Latency DOCSIS"[0] and related, WiFi[1], support it and with the former it's about non-exclusive scarce uplink capacity where cross-customer capacity sharing may rely on post-hoc analysis of flow behavior to check for abuse, switching to forced fairness if caught by such heuristics. For downstream it's even more natural to have shared capacity with enough congestion to matter, but often only the WiFi side would have a large discretionary range for bandwidth scheduling/allocation to matter much.
Apple already opportunistically uses L4S with TCP-Prague and there are real-world deployments/experiments [2] with end-to-end L4S.
Fixed-
[0]: https://github.com/cablelabs/lld
-
-
I don't believe it is possible today, but I am working on it! It would be great for users trying to co-stream.
I created OBS2Browser[0] that is a good first step in the direction.
[0] https://github.com/Sean-Der/OBS2Browser
Related posts
-
How to Create Simple Custom Insurance Quoting System with Flexible Pricing Rules
-
How to Create a Custom Policy Management Application in Just 5 Minutes
-
An interpreter inside an interpreter
-
How to Create a Custom Claims Management Application in Just 5 Minutes
-
Pyqwe: The quick work environment for Python