RELEASED: Beta Build 21 Firmware (v21.3.1) [Archive]

View Full Version : RELEASED: Beta Build 21 Firmware (v21.3.1)

Brent@RED

11-10-2009, 09:26 AM

The latest BETA version of RED ONE camera firmware has been posted on www.red.com/support - Build 21 RED ONE Beta Firmware, v21.3.1 (password-protected).

Changes since last beta Build 21 release (v21.2.1):
* Bug affecting adjustment of Ch1 / Ch2 Volume from USER KEYS resolved.
* Bug affecting adjustment of Ch1 / Ch2 Volume from RED-EVF menus resolved.
* GUI timecode display no longer counts in whole seconds when not in RECORD.
* OPACITY of LOOK AROUND are is now adjustable in MONITOR / CUSTOM menu.
* WRITE LOG label moved to SYSTEM / SETUP / MAINTENANCE menu
* Added REPEAT FRAME flag to VITC-2 HANC in HD-SDI PVW output.
* Added IN-RECORD flag to VITC-2 HANC in HD-SDI PVW output.
* Added CLIP NAME as metadata to VITC-2 HANC in HD-SDI PVW output.

ALWAYS READ ALL INSTRUCTIONS CONTAINED IN THE DOWNLOADED INSTALLATION FILES BEFORE PROCEEDING.

WARNING: AS THIS IS A BETA BUILD, THIS FIRMWARE IS RECOMMENDED FOR PREVIEW AND TESTING PURPOSES ONLY. IT IS NOT RECOMMENDED FOR USE ON COMMERCIAL PRODUCTIONS.

NOTE: After upgrading firmware, a BLACK SHADING calibration should be performed. Detailed instructions are contained in the Operations Guide.

If you have any questions or feedback, please contact RED Technical Support at www.red.com/support.

Please do not reply directly to this email.

Bastiaan Houtkooper

11-10-2009, 11:03 AM

Brent can you shine some light why you are adding flags to VITC-2 HANC.
what does it do? Does it help the stability of the signal so we can use the BlackmagicHDlinkPro again with the RED?

Stuart English

11-10-2009, 12:10 PM

Flags in HD-SDI have nothing to do with stability...

They allow capture cards to toss out repeated frames that you must generate in order to transfer a 24 fps image over a 60 fps HD-SDI link.

Bastiaan Houtkooper

11-10-2009, 12:11 PM

Thanks, learning everyday.......

Laco Zamba

11-10-2009, 02:08 PM

OPACITY of LOOK AROUND are is now adjustable in MONITOR / CUSTOM menu

This is great feature for me. Thank you, RED team.

Kwan Khan

11-10-2009, 02:12 PM

Thankx....

Andrae Palmer

11-10-2009, 02:41 PM

OPACITY of LOOK AROUND are is now adjustable in MONITOR / CUSTOM menu

This is great feature for me. Thank you, RED team.

Thanks for posting this. The exact menu map is MONITOR / FRAME GUIDE / CUSTOM

Tim Sutherland

11-10-2009, 03:01 PM

Flags in HDSDI plus lookaround opacity means that you could record the HDSDI feed. Not going to get the best image that way, but it makes for a better studio option.

Mark L. Pederson

11-10-2009, 05:25 PM

You will want to check out the little video I'm going to post in this thread tomorrow.

Tim Whitcomb

11-10-2009, 05:33 PM

You will want to check out the little video I'm going to post in this thread tomorrow.

subscribed!

and Thanks Stuart, don't know if anyone else is noticing, but updates are and releases are coming faster than ever. Keep up the great work RED!

Brent@RED

11-10-2009, 09:08 PM

You will want to check out the little video I'm going to post in this thread tomorrow.

Now that you have my attention...

BC

Brent@RED

11-10-2009, 09:11 PM

subscribed!

and Thanks Stuart, don't know if anyone else is noticing, but updates are and releases are coming faster than ever. Keep up the great work RED!

I notice, I post the build each time, haha. But in all seriousness, the firmware dev team rocks and a ton of props goes to two entities. One, to the people on this forum who provide great and constructive feedback/requests. Two, to Stuart, who wrangles all that feedback and pushes it to development. No easy task.

BC

Stuart English

11-10-2009, 11:08 PM

Martin Weiss

11-11-2009, 01:30 AM

Thanks guys […] please send us any new ideas for consideration :-)

http://www.reduser.net/forum/showpost.php?p=505127&postcount=6 :)

Antony M

11-11-2009, 02:28 AM

I'm sure we haven't exhausted optimization opportunities just yet, so please send us any new ideas for consideration :-)

1. I would still like a change to require confirmation before powering down the camera.

2. Or a quicker boot up time (10 seconds??)

3. Allow change of Time Base without needing to reformat drive (e.g. change from 24fps to 25fps)

Paul Leeming

