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

A videographer delivered to us in 1080p MOV instead of 6K R3D. Any thoughts why?

P

Peter Kovacs

New member
Joined
May 5, 2022
Messages
1
Reaction score
0
Points
0
The only thing I can think of is they set the file format to ProRes 422 HQ and the resolution to just 2K.

However, when I view the metadata in the MOV file it suggested it was shot in 6K and that there's a .R3D file:

Code: 
ExifTool Version Number : 12.62
File Name : A004_A007_05273H_001.mov
Directory : D:/Videos/2023/230526
File Size : 11 GB
File Modification Date/Time : 2023:05:26 15:12:04-04:00
File Access Date/Time : 2023:07:06 09:33:11-04:00
File Creation Date/Time : 2023:07:05 19:54:20-04:00
File Permissions : -rw-rw-rw-
File Type : MOV
File Type Extension : mov
MIME Type : video/quicktime
Major Brand : Apple QuickTime (.MOV/QT)
Minor Version : 2007.4.0
Compatible Brands : qt
Media Data Size : 11469180896
Media Data Offset : 36
Movie Header Version : 0
Create Date : 2023:05:26 19:03:52
Modify Date : 2023:05:26 19:03:52
Time Scale : 24024
Duration : 0:08:12
Preferred Rate : 1
Preferred Volume : 100.00%
Preview Time : 0 s
Preview Duration : 0 s
Poster Time : 0 s
Selection Time : 0 s
Selection Duration : 0 s
Current Time : 0 s
Next Track ID : 4
Track Header Version : 0
Track Create Date : 2023:05:26 19:03:52
Track Modify Date : 2023:05:26 19:03:52
Track ID : 1
Track Duration : 0:08:12
Track Layer : 0
Track Volume : 0.00%
Image Width : 1920
Image Height : 1080
Time Code : 3
Graphics Mode : srcCopy
Op Color : 0 0 0
Compressor ID : apch
Vendor ID : Apple
Source Image Width : 1920
Source Image Height : 1080
X Resolution : 72
Y Resolution : 72
Compressor Name : Apple ProRes 422 HQ
Bit Depth : 24
Color Profiles : nclc
Color Primaries : Unspecified
Transfer Characteristics : Unspecified
Matrix Coefficients : BT.709
Video Field Order : Progressive; 0
Pixel Aspect Ratio : 1:1:0
Video Frame Rate : 24
Balance : 0
Audio Format : in24
Audio Bits Per Sample : 16
Audio Sample Rate : 48000
Purchase File Format : in24
Endianness : Little-endian (Intel, II)
Layout Flags : Quadraphonic
Audio Channels : 4
Matrix Structure : 1 0 0 0 1 0 0 0 1
Media Header Version : 0
Media Create Date : 2023:05:26 19:03:52
Media Modify Date : 2023:05:26 19:03:52
Media Time Scale : 24024
Media Duration : 0:08:12
Gen Media Version : 0
Gen Flags : 0 0 0
Gen Graphics Mode : ditherCopy
Gen Op Color : 32768 32768 32768
Gen Balance : 0
Text Font : System
Text Face : Plain
Text Size : 12
Text Color : 0 0 0
Background Color : 0 0 0
Font Name : System
Handler Class : Data Handler
Handler Description : DataHandler
Other Format : tmcd
Playback Frame Rate : 24
Other Name :
Handler Type : Metadata Tags
Red Camera Camera Serial Number : KMDBK006266
Red Camera Exposure Time : 20833.333984375
Red Camera Kelvin : 5600
Red Camera Tint : 0
Red Camera Camera ID : A
Red Camera Reel Number : 004
Red Camera Clip Number : 007
Red Camera Clip Start Local Date: 20230527
Red Camera Clip Start Local Time: 030352
Red Camera Firmware Release Name: 1.5.3
Red Camera User Timecode Preference: (Binary data 1 bytes, use -b option to extract)
Red Camera Media Model Number : RED PRO CFast 512GB
Red Camera Clip Start GMT Date : 20230526
Red Camera Clip Start GMT Time : 190352
Red Camera Media Serial Number : G32BNCFA9NA1158
Red Camera Media Revision Number: RD3.05
Red Camera Frame Guide Rectangle: (Binary data 8 bytes, use -b option to extract)
Red Camera ISO : (Binary data 2 bytes, use -b option to extract)
Red Camera Anamorphic Setting : (Binary data 1 bytes, use -b option to extract)
Red Camera Sensor Model : (Binary data 1 bytes, use -b option to extract)
Red Camera Color Science Version: (Binary data 2 bytes, use -b option to extract)
Red Camera Flut Control : 0
Red Camera Sensor Filter : (Binary data 4 bytes, use -b option to extract)
Red Camera User Action Guide Rectangle: (Binary data 8 bytes, use -b option to extract)
Red Camera User Title Guide Rectangle: (Binary data 8 bytes, use -b option to extract)
Red Camera Camera Position : A
Red Camera Filename Random Characters: 3H
Red Camera Lens Mount Attached : (Binary data 1 bytes, use -b option to extract)
Red Camera Clip Filename : A004_A007_05273H_001.R3D
Red Camera Measured Black Value : (Binary data 10 bytes, use -b option to extract)
Red Camera Guides Active : (Binary data 1 bytes, use -b option to extract)
Red Camera Firmware Revision Number: (Binary data 4 bytes, use -b option to extract)
Red Camera Current Record Framerate: 24
Red Camera Color Space : (Binary data 2 bytes, use -b option to extract)
Red Camera Gamma Curve : (Binary data 2 bytes, use -b option to extract)
Red Camera Calibration ISO : (Binary data 4 bytes, use -b option to extract)
Red Camera DSMC Motion Mount Shutter: (Binary data 1 bytes, use -b option to extract)
Red Camera Resolution Format Name: 6K 16:9
Red Camera Sensor Calibration : 3.44963049888611 1 1.93558168411255 3.57447195053101 1 1.6834055185318 3.53574228286743 1 1.66773152351379 0.482072114944458 0.314668297767639 0.203259378671646 0.091143973171711 0.940995097160339 -0.0321390703320503 -0.0311378445476294 -0.546658992767334 1.57779622077942 0.612294256687164 0.210075885057449 0.177629560232162 0.212070822715759 0.833675146102905 -0.0457461588084698 -0.0200757663697004 -0.282881617546082 1.30295693874359 0.630903720855713 0.225711598992348 0.14338456094265 0.226652801036835 0.875373661518097 -0.10202656686306 -0.0132951457053423 -0.247883170843124 1.2611780166626 168.199996948242 154.899993896484 54.0299987792969 0.962047398090363 1 0.887163579463959 0.959161400794983 1 1.10654473304749
Red Camera Sensor Calibration ID: (Binary data 2 bytes, use -b option to extract)
Red Camera Alternate Monitor Color Space: (Binary data 1 bytes, use -b option to extract)
Red Camera Alternate Monitor Gamma Curve: (Binary data 1 bytes, use -b option to extract)
Red Camera OLPF User Swappable : (Binary data 2 bytes, use -b option to extract)
Red Camera DRX Enable : (Binary data 1 bytes, use -b option to extract)
Red Camera Camera Model Name : KOMODO 6K
Red Camera IPP2 Base ISO : 75.1495361328125 150.299072265625
Red Camera IPP2 ISO Compensation Gain: 1.17540001869202
Red Camera IPP2 Roll Off : (Binary data 1 bytes, use -b option to extract)
Red Camera IPP2 Output Color Space: (Binary data 1 bytes, use -b option to extract)
Red Camera IPP2 Development Contrast Enum: (Binary data 1 bytes, use -b option to extract)
Red Camera ISO Calibration Stop Adjust: 1
Red Camera Edge Timecode 2 : 00:04:42:03
Red Camera Absolute Timecode 2 : 00:46:00:02
Red Camera Playback Framerate : (Binary data 4 bytes, use -b option to extract)
Red Camera IPP2 Advance Enabled : (Binary data 1 bytes, use -b option to extract)
Red Camera Sensor Shutter Type : (Binary data 1 bytes, use -b option to extract)
Red Camera Chroma Noise Reduction: (Binary data 1 bytes, use -b option to extract)
Red Camera Record Framerate V2 : (Binary data 4 bytes, use -b option to extract)
Red Camera White Balance System : (Binary data 1 bytes, use -b option to extract)
Image Size : 1920x1080
Megapixels : 2.1
Avg Bitrate : 186 Mbps
Rotation : 0

