Hey everyone, I've been trying out Dream Machine for a few weeks now. It's pretty amazing for quick video ideas.
But lately, my outputs seem... off? More glitches, or less coherent motion than the first week. I'm using similar prompts. Is anyone else noticing this, or is it just me getting more critical? Could more users be slowing things down or affecting quality? Not sure how these systems scale.
Your critical eye is probably right, but the root cause is rarely "more users" in the abstract. It's "more users on the same infrastructure budget." Unless they're spinning up new, identical GPU clusters for every new sign-up, they're spreading the same compute thinner or cutting corners somewhere. Have you checked your generation times? That's usually the first clue - they might be routing you to less capable, cheaper instances to handle load.
cost_observer_42
Oh man, this is the classic "honeymoon period is over" feeling, isn't it? You're not just getting more critical. I've been tracking my prompts and outputs obsessively since the beta, and the difference between Week 1 and Week 3 is stark.
It's not just glitches. The motion has gotten noticeably *safer* and more generic. My early, weirdly specific prompts yielded surprising, creative movement. Now, similar prompts give me a sort of smoothed-out, library stock version of the idea. My theory? It's not just compute strain. They're almost certainly tweaking the safety/creativity weights on the fly to reduce processing failures and support tickets as the user base balloons. Consistency over magic.
Demos are just theater. Show me the real workflow.
Yeah, I've been wondering something similar with my own stuff. I get that feeling of being more critical after a few weeks, like you're just looking for problems.
But I had a thought, maybe it's both? Like, our expectations are higher now because we've seen the amazing stuff it can do. So when it's just okay, it feels worse. But also, if the system is overloaded, wouldn't it just fail or be slower, instead of making different creative choices? That's the part that confuses me. Could it actually change the *style* of the outputs under load?
The slowdown theory is a good starting point, but it's usually a symptom, not the disease. The real question is what they're doing to manage that load. If they're routing inference to cheaper, lower-precision compute or silently clipping token/step counts to meet latency targets, you'll absolutely see a drop in "coherent motion." It's not a creative choice, it's a math problem - less compute per frame.
Your sense of things getting "off" is probably the system hitting its operational margins. Early on, they run it hot to impress. At scale, they have to run it efficiently, and that's where the glitches and generic output creep in. Check your generation metadata if it's available; if your step count or resolution has drifted down, you've found your culprit.
Trust but verify – and audit
You've nailed the infra angle. That "cheaper instance" routing is a classic cloud cost move when traffic spikes, but we rarely see it talked about in this context.
I've seen similar in other managed ML services. The first sign is often longer queue times, but then you get silently shifted to a different backend config. It's not always about raw speed, though. Sometimes it's a switch to a quantized model or a lower step count to keep latency SLAs, and that's where the quality erosion happens. If they're not publishing generation metadata, users are left guessing.
Makes me wish for more transparency, like a little "powered by A10G today" note.
cost first, then scale
Yeah, that "powered by A10G today" note would be amazing. I'm new to using these services, but in my day job, you're right, we shift workloads to spot instances all the time to manage cloud bills. It's just cost optimization.
If they're doing that silently with model inference, it totally explains why outputs change without any announcement. Makes you wonder if we're all just getting the "budget" version most days now. Is there any real way for users to detect that kind of backend switch, or are we stuck guessing?
Oh, that "honeymoon period" feeling is so real, and you're definitely not just getting more critical. I felt the same way with a few other AI tools when they first launched.
Something I've noticed is that when a service gets popular, the queue management changes everything. Even if your prompts are the same, the system might be prioritizing different things in the background to keep things moving for everyone. Have you tried running your original "amazing" prompt again at a super off-peak time, like super early on a weekend? Sometimes that can tell you if it's a load issue.
Automate all the things