Messages

Great camera work and sound design. Good color as well. From a story perspective, I got everything up until the very end.  If Tio is meant to be someone who was kind of a badass, the reactions from the others laughing as Tio messed with the guy kind of killed it.  It set an "uplifting" mood as opposed to one that is "threatening".  For me, I think it boils down to tone and music choice that caused a confusing message. Thanks for putting yourself out there.

I've been wondering that myself. If anyone has attempted a feature with the 5D. I know Upstream Color was done on the GH2.

I had this problem too: you need to copy the modules directory into the ML directory, not on the root level.

-Christian

Thanks Christian. That did the trick! I'm on ML now for 2.02.

Darn, followed the instructions and got further but I'm getting a "missing symbol file b:/ML/Modules" error right after the firmware update screen pops up.  I checked and I have the EOSM_202.sym in the folder. What am I doing wrong here?

note: I was on a out of box 2.02, not upgraded. Did I jump the gun?

Awesome Drizzt321!  I was just rereading through the thread and about to try to answer my own question, so you've saved me some time. Now onto the tests.

I followed this, used the UpDaterM.fir instead of updaterM202.fir which I couldn't find. Got it to install and run fine, although like others it isn't booting right into ML after turning it off/on. Other than that, don't have more time to play with it tonight, but great job 1%!!

I didn't see a zip file in the bitbucket. Am I missing somthing?

Just for the record the combo is running stable on my EOSM - intervalometer and all that. Will try video raw on photo mode today.

1% you really are a superhero. The Canon guys need to take a lesson or two from A1ex, you and other ML developers. Thank you for all the GOOD work.

Quick question. Thought I read that there's no installer for those starting off in 2.02, but then read a post that said someone got it to work. Do these instructions work for new non-bootflagged 2.02? I only get the flashing green lights and have to battery pull.  If these are the right instructions, can you update with a quick link to the bitbucket files? Thanks guys.

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

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?

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?

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

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.

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.

Not sure if I was using an older raw2dng osx, but I grabbed it from the MKii thread. I was getting a green dot in the mov previews that raw2dng made. It was pretty annoying. I figured out that the actual dng files didn't have the green dot so if I followed the normal workflow (raw2dng->PS->QT7) then everything is fine.  Is this a known issue or do I have the wrong version? The one I have says raw2dng converter GUI for 5D2 // Beta 1.0  Thanks

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!

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!

Anyone know if there's still development going on for new 600D builds? Aslo I was looking at the other thread re: variable buffering. Anyone try that trick with the 600d? Is it even possible?