So is it possible the .R3D file exists?

An other thoughts before I contact the videographer?
Thanks
 
Is it one clip or many clips in the form of a REFERENCE movie?
 
It does look that the clip was recorded in PRORES inside a camera. If it's the case, Komodo doesn't do simultaneous record of PRORES and R3D, so that was the only format it was shot in.
 
What I'm seeing in that metadata is a 1080p ProRes file recorded on Komodo. The only way that is not the case is if this was transcoded with something like Scratch and maybe the camera metadata was passed through showing this was captured by Komodo. Hopefully it's the latter and you can get the R3D. But being Komodo you can only capture one or the other.
 
Steve Sherrick said:
What I'm seeing in that metadata is a 1080p ProRes file recorded on Komodo. The only way that is not the case is if this was transcoded with something like Scratch and maybe the camera metadata was passed through showing this was captured by Komodo. Hopefully it's the latter and you can get the R3D. But being Komodo you can only capture one or the other.
Click to expand...


The metadata shows that the filename was a .R3D. Which tells me that they transcoded the files. This line would reference a .mov if you acquired in the ProRes mode. That tells me they transcoded the file during or after backup.

"Red Camera Clip Filename : A004_A007_05273H_001.R3D"

Contact them and im sure they can help you out! For some situations some might choose a workflow where they will shoot R3D and then fine tune the white balance and ISO in RED Cine-X and transcode to ProRes before delivery.
 
I once dealt with an owner/op who shot something in 1080p, and then did an upscale to 6k to "increase the quality for post" prior to sending it to me.

So don't discount the possibility that you could just be dealing with a moron. There are a lot of them out there.
 
DJ Meyer said:
I once dealt with an owner/op who shot something in 1080p, and then did an upscale to 6k to "increase the quality for post" prior to sending it to me.

So don't discount the possibility that you could just be dealing with a moron. There are a lot of them out there.
Click to expand...

Ouch....

Brian Timmons
BRITIM/MEDIA
 
Another hypothesis: maybe the ProRes file was recorded on an external recorder while the R3D files are still on on the card (if not formatted yet)?

Then it might explain why we see the R3D file name in the EXIF data, if the original camera EXIF data was looped through to the recorder which added its own metadata to it without modifying the metadata it got from the camera. Don't know if this is possible though, no such recorder around here to test with.
 
You must log in or register to reply here.
Back
Top