11-11-2009, 03:53 AM

Worked fine on a production today, had to update on set due to previous build issue with Birger mount, happy to report that 21.3.1 with latest Birger firmware is smooth sailing all the way!

Thanks for the continual feature growth Red!!

Paul

Laco Zamba

11-11-2009, 02:04 PM

I cannot change opacity of look around area.
I have "none available" and cannot change this value.

What's wrong?

Ruairi Robinson

11-11-2009, 03:33 PM

Thanks guys, kudos is definitely due to both our customers and our camera firmware team.

In Build 21 we tried to address as many of your feature requests as we could, and squish some minor but annoying bugs.

I'm sure we haven't exhausted optimization opportunities just yet, so please send us any new ideas for consideration :-)

( And if Mark's video is what I think it might be, its going to be pretty cool .... )

Would it be possible to make anamorphic mode use full sensor height?

(so we don't have to crop as much)

This may not be the right place... but thought I'd throw that in as well :)

Best,
R.

Frank Cueto

11-11-2009, 03:55 PM

And a 1.33 aspect anamorphic mode would rock for people that want to do anamorphic work with Hawk 1.33 lenses.

Blair S. Paulsen

11-11-2009, 04:10 PM

And a 1.33 aspect anamorphic mode would rock for people that want to do anamorphic work with Hawk 1.33 lenses.

I believe the 1.33 Hawks allow you to shoot Scope (2.35, 2.39 or 2.40 to 1 depending on variant) onto the 1.78 to 1 (16x9) active sensor of 4096 by 2304. Due diligence recommended but it should work a charm.

Cheers - #19

Frank Cueto

11-11-2009, 04:26 PM

Yes they do. But the tools for onset monitoring and everything else can't compensate for the 1.33. In red anamorphic world is 2:1 or nothing :-(

I am looking into using the hawks so we can record an anamorphic image on a 16:9 sensor to get the best out of the camera.

Mark L. Pederson

11-11-2009, 08:25 PM

Now that you have my attention...

BC

Sadly I didn't have time today to make the little demo video I wanted to make as I'm racing off to New Orleans where Offhollywood's cameras will roll on our first 3D feature this weekend. Here's a description of what I wanted to show -

We tested the pre-release of this build by adding auto record support, valid frame recording as well as CLIP NAME support into QTAKE Advanced Video Assist. (www.QTAKEHD.com)

What does that mean?

Well ... QTAKE is an advanced dual camera video assist system which runs on a MAC - 2 cameras in 2D or one 3D rig using a single Kona 3 card. Further, you can "link" multiple Qtake systems together and record up to 18 cameras from one UI. There is a studio feature using this to record and playback from 3 3D rigs with a single video assist operator.

Now ... using the new firmware - QTAKE knows when each camera records and stops. So ... Qtake now records and stops both streams automatically. When the camera rolls ... Qtake rolls.

The valid frame flag is really amazing. If you shoot 23.98 - QTAKE will record 23.98 - the exact same frames as the R3D with the exact same timecode.

If you shoot ANY framerate up to 60 - QTAKE will record and playback that clip exactly as the camera does. If you RAMP up to 60fps - QTAKE will record (and play back instantly) that ramp.

QTAKE also displays the FULL CLIP NAME while recording AND gives you the option to have the quicktimes Qtake records be named the same as the clipname with the correct reel/roll/tape number in the QT header as well.

All over a single SDI cable. This is my favorite firmware build EVER. Huge thanks to Stuart for sticking with it and to Greg Milneck for helping us with additional QTAKE alpha/beta testing with the pre-release firmware.

I will get around to making some videos soon and get them up at digitalcinemalessons.com

Greg M

11-11-2009, 08:30 PM

and this is truly amazing to see in person...Thanks Stuart (and Mark and Vlado) for making this happen.
Now when our Video Assist op falls asleep on set, we are assured we wont miss a take.

and watching 60fps playback in HD at 60fps on a video assist system in realtime, instantly is also pretty sweet.

Laco Zamba

11-12-2009, 02:13 AM

I cannot change opacity of look around area.
I have "none available" and cannot change this value.

What's wrong?

I solved my problem.

When I installed newest beta I imported my profile from SD card which I exported from build 20.1.6 and then I could not set Opacity.
Then I reseted my custom settings and Opacity is working fine.

Jay A. Kelley

11-12-2009, 05:30 AM

I think the feature Mark is speaking of also has an effect on sound recorders such at the Cantar... They can now be set to start/stop recording when the camera operator engages the camera.

This was a feature we begged for a long time ago.. Glad to see it now.

Jay

Jay A. Kelley

11-12-2009, 05:34 AM

With all the HUNDREDS of bug fixes and little features that have been added to the R1 over the last couple years, my question is this:

Is there going to be a way to port over all these features into the new cameras?

I'd hate to think all this work being done on the R1 would have to be completely started over on the Epic / Scarlet...

(By this statement I do not mean we'll have to wait "years" for a good camera Op system, but more concern for the software guys at RED who would have to re-write what are by now tens of thousands of lines of code)

Jay

Paul Leeming

11-12-2009, 06:49 AM

I solved my problem.

When I installed newest beta I imported my profile from SD card which I exported from build 20.1.6 and then I could not set Opacity.
Then I reseted my custom settings and Opacity is working fine.
Saw this too as I did the same thing after updating. Thanks for the tip on how to fix it (I just said to myself "RTFM" and put it off for later as I personally don't mind the opacity as is).

Cheers,

Paul

Jay A. Kelley

11-12-2009, 07:06 AM

Bummer.. I was wrong about the recorder's start/stop... It has nothing to do with the SDI out, but more the TIMECODE.. It has to send RECORD RUN out and that's what turns the recorders off an on....

STUART?! How about this for a suggestion!

Jay

Stuart English

11-12-2009, 07:10 AM

David Rasberry

11-12-2009, 07:57 AM

Is what you want Timecode in the HD-SDI (SDI), or what we call "Edge Code" as the timecode output of the 5-pin analog timecode connector?

i.e a timecode signal that starts incrementing when the recording starts, stops when recording stops...

In general, you need to support this start/stop mode of timecode recording AND a freerun mode where devices are synced to a master clock and timecode increments independent of whether the camera is recording or not. On some types of multi-camera shoots, camera and audio recording may not be starting or stopping at the same time, but will need to sync to a continuous timecode reference.

Jay A. Kelley

11-12-2009, 03:31 PM

Is what you want Timecode in the HD-SDI (SDI), or what we call "Edge Code" as the timecode output of the 5-pin analog timecode connector?

i.e a timecode signal that starts incrementing when the recording starts, stops when recording stops...

We need Edge Code (Record run) as the timecode output of the 5 pin analog timecode connector. This will send the Cantar what it needs to start and stop recording automatically (The same with sound devices.)

Jay

Milan Spasic

11-12-2009, 04:05 PM

The lines from the monitor - gone.

Look around transparency - awesome feature.

Cheers Red Dev Team! :cheers2:

Mikael Lubtchansky

11-13-2009, 06:33 AM

I'm sure we haven't exhausted optimization opportunities just yet, so please send us any new ideas for consideration :-)

One could always ask for more hehehe...

Now that you've implemented the custom values for look around opacity I'd love to have 25 % and 75 % enabled... right now I'd stick with 50% as 0% is a bit disturbing to frame with and 100% is nice and can be useful to "videoguys" who like no lookaround area (or for those who want to record the HD-SDI output).

25% would be great for night/indoor scenes and 75% would be useful in bright daylight exteriors.

Mikael Lubtchansky

11-13-2009, 06:57 AM

with previous builts pressing the pixel for pixel zoom during recording had no action (as it only works in between takes)

On latest beta it doesn't zoom in or change the image (of course) but it does removes lookaround/markers and displays 'image zoom' along with the X in the middle as if it was zoomed in.

minor display bug not affecting recording

(btw is this an appropriate place to send feedback/bugs or shall we use a specific email for those ?)

Stuart English

11-13-2009, 10:28 AM

Mikael Lubtchansky

11-14-2009, 12:28 AM

I was using the latest beta v21.3.1
project setting was 4.5K redcode 42.
I'll do more tests today at other resolution/settings to narrow the problem down.

Manuel Wenger

11-14-2009, 04:22 AM

I tried to download the new firmware today, but as the download starts, i´m getting the manuals downloaded instead. Can u check if the link is wrong ?

thanks
Manuel

Cüneyt Kaya

11-14-2009, 04:49 AM

frameguides while playback would be great

Michael LAGERWEY

11-14-2009, 05:47 AM

Idem for me... ! Only the manual...
Can U check the link ?

Tx

Ramesh Jai

11-14-2009, 06:15 AM

Look around transparency options are great.

Has anyone asked for transparency options for different display guides (16:9, 3:4, etc.) That will be great for me. Thanks

Barry Dycus

11-14-2009, 02:05 PM

I tried to download the new firmware today, but as the download starts, i´m getting the manuals downloaded instead. Can u check if the link is wrong ?

thanks
Manuel

I am having the same issue. Can someone help?

Stuart English

11-14-2009, 04:32 PM

Try downloading again Barry... the files were incorrect on the web site.

Barry Dycus

11-15-2009, 05:40 AM

Thanks Stuart

Mikael Lubtchansky

11-15-2009, 12:00 PM

Stuart
so far the bug seems to appear only on 4.5WS or 4K ANA here. I tried at 24/25 fps and it was similar. 4K HD and 4K 16/9 were OK. Let me know if you can't reproduce it on your side I will investigate more tomorrow if needed... Downgrade firmware, reinstall etc to see if it is persistent.

Stuart English

11-15-2009, 02:25 PM

Yes, I see it on 4.5K too. Let me check..

jimhare

11-15-2009, 03:14 PM

Hey Stuart,

I shoot multicam, so shoot 6-7 REDs simultaneously for 90 minute takes.

The feature that would mean the most to us is the ability to check focus (1:1) while recording. I understand the danger of some users getting confused by this, but it could default to OFF and have a multi-step procedure to activate.

Is there a technical reason this can't be implemented or is it just the danger of confusing the operator?

I'm sure we haven't exhausted optimization opportunities just yet, so please send us any new ideas for consideration :-)

Stuart English

11-15-2009, 05:45 PM

Yeah, that is actually the "bug" being discussed above....

Tommy Schell

01-29-2010, 02:39 PM

Sadly I didn't have time today to make the little demo video I wanted to make as I'm racing off to New Orleans where Offhollywood's cameras will roll on our first 3D feature this weekend. Here's a description of what I wanted to show -

We tested the pre-release of this build by adding auto record support, valid frame recording as well as CLIP NAME support into QTAKE Advanced Video Assist. (www.QTAKEHD.com)

What does that mean?

Well ... QTAKE is an advanced dual camera video assist system which runs on a MAC - 2 cameras in 2D or one 3D rig using a single Kona 3 card. Further, you can "link" multiple Qtake systems together and record up to 18 cameras from one UI. There is a studio feature using this to record and playback from 3 3D rigs with a single video assist operator.

Now ... using the new firmware - QTAKE knows when each camera records and stops. So ... Qtake now records and stops both streams automatically. When the camera rolls ... Qtake rolls.

The valid frame flag is really amazing. If you shoot 23.98 - QTAKE will record 23.98 - the exact same frames as the R3D with the exact same timecode.

If you shoot ANY framerate up to 60 - QTAKE will record and playback that clip exactly as the camera does. If you RAMP up to 60fps - QTAKE will record (and play back instantly) that ramp.

QTAKE also displays the FULL CLIP NAME while recording AND gives you the option to have the quicktimes Qtake records be named the same as the clipname with the correct reel/roll/tape number in the QT header as well.

All over a single SDI cable. This is my favorite firmware build EVER. Huge thanks to Stuart for sticking with it and to Greg Milneck for helping us with additional QTAKE alpha/beta testing with the pre-release firmware.

I will get around to making some videos soon and get them up at digitalcinemalessons.com

Hi,

we make a portable recorder, nanoFlash, and some of our customers use our recorder with the SDI output of the RED. We are interested in adding the above-mentioned features into our recorder, with the record flag, valid frame flag, and clip name flags accessible to our recorder to be in sync with the camera's record. Please let me know if this possible, or if any nanoFlash users are interested in this.

Thanks, Tommy Schell

Caglar Kanber

02-08-2010, 09:30 AM

Hi,

we make a portable recorder, nanoFlash, and some of our customers use our recorder with the SDI output of the RED. We are interested in adding the above-mentioned features into our recorder, with the record flag, valid frame flag, and clip name flags accessible to our recorder to be in sync with the camera's record. Please let me know if this possible, or if any nanoFlash users are interested in this.

Thanks, Tommy Schell

Hi all,
As some of you might know, the Nanoflash is a brilliant product. We have 3 of them which we use as video assist devices with our R1 cameras. It is affordable, high quality and simple to use which makes it a great video assist device that uses the same recording media as R1, CF cards. It could record in various bitrates and formats from 18Mbit/sec to 280Mbit/sec in MPEG, MOV and native MXF for Avid.

With the introduction of build 21, we thought that if the Nanoflash could read and interpret the "flags" in the VITC signal over HD-SDI output of R1, then it could generate the MXF offline files for Avid on the fly.
With the record flag, Nanoflash would record and cut in sync with R1, with the VITC timecode it would lock to that of R1, and with the help of valid frame flag, it would record in the exact frame rate of R1. If it could also read the clipname flag, then it would append the clipnames from R1 as metadata to its files in sync.

Just think of it, with the Nanoflash recording in perfect sync with R1, you could have your offline MXF files for Avid in hand, just as the set wraps! No transcoding, no ingesting. You just load the clips from the nanoflash and start editing in Avid right away. Later you pull your original R3D files from the EDL generated by Avid.

Wouldn't this be great?
Plus, it is still a great video assist that records and cuts in sync with RED!

We have talked with Tommy from Convergent Design to see if they could implement the necessary features to read the "flags" introduced in build 21, just as the guys from Qtake did it. Tommy replied that he tried to contact RED about it but unfortunately his inquiriy remained unreplied.
I believe that if there are enogh RED users to demand this feature, then RED and Convergent Design may get along to come over with this.