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

Another Feature Request

Harry Clark

Harry Clark

Well-known member
Joined
Dec 29, 2006
Messages
1,791
Reaction score
0
Points
36
Location
NYC
Pardon me if it's already been thought of...
Or if it's too late to incorporate...
What about an inclinometer function? It would help for effects shots, since we currently take this measurement manually. How about along the tilt axis and the "dutch" axis?
Logically, it would be stored in metadata with the lens info.
Shooting FX work with the Epic would then REALLY be a breeze (I assume that the Cooke "i" data will be incorporated just like the Red) and since we can have an inclinometer on an iPhone, certainly we can have one on a digital cinema camera!
Or maybe we can't...
Or perhaps there can be a metadata input plug, and a third party could put out inclinometer modules and maybe even a height measuring instrument...
Just thinking out loud for the world of effects...
Cheers,
Harry
 
Lets add 5 million do dads to this camera completely riddle it with requested features so it becomes a $250,000 camera instead of something that is already great and feature packed for under 20k

Do these feature requests really sound reasonable when looking at what is trying to be accomplished by Red?
 
HD Bubaloo said:
Lets add 5 million do dads to this camera completely riddle it with requested features so it becomes a $250,000 camera instead of something that is already great and feature packed for under 20k

Do these feature requests really sound reasonable when looking at what is trying to be accomplished by Red?
Click to expand...

Does a ~4k camera for 17k sound reasonable? Not really. I think an inclinometer is the least of there worries. I think it would be a useful feature.


The really interesting thought here, though, is a metadata plug that 3rd parties can input to. Imagine being able to buy (from ET or whoever) an inclinometer, a gps, a whatsit, or a thingamabob and have its output recorded right into the R3D file, to be used in post?

Now that would be cool.
 
No 17k for a 4K resolution camera is not reasonable. Its really amazing so my thought is rather, why not be grateful and stop asking for everything under the sun. I mean isn't this camera pushed back far enough, why extend the time to market.

my 2 cents not meant to cause static
 
HD Bubaloo you can relax, Red asked for feed back. They even went so far as to ask us to describe our dream modules.

Simple suggestions like this are not the byproduct of ungrateful children.

I dislike "grabby" consumers as much as the next.
 
Describing a possible need for something can only be useful for camera developers. Millions of dollars are spent each year on focus groups to improve products. I am sure that many of the improvements to be found on the Scarlet and Epic will have come from just such requests.

These high resolution cameras are not going to be used by soccer moms to video tape their kids. They will be used by working professional operators.

An inclinometer is often used in effects work and also table top cinematography. This makes up a significant portion of the professional market.

If I had a dollar for every night we spent framing up a cheeseburger or a box of aspirin, I would be a very wealthy man.
 
An internal inclinometer would be great for when needed.

The bi product of your request; a 3rd party plug in that will contribute data to the metadata is what I am getting very exited about.

There would have to be either an automated option of 'add on' info to the end of the metadata stream so when extracted the info will appear sorted directly after the standard camera info. An alphabetically sorted metadata stream (would make things more complicated and less convenient for data base work) or a user defined order of metadata menu built into the menu system.

Connected to TC slates in the future the slating info of the digital slates could be recorded into the metadata!!!

I'm getting exited here...
 
Yes. Just a suggestion. Not whining. If I were going to whine about something it would be rolling shutters.
But it does not have to be an incline module.
Maybe it's just a metadata module that could be open to third party products.
It's just that I tend to do a lot of tabletop work, and it seems like now there are effect shots in EVERY commercial. Incline and height are measurements that are often as important as noting focal length and distance (data that already goes into the metadata if you use Cooke "i" lenses) Unfortunately, if the shot is not a lockoff, the AC can only estimate the interim incline and camera height.
Having other physical camera info on a frame-by-frame basis, incorporated into metadata, would be a great feature.
Cheers,
Harry
 
Harry Clark said:
Yes. Just a suggestion. Not whining. If I were going to whine about something it would be rolling shutters.

Harry
Click to expand...

The rolling shutter is the WORST thing about the Red 1, at least as far as things that can't be fixed by stuff you can buy from Element Technica !

Matt Uhry
www.mattuhry.com
 
They will get the photosite activation rate to go super fast. Then the rolling shutter will be fine. Film has skew too.
 
After looking at some fast whip pans from a build 17 clip, I have to say at this point it is not much of an issue except at very narrow shutter angles.
 
Unsynced flashes

Unsynced flashes

I still feel the rolling shutter is horrible with unsynced flashes. Half frame splits with strobes! Horrible! I know it's been said that film has this problem as well, but I've never encountered it or have seen it in all the years film has been used to shoot strobes and flashes going off. I've shoot deirectly into strobes and different speeds with 35mm and I never saw half frame splits like the RED's rolling shutter.
 
35mm film shutter issues and 80s television

35mm film shutter issues and 80s television

fastlayne said:
I still feel the rolling shutter is horrible with unsynced flashes. Half frame splits with strobes! Horrible! I know it's been said that film has this problem as well, but I've never encountered it or have seen it in all the years film has been used to shoot strobes and flashes going off. I've shoot deirectly into strobes and different speeds with 35mm and I never saw half frame splits like the RED's rolling shutter.
Click to expand...

My personal experience with automatic weapons on set is limited. However, it is my understanding that machine guns used in TV shows like the A-Team (Shot on film) were synced to the camera shutter so they would get barrel flare.

If they did not do this, the barrel flash would often occur in between exposed frames and the guns would not appear to be firing. As a result of this electronic synchronization, you often got these almost unnatural star shaped barrel flashes time and time again.

P.S. I loved when they got BA to drink the drugged milk so they could get him on a plane.
 
iphoneclinometer.jpg


about 79 cents in the app store.
 
Yes, James. We all have that.
Our ACs all take notes with inclinometers.
Our script supervisors write it in the script notes.
The effects guys write it down.
Reread my post. The value is in having frame accurate metadata that changes as the camera tilts.
Cheers,
Hary
 
It would be great to have a part of the R3D file metadata for user functions. So that in each frame, a fixed amount of data could be recorded. This would be accessable over USB port. That way, you could (conceivably) use a keyboard or iPhone app to write it's own data to each frame live as you record. And other 3rd parties could create ways to write the data.

All RED would have to do is create this user field space in the file, and, say, a small, separate SDK to allow to write to it. Shouldn't be to difficult and lots of us could get the info we need on a frame-by-frame basis.
 
Red@BirnsAndSawyer said:
It would be great to have a part of the R3D file metadata for user functions. So that in each frame, a fixed amount of data could be recorded. This would be accessable over USB port. That way, you could (conceivably) use a keyboard or iPhone app to write it's own data to each frame live as you record. And other 3rd parties could create ways to write the data.

All RED would have to do is create this user field space in the file, and, say, a small, separate SDK to allow to write to it. Shouldn't be to difficult and lots of us could get the info we need on a frame-by-frame basis.
Click to expand...

Exactly. This would be amazing. Didn't Panasonic demo something like this recently? A bluetooth connection (or something) to one of their Toughbooks that allowed lots of metadata?
 
You must log in or register to reply here.
Back
Top