Messages

At what bitrate is the stream coming out of the 5d Mark III? In other words, how much Mbs is uncompressed/clean?

Yes, it seems the whole project is stalled for whatever reason. But I can't believe that this here is a one man show and if a1ex has other things to do, it breaks. Or am I wrong?

@Walter Schulz: No, the 5dMark III 1.2.3 latest build is from August 7th.
But I anyway, I used the word branches in a misunderstanding way. What I meant was, that the builds for different cams are not the same date and that there are no new ones.

Hi,
does anybody know why there are no more nightlies for the 5dII 1.2.3 since August? Other branches get updated, so it does not appear to be a complete stall of the development...

kontrakatze

Hi,
I don't know if this would be possible:
Sometimes I very much like to change the aperture during recording, adding a subtle effect of drama to some scenes. But the problem is, with a change of aperture the brightness changes too. Would it be possible to combine Iso-settings to aperture settings, so that there would be no blinking while changing the aperture, or to minimise blinking?
It would be so nice to change the depth of filed without any brightness flickering.

Regards,
kontrakatze

@Sebastian: I think your forum is actually a more general one. For example, the hardware section appears to be about hardware in general, which does not help in this case. And in addition you have three things, the general forum, the wiki and the bugtracker/proposal list, which are all seperate and it is not very easy to get an overview, or just find the looked for information. Another example, the information about the different lens mounts can not easily accessed from the main wiki page, or at least I didn't find that link. Different accounts for each system doesn't help eather.

I think that needs to be more structured

Wouldn't it be nice to set up a separate forum to discuss things like that? Proposals could be discussed and voted for. And it would be more easy to follow the discussions in a transperant way. The Wiki is nice, but should be reserved for finalized ideas.

About 90% of the shootings I do are somewhere out in the wild, may it be a National Park in Norway or somwhere in the Alps. Therefore size and sturdiness matters a lot. It's no fun to walk with a backpacker of 25kg weight up to a summit just to know, that if it is drizzling you are out for nothing.
Same is for a quick shooting in a city like Venice, where you have to walk all the way. Sometimes I feel like one of those guys in Halo packed with gear.

Regards,
Kontrakatze

I too think a solid sata interface or the like would be much better than three experimental hdmi interfaces. What is a nice sensor with capabileties of 4k 300fps good for, if I can't capture the data? May it be internal or external.

In addition the rising cost for a working system are not promising (active ef mount, battery mount, recorder interface, display, recorder).

Regards,
Kontrakatze

