Messages

Looking at the latest pictures of Audionut.

Looks to me  that there's more chroma noise in the ML pictures, but there should be less noise in the ML pictures according to the numbers in this topic ?

Sorry, the first ones are the ML picture and the second ones are the canons 
Clearly less chroma noise in the ML pictures 

The DR measurement was just to compare ML vs RawDigger.  Nothing serious.

Reducing negative gain (yes I was past calibrated result) fixed the WL, but here is a standard Canon ISO where ML reports a different WL to RawDigger.

https://dl.dropboxusercontent.com/u/34113196/ML/ADTG/_46A6566.CR2



Rawdigger

Code Select Expand

White 13956
Std.Dev 7.2


Found this thread after a lot of searching after the Tweet "Psst..." etc.
Looks promising, 1/3 or 1/2 stop of extra dynamic range (and less noise).

But this material raises a lot of questions to me ?

How is the dynamic range calculated with the black level, white level and st.dev (I know what St.dev means, but can it in this context literally be seen as a noise indicator ?)
In the example above the black level is 2049 and the white level is 13919 and a Stdev. of 9,3.
Does this mean that the sensor at that moment can roughly measure from values 2049=black and 13919= white which results in 11870 usable values (and are these number literally counted photons?)
What is the formula for the dynamic range with these numbers ?

Does anyone know already if this stuff is related to the temperature of the sensor ?

Somebody told me a way to do the edit in RAW therapee without the command line.

You can select multiple images in RAW therapee with the "Ctrl  A" key combination.

