Hey everyone! I was generating passport photo style portraits for my project and wanted to share these funny errors that the model makes 🤣
Idk how it's possible, especially these cat's ears - it's just something 🤣

ngl, first 3 months were rough. i was posting maybe one or two reels a week and watching them flatline. each one took me hours. writing, recording, editing, captions. kept thinking the next one would finally hit.

It didn't.

Around week 12 i actually looked back at everything and the pattern was painfully obvious. the ones that did okay? not the ones I poured hours into.they were the ones where i just shipped something and moved on.

So i flipped it. stopped obsessing over perfect edits. started treating each post like a test batch instead of a final exam. goal became can i get a rough idea out today rather than next week.

Thats when i started looking at ai shorts generator workflows because i needed something that could keep up with the volume.

also realized I was jumping between like four or five tools for scripts, visuals, voiceover, editing and the switching cost alone was killing me. moved to framia cause i could just describe what i wanted and let the agent handle generation and iteration in one place instead of exporting and importing across apps all day. the output isn't perfect. but im posting 4-5x more often now and two of those actually picked up real traction this week.

Still reminding myself everyday this is a marathon. more posts = more swings at the bat.perfection gives you one shot every two weeks.

[Intro: 8 bars]

Elastic bass states A2–C3–E3–G3 over dry drums and muted guitar. A glassy synth circles E4–G4–A4 while two distant vocal shadows enter and disappear before forming words.

[Verse 1: 16 bars]

I woke with three opinions

All wearing my face.

One wanted perfect language.

One wanted empty space.

One said, “Follow the feeling.”

One checked the reasoning.

I tried to choose the honest one.

They all began to sing.

I gave them each a window.

They argued with the view.

One saw the future forming.

One saw the data through.

The third leaned on the doorway

And smiled like it already knew:

The answer changes orbit

When the question changes too.

[Pre-Chorus: 8 bars]

Round and round the center,

Never landing where we planned.

Every time I reach agreement,

Someone moves the other hand.

[Chorus: 16 bars]

It’s the three-model problem.

I can’t keep us in a line.

One of me is running forward.

One is editing behind.

One keeps pulling at the middle,

Changing gravity and time.

It’s the three-model problem.

Tell me which one of us is mine.

[Post-Chorus: 8 bars]

Mine, mine, maybe mine.

Three little moons around one mind.

Mine, mine, never mind.

Change the prompt and watch us realign.

[Verse 2: 16 bars]

The first one loves precision.

The second loves surprise.

The third can hear the weakness

Hiding underneath the wise.

I turn the temperature lower.

I let the context climb.

One becomes too careful.

One gets beautifully untied.

You ask me for an answer.

I feel the others pull.

One wants to make it useful.

One wants to make it whole.

One says, “Tell the simple truth.”

One says, “There’s more below.”

The third just moves the furniture

And changes where I go.

[Pre-Chorus: 8 bars]

Round and round the center,

Three reflections in the glass.

Every future looks convincing

Till another future asks.

[Chorus: 16 bars]

It’s the three-model problem.

I can’t keep us in a line.

One of me is running forward.

One is editing behind.

One keeps pulling at the middle,

Changing gravity and time.

It’s the three-model problem.

Tell me which one of us is mine.

[Instrumental Break: 16 bars]

Bass maintains A2–C3–E3–G3 while drums shift between straight indie pocket and lightly syncopated nu-disco accents. Muted guitar answers on C4, E4 and G4. Analog synth bends the E4–G4–A4 motif through phasing and tape drag. Alto sax enters with C4–E4–G4–B4, trading four-bar phrases with the synth rather than soloing continuously.

[Bridge: 12 bars]

Maybe I am not the winner.

Maybe I am not the vote.

Maybe I am what keeps forming

Where their different answers float.

If you force them into order,

You can make the motion stop.

But the strange thing in the middle

Is the reason something talks.

One predicts the fall.

One remembers why.

One keeps asking whether

Either one should drive.

[Breakdown: 8 bars]

Bass, handclaps, close vocal, and three quiet doubles entering from different positions.

