5D2 BUILDS WITH RAW_REC MODULEMaintainer: a.d. & pravdomil
Download the latest zip file
Obsolete link removed - Please use the official nightly builds //AudionutSource
https://bitbucket.org/pravdomil/magic-lantern-hack/
Nightly Buildhttp://builds.magiclantern.fm/#/
Extra featuresraw_rec: 1880
mlv_rec: crop marks for GLDraw Off
Modules:arkanoid, autoexpo, dual_iso, ettr, file_man, mlv_rec, mlv_play, mlv_snd, raw_rec, silent
PhotoAuto exposure (http://www.magiclantern.fm/forum/index.php?topic=7208.0) (credits pravdomil)
Dual ISO (http://www.magiclantern.fm/forum/index.php?topic=7139.0) (credits a1lex)
WIN:
CR2 Files need to be in the same folder with cr2hdr.exe + dcraw.exe + exiftool.exe
They should have a simple file name and no special char
Drag & drop the CR2 files over cr2hdr.exe
OSX:
Drag & drop the CR2 files and folders over cr2hdr
2014/02/1463b2f145cb3b
+ Memory Backend: more meory for ML and less conflict with Canon (credits a1ex)
+ mlv_rec +mlv_snd: Refactoring for full card recording (credits g3gg0)
2014/02/0475649ffe291b
2014/01/142b804e8cdd3c
2014/01/06f93150508421
2013/12/30b71322bb883c
2013/12/02c44ceb8452f2
2013/11/16d84b9cd9e86f
2013/10/24af9a60fe144d
2013/10/11a76fa4b23ad2
2013/10/04f620a8f2b27d
2013/09/26ce9fb256205c
2013/09/204b3129d5a739
2013/09/13f5c083059e9b
2013/09/1026f79287de2b
New To Magic Lantern RAW Video ?5D2 Alpha One is a complete editon for beginners. The main idea is to create a starting point package.
5D2_Alpha_One.pdf (https://bitbucket.org/a_d_/magic-lantern/downloads/5D2_Alpha_One.pdf)
5D2_Alpha_One.zip (https://bitbucket.org/a_d_/magic-lantern/downloads/5D2_Alpha_One.zip)
Post processing+ Exif> Camera Model: Canon EOS 5D Mark II
OSX https://bitbucket.org/a_d_/magic-lantern/downloads/5D2_OSX_raw2dng_ProRes.zip
WIN https://bitbucket.org/a_d_/magic-lantern/downloads/5D2_WIN_raw2dng.zip
Joining filesWIN
Start dialog: cmd
1. cd C:\Users\my_destination_folder
2. copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
OSX/LINUX
Start Terminal
1. cd /Volumes/my_destination_folder
2. cat xyz.RAW xyz.R00 xyz.R01 > xyz.RAW
Tips: cmd and Terminal support drag & drop => Don't need to type!
Many thanks to all MagicLantern devs!
No warranty!
Video Tutorialraw_rec: How to Install on 5D Mark 2 from Chris ( Boygetslost (http://www.boygetslost.com))
mlv_rec: 14Bit Raw+ Audio from David Miazga (reddeercitytv) (http://reddeercitytv.ca)
ToDo:https://docs.google.com/document/d/19XsIAn4pxZ5xCBW5CQrsPP-bSoup87GLQ7CHzebBYFI/edit?pli=1
Thanks for this. Unfortunately I can't get more than 155 frames out of a Transcend 400x 32GB card at 1280x720 and 24fps.
I've tried every build, and all possible settings.
My card benchmarks used to show 45-50MB/sec write speed, now they are all saying 20-25MB/sec write speed. Even when the benchmarks were higher, I still could not get more than a couple hundred frames at 1280x720 and 24fps. WTF could have happened?
I formatted the card both in camera and in Windows and reinstalled ML and no change in benchmarks.
Quote from: a.d. on May 20, 2013, 05:27:13 PM
Many thanks to all devs!
2013/05/20
3ab36d8a50de (https://bitbucket.org/a_d_/magic-lantern/downloads)
Known Issue:
# HaCKeD still not working for 5D2
Interesting fixed:
# Colour accuracy
# Exif : Camera Model: Canon EOS 5D Mark II ( download the new raw2dng_exe.zip)
# bad pixels via DIGIC
# Magenta cast in 5x & 10x magnify
Performance tip:
LV in movie mode
Thank you a.d.
Will test asap.
As for the raw2dng file you included in that link, what exactly was wrong with the previous, it seemed to have worked for me in different resolutions.
Ted
Confirmed no more pink cast in 5x and 10x magnify.
Quote from: haysuess on May 20, 2013, 06:07:21 PM
Thanks for this. Unfortunately I can't get more than 155 frames out of a Transcend 400x 32GB card at 1280x720 and 24fps.
...
I'm not familiar with Transcend, but did you 'ever try to set your LV in movie mode?
Quote from: ted ramasola on May 20, 2013, 06:30:39 PM
...
As for the raw2dng file you included in that link, what exactly was wrong with the previous, it seemed to have worked for me in different resolutions.
..
It adds Camera Model: Canon EOS 5D Mark II to the DNG
Getting a load module error on this latest build on 5D2.
props at: 0x00000000
cbr at: 0x00980108
Hmm gets worse, updated to latest nightly (20th), and ML won't load.
@mvejerslev
1. Unload modules now
2. Autoload modules on startup OFF
3. switch off
4. switch on
5. Load modules now...
Quote from: a.d. on May 20, 2013, 06:42:04 PM
I'm not familiar with Transcend, but did you 'ever try to set your LV in movie mode?
It adds Camera Model: Canon EOS 5D Mark II to the DNG
Pardon my ignorance a.d. what do you mean by "set LV in movie mode" ?
where in the menu do you do this? You mean the canon menu?(live view/movie func.set) ?
A.D. Unload modules does nothing, the procedure you outlined was the first thing I tried. Installed latest nightly and now ML wont boot at all.
Thank you, a.d.
Quote from: ted ramasola on May 20, 2013, 06:53:52 PM
where in the menu do you do this? You mean the canon menu?(live view/movie func.set) ?
Yes!
Live View/Movie func.set>Stills+movie>Movie dispay
@mvejerslev
you need to reformat your CF and install it again
Thanks a.d. for compiling us always the newest builds for the 5dmk2 :-)
Has anyone tried to open the DNGs in this build with resolve because there is a chance that it might work now;
From todays changelog:
89e62d808902 | alex: DNG: removed thumbnail, does it open now in DaVinci Resolve?
Thank you for your support and work on this A.D. I got it working :-)
I highly recommend the tutorial from CrewOfOne
http://5dfilmmaking.com/05/how-to-shoot-raw-video-on-your-5d2/
Update:
Ah, we post at the same time. ;D
will stop recording after about 80 frames with 1880x1080 25fps, the CF card is sandisk 90MB/s 32GB...
Successfully recorded a 30 second movie at 1880x720@24 on a Komputerbay 64gb 1000x card. I don't even know if it's aligned, but it worked smooth. Insane quality 8)
If I shoot in 10x crop mode, I get alternating (two different) frames from different time. The image is also no more cropped than 5x. I'm likely doing it wrong, I had the impression I could shoot at both 5x and 10x mag.
Good news is I havent gotten any actually corrupt files with latest raw2dng so far.
My two cents,
I got 201 frames with this newest build at 1880 x 1080
Quote from: Kabuto1138 on May 20, 2013, 09:44:18 PM
My two cents,
I got 201 frames with this newest build at 1880 x 1080
This is with your lexar 1000x ? :)
Quote from: ted ramasola on May 20, 2013, 09:47:02 PM
This is with your lexar 1000x ? :)
oops, sorry. Forgot to mention that. Yes, I have a Lexar 1000x 16gb card. Also, I was getting weird abrupt color shifts before this build, that seems to be OK now. Must do more testing to corroborate.
Quote from: Kabuto1138 on May 20, 2013, 09:44:18 PM
My two cents,
I got 201 frames with this newest build at 1880 x 1080
how many frames was it in previous build for you?
Quote from: olik on May 20, 2013, 11:59:07 PM
how many frames was it in previous build for you?
I don't have the exact number but if I remember correctly it was almost immediately. Now is a little bit over 8 seconds.
Any suggestions to bypass the limit of 4GB?
Quote from: JackDaniel412 on May 21, 2013, 02:51:31 PM
Any suggestions to bypass the limit of 4GB?
5D2 is FAT and not exFAT like on 5D3
Has anyone tried with the new build to import the DNGs with davinci resolve?
the new Raw2dng_resolve.exe still can not work with resolve..
Thanks I will correct the post! It seems Davinci Resolve doesn't like thumbnail in DNG (source (http://forums.creativecow.net/thread/277/22358#24269))
Thanks for the update.
Someone in this thread http://www.magiclantern.fm/forum/index.php?topic=5419.275
reply # 285
posted this image using build 21 version and show black spots,http://img35.imageshack.us/img35/993/raw1j.png
Is this the digic issue on bad pixels which I read was addressed in the change log?
Thanks for this new update a.d.
8)
Thanks for building :) I will test a new build soon
I have tested the last build and the raw2dng.exe and I always have the first DNG pink when I convert it, It's normal?
(It's only the first frame, so it's not a big problem...)
My 2 cents contrib ;)
P.S. : again, sorry for my english! ;)
Thanks for the new builds!
I do however have a strange new error when using your newest build of raw2dng for mac:
Quoterm: *.dng: No such file or directory
raw2dng converter GUI for OsX
Beta ver.0.7
/Users/root/Desktop/raw2dng.app/Contents/Resources/script: line 3: 368 Segmentation fault: 11 ./raw2dng "$file_is"
@ted ramasola
You are right. Thanks for the head up! It's the sensor noise. The DIGIC Register provide a fuction to fix that. a1ex (credits: nanomad) already implemented the call to the function 2 days ago.
@Atrakt
I will look after that
Update: I can't reproduce that!
@olik
Just tested on Mountain Lion at it works! Which Version of OSX?
Update: which scrax's version work for you?
@ a.d.
thx!
tested the new ETTR feature. really nice.
but back to RAW. I got an issue with the current build. when RAW is switched "on" and I zoom to 5x the LV does some weird things and shows a black/white image. at 10x its normal.
I think that BW image is a simulation of the coverage of the raw recording feature. Unlike in full frame mode, where you can just show a white box to indicate the crop areas, the zoom mode by itself can't show you the full extent of your crop zone so it has to show a distorted BW image to illustrate the full extent of your frame.
@X-RAY
Global Draw on?
@ Yoshiyuki Blade
So you mean its a feature not a bug? But that wasn't till this build. Didn't it show the real recording-area in 5x-mode before?
Is this a new "feature"?
Global Draw is On. When its Off its not happening.
It seems to occur only after I record in RAW the first time after booting. After that whenever RAW is on and I zoom to 5x it is b/w and kind of weird.
Yeah, I think it's related to this change from a while ago:
Quoteed94a01ee362 | alex: raw_rec: added live raw preview for x5 zoom mode (so you can frame in crop mode); added option for panning in menu (dolly mode)
It could also be related to the af-raw call as we don't really know what it does
Not a bug... this is raw preview. Otherwise you get 5x zoom box completely unrelated to what you're shooting. Do 10x if you want to see color/focus.
For those with a 5DmkII and a VAF filter, I tested that the filter is essential at 1x resolution.
However, its mushed up soft when used at 5X crop mode.
Here is a new chart test at 1880 x 1080 & 1920 x 1078 comparing the DNGs with a still CR2 sraw2 frame and also with a chart at h264.
This is using NB may 22.
Thanks! Nice test!
There is still a little color aliasing without the vaf filter, at crop mode using 5x magnify, there is slight color aliasing but it is minimal compared to no filter at 1x.
So my conclusion is, filter is good at normal 1x.
At crop mode 5x, using a VAF filter softens the image.
Quote from: ted ramasola on May 23, 2013, 03:10:13 PM
There is still a little color aliasing without the vaf filter, at crop mode using 5x magnify, there is slight color aliasing but it is minimal compared to no filter at 1x.
So my conclusion is, filter is good at normal 1x.
At crop mode 5x, using a VAF filter softens the image.
Thanks again! This feature is so cool to provide more cinematic fov. How long can you recording in 5x crop mode?
ok it`s 1:1 1920 crop, and what about 2.5 k crop mode, but in 1920px output image size?i think it can be possible. Thanks!
Built 2013/05/24: why with HaCKeD ON i have better speed? OFF 54/55 MB/s ON 58/59 MB/s.
CF SanDisk Extreme Pro 16 GB 90 MB/s.
Aspect ratio! Wonderful!
Interesting! Could you test it several times?
Quote from: a.d. on May 24, 2013, 08:10:38 PM
Interesting! Could you test it several times?
Sorry, at the first loading module I had a worst speed (i don't know why) then the rate has stabilized at 58/59 MB/s with HaCKeD ON and OFF...
Don't work...
I think ... It's normal behaviour. I notice we need something to kickstart. First RAW Record has always low frames.
May 24th seems a bit faster. Now get ~711 frames at 1880x940, where before I was getting 602 frames at 1880x960.
Hacked3d off, Global Draw off, Komputerbay 32gb 1000x
Man you're still outgunning me on these write speeds -- impressive.
But I just made head-smacking discovery. Disabling all stock Canon screen overlays via the "info" button gives me a boost from 59-60MB/sec to a solid 63-64MB/sec with the Komputerbay 64GB. I can now hit the 4GB limit on today's build at 1720x968. Amazing. People, absolutely disable both ML global draw *and* all Canon overlays for max write speed!
Note that my Lexar 32Gb 1000x still doesn't max out at 1720x968. It's always a touch slower than the Komputerbay.
Regardless I have to wonder what other simple fixes I may be overlooking that may account for the write speed differences I'm seeing from people with the same exact card.
Thanx a.d for your update ;)
Hazer,
>Disabling all stock Canon screen overlays via the "info" button
Assuming 5DII, could you explain what you mean by canon overlays and how to disable? Thanks!
Never mind.. Live View mode..
Yep, 5D2 -- sounds like you've figured it out, but yes, when in Live View just cycle through the "info" button until all the Canon graphics go away. In my case this makes the difference between between short clips and unlimited filming at 1720x960.
I'm testing build may 27 for 5d2 file bfd891fe53ab.zip and here is my observation so far.
The delete feature is a nice feature but currently it is very risky.
scenario:
Shoot several clips raw video, say clip 1 2, 3.
Go to ML menu>raw video menu>video file (this shows NO VIDEO FILE as default)
Click SET to show first clip, M0000000.RAW,
Say you want to delete 3rd clip so you turn the main scroll wheel to go to M0000003.RAW
then you ROLL down to select DELETE then press SET to delete video size but file remains but 0kb in size. This is ok for now, also note WAV file remains unchanged and not deleted.
But here is the risk,
While selection in still in DELETE if you happen to roll the TOP SCROLL WHEEL, the clips be DELETED 1 by 1. ! THIS IS RISKY as you think you are selecting the clips but in fact they are already deleted without warning.
You are right. I'll remove the delete function for now until we have a better concept.
Quote from: a.d. on May 28, 2013, 08:55:21 AM
You are right. I'll remove the delete function for now until we have a better concept.
Thank you for your prompt reply a.d.
I am getting the bad, stuck color pixel problem from the 27th build on my 5DII, but I do not have that problem when I go back to the 24th build. I have not tried the 28th build yet so I do not know if that addresses the issue. Not sure if anybody else is having this problem but just wanted to say something.
I've just tested to take about 5 shots with around 300 frames from yesterday build and I have no corrupt frame so far.
QuoteYou are right. I'll remove the delete function for now until we have a better concept.
Just have it delete the last file and leave the chunks alone I guess... either way file manager works now.
Quote from: 1% on May 28, 2013, 08:48:42 PM
Just have it delete the last file and leave the chunks alone I guess... either way file manager works now.
Yes, I agree with this, after a take, when you know it was bad after review, its logical to have it delete last file only.
Though ideally it would be a nice feature to be able to select and delete. And ideally the wav as well.
a.d.
I prefer the joystick press for raw record rather than the star since there are 3 buttons beside each other and easy to confuse.
@1%
The file browser is great
@ted
Do you think, it's better than the LV Button?
I think the joystick is better than the LV button. Because the LV button has a logical function already, and because I can reach the joystick button with my thumb with my hand in regular position - the LV button is waaay over on the other side of the camera!
Quote from: mvejerslev on May 28, 2013, 09:05:07 PM
I think the joystick is better than the LV button. Because the LV button has a logical function already, and because I can reach the joystick button with my thumb with my hand in regular position - the LV button is waaay over on the other side of the camera!
mverjerslev is correct on this reason.
The LV button is so out of the way. The Joystick is near the thumb and in certain situations a shooter can choose between h264 (SET) or raw (JOYSTICK).
For handheld run and gun shooting, the joystick is logical.
Many shooters shoot barebones, just handheld with a Vfinder.
agree with mvejerslev and ted! I also have my problem with the LV button! ;D
On the other hand the joystick is in conflict with the panning mode!
All cameras use the LiveView button for recording, except 5D2. Since the module code is designed to be portable, I don't see an easy solution to this, other than also adding the SET button as an alternate REC button.
Edit: took a closer look, and I can't just define BGMT_REC as BGMT_PRESS_SET without breaking the SET button.
+1...Set is doing too many things already. 600D/6D/everyone else uses LV for H264.
'Set' and joystick press is not the same thing on 5DII. Set is in the middle of the wheel, the joystick is above the wheel and have a press function as well. Works well with the 'alternative' raw build.
Quote from: mvejerslev on May 28, 2013, 09:30:18 PM
'Set' and joystick press is not the same thing on 5DII. Set is in the middle of the wheel, the joystick is above the wheel and have a press function as well. Works well with the 'alternative' raw build.
This is correct and was convenient when it was implemented on an earlier build.
+1 on *not* using the LV button for recording. Maybe I'm missing something, but this makes it impossible to turn off live view to save power when raw recording is enabled. i.e. Hitting live view always triggers recording. The Pravdomil build solves that problem elegantly with the joystick.
Between the joystick and the AF button, I'd prefer the AF button. I have accidentally triggered raw recordings when simply using the joystick to check focus in 5x/10x modes. The AF button would be a much more solid press with less room for error.
Panning mode on: Joystiq
first click stop the motion, second click center the window
It's late now, tommorow I'll do the two hacks. I hope we'll get more people to talk.
I think the panning mode is a bit crude. Is anyone using it? Enough for it to take up a button?
Quote from: mvejerslev on May 28, 2013, 10:34:50 PM
I think the panning mode is a bit crude. Is anyone using it? Enough for it to take up a button?
I agree. This is too fancy to be useful like built in filter effects. I agree this should not be a priority over using it for record activation.
The joystick is approximate to the start/stop buttons of newer cams like 7D, 5D3, etc.
Quote from: ted ramasola on May 28, 2013, 09:10:09 PM
mverjerslev is correct on this reason.
The LV button is so out of the way. The Joystick is near the thumb and in certain situations a shooter can choose between h264 (SET) or raw (JOYSTICK).
For handheld run and gun shooting, the joystick is logical.
Many shooters shoot barebones, just handheld with a Vfinder.
Only downside I can think of to the joystick is the fact that it is also used for panning when in the zoomed mode for raw recording (slow pans etc). I would not use the Joystick to start and stop recording for this reason alone being one might accidentally bump it and stop recording. Just my 2 cents.
Quote from: mvejerslev on May 28, 2013, 10:34:50 PM
I think the panning mode is a bit crude. Is anyone using it? Enough for it to take up a button?
I've used the panning mode actually, and it is pretty nice. I would not like to see this overwritten as a record alternative.
Quote from: Hazer on May 28, 2013, 10:16:01 PM
Between the joystick and the AF button, I'd prefer the AF button. I have accidentally triggered raw recordings when simply using the joystick to check focus in 5x/10x modes. The AF button would be a much more solid press with less room for error.
Please, don't use the AF button :) It's really helpful to me when I quickly want to set focus before I shoot.
To turn of the LV mode I just turn the program dial to either c1, c2 or c3. Don't think I have anything special programmed to them, but it turns of the LV mode.
Built 29th may, some corrupt frame...
(http://dcmakecreative.altervista.org/DNG000055.jpg)
Hi all :)
I just Tested the New Build (9eaa84d45f7b) for the 5D2
i have manage to record 1880x852 24p full card no Frame Drop
which is a Lexar 32GB_1000x. I'm in the process of checking for bad frames.
i check the preview in camera, works will, but can not control the playback.
would be nice stop play back at only time. I do like the Lv button for raw record its feels
more natral there. At less for me.
All in all very nice build at this point its Stable to put the the 5D2 in daily production
with RAW.
Update:
i just check all the frames, every thing looks Ok until frame 8926 of 10461 from that point there is pink noise
on alternating frames until the end.
i recorded until the Card was full and stop recording on its own which was 30GB.
it seams that when you let the card fill up, it has problems with pink noise,
on shorter files i don't see this problem.
on record i only had 1 to 2 buffer Star at only time, file was recorded @ 64.2 MB/s
i will try a lower setting and stop before the card fill up totally
Quick test with this build for the 29th -- I'm seeing write speeds of 68-69MB/sec on the KomputerBay 64GB 1000x. Very nice indeed. And optional AF-button use for recording. Fantastic! Thanks for this.
The Live view image is still active i.e. not frozen/hack3d during record. Has that feature been activated yet on the 5D2?
Thank you a.d.
The option which recording button to use is a nice touch. :)
Works as advertised. Tested with more than 4gig files. After breaching 13 gig at 1880x800 I knew it was already stable so I stopped recording. I was able to combined and open the files of more than 4,000 frames.
One bug is the playback within the file manager module doesnt seem to work and shows garbled characters on screen.
Delete functions work.
Quote from: Hazer on May 30, 2013, 02:12:02 AM
Quick test with this build for the 29th -- I'm seeing write speeds of 68-69MB/sec on the KomputerBay 64GB 1000x. Very nice indeed. And optional AF-button use for recording. Fantastic! Thanks for this.
The Live view image is still active i.e. not frozen/hack3d during record. Has that feature been activated yet on the 5D2?
I still have awrite speed around 62-64 MB/s
@all with corrupt frames
Thanks for the bug report. The fixed of the pink cast in magnify caused corrupt frames (I'm guilty!), so we need to live with it for now. (Credits a1ex)
I've just added the support of global draw on!
@Hazer
It still doesn't work for 5D2! I removed it!
@ ted ramasola
You are welcome.
Quote from: t2scorp on May 30, 2013, 10:00:59 AM
I still have awrite speed around 62-64 MB/s
Are you using a 1000x card? If so, make sure of the following:
*Global draw is off
*Photo quality (in the stock Canon menus) is set to JPEG "L" and Raw photos are off
*All stock Canon on-screen graphics are turned off -- i.e. enter live view and press the "info" button until the screen is clear.
In a few subsequent tests I was getting around 67MB/sec but either way this is pretty strong performance.
@a.d.
Is it that we haven't figured out how to disable LV during recording yet on the 5d2, or is the 5d3 simply the priority and we haven't had time to port that feature yet? Because if that saves a few more MB/sec, we can probably use full-res HD 1880x1060 for at least 1000 frames before buffering out. Which would be pretty cool!
You could use global draw on, if you like to, it automatically switch off during the recording.
What do you mean "disable LV"?
Sorry -- was referring to hack3d mode, where the LV display does not update video during record. If I understand correctly, this is worth a couple MB/sec write speed. Which would be really helpful if we could get that working on the 5d2.
Hey guys, I don't know if this is the right place to put this info, but with today's build I was able to get 741 frames at 1880x940 and stable until my card filled up at 1880x854.
5d2 with a 16gb lexar 1000x
Quote from: Kabuto1138 on May 30, 2013, 08:35:28 PM
Hey guys, I don't know if this is the right place to put this info, but with today's build I was able to get 741 frames at 1880x940 and stable until my card filled up at 1880x854.
5d2 with a 16gb lexar 1000x
That is almost the same as my tests with May 29 build by a.d with 32gig lexar 1000x.
With ml menu=global draw off, stills menu=no Raw+jpeg "L"
1880 x 1058 365 frames
1880 x 940 1,406 frames
1880 x 854 stable/continuous
1720 x 968 stable/continuous
1720 x 860 stable/continuous
1280 x 720 stable/continuous
Crop mode 5x NO FPS over ride.
1280 x 1078 138 frames
1880 x 1058 156 frames
1720 x 968 305 frames
1600 x 900 830 frames
1440 x 810 stable/continuous
Crop Mode WITH FPS Over ride. Thanks Noix222 for the heads up.
1920 x 1078 268 frames
1880 x 1058 372 frames
1720 x 968 stable/continuous
Quote from: Kabuto1138 on May 30, 2013, 08:35:28 PM
Hey guys, I don't know if this is the right place to put this info, but with today's build I was able to get 741 frames at 1880x940 and stable until my card filled up at 1880x854.
5d2 with a 16gb lexar 1000x
Was there only corrupt frames with the full card record?
i did a full card @ 1880x854 24p and the last 2500 frame of 10600 had alternating Pink color Frames with some
structure. I got a new Lexar 1000x 32GB, i'm going to test the new built today &
see if this happen on a full card record ;)
Quote from: reddeercity on May 30, 2013, 10:39:27 PM
Was there only corrupt frames with the full card record?
i did a full card @ 1880x854 24p and the last 2500 frame of 10600 had alternating Pink color Frames with some
structure. I got a new Lexar 1000x 32GB, i'm going to test the new built today &
see if this happen on a full card record ;)
the only trouble I'm having is that I am working of a Mac, I can't find the raw2dng that open files bigger than 4gb for Macs. Any idea where can I find that?
thanks
Quote from: Kabuto1138 on May 30, 2013, 11:57:24 PM
the only trouble I'm having is that I am working of a Mac, I can't find the raw2dng that open files bigger than 4gb for Macs. Any idea where can I find that?
thanks
If the one linked on the 1st post of this thread does not work,
try the one linked on the first post of this other thread:
http://www.magiclantern.fm/forum/index.php?topic=5404.0
you should get same recording frames with normal and 5x recording if you turn fps override ON [24fps|exact fps]...
Got 64 frames at 1880 X 1058 with a 64GB Wintec filemate pro (90mb/s read 45mb/s write)
Quote from: noix222 on May 31, 2013, 04:08:08 AM
you should get same recording frames with normal and 5x recording if you turn fps override ON [24fps|exact fps]...
oops forgot about FPS over ride when doing crop mode. Thanks. I'll update my results above.
Another nice feature of recording in Raw mode is that on my SWIT HD monitor, the resolution won't drop down to SD when recording!
In fact there is now no delay.
The bug is, it hangs the camera if you try to view the footage with HDMI cable attached ( ERR 70 )
The crop marks is not centered though and pushed to the left.
This would be good for focus pulling. :) Not for framing.
Things I also miss,
the proper frame view when in crop mode (5x)
the blacked area outside borders implemented by Pravdomil here; http://www.magiclantern.fm/forum/index.php?topic=5655.0
I'm still using may 29th build by a.d since I don't have corrupt frames and I don't want pink cast image in 5x and 10x.
Quote
I'm still using may 29th build by a.d since I don't have corrupt frames and I don't want pink cast image in 5x and 10x.
You are recording the results of Canon's edge detection algorithm overlaid on top of the raw image (people reported this as lots of bad pixels). This is the price to pay for non-pink preview. Sorry, I don't have a cleaner solution for this, so don't be afraid of pink cast for now.
Quote from: a1ex on May 31, 2013, 06:31:23 AM
You are recording the results of Canon's edge detection algorithm overlaid on top of the raw image (people reported this as lots of bad pixels). This is the price to pay for non-pink preview. Sorry, I don't have a cleaner solution for this, so don't be afraid of pink cast for now.
Ok, I tested may 30th build.
The LV framing when in crop mode is now implementing a low res but proper framing for what will be recorded in B/W no pink cast.
However, upon start of recording the LV image reverts to pink cast with offset framing.
This is not ideal when the shot is moving.
Now i'm getting All Pink Noise Frames Now :-[
This with the (d93b64292277) built from may 30th
i will go back to the May 29th & try a full card record @1880x800 and see if it happen agian :-\
Quote from: ted ramasola on May 31, 2013, 06:54:44 AM
However, upon start of recording the LV image reverts to pink cast with offset framing.
If you keep globaldraw on while recording, it will not revert. I remember reading it's auto-disabled in some custom builds though, but I don't recommend doing that (sure, you can add it as an option).
Quote from: a1ex on May 31, 2013, 07:23:13 AM
If you keep globaldraw on while recording, it will not revert. I remember reading it's auto-disabled in some custom builds though, but I don't recommend doing that (sure, you can add it as an option).
Tried it with or without global draw.
With global draw:
During preview= proper framing low res B/W
During record= offset framing high res pink cast
No Global draw:
During preview & record = offset framing high res pink cast.
Will i'm having all Pink noise frames on a 21 GB file. :-\
when i recorded a short 265 Frames @1880x800 24p
No problems at all everything look like it should, but when you combine the 4 GB file together
to make a Big file All the frames are Garbage all pink noise >:(
Can anyone Shed some light on this?
i turn off everything you can i'm still using the may 30 built.
i have no Drop frame & only 1-2 buffer star at only time
is it the "total commander" Software or a bug in Writing the smaller 4 GB file?
Thanks in advance
can't work on this only more tonite time to sleep
same here all pink noise on spanned files with 30th build. tried 29th build same thing. i just overwrote 30th ml files with 29th maybe that's not good? is this corrupted footer issue?
non spanned shots are fine. komputerbay 64 gig 1000x.
using may 30 build posted by a.d.
Spanned files more than 4gig in size, the following observation.
1.) If I use "copy/B file 1+ file2 new filename" method in command prompt to combine 2 files then extract
Frames would be ok until 1:01:06 after that everything is pink noise. I tried this with 2 separate recordings. My estimate based on the frame number is that the second spanned file is corrupted.
2.) Using the same files as above, I use drag over raw2dng.exe method, by dragging the 2nd file in the span. They would all extract but upon opening in ACR all frames are pink noise.
What file sizes do you get? (exact values)
Quote from: a1ex on May 31, 2013, 10:55:18 AM
What file sizes do you get? (exact values)
xxx .RAW file is at 4,185,570 KB
per DNG frame is 2,857 KB
this is at 1720 x 968 16:9
Exact values in bytes please, for all files you've got from the camera.
Quote from: ted ramasola on May 31, 2013, 11:02:05 AM
xxx .RAW file is at 4,185,570 KB
per DNG frame is 2,857 KB
this is at 1720 x 968 16:9
Stupid question maybe... but as the processor is not used in this case for converting to h264, could there not be the possibility to encode directly into dng or is the buffer to small for this?
Cheers
Clemens
Quote from: a1ex on May 31, 2013, 11:11:40 AM
Exact values in bytes please, for all files you've got from the camera.
all the DNGs extracted are the same at 2.78 MB (2,925,230 bytes)
the first .RAW file is 3.99 GB (4,286,023,280 bytes)
Build 717c5fb95219
Resolution : 960 x 960
Frames : 3399
Frame size : 1612800 bytes
Frame skip : 1
FPS : 23.976
split:
M31-1122.RAW 4.280.371.200
M31-1122.R00 1.186.940.097
join:
M31-1122.RAW 5.467.311.297
confirm.
The Playback works well with out a glitch.
0000-2637 ok
2637-3398 corrupt
So, 5D2 does not write anything if it would exceed 4GB, unlike 5D3 which writes exactly 4294967295 bytes.
Try this: if (r == -1) r = 0;
or this: https://bitbucket.org/hudson/magic-lantern/commits/d6786d675069
reinstalled build may 29 posted by a.d.
first file 3.99 GB (4,286,023,280 bytes)
2nd file 1.28 GB (1,378,170,832 bytes)
single DNG frame 2.81 MB (2,952,080 bytes)
same resolution as previous test 1720x968 at 23.976
timeline length 1:21:00
NO corrupt frames using command prompt join then raw2dng extract method.
Using drag 2nd file over raw2dng method CORRUPT FRAMES/PINK Noise starting at 0:19:17 up to last.
it looks good.
4.294.967.295 8)
I'm on USB2 it takes times before confirm!
Update:
works with OSX+WIN
I'll update the build + converter in the next release
-
Hey guys,
So I tried the latest raw2dng for MAC and it won't open any files, not even of a few seconds. This is the "error" I'm getting.
raw2dng converter GUI for 5D2
Beta ver.0.3
/script: line 10: 506 Segmentation fault: 11 raw2dng "$fldr$name".RAW
All it does is it creates a folder in my desktop with the name of the RAW file and does nothing else.
On a separate note, with the latest build for the 5d2 I'm getting 272 frames at 16x9 = 1880x1058. That's the most I've gotten since RAW became a reality. Using Lexar 1000x 16gb.
Tried latest Raw2DNG, and there's no camera profile in the files! There used to be at least the camera make and model in the exif, and camera Raw needs this info for its noise profiling etc.
Ehm. reverted to my last functioning raw2dng, and Bridge still doesnt see exif data in my DNGs... For camera Make it says 'Canikon'. What could I be doing wrong? Same ML and Raw module I've used before with success. Perplexed.
@ Kabuto1138
Good news about 14bit 1880 x 1058 recording duration of 272 frames. Is that at 24 or 25 fps ?
What made you buy Lexar 1000x CF card ? They are pretty expensive compared to Komputer Bay / Transcend cards ? I'm looking to buy new card and wonder which to get. :)
Is there still a 2Gb limit on raw to .dng files with Mac using ML converter ? Is it possible to use the free Adobe raw to dng converter ?
I've just installed ML today and would like to try raw recording soon. ;D
Is it likely that we will ever get perpetual 14bit raw recording with 5D2 ?
Quote from: Kabuto1138 on May 31, 2013, 08:56:47 PM
Hey guys,
So I tried the latest raw2dng for MAC and it won't open any files, not even of a few seconds. This is the "error" I'm getting.
raw2dng converter GUI for 5D2
Beta ver.0.3
/script: line 10: 506 Segmentation fault: 11 raw2dng "$fldr$name".RAW
All it does is it creates a folder in my desktop with the name of the RAW file and does nothing else.
I had this same problem with the file from bitbucket, I went to the forum page for the GUI and downloaded the current version there. That seems to work fine.
I have no problems with smaller files but I am unable to get some combined files for videos over 4gb to read in raw2dng, it comes back with the "This ain't a lv_rec RAW file" error.
video specs are below:
5d2
5/31 build d6786d675069
transcend 400x 32gb
Global draw on
1320x562
file 1: M31-1319.RAW - 4.294.967.295 bytes
file 2: M31-1319.R00 - 2.255.851.017 bytes
combined file - 6.550.818.312 bytes
I have seen elsewhere people having problems with certain aspect ratios, so I tried 1280x544 and was able to get raw2dng to recognize it. I haven't tried any higher aspect ratios as these are the only cards I have.
Quote from: NitromanX on May 31, 2013, 10:25:34 PM
@ Kabuto1138
Good news about 14bit 1880 x 1058 recording duration of 272 frames. Is that at 24 or 25 fps ?
What made you buy Lexar 1000x CF card ? They are pretty expensive compared to Komputer Bay / Transcend cards ? I'm looking to buy new card and wonder which to get. :)
Is there still a 2Gb limit on raw to .dng files with Mac using ML converter ? Is it possible to use the free Adobe raw to dng converter ?
I've just installed ML today and would like to try raw recording soon. ;D
Is it likely that we will ever get perpetual 14bit raw recording with 5D2 ?
I got the card way before the RAW revolution. That's the best card I have. I am dying to get a 64gb card, but still undecided which one to get. Waiting for more Toshiba 1066x reviews, otherwise I'll get a Komputerbay. I recorded 272 at 24fps.
You said you want to use Adobe raw to dng converter? I don't understand that one.
@a.d.
First, thanks for all the work on the builds and continued updates to this thread -- appreciated.
I see on the first page that "Canon 5D Mark II in Exif" is listed as being added to raw2dng. However I'm still seeing "Canikon" listed as the camera model. I'm on OS X. I've tested this with today's build and also the most recent versions of raw2dng (app and command-line). Has this not been implemented yet in the Mac builds?
Currently, .dng files do not display the usual Canon picture styles in Photoshop / Adobe Camera Raw, and I think this is because the camera is not being correctly identified.
Thanks!
Success ! :) i recorded 5145 Frames @1880x854 24p 13.6 GB (14,656,130,312 bytes)
Joined the 3 segmented 3.99 GB (4,294,967,295 bytes)=9.46 GB (10,163,543,257 bytes
Join A File with B file 3.99 GB (4,294,967,295 bytes)=13.6 GB :)
Drop on the new raw2dng.exe & everything look Great no more Pink Noise Frame
I still need to do a Full Card Record which is a Lexar 1000x 32GB
to see if there is any frame corruption, that when i had all my problems
i use the May 31st Bulit with the new raw2dng.exe
it looks like there maybe a little Speed increase, i was recording @ 64.2 MB/s
with only 1 Buffer Star ;D no frame drops.
As long as i have no problem with a full Card record i Have plans to
completely Film in RAW a 60 Mintue Documentry about a Young Street Artist in Central Alberta.
i should get about 8 Mintue per 32 GB card @ 1880x854 24p ;)
I converted my DNG to tiff with Adobe PhotoShop and Camera
Info is diplay right, but i convert with my Windows PC and edit with my MacPro
You can also use adobe Photoshop Elements to read, edit dng's or convert Tiff
i used it a little slow compared to Full blow Photoshop but works
it also read the MetaData right.
Quote from: reddeercity on June 01, 2013, 03:15:41 AM
Success ! :) i recorded 5145 Frames @1880x854 24p 13.6 GB (14,656,130,312 bytes)
Joined the 3 segmented 3.99 GB (4,294,967,295 bytes)=9.46 GB (10,163,543,257 bytes
Join A File with B file 3.99 GB (4,294,967,295 bytes)=13.6 GB :)
Drop on the new raw2dng.exe & everything look Great no more Pink Noise Frame
I still need to do a Full Card Record which is a Lexar 1000x 32GB
to see if there is any frame corruption, that when i had all my problems
i use the May 31st Bulit with the new raw2dng.exe
it looks like there maybe a little Speed increase, i was recording @ 64.2 MB/s
with only 1 Buffer Star ;D no frame drops.
As long as i have no problem with a full Card record i Have plans to
completely Film in RAW a 60 Mintue Documentry about a Young Street Artist in Central Alberta.
i should get about 8 Mintue per 32 GB card @ 1880x854 24p ;)
wait, i've been away on a production shoot. what did i miss about stitching consecutive files together?
how is it done? i dont have to buy a mark iii now to record past 4gb?
Quote from: reddeercity on June 01, 2013, 03:29:56 AM
I converted my DNG to tiff with Adobe PhotoShop and Camera
Info is diplay right, but i convert with my Windows PC and edit with my MacPro
You can also use adobe Photoshop Elements to read, edit dng's or convert Tiff
i used it a little slow compared to Full blow Photoshop but works
it also read the MetaData right.
Thanks for the feedback. Sounds like it might be a Win vs Mac thing. What happens if you use Raw2Dng on your Pro, does the exif still display properly?
Quote from: vikado on June 01, 2013, 03:57:33 AM
wait, i've been away on a production shoot. what did i miss about stitching consecutive files together?
how is it done? i dont have to buy a mark iii now to record past 4gb?
The most recent build starts a new clip once the 4gb limit has been reached. You can use terminal or command prompt to stitch them together. On mac open a terminal window in the folder you have the clips, enter the following
cat [file1name].RAW [file2name].R00> [newfilename].RAW
hit enter. The file will take a bit of time to compile, so don't try to convert it or move it until it shows the right file size.
Don't have a PC but I've seen comments on that process around as well.
Quote from: TekAzurik on June 01, 2013, 05:04:43 AM
The most recent build starts a new clip once the 4gb limit has been reached. You can use terminal or command prompt to stitch them together. On mac open a terminal window in the folder you have the clips, enter the following
cat [file1name].RAW [file2name].R00> [newfilename].RAW
hit enter. The file will take a bit of time to compile, so don't try to convert it or move it until it shows the right file size.
Don't have a PC but I've seen comments on that process around as well.
will on the pc Its that easy too, when you get the first 4 GB file and the rest are segmented in 4 GB files
i used "Total Commander" program that joins the file together, there is a Mac Verion i just found at "http://www.codeweavers.com/via/totalcommander8 there is a trial verion there.
then i use the Copy command in a dos window (go to the Start window and type "cmd" )Navigate
to where your 2 files are & input the file names @ the cmd promp type ("copy/B file 1+ file2 new filename" )
just let it run ;)
Quote from: Hazer on June 01, 2013, 04:26:28 AM
Thanks for the feedback. Sounds like it might be a Win vs Mac thing. What happens if you use Raw2Dng on your Pro, does the exif still display properly?
Just Run the RAW2DNG on my Pro
yes it look like it, the only thing i don't see is Len info, and iso rating
i just run a quick test on a frame
i was checking the metadata in Adobe Photoshop Elements verion 9
I'm still looking for a alternative to Adobe workflow, without stepping on the
quality.
Quote from: reddeercity on June 01, 2013, 06:46:54 AM
Just Run the RAW2DNG on my Pro
yes it look like it, the only thing i don't see is Len info, and iso rating
i just run a quick test on a frame
i was checking the metadata in Adobe Photoshop Elements verion 9
I'm still looking for a alternative to Adobe workflow, without stepping on the
quality.
Thanks for the test. I've used RawTherapee on Mac with some success -- it's free / open source so you can give that a try. The nice thing is that is has numerous command line options, so if you're familiar with scripting (or willing to learn) you can setup a workflow that uses RawTherapee automatically without even opening the program. Of course these will be automated settings so you will not have as much control as if you opened the app and made manual changes to each clip.
What I'm interested in with the Adobe workflow is having access to Picture Styles, both by Canon and also third party. Some of these are nice starting points for color grade. When you did the conversion on your Mac Pro, did you see Canon Picture styles (Landscape, Neutral, etc.) in ACR? They would be under the "Camera Calibration" tab, and there should be a pulldown there which lists them.
If you don't see them, this is where I think the current build may be omitting the metadata that allows ACR to identify the camera properly. Unless something is wrong with my setup -- which is entirely possible.
Quote from: Hazer on June 01, 2013, 07:34:38 AM
Thanks for the test. I've used RawTherapee on Mac with some success -- it's free / open source so you can give that a try. The nice thing is that is has numerous command line options, so if you're familiar with scripting (or willing to learn) you can setup a workflow that uses RawTherapee automatically without even opening the program. Of course these will be automated settings so you will not have as much control as if you opened the app and made manual changes to each clip.
I've also been using Raw Therapee for Windows and the CLI is virtually a must for large scale conversions lol. The GUI is so unstable when dealing with thousands of images, I ended up learning how to avoid certain ridiculous crashes by using hotkeys and not touching the batch tab. It seems to crop 4 pixels on each side of the image for some reason too and I haven't been able to find any information on why that is. The great thing about it though is that it can output the raw with no color profile at 1.0 gamma, which is good for it8 calibration.
Quote from: Hazer on June 01, 2013, 07:34:38 AM
Thanks for the test. I've used RawTherapee on Mac with some success -- it's free / open source so you can give that a try. The nice thing is that is has numerous command line options, so if you're familiar with scripting (or willing to learn) you can setup a workflow that uses RawTherapee automatically without even opening the program. Of course these will be automated settings so you will not have as much control as if you opened the app and made manual changes to each clip.
What I'm interested in with the Adobe workflow is having access to Picture Styles, both by Canon and also third party. Some of these are nice starting points for color grade. When you did the conversion on your Mac Pro, did you see Canon Picture styles (Landscape, Neutral, etc.) in ACR? They would be under the "Camera Calibration" tab, and there should be a pulldown there which lists them.
If you don't see them, this is where I think the current build may be omitting the metadata that allows ACR to identify the camera properly. Unless something is wrong with my setup -- which is entirely possible.
i have check in to that,there is Camera Profiles under the Camera Calibration Tab
whether they are Canon profiles i'm not sure, but it dose list the Profiles you would see
on the 5D2.
As listed: Embedded ? this could be third Party
Adobe Standard
Camera Faithful
Camera Landscape
Camera Neutral
Camera Portrait
Camera Standard
(But no third party profile, Technicolor CineStyle)
i did switch between the profiles and it dose change the image
i will have to Work with this and see if the embedded is the third party
Picture profiles, i'm very use to using Technicolor CineStyle Profile for H264
but in Raw its total different image , and that what i having problems with
it very robust, Not flat and desaturated like CineStyle.
Quote from: reddeercity on June 01, 2013, 08:49:39 AM
i have check in to that,there is Camera Profiles under the Camera Calibration Tab
whether they are Canon profiles i'm not sure, but it dose list the Profiles you would see
on the 5D2.
As listed: Embedded ? this could be third Party
Adobe Standard
Camera Faithful
Camera Landscape
Camera Neutral
Camera Portrait
Camera Standard
(But no third party profile, Technicolor CineStyle)
i did switch between the profiles and it dose change the image
i will have to Work with this and see if the embedded is the third party
Picture profiles, i'm very use to using Technicolor CineStyle Profile for H264
but in Raw its total different image , and that what i having problems with
it very robust, Not flat and desaturated like CineStyle.
If you like playing with picture styles, you may like this: http://cinescopophilia.com/download-the-vw-158-canon-dslr-picture-styles-picture-profiles/
Some of the film emulations are pretty cool, that said, I have hardly ever used any of them for serious work, the fun is in creating your own look matching each image, especially now with the RAW capabilities!
Quote from: reddeercity on June 01, 2013, 08:49:39 AM
i did switch between the profiles and it dose change the image
i will have to Work with this and see if the embedded is the third party
Picture profiles, i'm very use to using Technicolor CineStyle Profile for H264
but in Raw its total different image , and that what i having problems with
it very robust, Not flat and desaturated like CineStyle.
Yep, those are the Canon picture styles! That's great. And you're seeing these using Magic Lantern .dng images that you converted right on the Mac? If so I wonder what I'm doing wrong. What build are you using and what version of Raw2dng are you using?
The picture profiles in ACR should look almost exactly the same as they do in the camera. You just have to make sure there are no other settings applied, such as saturation and sharpness and so on. You can test this with a CR2 still image from the camera. When you load it into ACR with a particular picture style, it should look very similar to an in-camera JPEG taken with the same picture style.
If you load in a CR2 that is tagged with Cinestyle, that might load it into ACR and make it available in the drop down menu. If this works, it should say Cinestyle, not embedded. You'd probably have to test it.
Thing move quickly on here, no flies on you chaps.
I had a shoot over the weekend, tides and moons for the bbc natural history unit. Mainly timelapse but they wanted some video too, and I foolishly decided to shoot ML RAW...
It was a little hairy at times, we lost one card full of video, totally corrupt, but that probably had nothing to do with ML. The results are pretty impressive. I've posted a few examples if anyones interested. It has a gritty quality that I'm not sure the NHU will appreciate but I really like, and the performance in some pretty extreme low light conditions was superb. Not sure I'd have got these images on anything else, certainly not on one of their varicams.
(http://www.lightandtime.co.uk/media/redrocks/000287.jpg)
http://www.lightandtime.co.uk/media/redrocks/000287.dng (http://www.lightandtime.co.uk/media/redrocks/000287.dng)
(http://www.lightandtime.co.uk/media/redrocks/000000.jpg)
http://www.lightandtime.co.uk/media/redrocks/000000.dng (http://www.lightandtime.co.uk/media/redrocks/000000.dng)
(http://www.lightandtime.co.uk/media/redrocks/000105.jpg)
http://www.lightandtime.co.uk/media/redrocks/000105.dng (http://www.lightandtime.co.uk/media/redrocks/000105.dng)
So thanks again to y'all, if they use any of the footage I'll donate my fee.
Particular thanks to a.d. who's builds I've been using all along. The new one is blisteringly fast for me but like others on here I am having problems converting longer clips. Getting the old 'aint lv_rec' error, seemingly for anything over 2GB. Been testing at 1880x800, will try more later if needs be, but I'm guessing I'm just being stupid and missing something. Updated raw2dng.app to 0.10. This runs it's own code right, it doesn't call the command line tool? Am I being a twat?
@andyshon
Last week I watched your vimeo video and I'm impressed!
Does this fixed OSX user problem?
5D2_OSX_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5D2_OSX_raw2dng.zip)
In the zip folder is the command line:
1 cd destination_of_the_folder (drag&drop)
Terminal support drag and drop => don't need to type the path of the folder
2 /path_to_app/raw2dng /path_to_raw/JXX.RAW DNG_Name
@a.d.
Thanks fella. Likewise, loving your work. Your footer fix saved that little film, which in turn helped sell the location to the bbc, so ta!
I'll try this later cheers. We just got two kittens, so this shit just got less interesting... Ha ha
(http://www.lightandtime.co.uk/media/kittens-hidding.jpg)
Any idea what has caused me and Hazer to lose EXIF data? Can I upload some samples somewhere?
Sorry, I need to catch a train...
I suppose you use the wrong raw2dng.
a.d. -- thanks for the links. This new command line version solves the exif issue. The camera model now displays correctly, and picture styles are available in ACR.
Thank you!
Well I have a days worth of shooting, and no matter what raw2dng version I use (I'm on a PC), they come out with no exif data.. Perhaps something went wrong in the recording, although I have no idea what I did different.
You tried the files a.d. just linked to? Hm, strange.
One thing you can try, if you really need to get those files processed and nothing else is working: There is a command-line tool I was experimenting with called exiftool that can copy exif data from one file to another. I'm pretty sure you can run this on Windows. But I'm on Mac, where the syntax is:
exiftool -tagsfromfile sourcefile.dng destinationfile.dng
...where you replace "sourcefile.dng" and "destinationfile.dng" with the names of the files you're copying and to. What I did here is take a still image with the camera in CR2 format, and used Adobe DNG Converter (a free download from Adobe) to convert this to .dng. Then, use you that .dng as the source file and copy all those tags to the destination file.
When I did this to a Magic Lantern .dng, it opened up in Adobe Camera Raw and all the picture styles were then available. The important tag seems to be called "CameraUniqueID", which needs to be set to "Canon 5D Mark II". you can actually do that specifically with exiftool like this
exiftool -camerauniqueid="Canon 5D Mark II" destinationfile.dng
Anyway a bit convoluted and it would be better to sort out the Raw2Dng process so it works. But if you need to attempt a rescue of sorts this may work for you.
Edit: If you just want to do a quick check to see what exif data is even present in your Magic Lantern .dng files, just pick one .dng file and do this:
exiftool -s filename.dng
This will list everything that's there and you should see very quickly if it's an Adobe problem or a Raw2Dng problem.
Quote from: TekAzurik on June 01, 2013, 05:04:43 AM
The most recent build starts a new clip once the 4gb limit has been reached. You can use terminal or command prompt to stitch them together. On mac open a terminal window in the folder you have the clips, enter the following
cat [file1name].RAW [file2name].R00> [newfilename].RAW
hit enter. The file will take a bit of time to compile, so don't try to convert it or move it until it shows the right file size.
Don't have a PC but I've seen comments on that process around as well.
absolutely wonderful news.
Quote from: a.d. on June 01, 2013, 01:08:01 PM
Does this fixed OSX user problem?
5D2_OSX_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5D2_OSX_raw2dng.zip)
In the zip folder is the command line:
1 cd destination_of_the_folder (drag&drop)
Terminal support drag and drop => don't need to type the path of the folder
2 /path_to_app/raw2dng /path_to_raw/JXX.RAW DNG_Name
Yep, works for me. Converted a 3GB and a couple of 8GB files no worries. So I'm now looking at a load of shaky, out of focus footage of kittens... Hmm. Nice tones though.
And the .app gui seems to work now too. So it calls the raw2dng command from /usr/bin?
QuoteYou tried the files a.d. just linked to?
You mean the mac version? I'm on a P.C. but I tried every version of Raw2DNG I have, also known functioning ones and I still get no exif (verified with the excellent exiftool). Thanks for the codes for exiftool - I was looking for that. So if I wanted to batch process a library of dng's, copying exif from one good dng to a bunch of bad ones, what would the syntax be? Thanks again.
Ok, used exiftool GUI to copy the exif data over from some sound files, so the files are saved. Now for some more testing as to the whole reason for the missing exif.
Incidentally, should anyone do the same as me, remember to set the ISO speed correctly for your files - Camera Raw needs info like this for its denoise profiling.
Here is another test shot.
Technicolor Profile Vs 5D RAW
RAW footage sent through raw2dng then photoshop then to resolve.
Regular Canon h264 with technicolor profile sent to resolve for correction as well.
Love it! Thanks guys! Way better dynamic range and even though the RAW is lower res it's way sharper too.
Quote from: mvejerslev on June 01, 2013, 11:09:38 PM
Ok, used exiftool GUI to copy the exif data over from some sound files, so the files are saved.
Cool glad that worked. To be clear, this is just a hack, because a lot of the exif in the "good" dng might not match the "bad" one: resolution, ISO, etc. But ACR will probably just ignore the data that doesn't fit, or maybe set some sliders incorrectly -- like white balance -- which you will then have to fix. Hopefully you can figure out what is causing the problem in the first place.
Hello all :)
i just finish a full card record (29.7 GB 31,934,595,752 bytes) on the May 31st built, for 5d2.
i have a Lexar 1000x 32 Gb card, thats aligned to 32K, i read a lot about people have Read Write
Problems, my average write speed is about 55MB/s read @ about 60 MB/s
But i can Record raw @ 1880x854 24p 64.3 MB/s :) with no frame drop & 1 buffer Star.
the only thing i have set different from whats been recommended is i set my Photo to JPG Small not Large no raw.
wheather that makes a different or not im not sure , and i alway record a few seconds then stop and start the full card record.
i think that make a big different . I end up with 11,374 frames(7.633 Mintue) @ 2,782 KB in size.
i also been working with the Metadata, and there again i hear pepole having problems.
in Photoshop i have not see this problem with my tests, but what i have Notice :o is under the Camera Calibration Tab
there is a Embedded in Camera Profiles, so i did a test & set the picture profile to Technicolor CineStyle Profile
in camera, did my full card record test and when i enabled the embedded tab, it change to a flat, desaturated image close to
what i would see with CineStyle with H264 this will make Grading Faster. ;)
i did no remenber seeing the Embedded Tab when i used Landscape Profile .
Quote from: reddeercity on June 02, 2013, 07:12:10 AM
But i can Record raw @ 1880x854 24p 64.3 MB/s :) with no frame drop & 1 buffer Star.
Great!, that is so great. I shot a video at 1880x756 with a previous build and got an average of 600 frames using a lexar 1000x 16g.
I should try your way..if it works for me too, I will be so happy...I hope that by the end of June there will be a more stable and practical way to shoot raw in the 5Dm2, I'm shooting a short film this month and I'm considering to go RAW, the workflow is so complicated but every minute invested is totally worthy.
Hi Guys,
I just want to get it out there that I'm a total newb before I go any further.
Ok, I'm needing some help on installing this all on my 5D2. As far as I'm aware, I download the current stable ML which is v2.3, unzip it and take just the 5D2-212.fir onto the root of my CF. Where do I find the autoexec.bin and ML folder? Can I just use the autoexec.bin and ML folder from a previous build and copy/paste the raw_rec.mo file into where it should be?
I was going to try this but was worried I'd brick the camera so thought I'd get some expert advice first!
Thanks in advance,
Josh
Quote from: joshmonie on June 02, 2013, 05:10:29 PM
Hi Guys,
I just want to get it out there that I'm a total newb before I go any further.
Ok, I'm needing some help on installing this all on my 5D2. As far as I'm aware, I download the current stable ML which is v2.3, unzip it and take just the 5D2-212.fir onto the root of my CF. Where do I find the autoexec.bin and ML folder? Can I just use the autoexec.bin and ML folder from a previous build and copy/paste the raw_rec.mo file into where it should be?
I was going to try this but was worried I'd brick the camera so thought I'd get some expert advice first!
Thanks in advance,
Josh
I don't know if i'm a expert But the best & easist way to in stall ML with the raw record module,
this is what i do to install ML on my 5D2 :)
If any thing go wrong pull the Battery out ASAP!
1-make sure you have Canon Firmware update which is 2.1.2 First
2- prepare your Card, make sure you have a Fast Card i use
Lexar 1000x 32GB Card , many other ones work but your limited to smaller Frame size recording
600x cards work like the Scan disk but will no record continuous @ larger Frame size.
Downland the EOS Card 1.3 (http://pel.hu/eoscard) for Windows, this will prepare
the card for ML, it will make it Bootable & install the latest ML
3-download the May 31st RAW record module on Page 1,
unzip install the new Autoexec file on the root of card
and the raw module go in the ML Folder,
3-Start the camera up, press the delete key takes you to the
ML window, scroll over to the Module and load by the set key.
back to the movie tab enable the Raw record tab
to change setting hit the picture Profile button.
that pretty much it there is a few pit fall but you will work that out ;)
One last thing Go have Fun recording RAW ;D
Quote from: mino.rimada on June 02, 2013, 04:42:07 PM
Great!, that is so great. I shot a video at 1880x756 with a previous build and got an average of 600 frames using a lexar 1000x 16g.
I should try your way..if it works for me too, I will be so happy...I hope that by the end of June there will be a more stable and practical way to shoot raw in the 5Dm2, I'm shooting a short film this month and I'm considering to go RAW, the workflow is so complicated but every minute invested is totally worthy.
I think if you are planning your shots in a good way it's worth a try. The workflow is not that much more complicated when you directly go with After Effects and then render out to ProRes422 HQ oder ProRes444.
Only thing that I really wish happens is, that they figure out a way to record with 12 Bit.
Hi again.
Having followed the instructions, I'm now having another issue. Upon turning the camera on after the ML "success" screen, I'm getting a "scripts dir missing" message. I can then go into ML as normal, load the raw module, etc. but when I turn it on and go into live view, I cannot start raw recording.
Any ideas?
The scripts dir comes from the regular nightly builds. Once you load the RAW recording module, the option to record RAW should appear last on the "Movie" tab.
edit: whoa, what's up with the post counts?
Quote from: joshmonie on June 02, 2013, 09:59:33 PM
Hi again.
Having followed the instructions, I'm now having another issue. Upon turning the camera on after the ML "success" screen, I'm getting a "scripts dir missing" message. I can then go into ML as normal, load the raw module, etc. but when I turn it on and go into live view, I cannot start raw recording.
Any ideas?
Sorry i forgot to tell you about that, :-[ i had to download that i'm just looking for it
Quote from: reddeercity on June 02, 2013, 10:32:11 PM
Sorry i forgot to tell you about that, :-[ i had to download that i'm just looking for if
http://nanomad.magiclantern.fm/nightly/archive/2013-05-23-8f5f3c441614/
this is the file name (magiclantern-v2.3.NEXT.2013May23.60D.550D.600D.50D.500D.
5D2.1100D)
i found a older built , it has the files your missing, i used this for my 5D2
just take the Scripts Folder put it into the ML Folder
that should work, if not let me know i see if i can help further :)
Shot this last night June 1st/2013 about 6:00pm
off my Deck pointing northwest in Red Deer, Alberta,Can.
with my 5D2
ML ISO 50, with 50mm Sigma f1.4 EX DG @ f2.2 Variable ND
stop down 50%
I copied all the file in to my card, all the function are working properly, but when I switch raw video to on and I press the AF-ON button my camera dosen't record. Dose anyone know what is the problem?
You need to press the liveview Button to record!
I hope record fonction will be assign to another button !!
Quote from: seanturco on June 03, 2013, 08:04:00 AM
You need to press the liveview Button to record!
I hope record fonction will be assign to another button !!
Its already been transferred in new builds to either the joystick press or the AF-ON button. FYI.
I don't know why they refer to that thing as a 'joy stick'. There is no joy in using it :o
Using the 5/31 build, I get severe pixelation/slow refresh (basically unusable) at the first zoom level and a super-heavy pink color cast at the second zoom level.
Is this known/intended behavior? I'm not shooting anything with it this way, but it makes focusing before takes more difficult and wasn't an issue in earlier builds.
Please, to all the testers, could you recomend me the most stable build at this moment?. I suppose that some nightly builds has some bugs, and I do not need new features, I am searching the faster (?) build. Do you remenber a good one from these last days?. Thanks. I have been reading daily the forum and I learnt a lot, thanks guys you rock.
Quote from: Nachelsoul on June 03, 2013, 07:54:28 PM
Please, to all the testers, could you recomend me the most stable build at this moment?. I suppose that some nightly builds has some bugs, and I do not need new features, I am searching the faster (?) build. Do you remenber a good one from these last days?. Thanks. I have been reading daily the forum and I learnt a lot, thanks guys you rock.
I have been using the May 31 Built it stable and fastest one yet ;D
But make sure your card is fast, i use Lexar 1000x 32 Gb card
it dose 1880x854 24p until the card is full :)
no corruption .
i did a full card test see my Video a few post up from vimeo
Quote from: Oedipax on June 03, 2013, 07:31:56 PM
Using the 5/31 build, I get severe pixelation/slow refresh (basically unusable) at the first zoom level and a super-heavy pink color cast at the second zoom level.
Is this known/intended behavior? I'm not shooting anything with it this way, but it makes focusing before takes more difficult and wasn't an issue in earlier builds.
I haven't notice pixelation/slow refresh
On that built, I don't use the zoom
I turn on the over lay's & use ML focus
Or use my zatcua 2.5x focus dopter
Quote from: reddeercity on June 03, 2013, 09:47:43 PM
I haven't notice pixelation/slow refresh
On that built, I don't use the zoom
I turn on the over lay's & use ML focus
Or use my zatcua 2.5x focus dopter
Ah, I have to sheepishly admit I wasn't aware of the ML Focus technique, works pretty well! That's working for me now although I still get a pink display with the other method (5x/10x zoom button).
Quote from: Oedipax on June 03, 2013, 11:37:40 PM
Ah, I have to sheepishly admit I wasn't aware of the ML Focus technique, works pretty well! That's working for me now although I still get a pink display with the other method (5x/10x zoom button).
That the Price to pay for Stable Raw Video
they will work that out in the future .
When you have the overlays on and focus with any EF Lens the focus window pop up.
set the size in the menu. It the best feature i think ;)
when recording Raw the overlays turn off automatically.
You should go though the Magic Latern Menus and check
out all the feature, you may find some very interesting Funtions
It will make Filming alot smoother. :)
Quote from: Oedipax on June 03, 2013, 07:31:56 PM
Using the 5/31 build, I get severe pixelation/slow refresh (basically unusable) at the first zoom level and a super-heavy pink color cast at the second zoom level.
Is this known/intended behavior? I'm not shooting anything with it this way, but it makes focusing before takes more difficult and wasn't an issue in earlier builds.
Hi,
same here, same build.
Hey everyone, I'm new here. I tried to install the Magic Lantern firmware, however, I keep on getting this message "Memory card containing firmware is required to update" any clue about this? I would really appreciate all the help. I follow the instructions from http://5dfilmmaking.com/05/how-to-shoot-raw-video-on-your-5d2/
Quote from: leo on June 04, 2013, 03:01:43 AM
Hey everyone, I'm new here. I tried to install the Magic Lantern firmware, however, I keep on getting this message "Memory card containing firmware is required to update" any clue about this? I would really appreciate all the help. I follow the instructions from http://5dfilmmaking.com/05/how-to-shoot-raw-video-on-your-5d2/
Have you followed the instructions from here?
http://wiki.magiclantern.fm/faq#installation
Quote from: ted ramasola on June 04, 2013, 03:29:48 AM
Have you followed the instructions from here?
http://wiki.magiclantern.fm/faq#installation
If you are still having problem go back to page 6 about half way up the page i wrote
a short procedure on installing Magic Latern on 5d mark ii
also read a few post on page 7 about the Scripts Folder i wrote that should do it
ted ramasola, thank you so much for your help. reddeercity, thank you so much. I followed every step. However, I still have the same problem. I'm using a SanDisk Extreme Pro. I don't understand what's the problem, as I can install the old magic lantern, but not the nightly build ones that has the RAW recording feature.
Quote from: leo on June 04, 2013, 04:16:31 AM
ted ramasola, thank you so much for your help. reddeercity, thank you so much. I followed every step. However, I still have the same problem. I'm using a SanDisk Extreme Pro. I don't understand what's the problem, as I can install the old magic lantern, but not the nightly build ones that has the RAW recording feature.
remember that when when using the nightly builds you do not remove the folders from the unified stable release 2.3. You only add/replace the once duplicated by the nightly builds.
ted ramasola, thank you so much for your quick response. I deeply appreciate it. I don't understand what you mean by do not remove folders from the unified stable release. Do you mean I have to install a stable release 2.3 on my MK-II, then copy the nightly build over it?
Quote from: ted ramasola on June 03, 2013, 10:37:25 AM
Its already been transferred in new builds to either the joystick press or the AF-ON button. FYI.
I'm using the 5/31 build, I copied the raw_af-on and raw_joystick folders to my card, but when I press af-on with raw video on it dosen't record, do u know what is the problem
Quote from: leo on June 04, 2013, 04:43:38 AM
ted ramasola, thank you so much for your quick response. I deeply appreciate it. I don't understand what you mean by do not remove folders from the unified stable release. Do you mean I have to install a stable release 2.3 on my MK-II, then copy the nightly build over it?
Yes. The stable release stays on the card. You just replace the autoexec.bin and add MODULES into the ML folder. AND choose which raw rec to use, joystick or AF_on activated. I prefer the af_on. Replace the raw_rec in the Modules folder.
Quote from: shuntian on June 04, 2013, 04:52:27 AM
I'm using the 5/31 build, I copied the raw_af-on and raw_joystick folders to my card, but when I press af-on with raw video on it dosen't record, do u know what is the problem
You don't copy the folders only the file inside. Choose which one then replace the one in MODULES folder.
ted ramasola, thank you so so much! I finally got it to work! I really appreciate all your help. :) I did a couple of tests and it looks spectacular. I will have to do more tests tomorrow morning. :D
Quote from: ted ramasola on June 04, 2013, 04:54:54 AM
You don't copy the folders only the file inside. Choose which one then replace the one in MODULES folder.
thanks, it works perfect on my 5d2. I can record 1880x800 around 800 frames and 1800x1058 around 200 frames on my komputer bay 1000x 64gb card.
Quote from: shuntian on June 04, 2013, 08:04:30 AM
thanks, it works perfect on my 5d2. I can record 1880x800 around 800 frames and 1800x1058 around 200 frames on my komputer bay 1000x 64gb card.
Glad you got it to work.
The komputerbay cf cards are really not performing as advertised as I can get stable and continuous recording with 1000x lexar at 1880 x 854. 1,596 frames at 1880 x 940 and 349 frames at 1880 x 1058.
Shuntian,
I don't know if this will help but have you tried going to canon menu and disable RAW stills and choose only JPEG "L" .
I believe your raw video recording will improve.
Quote from: ted ramasola on June 04, 2013, 08:11:09 AM
Glad you got it to work.
The komputerbay cf cards are really not performing as advertised as I can get stable and continuous recording with 1000x lexar at 1880 x 854. 1,596 frames at 1880 x 940 and 349 frames at 1880 x 1058.
I've got a Lexar 1000x 64GB Card and I can get around 7 to 8 Gigs with a 1880x854 Resolution - what are you doing to improve the speed? I turned of Canon Screen Overlays, I also set Still Picture in Canon Menu to JPG L like you said (btw: why does this matter?) but all in all the buffer seems to fill up after a while.
Quote from: Clemens on June 04, 2013, 10:16:57 AM
I've got a Lexar 1000x 64GB Card and I can get around 7 to 8 Gigs with a 1880x854 Resolution - what are you doing to improve the speed? I turned of Canon Screen Overlays, I also set Still Picture in Canon Menu to JPG L like you said (btw: why does this matter?) but all in all the buffer seems to fill up after a while.
Did you try turning global draw in ML menu to OFF? In my test it is suppose to be continuous. I tested up to 16 gig then i got tired and turned it off. I will try longer.
Quote from: ted ramasola on June 04, 2013, 10:33:16 AM
Did you try turning global draw in ML menu to OFF? In my test it is suppose to be continuous. I tested up to 16 gig then i got tired and turned it off. I will try longer.
Yep - Global Draw is off. I tried now three times and it stopped after around 7 Gig each approach.
The only thing that I can see on the screen is one small line showing the recording area and - perhaps i can deactivate this somewhere, a box for face detection.
Which build are you using?
May 31.
Quote from: ted ramasola on June 04, 2013, 10:02:10 AM
Shuntian,
I don't know if this will help but have you tried going to canon menu and disable RAW stills and choose only JPEG "L" .
I believe your raw video recording will improve.
actually I disable raw still and choose JPEG 'S', I can record 3 minutes 2.35:1. I think that is good enough. I use raw2dng to transfer the raw video to dng sequence, some videos larger than 2g works, but some are not. Do u have some better advice for the workflow?
Hi guys, first post here as i'm new to ML RAw. ;)
I have several questions concerning the post workflow and i'm sure it could othere people too.
I'm using raw2dng and import the sequence into After Effects. When importing ACR opens up, as wanted, and my first question is, what settings do you set your raw sequence?
A part from white balance, in termes of contrasts, blacks, exposure brightness etc...
I tend to set everything to "0" except for recovery or exposure if i feel the need. I don't understand why ACR always want to give me like +25 brightness and some contrast too...
I also go and set every sharpen tool or denoiser to 0.
Why do i do that? Cause i want to grade in resolve, so i like a flatten picture, with minimum noise and alteration and maximum signal in order to then encode in prores4444 or 422HQ. And it seems to me that i get a better image than if all set as default by ACR.
- So : am i right or not? For example, by default ACR sets a +5 blacks, why? Do i degrade my blacks setting it back to 0 ?
- Then, in AE, what color space do you set your project to?
"None" (by default) seems too contrasty for me compared to what i have in ACR, rec709 seems more accurate... What does this means? Are we actually in video levels 16-235 with the ML raw footage or am i getting that wrong?
And 16bits right?
Those would be my questions, and if you guys could enlighten me, it would be much appreciated! :)
Many thx
(Sorry for my mistakes, as english is not my native language).
Hi,
Anyone know the limitations of the 5DmkII versus 5DmkIII in relation to Magic lantern Raw Vid?
1. Is there a limitation in resolution
2. Record Length (only 10 sec or more)
3. etc...
Thanks
Quote from: Clemens on June 04, 2013, 10:42:54 AM
Yep - Global Draw is off. I tried now three times and it stopped after around 7 Gig each approach.
The only thing that I can see on the screen is one small line showing the recording area and - perhaps i can deactivate this somewhere, a box for face detection.
Which build are you using?
Hello :) do you have frame over ride turn on?
made sure it on & set to 24 "exact FPS"
i just on may way to Work, hope that helps
Hi, long time user of ML and have now also switched to RAW on the 5D 2.
I had some trouble on my last test. A file bigger than 4gb wouldn't convert to DNG with the latest build of RAW2DNG, the ML RAW build was from 31/05.
Just reporting, no complaints ;) keep up the good work!!
Just tried the latest release June 4th, with the raw module that came with it (joystick on) and was noticing i was getting a max of about 300 frames at 720p (2.35:1) .. which i was able to do pretty much continuos before (may 23rd build)
even on my slow sandisk ultra card 30 mb/s
Quote from: romainmenke on June 04, 2013, 10:16:20 PM
Hi, long time user of ML and have now also switched to RAW on the 5D 2.
I had some trouble on my last test. A file bigger than 4gb wouldn't convert to DNG with the latest build of RAW2DNG, the ML RAW build was from 31/05.
Just reporting, no complaints ;) keep up the good work!!
what are the steps you do to convert the the.RAW files? You have to join them first via cmd prompt then drag over the raw2dng.exe.
If you did not join them first and simply dragged the spanned file, ex ( ******.R00 ) to the raw2dng.exe then you get pink noise.
Quote from: ted ramasola on June 05, 2013, 01:12:13 AM
what are the steps you do to convert the the.RAW files? You have to join them first via cmd prompt then drag over the raw2dng.exe.
If you did not join them first and simply dragged the spanned file, ex ( ******.R00 ) to the raw2dng.exe then you get pink noise.
I did not know that.
I'm on a mac, does this also apply? (probably yes)
I had no trouble with files smaller than 4gb, but I also only got the .R00 files when I crossed the 4GB "barrier".
Workflow:
Record, copy to HD, throw in RAW2DNG, develop in ACR to tiff.
Where can I find detailed instructions on this? As I said, I first followed these topics for a couple of weeks, but I missed some info.
Thx!
Found it:
OSX/LINUX
Start Terminal
1. cd /Volumes/my_destination_folder
2. cat xyz.RAW xyz.R00 xyz.R01 > xyz.RAW
No Luck, still getting the "Error: This ain't a lv_rec RAW file" error.
Is this just a broken file or am I still doing something wrong?
I successfully joined one .RAW with one .R00 the combined file is also the size of the 2 together so I think that went well.
Hello All :)
I just installed the new June 4th Bulit.
And i have to "Say Very Good Job Guys" it keep getting better all the time! 8)
file management , very nice i like that. Work smoothly no problems, deleted only one file at a time.
But the best feature by far is the "Dolly Mode" now you can utilized the complete sensor
I can see my self using that feature .
Like Always the speed is maintained i Have No problem record 1880x854 24p @64.3MB/s with Lexar 1000x 32GB
Look like the Limit for 14 bit on 5d2 right now until the 12 & 10 bit get going.
Quote from: reddeercity on June 05, 2013, 04:34:10 AM
Like Always the speed is maintained i Have No problem record 1880x854 24p @64.3MB/s with Lexar 1000x 32GB
Look like the Limit for 14 bit on 5d2 right now until the 12 & 10 bit get going.
Confirmed this too. Jun 4 build.
Speeds are maintained.
1880 x 854 is the biggest resolution that is stable in both 1X and in crop mode 5X.
I like there is no more pink cast on magnify modes.
Some issues to look into.
In crop mode:
While in preview, proper framing is available in mono and lores- when recording is started this reverts to canon magnify/in color but offset framing. not ideal when you a following a moving subject.
Some playback issues using file file browser. No playback just characters at top edge of lcd screen.
edited: corrected previous findings about flicker. It was a non issue.
Ted, can you do a test and record 1600x900 and tell me how many frames you get? (I believe you have a Lexar 1000x 32GB, right?)
Thanks
Quote from: ted ramasola on June 05, 2013, 05:16:40 AM
Confirmed this too. Jun 4 build.
Speeds are maintained.
1880 x 854 is the biggest resolution that is stable in both 1X and in crop mode 5X.
I like this. I hope that my Komputerbay will be able to handle it.
Quote from: mihaii on June 05, 2013, 02:31:45 PM
Ted, can you do a test and record 1600x900 and tell me how many frames you get? (I believe you have a Lexar 1000x 32GB, right?)
Thanks
I'm interested in this as well.
Are there plans to integrate the other raw_rec.mo with this build? I like this build but I really like the feature of the other raw_rec for 5D where it shuts off the global draw off automatically
i've been playing around with the new build and it's the best one so far for me.
I get very stable recordings at 1880x706 1720x732 and 1600x800 that fill the card with no buffer problems.
A few things to mention, i'm using an 8gb Sandisk Extreme 60mb/s, everything in the liveview is turned off, global draw is off, photo mode is jpeg and that seems to boost writing speeds a lot.
I've also noticed that at higher resolutions i get a bigger number of frames if i shoot in the monochrome profile and if fps override is activated, don't know if they are connected in any way i'm just reporting what i see and get.
One other thing is that the body starts to heat up a bit after 1 hour or so of recording raw, at one point the temperture inside was 63C.
I did the benchmark for writing and reading and interestingly enough the speed was lower from what i was seeing while recording.
i get roughly 43mb/s in the benchmarks and when i'm recording i see speeds up to 52mb/s
will test some more!
Quote from: mihaii on June 05, 2013, 02:31:45 PM
Ted, can you do a test and record 1600x900 and tell me how many frames you get? (I believe you have a Lexar 1000x 32GB, right?)
Thanks
1600 x 900 is stable and continuous. Just one * on the buffer. Using 32 gig 1000x Lexar.
Highest res it can do is 1880 x 854 2.20:1.
Highest 16:9 res it can do is 1720 X 968.
1880 x 1058 16:9 approx 349 frames.
1880 x 940 2:1 approx 1,596 frames -thats already slightly past a minute and spans 2 files.
Quote from: silvertonesx24 on June 05, 2013, 05:27:13 PM
Are there plans to integrate the other raw_rec.mo with this build? I like this build but I really like the feature of the other raw_rec for 5D where it shuts off the global draw off automatically
+1. I love Pravdomil raw_rec module.
Quote from: Nachelsoul on June 05, 2013, 10:41:45 PM
+1. I love Pravdomil raw_rec module.
Yep, +1. I really liked that feature.
@romainmenke
You seem to miss the footer. Could you check the Canon Menu? Auto power off
Quote from: silvertonesx24 on June 05, 2013, 05:27:13 PM
Are there plans to integrate the other raw_rec.mo with this build? I like this build but I really like the feature of the other raw_rec for 5D where it shuts off the global draw off automatically
already implemented
Quote from: a.d. on June 05, 2013, 10:59:58 PMalready implemented
We might be referring to different things - on the Pravdomil build, it would turn off all the ML overlays but also black out everything on the LCD apart from the image capture area. It really helps with framing. Could be nice to get that as an option.
Quote from: Oedipax on June 05, 2013, 11:45:08 PM
We might be referring to different things - on the Pravdomil build, it would turn off all the ML overlays but also black out everything on the LCD apart from the image capture area. It really helps with framing. Could be nice to get that as an option.
yeah, I have to admit I like that too, though having it semi transparent would be much better as it would give us a warning, like for instance that boom mic is about to get into the frame. :)
But if that black out crop marks are bitmaps then it occupies memory more. If that means lesser performance then I could do with just simple crop marks.
The blackout feature on the Pravdomil build is so handy and it doesn't make my highest reliable resolution unstable. That and af record make it all much easier.
Hi guys!
I'm looking for the crop factor mode into the ML menu, but can't find it! Can anyone help me?
I'm running build 29th may on the 5D2.
Thanks!
Quote from: neopixel on June 06, 2013, 02:22:56 AM
Hi guys!
I'm looking for the crop factor mode into the ML menu, but can't find it! Can anyone help me?
I'm running build 29th may on the 5D2.
Thanks!
just zoom in :)
Haven't changed anything... now it's running on 1880 x 854 25fps without problems. Buffer is always between 1 or 2 *
Perhaps a bit off topic but - I'm not a filming pro and everything I know, I learned through tutorial videos or articles on the internet. But what are the advantages of using 24fps? Sure, in this case it's less data on the card. But what are the advantages from a "design" point of view?
Quote from: danielcreed on June 06, 2013, 08:20:32 AM
just zoom in :)
Also thought so - but my zoom buttons are not working with Magic Lantern, which makes it somehow hard to focus, also.
Quote from: Clemens on June 06, 2013, 09:56:19 AM
Haven't changed anything... now it's running on 1880 x 854 25fps without problems. Buffer is always between 1 or 2 *
Perhaps a bit off topic but - I'm not a filming pro and everything I know, I learned through tutorial videos or articles on the internet. But what are the advantages of using 24fps? Sure, in this case it's less data on the card. But what are the advantages from a "design" point of view?
24FPS is an industry standard as far as filming goes, it's been since the early days of filming, you get a very filmic motion blur to the shots.
that's the jist of it
Quote from: danielcreed on June 06, 2013, 10:22:40 AM
24FPS is an industry standard as far as filming goes, it's been since the early days of filming, you get a very filmic motion blur to the shots.
that's the jist of it
-and ideally it's combined with 1/48 shutter speed (47 in ML ) to approximate 180 degree shutter in film.
Quote from: Clemens on June 06, 2013, 09:56:19 AM
Haven't changed anything... now it's running on 1880 x 854 25fps without problems. Buffer is always between 1 or 2 *
Wow, nice, what cards are you using? I have a Komputer Bay 64GB 1000x and I only get 677 frames on 1720x968@25fps with a.d. build from yesterday.
I have Lexar 64gb 1000x and I can't go over 55MB/s and it is 10MB/s less then normal. Is there any topic about how to set your 5d for the most MB/s possible? I turned draw off, only s size picture, no sound, etc.
Quote from: Lukasz on June 06, 2013, 01:19:42 PM
I have Lexar 64gb 1000x and I can't go over 55MB/s and it is 10MB/s less then normal. Is there any topic about how to set your 5d for the most MB/s possible? I turned draw off, only s size picture, no sound, etc.
at what resolution and aspect ratio do you get continuous recording?
1880x706 aspect ratio 2.67:1 frame rate 24.000
And the frame rate ?
Quote from: Lukasz on June 06, 2013, 01:27:03 PM
1880x710
yes. is your canon menu set at 24fps? If yes, try setting FPS override in ML menu to 24 as well.
look the menu option "live view/movie func.set "
And set "Stills + movie" and "movie display".
Movie rec size at 1920 X 1080 24fps.
I've done those two things. Also in my search for the "golden setting" I've noticed that when You change the main camera dial to either custom or automatic mode You will gain a few buffer stars but there might be some controls issues . Do not know is that an obvious thing for everybody.
I know that 24fps are cinema standard and 25fps PAL Standard. So i always just sticked to 25fps without really questioning why. I also used 1/50th to apply to the 180° shutter rule, and so far everything worked out. But I don't understand - is it a big difference to record in 24fps? Is it noticeable? Haven't found good articles on the net about it.
@Olik: I'm using a Lexar 1000x 64GB Card - and strangely it didn't work out first, but now i did about 15 recordings all about 7 or 8 GB, and Buffer was always very stable on 1 or 2 *
Quote from: Lukasz on June 06, 2013, 01:39:35 PM
I've done those two things. Also in my search for the "golden setting" I've noticed that when You change the main camera dial to either custom or automatic mode You will gain a few buffer stars but there might be some controls issues . Do not know is that an obvious thing for everybody.
What build date are you using?
Quote from: ted ramasola on June 06, 2013, 02:01:40 PM
What build date are you using?
Now I use 04 june so the newest one, but I've been testing all avilable 5d mark II builds and my Lexar 16gb 400x is doing 40MB/s and new Lexar 64gb 1000x max is 55MB/s. I turned off all possible things and there is slight improvment but nowhere near 1880x800 not filling the buffer up.
Quote from: Lukasz on June 06, 2013, 01:39:35 PM
I've done those two things. Also in my search for the "golden setting" I've noticed that when You change the main camera dial to either custom or automatic mode You will gain a few buffer stars but there might be some controls issues . Do not know is that an obvious thing for everybody.
HA ! really interesting, in custum functions mode you get almost twice the buffer ! and now i get twice the number of frames at 1880x800
Quote from: danielcreed on June 06, 2013, 02:18:05 PM
HA ! really interesting, in custum functions mode you get almost twice the buffer ! and now i get twice the number of frames at 1880x800
HA ! So it is not obvious for everybody. Yes You can do twice amount of the frames like in pravdomil's topic picture when he posted his build. 1% commented on it "I see all the buffer stars you got and I'm jealous :)" and I thought everybody knew how to do it. So now eveyone will get even more frames than me... :'(
Quote from: Lukasz on June 06, 2013, 02:25:10 PM
HA ! So it is not obvious for everybody. Yes You can do twice amount of the frames like in pravdomil's topic picture when he posted his build. 1% commented on it "I see all the buffer stars you got and I'm jealous :)" and I thought everybody knew it. So now eveyone will get even more frames than me... :'(
guess this is a new breakthrough :) just did a few tests now and i get double nr of frames on all resolutions that weren't stable for me :)
Quote from: danielcreed on June 06, 2013, 02:27:58 PM
guess this is a new breakthrough :) just did a few tests now and i get double nr of frames on all resolutions that weren't stable for me :)
Happy for You and that I was useful. In this case maybe start a new topic for people to spread it around.
already spreading the word m8 :)
Quote from: danielcreed on June 06, 2013, 02:43:08 PM
already spreading the word m8 :)
Also started new topic in Raw discussion ;)
http://www.magiclantern.fm/forum/index.php?topic=6221.0
Quote from: Lukasz on June 06, 2013, 01:19:42 PMIs there any topic about how to set your 5d for the most MB/s possible? I turned draw off, only s size picture, no sound, etc.
+1
Is there a list of things to do to improve the recording stability? It would be so helpful!
Quote from: danielcreed on June 06, 2013, 02:18:05 PM
HA ! really interesting, in custum functions mode you get almost twice the buffer ! and now i get twice the number of frames at 1880x800
what is the "custum functions mode" and how do i enable it?
I'm noticing vertical stripes in some test footage I just shot. Both the a.d. and ML bitbucket builds of raw2dng.exe (that was just updated) exhibit this anomaly. Unfortunately, I didn't keep the previous version around to see whether it's a problem with Raw2Dng, the latest ML build (6397e112ed41), or something else. Raw2Dng seems to be making a lot of corrections now whereas a lot of values were at 1.000 in the older version.
edit: JPEG for a quick look: http://dl.dropboxusercontent.com/u/63799907/000350.jpg
DNG: http://dl.dropboxusercontent.com/u/63799907/000350.dng
Hello All :)
With 5D2
i was interested to see how good the Raw DNG image is, in term of scalable.
So i took 1880x854 24p DNG file import to photoshop and upscaded to 4096 x 1861
maintained the 240 dpi, 16 bit tiff, Basic White Balance & Color Correction
when you play the video in the small screen you will notice moire & aliasing
But thats only in the small player go to full screen and there is no
moire & aliasing.
The Original file on the image quality tab is the 4K mp4 i uploaded .
Quote from: ch_d on June 07, 2013, 12:34:45 AM
what is the "custum functions mode" and how do i enable it?
they're on your dial knob, labeled C1 C2 C3 :)
4K video does not look good , even on my only 2.5k monitor.
really nasty edges.
upscaling = bad idea. ;)
Hi all,
I am shooting on the latest build (6-6-13) and I am noticing that a lot of my shots when imported into Premiere, seem to be playing as if in fast forward... anyone else having this problem? Adobe After Effects composition FPS is set to 23.976 (same as premiere).
Resolution: 1880x800
CF Card: Lexar 32GB Extreme (90mb/s)
Workflow: Raw2DNG--ACR--After Effects CS6 (export) TIFF--(import) Premiere CS6
Any Thoughts?
Thanks for the incredible work ML, you guys are making film history right now!
@Yoshiyuki Blade
31_05_WIN.zip (https://dl.dropboxusercontent.com/u/13314708/31_05_WIN.zip)
04_06_WIN.zip (https://dl.dropboxusercontent.com/u/13314708/04_06_WIN.zip)
07_06_WIN.zip (https://dl.dropboxusercontent.com/u/13314708/07_06_WIN.zip)
@b.a.s.
You also need to check the export from aftereffects to avi or ProRes
Quote from: Yoshiyuki Blade on June 07, 2013, 02:28:49 AM
I'm noticing vertical stripes in some test footage I just shot. Both the a.d. and ML bitbucket builds of raw2dng.exe (that was just updated) exhibit this anomaly. Unfortunately, I didn't keep the previous version around to see whether it's a problem with Raw2Dng, the latest ML build (6397e112ed41), or something else. Raw2Dng seems to be making a lot of corrections now whereas a lot of values were at 1.000 in the older version.
edit: JPEG for a quick look: http://dl.dropboxusercontent.com/u/63799907/000350.jpg
DNG: http://dl.dropboxusercontent.com/u/63799907/000350.dng
You are right... i also noticed those stripes... but with my footage they are not that obvious and looked like some noise pattern.
a.d.-
I'll check avi and report what I find. It's not possible to use ProRes without FCP is it? Third party plug-in?
Its possible to use Apple pro res with Adobe after effect and premiere.
You can also export To Quicktime-Animation. It is a lossless (meaning near 100% quality) like apple prores 4444.
Quote from: Yoshiyuki Blade on June 07, 2013, 02:28:49 AM
I'm noticing vertical stripes in some test footage I just shot. Both the a.d. and ML bitbucket builds of raw2dng.exe (that was just updated) exhibit this anomaly. Unfortunately, I didn't keep the previous version around to see whether it's a problem with Raw2Dng, the latest ML build (6397e112ed41), or something else. Raw2Dng seems to be making a lot of corrections now whereas a lot of values were at 1.000 in the older version.
edit: JPEG for a quick look: http://dl.dropboxusercontent.com/u/63799907/000350.jpg
DNG: http://dl.dropboxusercontent.com/u/63799907/000350.dng
You can remove those vertical stripes with ACR and masking option or luminance.
@seanturco I know, but if a more elegant solution exists, I'd prefer to use that. :)
@a.d. Thanks! I can confirm that the May 31st build looks good.
Any improvement with this one? https://bitbucket.org/hudson/magic-lantern/downloads
a1ex: The stripes still appear under Adobe's camera raw tool, but Raw Therapee's output (what I've been using regularly) looks just fine to me: http://dl.dropboxusercontent.com/u/63799907/000350-2.jpg
I mean, with the new raw2dng (uploaded 5 minutes ago), is there any improvement?
Yeah, the image I just posted was from the fresh build you linked. The stripes appear when opening the DNG with Adobe Camera Raw, but Raw Therapee (what I used for the image above) seems to read it fine.
The one from photoshop (no color corrections obviously): http://dl.dropboxusercontent.com/u/63799907/000350-3.jpg
update: Hang on, I think there's still stripes on the Raw Therapee version too. I was using the CLI earlier and might have used the wrong directory by accident, gonna doublecheck (edit: yeah, it turns out to have stripes too). The file opened with RT's GUI has stripes too. Sorry for the confusion.
Can you open this DNG in photoshop? http://a1ex.magiclantern.fm/bleeding-edge/raw/000000.dng
In ufraw it's 100% clean.
Yeah, it's clean in photoshop as well. Maybe it depends on what build of raw2dng I used at the time of posting that? I honestly can't remember whether it was one of your earlier builds or a.d.'s...
Yes, raw2dng has banding correction, and the algorithm was tweaked a few times.
Ok. Well, here's the DNG from the raw2dng.exe you posted ~30 mins ago: https://dl.dropboxusercontent.com/u/63799907/000350-4.dng
You sure about that? Post the md5sum of raw2dng you have used and the conversion log.
MD5: eec7a999eece55305222ae455003445c
I don't know where the conversion log is. If it's at the end of the conversion... well I'll have to wait for ~6k frames to extract :P. I'll update in a couple mins.
Yep, it's the same as mine. The conversion log is whatever it prints on the terminal.
Can you upload the source raw? (or better, the first few MB of it)
This latest build 6/6 is great speedwise.
However, I don't know why ML doesn't seem to save my raw settings. On previous builds it did. I even went in to the tools menu and made it save config now. I'm going to have to go back to an older build for now as I can't be changing 4-5 raw settings every time the camera is powered down and up.
Quote from: a1ex on June 07, 2013, 03:44:01 PM
Yep, it's the same as mine. The conversion log is whatever it prints on the terminal.
Can you upload the source raw? (or better, the first few MB of it)
Ah, I'm not sure how to copy text from the Windows command prompt so I can't provide that info atm. I'm guessing the relevant info is the vertical stripes correction? It reads like so:
1.000 1.000 1.028 1.025 1.064 1.059 1.028 1.027Never tried splitting before so I don't know if HJsplit is appropriate. Here's the first 30 MB it produced: https://dl.dropboxusercontent.com/u/63799907/M06-1624-merge.RAW.001
The original is like 14.5 GB :o so at that point, I might as well have made quick random recording instead.
The resulting DNG looks perfectly clean here...
http://a1ex.magiclantern.fm/bleeding-edge/raw/1624.dng
Hmm, not here. I'm noticing stripes in both Raw Therapee and Photoshop, particularly noticeable by the wooden fence in the back.
hey guys, trying to run my own tests but the link on the front page seems to be broken.
http://5dfilmmaking.com/05/how-to-shoot-raw-video-on-your-5d2/
can anybody share instructions on how to get it up and working? thanks
Hm, looks like weighting for highlights was the issue here.
Can you try these two converters?
http://a1ex.magiclantern.fm/bleeding-edge/raw/raw2dng_w1.exe (weight=1)
http://a1ex.magiclantern.fm/bleeding-edge/raw/raw2dng_wlog.exe (weight=log(x))
Both look much better. I'll give the edge to raw2dng_w1.exe.
Processed JPEGs:
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_w1.jpg
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_wlog.jpg
DNGs:
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_w1.dng
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_wlog.dng
I can just barely notice some vertical stripes on the blurry leaves to the left of the rose with the wlog version.
Cool. Now I have one DNG that has banding in the sky with these weights, and looks perfect with the one from the repo. Go figure...
Hehe, perhaps there's no silver bullet. :o Seems like quite a predicament here!
If its any help, vertical stripes are sometimes visible in cr2 files, especially if their pushed in post. Not sure if its the same thing.
Since there are a couple of threads more or less dealing with RAW builts for 5D2 I think I may have lost overview; is there some sort of change-log to see what is going on in newer builts? I have not updated since over a week and I am still using the may 27th built with pravdomils module as it worked quite well for me... looking at some posts it feels as if newer builts were not always an improvement, what are the major additions in the latest versions?
@yoshiyuki: can you also try these two?
http://a1ex.magiclantern.fm/bleeding-edge/raw/raw2dng_wlog_ev.exe (log weight, histogram in EV instead of multiplication factors, no longer skewed)
http://a1ex.magiclantern.fm/bleeding-edge/raw/raw2dng_w1_ev.exe (weight=1, histogram in EV)
Africashot, you mean something else than the 'Change Log' on the front page of the forum?
Quote from: mvejerslev on June 07, 2013, 06:48:44 PM
Africashot, you mean something else than the 'Change Log' on the front page of the forum?
Yes, I mean something specific to the 5D2 builds that are currently flying around... and I am not really saying there should be a changelog for this in specific, a vague update on what has been implemented over the last week will do it for me ;)
Quote from: a1ex on June 07, 2013, 04:44:44 PM
Cool. Now I have one DNG that has banding in the sky with these weights, and looks perfect with the one from the repo. Go figure...
lol. I was afraid your fix for people with stripes might give us stripes.
Quote from: fatpig on June 07, 2013, 09:52:34 AM
4K video does not look good , even on my only 2.5k monitor.
really nasty edges.
upscaling = bad idea. ;)
its hard to Really to Judge 4K content on the net or on a 2.5K monitor,
the test was to see if it can be upscalded , and it can With More Work
& setup the shot alot better etc....
Like i said in my YouTube post it can be used As "B-Roll"
a second of two of footage mixed in to 4K content with a red or C500.
I guess i will do a proper Test and Use my Canon "L" lens not my cheap Sigma. :)
Does the Dolly mode work on 5D2? I'm using June 4th build and I'm having trouble with it. Is there a guide how to use it somewhere?
When I go into crop mode with 'dolly mode' enabled I can only get the frame to move within the display (using 1600x680) so I can dolly just a little. How can I get it to dolly from one side to the other? If there is a post explaining, please let me know. I have tried to search...
Quote from: marten on June 07, 2013, 10:21:50 PM
Does the Dolly mode work on 5D2? I'm using June 4th build and I'm having trouble with it. Is there a guide how to use it somewhere?
When I go into crop mode with 'dolly mode' enabled I can only get the frame to move within the display (using 1600x680) so I can dolly just a little. How can I get it to dolly from one side to the other? If there is a post explaining, please let me know. I have tried to search...
i have used it with no problem, basically what i did was enable dolly mode , then start filming
press the little joystick up or down to pan then hit the center of the joystick to stop.
i can only pan up and down in full screen, i have not tried it in crop mode :D
edit: Sorry i didn't read your question right :-[
Only a very small amount on 5D2, according to this chart: http://www.magiclantern.fm/forum/index.php?topic=6215
Maybe it's more useful for 2.35:1 with vertical panning?
@a1ex The results are quite similar to before. w1 looks virtually perfect for this particular image while log shows some faint stripes.
JPEG:
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_w1_ev.jpg
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_wlog_ev.jpg
DNG:
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_w1_ev.dng
https://dl.dropboxusercontent.com/u/63799907/000350_raw2dng_wlog.dng
what happened to the tutorial URL?
Quote from: soulshooter on June 08, 2013, 03:12:09 AM
what happened to the tutorial URL?
YOu can use the google cache if you need it.
Ok I really need some help here. So I had ML on my mark ii for some time, so I decided I would try RAW. It worked at first but when I shut my camera off it wouldn't boot back up. I pulled the battery and CF card out. I deleted everything ML related off the CF card, the problem is the camera runs fine with just the battery, but when I put in the CF card it wont boot up!! Please HELP!
new build is amazing!!! im recording pretty much full hd 2:1 raw no stop... i dont really need bigger files than 4GB, specially for commercial production... thanks guys!!!! again! :-X
Quote from: noix222 on June 08, 2013, 07:15:08 AM
new build is amazing!!! im recording pretty much full hd 2:1 raw no stop... i dont really need bigger files than 4GB, specially for commercial production... thanks guys!!!! again! :-X
Sounds interesting, what built are you using (could you post a link please?) thanks a lot!
Quote from: noix222 on June 08, 2013, 07:15:08 AM
new build is amazing!!! im recording pretty much full hd 2:1 raw no stop... i dont really need bigger files than 4GB, specially for commercial production... thanks guys!!!! again! :-X
using jun 6 build? Full HD meaning 1920 x 1080? With jun 6 build 5d2 only does 1880 max and I'm only getting 1,400 frames around 3.7 gig before buffer overflows with 1880 x 940 2:1. Are you sure its "no stop" recording at 2:1 ? 2:1 ratio does not give you "full hd" spec. The closest to fullhd spec is 1880 x 1058 16:9 which currently gives around 348 frames.
Highest resolution with stable continuous recording using current builds is 1880x854 2.20:1 ratio.
using jun 6 build... not full hd but 2:1 is close enough... yes that's pretty much what everyone using a 1000x+ card will get with a 5dmk2 i guess... personally i dont like filming long takes, unless it is necessary, or im intended too. So 4GB limit with RAW is fine for me, with +-1500 frames i can film a lot of stuff ! :D im going to get a mk3 to work together... might be good live out of the moire/aliasing word tho. :o
edit: probably for the last five months all my work was finished with 2:35 crop.... now its coming out straight ! :D and RAW that's GOLD for me!
Quote from: reddeercity on June 07, 2013, 10:28:43 PM
i have used it with no problem, basically what i did was enable dolly mode , then start filming
press the little joystick up or down to pan then hit the center of the joystick to stop.
i can only pan up and down in full screen, i have not tried it in crop mode :D
edit: Sorry i didn't read your question right :-[
Ok, so the dolly mode cannot pan the entire sensor from left to right in crop mode. I think that would have been useful.
There's a small delay when changing the crop window (at least via properties). Maybe in the future we'll figure it out.
On 5D3/6D, the crop window has over 3500 pixels, and panning makes a bit more sense there.
Quote from: Chan875 on June 08, 2013, 04:16:28 AM
Ok I really need some help here. So I had ML on my mark ii for some time, so I decided I would try RAW. It worked at first but when I shut my camera off it wouldn't boot back up. I pulled the battery and CF card out. I deleted everything ML related off the CF card, the problem is the camera runs fine with just the battery, but when I put in the CF card it wont boot up!! Please HELP!
had this problem a while back, the card is probably busted, i had to pull the clock battery out just to get the camera to boot.
Quote from: togg on June 08, 2013, 03:33:16 AM
YOu can use the google cache if you need it.
worked like a charm. thanks!
Quote from: danielcreed on June 08, 2013, 01:18:05 PM
had this problem a while back, the card is probably busted, i had to pull the clock battery out just to get the camera to boot.
Actually I got lucky and fixed it this morning. When I put the CF card in the camera it wouldn't boot, I had deleted ML RAW so I decided to try and download v2.3 back on to my card. When I put the card back in the camera it booted up with ML on it just fine!
I do get some little black/stuck pixels with ISO 1250 and higher :-[ :-[ :-[
Great work to all the dev! The last build seems really cool. I'm doing some noob testing with my sandisk 60mb/s (43/real).
The image quality is so wonderful <3
(http://i.imgur.com/OalRAGM.jpg)
Quote from: sebble on June 09, 2013, 12:13:09 AM
I do get some little black/stuck pixels with ISO 1250 and higher :-[ :-[ :-[
camera raw should help you to get rid of them :)
Hello All :)
install the new June 8th built, speed is the same 1880x854 good and steady, reliable.
i did have a problem in crop mode 10x recorded 1880x854 pink corruption on the top 1/3
of the image and the bottom 2/3 was distorted, but on alternating frame , used the new
raw2dng.exe .
i had no problem in the 5x crop mode @ 1880x854 look OK & of course in full screen had No problems.
I like the raw record menu option :) that's great plus the option for the black overlay is cool to,
personal i don't use it .
i did notice a slight increase in writing load from 64.3MB/s to 67 - 68.5MB/s
i had not problems writing with my Lexar 1000x 32GB card .
i going to do the tests again and see if i have problems with the 10x mode.
Quote from: reddeercity on June 09, 2013, 06:15:24 AM
Hello All :)
install the new June 8th built, speed is the same 1880x854 good and steady, reliable.
i did have a problem in crop mode 10x recorded 1880x854 pink corruption on the top 1/3
of the image and the bottom 2/3 was distorted, but on alternating frame , used the new
raw2dng.exe .
i had no problem in the 5x crop mode @ 1880x854 look OK & of course in full screen had No problems.
I like the raw record menu option :) that's great plus the option for the black overlay is cool to,
personal i don't use it .
i did notice a slight increase in writing load from 64.3MB/s to 67 - 68.5MB/s
i had not problems writing with my Lexar 1000x 32GB card .
i going to do the tests again and see if i have problems with the 10x mode.
You could record in x10 crop mode with the 5d2 now? I did know it could do that.
Testing it.
yes, you can record in 10x & 5x
i just finish a crop record test to see if i still had the problem,
I seem to have no problem now :o
this is a list of what my 5D2 did in crop mode i think it was 5x ,
1920x1038= 365 frames @24p
2048x820 = 2040 frames @24p :)
2048x930 = 540 frames @24p ???
2152x1078 = 176 frames @24p
and at 2K the image is out standing ;D
recorded to Lexar 1000x 32GB card
update: 10x crop mode
2152x718 @24p until the card is Full
Write speed 63.0 - 66.2MB/s (about)
1 Star Buffer most of time, the odd time
it would go to 2 buffer stars but only briefly
Quote from: reddeercity on June 09, 2013, 07:45:10 AM
yes, you can record in 10x & 5x
i just finish a crop record test to see if i still had the problem,
My test with my charts show that you can't record in 10x crop mode.
You will be viewing canon preview in 10x magnify and when you press raw recording, only 5x crop mode will be recorded with offset framing.
In 5x magnify crop mode, you can use ML preview for proper framing (b&W) and what you you framed is actually what is recorded.
So here are my issues with this build, jun 8 uploaded by a.d.
1. raw recording should not be possible when 10x magnify is engaged if only 5x is possible. An info text should show instead what is and what is not possible.
2. Half press shutter enables raw recording when af-on is selected, half press should be disabled for raw record.
3. Settings are not saved upon power off and reboot and defaults not ideal, for instance wav recording is default when this is problematic on 5d2.
with so many settings to engage before recording, like ratio, sound, rec button etc, saving your settings is important.
4. a minor bug, after format, the file browser is not updated immediately and still shows old files. though upon turning lv on and off then going back to ml menu it is now refreshed. this is minor but might mislead someone.
1. what if you want to focus on the bigger image?
2. that's why I still recommend the LiveView button (all these top buttons send the same code)
Quote from: a1ex on June 09, 2013, 09:52:26 AM
1. what if you want to focus on the bigger image?
2. that's why I still recommend the LiveView button (all these top buttons send the same code)
Focusing via magnify is always an aid tool, but information should be indicated that what is recorded is still 5x crop, as previous poster reddeercity mistakenly believes that what he is seeing is actually being recorded. If this is left as is its ok, but really less useful as it is less accurate for framing.
The previous build does not activate recording via half press. Just remove the live view option for record as consensus is that most find the options between af_on or joystick is a more logical in terms of "finger management". ;)
edit: I double checked going far as may 31 and found that , YES half press raw rec is still there.
So, ok if this is difficult, we can leave it as is, I can live with it as accidental recordings can now be deleted unlike the early builds.
Well, the AF-ON is technically impossible to implemement reliably (if you compile from the official repo you won't find that there), and joystick... it's for centering the focus box.
I prefer portable code, and for now, LiveView button is the only portable solution, because almost all other cameras are using it for normal H.264 recording (except 50D). The idea behind modules was that they should be portable, same binary working on all cameras.
Also, a.d. should point out the differences between his builds the and main repo.
Quote from: a1ex on June 09, 2013, 10:07:50 AM
Well, the AF-ON is technically impossible to implemement reliably (if you compile from the official repo you won't find that there), and joystick... it's for centering the focus box.
I prefer portable code, and for now, LiveView button is the only portable solution, because almost all other cameras are using it for normal H.264 recording (except 50D). The idea behind modules was that they should be portable, same binary working on all cameras.
Also, a.d. should point out the differences between his builds the and main repo.
for the rec button, i'm fine that the options are given.
its ok then. I can live with it as it would be similar to some video cameras with dual or even triple buttons for recording, the handgrip, top handle and sometimes in other part of the camera body, in eng cams it would be in the left part front area.
Hopefully the ability to save settings would also finally be figured out, I think that's more important than the other quirks I am reporting.
Hi Guys! Need help!
I have used mac about ten ears. But now i have noob brain for this moment. I try to install Raw to MKII.
Downloaded right zip from topicstarter link, Copied file to ML root folder and started terminal like this
(http://s019.radikal.ru/i638/1306/47/529663ac761d.png)
And it has ganerated some new files.
(http://s16.radikal.ru/i190/1306/67/8886fbbf167e.jpg)
Tell me, what i'm doing wrong, and can someone make quick little tutorial step by step.. )) I need to shot a music video in several hours. Big thanks.
Big thanks :)
Quote from: aleksei.lungu on June 09, 2013, 01:18:05 PM
Hi Guys! Need help!
I have used mac about ten ears. But now i have noob brain for this moment. I try to install Raw to MKII.
Downloaded right zip from topicstarter link, Copied file to ML root folder and started terminal like this
http://s019.radikal.ru/i638/1306/47/529663ac761d.png
And it has ganerated some new files.
http://s16.radikal.ru/i190/1306/67/8886fbbf167e.jpg
Tell me, what i'm doing wrong, and can someone make quick little tutorial step by step.. )) I need to shot a music video in several hours. Big thanks.
Big thanks :)
What exactly are you trying to do in Terminal? Joining files over 4 GB? You don't need to fiddle with that to record RAW video on the 5D Mark II.
Look at the tutorial (http://wiki.magiclantern.fm/install) on how to install Magic Lantern on your camera.
The latest OSX RAW2DNG isnt working for me :-[, creates two separate folders both empty and lots of txt shows in the box underneath in details, im using an older version which works well :) but would be nice to be able to use some of the new features :) im not sure what version im currently using either as under About it shows 1.0 still and noticed it says that on all versions i downloaded.
Quote from: noix222 on June 08, 2013, 08:42:34 AM
using jun 6 build... not full hd but 2:1 is close enough... yes that's pretty much what everyone using a 1000x+ card will get with a 5dmk2 i guess... personally i dont like filming long takes, unless it is necessary, or im intended too. So 4GB limit with RAW is fine for me, with +-1500 frames i can film a lot of stuff ! :D im going to get a mk3 to work together... might be good live out of the moire/aliasing word tho. :o
edit: probably for the last five months all my work was finished with 2:35 crop.... now its coming out straight ! :D and RAW that's GOLD for me!
Can you please share (upload) your complete ML foder with autoexe.bin and *.fir files... I cant seem to manage it to work... its confusing why there are no complete builds for download... thank you very much!
Quote from: cheguevara on June 09, 2013, 08:26:05 PM
Can you please share (upload) your complete ML foder with autoexe.bin and *.fir files... I cant seem to manage it to work... its confusing why there are no complete builds for download... thank you very much!
If you go back to pages (6), (7) i wrote a short tutorial how to
install from the beginning with prepare your card etc...
about half way down the page.
make sure you read the part about "SCRIPTS" on page 7 ;)
Quote from: PressureFM on June 09, 2013, 05:09:13 PM
What exactly are you trying to do in Terminal? Joining files over 4 GB? You don't need to fiddle with that to record RAW video on the 5D Mark II.
Look at the tutorial (http://wiki.magiclantern.fm/install) on how to install Magic Lantern on your camera.
Hi PressureFM, i don't have any problems with installation of ML to my Mark II, problem is, how to install RAW plugin or patch, or what ever it is to camera. I tryed a latest build, the link is same as topicstarter updated on first page.
Quote from: reddeercity on June 09, 2013, 09:43:42 PM
If you go back to pages (6), (7) i wrote a short tutorial how to
install from the beginning with prepare your card etc...
about half way down the page.
make sure you read the part about "SCRIPTS" on page 7 ;)
Yeah i've done that and had it working a few weeks ago when it started but it buged alot so i reverted to original ML
Its hard to find 6june build with modules and .fir an autoexec.bat combination thats working...or any other for that sake... dont know why its not included in nightly builds...
sorry but i really cant find the combination thats working :(
even when i find the one that shows Modules menu in ML it does not record raw...
PS. i find it hard to belive that 60mb/s is not enough for 2K raw video... as 2K picture is roughly 2Mmpix in RAW that about 2-3mb. Make it 2.5mb x 24frames is exactly 60mb/s needed for it... :o
Im using 16gb 60mb/s SanDisk cards
Quote from: cheguevara on June 09, 2013, 11:06:45 PM
Yeah i've done that and had it working a few weeks ago when it started but it buged alot so i reverted to original ML
Its hard to find 6june build with modules and .fir an autoexec.bat combination thats working...or any other for that sake... dont know why its not included in nightly builds...
sorry but i really cant find the combination thats working :(
even when i find the one that shows Modules menu in ML it does not record raw...
PS. i find it hard to belive that 60mb/s is not enough for 2K raw video... as 2K picture is roughly 2Mmpix in RAW that about 2-3mb. Make it 2.5mb x 24frames is exactly 60mb/s needed for it... :o
Im using 16gb 60mb/s SanDisk cards
OK, :)
i way just doing some crop 5x recording @ 2152x820 24p & i can only get about 2000 frames then it stops.
now the only reason that it stops is the bus interface to the CF card was never design to maintain write speed beyond
69.9 MB/s. How do i know this? because of the above test i was doing.
the camera Started to write @66.5 MB/s & built up to 68.5MB/s until the bus interface can't keep up anymore and stops.
this is when it goes be-on 69.8 MB/s
i have a Lexar 1000x 32GB , benches @write 65.5MB/s read @ 70 MB/s that it. i just keeps up in a 5d2, if it was a 5d3 it design to write @ 90MB/s & up becauses of the "all i" in h264.
i have a Scandisk 32GB 60MB/s 400x, the max size it records is 1440x810 24p, it benches @ 50MB/s with 16k alignment & 32K alignment
drop to around 40MB/s.
to get more stable speed
Try to format your card but do a low level format, uncheck the Quick format box & try a 16K alignment
it will take some time 30 to 50 min.
How are you setting up camera ?
what frame size are trying to capture?
Start at lower frame size and find one that you can record a full card at,
then work with the next size up and fine tune the camera, eg. turn of overlays etc..
to see if you can get that stable.
I hope that helps :D
Hi, i tested it weeks ago with 1880x800 or so and 1280*720... the later one worked for about 4-5 sec before skipping frames...
but now it's not working :( i'm trying everything but it just not even showing Modules menu or when it does (raw video checked) does not start raw recording (it does h.264) ...
im missing something definitely... ???
Helloo
I have 5d m2 , when I installed the ML there was no RAW VIDEO function !!
how can i get it ?
Quote from: cheguevara on June 10, 2013, 01:11:38 AM
Hi, i tested it weeks ago with 1880x800 or so and 1280*720... the later one worked for about 4-5 sec before skipping frames...
but now it's not working :( i'm trying everything but it just not even showing Modules menu or when it does (raw video checked) does not start raw recording (it does h.264) ...
im missing something definitely... ???
before you try the below,
in the Modules folder do you have ?
FILE_MAN.MO
MAGIC.SYS
RAW_REC.MO
and the new autoexec.bin on the Root of the card
this must be from the some built, can not mix difference Raw record modules
components
Try deleting the log files in the ML folder/Logs folder
first, i do this when i load new Raw record module
if that doesn't Help delete the setting files (2 of them)(*.cfg)
:)
go back to 14-Bit RAW video Builds for 5D2, n there be a download section at top in red, choose latest win or osx, replace files on card with downloaded ones (tip: open each folder and drag n replace)
Quote from: Burair on June 10, 2013, 01:30:46 AM
Helloo
I have 5d m2 , when I installed the ML there was no RAW VIDEO function !!
how can i get it ?
go to page 6 & 7 that should help and go to page 1 to down load the
latest raw modules ;)
Quote from: reddeercity on June 10, 2013, 01:47:57 AM
go to page 6 & 7 that should help and go to page 1 to down load the
latest raw modules ;)
i will try and come back
thank ;)
Hi All,
Can you give me advise on buying a card for 5D2 RAW? Should I go for:
1) 32GB SanDisk UDMA7 90MB/s card
or
2) 32GB Lexar 600X 90MB/s card?
I'm not planning to buy the Lexar 1000x card, just want to know which one of these 2 is better.
I am currently running 5D2 with June 06 firmware and I can record about of 45 seconds of 1720x732@24p on an old 8GB SanDisk 60MB/s card.
Thanks,
M
I'm having a strange problem. When I try to make a RAW recording, or even a benchmark test!, without reason at a certain point the mirror shut down and the live view button make a blue light. The RAW recording is corrupt and I can't take out the dngs (Error: This ain't a lv_rec RAW file).
I'm using the latest build and raw2dng macosx for 5D2 Beta ver.0.4.
:(
@mgm : I have the SanDisk 90MB/s card (got it a week or so back). It works great, no complaints.
Quote from: Raelic on June 10, 2013, 04:08:39 PM
@mgm : I have the SanDisk 90MB/s card (got it a week or so back). It works great, no complaints.
Your using this on the 5dmkII right? are you able to record 1720 x 968 or 1880 x 854 continuously with this card without dropped frames? This could be a cheaper solution, I have the lexar 1000x and is looking to buy a 2nd one.
Quote from: Raelic on June 10, 2013, 04:08:39 PM
@mgm : I have the SanDisk 90MB/s card (got it a week or so back). It works great, no complaints.
Cool, what's the maximum resolution you get for continuous shooting, and how with how many buffer stars?
Thx
Hello I tried the raw 5d m2, and it worked.
When i tested the raw video i got 2 problems :
- the camera goes off automatically !
- when i record i get a pink bar while shooting for 1 sec only !
any solution ?
Quote from: Burair on June 10, 2013, 07:19:22 PM
Hello I tried the raw 5d m2, and it worked.
problems :
- the camera goes off automatically !
Do you mean that the mirror shut down automatically? It's my problem :'(
Auto power off > Off
Quote from: Raelic on June 10, 2013, 04:08:39 PM
@mgm : I have the SanDisk 90MB/s card (got it a week or so back). It works great, no complaints.
Really?
I just tried with the latest build and my 64gb card (UDMA 6 version) and I can't get passed 800 frames. The constant write is around 60mb/s and I am using the 1880 resolution. I was told somewhere to go into "hacker mode" and turn off global draw. Couldn't find that mode, but global draw off gave me an extra 20 frames.
I have the Sandisk Extreme Pro 32GB 90MB/s UDMA7 card, too.
In some recent tests with the newest build from 06/08/13, I can most of the time record contiously at 1880x800. Just sometimes the write rate decreases for some unrecognizable reason which causes the buffer to overflow.
But still, I'm waiting for a Lexar 1000x 32GB to arrive these days. This card is said to be even faster on the 5D2; so the recording could be much more stable due to the transfer rate.
Quote from: a.d. on June 10, 2013, 07:53:57 PM
Auto power off > Off
Omg THANK YOU. This was driving me crazy. I don't know how I've not understood it by myself. Yesterday it wasn't shutting down.
Anyway, my Sandisk 16GB 60mb/s can record a full card with 1472X828 resolution.
QuoteYour using this on the 5dmkII right? are you able to record 1720 x 968 or 1880 x 854 continuously with this card without dropped frames? This could be a cheaper solution, I have the lexar 1000x and is looking to buy a 2nd one.
Ted, I bought a Sandisk Extreme Pro 90MB/s card, and it will do 1880x800 continously but above that it stops before 4GB.
Hello All :)
Every one that's thinking of Buying Other then a Lexar 1000x 32GB CF card.
you will Not have Stable continuous Raw recording @ 1880x845 @24p or any Standard size.
i have spent a many days with my(2) Scandisk 400X 60MB/s,16GB, (1) Scandisk 400x 60MB/s 32GB ,(1)Scandisk 600x 90MB/s 32GB
the Maximum Write Speed for Scandisk is average 43MB/s to 52MB/s and the odd time it would hit 60 MB/s but only for a moment.
that was on the 600x Scandisk. The only stable size for continuous that i got on my 5d2 was 1440x810 ?
and at that it wasn't that stable.
if you are only looking for 100-200 frames any card can do, but really that's no good.
i can continuous record raw @1880x854 until full about 7.5 minute.
in 5x crop mode i can continuous record raw @ 2152x808 24p until card is full.
i Get only 1 buffer star and the readout says i'm recording @ 67.8 MB/s, & for 1880x854 thats 64.3 MB/s :)
in 5x crop mode 1920x872 24p i can do about 2000 Fames .
you must remember there is over head in the file writing, so if you need let say 50MB/s and you card is good for 50MB/s
you would think that would be OK, but in reality you would need about 53- 55Mb/s to maintain 50MB/s
so in the End it would be to every ones advantage if you but a higher end CF Card like, Lexar 1000x, or Hoodman 1000x etc....
Personal i will stay with the Lexar 1000x cards 32 or 64, there are Rock Solid and a Great investment,
and it you ungrade to 5d3 then you are set to go '
" It always better to have too much than not enough" ;D
1) well.. it's simple to say get a lexar but in Europe where i live it's about 410$ the 32GB one :)
2) Transcend 1000x and the others (Komputerbay and Sandisk 90MB are pretty stable in you record in 800x instead of 854x (continuous i mean) (I dont consider it a big difference)
3) With the latest speed improvements there is hope to get stable 854p for the others
4) The Lexar 1000x will never be used at full speed on a 5D2 (so you pay for something you will never use)
5) a fast CF card is not a good investment.. Sure, after 3 years when you're gonna switch for the 5D3, you'll be able to get a Kingston, Transcend, Delkin (cheap cards) with 128-256GB of storage able to record full HD 25/30fps
6) Did i mention that it costs 410$ in Romania? :))
Quote from: mihaii on June 10, 2013, 11:20:14 PM
6) Did i mention that it costs 410$ in Romania? :))
It's not the right topic to talk about that but... on ebay you can buy it 140€. And I think it's already a lot.
Can anyone confirm 10th july build more stable than 8th?
i like 8th july's but im worried bout 10th july's lol ;D
June sorry not July... thinking ahead!! haha :P
i see your point , :) i didn't realize that there so hi-priced :o
in Canada i paid 1/2 that $200.00 , I don't understand that, 2X the cost
How about HoodMan? or Toshiba 1066x ?
Quote from: mvejerslev on June 10, 2013, 08:43:48 PM
Ted, I bought a Sandisk Extreme Pro 90MB/s card, and it will do 1880x800 continously but above that it stops before 4GB.
Thank you for this info. How about 1720 x 968 ? Its slightly less wide but a bit higher than 1880 x 800 and can easily be scaled since it is 16:9 ?
QuoteHow about 1720 x 968
Considered higher than 1880x800.. I can shoot a minute or a bit more in 1720 x 968, but its above the threshold for continuous so far.
Quote from: mvejerslev on June 11, 2013, 12:31:59 AM
Considered higher than 1880x800.. I can shoot a minute or a bit more in 1720 x 968, but its above the threshold for continuous so far.
Thank you. I was thinking of wiggling down a bit to slightly lowers speeds for cost savings, but based on your tests, I think that current ML raw development demands the high speed 1000x cf cards to get the maximum possible performance from the 5D mkII.
Thanks again.
I like the warning on the new build :P
:)
Just testing the new June 10th built, it look like there is a little more speed :D
i have more stable frame sizes as follows
5x crop mode
1920x872@24p =2777 frames
2048x820@24p = continuous
2048x856@24p = continuous
2048x872@24p =1500 Frames
2152x808@24p = continuous
2152x860@24p = continuous
Non crop mode
1728x972 @24p = continuous
1880x854 @24p = continuous
1880x940 @24p =1500 Frames
tested with Lexar 1000x 32GB
Wow -- I'm seeing 70MB/sec on this build which is about 650 frames at 1880 x 1016. Great work everyone.
a.d. / Alex, is there any way to enable 1806 x 1016 as a 16:9 resolution choice? With the latest speed improvements, that might now be a continuous resolution for 16:9 on the 5d2.
Edit: Ok likely not continuous -- I'm seeing 2300 frames at 1880 x 940, which is great. If 1806 x 1016 is 1000 frames or better, that would be a great option.
Again, great work.
Okay, a follow-up question, - which of the 1000x cards is better for 5D2?
1) 32GB Komputerbay 1000x
vs
2) 32GB Lexar 1000x
Thanks,
M
There's such variation card to card that I don't know that there is an answer to that question. Personally, my Komputerbay 64GB 1000x is faster than my Lexar 32GB 1000x. But for others it may be the reverse.
For me the 10th build is an improvement in speed. I can get about 770 frames in 1880 x 940 now on a Komputerbay 1000x 64GB. Great work! I' am so happy!
The Zacuto Monitor still doesn't show the right frame size and the position of the frame shifted to the left side. So, work with an external monitor is still very difficult. I hope this could be fixed.
Wait a minute... my latest speed optimization was 3 days ago... (1479df3+f884d7a+150a9c5)
Could it be this? https://bitbucket.org/hudson/magic-lantern/commits/61b6b1dc97a15a6c780cdae587a75679fc53aac3
Can you run a hg bisect to identify the changeset?
1479df3+f884d7a+150a9c5
The 3 were already in last build, only 61b6b1d was not.
Is the edmac_memcpy, 150a9c5, fixed not for corrupt frames?
wow... so 10th's June seems be a big step forward again! Thanks guys who got back to me! sounds like a must have!
Sorry to say, that I don't know how to run a hg bisect. I am running the last version posted here: https://bitbucket.org/a_d_/magic-lantern/downloads 1222c61e8120.zip.
Works great! Except the Frame size and position in external monitor.
i got it working somehow :)))
but i find few quircks... average speed of h.264 is 50-54mbs and raw doesnt fo furhter than 35mbs ???
how to record 1280x720 without crop
Quote from: a.d. on June 11, 2013, 11:26:13 AM
Is the edmac_memcpy, 150a9c5, fixed not for corrupt frames?
I have no idea, you have to find out ;)
Quote from: cheguevara on June 11, 2013, 11:42:56 AM
i got it working somehow :)))
but i find few quircks... average speed of h.264 is 50-54mbs and raw doesnt fo furhter than 35mbs ???
how to record 1280x720 without crop
Don't forget that RAW unit of measurement for bitrate is in MB/s (mega
bytes per second) while h.264 is in Mb/s (mega
bits per second). 1 byte = 8 bits.
50-54 Mb/s video is only about 6.5 MB/s. RAW video pushes the bitrates on the 5D2 up to 60-70 MB/s!
Hi everyone!
I've got transcend 1000x 16Gb UDMA7 and ML benchmarks shows that it's capable of write speed up to 70Mb/s
In real action it shows no more than 58Mb/s
As I understand write speed depends on buffer size? And this speed/buffer size combination is unique for every card?
Is it theoretically possible to squeeze maximum from my card (this case 70Mb/s) by some sort of buffer size optimization or the only option here is to buy "legendary" Lexar 32Gb 1000x?
Hi everyone.
I ran into problem while trying to convert some of the raw videos.
While most of them are easily converted with the latest raw2dng (10 june), three videos (shot on build 08 june) of my batch reported following error:
"File Supported Error: This ain't a lv_rec RAW file"
Is there any solution?
PS Thanks to all developers for their amazing work!
So I installed the latest build on my 5DMK2, recording works just fine with a Transcend 32GB 400x (60MB/s) BUT
I'm experiencing one major problem: as soon as I drag the .RAW file (in this case 370MB) into the RAW2DNG.app, it says "file supported" but there aren't any DNGs in the designated folder that is created by the converter. :'(
has anyone had the same problem and got it solved?
Cheers, Alex
Quote from: scarimbolo on June 11, 2013, 07:39:57 PM
So I installed the latest build on my 5DMK2, recording works just fine with a Transcend 32GB 400x (60MB/s) BUT
I'm experiencing one major problem: as soon as I drag the .RAW file (in this case 370MB) into the RAW2DNG.app, it says "file supported" but there aren't any DNGs in the designated folder that is created by the converter. :'(
has anyone had the same problem and got it solved?
Cheers, Alex
Got same problem :-[ im using an older version that works great and also use RAWmagic which is nice indeed, iv noticed theres things you can do to get the latest RAW2DNG working but ill be honest and say i dont know much about terminal and how to code it to work, going to stick with old version and latest RAWmagic for now as there working great so far :)
This new build (1222c61e8120) gets my write speeds up to 66.*MB/s, where as the last (d5a606e8c616) got me 63.*MB/s. At 1728x972 (25fps) thats got me up from around 700 to around 1200 frames before it hit's the wall.
Nice one chaps!
ok... i have not been clear enough its 50000 kbps so its about 47 mbps ;) for h.264 and only 35000 kbps for RAW
anyway ill thnk ill do a low level format...
the other thing is how to rec 1280x720 without croped frame...
Is there any way we can save our settings in the raw module? It's great for experimenting now but for practical use it really would be beneficial to set up my preferred settings (rec button, resolution, sound sync beep on) and not have to reset them on each boot.
Quote from: silvertonesx24 on June 11, 2013, 10:42:23 PM
Is there any way we can save our settings in the raw module? It's great for experimenting now but for practical use it really would be beneficial to set up my preferred settings (rec button, resolution, sound sync beep on) and not have to reset them on each boot.
I totally agree. It's a nightmare every time the card is taken out to check out the footage on the computer and then having to go through the laborious process of setting up a RAW module settings. And if you need to quickly record something its near impossible if you have to go through the settings again. ::)
The ability to be able to save the settings is very important and really hope that we see something soon.
Also I just thought I would also applaud the noted increase in speed performance in writing! YAY! :D
Quote from: Doyle4 on June 11, 2013, 09:28:10 PM
Got same problem :-[ im using an older version that works great and also use RAWmagic which is nice indeed, iv noticed theres things you can do to get the latest RAW2DNG working but ill be honest and say i dont know much about terminal and how to code it to work, going to stick with old version and latest RAWmagic for now as there working great so far :)
I'm jumping around my desk writing this. Just downloaded Version 0.9 and it finally works after 2 entire days of trial, failing and raging! Thank you for your suggestion, you saved me!
Quote from: scarimbolo on June 12, 2013, 12:03:07 AM
I'm jumping around my desk writing this. Just downloaded Version 0.9 and it finally works after 2 entire days of trial, failing and raging! Thank you for your suggestion, you saved me!
No problem dude!! glad i helped you out! dont like knowing people are missing out on the best ML ever so far ;D
Could this post be pinned at top by any chance? its going further and further down the page each day :P i like this section as its where i get my latest's beta's ;D
Cheers
I have problems with my external SmallHD DP4 monitor. The recording preview frame is off ... In the camera it is on the right place.
Sorry for abit of a noob question..
Is the Alpha one for 5Dmkii the same as latest modules but all combined into one download?
sorry if this reads wrong im bad at grammar, what im trying to say is if i download the latest modules (12th June) and replace old ones is it the same as just downloading the full alpha one?
Cheers,
Doyle
5D2 Alpha One is a complete editon for beginners. The main idea is to create a starting point package.
For update just download the update build like before.
Quote from: a.d. on June 12, 2013, 06:24:57 PM
5D2 Alpha One is a complete editon for beginners. The main idea is to create a starting point package.
For update just download the update build like before.
Thanks a.d. ill carry on the way i have before then, cheers :)
I've got it ... 600 MB RAW file. But now I start raw2dng for WIN and the cmd-window appears for a short time. Nothing with drag-and-drop. It's late and I'm tired. Please spend me some ideas what's going wrong.
Thanks.
ralf4u
maybe you have lv_rec error?
Any ideia why in the newest build's when i use the 5x i cant see the white frame anymore.. it was so useful to me! it is something that i can customise?
edit: i can record 70mb/s always in 5x but in normal mode it goes around 68 67mb/s only is that right ? ? im with fps override 24 all time...
Hey Guys,
New to the Forum, but have been messing with the new raw function since it first went live. I'm getting weird magenta shadows wherever the camera is dealing with Moire in the latest build (6/12). Anyone else seeing the same?
On my 5D2 and with (2013/06/10)-build I was able to record at 1880x800@24,00fps until my Sandisk Extreme Pro (UDMA7) was filled up (32GB).
The write rate differed between 59MB/s and 62MB/s; so the buffer filled slowly (but didn't reach the top, before the card reached it's end).
A new Lexar 32GB 1000x arrived today. With it and the latest build (2013/06/12) I'm now able to continously record at 1880x854 @ 25,00fps!
Using jun 12 build posted by a.d I made chart tests to check the centering and framing of cropped raw recording.
The preview image using ML grayscale is low res and pixelated, but using a res chart to guide in centering and framing I made these measurements.
This might help ML programmers in making corrections for crop mode preview.
resolution: Offset in pixels: ^=up <=left
2152 x 1078 46^ 12<
2048 x 1078 49^ 9 <
1920 x 1078 69^ 9 <
1880 x 1058 69^ 1 <
1880 x 854 17^ 2 <
1728 x 972 58^ 5 <
I've done the tests twice and some of the offsets would vary by 2-7 pixels so the results I averaged.
The vertical offset is bigger, the horizontal is a bit negligible, I hope this can still be tweaked to make this feature more usable.
below are 2 frames from the test to show the offset framing.
1728 x 972
(https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-prn1/1014744_526206410769762_600208766_o.jpg)
1880 x 852
(https://fbcdn-sphotos-g-a.akamaihd.net/hphotos-ak-prn1/1015225_526206407436429_1946786011_o.jpg)
Hello everyone! my English is very bad, so I write a google translator) At the forum, I was a novice to yet I do not programmer, but I've tested all assemblies for 5dmII. Virtually all builds (except 5/19/2013 and 5/31/2013) I see a strange artifact - a green dot on the bottom left of the screen closer to the center. at the latest build it too is (a4ed372144). strange, but praised the latest build, it turns out that it only bothers me (maybe someone knows what this is? problemmy with my equipment? (http://i.imgur.com/72EVLv8.jpg) (http://i.imgur.com/Od3kL3o.jpg) (http://i.imgur.com/ZGP4tGo.jpg)
Yesterdays build (a4ed3721fc44) has a small negative impact on speed for me. I've lost approx 1-2 MB/s compared to 1222c61e8120. Great to have record back on the set button. And no more magenta previews in finder, at least not for me when using RAWMagic b4 on Mac OS 10.8.3.
Hi There! I am trying to install the latest release from two days ago, but it won't install! It goes from the first firmware update screen to blank! Then I have to take the battery out to reboot again... I don't get it.
I have had a previous ML installed which is ML-5D2-unified-2011Dec22-EarlyPreview for capturing HDR video. Now I have not used this for a long time and figured, let's install a new ML for capturing RAW!
It just won't install. Anyone have had this problem and how do I install it?
Thanks!
edit: My current firmware version is 2.1.1 because I needed that for my previous ML
Quote from: tepelstreeltje on June 13, 2013, 12:56:00 PM
Hi There! I am trying to install the latest release from two days ago, but it won't install! It goes from the first firmware update screen to blank! Then I have to take the battery out to reboot again... I don't get it.
I have had a previous ML installed which is ML-5D2-unified-2011Dec22-EarlyPreview for capturing HDR video. Now I have not used this for a long time and figured, let's install a new ML for capturing RAW!
It just won't install. Anyone have had this problem and how do I install it?
Thanks!
edit: My current firmware version is 2.1.1 because I needed that for my previous ML
Remove ML from ur camera, upgrade to
2.1.2 and then go back to page one on this topic and download the 5D Alpha One :)
Thanks! It works now! ;D
Nice update guys for the x5 and x10 framing :D
is x3 possible on 5D mkii at all? sorry if this has been mentioned else where.
Cheers
Oops my bad, Framing has been known as an issue in x5 and x10... fast reading for you ha. But save feature is good ;D
in the assembly "ee3385aa13bd" green dot is: (it's a small problem, but I hope it will correct)
Next release!
Playback frame skiping! Fast preview. Dynamic interface coordinates. Mask box updated to recording frame, now with no flicker. Restored frame skipping. Some module credits.
https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo (https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo)
Quote from: pravdomil on June 13, 2013, 05:33:06 PM
Next release!
Playback frame skiping! Fast preview. Dynamic interface coordinates. Mask box updated to recording frame, now with no flicker. Restored frame skipping. Some module credits.
https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo (https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo)
This is good development. Question; Is this update based on the jun 13 build which also allows settings to be saved?
Hello, since I suppose that the RAW silence mode is basically the same as the RAW video mode, I post a maybe slightly OT question here, please apologize. I was asking more than 4 months ago here in the forum, if it was possible to get a per-frame-flash-trigger out of my 5DII while recording movie. This seemed not to be possible. Now that there is this very fast burst mode coming into my camera I wonder if I can get my studio flashes triggered with that? I can´t test it right now. Does anyone know something about that?
Thanks! Martin...
QuotePlayback frame skiping! Fast preview. Dynamic interface coordinates. Mask box updated to recording frame, now with no flicker. Restored frame skipping. Some module credits.
Source code please.
FYI: playback can be done realtime without skipping anything.
Quote from: pravdomil on June 13, 2013, 05:33:06 PM
Next release!
Playback frame skiping! Fast preview. Dynamic interface coordinates. Mask box updated to recording frame, now with no flicker. Restored frame skipping. Some module credits.
https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo (https://bitbucket.org/pravdomil/raw_rec.mo/downloads/raw_rec.mo)
awesome job !!! but in 5x there is no mask box... it is possible?? I personally like to see the white mask before i shoot so i can frame correctly... would love that too... thanks guys
source
https://bitbucket.org/a_d_/magic-lantern-hack (https://bitbucket.org/a_d_/magic-lantern-hack)
works with latest a_d_ build, download from the begining of this forum
saving conf works too
last build is great "ee3385aa13bd"
I did some test in 16:9 ratio @25fps without drops in C1 mode :
1880x1058 = 250 frames (+ 2% scale for 1080)
1728x972 = 1050 frames !!!! (+11 % scale for 1080)
1600x900 = infinite at only 1* and 1000 frames with audio (+20% scale for 1080)
Curently write speed is @ 65-69 mb/s with a transcend 1000x 32Gb
XML config saving is very useful !!!
Great improvements... :D
decided to look for this green dot on the screen 5d2. and indeed, this point is present during the recording of "raw"! turn off the "raw" module, and it remains to zoom 10! but after the return of a zoom 0 point disappears. it's all in "ee3385aa13bd" (http://i.imgur.com/dVsZNBQ.jpg)
Quote from: pravdomil on June 13, 2013, 06:38:06 PM
source
https://bitbucket.org/a_d_/magic-lantern-hack (https://bitbucket.org/a_d_/magic-lantern-hack)
works with latest a_d_ build, download from the begining of this forum
saving conf works too
I like your fast preview implementation. Good work!
Hello All :)
Just been Test the 5x Crop mode very nice !
the only problem i still have is when i use my Zacuto Z-Finder EVF
the framing for the Raw is off and down to one side
works Ok with h264 record.
I just Started a documentary about a street artist Today with Raw
the images are truly impressionable :D
nice video. You say that you also film in h.264. Do yu mean that it,s possible to film in 5x mode also in h.264? I couldn,t get this to work on my 5d mark 3 and can,t find any info about it? Would you care to explain?
Thanks
//Daniel
Quote from: Danne on June 14, 2013, 07:50:46 AM
nice video. You say that you also film in h.264. Do yu mean that it,s possible to film in 5x mode also in h.264? I couldn,t get this to work on my 5d mark 3 and can,t find any info about it? Would you care to explain?
Thanks
//Daniel
No, I was refering to EVF with h264 recording & I just check my 5D2 & crop recording is only in Raw ???
Hi,
yesterday I had a bit of time for an outdoor test with the 5D. I wanted to test how was the focus with a deep depth of field, because you know, when you shot at f/16 with the 5d, everything is very blurry with a lack of detail and sharpness.
The overall quality looks good, a part from the noise presence multiplied with the grain of fimconvert(I simply forgot to denoise the footage).
I don't see any noticeable artifact or moire/aliasing problem(I use the VAF-5D2 filter btw).
For the green dots, I used the Simple wire removal from AE.
There's just one thing I don't like at all, the choppy panning. It was not a shutter issue(I was at 1/48th). What can it be? Any idea? Or is just an impression?
I had that choppy issue recently while editing my raw footage in Adobe Premier. Upon closer inspection, I realized the footage had not been interpreted properly. It was 29.97 instead of 23.976. As soon as I fixed this, the footage was smooth.
Ok so I will double check this. ;D
Quote from: a1ex on June 13, 2013, 06:00:31 PM
Source code please.
FYI: playback can be done realtime without skipping anything.
well I add fps measurement to playback and I got only 8fps with 5D2 1880x800 at 25p, no fast preview, no frame skip, Lexmark 64GB 1000x.
I noticed After effects was making my footage 30fps, its do with your comp settings, but even changing it to the right fps it put its back to 30fps when making an image sequence, like you say, drag the sequence in and just it back to the fps and its all good ;D
Quote from: avasarin on June 14, 2013, 01:40:43 PM
I don't see any noticeable artifact or moire/aliasing problem(I use the VAF-5D2 filter btw).
So in your opinion is it worth the price?
Quote from: togg on June 14, 2013, 03:40:59 PM
So in your opinion is it worth the price?
Of course. It gives you the freedom to shoot wherever you want. The only cons I see is the minimal focus shifting and the bad performance with zoom, because it didn't hold the focus while zooming. But This cons are microscopic against moiré and aliasing.
Quote from: avasarin on June 14, 2013, 04:34:35 PM
Of course. It gives you the freedom to shoot wherever you want. The only cons I see is the minimal focus shifting and the bad performance with zoom, because it didn't hold the focus while zooming. But This cons are microscopic against moiré and aliasing.
Thanks. I'll wait until I'll be able to afford it :)
Quote from: Doyle4 on June 14, 2013, 03:13:27 PM
I noticed After effects was making my footage 30fps, its do with your comp settings, but even changing it to the right fps it put its back to 30fps when making an image sequence, like you say, drag the sequence in and just it back to the fps and its all good ;D
You need to change the standard import sequences to 24 frames in preferences dialog box.
I'm having hot pixels with high ISOs (higher than 1250) and I've read many posts about it.
the newest build still has the hot pixel issue.
will it be fixed soon? or is it problem with raw2dng?
Quote from: a.d. on June 14, 2013, 06:51:26 PM
You need to change the standard import sequences to 24 frames in preferences dialog box.
Sweet, didnt notice that! cheers
@durisy
I've just updated raw2dng. There's a new algorithm for hot pixel fixed based on chdk
Hey guys,
I was getting 320 frames 1880/1058 @16x9 on a 1000x Lexar 16gb, with the 14th build I am now getting 280.
Love the preview though!
a.d.
Im still getting error:
raw2dng converter GUI for 5D2 Beta ver.0.7 /Volumes/EOS_DIGITAL/DCIM/100EOS5D/M14-1752.RAW File Supported /Users/doyle/Downloads/5D2_OSX_raw2dng/raw2dng.app/Contents/Resources/script: line 10: 564 Segmentation fault: 11 raw2dng "$fldr$name".RAW
Iv moved the raw file to desktop and tried n same, put in a folder and gettin the same, iv tried adding the other file into show package and same, think im on verion 0.4 still, i dont understand the command line thing either sorry.
Would love new version for the pixel fix
Cheers
Shot on 5DII with one of these builds, color in Photoshop, Vimeo killed a lot of the sharpness and introduced some artifacts.
Tested Jun 14 build.
No new problems found and was able to test long recordings that was able to fill up 32 gig card. Was able to extract all frames with no problems in both dng and cdng.
I pushed tested 1728 x 972 as this is the highest 16:9 resolution that I found easy to upscale to 1920x 1080.
Unfortunately I realized that it can only go approx 10,000 frames, buts its already good for most commercial or corporate needs as this is already at 7 minutes and near to the capacity of the card at 27.7 gig before buffer is filled and stops.
1880 x 854 2.20:1 is now the highest resolution at 24p possible on 5d2. This fills up card till full. Resulting file is 29.7 Gig(31,930,872,768 bytes).
I corrected the spreadsheet posted by roman here http://www.magiclantern.fm/forum/index.php?topic=6215.0 to reflect this new test results.
Hoping the framing in crop mode could also be tweaked and fixed.
Good job so far guys.
Quote from: ted ramasola on June 15, 2013, 09:34:31 AM
Hoping the framing in crop mode could also be tweaked and fixed.
I doubt it can be further improved without low-level access to the sensor.
Quote from: a1ex on June 15, 2013, 09:42:16 AM
I doubt it can be further improved without low-level access to the sensor.
A1ex,
At first I thought the offsets were random but I found out that they're "almost" consistent across repeated tests.
The Horizontal could be "negligible" since its mostly 2-16 pixels but its the horizontal offsets that at least needs adjusting so the user will be warned that the top will be cut off up to 69 pixels (lines) .
Using ML grayscale preview method, won't this involve moving crop marks or borders? For instance for 1920x1078 moving the black border masks (both top and bottom) up by 69 pixels? Although I understand that the pixel count might not be the same in low res preview as to that in final recorded frame.
Can we see some upscaled test footage from 1728 x 972 (16:9) to HD 1920 x 1080p Ted Ramosa ?
Can we .. can we ... pretty please ?! lol
Ideally with and without the Mosaic VAF-5D2 ! ;) I did buy one a few months ago but it had a tiny air bubble in the glass so sent it back. I also need to shoot stills and video so ultimately i'm living with the moire / aliasing for now ...
I've not installed the Raw update of ML just yet, waiting for all the little bugs to get ironed out on my 5D2. But getting very excited ... ;D
Just loaded 4c83f9edabc0 (latest built by a.d.) after not updating for a while; nice improvements in performance, these are just a few details I have noticed:
- The option to delete files is gone (or am I not looking in the right place?) for me at least it used to be more useful then the preview option as I usually know right away if I messed up or not... but its maybe just me...
- Is there an (official way) way to stop the preview playback? Half-pressing the shutter will stop it but triggered a buck by still showing the preview on the lower blacked out part of life view in at least one occasion
I hope this helps and please forgive me if any of this has been brought up before!
Ted: of course the offsets are not random. The recording window can't be positioned anywhere on the sensor; there are some large raw windows chosen by Canon code based on the position of the focus box, and within these windows, ML can move the smaller recording window freely.
So, at this point, ML is centering the recording window on the focus box as best as I could do.
Quote from: Africashot on June 15, 2013, 10:25:47 AM
Just loaded 4c83f9edabc0 (latest built by a.d.) after not updating for a while; nice improvements in performance, these are just a few details I have noticed:
- The option to delete files is gone (or am I not looking in the right place?) for me at least it used to be more useful then the preview option as I usually know right away if I messed up or not... but its maybe just me...
- Is there an (official way) way to stop the preview playback? Half-pressing the shutter will stop it but triggered a buck by still showing the preview on the lower blacked out part of life view in at least one occasion
I hope this helps and please forgive me if any of this has been brought up before!
Use the File Browser to view and delete files. Its more secure since it asks for confirmation if you really want to delete.
Thanks for the tip on how to stop playback by half press of shutter. It works for me.
Great as it is to have record on the Set button, being able to select AF-ON was quite useful. It meant you could start/stop record using a standard remote. Really handy when you can only record short clips and need the camera to be perfectly steady from frame 1.
Any chance we could have this back as a menu option?
Why not use the existing function for recording with half-shutter?
(didn't try it, but it should work, because it sends fake button events)
Yep, that works, ta.
Finding a few advantages and a few issues doing RAW recording with an Ikan V8000 monitor attached.
When dropping into record the HDMI output doesn't switch to 480p, so the picture stays at it's largest possible size on the monitor. Huge bonus.
Write speed seems slightly slower than with the internal display, but not much, maybe 5%.
The crop rectangle doesn't display properly. I get one of the two scenarios bellow. Actual recordings are not effected though.
(http://www.lightandtime.co.uk/media/ml/ikan1.JPG)
(http://www.lightandtime.co.uk/media/ml/ikan2.JPG)
EDIT - It seems if the HDMI is plugged in right through the session, from power up to power down, then I get the later. If the screen is plugged in after entering live view, or if it is disconnected and reconnected at any point during the session, then I get the former.
Hi,
I have these results with a Komputerbay 1000x i just got from amazon.
73.9 MB/s write speed
85.4 MB/s read speed
photo mode, global draw off.
at best.
(sorry don't know how to attach the jpg showing all banchmarks)
Do you think i should send it back ? seems low :(
You're on a 5D2? I'd try shooting some raw. If you're getting in the upper 60s MB/s then you're doing as well as I am.
Quote from: ted ramasola on June 15, 2013, 10:46:22 AM
Use the File Browser to view and delete files. Its more secure since it asks for confirmation if you really want to delete.
Thanks for the tip on how to stop playback by half press of shutter. It works for me.
Thanks Ted, the new file browser makes sense, I had no idea it was there, thanks for the pointer!
Quote from: andyshon on June 15, 2013, 03:29:05 PM
You're on a 5D2? I'd try shooting some raw. If you're getting in the upper 60s MB/s then you're doing as well as I am.
Yes i'm on a 5D2, you think it has something to do with it?
I shot this morning 1880x800 2.35 @24p, and i can do it continuously.
Seems like 1728x972 16:9 is ok too continuously.
sould i send back and hope for a better one? i ve seen benchmarks up to 110MB/S but on 5D3, is it related?
Alexcosy - is it 64Gb Komputer Bay 1000x or 128Gb ? The smaller capacity cards are apparently faster ...
Quote from: alexcosy on June 15, 2013, 04:22:37 PM
Yes i'm on a 5D2, you think it has something to do with it?
I shot this morning 1880x800 2.35 @24p, and i can do it continuously.
Seems like 1728x972 16:9 is ok too continuously.
sould i send back and hope for a better one? i ve seen benchmarks up to 110MB/S but on 5D3, is it related?
Don't send it back. It is definitely to do with the upper limit that you can write on the 5DMKII. When you run the benchmark you will most likely get a faster speed write but when you record you will see anywhere between 59 - 68 - 70MB/s sometimes mine goes above 70MB/s (briefly but its more usual to see it around 63MB/s)
I have a Komputerbay 1000x 32GB
So what I am saying is that if you buy a faster one it is pointless because the 5DMKII will cap it by its bus limitation (unfortunately). The 5DMKIII has a higher limit and I don't know exactly what that is because I have no experience of them.
Quote from: alexcosy on June 15, 2013, 04:22:37 PM
sould i send back and hope for a better one? i ve seen benchmarks up to 110MB/S but on 5D3, is it related?
Sounds like you got a good one there fella. I'd keep hold of it.
Thanks a lot for the advice guys, i'll keep it then :D
I have a 64 GB Komputerbay 1000x that usually gives me a speed of 64-68 MB/s. But on occasion I'll see an almost full buffer just suddenly empty without the write speed registering any real change. Never noticed this behaviour on the Lexar 1000x, but that could just be me not paying attention.
I like what i can do with 1880x800 2.35 anyway, so it should be sufficient.
Just a question, in AE, what color space do you set your project to? I think I'm noticing a bit of a gamma shift between ACR and AE when project set to "none".
Rec 709 is the colour space of standard HD video. If you're using a 10 bit or better codec and you intend to grade these shots further, you might want to consider using the broadcast limited version [Rec 709 (16-235)]. This way some highlight and shadow detail is retained beyond that visible in AE. However, these files will look flat in apps that don't honour broadcast levels, like QuickTime player and FCP.
Quote from: andyshon on June 15, 2013, 11:10:55 PM
Rec 709 is the colour space of standard HD video. If you're using a 10 bit or better codec and you intend to grade these shots further, you might want to consider using the broadcast limited version [Rec 709 (16-235)]. This way some highlight and shadow detail is retained beyond that visible in AE. However, these files will look flat in apps that don't honour broadcast levels, like QuickTime player and FCP.
I find that in AE on the Mac if you are importing the tiff sequence to render to ProRes 4444 and set the options
to "Trillion Plus" colors , "preserved the native color space" that put it in a 16bit and there is no gamma Shift that i can see.
ProRes will put it in a HD color space with out gamma shift.
But i have seen gamma shift on 10 bit codec of different flavors. :)
P.S. i use photoshop to white balance & basic color corrections to legal colors for grading
or you can built a L.U.T. or use the Camera Profiles :)
Been out for a few days, just seeing the auto-save feature now. Huge time saver, fantastic.
What is "fast preview" supposed to do? I'm not seeing any difference in live view mode or recording.
fast preview is for playback
next release, works with latest a_d_ build, download here
https://bitbucket.org/pravdomil/magic-lantern-hack/downloads/raw_rec.mo
some new features, look here
https://bitbucket.org/pravdomil/magic-lantern-hack/commits/all
Ah, ok, thanks. Do you mean in the file manager? Because playback in the file manager wasn't working at all for me just now using a.d.'s most recent build -- totally garbled, like television static.
yes playback is mostly corrupted, but using playback command in RAW menu immediately after rec works nice
Is anywhere i can go to read on how to make the latest build for mac work? i still dont understand why it wont convert n fails, using 0.4 still.. :(
Quote from: Doyle4 on June 16, 2013, 03:17:38 AM
Is anywhere i can go to read on how to make the latest build for mac work? i still dont understand why it wont convert n fails, using 0.4 still.. :(
Latest build of what? The ML firmware is pretty OS-agnostic, you just copy the files onto your CF card and the rest happens in-camera. :D
Sorry i was meant to add a quote about RAW2DNG latest build as it was mentioned somewhere in here someone else cant seem to get to convert on mac. Sorry about that.
ML is working great so far (14th July Build)
Hey, I was having the problem where Raw2DNG wouldn't work.
I think I found a fairly simple fix.
http://www.magiclantern.fm/forum/index.php?topic=5732.msg49469#msg49469
I had to replace the footer of the RAW files, then it ran in Raw2DNG with zero problems.
EDIT: There was one caveat. On files longer than 4.29GB, I could only get good DNG's out of the RAW file. But I had to abandon all the R00 files. I have no idea how to get those to work.
Hi,I noticed that "Bulb Ramping" menu is vanished after copying raw modules.
Are "Raw video" and "Bulb Ramping" exclusive functions?
Also I could no longer find Auto ETTR, has it been moved to a different location?
Auto ETTR is a module now; the build maintainers should probably include it.
Bulb ramping is obsolete, use intervalometer + auto ETTR + post deflicker instead: http://www.magiclantern.fm/forum/index.php?topic=5705
Thank you for your reply.
Quote from: percymate on June 16, 2013, 03:56:08 AM
Hey, I was having the problem where Raw2DNG wouldn't work.
I think I found a fairly simple fix.
http://www.magiclantern.fm/forum/index.php?topic=5732.msg49469#msg49469
I had to replace the footer of the RAW files, then it ran in Raw2DNG with zero problems.
EDIT: There was one caveat. On files longer than 4.29GB, I could only get good DNG's out of the RAW file. But I had to abandon all the R00 files. I have no idea how to get those to work.
I don't have a clue about coding so thats me out :(
As for R00 files you need to merge it with the other file, cant remember the file name
cheers
Which version of raw2dng works for you?
Quote from: a.d. on June 16, 2013, 01:26:47 PM
Which version of raw2dng works for you?
Im using raw2dng converter GUI for OsX Beta ver.0.10 :)
ill managed to get the new GUI working using the dng2raw file from 0.10 but i wasnt sure if that just makes the version i have now look better? im really wanting the new version for the fixes that have been made :)
Quote from: percymate on June 16, 2013, 03:56:08 AM
Hey, I was having the problem where Raw2DNG wouldn't work.
I think I found a fairly simple fix.
http://www.magiclantern.fm/forum/index.php?topic=5732.msg49469#msg49469
I had to replace the footer of the RAW files, then it ran in Raw2DNG with zero problems.
EDIT: There was one caveat. On files longer than 4.29GB, I could only get good DNG's out of the RAW file. But I had to abandon all the R00 files. I have no idea how to get those to work.
for R00 files you need too:
you need to combine the .RAW and the .R00 etc files.
On a Mac, in Terminal, you can use the command, for ex.:
cat file1.RAW file1.R00 > newfile.RAW
Then take newfile.RAW and drop it on raw2dng As quoted by Oedipax
With the latest build everything is corrupted :(
Quote from: togg on June 16, 2013, 02:03:14 PM
With the latest build everything is corrupted :(
uh huh :(
hopfully soon we will have answers lol ;D
@a.d.:
You should not touch lv_af_raw at all. Once you have enabled it for preview, you can no longer turn it off for recording, so you'll get "random" colored dots that contain AF info.
I was wondering why people are reporting stuff like this http://www.magiclantern.fm/forum/index.php?topic=6426.0 and this: http://www.magiclantern.fm/forum/index.php?board=49.0
After reviewing your changes, I've found the answer. Just leave it as in the official repo.
Thanks A1ex for taking the time to look at this, Looking forward to using RAW2DNG again!
a.d. is it possible to add a section in the program where you can add split files to join?
Thanks again Devs ;D
hello guys. sorry my ignorance, but what 5x or 10x not correct framing will do wrong?? ... I mean is 5x recording useful? I used a couple of times with the build 06/06 and i can't see any problem with that.... what's up with the new build ?
Quote from: noix222 on June 16, 2013, 06:22:37 PM
hello guys. sorry my ignorance, but what 5x or 10x not correct framing will do wrong?? ... I mean is 5x recording useful? I used a couple of times with the build 06/06 and i can't see any problem with that.... what's up with the new build ?
preview image is not the same framing as recorded image.
@a1ex
Done!
Quote from: a.d. on June 16, 2013, 10:26:19 PM
@a1ex
Done!
A.d
Tested your upload b93d6ae2b30d.zip
The 3x crop mode ( 5x magnify ) framing is
much better now, I have only tested some important resolutions and aspect ratios and
they're use able.
1728 x 972 very good framing ( 8 v 6 < )
1920 x 1078 almost perfect ( 0 v 5 > )
1880 x 1058 good vertical off horizontal ( 14 ^ 145 > )
2152 x 1078 perfect vert good horizontal ( 0 , 16 > )
Pink Cast is back in 10 x magnify (I have read A1ex comments on this and your response in first post )
..
Thanks for the updates, ML working great but RAW2DNG still not converting for me (5D2_OSX_raw2dng_ProRes)
raw2dng converter GUI for 5D2 Beta ver.0.09 M16-2334 File Supported /Users/doyle/Downloads/5D2_OSX_raw2dng_ProRes/raw2dng.app/Contents/Resources/script: line 35: 954 Segmentation fault: 11 "$RAW2DNG" "$FLDR$FILE_NAME".RAW Generating ProResHQ 422 *.dng: No such file or directory ffmpeg version 1.2.1-tessus Copyright (c) 2000-2013 the FFmpeg developers built on May 9 2013 21:58:14 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --enable-runtime-cpudetect libavutil 52. 18.100 / 52. 18.100 libavcodec 54. 92.100 / 54. 92.100 libavformat 54. 63.104 / 54. 63.104 libavdevice 54. 3.103 / 54. 3.103 libavfilter 3. 42.103 / 3. 42.103 libswscale 2. 2.100 / 2. 2.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 2.100 / 52. 2.100 [image2pipe @ 0x102016400] Could not find codec parameters for stream 0 (Video: ppm): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options [image2pipe @ 0x102016400] Estimating duration from bitrate, this may be inaccurate pipe:0: could not find codec parameters DONE
Quote from: Doyle4 on June 16, 2013, 11:46:25 PM
Thanks for the updates, ML working great but RAW2DNG still not converting for me (5D2_OSX_raw2dng_ProRes)
raw2dng converter GUI for 5D2 Beta ver.0.09 M16-2334 File Supported /Users/doyle/Downloads/5D2_OSX_raw2dng_ProRes/raw2dng.app/Contents/Resources/script: line 35: 954 Segmentation fault: 11 "$RAW2DNG" "$FLDR$FILE_NAME".RAW Generating ProResHQ 422 *.dng: No such file or directory ffmpeg version 1.2.1-tessus Copyright (c) 2000-2013 the FFmpeg developers built on May 9 2013 21:58:14 with llvm-gcc 4.2.1 (LLVM build 2336.1.00) configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --enable-runtime-cpudetect libavutil 52. 18.100 / 52. 18.100 libavcodec 54. 92.100 / 54. 92.100 libavformat 54. 63.104 / 54. 63.104 libavdevice 54. 3.103 / 54. 3.103 libavfilter 3. 42.103 / 3. 42.103 libswscale 2. 2.100 / 2. 2.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 2.100 / 52. 2.100 [image2pipe @ 0x102016400] Could not find codec parameters for stream 0 (Video: ppm): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options [image2pipe @ 0x102016400] Estimating duration from bitrate, this may be inaccurate pipe:0: could not find codec parameters DONE
You'll get better responses in this thread I link below as this thread is now for more for the raw rec module .
RAW POST PROCESSING;
http://www.magiclantern.fm/forum/index.php?board=14.0
Sweet cheers man,
Thanks for the link, they have the new version 0.12 there so ill try that as its 0.9 on this thread
A.d and A1ex
comparing the 16th and the 14th, while malloc may have increase to 227k from 99-103k I somehow noticed a slightly lower performance in terms of number of frames recorded.
Here are some comparisons, I will place 2 figures(# frames) on each resolution indicating 2 takes.
Jun 14
1x
1880x1058 = 408/401
1880x940 = 1,900/2500
1880x854 = continuous
1728x972 = 9,995/10,175 (gd off, fps,hacked)
1728x864 = continuos
5x
2152x1078 = 185/184
2048x1078 = 243/236
1920x1078 = 335/335
1920x960 = 684/1064
1880x854 = continuous
Jun 16
1x
1880x1058 = 251/251
1880x940 = 1,064/1,520
1880x854 = continuous
1728x972 = 7,565/9,711 (gd off, fps,hacked)
1728x864 = continuos
5x
2152x1078 = 151/165
2048x1078 = 172/229
1920x1078 = 276/285
1920x960 = 760/694
1880x854 = continuous
GUI Tweak request;
When pushing for maximum performance in 1728x972 16:9 I engage FPS override even in 1x mode, hacked preview and GD off, however upon recording the text "FPS OVER RIDE 23.976" is so big and is almost inside the shot frame, can this be reduced and moved to a part of the frame that is not within the shot?
Quote from: a.d. on May 20, 2013, 05:27:13 PM
5D2 BUILDS WITH RAW_REC MODULE
Download the latest zip file
https://bitbucket.org/a_d_/magic-lantern/downloads
Source
https://bitbucket.org/pravdomil/magic-lantern-hack/
...
2013/06/16
b93d6ae2b30d
API change: Please delete from previous build ML/MODULES/MAGIC.SYM
malloc: Now we have 227 K vs 99 to 103 K
I remove my modification, so magenta Cast is back in 5x and 10x, because a1ex point out to to this thread http://www.magiclantern.fm/forum/index.php?topic=6426.0. Some users suffer from that.
So I copied/replaced
AUTOEXEC.BIN and ML folder from
b93d6ae2b30d.zip (https://bitbucket.org/a_d_/magic-lantern/downloads) to my CF card.
But it is messed up. Something doesn't work. The screen freaks out and there is and info about missing Font files and then to copy all the Magic Lantern files.
I got
2.1.2-ml-v2.3.NEXT firmware version from here:
https://docs.google.com/file/d/0BzDGCq2guBAgb2UtVE1SUy0yeTQ/edit
(http://crewofone.com/2013/how-to-shoot-raw-video-on-your-canon-5d2-5d3-or-6d/)
Is the file
hudson-magic-lantern-15694a53cfa3.zip necessary?
a.d. writes:
"Source
https://bitbucket.org/pravdomil/magic-lantern-hack/"
in the very first post of this topic. I have no idea where to paste it.
Thanks for help.
Added
------------
that's embarrassing. I replaced the whole ML folder instead of just the files which were in a.d.'s folder. If any admin want's to remove this post, please do it. Sorry for trashing.
@ted:
pink preview = good image quality.
good preview = many bad pixels.
I wasn't able to get both at the same time, so I've used good preview when idle and pink preview while recording.
see https://bitbucket.org/hudson/magic-lantern/commits/15694a53cfa3
In the last release force left corrupt everything. Am I the only one?
Did it work before?!
Quote from: a1ex on June 17, 2013, 03:00:39 PM
Did it work before?!
I don't remember until it works. But it is a couple of builds that I'm having problems. It's only today that I've figured out that it is the force left option.
Quote from: a1ex on June 17, 2013, 09:11:21 AM
@ted:
pink preview = good image quality.
good preview = many bad pixels.
I wasn't able to get both at the same time, so I've used good preview when idle and pink preview while recording.
see https://bitbucket.org/hudson/magic-lantern/commits/15694a53cfa3
good preview when idle pink when recording is a good compromise.
In raw video mode Pink preview only distracts while in 10x mode, I use this only to check focus,
in 5x mode the pink preview is not an issue since ML grayscale is what I would use due to correct framing.
Hi all, please excuse my newbiness if some / all questions were answered before. I did not find all the infos so let me ask few things :
- Why a pink preview, apart for performance, why not b&w and with more contrast ? I have troubles to follow focus the actors moving for examples.
- I need to retry more with the last night build but I have an issue with some raw recordings : not skipped frames but like unordered frames (eg: fr1, fr50, fr2, fr51 and so on) on raw recordings during more than 200 frames in any resolution. I tried to reencode in DNG with both actual converters RAW2DNG & RAWMAGIC : sometimes retrying fixes the problem, often not.
(PS: fr1, fr50 are frame numbers examples, not actual correct numbers).
- The Prores 422HQ file is interesting for previewing, but why not 4444 ?
- Any way to get MXF in 10 bit ? :)
- How come Resolve can't understand the DNG from RAW2DNG actual version but Lightroom & PS do ?
- Could you add a sub menu for setting for good different resolution according to crop modes ? It actually resets to 1880 and I would keep 2K for 5X & 10X
- Could you rewrite the link or email to donate ? I have something for you.
Thanks for reading and keep it up all, your work is just amazing, i'm addicted, you changed our minds !
On my 5D2 the preview is only pink now when cropped (5x or 10x).
But, when copied to the computer, all the footage is pink.
And opened in Adobe Camera Raw everything is fine.
Until the actual version everything was fine.
Strange...
Quote from: onickz on June 17, 2013, 07:32:46 PM
- Why a pink preview, apart for performance, why not b&w and with more contrast ? I have troubles to follow focus the actors moving for examples.
Sharpness, I think, is much more helpful than b&w for focusing.
Quote from: onickz on June 17, 2013, 07:32:46 PM
- How come Resolve can't understand the DNG from RAW2DNG actual version but Lightroom & PS do ?
That's due to the fact that Resolve only opens
CinemaDNG files. RAWMagic, which you already tried, converts into this format.
Quote from: onickz on June 17, 2013, 07:32:46 PM
Thanks for reading and keep it up all, your work is just amazing, i'm addicted, you changed our minds !
I second that!
I did a few tests comparing build 13/06 and 14/06 and i found that with build 14/06 if i record in 1x with fps override ON 24 fps exact fps 24 it will record actually 29.997 as when i convert with raw2dng it says that. I did tried turning fps override OFF so it got back to 23.... Build 13/03 is fine to me i can record both 1x and 5x with fps override and i get 24fps converting with raw2dng version 0.10. I can't use the latest build the pink cast makes me see NOTHING :P anyway i also figured out (that's already been pointed) what's been recorded in 5x is larger that what actually appears in the viewfinder. All my tests were done in 1880 and 2.1... thanks guys..
I'd also like to report that jun 16 build apparently totally drains the battery even when power is off.
There was still around 70 percent in the battery then Left it off for around 10 hours.
Has this quirk been reported before in other builds?
Is there a "proper" shutdown method to avoid this?
Yes, see http://www.magiclantern.fm/bestpractices
Quote from: a1ex on June 18, 2013, 12:13:08 AM
Yes, see http://www.magiclantern.fm/bestpractices
A1ex,
I have read of this and was in fact conscious of watching for the led blink before cf removal when I was doing some tests last night.
My question is,
1. if for instance, the card was improperly (before led blink) removed for data transfer, then returned to camera, then camera was further handled, then shut down. Does this still drain the battery? Or does this battery drain occur when CF card is out of the camera?
2. does it make a difference if card was removed when power switch is still on or is it best practice to switch it off then remove cf?
1. no; if the card stays in the camera after shutdown, there shouldn't be any problems; but if you remove it while the camera is off, and put it back without turning it on, you may have surprises.
2. if you do not turn the camera off, the problem does not occur. So, just open the card door without turning the camera off. I do this all the time.
To understand it better: when you open the card door and power switch is off, the camera wakes up for 2-3 seconds.
Quote from: a1ex on June 18, 2013, 12:39:18 AM
1. no; if the card stays in the camera after shutdown, there shouldn't be any problems; but if you remove it while the camera is off, and put it back without turning it on, you may have surprises.
2. if you do not turn the camera off, the problem does not occur. So, just open the card door without turning the camera off. I do this all the time.
To understand it better: when you open the card door and power switch is off, the camera wakes up for 2-3 seconds.
Thank you.
I believe that what you said in #1 happened in the course of my tests. Since we now have raw video which requires constant removal of card unlike h264 movs I suggest best practices page should include something like this warning.
...AFTER TRANSFER OF RAW MOVIES VIA CF CARD READER IT IS ADVISABLE TO TURN ON THE CAMERA AFTER ML CARD IS INSERTED THEN OFF BEFORE STOWING AWAY YOUR CAMERA.
something like that.
It has nothing to do with raw videos...
And you should turn it on after card removal, because that's when it's locking up.
A1ex,
with regards to the hdmi out framing being off to the left, how about having a turn off option for the record frame (black/white rect) when using hdmi so I can just overlay the appropriate matte over my ext monitor screen for framing?
Quote from: ted ramasola on June 18, 2013, 01:33:37 AM
A1ex,
with regards to the hdmi out framing being off to the left, how about having a turn off option for the record frame (black/white rect) when using hdmi so I can just overlay the appropriate matte over my ext monitor screen for framing?
If you select ML grayscale from the preview menu the white or black bars will not be displayed. With my Zacuto EVF I use the internal 2.35 mask and on my 7" monitor regular gaffer tape. Don't know if ML Grayscale is supposed to do so or is just an side effect.
Quote from: avasarin on June 18, 2013, 08:07:34 AM
If you select ML grayscale from the preview menu the white or black bars will not be displayed. With my Zacuto EVF I use the internal 2.35 mask and on my 7" monitor regular gaffer tape. Don't know if ML Grayscale is supposed to do so or is just an side effect.
Thank you!! I did not know selecting ML grayscale will remove the white rectangle. Thank you for that info.
I'm also making crop lines on clear acetate to overlay on my ext monitor.
YES! came to see what happened to Auto ETTR and its back in 18th July Build ;D Thank you! :)
Is x5 and x10 so pose to have be pink when AF-ing? Yesterday when filming x5 and x10 filled the screen with pink and was branded here none useable, are we able to use it now? Thanks again for a brilliant update ;D
See my earlier posts. In x5 mode, you can't get good image without pink preview (well, grayscale now).
If you have correct color preview while recording in x5, expect colored dots that you can't remove, because their position is not fixed (they follow high-contrast areas). This happens only on 5D2 and 50D afaik.
I'm awaiting delivery on a CF card that will give me enough speed to test this all out for myself, but I was wondering if anyone could shed some light on shooting 4:3
Is it possible on the MkII? What are the resolutions you can do it at and how many frames will you get?
Quote from: mymadness on June 18, 2013, 02:21:47 PM
I'm awaiting delivery on a CF card that will give me enough speed to test this all out for myself, but I was wondering if anyone could shed some light on shooting 4:3
Is it possible on the MkII? What are the resolutions you can do it at and how many frames will you get?
Yes, no problem. With my slow card I can get 1280X960 continuous. 49,1 MB/s. But with a 1000X CF you will be able to get 1472X1104 (65 MB/s).
So! I'm trying the latest build and finally I've realized that the only preview that EVER worked for me is the Canon one. I'm not able to use ML Grayscale or HaCKed.
edit: ok, now it seems that 5X and 10X are always grayscaled.
Quote from: a1ex on June 18, 2013, 02:17:16 PM
See my earlier posts. In x5 mode, you can't get good image without pink preview (well, grayscale now).
If you have correct color preview while recording in x5, expect colored dots that you can't remove, because their position is not fixed (they follow high-contrast areas). This happens only on 5D2 and 50D afaik.
Cheers A1ex,
Ill give the X's amiss for now as not too important at this moment for me,
Thanks for the reply.
Quote from: mymadness on June 18, 2013, 02:21:47 PM
I'm awaiting delivery on a CF card that will give me enough speed to test this all out for myself, but I was wondering if anyone could shed some light on shooting 4:3
Is it possible on the MkII? What are the resolutions you can do it at and how many frames will you get?
On my mkII with a 64gb KomputerBay card, I can shoot 1472x1104 continuous/spanning to presumably fill up a whole card. I can also shoot 1600x1200 for shorter bursts (about 360 frames / 15 seconds).
Great for anamorphic, obviously!
Great...wanna see anamorphic raw footage soon.
Oedipax wich hack release have you installed to obtain 1472x1104 continuous recording.
It is a new resolution option? If yes, wich release have it?
Thanx!
Quote from: morflexxx on June 18, 2013, 06:41:02 PM
Great...wanna see anamorphic raw footage soon.
Oedipax wich hack release have you installed to obtain 1472x1104 continuous recording.
It is a new resolution option? If yes, wich release have it?
Thanx!
For last couple of builds jun 14, 16 and maybe earlier this was already available. But to be safe use the current one jun 18 NB.
Hey,
great work so far!
Is there a way to get files larger >4GB working?
raw2dng always comes up with:
[image2pipe @ 0x102019600] Could not find codec parameters for stream 0 (Video: ppm): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
pipe:0: could not find codec parameters
Done
What do you think?
@ted
Did you get pink frames on 5x with the build a43e030494e4?
Update
@sebble
You could try the new version.
Quote from: olik on May 21, 2013, 06:50:50 PM
Has anyone tried with the new build to import the DNGs with davinci resolve?
Nope... but click and drag to raw2dng doesn't seem to work anymore =(
http://www.magiclantern.fm/forum/index.php?topic=6218.0
Quote from: a.d. on June 18, 2013, 09:33:50 PM
http://www.magiclantern.fm/forum/index.php?topic=6218.0
i have a mkii and a pc
http://www.magiclantern.fm/forum/index.php?topic=5618.0
Update : Download Homepage
http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/
Quote from: a.d. on June 18, 2013, 09:10:01 PM
@ted
Did you get pink frames on 5x with the build a43e030494e4?
5x crop mode
2152x1078 = ok
2048x1078 = ok
1920x1078 = ok
1920x1038 = ok
1920 x 960 = ok
1880x1058 = ok
1880 x 940 = PINK IMAGE
1880 X 854 = ok
1728 x 972 = PINK IMAGE
First post so please flame appropriately as needed. I thought I'd try using a motion control rig for camera trigger for multipass VFX (both time-lapse and realtime )and wanted to see how close the still raw images and the raw video files would be in case they could be matched in AE or Nuke. For the most part it works but I was curious about two things that I thought might be relevant to the forum. The very center of the camera raw still and MLRaw image are a few pixels off. I'm not doing the RAW zoom function but do you think this is related to the issue with the zoom offset? Otherwise, they should both roughly have the same center pixel. Right?
Also, there is a very slight (but acceptable) color shift. Would this be related to the raw2dn conversion or something in camera? Maybe I should post that to the Raw workflow but thought I'd check here in case there might be an in-camera reason for the image to be different.
Thanks!
https://www.dropbox.com/s/6lokqvakvfhleug/test.jpg
Quote from: a.d. on June 18, 2013, 09:37:24 PM
http://www.magiclantern.fm/forum/index.php?topic=5618.0
Update : Download Homepage
http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/
dont work
Quote from: ted ramasola on June 18, 2013, 11:54:10 PM
5x crop mode
2152x1078 = ok
2048x1078 = ok
1920x1078 = ok
1920x1038 = ok
1920 x 960 = ok
1880x1058 = ok
1880 x 940 = PINK IMAGE
1880 X 854 = ok
1728 x 972 = PINK IMAGE
tested other resolutions in crop mode. NB a43e030494e4
1880 x 940, and 1728 x 972
PINKISH IMAGEFraming in the crop modes are now much better if ML grayscale is used.
Can you post the first few frames of a recording with pink image?
(I don't think it has anything to do with resolution)
It might be a stupid question, but have anybody find a way to have a remain space indicator while recording RAW? Because it happens twice that a recording suddenly stops because of the lack of space. For now I can only check the this when I'm not recording...
Again, there's no easy way to do it from code; just restart the camera when you want to check the space.
I got too menu and format and not press anything to check what space is left, and when i sometimes come out it shows space left.
For the last time, restart the camera before checking free space. I can't fix that.
hi there.
Ive been looking through the forum for an answer but cant find anything
Im trying to get raw on my 5dm2. I have installed the latest ML 2.3 and everything is running fine. Myt problem is that there is no Module folder contained with the ML directory.
I have also downloaded the new raw rec zip, all the forums say to copy the new files into the module folder of the ML directory how can this be done when it doesnt exist.
I have tried to put the module folder from the zip file onto the cf card and replace the auto.exe file with the new one from the zip file, this made my camera freeze and not boot.
any help would be appreciated.
Love ML by the way!!
Quote from: a1ex on June 19, 2013, 08:46:09 AM
Can you post the first few frames of a recording with pink image?
(I don't think it has anything to do with resolution)
(https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-prn1/1014629_335315349932589_124149581_o.jpg)
(https://fbcdn-sphotos-g-a.akamaihd.net/hphotos-ak-prn1/1025424_335315359932588_176319317_o.jpg)
Is the very first recorded frame pink?
Quote from: a1ex on June 19, 2013, 04:50:36 PM
Is the very first recorded frame pink?
yes, and the same up to the last for both clips.
How long were the clips?
The problem is that I can't reproduce this issue; I've recorded yesterday for half an hour in crop mode, with various settings, and couldn't get any pink frame.
Quote from: a1ex on June 19, 2013, 05:16:06 PM
How long were the clips?
The problem is that I can't reproduce this issue; I've recorded yesterday for half an hour in crop mode, with various settings, and couldn't get any pink frame.
1728 x 972 is 570 frames long. ---This shot was 1st take under crop mode after shots in normal mode of same resolution.
1880 x 940 is 2,973 frames long---This shot was taken after another resolution also in crop mode.
I did get pick frame on x5 with 2013/06/16 b93d6ae2b30d but I reverted to the build before it, now I have the latest build from the 6/16 and that solve the pink issue but now has gray frame while recording but I'm sure you guy have the answers. I do want to ask, what is the most Raw resolution from the 5D Mark II in 2.35.1-2.20.1-1.85.1-16:9 , I took your advise and I now have a Lexar 32 1000x?
Also, here's the correct link for raw2dng for OSX: http://bitbucket.org/a_d_/magic-lantern/downloads/5D2_OSX_raw2dng_ProRes.zip (http://bitbucket.org/a_d_/magic-lantern/downloads/5D2_OSX_raw2dng_ProRes.zip)
Thanks so much for the work, this is sweet! I'm testing the version from an hour ago in hopes to fix my issues. I have a Komputerbay 64gb 1000x card that can do 1880x880 continuous and fill up the card. The problem is that all the footage ends up garbled. Even if i turn off raw and try a normal 1920x1080x24 the video is jacked up. I'll report back with the latest build.
i got same problems as TED... pink everything in 1880x940 wich is the resolution i rely most. To be honest im on build 10/06 cause i can record almost 4gb files which is enough to me, and i have color image when filming 5x. To me its very useful.. i think the green dots or something when we have color recording could be something related to shutter actuations ? I mean the older the camera more suitable to get those dots it will be ??? Because i never got dots or dead pixels... my camera have 30k actuations and works fine. Also with th enew build i see less MB/s on recording giving me a little bit less frames. So it could be the simples the better! Amazing job guys thanks!
1856x844
2:20:1
Center
ML GRAYSCALE
First shot normal
second shot pink frames
Update:
Just done 4 shots
1. pink
2. pink
3. normal
4. pink
@noix222
I use my hack since 2 weeks and it works ;=)
I just noticed that reducing the frame rate with FPS override also increases the card's write speed slightly. So not only does it reduce the inherent write speed requirements versus the standard 24/23.976, it also increases card performance, which may make the difference between being able to record at a certain resolution or not. Anyone been naughty enough to record at lower rates and interpolate the frames in post? ;D
At 24 FPS, my 600x Sandisk card normally writes at around 63-64 MB/s out of the required ~80, so the buffer fills up quickly. Lowering it to 19 FPS reduces the speed requirement to 63 MB/s and also increases my write speeds to 66 MB/s. 20 FPS is just beyond the point of intersection for continuous shooting though; write requirement jumps to 66 MB/s and write speed drops to about 65 MB/s . Though I don't think we'll get much beyond 21-22 FPS with a faster card, it's nice to see that one can squeeze out a little more performance than expected from the raw resolution/fps calculations.
Hi,
using ML Raw Version a43e030494e4 on 5dmk2, CF 16GB, 30MB/s still I only have the
1880x800 aspect ratio to choose.
Where and how to get all the different aspect ratios and also fps ?!
Thanks for help.
The FPS is not part of the raw shooting module but should be located in the same movie page, it is called FPS override. To get the resolutions larger than 1880 you have to be in 5X or 10X crop mode, you need to press the button to zoom into the live view(usually used for checking focus) so that it is not zoomed all the way out. That will unlock the larger resolutions.
Thanks, do I understand right: The different aspect ratios provided is not linked to the speed and/or size of the cf card in any way, right?
Quote from: Yoshiyuki Blade on June 19, 2013, 10:23:38 PM
I just noticed that reducing the frame rate with FPS override also increases the card's write speed slightly.
Yepp, same thing here.
I usually got around 57-58Mb/s @24FPS and decreasing FPS gives me up to 60 (16FPS) - 61Mb/s (6-9FPS).
Twixtoring result very much depends on the nature of the filmed subject.
In the more or less static scenes (nature) it is possible to twixtor from 12fps.
My street tests (moving cars, people, etc) shown me that FPS should be at least 18, with further twixtoring to 75% speed.
But even in that case you should avoid fast moving large subjects close to the camera.
About the write speed.
I've found in the 550D thread A1ex posts about buffer optimisation and how different buffering strategies affect card write speed.
From here:
http://www.magiclantern.fm/forum/index.php?topic=5582.msg52455#msg52455
Question, is there some sort of connection betweeen FPS override and different buffering?
Thanks for all the work you guys do, I want to get a clear understanding on the best possible resolution and what keeps the 5D Mark II From utilizing the full Sensor functions? I know the full framing of the Canon 5D Mark II is 3:2, so can you explain why the camera gets RAW 1880 instead of 1920? ???
Quote from: dariSSight#1 on June 20, 2013, 12:56:29 AM
Thanks for all the work you guys do, I want to get a clear understanding on the best possible resolution and what keeps the 5D Mark II From utilizing the full Sensor functions? I know the full framing of the Canon 5D Mark II is 3:2, so can you explain why the camera gets RAW 1880 instead of 1920? ???
Here:
http://www.magiclantern.fm/forum/index.php?topic=6215.50
You may push larger resolution (2144x1078) utilizing 5x crop mode.
As it was mentioned here before, Canon's original 1920x1080 H.264 is upscaled from 1880.
Doesn't seem like a big deal to me, it's only 40 pixels. Nothing compared to RAW sharpness and detail even at the lower resolutions.
Quote from: Yoshiyuki Blade on June 19, 2013, 10:23:38 PM
Anyone been naughty enough to record at lower rates and interpolate the frames in post? ;D
Yes, I am naughty.
I record 1880X1058, 17 fps with my old 60 MB/s SanDisk.
Developed in Photoshop
Converted in Apple Compressor into 25 fps.
But I can not record audio or I do someting wrong?
hinrich
@A1ex
I was able to trigger pink frames in 5x crop mode in another scenario, while using FPS over ride.
Testing highest resolution on 5d2 at 2152 x 1078 with FPS over ride.
I did 4 takes.
take 1 at 5P --all frames pink
take 2 at 1P --1st frame OK the rest Pink
take 3 at 1P --1st frame OK the rest Pink
take 4 at 3P --all frames Pink
1 test at 1880 x 1250 at 1P -- all frames OK.
Hope this helps you do the troubleshooting.
Quote from: hini on June 20, 2013, 03:23:55 AM
Yes, I am naughty.
I record 1880X1058, 17 fps with my old 60 MB/s SanDisk.
Developed in Photoshop
Converted in Apple Compressor into 25 fps.
But I can not record audio or I do someting wrong?
hinrich
When shooting RAW you need to enable sync beep if recording sound from separate device, or choose WAV to record sound, iv read some people cant record more than 3seconds so give it a try, also as your shooting in 17fps check this out, it may help you if you want smooth video, its not a tutorial but shows it can be done :)
Quote from: Doyle4 on June 20, 2013, 02:23:52 PM
check this out, it may help you if you want smooth video
Yes, Twixtor can make miracles come true. But the result depends very much of the scene you are filming. Foreground, Background. It works best if the background is smooth. If not it is difficult. Thank you for the beep trick. Every night we become more and more professional.
What has been added/tweaked in 19th July build please, cant see the changes from 18th for some reason..
Cheers :D
Sorry for another post..
Am i doing something wrong here... When i choose ML Greyscale the white box vanish's in LV so I'm not sure whats going to be captured, sorry again :)
On the newest build, or what was newest about a week ago I guess, I managed to record 1880 x 800, until the card stopped (about 2.5 minutes) with a SanDisk 60 MB/s card. Has anyone else had these results? If so it seems like the newer builds are really getting amazing.
with the 19/06 build i get PINK IMAGES when shooting 1880x950 on 5x crop... also it gets black and white! To me i still prefer a color viewer..... thanks guys! i stick with build 10/06 still!!!
@A1ex
Testing Jun 19 build posted by A.d. 7eee493f6fc9
1 x modes ok
3x crop mode (5x magnify)
2152 x 1078 ---Pink image
1920 x 1078 ---Slightly warm/yellowish tint but blacks can be recovered.
1880 x 1058 ---Pink image
1728 x 972 --- @ 23.976 --- OK
--- @ 1FPS --- Pink image
--- @ 5 FPS --- Pinkish
This is amazing work! Question. When recording at 1880 and wav, the wav stops recording after a while. It says I need a faster card. Shooting on komputerbay 64gb 1000x. Not that huge of an issue since I only need a few seconds before syncing with external, but still wondering if this is a known constraint. Also, I was reading back in the forum because I got the green dot issue as well. Anyone know if there's a fix for this? Thanks!
Since sound recording is such a problem:
how about making it record a predefined number of seconds of WAV Audio only,
to not make the recording stop, but still have something for automatic syncing of audio like pluraleyes to work with...?
Who do I have to contact for this idea?
Quote from: a.d. on June 14, 2013, 09:01:46 PM
@durisy
I've just updated raw2dng. There's a new algorithm for hot pixel fixed based on chdk
Thank you.
hot pixels were gone.
But with the latest raw2dng, one pink hot pixel is back again.
h.264. no hot pixel.
@fatpig: Why don't you just use the sync beep to sync your audio? Even if the 5dm2 records only a few seconds of audio, it will cost you recording time. I would use internal audio recording only if it's not possible to record externally. If you're already recording with an external recorder, internal audio recording is just a waste of buffer space imo.
well, a sync beep still requires all the syncing work to be done, and the beep is not on the first frame but somewhere around the first second, which makes is almost useless.
The point in a WAV file, if only some seconds, is: use pluraleyes and not having to sync at all.
I will happily sacrifice some of my buffer time for it, as it records continuous with one or no stars anyway. :)
21st July Build VERY nice indeed! Thank you for the hard work and quick releases! nice to have x10 back!!
Digital Dolly is genius! wasn't sure what it was till now.... sweet!
Thanks ML Team :)
UPDATE: x10 still does not work... output video created is like someone is shaking the hell out of the camera ha, also the last frame when using dolly mode is all pink and pixely looking. :)
Today's build 6-21, runs beautifully. btw, how do I access the digital dolly feature?
Build is great but I'd also love to see an option for sound back. I understand that it causes issues with the buffer but as fatpig suggested, perhaps a few seconds? With the 5DmkII the audio in previous builds seemed to match up very easily with the start of the clip, making syncing external audio MUCH easier. I'm trying to think of this in terms of shooting a low-budget film, and audio syncing would be a constant.
if you use the beep feature for sync. I've done some tests with it syncing dialog and here's some info to help.
Set the camera speaker volume to 5 or highest so the beep is audible to the sound recorder.
In a 24P framerate the beep's peak is consistently of the 5th frame of video recording. There might be a slight fade in slope on the 4th frame but otherwise the peak begins on the 5th.
I figured out the green dot issue. In case it wasn't mentioned anywhere else, the green dot was because I was watching the mov file created out of raw2dng. When i opened up the dng files and followed the longer workflow (raw2dng->PS->QT7), the dot wasn't there. I'll post this on the raw thread as well. Thanks!
For those wanting to synch the sound and are having issues with the synch beep, why not just use a movie clapper. Just get one or make your own. Even clapping your hands in front of the camera would work.
Quote from: ted ramasola on June 21, 2013, 04:46:33 PM
if you use the beep feature for sync. I've done some tests with it syncing dialog and here's some info to help.
Set the camera speaker volume to 5 or highest so the beep is audible to the sound recorder.
In a 24P framerate the beep's peak is consistently of the 5th frame of video recording. There might be a slight fade in slope on the 4th frame but otherwise the peak begins on the 5th.
Thanks. Trilled to test the new build.
Quote from: disjecta on June 21, 2013, 03:53:58 PM
Today's build 6-21, runs beautifully. btw, how do I access the digital dolly feature?
Where you choose RAW video theres now Dolly Digital just underneath resolutions.. turn it on, use ur control stick to move in the direction you want :)
@a.d
you hack is amazing!!!! the new build is pretty good too. My only request would be not having GREYSCALE in 5x crop ... We can have the image with color when recording in 5x crop ??
thankssss
edit: im also testing frame rates.. and i usually record in 1x and 5x with both fps override ON to get smooth 24fps. But in 1x when i turn fps ON the frame rate comes out 29.997 pretty weird .... AND STILL GETTING PINK IMAGES RECORDING 5x 2.1.
https://dl.dropboxusercontent.com/u/36670435/000000.dng (https://dl.dropboxusercontent.com/u/36670435/000000.dng)
The new buffer graphic is really beautiful.
@fatpig
the 5s WAV is an interesting idea. You could post it in the features request.
@Doyle4
5x and 10x are identical. We record actually 3x crop.
@Indianac
Just to be clear about chdk. It's a DNG badpixel optcode for ACR. That means the converter for ProRes doesn't read the optcode!
Do you have a fast internet connection? If yes, I need only a second of a hotpixel.RAW to test.
Update: 2 DNGs are enough.
@Mati
Does your girl friend know, she is a zombie? ;)
@noix222
The workaround from a1ex is the best option for us now, because It takes into account such a problem http://www.magiclantern.fm/forum/index.php?topic=6426.0
:) :)
this is a documentary i'm working on with Raw, try to shoot as much as i can.
with the June 6th built, i was reluctant to try past built until now , i hear its very good now.
Been working in After Effect, apply a color profile "Panalog" or "Panavision Genesis Tungsten Log"
No other Correction was done
;D
I like the natural look and the film is in synch.
Quote from: a.d. on June 21, 2013, 10:52:03 PM
I like the natural look and the film is in synch.
Thanks, :)
Recorded with frame override on 24p
recorded audio with wireless sennheiser Ek 100 G3 to Zoom@96/24
Edit with Final Cut Pro x , FCPx has very good Audio Tools
Quote from: reddeercity on June 21, 2013, 11:07:59 PM
Thanks, :)
Recorded with frame override on 24p
recorded audio with wireless sennheiser Ek 100 G3 to Zoom@96/24
Edit with Final Cut Pro x , FCPx has very good Audio Tools
Nice colors but in my computer I think audio track is ahead by 1 or 2 frames.
Quote from: ted ramasola on June 21, 2013, 11:13:34 PM
Nice colors but in my computer I think audio track is ahead by 1 or 2 frames.
Thanks, Ted you are right, i didn't notice it until now
Good thing it my first Daft ::)
I was in a big hurry to post i didn't check it closely
Awesome improvement ;) thanks to all magic lantern team. Is it possible to have Focus Peaking during recording in raw ???
Great, great, really great work guys!
If someone could summarize the list of improvements of the last release about:
max res in continuos mode
max res in crop mode
max res in 4:3 mode (for anamorphic footage)
...and the others goals achieved by "dream Magic Lantern team"on raw recording...would be very appreciated!
Thanx!
Quote from: morflexxx on June 22, 2013, 11:48:20 AM
Great, great, really great work guys!
If someone could summarize the list of improvements of the last release about:
max res in continuos mode
max res in crop mode
max res in 4:3 mode (for anamorphic footage)
...and the others goals achieved by "dream Magic Lantern team"on raw recording...would be very appreciated!
Thanx!
I mean no disrespect but couldn't you just as well read the thread?
Using a Komputerbay 64GB & A1ex's new module on the 5d2:
Max continuous
4:3 = 1472 x 1104
3:2 = 1472 x 982
16:9 = 1600 x 900
1.85:1 = 1728 x 934
2:1 = 1728 x 864
2.20:1 = 1872 x 850
2.35:1 1872 x 796
2:39:1 1872 x 784
Quote from: Redrocks on June 22, 2013, 12:54:55 PM
Using a Komputerbay 64GB & A1ex's new module on the 5d2:
Max continuous
4:3 = 1472 x 1104
3:2 = 1472 x 982
16:9 = 1600 x 900
1.85:1 = 1728 x 934
2:1 = 1728 x 864
2.20:1 = 1872 x 850
2.35:1 1872 x 796
2:39:1 1872 x 784
Using a Laxar 1000x 32GB & 2013/06/21 0c3188c5134f Build on the 5d2, Ratio 4:3, 3:2, 16:9, 1.85:1 and 2:1 of Redrocks reading are the same but the 2.20:1, 2.35:1 and 2.39:1 are different on my readings:
2.20:1=1880x854
2.35:1=1880x800
2.39:1=1880x786
I see that a Jun 22 build has been released, does it have an improvement on the variable buffering or has variable buffering been totally taking out?
I just installed a.d's latest build (cf56893d7be4) and it appears to have variable buffering. Also he has removed his 1880 hack to bring his resolutions inline with A1ex's builds.
Hello to all. Does someone could explain to me why I can not install the latest versions of "Builds". I got stuck on the 14th June. From there, when I substitute for newer modules they dont load, (file_man error, raw_rec error, xml_cfg error). Thank you.
delete ML and start fresh. it should work.
Quote from: Redrocks on June 22, 2013, 02:38:05 PM
I just installed a.d's latest build (cf56893d7be4) and it appears to have variable buffering. Also he has removed his 1880 hack to bring his resolutions inline with A1ex's builds.
Hope your have a Cinematic day Redrocks and Magic Lantern Community,
I put the June 22 a.d's latest build (cf56893d7be4) in and it took my measure back to 1872 instead of 1880 what going on? So to keep thing somewhat accurate I put the 2013/06/21 0c3188c5134f Build back in at least the measurements right. What's the changes from 2013/06/21 0c3188c5134f Build and a.d's latest build (cf56893d7be4)?
Quote from: dariSSight#1 on June 22, 2013, 02:22:36 PM
Using a Laxar 1000x 32GB & 2013/06/21 0c3188c5134f Build on the 5d2, Ratio 4:3, 3:2, 16:9, 1.85:1 and 2:1 of Redrocks reading are the same but the 2.20:1, 2.35:1 and 2.39:1 are different on my readings:
2.20:1=1880x854
2.35:1=1880x800
2.39:1=1880x786
@ Redrocks & dariSSight#1
THANX!
This kind of summary-update-info about progress of improvements of the latest release are really useful to all ML users (instead to search and dig into 20+ pages of the thread with old infos).
From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?
Thanx again
cf56893d7be4, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:
1250 / just over 3:2 =
187
226
202
224
219
1054 / 16:9 =
575
510
511
561
543
1012 / 1.85:1 =
783
875
803
937
919
936 / 2:1 = one take only 7572 I'd say this ratio is good for 5 mins
850 / 2.20:1 = continuous
796 / 2.35:1 = continuous
Quote from: dariSSight#1 on June 22, 2013, 03:04:43 PM
Hope your have a Cinematic day Redrocks and Magic Lantern Community,
I put the June 22 a.d's latest build (cf56893d7be4) in and it took my measure back to 1872 instead of 1880 what going on? So to keep thing somewhat accurate I put the 2013/06/21 0c3188c5134f Build back in at least the measurements right. What's the changes from 2013/06/21 0c3188c5134f Build and a.d's latest build (cf56893d7be4)?
You too, dariSSight. A1ex has this to say about 1880 vs 1872:
"the builds from a.d. contain a number of extra changes, e.g. allows non-mod16 resolutions (which I prefer to stay away from, for DMA alignment reasons)"
"Bigger is not always better, mod16 resolutions are more important IMO, and the EDMAC is very sensitive to alignment."
Which is over my head, but I realised that 1872 is an exact 1/3 rd of the sensor and probably an easier number to work with.
From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?
Thanx again
______________
I intend to get one in the next week or so, but it's certainly acceptable without one.
Quote from: Redrocks on June 22, 2013, 03:29:44 PM
You too, dariSSight. A1ex has this to say about 1880 vs 1872:
"the builds from a.d. contain a number of extra changes, e.g. allows non-mod16 resolutions (which I prefer to stay away from, for DMA alignment reasons)"
"Bigger is not always better, mod16 resolutions are more important IMO, and the EDMAC is very sensitive to alignment."
Which is over my head, but I realised that 1872 is an exact 1/3 rd of the sensor and probably an easier number to work with.
I'm a little stomp but does that mean its an exact RAW video conversion from the sensor measurement, I think it's because Canon non-compromise for low-level access to the sensor that Magic Lantern cannot push the 1880 up.
Does lowering it to 1872 RAW measurements takes from conversions like 1080p?
Forgive my ignorance but I believe asking make you a little least ignorant.
Quote from: Redrocks on June 22, 2013, 03:36:54 PM
From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?
Thanx again
______________
I intend to get one in the next week or so, but it's certainly acceptable without one.
I will puchase a VAF filter soon because it seems to be something you might not want to be without, I do believe its always better to watch your ISO for Color Alasing and Moire and watch for pattern in your shots. What's the option for VAF filters I've only heard of the Mosaic VAF Filter?
As far as I know it is to do with line skipping which involves discarding 2/3rds of the data. In crop mode you have a true cutout of the sensor with no line skipping, but also a crop factor of 5.
EDIT:
http://www.magiclantern.fm/forum/index.php?topic=6242.0
more info here.
Current ad vs A1ex, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:
ad 1248 / 3:2 =
217
223
217
226
218
A1ex 1248 / 3:2 =
222
228
223
229
216
ad 1054 / 16:9 =
587
561
586
553
579
A1ex 1054 / 16:9 =
558
564
598
553
541
ad 1012 / 1.85:1 =
833
888
950
893
933
A1ex 1012 / 1.85:1 =
835
963
861
921
871
ad 936 / 2:1
4992
A1ex 936 / 2:1
3954
Yes it's better to do everything you can before relying on a filter, I haven't heard of any similar products to the Mosaic line.
Current ad vs A1ex, Sandisk Ultra 8GB, GD off, exact 24 fps, resolution 1872:
ad 1248 / 3:2 =
86
87
87
83
85
A1ex 1248 / 3:2 =
85
86
84
86
85
ad 1054 / 16:9 =
108
109
109
109
109
A1ex 1054 / 16:9 =
108
104
108
106
104
ad 1012 / 1.85:1 =
124
125
123
124
124
A1ex 1012 / 1.85:1 =
124
124
124
125
124
ad 936 / 2:1
132
128
133
131
117
A1ex 936 / 2:1
131
132
132
125
131
Quote from: Redrocks on June 22, 2013, 04:39:19 PM
Current ad vs A1ex, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:
ad 1248 / 3:2 =
217
223
217
226
218
A1ex 1248 / 3:2 =
222
228
223
229
216
ad 1054 / 16:9 =
587
561
586
553
579
A1ex 1054 / 16:9 =
558
564
598
553
541
ad 1012 / 1.85:1 =
833
888
950
893
933
A1ex 1012 / 1.85:1 =
835
963
861
921
871
ad 936 / 2:1
4992
A1ex 936 / 2:1
3954
Yes it's better to do everything you can before relying on a filter, I haven't heard of any similar products to the Mosaic line.
I seen that forum thread before but I don't think I soak it in. Reddeercity Post is very vital for the point of Aliasing and Moire fear, I took a closer look at his video after reading the thread and you can see he was correct Aliasing can be seen in the small low Res window but if you open it to full screen and even more pick the 1080p or Original format option it clears up greatly for presentation (beautiful), that's scratching the surface of filming in RAW and Upscaling. Thanks again for the revisit to the thread because it help drill the option of line skipping, Moire and Aliasing problem solving into my head.
The cf56893d7be4 build locks really great! Sorry to say, it crashes with an external monitor.
Quote from: dariSSight#1 on June 22, 2013, 03:56:14 PM
I'm a little stomp but does that mean its an exact RAW video conversion from the sensor measurement, I think it's because Canon non-compromise for low-level access to the sensor that Magic Lantern cannot push the 1880 up.
Does lowering it to 1872 RAW measurements takes from conversions like 1080p?
Forgive my ignorance but I believe asking make you a little least ignorant.
When a1ex says 1872 is a mod16 resolution, it means that 1872 is evenly-divisible by 16 (1872 / 16 = 117). In terms of upscaling 1872 x 1053 vs 1880 x 1057.5 to 1920x1080, you could say you see a difference, but you'd probably be lying or fooling yourself. It's dropping a total of 0.85% of the resolution for much better performance.
Quote from: eatstoomuchjam on June 22, 2013, 10:19:51 PM
When a1ex says 1872 is a mod16 resolution, it means that 1872 is evenly-divisible by 16 (1872 / 16 = 117). In terms of upscaling 1872 x 1053 vs 1880 x 1057.5 to 1920x1080, you could say you see a difference, but you'd probably be lying or fooling yourself. It's dropping a total of 0.85% of the resolution for much better performance.
So Redrocks and EatTooMuchJam, I should reinstall the latest build?
Everything nice again on latest build! Managed to solve the X5 and X10 how too shoot, took awhile as only just found the page to set up the framing box and things! all good stuff :)
One thing i have noticed on this build is the text at the bottom that lets you know if you can record continuous (green) and yellow if it needs to buffer, it'll go green when i first setup but after shooting a raw video for say even a few seconds the text goes yellow, even after rebooting?
Once again, great work :)
UPDATE: All showing yellow now, checked through all settings and all are fine, checked CF read and write speed and no change.
Quote from: dariSSight#1 on June 22, 2013, 10:36:56 PM
So Redrocks and EatTooMuchJam, I should reinstall the latest build?
I have no opinion on what you should or shouldn't install. :)
With that said, development is moving fast. It's usually worth staying up-to-date.
"When a1ex says 1872 is a mod16 resolution..."
Thanks for the explanation. I agree there is no noticeable difference and if it lends itself to performance, I'm sold.
Unless you have a specific reason, always be running the latest builds dariSSight. Even though RAW is pretty stable, it's far from ready for general release and the developers need to hear from people who encounter bugs.
Quote from: Doyle4 on June 23, 2013, 01:55:26 AM
Managed to solve the X5 and X10 how too shoot, took awhile as only just found the page to set up the framing box and things! all good stuff :)
I keep having pink images in crop mode with the lastest build (june 22nd); what settings did you use to get rid of that?
Any particular reslution or else?
Thanks for your help!
hi - just wanted to say: GREAT JOB GUYS!! keep up your good work ...
d.
Quote from: neopixel on June 23, 2013, 10:03:32 AM
I keep having pink images in crop mode with the lastest build (june 22nd); what settings did you use to get rid of that?
Any particular reslution or else?
Thanks for your help!
Is this when you are Auto focusing? If so.. thats normal :)
Quote from: Redrocks on June 23, 2013, 08:22:01 AM
"When a1ex says 1872 is a mod16 resolution..."
Thanks for the explanation. I agree there is no noticeable difference and if it lends itself to performance, I'm sold.
Unless you have a specific reason, always be running the latest builds dariSSight. Even though RAW is pretty stable, it's far from ready for general release and the developers need to hear from people who encounter bugs.
Thanks All for the feedback and I'm running the latest build, You had me at Mod16 Resolution.
Quote from: Doyle4 on June 23, 2013, 11:51:07 AM
Is this when you are Auto focusing? If so.. thats normal :)
Actually no! I only use the AF in photo mode... Are your dng files alright with the latest build?
thanks again!
Quote from: neopixel on June 23, 2013, 01:24:43 PM
Actually no! I only use the AF in photo mode... Are your dng files alright with the latest build?
thanks again!
When shooting RAW video are making sure ur LV is movie mode?
my DNG's seem to be fine mate.
Quote from: Doyle4 on June 23, 2013, 03:07:54 PM
When shooting RAW video are making sure ur LV is movie mode?
my DNG's seem to be fine mate.
Yep! LV is movie mode!
But now I'd noticed something very stange:I own a 24-105mm; in crop mode (x5):
when shooting at 24mm: image is perfect
when shooting at 105mm: pink image
Fps overide is set on 24fps exact...
I didn't had this problem with the previous build that I used (14th june)
UPDATE: just to be specific it's working perfectly with resolution 1920 but not higher (used to work just fine before)
UPDATE 2: pink image with aspect ratio at 2:1 in crop mode; perfect image at 2:35
I think it´s absolutely random.
Just made 12 movies in crop mode (tested 1920x960 (first 7) and 1920x818 (rest)):
- good
- pink
- pink
- pink
- good
- pink
- pink
- pink
- good
- good
- pink
- pink
Quote from: neopixel on June 23, 2013, 11:14:36 PM
Yep! LV is movie mode!
But now I'd noticed something very stange:I own a 24-105mm; in crop mode (x5):
when shooting at 24mm: image is perfect
when shooting at 105mm: pink image
Fps overide is set on 24fps exact...
I didn't had this problem with the previous build that I used (14th june)
UPDATE: just to be specific it's working perfectly with resolution 1920 but not higher (used to work just fine before)
UPDATE 2: pink image with aspect ratio at 2:1 in crop mode; perfect image at 2:35
Make sure u are using latest RAW2DNG also
Quote from: Doyle4 on June 24, 2013, 01:24:37 AM
Make sure u are using latest RAW2DNG also
Yes! I actually am! I think like moet_chandon, it looks completely ramdom....
Hello All :)
Just testing out the New Build From June 21.
I had the June 4th built until now,
I see a big boost in speed for slower Card,
Test out my Scandisk 600x 90MB/s 32 GB
the best i could do before was 1720x864 & 1880x752.
Now i get 1880x800 24p @ 57.3-60.1 MB/s Continuous Recording :D
On my Lexar 1000x 32 GB , with the June 22 Built
1856x928 24p @ 68.7-69.1MB/s with frame over ride on
Crop mode : 2048x856 24p Continuous Recording
Before non crop mode was 1880x854 24p, Crop 2048x820 24p
I didn't see any benefit to use the 22nd built on the Scandisk,
But Gain a little more Frame size with the Lexar
:)
new build is killing it ! smooth RAW. thankS
Quote from: reddeercity on June 24, 2013, 05:57:37 AM
Hello All :)
Just testing out the New Build From June 21.
I had the June 4th built until now,
I see a big boost in speed for slower Card,
Test out my Scandisk 600x 90MB/s 32 GB
the best i could do before was 1720x864 & 1880x752.
Now i get 1880x800 24p @ 57.3-60.1 MB/s Continuous Recording :D
On my Lexar 1000x 32 GB , with the June 22 Built
1856x928 24p @ 68.7-69.1MB/s with frame over ride on
Crop mode : 2048x856 24p Continuous Recording
Before non crop mode was 1880x854 24p, Crop 2048x820 24p
I didn't see any benefit to use the 22nd built on the Scandisk,
But Gain a little more Frame size with the Lexar
:)
I might have to go back to the June 21st build, it seems more stable I'm getting pink RAW footage. I don't know if its the .013 raw2dng.app or the June 22nd build it does sucks but we always have to keep in mind We Are On The Bleeding Edge.
22nd build seems fine to me, only thing iv noticed is the text stays yellow even though my card can capture continuos
UPDATE: 24th released gunna try this bad boy now :) Thanks a.d. :)
Since it was a supermoon weekend, here's a frame from raw video i shot.
Using 5D2 with nikkor 80-200mm f2.8 at 200mm + 2x teleconverter + MLraw 3x crop = a 1,200mm shot ? :)
(https://sphotos-a.xx.fbcdn.net/hphotos-prn1/1063883_531411320249271_1152279442_o.jpg)
Good Day Fellow Cinematic Revolutionists,
I see that you guys gave us an option to choose 1880 or 1872 resolution, the display of the resolution is very Cool also. My understanding of the option is that 1880 is the resolution Canon software coding allow from the sensor, the 1872 option is the exact 1/3 breakdown of the sensor ML coding and that allow for smoother file conversion without loosing quality from Canon's Sensor coding.
@ ted ramasola
https://vimeo.com/69038125
You and I had similar ideas!
5D2
180mm 2.8 Nikon
2x Converter Bower
Raw workflow
shot at 1728x 736 23.96 fps with 3x crop mode
12 GB file joined together (~4 minutes)
DNGs created with Rawanizer .5.5
dngs color graded in ACR
Resized with Red Giant's "Instant HD" in After Effects CS6
Rendered in Premiere CS6
@ted ramasola & duncanidaho25: Nice, I got a shot of the supermoon a couple days ago too! I just have a cheapo Canon 300mm lens though. Lots of atmospheric distortions were visible. I compared it to a shot I took a couple years ago of a regular full moon and it was indeed a little bigger!
edit: Btw, the moon was also a yellow/light orange in appearance at the time of the shot and it turns out that way in post when I use the same setup I have for regular daylight. What do you guys think about white balancing it to make it gray?
https://vimeo.com/68982034 Thought I'd share. First time out. Shots were really underexposed, having so much information to recover anyways was incredible. Anyone know why it came out more underexposed than I had seen in the LV? Jun 22 build.
Quote from: Yoshiyuki Blade on June 24, 2013, 11:18:54 PM
@ted ramasola & duncanidaho25: Nice, I got a shot of the supermoon a couple days ago too! I just have a cheapo Canon 300mm lens though. Lots of atmospheric distortions were visible. I compared it to a shot I took a couple years ago of a regular full moon and it was indeed a little bigger!
edit: Btw, the moon was also a yellow/light orange in appearance at the time of the shot and it turns out that way in post when I use the same setup I have for regular daylight. What do you guys think about white balancing it to make it gray?
Well, you have to turn the slider to the left = less temperature. But the surroundings will become more blue.
hello :)
Test the new June 24th built,
like the new option for frame size nice choice to have, i can use what works for me :D
Frame size overlay nice, from my point of view i think we are hitting the wall at 70.2MB/s
i have notice that if the recorded frames Start to write @ about 67 MB/s and Pecks at no more then 69.3 MB/s
This will maintain Continuous Recording. But if the write speed Starts to high (68.9MB/s) and perks @ 70.2 MB/s
It will not be stable in writing to card or you get Corrupted Frames.
variable buffing is the key to more Stable Frame sizes, & by Stable i mean "maintain Continuous Recording"
@ any given size.
With this built 1856x928 24p frame over ride on, @68.3-69.1 MB/s Continuous
Crop mode 1600x1076 24p @ 68.5-69.1 MB/s Continuous .Both with Hacked on & 1880 off
Lexar 1000x 32GB :)
I'm having a hell of a hard time finding a vendor to ship me a 1000x Komputerbay card to Iceland. What kind of success have you guys been getting with 2.35 cropped 1880p footage on slower cards, if any?
Quote from: krummi on June 25, 2013, 03:37:11 AM
I'm having a hell of a hard time finding a vendor to ship me a 1000x Komputerbay card to Iceland. What kind of success have you guys been getting with 2.35 cropped 1880p footage on slower cards, if any?
:) Will i just did a few tests on my slower CF cards as follows:
Scandisk 60MB/s 400x 32 GB = best 1728x736 24p @50.1MB/s (Continuous Recording)
Scandisk 90MB/s 600x 32 GB = best 1880x800 24p @58.9MB/s (Continuous Recording)
Both at 2:35
All with June 24th built, frame over ride on ;)
Performance gains with variable buffer and speculative start.
Using Lexar 1000x 32gb on 5d2. Each resolution was tested twice, results separated by ( / ).
Card is always formatted in camera before a new build is tested.
All tests done with: GD=off, preview=hacked, FPS over ride= 23.976
resolutions at 1x -- frames 1st take/2nd take
jun 19 by a.d.
1880 x 1058 -- 319/326
1880 x 1016 -- 532/425
1880 x 940 -- 779/988
1880 x 854 --continuous
alex variable buffer jun 21
1872 x 1054 -- 486/480
1872 x 1012 -- 755/732
1872 x 936 -- 2,391/2,272
1872 x 850 -- continuous
1856 x 1044 -- 521
1856 x 928 -- continuous
jun 22 by a.d. spec start off
1872 x 1054 -- 485/582
1872 x 1012 -- 932/876
1872 x 936 -- 4,085/3,626
1872 x 850 -- continuous
1856 x 1044 -- 644/563
1856 x 928 -- continuous
jun 22 by a.d. spec start ON
1872 x 1054 -- 504/531
1872 x 1012 -- 949/893
1872 x 936 -- 2,833/2,369
1872 x 850 -- continuous
1856 x 1044 -- 572/639
1856 x 928 -- continuous
jun 24 by a.d.
1872 x 1054 -- 572/506
1872 x 1012 -- 871/858
1872 x 936 -- 2,868/4,009
1872 x 850 -- continuous
1856 x 1044 -- 557/555
1856 x 928 -- continuous
CROP modes in the following builds;
jun 18-19-21-24 were all Unpredictable and always have pinkish cast in all frames.
I have the number of frames tabulated but since they're mostly pinkish I didn't bother posting.
last build with no pink cast in most resolutions was Jun 16 by a.d.
http://youtu.be/ieTRtKOSDmI
5D mark ii / 2013/06/22 Build
1872 x 936 / Komputerbay 128gb 1000x
:)
@ all with random pink frames in crop mode
https://bitbucket.org/a_d_/laboratory/wiki/Home
@ted and duncanidaho25
Beautiful shots of the Moon
@motionpikczer
I like it
@a.d.
in the link theres a download file, is this the 25th build please? or is it something else?
Cheers :)
UPDATE: yup... working nice :D
Quote from: a.d. on June 25, 2013, 10:37:15 AM
@ all with random pink frames in crop mode
https://bitbucket.org/a_d_/laboratory/wiki/Home
@ted and duncanidaho25
Beautiful shots of the Moon
@motionpikczer
I like it
Good Morning a.d,
Thanks for the new hack the pink frames were becoming a journey, I will install and test.
Quote from: dariSSight#1 on June 25, 2013, 11:33:15 AM
Good Morning a.d,
Thanks for the new hack the pink frames were becoming a journey, I will install and test.
It does say in the link btw if you suffer from pink frames to stay away from the build, im not sure if he means the new release or the 24th build, give it a shot :)
Quote from: Doyle4 on June 25, 2013, 11:39:58 AM
It does say in the link btw if you suffer from pink frames to stay away from the build, im not sure if he means the new release or the 24th build, give it a shot :)
I think a.d said if you had dead pixel in frames stay away from link, but the link is for a fix for pink frames.
I can't reproduce the pink frame issue at all.
Straight from my card: http://a1ex.magiclantern.fm/bleeding-edge/5D2/5d2-fac94f686d23-pink-debug.zip
Write down the black levels (they appear in the top area on the screen, when starting and when stopping recording) and post them, along with the result (whether the recorded frames were pink or not).
Quote from: dariSSight#1 on June 25, 2013, 12:28:11 PM
I think a.d said if you had dead pixel in frames stay away from link, but the link is for a fix for pink frames.
Ahhh right, sorry my miss understanding there, all working great btw :)
I can say i have no prink frames as of yet, but highest resolution i can record on atm is 1472x828 due my cards speed.
Quote from: a1ex on June 25, 2013, 12:33:59 PM
I can't reproduce the pink frame issue at all.
Straight from my card: http://a1ex.magiclantern.fm/bleeding-edge/5D2/5d2-fac94f686d23-pink-debug.zip
Write down the black levels (they appear in the top area on the screen, when starting and when stopping recording) and post them, along with the result (whether the recorded frames were pink or not).
Whats the difference between your fac94f686d23-pink-debug.zip ML A1lex and todays release? Im more than happy to try it or is this for pink frame suffer's again?
Cheers.
Mine is a vanilla build from the official repository (no third party code changes), with some debug info about black level.
I've tried to reproduce the pink issue with the latest build from a.d. and effectively got scared. Camera locked up, there were all sorts of overlays fighting and flickering, and there was a huge amount of options in the menu, to the point of being unusable.
I'm trying to stay away from infinite customizability and stick with something that works.
Ouch, Luckily i haven't had any lock up since 14th build, the build seems to be getting stronger, i would'nt let pink frames put anyone off if anyone else is reading this, to my understanding it seems a rare thing.
Ill stay away from your build for now then, as it sounds abit more complex than the one everyone can download,
be nice once everything is solved/tweaked etc and the big day comes for the major release, but for now im happy playing with new builds and finding things out for you guys...
If you were to recommend a build date A1ex which would it be? bit of a stupid question but i think people who are new here may feel that bit more safe about which Build to use, a lot has gone on since the finding of RAW and like you say, its constantly getting updated, or is it the question of download one and see if it work's?
Cheers,
Doyle
Did you actually read my post?
I trust my own code, and I've got scared when I've tried the one from a.d. Guess which one I recommend?
<--- Dyslexia guy here ill be honest and say i didn't read it clearly, re-read and understand what you put now. Sorry about that. i should proof read my own post too from now also, no wonder im confusing people :-\
Can i add the ETTR Module to your build A1ex?
UPDATE: yes you can, wasn't 100% sure if you could simply drop it into the modules folder.
Hey Guys, my first message on this forum, big thanks from the deep of my heart to ML, devs and community for making it real!!!
I'd like to partecipate with my modest feedback :)
I was playing around with 8262dacd390d.zip (2013-06-24 build) when I had a camera crash, here is the log:
ASSERT: 0
at Memory\Memory.c:561, task RscMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun24.5D2212
Mercurial changeset : 8262dacd390d+ (unified) tip
Built on 2013-06-24 13:19:11 by ad@MagicLantern.
Free Memory : 227K + 3863K
I switched it off and then on again and it was ok.
Also the resolution indicator was flickering as a1ex said, it was fighting with the audio indicator on the top left corner of the monitor.
I'm having a problem with raw2dng.exe... I'm still using a pc with Windows XP (forgive me :D) and when I drag and drop a raw file on raw2dng.exe the dng files are created in the following folder: C:\Documents and Settings\MyUserName\ instead of the same folder where raw and .exe files are located.
Thanks again to all, great job!
Just a simple upscaling test with the Photoshop Image Processor. DNG (1880x854) to TIFF (3072x1307). No Post-Sharpening etc.
It is not exactly RED-3K, but you can work with it.
Thanks to Reddeercity for providing the infos on the workflow :)
1880x854 32GB Transcend 1000x
06/13/2013 Build
Quote from: NewHourFilm on June 25, 2013, 04:17:52 PM
Just a simple upscaling test with the Photoshop Image Processor. DNG (1880x854) to TIFF (3072x1307). No Post-Sharpening etc.
It is not exactly RED-3K, but you can work with it.
Thanks to Reddeercity for providing the infos on the workflow :)
1880x854 32GB Transcend 1000x
06/13/2013 Build
NewHourFilm I've been looking at your video, how does the Tiff files hold up when you blow them up to test for pixel depth? Can you go into a little more about the RED-3K comparison, I'm always geeked to know opinions on how far my 5D Mark II can take me?
Quote from: a1ex on June 25, 2013, 12:33:59 PM
I can't reproduce the pink frame issue at all.
Straight from my card: http://a1ex.magiclantern.fm/bleeding-edge/5D2/5d2-fac94f686d23-pink-debug.zip
Write down the black levels (they appear in the top area on the screen, when starting and when stopping recording) and post them, along with the result (whether the recorded frames were pink or not).
I will test out the new .a.d new June 25 282abfa87fef build when I get home, but Alex where do you post you builds I have your pinkdebug build?
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem :)
Quote from: NewHourFilm on June 25, 2013, 08:46:08 PM
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem :)
WoW, For you to state the intercut possibility the 5D Mark II threat is real.
Quote from: NewHourFilm on June 25, 2013, 08:46:08 PM
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem :)
WoW, For you to state the intercut possibility the 5D Mark II threat is real.
Quote from: NewHourFilm on June 25, 2013, 08:46:08 PM
dariSSight#1 as far as i can tell, the Tiff file contains the full color information and original resolution. The DNG is transfered to Tiff with 16Bit color depth and so the full 14Bit should transfer in the process. No Banding etc. The PS Image Processor gives you the option to process the DNG to different sizes: 1880x854 (1,6MP) 2048x930 (1,9MP+) or 3072x1395 (4,3MP +) with 240 PPI the resulting 3K Tiff files really show much more detail in comparison to the original DNGs. I don't know if this resolution is just achieved through upscaling the 1880x854 or if the 3K data is backed in in the DNG files, but it really looks nice. It is a shame youtube just compresses everything to 2K in 8Bit 420.
When it comes to image quality and pure resolution and detail the Red cameras are the industy standard, but the images coming out of the 5D2 and 3 are nothing short of amazing. The Red cameras are designed to deliver the best possible image in the 2K+ range and there is a noticeable difference when you compare the upscaled 3K with an 3K R3d file, but it is not as dominant as one would think. I would say you can intercut footage and it would not be a major problem :)
Thanks guy for use my workflow :) to upscale.
Tiff can carry any embedded profiles that you can embed , or use Camera raw.
The Biggest think you must do is maintain the dpi, (240) Very important ! this is
where the image makes it or brakes it, I have been Working with PS & AE If you try to upscale in AE
it will look Bad, because AE dose not see the image as Photo image but as Frame image @ 72 dpi.
Plus i have play around with "Film Color Space" in Photoshop & After Effects.
i have been embedding the PanaLog "Panavision Genesis Tungsten Log"
in the Tiff image , i think that would be great for 2K or 4K "B" roll :D
Panavision Genesis Tungsten Log (Embedded LUT)or ICC for Photoshop
YouTube is the only ones that stream True 2K & 4K in the original Quality setting tab.
With the release of these newer memory cards, like the 1000x and the 1066x cards, will there be any sight of full hd in any of the nightlies, anytime in the near future? I for one, hope so, as, I've just ordered a 1066x car, today!
Quote from: sdesign on June 25, 2013, 11:04:21 PM
With the release of these newer memory cards, like the 1000x and the 1066x cards, will there be any sight of full hd in any of the nightlies, anytime in the near future? I for one, hope so, as, I've just ordered a 1066x car, today!
:) Can't be done 5d2 sensor will only do Max 1880 wide, and is limited integrally to about 70 MB/s
so with the new built the continuous recording that i get with lexar 1000x 32GB is 1856x928 24p @69.2 MB/s
we are fighting a battle against Hardware limitations :-[
perhaps then, mu question may be off topic, but then, how does a smaller sensor, like the 50d, get more latitude, as well as a higher bitrate?
Quote from: reddeercity on June 25, 2013, 10:36:15 PM
Thanks guy for use my workflow :) to upscale.
Tiff can carry any embedded profiles that you can embed , or use Camera raw.
The Biggest think you must do is maintain the dpi, (240) Very important ! this is
where the image makes it or brakes it, I have been Working with PS & AE If you try to upscale in AE
it will look Bad, because AE dose not see the image as Photo image but as Frame image @ 72 dpi.
Plus i have play around with "Film Color Space" in Photoshop & After Effects.
i have been embedding the PanaLog "Panavision Genesis Tungsten Log"
in the Tiff image , i think that would be great for 2K or 4K "B" roll :D
Panavision Genesis Tungsten Log (Embedded LUT)or ICC for Photoshop
YouTube is the only ones that stream True 2K & 4K in the original Quality setting tab.
Reddeercity thanks for getting the conversation started with the upscale possibility of Magic Lantern gift of RAW video, but to think of the 5D Mark II ML RAW firmware ability as only use for B-Roll kind of sucks. So let's begin with why not use Magic Lantern's gift of RAW as main film production stock? Why not use the the Rawness DNG to upscale at least to 2K, the reports of the Data from the DNG holds up? Why not use the Canon 5D Mark II for motion picture projects, I ask these questions keeping in mind that the fast race car scene in the beginning of Ironman 2 was shot with the Canon 5D Mark II with no fear of Rolling Shutters, the full 6th season finale of House was shot Exclusively with the 5D Mark II (it was a visually broad canvas presentation), the feature film ACT OF VALOR was shot exclusively with the 5D Mark II for 12 million dollars then grossing 81 million dollars and many more worthy Canon 5D Mark II professional projects. All those example of professional film work was accomplish with the Canon limitation firmware, now even if the limitation of Magic Lantern Firmware in RAW giving the Mark III 1920x1080 continuous RAW and the Mark II only shooting 1880x850 continuous RAW but Magic Lantern firmware setting option is very professional. Final question, Isn't the Magic Lantern 5D Mark II firmware settings and RAW capabilities industry standard?
Quote from: dariSSight#1 on June 26, 2013, 12:45:23 AM
Reddeercity thanks for getting the conversation started with the upscale possibility of Magic Lantern gift of RAW video, but to think of the 5D Mark II ML RAW firmware ability as only use for B-Roll kind of sucks. So let's begin with why not use Magic Lantern's gift of RAW as main film production stock? Why not use the the Rawness DNG to upscale at least to 2K, the reports of the Data from the DNG holds up? Why not use the Canon 5D Mark II for motion picture projects, I ask these questions keeping in mind that the fast race car scene in the beginning of Ironman 2 was shot with the Canon 5D Mark II with no fear of Rolling Shutters, the full 6th season finale of House was shot Exclusively with the 5D Mark II (it was a visually broad canvas presentation), the feature film ACT OF VALOR was shot exclusively with the 5D Mark II for 12 million dollars then grossing 81 million dollars and many more worthy Canon 5D Mark II professional projects. All those example of professional film work was accomplish with the Canon limitation firmware, now even if the limitation of Magic Lantern Firmware in RAW giving the Mark III 1920x1080 continuous RAW and the Mark II only shooting 1880x850 continuous RAW but Magic Lantern firmware setting option is very professional. Final question, Isn't the Magic Lantern 5D Mark II firmware settings and RAW capabilities industry standard?
:D
Don't get me wrong, I think the 5D Mark ii Is As good if not Better in some cases then Red, Sony etc..
At 2K you would not tell the difference. As Long as you Film in a way to show off the 5D2 Strong points,
& limit fast pans, & no complexes pattern from a distance etc...
But the Fact remains that In larger productions 5D mark ii will not get any Chances to prove it self @ 14bits
like all the Big Name players,
Why would you if you were a Production company, Have a choice between
a 1DC @ 4K compressed with a tried and true Workflow & a 5D Mark ii Magic Lantern Raw Record with a
Not so easily work flow in development , (i know the work flow will get better)
But Big productions will use the 5D mark 2 or 3 as "B" roll all day long ;)
What Magic Lantern has done is put the power of RAW into the Hands of Small Video Production Company
So we can compete with the larger Production Company s without Breaking the Bank!
edit:
I will Kept using the 5d mark 2 in all projects, I was very very interested in buy a new Body like a 1DC,
but that can wait for now. But i will be on the lookout for any used 5d2 or 5d3 .
Quote from: a1ex on June 25, 2013, 12:33:59 PM
I can't reproduce the pink frame issue at all.
Straight from my card: http://a1ex.magiclantern.fm/bleeding-edge/5D2/5d2-fac94f686d23-pink-debug.zip
Write down the black levels (they appear in the top area on the screen, when starting and when stopping recording) and post them, along with the result (whether the recorded frames were pink or not).
@a1ex
Heres the test I did on the pink-debug.
I did the test 2x consecutively for each resolution.
In all tests the BL is the same value at beginning and end of clip recording.
In 1X mode, BL=Black Level
Resolution -- test 1 BL/test 2 BL
1872 x 1054 -- 1793 / 1793
1872 x 1012 -- 1793 / 1793
1872 x 936 -- 1793 / 1793
1856 x 1044 -- 1793 / 1793
1856 x 928 -- 1793 / 1793
1728 x 928 -- 1793 / 1793
In 3X crop mode (5x magnify)
Resolution -- test 1 BL/test 2 BL
2144 x 1078 -- 1023 / 1043
2144 x 972 -- 1793 / 1076
1920 x 1076 -- 1793 / 1792
1856 x 1044 -- 1023 / 1023
1728 x 972 -- 1023 / 1793
Quote from: a.d. on June 25, 2013, 10:37:15 AM
@ all with random pink frames in crop mode
https://bitbucket.org/a_d_/laboratory/wiki/Home
@ted and duncanidaho25
Beautiful shots of the Moon
@motionpikczer
I like it
@a.d.
Thanks for the Fix for pink frames.
Tested it in various resolutions repeatedly, NO MORE PINK FRAMES IN CROP MODE.
Fortunately I do not suffer the bad pixel problem shown in this link.
http://www.magiclantern.fm/forum/index.php?topic=6426.0
I think It seems to be some race condition between EDMAC and Canon stuff, also in Grayscale mode, and not every camera are affected.
Vanilla for testing:
Update: Deleted!
It's from switching from correct preview (with dots) to gray preview (without dots). These two have different black levels.
Try this in raw_video_rec_task:
/* wait for two frames to be sure everything is refreshed */
frame_countdown = 2;
instead of 1.
Was there any changes to hardware/software on the 2nd edition of the 5D mkii?
I noticed mine is slightly different from my friends older version of the Mkii, he has the one with less water protection, i remember reading about the the two difference's somewhere before i bought mine and im sure the sensor may of been slightly tweaked also? could this be why some are suffering and some are not?
No, the pixels I'm talking about come from the Canon's focusing algorithm. They are the result of an edge detection filter.
In many cases they are not noticeable, but when you see them, they are impossible to remove because their location is not constant. They follow high-contrast areas.
Try shooting a barcode or a resolution chart or something similar to see for yourself.
Note: these pixels appear only in 5x color preview.
Using your build A1ex im not getting the problem, iv just noticed also my Focus settings for Video are setup to Quick Mode and not Live Mode, shouldn't make a difference should it? I know Live Mode has contrast detection but id of thought all three modes would due to the edge detection filter.
I also have Auto Lighting Optimization off, Highlight Tone Priority off and High ISO Noise Reduction off as i set my quality to Jpeg for the extra memory.
Good luck guys, im sure you will solve it sooner or later, we all thought RAW video wasnt possible and look where we are :)
I've updated the vanilla build with a1ex fixed for further testing:
6dfbee990661_2nd.zip (https://dl.dropboxusercontent.com/u/13314708/6dfbee990661_2nd.zip)
Quote from: sdesign on June 26, 2013, 12:42:48 AM
perhaps then, mu question may be off topic, but then, how does a smaller sensor, like the 50d, get more latitude, as well as a higher bitrate?
I guess, although the sensor is smaller, it is made up by bigger (and less) pixels resulting in less lineskipping, not sure about the bitrate but that is probably somehow related to the CF portal bottleneck
I've got a 5d M2 and edit on a mac computer. I can't find the information I'm looking for on this thread, and I wonder if anyone who has made ML work with this configuration would be willing to email me and later answer some questions on the phone. I live in the USA and can pay you something for your trouble via paypal. email address is dandmcguire at gmail.com.
Thanks,
Dan McGuire
Somehow the latest build with this new saving method of buffer is not so much speeding up my recordings.
@a.d. I have found some possible bugs. I don't know if anyone else has this but in the latest daily build, and the one before it at least, lists 1856 as the resolution rather than 1872 with 1880 turned off. It always shows as 1856 in the menu but when I select that resolution with 1880 on the resolution display on the live view shows 1880. When I disable 1880 the live view displays this as 1856. The videos are recoreded at 1856 so there is no way of getting 1872.
Also the needed MB/S indicator is off by a factor of 10, its displaying 616.6 mb/s rather than 61.7 mb/s for example.
@a1lex
The fixed works
@bnvm
It's not a bug, you need to choose 1920 to get 1872
@Petruk
just post your post-processing problem in this section:
http://www.magiclantern.fm/forum/index.php?board=14.0
@a.d. Got it, just a thought but it may be good to make the 1880/1872 their own independent resolutions separate from 1920, that way someone could shoot 1872 regular and in 5x crop mode. Right now it is only possible to shoot 1872 regular and 1920 crop. Thanks and awesome work.
I can't manage to get higher than 58mbs write speed using my 32gb Lexar 1000x on my 5d2.
I have the instructed camera settings, and global draw turned off.. Am I doing something wrong, or do I have a bad card?
Thanks,
Will.
Quote from: Will@Elevate on June 27, 2013, 01:44:30 AM
I can't manage to get higher than 58mbs write speed using my 32gb Lexar 1000x on my 5d2.
I have the instructed camera settings, and global draw turned off.. Am I doing something wrong, or do I have a bad card?
Thanks,
Will.
As far as im aware the 5D Mkii can only write upto 60mb? i could be wrong, the 1000X speed is read speed, usually on 90mb cards it's referring to read speed.
Quote from: Will@Elevate on June 27, 2013, 01:44:30 AM
I can't manage to get higher than 58mbs write speed using my 32gb Lexar 1000x on my 5d2.
I have the instructed camera settings, and global draw turned off.. Am I doing something wrong, or do I have a bad card?
Thanks,
Will.
are you setting up your camera in JPEG??
I have the Lexar and it writes high 60s, occasionally 70. As has been noted, set the camera to jpg *stills* and turn off raw stills. Turn off ML global draw. And finally, turn off all on-screen Canon graphics. i.e. Press the 'info' button until the display shows only the LiveView image, not the aperture, shutter, ISO, EV, or anything else.
Quote from: Hazer on June 27, 2013, 06:09:33 AM
I have the Lexar and it writes high 60s, occasionally 70. As has been noted, set the camera to jpg *stills* and turn off raw stills. Turn off ML global draw. And finally, turn off all on-screen Canon graphics. i.e. Press the 'info' button until the display shows only the LiveView image, not the aperture, shutter, ISO, EV, or anything else.
I have done all these. when you say high 60's are you referring to the benchmark results (stills/movie mode), or what you see while recording raw video?
Thanks.
EDIT: 70mb/s is the max write speed for the 5D2 correct?
Quote from: Will@Elevate on June 27, 2013, 07:07:24 AM
I have done all these. when you say high 60's are you referring to the benchmark results (stills/movie mode), or what you see while recording raw video?
Thanks.
EDIT: 70mb/s is the max write speed for the 5D2 correct?
benchmarks aside, can you record 1728 x 972 continuously?
Quote from: a.d. on June 26, 2013, 01:25:51 PM
I've updated the vanilla build with a1ex fixed for further testing:
6dfbee990661_2nd.zip (https://dl.dropboxusercontent.com/u/13314708/6dfbee990661_2nd.zip)
@a.d. & a1ex
Here is my comparative test between a.d. jun 25 nb "pink fix" (d07dab0ba6c2)
and that of the nb dated jun 26 "combining" a1ex "vanilla" and a.d. (6dfbee990661_2nd)
PINK cast in 5x crop modes are gone.
BUT apparently a.d. nb jun 25 seem to have slightly more frame count than that of nb jun 26.
For these tests, I want to activate features that would be useful for "serious testing".
GD= ON, Preview= Auto. FPS is still set to 23.976.
I made 2 consecutive recordings per resolution to get average # of frames except for 1856x928
were I made 4 tests each due to the high difference, i wanted to confirm the frame count.
test results are separated by ( / ).
RESOLUTION -- JUN 25 -- JUN 261x MODES
1872 X 1054 -- 395/
501 -- 447/379
1872 X 1012 --
882/822 -- 769/710
1872 X 936 -- 2389/
3359 -- 2764/2011
1872 X 850 -- continuous -- continuous
1856 X 1044 --
612/573 -- 611/567
1856 X 928 --
8675/2445 -- 4891/4267
/9101/9927 /2099/4891
1728 X 972 -- continuous -- continuous
1472 X 1104 -- continuous -- continuous
CROP MODES 3X (5X MAGNIFY)
2144 X 1076 --
234/237 -- 219/197
2144 X 1072 --
211/241 -- 153/178
2144 X 972 --
353/373 -- 326/302
1920 X 1076 --
402/411 -- 347/313
1856 X 1044 --
677/794 -- 611/567
1728 X 972 -- continuous -- contnuous
Also, other features I like in the 25th NB are;
The Black border crop from pravdomil.
Though minor, the options of 1880.
Though I know this is still testing phase, the buffer meter and
other info are smaller and out of the preview frame.
About the preview during recording in crop mode, is it
possible to have the option to choose between, ML grayscale and the
one in 25th build where you get realtime view and color? in the 26th NB
only ML grayscale is there. its ok since framing is accurate but preview
lags so much.
Did you have the same overlays enabled while recording, in both builds?
I did not remove the Canon preview during crop mode. It's grayscale while recording because of image quality issues with the color preview (I've explained it a lot of times).
Quote from: a1ex on June 27, 2013, 08:36:59 AM
Did you have the same overlays enabled while recording, in both builds?
I did not remove the Canon preview during crop mode. It's grayscale while recording because of image quality issues with the color preview (I've explained it a lot of times).
yes. Both have the same settings. cards are formatted everytime I change builds and also before i do the long recordings.
I understood your concerns on the preview.
I've checked the code and can't explain the speed difference. Can you compare the latest vanilla (#625) with the one that still had pink cast issues? (#597)
I've noticed the overlays are turned off while recording in a.d. version, while on vanilla builds you have to do so manually.
Also check whether the predicted frame number is achieved. That one is based on the ideal mathematical model: buffer_size / (capture_speed - measured_write_speed). If you are reaching that number, the buffering strategy is optimal (you can't get any better than that without increasing write speeds).
If you are not reaching the predicted number (say it predicts 2000 frames and you only get 1500), we need to enable the debug graphs to see what's going on. Most likely, ML is overestimating card write speed a little.
In my own tests, the prediction was pretty good.
First of all: I tested a1ex build and was surprised how few settings there are availlable (until now I only used a.d.'s builds). That's generally great, except one setting: '1880 or 1872'.
On the first hand, 8 pixels more (and 2 the other dimension) are not really something you need to fight for.
But on the other hand, why should I drop them if they are availlable anyway (thus even crop my image a little bit (the recording frame is obviously smaller with the lower resolution)) when there's no decreasing in speed performance?
By the way: Since I joined the raw builds (about two weeks ago), I tried every new build and never had any bad pixels or anything like that. But I never used the 5x or 10x crop modes for I can't see much sense in that (for me).
Hello! Just downloaded 282abfa87fef.zip, installed and took my 5d mark ii out to a field to test for 20 min. at sunset. Unfortunately I forgot my release plate so it's all handheld. The card is a 32 gb lexar 1000. I've used ML for a while now and I didn't take too much time to read up on the new raw features - just looking at the incredible results around the web!
So here's my rough test:
https://vimeo.com/69220598
So I noticed a couple of things - one clip was pink all the way through - it was at 10x. There are also some clips which stutter quite extremely - I was wondering if it was because I had my image stabilizer on and the camera wasn't moving enough? Thoughts on that? There is also a line at the bottom through a couple of the clips.
But I shot directly into the setting sun and there is visible foreground!!! Amazing! (I am using a Light Craft variable nd filter)
I used raw2dng and graded in AE - then exported to h264 720p for vimeo.
Below links to
0 is pink, 21 stutters and 18 has the line at the bottom.
https://dl.dropboxusercontent.com/u/79843444/000000.dng
https://dl.dropboxusercontent.com/u/79843444/000021.dng
https://dl.dropboxusercontent.com/u/79843444/000018.dng
Thank you for what you're doing here! Keep it up! ;D
Quote from: a1ex on June 27, 2013, 08:49:02 AM
I've noticed the overlays are turned off while recording in a.d. version...
Quite useful 8)
Quote from: Will@Elevate on June 27, 2013, 07:07:24 AM
I have done all these. when you say high 60's are you referring to the benchmark results (stills/movie mode), or what you see while recording raw video?
Thanks.
EDIT: 70mb/s is the max write speed for the 5D2 correct?
Hi, :)
you should be getting at least 65MB/s- 70MB/s write to the card on Lexar 1000x 32GB card
As of June 22nd built these are the Number i'm getting ;)
Test out my Scandisk 600x 90MB/s 32 GB
1880x800 24p @ 57.3-60.1 MB/s Continuous Recording
On my Lexar 1000x 32 GB , with the June 22 Built
1856x928 24p @ 68.7-69.1MB/s with frame over ride on
1880x854 24p @67.2MB/s with frame over ride on
Crop mode : 2048x856 24p Continuous Recording
In my setting i have Frame over ride On @ "24p" exact, Not 23.98
and i set my Photos to Small Jpeg.
i have Problems recording anythink over 70 MB/s
@guentergunter: I have explained the reasons for mod16 resolutions, and I'll stick with that.
If a.d. wants to provide 1880, that's his own choice and I do not support it in any way. I know what trouble I had on 5D3 with random lockups because of DMA misalignment, so I'll stick with a portable solution that works everywhere.
As for the other options, some of them are good and will be added to vanilla builds (e.g. black bars, but in a clean way that does not fight with other overlays), others are just ugly hacks (e.g. dropping frames instead of optimizing playback code, or some status displays moved over ML overlays, therefore flickering like crazy if you enable both.
Quote from: a1ex on June 27, 2013, 08:49:02 AM
I've checked the code and can't explain the speed difference. Can you compare the latest vanilla (#625) with the one that still had pink cast issues? (#597)
I've noticed the overlays are turned off while recording in a.d. version, while on vanilla builds you have to do so manually.
Also check whether the predicted frame number is achieved. That one is based on the ideal mathematical model: buffer_size / (capture_speed - measured_write_speed). If you are reaching that number, the buffering strategy is optimal (you can't get any better than that without increasing write speeds).
If you are not reaching the predicted number (say it predicts 2000 frames and you only get 1500), we need to enable the debug graphs to see what's going on. Most likely, ML is overestimating card write speed a little.
In my own tests, the prediction was pretty good.
I have data from tests with vanilla, give me a couple of minutes while I run some confirmatory tests.
Comparing Vanilla (5d2-fac94f686d23-pink-debug ) and a.d. pink fix jun 25 (d07dab0ba6c2)
Ran tests 2 times consecutive for each resolution except in 1856 x 928, ran it 4 times
Resolution -- A1ex -- a.d. jun 25 pink fix
Vanilla jun 25
1X
1872 x 1054 -- 390/528 -- 395/501
1872 x 1012 -- 840/709 -- 882/822
1872 x 936 -- 3667/2009 -- 2389/3359
1872 x 850 -- continuous -- continuous
1856 x 1044 -- 510/436 -- 612/573
1856 x 928 -- 3989/5177 -- 8675/2445
/3321/6452 /9101/9927
1728 x 972 -- continuous -- continuous
1472 x 1104 -- continuous -- continuous
3X Crop mode
2144 x 1076 -- 188/235 -- 234/237
2144 x 1072 -- 221/218 -- 211/241
2144 x 974 -- 487/376 -- 353/373
1920 x 1076 -- 416/386 -- 402/411
1856 x 1044 -- 736/748 -- 677/794
1728 x 972 -- continuous -- continuous
Results are close except for that in 1856 x 928
Quote from: a1ex on June 27, 2013, 09:02:48 AM
@guentergunter: I have explained the reasons for mod16 resolutions, and I'll stick with that.
If a.d. wants to provide 1880, that's his own choice and I do not support it in any way. I know what trouble I had on 5D3 with random lockups because of DMA misalignment, so I'll stick with a portable solution that works everywhere.
As for the other options, some of them are good and will be added to vanilla builds (e.g. black bars, but in a clean way that does not fight with other overlays), others are just ugly hacks (e.g. dropping frames instead of optimizing playback code, or some status displays moved over ML overlays, therefore flickering like crazy if you enable both.
It's a theme with two sides...
On the one hand, it's about in-camera write speed. That's something I absolutely trust you (since I don't know much about those algorithms), when you say it decreases write performance (although I do not suffer from that with 1880).
On the other hand it's about h.264. Let's suppose someone owns a 5D2 and does not want to crop the image (5x or 10x) due to the loss of wide angle perspective. So his highest possible resolution is 1880/1872. But noone will use these resolutions for anything further. Thus it's resized to (most obviously) 1080p or 2K.
By scaling an image that way, any previous mod16 resolution will become absolutely needless, unless the primary resolution overall is as high as possible. And here he goes to 1880.
I did not say anything about camera speed. I only said I had trouble with non-round resolutions in other cameras, and I see no good reason for adding an exception on 5D2 just because it seems to work.
@ted: are you sure the overlays are enabled in both builds while recording?
Quote from: ted ramasola on June 27, 2013, 09:30:34 AM
Comparing Vanilla (5d2-fac94f686d23-pink-debug ) and a.d. pink fix jun 25 (d07dab0ba6c2)
Ran tests 2 times consecutive for each resolution except in 1856 x 928, ran it 4 times
Resolution -- A1ex -- a.d. jun 25 pink fix
Vanilla jun 25
1X
1872 x 1054 -- 390/528 -- 395/501
1872 x 1012 -- 840/709 -- 882/822
1872 x 936 -- 3667/2009 -- 2389/3359
1872 x 850 -- continuous -- continuous
1856 x 1044 -- 510/436 -- 612/573
1856 x 928 -- 3989/5177 -- 8675/2445
/3321/6452 /9101/9927
1728 x 972 -- continuous -- continuous
1472 x 1104 -- continuous -- continuous
3X Crop mode
2144 x 1076 -- 188/235 -- 234/237
2144 x 1072 -- 221/218 -- 211/241
2144 x 974 -- 487/376 -- 353/373
1920 x 1076 -- 416/386 -- 402/411
1856 x 1044 -- 736/748 -- 677/794
1728 x 972 -- continuous -- continuous
Results are close except for that in 1856 x 928
Ted thanks for your extensive information, after your testing so far which build are you using?
im currently using 5d2-fac94f686d23-pink-debug which A1ex posted earlier, so far so good :) best one so far, not all features there but i added the ETTR module my self and seems a'ok, nice n stable.
Quote from: a1ex on June 27, 2013, 10:13:41 AM
I did not say anything about camera speed. I only said I had trouble with non-round resolutions in other cameras, and I see no good reason for adding an exception on 5D2 just because it seems to work.
Quote from: a1ex on May 30, 2013, 01:43:02 PM
Noticed that frame sizes multiple of 512 are a little faster to write (credits: CHDK (http://chdk.setepontos.com/index.php?topic=9970) and confirmed with my benchmark; also DMA block size is 512, so it makes sense). So, I've rounded things to 64x32 or 128x16, to make sure frame size is multiple of 512.
And indeed, according to my benchmark, 1920x1088 is a little faster to save than 1920x1080.
Now it's your job to calm down the guys who will flood the forum asking where did 1920x1080 disappear ;)
Anyway, I can definitely understand your point and might behave just as.
Quote from: Doyle4 on June 27, 2013, 11:59:54 AM
im currently using 5d2-fac94f686d23-pink-debug which A1ex posted earlier, so far so good :) best one so far, not all features there but i added the ETTR module my self and seems a'ok, nice n stable.
These post you guys are referring to are for the 5D Mark III?
Quote from: dariSSight#1 on June 27, 2013, 02:52:26 PM
These post you guys are referring to are for the 5D Mark III?
Thats for 5D mkii direct from A1ex himself :)
Hello a.d.,
After Effects CS4, nor Photoshop CS5 can't parse dng's created with raw2dng from June,14 (yours latest build for WIN).
But, I still have yours older June,8 build and it works perfectly fine.
Thnx for your work.
Quote from: Yaros525 on June 27, 2013, 03:21:11 PM
Hello a.d.,
After Effects CS4, nor Photoshop CS5 can't parse dng's created with raw2dng from June,14 (yours latest build for WIN).
But, I still have yours older June,8 build and it works perfectly fine.
Thnx for your work.
Same problem here, cannot import in After Effects CS4 "Import module could not parse the file" or something similar, but I can open them with Photoshop CS5 and Camera Raw 6.7 (Win XP SP3)
@A1ex sorry I am sure this info is somewhere else but I am kind of new here, where do I get the current builds for your version? Thanks.
Quote from: bnvm on June 27, 2013, 04:44:48 PM
@A1ex sorry I am sure this info is somewhere else but I am kind of new here, where do I get the current builds for your version? Thanks.
Its on page 26 on this topic at the top,
Quote from: a1ex on June 27, 2013, 10:32:24 AM
@ted: are you sure the overlays are enabled in both builds while recording?
Yes I am sure.
When I was doing the tests for optimum frame count and malloc tests I had GD=off. preview=hacked, FPS override.
For the tests I did for the pink debug, using (1)vanilla jun 25, (2) a.d. jun 25, (3) a.d. jun 26, I had GD=ON, preview=auto, FPS override.
Quote from: dariSSight#1 on June 27, 2013, 11:35:19 AM
Ted thanks for your extensive information, after your testing so far which build are you using?
Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.
For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.
Quote from: andrus on June 27, 2013, 03:33:13 PM
Same problem here, cannot import in After Effects CS4 "Import module could not parse the file" or something similar, but I can open them with Photoshop CS5 and Camera Raw 6.7 (Win XP SP3)
Same problem with CS3.
CS5 is ok.
Hmm.. old versions of CS seem not support opcode
@andrus
Version from 2013/06/08
5D2_WIN_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5D2_WIN_raw2dng.zip)
Hello all. Noticing improvement from June 19 to June 27 version
June 19 build
1880x940@24p max recording time : 1:30 seconds
June 27 build
1880x940@24p max recording time : 2:33 seconds
Write speed 69.8 MB/sec on Lexmark 1000x 32GB.
Keep up the great work guys!
Currently testing the jun 27 build and with 1872 x 1054, I did 2 takes and I found one clip containing "vertical" noise in all frames.
The 2nd clip is clean.
Whole frame:
(https://fbcdn-sphotos-b-a.akamaihd.net/hphotos-ak-prn2/1040883_338664332931024_498829654_o.jpg)
enlarged portion:
(https://sphotos-a.xx.fbcdn.net/hphotos-ash4/1048802_338664309597693_733392382_o.jpg)
The new hack option puts my 600x Sandisk 16GB card just into continuous levels at 1880x854! Write speed seemed to stick around 64.7 MB/s. Gonna inspect the frames to see if I get anything like ted ramasola is seeing. I'll also have to account for the fact that I left the unofficial 1880 option on as well...
edit: It was probably a bad idea to record my LCD screen for this test due to the moire lol. I don't see anything wrong, but I'll test it again later.
Whoa, I pushed the res a little higher to see where the write speeds will top off and it seems to be at around 67.5 MB/s @ 1880x940 24.000 FPS. It started off at 68.5 MB/s for a good 10 seconds or so, but dropped. We've come a long way since the early days where I couldn't get more than 53 MB/s. :D
I have been experiencing vertical noise. First noticed it a few days ago after taking a bunch of photos. It went away after recording a video and then it appeared again yesterday when I first fired up my camera.
Can you upload the first DNG from the clip?
Quote from: Yoshiyuki Blade on June 27, 2013, 08:16:27 PM
The new hack option puts my 600x Sandisk 16GB card just into continuous levels at 1880x854! Write speed seemed to stick around 64.7 MB/s. Gonna inspect the frames to see if I get anything like ted ramasola is seeing. I'll also have to account for the fact that I left the unofficial 1880 option on as well...
edit: It was probably a bad idea to record my LCD screen for this test due to the moire lol. I don't see anything wrong, but I'll test it again later.
Whoa, I pushed the res a little higher to see where the write speeds will top off and it seems to be at around 67.5 MB/s @ 1880x940 24.000 FPS. It started off at 68.5 MB/s for a good 10 seconds or so, but dropped. We've come a long way since the early days where I couldn't get more than 53 MB/s. :D
im getting the same results here.
im on a transcend 600x 16gb.
continuous recording at 1872x796.
peaking at 68mb/s and averaging around 64mb/s.
well done gentlemen :)
ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?
I didn't save the clip. I figured it was due to me stressing the camera (I was taking lots of bursts) and the 2nd time it happened there was no evidence of it after I pressed record, what puzzled me was why it happened to a camera that was 'cold'. The noise in Ted's image seems more uniform than what I saw. I'm using your latest build and no noise so far.
"ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?"
Correct me if I'm wrong, but I think the perceived effect of the C modes was down to photo settings and switching them down.
Quote from: Doyle4 on June 27, 2013, 03:17:04 PM
Thats for 5D mkii direct from A1ex himself :)
How are they receiving 1920x1088 or 1920x1080, are those reads from crop option?
Quote from: ted ramasola on June 27, 2013, 06:56:10 PM
Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.
For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.
I was referring to which build has the most stable frame increase, but I get your point all builds are from a growing improvement. Going to test out the June 27 build.
Just tested latest build (06/27) with Transcend 1000x 16Gb
with "small hacks" on
vs 06/25:
1880x1058 FPS 23.9 > 265/330
1880x1058 FPS override 20 > 807/2269 (write speeds up avg from 60 to 64 Mb/s)
1728x972 FPS 23.9 > 686/1720
Indeed huge performance breakthrough!
Still wonder, why lowering FPS significantly increases write speed, any ideas?
Anyway, 1880x1058 @20fps looks very good for me )
uh, yea, less fps= more room in the buffer.
Quote from: Redrocks on June 27, 2013, 09:07:42 PM
"ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?"
Correct me if I'm wrong, but I think the perceived effect of the C modes was down to photo settings and switching them down.
so at this point, C-modes have no bearing on buffer space.
If you kill the timer completely you might get more speed.
C modes should have never had effect on buffer... but you probably had different settings in them which did.
I don't see why 5DII can't do 80MB/s when 50D can.
If you no-op this, timer should be off completely:
ROM:FFAAF418 BL str_StartDialogRefreshTimer
I noticed under Small Hacks it says, Disable Auto White balance and exposure, does it mean it is disabling it or we have too manually? i know how to disable Auto White balance but not exposure if someone could let me know please.
Cheers.
UPDATED: It is under Live View/Movie func. / Stills+Movies and then be sure to be set to Movie Display. If
it is set to Exposure Simulation, the camera, after hitting the record button, will go to auto exposure.
:) Hi All,
Just tested the New Bulit by A_D_ today June 27th .(b77a85f7ac68)
Great speed , I didn't think the 70MB/s wall would be push back :o
I have Never had any pixel issues before like other had, so
i tried his hack, & i am seeing speeds close to 80MB/s Stable ;D
i tested the Frame sizes that i would use & the ones that are Continuous.
1856x1004 24p 1:85.1 74.7-75.1MB/s Continuous.
1856x1044 24p 16x9 75.6 MB/s 2300 Fame?
1872x1012 24p 1:85.1 75.1 MB/s 3925 Frames
1872x940 24p 2:1.1 73.4 MB/s Continuous.
1880x1016 24p 1:85.1 74.7MB/s 2526 Frames
1880x940 24p 2:1.1 71.8-72.3 MB/s Continuous.
Crop:
2048x930 24p 2:20.1 76.3 MB/s Continuous
2048x1024 24p 2:1.1 78.1 MB/s 890 Frames
2144x896 24p 2:39.1 77.9 MB/s Continuous
2144x912 24p 2:35.1 78.2MB/s 5167 Frames
Tested on Lexar1000x 32 GB
Frame over ride set to 24p Exact
Small Hack on
Jpeg small, Every thing on default.
;D
Complete newb, but I read the whole post and wasn't able to find anyone with an issue like mine.
I've gotten everything to work except the FPS override. When I toggle the options it first shows 23.976, then switches to 2.502. I'm not able to get to either 24 or 25.
Is there another setting that I'm missing to unlock 24 or 25? Thanks!
I am using 282abfa87fef from 6/25.
Quote from: qma5D on June 28, 2013, 02:08:36 AM
Complete newb, but I read the whole post and wasn't able to find anyone with an issue like mine.
I've gotten everything to work except the FPS override. When I toggle the options it first shows 23.976, then switches to 2.502. I'm not able to get to either 24 or 25.
Is there another setting that I'm missing to unlock 24 or 25? Thanks!
I am using 282abfa87fef from 6/25.
Make sure in "frame over ride" you go to
"Optimize For" set to "Exact FPS"then set to (in my case 24)
make sure in the Canon Live View/Movie func. set. menu
you are set to 1920x1080 24.
;)
I only have the option for 1080/23.98 or 1080/27.97 in the set menu.
I have 1080/23.98 selected.
I don't have any of those options in the "Frame Over Ride" section. I can only select "2.502" or "Off"
Thanks for your response!
Jun 27 build is an awesome leap in performance.
Amazing job ML team!
Below is a comparison between the best performance of jun 26 with "variable buffer"
to Jun 27 with "small hacks".
Figures separated by a / indicate another test record done.
Also included results for "expected" frames, the figure is the last one shown
at the end of recording.
Hopefully this will help A1ex fix the formula to estimate/predict recorded frames.
In the case of 1872 x 1012, for jun 27 build, the figure expected is very high(8663)
compared to actual recorded frames (4686).
More resolutions are now continuous!
Resolutions a.d. jun 26 a.d. jun 27 expected
1X Mode
1872 x 1054 447/379 1058/937 1127/972
1872 x 1012 769/710 2749/4686 3709/8663
1872 x 936 2764/2011 continuous continuous
1872 x 850 continuous continuous continuous
1856 x 1044 611 2378 2917
1856 x 928 4891 continuous continuous
1728 x 972 continuous continuous continuous
1472 x 1104 continuous continuous continuous
Crop Mode 3X
2144 x 1076 219 371 389
2144 x 1072 178 370 382
2144 x 974 326 947 1014
1920 x 1076 347 1326 1548
1856 x 1044 611 continuous continuous
1728 x 972 contnuous continuous continuous
Great job guys!
new build 27/06 amazing!@@ super speed i have just one problem!!! i always have the fps override 24 ON but some files seems to come out with 29.97 in 5x and 29.973 in 1x.... at least is what raw2dng or RAWMagic tells me sometimes... NOT ALL FILES COME LIKE THAT its random. Any ideas ?
edit: ok shooting more videos it seems to get stable 24 frames.... pretty strange :D anyway KIIILLLLING IT guysss :D
Do you guys do FPS override 24.000 fps when the LV mode is set to 24 FPS mode or 30 FPS? I found that I can get a shutter angle closer to 180 degrees in 30p mode and I *think* write speeds are very slightly higher (not sure if placebo). Are there any drawbacks with doing 30 FPS mode overridden to 24.000 FPS versus overriding the default 24 FPS mode?
Quote from: Yoshiyuki Blade on June 28, 2013, 06:49:08 AM
Do you guys do FPS override 24.000 fps when the LV mode is set to 24 FPS mode or 30 FPS? I found that I can get a shutter angle closer to 180 degrees in 30p mode and I *think* write speeds are very slightly higher (not sure if placebo). Are there any drawbacks with doing 30 FPS mode overridden to 24.000 FPS versus overriding the default 24 FPS mode?
My setting is 24p in canon menu, FPS override=23.976. Definitely more frames than when canon menu set to 30p.
Quote from: ted ramasola on June 27, 2013, 06:56:10 PM
Using? Like in real project? I would not recommend one at this point since development by the ML team is moving so fast.
For testing, I recommend you follow the current builds and draw your own conclusions based on the CF cards you are using.
Well, now that I've seen the raw, I'll probably never want to use anything else. And I have no fear of using it in real projects by now.
Can you run some card benchmarks (first or second, whichever you want) in playback mode?
(start the benchmark in photo mode with display off)
I'd like to compare the results with the ones from 50D.
Another Canon setting that may make a difference: LCD brightness should be set to Manual.
CPU usage of LightMeasureTask in play mode:
with LCD brightness auto: 19.3%
with LCD brightness manual: 0.1%
Quote from: a.d. on June 27, 2013, 07:34:57 PM
Hmm.. old versions of CS seem not support opcode
@andrus
Version from 2013/06/08
5D2_WIN_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5D2_WIN_raw2dng.zip)
a.d. thank you very much, I can import in AE CS4 with Camera Raw 5.0 with this version, quality is crystal clear!!!
@a1ex
Here are the results from a Sandisk Extreme Pro 600x 16GB:
(http://i.imgur.com/gXo9xbP.png)
Using a.d.'s build from commit b77a85f7ac68 (6-27-2013).
June 27 build : Hack On : LCD Manual : Lexar 1000x 32GB
1880x940 @ 73.5MB/s = Continuous
1880x1058 @ 75.7 MB/s = 50 s = 1213 f
1856x1044 @74.3 MB.s = 1:07 s = 1635 f
Incredible speed increase with the hack, - thank you ML team!
Here is a benchmark with a Pro Master 1000X 16 GB, June 27th build. small hacks on, LCD set to manual, 23.976 fps.
I am getting about 72.9 MB/s now in crop, 71.2 MB/s in normal. I was maxing out previously at around 63 MB/s - 65 MB/s.
1872 x 1054 = 565 f
1872 x 1012 = 890 f
1872 x 936 = continuous
1856 x 1044 = 789 f
1856 x 1004 = 1505 f
1856 x 928 = continuous
1920 x 1076 = 465 f
1920 x 1038 = 711 f
1920 x 960 = 3461 f
1920 x 818 = continuous
2048 x 930 = 1293 f
2048 x 872 = continuous
What is the best procedure for setting up a benchmark anyway. I just turn on the LV and go but I noticed that sets a mode of Movie... where most test show a mode of photo, this is for the benchmark in Debug BTW. Thanks.
Great idea the manual LCD :o
incredible performance leap with the 27th build.
I have a 8Gb Sandisk Extreme at 60mb/s and funny enough i get exactly 60mb/s :)) and sometimes just a bit over.
will test out the resolutions right now.
Quote from: andrus on June 28, 2013, 02:15:05 PM
a.d. thank you very much, I can import in AE CS4 with Camera Raw 5.0 with this version, quality is crystal clear!!!
andrus,
does that version of raw2dng work with files more than 4gig?
Quote from: a.d. on June 27, 2013, 07:34:57 PM
Hmm.. old versions of CS seem not support opcode
@andrus
Version from 2013/06/08
5D2_WIN_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5D2_WIN_raw2dng.zip)
@a.d.
does this old version still have issues with the vertical banding noise? I recall the raw2dng was tweaked to fixed the vertical noise issues.
Quote from: ted ramasola on June 28, 2013, 08:46:21 PM
andrus,
does that version of raw2dng work with files more than 4gig?
Ted I don't know, I'll have to try and let you know.
Quote from: andrus on June 28, 2013, 09:25:13 PM
Ted I don't know, I'll have to try and let you know.
Andrus,
I just rechecked my files and I do believe it does since the +4gig plus feature was implemented starting with May 21 build for raw2dng.
So jun 8 should be ok, what you should check for instead is vertical banding/noise. I think a1ex and others were tweaking the raw2dng to fix it.
Quote from: ted ramasola on June 28, 2013, 09:32:46 PM
Andrus,
I just rechecked my files and I do believe it does since the +4gig plus feature was implemented starting with May 21 build for raw2dng.
So jun 8 should be ok, what you should check for instead is vertical banding/noise. I think a1ex and others were tweaking the raw2dng to fix it.
Ok Ted, I'll check that in the next few days :)
I am getting corruption on all frames if I record in 1880x940 until card is full.
(http://s24.postimg.org/i64r4e2v9/rawerror.jpg)
Joined RAW files through Terminal and processed with GUI Raw2Dng 0.13 in OSX.
Short clips are fine though. Is this normal? Should I just stop the recording manually before card is full next time?
That black bar is on all frames? Seems like skip is wrong.
Anybody with Komputerbay 64GB can confirm the speed improvements?
I remember that in one build, the developers fixed something about Komputerbay cards..
Thing is when everybody got 350frames at 1880, 16/9, i was getting about 380 frames..
For me, the new build is at staying at 350frames (with small jpeg as picture size, manual lcd brightness, fps override 24)
Could it be a software related issue? Or just a slow card
Quote from: mihaii on June 28, 2013, 10:22:53 PM
Anybody with Komputerbay 64GB can confirm the speed improvements?
I remember that in one build, the developers fixed something about Komputerbay cards..
Thing is when everybody got 350frames at 1880, 16/9, i was getting about 380 frames..
For me, the new build is at staying at 350frames (with small jpeg as picture size, manual lcd brightness, fps override 24)
Could it be a software related issue? Or just a slow card
did you turn on small hacks?
the "small hacks" is setting the file type / size as jpeg small?
in the preview i set "hacked"
Quote from: mihaii on June 28, 2013, 10:44:06 PM
the "small hacks" is setting the file type / size as jpeg small?
in the preview i set "hacked"
no no no. "small hacks" is a new option in the raw settings
enable it and test again...
stupid / blind me :)
found the option.. 75MB/sec :)
guys, i'm gonna contribute, you really deserve it
Quote from: mihaii on June 28, 2013, 10:52:11 PM
stupid / blind me :)
found the option.. 75MB/sec :)
guys, i'm gonna contribute, you really deserve it
please post some numbers for the komputerbay 1000
especially for the close-to-1920x1080 sizes
thanks
For 5D2 users looking at how the 30P recording has improved with jun 27 "small hacks" build.
Resolutions # of frames @30P
1872 x 1054 237
1872 x 1012 312
1872 x 936 460
1872 x 850 770
1856 x 1044 287
1856 x 928 489
1728 x 972 650
1728 x 864 3338
1472 x 1104 701
1472 x 828 continuous
1600 x 900 continuous
Crop mode 3x
2144 x 1076 132
2144 x 1072 158
2144 x 974 213
1920 x 1076 235
1856 x 1044 294
1728 x 972 476
1600 x 900 continuous
1472 x 828 continuous
The highest res for continuous recording has indeed increased. Previous NB it was only at 1472x828 Now its at 1600x900.
getting 66mb/s with manual LCD brightness.
64mb/s with LCD brightness set to auto.
about a 2mb/s boost.
june 27 build
transcend 600x
small hacks-on
Quote from: vikado on June 28, 2013, 11:11:04 PM
getting 66mb/s with manual LCD brightness.
64mb/s with LCD brightness set to auto.
about a 2mb/s boost.
june 27 build
transcend 600x
small hacks-on
so how close are we to shooting 1920x817(1:2.35) or 1920x803(1:2:39)?
1920 width is technically not possible with 5D2. Thats according to A1ex when he looked at actual res beoing pulled out of the 5d2 sensor.
This he has mentioned "several" times already.
Quote from: ted ramasola on June 28, 2013, 11:13:40 PM
1920 width is technically not possible with 5D2. Thats according to A1ex when he looked at actual res beoing pulled out of the 5d2 sensor.
This he has mentioned "several" times already.
1920 is possible with crop modes only, I can record 2048 at 1:2.35 continuous with my 5D2.
Quote from: bnvm on June 28, 2013, 11:15:18 PM
1920 is possible with crop modes, I can record 2048 at 2.35/1 continuous.
that is correct. at 1:1 pixel in 3X crop mode. In fact the max for 5D2 is at 2144x1076 crop mode.
What some are asking is the 1x mode from the entire sensor readout. Max width "for now" is at 1872 (a1ex vanilla=more frames) 1880 (a.d. version)
Quote from: ted ramasola on June 28, 2013, 11:18:24 PM
that is correct. at 1:1 pixel in 3X crop mode. In fact the max for 5D2 is at 2144x1076 crop mode.
What some are asking is the 1x mode from the entire sensor readout. Max width "for now" is at 1872 (a1ex vanilla) 1880 (a.d. version)
Understood, but I don't see any reference to 1X recording in the post above just if it was possible. Just clarifying that is is possible and how. Thanks.
I tried to read through the threads but I can't find what 'Small hacks' actually is. Can someone explain this before turning it on? Thanks.
Quote from: Indianac on June 28, 2013, 11:22:18 PM
I tried to read through the threads but I can't find what 'Small hacks' actually is. Can someone explain this before turning it on? Thanks.
If you scroll down to it in the ML menu it will give a tool tip telling what it does. I don't recall exactly but it disables some automatic features, and slows down the refresh rate of the live view, etc... Something along those lines, it basically just disables some features that are not necessary to gain a little speed.
Quote from: ted ramasola on June 28, 2013, 11:13:40 PM
1920 width is technically not possible with 5D2. Thats according to A1ex when he looked at actual res beoing pulled out of the 5d2 sensor.
This he has mentioned "several" times already.
yeah my bad, realized that 1920x1080p was being upscaled.
Yet more advances? You guys make me feel good.
5d2, Komputerbay 64GB, b77a85f7ac68, small hacks on, GD off, exact 24 fps, manual lcd:
1880 x 1250
287
272
285
282
286
282
286
279
1872 x 1250
289
298
280
301
285
297
285
299
____________
1.85:1 is not far off continuous @1872 it seems. I had a momentary issue with write speed data display and performance dropping to under half of my normal numbers. Ignore the essay below if this isn't unheard of.
After doing these tests I put the card in my reader (Kingston FCR HS3) and used RAWanizer 0.5.5 to view the frame count on my tests. I put the card back in the camera without moving or wiping the files and began testing ratios. Started with 1.85:1 and figured I would be close to continuous with that. As soon as I hit record, the buffer filled and I dropped a frame. Went to RAW settings and the write speed was showing yellow 31.3MB/s. Flicked through the ratios and they were all crippled this way. Tried recording at 2.35:1 and that seemed to run as usual, went back to RAW settings and after scrolling through the ratios, the write speed data was showing 74.4MB/s.
Quote from: coma on June 28, 2013, 10:56:04 PM
please post some numbers for the komputerbay 1000
especially for the close-to-1920x1080 sizes
thanks
1872x1052 - 1311frames / 1515 frames / 1427 frames
before this build I was having about 380 frames
I propose the "small hacks" to be renamed in "BIG HACKS" :)
Quote from: mihaii on June 29, 2013, 02:45:34 AM
1872x1052 - 1311frames / 1515 frames / 1427 frames
before this build I was having about 380 frames
I propose the "small hacks" to be renamed in "BIG HACKS" :)
Better yet, they should just include it within the code and ON at default and should not even be an option to be ON or OFF.
DR and heavy grade test on Jun26 build. NOT a test for overall IQ but just seeing how much you can pull back in extreme conditions. Pretty impressive how much it holds on to in the highlights.
I can do 76MBps on my Computerbay 1000x 64GB with the 27th of june build, 1.85:1 at
[email protected]. 8)
.
Quote from: ted ramasola on June 29, 2013, 04:20:03 AM
Better yet, they should just include it within the code and ON at default and should not even be an option to be ON or OFF.
Best to have it as an options as the Small Hack slows down Canons GUI :)
Build b77a85f7ac68
LEXAR 64Gb x1000
1872x1012 apparently continuous at 24fps / small hack on / M / LV movie mode.
just started the test !!, that's great !!!
Quote from: Doyle4 on June 29, 2013, 11:03:52 AM
Best to have it as an options as the Small Hack slows down Canons GUI :)
Then have it ON when Raw Video is ON since you won't be using Canon GUI when shooting .
Eventually when devs have found optimum settings for this, things like Preview=hacked or small hacke=on/off and other graphics used for benchmarking, will be removed and integrated where its activation is transparent to the user.
Quote from: ted ramasola on June 29, 2013, 04:20:03 AM
Better yet, they should just include it within the code and ON at default and should not even be an option to be ON or OFF.
Hope you guys are having a good weekend.
I need answers to some question for me, I know 1872 is the 1/3 line skipping of the Full Sensor Res so is that the Max setting for Raw on 5D Mark II? Also what Aspect Ratio do you use the most and can you give a quick personal reason for your choosing? And finally Ted when you do your very instinctive test I alway wonder are you using the Max setting?
I love the isolation of the frame ratio in Canon Preview option, what is this a disliked preview? Most poster favor ML Grayscale and HaCKeD which I feel all are evenly necessary but why is the HaCKeD option better for frame increase?
@mgm
a1ex already fixed that for 5D3 2 weeks ago, you need to report the bug.
@ted
I've checked it, the difference between both are only the DNG file format 1.2 vs 1.3.
That means 4GB+ and the tweak to fix the vertical stripes are included.
@dariSSight#1
HaCKeD doesn't work on 5D2!
1872 nothing to do with line skipping! 512 are a little faster to write! That's all!
http://chdk.setepontos.com/index.php?topic=9970
Quote from: jplsfx on June 29, 2013, 04:40:28 PM
Build b77a85f7ac68
LEXAR 64Gb x1000
1872x1012 apparently continuous at 24fps / small hack on / M / LV movie mode.
just started the test !!, that's great !!!
Can you confirm that with your card? With a 3sgig 1000x At that resolution with that build its not continuous. I only averaged between 2400 - 4600 frames, Same with jun 29 build.
For now its 1872 x 936, 1872 x 850, 1856 x 928, 1728 x 972, 1472 x 1104 and lower that can give you continuous recording.
Quote from: a.d. on June 29, 2013, 05:32:54 PM
@ted
I've checked it, the difference between both are only the DNG file format 1.2 vs 1.3.
That means 4GB+ and the tweak to fix the vertical stripes are included.
Thanks for checking a.d. I'll use it and see if it will not have issues with the RAWanizer and Raw2Cdng converters as well.
Quote from: ted ramasola on June 29, 2013, 06:04:25 PM
Can you confirm that with your card? With a 3sgig 1000x At that resolution with that build its not continuous. I only averaged between 2400 - 4600 frames, Same with jun 29 build.
For now its 1872 x 936, 1872 x 850, 1856 x 928, 1728 x 972, 1472 x 1104 and lower that can give you continuous recording.
I was able to get 1872x1012 continuous on my Lexar 32GB 1000x with June 27 Build, I'm going to install the June 29th build right now.
Quote from: dariSSight#1 on June 29, 2013, 09:50:56 PM
I was able to get 1872x1012 continuous on my Lexar 32GB 1000x with June 27 Build, I'm going to install the June 29th build right now.
At first few frames the EXPECTED frames would say CONTINUOUS OK but after several thousand frames it would change to a much lower number. You have to see if,
1. It would stop when card capacity is reached.
or
2. It would change and stop before reaching card capacity.
I was misled during a couple of my tests when I immediately saw, CONTINUOUS OK then i stopped recording, when on my subsequent tests it would significantly lower.
I have ran 1872 x 1012 several times and it never would fill up my card.
This is with GD=ON, preview=Auto, since in production scenario you need them to be ON.
GD=off, preview=hacked makes no difference in 27 and 29 build.
Quote from: ted ramasola on June 29, 2013, 10:11:20 PM
At first few frames the EXPECTED frames would say CONTINUOUS OK but after several thousand frames it would change to a much lower number. You have to see if,
1. It would stop when card capacity is reached.
or
2. It would change and stop before reaching card capacity.
I was misled during a couple of my tests when I immediately saw, CONTINUOUS OK then i stopped recording, when on my subsequent tests it would significantly lower.
I have ran 1872 x 1012 several times and it never would fill up my card.
This is with GD=ON, preview=Auto, since in production scenario you need them to be ON.
GD=off, preview=hacked makes no difference in 27 and 29 build.
I stand corrected, thanks
Latest build = awesomenewss in terms of speed =)
Small reminder.
Quote from: a1ex on June 28, 2013, 08:14:08 AM
Can you run some card benchmarks (first or second, whichever you want) in playback mode?
(start the benchmark in photo mode with display off)
I'd like to compare the results with the ones from 50D.
my test :
http://s017.radikal.ru/i414/1307/ec/51308a3d7efb.jpg (http://s017.radikal.ru/i414/1307/ec/51308a3d7efb.jpg)
Hi,
I still have the issue of frame recorded in wrong order when using crop mode. The first frame appear each 2 frames. So it counts 1 2 1 3 1 4 1 5 1 6 and so on. Anyone with same issue ? Issue existing since first release of Raw module.
Quote from: onickz on July 01, 2013, 12:33:12 PM
Hi,
I still have the issue of frame recorded in wrong order when using crop mode. The first frame appear each 2 frames. So it counts 1 2 1 3 1 4 1 5 1 6 and so on. Anyone with same issue ? Issue existing since first release of Raw module.
Sounds to me you are using x10 crop.... it doesn't work.
What do we do with pink videos from 5x crop mode?
Is there any way to make these look normal again? :)
EDIT: it was a problem with RAW2GPCF, so never mind. :)
I want to thank the whole team for the great developers desired interesting work.
Build 3ecd254bdba1 (2013.06.29)
Benchmark card Transcend 32GB 1000x
(http://i.imgur.com/1ekmecA.gif)
Komputerbay 128GB 1000x UDMA7
(http://image-upload.de/image/IM2GVL/8e3088ead2.jpg)
Why is my write speed so low? Better with the 64GB CF card?
Speed keeps getting better, I am now getting continuous recording at 1920x960 (23.976 fps) for the first time. In crop my write speed has increased from 72.9 to 73.8 MB/s. This is with a ProMaster 1000X 16GB card.
my 5d2 with a transcend 1000x 32gb is not even closely as fast as the one above. any ideas why? is this related to "playback" or "photo" mode? and if so: how do i get into playback mode for the test?
(http://dirkmallwitz.net/wp-content/uploads/2013/07/TEST.bmp)
Quote from: dima510 on July 02, 2013, 08:45:24 AM
my 5d2 with a transcend 1000x 32gb is not even closely as fast as the one above. any ideas why? is this related to "playback" or "photo" mode? and if so: how do i get into playback mode for the test?
You want the latest build, your build doesn't have Small Hacks on the build, this helps alot, and also the new Card Warm up seems to be nice, i found writing 128mb to the card on boot up to be best so far.
Quote from: Doyle4 on July 02, 2013, 11:49:29 AM
You want the latest build, your build doesn't have Small Hacks on the build, this helps alot, and also the new Card Warm up seems to be nice, i found writing 128mb to the card on boot up to be best so far.
What do you mean the New Card Warm Up?
Quote from: Doyle4 on July 02, 2013, 11:49:29 AM
You want the latest build, your build doesn't have Small Hacks on the build, this helps alot, and also the new Card Warm up seems to be nice, i found writing 128mb to the card on boot up to be best so far.
thanks for your reply! i was referring to the first benchmark result from *al*, who used the same build (27-jun) and the same card. but his results have been achieved in "playback" mode, which i cannot activate while running the tests - at least i don't know, how :-)
also, this build has the "small hacks" option and i can enable that - but the performace stays low :-/
Goooooodmorning raw people, my first test! 2013-06-27 build
Unfortunately at the moment I can't afford a fast card, I'm testing with a Lexar 200x :(
GD off, small hacks on, LV mode: Movie, 23,976 fps (no fps override)
A few thoughts:
I'm working with After Effects CS4 and Camera Raw 5.0 on Win XP SP3, I'm using raw2dng.exe version 2013/06/08, as a.d. said CS4 doesn't support recent dng files.
On my pc raw2dng will not extract the pictures in the folder where my files are located but I found them in C:\Documents and Settings\MyUserName\ (probably I'm missing something?)
Shots look very good, no vertical stripes, just some bad frames in my second 10x crop mode shot, and the moon shaking in my last one, however I was reading that 10x is not working at the moment...
A new life has begun, things are improving very quickly, thank you so much guys!!!
Quote from: dima510 on July 02, 2013, 12:19:32 PM
thanks for your reply! i was referring to the first benchmark result from *al*, who used the same build (27-jun) and the same card. but his results have been achieved in "playback" mode, which i cannot activate while running the tests - at least i don't know, how :-)
also, this build has the "small hacks" option and i can enable that - but the performace stays low :-/
I believe you benchmark in playback mode by starting the test with the live view off. Don't worry about doing that because testing in playback mode gives invalid results anyways. It is benchmarking the performance of the camera to playback a recorded movie not the speed of recording a raw movie which is always slower. I am not sure what the proper settings are for doing a benchmark but I believe it should be either photo or movie mode.
Quote from: dima510 on July 02, 2013, 12:19:32 PM
thanks for your reply! i was referring to the first benchmark result from *al*, who used the same build (27-jun) and the same card. but his results have been achieved in "playback" mode, which i cannot activate while running the tests - at least i don't know, how :-)
also, this build has the "small hacks" option and i can enable that - but the performace stays low :-/
When i do a bench mark test ill be honest and say im not sure either how to get it photo mode, tried all sorts, iv managed to get it into playback mode and movie but not photo yet :/ if some one can share with us how that be great.
Also you results may be slow due to not having raw video settings correct, again i dont know the right settings but mine are as follows..
Jpeg small (no raw function at all)
LCD brightness - Manual
Highlight tone priority - off
Auto lighting optimizer - off
Global Draw - off
Small Hacks - on
Card Warm Up - 128mb
Update to latest build, enable hacks, enable card warm up with 128mb write and try again dude. ;)
i can´t get more than 64,8mb/s with my komputerbay 1000x udma7 128gb card.
GD off. Small hacks on. ect.
set up at 1872x1012
ratio 1:85
24fps
Global draw off
small Hack on
LV mode movie
warmup 128mo
and tell us.
On my side when my test go over 4Go and it create a second file xxxx00.RAR, when I uncompress it , all the sequence is noisy pink, all bad ... on different format ...
normal guyz ???
raw2dng version ???
Quote from: ch_d on July 02, 2013, 06:26:11 PM
i can´t get more than 64,8mb/s with my komputerbay 1000x udma7 128gb card.
GD off. Small hacks on. ect.
I will receive my 32gb komputerbay in the next days (*FINALLY*), I'll let you know.
Quote from: andrus on July 02, 2013, 12:26:21 PM
Goooooodmorning raw people, my first test! 2013-06-27 build
Unfortunately at the moment I can't afford a fast card, I'm testing with a Lexar 200x :(
GD off, small hacks on, LV mode: Movie, 23,976 fps (no fps override)
A few thoughts:
I'm working with After Effects CS4 and Camera Raw 5.0 on Win XP SP3, I'm using raw2dng.exe version 2013/06/08, as a.d. said CS4 doesn't support recent dng files.
On my pc raw2dng will not extract the pictures in the folder where my files are located but I found them in C:\Documents and Settings\MyUserName\ (probably I'm missing something?)
Shots look very good, no vertical stripes, just some bad frames in my second 10x crop mode shot, and the moon shaking in my last one, however I was reading that 10x is not working at the moment...
A new life has begun, things are improving very quickly, thank you so much guys!!!
There is no 10x crop mode. Only 3x crop mode triggered via 5X magnify button. The 10x magnify will still give you 3X crop mode.
It appears that crop mode has maximum vertical resolution of 1076, any reason why that is?
Quote from: ted ramasola on July 02, 2013, 10:55:02 PM
There is no 10x crop mode. Only 3x crop mode triggered via 5X magnify button. The 10x magnify will still give you 3X crop mode.
Uh?!? Thanks, didn't notice that... need to update my video ^_^
Just a question: when I shoot at 3x the frame rate (displayed in the top right corner of the LV) automatically changes from 23,976 to 29,667... why? Is this the reason why I have to use fps override?
@Clemens: yes, Vesuvio ;)
Quote from: andrus on July 03, 2013, 12:18:12 AM
Just a question: when I shoot at 3x the frame rate (displayed in the top right corner of the LV) automatically changes from 23,976 to 29,667... why? Is this the reason why I have to use fps override?
yes.. that's right... and its good to have fps override ON so you get same frame rate all the time!
Quote from: ted ramasola on June 29, 2013, 10:11:20 PM
At first few frames the EXPECTED frames would say CONTINUOUS OK but after several thousand frames it would change to a much lower number. You have to see if,
1. It would stop when card capacity is reached.
or
2. It would change and stop before reaching card capacity.
I was misled during a couple of my tests when I immediately saw, CONTINUOUS OK then i stopped recording, when on my subsequent tests it would significantly lower.
I have ran 1872 x 1012 several times and it never would fill up my card.
This is with GD=ON, preview=Auto, since in production scenario you need them to be ON.
GD=off, preview=hacked makes no difference in 27 and 29 build.
Hello Ted,
Hope everything is good for you, I was ordering the method behind Card Warm Up function and what's your theory of when and why us the 3x crop when for closer subject its a distance challenge. But I love it no matter what, I will use it for far wide shots and maybe micro subjects.
Quote from: ch_d on July 02, 2013, 06:26:11 PM
i can´t get more than 64,8mb/s with my komputerbay 1000x udma7 128gb card.
GD off. Small hacks on. ect.
Mine varies from 73MB/s to 76.4MB/s
Komputerbay 1000x 32gb
(http://i39.tinypic.com/727lhj.jpg)
where did the audio recording go off to?
also i really wish you guys could bring back the resolution selection of when this first came out. I was shooting anamorphic and a resolution between 4:3 and 1:1 would be great 4:3 gives me 2.66:1 and 11 gives me 16:9 on the old version you didnt have to select an aspect ratio, you could just select width and height. Great work though, cant wait to see how far this will go! Been using magic lantern ever since i bought my first canon (t2i) back in 2010.
Quote from: bnvm on July 02, 2013, 04:53:17 PM
I believe you benchmark in playback mode by starting the test with the live view off. Don't worry about doing that because testing in playback mode gives invalid results anyways. It is benchmarking the performance of the camera to playback a recorded movie not the speed of recording a raw movie which is always slower. I am not sure what the proper settings are for doing a benchmark but I believe it should be either photo or movie mode.
thanks!
Quote from: lagunak47 on July 03, 2013, 04:25:03 AM
where did the audio recording go off to?
also i really wish you guys could bring back the resolution selection of when this first came out. I was shooting anamorphic and a resolution between 4:3 and 1:1 would be great 4:3 gives me 2.66:1 and 11 gives me 16:9 on the old version you didnt have to select an aspect ratio, you could just select width and height. Great work though, cant wait to see how far this will go! Been using magic lantern ever since i bought my first canon (t2i) back in 2010.
ML has change the Game, where from professional videographer to Cinematographers if you have a limited budget but good technique you can achieve very film industry professional end results. You were saying you could get anamorphic 2.66:1 out of 4:3 and anamorphic 16:9 out of 1:1 frame recording, but aren't you cropping out image anyway as ML does now in format selection? I do wish they could put description icon or writing to explain different in aspect ratio for example 2.35:1 or 2.39.1 Cinescope setting and 16:9 or 1.85:1 HDTV setting ect. Please correct me where I maybe make an error in characterization recent anamorphic 2.35:1 or 2.39.1 may be called super 35.
Quote from: lagunak47 on July 03, 2013, 04:09:25 AM
Mine varies from 73MB/s to 76.4MB/s
Komputerbay 1000x 32gb
(http://i39.tinypic.com/727lhj.jpg)
ok - than my low mb/s is caused by my 128gb komputerbay card...
with your exact same settings i can´t get more than 65mb/s
here is my screenshot:
(http://i42.tinypic.com/32zn7up.jpg)
no green text!
Quote from: ch_d on July 03, 2013, 11:11:06 AM
ok - than my low mb/s is caused by my 128gb komputerbay card...
with your exact same settings i can´t get more than 65mb/s
no green text!
Iv read onthe web that the best Komputerbay card is the 64GB one, the rest are not as fast, not sure why but all over amazon people are saying 64GB if using ML.
I'm around 65-70mbs with my transcend 32gb 1000x...
With window's benchmark it's around 95-100 mbs.
At work we bought an 1DC with a 64gb 1000x Hoodman steel (350$), so i made a small bench...
I write 74mbs continuously 8)
Quote from: bronson on July 03, 2013, 12:28:43 PM
I'm around 65-70mbs with my transcend 32gb 1000x...
With window's benchmark it's around 95-100 mbs.
At work we bought an 1DC with a 64gb 1000x Hoodman steel (350$), so i made a small bench...
I write 74mbs continuously 8)
Im getting around 70 - 71mb with my transcend 32gb 1000x, cant continuos 1880 though still :( BUT its much better than i was when i was using a 60mb write max card :)
Has the 4gb Split been taken away? im complaining at all! just i got a raw file on my card over 4gb n its not split :) sweet
Quote from: Doyle4 on July 03, 2013, 02:29:41 PM
Has the 4gb Split been taken away? im complaining at all! just i got a raw file on my card over 4gb n its not split :) sweet
how big is your file?
was 4.8gb :D
it was probably just 4,294,967,295 bytes. 5D2 is still split files as of jun 29 nb.
Ahhhh that makes sense! would be nice if Canon allowed ExFat on the mkii
Sandisk Extreme 60 MB/s 400x 64GB card.
I can do a little less than 55MB/s in raw video mode.
I don't know how you guys got that screen shot of your results, so here is the text from the bench.log file
ML v2.3.NEXT.2013Jun29.5D2212, 3ecd254bdba1+ (unified) tip
Mode: playback, Global Draw: ON
10312704 607
15885312 615
80896 149
8949760 546
28661760 594
16264192 595
24521728 600
16424960 593
13148160 583
15619072 582
1658880 516
21001216 464
8548352 251
19760128 356
5965824 188
24906752 417
13968384 269
16770048 385
4542464 168
13063168 363
33263616 433
30312448 353
16713728 319
3887104 137
so many days without updates ...
Quote from: Bradley on July 03, 2013, 03:47:12 PM
Sandisk Extreme 60 MB/s 400x 64GB card.
I can do a little less than 55MB/s in raw video mode.
I don't know how you guys got that screen shot of your results, so here is the text from the bench.log file
It's saved in the CF card, in the main folder.
So. Now i know why i can´t record with 70mb/s...
I have the Komputerbay 128GB card. With the AJA System Test i can only get around 67mb/s in writing ... looks like komputerbay can´t keep the 1000x speeds like other cards.
Quote from: chadsky on July 05, 2013, 08:14:54 AM
so many days without updates ...
Not at all.... check the change log, always work going on on Magic Lantern that you dont see ;)
Quote from: ch_d on July 05, 2013, 11:09:38 AM
So. Now i know why i can´t record with 70mb/s...
I have the Komputerbay 128GB card. With the AJA System Test i can only get around 67mb/s in writing ... looks like komputerbay can´t keep the 1000x speeds like other cards.
Fastest Komputerbay card is the 64gb apparently
Quote from: avasarin on July 05, 2013, 10:36:46 AM
It's saved in the CF card, in the main folder.
The benchmark saves it on the CF in the main folder? when I run the benchmark it only creates a text file, and the only way I know to take a screenshot is from the menus, so when I go to take a screenshot it removes the benchmark results off screen.
Also I was wrong about my CF card doing 55MB/s the Sandisk extreme 64GB 400x will do 57.2-57.4MB/s which is pretty good I think for a 400x card. I can run 1600x900 for about 6GB worth of footage before the buffer overfills. I'm quite pleased with that as I don't have moneys for 1000x card and 1600x900 looks pretty great.
Also, I don't know if this is a understood bug, but when my raw videos go over 4GB magic lantern splits the file and then creates these .rar files. I get an error on the original 4GB raw file about it not containing a footer and it won't work with the DNG creator. I also can't unrar the rar files either.
I'd love an option for it to just stop recording at 4GB until it is fixed because it basically makes any video that goes over 4GB unusable.
Using 6/29 build and an external monitor, crashed every time when trying to write with the external monitor attached. Attached crash logs for review
http://sdrv.ms/17XKStJ
Quote from: Bradley on July 05, 2013, 04:50:16 PM
Also, I don't know if this is a understood bug, but when my raw videos go over 4GB magic lantern splits the file and then creates these .rar files. I get an error on the original 4GB raw file about it not containing a footer and it won't work with the DNG creator. I also can't unrar the rar files either.
I'd love an option for it to just stop recording at 4GB until it is fixed because it basically makes any video that goes over 4GB unusable.
The file splitting is not a bug, once the 4 GB limit is reached it automatically starts recording to a new file then later on the files can be merged back into 1 file before exporting to dng's, the files must be merged back together as they are all incomplete on their own. They are not rar files by the way they just use the same file extensions that split rar files use, they are RAW files. All this info is on the first post in this topic but here is how you join the files.
QuoteJoining files
WIN
Start dialog: cmd
1. cd C:\Users\my_destination_folder
2. copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?
Quote from: dariSSight#1 on July 05, 2013, 06:55:48 PM
In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?
We will need confirmation from one of the dev's but I am almost postive the answer will be no. The 5d2 cpu is not fast enough to do any kind of compression/encoding and there is no known way to change the compressor from h264 which I believe is handled by the DIGIC chip. Right now the only options are h264 from canon or just straight copying the raw data directly off the sensor to a file, the cpu is not even fast enough to convert the data to 12 or 10 bit before writing which would be a huge breakthrough allowing a compromise between bit depth and resolution. 14 bit is nice but a bit of overkill at times.
Quote from: dariSSight#1 on July 05, 2013, 06:55:48 PM
In the same fashion of the native H.264 from canon, is there anyway way ML firmware could allow ProRes 4444 or ProRes 422?
ProRes is an Apple codec... no chance it will happen,
I kind of thought that would be the answer, so that's it. I think once ML run thorough test to every function we might have a good understanding to this Miracle Firmware Called Magic Lantern RAW. I would like to thank the Magic Lantern Team for this Cinematic Break Through, I'm sure you might have more in store with your BETA and I'm on pins and needles.
wtf is this :o Same results in video mode. Done after card format.
Komputerbay 64gb 1000x
(http://i.imgur.com/PMd2Szd.png)
Hi All :)
Just Got My New 64 GB Lexar 1000x Card today so i tested with A_D_ June 29 & 27 Hack built
I did 6 tries at full 64GB card record.
After about 3 Hours of testing, i have found that at 42 GB there is a problem writing to card.
I was going after a full stable Card record of 64 GBs .
1856x1004 @ 24p or 23.976p it was continuous until i hit the 42 GB barrier , at that point
It when from "continuous Recording" with very little buffering to heavy buffer "expected 77" @ 2.8MB/ss ?
Then stop recording @ 14,921 frames , 12,568, 9122, 14,171, 14,187,14,111
5 out of 6 tests stared to have problems @ about 42GB. ???
I also tried a Safe frame size that i know works.
1880x854 24p @70MB/s and it to had a problem at about 42 GB
but it did not stop recording , it displayed frames " 94 expected k" @ 5.9MB/ss ?
that continued to increase to "112 expected K" @ 15MB/ss
until 64 GB then stop, i'm still in the process of checking the 64GB file , will report later.
Plus all the over lays information was incorrect,
it displayed 59.5 GB remaining, when i just finish
14,000 Frames ? Time for recording displayed 21:12 Min. ?
I though it was a temperature issue but it never got over 65 degrees "C"
i would think that the 32 GB Card will not suffer from this but the 64 GB Card
may have a problem at lest on the Lexar 1000x 64GB card :(
On all of the tests except the 1880x854(70MB/s), the write speed to card was
no more then 75MB/s
I would recommend people Test your 64 GB Card and see if you truly
can record a Full card, even at smaller resolution.
I did this test on both june 27, 29 builts same problem with both.
Has anyone Done a 64 GB continuous Full card Record ??
Quote from: reddeercity on July 06, 2013, 07:04:38 AM
Hi All :)
Just Got My New 64 GB Lexar 1000x Card today so i tested with A_D_ June 29 & 27 Hack built
I did 6 tries at full 64GB card record.
After about 3 Hours of testing, i have found that at 42 GB there is a problem writing to card.
I was going after a full stable Card record of 64 GBs .
1856x1004 @ 24p or 23.976p it was continuous until i hit the 42 GB barrier , at that point
It when from "continuous Recording" with very little buffering to heavy buffer "expected 77" @ 2.8MB/ss ?
Then stop recording @ 14,921 frames , 12,568, 9122, 14,171, 14,187,14,111
5 out of 6 tests stared to have problems @ about 42GB. ???
I also tried a Safe frame size that i know works.
1880x854 24p @70MB/s and it to had a problem at about 42 GB
but it did not stop recording , it displayed frames " 94 expected k" @ 5.9MB/ss ?
that continued to increase to "112 expected K" @ 15MB/ss
until 64 GB then stop, i'm still in the process of checking the 64GB file , will report later.
Plus all the over lays information was incorrect,
it displayed 59.5 GB remaining, when i just finish
14,000 Frames ? Time for recording displayed 21:12 Min. ?
I though it was a temperature issue but it never got over 65 degrees "C"
i would think that the 32 GB Card will not suffer from this but the 64 GB Card
may have a problem at lest on the Lexar 1000x 64GB card :(
I would recommend people Test your 64 GB Card and see if you truly
can record a Full card, even at smaller resolution.
I did this test on both june 27, 29 builts same problem with both.
Has anyone Done a 64 GB continuous Full card Record ??
is your auto power off set to=OFF ?
Yes, Auto power is set to "off"
i also had my AC adapter on the Camera
If any one can record full 64 GB card you will see About 28,000 Fames
Edit: i did try a 500 MB Warm up file to start before i did the continuous record.
Quote from: reddeercity on July 06, 2013, 07:14:48 AM
Yes, Auto power is set to "off"
i also had my AC adapter on the Camera
If any one can record full 64 GB card you will see About 28,000 Fames
On the 5D2 1872 x 936 is the highest res that I tested to be continuous. Even if it would initially say to be "continuous ok" in higher resolutions, later on it will change.
For 16:9 AR its 1728 x 972. For now that's it, even with fast cards.
Quote from: ted ramasola on July 06, 2013, 07:30:43 AM
On the 5D2 1872 x 936 is the highest res that I tested to be continuous. Even if it would initially say to be "continuous ok" in higher resolutions, later on it will change.
For 16:9 AR its 1728 x 972. For now that's it, even with fast cards.
Ok,
my camera never when off "continuous ok" it always said "continuous ok"
But i understand what you are saying, :)
i have always had better numbers then what i have read in this forum.
i will try the 1728x972 AR and see if this problems is still there.
But in the Short term i can record 1856x1003 for 14,000 frame ! that's 9.7 Mins ;D
Update:
I just check the DNG's from the 64 GB full card record @ 1880x854 24p, 22,571 frames
Frame over ride on, small hack on , Photo small jpeg , ETTR = Off,
and i had the last 3 Images are corrupt, pink garbage frames
So i call that success ! with 22,568 Good frames 15.67 minutes on lexar 1000x 64GB card
If only i can get 1856x1003 to do 64 GBs (max is 42GB)
Quote from: reddeercity on July 06, 2013, 07:54:48 AM
Ok,
my camera never when off "continuous ok" it always said "continuous ok"
But i understand what you are saying, :)
i have always had better numbers then what i have read in this forum.
i will try the 1728x972 AR and see if this problems is still there.
But in the Short term i can record 1856x1003 for 14,000 frame ! that's 9.7 Mins ;D
Update:
I just check the DNG's from the 64 GB full card record @ 1880x854 24p, 22,571 frames
Frame over ride on, small hack on , Photo small jpeg , ETTR = Off,
and i had the last 3 Images are corrupt, pink garbage frames
So i call that success ! with 22,568 Good frames 15.67 minutes on lexar 1000x 64GB card
If only i can get 1856x1003 to do 64 GBs (max is 42GB)
Do I have this process theory right or wrong, Because of the line skipping process from the DiGiC chip we have been shorted 266 continuous pixel for every frame 40 from the 1920 width and 226 from the height. I'm sure I might have something wrong, I was just wondering what was your opinion on 1880x854 for the Mark II vs 1920x1080 for the Mark II?
Quote from: reddeercity on July 06, 2013, 07:04:38 AM
Has anyone Done a 64 GB continuous Full card Record ??
I just filled my 64GB Komputerbay and speed dropped from 68 MB/s continuous to 2.1Mb/s 110 expected at the 42 GB point. The buffer stayed the same at barely a bar. 1856 x 742 26531 frames. All I can offer is the 42GB point is around the time the tenth file is written?
I have done a full card record on the 32Gb Komputerbay 1000x
I know it's not reallly going to help you much but I didn't have any problems with that; apart from it was never able to write the file footer (because it filled the card) so I had to patch it. But it did indeed work. :-\
Quote from: Redrocks on July 06, 2013, 06:28:57 PM
I just filled my 64GB Komputerbay and speed dropped from 68 MB/s continuous to 2.1Mb/s 110 expected at the 42 GB point. The buffer stayed the same at barely a bar. 1856 x 742 26531 frames. All I can offer is the 42GB point is around the time the tenth file is written?
Hey Thanks i though i was the only 1 :)
i was wondering if you have tried 1856x1003 24 with you 64GB Komputerbay?
How many frames can you get ?
Best i can get is 14,921 with ETTR=Off
So 42 GB is a Barrier for 64 GB card with larger frame size.
Can only one explain? "2.1Mb/s 110 expected at the 42 GB point"
and it always happen @ "42GB" evey time
Quote from: dariSSight#1 on July 06, 2013, 01:50:00 PM
Do I have this process theory right or wrong, Because of the line skipping process from the DiGiC chip we have been shorted 266 continuous pixel for every frame 40 from the 1920 width and 226 from the height. I'm sure I might have something wrong, I was just wondering what was your opinion on 1880x854 for the Mark II vs 1920x1080 for the Mark II?
:)
On the 5D2 the Max-with from the sensor is 1880
Canon upscale the image to 1920 for h264 with software.
It really depends on what your Project calls for.
Being that the image is very scale able meaning , re-framing, punching-in.
I like to use Max amount of the sensor then crop out sides .
the other reason i like it is because of the reduce height for a more Film look & feel !
It also easier to Write to the card @ 68.5 MB/s
That's at lest in my case, I think if with can keep frame data close to the best Hexadecimal
it should write quicker, but i'm Not a programmer so that a guess.
But with 1856x1003 it very close to HD @ 1:85.1 AR
that would be the ticket, there again re-framing etc...
I will settle for 1856x1003 for HD Work & for Documentary
I would use 1880x854 or even 1880x940 if you can do it.
Stop thinking about line skipping and all the stuff, you will always have problems
with that line skipping for panning etc..
But think of you camera as a "Film camera" to capture Positive Film Stock (but More)
It's Not a Video Camera, because with are capturing Frames like "true Film" Stock
I personally turn off everything on the camera & use manual focus,
use proper exposing Technics, "Use Meter on camera" i don't use the "ETTR" function.
but i have a Variable ND and Stop it up or down for scene.
Could someone please explain clearly please how to join a split files on a mac please? been stuck over an hour now and getting no where :(
i have a .RAW and a .R00, iv seen command's on here but it doesn't say how to actually do it, iv tired draggin in the files to terminal and the folder that they are in and keep getting message "No directory found"
Cheers,
Quote from: Doyle4 on July 06, 2013, 10:16:45 PM
Could someone please explain clearly please how to join a split files on a mac please? been stuck over an hour now and getting no where :(
i have a .RAW and a .R00, iv seen command's on here but it doesn't say how to actually do it, iv tired draggin in the files to terminal and the folder that they are in and keep getting message "No directory found"
Cheers,
Post processing for mac links:
http://www.magiclantern.fm/forum/index.php?topic=6218.0
http://www.magiclantern.fm/forum/index.php?topic=5508.0
Quote from: ted ramasola on July 06, 2013, 10:29:31 PM
Post processing for mac links:
http://www.magiclantern.fm/forum/index.php?topic=6218.0
http://www.magiclantern.fm/forum/index.php?topic=5508.0
Cheers dude, RAW2DNG wont let me add the .R00 or .RAW still, get an error every time, i love RAW2DNG, but the terminal thing is a brain killer, would love to know how to merge them using terminal, not so keen on RAWmagic.
A quick compare :
Hope is useful !
Config : 5D mark II - 24-105mm - Komputerbay x1000 128Go & build 3ecd254bdba1
AUDIO AUDIO AUDIO!!!!!! WHAT HAPPEN YOU THE AUDIO??? haha Please someone help me!
Quote from: F.T.I. ARMY on July 06, 2013, 11:17:43 PM
AUDIO AUDIO AUDIO!!!!!! WHAT HAPPEN YOU THE AUDIO??? haha Please someone help me!
On the 5d2 it goes out of sync when used with raw video so its advised to record separately using external recorder.
BUT you can try your luck by switching it on VIA FPS over ride menu>Sound record>WAV ,, thats where they hid it.
I have tested it extensively and it will give you low performance with raw video and produce unpredictable results in sync.
Quote from: ted ramasola on July 06, 2013, 11:32:26 PM
On the 5d2 it goes out of sync when used with raw video so its advised to record separately using external recorder.
BUT you can try your luck by switching it on VIA FPS over ride menu>Sound record>WAV ,, thats where they hid it.
I have tested it extensively and it will give you low performance with raw video and produce unpredictable results in sync.
THANKS !
@ted ramasola
Could you write an example of what you would have to write in terminal to join the files please,
Iv seen various commands on here but they dont say what to put before or after like destination ect, iv tried RAWmagic and it works but i find them not as clean looking as RAW2DNG, and i like the ProRess Export with R2D, help would be amazing right now, i have a 6gb file that i cant get access too :(
Cheers
Hi, just to report 5D mark II, new 64gb 1000x LEXAR card and just 60MB/s. I was reporting my low recording speeds to devs and they pointed out the memory. Now I have 227 malloc memory and still no improvement in recording speed( it improved with 29.06 build and small hack ON but it is still 15MB/s behind others who reported speed around 75MB/s) . I also want to report crashes that occur very often with monitor plugged in and okii usb controller (I have crash logs but I do not know how to report it properly because the crash seems to appear accidently but it is memory involved) It was reported by the other 5D mark II users also. Hoping for help from 1% and ALEX who implemented memory improvement. You Guys are doing just amazing job!!! You need some kind off people empower Oscar!!! . Just a question... Is it possible that shutter count has something to do with the recording speed????
Quote from: Lukasz on July 07, 2013, 12:48:38 AM
Hi, just to report 5D mark II, new 64gb 1000x LEXAR card and just 60MB/s. I was reporting my low recording speeds to devs and they pointed out the memory. Now I have 227 malloc memory and still no improvement in recording speed( it improved with 29.06 build and small hack ON but it is still 15MB/s behind others who reported speed around 75MB/s) .
Hi :)
I just got my new Lexar 1000x 64 Gb card also, and there is slow write speeds by the Benchmark.
But when you record you should see about 70 to 75MB/s write speeds.
Have you done any recording tests ?
The page before i posted about my card & the fact i can get 1856x1003 24p for 10,000 frames
at a time, because at 42 GB the card stops recording.
No mater what frame size on 64GB card there is a issue at the 42GB Mark every time.
i get around this by recording only 10,000 frame or 30GB at a time to get my 14 Min. of Raw @1856x1003 24p
on the Lexar 1000x 64GB card
There is far from 42gb problem... The camera regardless of the settings: global draw OFF, manual lighting of live view, S picture size, etc... I saw it going crazy with stuff like monitor and OKII controller plugged in... And It is 60MB/s limited with 29.06 build regardless of settings of the camera... It is far from expected frames per second...
Quote from: reddeercity on July 06, 2013, 09:10:46 PM
:)
On the 5D2 the Max-with from the sensor is 1880
Canon upscale the image to 1920 for h264 with software.
It really depends on what your Project calls for.
Being that the image is very scale able meaning , re-framing, punching-in.
I like to use Max amount of the sensor then crop out sides .
the other reason i like it is because of the reduce height for a more Film look & feel !
It also easier to Write to the card @ 68.5 MB/s
That's at lest in my case, I think if with can keep frame data close to the best Hexadecimal
it should write quicker, but i'm Not a programmer so that a guess.
But with 1856x1003 it very close to HD @ 1:85.1 AR
that would be the ticket, there again re-framing etc...
I will settle for 1856x1003 for HD Work & for Documentary
I would use 1880x854 or even 1880x940 if you can do it.
Stop thinking about line skipping and all the stuff, you will always have problems
with that line skipping for panning etc..
But think of you camera as a "Film camera" to capture Positive Film Stock (but More)
It's Not a Video Camera, because with are capturing Frames like "true Film" Stock
I personally turn off everything on the camera & use manual focus,
use proper exposing Technics, "Use Meter on camera" i don't use the "ETTR" function.
but i have a Variable ND and Stop it up or down for scene.
I totally agree with your assessment, I film some quick shots of a creek behind my home area
I also Have Lexar 16gb 400x card, and it is limited with my camera to 45MB/s... !?!
Quote from: Lukasz on July 07, 2013, 03:28:05 AM
I also Have Lexar 16gb 400x card, and it is limited with my camera to 45MB/s... !?!
??? this puzzles me, for you should have no problems recording Raw.
I wounder, what are your setting ?
Maybe there is something no set right of over looked .
these are my setting : Canon Menu
photo=small jpeg
Auto power off=OFF
LCD Brightness=manual
Movie rec. size=1920x1080 24p
ML Raw record module from june29 from A_D_ Hack built (the one with the disclamer)
ETTR=Off
FPS override = set to exact 24
in the Raw Video tab
i set previews to Auto or Hacked
recording frame=White rect
Small hacks= On
I have notice that on my Lexar 1000x 64 GB card i had to Brake in the Card like a pair of shoes ;)
I did about 12 full card records before it started to write at the proper speed ,
and the other thing that you may try is to set warmup card
or just write 200 frame at lower resolution then Start the Main record .
I hope that helps :)
edit:What is the Max Frame size you can record?
Don't be to concerned about the benchmark read write test,
It's the Frame size you need be concerned about.
Quote from: Lukasz on July 07, 2013, 03:28:05 AM
I also Have Lexar 16gb 400x card, and it is limited with my camera to 45MB/s... !?!
400x is too slow.
Quote from: Doyle4 on July 06, 2013, 11:58:50 PM
@ted ramasola
Could you write an example of what you would have to write in terminal to join the files please,
Iv seen various commands on here but they dont say what to put before or after like destination ect, iv tried RAWmagic and it works but i find them not as clean looking as RAW2DNG, and i like the ProRess Export with R2D, help would be amazing right now, i have a 6gb file that i cant get access too :(
Cheers
I'm on PC so I use rawanizer or raw2cdng.
I suggest you post over at the POST PROCESS THREADS specific to MAC as the developers for the app check it often not here since this thread is mostly checked by raw_rec developers like a.d. 1% and a1ex.
I post my suggestions and bug reports over at the RAWANIZER or CDNG threads and the devs themselves reply.
Shot some very quick tests of my class with the 5D Mk2 (last 2 shots) and the 50D (first shot) - under horrific cheap fluoro lights. And it looks amazing - even before dodgy web compression. Shot 2 was a lens test to check focus while crash zooming...
Also learnt 2 good lessons - never have a battery less than 50% - weird flicker happens - even under tungsten bulbs. Lesson 2 - if the lcd viewfinder flickers when recording then the footage will flicker (even if your light flicker meter tell you otherwise) - Shot 1 has a very slight flicker and it gets sorted in shot 2 and 3 - by tweaking the exact FPS.
Amazing thank you to all the dev team!
http://vimeo.com/69735373
thanks
R
creativesunshine
Quote from: silvertonesx24 on July 05, 2013, 05:30:33 PM
Using 6/29 build and an external monitor, crashed every time when trying to write with the external monitor attached. Attached crash logs for review
http://sdrv.ms/17XKStJ
Hmm, didn't try it again, since I got THIS (http://www.magiclantern.fm/forum/index.php?topic=6432.0) problem with my Lilliput 667, too.
There's actually, obviously not much effort done to solve this problem - or I just can't see the solution.
Quote from: ted ramasola on July 07, 2013, 04:56:41 AM
I'm on PC so I use rawanizer or raw2cdng.
I suggest you post over at the POST PROCESS THREADS specific to MAC as the developers for the app check it often not here since this thread is mostly checked by raw_rec developers like a.d. 1% and a1ex.
I post my suggestions and bug reports over at the RAWANIZER or CDNG threads and the devs themselves reply.
No problem dude, ill be honest n say i posted here as it gets alot of attention where as other post's dont but will give it a shot as i still haven't solved it.
Quote from: reddeercity on July 07, 2013, 04:08:50 AM
??? this puzzles me, for you should have no problems recording Raw.
I wounder, what are your setting ?
Maybe there is something no set right of over looked .
these are my setting : Canon Menu
photo=small jpeg
Auto power off=OFF
LCD Brightness=manual
Movie rec. size=1920x1080 24p
ML Raw record module from june29 from A_D_ Hack built (the one with the disclamer)
ETTR=Off
FPS override = set to exact 24
in the Raw Video tab
i set previews to Auto or Hacked
recording frame=White rect
Small hacks= On
I have notice that on my Lexar 1000x 64 GB card i had to Brake in the Card like a pair of shoes ;)
I did about 12 full card records before it started to write at the proper speed ,
and the other thing that you may try is to set warmup card
or just write 200 frame at lower resolution then Start the Main record .
I hope that helps :)
edit:What is the Max Frame size you can record?
Don't be to concerned about the benchmark read write test,
It's the Frame size you need be concerned about.
Thanks for Your input. Max frame size is around 1880x800 as it records with speed close to 60MB/s.
What is more intresting regarding settings, I can turn on stuff like global draw, size of pictures to L, etc.(all the memory consuming settings) and the writing speed is also 59-60MB/s?!?
So should I download the official ML 2.3 release and then install the modules and auto exec from the zip in the bitbucket link? Or should I download a nightly version of ML?
Quote from: dariSSight#1 on July 07, 2013, 03:17:27 AM
I totally agree with your assessment, I film some quick shots of a creek behind my home area
Thanks :D
Tried to watch you video but, said its Private :(
hmmmm. I turned on separate wav recording in the fps override menu, however no sound files are being recorded. Anyone have any idea what is going on? Also in the audio menu in ML it says i have sound disabled in the canon menus even though it is not.
Sound is not recorded with forced FPS.
Quote from: mvejerslev on July 07, 2013, 09:53:50 PM
Sound is not recorded with forced FPS.
even with forced fps off it still doesnt make a file
Quote from: reddeercity on July 07, 2013, 08:29:49 PM
Thanks :D
Tried to watch you video but, said its Private :(
Sorry About that, I Fix it
Quote from: lagunak47 on July 07, 2013, 11:04:01 PM
even with forced fps off it still doesnt make a file
A1ex did mention here that due to its being out of sync that sound recording is removed. So I guess that switch no longer works.
that's probably the reason why thy "hid" that option deep in FPS sub menu.
You can read the tip when you select it that say, SOUND GOES OUT OF SYNC. SO IT HAS TO BE RECORDED SEPARATELY.
as far as im aware it only records a 5second tone, this to allow a separate recording device to sync later to the footage.
Quote from: Doyle4 on July 08, 2013, 12:38:17 AM
as far as im aware it only records a 5second tone, this to allow a separate recording device to sync later to the footage.
It doesn't "record" the tone/beep. It just makes a sound of a tone/beep about 2-3 frames after the recording starts. There is no recorded tone file to find in the card.
The sound recording option from FPS submenu is for H.264...
Quote from: a1ex on July 08, 2013, 06:18:46 AM
The sound recording option from FPS submenu is for H.264...
ahhh okay. thanks alex! so no sound recording during raw then?
Quote from: lagunak47 on July 08, 2013, 07:22:25 AM
ahhh okay. thanks alex! so no sound recording during raw then?
There should be in the Raw menu. Well at least on the 6D it is...
I prefer to enable only things that are working well ;)
Quote from: a1ex on July 08, 2013, 07:46:43 AM
I prefer to enable only things that are working well ;)
Have any idea why its not working well on the 5D2? Will there be a fix?
There are no cameras where it's working well (it goes out of sync in unpredictable ways). It's very hard to fix, we need to understand better the ASIF DMA.
Quote from: a1ex on July 08, 2013, 08:17:57 AM
There are no cameras where it's working well (it goes out of sync in unpredictable ways). It's very hard to fix, we need to understand better the ASIF DMA.
Wait a second, we're talking about the audio sync beep right? On the 6D it seems to be working fine. It's always consistent and turns on right as it starts filming.
Edit: Oh I see recording sound with raw.
Well who cares about onboard right? External audio solutions are where its at.
Audio sync beep is fine (+/- a few frames). Wav recording is not. There are a lot of reports that it goes out of sync.
Quote from: Doyle4 on July 05, 2013, 11:54:44 AM
Not at all.... check the change log, always work going on on Magic Lantern that you dont see ;)
Where is that change log?!!
Quote from: neopixel on July 08, 2013, 09:37:01 AM
Where is that change log?!!
Here you go dude
http://nanomad.magiclantern.fm/nightly/ChangeLog.txt
to sync sound i use an external Zoom Mic and an iPhone and my 5Dmkii of course :)
I start my camera phone and mic and press record, i shoot on the canon.... later i match the audio from mic with the iphone using plural eyes, this gives me a clean sync with the camera, and sync the footage to the canon... long way round but the clip from the iphone lets me visually see and help me better, say like clapping hands or clicking a finger.
What frames exactly are recorded while the tone is playing?
Would it be possible to put a blue dot on the video frames while the tone is playing to help sync? Some sort of video cue as to when the tone is playing.
Crazy idea, how about a tone that plays in morse code what number video it is. Kinda like how a clapper has scene/take numbers, just to give more information to help figure out what audio goes with what clip.
Hey guys, has anyone tested the HDMI monitoring for the Mark II? I see on the Mark 3 thread that the HDMI monitor mostly works.
But has anyone tried taping with the HDMI connected to an external monitor for the Mark 2? I've been shooting with the June 29th building and it's been great. I may want to shoot a job where I'll be renting a monitor, so I'm curious if anyone's tried that setup with the Mark 2.
Big thank you to the Magic Lantern team! Wonderful work here, guys. This is incredible.
-John
Quote from: Bradley on July 08, 2013, 04:01:37 PM
What frames exactly are recorded while the tone is playing?
Would it be possible to put a blue dot on the video frames while the tone is playing to help sync? Some sort of video cue as to when the tone is playing.
Crazy idea, how about a tone that plays in morse code what number video it is. Kinda like how a clapper has scene/take numbers, just to give more information to help figure out what audio goes with what clip.
Its not precise but its around 2-3 frames of video before the ramp of the tone waveform on your wav file begins. When I say wav file, its the one from your external audio recorder.
Quote from: johnha on July 08, 2013, 08:29:33 PM
Hey guys, has anyone tested the HDMI monitoring for the Mark II? I see on the Mark 3 thread that the HDMI monitor mostly works.
But has anyone tried taping with the HDMI connected to an external monitor for the Mark 2? I've been shooting with the June 29th building and it's been great. I may want to shoot a job where I'll be renting a monitor, so I'm curious if anyone's tried that setup with the Mark 2.
Big thank you to the Magic Lantern team! Wonderful work here, guys. This is incredible.
-John
Yes it works on 5d2.
1. Its better than h264 since it does not down sample to 480 when you record but stays in HD.
2. You have to turn off the rectangular crop marks by choosing ML grayscale in raw video>preview since the crop marks are off centered on your external monitor. You will have to mask the monitor for your aspect ratios the old fashioned way, also do not playback or review recorded footage with external monito as it will lock up your camera. You'll have to remove battery to trocover.
I posted this earlier but got no response, is there some reason why the maximum vertical resolution in crop mode is only 1076? I can record up to 1250 in regular mode. Thanks.
Not getting any EXIF data on 7-7 build with Raw2DNG Batchelor ver 2.3... Goes for both x5 and normal RAW video. Anyone?
Quote from: Doyle4 on July 08, 2013, 12:29:37 PM
Here you go dude
http://nanomad.magiclantern.fm/nightly/ChangeLog.txt
Thanks a lot Doyle4 !
Been running some tests at 1880x1058 (actual resolution, at least in OSX FINDER: 1876x1054), extracted cDNG via RawMagic and transcoded and uprezzed to 1920x1080 through Resolve Lite.
I just realized however that x5 CROP MODE records as 29.97 instead of 23.976. Is there currently a setting that allows me to shoot in crop mode 23.976?
Crop mode is great by the way. Need to make sure it's extra stable but that additional reach and acquired detail is awesome.
I'm using Sandisk 32GB 90MB/s CF cards by the way, although it's labeled UDMA 7 and can average about 10secs per clip but for now that length is fine for testing. I can only get continuous recording at 2.50:1 aspect at 1880 wide.
Quote from: soulshooter on July 09, 2013, 08:00:51 AM
Been running some tests at 1880x1058 (actual resolution, at least in OSX FINDER: 1876x1054), extracted cDNG via RawMagic and transcoded and uprezzed to 1920x1080 through Resolve Lite.
I just realized however that x5 CROP MODE records as 29.97 instead of 23.976. Is there currently a setting that allows me to shoot in crop mode 23.976?
try FPS over ride.
Could I make the case for the return of the old buffer graphic? It may have been a little primitive but it was very easy to see at a glance how much you had left. The new graphic, though actually giving more info, is harder/slower to read and I find it quite distracting during a shot.
In fact, with the 'expected frames' pretty accurate, do we need a buffer graphic at all? If this is just a diagnostic tool for developers that will be disabled on the stable distributions, could we perhaps have an off switch now?
Here's a little film I've been working on, using Magic Lantern RAW on 5D2 (and a little 5D3) and a load of timelapse.
Thanks to everyone on here, especially a1ex and a.d. Without MLRAW it would have all been timelapse.
Quote from: andyshon on July 09, 2013, 11:18:07 AM
Could I make the case for the return of the old buffer graphic? It may have been a little primitive but it was very easy to see at a glance how much you had left. The new graphic, though actually giving more info, is harder/slower to read and I find it quite distracting during a shot.
In fact, with the 'expected frames' pretty accurate, do we need a buffer graphic at all? If this is just a diagnostic tool for developers that will be disabled on the stable distributions, could we perhaps have an off switch now?
I know what you mean but the buffer graphic has helped me alot, its let me know when my cards about to stop and it prepares me to get ready to stop and start again :)
Super nice video too btw too
Quote from: andyshon on July 09, 2013, 01:50:33 PM
Here's a little film I've been working on, using Magic Lantern RAW on 5D2 (and a little 5D3) and a load of timelapse.
Thanks to everyone on here, especially a1ex and a.d. Without MLRAW it would have all been timelapse.
This video Kicks Ass I would like to know some of your setting like, for the TimeLapse what fps and iso setting gave you the most smooth presentation. Also what were your settings for some of those night scene, because there is no grain or hard color blending. I have a 5D 2, What parts did you use the 5D 3 for and why?
Quote from: ted ramasola on July 08, 2013, 10:23:03 PM
Yes it [external Monitor via HDMI] works on 5d2.
1. Its better than h264 since it does not down sample to 480 when you record but stays in HD.
2. You have to turn off the rectangular crop marks by choosing ML grayscale in raw video>preview since the crop marks are off centered on your external monitor. You will have to mask the monitor for your aspect ratios the old fashioned way, also do not playback or review recorded footage with external monito as it will lock up your camera. You'll have to remove battery to trocover.
To Point 1, I agree.
But not with the second point. The white frame is (in my case) nearly correct.
It's just moved a bit to the left (out of the monitor) and comes back in from the right. So only the left and right borders are wrong, but they would align with the monitor frame anyway, so I can confidently ignore them.
The upper and lover borders on the other hand are obviously important (since I record 2.35). Except a little discontinuaton in the line due to the shift, they match.
Quote from: andyshon on July 09, 2013, 01:50:33 PM
Here's a little film I've been working on, using Magic Lantern RAW on 5D2 (and a little 5D3) and a load of timelapse.
Thanks to everyone on here, especially a1ex and a.d. Without MLRAW it would have all been timelapse.
Lovely work and a fine soundtrack.
Simple help required:
First off I just installed version 2.3 of ML. I then installed the newest June 29 build off of the bitbucket repository.
Everything works fine except 2 problems
1)when Im in live view and hit set to record, the first set starts recording h264. Then I hit the set button again. This time it stops h264 and starts RAW. Shouldnt ML disable h264?
2)I can't get the RAW video menu to highlight as if it's on. I'm in live view I don't know what could be the problem... Because of this I can't change the resolution or the aspect ratio.
Quote from: guentergunter on July 09, 2013, 08:34:48 PM
To Point 1, I agree.
But not with the second point. The white frame is (in my case) nearly correct.
It's just moved a bit to the left (out of the monitor) and comes back in from the right. So only the left and right borders are wrong, but they would align with the monitor frame anyway, so I can confidently ignore them.
The upper and lover borders on the other hand are obviously important (since I record 2.35). Except a little discontinuaton in the line due to the shift, they match.
Based on my monitor and with others the white rec is off centered to the left and also upwards so this CANNOT BE RELIED ON and also distracting. Both vertical and horizontal centering is off.
so how do i get accurate framing for 5x crop on the mark ii?
Quote from: lagunak47 on July 10, 2013, 04:34:49 AM
so how do i get accurate framing for 5x crop on the mark ii?
For now use the LCD on your 5d2 to get proper framing in 3x crop mode(5x magnify) and set preview to either ; auto or ML grayscale. I suggest using auto as its more convenient when you shift back to 1x mode.
added:
Also, while framing using auto is accurate, it is in grayscale and slightly pixelized and does not refresh in real time and this is so only when in preview/standby mode, upon start of recording the screen will revert to normal canon 5x magnification and real time refresh, AND the framing is slightly off.
So, with this handicap, I think this is useful only when the camera is locked down, and the subject does not move about.
You frame the subject first, then press record.
Quote from: ted ramasola on July 10, 2013, 04:47:38 AM
For now use the LCD on your 5d2 to get proper framing in 3x crop mode(5x magnify) and set preview to either ; auto or ML grayscale. I suggest using auto as its more convenient when you shift back to 1x mode.
added:
Also, while framing using auto is accurate, it is in grayscale and slightly pixelized and does not refresh in real time and this is so only when in preview/standby mode, upon start of recording the screen will revert to normal canon 5x magnification and real time refresh, AND the framing is slightly off.
So, with this handicap, I think this is useful only when the camera is locked down, and the subject does not move about.
You frame the subject first, then press record.
okay, thought i was doing something wrong but thats just how it is for now. I was going to buy a blackmagic pocket cinema camera and rig it out with 16mm lenses but if the raw hack progresses enough i might just stick with the trusty old 5d=]
here's the latest thing I've shot. Testing record time/resolve workflow/noise reduction/stabilization etc.
Is there a way to turn those info off and get a clean screen on raw recording? It's hard to frame when covered with the text :-\
(http://i42.tinypic.com/2eqf7te.jpg)
@Euan - Thanks man
@dariSSight - The frame rates in this vary from sync speed down to a shot every 30 secs, and ISOs 100 up to 3200. Horses for courses really. Night scenes were often captured at 3200 ISO, and little or no noise reduction was used in those shots as it created artefacts. But they were captured at least 4K, so noise is partially averaged out at 1080p. And onlining uncompressed 12 bit has kept banding at bay until the very end. The 5D3 was hired in as a spare body for a commission, so I thought I'd give it a go.
What is the maximum resolution in crop mode for the 5D2? I've read that it's 2144x1076, but is it possible to go any higher when using FPS override at 1 fps (e.g. for time lapse)?
FYI, FPS override changes the number of images per second, not the resolution.
That would be an incredible feature if it could be done? Wouldn't that also give you finer control over exposure time, and potentially smoother ramping. Not to mention giving the mechanical shutter a rest.
There is zero flicker with current ramping method if you use a good raw processor.
Quote from: a1ex on July 10, 2013, 05:13:43 PM
FYI, FPS override changes the number of images per second, not the resolution.
Yes, I understand. I guess my last post wasn't clear. By shooting at a lower FPS, I meant that the write speed should not be an issue.
I think I found an answer here (http://www.magiclantern.fm/forum/index.php?topic=6451.0). It looks like 2144x1076 may be the maximum live view resolution on the 5D2, whereas the 5D3 is capable of 3.5K.
I've always found that third stop jumps need more than just exposure adjustment. It is possible so long as there's no clipping, one big advantage of ETTR is fine control over this, but I have to tweak the contrast too to get a unable shot, and I've not found anything that can automate this.
If we can capture 2144x1076 25 times a sec, and we can dolly this around with digital dolly, then in theory it would be possible to capture the whole raw frame at speeds like 1fps, but with some very odd shutter effects. If you could minimise these and combine it with fine exposure control and ETTR, you'd have a unique tool for timelapse. The 5D3 might be even more impressive!
I'm waiting everyday for new updates!
The last one performed superbly, 1880x800p25 continuous with Sandisk Extreme Pro 90MB/s CF.
GR8T WORK guys!!
Does anyone know how to create that "RED" camera look with this 5DmkII RAW files? I tried so many times to achieve the 'smooth gradation Dynamic Range, bronze-y skin tones' to no pleasing result.. Must be me, lacking on the coloring technique :(
The dynamic range should be on par with RED doesn't it, is there other factor that makes it looks special such as resolution, etc?
I believe this camera could cure zombies!
QuoteIf we can capture 2144x1076 25 times a sec, and we can dolly this around with digital dolly, then in theory it would be possible to capture the whole raw frame at speeds like 1fps, but with some very odd shutter effects. If you could minimise these and combine it with fine exposure control and ETTR, you'd have a unique tool for timelapse.
Yeah. Or you could record at full 21 MP resolution and dolly in the NLE. Probably easier :-)
Umm... Why, even in crop mode, can't we choose over 1076 for vertical resolution? Even in 1x mode it should be able to use 1248.
Quote from: lagunak47 on July 10, 2013, 09:21:10 AM
here's the latest thing I've shot. Testing record time/resolve workflow/noise reduction/stabilization etc.
I don't understand, the hills are actually on fire in Las Vegas? Or is it just the sun's light illuminating the dust? Also what resolution was this shot in?"
Quote from: xNiNELiVES on July 11, 2013, 02:11:44 AM
I don't understand, the hills are actually on fire in Las Vegas? Or is it just the sun's light illuminating the dust?
no they're on fire. might go shoot something closer to it for a feature today.
Quote from: lagunak47 on July 11, 2013, 02:16:17 AM
no they're on fire. might go shoot something closer to it for a feature today.
How is dirt flammable?! What an amazing thing to see!
I wish I was at Vegas to see such a thing!
Quote from: andyshon on July 09, 2013, 01:50:33 PM
Here's a little film I've been working on, using Magic Lantern RAW on 5D2 (and a little 5D3) and a load of timelapse.
Thanks to everyone on here, especially a1ex and a.d. Without MLRAW it would have all been timelapse.
What slider did you use for the time lapses? Is that what its called? I'm specifically interested what the tool was in the star time-lapse.
To the developers:
Why, in the built in file browser can I see hidden files such as a trash folder? On ML on the 6D this doesn't occur.
Using latest version.
Hey guys, forgive me if this is the wrong place to post this, but I really am not sure where I would go to inquire about this subject. I cant seem to process any of my raw files over 4 gigs. Any help on this matter, or directing me on where I'd find the answer to this issue would be awesome. Thanks so much, this community is amazing!
Quote from: gentlemanbroncos on July 11, 2013, 08:18:15 AM
Hey guys, forgive me if this is the wrong place to post this, but I really am not sure where I would go to inquire about this subject. I cant seem to process any of my raw files over 4 gigs. Any help on this matter, or directing me on where I'd find the answer to this issue would be awesome. Thanks so much, this community is amazing!
Try raw2cdng
Works flawlessly for me.
Quote from: audyerel on July 10, 2013, 06:13:39 PM
I'm waiting everyday for new updates!
The last one performed superbly, 1880x800p25 continuous with Sandisk Extreme Pro 90MB/s CF.
GR8T WORK guys!!
Does anyone know how to create that "RED" camera look with this 5DmkII RAW files? I tried so many times to achieve the 'smooth gradation Dynamic Range, bronze-y skin tones' to no pleasing result.. Must be me, lacking on the coloring technique :(
The dynamic range should be on par with RED doesn't it, is there other factor that makes it looks special such as resolution, etc?
I believe this camera could cure zombies!
Use resolve.
And start with redlog film or bmd film.
Properly white balance as well as the rgb parades. Once color correction is done, now the grading begins.Adjust contrast using the waveform monitor.
Use nodes to single out all skin and adjust grading separately.
Sorry for the Newbie post, been through and through, but maybe have missed this.
1. Are new builds for the 5d2 no longer being posted here? 29 Jun seems to be the last.
2. If so, should we be using the regular Nightly builds (for raw rec on 5d2)?
Having a great time with ML and kudos to those who have been doing the work and supporting these forums.
Nelson
Quote from: loconetter on July 11, 2013, 05:39:58 PM
Sorry for the Newbie post, been through and through, but maybe have missed this.
1. Are new builds for the 5d2 no longer being posted here? 29 Jun seems to be the last.
2. If so, should we be using the regular Nightly builds (for raw rec on 5d2)?
Having a great time with ML and kudos to those who have been doing the work and supporting these forums.
Nelson
1. That would depend on a.d. if he will still include his own personal flavors to the nightly builds, I personally still use his jun 29 compile due to the inclusion of black border frame and less obtrusive buffer display when recording.
2. The nightly builds contain the "official" rep that is recommended for use by a1ex, it also contains the raw-rec modules now, so you can use it now.
I've tested it and its ok, though as I've mentioned I still use a.d. jun 29 build due to my personal preference for a less obtrusive display.
I do hope a less obtrusive display will be implemented in the official repo, but I think since we are still in testing phase some displays are still necessary for debugging/troubleshooting purposes.
a.d.'s builds can be found here
http://www.magiclantern.fm/forum/index.php?topic=6362.msg50149#msg50149
latest one is 7/11
Quote from: loconetter on July 11, 2013, 05:39:58 PM
Sorry for the Newbie post, been through and through, but maybe have missed this.
1. Are new builds for the 5d2 no longer being posted here? 29 Jun seems to be the last.
2. If so, should we be using the regular Nightly builds (for raw rec on 5d2)?
Having a great time with ML and kudos to those who have been doing the work and supporting these forums.
Nelson
Theres been an update 25mins ago, were now onto July 11th Build :) gunna check this one out now.
I like the Hold in the Joystick to get to ML, never noticed this unless it's not new?
Thanks, am trying the new AD build now.
Cheers!
Nelson
Quote from: silvertonesx24 on July 11, 2013, 08:48:29 PM
a.d.'s builds can be found here
http://www.magiclantern.fm/forum/index.php?topic=6362.msg50149#msg50149
latest one is 7/11
thank you for the link!
It seems to have given me 60 more frames. From 179 to 240 or so. Maybe it's because I just enabled the larger buffer hack by switching picture quality to jpeg.
@a.d. Cheers for the switch to turn the buffer display off. I couldn't stop watching it. Kept cocking me shots up.
Quote from: ted ramasola on July 11, 2013, 10:18:16 PM
thank you for the link!
What does Raw Settings refresh in zoom mode do different then before?
The Refactoring DxO dynamic range sounds like an option other then using HDR Video, am I correct?
Here's something I shot for a client on Monday. After that experience, I realize the post-production to use raw for something short like this is about an additional day.
This was mostly shot at ISO1600 and 3200. The dog in sun was shot at ISO100. June 29th build.
@nightly builds
If you guy focus on RAW video, it's not bad to understand the changelog. The Code of the RAW don't change since the last 2 weeks until yesterday.
@andyshon
you are welcome.
@dariSSight
... for example refresh from 5x to 10x
Refractoring ... the function is the same, but for the future implementation ... ISO in RAW.
@johnha
I like it.
What is the realistic projection of resolution for the mark ii and iii? Will 3.5k/4k be possible? When? I know I'm asking a lot. But, it will affect a very present purchase on production decision. Great work Guys! Images and coding are beautiful!
I must have missed something. The newest RAw2Dng is no longer giving me a Apple prores 4444. Any one know why?
I take that back. It will not Give me a prores at 1880x 752 694 frames. any answers? thanks?
Yeah actually the newest version gives me 14 more frames from 179 to 193.
Using a shitty lexar 300x.
Hello All :)
Just finish test the July 11 built
And i'm puzzled ??? i have slow write speed write this
built then the june 29 built !
July-11 Built
1856x1003 23.976p 14,306 Frames @ 75.0MB/s :)
1856x1003 24 p - 6989,7511, 11,784 frames @ 74.9MB/s :(
June-29 Built
1856x1003 23.976p 14,228 @ 75MB/s
1856x1003 24 p 14,160 @ 74.9 MB/s
All tests on Lexar 1000x 64 Card
So i will go back to the June 29 Built
it look like it has better stable speeds @ 1856x1003 at least for 24p
:)
Update: July-11Built -It looks like the problem is with the 64GB Card.
i just tried 1856x1003 in 24p & 23.976p on Lexar 1000x 32GB card
i Get a full card record -9800 frames @ 74.8MB/s = 32GB
i wounder if theirs a problem writing to larger capacity Cards
at bigger frame sizes ?
at the 42 GB mark i always have problems.
So stay on the newest build?
Quote from: F.T.I. ARMY on July 13, 2013, 02:11:52 AM
I take that back. It will not Give me a prores at 1880x 752 694 frames. any answers? thanks?
If you are using RAW2DNG on mac, open up the program, then you need to
DRAG RAW2DNG from Applications to RAW2DNG drop it in and it will ask you if you would like ProRes output. Hope this helps.
Quote from: estondiaz on July 13, 2013, 02:00:11 AM
What is the realistic projection of resolution for the mark ii and iii? Will 3.5k/4k be possible? When? I know I'm asking a lot. But, it will affect a very present purchase on production decision. Great work Guys! Images and coding are beautiful!
Please do not ask this...
Its been covered
MANY of times..... simple answer
no, you are lucky that someone has replied to this.
When 4K is possible... and i say
When, Magic Lantern will also allow you to connect a nikon lens without an adapter...cool huh? :P
As you are new... go here... http://www.magiclantern.fm/forum/index.php?topic=6518.0
Cool. Read that whole other forum. Helps understanding a bit from the coding side.
https://vimeo.com/70244910
shot with the 29th June build in 1728X972 with a Lexar 1000X 32gb Card and a Sandisk Extreme 600X 16gb Card. I could shoot continuous on the Lexar and got 310 - 340 frames on the Sandisk - long enough for a quick shot and I actually liked the limitation because it forces you to think fast.
Sound is H4N/sennheisser me66 + G3 and lav.
I really like the interface of Adobe Camera Raw in After Effects and the import is lighting fast. I resized to 1920X1080 and exported to Cineform .avis to edit in Premiere. Once the AE Comps were set up - 1 for each shot - it was easy to re-import the DNG's if I wanted to make an adjustment - then just export again.
As for storage, I can see it being an issue on larger projects - especially if there is the requirement of storing the raw files.
Question: should you save the DNGs and delete the .RAW files which come directly off the card? I don't see any point holding on to them once converted.
I tried converting directly to Cineform with Rawanizer and found the files just no fun to work with - ie. not like the easy intuitive ACR interface. I also felt like the Cineform files lost a whole lot of image depth in comparison to the DNG's - is that just my inability to use other AE tools for image editing?
Anyway, once the sharpness, highlights, shadows, contrast etc. are set I don't see any reason not to down-convert most footage to Cineform to edit and then to store as most of the major changes which would be effected by bit depth have already been done. Of course on a commercial project it would be important to save your raw data for a while.
Anyway, I don't see myself shooting much in the future which isn't raw.
Now I want a mark iii BUT I have to say another huge thank you to the ML crew for making my 5d mark ii into a much, much more powerful tool.
double post. Sorry.
I did just receive a Komputerbay 64gb card today. The benchmark test looks good.
I get his when im trying to get a Prores out of the raw2dng
Done. To convert to jpg, you can try: ufraw-batch --out-type=jpg *.dng To get a mjpeg video: ffmpeg -i %6d.jpg -vcodec mjpeg -qscale 1 video.avi
why wont it give me a prores file? it will on the 1280x720 but not on the 1880x752?
Quote from: Ethan_Reitz on July 13, 2013, 11:12:32 PM
https://vimeo.com/70244910
shot with the 29th June build in 1728X972 with a Lexar 1000X 32gb Card and a Sandisk Extreme 600X 16gb Card. I could shoot continuous on the Lexar and got 310 - 340 frames on the Sandisk - long enough for a quick shot and I actually liked the limitation because it forces you to think fast.
Sound is H4N/sennheisser me66 + G3 and lav.
I really like the interface of Adobe Camera Raw in After Effects and the import is lighting fast. I resized to 1920X1080 and exported to Cineform .avis to edit in Premiere. Once the AE Comps were set up - 1 for each shot - it was easy to re-import the DNG's if I wanted to make an adjustment - then just export again.
As for storage, I can see it being an issue on larger projects - especially if there is the requirement of storing the raw files.
Question: should you save the DNGs and delete the .RAW files which come directly off the card? I don't see any point holding on to them once converted.
I tried converting directly to Cineform with Rawanizer and found the files just no fun to work with - ie. not like the easy intuitive ACR interface. I also felt like the Cineform files lost a whole lot of image depth in comparison to the DNG's - is that just my inability to use other AE tools for image editing?
Anyway, once the sharpness, highlights, shadows, contrast etc. are set I don't see any reason not to down-convert most footage to Cineform to edit and then to store as most of the major changes which would be effected by bit depth have already been done. Of course on a commercial project it would be important to save your raw data for a while.
Anyway, I don't see myself shooting much in the future which isn't raw.
Now I want a mark iii BUT I have to say another huge thank you to the ML crew for making my 5d mark ii into a much, much more powerful tool.
You're getting bad frames with that lexar. You should be continuous @ 1880x800+
Quote from: Ethan_Reitz on July 13, 2013, 11:12:32 PM
Question: should you save the DNGs and delete the .RAW files which come directly off the card? I don't see any point holding on to them once converted.
It depends on your needs, but any footage that is valuable to you is more valuable in its original form. I got an answer to a related question here:
http://www.magiclantern.fm/forum/index.php?topic=6731.msg56002#msg56002
I can't speak to Cineform, but Resolve round tripping is working great for me. I was very comfy with AE / PP / SG before RAW, but found the Adobe workflow to be sluggish and counterproductive in that I was faced with grading decisions / opportunities before I'd cut a single shot and if I really need ACR, I can always introduce that after I have gotten a feel for the edit (quickly) using Resolve proxies. I also like the limitations of the higher ratios and the way they foster discipline. If I know I will only need a certain length shot, I select a ratio that can just about give me that knowing I will crop to a lower ratio anyway, whilst having room to later reframe. Liked your vid, btw.
Quote from: xNiNELiVES on July 14, 2013, 12:46:33 AM
You're getting bad frames with that lexar. You should be continuous @ 1880x800+
He's shooting in 16:9 which is limited to 1728 for continuous right now.
Quote from: Redrocks on July 14, 2013, 01:07:23 AM
He's shooting in 16:9 which is limited to 1728 for continuous right now.
how? Just a few posts above ours a guy @1856x1003 gets "continuous ok" until the 42gb mark, a glitch.
1880x800 is only 60.1mb/s. We with top end cards we get 75mb/s. 1880x1003 is 76.4 mb/s ...
Edit: nvm I get it he's filming 16:9 only. My bad.
@xNiNELLiVES You're right - I could shoot higher res and then upscale inside a 16:9 project which would also give a little room for re-framing. Between filling up the 32gb lexar and offloading the files I would fill up a 16gb sandisk - I wanted the footage to match and I got a little over 300 frames at that res, which was fine with me so that's the thinking there.
@Redrocks Thanks for the tips and the link. I don't have Resolve and it looks like a fairly big learning curve. I know the AE workflow isn't optimum but it feels creatively intuitive at the moment you are playing with the light in terms of highlight and shadow. For a larger project it would definitely be problematic.
Here's the benchmark for the 600x 16gb sandisk: http://www.flickr.com/photos/79873293@N03/9284673262/
And here benchmark for the 1000X 64gb komputerbay: http://www.flickr.com/photos/79873293@N03/9281892929/
I couldn't figure out how to get a clear screen for the 16gb benchmark and for the second it doesn't seem to be in film mode. Hm. Well, if I should do them again for anyone, just let me know. Btw. the komputerbay card is brand new and completely unused.
Quote from: Ethan_Reitz on July 13, 2013, 11:12:32 PM
https://vimeo.com/70244910
shot with the 29th June build in 1728X972 with a Lexar 1000X 32gb Card and a Sandisk Extreme 600X 16gb Card. I could shoot continuous on the Lexar and got 310 - 340 frames on the Sandisk - long enough for a quick shot and I actually liked the limitation because it forces you to think fast.
Sound is H4N/sennheisser me66 + G3 and lav.
Nice Clip! I really like it. Remembers me to my Berlin trip last summer ;-)
Just a question: Do you own a VAF (Video Aliasing Filter) for your 5D?
Quote from: Redrocks on July 14, 2013, 01:01:09 AM
It depends on your needs, but any footage that is valuable to you is more valuable in its original form. I got an answer to a related question here:
http://www.magiclantern.fm/forum/index.php?topic=6731.msg56002#msg56002
I can't speak to Cineform, but Resolve round tripping is working great for me. I was very comfy with AE / PP / SG before RAW, but found the Adobe workflow to be sluggish and counterproductive in that I was faced with grading decisions / opportunities before I'd cut a single shot and if I really need ACR, I can always introduce that after I have gotten a feel for the edit (quickly) using Resolve proxies. I also like the limitations of the higher ratios and the way they foster discipline. If I know I will only need a certain length shot, I select a ratio that can just about give me that knowing I will crop to a lower ratio anyway, whilst having room to later reframe. Liked your vid, btw.
Can you explain how youre using acr in your workflow with resolve?
My current wworkflow is raw>>>raw2cdng>>>resolve>>>premiere cc (via proxies)>>>and back to resolve for final grading and render.
I'd just like to introduce acr before cutting
@guentergunter Thanks!
A VAF is on my list but for now I just try and avoid surfaces which cause the nastiest antialiasing/moire, keep my camera moves and my shutter speeds slow. I would love to try out a VAF but the thing that I found most useful which I bought lately was a variable ND from lightcraft - motion blur seems to negate a lot of choppy aliasing artifacts.
@Ethan I hadn't used Resolve till a few weeks ago and I'm far from an expert, but Color Grading Central and AETUTS have some excellent Resolve tutorials. I'd love to see ACR enabled in Premiere and find it strange that the company who created DNG don't fully support it. Until then it's horses for courses and I would advise anyone to familiarize themselves with all of the workflow options.
@Vikado It's a mixture of round tripping and dynamic link. Export your XML to Resolve and if you have any problems you need ACR for, you can go back to PP and dynamic link to AE, do your stuff then render that out and import the results to Resolve.
My VAF arrived last week and I love it. Will up some comparisons tomorrow.
https://vimeo.com/67970827
THIS WORK FLOW IS GREAT, AND WORKS PERFECT WITH THE MARK II DNG FILES.
Quote from: Redrocks on July 14, 2013, 11:47:05 PM
@Ethan I hadn't used Resolve till a few weeks ago and I'm far from an expert, but Color Grading Central and AETUTS have some excellent Resolve tutorials. I'd love to see ACR enabled in Premiere and find it strange that the company who created DNG don't fully support it. Until then it's horses for courses and I would advise anyone to familiarize themselves with all of the workflow options.
@Vikado It's a mixture of round tripping and dynamic link. Export your XML to Resolve and if you have any problems you need ACR for, you can go back to PP and dynamic link to AE, do your stuff then render that out and import the results to Resolve.
My VAF arrived last week and I love it. Will up some comparisons tomorrow.
What do you mean, I load my DNG's into After effects just fine(not cinema DNG's) and am able to pull up ACR any time I want to as well.
@Redrocks looking forward to that VAF comparison. ACR in Premiere would definitely be good.
@F.T.I. ARMY yeah - that workflow looks straightforward and the result is very good. I'll have to give it a try.
I have to admit, I know very little about coloring and I go for some pretty unsubtle choices. Those Alexa like skin tones look very good and I can really see the appeal in it.
If you are interested in VAF - you can also check VAF-6D threads, I believe that the results would be the same.
BTW: the filter is great, i see huge improvement in picture quality so if you cannot switch to 5D3 the VAF would be a very nice improvement.
Quote from: aaphotog on July 15, 2013, 05:01:03 AM
What do you mean, I load my DNG's into After effects just fine(not cinema DNG's) and am able to pull up ACR any time I want to as well.
AE has realtime playback? Correcting 100's of clips isn't a chore? Sure you can do it in AE, I'm saying the process is inefficient is all.
re: AE - yup. Inefficient for sure. You grade sequences from your first frame and if you are doing run and gun and your camera is pointed at the ground you'll probably do it over later. Also - unless there's another way to do it - each sequence requires a separate Comp.
And on my machine forget realtime playback, I don't playback at all. Just load, adjust ACR and export Cineform AVIs to edit in PP.
You can use Bridge to open all frames within a clip at once, but you still have to reopen it to make further tweaks. Everyone has their own way, I just don't like the idea of grading too much before picture lock and prefer to be working with RAW footage after that.
I've got a small render farm headed up by a hex core with 64GB of RAM and every AE correction still requires rendering, whereas Resolve gives me real time playback of my whole project. The ability to add more GPU's is interesting too.
Quote from: Ethan_Reitz on July 15, 2013, 08:24:16 AM
@Redrocks looking forward to that VAF comparison. ACR in Premiere would definitely be good.
If that's what you're looking for:
http://vimeo.com/69350650
Ted Ramasola also posted tests, mine are cityscapes with lots of sharp edges and patterns that normally destroy RAW shots. A VAF pays for itself the first time you use it, IMHO.
http://www.youtube.com/watch?v=eeA-siZRE3A&feature=player_embedded
@all WINDOWS user
Sorry Guys! Please redownload the today release of raw2dng.exe! During cleaning up the code I forgot to add the Camera Tag.
@F.T.I. ARMY
Another Command Line Freak :D
I recommend dcraw (http://www.cybercom.net/~dcoffin/dcraw/) instead of ufraw-batch - it seems to be a lot faster on OSX. ffmpeg suports image2pipe, on the fly rendering, however if you want to render to ProRes 444. There's a bug in ffmpeg prores_kostya profile: The export file is being detected by Quicktime as ProRes 422, therefore I use ffmbc (https://code.google.com/p/ffmbc/) instead.
@Ethan_Reitz
It depends on your computer, but ...
After Effects supports realtime RAM previews playback + multi Core Rendering since CS5
http://forums.adobe.com/thread/734343
http://www.peachpit.com/podcasts/episode.aspx?e=7b2f2790-ea34-4adc-add2-487e40d40d6f
Quote from: Redrocks on July 15, 2013, 01:57:30 PM
Ted Ramasola also posted tests, mine are cityscapes with lots of sharp edges and patterns that normally destroy RAW shots. A VAF pays for itself the first time you use it, IMHO.
http://www.youtube.com/watch?v=eeA-siZRE3A&feature=player_embedded
I have been toying with the idea of getting a VAF-5D2b Moire / Aliasing Filter,
but i watched Ted Ramasola 's Video of shooting charts,
After watching that i don't think i will , What i notice was the morie pattern are still
there, but with a big Sharpness Drop with H264 & Raw.
I like its being de-focus or Soft focus. Plus i noticed a WB Change.
to a Yellow over-tones.
I was wondering it in Real world, do you notice these problems ?
Is the Sharpness lose a issue ?
:)
Let some friends shoot some plates of the fire out in vegas for their feature film. Hard to see the fire but pretty sky! Love the way the colors match what I actually saw with my eyes.
Quote from: reddeercity on July 15, 2013, 08:57:46 PM
I was wondering it in Real world, do you notice these problems ?
Is the Sharpness lose a issue ?
There is no sharpness loss. What you perceive as softness is actually the true resolution of the camera which is revealed by the filter. Yes, it's that soft in H264 mode -- scary. Aliasing creates false detail / jagged edges, which is why mark ii footage in raw sometimes looks a little "crispy". The filter removes this.
With the filter the images are really nice, and very detailed. I saw the charts before I bought one, and I was skeptical. However in most *practical* situations, the jaggies are greatly reduced. Hair is a great example. Hair almost always looks terrible with no filter -- horrendous false color that is visible with the slightest motion of your subject. This is nearly eliminated with the filter. However if you shoot things with lots of geometric patterns, then a 5D2 is not for you, even with the filter.
Also, the filter does reduce the resolution of still images. You must remove the filter for full resolution stills, and this can be a little annoying. For things like taking a snapshot of lighting setups, I just leave it in. The images are surprisingly useful. In fact, taking a 21MP still with the filter installed, and zooming all the way in, is a good way to see just how good the filter really is. The images are far more detailed than H264 mode.
I have a 6D with VAF-6D filter and I can confirm everything what Hazer said.
Because of the lack of false colour and false details with the filter you can also add more sharpness in post without exagerrating picture artifacts.
Quote from: reddeercity on July 15, 2013, 08:57:46 PM
I was wondering it in Real world, do you notice these problems ?
Is the Sharpness lose a issue ?
:)
This attached video is an example of my real world use of the 5D2+VAF. I shot this for non-profit work to raise funds for a church restoration, it will show a lot of wide shots of a brick structure that will simply be very difficult without the filter. Also shows some person interviews, I intentionally did not sharpen the interview shots since the person is old and it would "enhance" his wrinkles. :)
There was no raw video yet so this is H264, but Magic Lantern was used so I could monitor the sound and split the audio channel for safety, auto rec restart is also useful in long interviews.
Please view in 1080p.
Mostly people shots on this one.
@ ted ramasola, did you notice that you have used the german national anthem in the beginning? ;D
Quote from: Daedalus0506 on July 16, 2013, 12:53:44 PM
@ ted ramasola, did you notice that you have used the german national anthem in the beginning? ;D
Hahaha! Sounds similar though, but it was an improv, live piano a music professor was playing for me at the seminary. But yeah, sounds similar. Can't remember the title but he was playing from notes "he said he made". :D
Quote from: ted ramasola on July 16, 2013, 08:48:32 AM
This attached video is an example of my real world use of the 5D2+VAF. I shot this for non-profit work to raise funds for a church restoration, it will show a lot of wide shots of a brick structure that will simply be very difficult without the filter. Also shows some person interviews, I intentionally did not sharpen the interview shots since the person is old and it would "enhance" his wrinkles. :)
There was no raw video yet so this is H264, but Magic Lantern was used so I could monitor the sound and split the audio channel for safety, auto rec restart is also useful in long interviews.
Please view in 1080p.
Mostly people shots on this one.
Very Nice Ted,
I think you answered my question
I Think the VAF filter would be a good investment,
the interviews "Sold Me" Thanks :)
Here is the benchmark of a Flashraptor 800x 64GB Card
As some people are reporting low write rates for cards others report much higher values to, may there be something wrong with a batch of 5D's or some of the cards?
(http://img818.imageshack.us/img818/7356/t1vt.png)
What do you guys think? Should I be sending this card back? Can't get continuous on the Komputerbay 64gb 1000x. Only getting around 54.2mb/s currently. Here is the last benchmark
(http://i.imgur.com/7wPFwWQ.png)
Quote from: athimbleofdan on July 17, 2013, 04:13:48 PM
What do you guys think? Should I be sending this card back? Can't get continuous on the Komputerbay 64gb 1000x. Only getting around 54.2mb/s currently. Here is the last benchmark
(http://i.imgur.com/7wPFwWQ.png)
Can you run the test again in playback mode?
@coma I have a Monster 800x card and get around 60 MB/s and a Promaster 1000x card and get around 73 MB/s, if you want to get the maximum recording time with raw you will need a 1000x card.
@athimbleofdan you may want to try and return that card based of my tests and what others report you should be getting write speeds in the mid 70 MB/s range.
@bnvm Thanks! Doing a couple more tests in movie and playback mode. Here are the results. Looks like it's an improvement over photo mode. Right around where it should be. Still can't shoot full 16:9 1880 in continuous. It's not giving me the green "continuous okay" and saying it's around 56.4 mb/s now. Seems to change every so often.
(http://i.imgur.com/H97L7W8.png)
@athimbleofdan your number still seem low. As I recall it is not valid to benchmark the card in playback mode, the results are always higher than you get with other modes. I believe that the live view needs to be enabled during benchmarking to get an accurate reading of how the card will perform when recording raw.
With your 1000x card you should be getting around 75 MB/s when recording raw, the 56.4 MB/s you are getting is similar to what I see with my 800x card. I believe at this point continuous shooting at 1880 with 16/9 ratio is not possible with any card, the MK5D2 body doesn't quite have the speed required. As of now, if I remember correctly, I the highest resolution I can get continuous shooting is at 1880 with a aspect ratio of 2 (1880x940).
Things have been changing quickly so I may be wrong on some of the specifics however.
Did you get that resolution with the komputerbay 1000x.
Iv been reading and looking at samples of the new tweak that has been found, the Dual ISO, the results looks amazing from what i have seen so far. Iv noticed that its for the 5Dmkiii and 7D at the moment, will this ever come to 5Dmkii?
Cheers :)
Quote from: xNiNELiVES on July 17, 2013, 08:05:02 PM
Did you get that resolution with the komputerbay 1000x.
No with a ProMaster 1000x 16GB, I am getting about 73 MB/s with it.
Quote from: bnvm on July 18, 2013, 12:04:19 AM
No with a ProMaster 1000x 16GB, I am getting about 73 MB/s with it.
Oh, ok. Thats about the same, apparently a tad slower though. The komputerbay gets 75mb/s....
Yep definitely slower 71 MB/s normal and 73 MB/s in crop mode.
Its weird how the komputerbay is the fastest. Some report even faster than Lexars.
http://youtu.be/qBFUsbBXH-w
Apologies for the delay. VAF test: one with and one without (can you guess which is which?) @1872 x 1250 in a 1920 x 1080 AE comp. All settings at zero in ACR, 400% scale applied for the digital zoom and rendered out @ h264 8mbps. The aliasing looks terrible without the VAF in Resolve & AE, but that's a display trade off, although the 8Gb lossless version from AE has artifacts around the plain of focus. It's hard to differentiate and perhaps I'm justifying my outlay, but the areas that would suffer aliasing are much smoother, particularly the double yellow lines. The VAF also has a slight reverse diopter effect, adding 15-25mm to your closest focal point.
Buying a Komputerbay card was really really difficult for me, they keep sending me the wrong one. Now I have the opportunity to choose the size again. A lot of people here have tested them, which one is the fastest? 32GB or 64?
Recently I bought a 32g, in 1880x1058 (16:9) (23.976) can record some 1500f (some a minute and a half), so I think it is a good choice ... for your reference. ;)
(http://farm4.staticflickr.com/3782/9315482614_9dd51a39e8_o.jpg)
Quote from: a59192 on July 18, 2013, 05:12:03 PM
Recently I bought a 32g, in 1880x1058 (16:9) (23.976) can record some 1500f (some a minute and a half), so I think it is a good choice ... for your reference. ;)
Thanks a lot. How about 1856X1004?
Quote from: togg on July 18, 2013, 05:31:17 PM
Thanks a lot. How about 1856X1004?
Recording can be set at 1856x1044 exceed 3200f no skip, the largest in 5400f around (over four minutes), use the frame skip in 2, Card warm-up set at 1G, the average recorded for the 75 ~ 76.4MB / s up and down. :)
Quote from: a59192 on July 18, 2013, 05:49:53 PM
Recording can be set at 1856x1044 exceed 3200f no skip, the largest in 5400f around (over four minutes), use the frame skip in 2, Card warm-up set at 1G, the average recorded for the 75 ~ 76.4MB / s up and down. :)
Can you test to see if you get continuous at 1880x940? The aspect ratio should be at 2:1.
I literally just ordered this card yesterday night and I was searching ebrywhere on the forums for benchmarks etc., and all of a sudden you come out! Thanks so much!
Quote from: xNiNELiVES on July 18, 2013, 06:53:34 PM
Can you test to see if you get continuous at 1880x940? The aspect ratio should be at 2:1.
I literally just ordered this card yesterday night and I was searching ebrywhere on the forums for benchmarks etc., and all of a sudden you come out! Thanks so much!
Yes! Have been tested in 1880x940 (2:1) continuous recording over 10000f (over seven minutes) no frame skip, file size exceeds 30GB .. card is full. ::)
Quote from: a59192 on July 18, 2013, 05:49:53 PM
Recording can be set at 1856x1044 exceed 3200f no skip, the largest in 5400f around (over four minutes), use the frame skip in 2, Card warm-up set at 1G, the average recorded for the 75 ~ 76.4MB / s up and down. :)
Not bad. Now we need someone with the 64GB one.
Quote from: a59192 on July 18, 2013, 07:11:30 PM
Yes! Have been tested in 1880x940 (2:1) continuous recording over 10000f (over seven minutes) no frame skip, file size exceeds 30GB .. card is full. ::)
Freakin awesome! Thanks a lot. Is this the highest aspect ratio the card can go before non continuous shooting?
Quote from: togg on July 18, 2013, 07:25:53 PM
Not bad. Now we need someone with the 64GB one.
There are many other benchmark and reviews on this forum. I remember though yesterday when I was searching through, I found a guy who had a 32, 64, and 128 gb card. He did benchmarks for all three. The 32 and the 64 were the same. And the 128gb was significantly slower than the rest.
Here we go: http://www.magiclantern.fm/forum/index.php?topic=5510.25 Its post #49
Quote from: xNiNELiVES on July 18, 2013, 07:34:09 PM
Freakin awesome! Thanks a lot. Is this the highest aspect ratio the card can go before non continuous shooting?
I believe so and it will probably stay that way unless the dev's can find a way to decrease the amount of data written to the card, 10-12bit or find a way to squeeze a little more bandwidth out of the MII. Looks like mid 70's is about the limit for this camera.
I'm fine with that though I wouldn't say this is final for the 5D2.
Quote from: xNiNELiVES on July 18, 2013, 07:35:52 PM
There are many other benchmark and reviews on this forum. I remember though yesterday when I was searching through, I found a guy who had a 32, 64, and 128 gb card. He did benchmarks for all three. The 32 and the 64 were the same. And the 128gb was significantly slower than the rest.
Here we go: http://www.magiclantern.fm/forum/index.php?topic=5510.25 Its post #49
Thanks a lot. And he was really lucky with his purchase!
My 64GB Komputerbay is almost continuous @1.85.
1872 x 1012
5917
6331
5089
reformat
261
6579
5418
5498
1856 x 1004
14000+
Komputerbay 64GB 1856 x 1044
2035 frames which is nearly 2 mins
interesting fact: 1880 hack is giving me about 1-2MB/s less in writing speed...
Quote from: Redrocks on July 18, 2013, 11:54:14 PM
My 64GB Komputerbay is almost continuous @1.85.
1872 x 1012
5917
6331
5089
reformat
261
6579
5418
5498
1856 x 1004
14000+
What about 1880 @ 1.85?
Quote from: xNiNELiVES on July 19, 2013, 02:25:19 AM
What about 1880 @ 1.85?
1880 is actually 1872 (camera limit)
Quote from: coma on July 19, 2013, 02:04:06 AM
Komputerbay 64GB 1856 x 1044
2035 frames which is nearly 2 mins
interesting fact: 1880 hack is giving me about 1-2MB/s less in writing speed...
I think it's like that with any higher resolutions... Idk I may be wrong.
Quote from: coma on July 19, 2013, 02:29:54 AM
1880 is actually 1872 (camera limit)
I was wondering that, but why do they offer 1880 over 1872? I feel like the ML team found that the sensor actually doesn't utilize all of the sensor's pixels. For example the sensor is actually 22 mp but it only uses 21 mp, same with other cameras such as the 5d3.
Again I'm just speculating. I have no idea.
Quote from: xNiNELiVES on July 19, 2013, 02:35:26 AM
I was wondering that, but why do they offer 1880 over 1872? I feel like the ML team found that the sensor actually doesn't utilize all of the sensor's pixels. For example the sensor is actually 22 mp but it only uses 21 mp, same with other cameras such as the 5d3.
Again I'm just speculating. I have no idea.
1880 is not on the official repo and not "endorsed" by a1ex. It is only available in a.d. compile.
Thats the reason why it's an option in menu to switch on and off.
Quote from: ted ramasola on July 19, 2013, 03:12:57 AM
1880 is not on the official repo and not "endorsed" by a1ex. It is only available in a.d. compile.
Thats the reason why it's an option in menu to switch on and off.
So what's the point of A.d. adding it in when it's actually 1872? Is that what the dngs come out to when they're extracted?
Quote from: xNiNELiVES on July 19, 2013, 03:35:11 AM
So what's the point of A.d. adding it in when it's actually 1872? Is that what the dngs come out to when they're extracted?
Its not just 1880 is "actually 1872", a.d added it since its possible, and the dngs is still 1880, but if I understood a1ex correctly (he or a.d. could chime in and correct or add to this), 1872 is more "efficient" to process and determined that 1880 was not efficient to process thus some report to get lower performance than with 1872. It was explained way back, probably in this thread or in another.
There are some features added by a.d. that sometimes make it to the repo, some don't, like the black borders. My understanding is a1ex found out it "sometimes" causes problems with other users. So whenever he thinks its not efficient in other cameras or models, he doesn't port it to the official repo.
The black borders and 1880 don't cause problems with my camera and card though so I personally use a.d.'s build.
Quote from: ted ramasola on July 19, 2013, 04:16:11 AM
Its not just 1880 is "actually 1872", a.d added it since its possible, and the dngs is still 1880, but if I understood a1ex correctly (he or a.d. could chime in and correct or add to this), 1872 is more "efficient" to process and determined that 1880 was not efficient to process thus some report to get lower performance than with 1872. It was explained way back, probably in this thread or in another.
There are some features added by a.d. that sometimes make it to the repo, some don't, like the black borders. My understanding is a1ex found out it "sometimes" causes problems with other users. So whenever he thinks its not efficient in other cameras or models, he doesn't port it to the official repo.
The black borders and 1880 don't cause problems with my camera and card though so I personally use a.d.'s build.
Oh ok. Well I like these individual features and I rather have 8 more pixels. I'll stick with ad too. Nothing against a1ex or anything.
I have getting a few corrupted frame in the Crop Mode. :(
I'm on the July 11th Built, With the new raw2dng for PC
Frame size 2048x930 23.976p , recorded for 5700 frame on Lexar 1000x 64GB card
Used Canon 70-200 @ 200 with 2x extender = 400 mm
in crop mode should = 1200 mm
no problems recording continuous
(http://farm6.staticflickr.com/5322/9316806921_518f416072_b.jpg) (http://www.flickr.com/photos/96806538@N08/9316806921/)
001467 (http://www.flickr.com/photos/96806538@N08/9316806921/) by davidmiazga1 (http://www.flickr.com/people/96806538@N08/), on Flickr
(http://farm3.staticflickr.com/2844/9316806975_6367deb44e_b.jpg) (http://www.flickr.com/photos/96806538@N08/9316806975/)
001637 (http://www.flickr.com/photos/96806538@N08/9316806975/) by davidmiazga1 (http://www.flickr.com/people/96806538@N08/), on Flickr
(http://[url=http://www.flickr.com/photos/96806538@N08/9316806921/)
Edit: Fix Photo Links
Image 200 frame apart
your attached images are not showing.
I second this.
Why can't the Mark II get the new Dual ISO Dynamic Range, what different with the 7D that allows it?
Quote from: a1ex on June 27, 2013, 09:02:48 AM
@guentergunter: I have explained the reasons for mod16 resolutions, and I'll stick with that.
If a.d. wants to provide 1880, that's his own choice and I do not support it in any way. I know what trouble I had on 5D3 with random lockups because of DMA misalignment, so I'll stick with a portable solution that works everywhere.
As for the other options, some of them are good and will be added to vanilla builds (e.g. black bars, but in a clean way that does not fight with other overlays), others are just ugly hacks (e.g. dropping frames instead of optimizing playback code, or some status displays moved over ML overlays, therefore flickering like crazy if you enable both.
--------------
1880 doesn't seem worth taking a chance on at this point. Not that I don't appreciate a.d's efforts, I just prefer to work with the most reliable code. I did direct comparisons between a.d. & A1ex's builds:
http://www.magiclantern.fm/forum/index.php?topic=6662.msg53551#msg53551
Quote from: dariSSight on July 19, 2013, 09:36:14 AM
Why can't the Mark II get the new Dual ISO Dynamic Range, what different with the 7D that allows it?
http://cdn.bitbucket.org/hudson/magic-lantern/downloads/dual_iso.pdf
3.1 What about other cameras?
Unfortunately, most other Canon cameras follow a different pattern for the CMOS #0 register,
without any obviously duplicate fields. As we know from Canon specs, most cameras have
a 4-channel sensor readout, except for 5D Mark III and 7D which have a 8-channel readout.
Therefore, it's likely that our ISO trick may work on the 7D.
As for the Dual ISO video on the 5D2: I obviously have no idea that it will ever happen but, 1% found that it should work on the 6D... If it works on the 6D there's quite a larger chance that it should work on our 5D2. Then again though, its an older canon camera, things change...
Here's a stupid question :-\,
can someone tell me how to film in crop mode on the 5d2?
thanks!
Quote from: xNiNELiVES on July 19, 2013, 06:17:16 PM
As for the RAW video on the 5D2: I obviously have no idea that it will ever happen but, 1% found that it should work on the 6D... If it works on the 6D there's quite a larger chance that it should work on our 5D2. Then again though, its an older canon camera, things change...
You mean the
DUAL ISO RAW Video right? :)
Quote from: ThibaudS on July 19, 2013, 09:12:41 PM
Here's a stupid question :-\,
can someone tell me how to film in crop mode on the 5d2?
thanks!
To record in 3X crop mode;
Press magnify button, (the one with the magnifying glass symbol) on your camera body.
5x magnify only NOT 10x.
While in 5x magnify, choose the resolution you want in ML menu. (you can choose higher resolution while 5X magnify is engaged)
Use AUTO preview or ML grayscale in ML menu.
Start recording by pressing SET button.
:)
Quote from: ted ramasola on July 19, 2013, 09:20:53 PM
You mean the DUAL ISO RAW Video right? :)
Yeah. That's what I meant.
Quote from: ted ramasola on July 19, 2013, 09:26:27 PM
To record in 3X crop mode;
Press magnify button, (the one with the magnifying glass symbol) on your camera body.
5x magnify only NOT 10x.
While in 5x magnify, choose the resolution you want in ML menu. (you can choose higher resolution while 5X magnify is engaged)
Use AUTO preview or ML grayscale in ML menu.
Start recording by pressing SET button.
:)
Thanks Ted !
Quote from: ThibaudS on July 20, 2013, 09:16:18 AM
Thanks Ted !
Also, in ML menu make sure that centre framing mode is set to x5 mode :)
I guess this is pretty obvious, but turning off the buffer display does get me a little extra write speed. With a.d.s 5bad65ff8cb8 build, buffer display off, write speed peaks at 74MB/s and at 1856x1044 25fps I get between 700 and 800 frames. With buffer display on, or using the standard nightly 2013-07-20, write peaks at 73MB/s and at the same resolution I get 600 to 700 frames
Komputerbay 1000x 64GB in a very old and tired 5D2.
I'm going out this weekend to shoots some test scene for special effects and some potential scenery shots, I would like to have some advice on Resolution settings and aspect ratio setting. Now the native Canon 5D Mark II video output is a sensor downscale from 1880 RAW to 1920x1080p H.264, what would be the equivalent to that in our ML settings? What is the best possible Aspect Ratio and Resolution? From your research what's the hightest upconversion that can be don with the ML RAW setting for the 5D Mark II? I have the Cinestlye Picturestyle so what's the best option for DNG conversion, the Resolve workflow or Adobe Camera Raw workflow? Thanks for any info you guys give me, last I feel a.d's compile are great and does a.d compiles include Alex's also? Where are Alex compiles?
Hi there,
I used to be able to change the DNG's Camera Profile to "Neutral" or to any other profile in Lightroom and in ACR. Now I can't ("Embedded" is selected as the default profile, and it can't be changed). I don't know if this is the right thread, but could you give me a hint?
Thank you!
Just tested the new build from a.d laboratory working smooth no pink cast or anything! killing it !!! thanks devs
Getting 920 frames with 1880 frame size,
1600 frames with 1872 frame size
using a brand new Komputer Bay 64gb 1000x
BTW, can't find the way to open more than 4 gig files. Read it a long time ago but forgot where it was. Can anyone point me in the right direction?
thanks!
Quote from: Kabuto1138 on July 21, 2013, 03:20:21 AM
BTW, can't find the way to open more than 4 gig files. Read it a long time ago but forgot where it was. Can anyone point me in the right direction?
this might help you ..
http://www.magiclantern.fm/forum/index.php?topic=5655.0 (http://www.magiclantern.fm/forum/index.php?topic=5655.0)
Quote from: noix222 on July 21, 2013, 03:28:15 AM
this might help you ..
http://www.magiclantern.fm/forum/index.php?topic=5655.0 (http://www.magiclantern.fm/forum/index.php?topic=5655.0)
Thanks!
Quote from: Doyle4 on July 20, 2013, 10:46:52 AM
Also, in ML menu make sure that centre framing mode is set to x5 mode :)
Doyle4,
I have tried switching this to SET to x5 mode and I see no benefit over OFF/center since current build still give you off centered framing when recording is started.
While preview-AUTO setting gives you ML grayscale when in 3x crop mode, framing your shot is possible.
When record is started. the screen gives you a grayscale image with realtime feedback but off centered framing and scaling.
Quote from: ted ramasola on July 21, 2013, 08:11:19 AM
Doyle4,
I have tried switching this to SET to x5 mode and I see no benefit over OFF/center since current build still give you off centered framing when recording is started.
While preview-AUTO setting gives you ML grayscale when in 3x crop mode, framing your shot is possible.
When record is started. the screen gives you a grayscale image with realtime feedback but off centered framing and scaling.
Thanks for explaining this, I think due to not understanding this I may have ended up with a hell of a lot of oddly composed shots of my last job...
Quote from: ted ramasola on July 21, 2013, 08:11:19 AM
Doyle4,
I have tried switching this to SET to x5 mode and I see no benefit over OFF/center since current build still give you off centered framing when recording is started.
While preview-AUTO setting gives you ML grayscale when in 3x crop mode, framing your shot is possible.
When record is started. the screen gives you a grayscale image with realtime feedback but off centered framing and scaling.
Ahh sweet ill have to check this out, iv used x5 framing for all my crop shots, ill see what i make of it after changing somethings.
Iv read a few post's asking about the new Dual ISO for 5D mkiii and 7D and some people asking about the 5D mkii like my self... i found this to why its only thous two cameras.
From A1lex him self:
QuoteWorks for both photos and raw videos on Canon EOS 5D Mark III. On Canon EOS 7D, photo only (since it can't do raw video).
What are the benefits? more dynamic range (less shadow noise).
The functionality was not really in Canon firmware, but in the chip that samples the sensor. Canon firmware does not make any use of it (they just set both ISO "registers" to the same value). It was implemented on the hardware side though (and that's why it works only on these 2 cameras, because only they have two ISO amplifiers)
Here is a test I shot a few days ago:
Come on guys...
This is a community that we are all interested in and like to help one another, this is the first time iv witnessed this.
I think some people have read things wrong and taken in the wrong way, this happens, its apart of life, its hard to put feeling and emotion into text.
Lets start clean guys, theres enough crap going on in the world that we cant fix... but us on here should be sticking by each other and helping one and other.
Much love and peace. :)
PS. Iv upset devs by mistake and not ment too, im dyslexic and disprastic and dont always read things correctly so when replying i look like im moaning, but i never take offence if a reply is upsetting to me, its my own doing of how i explain and type it, i just apologise and try and explain better next time around, these devs do alot and must be under alot of stress fixing and tweaking... and have PM messages that we dont see.
Sit back and smile :) its all about you knowing the truth, let others think what they want.. you are you and thats all that matters :)
Quote from: Redrocks on July 19, 2013, 11:11:01 AM
Quote from: a1ex on June 27, 2013, 09:02:48 AM
@guentergunter: I have explained the reasons for mod16 resolutions, and I'll stick with that.
If a.d. wants to provide 1880, that's his own choice and I do not support it in any way. I know what trouble I had on 5D3 with random lockups because of DMA misalignment, so I'll stick with a portable solution that works everywhere.
As for the other options, some of them are good and will be added to vanilla builds (e.g. black bars, but in a clean way that does not fight with other overlays), others are just ugly hacks (e.g. dropping frames instead of optimizing playback code, or some status displays moved over ML overlays, therefore flickering like crazy if you enable both.
--------------
1880 doesn't seem worth taking a chance on at this point. Not that I don't appreciate a.d's efforts, I just prefer to work with the most reliable code. I did direct comparisons between a.d. & A1ex's builds:
http://www.magiclantern.fm/forum/index.php?topic=6662.msg53551#msg53551
It's me, a1ex replied to.
I said: If there's no difference in performance, I would always prefer the highest possible resolution (equal quality, in my oppinion).
And since I at least record at 2:1 or even wider, I can in any resolution (without crop) record untill my 64GB Lexar 1000x is full. Thus I see absolutely no sense in throwing those 8 pixels away (which would also imply a slide crop).
Also, I think a.d.'s code is highly reliable. It's simply not that fast when it comes to 1880, but that's due to the architecture of the camera's chipset (which is by the way linked to the mod16-topic, what a1ex explained).
So a.d. simply gives us the possibility to get the highest possible resolution out of our 5D's. And since it's optional you can unhurriedly find out if it fits your setup (aspect ratio; CF-card; etc.)
Quote from: a59192 on July 18, 2013, 07:11:30 PM
Yes! Have been tested in 1880x940 (2:1) continuous recording over 10000f (over seven minutes) no frame skip, file size exceeds 30GB .. card is full. ::)
Same here with Lexar 1000x, both 32GB and 64GB.
it's not possible just to keep it in 1872 ? So it would be nice to get same aspect 1872 in normal crop and 3x crop mode... im running a.d's builds and i get no corruption frames, bad pixels or anything even without the greyscale. It freaks me black and white when i press rec kkkkk at this point all RAW thing have changed a lot the whole industry and even my business saving me some money on new equipment. So guys this is the future and all you dev's made this happen! You all should be super proud and all i have to do is spread the word and thank all you guys! keep on ROCKING ! 8)
ps: sorry my english is not as sharp as a raw file
Hey guys
When I hit the 5x crop button, my image punches in, but when I hit record, nothing changes. I was under the impression that I could get proper framing before I hit record.
I've had this same issue on the last 3 builds. When I review the image, it's wider than what the live view displayed. Is it just my ignorance, or do I have a legitimate issue?
Thanks everybody
I've just removed a bunch of off-topic nonsense from this thread, and a couple of you are lucky that I've been told I'm often to heavy handed, or else I would have handed out a bunch or warnings also.
Please keep the discussion on-topic. Discuss misunderstandings in PM. Use the report button, or ignore the post and go and enjoy some sunshine.
With regards to the differences between builds by a.d. and the official repo. There are reasons why some of the features that a.d. provides do not make it into the official repo. The official repo must maintain some form of safety for users. Yes it's made quite clear that ML can brick your camera, but there is a clear difference between providing a warning, and pushing all manner of code to the official repo without sufficient testing and without a very clear understanding of the consequences of the code.
Also, individual developers might have ideas that do not fall within the scope of what the ML development team as a whole are trying to accomplish.
Endless bickering back and forth about specific features does not serve any purpose but to disrupt the flow of conversation. If there is a specific feature in a build that is not yet in the official repo, you are welcomed to make a feature request (http://www.magiclantern.fm/forum/index.php?board=24.0).
@Audionut
Sweet man, Apologies also..
Ok, I'm getting a dead pixel in my footage. Not sure if it's a h/w issue on the sensor, the build (July 11 A1ex), or the raw2dng. I have the raw files from the camera if someone would like to take a look. Let me know where to drop it.
H/W: 5D Mark ii, Shot on various lenses, 64gb Komputerbay 1000x CF
Post: raw2dng ->davinci resolve lite 9 -> fcpx
Settings:
1880x800
2.35:1
1880: on
Frame Skipping: off
Small Hacks: on
https://vimeo.com/70832943
(Posted in the post-processing forum as well as I'm not sure if it's hardware, ML or raw2dng). Thoughts?
it's a dead pixel: for example, post:raw2dng->aftereffects ...
adobe acr should remove it automatically.
Good evening A.d. Compiling a new build?
Thanks AD. Darn, I suppose that only leaves me with the raw2dng->ACR workflow. Darn. With the new Davinci resolve, I was really hoping to cut my workflow time. Any other solutions?
Also, if the dead pixel is on my camera, have I just not noticed it before when not shooting in raw or does RAW just accentuate dead pixels?
@xNiNELiVES
no code change => no new build
Quote from: Indianac on July 23, 2013, 07:49:47 AM
...
Also, if the dead pixel is on my camera, have I just not noticed it before when not shooting in raw or does RAW just accentuate dead pixels?
it's in the camera. in general canon firmware masked the bad pixel out (value=0)
@Indianac
If ACR is not removing it try the tutorial i found, using after effects and Wire removing.
Click on my name, choose show post's and there will be a dead/hot pixel fix tutorial :)
is there something I am missing on how to treat larger then 4 GB files... I got three of the sort with the .R00 file but when I try to process it all I get is noise and then a black screen, also have looked in the forum but haven't found a way that seemed clear enough, thanks again!
Quote from: Africashot on July 23, 2013, 02:46:17 PM
is there something I am missing on how to treat larger then 4 GB files... I got three of the sort with the .R00 file but when I try to process it all I get is noise and then a black screen, also have looked in the forum but haven't found a way that seemed clear enough, thanks again!
Make sure you merge the parts into 1 file before you run raw2dng. Checkout the first post in this topic.
I'm sorry but I'm very new to ML. I'd like to install the version that will allow me to shoot RAW video with my mkII. Where do the latest download files fit in to the install? Should I do the regular ML install first or can I just swap/add the ML (modules) folder into the original downloaded ML v2.3 folders.
Sorry I know you guys are far past this I just wanna make some great videos.
Thanks
Go to page one of this thread.
Quote from: a.d. on July 23, 2013, 08:54:05 AM
@xNiNELiVES
no code change => no new build
it's in the camera. in general canon firmware masked the bad pixel out (value=0)
Sorry for the late reply. Thanks AD. I found some sites which show how to get Canon's firmware to "discover" and correct for new dead pixels. I'm going to give it a go. Appreciate your help guys.
https://vimeo.com/70026258
https://vimeo.com/70026258
The new Auto Exposure is pretty damn sweet!
Going to try this option tomorrow at an air show :)
@elarturex
You need to put your link in between the code. E.g:
[ vimeo]your link here[ /vimeo] <---- i added spaces so it didnt think i was posting a link, theres a button under the Bold button that has V press that and insert :)
I made clip for my friends containing only RAW footage thanks to a.d.build2013/07/19 5bad65ff8cb8. Still hoping for someone to help me with my only 60MB/s with 64gb 1000x Lexar card write speed and frequent crashes with anything like monitor or okii controller connected to the camera. Also have 6 corrupted clips out of 67 which can not be fixed (adding footer like advised on the forum make the conversion to dng possible but it is just pinkish mush) ALL were created while okii controller was plugged in. Camera on it's own recording bugs free.
Just received my 64GB 1000X Komputerbay :o After warming up it can do 1856X1004 continuous, 74.9-75 MB/s. I've filled the card.
Anyone was able to get more speed? Even a little more.
edit: I'm an idiot. To see maximum speed I have to put a higher res. Anyway.
FPS override, Exact FPS,
shoot 0.2 fps, get a lot of copies of the first frame. And 1.0 fps is the same.
What to do? how to disable it?
Only at 2 FPS recording is normal.
Hi togg
24fps or 25fps? I get continuous with 24fps, with that resolution. same card. What you get with 25fps?
Quote from: togg on July 25, 2013, 01:13:28 PM
Just received my 64GB 1000X Komputerbay :o After warming up it can do 1856X1004 continuous, 74.9-75 MB/s. I've filled the card.
Anyone was able to get more speed? Even a little more.
Do you think 1856x1004 is the best continues option?
Quote from: dariSSight on July 25, 2013, 06:08:17 PM
Do you think 1856x1004 is the best continues option?
Yes!
It would be wonderful to achieve continuous 1856X1044 (16/9) someday.
I second the 1856x1004 Continuous, though I rather be at 1880. So 1880x940 is where its at for me.\
Actually no its not continuous for me, the camera is on the borderline of continuous and it is for the first couple minutes. Then once the card starts filling more the card becomes 1 mb/s slower and the card can't go continuous.
Quote from: PlayIt on July 25, 2013, 04:54:18 PM
Hi togg
24fps or 25fps? I get continuous with 24fps, with that resolution. same card. What you get with 25fps?
24fps, 25 it's not continuous, the camera can't go up to 77.7 MB/s. 25 fps gives me 1394frame.
I remember one time I was using my camera in crop mode I got 78mb/s, it was crazy...
Quote from: xNiNELiVES on July 25, 2013, 06:34:27 PM
I second the 1856x1004 Continuous, though I rather be at 1880. So 1880x940 is where its at for me.\
Actually no its not continuous for me, the camera is on the borderline of continuous and it is for the first couple minutes. Then once the card starts filling more the card becomes 1 mb/s slower and the card can't go continuous.
How much Upres do you think 1856x1004 or 1880x940 can handle before it disturbs the quality?
Quote from: dariSSight on July 25, 2013, 09:38:32 PM
How much Upres do you think 1856x1004 or 1880x940 can handle before it disturbs the quality?
I don't know, about 250 pixels on the width and the same proportionally on the width.
Btw tried new build a.d. works great! I'd like to request a interface that has the writing speed and a timer. No buffer other buffer statuses.
Quote from: xNiNELiVES on July 25, 2013, 10:01:42 PM
I don't know, about 250 pixels on the width and the same proportionally on the width.
Btw tried new build a.d. works great! I'd like to request a interface that has the writing speed and a timer. No buffer other buffer statuses.
So your saying a safe Upres for 1856x1004 is 2106x1254 or 1880x940 is 2130x1190?
Quote from: dariSSight on July 25, 2013, 11:00:43 PM
So your saying a safe Upres for 1856x1004 is 2106x1254 or 1880x940 is 2130x1190?
Yeah it would probably look very similar in sharpness to the native resolution, yes.
If you're crazy enough you can upscale to 2560 on the width...
Christ. :P
Quote from: togg on July 25, 2013, 06:47:31 PM
24fps, 25 it's not continuous, the camera can't go up to 77.7 MB/s. 25 fps gives me 1394frame.
with 25fps i get around 1500 before it stops
Thanks for the update I'm now getting continuous rec. 24fps @ 1880 x 940 up from 1800 x 800 using Lexar 64gb x1000 and I can get almost 60 secs 1880 x 1016.
Can anyone explain the new "auto exposure" module? I loaded it and enable it, but it doesnt "auto" anything. I supposd it should act like an "auto iso"?
Thanks
Quote from: mihaii on July 26, 2013, 09:08:20 AM
Can anyone explain the new "auto exposure" module? I loaded it and enable it, but it doesnt "auto" anything. I supposd it should act like an "auto iso"?
Thanks
It's just for photo mode.
Quote from: togg on July 26, 2013, 12:39:10 PM
It's just for photo mode.
After doing all the setting to shoot video, what is the setting to shoot Photo with ML firmware?
Quote from: dariSSight on July 26, 2013, 03:21:09 PM
After doing all the setting to shoot video, what is the setting to shoot Photo with ML firmware?
Same as normal, choose settings from photo menu in ML
if using LiveView make sure movie mode isnt enabled for LV :)
Quote from: mihaii on July 26, 2013, 09:08:20 AM
Can anyone explain the new "auto exposure" module? I loaded it and enable it, but it doesnt "auto" anything. I supposd it should act like an "auto iso"?
Thanks
Make sure you are in Manual mode, dosnt work with LiveView from what i can see,
I set min shutter too 1/180 and seems to be working great :)
Auto exposure discussion and help here
http://www.magiclantern.fm/forum/index.php?topic=7208
Hello all ;)
Fantastic job for this 14-Bit RAW video!
Tons of thanks!
After use it some times it's well working except:
With last builds (2013-07-11 ~ 2013-07-25) I get the same bug reported by Siberia in post http://www.magiclantern.fm/forum/index.php?topic=5533.msg61762#msg61762
-> with FPS override set at low FPS there's a frame doubling in RAW videos. the sequence is (frame numbers): 121314151617(...) after extraction with RAW2DNG (build 2013-07-15).
Other bug, maybe with the same origin: With FPS override, multiple RAW video files (RAW, R00, Rnn) cannot be concatenated with the DOS cmd line copy /B and DNG cannot be extracted in individual video files by renaming in RAW.
The error message is in both of cases: 'Error: This ain't a lv_rec RAW file'
And beside, I tried to change the colour of the frame border (white border on screen) in RAW video mode without success: Is there a way? Because this border is flicking... :'(
*Edit to add the error message.
I need to understand something. What's the difference between this raw2dng for Mac http://www.magiclantern.fm/forum/index.php?topic=5508.0 and the one that I can find in the first page here? https://bitbucket.org/a_d_/magic-lantern/downloads
I mean, are they using a different debayering algorithm? And why I am not able to disable auto ProRes file creation in the one in the first page?
Thanks :P
@a.d
What is autoexpo.mo? and how do we use it please?
EDIT: Updated module
anyone use a field monitor on the 5d2 yet?
Hello all :)
I came a cross a transcoder,from DNG's & or Cinema DNG
on Windows Platform, called "CINEMARTIN CINEC"
links >http://www.cinemartin.com/cinec/#versions
you can take you dng's in & convert to ProRes 4444, convert colormatix (space) etc... on the pc ;D
But you need the gold version to do this :( (399.00 EU dollars)
Bright side ;D there have a 35 Day free trial download unrestricted.
there is also a free Version that i use for h264 to ProRes on the PC ;D
i use a New toshiba Laptop i7 Ivorybrige
Take advantage of all your cpu core, pretty darn fast .
;)
Quote from: vikado on July 27, 2013, 03:46:46 AM
anyone use a field monitor on the 5d2 yet?
Yes :-)
Click (http://www.magiclantern.fm/forum/index.php?topic=6572.msg52101)
Quote from: vikado on July 27, 2013, 03:46:46 AM
anyone use a field monitor on the 5d2 yet?
With raw video, the HDMI out of 5D2 does not drop to SD resolution and stay in HD.
You do not have to turn on hdmi-vga option in ML menu.
However, the white rectangular framing guide is skewed and offset to the left, some find this distracting, so turn it off by choosing in raw video menu>preview>ml grayscale.
The hdmi out is still in color but the offset frame guide is removed. For framing I used the old fashioned way of placing a transparent acetate over screen with different crop lines, if your monitor support crop guides that may help.
You can use tape to mask your crop. ;D
Also, DO NOT preview raw video with hdmi monitor attached as it will freeze your cam, you have to take out battery and back to reboot.
Quote from: guentergunter on July 27, 2013, 02:27:57 PM
Yes :-)
Click (http://www.magiclantern.fm/forum/index.php?topic=6572.msg52101)
Quote from: ted ramasola on July 27, 2013, 04:45:18 PM
With raw video, the HDMI out of 5D2 does not drop to SD resolution and stay in HD.
You do not have to turn on hdmi-vga option in ML menu.
However, the white rectangular framing guide is skewed and offset to the left, some find this distracting, so turn it off by choosing in raw video menu>preview>ml grayscale.
The hdmi out is still in color but the offset frame guide is removed. For framing I used the old fashioned way of placing a transparent acetate over screen with different crop lines, if your monitor support crop guides that may help.
You can use tape to mask your crop. ;D
Also, DO NOT preview raw video with hdmi monitor attached as it will freeze your cam, you have to take out battery and back to reboot.
nice. thank you very much gents.
we're planning on doing a feature on a 5d2 or possibly a 5d3.
are there any other pitfalls i should be weary about during production?
me thinks the latest build is good enough for a pro shoot.
just tested new a.d laboratory build... work like a charm and i pushed a little bit this time. i tried some 30fps shots and work as good as 24fps but with the buffer limitation [200frames in 16:9 18526x1040 1880 off small hacks ON] . I also tested in 24fps with 1880 ON and OFF and both are framing perfect! To be honest i prefer using 1880 ON so i get all my shots 1876x1054 in both 1x mode or 3x mode. Awesome JOB guys... this thing keeps getting better and better!
Hi All :)
on July 16th 10:40pm MST i did a 3x crop test on the july 11th built which had 3 bad frames out of 5700 frames.
What i found very interesting is the framing is off a little.
Basically i let the moon pass though the crop window until it was gone in the preview window.
But it did not as you see, if you watch the whole Video until the end :D
I have not tried the new built yet to see if this is still a problems.
But at any rate i put some music on from vimeo so i hope everyone enjoy it ;D
Edit: 200mm with 2x extender = 400mm @f 5.6
in crop mode 3x = 1200mm
ISO 200 with ML -0.3 = 160 ISO, i think
to see the original 2K file i uploaded it to YouTube
http://www.youtube.com/embed/k5utCP7mRQ4
Quote from: reddeercity on July 28, 2013, 10:39:01 PM
Hi All :)
on July 16th 10:40pm MST i did a 3x crop test on the july 11th built which had 3 bad frames out of 5700 frames.
What i found very interesting is the framing is off a little.
Basically i let the moon pass though the crop window until it was gone in the preview window.
But it did not as you see, if you watch the whole Video until the end :D
I have not tried the new built yet to see if this is still a problems.
But at any rate i put some music on from vimeo so i hope everyone enjoy it ;D
Edit: 200mm with 2x extender = 400mm @f 5.6
in crop mode 3x = 1200mm
ISO 200 with ML -0.3 = 160 ISO, i think
to see the original 2K file i uploaded it to YouTube
http://www.youtube.com/embed/k5utCP7mRQ4
How you enebled crop mode in 5D2 ? :)
Quote from: cosmo.lv on July 29, 2013, 12:23:57 AM
How you enebled crop mode in 5D2 ? :)
Press the 5x/10x magnification button on the top right hand side
then go back to the ML menu & select frame sizes up to 2K etc..
:)
Quote from: reddeercity on July 29, 2013, 12:52:19 AM
Press the 5x/10x magnification button on the top right hand side
then go back to the ML menu & select frame sizes up to 2K etc..
:)
Trying several times, nothing :(
Quote from: cosmo.lv on July 29, 2013, 01:18:37 AM
Trying several times, nothing :(
What Raw record module built are you using ?
make sure you are in the ML menu and not the canon menu
and also you must be in 5X magnification mode not 10X
hope that helps :)
Quote from: reddeercity on July 29, 2013, 01:39:58 AM
What Raw record module built are you using ?
make sure you are in the ML menu and not the canon menu
and also you must be in 5X magnification mode not 10X
hope that helps :)
Nothing... trying several times without success :(
trying also all RAW module builds - nothing....
You are sure you have 5D Mark II and not mark III? :)
Sure ! i did the same on the mark II this week end (200 +extender on the moon).
All i did was "load modules"
activate video RAW in the ML menu
then go in 5x press "trash" to set your resolution, press record (set)
Quote from: cosmo.lv on July 29, 2013, 11:18:33 AM
Nothing... trying several times without success :(
trying also all RAW module builds - nothing....
You are sure you have 5D Mark II and not mark III? :)
Other folks with 5DII are using it too :D just hit the 5x zoom botton with raw video on and press record, its that simple!
https://vimeo.com/71227745
1880x854 (scaled to 1080)
24p
Quote from: Africashot on July 29, 2013, 03:43:01 PM
Other folks with 5DII are using it too :D just hit the 5x zoom botton with raw video on and press record, its that simple!
Ok, i find the problem, there must be magic zoom set in all modes in ML menu and then it worked like a charm :))
problem:
i use last modules , but when i convert with raw magic the cinedng is PINK!
i use APERTURE for Color correction and in this software is PINK file, but in Davinci is normal color
what is the problem?
in the old modules no have problem
sorry for my english
regards
Just Testing the July 25th built & i had a problem in the LV,
I'm getting random moving blocks of multiply pixels in Crop mode only,
there were showing up in canon preview as green blocks and
in the ML B/W preview they show up as white blocks.
But only in crop mode! its OK in 1:1 view.
When back to the July 11th built & i don't have this problem.
Its almost like hot or dead pixels, I have never had a problem until now.
5D2 has only 11,000 activation's. I still need to check the files to see
if there is any corruption :)
(2013/07/11 bild)
Resolution 1880 x 800.
24 fps
I used Raw2dng, and later Lightroom to edit the dng files (in some cases) and convert them into jpgs, I tried to use Davinci Resolve but couldn't import the files. How can you do it?
You can see some problems (01:53 in crop mode and 03:12 ).
SORRY IT IS VERY LONG
Quote from: hornblower on August 01, 2013, 02:48:21 PM
(2013/07/11 bild)
Resolution 1880 x 800.
24 fps
I used Raw2dng, and later Lightroom to edit the dng files (in some cases) and convert them into jpgs, I tried to use Davinci Resolve but couldn't import the files. How can you do it?
You can see some problems (01:53 in crop mode and 03:12 ).
SORRY IT IS VERY LONG
http://vimeo.com/71461674
Download the recent update for resolve and/or use raw2cdng.exe and choose 12bit or 16bit.
Thank you vikado; I downloaded the recent update. When I use raw2dng I drop the file into the exe, how can I choose 12bit or 16bit?
Quote from: hornblower on August 01, 2013, 02:48:21 PM
(2013/07/11 bild)
Resolution 1880 x 800.
24 fps
I used Raw2dng, and later Lightroom to edit the dng files (in some cases) and convert them into jpgs, I tried to use Davinci Resolve but couldn't import the files. How can you do it?
You can see some problems (01:53 in crop mode and 03:12 ).
SORRY IT IS VERY LONG
I don't mean to go on a rant here or disrespect anyone's work but I'm not sure what is the point of posting video that does not represent the strengths of shooting in RAW. A lot of footage I have seen, and this is no exception, shows high contrast scenes that have a large amount of over- and underexposure. These kind of examples look no different than if I shot video with my 5D2 without Magic Lantern. So I would ask anyone considering posting video to do so with the intent of demonstrating why it's worth shooting RAW. Show some scenes that cannot be captured using h.264. How about some detail in the shadows while maintaining cloud structure on an overcast day. Let's get a sense of what 13 stops of latitude looks like.
Again I'm not trying to offend anyone or be negative in any way, just encouraging everyone to show what's unique about RAW. I will be posting some things soon myself once I get the time to shoot.
No problem. Sure you are right. My first objective with the test was to know the workflow (excuse if my english is bad). I used Lightroom wich I hadn't used a lot. I used a predefined style and later play with the image. You can change that later in postpo as WB. I encourage you to make your own tests. And if you are worried about what others will think about RAW (if they don´t know what RAW is) you can yourself teach them the way you like.
My conclusion is that the workflow is very hard (12 mins, 64 Ggs Komputer Compact Flash gave me two days working), but , if Magic Lantern gains stability it worths it. Thanks
Quote from: hornblower on August 03, 2013, 06:22:55 AM
No problem. Sure you are right. My first objective with the test was to know the workflow (excuse if my english is bad). I used Lightroom wich I hadn't used a lot. I used a predefined style and later play with the image. You can change that later in postpo as WB. I encourage you to make your own tests. And if you are worried about what others will think about RAW (if they don´t know what RAW is) you can yourself teach them the way you like.
My conclusion is that the workflow is very hard (12 mins, 64 Ggs Komputer Compact Flash gave me two days working), but , if Magic Lantern gains stability it worths it. Thanks
As far as workflow is concerned I am just working on my 3rd project involving ML RAW and I am now editing cine form proxies done through batchelor in premiere and then duplicating the timeline and re-linking them to the DNGs in AE. Although this is far from perfect you do at least get to work with the full quality without adding compression before editing. You could also try RAW2CDNG if you'd like to use resolve in the mix (it only takes cinema DNG files)
Quote from: Africashot on July 29, 2013, 03:43:01 PM
Other folks with 5DII are using it too :D just hit the 5x zoom botton with raw video on and press record, its that simple!
But I'm still having the same problem... couldn't find a way to get it working :(
Quote from: Africashot on August 03, 2013, 08:25:33 AM
...try RAW2CDNG if you'd like to use resolve in the mix (it only takes cinema DNG files)
Just wanted to let you know that this is no longer true. As of version 9.1.5 (released mid-July) Resolve now supports regular DNG files converted from Magic Lantern RAW files.
See http://nofilmschool.com/2013/07/magic-lantern-dng-raw-files-supported-davinci-resolve-9-1-5/ (http://nofilmschool.com/2013/07/magic-lantern-dng-raw-files-supported-davinci-resolve-9-1-5/)
This might be me missing something obvious.
I set the 5d to record at 30fps - it says 27.something in exact FPS at 1600*900
I bring the DNGs into resolve and render out and it still runs normal speed.
The MOV files shows 24fps so I didn't bother conforming in FCPX
How do I get that slightly slow motion feeling (24/30speed) with RAW?
It works fine with H264 on the camera...
thanks
I don't use final cut pro so I have no idea. However if it is similar to after effects it may be an issue with the way FCPX interprets the dng sequence. In AE when I import a dng sequence it comes in at 30 FPS regardless of what it was actually shot at. If I create a 24 FPS comp and add the footage it will playback realtime. That is because AE recognizes that it is a different frame rate and converts if from 30 FPS to 24 FPS to maintain realtime playback, most of the time this is the behavior you want. If I wanted the dng sequence to play back slower at 24 FPS instead of 30 FPS I have to change the frame rate of the dng sequence to 24 FPS and add it to a 24 FPS comp. Now AE thinks that both comp and footage are 24 FPS and the footage will playback slower.
Quote from: bnvm on August 05, 2013, 05:08:57 PM
In AE when I import a dng sequence it comes in at 30 FPS regardless of what it was actually shot at.
There's a setting in the import section of AE preferences - Sequence footage - the fps you choose there is your default.
thanks!
I dont have a mac and would like to use the new firmware for a 7d. I am using it in a 5d but would love to have the 7d fir file. Please someone ;) pls send it to me at
[email protected]
Quote from: FartingPuppyProductions on August 08, 2013, 07:27:29 AM
I dont have a mac and would like to use the new firmware for a 7d. I am using it in a 5d but would love to have the 7d fir file. Please someone ;) pls send it to me at [email protected]
You need to go the 7D post in RAW section this post is under.
What is Flexible info screen? cant find anything to do with it in the ML menu.
Cheers :)
@Doyle4
Prefs>Config file>Restore ML defaults
Restart
Info
Quote from: a.d. on August 08, 2013, 01:58:45 PM
@Doyle4
Prefs>Config file>Restore ML defaults
Restart
Info
@a.d
Thanks man!
Dont know whats changed in latest build but im now getting 83-92mb Write speed on my Trancend 1000x 32gb on my mkii :D
Update: Just got 97.9mb Write!! Super good :D was previously getting 69-70..
(http://i42.tinypic.com/33m8ymg.jpg)
Does anybody have experience with the VAF-5D2B?
Aliasing and moire and just false detail in general is really holding back some of the deep focus stuff I like doing, but at the same time I also like shooting with wide lenses and I know that was an issue with the original model which they say they have fixed in the "B" revision. I'd really like to hear from somone who has shot with it, especially in RAW as I don't know at this point if I should sink more money into the MKII or save up for the MKIII
A.d., what have you done!? 8mb/s more write! Wow awesome job man.
I'll test with my komputerbay 32gb 1000x soon.
Quote from: krummi on August 08, 2013, 05:30:33 PM
Does anybody have experience with the VAF-5D2B?
Aliasing and moire and just false detail in general is really holding back some of the deep focus stuff I like doing, but at the same time I also like shooting with wide lenses and I know that was an issue with the original model which they say they have fixed in the "B" revision. I'd really like to hear from somone who has shot with it, especially in RAW as I don't know at this point if I should sink more money into the MKII or save up for the MKIII
hi
check my VAF-6D thread in hardware and accessories, i believe vaf-6d is technically the same as vaf-5d2b, just little different shape. Wide lenses works very well, i tried with tokina 11-16 and sigma 24 1.8. It can be little soft in the corners when wide open but it is much better than the first vaf-5d version (as seen in philip bloom review) I put the link to my dropbox where you could find 6d vs 5d3 raw dng frames. in terms of aliasing and other artifacts they look the same imho.
I'll check it out, thank you very much!
a.d is rocking !!! 8)
taking video in crop mode 1920x720 with latest build it is almost impossible to record normal video, every 2 or third shot is unusable. For me it looks like some code problems of proper frame ordering, it packs .RAW file with errors of frame order. maybe buffer issue, not enougt power or speed to calculate this process... ;)
Sample video:
Same here
exact same thing here; I'm also having this same issue with Alex's build when shooting with fps override and taking pictures in silent mode
This looks like you used 10x mode, which is known not to work. Stick to 5x.
Quote from: a1ex on August 09, 2013, 08:04:16 AM
This looks like you used 10x mode, which is known not to work. Stick to 5x.
Ou... Thanks, sad that it not work. :( (going back to 07.11 release :)
Going back?! why?!
Same problem here, like I explained page #42 (http://www.magiclantern.fm/forum/index.php?topic=5533.msg62034#msg62034) a couple of day ago. :-\
Since some days I switched to the unified nightly build (http://www.magiclantern.fm/forum/index.php?topic=3072.0) to use RAW + OFPS. It works fine, even if in title it says 'not for RAW' (&, it's a detail but I prefer OSD informations placement in this release).
Quote from: Doyle4 on August 08, 2013, 04:01:46 PM
Dont know whats changed in latest build but im now getting 83-92mb Write speed on my Trancend 1000x 32gb on my mkii :D
Update: Just got 97.9mb Write!! Super good :D was previously getting 69-70..
(http://i42.tinypic.com/33m8ymg.jpg)
Well I've tested with my card and I don't get an increase. My komputerbay 32gb 1000x does 105mb/s max on my read and it goes to just a bit above 90mb/s.
Is it my card? Other people are you guys experiencing the same with my card?
Oh wow, apparently Magic A1ex digged Dual ISO (http://www.magiclantern.fm/forum/index.php?topic=7139.msg65467#msg65467) for our beloved 5D2.
So, we will get new build soon, a.d. ? ))
Hey guys, so how do we use this dual ISO thing. I see in the menu, but when I record I don't see two streams in the files. New to this ISO thing.
thanks
Quote from: xNiNELiVES on August 09, 2013, 04:41:37 PM
Well I've tested with my card and I don't get an increase. My komputerbay 32gb 1000x does 105mb/s max on my read and it goes to just a bit above 90mb/s.
Is it my card? Other people are you guys experiencing the same with my card?
Im not sure what i did to get this as i have never got above 70mb again... an odd one indeed.
YESSSS!!! Dual Iso on the MKii !!
Thanks you A1ex ;D
Is there a Mac verison for cr2hdr?
Before i post in the Bug section am i doing something wrong or is there something wrong?
Iv installed latest build with Dual Iso function, reset to Magic Lantern Deafault and Manual Mode wont allow me to change any settings.
Dual Iso disabled i still cant and Auto Exposure is disabled too..
Any help would be great thanks.
Did some tests on the dual ISO and heres some quirks. Also posted this on the dual iso for 5d3 and 7D thread but maybe this is something a.d. can fix for the 5d2 compile.
1. after activating dual iso, i can take 1 shot with it then the following shots are normal cr2. I did not turn on alternate.
I sometimes take the card out and back before I can take a dual iso shot. Sometimes reboot cam will work sometimes not.
or I will download the cr2 via usb cable. after downloading i will take another shot, they will not be in dual iso. looking at ML menu dual iso is still at ON.
2. changing the recovery ISO has a bug, after entering submenu i can change it to 3200 for example. exiting sub menu I can see the the dual iso reads 100/1600 still.
I have no problems using dual iso with my 7D.
@ a.d.
could you also add in your first post info about cr2hdr.exe that the folder holding the cr2hdr.exe + dcraw.exe + exiftool.exe
should have a simple file name and no special char as the cr2hdr.exe won't convert if the file name is "complex."
@ted
updated
@Doyle4
I've already tried to port to OSX , but it didn't work. Exiftool seems to be the culprit.
Input file : /Users/ad/Desktop/dualiso/DUAL3473.CR2
Full size : 5792 x 3804
Active area : 5634 x 3753
White level : 12400
Black borders : 158 left, 51 top
Black level : 970
ISO pattern : BddB GBRG
Estimating ISO difference...
ISO difference : 4.95 EV (3090)
Black delta : 4.16
Interpolation : mean23-chroma5x5-contrast
Matching brightness...
Looking for hot pixels...
Hot pixels : 876
Full-res reconstruction...
Alias filtering...
Dark chroma filtering...
Building contrast map...
Dilating contrast map...
Smoothing contrast map...
ISO overlap : 4.1 EV (approx)
Black adjust : -3
Output file : /Users/ad/Desktop/dualiso/DUAL3473.DNG
sh: -c: line 0: unexpected EOF while looking for matching `"'
sh: -c: line 1: syntax error: unexpected end of file
Exiftool didn't work
Hi everyone.
I noticed some strange "flickering" while something crossed the frame (ex. somebody passing trough the shot). It's like the WB and exposure go crazy for one second.
But this happen only when I postprocess the RAW files with After effects. With Davinci nothing happend and everything works fine.
Has anybody notice that? I use AE CS5.5.
Quote from: a.d. on August 10, 2013, 09:30:54 AM
@Doyle4
I've already tried to port to OSX , but it didn't work. Exiftool seems to be the culprit.
Thanks for trying man, ill download parallels again, thanks for the work.
Dual Iso problem gone now, i deleted all cfg in modules and seems to of sorted it, i dont think i fully removed the old saved one.
Also, have some testing of dual iso, i must say its incredible... great find and amazing to see it on my 5Dmkii 8) i was pretty jealous of the mkiii n 7D owners ha.
UPDATE: When file name is set too DUAL9688 the exiftool comes up with an error saying cant find DesktopY when the file name is normal or changed to a single number it says Desktop and proceeds to convert. Also finding if dragging over more than one file to batch convert the same error happens.
Actual Error: File not found - C:/Users/Doyle/Desktop/cr2hdrY.@, No files Updated, 1 files werent updated due to errors,
Happens all the time on Batch convert even with a simple name.
Why does the newest build Aug 9th come up as Aug 5 969929a55d5d+ in camera ML Interface Menu, is that a bug and shouldn't it come up as a844c5e3a60e in camera?
I think it's an info bug in my changeset, but it's the latest.
changeset: 8019:a844c5e3a60e
branch: unified
tag: tip
user: alex@thinkpad
date: Fri Aug 09 17:45:44 2013 +0300
summary: cr2hdr: disable scaling when correcting black level, update exif info instead (fixes converting files with black level other than 2048)
I'm super happy to see dual ISO here! Hope that you will find a way to bring this to mac soon :)
RAW videos obviously can't be shot with dual ISO, yet. Or am I missing something?
Quote from: guentergunter on August 10, 2013, 06:41:04 PM
RAW videos obviously can't be shot with dual ISO, yet. Or am I missing something?
Photo only atm dude like the 7D, but agreed, Dual Iso is incredible!!
Quote from: togg on August 10, 2013, 06:28:46 PM
I'm super happy to see dual ISO here! Hope that you will find a way to bring this to mac soon :)
I tried to convert it using Winebottle and no joy, currently using Parallels.
Hello colleagues! And where you can read about the work of the video with dual ISO ?
https://www.google.cz/search?q=dual+iso
I know this might be a dumb question but with the dramatic progress you guys have accomplish with ML coding I have to ask, is there anyway to get some kind of clean Slow Motion from the 5D Mark II or is the DiGiC inside too slow. Whats the highest possible FPS could we get out of the Mark II? Thanks for every thing you guys do for us Mark II users, we are able to use 70-80% of 5D Mark III functions and that make life in independent production a little more easier.
I remember canon showing off 50/60fps on the mkii but i think the camera overheated very quickly, too get a slow motion look on the mkii try this..
I'm only getting ML Grayscale Preview in 5x Zoom mode, is this normal behavior?
It means I can't squeeze out 1856 x 1044 in non-cropped shooting (just below the 77.7 MB/s required for continuous at 23.976 FPS) but can in 5x Zoom mode (with ML Grayscale).
On the latest build :)
Pardon my ignorance, but is there a way to make 5x Crop Mode work without having the Live View reframe and just resizing the framing guide? I'm sure you geniuses have already thought of this, and if so, simply ignore this post except for this:
The raw module is the single greatest invention in the history of home video.
First dual ISO test: 100/1600.
Amazing results so far!
http://www.flickr.com/photos/100126311@N05/
Quote from: rizziriz on August 12, 2013, 05:26:21 AM
Pardon my ignorance, but is there a way to make 5x Crop Mode work without having the Live View reframe and just resizing the framing guide? I'm sure you geniuses have already thought of this, and if so, simply ignore this post except for this:
Use the HAcked or ML grayscale preview in the RAW menu for correct framing in 5x crop, its not perfect because the resolution takes a drop and as far as I know it doesn't work while recording but its a start.
QuoteThe raw module is the single greatest invention in the history of home video.
You are damn right it is!
Quote from: Doyle4 on August 11, 2013, 03:54:07 PM
I remember canon showing off 50/60fps on the mkii but i think the camera overheated very quickly, too get a slow motion look on the mkii try this..
Thanks for the response and video guide, I will test it out. I think I understand what he means by the movement needs to be very slow but I wish he show an example on a secon camera, I'll get it thanks again.
Took me a while to to understand what he ment, so i tried see where thr images where and when moving... he shoots around 24 photos in burst mode,
Thought id show some samples on the new Dual Iso.
I set the camera to take two pictures, one Dual Iso and then normal.
Images are not edit to look nice, iv edited them to see how much detail i can now keep using Dual Iso if i need too.
Blacks, Contrast and Shadow is all i tweaked, i made sure i had both selected in ACR so each image had identical settings.
.... Dual Iso is amazing!!
(http://i43.tinypic.com/2dvls1e.jpg)
(http://i39.tinypic.com/2zrmdc0.jpg)
Quote from: Africashot on August 12, 2013, 07:19:35 AM
Use the HAcked or ML grayscale preview in the RAW menu for correct framing in 5x crop, its not perfect because the resolution takes a drop and as far as I know it doesn't work while recording but its a start.
Thanks! Please check out my latest short, shot entirely raw.
Wow, awesome story, grade, edit, photography, in short - great short!
Really good job! In one day only!
Anyway, the dual iso looks terrific.
Anyone knowing if dual iso raw video will be possible on the 5d2? :)
Or hardware just too old and slow?
Quote from: oddname on August 12, 2013, 08:14:47 PM
Anyone knowing if dual iso raw video will be possible on the 5d2? :)
Or hardware just too old and slow?
you can do raw dual iso video on the 5d2 :)
How? Afaik dual iso on the 5D2 only works in photo mode not video?
Dual ISO raw video did not work for me. Only did 1 test though.
Someone that claim it works, feel free to tell how too, if it does indeed works :)
hmm i think you're right, i presumed it would work, my bad !
If it doesn't use up more memory/cycles it should be possible in time then with some luck :)
Dual Iso is Photo only on the 5Dmkii, like the 7D,
it also tells you when Raw video is enabled and Dual Iso is.
As in atm or forever? Would be sweet if it will work in videomode too someday :)
Or forget about it and go mk3 that is planned :)
i shot a test CR2 with dual ISO 100/1600. when i drag it over cr2hdr.exe, it comes back with the message "Doesn't look like interlaced ISO". however, if i open the file in ACR it clearly shows the interlaced exposures. can someone help? what is going wrong? thanx!!
@oddname
dual iso videomode: I think, we suffer enough of aliasing and moire on 5D2. :o
For now, I'm quite happy what a1ex done for us.
@dima510
underexposure?
Is anyone else still having problems shooting with an external monitor? Each time I try shooting raw the camera crashes when it finishes recording and must be rebooted.
Quote from: dima510 on August 13, 2013, 03:50:40 PM
i shot a test CR2 with dual ISO 100/1600. when i drag it over cr2hdr.exe, it comes back with the message "Doesn't look like interlaced ISO". however, if i open the file in ACR it clearly shows the interlaced exposures. can someone help? what is going wrong? thanx!!
Make sure u expose as u normaly would, also make sure the image is in the same folder as all 3 .exe's
Quote from: silvertonesx24 on August 13, 2013, 10:55:24 PM
Is anyone else still having problems shooting with an external monitor? Each time I try shooting raw the camera crashes when it finishes recording and must be rebooted.
Do you use a HDMI monitor or an Android device via USB?
Quote from: dima510 on August 13, 2013, 03:50:40 PM
i shot a test CR2 with dual ISO 100/1600. when i drag it over cr2hdr.exe, it comes back with the message "Doesn't look like interlaced ISO". however, if i open the file in ACR it clearly shows the interlaced exposures. can someone help? what is going wrong? thanx!!
I also have the same problem, some files can not be resolved ...
Quote from: dima510 on August 13, 2013, 03:50:40 PM
i shot a test CR2 with dual ISO 100/1600. when i drag it over cr2hdr.exe, it comes back with the message "Doesn't look like interlaced ISO". however, if i open the file in ACR it clearly shows the interlaced exposures. can someone help? what is going wrong? thanx!!
I found the color gamut sRGB changed by the AdobeRGB, untied high chance, mainly for this reason it?
Quote from: silvertonesx24 on August 13, 2013, 10:55:24 PM
Is anyone else still having problems shooting with an external monitor? Each time I try shooting raw the camera crashes when it finishes recording and must be rebooted.
i am still on 2013/07/25 build. However - i do have this problem with a smallHD dp6.
I found a "work around" - unplug the monitor to start with, record one RAW. Plug it back in and it doesn't crash anymore. At least with me. Also i figured out, that even though it crashed - the files were recorded.
"i shot a test CR2 with dual ISO 100/1600. when i drag it over cr2hdr.exe, it comes back with the message "Doesn't look like interlaced ISO". however, if i open the file in ACR it clearly shows the interlaced exposures. can someone help? what is going wrong? thanx!!"
Turn of Video Raw Module. EttR etc. - Leave only Dual ISO module autoloaded with the start of camera and ML
btw MY SETINGS in Dual iso menu:
Recovery ISO : +6 EV
Dynamic Range Gained 2.8 EV
Midtone overlaping 7 EV
ALternate Frames Only OF
Custom File Prefix DUAL
Quote from: matthieu on August 14, 2013, 05:37:05 PM
i am still on 2013/07/25 build. However - i do have this problem with a smallHD dp6.
I found a "work around" - unplug the monitor to start with, record one RAW. Plug it back in and it doesn't crash anymore. At least with me. Also i figured out, that even though it crashed - the files were recorded.
Thanks! I will try this out. My monitor, like yours, is HDMI.
Is the Magic Lantern Video format (.mlv) for Mark II and how do you install it, because I don't see it in recent build?
the mlv implementation is not finished yet and hasn't been optimized for 5D2 at all. g3gg0 is still adding features to the format and making it stable for the 5D3. When he has reasonably stable code it will be adapted for 5D2.
The mlv2dng converter is also under heavy development now and needs a lot of work before really being usable.
Galdessa Camp 5DII RAW, HDR RAW and h.264 video
Here is our latest addition to the ML RAW portfolio, although there is some h264 footage in there too... even some coming from the t3i, mainly because we're still stuck with a single 16gb 400x card, two 1000x 64 gb cards are coming next week, so things will be easier soon!
We graded this with Filmconvert Pro, its is the first time we implemented this plugin and I must say it is also the first time I am happy with a color preset and it really speeds up the grading process and takes out a bit of the guesswork, therefore great plugin. Conveniently there is a competition over at filmconvert pro so we of course submitted this video, therefore if you think we deserve it please head over there and give us a vote, a like or a tweet, we'll love you for it! http://www.FilmConvert.com/Competition/Video.aspx?id=169
Can certainly tell the difference between RAW and H.264 but amazing footage none the less. I doubt the general public would see any difference.
Quote from: Zao on August 16, 2013, 12:07:04 AM
Can certainly tell the difference between RAW and H.264 but amazing footage none the less. I doubt the general public would see any difference.
Yep... the difference is scary! And sadly I am guessing the general public will see it more then I'd like to admit. Also, try and show your client a rough cut before color grading and instead of going the extra mile and shooting RAW it will look like your screwing up things by still shooting h264 (and good luck explaining the differernce; what is bitrate anyway!? How much is that in megapixels???... why is the lion so blurry?)
Nice video Africashot. Yes, if those washed out and soft shots are h264, then yes I can also tell the difference. ;) Magic Lantern has spoiled us. Now theres no turning back. ;)
Quote from: Africashot on August 16, 2013, 03:20:56 AM
(...) why is the lion so blurry?
Because of atmospheric turbulence.
Sun heats ground, fresh air (I suppose it was filming at morning), so it makes big temperature gradient. We see light distortions through gradients (like through water/air), magnified by the small spacial sampling (relative long focal length apparently).
I see in the new update the guys have made improvements on Focus Peaking, can some one explain what focus peaking is it just a better focus check other then using 5x 10x then focus?
Here's a teaser for a music video I shot with my MarkII. I used two 32GB Komputerbay x1000 cards, and they were great!
For post-processing I used fatpig's BATCHelor exclusively and it worked like a charm. My workflow turned out pretty simple. I'd edit with the Cineform proxies straight out of BATCHelor, then opened the timeline in After Effects, replaced footage with the DNG's, corrected, then applied FilmConvert.
@a.d
Could you post that cr2hdr has been made for osx on front [age for us mac users :) Thanks man!
Working great!! is there a terminal line for multiple images please?
UPDATE: Solved, press space and add the next file name :) going to make this as a Automate Script, thanks again.
@Doyle4
just added cr2hdr with gui:
* drag & drop
* multi files & folders!
Quote from: a.d. on August 16, 2013, 04:39:31 PM
@Doyle4
just added cr2hdr with gui:
* drag & drop
* multi files & folders!
Thank you man! Very much appreciated!
I can't fill the card with the latest build (31302bbc6461) and the 1.85 max resolution, it keep going down to 74,1/74,3 MB/s. 3 minutes recording maybe. I'm using the computerbay 64gb 1000X.
With 728e571a1276 it's a lot much stable. (74,6 or more)
restore ML defaults, reboot camera
Quote from: Doyle4 on August 16, 2013, 11:59:28 PM
restore ML defaults, reboot camera
I'll try it. Thanks!
Quote from: togg on August 17, 2013, 03:06:31 AM
I'll try it. Thanks!
Worked for me when a.d told me to that :)
Quote from: a.d. on August 16, 2013, 04:39:31 PM
@Doyle4
just added cr2hdr with gui:
* drag & drop
* multi files & folders!
I have a Mac and I'm having problem installing the cr2hdr on my Mac. Is there any way you can give me a step by step installation direction?
Quote from: Doyle4 on August 17, 2013, 12:05:14 PM
Worked for me when a.d told me to that :)
It didn't work :( Can I use an older build for raw recording and the last build for dual iso? And what autoex.bin should I use?
I'm not sure about the capabilities of MKII... I will shoot a short film this month, and I really want to shoot RAW but nobody in my city (who I know, in Brindisi Italy) has got the MKIII; I can find only MKII.
Is it possible to shoot continuous 1920 x 800 @23.976 fps ? I read on the main topic about 1880x840 at 24 fps so I thought that
[email protected] will be possible.
Anyone tried ?
Quote from: Scipione205 on August 17, 2013, 03:56:53 PM
I'm not sure about the capabilities of MKII... I will shoot a short film this month, and I really want to shoot RAW but nobody in my city (who I know, in Brindisi Italy) has got the MKIII; I can find only MKII.
Is it possible to shoot continuous 1920 x 800 @23.976 fps ? I read on the main topic about 1880x840 at 24 fps so I thought that [email protected] will be possible.
Anyone tried ?
1920 is not an option on the mkii. But it's not really a problem.
what do you mean? I thought that since 1880x940 is supported for continuous shooting (which is 1'767'200 pixels), maybe 1920x800 would be (wich is 1'536'000 pixels, so about 231'200 pixels less).
That's only a simple tought, assuming that the MkII can handle the calculations (1920x800 isn't 'simpler' than 1880x940, due to bayern pattern etc.), and thinking only about the CF slot writing speed.
jeger
Quote from: Scipione205 on August 17, 2013, 05:36:29 PM
what do you mean? I thought that
1920 is simply not possible on mkii. You can find information about this limitation on the forum.
Quote from: dossisman on August 16, 2013, 02:42:02 PM
Here's a teaser for a music video I shot with my MarkII. I used two 32GB Komputerbay x1000 cards, and they were great!
For post-processing I used fatpig's BATCHelor exclusively and it worked like a charm. My workflow turned out pretty simple. I'd edit with the Cineform proxies straight out of BATCHelor, then opened the timeline in After Effects, replaced footage with the DNG's, corrected, then applied FilmConvert.
Sounds interesting. What is a BATCHelor? I googled it but nothing comes up.
Quote from: togg on August 17, 2013, 02:14:20 PM
It didn't work :( Can I use an older build for raw recording and the last build for dual iso? And what autoex.bin should I use?
Not sure man, best to ask in the general chat section, i dont want to say go ahead and find it bricks your camera, as far as im aware the autobex.bin gets updated to allow the modules to work.
@a.d
On the cr2hdr is possible in future update to view activity log in the app as it process? i noticed it shows at the end but be nice to watch and see which files are been process correctly/incorrect like the windows version?
Thanks man and GUI version working sweet man.
Hey guys ive been searching all night and just made an account so I could post this. I just came back from a skatepark with amazing lighting, I shot all raw video on my mark ii at 1280x720 (16:9) ratio 24 fps... For some reason when I edit it in photoshop, save as tiff, then open in quicktime as sequence it looks extremely grainy.. I forgot to mention but I was shooting at iso 160 - 320 at times with a 1/50 shutter speed to 1/80. The standard video looked 100x better on my mac then this raw.. I know im doing something wrong but i just dont know what.. any suggestions? also incase you were wondering I was shooting with a 24-105L if that helps.. my memory card is a lexar 1000x 32 gb..
Quote from: Doyle4 on July 20, 2013, 10:46:52 AM
Also, in ML menu make sure that centre framing mode is set to x5 mode :)
Where is this setting ML? I can't find it.
ML = Magic Lantern, ML Menu = Magic Lantern Menu = press trash :)
Quote from: Doyle4 on August 17, 2013, 09:11:44 PM
ML = Magic Lantern, ML Menu = Magic Lantern Menu = press trash :)
Thanks Doyle4. Is it in Focus Box Settings, where Snap Points should be set to: Center to x5 RAW?
When I start shooting RAW, the (white) resolution guide box goes away and comes back 10 seconds later. Is there a way to make it stay and not disappear as soon as REC is pressed?
Quote from: alexp on August 18, 2013, 04:42:08 AM
Thanks Doyle4. Is it in Focus Box Settings, where Snap Points should be set to: Center to x5 RAW?
Yeah should be in there, cant remember my self as i don't use it much at all.
Focus box disappearing, again im not 100% dude. sorry.
Quote from: Scipione205 on August 17, 2013, 03:56:53 PM
Is it possible to shoot continuous 1920 x 800 @23.976 fps ? I read on the main topic about 1880x840 at 24 fps so I thought that [email protected] will be possible.
The resolution You mention is not an option. However a 1920x084 can be set in ZOOM mode - 5X.
The closest at 1X is 1880x786 - which also is normal to use.
What to use is up to You. I think that the scaled picture is just as good + the benefit of using the lens at normal 1x ratio.
Both are giving me continius - with Transcend 1000x 16GB card - first is 62Mb/s the second is lower.
Images are in the spoiler
[spoiler]
First is the scaled 1880 image:
(http://www.zoomdesign.bg/ml/1880x768.jpg)
And then little cropped 1920 image:
(http://www.zoomdesign.bg/ml/1920x804.jpg)
[/spoiler]
Is there a way to disable the creation of ProRes 4444 in the raw2dng from the first page? I'm on a Mac and Son of Batch is slower. Or should I use this raw2dng instead? http://www.magiclantern.fm/forum/index.php?topic=5508.0
Which one is better?
Open up RAW2DNG, drop the application into it, you will be asked if you want a workflow and proress.
Quote from: Doyle4 on August 18, 2013, 07:09:42 PM
Open up RAW2DNG, drop the application into it, you will be asked if you want a workflow and proress.
This doesn't work on the one from the first page. Only on this one ---> http://www.magiclantern.fm/forum/index.php?topic=5508.0
thats the version you need dude!
The resolution You mention is not an option. However a 1920x084 can be set in ZOOM mode - 5X.
The closest at 1X is 1880x786 - which also is normal to use.
What to use is up to You. I think that the scaled picture is just as good + the benefit of using the lens at normal 1x ratio.
Both are giving me continius - with Transcend 1000x 16GB card - first is 62Mb/s the second is lower.
[/quote]
Yeah I think I got it: it's impossible to record raw 1920xsomething, the maximum in 1x is 1880x786 wich I can upscale to 1920x800 ; or I can record in crop mode 5x at 1920x804 (then I have to crop 4 pixels).
The 5x is ok only If I can borrow super narrow and super fast lenses (I want cine-depth of field and there are a lot of action scenes with narrow lenses), and that's quite impossible.
I'm not sure if upscaling will work well... we have already the moiré... but the RAW dynamic range is awesome... :'(
Anybody can tell me where I will find why 1920xsomething is not an option? I know that it's a software limitation but I'ms truggling in finding something in the forum.
Thanks you're awesome
Many pages back, there is a description about what you ask.
The 5D2 encodes the H.264 material directly from an internal RAW-buffer. This RAW buffer is the one ML (=magic lantern) reads and directly saves to the CF card. And this buffer has only those 1880 pixels.
That means: H.264 is also upscaled, but inside the camera! So, you may beleave it's true 1080p, but it isn't!
I would always rather take the 1880 RAW material and upscale it outside the camera. It will always and definitely look better than H.264!
By the way: On the 5D3, this internal RAW buffer is 1080p. So, it's not upscaled to encode H.264. That's also the reason why this cam can save 1080p RAW without crop.
Hey guys,
Just saw a recent posting asking how to disable the prores option in RAWDNG, just wondering, is there an option to ONLY make the prores files?
thanks for the help!
Quote from: Kabuto1138 on August 19, 2013, 11:09:17 AM
Hey guys,
Just saw a recent posting asking how to disable the prores option in RAWDNG, just wondering, is there an option to ONLY make the prores files?
thanks for the help!
Not too sure why you want this option when shooting RAW but let it convert and delete the folder with the RAW dng's? the proress option is there for backup/preview smaller file to work with.
I would like this option so I can do my edit, then export and edl, using that edl I'll know which are the only DNGs I'll need to convert from RAW. Is just to my edit.
the RAW file will still need converting to produce DNG's
@Scipione205 up-scaling 1880 to 1920 at %2 increase will work just fine, that is exactly what the camera does when shooting normal h.264 video. The 1880 pixel limit is not a limit of RAW shooting it is a limit with shooting video on the mkII(unless 5X crop which is not even an option for normal video). So until raw video all video out of the mkII was up-scaled to 1920. I am willing to bet that you cannot even tell the difference between 1880 and 1880 up-scaled to 1920, in terms of quality.
@guentergunter
Thank you very much. Now it's perfectly clear. Maybe is because of the 1880 buffer and upscaling (then in-camera H264) that MkII has badder moiré than MkIII?
@guentergunter @bnvm
Thank you very much, you people are wonderful.
Quote from: Scipione205 on August 19, 2013, 05:55:54 PM
@guentergunter
Maybe is because of the 1880 buffer and upscaling (then in-camera H264) that MkII has badder moiré than MkIII?
No. Aliasing (and thus moiré) always any only occurs, when you
skip lines.
In other words: Your 5D2 has 5616 columns and 3744 rows (→ 5616 x 3744 = 21026304 pixels total) of arranged silicon semiconductors which by light induce an electric voltage that is then interpreted by some mathematical logic behind to produce an image.
The very problem is, that semiconductors can only detect the intensity of light, but not it's color.
The solution: A Bayer filter (http://en.wikipedia.org/wiki/Bayer_filter)!
That means: Every one of those 21026304 pixels, your 5D2 sensor has, consists of four silicon semiconductors.
Let's now imagine a white item in from of a dark background that moves quite slowly in front of your camera. It will then first be detected by e.g. a semiconductor with a green filter, then one with a blue filter and so on. So, it always happens, that an item for a short period of time (and sadly often enough the very moment you shot) only covers half of the arranged four semiconductors which form a pixel.
So, only the green or blue or red semiconductor induces voltage and thus the mathematical logic behind means it's a green or blue or red item.
When the item moves ahead, it will cover more and more pixels completely, but at it's border, it will always just cover parts of pixels, as well.
The logical misinterpretation resulting in those wrong colored pixels at the edge of objects is what is called aliasing.
Moiré is an addition: It means that those pixels form patterns like e.g. colored streaks.
To prevent aliasing, you need to blur the light that reaches your sensor, so that it always fills one pixel completely.
In other words: Every digital camera has a blur filter in addition to the bayer filter in front of it's sensor.
And this only works for just the very resolution the sensor has.
So, when you now record a movie with 1920x1080 pixels from a sensor that has 5616x3744 pixels you have three options:
1) You only take the part in the middle of the sensor that matches your resolution.
→ no more aliasing; but higher crop factor
2a) You only read every second or third or even seldom pixel (= skip pixels/lines).
→ aliasing pops up, since the blur filter doesn't match your resolution anymore; but no higher crop
2b) You still read every second or third or even seldom pixel, but you implement a by voltage controllable variable blur filter.
→ no aliasing and no crop!
3) You take the full image from the sensor and downscale it by software on the fly in the camera before encoding.
→ no aliasing and no crop!
RED as an example uses method 1). That's why decreasing the recorded resolution increases the crop factor.
The 5D3 has one of those crazy by voltage controllable variable blur filters. That's why this camera uses the same sensor size for photos and video (no crop)
and has no aliasing.
The 5D2 has none of these solutions from stock, so there is aliasing (in video).
But there's hope: The aliasing filter from mosaic engineering (http://www.mosaicengineering.com/products/vaf/5d2.html)
Any questions left? ;)
@Scipione205
In fact I did some tests in 5x vs 1x mode, and the moire in 5x is less.
There are some factors to is - while in 5x mode You record EACH following line, in 1X mode You record each 5th line - still the four lines You skip are scanned meanwhile, so the lag is more and the moire is more pronounced. You can skip moire if You keep the focus at the edge - if it's ok for You to sharpen in post, but You will loose fine texture as well.
The explanation from @guentergunter is just wonderful, and if You haven't checked the pictures I can just say that even 1600x800 I use to shoot scales and looks extremly well on a FullHD plasma. Jus keep the color and dynamic well balanced and the CMOS clean - and forget about resolution!
Quote from: alexp on August 17, 2013, 06:25:10 PM
Sounds interesting. What is a BATCHelor? I googled it but nothing comes up.
Alexp, here's the link. Hope this helps.
http://www.magiclantern.fm/forum/index.php?topic=5645.0
Thanks dossisman.
Guys, raw2dmg just deleted my raw files and failed to create dmgs. Is there any way to recover the raw files?
Hey guys, is there a guide anywhere on how to shoot dual iso in the 5d? all I'm getting after setting up dual iso and hdr video is either RAW or regular H264 with the flicker. Any suggestions?
thanks!
Quote from: Kabuto1138 on August 20, 2013, 11:27:22 AM
Hey guys, is there a guide anywhere on how to shoot dual iso in the 5d? all I'm getting after setting up dual iso and hdr video is either RAW or regular H264 with the flicker. Any suggestions?
thanks!
Yes, Dual ISO is
ONLY working in photo mode, not video on the 5D Mark II.
DUH!!!, that explains it.
Thanks!
Quote from: alexp on August 20, 2013, 07:06:15 AM
Thanks dossisman.
Guys, raw2dmg just deleted my raw files and failed to create dmgs. Is there any way to recover the raw files?
Data rescue 3 on mac, add a file extension too it as RAW isnt deafult.
Quote from: Doyle4 on August 20, 2013, 03:13:33 PM
Data rescue 3 on mac, add a file extension too it as RAW isnt deafult.
I tried, but it's not allowing me to. Take a look. (https://dl.dropboxusercontent.com/u/10164102/raw.jpg)
Also, I was able to recreate a situation where raw2dng deletes files without creating dmgs. Here is a screen recording https://dl.dropboxusercontent.com/u/10164102/raw.mov
Try this method.
Copy youre RAW files straight to your external from your CF card,
Start RAW2DNG, drag RAW2DNG into the application and when asked to set a working folder choose no.
Drag the RAW files from the external, this will create a folder for the dng's using the default path of the RAW files.
Quote from: Doyle4 on August 20, 2013, 05:18:25 PM
Try this method.
Copy youre RAW files straight to your external from your CF card,
Start RAW2DNG, drag RAW2DNG into the application and when asked to set a working folder choose no.
Drag the RAW files from the external, this will create a folder for the dng's using the default path of the RAW files.
Yeah, I know. But right now, I'm still trying to recover files I lost :(((((
By the way, I couldn't find any way to receive email notifications about new posts here. How do you guys follow topics? I go to Profile, Summary, Show Posts, and then have to click on 10 different places where I posted messages before, just to see if anyone replied. Is there a better way?
to be honest im not sure how they got deleted, never once came across this :/
At the top it now says Show new replies to your posts.
Quote from: alexp on August 20, 2013, 04:41:42 PM
Also, I was able to recreate a situation where raw2dng deletes files without creating dmgs. Here is a screen recording https://dl.dropboxusercontent.com/u/10164102/raw.mov
It's alarming, that raw2dng deletes files at all!
Thus creating the worst of all cases imaginable! The loss of files!
I would consider this as a really dangerous bug!
By the way: Did you ever encounter something like this with RAWMagic (http://www.magiclantern.fm/forum/index.php?topic=6218.0)?
Quote from: guentergunter on August 20, 2013, 10:15:59 PM
It's alarming, that raw2dng deletes files at all!
Thus creating the worst of all cases imaginable! The loss of files!
I would consider this as a really dangerous bug!
By the way: Did you ever encounter something like this with RAWMagic (http://www.magiclantern.fm/forum/index.php?topic=6218.0)?
I found my missing files! The were not deleted, but rather misplaced. The files ended up in /Volumes.
I explain it here: http://www.magiclantern.fm/forum/index.php?topic=7778.msg68848#msg68848
Good bye raw2dmg, hello Son of Batch! ;D
Its the workflow option giving you the problem on RAW2DNG, dont create one, and RAW2DNG is best one i find :)
Quote from: dariSSight on August 17, 2013, 01:50:54 PM
I have a Mac and I'm having problem installing the cr2hdr on my Mac. Is there any way you can give me a step by step installation direction?
Remove the terminal command version, and then install the pkg :)
So just to summarise ...
When shooting raw video with Canon 5D2, is moire / aliasing better than h.264 video or worse (without any VAF5D2) ?
Are there any video resolutions that are best to reduce moire / aliasing ?
:)
Quote from: NitromanX on August 22, 2013, 10:11:50 AM
So just to summarise ...
When shooting raw video with Canon 5D2, is moire / aliasing better than h.264 video or worse (without any VAF5D2) ?
Are there any video resolutions that are best to reduce moire / aliasing ?
:)
To my eye, color aliasing and moire is a little worse in raw than h264. You can get much less aliasing and moire in crop mode. Any resolution.
With VAF, its much better BUT in crop mode the VAF softens the image. :)
Just shot this with VAF. Since I don't want to take out the vaf in the field i left it in during shots in crop mode. Crop mode shots are a bit soft but usable in this case.
Heres the charts I posted earlier comparing raw and h264, w/ and w/o vaf.
http://www.youtube.com/watch?v=eeA-siZRE3A
Quote from: ted ramasola on August 22, 2013, 11:00:11 AM
To my eye, color aliasing and moire is a little worse in raw than h264. You can get much less aliasing and moire in crop mode. Any resolution.
With VAF, its much better BUT in crop mode the VAF softens the image. :)
Just shot this with VAF. Since I don't want to take out the vaf in the field i left it in during shots in crop mode. Crop mode shots are a bit soft but usable in this case.
Heres the charts I posted earlier comparing raw and h264, w/ and w/o vaf.
http://www.youtube.com/watch?v=eeA-siZRE3A
Thanks for the much needed warning on Moire and Aliasing road block. How were you able to get 1880x1080 in 1x, What's your advice on the best aspect ratio with the most resolution and final what's your advice on scaling RAW?
Quote from: matthieu on August 14, 2013, 05:37:05 PM
i am still on 2013/07/25 build. However - i do have this problem with a smallHD dp6.
I found a "work around" - unplug the monitor to start with, record one RAW. Plug it back in and it doesn't crash anymore. At least with me. Also i figured out, that even though it crashed - the files were recorded.
Actually, this worked for me once, but after that it still crashes every time. Nothing like having to reboot after every take lol. Oh well, I'll put the external away for now.
Quote from: dariSSight on August 22, 2013, 11:23:20 AM
Thanks for the much needed warning on Moire and Aliasing road block. How were you able to get 1880x1080 in 1x, What's your advice on the best aspect ratio with the most resolution and final what's your advice on scaling RAW?
Just scale it in your NLE, we are talking 2-4% increase which will be negligible to your naked eye.
I only shoot in clean 16:9 aspect ratios so far, with a resolution of 1856 x 1044 (3,33% upscale for 1080p) or 1880 x 1058 (2,08% upscale to 1080p).
You just have to be aware of moire and aliasing, which I don't personally experience being a bigger problem in RAW versus H.264 record mode.
Quote from: ted ramasola on August 22, 2013, 11:00:11 AM
Just shot this with VAF.
Did you use the latest build? (31302bbc6461) I'm having some problem with it and the 64GB komputerbay, speed is not stable and I'm not able to shoot continuos.
I have the KomputerBay CF Card 1000x 128Gb, i've shooted continously 1880 x 856 (2:35.1) with the Alpha version.
Now that i took the 15/08 Build, i can't shoot continously over 100 frames :( ... i tried to go back but nothing to do, i still can't shoot over 100 frames :( Help please.
Quote from: bokoussama on August 22, 2013, 06:29:01 PM
I have the KomputerBay CF Card 1000x 128Gb, i've shooted continously 1880 x 856 (2:35.1) with the Alpha version.
Now that i took the 15/08 Build, i can't shoot continously over 100 frames :( ... i tried to go back but nothing to do, i still can't shoot over 100 frames :( Help please.
After shooting three projects on a single 16gb 400x card at pretty much continuous 2:35.1 I finally got two 64gb 1000x Komputerbay cards which I have formatted and loaded with the latest built, a little voice in my head kept screaming "freedom - at last!" while packing for my trip back to Tsavo East National Park tomorrow - then I read your post and had a bit of an uncomfortable feeling and pulled the already packed 5D2 back out of its bag to do the test I should have done before packing it... its maxing out at +- 600 frames pretty much every time... that's worse then my 400x card used to do!!! I hope there is a way to get the old speed back...
It seems that I'm not the only one having problem with latest build+komputerbay :P
Just formatted all the cards and went back to the 50f68ce14a69 built I had been using for a while, 2:35.1 'continuous ok' - I think I'll have a peaceful sleep up until my 4 am wake up call!
Quote from: dariSSight on August 22, 2013, 11:23:20 AM
Thanks for the much needed warning on Moire and Aliasing road block. How were you able to get 1880x1080 in 1x, What's your advice on the best aspect ratio with the most resolution and final what's your advice on scaling RAW?
Using the latest build aug 16. from a.d.
I shot this at 1728 x 972 even in crop mode to make it fill up the screen easily in 16:9 1920 x 1080.
1728 x 972 is continuous on a 1000x komputerbay cf.
1872 x 936 and 1880 x 940 is also continuous at 2:1
Quote from: ted ramasola on August 22, 2013, 10:17:48 PM
Using the latest build aug 16. from a.d.
I shot this at 1728 x 972 even in crop mode to make it fill up the screen easily in 16:9 1920 x 1080.
1728 x 972 is continuous on a 1000x komputerbay cf.
1872 x 936 and 1880 x 940 is also continuous at 2:1
So your saying 1x 1728x972, 5x 1920x1080 in 16:9 and 1x 1872x936, 1880x940 is the best option in Aspect Ratio and Resolution? How far could you upscale it for professional viewing presentation?
re: latest 16.08 build and speed on komputerbay 1000x 64gb card:
I was having massive speed reductions after the first update. I'd been mixing stills, H.264 video and raw at that point(on a single card) and I thought maybe reformatting and reinstalling could help. I formatted from my card reader, formatted in my 5d mii, reloaded ML onto the card and did the firmware update - the speed went back to continuous at 1728x972 which is what I shoot at.
So it's not exactly scientific but reformatting might possibly help.
@ a.d.: Would it be possible to deactivate any recording frame as an option?
Actually you can choose between white and black; and I would really like to deaktivate it at all.
That's due to the fact, that I'm recording quite often with an external monitor attached, which makes the frames from ML still useless!
I glued my monitor like most other people do for correct framing as well, here the wrong borders are annoing.
P.S.: Correct frames would be much better than wrong and deactivated ones. But the former should be much easier to implement, I think...
I guess it's problem many people apply to.
Quote from: guentergunter on August 23, 2013, 06:51:22 AM
@ a.d.: Would it be possible to deactivate any recording frame as an option?
Actually you can choose between white and black; and I would really like to deaktivate it at all.
That's due to the fact, that I'm recording quite often with an external monitor attached, which makes the frames from ML still useless!
I glued my monitor like most other people do for correct framing as well, here the wrong borders are annoing.
P.S.: Correct frames would be much better than wrong and deactivated ones. But the former should be much easier to implement, I think...
I guess it's problem many people apply to.
when you attach an external monitor, choose ML grayscale in preview. :) no more off centered white rectangle. But images are still in color. :)
1872 x 936 and 1880 x 940 is continuous at 2:1 70.1/71mb/sec, strange how CF card 5min test only maxes out at 65mb now :/ Photomode and global draw off. least i got continuous though :)
Anyone else noticing file name changes? Dual Iso names stay when disabled and also my raw files are adding an extra number after each recording eg: M23-1307 then it will be M23-1309. Cheers
Ok, 50f68ce14a69 seems to be the most stable build if you're using komputerbay cards. I was able to get stable speed and continuous recording.
But just before changing the build I was trying to get the greyscale preview or the hacked one. I was *never* able to get those, no matter what I choose. What could be the problem?
Quote from: togg on August 23, 2013, 02:51:26 PM
Ok, 50f68ce14a69 seems to be the most stable build if you're using komputerbay cards. I was able to get stable speed and continuous recording.
But just before changing the build I was trying to get the greyscale preview or the hacked one. I was *never* able to get those, no matter what I choose. What could be the problem?
I believe HaCked isn't functional on the 5D Mark II and that ML Grayscale only works in 5x Zoom.
Quote from: ted ramasola on August 23, 2013, 06:58:32 AM
when you attach an external monitor, choose ML grayscale in preview. :) no more off centered white rectangle. But images are still in color. :)
Yeah! Works like a charm! Thanks for the hint :D
Quote from: PressureFM on August 23, 2013, 04:09:04 PM
I believe HaCked isn't functional on the 5D Mark II and that ML Grayscale only works in 5x Zoom.
Oh. Now I understand. Thanks. Anyway I've forget to say that trying the hacked setting I've completely kill the screen. I had to put the card in the computer and delete config and all the build.
I think that the feature should be stripped out if it doesn't work.
Hey guys,
Sorry if this was reported or resolved. But I shot some stuff a couple of weeks ago, used the raw2dng, everything looks great in ACR, the ProRes files look good too. Now, when I try to drop the dngs in Davinci, is not reading the files. A few months ago, around late june, I was able to drop DNG files in Davinci and everything worked great, no problem. Did anything change? am I doing anything wrong?
please help.
thanks!
I checked with the previous shoots I've done and it seems to be a problem with the stuff I shot with either 7'th or 9th of August 5d2 build. Shots from previous builds are loading fine.
hi all
could anyone give me some help to install properly this build on my 5d2, i want to use the dual iso feature
something like a tuto will be perfect...
usually i can make it on my own but i don't understand with this build
i'm trying since a week ,so i advance many thanx!
Quote from: wared on August 24, 2013, 10:56:40 AM
hi all
could anyone give me some help to install properly this build on my 5d2, i want to use the dual iso feature
something like a tuto will be perfect...
usually i can make it on my own but i don't understand with this build
i'm trying since a week ,so i advance many thanx!
http://www.magiclantern.fm/forum/index.php?topic=7139.0
Quote from: Doyle4 on August 24, 2013, 12:01:58 PM
http://www.magiclantern.fm/forum/index.php?topic=7139.0
thank you doyle but i was able to find this one ans it didn't help me so much
What is it you would like to know? :)
why the package seems uncomplete?
i manage to activate the module on my camera but when i take a shot i have a picture with lines, did i miss something?
Quote from: wared on August 26, 2013, 05:40:07 PM
why the package seems uncomplete?
i manage to activate the module on my camera but when i take a shot i have a picture with lines, did i miss something?
Yes, you need to download the cr2hdr (https://bitbucket.org/a_d_/magic-lantern/downloads) program and convert the .CR2 pictures to DNGs.
And next time please look at the FAQ (http://www.magiclantern.fm/faq.html) or the white paper for Dual ISO (https://bitbucket.org/hudson/magic-lantern/downloads).
What's Arkanoid?
Quote from: Doyle4 on August 27, 2013, 09:18:06 PM
What's Arkanoid?
This is (http://en.wikipedia.org/wiki/Arkanoid).
haha, i just realised this when i pressed it on my mkii :P
its what you activate while waiting for your dngs to export proxies or master copy. :)
Hi All :)
Just test the new Built (2013/08/27-8cf76a551872), And what the Heck happen :(
I See a Big Drop in performance, i can Only record 3800 to 4000 Frames @ 1856x1004 23.976
on Lexar 1000x 32GB card.
Before i install the new built i was on the July 11th built, and
on that one i was getting 8000 Frames plus @ 1856x1004 23.976p
So it looks like a 50% drop in performance speed! >:(
Its the same for my 64 GB Lexar 1000x card.
When back to the The July 11th bulit (5db91070a1aa) from A_D_
And my Speeds are Back up to 14,000 Frames @ 75.0 MB/s on 64 GB Card=42GB
& 8000 Frames on my 32 GB card @1856x1004 23.976p =30GB
So are we putting too Many Features at The Cost of Large Stable Frame Sizes?
Like 1856x1004 ??
I see no point and having all these features if you can not record Raw video at it
Max size! Continuous.
I will Stay on the July 11th bulit (5db91070a1aa) from A_D_
Until I can see the Same or better performance @ 1856x1004.
Its nice to have lots of Features but for me, i only need Raw video ;)
im getting continuous at 1880 2:1, try deleting ml config file and try again. i didnt know this trick a.d told me.
wish i had kept my crash logs from few weeks ago, my camera crashed and i did a cf test and i was hitting 91mb... never hit that since, could of been something in the log to see how it happend... i deleted them :( may do a file recovery and see what i can find.
Quote from: reddeercity on August 28, 2013, 01:23:43 AM
So it looks like a 50% drop in performance speed! >:(
Read this: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
and then do the math; the difference in speed is likely 1%, not 50%. Make sure you use the exact same settings.
@A1ex,
Is it best to use 24fps over 23.976 shooting raw? if so is there a post with details please? had a search, found in one they say to use 24p with fps over ride but doesn't really say why, thanks :)
You set it like you would do on any other camera, nothing to do with raw.
Ahh ok cheers, iv been using 23.976 but spotted most people over ride to 24p, ill give it ago. Thanks again.
Quote from: a1ex on August 28, 2013, 03:10:16 PM
Read this: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
and then do the math; the difference in speed is likely 1%, not 50%. Make sure you use the exact same settings.
All my setting are the same, i Turn off everything, Dual ISO, Auto Exp. All the Feature were Disabled.
I tested this 5 Times just in case I made a
mistake. And the results are the Same.
The Reason i Said 50% Drop, is i no longer maintain the same Captured Frames,
And i have exactly Half The numbers of frames that i had on the July 11 built !
at 1856x1004 23.976p 75.0MB/s
You can unload the modules you don't use, see if any of them is slowing it down.
Did you read that link? what settings did you use? (post the config file)
What other modules do you have loaded?
Did you turn off global draw? enabled small hacks?
Seems to be a big problem with this build... most of my images are all corrupt ill post samples now.. going back to last build and see if its the same. Photoshop CC also says that CR2's are not recognised by Photoshop. Update, can open upto 8 files at a time.
Samples:
(http://i43.tinypic.com/154haoz.jpg)
(http://i42.tinypic.com/ouruqr.jpg)
Dual ISO disabled, Auto Expo disabled
(http://i44.tinypic.com/2ujox0m.jpg)
Update: Gone back to Aug 5th Build as that has good read and write speed, good new's is its not my camera that is broke!! Phew, so there seems to be something up with latest build, i thought i had pushed it to far and killed my sensor! good to know the mkii's ok :)
I have kept all CR2's if they are needed Dev's.
Find the first broken build (or, even better, the first broken changeset).
Also try this one: http://builds.magiclantern.fm/jenkins/job/5D2.212/7/artifact/platform/5D2.212/magiclantern-v2.3.NEXT.2013Aug28.5D2212.zip
(I didn't try it, but will do tomorrow if you can't find it)
Also, I didn't do any speed tweaks lately, so why do you say aug 5 has good read and write speed?! It shouldn't have slowed down.
Cheers A1ex will try that one now.
The 16th Aug is the first one i have ever had problems with.
On the 5th Aug build i was hitting 97mb write on the 5min bench test. Iv just done one now and its the same as usual 68/70mb. think the test i did few weeks back was a lucky go.
Try compiling without this and see if it changes anything:
https://bitbucket.org/hudson/magic-lantern/commits/fa0ef0e6150f27c5e63ff6adb262766fa3f7a8dd
Not one corrupt image on magiclantern-v2.3.NEXT.2013Aug28.5D2212.zip Thanks, took about 45 pics and all clean.
Ill be honest and say I dont have a clue how to compile, thank you for putting it across though and thanks for a working build.
In modules next to the names it says OldAPI wrong version, not sure if you knew or not.
Next, try the extras from the problematic build (maybe enable them one by one) and see which one breaks. I'm not sure what extras are there (autoexpo, arkanoid?)
Also try to unload the modules that you don't use (or unload all of them, then enable them one by one).
Once you isolate the thing that's causing the problem, we know what to do (reproduce and fix).
QuoteIn modules next to the names it says OldAPI wrong version
All of them?!
Then, no modules were loaded, so the problem is caused by one of them.
okie doke, going to do that now.
@reddeercity
you could delete the other modules which you don't use and copy back if you need it.
For RAW Video with minimal setup:
raw_rec + file_man and maybe ettr
@Doyle4
For Photo:
ettr + auto_expo+dual_iso+ file_man
Sorry i was meaning OldApi on the magiclantern-v2.3.NEXT.2013Aug28.5D2212.zip build before swapping with the 27th build.
autoexpo ok, ettr ok, rest are all OldApi (magiclantern-v2.3.NEXT.2013Aug28.5D2212.zip build)
magiclantern-v2.3.NEXT.2013Aug28.5D2212.zip with 27th extras
All ok apart from Pic View,
sounds stupid, but how do i disable a loaded module? cant see the option.
@ a.d
ettr + auto_expo+dual_iso+ file_man modules were loaded but not enabled.
I enabled dual iso later on during the day but my first few images were standard.
@a.d, Sorry i get what you are saying now, dont load all modules, only ones you need for Photo or Video.
No corrupt images with v2.3.NEXT.2013Aug28.5D2212 and a.d's 27th Aug Modules with the game deleted from CF, all modules were enabled also.
Cant be the game can it?
ill do more testing tomorrow for sure though.
Thanks for all the help.
Update: Think its the RAW_rec module, i have corrupt raw frames, if it is the raw_rec module would it do that to the images i were taking? as a.d pointed out, i had all modules loaded.
27th Build whilst recording in RAW the LCD glitches and flickers, im sure its to do witht eh rec module, sorry if im wrong. rest of the modules seem to be fine.
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
I have no idea what do you mean by "LCD glitches and flickers"...
Sorry about that, iv read that so many times too.
Whilst filming in RAW mode i noticed the camera's back screen looked strobed effect for a split second or two, Here is an example of what happned http://www.youtube.com/watch?v=Sm896oIzmws sorry its a laptop but couldnt find one on a DSLR.
i know for sure auto brightness was off and set to manual also. i would film it but to be honest im scared it may ruin my sensor if i chose too, its the only camera i have im afraid.
Iv also formatted the card too and lost footage/photo's im afraid also, in another post i said i had them if you needed them, sorry about that :-\
Anyone with komputerbays could say if the last release has stable speed?
Is there any way at all to get around the 4gb limit thing?
https://vimeo.com/68473652
That's the only thing I've been able to find with how to deal with that on a Mac. Everything else I see is for Windows. Is this actually the best/only thing I can do?
EDIT: I tried the cat command the person mentioned in the comments so I guess that's a better way to do all of this.
Hi friends,
I've come upon a 5Dm2 and a 7D. I must sell one soon, but am tempted to see how the 7D raw turns out. Do you guys see the 7D surpassing the 5Dm2 possibly with it's dual processors and higher buff?
Ah I'm also torn because the 7D looks and feels so solid / modern!
Quote from: teryoon on August 29, 2013, 04:48:05 AM
Is there any way at all to get around the 4gb limit thing?
https://vimeo.com/68473652
That's the only thing I've been able to find with how to deal with that on a Mac. Everything else I see is for Windows. Is this actually the best/only thing I can do?
EDIT: I tried the cat command the person mentioned in the comments so I guess that's a better way to do all of this.
It's easy.
- Open Terminal
- Write "cat"
- Drag'n'drop the first Mxx-xxxx.RAW file onto Terminal
- Drag'n'drop the next Mxx-xxxx.R00 file onto Terminal
- Add all the other Mxx-xxxx.Rxx files into Terminal like above
- Proceed to write ">"
- Then write the destination file (I usually just drag'n'drop the first file ending in RAW and renaming it)
- Push Enter and let the magic begin
Example:
cat /Volumes/Scratch\ Disk/RAW/M29-0830.RAW /Volumes/Scratch\ Disk/RAW/M29-0830.R00 > /Volumes/Scratch\ Disk/RAW/M29-FINI.RAW
Quote from: togg on August 29, 2013, 02:38:11 AM
Anyone with komputerbays could say if the last release has stable speed?
Latest build aug 27 stable. Almost same speed as aug 16.
Tested with Komputerbay 64gig and 256gig.
re. speed drops on updates. I know it doesn't help to isolate problem modules but I had a massive speed drop when I updated to the Aug. 16 build. (komputerbay 64gb) I couldn't find any problem module or setting when systematically shutting them down. I then decided to format the card on my card reader and re-install ml. That worked fine and speed returned to what it had been with the previous build.
Goofing around with older builds, which I got faster write speeds with in normal 1x mode.
Tested several versions and went back to build 31302bbc6461 and for some reason I can't get continuous shooting in 3x mode now, as I used to. Stops recording as soon as it hits around 200 frames (running out of memory)? :o
As an idiot I didn't save my earlier Magic Lantern installation ... so have to test them all now.
Update: Don't worry, I'm just an idiot. Forgot to enable FPS Override :P
Quote from: PressureFM on August 29, 2013, 08:42:11 AM
It's easy.
- Open Terminal
- Write "cat"
- Drag'n'drop the first Mxx-xxxx.RAW file onto Terminal
- Drag'n'drop the next Mxx-xxxx.R00 file onto Terminal
- Add all the other Mxx-xxxx.Rxx files into Terminal like above
- Proceed to write ">"
- Then write the destination file (I usually just drag'n'drop the first file ending in RAW and renaming it)
- Push Enter and let the magic begin
Example:
cat /Volumes/Scratch\ Disk/RAW/M29-0830.RAW /Volumes/Scratch\ Disk/RAW/M29-0830.R00 > /Volumes/Scratch\ Disk/RAW/M29-FINI.RAW
Wow thank you so much! I had no idea you could just drag and drop the files like that hahaha. You're a life saver.
It would be so helpful if a dev could set an override on all the small hacks when RAW video is enabled and youre in live view, then revert back to whatever was set before when you switch out of live view. Reason is, I'm a still photographer, and there's so many hacks and settings to set before RAW video (to enable large enough buffer and consistent fps), and these are easy to forget and easy to forget to revert when shooting stills. Its bothersome and dangerous. Something like a Custom Setting would work.
Quote from: teryoon on August 29, 2013, 04:48:05 AM
Is there any way at all to get around the 4gb limit thing?
https://vimeo.com/68473652
That's the only thing I've been able to find with how to deal with that on a Mac. Everything else I see is for Windows. Is this actually the best/only thing I can do?
EDIT: I tried the cat command the person mentioned in the comments so I guess that's a better way to do all of this.
It's even easier:
RAWMagic (http://www.magiclantern.fm/forum/index.php?topic=6218.0)
This programm creates dng files directly from spanned files. So, you
don't need to 'cat' them first!
Quote from: guentergunter on August 29, 2013, 07:39:01 PM
It's even easier:
RAWMagic (http://www.magiclantern.fm/forum/index.php?topic=6218.0)
This programm creates dng files directly from spanned files. So, you don't need to 'cat' them first!
I don't have anything to test with right now since I'm not at home, but do I just drag the .RAW and .R00 file into the program or just the .RAW file? I actually use RAWMagic, I just had no idea it was capable of doing that.
Quote from: teryoon on August 29, 2013, 09:17:30 PM
I don't have anything to test with right now since I'm not at home, but do I just drag the .RAW and .R00 file into the program or just the .RAW file? I actually use RAWMagic, I just had no idea it was capable of doing that.
Due to Apple's sandbox system you need to drag all the files. But then it'll work seamlessly ;)
Last Built 8cf76a551872
Thank You For DSLR arkanoid i was laughing to tears.
You made my day
I love you People !
Hey guys, I'm joining the 5D Mark II raw club :) Have been shooting with a 50D for a while but got a nice deal on a 5D II.
Installed the latest build yesterday, with my Komputerbay 64GB card i'm getting about 75Mb/s. I rarely record very long takes so 1880 or 1872 in 16:9 is quite usuable, which is nice!
Planning to use it for anamorphic at 1600x1250 as well. Will share some stuff soon!
Would love to see more real world examples of the VAF 5D2b in action on raw (preferably downloadable 1080p files). The aliasing is the only thing I don't like about the 5D2 raw...
Quote from: JulianH on August 30, 2013, 10:50:45 AM
Hey guys, I'm joining the 5D Mark II raw club :) Have been shooting with a 50D for a while but got a nice deal on a 5D II.
Installed the latest build yesterday, with my Komputerbay 64GB card i'm getting about 75Mb/s. I rarely record very long takes so 1880 or 1872 in 16:9 is quite usuable, which is nice!
Planning to use it for anamorphic at 1600x1250 as well. Will share some stuff soon!
Would love to see more real world examples of the VAF 5D2b in action on raw (preferably downloadable 1080p files). The aliasing is the only thing I don't like about the 5D2 raw...
Welcome to the club! You made me curious, what Anamorphic do you have / plan to get? Anamorphics have been bugging me for a long time, RAW seems ideal to harvest their full potential... but as you have pointed out a mosaic engineering filter should be the first investment!
Quote from: Africashot on August 30, 2013, 11:11:57 AM
Welcome to the club! You made me curious, what Anamorphic do you have / plan to get? Anamorphics have been bugging me for a long time, RAW seems ideal to harvest their full potential... but as you have pointed out a mosaic engineering filter should be the first investment!
Thanks :)
I have too many anamorphics actually... ;) Kowa B&H (2x), ISCO Optic Ultrastar (2x), super small Petit Cinevision (1.5x), Iscomorphot 8/2x.
I have been using them with my Panasonic GH2 mostly. You can check my video's on Vimeo. (https://vimeo.com/user3681587/videos/)
Here's a video I shot with the Kowa B&H on the 50D in 4:3 raw:
And a clip I shot 3 months ago with the Kowa B&H on a borrowed 5D II:
I've ran some speed tests and indeed, there was a roughly 2% speed drop from CONFIG_TSKMON.
But to say it was 50%?! That's trolling :D
Quote from: JulianH on August 30, 2013, 12:20:21 PM
Thanks :)
I have too many anamorphics actually... ;) Kowa B&H (2x), ISCO Optic Ultrastar (2x), super small Petit Cinevision (1.5x), Iscomorphot 8/2x.
I have been using them with my Panasonic GH2 mostly. You can check my video's on Vimeo. (https://vimeo.com/user3681587/videos/)
Here's a video I shot with the Kowa B&H on the 50D in 4:3 raw:
And a clip I shot 3 months ago with the Kowa B&H on a borrowed 5D II:
Thanks for posting! I wish I could say the same one day; having too many anamorphics I mean! Loved seeing the 50D perform here, off-topic: the location of that video; is it Arnhem?
Thanks again!
It's Den Haag! Even though I have quite a few anamorphics, I'm still looking for other ones... ::) Would love to have an Iscorama but prices have gone trough the roof. The days of the bargains are over or you have to be incredibly lucky. Not planning on keeping all the lenses I have either. After switching camera's the past few months I'm planning to settle down with the 5D2.
Hi guys,
Sorry to just come flying in here with questions I'm sure have been answered.
What's the longest recording time on 5d2?
What's the largest reliable resolution (is it 1880x1080)?
How did you all overcome the 4GB FAT file size limit?
I plan to use raw video in the field, how dangerous are these nightly builds in your opinion?
And realistically is my camera in danger, or really just my cards?
I'm on the verge of purchasing two 64GB Lexar 1000x cf cards for my 5d2 but am finding it hard to commit to this. Any help would be incredible!
Thanks
Dylan
I did my first video completly with RAW Workflow on my 5D2.
It's a promo video for the company i'm working for. I'm not a pro... just a screen designer with some ambitions in video. Hope you like it.
@Spring Pictures
QuoteWhat's the longest recording time on 5d2?
That is totally dependent on your settings and card size, but maxed out(75 MB/s) continuous recording on a 64GB card would be around 15 minutes I believe. If the max data rate is 73-75 MB/s so you can do the math, also lower resolutions have lower data rates and longer record times.
QuoteWhat's the largest reliable resolution (is it 1880x1080)?
Yes I believe some with KomputerBay cards have had near continuous at this resolution, for me my highest continuous resolution on my 1000x promaster card is 1880x940.
QuoteHow did you all overcome the 4GB FAT file size limit?
ML automatically splits to a new file once the limit is reached with no frame loss, the files are then recombined on a computer so the 4GB limit is no longer a factor.
QuoteI plan to use raw video in the field, how dangerous are these nightly builds in your opinion?
It is Alpha software and there is always a chance for bugs, however it has been very reliable for me I have not had any issues since May its has been pretty rock solid for me. But as an example, one of the latest builds caused massive speed loss on some cameras until the memory card was formatted and ML re-installed. No big deal but could be a big problem if it was discovered out in the field. I would recommend testing any new build before use.
QuoteAnd realistically is my camera in danger, or really just my cards?
Yes your camera could be damaged, although I have no fear or reservations about using ML and if it were to destroy my camera I couldn't afford to get a new one. At the heart of ML is a firmware update that enables the camera to boot software from the card. Any time you update the firmware on any device you risk bricking it, ML is no exception. There are other risks as well such as software causing the camera to lockup and overheat or some new feature pushing the sensor to hard and frying it. That said I use it and I have installed and used it on my company camera as well. Also the Dev's here are awesome and they really want to give us something that is safe and reliable, they are very carefully and strict about restricting new developments that could damage a camera and stuff generally doesn't get into a nightly build until it is fairly refined.
All I can say is. I have ML installed and I use raw video in the field, what you decided will be up to you.
Wow @bnvm what a fantastic reply! Thank you so much.
Played with build from 08/16 - on Transcend 16GB the speed was like previous build.
Still have to learn how to handle this one as a movie camera :-)
Sorry for the focus pulls and shaking image. Still - I really enjoy the sharp and tonal richness of the RAW video - AWESOME WORK guys!
Nice speed increase in latest build :)
Hitting 101mb read and 83.8mb write :) nice work!
Update: 1880 2:1 = Continuous, nice
My new Komputerbay 64gb card worked like a charm. It went so smoothly with no errors or freezing up at all. Check out the video I made with it!
https://vimeo.com/73503780
Hey all :)
Speed look like its back up to continuous for me
at 1856x1004 23.976p 75.0MB/s on Lexar 1000x 32GB= 9800 frames Full Card
And on my Lexar 1000x 64GB card i still have a road block @ 42GB 1856x1004 23.976p.
But one thing i have noticed is if you Format your card in Camera before
Recording, There is less Buffering going on. If i don't Format my card before recording i can not maintain
continuous recording at 1856x1004 , After all the testing it time to
go to Sleep, have good night all :D
A few test shots. ISO 1600/3200 with 50mm f/1.4 @ 2.0. Shot at 1856 x 1044.
Applied a Arri Lut in Resolve and stabilized some shots a bit, thats about it.
I wish Resolve would handle the raw files better. In ACR the aliasing/moire is a bit less bad. But I like the speed of the Resolve workflow... hard to beat that.
Quote from: JulianH on September 01, 2013, 03:01:02 PM
A few test shots. ISO 1600/3200 with 50mm f/1.4 @ 2.0. Shot at 1856 x 1044.
Applied a Arri Lut in Resolve and stabilized some shots a bit, thats about it.
I wish Resolve would handle the raw files better. In ACR the aliasing/moire is a bit less bad. But I like the speed of the Resolve workflow... hard to beat that.
ISO 1600/3200? Did you use the Dual ISO module for RAW Video recording and what about ETTR?
No, some shots iso 1600, some 3200. I don't use ETTR, don't see the point for video, I just use manual exposure.
JulianH, nice job! Impressed with how clean the footage looks at 1600 and 3200? Do you notice a lot of noise when zoomed in or on a bigger screen?
I used the 5d2 raw as a bcam on a short recently and I didn't notice any significant ailiasing until I shot a close up of a piece of paper with a chart on it and the coloring on the lines of the table was off for that.
Btw with the newest build I can record 1880x1016 @ 1.85 quite long (stopped out at around 6minutes). Sustained recording speed around 76.4-77MB/S on a Komputerbay 1000x 64GB.
Hello everyone.
It seems I've been missing something with the latest built because the modules are loaded, but can't turn them on. Can't do RAW.The modules are disabled
got the same problem with the aug 30th build :-[
Quote from: lespurs on September 01, 2013, 07:38:50 PM
got the same problem with the aug 30th build :-[
You have to manually turn them on
There are off by default
Go in to the submenu turn on the
Modules you what .
Then reboot the camera
And they will be there. :)
Quote from: reddeercity on September 01, 2013, 07:50:19 PM
You have to manually turn them on
There are off by default
Go in to the submenu turn on the
Modules you what .
Then reboot the camera
And they will be there. :)
thanks ;)
got it! THANKS!
Just a quick note about frame size on the new Built 08_30_
Testing larger frame sizes, at 1872x1012 23.976p 75.3MB/s for 4000 Frames :)
For me i need the larger 16x9 ratio, for paid work. 1856X1004 works for me but
i would like to see 1872x1004 Continuous.
So i'm always pushing for larger stable frame sizes.
But i still see a 42 GB Wall for 2048x940 23.976p this is the Same for 1856x1004 ?
There is little buffing until 41GB then the Buffer Maxs. out then stops at 42 GB every time, on Lexar1000x 64GB.
Has any One being able to record over 42GB at 1856x1004 23.976 on 64GB Cards of any make ?
I was wondering if anyone could give me some good Time Lapse setting tips, also HDR video tips and if there is any way to do HDR Time Lapse what should my settings be? Thank for any feedback
Hello everyone!
I am new to the forum. At first i wanted to thank everybody at Magic Lantern for your great work! The last build had a really impressive speed increase. Now i am able to record 1872x1016 continuously up to 42GB or 13000 frames , i think it was... with Komputerbay 64gb 1000x @ 75,9 - 76,3 MB/s / hacked mode / global draw off .
(its the second Komputerbay card..the first had to be replaced after smoe days...).
In the quality settings i choose "pure" RAW at the moment. Or does anyone use smaller/compressed quality settings like sRAW?
When shooting RAW video, change the quality settings to small jpeg! this gives you 32 of memory rather than 28 :) changing to jpeg will still allow you to record in RAW btw so dont panic about changing it :) get rid of all RAW quality settings for RAW video.
Quote from: dariSSight on September 02, 2013, 11:28:19 AM
I was wondering if anyone could give me some good Time Lapse setting tips, also HDR video tips and if there is any way to do HDR Time Lapse what should my settings be? Thank for any feedback
There are some good topics on here, best looking at workflows etc, best place to start is the search bar :) this section is mainly for 14-Bit RAW video Builds for 5D2 :)
Quote from: Doyle4 on September 02, 2013, 05:28:10 PM
When shooting RAW video, change the quality settings to small jpeg! this gives you 32 of memory rather than 28 :) changing to jpeg will still allow you to record in RAW btw so dont panic about changing it :) get rid of all RAW quality settings for RAW video.
Thank you! I will try that... maybe then i will pass the 42-43gb barrier(1872x936, 14000 frames..43gb). I guess THAT will save me a lot of postprocessing time as well...
no problem,
I think the mkii can only store upto 42gb not too sure why but im sure its explained somewhere on here.
Some other settings to try too:
Canon Menu
photo=small jpeg
Auto power off=OFF
LCD Brightness=manual
White Blance=Auto OFF
ML Menu
ETTR=Off
FPS override = set to exact 24
in the Raw Video tab
set previews to Auto
recording frame=White rect
Small hacks= On
Thank you very much! Ok i will look for that 42gb thing...
The settings were exactly as you posted, except the whitebalance...and small jpeg of course :-)
i can confirm the 42GB limit exist on Komputerbay 64GB 1000x card.
Hello everyone...after a very hard work..Urban Sniper tells the story of a professional shooter who finds himself in a situation that goes beyond his experience.
Shot entirely in Magic Lantern Raw
Enjoy :)
http://vimeo.com/lodiamont/urbansniper
Quote from: mihaii on September 02, 2013, 06:06:59 PM
i can confirm the 42GB limit exist on Komputerbay 64GB 1000x card.
Thanks for confirming this :)
today i had a short talk about this problem,
with my friend who is a IT/Programmer who specialize in "Thin ware"
which is running software on very low CPU cycle, something like that.
So he was say that blocks are now being recognize at some point in the recording process
and stops because it dose not know where to go, of course he was talking Over my head
But i think i understand the what he was saying.
All in all at best this is speculations by me and my friend, so take it with a grain of salt ;)
Quote from: reddeercity on September 02, 2013, 09:08:04 AM
But i still see a 42 GB Wall for 2048x940 23.976p this is the Same for 1856x1004 ?
There is little buffing until 41GB then the Buffer Maxs. out then stops at 42 GB every time, on Lexar1000x 64GB.
Has any One being able to record over 42GB at 1856x1004 23.976 on 64GB Cards of any make ?
Reddeercity,
I wasn't able to reply to this as i had to go back to some older notes I made for testing the KB cards,
regarding the 42gig limit, this was discussed by me and KB techsupport but it was a short conversation, I do rememeber that I reported several resolutions seem to stop around that size, approx 42.6 gig and yes it was mentioned that certain technical issues cause this. I forgot the details but it is.
Further tests, and I have also exceeded that with "manageable" resolutions but I recently stopped doing capacity stress tests as the cameras I use, the 5d2 and 7D would begin to get hot and smell exceeding the 70gig mark. Obviously these cameras were made when these capacity did not yet exist and also, originaly they were meant to stop movie recording at 4gig.
For your reference, using the 128 gig 1000X
1872 x 748 2.50:1 = continuous till full.
1856 x 790 2.35:1 = 19,192 or around 50 gig
1856 x 742 2.50:1 = 43,156 or around 100 gig
but curiously a lower res stops at 42.6
1728 x 972 16:9 = 15,578 around 42.6 gig
Quote from: ted ramasola on September 03, 2013, 02:41:12 AM
Reddeercity,
I wasn't able to reply to this as i had to go back to some older notes I made for testing the KB cards,
regarding the 42gig limit, this was discussed by me and KB techsupport but it was a short conversation, I do rememeber that I reported several resolutions seem to stop around that size, approx 42.6 gig and yes it was mentioned that certain technical issues cause this. I forgot the details but it is.
Further tests, and I have also exceeded that with "manageable" resolutions but I recently stopped doing capacity stress tests as the cameras I use, the 5d2 and 7D would begin to get hot and smell exceeding the 70gig mark. Obviously these cameras were made when these capacity did not yet exist and also, originaly they were meant to stop movie recording at 4gig.
For your reference, using the 128 gig 1000X
1872 x 748 2.50:1 = continuous till full.
1856 x 790 2.35:1 = 19,192 or around 50 gig
1856 x 742 2.50:1 = 43,156 or around 100 gig
but curiously a lower res stops at 42.6
1728 x 972 16:9 = 15,578 around 42.6 gig
Thanks Ted for your Information, i have no tried those sizes.
It looks like the problem is when the Horizontal resolution increases
above 800 pixels that when the problem starts.
It may indicate that we could reaching a limitation here.
I will try to fill my 64GB card at a Horizontal less then 800 pixel(1880x800)
then go above that until see what res. stops recording.
For now i will Know to stop at about 40 GB and then restart.
Just like h264, :o i had an idea , if we could implement auto record start when we hit
40 GB just like h264 at the 4 GB mark . Then it would almost be like continuous recording,
Just a thought :)
My concern is really the heat. At past 40 gig, I think your good as most takes really don't get to be that long.
If you need to get creative in say, landscapes, you can use FPS over ride and shoot at lower framerate to really have longer record time, and I think with lower fps, heat will take longer to build up.
Here's a music video I shot with the RAW module.
Quote from: mihaii on September 02, 2013, 06:06:59 PM
i can confirm the 42GB limit exist on Komputerbay 64GB 1000x card.
Probably unaware of its own limitations; my KB 64 gig card did 53.4 gb in 1856x1004 yesterday!
Quote from: ted ramasola on September 03, 2013, 05:23:59 AM
My concern is really the heat. At past 40 gig, I think your good as most takes really don't get to be that long.
If you need to get creative in say, landscapes, you can use FPS over ride and shoot at lower framerate to really have longer record time, and I think with lower fps, heat will take longer to build up.
Yes you are Right, i just what to know my limitations so i know how to Plan my shoots.
i do mostly Interviews which are about 5 to 10 Minutes takes.
Do you use frame over ride on all the time or something, i notice you said "you can use FPS over ride"
i always have it on , just wondering .
Quote from: reddeercity on September 03, 2013, 05:52:54 AM
Yes to are Right, i just what to know my limitations so i know how to Plan my shoots.
i do mostly Interviews which are about 5 to 10 Minutes takes.
Do you use frame over ride on all the time or something, i notice you said "you can use FPS over ride"
i always have it on , just wondering .
with the 5d2, if your always using raw, I guess its best practices to have it always on at 23.976 so that when you use crop mode(which is 30p by default) you are always at 23.976 with fps override.
also when using "creative artsy shots" like wide cityscapes or landscapes you can use lower FPS to get timelapse effect and also longer record times with higher resolutions.
Quote from: ted ramasola on September 03, 2013, 05:57:05 AM
with the 5d2, if your always using raw, I guess its best practices to have it always on at 23.976 so that when you use crop mode(which is 30p by default) you are always at 23.976 with fps override.
also when using "creative artsy shots" like wide cityscapes or landscapes you can use lower FPS to get timelapse effect and also longer record times with higher resolutions.
Thanks for the tips :)
i just tried 1872 x 748 2.50:1 , and my card stop at 60 GB,
i guess Lexar 1000x are not as fast as KB.
So i'm good we 1856x1004 for 40GB. at lest i know i will get 9 Safe minutes.
Note that if you have a 64 gig card it won't actually give you 64gig but
59.6 GB (63,997,534,400 bytes), so you actually filled up your card. :)
in my test with 1728 x 972 at 24P
thats a Length/duration of: 15:08 min
# frames: 21,763
Quote from: ted ramasola on September 03, 2013, 06:40:13 AM
Note that if you have a 64 gig card it won't actually give you 64gig but
59.6 GB (63,997,534,400 bytes), so you actually filled up your card. :)
in my test with 1728 x 972 at 24P
thats a Length/duration of: 15:08 min
# frames: 21,763
Yes , i see my mistake in math.
i ended up with 24,850 at 23.976p 1872 x 748 = 17.2 min.
Quote from: dossisman on September 03, 2013, 05:32:08 AM
Here's a music video I shot with the RAW module.
Very nice indeed!
Quote from: dossisman on September 03, 2013, 05:32:08 AM
Here's a music video I shot with the RAW module.
Very nice!
Do you wanted that cyan magenta look specially or it is from Resolve?
Best regards
Hello! Sorry for my English) What frame rate real make Canon 5d markII?
All my tests have drop frame ( every 5 ) with strobe effect , or low speed 20-21 fs with time laps effect) and trouble sound synchronization....
Please help))) memory card 64gb 1000x
I can look good raw tests on youtube, but don't no where my error...
Thank you so much!
QUESTION! What ratio are you shooting at to stretch the entire 1080p and how are you resizing it? I cant figure it out.................
Hello 5d2 forum folks,
I've been hanging out in the 50D forum for awhile but I think I'm ready to put the RAW on my 5D. I know there are many builds out there but I'm wondering what is the latest "stable" build that people are liking. Not looking for any frills more on the stable end. Any links would be great, I know that the latest aren't on the main page.
Thanks All!!!!
it's on the first post.
Thanks!
The teal/orange grade was applied in post. The Resolve round-trip workflow gave me problems with Premiere, so I ended up grading everything in After Effects.
Quote from: rawmania on September 03, 2013, 02:20:20 PM
Very nice!
Do you wanted that cyan magenta look specially or it is from Resolve?
Best regards
Thank you!
I wanted to put the camera through it's paces and this video was perfect for it. Dark scenes for the performance, daylight scenes for the story. I LOVE the post flexibility of the Raw module.
Quote from: Doyle4 on September 03, 2013, 01:22:25 PM
Very nice indeed!
What are the .EN files (RAW REC.EN, ETTR.EN, DUAL_ISO.EN, FILE_MAN.EN and AUTOEXPO.EN) that appears on my CF card?
If this is not appropriate for this forum, I apologize and feel free to remove it. I'm selling a brand new VAF-5D2b Moire / Aliasing Filter. If anyone is interested, PM me.
a.d. , maybe you can help me somehow? Can't get usb stream while RAW Video is ON.
http://www.magiclantern.fm/forum/index.php?topic=8081.0 (http://www.magiclantern.fm/forum/index.php?topic=8081.0)
Thanks!
is the possibility to record past the 4gb limit baked into the ML raw module by default; or do I need to tweak something to make it happen past 4gb? THANKS
Quote from: pointbob1 on September 04, 2013, 04:34:35 PM
is the possibility to record past the 4gb limit baked into the ML raw module by default; or do I need to tweak something to make it happen past 4gb? THANKS
its a fat32 limitation. exfat formated cards like the mark iii has can record past 4gb.
what magic lantern does is that it will keep recording, but it will break down the files into <4gb files.
what you then do, is a simple drop and drag of those spanned files into a program like rawanizer/raw2cdng and the utility will automitically process those files into a single DNG sequence.
Quote from: pointbob1 on September 04, 2013, 04:34:35 PM
is the possibility to record past the 4gb limit baked into the ML raw module by default; or do I need to tweak something to make it happen past 4gb? THANKS
Or use RAWMagic if you're on a mac.
S.B. Please helps me how to do the post processing work.
I have shot raw video on 5d2 and try the post processing work but get stuck.
I have donwloaded the DaVinci Resolve Lite 9.1.6 and don't know how to work thing out?
I try to find 9.1.5 ver. but there is none on their website (http://www.blackmagicdesign.com/).
Thank you in advance.
dd2020
Quote from: dd2020 on September 05, 2013, 07:23:37 PM
S.B. Please helps me how to do the post processing work.
I have shot raw video on 5d2 and try the post processing work but get stuck.
I have donwloaded the DaVinci Resolve Lite 9.1.6 and don't know how to work thing out?
I try to find 9.1.5 ver. but there is none on their website (http://www.blackmagicdesign.com/).
Thank you in advance.
dd2020
What platform are you on ? PC, Mac
Personally i stay away from Resolve, it's "node" basic and very hard to work with even professional
have a hard Time.
So if you are new to all this, use the "KISS Method" (keep it simple etc..)
if you have Adobe products its a simple workflow.
My workflow is :
Raw>DNG's>Photoshop-Tiff's>After Effects-ProRes4444
Then import to Final Cut ProX>edit>export master ProRes or H264.
So if you can give me some info i can see if i can help. ;)
Thanks so much for your generosity reddeercity.
I run on PC platform.
Would you please explain more on the part "Raw to DNG's" ... how to do that?
: )
You can go even simpler and skip photoshop.
Open DNGs in AE , do basic grade- export to whatever your NLE uses.
If you are in PC use RAWanizer to convert raw clips to DNGs.
Rawanizer automatically merges split files, its a windows interface and no more manual merging of split files via command line.
As you chug along using Raw you will realize the export of footage from AE takes a long time. Thats why learning Resolve was a must for me since it is much faster.
Say what takes an hour in AE will only be approx 30 min in resolve.
Quote from: dd2020 on September 05, 2013, 08:13:42 PM
Thanks so much for your generosity reddeercity.
I run on PC platform.
Would you please explain more on the part "Raw to DNG's" ... how to do that?
: )
That's the easy parts, i run on both Platforms.
I will assume you are having problems with the extractions of the DNG's.
So the first thing you need to do is if you have multiply spanning files.
you need to combine them, to do that's you will need the Command line.
so go to the start tab on window "7" type "cmd.exe"
that will being up the Command prompt window.
from there navigate to the folder that holds the Raw file.
to combine type:" copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
where (xyz=name of file) & xyz.Raw at the end is the new name of the file,
this must be different from the original name of the raw file.
take the raw combine file or the single raw file if under 4GB.
open up raw2dng.exe, if you don't have it download it
https://bitbucket.org/a_d_/magic-lantern/downloads/5D2_WIN_raw2dng.zip
drop & drag the raw file on the App.
make sure that raw file is in a new folder.
that about it. if you still have problems let know :D
The only thing about resolve is that you get the pink fringing when you import the dngs, with AE the footage is very clean and looks great. I don't use resolve for that reason, even though it's faster.
Quote from: gtsofilms on September 05, 2013, 09:49:54 PM
The only thing about resolve is that you get the pink fringing when you import the dngs, with AE the footage is very clean and looks great. I don't use resolve for that reason, even though it's faster.
I've noticed the pink fringing as well but apparently they're not there, or they are so minimal in the exported file. In cases where it does show is when aggressive sharpening was applied, but the magenta channel can be tweaked.
Quote from: ted ramasola on September 05, 2013, 09:54:20 PM
I've noticed the pink fringing as well but apparently they're not there, or they are so minimal in the exported file. In cases where it does show is when aggressive sharpening was applied, but the magenta channel can be tweaked.
Is this the kinda stuff that looks like chromatic abberation?
yep but in my experience it's been much heavier than normal CA from lenses. The files I've exported from Davinci have had lots of magenta casts to the point where it's unusable.
ML Raw is quiet reliable for serious work, thanks to developers!
That's video that I've made:
Shot on Canon 5D2 in Raw, some footage on 5D3 Raw (00:02-00:19, 00:36-00:56)
5d mk2 ML Raw July build, got up to 18-25 sec with 64Gb Transcend 1000x
Adobe After Effects + editing in Premiere Pro
Quote from: gtsofilms on September 06, 2013, 02:27:14 AM
yep but in my experience it's been much heavier than normal CA from lenses. The files I've exported from Davinci have had lots of magenta casts to the point where it's unusable.
Yeah shots especially out in sunlight are like this. Terrible. So how do I fix this? Defringe in post?
Greetings from the shadows.
Been wanting to register for a long time.-
First off. thank you for giving me a new cinema camera, a.d, alex and all the other developers ! I love you!
I've had no problems to speak of with the raw builds, camera has only crashed twice since RAW first was released.
But I just can't get full resolution out of crop mode. There is a black border to the right of the frame, some 30 pixels or maybe more. I read awhile ago that you had to move the Focus box 8 times left and 7 times up or something like that, but I can't find that post in this thread. Also tried "Center for 5x RAW" in focus box settings, but that too gives me the black border. Can someone redirect me or tell me what I need to do to get full res out of the Crop mode?
Thank you,
Kharak.
Quote from: Kharak on September 06, 2013, 11:39:36 AM
Greetings from the shadows.
Been wanting to register for a long time.-
First off. thank you for giving me a new cinema camera, a.d, alex and all the other developers ! I love you!
I've had no problems to speak of with the raw builds, camera has only crashed twice since RAW first was released.
But I just can't get full resolution out of crop mode. There is a black border to the right of the frame, some 30 pixels or maybe more. I read awhile ago that you had to move the Focus box 8 times left and 7 times up or something like that, but I can't find that post in this thread. Also tried "Center for 5x RAW" in focus box settings, but that too gives me the black border. Can someone redirect me or tell me what I need to do to get full res out of the Crop mode?
Thank you,
Kharak.
What exactly do you mean by full resolution?
Quote from: PressureFM on September 06, 2013, 11:44:18 AM
What exactly do you mean by full resolution?
Say I record in 2:35.1 in 3x crop mode. I record in 2152x918 or something like that (don't have camera here). The DNG's I extract say 2152x918, but looking at the DNG's, the right side of the frame has a black border, something like 30 pixels on the entire right side of the frame are black. So I have to crop the DNG's and actually have 2122x918.
So what I am asking is, how do I get full resolution out of the crop mode?
EDIT: I will post a frame so you can see what I mean.
Update: How do I post images?
Are you sure you are using (one of) the newest build(s)? This black border thing was common in the early days of ML raw.
Quote from: JulianH on September 06, 2013, 07:44:54 PM
Are you sure you are using (one of) the newest build(s)? This black border thing was common in the early days of ML raw.
Yes, I have newest build (2013.04.09) and I have experienced the same in every build since I started playing with crop mode.
I must admit, I did find it weird that I did not hear anyone else speak of this issue.
Maybe a complete re-install of ML will help?
What is the fastest workflow in Windows? I would like to convert the raw files to a flat profile to edit right in Premiere.
BTW, I saw a video doing 50 or 60fps on the MK II, does anyone know how it's done?
Quote from: Kharak on September 06, 2013, 12:26:58 PM
Say I record in 2:35.1 in 3x crop mode. I record in 2152x918 or something like that (don't have camera here). The DNG's I extract say 2152x918, but looking at the DNG's, the right side of the frame has a black border, something like 30 pixels on the entire right side of the frame are black. So I have to crop the DNG's and actually have 2122x918.
So what I am asking is, how do I get full resolution out of the crop mode?
EDIT: I will post a frame so you can see what I mean.
Update: How do I post images?
I just tested this resolution using aug 30 build. DNGs turn out ok . no black borders.
edit:
Just tested with sep 4 build . no blsck borders, dngs are ok.
Quote from: ted ramasola on September 06, 2013, 11:06:27 PM
I just tested this resolution using aug 30 build. DNGs turn out ok . no black borders.
edit:
Just tested with sep 4 build . no blsck borders, dngs are ok.
Thank you for testing this on my behalf.
This clearly shows it has something to do with my ML files (hopefully not my camera). I will re-install ML and get back to you on this.
Quote from: critycal on September 06, 2013, 10:39:50 PM
BTW, I saw a video doing 50 or 60fps on the MK II, does anyone know how it's done?
Where is this video, I'd like to see it. Until then I'm sure it would've been a 5d3 or a 7d...or twixtor etc
Quote from: Zao on September 07, 2013, 01:31:13 AM
Where is this video, I'd like to see it. Until then I'm sure it would've been a 5d3 or a 7d...or twixtor etc
The most the mk2 can do is 35fps (31.xx exact value) this is on 30P via canon menu.
60P possible with 7D and mkIII.
I hope devs will continue on improving the preview for crop mode. The images out of it is great detail wise.
Its such a waste if such a functionality cant be use in many situations as framing is difficult to predict when recording starts.
I was wondering if any one has work with the
raw2cdng converter ?
I found and downloaded version-1.3.0 works very well.
Did any one have trouble with color or any image problems ?
I only tested it once & had no problems, but i don't see many posts
about it.
For me If this converter is stable, i can import the cdng's right in to
Final Cut Pro X and start working right a way without stepping out of
FCPX , which is a big bouns, & with the "Send to" App i can
work in Motion and then back to FCPX all in the same session.
This workflow will rival Adobe's in the same Fashion.
I tried to use "raw2dng" but FCPX would not recognizes the file.
But it dose see the DNG's from "raw2cdng"
And i do not see any difference between them or is there?
:D
I tested them both with skin tones and color charts and I also don't see , to my eye at least, any difference.
Quote from: ted ramasola on September 07, 2013, 02:47:18 AM
I tested them both with skin tones and color charts and I also don't see , to my eye at least, any difference.
Thanks Ted, that what i kind of thought.
There's Less of a load on my System with dng(3.8MB) then tiff's(11.5MB)
I can play the image sequence in real time at full Res. in fcpx ;D
I see all kinds of clean looking RAW video! But mine always looks so nasty! Ive try to use neat video on it to get rid of the noisy but it just seems to make it more of a mess. its super noisy. HELP ME PLEASE!
MARK II
SIGMA 35MM 1.4 DG
davinci resolve
iso @ 100
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/Image1_zps68923fcc.jpg)
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/Image2_zps2375040b.jpg)
Are they a screen grab from your final export or individual frames from the .raw? Might be your export settings.
individual frames from the .raw
Are you using Magic Lantern ISO's or Canon ?
I use Magic Lantern ISO "-.03"
that pushes down the ISO or give you Negative Gain
From the image i see i would choose 200 ISO
use Negative Gain -.03 = 160 ISO .
I think that's should help with the noise problem you have .
Quote from: reddeercity on September 07, 2013, 05:17:14 AM
Are you using Magic Lantern ISO's or Canon ?
I use Magic Lantern ISO "-.03"
that pushes down the ISO or give you Negative Gain
From the image i see i would choose 200 ISO
use Negative Gain -.03 = 160 ISO .
I think that's should help with the noise problem you have .
Also, how are you importing your footage? When I import through Camera RAW I use a little of their NR to tame the grain, although my noise has never looked that nasty, more like film grain... hm.
Here's another music video I shot with the RAW module. Lenses used: Minolta MD 50mm f1.4 Rokkor X, 28mm f2.8, 135mm f3.5, 70-200mm f4.
Quote from: F.T.I. ARMY on September 07, 2013, 03:19:41 AM
I see all kinds of clean looking RAW video! But mine always looks so nasty! Ive try to use neat video on it to get rid of the noisy but it just seems to make it more of a mess. its super noisy. HELP ME PLEASE!
MARK II
SIGMA 35MM 1.4 DG
davinci resolve
iso @ 100
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/Image1_zps68923fcc.jpg)
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/Image2_zps2375040b.jpg)
Can you export as an uncompressed TIFF instead and upload that? That looks an awful lot like JPG compression. If you're exporting your frames as JPG that might be why you're getting these compression artifacts.
Im using "5D2_WIN_raw2dng" to convert the RAW. file to a DMG. file. Then I take it into davinci resolve. As soon as I play the video in davinci resolve the video just looks like trash. Ive even Imported it in to After Effects and still looks like trash.
heres a tiff. I know its dark. It dont look as bad to me. I took it right from After Effects. Maybe its davinci resolve?
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/000040_01235_zpsfe4a0494.jpg)
Whenever I import into davinci resolve the footage looks terrible. I use ACR and AE and export from there and the footage always looks clean that way for me.
Quote from: dossisman on September 07, 2013, 06:00:02 AM
Also, how are you importing your footage? When I import through Camera RAW I use a little of their NR to tame the grain, although my noise has never looked that nasty, more like film grain... hm.
I use to import thought Photoshop CC and save my Tiff's that way, i find Photoshop
Handles the DNG better then AE. I think because Photoshop deal with it as a photograph
not as video, and i do not see noise.
But now i use the raw2cdng and import CDNG,s directly in to Final Cut Pro X
as a image sequences so i by pass Adobe camera raw altogether.
I have notice the image is much more Cleaner.
The only time i see noise or grain is when i under expose to much.
KomputerBay warning.
I had one of two cards fail and they did not honor the warranty.
Quote from: dossisman on September 07, 2013, 06:04:13 AM
Here's another music video I shot with the RAW module. Lenses used: Minolta MD 50mm f1.4 Rokkor X, 28mm f2.8, 135mm f3.5, 70-200mm f4.
How do you use your Minolta MD lenses on the 5D Mark II? Do you use an adapter with optical element or did you convert the mount in some way? The flange distance for MD lenses is shorter than that for EF lenses so a 'normal' adapter wouldn't work, right?
I have lots of MD/MC lenses (used with my GH2) and I'm thinking of selling them cause they don't fit the EF mount...
Quote from: JulianH on September 07, 2013, 12:18:51 PM
How do you use your Minolta MD lenses on the 5D Mark II? Do you use an adapter with optical element or did you convert the mount in some way? The flange distance for MD lenses is shorter than that for EF lenses so a 'normal' adapter wouldn't work, right?
I have lots of MD/MC lenses (used with my GH2) and I'm thinking of selling them cause they don't fit the EF mount...
I'm using this:
http://www.amazon.com/Fotodiox-Adapter-Minolta-Rokkor-Digital/dp/B003EB0AY8/ref=sr_1_fkmr1_3?ie=UTF8&qid=1378562189&sr=8-3-fkmr1&keywords=opteka+md+to+ef
It works like a charm with my EF lenses. The adapter has a back element that corrects the focal flange.
Quote from: F.T.I. ARMY on September 07, 2013, 06:39:08 AM
Im using "5D2_WIN_raw2dng" to convert the RAW. file to a DMG. file. Then I take it into davinci resolve. As soon as I play the video in davinci resolve the video just looks like trash. Ive even Imported it in to After Effects and still looks like trash.
heres a tiff. I know its dark. It dont look as bad to me. I took it right from After Effects. Maybe its davinci resolve?
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/000040_01235_zpsfe4a0494.jpg)
I'm not really sure what your settings are in Resolve (besides, I've decided to grade in After Effects after the roundtrip failed on me several times), but like I said before... your JPEGs look like they're too compressed. That TIFF looks pretty clean to me.
Also, are you underexposing and then adjusting exposure in post? That can also cause artifacts. One thing I've learned with the RAW files is that proper exposure is paramount. As soon as you start pushing the exposure, the footage gets grainy (in my case, it's got some sort of grid-like noise pattern, not sure if anyone else is experiencing this?).
Quote from: dossisman on September 07, 2013, 03:59:19 PM
I'm using this:
http://www.amazon.com/Fotodiox-Adapter-Minolta-Rokkor-Digital/dp/B003EB0AY8/ref=sr_1_fkmr1_3?ie=UTF8&qid=1378562189&sr=8-3-fkmr1&keywords=opteka+md+to+ef
It works like a charm with my EF lenses. The adapter has a back element that corrects the focal flange.
Yeah, exactly, with an optical element... I've read that kills some sharpness. But maybe it's not so crucial for video. What's your experience?
Quote from: JulianH on September 07, 2013, 05:16:28 PM
Yeah, exactly, with an optical element... I've read that kills some sharpness. But maybe it's not so crucial for video. What's your experience?
I've never compared sharpness between the lens with a Minolta camera and using the adapter on my 5DmkII to be able to tell the difference. I've been using those exclusively for video, though, as they tend to give me a more cinematic look. It's still sharp enough but not as crisp (razor-sharp has never been my personal preference... if there's one thing I like about cinema lenses is the softer-edge feel of them).
The JPG compression here doesn't really do it justice, but just to give you an idea.
(https://sphotos-b-lga.xx.fbcdn.net/hphotos-prn1/v/1305245_10151660550508723_1380343117_n.jpg?oh=e028809aee8876614135b9657caea8fd&oe=522D423E)
Hello, I am an Italian guy!
I would like to record continuously with the 5d2 to 1880x800 (2.35:1)
you can do it with a fast card? at this moment I can only record 500 - 600 frames! SunDisk with a 32 gb extreme 60mb / s (on paper)
changing card I could?
and why do I have to look closer at the premiere 102.5% with respect to the ratio 2.35:1 screen? recording at 1880x800
Quote from: dossisman on September 07, 2013, 04:13:27 PM
I'm not really sure what your settings are in Resolve (besides, I've decided to grade in After Effects after the roundtrip failed on me several times), but like I said before... your JPEGs look like they're too compressed. That TIFF looks pretty clean to me.
Also, are you underexposing and then adjusting exposure in post? That can also cause artifacts. One thing I've learned with the RAW files is that proper exposure is paramount. As soon as you start pushing the exposure, the footage gets grainy (in my case, it's got some sort of grid-like noise pattern, not sure if anyone else is experiencing this?).
YEAH this shot was def underexposed. Its the one shot I had at the time when I was playing with the RAW. That tiff looks clean. but for some reason Im still having problems. I just dont understand what im going wrong. Ive tried to do everything in AF. But damn it takes for ever and it dont look any better. I love how fast and easy davinci resolve is.
Can anyone send me a link to a good work flow?
Quote from: F.T.I. ARMY on September 08, 2013, 08:43:22 PM
YEAH this shot was def underexposed. Its the one shot I had at the time when I was playing with the RAW. That tiff looks clean. but for some reason Im still having problems. I just dont understand what im going wrong. Ive tried to do everything in AF. But damn it takes for ever and it dont look any better. I love how fast and easy davinci resolve is.
Can anyone send me a link to a good work flow?
what platform are you on PC or Mac?
I'm developing 14 bit Work flow with Cdng's on the Mac
with Final Cut Pro X & Motion plus with the ability to link to adobe products.
If you interested let know and i will explain how it works ;)
Quote from: reddeercity on September 08, 2013, 09:06:02 PM
what platform are you on PC or Mac?
I'm developing 14 bit Work flow with Cdng's on the Mac
with Final Cut Pro X & Motion plus with the ability to link to adobe products.
If you interested let know and i will explain how it works ;)
I HAVE BOTH. But I use Sony Veges and AF. My PC is my Video computer
Quote from: F.T.I. ARMY on September 08, 2013, 09:15:24 PM
I HAVE BOTH. But I use Sony Veges and AF. My PC is my Video computer
I use to work in Vegas back in version 8.
Have you tried using "raw2cdng" and import dng's
directly as a image sequences ?
the "raw2cdng" have the option to change
the image to 16, 12 bit liner or 10 bit Log.
How are you exporting from A.E. ?
Quote from: reddeercity on September 08, 2013, 10:18:11 PM
I use to work in Vegas back in version 8.
Have you tried using "raw2cdng" and import dng's
directly as a image sequences ?
the "raw2cdng" have the option to change
the image to 16, 12 bit liner or 10 bit Log.
How are you exporting from A.E. ?
YEAH I tried to directly importing and it didnt work
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/photo_zps8422f466.jpg)
Quote from: F.T.I. ARMY on September 08, 2013, 11:06:42 PM
YEAH I tried to directly importing and it didnt work
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/photo_zps8422f466.jpg)
I see you are exporting as H264 ?
If you are, and then importing in Vegas you are not really in
a good format for editing!
I would use the Lest compressed format that your system can handle.
QT intermediate or a AVI would be better to use .
i would choose for a avi= blackmagic 10bit 444 ,if you have it (download the codec from blackmagic)
or in QT= Blackmagic 10bit, uncompressed 10bit 422 etc.....
and i always select trillions of color, if you have that option.
But if you have A.E. on the Mac you can just export as a ProRes4444. :)
Quote from: reddeercity on September 09, 2013, 01:57:22 AM
I see you are exporting as H264 ?
If you are, and then importing in Vegas you are not really in
a good format for editing!
I would use the Lest compressed format that your system can handle.
QT intermediate or a AVI would be better to use .
i would choose for a avi= blackmagic 10bit 444 ,if you have it (download the codec from blackmagic)
or in QT= Blackmagic 10bit, uncompressed 10bit 422 etc.....
and i always select trillions of color, if you have that option.
But if you have A.E. on the Mac you can just export as a ProRes4444. :)
OK we are getting some where lol. the footage looks so much better when I render it out with AVI. I downloaded the Blackmagic 10bit 422. But I had trouble finding it. (I dont know if I got the right one) and I dont know where to fine it. Im guess it should be under the "format options"??. and I could only keep the depth at millions of colors
Quote from: F.T.I. ARMY on September 09, 2013, 03:33:23 AM
OK we are getting some where lol. the footage looks so much better when I render it out with AVI. I downloaded the Blackmagic 10bit 422. But I had trouble finding it. (I dont know if I got the right one) and I dont know where to fine it. Im guess it should be under the "format options"??. and I could only keep the depth at millions of colors
Very Good !
download the Blackmagic "Desktop Video for windows"
Link below
http://www.blackmagicdesign.com/support/detail?sid=3958&pid=3966&leg=false&os=win
It free, i have Ultra Studio SDI usb 3.0 for capturing & monitoring
and thats the one i downloaded.
you don't have to Register just hit the "download Now" tab
That should put All the blackmagic codec on your system ;)
Quote from: reddeercity on September 09, 2013, 05:31:58 AM
Very Good !
download the Blackmagic "Desktop Video for windows"
Link below
http://www.blackmagicdesign.com/support/detail?sid=3958&pid=3966&leg=false&os=win
It free, i have Ultra Studio SDI usb 3.0 for capturing & monitoring
and thats the one i downloaded.
you don't have to Register just hit the "download Now" tab
That should put All the blackmagic codec on your system ;)
Ok dude I owe you.haha Thanks so much I think im finely on the right path. Heres that same image rendered the new way with the blackmagic codec
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/RA_zpsce523668.jpg)
underexposed YES but damn it looks cleaner.
Quote from: F.T.I. ARMY on September 09, 2013, 07:17:46 AM
Ok dude I owe you.haha Thanks so much I think im finely on the right path. Heres that same image rendered the new way with the blackmagic codec
(http://i1315.photobucket.com/albums/t583/Matthew_Mixx_Goodman/RA_zpsce523668.jpg)
underexposed YES but damn it looks cleaner.
that's more like it :)
Just remember that most of the noise came from the Luma channel.
Here a little Explanation about Luma i found on the net from "CG Society/ Society of Digital Artists"
Luminance (or Luma) is the normalized brightness of the sum of the RGB channels expressed as a greyscale value. For color systems such as YUV/ YIC that are used in video systems it refers to the base brightness of a given pixel, on top of which the color difference info is modulated.
So the more you under expose the more noise you introduce in to the image.
when you expose and you think that looks good bring up your exposure by 2 to 3 Stops .
you can always bring down the exposure in Post.
As long as you don't overexpose .
Hello, I am an Italian guy!
I would like to record continuously with the 5d2 to 1880x800 (2.35:1)
you can do it with a fast card? at this moment I can only record 500 - 600 frames! SunDisk with a 32 gb extreme 60mb / s (on paper)
changing card I could?
and why do I have to look closer at the premiere 102.5% with respect to the ratio 2.35:1 screen? recording at 1880x800
Quote from: poty on September 09, 2013, 04:11:43 PM
Hello, I am an Italian guy!
Being Italian is not an excuse for not reading the forum! (only saing that because not only have I seen docents of posts with similar lines but got already private messages and emails, funny enough all from fellow Italians!).
Quote from: poty on September 09, 2013, 04:11:43 PMI would like to record continuously with the 5d2 to 1880x800 (2.35:1)
you can do it with a fast card? at this moment I can only record 500 - 600 frames! SunDisk with a 32 gb extreme 60mb / s (on paper)
changing card I could?
You can easily do 1856 (not 1880 but pretty much the same) in 2.35:1 continuous on the SanDisK 60mbs Cards with image quality set to jpg and small hacks on it should work, I shot this video on a single SanDisk 16gb 60mbs card:
Quote from: poty on September 09, 2013, 04:11:43 PMand why do I have to look closer at the premiere 102.5% with respect to the ratio 2.35:1 screen? recording at 1880x800
That is because your timeline in Premmiere is probably set to 1920 x 817 or even 1080; if you shoot at 1856 you'll have to scale at 103.5%...
Quote from: reddeercity on September 09, 2013, 05:31:58 AM
Very Good !
download the Blackmagic "Desktop Video for windows"
Link below
http://www.blackmagicdesign.com/support/detail?sid=3958&pid=3966&leg=false&os=win
It free, i have Ultra Studio SDI usb 3.0 for capturing & monitoring
and thats the one i downloaded.
you don't have to Register just hit the "download Now" tab
That should put All the blackmagic codec on your system ;)
Awesome. I didn't know about this. Maybe that's the solution to the gap in my Premiere/Resolve roundtrip issue.
Quote from: dossisman on September 10, 2013, 02:29:48 PM
Awesome. I didn't know about this. Maybe that's the solution to the gap in my Premiere/Resolve roundtrip issue.
What kind of problem are you having?
Maybe I can help you solve the issue
You having :)
Quote from: reddeercity on September 10, 2013, 06:09:16 PM
What kind of problem are you having?
Maybe I can help you solve the issue
You having :)
Well.. let me start by saying that I didn't completely follow Hunter's tutorial way of doing it. After trying to render in AVI's and getting all sorts of problems (Perhaps because I didn't have the codecs installed!), I decided to use the Cineform files as proxies straight out of BATCHelor, then I imported the XML file and for a quick, 10-shot edit it worked. When I imported the full music video, it started giving me all these 'missing scene' messages even though I had my DNG clips named exactly the same as the AVI proxies. It's strange.
So after it couldn't find the one proxy (and didn't give me an option to point manually like After Effects does), it replaced all the cuts with the first clip, followed by the next, and the next.
I've color graded the last two videos in After Effects because I got so discouraged.
Quote from: dossisman on September 10, 2013, 09:06:20 PM
Well.. let me start by saying that I didn't completely follow Hunter's tutorial way of doing it. After trying to render in AVI's and getting all sorts of problems (Perhaps because I didn't have the codecs installed!), I decided to use the Cineform files as proxies straight out of BATCHelor, then I imported the XML file and for a quick, 10-shot edit it worked. When I imported the full music video, it started giving me all these 'missing scene' messages even though I had my DNG clips named exactly the same as the AVI proxies. It's strange.
So after it couldn't find the one proxy (and didn't give me an option to point manually like After Effects does), it replaced all the cuts with the first clip, followed by the next, and the next.
I've color graded the last two videos in After Effects because I got so discouraged.
I understand your frustration !
I lot of people on this form assume that ever one has knowledge of workflows,
Codec, and Terminology of the industry. And if you are "New" then you can Get very Lost & discouraged .
Because you Just what make the Best possible Video you can!
I Know i use to be one of those people.
OK now down to your problem, from the info you are on a PC,
Do you have a Raid 0 on you system? if you could give some info on
you PC so i Know your limitations and see if there is a simpler way of
implementing this work flow or changing to another workflow.
But in the mean time i run on Both PC & Mac.
I personalty Convert Raw to DNG's on my PC
and conform, edit on my Mac .
I can Set up your PC workflow on my PC and see whats happen :)
I used a komputerbay 1000x cf card 64gb in my 5d mark ii... but when i set raw video size on 1856*1044 it recording only 350 or 400 frames. Why i cant record continous shooting with my fast card????
Quote from: ali farahani on September 11, 2013, 03:03:11 AM
I used a komputerbay 1000x cf card 64gb in my 5d mark ii... but when i set raw video size on 1856*1044 it recording only 350 or 400 frames. Why i cant record continous shooting with my fast card????
Try to warm up the card First,
Record at a smaller frame size under the card get warm up
or turn on card warm up in the ML raw menu .
I have a Lexar 1000x 64GB card and maximum size i can record
for any length of time is 1856x1004 23.976p 14,000 frames.
Thank ad's WIN_cr2hdr_exe, I solved a part can not be converted CR2. :)
Hi everybody! Does someone have info (changes) about the new build (26f79287de2b)?
Quote from: reddeercity on September 11, 2013, 04:38:33 AM
Try to warm up the card First,
Record at a smaller frame size under the card get warm up
or turn on card warm up in the ML raw menu .
I have a Lexar 1000x 64GB card and maximum size i can record
for any length of time is 1856x1004 23.976p 14,000 frames.
i tried to warp up card.. but in 1856*1044 resolation expect frames is 276-291 and not continous :'( :'( :'(
Quote from: ali farahani on September 11, 2013, 12:40:53 PM
i tried to warp up card.. but in 1856*1044 resolation expect frames is 276-291 and not continous :'( :'( :'(
You could verify your card support high speed (benchmark in ML menu), I saw some reports about some Komputerbays doesn't work as expected (<1000x).
Quote from: SpcCb on September 11, 2013, 01:22:58 PM
You could verify your card support high speed (benchmark in ML menu), I saw some reports about some Komputerbays doesn't work as expected (<1000x).
I have Lexar 64gb 1000x and regardless of builds and settings (it can go 1-2MB/s up or down with settings like small hacks, fps override, etc. on/off, I have tried pretty much everything :-\) it is recording with 60MB/s +/-. Card is fine and I have reported it thru out the time but no one could tell why this is the case with my 5d mark II :'( :'( :'(
1856 X 1044 is 16:9 and 1856 X 1004 - is 1:185 I believe.
On the chart showing all raw capabilities 1856 X 1004 is listed as being the largest resolution near 16:9 which the 5D mark 2 can shoot continuously.
It's not, however, 16:9 - it's just as close as you can get and shoot continuously - at least as far as I've understood it.
My tests with the Aug. 5 build give me approx 1000 frames at 1856 X 1044 and with 1856 X 1004 it reads between 2000 and continuous. I haven't tried filling the card.
Could this be the problem some people are having?
When i shooting raw video with my komputerbay 1000x sometimes when input my card to my cam... camera doesnt on. I have to format card in windows :o
Quote from: ali farahani on September 11, 2013, 03:30:56 PM
When i shooting raw video with my komputerbay 1000x sometimes when input my card to my cam... camera doesnt on. I have to format card in windows :o
Did you try to format your card in
Camera?
I do every time before I film
That helps I have notice.
You really need to warm up
The card, it make a differences
Weather or not you get Continuous
At 1856x1004 . At lest for me.
When I have problem with my
Lexar 1000x card I record at small size
First until card full, then shoot
@ a bigger size . The benchmark
Dose not work !! I get only
32 to 42 MB/s there but I record at 75.0 MB/s .
Quote from: reddeercity on September 11, 2013, 04:37:11 PM
Did you try to format your card in
Camera?
I do every time before I film
That helps I have notice.
You really need to warm up
The card, it make a differences
Weather or not you get Continuous
At 1856x1004 . At lest for me.
When I have problem with my
Lexar 1000x card I record at small size
First until card full, then shoot
@ a bigger size . The benchmark
Dose not work !! I get only
32 to 42 MB/s there but I record at 75.0 MB/s .
Untill i started shooting by Kumputerbay 64gb cf card in my 5d mark ii i have a lot of issue and problems. my new problem is the raw footages can not convert by raw2dng.exe
Quote from: ali farahani on September 11, 2013, 04:43:46 PM
Untill i started shooting by Kumputerbay 64gb cf card in my 5d mark ii i have a lot of issue and problems. my new problem is the raw footages can not convert by raw2dng.exe
I would try and re-install ML software with the the "EOScard" program
and see if that help, i had to do this back 6 version ago.
Make sure also that your Battery is fully change or use
a AC adapter if shooting indoors,
I have notice from time to time if the battery is not up on power
and you start change thing in the Menu it some time Glitches out
reboot always fixes it though . :)
Edit : try the raw2cdng.exe i find it works really well!
Whats new in 10th Sept build please :)
Can someone help me do a complete re-install of ML RAW.
I've only updated builds since the beginning and don't even remember how I installed it at first place.
This is what I think I have to do.
1. Format Card.
2. Install 5D RAW Alpha Build.
3. Do firmware update (this is where I am in much doubt)
4. Overite with newest build.
Am I correct ?
Quote from: Kharak on September 11, 2013, 10:42:34 PM
Can someone help me do a complete re-install of ML RAW.
I've only updated builds since the beginning and don't even remember how I installed it at first place.
This is what I think I have to do.
1. Format Card.
2. Install 5D RAW Alpha Build.
3. Do firmware update (this is where I am in much doubt)
4. Overite with newest build.
Am I correct ?
i install ML via the EOScard.exe, on windows, than download the latest Raw record module
copy the New AUTOEXEC.Bin in the Root of card, That will replace the one that's there
and copy the Module fold to the ML folder.
Then you have to activate the module you when to use.
Then reboot camera , That it
Just testing the new Sept 10th built, and i see a little better speed &
Larger stable Frame sizes .
1872x1012 23.976p 4400 to 4800 Frames @ 75.5 MB/s
My Setting:
haCKed View = on
small Hacks = on
Features = on
FPS override = on
But it is still curious that at 42GB There still a Wall
on 1856x1004 and the same thing at 2048x930 23.976p.
Very little Buffering then the buffer fills up & stop recording.
all on Lexar 1000x 64GB
Oh shitttttttt . Please send me a note that what part of my work is false.
I first extract magiclantern zip file to my komputerbay 1000x 64 gb. then download latest nightly build and copy and replace that .
Input card to the camera and then update firmware. magiclantern installed sucessfully. rebot camera then load raw module. .. again rebot camera and set raw video in a lower resolation and active card warm up .
Camera recording this 4000 or 5000 frames. card warmed up and ready for haigher resolations. but when i want to record again. camera does not shooting... i have a massege that cant record .. or card mey be full. then when i check magiclantern menu, the raw module is removed.
Quote from: ali farahani on September 12, 2013, 01:52:26 AM
Oh shitttttttt . Please send me a note that what part of my work is false.
I first extract magiclantern zip file to my komputerbay 1000x 64 gb. then download latest nightly build and copy and replace that .
Input card to the camera and then update firmware. magiclantern installed sucessfully. rebot camera then load raw module. .. again rebot camera and set raw video in a lower resolation and active card warm up .
Camera recording this 4000 or 5000 frames. card warmed up and ready for haigher resolations. but when i want to record again. camera does not shooting... i have a massege that cant record .. or card mey be full. then when i check magiclantern menu, the raw module is removed.
Puzzling , the only thing i do different is i use the Eoscard.exe to install ML on my card.
Did you copy the new autoexec.bin over also, if you did, for some reason it my be corrupted.
here is a link to the eoscard.exe program i use to install ML on my CF card, it make them bootable .
Link: http://pel.hu/eoscard/
i would try reinstall it again .
Quote from: reddeercity on September 12, 2013, 02:14:05 AM
Puzzling , the only thing i do different is i use the Eoscard.exe to install ML on my card.
Did you copy the new autoexec.bin over also, if you did, for some reason it my be corrupted.
here is a link to the eoscard.exe program i use to install ML on my CF card, it make them bootable .
Link: http://pel.hu/eoscard/
i would try reinstall it again .
Thanks but eoscard.exe gives one error when i want to save: error zip file.
Excatly i have this error when i want to shoot raw in my camera : data corruption at slot 0 frame 1
Quote from: ali farahani on September 12, 2013, 02:21:19 AM
Thanks but eoscard.exe gives one error when i want to save: error zip file.
Excatly i have this error when i want to shoot raw in my camera : data corruption at slot 0 frame 1
i just when though the procedure of, first format card then used the esocard to make the
card bootable, check off all three boxes, and save.
then copy over the Alpha One ML on to card .
you have to
delete the File"
MAGIC.SYM" if it there that is more then likely the problem.
That file is left over from the 1st generation of raw record.
the following is a list of files you should have on your card in the ML Folder.
5D2_212.SYM
ARKANOID.MO
AUTOEXPO.MO
DUAL_ISO.MO
ETTR.MO
FILE_MAN.MO
RAW_REC.MO
I only copy over 5D2_212.SYM , FILE_MAN.MO , RAW_REC.MO
Because i only what Raw Video.
Quote from: reddeercity on September 11, 2013, 11:27:09 PM
i install ML via the EOScard.exe, on windows, than download the latest Raw record module
copy the New AUTOEXEC.Bin in the Root of card, That will replace the one that's there
and copy the Module fold to the ML folder.
Then you have to activate the module you when to use.
Then reboot camera , That it
Thank you for the answer.
Never heard of Eoscard until now. But I see its the better solution than my first clean installation and will hopefully fix the issue I've had with crop mode.
I only copied files on my first Raw installation and then been overwriting them since. Have had no issues though, except for my crop mode black border.
EDIT: Posted simultaneously as Reddercity in above post. You mention Magic.sym I will try to delete only that file and see where that takes me on my crop mode agenda. If no change I will continue with complete re-instal
Thanks. In card warm up there are variable numbers from 16mb to 1gb. which number i should to select?
I just verified the install procedure and it works Ok,
tested on Sandisk 60 MB/s 16GB card.
No error , and for all the guy who have slow card
i could record 1728x786 2.20:1 23.976p until Full
on the New Built :)
Quote from: ali farahani on September 12, 2013, 03:49:57 AM
Thanks. In card warm up there are variable numbers from 16mb to 1gb. which number i should to select?
try the 1GB that should be ok,
Basically you what it to be Warn to the Touch of you hand.
I think pehaps my cf card can not be bootable... when i shoot RAW over 4GB last frame getting to corruption data. a RAR file created the same name of the raw footages that was over 4gb. this RAR files do not allow to camera write RAW or even h.264 on cf card.
Quote from: ali farahani on September 12, 2013, 04:21:40 AM
I think pehaps my cf card can not be bootable... when i shoot RAW over 4GB last frame getting to corruption data. a RAR file created the same name of the raw footages that was over 4gb. this RAR files do not allow to camera write RAW or even h.264 on cf card.
I think what you see is the Spanning files , 5D2 is Fat32 file system and is limited to writing
4GB files , then you have to connect the spanning files together.
You can do this on the command line in windows,
Joining files: copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
where "xyz is the souce name, and "xyz.raw" is the New name at the end.
Or use raw2cdng.exe , just drop all theRaw plus spanning file on the program and choose the setting you like.
Link is below
http://dl.phreekz.de/raw2cdng/raw2cdng.1.3.0.zip
I use this as my main converter ;)
Edit:when i record full cards i see up to 10 Spanning files.
He is the my test workflow with cdng's natively as a Image Sequences in Final Cut Pro X
Then exported to Compressor by XML to 2k mp4 .
If you Select Original Quality that will be true 2k
Quote from: reddeercity on September 12, 2013, 09:24:25 AM
He is the my test workflow with cdng's natively as a Image Sequences in Final Cut Pro X
Then exported to Compressor by XML to 2k mp4 .
If you Select Original Quality that will be true 2k
Very nice!
Did you upscale 1880 or record in crop mode?
Quote from: guentergunter on September 12, 2013, 10:54:49 PM
Very nice!
Did you upscale 1880 or record in crop mode?
Thanks :D
no i recorded in Crop mode , with my EF 100mm macro f2.8L prime,(my go to Lens)
edited & color corrected the Navtive Cdng's image sequence no proxy.
But i did have problem that if i render it out to ProRes 4444 i got a big gamma shift down.
XML saved me there.
Plus a Bought the new Slice X from Coremelt for FCPX
i duplicated the Image sequence, drag the file above it,
and Cut out the Berries with the Free Form Rotoscope tool.
and adjusted the Berries separately from the leaves.
:)
BEST RENDER SETTINGS FROM DaVINCI RESOLVE TO SONY VEGAS
TOOK ME FOREVER TO FIGURE THIS OUT SO I FIGURE I WOULD SHARE
QUICKTIME
QUICKTIME DNxHD 1080P 220/185/175 10 BITS
PLEASE CORRECT ME IF IM WRONG
I'm curious to know what method you guys are using to uprez to 1080p. I'm shooting at 1880x800, etc.
Quote from: raf702 on September 13, 2013, 06:35:00 AM
I'm curious to know what method you guys are using to uprez to 1080p. I'm shooting at 1880x800, etc.
ME TO PLEASE HELP
A simple scale using the editor of your picking?
Quote from: F.T.I. ARMY on September 13, 2013, 06:48:14 AM
ME TO PLEASE HELP
Theres a few ways:
Photoshop - Resize all the images in ACR (Adobe Camera RAW)
Photoshop - Run Script - This allows you edit a batch of images, one of the options is resize and quality
After Effects - Resize in the comp
After Effects - Export footage > Choose resize choose high quality
Premiere Pro - Same as After Effects
FCP7/X - Same as PP & AE
after effects cc ships with a resizing plugin and adobe recommends using it instead of comp resizing
http://tv.adobe.com/watch/adobe-at-ibc-2013/after-effects-cc-detailpreserving-upscale/
Quote from: dradutu on September 13, 2013, 03:31:07 PM
after effects cc ships with a resizing plugin and adobe recommends using it instead of comp resizing
http://tv.adobe.com/watch/adobe-at-ibc-2013/after-effects-cc-detailpreserving-upscale/
This plugin will be available in october
While I mostly just resize in AE or PP I have also used Magic Bullet Instant HD pluginfor some of the more demanding blow ups, not sure if it is a lot better though...
I think I found the problem with using an external monitor on the 5D with RAW. It lies when using HaCKeD in the RAW preview settings. I'm not sure if this setting even does anything anymore as I did not notice a speed loss (or any change for that matter) between HaCKeD and the other modes. But at least I can use my external monitor now.
Also note that this only works still if I use the "record one raw file with the external monitor off" trick first.
Here is the code for when it crashes
ASSERT: 0
at Memory\Memory.c:561, task RscMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Sep10.5D2212
Mercurial changeset : 26f79287de2b+ (unified)
Built on 2013-09-10 20:59:33 UTC by ad@MagicLantern.
Free Memory : 228K + 3759K
and the end of the event log
13779: 63384.997 [DISP] SetPBForLV ZoomMode=0, LVType::Info=0, LVType::DispType=3
I know I've said a few times, but... HaCKeD doesn't work on 5D2. I'll remove it in the next release.
Hmm... I don't have a HDMI device, also I still don't know thoroughly how ML handle the HDMI signal. However it's possible to check if the HDMI is connected and we could do some HDMI special stuff.
btw
Today is Friday 13th :o
So external monitors or evfs dont work properly with raw recording on the 5d2 or 5d3? I was about to pull the trigger on an evf too.
Quote from: a.d. on September 13, 2013, 11:05:29 PM
I know I've said a few times, but... HaCKeD doesn't work on 5D2. I'll remove it in the next release.
Hmm... I don't have a HDMI device, also I still don't know thoroughly how ML handle the HDMI signal. However it's possible to check if the HDMI is connected and we could do some HDMI special stuff.
btw
Today is Friday 13th :o
It's definitely happened outside of Friday the 13th haha.
Unless you warm it out with recording a raw file without the monitor first, it will crash just after it empties the buffer from your recording. It freezes for a split second on the last green dot, and then the live-view goes off and the crash error is displayed.
My findings are that it does not crash if you both:
Record 1 raw before plugging in or powering up the external monitor.
Use a mode other than hacked after "warming" it up.
If you power cycle the device, and try again without "warming up" with a raw again, it will crash.
If you shut off live view after you've "warmed" it up and turn it back on, it will NOT crash.
It may or may not crash when going to the regular canon menu system.
Quote from: raf702 on September 13, 2013, 11:22:52 PM
So external monitors or evfs dont work properly with raw recording on the 5d2 or 5d3? I was about to pull the trigger on an evf too.
I don't know about the 5d3, but the 5d2 is definitely shaky with raw and HDMI. If you are planning on shooting anything more serious than random tests, I would not use it at this time.
Quote from: raf702 on September 13, 2013, 11:22:52 PM
So external monitors or evfs dont work properly with raw recording on the 5d2 or 5d3? I was about to pull the trigger on an evf too.
External monitor will work on the 5D mkII. Just a couple of tips:
-The rectangular guides don't work, its offset, so mask your monitor with tape or transparency.
-To remove the distracting off centered guide use ML grayscale in preview menu. (the image will still be in color via hdmi and no more skewed guides)
-Do not preview your footage with the HDMI monitor attached as your camera will freeze.
One big benefit of raw is the image is all HD even when recording unlike h264 that it will downrez when recording.
Its great for keeping focus. Tip: since raw doesnt burn in profiles, you can crank up sharpness in pic profile for easy focusing, raw doesnt burn in the sharpness unlike h264.
Quote from: a.d. on September 13, 2013, 11:05:29 PM
I know I've said a few times, but... HaCKeD doesn't work on 5D2. I'll remove it in the next release.
Yuppi! Finally we will get rid of this bitch 8)
I do know with HaCKeD view on i get more frames with it on then with off.
At lest on my 5D2 :)
I asked for help a couple of days ago or 2-3 pages back, regarding Crop Mode. As it was not working properly on my 5D MK II.
I had a black border on the right side of my frame. some 30-50 pixels.
Thanks to Reddercity I managed to do a complete re-install of ML and now I get full resolution in crop mode. BUT! Recording time is so small! Only 300-400 frames.
Now I'm not sure, but with whatever weird build I had mixed with the newest build, before I re-installed. I could sometimes record continuesly in crop mode. Now this was ofcourse with those 30-50 missing pixel grids on the right side of the frame, but even now when I've tried 2048 instead of 2152, its still pretty much the same amount of frames.
I find this very weird. Unless perhaps my camera never recorded with higher resolution in crop mode and just 3x'ed the image in to normal 1880x800.
How many frames do people normally get with 2152x916 and 2048x9xx (2:35.1) ?
With regards.
Kharak.
Quote from: ted ramasola on September 14, 2013, 12:31:38 AM
External monitor will work on the 5D mkII. Just a couple of tips:
-The rectangular guides don't work, its offset, so mask your monitor with tape or transparency.
-To remove the distracting off centered guide use ML grayscale in preview menu. (the image will still be in color via hdmi and no more skewed guides)
-Do not preview your footage with the HDMI monitor attached as your camera will freeze.
One big benefit of raw is the image is all HD even when recording unlike h264 that it will downrez when recording.
Its great for keeping focus. Tip: since raw doesnt burn in profiles, you can crank up sharpness in pic profile for easy focusing, raw doesnt burn in the sharpness unlike h264.
I also have only those problems and am using the given solutions.
In other words: I can confirm, that HDMI and RAW work pretty good together!
Quote from: Kharak on September 14, 2013, 02:50:26 PM
Thanks to Reddercity I managed to do a complete re-install of ML and now I get full resolution in crop mode. BUT! Recording time is so small! Only 300-400 frames.
How many frames do people normally get with 2152x916 and 2048x9xx (2:35.1) ?
With regards.
Kharak.
I'm Glad you got things working! :)
On my 5D2 when i record in Crop mode I keep the frame size to
2048x930 23.976p 2.20:1
i get full card record on my 32GB lexar1000x = 8,500 to 9,000 frames
64GB Lexar 1000x card 42 Gb = 14,238 frames @ 76.2 MB/s
Here is a sample of this Capture.
Plus this video was edited & process on the Native cdng's in FCPX no proxy
I have an issue when I go into the first crop mode the LV displays a grey and pixelated view. But when I go into the second crop mode, LV displays perfectly fine. Any reason why this happens?
Quote from: raf702 on September 14, 2013, 11:43:21 PM
I have an issue when I go into the first crop mode the LV displays a grey and pixelated view. But when I go into the second crop mode, LV displays perfectly fine. Any reason why this happens?
That is the ML Grayscale view for actuate framing but when you record it go to
the normal color view.
you can change this in the Raw sub-menu
under preview, you have 4 Choices.
Auto
Canon
ML Grayscale
HaCKeD View.
Auto will display the "ML Grayscale"
i use either Canon or HaCKeD, but i use A_D_ hack built,
the one with the disclaimer of hot pixels etc...
I see, I thought it was a glitch. Thanks!
Quote from: raf702 on September 15, 2013, 12:13:13 AM
I see, I thought it was a glitch. Thanks!
No problem, Glad to Help ;)
Has any one tested capturing the hdmi signal ?
i did a test with my AJA Kona LHi card & my Atomos Ninja
Both tell me i'm getting a 1080i 29.97 YCbCr 8Bit ?
and when i hit record on the 5D2 to record Raw video the signal
Dose not drop down it stay at 1080i 29.97 YCbCr 8Bit. ???
I though this was not Possible.
Or did i miss something.
So now you can have a backup recording to Ninja while you record Raw to CF
at the same time :)
Here is my test i talk about
hello,
i am new to the forum, would like to thank all smart guys for their work - incredible. Could You pls advice me on which build is the most stable - working for RAW video on mkii?
Thank You.
Quote from: Pijer on September 17, 2013, 10:16:01 AM
hello,
i am new to the forum, would like to thank all smart guys for their work - incredible. Could You pls advice me on which build is the most stable - working for RAW video on mkii?
Thank You.
Check the very first post of this thread (http://www.magiclantern.fm/forum/index.php?topic=5533.0) for answers :)
Hey everyone I was recently hired by this yoga studio to shoot a video at Whole Foods. I shot the whole thing in raw, except for the time lapse's of course. Oh and by the way, it was almost totally dark on that roof, i used absolutely no lights. most of the time I was in 3200iso or 6400iso. Let me know what you think. Thank you ML!
~Dustin
dolphincreativemedia.com
Quote from: reddeercity on September 17, 2013, 06:27:06 AM
Here is my test i talk about
This is a great news!
There is also a way to control the rec button (remote)?
Video output (rca) can be used as a video assist during shooting?
Thanks
Quote from: DolphinCreative on September 17, 2013, 10:34:40 AM
Hey everyone I was recently hired by this yoga studio to shoot a video at Whole Foods. I shot the whole thing in raw, except for the time lapse's of course. Oh and by the way, it was almost totally dark on that roof, i used absolutely no lights. most of the time I was in 3200iso or 6400iso. Let me know what you think. Thank you ML!
~Dustin
dolphincreativemedia.com
Nice, I recorded some 3200 iso shots last night. Haven't had a look at them yet, but your video made me wanna do it right now! :)
Did you use NeatVideo? or ?
Quote from: Kharak on September 17, 2013, 01:20:45 PM
Nice, I recorded some 3200 iso shots last night. Haven't had a look at them yet, but your video made me wanna do it right now! :)
Did you use NeatVideo? or ?
I used magic bullet denoiser 2. It works great with regular footage, but with raw its extremely effective, and very easy to use. Thanks man and good luck! Post your footage I would like to see it.
Some random shots I did the last two weeks, unfortunately YouTube compression absolutely kills the quality >:(
Shot using the standard Canon Zoom Lens EF 24-105mm 1:4 L IS USM and some shots with variable ND filter.
Quote from: reddeercity on September 14, 2013, 11:31:15 PM
I'm Glad you got things working! :)
On my 5D2 when i record in Crop mode I keep the frame size to
2048x930 23.976p 2.20:1
i get full card record on my 32GB lexar1000x = 8,500 to 9,000 frames
64GB Lexar 1000x card 42 Gb = 14,238 frames @ 76.2 MB/s
Here is a sample of this Capture.
Plus this video was edited & process on the Native cdng's in FCPX no proxy
Wonderfull cut, and cool musik too !!! :)
Quote from: xvince1 on September 17, 2013, 08:48:28 PM
Wonderfull cut, and cool musik too !!! :)
Thanks ,That's much appreciated :D
All these little Vignette i produces are Seen at the Local Independent Movie theater,
as fillers before the Main Movie Feature.
Here in Central Alberta, Canada. :)
shot with komputerbay 64 x1000, the last shots are taken in h264. i have to learn to ettr, was scared it wouldn't keep the highlights but it does it.
here's the vimeo link, for some reason could not embed it http://vimeo.com/arteelastice/marky
Quote from: rawmania on September 17, 2013, 12:13:06 PM
This is a great news!
There is also a way to control the rec button (remote)?
Video output (rca) can be used as a video assist during shooting?
Thanks
It is good New! now you have a backup.
on the record button thing , i'm no sure but i have heard talk of
usb triggers. i would do some searches on this form.
As far as i know, its just a hdmi thing. but if your Recorder , of
EVF have a Composite connector (rca) out then it should work.
But on the way i have it setup its just a hdmi ;)
For vimeo link, don't put the "s" after https:// (I've read somewhere that "s" mean secure for vimeo)
Quote from: DolphinCreative on September 17, 2013, 02:59:23 PM
I used magic bullet denoiser 2. It works great with regular footage, but with raw its extremely effective, and very easy to use. Thanks man and good luck! Post your footage I would like to see it.
This was shot at ISO 2500eq and later pushed the exposure +1.00 in ACR, was just fooling around and was surprised at how little sensor patterns and other noises were visible before the noise reduction.
Used Neat Video Pro
More specs in video description.
Quote from: Kharak on September 19, 2013, 05:40:13 PM
This was shot at ISO 2500eq and later pushed the exposure +1.00 in ACR, was just fooling around and was surprised at how little sensor patterns and other noises were visible before the noise reduction.
Used Neat Video Pro
More specs in video description.
God, this looks insane. I haven't pushed my camera beyond 1250 ISO, yet.
@ a.d.
Just a minor typo on the date of recent build. Its typed as 9/25. ;)
5 days ahead.
Was just bout to say the same :)
fixed! I'm always thinking about the future ;)
Update on CR2HDR is great!! my images now convert that couldn't be dual iso detected :) was going to trash them!
Quote from: Doyle4 on September 21, 2013, 04:51:08 AM
Update on CR2HDR is great!! my images now convert that couldn't be dual iso detected :) was going to trash them!
I've been wondering how to use or what to use the dual iso function for, are you using it to record RAW dual iso video or Stills Photography? If you don't mind can you explain how you're using it with the CR2HDR.app.
Hey I know this is probably a silly nooby question, and most don't get answered but;
When updating to the latest nightly builds I've just been using the original build and overwriting the with the new ML and Autoexe.bin file is this the correct way to do it?
Quote from: Samco on September 22, 2013, 05:11:58 PM
Hey I know this is probably a silly nooby question, and most don't get answered but;
When updating to the latest nightly builds I've just been using the original build and overwriting the with the new ML and Autoexe.bin file is this the correct way to do it?
Yes
Thank you Kharak
Few issues
1. Getting pink flashes on screen when I start recording.
2. ISO is jumping after I start recording. What can I change to disable that/Lock ISO??
3. Is there any way to get the DOT microfocus back or was it not feasible??
Thanks
What are you think about this timecode test
http://vimeo.com/75204373
5d markII; 1872x796; s Jpg; 23.976f/s override
drop frame ....
Quote from: Stuntfoto on September 23, 2013, 02:25:35 PM
What are you think about this timecode test
http://vimeo.com/75204373
5d markII; 1872x796; s Jpg; 23.976f/s override
drop frame ....
Do you have frame skipping allowed? Cause then it will drop frames and continue recording.
then again, 1872x796 shouldn't cause frame skipping with a 1000x. What build are you on?
Quote from: Samco on September 23, 2013, 04:44:38 AM
Thank you Kharak
Few issues
1. Getting pink flashes on screen when I start recording.
2. ISO is jumping after I start recording. What can I change to disable that/Lock ISO??
3. Is there any way to get the DOT microfocus back or was it not feasible??
Thanks
1. Never had this issue man, so I suggest you format card in camera and re-install ML. Or are these just flashes on the screen or do you also see pink flashes on the actual DNG's?
2. Not sure about this, is you ISO set to Auto in canon menu? Your dial on top of the camera, needs to be at M - Mode (Manual).
3. Are you referring to Focus peaking? Cause its available in the last 3-4 builds. Called FPeaking in menu I think and there is Digic peaking which you adjust according to the FPeaking.
Hope it helps.
Quote from: Kharak on September 23, 2013, 02:40:05 PM
Do you have frame skipping allowed? Cause then it will drop frames and continue recording.
then again, 1872x796 shouldn't cause frame skipping with a 1000x. What build are you on?
Yes frame skipping with a 1000x (KomputerBay, and Transcend).... today test with build 23.09.....Frame skipping setting (OFF) Any build made fast video( may be 20-18 f/s) any - drop and strobe effect....
Quote from: Stuntfoto on September 23, 2013, 02:54:04 PM
Yes frame skipping with a 1000x (KomputerBay, and Transcend).... today test with build 23.09.....Frame skipping setting (OFF) Any build made fast video( may be 20-18 f/s) any - drop and strobe effect....
Sorry my friend, but its kinda hard for me to understand the last part of your reply.
With frame skipping OFF. how many frames do you get until the camera stops recording with FPS Overide at 23,976?
I haven't tried the newest build yet, so maybe there is something in the newest build? anyone else got an answer for that?
Quote from: Kharak on September 23, 2013, 03:05:08 PM
Sorry my friend, but its kinda hard for me to understand the last part of your reply.
With frame skipping OFF. how many frames do you get until the camera stops recording with FPS Overide at 23,976?
I haven't tried the newest build yet, so maybe there is something in the newest build? anyone else got an answer for that?
Sorry for my English)) Camera don't stop recording, it write 65 -70 mb/s 1 min
Quote from: Stuntfoto on September 23, 2013, 03:14:59 PM
Sorry for my English)) Camera don't stop recording, it write 65 -70 mb/s 1 min
I can't really tell on that footage if the camera is skipping frames or not, but there might be another thing causing your RAW footage to go off sync on your Timecode. If you are using After Effects, then it will by default import your DNG sequence in 30 fps.
You need to Right Click your footage in project manager and click Interpret Footage and set the fps to 23,976. Also go in to Preferences >> Import and change 'Sequence Footage' to 23,976 so that After effects will import future sequences in that framerate.
Hope this solves your problem :)
Quote from: Kharak on September 23, 2013, 02:49:46 PM
3. Are you referring to Focus peaking? Cause its available in the last 3-4 builds. Called FPeaking in menu I think and there is Digic peaking which you adjust according to the FPeaking.
Hmm, when I activate DIGIC-Peaking, the image is just pretty much sharper or it is black without any image, but with lines indicating high contrast areas.
But it's comparable at all to 'normal' peaking.
Am I missing something?
Quote from: Kharak on September 23, 2013, 04:45:33 PM
I can't really tell on that footage if the camera is skipping frames or not, but there might be another thing causing your RAW footage to go off sync on your Timecode. If you are using After Effects, then it will by default import your DNG sequence in 30 fps.
You need to Right Click your footage in project manager and click Interpret Footage and set the fps to 23,976. Also go in to Preferences >> Import and change 'Sequence Footage' to 23,976 so that After effects will import future sequences in that framerate.
Hope this solves your problem :)
....Project settings 23.976 fs in AE ... I am rendering the new test with build 10.09.13 and set shutter speed 1/100
If convert RAW file to ProRes 444 in raw2dng - all good! And all frame in timeline)))))))))) but import dng sequence folder has error and drop frame... YES Interpret footage!!!!!All good!
Thank you ! And sorry my caveman's english!)))))
The flashing thing (brightness shift during ISO changed) ... Maybe caused by the ettr module? If on, i recommend to switch it off.
I think we could track down the problem:
* The ProRes 444 is correct.
* The export from After Effects is bad.
=> Some After Effects settings is not right.
Quote from: Stuntfoto on September 23, 2013, 09:59:51 PM
If convert RAW file to ProRes 444 in raw2dng - all good! And all frame in timeline)))))))))) but import dng sequence folder has error and drop frame... YES Interpret footage!!!!!All good!
Thank you ! And sorry my caveman's english!)))))
When I look at your Timecode, in both Prores 444 and After Effects I see it goes out of sync right before the 3 sec mark.
In both cases I see it starts jumping 0.02 frames.
or is it just me?
On your Slate you write 24 fps, do you have FPS overide set to 24 frames per second (Exact). Cause thats not 23,976 fps. and that will put your timecode out of sync eventually.
@a.d.
Possible to add the function to disabe proress in RAW2DNG again please? dragged the app into it and says along the lines, doesn't recognise file type, there times i dont need the proress video and takes up time from converting dngs whilst its making the video file.
Cheers :)
great
looks to me the dng sequence when imported into AE the frame rate isnt set to 24fps/23.976, import the dng's right click on it interpret footage and change the frame rate to 24fps, or watever u shot at.
Quote from: Kharak on September 23, 2013, 02:49:46 PM
1. Never had this issue man, so I suggest you format card in camera and re-install ML. Or are these just flashes on the screen or do you also see pink flashes on the actual DNG's?
2. Not sure about this, is you ISO set to Auto in canon menu? Your dial on top of the camera, needs to be at M - Mode (Manual).
3. Are you referring to Focus peaking? Cause its available in the last 3-4 builds. Called FPeaking in menu I think and there is Digic peaking which you adjust according to the FPeaking.
Hope it helps.
Everything is set to manual, after I formatted and re installed, both the jumping exposure and the pink flashes seem to have disappeared.
The red dot is a dead pixel but it only appears in video mode, does not come up in photos. There is a lot of talk about it but no one seems to have a solution other than sending it in?
Quote from: Samco on September 24, 2013, 06:43:32 PM
Everything is set to manual, after I formatted and re installed, both the jumping exposure and the pink flashes seem to have disappeared.
The red dot is a dead pixel but it only appears in video mode, does not come up in photos. There is a lot of talk about it but no one seems to have a solution other than sending it in?
Glad it worked for ya.
Regarding the dead pixel.. I used to have one, that was before RAW. But there is a way for you to do a manual Sensor Cleaning which will fix certain "dead" pixels (worked for me). I don't remember the specifics, but you can google it or youtube it. Basically you go in to canon menu and select manual sensor cleaning, you click it and the camera will start doing a sensor cleaning indefinitely. When I did it, I was told to let the camera clean for 1 min. You can't control anything in the mean time, if I remember correctly. So not sure if you have to just turn off the camera or not. But these are the basics. I suggest you google this to get confirmation. There is a video on youtube which explains it.
Just testing the Sept.20th built. :)
I notice a decrease in Speed a little, When the hdmi is plug in
to evf and or ninja recorder. At 1856x1004 23.976p about 3000 to 3500 Frames.
With out them plug in to the hdmi port i can maintain 1856x1004 23.976p @75MB/s
for about 14,250 Frames = 42GB
but when the evf and or hdmi recorder are pluged in i have to drop down to 1880x930 @23.976.
in which i get about 15,000 Fames=43 GB.
I was wondering if the HDMI port takes extra resources to stream the 60i signal ?
being it has a 2:3 pulldown, that can be exacted by "Reverse Telecine"
But on the Brighter Side there is No more Clashes with the hdmi connected :D
After recording Raw.
So to keep the backup & evf working i'll use 1880x930 for now. :)
I will be testing out the Workflow tomorrow afternoon,
I'll be filming a Dentist office Promo/testamentary, Mostly Head shots.
I'm starting to wonder, will there ever be anymore speed improvements?
Quote from: xNiNELiVES on September 25, 2013, 12:26:09 AM
I'm starting to wonder, will there ever be anymore speed improvements?
I have not really seen a big gain in performance since mid to late July .
its looking like we may have reach the limit with 5d2.
At lest with is version of ML Raw.
Ok...
Hello, guys,
i have been testing video raw and I keep getting back green colored picture (see link). Could anybody tell me what am I missing? Thank You. petr. link:https://plus.google.com/photos/109116047125258921069/albums/5926826577361752993?authkey=CIDF686kw_fhgwE (https://plus.google.com/photos/109116047125258921069/albums/5926826577361752993?authkey=CIDF686kw_fhgwE)
What software are you using to read the dng's and what converter are you using to convert raw to dng (raw2dng or raw2cdng) ?
@Doyle4
Sorry, Currently I don't have much times for it, 'cause I need to code from scratch! (procrastinate)
@Pijer
Yes, more infos please!
Quote from: a.d. on September 25, 2013, 05:15:19 PM
@Doyle4
Sorry, Currently I don't have much times for it, 'cause I need to code from scratch! (procrastinate)
@Pijer
Yes, more infos please!
Yo! a.d. My king!
Can you clarify a bit on why you need to code from scratch?
With love.
Your eternal servant.
Kharak ;)
Thank You guys, so much!
I am using raw2cdng coz raw2dng link at the formum is (was) broken. To read dng I use lightroom.
Thank You.
p.
Quote from: Pijer on September 25, 2013, 06:16:19 PM
Thank You guys, so much!
I am using raw2cdng coz raw2dng link at the formum is (was) broken. To read dng I use lightroom.
Thank You.
p.
I don't have light room but I had a similar issue with cdng's in another app. Everthing was green in there as well, in that app I had to un check and option for using color matrix from the meta data. I am not sure but I think it's either the Color Matrix or Forward Matrix data stored in the exif that is not correct and it is messing things up. You may want to try raw2dng instead and see if the problem goes away, it doesn't write as much meta data to the file.
Try the link at one the first post of this topic for downloading a.d's module. There is a link to the most current raw2dng there.
How do I re-enable global draw during raw recording? I am no longer trying to squeeze every last bit of speed out of the camera anymore and I would like to have magic zoom and focus peaking back for raw shooting. I remember there was an option to disable during raw shooting but cannot find it any more. Thanks.
@a.d.
No worries dude, thats understandable, thanks for getting back to me.
Quote from: reddeercity on September 25, 2013, 01:54:33 AM
I have not really seen a big gain in performance since mid to late July .
its looking like we may have reach the limit with 5d2.
At lest with is version of ML Raw.
Been a few big improvements since then, small hacks and the odd speed improvements, to see its full potential you will need a 1000x CF card. some dont notice but i have, iv gone from 65mb wtite to 72mb, big notice for me :)
@Kharak
The app is based on raw2dng from scrax and it's limited. I want to do more like RAWMagic, so I need to start from Ground Zero. I notice you do a lot of crop mode recording, you could try this version: https://bitbucket.org/a_d_/laboratory/downloads
@bnvm
Interface: Feature +
You should keep in mind: It could produce random pink frame on DIGIC IV based Camera! Maybe your camera is not suffer from that!
@Pijer
If you go the Adobe ACR way, I recommend to use 5D2_WIN_raw2dng.zip, because raw2cdng adds fixed Camera Model, Canon EOS PHR. However raw2cdng is fast and it works well with DaVinci Resolve.
@a.d thanks I was not aware of the pink frame issue, I think I will stay away from using it for now.
Quote from: Doyle4 on September 25, 2013, 07:42:15 PM
Been a few big improvements since then, small hacks and the odd speed improvements, to see its full potential you will need a 1000x CF card. some dont notice but i have, iv gone from 65mb wtite to 72mb, big notice for me :)
No not really, i have been using 2 Lexar 1000x Cards since July,
At the Max frames with small hacks on etc., there is no one that has reported
anything better then 1856x1004 23.976p for continuous recording up to 42GB = 14,250 frames!
As far as i have read there no one get including me that can get more then 42GB at 1856x1004 frame size.
i record at 75.0MB/s in non-crop mode & at 2k crop mode i record at 76.6MB/s
The Hardware has reach its Limits.
The improvements where really for the Slower cards :)
Quote from: reddeercity on September 25, 2013, 09:49:40 PM
No not really, i have been using 2 Lexar 1000x Cards since July,
At the Max frames with small hacks on etc., there is no one that has reported
anything better then 1856x1004 23.976p for continuous recording up to 42GB = 14,250 frames!
As far as i have read there no one get including me that can get more then 42GB at 1856x1004 frame size.
i record at 75.0MB/s in non-crop mode & at 2k crop mode i record at 76.6MB/s
The Hardware has reach its Limits.
The improvements where really for the Slower cards :)
So ~75MB/s is the max, hardware limited.
Do you think a 80 or 90MB/s card is good enough or we need a 1000x to reach 75MB/s?
I read many reports/tests here about cards & hardware speed but for 5D2 is hard to be synthetic in results..
I have hit nearly 80MB/s in crop mode with a 32GB KomputerBay card, so doubt we've seen the last drops of performance squeezed out of Magic Lantern yet.
Yeah actually. In rare occasions I somehow am able to get 80mb/s. I think I even did this in non-crop mode.
I saw somewhere 'theoretically' hardware card reader of the 5D2 is up to 90MB/s, but maybe it could be for read operations (?) and for write it's a bit less.
So with 75~80MB/s we are close to the maximum.
Quote from: a.d. on September 25, 2013, 08:55:43 PM
@Kharak
The app is based on raw2dng from scrax and it's limited. I want to do more like RAWMagic, so I need to start from Ground Zero. I notice you do a lot of crop mode recording, you could try this version: https://bitbucket.org/a_d_/laboratory/downloads
@ a.d. Thanks man, I'll give it a try.
@ SpcCb. Have faith my friend, believe in the magic (lantern) that is being performed on our beloved 5D's. I suggest you go for as fast a card as possible. Its not just the max speed in which the camera will be able to record in, but speaking from my experience. I had a 60 MB/s card and then upgraded to a 128gb 150 MB/s card, Recording speed hits max ofcourse, but also the transfer rate is phenomenal! Moving footage at 100-140 MB/s (it varies) is fast! and saves you a lot of time if your on set or out in the field and need to empty your card during takes. It all depends on what you gonna use it for.
On another note, having a 42 gb limit is not something I see as a problem. Most I've recorded was 26 gb, once when I was filming a trawler breaking through waves and was waiting for that one big splash. But I felt how hot my card and camera got around the CF slot. So stopped in between and did 10 gig takes at a time. But other than that, I really don't see me ever gonna film 128 gb in one take, professionally. The 5D RAW II is not an interview camera ;)
I´ve got one question on my 5D2 and the Komputerbay 1000x 64GB card.
Here is my benchmark:
(http://s1.directupload.net/images/130927/xuy9a9sl.jpg)
Since i got about 75MB/s writing speeds on 1880x1058 (and even in crop mode about 77MB/s) is my card good enough even with this benchmarks? ... since the camera speed limit is reached.
or should i replace this card?
Quote from: ch_d on September 27, 2013, 12:59:32 PM
... since the camera speed limit is reached.
or should i replace this card?
Why would you replace it?
You will also find when recording your write speed increases, this is because its warming up.. iv done a benchmark before and write was 67mb, when it came to recording it hit 71mb.. test it on RAW video first before sending it back, remember, the benchmark is only 5mins long.. so you wont see the cards full potential.
Quote from: Africashot on September 27, 2013, 01:23:51 PM
Why would you replace it?
because the benchmark results are too slow ... ? aren`t faster cards faster in terms of transfering to the computer / copying files?
i saw way better results on the 64gb 1000x komputerbay card
Quote from: ch_d on September 27, 2013, 02:20:38 PM
because the benchmark results are too slow ... ?
i saw way better results on the 64gb 1000x komputerbay card
record a 4gb+ video, doesn't matter what but keep on eye on write speed, what do you get?
Also some devs have said to format the card before recording,
Have anyone read anything on timecode ability for ML, also I think I read we can set our own presets now so can we keyword soon?
Why are you all benchmarking in photo mode?
Quote from: mvejerslev on September 27, 2013, 03:05:01 PM
Why are you all benchmarking in photo mode?
here is one in video mode
(http://oi41.tinypic.com/2poy3pg.jpg)
Benchmark in Playback:
turn on camera, then press info till screen is off (black) then run benchmark, should say Playback, not video or photo
Quote from: Doyle4 on September 27, 2013, 03:31:06 PM
Benchmark in Playback:
turn on camera, then press info till screen is off (black) then run benchmark, should say Playback, not video or photo
so here is one in playback mode:
(http://oi44.tinypic.com/2i0w7wk.jpg)
Quote from: ch_d on September 27, 2013, 02:20:38 PM
because the benchmark results are too slow ... ?
I had not realized you bench marked in photo mode, this way the card indeed looks slow, I assume you must have tried formatting too... was it any better at any earlier stage, do you get better results with other cards?
Quote from: ch_d on September 27, 2013, 03:47:27 PM
so here is one in playback mode:
(http://oi44.tinypic.com/2i0w7wk.jpg)
Much better and thats good speeds for the markii :)
Hi,
With the new build, bolt_rec.mo gives an error and won't load... I checked it from bitbucket, it changed 4 days ago, but I failed to find the compiled version. There is only bolt_rec.c .. does anybody point me to the latest compiled version of bolt_rec.mo? I tried to compile but, it exceeds my abilities..
Thanks,
Melih
it works well with ce9fb256205c.zip
BOLT_REC.MO (https://dl.dropboxusercontent.com/u/13314708/BOLT_REC.MO)
Thank you a.d. :)
What ISO are you guys using when shooting 5D2 Raw?
A couple of weeks ago I did a quickt test to see how the Raw video changes depending on the ISO setting and I found that the higher the ISO, the less noise was visible. Can that be right?
If I remember correctly, I also saw a kind of "grouping" of certain ISOs; meaning that the actual exposure was similar between multiple ISOs.
Quote from: ValentinSteiner on September 30, 2013, 11:49:13 PM
What ISO are you guys using when shooting 5D2 Raw?
A couple of weeks ago I did a quickt test to see how the Raw video changes depending on the ISO setting and I found that the higher the ISO, the less noise was visible. Can that be right?
If I remember correctly, I also saw a kind of "grouping" of certain ISOs; meaning that the actual exposure was similar between multiple ISOs.
I find the the higher you go with ISO the more chance of noise,
But as long as you don't under expose the image use what ISO looks good to you :)
i use negative (-0.3) or push down ML digital ISO.
So at 400 ISO (canon) becomes Magic Lantern digital 320 ISO .
There is little to no noise with push down ISO's
These are may experiences with ML ISO's
Other people may have some more advice to add. ;)
Well the push down ISOs aren't actually magiclantern ISOs, they're completely canon's doing. I saw in a thread (something posted about a month or so ago) that the digital ISOs are exactly the same in noise performance to their native ISO, when shooting raw. Using the pull down ISOs definitely work better in H.264, but there is no benefit in terms of noise performance in raw.
What I mean by this is that 160, 200, and 250 are all the same noise performance in raw, with 160 being .80 exposure of 200 and 250 being 1.25 of 200. Not 100% sure if that's how you would make the analogy, but that's the basic idea. So 320, 400, and 500 are all the same as well, in raw. It just keeps going on. This is how I understand it at least. I haven't done any tests with it yet, but that's what makes sense with understanding the hardware and looking at other people's tests.
Quote from: ValentinSteiner on September 30, 2013, 11:49:13 PM
What ISO are you guys using when shooting 5D2 Raw?
A couple of weeks ago I did a quickt test to see how the Raw video changes depending on the ISO setting and I found that the higher the ISO, the less noise was visible. Can that be right?
If I remember correctly, I also saw a kind of "grouping" of certain ISOs; meaning that the actual exposure was similar between multiple ISOs.
This "grouping" you speak of, I might be able to testify to that.
Cause a week ago or so me and a friend of mine were comparing extreme low light performance between my 5dii and his FS100.
We had ISO's ranging from 12000, 6400 and 3200. But when I looked at the DNG's the extreme ISO scenes were all at the same exposure.
6400 and 12000 are pushed from 3200 native iso. they were all exposed like the 3200 ISO. But in camera they looked brighter. Quite weird, but I guess there isn't too much difference between pushing ISO in camera and pushing it in ACR. I've had great results in ACR.
PS. I beat his FS1000. Some of his scenes seemed brighter and vice versa, but the 5D RAW II had much sharper images. FS100 records in AVCHD (standard) with some kind of "box" it can record AVI Uncompressed 12 bit, not sure how that compares to RAW.
Quote from: robert.roth001 on October 01, 2013, 12:40:38 AM
Well the push down ISOs aren't actually magiclantern ISOs, they're completely canon's doing. I saw in a thread (something posted about a month or so ago) that the digital ISOs are exactly the same in noise performance to their native ISO, when shooting raw. Using the pull down ISOs definitely work better in H.264, but there is no benefit in terms of noise performance in raw.
What I mean by this is that 160, 200, and 250 are all the same noise performance in raw, with 160 being .80 exposure of 200 and 250 being 1.25 of 200. Not 100% sure if that's how you would make the analogy, but that's the basic idea. So 320, 400, and 500 are all the same as well, in raw. It just keeps going on. This is how I understand it at least. I haven't done any tests with it yet, but that's what makes sense with understanding the hardware and looking at other people's tests.
Well form my video samples i tested i have found that if you use negative gain the image is very clean No noise.
Being most of the noise is in the Luma channel, The black & white of the image.
So when you push the expose in Post i find there is more latitude in the shadows & darks.
From my understanding when you use the ML digital gain ISO's there are a different algorithm , i think no sure though.
The results of this is that i do not have to use any noise reduction software at all, no matter what iso i use. :)
Quote from: reddeercity on October 01, 2013, 06:38:37 AM
Well form my video samples i tested i have found that if you use negative gain the image is very clean No noise.
Being most of the noise is in the Luma channel, The black & white of the image.
So when you push the expose in Post i find there is more latitude in the shadows & darks.
From my understanding when you use the ML digital gain ISO's there are a different algorithm , i think no sure though.
The results of this is that i do not have to use any noise reduction software at all, no matter what iso i use. :)
Give us some examples, I have a hard time seeing how you could pull this off if you are already at the cameras limit, at say, ISO1600 (which is the max native ISO for the 5D Mark II) and are still underexposed.
Isn't this merely true to your style of shooting because you have plenty of available light?
In RAW it only makes sense using ISO100, 200, 400, 800 and 1600. The rest are just manipulated afterwards, e.g. ISO160 is just ISO200.
To test it, shoot something at "ML" ISO160 and Canon ISO200, then pull down the ISO200 to 160 in post. Do you see a difference?
100,200,400 are digital iso's,
320,640,1600 are not :) 1600 gives less noise than 100 if done correct ;)
Quote from: Doyle4 on October 01, 2013, 12:14:04 PM
100,200,400 are digital iso's,
320,640,1600 are not :) 1600 gives less noise than 100 if done correct ;)
Can you expand on this theory? I'd really like to know more about how to make 1600 look as clean as 100!
Quote from: Doyle4 on October 01, 2013, 12:14:04 PM
100,200,400 are digital iso's,
320,640,1600 are not :) 1600 gives less noise than 100 if done correct ;)
I think there's a mistake somewhere :)
Hi there,
Here's a test with ml raw, hope you like
https://www.youtube.com/watch?feature=player_embedded&v=8_7UKTDmr0Y (https://www.youtube.com/watch?feature=player_embedded&v=8_7UKTDmr0Y)
Cheers,
Vincent
Quote from: SpcCb on October 01, 2013, 02:20:21 PM
I think there's a mistake somewhere :)
No mistakes, Doyle4 is right: 160 and multiples are not digital iso's, recommended for video recording.
Look in ML menu, Expo->ISO->submenu ;)
Quote from: valwello on October 02, 2013, 10:30:57 AM
No mistakes, Doyle4 is right: 160 and multiples are not digital iso's, recommended for video recording.
No no no, 160 and multiples ARE digital ISOs, whereas multiples of 100 is analog, native ISO for the sensor.
Listen to a1ex on this one.
Quote from: PressureFM on October 02, 2013, 10:40:12 AM
No no no, 160 and multiples ARE digital ISOs, whereas multiples of 100 is analog, native ISO for the sensor.
Listen to a1ex on this one.
Well, everywhere in the net you can read the native iso is 160 an multiples.
Personally I read only one article saying the native iso is 100 instead.
So which is the truth?
So. What about "Highlight Tone Priority"?
Since this was a little crappy with h264 ... what about RAW Video - should we turn this on?
UPDATE: http://www.magiclantern.fm/forum/index.php?topic=6967.0 (http://www.magiclantern.fm/forum/index.php?topic=6967.0)
With raw, does it even matter what ISO we've set?
Quote from: silvertonesx24 on October 02, 2013, 05:29:13 PM
With raw, does it even matter what ISO we've set?
Yes, as long as they are 'natural' analog ISOs (100, 200 etc without digital gain)
Quote from: Rewind on October 02, 2013, 05:40:42 PM
Yes, as long as they are 'natural' analog ISOs (100, 200 etc without digital gain)
Can anyone expand on that?
I'm under the impression that on the mk II the ISO 320 has the best noise/grain because it is acctually 400 ISO, with some sort of digital negative gain, supressing the noise in dark areas(on H264 that is). Am I mistaken?
Which are the Ideal ISOs for raw recording ? which ISO would be "0db" in your opinion?
When you shooting raw, digital gain doesn't affect recording at all.
So, if you shooting raw at iso 320 (400 -0.3 ev), the result will be the same as at iso 400.
Digital gain applies after the raw stream is taken.
When you shooting h.264 things become a bit more complicated (negative digital iso may have better highlight roll-off etc.), but in general, if you're shooting at iso 320, your result noisewise will be pretty much identical to iso 400 with negative exposure adjustment in post.
Also worth noting are gains made using recent changes.
With Sept. 26 build.
Higher continuous recording resolutions is now at 1856 x 1004 at 1x mode.
AND you can now set Photo/Stills at RAW even with Raw_rec module ON.
This is good for those wanting to take quality stills while RAW video module is engaged.
Quote from: ted ramasola on October 04, 2013, 09:41:14 PM
Also worth noting are gains made using recent changes.
With Sept. 26 build.
Higher continuous recording resolutions is now at 1856 x 1004 at 1x mode.
AND you can now set Photo/Stills at RAW even with Raw_rec module ON.
This is good for those wanting to take quality stills while RAW video module is engaged.
What are you talking about?
Quote from: a1ex on October 04, 2013, 09:46:24 PM
What are you talking about?
The previous builds need raw stills to be set to be set to non to get optimum performance.
edit.. I checked my records . seemed like the 1856 x 1004 was already achieved since 2 months ago. sorry about that.
Its just the RAW stills settings which I found as something new as I've always left it at NONE to get continuous record with raw.
For iso issue..
Read:
http://photocascadia.wordpress.com/2011/05/13/canon-eos-5d-mark-ii-iso-noise-test/
Also in there is a link to a well known tech company who also did a similar test.. results are there for you.
Quote from: Doyle4 on October 05, 2013, 01:45:54 AM
For iso issue..
Read:
http://photocascadia.wordpress.com/2011/05/13/canon-eos-5d-mark-ii-iso-noise-test/
Also in there is a link to a well known tech company who also did a similar test.. results are there for you.
yes but this is over 2 Years old!
I don't think there used Magic Lantern hack to do there Tests,
and i read here on the ML form that ML digital ISO's have a different algorithm
Then the Canon digital ISO's which is cleaner.
All my Video Samples i posted here on the Magic Lantern Form,
Have (-.03) negative gain,
Give it a try, as long as you expose correctly there will be no noise.
I use this set up on all my Paid Work. :)
Quote from: Doyle4 on October 05, 2013, 01:45:54 AM
For iso issue..
Read:
http://photocascadia.wordpress.com/2011/05/13/canon-eos-5d-mark-ii-iso-noise-test/
Also in there is a link to a well known tech company who also did a similar test.. results are there for you.
Yeah this is completely invalid for raw recording. This is how the camera acts with h.264.. Completely different beast with raw. :)
Can you explain how its invalid? Raw is uncompressed multiple images, h.264 is compressed.
i shoot alot of stuff at 1600, much better than 100, i also use 320 and 640, do some test's and you will see.
Because what comes out of the camera is 100, 200, 400, etc, iso. 160, 320, etc etc are applied as digital gain, aka processing done inside of the camera. This matters in h.264 because that is what is written to the file. However, the raw file is still only 100, or 200, or whatever you shot it at. When you open the raw file up in your editor of choice the digital gain is just metadata. Basically, something that you can change at will. You can take a 200 iso raw file and make it look exactly like the 160 iso raw file. When you open the file up in ACR there is a whole lot of metadata being displayed. That isn't necessarily bad, but it's faulty to think that's what is coming off of the sensor. Open the same DNGs up in Resolve and switch the colorspace to BMD film. That will give you a flat log profile that comes right off of the sensor.
Now, I haven't been able to do my tests yet to confirm this 100%, but that is how I understand it to work. I know for a fact that's how metadata and ACR works. Now whether or not the difference in raw files between 160 iso and 200 iso is just metadata... I'm going to have to test that, which I definitely plan on doing.
However what I do know is that anything other than the native ISOs (100, 200, 400, etc) when shooting raw is processing applied after coming off the sensor and by definition raw files do not have any processing burned into the image.
Quote from: robert.roth001 on October 05, 2013, 03:32:25 AM
Because what comes out of the camera is 100, 200, 400, etc, iso. 160, 320, etc etc are applied as digital gain, aka processing done inside of the camera. This matters in h.264 because that is what is written to the file. However, the raw file is still only 100, or 200, or whatever you shot it at. When you open the raw file up in your editor of choice the digital gain is just metadata. Basically, something that you can change at will. You can take a 200 iso raw file and make it look exactly like the 160 iso raw file. When you open the file up in ACR there is a whole lot of metadata being displayed. That isn't necessarily bad, but it's faulty to think that's what is coming off of the sensor. Open the same DNGs up in Resolve and switch the colorspace to BMD film. That will give you a flat log profile that comes right off of the sensor.
Now, I haven't been able to do my tests yet to confirm this 100%, but that is how I understand it to work. I know for a fact that's how metadata and ACR works. Now whether or not the difference in raw files between 160 iso and 200 iso is just metadata... I'm going to have to test that, which I definitely plan on doing.
However what I do know is that anything other than the native ISOs (100, 200, 400, etc) when shooting raw is processing applied after coming off the sensor and by definition raw files do not have any processing burned into the image.
After my latest test, I agree with this. My "extreme" iso tests all showed to be at 3200 ISO. even though they were set at 12000 iso etc.
@a.d.
Whats the details of new build please dude?
Nice one! With the 2013-10-04 version i got: 77.8MB/s on my 5DM2 with KB 1000x 64GB.
(in crop mode 79,6MB/s)
thank you!
Yeah, nice speed increase with the latest build. Saw over 77MB/s on my 32GB KomputerBay 1000x card.
Awesome a speed increase. A rarity these are!
what's are the steps for optimum speed write again?
like do i have to format the card on a card reader or inside the camera?
@a.d.
Thanks for posting update.
What are the changes in this build?
WOW.... 83mb Write!!! Best update yet!!
total beginner posting..
I have everything installed.. downloaded the stable release installed it.. then dl the nightly build and replaced the appropriate folders.. I noticed the modules say WILL LOAD.. do I have to restart my camera everytime if I want to turn modules on and off? I remember maybe two months ago I could just press the load modules button and they would simply load.. then if i didn't want them I could turn them off just as easy? All with out turning my camera on and off?.
gotta turn camera off then on, but there is now a custom config loader, make different configs with what modules you need, eg: RAW video config, Photo config, h.264 config etc etc.
Quote from: vikado on October 05, 2013, 10:47:23 PM
what's are the steps for optimum speed write again?
like do i have to format the card on a card reader or inside the camera?
I format from camera BUT a computer format i noticed can be that little bit better, but with hacks on and camera warm up i get nice write speeds, i hit 83mb today :)
Quote from: Doyle4 on October 06, 2013, 02:41:29 AM
I format from camera BUT a computer format i noticed can be that little bit better, but with hacks on and camera warm up i get nice write speeds, i hit 83mb today :)
whoa. 83mb. that's awesome.
doesn't matter but isn't that close to the write speed for 1920x1080?
and which card?
5Dmkii can hit the full 1920x1080 unfortunately atm, my 83mb write was on my card benchmark test, too late here in UK to test actually filming but i will tomorrow on the largest resolution the mkii can @16:9, i usually film @2:1 but im actually interested my self to see what can be done now with this beast of an update haha.
Hi all :)
Just check out the(f620a8f2b27d )Oct.,4 2013 Built from A.D.(the one with the disclaimer)
I guess i was Wrong! there is a little more speed still in 5D2 :)
I would suspect there is Better Memory management going on.
but we still have a 45 GB wall, which is better then before it was 42GB per shot
So to the results,
all tests on Lexar 1000x 64GB card
Without HDMI connected to Zacuto Evf pass-though to Ninja hdmi recorder.
1872x1012 1.85:1 AR @23.976p 76.1MB/s continuous up to 45GB about 13,500 Frame
Crop mode
2048x930 2.20:1 AR @23.976p 76.5 MB/s continuous up to 45GB (this unchanged from previous Built)
2048x1024 2:1 AR @23.976 79.8 MB/s 1,254 Frames
With HDMI connected to Zacuto Evf pass-though to Ninja hdmi recorder.
1872x1012 1.85:1 AR @23.976p 75.8MB/s 3875 Frames
1856x1004 1.85:1 AR @23.976p 74.8MB/s continuous up to 43GB :D (perfect for backup recorder, close to full HD)
before i could only use 1880x940 with hdmi connected for continuous.
Cpu temp was up a little to 63 degrees C, before it hang around 58 to 61
Like the New Font & layout. :)
No crashes with the hdmi connected while recorder Raw.
Very good job A.D.
Quote from: Doyle4 on October 06, 2013, 12:39:33 AM
WOW.... 83mb Write!!! Best update yet!!
what card do you use? 83mb/s seems very utopic ....
Transcend 32gb 1000x
Quote from: reddeercity on October 06, 2013, 03:39:54 AM
Hi all :)
Just check out the(f620a8f2b27d )Oct.,4 2013 Built from A.D.(the one with the disclaimer)
I guess i was Wrong! there is a little more speed still in 5D2 :)
I would suspect there is Better Memory management going on.
but we still have a 45 GB wall, which is better then before it was 42GB per shot
So to the results,
all tests on Lexar 1000x 64GB card
Without HDMI connected to Zacuto Evf pass-though to Ninja hdmi recorder.
1872x1012 1.85:1 AR @23.976p 76.1MB/s continuous up to 45GB about 13,500 Frame
Crop mode
2048x930 2.20:1 AR @23.976p 76.5 MB/s continuous up to 45GB (this unchanged from previous Built)
2048x1024 2:1 AR @23.976 79.8 MB/s 1,254 Frames
Testing 1872 x 1012 on 64gig 1000x komputerbay, it seems the 43-45 gig wall is also there. Strange that the datarate is constant at 75mbps then all of a sudden drops to 1.2 - 2 mbps past the 43-45gig mark. But yeah, it's already pretty usable. Its just something the user should take note of when having long takes.
Quote from: ted ramasola on October 06, 2013, 05:44:54 AM
Testing 1872 x 1012 on 64gig 1000x komputerbay, it seems the 43-45 gig wall is also there. Strange that the datarate is constant at 75mbps then all of a sudden drops to 1.2 - 2 mbps past the 43-45gig mark. But yeah, it's already pretty usable. Its just something the user should take note of when having long takes.
I have to wounder if its a Fat32 System problem.
I remembered the KB tech guy talking about this issue. I can't remember the details but it is something they know about.
Is it just me or isnt the new layout working as it shold?
The 2 rows of info should be on top and bottom, but all on bottom on my 5d2.
Maybe im missing something, settings etc?
A.d. can you update the changelog here on the thread. We are all wondering what changed.
Are you guys getting bigger resolutions or only more speed?
I just installed the latest build, upgraded from the basic alpha version. I'm very confused though, why is the max horizontal pixel length now 1872? It was 1880 on the last build. I understood why it was 1880 and not 1920 (canon just upscales to full HD from 1880). Either way, why did we lose those 8 pixels?
Quote from: robert.roth001 on October 06, 2013, 09:31:16 PM
I just installed the latest build, upgraded from the basic alpha version. I'm very confused though, why is the max horizontal pixel length now 1872? It was 1880 on the last build. I understood why it was 1880 and not 1920 (canon just upscales to full HD from 1880). Either way, why did we lose those 8 pixels?
On previews builds 1880 was an option you had to toggle ON.
Quote from: ch_d on October 06, 2013, 04:19:04 AM
what card do you use? 83mb/s seems very utopic ....
76mb whilst recording dude, 1880 (largest one, cant remember the height ha) @2:1 76mb and 16:9 73.8
Sorry the 83mb was on the benchmark.
Quote from: robert.roth001 on October 06, 2013, 09:31:16 PM
I just installed the latest build, upgraded from the basic alpha version. I'm very confused though, why is the max horizontal pixel length now 1872? It was 1880 on the last build. I understood why it was 1880 and not 1920 (canon just upscales to full HD from 1880). Either way, why did we lose those 8 pixels?
It depends of the build you use.
Builds here: -> https://bitbucket.org/a_d_/magic-lantern/downloads may had the 1880px capability. But builds here: -> http://builds.magiclantern.fm/#/ don't.
Quote from: SpcCb on October 07, 2013, 12:56:00 AM
It depends of the build you use.
Builds here: -> https://bitbucket.org/a_d_/magic-lantern/downloads may had the 1880px capability. But builds here: -> http://builds.magiclantern.fm/#/ don't.
Oh okay I see that. But why the difference? Different people working on those builds? If so, why would they have a difference in the max pixels?
Quote from: robert.roth001 on October 07, 2013, 01:33:36 AM
Oh okay I see that. But why the difference? Different people working on those builds? If so, why would they have a difference in the max pixels?
The build that has 1880 is a.d's custom build it is the only one that has the option, it is based of the "official" nightly build with some of his additional tweaks. When all this raw stuff was very new there was work being done on the main code base and then there are specific people who were compiling the builds for each camera so that all us of non coders could have access to it before it was in the nightly builds. I am not sure of the exact reason but I do know that having 1880 is something that is unique to the MKII and to have that option in the nightly builds would mean a specific exception just for the MKII. It seems like most of the dev's prefer not to have those kinds of things to make code more portable to other cameras and don't feel it is worth it for only 8 pixels. Also image sizes that are evenly divisible by 16 are more efficient to write 1872 is 1880 is not. Chances are when the next release of ML comes out that has raw video probably will not have 1880 as an option.
a.d's build is a custom build just for us MKII users.
The newest build (2013-10-04) definitly has a speed increase. I went from 75mb avg to 77mb avg with a Kompbay 64gb. The overlay on the newest version has some problems, the coloring is gone and the RGB scope is missing from the bottom left. I've installed on 3 different cards and they all have the same Overlay problem. Other than that I ran it all day yesterday during a shoot and it worked awesome. Fix the overlay and this will be the new go-to version for RAW video.
hello all,
I look for a moment realized on the progress 5d ii and i have installed the latest build of October 04, I have a 32 gb card Komputerbay 1000 x n but I can not manage to make more than 500 dng in 1880 x 1058 dng or 1000 with optional interface X.
What are the optimal power dampers for continuous shooting? what options they have to activate and deactivate? 24fps? small hack? auto preview? warm up card 128 mb, 1gb? standard interface, X, + feature? global draw on or off?
many questions that could help all the people who ask the same questions as me.
Even simpler, you can share a configuration, if so, could you share yours? thank you very much
Hi folks!
I'm new here but I've looked around for a while, there is one thing, (no not ONLY one thing :) ) but there is one thing that I am wondering now. I've purchased a kumbuterbay card 1000x, and going to record some RAW files, does it mather if I format the card in fat32 or exfat, I really don't understand that bit, or is it just for the mkIII-users? Files larger than 4 gig, will they still work in the standard format card? I've read the entire thread and haven't seen this questions. I'm sorry for stupid questions and bad spelling!
Cheers!
Quote from: lladron on October 07, 2013, 04:04:34 PM
Hi folks!
I'm new here but I've looked around for a while, there is one thing, (no not ONLY one thing :) ) but there is one thing that I am wondering now. I've purchased a kumbuterbay card 1000x, and going to record some RAW files, does it mather if I format the card in fat32 or exfat, I really don't understand that bit, or is it just for the mkIII-users? Files larger than 4 gig, will they still work in the standard format card? I've read the entire thread and haven't seen this questions. I'm sorry for stupid questions and bad spelling!
Cheers!
Yes I wonder this as well, a little list of what fine tunnings that work the best :)
I can't help you on the fine tuning, but what I can tell you is that the camera will create a single .raw file up until 4GB is reached. After that it creates a new file (I think it's a .rar) called a spanning file. When you go to extract the DNGs just drop all of the files into the extractor (I use raw2cdng) and it'll do everything for you.
Hope that helps!
oct 4 build has LV overlay issues, the 2 rows of info on the bottom is overlapping each other and alternates which one is over the other with every refresh. The one color (white) is fine with me. lesser visual clutter.
I didn't notice any issues on my 5D2.
(https://scontent-b.xx.fbcdn.net/hphotos-prn1/1385710_381540638643393_448854855_n.jpg)
at first I thought is was wrong settings so I deleted the .cfg file but the overlapping info on the bottom was still there. I also tried with different resolutions.
Quote from: jessy on October 07, 2013, 03:41:47 PM
hello all,
I look for a moment realized on the progress 5d ii and i have installed the latest build of October 04, I have a 32 gb card Komputerbay 1000 x n but I can not manage to make more than 500 dng in 1880 x 1058 dng or 1000 with optional interface X.
What are the optimal power dampers for continuous shooting? what options they have to activate and deactivate? 24fps? small hack? auto preview? warm up card 128 mb, 1gb? standard interface, X, + feature? global draw on or off?
many questions that could help all the people who ask the same questions as me.
Even simpler, you can share a configuration, if so, could you share yours? thank you very much
Sure
Aspect ratio 2:1 1880x940
1880 on
Small hacks on
23.97fps
32gb KB
I find these are the important ones in my case.
I get continuous Rec and export beautiful 2k+ tiff out of it.
I can even leave global draw on and don't have to mess with the picture format or anything
Quote from: guilhermemartins on October 07, 2013, 11:51:16 PM
Sure
Aspect ratio 2:1 1880x940
1880 on
Small hacks on
23.97fps
32gb KB
I find these are the important ones in my case.
I get continuous Rec and export beautiful 2k+ tiff out of it.
I can even leave global draw on and don't have to mess with the picture format or anything
How are you converting to 2K and are the final video file clean?
Quote from: dariSSight on October 08, 2013, 01:29:07 AM
How are you converting to 2K and are the final video file clean?
Either in photoshop or LR. This can be done in After Effects as well. It basically is sharpening, and changing the resolution on export (it's more complex than just sharpening same principle)
Quote from: dariSSight on October 08, 2013, 01:29:07 AM
How are you converting to 2K and are the final video file clean?
Photoshop Raw
Clean enough, some kinds is artifacts such as moire are more visible in raw, but I guess one would get those upscale or not.
So far the shadows recovery isn't fantastic and too much photoshop noise reduction works only until certain point. The same to anti-moire. Still it is possible to bring 1 mabe two stops of shadows back to visible spectrum and denoise it in post.
Highlight recovery is dreamlike, redlike! (ok mabe I'm overreacting).
People tend to mess up with accrual color on raw files an get weird results (in my opinion). It is best to get the most out of the contrast and exposure, WB and do the actual coloring on the prores 4444 file afterwards (using or not a log lut). Unless of course for chroma purposes.
I usually downscale the 2k+ tiff to 1080p (more realistic size for commercial productions of a small company) for all my testing. Although we're producing a short (expected for next year) where we intend to use the full might of 5D raw in which case I intend to do the whole thing in 2k (so far good results yei!).
Quote from: ted ramasola on October 07, 2013, 09:55:38 PM
oct 4 build has LV overlay issues, the 2 rows of info on the bottom is overlapping each other and alternates which one is over the other with every refresh. The one color (white) is fine with me. lesser visual clutter.
Not got this problem either, format the card and reinstall ML?
ok, I got it.
Screen Layout:
If set to bottom Under 16:9 is does the overlapping info.
That was the setting I've always used. I chose a different one now, bottom under 3:2 and its now ok.
1880 X 1016 is now continuous! :) Great. Sadly my card isn't stable above 74,5, but good job!
Quote from: ted ramasola on October 08, 2013, 04:13:05 AM
ok, I got it.
Screen Layout:
If set to bottom Under 16:9 is does the overlapping info.
That was the setting I've always used. I chose a different one now, bottom under 3:2 and its now ok.
I did not install the font folder - thats what messed my display up. Now its beautiful :)
Quote from: matthieu on October 08, 2013, 09:31:01 PM
I did not install the font folder - thats what messed my display up. Now its beautiful :)
bah, i knew i was out of the loop a bit because i kept getting a "fonts missing" message.
where do i get this font folder?
Quote from: vikado on October 08, 2013, 09:39:07 PM
bah, i knew i was out of the loop a bit because i kept getting a "fonts missing" message.
where do i get this font folder?
Go to: https://bitbucket.org/a_d_/magic-lantern/downloads
Download the latest build: e.g.: f620a8f2b27d.zip
In the ML folder is a folder called "fonts"
awesome thanks! ;D
Hi guys I have recently installed ML and have been shooting 1728 × 736 on my mkii, love it so far but whilst testing there was one shot that I left rolling for a few minutes and the Raw2dng won't read it, it says "image not found". Any ideas on why this has happened?
Is the file extension a .rar? If so, it's a spanning file and you need to throw it into raw2cdng with the original file it's linking to.
Quote from: robert.roth001 on October 08, 2013, 11:57:35 PM
Is the file extension a .rar? If so, it's a spanning file and you need to throw it into raw2cdng with the original file it's linking to.
Had no idea about this, thanks for the quick reply.
Quote from: Jack A on October 09, 2013, 12:09:14 AM
Had no idea about this, thanks for the quick reply.
No problem, there's a ton of stuff to know to use ML raw. That was one of the things I was unsure about when I first started too.
Just curious to see what speeds people are getting with their 5D2 while recording raw. The max I seem to get is around 77MB/S though it seems to hover around 75/76 more consistently. This is on a 1000x 64gb komputerbay.
Was just playing around with crop mode and I noticed that in that mode I can shoot continuous with a write speed around 78-79 MB/s. Anyone else experienced this? I wonder why recording rates are higher in crop mode.
Quote from: gtsofilms on October 09, 2013, 07:02:16 AM
Was just playing around with crop mode and I noticed that in that mode I can shoot continuous with a write speed around 78-79 MB/s. Anyone else experienced this? I wonder why recording rates are higher in crop mode.
Crop mode has been a touch faster for a while, when I was still shooting with slower cards I used to get continous in crop mode while in full frame it would max out at 400 - 800 frames in the same res.
Yep that sounds about right, a "good" 64gb Komputerbay 1000x card is hovering around 77mb in normal mode and around 80mb in crop mode.
This may seem stupid, but I was hoping someone could help.
So I've done a lot of reading, BUT, I'm not entirely sure how to start the recording process!
I turn on my camera, hit the liveview button, then hit the center wheel button (the camera then seems to start recording h.264), I then hit the centre button again to start the raw recording.
I think I'm doing something wrong, because it seems to keep recording h264 at the same time?!
Ignore that... Fiddled with my liveview settings and it works!
does anyone have problems with overheating? with latest build... today i shoot an interview(h264) and at temperature.. shows 52 in a orange square
Is there any way to get the white rectangle to remain on screen during raw recording like in previous builds? Would be quite useful to get accurate framing (although at the moment I'm using the cinescope cropmark since I'm recording in 2.35:1 aspect ratio).
overheating problem
(http://i41.tinypic.com/2ihrmdw.jpg)
Not to worry, ;)
My 5d2 Temp runs anywhere from 58 to 63 degrees C when recording Raw.
At 1872x1012 23.976p
Cools down to about 49 to 53 degrees C on Standby.
Just like any CPU, there have a thermal threshold of, i think 70 degrees C
and will shut down when it to hot. But as long as you don't go over 68 degrees C
there should be no problem.
I just finish a interview with a dentists this afternoon & he could not remember his lines,
so i had my camera running for about 1 hour recording Take after take and never got over 63 degrees C
to a total of 50 GB in data.
:)
Quote from: CerteZ on October 10, 2013, 12:48:07 AM
overheating problem
it looks like a hot pixel problem,
which ML built are you using, A.D. or Alex ?
Some 5d2 have problem with hot pixel with A.D. Builts.
i have no problems but my camera only has 12,000 activation.
Try doing a manual senses cleaning in the Canon menu.
and again temp. is no problem unless you go over 70 degrees C
Quote from: reddeercity on October 10, 2013, 01:52:21 AM
it looks like a hot pixel problem,
Might be focus peaking turned on
Quote from: Malcolm Debono on October 10, 2013, 07:14:32 AM
Might be focus peaking turned on
Yes i think you are right, i didn't think of that :D
Quote from: Malcolm Debono on October 10, 2013, 12:24:21 AM
Is there any way to get the white rectangle to remain on screen during raw recording like in previous builds? Would be quite useful to get accurate framing (although at the moment I'm using the cinescope cropmark since I'm recording in 2.35:1 aspect ratio).
Recording frame> White rect
Interface> Feature+
@CerteZ
Card warm-up?
Hey guys, new to this, but reading all your posts has been super helpful.
I'm using a Transcend 32gb 1000x in the mkii, using f620a8f2b27d OCT.4 . Here's what I've been getting (Small hacks on, 1gb warm up, S-jpeg):
- 2:1 1880x940 continuous w/ global draw off.
- 2.20:1 1880x854 continuous w/ global draw on.
Seems like it tops out at about 72mb/s. EDIT: Most i've seen is 74.3mb/s using 1.85:1
Just got the card today; going to shoot some more tests tomorrow.
Hi everybody,
Sorry for my bad english but i m french.
Well i has a question about these versions of magic lantern for raw video.
I want to know if the risks to brick the camera are same than the nightly versions of ml ?
Thanks you
Quote from: GutterPump on October 11, 2013, 07:44:53 PM
Hi everybody,
Sorry for my bad english but i m french.
Well i has a question about these versions of magic lantern for raw video.
I want to know if the risks to brick the camera are same than the nightly versions of ml ?
Thanks you
@Everybody
Can we get clear on this?
I don't believe any build can break your camera (except maybe for double ISO stuff). I do believe the camera may cease functioning due to some error which is normally corrected by dropping the battery with the camera still on (this actually happens sometimes with the nightlies :) ), and worst case scenario a clean card would do the trick.
That is, if the camera was "healthy" before the install, and with the appropriate firmware.
Anyone says different? really
@GutterPump
That being said, I tend to feel these builds from the 5DMKII raw topic tend to be more stable because we have a.d. "watching over us" and doing some extra testing while maximizing compatibility with the MkII before they come out. If something does go wrong, ML forum tends to be the best place to look for a solution. Take look at the Troubleshooting threads and i think you will come up with the same conclusion.
Anyway the disclaimer still stands USE IT AT YOUR OWN RISKS, to which I would add, FOLLOW THE INSTRUCTIONS CAREFULLY.
@devs & super dooper old-timer members
Although I'm new at the forum i've read a lot of it for a while now, so when I see a question i think i can answer I do (at the risk of sounding smug or pretentious). Just trying to help! If this is somehow a disservice please let me know.
Cheers All
PS: Shouldn't we open a tread to try and translate some of the documentation tho other languages? We could set up a peer review sistem and everything. I'd be Happy to help with Portugese.
Yes ML can brick your camera. If nothing else it requires a firmware update, that alone can brick your camera. I believe the risks are small and that is why I use it.
There is no different between the nightly builds and a.d's in terms of safety. All the dev's are careful and the only difference with a.d's build is that he adds some of his own custom features to it. It is based entirely off the nightly builds and to my knowledge he doesn't to any safety checks to the base code before posting his compiled version.
The only thing that could make it a little safer is that he has to manually compile his builds so they always fall a little behind the nightly time wise, he also only seems to compile when there is a significant change to the code so bugs my be skipped over or caught by others before he compile his build.
"# faster algorithm for detect black level vs less accurate"
i have not tried the new built yet but
Dose this mean better/more accurate black levels?
or is it not a noticeable differences, just for system stability ? :)
Shot a test today. Everything went fairly well. For my first time, it was awesome editing RAW video like I edit stills. I'll have to get the aspect ratio correct out of premiere next time..
https://vimeo.com/76742955 (https://vimeo.com/76742955) I don't have the free vimeo bandwidth to upload the pro res.
Notes: Lots of artifacts on asphalt/pavement. Transcend 1000x 32gb tops out just over 74mb/s, not enough for continuous 1.85:1 1880x1016.
@a.d.
When cr2hdr is re made possible to choose an output location? bought an ssd and would like to save as much write too it as possible as its a software launcher mainly, if not all good man as ill place the app onto my 2nd optibay hdd dude :)
Update:
Forgot it out puts to where the images are located, been use to always placing the folder on desktop... my bad. :P
My latest work preview using 5DmkII entirely on RAW 1880x800p25,
Glidecam shots of Cheerleaders ;)
or
https://vimeo.com/76044569
Quote from: a.d. on October 10, 2013, 11:58:04 AM
Recording frame> White rect
Interface> Feature+
@CerteZ
Card warm-up?
no card warm-up ..and when the screen shot was taken ..i just turned on the camera ..for screen shot and waited to see what happens..and got this 56 only in live view
Anyone else getting this on 11th build CF Benchmark?
(http://i41.tinypic.com/zl9hfs.jpg)
Got 2 malloc errors..
yooo! Need help! ACR interprets my 5DII footage as Canikon. Normally this wouldn't be a problem, but as I've started using Vision Log (http://www.magiclantern.fm/forum/index.php?topic=8816.0) I need ACR to interpret the footage correctly for Vision Log to work properly.
I am using RAWanizer. I have the idea that his might be an issue with raw2dng and sought to replace the raw2dng inside RAWanizer with the newest version available from a.d., but the RAWanizer version is 276 kb and the one from a.d. is 132 kb... So there must be something more to the raw2dng in RAWanizer than just the normal raw2dng.
Am I right to assume that this has something to do with raw2dng or is it something inside 5D MK II?
no problem with the 5d2, i remember back in june or july this was a problem.
But it had to do with the early version of raw2dng.
Have you tried just to use raw2dng without RAWanizer or raw2cdng ?
raw2cdng has a option to output 10bit Log if you didn't know ;)
Quote from: reddeercity on October 16, 2013, 03:16:15 AM
no problem with the 5d2, i remember back in june or july this was a problem.
But it had to do with the early version of raw2dng.
Have you tried just to use raw2dng without RAWanizer or raw2cdng ?
raw2cdng has a option to output 10bit Log if you didn't know ;)
What's the difference between.. say.. 16 bit linear and 10bit log? Trying to find an answer online but it's rather confusing.. so.. simplified for our purposes? :)
Quote from: Doyle4 on October 15, 2013, 05:43:31 PM
Anyone else getting this on 11th build CF Benchmark?
(http://i41.tinypic.com/zl9hfs.jpg)
Got 2 malloc errors..
Yeah I got that too with the 11th build
Quote from: robert.roth001 on October 16, 2013, 04:54:40 AM
What's the difference between.. say.. 16 bit linear and 10bit log? Trying to find an answer online but it's rather confusing.. so.. simplified for our purposes? :)
I will do my best to explain this.
Linear color space space is what it means, If 0= to Black & 256= Prue White with 12 Stop of Latitude
if you draw a line though a graph the line would be straight .
With the same graph in Log or logarithmic color space with the same stops the line would be Curve not straight .
Why ? because when the pixels are remapped ,there are push-down on the whites & pushing-up on the blacks.
and increasing the Mid-Range Latitude.Then became flat and low contrasted .
So you would express linear as Gamma 1 and Log would be Gamma 2.2
So let say Pixel Black from 0-16 well be remapped to black 16-25 And pixel white 256-235 well be remapped to 235-220
and 220 to 25 are more or less remapped across to each other.
I hope a didn't make this more confusing to you, here are some links that talk about
Log and linear,that sure clear thing up.
http://www.cirquedigital.com/howto/color_tutorial.html#Log+and+Linear+Color+Space
http://www.qvolabs.com/Digital_Images_ColorSpace_Log_vs_Linear.html
If you are looking for a log look try this:
Take a a jpeg photo with Technicolor CineStyle Picture Style,
the picture style will be burned in the image, and record some raw video
extract the one dng import both in to Photoshop and adjust the dng to match the log Jpeg image
and save is as a (.xmp) now you have a flat log like image to work with.
;)
Quote from: robert.roth001 on October 16, 2013, 04:54:40 AM
What's the difference between.. say.. 16 bit linear and 10bit log? Trying to find an answer online but it's rather confusing.. so.. simplified for our purposes? :)
10 bit log stores values using a logarithmic curve rather than linear like 16 bit does. The effect of this is that 10 bit log can store the same amount of dynamic range with nearly the same freedom for color correction with only 10 bits rather than 16 and with about %63 of the file size. Also the exposed film naturally has a logarithmic density relative to light intensity so film is essentially log encoded as well therefor working in log is similar to working with scanned film.
Okay that all makes sense. So if I take my .raw files and use cdng to make them 16-bit linear and load them into resolve and use BMD Film color space, do I need to worry about any of this? What if I do the same thing but with 10-bit log then? From the sounds of it 10-bit log will perform the same as 16-bit linear. So is there any reason to put my footage into 16-bit linear instead of 10-bit log? Sounds like 10-bit log is the way to go.
The log footage will appear de-saturated and will need grading with a curve or LUT to restore the contrast contained in the original 16 bit file... that and the different file size will be the main difference.
What africashot said, main difference is file size and personal preference. You will get better performance with 10 bit log. I am currently bringing in 16 bit dng's and converting them to 10 bit log dpx files. Performance is much better since the dpx is debayered and dpx files seem to be the fastest image file format to work with that I have used so far.
when connecting to an external monitor via hdmi.
sometimes the white rectangle recording area is only showing one white line instead of showing 4 lines to make a rectangle and that one white line is way off where its supposed to be.
anyway to fix this?
thank you in advance.
v2.3.next.2012OCT04.5D2212
also had Recording frame set to White rect. and Global draw at "always on"
(http://i.imgur.com/DoBlGQS.jpg)
(http://i.imgur.com/zpw9Jyo.jpg?1?4459)
Hello all :)
Just doing some testing on the Oct4th built, in Crop mode to check out if the Framing was actuate
With A.D. built. No problems
ISO 100 with ND Fader about 2 stops down
Edited the 16bit Cdng's Native in Final Cut Pro X 2k project 2048x1024.
I could only get between 1000 & 1200 frames pershot on lexar 64GB 1000x card
But good enough small project like this one.
Lens Canon EF 24-70mm f2.8L in 3x crop mode = 72-210mm
here is the results
:)
Small bug I'm experiencing with Oct12 build:
After pressing the AF-ON button to focus, the raw video crop (white rectangle and black bars) disappear and the full image appears. Going into ML menu and back out seems to redraw them. Also applies for cropmarks. Still need to check latest build.
Quote from: vikado on October 17, 2013, 03:33:42 AM
when connecting to an external monitor via hdmi.
sometimes the white rectangle recording area is only showing one white line instead of showing 4 lines to make a rectangle and that one white line is way off where its supposed to be.
anyway to fix this?
thank you in advance.
v2.3.next.2012OCT04.5D2212
also had Recording frame set to White rect. and Global draw at "always on"
[img]http://i.imgur.com/DoBlGQS.jpg/img]
[img]http://i.imgur.com/zpw9Jyo.jpg?1?4459/img]
managed a workaround for the white framing problem.
if you turn on your camera first and then you connect your monitor via hdmi port,
the framing will be correct, but if you connect your hdmi while your camera is off and then you turn on your camera,
you'll get the white framing issues.
i kept repeating it and it kept on repeating the same result.
go fig
hi, I'm having a problem interpreting the file. dng using DaVinci Resolve Lite. I can see some pink pixels, while using the aftereffects file is interpreted correctly, even if you lose the picture style. I would understand if it happens to other people, or if possibly someone has found a way to interpret the picture style in aftereffects without having to manually change from camera raw, because you only see the first frame ...
(p.s. I don't understand how to post the images....)
Quote from: [email protected] on October 22, 2013, 02:21:00 PM
hi, I'm having a problem interpreting the file. dng using DaVinci Resolve Lite. I can see some pink pixels, while using the aftereffects file is interpreted correctly, even if you lose the picture style. I would understand if it happens to other people, or if possibly someone has found a way to interpret the picture style in aftereffects without having to manually change from camera raw, because you only see the first frame ...
(p.s. I don't understand how to post the images....)
what version of da vinci lite are you using?
9.1.6 lite
http://sta.sh/0p7ui7nj1fs
http://sta.sh/01jjz7kbmn5a
ok thanks!
Quote from: vikado on October 17, 2013, 03:33:42 AM
when connecting to an external monitor via hdmi.
sometimes the white rectangle recording area is only showing one white line instead of showing 4 lines to make a rectangle and that one white line is way off where its supposed to be.
anyway to fix this?
Hi Vikado, have you try to select ML grayscale from the RAW-->Preview menu? This always works with my EVF and external monitor! When you have to monitor directly from the DSLR screen you have to choose Canon.
Quote from: avasarin on October 23, 2013, 08:11:51 AM
Hi Vikado, have you try to select ML grayscale from the RAW-->Preview menu? This always works with my EVF and external monitor! When you have to monitor directly from the DSLR screen you have to choose Canon.
hey thanks!
i needed a monitor during a shoot for the director and for really tight shots as well.
the white framing kept on getting wonky so i decided to tape up the monitor screen where the white frames are supposed to be.
it worked, but its good to know there's an ML option to make it work properly.
also, i've noticed the hdmi connection kept on getting disconnected during the shoot,
so i think im going to invest in one of those HDMI lock ports to insure connection never gets dropped with the slightest bump.
EDIT:
btw, we shot a comedy short last week with my 5dm2 with the oct.4 build.
it was only a one day shoot, which lasted about 15hours.
used about 400GB of raw footages and going the ACR route instead of Resolve.
i spent the last few days processing the raw files and syncing them up with the audio files.
and just by scrubbing through the takes, besides the dead pixels, they're are looking great.
no major errors so far.
i should have a final cut in a about 2 weeks or so to show.
Looking forward to it, Vikado :)
I love seeing this camera in action!
I shot some Chroma Key scenes with my 5d2 for a short, its in post now and I can't wait to see the outcome. The VFX guy was very pleased with the 14 bit quality of the chromas.
Quote from: Kharak on October 23, 2013, 01:47:26 PM
Looking forward to it, Vikado :)
I love seeing this camera in action!
I shot some Chroma Key scenes with my 5d2 for a short, its in post now and I can't wait to see the outcome. The VFX guy was very pleased with the 14 bit quality of the chromas.
oh that's real good to hear.
prores or dnxhd?
and after just a few takes, my 5d was getting real real hot!
Quote from: vikado on October 23, 2013, 09:29:23 PM
oh that's real good to hear.
prores or dnxhd?
and after just a few takes, my 5d was getting real real hot!
Yeah, mine got really hot too, but didn't smell of burned wiring though :)
Exported to dnxhd, with adjustments done in ACR beforehand.
Quote from: vikado on October 23, 2013, 11:52:56 AM
hey thanks!
i needed a monitor during a shoot for the director and for really tight shots as well.
the white framing kept on getting wonky so i decided to tape up the monitor screen where the white frames are supposed to be.
it worked, but its good to know there's an ML option to make it work properly.
also, i've noticed the hdmi connection kept on getting disconnected during the shoot,
so i think im going to invest in one of those HDMI lock ports to insure connection never gets dropped with the slightest bump.
With my Zacuto EVF I enable the 2.35 frameline directly from the EVF. For the external 7" monitor I just taped up it.
For the HDMI lock, I use the SmallHD one, it works properly.
For the dead pixels, have you try to set the Adobe Camera Raw to 2003, instead of 2010? You find it in one of the last menu pages of CR. I noticed that swapping it will eliminate all the dead/white pixels(if you mean this issue). Don't know why... Let me know!
where i can find 5d2 alex raw builds/forum topic?
@vikado
Are you sure You use my release? 'cause I switch off the cropmark for hdmi mode ???
http://builds.magiclantern.fm/#/
Quote from: a.d. on October 25, 2013, 12:01:52 AM
@vikado
Are you sure You use my release? 'cause I switch off the cropmark for hdmi mode ???
http://builds.magiclantern.fm/#/
i believe so a.d.
this is what it says on the boot screen.
"Magic Lantern version: v2.3.NEXT.2013OCT04.5D2212
Mercurial changeset :f620a8f2b27d+ (unified) tip
Built on 2013-10-04 15:20:32 UTC by ad@MagicLantern."
i got the build from here.
https://bitbucket.org/a_d_/magic-lantern/downloads
Hello all, Just test the new A.D. built with the new format "mlv" raw module for 5d2.
Will it has problems, it kept crashing the Lv, reboot fix it, & one battery pull.
There is a reduction in performance, i could not do any better than About 750 frames @1856x1004 lexar 1000x 64GB card
I know there is a options for buffer rate etc... but Not knowing what there are support to be set at for max writing speed.
So its all guess work for that, unless some one can enlighten me on the buffer system.
For some reason i had Frame skipping off but it would show up in the Lv
"frames skipped"then it would either crash Lv & or stop recording
and also did loses the raw record module on a crash, re-install the module from PC, Ok then.
and i see with A.D. built we lost "1880" :(
Gobal Draw is not the same from the non mlv, it had a Black box around the crop marks which i do not like, and the crop mark
was off to the left side of the Lv screen for 1872 frame size.
I do notice my 5d2 heating up a lot faster then before to about 62-63 degrees C
Just playing around with settings, normally i would have to work it hard for at lest 15 minute before i see temp come up.
Then i tried to convert some of the mlv raw files & mlv2dng would crash on some of the file
and have a message about bad header or something like that.
On the plus side,I was able to get some files out & read the metadata.
For the most part it did have the right information about the lens, f stop, exposure which is great :)
So i will keep to the Non mlv format for right now until more Bugs can be Worked out.
But I do like the format i see great possibilities with it just needs to be more stable.
Edit: I also just tried the A.D. Non mlv raw record Module, and its working Great, no problems.
Lexar 1000x 64GB card
Record 1872x1012 23.976p 76.0MB/s Continuous
& 1880x1016 23.976p 76.0MB/s mostly Continuous :)
Quote from: avasarin on October 24, 2013, 08:56:49 AM
With my Zacuto EVF I enable the 2.35 frameline directly from the EVF. For the external 7" monitor I just taped up it.
For the HDMI lock, I use the SmallHD one, it works properly.
For the dead pixels, have you try to set the Adobe Camera Raw to 2003, instead of 2010? You find it in one of the last menu pages of CR. I noticed that swapping it will eliminate all the dead/white pixels(if you mean this issue). Don't know why... Let me know!
just imported the dng sequences to ACR and switched to 2003 and i can confirm the hot/dead pixels are gone!
i still get white pixels but only in black areas.
thanks bro!
i did the manually clean the sensor trick and i dont have any dead pixel issues anymore as well.
How do mac user's convert MLV please?
Quote from: Doyle4 on October 25, 2013, 11:52:45 AM
How do mac user's convert MLV please?
+1 and if someone could recapitulate de benefits over normal raw it would be great!
Shot with Magic Lantern RAW
I will not be using MLV for the performance reasons.
Quote from: dossisman on October 25, 2013, 08:22:01 PM
Shot with Magic Lantern RAW
Boring... Raw doesn't make a video Great... You can make a great video using Raw, and some other important stuff. I would filled that club with people ... Or used closer shots so the place doesn't look that empty or "fake". If only 1 location is avaible try changing angles .. Not always the same.
Quote from: djzigoh on October 25, 2013, 09:47:24 PM
Boring... Raw doesn't make a video Great... You can make a great video using Raw, and some other important stuff. I would filled that club with people ... Or used closer shots so the place doesn't look that empty or "fake". If only 1 location is avaible try changing angles .. Not always the same.
I never said the video
was great because it was shot on RAW.
I shared it because it was shot on RAW.
Thanks for watching, and for the notes. The customer was pretty pleased with the end product, but there's always room for improvement.
Please don't take me the wrong way, I was only suggesting. English it's not my primary language so I could been misunderstood .
Quote from: xNiNELiVES on October 25, 2013, 09:12:30 PM
I will not be using MLV for the performance reasons.
I think MLV is really meant for the 5d3, being it has more processing power & faster interface.
What's killing the 5D2 with MLV, is all the overlays & Gobal Draw stuff.
When i kill gobal draw & overlays it dose pickup speed but not like the the original version.
The max. write speed i could see was about 70.MB/s, normally i see about 76.0MB/s
Its nice to have all the metadata that's being added to the raw files but
not at the cost of basic Raw recording.
If we could strip away all the gobal draw stuff i think MLV may work on the 5D2.
All we really need is basic audio & metadata , from may point of view :)
Where can we find the latest info on MLV? Any compiled, updated list of features? I remember there being a thread for it but I can't seem to find anything now...
Quote from: robert.roth001 on October 26, 2013, 10:25:21 AM
Where can we find the latest info on MLV? Any compiled, updated list of features? I remember there being a thread for it but I can't seem to find anything now...
Look at the very first post in this thread ...
I have a request for raw2dng.
a.d., can you hardcode 5D MK II profile in to the latest version of raw2dng?
Vision Log requires correct Camera Profile to work and I only found an old version of raw2dng which has 5dmkii hardcoded, but I'm worried that it might be worse quality in that old version than the newest. Something about black levels, I believe.
This mode will be loaded at next reboot.
Please, help!!!
Quote from: Pulpart on October 28, 2013, 01:15:48 PM
This mode will be loaded at next reboot.
Please, help!!!
Can you be a bit more specific?
Quote from: Pulpart on October 28, 2013, 01:15:48 PM
This mode will be loaded at next reboot.
Please, help!!!
try reboot :o
sorry how many bits is a raw file 5d2? 8, 10 or 14? I'm confused on how I can control this parameter.
Quote from: poty on October 28, 2013, 04:53:15 PM
sorry how many bits is a raw file 5d2? 8, 10 or 14? I'm confused on how I can control this parameter.
14, you can´t control this parameter. (you can shoot in h264 - 8bit)
Anyone got MLV running smoothly?
Just out of curiousity, while shooting raw at continuous 23.976 fps, can I use focus peaking on the LCD while recording? I am considering buying a 5D MkII and this would be a dealmaker/breaker for me.
Quote from: raichu93 on October 28, 2013, 09:46:49 PM
Just out of curiousity, while shooting raw at continuous 23.976 fps, can I use focus peaking on the LCD while recording? I am considering buying a 5D MkII and this would be a dealmaker/breaker for me.
there are 2 flavors of peaking on the mkII. The older one uses color to indicate areas of focus. There is also a newer addition called Digic peaking which renders areas in focus as slightly sharper. The latter is faster and less distracting than the former and I find it to be more accurate than the older color overlay method.
Quote from: ted ramasola on October 28, 2013, 10:09:16 PM
there are 2 flavors of peaking on the mkII. The older one uses color to indicate areas of focus. There is also a newer addition called Digic peaking which renders areas in focus as slightly sharper. The latter is faster and less distracting than the former and I find it to be more accurate than the older color overlay method.
I see, that sounds great. Are there any samples online of the digic peaking in action? And just to confirm, this does work flawlessly while recording RAW, correct? Thank you for the information, i appreciate it a lot, and sorry for the pestering with questions, I just want to make sure before I commit to buying it...
Keep in mind MLV is still experimental, but the future sounds promising. Previously MLV didn't run on 5D2 well. The LV is freezed and you couldn't even stop the record. you need to pull out the battery and so on... Now it works just fine. Performance wise it's still bad. Now I don't touch the code for the bug report.
@vikado
Could you test the hdmi crop mark fix?
hdmi_raw_rec.zip (https://dl.dropboxusercontent.com/u/13314708/hdmi_raw_rec.zip)
@Kharak
Latest raw2dng for 5D2
It's a little bit slower caused by the new median algorithm.
5d2_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5d2_raw2dng.zip)
Quote from: a.d. on October 28, 2013, 10:58:22 PM
Latest raw2dng for 5D2
It's a little bit slower caused by the new median algorithm.
5d2_raw2dng.zip (https://dl.dropboxusercontent.com/u/13314708/5d2_raw2dng.zip)
Median for 5D2? why?
Quote from: a.d. on October 28, 2013, 10:58:22 PM
@vikado
Could you test the hdmi crop mark fix?
hdmi_raw_rec.zip (https://dl.dropboxusercontent.com/u/13314708/hdmi_raw_rec.zip)
sure thing, chief.
I've just simplified thing: It took some basic ideas from median cr2hdr with code improvement: AHD, chroma smothing and 5x5 etc...
Okay, but last time I've checked there were no pink dots on the 5D2.
This will reduce image quality, so it's best to have it off by default. If you want to try it from some very noisy or aliased shots, it should be an option, not the default.
Colored playback in-camera for RAW video!! Thank you!
Quote from: ted ramasola on October 29, 2013, 03:06:46 AM
Colored playback in-camera for RAW video!! Thank you!
for mlv or raw?
Cause I can't playback mlv and raw is still black and white for me.
@a.d.
Thanks man!
It works and with RAWanizer.
Quote from: Kharak on October 29, 2013, 07:01:15 AM
for mlv or raw?
Cause I can't playback mlv and raw is still black and white for me.
I believe its both since it uses the mlv_play module. You have to load mlv_play module. It plays back even .raw files. I don't use mlv so I haven't tested it with mlv.
Default is colored playback, its slow, you can speed it up by pressing SET button, its goes low res grayscale but faster playback.
Note: its not yet added by a.d. in the first post. Its still in the nightly builds. Oct 28 NB.
Quote from: ted ramasola on October 29, 2013, 07:41:19 AM
I believe its both since it uses the mlv_play module. You have to load mlv_play module. It plays back even .raw files. I don't use mlv so I haven't tested it with mlv.
Default is colored playback, its slow, you can speed it up by pressing SET button, its goes low res grayscale but faster playback.
Note: its not yet added by a.d. in the first post. Its still in the nightly builds. Oct 28 NB.
Could you give the link ? i did not find it...
Francis
Its in the Nightly Builds in the downloads page. Link on top right of this page.
Quote from: a.d. on October 28, 2013, 10:58:22 PM
@vikado
Could you test the hdmi crop mark fix?
hdmi_raw_rec.zip (https://dl.dropboxusercontent.com/u/13314708/hdmi_raw_rec.zip)
using the same oct.4 build with the same settings as the shoot.
the top image is what happens when i plug in the hdmi to the camera.
a couple of seconds later, its the second image below,
and a couple seconds after its the bottom image.
the crop marks are correct after a few seconds but not initially.
screen layout is set to 4:3display, auto
force hdmi-vga: on
global draw off
resolution: 1880x800
the results are the same whether i connect the hdmi cable to camera and the camera being on or off.
during the shoot, i only got correct crop marks if i connected the hdmi cable before i turn on the camera.
so it looks like it works but it needs a few seconds to correct itself.
thank you!
(http://i.imgur.com/sXsiAEr.jpg)
Hey all,
So I just got a 5D mk 2 and installed ML on it... The results have been super disappointing. I pull the raw files from the camera, use cinema2dng as required, and put the DNGs into After Effects. However they're not sharp at all. It looks like the H.264 quality, and even my Panasonic GH2 unhacked is sharper. Basically it looks NOTHING like what I saw in these videos:
https://vimeo.com/66083408
https://vimeo.com/72008856
I got the latest build, tried it, was disappointed, and got the newest nightly build, and got no better results. Would you happen to know what's going on? Thanks!
@raichu93, u've already opened your own thread( http://www.magiclantern.fm/forum/index.php?topic=9099.0) Don't post your question in every other thread now...
Apologies, new around here, won't happen again.
Did some testing at the Winnipeg Zoo, I over baked some footage as the cats moved into much brighter light, I was curious to see how far I could pull the footage back. There are no in camera exposure changes throughout this video shot in 5x mode 1728x689 at 23.976fps with a 24-70mm F2.8 lens. The shutter speed is quite high so I'm way over 1/45 shutter, probably 1/250 at F/2.8
Footage is not usable but I wanted to see how subtle I could make exposure changes in post without it noticeably showing steps down.
(http://i.imgur.com/enwAP8Xh.jpg)
(http://i.imgur.com/WOfkzkjh.jpg)
This is how it looked with no modifications, this is probably pretty close to what the h.264 footage would have come out looking like at those settings.
(http://i.imgur.com/OFrDUXf.jpg)
Did you noticed with last build [af9a60fe144d 2013-10-24] in RAW video (not MLV) 1880px is 1872px + black borders? ???
Quote from: SpcCb on November 01, 2013, 05:07:43 AM
Did you noticed with last build [af9a60fe144d 2013-10-24] in RAW video (not MLV) 1880px is 1872px + black borders? ???
What do you mean by + Black borders.
My DNG's show as 1880 and I see no black border.
Indeed, after go back to the 2013-10-04 build I redone upload of files on the card from scratch and it's fine now.
It's why I asked, I found this strange. Thanks for the confirmation Kharak -.^
Things are changing so~ fast in ML that sometime I loose the thread... ^.^
Hi Dudes!
Anyone knows about this 1000x CF card? http://www.ebay.co.uk/itm/64GB-Compact-Flash-Memory-Card-1000X-Professional-UDMA-7-/181174615381?pt=LH_DefaultDomain_123&hash=item2a2ed93d55 (http://www.ebay.co.uk/itm/64GB-Compact-Flash-Memory-Card-1000X-Professional-UDMA-7-/181174615381?pt=LH_DefaultDomain_123&hash=item2a2ed93d55)
Happy to have helped :)
Quote from: kortefa on November 02, 2013, 04:00:53 AM
Hi Dudes!
Anyone knows about this 1000x CF card? http://www.ebay.co.uk/itm/64GB-Compact-Flash-Memory-Card-1000X-Professional-UDMA-7-/181174615381?pt=LH_DefaultDomain_123&hash=item2a2ed93d55 (http://www.ebay.co.uk/itm/64GB-Compact-Flash-Memory-Card-1000X-Professional-UDMA-7-/181174615381?pt=LH_DefaultDomain_123&hash=item2a2ed93d55)
Looks like the off brand 'Delkin' ones. I wouldn't. But I'd like to know if anybody has experienced them as well.
Hi folks!
I finaly migrated from 550d to 5dm2 and got some questions.
I registered basic preferences to CF1 mode for RAW shooting, but how to change Shutter speed on the fly without entering ML menu?
Different lamps have different frequency and sometimes it's flickering at 1/50th.
With t2i I could change shutter speed by holding down Av+Dial, how to do the same with 5dm2?
Quote from: coolerinc on November 03, 2013, 10:37:38 AM
Hi folks!
I finaly migrated from 550d to 5dm2 and got some questions.
I registered basic preferences to CF1 mode for RAW shooting, but how to change Shutter speed on the fly without entering ML menu?
Different lamps have different frequency and sometimes it's flickering at 1/50th.
With t2i I could change shutter speed by holding down Av+Dial, how to do the same with 5dm2?
If you look at the Shutter activation button (the one that takes a picture), right behind it there is a wheel. Scroll it left and right to adjust Shutter :)
Quote from: coolerinc on November 03, 2013, 10:37:38 AM
Hi folks!
I finaly migrated from 550d to 5dm2 and got some questions.
I registered basic preferences to CF1 mode for RAW shooting, but how to change Shutter speed on the fly without entering ML menu?
Different lamps have different frequency and sometimes it's flickering at 1/50th.
With t2i I could change shutter speed by holding down Av+Dial, how to do the same with 5dm2?
I suggest you read the manual if doing something as simple as changing shutter speed can be confusing ;)
See the wheel right behind the shutter button?
Quote from: Kharak on November 03, 2013, 11:02:20 AM
If you look at the Shutter activation button (the one that takes a picture), right behind it there is a wheel. Scroll it left and right to adjust Shutter :)
Very funny :)
Quote from: PressureFM on November 03, 2013, 03:23:48 PM
I suggest you read the manual if doing something as simple as changing shutter speed can be confusing ;)
See the wheel right behind the shutter button?
Yeap, I see the Dial wheel ^_^
But, when I'm scrolling it the Shutter Speed jumps to it's default number. For example I change Shutter Speed (SS) inside ML menu to 1/60 and in LiveView I cannot change it to any other because it respawns :) That's weird
Using Manual Lens Helios44-2 (ML version 31.10.13)
Look in the delta menu (modified settings). Should be obvious.
Quote from: a1ex on November 03, 2013, 07:40:39 PM
Look in the delta menu (modified settings). Should be obvious.
Yeah, Shutter Lock inside Movie Tweaks was ON. Thanks a lot ^_^
Yet another one Raw tests
Quote from: a.d. on October 28, 2013, 11:40:39 PM
I've just simplified thing: It took some basic ideas from median cr2hdr with code improvement: AHD, chroma smothing and 5x5 etc...
I've done some testing with the raw2dng you gave me.
I converted same file with your new raw2dng that has Median algorithm and with the old raw2dng (says Last modified July). I can not see any difference at all. Pixels are exactly the same on all. Both in shadows, highlights, aliasing, moire, noise you name it. There is no difference in pixels. Colours and brightness are the same for all pixels.
The only difference I see is the size of the dng.
Median: 2,71 MB (2.843.648 bytes)
Older: 2,71 MB (2.848.256 bytes)
What is the median algorithm supposed to do?
This is something I am not sure if it has to do with the build I am using (11.10) or is simply based on my incompetence but audio is disabled and I can't find a way to enable it... upon hitting record on regular canon video there will be a message of 'audio disabled', ml audio options are grayed out while audio is enabled in the canon menu... any help will be highly appreciated!
Quote from: Kharak on November 04, 2013, 01:00:02 PM
(...)
What is the median algorithm supposed to do?
It's to reduce hot pixels, if I'm not wrong.
Saw it in previous pages here.
IMHO it's not suitable if you don't have hot pixels problem.
Quote from: Africashot on November 05, 2013, 07:23:50 AM
This is something I am not sure if it has to do with the build I am using (11.10) or is simply based on my incompetence but audio is disabled and I can't find a way to enable it... upon hitting record on regular canon video there will be a message of 'audio disabled', ml audio options are grayed out while audio is enabled in the canon menu... any help will be highly appreciated!
I did not see that when I tested this build (I switched quickly to the 24-10 build because of black levels accuracy).
Do you checked if you are not in FPS override mode? Could be the cause (I see this message in this case).
Quote from: SpcCb on November 05, 2013, 01:25:33 PM
It's to reduce hot pixels, if I'm not wrong.
Saw it in previous pages here.
IMHO it's not suitable if you don't have hot pixels problem.
Yes, I read about the hot pixels too. Alex was responding to a.d. on that matter.
But as I can not see any difference at all between the two raw2dng's output. I'm wondering if the Median algorithm and the other things a.d. changed, even work. And even so if these features do work, every pixel is the same. Colour, placement, brightness. no difference.
There obviously must be some difference between the dng's, as the size of the files are not the same, though it is minimal, only few bytes. I would very much like to know what it is :)
I'll do another test, with a RAW file that I know had a few burned pixels in it. See if there is a difference.
Quote from: dariSSight on September 22, 2013, 12:44:05 PM
I've been wondering how to use or what to use the dual iso function for, are you using it to record RAW dual iso video or Stills Photography? If you don't mind can you explain how you're using it with the CR2HDR.app.
Sorry for such a late reply, i didnt spot this.
I use it for photography only as thats all the mkii can do, on my 600D iv used it for video but not yet come a need to use it.
I normally use 100/1600 or 100/800, all depends. dual iso is good if there is strong light and dark areas or vice versa, great when urbexing! to use cr2hdr just drag the dual iso cr2 :)
Quote from: SpcCb on November 05, 2013, 01:25:33 PM
It's to reduce hot pixels, if I'm not wrong.
Saw it in previous pages here.
IMHO it's not suitable if you don't have hot pixels problem.
mmm, I should try this than.
Quote from: SpcCb on November 05, 2013, 01:25:33 PM
(I switched quickly to the 24-10 build because of black levels accuracy).
What is this black levels accuracy?
Quote from: togg on November 06, 2013, 02:14:14 PM
(...)
What is this black levels accuracy?
Seems there's a black level accuracy issue in previous builds (plus 2013-10-24 build add MLV capability etc.).
Sometimes it's hard to follow because things are moving fast and I don't find any exhaustive change log for the a.d. builds (like we can find for jenkins builds).
However, I don't really see why RAW||Dual ISO black level is still set at 1792 ADU... Maybe there's a reason (5D3' black level is 2048 ADU ?), but it's far than the 'original' black level of 5D2' RAWs (1024 ADU). Plus, white level is set at 15000 ADU, and the original is 15600 ADU with the 5D2.
I think we loose informations & dynamic in those conditions, but I repeat, maybe there's a reason.
First post (so don't flame me), but I've been shooting Raw with various builds since July with few problems except one. I know it was supposedly fixed but I haven't gotten any of the the builds I've tried to do FPS override with anything less than 1.5 FPS. I get the repeated frame issue that was supposedly dealt with awhile back. I know "FPS override" may be a seldom used feature for many so I wanted to see if it was just me or if others can confirm that this is still not functioning.
Again, FPS still broke or just buggy with certain setups?
Anybody?
Thanks
Edit: Apparently this was my second post. Maybe it is just me ;)
Quote from: Steadicam on November 08, 2013, 08:55:18 PM
(...) I know it was supposedly fixed but I haven't gotten any of the the builds I've tried to do FPS override with anything less than 1.5 FPS. I get the repeated frame issue that was supposedly dealt with awhile back. I know "FPS override" may be a seldom used feature for many so I wanted to see if it was just me or if others can confirm that this is still not functioning.
Again, FPS still broke or just buggy with certain setups?
(...)
For me this issue was never fixed.
Still get framing 1-2-1-3-1-4-1-n... with low FPS override.
Have you seen if you get the same weird thing with the a1ex builds?Well, no. Just tried it and it's the same thing. :(
Had this problem once too. Imported in AfterEffect with the repeat frame 1. I Had this when i created a comp from the .mov and then ajust the fps of the comp.
Solved by creating an empty comp by settings the correct fps and THEN drop the .mov in the comp.
Hope this will help.
Quote from: piloui on November 09, 2013, 06:03:26 PM
Had this problem once too. Imported in AfterEffect with the repeat frame 1. I Had this when i created a comp from the .mov and then ajust the fps of the comp.
Solved by creating an empty comp by settings the correct fps and THEN drop the .mov in the comp.
Hope this will help.
This problem is only in RAW video mode: In regular H264 mode (->.mov file) it works fine with last builds; I'v checked it yesterday.
So you should not have this problem since a long time.
The weird thing is... I'm sure I used a build where low FPS override in RAW video was working fine. It was this last summer, with a1ex' builds.
I'm currently checking all builds to find when it was back (take a looong time). Apparently, it's very old, good builds cannot be find anymore in the download page (or I don't see where) and it was before the magical Dual ISO arrived (hard to make a choice!). Maybe during the autoexec unification (?).
Quote from: SpcCb on November 10, 2013, 12:00:06 AM
This problem is only in RAW video mode: In regular H264 mode (->.mov file) it works fine with last builds; I'v checked it yesterday.
So you should not have this problem since a long time.
The weird thing is... I'm sure I used a build where low FPS override in RAW video was working fine. It was this last summer, with a1ex' builds.
I'm currently checking all builds to find when it was back (take a looong time). Apparently, it's very old, good builds cannot be find anymore in the download page (or I don't see where) and it was before the magical Dual ISO arrived (hard to make a choice!). Maybe during the autoexec unification (?).
Yes SpcCb. This has only ever shown up shooting FPS override RAW. It works perfectly ( atleast for me) with h.264.
However, Raw is an extremely important feature for FPS override as it lends itself so much to landscapes and architectural shoots which so heavily rely on grading.
I also thought it was working earlier but as it only appears to occur below 1.5fps I am tempted to now think that the few times I used it successfully must of incidentally been above the 1.5fps threshold.
I'll have to check the cadence of the frame repeats. I've mainly seen the same 1-2-1-3-4-1 as you SpcCb. However, I seem to recall that I've seen different cadences with different settings in the past.
Is there an official bug reporting procedure with the RAW builds or is discussing it here on the forum actually functioning in that regard? I just want to make sure that I do whatever testing, etc. is most constructive and beneficial to helping the programmers/testers nail this bug.
Quote from: Steadicam on November 12, 2013, 06:08:18 PM
(...)
Is there an official bug reporting procedure with the RAW builds or is discussing it here on the forum actually functioning in that regard?
Apparently, not yet.
Quote from: Steadicam on November 12, 2013, 06:08:18 PMI just want to make sure that I do whatever testing, etc. is most constructive and beneficial to helping the programmers/testers nail this bug.
I was thinking like you; did not have time to make tests for a constructive report yet, but I'll do it today.
When tests will be done (in a couple of hours) I'll open a new issue in bitbucket.
Quote from: SpcCb on November 12, 2013, 09:53:04 PM
(...)
When tests will be done (in a couple of hours) I'll open a new issue in bitbucket.
Done:
-> https://bitbucket.org/hudson/magic-lantern/issue/1755/duplicate-first-frame-with-low-fps
Very happy to report that there is improvement via HDMI monitoring.
Using Latest NB NOV 14.
Camera no longer crash when playing back raw video via ext hdmi monitor.
On my first tests, I was able to preview video.
On my later tests I'm getting NO IMAGE message on the external monitor. This message is shown on a large black background that does not fill up the whole screen,
I can clearly see on the margins/border area my recorded image together with artifacts.
If I remove the hdmi and preview on camera LCD the video is played back normally.
The framing guide is still not giving accurate framing so I still use GD off.
The good news is that in my tests the camera did not freeze anymore.
I get good speed like everyone else on newest build.
But I get very random loadings of the modules.
Every third or forth time I turn on the camera, it starts without any modules and says "Modules will load next time" or something like that.
no biggey really, but I see that could be a problem if I was out running and gunning, as I'd have to restart the camera to capture "that ONE shot!!" :.
But perhaps this is just me? cause then a complete re-install might be in order.
Quote from: ted ramasola on November 15, 2013, 08:47:44 AM
Very happy to report that there is improvement via HDMI monitoring.
Using Latest NB NOV 14.
Camera no longer crash when playing back raw video via ext hdmi monitor.
Hi Ted , what built is this ?
I only see the Oct 24, built (af9a60fe144d), or is there a different
link for downloading the 5d2 raw module ?
reddeercity
The Nightly Builds have since ported the special features we were using in this fork. Go to the Nightly Builds download for 5d2.212 here: http://builds.magiclantern.fm/#/
Hello :)
Test out the new A.D. Built Nov., 16- (d84b9cd9e86f)
Global Draw on .
It's Slowed down the camera, With the GD on all the time.
I had lots of issue with Lv freeze, reboot + battery pull.
Write speed was down to about 65 - 68MB/s Normally 75MB/s
So i would only get about 400 - 600 frames @ 1872x1012 , on older builds i get
full card record at that size, (lexar 1000x 32GB).
There was no tone for record or stop, And for some reason we have lost
Clean(no overlayes) HDMI out when recording to a hdmi recorder ?
The only way now is to Clear overlays when recording.
That's fine but there is no way to know about your raw recording info data.
Before,when you have a hdmi recorder plugged in Global Draw would turn off when you start to record raw and the
info bars were at the very top & bottom of screen which was fine ,i could crop that out.
Now the icon & raw info are 1/3 down the screen , so there again you would have to turn off
All Overlay to record Lv to a hdmi recorder for backup. I think this is a important issue needs to be address.
On the Positive note the Hdmi don't crash when you stop recording raw
and the MLV format work better on this build but still slow with limited number of Frames.
At lest for myself i will return to the Oct 24th Built from A.D. and wait until there is more stable builds that have the
same performance level of the oct 24th raw build.
There is a little work around for the hdmi crashing in the Oct 24th built,
i have notice that if you plug your hdmi device in to the camera after it boots up
when you stop recording raw it will not crash or lockup. But if you boot up with hdmi device plugged in
Then it will crash every time upon writing the last buffer block .
:)
a.d.: "The Bad thing: I don't have much time and I also need some help in documentation: post production, sound, proof reading etc..."
Let me know how a none-programmer like me can help.
Thank You for the hard work a.d. !
Since the addition of the hack will go to the nightly build could You please add the link to them in the first post also, because I really like this thread much more than the general one :-)
Wish You more extremely well paid work, so You could have more free time for the development!
Hi a.d.!
I am having the exact same issues as reddeercity described. The whole module looks like the normal nightly builds, not the one from you.
I don't get it anyway. The a.d.-builds normally have a speed-benefit and some extra-features. Why not include them in the normal nightlies? Is there a drawback?
Greetz
Peter
Quote from: pholler on November 19, 2013, 11:57:17 AM
Hi a.d.!
I am having the exact same issues as reddeercity described. The whole module looks like the normal nightly builds, not the one from you.
I don't get it anyway. The a.d.-builds normally have a speed-benefit and some extra-features. Why not include them in the normal nightlies? Is there a drawback?
Greetz
Peter
I believe they only work on the 5D2 and may cause issues with other cameras.
I have very hard getting framing to be accurate on newest build.
Very rarely I get accurate framing in camera. I'd like very much if the white frame from previous build came back again.
And before, I could record without liveview but still see frame counts and expected and all, but now I need global or no info at all and usually global doesn't record.
I think I will be reverting back to previous build.
Hi all, here is a short video shot inside the Hanted House of LaRonde, a Six Flags amusement park in Montreal, were I worked in October for the Halloween Event.
The light condition where less the ideal but the result is pretty good (at least by my standard).
It's all shot with the same lens and hand held without any gear (it can be a bit shaky in some places but it still work all right).
I choosed to do it in these conditions to try to see how far the ML can go in terms of usability in real gigs.
The edit might look a bit cheesy (and I agree) but it was mostly fooling around with the music.
Workflow I used was .RAW->RawMagic->AE (Proxies/Grading/FX)->PPRO (trough Dynamic Link)->Vimeo
This workflow is extremely fast and efficient and ensure optimum quality of image throughout the process (no transcoding).
BTW, for people who says that proxy take to long to setup in AE to be usefull, there is a little but extremely helpful (and free) script that does it all in a few click. It's called rd_approximate_v1.0
Appreciate the comments!
Update: had to put password because of copyright things, sucks!
Update 2: Oupa, Sorry, forgot to put the password: professionnel
Quote from: lokki19 on November 24, 2013, 02:35:35 AM
Appreciate the comments!
Update: had to put password because of copyright things, sucks!
Understood. You going to give the password?
saw your video before you had to put on a password and I thought it looked extremely good!
Looked sharp and couldn't see any noise as of what I remember.
But now that I'm prohibited from seeing it again, I really wanna see it :)
Quote from: Kharak on November 25, 2013, 04:13:35 PM
saw your video before you had to put on a password and I thought it looked extremely good!
Looked sharp and couldn't see any noise as of what I remember.
But now that I'm prohibited from seeing it again, I really wanna see it :)
I updated my original post with the password.
really dope!!
is there any way i could get those tv shots?? i have a music video that has a setup similar... but i like the way u did it.. i wanna end my video how you started yours.. if not thats cool, if so ill credit you in the video description thanks.
Quote from: lokki19 on November 25, 2013, 04:22:06 PM
I updated my original post with the password.
aah thanks man!
Lighting is filmlike and at 1:41, when you see that guy from the side and he opens his mouth just a bit more than a human should, that was really good.
Check out my Movember video I shot on the Oct.24th build. Tech specs listed on vimeo.
nice dialogue
@a.d
is cr2hdr also A1ex's cr2hdr amaze edge2? if not could you possibly cross it to mac as i really like the look, cheers.
Shoot with magiclantern 1880X800
good one justinchase!
this shows really good what RAW does to a dslr cam! Especially with the frontlighting shots.
And: good flow/tune also! 8)
Hello!!!!I can make only 2 Seconds in 1880 Raw 16/9 on my 5D MKII, I have the latest build and a 800X Lexar 16GB...Does anyone tell how I must to prepare my CF or my camera to have continious record´s????I have apple computer...
Thankyou very much!!!!!
hdclip > What's the target FPS?
Quote from: SpcCb on December 02, 2013, 04:59:30 PM
hdclip > What's the target FPS?
24 or 25, with booth the same Result...when start record and arrives to +/-27mb/seg stop recording...and before to start record in the Magic menu said with this resolution only expecteed 140 frames...
It isnt normal, really???
Quote from: hdclip on December 02, 2013, 05:55:39 PM
24 or 25, with booth the same Result...when start record and arrives to +/-27mb/seg stop recording...and before to start record in the Magic menu said with this resolution only expecteed 140 frames...
It isnt normal, really???
Benchmark the Lexar 800x CompactFlash card in ML. It may not be fast enough at your chosen resolution.
Quote from: PressureFM on December 02, 2013, 06:01:53 PM
Benchmark the Lexar 800x CompactFlash card in ML. It may not be fast enough at your chosen resolution.
also have a 7D and I have not this problem, configure the 7D I turned more difficult by the issue of autostart but I can record 2 minutes, in contrast with the 5D I can not even two seconds ... I think something happens because 120mb/seg..., need to configure the card in a special way, any special formatting or something??
800x cards are to SLOW to record that frame size
Best you can get is 1872x930
1000x cards is min. For full
16:9 or even 1.85:1 at 1880,1872
You will be able to record 1728x768
16:9 (I think that the size)
The max size I record on my 5D2 @ 16:9
Is 1880x1058 @23.976 for about 700-1000 frame.
For continuous recording I use Lexar 1000x 32,64GB
For frame size in non crop mode 1872x1012,
And in crop mode 2048x930 both at 23.976.
This is on the Oct. 24th built from A.D.
Do not use the nightly built for the 5D2
As it dose not work every well (slows do the camera & crashes)
The only that stable right now is Oct24th built.
I use it for Paid work, and keep away from
The MLV format right now it kills the camera performances
It total useless on the 5D Mark2, it really only works
On the 5D3
Quote from: reddeercity on December 02, 2013, 07:35:04 PM
800x cards are to SLOW to record that frame size
Best you can get is 1872x930
1000x cards is min. For full
16:9 or even 1.85:1 at 1880,1872
You will be able to record 1728x768
16:9 (I think that the size)
The max size I record on my 5D2 @ 16:9
Is 1880x1058 @23.976 for about 700-1000 frame.
For continuous recording I use Lexar 1000x 32,64GB
For frame size in non crop mode 1872x1012,
And in crop mode 2048x930 both at 23.976.
This is on the Oct. 24th built from A.D.
Do not use the nightly built for the 5D2
As it dose not work every well (slows do the camera & crashes)
The only that stable right now is Oct24th built.
I use it for Paid work, and keep away from
The MLV format right now it kills the camera performances
It total useless on the 5D Mark2, it really only works
On the 5D3
Thankyou Very Much!!!!!!I will try... ;)
+1 with reddeercity.
Plus, I can say I never saw a 5D2 recording continuous in 16/9 RAW 1880px at 25, 24 or 23.976fps, even with a 160MB/s CF card.
Maybe with a 800x it should be continuous in 2.35 AR with 1880px at 23.976fps. I use this config with a Sandisk CF 60MB/s.
Quote from: SpcCb on December 03, 2013, 12:59:19 AM
+1 with reddeercity.
Plus, I can say I never saw a 5D2 recording continuous in 16/9 RAW 1880px at 25, 24 or 23.976fps, even with a 160MB/s CF card.
Maybe with a 800x it should be continuous in 2.35 AR with 1880px at 23.976fps. I use this config with a Sandisk CF 60MB/s.
Thank you very much this magicworld and their people is amazing, but the problem with the 5D is the buffer or the processor???what do you think???
Not sure exactly where the bottleneck on the 5D2 is, but the writing limit seems to be around 75 MB/s. That limit is due to the hardware of the camera so faster cards won't do any good.
Quote from: bnvm on December 03, 2013, 05:18:16 PM
Not sure exactly where the bottleneck on the 5D2 is, but the writing limit seems to be around 75 MB/s. That limit is due to the hardware of the camera so faster cards won't do any good.
But with this teory the lexar 800x must be work fine at 1880, and it seems that the camera cant go up 40Mb/seg...(in my camera)
?????
Quote from: hdclip on December 03, 2013, 10:15:59 PM
But with this teory the lexar 800x must be work fine at 1880, and it seems that the camera cant go up 40Mb/seg...(in my camera)
?????
Nope, the Lexar 800x rating is based on read speed, not write speed.
Yep most cards I have tried seem to write at about half of the speed they post on the card, I remember a 90 MB/s scandisk card writing at about 45 MB/s. I also have a monster 800x card and I believe I can get about 52 MB/s on that one. If you want to max out the write speed you will need a 1000x card, period.
Ok... :'( ... And now, one stupid question, the indicator of the Ml speed is Megabyte or Megabit??? ;D
And the CF is Megabyte or Megabit???
MB/s(Megabyte) not Mb/s(Megabit) :)
Thank's!!!!!
Hello
I the current operating system on my 5D MKII. I had ML installed and tried to install the RAW files from a download.
My Camera locked up and I removed ML.
Would it be possible for someone to post a step by step reinstall of ML and the RAW download?
It would be greatly appreciated.
Only the Best to You
Gary
Quote from: garymadison on December 04, 2013, 08:21:48 PM
Hello
I the current operating system on my 5D MKII. I had ML installed and tried to install the RAW files from a download.
My Camera locked up and I removed ML.
Would it be possible for someone to post a step by step reinstall of ML and the RAW download?
It would be greatly appreciated.
Only the Best to You
Gary
I wrote a short tutorial back late May , link below
http://www.magiclantern.fm/forum/index.php?topic=5533.msg44827#msg44827
I hope that helps, plus I have in the works a short video tutorial on how to
install ML raw on the 5D2 with trouble Shooting problems. :)
PS: On page one you will find the latest Raw module download,
right now the Oct 24th built is the best one from the 5D2
link the Raw module
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
Quote from: reddeercity on December 04, 2013, 08:53:48 PM
I wrote a short tutorial back late May , link below
http://www.magiclantern.fm/forum/index.php?topic=5533.msg44827#msg44827
I hope that helps, plus I have in the works a short video tutorial on how to
install ML raw on the 5D2 with trouble Shooting problems. :)
PS: On page one you will find the latest Raw module download,
right now the Oct 24th built is the best one from the 5D2
link the Raw module
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
Thanks for all your communication on this evolutionary forum community, I've gain an easier workflow as well as greater knowledge ML and your input. Thanks
I do have a few questions,
1. Do you shoot in aspect ratio 2:35?
2. What is your highest preferred Resolution with the 5DII?
3. Are you considering using Davinci Resolve in your Workflow?
4. I've use your workflow RAWMagic DNG to ACR to Tiff to Final Cut Pro X, but I'm wondering have you come up with a way to make the Tiff size smaller without losing quality and what's the highest up convert do you recommend for the DNG to Tiff?
5. Lastly, what's your thoughts on ProRes 422 vs ProRes 4444.
Thank, I like to share ;)
darriSSight, if you are using RawMagic that should be a Cdng and FCPx can Read
that file type. That How I get raw in to FCPx, it 1/3 the size of tiff's .
So same workflow that you use with tiff's but use Cdng's.
At lest this work with raw2cdng on Windows PC, but I think it should also work with
RawMagic.
I use Apple ProRes 4444, It's the closes think to CDNG being it's a RGB 10 or 12bit
the bandwidth is about the some, around 220 Mb/s.
There again I shoot in the Largest frame size my cards can handle
Just re-frame/Crop, I do this all the time.
1872x1012 23.976p for continuous recording on the Oct 24th built, I will not use any think newer.
But if I Make a Video for ME or a tutorial to help people understand ML better
then I shoot in either 1880x1250 3:2 ,1880x1058 16:9 or at 2k 2048x1024 2:1 2048x930 2.2:1
I don't Shoot any video unless I have plan it out, I would say that only about 20%
of the footage is cut out, where as when I would shot H264, or any other Cameras it more like
40% is cut out.
I have started to look at Resolve, but it would be as a last resort, it has a very odd GUI
which I'm not comfortable with.
And besides that the debayering in Resolve is not as good as the ACR plugin, in After Effect.
If I'm in rush to do a project I will sometimes make a ProRes 4444 In After Effect then
Finish off in FCPx with audio sync Grading etc...
You can go from 2k to 4k with tiff's that's about it for upscaling.
the reason for 2k Crop and not 1:1 non crop is there is no line Skipping, so no aliasing and moire
I hope I answered your Questions
FYI: when you import Image files in to FCPx you can Choose different Color Space .
there is 4 or 5 ones to pick, if you do not it will default to Adobe RGB. ;)
PS: keep on a lookout I'm just finishing off a Full 3:2 sensor test(1872x1250) with Film convert Pro applied Etc..
should be up in the next few days.
Quote from: reddeercity on December 05, 2013, 03:18:50 AM
Thank, I like to share ;)
darriSSight, if you are using RawMagic that should be a Cdng and FCPx can Read
that file type. That How I get raw in to FCPx, it 1/3 the size of tiff's .
So same workflow that you use with tiff's but use Cdng's.
At lest this work with raw2cdng on Windows PC, but I think it should also work with
RawMagic.
I use Apple ProRes 4444, It's the closes think to CDNG being it's a RGB 10 or 12bit
the bandwidth is about the some, around 220 Mb/s.
There again I shoot in the Largest frame size my cards can handle
Just re-frame/Crop, I do this all the time.
1872x1012 23.976p for continuous recording on the Oct 24th built, I will not use any think newer.
But if I Make a Video for ME or a tutorial to help people understand ML better
then I shoot in either 1880x1250 3:2 ,1880x1058 16:9 or at 2k 2048x1024 2:1 2048x930 2.2:1
I don't Shoot any video unless I have plan it out, I would say that only about 20%
of the footage is cut out, where as when I would shot H264, or any other Cameras it more like
40% is cut out.
I have started to look at Resolve, but it would be as a last resort, it has a very odd GUI
which I'm not comfortable with.
And besides that the debayering in Resolve is not as good as the ACR plugin, in After Effect.
If I'm in rush to do a project I will sometimes make a ProRes 4444 In After Effect then
Finish off in FCPx with audio sync Grading etc...
You can go from 2k to 4k with tiff's that's about it for upscaling.
the reason for 2k Crop and not 1:1 non crop is there is no line Skipping, so no aliasing and moire
I hope I answered your Questions
FYI: when you import Image files in to FCPx you can Choose different Color Space .
there is 4 or 5 ones to pick, if you do not it will default to Adobe RGB. ;)
PS: keep on a lookout I'm just finishing off a Full 3:2 sensor test(1872x1250) with Film convert Pro applied Etc..
should be up in the next few days.
Thanks for the response
FULL 3:2 sounds great for a project in your workflow and how many frames are you getting?
What color space do you recommend, I've heard that Adobe RGB was the best?
I always wonder how do you frame a shot in crop mode because it demands for further distance from subject, Right?
I get 400-500 Frames @1872x1250 23.976,
I use the Adobe RGB Color Space for the Cdng's in FCPx
in 3x Crop Mode you would want to use Shorter lens, like 24mm = 72 mm
I use my EF 24-70 f2.8L in crop mode mainly, or EF 100mm macro f2.8L
Which turn in to 300 mm , amazing Close ups at 1:1 in macro mode :D
Quote from: reddeercity on December 07, 2013, 02:47:47 AM
I get 400-500 Frames @1872x1250 23.976,
I use the Adobe RGB Color Space for the Cdng's in FCPx
in 3x Crop Mode you would want to use Shorter lens, like 24mm = 72 mm
I use my EF 24-70 f2.8L in crop mode mainly, or EF 100mm macro f2.8L
Which turn in to 300 mm , amazing Close ups at 1:1 in macro mode :D
AWSOME frame capture, a lot could be accomplished with 36 seconds of 1872x1250.
So it's unavoidable I will need to spend $2000 on those 2 lens, right?
Do you prefer 1872 over 1880?
After these questions I think I'm on track Thanks for the info, I will test out 1872x1250 this weekend.
Sorry for delay!
Quote from: Kharak on November 17, 2013, 04:37:54 PM
Let me know how a none-programmer like me can help.
Thank You for offer to help!
Post Production: When you have a good workflow, It's cool if you could share it ... screenshots and descriptions. I will add to our Alpha 2 documentation.
Quote from: cmac on November 19, 2013, 08:50:15 AM
Wish You more extremely well paid work, so You could have more free time for the development!
Thanks!
Quote from: pholler on November 19, 2013, 11:57:17 AM
Hi a.d.!
I am having the exact same issues as reddeercity described. The whole module looks like the normal nightly builds, not the one from you.
I don't get it anyway. The a.d.-builds normally have a speed-benefit and some extra-features. Why not include them in the normal nightlies? Is there a drawback?
Greetz
Peter
It's possible, but hardly to maintain.
1. If the code of are changed. Everytimes I need to check if it breaks
2. I have 3 different Respositories (2 bitbucket, 1 dropbox) => 3x test
3. API Development moves to LVInfo => our Interface concept doesn't fit
The big problem is the low performance DIGIC IV ARM CPU, for example
GLDraw On: 1-2MB drop
HDMI plug-in: 1-2MB drop
Currently IÃm still trying to wrap my head around how to port the hacks without breaking the API and easy to maintain.
That's Great to hear that you are working
On the 5d2 issue's A.D.
If you need any help , I be glad
To do what I can, specially in the HDMI department
I have several devices I test to test with.
:)
Is there any way the card space remaining monitor can be updated in real-time? Or some log be kept so that we can know exactly how much space is remaining on the card? It's pretty much the only thing left in the way of using raw on a professional shoot, because I have only a vague idea of when the space is going to run out.
Quote from: silvertonesx24 on December 08, 2013, 04:48:44 PM
Is there any way the card space remaining monitor can be updated in real-time? Or some log be kept so that we can know exactly how much space is remaining on the card? It's pretty much the only thing left in the way of using raw on a professional shoot, because I have only a vague idea of when the space is going to run out.
Turn the camera off and on.
Just tried the new Dec. 07/13 built From A.D.
:(
There has been a lot a changes, and we are going backwards,
The performances is still very poor, lucky to get 70MB/s
@ 1872x1012 23.976, 1500 frames,
Compared to the Best Built to Date Oct.24th 2013
at 1872x1012 23.976 I Get 42 GB or about 14,000 Frame ! at 75.5MB/s
There is No Recording Frame white rect., where did that go ?
just that ulgy Black Box.
The interface for raw record monitoring has change for the worse,
There again Oct 24th was better , it did not get in the way of view the Lv.
In the Preview Menu, when you select Canon preview mode it would before in Oct 24th built
It would turn all overlays off and leave the raw interface with buffer only displayed.
But now there is 2 semi transparent Bars upper and lower that can't be removed.
Now there is No more Clean HDMI out, unless you turn Off all overlay ,And or Global Draw Turn Off.
So with that you have no Idea on how much space free you have on the card or if the recording is about to Stop.
If I what to Use my Ninja hdmi recorder to Backup my raw recording I have to Turn Off All overlay then Record.
Before on the Oct 24th built with a hdmi recorder connected to would get a Clean out to the recorder,
With just the Raw interface in the UpperLeft hand Connor of Lv that could be crop out if needed.
Unfortunately I did not Check to see if the 42 GB Wall is broken, For I Have returned back to
the Oct 24th built, its looking like there is no more improvement that can be make to that built.
Its really looks like the 5D2 Can Not Handle the Global Draw On with Raw Recording.
I do not think that implementing a universal Global Draw on for all Cameras, is the right thing to do.
My Vote is to Go Back to the Oct 24th built Style of interface and functionality, (eg. proper hdmi support)
But I think the Dev. are trying to push the MLV format on the 5D2 and it will not work will, just not enough CPU!
There is just enough CPU to maintain the present raw format as it is in the Oct 24th Built.
Please I don't what to Sound Negative About this update and all the Hard work everyone has
done, but I would always choose to have Better Raw recording speed and large frame sizes over
Convenient On Screen displays (eg. Global Draw stuff) considering just about all Field Monitor have
Pecking, Wave from display etc... .
:)
Well, this kind of feedback encourages me to stop developing for raw video (which I don't really use anyway) and just focus on my own interests.
FYI: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Oh listen to the positives and not the, sorry to say it, buts its true, the ***** :)
They tend to sound more than the ones praising you. Despite being less.
"raw_rec: 43GB filesize fixed" !! Wooa! Wonderful, I can't try this now but thanks a lot.
Just to let everybody knows that I keep on checking this thread on regular basis, though I'm more just a silent reader but I get really excited when an update is up. We have a community right here in Indonesia that appreciates what a1ex, a.d and everyone else is doing especially on the RAW video development. I have use the raw video in professional projects and the clients are happier than ever due to the quality it have brought to us.
Please keep the spirit up for the sake of passion to reach the very edge of perfection.
Cheers :)
Audy Erel
A lot of us are still using mark ii's and the fact that anyone is working on releasing new mlraw updates is god sent. If you don't like the latest update just use the old version or make your own, you're not owed anything.
My apologies to the community. Got carried away.
He was just expressing some criticisms in the direction development is heading, I don't think he was being rude for the most part. This kind of thing is healthly for development, it is silly how everyone jumps all over someone who dares to question what the developers are doing. Isn't the whole point of these forums is for people to discuss these kind of things or should we close the forums and just use the builds that get provided no questions asked. Keep in mind the latest raw developments are much slower on the 5D2 which is the second most raw capable camera behind the 5D3 all of these changes will have more impact on the even slower cameras. Looks to me like development is primarily for the 5D3 at this point regardless of what that may mean for other cameras.
For the record I am happy with the new builds since I don't need to make the write speed shooting anamorphic, and the magic zoom is very helpful now.
Quote from: reddeercity on December 07, 2013, 05:00:01 PM
...
If you need any help , I be glad
To do what I can, specially in the HDMI department
I have several devices I test to test with.
...
Thanks, I'll come back for Alpha 2.
@ARP
mlv_rec: There's a new base_prio and it increases speed on 5D2 up to 72-73 (credits baldand). Tommorrow I'll put it in dropbox for download. It's late now. There're still some glitches, for example sometimes the LV freezes for a few seconds during recording.
Quote from: ARP on December 09, 2013, 09:54:06 PM
What an idiot. Unbelievable. A lot of us are still using mark ii's and the fact that anyone is working on releasing new mlraw updates is god sent. If you don't like the latest update just use the old version or make your own, you're not owed anything.
This is uncalled for. reddeercity did not write anything in his posts that is insulting and he has provided assistance to a lot of users in this forums.
I have seen all your 3 posts. Nothing there that shows any help you have provided but an insulting remark.
Thanks ted ramasola & bnvm :)
I will also be honest with my feedback, on new builds,
It's Never to offend or insult, but some my take it that way.
@A.D. Can't Wait to Put your new Built on my 5D2 and give it a work out ;)
@ARP, it is thanks to reedercity's post that I can now decide to stick to the old version without having to spend trying and testing the new one for myself; how has your voice been adding to the conversation here?
Suffice to say your post was unwelcomed ARP.
Lets dispense with the insults shall we.
Quote from: bnvm on December 09, 2013, 11:09:41 PM
He was just expressing some criticisms in the direction development is heading
I was expecting something better than one page of complaining that can can be resumed to "global draw is on by default, we have to turn it off". You can link it to the INFO button or you can have it turn off on timeout (say 5 seconds).
Having yet another option for global draw in the raw recording menu is an usability issue for me (other people pointed it out, for example in the 50D thread). I'd rather add an option in the main globaldraw menu (something like "turn off while recording").
My point was that whining about stuff being broken is not the best way to make us fix it, but proper bug reports are.
I just wanted to thank Alex and AD, I´m not an expert , so I have been a passive member of the forum. In this case I will only express my support to them and if there is any way to donate to keep you working on this, let me know. Many of us would love to help or donate.
In my case, your work has helped me to shoot in the best way possible my first short film after 14 years since the last one I did when I was in school ,and recently a commercial using green screen.
So, thanks guys...I will try to report bugs in a helpful way the next time I post.
The new base_prio for MLV_REC.
MLV_REC.zip (https://dl.dropboxusercontent.com/u/13314708/MLV_REC.zip)
btw
Don't format the card in the camera after recording! You need to switch off & on and then format or it wipes complete ML from card.
@a.d.
Something minor but just to avoid confusion, you might want to correct the date of your last update in the 1st post. Its 2013/07/02, is this suppose to be 2013/12/02 ?
fixed date! Thanks!
Quote from: a1ex on December 10, 2013, 07:09:44 AM
I was expecting something better than one page of complaining that can can be resumed to "global draw is on by default, we have to turn it off". You can link it to the INFO button or you can have it turn off on timeout (say 5 seconds).
Having yet another option for global draw in the raw recording menu is an usability issue for me (other people pointed it out, for example in the 50D thread). I'd rather add an option in the main globaldraw menu (something like "turn off while recording").
My point was that whining about stuff being broken is not the best way to make us fix it, but proper bug reports are.
I can see your point, besides my comment was not directed at you.
Hello all, Just finish with my 3:2 Sensor test, I give a little intro filmed at 2k
Plus I show Film Convert Pro applied to the raw file. used Oct 24th Build
hope all like it :)
If on a PC Internet Explorer 11,there is a gramma shift down, look like Crap there.
Use Chrome , then it looks right. :-[
Just checking in to give support. Great job A.D.!
Just finished filming a 10min short film for school using my 5DM2. All shot RAW. 1880x800 Scaled to 1920x818. I know the acting isn't great, it was my friends and I. We shot this in a day and a half.
It was graded entirely in Davinci Resolve, started off using Hunter's LUT then went from there. Film grain is by http://rgrain.com/.
Before & After example of the color correction. Click for larger image.
(http://farm6.staticflickr.com/5527/11363107715_8bf941baca.jpg) (http://farm6.staticflickr.com/5527/11363107715_1139b02826_o.jpg)
The original RAW DNG had the BMD Film applied to it in Resolve.
Quote from: reddeercity on December 13, 2013, 12:14:44 AM
Hello all, Just finish with my 3:2 Sensor test, I give a little intro filmed at 2k
Plus I show Film Convert Pro applied to the raw file. used Oct 24th Build
hope all like it :)
If on a PC Internet Explorer 11,there is a gramma shift down, look like Crap there.
Use Chrome , then it looks right. :-[
I love the 3:2 Sensor Test, I have a few questions like are to scaling up 3:2 to 16:9 in a 16:9 timeline? Have you read about Andy600 LUT on the forums and how are you applying LUT in FCPX? By the way RAW DNG from RAWMagic to ACR to FCPX, how would I do upscale 1872x1012 or 1880x1016 to 2k.
Quote from: dariSSight on December 16, 2013, 12:13:20 AM
I love the 3:2 Sensor Test, I have a few questions like are to scaling up 3:2 to 16:9 in a 16:9 timeline?
Thanks
Yes I am, scaling in FCPX timeline it dose a great Job,
Quote from: dariSSight on December 16, 2013, 12:13:20 AM
Have you read about Andy600 LUT on the forums and how are you applying LUT in FCPX?
No I have not read about Andy600 LUT, I will have to do some searches & read up on that.
I really don't use LUT's But I have been working with Film Convert Pro Plugin, which is Film Stock
emulation & Camera sensor mapping.
But I guess Film Convert Pro is basically working with LUT's that can be adjusted on the fly
with effects generators etc...
It dose Save a lot for on grading thou.
Quote from: dariSSight on December 16, 2013, 12:13:20 AM
By the way RAW DNG from RAWMagic to ACR to FCPX, how would I do upscale 1872x1012 or 1880x1016 to 2k.
Personally I would Film in 3x Crop Mode to get 2K, in my Video I shot myself at 2048x930, for 14300 frames or about 10 min.
The biggest reason is to eliminate aliasing and moiré and there is no Line skipping so you get cleaner and sharper images.
I have also notice I get better low light performance, no noise in the blacks.
But if you really what to up Scale to 2k from 1872x1012 or 1880x1016, then there are
Two ways I would approach it , the Best way is the ACR Photoshop>16bit tiff's up scaling workflow.
This gives the best Cinematic Feel to the image. More organic look.
Or in After Effect also but I don't like the results as much as Photoshop.
The Second would be on the timeline in Final Cut Pro X, just set the project to 2k and FCPX will do
the rest. Which is a very good job, either way works find .
:)
@delrosestephen
Nice short! I enjoyed it and was compelled to watch it to completion. That dancing baby was creepy as hell. ;D
On a related note, I noticed that most videos I've seen (related to RAW) have a odd levels (non-black shadows and nonwhite highlights). Is this the style people are going for these days or are they accidentally outputting to TV levels instead of PC? It lowers the contrast by quite a bit.
Quote from: Yoshiyuki Blade on December 17, 2013, 05:18:22 PM
@delrosestephen
Nice short! I enjoyed it and was compelled to watch it to completion. That dancing baby was creepy as hell. ;D
On a related note, I noticed that most videos I've seen (related to RAW) have a odd levels (non-black shadows and nonwhite highlights). Is this the style people are going for these days or are they accidentally outputting to TV levels instead of PC? It lowers the contrast by quite a bit.
Thanks!
The non-black shadows and non-white highlights for me was an aesthetic choice. I wanted to give it a little bit of a 90s television/movie feel. If you look at the image that I attached to my post you can see my color-correction process, and see that I started with a pretty leveled image.
Filmed almost entirely in raw using AD's October 24th build. I felt like I took a risk shooting 10-15min interview sessions in raw, but everything held up perfectly.
One or two hacked GH2 shots in the B roll. Graded with ColorGhear
Quote from: silvertonesx24 on December 20, 2013, 06:19:05 PM
Filmed almost entirely in raw using AD's October 24th build. I felt like I took a risk shooting 10-15min interview sessions in raw, but everything held up perfectly.
One or two hacked GH2 shots in the B roll. Graded with ColorGhear
Looks great but it suffers heavily from lipsync here?
Quote from: silvertonesx24 on December 20, 2013, 06:19:05 PM
Filmed almost entirely in raw using AD's October 24th build. I felt like I took a risk shooting 10-15min interview sessions in raw, but everything held up perfectly.
One or two hacked GH2 shots in the B roll. Graded with ColorGhear
Looks extremely good!
Are you using some anamorphics in some of the shots? Noticed the bokeh being all nice and vertical.
Quote from: PressureFM on December 20, 2013, 09:26:41 PM
Looks great but it suffers heavily from lipsync here?
Thanks! I'm not sure what's up with that as it seems to be a vimeo thing. The source file is perfect, as well as the YouTube upload.
Quote from: Kharak on December 21, 2013, 12:45:25 AM
Looks extremely good!
Are you using some anamorphics in some of the shots? Noticed the bokeh being all nice and vertical.
I do use anamorphic often, but in this case I was using the Vid Atlantic anamorphic filter.
Complete Video Guide To Installing Magic Lantern Raw On the 5d
http://youtu.be/3SzVnVk3xmU
Hi Everyone.
This is a complete guide to installing magic lantern raw on the 5d.
What is it?
What you need to know?
How to install it.
How to use it.
What to do with it in post.
Chris :)
www.boygetslost.com
Quote from: reddeercity on December 13, 2013, 12:14:44 AM
Hello all, Just finish with my 3:2 Sensor test, I give a little intro filmed at 2k
Plus I show Film Convert Pro applied to the raw file. used Oct 24th Build
hope all like it :)
If on a PC Internet Explorer 11,there is a gramma shift down, look like Crap there.
Use Chrome , then it looks right. :-[
hi,
many people use Oct 24th Build that works great but i couldn't find out.
https://bitbucket.org/a_d_/magic-lantern/downloads
Does everyone talk about Oct 24 build in this link???
Yes, that is.
Quote from: philostory on December 27, 2013, 08:36:17 AM
hi,
many people use Oct 24th Build that works great but i couldn't find out.
https://bitbucket.org/a_d_/magic-lantern/downloads
Does everyone talk about Oct 24 build in this link???
Hello, You are close but that's not the one I use
I use the one From A.D.'s Special Hack build for the 5D2
It the one with the disclaimer about Hot pixels .
This build is a lot faster then the vanilla (plane Jane) build that you are referring to.
Go to the first link read the disclaimer about hot pixels, (I don't think too many people even have this problem)
Then go to the second link, with the Oct 24th build.
Link below
https://bitbucket.org/a_d_/laboratory/wiki/Home
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
There is also better hdmi support with A.D.'s Hack Build which is very
critical for backup thought a hdmi recorder on paid jobs. (I use a Ninja hdmi recorder).
I always get about 15-20% more performance but on Lexar 1000x cards only,
I'm not sure if the Komputerbay 1000x cards are as fast, I have heard there is problems with them.
I hope this info helps, ;)
PS. I have being only using A.D. hack builds since June of this year
and never had a problem once !
Thank u for information clearly that sounds so cool.
I'll try some test even though i may need Lexar 1000x cards first.
Hey folks,
I have not worked with magic lantern for months and I am not up to date how the project progressed.
For examble, what is the difference between the "raw video" and the "raw video (MLV)" module?
Will dual iso finally work with the 5dmk2?
Is it still important to switch off global draw?
thanks for clarification. :-)
oli
@ olik
Well essentially the MLV format will hold all sorts of meta data but the latest addition that I think pleases many is the addition of audio. The MLV is a kind of package containing all the RAW data (including audio etc.). You need to use the the correct conversion tools to use this.
I am not going to explain all of this because there is more than enough information on this site. But yes, the audio that seems to synchronise well with the video, is what makes me want to use it.
Mageye,
I kinda got delayed adopting to the MLV format and stuck with rawrec till now that audio is available. Have you tried it already? and if you would be so kind, could you point to the MLV compile that has the MLV sound module already working for the mkII. I'd like to give it a try.
Many thanks in advance.
Ted
added:
Should I use the one on the first post in the "pre-built" link in this thread? http://www.magiclantern.fm/forum/index.php?topic=7122.0
thank you for the update.
I did a quick test and found that I can record less frames on MLV. I guess there is no advantages in terms of quality is there?
@ ted ramasola
Yes use the mlv_rec.mo, mlv_snd.mo from that link and (in my case) I used the 2013/12/02 (c44ceb8452f2) build. That works fine for me. :D
http://www.magiclantern.fm/forum/index.php?topic=5533.0 (http://www.magiclantern.fm/forum/index.php?topic=5533.0)
@ olik
Yes I get a lower data rate with the MLV format. But I am still able to record what I need to record so I can live with the reduced numbers.
The audio is really important to me. If the images are more important to you (as in more frames) then you can always use which module is more suited. Whenever! ;)
Thank you mageye.
@mageye,
Ok, I'm using the latest nightly dec 29 (dec 30 in the gui) + the mlv_rec.mo, mlv_snd.mo.
I'm getting continuous raw recording at 1856 x 928 and 1728 x 972 both with sound recording ON.
Questions,
1. with the current version is there no way to have correct framing while recording?
2. with the current version the onscreen overlays, (sound levels, shutter info, etc.) They disappear after every take and won't return after recording?
just need some confirmation if its the same with your version or if I'm missing something.
Somebody say something about Audio???
Quote from: Kharak on December 30, 2013, 08:50:23 AM
Somebody say something about Audio???
yup. 5D mkII raw video now has audio. ;) ...16 bit 48 khz.
Just tested audio recording. Ran a recording till it filled a 16GB card (~4 mins). Audio seemed in sync throughout the video, but cut off in the last 10 seconds or so. It's probably because I let it run till it force stopped.
Well it look like A.D. has given the 5D2 Users a Late Christmas Gift ;D
I just took the new build(the disclaimer one in crop mode warning) for a test drive from A.D. Hack Build for MLV with Audio .
Being I have just started to test it , from my first 3 records with audio
I would have to give 2 Thumb Up!!
All the Concerns I had with MLV format & global draw off I think have been
address. I still have to test it with all my hdmi devices .
So far my results for this build are:
continuous recording @ 1872x936 23.976p between 68 to 73 MB/s fill my Lexar 1000x 32GB No frame drop.
Buffer fill method - 2 (that seem to be the fastest setting)
Preview - Hacked No Preview
The audio lines up with the images very well.
Used my wireless sennheiser setup with line in on the 5D2
Very clean and clear audio at 16bit 48kHz 1.5 Mb/s. One thing I notice thou in FCPX
in metadata for the Audio it show the frame rate @ 23.976 .
I guess that would have something to do with the smpte time code.
:)
Edit: But we did Loose 1880x#### so just 1856 or 1872
I though I should test out the Raw module that with the MLV raw & sound module.
There is still issue with Global Draw/Low performance .
You can kill GD but still have the Black Bars on the top & bottom.
also now there is overlays in Crop mode. :(
My recommendation is to keep to the Oct.24th build for original raw format.
If you what Audio with the raw use the new build for the 5D2 MLV format.
I'm confused why, they fixed the global draw issue & low performance in the MLV format but not the
original raw format ?
MLV with sound recording using KB 64 gig 1000x I was able to fill up CF with 2 resolutions.
1728 x 972 16:9 and 1856 x 928 2:1.
1872 x 936 would skip at around 8 minutes.
I hope the devs can find a way to implement framing in MLV just like with the old raw_rec.mo
Quote from: reddeercity on December 31, 2013, 09:34:14 AM
I'm confused why, they fixed the global draw issue & low performance in the MLV format but not the
original raw format ?
I don't get it, doesn't turning off Global Draw bring back the old speeds? If it doesn't, I'll look into it.
For the UI, I said it before, I recommend adding a new item into the main GlobalDraw menu (something like "turn off while recording") instead of module-specific hacks.
Quote from: ted ramasola on December 31, 2013, 10:07:19 AM
I hope the devs can find a way to implement framing in MLV just like with the old raw_rec.mo
What exactly do you mean by this? (what's the difference?)
@A1ex,
I meant the frame guide, like the white rec or black border. It disappears when recording starts so it is difficult to frame a moving subject.
Also, on the mkII, the overlays don't return after recording. I have to turn off LV off and on again to bring back the overlays and information back on.
Unlike on the 7D, the overlays come back on after recording.
If it disappears, it's because you turn off Global Draw, right?
If you use a minimal set of overlays (everything off in the Overlay menu, but Global Draw on), do you still get performance problems?
in Overlays tab: every item OFF except GlobalDraw = Liveview
So in my lcd I can see the info on screen, Vu meters, temp etc. There is also black bordered framing.
So when I start recording, the black borders and the info(meters etc) disappears,
replaced with a buffer status graphic on the top part and elapsed info/frames expected info on the bottom part.
when I stop recording, the black borders and ML info dont return, instead the semi transparent canon letterboxing appears. No other info is displayed.
In MLV there are also some global draw menus (didn't try it lately, only looked at the code). Are these menus set to turn off global draw automatically? (if yes, change them to leave global draw on).
ok. I think I found it.
In Raw Video (MLV) menu there is an entry
DISABLE G. DRAW default setting is OFF, I turned it to ON so now Overlays info including framing stays on screen now while recording.
Isn't this wrongly worded? It should just say Global Draw NOT Disable G Draw as it seemes to do the opposite of what it says.
When record is started the buffer graphic and the elapsed frames/expected frames and data rate info conflicts with the other info thus cluttering the screen with flickering artifacts.
edit:
Changed the screen layout to 16:10 hdmi, t/b fixed the clashing graphics.
Yes, just make sure g3gg0 knows about it (I'm not sure if he follows this thread). A patch is also welcome.
@ted
g3gg0 is still porting the LVinfo therefore the on-screen conflicts are the "expected" behaviour.
@Boygetslost
Thanks, Chris! I added your tutorial on the first page.
This is my HDMI test results on MLV with Audio enabled:
HDMI devices (Zacuto EVF & Atomos Ninja HDMI recorder)
With HDMI>Largest Frame size Continuous record,
1872x850 23.976p 2.20:1 with Audio 22,710/15:47 min 60GB 67.9MB/s buffer method 1
Crop Mode > 1856x938 23.976p with Audio 20,000 frames 68 MB/s buffer method 0
Tried the nightly build from Jan-1 MLV, and could get larger frame size continuous with HDMI
1856x930 23.976p 2:1 19,000 frames 55GB buffer method 1
Crash 2 times with hdmi plugin when I tried to record 1856x1004 and or 1872x1012, the buffer just filled up with blue color then lockup
Battery pull & reboot ok after that.
Any Sizes in the 1.85:1 or 16.9:1 are not possible in Large sizes more then 20 or 30 second clips
It seems on the 5D2 you are limited to about 70-73 MB/s without hdmi active
and with it active then that drops to about 65-68 MB/s & in crop mode to about 74MB/s
Its definitely usable without hdmi at this point, run & gun style with audio ;)
Quote from: reddeercity on January 02, 2014, 02:28:01 AM
Its definitely usable without hdmi at this point, run & gun style with audio ;)
Great news and thanks for testing!
I have been using the newest build for a little while and have noticed a few things. Sometimes the recording will start go a few frames and then freeze up, the buffer no longer fills and the number of frames recorded stays the same but it acts like it is still recording. I stop the recording and go into the menu the MLV Raw menu shows stopping... but never does. I have to turn of the camera to get things working again.
Second occasionally when I run mlv_dump --dng, I will get a missing dng. A recent recording was missing just frame 181 out of 367 frames for example. Anyone else experiencing any of these?
Also I am using sound recording as well, so that may have something to do with it.
Quote from: reddeercity on January 02, 2014, 02:28:01 AM
This is my HDMI test results on MLV with Audio enabled:
HDMI devices (Zacuto EVF & Atomos Ninja HDMI recorder)
With HDMI>Largest Frame size Continuous record,
1872x850 23.976p 2.20:1 with Audio 22,710/15:47 min 60GB 67.9MB/s buffer method 1
Crop Mode > 1856x938 23.976p with Audio 20,000 frames 68 MB/s buffer method 0
Tried the nightly build from Jan-1 MLV, and could get larger frame size continuous with HDMI
1856x930 23.976p 2:1 19,000 frames 55GB buffer method 1
Crash 2 times with hdmi plugin when I tried to record 1856x1004 and or 1872x1012, the buffer just filled up with blue color then lockup
Battery pull & reboot ok after that.
Any Sizes in the 1.85:1 or 16.9:1 are not possible in Large sizes more then 20 or 30 second clips
It seems on the 5D2 you are limited to about 70-73 MB/s without hdmi active
and with it active then that drops to about 65-68 MB/s & in crop mode to about 74MB/s
Its definitely usable without hdmi at this point, run & gun style with audio ;)
So MLV Audio & Video work great with the Dec 30 build, RAW Audio & Video work great up to 20-30 seconds and RAW works great without audio in Oct 24 build?
Quote from: dariSSight on January 04, 2014, 12:33:27 AM
So MLV Audio & Video work great with the Dec 30 build,RAW works great without audio in Oct 24 build?
Yes MLV raw with Audio is working very well, the nighty build from Jan. 1st seems to be a little bit faster
with hdmi. I'm just finishing off a short test of about 3-4 Min, at 1856x928(continuous with hdmi) should be ready tomorrow to post.
And yes the Oct 24th build is the one to use for Non MLV raw (old format)
Quote from: dariSSight on January 04, 2014, 12:33:27 AM
RAW Audio & Video work great up to 20-30 seconds?
Yes, But you can get Continuous recording without hdmi active, but in 2:1 A.R. like, 1872x936, 1856x928 and smaller
just
not HD A.R. 1.85:1, 16:9 in larger frame size ,etc. 1872x1012 there limited to 20-30 second.
Just to confirm there is Headphone Monitoring on the 5D2
with MLV Raw+Audio, works very well.
Is it just me having issues with the overlay dissappearing when recording, despite it isnt supposed too, then never returns until reset?
The framing etc is just gone, so dont really know where Im shooting.
Some stuff shot in crop mode. I really like the gritty look the footage has, be great for a music video or something. Bit of a beast to use though.
Here a short test with MLV+Audio on the nighty build form Jan.1st
with me talking and counting to Ten plus a short tutorial on how to setup
MLV with audio, on the 5D2 :)
Thanks David!
I'll give the Sound a try now.
If I record 2 channels with my mic, will that be a problem with the MLV_snd ?
Quote from: Kharak on January 06, 2014, 03:57:40 PM
Thanks David!
I'll give the Sound a try now.
If I record 2 channels with my mic, will that be a problem with the MLV_snd ?
You should Ok , but I didn't check on a 2 channel Mic.
:)
I tested the Dec 30 build with audio filming b camera for a live show for a friend- it seems to have come out OK, but the build is too buggy to use for any serious work- mostly that the global draw doesn't turn off and some recordings just stop instantly and require a camera reboot. Oct 24 is still the one to use, for professional paid work at least. Too many corrupted outputs on the new one, slower speeds, and random file stops for now for me to move to MLV.
Is it possible to use regular old raw with audio at some point?
Quote from: oddname on January 05, 2014, 05:36:50 PM
Is it just me having issues with the overlay dissappearing when recording, despite it isnt supposed too, then never returns until reset?
The framing etc is just gone, so dont really know where Im shooting.
I have the same issue with the latest build. Hope something can be done.
I am having trouble finding the answer to this question with in the forum. If the answer is right in front of my face I apologize. I am trying to get my live view to display as it does by default in magic lantern with the exposure readings and the colors beside iso and shutter speed. Is there a way to do this when using this module? Thanks for the help
for those having issues with overlays, framing guides and other info disappear when recording using MLV raw video. Go to MLV menu and turn DISABLE G.DRAW to ON.
I know, its mislabeled and I was wracking my brains as I thought turning it on would do as it say, but it actually does the opposite and DOES NOT turn Gdraw off when it is ON.
Hope a developer can change this. :)
Quote from: reddeercity on January 05, 2014, 11:37:32 PM
Here a short test with MLV+Audio on the nighty build form Jan.1st
with me talking and counting to Ten plus a short tutorial on how to setup
MLV with audio, on the 5D2 :)
Thanks for the Tutorial. Your only using the MLV-Rec and MLV-Snd module, Right?
Does it helps to limit the amount of module on the CF Card, I have the 32GB 1000x Lexar?
@dariSSight
your welcome, yes that right I just load modules for raw video.
I don't Do Photo's with my 5D2 just Video.
I don't think it matters one way or the other, just load them as you need them.
I like to keep thing very simple so I only load the Video modules.
Quote from: silvertonesx24 on January 07, 2014, 12:28:09 AM
I tested the Dec 30 build with audio filming b camera for a live show for a friend- it seems to have come out OK, but the build is too buggy to use for any serious work- mostly that the global draw doesn't turn off and some recordings just stop instantly and require a camera reboot. Oct 24 is still the one to use, for professional paid work at least. Too many corrupted outputs on the new one, slower speeds, and random file stops for now for me to move to MLV.
Is it possible to use regular old raw with audio at some point?
Try the mlv_rec.mo from the nightly build it's a lot more stable. I use the mlv_snd.mo from A.D. build Dec.30/13 & the rest comes from Jan 1st nightly build.
I didn't find any issue with MLV, I always have hdmi evf connected , yes its a little slower but that will get better.
I don't need any overlays so maybe that why it works for me. My Evf has all the overlays etc.. that I need.
Just wondering what's is your CF card what Frames size did you record in & the buffer fill method.
On MLV format?
Quote from: reddeercity on January 06, 2014, 06:00:58 PM
You should Ok , but I didn't check on a 2 channel Mic.
:)
Not sure if it was my mic or some setting, but set it to external stereo and found the volume to be very low compared to recording on internal.
Analog gaining added quite some noise. Digital... I just didn't wanna go there.
But alas, I am very grateful for just having sound now. For any shortfilm it will be extremely helpful with the internal mic for syncing too.
And I still need to learn how the different settings in the sound tab affects the sound. For instance Mic power ON lowers impedance ? not so sure what thats all about.
A new learning curve is growing :)
Quote from: ted ramasola on January 07, 2014, 02:16:49 AM
for those having issues with overlays, framing guides and other info disappear when recording using MLV raw video. Go to MLV menu and turn DISABLE G.DRAW to ON.
I know, its mislabeled and I was wracking my brains as I thought turning it on would do as it say, but it actually does the opposite and DOES NOT turn Gdraw off when it is ON.
Hope a developer can change this. :)
Nice find. I prefer global draw to be disabled while recording to squeeze every possible bit of speed and stability out of the camera. But when I toggle the option, global draw does indeed turn off when I start recording, but it does not toggle back on after I stop (I have to reboot the camera to get it back)
Quote from: reddeercity on January 07, 2014, 04:07:39 AM
Try the mlv_rec.mo from the nightly build it's a lot more stable. I use the mlv_snd.mo from A.D. build Dec.30/13 & the rest comes from Jan 1st nightly build.
I didn't find any issue with MLV, I always have hdmi evf connected , yes its a little slower but that will get better.
I don't need any overlays so maybe that why it works for me. My Evf has all the overlays etc.. that I need.
Just wondering what's is your CF card what Frames size did you record in & the buffer fill method.
On MLV format?
Yes- I have Komputerbay 64gb cards that will max out around 75MB/s or so. Aside from some annoying warm-up issues, they're generally very reliable. I record in 1856, 16:9. I dropped to 1728 1.85:1 halfway through the shoot though to get some more speed. I will try your suggestion for today's test shoot.
Here it is: my first movie that was entirely shoot RAW.
Beside the story and directing, I operated the camera completely myself. So, I got a feeling about how it is to go the RAW-way.
Enjoy:
The shooting time was around september last year with build 2013/09/04.
- 2.20:1
- 2 Lexar 1000x cards (32GB + 64GB)
- VAF-5D2b + several fixed ND filters
- I always tried to to exposure to the right (ETTR) as far as possible.
Also it was very time consuming to backup the cards after every 7 or 14 minutes of filming (backup took 20-40 minutes on my Laptop with external drive)
My six batteries were more than enough.
And I had no (real) problems with my two Lilliput HDMI-monitors.
I collected 1TB of just RAW-data and it several times took one complete day (!) to render the daily media (white ballenced and illumination corrected) via After Effects into ProRes4444 (witch I used to cut and grade, etc.).
On the other side: What came out is one hell of an amazing quality!!
It was absolute fun to do white ballence, grade, denoise, etc since there are no bandings and/or blocks from too much compression.
Just one thing:
Thanks to the ML-devs, I will definitely never ever have to shoot without RAW again!
Thanks!
Quote from: bnvm on January 02, 2014, 08:22:58 PM
I have been using the newest build for a little while and have noticed a few things. Sometimes the recording will start go a few frames and then freeze up, the buffer no longer fills and the number of frames recorded stays the same but it acts like it is still recording. I stop the recording and go into the menu the MLV Raw menu shows stopping... but never does. I have to turn of the camera to get things working again.
...
I experienced the same thing, but It's hardly to reproduce. I still don't get a trace log.
Quote from: oddname on January 05, 2014, 05:36:50 PM
Is it just me having issues with the overlay dissappearing when recording, despite it isnt supposed too, then never returns until reset?
The framing etc is just gone, so dont really know where Im shooting.
fixed!
Quote from: andyshon on January 05, 2014, 06:32:46 PM
Some stuff shot in crop mode. ...
Beautiful always! I think that the crop mode is made for nature documentary.
@reddeercity
Thanks David! I added your tutorial on the first page.
@ted
I renamed it and now you could use Global Off during Recording with crop mark
@silvertonesx24
more Speed in next release!
@guentergunter
It looks promising. I'll watch your short film in the evening!
Quote from: a.d. on January 08, 2014, 08:28:07 AM
@silvertonesx24
more Speed in next release!
I love the way you say "Speed"
thanks for the fixes A.D. ! Much appreciated!
Thank A.D.
I always have fun making tutorials about ML :)
Hi A.D and other developers for the 5D2 Raw video :),
I am a programmer/videographer and interested to help with the 5D2 build for raw video.
I got my devel environment and source ready.
Is there a list of bugs or things to improve I can begin working on?
Thanks :)
JP
Some ideas:
https://bitbucket.org/hudson/magic-lantern/issues
http://www.magiclantern.fm/forum/index.php?topic=9625
http://www.magiclantern.fm/forum/index.php?topic=7541
Basically, just look around for something you think you can improve, and give it a try.
Thanks a1ex :)
The Jan 6 a.d. version seem to have issues with the preview> HDMI framing experiment. The screen blacks out for a few seconds after every take.
The Jan 10 build looks promising. Even with HDMI attached + Snd enabled. I'm still testing more resolutions and combinations.
So far:
With an ext mic via pre-amp attached and audio set L-int R-ext. And HDMI monitor attached.
1728 x 972 16:9 /buffering-4 = continuous and audio sync ok (nudge audio track back 2 frames).
1856 x 928 2:1 /buffering-4 = continuous and audio sync ok (nudge audio track back 2 frames).
@A1ex,
Is it possible to make buffer graph option to work? even at OFF the buffering graphics is still on screen.
It is useful during testing but sometimes during serious work it gets in the way of framing. a.d.'s jan 6 build does not show the buffering by default but can be toggled on and off.
Of course it's possible, but these days I'm just giving a chance for novice developers to get started.
@guentergunter
great movie and I really enjoyed your film. My favourite character is Konrad 'caused of his dialect "Grummbeer". ;) I also like the backyard setup of the business man: Roman Venus, neo-classicism and the French formal garden => cliché! ;D
btw You are quite talented in story telling!
@jpleveillee
Thanks! Just create an account at bitbucket and give me a note!
Quote from: ted ramasola on January 12, 2014, 07:31:37 AM
The Jan 6 a.d. version seem to have issues with the preview> HDMI framing experiment. The screen blacks out for a few seconds after every take.
There is bug Global Draw doesn't go back after recording, so I need to refresh the LV! Hmm... maybe I'll do it only in "Preview: Canon"
I was doing some tests on sound sync and I loaded SND.mo and saw the meters come on upon checking my footage I was surprised not to see a WAV file,
I checked my cam and saw I missed turning MLV sound to ON in ML menu, - I see potential for trouble here when using this in a shoot.
Can devs tweak this to put safety nets?
Like, If MLV sound is not ON then Vu meters should not be active?
Or, you should not hear anything on your headphones when MLV sound is OFF.
or, when SND module is loaded, this should automatically turn ON MLV Sound by Default.
There is just too many "buttons to push" that the probability for error is high.
Quote from: a.d. on January 12, 2014, 08:58:05 PM
@guentergunter
great movie and I really enjoyed your film. My favourite character is Konrad 'caused of his dialect "Grummbeer". ;) I also like the backyard setup of the business man: Roman Venus, neo-classicism and the French formal garden => cliché! ;D
btw You are quite talented in story telling!
Thank you very much! I tried to realize and implement as much of what I know about film as possible (only limited by time and costs).
So, I'm glad you enjoyed it 8)
Glad to see you guys continuing to develop ML. Keep it up.
oooooooh new release!! :)
*installing*
edit:
First thing I noticed is that the white framing box is a little to the left. The left side of the white border disappears in to the end of the LCD, but is visible on the right side.
Just me?
Now to test speed!
Quote from: Kharak on January 14, 2014, 09:36:44 PM
oooooooh new release!! :)
*installing*
edit:
First I thing I noticed is that the white framing box is a little to the left. The left side of the white border disappears in to the end of the LCD, but is visible on the right side.
Just me?
Now to test speed!
i am testing right now. the writing speeds are jumping up and down. just a readout bug?
Quote from: ch_d on January 14, 2014, 09:48:54 PM
i am testing right now. the writing speeds are jumping up and down. just a readout bug?
Same here, jumps between 70-77 mb and then jumps down to 60 mb and then up again to the 70's. (don't see anything more extreme than that)
I get continues on all aspect ratios up to 1:85:1 (1872x1012). There I get 1:01, 1:04 and max 1:06 min. The expected frames goes quite quickly up to over 2000 frames, but when I reach close or around (sorry now I don't remember) 1200 I think, it stops.
When paning back and forth in 1:85:1, I get around 50-55 seconds.
Using Lexar 128 gb.
all in all! looks like a boost. But crop mode was terrible for me.
edit: Sorry, these were my settings:
Global Draw off while recording
Hacked2 Prev off
Extra Hacks ON
Buffer Method: 1 (all the others decreased the speed)
MLV sound ON (recording on internal mic)
This test was not done with cap on.
Can anybody give me a hint where i can find a tool for osx 10.8 to convert the MLV format to dng and sound. I really looked everywhere in this forum but couldn´t find a working solution...
QuoteWhen paning back and forth in 1:85:1, I get around 50-55 seconds.
Why would there be any difference if you move the camera? If it was any compressed video I would assume the bitrate to be higher if panning, but in RAW?
Im testing right now and got continuos recording in 1872x936 (2:1) with sound.
Global Draw: Allow
Preview: Auto
(didn't improve anything turning them off)
Transcend 64GB 1000x
Extra hacks on, card warmup (128 MB)
Global Draw OFF
Get 305 frames on max 1872x1054 (16:9) compared to 244 on last build (not very scientific, but anyway)
mlv_rec seem to perform better than raw_rec? (with raw rec I only got continous when using 2.20:1). Is it a different Buffer fill method? (4 seems to work best for me). Will do more testing.
Great work!
Quote from: poromaa on January 14, 2014, 10:53:33 PM
Why would there be any difference if you move the camera? If it was any compressed video I would assume the bitrate to be higher if panning, but in RAW?
Don't know, but I got less speed when I was panning. More pixels to be moved around and stuff I guess.. Also have had the same experience out in the field, where extreme moving could sometimes stop the recording. Maybe I'm just imagining all these things, who knows.
Btw, after recording and having GD off, it did not return. But if I click Canon menu button and exit again, the GD appears again. Was shutting down liveview before and turning it on again, to get it back. So thats a nice trick.
Quote from: ch_d on January 14, 2014, 10:47:53 PM
Can anybody give me a hint where i can find a tool for osx 10.8 to convert the MLV format to dng and sound. I really looked everywhere in this forum but couldn´t find a working solution...
I can't find the MLV Sharp or whatever its name was anywhere? Anyone know where the thread went?
http://www.magiclantern.fm/forum/index.php?topic=9560.0 But here is an extremely helpful tool, clean playback of RAW or MLV file.
Here's the link to the MLV browser and player that includes MLVviewsharp and MLVbrowsesharp.
http://www.magiclantern.fm/forum/index.php?topic=8447.0
Testing the new Build for Jan.14/14
There is more improvement in performance write speed, plus stable crop marks though
hdmi devices. No crashes of any kind.
I Thing thou, When I formated my card in Camera I lost all magic lantern software plus raw files.
Had to reinstall all ML software on card including making card bootable. But that was in Crop mode,
and never happen in non crop mode, So be careful on that!
Here are my numbers: With HDMI Evf connected:
1872x938 23.976p continuous
Audio=on 48kHz
buffer=1
GD=off
Preview=Hacked no prev.
Crop Mode:
1856x1004 23.976p Continuous
buffer=0
No HDMI devices:
1856x1004 23.976p--3880, 3913, 2200, 1720 frames
Audio 48kHz
Preview=ML gray
Crop mode:
2048x930 23.976p 3987 frames
buffer 0
2048x872 23.976 continuous
preview= canon
Things are improving very well,
A.D. is possible to have the Raw record info out side the white Rectangle Crop Mark.
I record the Live View and the info is just inside on the low left, if that could be drop
to the bottom of the LV screen then I could record it cleanly without turning
All overlays off and keep the info while recording raw. :)
@reddeercity.
not sure if this is what you did, but in older builds, if you recorded something and did not turn the camera off and on again before formatting, then it would delete all ml files
I confirm reddeercity's numbers. This last build is the step into continuous 2k video 2.35:1 24fps X5 crop for 5D2.
2048x872 exact 24fps continuous with sound 73Mbps_ish( lexar 32Gb 1000X ).
Thanks ML !
Quote from: ted ramasola on January 15, 2014, 01:23:26 AM
Here's the link to the MLV browser and player that includes MLVviewsharp and MLVbrowsesharp.
http://www.magiclantern.fm/forum/index.php?topic=8447.0
thank you.
Thanks for testing, guys!
Quote from: Kharak on January 14, 2014, 09:36:44 PM
...
First thing I noticed is that the white framing box is a little to the left. The left side of the white border disappears in to the end of the LCD, but is visible on the right side.
...
It's the new Global Draw LV Info (same for raw_rec)
Quote from: ch_d on January 14, 2014, 09:48:54 PM
i am testing right now. the writing speeds are jumping up and down. just a readout bug?
Two things: First the buffer is divided in slots, therefore it jumps between the slots. Second the on screen display isn't always accurate. It refreshes every second, 'cause I need to slow down the LV Info to squeeze some more speed.
Quote from: Kharak on January 14, 2014, 10:12:36 PM
...
all in all! looks like a boost. But crop mode was terrible for me.
...
Global Draw LV Info is currently not ideal. The Top Bar collided with the Bottom Bar.
Quote from: Kharak on January 14, 2014, 11:21:18 PM
...
Btw, after recording and having GD off, it did not return. ...
Preview: Auto or Canon
Quote from: poromaa on January 14, 2014, 10:53:33 PM
...
mlv_rec seem to perform better than raw_rec? ...
raw_rec is still have an edge. You might take a look at the version of 24th Oktober.
Quote from: reddeercity on January 15, 2014, 05:25:33 AM
...
I Thing thou, When I formated my card in Camera I lost all magic lantern software plus raw files.
Had to reinstall all ML software on card including making card bootable. But that was in Crop mode,
and never happen in non crop mode, So be careful on that!
...
There seems to be some tasks conflict.
@reddeercity
It's possible, but in this state I don't want to change too much code, cause of the compatibility.
@a.d.
It was no biggey that the GD disappeared after recording, as I found a way to quickly make it reappear. By pushing Menu button and exiting again. The canon menu, not ML menu.
But tried out with Canon Preview and it worked, so I'll just stick to that.
And I forgot to say thank you for your and the rest of the teams, hard work. I pretty much always record in 2:20:1 (1872x850) and having continues recording with GD on and sound on is a blessing! so.. Thank youuu! :)
A few things to mention:
After recording stops, the blue light stays on until I shut off the camera. (only me?) Don't think this was the case yesterday when I first tried the build.
Also not always that I get white cropmark when I turn on my camera and I need to restart to get it back.
One thing I miss now, since MLV_snd module, is the beep when I hit record. Even though I've got it ON in Audio menu, there is no beep when I hit record. Its very helpful for syncing video with sound in editing.
Edit: Did in-camera format and Firmware update. That got cropmark back and everything was back to normal. After a couple of takes, the blue light started getting stuck again, but cropmark remained.
Quote from: a.d. on January 15, 2014, 08:48:42 PM
raw_rec is still have an edge. You might take a look at the version of 24th Oktober.
I'm shooting a music video in the next two weeks and really want to use magic lantern.
Do you think it'd be better using raw_rec from Oct 24th or the newest mlv_rec?
I really appreciate your help. Thanks a lot so far.
Quote from: sebble on January 15, 2014, 10:38:31 PM
I'm shooting a music video in the next two weeks and really want to use magic lantern.
Do you think it'd be better using raw_rec from Oct 24th or the newest mlv_rec?
I really appreciate your help. Thanks a lot so far.
What aspect ratio are you aiming at?
What cards you got?
16:9 gets you half a min or more in Raw rec at max resolution with GD off.
If its a music video, I guess you wont be
needing sound recording, so raw rec will do just fine but 2:20:1 is continues with GD on and sound in this MLV build (if you got the right card).
If you wanna go with Raw_rec, then 24th oct build is best one.
my 5 cents.
Quote from: Kharak on January 15, 2014, 10:47:27 PM
What aspect ratio are you aiming at?
What cards you got?
16:9 gets you half a min or more in Raw rec at max resolution with GD off.
If its a music video, I guess you wont be needing sound recording, so raw rec will do just fine but 2:20:1 is continues with GD on and sound in this MLV build (if you got the right card).
If you wanna go with Raw_rec, then 24th oct build is best one.
my 5 cents.
thanks for the input
we'll be using two lexar 1000x 32GB and are aiming at 1.85:1 or 2.39:1 aspect ratio
yes audio is not a big deal
Quote from: reddeercity on January 15, 2014, 05:25:33 AM
Testing the new Build for Jan.14/14
There is more improvement in performance write speed, plus stable crop marks though
hdmi devices. No crashes of any kind.
I Thing thou, When I formated my card in Camera I lost all magic lantern software plus raw files.
Had to reinstall all ML software on card including making card bootable. But that was in Crop mode,
and never happen in non crop mode, So be careful on that!
Here are my numbers: With HDMI Evf connected:
1872x938 23.976p continuous
Audio=on 48kHz
buffer=1
GD=off
Preview=Hacked no prev.
Crop Mode:
1856x1004 23.976p Continuous
buffer=0
No HDMI devices:
1856x1004 23.976p--3880, 3913, 2200, 1720 frames
Audio 48kHz
Preview=ML gray
Crop mode:
2048x930 23.976p 3987 frames
buffer 0
2048x872 23.976 continuous
preview= canon
Things are improving very well,
A.D. is possible to have the Raw record info out side the white Rectangle Crop Mark.
I record the Live View and the info is just inside on the low left, if that could be drop
to the bottom of the LV screen then I could record it cleanly without turning
All overlays off and keep the info while recording raw. :)
I will install new update today, I was wondering how this build compares to the Oct 24, 2013 build? I will do some shooting for the next few days to setup for a project I will be streaming from my website.
Testing the last 2 MLV nightlies including the latest one from a.d., is it a current limitation for MLV raw with sound to stop at a little past 10 minutes?
I notice the buffer graphs seem to be managing it until past 10 minutes when it would say skip and recording would stop. tested different buffer methods at 1728 x 972 16:9.
35.9 gig seem to be the limit in my tests.(40859MB on the camera lcd )
Tested another resolution, 1728 x 864 and it went past 11 min but again it stops at 40918MB as indicated on the LV screen.
@Kharak
GlDraw goes back is intended on Auto and Canon, 'cause other Preview is for HDMI Device.
I could reproduce the blue Led (same on nightly build): Global Draw On during Recording - Preview : Auto, Canon and HDMI. (fixed in the next release)
@sebble
The 2 cards need to be ML bootable and copy all the settings ML>SETTINGS from one card to another.
2.35:1 // max Resolution 1880x800 // continuos OK
1.85:1 // max Resolution 1880x1016 // 1:30 to 3:00
Keep in mind 2:10min is already around 10000MB!
@ted
I don't have 64GB card so I couldn't help. I've just took a look at the code and they seems ok. Do you have a log file?
Right now, LV Info Top Bar and Bottom Bar is on my priority list.
Just did a quick test with MLV and audio again after a read Ted's post.
I did have a problem with recording.
1872x938 + audio + HDMI + headphones
Preview=hdmi
buffer=1
GD=off
9208 frames 26.8 GB then stop on my Lexar 1000x 64GB
Now this is where it get strange, :o I tried a smaller resolution
1856x928 + audio + HDMI + headphones
Preview=hdmi
buffer=1
GD=off
The Camera just stop recording after 40.7 GB & LV just froze up with the display
overlay, just like I pause the video.
press the start button and heard a beep then a Red error message " Audio Failed To Stop State 4"
14216 Frames ,69.5MB/s ,125ms/idle
I'll test again without HDMI devices attached and see if I get the same error.
Ok no hdmi MLV + Audio Same problem,
1856x928 LV froze at about 40GB same error message "Audio Failed To Stop State 4"
Tried different setting 1872x850 buffer=0 ,1% idle, 15,426 frames, 40.9 GB same thing.
So I tried one more test without Audio just MLV and it's not the Audio that's the issue
1872x938, mlv 14,024 frames , 40,854 GB , 127ms/idle same froze LV no error message.
It dose it with or without audio. I'll go back to a older build and see if its there too. :)
Edit:
when back to the MLV nightly build from Jan 1st/14 and the Sound module from A.D. Jan 14th build
And Not problem recording. First without hdmi device, 1856x928, buffer 1, audio 44.1 ,full card 60GB (continuous)
Then with hdmi , I had to drop frame size a little to get continuous. 1856x844 with audio buffer 1 full card 60GB.
I think there maybe some problems with crop marks on this new build, I'm sure this will be fixed .
@reddeercity
Which nightly did you go back to that goes more than 40gig? Its not clear in your post, Jan 1 or jan 14?
So you tested MLV_REC.mo from Jan 1 nightly with MLV_SND.mo Jan 14 from a.d and you get continuous more than 40 gig?
Quote from: ted ramasola on January 17, 2014, 03:16:31 AM
@reddeercity
Which nightly did you go back to that goes more than 40gig? Its not clear in your post, Jan 1 or jan 14?
So you tested MLV_REC.mo from Jan 1 nightly with MLV_SND.mo Jan 14 from a.d and you get continuous more than 40 gig?
Sorry , I when back to the Jan 1st nightly build
http://builds.magiclantern.fm/jenkins/job/5D2.212/157/artifact/platform/5D2.212/magiclantern-v2.3.NEXT.2014Jan01.5D2212.zip
Yes I got continuous with the nightly Jan1st And sound from Jan14 . full card 60GB with or without hdmi but with hdmi a little smaller size
to keep continuous as per my post. this was also with buffer at 1
Ok, thanks I'll make a confirmation test to compare with your results.
Ok, so here's my tests in terms of filling up a 64gig card.
All tests run at 1728 x 972 16:9 all tests run with MLV SOUND ON.
5D mkII
Jan 16 nightly
skip/stop at 10'7" 40,800MB (41 GB)
Jan 14 by a.d.
skips/stops approx 10 min 40,859MB
Jan 8 nightly
skip/stop at 10'6" 40,721 (41.4 GB)
Jan 6 nightly - MLV_REC + Jan 14 a.d. -MLV_SND
OK CONTINUOUS FILLS UP CARD.
Jan 6 a.d. all modules.
OK CONTINUOUS FILLS UP CARD.
Jan 6 a.d -MLV_REC + Jan 14 a.d. - MLV_SND, FILE_MAN, MLV_PLAY
OK CONTINUOUS FILLS UP CARD.
For reference from 7D tests.
Jan 16 TL
skips/stop at 10'11" 40,929MB (39.9 GB)
Jan 14 TL
skips/stops 10'10" 40,907MB (39.9GB)
Jan 9 TL
skips/stops 10'11" 40,929MB (39.9GB)
Jan 8 TL (incomplete audio features in Audio tab ML menu - did not run test)
Jan 7 TL
OK CONTINUOUS FILLS UP CARD.
Jan 6 TL
OK CONTINUOUS FILLS UP CARD.
@ted and @reddeercity
how does the camera feel and smell after such extensive testing?
most I've recorded was 30 gb and my camera was getting hot.
I would say the temp is not unusual.
@Kharak
I would say the same thing as Ted .
At 60GB Temp around 61-62 degree C
There is times it will spike to 68 degree C if I'm push it with multiplies card record with hdmi.
Stop for 5 -10 min cools down quickly . You will know when you camera to hot when it starts to have
functions error. :)
Quote from: ted ramasola on January 17, 2014, 05:16:18 PM
I would say the temp is not unusual.
I would even say: It's harmless!
Your sensor is build upon silicon transistors. And silicon can stand a lot of temerature (many hundred degrees). It's just, that components around (like housings, wires, etc.) will tire from too much heat.
But: Your camera has a build-in shut-down-safety-feature. And this feature starts long before the temerature becomes
really critical!
In other word: Don't worry! ;)
By the way: Transistors build into your computer operate all day long at temperatures beyond 50 or 60 degrees (irregardless normal cooling). And it does not harm them as well.
Dear a_d and fellas :)
Is it just me or is it like that for everyone that when you use Magic Zoom window during recording the writing speed is dropped to 20-22Mb/s from 64-70Mb/s?
This applies to at least builds from Oct-24, Dec-30 and Jan-14 which all of them I have tried. I have tried to solve this issue with reformatting the card multiple times and using different settings etc... So I am just not using MZ window during recording now, but the window would be very useful to have for refocusing during panning. Thanks :)
My setup:
Canon 5DMKII
Lexar x1000 64Gb
Modified settings:
Magic Zoom: F+HS, Med, TL, 2:1
Cropmarks: CINESCO2.BMP
FPS Override 23.976
RAW video: 1880x800
Aspect ratio: 2.35:1
Preview: Canon
Small hacks: ON
Thanks for the info guys, got a 128 gig card but dont think i'll ever record that long a take.
but good to know I got ability to do so.. Well except for the recent posts about the recording stopping prematurely at 10 gig or was it 10k frames?
Current builds stop at 40gig. A.d. 's Jan 6 MLV_rec.mo is ok. Non stop till card is full.
Folks, did you notice that files processed as a RAW + WMV package on the MLV Browser are more noiser after DNG conversion than files that are directly DNG + WMV! Or, is it just me?
Another thing, I just figured out how to get the MLV + sound thing going. Downloaded the latest build (19/01/2014) and replaced the mlv related files with the mlv module files. Ran the files through the MLV Browser and the rest is history. A few things that I have not been able to figure out still. When even I use RAW or MLV to record files, I am let down when there is no second chance - like going out with the kids and catching them playing and having fun. It happened yesterday and I just gave up on the whole thing and came back to the tried and trusted H.264 recording on my 5D3.
So my question - what is the most reliable and trusted fps, frame size, setting to record raw / mlv sound and video so that things always turn out as per expectation. I have 32GB Lexar 1000X, Komputerbay 128GB 1000X and Scandisk Extreme 95Kbps cards.
Next question - I have kept all the builds since the last 1 month or so. With the g3gg0's mlv module and the 19/01/2014 build in camera can I delete all the older ones from my computer.
Last question - what is the mlv_dump file used for?
Hey guys!
I am playing with mlv+snd and love it! Especially with Davinci Resolve the workflow got as easy as h.264 just a lot more powerful.
After processing the .mlv-file with the latest version of mlv_dump on my mac i always end up with wav-files that are a little bit longer than the raw-material and audio is not perfectly sync.
(http://up.picr.de/17096789id.png)
I use the latest a.d.-build from Jan 14. I do not use FPS-Override and Davinci Resolve is set to 23.976 fps.
Yes, its normal.
Almost always, nudge back the WAV track by 2 frames. Sometimes, but rarely, 3 frames. And the wav track is always longer by approximately 8 to 10 frames. Just cut it off.
If recording is cut abruptly, by say skip frames or card full. The characteristics of you file will be as follows.
The wav file will be much shorter.
The video file will have some missing frames in the tail end resulting in chunks of frames not continuous in number from the main video file. No biggie, just delete them in your timeline.
Quote from: Canon eos m on January 19, 2014, 09:38:34 AM
Folks, did you notice that files processed as a RAW + WMV package on the MLV Browser are more noiser after DNG conversion than files that are directly DNG + WMV! Or, is it just me?
I actually haven't but now you made me paranoid and have to go do a test.
Do you have any examples?
Quote from: reddeercity on January 18, 2014, 04:05:46 AM
@Kharak
I would say the same thing as Ted .
At 60GB Temp around 61-62 degree C
There is times it will spike to 68 degree C if I'm push it with multiplies card record with hdmi.
Stop for 5 -10 min cools down quickly . You will know when you camera to hot when it starts to have
functions error. :)
I'm want to do some test before I film a Economic Segment for a News show, I want to test out the MLV so I can use the Jan 6 build with Jan 14 MLV.SND? If I use .RAW I need to use Oct 24th build for Stability.
Quote from: dariSSight on January 20, 2014, 02:31:21 PM
I'm want to do some test before I film a Economic Segment for a News show, I want to test out the MLV so I can use the Jan 6 build with Jan 14 MLV.SND? If I use .RAW I need to use Oct 24th build for Stability.
That's right, Oct24th for .raw and mlv+audio jan14th for audio & jan 6th or any nighty built mlv_rec before that to jan1st. :)
I'm curious, do you use any add on gear e.g. evf , monitor, backup(hard drive recorder) etc. ?
I'm doing a beginners guides video for ML Raw/MLV+Audio on the 5D2, for "Newbe's" . I will be cover
everything from installing ML raw, straight thought filming , post & trouble shooting problems, and I just wanted some input for you ;D
That's goes for anyone, if you have some input for this I would like to hear from you.
Specially if you had problem installing or filming, Thanks
@Jerone
It's an expected behaviour, 'cause your settings max out the usage of CPU and Raw Buffer.
@ted
Thanks, atleast I know what caused the bug now!
@Canon eos m
MLVViewSharp is the gui + mlv_dump and mlv_dump is the programm ...
Did you already try following settings on 5D3?
HaCKeD ON
Card spanning On (CF+SD)
Memory Hack On
Small Hacks On
@pholler
It's possible to stop in synch, however it generates more CPU Load and Buffer Allocation, that means less writing speed. Currently the stop concept is sequential: the video and then the sound, so you'll get more audio data in general.
@dariSSight
Oct24 Raw: max file size is around 43GB and it fixed in the latest release.
@reddeercity
Tutorial: maybe a setup picture of HDMI Recorder + EVF?
Quote from: reddeercity on January 20, 2014, 08:25:20 PM
That's right, Oct24th for .raw and mlv+audio jan14th for audio & jan 6th or any nighty built mlv_rec before that to jan1st. :)
I'm curious, do you use any add on gear e.g. evf , monitor, backup(hard drive recorder) etc. ?
I'm doing a beginners guides video for ML Raw/MLV+Audio on the 5D2, for "Newbe's" . I will be cover
everything from installing ML raw, straight thought filming , post & trouble shooting problems, and I just wanted some input for you ;D
That's goes for anyone, if you have some input for this I would like to hear from you.
Specially if you had problem installing or filming, Thanks
I have monitors, rode mic and I'm looking into Hardrive offloads. I have a 7in Haier Monitor but I can't get an output from my Canon 5D Mark II. PLEASE PLEASE HELP!!!
if you don't use magic lantern, can you output to your haier monitor?
Quote from: dariSSight on January 21, 2014, 01:58:56 AM
I have a 7in Haier Monitor but I can't get an output from my Canon 5D Mark II. PLEASE PLEASE HELP!!!
I did some research, on this monitor and what I found was its only component (RGB) and not HDMI.
If that's right then you need a hdmi to component converter box ,did a quick search and found this
http://www.amazon.ca/dp/B004I4WUSE/ref=asc_df_B004I4WUSE2948802?smid=A1UBX6JTHXVTF5&linkCode=asn&creative=395393&creativeASIN=B004I4WUSE&tag=shopbotca-20
but its $99.0 It maybe better to look for a hdmi monitor.
What do you people think.
In 5DM2 RAW mode: does it make sense to go for negative digital gain (-0,3 for example)?
And should i film in 100 or 160 ISO steps?
Thanks
In movie mode RAW, 160 = 200 = 250.
Digital gain only affects the preview.
Quote from: a1ex on January 21, 2014, 09:21:53 AM
In movie mode RAW, 160 = 200 = 250.
Digital gain only affects the preview.
OK - So it makes no difference if i choose 160 or 200 or 250 (of course correctly exposed - ettr) ?
Quote from: reddeercity on January 21, 2014, 06:52:19 AM
I did some research, on this monitor and what I found was its only component (RGB) and not HDMI.
If that's right then you need a hdmi to component converter box ,did a quick search and found this
http://www.amazon.ca/dp/B004I4WUSE/ref=asc_df_B004I4WUSE2948802?smid=A1UBX6JTHXVTF5&linkCode=asn&creative=395393&creativeASIN=B004I4WUSE&tag=shopbotca-20
but its $99.0 It maybe better to look for a hdmi monitor.
I have HDMI monitors but I want to put the Haier on a rig but I use a HDMI monitor. I think the HDMI ON the 5D Mark II is an microHDMI input right?
Quote from: ted ramasola on January 21, 2014, 05:01:46 AM
if you don't use magic lantern, can you output to your haier monitor?
Checking, I will get back to you.
Quote from: dariSSight on January 21, 2014, 11:48:02 AM
I think the HDMI ON the 5D Mark II is an microHDMI input right?
it is mini hdmi not micro. micro is smaller than mini.
Make sure you use HDMI to connect to monitor not the AV out cable.
Quote from: a.d. on January 20, 2014, 08:40:28 PM
@Jerone
It's an expected behaviour, 'cause your settings max out the usage of CPU and Raw Buffer.
@ted
Thanks, atleast I know what caused the bug now!
@Canon eos m
MLVViewSharp is the gui + mlv_dump and mlv_dump is the programm ...
Did you already try following settings on 5D3?
HaCKeD ON
Card spanning On (CF+SD)
Memory Hack On
Small Hacks On
@pholler
It's possible to stop in synch, however it generates more CPU Load and Buffer Allocation, that means less writing speed. Currently the stop concept is sequential: the video and then the sound, so you'll get more audio data in general.
@dariSSight
Oct24 Raw: max file size is around 43GB and it fixed in the latest release.
@reddeercity
Tutorial: maybe a setup picture of HDMI Recorder + EVF?
Will try your suggested settings. Thx. One more thing, if I load the *.snd file on the module with the 20th Jan build on my 5D3 it crashes - over and over. How do I share the crash log with developers.
Hello guys,
How to get the "white rectangle recording frame" back?
I can not see the framing when using 2.35:1 mode, for example- like I used to.
Can't get a clear answer to this : does raw video + dual iso doable with 5D2 please ? My dual iso seems to be greyed out on live view and only active on photo mode.
Thanks and long live ML !
Quote from: piloui on January 24, 2014, 06:07:06 PM
Can't get a clear answer to this : does raw video + dual iso doable with 5D2 please ? My dual iso seems to be greyed out on live view and only active on photo mode.
Thanks and long live ML !
No, Dual Iso Video is not possible on 5dmkii but Photo mode is
How is this possible:
Adobe: What was your workflow strategy and which cameras did you use?
Lowe: The film is made up of very high-res, IMAX-quality timelapse raw files. I shot the majority of the film in 5.6K on Canon 5D Mark II but I knew I couldn't do the whole film in timelapse. I needed 40% of the film to be beautiful slow-motion shots, and shooting 4K and 5K on RED cameras was the answer.
And I wanted to finish the film at 4K resolution. When I started two or three years ago, people said I was completely nuts. It wasn't possible to finish at 4K. It wasn't necessary, and so on. But I knew that if I was going to spend that much time in the field, I had to finish it in 4K.
Tow Lowe's full interview on: http://blogs.adobe.com/aftereffects/2013/01/tom-lowe-breaks-technological-and-creative-bounds-with-timescapes.html
It was time lapse footage, he shot raw photos, cr2, and made a movie from that. There is no way it could be raw video.
Quote from: bnvm on January 24, 2014, 10:12:29 PM
It was time lapse footage, he shot raw photos, cr2, and made a movie from that. There is no way it could be raw video.
:o
Quote from: Canon eos m on January 19, 2014, 09:38:34 AM
Folks, did you notice that files processed as a RAW + WMV package on the MLV Browser are more noiser after DNG conversion than files that are directly DNG + WMV! Or, is it just me?
I tested it and I do not see any difference.
It might be your mlv/raw converter that does not handle both aswell. What converter are you using?
Tested the Jan 25 Nightly and heres my test.
With MOVIE RESTART=ON MLV raw video will not stop recording. If you press SET to stop, it will start by itself.
This issue is not present with older builds like the Jan 6th NB and by a.d.
This is suppose to be active in H264 recording and should not have an effect in Raw recording.
HDMI MONITORING TEST
Tested playback functionality.
Immediately after recording a raw clip, I went to File manager> view mlv file.
Playback of COLOR or FAST was possible and it showed on HDMI monitor.
However after EXIT of mlv playback screen went Black and no function possible.
Had to remove battery to reboot camera.
On Older build using Jan 6 nB or A.D. Playback was possible and EXIT from playback was OK,
liveview came back and additional recording was possible.
CAPACITY BEYOND 40GIG TEST
Jan 25 Nightly build will still skip and stop approx, 39GB (Canon menu), 35.9GB (PC properties, 38,582,760,448 bytes)
The Jan 6 NB and by A.D. does not have this issue and will record till your CF card is full.
NBs after Jan 6 up to the 25th will Stop at approx that size or around 10minutes.
Ted, also to add if the raw video is taken when the sd card is the preferred card, the camera hangs. This is technically a glitch.
While I understand you can set your preference and all but I am sure there is a programming way to prevent the sd card from leading when it clearly is not meant to.
My take is that it will discourage mass adoption of the ML platform small things like these are not addressed. Pretty much like texting changed for ever when predictive texting was introduced.
Quote from: Canon eos m on January 26, 2014, 05:56:12 AM
Ted, also to add if the raw video is taken when the sd card is the preferred card, the camera hangs. This is technically a glitch.
This is a 5DmkIII specific issue then. Considering the devs maintaining this thread is focused more on the MkII, And there are others on the mkIII and others on the MLV module also, I duplicated this report on the MLV2.0 thread as well. Perhaps you should also post it there.
http://www.magiclantern.fm/forum/index.php?topic=7122.msg98039;topicseen#msg98039
Quote from: reddeercity on December 28, 2013, 12:57:14 AM
Hello, You are close but that's not the one I use
I use the one From A.D.'s Special Hack build for the 5D2
It the one with the disclaimer about Hot pixels .
This build is a lot faster then the vanilla (plane Jane) build that you are referring to.
Go to the first link read the disclaimer about hot pixels, (I don't think too many people even have this problem)
Then go to the second link, with the Oct 24th build.
Link below
https://bitbucket.org/a_d_/laboratory/wiki/Home
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
There is also better hdmi support with A.D.'s Hack Build which is very
critical for backup thought a hdmi recorder on paid jobs. (I use a Ninja hdmi recorder).
I always get about 15-20% more performance but on Lexar 1000x cards only,
I'm not sure if the Komputerbay 1000x cards are as fast, I have heard there is problems with them.
I hope this info helps, ;)
PS. I have being only using A.D. hack builds since June of this year
and never had a problem once !
Damn it!!
Hot pixel problem....
I shoot with the Oct 24th build (Trancend 1000x 32gb) then hot pixel or green dot whatever it calls occurred to me..
(http://www.magiclantern.fm/Users/tetsushiwakasugi/Desktop/140125.Still002.jpg)
I did sensor cleaning like this forum said
Step 1 Detach the lens from your Canon camera and use the cap
Step 2 Turn your camera on. Go to the menu and select "Sensor cleaning" under the utilities menu.
Step 3 Turn the dial to select "Clean manually" under the sensor cleaning option.
Step 4 Turn the dial to select "OK" and then press the "Set" button. The mirror will lock up and the shutter will open. Allow the shutter to remain open for at least 30 seconds.
Step 5 Turn your camera off and reattach the lens. Take a few test shots to see if the problem has been corrected. In most cases the red or white pixel will no longer be a problem because your camera has been remapped
If it does not help the first time, then change the ISO settings and try again.
But it didn't help.
togg says that you can use pencil correction on ACR. so there's no problem. Someone got helped from it.
What does pencil correction on ACR exactly mean??
What's ACR stand for??
Many people do not have this problem cuz different CF card they use or any solution for this?
If anyone fix this problem, please let me know
Thank you.
Quote from: philostory on January 26, 2014, 09:59:40 AM
Damn it!!
Hot pixel problem....
I shoot with the Oct 24th build (Trancend 1000x 32gb) then hot pixel or green dot whatever it calls occurred to me..
(http://www.magiclantern.fm/Users/tetsushiwakasugi/Desktop/140125.Still002.jpg)
I did sensor cleaning like this forum said
Step 1 Detach the lens from your Canon camera and use the cap
Step 2 Turn your camera on. Go to the menu and select "Sensor cleaning" under the utilities menu.
Step 3 Turn the dial to select "Clean manually" under the sensor cleaning option.
Step 4 Turn the dial to select "OK" and then press the "Set" button. The mirror will lock up and the shutter will open. Allow the shutter to remain open for at least 30 seconds.
Step 5 Turn your camera off and reattach the lens. Take a few test shots to see if the problem has been corrected. In most cases the red or white pixel will no longer be a problem because your camera has been remapped
If it does not help the first time, then change the ISO settings and try again.
But it didn't help.
togg says that you can use pencil correction on ACR. so there's no problem. Someone got helped from it.
What does pencil correction on ACR exactly mean??
What's ACR stand for??
Many people do not have this problem cuz different CF card they use or any solution for this?
If anyone fix this problem, please let me know
Thank you.
Hot pixels do not have anything to do with CF card. Its the sensor.
ACR stands for Adobe Camera Raw. If you have After Effects and import a DNG sequence then ACR will automatically open with the first DNG image of your sequence.
The Pen tool, is basically a "corrector", you place a point on the hot pixel and choose another spot, if possible, right beside the hot pixel and then ACR will make the hot pixel area "disappear" and look like the other spot.
This will most likely have to be done frame by frame, which is a very time demanding job, but it gets rid of the problem.
sorry hungover
Quote from: Kharak on January 26, 2014, 07:28:10 PM
Hot pixels do not have anything to do with CF card. Its the sensor.
ACR stands for Adobe Camera Raw. If you have After Effects and import a DNG sequence then ACR will automatically open with the first DNG image of your sequence.
The Pen tool, is basically a "corrector", you place a point on the hot pixel and choose another spot, if possible, right beside the hot pixel and then ACR will make the hot pixel area "disappear" and look like the other spot.
This will most likely have to be done frame by frame, which is a very time demanding job, but it gets rid of the problem.
sorry hungover
Thank you for details about hot pixel but...
That's the only way I can fix it??
Does anyone solve this problem without retouching one by one??
Thanx
Been away a few months and come back to see the build has leaped, im on 24th Oct build, is latest build worth moving too? really like 24th oct :)
Cheers!
jan 6th, a.d. will give you stable MLV recording with sound and can fill up your CF card.
The ones after 6th up to latest jan 26th? has issues and will stop at 40gig or 10min.
You can also view via HDMI (GD off) and preview using file man on hdmi.
If you remove hdmi monitor, reboot camera to restore live view.
Quote from: ted ramasola on January 28, 2014, 12:36:35 AM
jan 6th, a.d. will give you stable MLV recording with sound and can fill up your CF card.
The ones after 6th up to latest jan 26th? has issues and will stop at 40gig or 10min.
You can also view via HDMI (GD off) and preview using file man on hdmi.
If you remove hdmi monitor, reboot camera to restore live view.
I will shoot some commentary video today, I'm planning to shoot with the MLV. So MLV is just as much the .RAW file but it's with more organization with metadata and easy viewer format for Exclusivity to Magic Lantern?
Yes MLV is magic lanterns own format but the raw video is the same as it was in the older raw format. MLV has more meta data, audio, card spanning on the MKIII, etc... However I would say that MLV is not a stable as raw, I am running into some little bugs like the camera hanging, missing frames in the middle of a sequence, audio that is shorter than its video, and recently I had 14 GB worth of video clips that had no audio at all, probably 20 different shots all on one card. At this point I would be hesitant to use it for paid work.
Quote from: bnvm on January 28, 2014, 06:43:58 PM
I am running into some little bugs like the camera hanging, missing frames in the middle of a sequence, audio that is shorter than its video, and recently I had 14 GB worth of video clips that had no audio at all, probably 20 different shots all on one card.
On the mkII? What MLV version did you use that you experience this? What settings did you use, like resolution etc?
I'm trying to compile the report to devs on the nightly builds having problems.
As I posted earlier, jan 6 is stable on my tests.
It doesnt help just saying its not stable without a specific report on what build and settings you use.
I also experienced having shots without audio, but I realized it was my fault having failed to turn on MLV Sound in the menu.
I suggested devs turn off the audio meters when MLV_snd.mo not turned ON so it gives the user a hint.
He (bnvm) must be talking of the 5d3 , I don't see these issue on my 5d2 with mlv+audio
on nb build Jan1st plus sound from Jan14th.
Its rock solid , just I bit slow :)
Cheers guys! will test some firmwares soon :)
let me update my tests results so devs can also narrow down any fixes and users know what to use.
You can use a.d build Jan 14 for everything EXCEPT MLV_REC.MO
Use a.d. build Jan 6 for MLV-REC.MO only. (later builds of mlv_rec.mo will stop at 10 min/40gig)
The Jan 14 build has fixed issues in playing back MLV files in-camera like when playing back a mlv file you get "building index" freeze/lock up.
Quote from: ted ramasola on January 28, 2014, 06:54:04 PM
On the mkII? What MLV version did you use that you experience this? What settings did you use, like resolution etc?
I'm trying to compile the report to devs on the nightly builds having problems.
As I posted earlier, jan 6 is stable on my tests.
It doesnt help just saying its not stable without a specific report on what build and settings you use.
I also experienced having shots without audio, but I realized it was my fault having failed to turn on MLV Sound in the menu.
I suggested devs turn off the audio meters when MLV_snd.mo not turned ON so it gives the user a hint.
I am using the Jan 14th build from a.d. I have experienced all of these except for the audio problems on earlier builds including the nightlies. So far these occurrences seem very random and fairly rare, I cannot pinpoint any specific trigger. I have filed some bug reports but I have no idea how to reproduce any of them. I am shooting either 1728 x 1036 or 1728 x 934 at 23.976 (no fps override), I have global draw on with digic focus peaking and magic zoom enabled. I believe I was using buffer fill method 2. Also all of the missing audio clips were from one card which had no audio on any shot, when I switched to a different card the remaining shots all had their audio.
One unrelated question does MLV audio work with FPS override enabled? I tried it when I first switched and it didn't buy I may have done something wrong.
I always have fps override enable at all Times .
I use NB Jan 1 & sound from A.d. Jan 14
And global draw off when recording mlv+audio
But I use hdmi, Evf 1856x928 2:1 23.976p fps
My buffer is set to 1, I have notice that , 0 or 1
Seemed to be the fastest 2-4 stop recording after
A minute or less.
:)
Quote from: bnvm on January 29, 2014, 05:20:47 PM
One unrelated question does MLV audio work with FPS override enabled? I tried it when I first switched and it didn't buy I may have done something wrong.
I use FPS override all the time too. What happens, for some unknown reason, is that the live level metering doesn't work in that mode. I can assure you though that
it will still record the audio, just without being able to see the recording levels.
It's an annoyance, I know but;
it will record. I am sure that some time this will be resolved. (hopefully anyway!) ;) :D
While its ok NOW to use FPS override when using MLV since WAV is still recorded, its also ok NOT to use FPS over ride if;
Your shooting in 1X normal mode at 24fps in the canon menu. (fps override not needed)
USE FPS Over ride only if your using 3X crop mode since canon defaults to 30 fps so ML can overide this by setting 23.976 or 24 in FPS override function.
I've tested several times filling up 64gig cf with slated (head and tail) 15min(approx) footage to see if there is drift in sound and I see none even with no fps override.
Additional resolutions Ive tested that works with MLV+Sound are.
1856 x 928 2:1
Buffer-4 / With HDMI mntor / ext mic / headphones : Continuous till card full
1728 x 972 16:9
Buffer-4 / With HDMI mntor / ext mic / headphones : Continuous till card full
1728 x 1036 5:3 is not reliable using buff- 1 or 4
I have my Live View/Movie func. set. set to 1920x1080 @24
I turned my FPS override off and it sets the recording at 23.976. I can't work at that FPS.
Recording at 1872x1054
So what's happening there?
in normal mode? or crop mode?
The 5D does not do 1920 x 1080 in normal mode.
Widest is 1872.
Normal (the 1920x1080 was the setting from the canon menu!)
1872x1054 in ML
Quote from: mageye on January 29, 2014, 10:21:20 PM
I have my Live View/Movie func. set. set to 1920x1080 @24
I turned my FPS override off and it sets the recording at 23.976. I can't work at that FPS.
Recording at 1872x1054
So what's happening there?
you will not get very many frames at 1872x1054 maybe 30 second to 1 min
and that's a Big Maybe !
You might get 1872x1012 for about 1-2 min. Better chance at 1856x1004 but without any hdmi.
The max sensor size on 5d2 is 1880x1250, to get 1920x1080 in the Canon menu
canon upscale the image for h264.
@ted; do you get the same full card record with buffer at 0 or 1, or just at buffer 4
I can only get continuous at buffer 0 or 1, at buffer 4 my Lexar records for about 2 min then stop.
Just wondering , it my be the different between card brands.
@reddeercity
I think people are getting some wires crossed here!
First of all I was questioning what Ted was saying about turning off FPS override. In my experience, if I don't have FPS override turned on it will record at 23.976.
I work with 24 FPS that's the speed that I want to work at!
I am fully aware ;) of how long I will be able to record video for and at which resolutions. If I wanted continuous recording I would drop the resolution a touch. This is fine if you are doing long takes where you might need to be talking to the camera etc.
It all depends on the type and style of production you are doing. Watch any advert and you will notice that each cut lasts only for a very short time (a few seconds for example).
Many commercial (and non-commercial) films have very short cuts. Anyway that wasn't what I was questioning!. I was merely stating that if I turn off FPS override and I have my canon settings set to 1920x1080 @24 (from the canon menu) and the mentioned 1872x1054(ML menu) (it doesn't seem to make any difference what resolution this is set to either), it will record at 23.976.
So despite what Ted is saying, I will continue to use FPS override because without that I am not getting the 24 FPS that I require.
Ted was responding and then went offline so it never really got clarified. I am sure he will answer when he is around again. If he knows better I am sure he will let me know! ;)
@mageye
The 5d mk II's max resolution is 1880x1058 or some close to that.
Those 20 missing pixels were upscaled in camera before ML Raw came along.
I got what mageye is asking for, its not about resolution, its about getting exact FPS. I just finished testing it on the MLV module as I also noticed some repeating frames especially at 1FPS.
Give me a sec to check the tests i just made.
@ted ramasola
Correct!!! ;)
This all stems from me pointing out that when you use FPS override you lose the audio level meters (and no it's nothing to do with resolution!)
@mageye.
@Devs ( g3gg0, 1%,a.d. and the rest )
Tested FPS override and the audio meters does disappear.
We can try to request devs to tweak this, this is probably not updated since when FPS OR was made it was still h264 and it could not record audio, so it disapears.
I had an issue once where i failed to record sound in MLV raw when I missed to turn on MLV Sound since the audio meters was there(fps OR was off), I thought soiund was ON due to the active audio meters but in fact it was OFF.
Since MLV can now record sound AND fps override works with the sound module I hope they can;
1.) allow audio meters to show IF MLV Sound is ON and to disappear if MLV Sound is OFF
2.) if MLV rec or RawRec not loaded to behave as expected in h264 recording.
On FPS
@devs,
all settings are functioning from 24 to 2 FPS, there is a bug in 1FPS as a frozed frame alternates throughout the recording.
@mageye,
with FPS at 24 you can set the appropriate setting in your NLE to reflect this and you get the right framerate, I was testing recording a digital timer and its accurate.
I tested if i can conform the framerates from 24, 23.976 , 10, 5 up to 1 etc. And upon telling the NLE to interpret the DNGs the true framerate during recording, it hits the time markers accurately. The sound though is locked at what canon framerate was set at. But of course if you use this for ads then you have a 2nd system for sound and the mlv sound is just a scratch track.
@1%
tested jan 29 nightly and there is something really wrong with it as it cannot record past 3 seconds max, sometimes just 1 sec, depending on the buffer method.
I gotta ask again. Several pages ago I asked the same thing.
Its regarding crop mode and the black edge I get. It's not that I use it that often, but it would be very if I got it to work properly.
I've done complete re-installs and then it works for like a day or maybe just one or two takes then the blackedge returns. This has been on every single build I've tried.
See dng: https://www.dropbox.com/s/szlkhtc9nagsjsp/M26-1648-000004.dng
Does anyone else experience this and do you know how to fix it (for good)?
Kharak.
Quote from: Kharak on February 03, 2014, 03:17:00 PM
I gotta ask again. Several pages ago I asked the same thing.
Its regarding crop mode and the black edge I get. It's not that I use it that often, but it would be very if I got it to work properly.
I've done complete re-installs and then it works for like a day or maybe just one or two takes then the blackedge returns. This has been on every single build I've tried.
See dng: https://www.dropbox.com/s/szlkhtc9nagsjsp/M26-1648-000004.dng
Does anyone else experience this and do you know how to fix it (for good)?
Kharak.
Nice shot, Yes I get that black edge on the right also, at 2152x#### in crop mode but in older builds
with the 1880 enabled , Never notice in MLV thou, is this on the older raw format ?
In the latest MLV nightly build feb,2 in crop mode the max size is 2144x####,
So I think it must be that ML is capturing a bigger area then the crop window is displaying.
I guess just crop it out that's what I use to do, but now I just use 2048x#### .
Yeah, I get the same in cropped 2144 x 1076.
Fine in 16:9 1856 x 1044.
Quote from: ted ramasola on January 30, 2014, 04:36:16 AM
(...)
@devs,
all settings are functioning from 24 to 2 FPS, there is a bug in 1FPS as a frozed frame alternates throughout the recording.
(...)
Maybe the duplicate first frame old issue? (not fixed yet BTW)
-> https://bitbucket.org/hudson/magic-lantern/issue/1755/duplicate-first-frame-with-low-fps
perhaps, had same problems on 7D but as I reported it in the TL thread this was fixed in the Feb 1 nightly for tragic lantern. This is still present even with Feb 3 ML nightly for the 5D2.
Quote from: reddeercity on February 03, 2014, 08:20:40 PM
Nice shot, Yes I get that black edge on the right also, at 2152x#### in crop mode but in older builds
with the 1880 enabled , Never notice in MLV thou, is this on the older raw format ?
In the latest MLV nightly build feb,2 in crop mode the max size is 2144x####,
So I think it must be that ML is capturing a bigger area then the crop window is displaying.
I guess just crop it out that's what I use to do, but now I just use 2048x#### .
That was shot on raw rec.
I did a test right now and got black edge on 2048 and 2144, mlv. Did not do complete re-install
but went through an older harddrive and looked at some dng's and saw that some shots, shot at 2048x### and 1920x### were fine. raw rec
I am still quite sure that I got it to work once on 2152. But I also remember a.d. giving me a link once for a nightly that addressed something specific in crop mode. So I am not sure exactly if perhaps it was that nightly that did it that one time or what.
ps. I usually crop out the black edge if I have to use the shot, but just annoys me that I am actually squeezing the aspect ratio to fit.
Testing FEB 3
#1. Low FPS freeze frame still there. If using 1FPS and lower there is a frozen frame that repeats alternating between normal frame. (already fixed in 7D build)
#2. Sometimes in file manager can't view spanned files. Getting "Invalid Header Size" then show "file ends prematurely during block header."
#3 Crop mode. Borders & Overlay info takes a long time to appear when recording is started.
#4 Screen refresh takes a long time after recording is stopped.
#5 Is it possible to implement the Full time Color preview for 5D2 Crop mode ? this is now implemented in 7D and its very useful especially in focusing. Currently we can see it by half press of the shutter while in crop mode.
#6 can we now place a toggle switch for the buffer display that shows while recording? A.D's builds have removed this and I hope the nightlies can also give us option to turn it off.
#7 can he have audio meters when FPS over ride is active for MLV video?
#1. Pull request please.
#2. sounds like a MLV-specific issue rather than a 5D2 issue
#5. Press shutter halfway.
#6. Pull request please.
#7. Already answered in the MLV thread.
@ A.D. Great Job !
The new mlv build, at lest with the hack crop view build,
is very fast :) I was able to maintain around 73MB/s
at 1872x936 23.976p 2:1 A.R. fps override=on, GD=off around 49GB, 17,294 frames + Audio
with hdmi preview, buffer 1. But not with any hdmi device connected.
when you return for recording the ML overlays come back without refreshing LV.
With hdmi, 1856x928 23.976p + audio, buffer 0, 19,829 frames 55.9GB
No cashes or lockups with hdmi , ML overlays returned to LV.
Crop mode 1920x960 23.976p + audio, buffer 1, hack view preview
8200 frames, 24.5GB,
2048x872 23.976p + audio, buffer 1, Continuous 20,227 frames, full card (64GB)
No error or problems, 2 thumb up !
I like the new look of the info bar at the bottom of screen & small text (I use the 4:3 screen auto layout).
Things are looking very good, ;D
Testing Feb 4th by a.d.
1. Can the "Frames recorded" be made to disappear faster? If its not connected to the the writing time from buffer to CF then this could also be removed altogether?
2. Low fps freeze frame not yet fixed.
3. Request for Full color preview in crop mode which is currently via half press of shutter to be implemented in menu as start and stop via set does not work if I use Sticky half shutter.
I did experience a lock up when I tried to view a file with HDMI attached. Had to do a battery pull and reboot.
I also like the layout tweaks. Getting similar results like reddeercity's tests as well.
Quote from: reddeercity on February 05, 2014, 04:23:34 AM
(...)
The new mlv build, at lest with the hack crop view build,
(...)
Nice feature, but isn't better to see what is out of the record field?
Beside, just some feedbacks about the mlv_snd.mo: I was like Doyle4 _stayed with the 2013-10-24 a.d. build_ and want to try the new feature with sound recording in RAW video.
So I'v installed the 2014-01-14 a.d. build -> mlv_rec, mlv_snd loading etc. but no .wav recorded. I'v tried many configs, always no sound recorded.
Next I'v tried the last 2014-02-05 a.d. build -> same thing.
Maybe something is wrong somewhere, so I use the debug module feature to see what's wrong: I saw something about 'config can't be saved' in the console during a fraction of second and crash with battery drain to the death plus ' ghost things' (menu, crop frame, typos, etc.) stay printed in the screen during several minutes after unstuck the camera (gloops!).
End of the story. Gone to test last NB to try mlv_rec + w$ browser.
Quote from: SpcCb on February 05, 2014, 06:24:18 PM
Nice feature, but isn't better to see what is out of the record field?
Beside, just some feedbacks about the mlv_snd.mo: I was like Doyle4 _stayed with the 2013-10-24 a.d. build_ and want to try the new feature with sound recording in RAW video.
So I'v installed the 2014-01-14 a.d. build -> mlv_rec, mlv_snd loading etc. but no .wav recorded. I'v tried many configs, always no sound recorded.
Next I'v tried the last 2014-02-05 a.d. build -> same thing.
Maybe something is wrong somewhere, so I use the debug module feature to see what's wrong: I saw something about 'config can't be saved' in the console during a fraction of second and crash with battery drain to the death plus ' ghost things' (menu, crop frame, typos, etc.) stay printed in the screen during several minutes after unstuck the camera (gloops!).
End of the story. Gone to test last NB to try mlv_rec + w$ browser.
The camera does not record a separate .wav file, it is stored inside the mlv file and u will need mlvbrowsesharp to extract the wave file
edit: solved
Quote from: Kharak on February 05, 2014, 07:11:48 PM
The camera does not record a separate .wav file, it is stored inside the mlv file and u will need mlvbrowsesharp to extract the wave file
Ah! (shame on me) I did not figure that the .wav was in the .mlv.. Thanks Kharak.
Note on the mlv snd wav file for Feb 4 build by a.d.
If you stop recording manually your WAV file would "normally" by longer than the video file by 7-10 frames -which is fine.
However, if you keep on recording till Card is full, and the recording abruptly stops on its own, the resulting WAV file would be significantly shorter than the video file from 10 seconds to more than 1 minute.
Can we place safeguards on this behavior? perhaps based on CF capacity, the recording should stop safely?
Hi, would anybody know which is the latest build that allows 1880x800? I am using a 16Gb Lexar 1000x.
Thank you to all the developers for your tremendous work.
I believe 1880 is no longer available in the current builds at 1x.
You can do 1872x936 2:1, thats close to what your looking for.
or 1856 x 928 2:1.
1728 x 972 at 16:9.
These are tested to be continuous with sound, with HDMI monitor, with external mic, with headphones.
Hello guys,
I'm an Italian filmmaker and this is my first post.
I apologize now for my bad English ( Google translator is helping me ) .
Only a few months ago I became aware of the Magic Lantern. I have read , and read many of your posts and forums about all the great features, such as shoot in RAW , and I also tried it on my 5D m2.
It is absolutely fantastic. By now I had become accustomed to the standard quality of this camera, but after installing ML ... surprise ... it is as if I walked into a store and I bought a new
camera, but not any ... a camera that can do the miracles, and who also works in RAW !
I want to say : Thank you ... thank you ... thank you ... thank you ... also on behalf of all the Italians who are using ML , (although I do not know them ) , and that they do not even thank
(classic behavior of Italian people ) .
Thank you sincerely to all developers with their ability and patience have succeeded, and continue to do something truly " apocalyptic " .
You've managed to squeeze this camera until the last drop, and now they're coming also the seeds :)
I can assure you , when I will do that as my next job with the help of ML , I will send a good donation. You deserve it!
If I may, I would have just a few brief questions that I could not answer on forums, maybe for my bad english:
1 - I've noticed that when I shoot in RAW mode, increases the alias effect (moire), there is a way to reduce this, or is it strictly necessary to use the VAF Filter?
2 - I did not understand the difference of filming in RAW or MLV. Is this only for MAC? (I use windows)
3- I am currently filming with an old build that allows me to 1880 x 1016 (11/16/2013 d84b9cd9e86f build) and I'm finding it fine without audio. But I saw that for some time there is no longer a build that goes up to 1880. It 'was removed this option because it is dangerous for the camera?
4- When I shooting with 5x magnification, (you always talk about 3x magnification) for example 1880 x 1058 for a few seconds, when I import this in AE, I see that the size of the frame is always 1880 x 1058, and not highest as I read in the forums or in this table:
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5
It is a my mistake? Maybe I did not understand well how is shooting in crop mode?
if these questions are too stupid, please no one responds :)
Thanks again for everything.
Giacomo
@giacomari
1.) The moire was always there it was just covered up somewhat by the h264 compression, the only way to reduce this is with a VAF Filter or shoot in crop mode as it doesn't have this problem.
2.) MLV is a new container for holding raw data with extra features like audio and meta data. The raw data is the same with both RAW and MLV. MVL is just a file format so it works on all windows, MAC and Linux(I think), there are some tutorials around that go through the process of using MLV and RAW as well.
3.) The newer builds merged in MLV and as a result some of the custom additions that a.d. added are no longer there since his was/is a custom build. The reason why 1880 is not there is because only the 5D2 can use it, the other cameras don't work well with it so it was not included to keep things consistent across all cameras.
4.) The size of the image you can shoot in crop mode is different than in non crop. Specifically you can shoot higher resolutions horizontally but lower resolutions vertically. The 1058 is probably the max possible height in crop.
Quote from: bnvm on February 06, 2014, 08:12:24 PM
@giacomari
1.) The moire was always there it was just covered up somewhat by the h264 compression, the only way to reduce this is with a VAF Filter or shoot in crop mode as it doesn't have this problem.
2.) MLV is a new container for holding raw data with extra features like audio and meta data. The raw data is the same with both RAW and MLV. MVL is just a file format so it works on all windows, MAC and Linux(I think), there are some tutorials around that go through the process of using MLV and RAW as well.
3.) The newer builds merged in MLV and as a result some of the custom additions that a.d. added are no longer there since his was/is a custom build. The reason why 1880 is not there is because only the 5D2 can use it, the other cameras don't work well with it so it was not included to keep things consistent across all cameras.
4.) The size of the image you can shoot in crop mode is different than in non crop. Specifically you can shoot higher resolutions horizontally but lower resolutions vertically. The 1058 is probably the max possible height in crop.
Great answers it made me a little more informed on the world of Magic Lantern RAW. Shoot in Crop mode you said will eliminate most Moire errors, but doesn't that bring the image too close for frame accuracy?
Quote from: giacomari on February 06, 2014, 05:08:40 PM
Hello guys,
I'm an Italian filmmaker and this is my first post.
I apologize now for my bad English ( Google translator is helping me ) .
Only a few months ago I became aware of the Magic Lantern. I have read , and read many of your posts and forums about all the great features, such as shoot in RAW , and I also tried it on my 5D m2.
It is absolutely fantastic. By now I had become accustomed to the standard quality of this camera, but after installing ML ... surprise ... it is as if I walked into a store and I bought a new
camera, but not any ... a camera that can do the miracles, and who also works in RAW !
I want to say : Thank you ... thank you ... thank you ... thank you ... also on behalf of all the Italians who are using ML , (although I do not know them ) , and that they do not even thank
(classic behavior of Italian people ) .
Thank you sincerely to all developers with their ability and patience have succeeded, and continue to do something truly " apocalyptic " .
You've managed to squeeze this camera until the last drop, and now they're coming also the seeds :)
I can assure you , when I will do that as my next job with the help of ML , I will send a good donation. You deserve it!
If I may, I would have just a few brief questions that I could not answer on forums, maybe for my bad english:
1 - I've noticed that when I shoot in RAW mode, increases the alias effect (moire), there is a way to reduce this, or is it strictly necessary to use the VAF Filter?
2 - I did not understand the difference of filming in RAW or MLV. Is this only for MAC? (I use windows)
3- I am currently filming with an old build that allows me to 1880 x 1016 (11/16/2013 d84b9cd9e86f build) and I'm finding it fine without audio. But I saw that for some time there is no longer a build that goes up to 1880. It 'was removed this option because it is dangerous for the camera?
4- When I shooting with 5x magnification, (you always talk about 3x magnification) for example 1880 x 1058 for a few seconds, when I import this in AE, I see that the size of the frame is always 1880 x 1058, and not highest as I read in the forums or in this table:
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5
It is a my mistake? Maybe I did not understand well how is shooting in crop mode?
if these questions are too stupid, please no one responds :)
Thanks again for everything.
Giacomo
Great Question
Quote from: dariSSight on February 06, 2014, 08:40:23 PM
Great answers it made me a little more informed on the world of Magic Lantern RAW. Shoot in Crop mode you said will eliminate most Moire errors, but doesn't that bring the image too close for frame accuracy?
It simply means you will have to move to a wider lens, which luckily isn't a problem with EF mount. Many great options out there.
Because of moiré I usually only shoot in crop mode and it gives me continuous shooting with my cards.
Quote from: PressureFM on February 06, 2014, 09:54:01 PM
It simply means you will have to move to a wider lens, which luckily isn't a problem with EF mount. Many great options out there.
Because of moiré I usually only shoot in crop mode and it gives me continuous shooting with my cards.
So which wider lens do you use and how much are they going for?
I think this moire is a bit overrated. Ofc there are cases where you will see extreme moire patterns. but the normal viewer doesn't notice moire unless it gets extreme.
Keep the story interesting and people wont have time to consider moire
giacomari >
In crop mode You can use even the cheapest lenses which suits You - zoom or prime. Just remember that when You shoot at resolution close to FullHD You should multiply the lens by 3 (for example 10 mm lens = 35 mm lens on Full Frame).
The crop of 21 MP equivalent to APS-C sensor is around 8MP, so most lenses have that resolution covered well. Since You the center part of the frame it's about 1/2 of it - so You are using the sharpest part of the lenses - that's why almost ANY EF-S lens will do.
You should consider more the focus and zoom ring and stabilization more than the glass (my personal opinion).
But I guess You could just walk into a photo store and test few lenses in crop mode and decide which one will work for You!
Here is a small explanation of sizes and moire I did.
The red rectangle s the frame when You shoot in Full Frame, the green one is when You shoot in zoom (crop) mode.
(http://www.zoomdesign.bg/ml/explanation-moire-sensor.jpg)
You may wanna take a look at this little comparisson:
As you can see, Moire isn't completely eliminated with the VAF, but it's way better in the mid range.
In other words: there's still moire in really extreme cases. But the biggest part of what you'll find in the real world is gone!
----
My latest movie (see below) is entirely recorded in NON-crop-mode with the VAF. You can randomly scroll through it and will hardly see any moire.
Besides: Crop mode is free of moire (certainly without the VAF, as cmac explained really fine), but, you completely loose wide angle capabilities. Take a look at 13:14 mins. I used a 14mm-Lens - and created a look, you just can't in crop mode!
So, I would recommend a VAF with non crop mode for extreme wide angles. And once you got your VAF, the need for crop is gone in most cases (except really crazy zoom shoots).
really thank you for all these tips, they are very relevant.
I began to have a clearer idea about it.
Now I will do some thorough testing to better learn, especially in crop mode, which still know very little.
Unfortunately I do not have a VAF, however I will try to avoid as much as possible objects with strong alias, and not with strong wideangle.
Originally I'm from traditional film (super 16mm), and after a few time working on digital, I'm still getting used to all the infinite possibilities of this unique medium.
I will let you know very soon, maybe with a video.
thanks
Giacomo
When the camera takes video the sensor captures an image that is 5616x3744 pixels in size. In order to get a HD size video the camera needs to reduce the size of the images to HD size. It does so by only reading every 3rd pixel from the image in width and height, 5616/3 = 1872 pixels(This is why the max resolution in non crop mode is 1872 and not 1920). Since it is reading every 3rd pixel instead of doing some sort of averaging the result is an under-sampled image that has aliasing and moire.
In crop mode the camera reads every pixel on a smaller portion of the sensor, about 1/3 of it. Since it is now reading every pixel and no longer skipping the image no longer has any aliasing or moire. It is internally performing and operation similar to opening the image in a editing program which is 5616 pixels wide and cropping out a section in the middle that is only 1872 pixels across. This effectively increases the focal length of the lens 3 times or mimics a camera with a crop factor of 3. This is also why it is called 3x crop mode even though you are using the 5x zoom on the camera. It is exactly the same as a 48 mm lens on a super 35 mm camera having the same field of view as a 24 mm lens on a super 16 mm camera.
@gunter
13:14, moneyshot! Very nice and shows the power a full frame camera.
too bad I dont understand German. I remember you published your film here, but I could only watch about 5 min as I don't understand the story :(
personal fan of wides.
Quote from: PressureFM on February 06, 2014, 09:54:01 PM
It simply means you will have to move to a wider lens, which luckily isn't a problem with EF mount. Many great options out there.
Because of moiré I usually only shoot in crop mode and it gives me continuous shooting with my cards.
I tried and tried in various resolutions, but in crop mode (5x magnif.) I can't shoot more than a few seconds. For example: 6 sec. at 2048 x 1076 and 19 sec at 1856 x 928 using a KompterBay 1000x 128gb
What kind of cards do you use?
when in crop mode use FPS override and set to 23.976 and choose EXACT FPS.
Quote from: ted ramasola on February 08, 2014, 09:44:36 PM
when in crop mode use FPS override and set to 23.976 and choose EXACT FPS.
Hi Ted,
I went to take a ride on your website, and I was very impressed by how the question of the crop mode, and not only that, are explained very carefully, .
My compliments for everything you do.
As you have suggested, I tried to set on EXACT 23.976 fps and finally I managed to film in crop mode and in continuous.
Unfortunately, in this mode the camera now does something that has never done before: when I set at 5x magnification, the image on the viewfinder clears one or two stops after a second, and also the image has recorded this overexposure. I tried with various builds, but always with the same result.
But If I reset the "fps override" to off, everything comes back ok, but again does not allow me to shoot continuously.
I hope that mine is a known problem, maybe someone can help me understand?
Quote from: Kharak on February 08, 2014, 02:41:24 AM
@gunter
13:14, moneyshot! Very nice and shows the power a full frame camera.
too bad I dont understand German. I remember you published your film here, but I could only watch about 5 min as I don't understand the story :(
personal fan of wides.
Thank you :)
Btw, I just added some subtitles ;)
Quote from: guentergunter on February 07, 2014, 06:08:31 PM
You may wanna take a look at this little comparisson:
As you can see, Moire isn't completely eliminated with the VAF, but it's way better in the mid range.
In other words: there's still moire in really extreme cases. But the biggest part of what you'll find in the real world is gone!
----
My latest movie (see below) is entirely recorded in NON-crop-mode with the VAF. You can randomly scroll through it and will hardly see any moire.
Besides: Crop mode is free of moire (certainly without the VAF, as cmac explained really fine), but, you completely loose wide angle capabilities. Take a look at 13:14 mins. I used a 14mm-Lens - and created a look, you just can't in crop mode!
So, I would recommend a VAF with non crop mode for extreme wide angles. And once you got your VAF, the need for crop is gone in most cases (except really crazy zoom shoots).
Today only I could see your two videos: the test and your short film.
The test is very indicative and useful for a good example of how to fight the alias.
Your short film seems a funny story, is shot with care and cleanliness; my compliments. Too bad I could not understand German.
Thank you.
Hi Everyone,
I've been using magic lantern firmware to shoot raw vids with my DSLR for some time now and it always worked properly.
But today, when opening the files I shot yesterday, I found some vertical strides on each and every frame (cf link).
This problem occurred with both oct 24 (on one card) and Jan 14 (on the other).
https://www.dropbox.com/s/8m58izffa5amry3/Capture%20d%E2%80%99%C3%A9cran%202014-02-10%20%C3%A0%2014.23.14.png
Same strides appear wether using "raw magic" or "raw 2 dng".
Can somebody pleeeeaaaaase help me out ???
Upload a DNG and post the conversion log from raw2dng.
Ok that's very weird, I just "decompress" one more time a RAW file to upload a dng and now, I don't have problem any more with Raw2dng and RawMagic...
here's a pics from the same Raw file with the same software :
https://www.dropbox.com/s/kbsorp5jrss92ta/Capture%20d%E2%80%99%C3%A9cran%202014-02-10%20%C3%A0%2014.58.43.png
One decompress this morning and the other right now...
I gonna re-decompress all my Raw to see what's happen and I'll told you.
Thx
Someone point me in right direction for a MLV viewer for mac please, found one on here and doesnt boot up on 10.8.5, installed whats needed and nothing, cheers! :)
I found using the latest a.d. build 02/04 to be the most unstable one so far. I don't what to double post so I put the details on the mlv modules forum.
http://www.magiclantern.fm/forum/index.php?topic=7122.msg100790#msg100790 (http://www.magiclantern.fm/forum/index.php?topic=7122.msg100790#msg100790)
Sorry for the "tangental" question. How exactly do you set "CROP" mode. I am using 5dm2, with the Feb 04 ad build. I am using straight RAW mode, not MLV.
Thanks in advance.
Nelson
You press the zoom button on the upper right on the back of the body near the LCD screen, the same one that allows you to zoom the LV. Just press it once to 5x zoom, it doesn't work properly in 10x zoom.
to add to bnvm's answer I recommend your procedure for working in crop mode would be this additional tips.
1. Press the magnify button once to activate 3x crop mode (this is 5x zoom in canon terms) As bnvm mentioned.
2. Use Auto in preview to give you "proper" framing in crop mode. (framing is wyswyg) but in grayscale and low res.
3. Once in crop mode, you can use half press of shutter to give you color preview and apparent better resolution but still low refresh rate(does not affect recording)
4. Before recording, you can use 10X zoom to confirm your focus, go back to 3x (5x zoom)crop mode to start recording.
Hi, is it there any build that allows MLV to record 1880?
Also...has anyone had problems using lower sample rates on mlv_snd?
I'm using audio just to sinc my track while editing .. So I don't need CD quality.. I need just a reference. But when I hit stop there's a red message sain something like the audio failed to stop or something .
Thanks!!
Quote from: djzigoh on February 10, 2014, 11:38:24 PM
Hi, is it there any build that allows MLV to record 1880?
this has already been discontinued to conform all the ML builds with different camera models.
Thanks all for the help. The viewfinder does take a little getting used too once you go to record. I need to run some tests to see how long I can record in this mode, and if our weather straightens out, I can try this with my 70-200 lens outside.
Nelson
hello everybody,
I made ​​a video to show the problem that my 5d2 shooting in crop mode 3x.
Explain this is not easy, and I also watched a little out there, but I did not find other people talking about this.
The build is in use is: 2014-01 14 2b804e8cdd3c
When filming at 24 fps in crop with FPS OVERRIDE in OFF, the lightview respects the correct exposure, but it can shoot only for a few seconds.
But when filming at 23.976, with EXACT FPS activated (ML), can shoot continuously, but the image in lightview is increased of 1 stop. And this is not only in the viewer, but also in the recording.
I do not know how to do. I also tried other builds, but with the same result.
A little help ... Thank you.
Quote from: loconetter on February 11, 2014, 02:14:38 PM
Thanks all for the help. The viewfinder does take a little getting used too once you go to record.
Nelson
What viewfinder you talking about? The viewfinder cannot be used once in movie mode, only the LCD screen is active.
Quote from: giacomari on February 11, 2014, 04:52:15 PM
hello everybody,
I made ​​a video to show the problem that my 5d2 shooting in crop mode 3x.
Explain this is not easy, and I also watched a little out there, but I did not find other people talking about this.
The build is in use is: 2014-01 14 2b804e8cdd3c
When filming at 24 fps in crop with FPS OVERRIDE in OFF, the lightview respects the correct exposure, but it can shoot only for a few seconds.
But when filming at 23.976, with EXACT FPS activated (ML), can shoot continuously, but the image in lightview is increased of 1 stop. And this is not only in the viewer, but also in the recording.
I do not know how to do. I also tried other builds, but with the same result.
A little help ... Thank you.
what other camera settings do you have?
is your camera on manual?
what other modules is loaded?
what is you ML settings?
etc etc.
Is your recording in 1x mode continuous? at what resolution?
I suggest you use global draw ON
Can anyone tell me where to find info about getting around the 4gb file size limit on the Mark 2 during Raw?
Quote from: mrd777 on February 11, 2014, 07:38:15 PM
Can anyone tell me where to find info about getting around the 4gb file size limit on the Mark 2 during Raw?
Not possible , 5D2 runs a Fat32 system limited to 4GB that's it.
Quote from: reddeercity on February 11, 2014, 07:47:37 PM
Not possible , 5D2 runs a Fat32 system limited to 4GB that's it.
Makes sense now, looking at the raw capabilities graph for the cameras. I guess the MARK 3 is the only one that can keep going. I'll have to find a way to upgrade!
Ted. sorry, old photographer expression. I am of course referring to the LCD screen in Liveview mode, and just called it a "viewfinder". When I am in crop, I am seeing greyscale. I left Global Draw on but used the setting which turns it off when you record. At the time I start recording, not everything is greyscale. Depends on whether I manually shutoff Global Draw, or elect to have Global Draw go off when I press Record.
If I turn off Global Draw, when I press record it is "filling" the LCD and is greyscale. If I leave Global Draw on but set to go off when I press Record (Half Shutter for me), I see the same relative sized display as before pressing HS, but without the frame marks I see with Global Draw. However, the center frame, which is within the cropmark guides area, turns an alternate color, not exactly pink but pink-like, not sure.
I am going to continue experimenting with settings to see what I can expect.
The RAW files always seem fine, and when I process using raw2dng, then Photoshop to convert DNGs to TIF, and finally Compressor 4.1 to create a Prores 422 Movie, the results are Great!
Nelson
Quote from: loconetter on February 11, 2014, 08:03:21 PM
Ted. sorry, old photographer expression. I am of course referring to the LCD screen in Liveview mode, and just called it a "viewfinder". When I am in crop, I am seeing greyscale. I left Global Draw on but used the setting which turns it off when you record. At the time I start recording, not everything is greyscale. Depends on whether I manually shutoff Global Draw, or elect to have Global Draw go off when I press Record.
If I turn off Global Draw, when I press record it is "filling" the LCD and is greyscale. If I leave Global Draw on but set to go off when I press Record (Half Shutter for me), I see the same relative sized display as before pressing HS, but without the frame marks I see with Global Draw. However, the center frame, which is within the cropmark guides area, turns an alternate color, not exactly pink but pink-like, not sure.
I am going to continue experimenting with settings to see what I can expect.
The RAW files always seem fine, and when I process using raw2dng, then Photoshop to convert DNGs to TIF, and finally Compressor 4.1 to create a Prores 422 Movie, the results are Great!
Nelson
To get "proper framing" I would leave GD on both in overlays menu and in Raw video menu. I would just do a HS press to check focus or color composition. I sometimes would need to press 10x to get focus since crop mode is less forgiving when focusing using wide lenses.
I your previous post You asked how long it can record. On my tests with MLV+sound, at 1728x972 16:9 or 1856 at 2.20:1 recording is continuous until cf is full.
Your workflow seems tedious using photoshop. I strongly suggest going MLV instead of raw_rec and using g3gg0's mlvbrowser sharp or tonybeccar's MLV converter to extract dngs. Then prossesing the initial grade using resolve which is free anyway. exporting to whatever for final edit.
I haven't gone back to testing MLV. When I first read about it, and being a MAC computer user, I could not reliably get the MLV files converted. Last week I tried searching and reading thru threads, but did not find a LINK to a version of the MLV browser/converted newer than the one I had, which didn't work.
Also, although that was an earlier ML, it would ALWAYs hang my camera requiring a battery removal to get back to normal.
Perhaps things are more stable in the 2/04 release I am using.
Thanks for taking so much time with me!
Nelson
Quote from: ted ramasola on February 11, 2014, 06:57:01 PM
what other camera settings do you have?
--- There is no special setting, only those for the RAW REC. I also disabled MLV REC module.
is your camera on manual?
--- of course
what other modules is loaded?
--- YES, File Menager
what is you ML settings?
--- default ML settings.
etc etc.
Is your recording in 1x mode continuous? --- YES ---
at what resolution? --- 1872 x 850 or 1880 x 940 with 16-11-2013 build
I suggest you use global draw ON
--- I tried this, but records better without it
Thanks Ted for your help
how about your stills setting. Long recordings are better with RAW-none JPEG-L or any.
Also what is your CF card specs?
I also highly recommend using the latest build in the nightly. That is Feb 10, 2014.
Quote from: ted ramasola on February 11, 2014, 08:55:14 PM
how about your stills setting. Long recordings are better with RAW-none JPEG-L or any.
Also what is your CF card specs?
I also highly recommend using the latest build in the nightly. That is Feb 10, 2014.
Thanks Ted,
I managed to solve the problem: I did "restore ML default" in "Config Files" menu, and everything is back working.
Sorry for my ignorance.
Quote from: loconetter on February 11, 2014, 08:03:21 PM
I process using raw2dng, then Photoshop to convert DNGs to TIF, and finally Compressor 4.1 to create a Prores 422 Movie, the results are Great!
Nelson
If you Convert your .raw files with RAWmagic on the Mac or raw2cdng on PC to get Cdngs (Cinema dng's) then you can import directly a image sequences
In to Compressor 4.1 or Motion 5.0 then export prores4444 mov .
Feb 11 nightly, when turning off the camera, sensor cleaning will not stop, have to turn on and off again to make it stop.
Noticed this too a while ago, can you find a way to reproduce consistently?
yes, I think this behavior is only when installing this new update with default settings, after I made some menu changes, and made the off on off on routine, the following shutdowns are now normal.
edit: I think its still problematic even after initial changes. I'll study the behavior and see a pattern.
I'm looking for a way to make all shutdowns abnormal, or at least say 20% of them (I need that to begin narrowing down).
If it shuts down abnormally once every 2 weeks... I can't diagnose it.
this behavior was not present in the feb 10 nightly though.
I've seen it last week (but I had some debug stuff enabled, not the configuration from main builds). Tried to reproduce, all subsequent shutdowns were OK (some were showing sensor cleaning, others didn't).
edit: start camera, canon menu, disable sensor cleaning, enable it back, shutdown. This seems to do the trick, can you check whether it triggers the bug every time?
yes. And to confirm, in the canon menu when I disable then enable it again, I don't exit the menu after disable right? Its just selecting disable then immediately selecting enable again?
With that sequence, the sensor cleaning is stuck all the time.
Yep, I don't exit the menu. The point of this is to force a sensor cleaning at shutdown.
With that sequence, the sensor cleaning is stuck all the time.
also, turning OFF or ON the Global draw in overlays tab also trigger it consistently.
Narrowed down; CONFIG_TSKMON is the culprit.
(and yes, I had it enabled by default in my local builds, along with GDB)
edit: the tskmon hooks themselves are OK (they don't trigger the bug), so it must be something in the tskmon code.
Thats great. I also just checked that even the feb 10 nightly has that sensor cleen bug.
also, I find that the FPS 1 and lower is still buggy, 1.5 FPS and upwards are ok.
It seems to be a timing issue in tskmon's stack checker (if I do anything that takes too long, even just a longer bmp_printf, it locks up at shutdown).
It works for me, but it's not exactly a clean fix: https://bitbucket.org/hudson/magic-lantern/commits/89fdaf6a27be18cccc94348e3f1d18a137c79367
(it only patches the symptoms, but doesn't fix the underlying problem; maybe g3gg0 has some insights)
Updated the nightly build, can you try it?
If anyone can reproduce this kind of corrupted frames, please let me know:
(http://i.imgur.com/LTpy0g8.jpg)
(I might have a fix)
Quote from: a1ex on February 12, 2014, 09:26:33 AM
It seems to be a timing issue in tskmon's stack checker (if I do anything that takes too long, even just a longer bmp_printf, it locks up at shutdown).
It works for me, but it's not exactly a clean fix: https://bitbucket.org/hudson/magic-lantern/commits/89fdaf6a27be18cccc94348e3f1d18a137c79367
(it only patches the symptoms, but doesn't fix the underlying problem; maybe g3gg0 has some insights)
Updated the nightly build, can you try it?
yes, tried it feb12 nightly. the cleaning sensor freeze is gone. Will use it longer in my tests today to be absolutely sure.
Quote from: a1ex on February 12, 2014, 01:27:30 PM
If anyone can reproduce this kind of corrupted frames, please let me know: http://www.magiclantern.fm/forum/index.php?topic=5763
(I might have a fix)
Have You tried 1920x1080 with fixed framerate to 23,97 @ crop mode 10x? I just bumped on this issue yesterday doing some tests. It record MLV @ 5x with no problem. And on my test @ 10x it gave me a completely unusuable sequence - most of the video was a mess. I deleted it, but I can make another test if You can't reproduce it.
Just to add - Your work is amazing! I feel like entering a toy store each time I call the ML menu :-)
Raw video does not, has never, and probably never will work properly in 10x mode, so don't use it while recording.
I'm not talking about the 10x crop issue, I'm talking about the issue from that link.
Quote from: a1ex on February 12, 2014, 01:27:30 PM
If anyone can reproduce this kind of corrupted frames, please let me know: http://www.magiclantern.fm/forum/index.php?topic=5763
(I might have a fix)
The link says the topic is either missing or off limits.
I confirm .wav files from .mlv are a bit longer than video files. Perfect sync, however it can be a problem when importing multiple sequences on a same time line, each audio file adding a slight shift. (5D2, 2014/01/14 2b804e8cdd3c )
(http://www.cinemersion.fr/images/divers/shift.jpg)
Try the new mlv+audio feb 4th build from a.d.
I thinks the audio length is a little close to video length.
Testing Feb 14 build by a.d.
1. no pink frames on a series of tests, including crop modes
2. Audio meters now reflects weather sound module is On or Off
3. Audio meters now shows in FPS override mode, when sound module is on.
4. tested to record full 64gig cf card with sound.
5. Tested audio sync with video on a full 32 gig CF card. Audio remain in sync with no drift in the 7' 20" clip.
6. Record start/stop delay.
Previous builds like feb 10 (did not test 12 for delay) Had almost instant start recording with 1X: 3 centiseconds, 3xcropmode: 15 centiseconds.
for this build Feb 14, both 1X and 3X crop mode has a longer delay of 1.30 seconds
7. Low FPS frozen frame is still not fixed.
1. I didn't apply the pink frame fix for 5D2, were you getting pink frames before?
2..5: yay!
6. raw or mlv? any preallocation tricks enabled?
7. it's still a mystery
Quote from: a1ex on February 15, 2014, 08:17:08 AM
1. I didn't apply the pink frame fix for 5D2, were you getting pink frames before?
2..5: yay!
6. raw or mlv? any preallocation tricks enabled?
7. it's still a mystery
1. I havent had problems with pink frames with the 5D2 in a while, a quick check on my test lists show it was Jan 13 I last encountered it only when HDMI is attached.
I just included it since its problematic on the 7D.
6. prealloc tirck or the reserve card space was OFF.
7. hope this could be trouble shooted since I often use this for night cityscapes.
Test the Feb 14th build, from A.D. hack crop view mode & the non hack crop view mode.
We have Audio meter now with frame over ride on,
and a "reserve card space" feature so we don't loose audio on full card records to stop.
There's at lest a 3 second delay now when you push the set button to record raw, was not there
on the feb4th build. Is this a problem now ? Or is there a change in the way raw record works ?
Lost all informational overlays/text box on Lv when recording Raw.
Just a little icon with only time as information , I don't like that, there is no way of judging
how much video you recorded at what write speed, File size GB? so you don't know when raw will stop recording or how much you just recorded.
I Would like to see a option to switch back to the text information box with buffer bars instead of the little camera icon.
I switch on "show buffer graph" , this dose not work it just keep that little move icon, no buffer graph.
I have notice when you record a short clip then stop, the buffer bar shows for a spilt second .
The "Global Draw Off" only work in 2 preview mode, HDMI & ML Grayscale, in all other preview
there is a Black-box overlay.
I also notice if you use the hdmi Preview without a hdmi device attach you get wrong framing.
So if you do not want the black box for framing ( as I Do) the White Framing box is only correct for hdmi device.
If you press the delete button while recording raw you can remove the black box for framing to a dark Grey translucent overlay. ;)
It would be nice to have that feature to cycle though overlays or to kill them completely ,if possible.
Checking files, and notice "mlv_rec.tmp" on CF card, is this the reserve Space ?
For some reason after ever video clip capture ML save a screen shot of the Lv with overlays "bmp"
With the Crop view mode half shutter HI- Res preview in ML Gray preview, work like it should until you start
recording raw then the hi-res preview becomes all pinky overcast image, feb4th build was not like that it work with or without
raw record running.
Not Sure but I think we have a new frame size or I never notice before , 1792x968 1.85:1
This is continuous for me. :)
Most of these look like mlv-specific problems, so I'd say the best place to report them is in the MLV thread.
The FPS issue is 5D2-specific.
I'm also interested in what of these issues are also present in raw_rec. Rationale: if the new builds have introduced issues in both raw_rec and mlv_rec, it's probably something broken in the backend. If it's only on mlv_rec but not on raw_rec, it's likely a mlv-specific issue.
Ok I will do that :)
Quote from: a1ex on February 15, 2014, 08:47:31 AM
Most of these look like mlv-specific problems, so I'd say the best place to report them is in the MLV thread.
The FPS issue is 5D2-specific.
I'm also interested in what of these issues are also present in raw_rec. Rationale: if the new builds have introduced issues in both raw_rec and mlv_rec, it's probably something broken in the backend. If it's only on mlv_rec but not on raw_rec, it's likely a mlv-specific issue.
The FPS frozen frame problem is present in both raw_rec and mlv_rec modes.
Also, as a counter test for redddeercity's start/delay time, I also tested just now with HDMI monitor attached and its similar to the one without. Its a delay of 1" and 9-10 centiseconds.
Yes it looks like we do have a new set of frame sizes with 1792x#### ;)
Quote from: reddeercity on February 14, 2014, 07:11:32 PM
Try the new mlv+audio feb 4th build from a.d.
I thinks the audio length is a little close to video length.
Are those builds safe ? I'd rather wait a release ^^
( By the way do i have to confess how ML impress me each day ? ;) )
try the Feb 14 build from a.d. its stable enough for most reasonable requirements.
A.d. has missed to update his first post to indicate whats improved and to show he has a new build yet, but just download from the link on the first post.
And just keep checking back on this thread to keep posted with bug fixes and improvements.
Quote from: piloui on February 15, 2014, 07:49:42 PM
Are those builds safe ? I'd rather wait a release ^^
( By the way do i have to confess how ML impress me each day ? ;) )
I agree with Ted , try new feb14th build.
But yes , the last 2 builds from a.d. are very safe , in my tests
I push ML raw/mlv to there limits and then I push it over it's limits
To see where it fails, if it dose that is.
So normal usage with raw will never be a problem.
Don't wait jump in and play!
Quote from: reddeercity on February 15, 2014, 08:35:57 AM
...
Lost all informational overlays/text box on Lv when recording Raw.
Just a little icon with only time as information , I don't like that, there is no way of judging
how much video you recorded at what write speed, File size GB? so you don't know when raw will stop recording or how much you just recorded.
I Would like to see a option to switch back to the text information box with buffer bars instead of the little camera icon.
I switch on "show buffer graph" , this dose not work it just keep that little move icon, no buffer graph.
..
Me, neither! It doesn't fit with the interface and complicate the on-screen concept.(same at raw_rec). However ML is Opensource, it's an user request. Btw the crop mark is currently a compromise, because there is no crop mark for Global Off.
The fps bug is a quite complicated problem. I still don't fully understand how the algorithm from g3gg0's fps-engio works and who is the culprit.
Under the hood: It's really cool with a1ex's new memory backend (more memory and less conflict with canon code). g3gg0 optimized mlv_rec+ mlv_snd for more stability.
Quote from: a.d. on February 16, 2014, 10:16:11 AM
(...)
The fps bug is a quite complicated problem. I still don't fully understand how the algorithm from g3gg0's fps-engio works and who is the culprit.
(...)
Maybe a way for investigations: the fps override bug is only in raw video; in h264 it's working fine. And this bug was not present _even in raw video_ on builds made last summer (old builds, I agree).
This helps a lot. @a.d. (or anyone else with coding skills), can you do a hg bisect and pinpoint the changeset that triggered the bug?
@a.d. I just check the nightly for feb16th, in the Raw/mlv menu there a new
feature called "Status when recording" 3 option- none, icon, debug. This give us back the
text information box. Would it be possible to implement this feature from that nightly
in to your build ? :D
Does anyone know why after roughly 1 min 15 sec, my camera mirror closes and stops recording? I'm using 2:35 aspect ratio and 1850 (or something like that) resolution. I'm also getting dropped frames toward the end. Using Canon CF extreme pro 90 mb/s UMDA 6 (according to ML, it will record at like 50 mb/s on the resolution and aspect I'm using)
What does the menu help text say for raw_rec?
(read it out loud)
Quote from: a1ex on February 17, 2014, 06:58:55 AM
What does the menu help text say for raw_rec?
(read it out loud)
Thanks for pointing that out. For anyone who comes across this message, it said that Auto power off was enabled in the Canon menu - I disabled that and it went beyond the 1 min.
At some point, this text was printed in red blinking font ;)
Quote from: a1ex on February 17, 2014, 08:15:20 AM
At some point, this text was printed in red blinking font ;)
Must have been on my first run of it, when everything was new to me and I didn't catch it. :D
Quote from: a1ex on February 16, 2014, 03:39:06 PM
This helps a lot. @a.d. (or anyone else with coding skills), can you do a hg bisect and pinpoint the changeset that triggered the bug?
I'v thought to do that to see myself where is the problem to point it (plus try to corrected it, I can compile since some times) but I did not had time to check all old builds yet (between 2013-07 -> 2013-09, it was during these dates), to see when it append.
Maybe it was during the autoexec unification. This needs confirmation however I suspect that the bug was injected when the unification was done because the bug was present in NB but not in a.d. builds at this time.
Hi a1ex! I've tried bisect and it's time consuming... I think there seems to be no working version for 5D2 either. What I found so far, the "Double Buffering" and "Global Draw" have some kind of influence on the image sequence.
Revision 7651 (August)
some Revisions forward and backward=> bug!
Revision 6644
Single Buffering: Global Draw On
[1][2][2][3][3][4][4][5][5][6][6][7][7][8][9][9][10][10][11][11][12][12][13][13][14][14][15][16][16][17][17][18][18][19]...[n]
Single Buffering: Global Draw Off
[1][2][2][3][3][4][4][5][5][6][6]...[n][n]
[1][1][2][2][3][3][4][4][5][5][6][6]...[n]
The pattern is more seamless mostly double.
Revision 6650
Double Buffering: Global Draw Off
[1][2][3][2][4][2][5][2][6][2]...
Double Buffering: Global Draw On
[corrupt][1][corrupt][2][corrupt]5-9x corrupt and back to the second frame is different
Sometimes the last frame is corrupt only
Note
Revision 7198 (commit (https://bitbucket.org/hudson/magic-lantern/commits/98b41f60a2da3d2ed368f422ced701ec48b540b9)) too high write speed info in low fps (Revision 7195: more accurat write speed - Revision 7212: not)
@a.d. Back about 3 or 4 weeks ago I asked for suggestion for mlv+5d2 video tutorial .
you made a suggestion/request for HDMI setup guide, will here is my effort. Used the Feb4th hack view crop mode build
I hope you
ALL like it. :D
P.S. I have plans for a video tutorial with both Evf & hdmi recorder later on.
Quote from: reddeercity on February 19, 2014, 09:12:25 AM
@a.d. Back about 3 or 4 weeks ago I asked for suggestion for mlv+5d2 video tutorial .
you made a suggestion/request for HDMI setup guide, will here is my effort. Used the Feb4th hack view crop mode build
I hope you ALL like it. :D
P.S. I have plans for a video tutorial with both Evf & hdmi recorder later on.
Thanks for the tutorial, I'm curious about some of the equipment you had on the table you recorded. Please explain and give me pricing of equipment. Thanks
Quote from: dariSSight on February 19, 2014, 01:18:06 PM
Thanks for the tutorial, I'm curious about some of the equipment you had on the table you recorded. Please explain and give me pricing of equipment. Thanks
Lower left of the image , is my Zacuto Evf + 2.5x Doppler, just above that the frame for the camera so the Doppler can mount to the back
of the 5D2 against the Lcd screen. To the right is my Redrock Micro Matte Box with 4x5.65 Glass ND Filters.
Zacuto Evf - $665 cdn (demo unit)
Zacuto Z-Finder(Doppler+frame) Pro 2.5x for 3.2" Screens $429 cdn
Redrock Micro Matte Box $ 995
Redrock Micro 4x5.65 Glass ND filter kit (set of 3) $659
All these component's fit together on my Redrock Micro Cinema Camea rig.
Plus I can hang all my audio gear on the rig.
The Z-finder pro 2.5x was my first investment after my 5d2, For run & gun it's a must it give you a extra contact point
plus fine focus better exposure in daylight or bright area's
Then the Evf was my second this improve my content with more actuate image to adjust for exposure or when pulling focus.
The list of benefits go on and on, yes there are not cheap and you don't really need them but its really is nice to have them.
I would say it will save you money in the long run , because you can get your shot quicker and with less change of messing up. :D
Hey Im curious about what happened to the white framing on screen which helped to see whats being recorded. I just switched from June 2013 build to the latest :D
Quote from: Daedalus0506 on February 20, 2014, 10:00:44 PM
Hey Im curious about what happened to the white framing on screen which helped to see whats being recorded. I just switched from June 2013 build to the latest :D
The black border framing with white trim replaced it.
Anyone else having problems taking photos with the last 5 builds ?
My camera locks up pretty much everytime I take a photo with the last builds since dec or so.
Got another card running some build from summer and I got no problem there, so wondering if anyone else got the same?
All OK here.
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
(http://i17.photobucket.com/albums/b61/dd2020/baiyok2/asking1ex2_zps7f4386a7.jpg~original)
May I ask...
What's happen to this?
Look like ML on 5Dll cannot render correct pixels when shooting at pattern things like buildings' windows or floors.
I used October 4th build and 32GB Sandisk CF Extreme Pro 1067X (up to 160MB/S read 150MB/S write)
Is this ML limitation of 5Dll ? or I have to change to other builds?
Or I have to upgrade to 5Dlll?
Today I will try new build, the October 24 th.
Thank you mates.
:)
please update your photo to 900x900px. per forum rules.
THAT is what is called color aliasing and moire. It is there due to line skipping of the sensor and is present even in h264.
Video mode involves line skipping/photo mode does not.
Its in all canon dslrs except the mkIII which have minimal moire due to a more aggressive OLPF. BUT h264 is somewhat soft.
Its more obvious now due to raw and the only way to minimize it is via mosaic VAF filter.
You will find it very minimal to almost non in crop mode since its a 1:1 pixel recording from the sensor and no line skipping.
The mkIII does not have this problem so much.
Quote from: ted ramasola on February 23, 2014, 07:30:12 AM
please update your photo to 900x900px. per forum rules.
THAT is what is called color aliasing and moire. It is there due to line skipping of the sensor and is present even in h264.
Video mode involves line skipping/photo mode does not.
Its in all canon dslrs except the mkIII which have minimal moire due to a more aggressive OLPF. BUT h264 is somewhat soft.
Its more obvious now due to raw and the only way to minimize it is via mosaic VAF filter.
You will find it very minimal to almost non in crop mode since its a 1:1 pixel recording from the sensor and no line skipping.
The mkIII does not have this problem so much.
Thanks you so much for your help..
MLV module failed me miserably yesterday.
Did a take of 2090 frames and the middle 600 frames are missing or corrupted. Too bad I didn't find out until I came home... doh!!
build 2014/02/04 (75649ffe291b) (dont ask me why I was still using this one)
Camera: 5D MK II
Modules: MLV_rec + snd
Resolution: 2:1 1872x936
Card: Lexar 128 gb 1000x
GD: ON
Buffer Method: 1
Extra hacks: ON
frame skipping: ((OFF))
Recorded 2090 frames and of which a chunck of some 600 frames is missing somewhere in the middle of the take.
When I play the mlv file in mlvrawviewer somewhere in the middle of the take it starts skipping frames and then 600 frames are black and then it continues playing again like normal. Tried MLVbrowsesharp and MLVconverter and both extract only 1394 frames.
Extra notes: I noticed while it was recording that it struggled to increase expected frames to "Continues OK", but when it got there it would at times drop down again to specific number of frames and then back again to continues. (if that helps)
Never experienced dropped frames with RAW_rec.
Luckily the set is still up, so It'll be quick to re-take, but embarrassing.
Quote from: dd2020 on February 23, 2014, 07:14:26 AM
May I ask...
What's happen to this?
Look like ML on 5Dll cannot render correct pixels when shooting at pattern things like buildings' windows or floors.
I used October 4th build and 32GB Sandisk CF Extreme Pro 1067X (up to 160MB/S read 150MB/S write)
Is this ML limitation of 5Dll ? or I have to change to other builds?
Or I have to upgrade to 5Dlll?
Today I will try new build, the October 24 th.
Thank you mates.
:)
Some additional info to what ted ramasola said ;)
Quote from: Kharak on February 23, 2014, 06:20:07 PM
MLV module failed me miserably yesterday.
Did a take of 2090 frames and the middle 600 frames are missing or corrupted. Too bad I didn't find out until I came home... doh!!
build 2014/02/04 (75649ffe291b) (dont ask me why I was still using this one)
Camera: 5D MK II-Modules: MLV_rec + snd-Resolution: 2:1 1872x936-Card: Lexar 128 gb 1000x-GD: ON-Buffer Method: 1
Extra hacks: ON
frame skipping: ((OFF))
Recorded 2090 frames and of which a chunck of some 600 frames is missing somewhere in the middle of the take.
When I play the mlv file in mlvrawviewer somewhere in the middle of the take it starts skipping frames and then 600 frames are black and then it continues playing again like normal. Tried MLVbrowsesharp and MLVconverter and both extract only 1394 frames.
Extra notes: I noticed while it was recording that it struggled to increase expected frames to "Continues OK", but when it got there it would at times drop down again to specific number of frames and then back again to continues. (if that helps)
Never experienced dropped frames with RAW_rec.
Luckily the set is still up, so It'll be quick to re-take, but embarrassing.
The Feb 4th built should have been Ok, I think unless you really need Global Draw=On, when recording I would leave it Off
and I would try buffer 0 , It seems to be the fastest at least by my tests.
I find 1872 with GD=On can sometimes be very unstable at times, I always leave GD Off to be stable in the large frame size.
1856x928 is my base default, as I use hdmi recorder for backup. :)
I've been over confident in MLV I guess.. Thought it would stop if it started skipping.
But regarding the jumping from Continues OK to specific amount of frames and back, its not like the expected frames was ever close to the actual recorded frames. The expected was up in the 8000 and I only recorded 2000.
For safety reasons, I'll be doing next take on oct 24 RAW.
I agree with you. I just can't find the perfect MLV build for professional work. It is both too finicky and removes features that I like, like the buffer status (but no huge graph) and recording start beep.
No worries though, raw in Oct 24th is great, only thing is the HDMI monitor crash bug but at least I know the workaround. I will be sticking with that one for a while I think.
Quote from: silvertonesx24 on February 25, 2014, 07:04:33 AM
I agree with you. I just can't find the perfect MLV build for professional work. It is both too finicky and removes features that I like, like the buffer status (but no huge graph) and recording start beep.
No worries though, raw in Oct 24th is great, only thing is the HDMI monitor crash bug but at least I know the workaround. I will be sticking with that one for a while I think.
Use feb 4th a.d. hack crop view mlv built + audio its very stable and still have the buffer status bar overlays, that the one I use for work.
no need to go back to oct24th built unless you need large frame size for long shots.
The Nightly has the buffer bar back in there for debugging in the mlv raw menu, but its still a nightly so
its not always totally functional or things are turn off. :)
Hey guys,
i keep on reading about 3x-magnification in mlv_rec here in the forum. Is this a 5D3-only feature? I can only get 5x and 10x magnification.
When i push the magnify-plus-button on the camera during a mlv-recording the image gets magnified by 5x but recording stops instantly. Am i doing something wrong or is magnification not possible during recording?
Would be quite cool to use a wide-angle prime instead of a zoom.
Greetz
Peter
It's not a 5DMkIII specific mode. It's not really a magnification as such it's actually a crop of the sensor rather than the 'line skipping'. It avoids moire too.
Yes you can do it on the 5DMKII. It works.
Basically you will be able to record when you are in the 5x zoom mode (the 10x does not function that's just how it is).
Check out this video which explains it nicely:
https://www.youtube.com/watch?v=dQ51rE_ZUgo (https://www.youtube.com/watch?v=dQ51rE_ZUgo)
Thanx mageye for the reply! Sure, it's not a real optical magnification, it's reduced line skipping.
I still don't know how to activate this 3x-magnification. Is there a special menu hidden somewhere?
When i press the magnification-button on the cam it goes into 5x-magnification (not 3x!) and when i press the set-button to start the recording the camera zooms out and starts a h.264-recording instead of mlv.
My mlv-settings are:
Resolution: 1872x1012
Aspect ratio: 1.85:1
Global Draw: Allow
Frame skipping: off
Preview: Auto
Digital dolly: off
Extra Hacks: on
From what I can see; what you are doing is correct. There is no magic here as such (apart from the Magic Lantern itself! ;)). You just record when you are in the zoomed mode. The 3x zoom is the amount it's actually 'zooming'. Basically ignore the 5x it's actually 3x!!!
Anyway ... You are obviously triggering the h264 recording at the same time (or instead?) as the MLV RAW video. You obviously need to stop the h264 from recording and that's the bit I am not sure about?
I have had that before but now my cam is set up so it doesn't do that. I just can't remember what I switched. I am pretty sure if you did a fresh install with the latest build it should 'just work'.
I really can't remember what it was that I did to ensure that it only records just RAW but I know most things are common sense.
Maybe someone else can put us straight with that one? Sorry I can't help more than that right now!
The optimal setting for the 5D2 for continuous recording with 64GB Lexar 1000x card, at lest for my camera are as follows:
No HDMI attach, Non Crop mode with Feb 4th mlv build from a.d.
1872x938 23.976p + audio
Global Draw Off when recording
Preview Mode - Hack preview or HDMI* preview (note* this is only with a.d.'s builds)
Extra Hacks - On
Frame Over Ride = On (Exact 23.976)
Buffer fill rate - 0 or 1
In the Canon menu I use Small raw in Photo Mode
I posted a short Video about hdmi recorder with 5d2 on the new format mlv+audio
From about the 5:00 to 9:17 I show my setting for raw/mlv, I thinks that should help
If not just ask .
http://www.magiclantern.fm/forum/index.php?topic=5533.msg102567#msg102567
Thanx for your replies! I found the setting that caused the h.264-recording. I selected Prefs->LiveView zoom tweaks->Auto exposure on Zoom. After deactivating this function it worked just fine!
When using 3x-magnification the refresh rate is extremely low when Global Draw is on.
@reddeecity:
I also use a 64 GB Lexar 1000x an tried different resolutions. In the recent a.d.-releases the transfer rate got quite good while Global Draw is on. I luv shooting with Focus Peaking and Zebras. With Global Draw on and 1856x1004 i can shoot about one minute. That's enough for one scene.
With the mentioned resolution of 1872x938 i think you can even activate Global Draw an still get continuous recordings as long as the card is already warmed up. The Lexar 1000x is one of the cards that highly benefits from card warm-up. Most of the time i shoot stills with my 5D2 and for that i don't want the warm-up procedure to be done on every boot of my cam. Would it be possible to make a little menu-entry in the card warm-up menu where you could manually trigger the warm-up procedure?
I also found out that the Lexar 1000x needs far more than 1 GB to reach it's maximum performance. 4 or 6 GB would be just perfect.
Btw. it's a pity that the beep and the remaining time indicator disappeared. Those were great features.
No Lexar card are not the one's you need to warmup
You shouldn't have to warm up at all to reach max. Performance
You may have a bad card.
You will get far more stable recording with Global Draw Off.
You only need to see on screen display to adjust exposure etc...
After that you start recording you can't adjust anyways, so I would learn
To work without it then you can get larger stable frame size.
Are you sure that the Lexar cards don't benefit from warm-up? Did you try it with yours?
Well, i record kids. Everything they do is unpredictable and for that i need the flexibility to change the focus during recording. Without focus peaking it's quite hard. Sure, if you record an interview you don't need Global Draw at all.
Yes I have, there is no difference in fact I notice it would slow down
To point where I could no longer get continous recording .
The hotter the card gets the less reliable it becomes & after 10 plus minutes
Which is about 60GB the card get very warm to almost hot
But in a professional work environment you need to have reliable
Cards that are ready to be filled up continous or not.
I being running on the same Lexar cards since May of 2013.
:)
Had fun time to play with some very strange set of lenses and res chart shooting :-)
It's all about 3x (displayed as 5X) shooting versus 1X and moire.
For me there the main thing is that the color moire is much less in 3X.
Yet You need to consider the choice of lenses carefuly.
In critical situation this can give You a slight edge though...
Still for the one I used - a nikon mount Sigma 10-20 it is always closed at F22 when unmounted, so I had some more manual tweaking the lens with cardboard to keep it open :-)
Wow, finally getting to post here about the first project I've done that was %100 raw video using an old build from a few months ago! Loving all the fantastic free progress, it's like I have a whole new camera! Did this a few months back but it's finally going to be released soon, I suppose it's time to upgrade my ML version.
I used a build before the audio was added, shot in 1880 x 800, graded through davinci resolve. Hmm, it seems the biggest changes are the addition of audio and getting rid of 1880 mode? Is this true?
audio is added via mlv_snd. 1880 is still in the raw_rec a.d. build not in the mlv module.
Awesome thanks, thought 1880 was gone
Quote from: ted ramasola on March 04, 2014, 10:50:33 PM
audio is added via mlv_snd. 1880 is still in the raw_rec a.d. build not in the mlv module.
Hi Ted. I was getting audio wav files with the mlv's with a feb build. What do you mean audio is added? I'm in the middle of figuring out how to sync the wav's with the DNGs using a davinci resolve>premiere>resolve workflow.
Hi, does anybody knows on what ML release the black mask in LW in Raw mode disapeared ? I use the last of 02/2014 and I don't see it anymore in option.
& Again : thank's to ML team :)
Quote from: xvince1 on March 07, 2014, 12:29:02 PM
Hi, does anybody knows on what ML release the black mask in LW in Raw mode disapeared ? I use the last of 02/2014 and I don't see it anymore in option.
& Again : thank's to ML team :)
The black mask border is still there in both raw_rec and mlv. Looking at Mar 2 nightly.
Quote from: PeterR on March 05, 2014, 10:47:57 PM
Hi Ted. I was getting audio wav files with the mlv's with a feb build. What do you mean audio is added? I'm in the middle of figuring out how to sync the wav's with the DNGs using a davinci resolve>premiere>resolve workflow.
You can manually link the audio in resolve so you can export them as individual clips, if you don't link them, the clips will be exported without sound. When you export the resolve timeline as a SINGLE clip audio is included.
Look at page 122-124 of the Resolve manual PDF. There is a "one click" method to link all wav file to the clips however, I found out that longer clips will have a linked wav file that suddenly has no sound half way, and you can see in the resolve timeline the linked waveform volume is gone halfway. what I did was manually link only the problematic clips so I don't have to link all.
The oct 24th a.d. build is the one I use for Raw try that, you still can
download It .
Quote from: ted ramasola on March 07, 2014, 06:23:30 PM
The black mask border is still there in both raw_rec and mlv. Looking at Mar 2 nightly.
Thank's Ted. i don't really understand how to active it, as I have all modules activated. I will see further. :)
Do you have some feedback about reliability of KB CF for RAW since last summer ? My 128Gb still work very nicely (even I got some issue yesterday...), but I don't use it as professionnal work like U do.
Quote from: xvince1 on March 10, 2014, 12:02:17 PM
Thank's Ted. i don't really understand how to active it, as I have all modules activated. I will see further. :)
Do you have some feedback about reliability of KB CF for RAW since last summer ? My 128Gb still work very nicely (even I got some issue yesterday...),
If you are shooting mostly raw video, you should not load "all modules" as you stated. I'd say load only the essential ones. You can load only either raw_rec or mlv_rec, but not both.
In my case I load only 5 modules.
file manager
mlv_rec.mo
mlv_snd.mo
mlv_play
pic viewer
As for the KB, the 32 and 64 1000X are the top performers, 128 gig cards are very slightly slower than the 64s and the 128 1050x is slightly better than the 128 1000x.
The 128 1050x is ideal when using longer recordings at 1728x864, you can do 1728x972 if your clips are only at approx 2min each.
The 128 1050x can get higher resolutions on the 7D compared to the 5d2.
Hi Ted , so finally the 1050x work with 5D2 ?
For the black mask, I have try the old release from 24/10/2013 and I have the mask in the RAW menu named recording frame (with the choice between black bar or white rectangle) but I can't find it in the it in the last releases. I have only load all modules to find this, I don't usually load them aside RAW modules.
The white rectangle is not there anymore just the black borders.
I just find out : the black borders only appear with MLV module, not in RAW module anymore... I'm used to record in 1880x854, and 1880 isn't in MLV module, that's why I do not use MLV. I have to choose... I'm pretty happy with RAW module and RAWinizer... I'm not very familiar with MLV tools
Quote from: xvince1 on March 10, 2014, 10:53:41 PM
I just find out : the black borders only appear with MLV module, not in RAW module anymore... I'm used to record in 1880x854, and 1880 isn't in MLV module, that's why I do not use MLV. I have to choose... I'm pretty happy with RAW module and RAWinizer... I'm not very familiar with MLV tools
I was in your shoes, at the early stages of MLV. Now its ready. Sound is a good thing. The tools you need are also there.
Go for the Mar 2 nightly and you're good. Though I have only begun testing the mar 10, the mar 2 is what you want for MLV.
The resolutions you can do continuous recoding on a 64gig 1000x compared with a 128gig 1050X
are:
Resolution 128gig 1050 x 64gig 1000x
1X mode
1728 x 972 16:9 +- 2'9" continuous
1728 x 934 1.85:1 +- 1'11" continuous
1728 x 864 2:1 continuous/gd off continuous
1792 x 968 1.85:1 44" 2'59"
1792 x 896 2:1 continuous/GD off continuous
1856 x 928 2:1 +-34" continuous
1856 x 844 2.20:1 +-3'41" continuous
1856 x 790 2.35:1 continuous/GD-off continuous
1872 x 850 2.20:1 +-3' continuous
1872 x 796 2.35:1 +-1'32" continuous
1872 x 784 2.39:1 continuous continuous
3X crop mode with Global Draw ON
Resolution 128gig 1050 x 64gig 1000x
1728 x 972 16:9 +-1'4" continuous
1728 x 934 1.85:1 +-1' continuous
1728 x 864 2:1 continuous continuous
1856 x 928 2:1 +-18" continuous
1856 x 844 2.20:1 continuous continuous
1920 x 872 2.20:1 +-53" continuous
1920 x 818 2.35:1 +-4'28" continuous
1920 x 804 2.39:1 continuous continuous
2048 x 872 2.35:1 +-34" continuous
2048 x 856 2.39:1 +-36" continuous
2048 x 820 2.50:1 continuous continuous
On the 7D the 1050X can do 99 % of the resolutions the 64 1000x can do.
thank's Ted, I will see further on MLV. I've read the topic of reddeer to extract RAW+wav, but I need a topic for synchro in after effect or premiere. So 1050x cards are full functionnal on 5D2 ?
Quote from: xvince1 on March 11, 2014, 12:55:33 AM
thank's Ted, I will see further on MLV. I've read the topic of reddeer to extract RAW+wav, but I need a topic for synchro in after effect or premiere. So 1050x cards are full functionnal on 5D2 ?
To get the full potential on the 5D2 I recommend the 64gig 1000x, the 1050x will function on the 5d2 BUT due to its write speeds you get smaller resolutions that are continuous. But yes, it will function but you might not get longer record times.
For synchro, use resolve. It is faster and do not go the after effects route, its time consuming and the acr is not designed for long videos but photos. Its just ok for short clips but in the long run, resolve is designed from the ground up for raw videos.
To sync audio refer to pages 122-124 of the resolve manual.
To extract MLV videos with wav, use either g3gg0's MLV browser ro tonybeccar's mlv converter.
http://www.magiclantern.fm/forum/index.php?topic=8447.0
http://www.magiclantern.fm/forum/index.php?topic=10198.0
I should mention that right now the fastest stable MLV+Audio build comes from the nightly build
(magiclantern-v2.3.NEXT.2014Feb16.5D2212)
1872x936 2:1 23.976p + audio, Is continuous with 1000x card on 5d2 fill buffer set to "0"
I will be using this tomorrow on a News-story/interview ;)
Edit: I do my audio syncing in A.E., but I also record a master track on a Zoom 4Hn
I just use the audio in mlv to sync with master. Resolve is Ok, but ACR plugin is the best out there,
Its just a slower workflow but better result, at least that's what I think anyways.
Quote from: ted ramasola on March 07, 2014, 06:31:17 PM
You can manually link the audio in resolve so you can export them as individual clips, if you don't link them, the clips will be exported without sound. When you export the resolve timeline as a SINGLE clip audio is included.
Look at page 122-124 of the Resolve manual PDF. There is a "one click" method to link all wav file to the clips however, I found out that longer clips will have a linked wav file that suddenly has no sound half way, and you can see in the resolve timeline the linked waveform volume is gone halfway. what I did was manually link only the problematic clips so I don't have to link all.
Thank you, Ted. I'll try this in the morning.
Quote from: reddeercity on March 11, 2014, 06:52:13 AM
I should mention that right now the fastest stable MLV+Audio build comes from the nightly build
(magiclantern-v2.3.NEXT.2014Feb16.5D2212)
1872x936 2:1 23.976p + audio, Is continuous with 1000x card on 5d2 fill buffer set to "0"
I will be using this tomorrow on a News-story/interview ;)
Edit: I do my audio syncing in A.E., but I also record a master track on a Zoom 4Hn
I just use the audio in mlv to sync with master. Resolve is Ok, but ACR plugin is the best out there,
Its just a slower workflow but better result, at least that's what I think anyways.
Quote from: ted ramasola on March 11, 2014, 01:05:32 AM
To get the full potential on the 5D2 I recommend the 64gig 1000x, the 1050x will function on the 5d2 BUT due to its write speeds you get smaller resolutions that are continuous. But yes, it will function but you might not get longer record times.
For synchro, use resolve. It is faster and do not go the after effects route, its time consuming and the acr is not designed for long videos but photos. Its just ok for short clips but in the long run, resolve is designed from the ground up for raw videos.
To sync audio refer to pages 122-124 of the resolve manual.
To extract MLV videos with wav, use either g3gg0's MLV browser ro tonybeccar's mlv converter.
http://www.magiclantern.fm/forum/index.php?topic=8447.0
http://www.magiclantern.fm/forum/index.php?topic=10198.0
Thank's for both of you ;)
Quote from: reddeercity on March 11, 2014, 06:52:13 AM
I should mention that right now the fastest stable MLV+Audio build comes from the nightly build
(magiclantern-v2.3.NEXT.2014Feb16.5D2212)
1872x936 2:1 23.976p + audio, Is continuous with 1000x card on 5d2 fill buffer set to "0"
I will be using this tomorrow on a News-story/interview ;)
Edit: I do my audio syncing in A.E., but I also record a master track on a Zoom 4Hn
I just use the audio in mlv to sync with master. Resolve is Ok, but ACR plugin is the best out there,
Its just a slower workflow but better result, at least that's what I think anyways.
Thanks for the tips like always, now the magiclantern-v2.3.NEXT.2014Feb16.5D2212 file is the second Feb 15th download. Do you primarily use the 2:1 1872x936 setting.
Quote from: dariSSight on March 11, 2014, 09:13:46 PM
Thanks for the tips like always, now the magiclantern-v2.3.NEXT.2014Feb16.5D2212 file is the second Feb 15th download. Do you primarily use the 2:1 1872x936 setting.
Yes 2:1, I don't like any A.R. less then that as it can be re-framed to full HD
Or As is for Cinematic Super-Scope or also known as Univisium (http://en.wikipedia.org/wiki/Univisium)
So its a win win scenario, And for todays Interview I did with that build, everything when perfectly no problems.
It was to a point where I no longer worried about MLV/Raw Stop recording unexpectedly .
But I did not use any HDMI devices as this was a Run & Gun Style interview, so I don't think I would get Continuous
at 1872x936 with hdmi but I haven't tried that yet.
Hi,
I understand Dual ISO RAW video is yet to be ported to 5D2, right?
Any alternative idea for raw video in situations where dual iso video would apply? will dual iso video ever be ported to 5D2 or is there any physical/technical limit?
Thanks
Quote from: melimelo on March 13, 2014, 03:16:03 PM
Hi,
I understand Dual ISO RAW video is yet to be ported to 5D2, right?
Any alternative idea for raw video in situations where dual iso video would apply? will dual iso video ever be ported to 5D2 or is there any physical/technical limit?
Thanks
Please read the Dual ISO white paper to understand why it only works on a few camera models.
Quote from: PressureFM on March 13, 2014, 05:35:13 PM
Please read the Dual ISO white paper to understand why it only works on a few camera models.
I'm not too good at very technical stuff, but from what I can see in this doc http://acoutts.com/a1ex/dual_iso.pdf, nothing is said about dual ISO for video vs photography, and Dual ISO does work in picture mode for the 5D2.
Duel ISO just photo for 5d2, the CPU can not keep up.
Try HDR video-Raw it will come close to duel iso but at a cost of half of source frame rate.
The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.
So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.
This change was discussed here:
http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff
From a workflow point of view it would be better not having to crop in post.
Keeping things "simple" is important I think, to keep usability as high as possible.
Cropping exactly on the pixel can be tricky, and if you forget to crop and enlarge or sharpen the black border will effect the image.
If people worry about those lost pixels, they should buy a purpose build film camera with native Raw support.
My Vote for the max pixels 1888 ! I don't have problem cropping in post etc..
I vote for a resolution that requires less post manual adjustment and can be scaled equally so that NLEs can automatically scale to fit into "standard" aspect ratios.
Quote from: romainmenke on March 14, 2014, 10:31:30 PM
If people worry about those lost pixels, they should buy a purpose build film camera with native Raw support.
If people don't worry about those lost pixels, they should stick to their webcam
Please show us the difference in image quality between 1856 resized to 1920 and 1880 resized to 1920.
Blind test preferred.
The question is:
Quality (24 (effective) pixels more, no crop) VS A few seconds less clicking in post
I can understand, that any more steps in post drive you nuts - at least when you're in a pressure.
But I'm producing my own shorts (or other's as a camera man) without any time pressure in post. So, from this point of view, it would highly demand 1888 as for the higher resolution and no further crop.
Anyway, both options do not have much impact. But, for me it's only one thing, that drives me nuts:
Reviewing this decision from 10 years in the future, I will think: "I should have kept the reolution!" Because that is what lasts!
I repeat. Show me the difference. You need to convince me it's worth the extra coding effort.
There will be no visual effect on 1856 vs 1880.
I'd go for 1856, as it's a simple resize to 1920 or 1280 or whatever.
to pixel peepers, here's proof that there is virtually "NO" difference between 1856 and 1880 upscaled to 1920.
A downscaled image for posting:
(https://scontent-a-dfw.xx.fbcdn.net/hphotos-ash3/t1.0-9/1920453_452212864909503_2135285699_n.jpg)
A link to bigger image:
https://scontent-a-dfw.xx.fbcdn.net/hphotos-prn1/t31.0-8/1622320_452213114909478_1345754329_o.jpg
closer view of the vertical scales.
(https://scontent-a-dfw.xx.fbcdn.net/hphotos-frc1/t1.0-9/1922300_452216631575793_156180636_n.jpg)
Absolutely agree, have stopped using 1880 ages ago and never regretted it, no difference whatsoever.
Please make it 1856!
Having to re-align aspect ratio, as little as it may be.. Is just one more slow step in the post. I'd rather avoid it.
And thank you, Ted for pointing it out
I see a sharpness difference! 1880 is sharper with cleaner edges Then 1856.
1856 is softer image and never be as sharp as 1880, If you look closely at Ted's
Posted image you can really see this.
I Can't believe we are Really talking about this!!
This should be a No Brainer! Max. Resolution, since it take no extra performance out
Of the camera there is no need to limit the the frame size.
I just finish a shoot a few days back with nightly from feb16th
and filmed at 1872x936 continous . MLV is to a point now
That a can trust it not to fail. So anyone that's says that
There is no difference , you are just fooling you self in to thing it's OK.
And when come to Green Srceen/VFX you Need the Sharpes image
You can obtain .
I would be dishonest to say there is no difference. That is why I carefully wrote in my post, "VIRTUALLY NO DIFFERENCE" . ;)
And I can see it as well in the vertical scales between 600 and 700 lines. This is why I always rely on charts and just roll my eyes at those that say, "well, we don't shoot charts".
I have presented the exhibits/evidence in this "TRIAL" , I leave the judgement to the judge and jury. :D
And for kicks lets add how all that fare against a 2048 downscaled to 1920. :)
(https://scontent-a-ord.xx.fbcdn.net/hphotos-frc1/t31.0-8/1911130_452254731571983_377149549_o.jpg)
The reason for changing the resolution is portability: in order to keep 1872, one has to either add 5D2-specific exceptions in the code, or remove the safeguard in some other cameras (e.g. both 6D and 5D3 are known to crash on resolutions that are not multiple of 32 pixels, and this crash is a memory overflow that may result in anything, including permanent camera bricking).
I can choose between 1856 and 1888 with no coding effort. Between these 2 numbers there are no values that respect the alignment restrictions from EDMAC (it happens to work on 5D2, but I don't want to rely on this for all other cameras).
Camera-specific exceptions are not always desirable (they make the code harder to maintain and they have a negative effect on testing coverage). I've asked you to convince me that the extra effort to add the exception (and to maintain that exception from now on!) is worth it. I'm trying to simplify things, since this will reduce the burden of maintaining the code base (and this is one of these things that can be kept simple and portable).
Thanks A1ex for the explanation, now I understand what you tring to do
I will do some tests and post them, with my conclusion .
Quote from: a1ex on March 15, 2014, 06:53:43 PM
Camera-specific exceptions are not always desirable (they make the code harder to maintain and they have a negative effect on testing coverage). I've asked you to convince me that the extra effort to add the exception (and to maintain that exception from now on!) is worth it. I'm trying to simplify things, since this will reduce the burden of maintaining the code base (and this is one of these things that can be kept simple and portable).
There is a difference in quality (2048 looks amazing by the way) but for those who work with different cameras on one project I'd opt for 1856.
Camera-specific exceptions are also not desirable for post processing.
I'm not being lazy and I do care about quality, but keeping ML "simple" to use is important I think.
Also the 5D2 is no longer in production and keeping the code simple will make it more likely the camera will be supported by Magic Lantern for the coming years.
p.s. why is there so little moire in the 2048? Such a big difference between 2048 and the others.
As far as I can come with my fresh judgement about 1856/1872/1880, I agree with Reddeercity : I always shoot with the maximum resolution I can get (that's why I bought this 2000€ camera for a hobbyist, instead of 1000€ like my brain should have). I obviously continue to use RAW beside MLV (and because I don't really use audio) just to get 1880 instead of 1872. But I really understand the coder's positions and portabilities arguments. To be honest, I think I will stay with last releases as I have found some compromises and because the present work (performances / reliability) seem's to me already convenient.
And as always : a massive thank for that...
Quote from: romainmenke on March 15, 2014, 09:29:10 PM
p.s. why is there so little moire in the 2048? Such a big difference between 2048 and the others.
Probably because it's in 3x mode, so no line skipping
@ a1ex
When you ask if we want more pixels, the obvious response has to be yes, but ultimately i'm not a coder, and you know what you are doing.
So i'll go along with your choice either way !
Edit : and as pointed by xvince, we can still use previous builds for 1880
Quote from: a1ex on March 14, 2014, 09:55:26 PM
The horizontal resolution is restricted to multiples of 8 bytes and 16 pixels according to latest findings. This restriction is valid at least for 5D3 and 6D (didn't do much testing on other cameras), but I'd like to keep the code portable without camera-specific exceptions.
So, before including this change in nightly builds, I'd like to ask you which is better: 1888 with 8 pixels of black border that you will have to crop, or 1856 without any border pixels? Between these 2 values, there are no valid resolutions that respect the alignment restrictions.
This change was discussed here:
http://www.magiclantern.fm/forum/index.php?topic=3904.msg106087#msg106087
https://bitbucket.org/hudson/magic-lantern/pull-request/438/raw-recording-force-line-size-to-be/diff
In a world where Government and Self Victimization Citizen fight for paper and manufacturing jobs, you are a Breath of productivity. I will always vote for resolution but I'm grateful for the work you and the ML team do, so I'm good with your end decision.
Well, there are differences. But I guess, they barely exist in real circumstances.
Also, there's so much more degradation from Moiré or crappy lenses or ISO noise, etc.
I would vote for letting the developers decide, but would encourage to keep it simple. Exceptions might be added later (if really needed). If kept simple, more time can be put into other work, and the releases might get even more stable.
Again, thanks all devs for great work!
Quote from: poromaa on March 17, 2014, 09:28:12 AM
I would vote for letting the developers decide, but would encourage to keep it simple. Exceptions might be added later (if really needed). If kept simple, more time can be put into other work, and the releases might get even more stable.
Again, thanks all devs for great work!
What do mean, it's all readly stable !
The problem is with all the other cameras e.g. 5d3,6d . Read the link that a1ex talk about.
There asking the 5d2 user if there want 1888 or 1856 , Do Not leave This in the hands of the
Other people to decide for you ! Just because some more work , beside all that
The 5D Mark2 should be not limited , Its the Camera that Started
The DSLR revolution and gave Birth to Magic Latern ! So let make this camera
The best it can be even it we have to put more work in the code. It's well worth the extra
effort .
P.S. My test for this are still on the way
(https://scontent-a-ord.xx.fbcdn.net/hphotos-frc1/t31.0-8/1911130_452254731571983_377149549_o.jpg)
Looking to ted's test, I thought about VAF on 5D2 and the difference between 2048 crop downscale and the 2 other non crop resolution. The aliasing seems to me really so huge and I was asking myself in which ways decreasing resolution for upscaling will play.
To me the 1880 looks sharper than 1856 and 2048 look clearly sharper than the 2 others. I made some tests in RAW mode last summer with an old 600x compact flash @ around 1580 then upscale to 1920. the diffence with 1880 upscaled was really huge.
I agree that between 1856 and 1880, the difference is not important, but if I'm asked between 2 resolutions : I definitively vote for the maxima.
if the only downside of the larger 1880 is the black column-edge pixels, any mlv converter could just have an auto-detect camera type, and when its a 5d2, crop the needed empty columns out to fit a desired ratio. or perhaps theres some type of plugin for premiere that intelligently doubles-up an images edge column pixels to fill in the adjacent black columns.
Quote from: terranaut on March 17, 2014, 10:40:55 PM
if the only downside of the larger 1880 is the black column-edge pixels, any mlv converter could just have an auto-detect camera type, and when its a 5d2, crop the needed empty columns out to fit a desired ratio. or perhaps theres some type of plugin for premiere that intelligently doubles-up an images edge column pixels to fill in the adjacent black columns.
Absoluteley! Cropping the image before encoding to dng is easy to program and computed instantly.
And if I got a1ex right, it's no special coding effort to go for 1888. So, yeah I vote for that!
I'm also looking forwand for the tests from reddeercity.
P.S.: I don't see much chances for a premiere plug-in. First: You'll have to adopt it to any new version of premiere. And then? What about Finalcut or vegas or after effects or...
The faster, easier, simply better way will be to crop the borders right in the beginning while converting to dng. Then there's one program and not dozens of plug-ins.
So does an added resolution also help if in case we use a VAF filter? I tested it and also this time I also included how the max crop mode which is 2144x1076 compares downscaled.
This is a lower res image:
(https://scontent-b-atl.xx.fbcdn.net/hphotos-prn2/t1.0-9/1468722_453226608141462_1768299338_n.jpg)
Click this to view higher res image.
https://fbcdn-sphotos-b-a.akamaihd.net/hphotos-ak-ash3/t31.0-8/10012698_453226301474826_470179409_o.jpg
QuoteThe problem is with all the other cameras e.g. 5d3,6d . Read the link that a1ex talk about.
There asking the 5d2 user if there want 1888 or 1856 , Do Not leave This in the hands of the
Other people to decide for you ! Just because some more work , beside all that
The 5D Mark2 should be not limited , Its the Camera that Started
The DSLR revolution and gave Birth to Magic Latern ! So let make this camera
The best it can be even it we have to put more work in the code. It's well worth the extra
effort .
Well, if I had to choose between some few extra pixels and perhaps higher dynamic range, faster recording (continous as say 1856 - I have a 1000x card but it still stops sometimes), shutter-free full-res timelapse etc I would go for the latter. That means, any time the developer needs to put into this few extra pixels is lost time in other development areas. Im just saying that the difference seems too small for me to care. Anyway its my oppinion - thats what forum are for :)
cheers
1856 will still be there so no worry about performance , there saying we will Loose
The upper resolutions 1880, 1872 no more ! You are missing the point here there will be no
Loss to Photo functions and have nothing to do with that Just Raw Video, That's what is
Is all about !
Hi, and first, a massive THANKS to all the Devs who have made RAW on the 5D2., possible.
However, I am alarmred with the 'idea' of downgrading the 5D2 to only 1856 !
I have always believed that the core of Magic Lantern, was the pursuit of quality, not convenience.
Unified ? Mass marketing - Consumer - " One size fits all".
I bought a 5D2 because of Magic Lantern, not because it was a Canon.
I am therfore sadened by the idea that it maybe downgraded, to 'fit' in with other cameras.
There is no argument, that can show that less pixels are, 'the same', or, better than more.
In pure science, and in the 'real' world, this is NONsense.
I offer my total support to Reddeercity, who speaks sense.
Quality first, Please !
FYI, the very existence of raw video and all other features available on most cameras is based on portable code (unified, one size fits all).
I could have easily hardcoded the raw recording code to work only on 5D3, and fully optimize it for that camera only, since it has the most potential (especially regarding write speeds), but I chose to make the code portable. Yes, this means the code may not be fully optimized for any particular camera, but you have RAW on nearly all cameras that ML runs on. Would it have been better to have RAW only for 5D3?
If you are alarmed by the idea of us (who gave you all this stuff for free) trying to make our life easier by simplifying the code, feel free to get your hands dirty and implement a clean solution. Complaining without logical arguments will not do, and will only encourage us to stop the raw video development and focus on something else.
Quote from: 1880 on March 20, 2014, 11:55:04 PM
Hi, and first, a massive THANKS to all the Devs who have made RAW on the 5D2., possible.
However, I am alarmred with the 'idea' of downgrading the 5D2 to only 1856 !
I have always believed that the core of Magic Lantern, was the pursuit of quality, not convenience.
Unified ? Mass marketing - Consumer - " One size fits all".
I bought a 5D2 because of Magic Lantern, not because it was a Canon.
I am therfore sadened by the idea that it maybe downgraded, to 'fit' in with other cameras.
There is no argument, that can show that less pixels are, 'the same', or, better than more.
In pure science, and in the 'real' world, this is NONsense.
I offer my total support to Reddeercity, who speaks sense.
Quality first, Please !
The one argument is for the devs who put their time into creating ML and maintaining out of production camera's.
I would ask you to look at the big picture. Camera's can be rented now with ML and big productions use many different camera's, giving the 5D2 footage with black borders is like killing it. People will just choose other camera's.
Not only will the 1888 exception make the camera less desirable for recording but if one day the devs decide they will no longer support the 5D2 because of exceptions like this, you will be forced to upgrade. That is what I think the essence of ML is. Upgrading existing gear through firmware updates, unlocking and creating features, so you don't have to buy new gear every year.
Future first!
Quote from: a1ex on March 21, 2014, 12:50:37 AM
If you are alarmed by the idea of us (who gave you all this stuff for free) trying to make our life easier by simplifying the code, feel free to get your hands dirty and implement a clean solution. Complaining without logical arguments will not do, and will only encourage us to stop the raw video development and focus on something else.
I was thinking the same thing!
It might be worth testing the edmac flags that caused this resolution resolution restriction in general.
uint32_t dmaFlags = 0x40001000; // "enhanced"
vs
uint32_t dmaFlags = 0x20001000; //Original
I recorded some more on 7D/6D and not really sure about the improvement... On 6D ended up struggling with 720P and indicators took a long time to say continuous. Interestingly though at a higher res I got a few, maybe 20 more frames. 7D took longer to reach continuous too and write speed jumped all over the place. Slurp still seems like its set to the original flags and I think I may have changed them to the "enhanced" ones by mistake, leaving the originals for normal raw. Maybe the restriction + original flags are the best as it exposed some underlying problem and would explain why some resolutions performed "better".
What kind of room there is for optimization for 5DmkIII? Just interested and if someone has capacity to pick up and implement those ;)
Is alex talking of code options or specific hardware related ones (like sensor etc)
More accurate prediction of file write speeds, low-level file I/O, fully exploit the dual card slot, modify the source resolution to avoid the EDMAC copy step, hardcode all raw parameters, fine-tune task priorities, stop/slowdown Canon tasks not related to raw recording, refactor ML to use fewer tasks, optimize raw recording code to reduce idle times, stop YUV LiveView code, find more unused memory areas, find out how to change YUV resolution and crop window for a more efficient preview, exploit external storage mediums... I could fill a page with this stuff.
Some of these things are not camera-specific (e.g. task refactoring or code optimization). Others, like write speed prediction, may benefit from a mathematical model tailored to each camera, but I'll prefer a general solution (one size fits all, with automatic tuning). Others are highly camera-specific and I prefer to avoid them, unless the tweak brings significant improvement without major side effects.
To be honest, there's something I don't get : what the trouble to just add 1888 (if it's not too much complex to add in code) : All people who do not want to post-prod crop still can use 1856, and others can use max resolution ? (perhaps some notice in the readme file to warn about black border on 5D2, and that's all)
To a1ex :
Just to be precise : Actually, I (we ?) don't know clearly the history of ML developpement team and I can't really figure what's the involvement or deserving of every dev' in digging Canon code. BUT I can clearly figure that for the original core of the team it can be very painfull to see other people forking, using the original code you'd share, without following your guidelines, and I clearly understand your concern about portability.
I REALLY don't want to be fresh or misrepectfull about your work, I've only tried to honestly answer your question about max resolution on 5D2.
It looks like all Hope is Lost for the 5D Mark 2 this sadden me Greatly ! :-[
What camera will be Next , All for the greater good of the 5D Mark 3 !
I guess in the end the dev. can write all the code there want but, if not one uses
It what good is it.
I thought Magic Lantern was user base group who all have say in the end result
Maybe I'm wrong.
Quote from: a1ex on March 15, 2014, 06:53:43 PM
I can choose between 1856 and 1888 with no coding effort. Between these 2 numbers there are no values that respect the alignment restrictions from EDMAC (it happens to work on 5D2, but I don't want to rely on this for all other cameras).
Camera-specific exceptions are not always desirable (they make the code harder to maintain and they have a negative effect on testing coverage). I've asked you to convince me that the extra effort to add the exception (and to maintain that exception from now on!) is worth it. I'm trying to simplify things, since this will reduce the burden of maintaining the code base (and this is one of these things that can be kept simple and portable).
@a1ex,
Just to clarify, is that a typo you wrote 1888 or does the 5D2 actually can do 1888 aside from 1880 ? ;)
Here's my take on the resolution issue since you wrote it can be done with "no coding effort".
I can understand the burden from the developer's side in maintaining camera specific code. However, we must also consider that the cameras themselves were never really intended to perform similarly. Each has its own strengths. So at some point in making code, I think one should consider allowing each camera model stand out and maximize what it can truly be capable of and not sacrifice it for the sake of efficiency. I think you can still squeeze out some "juice", whatever that may be, from this old lady the 5D2, and I personally think that it should be allowed to. Other cameras can't do it. The 7D for instance, may not have the resolution the 5D2 has in 1X mode, however it shines in other features like higher frame rates and higher resolution in 3X mode. And just as the 7D is allowed to shine in that area, I believe the 5D2 should also have its niche.
The Magic Lantern project is for the community. It is not developed solely for individual users.
If an individual wants a feature implemented, then an individual is free to make his/her own modifications to the source code. This is an open source project after all.
You are granted no rights with Magic Lantern. This includes the right to complain, in a manner that is unbecoming to the time and effort that developers place into maintaining and enhancing this project.
a1ex could have simply implemented any resolution he saw fit, instead, he choose to bring the decision to the forums, for open discussion by members.
Well i though that's what we are doing, discussing this issue .
And from what I read here the community of 5d2 users would like to keep
The upper resolutions in the new version of the code.
@Ted no that's not a miss print, that's right 1888.
Quote from: romainmenke on March 21, 2014, 12:57:47 AM
Not only will the 1888 exception make the camera less desirable for recording but if one day the devs decide they will no longer support the 5D2 because of exceptions like this, you will be forced to upgrade. That is what I think the essence of ML is. Upgrading existing gear through firmware updates, unlocking and creating features, so you don't have to buy new gear every year.
Future first!
Future first, but that's also true for image quality!
Quote from: xvince1 on March 21, 2014, 10:01:30 AM
To be honest, there's something I don't get : what the trouble to just add 1888 (if it's not too much complex to add in code) : All people who do not want to post-prod crop still can use 1856, and others can use max resolution ? (perhaps some notice in the readme file to warn about black border on 5D2, and that's all)
Folks, there's a solution everyone would be happy with:
You will always have to convert your footage (*.raw or *.mlv), since there's absolutely no hope, that these formats will be supported by any major NLE. You have to convert it!
So, what's wrong about the idea to crop 1888 to 1880 while converting to DNG? I guess nothing!
Besides: It's way harder to implement such resolution differences into the camera (due to performance issues, etc.). But in post, where you have to convert anyway it's equal if it takes a hundredth second more for each frame!
So, why not do it this way?
Was going to fuel the discussion with some real world tests.
But there is no more 1880 res in the latest nightly.
How far do I have to go back to get that option?
I like the latest nightly by the way.
Preferred settings for tests?
Oct 24th Raw a.d. Build has 1880, I still use this built as
It is the fastest built to date for the 5d2.
They never being able to match this build since then it being down hill
For performance for the 5d2. FYI I can record 1880x1058 continuous.
So you better download it before they remove all old builds !
Still have that one.
I keep an extensive archive of all software I've ever used, so no worries there.
Quote from: reddeercity on March 22, 2014, 04:12:12 PM
Oct 24th Raw a.d. Build has 1880, I still use this built as
It is the fastest built to date for the 5d2.
They never being able to match this build since then it being down hill
For performance for the 5d2. FYI I can record 1880x1058 continuous.
So you better download it before they remove all old builds !
1880x1058 ? so 16:9 ?
Can you post what settings you were using? or pm me
blind test
tech specs:
latest nightly vs oct 24
1856 vs 1880
lens: 100mm F2.0 (really sharp if you don't know it)
indoor shots at F8
outdoor at F4 (couldn't reach ideal F8)
Iso 100
1/30s
Tripod mounted
Manual focus
Raw_rec => raw2dng => acr (only white balance) saved as 1080p
we'll name them top to bottom:
a1 / a2 (lots of detail far away)
b1/ b2 (dirty pillow test)
c1 /c2 (dark shiny textures)
please let me know which one is 1880
(http://www.romainmenke.com//ml/comp.jpg)
full size images
c1
(http://www.romainmenke.com//ml/dark-texture-test0.jpg)
c2
(http://www.romainmenke.com//ml/dark-texture-test1.jpg)
b1
(http://www.romainmenke.com//ml/dirty-pillow-test0.jpg)
b2
(http://www.romainmenke.com//ml/dirty-pillow-test1.jpg)
a1
(http://www.romainmenke.com//ml/lots-of-bricks-test0.jpg)
a2
(http://www.romainmenke.com//ml/lots-of-bricks-test1.jpg)
Quote from: Kharak on March 22, 2014, 04:39:39 PM
1880x1058 ? so 16:9 ?
Can you post what settings you were using? or pm me
yes, 16x9 . I use Small raw for photo in canon menu
Hacked preview ,with white rectangle frame, small hacks on
No overlays of course when recording raw, on a "freshly" formatted card.
I never change formats without formatting the card, I think this makes it
More stable & faster all on Lexar 1000x 64GB, 32GB .
Quote from: romainmenke on March 22, 2014, 06:44:38 PM
please let me know which one is 1880
Please let me know which one is 1880
@Reddeer
You mentioned card warm up off in a previous post as you think Lexar do not benefit from this? Still stands?
Hi everybody !
I need your help because I can not start a RAW pack! I succeeded it a few months ago (I can not find the version).
With 63b2f145cb3b version of February 14, when I run the module, it noted me "We Will load" even when I restart the camera. Whatever the module.
I respect the instructions carefully.
Does anyone have any idea where the problem is? Maybe give me a version where the RAW (mlv or not) module are already running.
Thank you for your answer!
Thibaud
Delete card's ML directory, copy contents of latest build to card (overwriting AUTOEXEC.BIN) and try again.
To me :
C1 - 1880 (The BG's screw looks sharper to me)
B1 / B2 - can't figure out
A1 - 1880 (upper windows looks sharper to me)
Yes I agree, it's very difficult to be shure and I may be easily wrong, but I stay my point : what the trouble to keep the max resolution available if there's no coding effort ?
@romainmenke
I know the embedded images you posted are relevant to the current discussion, but due to the forum posting rules of having a max 900pixx900, please post links to the images instead or a 100% crop of the image.
Thanks,
And yeah, there is only a very slight difference between 1880 and 1856 based on those images.
couldn't figure out how to embed, so i hosted them on my website and posted a link.
Is that what you mean?
edit: just checked the rules.
sorry your right, will keep that in mind in the future.
Do you want me to change them?
Quote from: romainmenke on March 23, 2014, 12:27:00 AM
couldn't figure out how to embed, so i hosted them on my website and posted a link.
Is that what you mean?
Yes, but what you did is actually "embed" when you use the "Insert image" function. So either you insert a 900x900 image or just copy paste the url of the image directly from where they are originally uploaded.
Like this:
https://fbcdn-sphotos-b-a.akamaihd.net/hphotos-ak-ash3/t31.0-8/10012698_453226301474826_470179409_o.jpg
Thanks.
Quote from: Kharak on March 22, 2014, 07:39:56 PM
@Reddeer
You mentioned card warm up off in a previous post as you think Lexar do not benefit from this? Still stands?
Yes and no, what I mean is I see no benefit's to card warm ups to continuous record but, as the card gets Hotter
It seems to stabilizes at a higher writing speeds with less buffering. I really see it when the camera hit about 64-67 degree C
and in Crop mode when I push it at 2048x1024 and can get about 2000+ frames. But I think when I change from small jPeg photo in
the Canon menu to small raw that's when I Notice a Big difference in performance. I would say 15-20% even to be the
difference between continuous and Not.
With the Oct24th build of course
@romainmenke
I'll give it a shot: a1,b2,c2
They are indeed extremely difficult to tell apart and my choices are without much confidence. I didn't do any zooming though, but had to look closely. The false color has a much greater negative effect than any loss in resolution.
Quote from: reddeercity on March 23, 2014, 12:39:45 AM
I push it at 2048x1024 and can get about 2000+ frames. But I think when I change from small jPeg photo in
the Canon menu to small raw that's when I Notice a Big difference in performance. I would say 15-20% even to be the
difference between continuous and Not.
With the Oct24th build of course
Are the Lexar Cards really that magic or am I doing something wrong? I got a little excited and tried to test things out again but can't get anywhere near those speeds, i have to step down to 1728x972 to shoot continuous 16:9 on a Transcend 32gb 1000x. Or instead I shoot 1880x800 anamorphic and upscale to 1920x816 for 2.35. Last summer I assumed Transcend had really good build quality, but does the brand of the card make that much of a difference?
Tried on both Oct24th Build and the Newest Build
You can also use the width tag
[img width=900]
Quote from: JosiahDuncan on March 23, 2014, 03:57:47 AM
Are the Lexar Cards really that magic or am I doing something wrong? I got a little excited and tried to test things out again but can't get anywhere near those speeds, i have to step down to 1728x972 to shoot continuous 16:9 on a Transcend 32gb 1000x. Or instead I shoot 1880x800 anamorphic and upscale to 1920x816 for 2.35. Last summer I assumed Transcend had really good build quality, but does the brand of the card make that much of a difference?
Tried on both Oct24th Build and the Newest Build
Yes I thinks so, Lexar 1000x cards seem to work better with 5d2, but my 64GB card is faster then my 32GB.
I always get better number then most, I usually shoot at 2:1 or 1.85:1 (1873x936 mlv & 1880x1014 raw)
Crop mode for continuous at 2048x930 (that's my favorite size)
*Note* even thou I can record at 16x9 (large frames 1880,1872) its not stable with HDMI devices, I choose to use 1.85:1 or 2:1
with those sizes . :)
Edit: Also check your card for being fragmented , I notice when the card slow down a little it's always fragmented by about 30%.
If you are working in Windows , I do a disk defragment & the speed always return . FYI the maximum write speed I have seen on
my 5d2 with Lexar 1000x is 79.8 MB/s ,but only in Crop mode 1:1 is around 75 MB/s on average.
For MLV try the Nightly Build from Feb16th, that seems to be the Fastest I have found to work with 5d2 @ 1872x936 2:1 .
That's the one I use for paid work, after that date things started to slow down and became unstable.
Quote from: Audionut on March 23, 2014, 04:03:43 AM
You can also use the width tag
[img width=900]
Thx for the edit.
spoiler: http://romainmenke.com/ml/a.html (http://romainmenke.com/ml/a.html)
pored it into a little html page. not perfect (the scroll doesn't follow) but the only way I could let you see them on top of each other in 5 minutes work.
another confession: I scrambled the naming in both sets I posted. Since no one noticed that, I'd say there is virtually no real world difference between 1856 and 1880.
crops:
a1 oct 24 1880
a2 nightly 1856
b1 nightly 1856
b2 oct 24 1880
c1 oct 24 1880
c2 nightly 1856
full size:
a1 nightly 1856
a2 oct 24 1880
b1 nightly 1856
b2 oct 24 1880
c1 nightly 1856
c2 oct 24 1880
Stating uppon 3 screens...
Aside that, I'm not a pixel peeper, but 1880 to 1856, there's a loss of 24 pixels (something about 1.3%). It's very few, I definitly agree, but there's a loss... what the point ?
As it's seems possible (and relatively easy to add), I still don't understand why not including the option ?
Like it was stated before the choice is not between 1856 an 1880.
The choice is between simple implementation for all camera's or an exception for the 5d2.
This exception comes without real coding effort now but makes it harder to maintain Raw for the 5d2 in the future.
The simple implementation has a very slight loss of resolution but makes ML easy to maintain, bug test, ....
So if there ever is a bug in raw video or a new feature there is no need to wait for the 5d2 port. It will just be there from the start.
a1ex asked for proof that 1880 is the way to go and worth all the extra trouble.
I think 1856 is just as good as 1880 even if logic says that there is loss of resolution and quality.
the loss is 1,0265 percent
Quote from: a1ex on March 15, 2014, 06:53:43 PM
The reason for changing the resolution is portability: in order to keep 1872, one has to either add 5D2-specific exceptions in the code, or remove the safeguard in some other cameras (e.g. both 6D and 5D3 are known to crash on resolutions that are not multiple of 32 pixels, and this crash is a memory overflow that may result in anything, including permanent camera bricking).
I can choose between 1856 and 1888 with no coding effort. Between these 2 numbers there are no values that respect the alignment restrictions from EDMAC (it happens to work on 5D2, but I don't want to rely on this for all other cameras).
Camera-specific exceptions are not always desirable (they make the code harder to maintain and they have a negative effect on testing coverage). I've asked you to convince me that the extra effort to add the exception (and to maintain that exception from now on!) is worth it. I'm trying to simplify things, since this will reduce the burden of maintaining the code base (and this is one of these things that can be kept simple and portable).
In fact, there's something to clarify : I understand that exceptions where to maintain 1872, but maybe I've missed something in the third part...
No you are right, the big camera specific exception refer to 1872.
I understood that 1888 with the black borders was also an exception.
@alex Is there no difference in coding now or in foreseeable the future between 1856 and 1888?
If there is no coding difference and since no one minds about removing those borders in post, it would be best to have 1880.
And if keeping 1888 may slowdown RAW/MLV developpement for 5D2, I completely agree to only keep 1856...
It will not make a difference now, all the effort and time it takes to make
All these tests Has come on Deaf Ears! Not matter how much sense it makes to keep
1888 it really come down the effort or the lack of effect on dev. part .
As users we suffer at the hands of miss direction by the form higher up.
So for me Magic Latern Stops at Feb16th for MLV and Oct24th for Raw
As these builds Can Not be improve on as they are maximized right now .
I suggest we keep emotions in check and keep things objective and technical.
We are asked for visual proof not feelings. We've presented charts and blind tests. Let us wait for the decision from the developers.
The charts show what is there and what is not and what is irrelevant. Until then, lets keep the drama out of a technical thread.
Interesting, so I got 2/3 correct on the test. I'm surprised that I guessed sample "a" wrong. Even after comparing the "side-by-side" shots, my eyes are still biased toward the 1856 shot :o.
the only thing i can think of which would be helpful to have higher res, is doing software stabililzation. i think i need about 3% edge area to get my preferred stabilization, so even the 1% gain in pixels would be handy, but not dire.
Quote from: terranaut on March 23, 2014, 09:17:45 PM
the only thing i can think of which would be helpful to have higher res, is doing software stabililzation. i think i need about 3% edge area to get my preferred stabilization, so even the 1% gain in pixels would be handy, but not dire.
true, hadn't thought about that.
Quote from: Yoshiyuki Blade on March 23, 2014, 09:00:48 PM
Interesting, so I got 2/3 correct on the test. I'm surprised that I guessed sample "a" wrong. Even after comparing the "side-by-side" shots, my eyes are still biased toward the 1856 shot :o.
if you look closely at the top connectors of the grip you can see a difference in sharpness
Quote from: romainmenke on March 23, 2014, 09:19:43 PMif you look closely at the top connectors of the grip you can see a difference in sharpness
That's sample "c." You have it in reverse order for the full shots :P. The one I have the most difficulty telling apart is the building shot.
Quote from: Yoshiyuki Blade on March 23, 2014, 10:06:38 PM
That's sample "c." You have it in reverse order for the full shots :P. The one I have the most difficulty telling apart is the building shot.
haha, in the building shot if you look at the paint strokes on the bricks you can see a difference, they have a bit more contrast.
Quote from: a1ex on March 15, 2014, 06:53:43 PM
I can choose between 1856 and 1888 with no coding effort.
...and it's also no coding effort to discard 8 pixels while converting to dng. You wouldn't even realize it!
This way, no one has to crop anything actively in post! It's simply done in background in the ever necessary converting step.
Seems like a nobrainer to me.
Quote from: guentergunter on March 24, 2014, 08:39:02 AM
...and it's also no coding effort to discard 8 pixels while converting to dng.
Can you describe the process?
What gets me to vote for 1888 is if the raw/mlv2dng discards those 8 Pixels.
that would be awesome!
@Audionut
I have less than zero programming skills, but couldn't a 1880 limit be set in the raw2dng, controlled by a center point? This could result in having to use two different versions of raw/mlv2dng. One specific for 1888 crop and another for all the other resolutions. I understand that creating UI's require quite some work.
But if I only got a raw/mlv2dng I can exchange the one in RAWanizer and some other batch converters eliminating the need to create a UI.
I'm new to Magic Lantern, I'm using it to shoot RAW on a 5dII. This results in a spectaculair quality, very exciting.
I can shoot continously RAW 1880*940 2:1. This can result in multiple large files of 4 Gb which have to be concatenated on a PC using a script like
cd C:\Users\my_destination_folder
copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
I'm about to create a bat file for PC that does some of the typing for me: like concatenating all RAW files in a directory, use raw2dng and clean up all files except the dng files. Since it's 15 years ago since my last bat file programming does anybody already have a bat file I could use?
Another question: I'm using After Effects to import the DNG files, which is a great way of importing, using camera RAW. I render a losless AVI file to be able to process further in Premiere Pro. It takes over one hour to create a losless AVI from 7549 frames. Is this a normal duration you think on new hardware? Are there any alternatives using Adobe software?
Quote from: elfrabo on March 24, 2014, 07:09:45 PM
I'm new to Magic Lantern, I'm using it to shoot RAW on a 5dII. This results in a spectaculair quality, very exciting.
I can shoot continously RAW 1880*940 2:1. This can result in multiple large files of 4 Gb which have to be concatenated on a PC using a script like
cd C:\Users\my_destination_folder
copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
I'm about to create a bat file for PC that does some of the typing for me: like concatenating all RAW files in a directory, use raw2dng and clean up all files except the dng files. Since it's 15 years ago since my last bat file programming does anybody already have a bat file I could use?
Another question: I'm using After Effects to import the DNG files, which is a great way of importing, using camera RAW. I render a losless AVI file to be able to process further in Premiere Pro. It takes over one hour to create a losless AVI from 7549 frames. Is this a normal duration you think on new hardware? Are there any alternatives using Adobe software?
I'm not sure what "concatenating" means, but I think you mean merging the spanned Raw files in to one raw file.
You can download software that does this for you. For raw_rec I recommend RAWanizer. http://www.magiclantern.fm/forum/index.php?topic=5557.0
For mlv_rec MLVBrowseSharp http://www.magiclantern.fm/forum/index.php?topic=8447.0
Quote from: elfrabo on March 24, 2014, 07:09:45 PM
I'm new to Magic Lantern, I'm using it to shoot RAW on a 5dII. This results in a spectaculair quality, very exciting.
I can shoot continously RAW 1880*940 2:1. This can result in multiple large files of 4 Gb which have to be concatenated on a PC using a script like
cd C:\Users\my_destination_folder
copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW
I'm about to create a bat file for PC that does some of the typing for me: like concatenating all RAW files in a directory, use raw2dng and clean up all files except the dng files. Since it's 15 years ago since my last bat file programming does anybody already have a bat file I could use?
Another question: I'm using After Effects to import the DNG files, which is a great way of importing, using camera RAW. I render a losless AVI file to be able to process further in Premiere Pro. It takes over one hour to create a losless AVI from 7549 frames. Is this a normal duration you think on new hardware? Are there any alternatives using Adobe software?
Use the MLV Viewer to view .mlv & .raw files on windows and to extract DNG's,there is no need to use command line download link below
http://upload.g3gg0.de/pub_files/09852505c6c352fdaf7fe4eddec48788/MLVViewSharp.zip
If you go to the first page of this thread I have a posted video tutorial with MLV View Sharp in action.
Try the A.E. Premiere Pro work around, I did a short video tutorial, this way you work with the raw dng's directly in Premiere Pro without pink HI-lights. link--> http://vimeo.com/79705806
I also think you my have to upgrade your computer performance, Being A.E. love Ram and Lots of GPU.
With about 8000 frame 1872x936 23.976 It takes about 15-20 min to make a video file on my mac to ProRes4444 with my PC the time is about the same but there
I Use QT Blackmagic RGB codec with trillion's + color.--> download link http://software.blackmagicdesign.com/DesktopVideo/Blackmagic_Desktop_Video_Windows_10.0.zip
If you like using AVI's try the AJA pc windows Codec there are about the best out there for a digital intermediate.
A speed Tip for A.E. , before you render press the Cap Lock key, that disables the viewer in A.E. and give a lot more speed !
PC I run a 8 core AMD overclock to 4.7Ghz cpu, 16GB dual channel ram ssd OS drive, raid0 , 2x-gtx580 1.5 ram each = 3GB Vram
On the MAC side I run a Mid2010 MacPro with a PC GTX 760 graphics card etc..
Quote from: Audionut on March 24, 2014, 08:58:03 AM
Can you describe the process?
I'm no programmer, but I did some Java, C and VHDL at university. That's enough to know what's possible and to estimate the effort.
If you're already in C++ (or any other language), you could e.g. implement it with a while loop:
Given is the 2D pixel array (our frame) 'MLV_pic' with 1888 of width (thus 4 black pixels on left and right).
int crop()
{
x = 4;
while (x <= 1884)
{
DNG_pic[x-4][y] = MLV_pic[x][y];
x++;
}
}That will give you the 2D pixel array 'DNG_pic' with 1880 of width and without the black pixels.
What about the checks for model and resolution?
Thanks for taking the time to reply with useful information. But the question was more rhetorical in nature. (Where's the smiley for that)
The entire point for the original question (1888 vs 1856), was to minimize code that is specific to a model. Here, you want to add a bunch of code, specific, not only to a model, but to the resolution it records also.
Cropping is a basic PP process. It takes 1 line in an AVS script for example.
Quote from: Audionut on March 25, 2014, 02:15:39 AM
The entire point for the original question (1888 vs 1856), was to minimize code that is specific to a model.
Here, you want to add a bunch of code, specific, not only to a model, but to the resolution it records also.
No, according to a1ex, it's no special effort to implement 1888 into ML/MLV and maintain it.
So, the question now is: what to do with our 1888 mlv frames?
Quote from: Audionut on March 25, 2014, 02:15:39 AM
What about the checks for model and resolution?
E.g. "RAWMagic" from Thomas Worth (Click (http://www.magiclantern.fm/forum/index.php?topic=6218.0)) already does check the camera model. So this little while loop could possibly be easily implemented.
The same goes for raw2dng or mlv2dng.
By the way: mlv comes with metadata about the camera model.
Quote from: Audionut on March 25, 2014, 02:15:39 AM
Cropping is a basic PP process. It takes 1 line in an AVS script for example.
I agree, that it's very little effort.
But, I would rather crop in mlv2dng / raw2dng / RAWMagic / etc., since that doesn't need the user to take action.
To summarize the above 1888 way:
- a minimum effort for ML is needed.
- all dng converters need to add some simple lines into their routines; since checking for the camera model is already implemented or can easily be done due to the given metadata.
I would say we leave this be for a bit until we hear back from a1ex.
He is the only one who can say it is no trouble coding the 1888.
In the mean while has anyone checked with the guys who developed mlv2dng / raw2dng / RAWMagic /....
Might be interesting too know all the sides to this question before we (users) start deciding things we cannot help with.
Quote from: a1ex on March 15, 2014, 06:53:43 PM
I can choose between 1856 and 1888 with no coding effort.
But you're right. Let's wait for the other side.
I asked already in the RAWMagic threat for a developer statement. Maybe someone with more inside in the other converters may just do it there...
that must be the most quoted sentence ever ;)
Probably because the lack of effort to pick between resolutions, is being construed to mean, how far away is the NLE. :P
Quote from: Kharak on March 24, 2014, 08:20:01 PM
I'm not sure what "concatenating" means, but I think you mean merging the spanned Raw files in to one raw file.
You can download software that does this for you. For raw_rec I recommend RAWanizer. http://www.magiclantern.fm/forum/index.php?topic=5557.0
For mlv_rec MLVBrowseSharp http://www.magiclantern.fm/forum/index.php?topic=8447.0
Thanks a lot fot your sugestions, I will try them for sure
Quote from: reddeercity on March 24, 2014, 08:22:24 PM
Use the MLV Viewer to view .mlv & .raw files on windows and to extract DNG's,there is no need to use command line download link below
http://upload.g3gg0.de/pub_files/09852505c6c352fdaf7fe4eddec48788/MLVViewSharp.zip
If you go to the first page of this thread I have a posted video tutorial with MLV View Sharp in action.
Try the A.E. Premiere Pro work around, I did a short video tutorial, this way you work with the raw dng's directly in Premiere Pro without pink HI-lights. link--> http://vimeo.com/79705806
I also think you my have to upgrade your computer performance, Being A.E. love Ram and Lots of GPU.
With about 8000 frame 1872x936 23.976 It takes about 15-20 min to make a video file on my mac to ProRes4444 with my PC the time is about the same but there
I Use QT Blackmagic RGB codec with trillion's + color.--> download link http://software.blackmagicdesign.com/DesktopVideo/Blackmagic_Desktop_Video_Windows_10.0.zip
If you like using AVI's try the AJA pc windows Codec there are about the best out there for a digital intermediate.
A speed Tip for A.E. , before you render press the Cap Lock key, that disables the viewer in A.E. and give a lot more speed !
PC I run a 8 core AMD overclock to 4.7Ghz cpu, 16GB dual channel ram ssd OS drive, raid0 , 2x-gtx580 1.5 ram each = 3GB Vram
On the MAC side I run a Mid2010 MacPro with a PC GTX 760 graphics card etc..
Thanks a lot fot your suggestions, I will check them out next weekend
I realize we are all resolution junkies here but I seriously doubt anyone could pick out a 1856 frame upscaled to HD vs a 1880 frame upscaled to HD. It is less the 2% difference in resolution. I bet if someone posted 10 shots with 9 1856 and 1 that was 1880 scaled to HD you wouldn't be able to pick out the 1880. Pixel peeping at %200 percent is virtually unnoticeable even when toggling back and forth, I can only see the slightest difference it very high contrast areas. Everywhere else shows no change and I certainly cannot say that one looks better than the other. I had to constantly remind myself which on was which when I was trying to determine if one was better. I have 20/15 vision BTW.
The difference in quality is so tiny it really isn't even worth the extra effort, I don't think it should even be called a quality difference just a difference. I would recommend shooting 1856 to get longer record times and smaller file sizes - 1856 is continuous and 1888 is not after all. I know there will be the "I want the highest resolution and best quality possible even if it is 1 pixel" replies, but in reality the quality difference is only in your head. If you disagree show us an example of how much better it is, if you can.
1880 is continous BTW, so that didn't wash.
1880 at 16:9 is nearly 80 MB/s at 24P, I have never seen anyone get that continuous on a MKII. Not to mention on MLV with audio won't be. That was the least important thing since the point was if the little bit of extra resolution was worth the effort. If you really want it they can probably add in both and you can crop off the extra 8 pixels in post.
My point is that the dev's do this work for us in their spare time and if they want to make things easier for them by sacrificing some resolution that is basically unnoticeable, maybe that is the best thing for ML.
No not at 16x9 but 1:85.1 @ 75MB/s ,16x9 I get about 3500 frames
The point is they could easily support the max resolution by there own words.
I don't think any camera should be limited because of short comings of
another.
@a.d., pravdomil or ted: feel free to create a thread in the Raw Video section, for Magic Lantern. This section will be shutdown, as announced (http://www.magiclantern.fm/forum/index.php?topic=11082) last week.
Third party builds are no longer accepted on this forum, so please contribute your changes to the main repository.
Dear 5DmkII Users,
Most of the essential features introduced by a.d. and pravdomil have been reviewed and were eventually integrated into the ML nightlies. Some are still being reviewed, new improvements from 3rd party developers are going to be implemented in a new method that the developers have agreed upon that will no longer necessitate the need for a third party section.
All 5DmkII with Magic Lantern related inquiry or posts are now directed to go here: http://www.magiclantern.fm/forum/index.php?topic=11205.0
It is an easy to find sticky under the Raw Video Section
Currently A1ex is working on a simplified installer that will allow you to install directly from the nightly builds, until then the old method is still being used.
This thread will now be closed.
Well all extras provided by us was already implemented into ML.
Only two features are remaining (1880 width and crop marks for GLDraw Off), but this is small changes so there no reason why keep this fork updated.
Thanks for all a. d. and ML team !