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

I sense a strong presence in the force...

I hope soon so everyone can beat the hell out of it. thats the only thing that makes me happy about waiting until nov for my cam. you guys will have field tested the life out of it and whatever builds come before then. which I greatly appreciate
 
Jim just posted saying the build 16 would be within a day or two...
 
We still can't use Redcine with Build 16 though upon release, right? And once we go 16 we can't go back, right?
 
correct, but they would not release build 16 beta without a way to process
footage so I am sure redcine or at least red alert for b16 will be released at the same time.
 
Since 16 is essentialy code or software, why is it not possible to go back to an earlier build?

I can put Windows 98 on a Linux machine, or Os X 10.2 on a Panther system?

(no complaint here, and why would anyone want to go back; I am just curious about the technical side - after all a new build does not change the hardware...)
 
The build is a very complicated upgrade. No going back. You won't want to. RED Alert! is finished, REDCINE should be ready by the end of this week (or weekend). SDK work has begun. Build 16 is very stable (should be, we took so long!). I'd look for tomorrow or Wed. for the beta release.

Jim
 
Since I know nothing about this, how long would it take to do the SDK? Also, with the SDK that means that other companies like Apple, Avid, Adobe can create their own post tools for Red, yes? Will the SDK give people the opportunity to hack their Red, or is that something else?
 
Martin Weiss said:
Since 16 is essentially code or software, why is it not possible to go back to an earlier build?
Click to expand...

I'm guessing that the Build 16 package contains (and relies on) one or more firmware updates for some of RED's onboard components. Those updates probably aren't backwards compatible with the software from the Build 15 package, and why should they be? :wink:
 
You must log in or register to reply here.
Back
Top