Welcome to our community

Be a part of something great, join today!

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

RED future...

Status
Not open for further replies.
ChrisLyon said:
I'm just wanting a better product so as I don't have to worry about "inadequacies" in the blue channel.
Click to expand...

But see that's just something that takes more time to maybe happen upon a solution to. If you improve the blue channel, you improve the overall noise floor. The blue channel is choppy because it's being pushed 1 or 2 stops more than the green channel. If you want to get another 2 stops out of the blue channel you're going to get another 2 stops out of the green channel... at which point we would still complain that the blue channel is the weak link. Maybe... if they made the blue photosites 50% wider than the other two you would get a more even response, but then the average noise floor raises and you might as well just filter.

Money can't always buy discoveries. There isn't a cost out there like "Well if we spend $XYZ we'll invent the mysterium chip."

If you want to put that $2500 to good use put it towards research, test shoots and best shoot practices to get the most out of what you've already bought.

So far it seems as if once we make something clear as "unacceptable" RED has been willing to invest the necessary funds to make it right. Perhaps dedicating a $2500 budget to rigorous stress testing to make sure RED is aware and adequate concerned about all the existing problems would also be a good use of your extra $2500.

There's a great saying "9 women can't make a baby in one month" I've always assumed that this is the reasoning behind RED's PR. While I would wish development on the software side would now hurry up a bit I can't say for certain that increasing the size of the team would accomplish anything if everybody is already waiting for something else to be completed.
 
I don't think Jim is too worried about making an extra $0.5 mil. profit for that $2500 price increase. Even if he spent like $25 mil. to invent the Mysterium, that's still just a drop in the bucket when you have a couple bil. Besides, think of all the complaints people would post here on the forum. Also, by the time Red ships all the cameras already ordered, they will already have recovered R&D costs, and be making millions in profit.
 
I forgot about something:

Add a "partial clip" and "full clip" indicator to the false color meter. Say, magenta when there's a partial clip [one or two channels clip] and neon green when all channels clip.
 
I feel for Jim,

He must be somewhat caught between a rock and a hard place. Through his many posts and those from others at the RED team, it has become clear these are very ethical people who have a real commitment to not only deliver on what they promise but to keep pushing the bar as high as they can. And those two aims could end up working against each other. Right now, the camera does not yet have all the features originally promised, and that's why they endeavor to retrofit existing units and improve ones ready for imminent delivery. But, at some point they'll need to take a deep breath and draw a line between what they feel is "owed" to all the loyal people who ordered cameras on pure faith, and what are improvements that should be acquired as an extra, whether in the shape of an add on or a more expensive or different camera.

That deciding moment will have to come at some point, but until that happens, let us all concentrate on helping the team improve those original features that were part of the original deal when the RED was first announced. We cannot expect or hope for more than that, but until that happens, let's not "suggest" they charge more for what they seem intent and able to deliver at the original price point. And let's not think either that the only way they would be able to solve those issues would be by charging more, that's actually counterproductive and disrespectful to their philosophy and way of doing things. Once the original promise is fullfilled (and in some aspects it has been already surpassed), and only then, let's talk about a more expensive product. And if that time comes, let's not bark at them either.
 
Rudi... I've always liked you.

Jim
 
I feel very small right now. I was making an observation based on previous red team statements. I never intended to undermine anyone. I feel offended but enlightened. It's a strange feeling. I do agree with the statement though.

How does he do that?
 
I would like to see different grids and cross hair switchable on/off on the monitor.

Also Trigger for 2 Red camera starting together on 3-d shoots.

The ability to check on the other Red camera when using with one finder on
2 Red cameras (hand-held or similar situation), may be with a switchable extension cable.

Thanks,
Henry
 
Can anyone at RED confirm this.

Can anyone at RED confirm this.

jbeale said:
A start-record trigger (digital input) is already done.

BETA Build 10 (v1.6.4) Release Date: 2007-11-22

... Addition of GPI trigger enabled RECORD ...
http://www.red.com/support/release_history/7
Click to expand...

I was told earlier not to try the gpi trigger yet, but it would be really nice to use in the underwater housing. Can anyone at RED confirm this? Could you repost a pinout? Does the tally work also? Can you gives us a spec for the tally LED?

EDIT Answered my own question, except can someone tell me simply how to make an LED work with that setup - can you just wire one side of the LED to Vout and the other to GPO tally?

Quote from new user manual:
"The camera provides two auxiliary power output connectors on its back panel. Each supplies
un-regulated +11.5 – +17V battery pass-through power. Maximum sustained current draw is 1
Amp per output. Outputs are over-current protected, and switched by camera firmware.

Mating connector LEMO FGG.0B.304.CLAD42Z (straight)

Pin Signal Description
1 -VOUT Auxiliary power return (Ground)
2 GPI Trigger
3 GPO Tally
4 +VOUT Auxiliary power output

