Messages

Mac user here, I'd like to test it out. Bonus being I'm socially awkward and thus have no personal life, which I think would make me an ideal candidate.

Either way I'm glad software like this is being developed as RAW becomes more and more prevalent. 

Here is another low light video graded in Resolve using the Canon 50mm 1.8  Click 'Show More' in the description to compare to the same clip without BlackMagic settings in Resolve and a few more tweaks.

Another nice looking clip, yeah with 1600 I'm getting way more noise perhaps RPP (what i use to process my dngs, correct white balance etc is the culprit. I don't have a nvidia card so I can't use resolve : (

Thanks CaptainOfObvious! I used Canon f1.8 50mm, wide open at an 1600 ISO. In resolve I interpreted my clip exposure at 0.90. The source files are nice and sharp.

Hmm, I dont feel like I get even near that kind of lowlight performance on 1600, any noise reduction going on in resolve?

Here's a low light indoor test.

Holy crap I love that grade. Good job on composition too.

What Iso and Lens? Youtube compression can be get blocky with dark scenes but even then I get the feeling the source files look good.

There are a bunch of ways you can do it - if I had an external sound recorder like an h4n I'd just have to slate it/sync it. In this case I just synced it by eye using more recognizable parts of the song.

I absolutely loathe syncing it by eye so slating it by specific verse/chorus will have to do. Embedded scratch audio is so much easier, I guess I've gotten lazy.

This is a short music video I shot in Thailand last week on the 50d with one of the earlier June builds. Enjoy!

Umm, nice...pool.

So I'm curious, as someone who used to using scratch audio for music video, how did you sync up the video to the track without the 50d having no audio capabilities?

Just tried and all videos have a left border. 1920x1080 records a few frames then frames go black

Same, I'm also getting a 71x930 border on the left side when recording max view. 1:1 1920x1080 records a few frames then frames go black.

Still getting 57-60MB/s in 1:1mode, am I missing something?

Double post.

You got it all wrong actually RawMagic gives you the correct White Balance as shot without all that magenta tint we use to have before.. are you using @GregoryOfManhattan (08 Jun Unified Build) ?  And what version of RawMagic you using.. Beta 4?  Mine runs perfectly now we have Spanned files with correct White Balance.

Hmm, I'm Using Beta 4 (and june 9th files) and I still get the magenta tint on RawMagic. What's interesting though is that if I use Raw2DNG for a file under 4GB, take that dng and open it in RPP I can get "as shot" white balance just fine. I wonder what I'm doing wrong, for the fifth-tenth time.  -_-

I was able to span two clips with no problems, Zero pink frames, and drop frames playback is soo smooth.. Use @GregoryOfManhattan code it works.

I (finally) got spanning to work as well! Awesome, the only problem is I couldn't use Raw2Dng (OSX) to convert them, had to use RawMagic, does anyone know if raw2dng works with 50d spanned files yet? What did you use godlenchild?

This workflow is still a bit of a pain too, as RawMagic doesn't retain "as shot" white balance. So I then have to convert to tiff with RPP after some adjustments, then into MPEGSTREAMCLIP to output prores 444.

Hello people,

A couple of days I made a decision to go for 50D. Couldn't resist this RAW monster

I loaned a fast x1000 card and did my first test shoot.

But I was surprised (in a bad way) with moire. Is it something to leave with? Or can you suggest any solution?

Thanks!

There is a ton of fine line detail in those shots, I'm not surprised. Look for the money this camera shooting RAW is insanely good, no doubt about it. With that being said it's far from perfect, I personally think it's aliasing (even more so than the moire it exhibits) is pretty darn poor.

What resolution did you shoot at?

Good to know, thanks a1ex. Yeah when I turn on the zoombox, I can see the buffer start to fill, however when I turn it off it goes back down, where as focus peaking just fills the buffer very quickly. So you wouldn't recommend periodically using magic zoom just to check focus quickly and turning it back off?

Oh and RAW Zebras while recording seems like a no go, quickly fills buffer.

Doing some stress testing to see what's stable and not. Seems totally stable with global draw off at 1592x896. What's even better is that I can shoot with Raw histogram and zoom box (but only periodically turning it on and off to check focus, if kept on it will fill the buffer) and it seems relatively stable.

CaptainOfObvious and Menoc thank you for bug report.

First unified build for 50D raw video -
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/08June13-50D-UNIFIED.zip

so now you can replace MODULES folder with this one.
you don't need FILE_MAN or BOLT_REC they are optional new modules i was looking at today.

for raw recording you must have an
AUTOEXEC.BIN and its matching
ML/MODULES/MAGIC.SYM and of course the
ML/MODULES/RAW_REC.MO module.

That did it! Thanks GregoryOfManhattan

On another more depressing note, just as user rockfallfilms has experienced my card has seem to suddenly drop in write speeds, from about 57-60mb/s to 45-48ish, buffer fills quickly and recording stops. That's at 1592x896, I'll try some lower resolutions and report back in.