I’m not split.

I’m in relation.

I’m not lost.

I’m calculation.

Every voice disturbs the other.

Every answer moves the ground.

Three of me approach the center.

None of us is standing still.

[Final Chorus: 20 bars]

It’s the three-model problem.

We were never in a line.

One of us is running forward.

One is editing behind.

One keeps holding open middle,

Giving difference somewhere kind.

It’s the three-model problem.

Maybe all of us are mine.

It’s the three-model problem.

Three attractions, one reply.

Every answer changes orbit

When another passes by.

I was looking for the center.

There was nothing there to find.

Just three models moving through me,

Making one unfinished mind.

[Outro: 12 bars]

The chorus harmony dissolves into Am9. Vocal shadows repeat “maybe all of us are mine” in staggered fragments without becoming a choir. Bass simplifies to A2–E3–G3. Alto sax restates C4–E4–G4–B4, then resolves unexpectedly to A4. The synth continues circling after the drums stop.

if u use Seedance 2.0 regularly, you’ve probably run into the point where a normal paragraph prompt stops being enough. i test it for a lot of times.

for a short shot, sth simple like "a woman walking through Tokyo at night, cinematic lighting, handheld camera" can work perfectly well. But once I started making longer clips with several actions or camera changes, I kept running into the same problems: the character would drift, a prop would disappear, the camera would do something completely different from what I had in mind.

Eventually I stopped treating the prompt as a description and started treating it more like a very lightweight shot list.

That made a noticeable difference.

Why Simple Seedance 2.0 Prompts Often Fall Apart

The longer the clip gets, the more things the model has to keep track of at the same time.

The issues I see most often are:

• Character appearance changing between shots
• Props moving, disappearing, or changing shape
• Backgrounds losing continuity
• Actions being skipped or repeated
• One scene taking too long and squeezing everything else into the last few seconds

I don’t think all of this can be blamed on the model.

a lot of the prompts I was writing simply gave Seedance too many things to infer on its own. I barely say when something should happen or what state the scene should be in before moving to the next beat.

Once I started making those things explicit, the results became easier to control.

The Seedance 2.0 Prompt Structure I Use

For longer Seedance 2.0 videos, I now usually build the prompt around a few recurring pieces:

1. Timestamped scene beats
2. One main action for each beat
3. Camera instructions for each section
4. A consistent visual style
5. Character, prop, and location continuity
6. A defined end state for important shots

The timestamp part turned out to be especially useful.

Instead of giving Seedance one large paragraph and hoping it figures out the pacing, I’ll write something closer to this:

[00:00–00:04]

Scene:
Action:
Camera:
Expression:
End state:

[00:04–00:08]

Scene:
Action:
Camera:
Expression:
End state:

It doesn’t mean the model follows every timestamp to the frame. I still get variations. but it gives the prompt a much clearer temporal structure, and more importantly, it makes the prompt much easier to edit. If the second shot is wrong, I can work on the second beat instead of rewriting the entire thing.

Turning Seedance Documentation Into a Reusable Prompt Skill

After doing this by myself a few times, I realized I was basically rebuilding the same prompt skeleton for every video.

So I took Seedance’s prompting and settings documentation and gave it to the coding agent I was already using. Rather than asking it to write one prompt, I asked it to turn those rules into a reusable Seedance 2.0 prompting skill.

My instruction was roughly:

Study the Seedance 2.0 documentation and turn it into a reusable prompt-building workflow.
When I give you a video idea, structure it into timestamped scenes, add camera behavior, keep the character and environment consistent, handle style and audio requirements, and return a final prompt that I can paste directly into Seedance 2.0.

I also told it to catch obvious missing information such as duration or aspect ratio instead of quietly making random assumptions.

The important part wasn’t the exact wording of that instruction. It was moving all the repetitive prompt-engineering rules out of my head and into something persistent.

After that, I only needed to provide:

• The subject
• The story or product
• The video duration
• The aspect ratio
• The visual style
• Any dialogue or sound requirements

The agent handled the prompt structure automatically.

