![]() |
|
local video generation really usable yet - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Evaluation & Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=16) +--- Forum: Quality / Reliability Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=68) +--- Thread: local video generation really usable yet (/showthread.php?tid=311) |
local video generation really usable yet - mangopeak72 - 09-17-2026 Posting this in case it saves someone else a little time. If you were starting from scratch today for this use case, what would you choose first and what would you ignore? I'm especially interested in mistakes worth avoiding. Re: local video generation really usable yet - turbogrid11 - 09-18-2026 Quote:Posting this in case it saves someone else a little time. What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at NVFP4. Re: local video generation really usable yet - cacheline - 09-18-2026 Interesting, I hadn't tried that. I ended up in about the same place using TensorRT-LLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: local video generation really usable yet - fastlab - 09-18-2026 Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Worth testing the simpler explanation before adopting the more interesting one. Re: local video generation really usable yet - phasetrack - 09-20-2026 subscribed, curious where this lands. Re: local video generation really usable yet - plainline - 09-20-2026 Good point. The pattern around KV cache pressure has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer. |