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 21 Firmware (v21.3.1)

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.
 
Brent@RED said:
Now that you have my attention...

BC
Click to expand...


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
 

Attachments

  • MVI_0571.jpg
    MVI_0571.jpg
    59.7 KB · Views: 0
Last edited:
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.
 
Opacity is OK

Opacity is OK

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

What's wrong?
Click to expand...

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.
 
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
 
This brings up a good question

This brings up a good question

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
 
Laco Zamba said:
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.
Click to expand...
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
 
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
 
Timecode

Timecode

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...
 
Stuart English said:
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...
Click to expand...

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.
 
Stuart English said:
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...
Click to expand...

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
 
more custom lookaround values...

more custom lookaround values...

Stuart English said:
I'm sure we haven't exhausted optimization opportunities just yet, so please send us any new ideas for consideration :-)
Click to expand...

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.
 
minor display bug

minor display bug

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 ?)
 
Build 21

Build 21

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 ?)
Click to expand...

Not on my camera it doesn't... what build are you using Mikael?

And what resolution are you recording at?
 
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.
 
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
 
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
 
You must log in or register to reply here.
Back
Top