Create a review in the Rush Portal

The Rush Portal is where new content comes into ClearView Rush. You create a review, upload the files for it, and then publish it when it's ready.
​

If you regularly submit content into Rush from outside the studio, you'll be given the Contributor role and work entirely within the Portal — it's where you land when you sign in. Workspace Managers move between the Portal and the main app; the Portal link sits near the bottom of the sidebar.

​

In the Portal, click + New Review. Name the review — leave it blank and it takes today's date — then pick the Project and the Review Type.
​

Every review needs one or more media files, in an approved format: .mov (DNxHR LB/SQ, ProRes 422/LT, H264, H265) or .mxf (DNxHR LB/SQ).

Cuts and dailies reels also need metadata — it's how Rush interprets the media as that review type, rather than a set of standalone assets:

Timeline data is a .csv with a header row and three columns — Scene, Description and Start — where Start is the scene's start timecode (HH:MM:SS:FF, HH:MM:SS;FF for drop-frame, or HH:MM:SS.fraction). Each scene runs until the next one's start, and the last to the end of the media. For now, a cut is a single media file.

Slate metadata is a standard Avid .ale. Its header must declare the FPS, and each clip row needs a Name, a Start, and either an End or a Duration. The slate columns — Scene, Take, Camera and circle take — drive the shot strip and its filters. Each clip is matched to its media file by Name.

Add your files by dragging folders or files onto the drop zone, or use the two buttons in its top-right to browse for a folder or for individual files. As each one is added it's sorted into a category and checked — a green status confirms it's been picked up correctly and is the right type.

A cut can also carry a continuity report (.pdf), kept with the review for viewers to open alongside the picture. It isn't parsed, so any PDF works.

For a cut or a dailies reel, this step previews what Rush read from your files, so you can catch problems before the upload starts.

For a cut, look over the scene list read from your CSV — each scene's start, duration and description, with the total scene count and running time. If something looks wrong, fix the CSV and go back a step. Once published, the scenes show in the review's details and as chapters in the player.

For a dailies reel, check each clip picked up its slate — scene, take, camera, circle take and shoot date, with the shot/setup/scene totals. A clip with an empty row usually means its filename doesn't match the ALE.

A general review has no metadata to read, so this step is skipped.

At Check Metadata, a dailies reel matches each row in your ALE to a media file by name — the clip's Name to its filename. Case and file extension don't have to match, but the names do. Two things can trip this up:

A few other messages you might meet:

When your files are ready, select Transfer to start the upload. It runs in your browser and shows live progress — the percentage done and an estimated time remaining — with three counters beneath it: Files Uploaded, Bytes Uploaded and Current Speed.

If your connection drops briefly, Rush retries automatically. If it can't recover, you'll see Transfer Failed — "The upload could not be completed. Please try again." — and you can run the transfer again. This is the most network-sensitive part of the process, so if you hit problems repeatedly, contact Sohonet support — it's usually something in the network path worth looking at together.

Uploading isn't the last step. Once your files are in, Rush generates previews for them — the transcoding pass that prepares the media for playback. This can take a while, depending on how much you've sent.

While it runs, the review sits under In Progress in the Portal; once every file has finished, it moves to the Ready tab, where you can publish it. A review can't be published until all its media has been transcoded — so if there's no Publish option yet, previews are still being generated.

You can cancel an import from the review drawer while it's still in progress.

Until you publish, a review stays a draft — only you can see it. Once it's through transcoding and sitting on the Ready tab, find it, click Publish and confirm.

What happens next depends on the review's type. If the project runs a workflow for that review type, publishing routes the review into it automatically and shares it with the first stage's audience — there's no separate sharing step. If there's no workflow, the review simply becomes shareable, ready for you to share directly. Either way, it moves to the Published tab.