MLV and RAW File Format Silent Pictures
With the latest full resolution silent picture development (http://www.magiclantern.fm/forum/index.php?topic=12523.0), saving these full resolution DNGs is still quite a slow process.
Now you can save these full resolution images in either of the raw video formats. This results in speeding up the saving of the images, and also provides the benefit of all images in a timelapse, being captured in one single file for post processing, rather than hundreds of separate files.
(https://bitbucket.org/dmilligan/magic-lantern/downloads/silent_mlv.gif)
source (https://bitbucket.org/dmilligan/magic-lantern/branch/fullres-silent-pics)
silent.mo (https://bitbucket.org/dmilligan/magic-lantern/downloads/silent.mo) Not for use with nightly builds, requires a build from the full-res-silent-pics branch
Some mlv/raw video converters may have trouble with the large frame sizes or OB areas.
You must load mlv_rec module to use the MLV option.
Intervalometer sequences and bursts will be stored in a single container (up to 4GB, then you'll get a .M00, .M01, etc.)
Rather than cluttering this thread with build requests, please request a build in this thread (http://www.magiclantern.fm/forum/index.php?topic=12608.0).
Work on 500D ;)
Quote from: dmilligan on July 20, 2014, 01:48:25 AM
Option to save using the raw video file format (much faster than DNG):
Would this have problem with 4gigs file size limit?
Can someone compile this for 5d Mark 2 so I can test it. Please :P
Maybe it will solve my 2 solid black frames problem.
Quote from: barepixels on July 20, 2014, 04:25:09 AM
Would this have problem with 4gigs file size limit?
No. Currently, writing isn't continuous. Each image is a separate raw file.
Quote from: dmilligan on July 20, 2014, 01:48:25 AM
Option to save using the raw video file format (much faster than DNG):
https://bitbucket.org/hudson/magic-lantern/pull-request/558/silent-pics-option-to-save-silent-pics/diff
Just post process with raw2dng as you would a raw video file
Thank you very much! Would you please to compile for 5d3 1.13.
BTW, what is "much faster than DNG" means? How many times?
Quote from: dmilligan on July 20, 2014, 01:48:25 AM
Just post process with raw2dng as you would a raw video file
How to process 500 files?
raw2dng each file name the 000000.dng
Quote from: Greg on July 20, 2014, 04:38:46 PM
How to process 500 files?
#!/bin/bash
for raw; do
dng="${raw%.raw}.dng"
if ./raw2dng "$raw"; then
mv "000000.dng" "$dng"
fi
done
call it like this: ./script.sh *.raw
got MLV done too, hooray for metadata!
https://bitbucket.org/hudson/magic-lantern/pull-request/558/silent-pics-option-to-save-silent-pics/diff
Quote from: dmilligan on July 21, 2014, 04:55:43 AM
got MLV done too, hooray for metadata!
am I understanding this right? full size silent pic with exif info? no freaking way!!!!!
please someone compile this for 5d mark 2 so i can test it out. please please.
Yep, I'll work on putting multiple frames in one mlv file when using intervalometer next
Quote from: dmilligan on July 21, 2014, 05:17:53 AM
I'll work on putting multiple frames in one mlv file when using intervalometer next
done: https://bitbucket.org/dmilligan/magic-lantern/commits/dcc3c2f8304529ec0392f2f73f8b3a77872b31b6
If you're running the intervalometer, all your frames will go into a single MLV file (till the 4GB limit, then you get a .M00, .M01, etc). I have not tested the 4GB limit thing and file splitting thing (takes too long ;)) so please test and provide feedback.
Danger: not tested, do not use this for anything serious! If your camera breaks you get to keep the pieces!
Warning: Do not use this module with nightly builds (except 60D)
You need an autoexec.bin compiled from the full-res silent pic branch with the correct EDMAC channels and skip offsets for your camera.
Hey dmilligan if you compile this for the 60D I would be happy to test this out...you know...for the good of the people.
unless of course this silent.mo is for the 60D...I'll check it out
Great! module works on 60D. I'll test the 4GB file split.
Thanks dmilligan.
trying on my 5d2
tcc: error: undefined symbol 'mv_fill_wbal'
tcc: error: undefined symbol 'mv_fill_rtci'
[E] failed to link modules
What I did was take mk11174's
https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul19.5D2212.zip
and swap out the silent.mo
Quote from: barepixels on July 22, 2014, 06:40:11 AM
trying on my 5d2
tcc: error: undefined symbol 'mv_fill_wbal'
tcc: error: undefined symbol 'mv_fill_rtci'
[E] failed to link modules
What I did was take mk11174's
https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul19.5D2212.zip
and swap out the silent.mo
Same error on my 60D, compiled from main branch and replaced silent.mo
Quote from: barepixels on July 22, 2014, 06:40:11 AM
trying on my 5d2
tcc: error: undefined symbol 'mv_fill_wbal'
tcc: error: undefined symbol 'mv_fill_rtci'
[E] failed to link modules
What I did was take mk11174's
https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul19.5D2212.zip
and swap out the silent.mo
Do you have the mlv_play and mlv_rec modules loaded too??? I think both have to also be loaded to make this link correct.
Quote from: mk11174 on July 22, 2014, 07:06:23 AM
Do you have the mlv_play and mlv_rec modules loaded too??? I think both have to also be loaded to make this link correct.
Ah, yes it works now
Quote from: mk11174 on July 22, 2014, 07:06:23 AM
Do you have the mlv_play and mlv_rec modules loaded too??? I think both have to also be loaded to make this link correct.
You are so right. I got it to work. Here you can see I have made 9 shots in a MLV file. The viewer am using is MlRawviewer v1.1.6
(http://199.167.201.88/screencaptures/fSe4A.png)
As you can see the EXIF info are there YAY !!!!
here is the problem, I can't seem to be able to convert the MLV to DNG
So far I have tried with:
MLV Converter 1.9.2
MLVMystic v0.5
both create empty folders with no files.
BTW the MLV file is 00000000.MLV. they are over expose and blurry pics while I held in front of computer screen while intervalmeter doing its thing (a shot every 5 seconds)
update:
over exposure problem solved. as alex instructed: exposure override must be on
am also able to extract the DNGs by drag and drop the MLV over mlv2dng.exe, which is located in MLV Converter 1.9.2/Tools/mlv2dng.exe The GUI fail but the exe works YAY
(http://199.167.201.88/screencaptures/lePP8.png)
EXIF is correct too: 1/6 sec; f/11; ISO 100
While this method does works. Here is the errors I get in mlv2dng.exe
(http://199.167.201.88/screencaptures/M3bey.png)
PS am using mk11174's https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul19.5D2212.zip
nightly build cause hard crash where I have to remove the battery
am guessing nightly build didn't have the EDMAC changes in the autoexec.bin
PS: huge thanks to dmilligan for making it MLV build
I have upload my MLV for those that want to play with it. It's 5 pics in a MLV (188mb)
https://dl.dropboxusercontent.com/u/63842491/00000004.MLV
Intervalomat + Silent Pics works great, puts the Frames inside a .mlv Container. But im gettin the same Error's inside mlv2dng.exe like barepixels. And like the image from him show's, there are some Blackborders in the Top and left of the Image after converting from mlv 2 dng.
@gcrook,
thanks, that data is very helpful
Quote from: barepixels on July 22, 2014, 09:30:50 AM
EXIF is correct too: 1/6 sec; f/11; ISO 100
Right now the shutter speed in the exif metadata is simply the shutter displayed on the screen which is
not actually correct. This needs to be fixed and figuring out the true shutter speed is going to be difficult.
Quote from: Attero on July 22, 2014, 12:36:15 PM
there are some Blackborders in the Top and left of the Image
You need to use this module with a build from the full-res-silent-pic branch that has the new correct EDMAC channels and skip offsets for your camera.
The module I posted will "load" with any recent builds, but if you don't use it with a build from the branch with the correct changes you will have problems actually trying to use it (except on 60D where there are no differences).
Do not use it with nightly builds
That's interesting dmilligan, I have a build I made myself from the 50D fullrespics branch and everything worked fine with correct centering with the silent.mo that I built. When I switched to your new module (while keeping the rest of my card untouched) the mlv saving function worked great, but I have black bars.
Went back and tested with your module saving in plain dng and the framing/centering are correct. Switch to mlv and I get black borders. Have two files if you want a look.
Quote from: dmilligan on July 22, 2014, 12:59:38 PM
@gcrook,
thanks, that data is very helpful
Right now the shutter speed in the exif metadata is simply the shutter displayed on the screen which is not actually correct. This needs to be fixed and figuring out the true shutter speed is going to be difficult.
You need to use this module with a build from the full-res-silent-pic branch that has the new correct EDMAC channels and skip offsets for your camera.
The module I posted will "load" with any recent builds, but if you don't use it with a build from the branch with the correct changes you will have problems actually trying to use it (except on 60D where there are no differences).
Do not use it with nightly builds
would a moderator or @brapodam please delete reply #160
Oh i see.Yes for the 60D i used the July 22 nghtly with the silent.mo you posted on post #153.So its ok to continue with 60D and July 22 nighly if i understand correctly?
I actually did the same with my 550D but with the silent.mo in mk11174 put in latest 60D build only with full res silent pics (no mlv).
Should i stop using that as well?
I have no means to compile the build for the 60D you say though,if someone has already done that and wouldn't mind posting a link to it
i would continue shooting further tests or any kind of test you or anyone else would like for me to do.
I dont know exactly what i have to do to set the center right to avoid black borders on the 600D when im using the newest silent.mo with Timelapse -> .mlv container. But im still very happy how it works without it. Im sure u will delet this minor bugs ;)
If there is anything i can do to help with my 600D let me know.
Quote from: dsManning on July 22, 2014, 01:17:52 PM
Went back and tested with your module saving in plain dng and the framing/centering are correct.
Confirm, in save as DNG mode, it centered without black bar
Hope someone can help get me on track.
I'm running the FF silent.mo on my 5DIII 123.
I'm using the MLV route.
I get my timelapse MLV packaged OK and mlv2dng.exe works fine: however, on the left and top image areas I have black offsets.
I thought I had used the correct versions of everything.
Can someone point me at the correct ML files to use with the 123 firmware on the 5DIII. I fear I'm out of sync somewhere.
Thanks in advance, and sorry to be a pain.
Quote from: gcrook on July 22, 2014, 01:55:00 PM
Oh i see.Yes for the 60D i used the July 22 nghtly with the silent.mo you posted on post #153.So its ok to continue with 60D and July 22 nighly if i understand correctly?
I actually did the same with my 550D but with the silent.mo in mk11174 put in latest 60D build only with full res silent pics (no mlv).
Should i stop using that as well?
I have no means to compile the build for the 60D you say though,if someone has already done that and wouldn't mind posting a link to it
i would continue shooting further tests or any kind of test you or anyone else would like for me to do.
I've used a self-compiled build from the main brach with dmilligan's silent.mo on my 60D without any problems, but I've compiled a build from his branch, and here's the link:
https://www.dropbox.com/s/yhevc9pkdkhuvsp/ML_60D.zip
Interestingly enough, I've had a weird bug with the build from his branch, but I think it's unrelated. After shooting a short test "time lapse", my camera refuses to take pictures, and the live view button has decided it would function as a AF mode toggle instead. A battery pull fixed the problem though.
Quote from: brapodam on July 22, 2014, 03:25:27 PM
I've used a self-compiled build from the main brach with dmilligan's silent.mo on my 60D without any problems, but I've compiled a build from his branch, and here's the link:
https://www.dropbox.com/s/yhevc9pkdkhuvsp/ML_60D.zip
Interestingly enough, I've had a weird bug with the build from his branch, but I think it's unrelated. After shooting a short test "time lapse", my camera refuses to take pictures, and the live view button has decided it would function as a AF mode toggle instead. A battery pull fixed the problem though.
Thank you i will test this.
Cheers.
Quote from: dsManning on July 22, 2014, 01:17:52 PM
Went back and tested with your module saving in plain dng and the framing/centering are correct. Switch to mlv and I get black borders. Have two files if you want a look.
thanks, I may have left out some field in an mlv chunk header, I'll have a look.
Just wanted to add: I was getting err 70 & raw file error message because I had raw video enabled (on) in the ML menu. Once I turned this off everything worked as previously mentioned.
@dmilligan
Quote from: dmilligan on July 22, 2014, 04:42:51 AM
done: https://bitbucket.org/dmilligan/magic-lantern/commits/dcc3c2f8304529ec0392f2f73f8b3a77872b31b6
I have tried to build the full res silent pics branch for 500D, replacing "silent.c" with your modified version, and building for the silent.mo fails:
Building module silent...
REBUILDING
[ README ] module_strings.h
[ CC ] silent.o
[ MODULE ] silent.mo
[ STRIP ] silent.mo
[ EXPORTS ] silent.sym
[ DEPENDS ] silent.dep
Will NOT load on:
500D (mlv_fill_expo, mlv_fill_rtci, mlv_generate_guid, and 7 others)
Not checked (compile ML for these cameras first):
1100D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 6D, 700D, 7D, EOSM
make[3]: *** [silent.dep] Error 1
********************************************************
WARNING: module silent failed to build, deleting
********************************************************
If I build the branch with the unmodified "silent.c", the module builds Ok, and full res silent pics work in camera.
Any thoughts, what could be the problem?
Quote from: dmilligan on July 22, 2014, 04:42:51 AM
You need an autoexec.bin compiled from the full-res silent pic branch with the correct EDMAC channels and skip offsets for your camera.
I think this is already done for 500D:
https://bitbucket.org/hudson/magic-lantern/pull-request/530/500d-switched-raw_photo_edmac-to-the-one/diff (https://bitbucket.org/hudson/magic-lantern/pull-request/530/500d-switched-raw_photo_edmac-to-the-one/diff)
you need to compile mlv_rec
I need to make all the references to mlv_rec functions WEAK_FUNC so that the module will still work without mlv_rec (it just won't be able to save mlv)
Quote from: dmilligan on July 22, 2014, 10:04:28 PM
you need to compile mlv_rec
I have compiled all modules at the same time, I think, as I usually do:
magic-lantern$ make 500D
magic-lantern$ cd modules
magic-lantern/modules$ make
magic-lantern/modules$ cd ..
magic-lantern$ cd platform/500D.111
magic-lantern/platform/500D.111$ make
magic-lantern/platform/500D.111$ make install
When I build the unmodified fullres-silent-pics branch, and test it on camera, mlv_rec module loads without problems, and mlv video recording works. (with a maximum resolution of 860x486. due to SD bus bandwith limited to 21 MB/s)
Latest:
I have reloaded the 5DIII-123 (full) build from this thread, ie replaced all the other ML files, and downloaded the silent.mo from this thread that does MLV.
Strangely I still have the left & top black 'bars'/offsets.
Can someone see what am I doing wrong?
@josepvm
You need to compile mlv_rec before silent.
MLV full res not remove the black borders:
(http://s1.postimg.org/rcl6gqcr3/000001.jpg)
Quote from: Greg on July 22, 2014, 10:37:37 PM
@josepvm
You need to compile mlv_rec before silent.
Ok, thanks.
I have edited "Makefile.modules.default" and seen that "silent" was placed before mlv_rec.
Moving "silent" to the end of the line, the build works.
And the resulting module works in the camera. Saving many silent pics in a single .mlv file is a very useful feature, and works nicely. I do not see any black borders.
I have spent hours trying every permutation of downloads and settings (on my 5DIII-123), but still have the dreaded off centre black bars.
I used the silent.mo from here: https://bitbucket.org/hudson/magic-lantern/downloads/silent.mo
And from here: https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul18.5D3123.zip
Would one kind person using FF silent on a 5DIII-123 and not getting the black bars point me in the right direction.
As I say, it all looks OK other than the bars.
Cheers
Garry
for those getting black bars, please post the output of mlv_dump -v
you should see something like this:
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 17136314949046505859
FPS : 1.000000
File : 0 / 0
Frames Video: 1
Frames Audio: 0
Block: RAWI
Offset: 0x00000034
Size: 180
Time: 9.281000 ms
Res: 5344x3516
raw_info:
api_version 0x00000001
height 3516
width 5344
pitch 9352
frame_size 0x01F5BBE0
bits_per_pixel 14
black_level 2045
white_level 14803
active_area.y1 50
active_area.x1 142
active_area.y2 3516
active_area.x2 5344
exposure_bias 0, 0
cfa_pattern 0x02010100
calibration_ill 1
Notice the OB areas are accounted for in the 'active_area' settings, 50 from the top, 142 from the left (on my 60D). When I use mlv_dump to convert this to DNG, I get a correct DNG with the OB removed (no black bars). So, if you have black bars it means one of two things:
1) your MLV converter program of choice is not respecting the active_area of the RAWI chunk and outputing the OB areas in the DNG,
2) the OB areas are coming in wrong from the ML raw backend and need to be re-calibrated
(the other possibility is that I was not writing them into the MLV file correctly, but that doesn't seem to be the case, I've checked)
You'll know it's #1 if you look at mlv_dump output and 'active_area' has some values that don't match the DNG you're getting (e.g. DNG width should be active_area.X2 - active_area.X1). You'll know it's #2 if the converted DNG appears to match 'active_area' but there are still black bars.
If you're using something besides mlv_dump then I'd say #1 is the most likely. Most normal raw videos don't have OB areas, so some converters might be ignoring the 'active_area' settings (you should submit a bug report to the author of the converter).
im running the july 18 build on the 5d3 123 and keep getting Raw Error, no file saved, can somebody helm me?
hey sdesign is you raw video set to 'off' ?
Quote from: dmilligan on July 23, 2014, 03:16:47 AM
for those getting black bars, please post the output of mlv_dump -v
...
When I use mlv_dump to convert this to DNG, I get a correct DNG with the OB removed (no black bars).
Me too, as I posted earlier, I do not see any black borders in my 500D tests. Intervalometer saving in mlv file, and using mlv_dump (mlv_dump --dng *.MLV) to extract the DNGs.
The output for mlv_dump -v is very similar to the one you have posted. Here is the output:
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 5214970244131067897
FPS : 0.066667
File : 0 / 0
Frames Video: 6
Frames Audio: 0
Block: RAWI
Offset: 0x00000034
Size: 180
Time: 23.117000 ms
Res: 4832x3201
raw_info:
api_version 0x00000001
height 3201
width 4832
pitch 8456
frame_size 0x019D0508
bits_per_pixel 14
black_level 1023
white_level 12932
active_area.y1 24
active_area.x1 62
active_area.y2 3201
active_area.x2 4832
exposure_bias 0, 0
cfa_pattern 0x02010100
calibration_ill 1
The size obtained substracting "active_area" values here, are:
active_area.x2 - active_area.x1 => 4770
active_area.y2 - active_area.y1 => 3177
Opening the DNGs with Darktable, the size of the images I get is exactly this value, 4770x3177
And these are the same values reported by ML on the camera screen when saving every fullres silent pic.
But Rawtherapee reports a sligthly smaller size for the images, 4762x3169, I don't know why ???
It's just Raw Therapy - from my limited experiments with it last year I found that it converts raw images a few pixels less than expected; whereas the same files brought into Adobe Camera Raw produce image frame sizes exactly as expected. Strange.
with mlv_dump work well, thanks! ;D
before use mlv2dng :o
When use the intervalometer -> Take pics -> like crazy
Each picture is a different file MLV
When use the intervalometer -> Take a pic every -> 1s
Each photo is in the same file MLV (work well)
Last night I asked josepvm to compile a fresh build for my 5D2. He did it by using build from the current "fullres-silent-pics" branch including the modified "silent.c" from dmilligan, for saving silent pics in mlv or raw files.
With his version I was able to create this MLV
https://dl.dropboxusercontent.com/u/63842491/00000001.MLV (188mb 5 pics)
on Windows 7 64 I was able to extract the 5 dngs using either
a) MlRawViewer_1_1_7
b) mlv2dng.exe found in MLV Converter 1.9.2/Tools/mlv2dng.exe
the DNGs from the above shows black bars
-------------------------------------------------------------
-------------------------------------------------------------
josepvm asked me to send him the https://dl.dropboxusercontent.com/u/63842491/00000001.MLV so he can "try to process it with mlv_dump, to see if this way the black borders are seen also."
here is his reply
I have processed the MLV, got 5 DNG images, and they do not show the black borders seen in your DNG.
This is one of the images I have processed from th mlv file:
https://www.dropbox.com/s/cdlu54kbtrlorub/00000001_frame_000000.dng
But there is an issue. When processing your mlv with mlv_dump I got this error:
mlv_dump --dng *.MLV
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000001.MLV'
- Convert to DNG frames
- Output into '00000001_frame_'
File 00000001.MLV opened
File 00000001.M00 not existing.
Processing...
Vertical stripes correction:
1.000 1.000 1.006 1.007 1.002 1.002 1.006 1.004
Reached end of chunk 1/1 after 37 blocks
Processed 5 video frames
*** Error in `mlv_dump': munmap_chunk(): invalid pointer: 0xf55ad008 ***
Aborting ( kernel image dump)
The 5 files have been already extracted before the error occurs, and they look all fine. But I do not see this errors when processing my own mlv files. The output I get is:
mlv_dump --dng *.MLV
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Convert to DNG frames
- Output into '00000000_frame_'
File 00000000.MLV opened
File 00000000.M00 not existing.
Processing...
Reached end of chunk 1/1 after 30 blocks
Processed 4 video frames
Done
josepvm explain that his copy of mlv_dump is build by himself from source, ML unified branch.
But is a Linux version, he use Linux exclusively. It will not work in Windows.
-------------------------------------------------------------
-------------------------------------------------------------
When I try to use the mlv_dump that came with MLV Converter 1.9.2 for windows OR from
http://www.magiclantern.fm/forum/index.php?topic=7122.0 this is what I get
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: 'D:\2014-07-23-Sillence-Full-MLV\00000001.MLV'
- Convert to DNG frames
- Output into 'D:\2014-07-23-Sillence-Full-MLV\00000001_frame_'
File D:\2014-07-23-Sillence-Full-MLV\00000001.MLV opened
File D:\2014-07-23-Sillence-Full-MLV\00000001.M00 not existing.
Processing...
[b][ERROR] File ends in the middle of a block[/b]
Processed 0 video frames
Done
-------------------------------------------------------------
-------------------------------------------------------------
Am asking other developer to look at my
https://dl.dropboxusercontent.com/u/63842491/00000001.MLV (188mb 5 pics)
and see if you can extract DNGs without black bar like josepvm did with his Linux version of mlv_dump
Please state which OS and software you used. Thnx
@ barepixels
I think there is something wrong in your MLV file.
I succedeed to extract the DNGs with my linux "mlv_dump" build, but getting an error, as you have already posted.
Now I've tried to process your mlv file again with the windows version found here:
http://ml.g3gg0.de/modules/mlv_dump.zip/mlv_dump.zip (http://ml.g3gg0.de/modules/mlv_dump.zip/mlv_dump.zip)
I've used it from linux, with Wine emulator, and I get the same error you have found, I can't extract the DNGs:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000001.MLV'
- Convert to DNG frames
- Output into '00000001_frame_'
File 00000001.MLV opened
File 00000001.M00 not existing.
Processing...
[ERROR] File ends in the middle of a block
Processed 0 video frames
Done
The same version of mlv_dump.exe for Windows works fine with my own mlv files (on linux using wine, but should be the same in Windows)
HHmm... i tryed to use mlv_dump to extract my own .mlv . It worked, he sad "Processed 3 video frames" but he did not created anything. What did i wrong?
If i extract my .mlv with mlv2dng i got the black borders...
When i change the format inside the Camera to .DNG i got nice Images without black bars.
Using the 600D with the Nightlybuild from 19July together with the silent.mo from dmilligan.
Attero, what camera model do you have? what OS do you use? If your MLV is small enough, maybe you can put it on dropbox and someone who using Linux can try to mlv_dump and see if black border goes away
Windows 7 64bit, Camera like i wrote in the last Post.
This .MLV contains just 1 image. I have a very slow internet conection so the less MB the faster it goes ;)
https://www.dropbox.com/s/97ki94gildw70cx/37830000.mlv
Tell me if u can extract the .DNG without black bars.
Just an update everyone.
I asked josepvm to process an older mlv file that were made with mk11174 build (see post 17 on first page) and guess what
josepvm's linux version of mlv_dump produce DNGs with no black border
Here is what Josep wrote
Done.
Exactly the same behaviour.
With my Linux build of mlv_dump I can extract the 5 images and they look fine, no black borders. But I get the same error message:
Processing...
Vertical stripes correction:
1.000 1.000 1.008 1.010 1.000 1.003 1.005 1.005
Reached end of chunk 1/1 after 37 blocks
Processed 5 video frames
*** Error in `mlv_dump': munmap_chunk(): invalid pointer: 0xf5530008 ***
With the Windows version of mlv_dump, same behaviour also as with previous mlv file. I can't extract the images:
File 00000004.MLV opened
File 00000004.M00 not existing.
Processing...
[ERROR] File ends in the middle of a block
Processed 0 video frames
Done
This is the result, from the second mlv file I have processed for barepixels.
Using mlv_dump, Linux build. No black borders:
https://www.dropbox.com/s/i7l5ps0hy22pumk/00000004_frame_000000.jpg (https://www.dropbox.com/s/i7l5ps0hy22pumk/00000004_frame_000000.jpg)
And @barepixels: my name is "Josep". ;) Is a Catalan name. A little longer than the Spanish "José", but a little shorter than the English "Joseph" :D
Attero's file is correctly processed by mlv_dump for Linux.
No errors, no black borders in the resulting DNG:
https://www.dropbox.com/s/tw8yhg4u16687o9/37830000_frame_000000.jpg (https://www.dropbox.com/s/tw8yhg4u16687o9/37830000_frame_000000.jpg)
But this one can be processed also with mlv_dump.exe through wine, no errors, same results.
thnx Josep
confirm: I too were able to process Attero's MLV with no black border on Windows 7/64
(http://199.167.201.88/screencaptures/NCg7u.png)
Attero, use mlv_dump to proccess http://www.magiclantern.fm/forum/index.php?topic=7122.0
(http://199.167.201.88/screencaptures/T432R.png)
Ok, thats very interesting. So the Problem is not inside the Camera. Its the Converter, thats good.
And now. I used mlv_dump.exe, he sad "Processed 3 video frames" but he did not created any files. What am i doing wrong?
And, Thanks Josep!
yes, raw video is set to off.. is this my issue?
Ok, thanks for the screenshoot barepixels ;) Its working fine by me too, now ^^
I was not familiar with the cmd. I simply dropped the .mlv on the mlv_dump.exe :D
a simple Interface would be awesome! But what ever gonna happen. This is so teriffic a this point. Taking TimeLapse without killing the shutter, so nice!
This thread is starting to turn into a debugging and stress test of MLV converters :P
With barepixel's 00000001.MLV file my version of mlv_dump on osx crashes (and does not output any dngs), however, -v works and lists all the blocks correctly. I'm not really able to debug issues with mlv_dump because I can't compile it due to GCC issues with '-mno-ms-bitfields' (I'm on a Mac and Apple's flavor of GCC has dropped support for '-mno-ms-bitfields'). So I don't really know what's going on. Maybe the file is corrupt, or 'slightly' corrupt (missing some data at the end or something, IDK. Other files seem to be processing fine, so for know I'll consider this a fluke/issue with mlv_dump. MLRawViewer is able to convert it, but it doesn't respect the 'active_area' and the black bars are in the output
If you are getting black borders it's a pretty safe bet that it's your converter and not anything wrong with this particular module. Please submit posts to the relevant threads of those particular converters, not here (I already made a post for MLRawViewer).
Could someone please test the 4GB limit thing? (Just take more than 4GB of photos in a timelapse and make sure you get a .M00 file and that it converts correctly.) I have not had any confirmation that it is working.
Agreed. Gonna test the 4GB limit right now.
Camera is shooing in this moment.
btw. i notice a bug. After i took an Image i wasnt able to take a picture on the normal way. Then i turned the camera off and on again. Still bugged... But now i wasnt able to turn the camera off. I had to take out the battery. Then the camera startet "normaly" again. "no clean shutdown - no moduls loading" etc.
Any Ideas?
update: EXIF shutter speed should now be the time of FA_CreateTestImage (the time you see displayed on the LV screen), not the value set in the Canon menu (which is wrong). This value may be slightly longer than the true exposure time, but it's more correct than Canon menu shutter speed.
Ok. I took 150 Images á 31,5MB what schould be 4,725GB. I got 2 Files
File 1 --> 00000000.MLV (4.145MB)
File 2 --> 00000000.M00 (601MB)
What does this mean? Can i rename the File 2 to 00000001.MLV and everything is fine?
Quote from: dmilligan on July 23, 2014, 10:30:09 PM
Could someone please test the 4GB limit thing? (Just take more than 4GB of photos in a timelapse and make sure you get a .M00 file and that it converts correctly.) I have not had any confirmation that it is working.
Ok I tested (5D3, Win7) for over 4gb and it did create the separate 4gb chunks in camera (mlv... m00... m01).
But mlv_dump gives the following error trying to extract the DNGs. I was able to extract the complete set of DNGs using mlv2dng.exe however I do get the black bars.
E:\0001-MLVs>mlv_dump 00000001.mlv --dng
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000001.mlv'
- Convert to DNG frames
- Output into '00000001_frame_'
File 00000001.mlv opened
File 00000001.m00 opened
File 00000001.m01 opened
File 00000001.m02 not existing. (This is where is breaks... it is expecting m02 even though m01 is actually the last file)
Processing...
[ERROR] File ends in the middle of a block
Processed 0 video frames
Done
Edit: I just verfied that mlv_dump works fine extracting DNGs from regular video on my system.
Mine worked totaly fine. It extracted all 150 Frames perfectly.
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: 'K:\DCIM\102CANON\00.MLV'
- Convert to DNG frames
- Output into 'F:\abc\ML_TL_'
File K:\DCIM\102CANON\00.MLV opened
File K:\DCIM\102CANON\00.M00 opened
File K:\DCIM\102CANON\00.M01 not existing.
Processing...
Vertical stripes correction:
1.000 1.000 1.002 1.000 0.999 1.004 1.000 1.001
Reached end of chunk 1/2 after 919 blocks
Reached end of chunk 2/2 after 133 blocks
Processed 150 video frames
DoneWin7 64bit - 600D NB.July19+silent.mo(.mlv container) - mlv_dump
Edit: Just added the sequenz for inspection ;)
Live View Full Res (loop without writing) :
MA Visuals with 5D3, can you make a small MLV file and upload to dropbox so Linux and OSX users can try to convert with their mlv_dump
I have a feeling Linux user will be able to extract DNG without black bars just as for my 5D2
Quote from: Attero on July 23, 2014, 11:44:36 PM
Mine worked totaly fine. It extracted all 150 Frames perfectly.
Great, thanks!
Quote from: MA Visuals on July 23, 2014, 11:33:46 PM
File 00000001.m02 not existing. (This is where is breaks... it is expecting m02 even though m01 is actually the last file)
actually, there's nothing wrong with that, it's just telling you there's not a m02 (which there isn't). This appears to be the same issue barepixels was having with one of his files (mlv_dump thinks the file ends in the middle of a block). I suspect this has nothing to do with the 4GB limit or the spanning. It might be a bug in mlv_dump, perhaps something to do with the huge frame sizes of these full res pics (it normally handles much smaller frames), as other converters seem to handle it fine. maybe @g3gg0 has some ideas or can take a look at it (like I said earlier, I can't really debug mlv_dump here on a mac).
Quote from: dmilligan on July 23, 2014, 10:30:09 PM
I'm not really able to debug issues with mlv_dump because I can't compile it due to GCC issues with '-mno-ms-bitfields' (I'm on a Mac and Apple's flavor of GCC has dropped support for '-mno-ms-bitfields').
Install GCC 4.8.2 using macports (http://www.ficksworkshop.com/blog/14-coding/65-installing-gcc-on-mac).
This will also give you nested functions so you can compile cr2hdr if needed.
Phil.
Quote from: barepixels on July 24, 2014, 12:12:14 AM
MA Visuals with 5D3, can you make a small MLV file and upload to dropbox so Linux and OSX users can try to convert with their mlv_dump
I have a feeling Linux user will be able to extract DNG without black bars just as for my 5D2
Ok.. I'll post a link shortly.
In case anyone needs it for testing purposes, here's a small mlv file shot on the 5D3 containing just 5 full-res silent pictures inside... https://copy.com/7pc7Tla4SAqx (https://copy.com/7pc7Tla4SAqx)
MA Visuals file behaves the same way as barepixels files.
With mlv_dump for Linux I can extract the 5 images, and after that, I get an error:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000002.MLV'
- Convert to DNG frames
- Output into '00000002_frame_'
File 00000002.MLV opened
File 00000002.M00 not existing.
Processing...
Reached end of chunk 1/1 after 37 blocks
Processed 5 video frames
*** Error in `mlv_dump': munmap_chunk(): invalid pointer: 0xf5530008 ***
The images look fine, no black borders:
(http://www.arrakis.es/~josepvm/00000002_frame_000000.jpg)
I think this reinforces dmilligan's possible explanation: a mlv_dump bug when handling large images. The issue, so far, affects full frame cameras (barepixels 5D2 and MA Visuals 5D3), with images larger than 18 Mpix.
so who is the author for mlv_dump for windows. can they help investigate?
Quote from: barepixels on July 24, 2014, 02:27:41 PM
so who is the author for mlv_dump for windows. can they help investigate?
I think g3gg0 is the author of mlv_dump:
http://www.magiclantern.fm/forum/index.php?topic=7122.0 (http://www.magiclantern.fm/forum/index.php?topic=7122.0)
Quote from: Greg on July 24, 2014, 12:01:48 AM
Live View Full Res (loop without writing) :
Very fast ;)
Writing images in an MLV file, intervalometer set to 1 sec, my 500D takes 10 full res silent pics in 1 minute. This is, one pic every 6 seconds.
At 25 frames/sec for the final video, this means: 1 min video --> 2.5 hours real time. Not bad for some landscape timelapses, in my opinion (sunsets, moving clouds, etc).
I will experiment with it next week.
If I try to supress completely the intervalometer delay ("take pics like mad") every pic is saved in a separate file, as you have already posted. And this is not faster.
upload a file which reproduces the error.
5d2
https://dl.dropboxusercontent.com/u/63842491/00000001.MLV
5d3
https://copy.com/7pc7Tla4SAqx
both extracted fine on linux mlv_dump but fail on windows mlv_dump
thanks, fixed in repository
binaries here (http://ml.g3gg0.de/modules/mlv_dump.zip/mlv_dump.zip)
that's amazingly fast. thank you...
confirm it's fixed YAY!!!!
tested with 5D2 and 5D3 files
Quote from: barepixels on July 24, 2014, 10:05:44 PM
that's amazingly fast. thank you...
confirm it's fixed YAY!!!!
tested with 5D2 and 5D3 files
I can confirm it's fixed
I have built the latest code in the "unified" branch, that already includes the fixed "mlv_dump.c"
I also have built this file for Linux, and processed again barepixels and MA Visuals sample MLV files,
Works OK, the extracted images look fine, no black borders (this is like before, in the Linux build) but now I do not get any error, mlv_dump completes the job normally.
Now we only need that someone builds this fixed version for Windows and Mac ;) I can't do that, I don't know how to crosscompile from Linux :-\
--------------------------------------------------------
Edit: I see now g3gg0 has already done it :)
The Windows version works fine now with the problematic MLV samples in Linux through Wine
Tested (5d3) the updated mlv_dump on a much larger spanned set of files and all works well and no black borders. Thank you.
Has anyone succeeded to get a fullres silent timelapse in MLV format using ETTR ?
If I set ETTR as "always on", apparently the capture works, the ETTR autoadjusts the exposure to changes in scene lighting... but I cannot process the resulting MLV files.
With mlv_dump I can extract only one frame, and it is completely black. And I get an error:
Vertical stripes correction:
1.000 1.000 1 1 1 1 1 1
[ERROR] Invalid block size at position 0x019d06c4
Processed 1 video frames
Done
But "mlv_dump -v " says that all the frames are there.
This is the complete output of "mlv_dump -v --dng *.MLV" for a file with 101 pics:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Verbose messages
- Convert to DNG frames
- Output into '00000000_frame_'
File 00000000.MLV opened
File 00000000.M00 not existing.
Processing...
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 10537559721678771798
FPS : 1.000000
File : 0 / 0
Frames Video: 101
Frames Audio: 0
Block: RTCI
Offset: 0x00000034
Size: 44
Time: 843519.905000 ms
Date: 25.07.2014
Time: 10:01:14 (GMT+0)
Zone: ''
Day of week: 5
Day of year: 0
Daylight s.: 0
Block: EXPO
Offset: 0x00000060
Size: 40
Time: 843520.475000 ms
ISO Mode: 0
ISO: 100
ISO Analog: 72
ISO DGain: 0/1024 EV
Shutter: 500000 µs (1/2.00)
Block: LENS
Offset: 0x00000088
Size: 96
Time: 843520.534000 ms
Name: '1-65535mm'
Serial: ''
Focal Len: 300 mm
Focus Dist: 0 mm
Aperture: f/16.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x0000001B
Flags: 0x00000000
Block: IDNT
Offset: 0x000000e8
Size: 84
Time: 843520.550000 ms
Camera Name: 'ERR:1 md:0x 0 ml:0'
Camera Serial: ''
Camera Model: 0x00000000
Block: WBAL
Offset: 0x0000013c
Size: 44
Time: 843520.599000 ms
Mode: 0
Kelvin: 5000
Gain R: 1024
Gain G: 1024
Gain B: 1024
Shift GM: 0
Shift BA: 0
Block: STYL
Offset: 0x00000168
Size: 52
Time: 843520.611000 ms
picStyle: 133
contrast: 0
sharpness: 0
saturation: 0
colortone: 0
Block: VIDF
Offset: 0x0000019c
Size: 27067688
Time: 845473.718000 ms
Frame: #100
Crop: 0x0
Pan: 0x0
Space: 0
Vertical stripes correction:
1.000 1.000 1 1 1 1 1 1
[ERROR] Invalid block size at position 0x019d06c4
Processed 1 video frames
Done
If I set the "Silent pics" module to save individual DNGs for each frame, the timelapse series looks fine, ETTR does his job of continuously autoadjust exposure to changing light.
Quote from: josepvm on July 25, 2014, 11:57:21 AM
Has anyone succeeded to get a fullres silent timelapse in MLV format using ETTR ?
Yes, I have succeeded in shooting a simple test while using ETTR. I haven't used mlvdump though. I used the MLV batch converter from this thread http://www.magiclantern.fm/forum/index.php?topic=10198.0
It worked without errors for me
May I have the latest silent.mo module to test on the 550D, I only have to previous one without the file format options.
Quote from: brapodam on July 25, 2014, 03:05:51 PM
Yes, I have succeeded in shooting a simple test while using ETTR. I haven't used mlvdump though. I used the MLV batch converter from this thread http://www.magiclantern.fm/forum/index.php?topic=10198.0
It worked without errors for me
Thanks, I have not tried MLV Batch converter (I use Linux) but reading the thread you linked, It seems it is a GUI frontend for "mlv_dump" ?
Quote
I've been making this simple program in Visual Basic for the last few days. It is, like the title says, the first MLV to DNG batch converter for windows, which basically converts all your MLVs into different DNG folders. It has a lot of features, it is very simple and efficient. It runs from mlv_dump.
If this is the case, I suspect it will give me the same error I get with mlv_dump alone :-\
I will search for the available mlv converters, and give them a try.
---------
update: mlv2dng does not work either, with my mlv files when I use ETTR
Quote from: surami on July 25, 2014, 03:31:23 PM
May I have the latest silent.mo module to test on the 550D, I only have to previous one without the file format options.
You have the module in this previous dmilligan post: http://www.magiclantern.fm/forum/index.php?topic=12733.msg122887#msg122887 (http://www.magiclantern.fm/forum/index.php?topic=12733.msg122887#msg122887)
But be aware that you need also a complete ML build for your camera from the fullres-silent-pics branch. You cannot put the silent.mo in a regular Nightly Build, it will not work.
Ask for a fullres-silent-pics build for your camera here:
http://www.magiclantern.fm/forum/index.php?topic=12608.0 (http://www.magiclantern.fm/forum/index.php?topic=12608.0)
Quote from: josepvm on July 25, 2014, 04:28:54 PM
You have the module in this previous dmilligan post: http://www.magiclantern.fm/forum/index.php?topic=12733.msg122887#msg122887 (http://www.magiclantern.fm/forum/index.php?topic=12733.msg122887#msg122887)
But be aware than you need also a complete ML build for your camera from the fullres-silent-pics branch. You cannot put the silent.mo in a regular Nightly Build, it will not work.
Ask for a fullres-silent-pics build for your camera here:
http://www.magiclantern.fm/forum/index.php?topic=12608.0 (http://www.magiclantern.fm/forum/index.php?topic=12608.0)
Thanks for the link to the dmilligan post and for the warning.
I have this 550D nightly build created by mk11174 (https://bitbucket.org/mk11174/magic-lantern/downloads/magiclantern-Nightly.2014Jul18.550D109.zip)
(Mercurial changeset: 25735947ce04+ (fullres-silent-pics), built on 2014.07.18.
Is this ok for testing purpose?
Yes I know about that topic, I asked there too for the proper build.
Yes, this build is OK.
Hi Josep
I just tried ETTR and Full-res Silent MLV
the new mlv_dump were able to extract the DNGs fine
here are each DNGs EXIF info
1) 1/15sec f11.3 ISO 400
2) 1/15sec f11.3 ISO 200
3) 1/15sec f11.3 ISO 100
4) 1/15sec f11.3 ISO 100
5) 1/15sec f11.3 ISO 100
6) 1/15sec f11.3 ISO 100
7) 1/15sec f11.3 ISO 100
8) 1/15sec f11.3 ISO 100
9) 1/15sec f11.3 ISO 100
10) 1/15sec f11.3 ISO 100
So I guess ETTR is working.
These are the module loaded at the time of shooting
dual_iso
ettr
mlv_play
mlv_rec
silent
Note: am using the build you made for me. Which doesn't have dmilligan latest update:
http://www.magiclantern.fm/forum/index.php?topic=12733.50.msg123088#msg123088
update: EXIF shutter speed should now be the time of FA_CreateTestImage (the time you see displayed on the LV screen), not the value set in the Canon menu (which is wrong). This value may be slightly longer than the true exposure time, but it's more correct than Canon menu shutter speed.
If you need I can upload the mlv file for you. It's 10 shot 376mb
Or if you want I can try to extract your on my machine
I just tried again but this time ETTR and DUAL ISO is activate
Once again the new mlv_dump extracted all 5 DNGs fine
Here are EXIF info
1) 1/15 sec F11.3 ISO 100
2) 1/1000 sec F11.3 ISO 100 this is the ONLY file have horizontal stripes aka dual iso (why is that?)
3) 1/1000 sec F11.3 ISO 100
4) 1/1000 sec F11.3 ISO 100
5) 1/166 sec F11.3 ISO 100
Note: am hand held the camera so the camera is constant moving, so sometime the camera is closer to the screen or has more bright white blank area in the frame
----------- EDIT: this explanation is not true, see the posts below ..............................................
Mistery solved, thanks, I can process now my MLV timelapses with ETTR on.
The problem was the lens.
In my previous tests, I was using a manual lens, following the advice in ML user guide, section "Shoot - Intervalometer". The guide suggests to use a manual lens, or an EF lens with aperture locked (I don't know how to do that ???), and unscrewed, to avoid flicker.
But I have seen that ETTR with the manual lens fools the "silent" module when writing the MLV file. The lens I used was a m42 Pentax lens coupled to the 500D through a ring adapter with an EMF programmable AF confirm chip.
With a Canon EF lens, it works fine. That might be the first thing I should have tested.
I have shot the timelapse indoors usiing a dimmed lamp. I have altered the light intensity several times during the test, and ETTR continuosly adjusts the exposure time, everything works fine.
Next test will be outdoors during a sunset, or perhaps a moonrise nightshot beside the sea ;)
This will be a much more interesting timelapse than my living room lighted with a dimmed lamp :D
------------------------------------------------Edit -----------------------------
Today is one of the rare days we have clouds in Sunny Diego, California. Currently am test shooting full-size silent mlv with ettr time-lapse
I decided not to do the lens twist to test the power of ETTR module. I hope I made the right decision. Beside I like to see aperture in EXIF
ETTR does not adjust, or care about, the aperture. If you notice different behavior with manual vs Canon lens, that's a bug.
Can you describe the issue in detail? It's not clear to me what the problem is.
Quote from: barepixels on July 25, 2014, 06:35:29 PM
I just tried again but this time ETTR and DUAL ISO is activate
It is possible to get a Dual-ISO fullres silent timelapse? ??? cr2hdr can process correctly the resulting DNGs? This will be great!
If the skip offsets are correct, it should work.
Quote from: a1ex on July 25, 2014, 08:30:52 PM
ETTR does not adjust, or care about, the aperture. If you notice different behavior with manual vs Canon lens, that's a bug.
Can you describe the issue in detail? It's not clear to me what the problem is.
Using the manual lens I can get a fullres silent pics timelapse, using ETTR to autoadjust the exposure, and works fine if I set "silent.mo" options to save the pics in individual DNG files. This way there is no problem at all.
But If I choose to save the pics alltogether in a single MLV file, then I cannot extract the pictures during postprocessing, mlv_dump reports an error.
I have posted mlv_dump output when this happens in a previous post:
http://www.magiclantern.fm/forum/index.php?topic=12733.msg123271#msg123271 (http://www.magiclantern.fm/forum/index.php?topic=12733.msg123271#msg123271)
With a Canon EF lens, both ways work fine. No errors when processing the MLV file with mlv_dump
josep
DUAL ISO with ETTR works with full-size silent MLV but see last few post here
http://www.magiclantern.fm/forum/index.php?topic=7139.msg123372;topicseen#msg123372
crap, am in trouble now
(http://199.167.201.88/screencaptures/F0FAK.png)
it produce one file number 109 and that dng cant be open with ACR.
Grrr 471 pics over 9 gigs
Using Canon 24-70mm 2.8 and not twist.
======================================
EDIT just tried second time, same settings but only 19 pics. Extracted OK. Going for my third try .... longer ... aiming for 100 pics
Quote from: barepixels on July 25, 2014, 08:53:26 PM
crap, am in trouble now
(http://199.167.201.88/screencaptures/F0FAK.png)
it produce one file number 109 and that dng cant be open with ACR.
Grrr 471 pics over 9 gigs
Using Canon 24-70mm 2.8 and not twist.
This is the error I observed this morning.
I'm doing a more complete series of tests now, and I see I was wrong, the error is not related to the lens (manual or EF). Tried several manual lenses, with adapters with or without AF confirm chip, and they all work well.
I suspect the problem is related to the interval between shots defined in the intervalometer. But I need another test to confirm it.
I notice each chunk is 2 gigs. I was expecting 4 gigs for each
(http://199.167.201.88/screencaptures/TyclX.png)
Quote from: barepixels on July 25, 2014, 11:02:55 PM
I notice each chunk is 2 gigs. I was expecting 4 gigs for each
The same happened to me with the problematic mlv files this morning.
Still no success to reproduce the error :(
It seems I need a long test to reproduce it. It happened to me with timelapses of 101 images.
Now I have done several tests of 20 images, and they always work, regardless of the lens or the delay choosed in the intervalometer.
maybe it has to do with splitting in chunks.
Quote from: barepixels on July 25, 2014, 11:20:04 PM
maybe it has to do with splitting in chunks.
Maybe, but only with ETTR on ?
what does 'mlv_dump -v' say?
Quote from: josepvm on July 25, 2014, 11:22:55 PM
Maybe, but only with ETTR on ?
I don't know I have never shot Full-res silent MLV this many frames. we were doing 5 or 10 frames to solve the mlv_dump problem.
I just got done with 102 shots. the single MLV fail to extract. gave me only one file name 101 and that cant be open with ARC.
Going for my fourth try now.... but this time I will use DNG and ETTR not MLV for around 100+ frames. My theory is if a frame get corrupted, with DNG the rest can be save but a similar corrupted frame may kill the whole MLV and its chunks.
DELETE, problem solved, cleaning forum
Got it again. With 101 pictures, I get the error. Intervalometer set to 1 sec. ETTR "Always on", saving as MLV. Only one MLV file written, 2.2 GB size
Output of "mlv_dump -v --dng *.MLV" :
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Verbose messages
- Convert to DNG frames
- Output into '00000000_frame_'
File 00000000.MLV opened
File 00000000.M00 not existing.
Processing...
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 3507273469957387890
FPS : 1.000000
File : 0 / 0
Frames Video: 101
Frames Audio: 0
Block: RTCI
Offset: 0x00000034
Size: 44
Time: 838839.378000 ms
Date: 25.07.2014
Time: 23:50:47 (GMT+0)
Zone: ''
Day of week: 5
Day of year: 0
Daylight s.: 0
Block: EXPO
Offset: 0x00000060
Size: 40
Time: 838839.942000 ms
ISO Mode: 0
ISO: 100
ISO Analog: 72
ISO DGain: 0/1024 EV
Shutter: 0 µs (1/inf)
Block: LENS
Offset: 0x00000088
Size: 96
Time: 838839.969000 ms
Name: '1-65535mm'
Serial: ''
Focal Len: 300 mm
Focus Dist: 0 mm
Aperture: f/4.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x0000001B
Flags: 0x00000000
Block: IDNT
Offset: 0x000000e8
Size: 84
Time: 838839.984000 ms
Camera Name: 'ERR:1 md:0x 0 ml:0'
Camera Serial: ''
Camera Model: 0x00000000
Block: WBAL
Offset: 0x0000013c
Size: 44
Time: 838840.034000 ms
Mode: 0
Kelvin: 5000
Gain R: 1024
Gain G: 1024
Gain B: 1024
Shift GM: 0
Shift BA: 0
Block: STYL
Offset: 0x00000168
Size: 52
Time: 838840.046000 ms
picStyle: 133
contrast: 0
sharpness: 0
saturation: 0
colortone: 0
Block: VIDF
Offset: 0x0000019c
Size: 27067688
Time: 841076.753000 ms
Frame: #100
Crop: 0x0
Pan: 0x0
Space: 0
Vertical stripes correction:
1.000 1.000 1 1 1 1 1 1
[ERROR] Invalid block size at position 0x019d06c4
Processed 1 video frames
Done
Exactly the same setup and lighting but only 20 frames (~500 MB MLV file) no errors.
now try again, same amount, but this time using DNGs. See if you will get any corrupted frame. i sent you a PM
there is no RAWI in this MLV.
can you upload the first few hundred MiB of a buggy file?
My last run for today ( after this one I go to sleep ) ::)
Same setup, same lighting, same number of pictures (101), but this time ETTR disabled.
And the error appears again:
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Verbose messages
- Convert to DNG frames
- Output into '00000000_frame_'
File 00000000.MLV opened
File 00000000.M00 not existing.
Processing...
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 1572878673380009968
FPS : 1.000000
File : 0 / 0
Frames Video: 101
Frames Audio: 0
Block: RTCI
Offset: 0x00000034
Size: 44
Time: 714192.069000 ms
Date: 26.07.2014
Time: 00:19:37 (GMT+0)
Zone: ''
Day of week: 6
Day of year: 0
Daylight s.: 0
Block: EXPO
Offset: 0x00000060
Size: 40
Time: 714192.635000 ms
ISO Mode: 0
ISO: 100
ISO Analog: 72
ISO DGain: 0/1024 EV
Shutter: 125000 µs (1/8.00)
Block: LENS
Offset: 0x00000088
Size: 96
Time: 714192.694000 ms
Name: '1-65535mm'
Serial: ''
Focal Len: 300 mm
Focus Dist: 0 mm
Aperture: f/4.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x0000001B
Flags: 0x00000000
Block: IDNT
Offset: 0x000000e8
Size: 84
Time: 714192.710000 ms
Camera Name: 'ERR:1 md:0x 0 ml:0'
Camera Serial: ''
Camera Model: 0x00000000
Block: WBAL
Offset: 0x0000013c
Size: 44
Time: 714192.759000 ms
Mode: 0
Kelvin: 5000
Gain R: 1024
Gain G: 1024
Gain B: 1024
Shift GM: 0
Shift BA: 0
Block: STYL
Offset: 0x00000168
Size: 52
Time: 714192.771000 ms
picStyle: 133
contrast: 0
sharpness: 0
saturation: 0
colortone: 0
Block: VIDF
Offset: 0x0000019c
Size: 27067688
Time: 716170.234000 ms
Frame: #100
Crop: 0x0
Pan: 0x0
Space: 0
Vertical stripes correction:
1.000 1.000 1 1 1 1 1 1
[ERROR] Invalid block size at position 0x019d06c4
Processed 1 video frames
Done
So now it's clear the problem is not ETTR related, It seems related to MLV files with more than 100 pictures.
I don't know if the bug is in mlv_dump, or in "silent.mo" module.
@g3gg0
These are the first 200Mb of the MLV file in my last test. I have used the linux command "split --bytes=200M 00000000.MLV mlv_part"
https://www.dropbox.com/s/ca5qbkpeiv7vai7/mlv_partaa (https://www.dropbox.com/s/ca5qbkpeiv7vai7/mlv_partaa)
I see that the "mlv_dump -h" output is much shorter for a MLV file with 101 pictures (with errors)
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000000.MLV'
- Verbose messages
- Verify file structure
- Dump all block information
File 00000000.MLV opened
File 00000000.M00 not existing.
Processing...
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 3507273469957387890
FPS : 1.000000
File : 0 / 0
Frames Video: 101
Frames Audio: 0
Block: RTCI
Offset: 0x00000034
Size: 44
Time: 838839.378000 ms
Date: 25.07.2014
Time: 23:50:47 (GMT+0)
Zone: ''
Day of week: 5
Day of year: 0
Daylight s.: 0
Block: EXPO
Offset: 0x00000060
Size: 40
Time: 838839.942000 ms
ISO Mode: 0
ISO: 100
ISO Analog: 72
ISO DGain: 0/1024 EV
Shutter: 0 µs (1/inf)
Block: LENS
Offset: 0x00000088
Size: 96
Time: 838839.969000 ms
Name: '1-65535mm'
Serial: ''
Focal Len: 300 mm
Focus Dist: 0 mm
Aperture: f/4.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x0000001B
Flags: 0x00000000
Block: IDNT
Offset: 0x000000e8
Size: 84
Time: 838839.984000 ms
Camera Name: 'ERR:1 md:0x 0 ml:0'
Camera Serial: ''
Camera Model: 0x00000000
Block: WBAL
Offset: 0x0000013c
Size: 44
Time: 838840.034000 ms
Mode: 0
Kelvin: 5000
Gain R: 1024
Gain G: 1024
Gain B: 1024
Shift GM: 0
Shift BA: 0
Block: STYL
Offset: 0x00000168
Size: 52
Time: 838840.046000 ms
picStyle: 133
contrast: 0
sharpness: 0
saturation: 0
colortone: 0
Block: VIDF
Offset: 0x0000019c
Size: 27067688
Time: 841076.753000 ms
Frame: #100
Crop: 0x0
Pan: 0x0
Space: 0
Processed 1 video frames
Done
than in the MLV file shot exactly in the same conditions but with only 20 pictures: dump_h.txt (https://www.dropbox.com/s/ia6awdcwm2769vp/dump_h.txt)
These two files have been shot using ETTR.
well, my 142 pics shot as DNGs and not MLV came out OK. Not a single corrupted file. Just no EXIF info in any of them.
I dont think the problem is mlv_dump because previously other programs were able to extract from MLV but they have black bars issue. Now those programs can't even open these large MLV.
Tested again, same setup, 101 pictures in a MLV file, this time using a new build of the latest "fullres-silent-pics" branch, including the latest "silent.c" file by dmilligan in this commit (https://bitbucket.org/dmilligan/magic-lantern/commits/c2c6ccf3fc2571bf4f218f3a07c2809c50dd290a)
Same problem, only one DNG extracted, completely black.
MLV Dumper v1.0
-----------------
Mode of operation:
- Input MLV file: '00000001.MLV'
- Verbose messages
- Convert to DNG frames
- Output into '00000001_frame_'
File 00000001.MLV opened
File 00000001.M00 not existing.
Processing...
File Header (MLVI)
Size : 0x00000034
Ver : v2.0
GUID : 7892295102139271782
FPS : 1.000000
File : 0 / 0
Frames Video: 101
Frames Audio: 0
Block: RTCI
Offset: 0x00000034
Size: 44
Time: 724172.532000 ms
Date: 26.07.2014
Time: 09:56:06 (GMT+0)
Zone: ''
Day of week: 6
Day of year: 0
Daylight s.: 0
Block: EXPO
Offset: 0x00000060
Size: 40
Time: 724173.094000 ms
ISO Mode: 0
ISO: 100
ISO Analog: 72
ISO DGain: 0/1024 EV
Shutter: 457000 µs (1/2.19)
Block: LENS
Offset: 0x00000088
Size: 96
Time: 724173.153000 ms
Name: '1-65535mm'
Serial: ''
Focal Len: 300 mm
Focus Dist: 0 mm
Aperture: f/4.00
IS Mode: 0
AF Mode: 3
Lens ID: 0x0000001B
Flags: 0x00000000
Block: IDNT
Offset: 0x000000e8
Size: 84
Time: 724173.169000 ms
Camera Name: 'ERR:1 md:0x 0 ml:0'
Camera Serial: ''
Camera Model: 0x00000000
Block: WBAL
Offset: 0x0000013c
Size: 44
Time: 724173.214000 ms
Mode: 0
Kelvin: 5000
Gain R: 1024
Gain G: 1024
Gain B: 1024
Shift GM: 0
Shift BA: 0
Block: STYL
Offset: 0x00000168
Size: 52
Time: 724173.226000 ms
picStyle: 133
contrast: 0
sharpness: 0
saturation: 0
colortone: 0
Block: VIDF
Offset: 0x0000019c
Size: 27067688
Time: 726217.946000 ms
Frame: #100
Crop: 0x0
Pan: 0x0
Space: 0
Vertical stripes correction:
1.000 1.000 1 1 1 1 1 1
[ERROR] Invalid block size at position 0x019d06c4
Processed 1 video frames
Done
okay it seems the frame #100 is getting saved into the first MLV file.
there it is overwriting RAWI and first part of the first frame.
-> this is an implementation failure from silent.mo, dmilligan has to fix that
as the overwritten RAWI has 0xB4 bytes, there are 0xB4 bytes crap right at the address mlv_dump prints.
how to fix those files:
if you see mlv_dump saying: [ERROR] Invalid block size at position 0x019d06c4 then
- open the file in a hex editor
- go to that offset
- mark 0xB4 bytes for deletion
- you should see a RTCI right after the deleted portion
(http://i.imgur.com/IsWYwXa.png)
- delete that
- save the file
- open a good file
- look for the RAWI block
(http://i.imgur.com/20jDicb.png)
- copy RAWI (0xB4 bytes) from the good file
- paste it before the first RTCI on the defect file (offset 0x34)
- voila
Thanks, g3gg0 ;)
I do not have any valuable images in the affected files, they are all only tests.
I was interested in testing the feature because I plan to capture a real landscape timelapse next week during my holidays ... now I know I cannot use MLV format until fixed. I will use fullres silent pics but saved as individual DNGs
sorry wrong thread ::)
Hi g3gg0
I have a bad MLV file 2gigs 102 pics
I used your method and were able to extract dng00 to dng55 (56 good ones) and a dng101 (bad one)
still missing more files. am unable to find the next error offset
Quote from: barepixels on July 26, 2014, 02:16:10 PM
Hi g3gg0
I have a bad MLV file 2gigs 102 pics
I used your method and were able to extract dng00 to dng55 (56 good ones) and a dng101 (bad one)
still missing more files. am unable to find the next error offset
can you send it to me?
e.g. install BitTorrentSync and use this share key: ATR2MPYDB6OGEKSPBKQZ2O2X73HPGQGQK
DELETE, problem solved, cleaning forum
enter the key into the top field and select the directory to share with me.
then press ok.
@barepixels:
you are sure there are > 100 images?
filesize 2159233448 / imagesize 38557376 = 56
thats all mlv_dump can get out of the file.
@dmilligan:
it looks like there is something odd with the file writing when reaching 2GiB.
can you limit the file size to approx 2GiB - 50M ? (e.g. 0x7CD00000)
@g3gg0
your math sound right but I could swear when i shot it.. it was 102 pics. also there was a file name 101 when i extracted fail. Possible it didn't write the next chunk ... am pretty sure I would copy to hard drive if there is more. anyway thnx for testing... am going to test recover on a 9gigs shoot now. 5 segments
EDIT: I just notice when doing mlv_dump -v on the next set of files the error is at the same offset
[ERROR] Invalid block size at position 0x024c585c
thats why i say that there seems to be a file size bug >2GiB
maybe everything above 2GiB of a file is lost and misplaced
the seek call
> FIO_SeekFile(save_file, 0, SEEK_END);
seems not to seek to the end correctly. i know it wont handle positions > 2GiB if passed as parameter.
dmilligan could use the one i use for mlv_play to seek correctly:
/* as soon all cameras provide FIO_SeekSkipFile, we can remove that temporary code */
static uint64_t FIO_SeekSkipFile_emulate(FILE* stream, uint64_t position, int whence)
{
const uint32_t maxOffset = 0x7FFFFFFF;
/* the OS routine FIO_SeekFile only accepts signed integers as position, so work around to position absolutely */
if(whence == SEEK_SET && position > maxOffset)
{
FIO_SeekFile(stream, 0, SEEK_SET);
while(position > maxOffset)
{
FIO_SeekFile(stream, maxOffset, SEEK_CUR);
position -= maxOffset;
}
return FIO_SeekFile(stream, (uint32_t)position, SEEK_CUR);
}
return FIO_SeekFile(stream, (uint32_t)position, whence);
}
DELETE, problem solved, cleaning forum
DELETE, problem solved, cleaning forum
Quote from: g3gg0 on July 26, 2014, 05:58:50 PM
thats why i say that there seems to be a file size bug >2GiB
maybe everything above 2GiB of a file is lost and misplaced
this ;)
yeah, am just documenting for the developer to analyze
Quote from: g3gg0 on July 26, 2014, 05:58:50 PM
the seek call
> FIO_SeekFile(save_file, 0, SEEK_END);
seems not to seek to the end correctly. i know it wont handle positions > 2GiB if passed as parameter.
I guess the position parameter is signed 32 bit int which would make sense for a 2GiB limit. I think FIO_SeekSkipFile has been found on all cameras now, so should I just use that?
Quote from: g3gg0 on July 26, 2014, 05:58:50 PM
the seek call
> FIO_SeekFile(save_file, 0, SEEK_END);
seems not to seek to the end correctly. i know it wont handle positions > 2GiB if passed as parameter.
dmilligan could use the one i use for mlv_play to seek correctly:
/* as soon all cameras provide FIO_SeekSkipFile, we can remove that temporary code */
static uint64_t FIO_SeekSkipFile_emulate(FILE* stream, uint64_t position, int whence)
I've just recently come across this issue also, and it doesn't look like
FIO_SeekSkipFile_emulate works properly across the 2 GB boundary, at least on the 50D.
FIO_SeekFile returns -1 when seeking across that boundary, and
FIO_SeekSkipFile_emulate just calls that. Since the stub for
FIO_SeekSkipFile has been found for nearly all cameras, I think it's time to ditch the emulated version.
here's a version using FIO_SeekSkipFile: silent.mo (https://bitbucket.org/dmilligan/magic-lantern/downloads/silent.mo)
Quote from: ayshih on July 26, 2014, 08:13:27 PM
I've just recently come across this issue also, and it doesn't look like FIO_SeekSkipFile_emulate works properly across the 2 GB boundary, at least on the 50D. FIO_SeekFile returns -1 when seeking across that boundary, and FIO_SeekSkipFile_emulate just calls that. Since the stub for FIO_SeekSkipFile has been found for nearly all cameras, I think it's time to ditch the emulated version.
uhm wait, calling FIO_SeekFile to incrementally position beyond the 2GiB border doesnt work on 50D only?
didnt know that.
Success!!
(http://199.167.201.88/screencaptures/YbkX6.png)
extracted 200 Full-res Silent MLV ETTR pics
Thank you
Quote from: g3gg0 on July 26, 2014, 08:32:59 PM
uhm wait, calling FIO_SeekFile to incrementally position beyond the 2GiB border doesnt work on 50D only?
didnt know that.
Yup, I first encountered it when trying to skip frames in a RAW video longer than 2GiB, and that's when I realized it was the same reason that building a MLV index was crapping out at the 2GiB point too.
Also see my
mlv_play pull request (https://bitbucket.org/hudson/magic-lantern/pull-request/562/more-improvements-to-mlv_play)
Quote from: dmilligan on July 26, 2014, 08:22:22 PM
here's a version using FIO_SeekSkipFile: silent.mo (https://bitbucket.org/dmilligan/magic-lantern/downloads/silent.mo)
Thanks! It works ;)
I have repeated the indoor test with 101 pics, EOS 500D, same settings and conditions, and mlv_dumps extracts now correctly all 101 frames.
The MLV now is a 2.55 GB file. Previously, for 101 pics, it was always a 2 GB File.
--------------------------------------------------------------------------------
Edit: I have completed now a longer test, with 301 pictures. Now I get 2 chunks, a 4 GB ".MLV" file and a 3.6 GB ".M00" file.
All the pictures are correctly extracted by mlv_dump, no errors.
The time value in exif data increases in every frame at a much higher rate than the real time. I mean, the last frames in the series show a time stamp that is more than an hour later than the real time when the series finished. I know, that's another story, I will measure this time offset better next week.
But the problem with files larger than 2GB seems solved. The transition to another chunk when the 4 GB limit is reached works well now.
Confirm on the time. My interval was 10 seconds apart but the files creation date reported as 20 seconds apart
tried it again with interval at 30 seconds.. file creation date reported as 60 seconds apart... with final few files almost 1 hour ahead of current time.
with that said, it didn't effect my workflow
lets try to keep this thread on topic, ETTR questions and issues should not be posted here
I've got one question regarding power saving feature and silent pics. Is there a possibility to change state of camera to "recording" when ML is saving silent pics with intervalometer ? When mlv_rec is recording movie we can dim or turn of display to save battery power. With silent pics camera is in standby mode. When silent pics saving is triggered by intervalometer, display is turned on for a while or brightness is reconfigured from minimal to standard value.. I would be nice to turn off display completely during long timelapse recordings..
Yea, i fully agree with marekk. To turn off the Display would be great trough timelapse! Or at least to auto decrees the brightniss of the Display.
Trying out full res silent pictures, very nice. :)
I saved the pictures as .RAW not MLV so what would the commanded line syntax (windows 7) for raw2dng to convert All (240) full res silent pictures to DNG's.
Or do I have to write a batch file to do this ?
You'll probably have to write a batch file. I have an example of a bash script (linux/mac) that will do this on the first page. I'm not familiar enough with the batch file scripting language to give an example, but it should be fairly straight forward.
maybe you should consider adding INFO tag using IME editing.
so users can enter what scenery/take etc this take was?
good idea, will do
oh and btw g3gg0,
Quote from: baldand on August 11, 2014, 06:35:29 PM
It very much sounds - though I can't confirm for sure without the files in my hands - as though the silent picture MLV code is not writing the MLVI block at the start of the subsequent files (.M00, .M01, etc) in the series.
From the MLV format thread (http://www.magiclantern.fm/forum/index.php?topic=7122.0 (http://www.magiclantern.fm/forum/index.php?topic=7122.0)):
"- MLVI block is the first block in every .mlv file"
and
"- using the GUID a tool can detect which partial or spanning files belong together, no matter how they are named"
While mlv_dump may be handling/decoding these file sets ok, MlRawViewer expects that block at the start of each file in the series. I think you should raise this as a possible bug against the Magic Lantern silent picture MLV code.
I was wondering what your thoughts were on this. I see Andrew's point but I think the spec is slightly ambiguous on this point. I didn't originally read it this way, and just assumed I only needed the MLVI once, not in the chunks, it only becomes clear reading the two points together. The spec should probably explicitly say the MLVI block should start every file including spanned chunks, I took, "every .mlv file" to mean only the ".mlv" and not the chunks, ".m00", ".m01" etc.
This requirement would also add a bit of complication to the code as you have to go back and re-write the MLVI header in each file (rather than just re-writing it in the first file).
reasons:
- files on disk should have predictable headers that declare which content they have (MLVI)
- this way a stray .m00 file can be uniquely identified, using its UUID (which is the same in main .mlv) no matter which name it has
- next to the UUID, the logical file number is coded in this header, so all files could be named randomly, you will find the ones that belong together
(imagine someone recovers files from a card named CHK00000.DAT, CHK00001.DAT etc, this must not be a problem for MLV)
especially the first reason is my strongest concern.
i dont like files whose content can only be determined by inspecting its payload. i want to check the first few bytes and know what it is, if its
part of a group of files and which others file belong to it.
hint:
mlv_rec does not rewrite the total file count - it just wirtes zero. its a deviation to the things i've defined, i know.
you can do it the same ;)
this is documented in the spreadsheed (https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdHJraTVTOEpmNEIwTVlKd0dHVi1ULUE&usp=drive_web#gid=0) btw:
> fileCount: when set to other than zero: how many files belong to this group (splitting or parallel), else: autodetect this
I write a quick batch file for Windows7 to process multiply ".raw" saved full res silent pictures with raw2dng to .dng
Its not prefect , it make the file name to long but it works. It anyone cares to fine tune the batch file please go ahead .
I haven write a batch file in years so I'm rusty on the syntax.
set raw2dng="D:\FullRes_Bat\raw2dng.exe"
for %%f in (*.raw) do %raw2dng% "%%f" "%%f"
Make sure raw2dng is with all the .raw files in same folder , it will exact to the same folder.
Set your path where raw2dng is , in my case drive "d:"
Just open windows notepad save as a "something.bat"
double click to run .
I've (hopefully) fixed the issue with MLVI headers. Testers needed: https://bitbucket.org/hudson/magic-lantern/pull-request/588/silent-pics-mlv-timelapse-write-the-mlvi/diff
should do, but i recommdend setting the fileNum to the actual file number.
depends on how strict tools parse this field.
>> mlv_file_hdr.fileNum = fileNumber;
MLV = 0, M00 = 1, M01 = 2
you can keep the fileCount zero for autodetection.
Just for Info. 600D 19July Nightly + silent.mo from dmiligan ist still working great for me. Taking 500 pictures without any dropframes and saves same into seperat .mlv/.m00 files. Extracting with mlv_dump.exe and works perfectly.
Here is one framegrab from a little "ML Full Res Silent Pic" promo video im putting together.
(http://i.imgur.com/pAeHXxy.jpg)
Just some Ideas. It would be great to see the (RAW?) Histogram during saving or when the pic is saved. For Day to Night(or Night to Day) TimeLapse this is very important.
Today i started doing some more silent/mlv tests with my 60D using a late July nightly using the same silent.mo -dmilligan?- posted a few weeks back.
For the life of me i can't understand why after a photo is taken, camera stays in preview after file is being copied to the mlv.It doesnt revert back to live view,if only for a split second before next photo is being taken, and i have tried every combo in the camera menus under the
image review.I didnt have this problem when i did the initial tests a couple of months back.Any thoughts?
Yeha. I have the same problem... Would be nice if it jumps back to LV earlyer to study the histogram. Now i have only 1/2 of a sec for this.
So, like i sad. I put together some sequenzes i've shoot. I hope u enjoy this short clip.
A High-Five to A1ex, Dmilligan and the whole Magic Lantern Team for this modul!
@dmilligan - thanks for this.
I just compiled and am testing this out on my 6D. For my purposes though I'm actually using silent.mo Simple mode because I need speed (going to try to use it to telecine some old 8mm home movies by "projecting" onto the camera sensor at a low frame rate and triggering the camera to photograph each frame of the film.
I was hoping with your addition that my pics would all be saved into a single MLV container. But when I take a bunch of silent pics it's presently saving each one to its own MLV. When I came back to this thread and re-read the first page I see now that you only implemented saving a single MLV for the intervalometer function.
How difficult would it be to enable this capability (single MLV) for silent pics taken via multiple half-presses? Any chance you could implement that? Maybe as a separate option in the settings since I guess for others it would be undesirable to have all pics from a "session" in a single MLV.
I'm sure you're not looking for more work, so I understand if this isn't something you want to do. Just thought I'd check in case it's a fairly simple change.
Thank you again!
So I'm totally new to this forum and pretty new to ML. I just want to say to all the ML developers...YOU GUYS ROCK... ML makes the Canon cameras soooo much better. I've been using it on my 60D for over a month now and I'm loving all the features (I can basically trash my plug-in intervalometer beast :).
As I said, I'm a total noob to this forum so I don't know how to find info very well on here yet, or how to put new build modules onto my card.
I'm a timelapse junkie but I don't want to wear my camera out and this silent shooting thing in full res raw looks like the perfect solution.
I see that you guys have it working for the 60D, but at the beginning of this post is says that this module will not work with the regular nightly build install. And then I saw some technical talk about having to "change the whole branch file".
Are you guys able to help a programming-ignorant dummy out and give me a step by step how-to guide so I can get silent shooting to work and save files as raw (CR2 im guessing) on my camera.
Also, I tried shooting in silent mode and it's saving pictures as DNG, but when I open the DNG file in PS Elements 10 all I see is a black image with red letters on top that says the file name (ex. 001.dng).
Just a few more quick questions:
What size raw file can it capture in silent mode? Largest?
Whats the longest exposure time in silent mode?
Will silent raw capture work with bracketing and ettr?
Can it damage the camera to have the mirro/shutter open for that long? Bad to point it at bright light?
I apologize if all of this is redundant for what may have already been covered somewhere.
Any help would be appreciated. Thank you all in advance.
Edit: I fixed the black image issue in PS Elements for DNG but I'm still very interested in getting the pictures to save in full res / raw format in silent mode.
Quote from: ferrocium on January 12, 2015, 03:19:38 AM
What size raw file can it capture in silent mode? Largest?
Whats the longest exposure time in silent mode?
Will silent raw capture work with bracketing and ettr?
It's not clear if your asking about regular silent picture or full-res.
Full-res silent pics answers:
1. The full resolution of your sensor
2. 15s
3. No (fastest shutter speed is 1/10s which will confuse ETTR)
Regular silent pics answers:
1. It's the same as raw video max resolutions, so see this chart (http://www.magiclantern.fm/forum/index.php?topic=6215.0)
2. 1/FPS
3. Yes
Quote from: ferrocium on January 12, 2015, 03:19:38 AM
Can it damage the camera to have the mirro/shutter open for that long? Bad to point it at bright light?
No different from shooting a movie for a long time, the main concern would be dust, and permanent damage is unlikely. The camera has built in mechanisms that will shut it off automatically in case of overheating. However, that being said:
We cannot guarantee that using ML won't cause your camera to burst into flames, but if it does, you get to keep the ashes.
dmilligan,
Thank you for your quick reply. To clarify, I am wondering if the camera can take a large enough picture in raw using silent mode to make a 4k timelapse video (3840 x 2160 pixels). It looks like, judging from the max video resolutions chart link you gave, that regular silent mode is not enough and I would need to somehow get full-res silent mode to work on my camera to get shots large enough for 4k TL video. From the info you gave it also looks like full-res silent mode opens up longer exposure times too :)
I mainly work with night sky and landscape timelapse. Over time I take a lot of photos and would like to extend the life of my shutter / mirror mechanism. Also, I don't want the camera working to convert raw to DNG because it puts further drain on the battery. I need to squeeze out all the battery time I can get for timelapse especially if I have to use live mode for the shots.
That being said, it looks like the full-res / save in raw mod would be perfect for what I need. I just need to figure out how to get it on my camera card.
For night time timelapses using AETTR the shutter speed would never get faster than 1/10" so ETTR should work for the night shots right? I'm wanting to transition from day (sundown time) to night stars.
Just for the battery thing: External batteries will solve such troubles. Adapters are available at low costs.
Yeah, I have the external battery grip, but when I'm miles out on a backpacking trip shoot it is easy to run out of battery and be out of luck. Also don't want to carry too much weight.
I was not referring to battery grips. Power adapters may connect to several battery types.
Quote from: bookemdano on January 11, 2015, 11:30:39 PM
How difficult would it be to enable this capability (single MLV) for silent pics taken via multiple half-presses? Any chance you could implement that?
in modules/silent/silent.c, in the save_mlv() function (line 234), replace the following code:
if (is_intervalometer_running())
{
frame_number = get_interval_count();
}
change it to this:
static int current_frame_number = 0;
frame_number = current_frame_number;
current_frame_number++;
and then recompile silent.mo
So... after reading more threads on this forum and discovering how the ML community works I realize just how noob my request was to show me how to install silent full-res raw for my 60D camera. I see that there are many noobs on here with many requests. Forgive me, I won't be offended if nobody shows me how to implement this.
But if someone is willing to show me how and where to get the compiled file working on my camera I would do my best to provide useful feedback to help the progress of this awesome module. I'm in the process of reading the "Want to help with the latest development but don't know how to compile?" thread. There should be a thread titled "How to provide useful testing feedback to developers", but I couldn't find anything like that.
+1 Vote from me for getting silent/full-res/raw save working well enough to place into nightly builds ASAP. It would be the best thing that has happened to timelapse junkies since the intervalometer!
Quotein modules/silent/silent.c, in the save_mlv() function (line 234), replace the following code:
Code: [Select]
if (is_intervalometer_running())
{
frame_number = get_interval_count();
}
change it to this:
Code: [Select]
static int current_frame_number = 0;
frame_number = current_frame_number;
current_frame_number++;
and then recompile silent.mo
Thanks dmilligan that works great. Can I trouble you again to ask if there is any way I can get more FPS out of this (remember I'm talking about Simple mode, not full-res)? Even holding the shutter button down halfway I get what looks like a little less than 2FPS. I'm trying to get at least 3FPS continuous, since that's the slowest rate my projector can go. Are there any settings you can think of in ML or the Canon menus that would speed it up? I'm already using an SanDisk Pro Extreme which is maxxing the 40MB/s SD bus on my 6D (I don't think the SD card is the bottleneck here, anyway).
Barring anything that can be done in the menus, in your opinion is there any further optimization that can be done to silent.mo to yield a slightly faster FPS? I'm just wondering if it's even possible or I'm bound here by some other constraint.
I should mention I haven't actually tried connecting this to my projector set up yet (which would be actuating the half-press actions via the wired remote port). But I figured that holding the shutter button halfway is going to show the max rate the camera is able to go.
Just wondering what my options are at this point. Any light you (or anyone else) can shed would be much appreciated.
Thanks again!
simple mode is exactly the same image data as raw video, so you could just shoot raw video, and you'll get 24 (or whatever) fps ;)
there are also some burst modes in the silent picture menu.
Thanks dmilligan. Unfortunately those options won't work for me (without introducing other complications) because it's impossible to keep the frame rame in sync between the projector and DSLR. I have outfitted my projector with a microswitch which can signal the DSLR to capture the next frame. But without completely replacing the motor in the projector, the slowest speed it offers is ~3FPS.
I have actually played around with RAW video prior to this and had no problem getting 24FPS continuous at 1024x768 (this is 8mm film so that is plenty of resolution for it). Figured 3FPS even at the full LV resolution would be no problem (file sizes are about 4MB each so it ought to be able to do 8 or 9FPS before exceeding the speed of the SD bus).
That's why I was wondering if maybe there are any settings in the menus that might eke out more speed. Has anyone seen higher speeds also with a 5D3 or maybe even an APS-C camera (due to smaller LV resolution)?
Any ideas? Thanks again.
Hi bookemdano,
Have had any progress on doing Telecine with your 6D? , I got a MovieStuff Workprinter XP and was thinking the same as you with the ML making it possible to take pictures without the shutter. I have EOS 30D so there is no ML on that so I was thinking a long the lines of a used 50D but I am not sure if it can keep up with the Workprinter XP running at about 6-7 fps but it would be possible to swap out the AC motor and use a DC motor and slow it down to even below 1 fps. Very slow but may worth the waiting to get the best image possible form the super 8 film.
Maybe it also would be possible to use Tethered shooting so the images goes directly to a computer over the usb but that maybe a bottleneck.
-GM