Use Shake SDK to add native R3D support?

[michael zaletel]

Considering the openness and flexibility of Shake and the amazing Shake SDK, what would be involved in adding native R3D support (rather than through quicktime)?

We could work with the proxies then link to the 4K as final step. Shake is so versatile, you could practically use it as a 4K edit, composite and color system if you had to. I suppose this could be done by converting the R3D to 4K sequential Tiffs but the files would be HUGE.

[Dj Joofa]

Considering the openness and flexibility of Shake and the amazing Shake SDK, what would be involved in adding native R3D support (rather than through quicktime)?

We could work with the proxies then link to the 4K as final step. Shake is so versatile, you could practically use it as a 4K edit, composite and color system if you had to. I suppose this could be done by converting the R3D to 4K sequential Tiffs but the files would be HUGE.

Last time I was looking at Shake SDK it appeared that its an Effects API and not Import/Export API. But I have to double check that.

[Dj Joofa]

Last time I was looking at Shake SDK it appeared that its an Effects API and not Import/Export API. But I have to double check that.

Sorry, I was wrong, I checked back cursorily and found out that Shake SDK does have Data Import/Export Utilities. So you are right, Shooter.

[Sanjin Jukic]

Sorry, I was wrong, I checked back cursorily and found out that Shake SDK does have Data Import/Export Utilities. So you are right, Shooter.

Joofa,

would you be so kind and DIG something between Shake SDK and R3D.

Regards,

[Dj Joofa]

Joofa,

would you be so kind and DIG something between Shake SDK and R3D.

Regards,

The only thing that stops me is the RED's SDK, otherwise I can write an importer for Shake. I know R3D can be reverse-engineered to know its format but I may not like to do that.

For that matter I can write a native R3D importer for Adobe (Premiere and After Effects) also. That is why I have asked Red several times if their SDK or R3D format will be publicly available so that poor folks like me who are not "partners" can do some stuff. But never gotten an answer from Red One.

[Deanan]

We've announced before that an SDK will be available. You won't have to be a partner to use it.

Shake does have an import api. The shake api is one of the most annoying api's I've used.
Right after it is infiniband.

[michael zaletel]

We've announced before that an SDK will be available. You won't have to be a partner to use it.

Shake does have an import api. The shake api is one of the most annoying api's I've used.
Right after it is infiniband.

Hi Deanan:

I've only just begun to dig into Shake's SDK so I'm seriously interested in your real-world experience. When you say "annoying", what do you mean?

In your opinion, once the Red SDK is out, how many hours of coding (by an expert) would it take to write an R3D file-in node. Are we talking tens of hours , hundreds of hours, thousands of hours? Also, would it be fairly easy to add R3D export support once the import is written? I have a very experienced C-programmer on staff that would love a project like this but maybe I'm dreamin'.

I just think with R3D support in Shake, we could do just about anything that needed to be done at least until proxy support for R3D is introduced in more mainstream applications.

[Peter McCully]

We've announced before that an SDK will be available. You won't have to be a partner to use it.

Shake does have an import api. The shake api is one of the most annoying api's I've used.
Right after it is infiniband.

What about Fusion then? I am sure Eyeon would welcome R3D to their import options. Perhaps their api is a little more user friendly?