Topics

3 x 64 GB card (1 Lexar and 2 Komputerbay)  + 1 32GB Lexar 1000x.

Not sure if this is allowed on this forum or not; just wanted a fellow ML fan to pick these up.  I bought a Sony a7s and no longer shoot ML raw on my 5d3, but all of these cards worked just fine.

If any of the developers could use these for development, please let me know.

Thanks, Shawn

Can anyone help?  Been shooting raw for about a year; happily with various builds.  My 64 1000x computerbay card is not quite writing as fast as it used too, despite low level formats and trying all sorts of things.

So I pulled down the May 24 build for the 113 5d3 and decided to enable spanning.

On my CF card, I have:
M26-1853.MLV
M26-1853.M00
through
M26-1853.M08

all 4GB files except for the last, where I ran out of space.

On my SD card I have:
M26-1853.M00 (almost 1 gb)
M26-1853.M01
trhough
M26-1853.M08 (all 1k in file size)

Normally in the past I used mlvbrowsesharp.exe and just right clicked - extract with dng + wav.

Now what do I need to do to put this all back together again, and especially the M26-1853.M01-.M08 (1k size) files on my SD card?

I've tried searching and will continue to do so.

Thanks,
Shawn

My favorite way to shoot non-raw video is manual shutter and F/stop, and let the camera pick the ISO.

With raw video, I find the ISO changes too abrupt.  Does everyone just shoot video with their ISO set manually?  Would it be possible to toggle the exposure lock * and get the same effect?

I've briefly fooled around with one of the ISO modules probably like last June - is this any better now?

Thanks, and sorry if this has been answered already.

In my quest for good lenses to use for AF on the new 70d, I have picked up a few to test, and I have tested some that I use on the 5d3.

