CatDV Server, Pegasus and Transcoding RED 8k

[Will Luker]

We have 2 REDs, including the Helium 8k. We are in the final stages of selecting a MAM, but 8k is causing some hesitations with regards to CatDV's 8k support.

What I'm looking to do is to ingest our 5k, 6k and 8k footage into CatDV server, and have CatDV generate the proxies and mezzanines automatically to use with our Adobe Premiere workflow.

I know the Pegasus client supports previewing 8k, and I've had mixed results using the Pegasus client generating the proxies itself.

There's a posting on Squarebox's website explaining a CatDV server / REDCINE integration whereas REDCINE is used to do the transcoding using the CLI and workernode. If that workflow works for 4k (using REDCINE), wouldn't it stand to reason it will work with all resolutions assuming that they are fully supported by the REDCINE CLI?

Who else is using CatDV to handle transcoding your RED footage?

If somebody is already using the recommended REDCINE integration with CatDV, can we try that with some 8k footage to see how it behaves?

I recently purchased a server specifically for transcoding and so far using REDCINE CLI alone, it's extremely fast.

 

[Gunleik Groven]

We're working on something like that for Qi.
The concept should be good.

(this not said to "poach" anything from CatDV, just as a conceptual: "Yes, this should work" response)

 

[Will Luker]

Seems like a smart way to approach it. Qi looks interesting. Is there an Adobe Premiere integration?

 

[Gunleik Groven]

It integrates through FCP7 .xml

Have to point out that the redline vs SDK implementation discussion isn't "done" in Quine, and that we won't do the RED transcode overnight without a good reason to do so (we have a few, but still...)

Qi is pretty good for what it does. Which is basically "multi user/project/working on different parts of the workflow simultaneously from several stations at the same time"
Others are stronger on other things.

Ours is free to use, though, so if the solutions fit your workflow, it can be cool.

http//quine.no

And we develop it because we need to, more than to try to take out the others.
We need it in our own ecosystem of hardware and software.