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

Red One connector "what is what"

Sean said:
Interesting about the scaling issues. But 720 pixel wide is sufficient for focus right? So from the sounds of it you could use the HDLink to get a 720 monitoring solution for Red from a 1280x800 monitor.
Click to expand...

I just pictured my focus puller standing next to the RED with a 23"LCD attached to the camera on a NOGA arm. :biggrin:

A decent Focus puller is not going to use the monitor to find focus, but it will settle the mind of the director and others at video village.

Still, an almost sharp monitor can cause problems. The last shoot I was on had the continuity lady screaming "sharps! Check FOCUS!". She was watching a 8" LCD monitor from a film split. My Focus puller almost walked over and slapped her.
 
FAT32 limit of 4 GB per file

FAT32 limit of 4 GB per file

Anders Holck said:
The drives are FAT32 formatted. The mediafiles are standard Quicktime files and using the Redcode codec either in RAW or RGB mode.
Click to expand...

Now I have a question: FAT32 has a limit of 4 GB per file. How is this handled, anyone, anyone? Files broken off into 4 GB chunks?

-rune
 
Port E,G, and F have a strange look to them. On most cameras these connectors would be handled with BnC's. What type of conector are they? I also saw that the camera was using a smaller then normal XLR for audio. Shouldn't all the conectors on the Red be the same type that we use in the industry? It would be a shame to have to have adapt everything.
 
Shane V8F said:
Port E,G, and F have a strange look to them. On most cameras these connectors would be handled with BnC's. What type of conector are they? I also saw that the camera was using a smaller then normal XLR for audio. Shouldn't all the conectors on the Red be the same type that we use in the industry? It would be a shame to have to have adapt everything.
Click to expand...
I don't know what E, G, and F are (possibly some kind of mini BNC). Since these are digital it won't matter to have a adaptor anyway...

I think that they used mini-XLR sockets for audio to fit them all in. Otherwise you could only fit 2 inputs on the side of the camera. I think I heard someone say that a lot of new wireless mics etc. are starting to use mini XLR now anyway.
 
Remote T/O

Remote T/O

Looking at the connections published I cannot recognize any provision for a remote turn over/record facility. Can anybody confirm there is indeed a way
of remotely controlling recording sessions?
 
A few posibilities:
L) B4 lens connector, I believe this has an interface for the Supergrip to start/stop etc. Could be a full RS-232.
M), N) USB. Stuart has said that a API will be available at some point to enable two way communication and control of the camera, even wireless with a Wifi/Bluetooth dongle.

*** Correction by Stuart ***
Stuart English said:
Connectors C have GPI and GPO... i.e. contact closures based - use one for start / stop the other for a remote tally.
Click to expand...
 
Anders Holck said:
A few posibilities:
L) B4 lens connector, I believe this has an interface for the Supergrip to start/stop etc. Could be a full RS-232.
M), N) USB. Stuart has said that a API will be available at some point to enable two way communication and control of the camera, even over wireless with a Wifi/Bluetooth dongle.
Click to expand...

A simple N/O momentary 2 way contact should suffise to ensure compatibility with most camera remote systems of this globe. Any deviation towards more complex setups for this purpose would be a manko.
 
Remote start / stop

Remote start / stop

Connectors C have GPI and GPO... i.e. contact closures based - use one for start / stop the other for a remote tally.
 
Sounds good. Is there a detailed pinout info with connector specs for all connections available as of yet so that we can prepare
remote systems for this woderful new tool in a timely manner?
 
Any one have a source for those damn mini BNC connectors, or pigtails? I'm going to need 20 of the freaking things in my case. Based on how often things like that go "missing" I'm really not stoked on them instead of standard BNC, plus they look very breakable.


_mike
 
BNC replacements

BNC replacements

We supply adaptors cables ..... and can certainly supply spares if you need them.

When its freezing cold or wet, those four compact, positive lock, push pull connectors that replace BNC's might just be seen in an entirely different light :matrix:
 
Anders Holck said:
The Red Drive and Red Ram has FW800 and USB2 connectors (and eSATA though it's using the custom connector)

The drives are FAT32 formatted. The mediafiles are standard Quicktime files and using the Redcode codec either in RAW or RGB mode.
Click to expand...

rune said:
Now I have a question: FAT32 has a limit of 4 GB per file. How is this handled, anyone, anyone? Files broken off into 4 GB chunks?

-rune
Click to expand...

Sorry guys, can we sort that out please ? Only found confirmation for the FAT32 - but how does it work now ?
Red has to split them up. Nice, so only the last file would be corrupted, on case something failes or you have a data-problem.
But its very unusual for these systems to make a split and still unclear how the chunks are sticked together again.
Wether AVIs on Windows systems, nor Apple systems as to my experience and awareness do a brakeup.
(Except a reference Quicktime)
 
augenmensch aka therock said:
Sorry guys, can we sort that out please ?
Click to expand...

I'm a bit surprised it's that important to you. We're writing chunked files with a sort of QT reference files. You will have a way to deal with corruption and such.
 
My comment that the mediafiles are quicktime files is in fact uncorrect and I'll edit that.
The mediafiles are custom data files with a small Quicktime reference file pointing to them.

Rob can you comment on how the filestructure is at the moment?
How are the files named in the file tree etc.
 
I cannot since we haven't fully nailed that down yet...
 
Anders Holck said:
Thom, you do need two BNC cables in parallel to run the HD-SDI at RGB 4:4:4, if you switch the RED Master HD-SDI output to 4:2:2 you only need one cable.
Click to expand...

When I pointed exactly that out at NAB my wish sounded to be very new. It looked as if singlelink SDI (422) was not really on plan until just now (?). So in my understanding its not a feature built-in yet ?

Rob Lohman said:
I'm a bit surprised it's that important to you. We're writing chunked files with a sort of QT reference files. You will have a way to deal with corruption and such.
Click to expand...

Hi Rob, sorry! My
augenmensch aka therock said:
Sorry guys, can we sort that out please ?
Click to expand...
was meant to have an :umm: or such at the end..

But indeed, corruption is exactly the reason why I think its important. If you had a corrupted QT file of some 300GB, when the recording was stopped due to whatever reason, than you understand why its corrupted wrapper is so annoying. I tried all options and usually with the defective wrapper in my experience you don't get this file working again.
One of the reasons I love image sequences for. Only the last image might have a failure.
AND because i experienced how difficult it might be to stick chunks together again if you don't know the nomenclature of them. Record a DV-stream or even bigger to a FAT32 with FCP over 20-30mins (>4GB) - gives you an idea of what I mean. FCP breaks them up for you. One mother QT and its chunks in a certain way.
 
I was a bit surprised since we like to take care of you :) As indicated there will be ways to deal with file corruption.
 
You must log in or register to reply here.
Back
Top