Setting up a simple Offload workflow

The most basic operation of QI is quick local verified Offload of your media, and giving you a receipt for the transaction. One of the huge advantages of QI is that once you have set-up a workflow, operation is mostly drag-and-drop’ing for the rest of that production.

Let’s set up a basic Offload workflow. Here is a quick video showing the procedure:

The Workflow Editor is an extremely powerful tool, but for now, let’s focus on the basics.

We will “Create a new” workflow

And for this workflow we will start with the “New data template”. Don’t get too hung up on the nuance between “New data” and “Existing” data for the moment. We want to offload a card. That is New! 🙂

To set up a workflow, you have to set up all nodes. If you skip one, you will not be able to save.
Don’t worry though, it is pretty fast and simple.

The “MovieSlate” node is not super important for this workflow. (And you only want to use the “Swap” switch if you work at NRK)

The “LocalCopy node is the important one for this workflow. We will now set it to the destination we just created (you can set multiple)

We set the FFmpeg node to “off”. No fancy transcodes here

Likewise we set the REDline node to “off”

We turn off all file-uploads.
The receipts, metadata and locators of your files will be written to QuineCore, still.

No point in creating online-streams for this workflow:

But we want the receipt to be stored in the project-folder:

And finally: Nope – we are not doing any of those fancy conforms

Now we just need to save ur new workflow:

I strongly recommend giving your workflows a good name. You will use this throughout your production.

We are now ready to offload some data