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 :)

RELEASED: RED ADOBE CS4 INSTALLER (v1.3.0)

My understanding is ColorFinesse is 32-bit floating point and it worked fine when I did a Cineform trial of a 2K timeline from converted .R3D files. Haven't encountered a 1080 ceiling to date (I'm on PC so can't speak about the Mac version of CS4 and Finesse). I'm testing the CS4/Red Plug-In/ColorFinesse combo right now. With the new Adobe plug-in I'm also digging the way the four discreet channels of Red One recorded audio appear on the timeline just like the Quciktime Proxie/Final Cut Pro method. It all seems to be coming together now.
 
Gunleik Groven said:
Hm. So what I read about a 1080/8-bit limit for premiere isn't true?
Because I can't use that.

I would have guessed something in AE...
Click to expand...

it says you can't render previews bigger than 1920x1080. you can use color finesse or magic bullet looks or wathever, and then render out to the format of your choice. for 4k outputs they recomend using AE for rendering. premiere can work at 4k 32 bit floating point, although you won't be able to render previews bigger than 1920x1080, it doesn't have an intermediate codec for sequences bigger than 1080.
BTW MB looks, CS4 and .r3d works simply amazing. the results looks great although i don't know if the plugin works in more than 8 bit inside premiere.
 
Priyesh P. said:
All of those "thank you" notes are littering the space, could you people just restrain yourself on issues, problem fixing and general information???
Click to expand...

The developers (Adobe & myself) definitely appreciate the thank you notes as well! There's a lot of hard work that went into this!

Some notes:

1) at the moment you cannot control any decoding parameters other than the ones in the global preferences dialog (decode resolution, quality, etc.). Other settings like ISO and white balance will be made available soon. For now it uses whatever the default was that was set in camera

2) as far as I understand the 1080p limitation is for preview only because the default preview codec is an MPEG codec. If you have a codec installed that can do higher resolutions than preview at higher resolutions should also work. You can output up to 4K in Premiere

3) the REDCODE importer supports both 8-bit as well as 32-bit float (see the settings dialog)

4) to the person asking about audio boards: it doesn't change anything for post, audio is still recorded in the R3D files (the QuickTime reference files simply point to the R3D files to get the video & audio)

5) don't forget to install Premiere Pro 4.0.1 and After Effects 9.0.1 updates :)

6) we're working on exciting stuff for this new workflow including full control over all decode parameters, better R3D browsing, metadata integration and control over decode resolution. This is just the first release, much more to come!

HTH
 
Rob & Co
Congratuøations!!!

It's fun that it looks like FCP/Color have one half of the equation handled, and Adobe has the other.

I'll test the Adobe thingy when the metadat is fully available. They're key to the RAW images, as is how the signal-chain is treated after the developing stage.

That not intended as a diminuation of your great achievement, just that I'll wait untill all the pieces are there.

Thanks for your answer!
 
Rob,

Thank you and all the development team at RED and Adobe. It looks like you've nailed this workflow. And there's more to come!

Congratulations on a job well done.

(Sorry for littering! ;-))
 
Gunleik Groven said:
Rob & Co
Congratuøations!!!

It's fun that it looks like FCP/Color have one half of the equation handled, and Adobe has the other.

I'll test the Adobe thingy when the metadat is fully available. They're key to the RAW images, as is how the signal-chain is treated after the developing stage.

That not intended as a diminuation of your great achievement, just that I'll wait untill all the pieces are there.

Thanks for your answer!
Click to expand...
I'm in the same boat. I'm excited that things have progressed to the point where R3Ds are being accessed natively, but control over RAW metadata is crucial for me. That's the thing that got me excited about the Color workflow. I'll wait this out and see how it develops. As more features get enabled I'll jump on board.
 
So it is true, i'm the only one who is:
- fully updated
- editing like a breeze on a mbpro
- unable to reopen a saved project: "this project contained a sequence that could not be open. No sequence preview preset file or codec could be associate ith this sequence type"
 
