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.

Messages - platu

Pages: [1] 2 3 4
Hm... sry, can't help with Resolve and can't fix Resolve. I can't find that either in their table.

OK... thank you anyway.

Aperture is saved into cdng.

That's very helpful, thank you.  I guess what I meant to say is if there was a way to view the aperture from within Davinci Resolve?  Other major EXIF fields show up there (ISO, Focal Length, etc).  It's just aperture that doesn't show, at least for my camera (5D Mark III).

My workflow involves using MLV App and exporting to Davinci Resolve Studio (using Cinema DNG Fastpass - DaVinci Resolve Naming Scheme.  I know you can see the aperture used in MLV App, but I delete the original MLV files after exporting to Davinci Resolve in order to save drive space.  Unless I'm missing this, is there a way to include the aperture used in the cndg metadata?

Modules Development / Re: MLV Lite
« on: April 21, 2016, 09:41:11 AM »
@DeafEyeJedi, No worries... I'm not easily discouraged anyway ;)

Modules Development / Re: MLV Lite
« on: April 21, 2016, 08:56:50 AM »
Workaround: use MLVFS and MLRawViewer together (MLRawViewer is capable of playing back DNG files).

I had already found this suggestion in a previous post but I still appreciate the tip.  I do happen to use MLraw Viewer for more than just previews.  For example, all exporting (DNG or MOV) does not work (at least for me) when viewed through MLVFS.  I realize that one of the main points of using MLVFS is to eliminate the need for doing this, but there are scenarios where some might prefer the workflow of baking white balance, luts, etc into a MOV for both space savings (deleting the orig mlvs) as well as sharing with other systems not equipped to handle ML Raw.   That said, what you achieved with MLVFS is pretty incredible and although I'm just in the testing stage with it, I can see using it in much of my future workflow.

Modules Development / Re: MLV Lite
« on: April 21, 2016, 08:13:36 AM »
and what's wrong with MLVFS + DR12 for quick previews @platu?

No doubt that MLVFS is amazing.  But there are just some things that MLRaw Viewer does that I prefer in my workflow.  It's not just quick previews.  As I said in my previous post, I'm not complaining.  Just adding my observation that MLV lite is not compatible with it.

Modules Development / Re: MLV Lite
« on: April 18, 2016, 11:42:19 PM »
Just tried the latest MLV Lite build on my 5D3 and the speed does seem comparable to the last nightly.  I've long wished to be able to use the extra features of MLV, but like some others, felt the performance tradeoff was an issue.

Also, as others have reported, I too am not able to use MLraw Viewer with MLV Lite files.  I just get a black screen.  I realize that MLraw Viewer is no longer being updated by the original developer, but for me, it is still the fastest way to work with ML raw files.  It has become quite an important piece of my workflow.  While I love the idea of consolidating the .raw and .mlv formats, it would be difficult to lose the real-time previews, exposure, white balance adjustments, and lut/log output of MLraw Viewer in exchange for this.  Not trying to complain, just pointing out something that may effect others who also have come to depend on MLraw Viewer as part of their workflow.

Regardless, good job to all the involved devs in refining the standard for ML raw.  Your work is very much appreciated.

General Development Discussion / Re: Bars facelift
« on: October 02, 2013, 06:14:39 PM »
Great work on the updated bars. 

A few things I noted...

-The shutter speed on the bottom bar doesn't match the one in the menu (shows as 1/51.3 in menu... and 1/63 on bottom bar).  This issue occurs in movie mode only... photo mode is fine.

-The temperature indicator on the top bar shows a caution condition relatively quickly so most of the time shooting, you will end up with a bright colored indicator always on.  Maybe the threshold for the caution indicator should be relaxed a bit.  My settings... movie mode, raw zebras, focus peaking, histobar all turned on.

The time indicator disappears quite often I assume to dynamically make space on the bar.   I have both Histobar and Ettr hint active.  It happens whenever the ETTR hint displays a negative value such as -0.1 but when the value is positive, the time indicator reappears.  So you end up with the time dissapearing and the histobar and everything else shifting to the left whenever the ETTR hint shows a negative value.  Again, this occurs only in movie mode.... photo mode is fine.

Wow mate!

This is the clearest video coming off the 5DM3 I have ever seen.

Approaches Alexa quality imo.

See here an additional comparison of Normal raw video "Denoised" vs Dual ISO raw video.

Wow... so clever!   And so useful!!  Thank you for your work on this and for the in depth technical docs.

As long as the demosaicing/debayering done from ACR is FAR superior to any other debayering process/software currently available, I can not understand what you mean with "ACR workflow not being suitable for any serious work".

I will not choose convenience over image quality, NEVER !

Agree completely with this.  I like everyone else, am looking for a faster workflow, but the difference in debayering quality is quite significant and no other workflow method seems to provide the level of quality ACR attains.  Sigh  :(

General Help Q&A / Re: [SOLVED] POST DEFLICKER with XMP
« on: June 17, 2013, 01:15:52 PM »
Alex, I just shot a sunset timelapse using the combination of ML intervalometer, silent pics, XMP post deflicker, and Auto ETTR (always on).  This combination works really well, with the bonus of saving shutter actuations.  The only thing I did notice is that in the 25 second timelapse I did, there were 6 specific frames (mostly spread out) that the exposure adjustments were off, causing noticeable flicker in those 6 spots.  I had to manually correct those frames.  I didn't use an ND so my shutter was at 8000 to start, eventually dropping to 640, than 360, and ISO remained constant at 100 till the end.  I have a feeling that the 6 times where the XMP exposure adjustment were off may have corresponded to same moments when the shutter needed to change due to Auto ETTR.  I just can't be sure without having a way to match the drops in shutter speed to the incorrect XMP exposure adjustments.   Since shutter, ISO, etc. are not written to the DNGs, maybe both shutter and ISO can be written to the XMP.  With that, I would be able to verify my theory.

Edit:  Here's the timelape I did with the 6 frames already corrected.  No flicker... pretty much auto mode for timelapses.

Modules Development / Re: [DONE] Port CHDK file browser
« on: June 17, 2013, 03:40:42 AM »
Ok... thanks.  Will use a separate Canon folder for each timelapse and that should suffice.

Modules Development / Re: [DONE] Port CHDK file browser
« on: June 16, 2013, 07:37:06 PM »
Just a few observations about the file manager module...

I spent a few hours shooting both raw video as well as a couple of timelapses.  The timelapses were short, only 360 shots each (using silent pics) plus associated xmp files.  In total, about 1500 files plus 20 raw files.  As others have mentioned, it takes a very long time for directories with a lot of files to open.  So long that it makes it a bit impractical to review/playback files between takes.  In order to try to solve this while I was out filming, I decided to use the move files feature to move the timelapse related files to another folder on the same CF card.  But this turns out to be a very long process as it seems to behave more like a file copy with regards to time than a move.  I suggest the following...

1.  To make this a more workable solution, is it possible for the move operation when performed within the same card only modify the file allocation table (for fat32 and exfat)?  If that's already what it's doing then disregard this suggestion.

2.  If the above is not possible, could files created via the intervalometer be automatically created in subfolders?  Each intervalometer based operation would be saved in its own subfolder.  This would allow viewing of standard raw files without the slowdown that currently exists.  This would be ideal since it would not only solve the speed issue, it would allow for logical grouping of timelapses in a way not possible at the moment.

General Help Q&A / Re: [SOLVED] POST DEFLICKER with XMP
« on: June 16, 2013, 04:32:13 AM »
Eureka!  Problems with XMP solved

I can now modify my xmp files.  My camera was set one hour ahead of my computer time.   Anytime I messed with xmp the edit time was set 1 hour earlier then the created time and ACR would not read the files.

I can now read my xmp files in ACR 100% of the time.  I had an issue with the Bulk Rename utility because I was modifying the name of the CR2 file.  This put a modified time stamp on this file which was later then the XMP file.  Now I rename my xmp files and also use the option in Bulk Rename Utility to set my time stamp of Date Modified to Current Time.

LEARNED LESSON No 1: Make sure your camera time is not ahead of the computer time.

LEARNED LESSON No 2: If the name of your CR2 file does not agree with the xmp, change the XMP always.  In this manner the xmp will be modified after the CR2.  If you do it the other way ACR will not read the files.

Have you tried XMP files that are now generated for silent pics?  I shot a timelapse using intervalometer + silent pics... the XMP files were generated but ACR, Lightroom, or After Effects didn't seem to pick up the exposure adjustments from the XMP.   This is a very new commit so I'm not sure if it's just me or something that doesn't function properly when the files are DNG+XMP.

EDIT:  I now see that this is a small problem with the XMP code which Audionut just identified.


Magic Lantern 14 Bit RAW vs H.264 Time-lapse test, using ML FPS override function.
Canon 5d Mark iii, 24mm, f/22, .500 fps, ISO 125 w/ND, playback @24fps.

Nice one.  What was your shutter?

With the newest commit of

xml_cfg: a module XML config save using mxml library

Does this mean that when I turn on raw video and set aspect ratio, when I turn off my camera and turn it back on, Raw video and the aspect ratio that I set before I turned it off should still be set???

No... appears that the basic infrastructure to support recalling module settings upon startup has just been put into place.  So far, only the Bolt module supports it.

Share Your Videos / Re: Magic Lantern Bolt in Raw
« on: June 09, 2013, 08:11:41 PM »
hey cool, now just the lightning bolt itself is mising :D
but here i germany didnt even have a single thunderstorm for months now, so you are quite ahead of me :)

Can you make a module to control the weather?

Feature Requests / Re: Option to remove crop box
« on: June 08, 2013, 04:38:42 AM »
In 5x it's not displayed...

Just realized that it works like this starting with yesterday's changes.  For HDMI monitoring, it's enough for me to stay in greyscale preview mode since that mode doesn't exhibit the crop mark issues and displays in realtime full color.  Thanks Alex.

Feature Requests / Re: Option to remove crop box
« on: June 08, 2013, 12:15:49 AM »
Enable grayscale display and you don't get a cropbox, because the image it's zoomed.

In 5x it's not displayed...

I didn't try it yet on HDMI.

Yes, it works fine when in greyscale preview as you mentioned, it's just that I always work in Canon preview.  The issues with hdmi also only happen when in Canon preview.  I didn't really expect you would work on HDMI issues at this point.  Not a biggie.

A few additional notes regarding HDMI for future reference...
- Greyscale preview is not transmitted via hdmi.. so it acts essentially like Canon preview.
- Raw playback does not work via HDMI... locks up the camera.
- Raw Zebras not working correctly
- Raw histogram ETTR hint not accurate


i know that there is no need for a profile when shooting raw, but there must be some specs cause the blackmagic cinema camera raw material looks really quite different.

wouldn´t it be useful to simulate that "flat raw picture style".. ?
have seen some really great material from the bmcc and there are some luts in resolve for getting great color and great contrast with a lot of detail..


The raw image that get recorded on the canon dslrs is the unprocessed raw data feed coming from the sensor.  It is just intercepted by ML and written straight to the card.  Any additional processing on this feed to create a more log-like look straight to card would require aditional pre-processing which would likely affect write speeds which can barely keep up as it is. Most development seems to be focused on optimizing and stabilizing the existing process to make it rock solid. 

Raw Video / Re: How to record: -- RAW Digital Cropped Video on 5D3 --
« on: June 07, 2013, 09:45:52 AM »

Raw Video / Re: How to record: -- RAW Digital Cropped Video on 5D3 --
« on: June 07, 2013, 09:40:46 AM »

Now it's as easy as moving the focus box wherever you want, pressing zoom and recording.


I hoped you'd get there.  Big improvement in usability.   :D

Does this mean that if the focus box is in the center of liveview, a crop occurs from the portion of the frame coming from exact center of the lense?

Pages: [1] 2 3 4