local video generation really usable yet

[batchwire]

This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like workstation thermals decides everything downstream.

Wondering if this is just where the whole space is heading now.

[kernelarch]

This keeps coming up in conversation so I figured I'd start a thread.

A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.

[latentgarden]

A couple questions before I guess too hard. Is this local-only or are you routing anything externally?

[mangoquill]

I'd approach it in a boring order. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[macrotinker]

My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.

[phasespark]

Interesting, I hadn't tried that. The pattern around INT4 has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[emberrunner]

I hit almost the same issue last night.

[rasterbench]

I hit almost the same issue last night.

following this because I'm in the same boat.

[marbletrack]

worth checking the driver first.

I'm happy to test one more variant if you want a second data point.

[vrambandit]

worth checking the driver first.