So far, these lenses are way too noisy for AF video (shotgun mic wouldn't even help):

Sigma 17-50 2.8 HSM VC (great lens otherwise - I shot with an external mic 2 ft away outdoors! and you could still hear it AF).
Tamron 17-50 2.8 - Didn't own it but heard the AF on Youtube - older screw drive lens that's pretty loud
Canon 50mm 1.4 - loud

The following are lenses that are pretty close to being acceptable that I've tried.
Canon 35mm F/2 IS - love the lens, but probably just a tad too loud.  Still heard the lens with external mic.  Just barely.
Sigma 30mm ART 1.4 - in a quiet room, no, but outdoors, probably ok.  Way quieter than the 17-50.

Here's lenses that I feel confident are quiet enough for video AF use:
Obviously, the 18-55 and 18-135 STM Canon's
24mm F/2.8 IS Canon (not as quiet as STM, and it's a shade quieter than the 35mm).  It's close.
Tamron 24-70 USD VC 2.8 - Actually pretty acceptable.
Canon 70-200 IS II 2.8 - Pretty darn quiet too

Let me know if there's interest and I can create a video with all the above lenses for you to hear, minus the Canon 50/1.4 and 35/2 IS (I no longer have them).

Thanks!

Shawn

Trying to figure out the easiest way for me to do this - here's what I want:
1.  To be able to shoot raw to any of my CF cards (no problem) and record audio externally (no problem).
2.  In a split second shoot standard H264 movies with Canon's built-in audio but use Magic Lantern's focus peaking and zebras.

The problem is this - if I disable "FPS override" and "raw video" the audio still isn't working right on the newer ML builds that have raw video as an option.  I sound like a chipmunk when I speak during the video.

So what I'm thinking is this - load the 2.3 "Alpha" (NON-RAW) version of ML on a separate card if I want to shoot H264 video, have focus peaking/zebras from ML, and use the built-in audio recording from the camera. 

Does that sound reasonable?  Or is there something else I can disable in the newer ML builds that make on-board audio recording work?  I've unloaded all modules.

Sorry just trying to make life easier away from the computer...

Shawn

To anyone's knowledge?
I'm not talking about people who forget to load the bootloader, or make a card bootable, or have a dead battery, or use an external power supply.

I'm talking one that died completely from shooting raw video and/or the ML software.

I cannot find evidence of this happening with May 2013 firmware or newer AND a 5d3.  Anyone?

I know personally I pounded the crap out of mine this summer, blowing through several 1000x CF cards and batteries, shooting 1920x1080 and 3x 1:1 mode on the hottest, muggiest days and never had any trouble - other than having to pop out the battery occasionally, and almost never after around the middle of June.

Early July ML build.
Canon 70-200 2.8 IS II @ 2.8
Handheld.
ISO 3200 / 6400 (lighting was awful)
Zoom H1 audio
dng to AE then exported.

Early July ML build.
Tamron 24-70 VC 2.8 @ F/4.5
No ND filter, handheld.
Audio: Zoom H1 shoe mounted
DNG to Adobe AE, exported.

5d3, purchased the end of November. Under warranty.
SD card stops working. Camera will not power on with any SD card inserted; tried 5 different ones.

I'm a CPS member. Sent camera back to Canon last week for repair.
Camera has never been dropped, dinged, scratched, out in the rain, harmed in any way. Always babied. Camera was in mint condition when I mailed it back (mailed back in very safe packaging.

Get an email today that states:



I called CPS services and asked to see PROOF of the damage. They are supposed to get back with me tomorrow. I am stunned. Beside myself. If there was even a time when I thought it could have been damaged I would certainly admit it. But there wasn't. Ever.

What would you do if you KNEW the camera wasn't damaged? Also especially if you're reading about other people on here having SD slots fail?

Is there one?  I've been reading and searching for a while and I'm starting to get a headache.

From my own use, I can confirm that Adobe After Effects v6 will open and import a DNG sequence.

Premiere Pro 6 / Sony Vegas 11 will not.  Both will do other sequences, like .jpg sequences.

From what I've read the latest version of Davinci Resolve will do it.

Anyone have any others?  I don't want to spend all day extracting and converting to many other file formats, and the bummer about Adobe After effects (even the latest CC version) is it doesn't support CUDA for exporting H264.  It will use CUDA for 3d rendering and to speed up previews, but not for actual rendering.

Shawn

Well it seems one cannot render fast enough.  I've been thinking about upgrading my i7 920 from late 2008; now I'm not as sure as before.  This thread will hopefully be for people to post their hardware setup (ram/mobo/cpu/overclock speed (if applicable) CS version number and render time.

There's a sample Adobe after effects project here:
http://benchmark.slashcam.de/AE_RENDERTEST.aep

The results of the fastest time are here (in Deutsche, just for you)

http://benchmark.slashcam.de/

For reference, my pc is running an Asus P6T, 12GB ram, Windows 7 64 bit, i7 920 @ 3.38 GHZ (overclocked), crappy video card, AE CS6
My time was 83 seconds no matter if I allocated 4 threads or 8 to it.

Seems ram makes a HUGE part of rendering. 

There's a I7 3930K w/64GB ram that did it in 41 seconds.
Same I7 3930K w/32GB; 56 seconds.  20GB?  82 seconds (but I'm not convinced he was doing it right)

Hell there's an i7 980 w/24GB that did it in 49 seconds.  My mobo supports a 980 chip.


Still pouring over the results - keep in mind there's lots of "tweaks" you can do to AE6 in the multiprocessor section; I'm not surprised mine is the fastest as I've tweaked the settings.


Please share your results.

Shot from F/4 or so to F/16.

http://www.eoshd.com/content/10610/the-eoshd-5d-mark-iii-raw-shooters-guide-available-now

Personally I wouldn't pay a penny to a guide creator BEFORE I donated to the ML team first; they're the ones who did all the work.  Nothing wrong with capitalism, but when I see comments on his site about "he has done so much to push the ML RAW to the masses" I just wonder if those people are thanking those on THIS site as well.

Shrug.

I'm thinking about it.  I have an i7 920 overclocked to about 3.56 GHz w/12 GB of ram.  I realize most other things wouldn't show improvement, but I'd like to think the AE rendering time would vastly improve.

And then there's nights like tonight where I'm not rendering or working on any raw stuff, and my machine sits idle.

Anyone done any research on the most "bang for your buck" rendering machines?  Is it Hexa-core?  Dual Xeons?

ML software or Canon software?  It's off by quite a bit with FPS override enabled - sorry if the answer is posted on here.  I think the Canon said 1/100 when ML said 1/48 or something.

IMO the best bang for the buck lens in the Canon lineup.
Shot @ F/2.8, Tiffen Vari-ND, Zoom H1n audio

I was thinking about this - since it's basically a 24 FPS burst in raw at a reduced resolution, why not crank the shutter up *if* I'm not worried about it ever being a movie file?  For example, I know about the 180 degree rule and shoot 1/50 for 24p, but let's say I wanted to get some great stills of my son batting in a baseball game.  I could take off the ND filter, crank up the shutter to like 1/640 and get a 24 frame per second burst of stills.

This would get rid of the motion blur that is not visible when playing back motion.  I realize it'd only be a 2 MP burst and not the 6fps @ 22 MP with the 5d3, but would still be fine for small prints and for posting on the Internet.

Will try this out later.

I post a lot recently on here - here's some shots from tonight.
These were imported as a sequence from dng into Adobe After effects and exported to mp4.  No pro-res stuff or any color grading.  Just tweaked the shadows/highlights a bit in ACR and set the white balance.  Trimmed the footage with TMPGEnc MPEG Smart Renderer 4 (this is an amazing tool that doesn't re-render your video - highly recommended!)

Also on Vimeo in case you want to download the original:

Lest we forget how much better the raw looks over H264.... 

Normally I set the shutter to 1/50, the aperture where I want, and leave the Auto ISO "on".

Just before I hit the record button, I check my exposure, and hit the Auto-Exposure lock.  This way the ISO doesn't ramp up or down during the shot, and I get nice even exposure for the entire "take".

Tonight I checked and double checked that I hit the AE button on the 5d3 - about 30 seconds in the exposure jumped up 1 full stop (I was able to correct the portion of the series in Lightroom) and just before the end it dropped back down to the original exposure.

So my question is this - does RAW shooting ignore the AE function, or is this something I need to hit right after I start shooting?  Or is this a bug?  Using the June 3rd build.

Anyone else notice this?  The really weird thing is I was shooting in a fixed lighting scene with a constant F/2.8 lens, and I'm 100% sure I didn't touch the wheel to adjust aperture during the shot.  I did very slowly zoom in during the shot though.  Was not using 5x (1:1) mode either.

Thanks,
Shawn

I went from a freshman last night to "new to the boards".  My 100+ posts are still there, but the number next to my name is way lower.  I realize I blather on a bit, but if I click on my name the original posts are still there.

Anyone know what happened?

Depending on the build (current ones seem to be about 16 to the left / 3 up) for 5x (1:1) recording - would love to be able to "set" a custom crop mark so I can immediately go to this.  I shoot lots and lots of 1:1 crop video.  If I could define one so I could just hit the joystick once to toggle it, it'd be great.

Love you guys,
Shawn

Quick background - in the last week I've purchased three 64GB 1000x KomputerBay cards.
First one didn't work in the camera, but was fine in the computer.
Second one is fine and works as expected.
Third one works but is far slower, and only does around 60MB/s.

In my external quest for fast enough cards I am going to run various tests with benchmark results, and show the effect (if any) on the cluster size of the formatted cards.  One would think a large cluster size would be fine since it's only going to store very large data files, even if not super efficient for small files.

Example -

Card B:

Formatted for 16384 cluster size:

1920x1080 = 73, 73, 91 frames before crash
1880x1058 = 73, 121, 127 frames before crash
1720x968 = ran indefinitely

I will post screen captures too of known "good" cards, like my 32GB Lexar and the sole remaining Komputerbay that works.

So, it's really a crapshoot with the Komputerbay cards if you want 1920x1080 @ 24p.

If you are recording and run out of space on the card, when you try to extract the dng files you'll get the following error:

Error: This ain't a lv_rec RAW file

You need to replace the file footer information to get this back.

Here's what I did, and I'm sure there are easier ways, but this is free.

Step 1:
Download the freeware Hex editor from here:
http://mh-nexus.de/en/downloads.php?product=HxD

Step 2: Open the .raw file in the hex editor.  Scroll all the way to the bottom.

You have 2 choices at this point:

Option 1 - Record another file with the same settings on the card, and retrieve the footer information in the hex editor.  It should be the last 12 lines of the file.  The downside to doing it this way is it'll only extract the same number of DNG files that the secondary file has listed; i.e. if your 2nd file is 200 megs or so, if you copy that file's footer information to the (assuming) larger troubled file, you'll only be able to pull out the first 50 or so dng files.

So I suggest you do #2:

Option 2 - Copy and paste this into your file footer:

52 41 57 4D 80 07 38 04 00 5F 37 00 F4 21 00 00 01 00 00 00 A8 5D 00 00 18 02 98 19 18 02 98 19 01 00 00 00 00 20 15 0B 26 05 00 00 20 08 00 00 38 0E 00 00 50 34 49 00 0E 00 00 00 0C 08 00 00 98 3A 00 00 00 00 00 00 00 00 00 00 88 07 00 00 08 05 00 00 1E 00 00 00 92 00 00 00 26 05 00 00 1A 08 00 00 00 00 00 00 00 00 00 00 00 01 01 02 01 00 00 00 42 1A 00 00 10 27 00 00 85 FD FF FF 10 27 00 00 3D FC FF FF 10 27 00 00 41 EF FF FF 10 27 00 00 AC 30 00 00 10 27 00 00 EC 07 00 00 10 27 00 00 74 FC FF FF 10 27 00 00 72 08 00 00 10 27 00 00 24 16 00 00 10 27 00 00 82 03 00 00

Save the file, and start unpacking your dng's!

This will work for file sizes up to 32gb.
**Of note - say your "bad" file was smaller than 32GB - let's say it was 11GB - by using this footer it will try to unpack 8692 DNG files.  Since I'm not smart enough to read hex, I just estimate where the good dng files should be and delete everything after it.

Here's a screen shot of the pasted in footer:

Just thought I'd share my experiences so far; if this helps out anyone that's great.
The following assumes you're using a 5d3 + Adobe after effects for importing.

Tip 1 - If you use a Sigma or Tamron lens, you can fix the vignette in the Adobe Raw importer if you select a Canon lens.  If you pick the actual lens you have it may not work (my Tamron 24-70 didn't).

Tip 2 - In Adobe after effects, you can import all of your DNG sequences and queue them up for rendering - just make sure you have 1 movie and at least one "composition"  Meaning if you drag/drop one movie to a composition and hit "add to render queue" and then try to add another one, it'll only render the LAST movie you added to that composition.  I manually create new compositions and get them all in the render queue so I don't have to sit and wait for each one.  If you know of a better way, I'm all ears.  So if I'm doing 6 raw sequences I'll have 12 files - 6 imported DNG sequences, 6 .wav files, and 6 compositions.  One per "movie".  The only reason I mention this is Adobe Premiere works a little differently; you can swap files out and keep adding to a render queue and it'll render correctly.

Tip 3 - Get a USB3 reader - it makes a WORLD of difference copying .raw files back over.  I picked one up tonight along with a PCIx - USB 3 4 port device and it's about 5x as fast copying files back over.

Tip 4 - If you want to record 1920x1080 with audio, insert an SD card in your other slot and it will automatically (assuming you have changed it from the default "beep").

That is all for now.

One "bummer" about this lens is the vignetting wide open.  Once stopped down to about F/4 you're fine if you don't like the vignette.  My workflow with the 5d3 + raw has been Adobe After effects - I noticed that when you import the first DNG file and go to the "lens profile" tab and select the correct Tamron lens, the vignette slider has no effect.

However, if you select "Canon" as the lens model (I chose 24-70 2.8 as the Canon lens) you can then get rid of your vignette, even at F/2.8.

Great news!  Not sure if this was thread worthy but I just had to share.