Note: Commencing with Build 10 firmware, Pins 2 and 3 can be used to provide an external
Trigger and Tally signal. The function of each GPIO pin can be configured by the operator,
however the default setting for the upper connector is Pin 2 = Record Start/Stop and Pin 3 =
Record Tally. For the lower connector, the default setting is Pin 2 = Record Next Frame and
Pin 3 = Frame Record Completed. Use this for animation or simple motion control interface."
 
AquaVideoRed206 said:
[..]
Mating connector LEMO FGG.0B.304.CLAD42Z (straight)

Pin Signal Description
1 -VOUT Auxiliary power return (Ground)
2 GPI Trigger
3 GPO Tally
4 +VOUT Auxiliary power output

Note: Commencing with Build 10 firmware, Pins 2 and 3 can be used to provide an external
Trigger and Tally signal. The function of each GPIO pin can be configured by the operator,
however the default setting for the upper connector is Pin 2 = Record Start/Stop and Pin 3 =
Record Tally. For the lower connector, the default setting is Pin 2 = Record Next Frame and
Pin 3 = Frame Record Completed. Use this for animation or simple motion control interface."
[..]
Click to expand...

Hey guys,

anyone out there who can verify that the two GPI/GPO ports are already working as described here?

I was asking for this feature since a while and was - if answered - always told "not yet".

I would strongly need to start & stop a new sequence, and to add single frames to it. Think of Moco and Stop Motion stuff.

If anyone has some clue here, please drop me a note.

Jim, Stuart, Graeme?

Cheers,
Axel
 
Mating connector LEMO FGG.0B.304.CLAD42Z (straight)
Pin Signal Description
1 -VOUT Auxiliary power return (Ground)
2 GPI Trigger
3 GPO Tally
4 +VOUT Auxiliary power output


Is it this one which we need to make custom GPI/O cables? :

http://www.lemo.com/partnum_search.do

Part Number FGG.0B.304.CLAD42Z
Size/Series 0B (Metal (Mechanical Keying))


MECHANICAL DETAILS

Shell Style/Model FG*: Straight plug, cable collet and nut for fitting a bend relief
Keying G: 1 key (alpha=0, plug: male contacts, receptacle: female contacts)
Housing Material C: Brass (chrome plated) shell and collet nut, nickel plated brass latch sleeve and mid pieces
Cable Fixing D42: 3.1 - 4 mm (0.12 - 0.16")
Variant Z: Nut for fitting a bend relief


Dimensions

A L M S1 S2
mm. 9.5 35.0 25.0 8.0 7.0
in. 0.37 1.38 0.98 0.31 0.28


PERFORMANCE DETAILS

Insert Configuration 0B.304: 4 Low Voltage
Insulator L: PEEK
Rear View


Specifications

Low Voltage Contact Type: Solder
Max. Matings: 5000
Contact Dia.: 0.7 mm (0.028")
Bucket Dia.: 0.8 mm (0.031")
Max. Stranded Conductor: 0.34 mm^2 (AWG 22)
Max. Conductor: 0.34 mm^2 (AWG 22)
R (max): 6.1 mOhm
Vtest (contact-shell): 700 V (AC), 990 V (DC)
Vtest (contact-contact): 850 V (AC), 1200 V (DC)
Rated Current: 7 A (AC/DC)


OTHER CHARACTERISTICS

Endurance (Shell): 5000 mating cycles
Temp (min): -55 deg C (-67 deg F)
Temp (max): 250 deg C (482 deg F)
Humidity (max): <=95% [at 60 deg C / 140 F]
Vibration: 15 g [10 Hz - 2000 Hz]
Shock Resistance: 100 g [ 6 ms]
Salt Spray Corrosion: >144 hr
IP Rating: 50
Climatical Category: 55/175/21
Shielding (min): 75 dB (10 MHz)
Shielding (min): 40 dB (1 GHz)
 
ChrisLyon said:
I feel very small right now. I was making an observation based on previous red team statements. I never intended to undermine anyone. I feel offended but enlightened. It's a strange feeling. I do agree with the statement though.

How does he do that?
Click to expand...

Chris, your honesty in this post is to be equally respected.
Jay
 
Followup: for those hooking up to the GPO / GPI pins: the beta firmware claims to enable it, but I'd be cautious about hooking up to these pins unless Red has already posted a clear description about their electrical interface.

If the tally signal is a direct connection to some general-purpose logic level I/O pin from a microcontroller, it may have a low current drive capability (so you'd need a buffer circuit to drive a LED to much brightness) and if the I/O lines are not protected from a static discharge and you connect a long wire to it going somewhere, bad things might happen on dry winter days on carpets, etc. There may be no issue here and I'm not saying Red's hardware designers did anything wrong, just might want to wait for a full wiring spec if it's not out there already.
 
Yep,

someone from RED should enlighten the situation about the GPI, as we really need that. We have a SFX shooting planned for mid/late january and their might be anything from crane to time lapse, slowmo, stop trick.

So I really need to understand and prepare for that.

The problem starts to get the right connectors in first place, and then do the right cable and interfacing.

Axel
 
Status
Not open for further replies.
Back
Top