Edit one picture, copy current processing profile to the clipboard (there's a button on the GUI interface in RAW therapee for this).
Use Ctrl A to select all the pictures in a folder and use the paste button to apply the processing profile to all the selected pictures.

Thanks for the info, ctrl-A works on the Mac version too 

Finally, now let's make some aliasing, noise free, sharp video's 

Looks like you will need to use RawTherapee - it's certainly what I use when I shoot raw on my 600D and it does a good job

I use RAWMagic to create the DNG sequence, then open up the first one on RAWTherapee, select  the option to remove dead pixels and then process it. That gives a 'corrected' 16-bit TIF file and a .pp3 file that can be used in the command line to do all the remaining DNGs.

If you are on a Mac, you can use

/Applications/RawTherapee.app/Contents/MacOS/rawtherapee -o "output_dir" -t -p "dir/filename.pp3" -c "input_dir_containing_DNGs"

You can import the TIF files into Resolve with no issues.

Hope it helps?

Aha, I was already wondering how to do the same correction in Raw-Therapee to a whole bunch of files.
(even started a topic:  http://www.magiclantern.fm/forum/index.php?topic=9836.0)

The command line way you're describing above, is that the only way ?
I could do that in terminal, but is that really the only way ?
In the GUI of raw-therapee you can copy your picture settings to the clipboard and past it on another file, isn't there a way in resolve to select ALL the pictures in one folder and then do the pasting ?

Hi fellow raw shooters,

Does anyone know how to edit multiple images in raw-therapee ?
I have a folder which contains all the DNG's from one sequence, I select one of them to edit (white balance, demosaicing etc), then I can copy the things I've edit to the clipboard, but then I'm stuck.
I can click on another picture and paste the edit on it, but I can't find a way or a button to select ALL the files in the folder at once and the paste the edit to ALL the images

Working on the latest Mac version of raw-therapee.

Used to work with Lightroom, but lightroom gives rather soft images compared to DaVinci Resolve.
Worked a while in DaVinci Resolve to find out that the demosaicing gives me more aliasing than lightroom. Especially with the Samyang 14mm lens (probably too sharp too handle)
Than I heard about Raw-therapee and the multiple options of demosaicing, tried it, WOW!!! Probably the best way to get rid of aliasing stuff.
But how do I batch process these images......

Not long, actual data is a few MB. The problem is if you get an asif did not stop error in MLV sound the wav will end up being huge. So for 6D. 1st wav is fine, 2nd wav asif didn't stop and you get the giant wav. In MLVbrowse it hangs on the last frame or maybe 1 before it and keeps extracting until the 4gb limit is reached.

Experiencing the same problem with my 6d (MLV-dump.osx, so on OSX platform).
When I'm filming now, I turn my camera off and on after every single clip, just to have sound (raw video WITH sound, which is an huge improvement!)
Will there be a solution for the "sound failed to stop, state 4" error problem ?

On 6d
working with the newest available build (11 december build for 6d). And the mlv-rec and mlv-snd module from yesterday (copied from the 5d build, from the download link in the 1st post.)
First clip is with audio and error free.
Every clip after the first one gives the error (audio failed to stop, state 4), in those files I can't extract a full wave file with MLV-dump.osx.

I'm I doing things right by using the 11 december build for the 6d and replacing the mlv-rec.mo and mlv-snd.mo file for the ones in available in the newest 5d build ?

That one is just as untested. Look here: http://builds.magiclantern.fm/jenkins

Ah found it, downloading it, thanks for the link 

I prefer this to be done by a 6D owner.

I'm not afraid of doing it (since I did the 600D and 50D ports via skype), but it's not easy, since each camera has its own set of quirks. These are best handled by somebody who is actually using that camera. There are people in the community who have both a 6D and the necessary skills, but time and motivation are probably an issue. ML is a spare-time project, after all.

Ah I see, no 6d, so you're builds would be none tested/checked at all, not even by yourself. 

In that case, is there anywhere still a link to the "magiclantern-v2.3.NEXT.2013Dec11.6D113" build, which is mentioned in this topic ? Can't find it anywhere and the latest build I is the tragic lantern build from 30 november. I'm experimenting with the new sound recording function with MLV raw recording, but it only works with the first clip, after that I get a "sound recording failed to stop, state 4" error.
Reading through the topic, the build I'm using could be too old (tragic lantern from 30 november)

As long as there's still some progress on the MLV recorder and sound recording module for MLV I'm still interested in new builds.
If it won't take too much of you're time, would it be possible to make, once a month a newer build and only post the link on this topic, where you mention that there's nothing tested at all.
And if there's nothing new happening on the MLV module or dual iso module (think there still working on that one too?), then a new build won't be needed I guess.
The other magic lantern function on the 6d are already working fine, so won't expecting something new there. Even the raw recording (not the MLV type) works fine, no progress needed/possible there.
I think that's the main reason why most people are satisfied with the already existing builds.
But sound recording with MLV recording would be something new and fantastic, that's why there's some need for newer builds

I bet nobody tried them in the last month or two, so I've removed them from the download page.

Last update on 6D codebase in the main repository was done by me, on 2013-09-24. I've tried to merge some changes from 1%, blindly, without being able to test them on the camera. Of course, without any sort of feedback I can't maintain the 6D port, so I moved it to "unmaintained" state until somebody will jump in and bring it back to speed.

Hi Alex,

Are you saying that if you get enough feedback on 6d builds,  you will maintain nightly builds of the 6d ?
I think there are (now the nightly builds are gone) enough 6d users who are happy to report feedback.
Is it an idea to start a new 6d development topic and claim in the first post that there should be at all time a minimum number(10 ?, 20 or more ?) of active users who download and use the newest builds and give feedback in the topic about bugs ?

P.S. happy magic lantern user on the 6d since september 
I just signed up for the forum this month because it looked like 6d development was dying and users needs to be more seen in the forum 

Is there anyone here who did some testing with their 6d and the MLV-rec module and the new sound module ?

http://www.magiclantern.fm/forum/index.php?topic=7122.1025

I'm using the tragic lantern build from 30 November and the new MLV-rec and sound build from the topic above.

The first clip after switching the camera on has sound recorded along with the raw clip. Every clip after it doesn't have sound and shows the error message "sound failed to stop, state 4".

Did anyone here some testing with their 6d and the MLV-rec module and the new sound module ?

http://www.magiclantern.fm/forum/index.php?topic=7122.1025

I'm using the tragic lantern build from 30 November and the new MLV-rec and sound build from the topic above.

The first clip after switching the camera on has sound recorded along with the raw clip. Every clip after it doesn't have sound and shows the error message "sound failed to stop, state 4".

I had the same problem. Newest build resolves this, just make sure sound recording is set to 48khz in the sound menu. This should help. Cheers

Thanks will check the newest build.

I see at the bottom of your posts that you also have 6d, do you use the new sound module and new MLV-rec  module with it, or did you only test it on 5d mark 3?

Hi, i still have problems with "lowered" and "slowed down" sound in my wav files (5d3). If you have everything synced all the time could you please tell me your settings in mlv tab? Thanks

Filmed some clips during the holidays and now I am editing I hear that my voice and other male voices do sound lower and slower (than they should be) and my wife and kids voices actually sounds normal ?
Could it be that there is something going on with the lower frequencies ?

On the 6d, every first clip, audio is recorded good.
Every clip after it, only has a very small audio file (just as long as the sync beep file would be), it contains normal audio though, but it's only 1 or 2 seconds long.
And it says "audio failed to stop, state 4".
When I turn the camera off and on, the first clip has normal audio, the next clips have the state 4 error message and a 1 or 2 seconds audio file.
Is there something in the ML menu that I need to turn on or off ?

I'm using the new MLV record and sound modules in tragic lantern build from 30 November, which is the most recent I can find for 6d.
There isn't a nightly build for 6d (does anyone know why there are no nightly builds for 6d ?)

Hi G3gg0,

If it won't take too much of your time, is it possible to put in some more horizontal video resolution options in the MLV module?
In some raw.rec builds there where options for 1792 pixels wide and 1664 pixels wide resolution.
The 1792 resolution is probably only used for 6d owners, but I happen to have a 6d and love the 1792 pixel wide clips. 

Further, THANKS for the audio recording in combination with raw video!
Works on my 6d (using the tragic lantern build of 30 November), audio clips are a little bit longer than video, but it seems in sync, it only records some more audio after video recording has stopped.

Seems to work now on 6D!

I had to turn OFF the FPS override function (It said so in a message at the bottom of the display, FPS override turns off most sound function settings...

Tested the new audio function in MLV on a 6d.

Got a real audio wav file, normal size, normal specs.
But when I play the audio file, there's no audio at all ? Not even noise, it's like it's recording without any real audio input...

Tested several options in the ML audio menu, like sound record: separate wav, sound record: normal, Input source: internal mic, Input source auto...
And all these options where tested with MLV sound: ON.

Anybody else tested it on 6d ?