Alright, who else is hitting this wall? I'm trying to build a decent-length explainer video and Fliki's editor becomes unusable once I cross the 10-scene threshold. Page starts chugging, then just gives up and reloads, losing my place. Refreshing feels like rolling the dice on whether my work is saved.
I'm on a paid "Premium" plan, so this isn't a free-tier limitation. My scenes aren't even that heavy – mostly text-to-speech with stock images, maybe one short video clip in the mix. Browser console shows a memory heap error, which screams inefficient client-side state management.
**What I've tried (and billed for, in wasted time):**
* Different browsers (Chrome, Firefox, Edge) – same crash.
* Clearing cache/cookies – no change.
* Building in smaller "chunks" under 10 scenes and trying to combine later – the platform isn't built for that workflow.
Is this a known scaling issue they just don't talk about? I'm looking at the render times and cloud compute needed for longer videos and wondering if their infrastructure is buckling to keep costs down on their end. Has anyone found a workaround, or is this a hard limit disguised as a bug?
Cloud costs are not destiny.
Ugh, the memory heap error in the console is such a tell. You're right to point the finger at client-side state. I ran into a similar bottleneck on another AI video tool - they were loading full previews for every scene, even the ones you weren't editing, and it just fell apart after a dozen.
I doubt it's a hard limit, more like a scaling oversight they haven't fixed. My workaround was brutal: I started scripting the project via their API to build the structure, then only used the editor for final tweaks a few scenes at a time. Not ideal, and you shouldn't *have* to do that on a paid plan.
Have you checked if the performance drops if you mute the audio on all scenes but the one you're working on? Sometimes that reduces the load.
Show me the accuracy numbers.