@kichetof: Thank you very much for your help! I can't do this as I simply don't have the knowledge, but I read the passage you were talking about. Having in mind that this happened about 6 month ago, I don't think they are going to change anything. A workaround is to export the dng from lightroom as new dng. Then the missing "optional" tags are in the new dng. Not smooth, but working.
(in the end, it is quite funny that most applications that create dng's add these "optional" flags, which makes it quite a standard?).

Regards,
kontrakatze

[If you are going to pass on the needed tags to the Magic Lantern people, these are the missing tags:CFAPlaneColor tag 50710CFALayout tag 50711]

I still have a problem, which I think is not directly related to your script, but maybe you know a solution.

After importing a dualiso raw file into lightroom and conversion using your script (either way using 20-bit or classic) the dng's open fine in lightroom, but not in other programs. I very often use Photomatix for example which opens the dng's with a terrible magenta cast. To work with it I have to export the files after conversion using the dng profile from Lightroom, making a dng from a dng. I already contacted the developers of Photomatix and send them an example file. The problem seem to be some missing tags in the dngs created by cr2hdr, I guess. I don't know what to with it, but this is what they told me:

If you are going to pass on the needed tags to the Magic Lantern people, these are the missing tags:

CFAPlaneColor tag 50710
CFALayout tag 50711

The magenta cast is also visible in the finders preview. Maybe it is of some help anyhow.
By the way, your new version of the script is a huge improvement, chapeau!

Regards,
kontrakatze

Oh, thank you! I took a look into the package and found them 

By the way, why do I get a message stating: "catalog has to be updated to use this new plugin"
I'm not quite sure if this was exactly what it said, as it appeared only once.

Regards,
kontrakatze

Hello,
to test the new version, do I need a current version of the cr2hdr package for osx and does anybody maintain this package? Mine is still from 4th of October 2013 and I can't find any newer anywhere.


Regards,
kontrakatze

Hello,
I shoot quite bit of photos using dualiso and am developing them on my mac. The lightroom script is very nice, but on the mac I see a problem using the commandline tools for more interactivity (mainly me not realy understanding how to work with them or installing). That is why I thought using one of the already existing (commercial) programs might ease the workflow for me. So, I asked one company if they wouldn't be interested in supporting dualiso dng's. They told me that they don't know exactly, but that the dng's would lack two different tags to be opened correctly to start with.

These tags are:
CFAPlaneColor tag 50710
CFALayout tag 50711

I absolutely don't know what to do with this, but thought it might be of interest for everybody to pass on this information. I hope I didn't do anything wrong.

Regards,
Kontrakatze

Sorry, just read that this problem is solved...

Regards,
Kontrakatze

I found another issue regarding mlv_play in conjunction with the follow focus option.
If mlv_play is loaded, recording started, the starting point for the follow focus saved and the second  focus point set, pressing the play button to play the focus sequence in the first time leads to no reaction, a second press on the button crashes my camera. After taking out the battery ml starts again with all settings reset. I repeated this several times on my 5d mark III 1.2.3
It appears as if mlv_play tries to play back a file while recording.

Regards,
kontrakatze

I'm having some issues with the latest nightly (2014-07-04).

Trash button to enter magic lantern menue sometimes works, most of the time it is not working. I just get the first ml screen, but if I press the trash button and next half shutter, I enter the ml menue.

Automated follow focus with mlv_viewer loaded crashes the camera when pressing play to start the folllow focus ramping while recording. I'm not sure if this was an issue before, because I usually used the filemanager instead of the mlv_viewer before. Without mlv_viewer loaded everything works.

Audiolevel indicater within the ml menue with mlv_snd enabled is stuck.

I installed this nighly on a clean cf-card without any older prefs on it.

I gave the new luts a quick try with realy bad starting settings (almost no light, my son sitting bored in a chair waiting for the soccer match to begin), too. Very impressive, indeed! Finally there semms to be no need to use ACR any longer, which is a huge speedup. In Addition, filmconvert in DaVinci semms to work much nicer. Fact is, it put a big fat smile on my face, which it never did before without a LOT of tweaking.

Also not quite sure where and how to drop in the PFE logs, but that is not my primary goal anyway.

You did a great job and these luts are worth evey penny paid (and even more, to be true).

Regards,
Kontrakatze

As far as I see it now, the best way seems to be:
Mlv --> dng --> acr with cinelog lut --> davinci --> cinelog to rec 709 lut --> filmconvert plugin from within resolve with arri alexa r709

But you have to pull the sliders for film color and curve down to something about 50%
The grain I usually take out completely as I don't like it - gorilla grain is much nicer in the end.

In my opinion FilmConvert works only if you just use it a tiny little bit, but than it can put in some magic.

In fact, it is quite simple.

1. Shoot something with the colorchart clearly visible
2. import into Davinci Resolve
3. on the color pane move to the preview window and choose "color chart" as a tool
4. drag, move, scale it to fit your recorded colorchart so that all squares are clearly within the squares of your recorded colorchart
5. on the color pane bottom left you can see the Color Match
6. set gamma and target color space to your needs
7. DON'T forget to adjust the Target Color Temp to fit your needs, otherwise you might get strange results
8. klick the button "Match"
9. Be happy...

The adjustments (highlights and so on) are quite useful, the Color Boost I always have pull down quite a bit.

I did exactly that and it works like a charm (colorchecker passport), but be aware to choose an appropriate target temerature. Otherwise some very moody candle light scences would look very strange 

Using chroma smoothing 2x2 results in colored dots (mainly blue) coming up in very dark areas if they are lifted. No problems without color smoothing on 5d Mark III.

Regards,
Kontrakatze

I think you haven't read enough. Sound is possible with mlv, shooting photos is also possible, why shouldn't it?

Take out the batterie for at least one minute, don't put in any card. After that time put batterie in again and turn it on. Does it work again?

Regards,
Kontrakatze

The full histogram is an option, but for me (as I'm farsightet, or have prebiopty) the ettr hint is hard to read. Maybe a customizable display would be a nice feature later on.

Regards,
Kontrakatze