UGC Clip

The UGC Clip node renders one clip of a UGC video: the creator saying that clip's lines. It runs once for each clip that UGC Clips made. When the clip is voiced, its voice is made first. A voice that runs longer than the clip makes the clip longer to fit.

Each render is checked. Two of its frames are read beside the creator's image to catch a bad take. If the check fails, the clip is rendered once more and checked again. The new take is kept if it passes. Otherwise the first take is kept, and the Notes of UGC Cards say what the check found. If the check itself cannot run, the take is kept without it, and the Notes say so.

On a Hebrew video, each render is also checked against the clip's recorded speech. A render with no sound fails that check and is rendered once more. If no render has sound, the clip stops with "Clip N has no sound, so the video cannot be finished. Re-render that clip from its UGC Clip node."

The node shows the clips it rendered, and how many warnings they carry.

UGC Clip runs on Nodaro Cloud only. On any other install, every UGC node fails before anything is reserved, with "UGC videos are a Nodaro Cloud feature and are not served on this deployment."

When to use it

• You have the clips from UGC Clips and want to render them.
• You want a new take of one clip, without rendering the others again.

Quick start

Inputs

Outputs

A connection from UGC Clip is in Selected mode by default, which passes on only one clip. Into UGC Finish, or straight into Combine Videos, set the connection to Bundle mode, so every clip goes on in order. A Hebrew video needs UGC Finish before the join. On an English video, UGC Finish passes the clips through at no cost. A video of one clip passes through Combine Videos unchanged, at no cost. See Connection modes.

The same output also feeds the Clip notes input of UGC Cards, which reads each clip's warnings and real length.

Settings

UGC Clip has no settings of its own. The settings panel lists the last run's clips, each with its length and its warnings, and a Re-render button for each clip.

Re-render a clip

Press Re-render on a clip. The clip is marked "Will re-render on the next run". The next run of UGC Clip, or of the workflow, renders that clip again and reuses every other clip at no cost.

In the editor, a clip whose content has not changed is not rendered again. The next run hands back the take it already made, at no cost. A clip renders again when its line, its creator or its voice changed. Every clip of a new script or a new creator renders again. A published app's run renders every clip of its own video.

All or nothing

If any clip fails, UGC Clip fails as a whole. A Bundle connection after it therefore never receives a partial list, and the joined video is never made with a clip missing. The clips that finished are kept and charged. In the editor, the next run reuses them at no cost and renders only what failed.

Credits

A clip costs:

• the video model's price for the clip's length;
• the voice, when the clip is voiced;
• one frame reading for each render.

While a clip renders, the node holds about twice the expected amount and returns what it did not use.

• A re-render costs the video's price and its frame reading again. The voice is made once.
• A clip that fails is not charged.
• A clip never costs more than it holds. When its voice makes the clip longer, the longer clip is priced at its new length out of the same hold. The re-render runs only if what is left still covers one. The Notes say when it could not.
• A clip handed back from an earlier run costs nothing.

In the listed price of an app or a template

The listed price of an app or a template counts a UGC video as its runners run it. Keep is off in what ships, so the price always includes the script and one creator, at the script's length setting. A step priced by the length of its input, such as Combine Videos, Trim Video, Loop Video or Video SFX, can sit on the output of UGC Clip. Such a step, other than the video's own join, counts UGC Clip as one clip at the longest length any video model makes.

Prices in the editor

Before a run that includes a UGC node, the editor prices the UGC part of the run with the server's own figure. The figure covers exactly the nodes the run executes, every creator option included. The price it shows is what the run is expected to cost.

Your balance is then checked against what the run holds while its clips render, about twice their price. The part not used comes back when the clips finish. On a Hebrew video, the recorded speech decides how many clips there are. The check then holds the most clips that any accepted recording of the video can be cut into, not the clips the length usually needs. A recording holds at most 1.2 times the target length, and never more than 21 seconds. A balance below that refuses the run before anything starts, and the buy-credits dialog opens.

This check applies to every way to start a run: Run, Run from here, Run up to here, Run selected, a node's own run button, Render final and Update preview. A run with no UGC part is checked as usual.

• Until the server's figure arrives, the run buttons show the editor's own estimate.
• When the figure cannot be checked, the run asks before it starts and says why. Render final and Update preview then mark their price "(estimate)".
• A kept creator or script costs nothing. A kept script is priced at its own length and screenshot cards.
• Clips that have not changed are reused at no cost, so a run may cost less than its price.

A published app's run is checked the same way before it starts, against what its UGC video can hold while it renders.

Tips

• Watch each clip before you join them. Press Re-render on the clips you do not like, then run again. Only those clips render.
• Read the Notes of UGC Cards. A note such as "Clip 2 may not say its line exactly" points at the clip to re-render.
• Reopen the editor after a long run. When a run ends while its editor is closed, reopening the editor shows that run's results on the UGC nodes and on the video's own join, overlay and captions. The newer run wins. UGC Clip and those three nodes show the newer video first and keep the older ones below it.
• Publishing ships no takes. A template published with Include this run's results shows each clip's current take as an example.

Troubleshooting

From the API

UGC Clip calls POST /v1/ugc/clip when it runs, and the route answers with a job id. The request and answer shapes of the UGC routes belong to the nodes and may change between versions. To make a UGC video from code, run a workflow or a published app that holds the UGC nodes. See Workflows.

A published app's run of a UGC video is checked before it starts. When the payer cannot cover what the video can hold while its clips render, the run is refused with 402 insufficient_credits, before anything runs or is billed. The message is "This video can hold up to about … credits while it renders; your balance is …." See MiniApps and Credits.