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

First days out: tips on working with the Raven

Trevor Meier

Well-known member
Joined
Jan 2, 2007
Messages
855
Reaction score
1
Points
0
Website
www.trevormeier.com
Just wrapped my first two-day shoot with the Raven. It's a great little camera. Here's a few tips on getting the best results from the little bird:

1. If you're using the v-mount expander and running audio to the camera, you're going to want strain relief on the audio cables. 1/8" jacks don't like any kind of pull on the cables. Use Velcro or a quick release cable to get the weight off the audio jacks

2. The crop sensor isn't as big a deal as I thought. We shot 4.5K widescreen and didn't really need to adjust our lensing and workflow. This was a surprise... I thought being on a tighter sensor would be more limiting. It wasn't (for us, anyway)

3. Power, power, power. The Raven's one significant weakness, in my view, is its power consumption. With the 4.7" MN monitor and the v-mount expander, it draws almost exactly 60 watts. This doesn't change no matter how you configure the camera - R3D + ProRes, ProRes-only, high framerate etc. It seems like all of the features of the camera are on, all of the time, and battery life suffers massively for it. I really wish Red could do some power management wizardry to shut off functions that aren't being used to get the camera down into the 25-30W range (but if I have to pick one thing I'm willing to live with vs losing for eg ProRes recordings, I can live with this)

4. R3D+ProRes is amazing. Two days of shooting and our total data was less than a terabyte, including edit-ready ProResLT files which totalled about 160GB - a totally manageable size. I'm deeply impressed. This is almost half the amount of data I'm used to working with shooting in 6K with my Epic Dragon.

5. You'll want to turn off ProRes for any high framerate work beyond about 48FPS. The ProRes recording starts eating to much bandwidth and the R3D recording suffers as a result. I wish it was an option to turn this off directly from the compression menu on the main screen. This would really speed things up while switching back and forth instead of having to dive into the menus.

6. Though it makes sense, it's kind of a pain that the QuickTime files are stored on the same folder with the R3Ds. It means some file reorganizing is required to get things into post which isn't ideal (I'm of the philosophy to never touch the cameras folder structure). I also wish there was a quicker way to batch just the high framerate material to a chosen ProRes format into the same folders. Doing this via Redcine-X requires quite a few steps at the moment which goes against the speedy flow of the rest of the system

7. The Dragon is the Dragon. I love this sensor, and it's just as amazing in Raven's diminutive size. Skin looks amazing, highlight handling is excellent, shutter motion is well controlled. I'm a huge fan.

Those are my first thoughts. I'm super happy to be shooting with the Raven. Though I have access to higher end Red gear, the light weight, low cost and amazing capabilities of the Raven make me think this is going to be my go to camera for most situations.

I've been shooting Red since build 12 on the Red One (build 13 enabled audio for the first time, so.... early). I know and love the Red ecosystem. I've been responsible for making Red look its best from 200-person crews down to solo expeditions in the Himalaya. I'm excited about how the Raven opens up what is in my view the "right" way to do things to almost anybody, and it's great to finally be able to work with it and out it through its paces.

Feel free to add more thoughts here on what you learn shooting with the little bird.
 
Completely agree with all of this. I get about 45 min to an hour on my hypercores. Still have yet to shoot R3D+ProRes but may have to give it a go soon. Thanks for posting this.
 
Fool controls beta app for proRes will take care of moving those QuickTime files to somewhere else for you.

can make this as a public beta soon if useful
 
Completely agree with all of this. I get about 45 min to an hour on my hypercores. Still have yet to shoot R3D+ProRes but may have to give it a go soon. Thanks for posting this.

Regular Hypercore? Or Slim?
Also, is it the ones built for RED? With communication back to the body about %?
 
apparently shooting r3d and prores simultaneously for some reason takes more power, ive noticed it cutting the battery time in almost half.
separating the quicktimes from each folder was also a task. the camera dept chose to just shoot r3d and make prores files in a transcode.
but i still love the prores feature for a couple of personal projects for artists that only wanted that format and i have to say it was the cleanest prores i have ever seen out of a camera in low light. very happy about that.

im still looking for anyone that has successfully triggered the camera to record from the sync port on the vlock expander. we've been dealing with red and preston support for almost a week now and no one can figure out why it doesnt work.
we have got the correct new cables, switched modules with the weapon, nothing seems to work.
the vlock and jetpack have the new non-constant pulse needed, but being geared towards a triggered control for drones and gimbals, youd think this was a hugely tested function of the system.
 
Mikael - that would be useful, thanks!

Jordan - I've tested all CODECs for their battery impact. In my tests, battery life was almost identical no matter the recording format
 
Mikael - that would be useful, thanks!

Jordan - I've tested all CODECs for their battery impact. In my tests, battery life was almost identical no matter the recording format
strange, mine was not according to my dit and AC's, i wasnt personally timing anything, but i was also using slim hypercores, so who knows. but it did make sense when they told me because the camera has to actually do processing to create the prores files.
 
I found that with the Anton Bauer Cine 150 I am getting around 3hrs out of the Raven. Mine was delivered Wednesday and I haven't really had a lot of time to work with it. I plan to delve more into this weekend.
 
strange, mine was not according to my dit and AC's, i wasnt personally timing anything, but i was also using slim hypercores, so who knows. but it did make sense when they told me because the camera has to actually do processing to create the prores files.

Its doing that processing always anyhow to get a feed to the SDI/HDMI
 
I get 100 minutes of recording time on Bebob 98's. Doesn't matter if it's ProRes, R3D or both. Ran the recording continuously (which messes up the ProRes files when the power cuts FYI - see this thread on batteries for the Raven)
 
Thanks for the post Trevor, great insight. Those early HFR results from Scarlet-W that caused a shitstorm due to the unusable compression artifacts with any footage shot over 48fps, I'm curious now if it was simply because they had both prores and redcode capturing simultaneously that they didn't have the necessary compression options available to capture clean HFR images. Or if both Raven and S-W just aren't designed for anything usable over 48-60fps. That was a deal breaker for me and opted for a BT Epic instead, but still trying to get to the bottom of that whole high frame rate mystery that surfaced 5-6 weeks back. Am hoping I'm wrong so I can get back in the Raven queue for all the dsmc2 perks. Any discoveries on this front? Thx
 
Mikael - that would be useful, thanks!

email me if you want to try and use the beta app.
Just note it requires El Capitan and one feature will only work with cam FW 6.3.x or higher
 
2. The crop sensor isn't as big a deal as I thought. We shot 4.5K widescreen and didn't really need to adjust our lensing and workflow. This was a surprise... I thought being on a tighter sensor would be more limiting. It wasn't (for us, anyway)

It's interesting because on my Scarlet-W, I've used 4.5K quite a bit and looking at Abel Cine's FOV calculator, 4.5K on Red is still a wider FOV than the FS7/F55 - 23.2mm Red vs 22.6mm on Sony which is what I've been using. I was a bit surprised that Sony's sensors are cropped like that, but if hasn't bothered me for the last 1 1/2 years, it's not bothering me now.

Even if I had a 6K option, I'd probably still just stick to 5K as near Super 35mm is the sweet spot for me.

The new cameras are SWEET!

As you mentioned, I do wish the battery life was a bit better. Man.. it goes so fast. On 150w I'm getting about 2 hours.
 
Last edited:
Back
Top