First project guide
This is an independent Digen guide, not a video generator. Partner links open Kyncept, a separate creation service; sign-in and paid credits may be required for video generation. No prompt is transferred.
Start with a scene you can describe clearly, then check the controls and terms shown in the tool you open. This guide covers the decisions you can make before generating anything, so you can judge a result against your original goal rather than guessing what to change.
Explore Kyncept on its own site
Example to prepare on the destination: A cyclist rides through a rain-soaked city at dusk; wide shot, soft reflections, calm mood, no visible text.
Prepare a short brief and check the tool's current options before you commit to a project.
Start here if you want to understand the kinds of creative tasks associated with Digen before drafting a brief.
Use this overview to separate a video concept from the generation features you need to verify in the available interface.
Review practical privacy and rights checks before submitting personal images, client material, or sensitive text.
Move from a testable idea to a careful review, changing one part of the brief at a time.
Choose a subject and one action that a viewer could recognize immediately. Instead of asking for an entire story, describe a single shot: who or what appears, where it is, what moves, and the atmosphere you want. For example, a cyclist crossing a wet street at dusk is easier to assess than a request for an exciting travel film. Decide what must remain visible throughout the shot and what can vary. That gives you a simple checklist when you inspect the result.
Open the destination through the action on this page and inspect its current input fields. If it accepts a text prompt, paste your short scene description and add useful visual direction such as framing, lighting, or pace. If it offers reference inputs or settings, use only those you understand and are permitted to submit. Avoid stacking conflicting instructions, such as asking for both a close-up and an uninterrupted wide view. Before you proceed, check any displayed terms, limits, or required steps; this guide cannot confirm which controls your session will show.
If the interface produces a result, compare it with the checklist from step one. Look first for the subject and action, then inspect continuity, readable details, and unwanted text or objects. Note one problem in plain language and revise the part of the description most likely to affect it. If the camera is too close, adjust the framing; if the setting is wrong, make the location more concrete. Save the wording of versions you prefer so later changes are easy to explain and you can return to an earlier direction.
An unclear brief is hard to evaluate. A specific brief gives you something observable to check.
These are separate illustrations, not a documented Digen before-and-after result. The useful comparison is in the wording: replace “make something cinematic” with a subject, action, setting, and camera view. If a result includes unwanted lettering, state that the scene should have no visible text; inspect the next result rather than assuming the instruction will work. If motion or framing feels inconsistent, simplify the action and request one clear shot. If the interface rejects a request, read its message and check the input requirements instead of repeatedly submitting the same description.
Keep a short record of each description and the change you made. Revise the largest mismatch first: subject, action, setting, or framing. Change one of those at a time when possible, so you know which edit helped. Describe visible details rather than abstract praise: “streetlights reflected in rain” gives you something to inspect, while “make it amazing” does not. For material involving real people, brands, or clients, confirm that you have the right to submit the inputs and use the result. Check the destination's current options and terms before relying on any output for a published project.
Pick one scene rather than a complete story, and write down its subject, action, setting, and mood. Open the destination and check which inputs it currently offers before adapting that brief to the interface. This keeps your first attempt small enough to assess.
Name what the viewer should see and what should happen in the shot. Add a setting and, if useful, one camera or lighting direction, such as a wide view at dusk. Avoid contradictory instructions, and leave room to revise after you see what the available tool produces.
Identify the biggest mismatch before rewriting anything: is it the subject, movement, setting, or framing? Make that part more concrete and try again if the interface permits another attempt. Keep your previous wording so you can compare what changed.
That depends on the inputs the destination currently provides, so check its interface rather than assuming image upload is available. If it accepts a reference, use material you have permission to submit and read the applicable terms first. A short text brief can still explain the action or mood you want from a visual reference.
Check it against your original brief and inspect details a quick preview might miss, including unintended text, inconsistent objects, and awkward motion. Then confirm the destination's current usage terms and any output options relevant to your project. A result that looks appealing is not automatically suitable for every use.