Welcome to our community

Be a part of something great, join today!

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

New Build 16 features...

TONIGHT !!!!
Aloha
-A
 
Ian look out =]

Once RedCine supports FinalCut XML, will Crimson still be useful for other things? I just use it for going between Final Cut and RedCine, but it seems like it could useful for other tasks as well.

You can expect that the basic workflow problems that Crimson solves would eventually be solved by the full quality Quicktime codec or by R3D support in Color. I'd use those things if they were available and up to my standards of quality and control.

Let's just say, all this stuff happening ain't no surprise.

Yet deep in the lab, something else is cooking :shifty:

IBloom
 
You can expect that the basic workflow problems that Crimson solves would eventually be solved by the full quality Quicktime codec

How so? Do you mean a solution could be cutting a medium proxy in Final Cut, then reconnecting with Full quality proxies which were corrected with Red Alert?


Yet deep in the lab, something else is cooking :shifty:
nice =]
 
This is an extremely pertinent question! To some extent in a scenario where the quality is decent enough AND you can go to REDALERT! and go back to the camera for playback... it would make sense to buy an extra RED body just to strap it on a Kona card in an editing suite just for the ability to output realtime dailies. (Aka. Extra RED body VS render farm + redline mayhem...)

Or is it me and my compulsive jerryrigging acting up again...

EDIT : Typos

Yep, this is what I was thinking. So far no noise on this from Red senior officials regarding quality. So, anyone? Dual link HD-SDI out of camera to dual link HD-SDI input on Bluefish/Kona/Whatever to DPX straight to disk array?

Quality when compared to software transcode?

Jim? Jarred?
 
I have a few Red kit rentals over the next week and I'm assuming I should steer my clients away from Build 16 until they can actually process it somehow. Correct?

I just want to make sure my clients are doing the right thing - right now, that seems like sticking with Build 15 for a couple more weeks. Can I get an Amen from Rob/Jarred/Jim?

It is an early BETA release, it's not meant for production work! If you must then I'd advice you to test it thoroughly beforehand so you know how it works, what has changed and what might not work.

RED Alert! and REDCODE QuickTime codec will be first and REDCINE & REDline will follow shortly.
 
Is it possible to control when the codec uses the full quality render?

Is it possible to, say, edit an _M proxy in Final Cut, but on render have those files render from the 4K layer to the sequence resolution (for e.g. 1080)

Is playback performance of the proxies improved (in QT or FCP)?

Thanks! Looking forward to this release...
 
Right - just confirming that there will be no way to actually use/process Build 16 upon its release in beta.

Build 15 it is then . . .

Thanks

Not on a PC. On a Mac you can use RED Alert. I assume this is what you mean?

Just trying to clarify for other users on here.

Ben
 
you would be surprised if you knew how much work Jim personally put into the development of build 16.. He outlasted us many of nights....



Jim & Red Team,

Thanks for burning the midnight oil to bring us Sweet 16!

Your work ethic, commitment to quality and dedication has set a new standard for camera companies!

P.S. When you butted heads with a certain camera company at NAB 2007 over line jumping you showed us what you were made of!!



Dave
 
* Addition of Pre-Record (10 sec or 30 sec loop) mode.

Great for wildlife shooting !! Not to speak of all the rest... Now, Jim and Red team, pleeease... a sleep-mode or whatever power saving function you may think of !!!
 
How so? Do you mean a solution could be cutting a medium proxy in Final Cut, then reconnecting with Full quality proxies which were corrected with Red Alert?
Well no, that's still a alot of work to do manually. In comparison to accessing R3D files directly their isn't a tremendous advantage to using the Full QT codec, we'll have to see. I'd rather skip quicktime and go straight to the source. Hmmm...
I think it depends on a lot of things. Red workflow is all about choice, that's why I like it. The more tools the better.

IBloom
 
Yip, what a deal. I just went and ordered me another one. Waiting for a serial number, it'll be interesting to see what number they are at.

Congratulations! I think they are just below 5000 now. Will be interesting to see what happens once 16 is a release version...

Also, with both the Birger and the Universal Mount now shipping, I'm sure that demand will not exactly decrease.

Go Red, go!:w00t:
 
User Buttons

User Buttons

Very excited by all the new features in Build 16, especially Programmable User Buttons.

Quick question:

Is FALSE COLOR one of the options available for assigning to the USER BUTTONS?

A lot of people (including ourselves) were really hoping for this... did it make it in?
 
User keys

User keys

Very excited by all the new features in Build 16, especially Programmable User Buttons.

Quick question:

Is FALSE COLOR one of the options available for assigning to the USER BUTTONS?

A lot of people (including ourselves) were really hoping for this... did it make it in?

Yes, sir.
 
Very very nice release!

The QT codec does seem to exhibit some problems with _F and _H sizes.
Here is a 4k 16:9 _H proxy in two different apps:
proxi.jpg
 
Back
Top