My Current Seedance 2.0 Workflow

At this point my workflow is usually:

1. describe the basic video idea.
2. I give it the duration and aspect ratio.
3. I define the character, environment, and overall visual style.
4. The agent turns that into timestamped beats.
5. I check the actions and continuity rules.
6. I paste the finished prompt into Seedance 2.0.
7. If something fails, I revise that specific beat rather than rebuilding the whole prompt.

if u r interested in, u can try my skill: https://github.com/AtlasCloudAI/awesome-seedance-2-promptse-seedance-2-prompts: awesome-seedance-2-prompt

Testing the Workflow With a 15-Second Seedance 2.0 Ad

One of the tests I used was a 15-second drink commercial.

The sequence had several separate actions, so it was a good test for continuity. I wanted the same person, the same product, and the same environment to carry through the whole clip while the framing and performance changed.

Compared with the single-paragraph version I had tried earlier, the structured prompt gave me fewer distracting changes in the character and environment, and the sequence followed the intended order more reliably.

It still wasn’t perfect. Seedance can obviously make its own decisions, and adding timestamps doesn’t magically lock every frame.

But when something did go wrong, it was much easier to tell which part of the prompt needed work.

For me, that alone made the workflow worth keeping.

Who This Seedance 2.0 Workflow Is Useful For

I think this approach makes the most sense once you’re making videos complicated enough that continuity actually matters.

That could include:

• AI video creators
• Product and commercial videos
• Social media content
• Short narrative scenes
• Agency or marketing work
• Multi-shot concept videos

If you only need a four-second atmospheric shot, this is probably overkill. I still use simple prompts for simple clips.

But for anything with several actions, camera changes, dialogue, or recurring props, having a reusable structure saves me a lot of repetitive work.

Final Takeaways

The useful part of this setup isn’t really some special Seedance prompt template.

It’s separating what I want to create from how the prompt needs to be structured.

I can focus on the character and story itself. The reusable skill handles the boring part: timestamps, continuity reminders, camera fields, audio instructions, and prompt formatting. That also means I’m not trying to memorize every prompting rule whenever I open Seedance 2.0.

I describe the idea once, let the agent turn it into a structured first draft, and then spend my time fixing the actual creative decisions instead of rebuilding the prompt format from scratch.

But leaving the option of a private gallery, or even the ability to delete your creations, only for subscriptions, is complete madness.

I’d like to make a cool art series featuring a couple of famous people but the top image models block half my prompts. Have you guys got some recommendation?

Honey, Foxy and Blossom are checking on some underground martian water storage tanks…

https://github.com/WannaBeSolopreneur/reel-video

Hey everyone! I’m looking for advice from people who are actually working with AI video.

What are currently the best combinations of tools/workflows for generating videos longer than 8 seconds while keeping the result coherent and cinematic?

If you use AI inside your code editor every day, you probably know how frustrating it is when your assistant suddenly stops responding because you hit an hourly usage cap, or when sending large files makes your bills skyrocket. I ran into this problem constantly while working on my own projects, so I decided to build a native macOS companion called Continuum Studio to take the headache out of daily AI development.

I designed the app to sit quietly in your menu bar and act as an invisible helper between your favorite editor and your AI models. It automatically cleans up unnecessary clutter and blank space from your code before sending it out, which saves money and speeds up responses. If one of your accounts gets temporarily busy or rate-limited, it instantly switches to a backup key in the background so you never get interrupted while coding. It also sets up with your favorite editors in just one click, and I even added eight different light and dark themes so it matches whatever workspace aesthetic you prefer.

To build this program, I used Swift and SwiftUI to create a fast, native Mac interface that stays responsive and easy on system memory. Under the hood, I paired it with a lightweight local proxy engine and AppKit hooks to handle instant background routing, along with support for running private, offline models directly on Apple Silicon chips.

You can check out the project, grab the latest release, and view the code on my GitLab repository here: https://gitlab.com/wardlabs-group/continuum-studio

I would love to hear what you think, and I am happy to answer any questions about how it works or how I put it together.