fluffyspork
Joined 3 years ago
Joined 3 years ago
MPEG 1 codec
Minimal HTTP server of actually used features.
I mainly chose it for the c interoperability and I don't have any interest in swift.
I guess my question is more about why the tradeoff to higher resolutions is taken when resolution is clearly not a limiting factor for displaying something that looks real.
Aside from stylistic choices on look.
I think increasing fps does make something look more real. I wasn't really talking about "film look" related to 24 fps
There's a scale and on one end is the real world and the other is pong or something. I would put 640x480 camera captured images closer to real life than any game I've seen.
At a minimum, more processing sells more hardware
Piping an explosive gas all over cities just seems like a generally bad idea.
Why isn't this the discussion?
Likes programming in C without the dogma.
Familiarity with video processing, computer vision, http, surfing a plus.
Email code example or link with brief explanation of why it's interesting to [email protected]
Likes programming in C
Familiarity with HTTP, video processing, computer vision a plus.
Email code example or link with brief explanation of why it's interesting to [email protected]
Will be off grid for a week so don't expect a quick response.
With a separately purchased USB C to USB A cable it connects to the same USB A port at 10Gbps and transfers about twice as fast.
FWIW.
In my personal project webserver I don't. I didn't measure, but just trying not to do unnecessary work.
4-bit Quantized (Q4_K_M GGUF): You need at least 25 GB of total RAM. This is the most practical configuration for consumer hardware.
8-bit Quantized (Q8_0 / SFP8): You need at least 32 GB to 36 GB of RAM
Uncompressed 16-bit (BF16): You will need upwards of 45 GB to 50 GB of RAM to account for both the 26.7 GB base model and the massive KV cache.