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: Beta Build 20 Firmware and RED ALERT!

Stewart,

Just to clarify here. A new RedAlert! download presumably means a new RedLine installation-- correct? Should I worry at all about my third party applications that call up RedLine behaving any differently?

Thanks
 
Tim Fassnacht said:
Just to clarify here. A new RedAlert! download presumably means a new RedLine installation-- correct? Should I worry at all about my third party applications that call up RedLine behaving any differently?

Thanks
Click to expand...

Monkey Extract (which uses REDLINE) gives me a warning that REDLINE is not a tested version, but allows you to continue. The results running through Qmaster worked same as before, and I noticed no problems.

Colin
 
BoouuuooM!!

Thanks team, wow!, what a soft update!

God save the RAW.
 
Yes, the new REDAlert package installs a new version of REDline.
When you render with the new REDline, at least white balance is different from previous versions.

In Clipfinder, currently neither the main window (proxy based) nor the loupe window (SDK based) show what you will get when you render. If you want to adjust look settings, you'll need to use REDAlert (CMD-R from Clipfinder).

Cheers,
Hans

Tim Fassnacht said:
Stewart,

Just to clarify here. A new RedAlert! download presumably means a new RedLine installation-- correct? Should I worry at all about my third party applications that call up RedLine behaving any differently?

Thanks
Click to expand...
 
Happy and excited to hear about the Build 20 Beta.

But ...

We're a rental house. As such, we can only rent out cameras with Release builds installed. RED's website states that Beta firmware is "not recommended for use on commercial productions," which means that for insurance liability we cannot use anything but a Release build.

So now that 20 is in Beta, how about a bit of progress on the Release builds? It's been about nine months now and it would be nice to see Build 18 graduate from Beta to Release.
 
Brent@RED said:
modified camera boot up sequence
Click to expand...

is it a step toward an optimized boot with faster startup time coming in the future ?

New built and color science looks awesome, well worth skipping directly to 20 :)
 
Hans-Georg Daun said:
Yes, the new REDAlert package installs a new version of REDline.
When you render with the new REDline, at least white balance is different from previous versions.

In Clipfinder, currently neither the main window (proxy based) nor the loupe window (SDK based) show what you will get when you render. If you want to adjust look settings, you'll need to use REDAlert (CMD-R from Clipfinder).

Cheers,
Hans
Click to expand...

Thanks Hans
 
RED Team, thank you very much for your work: start up time feels faster, picture quality is much better, a new camera again. I love my REDs, rolling and rolling and rolling. Only one thing I remarked: If I use the EVF, there is noise in the darks. It goes away, when I increase the brightness, but then the blacks doesn't match with the reality anymore. Anybody else the same effect?
 
Mitch Gross said:
Happy and excited to hear about the Build 20 Beta.

But ...

We're a rental house. As such, we can only rent out cameras with Release builds installed. RED's website states that Beta firmware is "not recommended for use on commercial productions," which means that for insurance liability we cannot use anything but a Release build.

So now that 20 is in Beta, how about a bit of progress on the Release builds? It's been about nine months now and it would be nice to see Build 18 graduate from Beta to Release.
Click to expand...

My thoughts as well, Mitch. I'd love to see the new color science and it's impact on the picture coming out HDSDI, but we have to wait until it goes to a release build before that happens.
 
Colin Hubick said:
Monkey Extract (which uses REDLINE) gives me a warning that REDLINE is not a tested version, but allows you to continue. The results running through Qmaster worked same as before, and I noticed no problems.

Colin
Click to expand...

In theory there shouldn't be anything that affects other apps that call redline.
 
in Build 20 the Phantom Power is still not retained across power cycles. It does stay on in the menu, but its not actually working. You need to disable it and put it on to actually enable it.
 
I'll be happy if we could get that green tinge to the HD-SDI ports to go away so that folks stop asking me why its green.

Thanks for the hard work!

Now I'll get back to Testing this bitch....

Do we know the support deadline?
 
Mitch Gross said:
So now that 20 is in Beta, how about a bit of progress on the Release builds? It's been about nine months now and it would be nice to see Build 18 graduate from Beta to Release.
Click to expand...

Same opinion. Had trouble with B17 so went back to B16: no problems here. But... I have 6 16GB CF cards aging uselessly for months waiting for a release build that solves those rebooting issues of B17!!!!
Guido
 
Just gave a quick run to build 20, the Redspace view isn't accurate in the Lcd (sorta of a mix between raw view in term of saturation and Redspace in terme of contrast) , as the rec 709 is perfect. I'll try again tomorrow, that build seems more than promising.
Red team, thanks for all that hard work.
Brice
 
Where did the iData go?

Where did the iData go?

I've been getting iData with my Birger/EOS on build 18. But, now, with build 20 the iData no longer appears. Just nothing, like nothing is connected. I noticed the read me file says iData no longer works with Cooke. Does this go for Birger/EOS as well? I hope not!
 
You must log in or register to reply here.
Back
Top