Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Adobe/SDK Update

D

Deanan

Red Team
Joined
Jan 19, 2007
Messages
3,844
Reaction score
0
Points
0
Quick update on SDK and Adobe support:

The alpha testers found a few bugs that prevented us from releasing today.
SDK is very very close with just a few small bugs to squash.
We will start emailing out the SDK on Monday.

The Adobe importer has a few very annoying bugs that we'd like to clean up
before releasing. We are squashing these bugs ASAP to get it out quickly for release next week.

Thanks for your patience.
 
Deanan said:
Quick update on SDK and Adobe support:

The alpha testers found a few bugs that prevented us from releasing today.
SDK is very very close with just a few small bugs to squash.
We will start emailing out the SDK on Monday.

The Adobe importer has a few very annoying bugs that we'd like to clean up
before releasing. We are squashing these bugs ASAP to get it out quickly for release next week.

Thanks for your patience.
Click to expand...

Although I'm super disappointed that I have to wait a few more days, I'm glad to hear about the work being done on it. Can you give us some details on performance in Premiere and Ae? on what kind of machines are you running it on? How much does the GFX come into play?
 
The first release is more a functional first step rather than a performance oriented release. We'll be growing the functionality tremendously over the next many months especially as things evolve from CS3 to CS4.
 
I'll do another update on monday about where we are at.
 
Please take your time and get this right. It is a huge development.

Either way, there are going to be some bugs discovered after it is released... let's try and make as few as few possible.

Looking forward to the SDK and ADOBE support!
 
rgdfilmsRED said:
Psh.. Probably 5 years from now..

Apple dropped the ball on this one, big time. Kudos to Adobe. Can't wait..
Click to expand...

Did they really drop the ball? Seems like RED is building this plugin or R3D importer not Adobe. Am I wrong?

Either way I'm happy.

\v
 
Vincent S said:
Did they really drop the ball? Seems like RED is building this plugin or R3D importer not Adobe. Am I wrong?

Either way I'm happy.
Click to expand...

Not sure who's building it, but Jim has said Adobe is offering real support. I'm a little confused by the "importer" idea. I thought this was going to be native support. What's the importer do if it's not transcoding?
 
joelnet said:
Not sure who's building it, but Jim has said Adobe is offering real support. I'm a little confused by the "importer" idea. I thought this was going to be native support. What's the importer do if it's not transcoding?
Click to expand...

There are different levels of "native" support. Having an "importer" doesn't necessarily mean transcoding as in the case of FCP. It could just mean that the RED plugin gives an Adobe product the ability to decode and debayer any frame of an R3D file it chooses to an RGB or perhaps Raw image. It could also mean that the Adobe product has a choice of qualities to facilitate realtime performance. It could also mean transcoding ;)

We'll have to see.

IBloom
 
joelnet said:
Not sure who's building it, but Jim has said Adobe is offering real support. I'm a little confused by the "importer" idea. I thought this was going to be native support. What's the importer do if it's not transcoding?
Click to expand...

If you take a look in the Plug-ins/Format folder of After Effects, you will see a lot of plugins that do just that, import different file formats.

It doesn't have anything to do with the "nativeness" of the different file formats. For instance, PS Layer Import.AEX gives you the option to load Photoshop files in layers. And that is pretty native.

Transcoding in AE? Over my dead body... ;)

Fred
 
Are these tools available?

Are these tools available?

I have to admit that I'm not up on After Effects 7 and I've never once used Premiere.

That said, I use Photoshop's RAW feature almost daily. I'm curious how similar AE's RAW tools are to Photoshops? And I wonder if a RED to Photoshop link is a possibility - since Photoshop can handle 16 and 32 bit files - and motion clips? There are several tools in there I would love to have that simply don't exist in Red Alert.

(Tools like:
Recovery,
Fill Light,
Blacks,
Hue-Saturation-Lum tools for each of the color channels that only with the selected color channels rather than across the whole image)

Then again, if these tools are present in AE (along with Rotospline matte-able layers), etc - I may have to add AE to my toolset.

-Glen
 
rgdfilmsRED said:
Psh.. Probably 5 years from now..

Apple dropped the ball on this one, big time. Kudos to Adobe. Can't wait..
Click to expand...

You know... People keep saying things like this, but I can only think of one NLE that, to this very day, supports editing .r3d proxies. Not only that, but it pretty much supported editing proxies from day one! There isn't another NLE with that kind of RED support, even today. We'd all like to have a complete solution to the native .r3d workflow problem, and considering how well Apple has supported RED in the past you'd be kind of foolish to think that a native FCS workflow will never happen.
 
I think we can credit the Adobe workflow to the fact that Adobe has had the right internals to support RAW workflow. FCP doesn't have it, so it's just easier to do it on Adobe probably.

Whether Adobe or Apple loves you more is pretty irrelevant. Apple still has a better interface, Avid even better in my oppinion. When you are generating a cutlist that is what matters right?

IBloom
 
joelnet said:
What's the importer do if it's not transcoding?
Click to expand...

Decoding? I think "import" just means load in a file, of whatever format, as others have mentioned. But I'm pretty sure it will at least be decoded to some working format like RGB or YCrCb, etc. Redcode natively stores data using wavelet compression- I don't think anyone's software operates on the wavelet basis vectors directly without decoding them, and if you want the full quality output you'll want it debayered as well.
 
jbeale said:
I think "import" just means load in a file, of whatever format, as others have mentioned.
Click to expand...

Makes sense. If we could import, edit and color correct the 1K stream and then render fully debayered from the 4K when the project is done I think we'd really have a cool workflow. Basically an offline with an automatic online from the 1K stream to the 4K stream.
 
Deanan said:
We'll be growing the functionality tremendously over the next many months especially as things evolve from CS3 to CS4.
Click to expand...

So I'm guessing once we have CS4, we'll be able to edit redcode natively 64bit with 8GB plus memory?

D
 
You must log in or register to reply here.
Back
Top