Messages

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 

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.

Here is the code for when it crashes

Code Select Expand

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

Code Select Expand

13779: 63384.997 [DISP] SetPBForLV ZoomMode=0, LVType::Info=0, LVType::DispType=3


Also note that this only works still if I use the "record one raw file with the external monitor off" trick first.

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.

But all my DNGs have pink noise now. Any ideas?

Same exact thing here each time I've tried this method.

I don't know about 5DIII, but on my 5DII raw recording fails almost every time a monitor is plugged in. It actually does record, but crashes and requires a reboot when dumping the buffer.

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.

What I am seeing is that the flickering comes from the contrast -100 slider. If I load Flatz and put the contrast back to 0, I do not get flickering.

Could someone supply me with a set of DNGs that experience the flickering for troubleshooting purposes?

My dropbox folder to add https://www.dropbox.com/sh/os0i5blap1vnqpl/1uSFKQPj9M

Thanks

I don't have dropbox but you can download one dng set that I get flicker with here

http://we.tl/xKcR8Opa12

It isn't as evident until I start to grade. But it is there.

Darn, it looks like a great profile, but I get flicker with this profile.

I confirm flicker here as well.

Great work btw, it still is a valuable idea that hopefully can get resolved.

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 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.

a.d.'s builds can be found here

http://www.magiclantern.fm/forum/index.php?topic=6362.msg50149#msg50149

latest one is 7/11

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

Pro Res 4444 should be the only format you should put into you editor.

Isn't the raw data 442? If so, wouldn't Pro Res 444 be a waste of space?

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.

Just wanted to clarify a few things, as I'm not an expert on raw workflow...

Is Cineform Raw truly lossless raw? I like the idea of that in theory at the compression ratios that I'm getting, but I'm not sure if it offers me any more quality than what I would get with the (free) Apple Prores which compresses to a similar size. Anyone have any opinions? I do not want to be working with CinemaDNG/Resolve/proxy editing workflows, I'd just like to commit to a quality intermediate codec and not have any regrets later in coloring.

I don't see settings for the raw module in the view config file.

Would it be possible at some point to save the raw settings?

Just wanted to see if anyone else had this issue. I can't seem to generate any kind of consistency on this, but I am very sure that at one time my raw settings saved through camera power cycles.

Using a.d.'s builds on 5d2. Each time the camera powers off, I have to manually enable raw recording, reset my desired resolution, turn on the sound beep, etc. I have auto save config turned on, and even tried manually saving.

Any ideas?

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.

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

This is great work, but doesn't seem to save any settings in the raw video menu. They have to be changed back every time I toggle the camera on-off.

Wow, really great work. Exactly the direction that I was looking for. Fastest build yet with a.d.'s May 24th firmware- 781 frames @ 1880x940 32gb Komputerbay 1000x. First time I used it it didn't disable crop marks and zebras on global draw, but now it seems to be working fine. Not sure if I like the joystick as raw trigger, but I guess I'll get used to it.

Not sure which part this is covered under, but it'd be nice to have a more accurate readout of space left on the card. Each time I run out of space it's a surprise- it seems as though both the Format in the Canon menu and the ML readout in the top right do not actively update and lag behind.

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

Reading this: http://francoismalan.com/2011/10/raw-12bit-or-14bit-lossy-or-lossless/
... i guess that it would only make a very very slight difference!

If this is really working... I just dont have words for how awesome this is...

Absolutely! I just used 5D raw for a paying client today (stupid, I know, but it ran without a hitch) and the only pain really was swapping cards around. Need to load up on a few 64gbs. Any space or efficiency savings are welcomed.