Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - 12georgiadis

#201
@ 1% :  Great ! I have a 7D. Which build I have to install to get the whole sensor in 5X ? I would like to test it. Thanks in advance
#202
I'm very interested too if there is a way to have the full sensor recorded, without lock up the mirror, even if it's one minute per pic =) !
#203
I think the question is : can we go above the limit res raw video, for instance 2560 x 1320 (5DmkIII), even if we have 1 recorded frame every 10 sec, as the goal is scanning.
#204
Tragic Lantern / Re: 7D Raw Thread
October 13, 2013, 10:21:32 PM
Thanks 1% for the answers. So if I understand correctly, you can have a 1920x1038 continuous  in crop mode (10x or 5x...) ?
For this resolution, it's obvious that the upscale is not a problem for quality. But it is an additional step in post-production and if it's done in the wrong way (id. using the FCP upscale) by the assistant editor, you're losing time in professional environment. Whereas if it's 1920X1080, it is ready for edit.
#205
Tragic Lantern / Re: 7D Raw Thread
October 13, 2013, 05:39:15 PM
Quote from: RenatoPhoto on October 13, 2013, 03:52:07 PM
Can only get 1920x1080 in cropped mode at 5X zoom.  I get 1 min 30 sec of 1920x1080 at 24 fps on 7D with Lexar Pro 1000X.

Ok, good to know. Beause the upscale is a step that I would like to avoid for quality and time.
#206
Tragic Lantern / Re: 7D Raw Thread
October 13, 2013, 02:53:39 PM
Hi everyone,

I wonder if there is still a hope to get continuous recording in 1920 X 1080 for the 7D (even if it's only 24p) or if we're locked with 1728 X 972 forever ?
Is it a buffer problem ? card write speed limit or dual digic issue ?

#207
Quote from: Felixlgr on May 22, 2013, 09:05:58 PM
i have been trying to find info on how to create CinemaDNG... since its open source everything seems available freely

adobe official page with white papers and specs: http://www.adobe.com/devnet/cinemadng.html

some interesting discussion about converting dng to cinemadng : http://forums.creativecow.net/thread/277/22358

im no coder but im trying hard to figure it out...it must be really a difference in metadata xmp data

Thank you for the creative cow link. So it could be the thumbnail added by Adobe DNG Converter (if there is a reconversion after raw2DNG) that pose a compatibility problem. Perhaps by removing it, the DNG would work with resolve =)
#208
Quote from: CaptainHook on May 22, 2013, 12:44:06 PM
I think the cinemaDNG discussion belongs in this thread:
http://www.magiclantern.fm/forum/index.php?topic=5404.0

Not in BMCC DNG's.. each DNG just contains some of the DNG Tags as described in the DNG spec here (section 4):
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf

They also use TIFF Tag 51043 for timecode and 51044 for framerate as defined in cinemaDNG spec:
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/cinemadng/pdfs/CinemaDNG_Format_Specification_v1_1.pdf

@Scrax - Registration for Resolve Lite can be filled in with any details, you don't have to be a customer. :)

Thanks for the informations. So if these tags are added (TC + DNG's tags from chapter 4) it should theorically work in Resolve?
#209
And there is a light version of Da Vinci Resolve which is free and can handle 1920 X 1080 resolution. So, perfect to test the Cinema DNG compatibility ;-)
#210
Quote from: scrax on May 22, 2013, 12:02:56 PM
Your are right, the dng file are generated by raw2dng (developed by Alex) that's inside the raw2dng.app package so this is something that need to be solved there, the know issue are relative to the GUI wrapper that do the work of starting the command line tool for the raw dragged in.
Added it to first topic

I think alex is already working on it. I can't test that problem because don't know Resolve and all those raw video procedures with proxies and so on.

What is the basic raw video workflow?
RAW to DNG
folder that should be cinemaDNG
Editing software

I saw that there is a win batch converted that converts to tiff and makes proxy but didn't get why or what they are.

Scrax, here is the workflow that I do with the Black Magic Cinema Camera that records in 12-bit Raw Cinema DNG (which work the same with the 5D Raw if you can transform raw to DNG DNG cinema..) :
When you open Da Vinci Resolve It recognizes Cinema DNG because I think in the first DNG file, there is the content of the metadata Cinema (Time Code, Frame Rate, T-Stop, Reel Name, Camera Label) + photo metadata record.
Then we created proxies to ProRes 422, which only contain the metadata cinema to edit the footage on any professional NLE (Premiere, FCP X, Avid, etc..).
Once finished editing, you export the project in XML and conformation is due to metadata Cinema, to link to the DNG. From there, Resolve recognizes files and keeps the edit right.
We can then do the color grading in raw.
If DNG is converted to Tiff is no longer raw.
#211
Quote from: CaptainHook on May 22, 2013, 06:09:49 AM
This is the wrong thread i think, but cinemaDNG can simply be a folder of DNG files with sequential numbers so the spec that needs to be followed in just the plain DNG spec.

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf

Currently using dng_validate (which is in the DNG SDK) gives these errors with DNG's from raw2dng which i've already let a1ex know about (this thread is about an OSX wrapper for that app):

*** Warning: IFD 0 Model is not NULL terminated ***
*** Warning: IFD 0 UniqueCameraModel is not NULL terminated ***
*** Warning: The ExposureTime is <= 0 ***
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***



Ok, sorry if I'm in the wrong thread (I'm new), I did not know it had been discussed elsewhere. Do you have the link to the right thread?
If I understand correctly, the files that come out of raw2DNG contain metadata errors that are the reason why Da Vinci Resolve does not recognize the result of DNG files (in a folder) as Cinema DNG?
With Black Magic Cinema Camera for example, additional metadata (timecode, Frame Rate, T-Stop, Reel Name, Camera Label) are contained in the first DNG but not in the other DNG file.

If there is a way for the DNG to be recognized in Da Vinci Resolve, the workflow would Become the same as the BMCC and could be used to make feature films. But it's more complicated if you have to go through Photoshop and After Effects before the editing.
#212
Perhaps Adobe has released an SDK Cinema DNG
I found this for the Cinema DNG's related tags : http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/cinemadng/pdfs/CinemaDNG_Format_Specification_v1_1.pdf (P.20)
#213
Hello,

First of all, thank you for the tremendous work done on the 5D Raw and the raw2dng.app !!

I wanted to know if it was possible to incorporate CinemaDNG specifications in the conversion of raw to DNG. In fact, Da Vinci Resolve does not recognize DNG or partially because they do not contain the following metadatas : Time Code, Frame Rate, T-Stop, Reel Name, Camera Label.
For rushes of BMCC (also in Cinema DNG), these metadatas are only stored in the first DNG, which allows it to be read in Resolve and help us to create proxies (id. ProRes LT) to mount on any NLE. Then we can make a XML to conform and send it to Da Vinci. This would avoid making color corrections before the editing and would give to the 5D Raw video, access to use for a feature film workflow.