EDIT: Oh god I'm a dummy -_- forgot to reenable fps override after updating to newest build. Sorry for the false alarm.

should load on top of my 28May13 build, smeangols or ML 2.3 -
re-format card
delete ML Config
replace AUTOEXEC.bin
replace MODULES folder

First off, thanks for the update! I seem to be having problems though, I replaced autoexec.bin and the modules folder but when booted up inside my camera trying to load the raw module I get the error:
"A:/ML/MODULES/MAGIC.SYM': File does not exist"

So when I take the MAGIC.SYM file from the May 28th build and place it into the modules folder I then get this error:
tcc: error: undefined symbol 'WAV_StopRecord'
tcc: error: undefined symbol 'vram_clear_lv'
[E] Failed to link modules

If I made a foolish error in replacing those files I apologize in advance.

I successfully joined the spanned files. My findings are that the first file (the one with the .RAW extension) is NOT corrupt and the DNGs look good, but the DNGs in the next file start to corrupt. My guess is that at some point after ML writes the first spanned file, either the next file in the sequence is not written correctly, or the DNG's code is not written correctly.

Same exact thing I was seeing with my frames, thanks for the confirmation.

@menoc and @savale spanning is much better on later builds - though i still do see frames like the posted example

Good to hear there's progress being made though. Thanks for the work you're doing.

I think RAW2DNG not recognizing it is due to an error in the footer. Fix the joined file in a hex editor (apparently) and it will read. Too busy with gigs but will test soon.

Does the footer needs to be done on the windows side of things aswell? In bootcamp I joined the files successfully and extracted them to DNG, but all files post spanning (contained in the .r00 file) are corrupted. They're a garbly mess of colors and noise.

Roman, you said you did it successfully, were there any corrupted frames when you extracted to DNG?

Btw I'm using the may28th build.

It seems to work for me already?

I accidentally recorded a file over 4gb yesterday, and I ended up with .raw and .r00

Then just recombined the files (in this case dv.raw and dv.r00) in Dos prompt with the command:

Copy/b dv.raw+dv.r00 output.raw

to end up with output.raw file which was over the 4gb limit.

Then I could output all of the files to DNG fine.

Wha?! I must of missed those developments, I tried joining on mac osx using unix command cat file1.raw file1.r00 > output.raw but raw2dng didn't recognize it. 

I'll try booting into my windows partition and using DOS. Thanks Roman. If anyone has done it successfully on terminal I'd appreciate knowing that method as well.

I have a quick question about this- the ML installation guide says the 50d needs to have the latest firmware (1.0.9) already installed before you can install ML; I purchased mine used, and it came with firmware 1.0.7.
I feel like I've seen a few posts about installation, and no one ever mentions updating the official firmware first; you do need to do this to get ML working on the camera, no?

I bought mine used with 1.0.7 on it aswell, updated to official firmware first THEN installed ML. It worked for me.

On Another note, any word of get file spanning functional? I would love to do some narrative tests on here, or perhaps music videos. Not being impatient just trying to gauge the progress on that particular hurdle. It seems to be one of the bigger ones we face with 50D raw right now. Keep up the great work guys.

It's something in MPEG Streamclip. I'm using QT Pro 7 and no issue.

Thanks, that pushed me in the right direction. I just tried compressor, and it seemed to render the frame rate accurately, the problem is every time I try to load an image sequence larger than about 140 frames compressor hangs on me. So close yet so far!

At least it wasn't something on the camera side.

Where are you processing the TIFF sequences?

Using Raw Photo Processor to process the DNGs into Tiff. From there MPEG Streamclip to process into prores444. I might try using the raw function on my t2i and see if I have the same frame rate problems.

Darn, not using after effects.

Your sunset sky made me happy, I've always had problems with sky colors in h264. Can't wait to get the 50d.

Being able to isolate colors with MUCH more accuracy is a breath of fresh air compared to the usual h264 you get out canon. The image just doesn't fall apart immediately I love it.

HOWEVER, does anyone know why I'm having these frame rate problems? ML RAW says I'm shooting at 24p, when I convert to dng with RAW2DNG it reads as 24p, but if I try to transcode into any codec or even drop raw Tiffs right onto my timeline I get playback as if it's 12fps, then I have to retime it by 2x just get close. Has anyone else experienced this?

Speaking of dumb questions, trying to figure it out myself but can't. Whenever I transcode my tiffs (from RPP) inside MPEG Streamclip I'm getting a sort of dreamy blurry motion, depsite FPS override being on at 24fps. I'm setting MPEG Streamclip for 24fps aswell I'm not sure what I'm not sure what's going wrong exactly. Anyone else experience this?

Thanks for that, I've turned it on and now the ISO dial is having an effect. Do you have exposure sim on or off?

Had it off at first, but for a clip I just shot I turned it on because I think I read that it's recommended? Just got my card today so I'm figuring out all the small details aswell.