Richard Darge said:
Do people notice a big difference in playback speed/quality when compared to using the M proxy files in FCP? I'm about to make the jump to Premiere & am curious about performance.

Also, being somewhat of an AE noob, what are people using for Color Correction? Colorista?
Click to expand...

Hey Richard,

I've used AE for almost two years now. It's got similar color correction tools that photoshop has to offer, I've used this EXTENSIVELY to grade my shots, including levels, curves, hue/saturation. I find many people CC their stuff differently, but this is what works best for me.
 
Vladimir Eugene said:
How does Adobe's ColorFiness compare to Apple's Color?
Click to expand...

ColorFinesse is not an Adobe application but a third-party plug-in by Synthetic Aperature. It was used to color grade the feature film Dust To Glory a few years back via the Cineform intermediate codec. Some say Finesse is like having a Davinci suite, without the cost. For me it blows anything else I've tried out of the water and the 32-bit float is a huge plus.
 
How do I go about get saturation to work? I've tried the Change Color effect and I'm not seeing any changes to the clip. My format is 4k. Resolution quarter in a 1k sequence.
 
Congratulations to the Red and Adobe teams ! Finally you made it...

I don't have the minimum system requirements and just gave a fast try to it but it seems to work ok on a XP SP2, 2 GHz, 4 GB memory system. I can edit realtime with the 1K settings.

You really made something great here...

Jean-Charles
 
Paolo Tinari said:
Everything is updated.
Reinstalled everything a second time and still the same problem.
Am i the only one here facing this?
Click to expand...

Can you check something for me:

If you navigate to your Adobe Premiere Pro folder, right-click the app icon & choose 'show package contents', can you verify if the following file exists:

/Contents/Settings/EncoderPresets/SequencePreview/795454D9-D3C2-429d-9474-923AB13B7018/I-Frame Only MPEG.epr

Also, as a test, can you create a new sequence, select one of the RED presets, and then click over in the 'New Sequence' dialog to the General tab & tell me what Preview File formats are available?

(See attached screen shot)

(If you want to experiment, if you don't have the MPEG preview option available, try creating sequence with QuickTime instead as your selection, & see if you can save & reload this as a sequence type. The only thing you would lose is the ability to create MPEG preview files of your timeline.)
 
Kristin Stewart said:
I don't have the minimum system requirements and just gave a fast try to it but it seems to work ok on a XP SP2, 2 GHz, 4 GB memory system. I can edit realtime with the 1K settings.
Click to expand...

It's more a recommended system for serious work :) Other systems will work fine, but may not have received as much testing etc.
 
Let me say for a Beta the plug-in rocks and is looking in very fine form. Great work.

It's probably just a buried setting or switch somewhere but I'm not getting the ColorFinesse color-corrections I make to the .R3D files in Premiere to "bake" into the final render from the render queue. The corrections appear fine in the preview monitor. Any suggestions? Will keep testing to see if I can find the solution.
 
Kristin Stewart said:
I don't have the minimum system requirements and just gave a fast try to it but it seems to work ok on a XP SP2, 2 GHz, 4 GB memory system. I can edit realtime with the 1K settings.

You really made something great here...

Jean-Charles
Click to expand...

First of all, thanks a lot for the people involved in this great plugin!

Now I'm trying to test this stuff in a slow pc, not too far from the one Kristin S. has just described. Which setup could I try, like the slowest configuration available to find a good flow not worrying about quality, just for previews purposes.

I tried to create a 1k sequence with the source settings set to a 16th quality, but the image look smaller than the video window. I got confused somewhere in the process.


The thing is: lately we were thinking around here about this: if we wanted to have an instant preview of takes during shooting, maybe cutting and putting together a couple of images, it seemed that we had to go with a mac for the final cut option to use the quicktime previews. There's no PC alternative for that, or is it and we've missed something? Now if we can have a way to make a quick edit (I insist, only for preview purposes, just checking quick things) with a windows humble notebook with the premiere in it, that would be soooo great.

So, as you can see, I'm in the need of some clarity... any bit of light will be very welcome!! =)


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