Updated install instructions here: http://www.magiclantern.fm/forum/index.php?topic=9852.0
Updated install instructions here: http://www.magiclantern.fm/forum/index.php?topic=9852.0
I'm ready :D ...well I will be when I get a CF card :(
(http://i.imgbox.com/acmE2Sze.jpg)
Looking forward to the results! I'm in the process of trying to find a cheap 50D ;)
Smeagol, you got it actually working? Could you upload a clip or some dng's?
Just got the KomputerBay 64GB 1000x Card. Here's the bench mark test results for the 50D:
(https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP)
https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP (https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP)
Quote from: menoc on May 24, 2013, 01:58:16 AM
Just got the KomputerBay 64GB 1000x Card. Here's the bench mark test results for the 50D:
(https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP)
https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP (https://www.dropbox.com/s/ayw9fiblyzxvtaw/50D1000xTEST.BMP)
Not bad. I think the 50d must have the same CF controller as the 5d2 but the file sizes are smaller. The Komputerbay card looks good. At those rates it's not far off being able to record the 1:1 crop size in 14bit and if/when they get the 12 bit compression working the 50d will probably be able to do it all. I'm glad I grabbed one now :)
Have you tried @smeangols latest build (2nd post in this thread)?
@JulianH - it's a great time to buy one if you can ;)
Quote from: Andy600 on May 24, 2013, 02:12:04 AM
Not bad. I think the 50d must have the same CF controller as the 5d2 but the file sizes are smaller. The Komputerbay card looks good. At those rates it's not far off being able to record the 1:1 crop size in 14bit and if/when they get the 12 bit compression working the 50d will probably be able to do it all. I'm glad I grabbed one now :)
Have you tried @smeangols latest build (2nd post in this thread)?
@JulianH - it's a great time to buy one if you can ;)
Trying it now . . . .
Quote from: menoc on May 24, 2013, 02:34:15 AM
Trying it now . . . .
Wow! Beautifully clean images at 1592x720. No dropped frames all the way to the 4GB file either!. Man, If we could only get the magenta shift fixed and larger than 4GB files!
Will try other crops later.
Post some sample DNGs showing the magenta shift.
Quote from: menoc on May 24, 2013, 02:57:45 AM
Wow! Beautifully clean images at 1592x720. No dropped frames all the way to the 4GB file either!. Man, If we could only get the magenta shift fixed and larger than 4GB files!
Will try other crops later.
Great! Could you try 1280x1080 or 1280x960? I'm hoping this will work, would be great for 2x anamorphic at 2560x1080 (2,37:1) or 2560x960 (2,66:1).
@menoc - Excellent! The magenta shift sounds like the black point issue.
@a1ex - Is the black point problem in the raw_rec module or the .bin? I can compile now BTW :)
@smeangol - once this is sorted you should submit a pull request ;) Sounds like you're close!
I wish my CF card would hurry up and be delivered
Black point will be correct only if the raw skip offsets (in raw.c) are correct. Otherwise, the calculation will be wrong.
If you post a DNG, I can tell if the offsets are correct or not.
Quote from: a1ex on May 24, 2013, 11:54:07 AM
Black point will be correct only if the raw skip offsets (in raw.c) are correct. Otherwise, the calculation will be wrong.
If you post a DNG, I can tell if the offsets are correct or not.
I've sent you @smeangol's raw.c if that helps? He has created a fork on Bitbucket but not added his changes to it atm. I have a copy of his source though.
Picking up a 50D tomorrow. Right now i'm using a friends 5D II with a Sandisk Extreme Pro 32GB 95MB/s (works fine with the max speed of the 5D II somewhere around 60MB/s). Will benchmark that in the 50D and try do do some 5DII vs 50D tests if I get everything running on the 50D :)
Raw video on a 5 year old dslr from before the hdslr era. Would have laughed everyone in the face if they told me this a month ago. Absolutely bonkers :)
Really easy to find the skips... set them all to 0 in raw.c.. take some silent DNG. Count black borders in phtoshop
Hi, I guess this is the typical n00b trolling first post ^^. I will get a 50d tomorrow for RAW video, any reason I should stay away?
Could anyone tell me if the quality is similar to the 5dmkii. I'm asking because I have a d800 and I have been comparing it to the raw shoots of the 5dmkii and they look a lot better indeed, so if the 50d will have the same quality it's defenitly a nice thing to have (despite 1.6x crop). Since I need the d800 I won't jump ships and this seems a cheap way to have an alternative for those shots that make me yell at the d800.
Excuse my manners, I got so excited.
We don't know yet. The sensor size is different to the 5d2 and I'm not yet sure how this will affect things like moire and aliasing. Raw video on the 50d is very much a work-in-progress as is the 5d2 version. I'm going to shoot some tests this weekend and do a comparison with the 600d. I know which one will win but by how much? ::)
Quote from: Andy600 on May 25, 2013, 12:26:03 AMI know which one will win but by how much? ::)
Stop making me jealous! ;D
@alex
http://www.smeangol.com/000026.dng
This is a dng from a "zoomed in like X5 or X10" shot - in this mode you get a 1920 X 1080 style frame - but it doesnt work perfectly :/
The Normal not cropped /zoomed LV mode should ~ 1500 X 1000 work without disturbance.
Quote from: smeangol on May 25, 2013, 12:29:48 AM
@alex
http://www.smeangol.com/000026.dng
This is a dng from a "zoomed in like X5 or X10" shot - in this mode you get a 1920 X 1080 style frame - but it doesnt work perfectly :/
The Normal not cropped /zoomed LV mode should ~ 1500 X 1000 work without disturbance.
Thanks smeangol, do you have any sample dng of the 1500x1000 "crop".
I have a sample posted here on the forums taken with silent shutter which is 1592x1062 and even with the visible aliasing/lineskipping it looks great, even upscaling it to 1920x1080 it looks way better than 1080p h264 footage from my d800, I mean, just the fact of being able to use ACR on video makes me the happiest man on the world (I'm not a real video guy, I come from stills but people want video).
This raw recording is from the same source as the silent shutter, I suppose.
Zoom LV with Resolution of 1992X1084 seems to be far less disturbed: http://www.smeangol.com/1992x1084_seq.zip
First few frames are rubbish, the recording ends with some dropped frames due my lame CF Card.
QuoteThanks smeangol, do you have any sample dng of the 1500x1000 "crop".
This resolution belongs to the normal field of view :)
Quote from: smeangol on May 25, 2013, 01:21:38 AM
Zoom LV with Resolution of 1992X1084 seems to be far less disturbed: http://www.smeangol.com/1992x1084_seq.zip
First few frames are rubbish, the recording ends with some dropped frames due my lame CF Card.
This resolution belongs to the normal field of view :)
Yea ;) that's why I said "crop", just wanted to know if you had any "screen grab" sample of that mode.
Downloading your sequence to give it a try on AE, btw what card did you use? Thanks for the sample btw :D
I loaded up your dngs in After effects and beside the corrupt images the score seems to be yellowish (after adjusting white balance tint), is it the lighting?
Btw that magenta shift menoc is talking about, is it the wb issue or is he referring to the corrupted magenta colored frames.
I'll make test with different settings if it helps when I got the 50d (ich hab' keine ahnung von programmieren)
OK,
Komputerbay 64GB 1000x CF card benchmarks;
(http://i.imgbox.com/acrP0LHK.png)
@ 1592x1062, writing to the card stops after about 50 frames; @ 1592x960, writing to the card drops frames but writes to 4GB; @ 1592x840, writing to the card drops frames but writes to 4GB; @ 1592x720, the 1st try stopped at 100 frames, the 2nd try wrote a 4GB fie without any frames dropped; @ 1280x720, writing to the card finishes the 4GB file without dropping frames.
Here you can download the sample DNGs:
https://www.dropbox.com/s/gnjjdzbi1s9g4xy/000023-1592x1062.dng
https://www.dropbox.com/s/o073davr3x3z0c7/000009-1592x960.dng
https://www.dropbox.com/s/j3674mdktlsfq1g/000027-1592x840.dng
https://www.dropbox.com/s/3k9h8o3d0axyibq/000095-1592x720.dng
https://www.dropbox.com/s/jbt34r1ziuscjva/000040-1280x720.dng
Here's a sample image with the pink tint - is this fixable? (it's really not a big deal- it's easily fixed in post). There's also a black line running vertically on the left side of the image - but you have to download one of the DNGs to see it.
ISO 320/F3.5/23.988FPS
(http://i.imgbox.com/actFZMZS.jpg)
Quote from: menoc on May 25, 2013, 02:51:22 AM
https://www.dropbox.com/s/gnjjdzbi1s9g4xy/000023-1592x1062.dng
dng has a black frame, resolution should be 1590x1060
Quote from: menoc on May 25, 2013, 02:51:22 AM
[spoiler]OK,
Komputerbay 64GB 1000x CF card benchmarks;
(http://i.imgbox.com/acrP0LHK.png)
@ 1592x1062, writing to the card stops after about 50 frames; @ 1592x960, writing to the card drops frames but writes to 4GB; @ 1592x840, writing to the card drops frames but writes to 4GB; @ 1592x720, the 1st try stopped at 100 frames, the 2nd try wrote a 4GB fie without any frames dropped; @ 1280x720, writing to the card finishes the 4GB file without dropping frames.
Here you can download the sample DNGs:
https://www.dropbox.com/s/gnjjdzbi1s9g4xy/000023-1592x1062.dng
https://www.dropbox.com/s/o073davr3x3z0c7/000009-1592x960.dng
https://www.dropbox.com/s/j3674mdktlsfq1g/000027-1592x840.dng
https://www.dropbox.com/s/3k9h8o3d0axyibq/000095-1592x720.dng
https://www.dropbox.com/s/jbt34r1ziuscjva/000040-1280x720.dng
Here's a sample image with the pink tint - is this fixable? (it's really not a big deal- it's easily fixed in post). There's also a black line running vertically on the left side of the image - but you have to download one of the DNGs to see it.
ISO 320/F3.5/23.988FPS
(http://i.imgbox.com/actFZMZS.jpg%5B/spoiler%5D)
Nice samples!
Could you try using less horizontal resolution and keeping the 16:9 aspect. 1427x802 should have the same pixel number as 1592x720, dunno if magic lantern lets you set that akward resolution.
Quote from: Greg on May 25, 2013, 03:21:52 AM
dng has a black frame, resolution should be 1590x1060
. . . I'm guessing the top and Left black frames?
I created a fork of magic lantern featuring the Raw video for 50D - how to merge with the main project?
https://bitbucket.org/smeangol/magic-lantern
@araucaria - I think the latest raw_rec module selects height based on selected aspect ratio.
Quote from: Andy600 on May 25, 2013, 12:03:11 PM
@araucaria - I think the latest raw_rec module selects height based on selected aspect ratio.
Thanks andy, but will it let you choose the horizontal resolution and select the hight following the aspect ratio?
@menoc What spped benchmark values are you getting with the komputerbay in liveview/movie mode rather than in playback?
Managed to trade my old 5D for the 50D and cash :)
I got raw recording working. Did a benchmark of Sandisk Extreme Pro 32GB 95MB/s in live view, but it doesn't seem to close the benchmark properly. I can't seem to find a log of bmp of the results. Where should it be?
Maximum seems to be around 50MB/s for continuous recording (with my card).
My results (how can I determine exactly at which frame skipping starts?):
Shot at 24 fps (didn't find a setting for 23.975..)
1592x1062 - frame skipping after about 50 frames (67.7MB/s)
1592x840 - frame skipping after about 480 frames (53.5MB/s)
1592x720 - no frame skipping (44.3MB/s)
1320x1062 - frame skipping after about 300 frames (56.1MB/s)
1320x960 - frame skipping after about 1200 frames (50.7MB/s)
1320x840 - no frame skipping (44.3MB/s)
1280x1062 - frame skipping after about 250 frames (54.4 MB/s)
1280x960 - no frame skipping (49.2MB/s)
The 50D did crash 2 times during my tests. Think it happened just after I pressed recording. Nothing happened, screen would stay on, had to take the battery out.
Big thanks to all of you amazing people making this possible. Shooting raw video on a 5 year old dslr... it's still hard to believe! ;D
Sample footage! shot some boring bricks to test for moire. Looks pretty good to me. I have the feeling it's better than the 5DII... Would have to check in a direct comparison though.
Download here (WeTransfer) (https://www.wetransfer.com/downloads/9601255fb2b189b37b4b0d44cb0194c320130525170445/0fc5fb145e9213a3c61911886b4a751d20130525170445/70564c)
Some exported sequences and some DNG files to play with. All the info in the readme.txt.
1592x840 @ 24 fps - Nikkor 50mm f/1.8 @ f/8
1280x960 @ 24 fps - Nikkor 50mm f/1.8 + Kowa B&H 2x anamorphic - Stretched to 2560x960 in Premiere
And a sharpened 1920x720 version of that last one.
Thanks Julian :)
Looking good. I had a suspicion the 50d might beat the 5d2 in terms of aliasing because of the smaller sensor size and that looks to be the case. I think there are still some bugs to iron out with black point etc but great to know it's working for you. I feel like a stuck record but my CF still isn't here so can't do anything. Frustrating excitement :D
I think these shots are good enough to prove the 50d is probably second only to the 5d3 for raw video even though the frame sizes are smaller than the 5d2.
The anamorphic lens seems to work very nicely and I think raw dimensions can be pushed even further.
No problem! Let me know if you or someone else want me to do some other tests. I'm not a coder but not completely stupid I think.
A bit more resolution would be nice. 1592x840 without skipped frames would be perfect for 1920x1080p I think. Pretty sure it's more detailed than native 1080p on Canon dslr's. Stable 1280x1062 would be nice for 2x anamorphic and for 1,5x anamorphic something like 1536x960 would be awesome. But I'm not complaining at all with the current possibilities!
Can understand your excitement. When I heard of this raw hack, I had to try it. The 5D3 looks great, but out of my budget. I would consider the 5D2, but not cheap either and the quality isn't perfect. Not that the 50D is perfect, but for this kind of money it's amazing to have the possibility to shoot raw.
I have a Blackmagic Pocket Cinema Camera on pre-order, but I'll seriously consider cancelling it if the 50D turns out to be usable. For me it's just a hobby anyway.
Now I just need some new badges for my camera.. :P
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_61847.jpg)
Ha! Love it... ;D
I'm not a coder either but I can compile and pull changes. I can also understand some of the less technical updates that are being done by the developers so I'm going to make a fork on Bitbucket and will try to sync with @smeangol. I will only upload things I have tried myself and we should keep the first post in this topic for updates. Eventually we will submit changes to be reviewed by the devs for the unified build.
Mods - Can you please move this thread to the new ports board? (I know technically the 50d is part of the unified ML but there is still a lot to do)
...And wath's about the humble, older and Ugly Duckling 40D :'(
Quote from: JulianH on May 25, 2013, 07:21:09 PM
Sample footage! shot some boring bricks to test for moire. Looks pretty good to me. I have the feeling it's better than the 5DII... Would have to check in a direct comparison though.
Download here (WeTransfer) (https://www.wetransfer.com/downloads/9601255fb2b189b37b4b0d44cb0194c320130525170445/0fc5fb145e9213a3c61911886b4a751d20130525170445/70564c)
Some exported sequences and some DNG files to play with. All the info in the readme.txt.
1592x840 @ 24 fps - Nikkor 50mm f/1.8 @ f/8
1280x960 @ 24 fps - Nikkor 50mm f/1.8 + Kowa B&H 2x anamorphic - Stretched to 2560x960 in Premiere
And a sharpened 1920x720 version of that last one.
Great Video JulianH the images coming out of the 50D looks great.. also like your new logo ML + C lol.. Looking for a 50D right now gotta get my hand on one. From your experience with the 50D thank it's real close to the 5D Mark III?
Quote from: ilex on May 25, 2013, 09:23:35 PM
...And wath's about the humble, older and Ugly Duckling 40D :'(
It seems a possibility but the whole 40d port needs resurrecting by someone.
@goldenchild9to5 sorry, I know you asked this to Julian but it's an easy question to answer. In terms of colour yes, resolution no but it's looking as good, if not better than the 5d2 because of moire and aliasing.
Lol 50Dc... yep everyone is peeing on 1DC right now.
Quote from: Andy600 on May 25, 2013, 09:34:47 PM
@goldenchild9to5 sorry, I know you asked this to Julian but it's an easy question to answer. In terms of colour yes, resolution no but it's looking as good, if not better than the 5d2 because of moire and aliasing.
Good enough answer for me.. on par with 5D2 without Aliasing and Moire I'm in..
Quote from: 1% on May 25, 2013, 09:38:40 PM
Lol 50Dc... yep everyone is peeing on 1DC right now.
The 1DC is surely getting a beating from all those Hacks..
Quote from: 1% on May 25, 2013, 09:38:40 PM
Lol 50Dc... yep everyone is peeing on 1DC right now.
The 1DC images look great but I know what I'd rather have atm (and what I can afford... stupid bloody price!). TBH, like nearly everyone else, anything I shoot will only ever end up on Vimeo or Youtube and maybe some low-level public access TV if I'm lucky :D
...but still, it's all fun isn't it!?
@goldenchild9to5 - I never said it was without moire and aliasing. ATM we don't know for sure. There IS some present in the samples JulianH posted but not as much as most of the 5d2 tests I've seen.
BTW TV has coped with moire, aliasing and the dreaded interlaced format for many years. You can simply avoid shooting the things that are prone to it or shoot with a shallower DOF to blur out the culprits ;)
Quote from: Andy600 on May 25, 2013, 09:46:32 PM
...but still, it's all fun isn't it!?
Yes! And raw videos make about 263.45 times more fun than H.264 ;D
Poor guys that bought a Nikon because of the dynamic range ...
Quote from: CFP on May 25, 2013, 09:54:02 PM
Yes! And raw videos make about 263.45 times more fun than H.264 ;D
Poor guys that bought a Nikon because of the dynamic range ...
Right about that..
Got a question for everybody on this post what does that mean "18492 actuations on the shutter" some are even Higher like 160876 actuations on the shutter does it matter for Raw video?
That's shutter count (the amount of times the shutter has opened and closed). 100k is the projected life of most Canon DSLR shutters.
Quote from: Andy600 on May 25, 2013, 09:51:06 PM
@goldenchild9to5 - I never said it was without moire and aliasing. ATM we don't know for sure. There IS some present in the samples JulianH posted but not as much as most of the 5d2 tests I've seen.
BTW TV has coped with moire, aliasing and the dreaded interlaced format for many years. You can simply avoid shooting the things that are prone to it or shoot with a shallower DOF to blur out the culprits ;)
So true the viewers don't care about all that, they just wanna see a great story told..
Quote from: Andy600 on May 25, 2013, 10:28:58 PM
That's shutter count (the amount of times the shutter has opened and closed). 100k is the projected life of most Canon DSLR shutters.
so after 100K the camera will breakdown?
Not necessarily. It can happen before it reaches 100k ;D
No one knows how long their shutter will last.
If you plan to use it for filming, a high shutter count isn't a big problem, since you won't be using the shutter/mirror. You only use it to enter and exit live view. I wouldn't buy a 50D that has 160000 shots on the shutter... that might break down any time (it might get to 300000 too, you just never know...).
If the shutter 'breaks' that also doesn't necessarily mean you can't use the camera any more. I think most of the time it will result in your photos looking weird, because the shutter is not working/syncing correctly. That shouldn't stop you from taking movies.
Also you can get the shutter unit replaced. I think here in Europe that would cost like €150, depends on the camera/service center. Not sure if they still have spare parts for old models like the 50D...
Quote from: Andy600 on May 25, 2013, 10:48:00 PM
Not necessarily. It can happen before it reaches 100k ;D
No one knows how long their shutter will last.
So it's not safe to buy one that's close to 100K. What would happen when your shutter reaches it's limits does that effect video recording in any way? Just wanna make sure cause I'm about to make a purchase.
Quote from: JulianH on May 25, 2013, 10:54:19 PM
If you plan to use it for filming, a high shutter count isn't a big problem, since you won't be using the shutter/mirror. You only use it to enter and exit live view. I wouldn't buy a 50D that has 160000 shots on the shutter... that might break down any time (it might get to 300000 too, you just never know...).
If the shutter 'breaks' that also doesn't necessarily mean you can't use the camera any more. I think most of the time it will result in your photos looking weird, because the shutter is not working/syncing correctly. That shouldn't stop you from taking movies.
Also you can get the shutter unit replaced. I think here in Europe that would cost like €150, depends on the camera/service center. Not sure if they still have spare parts for old models like the 50D...
Great info gonna shop around for one with minimal Shutter use thanks you all for answering my questions..
There is no way to check shutter count in the camera unless ML is installed but you can use this utility: http://astrojargon.net/eosinfo.aspx
Quote from: Andy600 on May 25, 2013, 11:24:01 PM
There is no way to check shutter count in the camera unless ML is installed but you can use this utility: http://astrojargon.net/eosinfo.aspx
So all those postings on ebay with a shutter # than are just a guess, but shutter doesn't really matter for video recording like Julian said.
It's better to have a shutter that works. It's a camera :D
If shutter count hasn't been taken from ML or another app then it will likely be just an estimate by the seller who is guessing how many shots they took. They guy I got mine from said shutter count was around 12k when it's actually 22k.
My advice would be to ask the seller what they usually shoot. If they say sports, run away. The 50d can shoot 6.3fps raw (photo) and sports photography usually involves a lot of burst shooting. Each time that shutter goes up and down it counts and 6.3x every second is a lot. Anything under 50-60k is probably a safe bet for a 4 year old camera, obviously the smaller the number, the better.
50d users: What picture size are you using ATM? Raw/Sraw1/Sraw2/Jpeg etc. Try changing it then check shoot_malloc, does it alter available memory?
Does raw video work in raw and jpeg modes?
Quote from: Andy600 on May 25, 2013, 11:57:42 PM
50d users: What picture size are you using ATM? Raw/Sraw1/Sraw2/Jpeg etc. Try changing it then check shoot_malloc, does it alter available memory?
Does raw video work in raw and jpeg modes?
I have raw disabled and jpg set to small with lowest quality. Raw video works.
Shoot_malloc total = 212M
Other settings and Shoot_malloc:
Raw = 188M
Raw + JPG = 188M
Sraw1 = 188M
Sraw2 = 188M
JPG L Fine = 212M
Thanks Julian :)
Useful info! Can you see what the shoot_malloc reads in jpeg mode with Global Draw on and off?
Quote from: Andy600 on May 26, 2013, 12:23:23 AM
Thanks Julian :)
Useful info! Can you see what the shoot_malloc reads in jpeg mode with Global Draw on and off?
Seems to be the same. 212M, on and off. Is that possible?
Hmmm ???
I'm not sure. I'm just starting to get my head around some of the code and looking at where things can be improved (I'm no expert). I think there should be a change.
I'm doing an iso/low light test and I just can't believe what I'm seeing... H2 is too good to be true :o
Going to double, triple check and will share the results...
Guy's what card is advisable to use with the 50D? is the 90mb/s cards good enough?
Quote from: JulianH on May 26, 2013, 12:52:11 AM
I'm doing an iso/low light test and I just can't believe what I'm seeing... H2 is too good to be true :o
Going to double, triple check and will share the results...
That means the low light capabilities is awesome right?
Quote from: goldenchild9to5 on May 26, 2013, 01:02:14 AM
Guy's what card is advisable to use with the 50D? is the 90mb/s cards good enough?
That is the question that I'm about at the moment too, so from my thoughts, the fastest CF will be the better, it is only Toshiba 1066x that will be an overkill, as the 50D controller tops near 133Mb/s, so we can speak of around 120Mb/s real world write speed capability, as a result most of current high speed cards should perform near their max. specs.
By the way what 90Mb/s cards exactly were you refering to? By that speed you meant write or read speed? As 90Mb/s read speed cards are usually top at write ~50-60Mb/s only.
Just thought if LV mode is limiting the write speeds, maybe it will be also worth making a RAW video mode not involving the LV at all, for videos with static camera postion that could mean a higher res possibilities.
Quote from: moomilk on May 26, 2013, 01:12:19 AM
That is exactly the question that I'm about at the moment too, so from my thoughts, the fastest CF will be the better, it is only Toshiba 1066x that will be an overkill, as the 50D controller tops near 133Mb/s, so we can speak of around 120Mb/s real world write speed capability here as a result most of current high speed cards should perform at their max. specs.
By the way what 90Mb/s cards exactly were you refering to, by that speed you meant write or read speed? As 90Mb/s read speed cards are usually top at write ~50-60Mb/s only.
Just thought if LV mode is limiting the write speeds, maybe it will be also worth making a RAW video mode not involving the LV at all, for videos with static camera postion that could mean a higher res possibilities.
So the 90mb/s card are a no go than, on Amazon the 32gb version is going for $134 trying to keep it within budget with memory cards.
Try to get a Komputerbay 1000x 64GB card. They are popular with the 5D3 shooters which need maximum speeds. It is one of the cheapest fast cards. More on mem cards here: http://www.eoshd.com/content/10433/which-compact-flash-cards-for-5d-mark-iii-raw-video
Yeah for the price Komputerbay 64Gb seems to be the way to go, the only thing is that they can differ in speed a bit from card to card.
I wonder if Transcend 32Gb 1000x (priced about 120$ now) will be able to perform better, and reach the advertised 120Mb/s write speed.
Anyone seen any benches of it on 5D markII or 50d?
Hi all,
I've been skimming through this thread. Am I to understand that the 50d raw video performance are better with the 50d than with the 600d for instance?
If I understood well, you got pretty high resolution for raw videos at 24 fps, much higher than what the 600d is getting currently with ML.
I have been searching the web for which model to buy, and I was getting set on the 600d. But if you had to choose, would you say that the 50d is the one to go with? I can find some 50d at about the same price, or even cheaper than the 600d.
And globally is it the best for raw video in this range of price (so excluding the 5d series which are much more expensive)?
Thanks all for the great work on Magic Lantern! :-)
@Jehan - I've got both (600d and 50d) and for raw video there is no competition. 50d hands down! It's really the only one in this price range. Just waiting to test against a 5d2. I think it might beat that too ;)
http://www.eoshd.com/content/10507/it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster 8)
Quote from: Andy600 on May 26, 2013, 02:29:27 AM
http://www.eoshd.com/content/10507/it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster 8)
Haha, expect 50D prices to rise now...
Great to be the 'cause' of this article, thanks to all of you guys!
Good stuff Julian :)
Kudos and appreciation to the devs and of course @smeangol who is working on this port.
BTW Julian, I'm pretty sure the CF will reach about 88MB/s write speed (at least) before maxing out. Might be more, dunno yet.
Anyway, time for some sleep for me. Looking forward to seeing your low light footage!
Yes.. sleep indeed. Expect the footage tomorrow with more tests.
Quote from: JulianH on May 26, 2013, 01:29:43 AM
Try to get a Komputerbay 1000x 64GB card. They are popular with the 5D3 shooters which need maximum speeds. It is one of the cheapest fast cards. More on mem cards here: http://www.eoshd.com/content/10433/which-compact-flash-cards-for-5d-mark-iii-raw-video
Thanks for letting me know.. it's really cheap comparing it to the others Komputerbay it is than.
Quote from: Andy600 on May 26, 2013, 01:55:35 AM
@Jehan - I've got both (600d and 50d) and for raw video there is no competition. 50d hands down! It's really the only one in this price range. Just waiting to test against a 5d2. I think it might beat that too ;)
That's a real big statement beating the 5D Mark II thank goodness I got me a 50D..
Guy's just found a great deal on an almost new 50D excited placed my order, can't wait for it to get here.
Quote from: goldenchild9to5 on May 26, 2013, 03:43:02 AM
Guy's just found a great deal on an almost new 50D excited placed my order, can't wait for it to get here.
Congrats! :)
Here is my iso test! download the original file.. Amazing results, if you ask me.
@JulianH - There's the proof! The 50d is a winner in low light :o Thanks!
Quote from: JulianH on May 26, 2013, 12:19:56 PM
Here is my iso test! download the original file.. Amazing results, if you ask me.
AMAZING !!! Looking for one 50D for my self =DD
The 1st post in this thread has been updated :)
Can you believe that this camera was released BEFORE the 5d MkII?
I've been meaning to start using the ML hack for some time but never got around to it. Then I read about the ML HDR video feature, and this really got my attention, because I thought it was potentially a very noticeable way to change the apparent DR of Canon video compared to stock H.264. But now raw video has appeared and I've decided I can't stay out of this thing any longer! After recently reading nice things about the Nikon D5200 I thought I would get one of those next for video, but a few days ago I bought a second hand 50D instead, purely for raw shooting. I already have a 550D and 60D, so didn't plan on getting another crop Canon this year, but the price (at the moment at least) is almost disposable - I paid £330 for a body described by the seller as almost like new. It should arrive some time next week and I also ordered a KomputerBay 64 GB 1000x CF card. Hopefully, you guys can help me start experimenting with this exciting new development. Many thanks for your inspiring work here.
@TrueIndigo - A warm welcome to the club! We're here to help :)
Other example with 50D. Found in http://www.eoshd.com/comments/topic/2801-it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster/
https://vimeo.com/66622780
Hi!
Does this camera as good as mark 2 in low light?
And the second question: is it possible to rec in 1:1 crop with no drops?
Thanks! great news!
Quote from: arrinkiiii on May 26, 2013, 01:57:38 PM
Other example with 50D. Found in http://www.eoshd.com/comments/topic/2801-it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster/
https://vimeo.com/66622780
Thanks @arrinkiiii. I think that is part of this thread a couple of pages ago.
It's not strictly raw video in the same sense as the raw_rec module, it's the same DNGs but using the silent picture burst method which is limited to the camera's buffer size. Raw video will give exactly the same results though, just longer shooting times and selectable frame sizes/aspect ratios.
Quote from: tihon on May 26, 2013, 01:58:04 PM
Hi!
Does this camera as good as mark 2 in low light?
And the second question: is it possible to rec in 1:1 crop with no drops?
Thanks! great news!
We don't know yet because no one has done a comparrison with the 5d2 but you can see for yourself that the results are very promising.
1:1 crop is possible yes. At the moment it probably can't do more than a few seconds at it's maximum 1992x1080 but this will be worked on.
Quote from: Andy600 on May 26, 2013, 02:03:35 PM
Thanks @arrinkiiii. I think that is part of this thread a couple of pages ago.
It's not strictly raw video in the same sense as the raw_rec module, it's the same DNGs but using the silent picture burst method which is limited to the camera's buffer size. Raw video will give exactly the same results though, just longer shooting times and selectable frame sizes/aspect ratios.
Thank you for the enlightening Andy600 :D :D :D :D
So, canon=restrictions, damn!!! I think that all the major company's have software and hardware for the next 10 or 20 years to come, but of course they need to make money. Why go from 1 to 3, if they can sell the 2, right? Bastards !!!!
Im a 7D owner and now with the 50D Raw it make me again feel alive ;D
Ready for RAW? Let's go...!!!
Quote from: Andy600 on May 26, 2013, 02:06:33 PM
We don't know yet because no one has done a comparrison with the 5d2 but you can see for yourself that the results are very promising.
1:1 crop is possible yes. At the moment it probably can't do more than a few seconds at it's maximum 1992x1080 but this will be worked on.
Thanks! Can we record in 1:1 1080p but set the output resolution - 1592x840?
Yes, I can't test that specific res atm myself but you can select frame dimensions. The latest raw module makes frame sizes aspect ratio dependent but we're using the older module for the time being.
Not having a CF card seriously sucks! I feel like I've been given the keys to a Ferrari but it's got no petrol >:(
@TrueIndigo: welcome to the club :) I might do a video tutorial on shooting raw with the 50D for first timers (just need to find time). I guess there are more people picking these camera's up. It's not difficult to get started. Just filled my 32GB card with anamorphic shots. Results later today!
Quote from: Andy600 on May 26, 2013, 02:46:59 PM
Not having a CF card seriously sucks! I feel like I've been given the keys to a Ferrari but it's got no petrol >:(
Heh) In 1:1 you can set 1583px width and get 3x crop. Nice! But i think that it`s will be more soft then crop in 5d mark 3 because of small pixel size
I think the 50D progress is by far the most interesting revelation so far about the raw video!
It's cool to not only see some life reinjected into something like the 50D, but have bloody amazing video out of it when it wasnt even meant to have it haha.
Quote from: JulianH on May 26, 2013, 03:05:25 PM
@TrueIndigo: welcome to the club :) I might do a video tutorial on shooting raw with the 50D for first timers (just need to find time). I guess there are more people picking these camera's up. It's not difficult to get started. Just filled my 32GB card with anamorphic shots. Results later today!
Lets see that results :D
Whats wrong with magenta in 50d raw dng?
Quote from: JulianH on May 26, 2013, 12:19:56 PM
Here is my iso test! download the original file.. Amazing results, if you ask me.
Amazing results Wow!!! are you sure it was @ 12,000 ISO Winner in my book. I think we will be seeing a lot of 5D Mark II's for cheap on ebay soon cause everybody is gonna jump ship and get a 50D. I'm even thinking on getting a second 50D before those prices surge.
LCDVF3 solution for 50d http://www.magiclantern.fm/forum/index.php?topic=5722.new#new
Quote from: Andy600 on May 26, 2013, 11:13:21 AM
Congrats! :)
Thank you man.. now I have to order a Komputerbay 64gb card, and an EF / M42 adapters for my manual lens.
Thanks for the welcome. If I can get raw working on a 50D with your help, I think that would usefully prove that anyone can do it! Cheers.
Quote from: tihon on May 26, 2013, 03:27:23 PM
Whats wrong with magenta in 50d raw dng?
The black point fix needs incorporating along with a couple of minor framing adjustments. Should be fixed soon :)
Quote from: JulianH on May 26, 2013, 03:05:25 PM
@TrueIndigo: welcome to the club :) I might do a video tutorial on shooting raw with the 50D for first timers (just need to find time). I guess there are more people picking these camera's up. It's not difficult to get started. Just filled my 32GB card with anamorphic shots. Results later today!
Please do a tutorial Julian would greatly appreciate it. You and Andy600 are the pioneers for the 50D, post those footages up later can't wait to see.
Preview! Quick edit:
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_94354.jpg)
Quote from: Andy600 on May 26, 2013, 02:46:59 PM
Not having a CF card seriously sucks! I feel like I've been given the keys to a Ferrari but it's got no petrol >:(
Lol.. I know it sucks Andy trying to get my hands on that Komputerbay 64GB ASAP..
Quote from: JulianH on May 26, 2013, 04:16:12 PM
Preview! Quick edit:
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_94354.jpg)
That looks filmic, please post video as soon as you can.
Be patient, a raw workflow isn't very fast... ;)
Hi, my 50d turned up yesterday, still waiting for my komputerbay 1000x 64gb though. As soon as it turns up I'll help out with the testing.
Looking forward to shooting some raw, I've had enough of 8 bit video!
Moire can be pretty bad by the way.
Worst case scenario: http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_317938.jpg
Most of the shots are fine though. Even with small lines and detail.
Quote from: JulianH on May 26, 2013, 05:50:22 PM
Moire can be pretty bad by the way.
Worst case scenario: http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_317938.jpg
Most of the shots are fine though. Even with small lines and detail.
is that 50d? mama miaaa
Yes it is :) Can't be all perfect... But like I said, worst case scenario.
Don't be alarmed guys! You can always stop-up to a shallower DOF, use some post trickery or just shoot something else. The 1:1 crop will also deal with it if you have a wide enough lens. It's never gonna be perfect but I suspect that scene would be crawling all over the place on most other cameras. The 5d3 would eat it no problem but at 10x the cost of the 50d :D
Exactly. Just trying to 'keep it real' here ;) We are all pretty enthusiastic, and we should be. But it's still early testing and it's not all going to be perfect. So I will post the bad stuff as well.
To make sure you guys won't run away from the 50D now, here's another shot, with lots of fine details, but hardly any nastiness:
http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_214987.jpg
The question is - would the 5d2 fair any better?
Answers on a postcard to:
The moire is killing me
c/o Canon inc.
Japan
;D
I just thought. We could strap 4 of these together in a matrix and just about get 4k raw for under 2k ;D
Another headline ::)
...or spend up to the cost of a RED for... ummmm.... 32k...maybe LOL
Damn! Plan thwarted. Didn't think it through. How much would all that glass cost? and how would you focus? :-\
Quote from: JulianH on May 26, 2013, 04:16:12 PM
Preview! Quick edit:
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_94354.jpg)
Thanks! Can you upload a dng file?
Will do. My computer is sweating now, exporting the dng's :)
"Neither camera featured dedicated video recording however, the 50d did have the feature, disabled in the Canon firmware. ML unlocked this to enable 1080p at 30fps with the ability to use FPS override for 24/25p."
Maybe a stupid question, but since I am buying a 50d and may need to shoot longer pieces where RAW would be impractical, confirming that I can shoot regular 5d style 1080 h264 on the 50d with the ML download?
Quote from: JulianH on May 26, 2013, 07:32:47 PM
Will do. My computer is sweating now, exporting the dng's :)
Raw is intensive.. but gotta love it cause the benefits outweighs the cons.
Quote from: eckelsteve on May 26, 2013, 08:01:24 PM
Maybe a stupid question, but since I am buying a 50d and may need to shoot longer pieces where RAW would be impractical, confirming that I can shoot regular 5d style 1080 h264 on the 50d with the ML download?
You can, but bear in mind it was not made for it, there is no audio recording on the 50D for example!
no audio is a bummer. especially since it is such a low-end feature, but means the world to pluraleyes users like me :-P
Yeah probably the simplest solution to synching it all together is having a cheap and nasty camera (like an early gopro or something) recording both sound and video at a very low bitrate, just for the sake of synching things with pluraleyes or whatever.
Pretty monsterous workflow compared to shooting normally with a different audio capable DSLR, but gotta pay to play!
I'm bidding on a 50D at the moment. In my mind it seems the best $$ option for raw video, and often when I've been shooting a time lapse or something I've been mega bored, so a second camera body will help keep me entertained. Nice burst rate too compared to my 600D.
It forces you to use some old skool tricks. A clapper board as a visual cue and external recording. Ok, it's not syncing but it's a workflow that was used in thousands of old movies. Hopefully some kind of timecode (preferably SMTPE) can be incorporated in ML in the future but I don't know if that is even possible.
Back from the dead :)
Quotehttp://www.eoshd.com/content/10507/it-lives-5-year-old-350-canon-50d-becomes-raw-cinema-monster
Nice article gives somewhat the feeling it was really woth it spending some night on this :)
Same "framegrabs" from the weekend - thanks to my slow card i get 2 sec duration at once :/ ( right click + "show image" to see the picture in full size)
1592x840p:
(http://www.smeangol.com/000016.jpg)
One of the undisturbed frames with 1920 X 720p - processed with UFRAW, no sharpening - now in jpg
Mind there is some motion blur before you judge.
(http://www.smeangol.com/000001.jpg)
Another!
(http://www.smeangol.com/000076.jpg)
Moire is absolutely present! But i think it is okay.
(http://www.smeangol.com/000004.jpg)
Someone got a good and fast workflow with free software to "expose" the DNG via batch? If so i will make a nice video with all my material!
It was definitely worth it Smeagol. Big thanks for your efforts! I can understand the focus is mostly on the 5D3 and other popular cams, but the 50D really is a little monster that deserves some attention :)
You coud try RAWanizer to batch your DNG's into video's maybe? (Windows).
http://www.magiclantern.fm/forum/index.php?topic=5557.0
Not sure if it will come out nice, when I open the DNG's I have to fix the white balance first so the proxies I made before with RAWanizer were way off. It's been updated since, going to try again :)
@Smeangol Welcome back :)
I totally agree with Julian. There is quite a buzz about the 50d now thanks to your port of the raw video features and Julian's weekend test shots. A lot of people are looking at the 50d as the lower budget alternative to the 5dmk3 which means a bigger 50d community. Great work!
I'll do my best to help iron out some of the bugs. I'm understanding the code more so hopefully I'll be able to contribute towards some improvements and minor bug fixes but it is working and looking good! :) It might be worth checking out the alternative raw module that's in development for the 5d2 as the 50d has a lot in common with it: http://www.magiclantern.fm/forum/index.php?topic=5655.0
I'm also a fan of the Rawanizer app. It's by far the best (and fastest) way to get the raw files ready for editing.
Finally! Graded, exported, edited, uploaded...
Details on Vimeo. Make sure to download the original file. Let me know what you think!
Oh RAWanizer just looks like i was looking for :) THX
@JulianH: The anamorphic Adapter seems to be a nice workaround for 4:3 'ish resolution of the 50D - looks good - tell me .. where did you film the trainstation scenes? Looks very familiar to me :)
Everything was shot around the Central Station of Den Haag, Netherlands :)
Quote from: JulianH on May 27, 2013, 12:38:58 AM
Finally! Graded, exported, edited, uploaded...
Details on Vimeo. Make sure to download the original file. Let me know what you think!
Impressive video, nice work :D
Did you find any moire? And if yes can be a software or raw to dng's ?? If the 50D got so big issues with moire whats it's possible to do to work around with this problem?
Thanks!
Found plenty of moire and aliassing. Download the video. See for yourself... I left out the worst shots, like that screenshot I posted above. But as you can see, the final result can be pretty decent I think. I didn't do any correction for moire.
Most of this was shot at f/8-f/16. It would help to shoot at bigger apertures so not everything is in focus...
Quote from: JulianH on May 27, 2013, 12:38:58 AM
Finally! Graded, exported, edited, uploaded...
Details on Vimeo. Make sure to download the original file. Let me know what you think!
Once again beautiful video.. 50D lives on the images are soo clean... In a couple spots I saw some frame skipping am I right? and a little motion blur in two of the shots.
Quote from: smeangol on May 27, 2013, 12:51:06 AM
Oh RAWanizer just looks like i was looking for :) THX
@JulianH: The anamorphic Adapter seems to be a nice workaround for 4:3 'ish resolution of the 50D - looks good - tell me .. where did you film the trainstation scenes? Looks very familiar to me :)
Welcome back smeangol..
Yeah, added a note on the frame skipping. It's probably my fault with making the image sequences, had some trouble with that... Didn't experience frame skipping during recording, but will upload a DNG sequence tomorrow so others can have a look!
Quote from: JulianH on May 27, 2013, 01:39:33 AM
Yeah, added a note on the frame skipping. It's probably my fault with making the image sequences, had some trouble with that... Didn't experience frame skipping during recording, but will upload a DNG sequence tomorrow so others can have a look!
Nice.. footage looking aswesome did you experience any motion blur at all doing recording, or it might of been the transcoding once again right? Once again appreciate all your efforts Julian, @smeangol we need you back ;D
Quote from: JulianH on May 27, 2013, 01:39:33 AM
Yeah, added a note on the frame skipping. It's probably my fault with making the image sequences, had some trouble with that... Didn't experience frame skipping during recording, but will upload a DNG sequence tomorrow so others can have a look!
Forgot to ask you you don't use (Raw2Dng) software any longer? What's the difference between the new one you posted and Raw2Dng?
What do you mean by motion blur? I'm filming at 24 fps with 1/50 shutter. There is supposed to be motion blur in moving things. That makes it look filmic ;)
RAWanizer uses Raw2DNG. It's just does more things!
Quote from: JulianH on May 27, 2013, 01:51:03 AM
What do you mean by motion blur? I'm filming at 24 fps with 1/50 shutter. There is supposed to be motion blur in moving things. That makes it look filmic ;)
RAWanizer uses Raw2DNG. It's just does more things!
You soo right Julian, Love those images it is so filmic.. Got another question should I order my 64GB Komputerbay from EOSHD source (Ebay) , or on Amazon found them there as well. If you ordered one where did you get your's from?
Quote from: goldenchild9to5 on May 27, 2013, 01:37:00 AM
Once again beautiful video.. 50D lives on the images are soo clean... In a couple spots I saw some frame skipping am I right? and a little motion blur in two of the shots.
Just watched it on a 50 inch screen Wow all I can say is (Movie) Like.
Just ordered a Komputerbay 64GB directly from them through Amazon, shipping was free. Have you guy's noticed how the suddenly increased the price by $8 Huuh!!! Does the ML Raw hack have anything to do with it.. "Absolutely" I won't be surprise if they increase it again, cause comparing it to the other brands there is a major price difference.
Quote from: goldenchild9to5 on May 27, 2013, 02:52:27 AM
You soo right Julian, Love those images it is so filmic.. Got another question should I order my 64GB Komputerbay from EOSHD source (Ebay) , or on Amazon found them there as well. If you ordered one where did you get your's from?
I bought mine on eBay but the package came in a flat Amazon cardboard package.
500MB DNG sequence (https://www.wetransfer.com/downloads/6277c46a98731a6c795f8f5e6c5c8d5d20130526234611/38ccc37246a862f48ee3d397f664216a20130526234611/cd541e)
If you want to play with the DNG's... (and see if you can get it working without frame skipping ;))
Is it possible to give a try on 1440 x 810 ?
it will be around 49MB/s and probably no skip frames, the best resolution for 16:9 video in the 50D.
1366 x 768 would a good option for 16:9 too, around 44MB/s
Each camera/card combo deserves more width options to get the best possible resolution without skip frames, so have 1280, 1366 and 1440 width will be good to find the best possible resolution without skip frames for each user.
thanks
There's no 1440 or 1366.
Options in the build i'm using:
Width: 640, 720, 960, 1280, 1320, 1920 (this resets to 1592 automatically).
Height: 320, 360, 480, 540, 720, 840, 960, 1080 (this resets to 1062).
Would be nice to have some more resolutions. Especially something between 1320 and 1592. Is this possible?
Just realised I should try 1320x840 with 1.5x anamorphic. That would make 1980x840 = 2,36:1 :)
Hi guys,
Would it be possible to try all this out on the 40D.
I have one happy to test with.
Cheers
D
I'll try compiling a new raw module with more values. I know it's hit and miss as to whether they will work. Still working blind here (no CF :( )
@Dunc101 - Sorry, not possible yet. We need a dev with a 40d to port the changes as it's much harder to do without having the actual camera to hand in order to test every change. It might be looked at after the 50d is sorted.
Quote from: JulianH on May 27, 2013, 09:39:56 AM
500MB DNG sequence (https://www.wetransfer.com/downloads/6277c46a98731a6c795f8f5e6c5c8d5d20130526234611/38ccc37246a862f48ee3d397f664216a20130526234611/cd541e)
If you want to play with the DNG's... (and see if you can get it working without frame skipping ;))
Thanks for posting julian.. will play with images.
Quote from: PressureFM on May 27, 2013, 09:37:42 AM
I bought mine on eBay but the package came in a flat Amazon cardboard package.
So they are all from the same source than, that makes sense now.
Quote from: Andy600 on May 27, 2013, 02:04:04 PM
I'll try compiling a new raw module with more values. I know it's hit and miss as to whether they will work. Still working blind here (no CF :( )
When did you order your card?
Guy's check this Raw Film batch converter out it's very interesting "Create a true film simulation of your video using RAW PHOTO PROCESSOR"
http://youtu.be/ICwv6GYLC9I
<iframe width="560" height="315" src="http://www.youtube.com/embed/ICwv6GYLC9I" frameborder="0" allowfullscreen></iframe>
And here is the site: http://www.raw-photo-processor.com/RPP/Overview.html
Let me know what you think about it.
Quote from: Andy600 on May 27, 2013, 02:06:17 PM
@Dunc101 - Sorry, not possible yet. We need a dev with a 40d to port the changes as it's much harder to do without having the actual camera to hand in order to test every change. It might be looked at after the 50d is sorted.
@Andy600 -
I have the basics to hacking in a compiler, I could try, if I can have a few pointers.
Cheers
D
Quote from: goldenchild9to5 on May 27, 2013, 06:57:43 PM
Guy's check this Raw Film batch converter out it's very interesting "Create a true film simulation of your video using RAW PHOTO PROCESSOR"
Let me know what you think about it.
Mac only, I'm on Windows.. looks interesting though.
Quote from: Dunc101 on May 27, 2013, 07:50:40 PM
@Andy600 -
I have the basics to hacking in a compiler, I could try, if I can have a few pointers.
Cheers
D
Very nice :D thats the way Dunc101 :D
@Dunc101 start here: http://www.magiclantern.fm/forum/index.php?topic=991.0 (I recommend using the VM compiler unless you're comfortable building your own. I tried the Windows one (cygwin) but the VM one is much better.
Get a Bitbucket account and fork from the unified build: https://bitbucket.org/hudson/magic-lantern and read up on Mercurial if you haven't used it :http://mercurial.selenic.com/wiki/Tutorial
Clone the repo locally.
@coutts has the stubs for 40d (but I have no clue as to what you would do with them)
That's where my knowledge ends I'm afraid.
I can pull changes, do minor code adjustments and compile but beyond that I'm a complete novice. The code is usually well commented so it's a case of going through it and trying to understand it a little piece at a time.
Porting the 40d will be a much harder thing than what I am capable of so good luck if you attempt it. There is already a port for the 50d and a developer working on incorporating the new features. I'm concentrating on understanding what these new additions do and looking for bugs.
This is weird. I've been shooting some footage, the camera reached 45 MB/s with the Transcend 16 GB 1000x. But suddenly the rate dropped to 25 again. That is so strange. I didn't change any variables, why does this happen. Nevertheless I shot 30 seconds of footage in 1592x720 which im going to upload now for you to look at.
Make sure you turn all the overlays off, also the Canon ones. Sad to hear the speed drops :(
1592x720 works fluid here with my Sandisk 90MB/s.
Quote from: JulianH on May 27, 2013, 09:39:56 AM
500MB DNG sequence (https://www.wetransfer.com/downloads/6277c46a98731a6c795f8f5e6c5c8d5d20130526234611/38ccc37246a862f48ee3d397f664216a20130526234611/cd541e)
If you want to play with the DNG's... (and see if you can get it working without frame skipping ;))
Weird, I looked it through and it doesn't frame skip here. There must be something wrong with your workflow or Vimeo/Youtube does something when re-encoding.
https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov (https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov)
Quote from: JulianH on May 27, 2013, 08:08:26 PM
Mac only, I'm on Windows.. looks interesting though.
It's Windows as well go to there site you will see the windows download link..
Quote from: dacssfreak on May 27, 2013, 09:10:07 PM
This is weird. I've been shooting some footage, the camera reached 45 MB/s with the Transcend 16 GB 1000x. But suddenly the rate dropped to 25 again. That is so strange. I didn't change any variables, why does this happen. Nevertheless I shot 30 seconds of footage in 1592x720 which im going to upload now for you to look at.
Try reformatting your card and reinstall ML with Raw Hack I was reading something about speeds drops the other day. If you try it and it does not work than it might be something with your card.
Quote from: PressureFM on May 27, 2013, 09:57:44 PM
Weird, I looked it through and it doesn't frame skip here. There must be something wrong with your workflow or Vimeo/Youtube does something when re-encoding.
https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov (https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov)
That's what I said too, the sequence has no frame drops, or skipping so something definitely went wrong with the encoding, or Vimeo.
Quote from: JulianH on May 27, 2013, 09:29:23 PM
Make sure you turn all the overlays off, also the Canon ones. Sad to hear the speed drops :(
1592x720 works fluid here with my Sandisk 90MB/s.
How many seconds of recording time do you get @ that Res..? Does it get to the 4GB file limit? Man I can't wait to get my 50D & all the other stuff to start shooting and testing. The holidays made it even slower, but I'll be patient.
hi all - first post - thank you for efforts and information.
just installed ml 50D from this thread - crashing @1592x720 with lexar 1000x 32G
will turn off all overlays, switch to jpg for photo, and let you know.
Andy600 and Smeangol,
are the autoexec.bin and modules linked on the 2nd post to smeangol.com/ still the best to use for the 50D?
i see the fork https://bitbucket.org/smeangol/smeangols-sneaky-magic-lantern/commits/all with commits on 25.05.2013
the files in the Modules folder were compiled 18-23.
is there another fork or more recent code i could (should) try?
50D vs 5D Mark II raw 8)
Notes, details and settings on Vimeo. You can download the file or watch here in 1080p!
Quote from: GregoryOfManhattan on May 27, 2013, 11:08:44 PM
hi all - first post - thank you for efforts and information.
just installed ml 50D from this thread - crashing @1592x720 with lexar 1000x 32G
will turn off all overlays, switch to jpg for photo, and let you know.
Andy600 and Smeangol,
are the autoexec.bin and modules linked on the 2nd post to smeangol.com/ still the best to use for the 50D?
i see the fork https://bitbucket.org/smeangol/smeangols-sneaky-magic-lantern/commits/all with commits on 25.05.2013
the files in the Modules folder were compiled 18-23.
is there another fork or more recent code i could (should) try?
Welcome :) use the ones from post #2 for the moment. Any changes, new downloads etc will be updated in 1st post
Quote from: JulianH on May 27, 2013, 11:33:40 PM
50D vs 5D Mark II raw 8)
Notes, details and settings on Vimeo. You can download the file or watch here in 1080p!
Nice test man was waiting for that one, downloading original files right now. 50D seems to be more organic and Film like to me, and the noise is cleaner @ 6400 ISO than the 5D Mark II. Even after you scale the 50D's image it still hangs with the Mark II impressive.
Hello everyone! I was already selling my 50D until I saw this, awesome job guys! Already installed it but since my 266x Kingston is choking I need to get new card and I can't order it until next week, oh the agony! But keep those test & comparison videos coming, keeps me going until I get faster card :)
Hi all, I ordered a 50D for 400$ last week (guess i did well because now they are at around 500$ on ebay!)
Ordered a Komputerbay 64GB 1000x CF Card too!
I hope you guys will help improve this little raw beast :)
Quote from: JIKIJI on May 28, 2013, 02:41:24 AM
Hi all, I ordered a 50D for 400$ last week (guess i did well because now they are at around 500$ on ebay!)
Ordered a Komputerbay 64GB 1000x CF Card too!
I hope you guys will help improve this little raw beast :)
Welcome on board.. you sure got a good deal got mines 3 days ago for $460 bet in another week or so they might go up to $550, or $600
Quote from: Markkedi on May 28, 2013, 12:56:52 AM
Hello everyone! I was already selling my 50D until I saw this, awesome job guys! Already installed it but since my 266x Kingston is choking I need to get new card and I can't order it until next week, oh the agony! But keep those test & comparison videos coming, keeps me going until I get faster card :)
Great decision on not selling it, Patience my friend 8) waiting on my card as well. What card did you get?
So there are a few 50d's in my area going for around $450. I would like to snag one up before prices raise, but have a few questions.
Is there any possibility of getting the 50d to shoot full 1080 or 1920x810?
My dilemma is whether to go with the 50d or the black magic pocket camera when it comes out.
Guy's check out this sample video from the 50D looks awesome ;D
Quote from: Hokie123 on May 28, 2013, 05:39:15 AM
So there are a few 50d's in my area going for around $450. I would like to snag one up before prices raise, but have a few questions.
Is there any possibility of getting the 50d to shoot full 1080 or 1920x810?
My dilemma is whether to go with the 50d or the black magic pocket camera when it comes out.
Right now it's not there yet but it will be I believe. Give the hack sometime and the programmers will eventually make everything work. As far as which camera to get huuh!! for me the Blackmagic Pocket Cinema Camera is a no brainer ProRes 422 HQ / Compress Raw 13 stops of dynamic range and it records on SD cards $1000 can't beat that, got one on pre-order right now. 50D Raw 14bit recording with wide dynamic range, no audio recording, and Huge file sizes with small record time limit, and finally a beautiful image. For me the 50D is an experimental camera that I will be using for major projects just because of what it offers, and the filmic images it produces. If I were you I would get both and call it a day.
Quote from: goldenchild9to5 on May 28, 2013, 06:15:01 AM
Right now it's not there yet but it will be I believe. Give the hack sometime and the programmers will eventually make everything work. As far as which camera to get huuh!! for me the Blackmagic Pocket Cinema Camera is a no brainer ProRes 422 HQ / Compress Raw 13 stops of dynamic range and it records on SD cards $1000 can't beat that, got one on pre-order right now. 50D Raw 14bit recording with wide dynamic range, no audio recording, and Huge file sizes with small record time limit, and finally a beautiful image. For me the 50D is an experimental camera that I will be using for major projects just because of what it offers, and the filmic images it produces. If I were you I would get both and call it a day.
Hmm, well currently I have a t2i, I plan on shooting RAW for short narrative films. I would use my t2i for everything else.
Getting a 50d now and a black magic pocket camera down the line sounds like a good idea. I could potentially sell the t2i and use the 50d for stills and the pocket camera for non-narrative video. Or I could save for a much more expensive camera such as a 5d mk3 to shoot RAW or the black magic cinema camera.
What path would you recommend?
Quote from: PressureFM on May 27, 2013, 09:57:44 PM
Weird, I looked it through and it doesn't frame skip here. There must be something wrong with your workflow or Vimeo/Youtube does something when re-encoding.
https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov (https://www.dropbox.com/s/ydcioufxct9oz1y/No_Frame_Skip.mov)
I think that skipping is because the program and camera is with different frame rates (like 24fps to 25fps or something like that).
Quote from: Hokie123 on May 28, 2013, 06:30:04 AM
Hmm, well currently I have a t2i, I plan on shooting RAW for short narrative films. I would use my t2i for everything else.
Getting a 50d now and a black magic pocket camera down the line sounds like a good idea. I could potentially sell the t2i and use the 50d for stills and the pocket camera for non-narrative video. Or I could save for a much more expensive camera such as a 5d mk3 to shoot RAW or the black magic cinema camera.
What path would you recommend?
Blackmagic Pocket Cinema Camera is a must.. long recording, no headaches a true S16 Cinema Camera, have you seen Johns Brawley's new video test yet? go check it out. Now that I know you have a T2i, by the way I use to have one also sold it love that little camera. If you love the images from the Raw cannons that much, I would sell my T2i cause you are limited as far as shooting Raw on it & use that money to upgrade to the 50D & I would do it fast cause prices will go up fast. Second scenario Holding on to your T2i for pictures like you said & wait for the Pocket Cinema Camera to come out. Third scenario buying the 50D test it out if you like it keep it, if not sell it back I guarantee you will make a profit selling it back you can't lose by getting the 50D. Hope that help you decide cheers..
I was going to pay off my credit card... but now I'm going to use that money to buy a 50D I think. I already have a 60D and 550D, but the RAW video on the 50D won't be matched by those due to the SD cards it seems...
I know that it can record at 720 height, how's the 1080p (or higher) looking? And what are the crop factors so far?
Hi. new to the board, but I was wondering why all talk is about recording to the CF and not HDMI (wiki says 50d does do hdmi out). Is this also the case on the 5d3? Also, what's the difference between recording to the buffer and the raw_rec?
Because the HDMI output goes through all of the compression etc as a normal recorded video file, and is 8 bit.
Where as recording to the cf card is 14 bit raw images at a fairly hefty bitrate.
I'm about an hour away from owning a 50D with a battery grip and 4 batteries, only challenge now will be finding a place that sells fast CF cards for less than a billion dollars that ships to New Zealand. :(
I got a very important question how come when I open the DNG files in Adobe Camera Raw (ACR) the metadata at the bottom shows :
Adobe RGB (1998) not sRGB : 8bit instead of 14bit I don't know what's going on. In Digital Space the cameras are Usually sRGB specially for video, Adobe RGB (1998) is good for print. I tried numerous other files even files from the 5D Mark III it still shows up with the same data. I'm soo confused right about now enlighten me.. anybody I thought that It was suppose to be be 14bit Raw.
Quote from: goldenchild9to5 on May 28, 2013, 03:11:16 AM
Great decision on not selling it, Patience my friend 8) waiting on my card as well. What card did you get?
Getting my paycheck next wednesday and I'm thinking of getting a Komputerbay 64GB 1000x card. The best thing is that I traded my 40D few weeks ago to this 50D @ 20k shutter count with just 50 euros :)
Quote from: Markkedi on May 28, 2013, 08:50:01 AM
Getting my paycheck next wednesday and I'm thinking of getting a Komputerbay 64GB 1000x card. The best thing is that I traded my 40D few weeks ago to this 50D @ 20k shutter count with just 50 euros :)
That's a great trade, that means you got another two weeks to to before you do any real shooting.
Quote from: goldenchild9to5 on May 28, 2013, 08:43:16 AM
I got a very important question how come when I open the DNG files in Adobe Camera Raw (ACR) the metadata at the bottom shows :
Adobe RGB (1998) not sRGB : 8bit instead of 14bit I don't know what's going on. In Digital Space the cameras are Usually sRGB specially for video, Adobe RGB (1998) is good for print. I tried numerous other files even files from the 5D Mark III it still shows up with the same data. I'm soo confused right about now enlighten me.. anybody I thought that It was suppose to be be 14bit Raw.
Don't worry. Click that line and you can change the settings to whatever you want. It is the workflow setting, ACR will import your raw to these settings when you click open, save or done. Look at the file info in bridge, you'll see the files are 14 bit.
@Roman: Thanks for the reply.
I'm waiting on a card myself. Perhaps I'll just rent a sandisk card to see how many frames I can get.
Also another thing, unless someone who's actually got one can confirm to the contrary,
The 50D does HDMI out, as in, you can view pictures on the TV or whatever. As best I know it's not possible to use an external monitor in a configuration which would allow recording an HDMI stream from the sensor, either way.
First post on the forum
(I've been using ml for quite some times now. On a t3i. For video mainly, time lapse, zebra, long time exposure, etc)
I played with the dng and i'm realy impressed.
The workflow is a bit slower but for 30 minutes of works for 12 seconds, from downloading the dng's, to lightroom and finaly vegas. It's not that bad at all considering that i have to color grade anyway because i use cinestyle when doing some videos.
Of course no audio can be a little of a bummer for some. But hey, will you use this camera alone? I don't think so. Having 2 cams to work with is great anyway. I'm working on a videoclip right now and this new tool will be amazing!
The t3i to sync with pluraleyes and the 50d for filmic in between shots.... Yummy
If any of you whants to see what s**t i do lol :
http://youtu.be/5z70iMgtNtQ
Exactly. Combination of h.264 for shallow DOF shots and RAW for chroma key and landscape shots is great workflow for me.
Oh lordy...
It's hot news on EOSHD, Petapixel, Canon Rumours, Nofilmschool.com and loads more DSLR blogs but now some giants, namely Cnet and Engadget have picked up on it:-
http://www.engadget.com/2013/05/28/canon-50d-gains-video-recording-through-magic-lantern-raw-hack/
http://www.cnet.com.au/canon-50d-takes-raw-video-thanks-to-magic-lantern-339344418.htm
The ML Devs deserve huge credit! @Smeangol specifically for his work on porting the raw features to the 50d!
Quote from: Viente on May 28, 2013, 04:22:25 PM
Exactly. Combination of h.264 for shallow DOF shots and RAW for chroma key and landscape shots is great workflow for me.
what do you mean by using h.264 for shallow DOF,can it not be achieved shooting raw?
Quote from: Andy600 on May 28, 2013, 04:26:42 PM
Oh lordy...
It's hot news on EOSHD, Petapixel, Canon Rumours, Nofilmschool.com and loads more DSLR blogs but now some giants, namely Cnet and Engadget have picked up on it:-
http://www.engadget.com/2013/05/28/canon-50d-gains-video-recording-through-magic-lantern-raw-hack/
http://www.cnet.com.au/canon-50d-takes-raw-video-thanks-to-magic-lantern-339344418.htm
The ML Devs deserve huge credit! @Smeangol specifically for his work on porting the raw features to the 50d!
Now it's in the open big media is covering it. I don't think ebay will have any more 50D's demand is going to go way high..
Quote from: Hokie123 on May 28, 2013, 04:40:37 PM
what do you mean by using h.264 for shallow DOF,can it not be achieved shooting raw?
I mean sometimes if you need a longer footage its not a problem to shoot in old mode on not so detailed shots.
Quote from: Hokie123 on May 28, 2013, 04:40:37 PM
what do you mean by using h.264 for shallow DOF,can it not be achieved shooting raw?
Wondered the same thing. Dof doesn't realy cares about h.264 ;)
Edit instead of trolling: got it, you ment convenience vs beauty :)
Cool stuff. I think the 50d will be a nice raw camera. I own a 5d2, but looking for a good alternative for shooting raw only and think I might have found one :)
hello and big thanks to everyone involved!
question, how do i enable 24p? i can only switch from 30fps to 2.5fps. also tried advanced mode. i've tried stable release and current nightly build. even with 64gig 1000x KomputerBay card i can only get about 300 frames at 1592x720.
i know the cards may vary and i have yet to try low level formatting card.
thanks for any help!
Hey Blackroom, welcome to the 50D club!
Press the joystick when you are navigated onto the 'FPS override' item. There you can select the framerate. Took me a while to figure that out as well ;) Please share your tests and footage!
thanks Julian! i can record long now at 24p, never quite reach 4 gigs but thats another issue.
You can't record continuously at 1592x720 24 fps with the KomputerBay card? That sounds weird as I can with my Sandisk 90MB/s 32GB.
Did you turn off all the overlays? Press the info button till you get a clear screen without any info.
How long can you record? I can record till 4GB (then it stops) without problems. The buffer never goes over 2 stars (out of 4).
Hmmm 4 stars ??? I think it should have more than that.
It never showed me more than 4 stars I think.
While recording 1592x720 it looks like this: (*...) sometimes it goes up to (**..) but then drops again to (*...)
With higher resolutions like 1592x840 it quickly goes to (**..) and (***.) and then starts to drop frames.
My understanding is that the stars are representative of chunks (31 - 32mb) of buffer data. The 50d has @2x that of the 600d which shows 3 stars, so I'm hazarding a guess that there could be some memory savings to be had somewhere to increase this to maybe 5 or more = bigger frame sizes. I think it would be important for the 1:1 crop mode... but then again, what do I know LOL ;)
Quote from: Andy600 on May 28, 2013, 09:31:13 PM
My understanding is that the stars are representative of chunks (31 - 32mb) of buffer data. The 50d has @2x that of the 600d which shows 3 stars, so I'm hazarding a guess that there could be some memory savings to be had somewhere to increase this to maybe 5 or more = bigger frame sizes. I think it would be important for the 1:1 crop mode... but then again, what do I know LOL ;)
It might be Andy.. let's wait and see how things pans-out.
Quote from: blackroom on May 28, 2013, 07:47:50 PM
thanks Julian! i can record long now at 24p, never quite reach 4 gigs but thats another issue.
Great you got things running now. Report back & let us know if your getting to the 4GB limit with the Komputerbay 64GB card...
Hello. I am not sure if this is the right topic, but I have a few questions to ask.
I am about to buy a used 50D in order to shoot raw video, I understand it is the best choice for those who cant afford a 5D2?
1.Does it record well in 24fps? That is the framerate I plan on shooting in, and want to sync audio to it, so accuracy is key.
2. Also, could I shoot raw at 30fps and slow it down to 24fps in post? Not caring about audio sync here.
3. How does raw recording affect the camera body? Does it overheat?
4. How is it on the camera's battery? I plan on using a battery grip, so how much recording time will I get on two fully charged batteries?
5. How big are raw files. Like MB/min.? How much am I going to be able to fit in a 64gb cf card?
6. Is the KOMPUTERBAY 64GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 a solid choice as the only cf card I would buy?
Thank you very much. I would appreciate any info that might be useful. I currently have a 550D so I guess the upgrade is worth it?
Quote from: Andy600 on May 27, 2013, 08:35:43 PM
@Dunc101 start here: http://www.magiclantern.fm/forum/index.php?topic=991.0 (I recommend using the VM compiler unless you're comfortable building your own. I tried the Windows one (cygwin) but the VM one is much better.
Get a Bitbucket account and fork from the unified build: https://bitbucket.org/hudson/magic-lantern and read up on Mercurial if you haven't used it :http://mercurial.selenic.com/wiki/Tutorial
Clone the repo locally.
@coutts has the stubs for 40d (but I have no clue as to what you would do with them)
That's where my knowledge ends I'm afraid.
I can pull changes, do minor code adjustments and compile but beyond that I'm a complete novice. The code is usually well commented so it's a case of going through it and trying to understand it a little piece at a time.
Porting the 40d will be a much harder thing than what I am capable of so good luck if you attempt it. There is already a port for the 50d and a developer working on incorporating the new features. I'm concentrating on understanding what these new additions do and looking for bugs.
@Andy600
Thanks very much this is great.
I am a novice too but my as well try.
@coutts any idea what to do with the stubs?
Cheers
D
@Dunc101 - The 40d was/is (maybe) being ported. It looks as though updates stopped a couple of months ago but you might want to try compiling this to see where it's up to: https://bitbucket.org/jplxpto/magic-lantern/commits/all ;)
Quote from: johansugarev on May 28, 2013, 11:17:21 PM
Hello. I am not sure if this is the right topic, but I have a few questions to ask.
I am about to buy a used 50D in order to shoot raw video, I understand it is the best choice for those who cant afford a 5D2?
Keep in mind this is very experimental. Don't make any conclusions yet.
1.Does it record well in 24fps? That is the framerate I plan on shooting in, and want to sync audio to it, so accuracy is key.
- Yes, you can use fps override and film at 24.000 fps exactly. 1592x720 works without problems for me at 24 fps.2. Also, could I shoot raw at 30fps and slow it down to 24fps in post? Not caring about audio sync here.
- Probably you could, but 30 fps takes more data so you'd have to lower the resolution. I didn't try anything at 30 fps yet.3. How does raw recording affect the camera body? Does it overheat?
It doesn't. The camera has less work to do4. How is it on the camera's battery? I plan on using a battery grip, so how much recording time will I get on two fully charged batteries?
- Don't know exactly. Pretty sure you can fill 64GB before draining two batteries... 5. How big are raw files. Like MB/min.? How much am I going to be able to fit in a 64gb cf card?
- Depends on the resolution. 1592x720 24p is about 50MB/s = 3GB per minute.6. Is the KOMPUTERBAY 64GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 a solid choice as the only cf card I would buy?
It should be. It's working fine for a lot of 5D3 users and that camera is much more demanding than the 50D. No guarantees though.No need to go wild with the bold tag btw.. and welcome :)
HDMI Monitoring works while recording RAW. Just tested it with my llilieput monitor.
(http://i.imgbox.com/abiU9Gch.jpg)
Fixed the frame skipping on my previous anamorphic video. The image sequences were imported as 25 fps and my project was 24 fps. Simple as that. Re-uploaded the correct file:
Quote from: menoc on May 29, 2013, 12:44:02 AM
HDMI Monitoring works while recording RAW. Just tested it with my llilieput monitor.
(http://i.imgbox.com/abiU9Gch.jpg)
Very nice @menoc :D raw and hdmi output, sweet :D
Quote from: menoc on May 29, 2013, 12:44:02 AM
HDMI Monitoring works while recording RAW. Just tested it with my llilieput monitor.
(http://i.imgbox.com/abiU9Gch.jpg)
Great News thanks for posting.. ;D
Quote from: JulianH on May 29, 2013, 12:50:49 AM
Fixed the frame skipping on my previous anamorphic video. The image sequences were imported as 25 fps and my project was 24 fps. Simple as that. Re-uploaded the correct file:
Fluid motion now..
Yeah i'm getting 1 to 2 stars now that i'm recording at 24p but recording stops around 2.5 - 3gigs and live view shuts down. the stars don't start to increase before it shuts down either.
all displays and global draw is off, this is happening with the same KomputerBay cards on my 5d2 as well. any recommendations on utilities for low level formatting? win7 won't do fat32 at 64gigs, i guess i could try linux or on mac disk utility?
thanks again everyone!
update: ok i just shot 4 gigs finally, it's not consistent. and another question, is it normal that after recording stops and live view shuts down, u have to reload the raw_rec module?
Sounds like you got back luck with the card.. :( can you benchmark it in a USB3 reader? return it for another one?
Another check: did you disable raw in the Canon menu's? Put the camera on jpg - that will give you the biggest buffer.
@JulianH Hey thanks very much for your reply. Sorry about all the questions, been way too excited researching this raw thing the past couple of nights and finally decided it's worth getting a 50d.
Quote from: menoc on May 29, 2013, 12:44:02 AM
HDMI Monitoring works while recording RAW. Just tested it with my llilieput monitor.
(http://i.imgbox.com/abiU9Gch.jpg)
I thought this would be the case but couldn't be sure without trying it so big thanks for proving it Menoc :)
This is actually big news! I will update the 1st page
@JulianH - Your updated footage looks great! It had to be something so simple LOL ;D
How many of you know that the 50d was actually the first camera to use the DIGIC 4 processor? http://cpn.canon-europe.com/content/education/infobank/capturing_the_image/digic_processing.do
have merged a set of edits to enable 50D to record raw video with today's commits 7183:8ba641e4a5ef
hoping to get more stability than i experienced with the build in Post#2 of this thread.
with that autoexec.bin and modules, i can hit 4GB limit, but have frequent crashes.
with the latest code, there are now many more resolution options combined with aspect ratio selection.
in tests with the latest unified code, i can get hundreds of frames at the 1592x896 (57 MB/s) on komputerbay 64G card
adjusting resolution down to less than 50 MB/s , 40 or even 30 and i'm still not hitting the 4GB limit -
seems to stop a little past 1400 frames the tests i've made and ML crashes the resulting files yield Error: This ain't a lv_rec RAW file
stopping recording before 1400 frames works at the moment and the raw files can be processed.
fun to be able to edit and install software on your camera.
in terms of code modifications, in modules/raw_rec/raw_rec.c
don't know the coding convention in magic lantern to handle the case of the 50D, where there is no audio, in module code - so just deleted the if (sound_rec == 1) sections since i was getting an undefined symbol on WAV_StartRecord
Quote from: GregoryOfManhattan on May 29, 2013, 06:32:05 AM
have merged a set of edits to enable 50D to record raw video with today's commits 7183:8ba641e4a5ef
hoping to get more stability than i experienced with the build in Post#2 of this thread.
with that autoexec.bin and modules, i can hit 4GB limit, but have frequent crashes.
with the latest code, there are now many more resolution options combined with aspect ratio selection.
in tests with the latest unified code, i can get hundreds of frames at the 1592x896 (57 MB/s) on komputerbay 64G card
adjusting resolution down to less than 50 MB/s , 40 or even 30 and i'm still not hitting the 4GB limit -
seems to stop a little past 1400 frames the tests i've made and ML crashes the resulting files yield Error: This ain't a lv_rec RAW file
stopping recording before 1400 frames works at the moment and the raw files can be processed.
fun to be able to edit and install software on your camera.
in terms of code modifications, in modules/raw_rec/raw_rec.c
don't know the coding convention in magic lantern to handle the case of the 50D, where there is no audio, in module code - so just deleted the if (sound_rec == 1) sections since i was getting an undefined symbol on WAV_StartRecord
How can we go about grabbing this?
Quote from: JulianH on May 29, 2013, 01:21:30 AM
Sounds like you got back luck with the card.. :( can you benchmark it in a USB3 reader? return it for another one?
Another check: did you disable raw in the Canon menu's? Put the camera on jpg - that will give you the biggest buffer.
yes thanks.
i read somewhere (not sure where now) how write performance improves, like the camera needs to warm up or something? seems to be the case, the first few shots when i start filming are all 3-4 stars and end within a few hundred frames. a few minutes later i turn it back on, format in camera and try again and its solid 1 star for 4 gigs. i dunno! i'll test my old Lexar 600X next:)
i benched with Crystal Disk Mark and got this:
komputerbay 64gig 1000x
CrystalDiskMark 3.0.2
Sequential Read : 140.503 MB/s
Sequential Write : 113.864 MB/s
Random Read 512KB : 63.013 MB/s
Random Write 512KB : 23.002 MB/s
Ok, call me ignorant. I've followed the 5D3 thread, and I've searched this thread. Why is the resolution limited to 1592 x 1062? I noted another user stating that the resolution is bumped down to this when trying to select 1920x1080. Also, why is the default fps at 30?
In terms of pixels a second:
1592x1062*30 = 50,721,120
1920x1080*24 = 49,766,400
In other words, in terms of bandwidth, 1080p @ 24 fps is "easier". Again, call me ignorant :)
Aside from that, congrats to the achievement.
The default FPS is 30, because that's what liveview works at. (Because it never had video, it never had a need to specify anything else for this)
However you can just leave FPS override turned on and leave it at 24.
Quote from: Roman on May 29, 2013, 10:30:01 AM
The default FPS is 30, because that's what liveview works at. (Because it never had video, it never had a need to specify anything else for this)
However you can just leave FPS override turned on and leave it at 24.
Makes sense :D
Quote from: menoc on May 29, 2013, 12:44:02 AM
HDMI Monitoring works while recording RAW. Just tested it with my llilieput monitor.
(http://i.imgbox.com/abiU9Gch.jpg)
Thanks for the test!
Is the 50D HDMI outputting 480p like the 5D2, 550D, 600D and 60D when recording? Or does it stay at 1080i when using the RAW recorder?
@KahL what i have is less stable than currently available.
I'm surprised about your stability issues with the build from the 2nd post Gregory. Ok, granted, I didn't shoot much long sequences, just tried the 4GB limit once, but recording is quite stable. When I shot the anamorphic video I made about 30 sequences in the course of one hour (each 10-20 seconds), without any complications.
If I try 5x or 10x zoom the camera crashes almost instantly. When do you experience problems?
Quote from: Digital Corpus on May 29, 2013, 09:49:35 AM
Ok, call me ignorant. I've followed the 5D3 thread, and I've searched this thread. Why is the resolution limited to 1592 x 1062? I noted another user stating that the resolution is bumped down to this when trying to select 1920x1080. Also, why is the default fps at 30?
In terms of pixels a second:
1592x1062*30 = 50,721,120
1920x1080*24 = 49,766,400
In other words, in terms of bandwidth, 1080p @ 24 fps is "easier". Again, call me ignorant :)
Aside from that, congrats to the achievement.
Unfortunately 1920x1080 14bit at 24fps is about 88 MB/s which may be more than the 50D and 5D2 could ever handle, in fact I don't think 1592x1062 at 30p even works (you have to framerate override to 24 and that requires about 71 MB/s which doesn't last long)
How big is the frame buffer on the 50D? I think I heard 60MB
The raw_rec buffer on the 50d (as all cameras that are recordings raw video) is split into 31mb chunks and is derived from shoot_malloc memory which in the 50d is 220MB. The early build for the 50d is not yet fine tuned and there is more buffer to be had which, in theory, means longer shooting times at larger frame sizes.
The CF controller is UDMA6 'compatible' which, again in theory, is capably of recording data up to 133MB/s. I doubt it will get anywhere close to this but I am pretty sure it can and will match the speed of the 5d2 as it has essential the same hardware controlling the CF card. 'UDMA6 Compatible' is an important phrase in this sense as we don't (yet) know the specifics of the controller chipset and what it's maximum transfer rate is.
The maximum recordable frame sizes are derived from the LV display feed that comes from the sensor. In normal shooting this is a maximum of 1592x1062 and in 1:1 crop (x5 zoom) this goes up to 1992x1080. When everything is tuned and the bugs are ironed out I believe we can achieve continual recording at maximum frame size (normal mode) and very close to it in crop mode. Restricting the frame size to specific aspect ratios reduces file sizes still further so my guess is that, on the right card, we can push the 50d to ITS maximums while the 5d2, having larger frame/file sizes may remain slightly under its maximums limited by hardware.
As it states in the first post of this topic "The raw video recording features on the 50d are still at a very early stage of development so don't expect everything to be working flawlessly." so just give it time to mature ;)
@Andy600 yes agree very early and experimental
@JulianH with the 2013May23 build - i'm getting crashes or lock ups on 3 out of 4 takes. the good news is that most of the .raw files can be processed. this is on a lexar 1000x 32G card - at various resolutions and resulting bit rates 1592x720, 1592x540, 1320x720
like your anamorphic video - do you reset the camera pull battery after every shot?
code notes on src/raw.c - posting these so the community can confirm values
@Smeangol - great job figuring this out, getting the values and adjusting the code to make it possible to try .raw on 50D
there are 6 conditionals for each camera type.
Smeangol has inserted values for 5 of these 6 - leaving out the QR_mode (only needed for playback i think).
the comment on the color matrix is "CONFIG_50D // not found yet"
are these values are correct ?
1. LiveView raw buffer address
same as 5D2
#if defined(CONFIG_5D2) || defined(CONFIG_50D)
#define RAW_LV_EDMAC 0xC0F04508
2. Photo-mode raw buffer address
same as 5D2
#define RAW_PHOTO_EDMAC 0xc0f04A08
3. Color matrix should be copied from DCRAW.
#ifdef CONFIG_50D // not found yet
//~{ "Canon EOS 50D", 0, 0x3d93,
//~{ 4920,616,-593,-6493,13964,2784,-1774,3178,7005 } },
#define CAM_COLORMATRIX1 \
4920, 10000, 616, 10000, -593, 10000, \
-6493, 10000, 12964, 10000, 2784, 10000, \
-1774, 10000, 3178, 10000, 7005, 10000
#endif
4. raw_update_params - adjust EDMAC RAW file sizes for each camera which have "unused areas, usually black"
#ifdef CONFIG_50D
skip_top = 22;
skip_left = 72;
skip_right = 0;
skip_bottom = 0;
#endif
5. (QR_MODE) // image review after taking pics- Raw buffer size for photos (using FFT to guess the period of the image stream.)
/* #if defined(CONFIG_50D) NEED Raw dump to get correct values
width = 5344;
height = 3516;
skip_left = 142;
skip_right = 0;
skip_top = 50;
#endif */
6. Dynamic range, from DxO
#ifdef CONFIG_50D
int dynamic_ranges[] = {1140, 1106, 1051, 965, 872, 772, 679};
#endif
Thanks Andy!
So if we have 220MBs and UDMA6 CF cards then what's the bottleneck currently preventing us from 88MB/s footage (14bit RAW 1080p24)? I assume it's the bandwidth of that 220MB memory buffer.
Anyone know how many of those 31MB chunks that 220MB buffer is currently passing per second? (I assume about 60MB/s worth)
@Andy600 What do you mean 'there's more buffer to be had' (size or speed?) and how do you know there's more; have the other cameras gone through fine tuning to improve their buffer that the 50D hasn't yet? (Aren't they all using the same "shoot memory buffer" and therefore limited to the specific size and speed of each camera's "shoot_malloc"?) I'm not trying to call you out on anything, just trying to figure out potential for the 50D (maybe look at how fast the 5D2 shoot memory is running)
Also in the 5x zoom mode, is it changing the field of view or is it still recording the same image but in 1992x1080?
Hey everyone, found out about ML yesterday from Engadget. Installed it last night on my 50D. LOVE IT!
But a quick question for you guys, as there is no audio, do you just buy a good audio recorder to sync up?
I'd like something that's somewhat lowprofile to mount on the 50D's hotshoe. Any suggestions?
What about?
Tascam DR-07mkII Portable Digital Audio Recorder
http://www.bhphotovideo.com/c/product/760375-REG/Tascam_DR_07MKII_DR_07mkII_Portable_Digital_Audio.html
(http://static.bhphoto.com/images/images345x345/760375.jpg)
and:
Revo Hot Shoe to 1/4"-20 Male Post Adapter
http://www.bhphotovideo.com/c/product/860269-REG/Revo_sa_cs_14m_Hot_Shoe_to_1_4.html
(http://static.bhphoto.com/images/images150x150/860269.jpg)
Is that typically what you guys are doing? Any way to have recording start and stop at the same time as video recording?
Thanks.
Quote from: P337 on May 29, 2013, 04:02:44 PM
Thanks Andy!
So if we have 220MBs and UDMA6 CF cards then what's the bottleneck currently preventing us from 88MB/s footage (14bit RAW 1080p24)? I assume it's the bandwidth of that 220MB memory buffer.
Anyone know how many of those 31MB chunks that 220MB buffer is currently passing per second? (I assume about 60MB/s worth)
@Andy600 What do you mean 'there's more buffer to be had' (size or speed?) and how do you know there's more; have the other cameras gone through fine tuning to improve their buffer that the 50D hasn't yet? (Aren't they all using the same "shoot memory buffer" and therefore limited to the specific size and speed of each camera's "shoot_malloc"?) I'm not trying to call you out on anything, just trying to figure out potential for the 50D (maybe look at how fast the 5D2 shoot memory is running)
Also in the 5x zoom mode, is it changing the field of view or is it still recording the same image but in 1992x1080?
By 'more buffer to be had' I mean that the 50d port is still missing a few ML features and some of the features it has can be refined further. 1% demonstrated this with his Tragic lantern ports for the 600d. The 50d currently shows 4 buffer stars = @120MB so I think there is more. The bigger the buffer allocation = the more time you can record at larger frame sizes BUT it then needs to be written to the card and that is where the bottleneck is. I think this bottleneck (although hardware) is, I believe also being restricted in software atm and might be better calculated better to allow faster card writing.
5x zoom will do exactly what it sounds like. The field of view recorded will be zoomed and exactly what you see in LV. The actual recorded area is denoted by the white box. At 1992x1080 the white box covers the whole sensor.
The 50d runs the unified build of Magic Lantern with module support added by @Smeangol (i.e. raw rec) but there is a lot of 50d specific adjustments that can be made to improve it.
The 600d did not have sraw and mraw but 1% enabled those features and 600d. The 50d currently needs to be in jpeg mode for raw video recording but has sraw. I'm not sure if using those settings will improve things when the code is worked on. Who knows?
@Smeangol has done some amazing work so far. He was also responsible (with help from A1ex) for adding 1080p video when the camera had no video capability but he has very limited time to devote to the project ATM. We are hoping to have 1% onboard soon but need to get him a 50d to work on ;)
Quote from: Thai on May 29, 2013, 04:27:11 PM
Hey everyone, found out about ML yesterday from Engadget. Installed it last night on my 50D. LOVE IT!
But a quick question for you guys, as there is no audio, do you just buy a good audio recorder to sync up?
I'd like something that's somewhat lowprofile to mount on the 50D's hotshoe. Any suggestions?
Thanks.
Check out the latest RODE video mics with built-in recording. You can also output to a HDMI monitor and feed the monitor signal to an external recorder (one with with sound recording capability, inputs a mic etc) to get a proxy video (in whatever format the recorder uses) with sound. This will help with sync. If you just want sound recording you'll need to go old skool and use a clapper board. The 50d can't record the audio itself but it will show the clapper strike as a visual cue for audio syncing.
Just saw your updated post: The Tascam will work great. You will need to start audio recording before hitting video record. You can't currently control recording stop/start on an external device with the 50d.
Quote from: GregoryOfManhattan on May 29, 2013, 03:42:39 PM
like your anamorphic video - do you reset the camera pull battery after every shot?
I basically left the camera on for about an hour while walking around taking the shots from time to time. No problems whatsoever. Switched it off sometimes, then I have to reload raw rec and put it on the right settings again. But I never had raw files that were not readable. Sometimes when I'm experimenting at home the camera won't power up and I have to pull out the battery first and put it back in. But overall, for a 'very experimental early build', this has worked pretty well for me :)
@Andy: great ideas on the hdmi+audio. If anamorphic live view is possible, I will get a cheap external LCD and still be able to get a corrected anamorphic fov... that would be great as lcd's with anamorphic options are pretty expensive.
Just read a couple of tech blogs (there are dozens now) that have picked up on the 50d's new trick and most are getting it completely wrong so for any bloggers reading this without reading the front page:-
1) The 50d did not have any video modes when shipped.
2) Magic Lantern enabled compressed H.264 1080p at 30fps over a year ago. This is NOT the news ;)
3) The new 'raw video' ability captures 14bit uncompressed data from the sensor and writes this as a .raw file to a CF card. THIS is the news :D
Quote from: blackroom on May 29, 2013, 08:31:38 AM
yes thanks.
i read somewhere (not sure where now) how write performance improves, like the camera needs to warm up or something? seems to be the case, the first few shots when i start filming are all 3-4 stars and end within a few hundred frames. a few minutes later i turn it back on, format in camera and try again and its solid 1 star for 4 gigs. i dunno! i'll test my old Lexar 600X next:)
i benched with Crystal Disk Mark and got this:
komputerbay 64gig 1000x
CrystalDiskMark 3.0.2
Sequential Read : 140.503 MB/s
Sequential Write : 113.864 MB/s
Random Read 512KB : 63.013 MB/s
Random Write 512KB : 23.002 MB/s
Thanks for reporting back, great findings now gotta let the camera warm-up and card I guess where you shooting @ 1592 x 720?
Quote from: Andy600 on May 29, 2013, 05:12:37 PM
Just read a couple of tech blogs (there are dozens now) that have picked up on the 50d's new trick and most are getting it completely wrong so for any bloggers reading this without reading the front page:-
1) The 50d did not have any video modes when shipped.
2) Magic Lantern enabled compressed H.264 1080p at 30fps over a year ago. This is NOT the news ;)
3) The new 'raw video' ability captures 14bit uncompressed data from the sensor and writes this as a .raw file to a CF card. THIS is the news :D
Say it like it is Andy, let them know... 50D no video + M.L = Raw 14bit recording incredible
What I don't get is how come some people are having problems with their 50D's crashing and other ok from the same build. Does it have to do with the way you load ML on CF cards, or is it a something missing in the folders. Don't have my 50D yet it's on his way, just trying to get a ball park answer so when I get mines it can run as smooth as @Julian.H's 50D. @Andy600 hope you get that card soon man so you can start testing.
had a chance to test a little bit more the unified merge build and see that it records well up to around 1437 frame - 60 seconds.
this merged code can record with graphics overlay enabled at a wide variety of bit rates, just crashes if recording goes past 60 seconds.
the interface is different now and to record,
-live view on
-modules enable raw_rec
-frame rate 24
-Raw Rec - turn off sound adjust width and aspect ratio as desired
- hit live view
- half press shutter to start a regular video (may not be required)
-stop regular video
- now hit live view again to record raw
- turn off before frame 1437 or the camera crashes.
http://pic.twitter.com/rrxmC8OupA
6 buffer stars :) ::)
@GregoryOfManhattan - Did you try crop mode (5x zoom)?
Quote from: JulianH on May 29, 2013, 01:48:07 PM
If I try 5x or 10x zoom the camera crashes almost instantly. When do you experience problems?
That happens also in the 550d. When i tried the 10x zoom the camera crashes.
i found a trick: I zoom 5x, push the menu button twice, then the camera goes to liveview again
Quote from: GregoryOfManhattan on May 29, 2013, 07:29:11 PM
had a chance to test a little bit more the unified merge build and see that it records well up to around 1437 frame - 60 seconds.
this merged code can record with graphics overlay enabled at a wide variety of bit rates, just crashes if recording goes past 60 seconds.
the interface is different now and to record,
-live view on
-modules enable raw_rec
-frame rate 24
-Raw Rec - turn off sound adjust width and aspect ratio as desired
- hit live view
- half press shutter to start a regular video (may not be required)
-stop regular video
- now hit live view again to record raw
- turn off before frame 1437 or the camera crashes.
http://pic.twitter.com/rrxmC8OupA
Great findings.. so that means without the graphic overlay's it should record flawlessly than. Also this unified build you talking about download link is on the first page right?
Quote from: Andy600 on May 29, 2013, 07:33:38 PM
6 buffer stars :) ::)
@GregoryOfManhattan - Did you try crop mode (5x zoom)?
Andy your right it has 6 Stars (*.....) What happened there 2 more stars added in this new build?
Quote from: goldenchild9to5 on May 29, 2013, 07:54:57 PM
Great findings.. so that means without the graphic overlay's it should record flawlessly than. Also this unified build you talking about download link is on the first page right?
You're making conclusions a bit too fast here ;) The built by Gregory is custom, but another modification than the one that is on the first page here.
Things are looking good though and it sure looks like the 50D has more headroom then what's possible right now. Don't rush things. I'm sure it should be possible to get it up and running as smooth as it has been for me, with the right card. CF cards seem to be a bit of a guess. Not all cards (even same manufacturer and specifications) are equal.
I understand still early, is Gregory part of the ML coding team?
Quote from: JulianH on May 29, 2013, 08:01:24 PM
....CF cards seem to be a bit of a guess. Not all cards (even same manufacturer and specifications) are equal.
I wouldn't know about such things thanks to the local post office >:( I'm sure it would be faster for me to just make one LOL
/Edit: forget what I wrote here.. premature conclusions, have to check how/if the footage actually works.
@JulianH if footage is looking good, we will need a few more 50D testers to review build.
Quote from: GregoryOfManhattan on May 29, 2013, 10:08:39 PM
@JulianH if footage is looking good, we will need a few more 50D testers to review build.
It's looking very promising Gregory, many thanks for the build :) Looking at the files now, I will let you all know soon, everybody is eager, I know ;)
if there are other alpha testers interested and standing by with 50D and fast cards, please PM me and i'll arrange to send you a build.
I have a 50d on its way from south korea. It's going to be a long wait (2/3 weeks).
When i'll have it in hands i will of course test new build
Quote from: P337 on May 29, 2013, 12:47:11 PM
Thanks for the test!
Is the 50D HDMI outputting 480p like the 5D2, 550D, 600D and 60D when recording? Or does it stay at 1080i when using the RAW recorder?
Recording to H.264 automatically switches HDMI output to 480p but RAW recording DOES NOT - it stays at 1080i. Keep in mind though that the 50D right now does not output the sensor data at 16:9. You will instead get a 4:3 image in the middle with black bars on the side. Depending on the monitor you have, you may have a function to crop the output to 16:9.
(http://i.imgbox.com/adpyNOAY.jpg)
New resolution test with GregoryOfManhattan's build, using Hacked mode.
Sandisk 32GB 90MB/s CF
3:2 @ 1592x1062 ~ 135 frames
5:3 @ 1952x955 ~ 270 frames
16:9 @ 1592x 895 ~ 480 frames
1.85:1 @ 1592x860 ~ 850 frames
2:1 @ 1592x796 - No skipping!
It can record over 4GB and span! I shot 1592x796 continously, stopped recording manually at 10GB. The buffer is completely fine. But right now the files don't convert properly so it's not usable yet!
Wanted to try anamorphic resolutions like 1440x1062 and 1320x990 but ran out of batteries...
Overall definitely an improvement over the previous build, that gave me these results:
1592×1062 – frame skipping after about 50 frames
1592×840 – frame skipping after about 480 frames
1592×720 – no frame skipping
My quick observations using GregoryOfManhattan's Alpha build:
- Better speed, stable 1592x796 recording (see test above)
- Playback works (B&W, slow speed)
- Buffer improved to 5 stars from 4 stars on my camera
- Way more available resolutions, select width and choose aspect ratio
- 'Digital dolly' mode works!
- Recording with live view button, I don't have to do any kind of work around
- Cropped mode works - display still turns pink but DNG files are fine!
- 4GB+ recording works but the raw files aren't converted properly yet - not usable yet, work in progress
- recording rectable / frame counter is flickering all the time (same as previous build)
- Camera crashes when trying to play back raw files made in cropped mode
I can't recreate the crashes he mentions.
I do not have a 50D to do tests, so I do not know if this resolution is already enabled:
1440 x 810 (16:9) is 49MB/s so probably it would be the maximum resolution for 16:9 in 50D
1360 x 768 is also a good option for 16:9
Quote from: apefos on May 29, 2013, 11:33:46 PM
I do not have a 50D to do tests, so I do not know if this resolution is already enabled:
1440 x 810 (16:9) is 49MB/s so probably it would be the maximum resolution for 16:9 in 50D
1360 x 768 is also a good option for 16:9
No need to crop so much. The 50d is fine at 1592 width ;)
Quote from: Andy600 on May 29, 2013, 11:44:58 PM
No need to crop so much. The 50d is fine at 1592 width ;)
1592 Res is fine for me as well..
I am so lucky ;D: just bought an almost mint 50d for 340 euro including 3 original batteries and original grip. I already have a 64gb 1000x compact flash and some nice m42 takumar lenses so let the fun begin :P
Those advances with Gregory's build are extremely promising, still waiting for my 50D.. When I get it it's on.
Julian - Your 2.5k upscaled still test is pretty impressive. Easily outresolves H.264 1080p. Nice! 8) We'll need a BMCC vs 50d test soon hehe (yes, I know the BMCC will beat it but by how much?)
...for those that haven't seen it: http://www2.picturepush.com/photo/a/13184955/img/13184955.png
Quote from: savale on May 29, 2013, 11:58:43 PM
I am so lucky ;D: just bought an almost mint 50d for 340 euro including 3 original batteries and original grip. I already have a 64gb 1000x compact flash and some nice m42 takumar lenses so let the fun begin :P
Nice.. Welcome to the club. What brand of card do you have?
Quote from: Andy600 on May 30, 2013, 12:03:37 AM
Julian - Your 2.5k upscaled still test is pretty impressive. Easily outresolves H.264 1080p. Nice! 8) We'll need a BMCC vs 50d test soon hehe (yes, I know the BMCC will beat it but by how much?)
...for those that haven't seen it: http://www2.picturepush.com/photo/a/13184955/img/13184955.png
Wow!!! that is impressive.. love that log look.
I still think the Panasonic GH2/G6 will beat the 50D for detail ;) Have to do that test soon... Dynamic range / noise is another thing.
Got some juice in my battery, did some more speed tests on resolutions that will be appreciated by anamorphic shooters (like me ;)).
1440x1062 ~ 250 frames
1440x960 ~ 370 frames
1440x864 and lower heights without frame skipping at all
1320x1062 - This is an interesting one, ran it several times and results vary wildly, between 250 and 650 frames!
1320x990 - No frame skipping
This will be my new shooting mode of choice on the 50D for 2x anamorphic. It will output 2640x990 (2.66:1) after desqueezing.
1280x1064 - Looks like it's running without problems, but stopped around the 4GB mark. Might have to test more.
5:4 is pretty cool for 2x anamorphic too, gets you 2560x1064 = 2.40:1
Lower resolution variations like 1280x960 and 1320x880 work fine.
Quote from: GregoryOfManhattan on May 29, 2013, 10:21:58 PM
if there are other alpha testers interested and standing by with 50D and fast cards, please PM me and i'll arrange to send you a build.
I've got both. How do I get the build you created?
Thanks in advance, Alex
The upscale I did had no sharpening applied either. I'd imagine NeatVideo's sharpening would really enhance the footage.
As far as the log look, it's a must for flexible color. I essentially pulled all of the sliders involving shadow, blacks, highlights, and whites as far out as I could. Saturation reduced as well and exposure brought down to pull the sky back. Grades nicely as well.
Here's the 4k ProRes 4444 of JulianH's footage to play with. Have a go in DaVinci and see the latitude. Way worth the sacrificed resolution.
http://www.qfpost.com/file/d?g=QxEkiKUg1
Quote from: artiswar on May 30, 2013, 12:57:25 AM
The upscale I did had no sharpening applied either. I'd imagine NeatVideo's sharpening would really enhance the footage.
As far as the log look, it's a must for flexible color. I essentially pulled all of the sliders involving shadow, blacks, highlights, and whites as far out as I could. Saturation reduced as well and exposure brought down to pull the sky back. Grades nicely as well.
Yeah you right with a little sharpening from NeatVideo you would be all set. Your using (ACR) Right.. that's what I've been doing also with the DNG's for that log look than convert to ProRes 4444, but I don't think I would mess around with the exposure if it's already exposed correctly all depends on the shot. What do instead I would slide the Highlight recovery until the sky has more detail and Voila.
Quote from: goldenchild9to5 on May 30, 2013, 01:20:30 AM
Yeah you right with a little sharpening from NeatVideo you would be all set. Your using (ACR) Right.. that's what I've been doing also with the DNG's for that log look than convert to ProRes 4444, but I don't think I would mess around with the exposure if it's already exposed correctly all depends on the shot. What do instead I would slide the Highlight recovery until the sky has more detail and Voila.
Precisely. The sky here was a bit hot so highlight recovery did quite a bit. I wanted just a bit more detail from the sky so I pulled the exposure down a bit. I can't believe I'm looking at DSLR footage with this much DR
Quote from: artiswar on May 30, 2013, 01:03:39 AM
Here's the 4k ProRes 4444 of JulianH's footage to play with. Have a go in DaVinci and see the latitude. Way worth the sacrificed resolution.
http://www.qfpost.com/file/d?g=QxEkiKUg1
Thanks for posting artiswar. The saturation slider how far back did you slide it? (-20)
Quote from: goldenchild9to5 on May 30, 2013, 01:25:48 AM
Thanks for posting artiswar. The saturation slider how far back did you slide it? (-20)
I'm sitting at about -20. -40 is pretty extreme but everything still comes back. Splitting the difference at -30 would be pretty nice.
Additionally, 50D on its way to me. I'll be testing some Zeiss glass to see if that helps with resolution.
Quote from: artiswar on May 30, 2013, 01:23:24 AM
Precisely. The sky here was a bit hot so highlight recovery did quite a bit. I wanted just a bit more detail from the sky so I pulled the exposure down a bit. I can't believe I'm looking at DSLR footage with this much DR
Right on looking at the footage you make a lot of sense, pull it back for some more detail. I can't believe how much DR that camera has, you can pull the sky right back no problem. Now we can really get creative, and have fun with our grades without worrying about extract noise / Codec breakdowns. It might have a little less sharpness than the GH2, or G6 but at the end I like that softer image it's looks very filmic. I have a question you up-res the footage in after effects right.. What dimension did you plug in (4... x 2...)
Quote from: artiswar on May 30, 2013, 01:31:34 AM
Additionally, 50D on its way to me. I'll be testing some Zeiss glass to see if that helps with resolution.
Same here waiting on mines, yeah Zeiss glasses would definitely help. But to me the images are lovely the way they are, with a nice grade it will pop, and the edges will be roll-off, and soft.
Quote from: goldenchild9to5 on May 30, 2013, 01:33:41 AM
Right on looking at the footage you make a lot of sense, pull it back for some more detail. I can't believe how much DR that camera has, you can pull the sky right back no problem. Now we can really get creative, and have fun with our grades without worrying about extract noise / Codec breakdowns. It might have a little less sharpness than the GH2, or G6 but at the end I like that softer image it's looks very filmic. I have a question you up-res the footage in after effects right.. What dimension did you plug in (4... x 2...)
I was a die hard anti-Canon, GH2 fanboy. Now, having lost my GH2 body, this is a perfect place to start playing. To me, color rendition matters entirely more than sharpness, especially for web delivery.
My workflow was as follows:
1. Process the DNG files through Camera Raw in PS, save the individual files to .tifs.
2. Open Quicktime Pro 7 (insanely useful application), Select "Open as Image Sequence" from the File drop down menu.
3. Export as ProRes 4444 at 4k resolution.
Having worked DI on sets a couple times, I would be interested in creating an Automator app on Mac that creates a folder structure as follows
Master folder for shot
Subfolders labeled "RAW", "DNG", and "TIF"
Have automator run RAW2DNG for each .raw file and have it render the DNGs to each subfolder.
Then manually process each shot through Camera Raw, rendering to 4444s which would sit inside the shot's master folder.
Gorgeous progress on the 50D.
I'm getting continuous 1592x840 filming at 24fps, for a clean 1920 horiz px upscale. Needless to say, send me over the latest builds when they're all set :-D
Untouched.
(http://farm6.staticflickr.com/5321/8884511848_e82996edf3_o.jpg)
Graded and Textured.
(http://farm6.staticflickr.com/5337/8884511682_b5975c0012_o.jpg)
What's with the small 3px black line on all of the 50D stuff I've seen?
Oooh shoot your the one who made a post about your GH2 being stolen on Personal-View right? Myself I'm all about the GH2 had a canon before sold it than got my first GH2 now own two. You right DR, and Color Depth is more important imagine what we can achieve now with a software as powerfull as davinci resolve my head spinning. Someone will create that software you talking about soon, cause a lot of professionals will be using those hacked canons on projects.
Quote from: artiswar on May 30, 2013, 01:51:00 AM
What's with the small 3px black line on all of the 50D stuff I've seen?
Black pixels. They'll get fixed.
Where can we download the raw hack?
Quote from: artiswar on May 30, 2013, 01:43:22 AM
I was a die hard anti-Canon, GH2 fanboy. Now, having lost my GH2 body, this is a perfect place to start playing. To me, color rendition matters entirely more than sharpness, especially for web delivery.
My workflow was as follows:
1. Process the DNG files through Camera Raw in PS, save the individual files to .tifs.
2. Open Quicktime Pro 7 (insanely useful application), Select "Open as Image Sequence" from the File drop down menu.
3. Export as ProRes 4444 at 4k resolution.
Having worked DI on sets a couple times, I would be interested in creating an Automator app on Mac that creates a folder structure as follows
Master folder for shot
Subfolders labeled "RAW", "DNG", and "TIF"
Have automator run RAW2DNG for each .raw file and have it render the DNGs to each subfolder.
Then manually process each shot through Camera Raw, rendering to 4444s which would sit inside the shot's master folder.
It's doable but you'll probably have to do some AppleScript with it.
Quote from: KahL on May 30, 2013, 01:49:05 AM
Gorgeous progress on the 50D.
I'm getting continuous 1592x840 filming at 24fps, for a clean 1920 horiz px upscale. Needless to say, send me over the latest builds when they're all set :-D
Graded and Textured.
(http://farm6.staticflickr.com/5337/8884511682_b5975c0012_o.jpg)
First off, Hello everyone! Just registered, I was able to snatch a 50D on ebay for relatively cheap, it's coming in tomorrow and my CF card is coming friday, I'm eager to help out with any testing or workflow solutions.
Secondly, wow, this is great. A little soft as it's not native 1080 but yet the detail kicks the hell out of H.264 to my eyes. Would you mind sharing which card you're using?
Where can we download the raw hack?
User GregoryOfManhattan has asked that those willing to test the newest builds PM him.
@CaptainOfObvious and @LukeJflowers current released build is Post #2 of this thread -
http://www.magiclantern.fm/forum/index.php?topic=5586.msg39086#msg39086
working toward another release.
http://vimeo.com/67268599
Grading test.
Quote from: GregoryOfManhattan on May 30, 2013, 05:46:40 AM
@CaptainOfObvious and @LukeJflowers current released build is Post #2 of this thread -
http://www.magiclantern.fm/forum/index.php?topic=5586.msg39086#msg39086
working toward another release.
Thanks, look forward to the next one.
A little video on the HDMI Monitoring . . .
Quote from: goldenchild9to5 on May 30, 2013, 12:06:17 AM
Nice.. Welcome to the club. What brand of card do you have?
Thank you! I have a komputerbay 1000x 64gb.
Quote from: artiswar on May 30, 2013, 06:54:07 AM
http://vimeo.com/67268599
Grading test.
I did a similar grade - great minds think alike! No sharpening on mine though - I think it has a smoother look without.
(http://brightideasmedia.co.uk/wp-content/themes/storage/fourktest-1st%20grade.jpg)
Nice :) Are you guys interested in more DNG footage from the 50D?
I'm planning on shooting something more this evening, would be nice to see your grades on it! I'll upload some DNG sequences. Going to shoot in 16:9 @ 1592x 896, this gives me about 480 frames, or 20 seconds.
Also will do a test with a Nikkor 80-400mm VR II in 10x cropped mode.. ;D I can get 320 frames at 1600x900 :)
What is the actual crop factor in 10x zoom?
Well, i would be interested at some dng footage.
I realy love the fact (psychologic i'm sure it is) that i can grade in lightroom instead of vegas
More DNG's as much as you can!
I'm trying to find the best way to work with these files. What is everyone doing for noise & moire? Neat video? Lightroom?
I want to regrade this to get a cleaner look.
Quote from: AnotherTim on May 30, 2013, 01:07:51 PM
More DNG's as much as you can!
I'm trying to find the best way to work with these files. What is everyone doing for noise & moire? Neat video? Lightroom?
I want to regrade this to get a cleaner look.
Lightroom will do the job, but neat video is also really good. But I see some strange thing in your video:
1) Are these a few loops?
2) I see flickering... But this might have to do with issue 1.
Probably because of the loops. Beware when editing in ACR or Lightroom, it can cause flickering when you use the shadows/highlight recovery sliders. If you switch to process version 2010 that's solved, but you don't have the same controls.
will upload a big pack of dng's tonight.
Quote from: JulianH on May 30, 2013, 01:43:36 PM
Probably because of the loops. Beware when editing in ACR or Lightroom, it can cause flickering when you use the shadows/highlight recovery sliders. If you switch to process version 2010 that's solved, but you don't have the same controls.
will upload a big pack of dng's tonight.
Good tip! Thx :)
Quote from: savale on May 30, 2013, 01:33:31 PM
Lightroom will do the job, but neat video is also really good. But I see some strange thing in your video:
1) Are these a few loops?
2) I see flickering... But this might have to do with issue 1.
Yes. I looped it since the clip was quite short. I think the flickering is to do with a brighter part of the sky looping in & out of frame.
Compression seems to be hiding some of the issues, my original export has far more moire. For me that will be the last piece of the puzzle.
BTW i don't have lightroom (got my eye on creative cloud though). I used color finesse in AE, exported to DNxHD for viewing & compressed to H.264 720p for vimeo.
I've been trying to simultaneously buy a 50d & work out the worst case scenario (which at the time was raw being unusable for some reason).
Can anyone tell me their first hand experience of working with 50d H.264 footage from the latest stable version? Is it exactly the same as rebel H.264 footage.
I'll probably use this as a B-cam more often than for raw video. Is there anything i need to know.
Quote from: JulianH on May 30, 2013, 01:43:36 PM
Beware when editing in ACR or Lightroom, it can cause flickering when you use the shadows/highlight recovery sliders.
Even if you copy/paste the exact same settings to all of the dng's?
I can imagine the algorithm decides to do something with highlight recovery / black levels depending on the situation. If there is some sort of flickering this might be emphasized by the algorithm...
I have a question regarding the h264 VIDEO of the 50D (not raw frames). In the Canon menu, I have "Exposure Simulation" clicked to "on" to eliminate the auto-exposure in Live View. However when I try to record the video, it automatically jumps BACK to auto exposure, which immediately ceases once I stop recording. I'm sure it's because I'm late to the 50D party but, how can I fix this issue?
Quote from: KahL on May 30, 2013, 03:28:03 PM
I have a question regarding the h264 VIDEO of the 50D (not raw frames). In the Canon menu, I have "Exposure Simulation" clicked to "on" to eliminate the auto-exposure in Live View. However when I try to record the video, it automatically jumps BACK to auto exposure, which immediately ceases once I stop recording. I'm sure it's because I'm late to the 50D party but, how can I fix this issue?
Set the camera to "Manual (M)" mode and set "Exposure Overwrite" to ON in ML menus.
Quote from: menoc on May 30, 2013, 04:59:13 PM
Set the camera to "Manual (M)" mode and set "Exposure Overwrite" to ON in ML menus.
D'oh!
Well'p that helped. Thanks man :)
Anyone else using a RPP workflow? To be more specific I'm doing:
Raw2dng ->RPP w/ Blur chroma, Auto WB and 5 Sharpening (to 16bit Tiff) ->MpegStreamClip (to ProRes444). Pretty happy with the results, but RPP's interface leaves a lot to be learned.
I'd love more DNGs. As far as flickering, it seems to be from the looping. I'll have cam in hand tomorrow so I'll get some tests up as well.
I don't know too much about this but would it be possible to capture in 12-bit raw instead of 14-bit (I think this is right) that is currently being recorded? That way you should be able to capture higher res with less buffer usage, and maybe make 1920 a captureable res without dropping frames.
has anyone been able to process spanned .raw .r01 .r0... files generated on the 50D?
I'm going out now to shoot. Will make a nice collection of DNG's to play with. Have a nice idea to make a grading collaboration video to show off 'the power of raw' as well :)
@Gregory: How should I process the spanned files with raw2dng? just drag and drop like other files? I thought I read somewhere I should do something else, but can't find it...
50D party may be over - merging with the latest unified, builds are not producing spanned raw files which can be processed with the latest 04a39e3 modules/raw_rec/raw2dng
getting the Error: This ain't a lv_rec RAW file
How were spanned files from the MKII being processed? I find it hard to believe there isn't a work around.
@JulianH - cut before span - no shots longer 4G
latest raw2dng is supposed to be able to start from the first .RAW and continue through .R01, ...
not working with 50D files.
(also tried making a 16G cat of all of the .R files - that didn't work either.)
not sure that this is a "bug" we can report as 50D raw is not supported.
looks like something is slightly off for the 50D when the span happens.
you can get pink noise version of your images if you raw2dng the last .R0_ file
you may be able to recover the first file with the footer fix.
safest for now to not shoot longer than 4G
Gregory, have you tried this (what you describe as merging?):
http://www.magiclantern.fm/forum/index.php?topic=5655.msg41045#msg41045
New 50D video posted on vimeo
referring to a code merge with current code from the unified branch
hg merge unified
building and using the very latest raw2dng
$./magiclantern/magic-lantern/modules/raw_rec/raw2dng /Volumes/EOS_DIGITAL/DCIM/100CANON/M30-1055.RAW
Error: This ain't a lv_rec RAW file
did try the "cat" command to join the raws - but this should not be required with the current raw2dng
will need more time and help from others to resolve the file spanning.
Quote from: GregoryOfManhattan on May 30, 2013, 07:53:01 PM
referring to a code merge with current code from the unified branch
hg merge unified
building and using the very latest raw2dng
$./magiclantern/magic-lantern/modules/raw_rec/raw2dng /Volumes/EOS_DIGITAL/DCIM/100CANON/M30-1055.RAW
Error: This ain't a lv_rec RAW file
did try the "cat" command to join the raws - but this should not be required with the current raw2dng
will need more time and help from others to resolve the file spanning.
Thank you for all your work & efforts to try getting the 50D unified, and file spanning.
Quote from: GregoryOfManhattan on May 30, 2013, 07:19:45 PM
has anyone been able to process spanned .raw .r01 .r0... files generated on the 50D?
I'd be glad to test the new build. I sent you a PM with my email.
Gregory, if I can get a hold of those .raws I'd be glad to start working on it. SoShareIt should be able to handle those sizes.
I have raw working fine on the 5DMiii - but I'm new to the 50D and probably making a naive mistake in the setup.
1. I have the regular 50D ML setup right on the 50D
2. I used the 'autoexec.bin' file for the 50D, from one of the first posts in this thread, to replace the autoexec file that was in the regular ML setup.
3. I copied the MODULES folder from the link in that same 50D post near the top of this thread.
I get a message along the lines of 'Scripts folder missing', but I can load the modules and the raw menu items work in the 50D
BUT - even when shooting at, say, 1280 x 720, using a 1000x Komputerbay 64GB card, data rate peaks at about 20Mbits/sec and frame skipping happens in about 10 seconds. I'm sure I've screwed something up. I don't mind learning on my own and waiting a while to get things working - but I'd appreciate any tips that you might offer.
Quote from: GregoryOfManhattan on May 30, 2013, 07:26:34 PM
50D party may be over - merging with the latest unified, builds are not producing spanned raw files which can be processed with the latest 04a39e3 modules/raw_rec/raw2dng
getting the Error: This ain't a lv_rec RAW file
Hello guys, I have just been reading this forum since a few days and I am astonished with all the work you have done and the results you are getting with this camera.......I just got a 50d yesterday and I should be receiving it in a few days.
My congrats to Gregory, Andy, Julian and the rest for all the time and efford they are putting in this task.......and I hope the party is not over yet....I am still dreaming with 2K RAW on the 50d......
Quote from: hijodeibn on May 30, 2013, 09:27:24 PMI am still dreaming with 2K RAW on the 50d
Well, stop dreaming. 2K is impossible.
Not because the write speed is to low but because the 50D's maximal resolution is 1592 X 1062 (Without crops). You can't get 20 Megapixel from a 12 Megapixel sensor and you can't get 2K from a 1592 X 1062 LiveView image.
But higher framerates than 24 frames per second might be possible in the future.
hello quys
i am strugelin withe the latest build on my 550d reachin 1280*480 19fps....
now..what you think will it be possible to get a horizontel of 1920 or near that on the 50d in the future.
otherwise i will safe my money for a 5dm3;-)
2k (or 3k or 4k) refers to the horizontal resolution of the image, not the overall pixel count. The sensor on the 50d is over 4k wide. Is it the live view buffer you're talking about?
I'm really looking forward to someone giving the 40d a good go as it's sensor is lower res but still over 3k wide (and i've got one).
The live view in full sensor mode is restricted to 1592 wide. In cropped mode it's wider, maximum 1992. As far as I understand there is no way it's resolutions are going to get any wider than that.
Don't worry, I know what 2K is. And I am very sure that it is not possible for the 50D to record 2K raw videos at any frame rate.
The actual resolution of the 50D's sensor may be 4752 X 3168 (15 Megapixel) but Canon doesn't read the full sensor and downscale it to every resolution we want but simply skips columns and lines to get the LiveView image.
And that's what Magic Lantern's raw video is: The LiveView image.
Since something like 2048 X 1152 (16:9) 14-bit raw video at 24 frames per second would require 95 Megabyte/s write speed, the write speed is not the biggest issue. But I doubt that there's a way to increase the LiveView image's resolution without replacing the Canon Firmware ...
@julian
that will be the neckbrackin problem....
we will see what the future brings;-)
the raw.rec module is a nice plaything at at the moment but nothing else!! exept the 5dm3
Why is that a neckbreaking problem. It's not all about resolution. Compare 1920x1080p standard h264 footage to 1592x864 50D raw... guess what I prefer?
please post links to color issues in raw recordings - DNGs and jpgs.
are zoom mode recordings looking different?
or if it all looks good, let us know.
Quote from: menoc on May 30, 2013, 08:12:02 PM
I'd be glad to test the new build. I sent you a PM with my email.
:P . . Well, silly me . . . it was in my junk folder all this time! Darn Microsoft, they throw away the things you want, and send you the things you don't!
Major props go to GregoryOfManhattan for the prompt response . . . and to the entire ML Dev team for all the help. Much appreciated!!
Quote from: GregoryOfManhattan on May 30, 2013, 11:15:29 PM
please post links to color issues in raw recordings - DNGs and jpgs.
are zoom mode recordings looking different?
or if it all looks good, let us know.
Normal mode colors are fine (working on footage now, will make a lot of DNG's available)
In 5x zoom mode colors are weird (lot of green in the shadows), impossible to correct in ACR properly I think.
(http://www.eoshd.com/comments/uploads/gallery/album_64/med_gallery_20742_64_109957.jpg)
Quote from: KahL on May 30, 2013, 05:59:35 PM
D'oh!
Well'p that helped. Thanks man :)
;D Gladly . . .
Quote from: JulianH on May 30, 2013, 11:30:14 PM
Normal mode colors are fine (working on footage now, will make a lot of DNG's available)
In 5x zoom mode colors are weird (lot of green in the shadows), impossible to correct in ACR properly I think.
(http://www.eoshd.com/comments/uploads/gallery/album_64/med_gallery_20742_64_109957.jpg)
The halos aren't cool but the green kind of gives it a filmic look . . . I kind of like it!
But play around with it in ACR. It may need some work to get rid of the greens though.
Quote from: JulianH on May 30, 2013, 11:30:14 PM
Normal mode colors are fine (working on footage now, will make a lot of DNG's available)
In 5x zoom mode colors are weird (lot of green in the shadows), impossible to correct in ACR properly I think.
Can you provide a DNG? Do I see correctly that the native resolution of the frame is 1920x1056 ? Very nice for a "plaything" ! ;-)
Quote from: GregoryOfManhattan on May 30, 2013, 07:26:34 PM
50D party may be over - merging with the latest unified, builds are not producing spanned raw files which can be processed with the latest 04a39e3 modules/raw_rec/raw2dng
getting the Error: This ain't a lv_rec RAW file
the party's over already? I just bought a 50D on the offchance this was going to pull through, haha, i guess if it seems too good to be true...
As mentioned previously, this isn't really a bug as it's unsupported, but perhaps in light of the 50D's latent capabilities is there any chance developers will take a look to get raw working again for it?
thanks to everyone for taking it as far as it's come already, unbelievable really.
It's still early days! The 'bugs' will be fixed. ::)
Quote from: necronomfive on May 30, 2013, 11:38:03 PM
Can you provide a DNG? Do I see correctly that the native resolution of the frame is 1920x1056 ? Very nice for a "plaything" ! ;-)
You just see the output settings below. I shot at 1600x900. 1920x1056 is possible theoretically, but the 50D can't keep up with the speed needed for that.
Quote from: CFP on May 30, 2013, 10:13:13 PM
Don't worry, I know what 2K is. And I am very sure that it is not possible for the 50D to record 2K raw videos at any frame rate.
The actual resolution of the 50D's sensor may be 4752 X 3168 (15 Megapixel) but Canon doesn't read the full sensor and downscale it to every resolution we want but simply skips columns and lines to get the LiveView image.
And that's what Magic Lantern's raw video is: The LiveView image.
Since something like 2048 X 1152 (16:9) 14-bit raw video at 24 frames per second would require 95 Megabyte/s write speed, the write speed is not the biggest issue. But I doubt that there's a way to increase the LiveView image's resolution without replacing the Canon Firmware ...
But when you think about it, in stills mode it is indeed a 4K camera. If you shot a RAW stills time-lapse, it would in fact be a 4K RAW sequence.
So, what is the process to grab the full 4K stills frames?? . . . Perhaps a module could be written to hijack the process that reads the sensor and get rid of all the line skipping? I know that we will not be able to do 4K - the write speeds just aren't there - but perhaps we could improve color rendition and problems like moire . . .
Just thinking out loud . . . feel free to debunk me.
Quote from: father_v on May 30, 2013, 11:52:41 PM
the party's over already? I just bought a 50D on the offchance this was going to pull through, haha, i guess if it seems too good to be true...
As mentioned previously, this isn't really a bug as it's unsupported, but perhaps in light of the 50D's latent capabilities is there any chance developers will take a look to get raw working again for it?
thanks to everyone for taking it as far as it's come already, unbelievable really.
Honestly the issue Gregory mention seems like an easy fix. It's on the OS side of things. And only for spanned footage.
The file spanning issues are still a problem for the 5d3 too and A1ex has been working on them (a lot). There are newer commits specifically related to the issue and changes have been made since Gregory posted his update. There is also a new raw2dng.exe. I could pull Gregory's build and compile with the latest commits but maybe he is already on it? Gregory?
Here are some greenish DNG's from the 5x crop mode (https://www.wetransfer.com/downloads/abe691810a3fc013c880b20ee65aa6bb20130530220816/ea8f756fbcaeab21db01e8ef418a35cf20130530220816/e9da87)
Quote from: Andy600 on May 31, 2013, 12:12:02 AM
The file spanning issues are still a problem for the 5d3 too and A1ex has been working on them (a lot). There are newer commits specifically related to the issue and changes have been made since Gregory posted his update. There is also a new raw2dng.exe. I could pull Gregory's build and compile with the latest commits but maybe he is already on it? Gregory?
Continually blowing minds. Good on all of you guys.
I'm looking through the source files and it looks as though the 50d hasn't actually been added to something important so it isn't calibrated correctly (if at all). It looks like it's guessing or assuming settings from other cameras to get it's black point and I suspect this will have a lot to do with magenta or green casts. I could be wrong but it looks like raw.c needs some work.
Scrub that. I wasn't looking at Gregory's changed raw.c. Just looking over them now to see if I can spot anything.
@ menoc:
Another way to get higher resolutions:
Use 5X crop mode. Capture first frame, move the AF-box, capture second frame, move the AF-box, capture third frame, move the AF-box, fourth frame, reset the AF-box to the first position and repeat the whole thing.
In post just merge the 4 frames together - On the 50D you would get almost 4K!
But I don't see this working at 24 frames per second.
And the file spanning thing should be solved soon. Btw. why aren't you just using exFat like on the 600D and 5D Mark III to record over 4 GB in one file? Doesn't that work on the 50D?
And the green tint is a black level issue. Should bee easy to fix that.
Quote from: menoc on May 31, 2013, 12:06:01 AM
But when you think about it, in stills mode it is indeed a 4K camera. If you shot a RAW stills time-lapse, it would in fact be a 4K RAW sequence.
So, what is the process to grab the full 4K stills frames?? . . . Perhaps a module could be written to hijack the process that reads the sensor and get rid of all the line skipping? I know that we will not be able to do 4K - the write speeds just aren't there - but perhaps we could improve color rendition and problems like moire . . .
Just thinking out loud . . . feel free to debunk me.
From what I have gathered so far, the ARM CPU in all Canon EOS is not fast enough to do any kind of real-time processing on the image data (like scaling, or bit reduction). The other problem would be that at 4K resolution, DMA probably puts a heavy burden on the SDRAM bandwidth, limiting other bus masters which access the memory area.
But what I still need to understand is why the maximum resolution increases in live view when the zoom mode is being used. I understand that Magic Lantern is currently using the default Canon register settings for the DIGIC4, which controls the downsampling of the sensor image data before it's written to SDRAM for Live View. The different screen sizes are a result of a EDMAC copy with different size parameters from that area.
The question now is: how flexible is DIGIC4 in downsampling the sensor data before it's written to SDRAM?
Sorry if I sound like a total noob, but I'm still reading my way through the sorce code and the reverse engineered register list. :-[
Quote from: CFP on May 31, 2013, 12:25:38 AM
@ menoc:
Another way to get higher resolutions:
Use 5X crop mode. Capture first frame, move the AF-box, capture second frame, move the AF-box, capture third frame, move the AF-box, fourth frame, reset the AF-box to the first position and repeat the whole thing.
In post just merge the 4 frames together - On the 50D you would get almost 4K!
But I don't see this working at 24 frames per second.
And the file spanning thing should be solved soon. Btw. why aren't you just using exFat like on the 600D and 5D Mark III to record over 4 GB in one file? Doesn't that work on the 50D?
And the green tint is a black level issue. Should bee easy to fix that.
That would be a neat work around.
I'm assuming no exFAT due to the CF slot limitations.
Re: File splitting;
Are you sure this camera doesn't support exfat? I have no large file problems on SD cameras. A1ex fixed card full footer writing or at least appears so.
@andy600 - 'bugs' perhaps not the greatest term when talking about nightly builds - apologies.
as a longterm ML user but development rookie i guess i wasn't sure what constitutes official ML support & whether that extends to the 50D.... you'll hear no complaints or demands from me, the work you've all done is amazing.
anyway cam arrived today & fast card should be here end of week so will get going with whatever limited testing I can offer - cheers!
The 50d is NEVER going to get 4k 24fps video EVER. It's just not capable. Even if the devs managed to get something like 8bit motion jpeg working it would still not be powerful or fast enough to handle that much data. The maximum dimensions are dictated by the raw sensor data that feeds LV. In other camera bodies (i.e. the 600d) changing the jpeg/raw mode could alter frame sizes but that is not implemented in the 50d and I don't know if it ever will be or if it will have any effect. The biggest frame dimensions we will get are what it stated on page one of this topic. What we need is normal and crop modes working as well as possible within the confines of CF writing speed limits.
Quote from: 1% on May 31, 2013, 12:32:31 AM
Re: File splitting;
Are you sure this camera doesn't support exfat? I have no large file problems on SD cameras. A1ex fixed card full footer writing or at least appears so.
Would this be a rewrite somewhere in the source or a format on a PC for the card?
Quote from: father_v on May 31, 2013, 12:33:43 AM
@andy600 - 'bugs' perhaps not the greatest term when talking about nightly builds - apologies.
as a longterm ML user but development rookie i guess i wasn't sure what constitutes official ML support & whether that extends to the 50D.... you'll hear no complaints or demands from me, the work you've all done is amazing.
anyway cam arrived today & fast card should be here end of week so will get going with whatever limited testing I can offer - cheers!
Don't thank me ;) I haven't really done anything yet :D
Quote from: artiswar on May 31, 2013, 12:37:33 AM
Would this be a rewrite somewhere in the source or a format on a PC for the card?
Format the CF to exfat in a computer
Quote from: Andy600 on May 31, 2013, 12:39:36 AM
Format the CF to exfat in a computer
Cards and cam in hand by Monday but by then I'm sure this will be a thing of the past. So the spanning issue originates in the segmentation based on a FAT32 system?
@1% - If you have 2 mins can you have a peek at Gregory's pull request, specifically the raw.c changes and see if anything jumps out at you that would/might cause this green/magenta issue in crop mode.
Also I'm looking at lines 438 & 439. I presume these define the max raw image size of the 50d? If so they are wrong. They are showing the same dimensions as the 60d which has an 18MP sensor.
So does exFat work on the 50D?
If it does, you won't need file spanning.
Just format the card in your PC and make it bootable with EOScard.
Quote from: JulianH on May 31, 2013, 12:14:05 AM
Here are some greenish DNG's from the 5x crop mode (https://www.wetransfer.com/downloads/abe691810a3fc013c880b20ee65aa6bb20130530220816/ea8f756fbcaeab21db01e8ef418a35cf20130530220816/e9da87)
Not using ACR, but Raw Photo Processor seems to have done a decent job with it.
(http://i.imgur.com/0ZdTy9Q.jpg)
Still quite a lot of green in the blacks Captain.
I'll try exFat tomorrow. Really have to get some sleep now - after I upload the footage I shot today :)
Quote from: Andy600 on May 31, 2013, 12:43:29 AM
@1% - If you have 2 mins can you have a peek at Gregory's pull request, specifically the raw.c changes and see if anything jumps out at you that would/might cause this green/magenta issue in crop mode.
Also I'm looking at lines 438 & 439. I presume these define the max raw image size of the 50d? If so they are wrong. They are showing the same dimensions as the 60d which has an 18MP sensor.
in http://www.magiclantern.fm/forum/index.php?topic=5586.msg42456#msg42456 , i said there are 6 camera specific conditionals for which the values need to be confirmed for the 50D.
the ones around line 438 are commented out and inactive - they are for QR_MODE - image review after taking pics.
/* #if defined(CONFIG_50D) NEED Raw dump to get correct values
width = 5344;
height = 3516;
skip_left = 142;
skip_right = 0;
skip_top = 50;
#endif
*/
so let's get the correct values for the Raw image size - though this likely will not help the tint issues.
Sorry Gregory, I should have read your notes first :-[ So it's playback related. I'm gonna try work it out.
BTW are you seeing any black borders on DNGs?
Quote from: JulianH on May 31, 2013, 01:17:29 AM
Still quite a lot of green in the blacks Captain.
I'll try exFat tomorrow. Really have to get some sleep now - after I upload the footage I shot today :)
Indeed, not ideal. I just wanted to see what RPP would do with it's autoWB. With some further tweaking I was able to push it further towards proper white balance. Wish I could help out with the exfat question, I have my 50D in hand but CF card comes wednesday! :-\
Quote from: Andy600 on May 31, 2013, 01:23:48 AM
BTW are you seeing any black borders on DNGs?
1592 width has two black pixels on the left.
I think it depends on the resolution. There are a lot now :) Can check if needed which ones give black borders or not. Let me know!
Panning mode working on the 50D. Shot at 1592x530 to show some movement.
@Gregory - I've just read the notes for running a raw dump through img.py and it's well beyond what I can do with my limited knowledge. It's the only way to get it accurate.
Have you tried altering the skip values to get rid of the 2px border (maybe line 323 should be 74?). I think these might also affect black point calc. (I seem to remember 1% saying something about it).
Thanks @JulianH
Quote from: 1% on May 31, 2013, 12:32:31 AM
Re: File splitting;
Are you sure this camera doesn't support exfat? I have no large file problems on SD cameras. A1ex fixed card full footer writing or at least appears so.
those fixes are not working on 50D, file splits at 4G, but then cannot be processed by raw2ndg
this is using code from today such as unified commit e4fc7c7
few more details at:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg43110#msg43110
exFat does not affects the ability of raw_rec.c to segment into files and raw2dng to process the files.
i'd be willing to try exFat it if the contrib make-bootable played nice with osx diskutil (or someone has another gpt/sg/fdisk command suggestion known to work on osx 10.8)
$diskutil eraseDisk exFAT EOS_DIGITAL disk1
Started erase on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as ExFAT with name EOS_DIGITAL
Volume name : EOS_DIGITAL
Partition offset : 411648 sectors (210763776 bytes)
Volume size : 62107648 sectors (31799115776 bytes)
Bytes per sector : 512
Bytes per cluster: 32768
FAT offset : 2048 sectors (1048576 bytes)
# FAT sectors : 8192
Number of FATs : 1
Cluster offset : 10240 sectors (5242880 bytes)
# Clusters : 970272
Volume Serial # : 51a7e1ed
Bitmap start : 2
Bitmap file size : 121284
Upcase start : 6
Upcase file size : 5836
Root start : 7
Mounting disk
Finished erase on disk1
$ sudo sh contrib/make-bootable/make_bootable.sh
Found /dev/disk1s2
Volume EOS_DIGITAL on disk1s2 unmounted
Error: /dev/disk1s2 is not a FAT16, FAT32 of EXFAT device
Format your card in camera before using this script
debug /dev/disk1s2 (
fat32 is no problem
diskutil eraseDisk FAT32 EOS_DIGITAL disk1
Started erase on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as MS-DOS (FAT32) with name EOS_DIGITAL
512 bytes per physical sector
/dev/rdisk1s2: 62077280 sectors in 1939915 FAT32 clusters (16384 bytes/cluster)
bps=512 spc=32 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=411648 drv=0x80 bsec=62107648 bspf=15156 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished erase on disk1
$ sudo sh contrib/make-bootable/make_bootable.sh
Found /dev/disk1s2
Volume EOS_DIGITAL on disk1s2 unmounted
Applying FAT32 parameters on /dev/disk1s2 device:
writing EOS_DEVELOP at offset 71 (Volume label)
11+0 records in
11+0 records out
11 bytes transferred in 0.000376 secs (29256 bytes/sec)
writing BOOTDISK at offset 92 (Boot code)
8+0 records in
8+0 records out
8 bytes transferred in 0.000409 secs (19565 bytes/sec)
I think 1% is saying that splitting files isn't needed at all with exFat but I don't think exFat is supported in the 50d.
hey Andy600,
yes, this is what we need to adjust.
Quote from: Andy600 on May 31, 2013, 01:42:30 AM
@Gregory get rid of the 2px border (maybe line 323 should be 74?). I think these might also affect black point calc. (I seem to remember 1% saying something about it).
Quote
* The RAW file has unused areas, usually black; we need to skip them.
* To find the skip values, start with 0,
* load the RAW in your favorite photo editor (e.g. ufraw+gimp),
* then find the usable area, read the coords and plug the skip values here.
*
* Try to use even offsets only, otherwise the colors will be screwed up.
for raw file we have in the code now (and perhaps need to adjust)
skip_top 22;
skip_left = 72;
skip_right = 0;
skip_bottom = 0;
for zoomed in raw we have in the code now and need to adjust
skip_top = 50;
skip_left = 72;
skip_right = 0;
skip_bottom = 0;
can someone please load in a processed raw of each type and measure how many pixels off we are.
Julian sees 2 black pixels on left is that for zoomed or not or both?
the zoomed in image is the one with the potential black point shift - see any more black edges?
wonder what happens if we crop too much off here?
Quote from: Andy600 on May 31, 2013, 02:03:02 AM
I think 1% is saying that splitting files isn't needed at all with exFat
Right.
I was able to record a 7 GB file with exFat on the 600d. And to process it with Raw2Dng.
Quote from: GregoryOfManhattan on May 31, 2013, 02:06:35 AM
wonder what happens if we crop too much off here?
It says to keep offsets to even numbers or the colors get screwed. Changing the value will either screw the image or adjust the border. It wont do any damage. I think it's been done by trial and error on the other bodies. My guess is that skipping 2 px will remove the border and any more will probably distort the image.
If the Black point is calculated on an image with any black border it will be off. This might fix the color cast... might ???
I also noted the white point has a universal value of 15000 apart from the 6d which is 13000. I wonder what playing with this will do? We have a different sensor so it might need tuning more.
Man you guy's are moving so fast with the build updates ;D Keep up the good work @Gregory my camera should be coming this weekend I'll be able to help than. @JulianH once again another great test like that panning option so cool.
My results for today. The video is graded in ACR. I did reduce some moire on the water :)
Download the original. Shot at 1592x864, upsized to 1080p.
Will upload dng's tomorrow.
@JulianH - Very nice :) You can pick out colour and texture in the harbor wall that would usually be trashed by H.264.
Quote from: JulianH on May 31, 2013, 02:20:00 AM
My results for today. The video is graded in ACR. I did reduce some moire on the water :)
Download the original. Shot at 1592x864, upsized to 1080p.
Will upload dng's tomorrow.
Wow Wow Wow!!!! Great video Julian.. I don't care what anybody says the 50D is by far the most filmic out of all the Canon's including the 5D Mark III. The images are soo organic looking it gives you that celluloid feel, the colors texture is unmatched Love it. Glad that I got a 50D, I think the resolution is just perfect not too sharp, not too soft just right. Keep it up Julian will be shooting some test footage soon as I get my 50D in the mail Cheers.
Quote from: Andy600 on May 31, 2013, 02:32:53 AM
@JulianH - Very nice :)
Love the 50D footage looks amazing. The 5D Mark III don't have that organic celluloid nature the way it renders the images, The cadence & motion is by far the best in the canon line-up. Now let's get that build stable in functioning a 100%. Did you get your card yet?
That footage looks absolutely incredible!
I'm off to buy a CF card today... So just a question, what sort of bit rate does the 50D go up to, or how fast can it go in the read/write tests? Is it limited to 50mb/s or there abouts?
Will a 60mb/s card fare well enough?
Sandisc 90mb/s is about twice the price... Which I'm willing to buy if it makes a difference.
I ran a benchmark on the cards that came with the camera.... 6mb/s write speed hahaha. Not nearly using the camera to its potential, if using burst mode or whatever!
Quote from: goldenchild9to5 on May 31, 2013, 02:40:26 AM
Did you get your card yet?
It's not in my hands but it's arrived in the country. Got to pick it up but never had a chance today and I missed delivery of another 'temporary' card that I bought locally while waiting. I think I used up all my luck getting the camera cheap :D
Any idea from anyone out there if the Mosaic Engineering AAF for the 60D would fit the 50D? Could be a nice solution for the moire and aliasing issues.
hmmm yeah I wouldnt commit to buying one just yet...
As best I know they basically are optimised for the 1080p resolution for standard video, if you recorded in 720p it doesnt quite work as intended.
Since we're not necessarily recording at a size/resolution/etc which is comparable to standard 1080p, it may come out strange.
It's annoying that they're such a niche item though, it's not as though you can just borrow one from your neighbour to test haha.
Although my understanding of how it works may be incorrect... I'd definitely just ask a lot of questions before committing $$$ to it though.
Quote from: Roman on May 31, 2013, 02:56:39 AM
hmmm yeah I wouldnt commit to buying one just yet...
As best I know they basically are optimised for the 1080p resolution for standard video, if you recorded in 720p it doesnt quite work as intended.
Since we're not necessarily recording at a size/resolution/etc which is comparable to standard 1080p, it may come out strange.
It's annoying that they're such a niche item though, it's not as though you can just borrow one from your neighbour to test haha.
Although my understanding of how it works may be incorrect... I'd definitely just ask a lot of questions before committing $$$ to it though.
Good call. There're some other DIY options I want to try first anyway.
Quote from: Andy600 on May 31, 2013, 02:45:01 AM
It's not in my hands but it's arrived in the country. Got to pick it up but never had a chance today and I missed delivery of another 'temporary' card that I bought locally while waiting. I think I used up all my luck getting the camera cheap :D
Lol.. at least the card is here for pick-up. I have to wait a couple more days to get the camera & card I'm patient. In the meantime I'm clearing out space from my Hard-Drive & updating my system from Adobe CS5.5 to CS6
Back from my test shoot with yesterday's build on the 50D w/ some great results. I'll show some updated images in a few after processing the .RAW files shortly :) It's turning out better and better!
Quote from: CaptainOfObvious on May 31, 2013, 01:06:39 AM
Not using ACR, but Raw Photo Processor seems to have done a decent job with it.
(http://i.imgur.com/0ZdTy9Q.jpg)
Green'ish blacks looks much like Kodak Portra film with that frame.
hear good things from KahL and JulianH who have been testing this build.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/50D-2013May28build.zip
if you are new to ML or 50D, please
1. Make sure you can install and use the officially release Magic Lantern 2.3 with beautiful h.264 1920x1080 video on the 50D. http://www.magiclantern.fm/releasenotes
2. Read the "RAW video & ML -- Beginners Guide and FAQ -- READ FIRST" http://www.magiclantern.fm/forum/index.php?topic=5520.0
3. remember that this is alpha - things will break, when in doubt pull it out - the battery. if you set up an action sequence and the train rolls up on cue as the actor in the jeep pulls up, and he jumps off the jeep runs up to a boxcar and jumps onto the rolling train - your shot may be lost or ruined with alpha code.
4. there may be quirks where for example the first recording after loading a battery fails with dropped frames but everything thereafter works.
lets see some more raw videos. please share your results and workflow.
regards,
gregory
if you don't know how to use it, stick with the release
Quote from: CFP on May 31, 2013, 12:25:38 AM
@ menoc:
Another way to get higher resolutions:
Use 5X crop mode. Capture first frame, move the AF-box, capture second frame, move the AF-box, capture third frame, move the AF-box, fourth frame, reset the AF-box to the first position and repeat the whole thing.
In post just merge the 4 frames together - On the 50D you would get almost 4K!
But I don't see this working at 24 frames per second.
And the file spanning thing should be solved soon. Btw. why aren't you just using exFat like on the 600D and 5D Mark III to record over 4 GB in one file? Doesn't that work on the 50D?
And the green tint is a black level issue. Should bee easy to fix that.
See what you're saying but as you capturing multiple Liveview grabs per frame would require perhaps a faster processor. Who knows, they may figure it out at some point. Remember, a year ago all the developers swore that RAW was impossible!!
The 50D's hardware itself does not support exFat. Only the newer cameras and the 5D3 supports it. But the thing is that if we can do seamless file spanning (files that have no time breaks or skipped frames between them) then Fat32 is not an issue.
It'll be interesting to see where we are by August or September of this year.
Okay I just bought a Sandisk 90mb/s 16gb.
Ran an initial speed test in the 50D- 35-39mb/s :(
However after reformatting, following this guide:
http://www.sevenforums.com/tutorials/113967-ssd-alignment.html
It's now getting between 60-70mbs! Quite a remarkable difference just on account of formatting in a particular way.
Still not as good as 100mb/s or whatever from Komputerbay but I was impatient and this was the best I could get today haha.
Great work everybody on getting this done! Given the subject of this thread, is this close to happening on the 40d as well?
Quote from: necronomfive on May 31, 2013, 12:27:47 AM
From what I have gathered so far, the ARM CPU in all Canon EOS is not fast enough to do any kind of real-time processing on the image data (like scaling, or bit reduction). The other problem would be that at 4K resolution, DMA probably puts a heavy burden on the SDRAM bandwidth, limiting other bus masters which access the memory area.
But what I still need to understand is why the maximum resolution increases in live view when the zoom mode is being used. I understand that Magic Lantern is currently using the default Canon register settings for the DIGIC4, which controls the downsampling of the sensor image data before it's written to SDRAM for Live View. The different screen sizes are a result of a EDMAC copy with different size parameters from that area.
The question now is: how flexible is DIGIC4 in downsampling the sensor data before it's written to SDRAM?
Sorry if I sound like a total noob, but I'm still reading my way through the sorce code and the reverse engineered register list. :-[
My guess is that in order to make the crop mode usable, Canon engineers probably had to increase the resolution but for monitoring through the LCD you don't need that much resolution - it was meant just to be a display, plain and simple. But this suggests that there is a lot of upscaling and downscaling going on before the data gets to SDRAM. I don't know that hijacking that process is doable as it may require modifying the firmware
Quote from: GregoryOfManhattan on May 31, 2013, 04:24:20 AM
hear good things from KahL and JulianH who have been testing this build.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/50D-2013May28build.zip
if you are new to ML or 50D, please
1. Make sure you can install and use the officially release Magic Lantern 2.3 with beautiful h.264 1920x1080 video on the 50D. http://www.magiclantern.fm/releasenotes
2. Read the "RAW video & ML -- Beginners Guide and FAQ -- READ FIRST" http://www.magiclantern.fm/forum/index.php?topic=5520.0
3. remember that this is alpha - things will break, when in doubt pull it out - the battery. if you set up an action sequence and the train rolls up on cue as the actor in the jeep pulls up, and he jumps off the jeep runs up to a boxcar and jumps onto the rolling train - your shot may be lost or ruined with alpha code.
4. there may be quirks where for example the first recording after loading a battery fails with dropped frames but everything thereafter works.
lets see some more raw videos. please share your results and workflow.
regards,
gregory
if you don't know how to use it, stick with the release
Thanks for Sharing Gregory.. will try as soon as I get my camera.
Quote from: Roman on May 31, 2013, 04:35:30 AM
Okay I just bought a Sandisk 90mb/s 16gb.
Ran an initial speed test in the 50D- 35-39mb/s :(
However after reformatting, following this guide:
http://www.sevenforums.com/tutorials/113967-ssd-alignment.html
It's now getting between 60-70mbs! Quite a remarkable difference just on account of formatting in a particular way.
Still not as good as 100mb/s or whatever from Komputerbay but I was impatient and this was the best I could get today haha.
Roman did you do every single step when formatting your card?
I'm very excited to try raw recording on my newly acquired 50D. If I crack it, I'll post video and DNGs for sure.
I'm a little confused as to the state of things and what I can expect. How long will I be able to record raw on the 50D for? Assuming a fast card and the maximum allowable resolution / frame rate. What can i expect?
Please forgive the question but its not obvious to me from reading the forum.
Quote from: menoc on May 31, 2013, 04:56:16 AM
My guess is that in order to make the crop mode usable, Canon engineers probably had to increase the resolution but for monitoring through the LCD you don't need that much resolution - it was meant just to be a display, plain and simple. But this suggests that there is a lot of upscaling and downscaling going on before the data gets to SDRAM. I don't know that hijacking that process is doable as it may require modifying the firmware
I mean, for standard Live View, it's clear that it's 1/3 downscaling, because that's the easiest way to downscale the sensor data while retaining the bayer pattern structure. Very easy to implement in hardware.
As I understand, 5x and 10x zoom configures the scaling factor to x1, but DIGIC writes only a window of the original sensor area into SDRAM. The question would be if the width and height and position of this window can be adjusted in hardware, which, in theory, would enable to save, let's say, 2K of sensor data to SDRAM (of course with a much bigger crop factor, but that's basically the same "problem" the Black Magic Pocket Cinema Camera has). I bet that it's possible, because DIGIC4 was obviously designed to adapt to different sensor metrics (50D vs. 5DMKII).
Adjusting the width and height of the sampling window inside the DIGIC4 (instead of just copying a rectangle from a larger area via EDMAC), might also have a positive impact on performance, because only data that's supposed to be visible is being copied to SDRAM, freeing additional bandwidth for Compact Flash DMA.
If such registers exist, they would be changed by the Canon firmware when the User presses the +/- buttons in Live View and could be overridden by the raw recording task.
@JulianH: for (digital) panning mode you need to film in crop mode right? What (crop mode) did you use for the "Scheveningen" movie? thnx I will do my first tests this weekend
Quote from: artiswar on May 31, 2013, 02:53:24 AM
Any idea from anyone out there if the Mosaic Engineering AAF for the 60D would fit the 50D? Could be a nice solution for the moire and aliasing issues.
As mentioned it won't work since it's not recording 1920*xxxx. Another workaround would be to film in crop mode (it will eliminate more/aliasing), but we need wider angle lenses for that (a 12mm to get the same 35mm look for example)...
Crop factor in 1920x1080 should be around (4770/1920)*1,6 = 3,975. So a 12mm lens would be equal to 48mm.
On the other hand, it would enable to use regular 16mm /Super 16mm film lenses for filming, because the size of the used sensor area would measure around 9,05mm x 5,08mm, which fits into the 16mm size boundaries.
So, in theory, IF the 50D code could be optimized to write 1920x1080 24fps in cropped mode, it would be a perfectly useable digital replacement for a 16mm film camera. Even better, you could switch between full resolution in 16mm mode, or slightly lower resolution for shots which require shallow DOF.
QuoteThe 50D's hardware itself does not support exFat.
Has nothing to do with hardware. Check if exfat strings exist in the FW. Either support for the FS is in there or not.
Exfat released in 2009... 50D first release in 2008.. latest 50D firmware released in 2012 and should share the same code base as other cameras. So 50/50.
If your skips are wrong either you'll get darkened/green shadows or pink image. Every mode is slightly different just take a silent pic with 0 skips and count the pixels.
For raw photo.. the skips are in the meta data of the cr2 files... open with photoME. You have to get the right state for it to grab the raw buffer... its probably the 5d2 state.
QuoteThe question would be if the width and height and position of this window can be adjusted in hardware
You should be able to move the zoom window around.. making it bigger probably not. Otherwise they would have done a full height -> ram and not bothered. They seem to like big image in ram and then lots of transforms to it to get H264/YUV/etc.
Quote from: savale on May 31, 2013, 10:15:41 AM
@JulianH: for (digital) panning mode you need to film in crop mode right? What (crop mode) did you use for the "Scheveningen" movie? thnx I will do my first tests this weekend
You don't have to use crop mode for panning. I shot at 1592x530 so you can pan up and down quite a lot. You could also shoot 1280x720 and pan in all directions.
In my last movie, only the last zoomed shot of the kissing couple is in crop mode (5x). I shot a lot more in crop mode but everything turned out greenish as showed earlier, so I left most of it out of the video.
If you have green color cast, the skip values in raw.c are not correct. Set black level manually to 1024 when developing the raws.
I dont think its possible to set the black level in acr. Ill give raw therapy a try or should i use something else?
Quote from: JulianH on May 31, 2013, 11:00:56 AM
You don't have to use crop mode for panning. I shot at 1592x530 so you can pan up and down quite a lot. You could also shoot 1280x720 and pan in all directions.
In my last movie, only the last zoomed shot of the kissing couple is in crop mode (5x). I shot a lot more in crop mode but everything turned out greenish as showed earlier, so I left most of it out of the video.
I understand :) When not in crop mode: you can pan up and down because of the 4/3 sensor size. Pan left / right is not possible of course... Thnx
Hey regarding card speed etc on 50D, I've been having some inconsistent results since formatting the card initially.
With the 600D there were some settings I put the camera to, to eke out a bit more performance... I got it running bang on the 20-12mb/s limit.
However no matter what I've done so far with the 50D, I havent been able to get back to the combination of things which gave me 60-70mb/s.
I've tried: Setting camera to raw, sraw2, small jpg, large jpg (doesnt seem much difference to speed test)
global view on/off - meh.
But then, camera set to 30fps as per default - gave me 30-40mb/s
So I tried exposure override to 2fps, and got 50-60mb/s
Then back to 24fps, and getting somewhere in the middle.
Why would this be? And what settings do other people have, to acheive the 100mb/s read/write speeds if I'm getting non card related variance at such a lower speed? It seems reformatting either in camera, in windows, or aligning the partition dont make much difference now.
JulianH and 1%, yes we discussed changing the settings in raw.c
we know that 2 out of 6 camera specific parameters in raw.c are incorrect for 50D.
asking community for input is yielding slow results.
need to know for both regular and zoomed in exactly how many pixels top,right,bottom,left of black are present if any.
Julian says 2 on the left and i asked to clarify if that is zoom only and prefer confirmation from another user before editing code.
Quote from: GregoryOfManhattan on May 31, 2013, 02:06:35 AM
yes, this is what we need to adjust.
can someone please load in a processed raw of each type {zoomed and not-zoomed} and measure how many pixels off we are.
Julian sees 2 black pixels on left is that for zoomed or not or both?
the zoomed in image is the one with the potential black point shift - see any more black edges?
same for the QR_mode image sizes - http://www.magiclantern.fm/forum/index.php?topic=5586.msg43295#msg43295
i did scan the ufraw-0.19.2 source code to confirm the CAM_COLORMATRIX1 (1 out of 6)
Set the skip offsets to 0, set 1024 for black level, then check the black border sizes in Paint (count the pixels). That's it.
Hi everyone! I got 50D yesterday and made some test shot.
http://www.youtube.com/watch?v=J2X1KqNmiDQ
I wanted upload to Vimeo but I could not.
I'm using sandisk Extreme 60MB/s.
I don't have windows so I'm using Macboot but it doesn't work well.
Camera says "script dir missing" always.
So I'm keeping ML program in my CF card.
Then it woks well.
But if I could use Macboot correctly, then it's very helpful.
I checked some tutorial movie and I did same but still ML program don't stay in camera.
Any Mac user have same problem with 50D or only me?
I don't have a time in this weekend. But I will have some free time in next week and would go to some test shot.
And gonna film more cool footage.
Please let me know if you guys have some question. I want to support each other on this board though my English is not so good. But I do my best.
Thanks a lot!
Quote from: a1ex on May 31, 2013, 12:47:50 PM
Set the skip offsets to 0, set 1024 for black level, then check the black border sizes in Paint (count the pixels). That's it.
understood and the comments on pull request as well.
thanks you.
How many real modes do you guys have avail? I have a feeling 24p and possibly others are in there without FPS override... again another thing to check in the dump. You'd have to switch them manually.
Quote from: 1% on May 31, 2013, 04:22:51 PM
How many real modes do you guys have avail? I have a feeling 24p and possibly others are in there without FPS override... again another thing to check in the dump. You'd have to switch them manually.
Thank you for contribution 1%
My 50D is in town should be delivered today, or I'll go pick it up myself ;D Should be helping out soon.
1%
are you suggesting:
compile with CONFIG_DEBUGMSG=1
Dump ROM from Debug
examine ROM0.bin for "real modes" ?
can you please provide examples of what to look for.
otherwise, i'd think of diffing platform/5D2.212/stubs.S and platform/50D.109/stubs.S to see whats missing on 50D that is present on 5D2.
Since there is no real conclusion yet: I will try exFat tomorrow.
@ julian
my 550d now get up to 2496*1065 in crop mode...
i take the new raw.rec.mo from the 5d3 and replace it works without any problems..
you guys should try the same!
Quoteexamine ROM0.bin for "real modes" ?
Yup, and look for exfat + get 640K memory.
Look for this: H264E InitializeH264Encode in strings.
If you get a dump, send it this way too and I can poke around.
Quote from: hammermina on May 31, 2013, 06:03:44 PM
@ julian
my 550d now get up to 2496*1065 in crop mode...
i take the new raw.rec.mo from the 5d3 and replace it works without any problems..
you guys should try the same!
How many frames can you record at 2496*1065 before it stops?
i can record still to 4gb but only 4fps:-) ots perfect for timelapsing...but still remember the 550d has this ugly 21.3mb/s limit and the 50d didnt.
i think thw 50d can do 12 fps at this res...
In 5X Crop mode the 50D's resolution is "only" ~ 1920 X 1080. To record continuously with this resolution at 24 frames per second the 50D would need 83 Megabyte/s write speed. We already saw benchmarks in play back mode which have proven that the 50D has that write speed.
But in LiveView the write speed drops. Until somebody finds a way to avoid that, full HD isn't possible for more than a few seconds.
And it would be crop, of course.
@CFP
this hack now exists since 2 weeks...wait what the future brings. 3 days ago the 550d was max 1730 now its near 2600...
if the guys get a hand on implement 12 or 10 bit raw or efen an compession like red does.the train will rolling fast.
still trinking tee and testing the newest versions and report bugs:-)
thats what i do...
Kill the edmacs when recording.. see if speed goes up.
Saw a 50D for 450... still too much for me to drop on a whim.
@CFP
replace only the raw_rec.mo from newest 5dm3
Here is the new updated build for the 5D3
https://drive.google.com/folderview?id=0B7QlH_BH2m32d3Y4em1lZEYwOE0&usp=sharing
and report
on my 550D it brings me the 2496 in 5*zoom
Quote from: 1% on May 31, 2013, 07:12:12 PM
Kill the edmacs when recording.. see if speed goes up.
Saw a 50D for 450... still too much for me to drop on a whim.
Great news Just got my 50D in the mail ;D I have a 30mb/s card right now which is slow but still gonna give it a run. KomputerBay 64GB card coming tomorrow I'll be prepping for when it comes. @ the moment I'm charging battery to update to firmware v1.0.9 currently it's v1.0.7 . Got one question are there any settings in camera that I should enable, or disable before shooting Raw?
Quote from: 1% on May 31, 2013, 07:12:12 PM
Kill the edmacs when recording.. see if speed goes up.
Saw a 50D for 450... still too much for me to drop on a whim.
Everybody Let's put money together and help 1% get a 50D.. The more we help each other the better the hacks for the 50D and other canons will be... Who is in?
$10 each person, & if you want to put more that's even better (X) 50 people that's $500
1% let us know if you approve?
I'm ready to put my contribution in.
Quote from: goldenchild9to5 on May 31, 2013, 07:51:22 PM
Everybody Let's put money together and help 1% get a 50D.. The more we help each other the better the hacks for the 50D and other canons will be... Who is in?
$10 each person, & if you want to put more that's even better (X) 50 people that's $500
1% let us know if you approve?
I'm ready to put my contribution in.
I totally agree.....1% please give us your paypal account......and please everybody give some money to 1%......he is doing an incredible work for all of us....
Count me in for $20. It's the least i can do.
Quote from: goldenchild9to5 on May 31, 2013, 07:51:22 PM
Everybody Let's put money together and help 1% get a 50D.. The more we help each other the better the hacks for the 50D and other canons will be... Who is in?
$10 each person, & if you want to put more that's even better (X) 50 people that's $500
1% let us know if you approve?
I'm ready to put my contribution in.
Count me in.
Quote from: hammermina on May 31, 2013, 07:43:43 PM
@CFP
replace only the raw_rec.mo from newest 5dm3
Here is the new updated build for the 5D3
https://drive.google.com/folderview?id=0B7QlH_BH2m32d3Y4em1lZEYwOE0&usp=sharing
and report
on my 550D it brings me the 2496 in 5*zoom
Will give it a try!
Also will upload dngs with black bars as soon as I get home.
@GoldenChild: put the camera on jpg to maximize buffer. Turn on exposure simulation in live view menu. Good luck, enjoy and share your footage.
Considering collecting money for devs to buy bodies: Andy and me are looking into that.
I'm in for $20.
(eagerly awaiting my 50d!)
Quote from: hammermina on May 31, 2013, 07:07:17 PM
replace only the raw_rec.mo from newest 5dm3
My EOS 600D simply freezes if I do that ;)
But it doesn't matter to me.
On the 600D we had 2496 X 1065 in 5X/10X crop mode since the very first build. That's nothing new.
But every camera has a max. resolution in 1X mode and a max resolution in 5X/10X mode.
And for the 50D that's simply 1592 X 1062 and 1920 X 1080. For the 550D/600D/60D it's 1732 X 1154 and 2496 X 1065. And the 5D Mark III has even higher resolutions in both modes.
And since 1% said that there likely won't be a way to increase it, I would simply stop dreaming and be happy with what we already have :D
Quote from: goldenchild9to5 on May 31, 2013, 07:51:22 PM
Everybody Let's put money together and help 1% get a 50D.. The more we help each other the better the hacks for the 50D and other canons will be... Who is in?
$10 each person, & if you want to put more that's even better (X) 50 people that's $500
1% let us know if you approve?
I'm ready to put my contribution in.
Im in :D
What I'm most interested in at this point is getting spanning to work. I'm more than satisfied with the images produced thus far. Just want to be able to roll a long clip.
Guys,
Thankyou for your enthusiasm.
We are seeking clarification from admins regarding donations specifically for development. However, there is nothing to stop you privately donating to an individual in recognition of their help and advice given on this or any other forum. What they use your donation for is entirely up to them but please do so privately ;)
Hopefully the admin team will make an announcement soon covering donation issues and other matters.
My latest test, guys.
This shows off the latest 50D build with the raw, untouched images and fully graded images. Also a small comparison between Canon h.264 video and RAW image frames.
BTW, I'm in to donate as well!
Quote from: CFP on May 31, 2013, 08:25:51 PM
And since 1% said that there likely won't be a way to increase it, I would simply stop dreaming and be happy with what we already have :D
Only unhappy guys have the ambition to push boundaries. 8)
When my KomputerBay card arrives hopefully tomorrow, I'm all set for testing and hacking.
@ kahl
wonderful colors looks like the seventies are back..
Quote from: KahL on May 31, 2013, 08:56:27 PM
My latest test, guys.
This shows off the latest 50D build with the raw, untouched images and fully graded images. Also a small comparison between Canon h.264 video and RAW image frames.
https://vimeo.com/67415324
BTW, I'm in to donate as well!
I really like that grainy 16mm look. And detail is quite good, leaps and bounds above the H264 video image. I think that from a price<>image quality point, the 50D is by far the best alternative, and a serious threat to the upcoming BMPCC.
Quote from: hijodeibn on May 31, 2013, 07:59:26 PM
I totally agree.....1% please give us your paypal account......and please everybody give some money to 1%......he is doing an incredible work for all of us....
Great to know your for it..
Quote from: muddmanrich on May 31, 2013, 08:03:57 PM
Count me in for $20. It's the least i can do.
Great to know your for it.. that's good enough.
Quote from: JulianH on May 31, 2013, 08:22:59 PM
Will give it a try!
Also will upload dngs with black bars as soon as I get home.
@GoldenChild: put the camera on jpg to maximize buffer. Turn on exposure simulation in live view menu. Good luck, enjoy and share your footage.
Considering collecting money for devs to buy bodies: Andy and me are looking into that.
Great!!! Thanks for the info JulianH. Yeah collecting for 1% would be great.
Quote from: pbr on May 31, 2013, 08:23:43 PM
I'm in for $20.
(eagerly awaiting my 50d!)
Great to know your for it.. $20 would be perfect.
Quote from: necronomfive on May 31, 2013, 09:17:58 PM
I think that from a price<>image quality point, the 50D is by far the best alternative, and a serious threat to the upcoming BMPCC.
I have the BlackMagic Pocket on preorder, since the day it was announced. Seriously thinking about cancelling it so yes, that might be the case ;)
any word on exFat on 50D?
i've used osx diskutil to format, but
sh contrib/make-bootable/make-bootable.sh - doesn't work for me.
please let me know if anyone has run exFat on50D.
Count me in for 20.00 for 1%
Quote from: GregoryOfManhattan on May 31, 2013, 09:55:41 PM
any word on exFat on 50D?
i've used osx diskutil to format, but
sh contrib/make-bootable/make-bootable.sh - doesn't work for me.
please let me know if anyone has run exFat on50D.
Emptying my card and going to try it right now.
No success w/ exFat: Tried exFAT on a 8GB SanDisk using Win7 Disk Manager for low level reformat and EOScard to set the boot flag -> Camera complains that the card is either unformatted or not formatted with the camera...
Quote from: 1% on May 31, 2013, 10:41:02 AM
Has nothing to do with hardware. Check if exfat strings exist in the FW. Either support for the FS is in there or not.
Exfat released in 2009... 50D first release in 2008.. latest 50D firmware released in 2012 and should share the same code base as other cameras. So 50/50.
If your skips are wrong either you'll get darkened/green shadows or pink image. Every mode is slightly different just take a silent pic with 0 skips and count the pixels.
For raw photo.. the skips are in the meta data of the cr2 files... open with photoME. You have to get the right state for it to grab the raw buffer... its probably the 5d2 state.
You should be able to move the zoom window around.. making it bigger probably not. Otherwise they would have done a full height -> ram and not bothered. They seem to like big image in ram and then lots of transforms to it to get H264/YUV/etc.
I was under the impression that exFat was a hardware issue, apparently not . . . Haven't read all the posts yet but, has anyone gotten exFat to work on the 50D yet?
@GregoryOfManhattan: want me to try as well or is the info from rue enough? I'm on Win7 too.
Quote from: rue on May 31, 2013, 10:32:08 PM
No success w/ exFat: Tried exFAT on a 8GB SanDisk using Win7 Disk Manager for low level reformat and EOScard to set the boot flag -> Camera complains that the card is either unformatted or not formatted with the camera...
Also tried it (with a POS 512MB Kingston CF card), no success! :(
Quote from: JulianH on May 31, 2013, 12:14:26 PM
I dont think its possible to set the black level in acr. Ill give raw therapy a try or should i use something else?
You can set the black level in ML menus . . . I think . .
Quote from: necronomfive on May 31, 2013, 10:43:21 PM
Also tried it (with a POS 512MB Kingston CF card), no success! :(
Just tried exFat with my card, the camera does not recognize it.
Are you sure you made it bootable with EOScard? Just formating doesn't work!
If exFat really doesn't work in the 50D, that's sad. Then you'll have to wait until the spanning is optimized.
Quote from: Roman on May 28, 2013, 07:43:35 AM
Because the HDMI output goes through all of the compression etc as a normal recorded video file, and is 8 bit.
Where as recording to the cf card is 14 bit raw images at a fairly hefty bitrate.
I'm about an hour away from owning a 50D with a battery grip and 4 batteries, only challenge now will be finding a place that sells fast CF cards for less than a billion dollars that ships to New Zealand. :(
Let me know if you find decent price on CF card to NZ. I'm in the same boat.... except I will be waiting on 50D for a few days at least!
Quote from: CFP on May 31, 2013, 11:00:16 PM
Are you sure you made it bootable with EOScard? Just formating doesn't work!
If exFat really doesn't work in the 50D, that's sad. Then you'll have to wait until the spanning is optimized.
What's the terminal based method for making exFAT bootable?
Quote from: CFP on May 31, 2013, 11:00:16 PM
Are you sure you made it bootable with EOScard? Just formating doesn't work!
Just tried on a 4GB Sandisk Extreme III with EOScard (clicked the ML setting). Doesn't work, same error in camera.
Quote from: JulianH on May 31, 2013, 11:18:44 PM
Just tried on a 4GB Sandisk Extreme III with EOScard (clicked the ML setting). Doesn't work, same error in camera.
Julian, manually merging the spanned raw files as mention a few pages back doesn't work either?
necronomfive, menoc, JulianH - thanks for trying the 50D exFat formatting card in computer and make-bootable.
seems clear that it does not work.
i spoke with komputerbay today to see if they had additional information on partition alignment on FAT32.
they did not have immediate information on that.
they had an ML team on site yesterday (someone named Nathan and friends).
they seem to think that one user with a 50D was able to get exFat to work - this is why i asked here.
exFat gives another 20MB/s over FAT32
they suggested formatting a 64GB into 2 32GB partitions to see if that helps the speed.
they also tell me to be sure to "clear your buffers" on the camera - i do not know what this means in practice.
Cool to hear Komputerbay is helping with this. Not surprising though, they must have doubled their profits over the past few weeks ;)
@GregoryOfManhattan: I emailed you the pics of the black bars in the DNG's.
The only cases I get black pixels are:
Full sensor mode
1592x1062 - 2 black pixels left, 4 pixels on top
1592x lower height - 2 black pixels left
No black pixels in crop mode
Didn't try _all_ the variations, but I suspect it only has to do with the boundaries, so for example 1440x720 (full sensor) can't be affected anyway?
Quote from: a1ex on May 31, 2013, 12:47:50 PM
Set the skip offsets to 0, set 1024 for black level, then check the black border sizes in Paint (count the pixels). That's it.
important result of tests.
zoom mode color cast is not due to black edges and incorrect values in the raw_update_params() function.
JulianH and I have both produced zoom mode dng, examined them and found no black borders.
(the values in raw_update_parameters are incorrect but not in a way that leaves any black borders on zoom'ed raw)
also, i did not modify code to lock the black_level to 1024 - let me know if i should have done so.
could something else used in the autodetect_black_level function be inaccurate in zoom mode?
can anyone summarize technically what happens in ML zoom x5 mode for live view recording - there is a lot of code to read through from modules/lv_rec modules/raw_rec and src/raw.c
are other cameras experiencing this issue with recent builds?
I just got a 50D and a Delkin Devices 32GB UDMA 7 card. I've installed ML and replaced the autoexe.bin w/ the one from this thread (2nd post). I've also added the MODULES folder into the ML Directory. When I start the camera up, I get a "scripts dir missing" message. It allows me to load the modules and start shooting RAW but it stops within the first 2-5 seconds.
Can anyone help troubleshoot the problem?
I followed the same steps and had the same experience. GregoryofManhatten was good enough to offer to send me an updated build through email - and that helped some (write rates more like 35Mb/s versus the 20 or so with those first files) - still I'm trying to figure out why a card that operates at 80-90Mb/s doing raw in my 5Dmiii is so much slower so-far in the 50D.
Please post any progress and I'll do the same....
Best regards
welcome methodikalgee,
please Read the "RAW video & ML -- Beginners Guide and FAQ -- READ FIRST" http://www.magiclantern.fm/forum/index.php?topic=5520.0
builds are posted to the forum now.
dhallowell19 are you using separate clean cards for each camera? is the 5D3 exFat?
Quotestill I'm trying to figure out why a card that operates at 80-90Mb/s doing raw in my 5Dmiii
Lower UDMA mode supported. Shame if exfat isn't supported... supposedly the spanning works now on 5D2 and this camera looks to be what 6D is to 5D3.. cut down version. So probably no 720P60 (5DII doesn't have this?)
I had issues with FPS override creating slightly different borders on 6D... you have FPS override on all the time.
I guess would have to take a look. We'll see what happens with the donations. I'd prefer a camera to money honestly. btw dumper in debug.c is set for digic V addresses.. noticed this from 550D thread.
Quote from: 1% on June 01, 2013, 02:50:29 AM
Lower UDMA mode supported. Shame if exfat isn't supported... supposedly the spanning works now on 5D2 and this camera looks to be what 6D is to 5D3.. cut down version. So probably no 720P60 (5DII doesn't have this?)
I had issues with FPS override creating slightly different borders on 6D... you have FPS override on all the time.
I guess would have to take a look. We'll see what happens with the donations. I'd prefer a camera to money honestly. btw dumper in debug.c is set for digic V addresses.. noticed this from 550D thread.
So then the MKII supports exFAT? I'm interested to know hiw the user Gregory mentioned got exFAT to work.
Does joining the spanned files in Terminal into a single .raw play nicely with raw2dng?
MKII is supposed to not support exfat, thats what I heard but obv, can't test. Firmware would tell for sure or if its disabled.
Joining the files in terminal is supposed to work.
Quote from: 1% on June 01, 2013, 03:06:12 AM
MKII is supposed to not support exfat, thats what I heard but obv, can't test. Firmware would tell for sure or if its disabled.
Joining the files in terminal is supposed to work.
Thank you. Cards and body in hand finally. No glass yet. I'm gonna play with some exFAT formatting and spanning this evening.
Quote from: artiswar on May 31, 2013, 08:39:58 PM
What I'm most interested in at this point is getting spanning to work. I'm more than satisfied with the images produced thus far. Just want to be able to roll a long clip.
I think that's a good idea. It will speak very well for the hack and will put it on a different level . . .
Quote from: KahL on May 31, 2013, 08:56:27 PM
My latest test, guys.
This shows off the latest 50D build with the raw, untouched images and fully graded images. Also a small comparison between Canon h.264 video and RAW image frames.
BTW, I'm in to donate as well!
Nice! Question: Did you use a profile? Did you add grain in ACR?, or some other means?
Quote from: menoc on June 01, 2013, 03:53:27 AM
I think that's a good idea. It will speak very well for the hack and will put it on a different level . . .
Precisely. I have a script waiting to be shot and Zeiss glass in route. Even if it requires a stint in terminal to get the spanned clips out, that'll due.
Quote from: artiswar on June 01, 2013, 03:10:19 AM
Thank you. Cards and body in hand finally. No glass yet. I'm gonna play with some exFAT formatting and spanning this evening.
Congrats..
Quote from: artiswar on June 01, 2013, 04:15:18 AM
Precisely. I have a script waiting to be shot and Zeiss glass in route. Even if it requires a stint in terminal to get the spanned clips out, that'll due.
Nice.. Zeiss is the way to go..
Hopefully we can get some method of file spanning to work, I hope it's something that can be done otherwise you only get about a minute of stable maximum-res 50D RAW right?
By the way I'm totally down to donate aswell, we have people contributing their time here for something that only benefits us and I have no problem in helping out.
Just wanted to share this test video w/ you guys. Don't judge me on the subject matter, or the non stabilized hand held shots, or the choice of music, or the different white balances in each shot LoL
Anyway, I don't know how good YouTube is w/ compression but it looks pretty close to my original file if you ask me. (Will update w/ a vimeo link as soon as it's available.)
Guy's I have a question does the 50D warm-up when using the hack? my temp reading started at 39 degrees and after about 10 minutes it went up to 55 degree. I have a 30mb/s card just not enough to shoot Raw only getting 51 frames.. today I'm getting my new card 8)
Quote from: methodikalgee on June 01, 2013, 09:06:45 AM
Just wanted to share this test video w/ you guys. Don't judge me on the subject matter, or the non stabilized hand held shots, or the choice of music, or the different white balances in each shot LoL
Anyway, I don't know how good YouTube is w/ compression but it looks pretty close to my original file if you ask me. (Will update w/ a vimeo link as soon as it's available.)
Nice... Thanks for sharing great job. At what res did you shoot on? I see a lot of frame drops, and a couple pink frames. What card did you use to shoot?
I'm testing now. I have some questions:
1. To enable recording, I press live view from the ML menu, then the set button in the back dial? I was able to record video from the live view button itself and I'm a little confused.
2. I'm only given 1080p/3-fps as an option from movie recording mode... the raw shows 0x0; as an aside I'm getting about 70 frames on a 400x Transcend card.
Any suggestions?
I'm in for $10 for 1% too
I'm doing a 'shoot raw on your 50D' video tutorial for first time ML users. This should answer most questions. Hope to have it online in a few hours.
Quote from: JulianH on June 01, 2013, 01:26:11 PM
I'm doing a 'shoot raw on your 50D' video tutorial for first time ML users. This should answer most questions. Hope to have it online in a few hours.
Thanks you Julian :)
Quote from: JulianH on June 01, 2013, 01:26:11 PM
I'm doing a 'shoot raw on your 50D' video tutorial for first time ML users. This should answer most questions. Hope to have it online in a few hours.
Now that's what I'm talking about a tutorial is really needed including with settings . Does your camera warm-up a bit when recording Raw? Mine does warm-up not overly hot but it get's warm.
Quote from: rommex on June 01, 2013, 11:06:20 AM
I'm in for $10 for 1% too
Great... still waiting on 1% to approve.
Quote from: buildbyflying on June 01, 2013, 10:59:45 AM
I'm testing now. I have some questions:
1. To enable recording, I press live view from the ML menu, then the set button in the back dial? I was able to record video from the live view button itself and I'm a little confused.
2. I'm only given 1080p/3-fps as an option from movie recording mode... the raw shows 0x0; as an aside I'm getting about 70 frames on a 400x Transcend card.
Any suggestions?
JulianH is making a tutorial video for beginners should be up soon.
Heh, I approve but does a1ex approve. You guys can make a paypal somewhere and put money in it then just drop ship me a 50D (body only, maybe power adapter + medium range CF (I only have 2x32gb from my XTI)
Quote from: 1% on June 01, 2013, 03:12:46 PM
Heh, I approve but does a1ex approve. You guys can make a paypal somewhere and put money in it then just drop ship me a 50D (body only, maybe power adapter + medium range CF (I only have 2x32gb from my XTI)
I'm on a 50D hunt, I'm willing to buy one and ship it to you (from the Netherlands, you're in the US I heard? have to find out how that works with tax.. can ship as gift + low value I suppose). Then after that is done it would be nice if people could pay me some money back.
AC adapter is harder to find I think. I'll try to find a 50D this weekend, keep you guys posted.
Hi all,
Fantastic work so far, big thanks to all involved. I own a 550D and my GF owns a 50D. I've been doing some testing on both and so far results and stability have been good even using very early builds. I am going to buy a faster CF card to test since she only has 300x CF cards (and I have 95m/s sony card to test on my 550). I work at a camera shop and I have access to cheap prices on Promaster 1000x 150 MB/s cards (I'm in Australia) so I'm lucky there.
I'll hopefully have time this week to get out and shoot some test shots that aren't just of the inside of my house. Any requests for specific shots or tests?
Also +1 for donating to get 1% a 50D.
I was just thinking the same as you Julian (at the same time lol) my thought was is there anyone that lives close to one of the devs that wouldn't mind lending their body for a while? That is, if it's ok with them :)
No tax for me, no tariffs here, esp on personal packages.
Yep, I'm in the US... also good for only 1 person to have my address. Crappy china adapter would work, doesn't need to be original canon. If not I'll charge the battery, dunno how long it lasts shooting raw. Was OK on 600D/6D.. but then you get stuck with a dead battery wanting to test something.
Quote from: 1% on June 01, 2013, 03:28:29 PM
No tax for me, no tariffs here, esp on personal packages.
Yep, I'm in the US... also good for only 1 person to have my address. Crappy china adapter would work, doesn't need to be original canon. If not I'll charge the battery, dunno how long it lasts shooting raw. Was OK on 600D/6D.. but then you get stuck with a dead battery wanting to test something.
I'm going to pick up a 50D + Battery grip + china battery now! Will send you a PM later. Could probably ship it today.
I'm totally ok on investing some money on it but would like to get some funds back from the other peeps here who would like to invest. So lets see how we work that out - but that will be my problem :)
50D battery is very close to 6D/5D definitely better than 600D
A/C adapter can be had for like $16 on ebay. Whoever buys one between 1% and Julian PM me your paypal and I'll give you the money for it, plus donation towards body :D
First post in this great community.
I'm very happy to join the party. I only regret that I don't have much time these days. I'll be a weekend only poster/tester, but I'm thrilled to get to share the excitement that Magic Lantern has brought to indie's everywhere. Cheers!
Julian H, keep us up to date on how/where to support for the camera you are sending to 1%. 20 bucks in the least I can do to see if we can get even more firepower from the 50D.
I'm staring at 2 boxes that just arrived. 1 has a 50d, the other has a Komp 100x card. Time to read some ML guides, huh? :)
I'll share my results when they are available. Let's have some fun!!!!
(http://www.eoshd.com/comments/uploads/gallery/album_64/med_gallery_20742_64_169231.jpg)
50D (46K clicks)
BG-E2 grip + AA battery tray
1x original battery
1x fake battery
All cables/charger included.
4GB mem card (not so fast but better than nothing)
Just picked this kit up for 350 euro's. My plan is to send this to 1% - Shipping will be 24,30 euro's or 34,30 (if over 2 kg).
I will try to set up a paypal donation page so people who want to donate can pay me back.
Total about $485 - I'll donate the first $50 so about $435 would be welcome... I will send the camera ASAP (before taking donations) and take the financial risk.
Before proceeding I'll go over the details with 1%. If it doesn't work out, no problem, then I have a back-up 50D ;)
Awesome stuff! Yep I'll put in some $$$ when you can confirm paypal etc.
I went out today and took some video @720p 30fps without issue... which is great, my TV only goes to 720p resolution so I've not got a burning desire for anything bigger than that, haha. 30fps is a lot more useful to me, so I was pretty happy it could do that without fuss.
I'm just processing all of the files in Lightroom now, but one thing I've noticed is it seems to be a bit of a mission getting the green/magenta balance on the white balance correct. All said and done though, it looks amazing!
Here's a frame from one of the shots, excuse the colours etc just a quick mash around to get something out the door:
http://iforce.co.nz/i/vduu0y4z.i3f.tif
Raw video or not I'm really happy with my 50D purchase...
Got it from a guy who'd babied it since new with 18k shutter actuations, guard on the screen, genuine canon battery grip, 4 batteries, and three (slow) memory cards for $509NZD (about $400 USD) Which is a crazy good deal for what you get.
Quote from: JulianH on June 01, 2013, 03:30:41 PM
I'm going to pick up a 50D + Battery grip + china battery now! Will send you a PM later. Could probably ship it today.
I'm totally ok on investing some money on it but would like to get some funds back from the other peeps here who would like to invest. So lets see how we work that out - but that will be my problem :)
Julian thank you for taking the initiative to buy 1% a 50D, Everybody all Donations to @JulianH now we getting the ball really rolling. Let us know how you wanna receive payments. Got one question does your 50D heat-up when shooting raw? Did some preliminary test late last night with my slow card 30mb/s after about 10 - 15mins the 50D body gets real warm temperature hovers around 55 degrees from the 39 degrees @ start-up. Does anybody experience the same thing, or is that normal.
Quote from: goldenchild9to5 on June 01, 2013, 04:27:23 PM
Julian thank you for taking the initiative to buy 1% a 50D, Everybody all Donations to @JulianH now we getting the ball really rolling. Let us know how you wanna receive payments. Got one question does your 50D heat-up when shooting raw? Did some preliminary test late last night with my slow card 30mb/s after about 10 - 15mins the 50D body gets real warm temperature hovers around 55 degrees from the 39 degrees @ start-up. Does anybody experience the same thing, or is that normal.
I'll test it but 55C shouldn't be a problem something to be worried about I think. It's normal the camera gets warmer when live view is on because the sensor is powered all the time. Try if you see any difference if you just leave live view on without recording raw - or record h264.
Quote from: JulianH on June 01, 2013, 04:23:18 PM
50D (46K clicks)
BG-E2 grip + AA battery tray
1x original battery
1x fake battery
All cables/charger included.
4GB mem card (not so fast but better than nothing)
Just picked this kit up for 350 euro's. My plan is to send this to 1% - Shipping will be 24,30 euro's or 34,30 (if over 2 kg).
I will try to set up a paypal donation page so people who want to donate can pay me back.
Total about $485 - I'll donate the first $50 so about $435 would be welcome... I will send the camera ASAP (before taking donations) and take the financial risk.
Before proceeding I'll go over the details with 1%. If it doesn't work out, no problem, then I have a back-up 50D ;)
Great initiative Julian! I will be contributing to the donations as well.
Thanks. This is awesome.. will email when I get on the other PC.
Quote from: JulianH on June 01, 2013, 04:29:49 PM
I'll test it but 55C shouldn't be a problem something to be worried about I think. It's normal the camera gets warmer when live view is on because the sensor is powered all the time. Try if you see any difference if you just leave live view on without recording raw - or record h264.
Great idea gonna test today.. let me know your 50D's Temp readings after 15-20 mins of running live view.
Quote from: JulianH on June 01, 2013, 04:23:18 PM
(http://www.eoshd.com/comments/uploads/gallery/album_64/med_gallery_20742_64_169231.jpg)
50D (46K clicks)
BG-E2 grip + AA battery tray
1x original battery
1x fake battery
All cables/charger included.
4GB mem card (not so fast but better than nothing)
Just picked this kit up for 350 euro's. My plan is to send this to 1% - Shipping will be 24,30 euro's or 34,30 (if over 2 kg).
I will try to set up a paypal donation page so people who want to donate can pay me back.
Total about $485 - I'll donate the first $50 so about $435 would be welcome... I will send the camera ASAP (before taking donations) and take the financial risk.
Before proceeding I'll go over the details with 1%. If it doesn't work out, no problem, then I have a back-up 50D ;)
Great finding Julian that's a great price.. was that on ebay?
www.marktplaats.nl - the Dutch eBay :)
Quote from: Roman on June 01, 2013, 04:24:54 PM
Awesome stuff! Yep I'll put in some $$$ when you can confirm paypal etc.
I went out today and took some video @720p 30fps without issue... which is great, my TV only goes to 720p resolution so I've not got a burning desire for anything bigger than that, haha. 30fps is a lot more useful to me, so I was pretty happy it could do that without fuss.
I'm just processing all of the files in Lightroom now, but one thing I've noticed is it seems to be a bit of a mission getting the green/magenta balance on the white balance correct. All said and done though, it looks amazing!
Here's a frame from one of the shots, excuse the colours etc just a quick mash around to get something out the door:
http://iforce.co.nz/i/vduu0y4z.i3f.tif
Raw video or not I'm really happy with my 50D purchase...
Got it from a guy who'd babied it since new with 18k shutter actuations, guard on the screen, genuine canon battery grip, 4 batteries, and three (slow) memory cards for $509NZD (about $400 USD) Which is a crazy good deal for what you get.
Looking good.. Yeah 720p should be good enough & also for quick slowmo's. Yeah let's all donate to @JulianH he just got the 50D body for 1%
I'll let you guys know about the donations when everything is set and talked about. Don't worry about it for now.
Quote from: JulianH on June 01, 2013, 04:59:08 PM
www.marktplaats.nl - the Dutch eBay :)
When I'm buying another 50D body I'm gonna have to contact you. Do they ship to the US?
Quote from: goldenchild9to5 on June 01, 2013, 05:03:57 PM
When I'm buying another 50D body I'm gonna have to contact you. Do they ship to the US?
They don't have buyer protection like eBay, it's really a Dutch thing where people just put stuff up, have a mail or phone conversation and pick up the stuff on location. I also bought a lot of stuff by just paying and hoping it would arrive (never had problems) but that is a risk.
Wouldn't advise this route if you are in the US.
Count me in as well. I'm amazed at how quickly these things are progressing.
I was able to work around the menu a bit, (and I'm looking forward to a 50D starter video) though I'm still having some difficulties with menu options.
I've got several raw files at about 160mb each and a pair of mov files... though I'm not entirely sure how I got one or the other.
Right now I just can't figure out how you are getting the aspect ratio changes... I'm not getting any options. I get one option out of raw and in the movie mode. Also, frame rates are 30p and 2.something-or-another.
Anyway, looking forward to seeing where this is going.
@buildbyflying: press the joystick or the func. button on the menu items for FPS and raw video to change the settings!
Quote from: goldenchild9to5 on June 01, 2013, 10:06:14 AM
Nice... Thanks for sharing great job. At what res did you shoot on? I see a lot of frame drops, and a couple pink frames. What card did you use to shoot?
Shot on a Delkin 32gb 1000x UDMA 7 CF Card.I'm only getting 40mb/s write, but it says it goes up to 80mb/s. I will try a build by GregoryinManhattan today to see if that write speed goes up.
Shot at 1592x720 and upscaled to 1920x1080
Quote from: JulianH on June 01, 2013, 05:18:15 PM
They don't have buyer protection like eBay, it's really a Dutch thing where people just put stuff up, have a mail or phone conversation and pick up the stuff on location. I also bought a lot of stuff by just paying and hoping it would arrive (never had problems) but that is a risk.
Wouldn't advise this route if you are in the US.
Ok I see it's simular to Craigslist than. Was reading one of your earlier post about the BMPCC I also have one on pre-order, it's a different tool than the 50D Longer recording time, Raw & the option to record compress ProRes when needed. Don't think you should cancel your order that's just my opinion.
Quote from: goldenchild9to5 on June 01, 2013, 05:55:50 PM
Ok I see it's simular to Craigslist than. Was reading one of your earlier post about the BMPCC I also have one on pre-order, it's a different tool than the 50D Longer recording time, Raw & the option to record compress ProRes when needed. Don't think you should cancel your order that's just my opinion.
Sure it's different, completely agree. Just for my needs (playing around...) the 50D is enough I think. By the time the BMPCC was announced, it was incredibly amazing to get raw video for $1K. That's what made me pull the trigger. With the 50D in my hands I find it hard to justify spending the $1K. Can always buy one later or wait what BM will bring next NAB ;)
Quote from: JulianH on June 01, 2013, 03:22:11 PM
I'm on a 50D hunt, I'm willing to buy one and ship it to you (from the Netherlands, you're in the US I heard? have to find out how that works with tax.. can ship as gift + low value I suppose). Then after that is done it would be nice if people could pay me some money back.
AC adapter is harder to find I think. I'll try to find a 50D this weekend, keep you guys posted.
This is the one you want. I've been using it constantly for over a year with no problems:
http://www.ebay.com/itm/AC-Adapter-ACK-E2-Power-Supply-for-Canon-EOS-40D-5D-50D-30D-35-350D-DSLR/400379843873?_trksid=p2047675.m1850&_trkparms=aid%3D222002%26algo%3DSIC.FIT%26ao%3D1%26asc%3D11%26meid%3D8072889161934500457%26pid%3D100011%26prg%3D1005%26rk%3D5%26sd%3D120658241461%26 (http://www.ebay.com/itm/AC-Adapter-ACK-E2-Power-Supply-for-Canon-EOS-40D-5D-50D-30D-35-350D-DSLR/400379843873?_trksid=p2047675.m1850&_trkparms=aid%3D222002%26algo%3DSIC.FIT%26ao%3D1%26asc%3D11%26meid%3D8072889161934500457%26pid%3D100011%26prg%3D1005%26rk%3D5%26sd%3D120658241461%26)
Hey Peeps. Real quick, is the latest and greatest build on the 2nd post of this thread? I says its been updated, just wondering. I'll start there and check back to see if anyone has anything better. I checked the "latest builds" thread for ML, but it says that it isn't for RAW video updates. Anywho...
The newest build is here:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
I've asked Andy600 to include it in the topic start.
50D 1k RAW video works.
black point is back where it belongs.
using ufraw-batch or RPP processing after modules/raw_rec/raw2dng
jpegs and links to tiffs and dng below.
RPP default values white balance "as shot" - seems off from the actual colors
(http://50.56.67.113/ml-01June13/rpp-wb-as-shot-color-000035.jpeg)
need white balance auto to get close to scene colors, also here with the Duo profile
(http://50.56.67.113/ml-01June13/rpp-wb-auto-Duo-000035.jpeg)
raw DNG used modules/raw_rec/raw2dng
http://50.56.67.113/ml-01June13/raw2dng-000035.dng
Tiffs
http://50.56.67.113/ml-01June13/rpp-wb-auto-Duo-000035.tiff
http://50.56.67.113/ml-01June13/ufraw-wb-auto-000035.tif
there's a minor bug in raw.c for zoom mode only takes certain skip_left values, otherwise the black point goes wild.
for wild black_point, RPP was able to produce OK tiffs.
at the moment, the framing is not available in zoom mode - only shows the right half of actual shot - use your imagination to set up.
spanning is now working for shots over the 4G limit.
Post a silent pic DNG (silent photo, not video) to find the offsets.
@GregoryOfManhattan: did you make a new build for spanning over 4GB? If so, can you upload it?
Quote from: a1ex on June 01, 2013, 07:05:28 PM
Post a silent pic DNG (silent photo, not video) to find the offsets.
don't i need the lv_rec module for silent pics?
if so, i'll have to do a little more work, as there are several undefined symbols when i try to load lv_rec on 50D.
otherwise, i'm not seeing silent picture mode - let me know if i'm missing something obvious here.
Quote from: a1ex on June 01, 2013, 07:05:28 PM
Post a silent pic DNG (silent photo, not video) to find the offsets.
btw - you are aware of the bug where skip_left cannot have certain values, such as zero.
Silent picture mode isn't on the 50D afaik (at least not in the ML menu's).
Quote from: JulianH on June 01, 2013, 06:11:51 PM
Sure it's different, completely agree. Just for my needs (playing around...) the 50D is enough I think. By the time the BMPCC was announced, it was incredibly amazing to get raw video for $1K. That's what made me pull the trigger. With the 50D in my hands I find it hard to justify spending the $1K. Can always buy one later or wait what BM will bring next NAB ;)
Definitely right you can always get it later or new model.. the 50D is doing Raw right now & does it well why wait.
50D is being sent... I'll find the correct skips unless you beat me to it. Also raw histo, etc. 50D seems to need a bit of work for normal ML stuff too. I think nobody had one to actively develop.
Quote from: JulianH on June 01, 2013, 06:45:17 PM
The newest build is here:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
I've asked Andy600 to include it in the topic start.
Thanks JulianH! ML loaded, just getting used to it...I'll get this latest version and go from there.
1% what is needed for silent pics on 50D?
some skip values should be zero, but that throws other errors with black points gone wild.
at the moment, putting in inaccurate skip values leads to better results.
do other camera have proper framing in zoom mode?
at the moment, 50D live view is only showing right half of actual frame.
For silent pics? All the stubs and LV edmac.
How does raw_rec work without silent pics?
Skips can be 0 for some stuff, you have to have skips on either top or left.
600D:
#ifdef CONFIG_600D
// raw_info.height = mv1080crop ? 1042 : zoom ? 1100 : mv720 ? 714 : 1176;
skip_top = 26;
skip_left = zoom ? 0 : 152;
skip_right = zoom ? 0 : 2;
#endif
Skip is 0 in zoom mode.
Quote from: 1% on June 01, 2013, 07:49:10 PM
50D is being sent... I'll find the correct skips unless you beat me to it. Also raw histo, etc. 50D seems to need a bit of work for normal ML stuff too. I think nobody had one to actively develop.
Nice.. 1% make the 50D shine we got your support whatever you need.
Quote from: GregoryOfManhattan on June 01, 2013, 07:58:25 PM
1% what is needed for silent pics on 50D?
some skip values should be zero, but that throws other errors with black points gone wild.
at the moment, putting in inaccurate skip values leads to better results.
do other camera have proper framing in zoom mode?
at the moment, 50D live view is only showing right half of actual frame.
I see you working none stop Gregory, thanks for all your help developing. I started testing your build but don't have my fast card yet only getting a few seconds of record time.
Hey guy's how come whenever I shoot Raw my shots are all @ 30fps I put in on FPS Override but still comes out as 30fps, I'm definitely doing something wrong. Any help would be appreciated. Also is it possible to over over expose Raw to the point of no recovery? I have one interior shot looking out a window looks totally blown out, and when I try to recover detail can't get nothing back.
Yep, will be fun... btw pink frames on 600D were found to be from CPU usage form global draw. Check cpu usage... dunno if 50D has show cpu in debug menu.
And yes, you can over/under the raw to where nothing will help.
Quote from: 1% on June 01, 2013, 09:36:39 PM
Yep, will be fun... btw pink frames on 600D were found to be from CPU usage form global draw. Check cpu usage... dunno if 50D has show cpu in debug menu.
And yes, you can over/under the raw to where nothing will help.
Got ya will be more careful with my highlights. Gonna check if 50D has Global draw in menu & I'll check back with you.
Quote from: 1% on June 01, 2013, 09:36:39 PM
Yep, will be fun... btw pink frames on 600D were found to be from CPU usage form global draw. Check cpu usage... dunno if 50D has show cpu in debug menu.
And yes, you can over/under the raw to where nothing will help.
How do you check your Shutter Count in ML, wanna know if it has a low Shutter count like described in the listing.
I hope it has global draw... cpu usage and shutter count should be in the debug menu. If they're not will have to find out why.
Quote from: 1% on June 01, 2013, 09:52:15 PM
I hope it has global draw... cpu usage and shutter count should be in the debug menu. If they're not will have to find out why.
Yes, yes and yes. It's all there.
Quote from: 1% on June 01, 2013, 09:52:15 PM
I hope it has global draw... cpu usage and shutter count should be in the debug menu. If they're not will have to find out why.
Found it yes it has CPU Usage and I saw the Shutter Count 18K. I couldn't find global draw.. What does that mean "Scripts Dir Missing" it shows up every time I boot ML.
I hate to post a noob-y question but I haven't found a definite answer.
1. When I record to my Komputerbay cards, the camera stops after 4gbs is reached. How does one enable spanning, even on FAT32?
2. I too get the "This ain't a raw LV rec File" error when using the raw2dng app. Whats the work around on OSX?
Quote from: goldenchild9to5 on June 01, 2013, 10:07:19 PM
Found it yes it has CPU Usage and I saw the Shutter Count 18K. I couldn't find global draw.. What does that mean "Scripts Dir Missing" it shows up every time I boot ML.
Just make a new (empty) folder in the ML folder called 'scripts' and that will be fixed :)
Global draw is on the 2nd menu on the left, top option. Probably best to keep it turned off while recording raw for now.
@artiswar: do you use the latest build? (check first post). What if you try lower resolutions, does it span? It might just run out of buffer at 4GB or something...
Quote from: JulianH on June 01, 2013, 10:13:51 PM
Just make a new (empty) folder in the ML folder called 'scripts' and that will be fixed :)
Global draw is on the 2nd menu on the left, top option. Probably best to keep it turned off while recording raw for now.
@artiswar: do you use the latest build? (check first post). What if you try lower resolutions, does it span? It might just run out of buffer at 4GB or something...
Latest build installed. I do receive the "Scripts dir missing" error at boot. When it reaches just under 4gb it stops, even at lower resolutions. Perhaps a good format would help.
Quote from: JulianH on June 01, 2013, 10:13:51 PM
Just make a new (empty) folder in the ML folder called 'scripts' and that will be fixed :)
Global draw is on the 2nd menu on the left, top option. Probably best to keep it turned off while recording raw for now.
@artiswar: do you use the latest build? (check first post). What if you try lower resolutions, does it span? It might just run out of buffer at 4GB or something...
So Julian your saying not to use Gregory's lastest build yet. Did you revert back to the build from the 1st page? it's more stable right, gonna try in a couple minutes letting my battery charge. Tell you the truth I think I might need to invest on a battery grip, and whole bunch of batteries... think mines gave me around 30 - 35 minutes continuously staying on. It's not bad but on a real shoot gonna need about 3 extras. Thanks for the tip about Global draw. One last question even when I put the 24fps override it still spits out 30fps not sure what I'm doing wrong here. Every time I load it in After Affects it shows as 30fps
Yeah my global draw setting what On. That's why all those overlays were displaying on my screen that's probably why I coudn't record for longer time.
When you load the footage into after effects, click right on" interpret footage" and then "Main ...". In the window set the assumed framerate to 24 or 23,976 depending on which framerate you actually shot in camera
Quote from: goldenchild9to5 on June 01, 2013, 10:34:00 PM
So Julian your saying not to use Gregory's lastest build yet. Did you revert back to the build from the 1st page? it's more stable right, gonna try in a couple minutes letting my battery charge. Tell you the truth I think I might need to invest on a battery grip, and whole bunch of batteries... think mines gave me around 30 - 35 minutes continuously staying on. It's not bad but on a real shoot gonna need about 3 extras. Thanks for the tip about Global draw. One last question even when I put the 24fps override it still spits out 30fps not sure what I'm doing wrong here. Every time I load it in After Affects it shows as 30fps
Gregory's build is added to the first post by Andy600. It's the best built I've used and it's stable for me as long as I don't do anything weird/experimental (playing back a file shot in 5x zoom mode makes the camera crash). Just recording raw works like a charm.
I don't know what you are doing wrong with your FPS override, but you are doing something wrong, it works fine here. Press the func. button when the menu item is selected for more options and set it to exact fps.
Okay, successfully recorded at 5gb file on my third go. First time around I got to around 1110 frames when the buffer filled. Now recording stopped at 5gbs with a frame skip. I'm assuming this is because I'm using the highest resolution. The buffer just seems rather inconsistent to me.
Quote from: JulianH on June 01, 2013, 10:48:14 PM
Gregory's build is added to the first post by Andy600. It's the best built I've used and it's stable for me as long as I don't do anything weird/experimental (playing back a file shot in 5x zoom mode makes the camera crash). Just recording raw works like a charm.
I don't know what you are doing wrong with your FPS override, but you are doing something wrong, it works fine here. Press the func. button when the menu item is selected for more options and set it to exact fps.
Just got my KomputerBay 64GB card ;D now it's time to put this baby to the test. Gonna download from front page. Any special formatting for the CF card, or just plain in camera formatting?
Quote from: artiswar on June 01, 2013, 10:58:04 PM
Okay, successfully recorded at 5gb file on my third go. First time around I got to around 1110 frames when the buffer filled. Now recording stopped at 5gbs with a frame skip. I'm assuming this is because I'm using the highest resolution. The buffer just seems rather inconsistent to me.
Nice..
Quote from: artiswar on June 01, 2013, 10:58:04 PM
Okay, successfully recorded at 5gb file on my third go. First time around I got to around 1110 frames when the buffer filled. Now recording stopped at 5gbs with a frame skip. I'm assuming this is because I'm using the highest resolution. The buffer just seems rather inconsistent to me.
What card and what exact resolution? The first clip recorded in raw, when you just turn on the camera and load the raw module, for me it usually fills the buffer faster. Just try a few consecutive runs and you'll get more stable results.
Quote from: goldenchild9to5 on June 01, 2013, 11:10:05 PM
Just got my KomputerBay 64GB card ;D now it's time to put this baby to the test. Gonna download from front page. Any special formatting for the CF card, or just plain in camera formatting?
Start with plain format, works for me. The card should be plenty fast for the 50D. Good luck!
Quote from: goldenchild9to5 on June 01, 2013, 10:34:00 PM
So Julian your saying not to use Gregory's lastest build yet. Did you revert back to the build from the 1st page? it's more stable right, gonna try in a couple minutes letting my battery charge. Tell you the truth I think I might need to invest on a battery grip, and whole bunch of batteries... think mines gave me around 30 - 35 minutes continuously staying on. It's not bad but on a real shoot gonna need about 3 extras. Thanks for the tip about Global draw. One last question even when I put the 24fps override it still spits out 30fps not sure what I'm doing wrong here. Every time I load it in After Affects it shows as 30fps
After Effects is showing 30fps because that's what the default After Effects preferences are when importing an image sequence. You need to go into preferences under the "edit" tab to change this setting to your desired default. On the other hand, you can always right click on the image sequence in the project window after you've imported it, and select "interpret". A new window will open that allows you to change the fps.
Hope this helps.
Quote from: pinger007 on June 01, 2013, 11:38:03 PM
After Effects is showing 30fps because that's what the default After Effects preferences are when importing an image sequence. You need to go into preferences under the "edit" tab to change this setting to your desired default. On the other hand, you can always right click on the image sequence in the project window after you've imported it, and select "interpret". A new window will open that allows you to change the fps.
Hope this helps.
Thank you soo much great explanation of what's really going on. I'm a noob to After Effects, more of a Premiere Pro avid.
Quote from: JulianH on June 01, 2013, 11:27:22 PM
What card and what exact resolution? The first clip recorded in raw, when you just turn on the camera and load the raw module, for me it usually fills the buffer faster. Just try a few consecutive runs and you'll get more stable results.
Start with plain format, works for me. The card should be plenty fast for the 50D. Good luck!
No problem gonna do a plain in camera format..
Can you guys do some speed tests like I did? Curious to see if 1000X cards work faster than my 90MB/s.
Below I quote my previous results. Just ran some tests again, results vary sometimes... added them.
Just shoot at those resolutions a few times till the buffer fills. Make sure you're in 24 fps (it blinks on the screen if it works: 24 fps override), global draw off and hacked mode on (not sure if this makes a big difference but I used it).
Quote
Resolution test with GregoryOfManhattan's build, using Hacked mode.
Sandisk 32GB 90MB/s CF
3:2 @ 1592x1062 ~ 135 frames ~ 200 frames
5:3 @ 1952x956 ~ 270 frames ~ 280 frames
16:9 @ 1592x 896 ~ 480 frames ~ 440 frames
1.85:1 @ 1592x860 ~ 850 frames ~ 950 frames max.
2:1 @ 1592x796 - No skipping!
Quote from: JulianH on June 01, 2013, 11:44:57 PM
Can you guys do some speed tests like I did? Curious to see if 1000X cards work faster than my 90MB/s.
Below I quote my previous results. Just ran some tests again, results vary sometimes... added them.
Just shoot at those resolutions a few times till the buffer fills. Make sure you're in 24 fps (it blinks on the screen if it works: 24 fps override), global draw off and hacked mode on (not sure if this makes a big difference but I used it).
Will test in another 30 minutes battery almost finish charging. I'll post all results.. res 1592x1062 is crop mode right? so new to all of this.
Quote from: JulianH on June 01, 2013, 11:44:57 PM
Can you guys do some speed tests like I did? Curious to see if 1000X cards work faster than my 90MB/s.
Below I quote my previous results. Just ran some tests again, results vary sometimes... added them.
Just shoot at those resolutions a few times till the buffer fills. Make sure you're in 24 fps (it blinks on the screen if it works: 24 fps override), global draw off and hacked mode on (not sure if this makes a big difference but I used it).
I'm seeing the same numbers essentially. I skipped 2:1 and went for 2.20:1, though. 5 and 10 gb clips recorded successfully.
Quote from: JulianH on June 01, 2013, 11:44:57 PM
Can you guys do some speed tests like I did? Curious to see if 1000X cards work faster than my 90MB/s.
Below I quote my previous results. Just ran some tests again, results vary sometimes... added them.
Just shoot at those resolutions a few times till the buffer fills. Make sure you're in 24 fps (it blinks on the screen if it works: 24 fps override), global draw off and hacked mode on (not sure if this makes a big difference but I used it).
Where do you find the hacked mode? can't see it.
Might be a bit off-topic, but has a solution for the pink colorcast been found?
Thanks.
Is the Lexar 1000x overkill for the 50D? I'm thinking about getting the Komputerbay 32GB/64GB card but unsure about the cards not functioning after a while.
Quote from: JulianH on May 29, 2013, 12:50:49 AM
Fixed the frame skipping on my previous anamorphic video. The image sequences were imported as 25 fps and my project was 24 fps. Simple as that. Re-uploaded the correct file:
Julian, by the way, what is the wider lens that you can use with the Kowa B&H 2x anamorphic before it vignettes?.......
Quote from: ashtrai on June 02, 2013, 12:22:24 AM
Is the Lexar 1000x overkill for the 50D? I'm thinking about getting the Komputerbay 32GB/64GB card but unsure about the cards not functioning after a while.
This question will be up in the air for a while.
Juilan, any idea why I would be getting that "aint a LV raw file" with something around 3gbs?
Footer is missing... check with a hex editor for RAWM at the end.
Probably 1000x cards will be overkill.. look up the max supported UDMA mode and see.
I am about to buy a CF card tomorrow for my new 50D. Help me choose between Komputerbay 64gb1000x or 128gb600x. Are there any issues with running ML on a 128gb card? Is 600x enough? I think the 50D is UDMA6 compatible, so is there going to be any benefit from 1000x card?
Okie dokie. No images worth sharing at this time, but here's an update and some questions.
1. Battery drain: I'm burning through a battery in mere minutes. I'll bet this means something....and probably not good. (Not that it's a problem for everyone else, or that they should worry....just likely a flag that I did something wrong in the install.
2. It's showing on the camera as 29.97 fps. I'm aware that RAW mode is not video mode, two different things. Just wondering.
3. I'm only getting 145 frames.
Also, I'll read through this to see where the frame aspect ratio is, because I haven't found it in my adventures so far. I'll read through the thread, someone else has likely asked....
OK. So the 29.97 fps is guess might be a statement, not a setting:
"Write speed needed: 71.3 MB/s at 29.985 fps" That said, I'm not seeing where to configure the fps or the aspect ratio. No biggie, I'll keep reading, lol.
Try pressing the 'func' button when you are on the menu item for fps override or raw video ;)
My question is off topic, but I can't find a better place to ask it. With the addition of RAW video on the 50D, the 50D is a tool I might just add to my kit. The only issue is the line skipping causing moire and aliasing artifacts. I know Mosaic Engineering makes some really effective video aliasing filters (VAF) for many of the Canon and Nikon DSLR's. Since the 50D was never intended to do video Mosaic Engineering doesn't make one for the 50D. I see some of their VAF's work on multiple camera's like the same one works on the T2i, T3i, and T4i. I was wondering if anyone knows if one of the other VAF's work on the 50D? For example does the VAF for the 60D also fit the 50D?
Probably it would fit in the 50D if it does in the 60D. But they are designed for 1080p video. They don't produce nice results in 720P for example, so most probably the 50D's raw resolution(s) will be trouble.
Quote from: JulianH on June 02, 2013, 01:30:18 AM
Try pressing the 'func' button when you are on the menu item for fps override or raw video ;)
Thanks Buddy! That helped a lot. Changed resolution, and I got LOTS of frames....lol. I stopped after a while.
This one I think means something, lol. Is there some reason that I can't run any of the benchmarking menu items? They all "blow up", it locks up the camera. Is anyone else having this problem?
Camera R/W Bench mark. That one crashes for me. It gets through the Write, Then the Read, then it stops. I have considered that what it does next is actually a part of the test, but it goes 'blank'. That doesn't seem correct. More on this later.
Benchmarks have been weird for me as well. Don't seem to end correctly.
I thought that maybe it was because Live View was auto turning off after 1 min. Sure enough, that was the setting, however, it still locked my camera. So, the image on the screen in Live View just stopped/froze. Had to remove battery. Indeed, I think this one is official from me.
On this build from "Gregory of Manhattan", May 28th build, the "Benchmark" for "Camera R/W" is locking up after completing 1 of 9 bench marks.
Is anyone else having this problem? Cheers Peeps!
ps....I have a Komputar 1000x 64GB card. Camera only has 23K actuations.
Quote from: JulianH on June 02, 2013, 02:01:41 AM
Benchmarks have been weird for me as well. Don't seem to end correctly.
Thanks JulianH. Confirmed. Do we just email him to have him a heads-up, or is he reading through this thread on a regular basis? Anywho....
He is reading and I wouldn't be to worried about a benchmark not working. Just check what speeds are reliable when recording. See my results posted a few posts back.
Quote from: JulianH on June 01, 2013, 11:44:57 PM
Can you guys do some speed tests like I did? Curious to see if 1000X cards work faster than my 90MB/s.
Below I quote my previous results. Just ran some tests again, results vary sometimes... added them.
Just shoot at those resolutions a few times till the buffer fills. Make sure you're in 24 fps (it blinks on the screen if it works: 24 fps override), global draw off and hacked mode on (not sure if this makes a big difference but I used it).
Hey julian I'm back with some results still not too familiar with the ML but I tried a couple shots @ different res..
1592 x 960 @ 30FPS ~ 248 frames (Skip)
1592 x 960 @ 24FPS ~ 1576 frames (Skip)
1592 x 720 @ 24FPS ~ 2101 frames (4GB Limit) Note: (First recording stopped midway second try was good to go)
1592 x 540 @ 24FPS ~ 2800 frames (4GB Limit) everytime
Gonna do some more test tonight but so far that what I got. Also a couple times @ 1592 x 720 @ 24FPS it got to two (**_) and showed in red 7 Frame skipped, but when I convert using Raw2Dng it it says 1 frame skipped. Trying to understand the whole process of recording and converting.. the good & bad. Hope that help to shed some light on the KomputerBay 64GB 1000X card, but from my experience it seems you need to shoot minimum of two test shots before everything runs smooth. It might be just my card but that's what I got so far from the card, now time to go learn the post production side of things 8) any ideas on how to convert to ProRes 4444 After Affects done seem to have that option from Raw.
On a cleaned Komputerbay 64GB card, I did a fresh install of ML and then the newest 50D raw build (5/28) - just to be sure I wasn't introducing any problems with cards that had been used for raw in my 5DMiii.
Still - I don't get write rates anything like what Julian and others seem to be achieving. Even 1280x720 writes at about 35-40 Mb/s and I start dropping frames after about 400 or so. Same result whether or not I turn on Hacked mode, I have selected small jpg for still image size, turned off Global Draw.... still I seem to be missing something.
I'll keep trying and reading the forum and other resources to learn - but I'll appreciate any tips about other things to test or try.
Thanks
Quote from: goldenchild9to5 on June 02, 2013, 02:25:10 AM
any ideas on how to convert to ProRes 4444 After Affects done seem to have that option from Raw.
Assuming you have prores codecs installed on your computer, then it's just a matter of exporting your comp as a quicktime. In the quicktime options, there's an option for you to select a format: prores, animation, etc. I prefer the Avid DNxHD codec personally. :)
Is there a way to have the depth of field preview selected automatically while shooting raw video? Right now I'm pushing the live view button to start recording, then I press and hold the depth of field preview button until I'm done with the shot. It's a pain, but that's what I have to do to if I don't want to shoot wide open. Is there a work around, or do I just have to adapt my Nikon lenses and use their manual aperture?
Thanks.
Quote from: JulianH on June 02, 2013, 01:44:28 AM
Probably it would fit in the 50D if it does in the 60D. But they are designed for 1080p video. They don't produce nice results in 720P for example, so most probably the 50D's raw resolution(s) will be trouble.
This is true, they are designed for 1080p, all except the one for the Nikon D800 anyway. That one is recommended for both 1080p and 720p. It would still be good to know if one will fit and even better if someone could test it.
Quote from: dhallowell19 on June 02, 2013, 03:39:13 AM
On a cleaned Komputerbay 64GB card, I did a fresh install of ML and then the newest 50D raw build (5/28) - just to be sure I wasn't introducing any problems with cards that had been used for raw in my 5DMiii.
Still - I don't get write rates anything like what Julian and others seem to be achieving. Even 1280x720 writes at about 35-40 Mb/s and I start dropping frames after about 400 or so. Same result whether or not I turn on Hacked mode, I have selected small jpg for still image size, turned off Global Draw.... still I seem to be missing something.
I'll keep trying and reading the forum and other resources to learn - but I'll appreciate any tips about other things to test or try.
Thanks
Man sorry your having that much problems with your 50D Since we have the same CF cards (KomputerBay 64GB) here is what I did to get it running good enough but not perfect first of all don't use the may 28th build yet it's not final.
Step 1: Download my complete folder hack here: http://limelinx.com/ca42c (everything is included for hack in folder)
Step 2: Format your KomputerBay card in camera ( should be in first setting option on the 50D Menu ) Takes just a couple seconds
Step 3: Unzip folder from download link and drag all files to your CF card directory (Leave everything else intact just copy and paste.
Step 4: Insert card back in camera go to your firmware update which should be the Third option on your 50D (click on Firmware and update let magic lantern do it's thing should say Success in green should know about this process since your hack your camera already.
Step 5: Global Draw off, The Hack Mode I still can't find that myself but I heard it should be on, than go through your regular routine Raw rec on, FPS Override set to 24FPS and I think that should be it.
One last thing shoot two continuous shots before you really shoot cause for some reason the first two are like a warm up enjoy 8)
If your still having trouble let me know I'll here to help.
GOD Bless
Quote from: dhallowell19 on June 02, 2013, 03:39:13 AM
On a cleaned Komputerbay 64GB card, I did a fresh install of ML and then the newest 50D raw build (5/28) - just to be sure I wasn't introducing any problems with cards that had been used for raw in my 5DMiii.
Still - I don't get write rates anything like what Julian and others seem to be achieving. Even 1280x720 writes at about 35-40 Mb/s and I start dropping frames after about 400 or so. Same result whether or not I turn on Hacked mode, I have selected small jpg for still image size, turned off Global Draw.... still I seem to be missing something.
I'll keep trying and reading the forum and other resources to learn - but I'll appreciate any tips about other things to test or try.
Thanks
You selected Small JPG myself I'm using Large JPG. Try to set it on Large JPG which is the first one & put Raw off ( --- )
Quote from: pinger007 on June 02, 2013, 03:41:35 AM
Assuming you have prores codecs installed on your computer, then it's just a matter of exporting your comp as a quicktime. In the quicktime options, there's an option for you to select a format: prores, animation, etc. I prefer the Avid DNxHD codec personally. :)
It only has Quicktime Uncompress 10bit 422, I'm looking for Quicktime 4444 it's no where to be found.
Quote from: pinger007 on June 02, 2013, 03:48:25 AM
Is there a way to have the depth of field preview selected automatically while shooting raw video? Right now I'm pushing the live view button to start recording, then I press and hold the depth of field preview button until I'm done with the shot. It's a pain, but that's what I have to do to if I don't want to shoot wide open. Is there a work around, or do I just have to adapt my Nikon lenses and use their manual aperture?
Thanks.
Manual lenses all the way Nikkor, Nikons are real filmic and sharp @ the same time I have a pair. Also your using the May 28 build right use this build instead it's more stable http://limelinx.com/ca42c Gregory is ironing out all the glitches, so glad that his taking time to work on it.
That's right. I'm using the May 28th build right now. What does the new build offer over the old build? Will the electronic aperture on the ef lenses engage during the live view shooting?
Also, what adapters do you recommend for Nikon glass? I need something that offers a secure fit (I use a follow focus and can't have any shifting going on). I also don't want a permanent solution since I still use my Nikons for my family of GH2s. :) Finally, will I need an adapter for each nikkor I own (for convenience), or will one adapter be enough?
I was reading something the other day, about older manual lenses giving lower contrast than those designed for DSLRs - as the sensor is more reflective than film is, you get reflections going back up and down the lense reflecting off the elements back to the sensor again.
Where as lenses designed for digital cameras have elements designed to reduce this reflection.
In saying this, previously I've been an advocate of using kit lenses for filming - as I've not been able to tell the difference, and usually lose out on image stabilisation etc.
However with raw on 50D, the difference between my Samyang 35mm and the kit lenses is like night and day. Good glass is finally worth while for video, rather than having the image put though a blender before ending up on the memory card.
Seems like someone was asking about highlight recovery. Make no mistake people, ....this is RAW. If you are wondering about highlight recovery, wonder no more. YES...this is out of focus. I was in a hurry. The only purpose of posting these two images is to help anyone wondering about highlight recovery. Enjoy. Thanks Magic Lantern!!! :)
(http://farm9.staticflickr.com/8397/8920175072_3cdb4bbb87_o.jpg)
(http://farm3.staticflickr.com/2842/8920174844_e854227ef7_o.jpg)
Quote from: pinger007 on June 02, 2013, 03:48:25 AM
Is there a way to have the depth of field preview selected automatically while shooting raw video?
I believe under one of the ML menus there is a 'sticky DOF preview' button - so you can press the button and it holds it down until you press it again. I havent tried it on the 50D yet, but have just been re-reading the ML user guide.
How easy is it to change the record start button? At the moment with d.o.f. sticky on the record button doesn't work, for me at least.
I never saw a dof sticky option in the menus... I'll give it another look once my battery charges. Hopefully I can find it and that it works. On another note, the Raw hack really chews up the batteries... I've got another two and a battery grip on order. :P
One more example of highlight recovery. Enjoy!
(http://farm6.staticflickr.com/5445/8919875957_d5c6b4d421_o.jpg)
(http://farm4.staticflickr.com/3748/8919875721_50d4e5b268_o.jpg)
Is that with auto white balance?
I find it comes out really green looking when I use auto white balance in Lightroom... Have to ramp the Magenta slider right over in some cases.
(The above 'after' images look pretty green to my eyes)
Quote from: Roman on June 02, 2013, 07:43:39 AM
Is that with auto white balance?
I find it comes out really green looking when I use auto white balance in Lightroom... Have to ramp the Magenta slider right over in some cases.
(The above 'after' images look pretty green to my eyes)
True Roman. (Lightroom) ...and I agree. Cheers!
Quote from: goldenchild9to5 on June 02, 2013, 04:27:07 AMAlso your using the May 28 build right use this build instead it's more stable http://limelinx.com/ca42c Gregory is ironing out all the glitches, so glad that his taking time to work on it.
This is the 23-05 build you are linking. Why?
I've been using 28-05 by GregoryOfManhattan and it is definitely the best so far. More options, better speeds. I don't have stability issues.
I'd strongly suggest this one. Download here: http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
I'm still working on the basic install/settings video guide. Hope to finish it today.
I wanted to see how the 14-Bit Raw stacked up against the native Canon h264 video codec on the 50d.
The difference is NIGHT AND DAY.
35mm f1.4L
Resolution: 1280x720 h.264 vs. 1280x720 14Bit Raw
14Bit Raw converted to ProRes 422
Upscaled to 1080p for optimal viewing on YouTube.
Cool vid, really shows the difference in both sharpness but especially the colors/dynamics. A bit offtopic: does one know what's the best upscaling to 1080p method?
I still need help over those cf cards. Komputerbay 128gb 1000x vs. 64gb 600x vs Kingston 32gb 1000x. What should I get?
the komputerbay cards have a nice performance / price. I heard the 128gb one is slower then the 64gb. (I own one). Try one 64gb first and then buy another one if you need the space
Quote from: johansugarev on June 02, 2013, 11:44:52 AM
I still need help over those cf cards. Komputerbay 128gb 1000x vs. 64gb 600x vs Kingston 32gb 1000x. What should I get?
It's trial and error. 600x should be enough, as my Sandisk 90MB/s (600x) is getting the max speed of the 50D (right now, maybe the future will bring more?). 64GB 1000x will be safe. 128GB 600x should be enough, but we don't know for sure until someone actually tries... so go ahead ;)
Quote from: johansugarev on June 02, 2013, 11:44:52 AM
I still need help over those cf cards. Komputerbay 128gb 1000x vs. 64gb 600x vs Kingston 32gb 1000x. What should I get?
There is a thread regarding CF cards for RAW recording here http://www.magiclantern.fm/forum/index.php?topic=5391.0 (http://www.magiclantern.fm/forum/index.php?topic=5391.0)
Loads of info on many cards there. Not camera specific, but still lots to get stuck into in terms of speeds / reliability.
Been using ML on 7D for awhile. Love it. Currently waiting on 50D. ;D Going to need some faster cards myself but Amazon won't ship KomputerBay 64GB 1000x Card to New Zealand. :'( Currently talking with them to see if I can get that changed.
-Off topic for here...but anyone got any idea about where 7D RAW? All I've found is "
7D has dual processors so its development will be different. Not working right now." UPDATE: Just found this re 7D :
Quote from: g3gg0 on May 16, 2013, 01:50:42 AM
its not that easy.
the slave processor ML runs on, doesnt have access to the raw data stream as it seems :(
@ JulianH let us know when Paypal is set up for 50D body donations.
THANKS TO EVERYONE FOR MAKING ALL THIS HAPPEN. Feel like a kid before Christmas waiting for the 50D in the mail.
Thanks @goldenchild9to5 - I used the steps that you suggested (reformatting the card, backing to a build before 5/28, etc).
That changed things for the better -- now 1280x720 starts off great, just one star in the buffer, maybe 2....runs for 10-20 seconds, and then just announces 'stopped automagically' It's not even close to skipping frames - so I'm sure it's another newbie blind spot on my part.
I'll poke around to learn more about that - but at least the chance for some stable 1280x720 raw shooting is getting closer.
Thanks again for the help - I'll watch for any more tips.
Best
(http://www.eoshd.com/comments/uploads/gallery/album_64/med_gallery_20742_64_1835.jpg)
Since ML isn't taking donations, I have taken the initiative to buy a 50D + Battery grip + batteries + 4GB CF for a good price. I've shipped it to 1% today.
I hope we can split the costs. If you want to contribute send me a PM and I'll give you the details. Thanks in advance :)
*respect* 8) Let's hope 1% can do the magic :) *PM*ed
Quote from: JulianH on May 25, 2013, 05:39:59 PM
Managed to trade my old 5D for the 50D and cash :)
I got raw recording working. Did a benchmark of Sandisk Extreme Pro 32GB 95MB/s in live view, but it doesn't seem to close the benchmark properly. I can't seem to find a log of bmp of the results. Where should it be?
Maximum seems to be around 50MB/s for continuous recording (with my card).
My results (how can I determine exactly at which frame skipping starts?):
Shot at 24 fps (didn't find a setting for 23.975..)
1592x1062 - frame skipping after about 50 frames (67.7MB/s)
1592x840 - frame skipping after about 480 frames (53.5MB/s)
1592x720 - no frame skipping (44.3MB/s)
1320x1062 - frame skipping after about 300 frames (56.1MB/s)
1320x960 - frame skipping after about 1200 frames (50.7MB/s)
1320x840 - no frame skipping (44.3MB/s)
1280x1062 - frame skipping after about 250 frames (54.4 MB/s)
1280x960 - no frame skipping (49.2MB/s)
-Waiting for 50D in the post- looking at card options. Just looking at these speeds against the benchmark of my current cards, Sandisk Extreme 60Mb/s - 8/16/32GB. The 16 and 32 GB write at 44.5 Mb/s. Lowest speed from Julian is 44.3 MB/s at 1320 x 840. I'm thinking / hoping to be able to record something like 1280 x 720 on these cards just to get me going. Still crossing fingers Komputer Bay get back to me about shipping to NZ to make the most of this amazing breakthrough.
Has anyone had any success with 60MB/s cards and lower resolutions? Or should I try and find bigger and faster card (that ships to NZ) ASAP???
Advertised speeds are maximum read speeds. Write speeds are typically lower.
Just benchmarked my cards with CrystalDiskMark in the USB 3 card reader:
Sandisk 32GB 90MB/s CF: 96MB/s read - 66MB/s write
Sandisk 4GB 30MB/s CF: 29MB/s read - 24MB/s write
The write speed is the important one!
My sandisk extreme 60MB/s seem to be writing at 44.5 MB/s for both 16GB and 32BG. 8BG was 40.9. Hope this gets me some RAW footage to play with. Even if its 1280 x 720 I'd be happy!
Hi JulianH,
Quote from: JulianH on June 02, 2013, 04:12:13 PM
Advertised speeds are maximum read speeds. Write speeds are typically lower.
Just benchmarked my cards with CrystalDiskMark in the USB 3 card reader: [...]
which reader are you using? I tried one from Transcend on my Mac running OSX 10.7.5 but the DOS file system could not be mounted. ExFAT worked on the Mac but not on the 50D.
Regards,
Andrew
Quote from: HHL on June 02, 2013, 07:19:56 AM
One more example of highlight recovery. Enjoy!
(http://farm6.staticflickr.com/5445/8919875957_d5c6b4d421_o.jpg)
(http://farm4.staticflickr.com/3748/8919875721_50d4e5b268_o.jpg)
Amazing colors grade on those shots.
Quote from: JulianH on June 02, 2013, 10:18:04 AM
This is the 23-05 build you are linking. Why?
I've been using 28-05 by GregoryOfManhattan and it is definitely the best so far. More options, better speeds. I don't have stability issues.
I'd strongly suggest this one. Download here: http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
I'm still working on the basic install/settings video guide. Hope to finish it today.
In one of your post you said not to use the May 28th build guess I was reading wrong than, Gonna try out the new build today. For some reason I'm getting a lot noise in almost all ISO settings don't know what I'm doing wrong. Is it a setting that's boosting the noise in camera.
Quote from: Fioritura on June 02, 2013, 04:23:47 PM
Hi JulianH,
which reader are you using? I tried one from Transcend on my Mac running OSX 10.7.5 but the DOS file system could not be mounted. ExFAT worked on the Mac but not on the 50D.
Regards,
Andrew
Just a basic HAMA USB 3.0 reader. On Windows, don't know how that works for MAC. Should be no problem, card reader = card reader... it's just usb... as far as I know.
Quote from: John-Jo on June 02, 2013, 04:21:12 PM
My sandisk extreme 60MB/s seem to be writing at 44.5 MB/s for both 16GB and 32BG. 8BG was 40.9. Hope this gets me some RAW footage to play with. Even if its 1280 x 720 I'd be happy!
1280x720p should be safe!
@Goldenchild: what mode are you shooting at? M? What lenses? (manual aperture?) what iso's? upload some DNG's! just send them to yourself with www.wetransfer.com and paste the download link here.
Quote from: dhallowell19 on June 02, 2013, 12:49:49 PM
Thanks @goldenchild9to5 - I used the steps that you suggested (reformatting the card, backing to a build before 5/28, etc).
That changed things for the better -- now 1280x720 starts off great, just one star in the buffer, maybe 2....runs for 10-20 seconds, and then just announces 'stopped automagically' It's not even close to skipping frames - so I'm sure it's another newbie blind spot on my part.
I'll poke around to learn more about that - but at least the chance for some stable 1280x720 raw shooting is getting closer.
Thanks again for the help - I'll watch for any more tips.
Best
Great to hear.. Gonna try the new build & see what results I get than I'll send you all my steps using the KomputerBay 64GB card. Also one more thing I think you should try to reinstall Canon's 1.0.9 firmware on your camera to give it a fresh start, than put all settings to default there is a button for that. Download here: http://limelinx.com/ds6cw
Quote from: JulianH on June 02, 2013, 05:42:54 PM
Just a basic HAMA USB 3.0 reader. On Windows, don't know how that works for MAC. Should be no problem, card reader = card reader... it's just usb... as far as I know.
1280x720p should be safe!
@Goldenchild: what mode are you shooting at? M? What lenses? (manual aperture?) what iso's? upload some DNG's! just send them to yourself with www.wetransfer.com and paste the download link here.
Thanks for reply julian I'm shooting in "M" mode, using a manual Nikon 50mm f1.8. Tried ISO's 100 - 800 all seem to have noise. Gonna send you over some DNG's ASAP.
Check your histogram, if you underexpose noise shows up earlier. If you start lifting the shadows it will get more obvious of course.
Quote from: Fioritura on June 02, 2013, 04:23:47 PM
Hi JulianH,
which reader are you using? I tried one from Transcend on my Mac running OSX 10.7.5 but the DOS file system could not be mounted. ExFAT worked on the Mac but not on the 50D.
Regards,
Andrew
I'd recommend you benchmark in camera . . .
Quote from: menoc on June 02, 2013, 05:58:00 PM
I'd recommend you benchmark in camera . . .
Agree. Although the benchmark in the camera doesn't seem to end correctly (for me) and doesn't save the results.
Also, in live view, the benchmark is not showing the max of your card, the card controller can be the limiting factor. So it can be interesting to check with a USB 3 reader what the card is capable of, I think.
Quote from: JulianH on June 02, 2013, 06:03:46 PM
Agree. Although the benchmark in the camera doesn't seem to end correctly (for me) and doesn't save the results.
Also, in live view, the benchmark is not showing the max of your card, the card controller can be the limiting factor. So it can be interesting to check with a USB 3 reader what the card is capable of, I think.
Try the pre-May 28th build to benchmark. You should get a .BMP in the root of your card with the benchmark results.
BTW, major props for the 50D to 1% . . . I'll send some contribution your way . . .
Quote from: JulianH on June 02, 2013, 05:42:54 PM
Just a basic HAMA USB 3.0 reader. On Windows, don't know how that works for MAC. Should be no problem, card reader = card reader... it's just usb... as far as I know.
That's what I thought, but the card usable by the 50D is not readable by the Mac OS: Unrecognized File System. Might a different card reader work? I am able to access the card through a M-Audio Microtrack, at an abyssmal speed...
Regards,
Andrew
Lexar Professional 600x (32GB or 64GB) is a good alternative. Rock solid - been using it for over a year and a half now. Never had problems with it. But if you must know, here are the speed comparisons with my Komputerbay 64GB 1000x card:
Lexar Professional 32GB 600x
(http://i.imgbox.com/abjPxylC.jpg)
Komputerbay 64GB 1000x:
(http://i.imgbox.com/acrP0LHK.jpg)
Looks good. That Lexar 600x is definately faster than my Sandisk 90MB/s. Would be interesting to see Komputerbay 600x results.
64GB 600X for 57 Euro seems to be the best deal in Europe. (ebay link (http://www.ebay.nl/itm/Komputerbay-64Go-Professional-Compact-Flash-Carte-CF-600X-90MB-s-Extreme-Speed-/110936115599?pt=FR_YO_Informatique_Stockage_CartesMemoire&hash=item19d44ec98f)).
Cheaper per GB than 128GB 600X at 99 Euro.
Quote from: JulianH on June 02, 2013, 06:49:49 PM
Looks good. That Lexar 600x is definately faster than my Sandisk 90MB/s. Would be interesting to see Komputerbay 600x results.
64GB 600X for 57 Euro seems to be the best deal in Europe. (ebay link (http://www.ebay.nl/itm/Komputerbay-64Go-Professional-Compact-Flash-Carte-CF-600X-90MB-s-Extreme-Speed-/110936115599?pt=FR_YO_Informatique_Stockage_CartesMemoire&hash=item19d44ec98f)).
Cheaper per GB than 128GB 600X at 99 Euro.
That's a great deal. I paid almost $200 for the Lexar when I first bought it . . .
Everybody please make your donation to @JulianH he took the risk and got a 50D package for 1% now let's take the initiative and repay him back with whatever you can. Email him he will forward you a link with all details about package.
Quote from: JulianH on June 02, 2013, 06:49:49 PM
Looks good. That Lexar 600x is definately faster than my Sandisk 90MB/s. Would be interesting to see Komputerbay 600x results.
64GB 600X for 57 Euro seems to be the best deal in Europe. (ebay link (http://www.ebay.nl/itm/Komputerbay-64Go-Professional-Compact-Flash-Carte-CF-600X-90MB-s-Extreme-Speed-/110936115599?pt=FR_YO_Informatique_Stockage_CartesMemoire&hash=item19d44ec98f)).
Cheaper per GB than 128GB 600X at 99 Euro.
Quote from: a1ex on May 19, 2013, 09:41:14 AM
CF shootout:
(http://a1ex.magiclantern.fm/bleeding-edge/raw/bench-cf.gif)
SD shootout:
(http://a1ex.magiclantern.fm/bleeding-edge/raw/bench-sd.gif)
I've only used the log files created outside LiveView, so the results should be comparable.
Am I read this right? Is that a
Komputer Bay 600x card waaaayy down at about 30Mb/s????? No idea what the "no name chip log" bit means.....
Hey there,
I tested the latest nightly build and it´s awesome! Thanks a lot guys!
Issue´s which arised during raw recording:
- The buffer is full after 129 frames (recording at 24fps, 15XX x 720, sandisk extreme 60 mbits/sec). Is that the card´s buffer which is full or the camera´s buffer? I already ordered a komputerbay 1000x. Hope this solves the problem. I´ll let you know.
- Another issue I found was that the exposure changes after hiting the record button (not exclusivley in raw mode). The camera adjusts the exposure by itself when I point the lens on dark or bright areas. Anybody knows how to fix that? Does it have to do with the new exposure lock functions?
cheers
Quote from: closetoheaven on June 02, 2013, 07:53:05 PM
Hey there,
I tested the latest nightly build and it´s awesome! Thanks a lot guys!
Issue´s which arised during raw recording:
- The buffer is full after 129 frames (recording at 24fps, 15XX x 720, sandisk extreme 60 mbits/sec). Is that the card´s buffer which is full or the camera´s buffer? I already ordered a komputerbay 1000x. Hope this solves the problem. I´ll let you know.
- Another issue I found was that the exposure changes after hiting the record button (not exclusivley in raw mode). The camera adjusts the exposure by itself when I point the lens on dark or bright areas. Anybody knows how to fix that? Does it have to do with the new exposure lock functions?
cheers
Hey Closetoheaven.
"You need to turn all overlays off (even native Canon overlays), keep liveview exposure simulation on and set photo mode to jpeg only" this could help get it going. also Is it possible to go to 1280 by 720? Maybe do a benchmark test to check your card speed. Test can be found in the debug menu. Will need 43-44 Mb/s I think to run UP TO 1280 x 720. Higher res than that will need faster cards to record with out stopping / dropping frames.
I have a 50D in the mail and the same cards as you. Sandisk extreme 16 /32g. They write at about 44.5Mb/s on my 7D. My 8GB Sandisk xtreme was only 40.9Mb/s. What size is your Card? CAn you try these settings and post back?
Was hoping to delay dropping more $$$ on cards right away and just use what I have.
Thanks.
Hello!
I have been following this thread since it was created. I was just wondering, why my videos on 50d even on 640x480 are a little bit lagging(maybe frame skipping will be more suitable)? Is it because of the card? I am not sure but I think I have lexar professional 233x.
Thanks!
Quote from: John-Jo on June 02, 2013, 08:12:43 PM
Hey Closetoheaven.
"You need to turn all overlays off (even native Canon overlays), keep liveview exposure simulation on and set photo mode to jpeg only" this could help get it going. also Is it possible to go to 1280 by 720? Maybe do a benchmark test to check your card speed. Test can be found in the debug menu. Will need 43-44 Mb/s I think to run UP TO 1280 x 720. Higher res than that will need faster cards to record with out stopping / dropping frames.
I have a 50D in the mail and the same cards as you. Sandisk extreme 16 /32g. They write at about 44.5Mb/s on my 7D. My 8GB Sandisk xtreme was only 40.9Mb/s. What size is your Card? CAn you try these settings and post back?
Was hoping to delay dropping more $$$ on cards right away and just use what I have.
Thanks.
Thanks for your reply!
My card is 16GB. I will test your recommendations tommorow and post my results.
cheers
Don't forget to contribute to the payment of the camera JulianH purchased for 1%. He's stuck his neck out for us and any contribution is welcomed.
Send him a PM to get more details.
Quote from: ashtrai on June 02, 2013, 09:15:44 PM
Don't forget to contribute to the payment of the camera JulianH purchased for 1%. He's stuck his neck out for us and any contribution is welcomed.
Send him a PM to get more details.
I've PM'd him. It's a great thing he's done for the 50D ML community and he shouldn't have to carry the cost on his own!
By the way guy's I'm getting phenomenal results with the new Build May, 28 from Gregory on the KomputerBay 64GB card. full recording to 4.28GB @ 1592 x 896 just got one hick-up for the first recording. I also learned a trick Put resolution to 1600 not 1920 it records smootly no problem no drop frames, the hack automatically places it to 1592 x 896. loving it.. smooth recording thank you ML @Gregory and all the other developers.
Quote from: kretynjakchuj on June 02, 2013, 08:25:42 PM
Hello!
I have been following this thread since it was created. I was just wondering, why my videos on 50d even on 640x480 are a little bit lagging(maybe frame skipping will be more suitable)? Is it because of the card? I am not sure but I think I have lexar professional 233x.
Thanks!
Need faster card..
Quote from: goldenchild9to5 on June 02, 2013, 09:31:26 PM
By the way guy's I'm getting phenomenal results with the new Build May, 28 from Gregory on the KomputerBay 64GB card. full recording to 4.28GB @ 1592 x 896 just got one hick-up for the first recording. I also learned a trick Put resolution to 1600 not 1920 it records smootly no problem no drop frames, the hack automatically places it to 1592 x 896. loving it.. smooth recording thank you ML @Gregory and all the other developers.
That's great news! 1592X896 @ 24 fps continuous recording? Can you confirm that? Post a picture of the camera doing it :) I really can't squeeze it beyond 450 frames at this resolution. Tried setting it to 1600 instead of 1920 but that doesn't seem to make a difference.
Quote from: JulianH on June 02, 2013, 09:36:23 PM
That's great news! 1592X896 @ 24 fps continuous recording? Can you confirm that? Post a picture of the camera doing it :) I really can't squeeze it beyond 450 frames at this resolution. Tried setting it to 1600 instead of 1920 but that doesn't seem to make a difference.
Confirmed. (http://s21.postimg.org/xgg59uimv/image.jpg)
Guy's we need everybody to contribute towards @JulianH purchase of a 50D for developers 1% he was kind enough to take that risk anything that you can give will help, like a posted before a $10 + is great got a long way to recover his expenses. Let's make it happen guy's send him an email he will send you the info for donation we need everybody, we have the power to make the 50D shine with those contributions.
Got to 14gbs before I got bored. :P
One clip to "warm up the card" and I'm off running. Also on the Komputerbay 64GB
Quote from: JulianH on June 02, 2013, 09:36:23 PM
That's great news! 1592X896 @ 24 fps continuous recording? Can you confirm that? Post a picture of the camera doing it :) I really can't squeeze it beyond 450 frames at this resolution. Tried setting it to 1600 instead of 1920 but that doesn't seem to make a difference.
Yep 1592X896 @ 24 fps continuous recording with no problem ;D Cool gonna take a picture while recording I'll post as soon as possible. For some reason with Res set to 1600 instead of 1920 to me seems to make a difference, but it automatically set's it to 1592 x 896 anyways.
Quote from: artiswar on June 02, 2013, 09:50:33 PM
Got to 14gbs before I got bored. :P
One clip to "warm up the card" and I'm off running. Also on the Komputerbay 64GB
Nice.. but can you convert the files with Raw2Dng program, or windows version? when I get to 4.28GB mines stops but I can't convert files.
Quote from: artiswar on June 02, 2013, 09:46:29 PM
Confirmed. (http://s21.postimg.org/xgg59uimv/image.jpg)
It has been confirmed ;D great job Artiswar, but how did you get to 15GB guess card needs to warm-up gonna try also. One more thing what settings do you have in camera?
Quote from: artiswar on June 02, 2013, 09:50:33 PM
Got to 14gbs before I got bored. :P
One clip to "warm up the card" and I'm off running. Also on the Komputerbay 64GB
Nice! But what build is that? I got 6 buffer stars on Greg's 28 may built. How come you have only 3 with a faster card.. interesting :)
@goldenchild9to5 how many dots do you get for the buffer? Mine shows like <**....>
Quote from: JulianH on June 02, 2013, 10:05:06 PM
Nice! But what build is that? I got 6 buffer stars on Greg's 28 may built. How come you have only 3 with a faster card.. interesting :)
@goldenchild9to5 how many dots do you get for the buffer? Mine shows like <**....>
Same as @Artiswar (*..) 3 Stars not 6. If you want I can zip a copy of my build for you to try, let me know Julian.
Quote from: JulianH on June 02, 2013, 10:05:06 PM
Nice! But what build is that? I got 6 buffer stars on Greg's 28 may built. How come you have only 3 with a faster card.. interesting :)
@goldenchild9to5 how many dots do you get for the buffer? Mine shows like <**....>
I was curious to that as well.
Camera setting have hacked mode on, 1600 resolution picked, jpg L in Canon menu.
No CF reader around right now but I'm planning on merging the spanned clips in Terminal, adding the footer in a hex editor, and hoping for the best.
Quote from: JulianH on June 02, 2013, 10:05:06 PM
Nice! But what build is that? I got 6 buffer stars on Greg's 28 may built. How come you have only 3 with a faster card.. interesting :)
@goldenchild9to5 how many dots do you get for the buffer? Mine shows like <**....>
I just noticed something I'm getting none stop recordings with canon's bottom overlays on. Looking @Artiswar's picture he has no overlays that's probably why I'm not getting to 15GB myself. And I tried hard pans still no Hick-ups with bottom overlays from Canon ;D
Quote from: goldenchild9to5 on June 02, 2013, 10:10:52 PM
Same as @Artiswar (*..) 3 Stars not 6. If you want I can zip a copy of my build for you to try, let me know Julian.
Please! I'll give it a try.
Going to format and align my card again, see if I can squeeze a bit more speed out of it. I thought the camera was the bottleneck, turns out it's not. Good :)
I'm using what would seem to be the same setup as goldenchild9to5 (latest build, Komputerbay 64, etc) - who reports smooth results.
I tried setting resolution to 1600 to see if that helped, but even with Global Draw OFF, Hacked Mode ON, 24fps overrride... the 1592x896 - writing to the card is at about 41Mb/s and I start dropping after about 200 frames. I'd love to figure out what's causing performance in my setup to be so much slower.
Will stay with it and learn my way there somehow. Ongoing thanks for any tips along the way.
Best
Quote from: JulianH on June 02, 2013, 10:14:29 PM
Please! I'll give it a try.
Going to format and align my card again, see if I can squeeze a bit more speed out of it. I thought the camera was the bottleneck, turns out it's not. Good :)
Julian, are you formatting in camera? With what are you aligning in OSX?
Quote from: artiswar on June 02, 2013, 10:13:11 PM
I was curious to that as well.
Camera setting have hacked mode on, 1600 resolution picked, jpg L in Canon menu.
No CF reader around right now but I'm planning on merging the spanned clips in Terminal, adding the footer in a hex editor, and hoping for the best.
Nice.. that 1600 resolution seems to work well for some odd reason, JPG (L) that's the first setting for JPG right.. the 15megapixel one. Let us know how it works out for you.
My situation is not stable with the komputerbay 1000x 64gb tonight. But I didn't set the the picture quality to JPG...
I've found a few more issues that are kind of disturbing (using the 28may build):
1) My raw settings are not persistent. Every time I close liveview / switch off the camera I have to setup the raw settings again (I have the raw module loading automatically)
2) start recording raw is done using the liveview button. After I stopped recording, the only way to switch off liveview is to turn off the camera.
3) It might be a setting? But after doing nothing for about a minute it switches off liveview. Not a big deal, but together with issue 1 it's frustrating :P
Quote from: JulianH on June 02, 2013, 10:14:29 PM
Please! I'll give it a try.
Going to format and align my card again, see if I can squeeze a bit more speed out of it. I thought the camera was the bottleneck, turns out it's not. Good :)
Give me a couple minutes gonna send right away for you. I guess not cause it does not stop & no frame dropped.
3 stars means you have something using memory... ie raw + jpeg.
Quote from: dhallowell19 on June 02, 2013, 10:15:47 PM
I'm using what would seem to be the same setup as goldenchild9to5 (latest build, Komputerbay 64, etc) - who reports smooth results.
I tried setting resolution to 1600 to see if that helped, but even with Global Draw OFF, Hacked Mode ON, 24fps overrride... the 1592x896 - writing to the card is at about 41Mb/s and I start dropping after about 200 frames. I'd love to figure out what's causing performance in my setup to be so much slower.
Will stay with it and learn my way there somehow. Ongoing thanks for any tips along the way.
Best
Hey dhallowell here is another trick I tried: If your using a mac, or windows I formatted my card to Exfat first & reformatted my card in camera. Gonna post a link of my build so you can give it a try yourself, also try to re-install canon's 1.0.9 firmware again and reset everything in camera to the default setting. I forgot in camera turn off Raw in canon menu & turn on JPG (L) setting on geat tip from @JulianH lastly install my build on your camera.
You guys getting <...> for buffer, check Shoot Malloc. Should be 212M. It's 188 when raw is on in the camera.
(http://cs537512.vk.me/u16007354/doc/1ca5595b3551/VRAM1.jpg)
Quote from: JulianH on June 02, 2013, 10:14:29 PM
Please! I'll give it a try.
Going to format and align my card again, see if I can squeeze a bit more speed out of it. I thought the camera was the bottleneck, turns out it's not. Good :)
Here is the link to build: http://limelinx.com/flwls
Quote from: dhallowell19 on June 02, 2013, 10:15:47 PM
I'm using what would seem to be the same setup as goldenchild9to5 (latest build, Komputerbay 64, etc) - who reports smooth results.
I tried setting resolution to 1600 to see if that helped, but even with Global Draw OFF, Hacked Mode ON, 24fps overrride... the 1592x896 - writing to the card is at about 41Mb/s and I start dropping after about 200 frames. I'd love to figure out what's causing performance in my setup to be so much slower.
Will stay with it and learn my way there somehow. Ongoing thanks for any tips along the way.
Best
Here is a link to download the build that I'm using http://limelinx.com/flwls
Aligned the card (to 1024KB) and reinstalled everything. That build you're uploading is exactly GregoryOfManhattans build of 28May I suppose? Maybe best to keep it centralized and just link to the post (it's linked in the topic start as well).
I still get the same results. Actually I think the card got worse after aligning it. I've set it to 1024KB, should I use something else? I've no idea to be honest ::)
Quote from: 1% on June 02, 2013, 10:25:38 PM
3 stars means you have something using memory... ie raw + jpeg.
I Checked my settings 1% I'm only on the JPG (L) Mode. Now I'm getting Past 5GB files.
I aligned my card (first sector) to 4096 and formatted it fat32 with block size 4096. In the usb 3 cardreader I get read speeds above 125MB/s. I will do a benchmark now to see my speeds
@goldenchild9to5: your card is formatted exFat or what? How do you get past the 4GB limit? :O
Spanning works with Fat32!
Quote from: JulianH on June 02, 2013, 10:44:19 PM
Aligned the card (to 1024KB) and reinstalled everything. That build you're uploading is exactly GregoryOfManhattans build of 28May I suppose? Maybe best to keep it centralized and just link to the post (it's linked in the topic start as well).
I still get the same results. Actually I think the card got worse after aligning it. I've set it to 1024KB, should I use something else? I've no idea to be honest ::)
I think you should format in camera that's what I've been doing.
I'm currently getting past 5GB actually got to 8GB and stopped it cause it kept on going consistent 57mb/s here is a picture.
@Artiswar confirmed more than 5GB's
Link: http://imageshack.us/photo/my-images/24/img20130602164422.jpg/
(http://imageshack.us/photo/my-images/24/img20130602164422.jpg/)
Quote from: JulianH on June 02, 2013, 10:32:27 PM
You guys getting <...> for buffer, check Shoot Malloc. Should be 212M. It's 188 when raw is on in the camera.
(http://cs537512.vk.me/u16007354/doc/1ca5595b3551/VRAM1.jpg)
Turn OFF: Auto Lightning Optimizer, Long Exposure Noise Reduction, High ISO Noise Reduction, Highlight Tone Rpiority
Quote from: savale on June 02, 2013, 10:51:41 PM
I aligned my card (first sector) to 4096 and formatted it fat32 with block size 4096. In the usb 3 cardreader I get read speeds above 125MB/s. I will do a benchmark now to see my speeds
@goldenchild9to5: your card is formatted exFat or what? How do you get past the 4GB limit? :O
I first format it Exfat than reformat in camera just trying different tricks sometimes those tricks work. I don't know I just shot for 20GB none stop..
To free up malloc set these settings in Canon Menus:
(http://i.imgbox.com/acwXVvAw.jpg)
Quote from: JulianH on June 02, 2013, 10:56:19 PM
Spanning works with Fat32!
Yes. But Files are corrupt. Unless there's something newly developed . . .
Guy's I just recorded a 20GB file with my 50D I had to stop it it kept on going Zero frame drops hard pans + @ ISO 3200 no problem. @ times it shows a little hint of going to 2nd stars because I was panning it like crazy after that back to 1 * Idling 57mb/s constant. Now we only gotta figure out the panning situation. Lastly need to record 1, or 2 warm-up shots to ramp the card up than you can't stop it.
Quote from: menoc on June 02, 2013, 11:17:09 PM
Yes. But Files are corrupt. Unless there's something newly developed . . .
I know now we just gotta wait for new development. Thanks for those in camera settings gonna try now.
Quote from: Roman on June 02, 2013, 06:48:08 AM
I believe under one of the ML menus there is a 'sticky DOF preview' button - so you can press the button and it holds it down until you press it again. I havent tried it on the 50D yet, but have just been re-reading the ML user guide.
I found the DOF sticky option. It's located in the Misc key settings under Prefs. It works great, but you can only activate it once recording has begun - if you activate it first, then you will be unable to record using the liveview button. The problem I have in post is when I import the DNG sequence into After Effects, I only have the option to grade the first representative frame. Unfortunately, the first frame is almost always incorrectly exposed since there's a delay from the time I hit record to the time the DOF sticky is engaged.
Is there a way to engage the DOF sticky before the Raw recording? If this isn't possible, then is there a way to specify a different representative frame in After Effects? I know this can be done via Adobe Bridge, but I'd like to avoid the extra steps if at all possible.
Thanks.
Quote from: goldenchild9to5 on June 02, 2013, 05:38:22 PM
In one of your post you said not to use the May 28th build guess I was reading wrong than, Gonna try out the new build today. For some reason I'm getting a lot noise in almost all ISO settings don't know what I'm doing wrong. Is it a setting that's boosting the noise in camera.
////
check your fps override settings... mine was set for optimize for exact frames which seemed to bring a lot of noise. changed to optimize for low light and it's shooting clean at 1600 now.
Guy's I'm getting (*.....) 6 dots now instead of my previous 3 (*..) thanks to @menoc a lot of memory been freed-up Record Past 5GB with Zero Hick-ups Zero problems Here is a picture:
(https://mail-attachment.googleusercontent.com/attachment/u/0/?ui=2&ik=cc3e02cd84&view=att&th=13f06cdd3367deb3&attid=0.1&disp=inline&realattid=1436767965501456384-local0&safe=1&zw&saduie=AG9B_P9nrcuG6qOBiLmSlBInlbT7&sadet=1370208910480&sads=QYjdzt_2Wfqu2LFv5C3Ee7UHblI)
Guy's $180 dollars left to put in for donations Let's get it done for the 50D contact @JulianH for info.
Quote from: goldenchild9to5 on June 02, 2013, 11:41:37 PM
Guy's I'm getting (*.....) 6 dots now instead of my previous 3 (*..) thanks to @menoc a lot of memory been freed-up Record Past 5GB with Zero Hick-ups Zero problems Here is a picture:
(https://mail-attachment.googleusercontent.com/attachment/u/0/?ui=2&ik=cc3e02cd84&view=att&th=13f06cdd3367deb3&attid=0.1&disp=inline&realattid=1436767965501456384-local0&safe=1&zw&saduie=AG9B_P9nrcuG6qOBiLmSlBInlbT7&sadet=1370208910480&sads=QYjdzt_2Wfqu2LFv5C3Ee7UHblI)
Actually, the only setting that affects Shooting malloc is High ISO Speed Noise Reduction. Turn it OFF.
(http://i.imgbox.com/abhwtsCO.jpg)
Quote from: menoc on June 02, 2013, 11:52:02 PM
Actually, the only setting that affects Shooting malloc is High ISO Speed Noise Reduction. Turn it OFF.
(http://i.imgbox.com/abhwtsCO.jpg)
Thanks for update Menoc..
Here's what my shooting memory allocation reports after turning off High Speed Noise Reduction . . .
(http://i.imgbox.com/adlbZZa3.jpg)
I've had inconsistent results with the read/write tests, that dont correlate to recoridng performance.
If I set FPS override to 0.15fps I get 60+mb/s, if 24fps I get 50ish, if 30fps I get 40-50+
So either the test is inaccurate if fps override is on, or there's something slowing it down in camera when it's at the higher frame rates.
Either way, regardless of what the speed tests indicate I seem to be able to record continuously up to about 55mb/s.
Quote from: menoc on June 03, 2013, 12:01:35 AM
Here's what my shooting memory allocation reports after turning off High Speed Noise Reduction . . .
(http://i.imgbox.com/adlbZZa3.jpg)
////
I'm finding that once you turn off the noise reduction it frees up the memory and you can actually turn it back on without affecting the free memory. Also noticed no difference in frames captured at 3200iso with noise reduction on or off.
What the.... Surprise!
I had global draw turned off all the time. Thought that would take a hit on performance.
Just turned it on (Live view) and guess what, recording speed goes up! Getting stable 1592x896 now, recording at 57MB/s. Without GD i get like 52 and drops to 50. great!
Lets try how far we can get in 5x zoom. I'm getting 300 frames at 1720x968.
1600x900 is stable.
Quote from: goldenchild9to5 on June 02, 2013, 11:44:55 PM
Guy's $180 dollars left to put in for donations Let's get it done for the 50D contact @JulianH for info.
Super work guys. I'm shooting 720x1280 24fps at 37MBps and only (*....) with the original build on a 60 MBps Sandisk card I got yesterday. I'll PM Julian to pony up $20 for taking the lead on the development camera and I wish I got anywhere near as much value and fun from my other donations.
Quote from: JulianH on June 03, 2013, 12:31:37 AM
I had global draw turned off all the time. Thought that would take a hit on performance.
Just turned it on (Live view) and guess what, recording speed goes up! Getting stable 1592x896 now, recording at 57MB/s. Without GD i get like 52 and drops to 50. great!
Great find!!!
(and it makes sense, since the 50D ML kills all Canon drawing code)
Tip: turn it off and call canon_gui_disable_front_buffer() from somewhere.
LOL weird stuff. For me it's the exact same opposite at 1592x896 with my 64gb komputerbay 1000x... Global draw on liveview and it stops after about 80 frames. Global draw off and it's at 12GB right now without a single skip :)
Quote from: JulianH on June 03, 2013, 12:31:37 AM
What the.... Surprise!
I had global draw turned off all the time. Thought that would take a hit on performance.
Just turned it on (Live view) and guess what, recording speed goes up! Getting stable 1592x896 now, recording at 57MB/s. Without GD i get like 52 and drops to 50. great!
Lets try how far we can get in 5x zoom. I'm getting 300 frames at 1720x968.
1600x900 is stable.
QuoteGreat find!!!
Wooohoo.. new trick to add to hacked mode. Esp.. for 600D/550D/etc.
Sick stuff: Global draw on liveview (but I have now all draw options disabled) and resolution at 1600: I can almost record 3:2 resolution:
1592x1062 1103 frames 8) (needed write speed 67,6)
Komputerbay 64gb 1000x (aligned at 4096)
edit: 5x zoom gives me a pink liveview....
BUT runs stable so far at 1920x818 (2.35:1) (62MB/s)
Recorded continuously to 4gb at 1920x818 in 5x crop mode on a Lexar 1000x 16g card. Stars got up to 4 near the end but it made it to 4gb. Not very sharp but some L glass might help this. A lot of jello too...
(http://www.prodigyvideo.com/videos/000266.jpg)
Quote from: JulianH on June 03, 2013, 12:31:37 AM
What the.... Surprise!
I had global draw turned off all the time. Thought that would take a hit on performance.
Just turned it on (Live view) and guess what, recording speed goes up! Getting stable 1592x896 now, recording at 57MB/s. Without GD i get like 52 and drops to 50. great!
Lets try how far we can get in 5x zoom. I'm getting 300 frames at 1720x968.
1600x900 is stable.
Wild. Good find. Testing tonight.
I really feel a shared experience with this thread - I've recently bought a second hand 50D, and still waiting for a KomputerBay 64 GB card to arrive!
Quote from: savale on June 03, 2013, 01:14:09 AM
Sick stuff: Global draw on liveview (but I have now all draw options disabled) and resolution at 1600: I can almost record 3:2 resolution:
1592x1062 1103 frames 8) (needed write speed 67,6)
Komputerbay 64gb 1000x (aligned at 4096)
edit: 5x zoom gives me a pink liveview....
BUT runs stable so far at 1920x818 (2.35:1) (62MB/s)
I bet you could do it if you kill all drawing with Clear Overlays . . .
Quote from: goldenchild9to5 on June 02, 2013, 09:49:59 PM
Guy's we need everybody to contribute towards @JulianH purchase of a 50D for developers 1% he was kind enough to take that risk anything that you can give will help, like a posted before a $10 + is great got a long way to recover his expenses. Let's make it happen guy's send him an email he will send you the info for donation we need everybody, we have the power to make the 50D shine with those contributions.
I'm in - and have been in touch with Julian.
Hello everyone,
First off thank you very much for all the effort being made to make the canon 50d able to shoot raw video it's been an awesome great experience.
however i'ave some doubt's. im currently using the Greg's 28 may built, with a sandisk extreme 60mb/s udma 8gb card. im getting about 38mb/s stable wich makes me able to shoot in 1280x720 without any problems, i can get away by shooting in a bit higher resolution by comprimessing height. when i warm up the card i can shoot about 41mb/s without any problems.
Globaldraw on my camera with only peak focus enabled makes my write speed about 23mb/s so not good.
i also have download the nightly build however it doesnt come with raw movie module and the only way to get it is by replacing the autoexebin file and placing the modules folder also wich makes not using the nightly build since im replacing the autoexe bin file.... how do i use the latest nightly build and the raw module at the same time?
Ok so, lets say i have recorded some raw movie footage. i want to edit it. i use raw2dng to convert to a dng file wich is at color deph? 14 bit? because i export the dng files. open them in photoshop and the camera raw give me rgb values that are in 8 bit mode range not more than that. however. i open a dng file in after effects, and the rbg values are in the same range as photoshop was giving me. if i change the project settings to a color depth of 16bit the values change and are much higher like a true 14 bit file should be however, i export the movie file in a openexr open that file in nuke and the values are a 8 bit file.
that being said why is my camera shooting in 8 bit color depth mode not in 14 bit... or am i doing something wrong? is the dng file that raw2dng makes a 14 bit file? because my investigation dont indicate me that :/
i was expecting the dng files being a 14 bit image not a 8 bit color mode :C
well sorry for my poor english im from portugal.
thank you all for the effort being made to create this awesome hack :)
Quote from: bperrine on June 03, 2013, 12:41:16 AM
Super work guys. I'm shooting 720x1280 24fps at 37MBps and only (*....) with the original build on a 60 MBps Sandisk card I got yesterday. I'll PM Julian to pony up $20 for taking the lead on the development camera and I wish I got anywhere near as much value and fun from my other donations.
That is exactly the post I wanted to see! Have 60Mb/s cards that write at 44.5Mb/s. Keen to try 720 work flow all way to vimeo.
Quote from: menoc on June 03, 2013, 01:38:43 AM
I bet you could do it if you kill all drawing with Clear Overlays . . .
Holy mother of God!! . . . . I'm getting FULL FRAMES stable 3:2 !!
Did like 12GB with no frames skipping! . . .WE HAVE TO GET FILE SPANNING WORKING!
Disabling the front buffer lets me preview with no loss of speed it appears.
High ISO noise reduction is really interesting, it reconfigures memories... some blocks become blue and your green blocks move around. I guess on 50D it actually frees the memory its not using.
Quote from: menoc on June 03, 2013, 02:09:26 AM
Holy mother of God!! . . . . I'm getting FULL FRAMES stable 3:2 !!
Did like 12GB with no frames skipping! . . .WE HAVE TO GET FILE SPANNING WORKING!
Can you confirm what resolution and frame rate that is please? And what speed it is writing at? Thanks.
Results im getting with my sandisk extreme 60mb/s UDMA 8 gb card
(http://img18.imageshack.us/img18/6815/testoj.png)
Hey John here are some bitrates for 50D in each mode, in 24fps/16:9 ratio:
640x480 - 9.2mb/s
720x406 - 11.6mb/s
960x540 - 20.7mb/s
1280x720 - 36.9mb/s
1329x742 - 39.2mb/s
1440x810 - 46.7mb/s
1592x896 - 57.1mb/s (max res unless using 5x zoom)
1600x900 - 57.6mb/s (5x zoom only)
1720x960 - 66.0mb/s (5x zoom only)
1880x1056 - 79.5mb/s (5x zoom only)
1920x1056 - 81.2mb/s (5x zoom only)
1992x1056 - 84.2mb/s (max res for 5x zoom mode)
As I mentioned earlier, despite speed tests showing 40-50mb/s I can happily sit at 1592x896 24fps until 4gb. The fastest rate it's shown while recording is 58mb/s.
Awesome. Thanks for that. :) Have been finishing off edits so when the Camera finally gets here I wont have any distractions! Although hoping to get by on Sandisk extremes in short term, will be getting a bigger and faster card when I can work out best deal that can also be shipped to NZ.
Quote from: John-Jo on June 03, 2013, 03:02:11 AM
Can you confirm what resolution and frame rate that is please? And what speed it is writing at? Thanks.
With Komputerbay 64GB 1000x card:
Runs non-stop stable @ 1592x1062 (I stopped it at 13GB), at about 64 mb/s
@ 1592x896 it will run forever . . .
Set the following:
ISO: 100-200
FPS override: 23.988
Canon Menus: Set Qualiy to JPEG Only
Disable all settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: LiveView (Turn off all other options)
Raw Video Resolution: 1600
Raw Video Ratio: 3:2
Sound: OFF
Hacked Mode: ON
Fantastic! Thanks for full detailed post!!! :)
Don't know if it has been discussed yet, but my screen goes pink with the LV image overlaid below when I'm using 5x and 10x zoom. Returns back to normal when I disengage the zoom function. That is using the 28may build by gregoryofmanhattan.
Quote from: johansugarev on June 03, 2013, 06:12:43 AM
Don't know if it has been discussed yet, but my screen goes pink with the LV image overlaid below when I'm using 5x and 10x zoom. Returns back to normal when I disengage the zoom function. That is using the 28may build by gregoryofmanhattan.
Known issue. It's a work in progress . . .
I've noticed a lot of people getting differing results with the komputerbay cards. Might this have something to do with the fact that they were exposed as actually being Lexar cards that failed quality control?
Anyone else notice the weird square noise pattern on the dngs? Here is the same frame with max sharpen in AE to highlight it. Second frame has blur + noise before the sharpen. turning off sharpening in ACR doesn't seem to help.
(http://imageshack.us/a/img834/2233/86229502.jpg)
(http://imageshack.us/a/img6/2960/47080469.jpg)
Quote from: menoc on June 03, 2013, 04:57:25 AM
With Komputerbay 64GB 1000x card:
Runs non-stop stable @ 1592x1062 (I stopped it at 13GB), at about 64 mb/s
@ 1592x896 it will run forever . . .
Set the following:
ISO: 100-200
FPS override: 23.988
Canon Menus: Set Qualiy to JPEG Only
Disable all settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: LiveView (Turn off all other options)
Raw Video Resolution: 1600
Raw Video Ratio: 3:2
Sound: OFF
Hacked Mode: ON
Great stuff :) My card is actually the limit now. Maxes out around 59MB/s, recording stable between 56-59MB/s.
So 16:9 1592x896 works fine.
I'll have to get a faster card though, I'd love to use 3:2 and 4:3. 1440x1062 + 2x anamorphic lens is going to be great.
The 50D now officially became the most awesome camera for anamorphic shooters on a budget :)
@primemultimedia: what iso are you on? Can you upload some DNG's? At high iso's when you do a lot of noise correction you can get artefacts like that. It is a pretty old sensor after all... the 50D was known for it's banding problems at high iso in photo mode.
@primemultimedia
Just a guess: It might have to do something with skipping pixels. As I understand it right only a part of the sensor pixels are used.
Probably something like this:
1001001001
0000000000
0000000000
1001001001
0000000000
0000000000
1001001001
0000000000
0000000000
1001001001
when using crop mode the sensor pixels are used like this:
000000000000
000000000000
000000000000
000000000000
000011110000
000011110000
000011110000
000011110000
000000000000
000000000000
000000000000
000000000000
Where a "1" indicates a pixel is used for recording raw.
You could try to use crop mode and see if that helps.
Duplicated the above results. ISO seems to make no difference. The 5th star in the buffer never stayed on consistently. This is getting pretty stable. Now once I get a CF reader back and some glass I get to stop shooting my body cap and film something of substance. Has anyone had luck with joining the spanned files in Terminal?
(http://i44.tinypic.com/3539gcg.jpg)
Quote from: primemultimedia on June 03, 2013, 07:22:55 AM
Anyone else notice the weird square noise pattern on the dngs?
Yep same here.
I've only noticable when zooming right in/pixel peeping though... I'll check a few 5x and 10x screen grabs and see if it looks the same.
Might be from the downscaling, as mentioned.
@Roman: thanks for testing. Looking forward to the results
Just started testing with the May 28th build with the settings menoc listed and a Komputerbay x1000 64gb. I get fairly steady results at 1592x1062 with an average of 67 MB/s, but for some reason my camera keeps dropping down to 22.331 FPS. My screen changes exposure when it happens and it usually occurs while I'm recording... It seems to be stuck at 22 fps until I reboot the camera.
I also get a "scripts dir missing" message when turning on the camera, not sure if that's related.
Quote from: evanamorphic on June 03, 2013, 10:20:43 AM
Just started testing with the May 28th build with the settings menoc listed and a Komputerbay x1000 64gb. I get fairly steady results at 1592x1062 with an average of 67 MB/s, but for some reason my camera keeps dropping down to 22.331 FPS. My screen changes exposure when it happens and it usually occurs while I'm recording... It seems to be stuck at 22 fps until I reboot the camera.
I also get a "scripts dir missing" message when turning on the camera, not sure if that's related.
Did you put FPS override on Exact FPS? (press FUNC when you are on the setting in the menu to get more options)
Just make a emtpy folder 'scripts' in the ML directory on your CF card. That will cancel the message.
https://vimeo.com/67550950
ML Version of Nightly Build EOS 50D May 28th
smeangol.com/autoexec.bin
smeangol.com/MODULES.zip
One Taker
Shot at 1592x480
24mm of 24-105mm L-Lens
F 4.0
ISO 800
Converted (after DNG-Rewrapping with RAW2DNG v0.9) in AE to QT Animation Codec.
Continious Recording at 90MB/s SanDIsk Extreme Pro UDMA 7 Card
@Ciardi: looks good!
The build you are linking is not the May28 build, you should link (and use!) this one:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/50D-2013May28build.zip
See: http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
50D cinemascope is coming - but i'm dropping my main ML dev machine at apple store this morning (down to a single usb port on mb air - so i can't plug in drives and card reader at same time)
build code status: over past couple of days, there have been many conflicts with 50D code and new features.
best stable running builds have been the 28th, morning of the 30th (wish i'd kept that one around).
there will be a different set of resolutions available depending on the mode.
RESOLUTION_CHOICES_X CHOICES("640","768","960","1280","1344","1472","1600","1728","1856","1920","2048","2560","2880","3584")
aspect_ratio_choices[] = { "3:1","2.67:1","2.50:1","2.39:1","2.35:1","2.20:1","2:1","1.85:1", "16:9","5:3","3:2","4:3","1:1"};
the 50D in raw mode will drop the width to the maximum available in LiveView - approximately 1536 pixels.
in zoom mode, 1920 is possible.
camera card writing speed will limit maximum resolution - seems like around 55 MB/s is maximum even on cards that benchmark at higher speeds.
for 16x9 HD aspect shooters:
Resolution : 1536 x 864
Frames : 2946
Frame size : 2322432 bytes
Frame skip : 1
FPS : 24.000
Processing frame 2946 of 2946...
Done.
Resolution : 1920 x 768
Frames : 2080
Frame size : 2580480 bytes
Frame skip : 1
FPS : 24.000
Processing frame 2080 of 2080...
FWIW - thought i let people know that graphics enables works with the released 28May13 build stable at 57MB/s
Gregory Of Manhattan @GregoryOnRoad 29 May
canon #50D gating 60 seconds of raw video at 57MB/s with graphic overlay enabled @autoexec_bin pic.twitter.com/rrxmC8OupA
speaking of graphics draw, recent builds have been doing weird things with it and that needs to be sorted out as well.
will be online less frequently until i get my computer back.
I think it's of important matter that specific needed changes for the 50d are merged to the unified branch as soon as possible to make sure there are little conflicts in the future. Then it's easier to branch of the unified code to play around a bit :)
Is there an overview of specific 50d stuff? Can't be that much code I guess?
Thanks all of you guys for the donations so far. I got a lot of response and PM's and after one day the funding for the camera is almost complete! (€ 52,60 left).
I think it will be a good idea to supply 1% with a fast CF card as well, since he only has slow ones. I'm suggesting the 64GB Komputerbay 1000X, cheapest I can find on ebay is about $120. (http://www.ebay.com/itm/KOMPUTERBAY-64GB-COMPACT-FLASH-CARD-CF-1000X-150MB-s-Extreme-Speed-UDMA-7-64-GB-/140978267936?pt=Digital_Camera_Memory_Cards&hash=item20d2f5a720)
I'd like to finish the funding of the camera first and then keep the donations open for a little longer to fund the CF card. If you want to help, send me a PM and I'll send you the instructions and donations overview! Everything counts, even a few dollars/euros are welcome.
(http://i.ebayimg.com/t/KOMPUTERBAY-64GB-COMPACT-FLASH-CARD-CF-1000X-150MB-s-Extreme-Speed-UDMA-7-64-GB-/00/s/MTI5NlgxNTAw/z/ZjkAAOxyPepRlmKW/$T2eC16h,!yUE9s6NGYHtBRlmKWhCJQ~~60_12.JPG)
Quote from: GregoryOfManhattan on June 03, 2013, 01:35:47 PM
camera card writing speed will limit maximum resolution - seems like around 55 MB/s is maximum even on cards that benchmark at higher speeds.
I'm getting a bit more out of my card, 59MB/s, but that seems to be the limit of the card rather than the camera, as others have reported getting 1592x1062 recording stable (thats 60+ MB/s).
@JulianH
Good call on sending the 50D to 1%. Hopefully my card will turn up today and I can help with testing.
I'll PM you for donation details.
Thanks for everyone's hard work so far.
maybe getting the Komputerbay card from Amazon would be a better idea? or is it not available for International purchase? where is 1% located?
Quote from: JulianH on June 03, 2013, 02:53:05 PM
Thanks all of you guys for the donations so far. I got a lot of response and PM's and after one day the funding for the camera is almost complete! (€ 52,60 left).
I think it will be a good idea to supply 1% with a fast CF card as well, since he only has slow ones. I'm suggesting the 64GB Komputerbay 1000X, cheapest I can find on ebay is about $120. (http://www.ebay.com/itm/KOMPUTERBAY-64GB-COMPACT-FLASH-CARD-CF-1000X-150MB-s-Extreme-Speed-UDMA-7-64-GB-/140978267936?pt=Digital_Camera_Memory_Cards&hash=item20d2f5a720)
I'd like to finish the funding of the camera first and then keep the donations open for a little longer to fund the CF card. If you want to help, send me a PM and I'll send you the instructions and donations overview! Everything counts, even a few dollars/euros are welcome.
(http://i.ebayimg.com/t/KOMPUTERBAY-64GB-COMPACT-FLASH-CARD-CF-1000X-150MB-s-Extreme-Speed-UDMA-7-64-GB-/00/s/MTI5NlgxNTAw/z/ZjkAAOxyPepRlmKW/$T2eC16h,!yUE9s6NGYHtBRlmKWhCJQ~~60_12.JPG)
I'm getting a bit more out of my card, 59MB/s, but that seems to be the limit of the card rather than the camera, as others have reported getting 1592x1062 recording stable (thats 60+ MB/s).
He definitely needs one of those Fast cards for testing. Guy's let's keep the donations coming we getting there PM Julian for the info. By the way here is where I bought mines it's directly through KomputerBay for $114 got it in 4 days regular mail:
http://www.amazon.com/KOMPUTERBAY-Professional-COMPACT-FLASH-Extreme/dp/B009JCL55Y/ref=sr_1_1?ie=UTF8&qid=1370274547&sr=8-1&keywords=Komputerbay+64GB+CF
Quote from: rockfallfilms on June 03, 2013, 03:01:49 PM
@JulianH
Good call on sending the 50D to 1%. Hopefully my card will turn up today and I can help with testing.
I'll PM you for donation details.
Thanks for everyone's hard work so far.
Great please do so we are getting closer to our donations goals for 1%
Quote from: blackroom on June 03, 2013, 05:38:12 PM
maybe getting the Komputerbay card from Amazon would be a better idea? or is it not available for International purchase? where is 1% located?
That's what I was thinking also that's where I got mines it's directly through KomputerBay for $114. Shipping was fast 4 days max possibly 5 depends on where you live.
http://www.amazon.com/KOMPUTERBAY-Professional-COMPACT-FLASH-Extreme/dp/B009JCL55Y/ref=sr_1_1?ie=UTF8&qid=1370274547&sr=8-1&keywords=Komputerbay+64GB+CF
Guy's uploading some 50D footage to vimeo right now. Just did a quick gorilla handheld style video just to see how it would hold up will post link in 30mins - 1 hour.
Great news: the Camera is
fully funded, thanks to donations from the following ML users:
Quote
JulianH (ML)
Andy600 (ML)
Novosibirets (ML)
Savale (ML)
dhallowell19 (ML)
Menoc (ML)
Goldenchild9to5 (ML)
Hijodeibn (ML)
ashtrai (ML)
Rue (ML)
PhilK (ML)
Blackroom (ML)
Paulforte (ML)
John-Jo (ML)
Primemultimedia (ML)
Bper****
HHL (ML)
Roman (ML)
Buildbyflying (ML)
Frerichs (ML)
rockfallfilms (ML)
xaled (ML)
Anonymous (ML)
Big thanks to all of you. I took a risk on just buying the camera and shipping it... But I didn't doubt you would be willing to share the costs with me. The response has been great!
There's even $20 'left over' - I have proceeded this into the funds for a CF card. I'll talk to 1% what will be the best way to get a card to him. No worries about that. We can even discuss the specific card, type etc. I've set the goal at $120 which should be enough.
Quote from: JulianH on June 03, 2013, 06:23:18 PM
Great news: the Camera is fully funded, thanks to donations from the following ML users:
Big thanks to all of you. I took a risk on just buying the camera and shipping it... But I didn't doubt you would be willing to share the costs with me. The response has been great!
There's even $20 'left over' - I have proceeded this into the funds for a CF card. I'll talk to 1% what will be the best way to get a card to him. No worries about that. We can even discuss the specific card, type etc. I've set the goal at $120 which should be enough.
He needs a fast card, Let's make it happen keep us updated..
Hey guy's here is a quick test 50D Resolution blew me away..
WorkFlow: After Effects (ACR) exported to a Flat Log ProRes 4444 File / Into Premiere Pro CS5.5 for editing / Into Resolve 9 for so simple color adjustments nothing major / Back into Premiere Pro little bit of sharpening and exported out to H264 1080p voila..
KomputerBay 64GB 1000X CF Card
Finally got my card and just did a quick test:
1320x742 - continuous
1440x810 - 800 frames
1592x896 - 200 frames
All 24 fps
Komputerbay 64gb 1000x
I'm getting slower than other people so I may have something still turned on in the canon menus. Do you guys turn off histogram/wave form etc?
This is with global draw set to liveview
Also when you run the benchmark how do you get a screen print?
Quote from: rockfallfilms on June 03, 2013, 07:29:14 PM
Finally got my card and just did a quick test:
1320x742 - continuous
1440x810 - 800 frames
1592x896 - 200 frames
All 24 fps
Komputerbay 64gb 1000x
I'm getting slower than other people so I may have something still turned on in the canon menus. Do you guys turn off histogram/wave form etc?
Also when you run the benchmark how do you get a screen print?
Yep turn all of those off, make sure you put your 50D on JPG (Large) mode and turn off Raw. In Magic Lantern menu turn off Global Draw, turn Hacked Mode (ON) One more thing what build are you using? you need to be on the @Gregory's May 28th build that's the most stable one so far, go back 1, or 2 pages from this post I posted a link of full build download and install. Make sure you format your card in camera. Let me know if everything went smoothly.
Check this post by Menoc for settings to disable in the Canon menu's:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg45086#msg45086
Use Gregory's May28th build, it is linked in the first post of this topic! (last update).
Yeah I'm using the build you mentioned.
I just did another test with everything switched off and it now runs continuously at 1592x896. I wonder how Julian is getting continuous with global draw on??
Here's a quick screengrab:
(https://dl.dropboxusercontent.com/u/24738031/ML/000575.jpg)
Quote from: rockfallfilms on June 03, 2013, 07:53:31 PM
Yeah I'm using the build you mentioned.
I just did another test with everything switched off and it now runs continuously at 1592x896. I wonder how Julian is getting continuous with global draw on??
Here's a quick screengrab:
https://docs.google.com/file/d/0B6HUSFpmHmZEbFlhdmxEZ2RmSVE/edit?usp=sharing
I wonder too.. but it really works for me.
Just checked again:
GD off, 1592x896, recording around 52-53MB/s, skips after about 500 frames.
GD on, 1592x896, recording around 56-57MB/s, keeps running. After 12GB I got bored and stopped, it just keeps going.
Anyway, the development of the 50D is still early. The fact that it can run like this (and even better for other users with faster cards than my Sandisk 90GB/s) proves that there are good things to come :) IMO it already works like a charm, even with all the bugs and errors in the code.
Your screengrab doesn't work, it's not public.
Which card are you using?
Just been out and filmed something in the garden, going to see how it turned out! Strangely I've got a .R00 file in with the RAW's
Link should work now.
Finally, my KomputerBay 32GB card arrived! ;D
Just shot a few tests @1592x896. Buffer always stayed at one star, no big deal, camera and CF card bored as hell!
But important: turn on hacked mode! Otherwise, it won't work!
More experiments following...
Quote from: necronomfive on June 03, 2013, 08:51:10 PM
Finally, my KomputerBay 32GB card arrived! ;D
Just shot a few tests @1592x896. Buffer always stayed at one star, no big deal, camera and CF card bored as hell!
But important: turn on hacked mode! Otherwise, it won't work!
More experiments following...
While every camera/card is different, I'm able to get 29+ GB non-stop recording @ 1592x896 24p with my 32GB KomputerBay card without having hacked mode on. I do, however, need hacked mode when shooting at 1920 resolution in 5X mode.
Got my CF card in today Recorded 1329frames (stopped myself, seemed very stable) 1592x896 24fps on Komputerbay 64gb 1000x Card. Global draw On but no histograms or focus peaking. Transcoding the footage right now, but so far things are seemingly going off to a good start.
Quote from: rockfallfilms on June 03, 2013, 08:31:08 PM
Which card are you using?
Just been out and filmed something in the garden, going to see how it turned out! Strangely I've got a .R00 file in with the RAW's
Link should work now.
Sandisk Extreme 90MB/s 32GB.
R00 (and R01 etc.) you'll get when your recording is larger than 4GB. It will split up the files.
Link is working, good job on the dishes! ;)
What do you think guys?, is it Komputerbay 64 GB 1000x the way to go?.......
What settings are you guys using in liveview? I have a manual lens on the camera and when i change aperture it changes brightness in liveview as it should.
I must have the wrong setting somewhere because when I increase the ISO it has no effect and the spot meter doesn't move. Even if I put it on ISO auto nothing changes.
I checked the ISO and it's working fine through the viewfinder, just not in liveview.
Any ideas what I've got wrong?
Just another test video. Trying to wrap my head around the low light performance of this beast.
Shot with Sigma 30mm f/1.4 at 1/50 H1 (ISO 6400 equivalent) at 1592x864. Upsized in Premiere to 1080p (just scaled 121%).
Pushed the exposure in ACR two stops up, so equivalent = ISO 25.600. Added a bit of luma and color noise correction to taste, kept sharpening low.
Here's a screen grab, edited and unedited (http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_301194.jpg)
Quote from: hijodeibn on June 03, 2013, 09:49:55 PM
What do you think guys?, is it Komputerbay 64 GB 1000x the way to go?.......
Reading through the forum you'll see that the KompterBay 1000X 32gb and 64gb are great cards. I get flawless recordings on my 50D and 5D Mark III with both flavors.
Quote from: rockfallfilms on June 03, 2013, 09:59:27 PM
What settings are you guys using in liveview? I have a manual lens on the camera and when i change aperture it changes brightness in liveview as it should.
I must have the wrong setting somewhere because when I increase the ISO it has no effect and the spot meter doesn't move. Even if I put it on ISO auto nothing changes.
I checked the ISO and it's working fine through the viewfinder, just not in liveview.
Any ideas what I've got wrong?
Have you tried exposure override in ML's exposure menu?
EDIT: override not lock, sorry.
@JulianH:
It's a proof you should try to avoid these high iso's because of the noise and color issues. BUT it's also a proof that if you have little choice the footage is still very usable :) (or you can use the noise as creative effect) Thanks
Have you seen this: 50D RAW vs C100 | Vimeo (http://vimeo.com/67543234)?
SHIT! That really blew my mind! ;D
I said it a few times already but it's true: Magic Lantern is the best thing you can download from the internet.
It's a free firmware add-on that turns your 5 year old 50D (A camera that was build for photography only!!!) into a 5.000 € BEAST!
Quote from: JulianH on June 03, 2013, 10:02:48 PM
Just another test video. Trying to wrap my head around the low light performance of this beast.
Shot with Sigma 30mm f/1.4 at 1/50 H1 (ISO 6400 equivalent) at 1592x864. Upsized in Premiere to 1080p (just scaled 121%).
Pushed the exposure in ACR two stops up, so equivalent = ISO 25.600. Added a bit of luma and color noise correction to taste, kept sharpening low.
Here's a screen grab, edited and unedited (http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_301194.jpg)
Great test man.. Amazing ISO 25,600 Wow looks like it's day time 50D is official a beast of a camera ;D
Quote from: CFP on June 03, 2013, 10:19:42 PM
Have you seen this: 50D RAW vs C100 | Vimeo (http://vimeo.com/67543234)?
SHIT! That really blew my mind! ;D
I said it a few times already but it's true: Magic Lantern is the best thing you can download from the internet.
It's a free firmware add-on that turns your 5 year old 50D (A camera that was build for photography only!!!) into a 5.000 € BEAST!
Yeah.. that video is amazing the 50D images looks better than the C100 even upscaled. The C100 is $6K right Canon 50D $500 with Raw recording. I think we are gonna see a lot of C100's on ebay soon.
Quote from: CaptainOfObvious on June 03, 2013, 10:11:45 PM
Have you tried exposure override in ML's exposure menu?
EDIT: override not lock, sorry.
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?
How is battery life doing with raw recording? I heard when recording h264 it drains pretty fast.
Quote from: rockfallfilms on June 03, 2013, 10:51:14 PM
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.
Here is my first raw test. I use to shoot girls/models, but since there was none available today I used some flowers for my first test ;)
Quote from: araucaria on June 03, 2013, 10:52:26 PM
How is battery life doing with raw recording? I heard when recording h264 it drains pretty fast.
I haven't 'counted' it but it runs out pretty fast I think. I'm not very concerned about it, just keep a few spares and my card is full (32GB) before I run out of a battery anyway. You'd need a sh*tload of storage to shoot more than you can last with your batteries.
hey all, big fan of ML and just registered to help walk me through this new canon raw video revolution. just picked up a handful of 50Ds and hoping to get some test footage up soon and help with the development. advance apologies for being a noob and the subsequent dumb questions i'll be asking.
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?
Hey all.
I'm a fan of ML, have used it on my 550D a lot and now am very close to decide to buy a used 50D -- all for the sake of RAW video. I also took part in 1% cam donation -- this is my token contribution to all the HUGE work that's being done here.
I have 2 questions though that bother me:
1. I see all these amazing test videos with 24 FPS. Is there 25FPS? For my work it is crucial.
2. I read the other day about the problem with electronic aperture for EF lens. I would appreciate if someone assures me that I can control my electronic aperture while shooting RAW video.
Thanks a lot people! This community is cool 8)
Quote from: rommex on June 03, 2013, 11:21:26 PM
Hey all.
I'm a fan of ML, have used it on my 550D a lot and now am very close to decide to buy a used 50D -- all for the sake of RAW video. I also took part in 1% cam donation -- this is my token contribution to all the HUGE work that's being done here.
I have 2 questions though that bother me:
1. I see all these amazing test videos with 24 FPS. Is there 25FPS? For my work it is crucial.
2. I read the other day about the problem with electronic aperture for EF lens. I would appreciate if someone assures me that I can control my electronic aperture while shooting RAW video.
Thanks a lot people! This community is cool 8)
Answers:
1) 25FPS will work too, but the lower the FPS the less bandwidth is needed. Make sure you get a 1000x card and you're fine :)
2) I read that also, but I had no problem controlling an EF-S lens. Maybe someone else can help you out... If this is even an issue I am pretty sure it will be fixed one day
Quote from: rommex on June 03, 2013, 11:21:26 PM
1. I see all these amazing test videos with 24 FPS. Is there 25FPS? For my work it is crucial.
2. I read the other day about the problem with electronic aperture for EF lens. I would appreciate if someone assures me that I can control my electronic aperture while shooting RAW video.
I've just shot some footage at 25fps and it recorded fine, I'm using a 1000x card, the buffer usage looked pretty similar to 24fps.
I also tried out an EFS lens (Tamron 17-50mm) and found that when I stopped it down the LV image didn't darken much. Even when I stopped down to almost closed, the LV image was still pretty bright.
Manual aperture lenses seem to work fine though.
Hello everyone,
have been doing some testing and i would like to know how is your workflow from shooting to final video.
So, i capture the movie. use raw2dng to convert to dng, open the dng in after effects which opens camera raw and i make my adjustments in a supossed to be (14 bit) file. then when e edit the video im not getting the dinamic range that a 14 bit image should give me. is there any software that makes me able to work with dng's at their full color depth? im using after effects but im sure there is another way around....
Quote from: Chris50d on June 03, 2013, 11:50:48 PM
Hello everyone,
have been doing some testing and i would like to know how is your workflow from shooting to final video.
So, i capture the movie. use raw2dng to convert to dng, open the dng in after effects which opens camera raw and i make my adjustments in a supossed to be (14 bit) file. then when e edit the video im not getting the dinamic range that a 14 bit image should give me. is there any software that makes me able to work with dng's at their full color depth? im using after effects but im sure there is another way around....
After Effects can handle up to 32 Bit float footage so 14 Bit raw is no problem for AE. Just make sure to change the composition settings to 16 Bits per channel. Press Ctrl+Alt+Shift+K to access that menu
(A standard AE composition has only 8 Bits per channel which equals a JPEG picture)
You'll always loose the dynamic range of raw / dng, but make sure you do that in the final stage only. (back to h264/mp4 for internet usage) Only problems I run into myself is the color space in after effects.
@dacssfreak: thanks for that one. The video I posted was 8bit :o (bit still ok)
I don't think there's a program that will let you work with a preserved 14-bit colour. That's why its important to desaturate /turn down highlights/ turn up shadows when you're importing into After Effects, you'll need to create "log style" images that you can later retrieve your entire colorspace.
If any program is close to working with native RAW, it's Resolve, but they're not quite there yet.
Hope that helps.
There's no need or sense to want a 14 bit final file I think. The whole advantage of raw is the freedom you have when grading. The final result can have way less dynamic range if you push the contrasts, or you can compress the highlights and brighten the shadows to get as much as DR as you want. You'll never see the whole 14 bits on a screen anyway. The power is in the 'hidden' data, the fact that you can lift up shadows or darken highlights without destroying the image.
was just corresponding with the mosaic engineering guys about the 5D2 VAF.
they're interested in getting a 50D to test out, we might find out soon if the 6D filter could work.
Quote from: blackroom on June 04, 2013, 12:13:46 AM
was just corresponding with the mosaic engineering guys about the 5D2 VAF.
they're interested in getting a 50D to test out, we might find out soon if the 6D filter could work.
Don't think the 50D needs it, to me the image is fine I have little to none Aliasing and moire in my footage.
Guy's only $53 to go.. please get your donations in, if you haven't yet contact @JulianH for details.
Quote from: savale on June 03, 2013, 11:04:02 PM
Here is my first raw test. I use to shoot girls/models, but since there was none available today I used some flowers for my first test ;)
Looks OK for a first test.....and I would love to see some RAW in girls/models.....please include the resolution you are shooting :)
Quote from: goldenchild9to5 on June 04, 2013, 12:53:55 AM
Guy's only $53 to go.. please get your donations in, if you haven't yet contact @JulianH for details.
This community rocks.....almost there guys.....lets complete the last step!!!
Went out for some shots earlier, didn't have the time to process everything and to make an edit, but I wanted to show some shots anyway. Going to try some new workflows with more of the footage later.
Nikkor 17-55mm f/2.8, after sunset. High iso.
Ungraded, straight conversions from raw (bit of noise reduction and less sharpening)
Upsized in Premiere to 1080p. Added sharpen 20 in Premiere.
Quote from: goldenchild9to5 on June 04, 2013, 12:53:55 AM
Guy's only $53 to go.. please get your donations in, if you haven't yet contact @JulianH for details.
Waiting that my money enter in my paypal account :'( (3 days)
I'm thinking of buying a 50D, I see you said High ISO but how high? I can't take my T2i over 1250 without a lot of noise
Quote from: arrinkiiii on June 04, 2013, 01:57:10 AM
Waiting that my money enter in my paypal account :'( (3 days)
Likewise. The growth of this is phenomenal.
Quote from: ble55ed on June 04, 2013, 01:57:44 AM
I'm thinking of buying a 50D, I see you said High ISO but how high? I can't take my T2i over 1250 without a lot of noise
It's hard to tell what iso the camera is really using in live view... I can't tell any more. I've put it on H1, H2, (6400, 12800) but it might be less actually. If I take a picture at the same setting, it's brighter than the live view image. Anyway, it was dark and i shot at f/2.8 1/50s and it looks pretty good to me.
Do buy a 50D. It's worth it for the resolution alone.
Quote from: JulianH on June 04, 2013, 02:18:37 AM
It's hard to tell what iso the camera is really using in live view... I can't tell any more. I've put it on H1, H2, (6400, 12800) but it might be less actually. If I take a picture at the same setting, it's brighter than the live view image. Anyway, it was dark and i shot at f/2.8 1/50s and it looks pretty good to me.
Do buy a 50D. It's worth it for the resolution alone.
Your sunset sky made me happy, I've always had problems with sky colors in h264. Can't wait to get the 50d.
Quote from: araucaria on June 04, 2013, 02:26:13 AM
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?
Quote from: CaptainOfObvious on June 04, 2013, 02:50:37 AM
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?
Where are you processing the TIFF sequences?
Quote from: CaptainOfObvious on June 04, 2013, 02:50:37 AM
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?
Well that used to happen to me doing timelapses in AE, I forgot where you can change the import settings (do a quick google) but you can always press "interprete footage" by right click on the secuence and change the framerate to 24 or 23,976
[edit] I found it, in After effects -> Edit -> Preferences ->Import -> Image secuence -> set to correct framerate.
Quote from: artiswar on June 04, 2013, 02:51:30 AM
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.
Quote from: CaptainOfObvious on June 04, 2013, 02:59:35 AM
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.
It's something in MPEG Streamclip. I'm using QT Pro 7 and no issue.
Quote from: JulianH on June 04, 2013, 01:21:42 AM
Went out for some shots earlier, didn't have the time to process everything and to make an edit, but I wanted to show some shots anyway. Going to try some new workflows with more of the footage later.
Nikkor 17-55mm f/2.8, after sunset. High iso.
Ungraded, straight conversions from raw (bit of noise reduction and less sharpening)
Upsized in Premiere to 1080p. Added sharpen 20 in Premiere.
Great job Julian images looks clean looks like it was shot @ ISO 1250.
My first shot with 50D Raw.
https://vimeo.com/67608412 (https://vimeo.com/67608412)
Quote from: JulianH on June 03, 2013, 10:02:48 PM
Just another test video. Trying to wrap my head around the low light performance of this beast.
Shot with Sigma 30mm f/1.4 at 1/50 H1 (ISO 6400 equivalent) at 1592x864. Upsized in Premiere to 1080p (just scaled 121%).
Pushed the exposure in ACR two stops up, so equivalent = ISO 25.600. Added a bit of luma and color noise correction to taste, kept sharpening low.
Here's a screen grab, edited and unedited (http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_301194.jpg)
Did you use FPS override or is this 30fps?
Quote from: paulforte on June 04, 2013, 03:19:56 AM
My first shot with 50D Raw.
https://vimeo.com/67608412 (https://vimeo.com/67608412)
Beautiful images.. What was you workflow? Did you shoot @ 24FPS exact?
Quote from: savale on June 03, 2013, 11:35:49 PM
Answers:
1) 25FPS will work too, but the lower the FPS the less bandwidth is needed. Make sure you get a 1000x card and you're fine :)
2) I read that also, but I had no problem controlling an EF-S lens. Maybe someone else can help you out... If this is even an issue I am pretty sure it will be fixed one day
You can definitely control electronic aperture lenses, but it's currently a bit of a hassle. There's an option in the magic lantern menus to select DOF Preview sticky. When you select this, you can push the DOF preview button on the front of the camera (just to the lower left of the lens). Once engaged, the liveview button will light up blue and your lens aperture will be correct. However, if you are shooting raw, you must first push the live view button to begin recording, and THEN you press the DOF preview button. When you're ready to stop recording, you must FIRST disengage the DOF preview, and THEN press the live view button to stop filming.
Quote from: goldenchild9to5 on June 04, 2013, 03:27:34 AM
Beautiful images.. What was you workflow? Did you shoot @ 24FPS exact?
My workflow was the following:
1. raw2dng
2. Import .dng into After Effects, correct white balance.
2a. Adjust the aspect ratio to 66% because I shot with anamorphic lens
2b. Made some color corrections using the basic color corrector inside AE
3. Export to Pro Res 422 at 1280 x 720 and upload to Vimeo. (didn't bother with 1080 for this)
I used 23.98 FPS override in the 50D.
The above is very straight forward (and I love AE's Raw processor cos its just like Lightroom). I intend on shooting more when I get my 128GB CF card (and, er, with a tripod), and I want to master the online / offline workflow using Pro Res 4444 1080 as my master files, then edit in 422 in FCP then reconform to 4444, color and export. That looks like the best workflow to me. Although, not sure if I need 4444 or 422 just yet. Maybe it's not worth the extra work.
Quote from: artiswar on June 04, 2013, 03:11:46 AM
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.
Quote from: artiswar on June 04, 2013, 02:09:48 AM
Likewise. The growth of this is phenomenal.
Yes, indeed. I was impossible to make a donation at the time went out the ML for the 7D, which is my camera ... but I followed the treat of the 50D from the beginning and how I could not in my time I want to do it now ... although i dont have a 50D, but very soon i will buy one ;D
Quote from: paulforte on June 04, 2013, 03:54:48 AM
My workflow was the following:
1. raw2dng
2. Import .dng into After Effects, correct white balance.
2a. Adjust the aspect ratio to 66% because I shot with anamorphic lens
2b. Made some color corrections using the basic color corrector inside AE
3. Export to Pro Res 422 at 1280 x 720 and upload to Vimeo. (didn't bother with 1080 for this)
I used 23.98 FPS override in the 50D.
The above is very straight forward (and I love AE's Raw processor cos its just like Lightroom). I intend on shooting more when I get my 128GB CF card (and, er, with a tripod), and I want to master the online / offline workflow using Pro Res 4444 1080 as my master files, then edit in 422 in FCP then reconform to 4444, color and export. That looks like the best workflow to me. Although, not sure if I need 4444 or 422 just yet. Maybe it's not worth the extra work.
Thanks for reply.. you should try 24fps Exact just tried it today, gonna compare with low light. I think ProRes 4444 1080 is the way to go, you will have all the flexibility in post to grade.
Quote from: arrinkiiii on June 04, 2013, 03:59:56 AM
Yes, indeed. I was impossible to make a donation at the time went out the ML for the 7D, which is my camera ... but I followed the treat of the 50D from the beginning and how I could not in my time I want to do it now ... although i dont have a 50D, but very soon i will buy one ;D
You don't even have a 50D yet Wow.. you gotta be a true fan of the 50D than. Hope you get yours soon let us know.
damn i was kicked out because of timelimit i guess ;D
can i still donate for the cf card for 1%?
i got a 50D one week ago and like to support julians commitment to press ahead with the 50D raw filmmakingpossibility one couldnt imagine a few weeks ago, started with the 5d mk3.
the abilities even low budget enthousiatsts get right now are groundbreaking.
hope i can help more when a transcend 16gb 1000x arrives:)
P.S.
big thanks to this community for the possibilities people get in filmmaking, it's amazing.
(that was also something like i wrote in my first post, when i got kicked out haha :))
in early tests with a transcend 400x 32gb i shot in 1280 x 752 i guess, i noticed a lot of moire. (a detailed street scenery)
what are your experiences?
is it acceptable in 1592 width?
greetings
David
Zeiss glass and the 50D tonight. Finally. I'll get a video up soon. Show some log to color stuff.
Quote from: savale on June 03, 2013, 10:02:17 AM
@Roman: thanks for testing. Looking forward to the results
Hey sorry I've been busy but when I had a look... some footage I filmed at 10x zoom didnt seem to be affected by this (although it was probably 'stretching' the image rather than downsizing it to achieve 10x zoom?)
I havent had a good look at the 5x ones yet.
But since it's not present in the still picture raw files that I've taken, I've got a few theories...
1. It's something to do with how raw2dng debayers the image perhaps, or this needs to work slightly different for 50D compared to other cameras? Probably not if it doesnt affect 10x zoom images.
2. When it downsamples the image for livewview perhaps it takes 'clusters' of pixels rather than 1? So you get an aliased/moired 'edge' on the blocks of 4 or 6 pixels wide which is giving the square pattern. (I'll try count the 'block' size tonight)
Might be a plan to try shoot some 'dark' frames and subtract the difference from an image to find the exact pattern and see if that helps figure out what might be causing it. Or, I wonder if part of the in camera iso noise reduction could remove this in real time if it's caused by predictable sensor noise. Or maybe worst case scenario batch subtracting 'dark' frames from shots that are affected might help if it's uniform in appearance.
Quote from: goldenchild9to5 on June 04, 2013, 04:11:50 AM
You don't even have a 50D yet Wow.. you gotta be a true fan of the 50D than. Hope you get yours soon let us know.
Yes, im huge fan of 50D :D i just use my 7D for video and some times the foto for timelapse... i already think exchange my 7D for a 50D and some more money... but then i lost my 60fps and sound capability. So, i will wait more a little bit and get the all money for one 50D and some cf cards.
...and also this is one way to say thanks ML All Super Stars Team, thank you for the 7D ML (close donation at that time...) and for all the achievement that they have for over pass the Canon functions.
Lets rock !!!
Quote from: JulianH on June 03, 2013, 11:07:04 PM
I haven't 'counted' it but it runs out pretty fast I think. I'm not very concerned about it, just keep a few spares and my card is full (32GB) before I run out of a battery anyway. You'd need a sh*tload of storage to shoot more than you can last with your batteries.
Julian, I would like to donate, please can you send your pay pal information to my email
Quote from: Roman on June 04, 2013, 05:06:57 AM
Hey sorry I've been busy but when I had a look... some footage I filmed at 10x zoom didnt seem to be affected by this (although it was probably 'stretching' the image rather than downsizing it to achieve 10x zoom?)
I havent had a good look at the 5x ones yet.
But since it's not present in the still picture raw files that I've taken, I've got a few theories...
1. It's something to do with how raw2dng debayers the image perhaps, or this needs to work slightly different for 50D compared to other cameras? Probably not if it doesnt affect 10x zoom images.
2. When it downsamples the image for livewview perhaps it takes 'clusters' of pixels rather than 1? So you get an aliased/moired 'edge' on the blocks of 4 or 6 pixels wide which is giving the square pattern. (I'll try count the 'block' size tonight)
Might be a plan to try shoot some 'dark' frames and subtract the difference from an image to find the exact pattern and see if that helps figure out what might be causing it. Or, I wonder if part of the in camera iso noise reduction could remove this in real time if it's caused by predictable sensor noise. Or maybe worst case scenario batch subtracting 'dark' frames from shots that are affected might help if it's uniform in appearance.
If its a fixed pattern, shooting an 18% grey solid at all ISOs and holding that in neat video as a preset will knock it out perfectly.
Aahhh yeah true! I forgot about neat video heh.
Perhaps that could be the way to go, then upload Neat video presets for the pattern noise removal.
Quote from: Roman on June 04, 2013, 05:34:10 AM
Aahhh yeah true! I forgot about neat video heh.
Perhaps that could be the way to go, then upload Neat video presets for the pattern noise removal.
That might work, a cam to cam profile might be better. Due to the fact that it's raw.
Yeah good point... I guess there might be more variance on account of that 50Ds are about 5yrs old now, compared to others. I think mine might be due for a clean.
Thank you ML for reviving my 50d, it has been parking at my drybox for more than a year.
I just get one sandisk extreme pro, loaded ML (28May) on it and tested my first raw video, i got average speed of 55mbps.
and here is it, my 6 months old baby girl tasting her first papaya.
http://www.youtube.com/watch?v=dFa6-n4Rsdk
Been doing some more tests tonight. I'm not convinced that there is any control over ISO or shutter speed at this stage. (using a manual lense, samyang 35mm)
For example if I'm recording at 30fps, I can set it to higher than 1/30th of a second which shouldnt be possible. Setting it any lower appears to make no difference I can discern either.
Also selecting through different ISOs, and the raw histogram stays exactly the same.
When I scroll the camera past a dark scene, to a light scene, and back to a dark scene, the camera is automatically adjusting the exposure to suit.
I havent checked the footage itself yet though... But I would assume it corresponds with the live view image, given that's where the raw file comes from.
As best I can tell there's no way to adjust the "exposure override" settings when it's in movie mode.
EDIT: Here are two frames from a panning shot with no settings adjusted by me:
(http://iforce.co.nz/i/bb515gmg.by5.jpg)
(http://iforce.co.nz/i/nxbgrunk.vl0.jpg)
Another update:
Okay so doing some more checks back home , it looks as though changing exposure works... up to a certain point. I think it just needs a 'lock' at the upper limit relating to FPS.
And it looks like ISO adjustment works now too... super weird. Working in both recording and not.
I definitely had the camera set to 'M' and tried adjusting settings with no luck while out earlier.
Well, Exposure Override does the job for me. Just set it to ON. ML now also controls the Aperture, so there also should be no need to activate the sticky DOF.
Ahh that's good news about the sticky DOF. 8)
Perhaps I had some weird settings there, prior to starting movie mode which have translated across. I'll try some more to replicate it, and find out where I went wrong.
Aha! I think I know where I went wrong.
I had exposure simulation OFF from when I was playing around with the camera before... But when I was out tonight I already had liveview/movie mode turned on, so when I went to the exposure menu to check, it just shows exposure simulation mode as MOVIE rather than on or off.
Would it be possible to update the exposure simulation setting title to be 'movie(off)' or 'movie(on)' perhaps?
Or just force it on, when in movie mode?
I cant think why you'd have it off while recording.
When you set Exposure Override to ON it automatically overrides the exposure simulation. Also disable Movie Mode ... Raw video works without having it enabled.
And turn OFF Exposure Lock and Exposure Presets
ExpSim has only 3 values: off, on or movie. Canon movie mode on 50D is fully automatic, no manual controls.
aahhh I see... I thought I needed movie mode turned on, for the raw video to work. (which is part of where I got stuck)
Makes sense, thanks guys!
I'll give it another try tomorrow.
If you guy's really wanna know what the 50D in capable of them you need to watch this video. It's by far one of the best video's I've seen from the beloved 50D I don't the 5D Mark III can hang 50D is more filmic. Check it out guy's let me know what you think.
Just been doing some testing at 1592x896 and 25fps
I can get constant recording with the following settings:
Global draw on
Focus peaking on
Sound mode off
Hacked mode on
ISO 500
If I raise the ISO any further then it skips frames.
Has anybody tried silent pics lately? I was wondering what the max resolution in 5x zoom mode is.
Quote from: goldenchild9to5 on June 04, 2013, 03:57:58 PM
If you guy's really wanna know what the 50D in capable of them you need to watch this video. It's by far one of the best video's I've seen from the beloved 50D I don't the 5D Mark III can hang 50D is more filmic. Check it out guy's let me know what you think.
it looks great and shows quite well the enormous capabilities of the 50D. nice example you found.
though you can still recognize moire in detailed shots like the first even in 1592 x 724. of course its much better
than in 1280 width which was the max. resolution i was able to test at the moment.
maybe the chromatic aberration remove tool in ACR could help?
has anyone tested it yet?
P.S. shouldn't sound like too much critics, i more than love the look, the 50d produces :D
P.S.
@ goldenchild9to5
did you shot "venice beach" or did you found it?, wasn't sure:)
somehow or other, nice you shared it.
Wonderful works on the hack!
I haven't got a fast card yet. Just got a cheap 600x silicon power, only give me 38m/s. Komputerbay on its long way (10days to AU)!
One question for 1988X1052 in 5x crop mode. Despite of its pinky appearance, actual image seems cover more than the live view display. Is there any possiblity to have a full frame monitoring in crop mode?
Here is a fast test on resolution of my old Tarmon 400/6.3 in 5X mode, 1988X1052, cropped and letter box (basically all black though) to 1920X1080. Noticing the thumbnail is the display from the live view when I shot it, but the actual image recorded is much wider (nearly 2x wider).
Update: Never mind. I found the exact cover here: http://www.magiclantern.fm/forum/index.php?topic=5441.msg44398#msg44398
But still, if we can have a actual frame monitoring would be good for tele-shots. I am afraid it's too much to tweak.
Quote from: Ifani on June 04, 2013, 04:59:04 PM
P.S.
@ goldenchild9to5
did you shot "venice beach" or did you found it?, wasn't sure:)
somehow or other, nice you shared it.
I didn't shoot the video I just found it, to me the images are just perfect. 50D does not produce that much aliasing, or moire from all the test I've done and the lower than 1080p Resolution and the way it processes the images gives it that softness roundness to the image which the 5D Mark III don't have.
Quote from: goldenchild9to5 on June 04, 2013, 03:57:58 PM
If you guy's really wanna know what the 50D in capable of them you need to watch this video. It's by far one of the best video's I've seen from the beloved 50D I don't the 5D Mark III can hang 50D is more filmic. Check it out guy's let me know what you think.
Thanks goldenchild, that's my video. I'm amazed at the images that the 50D produces in RAW. Yes, there is still moire; it's especially bad around the houses in the first shot, but overall I'd say moire isn't a big problem. I didn't try the CA tool, but that might take care of some of the color noise.
Jason
Quote
Thanks goldenchild, that's my video. I'm amazed at the images that the 50D produces in RAW. Yes, there is still moire; it's especially bad around the houses in the first shot, but overall I'd say moire isn't a big problem. I didn't try the CA tool, but that might take care of some of the color noise.
Jason
Indeep I liked it....very filmic images......probably with Luxury line lens you could reduce even more the moire and get fantastics images......I just wish i had my camera to do some test with my LOMO lens......a little bit more of patience!!
Quote from: jchristman on June 04, 2013, 06:18:05 PM
Thanks goldenchild, that's my video. I'm amazed at the images that the 50D produces in RAW. Yes, there is still moire; it's especially bad around the houses in the first shot, but overall I'd say moire isn't a big problem. I didn't try the CA tool, but that might take care of some of the color noise.
Jason
No problem Christman was such a beautifully shot video I had to post 8) By the way do you use the "Hacked Mode On" or you just leave it on off. Lastly what FPS did you set you AE Comp to? 24fps, or 23.976fps Keep those video's coming..
Guy's let's keep the donations flowing we are only $25 away from achieving goal, Let's go 50D community. Developer @1% is counting on us to make it happen & also developer @Gregory. For more info Please contact @JulianH he will forward you all the info thank you.
Hey team.
50D finally arrived this afternoon. ;D CF card is Sandisk Extreme 32GB 60Mb/s. With this in mind I just went for a 1280 x 720 workflow. Just wanted to try and get my head round it all. Have included the video below, not to show what this camera can do as others have done that far better!!! This is my first go at the whole thing. Pretty exciting times! Currently in a cast and on crutches but hoping to get out and about to get some decent footage tomorrow.
Was running fine at these settings. Can not get Komputer bay sent to NZ. Looking round for others.
For now, here is a beer for all the hard working Magic Lantern crew! Can't send beer through the post to 1% but lets get that card to him!
https://vimeo.com/67630114
Quote from: John-Jo on June 04, 2013, 07:23:33 PM
Hey team.
50D finally arrived this afternoon. ;D CF card is Sandisk Extreme 32GB 60Mb/s. With this in mind I just went for a 1280 x 720 workflow. Just wanted to try and get my head round it all. Have included the video below, not to show what this camera can do as others have done that far better!!! This is my first go at the whole thing. Pretty exciting times! Currently in a cast and on crutches but hoping to get out and about to get some decent footage tomorrow.
Was running fine at these settings. Can not get Komputer bay sent to NZ. Looking round for others.
For now, here is a beer for all the hard working Magic Lantern crew! Can't send beer through the post to 1% but lets get that card to him!
https://vimeo.com/67630114
Congrats John.. Great video look good @ 720p looks like a commercial. You forgot to mention @Gregoryofmanhattan he put in a lot of work on this lastest build that we are currently using.
I've been having a great time with a KomputerBay 32GB 1000x CF card - being able to shoot continuously at max resolution. Unfortunately, the same can't be said for my new KomputerBay 1000x 128GB card. It typically stops recording around 250 frames every time. Seems to max out at 48 MB/s where as my 32GB card runs smoothly at around 57 MB/s. - Are the 128GB cards known to be bad? Or could it be that I'm doing something wrong?
Quote from: paulforte on June 04, 2013, 08:08:48 PM
I've been having a great time with a KomputerBay 32GB 1000x CF card - being able to shoot continuously at max resolution. Unfortunately, the same can't be said for my new KomputerBay 1000x 128GB card. It typically stops recording around 250 frames every time. Seems to max out at 48 MB/s where as my 32GB card runs smoothly at around 57 MB/s. - Are the 128GB cards known to be bad? Or could it be that I'm doing something wrong?
The KomputerBay 128GB seems to be slower don't know why but it is..
Quote from: paulforte on June 04, 2013, 08:08:48 PM
I've been having a great time with a KomputerBay 32GB 1000x CF card - being able to shoot continuously at max resolution. Unfortunately, the same can't be said for my new KomputerBay 1000x 128GB card. It typically stops recording around 250 frames every time. Seems to max out at 48 MB/s where as my 32GB card runs smoothly at around 57 MB/s. - Are the 128GB cards known to be bad? Or could it be that I'm doing something wrong?
Yes. The 128GB cards are slower. You should have gotten 2 64GB 1000x . . . Send it back for refund or exchange maybe?
Quote from: menoc on June 04, 2013, 09:02:36 PM
Yes. The 128GB cards are slower. You should have gotten 2 64GB 1000x . . . Send it back for refund or exchange maybe?
Indeed - thanks. Just saw this post as well - http://www.magiclantern.fm/forum/index.php?topic=5391.msg34356#msg34356 - I'll return the 128 and go for the 64s.
Dear All
This is amazing. Huge thanks to everyone working on this!! I am a newbie here and was thinking about creating a summary help document for 50D users. I have had a interesting 5 days getting this working. My background is film cinema and this whole canon ML and Canon ML RAW is all new to me. So hopefully my ignorance can help write a better document for complete newbies to 50D RAW. Please amend / correct which I have had to figure out from reading various posts all over the place. Again I expect I have made some basic errors but this is draft 1...and if this has been done before then apologies.
Get a 50D - ideally with low shutter count - submit a picture from the camera to a site (search google for shutter count websites) to get the shutter count
Get fast CF cards (link here for reviews) but ideally a 4 x 64GB 1000x card
Format the card in camera
Copy the latest build for 50D to your computer drive - link here to latest build (not sure of best..) - (Note - Each CF card you use in the camera needs the build software since ML seems to reference the code on the CF card - is this correct?)
Copy the files to the CF card (Note for mac OSX users - The fast CF cards needs a USB3 reader - even if your machine only has USB2 ports. If you use USB2 readers with the fast cards then it endlessly mounts and dismounts - even in Disk Utility)
Put CF card with ML software into camera
Update firmware on camera - using standard canon menu
reboot camera - do this by power off and on
Press the TRASH button (this takes you into ML controls) on camera to check it has loaded correctly (click through messages using the wheel, set and mouse, centre mouse hold (figure out what does what -it is easy-ish)
The ML interface build should have a M tab - enable the modules and set to auto load - you should see a RAW modules
Reboot camera
Set camera to no RAW and S JPEG using standard Canon controls - this helps buffer sizes and makes ML video better going forward
Click TRASH - you are now in ML in video
Go to ML video tab - enable RAW (It might give you weird frame sizes - don't worry)
Go into Live View - press TRASH - amend RAW frame / fps settings by holding the mouse click button down for a few seconds
Set the frame rate to 24 or 25
Make sure camera battery is at least 20% - ML seems to go wonky on me sometimes below 20%
disable global draw - is this valid?
(note each time you reboot you need to set the RAW settings again - this is irritating but you learn how to do it quite quickly - is this correct)
Now this is where I get hazy - my film background says I need to light meter then set and lock exposure and ISO in camera and then adjust lighting to keep a constant F stop because otherwise the inconsistent DOF is distracting to audience (and it keeps my HMI rental companies in business :-)...
but the 50D seems to not easily allow me to lock F stop with canon standard lenses when shooting video... My newbie question here is "What is the easiest way to lock the camera with a canon lens to F4 at ISO 160 and 24fps - irrespective of reboots or mad changes in scene brightness?"
Is this why most videos using D50 and ML RAW do not use canon lenses. It seems you need a manual lens - I imagine there is a way to lock the F stop on a canon lens but i can't figure it out yet :-) - There seems to be some way using the * button but I can't always get it to work
Once you got footage
Download to computer - using USB3 reader for MAC OSX
Convert RAW sequence to DNG - I use RAW2DNG - drag and drop and builds directory in same place as RAW file - which is why I put it on a separate video hard drive
select all images and open in Photoshop CS5. This opens the RAW tool
Select all images
Tweak to taste - set exposure and colour temp - this is where it is amazing!!
Save as TIFF sequence - left hand menu
Cancel out of RAW CS5 tool then close Photoshop
Then bring into Resolve and grade!
Then be amazed at footage!!
Thanks
Rolfe Klement
creativesunshine.com
Quote from: goldenchild9to5 on June 04, 2013, 07:03:08 PM
Guy's let's keep the donations flowing we are only $25 away from achieving goal, Let's go 50D community. Developer @1% is counting on us to make it happen & also developer @Gregory. For more info Please contact @JulianH he will forward you all the info thank you.
Count me in, PM the details please
Just a few more tests.
KomputerBay 32GB card:
Full sensor in cropped mode (1592x1062): no frame drops. Excellent to choose framing at a later point, like Super35 mm.
5x zoom mode in 2.35:1 aspect ratio (1920x818) : no frame drops. Very nice, full HD shooting in Cinemascope possible!
5x zoom mode in 2.20:1 aspect ratio (1920x872): frame dropping. No 70mm aspect ratio available... :P
Sorry guys for interrupting. I´am new in the 50D (purchased this evening) land and after reading this forum through 33 pages, I got a question I can not solve. In the fps override I cant not get 24fps exact, the closer I get is 24.001fps, I tweaked the timers but it was no possible. Is the 24.001 the real 24fps or not?. Thanks to all.
Turn optimize for -> exact fps on in FPS Override Menu.
32GB Lexar and 64GB Komputerbay getting cinemascope
1920x720 with a build on Sunday (this mornings build is lower data-rate no more than 50MB/s on Komputerbay will not do cinemascope - things keep changing very quickly and there are few stable points).
makes a difference how the .raw file is processed.
for this type of thing, i use
ufraw-batch
have also tried RPP and Lightroom
ran a script to process through clips from Sunday - took 3 hours - have more to evaluate.
still noticing strange exposure and white balance shifts if i pan from bright to dark areas.
thought i had set ISO to daylight and locked other settings.
Quote from: GregoryOfManhattan on June 04, 2013, 11:44:26 PM
32GB Lexar and 64GB Komputerbay getting cinemascope
1920x720 with a build on Sunday (this mornings build is lower data-rate no more than 50MB/s on Komputerbay will not do cinemascope - things keep changing very quickly and there are few stable points).
makes a difference how the .raw file is processed.
for this type of thing, i use
ufraw-batch
have also tried RPP and Lightroom
ran a script to process through clips from Sunday - took 3 hours - have more to evaluate.
still noticing strange exposure and white balance shifts if i pan from bright to dark areas.
thought i had set ISO to daylight and locked other settings.
Great job Gregory this is beautiful footage man, Keep up the good work can't wait to get my hands on this build.
I did some more tests, this time with HDMI plugged in. I got strange pink frames every so often.
(https://dl.dropboxusercontent.com/u/24738031/ML/pink-frame.jpg)
Recorded at 1592x896 at 25fps
Same settings with HDMI unplugged and it was fine.
Quote from: Rolfe Klement on June 04, 2013, 11:03:47 PM
Dear All
Put CF card with ML software into camera
Update firmware on camera - using standard canon menu
reboot camera - do this by power off and on
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?
Yes you need to update the Canon firmware to 1.0.9 before installing ML, you can download it here:
https://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_50D.aspx?type=important&faqtcmuri=tcm:13-846249 (https://www.canon-europe.com/Support/Consumer_Products/products/cameras/Digital_SLR/EOS_50D.aspx?type=important&faqtcmuri=tcm:13-846249)
Quote from: briwil on June 05, 2013, 12:04:11 AM
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.
Quote from: CaptainOfObvious on June 05, 2013, 12:12:49 AM
I bought mine used with 1.0.7 on it aswell, updated to official firmware first THEN installed ML. It worked for me.
Ok, just checking; I couldn't get mine to update the firmware, getting the famous "Update file cannot be found. Please check the memory card and reload the battery and try again" message, not matter what card I used, or using EOS Utility. After scouring forums and seeing it happen to quite a few people over the years, and not seeing any solutions other than people saying they eventually sent their cameras in get checked out (and finding that, yes, there was a problem with the camera), I gave in myself and sent my new/used 50D that I got last week off to Canon yesterday to get looked at.
Just making sure I wasn't missing something in regards to this firmware thing. :-\
Quote from: CaptainOfObvious on June 05, 2013, 12:12:49 AM
On Another note, any word of get file spanning functional?
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.
Quote from: goldenchild9to5 on June 04, 2013, 07:38:46 PM
Congrats John.. Great video look good @ 720p looks like a commercial. You forgot to mention @Gregoryofmanhattan he put in a lot of work on this lastest build that we are currently using.
But of course! @Gregoryofmanhattan deserves a big thanks! And A1ex, JulianH and pretty much everyone one here!!
Never sure who is on for ML / helping with code, or what everyone's specific involvement is... however great community to be part of and big thanks all round. I know ZERO about code so made sure to donate as a way of hopefully helping out.
Currently only issue for me being the 2 batteries I got with the 50D are shot. The "good" one lasts bout 10 mins. 2 generic replacements en route. Fast CF card next on the list!
Does anyone know how I can get all these things in one Magic Lantern build for the 50D:
1. Anamorphic Preview,
2. the 3x zoom, and;
3. Raw recording.
Is it even possible? THANKS!
Quote from: Roman on June 05, 2013, 01:15:51 AM
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.
Wow Roman you figured it out that's awesome, When you convert to DNG it streamlines perfectly with no glitches right? just one smooth conversion? That is big new ;D Gonna give it a try later to see how it goes.
Quote from: John-Jo on June 05, 2013, 01:17:41 AM
But of course! @Gregoryofmanhattan deserves a big thanks! And A1ex, JulianH and pretty much everyone one here!!
Never sure who is on for ML / helping with code, or what everyone's specific involvement is... however great community to be part of and big thanks all round. I know ZERO about code so made sure to donate as a way of hopefully helping out.
Currently only issue for me being the 2 batteries I got with the 50D are shot. The "good" one lasts bout 10 mins. 2 generic replacements en route. Fast CF card next on the list!
You definitely right thanks to everyone contributing & this whole ML forum. 10mins is just a tease, when the new ones come in you'll be good to go.
Quote from: Roman on June 05, 2013, 01:15:51 AM
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.
So Roman if you have more that two spanned clips than you add another + right..
and here's my first noob question: i'm trying to put the ML files onto my komputerbay 64gb CF and for some reason i can't even get my macbook pro to read the card. tried the same card on my gf's mbp and it won't read it either. is this a dead card or am i missing a step to make the card readable?
NOTE: the other CF card i have (an old/slow lexar that came with the 50D) works/reads just fine and allowed me to install ML 2.3. haven't bothered to try to install the raw modules/autoexec.bin files on a card this slow.
Quote from: eattheblinds on June 05, 2013, 02:09:05 AM
and here's my first noob question: i'm trying to put the ML files onto my komputerbay 64gb CF and for some reason i can't even get my macbook pro to read the card. tried the same card on my gf's mbp and it won't read it either. is this a dead card or am i missing a step to make the card readable?
NOTE: the other CF card i have (an old/slow lexar that came with the 50D) works/reads just fine and allowed me to install ML 2.3. haven't bothered to try to install the raw modules/autoexec.bin files on a card this slow.
Does your camera read it? Format the KomputerBay card in camera. Press canon menu button and scroll to third option you should see it. If that don't work than your CF card might be bad, or your card reader might not be working.
Quote from: goldenchild9to5 on June 05, 2013, 02:27:56 AM
Does your camera read it? Format the KomputerBay card in camera. Press canon menu button and scroll to third option you should see it. If that don't work than your CF card might be bad, or your card reader might not be working.
yes, my camera reads the card and i'm able to format it in the camera. but when i plug the card/card reader into my mbp...nothing. even when i look into the system profiler there's no card. when i look on disk utility, again...no card.
There might be something wrong with your card reader than, if the camera reads it it should load on your mbp..
Quote from: goldenchild9to5 on June 05, 2013, 02:58:09 AM
There might be something wrong with your card reader than, if the camera reads it it should load on your mbp..
i guess there's only one way to find out. i've got a usb 3.0 card reader being shipped. this doesn't appease an impatient man itching to shoot raw video.
I feel you that's how I was waiting for my 50D and card to come in. You gotta have a friend that have a spare CF card reader give them a call that's the oldest trick in the book.
Quote from: Roman on June 05, 2013, 01:15:51 AM
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.
Quote from: CaptainOfObvious on June 05, 2013, 04:04:10 AM
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 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.
Quote from: a1ex on June 04, 2013, 03:33:55 PM
ExpSim has only 3 values: off, on or movie. Canon movie mode on 50D is fully automatic, no manual controls.
Can you explain this for me? Does this mean that in all modes for 50D ML, there are no manual controls? Sorry if my newness is causing unecessary time to answer questions. thanks.
Quote from: wesleydumont on June 05, 2013, 04:58:53 AM
Does this mean that in all modes for 50D ML, there are no manual controls?
No, but that's what I initially thought as I had the settings wrong...
When you are shooting a regular H264 movie with the 50D, there are no manual controls.
When you are shooting a raw video however, you dont even need to be in movie mode... it can sample the frames from the live view screen in photo mode.
So you can set the exposure time and ISO etc as you would for a picture (with exposure compensation turned on) and it operates as per the settings you've put in there.
However I've noticed that if I choose an exposure of say 1/10th of a second when I'm recording at 24fps, it still brightens the screen towards that... which it shouldnt, I dont know what it does to the raw file when you do this.
So just be mindful of setting the exposure length to some amount below the indicated frame rate.
I'm not sure how fps override affects the indicated exposure length though, whether it's accurate for 30fps only.
Tried deleting files in camera - some I could delete but then "no images to display" came up but top LCD said card had only 2 remaining shots. 32 GB Sandisk extreme. Just wanted to make some space for more shooting but failed. Tried to record anyway and would let me get a few frames before it cut out. Got home and it was full CF. Also tried deleting in Canons menu, first time round I was in ML, hitting play, to select, then trash to delete.
Q's:
1: Can you review, not play but just delete in camera with files actually being deleted not just hidden?
2: Is this a known issue or have I got a setting checked /unchecked somewhere?
- don't think I've read it anywhere in this thread, forgive me if it is in here though, just so much data been written into my brain right now I may be the one with dropped frames etc!
Thanks for any input. :)
Quote from: artiswar on June 05, 2013, 04:48:37 AM
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.
Quote from: necronomfive on June 04, 2013, 11:33:31 PM
Turn optimize for -> exact fps on in FPS Override Menu.
Thanks man. Solved it!!!!
Hi eattheblinds,
Quote from: eattheblinds on June 05, 2013, 02:09:05 AM
and here's my first noob question: i'm trying to put the ML files onto my komputerbay 64gb CF and for some reason i can't even get my macbook pro to read the card. tried the same card on my gf's mbp and it won't read it either. is this a dead card or am i missing a step to make the card readable?
NOTE: the other CF card i have (an old/slow lexar that came with the 50D) works/reads just fine and allowed me to install ML 2.3. haven't bothered to try to install the raw modules/autoexec.bin files on a card this slow.
I had the same problem: the FAT32 filesystem of the 64 GB (KomputerBay 600x) not being accessible via a Transcend USB 3 CF card reader--but through an old Microtrack (at abyssmal "speed"). Possibly it's the size! Trying a 32 GB card soon. Let's see if that solves the issue.
Hi Roman,
Quote from: Roman on June 05, 2013, 05:06:42 AM
When you are shooting a regular H264 movie with the 50D, there are no manual controls.
it does not seem to be so for me. I can set ISO, aperture & fps just fine.
ML has manual controls with expo override (see the help).
Quote from: a1ex on June 05, 2013, 09:57:05 AM
ML has manual controls with expo override (see the help).
In ML we TRUST ;D
When I open the DNG´s in ACR, I see the images way out of the WB and tint I suppose to shot. Although it is easy to fix in ACR, I was wondering if it is possible to keep the WB values I choose while shooting?. The 5D2, that I also use, do not show that weird tint when imported in ACR. Thanks.
Feel free to implement all those matrix multiplications for proper WB info (just look at dcraw/ufraw code)
;)
the basic CAM_COLORMATRIX values are and have been same as those in ufraw-0.19.2 for some time.
if these are inaccurate, correcting them should also be done in ufraw.
does any one else perceive the white balance values changing from camera settings during a shot -
particularly on shots with camera movement (or scene change) from bright to dark?
That matrix (and others) should be used when converting from kelvin to RGB multipliers. See Temperature_to_RGB from ufraw source code - if you can port that, plug the kelvin value and get the multipliers. No idea about green/magenta shift though.
Quotedoes any one else perceive the white balance values changing from camera settings during a shot -
particularly on shots with camera movement (or scene change) from bright to dark?
I don't remember any confirmation for fixing black level and skip offsets. Did you post the silent pic DNG I've asked for a while ago?
My first 1920 x 1080 test on line.
https://vimeo.com/67720156
Shot at 1576 x 880. 24 fps. 0.9 bit rate. Canon 50mm F/1.8. Sandisk Extreme 32GB 60Mb/s.
raw2dng>AE: scaled and light grade. 16 bit. scaled by 122% to 1920x1080> exported as ProRes 422HQ>FCP7 Light grade / cut.
https://vimeo.com/67720156
Quote from: John-Jo on June 05, 2013, 01:54:11 PM
My first 1920 x 1080 test on line.
https://vimeo.com/67720156
Shot at 1576 x 880. 24 fps. 0.9 bit rate. Canon 50mm F/1.8. Sandisk Extreme 32GB 60Mb/s.
raw2dng>AE: scaled and light grade. 16 bit. scaled by 122% to 1920x1080> exported as ProRes 422HQ>FCP7 Light grade / cut.
https://vimeo.com/67720156
How many frames did you get before skipping?
Btw, looks very 16mm ;)
Hey guys,
I received my Komputerbay 32GB 1000x card today. Now, everything runs stable. It records until the card is full. Except for some times, when the buffer was filled just after 1 second. No idea what the reason for that may be.
The problems I am facing right now are on a post production site.
1. I have the impression that raw2dng.exe is not able to convert files bigger than 2GB. Can anybody confirm that? Is there a way to get around this? Any alternatives to this program?
2. I can record over 4GB without a problem. The problem however is, that the files are packed into a .WINrar file, which I can not access for whatever reason. Any solutions for that?
Another thing: Who do I have to contact in order to donate ML?
Best regards!
It's not a winrar file - It's just that R00 R01 etc are also file extensions that spanned .RAR files use.
In this case instead its first .raw, then .r00, then .r01, etc.
Basically you need to merge the files back into one, using a dos command or similar in before you can decode them to dng files.
Thanks for your reply! Can you give instructions on how to do that?
Do you have a way to convert .raw files with a file size bigger than 2GB?
Quote from: a1ex on June 05, 2013, 01:20:50 PM
I don't remember any confirmation for fixing black level and skip offsets. Did you post the silent pic DNG I've asked for a while ago?
mentioned on another thread - have Silent Pics and took 2 DNGs after setting skips to 0 - one default, one zoom mode.
inserted measured skip values into src/raw.c now in unified branch.
tested zoom and regular video no longer have wild black point (fixable in gimp or RPP).
zoom mode test video - https://vimeo.com/67680036 ( ufraw-batch -a ) color slightly magenta - roses were a little less pink to my eye.
i see some cameras have different skip values for mv1080 and mv720 - which i don't think apply to 50D.
is there value in testing this further -
zoom at different aspect ratios?
zoom with box top left vs. center (wonder about this because of some comments on color changes when using raw panning)?
please let us know how much additional testing should be done and i will send a zero skip build to some of the experienced testers.
Quote from: CaptainOfObvious on June 05, 2013, 06:38:05 AM
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.
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. I also tried adding the footer to the second file in the sequence and renaming it with the .RAW extension. raw2dng recognizes it and it extracts all the DNGs properly but they all look corrupt as in the second example below. This leads me to believe that there is something in the code to write the DNG that is causing the corruption. Here's an example of the DNGs:
Here's a link to the original DNGs:
https://www.dropbox.com/s/bg9wu6ykuprui77/001715.dng (https://www.dropbox.com/s/bg9wu6ykuprui77/001715.dng)
https://www.dropbox.com/s/6gyg4hvsbqeicwf/001716.dng (https://www.dropbox.com/s/6gyg4hvsbqeicwf/001716.dng)
This is the last DNG in the first file in the file spanning sequence (M04-1458.RAW):
(http://i.imgbox.com/aciw00i4.jpg)
This is the first DNG in the second file in the file spanning sequence (M04-1458.R00):
(http://i.imgbox.com/abrJLJRM.jpg)
Here's what the header of the good DNG looks like:
(http://i.imgbox.com/abvm4PEy.png)
And here's the header of the corrupt DNG:
(http://i.imgbox.com/abtiPQqR.png)
Known issue that needs to be fixed...
@menoc and @savale spanning is much better on later builds - though i still do see frames like the posted example
Quote from: GregoryOfManhattan on June 05, 2013, 04:17:21 PM
@menoc and @savale spanning is much better on later builds - though i still do see frames like the posted example
Do tell . . . Is there a better build than the May 28th for the 50D? . . . I guess not for the 50D
Been a lurker on this thread for a while but I've just received my 50d + Transcend 32gb 1000x card today and would love to help with testing once I get everything up and running.
Quote from: a1ex on June 04, 2013, 03:33:55 PM
ExpSim has only 3 values: off, on or movie. Canon movie mode on 50D is fully automatic, no manual controls.
on 50D, doesn't Exp. Override permit manual operation, per the 2.3 user guide - http://wiki.magiclantern.fm/userguide#exposure-override ?
Quote from: GregoryOfManhattan on June 05, 2013, 06:19:36 PM
on 50D, doesn't Exp. Override permit manual operation, per the 2.3 user guide - http://wiki.magiclantern.fm/userguide#exposure-override ?
Yes we have manual controls Exp. Override permits that. I found that out last night after playing around with the camera.
It would be really perfect to get spanning to work.
Finally a test:
http://vimeo.com/67713580
Some flicker from ACR Process 2012 but will switch to 2010 to alleviate the issue.
I've been lurking here for a while. (At the moment still not a 50D owner.) I want to say, that's some really nice footage, Artiswar! What resolution(s) did you use?
Quote from: mva on June 05, 2013, 06:59:20 PM
I've been lurking here for a while. (At the moment still not a 50D owner.) I want to say, that's some really nice footage, Artiswar! What resolution(s) did you use?
That was all the maximum 16:9 resolution so 1592 x 896. Upscales to 1080p, log look applied in ACR and a quick grade in Premiere. I think the secret to the sharpness I achieved was the Zeiss glass.
Quote from: Fioritura on June 05, 2013, 09:29:37 AM
Hi eattheblinds,
I had the same problem: the FAT32 filesystem of the 64 GB (KomputerBay 600x) not being accessible via a Transcend USB 3 CF card reader--but through an old Microtrack (at abyssmal "speed"). Possibly it's the size! Trying a 32 GB card soon. Let's see if that solves the issue.
hmmm...i'm using a cheap-o bower usb2.0 reader i bought in chinatown. i expected it to be the culprit so i bought a USB3.0 off newegg and it should arrive soon. i wonder if i'll have better luck or if this is a more persistent problem.
komputerbay is getting back to me with tech support. fingers crossed there's a solution i'll be able to share.
Quote from: menoc on June 05, 2013, 04:01:10 PM
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.
Quote from: GregoryOfManhattan on June 05, 2013, 04:17:21 PM
@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.
Can anyone confirm if they've broke the hard limit of 60 MB/s with the 50D?
Hello all,
First, THANK YOU to all the devs making this work! :D
I made a comparison video to show the difference between raw and h.264 on the 50D. I wanted to see how far both formats could be pushed. I started by grading the raw, then graded the h264 to match. I was surprised by some of the results!
Workflow:
Raw clips turned to .dng sequences with RAWanizer, then imported into After Effects (which prompts Adobe Camera Raw. Interpret footage: 24p. (Note: if you want to retune raw, Interpret Footage, More Options to relaunch ACR.)
Sequences dropped into AE comp, exported to QT Uncompressed 10 bit 422. (This took 2 hours for an 11 minute sequence, but edited smoothly in Premiere.)
Then edit in Premiere, where the h.264 clips were graded to match. Shadow/Highlight is causing most of the breakup you'll see. A very twitchy effect sometimes.
h.264:
1920X1080
Profile: Faithful
Graded with Premiere CS6:
-Three Way Color
-Shadow/Highlight
-Sharpen
No noise reduction
Cropped to 2.35:1
RAW:
1440x612 (2.35:1)
Graded in
Adobe Camera Raw
with Noise Reduction
Upscaled in Premiere
Note: I was limited to 1440x612 in Raw mode (which is 2.35:1, 35MB/s at 24p) because of the limitations of my CF card- a Lexar 32GB 800x. I now have a Komputerbay 64GB 1000x card which is capable of handling the 50D's current maximum resolution in RAW: 1592x896 (16:9, 57MB/s at 24p).
VIDEO HERE
http://www.youtube.com/watch?v=U5jqmgtf4YA
Thank you again, everyone! I'm so grateful for this new format! And I love this forum. So many good people and great information! :)
Not a raw question, but how would you shoot a music video with the 50D? I would love an easy way to record scratch audio.
Quote from: johansugarev on June 05, 2013, 09:15:10 PM
Not a raw question, but how would you shoot a music video with the 50D? I would love an easy way to record scratch audio.
ALL audio with the 50D has to be done externally. You may have to slate. Many options out there . . .
have sent out the following email to a dozen registered testers
hi 50D testers,
per a1ex request, we need to confirm the black borders on DNGs generated in Silent Pics mode.
http://www.magiclantern.fm/forum/index.php?topic=5586.msg46436#msg46436
i have made a special build to do this - it's not intended for general shooting and most .raw files will have the black borders and crazy colors.
it is to put the camera in Silent Picture mode, take single silent pictures, and get the exact pixel count of any black borders.
this build has set the borders to 0 - hence the name NULL-05June13
if you haven't loaded new builds onto an existing card before, be careful, format it first and delete the ML config file.
not all of us need to do this, so whoever has time tonight should give it a go and report results on the forum.
the values that look correct to me are:
default image size -
top 26
left 74
right 0
bottom 0
in 5x zoom mode
top 0
left 74
right 0
bottom 0
please shoot some Silent DNGs and report back any discrepancies.
it may be helpful to confirm that nothing changes in the other cases:
- try 10x zoom
- move the zoom box to various positions top,left, center, bottom right (didn't JulianH report that thee borders changed when he did a raw video pan?).
- turn on raw_rec and try at various aspect ratios - i'm not even sure this will give images of different resolutions, if it does check for black borders.
the code assumes that these values are always the same, so if they are not there will be black borders.
this build may be slower that 28May13
file spanning will work.
.raw files will all have the black border issue.
weird things may happen with HDMI.
please refer back to forum post and provide credit in any public video.
regards,
Quote from: GregoryOfManhattan on June 05, 2013, 03:26:18 PM
mentioned on another thread - have Silent Pics and took 2 DNGs after setting skips to 0 - one default, one zoom mode.
inserted measured skip values into src/raw.c now in unified branch.
tested zoom and regular video no longer have wild black point (fixable in gimp or RPP).
zoom mode test video - https://vimeo.com/67680036 ( ufraw-batch -a ) color slightly magenta - roses were a little less pink to my eye.
i see some cameras have different skip values for mv1080 and mv720 - which i don't think apply to 50D.
is there value in testing this further -
zoom at different aspect ratios?
zoom with box top left vs. center (wonder about this because of some comments on color changes when using raw panning)?
please let us know how much additional testing should be done and i will send a zero skip build to some of the experienced testers.
Complete noob question. I have posted a HOW to 50D draft guide before but need help on this one section
"ML has manual controls with expo override (see the help)."
I cannot get this to work. I get a message saying cannot lock the aperture. All my test videos prove this. I want to lock the camera to ISO 160, F4 and 24fps. I get weird exposure and colour shifts - this might be a bug issue. can do the FPS override using the exact FPS so that works - but not the other bits. I have EXP lock set to AV, 150
EXPO - PRESETS OFF
Expo override ON
Camera in M mode
Can someone explain step by step how this should be done. I am probably doing something silly 8)
thanks a mill!
Quote from: eattheblinds on June 05, 2013, 02:32:50 AM
yes, my camera reads the card and i'm able to format it in the camera. but when i plug the card/card reader into my mbp...nothing. even when i look into the system profiler there's no card. when i look on disk utility, again...no card.
And if you plug the camera to your mbp with a usb cable?
I'm just thinking out loud....
Could it be possible to use the raw in dxo?
I got it with the film pack, i don't know if it could render that many image at the same time ?
But a movie developed like a polaroid or velvia would be, like sh*t :)
Has anybody experience better performance with the Canon setting: silent mode1 for live view shooting?. I feel it faster, maybe not much, do not know if it could alter performance (¿¿¿). One of the advantages of this setting is that you can put safely PL mount lenses, and this option for the 50D RAW could be super cool.
UPDATE: Don´t try it. Crash when recording (in mode 2)
Quote from: araucaria on June 05, 2013, 02:12:07 PM
How many frames did you get before skipping?
Btw, looks very 16mm ;)
Thanks!
Don't think I got over about 192 frames before buffer got full. The card is too slow- but just wanted to play with this resolution.
Finally I have my CF card (KomputerBay 64 GB 1000x). I loaded ML for the first time ("Success! BOOTDISK flag is enabled" etc). Going into the M menu I highlight "Load modules now..." but I can't load anything. Pressing the Set button doesn't do anything, so I can't load the Smeangol module. Any ideas what's gone wrong? Thanks.
Quote from: TrueIndigo on June 05, 2013, 11:25:27 PM
Finally I have my CF card (KomputerBay 64 GB 1000x). I loaded ML for the first time ("Success! BOOTDISK flag is enabled" etc). Going into the M menu I highlight "Load modules now..." but I can't load anything. Pressing the Set button doesn't do anything, so I can't load the Smeangol module. Any ideas what's gone wrong? Thanks.
Is your Camera in M mode? . . . Did you turn LiveView ON? . . . Did you add the Modules directory to the ML directory? . . . Did you make the card scriptable?
Quote from: TrueIndigo on June 05, 2013, 11:25:27 PM
Finally I have my CF card (KomputerBay 64 GB 1000x). I loaded ML for the first time ("Success! BOOTDISK flag is enabled" etc). Going into the M menu I highlight "Load modules now..." but I can't load anything. Pressing the Set button doesn't do anything, so I can't load the Smeangol module. Any ideas what's gone wrong? Thanks.
Use the 28May build by Gregory. It is linked in the first post of the topic!
You have to scroll down in the movie tab to enable raw shooting (after loading the modules).
I'm happy to see the progress being made - some nice footage being posted. I'm still trailing behind with a 1000x komputerbay 64gb card that won't seem to run at more than about 45mb/s -- meaning that 1280x720 is the best I can capture with no frame drops.
I'm running the 5/28 build -- and I think I've done all the things I see you all doing to smooth performance:
- FPS override for 24fps (optimize for exact)
-Global Draw on for LiveView
- Hacked Mode ON
While I don't expect things to be the same as the 5dm3 envt - that same card runs at 75+mb/s in that camera raw.
Am I right to be thinking that others with the same card are getting continuous capture at 1592x896? (or maybe you are dropping frames and just posting short shots that worked?)
Thanks for any tips
Thanks for the quick replies.
Menoc: was the camera in M mode -- yes. In live view -- yes. Added the modules to the ML folder -- yes (the Smeangol modules). Did I make the card scriptable -- no. Please tell me how to do that.
JulianH: Use the 28may build by Gregory -- yes, that is the one I'm using (50-2013May28build.zip). Scroll down the movie tab to enable raw shooting -- yes, because I can't load the modules, they are not yet listed in the movie tab.
I made an empty "scripts" folder within the ML folder as it was mentioned this stops the warning about no scripts. Would that make a difference?
Quote from: dhallowell19 on June 06, 2013, 12:50:50 AM
I'm happy to see the progress being made - some nice footage being posted. I'm still trailing behind with a 1000x komputerbay 64gb card that won't seem to run at more than about 45mb/s -- meaning that 1280x720 is the best I can capture with no frame drops.
I'm running the 5/28 build -- and I think I've done all the things I see you all doing to smooth performance:
- FPS override for 24fps (optimize for exact)
-Global Draw on for LiveView
- Hacked Mode ON
While I don't expect things to be the same as the 5dm3 envt - that same card runs at 75+mb/s in that camera raw.
Am I right to be thinking that others with the same card are getting continuous capture at 1592x896? (or maybe you are dropping frames and just posting short shots that worked?)
Thanks for any tips
Set the following:
ISO: 100-200 (actually the ISO Does not matter so much use whatever ISO you need)
FPS override: 23.988 (Don't use 24 exact, use optimized for low light instead)
Canon Menus:
Set Qualiy to: JPEG Large Only - NO RAW
Settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: set it to "LiveView" (Turn off peaking and all other global draw settings)
RAW Video Settings:
Raw Video Resolution: 1600 (it will default to 1592)
Raw Video Ratio: 3:2 or 16:9
Sound: OFF
Hacked Mode: ON
Shoot something for a while . . . . 1600 resolution & 16:9 ratio is the most stable.
Quote from: TrueIndigo on June 06, 2013, 01:04:53 AM
Thanks for the quick replies.
Menoc: was the camera in M mode -- yes. In live view -- yes. Added the modules to the ML folder -- yes (the Smeangol modules). Did I make the card scriptable -- no. Please tell me how to do that.
JulianH: Use the 28may build by Gregory -- yes, that is the one I'm using (50-2013May28build.zip). Scroll down the movie tab to enable raw shooting -- yes, because I can't load the modules, they are not yet listed in the movie tab.
I made an empty "scripts" folder within the ML folder as it was mentioned this stops the warning about no scripts. Would that make a difference?
Use EOSCard tool in Windows, or Macboot in OSX.
As a matter of interest in the Debug menu I checked the shutter count, which says: "ok = 379+66". Can you tell me what that actually means as a shutter count (there are two figures). The seller said the camera was hardly used...
Menoc: Use EOSCard tool -- does that mean starting from scratch: make the card scriptable and then copy ML across again?
Many thanks for your help.
Quote from: TrueIndigo on June 06, 2013, 01:17:13 AM
As a matter of interest in the Debug menu I checked the shutter count, which says: "ok = 379+66". Can you tell me what that actually means as a shutter count (there are two figures). The seller said the camera was hardly used...
Your shutter has been actuated about a little over 400 times.
Quote from: GregoryOfManhattan on June 05, 2013, 10:06:07 PM
have sent out the following email to a dozen registered testers
hi 50D testers,
per a1ex request, we need to confirm the black borders on DNGs generated in Silent Pics mode.
http://www.magiclantern.fm/forum/index.php?topic=5586.msg46436#msg46436
i have made a special build to do this - it's not intended for general shooting and most .raw files will have the black borders and crazy colors.
it is to put the camera in Silent Picture mode, take single silent pictures, and get the exact pixel count of any black borders.
this build has set the borders to 0 - hence the name NULL-05June13
if you haven't loaded new builds onto an existing card before, be careful, format it first and delete the ML config file.
not all of us need to do this, so whoever has time tonight should give it a go and report results on the forum.
the values that look correct to me are:
default image size -
top 26
left 74
right 0
bottom 0
in 5x zoom mode
top 0
left 74
right 0
bottom 0
please shoot some Silent DNGs and report back any discrepancies.
it may be helpful to confirm that nothing changes in the other cases:
- try 10x zoom
- move the zoom box to various positions top,left, center, bottom right (didn't JulianH report that thee borders changed when he did a raw video pan?).
- turn on raw_rec and try at various aspect ratios - i'm not even sure this will give images of different resolutions, if it does check for black borders.
the code assumes that these values are always the same, so if they are not there will be black borders.
this build may be slower that 28May13
file spanning will work.
.raw files will all have the black border issue.
weird things may happen with HDMI.
please refer back to forum post and provide credit in any public video.
regards,
My resultsFull sensorSilent DNG: 1664x1084
Top 26
Left 74
Right 0
Bottom 0
5x zoom modeSilent DNG: 2064x1106
Top 26
Left 64
Right 0
Buttom 0
Weird that we get different results here. But I suppose that has to do with the 2064 width I get for Silent DNG's in zoom mode. In Raw video mode 1920x1104 I get 26 black pixel rows on top, zero on the other sides.
10x zoom testSilent DNG: Gives the same image and result as 5x, doesn't seem to change anything.
Other observationsNot sure if all relevant, but I'll notice them just in case.
Raw video speeds look the same to me as the 28May build. But my card is the bottleneck around 59Mb/s max (Sandisk 90MB/s 32GB).
Shoot_Malloc_total seems to have grown. It reports 219M, I thought it was max. 212M with the other build. Contig = 27M.
- try 10x zoomRecording raw video in 10x zoom gives garbadged results, just funky lines. But it looks like it's actually doing something different than in 5x.
- move the zoom box to various positions top,left, center, bottom
right (didn't JulianH report that thee borders changed when he did a
raw video pan?).I don't think I reported this, didn't have this experience. Didn't test it with the 05June build yet.
- turn on raw_rec and try at various aspect ratios - i'm not even sure this will give images of different resolutions, if it does check for black borders.It does give different resolutions. No surprise with the black borders here. With max image size it's the same as in silent DNG and when cropping down to other aspect ratios the black lines disappear (when they are cropped out by lower height).
Quote from: TrueIndigo on June 06, 2013, 01:19:56 AM
Menoc: Use EOSCard tool -- does that mean starting from scratch: make the card scriptable and then copy ML across again?
Many thanks for your help.
Making scriptable does not require starting over. Just insert the card check the option for scriptable and tell it to prepare the card.
QuoteContig = 27M.
This is what is eating at your writes.
Quote from: menoc on June 06, 2013, 01:07:37 AM
Set the following:
ISO: 100-200 (actually the ISO Does not matter so much use whatever ISO you need)
FPS override: 23.988 (Don't use 24 exact, use optimized for low light instead)
Canon Menus:
Set Qualiy to: JPEG Large Only - NO RAW
Settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: set it to "LiveView" (Turn off peaking and all other global draw settings)
RAW Video Settings:
Raw Video Resolution: 1600
Raw Video Ratio: 3:2 or 16:9
Sound: OFF
Hacked Mode: ON
Shoot something for a while . . . . 1600 resolution & 16:9 ratio is the most stable.
Thanks for the notes - I've done every single thing quite carefully -- and the card tops out at about 44mb/sec -- and drops frames after about 300 with raw resolution set at 1600.
For the komputerbay 1000x 64 GB card, what write rates are others seeing using those settings? I had a second of that same card which performed exactly the same. I guess i could have seen two dud cards - but I'm thinking it's something else that has me crawling where others are having better luck.... many thanks for the group's patience and tips...
Quote from: dhallowell19 on June 06, 2013, 01:47:19 AM
Thanks for the notes - I've done every single thing quite carefully -- and the card tops out at about 44mb/sec -- and drops frames after about 300 with raw resolution set at 1600.
For the komputerbay 1000x 64 GB card, what write rates are others seeing using those settings? I had a second of that same card which performed exactly the same. I guess i could have seen two dud cards - but I'm thinking it's something else that has me crawling where others are having better luck.... many thanks for the group's patience and tips...
Did you set the ratio to 16:9? . . . Otherwise, format and benchmark the card in Camera and post your results. I have the same card, here are my results. If yours do not look like these, then you have a dud :P:
(http://i.imgbox.com/acrP0LHK.jpg)
@menoc - Here's something odd, but good, that happened...when I formatted the card in the camera for this run of the tests (even though I'd done that before) -- for some reason the performance numbers jumped from the 30s and 40s to this higher range. It looks more like your card.
NOW when shooting raw, I'm seeing write speeds in the range of 48-55mb/s (not 35 or so, like before). At the raw resolution of 1600 I can get maybe 800+ frames before dropping - lots better than before, but still not continuous.
Are you able to shoot at 1600 with no dropped frames?
(http://img259.imageshack.us/img259/3345/testkx.png)
Thanks again for the help!
My komputerbay 1000x 64GB card is getting consistant 57 MB/s (no max-out) which is great for 1592 x 896, but it does worry me that it won't be enough for 1920 x 1080 if / when that happens.
Quote from: menoc on June 06, 2013, 01:52:20 AM
Did you set the ratio to 16:9? . . . Otherwise, format and benchmark the card in Camera and post your results. I have the same card, here are my results. If yours do not look like these, then you have a dud :P:
(http://i.imgbox.com/acrP0LHK.jpg)
You have something set in your camera. Can you post your melloc?
Quote from: menoc on June 06, 2013, 01:07:37 AM
Set the following:
ISO: 100-200 (actually the ISO Does not matter so much use whatever ISO you need)
FPS override: 23.988 (Don't use 24 exact, use optimized for low light instead)
Canon Menus:
Set Qualiy to: JPEG Large Only - NO RAW
Settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: set it to "LiveView" (Turn off peaking and all other global draw settings)
RAW Video Settings:
Raw Video Resolution: 1600 (it will default to 1592)
Raw Video Ratio: 3:2 or 16:9
Sound: OFF
Hacked Mode: ON
Shoot something for a while . . . . 1600 resolution & 16:9 ratio is the most stable.
If I shoot at 23.988 (optimize for low light) my camera randomly drops to 22fps while recording.
@JulianH - thanks for being so quick to report back key results.
Quote from: JulianH on June 06, 2013, 01:24:18 AM
My results
Full sensor
Silent DNG: 1664x1084
Top 26
Left 74
Right 0
Bottom 0
5x zoom mode
Silent DNG: 2064x1106
Top 26
Left 64
Right 0
Buttom 0
Weird that we get different results here. But I suppose that has to do with the 2064 width I get for Silent DNG's in zoom mode. In Raw video mode 1920x1104 I get 26 black pixel rows on top, zero on the other sides.
i agree - typo in my post for skip left in zoom mode - tests on Sunday matched this.
1664x1084 - (74x26) and
2064x1106 - (64x26)
Quote
10x zoom test
Silent DNG: Gives the same image and result as 5x, doesn't seem to change anything.
Other observations
Not sure if all relevant, but I'll notice them just in case.
Raw video speeds look the same to me as the 28May build. But my card is the bottleneck around 59Mb/s max (Sandisk 90MB/s 32GB).
Shoot_Malloc_total seems to have grown. It reports 219M, I thought it was max. 212M with the other build. Contig = 27M.
bloat and now contig = 27M will kill speed
Quote
- try 10x zoom
Recording raw video in 10x zoom gives garbadged results, just funky lines. But it looks like it's actually doing something different than in 5x.
- move the zoom box to various positions top,left, center, bottom
right (didn't JulianH report that thee borders changed when he did a
raw video pan?).
I don't think I reported this, didn't have this experience. Didn't test it with the 05June build yet.
- turn on raw_rec and try at various aspect ratios - i'm not even sure this will give images of different resolutions, if it does check for black borders.
It does give different resolutions. No surprise with the black borders here. With max image size it's the same as in silent DNG and when cropping down to other aspect ratios the black lines disappear (when they are cropped out by lower height).
not sure if we are talking about the same thing here - i mean only borders on the Silent Pics
when i shoot Silent Pics with raw_rec module enabled and various aspect ratios, all Silent Pic DNGs are 2064x1106
any other official testers take a crack at the NULL build to measure Silent Pic borders?
for anyone else, don't worry about this - Silent Pics (from the Shoot Menu) will be coming soon.
I'll try it when I get home, and report back.
How can I access the zoom mode on the 50D? Is this part of the May 28th build? Thanks!
You just press the normal liveview zoom button, Same as zoom for normal live view without ML.
It's near where your right thumb is, top right hand side of the camera.
Quote from: djfremen on June 05, 2013, 08:59:41 PM
Can anyone confirm if they've broke the hard limit of 60 MB/s with the 50D?
My Lexxar 1000x 32GB card peaks at 63 mb/s, but runs stable at 59 mb/s.
Nah, for me writing is at 57/58mb/s max while recording.
Higher in read/write tests, but there's a bottlneck elsewhere currently by the looks.
Max 57/58 here. KomputerBay 32 / 64 1000x
Quote from: Cumulus on June 05, 2013, 09:08:29 PM
(Note: if you want to retune raw, Interpret Footage, More Options to relaunch ACR.)
Thanks for that tip ;)
The 2 batteries I got with my 50D have gone from holding charge for 10 mins to zero. New battery turned up today from TradeMe (NZ) seller: "
realwholesale": clearly advertised as 50D bat. Shame its is 3 times the size of the 50D battery! Back to waiting by the post box.
Quote from: paulforte on June 06, 2013, 09:02:47 AM
Max 57/58 here. KomputerBay 32 / 64 1000x
so a Komputerbay 600x UDMA6 (min write speed 60) could be enough? It costs 1/3 than the 1000x!
Quote from: riccardocovino on June 06, 2013, 10:22:58 AM
so a Komputerbay 600x UDMA6 (min write speed 60) could be enough? It costs 1/3 than the 1000x!
It could be! I'll try it and see, but its cutting it very close and there's no room for growth if they get 1080 going
Quote from: riccardocovino on June 06, 2013, 10:22:58 AM
so a Komputerbay 600x UDMA6 (min write speed 60) could be enough? It costs 1/3 than the 1000x!
I use Sandisk 60Mb/s and is fine for 1280 x 720, but only about 190 frames of 1576 x 880. But if it truly is MINIMUM of 60Mb/s.. maybe, but as paulforte says future proofing may be the way to go.
Quote from: menoc on June 06, 2013, 04:19:51 AM
You have something set in your camera. Can you post your melloc?
malloc is 153K
Thanks again for the ongoing problem-solving help -- it'd be great to get to the bottom of this.
Best
D
Quote from: riccardocovino on June 06, 2013, 10:22:58 AM
so a Komputerbay 600x UDMA6 (min write speed 60) could be enough? It costs 1/3 than the 1000x!
according this benchmark it will work...
http://www-cameraextensionpole.blogspot.nl/2013/05/komputerbay-64gb-professional-compact.html
Guys, im getting considerably faster speeds by using an external monitor :) try it.. the buffer doesnt fill no where near like it used to when not using an external monitor.... got a 9mb/s speed improvement and a non filling buffer :P this was tested with a sandisk 60mbs max constant speed was 45mb otherwise would be 36 mbs
(http://img32.imageshack.us/img32/193/wp000071u.jpg)
Not for me...
When going to external monitor at a higher resolution than my card can allow for, I get 224 frames with external monitor vs 337 frames without.
Without it I'm getting max of 60.1 / 60.2mbps, when I plug in the HDMI cable I get 54-55mb/s. I tested a few times to be sure.
In saying this, I might have different camera settings to you currently.
Can you please give full details like: photo mode or video mode, live view on/off, fps you are recording at, raw or jpg setting, etc etc?
If you can tell me the exact settings, I'll try to repeat my test using those too.
Stupid question but how do you record? I set this raw_rec module on and after that it says to press livescreen button to start. But when I hit it, nothing happens. Sorry for this noob question
Quote from: kretynjakchuj on June 06, 2013, 02:15:48 PM
Stupid question but how do you record? I set this raw_rec module on and after that it says to press livescreen button to start. But when I hit it, nothing happens. Sorry for this noob question
Did you also go to the camera menu and select/enable Raw recording? The default is OFF. After loading the module you have to further turn on Raw in the other menu.
Perhaps the difference is that it turns global draw on or off when you've plugged in the monitor?
If I have HDMI plugged in and global draw off, I get 50mbs
If I unplug HDMI, I get 54-55
If I turn global draw on, I'm banging on 60-61.
Quote from: Roman on June 06, 2013, 02:49:50 PM
Perhaps the difference is that it turns global draw on or off when you've plugged in the monitor?
If I have HDMI plugged in and global draw off, I get 50mbs
If I unplug HDMI, I get 54-55
If I turn global draw on, I'm banging on 60-61.
Guy's I don't know I'm getting upwards of 63 - 64mb/s on my Komputerbay 64gb 1000X card
Although my card (Transcend 16Gb 1000x) performs pretty similar in the benchmark i get ~47 MB/s while Recording RAW. I dont get this. I tested soo many settings and none of them are leading to any performance increase
Wanna see something odd?
(https://photos-5.dropbox.com/t/0/AABECPhUBEnQTl6R4na1BGzQQqcYuZlR3NlGirXK0BAvow/12/2427776/jpeg/32x32/3/_/1/2/20130606_165222.jpg/lcNEuQvf2KkAAMTEr0HJERmzB2cFUL9kDQCJes_1fIo?size=1600x1200)
YEa
When shooting 1592x896 @ 25fps I get 59mb/s pretty constantly with my Komputerbay 64gb 1000X card
Global draw on, HDMI unplugged.
QuoteAlthough my card (Transcend 16Gb 1000x) performs pretty similar in the benchmark i get ~47 MB/s while Recording RAW. I dont get this. I tested soo many settings and none of them are leading to any performance increase
It's rated faster than mine, maybe you have something still turned on in one of the menus?
Quote from: goldenchild9to5 on June 06, 2013, 04:42:16 PM
Guy's I don't know I'm getting upwards of 63 - 64mb/s on my Komputerbay 64gb 1000X card
mmm!!!!.......I guess it is all related on how lucky you are to get right CF card from Komputerbay
Quote from: rockfallfilms on June 06, 2013, 05:15:07 PM
When shooting 1592x896 @ 25fps I get 59mb/s pretty constantly with my Komputerbay 64gb 1000X card
Global draw on, HDMI unplugged.
I'm getting the same results and @ times even higher.. I think it's all about the settings & in camera formatting plays a big part of it also.
Quote from: hijodeibn on June 06, 2013, 05:22:32 PM
mmm!!!!.......I guess it is all related on how lucky you are to get right CF card from Komputerbay
To tell you the truth don't think it's the card, cause those cards are capable of handling way more write speeds than 60mb/s it should be no problem for those cards. Have to set your camera the right way as far as settings goes.
regarding issues i'm having getting my komputerbay card to read on my mac:
Komputerbay Tech Support
4:15 AM (4 hours ago)
to me
Hello,
The card is possibly corrupted.
From what we know the 50D is limited to FAT32 but your Mac is not. (your Mac possibly tried to read the card as exFAT instead of FAT32 seeing that it is a 64GB card - lot of customers have done this.)
It can be uncorrupted using a PC using SD Formatter's free software to format the cards. The Mac version has some bugs and as such we donot recommend it.
Also - we do not know if the bower USB2.0 CF Reader #CRCF is compatibnle with UDMA 7 cards.
Have you tried any formatting apps on your Mac?
Thank You
Tech Support
CS
Quote from: dhallowell19 on June 06, 2013, 02:32:00 PM
Did you also go to the camera menu and select/enable Raw recording? The default is OFF. After loading the module you have to further turn on Raw in the other menu.
Yes I enabled it nad it shows that it's on. Could tell me how do you record it? Maybe, I'm doing something wrong.
Once the raw video mode is enabled, you can close out of the window and press the live view button. Then press it again to start recording, press it again to stop.
Quote from: Roman on June 06, 2013, 06:08:52 PM
Once the raw video mode is enabled, you can close out of the window and press the live view button. Then press it again to start recording, press it again to stop.
It works, thank you! Jesus, I feel so ashamed...
Here's a video I shot yesterday, walking about my neighborhood - https://vimeo.com/67793246 (https://vimeo.com/67793246) - I used Lightroom for most of the grade, in that I exported a few presets into ACR and then used ACR.
Quote from: paulforte on June 06, 2013, 06:41:43 PM
Here's a video I shot yesterday, walking about my neighborhood - https://vimeo.com/67793246 (https://vimeo.com/67793246) - I used Lightroom for most of the grade, in that I exported a few presets into ACR and then used ACR.
Nice film look! Now get some stabilizer :) By the way I'm sorry, I had plans to join developing, but things changed a little here so I have little time :(
Just got my 50d with grip. I've been trying with some Sandisk Extreme IV 4GB card. On full res I get 98frames with global dram off and 109 frames with global draw on. Around 300-400 on 720p.
Zoom mode looks pretty bad, but I think that's the cameras limitation.
Has onyone tried out a 600x Komputerbay card? If anyone has and gets continuos rec on 1:1 I will go for that one.
Thanks to all of you who made this possible, I'm having a lot of fun!
Quote from: paulforte on June 06, 2013, 06:41:43 PM
Here's a video I shot yesterday, walking about my neighborhood - https://vimeo.com/67793246 (https://vimeo.com/67793246) - I used Lightroom for most of the grade, in that I exported a few presets into ACR and then used ACR.
I like this a lot.
Nice work!
Quote from: araucaria on June 06, 2013, 07:13:08 PM
Has onyone tried out a 600x Komputerbay card?
I have one on its way. Will report back.
Quote from: paulforte on June 06, 2013, 06:41:43 PM
Here's a video I shot yesterday, walking about my neighborhood - https://vimeo.com/67793246 (https://vimeo.com/67793246) - I used Lightroom for most of the grade, in that I exported a few presets into ACR and then used ACR.
Very nice video like the look a lot..
By the way I could get my hands on the new STM 18-55 IS lens. (for just 60 euro) It's actually really nice for filming. It's really sharp for a zoom lens and the manual focus is really smooth. I have some extra m42 mount lenses to get a shalow dof when needed, but they lack real wide angle and IS.
So I did a semi bold move on my part yesterday. I traded my 60D which is my main camera for a 50D and $250 cash. I think it was the right move. I just still can't get over the fact that I downgraded(kind of) my camera for the first time in my life. I pray this hack keeps on growing
Quote from: goldenchild9to5 on June 06, 2013, 04:42:16 PM
Guy's I don't know I'm getting upwards of 63 - 64mb/s on my Komputerbay 64gb 1000X card
I think the highest I've achieved is ~67mb/s. I could be mistaken but that was in the 3:2 aspect ratio.
Quote from: AaronL on June 06, 2013, 08:09:01 PM
So I did a semi bold move on my part yesterday. I traded my 60D which is my main camera for a 50D and $250 cash. I think it was the right move. I just still can't get over the fact that I downgraded(kind of) my camera for the first time in my life. I pray this hack keeps on growing
You did the right thing probably :) the sd controller in the sd card cameras seems pretty limited. Don't think there is a way to overcome this. So for raw video, the 50D should have a big advantage (like it has right now).
Quote from: GregoryOfManhattan on June 06, 2013, 05:31:56 AM
not sure if we are talking about the same thing here - i mean only borders on the Silent Pics
when i shoot Silent Pics with raw_rec module enabled and various aspect ratios, all Silent Pic DNGs are 2064x1106
Ah yeah, I should clarify that. When changing raw_rec resolution the Silent pics always stay the same resolution. There's just the difference between full sensor and zoomed modes.
Sorry for my ongoing reports about performance that seemed to be lagging the pack -- but *good news --- I finally seem to have hit upon the conditions that will let me shoot indefinitely at '1600' resolution.
Not sure which of these final changes that did the trick, but what I'd done included:
- turning off every single feature (zebras, etc.) in the shooting menus, though I hadn't seen that level of 'turning off' specified, I just went 100% off on everything.
- Even though 16:9 is default, I momentarily chose 3:2, then explicitly chose 16:9. I know that shouldn't matter - but with early code, we know things like that can matter.
Anyway - now my komputerbay 64 (1000x) card shows about 56-58mb/s and just one or maybe two stars in the buffer, then steady state for at least way longer than before. Will try some quite long shots after battery is recharged.
Thanks again for the patience and the tips. Now maybe I can get some test footage and try some other things.
I'm new to the forums. I've been a ML user with a T2i, sold it for the GH3 and now just purchased a 50d that comes in the mail today! Thank you to your hard work and hopefully I'll be able to donate some money in the next few weeks after I get paid.
I see a lot of people using the Komputerbay 64gig 1000x cf and I was wondering if any tests have been made with the 50d using Lexar 32gb 1000x cf?
Quote from: savale on June 06, 2013, 07:50:33 PM
By the way I could get my hands on the new STM 18-55 IS lens. (for just 60 euro) It's actually really nice for filming. It's really sharp for a zoom lens and the manual focus is really smooth. I have some extra m42 mount lenses to get a shalow dof when needed, but they lack real wide angle and IS.
You mean CANON EF-M 18-55mm F/3.5-5.6 STM IS, well......you can just use it in daylight...indoors you will need at least 3 generators.....My personal option is always to choose a lens starting at least in 2.8.....
Quote from: AaronL on June 06, 2013, 08:09:01 PM
So I did a semi bold move on my part yesterday. I traded my 60D which is my main camera for a 50D and $250 cash. I think it was the right move. I just still can't get over the fact that I downgraded(kind of) my camera for the first time in my life. I pray this hack keeps on growing
I already think doing that with my 7D... but then i loose my 60fps =(((
Quote from: AaronL on June 06, 2013, 08:09:01 PM
So I did a semi bold move on my part yesterday. I traded my 60D which is my main camera for a 50D and $250 cash. I think it was the right move. I just still can't get over the fact that I downgraded(kind of) my camera for the first time in my life. I pray this hack keeps on growing
It's a great move, now you have a true Raw Camera in your hands + some money buy yourself two Komputerbay 64GB 1000X cards with that money.
got everything ready....
but apparently my live view button doesn't work? It only turns on when i turn on/off my camera? :-\
I can manually turn it off in the menu but i can't turn it back on again unless i turn it off which makes raw recording not possible?
Am i doing something wrong? Does it has something to do with my lens? its a Tamron 28-300mm...
Quote from: eattheblinds on June 05, 2013, 07:29:01 PM
hmmm...i'm using a cheap-o bower usb2.0 reader i bought in chinatown. i expected it to be the culprit so i bought a USB3.0 off newegg and it should arrive soon. i wonder if i'll have better luck or if this is a more persistent problem.
komputerbay is getting back to me with tech support. fingers crossed there's a solution i'll be able to share.
The 32GB SanDisk Extreme works fine in the Transcend reader that would not let me access the 64GB KomputerBay. Some speed tests tomorrow.
Hello guys,
so, I tried shooting some test footage in 2.35:1, 5x mode (1920x818) today with May 28th build, but there still seem to be some bugs left. I apologise in advance in case these issues have been resolved in the meantime.
Firstly, the framing is not correct. Instead of being in the middle of the sensor, it seems that the image is captured at sensor pixel coordinates X=Y=0.
Another problem is that, although I constantly recorded in 5x mode, the written RAW data is sometimes being interpreted as 1592x678, but the image itself seems to be still 1920x818, with a wrong stride being applied in the raw file.
Here is an example DNG of the wrong image data:
http://www.filedropper.com/m000000 (http://www.filedropper.com/m000000)
As a reference, here is a DNG with correct image data (roughly the same scene):
http://www.filedropper.com/m000000_1 (http://www.filedropper.com/m000000_1)
I think it has something to do with the fact that I constantly switched between 5x and 10x mode to check the focus. But I always started recording when the Live View was in 5x mode.
Quote from: JIKIJI on June 06, 2013, 10:33:27 PM
got everything ready....
but apparently my live view button doesn't work? It only turns on when i turn on/off my camera? :-\
I can manually turn it off in the menu but i can't turn it back on again unless i turn it off which makes raw recording not possible?
Am i doing something wrong? Does it has something to do with my lens? its a Tamron 28-300mm...
have you activated live view?
Ok, i sold my 550d to get an almost new 50d. First time you see the detail is nothing compared to h.264. The capacity of manipulate the colors and contrast is just amazing, like photography. The closer to cinema: develop and then edit. Thank you very much!
I bought the camera with a Sandisk Extreme 60mbps and that's what i'm gonna use until i have money for a 1000x. With this card i'm getting around 7 seconds at 1576x880 24p and 6 seconds 25p aprox. Lower resolutions, i can record much more (the only test at 1440 gave me more than 1500 frames)
My first test. I used the may 28th build and this is the result: (24p instead of 23.978)
https://vimeo.com/67842597
Quote from: araucaria on June 06, 2013, 11:29:49 PM
have you activated live view?
Yes i have enabled it in the menu, Is the live view button supposed to be rock solid? it doesn't click or anything.
Quote from: simulacro on June 07, 2013, 01:24:28 AM
Ok, i sold my 550d to get an almost new 50d. First time you see the detail is nothing compared to h.264. The capacity of manipulate the colors and contrast is just amazing, like photography. The closer to cinema: develop and then edit. Thank you very much!
I bought the camera with a Sandisk Extreme 60mbps and that's what i'm gonna use until i have money for a 1000x. With this card i'm getting around 7 seconds at 1576x880 24p and 6 seconds 25p aprox. Lower resolutions, i can record much more (the only test at 1440 gave me more than 1500 frames)
My first test. I used the may 28th build and this is the result: (24p instead of 23.978)
https://vimeo.com/67842597
Great job man footage looks great.. Yeah you definitely need a 1000x card.
Quote from: dhallowell19 on June 06, 2013, 08:43:23 PMnow my komputerbay 64 (1000x) card shows about 56-58gb/s
MBps = Megabytes per second
Mbps = Megabits per second
Quote from: goldenchild9to5 on June 06, 2013, 10:12:03 PM
It's a great move, now you have a true Raw Camera in your hands + some money buy yourself two Komputerbay 64GB 1000X cards with that money.
That's actually the first thing i did. I got the 128gb instead of the 64 and had it overnighted since i couldn't wait. Hopefully it will be awesome weather so i can test it out tomorrow night
Quote from: AaronL on June 07, 2013, 04:34:22 AM
That's actually the first thing i did. I got the 128gb instead of the 64 and had it overnighted since i couldn't wait. Hopefully it will be awesome weather so i can test it out tomorrow night
OOh no email them ASAP I Mean now the 128GB card is way slower than the 64GB KomputerBay version don't know why exactly but it's slower. Have them change it to two 64GB, it's going to cost you a little bit more but it's worth it. Go back and read all the previous post everybody been saying the same thing about the 128GB card even Mark III users.
hi all, update on my builds and code for the 50D.
i got my 50D via craigslist in the US on Sunday May 26th, i signed into this forum the next day and did a magic lantern install.
had as many of you been following the various camera raw video forums as well as looking at code commits from the magic lantern core team on bitbucket.org/hudson/magic-lantern/ (click on source then naviagte to Magic Lantern / modules / raw_rec / raw_rec.c and click "Blame") to see the macro view of the code.
thought that within a week i'd be able to push a set of code for the 50D into the main magic lantern development "unified" branch, so that further developments are easy to keep in line with the extensive ongoing code work.
today i pushed all the code via a pull request to the core team (took me 10 days not 7 - oh well). once this is accepted, it will make it much easier for anyone to make builds and add on to the 50D part of the project, as it will be in sync.
a "build" is the set of files you install on your card to run magic lantern. these have to be generated for each camera, as certain files you see on your card like "autoexec.bin" and "ML/MODULES/MAGIC.SYM" are cameras specific and must be "compiled" for that camera - the 50D.109 in this thread.
if you're using a build from 28May13 on the 50D you will likely see my computer name on the ML info screen.
going forward, in the very near future, all the code needed to make the 50D record raw video will be in the main "unified" branch. it is also available in the public repository https://bitbucket.org/GregoryOfManhattan/magic-lantern/commits/branch/50DrawNow (the 50DrawNow branch is the one to use, i am also new to using bitbucket and the mercurial version control system, so please ignore the other 50D branch)
anyone is free to make builds with the code going forward.
over the past week, i've been merging code with the main unified branch and making builds.
the builds from the code vintage of May 28 - May 31 seem to have had the highest performance to me with as i now recall a magical build on the 30th which could run at 57MB/s with focus peaking and graphics.
many users are reporting 55MB/s+ performance from the build i released on 28May13.
more recent builds do not match this performance for me. for example with the merge this morning, i didn't have stable recording above 50MB/s - though i did have Silent Pictures, AutoETTR and many other new features running on the 50D.
i'd like to thank everyone on this very helpful forum and the many contributors to magic lantern. i really don't know how a1ex can get so much done - seems like he only sleeps 3 hours a night.
i've learned quite a bit in 10 days.
cheers
Julian,
yes this answers the question and the values are committed into code on bitbucket.
Quote from: JulianH on June 06, 2013, 08:41:39 PM
Ah yeah, I should clarify that. When changing raw_rec resolution the Silent pics always stay the same resolution. There's just the difference between full sensor and zoomed modes.
DNGs files from the Null build at regular and zoom mode linked below for reference.
http://50.56.67.113/ml-06June13/51170003.DNG (http://50.56.67.113/ml-06June13/51170003.DNG)
http://50.56.67.113/ml-06June13/27170022.DNG (http://50.56.67.113/ml-06June13/27170022.DNG)
http://50.56.67.113/ml-06June13/27170002.DNG (http://50.56.67.113/ml-06June13/27170002.DNG)
Quote from: GregoryOfManhattan on June 07, 2013, 05:37:43 AM
Julian,
yes this answers the question and the values are committed into code on bitbucket.
this should settle the "skip" values for the 50D.
DNGs files from the Null build at regular and zoom mode linked below for reference.
http://50.56.67.113/ml-06June13/51170003.DNG (http://50.56.67.113/ml-06June13/51170003.DNG)
http://50.56.67.113/ml-06June13/27170022.DNG (http://50.56.67.113/ml-06June13/27170022.DNG)
http://50.56.67.113/ml-06June13/27170002.DNG (http://50.56.67.113/ml-06June13/27170002.DNG)
Quote from: GregoryOfManhattan on June 07, 2013, 05:16:34 AM
hi all, update on my builds and code for the 50D.
i got my 50D via craigslist in the US on Sunday May 26th, i signed into this forum the next day and did a magic lantern install.
had as many of you been following the various camera raw video forums as well as looking at code commits from the magic lantern core team on bitbucket.org/hudson/magic-lantern/ (click on source then naviagte to Magic Lantern / modules / raw_rec / raw_rec.c and click "Blame") to see the macro view of the code.
thought that within a week i'd be able to push a set of code for the 50D into the main magic lantern development "unified" branch, so that further developments are easy to keep in line with the extensive ongoing code work.
today i pushed all the code via a pull request to the core team (took me 10 days not 7 - oh well). once this is accepted, it will make it much easier for anyone to make builds and add on to the 50D part of the project, as it will be in sync.
a "build" is the set of files you install on your card to run magic lantern. these have to be generated for each camera, as certain files you see on your card like "autoexec.bin" and "ML/MODULES/MAGIC.SYM" are cameras specific and must be "compiled" for that camera - the 50D.109 in this thread.
if you're using a build from 28May13 on the 50D you will likely see my computer name on the ML info screen.
going forward, in the very near future, all the code needed to make the 50D record raw video will be in the main "unified" branch. it is also available in the public repository https://bitbucket.org/GregoryOfManhattan/magic-lantern/commits/branch/50DrawNow (the 50DrawNow branch is the one to use, i am also new to using bitbucket and the mercurial version control system, so please ignore the other 50D branch)
anyone is free to make builds with the code going forward.
over the past week, i've been merging code with the main unified branch and making builds.
the builds from the code vintage of May 28 - May 31 seem to have had the highest performance to me with as i now recall a magical build on the 30th which could run at 57MB/s with focus peaking and graphics.
many users are reporting 55MB/s+ performance from the build i released on 28May13.
more recent builds do not match this performance for me. for example with the merge this morning, i didn't have stable recording above 50MB/s - though i did have Silent Pictures, AutoETTR and many other new features running on the 50D.
i'd like to thank everyone on this very helpful forum and the many contributors to magic lantern. i really don't know how a1ex can get so much done - seems like he only sleeps 3 hours a night.
i've learned quite a bit in 10 days.
cheers
Thank you so much for all your work Gregory you sacrificed 10 days of you life coding just so we all can enjoy the Raw Capabilities of the 50D, thank you once again. Will definitely follow your Bitbucket..
guess i'll have to return my body , my live view button doesn't do anything so i cant record raw on it :(
Quote from: JIKIJI on June 07, 2013, 07:17:31 AM
guess i'll have to return my body , my live view button doesn't do anything so i cant record raw on it :(
Sorry to hear it.
50D Live view only works in certain camera modes - make sure you've got it set to 'M' on the dial.
it is set on ''M'' mode, I will have to bring it back...
unless there is a way to record raw using a different button?? My live view turns on automatically when you turn on the camera ???
Quote from: goldenchild9to5 on June 07, 2013, 02:57:37 AM
Great job man footage looks great.. Yeah you definitely need a 1000x card.
Thanks. I know, but i got bankrupt with this investment... my little savings went to the camera. At some point i think i'm going to be able to make a 6,5 seconds shots videos haha
Quote from: menoc on June 06, 2013, 01:07:37 AM
Set the following:
ISO: 100-200 (actually the ISO Does not matter so much use whatever ISO you need)
FPS override: 23.988 (Don't use 24 exact, use optimized for low light instead)
Canon Menus:
Set Qualiy to: JPEG Large Only - NO RAW
Settings in C.Fn II: Image
High ISO speed Noise Reduction: Disable
Auto Lighting Optimizer: Disable
Highlight Tone Priority: Disable
Long Exposure Noise Reduction: OFF
Global Draw: set it to "LiveView" (Turn off peaking and all other global draw settings)
RAW Video Settings:
Raw Video Resolution: 1600 (it will default to 1592)
Raw Video Ratio: 3:2 or 16:9
Sound: OFF
Hacked Mode: ON
Shoot something for a while . . . . 1600 resolution & 16:9 ratio is the most stable.
Just did my first test using the above settings and Gregory's May 28th build with a Transcend 32gb 100x card. First time I started recording, it stopped after 120 frames. Started it right away again and it recorded till the card was full. Constant 57MB/s.
Quote from: GregoryOfManhattan on June 07, 2013, 05:16:34 AM
hi all, update on my builds and code for the 50D.
i got my 50D via craigslist in the US on Sunday May 26th, i signed into this forum the next day and did a magic lantern install.
had as many of you been following the various camera raw video forums as well as looking at code commits from the magic lantern core team on bitbucket.org/hudson/magic-lantern/ (click on source then naviagte to Magic Lantern / modules / raw_rec / raw_rec.c and click "Blame") to see the macro view of the code.
thought that within a week i'd be able to push a set of code for the 50D into the main magic lantern development "unified" branch, so that further developments are easy to keep in line with the extensive ongoing code work.
today i pushed all the code via a pull request to the core team (took me 10 days not 7 - oh well). once this is accepted, it will make it much easier for anyone to make builds and add on to the 50D part of the project, as it will be in sync.
a "build" is the set of files you install on your card to run magic lantern. these have to be generated for each camera, as certain files you see on your card like "autoexec.bin" and "ML/MODULES/MAGIC.SYM" are cameras specific and must be "compiled" for that camera - the 50D.109 in this thread.
if you're using a build from 28May13 on the 50D you will likely see my computer name on the ML info screen.
going forward, in the very near future, all the code needed to make the 50D record raw video will be in the main "unified" branch. it is also available in the public repository https://bitbucket.org/GregoryOfManhattan/magic-lantern/commits/branch/50DrawNow (the 50DrawNow branch is the one to use, i am also new to using bitbucket and the mercurial version control system, so please ignore the other 50D branch)
anyone is free to make builds with the code going forward.
over the past week, i've been merging code with the main unified branch and making builds.
the builds from the code vintage of May 28 - May 31 seem to have had the highest performance to me with as i now recall a magical build on the 30th which could run at 57MB/s with focus peaking and graphics.
many users are reporting 55MB/s+ performance from the build i released on 28May13.
more recent builds do not match this performance for me. for example with the merge this morning, i didn't have stable recording above 50MB/s - though i did have Silent Pictures, AutoETTR and many other new features running on the 50D.
i'd like to thank everyone on this very helpful forum and the many contributors to magic lantern. i really don't know how a1ex can get so much done - seems like he only sleeps 3 hours a night.
i've learned quite a bit in 10 days.
cheers
Sorry Mr Gregory, but I'm still so dumb :o that I do not know where to find your new builds. Should I find then in the Unified Nightly builds? or Should I compile (something I never did) the code of Bitbucket?. Thanks for attending these newbie questions.
Quote from: Nachelsoul on June 07, 2013, 11:46:26 AM
Sorry Mr Gregory, but I'm still so dumb :o that I do not know where to find your new builds. Should I find then in the Unified Nightly builds? or Should I compile (something I never did) the code of Bitbucket?. Thanks for attending these newbie questions.
If you're just trying it out for the first time, try the May 28th build. It is mentioned where to find it on the first page, in the first post. Just scroll down. Or go here: http://www.magiclantern.fm/forum/index.php?topic=5586.msg43359#msg43359
Thanks a lot Gregory for turning up out of nowhere and getting this far.
Awesome :)Quote from: Nachelsoul on June 07, 2013, 11:46:26 AM
Sorry Mr Gregory, but I'm still so dumb :o that I do not know where to find your new builds. Should I find then in the Unified Nightly builds? or Should I compile (something I never did) the code of Bitbucket?. Thanks for attending these newbie questions.
In other words: Gregory worked his ass of the past 10 days to make future developments easier, because from now on (or in the near future) it should be possible to let the development run along with the other camera's - not separate.
For now, use the 28th may build (linked in the first post of this topic, not the second one). The newer test builds aren't interesting for actual use.
Quote from: JulianH on June 07, 2013, 01:27:07 PM
Thanks a lot Gregory for turning up out of nowhere and getting this far. Awesome :)
In other words: Gregory worked his ass of the past 10 days to make future developments easier, because from now on (or in the near future) it should be possible to let the development run along with the other camera's - not separate.
For now, use the 28th may build (linked in the first post of this topic, not the second one). The newer test builds aren't interesting for actual use.
Thanks Julian, I am already using the 28May build. Incredible work guys. I would like to keep track of the devlopment. I recnetly bought the 50D mainly because your thread is the most fascinating. The camera is also. I want to compare it with my 5D2. I am very happy cause the cameras looks are very different and give me a lot of possibilities. You were right Julian about the cinematic look of the 50D, with vintage glass has a unique feel. The markIII reigns in RAW world, but the ancient 50D has a lot to say. Thanks all for share your talent.
Quote from: JIKIJI on June 07, 2013, 08:14:56 AM
it is set on ''M'' mode, I will have to bring it back...
unless there is a way to record raw using a different button?? My live view turns on automatically when you turn on the camera ???
You also have to enable Live View shoot in the Canon Menus . . .
Is anyone going to test a Toshiba 1066x card?.....supposed 150Mb/s, not sure if we will see any difference.
Quote from: hijodeibn on June 07, 2013, 08:33:04 PM
Is anyone going to test a Toshiba 1066x card?.....supposed 150Mb/s, not sure if we will see any difference.
That might be overkill for the 50D - 1000x is more than capable.
Quote from: menoc on June 07, 2013, 06:23:30 PM
You also have to enable Live View shoot in the Canon Menus . . .
I do know that....... my live vew button is faulty.......
Sounds unlikely, but I guess it could be possible. Try with the normal Canon firmware, read the manuals etc, make sure you're not overlooking something. Anyway, good luck...
In the process of writing a short narrative piece to test a motivated workflow of the 50D. Should be shot and wrapped in the coming weeks.
Hey everyone. I just got my card and I'm ready to roll. I just needed to know what the exact setting are i need to operate the fastest and also what build model. I think its the 5/28 one but in that model i cant choose what frame size i want to record at. Anyways thank you in advance for the help
Quote from: artiswar on June 07, 2013, 10:27:08 PM
In the process of writing a short narrative piece to test a motivated workflow of the 50D. Should be shot and wrapped in the coming weeks.
Awesome can't wait to see it, got a music video shoot this weekend gonna put the 50D to the test as well big workflow but worth it.
Quote from: AaronL on June 07, 2013, 10:42:21 PM
Hey everyone. I just got my card and I'm ready to roll. I just needed to know what the exact setting are i need to operate the fastest and also what build model. I think its the 5/28 one but in that model i cant choose what frame size i want to record at. Anyways thank you in advance for the help
Yep Gregory's 5/28 Build is by far the most stable.. Settings are as follow -
Canon In camera settings: Press menu on 50D & Scroll to the 8th option menu than select (C.FnII:Image) Long exp. noise reduction (Off) - High ISO Speed Noise Reduct'n (Disable) - Highlight tone priority (Disable) - Auto Lighting Optimizer (Disable)
Magic Lantern Settings:
Global Draw = (Off) - Override Exp (ON) - Override FPS (24 Exact FPS / Low Light) all up to you I prefer 24 exact - Hacked Mode (ON)
That's it have fun with your 50D Post footage when you compile one Cheers.. 8)
Quote from: AaronL on June 07, 2013, 10:42:21 PM
Hey everyone. I just got my card and I'm ready to roll. I just needed to know what the exact setting are i need to operate the fastest and also what build model. I think its the 5/28 one but in that model i cant choose what frame size i want to record at. Anyways thank you in advance for the help
One last thing very important format the card in camera, I get the best result from doing that.
Quote from: goldenchild9to5 on June 07, 2013, 11:09:37 PM
Yep Gregory's 5/28 Build is by far the most stable.. Settings are as follow -
Canon In camera settings: Press menu on 50D & Scroll to the 8th option menu than select (C.FnII:Image) Long exp. noise reduction (Off) - High ISO Speed Noise Reduct'n (Disable) - Highlight tone priority (Disable) - Auto Lighting Optimizer (Disable)
Magic Lantern Settings:
Global Draw = (Off) - Override Exp (ON) - Override FPS (24 Exact FPS / Low Light) all up to you I prefer 24 exact - Hacked Mode (ON)
That's it have fun with your 50D Post footage when you compile one Cheers.. 8)
Thanks man. Whats wrong with the other settings? I was really hopping to shoot some 2:39
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
Quote from: JulianH on June 07, 2013, 11:50:05 PM
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
On mobile so I haven't have it a watch yet, but transcoding to Cineform, how's highlight and shadow recovery. What's the files size of the Cineform stuff? Thanks for all the hard work.
Quote from: JulianH on June 07, 2013, 11:50:05 PM
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
Very Nice Julian. Magnificent images.
Quote from: JulianH on June 07, 2013, 11:50:05 PM
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
Very good video. Is
Quote from: JulianH on June 07, 2013, 11:50:05 PM
so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage)
Can you post your computer specs Julian. Mac or PC/Hackintosh?
Thanks Julian! Could you please upload somehwere unscaled original footage?
Im going to buy 50D soon and would like to play with the original raw footage first. Thanks!
Quote from: JulianH on June 07, 2013, 09:50:21 PM
Sounds unlikely, but I guess it could be possible. Try with the normal Canon firmware, read the manuals etc, make sure you're not overlooking something. Anyway, good luck...
Thanks but I did try with original firmware, had it for a week and tried everything so decided to bring it back today. The button just had no response whatsoever, must be a mechanical malfunction. Anyways ordered a new one, waiting for next week for it arrive.
Quote from: JulianH on June 07, 2013, 11:50:05 PM
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
Julian once again beautiful images man I'm loving the 50D more and more each everyday. By the way there is a direct way now to get CinemaDNG's from the 50D's Raw files I'll post link.
Guy's new update their is a converter developed by the RareVision guys the ones who developed 5DtoRGB. Basically it's a Raw to CinemaDNG converter that means you can import right into Davinci Resolve 9 to edit and color footages that's big. Here is the link to topic and download link should be the second post
http://www.magiclantern.fm/forum/index.php?topic=6218.50 (http://www.magiclantern.fm/forum/index.php?topic=6218.50)
another little test:
http://www.youtube.com/watch?v=qDI45rdEBCs&feature=youtu.be
https://vimeo.com/67869940
bringing the overexposed images to safer zones is like magic!
Quote from: goldenchild9to5 on June 08, 2013, 03:25:36 AM
Guy's new update their is a converter developed by the RareVision guys the ones who developed 5DtoRGB. Basically it's a Raw to CinemaDNG converter that means you can import right into Davinci Resolve 9 to edit and color footages that's big. Here is the link to topic and download link should be the second post
http://www.magiclantern.fm/forum/index.php?topic=6218.50 (http://www.magiclantern.fm/forum/index.php?topic=6218.50)
Any luck processing spanned clips? Highlight and shadow recovery akin to the ACR workflow?
Quote from: JulianH on June 07, 2013, 11:50:05 PM
Found some time to edit my shots I made earlier this week.
Experimented with a new workflow, I wanted something faster than ACR/Bridge, so I used RAWanizer to convert to CineformRAW 444 (about 10 minutes for 21GB of footage), graded the clips in Davincie Resolve Lite 9 and edited in Premiere CS6.
More details (and download option) on vimeo.
Shot with the 28th May build by Gregory.
Julian, did you get small squared noise patterns when using that workflow? I tried the RAWanizer + CineForm combo and I got some very unusual results...
Quote from: araucaria on June 06, 2013, 07:13:08 PM
Has onyone tried out a 600x Komputerbay card? If anyone has and gets continuos rec on 1:1 I will go for that one.
Just got my 600x Komputerbay 32 from Amazon and tested it. No go. Cannot get more than 100 frames, 25.2 MB/s. Gonna return it. My 1000x's 64 and 32 work well.
Quote from: artiswar on June 08, 2013, 04:56:16 AM
Any luck processing spanned clips? Highlight and shadow recovery akin to the ACR workflow?
Haven't tried but I will.. Yep you can recover Highlight and shadows actually you can put it in Log mode which is nice a flat BMC looking image just tried it, it's very nice. The other plus also is that Davinci upscales the footage for you automatically & to tell you the truth I can't tell the difference between the original and upscaled version. Give it a go when you can..
Quote from: paulforte on June 08, 2013, 05:02:40 AM
Just got my 600x Komputerbay 32 from Amazon and tested it. No go. Cannot get more than 100 frames, 25.2 MB/s. Gonna return it. My 1000x's 64 and 32 work well.
1000X is always a safe bet, sorry it didn't work-out for you with that card now it's going to be another wait to get new one.
Okay so I'm sure we're all totally amazed at what the 50D can do, especially since it never came with video for starters!
However, there are still a few realistic ways I think it could be better.
Since I'm not technically capable of programming Magic Lantern in any which way, I thought I'd put together a wish list for futre 50D video features, as follows...
1. A hard upper limit to exposure time, of 1/fps when raw video mode is turned on. i.e. it will not let you shift the exposure time beyond 1/24th of a second if you are shooting 24fps.
2. Tying into the above, exposure time indicated in degrees, 180, 275, etc.
3. Clarification on real exposure time, when fps override is turned on. For example, if you set the camera to 1/250th of a second when at 30fps, and then set fps override to 24fps... Is it still 1/250th? Or is it 1/250th * (30/24) ? If it's the latter, then updating exposure time to match FPS would be handy. (And make sure the 360 degree exposure time matches fps override, instead of 30fps still)
4. Perhaps far fetched, but there was mention that there could possibly be other native video modes apart from 30fps?
Perhaps would help with the above scenario if there was a native 24fps setting floating around somewhere in the camera already.
5. Sticky DOF automatically working when you hit the record button. As it's quite cumbersome to use electronic lenses at the moment.
6. Not 50D specific, but I find it a real pain to autofocus in video mode, and usually only do it at the start of a shot. So what I tend to do, (if not manually focus0 is turn liveview off, autofocus the camera the 'normal' way, (as this works very quickly) and then switch it back to liveview and go from there. Would it be possible to automate this sequence? Live view off > autofocus > focus confirmation > liveview on? Assuming anyone else would find that handy of course. If that could be automated to a half shutter press or something, it would be freaken sweet.
So just a few thoughts, anyone else got any other (realistic) suggestions?
1. A non-cumbersome way of loading video modules.
2. 2353x1568 @ 23.98 FPS
3. 12-bit HDMI out ;)
Anyone else having issues reviewing images? I used to be able to see the first frame of a raw file, and select and delete. Now i just get "no image"?
Sandisk 32GB
28th build - G. Manhattan
Any suggestions would be appreciated. Thanks!
Edit: First time I was using ML Raw it was an old version... image play back says something about only being enabled in photo mode? was this a change in the 28th may build?
Also just bout go go look for info on file spanning. currently @ 1280 x 720 I can only go up to 2.7GB files. On a slow card hence aonly 1280 x 720. 60mb/s getting about 44.5 mb/s. 720 is only about 37 ish Mb/s... so not the card limiting.
Roman, i dont get the problem with the Sticky DOF. As soon as you Enable Exp. Override it changes the Aperture right after you dialed it in. Where's your problem?
Quote from: djfremen on June 08, 2013, 01:08:36 AM
Can you post your computer specs Julian. Mac or PC/Hackintosh?
Windows 7, Core i5 2400, 16GB, GeForce GTX660 (for Resolve), 180GB ssd for OS/programs.
Pretty midrange by now. Nothing extreme, but enough. Just going to get another 256GB SSD to put the project files on. Now i was working from my normal hdd since my 1st ssd is pretty full.
... Had the same experience. The first time I shot raw I was also able to view independent clips and delete. In addition, at one point, I was able to adjust through multiple shots and actually choose which file to playback.
... Also, I have now tested three different Canon 50D cameras. One camera in particular, having what appears to be a late model serial number will not record past a 2:1 aspect ratio w/ a 64GB 1000x Komputerbay card. Using the same card, I am able to shoot 5:3 aspect ratio continuously on what appears to be a much earlier model number. It's even recording steady at 64MB/s. Finally, had another 50D that featured a great deal of stuck pixels. I applied a 5 minute manual sensor clean, same technique that repaired the early model 50D model with nearly 40,000 click, however, I was not able to test the camera with the 64GB 1000x. I'm not sure what to do for those who have this issue... Might be an issue for other? It's good to know that this camera was recording 2:1 continously on a Komputerbay 128GB 1000x. Based on these tests, yes, the 64GB 1000x is much faster. However, there may be variations in camera technology within the 50D production period.
Camera settings are specifically reduced for optimal resolution during raw recording... Been following each of our posts and have compiled a number of test shots. Finding the camera to perform stunningly when practicing ETTR (exposure to the right)... Always finding incredible dynamic range and very minimal noise, including ISO 3200.
Having difficulties getting past the built in "screen-like" grid pattern when viewed at %200 or more. It appears to be the foregoing limitation to adjusting the image's sharpness. In many ways, it also creates a "max resolution" appearance to the image. It is a 14-bit image, however, this grid pattern is more of a step back from 14 bit. It's almost as though its a 10-bit limitation?
Can't say enough about how exciting this development is! Seems there is so much room to express cinema photography that it's time to truly say, "This is the way to go!" Way to go everyone! Thanks so much ML Team & Testers!
Canon 50D May 28th Build... Nikon Nikkor AI-s lens kit, Komputerbay 64GB 1000x cards.
Hey guys, I switched my t2I for a 50D (coming in the mail). Do the 50D have a sync beep option in raw video? Having this feature could be very usefull to sync the footage with an external recorder. I know the 50D does not have a speaker but maybe the AF confirm or timer beeps could be used for this?
If it's already done, did someone test it in a project?
LEVISDAVIS, interesting theory. I guess it could be possible that canon has used different cf card controllers over the years.
Now that was a surprise:
Went to the post office yesterday to pick up the 50d i ordered from soith korea.
First, it took only 4 days from there to canada!
Went back home hoping that everything would work as it should on the camera, that the battery get a decent amount of time to work with, etc. The camera looks like it hass been refurb, minor signs of use, almost like new.
Checked the current firmware on the card ... Ish.... 1.0.3 damn the cam is freaaking old...
I installed ML unified on an old cf card I had.
Whent to see how many shutter actuations: 2k.... What?? Cool!!!
Now today I'm going to get a card reader to install raw recording on a 16gb 1000x lexar.
My card reader built in a mpc1000 usb 1.1 just can't take something that big. It's long tedious and simply doesn't work
Whoa 2k shutter count! Nice. I was pretty happy with 18k, which is still quite low for a 5+ year old camera.
Quote from: dacssfreak on June 08, 2013, 11:17:57 AM
Roman, i dont get the problem with the Sticky DOF. As soon as you Enable Exp. Override it changes the Aperture right after you dialed it in. Where's your problem?
Right you are! Sorry didnt realise that's what it did, haha.
so let it be written (commit 8118ed9)
so let it be done. (http://www.youtube.com/watch?v=3bQnxlHZsjY if you don't know the movie)
it is official - 50D raw video is now part of the unified branch of Magic Lantern.
Giovanni C reviewed and merged the code this hour.
there was some question about leaving Silent Pictures enabled by default and Silent Pics are in.
in terms of the 50D playing nice with the latest modules, users mk11174, Chucho and Coutts provided key information.
this code matches the build i posted yesterday
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/07June13-50DrawNow-bbf358d.zip
which has Silent Pics, AutoETTR and all the newest ML code (up to around 20130607-1200 UTC time).
sent out an email to the testers yesterday and haven't heard reports of disastrous occurrences (there have been 70 downloads).
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
WARNING: may not record faster than my 28May13 build. so if you are shooting a music video this weekend, you may not want to "upgrade". it's easy to switch back anyway.
hope this helps.
Quote
WARNING: may not record faster than my 28May13 build. so if you are shooting a music video this weekend, you may not want to "upgrade".
Huh?!
with latest merged code, i am not getting steady recordings at the same rates as code from last week.
can recod stable raw video, but not for example continuous 1920x720 until the card is full.
have only tried with one komputerbay card.
hoped to get more feedback.
(http://50.56.67.113/ml-07june13/TEST.BMP)
The benchmark code wasn't touched since then...
90MB on write speed? that puts it in the same league as 5D3...
Is ML properly disabling Canon GUI while recording raw? (to check, enable Canon histogram, it should freeze or disappear while recording)
do you mean this Canon gui
https://twitter.com/GregoryOnRoad/status/343361207354396672/photo/1
?
love that histogram - cuold be helpful for exposure though i'd only be recording at 10 frames/ second
Yes. Does Canon histogram stop updating while shooting raw video?
Canon histogram is not relevant for exposing raw btw. Use ML raw histogram for that.
went outside - couldn't easily post photo
now witness the firepower of this armed and fully operational (canon gui)
https://twitter.com/GregoryOnRoad/status/343361207354396672/photo/1
yes the canon gui is active during raw video recording
for those following along at home, the empire strikes back and the canon gui is showing up during raw recording in my recent build.
you do NOT want the canon gui during raw recording as it will slow it down.
ideally you'd want to use magic lantern histogram and spot exposure during raw recording.
(waveform is based on YUV not raw so it may not be entirely accurate during raw recording)
Active and moving? that's not quite good.
The only easy solution that I see right now is to try globaldraw on and all other things disabled.
Or... hack the CONFIG_KILL_FLICKER code so Canon GUI can be disabled from some other tasks too. Not sure what is the best way to implement this; maybe a reference counting like LV RAW mode from raw.c.
Well 50D is stateside... but not in my hands yet. I want to work on stuff like this... ie getting 50D up to speed with its brother the 5DII, display filters, etc.
Also want to see how far I can push H264 with infinite write speed and huge buffers :)
Quote from: 1% on June 08, 2013, 04:33:54 PM
Well 50D is stateside... but not in my hands yet. I want to work on stuff like this... ie getting 50D up to speed with its brother the 5DII, display filters, etc.
Also want to see how far I can push H264 with infinite write speed and huge buffers :)
uhhh . . . . I'm salivating at 60-120fps H.264 :)
I wish... the IC doing the encoding can't handle over 36.. I can't break physics. But probably 200MB/s H264 and hopefully native 24/25P. This is one of the only cameras that will probably do *GOOD* all-I.
5d2 has no 720P.. I'll look tho.
Tried to shoot some stuff earlier, the 1st couple of shots were fine and recorded at 59mb/s then the write speed dropped to 45mb/s and the buffer filled quickly. I can't seem to get it back to recording at 59mb/s
I've formatted the card in the camera etc, anyone else noticed a sudden drop in write speeds?
I'm using 28th build shooting at 1592x896 on 64gb komputerbay card.
Quote from: 1% on June 08, 2013, 04:58:46 PM
I wish... the IC doing the encoding can't handle over 36.. I can't break physics. But probably 200MB/s H264 and hopefully native 24/25P. This is one of the only cameras that will probably do *GOOD* all-I.
5d2 has no 720P.. I'll look tho.
:( Bummer . . . . maybe at 720 or even 640p- I'll take 640p/60
Quote from: GregoryOfManhattan on June 08, 2013, 02:25:54 PM
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.
Quote from: CaptainOfObvious on June 08, 2013, 05:15:34 PM
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.
Yes. Exactly the same here . . . had to revert to 28th build.
double checked armed and fully operational - so yes active and moving during raw_rec
on 28May13, i could record 57MB/s with Graphics Draw on with Histogram, Waveform -
pic.twitter.com/g3ACzE2Ux9
(should have had Exp Simulation On ).
could there be a more simple solution - it seems that this lack of canon_gui deactivation occurred during code changes the past week?
for example, poking around in changes
hg diff -r caffd8a src/| grep canon_gui
see that UNAVI_FEEDBACK_TIMER_ACTIVE is not defined in platform/50D.109/consts.h
this week the logic in src/gui_common.c is changed using UNAVI_FEEDBACK_TIMER_ACTIVE
i just tried a quick edit to gui-common.c to force the call to canon_gui_disable_front_buffer();
that doesn't help the frame rates - though it does turn off the visible canon gui.
so issue appears more complicated.
Quote from: 1% on June 08, 2013, 04:58:46 PM
I wish... the IC doing the encoding can't handle over 36.. I can't break physics. But probably 200MB/s H264 and hopefully native 24/25P. This is one of the only cameras that will probably do *GOOD* all-I.
5d2 has no 720P.. I'll look tho.
Question: Would all-I help with moire??
Quote from: menoc on June 08, 2013, 05:17:14 PM
Yes. Exactly the same here . . . had to revert to 28th build.
hold on - MAGIC.SYM must match the AUTOEXEC.BIN
must be bad upload.
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.
@1% any thoughts on the canon gui issue and recording frame rate slowing down over the past week of code updates?
have put up a build from the unified branch with all of the current code, so if there is any tests which could be done before you have the camera, just ask and the 50D users can try things out and post results.
Will have to test and see why its getting enabled. I'll put them up as I make em. The only thing I can benfit from is getting the rom so I can start disassembling it.
Just look at CONFIG_KILL_FLICKER ifdefs and you'll see why it's getting enabled.
Quote from: a1ex on June 08, 2013, 03:04:37 PM
90MB on write speed? that puts it in the same league as 5D3...
We only see those speeds with benchmark in playback mode. In LV it benchmarks lower.
I don't know the cause of that or the difficulties behind it, would it be possible to speed up writing in LV? The camera seems capable of it..
Can't wait to try the new build. First thing when I get home later today :)
Quote from: GregoryOfManhattan on June 08, 2013, 05:35:00 PM
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.
QuoteTried to shoot some stuff earlier, the 1st couple of shots were fine and recorded at 59mb/s then the write speed dropped to 45mb/s and the buffer filled quickly. I can't seem to get it back to recording at 59mb/s
I've formatted the card in the camera etc, anyone else noticed a sudden drop in write speeds?
I'm using 28th build shooting at 1592x896 on 64gb komputerbay card.
I repartitioned the card in my mac and then reformatted in camera, write speed is now back up to 59mb/s. The card must have corrupted somehow.
Most likely CPU or DMA is overloaded with something else; disabling certain stuff (Canon GUI, maybe LiveView display) helps.
On 50D only, to disable Canon GUI, enable Global Draw.
What changeset are you running? There should not be any drops in write speeds, unless you have enabled zebras or focus peaking or who knows what other CPU-intensive stuff.
Quote from: GregoryOfManhattan on June 08, 2013, 05:35:00 PM
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.
Terrific work Greg. ALL is good.
QuoteWhat changeset are you running? There should not be any drops in write speeds, unless you have enabled zebras or focus peaking or who knows what other CPU-intensive stuff.
Global draw etc off. the first 3 files were fine at 59mb/s then the write speed dropped on any further files i tried to record.
Formatting in camera didn't change anything but repartitioning and then formatting put the write speed back to 59mb/s
@GregoryOfManhattan
Thanks for getting the 50D into the unified build:
Just did a test and got 57mb/s constant, only 1 buffer star and no Canon overlays.
Global draw off
24fps
1584x892
Seems to be working for me.
Quote from: Roman on June 08, 2013, 01:22:05 PM
Right you are! Sorry didnt realise that's what it did, haha.
Im glad I could help ;)
Quote from: GregoryOfManhattan on June 08, 2013, 05:35:00 PM
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.
Great work Gregory.. gonna give it a go right after my video shoot with your awesome May, 28th Build 8) I also see that you enabled ETTR on the new one.. How can I enable ETTR on the May 28th build?
that is great news rockfallfilms - let me go through my settings then, i keeps changing so many things and finding creative ways to break my camera - i'll go back to defaults and go through my checklist.
FYI when a1ex asks what changeset we are running - you can see it at the bottom of the ML Help tab
file - https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/08June13-50D-UNIFIED.zip
is:
Mercurial changeset: 68208a7efac3 (unified)
Ah right, I wondered what that meant :)
With global draw on I get 45mb/s.
Quote from: goldenchild9to5 on June 08, 2013, 06:01:25 PM
Great work Gregory.. gonna give it a go right after my video shoot with your awesome May, 28th Build 8) I also see that you enabled ETTR on the new one.. How can I enable ETTR on the May 28th build?
hey goldenchild9to5,
been an amazing week in ML coding history and ETTR and AutoETTR is part of the story.
you have to get the latest edition to get all of the ETTR goodness (say goodbye to AutoISO if you liked that).
wiping a card and resetting camera to see if my new unified build can run well for me.
sounds like rockfallfilms is getting good results with it.
Quotebeen an amazing week in ML coding history and ETTR and AutoETTR is part of the story.
you have to get the latest edition to get all of the ETTR goodness (say goodbye to AutoISO if you liked that).
Is AutoETTR enabled in the latest 50D unified build?
Quote from: GregoryOfManhattan on June 08, 2013, 06:09:17 PM
hey goldenchild9to5,
been an amazing week in ML coding history and ETTR and AutoETTR is part of the story.
you have to get the latest edition to get all of the ETTR goodness (say goodbye to AutoISO if you liked that).
wiping a card and resetting camera to see if my new unified build can run well for me.
sounds like rockfallfilms is getting good results with it.
WOW!!! ;D Great work man you don't sleep hugh.. So that means with your new build ETTR and Auto ETTR is an option (Auto ISO) gone Lol.. that's amazing work man I didn't think it would advance soo fast, and your May 28th Build set the bar way high but it seems you have surpassed your own threshold. Got one last question with the new ETTR modes advances does that help eliminate those nasty noise patterns from the Images? specially present in low light off course.
Getting a solid 56 mb/s at 1600/16:9, 3:2 is also good (about 4 stars) at 62 mb/s . . . shooting with global draw on " ALL Modes" (everything else off). Will try Auto ETTR, seems to be awesome!
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.
Raw histogram is a low-priority task, so it should be OK. Zoom is one of the most CPU-intensive overlays, try to avoid it.
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.
These are high priority tasks, because they refresh quickly. The priority was tweaked so they don't affect Canon's H.264 recording, but raw recording needs pretty much all the resources it can get.
On 5D3 I notice a 2-3 MB speed drop with raw zebra and peaking enabled, but the task scheduler on 50D/5D2/500D is quite a bit behind 550D and newer cameras.
Quote from: a1ex on June 08, 2013, 06:40:14 PM
Raw histogram is a low-priority task, so it should be OK. Zoom is one of the most CPU-intensive overlays, try to avoid it.
New unified build very stable without Global Draw on just recorded a 9GB file only stays on 1 star amazing..
Quote from: GregoryOfManhattan on June 08, 2013, 06:09:17 PM
hey goldenchild9to5,
been an amazing week in ML coding history and ETTR and AutoETTR is part of the story.
you have to get the latest edition to get all of the ETTR goodness (say goodbye to AutoISO if you liked that).
wiping a card and resetting camera to see if my new unified build can run well for me.
sounds like rockfallfilms is getting good results with it.
Reporting back, Just gave the new Unified build a test run man oh man extremely stable just recorded past 9GB had to stop it only stays on (*.....) pans aperture adjutments don't effect it at all nice work man. The only drawback is when I enable Global Draw buffer fills-up very quickly it was the same in the may, 28th build so it's no big deal for me I think I might have to shoot video on this new build ;D I'm gonna keep testing it. One last thing how do you access the ETTR modes can't seem to find it in the menu.
Just read the whole Auto ETTR topic. Didn't look into it before since I always shoot manual for video anyway, but this looks rather interesting. Curious what the results will be, going to give it a try!
@Julian
Hi Julian
May you tell here how is possible ( in 28 build, 50d, M (manual) mode) to have in the LCD the ACTUAL exposure?
I have always a kind of constant exposure in LCD whatever the shutter, iso or T stop i set.
Regards and go 50d!
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!
(http://i39.tinypic.com/bi74wl.jpg)
(http://i40.tinypic.com/2rmuwcy.jpg)
Quote from: rommex on June 08, 2013, 08:44:46 PM
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?
Quote from: rommex on June 08, 2013, 08:44:46 PM
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!
(http://i39.tinypic.com/bi74wl.jpg)
(http://i40.tinypic.com/2rmuwcy.jpg)
Have you sharpened this?
The only good fixes for aliasing are crop mode or the Mosaic filter (which afaik doesn't fit on the 50D).
As per questions to my frames:
- I have not applied sharpness
- I shot with the max resolution for 50D - that was the main idea behind loaning a fast card
- one frame is 100% crop and the other is enlarged to 1920x1080
beyond 1k - my 08June13 build is a cinema camera - getting stable 2000x720 14bit raw video - wow!
~/bin/raw2dng /Volumes/transfer/ML-TEST/M08-1349-combined.RAW
Resolution : 2000 x 750
Frames : 6979
Frame size : 2625536 bytes
Frame skip : 1
FPS : 24.000
Processing frame 1 of 6979...
Vertical stripes correction:
1.000 1.000 0.994 0.991 1.000 1.003 0.997 0.994
Processing frame 4679 of 6979...
shooting GD enabled (had to turn off everything)
Hack mode
stable @62.5MB/s
note, it is possible to get your 50D into a very weird state as i did this morning and have it show the Canon GUI.
if you see things like that - reset everything and go through the checklist of settings (which i wish were edited into the first post of this thread)
Quote from: rommex on June 08, 2013, 08:44:46 PM
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!
(http://i39.tinypic.com/bi74wl.jpg)
(http://i40.tinypic.com/2rmuwcy.jpg)
I'm not sure how your getting all that Moire must be a setting, or setting maybe the way your converting your Raw to DNG. My 50D has little to none moire & aliasing, don't get me wrong it's present but not like what I'm seeing here. Let me know your conversion process after shooting.
Cool, that's almost 2K.
Can you get a screenshot with the latest changeset? I've modified the speed calculation routine to include only the time used for writing to card (idle time is displayed separately, if any).
There's also a minor speed optimization, but it doesn't seem to make any difference on 5D3.
P.S. What's the point in quoting a huge image 5 times?
Quote from: GregoryOfManhattan on June 08, 2013, 09:03:44 PM
beyond 1k - my 08June13 build is a cinema camera - getting stable 2000x720 14bit raw video - wow!
~/bin/raw2dng /Volumes/transfer/ML-TEST/M08-1349-combined.RAW
Resolution : 2000 x 750
Frames : 6979
Frame size : 2625536 bytes
Frame skip : 1
FPS : 24.000
Processing frame 1 of 6979...
Vertical stripes correction:
1.000 1.000 0.994 0.991 1.000 1.003 0.997 0.994
Processing frame 4679 of 6979...
shooting GD enabled (had to turn off everything)
Hack mode
stable @62.5MB/s
note, it is possible to get your 50D into a very weird state as i did this morning and have it show the Canon GUI.
if you see things like that - reset everything and go through the checklist of settings (which i wish were edited into the first post of this thread)
In what mode are you getting (2000x720) ? is it on 5X or 10X mode, or regular 16:9 aspect ratio? I was just reviewing some footage that I just shot with the new Unified build it seems that the shadows are really getting crushed, I'm seeing less detail in the shadows than in the May 28th Build.
Quote from: a1ex on June 08, 2013, 08:53:38 PM
The only good fixes for aliasing are crop mode or the Mosaic filter (which afaik doesn't fit on the 50D).
I emailed Mosaic Engineering to ask if they might make a filter for the 50D. Not heard back yet but who knows, maybe if everyone does it then it may make them consider it?
contact "at" mosaicengineering.com
Quote from: goldenchild9to5 on June 08, 2013, 09:09:40 PM
I'm not sure how your getting all that Moire must be a setting, or setting maybe the way your converting your Raw to DNG. My 50D has little to none moire & aliasing, don't get me wrong it's present but not like what I'm seeing here. Let me know your conversion process after shooting.
I do hope there something in the conversion, or else my investment is futile.
I did Raw2DNG -> Import to AE CS5.5 -> Save Frame
Moire and aliasing... Heavily dependent on the shooting situation of course. For the anamorphic video I made, everything at f/8/11/16 a few shots were useless. Still, I got plenty of high detail shots without much problems.
After that I haven't experienced moire so bad as with that example. Could it be dependent on the build as well or is that impossible? Shot mostly lowlight lately at bigger apertures so it makes sense it showed up less.
I think it's pretty workable and you can get around it in most situations. Will experiment more with high detail settings.
One thing I do for sure is disabling sharpening when converting the dngs. I do add it but only after resizing to my desired resolution.
Quote from: JulianH on June 08, 2013, 09:25:19 PM
...
One thing I do for sure is disabling sharpening when converting the dngs. I do add it but only after resizing to my desired resolution.
Julian, how do I do that? thanks
Quote from: goldenchild9to5 on June 08, 2013, 09:15:40 PM
In what mode are you getting (2000x720) ? is it on 5X or 10X mode, or regular 16:9 aspect ratio? I was just reviewing some footage that I just shot with the new Unified build it seems that the shadows are really getting crushed, I'm seeing less detail in the shadows than in the May 28th Build.
1.
resolution is 2000x750 (can also do 1920x720) in zoom mode - CinemaScope 8/3 - i love it.
at the moment, you can't see what you're shooting which may be why i like it tracking the framing issue in a separate thread - http://www.magiclantern.fm/forum/index.php?topic=6082.msg48288;topicseen#msg48288 (http://www.magiclantern.fm/forum/index.php?topic=6082.msg48288;topicseen#msg48288)
2. have to shoot more to look for any black crushing.
The issue can't be fixed once the aliasing got in the digital domain; you just can't fix it in post. Well, maybe if you are Ken Rockwell so you can break some physics laws...
You can also record slightly out of focus. This will work.
Read some signal processing theory before blaming ML or conversion tools or whatever other software things.
Quote from: rommex on June 08, 2013, 09:18:14 PM
I do hope there something in the conversion, or else my investment is futile.
I did Raw2DNG -> Import to AE CS5.5 -> Save Frame
What version of Raw2DNG are you using?
Quote from: GregoryOfManhattan on June 08, 2013, 09:29:26 PM
1. resolution is 2000x750 (can also do 1920x720) in zoom mode - CinemaScope 8/3 - i love it.
at the moment, you can't see what you're shooting which may be why i like it tracking the framing issue in a separate thread - http://www.magiclantern.fm/forum/index.php?topic=6082.msg48288;topicseen#msg48288 (http://www.magiclantern.fm/forum/index.php?topic=6082.msg48288;topicseen#msg48288)
2. have to shoot more to look for any black crushing.
That's awesome man we are inching away, when you get a chance please check it out.
Quote from: goldenchild9to5 on June 08, 2013, 09:37:36 PM
What version of Raw2DNG are you using?
I'm looking into properties of .exe file and there is no info on version. Where can I look up it?
Quote from: a1ex on June 08, 2013, 09:31:42 PM
The issue can't be fixed once the aliasing got in the digital domain; you just can't fix it in post. Well, maybe if you are Ken Rockwell so you can break some physics laws...
You can also record slightly out of focus. This will work.
Read some signal processing theory before blaming ML or conversion tools or whatever other software things.
Thanks for a nice answer )
Quote from: goldenchild9to5 on June 08, 2013, 09:15:40 PM
In what mode are you getting (2000x720) ? is it on 5X or 10X mode, or regular 16:9 aspect ratio? I was just reviewing some footage that I just shot with the new Unified build it seems that the shadows are really getting crushed, I'm seeing less detail in the shadows than in the May 28th Build.
Whoe! . . . I did not even care to try it before but yes stable at 2000x750 also!! Note: this is 5x zoom mode
Are the zoom 5x mode colors fixed in the new build? I can't fix them in ACR on 28th may footage.
Quote from: a1ex on June 08, 2013, 09:31:42 PM
The issue can't be fixed once the aliasing got in the digital domain; you just can't fix it in post. Well, maybe if you are Ken Rockwell so you can break some physics laws...
You can also record slightly out of focus. This will work.
Read some signal processing theory before blaming ML or conversion tools or whatever other software things.
I have found absolute 0 sharpess in the ML menus combined with 0 sharpness in picture style helps . . . But I'mnot seeing that much crap like that guy is getting. He shot the worst scenerio possible!
Gregory, the build works like a charm. Thank you so much for the hard work you have done. I got 220 frames of full 16:9with a sandisk extreme 60mb/s when with the previous buidl I could only make 50. Good work dude.
Re-reporting about testing 3 Canon 50D cameras. This morning after going through a series of ML feature sets, specifically global shutter, histogram, and 3:2 display mode, I was able to pass by the 52MB/s recording limit. I am using a 64GB 1000x Komputerbay card, the same card that was writing continuously in a 5:3 aspect ratio on a second Canon 50D camera. Anyway, in my last post I had mentioned that the serial number looked like a much later serial number... It made me wonder if there was some type of Canon factory quality control issue... Rest assured, this is not the case. I had a breakthrough in recording tests after adjusting the ML feature sets and seeing a difference in the write speed per second and also the number of frame captured before the recording stopped. In other words, I was fine tuning the camera. And after shooting about 20 videos in less than 3 minutes and referencing the write speed and frame per second number the camera suddenly began recording upwards of 60MB/s. Interestingly, the tests before, using the same setting as that of the second camera, were only producing a maximum of 54MB/s write speeds. I believe that I was able to reach this recording speed by turning on and off global shutter, histogram, and 3:2 aspect live view mode. It's like the monster woke up by toggling these feature sets on and off. They are now currently turned on. And I have no trouble recording at any resolution.
Sorry that I don't have an exact answer as to why the camera wasn't recording continuously past a 2:1 aspect ratio, however, the camera is now capable of writing a 4GB file in 3:2 aspect ratio with 3-4 bars on screen at a stable 67MB/s write speed.
Got the day off from work... Will be testing away!!! Woohoo! Thanks ML! Thanks everyone!
Quote from: GregoryOfManhattan on June 08, 2013, 09:03:44 PM
beyond 1k - my 08June13 build is a cinema camera - getting stable 2000x720 14bit raw video - wow!
~/bin/raw2dng /Volumes/transfer/ML-TEST/M08-1349-combined.RAW
Resolution : 2000 x 750
Frames : 6979
Frame size : 2625536 bytes
Frame skip : 1
FPS : 24.000
Processing frame 1 of 6979...
Vertical stripes correction:
1.000 1.000 0.994 0.991 1.000 1.003 0.997 0.994
Processing frame 4679 of 6979...
shooting GD enabled (had to turn off everything)
Hack mode
stable @62.5MB/s
note, it is possible to get your 50D into a very weird state as i did this morning and have it show the Canon GUI.
if you see things like that - reset everything and go through the checklist of settings (which i wish were edited into the first post of this thread)
Whoa, so that's spanning working for you then too? Processed with the cat command I'm assuming?
Just tried joining the files in terminal and getting the bizarre switch to pseudo false color at the break in files. Any hope for spanning?
I have also had issues with aliasing, specifically with ropes on a golf course. There is one way to bring back the aliasing ever so much... In ACR adjust your settings for Chromatic Abboration - - Defringe - - All Edges... - - >It will help take the edge off the color fringed aliased areas.
@artiswar - yes spanning works - wished the names fell into default bash order but
cat M08-1601.RAW M08-1601.R01 M08-1601.R02 M08-1601.R03 > M08-1601-combined.RAW
works fine for me on osx (or use the windows equivalent to concatenate files) - what command did you try?
for those who would like to use the rawmagic 1.0 to convert to cinemaDNG on osx - there is a bug with today's raw files in rawmagic as reported already by @rockfallfilms @goldenchild9to5 - no need for further bug reports or testing - we have to wait a while to try again with Resolve (worked for me with a build yesterday).
files work fine with raw2dng
@araucaria - raw file colors are OK now in zoom mode and process fine.
(with older builds i found that gimp and RPP had easily available black point settings which could render OK images)
@rommex to convert from DNG to tiff or jpeg you may also want to try RPP - http://www.raw-photo-processor.com/ ( Наша группа поддержки http://raw-rpp.livejournal.com/ )
@LEVISDAVIS 67MB/s stable would be amazing
@Nachelsoul - the new build has many more resolutions possible, so on a slower card you can get 16x9 by reducing the maximum width. try the various options in the Raw Rec menu, try 1344 or 1280 see where you get continuous recording
Quote from: LEVISDAVIS on June 08, 2013, 10:12:53 PM
I have also had issues with aliasing, specifically with ropes on a golf course. There is one way to bring back the aliasing ever so much... In ACR adjust your settings for Chromatic Abboration - - Defringe - - All Edges... - - >It will help take the edge off the color fringed aliased areas.
Also, Set the Noise Reduction "Color" setting in ACR to 100, and the Color Detail to 0.
Quote from: menoc on June 08, 2013, 09:52:11 PM
I have found absolute 0 sharpess in the ML menus combined with 0 sharpness in picture style helps . . . But I'mnot seeing that much crap like that guy is getting. He shot the worst scenerio possible!
Right on Menoc.. that's what I've been doing all along and the images comes out just perfect..
Hi Guys,
Fantastic work all round to everyone involved.
Im new to all this but i thought i would run this past you guys with your vast experience, maybe you can work it out to help the build.
Could you tell me the longest i should expect to get from 3:2 mode in regards to recording time? or any mode at that. Or can someone give me a resolution that they are unable to reach 4gb with so I can test.
Sorry if it is a silly question but i was messing around and stumbled across a way for the camera to continue record for as long as your card can take or at least 10,000 frames at 66.5MB/s. Whilst keeping the stars down.
I find that after this, sometimes the files are accessible and sometimes they are not.
Data is certainly on the card but it doesn't always let me extract the dng's, but that may be down to my process...as im still learning.
I have tried to attach a screenshot showing 25gb at 66.8 mb/s, but not sure how to lol.
Like i said im not at all knowledgeable in this area so if i sound crazy or there is a stupid obvious reason then its okay...just thought i would run it by you guys first. So go easy on me.
Quote from: GregoryOfManhattan on June 08, 2013, 10:19:42 PM
@artiswar - yes spanning works - wished the names fell into default bash order but
cat M08-1601.RAW M08-1601.R01 M08-1601.R02 M08-1601.R03 > M08-1601-combined.RAW
works fine for me on osx (or use the windows equivalent to concatenate files) - what command did you try?
Did the same, do you have to enter the directory of the file along with the name? (Noob question).
Heres the frames
(http://i42.tinypic.com/binerq.png)
(http://i44.tinypic.com/2ypmf5g.png)
Quote from: menoc on June 08, 2013, 09:52:11 PM
I have found absolute 0 sharpess in the ML menus combined with 0 sharpness in picture style helps . . . But I'mnot seeing that much crap like that guy is getting. He shot the worst scenerio possible!
Any sharpness settings only affect what you see on the liveview screen, being a raw file?
Quote from: GregoryOfManhattan on June 08, 2013, 10:19:42 PM
@artiswar - yes spanning works - wished the names fell into default bash order but
cat M08-1601.RAW M08-1601.R01 M08-1601.R02 M08-1601.R03 > M08-1601-combined.RAW
works fine for me on osx (or use the windows equivalent to concatenate files) - what command did you try?
for those who would like to use the rawmagic 1.0 to convert to cinemaDNG on osx - there is a bug with today's raw files in rawmagic as reported already by @rockfallfilms @goldenchild9to5 - no need for further bug reports or testing - we have to wait a while to try again with Resolve (worked for me with a build yesterday).
files work fine with raw2dng
@araucaria - raw file colors are OK now in zoom mode and process fine.
(with older builds i found that gimp and RPP had easily available black point settings which could render OK images)
@rommex to convert from DNG to tiff or jpeg you may also want to try RPP - http://www.raw-photo-processor.com/ ( Наша группа поддержки http://raw-rpp.livejournal.com/ )
@LEVISDAVIS 67MB/s stable would be amazing
@Nachelsoul - the new build has many more resolutions possible, so on a slower card you can get 16x9 by reducing the maximum width. try the various options in the Raw Rec menu, try 1344 or 1280 see where you get continuous recording
. . .and if you're the type that does does not like the command line, you can use a hex editor to combine the files. I use "Hex Fiend", it's light and fast and loads >4GB files with no problem. All I do is copy and paste the hex code of the spanned files at the end of the first .RAW file, then save the new file with a new name or to a different location.
Now with file spanning working, unlimited recording is possible . . . Interviews and narratives are a go!
@artiswar yes, you need to
cd DIRECTORY_OR_PATH_WHERE_THE_FILES_ARE
to the directory where the files are or include the directory (or path) as part of the "cat" concatenate command.
cat /Volumes/EOS_Digital/DCIM/100CANON/M08-1601.RAW Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R01 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R02 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R03 > ~/Desktop/M08-1601-combined.RAW
where is the weird frame from ? the very last frame or somewhere in the middle.
have not tested enough with today's gamechanger build, but i have seem corrupt frames near the end of files in other builds.
Quote from: artiswar on June 08, 2013, 10:46:31 PM
Did the same, do you have to enter the directory of the file along with the name? (Noob question).
Quote from: Roman on June 08, 2013, 10:57:02 PM
Any sharpness settings only affect what you see on the liveview screen, being a raw file?
You're right. RAW is only affected by Exposure settings. The effect you see is being done by your RAW converter . . .
Another test with the latest build, this time at 25fps:
Global draw on
Raw histogram on
Sound set to OFF in raw video menu
Waveform on (not sure if waveform is relevant in RAW mode or not?)
Write speed 59mb/s
Komputerbay 64gb 1000x
Pushing 67MB/s no problem with Komputerbay 64GB 1000x... Had to go through every setting and look at each and every sub-menu. I turned off anything not related to video... I'd be more specific but there are so many menus and adjustments... However, it's good to know there is a that much room for writing files, right?
I do use histogram, global draw, "Under 3:2" in the live view menu and also set my frames per second to low-light frame rates. This is all with the latest build.
Is RAWMagic working for you guys with combined files??
Quote from: GregoryOfManhattan on June 08, 2013, 11:12:00 PM
@artiswar yes, you need to
cd DIRECTORY_OR_PATH_WHERE_THE_FILES_ARE
to the directory where the files are or include the directory (or path) as part of the "cat" concatenate command.
cat /Volumes/EOS_Digital/DCIM/100CANON/M08-1601.RAW Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R01 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R02 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R03 > ~/Desktop/M08-1601-combined.RAW
where is the weird frame from ? the very last frame or somewhere in the middle.
have not tested enough with today's gamechanger build, but i have seem corrupt frames near the end of files in other builds.
Weird frame is towards the end of the files but exists for a good chunk, seemingly the spanned portion.
Quote from: LEVISDAVIS on June 08, 2013, 11:25:43 PM
I do use histogram, global draw, "Under 3:2" in the live view menu and also set my frames per second to low-light frame rates. This is all with the latest build.
What if you set FPS override to exact fps?
I think 'low light' is not ment for video, but to make the visibility better when shooting in the dark. Correct me if I'm wrong...
Quote from: artiswar on June 08, 2013, 11:30:05 PM
Weird frame is towards the end of the files but exists for a good chunk, seemingly the spanned portion.
Make sure when you're addressing you're home folder you start with the tilda (~). Such as: ~/Desktop/M08-1441.RAW
Quote from: menoc on June 08, 2013, 11:13:52 PM
You're right. RAW is only affected by Exposure settings. The effect you see is being done by your RAW converter . . .
hm i think i dont understand, why turning sharpness in ml menus down if it doesnt affect raw recording.
also picture styles dont have an influence on raw recording do they?
i would appreciate a less sharper image due to the problem of alaising (in my eyes the only "problem" of the 50D raw)
apart from that, its imagequality is just mindblowing and high prieced like.
reverence
greetings and big thanks:)
Quote from: JulianH on June 08, 2013, 11:48:04 PM
What if you set FPS override to exact fps?
I think 'low light' is not ment for video, but to make the visibility better when shooting in the dark. Correct me if I'm wrong...
23.976 is better to work with when you sync with audio recorded at 48khz. Most everything digital is shot at 23.976 to avoid the extra step of slowing film shot at 24 to 23.976 for digital . . . But it's not set in stone. You can shoot at true 24 as well but you'll have to get your audio sped up or slow to sync it with the video.
Quote from: menoc on June 09, 2013, 12:17:56 AM
23.976 is better to work with when you sync with audio recorded at 48khz. Most everything digital is shot at 23.976 to avoid the extra step of slowing film shot at 24 to 23.976 for digital . . . But it's not set in stone. You can shoot at true 24 as well but you'll have to get your audio sped up or slow to sync it with the video.
You can use FPS override 'exact fps' at 23.976 (or something very, very close at least I think. You have to tweak the clock a bit in the fps override settings). I just thought using the 'exact fps' option would make more sense than 'low light'.
Quote from: Ifani on June 09, 2013, 12:05:05 AM
hm i think i dont understand, why turning sharpness in ml menus down if it doesnt affect raw recording.
also picture styles dont have an influence on raw recording do they?
i would appreciate a less sharper image due to the problem of alaising (in my eyes the only "problem" of the 50D raw)
apart from that, its imagequality is just mindblowing and high prieced like.
reverence
greetings and big thanks:)
Well, I was wrong in saying that sharpness affects RAW - it doesn't. Basically, RAW is only affected by your exposure settings like aperture and shutter. When you open a RAW file in a RAW converter such as ACR, then ACR will apply some default secondary settings such as sharpness. So, the best way to avoid moire is like Alex said, avoid that sort of environment, shoot a bit defocused or use a filter - which is not available for the 50D at this point.
Quote from: JulianH on June 09, 2013, 12:27:38 AM
You can use FPS override 'exact fps' at 23.976 (or something very, very close at least I think. You have to tweak the clock a bit in the fps override settings). I just thought using the 'exact fps' option would make more sense than 'low light'.
They called it "Low light" because it does help in low lighting situations.
Doesn't it mean it helps you to view the live view better in low light situations? Live view is 1/30 by default. Say you a shooting at 1/15 sec (photo) you can use fps override low light to get the actual 1/15s preview. That's what I understand at least.
Just noticed that on the june8 build you can choose exact fps at 23.976 - so I'm using that. Probably low light at 23.976 does exactly the same.
Firing up the new build... Results soon!
Finally had a chance to quickly try out the June 8th build
:-) :-) :-)
I'm getting a rock solid 2000x800 with write speeds maxing out at slightly below 66 MB/s. And this with my Komputerbay card benchmarking way below Gregor's. Also works with GlobalDraw on, all features underneath explicitely set to "off".
Great work, Gregor! Thanks!
How do I set 2000x800? If I go into the size options and try to change anything it just defaults back to 1584x892
5x zoom only.
2000x800 is set in 5x zoom mode with 2048 width and Aspect Ratio 2.5:1 (you will only be able to access these settings if you activate LV, then zoom 5x and then go into the ML RAW menu)
Ah right, thanks for that.
With the June 08 build, on start up I'm getting a ML/DATA/FONTS.DAT retry...
As descriptive as the error is, I get a font (in ML menu) that may be understood by someone living over the greater seas. How shall it be rectified?
By the way, thanks for the work guys -I purchased a 50D and am thinking of selling the 60D for another 50D plus cards -have been using ML for a year now and have not looked back despite the naysayers.
Edit:
Followed these instructions and it solved the problem:
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
I predict we could do at least 2K RAW or better if we can get 10-bit recording to work . . .
Using the latest unified build from today myself. Very stable, even when filming the full 1:1 frame of the sensor. I'll definitely be using this feature for plate shooting now for a 2.35:1 re-frame :)
i tried the build of today without good results.
maybe because i don't know where to look at.
did the scripts folder.
loaded the raw_rec module
but i can't figure out how to start recording in raw or define what resolution to use. no place to be found for these 2 issues.
forgot to write that the magic.sym doesn't seems to load.
i erased magic.cfg so ML can make a fresh one. without any results
the 28th may is working. i chamged the raw_rec.mo for the one of today but got the vram_clear_lv failed to link modules message
Using the May 28 build and the settings recommended throughout this post, I did a test run and posted the video on Vimeo. I have a Lexar 64Gb 1000X card and was able to record at 16:9 at 57mbps without filling the buffer but had issues at 3:2 at 71mbps and couldn't achieve more than 450 frames before stopping.
I used an external SmallHD monitor via HDMI and had weird intermittent frame garbage. I'll post a DNG of the weird magenta blown frame. Happened in both 16:9 and 3:2.
Workflow was RAW>raw2dng>Photoshop RAW>TIFF>Quicktime>FinalCut 7.
Shot with a Moller Bolex 1.5x anamorphic lens and Zeiss 80mm f/2.8.
www.vimeo.com/67965891
You might notice in some of the clips (https://vimeo.com/67965891) a slight jump, which looks similar to a dropped frame.
I didn't notice the magenta blips in the camera display, but when hooked up to a SmallHD HDMI external monitor, I saw the attached frames. Not consistent and sometimes 1, but usually not more than 3 in a 30-second span.
Happened with both 16:9 at 1600 using all the recommended settings as well as 3:2 at 1600. Pretty consistent and roughly 90% of my RAW files have them.
Examples:
http://www.flickr.com/photos/operationstarfish/8993240548/
http://www.flickr.com/photos/operationstarfish/8993241174/
http://www.flickr.com/photos/operationstarfish/8993241934/
Quote from: rockfallfilms on June 08, 2013, 05:52:34 PM
Global draw etc off. the first 3 files were fine at 59mb/s then the write speed dropped on any further files i tried to record.
Formatting in camera didn't change anything but repartitioning and then formatting put the write speed back to 59mb/s
Hey can you tell me more about partitioning the CF card? I think I can do it though disk utility (mac) but what will this do / what size partition and what format FAT etc? Thanks.
Quote from: Roman on June 08, 2013, 08:23:28 AM
...
6. Not 50D specific, but I find it a real pain to autofocus in video mode, and usually only do it at the start of a shot. So what I tend to do, (if not manually focus0 is turn liveview off, autofocus the camera the 'normal' way, (as this works very quickly) and then switch it back to liveview and go from there. Would it be possible to automate this sequence? Live view off > autofocus > focus confirmation > liveview on? Assuming anyone else would find that handy of course. If that could be automated to a half shutter press or something, it would be freaken sweet.
You need a high resolution external monitor to get the focus right when filming HD video. I believe there's no way around that.
Not really, if the focus isnt changing through the shot.
It's just that the above is the quickest method.
(I have a lilliput monitor but dont use it if I can help it)
A quick test, worst case scenario for me, high DR and very fine detail and shot with a pretty bad 28-70 canon 3.5-4.5 at f9 (waiting for nikkon adapter). I got a lot of aliasing. I made some slides which turned out to be horrible but at least you can see the movement which induces aliasing.
1592x636 1:1 mode, build May 28th. Had to shoot in this low resolution as I'm still stuck with some old 4gb 32mb/s card.
Workflow. raw2dng->AfterEffects->h264 (I tried to compile the compositions and use them in PremierePro but I was getting strange speed jumps)
I fixed the alisasing with defringe option in ACR and sometimes with NR ,color 100, colordetail 0, although you have to be careful not to kill your colors.
Quote from: Frerichs on June 09, 2013, 06:25:10 AM
You might notice in some of the clips (https://vimeo.com/67965891) a slight jump, which looks similar to a dropped frame.
I didn't notice the magenta blips in the camera display, but when hooked up to a SmallHD HDMI external monitor, I saw the attached frames. Not consistent and sometimes 1, but usually not more than 3 in a 30-second span.
Happened with both 16:9 at 1600 using all the recommended settings as well as 3:2 at 1600. Pretty consistent and roughly 90% of my RAW files have them.
Examples:
http://www.flickr.com/photos/operationstarfish/8993240548/
http://www.flickr.com/photos/operationstarfish/8993241174/
http://www.flickr.com/photos/operationstarfish/8993241934/
I get this with a monitor connected too.
Hi guys,
Firstly, @GregoryOfManhatten - Excellent work on your latest (Unified) build. I did receive your email and I'll update the first post to reflect developments. Sorry I couldn't do it sooner but I've had a very tough week at work. (UPDATE: First post now updated)
I finally got my CF cards earlier this week and had about 10 mins to try them out. My Komputerbay 64gb was DOA (neither the camera or card reader would recognize it) so that's gone back and my temporary solution of a Kingston 600x could only manage 40-45MB/s in-camera and only 61MB/s with Crystalmark on a Transcend USB3 reader (http://www.transcend-info.com/products/Catlist.asp?modno=331). I would not recommend the Kingston cards for raw video but they are great value for H.264.
Obviously I was a bit annoyed and impatient to wait another couple of weeks for a working Komputerbay card so I did some research yesterday and found that the Transcend 600x cards should do the job (90MB/s max write speed). I bought a 16gb card this morning and I'm happy to report it writes flawlessly up to 60-65MB/s in the 50d (2000x750 shoots continuous). The Transcend 1000x card looks like it will be even better but beware that you need at least the 32GB card or greater as the 16GB 1000x card is considerably slower than the 600x. If my replacement Komputerbay card has any issues I'll just stick to Transcend cards.
BTW I noticed a few posts about battery life when shooting raw video. If you purchased a 50d secondhand with batteries your should consider buying new ones. Look for replacements rated at least 1700mAh as they will last longer and charge faster than original Canon batteries. I recommend Phottix if you can get them.
I suppose I should go shoot something now ::)
p.s. @JulianH - No luck yet with finding a J9 but I'm looking ;)
... Been processing footage in ACR... Adjusted the output setting from Screen to Glossy Paper... Final images had vertical streaks in the image... Thought it was associated with the camera's native recording. Discovered that it was not the issue when I processed footage via RawMagic (doesn't work properly with 50D and utilizing the current June 8 build). Anyway, had posted earlier that it was an inherent factor in a shooter's ability to capture greater bit depth and image resolution... Good thing for tests, right?
... The ETTR technique (exposure to the right) is really pushing the boundaries of dynamic range and image resolution. Just sort of hanging back and thinking about a fast work-flow post-production procedure and of course proper file spanning. (Note: have not shot over 4GB yet and need to test. It appears that other users have spanned files and yet others haven't.)
The quality of the footage is really driving my abilities as a shooter into a whole new light. I'm quite satisfied with how well the camera consistently responds scene after scene.
Thanks.
Quote from: Andy600 on June 09, 2013, 11:29:58 AM
BTW I noticed a few posts about battery life when shooting raw video. If you purchased a 50d secondhand with batteries your should consider buying new ones. Look for replacements rated at least 1700mAh as they will last longer and charge faster than original Canon batteries. I recommend Phottix if you can get them.
Having battery issues myself. Just wondering what the average usage time was for the folks out there?
My first 2 canon batteries that arrived with the 50D were only lasting 2 mins and 10 mins.. so ordered a new (non canon) and it worked well for first day, but then the charger was saying full, but the camera said 1/3 and not enough to update firmware. I'm leaving it on charge for ages and seems to get a bit more from it, hoping to get the full icon like the first day. Have been counting to 5 before removing CF card also..
So, how long shooting time do you get from you batteries? Canon and others?
Thanks!
My batteries last about 30 mins but they came with the camera so are probably old. I've just ordered a couple of duracell replacements so I'll see how I get on with those.
Quote from: rockfallfilms on June 09, 2013, 01:57:17 PM
My batteries last about 30 mins but they came with the camera so are probably old. I've just order a couple of duracell replacements so I'll see how I get on with those.
Sweet, thanks for that. I'm used to my 7D batteries going for ages! I have read somewhere that as 50D not designed for video, it will use a lot of power (live view etc) All good though.
Got 2 more batteries on the way so will be sorted soon enough. Still would be good to get some more input. Anyone using NEW Canon batteries out there? How long you get out of them shooting RAW video?
What are people using to nail exposure, raw histogram? raw zebras?
What do the numbers in the red circle mean on the histogram?
1. raw file format was refined slightly yesterday and some of the post processing tools need to be updated to use the latest raw2dng code so you may experience temporary issues with your favorite tool (as did those who tried rawmagic beta 3 yesterday which is better now that Thomas Worth released beta 4)
2. pink frames - may be related to the glitch in the matrix caused by these changes to raw
seem to be gone in a build i tested with this morning's code - 11GB without the pinkness (i.e. no pink glitchy frames as artiswar and others have posted).
(do get alIaSiNG which we will need to shoot around on the 50D)
Sorry guys, less progress on this side. I guess my komputerbay 1000x 64gb is defective. I cannot get stable transfers using 2 different cardreaders (get IO timeouts) and in raw recording mode It suddenly stops recording / crashes during recording (while I have descent speed and just one star buffer)
Hello,
here is my my 50D RAW Video test:
Do you know how to get rid of the problem that sometimes exposure is automatically controlled by the camera itself?
recovering footage with black borders.
for footage from older builds before we fixed the black borders on the raw frames, the "black point" is incorrect in resulting DNG files and it is difficult to process them.
if you want to use such shots, i would process them to 16bit tiff with gimp.org (cross platform) which has a slider on one of the color curve windows you can use to shift the black point then try out the batch tools to get it to process a directory full of tiff files.
on the mac you can also try RPP with the Black Point at some really large value, like 10.0
zoom mode for cinemascope - known issues are covered in another thread.
Topic: 1k 50D raw cinemascope difficult when LiveView not showing 2000x750 8/3
http://www.magiclantern.fm/forum/index.php?topic=6082.msg44905#msg44905 (http://www.magiclantern.fm/forum/index.php?topic=6082.msg44905#msg44905)
framing is not correct
display is magenta (pink) no matter what Preview Mode you are in (auto, canon, ML Grayscale, or Hacked)
Latest build working well for me :) but I think there may be an issue with the exposure warning message. I'm only using manual lenses so I'm not sure if this is relevant when using electronic lenses but when I see the over exposure warning and stop-down the over exposure warning increases by a stop (i.e. it's doing the opposite of what it should be doing). Can anyone else confirm?
What exposure warning message?!
You have full manual exposure, right?
Quote from: araucaria on June 09, 2013, 10:30:35 AM
A quick test, worst case scenario for me, high DR and very fine detail and shot with a pretty bad 28-70 canon 3.5-4.5 at f9 (waiting for nikkon adapter). I got a lot of aliasing. I made some slides which turned out to be horrible but at least you can see the movement which induces aliasing.
1592x636 1:1 mode, build May 28th. Had to shoot in this low resolution as I'm still stuck with some old 4gb 32mb/s card.
Workflow. raw2dng->AfterEffects->h264 (I tried to compile the compositions and use them in PremierePro but I was getting strange speed jumps)
I fixed the alisasing with defringe option in ACR and sometimes with NR ,color 100, colordetail 0, although you have to be careful not to kill your colors.
...vimeo....
wow, this is AMAZING! thanks for showing this. I hope I will overcome my moire problems )
@A1ex Yes, full manual. I'm seeing a black bar with 'preview over exposed by 0.5 EV'. If I stop down 1 stop it increases to 1.0 EV if I increase shutter speed it changes to 1.0 EV (sorry, meant if I change shutter speed the warning changes. If I stop down, the warning message remains at 0.5 EV)
That happens if you ask for some exposure parameters that are out of range (usually if you have FPS override on, which limits shutter speeds a lot).
And... you are in photo mode.
@a1ex - ah ok, I get it. Thanks! :) I have FPS override on. BTW, I'm curious to know how we can now have 2k width when DNGs were previously restricted to 1920? It shoots stable at 2000x750 up to 25fps for me 8)
See here: http://www.magiclantern.fm/forum/index.php?topic=6215
I'll restrict raw video to movie mode to avoid this kind of mistakes. The raw backend does behave differently in photo liveview, because... I'm assumming you are taking pictures in photo mode, not videos.
I don't have video mode enabled (haven't actually tried H.264 on the 50d yet LOL). Will restricting it have any impact on the length of shots I can get? Photo mode seems very stable to me.
You must enable it. In photo mode, most the raw stuff (white levels, histogram) behaves differently, it's optimized for getting a histogram that matches the CR2 pictures. For raw video, this can cause severe exposure issues.
In photo mode, you are not even getting the exposure values from menu (not even in expo override mode), you are just getting something with equivalent brightness (ExpSim). And white level on the raw files recorded in photo mode will be wrong.
Well that's something i didn't know :D Thanks.
I assumed if it was working in photo mode then it was ok. I just did my first few shots 2000x750 and it's looking great although exposure wasn't exactly doing what the meters were telling me. I'll try again now with video mode enabled.
Quote from: GregoryOfManhattan on June 09, 2013, 03:30:34 PM
1. raw file format was refined slightly yesterday and some of the post processing tools need to be updated to use the latest raw2dng code so you may experience temporary issues with your favorite tool (as did those who tried rawmagic beta 3 yesterday which is better now that Thomas Worth released beta 4)
2. pink frames - may be related to the glitch in the matrix caused by these changes to raw
seem to be gone in a build i tested with this morning's code - 11GB without the pinkness (i.e. no pink glitchy frames as artiswar and others have posted).
(do get alIaSiNG which we will need to shoot around on the 50D)
Exciting stuff. When should we see this trickle down to non developers? Still joining files in Terminal?
Oops.. I've been working with Movie mode disabled as well! (explains why I couldn't really understand the way exposure worked in live view I guess) Thanks for the tip A1ex. Turning it on by default when raw rec is enabled makes sense!
Giving Auto ETTR a spin now. I'm working with a manual lens, the variables are iso and shutter speed. I can set a minimum shutter speed, but can't change the iso limits and it doesn't seem to go higher than 1600.
Is it possible to use AutoETTR with a fixed shutterspeed (and manual aperture)? Baiscally that would be auto iso, but still, that sounds the most practical to me for video.
I've also had movie mode turned off, that explains why my exposure hasn't been consistant.
Quote from: John-Jo on June 09, 2013, 02:36:20 PM
Sweet, thanks for that. I'm used to my 7D batteries going for ages! I have read somewhere that as 50D not designed for video, it will use a lot of power (live view etc) All good though.
Got 2 more batteries on the way so will be sorted soon enough. Still would be good to get some more input. Anyone using NEW Canon batteries out there? How long you get out of them shooting RAW video?
I have owned a few 50Ds for a couple of years. The battery life is phenomenal and I would base all your issues on old or cheap batteries. I use Canon originals, then also 2200mAh replacements designed for CNBP511. Bought for about $11 each on Amazon a few years back & still going strong.
I have shot over 500 hours of 1080p video footage on the same batteries for my film production company where each charge lasts approximately 90 minutes per battery. With the 50D charger, this is up to 3 hours per charge using Magic Lantern. You could argue that this was HD and not RAW, but I've also used the 50D as an actual camera with over 2,000 shutter actuations per charge over the course of 5 hours on various swimsuit photoshoots.
The short:
this camera is a tank & I'm glad to see so many other users finally realizing it is the hidden gem in the Canon lineup. My photos with it: OpenVase (http://openvase.com) - video with it on my Youtube (http://youtube.com/krashnik).
By enabling Movie Mode the live view is forced to a 16:9 crop. So when recording 4:3 or 3:2 a part of the image is blocked by the GD info and/or black bars. Can't find a way to change the live view settings for movie mode either.
On another note: I seem to have lost a buffer star. 5 available now, used to be 6. Malloc numbers are the same as before though and double checked settings in the Canon menu (jpg, all custom functions related to image quality off).
Can't really help with that, this is how ML looks in movie mode on all cameras. You can try a custom cropmark.
Thanks A1ex, will do. Turning off global draw also helps.
/edit: just found out I can clear overlays with half press for example, that would be good so I can just clear it during framing.
Good thing about Movie mode turned on, the aperture now actually changes during live view with electronic lenses :) (doh!)
@JulianH - I've got 6 buffer stars with Global Draw enabled just for the raw histogram. Enabling movie mode doesn't seem to affect anything in so far as frame amounts etc but it looks like it's cured the pink screen in 5x crop (WB must be set correctly or it does get a bit pink so it seems to act as a good warning to set it) and (of course) exposure now seems to work correctly.. all of a sudden the colors just sing!
For the LV problem try playing around with display settings - Display > Advanced Settings (might help if you haven't already been there).
Loving this 2k Cinemascope. I seem to be getting about 10-15% more frames than the setting suggests and hitting about 62MB/s write speed. Maybe it's card related, I dunno but I seem to have golden settings ATM. 8)
Quote from: Andy600 on June 09, 2013, 07:42:28 PM
@JulianH - I've got 6 buffer stars with Global Draw enabled just for the raw histogram. Enabling movie mode doesn't seem to affect anything in so far as frame amounts etc but it looks like it's cured the pink screen in 5x crop (WB must be set correctly or it does get a bit pink so it seems to act as a good warning to set it) and (of course) exposure now seems to work correctly.. all of a sudden the colors just sing!
For the LV problem try playing around with display settings - Display > Advanced Settings (might help if you haven't already been there).
Loving this 2k Cinemascope. I seem to be getting about 10-15% more frames than the setting suggests and hitting about 62MB/s write speed. Maybe it's card related, I dunno but I seem to have golden settings ATM. 8)
Do you know what the equivalent cropfactor is in 2000x750 5x mode?
Quote from: ashtrai on June 09, 2013, 08:12:06 PM
Do you know what the equivalent cropfactor is in 2000x750 5x mode?
I believe its a bit over 3x. Could be mistaken. That puts it in the BMPCC territory.
Loaded a fresh battery and got my 6 stars back. Don't know if it's related but I'm happy :)
artiswar more like 4 - isn't it?
4572x3168 maximum resolution (wikipedia)
4752/1920 *1.6 = 3.96
for the 2000 wide (mistake) it would be 3.6 crop factor
JulianH - i always see magenta in zoom mode no matter what the white balance - unless i do a G/M Shift of between +7 and +10 Green - then it can look correct to my eyes
Quote from: artiswar on June 09, 2013, 08:32:11 PM
I believe its a bit over 3x. Could be mistaken. That puts it in the BMPCC territory.
Quote from: GregoryOfManhattan on June 09, 2013, 09:00:53 PM
artiswar more like 4 - isn't it?
4572x3168 maximum resolution (wikiepdia)
4752/1920 *1.6 = 3.96
for the 2000 wide (mistake) it would be 3.6 crop factor
JulianH - i always see magenta in zoom mode no matter what the white balance - unless i do a G/M Shift of between +7 and +10 Green - then it can look correct to my eyes
Thanks guys.
Same here Gregory.
Why is 2000 a mistake? It seems to work fine? Any disadvantages to it compared to 1920?
from a question Andy600 asked
Quote from: a1ex on June 09, 2013, 04:46:48 PM
See here: http://www.magiclantern.fm/forum/index.php?topic=6215
I'll restrict raw video to movie mode to avoid this kind of mistakes. The raw backend does behave differently in photo liveview, because... I'm assumming you are taking pictures in photo mode, not videos.
is a1ex is saying he will disable these unusual widths for raw video mode, as they should only be there for photos (silent pics) or is he saying that he will automatically activate movie mode when you turn on raw video or both or ...? - we will see soon enough.
Quote from: JulianH on June 09, 2013, 09:02:59 PM
Same here Gregory.
Why is 2000 a mistake? It seems to work fine? Any disadvantages to it compared to 1920?
a disadvantage is you will have to scale video for one of the current "standard" output formats.
White level/stuff like that is different for movie + photo... so there is a faux movie mode he made to fix the indicators if you're shooting video and not pictures. Otherwise indicators and maybe black level detection would have been wrong.
He means restrict raw video to movie mode because I wasn't using movie mode. Maybe he will enable movie mode by default when raw recording is enabled... It's one less thing to remember to do before hitting record :)
Have I got this right? Shooting in crop mode only uses the left part of the sensor?
Ahh.. well that restriction isn't really a restriction.
It probably uses whichever part of the sensor you want... depending on where you move the zoom box. That seems to be the case on other cameras.
Ah, I disabled the zoom box ::) It must have retained the last used settings
Amazing new build!
In M video mode - I ran the RW test then starting flipping around in LiveView (with global draw on, focus assist, magnify at 3:1 and histogram on) before RW test had finished. Camera got hot quite quickly. To the point where I had to unplug and get batteries out. But since then all OK!
Also excuse my ignorance but I got the 9th Jun build but can't get up to 2000 pixels by anything. I am running KomputerBay 64gb 1000x. IN M mode with ML Exp locked for my EF Canon lenses...
thanks
I got about 3000 frames at 1920x818 and then my FPS randomly dropped to 21 FPS again while recording. When it happens, my exposure shifts slightly and the buffer goes to *. When I stop recording and go into the menu it looks like this:
(http://i39.tinypic.com/9h5n4j.jpg)
It takes 1 or 2 reboots to get back to 23.976 FPS. It only seems to occur in 5x zoom. Other than this little issue and the pink 5x zoom, the camera is performing incredibly well. I can get around 830 frames at 2000x852 before dropping on my Komputerbay x1000. Truly impressive.
+1 in the 50D RAW army :)
Just got the body for very cheap price, pretty much used but im going to replace some parts soon, so it will be like a new :)
Anyway i'll be glad to heavy test RAW video and provide as much info as possible.
Im going to shoot music video tomorrow, so can't wait to check it out in action!
(http://i.imgur.com/dNs65S7.jpg)
@evanamorphic: Your actual FPS is on 21.723? Why not put it on exact fps (optimize for) 23.976?
@Viente: welcome to the happy 50D owners club :)
In 600D RAW menu there is an opion to start shooting after desired number of seconds which is very handy! Is it possible to do something like this on 50D?
Quote from: JulianH on June 09, 2013, 09:49:06 PM
@evanamorphic: Your actual FPS is on 21.723? Why not put it on exact fps (optimize for) 23.976?
@Viente: welcome to the happy 50D owners club :)
I'll try optimize for 23.976 for awhile to see if it still occurs. I seem to get more frames when using the other optimize settings, I guess it's a trade off.
You might get more frames because the camera is actually shooting at a lower framerate?
- Again, correct me if i'm wrong.. this whole fps override thing with so many options is puzzling me a bit. To me the only logical choice seems 'exact fps' - since that's what we want to get after all..
You don't have to use the advanced mode ;)
Also, can you check for cpu usage when FPS override is on? Exact FPS does a bit of searching through all these timer combinations, so there may be surprises.
It just happened in "Exact FPS" as well. I couldn't tell when it occurred though.
(http://i42.tinypic.com/5kfrrn.jpg)
When FPS Override is on, CPU usage is at about 26% with LiveView on, and all overlays disabled. When FPS Override is off, CPU usage is between 28-29%
@evanamorphic where are you getting 22 fps from (it says 23.976 from 22) It should say 30 Ignore this, I re-read original post :-[
@Evan: your actual FPS is still weird...
Did you tweak your fps timers A+B? mine are on 686 and 1751, that gives me exact 23.976.
Quote from: a1ex on June 09, 2013, 10:15:40 PM
You don't have to use the advanced mode ;)
Just trying to help...
Or am I wrong that it isn't advisable to use an actual fps lower than 23.976?
Will check the cpu usage.
removed after re-reading the post I was trying to answer
I've fixed a similar FPS problem on 5D3 a few days ago.
@JulianH: you said FPS override is too complex. There is a beginner mode and an advanced mode, use the one corresponding to your skill level ;)
Quote from: artiswar on June 09, 2013, 08:32:11 PM
I believe its a bit over 3x. Could be mistaken. That puts it in the BMPCC territory.
Using 1920x1080 pixels in 5x mode would yield a crop factor of about 3.975. The sensor area being used is a little bit smaller as a regular 16mm film frame. Already did some calculations concerning this earlier in this thread.
I think the 50D is far more flexible now than the BMPCC. I'm so glad that these developments here happened before buying one.
QuoteIn 600D RAW menu there is an opion to start shooting after desired number of seconds which is very handy!
Yup, that will be in.
Btw, I also had time now to test the June 8th build.
Compared with May 28th build, I now have to switch off the RAW zebras and the colour histogram to yield a comparable performance. My KomputerBay 32GB card maxes out at 62-63MB/s in 5x zoom mode, 1920x818.
On the other hand, the framing and recording issues in 5x zoom mode are gone now.
It seems also that initially, the write performance is way lower, up until you run the "Card Buffer Benchmark" test in the Debug menu for about 1-2 mins, with LiveView turned on. It seems that ML picks then the best buffer size for your card.
Raw zebras are CPU intensive. Before you had YUV zebras with zero cpu. Just turn them off while recording.
Quote from: a1ex on June 09, 2013, 11:21:06 PM
Raw zebras are CPU intensive. Before you had YUV zebras with zero cpu. Just turn them off while recording.
Thanks for the clarification! Do you think it would be worthwile to make this option switchable in RAW recording mode, or are the YUV zebras too imprecise for any useful application in RAW mode? I personally found them useful to make quick changes to my exposure settings when the lighting conditions changed constantly.
EDIT: AARGH, I'm dumb, just found out how to switch to YUV Zebras... :-\
That timing slowdown commit caused err70 on 600D for evf state, esp with MZ... but was good for Digic V. DigiIV I think the raw zebras hurt more than help.
Quote from: a1ex on June 09, 2013, 10:45:19 PM
@JulianH: you said FPS override is too complex. There is a beginner mode and an advanced mode, use the one corresponding to your skill level ;)
Not saying it is too complex. I see different people using different settings though and I didn't think using something like 'low light' or having an actual fps that is lower than your desired one would make sense if you're shooting video at a certain framerate. I just couldn't confirm it. Anyway, I RTFM: http://wiki.magiclantern.fm/userguide#fps_override and it seems to do pretty much what I thought it would.
Quote from: 1% on June 09, 2013, 11:08:13 PM
Yup, that will be in.
Thanks! I'll also will donate to Julian asap. Need to recover some money after purchase.
Wow! resolution in crop mode (2000x852) is just amazing! After 600D it looks like dreams come true lol :D
Another update: when the KomputerBay 32GB card is warm, I get a constant 65.5 MB/s write speed in 5x zoom mode, allowing to shoot about 1450 frames in 1920x876 mode.
In standard 1x zoom mode, 1584x1056 at 66.9 MB/s is no problem.
So, as I thought, at this point, the limiting factor in the 50D seems not to be the CF controller, or the card, but the DMA bandwidth being left available in Live View 5x / 10x zoom mode. No matter what resolution you choose for recording, DIGIC4 always seems to write 2000x1080 pixels to SDRAM in 5x mode, which puts a heavier burden on DMA bandwidth than 1x mode in 1584x1056.
If one could alter that value to match the recording size, I think recording between 1920x872 and 1920x960 continuously might become possible with the 50D.
But, as it stands now, being able to record RAW, uncompressed video in 1920x818 on a 5 year old DSLR ist just plain amazing!
No more need for donations (to me) Viente. Everything is covered! Thanks anyway :)
I know you guys like cinemascope... Me too, but I shoot 2650x1058 ;)
Gregory's June 8th build.
Shot at 1472x1058, de-squeezed in post by 1.8x
Canon EF 50mm f/1.4 (mostly at 1.4. Bit of 2 and 2.8) + Isco Optic Ultrastar Anamorphic.
Everything at ISO 3200 1/48 - No tripod around so had to put the rig on the floor/walls etc.
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_199823.png)
The 50D + anamorphic is an awesome combo. I
love the possibility to shoot in anamorphic friendly aspect ratio's!
Quick CineForm workflow:- Convert with RAWanizer to Cineform 444 (I have the trial of Cineform premium installed...)
- Open Cineform studio, import files.
The converted iso 3200 files look pretty bad in Cineform. I didn't want to take the slow ACR/Bridge route so fiddled around a bit. Found a setting that looks pretty nice and the noise doesn't look bad. Settings:
Input lut - Protune
Output lut - R-space
Color Matrix - neutral
Thats about all the grading I did. Lowered the contrast a bit on some dark shots.
Then open the Cineform clips (without exporting them) in Premiere, edit and export...
Quote from: rockfallfilms on June 09, 2013, 03:14:51 PM
What are people using to nail exposure, raw histogram? raw zebras?
What do the numbers in the red circle mean on the histogram?
Give Auto ETTR a try . . .
I have no idea how you've gotten RAWanizer + CineForm combo to work... My results with that workflow are completely unusable.
What recent biuld you guys are hsing that seems to work so well?
I tried the june 8th build but with out succes.
Can't get the raw tab in the video menu. Even if i load magic.sys
Raw_rec.mo
Quote from: krashnik on June 09, 2013, 06:25:04 PM
I have owned a few 50Ds for a couple of years. The battery life is phenomenal and I would base all your issues on old or cheap batteries. I use Canon originals, then also 2200mAh replacements designed for CNBP511. Bought for about $11 each on Amazon a few years back & still going strong.
I have shot over 500 hours of 1080p video footage on the same batteries for my film production company where each charge lasts approximately 90 minutes per battery. With the 50D charger, this is up to 3 hours per charge using Magic Lantern. You could argue that this was HD and not RAW, but I've also used the 50D as an actual camera with over 2,000 shutter actuations per charge over the course of 5 hours on various swimsuit photoshoots.
The short: this camera is a tank & I'm glad to see so many other users finally realizing it is the hidden gem in the Canon lineup. My photos with it: OpenVase (http://openvase.com) - video with it on my Youtube (http://youtube.com/krashnik).
Thanks so much for the info. I think I either have a faulty battery, or possibly a faulty charger? Hoping not an issue with the body.
Had my new aftermarket battery (7.4v 2500mAh) on charge overnight and yet when I put it in the 50D the icon was only showing the last 3rd, and camera would not update the firmware as bat level too low.
The 2 Canon batteries although would work for 5-10 mins when they first got here now don't even hold a charge.
Have got 2 batteries on the way hoping to shed some light on the subject for me.
Is there a way to show battery % other than the top LCD screen?
Frustrating as all hell!!! :-\ Need to test more variables.
Thanks in advance for any help on this matter.
This is my first quick test with my new 50D. Using the 28May build. No problems at all, except the aliasing normal issues.
Quote from: evanamorphic on June 10, 2013, 03:01:51 AM
I have no idea how you've gotten RAWanizer + CineForm combo to work... My results with that workflow are completely unusable.
I use Cineform Studio Premium and set RAWanizer to Cineform 444 .mov
The resulting files look crap when opened in Mediaplayer Classic (VLC doesn't play them at all) but in Resolve or in Cineform Studio Premium it looks good.
With the free version and Cineform 422 I can't get it to work either. Premiere just crashes if I load the converted files.
Currently I'm on the 15 days trial of Cineform Studio Premium, I like the workflow, but not the pricetag ($299) so I hope I can get it to work with the free version for quick edits / proxies.
Hey everybody
Been following this thread as well as many others in the RAW development realm for the last couple of weeks and I feel that it is now time to finally pick up a camera to shoot with. I didn't feel like I should start a new topic and that probably you guys here could provide a few pointers.
I'm coming from a hacked GH2, which I love dearly for sharpness and fidelity but I can't really pass up the opportunity to shoot 14 bit RAW. My options right now are either a 50D or a MKII. Where I am a used MKII is 2.5 the price of a used 50D. But let's forget price for a second.
From what I've seen the two cameras seem fairly evenly matched on paper with regards to how they handle RAW video but from what I've seen the MKII footage seems to both have more resolution and higher dynamic range. I'm wondering if that is really so or if the image fidelity is simply superior? Also there seems to be quite a bit of false detail and edge sharpening in a lot of the 50D footage, is that something that feels baked into the footage or are people just dialing the sharpness too high in ACR?
Mostly I'm just wandering what people in the know are generally feeling with regards to overall quality of the RAW recording between these two cameras not counting inherent trades like sensor size and ISO performance.
Many, many thanks for all your hard work!
@krummi - I don't personally have a Mk2 but it does have a slight edge in resolution and better low light ability due to it's full frame sensor. It also doesn't have the 1.6x crop factor of APS-C cameras like the 50d. As for false detail, the DNGs are relatively soft and most footage that has been posted has IMO been over-sharpened. I think this area needs a better workflow to achieve less fringing etc. I think a hacked GH2 will still have an edge over the 50d for detail but obviously not the color depth.
The 50d is a bargain as it shoots better resolution (even when upscaled) compared to H.264. The Rebel cameras get close to H.264 resolution when upscaled but they don't look as good to my eyes and have limited shooting times because of the SD interface.
If a 5d2 is 2.5x the price I would save some money and get a 50d then start saving for a 5d Mk3. I can't see any point getting the 5d2 unless you want that sensor size and a little better low light capability.
One thing to note is that the 5d Mk2 seem to share the same CF controller so they will both max out around the same time. You can get slightly larger frame sizes on the 5d2 but shooting time for larger frame sizes will be reduced.
Hey Krummi,
Have a look at my videos (https://vimeo.com/user3681587/videos) if you haven't seen them. I usually turn sharpness off or at least turn it off in ACR and add a bit in premiere after resizing. I don't like that overprocessed/sharpened 'raw' look either.
I think the hacked GH2 will still beat the 50D on detail for 1080p landscape shots for example (I have a GH2 myself but haven't touched it since I got the 50D... should do a 1vs1 test). But detail isn't everything. I gladly trade some detail for the dynamic range, brilliant colours and all the possibilities it gives you in post. The 50D is definitely better in low light than the GH2.
The 5D II has the same problems as the 50D: moire/aliasing can be nasty in some situations. In real life I can work around it most of the times.
I'd say, keep the GH2 and get a 50D next to it. If you don't like it or if you want to upgrade to the 5D II, it shouldn't be difficult to sell the 50D. It's a very good investment right now and I think you'll love it (I absolutely do). Still it will be good to have a second camera for the times you don't want to bother with shooting process/storage heavy raw.
Here is few shots from today shooting of music video. The uncompressed footage impressed me a lot! Such a shame YouTube conversion killed it :)
Just very fast draft color correction
a night shot example... at iso 200, 400 & 800. RAWMagic + DaVinci Resolve.
Thanks so much for the replies guys! I'm leaning towards your advice to get a 50D and see if I can muster up the cash for a MKIII down the road.
To be sure, are there any good DNG sequences from relatively new build from the 50D I can download and play with?
Quote from: JulianH on June 09, 2013, 10:31:15 PM
@Evan: your actual FPS is still weird...
Did you tweak your fps timers A+B? mine are on 686 and 1751, that gives me exact 23.976.
Just trying to help...
Or am I wrong that it isn't advisable to use an actual fps lower than 23.976?
Will check the cpu usage.
Not recommended. With the 50D you will have to record audio externally and synch in post. You will have synching problems if you deviate from 23.976 (23.988) or 24.
There is a reason for 23.976. Especially if you are doing professional work for broadcast.
Hi, just dowloaded the RAW-Module for the 50D I am confronted with 1 problem: into which folder on my CF-card should I put the RAW_REC.MO? I've tried various folders but it just doesn't work... please help! Thanks in advance!
Quote from: scarimbolo on June 10, 2013, 05:07:11 PM
Hi, just dowloaded the RAW-Module for the 50D I am confronted with 1 problem: into which folder on my CF-card should I put the RAW_REC.MO? I've tried various folders but it just doesn't work... please help! Thanks in advance!
Make a folder in the ML directory and name it "MODULES". Place the following files there: magic.sym, raw_rec.mo
And also make sure you are using the Autoexec.bin from the latest build. See the post below for more info . . .
http://www.magiclantern.fm/forum/index.php?topic=5586.msg39086#msg39086 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg39086#msg39086)
Has anyone successfully gotten all the standard ISO values to work? As of now, the only ISO values that alter exposure for me are 160, 320, 640, etc. Flipping between ISO 200, 400, 800 does nothing in LiveView.
Quote from: evanamorphic on June 10, 2013, 05:54:32 PM
Has anyone successfully gotten all the standard ISO values to work? As of now, the only ISO values that alter exposure for me are 160, 320, 640, etc. Flipping between ISO 200, 400, 800 does nothing in LiveView.
Enable H264 Movie mode (!!) and force exposure override (in the first ML tab) - iso 100/200/400 etc works for me.
My first tests of 50D raw video:
Photos, I mean videos :), taken with Canon 100-400 LIS lens. I had only a Sandisk 30MB/s card, so the resolution was about 1200x600 (I tested several of them). It's nice to be able to process 14-bit dng files.
I used @GregoryOfManhatten's 28 may build. The new 8 June build is especially interesting to me for Auto-ETTR and silent pics functions.
Several questions if I may:
1. How to turn off Live view mode in raw video? Pressing live view again stops it only, turning off camera deletes all settings.
2. Is it possible for ML to remember raw video settings?
3. Was anybody able to use Auto-ETTR of the new build in photo mode? It worked for me (more less) in Live view mode only.
Quote from: JulianH on June 10, 2013, 05:58:26 PM
Enable H264 Movie mode (!!) and force exposure override (in the first ML tab) - iso 100/200/400 etc works for me.
I had them both on and it still wasn't working. But then my camera crashed, and I had to remove the battery a few times and now all the ISO settings are working again.Ok never mind, it looks like ISO 160, 320, 640, etc. are the only values that work in 5x zoom.
Quote from: akumiszcza on June 10, 2013, 06:10:53 PM
...
Several questions if I may:
1. How to turn off Live view mode in raw video? Pressing live view again stops it only, turning off camera deletes all settings.
2. Is it possible for ML to remember raw video settings?
3. Was anybody able to use Auto-ETTR of the new build in photo mode? It worked for me (more less) in Live view mode only.
1. You can switch off raw video and movie mode in the menu.
2. Not yet and not sure if it will be possible as it's a module and doesn't use the config file
3. Same as you. LV mode only. Great feature! 8)
Hey guys just a report from the field, I cant' get more than 24,5mb on my Komputarbay 600x 32gb, formated in camera.
Anything I could do to improve this? Global draw is off.
Adam
Quote from: krummi on June 10, 2013, 03:47:07 PM
Thanks so much for the replies guys! I'm leaning towards your advice to get a 50D and see if I can muster up the cash for a MKIII down the road.
To be sure, are there any good DNG sequences from relatively new build from the 50D I can download and play with?
Here's a 25 frame sequence to play with.
http://greatmindspro.com/temp/Canon50D_ML_June8build_DNGs.zip
QuoteWas anybody able to use Auto-ETTR of the new build in photo mode?
Are raw zebras and histogram working in photo mode? That's a prerequisite for photo mode ETTR.
Uh oh - known issue here but was wondering if there was a solution - shot a studio test on the 50D, fine, one of the files however is 4.26GB. Accidentally - I was usually stopping recording before I got near the 4GB max - and now can't get raw2dng to open the file. Is there any solution to that?
Seriously love the work you guys are putting into this! Gonna be shooting at a gym in LI this evening, so I'll upload a couple of clips once it's all wrapped (using the June 8th build).
Woot! 50D is here.. time to order a card. Have to order a charger though, only have the plug. AA batteries might do in the meantime.
Nice to hear 1%
By the way, where do I change to Movie mode? I still get the pink tint during 5x zoom in live view so I guess I'm in photo mode but can't find the setting in the ML menu.Sorry:
QuoteMost cameras have a dedicated movie mode on the mode dial. In this case, it's obvious what movie mode is.
However, the following cameras do not have a dedicated movie mode. For these cameras, Magic Lantern considers the following configurations as movie mode:
For Canon 5D Mark II: in LiveView, with movie recording enabled AND LiveView display set to Movie. Tip: you can change LiveView display type from Expo menu.
For Canon 50D: in LiveView, with movie recording enabled from ML menu.
Even in moviemode I still get a pink preview (June 6th build)
Just saw 1%'s comment, looked around the room and I found two 50D chargers... Forgot to put it in the box when I was packing it, aaargggh stupid! :-[ Sorry guys. Good to hear the camera arrived though.
@araucaria: there's no solution for the pink screen in zoom yet.
Quote from: 1% on June 10, 2013, 09:08:58 PM
Woot! 50D is here.. time to order a card. Have to order a charger though, only have the plug. AA batteries might do in the meantime.
YEAHHH ;D Its time for an upgrade in the 50D ML
Yea, I see tons of missing shit.
Quote from: 1% on June 10, 2013, 10:39:40 PM
Yea, I see tons of missing shit.
It's certainly a bit 'lite' compared to Tragic Lantern ;)
Apologies if this has already been answered, but.... What do I do when I get .RAW (4.28GB) and .R00 (1GB) files, neither of which I can process? Is there a save? THANK YOU
search 'merge raw' ;)
Quote from: a1ex on June 10, 2013, 07:22:07 PM
Are raw zebras and histogram working in photo mode? That's a prerequisite for photo mode ETTR.
@a1ex - Neither appear to be working in photo mode. The non raw versions still show regardless of changing settings. Maybe these changes still need porting? Also, just noticed that zebras are truncated top and bottom. Are they set up to only work on 16:9 screens?
got a new 50D today and the live view button works and (clicks) the other camera i had last week had a rock solid button.... Good call i sent it back. Just recorded Raw footage :D
Quote from: 1% on June 10, 2013, 09:08:58 PM
Woot! 50D is here.. time to order a card. Have to order a charger though, only have the plug. AA batteries might do in the meantime.
Good to hear it 1%......I also just got my 50D, in very very good shape (almost new).....so happy ;-)
Now i have to order the CF as well.....but not sure which one yet, I don`t have confidence in Komputerbay 64GB 1000x, is anyone testing a Lexar 32GB 1000x?
Quote from: hijodeibn on June 11, 2013, 12:50:18 AM
Now i have to order the CF as well.....but not sure which one yet, I don`t have confidence in Komputerbay 64GB 1000x, is anyone testing a Lexar 32GB 1000x?
I'm using a lexar 16gb 1000x works nice for me. With the may 28th build, zebra on and a lot of overlays on, i can still record at 1600 in 16:9 24 fps that hits 57mb/s
50D Infrared footage ... with a 60 mb/s SanDisk Extreme card ... notice the hick-up.
(NOTE: you must Disable Sensor Cleaning when using an IR converted camera, which won't do a Sensor Cleaning, otherwise you will get stuck at an error message)
https://vimeo.com/68076195
The mov. file says it's H.264 at 41.17 mbits/sec. How does one get RAW ?
When I click on Get Info on my mac it says color profile is (1-1-6) .... what does that mean?
Camera was converted by http://www.digitalsilverimaging.com/ir
I got the 830 nm Extreme filter placed in camera, after the IR filter was removed.
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
Quote from: GregoryOfManhattan on June 11, 2013, 02:44:28 AM
Updated build for 50D:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip
Current as of commit: 45e63064ec08
https://bitbucket.org/hudson/magic-lantern/commits/45e63064ec08598f927ac5ef8476a446381ee082
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
You don't have the state defined for photo mode... will find it. just got display filters/bootup working.
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
What resolution are you getting at 70MB/s?
Hey Everyone. Let me say I am extremely impressed by the June 5th build. My camera is stable and I have yet to have any hiccups on the 128GB Komputerbay 1000X card with this current build. I shot some stuff on the May 28th build but it was all under exposed due to the fact that i had the histograms off to conserve speed.
My process was RAWMagic>AE>ProRes444>Premiere. I shot at a 2.39 aspect ratio 24p and had the histogram and cinemascope 2.39 on. The Lenses used were a Leica R 35mm 2.8, a Pentax SMC 50mm 1.4 and a Zeitar 135mm 3.5. The last 2 shots were shot at 12,800 ISO
https://vimeo.com/68098550
I'm confused. Did you get FCP-X to see the proxy file for XML export?
I'm really interested in this exact workflow except for FCP 7.0.3.
Can you elaborate?
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
AMAZING !!!! NEW RECORD :o
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
You keep on outdoing yourself every time 70MB/s Wow!!! that's definitely running right behind the Mark III
Quote from: 1% on June 11, 2013, 03:21:00 AM
You don't have the state defined for photo mode... will find it. just got display filters/bootup working.
Glad you got your 50D in hand..
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
Gonna download now to test.. by the way the shoot went as planned used your Jun 08th Build real smooth. just got a couple files that went over the 4GB limit now have to figure out a way to get them to span.
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip)
70-73MB/s is now possible on the 50D pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
shot with this build yesterday and it ran great.
for those "upgrading" from my 28May or 08June builds,
replace your current autoexec.bin and ML/MODULES folder
if you have problems or do not get stable high bitrate recording on fast cards - go through the official 50D checklist (wish it was in the first post of this thread), start over, reformat card in computer, make bootable, reformat card in the camera. put in ML/DATA , ML/CROPMKS, ... if this isn't immediately obvious to you, please refer to the raw video how to http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
you should be able to hit stable 70MB/s video on komputerbay 1000x or lexar 1000x
tonight i tried out another workflow and it proved to be a work-slow
.raw from CF card processed by rawmagic 1.0.4 beta into cinema DNGs
opened up clips in davinci resolve - deliver individual clips proress proxy
fcpx - simple linear edit cut down to 60 seconds
export XML
reimport resolve and
... fail (it kept using the wrong clips, examined the XML files had they had the correct clips in them ... maybe some default audio setting in fcpx or ...)
build linked here works at speeds above 70MB/s
so i'm releasing it.
shoot.
Very, very nice. I'm running full 3:2 frames stable. For some reason though, the FPS just keep screwing up . . . it keeps going from 23.988 to 22fps.
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
UPDATED and amazing 70MB/s BUILD available
This is a huge achievement Gregory....well done!.......what is the max resolution you are reaching at 70MB/s?
ashtrai - for the shot in the twitter picture the resolution was 1584x892 the twitter picture is frame 756 pic.twitter.com/bENSpaArct (http://pic.twitter.com/bENSpaArct)
i'll post the DNG and a jpg below so you can confirm. the shot is actually overexposed looking east at 1742 (UTC+5) needed some ND or should have stopped down more.
goldenchild9to5 - on mac or linux use the "cat" concatenate command on windows its "copy" - check out the post processing thread http://www.magiclantern.fm/forum/index.php?topic=5654.0
djfremen - work slowdown was the XML from fcpx being loaded into davinci resolve (s.b. latest versions of everything)
rawmagic 1.0.4 beta made cinema DNGs quite quiclky
resolve can load in all the clips no problem
resolve can "Deliver" individual clips in a variety of flavors (proress proxy)
resolve 9 is not too capable an editor, so i imported the clips into fcpx
fcs2 /fcp7 may work fine for you - so give it a try.
i haven't read the various manuals for correct settings exporting from fcpx and loading into resolve.
would prefer an informative error message over have incorrect clips loaded in place of the edited ones which is what happened on import - but can't expect much when i've only glanced at shane hurlburt's post on raw files.
menoc - do you have Exact FPS or Low Light on the advanced FPS override menu?
(http://50.56.67.113/ml-09june13/000756-1.jpg)
http://50.56.67.113/ml-09june13/000756.dng (http://50.56.67.113/ml-09june13/000756.dng)
Quote from: novielo on June 11, 2013, 01:36:48 AM
I'm using a lexar 16gb 1000x works nice for me. With the may 28th build, zebra on and a lot of overlays on, i can still record at 1600 in 16:9 24 fps that hits 57mb/s
Oky...thanks!.....I am going for a Lexar too....I can not risk to get a slow card.....return will be a hell!
Quote from: GregoryOfManhattan on June 08, 2013, 11:12:00 PM
@artiswar yes, you need to
cd DIRECTORY_OR_PATH_WHERE_THE_FILES_ARE
to the directory where the files are or include the directory (or path) as part of the "cat" concatenate command.
cat /Volumes/EOS_Digital/DCIM/100CANON/M08-1601.RAW Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R01 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R02 Volumes/EOS_Digital/DCIM/100CANON/M08-1601.R03 > ~/Desktop/M08-1601-combined.RAW
I tried those Codes but didn't work.. :-\ from the link it says to rename the files should I do that the two original files are called:
M09-1640.R00 / M09-1640.RAW so I should rename the M09-1640.R00 file to M09-1640.R01 right..
you have to list all of the files in file order raw r00 r01 f02 ... (.raw followed by the available .r__ files in numerical order)
M10-000540.RAW M10-000540.R00 M10-000540.R01 M10-000540.R02
I used the following: "cat XX.RAW XX.R00 XX.R01 > MergedXX.RAW" and got a merged RAW file that RAWMagic seems to be able to handle. It does, however, have pink frames. :( This may be due to my recording raw in photo mode (doh) or a spanning/conversion problem. Think someone else mentioned it on here.
But anyway, Great work to all of you! I'm so thrilled to be able to shoot raw on this 50d!
Quote from: GregoryOfManhattan on June 11, 2013, 05:44:48 AM
you have to list all of the files in file order raw r00 r01 f02 ... (.raw followed by the available .r__ files in numerical order)
M10-000540.RAW M10-000540.R00 M10-000540.R01 M10-000540.R02
Thank you so much Gregory I successfully spanned two clip without a single Pink frame or any frame drops ;D Now it's possible to span until card is full I'm so excited right about now. You know what that means time to go get some more CF cards 8)
Quote from: pbr on June 11, 2013, 06:03:19 AM
I used the following: "cat XX.RAW XX.R00 XX.R01 > MergedXX.RAW" and got a merged RAW file that RAWMagic seems to be able to handle. It does, however, have pink frames. :( This may be due to my recording raw in photo mode (doh) or a spanning/conversion problem. Think someone else mentioned it on here.
But anyway, Great work to all of you! I'm so thrilled to be able to shoot raw on this 50d!
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.
Quote from: goldenchild9to5 on June 11, 2013, 07:59:00 AM
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.
Quote from: GregoryOfManhattan on June 11, 2013, 03:14:48 AM
...
wish it was in the first post of this thread
First post updated with latest build and added links to raw video installation threads etc.
@Gregory - I assume by
'official 50d checklist' you meant this thread: http://www.magiclantern.fm/forum/index.php?topic=5520.0 ??
Great work Gregory, I'll give your new build a go tonight.
Here's a frame from my weekend test shoot, I'm still trying to get on top of the workflow.
(https://dl.dropboxusercontent.com/u/24738031/ML/M09-1459_00000.jpg)
Thanks again to all who donated for the Camera + CF card. With your help 1% was able to order a Komputerbay 64GB 1000X CF card, charger and AC adapter. The remaining funds went towards ML for hosting costs.
This might be interesting :O
looks like the 50d has a mic base built in :O
http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg (http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg)
Quote from: Chris50d on June 11, 2013, 12:02:24 PM
This might be interesting :O
looks like the 50d has a mic base built in :O
http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg (http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg)
Maybe it's possible to weld a female jack for connect a mic ?!?!
Quote from: arrinkiiii on June 11, 2013, 12:18:42 PM
Maybe it's possible to weld a female jack for connect a mic ?!?!
No use unless a mic preamp is discovered and audio controls are in the FW
Quote from: Andy600 on June 11, 2013, 12:26:24 PM
No use unless a mic preamp is discovered and audio controls are in the FW
Maybe the preamp is already there, in the circuit board... need to send a email to planet 5d for see if its possible for them send a email to the anonymous canon work to ask him if it got.
Andy600, what is the meaning of FW (sorry for my ("dumbiness") ;D
Firmware.
Quote from: Roman on June 11, 2013, 12:47:48 PM
Firmware.
Thank you Roman.
So, even if it got a mic preamp in the circuit board its impossible to do it because of the firmware or its possible with some code in the ML ? (just for be sure if its possible or not...)
No one knows yet.
exciting times..
next discovery will be "50D has image based stabilization, only firmware disabled" :)
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
Great news!
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
8)
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
NOOOO... No way :D So its possible to weld a female jack (or something) and connect a mic?
The 50D already can handle 73MB/s maybe its possible to record to CF card or to the ssd (if the guys can pull out http://www.magiclantern.fm/forum/index.php?topic=5470.225 )
Again... AMAZING !!!
I installed Version 2.3 and the RAW-Module with the new Autoexec.bin on my 50D but it just doesn't work: as soon as I try converting the .RAW file into .DNG with the raw2dng app I only get an empty jpeg folder (that's alright) and a dng folder just with the log but without any images... I run a 32GB Transcend 60MB/s CF card.
Any idea what I'm doing wrong?
Cheers
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
With the chip ak4646 its possible to connect headphones, line in, external mic, etc... this is very good news :D
http://www.akm.com/akm/en/file/datasheet/AK4646EN.pdf
No mic or mic port tho... so unless someone opens the camera and installs those you'll be recording silence.. I'll see what happens when I put in the beep. Have to work out whether I want to do it "lite" with no audio module or just do the whole thing.. I'm running out of space in the bin. Allocatemem doesn't go down no matter which way you patch it.
What is up with zoom mode.. when lv_save_raw is turned on it has all kinds of aberrations.
Have to update hacked mode to kill LV in zoom too. Maybe that will quiet it down for recording.
Quote from: CaptainOfObvious on June 11, 2013, 09:58:24 AM
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.
I used RawMagic to span the clips, I don't think the white balance is a problem you can quickly balance a shot just make sure you have a grey card in your shot, or a piece of white paper to get close to white balance than tweak with tint.
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
Son of a B@$%@CH!!
Quote from: 1% on June 11, 2013, 03:25:26 PM
No mic or mic port tho... so unless someone opens the camera and installs those you'll be recording silence.. I'll see what happens when I put in the beep. Have to work out whether I want to do it "lite" with no audio module or just do the whole thing.. I'm running out of space in the bin. Allocatemem doesn't go down no matter which way you patch it.
What is up with zoom mode.. when lv_save_raw is turned on it has all kinds of aberrations.
Have to update hacked mode to kill LV in zoom too. Maybe that will quiet it down for recording.
I dont mind to open a 50D and weld some cables. Do you think that i need to weld to the /board/chip or the camera got some kind of jumpers that i can connect? I already check the ak4646 chip and already know here is the external mic, headphones, etc... in the chip.
(I Am a owner of a 7D, not yet get enough money for a 50D :-[ but for you guys see how i follow this religiously i even make a nonation for the 50D ...and im happy with that. I believe in this !!!
IN ML WE TRUST :D
Quote from: 1% on June 11, 2013, 03:25:26 PM
No mic or mic port tho... so unless someone opens the camera and installs those you'll be recording silence.. I'll see what happens when I put in the beep. Have to work out whether I want to do it "lite" with no audio module or just do the whole thing.. I'm running out of space in the bin. Allocatemem doesn't go down no matter which way you patch it.
What is up with zoom mode.. when lv_save_raw is turned on it has all kinds of aberrations.
Have to update hacked mode to kill LV in zoom too. Maybe that will quiet it down for recording.
Great findings 1% 50D is the "ONE" 8)
Quote from: JulianH on June 11, 2013, 11:45:46 AM
Thanks again to all who donated for the Camera + CF card. With your help 1% was able to order a Komputerbay 64GB 1000X CF card, charger and AC adapter. The remaining funds went towards ML for hosting costs.
Nice.. Great Job 50D community we made it happen..
Basically the 50D is a 5D Mark II with a smaller sensor . . .
No wonder this damn camera cost so much more than the T2i which had video and audio . .
Aren't the flex cable connectors there for the mic... Or is the whole area unpopulated (just pads).
The 50D is taking on Godzila scales. Canon is so freaken lucky to have made this little monster. Otherwise we'd all have BMCCs . . .
1% . . . I will wait patiently for your discovery of 720P 60fps. . . . even if it's H.264...
Quote from: CaptainOfObvious on June 11, 2013, 09:58:24 AM
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.
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.
Quote from: menoc on June 11, 2013, 04:05:49 PM
The 50D is taking on Godzila scales. Canon is so freaken lucky to have made this little monster. Otherwise we'd all have BMCCs . . .
Indeed ;D
Quote from: goldenchild9to5 on June 11, 2013, 04:17:44 PM
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.
My workflow is with RawMagic and Resolve. For some reason the clips have a green tint when I open them in Resolve, but when I open them in ACR they're fine.
Have you guys encountered this?
Quote from: menoc on June 11, 2013, 04:45:02 PM
My workflow is with RawMagic and Resolve. For some reason the clips have a green tint when I open them in Resolve, but when I open them in ACR they're fine.
Have you guys encountered this?
Yep they have a very Greenish tint to them, you right in ACR no problem it actually gives the correct White Balance.
Quote from: menoc on June 11, 2013, 04:45:02 PM
My workflow is with RawMagic and Resolve. For some reason the clips have a green tint when I open them in Resolve, but when I open them in ACR they're fine.
Have you guys encountered this?
I found the same thing so at the moment I'm sticking to ACR. I find the raw controls in Resolve pretty limiting anyway, I can get a much better result in ACR and it deals with moire better.
dear community,
my simple workflow till now was: shooting; raw2dng; after effects -> import -> import as camera raw sequence.
but now after effects says: "after effects error: photoshop file format error (-30504)"
has anyone experienced the same or knows what that means?
may the raw clips on the cf card be destroyed in any way because i shot until the card's capacity maximum?
i didn't changed the workflow and i can open clips i shot before my last session this night.
thank you in advance
Have you tried to open one of the pictures in Photoshop? Or tried to open picture two or later of the sequence?
Quote from: Ifani on June 11, 2013, 05:24:30 PM
dear community,
my simple workflow till now was: shooting; raw2dng; after effects -> import -> import as camera raw sequence.
but now after effects says: "after effects error: photoshop file format error (-30504)"
has anyone experienced the same or knows what that means?
may the raw clips on the cf card be destroyed in any way because i shot until the card's capacity maximum?
i didn't changed the workflow and i can open clips i shot before my last session this night.
thank you in advance
Not sure what's going on but it seems like those files are corrupted. I filled up my card before and the files were fine try and convert them with RawMagic if you using a Mac and see if you get the same results. If you do get the same results than your files are definitely corrupt.
Quote from: goldenchild9to5 on June 11, 2013, 06:00:16 PM
Not sure what's going on but it seems like those files are corrupted. I filled up my card before and the files were fine try and convert them with RawMagic if you using a Mac and see if you get the same results. If you do get the same results than your files are definitely corrupt.
@ breaker:
yes i tried. neither it opens in ae nor random dng's of different sequences cant be opened in ps.
a message pops up, that "the process can't be accomplished because the file apparently comes from a camera model which isn't supported by the installed version of camera raw".
yesterday everything worked fine.
@ goldenchild:
regrettably i dont work on mac and can't use rawmagic. but does anyone of you know an alternative to raw2dng for windows?
i'm not sure if the files are corrupted because i made a new test earlier and formated the card (except ML). the error is still present.
it is a pitty to invest a night in shooting instead of sleeping and not being able to see results :)
P.S. but every beginning is hard;)
thank you for the fast responses
Just tested the June 11th update with my KomputerBay 32GB card.
In 5x Zoom mode, 50D maxes now out at 67.7 MB/s.
On the other hand, 2.20:1 aspect ratio in full HD (1920x872) has now become possible with the 50D. Very nice! :)
Quote from: menoc on June 11, 2013, 04:05:49 PM
The 50D is taking on Godzila scales. Canon is so freaken lucky to have made this little monster. Otherwise we'd all have BMCCs . . .
I have to admit that the
BMCC still has some serious advantages over the 50D (2.5k, SSD, Audio).
However, I see very little to no reason now, if you want to shoot RAW on a low budget, to buy the
BMPCC. Even less every step we get closer to Full HD.
Quote from: Ifani on June 11, 2013, 06:29:43 PM
@ breaker:
yes i tried. neither it opens in ae nor random dng's of different sequences cant be opened in ps.
a message pops up, that "the process can't be accomplished because the file apparently comes from a camera model which isn't supported by the installed version of camera raw".
yesterday everything worked fine.
@ goldenchild:
regrettably i dont work on mac and can't use rawmagic. but does anyone of you know an alternative to raw2dng for windows?
i'm not sure if the files are corrupted because i made a new test earlier and formated the card (except ML). the error is still present.
it is a pitty to invest a night in shooting instead of sleeping and not being able to see results :)
P.S. but every beginning is hard;)
thank you for the fast responses
Man I feel you spending a whole night shooting and not able to see none of the footage is crazy.. Here is what you do send me your smallest .RAW file I means smallest use this site to upload www.soshareit.com (http://www.soshareit.com) I'll check it out for you..
Quote from: necronomfive on June 11, 2013, 06:38:21 PM
Just tested the June 11th update with my KomputerBay 32GB card.
In 5x Zoom mode, 50D maxes now out at 67.7 MB/s.
On the other hand, 2.20:1 aspect ratio in full HD (1920x872) has now become possible with the 50D. Very nice! :)
Are you serious 1920x872 before it was 1584x720 that's great news is it stable? Where did you find that build because @GregoryOfManhattan only posted the one from June 9th please send direct link wanna give it a run.. I love that aspect ratio.
Quote from: necronomfive on June 11, 2013, 06:41:45 PM
I have to admit that the BMCC still has some serious advantages over the 50D (2.5k, SSD, Audio).
However, I see very little to no reason now, if you want to shoot RAW on a low budget, to buy the BMPCC. Even less every step we get closer to Full HD.
I think the Pocket Cinema Camera is a better companion to the 50D. The BMCC is an incredible camera would still want to own one but M/43 version so I can fit a multitude of lens on there..
Quote from: menoc on June 11, 2013, 04:05:49 PM
Canon is so freaken lucky to have made this little monster.
Why do you think Canon's lucky? Canon doesn't earn any money if you buy a used 50D on eBay ;)
Instead, I guess they are pretty despaired since there's almost no reason left to buy a camera of their C-line ;D
If you have the cash, either get a 5D Mark III or a Blackmagic Production Camera 4K. Why should you buy a C-camcorder?
But it's nice to see how much progress has been made. And now 1% has a 50D too ...
I don't know. Hopefully Canon releases the 70D soon and gives it a CF card slot and the same aliasing reduction like the 5D Mark III ...
Ifani and others -
there were brief and slight changes to the .raw file format over the weekend.
if you are using a newer build after 08June13 - you may need to update to the latest raw2dng based tools.
not sure about the converse situation of older .raw with latest raw2dng based tools.
if you have essential footage of a red wedding, you may need to carefully specify the versions of everything you are using - it you want help in recovering the event
also, for now do not mix and match raw_rec.mo from one build with an autoexec.bin and MAGIC.SYM from a different build (ultimately modules are intended to be modular, but there are many subtle ongoing changes)
Quote from: goldenchild9to5 on June 11, 2013, 04:17:44 PM
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. -_-
Double post.
Quick low light test on the way home tonight.
6400 ISO, 15mm f4...
Real cinema beast :)
Quote from: goldenchild9to5 on June 11, 2013, 06:53:36 PM
Are you serious 1920x872 before it was 1584x720 that's great news is it stable? Where did you find that build because @GregoryOfManhattan only posted the one from June 9th please send direct link wanna give it a run.. I love that aspect ratio.
With June 9th build, I could "only" do 1920x818 (2.35:1). 1920x872 is with the current June 11th build. In 1x mode, I could easily do 1582x1056 with all builds so far.
Just grab it on the first page of this thread. ;)
Quote from: Chris50d on June 11, 2013, 12:02:24 PM
This might be interesting :O
looks like the 50d has a mic base built in :O
http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg (http://www.cinema5d.com/wp-content/uploads/2013/06/low.jpg)
hello here
i have a 50d myself for a month now :) and may camera has not the place for the mic. so i think i could be an earlier version...
https://www.dropbox.com/s/f7pxzvrhzcacm84/2013-06-11%2020.01.45.jpg
by the way, great work you do here, and especially to Julian who simply bought the 50d on his cost an sent it to 1% and then asked for donation
really great community, and i will help as good as i can and have time (which is not much right now)
@ Ifani, can you playback the files on camera from Raw video Q-menu or in the file browser?
Quote from: necronomfive on June 11, 2013, 08:10:49 PM
With June 9th build, I could "only" do 1920x818 (2.35:1). 1920x872 is with the current June 11th build. In 1x mode, I could easily do 1582x1056 with all builds so far.
Just grab it on the first page of this thread. ;)
is 1920x818 (2.35:1) also in 1X mode? You mean 1:1 mode right..
Quote from: goldenchild9to5 on June 11, 2013, 08:31:07 PM
is 1920x818 (2.35:1) also in 1X mode? You mean 1:1 mode right..
1920x818 in 5x zoom (aka 1:1) mode, full sensor area (1584x1056) in 1x zoom, (3:1) mode.
Awesome speed with Gregory's new build. I'm getting around 69mb/s at 25fps 1584x892!
Global draw on with just raw histogram.
Thanks Gregory
Quote from: necronomfive on June 11, 2013, 08:43:04 PM
1920x818 in 5x zoom (aka 1:1) mode, full sensor area (1584x1056) in 1x zoom, (3:1) mode.
I think my early first dream could become a reality.......is it possible to get 2K in 5x zoom?
Finally the quality of lenses matters! Going to choose the best wide lenses possible to be able to shoot in 5x mode...
Hey guys. I'm still struggeling to achieve acceptable speeds in raw Video mode. My Benchmarks dont differ that much from the Komputerbay cards but I'm just achieving ~50 MB/s in video mode. I changed all my settings to the recommended. What am I doing wrong? Im using a Transcend 16GB 1000X Card
(https://photos-3.dropbox.com/t/0/AACbSXN-HDCAK3lvt6vOXNvJFeGfnLFK8_DskiTqAry2qA/12/2427776/jpeg/32x32/3/_/1/2/IMG-20130611-WA0006.jpg/F5Zlmwzhx3MjtsZZekuhwxDnuOF4T5VSj11ZIsIqXW8?size=1600x1200)
Hey Guys I did some tests today with the 8 of June build, I am getting magenta pictures out, I am using rawnizer 5.3
Is there a setting to set somewhere to lock black point or is this issue caused by a old build of raw2dng?
(https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-frc1/p160x160/995324_10151666222549617_721237343_n.jpg)
update: my new card reader reads the komputerbay card just fine on my MBP. sorry for the delay with the update but i've been in the field shooting.
Quote from: eattheblinds on June 06, 2013, 05:48:23 PM
regarding issues i'm having getting my komputerbay card to read on my mac:
Komputerbay Tech Support
4:15 AM (4 hours ago)
to me
Hello,
The card is possibly corrupted.
From what we know the 50D is limited to FAT32 but your Mac is not. (your Mac possibly tried to read the card as exFAT instead of FAT32 seeing that it is a 64GB card - lot of customers have done this.)
It can be uncorrupted using a PC using SD Formatter's free software to format the cards. The Mac version has some bugs and as such we donot recommend it.
Also - we do not know if the bower USB2.0 CF Reader #CRCF is compatibnle with UDMA 7 cards.
Have you tried any formatting apps on your Mac?
Thank You
Tech Support
CS
Quote from: dacssfreak on June 11, 2013, 09:11:43 PM
Hey guys. I'm still struggeling to achieve acceptable speeds in raw Video mode. My Benchmarks dont differ that much from the Komputerbay cards but I'm just achieving ~50 MB/s in video mode. I changed all my settings to the recommended. What am I doing wrong? Im using a Transcend 16GB 1000X Card
(https://photos-3.dropbox.com/t/0/AACbSXN-HDCAK3lvt6vOXNvJFeGfnLFK8_DskiTqAry2qA/12/2427776/jpeg/32x32/3/_/1/2/IMG-20130611-WA0006.jpg/F5Zlmwzhx3MjtsZZekuhwxDnuOF4T5VSj11ZIsIqXW8?size=1600x1200)
Still having problems with that card.. it has to be something simple. What version of Gregory's build are you using currently? are you using window's or mac?
Quote from: goldenchild9to5 on June 11, 2013, 09:29:49 PM
Still having problems with that card.. it has to be something simple. What version of Gregory's build are you using currently? are you using window's or mac?
Im using a Windows PC and the 70 MB/s build of Gregory.
Quote from: dacssfreak on June 11, 2013, 09:32:19 PM
Im using a Windows PC and the 70 MB/s build of Gregory.
Are you formating the card in camera?
Quote from: dacssfreak on June 11, 2013, 09:11:43 PM
Hey guys. I'm still struggeling to achieve acceptable speeds in raw Video mode. My Benchmarks dont differ that much from the Komputerbay cards but I'm just achieving ~50 MB/s in video mode. I changed all my settings to the recommended. What am I doing wrong? Im using a Transcend 16GB 1000X Card
(https://photos-3.dropbox.com/t/0/AACbSXN-HDCAK3lvt6vOXNvJFeGfnLFK8_DskiTqAry2qA/12/2427776/jpeg/32x32/3/_/1/2/IMG-20130611-WA0006.jpg/F5Zlmwzhx3MjtsZZekuhwxDnuOF4T5VSj11ZIsIqXW8?size=1600x1200)
Sorry to be the bearer of bad news but the Transcend 1000x 16gb card is actually slow. The 600x version beats it for write speed by 20-30MB/s. The 1000x Transcend cards only becomes 'fast' when you use the 32GB or 64GB. Check out the specs and compare the cards on the Transcend site and you'll see what I mean. :(
Quote from: dacssfreak on June 11, 2013, 09:11:43 PM
Hey guys. I'm still struggeling to achieve acceptable speeds in raw Video mode. My Benchmarks dont differ that much from the Komputerbay cards but I'm just achieving ~50 MB/s in video mode. I changed all my settings to the recommended. What am I doing wrong? Im using a Transcend 16GB 1000X Card
hi dacssfreak,
i got the same card a few days ago and have the same problems.
read in this forum, the 16gb 1000x is actually as slow as the 600x one.
maybe the 32gb and up are better.
(yes, same info like andy600, have been too slow)
here is a benchmarktest for those who are interested:
http://postimg.org/image/sigpsl59b/ (http://postimg.org/image/sigpsl59b/)
(global draw: just histogram)
@goldenchil9to5
thank you very much for the help, how could i send you a file?
on justshareit you need a email adress.
i will try to reinstall ml with the right .bin's
Did you even look at the picture of my benchmark? My numbers are double of what you posted Ifani. Menoc postet a picture of his Komputerbay 64 GB 1000x card, and the numbers in the screenshot are the same.
Quote from: Andy600 on June 11, 2013, 09:40:36 PM
Sorry to be the bearer of bad news but the Transcend 1000x 16gb card is actually slow. The 600x version beats it for write speed by 20-30MB/s. The 1000x Transcend cards only becomes 'fast' when you use the 32GB or 64GB. Check out the specs and compare the cards on the Transcend site and you'll see what I mean. :(
What about Silicon Power 1000x? Where can i find benchamrks? Thnx
Quote from: dacssfreak on June 11, 2013, 09:50:49 PM
Did you even look at the picture of my benchmark? My numbers are double of what you posted Ifani. Menoc postet a picture of his Komputerbay 64 GB 1000x card, and the numbers in the screenshot are the same.
i couldn't see your benchmark test.
it seams to be private.
and you said something like you get 50mb/s in video mode, how can your write speed of the transcend 16gb 1000x be twice as high as mine?
Try this one http://pl.vg/2dpya (http://pl.vg/2dpya)
@Ifani the 1000x isn't 'as slow as the 600x' it's actually slower
@Viente - Hey man, you got the 50d now? 8) As for the Silicon Power CF's I have no idea but from my research you need to buy 32GB and up if you're getting a 1000x speed card (although 128GB cards can be slow as is the case with the Komputerbay cards). 16GB 600x speed cards are generally faster than 1000x 16GB cards but they are not all the same. I had a Kingston 600x and it was a lot slower than my Transcend 16GB 600x. I checked both cards for alignment and both were ok but later discovered that the Kingston isn't using DMA (apparently) which would explain things.
Here are some benchmarks for (upto) 600x cards I found: http://en.gomemory.net/index.php?page=cf
The June 9th build works amazingly well for me. THANK YOU! :) Consistant, stable recording at 67 MB/s (KomputerBay 1000x 64). I still have the issue when I zoom in, I get a pink frame. Any fixes for that?
And also: I shoot with an anamorphic lens and in the past I've used the Anamorphic Preview setting - http://www.magiclantern.fm/forum/index.php?topic=3323.0 - Does anyone know if/how I can combine the anamorphic preview setting with Raw recording?
Quote from: Andy600 on June 11, 2013, 10:17:09 PM
@Ifani the 1000x isn't 'as slow as the 600x' it's actually slower
@Viente - Hey man, you got the 50d now? 8) As for the Silicon Power CF's I have no idea but from my research you need to buy 32GB and up if you're getting a 1000x speed card (although 128GB cards can be slow as is the case with the Komputerbay cards). 16GB 600x speed cards are generally faster than 1000x 16GB cards but they are not all the same. I had a Kingston 600x and it was a lot slower than my Transcend 16GB 600x. I checked both cards for alignment and both were ok but later discovered that the Kingston isn't using DMA (apparently) which would explain things.
Here are some benchmarks for (upto) 600x cards I found: http://en.gomemory.net/index.php?page=cf
@Andy- any benchmark available for Lexar cards?
@hijodeibn do a search on this forum. There are plenty of benchmarks for Lexar, Sandisk, Komputerbay etc. Also check out the card benchmark thread that @a1ex posted. It has graphs ;)
Hey Andy, if you take a look at how my Transcend 16GB 1000x performed at the ML benchmark, I doubt that the 16GB is actually slower. Take a look at that http://pl.vg/2dpya (http://pl.vg/2dpya)
Quote from: dacssfreak on June 11, 2013, 10:14:46 PM
Try this one http://pl.vg/2dpya (http://pl.vg/2dpya)
thank you,
quite strange that mine had so low accounts.
i will try to format the card
Quote from: dacssfreak on June 11, 2013, 10:43:43 PM
Hey Andy, if you take a look at how my Transcend 16GB 1000x performed at the ML benchmark, I doubt that the 16GB is actually slower. Take a look at that http://pl.vg/2dpya (http://pl.vg/2dpya)
It looks pretty close to my 600x benchmark so you should be hitting 60-65MB/s
I was going by the comparisons on the manufacturer's website :http://uk.transcend-info.com/Products/compare.asp?ck=406|252
1000x Write 70 MByte/s (16GB) / Write 120 MByte/s (32~128GB)
600x Write 90 MByte/s (16~64GB)
Read speeds will of course be higher on 1000x cards.
Have you tried a benchmark in movie mode with LV and raw video enabled? Speeds will be less but more accurate of achievable raw video performance.
Also, have you tried Gregory's new upload? https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (I'm getting slower benchmarks with this build for some reason and my batteries just died so I need to charge before trying it again)
Quote from: hijodeibn on June 11, 2013, 10:32:13 PM
@Andy- any benchmark available for Lexar cards?
Lexar Profesional 32GB 600x. Stable @1600/16:9 with the June 9th build:
(http://i.imgbox.com/abjPxylC.jpg)
Quote from: Andy600 on June 11, 2013, 10:58:29 PM
Have you tried a benchmark in movie mode with LV and raw video enabled? Speeds will be less but more accurate of achievable raw video performance.
Also, have you tried Gregory's new upload? https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (I'm getting slower benchmarks with this build for some reason and my batteries just died so I need to charge before trying it again)
In LV with raw video enabled the camera stalls while benchmarking. I have no idea why it performs so weird.
Quote from: dacssfreak on June 11, 2013, 11:09:14 PM
In LV with raw video enabled the camera stalls while benchmarking. I have no idea why it performs so weird.
Yes, I'm getting that happen to ???
BTW here is a benchmark I pulled off just before my batteries died using Gregory's very latest build (uploaded today).
Transcend 600x UDMA7 16GB
(http://i.imgbox.com/abmd5piA.jpg)
Quote from: menoc on June 11, 2013, 11:02:57 PM
Lexar Profesional 32GB 600x. Stable @1600/16:9 with the June 9th build:
Thanks menoc!......I just bought a Lexar 32GB 1000x which I should receive tomorrow......hope it will perform at least as you showed.
@ breaker & goldenchild9to5
i reinstalled ML (vers. 9th of june) and downloaded the latest raw2dng.exe
(https://bitbucket.org/hudson/magic-lantern/downloads)
and gave it an other try.
luckily it worked but i don't know why:)
thank you for your help.
Wow - I am getting 70mb with latest build!! Thanks to all.
Someone showed me there is a useful filter in Photoshop CS5 for DNG conversion in the sharpness tab (noise reduction - colour /luminance http://www.youtube.com/watch?v=xh1X7MTvWyM )
Thanks again!
It was sunny at the weekend so I went and shot something. Sorry it's shaky, didn't have my shoulder rig or tripod.
- Using GregoryofManhattan's 8th June build
- Shot at 1584x892 and upscaled to 1080
- DNG's extracted with RAWMagic 1.0 Beta 4
- Raw processing in ACR
- A bit of sharpening in Resolve
- Tamron 17-50mm f2.8
Sorry for OT but is it necessary to upscale 1584x892 to 1920x1080 for Vimeo if you don't have Pro account. I guess it will downscale to 720p back...
Quote from: Andy600 on June 11, 2013, 10:17:09 PM
@Ifani the 1000x isn't 'as slow as the 600x' it's actually slower
@Viente - Hey man, you got the 50d now? 8) As for the Silicon Power CF's I have no idea but from my research you need to buy 32GB and up if you're getting a 1000x speed card (although 128GB cards can be slow as is the case with the Komputerbay cards). 16GB 600x speed cards are generally faster than 1000x 16GB cards but they are not all the same. I had a Kingston 600x and it was a lot slower than my Transcend 16GB 600x. I checked both cards for alignment and both were ok but later discovered that the Kingston isn't using DMA (apparently) which would explain things.
Here are some benchmarks for (upto) 600x cards I found: http://en.gomemory.net/index.php?page=cf
Yeah couldn't resist :) Found a very hard used body with a lot of scratches and scars, but very cheap (about 300 USD). I called Canon and they can replace the case for about 150 USD which is not bad.
Not so many options to buy fast CF cards in local stores without pre ordering. I'll try that Silicon Power and post my results tomorrow.
@Viente - Nice deal! Got the same problem here regarding CF cards. Very limited selection of fast ones locally. I'm interested to know how the Silicon Power cards perform because I can get them here quite cheap. Sandisk/Lexar are almost double the cost of US prices :(
Quote from: Viente on June 12, 2013, 12:52:39 AM
Sorry for OT but is it necessary to upscale 1584x892 to 1920x1080 for Vimeo if you don't have Pro account. I guess it will downscale to 720p back...
I finished in 1080p to test the workflow for future projects. Vimeo will just scale it.
With the new 09 june build: 285 frames at 25p size 1584 with my 60MB/s Sandisk Extreme. Very happy
GregoryOfManhatann, Thank you very much!
edit: now i get 200 frames, not so bad :)
Well after testing the latest build i found one interesting thing... when i enable h264 movie mode, before shooting raw footage i get 50mb/s speed. if i disable movie mode i get 45-46 mb/s..humm interesting..
another interesting fact was that my digic 4 got so hot like 48deg that i think that fogged the back of my 24.70 l lens -.-'
could this be possible? i mean like the lens is weather sealed and this didn't happened before...
Quote from: Ifani on June 12, 2013, 12:20:44 AM
i reinstalled ML (vers. 9th of june) and downloaded the latest raw2dng.exe
(https://bitbucket.org/hudson/magic-lantern/downloads)
and gave it an other try.
luckily it worked but i don't know why:)
I also got the same problem of "camera model isn't supported by the installed version of camera raw" on DNGs from some RAW files, after I install the newest build. Perhaps, I need to reinstall the whole thing again to keep use RAW2DNG. Luckily, RAWMagic saved those problematic RAW file with ease. I think I will stick to RAWMagic from now on, because it gave me easier previews of CinemaDNGs than photo-DNGs from RAW2DNG.
Here are some results of SUPER MACRO clips of MP-E 65mm 1-5x macro lens combined with 5x crop mode about plankton in my nano fishtank. Fish and shrimp shots are h264, which are dramatically softer than the raw clips. But H264 are quick and dirty, working fine together with the raw sequences, although with noticeable differences.
With up to 15x macro capability, I just realised how many protists can live on a tiny stone :o . Big Diotam can be easily spotted when a baby snail is grazing on them.
And also! Timelapse haven't been this easy to simply use 2-12fps at 1920x1080 to reveal the slow movements of protists. Big thanks to this wonderful community and developers! ;D
Quote from: Viente on June 12, 2013, 12:58:20 AM
Yeah couldn't resist :) Found a very hard used body with a lot of scratches and scars, but very cheap (about 300 USD). I called Canon and they can replace the case for about 150 USD which is not bad.
Not so many options to buy fast CF cards in local stores without pre ordering. I'll try that Silicon Power and post my results tomorrow.
Just read your post! Stay away from Silicon Power! I got a 32GB 600X, only gave me 37m/s, very sad! And I just got KomputerBay from US Fedex (7days to AU), 67m/s stable, so easy!
Quote from: AndyNCode on June 12, 2013, 06:37:48 AM
I also got the same problem of "camera model isn't supported by the installed version of camera raw" on DNGs from some RAW files, after I install the newest build. Perhaps, I need to reinstall the whole thing again to keep use RAW2DNG. Luckily, RAWMagic saved those problematic RAW file with ease. I think I will stick to RAWMagic from now on, because it gave me easier previews of CinemaDNGs than photo-DNGs from RAW2DNG.
Here are some results of SUPER MACRO clips of MP-E 65mm 1-5x macro lens combined with 5x crop mode about plankton in my nano fishtank. Fish and shrimp shots are h264, which are dramatically softer than the raw clips. But H264 are quick and dirty, working fine together with the raw sequences, although with noticeable differences.
With up to 15x macro capability, I just realised how many protists can live on a tiny stone :o . Big Diotam can be easily spotted when a baby snail is grazing on them.
And also! Timelapse haven't been this easy to simply use 2-12fps at 1920x1080 to reveal the slow movements of protists. Big thanks to this wonderful community and developers! ;D
Hi Andy,
This video is incredible!! It really is fantastic.
Which build did you use as I can't get that resolution on my build? Can i do this on the 5d as reduced frame rate May allow theis resolution. How did you set up lights and did you put your lens up against the glass of the tank.
I am hoping to make a tank of pond life and film similar animals for a kids show.
Thanks
D
Quote from: Dunc101 on June 12, 2013, 04:02:52 PM
Hi Andy,
This video is incredible!! It really is fantastic.
Which build did you use as I can't get that resolution on my build? Can i do this on the 5d as reduced frame rate May allow theis resolution. How did you set up lights and did you put your lens up against the glass of the tank.
I am hoping to make a tank of pond life and film similar animals for a kids show.
Thanks
D
Glad you like it! I'm using 9th June build but with a slow 600x card which only give me 37mb (just receive komputerbay today that give me 67mb). Anyway I shot the most microscopic clip with 2-4fps at 1920x1080 crop mode, partially because of my slow card, but also because I need timelapse.
5D definitely can do it, I guess you can get 15-20fps at 1920x1080 (both crop mode or 1x nearly 1080p mode) with a fast card.
I used 20+ led arrays as a diffused light and a led torch on the side as the shadow light to darken the background. The lens I am using it's the beast macro MP-E 1-5x, thats why it's interesting to try even higher power of magnification by crop mode to get microscopic video, meanwhile, still give me several centimeters to work with away from the glass. Normal 100mm macro lens will do it on relatively larger plankton with even more working distance.
I'm quite interested in your pond life film. Hope to follow up your progress in future.
Cheers,
Andy
Is there any way to have slow framerates without rising exposure compared to normal framerates? (and without having to use an ND filter)
Dont think so, apart from apeture or ND filters.
Situation might get a little better if someone fishes around and finds a native 24fps mode to reduce fps from rather than 30.
With june 09 build in a 60 MB/s card, -memory hack off- i am getting more frames, 300, even with raw histograma on. Raw zebras uses lots of memory, only get 100 frames , -1584 resolution--
Hey guys, could anyone remind me where did we talked about this? The thread is huge to go through to find something about this unusual writing speed. I sort of remember someone mentioned this before.
(http://farm6.staticflickr.com/5332/9027636492_8f5f0603ca_o.jpg)
70mb build, Komputerbay 64GB 1000X crop mode 1920x1080 2fps (that's why it does't make sense)
Otherwise the card stabilised at around 68mb/s
Wait a minute, you aren't getting any idle time at all?!
Quote from: a1ex on June 12, 2013, 08:22:25 PM
Wait a minute, you aren't getting any idle time at all?!
Yes, I will get it seconds later. 89-91% idle. Speed varies at 75-80mb/s. Sorry for the dummy question, I don't really know what idle is...
posting a build with the latest code if anyone has time to try and report back confirming that Idle time shows up.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/12june13-50D-8823d8ad10ef.zip
don't have time to test it myself now.
thank you.
In this context, idle means it's not writing to the card. So, 10% of time is writing at ~80MB/s, 90% of time is just waiting for buffers to fill.
When idle time becomes 0, the buffer will slowly fill up and recording will stop eventually.
If there's a tiny bit of idle time, it's likely that recording will not stop (continuous recording). With this hint, you know how far you can go (this is used by ML to predict how much you will record at current settings).
Quote from: GregoryOfManhattan on June 12, 2013, 08:44:51 PM
posting a build with the latest code if anyone has time to try and report back confirming that Idle time shows up.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/12june13-50D-8823d8ad10ef.zip
don't have time to test it myself now.
thank you.
Just checked, it works.
Noticed that sometimes it displays idle time in ms and then in %. The milliseconds showed up when I was recording at the card limit I think, after a while it changed to 1% (and then stopped recording shortly after).
Build seems fast. Squeezed out more than 4GB on 1584x950 with my card (limits around 60MB/s) never got that far I think.
Hopefully get my Komputerbay 64GB tomorrow :)
Quote from: GregoryOfManhattan on June 12, 2013, 08:44:51 PM
posting a build with the latest code if anyone has time to try and report back confirming that Idle time shows up.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/12june13-50D-8823d8ad10ef.zip
don't have time to test it myself now.
thank you.
Working for me, 68mb/s, 10% idle
Komputerbay 64gb 1000x
Yeah, instead of 0% it prints milliseconds.
With 68MB/s and 10% idle, you can push it to around 75, no?
Sorry if someone already posted this. This is from the CinemaDNG discussion thread.
User chmee created the tool raw2cdng which will convert ML raw video to 16 or 12bit CinemaDNG files. These files are compatible with Davinci Resolve!!! 8)
Link to thread here http://www.magiclantern.fm/forum/index.php?topic=5618.100 (http://www.magiclantern.fm/forum/index.php?topic=5618.100)
Link to his download page here http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/ (http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/)
Just wanted to share a recent video I made.
The last two shots were examples of how much you can push the footage. :D
Quote from: a1ex on June 12, 2013, 09:05:52 PM
Yeah, instead of 0% it prints milliseconds.
With 68MB/s and 10% idle, you can push it to around 75, no?
Can't seem to get it to go past 68mb/s
Which mode and res should i be testing in?
Quote from: GregoryOfManhattan on June 12, 2013, 08:44:51 PM
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/12june13-50D-8823d8ad10ef.zip
I have a lot of problems with the Auto ETTR in this build. Since Recording has been moved to Set button I have choosen Shutter Doubleclick, but it's not always working. The result is also most of the time wrong. On the build from 08june13 it was great - also with Shutter Doubleclick selected!
Just for info; I'm waiting for a Toshiba 64 GB 1066X which hopefully will arrive this weekend. I will post my benchmark then. Now i'm just playing with a Kingston 266X...
Rockfallfilms: Try 1920x960 in 5x zoomed mode. It needs 73.7MB/s. Or 2000x910 at 72.8MB/s.
Quote from: JulianH on June 12, 2013, 10:25:07 PM
Rockfallfilms: Try 1920x960 in 5x zoomed mode. It needs 73.7MB/s. Or 2000x910 at 72.8MB/s.
All of a sudden I'm only getting 40mb/s in any mode i try. Card must need a format.
Ok, it's picked back up again but only to 65mb/s in the resolutions above, recording stops pretty quickly.
So I'm getting my Komputerbay 64gb Card tomorrow. Could someone list the steps I should take to test out my card, such as proper way to format/ benchmark/ etc? I want to make sure the card is fast enough so I don't have to RMA it.
How is everyone working out the framing in crop mode? I just had a play about with it but it's hard to know what's in frame.
DaVinci seems to be the best workflow. @BoKia - You can pull more out if you open RAWMagic processed CDNGs in DaVinci and set the clip setting to BMD film. See below.
(http://imageshack.us/a/img22/847/screenshot20130612at432.png) (http://imageshack.us/photo/my-images/22/screenshot20130612at432.png/)
Uploaded with ImageShack.us (http://imageshack.us)
(http://imageshack.us/a/img59/4386/screenshot20130612at430.png) (http://imageshack.us/photo/my-images/59/screenshot20130612at430.png/)
Uploaded with ImageShack.us (http://imageshack.us)
(http://imageshack.us/a/img843/4386/screenshot20130612at430.png) (http://imageshack.us/photo/my-images/843/screenshot20130612at430.png/)
Uploaded with ImageShack.us (http://imageshack.us)
(http://imageshack.us/a/img833/4386/screenshot20130612at430.png) (http://imageshack.us/photo/my-images/833/screenshot20130612at430.png/)
Uploaded with ImageShack.us (http://imageshack.us)
Quote from: a1ex on June 12, 2013, 08:22:25 PM
Wait a minute, you aren't getting any idle time at all?!
Hey Alex here my idle time mine reports at 1600/16:9. I ran a test to see the consistency of writing to the card. Basically I emptied the card. Then , from a completely cool down camera I started recording and let it record until the camera filled up. On my 64GB 1000x Komputerbay Card that took 20 minutes of recording with 13 spanned files. It worked flawlessly and speed was consistent. The only concern I had was the temperature. See the image below. What are the safe temperatures the camera should be operating on? At what temperature does the camera shuts itself down to prevent damage? I'd assume that on a 128GB card you can go even longer to 40 minutes of recording . . . but would that be recommended?
Also, I know that in h.264 mode FPS Override would force the shutter to 1/FPS. Is this still the case with RAW?
(http://i.imgbox.com/adoxW3q7.jpg)
Quote from: artiswar on June 13, 2013, 12:41:45 AM
DaVinci seems to be the best workflow. @BoKia - You can pull more out if you open RAWMagic processed CDNGs in DaVinci and set the clip setting to BMD film. See below.
(http://imageshack.us/a/img833/4386/screenshot20130612at430.png)
Did you by any chance applied Hunter's 5D3 LUT to the image? Kind of looks like his Arri LUT.
Quote from: menoc on June 13, 2013, 01:00:42 AM
Did you by any chance applied Hunter's 5D3 LUT to the image? Kind of looks like his Arri LUT.
Nope. Solely the BMD Film color space from Davinci.
Quote from: a1ex on June 12, 2013, 08:53:11 PM
In this context, idle means it's not writing to the card. So, 10% of time is writing at ~80MB/s, 90% of time is just waiting for buffers to fill.
When idle time becomes 0, the buffer will slowly fill up and recording will stop eventually.
If there's a tiny bit of idle time, it's likely that recording will not stop (continuous recording). With this hint, you know how far you can go (this is used by ML to predict how much you will record at current settings).
Thanks for the explaining. Does that mean speed will not bottleneck at 70mb/s?
The peek speed I got for lower fps is 85mb/s. Hope it will happen in continuous recording in the future.
Quote from: rockfallfilms on June 13, 2013, 12:26:00 AM
How is everyone working out the framing in crop mode? I just had a play about with it but it's hard to know what's in frame.
With the new builds, the default zoom area is the centre of 5x crop image with about half horizontal line of 1920x1080.
I normally checked framing by guessing from the 1x mode according to the drawing in the crop mode thread, than focusing the centre in 5x, noticing edges will not show up there.
Quote from: Hokie123 on June 12, 2013, 11:21:07 PM
So I'm getting my Komputerbay 64gb Card tomorrow. Could someone list the steps I should take to test out my card, such as proper way to format/ benchmark/ etc? I want to make sure the card is fast enough so I don't have to RMA it.
bump
Quote from: Hokie123 on June 13, 2013, 04:59:05 AM
bump
If you're on a mac just download blackmagic's speed test (free). It writes a 5GB file to the card and tells you how many FPS you can expect. They may even have it for PC.
Greetings :D!
I've been testing raw video on my 50D for about a week now..
The first problem I had was, that my computer froze with .raw file on my card (via card reader). No idea why, but compliments to the 9th June update, which solved that problem.
My current problem is, that I can only record 12-15mb/s on raw recording. I have 16gb sandisk 30mb/s card (it achieved 27mb/s write rating on ml benchmark test). I have the latest update installed (from 11.6.) and i have formatted the card in camera (keeping ml).
Before the last update, it was even slower, about 10-12mb/s.
I scrolled trough the last two pages and noticed that you guys have much faster speeds.. Am I doing something wrong, or why does my card perform only 50% of it's potential?
Thx :)
(i hope I haven't opened up a solved issue..)
Quote from: NoWii on June 13, 2013, 01:31:41 PM
Greetings :D!
I've been testing raw video on my 50D for about a week now..
The first problem I had was, that my computer froze with .raw file on my card (via card reader). No idea why, but compliments to the 9th June update, which solved that problem.
My current problem is, that I can only record 12-15mb/s on raw recording. I have 16gb sandisk 30mb/s card (it achieved 27mb/s write rating on ml benchmark test). I have the latest update installed (from 11.6.) and i have formatted the card in camera (keeping ml).
Before the last update, it was even slower, about 10-12mb/s.
I scrolled trough the last two pages and noticed that you guys have much faster speeds.. Am I doing something wrong, or why does my card perform only 50% of it's potential?
Thx :)
(i hope I haven't opened up a solved issue..)
Your card is too slow, most people are using Komputerbay 64gb 1000x cards which are rated at around 100mb/s write, although most people are getting about 70mb/s.
Your 16gb sandisk 30mb/s card won't write fast enough so the buffer will fill up and recording will stop.
FROM BUILD 6/8/2013
So I went ahead to do a full shoot for a commercial spot using the 50D and came back with a few notes. Some of which I'm sure you guys are aware of already, but these are notes that came up under a pressured shoot situation.
1. I definitely need a larger card. I originally purchased a 32GB card for testing, but it's obvious that test-shooting and real-shooting are very different. I tend to use longer record times when filming for real and also swapped between 24fps and 30fps (via fps override) to gain a few more frames for slow motion in post. I'd say that the card reached 1GB of space in about 15min, give or take.
2. The storage indicator doesn't update after footage has been captured. It will continue to say that I have 29.7GBs left on the card, even after several minutes of filming. It wasn't until I changed batteries or turned it off that the indicator updated, informing me that I had run out of space at a really bad time.
3. 50D eats batteries like nobody's business. Seriously, I may have to purchase at least 10 of these puppies.
How old are your batteries though?
I've got 4 batteries of unknown age, and yes I must admit the 50D hoofs through them a lot quicker than my 600D doing the same thing.
However I've no clue how old they are, I'm sure a fresh set wouldnt go amiss.
In other news, my Samyang 35 F1.4 has actually got a really awesome minimum focus distance even without reversing or extension tubes.
This is a crop at minimum focus distance:
http://iforce.co.nz/i/5rgrkus5.aoh.jpg
Looking forward to trying out the 5x zoom mode at MFD and seeing what interesting or horrifying things I can capture haha.
I've just bought a couple of Duracell DRC511 batteries, replacements for the BP-511A. So far they are lasting pretty well and they are only £14 each.
Hey guys, one more report on cards and 50D recording.
I got a 1000x Komputerbay to replace the x600 one that did not write more than 24mo/sec.
Now it's all good, can shoot at full crop, 70mo/sec :) However I still have the pink picture when I zoom X5, I don't know if it is normal?
When outputting HDMI signal from 50D... I am using the May 9th build.
1. Playback of raw footage causes the camera to freeze. (Have two 50Ds and both have the same issue.)
2. ML Overlays have been very tricky. For example, I am able to view Global Draw and use my histogram for exposure settings on startup with the Canon display. Then, I will plug in the HDMI. The external monitor does not show the histograms or anything related to ML (except ML menus). When unplugging the HDMI, I am no longer able to view the ML histograms and feature sets on the Canon display during liveview. It's almost like the camera is back to the original Canon factory settings.
a. When turning on raw_recording I am able to display part of what may appear to be an ML on-screen overlay on the external monitor. It's like part of a very large white square, a square that is offset of the screen. It is blinking.
b. Also, when the camera is recording footage the recording bars are blinking on screen. However, it's nearly impossible to view the status of just how much footage has been captured and how many MB/s the camera is writing to the card.
Oh, I'm outputting the HDMI signal to an 23" LED monitor. It's not a production monitor. BUt that shouldn't affect the test, right?
Lastly, I was able to view the correct ML Global Draw LiveView overlays as though the external monitor were the same as the Canon display, but only one time. I have not yet been able to re-create the same results... This occurred after adjusting ML menu feature sets in the ML menu and not upon upon start up of the external monitor.
... Just want to say thanks g3ggo and ML Team! Thanks GreggoryofManhattan, JulianH... and other ML testers.
Quote from: bzhwindtalker on June 13, 2013, 06:45:45 PM
I still have the pink picture when I zoom X5, I don't know if it is normal?
Pink picture here too. Have yet to find a fix (if there is one)...?
Quote from: paulforte on June 13, 2013, 07:46:08 PM
Pink picture here too. Have yet to find a fix (if there is one)...?
Like wise. And when the shots are processed through RAWMagic I get harsh, crushed, ugly frames with white borders on the bottom.
Pink screen is normal. No fix (yet).
Got my Komputerbay 64GB 1000X, yay!
First of all, I'm happy. Now I can record the max 3:2 and 4:3 resolutions without problems.
But I wanted to know how far I could push it, here my results.
Didn't do anything special with it, formatted in camera.
50D results with 12june build by Gregory:
(hardly idle means just a few ms, no %)
1584x892
16:9 24 fps = continuous @68mb/s (17% idle)
16:9 25 fps = continuous @ 68mb/s (13% idle)
16:9 28 fps = continuous @ 64.5mb/s (hardly idle)
16:9 29 fps = 700 frames @ 64mb's (no idle)
16:9 30 fps = 400 frames @ 63mb/s (no idle)
1584x1058 (24 fps) = continuous 67.5mb/s (hardly idle)
1584x1058 (25 fps) = 800 frames 67mb/s (no idle)
5x zoom
1920x818 = continuous @ 66.2mb/s (5% idle)
1920x872 = 1700 frames @ 65.6mb/s (no idle)
1920x960 = 300 frames @ 65mb/s (no idle)
2000x836 - 1700 frames (hardly idle)
2000x852 - 999 frames (hardly idle)
2000x910 - 350 frames (no idle)
Isn't it strange that the speed goes down, when higher speeds are needed?
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_115920.jpg)
camera crashes when benchmarking in live view movie mode...
In my USB card reader it benchmarks (very quick test) at 122mb/s read and 93mb/s write.
Either the DMA gets overloaded by larger frame sizes, or FIO_WriteFile returns a bit earlier (so ML overestimates the speed a little).
Quote from: JulianH on June 13, 2013, 08:06:40 PM
Pink screen is normal. No fix (yet).
Good to know - thanks.
Off topic I know, but does anyone have an external battery solution for the 50D? I was looking to buy this - http://goo.gl/to1vd - but I believe the 50D uses different batteries and so it may not work. Any ideas?
Quote from: artiswar on June 13, 2013, 12:41:45 AM
DaVinci seems to be the best workflow. @BoKia - You can pull more out if you open RAWMagic processed CDNGs in DaVinci and set the clip setting to BMD film.
Sorry if this is naive... but is the BMD Film Gamma selection available in Resolve 9 Lite? I see the dropdown in Lite, but it's inactive.
Thanks for any info....
D
latest build with changes to Auto-ETTR (many changes since weekend)
raw_rec module should now keep settings
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/13june13-50D-0d47d7f96111.zip
if you are interested in testing auto-ETTR, don't forget to switch you back to saving raw photos in the canon menu.
speed should be comparable to what Julian just measured with yesterday's build.
cheers
Quote from: dhallowell19 on June 13, 2013, 10:20:16 PM
Sorry if this is naive... but is the BMD Film Gamma selection available in Resolve 9 Lite? I see the dropdown in Lite, but it's inactive.
Thanks for any info....
D
Click on the pulldown menu and select "Clip" should do the trick..
Quote from: a1ex on June 13, 2013, 08:09:35 PM
Either the DMA gets overloaded by larger frame sizes, or FIO_WriteFile returns a bit earlier (so ML overestimates the speed a little).
hopefully, there are a variety of fixes 1% has in process which should make the 50D code more efficient.
not sure if there's enough overhead in the 50D's capacity to hit the 1920x1080 - 83 MB/s in zoom mode.
seems like with fast cards, 70MB/s continuous is where we are at the moment.
JulianH do your DNGs come out exactly 1584x1084 and was your frame rate 24.0 ?
(if so, i'd expect 68.8 MB/s as opposed to your reported 67.5 MB/s)
Quote from: GregoryOfManhattan on June 13, 2013, 10:55:50 PM
latest build with changes to Auto-ETTR (many changes since weekend)
raw_rec module should now keep settings
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/13june13-50D-0d47d7f96111.zip
if you are interested in testing auto-ETTR, don't forget to switch you back to saving raw photos in the canon menu.
speed should be comparable to what Julian just measured with yesterday's build.
cheers
Great work getting better and better daily.. ;D
So I got the komputerbay 64gb 1000x, can someone tell me how to properly benchmark it in camera? I'm only getting a 45mbps write speed
Quote from: GregoryOfManhattan on June 13, 2013, 11:24:07 PM
JulianH do your DNGs come out exactly 1584x1084 and was your frame rate 24.0 ?
(if so, i'd expect 68.8 MB/s as opposed to your reported 67.5 MB/s)
Haven't checked any of the actual files, just let it run in the camera. Framerate was 23.976 (for 24). The reported write speed is changing over time - I noted the average. Most of the times it starts a bit lower and during recording it can change value a bit.
I'll give the new build a quick test and check if the files are ok at 1584x1058 .
/edit: See that I made a typo in my previous post... it's 1058 not 1084 of course.
/edit2: Speeds on june13th build look the same indeed. Getting 800-1000 frames at 1058x1058 25 fps. Continuous at 23.976 fps.
Quote from: paulforte on June 13, 2013, 10:14:32 PM
Off topic I know, but does anyone have an external battery solution for the 50D? I was looking to buy this - http://goo.gl/to1vd - but I believe the 50D uses different batteries and so it may not work. Any ideas?
I bought a pack of 2x2000mAh batteries for my 50D they costed around ~15$ They last about 2.5h of CONSTANT recording and about 8h for photography work. Even after 6 months they haven't lost any of their "power" so to speak.
So you could get about 6 of those packs for the same amount of money you would spend on the external battery pack.
Quote from: paulforte on June 13, 2013, 10:14:32 PM
Off topic I know, but does anyone have an external battery solution for the 50D? I was looking to buy this - http://goo.gl/to1vd - but I believe the 50D uses different batteries and so it may not work. Any ideas?
There is a solution for the 50D. The Canon DS8111. I bought mine at Samy's Camera. Here's one on ebay (http://www.ebay.co.uk/itm/Canon-DS8111-AC-Adapter-and-DC-Coupler-DR-400-Canon-/230943250849?pt=UK_Camera_Cables_Adapters&hash=item35c54a59a1).
Just like Bokia mentioned, you can get multiple batteries that are high mAh. I have 4 2200 mAh batteries that literally last 3 hours. Use them in a battery grip & you will be set. I've shot on 12 hour productions with these out in the field over past 2 years with great results.
The DS8111 is a great solution for indoors. I'm still hoping for a run n gun battery pack! I bought some 2200's, I guess that's the way to go. More the better. THANKS
Another 50d & 5dmk3 test:
Nice shots Jacub. Your sensor could use a cleaning though ;) And I think the vignetting is a bit too obvious. Wouldn't be able to tell the 5D3 from the 50D shots, but I see you finalized in 1600px.
Quote from: artiswar on June 13, 2013, 12:41:45 AM
DaVinci seems to be the best workflow. @BoKia - You can pull more out if you open RAWMagic processed CDNGs in DaVinci and set the clip setting to BMD film. See below.
Uploaded with ImageShack.us (http://imageshack.us)
(http://imageshack.us/a/img833/4386/screenshot20130612at430.png) (http://imageshack.us/photo/my-images/833/screenshot20130612at430.png/)
Uploaded with ImageShack.us (http://imageshack.us)
Great tip! Just been playing with some of my footage in Resolve Lite and it looks really nice. Apart from coloring. the scaling and sharpening algorithms seem to be much better in Resolve than Premier Pro or After Effects.
Quote from: GregoryOfManhattan on June 13, 2013, 10:55:50 PM
latest build with changes to Auto-ETTR (many changes since weekend)
raw_rec module should now keep settings
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/13june13-50D-0d47d7f96111.zip
if you are interested in testing auto-ETTR, don't forget to switch you back to saving raw photos in the canon menu.
speed should be comparable to what Julian just measured with yesterday's build.
cheers
Good work !!! Thank you !!!
Quote from: jakub on June 14, 2013, 12:53:13 AM
Another 50d & 5dmk3 test:
Great video couldn't tell the difference between the two. What was your workflow?
You are right @Andy600 Davinci upscale looks exactly like the original I don't know what's going on under the hood but it's working beautifully.
Quote from: BokiA on June 14, 2013, 12:11:46 AM
I bought a pack of 2x2000mAh batteries for my 50D they costed around ~15$ They last about 2.5h of CONSTANT recording and about 8h for photography work. Even after 6 months they haven't lost any of their "power" so to speak.
So you could get about 6 of those packs for the same amount of money you would spend on the external battery pack.
Could you refer us to a few models? I'm really interested in this and could definitely use the hardware upgrade ;-)
@1% - How did you get Display Filters working? I enabled them and recompiled but they don't show in the menu
Its not as simple as that. I figured out how a1ex did it for 5DII and ported it. You have to add the code to your repo to make it work.
Using Gregory's June 13th build I'm finding my komputerbay 1kx 64G card is now slowed back down to 45-50Gb/s (1584x892)...
GLobalDraw = LiveView, small waveform. Everything else off, and per the long list of suggestions that were specified a week or so ago.
Exposure Sim is ON, and even when I hit Func and attempt to turn off - I see the ON and OFF choices, but neither wheel effects a change - so that's on no matter what.
Thanks for any ideas about what I might have missed....
(http://s12.postimg.org/ck7g1xir0/ML_14_000000.jpg)
I'm getting some nice image when converting from raw to CinemaDNG then used lightroom :)
Quote from: dhallowell19 on June 14, 2013, 04:27:23 AM
Using Gregory's June 13th build I'm finding my komputerbay 1kx 64G card is now slowed back down to 45-50Gb/s (1584x892)...
GLobalDraw = LiveView, small waveform. Everything else off, and per the long list of suggestions that were specified a week or so ago.
Exposure Sim is ON, and even when I hit Func and attempt to turn off - I see the ON and OFF choices, but neither wheel effects a change - so that's on no matter what.
Thanks for any ideas about what I might have missed....
Exposure Sim should say 'movie' (because you're in movie mode ;)) and should be on. If you switch out of Movie mode you'll see you can switch it off. Try turning off waveform and use histogram. Reformat your card and delete your config file then try again. I noticed a speed drop for 1st recording then it goes back to high speeds.
Quote from: Andy600 on June 14, 2013, 09:02:51 AM
I noticed a speed drop for 1st recording then it goes back to high speeds.
Same here.
I've forked Gregory's repo so I can compile updates with the latest changesets when he's not around. Anything I upload has been tested on my camera. If you are just getting started with the 50d DO NOT use my builds but read post #1.
My compiles are here: https://bitbucket.org/andy600/magic-lantern/downloads (up to Unified commit 4c83f9e)
I've been trying various raw workflows using After Effects, Premier Pro and Davinci Resolve Lite and I get the best looking footage this way:
1) Shooting raw video - ETTR always ON / Push WB (seems to give better results in post)
2) raw video converted to 12bit Cinema DNG using Chmee's excellent raw2CDNG converter http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/ (no need to lower White Level if you used Auto ETTR)
3) In Resolve - Camera Raw set to CinemaDNG with Gamma and Colorspace set to BMD Film with Highlight recovery ON
4) Resolve Image Scaling - Smoother Filter with Anti-Alias Edges ON (by far the best method of upscaling I have used)
5) In first Node set LUT to 3D > ARRI > Arri Alexa LogC To REC709 (you can set this in setup if you want but I prefer to have control per clip) - The Blackmagic Cinema Camera Film to Rec709 LUT is also good but a little too vibrant for me
tip: http://www.arri.de/camera/digital_cameras/tools/lut_generator/lut_generator.html
6) sharpen to taste (you can sometimes get nice results using the MIST setting in Blur/Sharpen) - Resolve sharpening is better than Adobe full stop! ;)
7) Image stabilization in Resolve is fantastic and very FAST! (set Tracker to Stabilizer if you want to use it)
8) CC, edit and output to the format of your choice for editing in your NLE
I don't know why but shooting and editing this way seems to have a positive impact on moire in the tests that I have done. Works for me :)
(Don't forget to use separate nodes for every edit you make in Resolve)
Thanks a lot for that! Been looking for a good workflow. This seems to be fairly quick and painless in comparison to what i've been doing.
My Toshiba 1066X 64GB arrived today, and I have been doing some tests :)
I used Andy600's build of June 14th.
Benchmark in Moviemode, Global Draw OFF. Crashed during the test so here is a photo of the screen after the freeze:
(http://imageshack.no/59r)
Playbackmode, Global Draw ON:
(http://imageshack.no/59t)
When testing the card on ATTO Disk Benchmark (default settings) the highest writespeed i get is approx 125 MB/s.
Quote from: GregoryOfManhattan on June 13, 2013, 10:55:50 PM
latest build with changes to Auto-ETTR (many changes since weekend)
raw_rec module should now keep settings
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/13june13-50D-0d47d7f96111.zip
if you are interested in testing auto-ETTR, don't forget to switch you back to saving raw photos in the canon menu.
speed should be comparable to what Julian just measured with yesterday's build.
cheers
So, Auto-ETTR is gone for now?
Quote from: menoc on June 14, 2013, 05:52:25 PM
So, Auto-ETTR is gone for now?
No, it's now a module and all modules have config files (settings are saved) :)
But remember to choose save to RAW in canon menu if not already done. And since Record start have been changed to Set button you will have to choose how to activate Auto-ETTR (double click shutter or Always on).
Personally I found ETTR unreliably on this build, but it seems to be a bit better on Andy600's build of today. Mostly unreliably on not Auto-ETTR when doubleclicking the shutter - sometimes I have to doubleclick many times before it activates.
I got the benchmark working in moviemode. Just had to change the Movie Record (H264) setting to 640x480.
(Toshiba 1066X 64GB)
Moviemode, Global Draw OFF:
(http://imageshack.no/59u)
I installed the latest June 13 build and it looks like it's speedy. But Auto-ETTR seems to have disappeared. I have the camera set to RAW in canon menus and I have loaded all modules. Is that normal?
Quote from: johansugarev on June 14, 2013, 06:43:00 PM
I installed the latest June 13 build and it looks like it's speedy. But Auto-ETTR seems to have disappeared. I have the camera set to RAW in canon menus and I have loaded all modules. Is that normal?
Try this one http://www.magiclantern.fm/forum/index.php?topic=5586.msg50809#msg50809
Thanks.
I'm going to re-write the first post later and want a few nice 'showcase' videos so everyone can see what the 50d is really capable of with raw video. I already know a few that are contenders but let me know if you have any suggestions for the following categories (need maybe 6-10):
Macro
Low Light / Night
Anamorphic
Motion
Skin
Aliasing and Moire (worst case scenarios)
Color
Any other suggestions welcome :)
Thanks!
Quote from: Andy600 on June 14, 2013, 07:09:13 PM
I'm going to re-write the first post later and want a few nice 'showcase' videos so everyone can see what the 50d is really capable of with raw video. I already know a few that are contenders but let me know if you have any suggestions for the following categories (need maybe 6-10):
Macro
Low Light / Night
Anamorphic
Motion
Skin
Aliasing and Moire (worst case scenarios)
Color
Any other suggestions welcome :)
Thanks!
That's a great Idea Andy..
Quote from: Andy600 on June 14, 2013, 07:09:13 PM
I'm going to re-write the first post later and want a few nice 'showcase' videos so everyone can see what the 50d is really capable of with raw video. I already know a few that are contenders but let me know if you have any suggestions for the following categories (need maybe 6-10):
Macro
Low Light / Night
Anamorphic
Motion
Skin
Aliasing and Moire (worst case scenarios)
Color
Any other suggestions welcome :)
Thanks!
Dynamic Range. Use a light meter to figure out lighting ratios (64:1, 32:1, etc.)
Direct comparison to t3i or similar, non raw.
Yeah I'm back into raw 50d land :) I do have a brand new Komputerbay 1000x 64gb card.
My previous komputerbay 1000x 64gb was broken (actually it was already dying when I received it, but I thought my cardreader was causing the trouble...)
I just tested the latest Andy build and works like a charm. I see lots of quirks are fixed now and it's so stable:
I was able to record a 50gb raw recording 1592x892 (16:9) with raw histogram enabled. Time to record some real footage :)
I got the komputerbay 64gb card. Formatted to fat32 (bleh).. aligned to 4096 with 64K clusters (largest fat32 formatter can make and best according to shield's tests). Still waiting on charger or ac adapter. Dunno why new AA's go from full to flat in 10 sec.
Quote from: 1% on June 15, 2013, 02:08:41 AM
I got the komputerbay 64gb card. Formatted to fat32 (bleh).. aligned to 4096 with 64K clusters (largest fat32 formatter can make and best according to shield's tests). Still waiting on charger or ac adapter. Dunno why new AA's go from full to flat in 10 sec.
Sounds like a faulty battery caddy in the grip maybe
Quote from: Andy600 on June 14, 2013, 11:47:22 AM
1) Shooting raw video - ETTR always ON / Push WB (seems to give better results in post)
Noob question. Where is ETTR?
Yea, maybe need to push the battery caddy up with paper or something.. or these AA's aren't enough voltage. I got enough juice to boot a little from both batteries in the grip... oh well other stuff should be here soon. I ordered on the same day.
Quote from: artiswar on June 15, 2013, 02:28:21 AM
Noob question. Where is ETTR?
Exposure settings - 1st tab in the menu
Quote from: 1% on June 15, 2013, 02:33:02 AM
Yea, maybe need to push the battery caddy up with paper or something.. or these AA's aren't enough voltage. I got enough juice to boot a little from both batteries in the grip... oh well other stuff should be here soon. I ordered on the same day.
Did you check the AA's after in another device?
Yea, with DMM. Show normal voltages.. but they are cheapies... maybe lithium ones would work.
Quote from: 1% on June 15, 2013, 02:41:16 AM
Yea, with DMM. Show normal voltages.. but they are cheapies... maybe lithium ones would work.
Probably not worth the cost only to have the same thing happen unless you have some laying around. The 50d is quite hungry. I have 2 chargers on the go all the time but my batteries are quite old.
Quote from: 1% on June 15, 2013, 02:08:41 AM
I got the komputerbay 64gb card. Formatted to fat32 (bleh).. aligned to 4096 with 64K clusters (largest fat32 formatter can make and best according to shield's tests). Still waiting on charger or ac adapter. Dunno why new AA's go from full to flat in 10 sec.
I got a similar thing happened when I firstly realigned my card to 4096. Battery suddenly died after I insert the card. But nothing went wrong after I recharged it. Weird!
Quote from: Andy600 on June 14, 2013, 07:09:13 PM
I'm going to re-write the first post later and want a few nice 'showcase' videos so everyone can see what the 50d is really capable of with raw video. I already know a few that are contenders but let me know if you have any suggestions for the following categories (need maybe 6-10):
Macro
Low Light / Night
Anamorphic
Motion
Skin
Aliasing and Moire (worst case scenarios)
Color
Any other suggestions welcome :)
Thanks!
Hi all,
Thank you all for made this possible. It's not only an amazing story but it's the thruth ... 14 bit RAW + 50MBYTE/s when recording 24, 25, 30 frames/s on a canon 50D from 2008.
Haven't seen green screen results yet. So if ... I suggest a cattegorie for it.
TVMol
Hey guys I'm still getting pink tones in all modes (not just in hightlights), despite using a recent build of RAW2dng, with the june 13 build in camera. Is it normal?
Quote from: bzhwindtalker on June 15, 2013, 02:27:56 PM
Hey guys I'm still getting pink tones in all modes (not just in hightlights), despite using a recent build of RAW2dng, with the june 13 build in camera. Is it normal?
Yes it is, when you import the DNG's to AE, they will open themselves in CRaw and there you can just move a slider for the green/magenta tint from +148 to +70 and that will remove all the pink tones and everything will look 'normal', then render it out as prores 422 and edit it :)
I'm working on a 4k Build and other tweaks... just wondering where the latest branch is which I should use for the 50D?
I know multiple ppl have various branches. Any insight on which has the cleanest & most up to date code?
Here's my first real edit with the 50D, cant wait to get shooting projects with it!
Quote from: krashnik on June 15, 2013, 06:29:40 PM
I'm working on a 4k Build and other tweaks... just wondering where the latest branch is which I should use for the 50D?
I know multiple ppl have various branches. Any insight on which has the cleanest & most up to date code?
Yeah contact @Gregoryofmanhattan his been working diligently on 50D's code & thanks to his hard work we currently getting 70mb/s. Are you talking about 4K build for the 50D or I'm reading it wrong? Is that even possible?
I'm going to say no... but let him try to surprise us.
Quote from: bzhwindtalker on June 15, 2013, 07:35:35 PM
Here's my first real edit with the 50D, cant wait to get shooting projects with it!
That is beautiful man great test.. What shots were shot in 2000X crop mode cause I can't tell the difference in quality. Keep the videos coming... if you really wanna tweak your images you should try to concert to .DNG's and do your initial color correction with Adobe Camera Raw in After effects.
Quote from: 1% on June 15, 2013, 08:40:11 PM
I'm going to say no... but let him try to surprise us.
That's what I said too.. let's wait and see. I see you having problems with batteries on your 50D because you don't have the charger, hope you get it up and running soon.. When is your charger coming?
Quote from: goldenchild9to5 on June 15, 2013, 08:35:18 PM
Yeah contact @Gregoryofmanhattan his been working diligently on 50D's code & thanks to his hard work we currently getting 70mb/s. Are you talking about 4K build for the 50D or I'm reading it wrong? Is that even possible?
I just forked @Gregoryofmanhattan on bitbucket. Hopefully that will work. I am talking about 4k on 50D. It will definitely work, it's just a matter of how high of quality it will be & if reverse-engineering is worth the effort. I'll post progress on bitbucket (https://bitbucket.org/krashnik/magic-lantern/). Best of luck to other weekend coders!
Quote from: krashnik on June 15, 2013, 09:14:59 PM
I am talking about 4k on 50D. It will definitely work
That's interesting. 14-bit RAW videos with a resolution of 4096 X 2304 at 24 frames per second require 378 Megabyte/s write speed.
Might become a little tight with the 50D's write speed ... ;D
But for silent pictures 4K would be a nice feature on all Canon DSLR.
Remember this?
http://twitter.com/cineblur/status/149357130175098880
Quote from: CFP on June 15, 2013, 09:27:58 PM
That's interesting. 14-bit RAW videos with a resolution of 4096 X 2304 at 24 frames per second require 378 Megabyte/s write speed.
Might become a little tight with the 50D's write speed ... ;D
But for silent pictures 4K would be a nice feature on all Canon DSLR.
I'm not talking about 4K raw. I'm talking about JPG at 4k. This requires significantly less throughput. We already have small JPG image capability on the camera, just need to put this in silent burst mode and see how many frames per second we can make happen with it.
This mod will allow us to sacrifice dynamic range & low-light capability for increased resolution with the same bandwidth. We can also start with 8-bit and work our way up to higher br until bandwidth is at max threshold.
Quote
just need to put this in silent burst mode and see how many frames per second we can make happen with it.
This is the easiest part. The question is... how do you get high-res jpegs without moving the shutter?
Low-res jpegs are trivial, and so is mjpeg. See http://www.magiclantern.fm/forum/index.php?topic=2803.0 (one of my posts from there contains a mjpeg video, 1120x752 on 5D2)
QuoteWhen is your charger coming?
I'm tracking and says out for delivery... but its saturday 3PM so I dunno wtf the post office is doing.
Lol, it wasn't that trivial since it never got 100% usable and the FPS wasn't that big... maybe now with edmac on 50D/5D2 it would work because of lv_save_jpeg.
Yes, back then it wasn't trivial, but now I expect it to work just fine on old cameras if you replace the source buffers in raw_rec and slap a mjpeg header.
On 5D3 I still don't know how to get the jpegs, except for the EOS utility trick.
The jpeg function still didn't work for me when I was tethered, just crashed LV. On 600D tetherin worked... seems like a nice idea to revisit and possible to just cache hack the jpeg to be larger sized... it has the whole raw size to work with. But even in EOS utility the FPS is closer to 20 with the small ones.. maybe the jpeg engine isn't fast enough? And 2 in 2 out would imply it processes 2 frames at once?
Also lv_save_sndpass size should be investigated for 422. That way maybe there could be a choice, RAW -> 422 -> jpeg. Would completely obsolete H264
Quote from: 1% on June 15, 2013, 10:29:29 PM
The jpeg function still didn't work for me when I was tethered, just crashed LV. On 600D tetherin worked... seems like a nice idea to revisit and possible to just cache hack the jpeg to be larger sized... it has the whole raw size to work with. But even in EOS utility the FPS is closer to 20 with the small ones.. maybe the jpeg engine isn't fast enough? And 2 in 2 out would imply it processes 2 frames at once?
Also lv_save_sndpass size should be investigated for 422. That way maybe there could be a choice, RAW -> 422 -> jpeg. Would completely obsolete H264
Yes, this is why I want to revisit it. I believe the knowledge gained from RAW can be applied to what you have already tried on JPG in past.
I feel the architecture of the canon firmware was designed to accept slow CF cards. We could optimize this for 1000x cards only - which would cause slower cards to crash, but at least give us new buffers & capabilities for the faster cards we have today.
The RAW -> 422 -> jpeg setup sounds great as long as the buffer doesn't get filled too quickly since we will be re-introducing compression.
True.. if you're up for it start disassembling the FW. 50D has other stuff to FIX first so its at least up to 5DII.
QuoteI feel the architecture of the canon firmware was designed to accept slow CF cards.
Why, it just kinda works with whatever you throw into it. For the buffers it may help to somehow alter the contiguous memory to be faster. Right now only the first chunk is 29M and the rest are 27. I dunno if optimal write on this camera is closer to 31MB or 28, 29, etc. Memory can be "re-organized" by several functions in the resource manager... also find a way to get the blue blocks back.
Check the asm+hardware first tho... this isn't a 1 day and you're done type of thing unless you're superman.
Second test video. First using the 08June13 build. Still experiencing a lot of magenta frames (1-5 per 30 second shots) and a lot more "flickering" as in jumping aperture. Average write speed was 57mbps and had no issues with the buffer (usually 1 star, maybe 2 stars) and could record without filling up the buffer.
Used a Lexar 64gb 1000X card, Zeiss 80mm f/2.8 taking lens and Moller Bolex 1.5x anamorphic lens. Shot on a gloomy windy day, mid afternoon.
Workflow RAW>RAWMagic>Photoshop>Quicktime>Final Cut 7 (export from QT at 1280x720 then scaled to 640x480 with -33% for anamorphic)
Recorded at 1584x892 at 1600 using all of the forum suggestions.
Nice shots Frerichs, I don't understand why you have those issues. I don't experience any of them. Try a clean install and a new build I'd say...
Btw: why didn't you unsqueeze the footage? You shot 16:9 with an 1.5x anamorphic, but your final export is 16:9 (and looks squeezed) - you should resize the 1584 width to 150% (2376 pixels).
I don't know how it works in FCP, but in Premiere I just make a project with my desired resolution (in your case that would be 2376x892) then import the files and stretch the clips (150% in your case). Then you could export to 1920x720 for example.
Quote from: Frerichs on June 15, 2013, 11:19:39 PM
and a lot more "flickering" as in jumping aperture.
This was probably caused by Adobe camera raw, I got the same issue as have others. ACR seems to be doing auto adjusting behind the scenes and causing a flicker in the highlights. So far there doesn't seem to be a solution, other than going direct to Resolve.
Ah, makes sense. Going to install the latest build and use Resolve going forward. Just experimenting at this stage but love what the 50D can do, even at this early stage.
Also, the magenta frames seem to only happen when I use an external monitor. You can see the magenta blip when recording and usually get 1 to 5 during a 30-second clip. I'm using a SmallHD 7" HDMI monitor.
Quote from: rockfallfilms on June 15, 2013, 11:46:31 PM
This was probably caused by Adobe camera raw, I got the same issue as have others. ACR seems to be doing auto adjusting behind the scenes and causing a flicker in the highlights. So far there doesn't seem to be a solution, other than going direct to Resolve.
Wasn't that fixed by using an older process version? The new one applies highlight corrections even if you don't touch any of the sliders I think.
It happens with all the processes to varying degrees, 2010 is slightly better but doesn't cure it.
You can turn off autotone so ACR stops guessing but this is the way I understand it:
if there's a change in exposure during the scene like the sun coming out then the frames with the brighter sun would inherit the same changes which were made on the 1st image that was changed in ACR. (with darker initial exposure) I believe that the only real way round it is to find the brighter frames and make different corrections to them to compensate. That would take too long though!
What is needed is some kind of smooth transition between frames to iron out any differences in exposure. Out of all my shots so far, I've only had an issue with one so I'll just live with it for now!
Quote from: rockfallfilms on June 16, 2013, 12:13:10 AM
It happens with all the processes to varying degrees, 2010 is slightly better but doesn't cure it.
You can turn off autotone so ACR stops guessing but this is the way I understand it:
if there's a change in exposure during the scene like the sun coming out then the frames with the brighter sun would inherit the same changes which were made on the 1st image that was changed in ACR. (with darker initial exposure) I believe that the only real way round it is to find the brighter frames and make different corrections to them to compensate. That would take too long though!
What is needed is some kind of smooth transition between frames to iron out any differences in exposure. Out of all my shots so far, I've only had an issue with one so I'll just live with it for now!
Or use the CDNG and DaVinci workflow. Much cleaner.
Quote from: artiswar on June 16, 2013, 12:40:14 AM
Or use the CDNG and DaVinci workflow. Much cleaner.
Unfortunately Davinci's debayer isn't as good as ACR and I find the DNG raw controls pretty limiting. Also ACR's chroma noise reduction does a good job of reducing moire.
There's no perfect workflow for me yet, I'm hoping resolve 10 will improve things.
I'm looking at a lot of 50D RAW footage. Most of it is pretty soft, especially compared to the 5D mkIII. Only rarely i find footage that is quite sharp.
Anyone know why this is? Is it only due to people using soft lenses, cause i would think that would be quite the coincidence.
Anyway, i think this thread's got great potential. Possibly i will buy a second-hand 50D as well. I just need to know if it will be sharp enough.
Heh, got battery charger.. charging 'em up.
Hey! I finally got a working 50D!! :D
Quote from: 1% on June 16, 2013, 02:43:46 AM
Heh, got battery charger.. charging 'em up.
Let's go :D
Quote from: Andy600 on June 14, 2013, 10:47:07 AM
I've forked Gregory's repo so I can compile updates with the latest changesets when he's not around. Anything I upload has been tested on my camera. If you are just getting started with the 50d DO NOT use my builds but read post #1.
My compiles are here: https://bitbucket.org/andy600/magic-lantern/downloads (up to Unified commit 4c83f9e)
Is it normal for this build to have auto ETTR work in P mode, seems like M mode is ML's preference (blinking -live view- blue button until M mode is selected -except Auto ETTR is non-functional) :o
Quote from: 1% on June 16, 2013, 02:43:46 AM
Heh, got battery charger.. charging 'em up.
Now that's what I'm talking about. Let the games begin.. ;D
Quote from: soulofsound on June 16, 2013, 01:31:49 AM
I'm looking at a lot of 50D RAW footage. Most of it is pretty soft, especially compared to the 5D mkIII. Only rarely i find footage that is quite sharp.
Anyone know why this is? Is it only due to people using soft lenses, cause i would think that would be quite the coincidence.
Anyway, i think this thread's got great potential. Possibly i will buy a second-hand 50D as well. I just need to know if it will be sharp enough.
50D can be really sharp, I've shot some sharp footage with it.
It was 106 degrees in Phoenix, AZ today. I found myself standing on top of a rock faced mountain overlooking most of the city. Had a set of lenses, 2 64GB 1000X Komputerbay cards, and a slew of batteries...
The camera showed the "overheating" indicator on-screen quite-a-lot. However, the camera did not power off. I used to own a 550D and that camera would automatically shut down after about 10 minutes in direct sunlight. I carried a large white towel to utilize the Canon's display in direct sunlight as well as to protect and keep the camera cool when moving from shot to shot. In the end, the camera did not automatically turn off, not once.
It was reliable enough to set the camera to raw_record, start/leave the recording, climb the last 30 feet of a mountain, and grab a hero shot!
Say, if you haven't used MagicRAW beta 6 from Thomas Worth I highly recommend downloading this beta. Files are spanning perfectly. Here is a link to beta 7... http://www.mediafire.com/download/ht3ydb4s254ka5z/RAWMagic-beta7a.dmg. I imagine it's only better than beta 6.
Quote from: soulofsound on June 16, 2013, 01:31:49 AM
I'm looking at a lot of 50D RAW footage. Most of it is pretty soft, especially compared to the 5D mkIII. Only rarely i find footage that is quite sharp.
Anyone know why this is? Is it only due to people using soft lenses, cause i would think that would be quite the coincidence.
Anyway, i think this thread's got great potential. Possibly i will buy a second-hand 50D as well. I just need to know if it will be sharp enough.
You can't do better than the 50D for the price.. and it's still in an early dev stage I think, so the safe resolution could improve .. even now however many of the images are great - especially when aliasing and moire are avoided.. very cinematic, which does not necessarily mean ultra-sharp
I'm looking at some of the 5x crop images... They are incredibly sharp!!! No aliasing or moire. It's tough to look away.
Not sure if it's my ACR process, but I am noticing squares/black lines between the pixels. They are highly noticeable in a perfect blue sky.
Using the MagicRaw Beta 7 along with AE & ACR to process footage...
Quote from: 7thRest on June 16, 2013, 03:31:56 AM
Is it normal for this build to have auto ETTR work in P mode, seems like M mode is ML's preference (blinking -live view- blue button until M mode is selected -except Auto ETTR is non-functional) :o
Yes, it's supposed to work thanks to @a1ex's commit
b84b98c 'Auto ETTR: experimental support for auto modes (Av, Tv, P)'If nothing is happening you must have Exposure Override set to ON. Try Auto ;)
Got no blinking blue light here though in P mode
Quote from: soulofsound on June 16, 2013, 01:31:49 AM
I'm looking at a lot of 50D RAW footage. Most of it is pretty soft, especially compared to the 5D mkIII. Only rarely i find footage that is quite sharp.
Anyone know why this is? Is it only due to people using soft lenses, cause i would think that would be quite the coincidence.
Anyway, i think this thread's got great potential. Possibly i will buy a second-hand 50D as well. I just need to know if it will be sharp enough.
Lens, aperture settings and post sharpening choices can make footage soft. A lot of footage I've seen is over-sharp which, IMO is ugly. If you compare upscaled raw video from the 50d to H.264 you'll see it's a lot more
detailed. Don't confuse sharpness with resolution ;)
5d2 footage will be marginally higher resolution when upscaled as it's native raw video frame size is a little bigger than the 50d's... but 50d upscaled raw video still wipes the floor with native EOS H.264 1080p
BTW the best sharpening and upscaling method I have found is to work in Davinci Resolve Lite (FREE). I can't get Premier Pro or After Effects anywhere near the same quality without artifacts. See this: http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829)
Quote from: TVMol on June 15, 2013, 01:55:54 PM
...
Haven't seen green screen results yet. So if ... I suggest a cattegorie for it.
TVMol
Yes, I forgot to add that one. Thanks for your suggestion :)
Hey Andy, seems like your latest build is having issues with iso, the top lcd says iso 100 but the liveview 3200 and I can't change it.
Edit, it has something to do with exposure override, maybe it's just me
Quote from: bzhwindtalker on June 16, 2013, 01:44:39 PM
Hey Andy, seems liike your latest build is having issues with iso, the top lcd says iso 100 but the liveview 3200 and I can't change it.
Yes, I think it's a 50d specific bug with ETTR and I've removed the download. Revert to Gregory's latest build as it's newer than my previous one. Hopefully one of the guys will have a look at the issue later.
I still can't figure out why I get pink tones with raw2dng (and apps based on it) while raw2cdng works perfectly?
I made this test with the latest raw2dng downloaded from bitbucket.
(https://fbcdn-sphotos-f-a.akamaihd.net/hphotos-ak-prn2/p200x200/983575_10151675954929617_948239915_n.jpg)
(https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-frc1/p200x200/1004580_10151675954919617_767648952_n.jpg)
Quote from: bzhwindtalker on June 16, 2013, 02:34:42 PM
I still can't figure out why I get pink tones with raw2dng (and apps based on it) while raw2cdng works perfectly?
Backup raw2dng.exe in whatever app directory you are using and try this one https://bitbucket.org/andy600/magic-lantern/downloads/raw2dng.exe
You need to adjust white balance manually.
Quote from: Andy600 on June 16, 2013, 02:57:53 PM
Backup raw2dng.exe in whatever app directory you are using and try this one https://bitbucket.org/andy600/magic-lantern/downloads/raw2dng.exe
No workie, your file is 18kb vs 260~ for the regular one?
Quote from: Andy600 on June 16, 2013, 10:37:00 AM
BTW the best sharpening and upscaling method I have found is to work in Davinci Resolve Lite (FREE). I can't get Premier Pro or After Effects anywhere near the same quality without artifacts. See this: http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829)
I second that, Resolve's sharpening algorithm is pretty good. The best results can be had by sharpening only the luma channel and not the chroma, this will avoid colour fringes.
http://www.liftgammagain.com/forum/index.php?threads/building-a-better-sharpen-in-resolve.278/ (http://www.liftgammagain.com/forum/index.php?threads/building-a-better-sharpen-in-resolve.278/)
Quote from: bzhwindtalker on June 16, 2013, 03:07:30 PM
No workie, your file is 18kb vs 260~ for the regular one?
oops, my bad. Have you tried the last updated one here? https://bitbucket.org/hudson/magic-lantern/downloads
Quote from: rockfallfilms on June 16, 2013, 03:13:46 PM
I second that, Resolve's sharpening algorithm is pretty good. The best results can be had by sharpening only the luma channel and not the chroma, this will avoid colour fringes.
http://www.liftgammagain.com/forum/index.php?threads/building-a-better-sharpen-in-resolve.278/ (http://www.liftgammagain.com/forum/index.php?threads/building-a-better-sharpen-in-resolve.278/)
Yep, I built one of those node setups ages ago and saved it as a look. Forgot all about it ;D
Quote from: Andy600 on June 16, 2013, 03:19:39 PM
oops, my bad. Have you tried the last updated one here? https://bitbucket.org/hudson/magic-lantern/downloads
Yep that's the one I used. I can correct this tone in post but it's always better to start with files looking good!
BTW is there any developpemnt going on to port the audio sync beep feature on the 50D? Is it even possible on the hardware side?
Adam
Quote from: bzhwindtalker on June 16, 2013, 03:44:00 PM
Yep that's the one I used. I can correct this tone in post but it's always better to start with files looking good!
BTW is there any developpemnt going on to port the audio sync beep feature on the 50D? Is it even possible on the hardware side?
Adam
Yes, I think 1% got it working along with screen filters (anamorphic squeeze, defish etc).
I know we've all gotten used to it by now but, I'm madly in love w/ the 50D's new-found digital cinema capabilities thanks to you guys here.
I alternately swap between RAWanizer DNxHD export and Lightroom export depending on how much latitude I want. Here's one workflow I've used for the commercial spot we're shooting:
1. DNG to Lightroom (specifically to save latitude)
2. export upscale to 1920px horizontally at 100% JPEG quality
3. edit in Premiere CS6 (JPG frame sequence)
4. export as DPX LOG frame
5. color in AE CS6 (combination of adding a specific LUT base, then grading in curves, sharpening and adding 35mm grain scan)
(http://farm8.staticflickr.com/7449/9058788202_f6e95c2962_h.jpg)
Quote from: KahL on June 16, 2013, 04:48:14 PM
...
1. DNG to Lightroom (specifically to save latitude)
2. export upscale to 1920px horizontally at 100% JPEG quality
3. edit in Premiere CS6 (JPG frame sequence)
4. export as DPX LOG frame
5. color in AE CS6 (combination of adding a specific LUT base, then grading in curves, sharpening and adding 35mm grain scan)
So you are exporting to JPEG first? Surely you are losing all that nice color information ???
Quote from: KahL on June 16, 2013, 04:48:14 PM
I know we've all gotten used to it by now but, I'm madly in love w/ the 50D's new-found digital cinema capabilities thanks to you guys here.
I alternately swap between RAWanizer DNxHD export and Lightroom export depending on how much latitude I want. Here's one workflow I've used for the commercial spot we're shooting:
1. DNG to Lightroom (specifically to save latitude)
2. export upscale to 1920px horizontally at 100% JPEG quality
3. edit in Premiere CS6 (JPG frame sequence)
4. export as DPX LOG frame
5. color in AE CS6 (combination of adding a specific LUT base, then grading in curves, sharpening and adding 35mm grain scan)
(http://farm8.staticflickr.com/7449/9058788202_f6e95c2962_h.jpg)
Thanks for the workflow! The pic's look very good. Wend can we see the final work?
I have some questions,
-why export in DPX Log?
-what is this espcific Lut base?
Hope to see the final output. Good work =D
Quote from: Andy600 on June 16, 2013, 03:56:24 PM
Yes, I think 1% got it working along with screen filters (anamorphic squeeze, defish etc).
Anamorphic (de)squeeze... omg, can't wait!
Thanks for all the Resolve tips guys. Going to shoot something for the Vimeo Weekend project (https://vimeo.com/videoschool/lesson/409/weekend-challenge-shapes) and will do the CinemaDNG/Resolve workflow :)
For those of you who are new to Magic Lantern and are not very adept at the command line, here's a tutorial on how to merge ML RAW files without having to use the command line. This tutorial was created for the Mac, but it will also work in Windows. You'll need a hex editor and of course, a DNG extractor Utility like raw2dng, RAWMagic or raw2cdng.
HEX EDITORS:
Hex Fiend Hex editor for Macintosh
http://ridiculousfish.com/hexfiend/ (http://ridiculousfish.com/hexfiend/)
HxD Hex editor for Windows
http://mh-nexus.de/en/hxd/ (http://mh-nexus.de/en/hxd/)
RAW UTILITY:
RAWMagic
http://www.mediafire.com/download/ht3ydb4s254ka5z/RAWMagic-beta7a.dmg (http://www.mediafire.com/download/ht3ydb4s254ka5z/RAWMagic-beta7a.dmg)
raw2dng
http://www.magiclantern.fm/forum/index.php?topic=5404.0 (http://www.magiclantern.fm/forum/index.php?topic=5404.0)
Quote from: KahL on June 16, 2013, 04:48:14 PM
1. DNG to Lightroom (specifically to save latitude)
2. export upscale to 1920px horizontally at 100% JPEG quality
3. edit in Premiere CS6 (JPG frame sequence)
4. export as DPX LOG frame
5. color in AE CS6 (combination of adding a specific LUT base, then grading in curves, sharpening and adding 35mm grain scan)
As Andy600 said, you are exporting as jpeg and killing your colour information (going from 14bit to 8 bit) then grading an 8 bit image in AE.
A better workflow would be to open the DNG image sequence directly into AE via ACR, that way you keep all your colour info. Then you can export out of AE as prores 4444 or DNXHD and keep it at least 12bit.
I've read that for better upscale results we shoud use 4:4:4 format (as pretty much obvious since we have more unique pixels). So what is the best encoder to use for this? Let's say we need to keep 14 bit and 4:4:4 subsampling at the same time?
Is it posible to export a low rez proxy out of After Effects (from the DNGs) into FCP or Premiere, edit and then relink to the DNGs back in AE and export a high rez final master from AE? Basically and offline/online workflow?
Quote from: paulforte on June 16, 2013, 06:37:38 PM
Is it posible to export a low rez proxy out of After Effects (from the DNGs) into FCP or Premiere, edit and then relink to the DNGs back in AE and export a high rez final master from AE? Basically and offline/online workflow?
Of course. It will work the in the same way as any AE proxy does. Just scale the proxy size if you want to keep color depth.
Quote from: KahL on June 16, 2013, 04:48:14 PM
I know we've all gotten used to it by now but, I'm madly in love w/ the 50D's new-found digital cinema capabilities thanks to you guys here.
I alternately swap between RAWanizer DNxHD export and Lightroom export depending on how much latitude I want. Here's one workflow I've used for the commercial spot we're shooting:
1. DNG to Lightroom (specifically to save latitude)
2. export upscale to 1920px horizontally at 100% JPEG quality
3. edit in Premiere CS6 (JPG frame sequence)
4. export as DPX LOG frame
5. color in AE CS6 (combination of adding a specific LUT base, then grading in curves, sharpening and adding 35mm grain scan)
(http://farm8.staticflickr.com/7449/9058788202_f6e95c2962_h.jpg)
Man, you do color corr to 8-bit picture. Why bother with RAW then? )
Quote from: Andy600 on June 16, 2013, 05:05:21 PM
So you are exporting to JPEG first? Surely you are losing all that nice color information ???
You would think I would be, but from my tests in AE using 32bit channels, there is virtually zero difference.
Before I settled on JPEGs as a workable file, I tested the DNG files, TIFFs and JPEGs on the same timeline in AE to see the color differences. I didn't notice any discernible difference between the three whatsoever. Of course the TIFF and JPEG files become baked-in, so it's the DNG's flexibility that is a main advantage. Beyond that point, there were virtually similar. Though I'm sure there are some differences that I don't see so far.
Is it possible that Lightroom's JPG settings are of a higher quality? I'm going purely off of what my eye sees at this point, of course.
Quote from: arrinkiiii on June 16, 2013, 05:52:32 PM
Thanks for the workflow! The pic's look very good. Wend can we see the final work?
I have some questions,
-why export in DPX Log?
-what is this espcific Lut base?
Hope to see the final output. Good work =D
I normally export in DPX for color work because of the color density the frames provide. Even if doing this from a lower quality source (such as DSLR h.264 footage), it produces higher flexibility similar to that of RAW.
The oddity right now is that LR's JPEGs appear to be giving me similar density and flexibility as the .DNGs sources when coloring. RAW does however provide the absolute BEST source negative out-of-camera and unlike JPEG or DPX, none of the information is baked in (which is why you can recover highlight information). I may just be exporting in DPX out of habit at this point, but in DPX LOG, it allows me to utilize a proper LUT before color grading.
For a LUT base, I use a few that I've created in Resolve or a Kodak one.
@ kahl
In my opinion your workflow is something like the basic "telecine" concept from commercials
Colorisation was done BEFORE editing...
For the new generation of "digital cinematographers" this concept "telecine" is maybe stupid but is used even today
However, 99 percentage of our work is in 8 bit teritory
The raw files from Canon DSRL raw are like kodak or Fuji frames in my analogy
If I'm wrong please correct me...
So I checked out video modes and it doesn't want to take 24FPS or different display modes.. Seems to be hard coded for either 640 x 480 or 1080P.
There are several spots for frame rate and gop, I'm looking for those.
Found shutter frequency for fps, ae value, shutter timer, frame aperture/shutter/etc
Still working on beep.
also hunting for flush rate, found slice already... getting same 70MB/s max out of the module... I think we can gain some write speed if the edmacs get killed correctly, right now they are not.
Quote from: KahL on June 16, 2013, 07:01:03 PM
I normally export in DPX for color work because of the color density the frames provide. Even if doing this from a lower quality source (such as DSLR h.264 footage), it produces higher flexibility similar to that of RAW.
The oddity right now is that LR's JPEGs appear to be giving me similar density and flexibility as the .DNGs sources when coloring. RAW does however provide the absolute BEST source negative out-of-camera and unlike JPEG or DPX, none of the information is baked in (which is why you can recover highlight information). I may just be exporting in DPX out of habit at this point, but in DPX LOG, it allows me to utilize a proper LUT before color grading.
For a LUT base, I use a few that I've created in Resolve or a Kodak one.
Thank you for the information. Never use DPX LOG or any LUT's but I will investigate more. Wood be nice an video tutorial of the workflow...
Do you know were I can get this LUT's base from Kodak to trie out?
Quote from: 1% on June 16, 2013, 09:20:25 PM
So I checked out video modes and it doesn't want to take 24FPS or different display modes.. Seems to be hard coded for either 640 x 480 or 1080P.
There are several spots for frame rate and gop, I'm looking for those.
Found shutter frequency for fps, ae value, shutter timer, frame aperture/shutter/etc
Still working on beep.
also hunting for flush rate, found slice already... getting same 70MB/s max out of the module... I think we can gain some write speed if the edmacs get killed correctly, right now they are not.
Good news
Quote from: menoc on June 16, 2013, 06:05:00 PM
For those of you who are new to Magic Lantern and are not very adept at the command line, here's a tutorial on how to merge ML RAW files without having to use the command line. This tutorial was created for the Mac, but it will also work in Windows. You'll need a hex editor and of course, a DNG extractor Utility like raw2dng, RAWMagic or raw2cdng.
HEX EDITORS:
Hex Fiend Hex editor for Macintosh
http://ridiculousfish.com/hexfiend/ (http://ridiculousfish.com/hexfiend/)
HxD Hex editor for Windows
http://mh-nexus.de/en/hxd/ (http://mh-nexus.de/en/hxd/)
RAW UTILITY:
RAWMagic
http://www.mediafire.com/download/ht3ydb4s254ka5z/RAWMagic-beta7a.dmg (http://www.mediafire.com/download/ht3ydb4s254ka5z/RAWMagic-beta7a.dmg)
raw2dng
http://www.magiclantern.fm/forum/index.php?topic=5404.0 (http://www.magiclantern.fm/forum/index.php?topic=5404.0)
I just bundled a windows and os X executable of a python script I wrote to concatenate spanned raw files. It takes all XXXXXX.RAW files in a directory for which there are also XXXXXX.R00 files and then looks for any .R01, .R02, etc with the same name and then cat's them together into a XXXXXXX_merged.RAW file in the same directory. And provides minimal command line output so you know it's working.
It's pretty simple and uses the OS specific copyfile command. I havent' run into any problems but PM me if anyone does.
The mac file will need to be run with admin privileges ("~$sudo [directory-to-executable]/ML_RAW_cat.command") to work.
https://dl.dropboxusercontent.com/u/22921777/ML_RAW_cat.rar
Quote from: arrinkiiii on June 16, 2013, 09:38:01 PM
Do you know were I can get this LUT's base from Kodak to trie out?
http://juanmelara.com.au/print-film-emulation-luts-for-download/
http://www.arri.de/camera/digital_cameras/tools/lut_generator/lut_generator.html
What kind of video card should around 100-200 usd would be enough to run resolve properly? 18-20 fps is enough for me.
Quote from: simulacro on June 16, 2013, 11:56:08 PM
http://juanmelara.com.au/print-film-emulation-luts-for-download/
Thanks Simulacro =D
Quote from: pbr on June 16, 2013, 09:39:45 PM
I just bundled a windows executable of a python script I wrote to concatenate spanned raw files. It takes all XXXXXX.RAW files in a directory for which there are also XXXXXX.R00 files and then looks for any .R01, .R02, etc with the same name and then cat's them together into a XXXXXXX_merged.RAW file in the same directory. And provides minimal command line output so you know it's working.
It's pretty simple and uses the windows OS copyfile command. I havent' run into any problems but PM me if anyone does.
https://dl.dropboxusercontent.com/u/22921777/ML_RAW_cat.rar
Great. Is there something like it for the OS X?
Quote from: johansugarev on June 17, 2013, 12:34:45 AM
What kind of video card should around 100-200 usd would be enough to run resolve properly? 18-20 fps is enough for me.
Windows? In that case only Nvidia works (Resolve 10 will support AMD later this year).
More memory is better, but also the speed of the memory is important. Frame-rate really depends on the amount of nodes etc.
Don't know about prices in dollar, but within your budget, a GeForce GTX 650Ti Boost is probably the best you can get. Get one with 2GB and a 192 bits bus (the Boost version). 192 bits means more bandwidth for your memory. Those cards are around €150 here.
forking the new build posts to another thread to make it easier for developers to follow technical issues and bug reports.
for known issues with recent builds of the 50D we have:
- crop mode (zoom mode) - framing problems
- crop mode - pink cast to the view.
- HDMI out - are the issues different on 50D from on other cameras 50D bug report http://www.magiclantern.fm/forum/index.php?topic=6471.0 and 5D3 http://www.magiclantern.fm/forum/index.php?topic=6302.msg48407#msg48407
are there other issues which should be on a 50D bug list?
please keep using this current thread for general 40D and 50D raw video questions and discussions.
if you have identified specific issues with a build report them to the 50D build thread:
http://www.magiclantern.fm/forum/index.php?topic=6554
Quote from: menoc on June 17, 2013, 01:43:27 AM
Great. Is there something like it for the OS X?
I just made and added a .command executable of the same name to the linked rar. I tried on one archive on my mac, it made the merged file but I didn't verify further than that. Should be fine. You'll need to run the file with "sudo [dir path]/ML_RAW_cat.command" (or however you can activate administrator privileges from finder -- I couldn't figure it out. ).
Missing front develop 3 state.
I found the functions that are needed for raw histogram in photo but no state... I see a couple of candidates to try
here: http://a1ex.bitbucket.org/ML/states/50D-alt/sm37.htm
but it seems like those are updated with 109 fw and state list is wrong
front state is *0x3750 maybe just need to try it like 5d2.. also there is a 374c and it looks like a stateobj object in memory but I can't find where its initialized.
also force left produces garbage for me in all modes (at least in preview) and edmacs aren't dying when resized... maybe related to constant drawing by canon.. have to poke around the timers and see what makes it keep refreshing.
killing the edmacs will increase write speed as when messing around I got higher speeds for a little while when trying to "hack" them.
Both front states didn't work. Need to find the actual transitions instead of shooting in the dark :)
Quote from: 1% on June 16, 2013, 09:20:25 PM
So I checked out video modes and it doesn't want to take 24FPS or different display modes.. Seems to be hard coded for either 640 x 480 or 1080P.
There are several spots for frame rate and gop, I'm looking for those.
Found shutter frequency for fps, ae value, shutter timer, frame aperture/shutter/etc
Still working on beep.
also hunting for flush rate, found slice already... getting same 70MB/s max out of the module... I think we can gain some write speed if the edmacs get killed correctly, right now they are not.
Great Job.. can't believe we can squeeze more than 70mb/s
Quote from: rawmania on June 16, 2013, 08:14:06 PM
@ kahl
In my opinion your workflow is something like the basic "telecine" concept from commercials
Colorisation was done BEFORE editing...
For the new generation of "digital cinematographers" this concept "telecine" is maybe stupid but is used even today
However, 99 percentage of our work is in 8 bit teritory
The raw files from Canon DSRL raw are like kodak or Fuji frames in my analogy
If I'm wrong please correct me...
This is true. I could've used the the proxy round trip method from PPRO to AE, but it's much too tedious and over complicated to me. I find doing it this way is much simpler and straight forward for the most part and if I'm REALLY concerned w/ the bits rather than what I can see (using the JPEG workflow, for example), I can always render my DNGs to DNxHD RGB and then back out to DPX for color.
Quote from: Andy600 on June 16, 2013, 10:37:00 AM
BTW the best sharpening and upscaling method I have found is to work in Davinci Resolve Lite (FREE). I can't get Premier Pro or After Effects anywhere near the same quality without artifacts. See this: http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg50829#msg50829)
In AE can't you duplicate the layer, add your sharpen effect of choice, and change the transfer mode to luminance? That'll get rid of color fringing. Or you could apply your sharpen effect to the layer then use CC Composite and change Composite Original to Color; then just create a preset for luma sharpen.
Is there a mode (resolution ?) who can limit the moire and aliasing on a 50D ? I've seen some tests footage around and it seems that there is no moire and aliasing.
I search on the forum but I did not find any answer to this question. What you mean by crop mode ? I check also about anamorphic recording but is it made by an anamorphic lens or by software ?
Actually I've made a lot of test at 1280x720. Then I use raw2dng, import the raw on After Effect (I print the frame number and the file name on the output do process like the old 16mm way before 'negative conformation'). The result is very good except the moire and aliasing.
Very impressive job on a 50D !
Another 50D RAW video test. This time in B&W.
Shot with 12Jun GregoryOf Manhattan build. I love the possibility to choose different aspect ratio for filming. Thanks to all involve in the development. Vimeo does not show the video in the original aspect ratio, they included it in a 16:9 canvas. >:(
Quote from: 1% on June 17, 2013, 04:03:37 AM
Missing front develop 3 state.
I found the functions that are needed for raw histogram in photo but no state... I see a couple of candidates to try
here: http://a1ex.bitbucket.io/ML/states/50D-alt/sm37.htm
but it seems like those are updated with 109 fw and state list is wrong
front state is *0x3750 maybe just need to try it like 5d2.. also there is a 374c and it looks like a stateobj object in memory but I can't find where its initialized.
also force left produces garbage for me in all modes (at least in preview) and edmacs aren't dying when resized... maybe related to constant drawing by canon.. have to poke around the timers and see what makes it keep refreshing.
killing the edmacs will increase write speed as when messing around I got higher speeds for a little while when trying to "hack" them.
Both front states didn't work. Need to find the actual transitions instead of shooting in the dark :)
Is this something I can help with? I'll need to know what to look for and how to look for it.
I think I need to figure out how to redo state diagrams.
http://charlottesville.craigslist.org/pho/3876250683.html
If any of you live near Charlottesville, VA. I'm not willing to drive the 2 hours to buy it!
But if you were, $350 is on the cheap from what I have seen.
Hey Andy600 I'm trying out your latest build, I'm liking the new *5 preview mode with good colors, however exposure overide seems to have issues, it's locked at iso 3200 again and I can't change it, and with exposure overide disabled it's stuck at iso 100. Also, exposure simulation does not seem to work for me.
Edit : Went back to your 14 june build, seems stable enought! I hope you can get the grayscale crop mode preview working stable!
Quote from: bzhwindtalker on June 17, 2013, 09:39:11 PM
Hey Andy600 I'm trying out your latest build, I'm liking the new *5 preview mode with good colors, however exposure overide seems to have issues, it's locked at iso 3200 again and I can't change it, and with exposure overide disabled it's stuck at iso 100. Also, exposure simulation does not seem to work for me.
Edit : Went back to your 14 june build, seems stable enought! I hope you can get the grayscale crop mode preview working stable!
Yep, that's why it says ETTR broken in the name of the zip ;) I'm going back through the changes to find where it began to go wrong. Have you tried Gregory's latest? Same issues?
I just filmed another short test trying to see how do the skin tones look like in RAW, I might add they're pretty good :)
The only thing I will add is that YT compresses the hell out of the footage, the original ProRes422 file is damn sharp (just a touch of sharpening in CRaw in AE), even the compressed file (h264 15~20Mbps) looks a lot sharper than this, but on YT it looks all mushy.
I'm getting weird results in Resolve.
Colored lines around the frame and a 1px black border.
Looks like this:
(http://www.eoshd.com/comments/uploads/gallery/album_64/gallery_20742_64_79575.jpg)
Framegrab from exported h264 file at 300% + curves to make it more clear.
The CDNG file is fine (converted with raw2cdng.1.1.6) if I open it in Photoshop so must be a setting in Resolve somewhere I suppose.
Anyone seen this before? What could it be?
Quote from: JulianH on June 17, 2013, 11:33:47 PM
I'm getting weird results in Resolve.
Colored lines around the frame and a 1px black border.
The CDNG file is fine (converted with raw2cdng.1.1.6) if I open it in Photoshop so must be a setting in Resolve somewhere I suppose.
Anyone seen this before? What could it be?
Yeah I've seen the same thing, it is a blueish colour on mine. I think it must be how Resolve is interpreting the DNG's. What do you use to extract DNG's from the ML RAW files?
Good to know I'm not the only one...
It's blue on one side, orange-ish on the other side. Barely visible with BMD Lut, but really annoying in the final result.
I'm using raw2cdng.1.1.6. That's the only option I think.. (Windows).
Hmm.. well might want to add the *frame_* stuff to your consts... I don't seem to be having any problem with it locked on iso 3200, it won't even go there, stops at 1600.
I'm not getting this issue in Resolve. Have you set input or output scaling to fill the frame?
Frame consts are only used on new cameras (those that can do HDR video with shutter timer). The old ones use the slow method, which only change settings via properties or expo override. If expo override is enabled, ETTR acts like in M mode, so it should use auto_ettr_work_m (check if this actually happens).
I also can't get it to go to ISO 3200, does it go there even if you start at say ISO 200? ISO is limited to 100-1600 on this line:
int isor = COERCE((iso + 4) / 8 * 8, MIN_ISO, max_auto_iso);
(on new cameras it goes to the value from Canon menu, but 50D doesn't have it, so it defaults to 1600).
Quote from: Andy600 on June 18, 2013, 12:18:00 AM
I'm not getting this issue in Resolve. Have you set input or output scaling to fill the frame?
Yeah. Tried different options. But I also get it when I make a project with the exact pixel size...
Quote from: JulianH on June 17, 2013, 11:57:57 PM
Good to know I'm not the only one...
It's blue on one side, orange-ish on the other side. Barely visible with BMD Lut, but really annoying in the final result.
I'm using raw2cdng.1.1.6. That's the only option I think.. (Windows).
I've just done another test, I'm not getting the issue when using RAWMagic on the Mac. It was only happening when using Raw2dng.
Removed post. Bug is fixed :)
see: http://www.magiclantern.fm/forum/index.php?topic=6554.msg52318#msg52318
I dunno whats up with this since its working for me like it works for a1ex.
QuoteFrame consts are only used on new cameras (those that can do HDR video with shutter timer). The old ones use the slow method, which only change settings via properties or expo override.
I found them all (there are 2 sets, both match, the 2nd iso stops at analog tho), bv seems slightly different than the formula. Is it different on 5D2?
Why can't we use shutter timer? I have it found.
Can anyone tell me when I boot up my camera, I get a scripts "dir missing" message, everything seems to work properly though.
Hokie123, I get the same error after I've formatted the card in the camera (ML reinstalls after the in camera format if you followed all the steps found throughout this forum in preparing the CF card.) I might be wrong, but the simple fix is to drop in a scripts empty folder in the ML directory.
I haven't noticed any issues by having the error to date.
Quote from: Nachelsoul on June 17, 2013, 12:06:02 PM
Another 50D RAW video test. This time in B&W.
Shot with 12Jun GregoryOf Manhattan build. I love the possibility to choose different aspect ratio for filming. Thanks to all involve in the development. Vimeo does not show the video in the original aspect ratio, they included it in a 16:9 canvas. >:(
Great job man.. loving the look 50D is looking more like a champ daily. Yeah Vimeo I think only does 16:9 aspect ratio.
Quote from: BokiA on June 17, 2013, 11:07:50 PM
I just filmed another short test trying to see how do the skin tones look like in RAW, I might add they're pretty good :)
The only thing I will add is that YT compresses the hell out of the footage, the original ProRes422 file is damn sharp (just a touch of sharpening in CRaw in AE), even the compressed file (h264 15~20Mbps) looks a lot sharper than this, but on YT it looks all mushy.
Great video I think the video is sharp enough, too sharp it would start looking too Videoish...
Quote from: goldenchild9to5 on June 18, 2013, 03:42:55 AM
Yeah Vimeo I think only does 16:9 aspect ratio.
Hey just to clarify aspect ratio on Vimeo:
"Can I upload a video with any aspect ratio I want?
Vimeo does its best to accommodate any aspect ratio that you upload. However, there is no guarantee your video will look correct or play properly if you upload an unusual aspect ratio."
Here is one I uploaded at 1:2.35 without back borders (it has no boarders on vimeo and is correct aspect at full screen. It is actting differently here thoguh). Its not the 50D and not raw- its 7D h.264! - hope no one is upset by that!
EDIT: removed "s" from video link to allow embedding.
Quote from: JulianH on May 25, 2013, 05:39:59 PM
Managed to trade my old 5D for the 50D and cash :)
I am new to ML. Just want to know can u record in desired resolution in ml? or it is having some presets for recording resolutions. Can you record raw in 960x540 (60/30/25/24/23.9p) with high quality ?
Why because as I have seen when we resize image by double it looks better then scaling it disproportional.
you can check this concept with images. I don't know i it same in case of videos. The whole idea is if anyhow we are scaling it because of limitations. why not try low res. high quality video and do other things in post mostly scaling in proportional way.
Quote from: icemagic on June 18, 2013, 11:17:34 AM
I am new to ML. Just want to know can u record in desired resolution in ml? or it is having some presets for recording resolutions. Can you record raw in 960x540 (60/30/25/24/23.9p) with high quality ?
Why because as I have seen when we resize image by double it looks better then scaling it disproportional.
you can check this concept with images. I don't know i it same in case of videos. The whole idea is if anyhow we are scaling it because of limitations. why not try low res. high quality video and do other things in post mostly scaling in proportional way.
You can record 960x540 (16:9) at maximum of 30p if you really want to. Higher frame rates are not possible atm.
For the latest 50D builds and for bug reporting ONLY, please see this post: http://www.magiclantern.fm/forum/index.php?topic=6554.0
We will keep this post for general 50D raw video discussion.
Quote from: icemagic on June 18, 2013, 11:17:34 AM
I am new to ML. Just want to know can u record in desired resolution in ml? or it is having some presets for recording resolutions. Can you record raw in 960x540 (60/30/25/24/23.9p) with high quality ?
Why because as I have seen when we resize image by double it looks better then scaling it disproportional.
you can check this concept with images. I don't know i it same in case of videos. The whole idea is if anyhow we are scaling it because of limitations. why not try low res. high quality video and do other things in post mostly scaling in proportional way.
I get your point, but I doesn't work like that. More important with downscaling I think.
Try it out yourself, take a random image, resize it to 1584x892 and save. Resize to 960x540 and save as copy. Now open both files and resize to 1920x1080...
Quote from: 1% on June 18, 2013, 12:01:03 AM
Hmm.. well might want to add the *frame_* stuff to your consts... I don't seem to be having any problem with it locked on iso 3200, it won't even go there, stops at 1600.
Added your Frame stuff to consts.h :)
Hi! What do you think about Sandisk Extreme 400X 60 MB/s? Who used it? Will it handle 1592×840 24p in 50D?
Quote from: JulianH on June 18, 2013, 01:37:13 PM
resize it to 1584x892 and save. Resize to 960x540 and save as copy. Now open both files and resize to 1920x1080...
As I know Going from 960x540 to 1920x1080 will give better result then Going from 1584x892 to 960x540 and again to 1920x1080. And 1584x892 => 1920x1080 may look different then 960x540 => 1920x1080 but if too much of movement is there then (I think ) 960x540 => 1920x1080 will give better result. Because no matter which interpolation algorithm you use to re-size the video it will just do math. And for computer it is tough to guess which pixel to keep and which pixel to remove (in case of disproportional re-sizing). I will just do a re-sizing and send the images. ::) .
Quote from: galaxy on June 18, 2013, 03:02:41 PM
Hi! What do you think about Sandisk Extreme 400X 60 MB/s? Who used it? Will it handle 1592×840 24p in 50D?
If you're looking to buy it I suggest getting the Transcend 600x 16,32 or 64gb which is cheaper and works. I have the 16gb and 1584x950 is no problem. Writes up to 65MB/s.
Alternatively get the Komputerbay 64gb card which is good value for money, even though mine was DOA. Ordered another.
Quote from: JulianH on June 18, 2013, 01:37:13 PM
I get your point,
Just checked. Your work flow is better . Because with image it is not possible to check this.
Only a video will help, which is having same field in both the resolutions. Then only we can compare.
Quote from: Andy600 on June 18, 2013, 03:15:09 PM
If you're looking to buy it I suggest getting the Transcend 600x 16,32 or 64gb which is cheaper and works. I have the 16gb and 1584x950 is no problem. Writes up to 65MB/s.
Alternatively get the Komputerbay 64gb card which is good value for money, even though mine was DOA. Ordered another.
Thanks for the tip! I think, Transcend 600x 16GB is a good choice. What about Transcend 1000x, it's supposed to be faster, but as i know, 50D doesn't support UDMA7 and the real speed would not be so fast?
Quote from: galaxy on June 18, 2013, 04:25:44 PM
Thanks for the tip! I think, Transcend 600x 16GB is a good choice. What about Transcend 1000x, it's supposed to be faster, but as i know, 50D doesn't support UDMA7 and the real speed would not be so fast?
The 600x card is UDMA7 too. The 50d supports up to UDMA6 so obviously you lose some speed benefits of UDMA7 but it's better to have a faster card than a card that is hitting it's limits.
Re: 1000x transcend. There was some debate on this a few pages ago. On the Transcend website (when you compare 2 cards) it states that the 600x 16gb card (max 90MB/s write) is faster than the 1000x 16gb card (max 70MB/s write) but the 32gb and 64gb 1000x versions are much faster. I haven't tested but I wouldn't risk getting a 1000x 16gb card just to try when the 600x 16gb card works well.
Quote from: Andy600 on June 18, 2013, 04:32:24 PM
The 600x card is UDMA7 too. The 50d supports up to UDMA6 so obviously you lose some speed benefits of UDMA7 but it's better to have a faster card than a card that is hitting it's limits.
Re: 1000x transcend. There was some debate on this a few pages ago. On the Transcend website (when you compare 2 cards) it states that the 600x 16gb card (max 90MB/s write) is faster than the 1000x 16gb card (max 70MB/s write) but the 32gb and 64gb 1000x versions are much faster. I haven't tested but I wouldn't risk getting a 1000x 16gb card just to try when the 600x 16gb card works well.
Thank you for advices, really help! I'm getting Transcend 600x 16gb!
Anyone tried Kingston Ultimate 600x 32GB ? The claim is it is 90MB/s write speed, the real life performance is more like 76 MB/s (http://www.gavtrain.com/?p=1831). I wonder how does it fair on 50D? It is on sale now here in Canada (Canada Computers, 60$).
Also - any more information regarding audio support in 50D on a hardware level? I saw it discussed here on page 50, with the statement that 50D seems to have the audio chip. If there is a way to simply solder in an audio in connector (to be used e.g. with Zoom H1 recorder) that would be super sweet.
Quote from: icemagic on June 18, 2013, 04:08:19 PM
Just checked. Your work flow is better . Because with image it is not possible to check this.
Only a video will help, which is having same field in both the resolutions. Then only we can compare.
I don't think it will be any different with video. It would be easy to try, but I'm not going to do it (sorry). I just don't believe that upscaling something 200% will look better than upscaling something 50%. There is just a lot more detail if you shoot at the highest possible resolution. You're not magically getting that detail back by a 200% upscale.
Quote from: pulsar124 on June 18, 2013, 04:52:02 PM
If there is a way to simply solder in an audio in connector (to be used e.g. with Zoom H1 recorder) that would be super sweet.
Even if that is possible it still has to be implemented in the software...
Quote from: pulsar124 on June 18, 2013, 04:52:02 PM
Anyone tried Kingston Ultimate 600x 32GB ? The claim is it is 90MB/s write speed, the real life performance is more like 76 MB/s (http://www.gavtrain.com/?p=1831). I wonder how does it fair on 50D? It is on sale now here in Canada (Canada Computers, 60$).
Also - any more information regarding audio support in 50D on a hardware level? I saw it discussed here on page 50, with the statement that 50D seems to have the audio chip. If there is a way to simply solder in an audio in connector (to be used e.g. with Zoom H1 recorder) that would be super sweet.
There is no audio chip inside the 50D.
Quote from: 1% on June 11, 2013, 02:51:05 PM
Audio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
720P encoder mode is in there too but not sure if the video mode works... will have to try in C mode.
Don't be fooled by the FW because the 50D has got no audio chip, i pulled it apart until the motherboard and there is no sign of any audio processing stuff.
I know that the FW says you should have an Asahi Kasei chip but i still have my pics uploaded on the CHDK forum and you can clearly see there is nothing useful onboard.
http://chdk.setepontos.com/index.php?topic=6161.180
Yea, I don't see one either... maybe can be made to beep through tx19a somehow. Something generates audio to that speaker.
I guess so but since it's not coming through the audio chip itself is going to be much harder, i guess.
The 5DII had to be Canon's first Video DSLR; the 50D would have sold a lot more in comparison to the former if it had all the feature they wanted to put into it maybe in the first stages of its development.
The FW is ready for the chip, the body too. Only the motherboard is missing the most important bit.
Maybe there is a function like beep_it or something... would be better than no beep at all. I'll have to look. Sucks though, didn't know they didn't include the chip.
My 50D is fairly old in terms of production batch so there is no chance newer ones have it instead.
Also, i see no room for it either on the board.
Quote from: 1% on June 18, 2013, 05:47:38 PM
Maybe there is a function like beep_it or something... would be better than no beep at all. I'll have to look. Sucks though, didn't know they didn't include the chip.
Well something beeps when my chipped K-mount adapter confirms focus ::)
I was probably confused by the statement from 1% on page 50:
QuoteAudio stuff is all in there.. mic is not hooked up.. audio is ak4646. I was going to make it beep next... but battery died. i'll have to use AA's.
So does 50D have ak4646? Form the chip description:
QuoteThe AK4646 features a stereo CODEC with a built-in Microphone-Amplifier and Speaker-Amplifier. Input circuits include a Microphone-Amplifier and an ALC (Auto Level Control) circuit, and Output circuits include a Speaker-Amplifier.
Quote from: Andy600 on June 18, 2013, 05:49:48 PM
Well something beeps when my chipped K-mount adapter confirms focus ::)
Even an old 20D would beep and i am very sure it has got nothing that can record audio in it.
The FW has got references to the AK4646 but there is nothing on the hardware side that barely resembles such chip.
That's it.
The way i look at it is that 50D and 5DII were meant to be very close except for the sensor size and then somebody in the marketing department thought it was better to differentiate the products a bit, just so that the 5DII could have that something that would attract users towards its purchase.
If you consider the write speed the 50D is capable of you will start to understand what i am talking about, even though it is just MY opinion.
Quote from: ilguercio on June 18, 2013, 05:54:55 PM
Even an old 20D would beep and i am very sure it has got nothing that can record audio in it.
The FW has got references to the AK4646 but there is nothing on the hardware side that barely resembles such chip.
That's it.
The way i look at it is that 50D and 5DII were meant to be very close except for the sensor size and then somebody in the marketing department thought it was better to differentiate the products a bit, just so that the 5DII could have that something that would attract users towards its purchase.
If you consider the write speed the 50D is capable of you will start to understand what i am talking about, even though it is just MY opinion.
I think bar the sensor size and audio the 50 and 5d2 are pretty much the same. I was hinting at maybe using the focus confirmation beep for sync but I doubt it's loud enough.
QuoteSo does 50D have ak4646? Form the chip description:
In firmware yes, from the pictures no.
@1% - Just enabled display filters. It seems to be doing something. Anamorphic de-squeeze is flickering and it does bend the image. Is it just a sync issue or more complicated?
Also, trying to figure out why H.264 movie logging isn't working ???
You need to add display filter sync for 50D.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/21977f4ab173d551a7bf6f6abdbd1700e3c5f5e7
Quote from: 1% on June 18, 2013, 06:08:21 PM
You need to add display filter sync for 50D.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/21977f4ab173d551a7bf6f6abdbd1700e3c5f5e7
Cool :) Thanks. I was on the right track by the looks of things except for the
hard coding bit ;D
Quote from: Andy600 on June 18, 2013, 02:14:54 PM
Added your Frame stuff to consts.h :)
Thanks for all the amazing work everyone. Really glad I picked one of these off Craigslist for cheap last week. (All the prices now are upwards of $700 for body only.)
Running Andy's build from today with 5x crop centering
https://bitbucket.org/andy600/andy50d/downloads/Andy600ML_June18th_50D.109.d55f33a1d395_Snap_to_5x_center.zip
ETTR is running smoothly, but I am still getting max ISO at 1600 for ETTR. I have expanded ISO enabled in the Cannon menu. Is there another setting I have toggled that is interfering? Was this edit to consts.h what was supposed to fix ISO 100-1600?
There's no point in going above ISO 1600 on DIGIC IV.
http://www.guillermoluijk.com/article/isos5dmkii/index.htm
Quote from: dsManning on June 18, 2013, 06:35:43 PM
Thanks for all the amazing work everyone. Really glad I picked one of these off Craigslist for cheap last week. (All the prices now are upwards of $700 for body only.)
Running Andy's build from today with 5x crop centering
https://bitbucket.org/andy600/andy50d/downloads/Andy600ML_June18th_50D.109.d55f33a1d395_Snap_to_5x_center.zip
ETTR is running smoothly, but I am still getting max ISO at 1600 for ETTR. I have expanded ISO enabled in the Cannon menu. Is there another setting I have toggled that is interfering? Was this edit to consts.h what was supposed to fix ISO 100-1600?
No it's not you, it's supposed to happen with this build. the 50d is missing something and defaults to ISO1600. It's still development code don't forget ;)
The consts thing was something else. I'm just cherry-picking a few features that the real devs are working on.
Thanks! Quick replies and so very informative. Great thread and development you have got going here. Learning so much :)
Quote from: a1ex on June 18, 2013, 06:38:18 PM
There's no point in going above ISO 1600 on DIGIC IV.
http://www.guillermoluijk.com/article/isos5dmkii/index.htm (http://www.guillermoluijk.com/article/isos5dmkii/index.htm)
Noise isn't so ugly at 3200 with raw video. If you use chroma noise reduction it actually looks like film grain. This shot has no NR
[spoiler]
(http://i.imgbox.com/acv82gmr.jpg)[/spoiler]
Could anyone please give me a link to the description of how RAW is done under Magic Lantern?
Specifically, it is not clear to me what is the 14 bit color. My understanding is that for some video modes the whole sensor is used. The sensor itself is 14 bit per pixel + Bayer matrix to get proper colors by interpolation. To make 1080p video from the whole sensor, one has to bin multiple pixels. What is binned by ML - the raw pixel values (before demosaicing)? Perhaps separately for the pixels of each color (R/G/B)? And what is the RAW video format: is it 14 bit per pixel, and has to be demosaiced? Meaning the color resolution is pretty poor?
Thanks.
Why would that make the color resolution pure?
14 bit raw video is just like a 14 bit raw photo, only you get less pixels per frame. That doesn't have anything to do with the data that is in the pixels.
Hi Andy.
So Transcend x600 will allow full 50D Resolution for, let's say 1 min non-stop for sure? I'm also looking into buying one.
Thanks for your info!
Quote from: Andy600 on June 18, 2013, 03:15:09 PM
If you're looking to buy it I suggest getting the Transcend 600x 16,32 or 64gb which is cheaper and works. I have the 16gb and 1584x950 is no problem. Writes up to 65MB/s.
Alternatively get the Komputerbay 64gb card which is good value for money, even though mine was DOA. Ordered another.
Quote from: rommex on June 18, 2013, 11:02:56 PM
Hi Andy.
So Transcend x600 will allow full 50D Resolution for, let's say 1 min non-stop for sure? I'm also looking into buying one.
Thanks for your info!
It depends what you mean by 'full resolution'. If you mean maximum settings then no, you can't. But it you want to record footage scalable nicely to 1080p you can get continual shooting :)
FYI I get 1584x892 (16:9) continuous and 1584x950 (5:3) for a couple of mins at 25p with write speeds up to 65MB/s. (yes 25p :) )
My first real test oudoor with my new 50D.
Shot at 1584x892, graded in AE with ACR, scaled up to 1920; scaled down to 1280 because vimeo won't let me upload a file bigger than 5gb.
Used the cheap Canon 50mm 1.8f; looking at the footage, makes me realize the importance of image stabilization, which this lens obviously doesn't have.
Quote from: Andy600 on June 18, 2013, 11:34:34 PM
...
FYI I get 1584x892 (16:9) continuous and 1584x950 (5:3) for a couple of mins at 25p with write speeds up to 65MB/s. (yes 25p :) )
That settles then. THNX!!
Quote from: briwil on June 18, 2013, 11:38:21 PM
My first real test oudoor with my new 50D.
Shot at 1584x892, graded in AE with ACR, scaled up to 1920; scaled down to 1280 because vimeo won't let me upload a file bigger than 5gb.
Used the cheap Canon 50mm 1.8f; looking at the footage, makes me realize the importance of image stabilization, which this lens obviously doesn't have.
Yep, I almost got seasick by the end ;D ;D
Quote from: rommex on June 18, 2013, 11:51:46 PM
Yep, I almost got seasick by the end ;D ;D
Can anyone tell me, would a lens with Image stabilization help much?
And what is this stuttering effect on panning shots, is that a result of FPS override dropping frames, or something else?
Quote from: briwil on June 19, 2013, 12:04:42 AM
Can anyone tell me, would a lens with Image stabilization help much?
And what is this stuttering effect on panning shots, is that a result of FPS override dropping frames, or something else?
Well lens stabilization isn't going to help you while walking around with the camera in your hands, specially not at 50mm on 1.6x crop.
The stutter might come from importing your 24fps secuence as a 30fps material but having a 24fps composition. check it out, right click on secuence and click interpret footage, should be at 24fps for a 24fps secuence. Has already been discussed in a lot of posts.
Rolling shutter is not going to go away even with raw (makes no difference). 50mm + shake panning =terrible rolling shutter.
Anyway, that's all basic stuff, nothing to do with RAW.
Quote from: araucaria on June 19, 2013, 01:07:30 AM
Well lens stabilization isn't going to help you while walking around with the camera in your hands, specially not at 50mm on 1.6x crop.
The stutter might come from importing your 24fps secuence as a 30fps material but having a 24fps composition. check it out, right click on secuence and click interpret footage, should be at 24fps for a 24fps secuence. Has already been discussed in a lot of posts.
Rolling shutter is not going to go away even with raw (makes no difference). 50mm + shake panning =terrible rolling shutter.
Anyway, that's all basic stuff, nothing to do with RAW.
Well, I shoot footage handheld all the time with my Nex-6, with an old Canon FD 50mm lens, and the shakiness is nothing like this.
And why wouldn't IS help with handheld footage?
And yes, it has been discussed a lot in other posts; I set my AE preferences for image sequence import to 24p, it was definitely imported correctly.
But you're right, it probably is just rolling shutter and me being too shaky.
hi,
i got my 50D now and i am a little bit disappointed.
first of all: it´s dark outside, so there´s nothing to shoot.
and i got horrible writing speeds!!
i have a komputerbay 32 GB x600 card and can barely top the data rate, that´s possible in the 550d.
to check if there´s something wrong with the komputerbay card i got me a lexar 16 GB x800.... and now:
average write speed 41 MB/s
average read speed 100 MB/s
with komputerbay:
average write speed 26 MB/s
average read speed 63 MB/s
using the W/R benchmark
i use todays build. tryed different aligning settings. btw. if you set the sector sizes the same as the allocation sizes the cam dies.
i had to remove the battery, start the cam with another NON ML card, restart it with an ML card.... and it worked again.
used all the "tricks" ( raw off, noise reduction, global draw off/on...)
but back to my problem. i expected specially with the lexar card a data rate of at least 50-60 MB/s
or is this impossible with such a card?
or am i the problem?
to me it seems, as if write speed/read speed = 1/2
i expected a 2/3 ratio. at least from the x800 card.
i have just a usb 2 card reader
someone any suggestions?
thanks!!
So in a massive spanned clip today (interview) this happened. I didn't notice the buffer fill or anything strange.
What is it?
(http://img42.imageshack.us/img42/7889/6ok1.png) (http://imageshack.us/photo/my-images/42/6ok1.png/)
Uploaded with ImageShack.us (http://imageshack.us)
Quote from: crash-film on June 19, 2013, 03:06:01 AM
i use todays build. tryed different aligning settings. btw. if you set the sector sizes the same as the allocation sizes the cam dies.
Have you tried a different build, like June 11th?
Quote from: crash-film on June 19, 2013, 03:06:01 AM
and i got horrible writing speeds!!
i have a komputerbay 32 GB x600 card and can barely top the data rate, that´s possible in the 550d.
I had the 600x komputerbay and did not get more than 25mo/sec. Now I returned it for the 1000x and get speeds up to 65mo/sec, and i'm not sure this is limited by the card or the current build.
Quote from: briwil on June 19, 2013, 12:04:42 AM
Can anyone tell me, would a lens with Image stabilization help much?
And what is this stuttering effect on panning shots, is that a result of FPS override dropping frames, or something else?
Actually I really like the 18-55 IS or STM kitlens. On a wider angle it's easier to shoot handheld. The IS will help!
Quote from: savale on June 19, 2013, 08:29:54 AM
Actually I really like the 18-55 IS or STM kitlens. On a wider angle it's easier to shoot handheld. The IS will help!
Thank you!
will a 1000x 32GB work with all resolutions?
Appears there are at least a couple of posts stating that the Komputerbay 32GB 1000X is producing high-MB/s recordings. You might try a search.
Here's a sample...
QuoteQuote 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.
« Last Edit: June 15, 2013, 04:45:24 PM by mageye »
Report to moderator Logged
Hey Crash-Film... Got a response to your card write-speed issue.
The math doesn't seem to add up when it comes time to how a card performs... Put a Komputerbay 64GB 1000x in a Canon 5DIII and experience 125MB/s write speeds. Place the same card in the 50D and experience approximately 70MB/s. The difference can be in the EXFAT format and the FAT32 format limitations. In addition to the card's read/write limitations, the camera also has it's read/write limitations. Thus, it's important to find the correct mate, if you will.
The reason why the math isn't really panning out is because the camera is writing data at the very edge of it's capabilities. And since it appears that your card is pushing the edge of it's capabilities, in addition to your camera, you may be dealing with what may be described as a double-negative recording process.
Try searching the ML forum and you might discover that the Lexar Professional 1000X and the Komputerbay 32GB 1000X, and the 64GB 1000X are the cards of choice. I can't write that for sure, of course. Myself, I've primarily been glued to the 50D Raw Recording forum and not so much the 5D II and 5D III. Anyway, the best value is probably 64GB 1000X from Komputerbay.... By the way Komputerbay has been quoted as stating, "We receive/sell/brand Lexar Professional's cards that didn't meet the highest, most stringent quality-control measures."
Aside from that bit of re-assurance in the quality of the Komputerbay, having originated from a high-end compact-flash card manufacturer, I guess we're discovering that the Lexar 800 compactflash card is more of an entry level UDMA 7 rather than a high-end UDMA 7.
You might consider turning off every feature not related to raw_record, and completely clear the screen of excess overlays, in addition, make sure you have all of your Canon menu settings for image & exposure set to disable. These are definite disrupters for maximizing raw_record.
Hang in there and keep up with the posts. See you around.
- Levi
I wonder if there is anti aliaisng filter from other canon models which fits to 50D? Maybe from 7d or 60d? Does anybody knows?
Quote from: Viente on June 19, 2013, 12:36:28 PM
I wonder if there is anti aliaisng filter from other canon models which fits to 50D? Maybe from 7d or 60d? Does anybody knows?
An 7D filter will probably fit but they are made specifically for 18mp sensors. We have a 15mp sensor in the 50d. It would do strange things to the image.
I think maybe some kind of petition will push Mosaic Engineering to develop AA filter for 50D?
Quote from: LEVISDAVIS on June 19, 2013, 10:35:44 AM
Hey Crash-Film... Got a response to your card write-speed issue.
The math doesn't seem to add up when it comes time to how a card performs... Put a Komputerbay 64GB 1000x in a Canon 5DIII and experience 125MB/s write speeds. Place the same card in the 50D and experience approximately 70MB/s. The difference can be in the EXFAT format and the FAT32 format limitations. In addition to the card's read/write limitations, the camera also has it's read/write limitations. Thus, it's important to find the correct mate, if you will.
The reason why the math isn't really panning out is because the camera is writing data at the very edge of it's capabilities. And since it appears that your card is pushing the edge of it's capabilities, in addition to your camera, you may be dealing with what may be described as a double-negative recording process.
Try searching the ML forum and you might discover that the Lexar Professional 1000X and the Komputerbay 32GB 1000X, and the 64GB 1000X are the cards of choice. I can't write that for sure, of course. Myself, I've primarily been glued to the 50D Raw Recording forum and not so much the 5D II and 5D III. Anyway, the best value is probably 64GB 1000X from Komputerbay.... By the way Komputerbay has been quoted as stating, "We receive/sell/brand Lexar Professional's cards that didn't meet the highest, most stringent quality-control measures."
Aside from that bit of re-assurance in the quality of the Komputerbay, having originated from a high-end compact-flash card manufacturer, I guess we're discovering that the Lexar 800 compactflash card is more of an entry level UDMA 7 rather than a high-end UDMA 7.
You might consider turning off every feature not related to raw_record, and completely clear the screen of excess overlays, in addition, make sure you have all of your Canon menu settings for image & exposure set to disable. These are definite disrupters for maximizing raw_record.
Hang in there and keep up with the posts. See you around.
- Levi
thanks levi!
okay, i got 720p raw video.....with the x800 card its absolutely no problem.
that´s all i wanted since i could not get it with my 550D.
i can even get the 14.. x 5.. 1:2.20 (it´s to hot, to grab the camera just for that...) resolution@23,9 fps and the buffer is like <*.....> and idling. just one step greater in vertical resolution and the buffer fills continuously up. so it´s the cards performance for shure.
i think card manufacturers gain their incredible x1000 speeds by creating a card intern raid. ( as in panasonics P2 cards are technically SD-Cards in a raid) also the used memory chips influence the memory bandwith with their inner structure.
so in a 32 GB card may be the doubled infrastructure of a 16 GB card. leading to a theoretically doubled performance.
and so on....
as far as i can remember CF cards where always the fastest cards because of their intern UDMA controller. maybe in some cards (komputerbay) there´s a controller with two "lanes" each with a memory interface that matches the 16GB modules. so in the 16 GB card there´s just one "lane" used. in the 32 GB card both of them are used. and in the 64 GB card a controler optimized for four 16 GB modules (or two 32 GB modules) is used. and this controler is also used in the 128 GB but organized in a way that´s good enough for marketing but technically not perfect. this explains the different performances of differently sized cards.
i know there´re no 16 GB modules and so on and memory is organized and transferred in bits.
but i hope i could explain my thoughts about this as plain as possible ;)
so as long as there´s no card manufacturer, that gives exakt specs of it´s cards there will be always some gambling.
you must always hope that e.g. komputerbay understands the needs of it´s customers and doesn´t just follow the law of economy and raises the prices and lowers the production costs.... by changing to a cheaper controller or memory chips.
maybe a magic lantern raw performance guarantee and a nice sticker on the box would help. of course making the card 10% more expensive than the standard cards but encouraging the manufacturer to hold up performance.
and there´s a lot of marketing in those memory cards.
sony itself offers a SxS to SD card adapter. no problem recording on a cheap 32 GB class 10 card in a EX1. or F3.... if you want to ;)
not the fastest cards on the market will do the trick, but to find cards which match the memory interface ( or call it bandwidth limit) of the specific cam as close as possible should safe buffer and gain bandwith.
and i am pretty shure i am telling no news to the most of you...
i ordered a komputerbay 32 GB x1000. the lexar 16 GB goes back to the retailer. final step will be the lexar 32 GB x1000
would love to buy them all and cross check in my own camera. but, could get a little bit expensive.
we will see...
Quote from: crash-film on June 19, 2013, 03:06:01 AM
hi,
i got my 50D now and i am a little bit disappointed.
first of all: it´s dark outside, so there´s nothing to shoot.
and i got horrible writing speeds!!
i have a komputerbay 32 GB x600 card and can barely top the data rate, that´s possible in the 550d.
to check if there´s something wrong with the komputerbay card i got me a lexar 16 GB x800.... and now:
average write speed 41 MB/s
average read speed 100 MB/s
with komputerbay:
average write speed 26 MB/s
average read speed 63 MB/s
using the W/R benchmark
i use todays build. tryed different aligning settings. btw. if you set the sector sizes the same as the allocation sizes the cam dies.
i had to remove the battery, start the cam with another NON ML card, restart it with an ML card.... and it worked again.
used all the "tricks" ( raw off, noise reduction, global draw off/on...)
but back to my problem. i expected specially with the lexar card a data rate of at least 50-60 MB/s
or is this impossible with such a card?
or am i the problem?
to me it seems, as if write speed/read speed = 1/2
i expected a 2/3 ratio. at least from the x800 card.
i have just a usb 2 card reader
someone any suggestions?
thanks!!
Return and get 1000X Komputer Bay..
Quote from: Viente on June 19, 2013, 02:05:37 PM
I think maybe some kind of petition will push Mosaic Engineering to develop AA filter for 50D?
I emailed them 2 weeks ago and haven't heard a thing. Perhaps if everyone does it then we may get a response.
Quote from: rockfallfilms on June 19, 2013, 07:07:42 PM
I emailed them 2 weeks ago and haven't heard a thing. Perhaps if everyone does it then we may get a response.
I just emailed them.
Has anybody been shooting charts with the 50D? I'd be interested in seeing how it compares to the 5D MKII and other RAW Canons(or the Sony FS series or similar 1080p camcorders) in actual lines of resolution and stops of DR.
Just tried the latest build from GregoryOfManhattan, so much more stable than the May28 build! Thank you so much! Will be out testing it some more today w/ the dog. On my Delkin 1000x card, I was getting 45-53mb/s, now it's up to 55-71mb/s. Buffer is being handled well, w/ only 5-7% idle.
One thing I noticed was that ExpSim seems like it's not working as well as before? When I change apertures, ExpSim doesn't seem to translate the extra stops of light...or maybe it's just me. I had to hit the DOF preview button to see what the actual exposure is going to look like.
Overall, really impressed at the progress of this build, and by the ML devs as a whole. Thank you thank you thank you so much. ;D ;D
I'm thinking the 50D is in third, the 5D II in second, and the 5D III in first. Having downloaded footage from the 5D II it probably isn't that far off from the 5D III, in terms of resolution. However, the 5D III appears to offer far greater advancements in terms of pixel resolution and write speeds to the card. The 50D and the 5D II appear to have a similar generation of CMOS sensor. You'll probably find the two cameras are a perfect match for recording continuous raw using multiple cams.
...Having said all of that, remember that each camera features an ability to shoot 1:1. At that point, every camera records with a pixel to pixel perfectly sharp image. I suppose the quality of the 50D and 5D II are similar to the upcoming Blackmagic Pocket Cinema Camera when shooting in a 1:1 crop mode. However, the BMPC camera will have a much newer sensor and will feature better high-ISO noise performance. Then again, it's 12-bit and not 14-bit video. Technically it may be possible to apply noise reduction to the Canon 50D and 5D II and have the same low-noise performance based on the extra information.
Quote from: LEVISDAVIS on June 19, 2013, 10:35:44 AM
Hey Crash-Film... Got a response to your card write-speed issue.
The math doesn't seem to add up when it comes time to how a card performs... Put a Komputerbay 64GB 1000x in a Canon 5DIII and experience 125MB/s write speeds. Place the same card in the 50D and experience approximately 70MB/s. The difference can be in the EXFAT format and the FAT32 format limitations.
The biggest limitation on the 5DMKII and 50D is not file system related, but the memory bandwidth of the internal RAM. If you benchmark the write speed of the 50D without LiveView activated, it easily surpasses 90 MB/s on my 1000x KomputerBay 32GB Card. Once you activate LiveView, sensor data gets written into SDRAM, and the Compact Flash DMA has to share the memory bandwidth with the sensor image DMA stream, dropping to about 67 - 70MB/s.
The 5DMKIII has a revised DIGIC with faster SDRAM memory access, which is the reason why it can still write >90MB/s with Live View on.
Quote from: LEVISDAVIS on June 19, 2013, 08:26:02 PM
...Having said all of that, remember that each camera features an ability to shoot 1:1. At that point, every camera records with a pixel to pixel perfectly sharp image. I suppose the quality of the 50D and 5D II are similar to the upcoming Blackmagic Pocket Cinema Camera when shooting in a 1:1 crop mode. However, the BMPC camera will have a much newer sensor and will feature better high-ISO noise performance. Then again, it's 12-bit and not 14-bit video. Technically it may be possible to apply noise reduction to the Canon 50D and 5D II and have the same low-noise performance based on the extra information.
What I really don't like about the BMPC is that you are stuck with a 3x sensor crop. It severely limits your choices. On a 50D, you can choose between shooting wider at a slightly reduced resolution, or 1:1 with a 3.975 sensor crop. I also really like the fact that on the 50D, you are not limited to 1.78:1 aspect ratio.
It also needs to be seen if Black Magic will actually manage to get full 12-bit raw recording working on SD Cards. Currently, the BMPC "only" shoots 10-bit ProRes 4:2:2.
From a price point, I think you either go with a 50D, and shoot good quality RAW at a VERY LOW price, or get a BMCC and have real 2.5K resolution for an affordable price. Getting an BMPC suddenly doesn't make much sense to me anymore.
The biggest limitation on the 5DMKII and 50D is not file system related, but the memory bandwidth of the internal RAM. If you benchmark the write speed of the 50D without LiveView activated, it easily surpasses 90 MB/s on my 1000x KomputerBay 32GB Card. Once you activate LiveView, sensor data gets written into SDRAM, and the Compact Flash DMA has to share the memory bandwidth with the sensor image DMA stream, dropping to about 67 - 70MB/s.
The 5DMKIII has a revised DIGIC with faster SDRAM memory access, which is the reason why it can still write >90MB/s with Live View on.
[/quote]
okay, very good hint!
so, for me.....the writing speed does not alter in any way. neither live view enabled/disabled nor turning the screen completely off makes any difference.
writing speed does not exceed 40 MB/s. while reading is always about 100 MB/s.
think it is truly a limitation of the card.
tomorrow i should have the new komputerbay x1000 card. i just want around 50-60 MB/s.
but the latest build with the fast_raw recording module gives me 1536x656 @ 23.9 fps. global draw off.
and it seems that temperature really influences the recording performance. my cam gets really hot after a while. i don´t have the issues with the 550D. it showed rock solid performance even in bright sun light and 35 degrees centigrade. i would be worried taking pictures in those conditions with the 50D.
maybe it´s just the metal case of the 50D, conducting more heat to the outside??
Quote from: necronomfive on June 19, 2013, 08:52:51 PM
It also needs to be seen if Black Magic will actually manage to get full 12-bit raw recording working on SD Cards. Currently, the BMPC "only" shoots 10-bit ProRes 4:2:2.
Getting an BMPC suddenly doesn't make much sense to me anymore.
I'm not saying this is true, I really don't know, but couldn't one argue that the BMPC's 1080p ProRes is still better than 1536x864 RAW?
Quote from: briwil on June 19, 2013, 10:03:19 PM
I'm not saying this is true, I really don't know, but couldn't one argue that the BMPC's 1080p ProRes is still better than 1536x864 RAW?
this is sth we will see, when the cam is finally out!
but despite picture quality:
this camera still offers the ability to take the movs straight from the card and start editing immediately. from a professional point of view this is a killer feature!
and 10 bit 422 pro res can provide really good resolution and enough color information to correct the usual accidents while shooting ( white balance, underexposure.... )
and you can be pretty shure there´s less moire and aliasing straight out of cam.
the workflow is just faster and smoother.
there will be two different kinds of users:
- eos ml raw for the advanced amateur/semi-pro, experimentalists and video artists. just people that don´t have to meet dead lines. maybe the 5DIII will realy find its market as a production raw shooter
- bmpcc for industrial/image film shooters, maybe journalists who will like the sleek and slim design and format. the people that pre-ordered it..... and of course as a landmark in affordable picture quality. just to set pressure on the market and make maybe 422 10 bit the new market standard, replacing 420/411 8 bit
just my thoughts! ;D
Hi guys, new here and finding interesting helpful stuff here and wanted to share experiences with Transcend 1000x 32 GB.
I am finding that depending on resolution you are filming memory buffer will change.
When filming 1280 x 960 I get speed start at 56mb and shortly climb upto 65-67mb with only one star or ocassionally 2 stars
and fills the whole 32GB card with no frame drop outs.
However, if I was to film in higher resolution memory buffer will drop to 41-50mb and frame skip also depending on resolution.
Is it likely the 50D will one day be able to record 23.98 at 1920 x 1080?
The zoom mode res is close to that... we'd have to get LV edmacs killed to try to get enough speed.
No force left... did a search of the FW for regs. Section that has force left on the other cameras is missing... fw is too old. Anything with LV_STATE won't have it.
Quote from: 1% on June 19, 2013, 11:16:21 PM
The zoom mode res is close to that... we'd have to get LV edmacs killed to try to get enough speed.
So non-crop mode will never be able to do more than 1592x1062, yeah?
I'm fine with that for what it is, I'm not complaining; but I really don't think I'll ever be able to shoot anything in crop mode, I don't see myself being able to compose a shot with a good chunk of it offscreen.
OK! I finally got my 50d and a Lexar 32GB 1000x.......now is time for the first noob question (first time I ever touch a canon camera).
I did update the firmware and installed ML 2.3v and looks like everything is ok, but now I have to install RAW and a little confused, what`s next?, I think I have to format the card again (is there an option to format the card from ML menu or do i have to do it from canon menu?) and then copy in the card the following files: autoexec.bin and the directory ML with all subdirectories from one of the builds that Gregory has released......then just turn on and ready?
Quote from: hijodeibn on June 20, 2013, 12:16:21 AM
OK! I finally got my 50d and a Lexar 32GB 1000x.......now is time for the first noob question (first time I ever touch a canon camera).
I did update the firmware and installed ML 2.3v and looks like everything is ok, but now I have to install RAW and a little confused, what`s next?, I think I have to format the card again (is there an option to format the card from ML menu or do i have to do it from canon menu?) and then copy in the card the following files: autoexec.bin and the directory ML with all subdirectories from one of the builds that Gregory has released......then just turn on and ready?
I don't think you need to reformat the card; you should just be able to copy the files from Gregory's build onto the card, overriding the files that you already have on the card from the orignal ML install, and you're good to go.
And this assuming you already made the card bootable with macboot.
I've fixed the "flicker" with 2 cache hacks... I think.
ROM:FFB52D94 BL str_UnvisibleLvDialogItemForBlackout
The offending function is there....
For crop mode, what do you mean you can't compose the shot.. just use ML grayscale preview.. display filter works off my repo.. .should be merged to main.
Shit maybe spoke too soon, will keep looking.
Well now I kinda did it but it never updates... there is a startdialogrefreshtimer called 3x, kill them and canon stops being crazy. I'm looking at one spot where its called after some msleep.
ROM:FFA872D4 BEQ loc_FFA872F0
ROM:FFA872D8 LDR R0, [R4,#0x30]
ROM:FFA872DC CMP R0, #1
ROM:FFA872E0 BNE loc_FFA872F0
ROM:FFA872E4 MOV R0, #8
ROM:FFA872E8 BL msleep
ROM:FFA872EC STR R6, [R4,#0x30]
ROM:FFA872F0
ROM:FFA872F0 loc_FFA872F0 ; CODE XREF: sub_FFA86E8C+448j
ROM:FFA872F0 ; sub_FFA86E8C+454j
ROM:FFA872F0 BL str_StartDialogRefreshTimer
ROM:FFA872F4 B loc_FFA880E0
Quote from: 1% on June 20, 2013, 12:29:26 AM
For crop mode, what do you mean you can't compose the shot.. just use ML grayscale preview.. display filter works off my repo.. .should be merged to main.
Well, I think I may just be an idiot, I don't know anything about grayscale previews or their existence; I'll go do my research, thanks.
Quote from: briwil on June 20, 2013, 12:34:44 AM
Well, I think I may just be an idiot, I don't know anything about grayscale previews or their existence; I'll go do my research, thanks.
You set preview mode in the raw module. Grayscale preview in crop mode shows corrected frame albeit in a lower quality.
Andy600, sounds like 1% is suggesting that we merge the code. lets do that and post a test build tomorrow - separate from unified. try it, see what happens and merge on Friday.
Quote from: briwil on June 20, 2013, 12:25:31 AM
I don't think you need to reformat the card; you should just be able to copy the files from Gregory's build onto the card, overriding the files that you already have on the card from the orignal ML install, and you're good to go.
And this assuming you already made the card bootable with macboot.
When do we need Macboot.? It was never mentioned in ML Installation. Do we need to use to properly install ML and forward.?
Just got my 32gb komputerbay 1000x, getting 70mb/s continous recording in 1:1 mode, 67mb/s in crop mode, using the unified 19/6 build.
Got 76MB/s now from stopping the refresh. Its faster in zoom for some reason.
Ha! I was recording 30P.. get 80MB/s in 24P.
Lulz, I'm recording almost 1080P steady.
Probably makes sense to run the don't click me before opening LV. 2nd or 3rd record in reggo mode should get you up to speed, then switch to 5X.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B50D%5D%20Side%20Effects.zip
Quote from: 1% on June 20, 2013, 02:22:22 AM
Got 76MB/s now from stopping the refresh. Its faster in zoom for some reason.
Ha! I was recording 30P.. get 80MB/s in 24P.
Lulz, I'm recording almost 1080P steady.
UNBELIEVABLE :o
;D ;D ;D
(http://i.imgur.com/0ErJIu9l.png)
Don't set your camera on fire... maybe this will work on others... lowers cpu usage tho.
Switching between photo and movie helps... seems to write the same in both eventually tho.
1920x1040 is decent the 1072 isn't continuous.
GD deff off at record. If there was a way to kill edmacs or lower cpu usage it could write faster. I think kill flicker on top helps but may not... test away.
Huge news. Nice job.
ok i guess i'ts time to get a 1000x card now
Quote from: robertgl on June 20, 2013, 03:26:53 AM
ok i guess i'ts time to get a 1000x card now
Yup, cruising along @ 30fps and even had enough buffer and idle to turn raw histogram on during recording. Getting about 73-76mb/s write and still have some idle. Wonderful work :)
Quote from: dsManning on June 20, 2013, 03:39:14 AM
Yup, cruising along @ 30fps and even had enough buffer and idle to turn raw histogram on during recording. Getting about 73-76mb/s write and still have some idle. Wonderful work :)
Lurker here! Just want to say that I am so thrilled with the work you all are doing and that I am having the time of my life grading raw video (in AE). I got a lightly used 50d three weeks ago and have been dragging it with me everywhere! You all have renewed my passion of shooting and for that I am so grateful. :)
My latest little vid: http://vimeo.com/m/68553373
that looks very good.. clean images and has sortof an emulsion quality to it.. also no aliasing.. what res did you shoot at?
Quote from: 1% on June 20, 2013, 03:11:40 AM
(http://i.imgur.com/0ErJIu9l.png)
Don't set your camera on fire... maybe this will work on others... lowers cpu usage tho.
Switching between photo and movie helps... seems to write the same in both eventually tho.
1920x1040 is decent the 1072 isn't continuous.
GD deff off at record. If there was a way to kill edmacs or lower cpu usage it could write faster. I think kill flicker on top helps but may not... test away.
Great work man.. 80mb/s that's awesome that's really close to what the Mark III is pushing, can't believe it & there is still room for more speed Wow!!!
It is a bit bootleg, needs some refinement.. and I think after some recording the last chunk shrinks. Wonder what diff order would do now.
Well any more speed an the camera will just record full res. Its close now. Some side effects are that you lose all dialogs.
sounds like the dial is really going to hit 11. :D
Quote from: 1% on June 20, 2013, 05:46:40 AM
It is a bit bootleg, needs some refinement.. and I think after some recording the last chunk shrinks. Wonder what diff order would do now.
Well any more speed an the camera will just record full res. Its close now. Some side effects are that you lose all dialogs.
AWESOME!
-awaiting komputerbay 64GB and praying it aint a dud. ....any day now...
Quote from: albert-e on June 20, 2013, 01:50:13 AM
When do we need Macboot.? It was never mentioned in ML Installation. Do we need to use to properly install ML and forward.?
Macboot?...first time I heard is needed for ML.....can anyone of the expert (@gregory, @1%, @Andy, etc) give us some light?
how do we install RAW after the ML firmware is loaded?
Quote from: hijodeibn on June 20, 2013, 07:16:25 AM
Macboot?...first time I heard is needed for ML.....can anyone of the expert (@gregory, @1%, @Andy, etc) give us some light?
how do we install RAW after the ML firmware is loaded?
It's needed for SDXC cards; it's in the installation guide. Needed for 64gb and higher cards.
wiki.magiclantern.fm/install
Quote from: 1% on June 20, 2013, 05:46:40 AM
It is a bit bootleg, needs some refinement.. and I think after some recording the last chunk shrinks. Wonder what diff order would do now.
Well any more speed an the camera will just record full res. Its close now. Some side effects are that you lose all dialogs.
That's going to blow up tomorrow in the news. As soon as I saw the post about 80Mbs, I ran to pick up a 50d. Looking forward to running the Toshiba 1066x through some tests.
Great job devs, where are paypal donation links, I'd like to send some beer to ease the coding in the hot summer :)
And question, is there a hardware limit to fps speed, it would be nice to be able to use 720x480@100fps?
Regards!
1%, i can shoot only in 1536 instead of 1584 with your build, is there is something wrong i do? ::)
75MB/s on a 600x Transcend ;D This is crazy! Nice work man.
@Viente - 1534 is correct. It uses the 512-byte rounding method so 512x3 = 1534. It's less work for the CPU to process
I guess it would be useful for the raw_module to auto-switch to the 512-byte rounding method at 30p and in crop mode. That way we retain max width in normal mode. Normal mode can shoot continuous (16:9) using the old method so it doesn't benefit it as much. Easy done with 2 modules but can it be done in 1?
BTW 1% - I haven't a clue if this is useful but I was looking at EDMAC and #5 is 2912 x 1083 - maybe larger frame sizes are possible? (I don't understand EDMAC TBH)
Quote from: nightvision04 on June 20, 2013, 09:38:44 AM
That's going to blow up tomorrow in the news. As soon as I saw the post about 80Mbs, I ran to pick up a 50d....
You mean the previous news that the 50d could shoot continuous raw video wasn't enough to tempt you? ;D
I just wonder what (if it works) will do for the 5d2 & 3. Looks like steady 2k and above might become a reality soon on the 5d3
Quote from: Andy600 on June 20, 2013, 12:17:38 PM
75MB/s on a 600x Transcend ;D This is crazy! Nice work man.
@Viente - 1534 is correct. It uses the 512-byte rounding method so 512x3 = 1534. It's less work for the CPU to process
I guess it would be useful for the raw_module to auto-switch to the 512-byte rounding method at 30p and in crop mode. That way we retain max width in normal mode. Normal mode can shoot continuous (16:9) using the old method so it doesn't benefit it as much. Easy done with 2 modules but can it be done in 1?
BTW 1% - I haven't a clue if this is useful but I was looking at EDMAC and #5 is 2912 x 1083 - maybe larger frame sizes are possible? (I don't understand EDMAC TBH)
that would be amazong 2500x780 or something like that would be 80mb/s. Nice for panoramic shots and fighting against the extreme crop of 5x zoom on 1.6 sensor.
Quote from: araucaria on June 20, 2013, 01:11:05 PM
that would be amazong 2500x780 or something like that would be 80mb/s. Nice for panoramic shots and fighting against the extreme crop of 5x zoom on 1.6 sensor.
Yes, but don't get your hopes up
Hey all,
Does anyone know if there is any good progress with truncating 14 bits to 12 bits? Together with the new writing speeds 12 bits would rock )
Andy, using your Transcend x600 card what max resolution you can run steadily @25p? My card is on the way, I'd like to know what to realistically expect ) thank you man
@rommex - TBH I don't know now. Everything just changed with 1%'s discovery. I could record non-stop 16:9 and 5:3 (width 1583) no problem. I'm just trying crop modes now and I can get 10-12 seconds at 1920 x 1072. Hoping my Komputerbay card gets here today ::)
now got the komputerbay 32 GB x1000
and i can verify all of your speeds and resolutions. even 2000x836 @23,9 was right from the start no problem. i really wonder, where this will end now...... great work!!!
I mentioned this in the test thread as well. I got a ton of pink frames during a hot (85-degree) exterior shoot yesterday afternoon (not 1% latest build).
Is this a heat related issue by any chance?
(http://img.photobucket.com/albums/v64/shenyin/pinkframe_zpsfd9a5c49.jpg)
there´s another idea i got to overcome the lacking sound ability of the 50D:
is it possible, to fire the flash when raw recording starts?
one could use a regular video camera/dslr as a 2nd unit (e.g. in interviews) to record the sound and then sync both cams using the flash.
it would also be thinkable to record the flash sound via a cheap lavalier microphone and mixing it into the sound signal using a production mixer. this could save the 2nd camera, replacing it by a regular external sound recorder.
fine tuning should be possible with the ttl-settings....
could be some kind of a hardware hack.
The worst I got was a couple of bad frames at the begining.. pink on 600D just like that is from CPU usage.. ie GD on, display filter on, etc.
This lowers CPU by like 10% so should help with that too. Yes, I kept the restriction on frame sizes.. easiest thing would be just to add some back and try it out. Anyone really want the couple of pixels?
In crop mode 1920x1040 kept going most of the time. The 1072 writes slower it seems.
And it does work on other cameras.. 6D got 41MB so 5d3 will probably cruise along at whatever its top speed is. I was actually hoping a1ex with his greater knowledge would find a nicer way to do this but there may be no nicer way, who knows. I can try flipping it on in LV, and see if it speeds up after a few records, then it can just be turned on/off with raw.
Quote from: 1% on June 20, 2013, 02:42:23 PM
This lowers CPU by like 10% so should help with that too. Yes, I kept the restriction on frame sizes.. easiest thing would be just to add some back and try it out. Anyone really want the couple of pixels?
In 1x mode, yes please, since even with the May 28th build, it has never been a problem to record the full sensor size of 1584x1062. I think the 50 pixels matter.
Never been a problem to record the small LV size though, the bandwidth is pretty low... tons of idle.
Just looking at some 1920 x 1040 shots (managed about 10-15 seconds each on my 600x card). Just :o
Hmmm, it seems that when I copy %1 newest build over a freshly installed unified ML build from June 19th, the camera freezes when raw_rec is being loaded. Do I do something wrong here?
Quote from: necronomfive on June 20, 2013, 03:51:07 PM
Hmmm, it seems that when I copy %1 newest build over a freshly installed unified ML build from June 19th, the camera freezes when raw_rec is being loaded. Do I do something wrong here?
Just be sure the modules folder goes into the ML folder. I had the same thing last night when I was sleepy and didn't notice the modules were outside of ML
What build is the latest most stable one? Is it this one?
Quotehttps://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun19.50D.109.go.unified.7eee493f6fc9.zip
Quote from: ashtrai on June 20, 2013, 04:38:46 PM
What build is the latest most stable one? Is it this one?
Yes. http://www.magiclantern.fm/forum/index.php?topic=6554.msg51887#msg51887
Quote from: crash-film on June 20, 2013, 02:35:05 PM
there´s another idea i got to overcome the lacking sound ability of the 50D:
is it possible, to fire the flash when raw recording starts?
one could use a regular video camera/dslr as a 2nd unit (e.g. in interviews) to record the sound and then sync both cams using the flash.
it would also be thinkable to record the flash sound via a cheap lavalier microphone and mixing it into the sound signal using a production mixer. this could save the 2nd camera, replacing it by a regular external sound recorder.
fine tuning should be possible with the ttl-settings....
could be some kind of a hardware hack.
I think it's best to go the tired and trusted way and use a clapperboard.. other ways i've read are a pop gun, or a keychain pet clicker
Quote from: GregoryOfManhattan on June 20, 2013, 01:28:04 AM
Andy600, sounds like 1% is suggesting that we merge the code. lets do that and post a test build tomorrow - separate from unified. try it, see what happens and merge on Friday.
I think things are moving very fast ATM with 1%'s refresh hack and a1ex's buffer sort. Both have dramatically upped the game. If they can be combined we'll certainly get continuous Full HD on the 50d. Probably better to wait for the new stuff to mature a little and for us to fully test before merging?
One thing is for sure, another big raw video news story is about to happen 8)
Please guys, bring back full width for 1:1 mode :) I had no problems with that. And since we have to upscale the footage every pixel is important! And with smaller width i have to worry about correct framing.
It sounds the RAW hack is super battery hungry - do any of you use a battery grip for your 50D? What kind? Are there grips which provide a lot of power through AA batteries? The ones I saw take 6 AAs; with my Eneloops (2000mAh) it's only 40% more Wh than a single BP-511 battery, doesn't look interesting. Are there grips which would have triple or more the Whs of BP-511? I never had a need for grip, with my 3 batteries, but now with the video feature I might reconsider.
Going back to my question of a beep at the video recording start - I really hope it will materialize. I just received my Zoom H1 recorder - really cool stuff! It'd be great to have a convenient way to sync its audio with the 50D video.
any risks with this setup ?
12V battery > inverter to 110v > AC adapter >50D ?
Quote from: robertgl on June 20, 2013, 08:14:38 PM
any risks with this setup ?
12V battery > inverter to 110v > AC adapter >50D ?
Exactly what i am going to do in the future, don't worry it is a safe configuration, just make sure the AC adapter is designed for the 50d, I saw some availables on ebay.
try to get a straight 12 V to 8.... (whatever voltage it needs) converter. your method will destroy a lot of electrical energy into direct heat...
you convert DC to AC and then back to DC. you can go DC to DC. much better!!
theoretically a resistor should work. but a stabilized power supply would be the best.
Quote from: pulsar124 on June 20, 2013, 07:42:53 PM
It sounds the RAW hack is super battery hungry - do any of you use a battery grip for your 50D? What kind? Are there grips which provide a lot of power through AA batteries? The ones I saw take 6 AAs; with my Eneloops (2000mAh) it's only 40% more Wh than a single BP-511 battery, doesn't look interesting. Are there grips which would have triple or more the Whs of BP-511? I never had a need for grip, with my 3 batteries, but now with the video feature I might reconsider.
I can't attest to this one, yet, but I just got it delivered from Amazon. Holds 2x 50D batteries or has a cartridge for 6x AA for emergency use. Seems pretty nice for the cost. Screws into the 1/4-20 thread for quick release and has a strong screw to keep contract to the camera's battery receiving end. Also has a 1/4-20 tread so you can put a quick release on the bottom (important!) Side buttons for shooting photos vertically work fine.
Nice to have the 2x battery capacity. I was running through a fully charged 2200mAh in about 30min of footage (including setup in LV). 60 min will be nice and I have 2 more stock Canon 1390mAh backups. So theoretically about 2 hours of footage with my 50D batteries and maybe another 20-30 min on the 6x AA cartridge. Not so bad... Will update with results soon.
Forgot link :P http://www.amazon.com/gp/product/B003MACYGS/ref=oh_details_o03_s00_i00?ie=UTF8&psc=1
Quote from: briwil on June 20, 2013, 07:24:50 AM
It's needed for SDXC cards; it's in the installation guide. Needed for 64gb and higher cards.
wiki.magiclantern.fm/install
Thanks...I figured out I do not have to format the card, just replace the files that @gregory is releasing.....and I saw the macboot is used to format another card in the computer for the 50d......great!!!
Quote from: hijodeibn on June 20, 2013, 08:18:05 PM
Exactly what i am going to do in the future, don't worry it is a safe configuration, just make sure the AC adapter is designed for the 50d, I saw some availables on ebay.
That's what I'm using. A car battery starter and DC-AC converter . . .it's all good. But I have an even better solution that I post later . . .
Quote from: crash-film on June 20, 2013, 08:20:39 PM
try to get a straight 12 V to 8.... (whatever voltage it needs) converter. your method will destroy a lot of electrical energy into direct heat...
you convert DC to AC and then back to DC. you can go DC to DC. much better!!
theoretically a resistor should work. but a stabilized power supply would be the best.
Do not go with the resistor solution unless you know exactly what you are doing, meaning you have the right tester to measure the output and the knowledge to confirm it is what the camera needs......the DC converter teorically is a better solution but also I will not use it unless I can measure the output and confirm it is exactly what the camera needs.......the safer solution is DC-AC converter and the canon adapter for AC, yes you will loose some energy in the convertion, but it really is not so much......if you really are going to need a lot energy because of you will be recording in exterior for hours, then I suggest to use a car battery with a DC-AC converter, that will last for many hours, if you need to move with the camera, then use a belt battery....it will also work :)
Quote from: menoc on June 20, 2013, 08:45:20 PM
That's what I'm using. A car battery starter and inverter . . .it's all good. But I have an even better solution that I post later . . .
Yeap....it is the safer and cheaper solution....I am using the same for audio recording equipments in exterior.....guarantee it will work!!!!
Just got my new Transcend x600 32Gb. OMG, it works! :'( (tears of joy))
Some strange behavior: when I shut GD off and shoot continuously @1592x896, the buffer gradually fills up at approx 40 sec and the shooting stops.
But when I turn on Global Drawing the shooting goes smoothly with 1-starred buffer.
I'm using 28 May build (being somewhat conservative at the beginning of the test). Anybody had this?
And yes, it's a battery eater. I have 2 used batteries that last through a loooong photo shooting. But RAW recording does them in 15 min, I guess. Additional batteries and AC adapter are being launched from China )))
EDIT: The following extra-battery discussion has overwhelmed my question, I guess )
Thanks - I didn't realize there were AC adapters for 50D. I spent hours calibrating my lenses, this would have been very handy. I just ordered one from ebay for only 12$ with free shipping. I do have a car booster battery, I'm pretty sure it has 12V out. Now I only need to get the inverter. 100W inverter should be sufficient, right?
of course it´s guaranteed to work.
but the ideal solution would of course be a standard v-mount to the canon specific voltage converter.
just search for it on ebay. india seems to be full of those things! ;)
i have here a bunch of NP1 batteries (anybody remembers them?) used a car 12 volt to usb 5 volt adapter to power a portable beamer.
worked fine.
maybe there´s a car to canon adapter. would be much cheaper and lighter. the inverters i know a mostly pretty heavy.
good equipment to verify the voltages and much more important the currents is imperative!
and of course you really should know what you are doing.
if you don´t know how to measure currents or voltages.... of course, always go the safe way and buy already tested and working configurations......i tell people that execute not really tested code on their pricey cams :o
DataVideo DDC-4012
9-30VDC to 7.2VDC max 4A (48W)
http://www.expandore.biz/product_detail.asp?productid=5025 (http://www.expandore.biz/product_detail.asp?productid=5025)
http://www.creativevideo.co.uk/pdf/Datavideo_DDC-4012.pdf (http://www.creativevideo.co.uk/pdf/Datavideo_DDC-4012.pdf)
Quote from: Mark0ki on June 20, 2013, 09:24:24 PM
DataVideo DDC-4012
9-30VDC to 7.2VDC max 4A (48W)
http://www.expandore.biz/product_detail.asp?productid=5025 (http://www.expandore.biz/product_detail.asp?productid=5025)
http://www.creativevideo.co.uk/pdf/Datavideo_DDC-4012.pdf (http://www.creativevideo.co.uk/pdf/Datavideo_DDC-4012.pdf)
This is great!!!!......i will certainly go for it if I needed.....but $155 I think is too much for some people.....
I think Astronomiser sells the proper solution: http://www.astronomiser.co.uk/canonpowerpro.htm#ast300ddc
This is a power converter from car 12v to Canon 50D battery-type connector, for 40 pounds + shipping.
Comparable price, in French: http://www.eosforastro.com/astro-photographie/accessoires-pour-apn/adaptateur-allume-cigare-12v-pour-apn-canon-eos-details
Much pricier (but also more professionally looking) solution is Cercis A633, for 119$ _shipping: http://www.cercisastro.com/DslrStar%20Ordering%20Info.html
Quote from: pulsar124 on June 20, 2013, 09:21:10 PM
Thanks - I didn't realize there were AC adapters for 50D. I spent hours calibrating my lenses, this would have been very handy. I just ordered one from ebay for only 12$ with free shipping. I do have a car booster battery, I'm pretty sure it has 12V out. Now I only need to get the inverter. 100W inverter should be sufficient, right?
More than enough, with 50 W you are OK!
Quote from: pulsar124 on June 20, 2013, 09:37:16 PM
I think Astronomiser sells the proper solution: http://www.astronomiser.co.uk/canonpowerpro.htm#ast300ddc
This is a power converter from car 12v to Canon 50D battery-type connector, for 40 pounds + shipping.
Much pricier (but also more professionally looking) solution is Cercis A633, for 119$ _shipping: http://www.cercisastro.com/DslrStar%20Ordering%20Info.html
WAW!!! this is the way to go with my battery belt......I just remove the auto jack for cigarette, connect a XLR and ready to shoot........nice!
If you know how to solder then the cheapest solution is the lm337 (if 1.5A is enough). You will need old battery, some resistors, capacitors and cooling radiator. Total cost of less than $ 5.
http://www.onsemi.com/pub_link/Collateral/LM337-D.PDF (http://www.onsemi.com/pub_link/Collateral/LM337-D.PDF)
*****
would be better to make a new topic to discuss this.
Quote from: Mark0ki on June 20, 2013, 10:08:44 PM
If you know how to solder then the cheapest solution is the lm337 (if 1.5A is enough). You will need old battery, some resistors, capacitors and cooling radiator. Total cost of less than $ 5.
http://www.onsemi.com/pub_link/Collateral/LM337-D.PDF (http://www.onsemi.com/pub_link/Collateral/LM337-D.PDF)
hahahaha......I do know how to solder ether......but I don't think is a good idea to spend all the time needed to make it work.......the adapter for 40 euros is a better solution for me........but oviously your solution is much more fun!!!
Quote from: hijodeibn on June 20, 2013, 10:16:25 PM
hahahaha......I do know how to solder ether......but I don't think is a good idea to spend all the time needed to make it work.......the adapter for 40 euros is a better solution for me........but oviously your solution is much more fun!!!
I think that's inside the box is a lm337 (lm338) or something similar.
Quote from: Mark0ki on June 20, 2013, 10:21:14 PM
I think that's inside the box is a lm337 (lm338) or something similar.
Probably.......should be something very similar to your diagram.....just with a nicer presentation.... :P
1920x872 scales pretty nice to 4k (4096x1920)....... this is so awesome!! ;D
OK, I'm only getting pink frames. Am I missing something? I kind of messed around with PROP. Would that affect anything? It says it's a read only property . ..
Komputerbay 64GB 1000x, 5x crop, 1920x1040 @ 23.976 (using 1%'s latest build ) . . . But fully stable after the 3rd recording and enabling "Don't click me!"
(http://i.imgbox.com/abuYjPoi.jpg)
Quote from: crash-film on June 20, 2013, 11:32:09 PM
1920x872 scales pretty nice to 4k (4096x1920)....... this is so awesome!! ;D
I'm using the latest Andy builds (Andy 600 RAW and Fast RAW) - and (5x crop, of course) I can't get more than a few seconds at that size (with Komputerbay 1000x 64 card that's fine at 1536 x 864 or whatever). I wonder if I'm missing something that others are doing to squeeze a bit more speed in that mode.
Some FULL HD (1920 x 1080p) raw video footage I shot this evening on the 50D. (no audio)
The original is NOT scaled. It's shot at 1920 x 1080 24p
Download the original. Vimeo has scaled this to 720p because I'm cheap and haven't got a Vimeo Plus account ;D
https://vimeo.com/68807509/download?t=1371767517&v=172469260&s=c3b55aa4afede69ce86a0f5f3b155de7 (https://vimeo.com/68807509/download?t=1371767517&v=172469260&s=c3b55aa4afede69ce86a0f5f3b155de7)
This is using A1ex's buffer sorting method and I get about 6-10 seconds per clip (1080p) on a Transcend 600x CF card. Not bad ;)
Here are some frame grabs: http://imgbox.com/g/LefsA41Eo9 (http://imgbox.com/g/LefsA41Eo9) (Gallery)
Quote from: menoc on June 20, 2013, 11:50:46 PM
OK, I'm only getting pink frames. Am I missing something? I kind of messed around with PROP. Would that affect anything? It says it's a read only property . ..
Komputerbay 64GB 1000x, 5x crop, 1920x1040 @ 23.976 (using 1%'s latest build ) . . . But fully stable after the 3rd recording and enabling "Don't click me!"
(http://i.imgbox.com/abuYjPoi.jpg)
Deleted all the config files. No more pink frames.
Quote from: dhallowell19 on June 20, 2013, 11:50:58 PM
I'm using the latest Andy builds (Andy 600 RAW and Fast RAW) - and (5x crop, of course) I can't get more than a few seconds at that size (with Komputerbay 1000x 64 card that's fine at 1536 x 864 or whatever). I wonder if I'm missing something that others are doing to squeeze a bit more speed in that mode.
use 1%'s and turn on "Don't click me!"
Quote from: Andy600 on June 20, 2013, 11:52:16 PM
Some FULL HD (1920 x 1080p) raw video footage I shot this evening on the 50D. (no audio)
The original is NOT scaled. It's shot at 1920 x 1080 24p
Download the original. Vimeo has scaled this to 720p because I'm cheap and haven't got a Vimeo Plus account ;D
https://vimeo.com/68807509/download?t=1371767517&v=172469260&s=c3b55aa4afede69ce86a0f5f3b155de7 (https://vimeo.com/68807509/download?t=1371767517&v=172469260&s=c3b55aa4afede69ce86a0f5f3b155de7)
This is using A1ex's buffer sorting method and I get about 6-10 seconds per clip (1080p) on a Transcend 600x CF card. Not bad ;)
Nice. Moire is non-existant and there's little aliasing . . .
Quote from: menoc on June 21, 2013, 12:34:24 AM
use 1%'s and turn on "Don't click me!"
which one is that? thanks
Quote from: menoc on June 21, 2013, 12:39:31 AM
Nice. Moire is non-existant and there's little aliasing . . .
Thanks.
The aliasing is my fault probably. Too much sharpening ;D
Here's some frame grabs: http://imgbox.com/g/LefsA41Eo9 (http://imgbox.com/g/LefsA41Eo9)
@Andy600 It looks nice, very filmic. I tried crop mode but didn't find it very practical to use as I could only see the middle part of the frame.
Can you upload the DNGs for the sample frame grabs?
Quote from: rockfallfilms on June 21, 2013, 01:11:26 AM
@Andy600 It looks nice, very filmic. I tried crop mode but didn't find it very practical to use as I could only see the middle part of the frame.
Thanks :)
Grayscale preview shows the recordable frame size so you don't have to guess. Set it in the raw module ;)
Gonna try hack + new buffer method... hopefully maxes it out.
80.1 solid.
Quote from: a1ex on June 21, 2013, 01:14:50 AM
Can you upload the DNGs for the sample frame grabs?
Yep. I had already rendered H.264 to Premier and frame grabbed there but I'll try to find the corresponding DNGs - I converted to 12-bit Cinema DNGs
Quote from: Andy600 on June 21, 2013, 01:14:57 AM
Thanks :)
Grayscale preview shows the recordable frame size so you don't have to guess. Set it in the raw module ;)
I know I asked about this yesterday...
I tried out Grayscale preview- but just to be sure I'm not missing something- its really only useful for framing up a shot before you begin recording, no?
Once I hit record, the screen's frame rate went down to maybe updating once every second or two, not really useable if you're shooting people or moving objects and trying to keep focus.
Quote from: Andy600 on June 21, 2013, 01:14:57 AM
Thanks :)
Grayscale preview shows the recordable frame size so you don't have to guess. Set it in the raw module ;)
Yeah I've got that switched on but the liveview image still differs from recorded one. Maybe I need a different build, I'm using 19th unified.
Quote from: a1ex on June 21, 2013, 01:14:50 AM
Can you upload the DNGs for the sample frame grabs?
Here you go a1ex:
http://we.tl/ua04qhB1wp 12bit CDNG & Post frame grab Jpegs
Quote from: rockfallfilms on June 21, 2013, 01:27:35 AM
Yeah I've got that switched on but the liveview image still differs from recorded one. Maybe I need a different build, I'm using 19th unified.
Have you set snap to center 5x in zoom box settings? Then press joystick in zoom mode to center on the crop area.
Quote from: 1% on June 21, 2013, 01:16:31 AM
Gonna try hack + new buffer method... hopefully maxes it out.
That's what I was hoping you would say :D
Its up. I guess will see 81 when a1ex updates the strategy some more.
Quote from: 1% on June 21, 2013, 01:35:57 AM
Its up. I guess will see 81 when a1ex updates the strategy some more.
I'm was going to bed but can't resist the urge to try this :D
It takes 5 minutes :)
I'm tired too and its only 6:40PM
BTW, wow card gets eaten up fast recording big raw... on an SD card it lasts a while, here not so much.
Quote from: 1% on June 21, 2013, 01:46:42 AM
It takes 5 minutes :)
I'm tired too and its only 6:40PM
BTW, wow card gets eaten up fast recording big raw... on an SD card it lasts a while, here not so much.
wow! Getting 360 frames now compared to 160 - 170 with buffer-sorting only :o Frames look fine!
Buffer sorting write speeds average 57 - 59MB/s. With this I'm steady at 72MB/s on a 600x card. Crazy shit!
Would be good to have those 6 lines back ;) or I guess 1088 to round it up?
Pissed I can't shoot more tomorrow and I bet my Komputerbay 1000x will arrive too.
Truly amazing work guys. Thankyou :)
I'll try to add full max sizes back. This writing strategy is pretty good for longevity.
posted a new unified (the main magic-lantern branch used by many other cameras) based build.
http://www.magiclantern.fm/forum/index.php?topic=6554.msg51887#msg51887 (http://www.magiclantern.fm/forum/index.php?topic=6554.msg51887#msg51887)
gets 220-250 1920x1080 (23.976) frames.
@KahL - Kahleem - which build were you using when that happened on your shoot? please report back, so devs and users know where problems and instabilities may lie.
@Andy600 very many changes and the code differences between the tragic and the unified are substantial.
what settings are required to get to the 80s (i liked 90s music much better anyway)?
just tried the tragic [50D] 80point1.zip and i'm getting less speed than on unified - 150-200 frames at 1920x1072 (23.976)
can't wait to see the speed - thanks 1% and a1ex.
EDIT: just recorded 300plus 1920x1080 (23.976) frames with this unified.
earlier build today has really cool graphs - a plot of buffer overflow so you can see it as you hit your maximum.
recommend the most recent build - but if you want to see it -the build with the graphs is: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/ml-2013Jun20.50D.109.go.unified.90c50ab005b7.zip
You have to kill the dialog timers with don't click me and then get into LV.. second record speeds up. Do first in regular mode before you zoom.
1200+ frames of 1920x1072
1000+ 1984x1056
1920x1040 - supposed to be continuous but my card filled
thank you ;D - had to do the regular mode first.
855, 448, 1261 frames - yes that is much faster than 300.
why are the module settings included with preview canon?
is that the recommendation?
The edmac hack doesn't work on 5D2/50D.. auto uses the grayscale preview which eats CPU.
GD off@record and alternate photo and movie seems to give me best speeds.
Only getting 12-16GB of the 1920x1040 at a time for some reason. Slightly smaller and its good.. like 1856x1056 or something... but a 64GB card will only hold like 15Mins max.
Got temp warning too. WTF makes 50D so hot.
Quote from: briwil on June 21, 2013, 01:25:28 AM
I know I asked about this yesterday...
I tried out Grayscale preview- but just to be sure I'm not missing something- its really only useful for framing up a shot before you begin recording, no?
Once I hit record, the screen's frame rate went down to maybe updating once every second or two, not really useable if you're shooting people or moving objects and trying to keep focus.
Look, if you want to make 5x crop work like a normal lens than you'll have to get something like a 10mm EF-S lens so that 5x mode will convert it to something more like a 50mm lens. Otherwise, you have to shoot from afar . . .
what's the current max res achievable full-sensor?
Quote from: menoc on June 21, 2013, 06:10:35 AM
Look, if you want to make 5x crop work like a normal lens than you'll have to get something like a 10mm EF-S lens so that 5x mode will convert it to something more like a 50mm lens. Otherwise, you have to shoot from afar . . .
Ok. I feel like everytime I ask a question on this forum I'm getting responses from people who sound annoyed.
I understand that crop mode works differently than the normal mode, that's exactly what I was saying, and people are telling me to turn on ML Previews as though that will alleviate my issue with it, and as you just said, it won't. Was just looking for clarification.
The problem is the raw frame is larger than the preview area. Grayscale preview does I think the whole frame not 1024x640 or whatever of it.
Here's a bit of 1920x 1040 from my 50d. Quick Test for latitude. I accidentally severely underexposed the face yet I was able to bring most of it back. F7 in low light. Wow. A 50mm f1.8 lens was used.
Quote from: Andy600 on June 21, 2013, 01:30:06 AM
http://we.tl/ua04qhB1wp 12bit CDNG & Post frame grab Jpegs
I knew it... black level is wrong on all of them...
Can you take some silent pics in the same video mode, and send me the dng?
https://vimeo.com/68826602
I vowed to never do a test video. I lied.
Quote from: Andy600 on June 21, 2013, 01:31:22 AM
Have you set snap to center 5x in zoom box settings? Then press joystick in zoom mode to center on the crop area.
Yeah I've got that selected aswell. I get the greyscale preview when recording but the view stays the same with or without it. I still only get to see the middle of the crop.
I'll format the card later and try a fresh install, maybe something has got screwed up.
I was testing Unified Build of 19 June.
I often increase contrast of images to see some textures/bugs that are not obvious but could pop up in post.
That's the texture that I saw:
100% crop
(http://img35.imageshack.us/img35/646/ylfp.jpg)
(http://img11.imageshack.us/img11/5374/7rxo.jpg)
And also with x5 zoom:
100% crop
(http://img21.imageshack.us/img21/826/voch.jpg)
(http://img341.imageshack.us/img341/5329/us14.jpg)
I was doing stable shooting @1600 at Transcend x600 card.
Still getting 57-60MB/s in 1:1mode, am I missing something?
Is it possible to move record & buffer information a bit higher so it won't overlap recording image? ::)
(http://i.imgur.com/ta07Yja.jpg)
Above, I have this done.
Hmmm... so black level is still wrong, I haven't had the chance to check it yet. Maybe should look at that today.
Dumb question: how to open submenu in ML on 50D? On my 600D it appears when i press "Q" button.
FUNC. :)
Another one. When live view is on, the brightness on the screen is changing everytime i direct the camera to the bright and dark. How to disable that? And what is normal temperature for the chip?
Quote from: 1% on June 21, 2013, 02:56:43 PM
Above, I have this done.
Hmmm... so black level is still wrong, I haven't had the chance to check it yet. Maybe should look at that today.
what in the appearance tells you the black level is off?
JulianH and I both measured the DNG size could that have changed or been shifted this past week?
easy enough to shoot some DNGs and find out.
the pink/ magenta clips seem to be an occasional anomaly of the recent [50]80pt1 build ( 2 out of 34 clips had this and it covered the whole frame unlike KahL issue).
this build showed rates as high as 80.5 MB/s but i wonder about the actual data rate required for 1920x1072p23.976 - isn't that 82.4 MB/s?
is the tragic lantern slowing down the frame rate or is it actually recording at a rate greater than the display?
does 50D at 11 really = 83 MB/s?
thanks for everything - love the look even in very low light - ran out to grab some shots late last night : http://vimeo.com/gregoryo/50d-1080p
if i can get any time tonight to try a grade, i'll repost it.
Are your 50D's heating up? After 20 minutes of raw video shooting mine gets to about 50deg. C. It does the same for about an hour continuous h.264 shooting. I shot a concert for two hours straight last week and the camera was pretty hot. The reading showed 57deg.
Normally when I fire it up it shows about 35deg.
How hot should I let it go before I give it a break?
When i turn on thу camera it was 35C, I did 1 test raw recording (3 sec) and it boosted from 35C to 43C. I just thought that it's quite quick.
New guy here, everything seems straightforward, I just have a couple questions because I haven't seen them addressed in the forums thus far:
1) My crop mode clips are pink. My full-sensor clips are fine. What gives?
2) Besides shooting in crop mode, disabling everything I can in the Canon menus, and leaving as little up to the camera as I can (e.g. AWB etc), and turning off Global Draw, what specifically can I do to optimize this camera for higher write speeds? My benchmarks regularly top out at 50-55mb/s and I'm using a 1000x/32GB card. I haven't ruled out the card being bad, but before I send it back what can I do to verify it's not fast enough?
Quote from: ddueck88 on June 21, 2013, 05:26:17 PM
New guy here, everything seems straightforward, I just have a couple questions because I haven't seen them addressed in the forums thus far:
1) My crop mode clips are pink. My full-sensor clips are fine. What gives?
2) Besides shooting in crop mode, disabling everything I can in the Canon menus, and leaving as little up to the camera as I can (e.g. AWB etc), and turning off Global Draw, what specifically can I do to optimize this camera for higher write speeds? My benchmarks regularly top out at 50-55mb/s and I'm using a 1000x/32GB card. I haven't ruled out the card being bad, but before I send it back what can I do to verify it's not fast enough?
Same issues with 5x pink frames. Regular sensor frames are fine.
I have the same card (and am doing a bit faster than yours) and have been tweaking settings like crazy to try to get close to 80mb/s. I'm capping at about 67mb/s right now.
Running mlmod Jun20th build by GregoryOfManhattan with the stock raw module included in that pack.
Quote from: dsManning on June 21, 2013, 05:33:45 PM
Running mlmod Jun20th build by GregoryOfManhattan with the stock raw module included in that pack.
I forgot to mention what build I'm using, my bad, but yes, this is the same one I'm running.
Quote from: 1% on June 21, 2013, 03:43:18 AM
You have to kill the dialog timers with don't click me and then get into LV.. second record speeds up. Do first in regular mode before you zoom.
1200+ frames of 1920x1072
1000+ 1984x1056
1920x1040 - supposed to be continuous but my card filled
This is the key. I'm getting 77 Mb/s average.
Also I should mention, I'm getting pink frames on 80% of 1:1 @ 1920 x 1040. GregoryOfManhatten build with 1%'s side effect modules. Im using a Toshiba 1066x Exceria 64gb.
What about this?
/* change dialog refresh timer from 50ms to 1024ms */
if (MEM(0xffa84e00) == 0xe3a00032) /* mov r0, #50 */
cache_fake(0xffa84e00, 0xE3A00B01, TYPE_ICACHE); /* change to mov r0, #1024 */
Should be a bit cleaner (no major side effects).
The dreaded Pink screen:
I was using a 1.4 50mm Nikkor S.C with aperture wide open and ETTR enabled (was using 1%'s -don't click me). I noticed when the I changed the ML digital ISO to -2.0 EV I got pink frames, when I zeroed it out I got the friendly screen back. Could be an issue but, ND filters will work for now.
And yes, my 50D heats up quite quickly on this build but, I think a1ex has figured it out.
temperature - usually 43 with some builds i have transiently hit 57.
does anyone have their 50D and computer near enough eachother to shoot some Silent Picture mode DNGs at regular and zoom mode and upload them?
in response to some color issues, 1% asked for current silent picture mode DNGs - it is especially important if you take one and see a black border of any width - so shoot a light color object or otherwise expose in some way so that any potential black border is visible.
perhaps something has changed which affect the calculations using offsets - i see that the offsets for the 5D2 were adjusted again a couple of days ago.
Quote from: a1ex on June 21, 2013, 07:44:26 AM
I knew it... black level is wrong on all of them...
Can you take some silent pics in the same video mode, and send me the dng?
@a1ex - Sorry, I was away all day and didn't have a chance to do this sooner.
I've uploaded some silent pics taken with the same settings as last night's 1080p video and also a few with today's commits (just compiled myself). Black level is still wrong.
http://we.tl/GC7rduWeiW (http://we.tl/GC7rduWeiW) (guys, these are very uninteresting test shots FAO a1ex so please don't waste your time downloading them :) )
I'm still having an issue with previewing in 5x zoom mode, only getting the centre part visible so framing is hard.
I've activated the settings people have mentioned and I'm beginning to think I might have a faulty camera/button but just wanted to check again.
My settings are:
Prefs, snap points - "center to 5x raw"
Movie, Raw video, preview, "ML Grayscale"
When i press the joystick in 5x mode it just takes me back into the ML menu.
Any ideas?
Quote from: rockfallfilms on June 21, 2013, 10:26:58 PM
I'm still having an issue with previewing in 5x zoom mode, only getting the centre part visible so framing is hard.
I've activated the settings people have mentioned and I'm beginning to think I might have a faulty camera/button but just wanted to check again.
My settings are:
Prefs, snap points - "center to 5x raw"
Movie, Raw video, preview, "ML Grayscale"
When i press the joystick it just takes me back into the ML menu.
Any ideas?
What build are you using?
Quote from: Andy600 on June 21, 2013, 10:27:53 PM
What build are you using?
Todays unified that @gregory posted at the bottom of the other thread.
Just tried your June 18th build and get the same issue.
skip_top = 26 -> correct
skip_left = zoom ? 64: 74 -> wrong, should be zoom ? 0 : idk (all the DNGs were for zoom as far as I could tell)
Quote from: a1ex on June 21, 2013, 10:43:31 PM
skip_top = 26 -> correct
skip_left = zoom ? 64: 74 -> wrong, should be zoom ? 0 : idk (all the DNGs were for zoom as far as I could tell)
I put a non-zoomed DNG in the zip 00000006.DNG
Sorry, what file to change skip values? I'll recompile it
Quote from: rockfallfilms on June 21, 2013, 10:29:36 PM
Todays unified that @gregory posted at the bottom of the other thread.
Just tried your June 18th build and get the same issue.
Have you tried deleting your config files? Delete everything off the card and copy Gregory's build. I just checked and I'm having issues with raw preview modes too
Quote from: Andy600 on June 21, 2013, 10:51:39 PM
I put a non-zoomed DNG in the zip 00000006.DNG
Hm, that one also has skip_top=26 and skip_left=0. Interesting, 50D looks unique.
Quote from: Andy600 on June 21, 2013, 10:53:26 PM
Have you tried deleting your config files? Delete everything off the card and copy Gregory's build. I just checked and I'm having issues with raw preview modes too
Yeah I've done a clean install from a format. When in normal mode, pressing the middle joystick is snapping the focus box to the middle of the screen so the joystick appears to be working ok. In 5x mode, pressing the joystick just moves the focus box around the screen randomly on each press but doesn't change the preview grey or let me see anymore of what I'm shooting.
When I long press it goes to a menu, I thought the camera was faulty but it looks like it's supposed to do that.
Quote from: a1ex on June 21, 2013, 10:43:31 PM
skip_top = 26 -> correct
skip_left = zoom ? 64: 74 -> wrong, should be zoom ? 0 : idk (all the DNGs were for zoom as far as I could tell)
hey there, remember the procedure now - set all of the skip values to 0, created a build.
shot silent pic DNGs.
we did that 2 weeks ago and got the results here
http://www.magiclantern.fm/forum/index.php?topic=5586.msg46715#msg46715
why is it different today?
it looks easier to just set
define RAW_DEBUG in platform/50D.109/features.h
but shouldn't that be the same as forcing all of the values to zero in src/raw.c (for the CONFIG_50D near line 348)
i also see that the code for the 5D2 had to change these values a couple of days ago - has something else shifted these values for all cameras?
Andy600 - do you see where in the code a1ex is referring?
the test should be to set skip to 0 (and/or/or only - define RAW_DEBUG - ask a1ex)
shoot silent mode DNGs then count the blackness.
Quote from: a1ex on June 21, 2013, 10:59:43 PM
Hm, that one also has skip_top=26 and skip_left=0. Interesting, 50D looks unique.
So if I set skip_left = zoom ? 0: ???
I should just trial and error the other value?
Quote from: GregoryOfManhattan on June 21, 2013, 11:08:40 PM
hey there, remember the procedure now - set all of the skip values to 0, created a build.
shot silent pic DNGs.
we did that 2 weeks ago and got the results here
http://www.magiclantern.fm/forum/index.php?topic=5586.msg46715#msg46715
why is it different today?
it looks easier to just set
define RAW_DEBUG in platform/50D.109/features.h
but shouldn't that be the same as forcing all of the values to zero in src/raw.c (for the CONFIG_50D near line 348)
i also see that the code for the 5D2 had to change these values a couple of days ago - has something else shifted these values for all cameras?
Andy600 - do you see where in the code a1ex is referring?
the test should be to set skip to 0 (and/or/or only - define RAW_DEBUG - ask a1ex)
shoot silent mode DNGs then count the blackness.
Yep, in raw.c right?
#ifdef CONFIG_50D
skip_top = 0;
skip_left = 0;
skip_right = 0;
skip_bottom = 0;
#endif
though as i am now reading c code it does look like you could just
#define RAW_DEBUG
in features.h
would be interesting if your DNGs had different borders from the ones JulianH and i shot 2 weeks ago.
many things are changing and they just had to update the values for the 5D2
Quote from: GregoryOfManhattan on June 21, 2013, 11:15:58 PM
#ifdef CONFIG_50D
skip_top = 0;
skip_left = 0;
skip_right = 0;
skip_bottom = 0;
#endif
though as i am now reading c code it does look like you could just
#define RAW_DEBUG
in features.h
would be interesting if your DNGs had different borders from the ones JulianH and i shot 2 weeks ago.
many things are changing and they just had to update the values for the 5D2
yes, I think we need to recheck. Also there's no need to define top and bottom skips if they are 0 (as currently set in raw.c) correct?
BTW I was probably still waiting for my CF card when all this was being done so I wasn't testing.
re: features.h - try it
To get the offsets from dng:
dng2raw foo.dng -> this will set the offsets to 0
raw2dng foo.raw
From the latest samples, I'd say skip_top 26 and all the others 0.
Maybe it's this RAW_DEBUG_BLACK not RAW_debug?
Quote from: a1ex on June 21, 2013, 11:28:12 PM
To get the offsets from dng:
dng2raw foo.dng -> this will set the offsets to 0
raw2dng foo.raw
From the latest samples, I'd say skip_top 26 and all the others 0.
Ok, I'll try that before we start debugging
Ok, looks like I've found the problem :)
Should be:
skip_top = 26;
skip_left = zoom ? 74 : 74;
This means max frame dimensions are actually:
1590 x 1058 normal mode
1990 x 1080 zoomed
Took lots of DNGs, none were pink or corrupted
Where did you find the left border? I couldn't see it in your samples...
Quote from: a1ex on June 22, 2013, 12:18:52 AM
Where did you find the left border? I couldn't see it in your samples...
it's not in the samples. I reset to 0 and measured again
Just trying some raw video with these settings now
update: Video is fine. No pink or corrupt frames :) in normal and zoomed mode. Tried several resolutions. All looking good!
Maybe the 500d is also wrong too as it had the same settings?
Bit bucket isn't letting me upload anymore :(... i dunno did I upload too many files or they hate me..
http://www.qfpost.com/file/d?g=zt8KEGWau (http://www.qfpost.com/file/d?g=zt8KEGWau)
That is today's stuff as of this moment.
Module with no doubled frame skip... ooops
http://www.qfpost.com/file/d?g=4j28LxXwG (http://www.qfpost.com/file/d?g=4j28LxXwG)
Quote from: 1% on June 22, 2013, 01:18:47 AM
Bit bucket isn't letting me upload anymore :(... i dunno did I upload too many files or they hate me..
http://www.qfpost.com/file/d?g=zt8KEGWau (http://www.qfpost.com/file/d?g=zt8KEGWau)
That is today's stuff as of this moment.
Module with no doubled frame skip... ooops
http://www.qfpost.com/file/d?g=4j28LxXwG (http://www.qfpost.com/file/d?g=4j28LxXwG)
Just tried and all videos have a left border. 1920x1080 records a few frames then frames go black
Quote from: Andy600 on June 22, 2013, 02:40:34 AM
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.
I was away for work a few days and now suddenly the 1080p barrier seems broken. Amazing! :)
I'm away for the weekend - took my camera with yesterdays build by Gregory.
I'm reading about this workflow where you have to use 'don't click me' - whenever I do that my camera crashes hard though. I press it before enabling live view. The display turns black and i cant turn on live view or get a menu on the screen. When I press the shutter I get Err 80.
Any advice on the don't click me thing?
See reply #1693.
Quote from: JulianH on June 22, 2013, 09:34:52 AM
I was away for work a few days and now suddenly the 1080p barrier seems broken. Amazing! :)
I'm away for the weekend - took my camera with yesterdays build by Gregory.
I'm reading about this workflow where you have to use 'don't click me' - whenever I do that my camera crashes hard though. I press it before enabling live view. The display turns black and i cant turn on live view or get a menu on the screen. When I press the shutter I get Err 80.
Any advice on the don't click me thing?
Use 'don't click me' only for 1%'s build
I made a new menu for this.. just have to see hat is up with these skips.
Quote from: 1% on June 22, 2013, 02:58:55 PM
I made a new menu for this.. just have to see hat is up with these skips.
have you tried the cache hack code a1ex suggested in reply #1693?
Hmm.. should actually try his cache hack for all the time and see if it fixes the menus.
Ok also what about shutter speeds?
In movie mode if you follow the timer real speeds are like 1/24 - something... the gui still lets you turn past it and then ML can freeze. Not locking the speeds gives you fake shutters that don't change expo and you still lock when in movie mode it goes to like 20".
Gentler hack: 79.1
Full Hack 80.1
So maybe slow it down some more.
Hmm.. 4096 is almost there... going to try 8192... I guess best thing would be make this an option, either totally off or 1024, 2048, 4096, 8192, etc... 4096 is almost good enough for menu.
Quote from: 1% on June 22, 2013, 03:45:21 PM
Hmm.. should actually try his cache hack for all the time and see if it fixes the menus.
Ok also what about shutter speeds?
In movie mode if you follow the timer real speeds are like 1/24 - something... the gui still lets you turn past it and then ML can freeze. Not locking the speeds gives you fake shutters that don't change expo and you still lock when in movie mode it goes to like 20".
I've noticed shutter speeds can be a bit random but don't dip below min shutter speed selected for me (movie mode). I tend to shoot 23.976p, 24p or 25p (because I'm in Europe) and noticed last night under tungsten lighting that I was getting flicker at 24p and had to push up the shutter speed, probably because of FPS override. Would be good (as Driftwood just mentioned in the 5d3 topic) to set a better base shutter in movie mode when using auto ETTR.
@1% - Still having issues with Bit Bucket? Maybe delete some older downloads?
hey Andy600, how are you fixing black point errors in Resolve?
for stills, there are many ways - like the free gimp (see screenshot below with your DNG)
lift doesn't do the same thing as shifting the black point does - so if you have any Resolve tips for adjusting this, let me know.
(http://50.56.67.113/ml-21june13/Screen%20Shot%202013-06-22%20at%2012.50.34%20AM.png)
Quote from: GregoryOfManhattan on June 22, 2013, 05:32:53 PM
hey Andy600, how are you fixing black point errors in Resolve?
for stills, there are many ways - like the free gimp (see screenshot below with your DNG)
lift doesn't do the same thing as shifting the black point does - so if you have any Resolve tips for adjusting this, let me know.
It's just 1 button press ;)
In the 3-way Color panel just hit the A (auto color) button. It's bottom-left of screen.
I apply Black Magic film settings in Camera Raw (per clip or project) then auto correct the first node, then apply a LUT (I like the Black Magic Film LUT or the Arri Alexa LUT) and grade to taste. Also, WB settings in camera raw are worth playing with but i didn't for the video.
I didn't really do much more than add some Luma sharpening, saturation and slight gamma lift for that test video.
Regarding 5x crop can someone tell if what I'm doing is correct?
I activate the following in the menus:
(https://dl.dropboxusercontent.com/u/24738031/ML/focusbox.jpg)
(https://dl.dropboxusercontent.com/u/24738031/ML/raw-menu.jpg)
This is the view i get in 5x crop mode
(https://dl.dropboxusercontent.com/u/24738031/ML/liveviewframing.jpg)
This is what it's like whilst recording:
(https://dl.dropboxusercontent.com/u/24738031/ML/LV-whilst-recording.jpg)
and this is what the dng looks like.
(https://dl.dropboxusercontent.com/u/24738031/ML/5xcrop-frame.jpg)
Is this correct or should i be seeing more of the frame on liveview? As it stands composing a shot is difficult as the LV image differs greatly from the recorded one.
Cheers
@rockfallfilms you should be seeing more but I think Grayscale Preview is broken or maybe bypassed atm. I have the same issue now.
Quote from: Andy600 on June 22, 2013, 05:49:07 PM
@rockfallfilms you should be seeing more but I think Grayscale Preview is broken or maybe bypassed atm. I have the same issue now.
Ah right, at least it's not just me then. Do you get the black line on the left of frame too?
Quote from: rockfallfilms on June 22, 2013, 06:08:34 PM
Ah right, at least it's not just me then. Do you get the black line on the left of frame too?
Yes, it depends on the resolution selected. It's being worked on atm
I have a question. I use "80point1" build, i can't set the sutter speed to 1/500, 1/1000 or more. In RAW recording, the image brightness stays like i'ts 1/200. When i take a picture, its brightness matches 1/1000 as i set. Is it the way to set the sutter speed more than 1/200 in RAW video recording?
@RockFallFilms - Can you try this build and let me know if you're still getting that left border. try normal and crop, largest resolutions you can select.
The test again with width set to 1920 x (any height)
https://bitbucket.org/andy600/andy50d/downloads/Andy600.50D.ML.Border.Fix.Test.Build.Not.Official.zip
Delete your raw config file first.
Quote from: Andy600 on June 22, 2013, 06:22:28 PM
@RockFallFilms - Can you try this build and let me know if you're still getting that left border. try normal and crop, largest resolutions you can select.
The test again with width set to 1920 x (any height)
https://bitbucket.org/andy600/andy50d/downloads/Andy600.50D.ML.Border.Fix.Test.Build.Not.Official.zip
Delete your raw config file first.
Yeah that's fixed it, no black borders now at the following resolutions:
1584x892
1984*1080
1920*818
I did get all pink frames when shooting at 1344x756 though.
Andy, did you have another look at that EDMAC thing you were looking at to get more resolution?
Yea, I dunno, I get that black line.. esp on raw zebras.. I think the skips are fucked.
If it "works' when you change res its just cutting off the black skip area.
BTW, grayscale preview needs GD ON.
* I can't delete anything on bitbucked.. download page just logs me out as if they banned me from uploading or something.
Quote from: araucaria on June 22, 2013, 06:46:38 PM
Andy, did you have another look at that EDMAC thing you were looking at to get more resolution?
Yes, we're already using it so it's not news ;D
Quote from: 1% on June 22, 2013, 06:49:27 PM
Yea, I dunno, I get that black line.. esp on raw zebras.. I think the skips are fucked.
If it "works' when you change res its just cutting off the black skip area.
BTW, grayscale preview needs GD ON.
* I can't delete anything on bitbucked.. download page just logs me out as if they banned me from uploading or something.
See: http://www.magiclantern.fm/forum/index.php?topic=6554.msg54060#msg54060 (if you haven't already) ;)
Quote from: Andy600 on June 22, 2013, 06:50:59 PM
Yes, were already using it so it's not news ;D
So is there coming more res? :p
From where exactly. Its zoom size or regular size.
Quote from: 1% on June 22, 2013, 07:57:38 PM
From where exactly. Its zoom size or regular size.
I was asking about zoom size, I thought when reading a comment by Andy600 that maybe the zoom stream was bigger than 20xx X 10xx but apparently it's not that way.
If g3gg0 figures out something from the sensor logger.. maybe.. good luck recording it tho.. 1080P or 1038 is about where it maxes write speed. Would help for silent pics.. hopefully no more corruption on those.
Quote from: 1% on June 22, 2013, 08:10:35 PM
If g3gg0 figures out something from the sensor logger.. maybe.. good luck recording it tho.. 1080P or 1038 is about where it maxes write speed. Would help for silent pics.. hopefully no more corruption on those.
Yes but if there were 2560 for example, and you could still get 80mb/s, that would make 2560x780@24 or for a more useful format 1:2.50 would give theoretical 2234x893@24.
Anyway, it's just daydreaming ^^.
Yea, not a bad plan. Hopefully something will get found out. Right now its just speculation :(
I'm getting these kind of frames when the card is full and camera stops recording
(http://lh6.googleusercontent.com/-UWrYhOFg4uQ/UcbNQc4y9yI/AAAAAAAACGc/EhZb3qcO8ck/s1024/M20-2050_00106.jpg)
I'm shooting with the last june 20 build and a 60MB/s sandisk extreme card. Recording about 380-450 frames before the camera stops recording.
Quote from: simulacro on June 23, 2013, 12:34:55 PM
I'm getting these kind of frames when the card is full and camera stops recording
[spoiler](http://lh6.googleusercontent.com/-UWrYhOFg4uQ/UcbNQc4y9yI/AAAAAAAACGc/EhZb3qcO8ck/s1024/M20-2050_00106.jpg)[/spoiler]
I'm shooting with the last june 20 build and a 60MB/s sandisk extreme card. Recording about 380-450 frames before the camera stops recording.
What all raw videos look like this or just the last one?
with 1%s latest build 80point1 i get nearly 80 MB/s writing speed in 1920x1072 @ 24 fps on a 64 GB Komputerbay x1000 card.
the first frame is in 80% of the files okay. all other frames are completely pink. in every .raw file.
tried different drawing modes in 1:1 crop mode but has no effects for me. uncropped mode is flawless.
in other posts i read this is a issue for a lot of people, but there are reports only a few files are corrupted.
what raw unpacker do you guys use?
i´m using raw2cdng 1.1.6 (lowering white levels has no effect since the whole image is affected)
tried to swap rgb channels. no correct solution.
My battery ends up very quick in RAW recording, is it normal?
Quote from: crash-film on June 23, 2013, 02:27:31 PM
with 1%s latest build 80point1 i get nearly 80 MB/s writing speed in 1920x1072 @ 24 fps on a 64 GB Komputerbay x1000 card.
the first frame is in 80% of the files okay. all other frames are completely pink. in every .raw file.
tried different drawing modes in 1:1 crop mode but has no effects for me. uncropped mode is flawless.
in other posts i read this is a issue for a lot of people, but there are reports only a few files are corrupted.
what raw unpacker do you guys use?
i´m using raw2cdng 1.1.6 (lowering white levels has no effect since the whole image is affected)
tried to swap rgb channels. no correct solution.
I managed to fix it but the downside is that it might cause the same 'pink' issues with silent pics. https://bitbucket.org/andy600/andy50d/downloads/Andy600.50D.ML.Border.Fix.Test.Build.Not.Official.zip This is based on Unified code and doesn't have 1%'s cache hack for increasing speed so you're not gonna get 81MB/s.
I'm currently testing 1%'s new code. I'm sure he will upload a build when we're sure it's working.
As for your pink footage, the video I shot in 1080p also had pink frames. It's easily remedied in Davinci Resolve Lite. Just use auto-color in the first node (it's the round 'A' button in the color wheels panel) and then apply CC, sharpening etc (be sure to set it to Black Magic Film in Raw Camera settings).
Quote from: galaxy on June 23, 2013, 03:30:58 PM
My battery ends up very quick in RAW recording, is it normal?
How old is you battery? What are it's voltage and mAh?
It's original 50D's battery 1400mah 7.4v as i remember. I didn't noticed that it discarged fast in regular use, but in raw recording i have about 5-10 min. It's quite old, 2 year. How long your battery lives in raw? Maybe my battery is just old, i don't know.
Quote from: Andy600 on June 23, 2013, 01:41:30 PM
What all raw videos look like this or just the last one?
Only the last clip, when the card is full. If I erase one clip and record anything, the same error. Something between 3-15 frames with those weird lines at the end of the clip
Quote from: galaxy on June 23, 2013, 03:58:15 PM
It's original 50D's battery 1400mah 7.4v as i remember. I didn't noticed that it discarged fast in regular use, but in raw recording i have about 5-10 min. It's quite old, 2 year. How long your battery lives in raw? Maybe my battery is just old, i don't know.
How long does it last in regular movie mode? Raw video does seem a bit power hungry but I have a 5 year old battery that lasts about 20 mins. I would advise getting a new battery or better still get a couple. I bought 2 cheap replacement 1600 mAh 7.4v unbranded after-market batteries and they give me about 40 mins each. My card can get filled and formatted several times on one charge.
Quote from: simulacro on June 23, 2013, 04:05:12 PM
Only the last clip, when the card is full. If I erase one clip and record anything, the same error. Something between 3-15 frames with those weird lines at the end of the clip
Maybe try stopping recording manually before the card maxes out. It should show a warning when your card is full?
Quote from: Andy600 on June 23, 2013, 04:08:25 PM
Maybe try stopping recording manually before the card maxes out. It should show a warning when your card is full?
Yeah, i see the warning, something like "there is an error, maybe the card is full"
the clips with the error:
http://www.youtube.com/watch?v=Gc49OhjJPJQ&feature=youtu.be
The free space doesn't update for a while. I know because I keep refilling /deleting the card.
thank you andy!
pretty frustrating since i use resolve for a while, but somehow the images come pretty dirty and noisy in resolve.
i still prefer ACR, it is much slower but the images are a lot cleaner.
or is this all just a preview/real time issue of resolve?
using 1%s side effects build the pink images are gone for some image size settings. will keep testing on this.
what´s the reason for the pink? is it a recording or a decoding/debayering issue?
Andy, with your build i have to take the battery off every time after i switch off the camera in order to make it working again...
Just want to let you know :)
This is what I'm running now:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B50D%5D%20ShutterCrashFx.zip
Quote from: Viente on June 23, 2013, 04:40:10 PM
Andy, with your build i have to take the battery off every time after i switch off the camera in order to make it working again...
Just want to let you know :)
Thanks. Not happening on my camera. Maybe delete all your config files.
Try 1%'s new build. It's working well here with dialog timers disabled in the menu (set before switching to Live View)
1%, the last frame of the footage appears corrupted on your latest build here...Plase let me know if you need more info.
Running footage through Davinci Resolve is clean plus it gives you the option to convert to Film Log mode which is a plus.
Quote from: goldenchild9to5 on June 23, 2013, 05:38:46 PM
Running footage through Davinci Resolve is clean plus it gives you the option to convert to Film Log mode which is a plus.
Not to mention the waaaay better sharpening, upscaling, anti-aliasing etc. The tracker is also amazing for image stabilization and for using chroma blurring (in a window or a qualified selection) to reduce moire if a shot has it. ;)
Quote from: Andy600 on June 23, 2013, 05:42:15 PM
Not to mention the waaaay better sharpening, upscaling, anti-aliasing etc. The tracker is also amazing for image stabilization and for using chroma blurring (in a window or a qualified selection) to reduce moire if a shot has it. ;)
Noticeable improvement to footage when at export you choose "Force to highest res" and "force debayer to highest quality."
1% - random OT thought: I wonder if it's possible to take picture styles out of the equation when recording H.264. i.e. switch them off. This, as i understand is done prior to encoding; so could the pre-encoder feed be intercepted to do this? If so, we would have H.264 footage that matches raw video (albeit compressed and 8bit).
Quote from: artiswar on June 23, 2013, 05:47:46 PM
Noticeable improvement to footage when at export you choose "Force to highest res" and "force debayer to highest quality."
Yes, I do that by default. TBH no NLE that I have used comes close to the quality you can get (with a bit of work) from Resolve.
Sorry if I've missed something, but when I try any of the builds more recent than about June 15th my raw write speeds have dropped to 35-45Mb/s at 1x crop, largest image size. I've reformatted cards, rebuild core ML, used all the settings that were working before (Global Draw:LiveView, fps override, etc.) -- still it seems odd. (KompBay 64G 1K card). There was an Andy600 build with a 'fast_raw' that worked fine - then I moved to the mainstream builds and I'm going backwards. I'm hoping that I might have missed something obvious and that someone might set me straight.
I've searched for answers and read all the posts under this topic.
Many thanks,
D
Quote from: dhallowell19 on June 23, 2013, 05:52:42 PM
Sorry if I've missed something, but when I try any of the builds more recent than about June 15th my raw write speeds have dropped to 35-45Mb/s at 1x crop, largest image size. I've reformatted cards, rebuild core ML, used all the settings that were working before (Global Draw:LiveView, fps override, etc.) -- still it seems odd. (KompBay 64G 1K card). There was an Andy600 build with a 'fast_raw' that worked fine - then I moved to the mainstream builds and I'm going backwards. I'm hoping that I might have missed something obvious and that someone might set me straight.
I've searched for answers and read all the posts under this topic.
Many thanks,
D
If you want speed see Reply #1760 ;)
May be possible to cache hack away the picture style step.. but I don't think it will help make it any more raw_like.
Quote
1%, the last frame of the footage appears corrupted on your latest build here...Plase let me know if you need more info.
You mean the very last frame? Its supposed to cut that off? Or it cuts off 1 and the one before that is corrupted?
Quote from: 1% on June 23, 2013, 05:58:14 PM
May be possible to cache hack away the picture style step.. but I don't think it will help make it any more raw_like.
Not for resolution or color depth of course but it should match raw's colors no? I'm just curios to see what a no-picture-style, post encoded compressed image looks like. It would be linear wouldn't it?
hmmm......okay.
but do you also have the problem of flickering images in resolve? every now and then theres a heavily darker image.
and there´s some blue and red noise at the image borders.
sorry for my questions but visually ACR gives me from the start less noise and since ACR is optimized for photo camera raw and the different raw interpretation methods of ACR changed during the last years noticeable. i think there´s a lot of optimization going on in the background. also not to forget the easy possibility to remove CA.
but i´ll continue experimenting with resolve.
edit: just compared one shot in ACR to resolve. somehow pink (maybe) dead pixels visible in resolve are gone via ACR.
Quote from: crash-film on June 23, 2013, 06:03:50 PM
hmmm......okay.
but do you also have the problem of flickering images in resolve? every now and then theres a heavily darker image.
and there´s some blue and red noise at the image borders....
I've not noticed that on any raw footage I've put through Resolve. Did you set camera raw to BMD Film etc? ACR is known to cause flicker. I don't use it at all. I denoise in AE and lens choice/settings helps with CA.
I convert to 12bit Cinema DNG btw.
It won't match the raw colors, the conversion to 8 bit is what messes it up and you can't take that out.
Quote from: crash-film on June 23, 2013, 06:03:50 PM
hmmm......okay.
but do you also have the problem of flickering images in resolve? every now and then theres a heavily darker image.
and there´s some blue and red noise at the image borders.
crash, I used to have the same issue with Resolve (flicker + glitches at the upper border). Replaced my Resolve with the latest Lite version from BMD site -- the issues are gone.
cool rommex. will give it a try.
but there´s no noise reduction in the free version, no tracker.....or did they change that?
i made three short test videos (with the 550D, see in my posts) and all happened in after effects through acr. and i never had flickering issues.
andy600:
yes, i used all the bmd settings (is it somehow confirmed, that bmd settings are correct. or does it just "fit" somehow?)
maybe i´ll get some stable shots today. have some charts and gray boards here and try to get some comparable images and maybe generate a LUT for the 50D. time to take that book of the shelf..... color correction handbook ......good extra reference for resolve!
just need to finally read it :P
Quote from: crash-film on June 23, 2013, 06:43:09 PM
cool rommex. will give it a try.
but there´s no noise reduction in the free version, no tracker.....or did they change that?
i made three short test videos (with the 550D, see in my posts) and all happened in after effects through acr. and i never had flickering issues.
andy600:
yes, i used all the bmd settings (is it somehow confirmed, that bmd settings are correct. or does it just "fit" somehow?)
maybe i´ll get some stable shots today. have some charts and gray boards here and try to get some comparable images and maybe generate a LUT for the 50D. time to take that book of the shelf..... color correction handbook ......good extra reference for resolve!
just need to finally read it :P
No NR but everything else is there including the Tracker. BMD Film settings just seem to work for me (and quite a few others it seems) and I'm using Arri LUTs for a base to grade from. The BM Film LUT is nice too but saturation needs toning down a touch.
Quote from: Andy600 on June 23, 2013, 06:50:51 PM
No NR but everything else is there including the Tracker. BMD Film settings just seem to work for me (and quite a few others it seems) and I'm using Arri LUTs for a base to grade from. The BM Film LUT is nice too but saturation needs toning down a touch.
yeah, two arguments for me for ACR.
NR is a must for raw files. and ACR has the correct canon image settings.
everything´s of course in a very early stage of development and for now it´s okay to drop just any lut on the footage just to get things working. but a lut is a very powerful component. and you can be assured that a arri alexa lut also corrects some flaws of the alexa sensor. what´s good for the alexa or bmd cams can for example emphasize noise with the canon dngs or it provokes false colors. and a grade based on false colors can get pretty uncontrollable.
resolve will be the future first choice. no doubt.
just can´t wait to see resolve 10!
could be the perfect way of avoiding any intermediate format.
Quote from: 1% on June 23, 2013, 05:58:14 PM
May be possible to cache hack away the picture style step.. but I don't think it will help make it any more raw_like.
You mean the very last frame? Its supposed to cut that off? Or it cuts off 1 and the one before that is corrupted?
Yes, the very last frame
This is what i've got
(http://i.imgur.com/I8QbK0X.jpg)
I don't know anything about LUTs but with my last shoot i'm aplying to the raw pics the prolost flat principle in Camera Raw: putting all the contrast to the left (-50), the same with the black level (0). i don't touch the brightness or exposure unless the image needs it. I'll post soon a little video using these settings. Hope don't mess it :o
Quote from: crash-film on June 23, 2013, 07:07:24 PM
yeah, two arguments for me for ACR.
NR is a must for raw files. and ACR has the correct canon image settings.
everything´s of course in a very early stage of development and for now it´s okay to drop just any lut on the footage just to get things working. but a lut is a very powerful component. and you can be assured that a arri alexa lut also corrects some flaws of the alexa sensor. what´s good for the alexa or bmd cams can for example emphasize noise with the canon dngs or it provokes false colors. and a grade based on false colors can get pretty uncontrollable.
resolve will be the future first choice. no doubt.
just can´t wait to see resolve 10!
could be the perfect way of avoiding any intermediate format.
Of course. Creating a calibrated raw-to-Log or raw-to-REC709 LUT for ML raw video footage would need scopes and measuring equipment. It's a science and I only know the basics ATM. I only use the BMD or Arri ones as a quick 'look' and a useful base to grade from. If I was doing any serious work I would probably grade without one (but I don't do any serious work LOL).
It would be useful to make some 50D specific FPN presets for neat video. Has anyone done that yet?
Quote
Yes, the very last frame
This is what i've got
Do you have that quick ramp up on? Its basically happening when raw is stopping, not much I can do, just write off last 2 or 3 frames (a1ex already cuts the last one I think).
No, i've just reset all settings and tried again. The same thing.
Not a big deal actually, just want to report as much as i can :)
Question for all of you:
Is there a way to save settings for when the cam powers on? Ie, raw on, res set, sound off, memory hack on?
Yea, it does that.
I'll see if anything makes it go away... refreshes, pause resume LV, etc all can corrupt a frame. I've had some in the first couple frames before and I guess now the last couple :( I'd rather it be at the end tho, haven't seen anything corrupt at start recently.
so....the latest version of resolve works. but theres still an issue with dabayering i think. or some superblack issues?? lots of red pixels in the blacks. and acr seems to have an automatic hot pixel remover.
i made some testhots using an old esser gray scale test chart. resolves bmd preset + the auto correction of resolve gives pretty similar results than acr+after effects.
when i generate a lut using the grade settings everything explodes (pixel mismatch, overexposure...)
is anybody working on that pink frame issue? i don´t trust there any "fix it in post" approaches.
Quote from: dhallowell19 on June 23, 2013, 05:52:42 PM
Sorry if I've missed something, but when I try any of the builds more recent than about June 15th my raw write speeds have dropped to 35-45Mb/s at 1x crop, largest image size. I've reformatted cards, rebuild core ML, used all the settings that were working before (Global Draw:LiveView, fps override, etc.) -- still it seems odd. (KompBay 64G 1K card). There was an Andy600 build with a 'fast_raw' that worked fine - then I moved to the mainstream builds and I'm going backwards. I'm hoping that I might have missed something obvious and that someone might set me straight.
I've searched for answers and read all the posts under this topic.
Many thanks,
D
My process for a cap of 77.7mb/s @ 1920x1080 @ 24fps on a 32GB Komputerbay 1K on 1%'s most recent posted on last page;
Boot camera
Format card
Set all desired settings for recording (FPS, Overlays, Resolution, pretty much just set up your shot now)
To set 1920x1080; In LV go to 5X Zoom, set Aspect Ratio to 16:9 and Resolution to 1920x1080 in RAW Video settings in ML settingsPower down camera
Boot camera
Open ML menu
Navigate to Debug tab
Scroll down to Dialog Timers and set to Disabled
Open LiveView
Record your first shot @ no crop and let the speed peak (I usually let it sit for a minute)
Zoom to 5x and record your new 1920x1080 shot
Hope this helps. And to the smarter ups, does disabling the Dialog Timer have any negative impact?
Quote from: dsManning on June 23, 2013, 10:30:51 PM
My process for a cap of 77.7mb/s @ 1920x1080 @ 24fps on a 32GB Komputerbay 1K on 1%'s most recent posted on last page;
Boot camera
Format card
Set all desired settings for recording (FPS, Overlays, Resolution, pretty much just set up your shot now)
Power down camera
Boot camera
Open ML menu
Navigate to Debug tab
Scroll down to Dialog Timers and set to Disabled
Open LiveView
Record your first shot @ no crop and let the speed peak (I usually let it sit for a minute)
Zoom to 5x and record your new 1920x1080 shot
Hope this helps. And to the smarter ups, does disabling the Dialog Timer have any negative impact?
Finally step by step guide for n00bs. It would save me a lot of time if it was on the very first post of this thread, also I'd add URL for ML build and guide how I could increase resolution above 1584.
Thanks!
Granted, you don't need to format every time. This is just the process I use for speedtests on new builds.
Quote from: dsManning on June 23, 2013, 10:30:51 PM
My process for a cap of 77.7mb/s @ 1920x1080 @ 24fps on a 32GB Komputerbay 1K on 1%'s most recent posted on last page;
Boot camera
Format card
Set all desired settings for recording (FPS, Overlays, Resolution, pretty much just set up your shot now)
Power down camera
Boot camera
Open ML menu
Navigate to Debug tab
Scroll down to Dialog Timers and set to Disabled
Open LiveView
Record your first shot @ no crop and let the speed peak (I usually let it sit for a minute)
Zoom to 5x and record your new 1920x1080 shot
Hope this helps. And to the smarter ups, does disabling the Dialog Timer have any negative impact?
Guys....I am still lost......not able to make any RAW recording, I am just getting video recording, a .MOV file each time i tried to record RAW, I will describe what i am doing and will appreciate somebody help me with the missed steps...
1. updated firmware and loaded ML 2.3 in the camera, get the green screen at the end, everything looks OK.
2. downloaded last build from @gregory
3. removed CF card and plug it into de computer (didn`t format the card after ML 2.3 was loaded)
4. deleted autoexec.bin and ML directory from the card
5. copy new autoexec.bin and ML directory from last @gregory build
6. removed card from computer and inserted in the camera, turn on camera
7. enter to ML menu, go to Movie tab and in field Movie Record only have two options.....1920x1080, 30 fps and 640x480, 30 fps
8. go to help tab and see ML version showed is the last build from @gregory
9. go to liveview and shoot
10. turn off, remove CF and plug in into the PC, I only see a file with extension .mov, just a video.....
Any help will be much appreciated!!!! (I am so noob in canon and ML)...thanks
Quote from: hijodeibn on June 23, 2013, 11:25:20 PM
Guys....I am still lost......not able to make any RAW recording, I am just getting video recording, a .MOV file each time i tried to record RAW, I will describe what i am doing and will appreciate somebody help me with the missed steps...
Any help will be much appreciated!!!! (I am so noob in canon and ML)...thanks
Far right tab in ML menu is Modules. You need to enable the modules included in the build (most importantly the RAW one for this, but enable all of them)
Then go back to Movie tab and at the bottom, you will see RAW Video. Turn on and enjoy :)
Quote from: dsManning on June 23, 2013, 11:28:03 PM
Far right tab in ML menu is Modules. You need to enable the modules included in the build (most importantly the RAW one for this, but enable all of them)
Then go back to Movie tab and at the bottom, you will see RAW Video. Turn on and enjoy :)
Finally......RAW in camera....many thanks!!!!!!!!
Quote from: simulacro on June 23, 2013, 12:34:55 PM
I'm getting these kind of frames when the card is full and camera stops recording
(http://lh6.googleusercontent.com/-UWrYhOFg4uQ/UcbNQc4y9yI/AAAAAAAACGc/EhZb3qcO8ck/s1024/M20-2050_00106.jpg)
I'm shooting with the last june 20 build and a 60MB/s sandisk extreme card. Recording about 380-450 frames before the camera stops recording.
Now the last frame of every clip I record is like the above. When the card gets full it's more, the clip with more weird frames has 64 of them. I have to say, as having a slow card (60MB/s) I record until the camera stops automatically (290-400 frames)
Gonna format the card to see what happens
Quote from: Viente on June 23, 2013, 07:07:52 PM
Yes, the very last frame
This is what i've got
(http://i.imgur.com/I8QbK0X.jpg)
I opened my clips with raw2dng and my last frame looks like Viente's.
with rawmagic all the last frames look like a bar code
(https://lh6.googleusercontent.com/-UWrYhOFg4uQ/UcbNQc4y9yI/AAAAAAAACGc/EhZb3qcO8ck/s1152/M20-2050_00106.jpg)
The new build's interface has "buffer use"(?) lines above the raw frame counter, and for me, they look similar to the vertical lines of the last frame (from rawmagic). Can these interface lines be related to the line error?
(https://lh4.googleusercontent.com/-g0Y-XnWM_Yg/UciAVGYzm6I/AAAAAAAACIE/yR8jq3I761k/s912/2013-06-24%252018.19.05.jpg)
Quote from: simulacro on June 24, 2013, 07:31:26 PM
The new build's interface has "buffer use"(?) lines above the raw frame counter, and for me, they look similar to the vertical lines of the last frame (from rawmagic). Can these interface lines be related to the line error?
I'm sure those buffer lines have nothing to do with the last frames being corrupted.
Didn't 1% already comment on this earlier?-
Quote from: 1% on June 23, 2013, 07:30:35 PM
Its basically happening when raw is stopping, not much I can do, just write off last 2 or 3 frames (a1ex already cuts the last one I think).
Just don't use the last frames of your clip?
Yea basically, if its 60 bad frames then we have to find whats wrong... if its like 1 or 3, just cut them off.
hello
I was wondering how long can the 50d record at 1080p or near 1080p resolution?
thank you.
Until your card runs out.... like 15 minutes max on 64 card.
Question: since 5x zoom multiplies field of view by 5x times what lens mm on a crop sensor would I need to achieve 50mm? Something like fisheye?
Quote from: 1% on June 24, 2013, 10:33:46 PM
Until your card runs out.... like 15 minutes max on 64 card.
ahh excellent
its not like there's a 400 frames then it stops?
on the 5dmk2 I can do 1720 continuous which is great though getting a 50d for under $400 is an additional plus
I'm currently shooting a short film with the 5DM3 Raw at 1920x1080. The image is great, but there's just something about the image from my 50D that I love. I would like to bring the 50D onboard as a 2nd camera, but am concerned about the two resolutions mixing well together, not to mention the 50D moire. Do you all think the 50D footage upscaled to 1920x1080 will be consistent with my 5DM3's 1920x1080 footage?
Zoom won't need much upscale. I don't think it has moire in zoom.
Quote from: djfremen on June 24, 2013, 11:17:37 PM
Question: since 5x zoom multiplies field of view by 5x times what lens mm on a crop sensor would I need to achieve 50mm? Something like fisheye?
The thing goes like this, 5x zoom is actually 3x additional crop (please correct me if I'm wrong), then there is the 1.6x canon aps-c crop.
So 50/3/1.62= 10.28mm lens will give you a 50mm equivalent fov, depth of field will be the same as on a 10mm lens, so no shallow depth of field.
That would make it slightly smaller than a 1/1.7" sensor area which has a crop factor of 4.55x compared to the 4.86x crop from the 5x zoom mode. I don't know if it exists, but if you put a m43 7-14mm lens on this you could get a 34-68 lens which should be ok for most shots.
Quote from: araucaria on June 24, 2013, 11:58:50 PMdepth of field will be the same as on a 10mm lens, so no shallow depth of field.
Oy- that's rough.
The Canon EF-S 10mm - 22mm F/3.5 - 4.5 USM Lens is 600 bucks used.
So everything would be in focus, with no DoF, unless you shot macro ;)
Quote from: 1% on June 24, 2013, 11:56:43 PM
Zoom won't need much upscale. I don't think it has moire in zoom.
There could be moire, but the 50d has a very strong aliasing filter so I don't think it will ever show up.
Btw, does anybody know if the 5x is really a 3x crop, and if the same applies on the 5dmkii.
You can always upscale the 15XX*10XX... people had luck with even 2x upres.
tonight i catched the moon!
I have a soviet lens that wanted to sell but i think i'm gonna keep it :)
5x video. with my sandisk extreme 60MB/s i only could record 13 second clips aprox, still, very impressive
http://www.youtube.com/watch?v=FrByg6Ke9_c&feature=youtu.be
This is a short music video I shot in Thailand last week on the 50d with one of the earlier June builds. Enjoy!
Quote from: sschwartz23 on June 25, 2013, 03:47:41 AM
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?
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.
Lol at that video
Quote from: sschwartz23 on June 25, 2013, 04:05:58 AM
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.
Quote from: simulacro on June 25, 2013, 02:17:51 AM
tonight i catched the moon!
I have a soviet lens that wanted to sell but i think i'm gonna keep it :)
5x video. with my sandisk extreme 60MB/s i only could record 13 second clips aprox, still, very impressive
http://www.youtube.com/watch?v=FrByg6Ke9_c&feature=youtu.be
Nice MOON :D
Quote from: sschwartz23 on June 25, 2013, 03:47:41 AM
This is a short music video I shot in Thailand last week on the 50d with one of the earlier June builds. Enjoy!
Nice video. Nice color grading :D
Quote from: pinger007 on June 24, 2013, 11:37:42 PM
I'm currently shooting a short film with the 5DM3 Raw at 1920x1080. The image is great, but there's just something about the image from my 50D that I love. I would like to bring the 50D onboard as a 2nd camera, but am concerned about the two resolutions mixing well together, not to mention the 50D moire. Do you all think the 50D footage upscaled to 1920x1080 will be consistent with my 5DM3's 1920x1080 footage?
I said the same thing that's why I went with the 50D there is something magical going on with the images coming out of that camera. I think the images will intercut pretty well, to tell you the truth I haven't been experiencing that much moire on my footages should be all fine..
Quote from: sschwartz23 on June 25, 2013, 03:47:41 AM
This is a short music video I shot in Thailand last week on the 50d with one of the earlier June builds. Enjoy!
Great video man.. nice grade also, you made the 50D shine. By the way what lens did you use?
Thanks!
I used the Canon L-series 28-70 f2.8 and a Samyang 14mm f2.8 for the wides...
Quote from: sschwartz23 on June 25, 2013, 03:47:41 AM
This is a short music video I shot in Thailand last week on the 50d with one of the earlier June builds. Enjoy!
I see lot's of RRRAWWW posibilities on your video ;)
Very nice! congratulations!
The first shot is beautiful. The other shots... i was staring at two specific spots so I don't really know ;D
Quote from: sschwartz23 on June 25, 2013, 08:26:01 AM
Thanks!
I used the Canon L-series 28-70 f2.8 and a Samyang 14mm f2.8 for the wides...
I saw i very nice use of the zoom in - out movement. I tried once with a 24-105 and it wasn't soft at all
when I shoot with the 50D, I definitely get considerable moire (haven't tested in crop mode). This moire makes it unusable for the film unless it's used solely for facial close ups. However, if I can utilize the crop mode free of moire, then I've got myself a good b cam. My only issue is that the liveview framing in crop mode isn't correct - it's showing a much smaller fov compared to what the camera is actually capturing. I've tried different preview modes (auto, canon, magic lantern grayscale, hacked), but none of them seem to fix the problem. Am I missing something? Please help.
If I understood correctly, there's no way to get FHD at 1:1, only on 5x crop.
Is it a hw constraint or is it being worked on?
Is it even worth the development effort, to use a small fraction of the 50D sensor (effectively turning 50D into a tiny sensor, consumer level camcorder), RAW or not? (I am talking about zoom RAW recording.) With a tiny sensor, you lose most of the advantages of the DSLR-based video-camera - shallow DoF and great light sensitivity.
numbers may change but the frames remain the same.
today's builds include code changes to bitrate calculations - so the numbers may display differently than before.
you can compare performance with past builds by maximum frames under some settings (1920x1080 @23.976) or maximum continuous recording at your favorite aspect ratio.
(for the super speed builds, it's looked to me as if the numbers on screen were less than the required bitrate - e.g. 1920x1080p23.976 should be closer to 83MB/s and the 80point1 build reported around 80.1)
@Rawolution - enjoy 1600 maximum width in regular raw video mode - that is it.
@pinger007, @rommex (and the whole moire gang) - i wouldn't go so far as to say unusable - you have to decide where to use it. it will present issues in environments with regular patterns and hard thin lines. for myself, i did some camera tests to see a range of conditions.
included a not great panning city scape to show the moire.
at 25second far left top corner the windows have a crazy multicolor pattern,
the rooftops to the left of the Allianz building show some strange flickering digital artifacts which i think is caused by antennas.
the side of the dark brick building center frame at 35second has very visible moire.
in resolve lite, i tried to separate luma and chroma and to blur the chroma to reduce at least the rainbow portions of the moire pattern. all these things look worse at full resolution viewing the cinemaDNGs - the silver lining in all the compression to post videos online is that the apparent problems are reduced.
the earlier shots of the trees could have been processed (perhaps by masking the backs of the trees or could i have keyed on the tree bark color?) to keep the dark detail in a very wide dynamic range shot.
(note: uploaded a 444 prores with vimeo compression and somewhere - this vimeo gamma is much darker from what i saw on screen - at my limit for the week of uploads - so cannot be replaced)
looks to me like the 50D image can be sharpened and look very nice on organic natural shots - trees, forest , ocean, etc...
a deep focus city shot is going to require post work to reduce the moire.
basically you need to limit depth of field in a city or room with patterns.
the final shot show crop/ zoom mode at 105mm looking at one world trade center (4.2miles / 6.7km ) and 1 penn plaza (1.3 miles / 2.3 km) distance.
@rommex - you may like a documentary film "crumb" (1994) - it shows an artistic interpretation of telephone and power cables.
Hi there, I'm new and find all this amazing. I'm trying to use the 50d to shoot 4:3 for Anamorphic as high res as I can get without crop. I can't get a continuous bit rate of more than 50MB/s though. I'm using Gregory of Manhattan's 70MB/s 9th June build and a Lexar 800x card. I've tried with memory hack on and off but can't seem to get over 50. Best resolution I got was 1152 x 854 and even then all the frames were corrupted like "the last few frame" corruptions on an earlier post I saw. Not sure what I'm doing wrong, any ideas?
Thanks
Quote from: pulsar124 on June 25, 2013, 04:23:16 PM
Is it even worth the development effort, to use a small fraction of the 50D sensor (effectively turning 50D into a tiny sensor, consumer level camcorder), RAW or not? (I am talking about zoom RAW recording.) With a tiny sensor, you lose most of the advantages of the DSLR-based video-camera - shallow DoF and great light sensitivity.
of course it is!
in crop mode you get a 1:1 pixel representation. yeah, it is just a pretty tiny fraction of the sensor size. but it´s fine for establishing shots or high detail images.
from a technical point of view there should be no difference in dynamic range or sensitivity. just noise could be a little bit more noticeable.
for your shallow dop needs you can use the non crop resolutions. faces or close ups of organic things without sharp edges work perfectly.
to avoid aliasing in sound recorded with low sampling frequency ( to record a frequency range between 20 hz and 20 khz the sampling frequency has to be 40 khz according to shannon-nyquist)
there´s something called noise shaping. maybe turning the iso levels up to generate a strong random noise pattern could help prevent edge aliasing.
could be a reason why some people report moire reduction after applying noise reduction.
this method can also be used to avoid bending in your web videos: just ad a little amount of noise to your videos.
the encoder (mostly h264) detects the noise as detail and lowers its macroblocking giving smoother gradients in large flat surfaces (skies etc.)
the magical images from the 50D are in my opinion a result of the "low" resolution chip. a 50D with a 10 or 12 MP sensor would give you even better images. the 50D was called a pixel over kill when it was released. if they built in a lower res sensor with bigger sensel size dynamic and low light performance could even be better. but the 50Ds sensor was quite unique at that time. the first one without real spaces between the sensels.
and if i understand the live view down scale line skipping right, there would be less line aliasing as a result of less lines needed to be skipped.
is this correct?
so theoretically the 40D would give better line-aliasing results.
moire can only be solved in cam with an optical low pass filter since the visible moire effect is just a result of the nyquist-shannon theoreme. every image sensor has its high frequency limits (high frequencies meaning small image details).
a lower res chip can be the solution for micro moire.
an ideal cam would have a full frame 35 mm faveon (or 3 chip) style sensor with the exact pixel count you want to shoot and a specially designed LPF.
this is the reason why the 5DIII is so good for video: good LPF and a sensor pixel count that´s ideal for downscaling.
did some tests with the moire reduction in ACR. works pretty good in special cases!
Quote from: GregoryOfManhattan on June 25, 2013, 04:56:15 PM
numbers may change but the frames remain the same.
today's builds include code changes to bitrate calculations - so the numbers may display differently than before.
you can compare performance with past builds by maximum frames under some settings (1920x1080 @23.976) or maximum continuous recording at your favorite aspect ratio.
(for the super speed builds, it's looked to me as if the numbers on screen were less than the required bitrate - e.g. 1920x1080p23.976 should be closer to 83MB/s and the 80point1 build reported around 80.1)
@Rawolution - enjoy 1600 maximum width in regular raw video mode - that is it.
@pinger007, @rommex (and the whole moire gang) - i wouldn't go so far as to say unusable - you have to decide where to use it. it will present issues in environments with regular patterns and hard thin lines. for myself, i did some camera tests to see a range of conditions.
included a not great panning city scape to show the moire.
at 25second far left top corner the windows have a crazy multicolor pattern,
the rooftops to the left of the Allianz building show some strange flickering digital artifacts which i think is caused by antennas.
the side of the dark brick building center frame at 35second has very visible moire.
in resolve lite, i tried to separate luma and chroma and to blur the chroma to reduce at least the rainbow portions of the moire pattern. all these things look worse at full resolution viewing the cinemaDNGs - the silver lining in all the compression to post videos online is that the apparent problems are reduced.
the earlier shots of the trees could have been processed (perhaps by masking the backs of the trees or could i have keyed on the tree bark color?) to keep the dark detail in a very wide dynamic range shot.
(note: uploaded a 444 prores with vimeo compression and somewhere - this vimeo gamma is much darker from what i saw on screen - at my limit for the week of uploads - so cannot be replaced)
looks to me like the 50D image can be sharpened and look very nice on organic natural shots - trees, forest , ocean, etc...
a deep focus city shot is going to require post work to reduce the moire.
basically you need to limit depth of field in a city or room with patterns.
the final shot show crop/ zoom mode at 105mm looking at one world trade center (4.2miles / 6.7km ) and 1 penn plaza (1.3 miles / 2.3 km) distance.
@rommex - you may like a documentary film "crumb" (1994) - it shows an artistic interpretation of telephone and power cables.
Beautiful images.. keep up the great work you turned the 50D into a beast :D You used Davinci to process the footage right?
Hey 50D community I had an idea to put together a collaborative project for the 50D, mainly to showcase the power of the camera. It can also be a learning ground for new comers, and educational platform to share settings, shooting styles, tricks, and most importantly workflows & color grading. Let me know if it's something you all would be interested in, I think we all have a common goal to get the best possible images out of the 50D and turn it into a movie make machine Cheers..
GOD Bless
Quote from: goldenchild9to5 on June 25, 2013, 06:11:26 PM
Hey 50D community I had an idea to put together a collaborative project for the 50D, mainly to showcase the power of the camera. It can also be a learning ground for new comers, and educational platform to share settings, shooting styles, tricks, and most importantly workflows & color grading. Let me know if it's something you all would be interested in, I think we all have a common goal to get the best possible images out of the 50D and turn it into a movie make machine Cheers..
GOD Bless
Its a very good idea indeed!!!
Quote from: arrinkiiii on June 25, 2013, 06:21:01 PM
Its a very good idea indeed!!!
Thanks Arrinkiiii for being the first one to show interest I think that it would be a great collaborative platform, and very educational we can never stop learning right.. let's wait and see what the rest of the community thinks about it.
here´s some test footage including nearly almost wide shots. did not check all shots for moire.
but some are corrected via ACR moire reduction.
can´t upload to vimeo atm, so there´s just a 720p youtube version. original resolution is 1536x1056 and much cleaner and sharper.
did some upscale/downscale tricks to reduce line aliasing. pretty subtle. but the dark outlines of the buildings are nearly straight.
lens: canon 28mm 2.8 prime
workflow: as described in my 12 bit workflow post (very slow, but the final product is a robust 32bit exr sequence that renders to every format very fast)
updated to 1080p:
Okay so I'm up to 1154 x 864 in 4:3 but can't get the bitrate any higher for continuous shooting. Does this sound right? I'm using a Lexar 800x speed card with todays Gregoryofmanhattan's build. Any help to get me up to 1584 x 1068 would be greatly appreciated.
what size is your card supermac?
Heyho boys, just dropping in to say thanks for your awesome work, I've never would have imagined the possibilities lying in a 50D. Seriously, great job so far. I've managed to snag a body for $316, so hopefully I can help out with testing soon. (someone hack the post to teleport packages, the waiting's killing me lol)
Also, for anyone that wants to grab themselves a 50D, I'd advise to check the american and british ebay on a hourly basis, as quite a few bodies pop-up for buy it now under $380. Don't bother with the canadian, german, and austrian one's tho, the prices just skyrocket there (I've got mine from the uk).
On another note, if someone can't use amazon, Komputerbay Ltd is on ebay under the name of "fastflashstore", although the prices are a bit higher there... hope this helps someone.
It's only an 8GB card which I'm using as a quick test before forking out for a bigger card. Would this make a difference? Thanks
Quote from: Supermac on June 25, 2013, 08:32:46 PM
It's only an 8GB card which I'm using as a quick test before forking out for a bigger card. Would this make a difference? Thanks
yes, it makes a big difference. i tested the 16 GB x800 card and couldn´t get higher writing speeds than 40 MB/s.
changed to komputerbay 32 GB x1000 and now the 80 MB/s are no problem!!
i think the 8 GB card is even slower than the 16 GB. this cards may have a udma7 interface but they are slower on the inside so to speak.
i recommend you buy a komputerbay card. but only the x1000s
Quote from: crash-film on June 25, 2013, 08:49:42 PM
yes, it makes a big difference. i tested the 16 GB x800 card and couldn´t get higher writing speeds than 40 MB/s.
changed to komputerbay 32 GB x1000 and now the 80 MB/s are no problem!!
i think the 8 GB card is even slower than the 16 GB. this cards may have a udma7 interface but they are slower on the inside so to speak.
i recommend you buy a komputerbay card. but only the x1000s
Ok cool, I've got a 600x Duracel 32G which might work better for testing purposes. I guess I'll look at the Komputerbay one too. Hopefully I can post some footage if I get anything decent.
Here's a low light indoor test.
Quote from: nightvision04 on June 26, 2013, 02:01:09 AM
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.
Quote from: CaptainOfObvious on June 26, 2013, 02:55:46 AM
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.
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. :)
Quote from: nightvision04 on June 26, 2013, 03:47:05 AM
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?
Quote from: CaptainOfObvious on June 26, 2013, 04:23:52 AM
Hmm, I dont feel like I get even near that kind of lowlight performance on 1600, any noise reduction going on in resolve?
No.
Quick question re lens. I read that using FF Lens on a crop body like the 50d leads to softness in the video. Is this true in anyone's opinion? Sorry if this is a dumb question, I'm used to filming with dedicated video cams, not DSLR's.
What lens are people using besides the typical primes (30mm, 50mm)?
Also, anyone used a ewa lens like the canon 14mm with RAW?
Any comments would be great!
Quote from: nightvision04 on June 26, 2013, 03:47:05 AM
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. :)
Best cheap (really cheap) Canon lens for low light. I've tested against the 1.4 in quite a few settings and really haven't seen that considerable a difference for your price.
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.
http://www.youtube.com/watch?v=DYVq7W7tEh8 (http://www.youtube.com/watch?v=DYVq7W7tEh8)
(btw, song is not the original. Just picked a freebee off YouTube to make the video more bearable. So ignore a bit of sync if you will)
Quote from: flambe on June 26, 2013, 04:38:29 AM
I read that using FF Lens on a crop body like the 50d leads to softness in the video.
That is bullshit.
Quote from: flambe on June 26, 2013, 04:38:29 AM
Quick question re lens. I read that using FF Lens on a crop body like the 50d leads to softness in the video. Is this true in anyone's opinion? Sorry if this is a dumb question, I'm used to filming with dedicated video cams, not DSLR's.
What lens are people using besides the typical primes (30mm, 50mm)?
Also, anyone used a ewa lens like the canon 14mm with RAW?
Any comments would be great!
While specific crop sensor lenses will work better on crop sensors, a full frame lens should perform just as well on a crop sensor. Example: Contax Zeiss glass can cover the entirety of a RED Epic's 5k sensor, thus, with the resolution that a 50D can resolve should look stellar.
I'm loving my 11-16 on the 50D.
WOW! Just saw this thread. I have a 3 year old Canon 50D with Magic Lantern. However, I don't have this new version. Is the download for the latest ML for Canon 50D only found in the first page? I was thinking there might another download link posted embedded on a different page.
Check out my video which was recorded by Magic Lantern WITHOUT Raw support.
Any help would be greatly appreciated!
You guys are awesome! I've seen some video recordings and it is phenomenal! Awesome work!
Quote from: dsManning on June 26, 2013, 04:48:39 AM
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 : (
Quote from: v1rt on June 26, 2013, 05:12:19 AM
WOW! Just saw this thread. I have a 3 year old Canon 50D with Magic Lantern. However, I don't have this new version. Is the download for the latest ML for Canon 50D only found in the first page? I was thinking there might another download link posted embedded on a different page.
Check out my video which was recorded by Magic Lantern WITHOUT Raw support.
https://www.youtube.com/watch?v=SVHmU7Mn0lU
Any help would be greatly appreciated!
You guys are awesome! I've seen some video recordings and it is phenomenal! Awesome work!
Go to this link and you will find all the Raw Builds for the 50D, by the way nice video.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads)
Quote from: nightvision04 on June 26, 2013, 02:01:09 AM
Here's a low light indoor test.
Very nice also nice colors.
Quote from: goldenchild9to5 on June 26, 2013, 05:32:11 AM
Go to this link and you will find all the Raw Builds for the 50D, by the way nice video.
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads)
Thank you for the kind words. I'll try to update it tonight. I'll make a lot of test and will post it as well!!! :D
I will use the following lenses for my test
Asahi Takumar 50mm 1.4
Canon 70-200 F4L
Tamron 17-50mm f2.8
Sears 50mm 2.0
I'm so happy, I don't need to buy GH2. Glad I really saw this thread! :)
Quote from: CFP on June 26, 2013, 04:52:13 AM
That is bullshit.
Thanks. It sounded weird when I read it!
I guess everything you read on the Internet isn't true after all.
I got it installed on my 50D. Any ideas why recordings stops after few seconds? I even chose a smaller resolution like 1280x720, it still stops. Is there a setting that I forgot to turn off/on?
All I did was extract the file magiclantern-2013Jun25.50D.109.go.unified.282abfa87fef.zip onto my compact flash. I'm not sure if there are other files that I need to download.
Quote from: v1rt on June 26, 2013, 07:19:22 AM
I got it installed on my 50D. Any ideas why recordings stops after few seconds? I even chose a smaller resolution like 1280x720, it still stops. Is there a setting that I forgot to turn off/on?
All I did was extract the file magiclantern-2013Jun25.50D.109.go.unified.282abfa87fef.zip onto my compact flash. I'm not sure if there are other files that I need to download.
Well, what Compactflash Card do you have? :)
I woudtn't advice you to use the latest releases for non-test purposes. Besides short sequences, they have other malfunctions. That's why I still use 28May build )
Quote from: v1rt link=topicort hs=5586.msg55078#msg55078 date=1372223962
I got it installed on my 50D. Any ideas why recordings stops after few seconds? I even chose a smaller resolution like 1280x720, it still stops. Is there a setting that I forgot to turn off/on?
All I did was extract the file magiclantern-2013Jun25.50D.109.go.unified.282abfa87fef.zip onto my compact flash. I'm not sure if there are other files that I need to download.
Quotethey have other malfunctions.
Which ones? I'm not aware of any...
Can someone instruct me on how to record in crop mode? I get only about a split second of recording before it stops. Komputerbay 64gb 1000x
Quote from: Hokie123 on June 26, 2013, 11:29:48 AM
Can someone instruct me on how to record in crop mode? I get only about a split second of recording before it stops. Komputerbay 64gb 1000x
have you actually read this? http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
Also, no mention what build you are using? In another post you state you are only getting 45MB/s in your card benchmark. Read up on Benchmarking and then check your card alignment. You won't actually learn anything without following the steps yourself. If you learn how to correctly set up for raw video you will save yourself a ton of time in the future.
There is a whole section of this forum dedicated to raw video. Everything you get stuck on has already been answered.
http://www.magiclantern.fm/forum/index.php?board=49.0
In the latest build of 25 June after I have set ISO and trying to adjust exposure, changing aperture is fine but attempt to modify the shutter speed modifies ISO for some reason.... But the main drawback of this build is 2-3 seconds sequence and then skipped frame. While 28 May build works fine continuously. With all GD settings the same.
Quote from: a1ex on June 26, 2013, 11:19:03 AM
Which ones? I'm not aware of any...
Post a video showing the problems. Make sure you use the same config file for both (and paste it too).
Quote from: PressureFM on June 26, 2013, 11:10:43 AM
Well, what Compactflash Card do you have? :)
It's a Transcend 32g 400x. Looks like it's a slow card? If so, which should I buy?
Quote from: v1rt on June 26, 2013, 03:17:39 PM
It's a Transcend 32g 400x. Looks like it's a slow card? If so, which should I buy?
I used to record continuous 720p on such card. Build 28 May, GD on, histogram and scopes ON, but zebra stops recording, so was OFF.
Last sunday i was trying to catch the full moon with no luck, too much wind for my tripod. I was with my 135mm lens instead my vivitar 28-90 and only could take long focal distance shots. It was "La noche de San Juan" and people was dancing, jumping in fire, so i made a video.
There are some 5x shots, with my slow card only 1600x900. One of them was magenta magenta so I did what I could in ACR
The very last clip of the card had 13 bad frames. The rest of them, only one bad frame.
Thanks again for this development guys!!!
http://www.youtube.com/watch?v=cPPrYAmvznk&feature=youtu.be
QuoteIn the latest build of 25 June after I have set ISO and trying to adjust exposure, changing aperture is fine but attempt to modify the shutter speed modifies ISO for some reason
50D doesn't have manual exposure in movie mode.. if you don't have expo override on canon changes the ISO once it runs out of "real" shutter speeds. It ill say iso XXX eq. Also be aware aperture may not be really clicking down either, or at least not where you're putting it.
*new builds working the exact same for me.. but I turn the dialog timers off so still get like 80MB/s
hmm... tested some more.. there is a speed difference between photo mode and movie mode
I went to Great Falls Park, and tried out a couple res on some waterfalls and friends
I made the final video have 2048x1152 so it would trigger youtube's original res for 18-26 MBPS
Edit: I've also uploaded a Final uncompressed output with 8bit lagarith lossless codec (5.6 GB) available here: https://docs.google.com/file/d/0BxmF1M7jtUvFZzhhOVlHUV9Ub0U/edit?usp=sharing
Sorry, again, if I'm missing something obvious - but I was doing great with the builds up to the end of May or so. 64G KompBay 1K card, 65+Gb/s write rates with 1600 1x crop raw.
Then, as I've started trying the more recent builds (unified, mostly) - my speeds have dropped into the 40-45 Gb/s range.
I have all the other menu choices as before (Global Draw LiveView, 24.000 fps override, etc.).
I see discussion about turning off dialog timers, and searching the forum, mention that that involves the "Dont Click Me' menu - clicking that with latest posted build gives me weird sliding screens and a crash.
I have cleaned and rebuilt the card from scratch a few times. Ran benchmarks again, and I think they look OK.
Oddly - when I select RAW video, the message at the bottom of the screen says "565.7GB/s needed for 24p" -- making me wonder if something is configured wrong. I'm scratchin' my head. Maybe someone has a clue that'll help?
(http://img268.imageshack.us/img268/2643/aap9.jpg)
That got moved + you're looking at a unified build which is 1 commit behind to boot.
Nice to see that there is extra 10MB left to discover.
Its not shutter... fake movie mode in real photo mode has same speeds as before... it also shouldn't be the indicators as they still display in fake movie mode... wtf else changed.
Here you can try it...
[50D] Still fast in photo mode.zip
https://mega.co.nz/#!x9JUUTaQ!crrTnHy6f7ziG9HUfKhhrFkbdx0cnmMykXCOLCjFJ5g
timers are above don't click me.. which is now "native" 24fps... for H264 this resizes it... just noticed this morning... so I'm going to see what happens with the larger sizes again. Hmm.. maybe its just aspect ratio
@1% - So raw video and H.264 is 24p without FSP override now?
Yea, but meta data not changed. Still testing this and other debug functions... maybe there is a way to disable ae and wb, the command used now isn't present.. also face detection.
Also the ADTG based shutters should work but I dunno how to translate reg # to reg address
So disabling AE and probably wb works... saves a tiny bit off cpu.. gonna see f its the same for face detection.
I can set face detection address to 0x0... dunno if it helps, the ae stuff locks expo while recording unless you change from ML.. dunno good? bad? Went up to 81Mb/s in photo mode... really no reason to use movie mode till this is fixed... also can select LV output device.. have to check on that...
what else is eating gilbert's grapes? LV jpeg creation is constant... we need to kill this
81.x MB shrinking lv to "vga" size.
Quote from: araucaria on June 25, 2013, 11:33:41 PM
was that in 5x zoom mode?
I think the only shot which was done in crop mode was the bird in the sand. Everything else was upscaled to 1920 from the 16xx resolution (can't remember the exact number).
Quote from: 1% on June 26, 2013, 07:01:21 PM
also can select LV output device.. have to check on that...
Does that include over USB? I used to use DSLR Controller with my Nexus 7 for photo composition and time lapse functions before I installed Magic Lantern. Currently locks up using RAW video and or Zoom Mode. Not a huge issue, would just be nice to use a nice 7in screen I already usually have with me as an external display.
Anyone else use this app for Android?
http://dslrcontroller.com/ (http://dslrcontroller.com/)
Quote from: GregoryOfManhattan on June 25, 2013, 04:56:15 PM
numbers may change but the frames remain the same.
today's builds include code changes to bitrate calculations - so the numbers may display differently than before.
you can compare performance with past builds by maximum frames under some settings (1920x1080 @23.976) or maximum continuous recording at your favorite aspect ratio.
in the last couple of days a1ex modified the code in hudson/unified branch which reports the speed (bitrate) so numerical comparisons with past and other builds may not be accurate.
there has been a single change (commit) since i posted the unified build yesterday - a "fix typo" where speed in one place is shown 10x greater than actual. no functional differences.
Yea, but shouldn't drop 80MB/s in movie mode to 76 or stop that initial record so quickly.
I was more thinking of this: https://bitbucket.org/hudson/magic-lantern/commits/81765310b9533d061092c1e8d4e5a8056a8e4eff
Could anyone tell me is it technically possible to increase FPS and lower resolution? Is it planned for the future? Perfect for slow motion clips...
Quote from: 1% on June 26, 2013, 06:00:28 PM
That got moved + you're looking at a unified build which is 1 commit behind to boot.
Here you can try it...
[50D] Still fast in photo mode.zip
https://mega.co.nz/#!x9JUUTaQ!crrTnHy6f7ziG9HUfKhhrFkbdx0cnmMykXCOLCjFJ5g
Bingo -- that put me back in action -- now seeing "Continuous OK' and in the 60-65 Mb/s range.
Thanks!
Which 64g cf card should I buy? Transcend or KomputerBay?
Quote from: v1rt on June 26, 2013, 10:53:49 PM
Which 64g cf card should I buy? Transcend or KomputerBay?
Komputerbay
Quote from: 1% on June 26, 2013, 06:00:28 PM
Here you can try it...
[50D] Still fast in photo mode.zip
https://mega.co.nz/#!x9JUUTaQ!crrTnHy6f7ziG9HUfKhhrFkbdx0cnmMykXCOLCjFJ5g
I'm suffering from a speed depression. Last night installed gregory's june 25th build and was able to get about 8gbs of 1584x1058. However after a couple clips, I couldn't seem to get more than 60.1mb/s with that build and today the same with the one you linked above. Also just tried Gregory's June 26th build (just uploaded) and I can't get above 62.5 mb/s in 16:9. Using the Komputerbay 1000x 64 formatted in camera and haven't changed anything (global draw off, etc). What could be the problem?
I dunno, good question. You should try with timers off (debug menu) and in photo mode, you can still do 1038 and full non zoom (room to spare).... but a couple of days ago I had 1920x1080 almost continuous in MOVIE mode.
Quote
Using the Komputerbay 1000x 64 formatted in camera
This actually works and doesn't make your card 32gb?
hm... so you can... except it does 32KB clusters and cuts speed down a tiny bit
No problem here. Still getting around 72MB/s with timers off 1080p 25p gives me about 15 seconds per clip on my card which isn't bad. BTW 1% - I just added the pink frame fix to raw_rec.c in my TL clone. I presume it wont do any harm?
I'm using it now, just haven't pushed/remade a bin.
Heh, started 1/2 way on a full format and speed jumped up, maybe its the cards?
Cool. How you getting on with that ADTG thing on the 50d? Any luck?
Nope, on 6D neither... I'll see whats in the bins... if its just REG [03232] -> then its what I see on LV. can't figure out the reg #s to write to.
going to fully format the card for 64K and see if speed comes back.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B50D%5D%20NewerHacks.zip
Am I right folks that with raw recording in 50D using fast cf card, we can only record less than 20 seconds?
Quote from: v1rt on June 27, 2013, 04:19:33 AM
Am I right folks that with raw recording in 50D using fast cf card, we can only record less than 20 seconds?
No. I am using a Komputerbay 1000x card (like many here) and can record at full sensor (1584x892 @ 16.9 ratio) continuous till I fill my card. And this upscales quite nicely if you are good with your original capture exposure, and handiness in RAW edits. At 24fps this only requires about 55mb/s. Cropped frame (1920x1080) for me shoots about 30-45 seconds
sometimes using 1%'s Dialog Timer "off" settings. This requires about 83mb/s which my card currently caps at around 77-78mb/s (resulting in less than 45 second full HD recordings seeing as the buffer will eventually fill with no idle, forcing the recording to stop).
tried that latest hudson/unied build with today's removal of pink frame code.
if you have had pink frames in crop/zoom mode you may want to try it as a.d. has confirmed this is an improvement on the 5D2
at 23.976 frames per second
getting continuous recording at:
1584x1058
1920x872
1920x1080 got 221 frames in a single test.
at 25 fps 1584x1058 got 1835 frames in a single test (for the 50hz anamorphic users).
reformatting these FAT32 cards periodically is a very good idea, for anyone who is experiencing speed challenges.
tried this setting a 64k block size with perhaps better results
1920x1080 got 227 frames in a single test
at 25fps 1584x1058 got 2400 frames and then 3400 frames.
did get into some state where the canon info menus re-appeared - power cycle seemed to cure it.
unified build seem to be fine with real speeds near 70MB/s.
@1%
Can you or anyone point me in the right direction regarding disabling the timer. I have looked for it in debug as mention, but none in my list say timer. I'm using the most current Greg build.
Thank you!
Quote from: 1% on June 27, 2013, 01:03:47 AM
I dunno, good question. You should try with timers off (debug menu) and in photo mode, you can still do 1038 and full non zoom (room to spare).... but a couple of days ago I had 1920x1080 almost continuous in MOVIE mode.
This actually works and doesn't make your card 32gb?
hm... so you can... except it does 32KB clusters and cuts speed down a tiny bit
I've been doing in camera formats for awhile and pretty sure I've recorded 32gb+ at least a couple times. I'll try it with timers off and a FAT 32 format tmr.
Thx.
wow amazing work! ML RAW is insane for the 50d :)
any idea of the dynamic range we are getting?
Quote from: Chazo on June 27, 2013, 08:26:46 AM
wow amazing work! ML RAW is insane for the 50d :)
any idea of the dynamic range we are getting?
I guess it's around what we get from still RAWs. But needs some testing...
Is there any chance to use one of the mosaic engineering filters in 50D an reduce moire and aliasing?
Quote from: frontloop on June 27, 2013, 10:57:14 AM
Is there any chance to use one of the mosaic engineering filters in 50D an reduce moire and aliasing?
It has been discussed 2-3 times earlier in this thread. To put it short: no.
http://www.ultraimg.com/images/z3Nu.gif
Quick grade from today's shoot. So much flexibility from raw. Love it.
Quote from: GregoryOfManhattan on June 25, 2013, 04:56:15 PM
included a not great panning city scape to show the moire.
at 25second far left top corner the windows have a crazy multicolor pattern,
the rooftops to the left of the Allianz building show some strange flickering digital artifacts which i think is caused by antennas.
the side of the dark brick building center frame at 35second has very visible moire.
in resolve lite, i tried to separate luma and chroma and to blur the chroma to reduce at least the rainbow portions of the moire pattern. all these things look worse at full resolution viewing the cinemaDNGs - the silver lining in all the compression to post videos online is that the apparent problems are reduced.
the earlier shots of the trees could have been processed (perhaps by masking the backs of the trees or could i have keyed on the tree bark color?) to keep the dark detail in a very wide dynamic range shot.
(note: uploaded a 444 prores with vimeo compression and somewhere - this vimeo gamma is much darker from what i saw on screen - at my limit for the week of uploads - so cannot be replaced)
looks to me like the 50D image can be sharpened and look very nice on organic natural shots - trees, forest , ocean, etc...
a deep focus city shot is going to require post work to reduce the moire.
basically you need to limit depth of field in a city or room with patterns.
the final shot show crop/ zoom mode at 105mm looking at one world trade center (4.2miles / 6.7km ) and 1 penn plaza (1.3 miles / 2.3 km) distance.
@rommex - you may like a documentary film "crumb" (1994) - it shows an artistic interpretation of telephone and power cables.
Very great looks! Which LUT are you using in Resolve? Especially I'm loving the color of forest footage.
Tonight there is a Jazz concert in my town and my nikon lens adapters just arrived, I'm still on an older build and I wanted to know which is the latest stable/fast one to try out zoom mode. Was the 80mb/s wrong info? As I'm reading 70megs lately.
After reformat got 81.
Quote from: dsManning on June 27, 2013, 05:39:07 AM
No. I am using a Komputerbay 1000x card (like many here) and can record at full sensor (1584x892 @ 16.9 ratio) continuous till I fill my card. And this upscales quite nicely if you are good with your original capture exposure, and handiness in RAW edits. At 24fps this only requires about 55mb/s. Cropped frame (1920x1080) for me shoots about 30-45 seconds sometimes using 1%'s Dialog Timer "off" settings. This requires about 83mb/s which my card currently caps at around 77-78mb/s (resulting in less than 45 second full HD recordings seeing as the buffer will eventually fill with no idle, forcing the recording to stop).
Ok. I got confused when you mentioned Cropped frame 1920x1080. Can our 50D record at 1920x1080 raw? The old ML I was using allows me to record at 1920x1080 but not raw.
It should be able to for a bit like 30 sec, sometimes more. 1920x1038 is a bit better.
Have you tried recording any? You can still record H264.
Quote from: 1% on June 27, 2013, 04:53:43 PM
It should be able to for a bit like 30 sec, sometimes more. 1920x1038 is a bit better.
Have you tried recording any? You can still record H264.
I haven't bought the KomputerBay 1000x cf card yet. I have an old Transcend 400x which I think is not capable of raw recording at high resolutions with menus. I was able to raw record but I set it to 1280x720 with the menus turned off.
Quote from: v1rt on June 27, 2013, 05:04:58 PM
I haven't bought the KomputerBay 1000x cf card yet. I have an old Transcend 400x which I think is not capable of raw recording at high resolutions with menus. I was able to raw record but I set it to 1280x720 with the menus turned off.
Transcend 400x is rated for 60mb/s (150Kbp/s( Industry standard transfer rate) x 400 = 60Mb/s. With KomputerBay 1000x, based on the formula,it is 150Mb/s. The Canon 50D is UDMA 6, based on the CF specification (http://en.wikipedia.org/wiki/UDMA), it's transfer rate is capable of 133Mb/s.
In the end, KomputerBay is the best;but I heard too that it's out of spec. A lot of manufacturer's are! We'll be happy if it reaches 100Mb/s.
The question: Are the Canon camera's out of spec. or the card manufacturers? or maybe, the software overheard in ML; all the features. The proof is pointing to the features of ML? GD off,ETTR off,etc. and turning off some features makes the big difference. True or not, we'll find out, testers!
:-)
CPU usage by canon/ML definitely affects write speed. If we break more stuff it will be faster.. I'm hoping for maybe 10Mb/s more somehow... not expecting the 100s on UDMA 6 but from SD cards should only be 5MB or less under max write of the card. Just 5 more MB or even like 2 or 3 and 1080P will be continuous. 10MB more and probably stable.
Quote from: 1% on June 27, 2013, 05:56:18 PM
CPU usage by canon/ML definitely affects write speed. If we break more stuff it will be faster.. I'm hoping for maybe 10Mb/s more somehow... not expecting the 100s on UDMA 6 but from SD cards should only be 5MB or less under max write of the card. Just 5 more MB or even like 2 or 3 and 1080P will be continuous. 10MB more and probably stable.
That's great to hear, thanks a lot to all of you for your continuous effort. Btw, is there a reason, aka technical limitation, why the 5dmkii still is doing only 70mb/s compared to the 81mb/s of the 50d?
When selecting resolution in the RAW menu, i get the following message at the bottom of the screen when i try to select 1600 or higher:
1600 is not possible in current video mode (max 1584)
I'm running ML v.2.3 and GregoryOfManhatten's June 11th RAW build with a Lexar 32Gb 1000x CF card on a 50D.
Is this expected?
Thanks!
Yea, I don't have a 5D2... a1ex ported the slowdown hack today.. its only a few MB short but a bit more convenient... and if you forget to disable timers or are just shooting non zoom LV its winner. Also this method seems to make GD/buffer disabling a bit nicer.. the clear screen actually works, looks better overall.
Quote from: artiswar on June 27, 2013, 11:13:53 AM
http://www.ultraimg.com/images/z3Nu.gif
Quick grade from today's shoot. So much flexibility from raw. Love it.
Great Color Grading.. was it in Davinci? should post a short of that video.
Quote from: 1% on June 27, 2013, 05:56:18 PM
CPU usage by canon/ML definitely affects write speed. If we break more stuff it will be faster.. I'm hoping for maybe 10Mb/s more somehow... not expecting the 100s on UDMA 6 but from SD cards should only be 5MB or less under max write of the card. Just 5 more MB or even like 2 or 3 and 1080P will be continuous. 10MB more and probably stable.
Great work 1% I believe will be able to squeeze the other 5-10mb in time, but for now the Hacks are more than usable & stable. Thank you for all your hard work cheers.
Yesterday I was shooting with the 50D and thought to myself.. I have the ability, or the tool in my hand to shoot in the same league as the big dogs. With the right skill I should be able to create that elusive Hollywood look the time is now, let's create magic with the 50D and not get too technical with the specs. Gonna crank it up and do some serious shooting with my 50D got a couple shoots next month, I hope everybody feels the same. I'm soo grateful ;D for all the advances and the hard work that everybody on this community has put in thank you.
GOD Bless
1%'s hacks for variable buffering are now in part included in the hudson/unified branch and builds.
is the "estimation of how many frames you are going to get" using the latest raw_rec.mo module with the Small Hacks enabled accurate?
Quote from: GregoryOfManhattan on June 17, 2013, 01:53:22 AM
Update 26 June 2013 - there is a new "Small Hacks" feature in the raw_rec module. in the Raw Rec Detail Menu enable Small Hacks. This is the first 50D hudson/unified build to hit 81MB/s.
a1ex is looking for feedback on the accuracy (http://www.magiclantern.fm/forum/index.php?topic=6662.msg55450#msg55450) of the reported speed and frames - please report details if you have them.
@flambe - yes that's the maximum in regular video mode
@araucaria - these "Small Hacks" should bring up the speed on the 5D2 as well
@albert-e - be happy that the canon engineers built a sensor and datapipline capable of these speeds (greater than the red one)
@goldenchild9to5 and @2FAST - feel free to discuss on vimeo - bmcc, pump up the gamma, offset negative red, - a little too yellow and i need to learn to keep the full dynamic range with the detail in the tree bark. been watching excalibur (1981) and loving green.
@goldenchild9to5 yes shoot it
Quote from: goldenchild9to5 on June 27, 2013, 06:52:31 PM
Great Color Grading.. was it in Davinci? should post a short of that video.
It was indeed DaVinci. I'll post something quick up.
Quoteis the "estimation of how many frames you are going to get" using the latest raw_rec.mo module with the Small Hacks enabled accurate?
Kinda. It goes off of previous writes, hacks or not. Sometimes I notice its predicting too many or too few frames... why is this bad? I think a1ex sets buffer size from it.
If it predicts too many, the buffering algorithm is probably overestimating the card speed and it stops too early.
Look for this message: "careful, will overflow in %d.%d seconds, better write only %d frames"
and try to change these:
measured_write_speed * 9 / 100 => that means assume you will get at least 90% of measured speed. Try 80% or something.
frame_limit - 2 => that means it will use a safety margin equal to 2 frames. Try frame_limit - 3 maybe.
If you enable the debug graphs, buffer size should decrease slowly. If it stops while buffer is still large, that's an early stop and it shouldn't happen.
Will have to enable debugging stuff and see what its actually doing.
Quotemeasured_write_speed * 9 / 100
This makes sense most of the time tho.. 81*.90 is about 72.. doesn't drop much lower than that maybe 67-69 at absolute worst. When its properly working the 81 stays for a good length of time.
Quote from: GregoryOfManhattan on June 27, 2013, 07:11:07 PM
1%'s hacks for variable buffering are now in part included in the hudson/unified branch and builds.
is the "estimation of how many frames you are going to get" using the latest raw_rec.mo module with the Small Hacks enabled accurate?
@flambe - yes that's the maximum in regular video mode
@araucaria - these "Small Hacks" should bring up the speed on the 5D2 as well
@albert-e - be happy that the canon engineers built a sensor and datapipline capable of these speeds (greater than the red one)
@goldenchild9to5 and @2FAST - feel free to discuss on vimeo - bmcc, pump up the gamma, offset negative red, - a little too yellow and i need to learn to keep the full dynamic range with the detail in the tree bark. been watching excalibur (1981) and loving green.
@goldenchild9to5 yes shoot it
Best way to preserve your detail but still have blacks in DaVinci: Use the eyedropper in the curves window to pin point where on the luma curve the detail you want to keep is. then create another point below that to pull down the remaining dark tones.
Quote from: GregoryOfManhattan on June 27, 2013, 07:11:07 PM
1%'s hacks for variable buffering are now in part included in the hudson/unified branch and builds.
is the "estimation of how many frames you are going to get" using the latest raw_rec.mo module with the Small Hacks enabled accurate?
@flambe - yes that's the maximum in regular video mode
@araucaria - these "Small Hacks" should bring up the speed on the 5D2 as well
@albert-e - be happy that the canon engineers built a sensor and datapipline capable of these speeds (greater than the red one)
@goldenchild9to5 and @2FAST - feel free to discuss on vimeo - bmcc, pump up the gamma, offset negative red, - a little too yellow and i need to learn to keep the full dynamic range with the detail in the tree bark. been watching excalibur (1981) and loving green.
@goldenchild9to5 yes shoot it
i'm quite happy too, I have a 50D! but I was expecting >100Mb/s write speed rate but not more than 115Mb/s at any point of recording. But at this stage of development, I'm jumping...like a kid, lol! Three bangs for the ML team ...here it is - !!!
Quote from: GregoryOfManhattan on June 27, 2013, 07:11:07 PM
1%'s hacks for variable buffering are now in part included in the hudson/unified branch and builds.
is the "estimation of how many frames you are going to get" using the latest raw_rec.mo module with the Small Hacks enabled accurate?
@flambe - yes that's the maximum in regular video mode
@araucaria - these "Small Hacks" should bring up the speed on the 5D2 as well
@albert-e - be happy that the canon engineers built a sensor and datapipline capable of these speeds (greater than the red one)
@goldenchild9to5 and @2FAST - feel free to discuss on vimeo - bmcc, pump up the gamma, offset negative red, - a little too yellow and i need to learn to keep the full dynamic range with the detail in the tree bark. been watching excalibur (1981) and loving green.
@goldenchild9to5 yes shoot it
Will do..
Quote from: albert-e on June 28, 2013, 01:34:06 AM
i'm quite happy too, I have a 50D! but I was expecting >100Mb/s write speed rate but not more than 115Mb/s at any point of recording. But at this stage of development, I'm jumping...like a kid, lol! Three bangs for the ML team ...here it is - !!!
Why would you have ever expected the write speed to be so high?? There's no reason to believe the camera's card reader can get anywhere close to that...
If anyone out there is still looking for a camera, I've decided to sell mine, comes with the 64gb KOMPTERBAY x1000 card and some extra batteries...
http://www.ebay.com/itm/181166102079?ssPageName=STRK:MESELX:IT&_trksid=p3984.m1555.l2649
Quote from: briwil on June 28, 2013, 02:09:55 AM
Why would you have ever expected the write speed to be so high?? There's no reason to believe the camera's card reader can get anywhere close to that...
If anyone out there is still looking for a camera, I've decided to sell mine, comes with the 64gb KOMPTERBAY x1000 card and some extra batteries...
http://www.ebay.com/itm/181166102079?ssPageName=STRK:MESELX:IT&_trksid=p3984.m1555.l2649
Here: http://en.wikipedia.org/wiki/UDMA
I can't tell if it's read transfer rate or write transfer rate. It's probable that those numbers are read transfer rate...not sure!
:....
Hey guys - I'm in Thailand currently on the island of Koh Samui. I'm about to go out and shoot some raw video. I have the latest build from @gregoryofmanhattan - but it seems like the highest resolution is still 1584 x 892.
How do I get it to record 1920 x 1080? Or just higher resolutions in general? Sorry to be such a n00b about it - just want to shoot some amazing footage on this island to share.
Quote from: sschwartz23 on June 28, 2013, 05:16:14 AM
Hey guys - I'm in Thailand currently on the island of Koh Samui. I'm about to go out and shoot some raw video. I have the latest build from @gregoryofmanhattan - but it seems like the highest resolution is still 1584 x 892.
How do I get it to record 1920 x 1080? Or just higher resolutions in general? Sorry to be such a n00b about it - just want to shoot some amazing footage on this island to share.
http://www.magiclantern.fm/forum/index.php?topic=5586.msg54376#msg54376 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg54376#msg54376)
Ignore part about Debug and Dialog Timers if you are on latest build. Instead turn on Small Hacks in RAW menu. Part you want is in bold..
Here's a pretty intense low light test. It was shot on exposure override at f1.8 1/48th shutter speed and 3200ISO. I was very impressed with the resolution we can achieve with such a high ISO!
It was a canon 50mm f1.8 lens. Shot during the darkest part of the night.
Quote from: nightvision04 on June 28, 2013, 07:26:27 AM
Here's a pretty intense low light test. It was shot on exposure override at f1.8 1/48th shutter speed and 3200ISO. I was very impressed with the resolution we can achieve with such a high ISO!
It was a canon 50mm f1.8 lens. Shot during the darkest part of the night.
Nice video. Which cf card are you using?
Hey folks. I just noticed there is another fork called Hudson. So which one should we be using, GregoryofManhattan or Hudson's? Currently, I installed GregoryofManhattan build 2 days ago.
Thanks!
Quote from: v1rt on June 28, 2013, 08:01:30 AM
Nice video. Which cf card are you using?
Thanks. The toshiba 1066 exceria pro 64gb
Thanks to everyone involved on this project. Your work is greatly appreciated.
I'm no expert, but if the 50D is able to record 1584x892 continously at full sensor (or even 1584x1058?), shouldn't we be able to record at higher resolutions with cinemascope ratio? With 1584x1058, let's cut 200 pixels from the height and extend the width - that's almost FullHD at cinemascope.
You know, I'm sure a lot of people thought about this. So I bet it just doesn't work (yet). But I'm curious; why doesn't it work?
Why doesn't what work, you can record the whole non zoomed LV for a while.
Quote from: niggo on June 28, 2013, 02:53:24 PMBut I'm curious; why doesn't it work?
Because the camera isn't reading the full sensor resolution (4752 X 3168) and scaling it down to what ever we want. It skips every third line and column to reduce the resolution to 1584 X 1056. In crop mode, there's no skipping so it is possible to get higher resolutions.
If the developers would find a way to set the skipping from 3 to 2 it would be possible to record higher resolutions on the 50D, even without the strong crop. And it might reduce the aliasing. But that would be too nice ... ;D
@1%: The question is "Why can't we record continously at higher resolutions?" - and I'm not talking about crop mode. I'm mostly interested in shooting cinemascope, so all those extra pixels in height don't interest me. I'd much rather like to add those to the width.
@CFP: I see, so 1584x1056 isn't a limit in regards of write speed but rather the line skipping?
That is the image size without zoom. You can take the whole thing or 1584 x whatever.
Also taking out the skipping will probably increase the crop. It seems that way on every canon. Resizing the raw buffer, if ever possible, will probably lower FPS.. which might be OK on 50D since its 30fps all the time.
Quote from: 1% on June 28, 2013, 03:45:21 PMAlso taking out the skipping will probably increase the crop.
But if it would be possible to set the skipping from 3 to 2 the image's size would be 2376 X 1584 right? If you choose an aspect ratio like 2.5:1 you would get a resolution of 2376 X 950 (Or 2368 X 960 with multiples of 64) which would require 90 Megabyte/s. It wouldn't increase the crop and should work for a few seconds. Setting the aspect ratio to 3:1 or decreasing the resolution slightly would make it continously.
But that's just one of these pointless "if & would" ideas. I'm not expecting to see that possiblity soon. If it exists.
Quote from: niggo on June 28, 2013, 03:30:27 PM
@CFP: I see, so 1584x1056 isn't a limit in regards of write speed but rather the line skipping?
As far as I know: yes.
Okay guys, so an update.
I just wrapped a commercial shoot w/ the 60D but used the 50D ML RAW for a few interviews. They're brief cuts, but the results were amazing.
As a result, I've purchased a Transcend 128GB 1000x card for full production purposes and wrapped principal for a fashion film short. The results are f'ing STUNNING. This time around I used a Davinci Resolve process to DNxHD 10bit 422>Premiere CS6 edit>LOG DPX esport>AE CS6 color (yes, Resolve would be just as good, but I'm accustomed to the AE workflow right now).
DPX LOG
(http://farm8.staticflickr.com/7367/9160060852_4edc8be86f_o.jpg)
Grade and texture
(http://farm8.staticflickr.com/7353/9157835603_a91d496d3c_o.jpg)
Hi guys,
here´s my comparison between ACR and Resolve.
Natural grade in ACR and extrem greenish day for night something in resolve...
Infos:
http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Quote from: funkysensation on June 28, 2013, 06:31:54 PM
Hi guys,
here´s my comparison between ACR and Resolve.
Natural grade in ACR and extrem greenish day for night something in resolve...
Infos:
http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Great shots! What lenses did you use? Also did you shoot in crop mode? I can't see any strong aliasing there...
for wide shot´s i used a tokina 12-24mm and for the closer ones sigma 28-300mm no crop mode at all
more about my workflow: http://550draw.blogspot.com/
Quote from: funkysensation on June 28, 2013, 06:31:54 PM
Hi guys,
here´s my comparison between ACR and Resolve.
Natural grade in ACR and extrem greenish day for night something in resolve...
Infos:
http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Hi
It is possible to get the same result in terms of cc with resolve comparing to ACR?
Regards
Quote from: nightvision04 on June 28, 2013, 08:11:47 AM
Thanks. The toshiba 1066 exceria pro 64gb
One of the best so far.I like the spec. 160Mb/s. Nice,on my wish list.
nice grade,
lads, how do I change resolution ?
I press Q just like with 5mdII and it just jumps between 1920x1080 an 640x480, (9th June build)
Quote from: mjstudio on June 28, 2013, 08:15:41 PM
nice grade,
lads, how do I change resolution ?
I press Q just like with 5mdII and it just jumps between 1920x1080 an 640x480, (9th June build)
You have to load the raw modules first, go to "M" menu on ML menu.
Thanks for a quick reply.
I did, just didn't find the separate raw recording field, in the scroll down menu. Found it eventually :)
Another thing. I have 600x udma6 32GB Kingston card and it won't let me go over 40 frames at 1584x892, any ideas?
Hey guys,
When I go inside Resolution and move my selection over 1600 menu or any resolution above 1600, the status says
1600 is not possible in current video mode (max 1584).
I was told that our 50D can do 1920 raw.
Thanks!
Zoom in.
Quote from: v1rt on June 28, 2013, 09:47:42 PM
Hey guys,
When I go inside Resolution and move my selection over 1600 menu or any resolution above 1600, the status says
1600 is not possible in current video mode (max 1584).
I was told that our 50D can do 1920 raw.
Thanks!
You'll have to press the 5x zoom button on your 50d. The recording resolution will automatically change to 1920x1072.
now 50d is so much fun!
Thank you guys!
Quote from: nightvision04 on June 28, 2013, 10:02:58 PM
You'll have to press the 5x zoom button on your 50d. The recording resolution will automatically change to 1920x1072.
I tried it but it didn't work. It still picked 1584x892. Maybe because my cf card is slow. Do you think it's because of my non-1000x cf card?
You have to change resolution in the raw module when zoomed in.
Quote from: 1% on June 28, 2013, 10:10:28 PM
You have to change resolution in the raw module when zoomed in.
Got it to work! However, what will be recorded as video? Is it still going to record the non-zoomed area? Btw, it stopped after 2 seconds. My 400x is so slow, LOL :D Really need to buy the 1000x cf cards.
Quote from: v1rt on June 28, 2013, 10:08:52 PM
I tried it but it didn't work. It still picked 1584x892. Maybe because my cf card is slow. Do you think it's because of my non-1000x cf card?
That's odd. So you're saying that while you are in 5x zoom mode, if you enter the magic lantern menu, you don't see a grayed-out "1920x1072"? I'm probably stating the obvious here... but the 5x button isn't an on/off switch 1920 recording, it's a different video mode altogether.
The card you are using exceeds the bitrate required for 1920 recording. Perhaps 1% can comment?
Quote from: mjstudio on June 28, 2013, 10:06:53 PM
Just tried 1472x828 , 40 frames and stops :'(
The Kingston ultimate 600x is not actually UDMA6. It's UDMA6 compatible. The write specs are way over rated. I have one and it's crap.
Quote from: nightvision04 on June 28, 2013, 10:15:47 PM
That's odd. So you're saying that while you are in 5x zoom mode, if you enter the magic lantern menu, you don't see a grayed-out "1920x1072"? I'm probably stating the obvious here... but the 5x button isn't an on/off switch 1920 recording, it's a different video mode altogether.
The card you are using exceeds the bitrate required for 1920 recording. Perhaps 1% can comment?
It's good now. 1% helped me on how to get it triggered. I have actually posted just few minutes ago since I had a follow up question.
Quote from: nightvision04 on June 28, 2013, 10:15:47 PM
That's odd. So you're saying that while you are in 5x zoom mode, if you enter the magic lantern menu, you don't see a grayed-out "1920x1072"? I'm probably stating the obvious here... but the 5x button isn't an on/off switch 1920 recording, it's a different video mode altogether.
The card you are using exceeds the bitrate required for 1920 recording. Perhaps 1% can comment?
1072? ??? - should be 1080 if set width is 1920 (16:9)
Quote from: v1rt on June 28, 2013, 10:14:34 PM
Got it to work! However, what will be recorded as video? Is it still going to record the non-zoomed area? Btw, it stopped after 2 seconds. My 400x is so slow, LOL :D Really need to buy the 1000x cf cards.
Great to hear you got it working! Using a Toshiba 1066x Exceria Pro 64gb, i'm only getting about 10 seconds... Have you tried turning off global draw? If you haven't yet, that should give you a few more seconds.
Quote from: nightvision04 on June 28, 2013, 10:18:55 PM
Great to hear you got it working! Using a Toshiba 1066x Exceria Pro 64gb, i'm only getting about 10 seconds... Have you tried turning off global draw? If you haven't yet, that should give you a few more seconds.
Yup it's off. Are you saying that's impossible for our 50D to do a continous 1920x1080 raw recording atm?
@nightvision04 - what build are you using?
I'm getting 15 secs of 25p (1080p) on a 600x transcend card.
Quote from: v1rt on June 28, 2013, 10:20:18 PM
Yup it's off. Are you saying that's impossible for our 50D to do a continous 1920x1080 raw recording atm?
That's correct.
Quote from: Andy600 on June 28, 2013, 10:20:59 PM
@nightvision04 - what build are you using?
I'm getting 15 secs of 25p (1080p) on a 600x transcend card.
I'll butt in here. :)
Which build should I use? Maybe you can specify a link. I'm using the latest GregoryofManhattan. I also read yesterday that there is a Huston. Not sure what it is.
Quote from: v1rt on June 28, 2013, 10:23:29 PM
I'll butt in here. :)
Which build should I use? Maybe you can specify a link. I'm using the latest GregoryofManhattan. I also read yesterday that there is a Huston. Not sure what it is.
Gregory's latest is up to date. I'm using 1%'s latest (own compile). Not sure if he's uploaded it anywhere???
BTW 1% - when you go into LV with the latest TL build I get black pillar boxes as if it's in 480p and need to hit the info button 2 or 3 times to get rid of them.
Quote from: Andy600 on June 28, 2013, 10:29:09 PM
Gregory's latest is up to date. I'm using 1%'s latest (own compile). Not sure if he's uploaded it anywhere???
Maybe I can try his build. Do you know where I can download it?
Quote from: v1rt on June 28, 2013, 10:30:32 PM
Maybe I can try his build. Do you know where I can download it?
https://bitbucket.org/andy600/tl50d/downloads/1.percents.tragic.lantern.for.50D.test.only.compiled.by.andy600.zip
for best speeds set Dialog Timers to 'disable' in debug menu
before going into Live View
I'm currently looking into buying a 50D.
Are there any 600x cards that can reliably do 1080 crop and full sensor modes (Preferably 16 or 32 GB)?
Quote from: ClmnsKbn on June 28, 2013, 10:44:30 PM
I'm currently looking into buying a 50D.
Are there any 600x cards that can reliably do 1080 crop and full sensor modes (Preferably 16 or 32 GB)?
Transcend 600x 16gb is great for the money. Writes up to 74MB/s :) If you go for the 32gb get the 1000x (but don't get the 16gb 1000x. It's slower than the 600x)
Quote from: Andy600 on June 28, 2013, 10:36:54 PM
https://bitbucket.org/andy600/tl50d/downloads/1.percents.tragic.lantern.for.50D.test.only.compiled.by.andy600.zip
for best speeds set Dialog Timers to 'disable' in debug menu before going into Live View
Thanks a lot!
Quote from: Andy600 on June 28, 2013, 10:46:52 PM
Transcend 600x 16gb is great for the money. Writes up to 74MB/s :) If you go for the 32gb get the 1000x (but don't get the 16gb 1000x. It's slower than the 600x)
Thanks!
A lot of people here seem to love the Komputerbay 64GB 1000x. Is the 64GB 600x any good?
Quote from: ClmnsKbn on June 28, 2013, 11:04:56 PM
Thanks!
A lot of people here seem to love the Komputerbay 64GB 1000x. Is the 64GB 600x any good?
I dunno. I have the 64gb 1000x too :D
QuoteBTW 1% - when you go into LV with the latest TL build I get black pillar boxes as if it's in 480p and need to hit the info button 2 or 3 times to get rid of them.
Yep, shrinks the LV to add some more .1 MB.
Quote from: 1% on June 28, 2013, 11:35:23 PM
Yep, shrinks the LV to add some more .1 MB.
aha, I knew there had to be a reason for it :D
That black screen happened to me too. I also had other errors.
Quote from: v1rt on June 29, 2013, 12:31:08 AM
That black screen happened to me too. I also had other errors.
Errors?
Quote from: Andy600 on June 29, 2013, 12:38:35 AM
Errors?
Yes, I'll try to recreate it again later and post it. Or maybe because my cf card ran out of space. I will have to redo it.
Yea, what errors?
At 1080P I'm getting predicted 2K+ even 2500+ frames... then around 4900MB something happens, buffer fills an it stops early, writes get smaller and smaller. Writing at 80-81 1920x1038 is continuous without this issue.
Quote from: 1% on June 29, 2013, 01:21:17 AM
Yea, what errors?
At 1080P I'm getting predicted 2K+ even 2500+ frames... then around 4900MB something happens, buffer fills an it stops early, writes get smaller and smaller. Writing at 80-81 1920x1038 is continuous without this issue.
Do you think our 50D will be able to record 1080raw without stops in the future?
Maybe, the 1920x1038 is pretty damn close. I think I should graph it and see what is happening. Have to look for another way to increase speed too.
Quote from: albert-e on June 29, 2013, 05:39:48 AM
Don't bet your life on it!
:-)
Agreed :) He was just asking if it was possible at the moment though.
Quote from: nightvision04 on June 29, 2013, 07:26:25 AM
Agreed :) He was just asking if it was possible at the moment though.
:) :) :) :) Cool. By the way, I liked your video "On A Distant Planet"; short but I got the message, in the end I was looking for more. Is it alright if I link or embed the video on a web page.?
It seems I fucked up today, I was shooting in Crop mode but the led wouldn't go off after recording, I waited for a few minutes, then I turned off the camera and a ML message "Memory Corruption at frame 327" came on screen. I took out the battery and when I turned on the camera again the card needed format, but I can't format the thing, not on Windows, not in Camera, my nikon D3 formats it but with no result. Any ideas?
Thanks for all the hard work on squeezing every bit of speed out of this camera. Shot another low light concert in Boston last night with great results. Just built a little stabilizer and it is working out great! http://goo.gl/lz5Iw (http://goo.gl/lz5Iw) (Added bike handlebar grip for a nicer fit and look since)
One question on the 'squeeze' though;
Since parts of the Canon base are slowly being taken out or disabled to favor write speed, would this break the LiveView output over USB to another device?
I am having trouble getting an image to display in both DSLR Controller (Android App) and EOS Utility on my computer, which I was instructed to test by the DSLR Controller developer, to see if it was an issue with his app and ML or if something in this build stripped that functionality. All other controls input through DSLR Controller show changes on my camera. Change shutter speed, aperture, ISO, etc, they all update. Just no image.
Thanks
It shouldn't break usb output, Ill have to try connecting to something and check.
Hello
(sorry for my english)
Could you tell me, how much cropped will be images, for example, in 1320x840 mode? (i want aspect ratio near to 16:9)
I don't have 50d yet and i'm going to buy wide lens soon.
I like samyang 14 mm, but if image will be too cropped, i'd prefer sigma 10-20
Quote from: ninurta on June 29, 2013, 04:23:29 PM
Hello
(sorry for my english)
Could you tell me, how much cropped will be images, for example, in 1320x840 mode? (i want aspect ratio near to 16:9)
I don't have 50d yet and i'm going to buy wide lens soon.
I like samyang 14 mm, but if image will be too cropped, i'd prefer sigma 10-20
14mm in crop will be ~ 67mm
10mm will give you approx 50mm
Aspect ratios are selectable and do not affect the crop factor. Crop is ~3x compared to normal mode (full sensor).
Quote from: Andy600 on June 29, 2013, 05:12:17 PM
no, i didn't mean crop mode
as i know, in dslr cameras video uses only 1/3 lines (or less) of sensor
what pixels uses magic lantern in raw video?
if 1/3, so 4752/3=1584
and how can ml get resolution 1320 without cropping?
Quote from: ninurta on June 29, 2013, 06:34:38 PM
Could you tell me, how much cropped will be images, for example, in 1320x840 mode?
Do the math yourself ;)
The formula is: Max. width / your width X sensor crop
In 1X mode the LiveView resolution is 1584 wide. And the sensor is a APS-C sensor so it has a 1.6 crop factor. For a width of 1320 that means 1584 / 1320 X 1.6 = 1.92. But why do you want to crop? You can record the full width if your card is fast enough ... :D
Your 14mm lens would become a 27mm with a resolution of 1320 X 840. Not that bad, right?
Oh and by the way, 1320 X 840 isn't 16:9 but almost 3:2 (3.14:2)
CFP
ok, thanks )
Guys,
I'm a bit confused about which build to use, there are 5 different at the moment (unified, gregor's,a1ex', 1%'s, andy's).
Are we getting a single with all the features and when? We would definately need a wiki with faq and guide. I can start one when I clear the confusion about which build to use. I guess it's too early due to fast development.
I apologize if this has been discussed. I have searched this topic and the post-production topic.. either skipped it or it hasn't been addressed. I just tested a video out and I have the raw file (m29-1506) and a rar file of the same file name. The rar is 'corrupt' and the .raw file won't extract. Any way to recover/fix this?
Nevermind. Found it.
Quote from: fromdecember on June 29, 2013, 09:54:19 PM
Nevermind. Found it.
I linked a compiled script somewhere back in this thread that i wrote to auto merge spanned raw files.
Quote from: CFP on June 28, 2013, 04:42:24 PM
But if it would be possible to set the skipping from 3 to 2 the image's size would be 2376 X 1584 right?
To answer my own question: Forget that.
I just understood that it is impossible because of the sensors's bayer pattern. It would result in a monochrome picture. The only usefull skipping values are 3 or 1 (No skipping). Looks like there is no way to increase the 1X mode resolution of any Canon DSLR. The only way I can imagine would be to combine 4 pixel to one cluster and skip clusters instead of pixels. But I doubt that this is possible and it might affect the image quality. Time to stop dreaming and be happy with what we have I guess ;D
There is a chance of making it bigger... it samples X area to get 30FPS.. from getting the native modes it will slow down if you up the rez. so maybe get can get like a 1800xsomething at 24P. Not happening any time soon tho.
Quote from: 1% on June 30, 2013, 05:56:33 PM
There is a chance of making it bigger... it samples X area to get 30FPS.. from getting the native modes it will slow down if you up the rez. so maybe get can get like a 1800xsomething at 24P. Not happening any time soon tho.
Wow!!! 1% that would be incredible... would be almost 1920.. What do you need to make this happen? I know time is one, but what else?
Loving the 50D right about now ;D. Tweaking a custom WB setting so far it's yielding great results, but I'm gonna keep testing away until it's perfect, or to my liking this camera has crazy potential...
Understanding of the paths and CMOS/ADTG registers. Right now its only doing shutter speed on 5d3.
Quote from: albert-e on June 29, 2013, 01:07:54 PM
:) :) :) :) Cool. By the way, I liked your video "On A Distant Planet"; short but I got the message, in the end I was looking for more. Is it alright if I link or embed the video on a web page.?
I would be honored!
---------------------
Quote from: 1% on June 29, 2013, 03:15:54 PM
It shouldn't break usb output, Ill have to try connecting to something and check.
I also tried to Magic Lantern Controller app for Android which does not work for me now. https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=en (https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=en)
I remember trying this on an earlier RAW build (sadly don't remember which, but at least 2 weeks back) and I did have LiveView showing on my tablet using this app.
Any chance someone else out there could test to see if LiveView over USB is working for them? Easiest way to test would be EOS Utility if you have it installed on your computer. Wanting to get this set up before a shoot next weekend and I'd rather not rent a HDMI monitor when I already own a very capable 7" tablet.
Off to dig through my downloads folder to test some old builds on my backup card to see what will work. Sadly I'm no code expert, so I'm no help in finding it there. Maybe if I can find a working build a smarter up could help me compare?
EDIT: So I jumped back to one of the unified builds. ml-2013Jun18.50D.109.go.unified.d55f33a1d395 to be exact. No issue with LiveView in EOS Utility. Going to move forward and try to find where it was broken.NEW EDIT: So it turns out after a few tests with quite a few builds, that LiveView works just fine with MagicLantern, until you enable RAW video. What I was running as my daily driver, I had my modules autostart which led me to believe it was the new builds that broke LiveView. When you install a new build (or old while I was testing back) the modules are usually set to not load at start. So with no RAW video enabled, LiveView works :-\
Thanks
why is everyhing pink in x5 and x10 mode?
QuoteSo with no RAW video enabled, LiveView works
That sucks. Probably canon function messes with USB. Have to plug in and try.
Yeah. Bummer.
At least you can frame your shot with a USB monitor.
With camera unplugged from USB;
Power on
Switch LiveView on
Set your desired RAW settings
Go to Modules tab
Disable autolaod modules on boot
Power off (wait for activity lights to stop blinking)
Plug in USB to tablet (USB OTG needed)
Power on (this auto boots DSLR Controller on my tablet)
LiveView should be working! ;D
Frame your shot
When ready click the Trash icon to get to ML Menu and turn on RAW in Movie tab (this will freeze (or black out) LiveView on your tablet
From here, all adjustments available through DSLR Controller (pretty much every stock Canon setting) is still adjustable through your tablet (just no LiveView on your screen
I don't get it tho.. the jpegs are still being created. I see them in the logs. Cache hacking them off didn't produce a speed increase.. maybe have to save one and see if its black with raw video on.
Quote from: CFP on June 30, 2013, 02:02:06 PM
To answer my own question: Forget that.
I just understood that it is impossible because of the sensors's bayer pattern. It would result in a monochrome picture. The only usefull skipping values are 3 or 1 (No skipping). Looks like there is no way to increase the 1X mode resolution of any Canon DSLR. The only way I can imagine would be to combine 4 pixel to one cluster and skip clusters instead of pixels. But I doubt that this is possible and it might affect the image quality. Time to stop dreaming and be happy with what we have I guess ;D
In fact at least my 60D has another frame skipping algorithm, it's activated in 5x zoom mode: it skips 2 lines and keeps 3 consecutive lines. But apparently it gives bad aliasing. In general for line skipping to work, the rule is to consecutively skip multiples of 2 lines. You can then keep any amount of lines.
Any thoughts as to why the raw module will not let me record any resolution higher than 1500p on a LEXAR 1000x 128 gb card that has write speeds of 145mbs?
Quote from: LukeJflowers on July 02, 2013, 10:14:46 PM
Any thoughts as to why the raw module will not let me record any resolution higher than 1500p on a LEXAR 1000x 128 gb card that has write speeds of 145mbs?
In non crop mode we can record every 3rd line, hence 1528 pixels. In crop mode (zoom) we can do 1080p@24fps.
Quote from: Rawolution on July 02, 2013, 10:24:18 PM
In non crop mode we can record every 3rd line, hence 1528 pixels. In crop mode (zoom) we can do 1080p@24fps.
How would one turn it to crop mode?
Quote from: LukeJflowers on July 02, 2013, 10:59:04 PM
How would one turn it to crop mode?
haha got it thanks!
Quote from: Rawolution on July 02, 2013, 10:24:18 PM
In non crop mode we can record every 3rd line, hence 1528 pixels. In crop mode (zoom) we can do 1080p@24fps.
Although this does skip several frames is this something that has happened to everyone?
Getting continous 24p 1584x1056 with Komputerbay 32Gb 1000x. Non crop mode.
Awesome aspect ratio, full sensor. I ve seen improved the aliasing issue with this resolution. Is that possible or just placebo?
Thanks folks awesome job.
Yay, my 50D arrived, so happy ;D Still waiting for my cf card though...
Btw, if anyone needs to fix a broken submirror pin...
(http://i.imgur.com/nP9Vxth.jpg)
lol
QuoteI ve seen improved the aliasing issue with this resolution. Is that possible or just placebo?
VS h264 for sure, vs other raw, not really.
Quote from: 1% on July 03, 2013, 03:36:54 PM
VS h264 for sure, vs other raw, not really.
I should test it more extensively. From what I have "seem" looks better than the 5d2 I own. I will make a comparative with various aspect ratios and cameras. Thanks 1% for your efforts. Good luck with 24p native mod, it will be a giant step for this camera.
Im getting red dots all over my image when I review my footage. Not sure if thats the moire or if the camera is broken or if this is normal...i havent seen these red dots in other peoples videos. HELP! :) thanks
(http://i958.photobucket.com/albums/ae65/ultramaze/42d0ad17-f337-4579-a6f4-823c6082670a.jpg) (http://s958.photobucket.com/user/ultramaze/media/42d0ad17-f337-4579-a6f4-823c6082670a.jpg.html)
the internet has softened the image a bit but there is a ton of red dots all over the leaves in my footage....
Quote from: ultramaze on July 03, 2013, 09:04:12 PM
Im getting red dots all over my image when I review my footage. Not sure if thats the moire or if the camera is broken or if this is normal...
What did you use to process the RAW videos? RAW2DNG to create DNG images and something else to convert the DNGs to JPEG I guess?
What ever you used for the DNG->JPEG step probably has a bad debayering algorithm. Use something else.
Quote from: ultramaze on July 03, 2013, 09:04:12 PM
Im getting red dots all over my image when I review my footage. Not sure if thats the moire or if the camera is broken or if this is normal...i havent seen these red dots in other peoples videos. HELP! :) thanks
(http://i958.photobucket.com/albums/ae65/ultramaze/42d0ad17-f337-4579-a6f4-823c6082670a.jpg) (http://s958.photobucket.com/user/ultramaze/media/42d0ad17-f337-4579-a6f4-823c6082670a.jpg.html)
the internet has softened the image a bit but there is a ton of red dots all over the leaves in my footage....
Looks like a bad case of moire between those leaves and siding. :(
It can be some moire issue. On 6D i had many green and blue blocks especially on the trees (very detailed shots) . They are all gone after installing VAF anti aliasing/moire filter.
Quote from: kgv5 on July 03, 2013, 09:35:05 PM
It can be some moire issue. On 6D i had many green and blue blocks especially on the trees (very detailed shots) . They are all gone after installing VAF anti aliasing/moire filter.
okay cool! do you know if the VAF anti aliasing/moire filter for the 60d will work on the 50d???
I don't know, sorry.
Quote from: ultramaze on July 03, 2013, 09:41:34 PM
okay cool! do you know if the VAF anti aliasing/moire filter for the 60d will work on the 50d???
That's going to be the next hurdle here...
Quote from: nightvision04 on July 03, 2013, 10:10:19 PM
That's going to be the next hurdle here...
hope we can get a filter for the 50d!
you can check my thread about VAF-6D
http://www.magiclantern.fm/forum/index.php?topic=6577.0
i uploaded some footages, there is also nice comparison video made by noisyboy - it shows how the filter handles those nasty colour blocks. I bet it works the same with 60d, so maybe it could make the same with 50d.
I think the only way is just to find someone with 60d and the filter and try to put it in 50d. Couple days ago I asked mosaic engineering guys if VAF-6D will fit 5D2 but no answer, i think they won't answer about 60d/50d either.
Since a VAF filter for the 50D is no option at the moment, using a different Software might help too.
I got similar results when I open my DNG images with Google Picasa, but by opening them with Lightroom 4 I got rid of the colorfull borders.
Probably because Picasa's debayering sucks.
So if you aren't using ACR or Lightroom already, you might want to give them a try.
Same thing goes for Resolve. It's debayering isn't as good as results using ACR.
Sharp 50D footage needs a pass through ACR, the best way is to import directly into After Effects and use the defringe option.
Play with the amount and with the colors it affects, keep an eye not destroying your edge colors, you might not see it at first sight but it's noticable.
(http://thelightroomlab.com/wp-content/uploads/2012/05/Lightroom-4_1-Color-Fringe-Removal-Tools.jpg)
wow. this is all great. thanks guys. gonna run through ACR next time i need it.
Here is a little test film I threw together. Love the 50D and I love my girlfriend :)
https://vimeo.com/69669066
Quote from: ultramaze on July 04, 2013, 05:36:55 AM
Here is a little test film I threw together. Love the 50D and I love my girlfriend :)
https://vimeo.com/69669066
Oh, this is you Dave! Its me, Dan. :)
Brilliant color! Did you use a Print LUT? Resolve?
At 0:05, I knew it was gonna be a mindblow.
This will solve your purple magenta fringing/moire problem in resolve...
http://550draw.blogspot.com/
New 50D user here.. :)
I succeded in having everything working and recording RAW video, but I have problems in post.
I used Raw2DNG (PC) to convert the files, photoshop opens the files correctly but DaVinci opens a tiny preview in magenta tint as big as an icon.
What's wrong? Can somebody help me?
Quote from: riccardocovino on July 04, 2013, 03:50:59 PM
New 50D user here.. :)
I succeded in having everything working and recording RAW video, but I have problems in post.
I used Raw2DNG (PC) to convert the files, photoshop opens the files correctly but DaVinci opens a tiny preview in magenta tint as big as an icon.
What's wrong? Can somebody help me?
You need raw2cdng by Chmee. Search the forum for the topic ;)
I use Andy600's last build. When i'm in 5x crop mode, and record a video, the image is not in the center. When i watch recorded meterial, i see that it slided to the left. Is it the way to record centered video in 5x crop mode?
Go to zoom box settings in the menu and change to snap to 5x center. When you're in crop mode (zoomed) press the joystick ;)
Quote from: ultramaze on July 04, 2013, 05:36:55 AM
Here is a little test film I threw together. Love the 50D and I love my girlfriend :)
https://vimeo.com/69669066
Beautiful footage you making the 50D shine. What was your workflow? ACR into Davinci, or RawMagic straight into Davinci? Did you use any sharpening?
Quote from: Andy600 on July 04, 2013, 03:59:23 PM
Go to zoom box settings in the menu and change to snap to 5x center. When you're in crop mode (zoomed) press the joystick ;)
Hmm, it does not work. I set "snap to 5x center" and in the crop mode when i press joystick (center, not left or right) the image just jumped to the left a bit. When i try to record, the image is still not on the center. I press joystick again and it jumpes again to the left and to the top a little bit.
Quote from: Andy600 on July 04, 2013, 03:55:30 PM
You need raw2cdng by Chmee. Search the forum for the topic ;)
It worked, thanks!
Info on settings in ML, conversion and editing in main softwares are scattered through 80+ pages of topic, would you think it could be of great help to sum it up on first topic?
richt now it has links to other posts regarding installation of ML and RAW modules, but nothing from then on.
thank you again for all the great efforts of coders, users, forum moderators!
Quote from: riccardocovino on July 04, 2013, 05:03:46 PM
It worked, thanks!
Info on settings in ML, conversion and editing in main softwares are scattered through 80+ pages of topic, would you think it could be of great help to sum it up on first topic?
richt now it has links to other posts regarding installation of ML and RAW modules, but nothing from then on.
thank you again for all the great efforts of coders, users, forum moderators!
It's not camera specific and there are already topics for setting up and shooting raw plus all the conversion options etc but I will add the relevant post links to the first post when I have a few mins spare.
Got my CF card today, went with a 64gb 600x Komputerbay since no one appeared to have test that yet... it's garbage. Was advertised as 60 mb/s and 90 mb/s, but the write speed is 24 mb/s, and the read is 20 mb/s. Ridiculous.
Edit: Did the first test in the afternoon, running the benchmark again, write speed is 17.5 mb/s, read is 8.4 mb/s... it's a dud
I posted about this card about 2-3 times on this tread and others advising not to buy it and saw similar experiances from other people. Some reading would have saved you the hassle of sending it back ;)
on 50D i'm seeing the Canon full color screen when in ML Grayscale until i hit record then it switches to grayscale.
(recent unified build)
Movie -> Raw Video -> Preview ->ML Grayscale
is this a bug? is this happening on the tragic builds from 1%?
also, the 50D ML grayscale is beautifully detailed in comparison to ML grayscale on 5D3.
note: for those PM'ing me about pink frames - you should not get pink frames in any recent build.
when the white point (set in the exif) of the DNG is above the actual white level you will see a pink frame.
these bugs were fixed weeks ago.
do not be fooled by pink preview images.
if you have a DNG from a recent build which is pink when viewed in gimp or a commercial tool then that is a bug.
post the DNG image and build info to the forum.
@ultramaze thanks for the video - like the hand held vérité shots in the car - parthenon is not a bad place for a picnic. 8)
Hi everyone. This is my first post on a ML forum. Just bought a 50D and really hope to make some tests too.
I'm having trouble to get a fast CF card, though. Since the 50D can't be as fast as a 5D3 because of the RAM, can someone help me on this one? I know that Komputerbay 1000x has the best perfomance for price by now, but I can't find who could ship me a card: I'm in Brazil. And I searched on eBay, Amazon and so on, all with answers like "we can't ship to Brazil right now". :-\
I could buy a Lexar 1000x, but it's just too expensive and I don't know if I'll need all that. So, I started reading everything here and, aside tests of a Komputerbay on a 50D, all I found was some guy complaining about the Transcend 1000x 16GB.
http://www.magiclantern.fm/forum/index.php?topic=5481.msg40408#msg40408
Sugestions, options, anyone?
Quotealso, the 50D ML grayscale is beautifully detailed in comparison to ML grayscale on 5D3.
I told you before - if it's that beautifully detailed, it's not ML grayscale, it's Canon LiveView with a workaround for masking the pink tint.
ML grayscale is for correct framing. You can't have it at realtime speed, just as you can't playback FullHD video on a 486.
1% enabled display filters. You probably need to do the same thing; I'd research a more robust method instead, using the EDMAC, because the 5D2 method leaves LiveView in a "hacked" state (single-buffered, with tearing).
Quote from: bzhwindtalker on July 04, 2013, 08:04:02 PM
I posted about this card about 2-3 times on this tread and others advising not to buy it and saw similar experiances from other people. Some reading would have saved you the hassle of sending it back ;)
I did that, but there was only ever talk about the 32 gig version (or I missed it).
Quote from: a1ex on July 04, 2013, 08:23:38 PM
I told you before - if it's that beautifully detailed, it's not ML grayscale, it's Canon LiveView with a workaround for masking the pink tint.
1% enabled display filters. You probably need to do the same thing; I'd research a more robust method instead, using the EDMAC, because the 5D2 method leaves LiveView in a "hacked" state (single-buffered, with tearing).
yes - sorry for any repetition - thank you - wanted to alert the 50D users and ask if it was different on 1% builds.
so on 50D it is not ML Grayscale - rather gray covering up the pink.
Quote from: Molinsky on July 04, 2013, 08:19:59 PM
Hi everyone. This is my first post on a ML forum. Just bought a 50D and really hope to make some tests too.
I'm having trouble to get a fast CF card, though. Since the 50D can't be as fast as a 5D3 because of the RAM, can someone help me on this one? I know that Komputerbay 1000x has the best perfomance for price by now, but I can't find who could ship me a card: I'm in Brazil. And I searched on eBay, Amazon and so on, all with answers like "we can't ship to Brazil right now". :-\
I could buy a Lexar 1000x, but it's just too expensive and I don't know if I'll need all that. So, I started reading everything here and, aside tests of a Komputerbay on a 50D, all I found was some guy complaining about the Transcend 1000x 16GB.
http://www.magiclantern.fm/forum/index.php?topic=5481.msg40408#msg40408
Sugestions, options, anyone?
Estou proximo de SP talves possa ajuda-lo, estou fazendo experiencia com duas 50D. Por favor mande um PM abraços
Quoteso on 50D it is not ML Grayscale - rather gray covering up the pink.
Either you have the ML preview of the raw or you have the desaturated "canon" preview in zoom mode.
Both are gray but one shows you the whole frame, the other just a tiny window.
Quote from: funkysensation on July 04, 2013, 01:47:30 PM
This will solve your purple magenta fringing/moire problem in resolve...
http://550draw.blogspot.com/
The free version of resolve has the denoiser disabled. Just so you know. Perhaps, it's best to do the defringing in ACR or lightroom, save the images, then work in resolve for coloring.
QuoteThe free version of resolve has the denoiser disabled. Just so you know. Perhaps, it's best to do the defringing in ACR or lightroom, save the images, then work in resolve for coloring.
I just tried this technique yesterday, but instead of the noise reduction on the chroma node, I used blur. Has pretty much the same effect. I still prefer a pass through ACR though rather than bringing in the the CinemaDNG files directly into Resolve.
Still trying to find the optimal workflow, but am slightly stumped. Would be cool to know what other 50d shooters are doing.
CANON 50D- My Mercedes Raw test shoot video
Here's a another quick test of the Magic Lantern Raw firmware on my Canon 50D.
I wanted to see how much I could push the contrast and shadows, but still maintain visibility of the subject ( in this case, car) I was filming.
Camera: Canon 50D with Magic Lantern Raw firmware
Lens: Tokina 11-16mm
Workflow: RAWMagic, AE, ACR, Final Cut
Latest Build: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/magiclantern-2013Jun28.50D.109.go.unified.3ecd254bdba1.zip
Quote from: menoc on July 05, 2013, 05:20:31 AM
The free version of resolve has the denoiser disabled. Just so you know. Perhaps, it's best to do the defringing in ACR or lightroom, save the images, then work in resolve for coloring.
Would the CDNGs open in ACR and still be recognized by resolve?
Quote from: artiswar on July 05, 2013, 12:33:24 PM
Would the CDNGs open in ACR and still be recognized by resolve?
If you make adjustments on the raw it's no raw anymore.
Okay so I'm running continuously at 1584 x 1056 which is exciting. I just need to squeeze a bit extra out for my focus peaking on Global Draw, is this possible? I'm using Gregory of Manhattens June 28th build, 32GB Komputerbay 1000x, small hack's on. Global draw just focus peaking activated.
Also when benchmarking do you load the RAW modules first? I'm getting about 75-80MB/s without them loaded and 45-50MB/s with them loaded. Does that sound right?
Sorry for the stupid questions, couldn't find the answers elsewhere.
Cheers
Quote from: artiswar on July 05, 2013, 12:33:24 PM
Would the CDNGs open in ACR and still be recognized by resolve?
I do it all in After Effects but that's how it should work. ACR modifies the dng files themselves but preserves the structure and format. So, you could reduce noise and defringe in ACR, hit OK to save the files, then import into Resolve. The changes from ACR should be preserved in Resolve.
ACR modifies the files? It never did for me. I'm assuming its applying whatever you picked out to every image when you are previewing/rendering from AE.
I would think you need to do resolve first or just grade the video produced by AE. I can see it doing something like that if you batch through photoshop. Even then wouldn't the settings just get saved to the meta data like with light room, etc. I have ACR 8.1 and this is how it seems to work for me.
Quote from: Supermac on July 05, 2013, 03:53:23 PM
Okay so I'm running continuously at 1584 x 1056 which is exciting. I just need to squeeze a bit extra out for my focus peaking on Global Draw, is this possible? I'm using Gregory of Manhattens June 28th build, 32GB Komputerbay 1000x, small hack's on. Global draw just focus peaking activated.
Found this posted somewhere on the forums. If you can't use Focus Peaking (which is awesome btw) try using Cartoon Look 1 under Creative Effects. Movie tab -> Creative Effects -> Cartoon Look -> Mode 1
This brings out the edges quite a bit more. Of course, this does not write to the RAW file, so you're all good. Not nearly as good as Focus Peaking, but a good alternative for finding edges if you can't get that squeeze.
Quote from: dsManning on July 05, 2013, 05:28:54 PM
Found this posted somewhere on the forums. If you can't use Focus Peaking (which is awesome btw) try using Cartoon Look 1 under Creative Effects. Movie tab -> Creative Effects -> Cartoon Look -> Mode 1
This brings out the edges quite a bit more. Of course, this does not write to the RAW file, so you're all good. Not nearly as good as Focus Peaking, but a good alternative for finding edges if you can't get that squeeze.
Nice tip thanks.
Quote from: 1% on July 05, 2013, 05:12:08 PM
ACR modifies the files? It never did for me. I'm assuming its applying whatever you picked out to every image when you are previewing/rendering from AE.
I would think you need to do resolve first or just grade the video produced by AE. I can see it doing something like that if you batch through photoshop. Even then wouldn't the settings just get saved to the meta data like with light room, etc. I have ACR 8.1 and this is how it seems to work for me.
Well, I'm gonna test it . . .
Quote from: nightvision04 on July 04, 2013, 09:08:16 AM
Brilliant color! Did you use a Print LUT? Resolve?
At 0:05, I knew it was gonna be a mindblow.
thanks man! ya i used a print LUT in Resolve! just like you! i watched your tutorial on youtube and had to give it a try! thanks for sharing!
Quote from: GregoryOfManhattan on July 04, 2013, 08:13:36 PM
on 50D i'm seeing the Canon full color screen when in ML Grayscale until i hit record then it switches to grayscale.
(recent unified build)
Movie -> Raw Video -> Preview ->ML Grayscale
is this a bug? is this happening on the tragic builds from 1%?
also, the 50D ML grayscale is beautifully detailed in comparison to ML grayscale on 5D3.
note: for those PM'ing me about pink frames - you should not get pink frames in any recent build.
when the white point (set in the exif) of the DNG is above the actual white level you will see a pink frame.
these bugs were fixed weeks ago.
do not be fooled by pink preview images.
if you have a DNG from a recent build which is pink when viewed in gimp or a commercial tool then that is a bug.
post the DNG image and build info to the forum.
@ultramaze thanks for the video - like the hand held vérité shots in the car - parthenon is not a bad place for a picnic. 8)
lol thanks! parthenon is a great place for a picnic!
Quote from: goldenchild9to5 on July 04, 2013, 04:50:03 PM
Beautiful footage you making the 50D shine. What was your workflow? ACR into Davinci, or RawMagic straight into Davinci? Did you use any sharpening?
RawMagic to Resolve to FCPX. No sharpening. I used a custon LUT I downloaded off the internet. Learned a lot from my friend Dan. http://www.youtube.com/watch?v=E8Bg4E2SyRE
Wanted to share my latest piece using the 50D Raw (off of the June 28th build).
80% shot on raw, and slow mo pieces using 60D video.
It's becoming smoother using Davinci Resolve to start things off. The color matching gets a bit cluttered, but w/ a LOG export setup from the Raw sources, it streamlines things a bit.
Is there anyway to currently be able to view the screen during recording at 1:1 "zoom" mode? If I could see my framing and not have the like 5 fps lag I would be a very happy man.
Quote from: KahL on July 06, 2013, 08:32:04 AM
Wanted to share my latest piece using the 50D Raw (off of the June 28th build).
80% shot on raw, and slow mo pieces using 60D video.
It's becoming smoother using Davinci Resolve to start things off. The color matching gets a bit cluttered, but w/ a LOG export setup from the Raw sources, it streamlines things a bit.
nice one!
how did you synch audio? did you have a clapboard?
Got to try out the 5x crop mode for filming birds today. Always thought the Full HD crop mode was the best kept secret killer feature of the 600D, so I'm really impressed with how well it works on the 50D. :) Sure beats the 640x480 crop mode on the 550D.
It would be great if you could save presets for commonly used settings so you could quickly respond to different situations without getting bogged down with technicalities each time. I also keep wishing I could choose 'delete last video' or see thumbnails of raw videos on the camera since you can so easily end up with GB's of video you know you're going to have to delete on the computer later.
Used the sigma 70-200 at 200mm.
Quote from: ultramaze on July 06, 2013, 08:38:35 AM
Is there anyway to currently be able to view the screen during recording at 1:1 "zoom" mode? If I could see my framing and not have the like 5 fps lag I would be a very happy man.
Have you tried keeping global draw on?
The older build im using lets me frame in grayscale if you keep global draw on. I get 9 seconds with global draw on (for framing) and about 17 seconds with global draw off (without framing).
Quote from: riccardocovino on July 06, 2013, 10:30:12 AM
nice one!
how did you synch audio? did you have a clapboard?
Somewhat. I used the impromptu hand-clap method on site. I use that often for rushed shots alongside the recorders and it definitely helps.
Hey all,
I still have some strange behaviour in the latest unified builds:
When I adjust shutter speed in M mode, it does not change freely but at some point ISO starts changing. So I get 800eq while the top LCD shows 1600 ISO.
Will appreciate any tips.
ALSO, recently shot BMCC against 50D in terms of DR. Black Magic definitely wins, but not overwhelmingly. If anyone is interested I will post results.
Please post these results BMCC vs 50D. Can't wait to see how the pocket cinema camera shots are also compared to the 50D.
Hey guy's just uploading a new 50D video. This test was to simulate film working on a LUT.
Quote from: rommex on July 06, 2013, 02:14:26 PM
Hey all,
I still have some strange behaviour in the latest unified builds:
When I adjust shutter speed in M mode, it does not change freely but at some point ISO starts changing. So I get 800eq while the top LCD shows 1600 ISO.
Will appreciate any tips.
hi @rommex - did you have LiveView off?
with LiveView off - the shutter speed cannot be adjusted lower than 1/24 from the ML Exposure menu.
obviously, you can use the canon top main dial to adjust the shutter speed to any desired value.
i had to do this last night setting up a timelapse with LiveView off.
see discussion "Shutter speed, what am I missing" http://www.magiclantern.fm/forum/index.php?topic=4055.0
@Rommex - Is ETTR on? ML ISO values will usually override Canon values
BTW latest build of @1%'s Tragic Lantern is up if anyone wants to try it: https://bitbucket.org/andy600/tl50d/downloads
QuoteWhen I adjust shutter speed in M mode, it does not change freely but at some point ISO starts changing. So I get 800eq while the top LCD shows 1600 ISO.
50D really lies about shutter. Those lower shutters are not possible in LV, in reality the camera is adjusting ISO to keep the expo sim "accurate". Turn on expo override for it to stop doing this.
Quote from: 1% on July 05, 2013, 05:12:08 PM
ACR modifies the files? It never did for me. I'm assuming its applying whatever you picked out to every image when you are previewing/rendering from AE.
I would think you need to do resolve first or just grade the video produced by AE. I can see it doing something like that if you batch through photoshop. Even then wouldn't the settings just get saved to the meta data like with light room, etc. I have ACR 8.1 and this is how it seems to work for me.
After running some tests, it is evident that Resolve does not see changes made to DNGs in ACR. Since Resolve Lite does not have Noise Remover Enabled, then most likely you'll have to choose one or the other as a post workflow. If you choose Resolve Lite, then you'll have to use a different method of noise reduction. see link below:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg57336#msg57336 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg57336#msg57336)
Re: STRANGE SHUTTER SPEEDS
Thanks people for your fast replies.
Now, the LiveView was ON for sure.
I disabled ETTR module completely (basically I don't get the whole idea of auto adjustment of exposure components - they are valuable creative tools for me).
Exposure override was ON as I can remember.
I'm asking all this because there was no such problem in Build 28 May. At all I mean. I was setting shutter speed manually 1/50 or 1/8000 and I could tell from shooting a moving object it WORKED.
Those speeds are just gain.
Turn off movie recording. Now set a shutter like 32" with expo override on. It will get bright, turn down the aperture and look at the wonderful lines of noise on the screen.
I have notice that when you nail exposure, the photo and the video result is about half stop underexposed. If I select constant expo in FPS override the exposure result is right with I saw in LV, but It can use only 100-200 Iso before it flickers. Is there something I do not do right?
I am using 27Jun build, FPS override 24p exact fps, ettr ON, exposure simulation ON, manual lens, M mode.
Sorry to go off topic, but hope 1% knows what happen. Thanks.
Quote from: 1% on July 06, 2013, 10:09:52 PM
Those speeds are just gain.
Turn off movie recording. Now set a shutter like 32" with expo override on. It will get bright, turn down the aperture and look at the wonderful lines of noise on the screen.
Ok, I see, but a very practical situation:
I'm trying to change shutter speed from 1/25 to 1/50, the value gets stuck somewhere at 1/37 and then ISO starts changing, and I get 800eq on the screen while LCD shows 1600.
Now, what should I do next? How must I understand this quirk?
(LiveView On, ETTR disabled, exp. OVERRIDE ON)
Is there a tool that is capable of playing the raw file generated by ML? A 640 pixel wide resolution would be fine. I just need to see what I recorded. Didn't want to extract it and post process it just to see what it is.
Thanks!
Ginger HDR for AE can read RAW w/o conversion...
If override is on it shouldn't be touching ISO.
The problem is finding correct shutter timings because canon keeps changing everything... it alters the shutter timer when you change ISO in movie mode so finding the "real" value is hard. I think I finally did.. 1/60 shows as 1/60.
It also likes setting the shutter timer to 1241 and using other parameters to do expo sim.
I guess next build you can try it... really need to set shutter w/ adtg on this camera.
bitbucket is upgrading
#define TG_FREQ_SHUTTER 38760000 // ShutterT (646) * 60000 ISO 100 1/60.0
//~ #define TG_FREQ_SHUTTER 74460000 // ShutterT (1241) * 60000 1/30 shows 1/60
//~ #define TG_FREQ_SHUTTER 37230000 // ShutterT (1241) * 60000 1/60/2
Thank you, 1%
Looking forward to it having been fixed. If you need me to video shoot the monitor with such specific cases, let me know.
Quote from: 1% on July 07, 2013, 09:58:19 PM
If override is on it shouldn't be touching ISO.
The problem is finding correct shutter timings because canon keeps changing everything... it alters the shutter timer when you change ISO in movie mode so finding the "real" value is hard. I think I finally did.. 1/60 shows as 1/60.
It also likes setting the shutter timer to 1241 and using other parameters to do expo sim.
I guess next build you can try it... really need to set shutter w/ adtg on this camera.
bitbucket is upgrading
#define TG_FREQ_SHUTTER 38760000 // ShutterT (646) * 60000 ISO 100 1/60.0
//~ #define TG_FREQ_SHUTTER 74460000 // ShutterT (1241) * 60000 1/30 shows 1/60
//~ #define TG_FREQ_SHUTTER 37230000 // ShutterT (1241) * 60000 1/60/2
Great work 1% getting the right shutter speed would be awesome.. So all this time the 50D wasn't showing the right shutter? but still the motion & cadence looks so filmic that might be the magic sauce 8) just saying.
Its fixed enough... but not perfect. 1/30 exists (you weren't hoping for 1/25 in 30fps mode?), 1/30 canon is actually ~1/31 1/25 is 1/30 since you can't have shutters lower than FPS.
When I set the 1/30 actual I get no movement on my laptop screen so it would appear in sync with the screen.
Canon is really doing something weird in modes like AV/TV... neither aperture or shutter is close to real speeds and in movie mode these settings are completely useless. I.e screen darkens when you move the aperture while the aperture doesn't click.
With expo override its a bit better and things move as they should. However the top wheel only moves real shutter when going backwards an tends to skip one adjustment going forward.
Quote from: 1% on July 08, 2013, 12:00:39 AM
.....you weren't hoping for 1/25 in 30fps mode?......
))) My only hope was 1/50 @25fps - my main shooting setup in 99% cases.
I can get 1/50.5 right now. 1/50 in High Jello.
Anyone have a download link mirror to the current build?
Bitbucket appears to be down.
Thanks,
Quote from: 1% on July 08, 2013, 12:00:39 AM
Its fixed enough... but not perfect. 1/30 exists (you weren't hoping for 1/25 in 30fps mode?), 1/30 canon is actually ~1/31 1/25 is 1/30 since you can't have shutters lower than FPS.
When I set the 1/30 actual I get no movement on my laptop screen so it would appear in sync with the screen.
Canon is really doing something weird in modes like AV/TV... neither aperture or shutter is close to real speeds and in movie mode these settings are completely useless. I.e screen darkens when you move the aperture while the aperture doesn't click.
With expo override its a bit better and things move as they should. However the top wheel only moves real shutter when going backwards an tends to skip one adjustment going forward.
All that matters it's that it's close.. I don't think we would even see the difference. On the 5D Mark II you think the Shutter is exact?
Its probably better, it is on 6D, 600D, etc. In photo mode you're fine but as a video camera the LV image is what you're actually recording. The shutter is just image blanking so can be checked with something that flashes at set frequencies.
Quote from: 1% on July 08, 2013, 03:56:35 AM
Its probably better, it is on 6D, 600D, etc. In photo mode you're fine but as a video camera the LV image is what you're actually recording. The shutter is just image blanking so can be checked with something that flashes at set frequencies.
Got it now great explanation.. How would you say the 50D and 5D Mark II compares in image quality, I'm loving both images over the 5D Mark III.
You can compute exact shutter speeds from ADTG blanking register. No need to guess TG_FREQ_SHUTTER - you get the sensor duty cycle (0-100%), scale it with 1/FPS and that's it.
(and this proves that my previous hypothesis about NTSC TG_FREQ_SHUTTER was wrong on all cameras).
Quote from: a1ex on July 08, 2013, 06:27:38 AM
You can compute exact shutter speeds from ADTG blanking register. No need to guess TG_FREQ_SHUTTER - you get the sensor duty cycle (0-100%), scale it with 1/FPS and that's it.
(and this proves that my previous hypothesis about NTSC TG_FREQ_SHUTTER was wrong on all cameras).
So that means you got the Shutter to work as it should 8)
Any news on the beep on rec issue?
That's still the only easy solution when you cannot clap hands or boards..
QuoteYou can compute exact shutter speeds from ADTG blanking register
I've had no luck finding the address of the register in other cameras.. I can't even find it on 5D3.. I see the XX5F and XX61 which look like they have shutter but either get 1/0 when I use those or just one immobile 1/fps shutter. 5E and 60 addresses from 5D3 don't work.
Quote(and this proves that my previous hypothesis about NTSC TG_FREQ_SHUTTER was wrong on all cameras).
Not exactly wrong but not really right either... they seem to be off by some amount even when calculated from the shutter timer. i.e. 1/48 is 1/47 on 6D. on 50D 1/48 doesn't turn green, etc.
Finally finished up the fashion film short that I posted still frames from a few pages back. This was done on a previous build (that kept crashing w/ my DP4 EVF plugged in) and gave some great results. It's fully colored as well, but if I get enough requests, I'll post up the uncolored version from the DPX LOG export (with and w/o the base Kodak LUT).
Quote from: 1% on July 08, 2013, 04:16:45 PM
I've had no luck finding the address of the register in other cameras.. I can't even find it on 5D3.. I see the XX5F and XX61 which look like they have shutter but either get 1/0 when I use those or just one immobile 1/fps shutter. 5E and 60 addresses from 5D3 don't work.
For 5D2:
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404B4110) // ADTG register 105F
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404B4114) // ADTG register 1061
Quote from: KahL on July 08, 2013, 06:12:51 PM
Finally finished up the fashion film short that I posted still frames from a few pages back. This was done on a previous build (that kept crashing w/ my DP4 EVF plugged in) and gave some great results. It's fully colored as well, but if I get enough requests, I'll post up the uncolored version from the DPX LOG export (with and w/o the base Kodak LUT).
Great video Kahl like the mood, and cinematography.
Quote from: a1ex on July 08, 2013, 06:22:37 PM
For 5D2:
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404B4110) // ADTG register 105F
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404B4114) // ADTG register 1061
So that means you found them for the 5D Mrk II..
Hello All,
First off thanks for the hard work/community of this forum, really amazing.
So just got a nice low shutter 50D and loaded up the June 28th build and it's working but a bit strange. I can only shoot about 400mb of footage before it stops recording. Could this be buffer issues that I could tweak? In addition I just can't seem to be able to change the resolution size beyond the raw default. I have tried but my gray menu says "N/A" and even when I hit function I can't seem to trigger anything new.
I'm sure within the 84 pages of posts the answers are there (and I have looked) but any simple newbie advice would be great.
One thing to know:I picked up the Komputer Bay UDMA7 card that is 128G. Could this be the problem? Maybe the it should be 64 or maybe UDMA6?
Thanks again in advance
J
Quote from: JBTML on July 08, 2013, 09:49:29 PM
One thing to know:I picked up the Komputer Bay UDMA7 card that is 128G. Could this be the problem? Maybe the it should be 64 or maybe UDMA6?
The 64GB Komputer Bay is faster than the 128. Also, it is hit or miss with each card, so you can return it if it doesn't do well, however, settings like GlobalDraw & others may be interfering with your speed, too. Rule of thumb - turn everything off before recording. Hope this helps.
Here's my latest footage of a Bikini Commercial using 50D Raw with June 28th build. I'm using a 16GB SanDisk Extreme Cards as I knew I wouldn't be shooting more than a few seconds at once. It worked out well. Edited in After Effects. Lens: Tamron F2.8 17-50mm + Canon f1.8 50mm.
Quote#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404B4110) // ADTG register 105F
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404B4114) // ADTG register 1061
Heh, the regs are the same but trying it I just get shutter locked at 1/30. It does follow FPS tho... 28fps produces 1/28, etc.
//~ [REG] ADTG:[0x105f00cf]
//~ [REG] ADTG:[0x106100cf]
Maybe this part is wrong?
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM) /* when reading, use the other mode, as it contains the original value (not overriden) */
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
http://www.qfpost.com/file/d?g=EGA6Fm7Ub (http://www.qfpost.com/file/d?g=EGA6Fm7Ub)
Log while changing shutter speed.
Without trying to set registers, shorter.
http://pastebin.com/UstgT5c9
Quote from: krashnik on July 08, 2013, 10:42:33 PM
Here's my latest footage of a Bikini Commercial[/youtube]
Too bad she has that ugly tattoo!
Nicely graded.
Quote from: JBTML on July 08, 2013, 09:49:29 PM
Hello All,
First off thanks for the hard work/community of this forum, really amazing.
So just got a nice low shutter 50D and loaded up the June 28th build and it's working but a bit strange. I can only shoot about 400mb of footage before it stops recording. Could this be buffer issues that I could tweak? In addition I just can't seem to be able to change the resolution size beyond the raw default. I have tried but my gray menu says "N/A" and even when I hit function I can't seem to trigger anything new.
I'm sure within the 84 pages of posts the answers are there (and I have looked) but any simple newbie advice would be great.
One thing to know:I picked up the Komputer Bay UDMA7 card that is 128G. Could this be the problem? Maybe the it should be 64 or maybe UDMA6?
Thanks again in advance
J
Try this. Getting up to 81.8mb/s on a 32GB Komputerbay 1000x now
Instead of Dialog Timers, find 'Small Hacks' in the RAW Video section and turn on. This is the new that.
Also, in the most recent build, there is a 'Warm up Card' function, which preforms the first write on boot.
http://www.magiclantern.fm/forum/index.php?topic=5586.msg54376#msg54376 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg54376#msg54376)
Thanks Guys for responding so quickly!!!
So i ordered the 32gig 1000X card today so I hope that takes care of my problems.
Quote"Try this. Getting up to 81.8mb/s on a 32GB Komputerbay 1000x now
Instead of Dialog Timers, find 'Small Hacks' in the RAW Video section and turn on. This is the new that.
Also, in the most recent build, there is a 'Warm up Card' function, which preforms the first write on boot."
So DSmanning just to be clear what is the build you were referring to that I should use? So once I find this build its really as simple as keeping the old 2.3 fir replacing the autoEX file and add the "modules" folder to the existing ML folder, then it's off to the races? I think.
Will keep you posted when the 32gig arrives,
Thanks again,
J
Quote from: 1% on July 09, 2013, 01:16:51 AM
Heh, the regs are the same but trying it I just get shutter locked at 1/30. It does follow FPS tho... 28fps produces 1/28, etc.
The shutter blanking is used to compute the sensor duty cycle. Of course, if nothing changes there, it will consider duty cycle constant and will multiply it by 1/FPS (so it will follow the FPS).
Normal values (after NRZI decode) should be between 0 and FPS timer B - 1 (roughly).
You have checked shutter speed with expo override, right?
The register seems to be changing correctly in the logs though.
First log adtg.txt has the hack on, second one is no hack. Expo override was on to have movie mode shutters and no iso shifting.
It looks more like frame shutter timer than timer b I think.
What are the register values at 1/fps and 1/8000? (or 1/4000, whatever you can get)
I would like to do some more card speed tests on the 50D, but i can't figure out how to run the benchmark or where to run it. Is it a module which should be added manually to ML or a custom build?
1/30 - lowest via frame shutter timer - 1/25 on top screen
/* 00:00:00.009929 */ ADTG
/* 00:00:00.010004 */ 01 105F 0002
/* 00:00:00.010056 */ 01 1061 0002
/* 00:00:00.010102 */ 01 1172 0665
/* 00:00:00.010143 */ 01 1173 07A7
/* 00:00:00.010181 */ 01 1178 0665
/* 00:00:00.010221 */ 01 1179 07A7
1/60 - top screen + ML
/* 00:00:00.027086 */ ADTG
/* 00:00:00.027165 */ 01 105F 03B3
/* 00:00:00.027227 */ 01 1061 03B3
/* 00:00:00.027280 */ 01 1172 0665
/* 00:00:00.027325 */ 01 1173 07A7
/* 00:00:00.027371 */ 01 1178 0665
/* 00:00:00.027413 */ 01 1179 07A7
1/7800 ML - 1/8000 top screen
/* 00:00:00.041803 */ ADTG
/* 00:00:00.041878 */ 01 105F 07F1
/* 00:00:00.041941 */ 01 1061 07F1
/* 00:00:00.041991 */ 01 1172 0665
/* 00:00:00.042049 */ 01 1173 07A7
/* 00:00:00.042101 */ 01 1178 0665
/* 00:00:00.042151 */ 01 1179 07A7
nrzi_decode(0x7F1) = 1374, FPS timer B is 1380 by default, so the values look alright. Also, if ML displays 1/30, 1/60 and 1/7800, it shows the right thing.
So... where's the problem?
These are with just shutter timer. When I enable ADTG I can't change the shutter, its stuck at 1/fps.
Quote from: guruaner on July 09, 2013, 12:23:12 PM
I would like to do some more card speed tests on the 50D, but i can't figure out how to run the benchmark or where to run it. Is it a module which should be added manually to ML or a custom build?
once you load the custom FW and then load the module there should be a 'benchmark' submenu under one of the main menu items. I can't remember which however.
PS if you have a question about something you might need to ask it multiple times before getting an answer. Almost all my tech support questions have gone unanswered on here, and the 'guide' thread does not help much either
http://postimg.org/image/ffo627dut/
Any idea why this is happening? Long spanned clip, not on the latest build. Processed through RAWmagic.
Quote from: artiswar on July 10, 2013, 10:43:51 AM
http://postimg.org/image/ffo627dut/
Any idea why this is happening? Long spanned clip, not on the latest build. Processed through RAWmagic.
"Not on the latest build" - have you tried the latest build?
It's probably a footer issue. I've seen lot of posts with this kind of problem. Search for 'spanning raw files'.
Quote from: robertgl on July 09, 2013, 08:26:40 PM
once you load the custom FW and then load the module there should be a 'benchmark' submenu under one of the main menu items. I can't remember which however.
PS if you have a question about something you might need to ask it multiple times before getting an answer. Almost all my tech support questions have gone unanswered on here, and the 'guide' thread does not help much either
There is no 'tech support' here beyond users and devs helping each other out. A lot of user questions have already been answered multiple times (though maybe not your questions specifically) and some users don't seem to know how to use the search function.
@guruaner - re: Benchmarks. You can find the tests in the 'Debug' tab under the cryptically titled 'Benchmarks' menu ;) If you can't see it you must be using a build with debug disabled (though I don't know what build that would be TBH?).
I´m thinking about the 3x zoom mode.
Maybe it´s possible to use a B4 lens on the 50D with 3x zoom mode.
This is the theory
http://2.bp.blogspot.com/-cojSlCkZDkI/Udx5rn-AYxI/AAAAAAAAABc/P8gSubLisC4/s1600/crop_text.jpg
http://550draw.blogspot.com/
Show this one off, I figure.
GH2 and 50D cut together.
http://www.youtube.com/watch?v=ZOS2PLI1n0s
Quote from: artiswar on July 10, 2013, 09:47:04 PM
Show this one off, I figure.
GH2 and 50D cut together.
http://www.youtube.com/watch?v=ZOS2PLI1n0s
Great video.. I can almost spot the 50D footage just cause of it's organic nature. Which shots exactly were the 50D's?
Quote from: goldenchild9to5 on July 11, 2013, 12:39:41 AM
Great video.. I can almost spot the 50D footage just cause of it's organic nature. Which shots exactly were the 50D's?
Thanks!
1st, 2nd, and 4th shots are all 50D. Much more but those should Give a basis to whats what.
The error I reported earlier with the corrupted CDNG. It seems to be only on an occasional basis. Any explanation? Also, in terms of frame rate, is everyone out there fiddling with shutter timers to get 23.976?
You mean 23fps with more shutter range? I can get 23.98x with all shutters.
@1% - I suppose I mean when you turn FPS override on, I don't get 23.976 straight off the bat. I have to tinker under advanced with the timers to get it, which I think might lead to some of my issues in post.
If I pick exact fps I get 23.976
Probably not the best grading or best workflow but here is some footage shot with the 50D raw hack.
Another test with the 50D. Still learning how to handle the exposure, some shots overexposed, maybe i'm still shooting as if it was h.264 ;D
There are some shots where one can see the exposure changes produced by ACR.
Nice video simulacro. I like your still composition for quite a few of the shots. Your exposure and dynamic range look pretty good. Watch a few videos for Resolve tutorials to really pull some colours. The waveform scope has become my new best friend. Hitting ⌘D to show before and after, even just after expanding my colour range in Resolve, shows a world of difference.
Good video & Good luck
Can I have a moment to share a quick suggestion?
Since I get more frames when shooting in JPEG mode, rather than RAW mode (in Canon Menu), when I shoot video I change the mode. But then I want to take a picture, so I do. Only on the computer I realise that I forget to turn the mode to RAW again.
I know about the bad settings warning feature in ML, but when I use it it constantly blinks when I shoot raw video.
So is there a way to maybe make the camera switch to JPEG when RAW video is enabled, and then switch back to RAW? Or maybe desable the bad settings warning when RAW video is enabled?
The latter might be the best idea.
Quote from: johansugarev on July 11, 2013, 08:32:12 PM
Can I have a moment to share a quick suggestion?
Since I get more frames when shooting in JPEG mode, rather than RAW mode (in Canon Menu), when I shoot video I change the mode. But then I want to take a picture, so I do. Only on the computer I realise that I forget to turn the mode to RAW again.
I know about the bad settings warning feature in ML, but when I use it it constantly blinks when I shoot raw video.
So is there a way to maybe make the camera switch to JPEG when RAW video is enabled, and then switch back to RAW? Or maybe desable the bad settings warning when RAW video is enabled?
Why not just use C1 or C2 for raw video and the other modes for photos? ;)
Thought of that and just did it. Let's hope I don't forget again.
Quote from: dsManning on July 11, 2013, 08:17:09 PM
Nice video simulacro. I like your still composition for quite a few of the shots. Your exposure and dynamic range look pretty good. Watch a few videos for Resolve tutorials to really pull some colours. The waveform scope has become my new best friend. Hitting ⌘D to show before and after, even just after expanding my colour range in Resolve, shows a world of difference.
Good video & Good luck
Thanks dsManning. Unfortunately i can´t work with Resolve, I have an old 2008 macbook. Working with AE and premiere. Gonna check some Resolve tutorial to see if i can use some tips with camera raw and premiere
I have been shooting with the 50D, feel free to pixel peep this. Variety of modes - full sensor with anamorphic 1.5x, 2x and crop mode. I'm getting 1920x818 continuously in crop mode. 65MB/s seems to be my maximum. What do you have to turn off to get 80MB/s?
Dialog refresh timer. Slowing it down only knocks the CPU down 80% of the way. Only down side is you have to toggle LV on/off to enable it if you need the canon menus to update.
Hi everyone.
I've been following this thread for some time and am currently saving money for a 50D. I've had an idea for a while and would like to hear what you all think. Since crop mode outputs a higher resolution and is free of moire and aliasing, how about using some old c-mount lenses that would not otherwise cover the sensor? Like cheap cctv lenses or old 16mm camera glass? Wouldn't this be cheaper than buying a super-wide lens that will be cropped, in case you'd like to have something wider than tele or standard range? This way only the part that isn't covering the sensor will get cropped anyway. Of course it will varry from lens to lens, but do you think it could give good results? Would there be problems with focus because of c-mount to EOS adapters or any other problems you think might occur?
I have been thinking the same for a while. I think one problem is the reading from the sensor in crop mode being far to the left. C-mount lenses are smaller so there will be vignetting and black borders? The second problem is how to get a c-mount lens to fit infinity on an eos camera. Not sure if the distance won,t hit the mirror being to close to the sensor. Anyone?
So, my conclusion is that the lens would be put to the left and a bit closer to the sensor than the eos lenses. Could be wrong though...
No chance - c-mount lenses only have 17.5 mm flange distance to the sensor. They would need to sit in the mirror box of the 50D in order to focus beyond macro distance.
Quote from: EOSHD on July 11, 2013, 11:56:27 PM
I have been shooting with the 50D, feel free to pixel peep this. Variety of modes - full sensor with anamorphic 1.5x, 2x and crop mode. I'm getting 1920x818 continuously in crop mode. 65MB/s seems to be my maximum. What do you have to turn off to get 80MB/s?
Quote from: GregoryOfManhattan on June 17, 2013, 01:53:22 AM
...
Update 26 June 2013 - there is a new "Small Hacks" feature in the raw_rec module. in the Raw Rec Detail Menu enable Small Hacks. 50D builds hit 81MB/s for hundreds or more frames at 1920x1080 in crop/zoom mode only. The goal is 83/84 MB/s as this would permit continuous 1080p24 recording.
on unified builds for many cameras the options are
Movie->Raw Video->Small Hacks
https://bitbucket.org/hudson/magic-lantern/commits/b77a85f7ac68098b219754d827fe2102fdbc5c38
Quote from: 1% on July 12, 2013, 12:00:31 AM
Dialog refresh timer. Slowing it down only knocks the CPU down 80% of the way. Only down side is you have to toggle LV on/off to enable it if you need the canon menus to update.
Edit: question answered by GregoryOfManhattan. Thanks
Edit2: using Andy600's compiled build https://bitbucket.org/andy600/tl50d/downloads
Quote from: EOSHD on July 12, 2013, 01:23:08 AM
Edit: question answered by GregoryOfManhattan. Thanks
I must be using the wrong build, since Small Hacks don't show in the raw video menu. Which build shall I download from the Tragic Lantern directory?
hi EOSHD -
1% has been producing builds and developments to
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
and its critical that a significant group of users try those builds under his direction and report back issues.
based on the code which a1ex has integrated into unified, i put together builds for 50D at:
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads
these make it easier for me to use the exact same code on a 50D as well as a 5D3 and hopefully helps the community to ensure that unified works well on the 50D.
the big speed ups the past month have happened with variable buffering and much experimentation by a1ex and the "Small Hacks" that 1% discovered to slow down Canon dialog refresh and disable Canon AE and AutoWB.
hopefully its not too confusing that there are different code bases for this alpha stage software.
a1ex and 1% may use different terminology.
with either code base, at the moment and for weeks now, one can record at 1920x1080p24 for 1000s of frames.
the instructions for the unified builds apply to all cameras - so what helps you achieve 1920x1080p24 on 50D gets you 2.2k on 5D3 and increases the number of frames at 3.5k.
several users have posted 50D 1920x1080p24 videos over the past 2 weeks with 80MB/s and more.
basically, as several users have asked - you don't get because you don't need 80MB/s for regular 1584x896p24 RAW video on the 50D - you only need 58MB/s
for 25p anamorphic shooters you could use 70MB/s for 1584x1058p25
with any of the recent builds "Small Hacks" enabled on unified - you should be able to shoot at
1584x1058p25.
i just did a test and have continuous recording at 1584x1058p25
please confirm that you can get that data rate and perhaps you could update your 11 July article as to the 65 MB/s limit.
Quote from: funkysensation on July 10, 2013, 02:07:45 PM
I´m thinking about the 3x zoom mode.
Maybe it´s possible to use a B4 lens on the 50D with 3x zoom mode.
This is the theory
http://2.bp.blogspot.com/-cojSlCkZDkI/Udx5rn-AYxI/AAAAAAAAABc/P8gSubLisC4/s1600/crop_text.jpg
http://550draw.blogspot.com/
Theres a B4 to EOS adapter from ciecio I presume - is 340$ on ebay :-\ :-\ :-\ :-\
I have three S16 arri bayonet lenses that I bet would look amazing in crop mode, but it would cost 300+$ to even test.
I guess i'll have to use them for film, or buy a BMPC or hope for a RAW video nikon V3
Quote from: EOSHD on July 11, 2013, 11:56:27 PM
I have been shooting with the 50D, feel free to pixel peep this. Variety of modes - full sensor with anamorphic 1.5x, 2x and crop mode. I'm getting 1920x818 continuously in crop mode. 65MB/s seems to be my maximum. What do you have to turn off to get 80MB/s?
Andrew that's incredible footage right there. Love the organic look of it, and it's really filmic, Like I said before I think the 50D is more filmic than the Mark III but that's just my opinion. Great job man keep the 50D videos coming.
I'm writing a comprehensive '50d raw video set-up and shoot guide' which will encompass the additional features of Tragic Lantern 2.0. It should be ready within the next few days. I'll post links.
Big thumbs up for this, Andy - I have been following rather closely and tested especially Gregory's builds but have to admit that things moved pretty quick and it was quite easy to loose track ;-)
Quote from: GregoryOfManhattan on July 12, 2013, 02:02:21 AMplease confirm that you can get that data rate and perhaps you could update your 11 July article as to the 65 MB/s limit.
Thanks. Although I was using a build without Small Hacks enabled, I did mention in the article that 80MB/s speeds were possible with the latest experimental builds. I am testing your build now and will update the blog when I've had more shooting experience with it. Right now I can't get above 70MB/s but will carry on testing and see if I can get higher, using my KomputerBay 64GB 1000x card which does 100MB/s+ in the 5D3. Keep up the good work. It's very exciting stuff.
Quote from: Andy600 on July 12, 2013, 10:55:05 AM
I'm writing a comprehensive '50d raw video set-up and shoot guide' which will encompass the additional features of Tragic Lantern 2.0. It should be ready within the next few days. I'll post links.
That would be great for Newbies Andy.. by the way yesterday was testing your lastest build for some reason my camera heated up quickly that's the first time I got the Red overheating warning any thoughts on why this is occurring?
Quote from: goldenchild9to5 on July 12, 2013, 04:22:22 PM
That would be great for Newbies Andy.. by the way yesterday was testing your lastest build for some reason my camera heated up quickly that's the first time I got the Red overheating warning any thoughts on why this is occurring?
Maybe it's the summer.
50D gets really fcking hot. I only had the warning once though. I haven't gotten it when the display timer is killed... but I haven't been shooting in the 90F heat outside so ymmv
Tested out both (Raw & JPEG) picture quality settings from Canon menu when shooting Raw but they both seem to output the same amount of (mb/s) your take @Gregoryofmanhattan @1% @Andy600 @EOSHD and to anybody else reading this. I remember in the early stages of the Hack (JPEG) Picture Quality was the setting to put the 50D on, but it seems by putting it on (RAW) I'm getting a little more filmic cadence, or motion out of the picture.
Quote from: 1% on July 12, 2013, 04:46:20 PM
50D gets really fcking hot. I only had the warning once though. I haven't gotten it when the display timer is killed... but I haven't been shooting in the 90F heat outside so ymmv
Does the overheating effects the sensor after sometime?
Quote from: goldenchild9to5 on July 12, 2013, 05:07:24 PM
Does the overheating effects the sensor after sometime?
That's why it's called overheating - heat beyond the safe levels.
What can be considered overheating for the 50D - I dont know. I don't let it go above 57 deg. Celsius.
Question: I'm trying to shoot 1584:674 raw at 30fps with Gregory's latest Jun28 build.
I don't understand the shutter values at all. Most of the time it says different things on the top screen from the ml settings in live view. The shutter sometimes locks at 1/33.3 or other values. The ISO shows 100eq or 200eq. When I change the ISO, shutter also changes. It all appears to be a bit random. I can get 1/59.7 with exposure override, but I don't think that is the correct way.
What am I doing wrong?
I use movie mode 1080p 30fps, 1584:674, no FPS override, small hacks ON, Global draw ON all modes and RAW histogram. Everything else is turned off.
And btw, does the Image Finetuning menu do anything in RAW?
Quote from: johansugarev on July 12, 2013, 06:28:01 PM
Question: I'm trying to shoot 1584:674 raw at 30fps with Gregory's latest Jun28 build.
I don't understand the shutter values at all. Most of the time it says different things on the top screen from the ml settings in live view. The shutter sometimes locks at 1/33.3 or other values. The ISO shows 100eq or 200eq. When I change the ISO, shutter also changes. It all appears to be a bit random. I can get 1/59.7 with exposure override, but I don't think that is the correct way.
What am I doing wrong?
I use movie mode 1080p 30fps, 1584:674, no FPS override, small hacks ON, Global draw ON all modes and RAW histogram. Everything else is turned off.
And btw, does the Image Finetuning menu do anything in RAW?
Download Gregory's latest July 11 Built Here: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads)
So far its running real smooth, for 30fps Raw it's best to use aspect ratio 2:21 it runs with no problems.
Quote from: goldenchild9to5 on July 12, 2013, 04:22:22 PM
That would be great for Newbies Andy.. by the way yesterday was testing your lastest build for some reason my camera heated up quickly that's the first time I got the Red overheating warning any thoughts on why this is occurring?
Not sure unless the temps were very hot where you are. I shot about 80gb of 1080/25p footage this afternoon using the latest Tragic Lantern build. It was 25C/77F in the shade but I didn't get any temp warnings or other issues. The camera does get hot compared to my 600d but I think a lot of that heat is probably in the card and body.
re: your thoughts on raw vs jpeg mode. I don't think it makes any difference to cadence but there is a difference in allocated frames when you hit record. I think this translates to fewer frames if you're shooting 1080p for instance.
BTW I was trying out my 1974 Nikon 50mm F2 again. Not bad for a 40 year old lens :D
A frame grab from today.....
[spoiler](http://i.imgbox.com/adwUJD0U.jpg) [/spoiler]
What's up guys. Say I'm from Phoenix, AZ. I've been testing a lot here recently and have done so in some temperatures above 100 degrees and up to 115. What I've noticed is that when the temperature warning light comes on I get reduced frame rates. For example, I have the FPS set to 24 with low Jello, but the actual FPS is 22.148. It appears that the sensor slows down the FPS as a means of not overheating. The camera will not shut off for any reason, which is good. But take notice of your actual FPS when shooting. You'll want to keep an eye out for how you are going to align your audio/video in post.
(http://i.imgur.com/AgG1H5w.jpg?1)
At 115 degs I'd be more worried about me dying than the camera ;D
Why are you shooting lo jello mode?
I shoot in lo-jello because the image is in line with the sensor refresh rate rather than an FPS trying to align to the shutter. It should hold better motion values. The jello effect is basically an issue with the sensor not refreshing fast enough to capture the time distances between frames. Essentially, lo-jello ought to provide a quicker capture of the time between sensor refreshes.
I'm considering shooting at 25 FPS lo-jello because it's a perfect 180 degree shutter.
Quote from: LEVISDAVIS on July 12, 2013, 10:38:22 PM
I shoot in lo-jello because the image is in line with the sensor refresh rate rather than an FPS trying to align to the shutter. It should hold better motion values. The jello effect is basically an issue with the sensor not refreshing fast enough to capture the time distances between frames. Essentially, lo-jello ought to provide a quicker capture of the time between sensor refreshes.
I'm considering shooting at 25 FPS lo-jello because it's a perfect 180 degree shutter.
Thanks :) I hadn't looked that one up yet. Does fps remain constant when you don't have heat issues?
The FPS is never an issue when I'm not shooting in high-heat situations.
(http://i.imgur.com/H1RbcsL.jpg)
(I'm not sure if this is the right place to post this,so if not, my apologies!)
I was thinking about trading in my t2i for a 50d to take advantage of the raw capabilities. If I wanted to film a long project, would a hacked 50d work better than what I've got? I've been researching specs but I'm still a bit fuzzy on how stable this thing is.
Quote from: goldenchild9to5 on July 12, 2013, 07:36:55 PM
Download Gregory's latest July 11 Built Here: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads (https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads)
So far its running real smooth, for 30fps Raw it's best to use aspect ratio 2:21 it runs with no problems.
I get the same stuff with shutter/ISO. When I put exposure override on it seems to be better, ISO says what is supposed to most of the time. But when I change it, shutter starts saying 1/33.3 and ISO 400ov. I guess it's supposed to do that, I just don't understand it. I'll reformat and try again.
Help please !! when i drag my raw file to "raw2dng" app, it not only generates a DNG folder with all the DNG files but also a MOV. file. I am confused, does the "raw2 dng" directly combine DNG file into a raw MOV. file or it is just normal H.264 format?
It generates a prores mov file, in order to preview your footage. It's only for reference. The raw frames are in the _dng folder.
Quote from: FilmPerson on July 13, 2013, 03:05:52 AM
(I'm not sure if this is the right place to post this,so if not, my apologies!)
I was thinking about trading in my t2i for a 50d to take advantage of the raw capabilities. If I wanted to film a long project, would a hacked 50d work better than what I've got? I've been researching specs but I'm still a bit fuzzy on how stable this thing is.
I have both the 50d and T2i right now and I'll have to say for the most part it depends on what you'd like to do for your "long project"
Currently I'd say the 50d ML is pretty stable for now and I hadn't had issues recording for long periods of time. Granted, it's still experimental in a way, but for the purposes of your situation let's just say it's perfectly stable.
With that said, you'll be getting into a lot more required post processing and setup when it comes to recording raw.
- External Mic and recording device (if you need sound that is)
- 1000x minimum speed CF card (64GB for about 15 min of 1584x896 res footage at 24p, ) (or slower if you're only shooting a few second clips)
- Ample amounts of hard drive space, preferably ssds for storage and transcoding
- fast cpu and lots of ram for video editing and stuff (typically that is)
- transcoding every clip
- learn to conform and grade
Also there's only a max of 1584x896 res (though upscaled to 1080p seems pretty good people say) or 1080p24 in 5x zoom
With raw you do get a minor increase in sharpness and resolution(though moire and aliasing might crop up easily, where special care needs to be taken) (or a good amount in 1080p crop), a lot in dynamic range (for grading), but you do need to know how to use it
If this is going to be a feature length film, just 1 hour would require at least 512 GB of space, and if it's a short film... well that's somewhere along the lines of footage you'd record and cut from... That is just all the raw data... Still needs to be extracted into DNGs or turned into some intermediary codec...
Anyway it'll require a LOT of work, so if you aren't familiar with the workflow or have the necessary hardware for it.. it'll be a pain..
I shoot a lot of events which are hours in length and I find that the T2i h264 at 1080p or 720p is more than sufficient since I don't need to do grading and it just gets cut together for youtube uploading. I got the 50d and a komputerbay 1000x 64gb for $650 (i paid like 100-200 more than necessary) because I want to learn about the capabilities, raw workflow, and possible further developments with ML since I am a comp eng.
If you're technically able to find grading footage shot in h264 limiting and restricting, then it's a good consideration to make, else it might be better to stick with the T2i instead of swapping it for the 50d
Can someone tell me why my exposure meters are not showing up in liveview??
Can someone please tell me if it's possible to activate the lens IS/VR before and during recording of RAW video without having to half-press the shutter button? .. If that's not possible then how can I start recording when I have the shutter button half pressed? Right now I have to release the shutter button in order to start recording with the SET button.
I am getting continues OK shooting at 2000 x 852 with Transcend x1000 32GB in x5 mode at 25fps,
also 1584 x 1056 continues Ok in normal LV mode with latest Gregory's build from 11th July(hack on - card warm up 128 MB)
and in 1920 X 1080 (X5 mode) getting 308 frames at 25 fps and 426 frames at 23.984 fps
This is huge improvement , previously only was getting up to 1340 x 1058 continues shoot.
This is real stable now ,of coarse also using exposure override and ISO works well.
Now would be comfortable to go and film music vid paid gig with 2 x 50d cameras .
It writes up to 75MB/S !
Tested many times times today and happy to confirm those numbers above they are correct , also just discovered that crop mode x5 at 24 fps I am able to just get continues shoot at 2000 x 910 ! yes,it writes about 71- 73.7MB/s sitting stable,shot 12GB STRAIGHT then my battery went flat,oops...forgot to charge/change...CONFIDENT WILL DO FULL CARD AT 2000 X 910 AT 24 FPS WITH TRANSCEND X1000 32GB
All been good but with latest build (Greg 11 Jul) I suddenly started getting a few pink dots - using RAWMagic 7b
Thoughts?
EDIT - just ran files through RAW2DNG and no pink dots... Something in RAWMagic
thanks
Strong results from the latest build as well, guys.
A few frame captures from a comedy short we're in post for, "The Passive Aggressive Little Toaster"
(http://media-cache-ec2.pinimg.com/originals/ee/d3/45/eed345b3703dda21968d2b151c039ec6.jpg)
(http://media-cache-ak0.pinimg.com/originals/86/1b/d5/861bd5cd6dcdefacce4cea741e70c699.jpg)
(http://media-cache-ak3.pinimg.com/originals/1b/b5/46/1bb5466994c151daf728ea1ba0ee7952.jpg)
So this now marks the SECOND official production that I've shot totally in Magic Lantern DNG RAW. The Director didn't mind not having playback at all actually. I just gave him a second monitor to manage the shots as if we were shooting on film. Actually it made things FASTER, since the idea of playback from a Producer or anyone else wasn't on the table :-)
*um...can we NOT have playback in the final build, by the way? HAHA*
Quote from: KahL on July 13, 2013, 11:35:11 PM
Strong results from the latest build as well, guys.
A few frame captures from a comedy short we're in post for, "The Passive Aggressive Little Toaster"
(http://media-cache-ec2.pinimg.com/originals/ee/d3/45/eed345b3703dda21968d2b151c039ec6.jpg)
(http://media-cache-ak0.pinimg.com/originals/86/1b/d5/861bd5cd6dcdefacce4cea741e70c699.jpg)
(http://media-cache-ak3.pinimg.com/originals/1b/b5/46/1bb5466994c151daf728ea1ba0ee7952.jpg)
So this now marks the SECOND official production that I've shot totally in Magic Lantern DNG RAW. The Director didn't mind not having playback at all actually. I just gave him a second monitor to manage the shots as if we were shooting on film. Actually it made things FASTER, since the idea of playback from a Producer or anyone else wasn't on the table :-)
*um...can we NOT have playback in the final build, by the way? HAHA*
Great Job Kahl.. real nice images and colors. Got a question how how did you keep the noise down from the 50D. Any specific Settings from Canon menu, and ML settings?
Quote from: goldenchild9to5 on July 14, 2013, 12:55:27 AM
Great Job Kahl.. real nice images and colors. Got a question how how did you keep the noise down from the 50D. Any specific Settings from Canon menu, and ML settings?
Well my usual setting fall in line w/ using magic lantern iso settings by default, but that may not play a part in it at all. Best guess: it's probably how I lit the scenes. Also the dng noise looks more like grain as well, so that could be a factor too.
Hi everyone,
I've been lurking on this thread since about page 35, thank you everyone for contributing so much great info! And huge thanks to the developers for the constant improvements!
I've tried searching but I've not found the info I'm looking for, but I shot with the latest Hudson build (magiclantern-2013Jul11.50D.109.go.unified.5db91070a1aa) and I'm getting this weird frame tearing:
(http://i.imgur.com/0EFaD4U.jpg)
I shot 12 different shots and I got it in each shot... any ideas as to what's happening? I've tried using raw2dng and rawmagic to process to dng, and it happens with both.
1%'s 80point1 build is the one I'm finding to be rock solid, though I understand that that is an experimental build and I'd like to get back to the standard builds if I can.
Thanks everyone, keep up the great work!
With GD off?
Quote from: KahL on July 14, 2013, 02:07:33 AM
Well my usual setting fall in line w/ using magic lantern iso settings by default, but that may not play a part in it at all. Best guess: it's probably how I lit the scenes. Also the dng noise looks more like grain as well, so that could be a factor too.
You mean by changing ISO's from ML ISO window? or its something else?
Quote from: dsManning on July 01, 2013, 03:09:22 PM
I also tried to Magic Lantern Controller app for Android which does not work for me now. https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=en (https://play.google.com/store/apps/details?id=hu.sztupy.android.mlcontroller&hl=en)
I remember trying this on an earlier RAW build (sadly don't remember which, but at least 2 weeks back) and I did have LiveView showing on my tablet using this app.
Any chance someone else out there could test to see if LiveView over USB is working for them? Easiest way to test would be EOS Utility if you have it installed on your computer. Wanting to get this set up before a shoot next weekend and I'd rather not rent a HDMI monitor when I already own a very capable 7" tablet.
Off to dig through my downloads folder to test some old builds on my backup card to see what will work. Sadly I'm no code expert, so I'm no help in finding it there. Maybe if I can find a working build a smarter up could help me compare?
EDIT: So I jumped back to one of the unified builds. ml-2013Jun18.50D.109.go.unified.d55f33a1d395 to be exact. No issue with LiveView in EOS Utility. Going to move forward and try to find where it was broken.
NEW EDIT: So it turns out after a few tests with quite a few builds, that LiveView works just fine with MagicLantern, until you enable RAW video. What I was running as my daily driver, I had my modules autostart which led me to believe it was the new builds that broke LiveView. When you install a new build (or old while I was testing back) the modules are usually set to not load at start. So with no RAW video enabled, LiveView works :-\
Thanks
Sorry to harp on this, but it seems a 5d3 user has liveview working with RAW video on an Android tablet.
http://www.magiclantern.fm/forum/index.php?topic=7054.msg58951#msg58951 (http://www.magiclantern.fm/forum/index.php?topic=7054.msg58951#msg58951)
Does anyone using the 50D have a 5D2 as well to help me with some testing? Seeing as a good amount of hardware is the same in the two, I'd like to know if the 5D2 works and compare to the 5D3 from there.
Quote from: goldenchild9to5 on July 14, 2013, 05:54:36 AM
You mean by changing ISO's from ML ISO window? or its something else?
No, they're the specific magic lantern ISO values (rather than the Canon default ISO adjustments) where you can add + or - values. They're used to decrease noise in the darks w/o compromising the highlights (such as through HL tone priority). It usually works, but in VIDEO. I'm unsure if they have an effect, if any at all in RAW frame recording.
Someone mentioned that the Canon 5OD does work with an Android tablet. However, there are some strange circumstances with the way it works... Might want to do a quick research through the past five pages or so... I kind of considered this option too... However, the limitations made using an HDMI monitor far more user friendly, in my opinion...
Quote from: 1% on July 14, 2013, 04:21:52 AM
With GD off?
Hi 1%, GD was on... I vaguely remember GD being an issue in previous builds but I thought that was all fixed? I kinda rely on the crop overlay because the box showing where the recording area is doesn't work properly when using an external monitor.
I'll test again with global draw off and report back details, but I think going back to the 80point1 build works best for me.
Thanks!
Kermis Best 2013
Camera: Canon 50D with Kowa 8Z anamorphic lens
Recording: RAW recording using magic lantern June 28 build
Workflow: RawMagic - ACR - FCP-X
Original DNG resolution: 1344 x 1058 color depth 14Bit
Kowa Anamorphic ratio is 2:1, so after conversion resolution will be 2688 x 1058
Sound: Zoom H2N 4 channel surround
Images:
http://www.gerstel.org/images/canon/M06-2200_00236.jpg
http://www.gerstel.org/images/canon/M06-2224_00341.jpg
http://www.gerstel.org/images/canon/M06-2225_00594.jpg
http://www.gerstel.org/images/canon/M06-2244_00057.jpg
Quote from: LEVISDAVIS on July 14, 2013, 08:40:46 AM
Someone mentioned that the Canon 5OD does work with an Android tablet. However, there are some strange circumstances with the way it works... Might want to do a quick research through the past five pages or so... I kind of considered this option too... However, the limitations made using an HDMI monitor far more user friendly, in my opinion...
Yup.... That was me quoting me.... I've done the testing already to show RAW breaks LV on the 50D. Just trying to make it conversation again, because it seems that the 5D3 has RAW LV, while the 50D does not.
GD on can pink frame older cameras, + do what you see. I do the best of both worlds and turn it off while recording. You can try reducing the # of indicators, check CPU usage see how high it is. 20-30% may be ok, 60-90% will probably give you bad frames.
I have later builds too, lol.
For the LV in dslr controller, etc. Does 50D even support this function without raw? Its pretty old, I'd compare with 5DII.
Quote from: jgerstel on July 14, 2013, 02:49:39 PM
Kermis Best 2013
[spoiler][/spoiler]
Camera: Canon 50D with Kowa 8Z anamorphic lens
Recording: RAW recording using magic lantern June 28 build
Workflow: RawMagic - ACR - FCP-X
Original DNG resolution: 1344 x 1058 color depth 14Bit
Kowa Anamorphic ratio is 2:1, so after conversion resolution will be 2688 x 1058, scaled to 1920 x 917 in FCP export
Sound: Zoom H2N 4 channel surround
Download original here: https://www.wetransfer.com/downloads/95ba4b144f5ad4aa540ecfbbe54b40ca20130714110657/5283384a9f6b65f817e29c13dceea58320130714110657/b0d081
Looks great but I think you forgot to conform your footage? Did you shoot with FPS Override on? I downloaded the original and it plays back at 30p and looks a little fast
I'm used to seeing a bit of aliasing and moire and usually avoid shots where it will happen but I decided to test how bad it can be.
[spoiler](http://i.imgbox.com/abuNAZbX.jpg)[/spoiler]
The woman's top is alive with a maze pattern and I often see this in highlights when I push them. Is this sensor fixed pattern noise?
Also getting sprinkles here and there.
As I say, I tend to avoid this kind of shot or shoot with a shallower DOF
Try a better demosaicing algorithm.
Yea, I get those on 6D depending on what I use to convert. So they aren't AF "helper" related? They like following edges too.
Quote from: a1ex on July 14, 2013, 05:17:20 PM
Try a better demosaicing algorithm.
I would if I knew how ;D
Nope, these are demosaic artifacts. Try AMaZE or DCB (rawtherapee has them).
edit: found a comparison: http://farm5.staticflickr.com/4139/4826692002_b975d1b5db_o.jpg
Quote from: a1ex on July 14, 2013, 05:21:13 PM
Nope, these are demosaic artifacts. Try AMaZE or DCB (rawtherapee has them).
edit: found a comparison: http://farm5.staticflickr.com/4139/4826692002_b975d1b5db_o.jpg
So its down to whatever app you use to convert to DNG/CDNG? Doh, ignore that
Wish that worked for ACR.
@Andy600
Here's your jpg processed through ACR. It's removed most of the smaller moire artifacts but the woman's shirt is too far gone. Also I suspect there will still be a fair amount of aliasing/flickering left over in the motion version.
Did you process in Resolve?
(https://dl.dropboxusercontent.com/u/24738031/ML/Andy600-ACR.jpg)
AMaZE works great on this shot.
Quote from: rockfallfilms on July 14, 2013, 06:01:14 PM
@Andy600
...Here's your jpg processed through ACR. It's removed most of the smaller moire artifacts but the woman's shirt is too far gone. Also I suspect there will still be a fair amount of aliasing/flickering left over in the motion version.
Did you process in Resolve?
Yes, processed in Resolve. I must remember to add that to Resolve feature requests.
Just tried Rawtherapee (for the first time) and it cleaned up nicely. The mosaic pattern is all but gone using AMaZE. I guess I need to refine my pre-Resolve workflow but sucks that Rawtherapee can't output DNG. If it's not one thing it's another! ;D
Yeah there's no solution that's perfect at the moment. Maybe Resolve 10 will offer debayer improvements.
Quote from: Andy600 on July 14, 2013, 06:11:20 PM
Yes, processed in Resolve. I must remember to add that to Resolve feature requests.
Just tried Rawtherapee (for the first time) and it cleaned up nicely. The mosaic pattern is all but gone using AMaZE. I guess I need to refine my pre-Resolve workflow but sucks that Rawtherapee can't output DNG. If it's not one thing it's another! ;D
That's awesome Andy I've been getting those patterns as well but couldn't find a real solution. Does it also take out edge (Fringing) from leaves? What output formats does Rawtherapee have?
Quote from: goldenchild9to5 on July 14, 2013, 07:02:57 PM
That's awesome Andy I've been getting those patterns as well but couldn't find a real solution. Does it also take out edge (Fringing) from leaves? What output formats does Rawtherapee have?
Jpeg, PNG and Tiff from what I can see. I have only just installed it so I don't know exactly but it looks like it has a full compliment of tools for NR, fixing CA etc. For me it's not really a viable option for daily use because I don't want to work with huge TIFF files and need the exposure control I have with DNG/CDNG in Resolve. It will be useful for the shots where I have issues though... and it's free :)
Quote from: Andy600 on July 14, 2013, 04:23:09 PM
Looks great but I think you forgot to conform your footage? Did you shoot with FPS Override on? I downloaded the original and it plays back at 30p and looks a little fast
Yes you are right, I shot at 24 fps in the 50D and somehow in the conversion it has been set to 30. I corrected and reposted, Thanks!
Quote from: goldenchild9to5 on July 14, 2013, 07:02:57 PM
That's awesome Andy I've been getting those patterns as well but couldn't find a real solution. Does it also take out edge (Fringing) from leaves? What output formats does Rawtherapee have?
I just tried with a horrible false color shot and it gets rid of it perfectly, also it looks like it got more resolution.
I will use this for the problematic shots!
Hi, Sorry to bother, new - my first post on ML forums...(just started RAW video on my 50d)
I have a 50d like you, its in as new condition... running a Transcend 32gb UDMA7 1000x card...
It seems to be dropping out and stopping after like 200 frames at 1280x720 and even less at the 1472x828 bigger resolution.
Do you have similar issues? Maybe my new card is buggy? or maybe try a better name brand like Lexar etc?
Any tips would be amazing, thank you. I am keen to get it all going smooth as I am ken to then get it set up on a 5dmk2 etc
thanks
toby kazumcihi.
Quote from: JulianH on May 25, 2013, 05:39:59 PM
Managed to trade my old 5D for the 50D and cash :)
I got raw recording working. Did a benchmark of Sandisk Extreme Pro 32GB 95MB/s in live view, but it doesn't seem to close the benchmark properly. I can't seem to find a log of bmp of the results. Where should it be?
Maximum seems to be around 50MB/s for continuous recording (with my card).
My results (how can I determine exactly at which frame skipping starts?):
Shot at 24 fps (didn't find a setting for 23.975..)
1592x1062 - frame skipping after about 50 frames (67.7MB/s)
1592x840 - frame skipping after about 480 frames (53.5MB/s)
1592x720 - no frame skipping (44.3MB/s)
1320x1062 - frame skipping after about 300 frames (56.1MB/s)
1320x960 - frame skipping after about 1200 frames (50.7MB/s)
1320x840 - no frame skipping (44.3MB/s)
1280x1062 - frame skipping after about 250 frames (54.4 MB/s)
1280x960 - no frame skipping (49.2MB/s)
The 50D did crash 2 times during my tests. Think it happened just after I pressed recording. Nothing happened, screen would stay on, had to take the battery out.
Big thanks to all of you amazing people making this possible. Shooting raw video on a 5 year old dslr... it's still hard to believe! ;D
I need to borrow your brains.
I finally got little bit of time to try out my 50d (just to make sure I hadn't bought a dud). I'm trying to work out what data rate I shot. My .RAW file is 215.2 MB and i shot 87 frames what is the data rate? My math puts that at 74MB/s but I shot it on a 133x card that came with the camera, am I missing something? I'm using 11th July unified.
Also my camera won't turn off, the on/off switch does nothing, any ideas?
Quote from: araucaria on July 15, 2013, 04:21:38 PM
I just tried with a horrible false color shot and it gets rid of it perfectly, also it looks like it got more resolution.
I will use this for the problematic shots!
;D Great to hear.. I'm gonna have to give it a test drive.
Quote from: kazumichi on July 15, 2013, 04:28:59 PM
Hi, Sorry to bother, new - my first post on ML forums...(just started RAW video on my 50d)
I have a 50d like you, its in as new condition... running a Transcend 32gb UDMA7 1000x card...
It seems to be dropping out and stopping after like 200 frames at 1280x720 and even less at the 1472x828 bigger resolution.
Do you have similar issues? Maybe my new card is buggy? or maybe try a better name brand like Lexar etc?
Any tips would be amazing, thank you. I am keen to get it all going smooth as I am ken to then get it set up on a 5dmk2 etc
thanks
toby kazumcihi.
I don't know too much about the Transcend 32gb UDMA7 1000x card.. but the most important question would what "Build" are you using with your 50D (Gregory's / 1% / Andy600) Let me know than I can point you in the right direction.
50D is an awesome camera glad your using it now. First of all that card you using (133X) is way too slow to handle Continuous Raw Recording. Get yourself a Komputerbay 64GB card that, that card is a goto card for Raw recording from the 50D all the way up to the 5D Mark III. About your power button, or switch not turning off the camera I think that's a hardware problem, not software you should probably take it to a camera shop to get it looked at. Here is a simple test does it turn off when your not running Magic Lantern?
Quote from: goldenchild9to5 on July 15, 2013, 05:44:41 PM
50D is an awesome camera glad your using it now. First of all that card you using (133X) is way too slow to handle Continuous Raw Recording. Get yourself a Komputerbay 64GB card that, that card is a goto card for Raw recording from the 50D all the way up to the 5D Mark III. About your power button, or switch not turning off the camera I think that's a hardware problem, not software you should probably take it to a camera shop to get it looked at. Here is a simple test does it turn off when your not running Magic Lantern?
Thanks for the reply, the card is just what came with the camera till i get my Komputerbay card. But what's with the speed I reported, is my math wrong & where?
Quote from: AnotherTim on July 15, 2013, 04:32:27 PM
I finally got little bit of time to try out my 50d (just to make sure I hadn't bought a dud). I'm trying to work out what data rate I shot. My .RAW file is 215.2 MB and i shot 87 frames what is the data rate? My math puts that at 74MB/s but I shot it on a 133x card that came with the camera, am I missing something? I'm using 11th July unified.
It depends on your frame rate. For 30 fps it's 74 MB/s, for 24 fps it's 59 MB/s I think. But, the camera has internal memory and can handle some frames before writing them on the card. So you can have some seconds of high resolution video even on a slow card. If your card was fast enough, the video recording would be continuous.
Quote from: akumiszcza on July 15, 2013, 08:24:54 PM
It depends on your frame rate. For 30 fps it's 74 MB/s, for 24 fps it's 59 MB/s I think. But, the camera has internal memory and can handle some frames before writing them on the card. So you can have some seconds of high resolution video even on a slow card. If your card was fast enough, the video recording would be continuous.
Aha! that's the answer. It was 30fps & 74MB/s is what I got. Can't wait to shoot for real & get active on the forum. I've been lurking since about page 5!
@GoldenChild9to5
The buttons along the bottom don't work at all, from before ML, but ML & Raw works, that'll do for playing, if things get serious I'll get another one/repair.
Thanks, Akumiszcza & GoldenChild
also: ML team is AWESOME!
In which framerate records the 50d in raw video? 24fps? And is it adjustable? I'm using the 9june build
Hey people,
I was shooting today a test shoot with my 50D for a commercial. I'm pretty amazed with images and this is a good start.
But once I overlooked the size of a clip and it got split into 2 parts.
I remember that some 20-30 pages back someone was explaining how to stitch them with some hex editor.... If anyone can help to find that spot, I'll be gratefull. Search on the forum didn't help (
Thanks!
Quote from: rommex on July 15, 2013, 10:04:22 PM
[...]
But once I overlooked the size of a clip and it got split into 2 parts.
I remember that some 20-30 pages back someone was explaining how to stitch them with some hex editor.... If anyone can help to find that spot, I'll be gratefull. Search on the forum didn't help (
http://www.magiclantern.fm/forum/index.php?topic=5654.msg39968#msg39968 et al.
Lads, today I tried shooting with 100mm L lens and the IS is not working. Any ideas?
mjstudio, it's a known issue. Raw recording is done while Live View is idle (at least on the canon firmware side). When it's not taking a picture or a video, IS is off to preserve battery life.
I guess they'll fix it in the future.
Quote from: akumiszcza on July 15, 2013, 11:08:34 PM
http://www.magiclantern.fm/forum/index.php?topic=5654.msg39968#msg39968 et al.
akumiszcza, my heartiest THANKS! much easier than I thought of.....
Quote from: johansugarev on July 16, 2013, 12:29:25 AM
mjstudio, it's a known issue. Raw recording is done while Live View is idle (at least on the canon firmware side).
You're right, but at the same time it works well on 5dmkII
Quote from: johansugarev on July 16, 2013, 12:29:25 AM
I guess they'll fix it in the future.
Fingers crossed!
I'm about to give up shooting raw with my 50d :(
All I get are pink corrupted frames. ALL of them. It's really frustrating.
An example:
http://www.sendspace.com/file/vv7xtg
My setup:
Canon 50D with 10-22mm lenses
Sandisk Extreme 16GB 60mb/s and Transcend 16GB 1000x UDMA
Magic Lantern 2.35 stable build
magiclantern-2013Jul11.50D.109.go.unified.5db91070a1aa for RAW video
All settings reset to default, no HTP, GD off
I'm using the workflow by cantsin
(source: http://www.eoshd.com/comments/topic/3059-canon-50d-magic-lantern-raw-review/)
"Format your CF card in the camera, take it out and put it into the card reader of your computer
Download the current stable, unified 2.3.5 MagicLantern release from http://www.magiclantern.fm/download
Download the most current development snapshot for 50D raw video recording either from https://bitbucket.or...tern/downloads/ (Gregory's 50D Magic Lantern tree) or from https://bitbucket.or...tl50d/downloads (1%'s TragicLantern tree)
Create a folder for the Magic Lantern files on your computer
Unzip the downloaded archive of the stable Magic Lantern release into that folder - and trash the file "autoexec.bin" + the folder "ML"
Unzip the 50D development snapshot into that same folder - after which "autoexec.bin" and the "ML" should be visible again.
In this folder, you should now see a number of files ending with ".fir", the manuals "INSTALL.pdf" and "Userguide.PDF", "autoexec.bin" and the folder "ML".
Copy "autoexec.bin", "ML" and "50D-109.fir" onto your CF card (that still rests in the card reader of your computer).
Cleanly unmount/eject the CF card via the software menu of your operating system and put it into your camera.
Make sure that you have a fully charged, preferably original Canon battery inside your camera.
Switch on the camera. Press the "Menu" button (on the upper left), go to the third (olive-colored) menu with the tool icon, go to the "Firmware" entry, press the button and run the Firmware update.
Wait for all installation messages till you get the message that it is safe to switch off the camera. Switch off the camera.
Switch it on again, wait a few seconds, and press the trashcan button on the lower left to enter the MagicLantern menu.
With the joystick, navigate into the menu with the video camera. Scroll down and adjust the entries with the big scroll wheel.
Activate the entry "REC key: HalfShutter".
Scroll down to the very bottom to the submenu "RAW video". Activate this option. Then press the "Func" button on the lower left to enter its option menu.
Start with conservative settings/low video resolutions (like 640x480) first. Activate the entry "Small Hacks".
Press the trashcan button to leave the Magic Lantern menu.
Press the Live View button on the upper left (next to "Menu") to enter LiveView. If this does not work, activate LiveView in the normal configuration menu of the camera (in the second olive tool menu).
If Live View is working, adjust shutter speed and aperture (if you are using a modern Canon lens) by pressing the trashcan button and going in the first submenu of Magic Lantern. Press the trashcan icon once you are done.
In Live View, half depress the normal camera release. You now see an indication that raw video is being recorded. Stop by pressing the release again.
When you are done, switch off the camera, copy the files ending with ".raw" from the DCIM folder of the CF card to your computer, use a program like RawMagic for Mac OS X (http://www.magiclant...hp?topic=6218.0) or ... (don't what is the recommended Windows solution at the moment, so I better leave this blank) to transform the files into Cinema DNG sequences, then grade/transform with your favorite raw conversion/grading tool (AE, Lightroom, Resolve...). "
Can anyone help me plz?
Quote from: johansugarev on July 16, 2013, 12:29:25 AM
mjstudio, it's a known issue. Raw recording is done while Live View is idle (at least on the canon firmware side). When it's not taking a picture or a video, IS is off to preserve battery life.
I guess they'll fix it in the future.
I was recording raw video with IS working on my 17-55/2.8 at least (I think I didn't check other lenses). All I had to do was keeping shutter half-pressed during recording.
Quote from: dogmydog on July 16, 2013, 06:33:04 AM
I'm about to give up shooting raw with my 50d :(
All I get are pink corrupted frames. ALL of them. It's really frustrating.
[spoiler]
An example:
http://www.sendspace.com/file/vv7xtg
My setup:
Canon 50D with 10-22mm lenses
Sandisk Extreme 16GB 60mb/s and Transcend 16GB 1000x UDMA
Magic Lantern 2.35 stable build
magiclantern-2013Jul11.50D.109.go.unified.5db91070a1aa for RAW video
All settings reset to default, no HTP, GD off
I'm using the workflow by cantsin
(source: http://www.eoshd.com/comments/topic/3059-canon-50d-magic-lantern-raw-review/)
"Format your CF card in the camera, take it out and put it into the card reader of your computer
Download the current stable, unified 2.3.5 MagicLantern release from http://www.magiclantern.fm/download
Download the most current development snapshot for 50D raw video recording either from https://bitbucket.or...tern/downloads/ (Gregory's 50D Magic Lantern tree) or from https://bitbucket.or...tl50d/downloads (1%'s TragicLantern tree)
Create a folder for the Magic Lantern files on your computer
Unzip the downloaded archive of the stable Magic Lantern release into that folder - and trash the file "autoexec.bin" + the folder "ML"
Unzip the 50D development snapshot into that same folder - after which "autoexec.bin" and the "ML" should be visible again.
In this folder, you should now see a number of files ending with ".fir", the manuals "INSTALL.pdf" and "Userguide.PDF", "autoexec.bin" and the folder "ML".
Copy "autoexec.bin", "ML" and "50D-109.fir" onto your CF card (that still rests in the card reader of your computer).
Cleanly unmount/eject the CF card via the software menu of your operating system and put it into your camera.
Make sure that you have a fully charged, preferably original Canon battery inside your camera.
Switch on the camera. Press the "Menu" button (on the upper left), go to the third (olive-colored) menu with the tool icon, go to the "Firmware" entry, press the button and run the Firmware update.
Wait for all installation messages till you get the message that it is safe to switch off the camera. Switch off the camera.
Switch it on again, wait a few seconds, and press the trashcan button on the lower left to enter the MagicLantern menu.
With the joystick, navigate into the menu with the video camera. Scroll down and adjust the entries with the big scroll wheel.
Activate the entry "REC key: HalfShutter".
Scroll down to the very bottom to the submenu "RAW video". Activate this option. Then press the "Func" button on the lower left to enter its option menu.
Start with conservative settings/low video resolutions (like 640x480) first. Activate the entry "Small Hacks".
Press the trashcan button to leave the Magic Lantern menu.
Press the Live View button on the upper left (next to "Menu") to enter LiveView. If this does not work, activate LiveView in the normal configuration menu of the camera (in the second olive tool menu).
If Live View is working, adjust shutter speed and aperture (if you are using a modern Canon lens) by pressing the trashcan button and going in the first submenu of Magic Lantern. Press the trashcan icon once you are done.
In Live View, half depress the normal camera release. You now see an indication that raw video is being recorded. Stop by pressing the release again.
When you are done, switch off the camera, copy the files ending with ".raw" from the DCIM folder of the CF card to your computer, use a program like RawMagic for Mac OS X (http://www.magiclant...hp?topic=6218.0) or ... (don't what is the recommended Windows solution at the moment, so I better leave this blank) to transform the files into Cinema DNG sequences, then grade/transform with your favorite raw conversion/grading tool (AE, Lightroom, Resolve...). "
[/spoiler]
Can anyone help me plz?
Did you get this from EOSHD forums? Read my comment under Cantsin's reply.
What card are you using? Slower cards tend to corrupt data.
Try deleting your config file (magic.cfg) and try again. If you're still getting the problem try another build.
I'm nearly finished writing a proper guide for the 50d ;)
I too am getting IS to work when half-pressing the shutter button during recording... Wonder if it can be implemented without pressing shutter?
Quote from: akumiszcza on July 16, 2013, 07:37:50 AM
I was recording raw video with IS working on my 17-55/2.8 at least (I think I didn't check other lenses). All I had to do was keeping shutter half-pressed during recording.
akumiszcza you're the man! Thank you so much!
Quote from: LEVISDAVIS on July 16, 2013, 11:00:31 AM
I too am getting IS to work when half-pressing the shutter button during recording... Wonder if it can be implemented without pressing shutter?
There is an option for that in ML menu, but it doesn't work. So it's probably not implemented on 50D yet.
Quote from: dogmydog on July 16, 2013, 06:33:04 AM
I'm about to give up shooting raw with my 50d :(
All I get are pink corrupted frames. ALL of them. It's really frustrating.
An example:
http://www.sendspace.com/file/vv7xtg
I'm having good luck with the 50D -- let me mention a few places where my workflow differs from your list:
-I install the unified ML build on the camera (firmware update step) before bringing the RAW devt build into the picture.
You say you replace the unified build ML folder with one from a development build, then do the whole ML install. I have seen situations where it was necessary to simply add the devt ML/MODULES folder, keeping other content that had been in the original ML.
- I set the FPS override to 24 (you don't mention that)
- I set the Exp Override ON
Not sure if there's any help there, but I'm mentioning those for completeness as you consider potential causes.
hi!
back again. found some time to test 50Ds low light capabilities. see video description for details.
i´m also refining my post workflow (see: http://www.magiclantern.fm/forum/index.php?topic=6683.msg53727#msg53727 (http://www.magiclantern.fm/forum/index.php?topic=6683.msg53727#msg53727) )
for your moiré needs with ACR see: http://www.magiclantern.fm/forum/index.php?topic=6242.msg54704#msg54704 (http://www.magiclantern.fm/forum/index.php?topic=6242.msg54704#msg54704)
i also tested rawtherapee a few weeks ago. the different debayering methods are amazing. the tone mapping function is also very interesting.
but it is very slooooow and crashes from time to time.
rawtherapee+gpu raw encoding would be great.... and they´re working on it!
Quote from: Andy600 on July 16, 2013, 09:47:51 AM
Did you get this from EOSHD forums? Read my comment under Cantsin's reply.
What card are you using? Slower cards tend to corrupt data.
Try deleting your config file (magic.cfg) and try again. If you're still getting the problem try another build.
I'm nearly finished writing a proper guide for the 50d ;)
Ty for the help, Andy!
I'm using the Sandisk 16 GB 60mb/s and Transcend 16GB 1000x.
I formated both cards several times and got similar results, specially with videos over 1 or 2min.
I also tried the Tragic Lantern, with no luck either.
Looking foward to read ur guide :)
Quote from: dhallowell19 on July 16, 2013, 12:05:32 PM
I'm having good luck with the 50D -- let me mention a few places where my workflow differs from your list:
-I install the unified ML build on the camera (firmware update step) before bringing the RAW devt build into the picture.
You say you replace the unified build ML folder with one from a development build, then do the whole ML install. I have seen situations where it was necessary to simply add the devt ML/MODULES folder, keeping other content that had been in the original ML.
- I set the FPS override to 24 (you don't mention that)
- I set the Exp Override ON
Not sure if there's any help there, but I'm mentioning those for completeness as you consider potential causes.
Thx for the help, dhallowell19!
- What i do is copying the whole ML 2.35 stable build into the card (after formating in the camera) and then overwriting the content with the development build (autoexec bin and modules folder). I don't understand what you mean by doing the whole ML install. Can you try to explain it again plz? Sorry for the trouble :(
- I set the FPS override to 23.976 (maybe thats the issue?). I'll try 24 :D
- When I turn on Small Hacks, it kills the Exposure Sim (I see the item ticked on my screen). Can I turn it off on another setting?
Quote from: dogmydog on July 16, 2013, 02:43:13 PM
Ty for the help, Andy!
I'm using the Sandisk 16 GB 60mb/s and Transcend 16GB 1000x.
I formated both cards several times and got similar results, specially with videos over 1 or 2min.
I also tried the Tragic Lantern, with no luck either.
Looking foward to read ur guide :)
Do you get the same issues when recording lower resolutions? or when recording shots under 4gb?
I just don't get these problems TBH. You could try my latest build of Tragic Lantern https://bitbucket.org/andy600/tl50d/downloads if you haven't already.
Quote from: Andy600 on July 16, 2013, 02:54:19 PM
Do you get the same issues when recording lower resolutions? or when recording shots under 4gb?
I just don't get these problems TBH. You could try my latest build of Tragic Lantern https://bitbucket.org/andy600/tl50d/downloads if you haven't already.
At shots under 4gb, it all works fine. But that doesn't help me since i need to record stuff at least two minutes long.
If your build doesn't work, I'll try at resolutions under 1584x960.
Quote from: dogmydog on July 16, 2013, 02:49:59 PM
Thx for the help, dhallowell19!
- What i do is copying the whole ML 2.35 stable build into the card (after formating in the camera) and then overwriting the content with the development build (autoexec bin and modules folder). I don't understand what you mean by doing the whole ML install. Can you try to explain it again plz? Sorry for the trouble :(
- I set the FPS override to 23.976 (maybe thats the issue?). I'll try 24 :D
- When I turn on Small Hacks, it kills the Exposure Sim (I see the item ticked on my screen). Can I turn it off on another setting?
Try a fresh install like Andy600 had mentioned, not sure why your having such difficulties running the Hacks.. Unless your cards are faulty, or corrupted somehow. You know what try this it works like a charm..
1) Format your card first as ExFat (I know you probably saying why it worked for me in the beginning)
2) Reformat it in your camera
3) Download and install this build https://soshareit.com/5HaST9Ok7g (https://soshareit.com/5HaST9Ok7g) (Make sure you copy everything from this folder and don't change nothing as is)
4) Run Magic lantern install after you get that green writing and ok to restart your camera restart.
5) Run modules / Exposure Override On / FPS Override 23.976 / Try turning Global Draw on with everything off for now
That's it.. it should work with no problems. If it's' still acting up than it's definitely your CF cards. Hope that helps
GOD Bless
Quote from: dogmydog on July 16, 2013, 04:53:54 PM
At shots under 4gb, it all works fine. But that doesn't help me since i need to record stuff at least two minutes long.
If your build doesn't work, I'll try at resolutions under 1584x960.
Ok, this is significant as it points to file spanning being an issue (for you). What app are you using to convert the raw files?
I think the Batchelor and raw2cdng apps have file spanning support (split raws), not sure what else can do it.
Quote from: Andy600 on July 16, 2013, 06:47:37 PM
Ok, this is significant as it points to file spanning being an issue (for you). What app are you using to convert the raw files?
I think the Batchelor and raw2cdng apps have file spanning support (split raws), not sure what else can do it.
Andy RawMagic Beta 7b Spans raw files
Thank you all very much for the support!
Ok, here it goes.
My setup:
Canon 50D
Canon EFS 10-22mm
Sandisk 16GB 60mb/s
RAW 1584x896
FPS 23.976
Windows 7 x64
First I made the test by goldenchild9to5 (magiclantern-2013Jul11), and everything worked out correctly, no pink corrupt frames.
GD ON with everyting off, Exposure Override On
However, I couldnt exceed 4GB because dropped frames would stop recording. I couldn't get continuos recording, even at 1474.
Then, I used Andy's build (Tragic.Lantern.Andy600build.Jul15.50D109) and I could record continuosly up to full card. However, all I got was pink corrupt frames, such as the one I uploaded. The funny fact is that when I stopped the video before the 4GB (I also recorded a 15sec video to test it), no pink frames, everything perfect.
I'm using RAW Batchelor Beta 2.3. Maybe its a spanned files problem?
It's nice weather here in the UK at the moment so I went and shot another raw test.
- Used Tragic Lantern by 1% (11th July build compiled by Andy600)
- Mostly shot at 1584x892 and upscaled to 1080
- 1 or 2 shots in 5x crop mode
- DNG's extracted with RAWMagic 1.0 Beta 7
- Raw processing in ACR
- Tamron 17-50mm f2.8
I'm getting more accustomed to the workflow now. I did a light 'logish' grade in ACR rendered out to Prores 444. Then applied a custom LUT in Resolve, tweaked it and added a little sharpening.
Quote from: dogmydog on July 16, 2013, 07:31:14 PM
[spoiler]Thank you all very much for the support!
Ok, here it goes.
My setup:
Canon 50D
Canon EFS 10-22mm
Sandisk 16GB 60mb/s
RAW 1584x896
FPS 23.976
Windows 7 x64
First I made the test by goldenchild9to5 (magiclantern-2013Jul11), and everything worked out correctly, no pink corrupt frames.
GD ON with everyting off, Exposure Override On
However, I couldnt exceed 4GB because dropped frames would stop recording. I couldn't get continuos recording, even at 1474.
Then, I used Andy's build (Tragic.Lantern.Andy600build.Jul15.50D109) and I could record continuosly up to full card. However, all I got was pink corrupt frames, such as the one I uploaded. The funny fact is that when I stopped the video before the 4GB (I also recorded a 15sec video to test it), no pink frames, everything perfect.[/spoiler]
I'm using RAW Batchelor Beta 2.3. Maybe its a spanned files problem?
I'll try to recreate the issue and see if I can spot what the problem is. I guess if you are using Batchelor etc you must be on a PC so RawMagic won't work.
@1% do you know if file spanning is ok with TL2.0?
Quote from: dogmydog on July 16, 2013, 07:31:14 PM
Thank you all very much for the support!
Ok, here it goes.
My setup:
Canon 50D
Canon EFS 10-22mm
Sandisk 16GB 60mb/s
RAW 1584x896
FPS 23.976
Windows 7 x64
First I made the test by goldenchild9to5 (magiclantern-2013Jul11), and everything worked out correctly, no pink corrupt frames.
GD ON with everyting off, Exposure Override On
However, I couldnt exceed 4GB because dropped frames would stop recording. I couldn't get continuos recording, even at 1474.
Then, I used Andy's build (Tragic.Lantern.Andy600build.Jul15.50D109) and I could record continuosly up to full card. However, all I got was pink corrupt frames, such as the one I uploaded. The funny fact is that when I stopped the video before the 4GB (I also recorded a 15sec video to test it), no pink frames, everything perfect.
I'm using RAW Batchelor Beta 2.3. Maybe its a spanned files problem?
Great to hear that you got to work.. try one more thing. From the canon menu put your picture quality on (JPEG Large) and not (RAW) it shouldn't make that much difference but still try it out and report back. It might be a spanned files problem.
Still working on the 50D/raw video (including Tragic Lantern 2.0) guide. Up to 5k words+ and trying to cover everything I can think of but there will be a 'quick setup' section. If anyone has any specific 'user' questions about raw video on the 50D just PM them to me. I think I'll have answered most things in the guide but there may be things I've overlooked.
Quote from: rockfallfilms on July 16, 2013, 07:39:04 PM
It's nice weather here in the UK at the moment so I went and shot another raw test.
- Used Tragic Lantern by 1% (11th July build compiled by Andy600)
- Mostly shot at 1584x892 and upscaled to 1080
- 1 or 2 shots in 5x crop mode
- DNG's extracted with RAWMagic 1.0 Beta 7
- Raw processing in ACR
- Tamron 17-50mm f2.8
I'm getting more accustomed to the workflow now. I did a light 'logish' grade in ACR rendered out to Prores 444. Then applied a custom LUT in Resolve, tweaked it and added a little sharpening.
Great job.. like that logish look a lot, keep posting more test beautiful.
Quote from: Andy600 on July 16, 2013, 07:48:46 PM
Still working on the 50D/raw video (including Tragic Lantern 2.0) guide. Up to 5k words+ and trying to cover everything I can think of but there will be a 'quick setup' section. If anyone has any specific 'user' questions about raw video on the 50D just PM them to me. I think I'll have answered most things in the guide but there may be things I've overlooked.
We needed something like that for all Beginners, thanks for taking the initiative for doing so. All I'm going to say is Team 50D is the best 8)
Quote from: goldenchild9to5 on July 16, 2013, 07:55:20 PM
We needed something like that for all Beginners, thanks for taking the initiative for doing so. All I'm going to say is Team 50D is the best 8)
I'll send you a draft when it's ready. Gotta add some pretty pics and formatting in InDesign so it's an interactive PDF (hopefully). I keep thinking of new things to add so it's taking ages ;D
Quote from: Andy600 on July 16, 2013, 07:42:45 PM
I'll try to recreate the issue and see if I can spot what the problem is. I guess if you are using Batchelor etc you must be on a PC so RawMagic won't work.
@1% do you know if file spanning is ok with TL2.0?
Ok, I repeated the same test with my Transcend 16GB 1000x and it looks like the problem is when I extract with Batchelor the spanned files.
I rename the 1234.RAW and 1234.R01, 1234.R02 etc to 1.RAW, 2.RAW, 3.RAW, then use Batchelor to export to DNG. The result is always pink corrupt files, either on Tragic.Lantern.Andy600build.Jul15.50D109 or magiclantern-2013Jul11.
I will try on RAWmagic on a MAC mini that I have, to see what happens.
Then Ill try to upload results here.
EDIT: golden, I forgot to mention that I've been using JPEG large quality and no RAW on camera setup since the 1st try :)
Quote from: goldenchild9to5 on July 16, 2013, 07:43:23 PM
Great to hear that you got to work.. try one more thing. From the canon menu put your picture quality on (JPEG Large) and not (RAW) it shouldn't make that much difference but still try it out and report back. It might be a spanned files problem.
Quote from: Andy600 on July 16, 2013, 06:47:37 PM
Ok, this is significant as it points to file spanning being an issue (for you). What app are you using to convert the raw files?
I think the Batchelor and raw2cdng apps have file spanning support (split raws), not sure what else can do it.
Guys, thank you so much for all the help!
I used rawmagic on my MAC MINI, and guess what? No pink corrupt frames :D
http://www.sendspace.com/file/09w44k
Im going to seek help on the RAWBatchelor topic and see what they can do for me.
If there is anyting i can add to this discussion, Tragic.Lantern.Andy600build.Jul15.50D109 is way better than magiclantern-2013Jul11, since it can write 1592x892 on my SanDisk 16GB 60mb/s CONTINUOUSLY while the other cannot :)
Ty all so much. Team 50D rocks!!!
EDIT: Funny fact... DNG thumbnails on my mac look magenta tinted. Files are ok thought
Quote from: Andy600 on July 16, 2013, 08:02:27 PM
I'll send you a draft when it's ready. Gotta add some pretty pics and formatting in InDesign so it's an interactive PDF (hopefully). I keep thinking of new things to add so it's taking ages ;D
Don't take to long now because there are plenty of hungry 50D owners out there waiting to devourer this guide ;D 50D is looking too good to pass-up right now.
Quote from: dogmydog on July 16, 2013, 08:48:10 PM
Guys, thank you so much for all the help!
I used rawmagic on my MAC MINI, and guess what? No pink corrupt frames :D
http://www.sendspace.com/file/09w44k
Im going to seek help on the RAWBatchelor topic and see what they can do for me.
If there is anyting i can add to this discussion, Tragic.Lantern.Andy600build.Jul15.50D109 is way better than magiclantern-2013Jul11, since it can write 1592x892 on my SanDisk 16GB 60mb/s CONTINUOUSLY while the other cannot :)
Ty all so much. Team 50D rocks!!!
EDIT: Funny fact... DNG thumbnails on my mac look magenta tinted. Files are ok thought
Great!!! glad that it all worked out for you. Thanks for letting me know about your findings now i'm gonna have to give the Tragic another spin.
hi andy!
i think your guide will be awesome.
if you need any help with it or want some more eyes to take a look at it, i would be glad to do so.
i´m in the tv, film and commercial business since 12 years and the last 5 years i worked as a technical director, trained hundreds of people and wrote many manuals and optimized workflow after workflow.
and maybe just somebody wants a german translation..... just tell me ;-)
Quote from: crash-film on July 16, 2013, 09:46:30 PM
hi andy!
i think your guide will be awesome.
if you need any help with it or want some more eyes to take a look at it, i would be glad to do so.
i´m in the tv, film and commercial business since 12 years and the last 5 years i worked as a technical director, trained hundreds of people and wrote many manuals and optimized workflow after workflow.
and maybe just somebody wants a german translation..... just tell me ;-)
Welcome to the forum Crash-Film glad to have you on board. Maybe in the near future you can share some of your findings about the 50D as far as workflows goes.
Quote from: crash-film on July 16, 2013, 09:46:30 PM
hi andy!
i think your guide will be awesome.
if you need any help with it or want some more eyes to take a look at it, i would be glad to do so.
i´m in the tv, film and commercial business since 12 years and the last 5 years i worked as a technical director, trained hundreds of people and wrote many manuals and optimized workflow after workflow.
and maybe just somebody wants a german translation..... just tell me ;-)
Hey thanks :)
I'll certain need eyes on it before releasing it and it will be good to have someone look at it who is used to writing manuals etc so thanks for your offer!
I'll send over a 'text only' review copy when I start making the PDF layout, hopefully tomorrow or the day after. The guide will be FREE to download by anyone BTW :)
Just uploaded the latest 50D Unified build if anyone wants it. (it's Unified code, not Tragic Lantern).
Seems stable here.
https://bitbucket.org/andy600/andy50d/downloads/Magic.Lantern.July162013.50D.109.Andy600.unified.9f843c096fda+.zip
The latest commits are all about Dual ISO for the 5d3 (That is Waaaaaay cool but of course, it won't work on the 50D) but there are also minor code updates that will affect other cameras. This is built with completely fresh code ;)
Quote from: dogmydog on July 16, 2013, 08:06:37 PM
Ok, I repeated the same test with my Transcend 16GB 1000x and it looks like the problem is when I extract with Batchelor the spanned files.
I rename the 1234.RAW and 1234.R01, 1234.R02 etc to 1.RAW, 2.RAW, 3.RAW, then use Batchelor to export to DNG. The result is always pink corrupt files, either on Tragic.Lantern.Andy600build.Jul15.50D109 or magiclantern-2013Jul11.
I will try on RAWmagic on a MAC mini that I have, to see what happens.
Then Ill try to upload results here.
EDIT: golden, I forgot to mention that I've been using JPEG large quality and no RAW on camera setup since the 1st try :)
Try to always merge spanned RAW files first before using a RAW file converter like RawMagic. The reason is that, in a spanned RAW sequence, only the last file in the sequence has the RAW file footer in it's contents. At least as far as I know.
Trying to convert a RAW file without the footer could also cause corruption. But please, let me know if I have missed any developments that render my point mute! :P - developments come so fast I could have missed something.
Quote from: Andy600 on July 16, 2013, 10:58:58 PM
Just uploaded the latest 50D Unified build if anyone wants it. (it's Unified code, not Tragic Lantern).
Seems stable here.
https://bitbucket.org/andy600/andy50d/downloads/Magic.Lantern.July162013.50D.109.Andy600.unified.9f843c096fda+.zip
The latest commits are all about Dual ISO for the 5d3 (That is Waaaaaay cool but of course, it won't work on the 50D) but there are also minor code updates that will affect other cameras. This is built with completely fresh code ;)
Thanks for posting will give it a try later on. 5D3 is getting all the goodies.. but it's awesome what Alex1 has been able to accomplish 14 stops of Dynamic Range that is ALexa territory.
Just wanting to share a video shot with the 50D & Unified ML from July 11th. Encountered some glitches shooting on a 60 MB/s Sandisk card and decided to include some of them in the edit:
https://vimeo.com/70259256
Workflow: RawMagic, Lightroom 5 -> tiff, ffmpeg -> ProRes 444, Premiere CC + FilmConvert.
Quote from: cantsin on July 17, 2013, 01:15:40 AM
Just wanting to share a video shot with the 50D
I have that same glitch with a single frame being darker. Your workflow seems longer than mine though.
RAW > Import with Ginger HDR into AE > Grade > Render out ProRes 4444 to FCP 7.03.
Also, noob question- how do I turn off autoexposure? When I lock ISO, shutter, WB it still gains up and down depending on brightness.
Quote from: djfremen on July 17, 2013, 02:09:51 AM
I have that same glitch with a single frame being darker. Your workflow seems longer than mine though.
RAW > Import with Ginger HDR into AE > Grade > Render out ProRes 4444 to FCP 7.03.
Also, noob question- how do I turn off autoexposure? When I lock ISO, shutter, WB it still gains up and down depending on brightness.
Exposure override.
For some reason, the prores 4444 file put out by raw2dng is unrecognized by my system - OSX 10.8.4
(http://i.imgbox.com/abgLd3AS.png)
Anybody has any idea why? Here's the resultant text:
raw2dng converter GUI for OsX
Beta ver.0.13
M28-1957 File Supported
Generating ProResHQ 4444 with FPS: 23.976
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 @ 0x102019600] Stream #0: not enough frames to estimate rate; consider increasing probesize
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
Input #0, image2pipe, from 'pipe:0':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: ppm, rgb48be, 1920x1080, 23.98 tbr, 23.98 tbn, 23.98 tbc
Output #0, mov, to '/Users/oscarmoreno/Desktop/test/M28-1957.mov':
Metadata:
encoder : Lavf54.63.104
Stream #0:0: Video: prores (apch / 0x68637061), yuv444p10le, 1920x1080, q=2-31, 200 kb/s, 11988 tbn, 23.98 tbc
Stream mapping:
Stream #0:0 -> #0:0 (ppm -> prores_kostya)
frame= 3 fps=2.1 q=0.0 size= 2844kB time=00:00:00.12 bitrate=186177.9kbits/s
frame= 4 fps=1.6 q=0.0 size= 3792kB time=00:00:00.16 bitrate=186204.1kbits/s
frame= 5 fps=1.4 q=0.0 size= 4740kB time=00:00:00.20 bitrate=186198.5kbits/s
frame= 6 fps=1.3 q=0.0 size= 5688kB time=00:00:00.25 bitrate=186211.6kbits/s
frame= 7 fps=1.3 q=0.0 size= 6637kB time=00:00:00.29 bitrate=186225.3kbits/s
frame= 8 fps=1.2 q=0.0 size= 7585kB time=00:00:00.33 bitrate=186231.5kbits/s
frame= 9 fps=1.2 q=0.0 size= 8533kB time=00:00:00.37 bitrate=186225.4kbits/s
frame= 10 fps=1.2 q=0.0 size= 9481kB time=00:00:00.41 bitrate=186221.4kbits/s
frame= 11 fps=1.1 q=0.0 size= 10428kB time=00:00:00.45 bitrate=186206.4kbits/s
frame= 12 fps=1.1 q=0.0 size= 11377kB time=00:00:00.50 bitrate=186209.4kbits/s
frame= 13 fps=1.1 q=0.0 size= 12325kB time=00:00:00.54 bitrate=186211.3kbits/s
frame= 14 fps=1.1 q=0.0 size= 13273kB time=00:00:00.58 bitrate=186209.0kbits/s
frame= 15 fps=1.1 q=0.0 size= 14221kB time=00:00:00.62 bitrate=186216.2kbits/s
frame= 16 fps=1.1 q=0.0 size= 15169kB time=00:00:00.66 bitrate=186212.7kbits/s
frame= 17 fps=1.1 q=0.0 size= 16118kB time=00:00:00.70 bitrate=186218.8kbits/s
frame= 18 fps=1.1 q=0.0 size= 17065kB time=00:00:00.75 bitrate=186210.9kbits/s
frame= 19 fps=1.1 q=0.0 size= 18013kB time=00:00:00.79 bitrate=186204.8kbits/s
frame= 20 fps=1.1 q=0.0 size= 18961kB time=00:00:00.83 bitrate=186203.5kbits/s
frame= 21 fps=1.1 q=0.0 size= 19909kB time=00:00:00.87 bitrate=186204.9kbits/s
frame= 22 fps=1.0 q=0.0 size= 20857kB time=00:00:00.91 bitrate=186204.0kbits/s
frame= 23 fps=1.0 q=0.0 size= 21805kB time=00:00:00.95 bitrate=186202.9kbits/s
frame= 24 fps=1.0 q=0.0 size= 22752kB time=00:00:01.00 bitrate=186202.0kbits/s
frame= 25 fps=1.0 q=0.0 size= 23701kB time=00:00:01.04 bitrate=186206.6kbits/s
frame= 26 fps=1.0 q=0.0 size= 24650kB time=00:00:01.08 bitrate=186209.7kbits/s
frame= 27 fps=1.0 q=0.0 size= 25597kB time=00:00:01.12 bitrate=186208.6kbits/s
frame= 28 fps=1.0 q=0.0 size= 26546kB time=00:00:01.16 bitrate=186211.4kbits/s
frame= 29 fps=1.0 q=0.0 size= 27494kB time=00:00:01.20 bitrate=186211.7kbits/s
frame= 30 fps=1.0 q=0.0 size= 28442kB time=00:00:01.25 bitrate=186208.4kbits/s
frame= 31 fps=1.0 q=0.0 size= 29389kB time=00:00:01.29 bitrate=186205.5kbits/s
frame= 32 fps=1.0 q=0.0 size= 30337kB time=00:00:01.33 bitrate=186203.8kbits/s
frame= 33 fps=1.0 q=0.0 size= 31284kB time=00:00:01.37 bitrate=186198.8kbits/s
frame= 34 fps=1.0 q=0.0 size= 32233kB time=00:00:01.41 bitrate=186201.7kbits/s
frame= 35 fps=1.0 q=0.0 size= 33181kB time=00:00:01.45 bitrate=186202.6kbits/s
frame= 36 fps=1.0 q=0.0 size= 34129kB time=00:00:01.50 bitrate=186203.7kbits/s
frame= 37 fps=1.0 q=0.0 size= 35077kB time=00:00:01.54 bitrate=186202.6kbits/s
frame= 38 fps=1.0 q=0.0 size= 36026kB time=00:00:01.58 bitrate=186206.1kbits/s
frame= 39 fps=1.0 q=0.0 size= 36973kB time=00:00:01.62 bitrate=186205.2kbits/s
frame= 40 fps=1.0 q=0.0 size= 37922kB time=00:00:01.66 bitrate=186205.4kbits/s
frame= 41 fps=1.0 q=0.0 size= 38869kB time=00:00:01.71 bitrate=186203.8kbits/s
frame= 42 fps=1.0 q=0.0 size= 39817kB time=00:00:01.75 bitrate=186205.0kbits/s
frame= 43 fps=1.0 q=0.0 size= 40765kB time=00:00:01.79 bitrate=186204.8kbits/s
frame= 44 fps=1.0 q=0.0 size= 41713kB time=00:00:01.83 bitrate=186201.0kbits/s
frame= 45 fps=1.0 q=0.0 size= 42660kB time=00:00:01.87 bitrate=186196.7kbits/s
frame= 46 fps=1.0 q=0.0 size= 43608kB time=00:00:01.91 bitrate=186196.9kbits/s
frame= 47 fps=1.0 q=0.0 size= 44556kB time=00:00:01.96 bitrate=186196.1kbits/s
frame= 48 fps=1.0 q=0.0 size= 45503kB time=00:00:02.00 bitrate=186195.8kbits/s
frame= 49 fps=1.0 q=0.0 size= 46452kB time=00:00:02.04 bitrate=186197.0kbits/s
frame= 50 fps=1.0 q=0.0 size= 47401kB time=00:00:02.08 bitrate=186200.4kbits/s
frame= 51 fps=1.0 q=0.0 size= 48349kB time=00:00:02.12 bitrate=186202.9kbits/s
frame= 52 fps=1.0 q=0.0 size= 49298kB time=00:00:02.16 bitrate=186206.9kbits/s
frame= 53 fps=1.0 q=0.0 size= 50247kB time=00:00:02.21 bitrate=186210.0kbits/s
frame= 54 fps=1.0 q=0.0 size= 51195kB time=00:00:02.25 bitrate=186209.3kbits/s
frame= 55 fps=1.0 q=0.0 size= 52144kB time=00:00:02.29 bitrate=186211.3kbits/s
frame= 56 fps=1.0 q=0.0 size= 53092kB time=00:00:02.33 bitrate=186213.0kbits/s
frame= 57 fps=1.0 q=0.0 size= 54041kB time=00:00:02.37 bitrate=186213.6kbits/s
frame= 58 fps=1.0 q=0.0 size= 54988kB time=00:00:02.41 bitrate=186213.1kbits/s
frame= 59 fps=1.0 q=0.0 size= 55936kB time=00:00:02.46 bitrate=186211.6kbits/s
frame= 60 fps=1.0 q=0.0 size= 56884kB time=00:00:02.50 bitrate=186212.4kbits/s
frame= 61 fps=1.0 q=0.0 size= 57832kB time=00:00:02.54 bitrate=186209.4kbits/s
frame= 62 fps=1.0 q=0.0 size= 58779kB time=00:00:02.58 bitrate=186209.0kbits/s
frame= 63 fps=1.0 q=0.0 size= 59727kB time=00:00:02.62 bitrate=186208.0kbits/s
frame= 64 fps=1.0 q=0.0 size= 60675kB time=00:00:02.66 bitrate=186208.5kbits/s
frame= 65 fps=1.0 q=0.0 size= 61624kB time=00:00:02.71 bitrate=186208.7kbits/s
frame= 66 fps=1.0 q=0.0 size= 62572kB time=00:00:02.75 bitrate=186208.7kbits/s
frame= 67 fps=1.0 q=0.0 size= 63519kB time=00:00:02.79 bitrate=186206.9kbits/s
frame= 68 fps=1.0 q=0.0 size= 64467kB time=00:00:02.83 bitrate=186207.1kbits/s
frame= 69 fps=1.0 q=0.0 size= 65415kB time=00:00:02.87 bitrate=186206.6kbits/s
frame= 70 fps=1.0 q=0.0 size= 66364kB time=00:00:02.91 bitrate=186209.1kbits/s
frame= 71 fps=1.0 q=0.0 size= 67312kB time=00:00:02.96 bitrate=186209.0kbits/s
frame= 72 fps=1.0 q=0.0 size= 68261kB time=00:00:03.00 bitrate=186210.4kbits/s
frame= 73 fps=1.0 q=0.0 size= 69208kB time=00:00:03.04 bitrate=186209.6kbits/s
frame= 74 fps=1.0 q=0.0 size= 70158kB time=00:00:03.08 bitrate=186213.7kbits/s
frame= 75 fps=1.0 q=0.0 size= 71106kB time=00:00:03.12 bitrate=186213.8kbits/s
frame= 613 fps=1.0 q=0.0 size= 581090kB time=00:00:25.56 bitrate=186187.0kbits/s
/Applications/raw2dng.app/Contents/Resources/script: line 40: 4661 Done "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
4662 Segmentation fault: 11 | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done
I honestly dislike that rawdng outputting a file. Doesn't it output a 422 file and not a 4444 file?
i´m striving through the raw therapee forum.
they have really good attempts on integrating some kind of video (aimed at timelapse purposes) functionality.
really good ideas on gpu acceleration, open exr integration (oexr is a rock solid, free image format....whereas tiff is just a container format and can be everything, making it somewhat dangerous to work with) , debayering methods.... and so on.
what i understand in that forum, they really need people to code. just raw man power.
for me the raw recording function and dng extraction works stable and i would use it as a real world production workflow.
now that the first step is done, it would be a really great opportunity to keep magic lantern raw recording really open source and independent.
depending on black magic and hoping they implement and support the #1 pocket cinema killer..... well, it works somehow. but depending on the good will of a profit oriented firm could be the wrong idea.
the adobe way is not free and nobody knows what will happen next in the adobe cloud.
developing a true ML own workflow would be perfect. inventing the wheel from scratch, while there´s a great free tool.... it just feels wrong ;)
but a cooperation with the raw therapee folks could be the best short cut to a true open source consistent and big name independent raw system.
because: raw means your image is finally created in post
Quote from: menoc on July 16, 2013, 11:15:22 PM
Try to always merge spanned RAW files first before using a RAW file converter like RawMagic. The reason is that, in a spanned RAW sequence, only the last file in the sequence has the RAW file footer in it's contents. At least as far as I know.
Trying to convert a RAW file without the footer could also cause corruption. But please, let me know if I have missed any developments that render my point mute! :P - developments come so fast I could have missed something.
I sure will. Thanks menoc!
I updated my raw2dng.exe and now I'm joining files with FSJ (recommended on Begginers guide) and no more issues with pink corrupted frames :)
Hello all 50D folks,
So far so good with my new 32 gig card as opposed to my first 128gig, from a week back ,but a couple of questions. When I opened up one of the dng files in photoshop it seems to indicate that i have an 8bit file. The other issue on the July 11th build is that I'm not having any luck on the 5X and 10X magnification recording, I seem to get a monochrome LV screen during REC. With all these things still very happy.
Thanks again all
Quote from: JBTML on July 17, 2013, 09:03:41 PM
Hello all 50D folks,
So far so good with my new 32 gig card as opposed to my first 128gig, from a week back ,but a couple of questions. When I opened up one of the dng files in photoshop it seems to indicate that i have an 8bit file. The other issue on the July 11th build is that I'm not having any luck on the 5X and 10X magnification recording, I seem to get a monochrome LV screen during REC. With all these things still very happy.
Thanks again all
If it's a DNG converted from a raw file it's 14bit (or 10, 12 or 16bit Cinema DNG if converted with raw2cdng) so Photoshop is lying to you ;)
Grayscale preview in crop mode is normal. I haven't tried with that build but try changing your preview mode to Canon. It's probably set to auto, grayscale or hacked.
Hi, I`m new here. I`ve read a few entries here but I`m still not sure if the Eos 50D is able to record RAW video continuasly ( without dropframes ) at 1080x1920 - 24/25 fps with a 1000x CF Card UDMA 7 100MB/second write speed or even greater (I`ve seen one with a speed of 150MB/s).
Does somebody tested it this way ? What`s about heating issues at the sensor or the cpu? Is it possible to record a few minutes not croped HD RAW video ?
Do the 50D will have any other Codec options than RAW for video recording after the ML update ? Or is it maybe a better idea to buy something like a 600D which nativly is able to record vodeo including buttons...
But the problem is that I don`t want to have the hard H264 compression on the video. Does ML supports any other video codec solutions than cropped RAW for all these EOS which haven`t an CF Card slot? for example h264 with a much higher Mbit/s rate or even somethin like
4:2:2 DNxHD or ProRes ( if the copyrights allow those things )?
Thanks for answering
and thanks for ML – I`m realy excited since I`ve found this homepage!!!
Thanks to the awesome help of you all, I present my results on vimeo.
Dude... RAW is amazing.
Quote from: Mak44 on July 17, 2013, 10:12:13 PM
Hi, I`m new here. I`ve read a few entries here but I`m still not sure if the Eos 50D is able to record RAW video continuasly ( without dropframes ) at 1080x1920 - 24/25 fps with a 1000x CF Card UDMA 7 100MB/second write speed or even greater (I`ve seen one with a speed of 150MB/s).
Does somebody tested it this way ? What`s about heating issues at the sensor or the cpu? Is it possible to record a few minutes not croped HD RAW video ?
Do the 50D will have any other Codec options than RAW for video recording after the ML update ? Or is it maybe a better idea to buy something like a 600D which nativly is able to record vodeo including buttons...
But the problem is that I don`t want to have the hard H264 compression on the video. Does ML supports any other video codec solutions than cropped RAW for all these EOS which haven`t an CF Card slot? for example h264 with a much higher Mbit/s rate or even somethin like
4:2:2 DNxHD or ProRes ( if the copyrights allow those things )?
Thanks for answering
and thanks for ML – I`m realy excited since I`ve found this homepage!!!
You can forget about codecs, at lest in the near future. With ML the 50D shoots 1080p at 30fps and 640x480 at 30fps, you can sort of change the fps with fps override.
For RAW, a 1000x cf card is a must, and you can shoot in full 1080p HD in cropped mode and in full sensor at 1584x1058 both in 24fps. The max write speed achieved at this time is 81MB/s.
If you want a canon camera for raw, you should buy nothing but the 5Dmk2/3 or the 50D.
Hi everyone, thanks for all your help in getting me up and running. Check out the results from my low light test below.
All the clips were taken from the same 7 minute video and adjusted seperately in post.
Quote from: dogmydog on July 17, 2013, 11:41:56 PM
Thanks to the awesome help of you all, I present my results on vimeo.
Dude... RAW is amazing.
Great job on your first video dogmydog.. the only thing that I can see is there seems to be something odd with the cadence, or motion. I believe that your timeline was set to 30fps instead of 24fps.
Quote from: Supermac on July 18, 2013, 03:47:30 AM
Hi everyone, thanks for all your help in getting me up and running. Check out the results from my low light test below.
All the clips were taken from the same 7 minute video and adjusted seperately in post.
Great video Supermac.. very little noise present.
Hey folks! Tested the 2K RAW in 5X mode and I'm getting over 5,000 frames of recording time with my Komputer Bay CF card.
Does anyone have a tutorial or have some knowledge about how to confidently frame your shot using 5X mode? I'm having trouble knowing exactly what I'm shooting and I don't like flying blind.
Quote from: D.L. Watson on July 18, 2013, 07:53:31 AM
Hey folks! Tested the 2K RAW in 5X mode and I'm getting over 5,000 frames
What specific resolution did you get and what MB/s?
My KomputerBay at 1050x 128GB is coming Monday. Can't wait to see if I can break the 81 MB/s speed barrier.
The latest 50D Magic Lantern and Tragic Lantern 2.0 builds are up:-
Magic Lantern Unified - https://bitbucket.org/andy600/andy50d/downloads
Tragic Lantern 2.0 - https://bitbucket.org/andy600/tl50d/downloads
Extensive guide hopefully coming this weekend if I can find the time to finish it.
]Here is some footage shot with 12,800 ISO
http://www.youtube.com/watch?v=wfI-UWyHQuw
used ACW to take out the noise
The ADTG shutters should give you a bigger range than 1/110 now.
Quote from: D.L. Watson on July 18, 2013, 07:53:31 AM
Hey folks! Tested the 2K RAW in 5X mode and I'm getting over 5,000 frames of recording time with my Komputer Bay CF card.
Does anyone have a tutorial or have some knowledge about how to confidently frame your shot using 5X mode? I'm having trouble knowing exactly what I'm shooting and I don't like flying blind.
Looks really good great job What exact build did you use? What settings did you use? I can only get a few seconds @ 2K Raw
Quote from: 1% on July 18, 2013, 03:21:43 PM
The ADTG shutters should give you a bigger range than 1/110 now.
Great work 1% is it implemented in the new Unified build, or the new Tragic build?
Need some tips about settings. When I record video on my 50D, I just make sure the white balance and exposure is right. I also make sure that my setting is at Manual setting. This means, I'll be adjusting iso, aperture and shutter. However, I don't pay attention to the shutter value but I think it's something I need to be concerned about. When I was looking at each dng files, I noticed some are blurry. I was thinking that maybe my shutter had a small value. Am I right that when I shoot, I should aim for at least 1/80 or more to minimize blurriness? I'm also aware that I should increase iso to suck more light but I'm also aware that image quality will be affected(more noise).
What do you think folks?
@v1rt
shutter speed is mandatory for having a natural look of your images.
what you call "blurry" frames is the motion blur, and is not a problem, it's a requirment if you want the images to be similar to what a human eye would perceive.
so, first rule is that shutter speed has to be costant in your clips.
second rule is that it should be double the frame rate you choose
24 fps -> 1/48
25 fps -> 1/50
30 fps -> 1/60
this rule can be broken if you have extremely fast action scenes, where blurriness would make the picture too confused.
Only in these you can go up at a maximum of double the values explained before.
So, in general, don't try to minimize blur because that's what makes the images look natural!
Quote from: riccardocovino on July 18, 2013, 06:14:17 PM
@v1rt
shutter speed is mandatory for having a natural look of your images.
what you call "blurry" frames is the motion blur, and is not a problem, it's a requirment if you want the images to be similar to what a human eye would perceive.
so, first rule is that shutter speed has to be costant in your clips.
second rule is that it should be double the frame rate you choose
24 fps -> 1/48
25 fps -> 1/50
30 fps -> 1/60
this rule can be broken if you have extremely fast action scenes, where blurriness would make the picture too confused.
Only in these you can go up at a maximum of double the values explained before.
So, in general, don't try to minimize blur because that's what makes the images look natural!
Awesome! I'm going to try this tonight!
Btw, what is the difference between Gregory Of Manhattan Build and Tragic Lantern? What features or improvements is it on each build? Which build do you prefer folks?
Quote from: djfremen on July 18, 2013, 08:45:29 AM
What specific resolution did you get and what MB/s?
My KomputerBay at 1050x 128GB is coming Monday. Can't wait to see if I can break the 81 MB/s speed barrier.
Right now, I'm recording 2000x835 in the 2.39:1 aspect ratio. I'm not sure what my MB/s is - all I know is I can basically record more than what I need. The 32gig goes quick though.
Quote from: goldenchild9to5 on July 18, 2013, 04:42:18 PM
Looks really good great job What exact build did you use? What settings did you use? I can only get a few seconds @ 2K Raw
Using the July 10th Nightly Build. Shutter 1/48th. 24fps. Raw recorded in the 2.39:1 ratio - global draw turned off, with the ML Grayscale for the live-view during recording, and between ISO -100 through 1600. Hacked settings turned on.
Thanks for watching!
Quote from: 1% on July 18, 2013, 03:21:43 PM
The ADTG shutters should give you a bigger range than 1/110 now.
Confirmed :)
Shutter works from (roughly) 60 to 359 degrees now.
I think this should be pushed to Unified.
Really wanting to know how to setup the 50d with the 5x crop mode properly. Is there no possible way to view what is actually being recorded? I need to be able to view correct framing.
Quote from: ultramaze on July 19, 2013, 01:09:37 AM
Really wanting to know how to setup the 50d with the 5x crop mode properly. Is there no possible way to view what is actually being recorded? I need to be able to view correct framing.
You could make marks around the camera screen to show the crop boundries in relation to the fullsensor mode.
Quote from: ultramaze on July 19, 2013, 01:09:37 AM
Really wanting to know how to setup the 50d with the 5x crop mode properly. Is there no possible way to view what is actually being recorded? I need to be able to view correct framing.
No! Hacked preview mode will only let you see a low-res preview of the recordable crop area before recording. It will revert to 5x grayscale when you hit record. No fixes for this yet and don't expect that to change anytime soon.
Just how critical is your framing that you can't use an educated guess as to what the recorded frame will look like? Think of it like a broadcast safe guide overlay in your NLE and you are seeing the safe area. You have to think a bit 'old skool' with the 50D ;)
Thank you for a new build lads!
I need your help again. Every overexposed element gets stripes. Any cure?
(http://s11.postimg.org/xhc6atfk3/DNGM16_1656_000004.jpg)
Quote from: mjstudio on July 19, 2013, 02:55:10 AM
Thank you for a new build lads!
I need your help again. Every overexposed element gets stripes. Any cure?
[spoiler](http://s11.postimg.org/xhc6atfk3/DNGM16_1656_000004.jpg)[/spoiler]
I've not seen that one before ;D
What build?, what are you converting raw files with? and what's your post app?
For a cure, the first thing that comes to mind is don't over expose your shots ;) Are you using the raw histogram?
Quote from: mjstudio on July 19, 2013, 02:55:10 AM
Thank you for a new build lads!
I need your help again. Every overexposed element gets stripes. Any cure?
(http://s11.postimg.org/xhc6atfk3/DNGM16_1656_000004.jpg)
The horses are turning to zebras! Almost looks like your zebras from GD are being put into RAW (not really happening, just what it looks like).
Sorry that's happening, good luck on a cure.
Hey Folks,
So here is a good one, I'm loving the raw but this one I can't quite figure this one out So I shot and exposed for a greyscale chart in both H264 Cinestyle and then a minute later clicked to shoot raw with the same settings:shutter 1/50,5.0, iso 160 cinestyle and here is what I got. The first shot is the H264 and it looks like what I expected. I then shot the identical chart in RAW converted in RawtoDNG and brought a still frame in CS5 s. When I pull up the shot It looks at least 2-3 stops underexposed and as a default the brightness is defaulting to "50" already!!!!. Yes I could crank up exposure but then I start adding noise. This must be something I am messing up. The H264 is pretty close to what I see on the back of the camera and I'm making sure with the histogram i'm not crushing or blowing out. Really strange. I guess I expected a very similar Cine flat raw file. Could it be some thing in the ML setting that is crushing the image?
So This is the July 11th build with a 32gig Komputer card, Global Draw off and that's about it. Creating DNG files with Raw2DNG and then I'm looking at raw dng file in cs5 and this is what I see,
What do you think?
Thanks in advance, loving the possibilities!!!!
Will try to put up stills tomorrow
So Here are the two grabs from the previous post. First is the H264 cine and the 2nd is the first thing I see in Cs5 when I open up a DNG still from the same greyscale shot in raw.
Thanks again
(http://i1291.photobucket.com/albums/b555/JBTWHU14/cineflat_zps8df2636c.jpg) (http://s1291.photobucket.com/user/JBTWHU14/media/cineflat_zps8df2636c.jpg.html)
(http://i1291.photobucket.com/albums/b555/JBTWHU14/rawdialogue_zpsf6c6b558.jpg) (http://s1291.photobucket.com/user/JBTWHU14/media/rawdialogue_zpsf6c6b558.jpg.html)
in Desired FPS, do you pick 23.976 or 24? I'm using the former.
Quote from: Andy600 on July 19, 2013, 02:31:18 AM
No! Hacked preview mode will only let you see a low-res preview of the recordable crop area before recording. It will revert to 5x grayscale when you hit record. No fixes for this yet and don't expect that to change anytime soon.
Just how critical is your framing that you can't use an educated guess as to what the recorded frame will look like? Think of it like a broadcast safe guide overlay in your NLE and you are seeing the safe area. You have to think a bit 'old skool' with the 50D ;)
My framing is very critical lol. I want to be able to see what im recording at all times! :P I guess I will just stick with the standard mode.... need to get a 5d3...
Quote from: mjstudio on July 19, 2013, 02:55:10 AM
Every overexposed element gets stripes.
Can you upload a DNG converted with raw2dng from the horse video, and one second (or less) of a raw test shot (the RAW file) showing the same problem?
In an old post:
Quote from: D.L. Watson on July 13, 2013, 06:31:40 AM
[...]
By the way, I'm using the Komputer Bay 1000x 32gig and I'm experiencing continuous recording in 5X mode, 1080p.
[...]
New post:
Quote from: D.L. Watson on July 18, 2013, 07:08:46 PM
Right now, I'm recording 2000x835 in the 2.39:1 aspect ratio. I'm not sure what my MB/s is - all I know is I can basically record more than what I need. The 32gig goes quick though.
Using the July 10th Nightly Build. Shutter 1/48th. 24fps. Raw recorded in the 2.39:1 ratio - global draw turned off, with the ML Grayscale for the live-view during recording, and between ISO -100 through 1600. Hacked settings turned on.
So, are you really experiencing continuous recording in 1080p? This means 1920x1080 (16:9 aspect ratio). I was really trying all options and can't do that on 32gig 1000x Komputerbay card. About 2000 frames max.
Continuous means the buffer is not increasing during filming, you can see it on the screen. And after a while you see "continuous OK" or similar.
Quote from: JBTML on July 19, 2013, 04:53:19 AM
Could it be some thing in the ML setting that is crushing the image?
Cinestyle is a LOG profile and raw is linear. There will obviously be a difference in how the unprocessed images look.
Are you exposing for raw with the raw histogram enabled? Have you tried auto ETTR?
Quote from: JBTML on July 19, 2013, 05:37:37 AM
So Here are the two grabs from the previous post. First is the H264 cine and the 2nd is the first thing I see in Cs5 when I open up a DNG still from the same greyscale shot in raw.
Thanks again
I have same kind of problem. I can get only darker and almost grey image. I tried to many way like use raw2dng, ACR and Rawmagic, Davinci. But I could not any good result. Image is darker and grey always...
If you can't wait for my free 50D guide Andrew Reid of EOSHD has just released his 50D raw shooters guide for the introductory price of $19.99 (usual price $29.99).
http://www.eoshd.com/the-eoshd-50d-raw-shooters-guide
I haven't bought or read it but it will likely be packed with useful information.
My free guide (coming asap) no doubt covers a lot of the same topics but there will be areas where the guides differ. Andrew Reid is very knowledgeable in his field and will offer a pro's perspective and tips while I approach the 50D from the position of the end user who uses the 50D as their main camera (and on a budget). The free guide also explores the idiosyncrasies of the 50D, the workarounds, the problems and development of Magic Lantern in easy to understand language and all based on my own working experience with the camera. I also cover 1%'s Tragic Lantern 2.0 in detail, explaining the differences between it and the Unified code plus I try to answer a lot of your questions from beginners through to more advanced users.
I'll post the guide online hopefully in the next few days but if you can't wait, check out EOSHD's offering :)
Thanks for putting it all together Andy. Looking forward to reading your guide. I check here most days to keep up to speed but soo much to keep track of. All the info in one package would be a big help.
Thanks again.
Using the right picture profile is tricky... For example, I've been working with some profiles such as Cinestyle and I too get similar results with the H264 exposure vs the raw... The reality of the processed image in LiveView is not the same as the raw footage being recorded to the card. Though I love looking at the Cinestyle picture profile compared to other picture profiles, especially in low-light... I will actually tend to shoot raw in Standard picture. Personally, I tend to dial in the Standard picture profile in a way that provides consistent exposure/noise floor results. Eventually, you'll be able to push the image as far as Cinestyle in post, but you've got to find the right pathway to the sensor and the LiveView.
The histogram doesn't lie... The Auto ETTR will push your shot right to the max without over clipping... You could technically continue to shoot with different picture profiles, but you'll definitely want to be zoned in on the histogram. Essentially, there are some picture profiles that truly boost the image to a great degree in LiveView. But, the data in the card is reading the information directly from the sensor. Keep practicing and stay true to the sensor readouts... They are there for you to push the limits. The LiveView simply serves as a constant unchanging rhythm featuring a dynamic range similar to a poor/standard quality computer monitor & television. Feel free to tune the LiveView to lean towards the results you most keenly require in post such as skin tones, black levels, and/or highlights.
Hang in there and keep up with the posts. Thanks everyone! Thanks ML Team!
For this video, I shot with a slower CF Card (60MBS) that gave me 1152 X 864 resolution at 24 FPS in 4:3 mode without skipping frames. I could shoot for at least 4 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 2304 X 864 in Compressor. Does anyone know what the resolution size limitations are when shooting in 4:3 mode? Do the limitations depend upon the speed of the card? Thank you.
Quote from: Andy600 on July 19, 2013, 11:49:29 AM
If you can't wait for my free 50D guide Andrew Reid of EOSHD has just released his 50D raw shooters guide for the introductory price of $19.99 (usual price $29.99).
http://www.eoshd.com/the-eoshd-50d-raw-shooters-guide
I haven't bought or read it but it will likely be packed with useful information.
My free guide (coming asap) no doubt covers a lot of the same topics but there will be areas where the guides differ. Andrew Reid is very knowledgeable in his field and will offer a pro's perspective and tips while I approach the 50D from the position of the end user who uses the 50D as their main camera (and on a budget). The free guide also explores the idiosyncrasies of the 50D, the workarounds, the problems and development of Magic Lantern in easy to understand language and all based on my own working experience with the camera. I also cover 1%'s Tragic Lantern 2.0 in detail, explaining the differences between it and the Unified code plus I try to answer a lot of your questions from beginners through to more advanced users.
I'll post the guide online hopefully in the next few days but if you can't wait, check out EOSHD's offering :)
This is exactly what I was waiting for.......your guide certainlly will help us a lot Andy.....Thanks for all your hard work!
What am I doing wrong? I am trying low light. My resulting video is noisy that is similar to 3200 iso.
I chose LowLight from the settings, 1280x720, global off, 23.976 fps, manual aperture to f1.4(Asahi Super Takumar 50mm lens). I remember my ISO was around 400-800. I will try it again tonight once I get home.
Forgot to mention, I'm using the latest GregoryofManhattan build.
filmed end of the day with nice sun.
Canon 50D Raw test to check moire in high contrast. You can see moire in the water.
Lens: Kowa 8z anamorphic
Some parts were over exposed, is very hard to see in the display, sorry for that.
Quote from: BT on July 19, 2013, 05:06:06 PM
For this video, I shot with a slower CF Card (60MBS) that gave me 1152 X 864 resolution at 24 FPS in 4:3 mode without skipping frames. I could shoot for at least 4 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 2304 X 864 in Compressor. Does anyone know what the resolution size limitations are when shooting in 4:3 mode? Do the limitations depend upon the speed of the card? Thank you.
Some really nice shots in there sir.
The opening flare was epic.
Is this the Kowa 8Z-alike Bell & Howell? Black barrel?
Quote from: EOSHD on July 19, 2013, 09:12:58 PM
Some really nice shots in there sir.
The opening flare was epic.
Is this the Kowa 8Z-alike Bell & Howell? Black barrel?
Yeas very nice anamorphic flares, I like 8)
@Gregoryofmanhattan July17 build seems to be reducing write speeds and less stable.. but on the other hand the July11 build is rock solid Love it ;D . Just reporting back on my findings. I have a question what's up with the ETTR mode seems that everytime it is on the shutter speeds get's all screwed-up and you can't fix it until you turn the camera off.
Quote from: Mak44 on July 17, 2013, 10:12:13 PM
Hi, I`m new here. I`ve read a few entries here but I`m still not sure if the Eos 50D is able to record RAW video continuasly ( without dropframes ) at 1080x1920 - 24/25 fps with a 1000x CF Card UDMA 7 100MB/second write speed or even greater (I`ve seen one with a speed of 150MB/s).
Does somebody tested it this way ? What`s about heating issues at the sensor or the cpu? Is it possible to record a few minutes not croped HD RAW video ?
Do the 50D will have any other Codec options than RAW for video recording after the ML update ? Or is it maybe a better idea to buy something like a 600D which nativly is able to record vodeo including buttons...
But the problem is that I don`t want to have the hard H264 compression on the video. Does ML supports any other video codec solutions than cropped RAW for all these EOS which haven`t an CF Card slot? for example h264 with a much higher Mbit/s rate or even somethin like
4:2:2 DNxHD or ProRes ( if the copyrights allow those things )?
Thanks for answering
and thanks for ML – I`m realy excited since I`ve found this homepage!!!
thanks a lot for answering... ( johansugarev )
Does anybody know if it`s still possible to use software based remote ( via usb ) after installing ML ?
Quote from: goldenchild9to5 on July 19, 2013, 10:01:34 PM
I have a question what's up with the ETTR mode seems that everytime it is on the shutter speeds get's all screwed-up and you can't fix it until you turn the camera off.
I think it's this problem (exposure limits of LiveView): http://www.magiclantern.fm/forum/index.php?topic=6554.msg59013#msg59013 - see explanation by a1ex.
Quote from: akumiszcza on July 19, 2013, 10:54:38 PM
I think it's this problem (exposure limits of LiveView): http://www.magiclantern.fm/forum/index.php?topic=6554.msg59013#msg59013 - see explanation by a1ex.
Correct :)
I switch auto ETTR off for low-light shots and stop down and/or use ND filters in strong light. 'Always on' ETTR works well in most situations for me.
Incidentally it seems to work a lot better with ADGT shutter timers in Tragic Lantern but still testing it TBH.
Quote from: akumiszcza on July 19, 2013, 10:54:38 PM
I think it's this problem (exposure limits of LiveView): http://www.magiclantern.fm/forum/index.php?topic=6554.msg59013#msg59013 - see explanation by a1ex.
Thanks for the link..
Quote from: Andy600 on July 19, 2013, 11:05:18 PM
Correct :)
I switch auto ETTR off for low-light shots and stop down and/or use ND filters in strong light. 'Always on' ETTR works well in most situations for me.
Incidentally it seems to work a lot better with ADGT shutter timers in Tragic Lantern but still testing it TBH.
Thank you for the info..
Just finished up an interview shot on both the 5DM3 (CU) and the 50D (Medium). The cameras worked well together, but looking back I would have made the 50D the CU camera in order to avoid the moire. However, I just updated the 50D to the July 11th build and tested the crop mode at 1920 1:85 and it recorded continuously on my 32GB KomputerBay 1000X CF for 5gb before I stopped it! This is great! I'll be sure to use this crop mode next time when I shoot alongside the 5DM3.
Quote from: akumiszcza on July 19, 2013, 10:18:10 AM
In an old post:
New post:
So, are you really experiencing continuous recording in 1080p? This means 1920x1080 (16:9 aspect ratio). I was really trying all options and can't do that on 32gig 1000x Komputerbay card. About 2000 frames max.
Continuous means the buffer is not increasing during filming, you can see it on the screen. And after a while you see "continuous OK" or similar.
I apologize. 1080p was a typo. It's 1920x802 (2.39:1) crop for continious. Sorry for the confusion. I can get continuous recording at 2:20:1 as well.
I'm getting continuous recording with 1920x1038 (1.85) with the KomputerBay 32GB 1000X on the July 11th build.
QuoteThe horses are turning to zebras!
People too, I'd rather a rainbow unicorn mode ;D
Quote from: a1ex on July 19, 2013, 08:58:18 AM
Can you upload a DNG converted with raw2dng from the horse video, and one second (or less) of a raw test shot (the RAW file) showing the same problem?
Sure, another exapmple from yesterday as I usually delete raw files straight away. http://s22.postimg.org/9e0aavw1d/DNGM19_1702_000027.jpg
(http://s22.postimg.org/9e0aavw1d/DNGM19_1702_000027.jpg)
Unfortuantely it's 222mb big as the overexposure stripes are not happening all the time. So had to take the camera out and shoot a lot yesterday, this one is the smallest.
http://speedy.sh/8rnhJ/1702.RAW
Quote from: Andy600 on July 19, 2013, 02:57:56 AM
What build?, what are you converting raw files with? and what's your post app?
The one with horses shot with Gregory's 11 of July build, but it also happened with 11 of June build. Yesterday's one shot with Tragic Lantern posted 2 days ago. I always convert using raw2dng straight through Camera Raw to AfterEffects. Used to look at the histogram, but now it's more than a a must.
Can't convert that raw file (maybe download issue). What resolution did you use?
(or, better, paste the conversion log from raw2dng - I can recover the metadata from that).
It was 1584 x 662. I think I found what's wrong - it's the canon's highlight allert form the main menu - will test it later on and let you guys know. Thanks for all help.
Quote from: v1rt on July 19, 2013, 07:05:48 PM
What am I doing wrong? I am trying low light. My resulting video is noisy that is similar to 3200 iso.
I chose LowLight from the settings, 1280x720, global off, 23.976 fps, manual aperture to f1.4(Asahi Super Takumar 50mm lens). I remember my ISO was around 400-800. I will try it again tonight once I get home.
Forgot to mention, I'm using the latest GregoryofManhattan build.
Not sure why I didn't get a response :( Should I post a video to get a response?
I tried my best last night and this is the best quality I was able to achieve. Is it acceptable?
Quote from: v1rt on July 20, 2013, 01:21:21 PM
Not sure why I didn't get a response :( Should I post a video to get a response?
I tried my best last night and this is the best quality I was able to achieve. Is it acceptable?
[spoiler]
[/spoiler]
Looks like the shot is very under-exposed for the lighting conditions. Can you upload a short raw file and I'll take a look?
Try the same shot with auto ETTR enabled. My guess is that it will hit the ETTR limits (1/25 shutter ISO 1600 in video mode) meaning the scene is too dark anyway. The sensor is still the same as it always was, regardless of the recording format ;)
QuoteCinestyle is a LOG profile and raw is linear. There will obviously be a difference in how the unprocessed images look.
Are you exposing for raw with the raw histogram enabled? Have you tried auto ETTR?
Hey Andy,
Yeah I'm now using the raw histogram and I still feel it's coming in underexposed. I just downloaded andy's 50D guide so for the next day I'll be trying to get my head around this. I'll let you know what I find out.
Thanks All
Quote from: Andy600 on July 20, 2013, 03:45:05 PM
Looks like the shot is very under-exposed for the lighting conditions. Can you upload a short raw file and I'll take a look?
Thanks Andy600! I just looked at my raw files. The ones I shot last night is around 1gigabyte. Do you want me to capture another short recording?
QuoteTry the same shot with auto ETTR enabled. My guess is that it will hit the ETTR limits (1/25 shutter ISO 1600 in video mode) meaning the scene is too dark anyway. Cinestyle will look brighter for sure but if you applied the same LOG curve as cinestyle to that footage it will likely look identical to cinestyle.
Andy, I got lost with this one. Where can I find ETTR? Also, I am using Gregory build. Should I use your build? Another thing, where can I find Cinestyle?
Sorry, I'm new to this.
Thanks!
Quote from: JBTML on July 20, 2013, 05:04:03 PM
Hey Andy,
Yeah I'm now using the raw histogram and I still feel it's coming in underexposed. I just downloaded andy's 50D guide so for the next day I'll be trying to get my head around this. I'll let you know what I find out.
Thanks All
Can you please post the link to Andy's Canon 50D guide? Thanks!
Quote from: v1rt on July 20, 2013, 05:06:38 PM
Thanks Andy600! I just looked at my raw files. The ones I shot last night is around 1gigabyte. Do you want me to capture another short recording?
Andy, I got lost with this one. Where can I find ETTR? Also, I am using Gregory build. Should I use your build? Another thing, where can I find Cinestyle?
Sorry, I'm new to this.
Thanks!
Ignore the Cinestyle bit. I was confusing your issue with the one @v1rt was talking about.
ETTR should be in your modules list no? Look under exposure menu, switch it to 'always on' (for this test). Make sure you have exposure override enabled!
See how that looks and if you are still getting the same problems we'll explore things more. I'm guessing it is your settings and lighting conditions that are causing the issue and although you set ISO to 800 it probably needs more in this case.
@1% - What else can the ADTG be used for? It's working well for the shutter on the 50D :)
Quote from: Andy600 on July 20, 2013, 05:11:11 PM
Ignore the Cinestyle bit. I was confusing your issue with the one @v1rt was talking about.
ETTR should be in your modules list no? Look under exposure menu, switch it to 'always on' (for this test). Make sure you have exposure override enabled!
See how that looks and if you are still getting the same problems we'll explore things more. I'm guessing it is your settings and lighting conditions that are causing the issue and although you set ISO to 800 it probably needs more in this case.
I found the ETTR module. It's already set to ON. Also, my exposure enabled was also set to on. So looks like it's lighting conditions. I have a Panasonic TM700 camcorder. It is very clean in low light. I was expecting the video quality would be somewhat the same. I'll try ISO 1600 tonight, same spot.
Thanks!
Update: I was playing with ML and I saw Auto ETTR. What does do? I went inside and it shows
Exposure target says -0.5
Highlight Ignore 0.2%
Clipping Mode: no clipping
Slowest shutter: 1/16
Quote from: v1rt on July 20, 2013, 05:29:15 PM
I found the ETTR module. It's already set to ON. Also, my exposure enabled was also set to on. So looks like it's lighting conditions. I have a Panasonic TM700 camcorder. It is very clean in low light. I was expecting the video quality would be somewhat the same. I'll try ISO 1600 tonight, same spot.
Thanks!
Update: I was playing with ML and I saw Auto ETTR. What does do? I went inside and it shows
Exposure target says -0.5
Highlight Ignore 0.2%
Clipping Mode: no clipping
Slowest shutter: 1/16
It automatically sets optimal exposure for raw images (including raw video) by exposing to the right (hence ETTR). Look it up, there is a whole thread about it. It works with raw video but is intended mainly for stills.
Another question. Why are my guitar's strings not straight or smooth? The image was converted from DNG to JPG. The DNG when viewed 100% within Lightroom also shows the guitar strings broken and not straight(like the link below).
http://neil.privatedns.org/M000371.jpg
I try to check twice daily the topic but not sure if i miss something, so.. does anybody know if there's news about the following developments:
- beep for audio sync
- dual ISO (is there proof that 50D cannot do it?)
- 12/10 bit raw
all of them would help a lot in making the 50D usable for real work and not just random testing.
Quote from: riccardocovino on July 20, 2013, 08:24:57 PM
I try to check twice daily the topic but not sure if i miss something, so.. does anybody know if there's news about the following developments:
- beep for audio sync
- dual ISO (is there proof that 50D cannot do it?)
- 12/10 bit raw
all of them would help a lot in making the 50D usable for real work and not just random testing.
No (no developments and probably can't do it)
No (50D can't do it)
No (I guess you're talking about compression)
Quote from: v1rt on July 20, 2013, 08:10:59 PM
Another question. Why are my guitar's strings not straight or smooth? The image was converted from DNG to JPG. The DNG when viewed 100% within Lightroom also shows the guitar strings broken and not straight(like the link below).
http://neil.privatedns.org/M000371.jpg
jaggy edges = aliasing
colors visible in the strings = moiré
Both caused by line skipping.
Quote from: Andy600 on July 20, 2013, 08:28:56 PM
No (no developments and probably can't do it)
No (50D can't do it)
No (I guess you're talking about compression)
thanks for the reply.. I wonder why 50D has problems in making a beep, being the camera able to do it while focusing.
as far as i understood right now the command that works in the others does not work for the 50D right?
regarding dual iso, i found a post from 1% dated yesterday that says he's trying to make it work on 50D:
http://www.magiclantern.fm/forum/index.php?topic=3904.msg60409#msg60409
I guess you have more recent news if you say it's not possible :(
12/10 bit: it's compression as long as it cuts 2/4 bits of information, but it's still raw. there was a topic with many different attempts started but none was succesful. BMCC has 12 bit raw and it's more than enough! every way to shrink the size of the files without evident loss in quality is welcome, 8 minutes in 32GB is still a problem for longer productions.
Quote from: Andy600 on July 20, 2013, 08:36:12 PM
jaggy edges = aliasing
colors visible in the strings = moiré
Both caused by line skipping.
Got it. Is there any fix being worked on for this?
We can't break the laws of physics. Read some theory before asking the same things over and over.
Quote from: a1ex on July 20, 2013, 09:58:38 PM
We can't break the laws of physics. Read some theory before asking the same things over and over.
The reason I asked is because when doing multiple shots using external intervalometer, I can get a very clean shot on my 50D. I was under the impression that the dng files inside the raw file have the same quality.
Thanks.
Nope, not even on 5D3.
To get the same quality, you need to sample the entire sensor at 30fps (without line skipping). I doubt the 50D can do that (just look at the rolling shutter from x5 zoom).
Quote from: v1rt on July 20, 2013, 10:43:01 PM
The reason I asked is because when doing multiple shots using external intervalometer, I can get a very clean shot on my 50D. I was under the impression that the dng files inside the raw file have the same quality.
Thanks.
The only consumer cameras I know of doing that are the nikon v1,v2 and for only 2 seconds,so...
My shots tend to look underexposed compared to a still photo or h264 at the same settings. Anyone else with that feeling?
It still bugs me that LV and the LCD top display show different shutter speed values. Witch is the accurate one?
Hi guys, long-time lurker/not-so-secret admirer of all the work going on here, I figured I'd finally join up and see what help I can be.
(Realised what I posted here previously was probably better suited to the workflow board :P)
Quote from: riccardocovino on July 20, 2013, 09:32:28 PM
thanks for the reply.. I wonder why 50D has problems in making a beep, being the camera able to do it while focusing.
as far as i understood right now the command that works in the others does not work for the 50D right?
regarding dual iso, i found a post from 1% dated yesterday that says he's trying to make it work on 50D:
http://www.magiclantern.fm/forum/index.php?topic=3904.msg60409#msg60409
I guess you have more recent news if you say it's not possible :(
12/10 bit: it's compression as long as it cuts 2/4 bits of information, but it's still raw. there was a topic with many different attempts started but none was succesful. BMCC has 12 bit raw and it's more than enough! every way to shrink the size of the files without evident loss in quality is welcome, 8 minutes in 32GB is still a problem for longer productions.
I think what 1% was referring to in his comment about the 50D was ADTG shutter timers. The ADTG is a chip in the camera that the devs can now access and use for certain things, Dual ISO being one of them. http://magiclantern.wikia.com/wiki/ADTG
According to the Dual ISO info it "Requires a camera with two analog amplifiers. (cameras with 8-channel readout seem to have this)". The newer cameras 5D MkIII and 6D have this but older cameras do not as they have 4-channel readout. The reason the 7D can also do it (I presume) is that it has dual DIGIC4 processors which is 2 x 4-channel readout (this is also why Dual ISO implementation is more tricky on the 7D).
That's my understanding of it.
re: in-camera compression - forget it!
re: Beep - the 50D does not have the audio components of the other cameras. The focus confirm beep is not the same thing and I think, even if that can be triggered it wouldn't be loud enough to be of any use unless you're using a hotshoe mounted mic.
thanks andy600, now everything is much more clear.
so 1% is trying to make the ADTG work in the 50D but that's just the first step for dual ISO, and next steps are not possible due to single analog amplifier.
my only hope about all of this is the beep, you're right it's not so loud but i still think you can easily recognize it in a normal ambient if shotguns aren't your only source.
the post about 12/10 bit is sadly sleeping from june.. you are right about forgetting it!
http://www.magiclantern.fm/forum/index.php?topic=5601.250
Here is my latest one. What do you think?
Hello. I can't seem to figure out how to read and set my shutter speed settings in ML..
How come when every I make adjustments to ISO my shutter speed changes?
What are the Tv numbers?
Sometimes I can't get my shutter speed setting down to 1/48, how come?
Thanks
QuoteIt still bugs me that LV and the LCD top display show different shutter speed values. Witch is the accurate one?
With ADTG, its LV. Top screen shows you photo shutter.
QuoteAccording to the Dual ISO info it "Requires a camera with two analog amplifiers. (cameras with 8-channel readout seem to have this)". The newer cameras 5D MkIII and 6D have this but older cameras do not as they have 4-channel readout. The reason the 7D can also do it (I presume) is that it has dual DIGIC4 processors which is 2 x 4-channel readout (this is also why Dual ISO implementation is more tricky on the 7D).
I'm not even sure if 6D has this. I'm having problems there.. .at least on 50D reg0 moves, on 6D it doesn't. I need a log to see what it even looks like from 5D3. Also the reg address keeps changing. I should probably read the PDF, maybe it will help me "get it".
Quote from: thorstone137 on July 21, 2013, 09:44:48 PM
Hello. I can't seem to figure out how to read and set my shutter speed settings in ML..
How come when every I make adjustments to ISO my shutter speed changes?
What are the Tv numbers?
Sometimes I can't get my shutter speed setting down to 1/48, how come?
Thanks
Welcome to the world of under-development and not-final software, bro ))))
Try this build by Andy:
http://www.magiclantern.fm/forum/index.php?topic=5586.msg59779#msg59779 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg59779#msg59779)
It does adjustment of shutter much better than some previous builds.
It has some... feature that you must be aware of (at least in my camera): when you rotate the front wheel to change the shutter speed, nothing may change. Keep rotating, and the values will start changing. It's a small quirk and once you know it - you are golden. I'd like to repeat: it's much better than previous builds )
Quote from: johansugarev on July 21, 2013, 04:09:22 AM
My shots tend to look underexposed compared to a still photo or h264 at the same settings. Anyone else with that feeling?
I got the same problem. Asked few days earlier, and no response. I figure out that is something 1% is working on. The only remedy I have found is to enable Constant expo in FPS override settings. Also If you use Auto ETTR, the LV exposure is equal to the Photo and Video exposure.
Right. I hear ya. I'll try this build :)
Quote from: thorstone137 on July 21, 2013, 10:41:51 PM
Right. I hear ya. I'll try this build :)
What photo mode are you in?
You should at least be in 'M' manual mode and preferably in a duplicate of it written to a custom preset (C1 or C2) on the top mode dial.
Tv = Time value for auto exposure with shutter priority (which you certainly don't want for video).
All basic camera stuff TBH. I worry when I see people trying to run before they can walk. ::)
I haven't had time to finish writing my guide yet but I would suggest to anyone starting out with raw video on the 50D to first learn the basics of the camera.
I have found that using a custom preset is the least problematic. In other modes the camera will function and behave as it should but may cause issues for video and you might mistake those problems as bugs or Magic Lantern problems.
I suggest you dial-in M on the top dial then write this to either C1 or C2 (custom preset locations). This has proven to be the least problematic for me and it's also 'safer' to use one of these memory spaces. The 50D doesn't have a video mode so C1 or C2 will become that. (btw, C1/C2 will always load as saved so WB, ISO etc will default to saved values unless overridden by Magic Lantern).
Hi
Today I also did some shoot out to test crop mode, will post later. I always put it in M mode, check my settings and shutter in "photo" mode before record. Also in very bright (sun) light I use viewfinder to check, do the focus and then switch to live view for raw recording. This gives me the best & sharp results. If you don't have any filter then shutter must be set higher than 1/48 in bright light.
One more thing: if your "live view" does not really do what you expect in your setting (shutter, iso etc), goto menu, 6th, Live View function settings, expo simulation: Enable
hope this helps :-)
Quote from: rommex on July 21, 2013, 09:53:22 PM
....It has some... feature that you must be aware of (at least in my camera): when you rotate the front wheel to change the shutter speed, nothing may change. Keep rotating, and the values will start changing.
yes, I've noticed that too. Seems to only change the value on every other click of the wheel.
For exposing correctly for raw video make sure the histogram is first enabled for RAW. You need to set it up and make sure 'hint's are enabled' so you can manually ETTR.
The auto ETTR module is fantastic for photos but it will alter your shutter speed in video mode and you don't really want that. If it's too bright you will need to stop-down you lens but (depending on your lens) I wouldn't suggest going to the last stop as it may cause diffraction problems. Get a variable ND filter. It's vital in bright conditions TBH.
Hi,
I see many exposure issues and questions for RAW recording.
I am quite new with ML and RAW recording but from my experience so far the best idea is to put exp. override=ON and set ISO and shutter to fixed value (for fps=24 shutter can not be higher then 1/24). I have fully manual lens (Samyang vdslr) so changing aperture continuously during filming.
Don't you think this is the best idea which gives you full control?
Quoteyes, I've noticed that too. Seems to only change the value on every other click of the wheel.
Go one shutter up and then turn the wheel back. Or set from ml menu.
This is how canon does it. 50D is mostly expo simulation and geared towards photos. Also turn on raw video after starting "movie' mode.
Quote from: jgerstel on July 21, 2013, 11:44:33 PM
Hi
Today I also did some shoot out to test crop mode, will post later. I always put it in M mode, check my settings and shutter in "photo" mode before record. Also in very bright (sun) light I use viewfinder to check, do the focus and then switch to live view for raw recording. This gives me the best & sharp results. If you don't have any filter then shutter must be set higher than 1/48 in bright light.
One more thing: if your "live view" does not really do what you expect in your setting (shutter, iso etc), goto menu, 6th, Live View function settings, expo simulation: Enable
hope this helps :-)
Thanks :) But I don't understand how you're in M mode and then putting shutter in "photo".. What am I missing here?
Quote from: BartekS on July 22, 2013, 12:43:05 AM
Hi,
I see many exposure issues and questions for RAW recording.
I am quite new with ML and RAW recording but from my experience so far the best idea is to put exp. override=ON and set ISO and shutter to fixed value (for fps=24 shutter can not be higher then 1/24). I have fully manual lens (Samyang vdslr) so changing aperture continuously during filming.
Don't you think this is the best idea which gives you full control?
Exp override = yes
Shutter speed depends on what you are shooting or what look you are trying to achieve for the motion/motion blur. 1/24 at 24p is a 360 degree shutter. The typical shutter speed for natural motion blur is fps x2 so 24fps would mean 1/48 shutter speed. Go higher for less motion blur and a more choppy look and lower for low light (only if you have to).
ISO is wholly dependent on what you need to achieve correct exposure at your chosen aperture and shutter speed.
Quote from: Andy600 on July 21, 2013, 11:27:50 PM
What photo mode are you in?
You should at least be in 'M' manual mode and preferably in a duplicate of it written to a custom preset (C1 or C2) on the top mode dial.
Tv = Time value for auto exposure with shutter priority (which you certainly don't want for video).
All basic camera stuff TBH. I worry when I see people trying to run before they can walk. ::)
Thanks for tips Andy ;) For the record I was in M mode. I just got my 50d(without a manual) so I hadn't caught up on the C settings; I've made my presets.
Any tips on setting up the histogram? I understand how to navigate to it and make sure it's on. And I've read up on ETTR so I get that.. And I realize it's an exposure equation of ISO, Aperture, and Shutter speed..
I guess where I'm getting lost is trying to understand where the line or balance is between canon firmware settings and ML's and how they effect each other.
Quote from: Andy600 on July 21, 2013, 11:47:02 PM
yes, I've noticed that too. Seems to only change the value on every other click of the wheel.
Andy, in this build I also lost the overexposure warning dots on my histogram, per channel. They are on in the menu for sure, just not displayed. Not a big deal, just so you know.
Thanks for the build, I like it )
Quote from: Andy600 on July 22, 2013, 01:20:03 AM
Exp override = yes
Shutter speed depends on what you are shooting or what look you are trying to achieve for the motion/motion blur. 1/24 at 24p is a 360 degree shutter. The typical shutter speed for natural motion blur is fps x2 so 24fps would mean 1/48 shutter speed. Go higher for less motion blur and a more choppy look and lower for low light (only if you have to).
ISO is wholly dependent on what you need to achieve correct exposure at your chosen aperture and shutter speed.
I realize these modules can and will be buggy, and I'm not trying to make a motion picture or doing and commercial work. However, I really would like to start getting consistent results.
And because you are working on a manual so to speak. I'm still meerky when it comes to get a that consistent shutter speed. Should I be prioritizing the FPS (23.976 or 24 for that cinematic look) and let the shutter speed do it's thing?
Or should I be using filters to make sure I always get the shutter speed correct?
Quote from: thorstone137 on July 22, 2013, 01:30:59 AM
I realize these modules can and will be buggy, and I'm not trying to make a motion picture or doing and commercial work. However, I really would like to start getting consistent results.
And because you are working on a manual so to speak. I'm still meerky when it comes to get a that consistent shutter speed. Should I be prioritizing the FPS (23.976 or 24 for that cinematic look) and let the shutter speed do it's thing?
Or should I be using filters to make sure I always get the shutter speed correct?
It's a big topic but for a quick and very basic set up:
Set FPS to 23.976, 24 or 25p with FPS Override (set FPS override to exact)
Set shutter speed to one of the green values (these are approx 180 degrees)
Set histogram to raw
use the aperture and ISO to push exposure to the right of the histogram. If you see a "-" in front of the exposure value on the histogram you are clipping i.e. E1.0 is ok but E-1.0 is clipping so adjust your aperture and/or ISO to pull it back.
As I say, this is a pretty big topic with many variations of settings either for the shooting conditions, subject matter or for effect (i.e. Private Ryan) but these settings will get you started with (when used properly) good motion blur and good exposure. Don't forget to conform your footage in your NLE to whatever framerate you set FPS override to or you'll get glitchy playback.
If you let the shutter go wild you'll get un-natural looking footage so either try to stay at or around 2x your framerate and then read up on when and why to change the shutter speed.
Is there actually a way to make the camera wheels change the speed and iso values,? or at least the same way it eorks for photo, right now Im always doing it over the menus.
The wheel (above shutter button) controls framerate and use top ISO button to change ISO
Quote
Exp override = yes
Shutter speed depends on what you are shooting or what look you are trying to achieve for the motion/motion blur. 1/24 at 24p is a 360 degree shutter. The typical shutter speed for natural motion blur is fps x2 so 24fps would mean 1/48 shutter speed. Go higher for less motion blur and a more choppy look and lower for low light (only if you have to).
ISO is wholly dependent on what you need to achieve correct exposure at your chosen aperture and shutter speed.
Thanks Andy for explanations :) All of these I understand. I just wanted to point out the best idea is to stay with full manual control, set shutter and iso fixed and respond to changing light during filming by changing aperture.
Quote from: Andy600 on July 22, 2013, 01:51:24 AM
It's a big topic but for a quick and very basic set up:
Set FPS to 23.976, 24 or 25p with FPS Override (set FPS override to exact)
Set shutter speed to one of the green values (these are approx 180 degrees)
Set histogram to raw
use the aperture and ISO to push exposure to the right of the histogram. If you see a "-" in front of the exposure value on the histogram you are clipping i.e. E1.0 is ok but E-1.0 is clipping so adjust your aperture and/or ISO to pull it back.
As I say, this is a pretty big topic with many variations of settings either for the shooting conditions, subject matter or for effect (i.e. Private Ryan) but these settings will get you started with (when used properly) good motion blur and good exposure. Don't forget to conform your footage in your NLE to whatever framerate you set FPS override to or you'll get glitchy playback.
If you let the shutter go wild you'll get un-natural looking footage so either try to stay at or around 2x your framerate and then read up on when and why to change the shutter speed.
Thanks Andy. Obviously I'm a newbie, but I've been trying to do my research. It's pretty cool how much is out there if you look. Everything was telling me I needed to get the shutter speed right. So I appreciate your confirmation. ;)
What do you mean by "Green Values"?
Is my shutter speed in the ML Exposure settings suppose to be changing automatically?
When I first turn on my camera at my C1 settings I have set shutter speed of 1/48 to my 24FPS. Then when I switch to live view to see my exposure my shutter speed changes. How and why? :p
Green values = exactly how it sounds. The shutter numbers are green (or blue or red).
As I said earlier, using C1 or C2 will load settings exactly as they were saved unless overriden by magic lantern settings. If your shutter value is constantly changing you're either playing with the front wheel or some other ML setting is affecting things.
My shutter is constantly changing to 1/33 when I gear up the ISO above 200. At ISO 100 I can get 1/48, but when I try to change the ISO things go south - the top LCD shows 1/50 but LV shows 1/33 and somthing like ISO 800eq when I'm on ISO 1600. Tried changing both with the wheel and in ML menu. THat is with Gregory's latest build, also with Tragic Lantern 2.0.
Quote from: johansugarev on July 22, 2013, 02:30:25 AM
My shutter is constantly changing to 1/33 when I gear up the ISO above 200. At ISO 100 I can get 1/48, but when I try to change the ISO things go south - the top LCD shows 1/50 but LV shows 1/33 and somthing like ISO 800eq when I'm on ISO 1600. THat is with Gregory's latest build, also with Tragic Lantern 2.0.
Do you have exposure override enabled and what mode are you in?
Are you using auto ETTR? If so, switch it off.
re: top display - http://www.magiclantern.fm/forum/index.php?topic=5586.msg60835#msg60835
Read through the last page or so. I explained how to set up and 1% explained that the top LCD shows photographic shutter speed. When you're shooting raw video you're in movie mode. Magic Lantern values are the correct ones.
Read that. Not using auto ETTR. In C1 mode, witch is M in photo mode set to 1/50sec. ISO 100, auto WB. I first enable this mode, then LV, then Movie Mode, then Modules, then RAW, then I expose. EXP simulation is set to Movie, Exposure Override is not enabled. Should I always use it?
I'll try you 18Jul build in a moment.
Edit: Using Andy600's 18Jul build, it seems to be correct with exposure override. Its showing the ISO's as for example ISO100ov - what does that mean? When I enable FPS override along with exposure override, I can get 1/54sec. and 1/49sec. with 23.976fps at ISO100ov set to optimize for low light. Also 1/64 at 30fps with FPS override off at ISO100ov, as well as other ISO values.
Shutter changes from 1/54 to 1/52 in 5x zoom with fps override on and from 1/64 to 1/59 with fps override off.
I should desable auto exposure on zoom mode (i guess).
Hey guys, I just want to say thank you for working so hard on these builds and turning the Canon 50D into a baby Red One! I was thinking about getting a BMCC, but this changed my mind at the last minute (literally, I had just tested out the 50D footage and I got a call about my BMCC pre-order shipping the next day. I canceled it and now I'm not as broke as I would've been, haha).
I did my first video here using Gregory's May 28th build:
https://vimeo.com/69726896 (https://vimeo.com/69726896)
*I lost some footage because I went over the 4GB mark and got those pink files and .R00 files.
*I'm still unclear if RAW2DNG (PC version) works on files over 3.99GB. It wouldn't transcode to .DNG files for me. So for now, I'm just making sure my clips don't hit 4GB.
*I read something about stitching files together, but I'm not sure if that's related to the above problem or not.
Other than those two minor hiccups, I'm loving RAW. Recorded on Komputrbay 64GB 1000x. POST: I used CS6 ACR and made JPEGS and imported the JPEGS into PPRO and nested them to make sequences. (I think this was probably the long method, and I will try making DNxHD files in AE next time.)
Quote from: Andy600 on July 22, 2013, 02:22:34 AM
Green values = exactly how it sounds. The shutter numbers are green (or blue or red).
As I said earlier, using C1 or C2 will load settings exactly as they were saved unless overriden by magic lantern settings. If your shutter value is constantly changing you're either playing with the front wheel or some other ML setting is affecting things.
Ok.. So, I went through my settings and found that under "Movie Tweeks" I had "Shutter Lock - On". Turning it off seemed to stop the shutter speed from changing randomly.
That said, when I load C1 my settings are what they should be. I trash out of ML and hit the live view button then I hit the trash button to see my ML settings and my shutter speed changes to roughly 1/80. This is the same number that is at the bottom of my screen in "Green".
When I back out the same way and don't try to change the shutter speed by closing the live view screen and then hitting trash to bring up the ML settings my shutter speed is at 1/48 again.
When the live view screen is active and I see 1/80 and try to lower it to something close it won't let me set it to 1/48. However many stops down I try to take it from 1/80 reflects on the shutter speed though. For example, if I tried 3 stops down and then backed out by turning of live view and then bring up the ML settings my shutter speed will be at 1/45 rather than 1/48..
Is this normal?
As I mentioned earlier Andy's new build sort of fixed the problem. I can record at 1/64 at 30fps and at 1/54 at 23.988 fps.
The camera got pretty hot after 15 minutes of testing.
Here's a video of the shutter lock issue I was talking about
After having success indoors. I decided to take a walk and get some footage. When using the latest Raw2dng I got a interlacing method not supported on all my raw files.. what the?
Raw2cDng won't even let me load them in the program..
Any clues?
Actually, I just remembered while I was in live view my greys and blacks would shift to a purple for a sec and then shift back for a couple secs and then back to purple.. It was a first for me..
I've tried several more since I got home and I get the same thing when using Raw2dng.exe
interlacing method not supported
iso bdbd
Quote from: thorstone137 on July 22, 2013, 03:48:25 AM
Here's a video of the shutter lock issue I was talking about
Try putting "Exp Override" ON cause you had it off need that for right Shutter..
Quote from: DJG on July 22, 2013, 03:03:20 AM
Hey guys, I just want to say thank you for working so hard on these builds and turning the Canon 50D into a baby Red One! I was thinking about getting a BMCC, but this changed my mind at the last minute (literally, I had just tested out the 50D footage and I got a call about my BMCC pre-order shipping the next day. I canceled it and now I'm not as broke as I would've been, haha).
I did my first video here using Gregory's May 28th build:
https://vimeo.com/69726896 (https://vimeo.com/69726896)
*I lost some footage because I went over the 4GB mark and got those pink files and .R00 files.
*I'm still unclear if RAW2DNG (PC version) works on files over 3.99GB. It wouldn't transcode to .DNG files for me. So for now, I'm just making sure my clips don't hit 4GB.
*I read something about stitching files together, but I'm not sure if that's related to the above problem or not.
Other than those two minor hiccups, I'm loving RAW. Recorded on Komputrbay 64GB 1000x. POST: I used CS6 ACR and made JPEGS and imported the JPEGS into PPRO and nested them to make sequences. (I think this was probably the long method, and I will try making DNxHD files in AE next time.)
Great video.. like the images and camera work.
I don't know what it is with the 50D with low light shooting :'(, any ISO above 800 example 1000, 1250 +.. are really noisy. Images @ times are not even usable way too many pattern noise specially in the shadows. I replicated the same scenes, and settings meaning ISO, F-Stop used the same lens and gaged the exposure on my Hacked GH2 and got way cleaner and usable footage. Not knocking the 50D but when shooting Raw in low light to me it's been a problem with the amount of noise I'm getting. Try every setting on the Canon menu, and ML nothing helps. From my observation and test the 50D is surely a winner for all daylight shoots, and not for low light.
If anybody wanna chime in with their experiences and settings shooting with the 50D in low light that would be great.
Really happy with ML. Thank you folks!
Canon 50D
f/5.6
Canon 70-200mm @ 200mm
400x CF card
ML settings
Exp Override true
ISO 100
23.976 fps Exact
1/48 shutter
HaCKed
Global Draw false
1584x662 reencoded to 1920x1080 libx264 using ffmpeg
I post processed all the images in Linux using ffmpeg. I also used it to pad 139pixels top and bottom since a/r is 2.39. If I don't do it, YouTube down converts the quality to 480p :( Anyways, by padding it, I'm able to keep the high image quality.
I'm extremely happy with the results.
Quote from: DJG on July 22, 2013, 03:03:20 AM
Hey guys......
*I lost some footage because I went over the 4GB mark and got those pink files and .R00 files.
*I'm still unclear if RAW2DNG (PC version) works on files over 3.99GB. It wouldn't transcode to .DNG files for me. So for now, I'm just making sure my clips don't hit 4GB.
*I read something about stitching files together, but I'm not sure if that's related to the above problem or not.
Nice video.
Try using Raw2CDNG. It does work with files longer than 4GB.
You first rename split files (so that they have extensions .001, .002, etc) and then use the free program
File Splitter & Joiner to join them.
Then you feed the resulting files to Raw2CDNG -- it should work. It worked for me.
UPDATED: also I had been a fan of 28 May Build for long since it was stable and firm as a rock. Now I use Andy's new build and I would encourage you to try it -- you'll like it as well --
PINK frames are a history :) :
http://www.magiclantern.fm/forum/index.php?topic=5586.msg59779#msg59779
@thorstone137 - First, why are jumping in and out of Live View and changing settings? Also, I noticed you have auto WB enabled. Set WB manually or at least use a preset (daylight, cloudy, tungsten etc). I don't know if auto WB will cause color shift during a shot but my guess is that it could.
The 'purple' frame issue is something else. What build are you using?
Regarding your conversion problem. Interlacing error? I've not seen this before ???. Is Raw2dng.exe displaying this error and if so can you explain the steps you are taking to see the error? Does it happen when you drag-and-drop a raw file onto raw2dng.exe.
Quote from: rommex on July 22, 2013, 10:20:52 AM
Nice video.
Try using Raw2CDNG. It does work with files longer than 4GB.
You first rename split files (so that they have extensions .001, .002, etc) and then use the free program File Splitter & Joiner to join them.
Then you feed the resulting files to Raw2CDNG -- it should work. It worked for me.
UPDATED: also I had been a fan of 28 May Build for long since it was stable and firm as a rock. Now I use Andy's new build and I would encourage you to try it -- you'll like it as well -- PINK frames are a history :) :
http://www.magiclantern.fm/forum/index.php?topic=5586.msg59779#msg59779
I wouldn't advise anyone to use the 28 May build. Too much has changed and lots of issues have since been fixed and continue to be fixed.
My latest builds are here https://bitbucket.org/andy600/andy50d/downloads (Unified) or here: https://bitbucket.org/andy600/tl50d/downloads (Tragic Lantern 2.0)
My Unified build is effectively the same code that GregoryOfManhatten compiles here: https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads so check for whichever of ours is newer. His is currently.
Tragic Lantern 2.0 has better raw video performance and better shutter control but if you are a newbie I would suggest waiting for the coming 50D guide before trying it as some of the settings (and quirks) are undocumented and need explanation.
Quote from: Andy600 on July 22, 2013, 11:32:49 AM
...
I wouldn't advise anyone to use the 28 May build...
For some reason I stuck to it for a month a so -- it worked just reliably and with no glitches, as opposed t some newer ones in June.
But the current builds are super, for sure. 8)
FYI: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Testing 50D crop mode, now 50mm lens turns into zoom lens!
Very crisp image!
Camera: canon 50D
Resolution: 1920 x 1080
Magic Lantern RAW
max frames I get with 1080P crop on 50D: 171
RAW shot straight from camera can be downloaded here:
https://www.wetransfer.com/downloads/a3a6bc0b5c34c138b7c348c52487b0c320130722140507/47f5ed6aaaeab43d763b2e40731f901b20130722140508/d0bcc2
Quote from: rommex on July 22, 2013, 10:20:52 AM
Try using Raw2CDNG. It does work with files longer than 4GB.
You first rename split files (so that they have extensions .001, .002, etc) and then use the free program File Splitter & Joiner to join them.
Then you feed the resulting files to Raw2CDNG -- it should work. It worked for me.
You don't need to join them before dropping to raw2cdng. Just get .raw, .r00 etc. and drop everything to newest raw2cdng. It will join and convert them itself.
Shot with the Gregory July 11th build. Camera was in crop mode with the resolution set to 1920x818 (2.35). The following are the settings:
fps: 23.976
shutter: 1/48
iso: 100
color profile: standard (3,0,0,0)
HacKed Mode
I was able to achieve continuous recording up to 1.85 aspect ratio using a KomputerBay 32GB 1000X.
Post-Processing: dng's were created with Rawanizer. Grading was done in ACR, with a final pass performed in Color Finesse 3. h.264 was created in Adobe Media Encoder CC.
https://vimeo.com/70786766
Quote from: pinger007 on July 22, 2013, 05:45:09 PM
Shot with the Gregory July 11th build. Camera was in crop mode with the resolution set to 1920x818 (2.35). The following are the settings:
fps: 23.976
shutter: 1/48
iso: 100
color profile: standard (3,0,0,0)
HacKed Mode
I was able to achieve continuous recording up to 1.85 aspect ratio using a KomputerBay 32GB 1000X.
Post-Processing: dng's were created with Rawanizer. Grading was done in ACR, with a final pass performed in Color Finesse 3. h.264 was created in Adobe Media Encoder CC.
https://vimeo.com/70786766
Pinger that was beautiful.. Did you export out of ACR as .Tiff was lens did you use?
QuoteCan you please post the link to Andy's Canon 50D guide? Thanks!
It's on the front page of EOSHD.com
It's very well done
Quote from: JBTML on July 22, 2013, 06:38:26 PM
It's on the front page of EOSHD.com
It's very well done
If it's a paid one then it's not Andy600's.
Quote from: akumiszcza on July 22, 2013, 08:03:05 PM
If it's a paid one then it's not Andy600's.
That's what I thought too. I was looking for Andy's.
It's coming but it's a lot of work and I have to write it in between other work. I have about 40 pages written so it won't be too much longer :)
Quote from: Andy600 on July 22, 2013, 09:24:13 PM
It's coming but it's a lot of work and I have to write it in between other work. I have about 40 pages written so it won't be too much longer :)
Coolio! Am I right that you own Tragic Lantern?
Quote from: v1rt on July 22, 2013, 10:12:04 PM
Coolio! Am I right that you own Tragic Lantern?
No, it's 1% who does the hard work. Tragic Lantern is his baby. He's the clever one ;D I just compile it.
I'm learning code but still a long way off being able to contribute anything.
Quote from: Andy600 on July 22, 2013, 10:48:12 PM
No, it's 1% who does the hard work. Tragic Lantern is his baby. He's the clever one ;D I just compile it.
I'm learning code but still a long way off being able to contribute anything.
Oh ok! :)
I hope I can share too in the future. I was trying to git pull the other day but was failing. I hope someone here can provide the .git link
Quote from: v1rt on July 22, 2013, 11:24:22 PM
Oh ok! :)
I hope I can share too in the future. I was trying to git pull the other day but was failing. I hope someone here can provide the .git link
Magic Lantern source code is hosted on Bitbucket https://bitbucket.org/hudson/magic-lantern/src
Thank you so much! :)
Quote from: Andy600 on July 22, 2013, 11:17:16 AM
@thorstone137 - First, why are jumping in and out of Live View and changing settings? Also, I noticed you have auto WB enabled. Set WB manually or at least use a preset (daylight, cloudy, tungsten etc). I don't know if auto WB will cause color shift during a shot but my guess is that it could.
The 'purple' frame issue is something else. What build are you using?
Regarding your conversion problem. Interlacing error? I've not seen this before ???. Is Raw2dng.exe displaying this error and if so can you explain the steps you are taking to see the error? Does it happen when you drag-and-drop a raw file onto raw2dng.exe.
I'm using your latest build. I'll try manual WB. Here is a screen shot of my try to run Raw2dng
Quote from: Andy600 on July 22, 2013, 09:24:13 PM
It's coming but it's a lot of work and I have to write it in between other work. I have about 40 pages written so it won't be too much longer :)
Why not make a wiki or even a Wordpress page with free access for others to help out?
I designed an app that allows this easily if you want an account at www.openbuk.com - I'll contribute a free account for this use if the community wants one. Just lmk
Quote from: thorstone137 on July 23, 2013, 12:50:43 AM
I'm using your latest build. I'll try manual WB. Here is a screen shot of my try to run Raw2dng
[spoiler][/spoiler]
Try this one: https://bitbucket.org/andy600/andy50d/downloads/raw2dng.exe
Quote from: krashnik on July 23, 2013, 01:08:39 AM
Why not make a wiki or even a Wordpress page with free access for others to help out?
I designed an app that allows this easily if you want an account at www.openbuk.com - I'll contribute a free account for this use if the community wants one. Just lmk
Hey thanks :)
Yes, I've thought of doing something like that and I'll be happy to contribute towards a general Magic Lantern guide when I have time but I want to finish the 50D downloadable guide first as it's a special project.
Less than two months my Komputerbay 64GB 1000X went corrupt, or failed on me lol.. it won't show in camera, won't show on my mac, won't show on my PC. This is how it happened.. Was running on @Gregoryofmanhattan July 11 Build 5X Zoom mode 1920x818 res aspect ration 2:35 after shooting for 30sec the camera froze-up put the camera switch on off nothing, finally pulled the battery out than put it back in turned it back on than nothing. For a second I believed my camera was bricked, took the card out turned it on again bam camera was fine. Contacted Komputerbay a couple times, still waiting for an answer to swap my card. If anybody had to return their card to Komputerbay, what's the process, and how long does it take for you to get it back?
Quote from: Andy600 on July 23, 2013, 02:00:57 AM
Try this one: https://bitbucket.org/andy600/andy50d/downloads/raw2dng.exe
I tried the raw2dng.exe your suggested with the RAWs from last night and the same thing happens..
So I did a fresh install of your latest unified build by re-installing the 1.0.9 50d firmware, reformatting my 32g Kumputerbay 1000x card, and reinstalling ML. That seemed to clear it up. Weird.
Quote from: goldenchild9to5 on July 23, 2013, 02:23:42 AM
Less than two months my Komputerbay 64GB 1000X went corrupt, or failed on me lol.. it won't show in camera, won't show on my mac, won't show on my PC. This is how it happened.. Was running on @Gregoryofmanhattan July 11 Build 5X Zoom mode 1920x818 res aspect ration 2:35 after shooting for 30sec the camera froze-up put the camera switch on off nothing, finally pulled the battery out than put it back in turned it back on than nothing. For a second I believed my camera was bricked, took the card out turned it on again bam camera was fine. Contacted Komputerbay a couple times, still waiting for an answer to swap my card. If anybody had to return their card to Komputerbay, what's the process, and how long does it take for you to get it back?
My 32gb KB card also died while in crop mode after stopping recording it wouldnt finish writing the buffer to the card, it wouldnt turn off so I had to take out the battery. After that there was no way of reviving the card.
Amazon wouldnt offer replace only refund(got lucky because it was during the 30day period). I was goin to get a transcent but the komputerbay is now 69€ and the transcent went from 86€ to 106€. I guess I will go with the transcent anyway, and avoid cropmode.
Just to clarify.. I take it there is no way to get past the 4gb RAW file limit?
Sorta defeats the 50d's writing speed capabilities.. at 1584x856 I can't seem to more than a min of continous footage.. :(
Quote from: thorstone137 on July 23, 2013, 02:46:24 AM
Just to clarify.. I take it there is no way to get past the 4gb RAW file limit?
Sorta defeats the 50d's writing speed capabilities.. at 1584x856 I can't seem to more than a min of continous footage.. :(
??? If your card can record continuously it will record split files up to the cards limit. You just need to use an app or script to stitch them together. Raw2cdng will do it automatically
Quote from: Andy600 on July 23, 2013, 02:50:47 AM
??? If your card can record continuously it will record split files up to the cards limit. You just need to use an app or script to stitch them together. Raw2cdng will do it automatically
Thanks.. I guess I needed to dig a little deeper ;) I just successful joined 2 and converted with RAW2Dng! PROGRESS :p
Has anyone seen any differences is dng quality among the different raw converters?
Quote from: araucaria on July 23, 2013, 02:42:04 AM
My 32gb KB card also died while in crop mode after stopping recording it wouldnt finish writing the buffer to the card, it wouldnt turn off so I had to take out the battery. After that there was no way of reviving the card.
Amazon wouldnt offer replace only refund(got lucky because it was during the 30day period). I was goin to get a transcent but the komputerbay is now 69€ and the transcent went from 86€ to 106€. I guess I will go with the transcent anyway, and avoid cropmode.
Thanks for letting me know araucaria, so that means I have to buy a new one after the 30 days right? So how come so many are getting their cards exchanged, and saying that there is a lifetime guarantee on them?
Quote from: araucaria on July 23, 2013, 02:42:04 AM
My 32gb KB card also died while in crop mode after stopping recording it wouldnt finish writing the buffer to the card, it wouldnt turn off so I had to take out the battery. After that there was no way of reviving the card.
Amazon wouldnt offer replace only refund(got lucky because it was during the 30day period). I was goin to get a transcent but the komputerbay is now 69€ and the transcent went from 86€ to 106€. I guess I will go with the transcent anyway, and avoid cropmode.
Card is back running stronger than ever Araucadia, I just stayed positive about the situation. I'm not sure what I did but all I remember is that I blew air in the pin holes shook the card-up a couple times put it in the memory card reader and Voila everything is there. Mind you I've been trying for half a day to get it to show, or mount. Going to reformat and reinstall everything ;D
Quote from: goldenchild9to5 on July 23, 2013, 03:59:25 AM
Card is back running stronger than ever Araucadia, I just stayed positive about the situation. I'm not sure what I did but all I remember is that I blew air in the pin holes shook the card-up a couple times put it in the memory card reader and Voila everything is there. Mind you I've been trying for half a day to get it to show, or mount. Going to reformat and reinstall everything ;D
Wow, thats great! anyway, if it breaks after the 30 days you still have warrant (2 years in europe) but its a pain to deal with manufacturers.
Quote from: araucaria on July 23, 2013, 04:58:16 AM
Wow, thats great! anyway, if it breaks after the 30 days you still have warrant (2 years in europe) but its a pain to deal with manufacturers.
Thanks for the info.. I already sent them an email now I don't know what to do ::) should I send it back, or just ride it out. My philosophy on it is if it went dead and came back that means it's here to stay 8)
Quote from: Andy600 on July 23, 2013, 02:00:57 AM
Try this one: https://bitbucket.org/andy600/andy50d/downloads/raw2dng.exe
Ugh.. So I did some more shooting today and this evening, and my first 12 or so takes convert just fine. Just now I got half way through a batch of 15 takes I took this evening right a dusk and half way through I started getting that interlacing method not support thing again..
Raw2cDng seems to be working.. I'm not sure if it's a raw2dng bug or my RAW files?
While looking a some low light work in ACR I'm coming across a lot of blue artifacts.. Any guidance on what causes these and how to avoid them?
Grades from today:
(http://i43.tinypic.com/27yvjbd.png)
(http://i43.tinypic.com/2801pue.png)
(http://i41.tinypic.com/nbq2ph.png)
(http://i40.tinypic.com/289lgmf.png)
Quote from: artiswar on July 23, 2013, 06:58:41 AM
Grades from today:
(http://i43.tinypic.com/27yvjbd.png)
(http://i43.tinypic.com/2801pue.png)
(http://i41.tinypic.com/nbq2ph.png)
(http://i40.tinypic.com/289lgmf.png)
dude! cant wait to see this! looks gorgeous!
@artiswar the upper ones are the original shots right? a question: did you underexpose the images on purpose?
A local festival was on so I shot some video with the 50D using Magic Lantern Raw.
A bit of moire crept in here and there but it's not overly distracting. Also some shots could benefit from de-noising as I may have increased the shadows too much. I'm still trying to optimise my shooting and post workflow.
- Used Tragic Lantern by 1%
- Shot at 1584x892 and upscaled to 1080
- DNG's extracted with RAWMagic 1.0 Beta 7
- Tamron 17-50mm f2.8
Logish grade in ACR, rendered out to Prores 444 and then applied a custom LUT in Resolve with a little sharpening. I might try the Resolve BMD Film workflow next.
Latest Magic Lantern and Tragic Lantern 2.0 builds are up:
Magic Lantern (Unified with raw):- https://bitbucket.org/andy600/andy50d/downloads
Tragic Lantern 2.0:- https://bitbucket.org/andy600/tl50d/downloads
Fixes:-
Raw histogram - Highlight warning dots are back + Small speed-up.
Zebra - minor tweaks
(As ever, check first to see if GregoryOfManhatten has uploaded a newer Unified build before using mine.)
Quote from: rockfallfilms on July 23, 2013, 04:07:02 PM
A local festival was on so I shot some video with the 50D using Magic Lantern Raw.
A bit of moire crept in here and there but it's not overly distracting. Also some shots could benefit from de-noising as I may have increased the shadows too much. I'm still trying to optimise my shooting and post workflow.
- Used Tragic Lantern by 1
- Shot at 1584x892 and upscaled to 1080
- DNG's extracted with RAWMagic 1.0 Beta 7
- Tamron 17-50mm f2.8
Logish grade in ACR, rendered out to Prores 444 and then applied a custom LUT in Resolve with a little sharpening. I might try the Resolve BMD Film workflow next.
Very nice footage looks like it was shot on a Blackmagic Cinema Camera.. The problem with the resolve BMD Film workflow is that Resolve doesn't de-bayer as efficiently as (ACR) I've been testing for a while.
Quote from: goldenchild9to5 on July 23, 2013, 08:36:07 PM
Very nice footage looks like it was shot on a Blackmagic Cinema Camera.. The problem with the resolve BMD Film workflow is that Resolve doesn't de-bayer as efficiently as (ACR) I've been testing for a while.
Cheers for the feedback.
Yeah I did have a go a while back with Resolve and wasn't too impressed but the new version is supposed to be out any day now so I'm hoping they have improved the debayer.
If someone could make a true log film profile for ACR then that would be a start, I've done a close approximation preset but I doubt I'm harnessing all the available DR from the dng, I don't know enough about log curves.
An even better option would be to convert to LOG when doing the initial conversion of the .RAW files and render a proxy too.
How's Cineform's debayer? has anyone given that a thorough testing?
Hey 50D RAW community!
I was the guy who brought up those ugly aliasing+moire pictures some time ago )) and even was referred to as a "moire gang" man )) so I continue to explore into the issue.
Let me tell you I love my ML'ed 50D. But the issue of aliasing (whenever I some fine details / textures fall into the frame) still bothers me. And I try to find ways of workaround.
According to the theory, the problem happens when the fineness of the details in your frame comes close to the distance between the most near pixels. In the case of 50D, it's 0.0140783 mm. Rough (and over-simplified) solution is to blur the image in those small details while keeping larger details intact.
What do I do?
First, I use the aperture values out of the sweet mid spot of a lens. Basically it's either wide open or completely shut.
Secondly, I use some old manual lens (a guy in Ukraine does Canon EF mounts for old Olympus and Minolta lenses) and they lose some sharpness.
Thirdly, I use a stills photography Cokin add-on and insert a cheap Chinese ND2 filter in front of my lenses to lose some sharpness.
There is yet another method -- to de-focus your lens from the area with problematic details.
And I'd like to suggest one tool to make this de-focusing slightly more scientific.
It's a free application for Android that I wrote last winter. It does 2 things:
- calculates DOF (nothing special)
- calculates the degree of blurriness out of DOF
It gives a specific parameter that is called "Min Detail" that shows how much any object is blurred that is out of DOF (that is, de-focused). So whenever you have fine details / fabrics make sure that you take exact focus from that and that Min Detail parameter for that distance is not less than the real size of a detail / pattern unit.
Will not go into detail here more, as I'm not sure if a lot of people will find this usefull...
The app is here: https://play.google.com/store/apps/details?id=net.kadru.dev.visualdof2 (https://play.google.com/store/apps/details?id=net.kadru.dev.visualdof2)
The help info is here http://dev.kadru.net (http://dev.kadru.net)
Quote from: rockfallfilms on July 23, 2013, 08:50:59 PM
Cheers for the feedback.
Yeah I did have a go a while back with Resolve and wasn't too impressed but the new version is supposed to be out any day now so I'm hoping they have improved the debayer.
If someone could make a true log film profile for ACR then that would be a start, I've done a close approximation preset but I doubt I'm harnessing all the available DR from the dng, I don't know enough about log curves.
An even better option would be to convert to LOG when doing the initial conversion of the .RAW files and render a proxy too.
How's Cineform's debayer? has anyone given that a thorough testing?
Glad Resolve is improving on their debayer.. I think your log preset look very nice you should share it with the community. You right it would be awesome if someone can come-up with it right from the .RAW conversion to DNG. Don't know enough info about cineform debayer, not sure how good it is.
Quote from: rommex on July 23, 2013, 09:25:13 PM
Hey 50D RAW community!
I was the guy who brought up those ugly aliasing+moire pictures some time ago )) and even was referred to as a "moire gang" man )) so I continue to explore into the issue.
Let me tell you I love my ML'ed 50D. But the issue of aliasing (whenever I some fine details / textures fall into the frame) still bothers me. And I try to find ways of workaround.
According to the theory, the problem happens when the fineness of the details in your frame comes close to the distance between the most near pixels. In the case of 50D, it's 0.0140783 mm. Rough (and over-simplified) solution is to blur the image in those small details while keeping larger details intact.
What do I do?
First, I use the aperture values out of the sweet mid spot of a lens. Basically it's either wide open or completely shut.
Secondly, I use some old manual lens (a guy in Ukraine does Canon EF mounts for old Olympus and Minolta lenses) and they lose some sharpness.
Thirdly, I use a stills photography Cokin add-on and insert a cheap Chinese ND2 filter in front of my lenses to lose some sharpness.
There is yet another method -- to de-focus your lens from the area with problematic details.
And I'd like to suggest one tool to make this de-focusing slightly more scientific.
It's a free application for Android that I wrote last winter. It does 2 things:
- calculates DOF (nothing special)
- calculates the degree of blurriness out of DOF
It gives a specific parameter that is called "Min Detail" that shows how much any object is blurred that is out of DOF (that is, de-focused). So whenever you have fine details / fabrics make sure that you take exact focus from that and that Min Detail parameter for that distance is not less than the real size of a detail / pattern unit.
Will not go into detail here more, as I'm not sure if a lot of people will find this usefull...
The app is here: https://play.google.com/store/apps/details?id=net.kadru.dev.visualdof2 (https://play.google.com/store/apps/details?id=net.kadru.dev.visualdof2)
The help info is here http://dev.kadru.net (http://dev.kadru.net)
Hey Rommex I feel your pain.. But all I can say about your post is to use a software with the highest debayer process currently right now (ACR) takes the Cake. At first I was going straight into Resolve 9, the results were pretty good but in certain shots the noise, or fringing, aliasing was just too much. If you wanna get better footage from your 50D trust me go (ACR). Ooh by the way I just learned a new trick that gets rid of a lot of the Color Fringing when I tried it I was amazed (UV Filter) yes you heard me right UV filtration without it that's what's causing the fringing. Don't get the cheap kinds, get yourself the Tiffen Haze-2a UV Filter it filtrates 100% of contaminated UV light. Try those two things and post your findings cheers.
Quote from: goldenchild9to5 on July 23, 2013, 10:11:27 PM
...
If you wanna get better footage from your 50D trust me go (ACR).
..... (UV Filter) yes you heard me right UV filtration that's what's causing it. ........
1. Recently I was testing ACR as I read several posts here on the forum about it being better. However, ACR doesn't solve the issue for me as I wished it would.
2. Maybe you mean that a good UV filter can eliminate Chromatic Aberrations, which it could for sure. But Digital (Bayer) color fringing happens when the ray of light has gone past the filter, the glass and hits Bayer pixels. You can't help it but blur
at the length of the inter-pixel distance. That's why low-pass filters exists right in front of the sensor.
Hi,
Looks like shooting in crop mode has little less moire.
Caonon 50mm lens
Magic Lantern Raw - 1080P filmed in zoom / crop mode (exept for evoluon intro clip)
ML build 11th July 2013
Quote from: rommex on July 23, 2013, 10:24:00 PM
1. Recently I was testing ACR as I read several posts here on the forum about it being better. However, ACR doesn't solve the issue for me as I wished it would.
2. Maybe you mean that a good UV filter can eliminate Chromatic Aberrations, which it could for sure. But Digital (Bayer) color fringing happens when the ray of light has gone past the filter, the glass and hits Bayer pixels. You can't help it but blur at the length of the inter-pixel distance. That's why low-pass filters exists right in front of the sensor.
(ACR) is working for me so far getting great results, That Tiffen Haze-2a filter is magic that's all I can say. I'll post some of my results later or tomorrow, also don't forget to check Blackmagic Davinci Resolve 9 latest updates. I think they should be upgrading there Debayer process.
Quote from: jgerstel on July 23, 2013, 10:40:51 PM
Hi,
Looks like shooting in crop mode has little less moire.
Caonon 50mm lens
Magic Lantern Raw - 1080P filmed in zoom / crop mode (exept for evoluon intro clip)
ML build 11th July 2013
Great Job.. very nice
Quote from: rommex on July 23, 2013, 09:25:13 PM
Will not go into detail here more, as I'm not sure if a lot of people will find this usefull...
The app is here...
rommex, please don't get me wrong.
I see a very hard-working community here and read all about the progress regarding the 50D with great pleasure. There are tons of people developing the firmware and it's simply unbelievable what came out so far. And this all because these people work for all of us, taking no money for it and releasing it free of any copyright. ML is absolutely free. But here's the issue that makes me concerned. Without ML, especially the 50D would not be of ANY interest to anyone of us anymore. And i can't believe, that the guys at EOSHD.com don't hesitate to make MONEY with it. Although the progress in developing ML is not made by them, they try to earn money with it.
And so are you. Please, by any means: PLEASE stop trying to make money with this FREE work and respect the hard efforts the developers give even YOU as a GIFT. Try to merchandize and sell your products anywhere. But PLEASE don't do it in this forums. Thank you for your understanding.
Quote from: savale on July 23, 2013, 03:06:08 PM
@artiswar the upper ones are the original shots right? a question: did you underexpose the images on purpose?
Upper shots are originals. I didn't underexpose too much. What you're seeing is a decreased exposure value in DaVinci along with the BMD film preset. Much more flexibility in post to push everything. As long as things don't get too dark and as long as highlights don't clip, with raw you're good.
Quote from: Gekko on July 24, 2013, 01:52:11 AM
rommex, please don't get me wrong.
I see a very hard-working community here and read all about the progress regarding the 50D with great pleasure. There are tons of people developing the firmware and it's simply unbelievable what came out so far. And this all because these people work for all of us, taking no money for it and releasing it free of any copyright. ML is absolutely free. But here's the issue that makes me concerned. Without ML, especially the 50D would not be of ANY interest to anyone of us anymore. And i can't believe, that the guys at EOSHD.com don't hesitate to make MONEY with it. Although the progress in developing ML is not made by them, they try to earn money with it.
And so are you. Please, by any means: PLEASE stop trying to make money with this FREE work and respect the hard efforts the developers give even YOU as a GIFT. Try to merchandize and sell your products anywhere. But PLEASE don't do it in this forums. Thank you for your understanding.
@Gekko - In what way does Rommex's app constitute trying to make money from, through or by Magic Lantern. His app, from what I can see is 1) FREE (he accepts donations) and 2) universally applicable to photography and video makers, regardless of what camera they use.
Though I can appreciate the sentiment, for a first post as a new member, you're not exactly well placed to make such a criticism really.
I was doing some 50d low light exposure research and I found that the 50d has full stop and incremental stop ISO capabilities.. Full stops are mechanical (electrical.. i.e. cleaner) than the incremental stops that interpolated via canon firmware.
I found many complaints about the 50d "low light" and some were saying that if you stick to the "full stops" when setting ISO you'll get the results you'd expect from this level of camera.
So my question is.. How is ML handling ISO settings? When do I have a full stop vs a incremental stop?
In raw you are getting only full stops (you can't get digital gain). Make sure you expose to the right.
@GoldenChild9to5 - Thanks!
@rommex and @Andy600 - Thanks for the tips!
*Actually the last video (page 95) was the June 11th build! Sry about the mix up.
I went and got a few test clips today and I ran into a new problem. Still using June 11th build.
Anamorphic shooting this time. 4:3 Mode. 1280x960. Used RAW2DNG. All the DNG images came out fine.
POST:
Color corrected in ACR. Imported RAW sequence into AE. Resized to 2560x960. Rendered out DNxHD 444 10 Bit. No problems there.
This is a VLC snapshot:
(http://i40.tinypic.com/28aqmvs.jpg)
Then I imported DNXHD clip into PPRO to make a sequence. Rendered to 1080p H264, and got this:
(http://i39.tinypic.com/25jcgzo.png)
I also tried rendering to 1080p MPEG2, Quicktime H264, and 2560x960 DNxHD. I still get a video with those weird white dots the second time I export. Nothing was clipping in the highlights in any of the versions. All scopes in PPRO show everything within a normal range too.
Has anyone else run into this problem?
Quote from: a1ex on July 24, 2013, 07:22:24 AM
In raw you are getting only full stops (you can't get digital gain). Make sure you expose to the right.
Keep up the great work a1ex the development of the cameras are fast, almost everyday something new comes up, I'm so thankful.
Quote from: DJG on July 24, 2013, 07:29:09 AM
@GoldenChild9to5 - Thanks!
@rommex and @Andy600 - Thanks for the tips!
*Actually the last video (page 95) was the June 11th build! Sry about the mix up.
I went and got a few test clips today and I ran into a new problem. Still using June 11th build.
Anamorphic shooting this time. 4:3 Mode. 1280x960. Used RAW2DNG. All the DNG images came out fine.
POST:
Color corrected in ACR. Imported RAW sequence into AE. Resized to 2560x960. Rendered out DNxHD 444 10 Bit. No problems there.
This is a VLC snapshot:
(http://i41.tinypic.com/28s4rrs.jpg)
Then I imported DNXHD clip into PPRO to make a sequence. Rendered to 1080p H264, and got this:
(http://i39.tinypic.com/zx0k84.png)
I also tried rendering to 1080p MPEG2, Quicktime H264, and 2560x960 DNxHD. I still get a video with those weird white dots the second time I export. Nothing was clipping in the highlights in any of the versions. All scopes in PPRO show everything within a normal range too.
Has anyone else run into this problem?
My workflow I don't render out as DNxHD I always render ProRes files, so I'm not sure what would cause such problem. I'll try and replicate your workflow and see if I get the same results.
Quote from: goldenchild9to5 on July 24, 2013, 07:33:34 AM
My workflow I don't render out as DNxHD I always render ProRes files, so I'm not sure what would cause such problem. I'll try and replicate your workflow and see if I get the same results.
Hey I just doubled checked and where the spots were it WAS clipping in ACR. It's strange though. I zoomed in on the ACR it reveled little red dots showing the clipping warning. This wasn't showing in the histogram though or on the normal view. And for some reason the dots didn't show up on that first DNxHD version I rendered from AE and I didn't get any hightlight clipping in any scopes in PPRO (even when zoomed in).
I went back and re-did everything, getting rid of the tiny clipping I could only see zoomed in on ACR. Imported RAW sequence into AE. Exported as DNxHD 444. Imported DNxHD into PPRO. Exported as 1080p H264. Dots gone!
(http://i39.tinypic.com/10x7l1c.png)
Thanks for trying out the workflow if you got around to it. I'd be interested to see if you left any clipping in ACR if you'd end up seeing those dots on any renders. I would render out to Prores too, but I'm on a PC and can't write the files :/
Quote from: artiswar on July 23, 2013, 06:58:41 AM
Grades from today:
(http://i43.tinypic.com/27yvjbd.png)
(http://i43.tinypic.com/2801pue.png)
(http://i41.tinypic.com/nbq2ph.png)
(http://i40.tinypic.com/289lgmf.png)
Looks beautiful! Literally, lol. If you don't mind, when you post the vid, could you describe your workflow? Your images look very smooth and detailed. I always have to de-noise in ACR. And it looks like you're starting with a Log image too?
Quote from: DJG on July 24, 2013, 08:49:35 AM
Looks beautiful! Literally, lol. If you don't mind, when you post the vid, could you describe your workflow? Your images look very smooth and detailed. I always have to de-noise in ACR. And it looks like you're starting with a Log image too?
Will do. I'm not doing ACR at all. Straight RAWMagic into DaVinci with this defringing trick. http://www.magiclantern.fm/forum/index.php?topic=6845.0
What anamorphic lens is that DJD? It makes a lot of sense to go this squeezed route.
@Artiswar - Awesome. More reason for me to learn Resolve, ha.
@djfremen- It's a Kalart Victorcsope. I took a chance and bought one for $150 on ebay and it seems like it's just as good as the 2x Kowa's and Sankors that go for twice or three times as much, imo. It doesn't flare as well as those, but it has a much cleaner image. Kind of like the Panasonic LA7200 except it blurs the video lines nicely. I would recommend it if you can find one. If not, then a Kowa or Sankor is really good for vintage looks (they might be a little sharper too). ML was right on the money adding the 4:3 mode.
Quote from: djfremen on July 24, 2013, 09:16:11 AM
What anamorphic lens is that DJD? It makes a lot of sense to go this squeezed route.
Sorry for the offtopic but could I put one of those anamorphic adapters on my glass (12-24 DX, 28-70 2.8,135 2, 28 1.4) with big front elements of 72-77mm?
I see a lot of people putting these on small m4/3 glass or Russian helios,etc... but I don't have a clue about big lenses. Any cheap recomendation?
some pretty extreme grading:
filmed entirely on the 50D. mirrored, graded and some filters on top...
still trying to get a freeware workflow. this is done @work using creative suite and saphire plug ins.
(after effects+acr+scaling => dnxhd proxies/EXR sequences, edited in premiere with dnxhd proxies. sequence replaced with after effects composition. footage replaced with EXR sequences => grading+FX)
Quote from: crash-film on July 24, 2013, 11:57:44 AM
some pretty extreme grading:
filmed entirely on the 50D. mirrored, graded and some filters on top...
Wasn't that a bit of moire I detect at about 02:0.... (just kidding)
That's quite a piece! I love the effects. I'll be keen to learn more about the tools you used - thanks for any further details you might want to share.
Quote from: araucaria on July 24, 2013, 11:21:11 AM
Sorry for the offtopic but could I put one of those anamorphic adapters on my glass (12-24 DX, 28-70 2.8,135 2, 28 1.4) with big front elements of 72-77mm?
I see a lot of people putting these on small m4/3 glass or Russian helios,etc... but I don't have a clue about big lenses. Any cheap recomendation?
Hi Araucaria,
On an APS camera using a 16mm Anamorphic adapter you can't go any wider than 50mm otherwise you'll get some serious vignetting. Any more than 100mm becomes difficult to focus due to Anamorphic Astigmatism. You could use your 28-70mm in the mid range using a step down ring and a Redstan adapter. Or you could pick up a helios 58mm for £20. Anyway, I'm gonna run before I get in trouble for going off topic! :)
Cheers
Quote from: Supermac on July 24, 2013, 11:12:19 PM
Hi Araucaria,
On an APS camera using a 16mm Anamorphic adapter you can't go any wider than 50mm otherwise you'll get some serious vignetting. Any more than 100mm becomes difficult to focus due to Anamorphic Astigmatism. You could use your 28-70mm in the mid range using a step down ring and a Redstan adapter. Or you could pick up a helios 58mm for £20. Anyway, I'm gonna run before I get in trouble for going off topic! :)
Cheers
That's one thing I would like to see on this forum. A dedicated anamorphic section. It's even more relevant since the introduction of raw and selectable aspect ratios.
Quote from: Andy600 on July 24, 2013, 11:19:43 PM
That's one thing I would like to see on this forum. A dedicated anamorphic section. It's even more relevant since the introduction of raw and selectable aspect ratios.
Anamorphic is very relevant and makes a lot of sense with Raw on the 50d. A 2 x squeeze is a lot less extreme with a squarer frame like 1584 x 1056 for example. I don't have to crop 1080p h.264 to get a more normal aspect ratio like 2.4/2.66. And there's more detail and dynamic range too. Cool!
Took a camping trip to Diamond Lake and got some shots of Crater Lake just a few miles away using 50D Raw. Some good shots, some not so good shots, but hey, still testing.
Great work and impressive videos!
I am always interested in details about posted videos, like build, lens, mm, card, settings etc.
For people interested in anamorphic, have you considered crop mode at something like 1328x1494 up to 1360x1530 with a 2x anamorphic lens?
That would be 16:9 with high resolution and at current maximum bitrate. Vignetting should be less than at 1584x1056 non crop mode. The quality may get higher, but you would get more zoom effect than the non crop mode.
I do not own any anamorphic lens, and would like to know more about them. It would indeed be nice to have that discussion at another thread.
Quote from: rommex on July 23, 2013, 10:24:00 PM
1. Recently I was testing ACR as I read several posts here on the forum about it being better. However, ACR doesn't solve the issue for me as I wished it would.
goldenchild, I take my words back and now have full agreement with your point. I tested ACR against DV Resolve specifically in terms of moire and aliasing -- ACR ROCKS!
UPDATE: a very noobish question: when importing the cDNG sequence to After Effects, is there a waу to see another than the first frame, and make adjustments against it? thnx
Quote from: rommex on July 25, 2013, 03:50:25 PM
goldenchild, I take my words back and now have full agreement with your point. I tested ACR against DV Resolve specifically in terms of moire and aliasing -- ACR ROCKS!
UPDATE: a very noobish question: when importing the cDNG sequence to After Effects, is there a waу to see another than the first frame, and make adjustments against it? thnx
Is there any available format to export from AE that will allow me to utilize the defringing benefits of ACR but still grade in DaVinci with all of the RAW camera options?
http://www.youtube.com/watch?v=Uk_tRCWeND8&feature=youtu.be
GH2 and 50D teaser for a Fstoppers BTS. GH2 was only the aerial shot.
Cool aerial! What flying rig is that?
Quote from: djfremen on July 25, 2013, 10:31:04 PM
Cool aerial! What flying rig is that?
Don't know too much about it besides that it's a cine star 8
Quote from: rommex on July 25, 2013, 03:50:25 PM
goldenchild, I take my words back and now have full agreement with your point. I tested ACR against DV Resolve specifically in terms of moire and aliasing -- ACR ROCKS!
UPDATE: a very noobish question: when importing the cDNG sequence to After Effects, is there a waу to see another than the first frame, and make adjustments against it? thnx
Rommex glad you did proper testing. Davinci is not quite there yet handling DNG's from the Canon's. I was having the same problem with After Effects there might be but not sure, I'm currently using Lightroom 5 man I tell you I'm in love with it should give it a try as well worflow is very optimized. Let me know if you need help with Lightroom 5 Cheers.
GOD Bless
Quote from: artiswar on July 25, 2013, 06:47:44 PM
Is there any available format to export from AE that will allow me to utilize the defringing benefits of ACR but still grade in DaVinci with all of the RAW camera options?
Don't think so Artiswar the only format you can export to edit in Resolve in ProRes, and a couple others. In ACR if you save back a DNG Davinci won't recognize the DNG file and it won't read it.
Quote from: D.L. Watson on July 25, 2013, 11:18:59 AM
Took a camping trip to Diamond Lake and got some shots of Crater Lake just a few miles away using 50D Raw. Some good shots, some not so good shots, but hey, still testing.
Great video..
Quote from: artiswar on July 25, 2013, 07:03:38 PM
http://www.youtube.com/watch?v=Uk_tRCWeND8&feature=youtu.be
GH2 and 50D teaser for a Fstoppers BTS. GH2 was only the aerial shot.
Very nice.. like the grit you put in it (grain, and scratches)
Quote from: goldenchild9to5 on July 26, 2013, 12:38:30 AM
Very nice.. like the grit you put in it (grain, and scratches)
Thank you. Gorilla Grain is killer.
Quote from: goldenchild9to5 on July 26, 2013, 12:32:00 AM
I was having the same problem with After Effects there might be but not sure, I'm currently using Lightroom 5 man I tell you I'm in love with it should give it a try as well worflow is very optimized. Let me know if you need help with Lightroom 5
Would you mind outlining your LR5 workflow - or pointing me to a place where that might already be discussed?
Here is a piece I did as part of the Canon "Long Live Imagination" contest. Shot it all on the Canon 50d in raw. A few1:1 shots in the field at the end..other than that..all at 1580 or whatever because my composition was important and I needed to see what I was recording... Its a shame you cant currently view what is actually being recorded at 1:1 because the image quality is dramatically better. Wanted to test out the lowlight ability of this bad boy and see how it would play in a more professional setting. Hope to use it more soon.
https://www.longliveimagination.com/gallery/video/671
https://vimeo.com/70853696
workflow
ML Raw> RAWMagic> Resolve [converted to BMD Log]> ProRes 4444> Filmconvert> FCPX> Vimeo :)
(http://i958.photobucket.com/albums/ae65/ultramaze/ScreenShot2013-07-26at10003AM.png)(http://i958.photobucket.com/albums/ae65/ultramaze/ScreenShot2013-07-26at10654AM.png)(http://i958.photobucket.com/albums/ae65/ultramaze/ScreenShot2013-07-26at10411AM.png)(http://i958.photobucket.com/albums/ae65/ultramaze/ScreenShot2013-07-26at10702AM.png)
Shot the moon this evening. It was so big! I took the raw video 10 mins after it showed itself above the horizon.
Quote from: ultramaze on July 26, 2013, 08:04:47 AM
Here is a piece I did as part of the Canon "Long Live Imagination" contest. Shot it all on the Canon 50d in raw. A few1:1 shots in the field at the end..other than that..all at 1580 or whatever because my composition was important and I needed to see what I was recording... Its a shame you cant currently view what is actually being recorded at 1:1 because the image quality is dramatically better. Wanted to test out the lowlight ability of this bad boy and see how it would play in a more professional setting. Hope to use it more soon.
https://www.longliveimagination.com/gallery/video/671
https://vimeo.com/70853696
workflow
ML Raw> RAWMagic> Resolve [converted to BMD Log]> ProRes 4444> Filmconvert> FCPX> Vimeo :)
great shots, but noise is at an insane level!
I can see it even in daylight shots :(
which were the settings of the camera?
Quote from: riccardocovino on July 26, 2013, 10:51:46 AM
...noise is at an insane level!
I can see it even in daylight shots :(
which were the settings of the camera?
If you're getting noise in daylight shots you're either seriously underexposing or your ISO is set very high. Use the raw histogram and expose to the right.
Quote from: Andy600 on July 26, 2013, 12:06:34 PM
If you're getting noise in daylight shots you're either seriously underexposing or your ISO is set very high. Use the raw histogram and expose to the right.
I'm talking about HIS video (ultramaze's)
https://vimeo.com/70853696
did you see it? noise is worse than with my 200$ mobile..
I don't think he put an ND filter un daylight so strong to raise ISO to 6400 or whatever, it would be quite absurd!
I'm even wondering if such noise is added in post.
indoor shots are clearly in low light condition but there the noise is totally unacceptable, way beyond lowest expectations.
That's why I asked about his camera settings, and his Davicni workflow would be interesting too.
Sorry Riccardo, I misunderstood what you wrote previously.
Yes, I agree. The video is very dark and noisy. Maybe it was an intentional look and noise was added in post? but it still looks very underexposed to me. It could also be down to an uncalibrated monitor when grading.
Quote from: rommex on July 22, 2013, 10:20:52 AM
Nice video.
Try using Raw2CDNG. It does work with files longer than 4GB.
You first rename split files (so that they have extensions .001, .002, etc) and then use the free program File Splitter & Joiner to join them.
Then you feed the resulting files to Raw2CDNG -- it should work. It worked for me.
UPDATED: also I had been a fan of 28 May Build for long since it was stable and firm as a rock. Now I use Andy's new build and I would encourage you to try it -- you'll like it as well -- PINK frames are a history :) :
http://www.magiclantern.fm/forum/index.php?topic=5586.msg59779#msg59779
Hey Rommex, are you using Raw2CDNG on a PC? It doesn't seem to be working for me, ver.1.2.1. I joined a split file and now have 4.95GB file I load into RAW2CDNG, but I get an error "RAW2CDNG has stopped working" every time. RAW2CDNG also is showing under Resolution: 4385 and FPS: 555512.80. Basically weird numbers.
Do you or anyone else know of any other conversion methods on a PC that can handle files over 4GB?
*Also, how do you enable RAW recording on the above build you linked me to? Thanks :)
Filmed 1920 x 818, 64gb komputerbay, duration looks continuous & stable. However format CF card so now & then to keep card fast.
Camera: Canon 50D
Caonon 50mm lens
ML build 11th July 2013
Quote from: dhallowell19 on July 26, 2013, 04:51:54 AM
Would you mind outlining your LR5 workflow - or pointing me to a place where that might already be discussed?
Do you have LR5? If you do here is one of the videos that I used to get familiar with LR interface and the way it catalog files, it uses ACR same as photoshop, and after effects but just cosmetic changes 8). https://vimeo.com/70637970 (https://vimeo.com/70637970) Will be posting a video today showcasing what I've done using LightRooms workflow. If you have any other question regarding LR5 let me know.. Hope that helps cheers.
GOD Bless
The Canyon - Shot during a two hour trip to the canyon
For this video, I shot with a faster CF Card (100 MBS) that gave me 1344 X 1008 resolution at 24 FPS in 4:3 mode without skipping frames. I could shoot for at least 6 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 2688 X 1008 in Compressor.
Anyone else shooting anamorphic on the 50D in 4:3? Can anyone shoot higher resolution than 1344 X 1008? Thank you.
Shot RAW on the 5DM3 and 50D using the Magic Lantern Hack. The 5DM3 was shot at 1920x1038 (1.85). The 50D was shot at 1920x1038 resolution in cropped mode to match the 5D. A pair of 64GB 1000X KomputerBay CF cards were used for the shoot. The ratio of 5D/50D is approximately 60/40. Can you tell which shots are which?
https://vimeo.com/71108800
The RAW files were converted to dng sequences with Rawanizer ver 0.5.5. DNxHD proxies were used to edit the footage in Adobe Premiere CC. Once edited, the sequence was brought into Adobe After Effects CC via Dynamic Link and the proxies were replaced with the RAW footage. First light color correction was done in ACR, and additional corrections were performed in AE. All compositing was performed within AE. Gorilla Grain was added to the final output.
Quote from: DJG on July 26, 2013, 01:52:12 PM
Hey Rommex, are you using Raw2CDNG on a PC? It doesn't seem to be working for me, ver.1.2.1. I joined a split file and now have 4.95GB file I load into RAW2CDNG, but I get an error "RAW2CDNG has stopped working" every time. RAW2CDNG also is showing under Resolution: 4385 and FPS: 555512.80. Basically weird numbers.
Do you or anyone else know of any other conversion methods on a PC that can handle files over 4GB?
*Also, how do you enable RAW recording on the above build you linked me to? Thanks :)
Hello there,
Yes I use Raw2CDNG, I have version 1.1.6 on my PC. It does not join the split files, as someone here suggested some time ago -- I assume it's a newer version that does. So first I join them manually by a File Splitter & Joiner, and then submit it to Raw2CDNG. Today I did that 3 times. One resulted sequence was failed -- full of pink rubbish. I just repeated the joining and converting -- it worked fine this time.
RAW mode: you turn on the RAW_REC module, then you enable RAW record in the menu. It's all done while LiveView is ON. I hope there are some detailed instructions at the top of this thread, the bloody manual that should be read, so to speak 8)
Quote from: DJG on July 26, 2013, 01:52:12 PM
Hey Rommex, are you using Raw2CDNG on a PC? It doesn't seem to be working for me, ver.1.2.1. I joined a split file and now have 4.95GB file I load into RAW2CDNG, but I get an error "RAW2CDNG has stopped working" every time. RAW2CDNG also is showing under Resolution: 4385 and FPS: 555512.80. Basically weird numbers.
Do you or anyone else know of any other conversion methods on a PC that can handle files over 4GB?
*Also, how do you enable RAW recording on the above build you linked me to? Thanks :)
I've been using Rawanizer and it's been working fine automatically stitching spanned files.
Quote from: jgerstel on July 26, 2013, 04:46:35 PM
Filmed 1920 x 818, 64gb komputerbay, duration looks continuous & stable. However format CF card so now & then to keep card fast.
Camera: Canon 50D
Caonon 50mm lens
ML build 11th July 2013
Does the 50D shoot 1920 x 818 in full sensor mode or do you have to use cropped mode to retain such high resolutions?
Quote from: rommex on July 25, 2013, 03:50:25 PM
goldenchild, I take my words back and now have full agreement with your point. I tested ACR against DV Resolve specifically in terms of moire and aliasing -- ACR ROCKS!
UPDATE: a very noobish question: when importing the cDNG sequence to After Effects, is there a waу to see another than the first frame, and make adjustments against it? thnx
I'd be interested in this too, I guess it's because ACR is designed for stills? Only thing I can think of is to import individual tiff's and remember the settings. Bit of a pain though.
I've been working with an ACR workflow (because I don't have a computer that runs resolve) and the way I do it is
1 - Open the whole sequence in ACR
2 - Make whatever changes I need to get a super flat file
3 - Save images as either JPGs or TIFFs
4 - Open the saved jpg/tif image sequence in Quicktime 7 Pro
5 - Export form Quicktime 7 Pro to a Prores 422 HQ movie
You can use Lightroom instead of ACR (the raw processing engine is the same), and you can use something other than Quicktime 7 Pro to convert image sequences to video. In my early testing I was using Cineform Studio Premium to convert image sequences to Cineform RAW, but I decided against it because the OSX version is nowhere near as good as the Windows version (I'm mac based).
I find that RAW > ACR > JPG > QT7 > Prores422 is faster than importing the raw sequence into After Effects and rendering a Prores422 file, but it may not be for you. I have also found that exporting a 16bit TIFF instead of an 8bit JPG takes about the same time, so if you really want to preserve every little bit of information and you don't mind the huge amount of space it'll use up that could be a good workflow. Once I convert to prores I delete the exported jpgs.
Here's a test I shot a couple of weeks ago using this method:
https://vimeo.com/69413995
Hey jhnkng, thanks for the description!
I come from the world of photography and i'm a bloody noob regarding film, so i've a couple of questions:
- What exactly is the advantage of converting the sequence to Prores 422?
- Which tools take a benefit of prores 422 instead of using a raw-sequence?
- And what do you mean exactly with "get a super flat file"...do you mean flat in terms of flatten the color & contrast or flat in terms of file size?
Thanks for an answer,
Gekko
Quote from: Supermac on July 26, 2013, 11:03:42 PM
I'd be interested in this too, I guess it's because ACR is designed for stills? Only thing I can think of is to import individual tiff's and remember the settings. Bit of a pain though.
(https://lh4.googleusercontent.com/-hK53ToKutfI/UfOctvHikfI/AAAAAAAACJg/7nt6-l4S_Wc/s1024/acr.jpg)
You don't have to remember the settings: there is an options panel where you find the option to give the picture the settings applied to the last picture you worked with. (i suppose in english "former conversion")
Quote from: Gekko on July 27, 2013, 05:56:42 AM
Hey jhnkng, thanks for the description!
I come from the world of photography and i'm a bloody noob regarding film, so i've a couple of questions:
- What exactly is the advantage of converting the sequence to Prores 422?
- Which tools take a benefit of prores 422 instead of using a raw-sequence?
- And what do you mean exactly with "get a super flat file"...do you mean flat in terms of flatten the color & contrast or flat in terms of file size?
Thanks for an answer,
Gekko
Hi Gekko, I'm a photographer too, and all this is new for me as well! Perhaps if there are things that I'm doing that's not quite right someone more knowledgeable could chime in?
From what I understand the basic Resolve workflow is to import raw sequence, generate proxy files (basically jpg previews in stills) that go into your editing program, and once its edited it you bring the edit metadata (the sequence of files, the in and out points etc) back into Resolve which will then let you grade and export the final high res video. Because I don't use Resolve, and because I don't need to do any serious grading, I figure having a high quality Prores file that I can edit and grade without having to do a round trip will be faster and easier.
So to do this I open the DNG files in ACR, set my white balance and exposure, lower the contrast, add shadow detail, pull down the highlights, and that generally gives me a flat, low contrast look. Once I get the prores files into Premiere I find I can use one of the preset Lumetri LUTs included in the latest version of Premiere and it gives me a nice looking file. And then it's just a matter of editing and grading for the mood, and I can do all that in Premiere using a combination of Colorista and the Lumetri presets. I'm slowing looking at Speedgrade and trying to get my head around that, but to be frank my interest is in directing and writing, so right now I'm all about learning just enough to produce good work, building my chops and moving onto bigger projects where I could use a proper editor and colourist, because each of those fields are artforms unto their own.
I hope that helps a little bit mate!
Quote from: jhnkng on July 27, 2013, 12:27:00 PM
I hope that helps a little bit mate!
Much more than you might think!
Thanks alot for the details!
:)
Quote from: pags on July 26, 2013, 10:38:24 PM
Does the 50D shoot 1920 x 818 in full sensor mode or do you have to use cropped mode to retain such high resolutions?
Hi
This is filmed in crop mode, 50 mm lens. Full sensor goes only to 1584 width. However using a anamorphic lens works very well in full sensor mode. 1344 x 1058 works continuous.
Quote from: pinger007 on July 26, 2013, 07:57:21 PM
Shot RAW on the 5DM3 and 50D using the Magic Lantern Hack. The 5DM3 was shot at 1920x1038 (1.85). The 50D was shot at 1920x1038 resolution in cropped mode to match the 5D. A pair of 64GB 1000X KomputerBay CF cards were used for the shoot. The ratio of 5D/50D is approximately 60/40. Can you tell which shots are which?
https://vimeo.com/71108800
The RAW files were converted to dng sequences with Rawanizer ver 0.5.5. DNxHD proxies were used to edit the footage in Adobe Premiere CC. Once edited, the sequence was brought into Adobe After Effects CC via Dynamic Link and the proxies were replaced with the RAW footage. First light color correction was done in ACR, and additional corrections were performed in AE. All compositing was performed within AE. Gorilla Grain was added to the final output.
Very nice 8)
Quote from: pinger007 on July 26, 2013, 07:57:21 PM
The RAW files were converted to dng sequences with Rawanizer ver 0.5.5. DNxHD proxies were used to edit the footage in Adobe Premiere CC. Once edited, the sequence was brought into Adobe After Effects CC via Dynamic Link and the proxies were replaced with the RAW footage. First light color correction was done in ACR, and additional corrections were performed in AE. All compositing was performed within AE. Gorilla Grain was added to the final output.
this is exactly the workflow i´m using now too.
first i saved the proxies by importing the dng´s straight into premiere. but the ginger plug in only works for 30 days for free....
but i´m using then EXR files in after effects and set the dnxhd files as proxy files. this can help with slower computers. for me it is the same speed.
i wrote a step by step guide on using this method. but it is outdated because of the ginger plug in issue and the slow dng performance.
what i noticed is, albeit using 32 bit floating point EXR files it is still crucial to "develop" the dngs in ACR correctly. trying to tune the exposure with colorista sort of works, but comes not even close to the exposure control possible with ACR.
i use the EXR sequences, because they process roughly 400 to 600 percent faster (depending on filters, masks, layering....etc). reducing rendertime (for my last 4 minute clip) from nearly 18 h to 6 h....
and i can use the sequences in my favourite comp software: nuke. nuke is highly optimized for 32 bit EXRs.
and yes, working in raw is a real pain.
if you plan just to edit your footage and then grade it in AE. you can stick with the dng workflow. you replace the footage, grade, adjust....hit the render button and go to bed... you can even save rendertime by adding more than one output file format in AEs render queue per comp. ( image sequence + your proxy format )
AE compositions can be rendered in the media encoder offering a much broader output file format (AE does h264 but you can´t adjust the settings.... or i am just blind...)
if you plan to add a lot of compositing to your images, then the EXR workflow is your first choice. ( or tiffs, if you wish )
the RAW dng sequences can be zipped, reducing disk space by about 25%.
what are your strategies for archiving?
i plan to save the uncut clips as dnxhd 10bit
and one consolidated AE project with only the used dngs, to reduce data amount and then zipping it in one archive file.
ah yes and the above mentioned "filmconverter" is a AE plug in, that adds not only film stock specific color tone and exposure response, but also the corresponding grain. within it you can choose different film sizes ( from 8 mm to 35 mm full frame ). this setting influences the grain size dramatically. never go under super 16 mm.
you don´t really need such filters. the grain from the 50d files is very filmic and the special film stock looks can be achieved by simple color correction and a little bit channel blurring and maybe a glow.....
Quote from: rommex on July 25, 2013, 03:50:25 PM
goldenchild, I take my words back and now have full agreement with your point. I tested ACR against DV Resolve specifically in terms of moire and aliasing -- ACR ROCKS!
UPDATE: a very noobish question: when importing the cDNG sequence to After Effects, is there a waу to see another than the first frame, and make adjustments against it? thnx
This is how I do it:
- In AE project window right click the dng and choose 'Reveal in Bridge'
- In Bridge, select all thumbnails then choose File/open in camera raw
- Make changes to your favourite frame then click synchronise
- Click Done
- Back in AE right click on the dng in the project window and choose 'reload footage'
Your changes will now be viewable in AE.
If you have a lot of clips which are going to need similar corrections then you could save a preset when in adobe bridge/camera raw then just load that preset into AE.
There might be an easier way but I haven't found it yet.
Hows it going guys, first time poster!!!!1!1
But all stupidity aside I would like to take the chance to thank everyone for their tireless contributions towards this effort. It is needless to say that the RAW capabilities and simply the ability to record h.264 compressed video on the 50D has opened doors for budding Videographers Northwest wide and abroad. Doors that certainly not even Black Magic Cinema cameras could open within this price range.
So all the lovey dovey stuff aside I wish the contributors and founders of ML Firmware a bright future hopefully exempt of Canon intervention.
So, lets get to bidness.
Before I go into depth about my findings and questions I will just share my current set-up as to avoid any possible confusion.
Unified ML Build: Magic Lantern v2.3.
Secondary Build: Tragic Lantern Andy600 Build July,23,2013
CF Card: Lexar Professional UDMA7 32GB 1000x
For those interested I have benched this card both in-camera as well as on a USB3.0 CF card reader and have an average median of 82mb/s allowing continuous recording of all full sensor aspect ratios/resolutions.
To auto-boot ML I used the latest build of EOSCard.
So for the past 2 days or so I have been migrating, optimizing, and experimenting with the new options available within Tragic Lantern. Most the standard stuff I am already accustomed to as I have been using the unified builds for my 600D for some time now. So today I got the chance to go out and record some test footage and kind of perform a "mock" shoot to see if I could still perform under a professional level using this build, it's UI, and operational effectiveness.
So from the day I spent with it I have compiled a few absolute pointers for those wishing to use this camera and firmware in a professional setting, as well as a few questions and inquiries.
These are a few little tips I have compiled that I strongly recommend are followed for a streamlined shoot and archive scenario:
1. At minimum I recommend having one 64GB 1000x CF card from a reputable producer such as Lexar or Hoodman, However for a few less dollars you can always try the Komputerbay 1000x "Slot Machine" CF Cards. But if you plan on shooting anything more than 8-12 minutes long your left with only 2 options, either have a laptop on-sight for offloading one card whilst you shoot on another or purchase 128GB 1000x CF cards from the dealers I stated before; as 128GB komputerbay cards have been known to falter in sufficient write speeds. Always remember to make a secondary backup of your files on-sight for paid work!
2. This brings me to my second point, it is highly preferable to have USB3.0 ports as well as a 3.0 CF card reader(s) on-sight for file transferring; especially if you only have one card to work with. To put this into perspective on a USB2.0 based system and generic USB2.0 CF card reader a 32GB card brimmed with RAW files will average a transfer rate of 13-19mb/s meaning a nearly 30 minute transfer time. Definitely not professional when you have actors and other staff waiting around for a green bar to finish it sluggish race to the end of the screen.
3. I am not sure if this is entirely isolated to me or maybe its just common and I have not picked up on it yet but the 50D when recording RAW video especially eats through batteries like there is no tomorrow. I am averaging roughly 10-14 minutes of battery life even when putting all of the energy saving tactics to use. Maybe the previous owner of this camera did not fully charge and discharge his battery? Or maybe the camera just does that. Feel free to correct me if I have made a mistake but otherwise you can never have enough batteries for this camera for those long 3-4 hour shoots.
4. Also, just be wary of how many modules you have running during the recording phase. As I have found that certain modules more than others can severely bog the CPU down causing the LV cycles to be slower as well as slow you cumulative writing speeds preventing certain resolutions from being captured that your card normally could write continuous.
Now for the questions,
One problem I ran into today repeatedly was the ability to ficus accurately manually using LV, Focus Peaking, and the Zoom Box for assisting focus. This was even more the case when I converted the raw files on my computer only to find that half of my shots were blatantly out of focus. This coupled with the fact that the 50D LCD screen does not swivel and even on maximum brightness still gets easily drowned out by direct sunlight. So naturally I tried using the LV AF but to zero response from the camera. Has anyone here had any experience with this issue? And if so have you been able to develop a operational fix for getting the AF operational?
And as a side note I found that the focus peaking module was overall the most effective tool for visually confirming focus. However it is VERY taxing on the camera even in low-res sampling mode and requires to be manually shut off every-time I begin shooting consuming valuable time in the process. If there is any chance the option to hide or essentially temporarily disable this module whilst recording could be added it would be incredibly useful. Unless there already exists some method...
And finally I know AC/DC converters exist for the 50D but has anyone seen a corded external battery pack? Essentially they are of the same construction as the corded AC/DC converters however instead of using a car-jack or 120 plug it is just a large battery cell obviously much larger than the standard pack. I wish I could give a better description but honestly I have been awake for 2 days straight and this is as cohesive as it gets.
Thanks for any and all responses,
-Daen
Slug on my Clematis vine.
Quote from: Daen The Scamp on July 27, 2013, 03:42:58 PM
Now for the questions,
One problem I ran into today repeatedly was the ability to ficus accurately manually using LV, Focus Peaking, and the Zoom Box for assisting focus. This was even more the case when I converted the raw files on my computer only to find that half of my shots were blatantly out of focus. This coupled with the fact that the 50D LCD screen does not swivel and even on maximum brightness still gets easily drowned out by direct sunlight. So naturally I tried using the LV AF but to zero response from the camera. Has anyone here had any experience with this issue? And if so have you been able to develop a operational fix for getting the AF operational?
And as a side note I found that the focus peaking module was overall the most effective tool for visually confirming focus. However it is VERY taxing on the camera even in low-res sampling mode and requires to be manually shut off every-time I begin shooting consuming valuable time in the process. If there is any chance the option to hide or essentially temporarily disable this module whilst recording could be added it would be incredibly useful. Unless there already exists some method...
Thanks for any and all responses,
-Daen
I have not used AF since I installed ML.
For strong light, get a LCD Viewfinder. Most have a bit of magnification, which is nice.
Focus peaking is amazing, but I too disable when I shoot. To save a few valuable seconds while shooting, set up LV Display Presets. Quickly toggle LV overlays just by pressing INFO. I have one set up with No Overlays (recording 1080), one with just RAW Histogram (full frame shooting), and one with all my desired overlays (for setting up my shot).
http://www.magiclantern.fm/forum/index.php?topic=1729.0 (http://www.magiclantern.fm/forum/index.php?topic=1729.0)
Also, turn on Cartoon Mode 1 under Creative Effects in the Movie tab to sharpen edges on display, which are not saved to RAW Video file. When you have Focus Peaking off while recording, this serves as a slight improvement over No Overlays.
Edit Also, what lens are you using that is giving you so much trouble focusing manually?
Quote from: pinger007 on July 26, 2013, 07:57:21 PM
Shot RAW on the 5DM3 and 50D using the Magic Lantern Hack. The 5DM3 was shot at 1920x1038 (1.85). The 50D was shot at 1920x1038 resolution in cropped mode to match the 5D. A pair of 64GB 1000X KomputerBay CF cards were used for the shoot. The ratio of 5D/50D is approximately 60/40. Can you tell which shots are which?
https://vimeo.com/71108800
The RAW files were converted to dng sequences with Rawanizer ver 0.5.5. DNxHD proxies were used to edit the footage in Adobe Premiere CC. Once edited, the sequence was brought into Adobe After Effects CC via Dynamic Link and the proxies were replaced with the RAW footage. First light color correction was done in ACR, and additional corrections were performed in AE. All compositing was performed within AE. Gorilla Grain was added to the final output.
Very nice video :D With what you did the fireworks??
Not exactly on topic, but I'm trying to learn 50D movie recording using the old non-RAW (compressed 1080p) video hack, which produces MOV files. If anyone here did shoot video this style - what is your workflow? I have an external recorder (Zoom H1), so the workflow should include a way to demux MOV into h264, sync it with external WAV audio, and mux it into something like MKV or M2TS. Is there a tutorial somewhere which would explain every step? Also, may be there is a tutorial on shooting non-RAW video with 50D - what settings to use (like, picture profiles etc.) and how?
Finally - it is probably impossible, but perhaps there is a way to join compressed video produced by 50D (which is 1080/30p h264) with the output of my Canon HD camcorder, which produces 1080/60i h264 - without recoding? I think there are containers out there which allow video stream to switch frame rates, interlacing and non-interlacing, in the middle of the stream. May be MKV can do that? Which video tool would let me join non matching frame rate files? I tried a few (AVdemux, tsMuxerGUI etc.) but it doesn't work.
Quote from: DJG on July 26, 2013, 01:52:12 PM
Hey Rommex, are you using Raw2CDNG on a PC? It doesn't seem to be working for me, ver.1.2.1. I joined a split file and now have 4.95GB file I load into RAW2CDNG, but I get an error "RAW2CDNG has stopped working" every time. RAW2CDNG also is showing under Resolution: 4385 and FPS: 555512.80. Basically weird numbers.
Did you read my post a few posts after Rommex'es post? Maybe it will work for you: http://www.magiclantern.fm/forum/index.php?topic=5586.msg61023#msg61023
beautiful
Quote from: Andy600 on May 25, 2013, 09:28:37 PM
It seems a possibility but the whole 40d port needs resurrecting by someone.
One day our dream will become a reality .... :)
I have not given up! Soon, I'll try to compile ML for 40D.
I'm predicting some difficulties ... The development team is unstoppable.
I'm amazed at the amount of changes that exist in the source code.
Loving the hack for the 50d - all glories to those who have developed it! For some reason in different shots in this vid I am getting strong cyan and pinky color coming through. Perhaps it is my camera?
Another macro videography! This time, there was good light. ISO was at 200.
Quote from: riccardocovino on July 26, 2013, 10:51:46 AM
great shots, but noise is at an insane level!
I can see it even in daylight shots :(
which were the settings of the camera?
it was intentional. added it in post with film convert.
Quote from: Andy600 on July 26, 2013, 12:06:34 PM
If you're getting noise in daylight shots you're either seriously underexposing or your ISO is set very high. Use the raw histogram and expose to the right.
it was intentional. added it in film convert
Quote from: Andy600 on July 26, 2013, 12:29:28 PM
Sorry Riccardo, I misunderstood what you wrote previously.
Yes, I agree. The video is very dark and noisy. Maybe it was an intentional look and noise was added in post? but it still looks very underexposed to me. It could also be down to an uncalibrated monitor when grading.
much of what i shot was cranked to the highest iso settings and noise was added in post.
My lastest test with the 50D Loving it ;D refining my workflow gearing-up for a video shoot..
Shot on a Canon 50D with Magic Lantern Raw Hack. (Thank you ML)
Hack Build: 1% - Andy600 (Tragic 2) it's a wonderful build.
All shot @ max resolution (1584 x 896)
Global Draw: On (Waveform, Zebra, Histogram)
Small Hack: On
CF Card: Komputerbay 64gb 1000X
Lens: Vintage Nikon 50mm f1.8 Series E
Post WorkFlow: RawMagic - LightRoom 5 to .tiff sequences - Imported into QuickTime 7 Pro exported to ProRes 422 - Imported in Premiere Pro CS6 quick edit & finally used plugin (FilmConvert) to add grain and a little bit of film color. Image is a little shaky because it was shot all handheld, it was a quick test preparing myself for a major shoot for next month.
I seem to be having issue on the July 16 build on one of my 2 KomputerBay cards. Midway through a recording, the shutter speed will drop from 1/48 to 1/84. I have FPS override on and at exact framerate for 23.976.
Quote from: goldenchild9to5 on July 28, 2013, 08:47:04 PM
My lastest test with the 50D Loving it ;D refining my workflow gearing-up for a video shoot..
Shot on a Canon 50D with Magic Lantern Raw Hack. (Thank you ML)
Hack Build: 1% - Andy600 (Tragic 2) it's a wonderful build.
All shot @ max resolution (1584 x 896)
Global Draw: On (Waveform, Zebra, Histogram)
Small Hack: On
CF Card: Komputerbay 64gb 1000X
Lens: Vintage Nikon 50mm f1.8 Series E
Post WorkFlow: RawMagic - LightRoom 5 to .tiff sequences - Imported into QuickTime 7 Pro exported to ProRes 422 - Imported in Premiere Pro CS6 quick edit & finally used plugin (FilmConvert) to add grain and a little bit of film color. Image is a little shaky because it was shot all handheld, it was a quick test preparing myself for a major shoot for next month.
Nice shoot and nice music! Good luke with the video :D
Quote from: artiswar on July 28, 2013, 11:47:16 PM
I seem to be having issue on the July 16 build on one of my 2 KomputerBay cards. Midway through a recording, the shutter speed will drop from 1/48 to 1/84. I have FPS override on and at exact framerate for 23.976.
Artiswar you talking about (Tragic 2) ? if it is I haven't had any problems with it yet. I think the problem stems from using ETTR, everytime I use it my shutter changes automatically & @ times It drops to 1 and locks so I have to reboot the camera. Also on my camera when Liveview is not (On) my shutter always on 1/84, so I'm thinking that something is switching your liveview (On & Off) Report back let me know if you got it fixed Cheers.
GOD Bless
Quote from: arrinkiiii on July 29, 2013, 12:50:57 AM
Nice shoot and nice music! Good luke with the video :D
Thank you ArrinKiiii appreciate it I'm getting more and more comfortable shooting Raw with the 50D, got a couple more hurtles to jump but I'll get there. The song is called "SuperStar" if your wondering, it's a single that I produced for American Idols Top 24 singer "Ashley Robles" she's amazing. I'll keep you & the forum updated on the shoot for my upcoming (EDM) project.
GOD Bless
Quote from: goldenchild9to5 on July 29, 2013, 01:36:26 AM
Thank you ArrinKiiii appreciate it I'm getting more and more comfortable shooting Raw with the 50D, got a couple more hurtles to jump but I'll get there. The song is called "SuperStar" if your wondering, it's a single that I produced for American Idols Top 24 singer "Ashley Robles" she's amazing. I'll keep you & the forum updated on the shoot for my upcoming (EDM) project.
GOD Bless
God bless you to.
Yes, good track and good singer. Please, keep us updated with your next video... if possible with a BTS ;D
Quote from: arrinkiiii on July 29, 2013, 01:46:12 AM
God bless you to.
Yes, good track and good singer. Please, keep us updated with your next video... if possible with a BTS ;D
I sure will.. 8)
Lads, I still get the zebra thing. I use histogram, but even thou sometimes overexposed areas must appear and I'm down. I tried resetting factory settings, reinstalling ML, bu no good. Of course global draw is off.
Dng frame:
http://speedy.sh/5k7B8/DNGM20-1508-000093.dng
Raw file:
http://speedy.sh/xth3q/1508.RAW
(http://s9.postimg.org/59hd134wv/DNGM25_2000_000038.jpg)
(http://s9.postimg.org/am67f7stb/image.jpg)
Quote from: mjstudio on July 29, 2013, 10:52:56 AM
Lads, I still get the zebra thing. I use histogram, but even thou sometimes overexposed areas must appear and I'm down. I tried resetting factory settings, reinstalling ML, bu no good. Of course global draw is off.
It's your conversion routine that's the problem. I just downloaded your dng and get the same issue but I also downloaded your raw file and converted with BATCHelor (v3). The issue goes away.
(http://i.imgbox.com/ach4x29w.jpg)
Quote from: ultramaze on July 28, 2013, 11:34:09 AM
it was intentional. added it in post with film convert.
ahh ok.. so your video is not a quality test but an artistic maniulation, understood.
Quote from: Supermac on July 26, 2013, 10:10:29 PM
I've been using Rawanizer and it's been working fine automatically stitching spanned files.
Thanks! Rawanizer is doing the trick perfectly for me on a PC.
Quote from: Andy600 on July 29, 2013, 11:20:41 AM
It's your conversion routine that's the problem. I just downloaded your dng and get the same issue but I also downloaded your raw file and converted with BATCHelor (v3). The issue goes away.
sweet lord Jesus, you saved my ass!
many many thanks!
Is ETTR still not working one the 50D with raw video?
I've been shooting in crop mode and noise is really a problem, don't even think of iso 200 unless you can severly overexpose, that's why I'm asking. It's a pain in the ass having to turn historgrams on and off before everyshot. Turning off automaticly globaldraw would help a lot,too. Maybe this is already implemented and I haven't noticed.
@arrinkiiii
The fireworks were done in After Effects using a mix of Red Giant's Particular and some of Video Copilot's Action Essentials II for the smoke effects. I used a mix of Chroma Key and rotoscoping to mask the fireworks to the sky.
https://vimeo.com/71108800
Glad you enjoyed it.
Curious question I just thought about.
Would shooting with a 'flat' color profile on top of the Raw video help the grading process instead of shooting the Raw with the default profile, then making it flat via ACR or BMD Film on Resolve?
Quote from: araucaria on July 30, 2013, 01:01:42 AM
Is ETTR still not working one the 50D with raw video?
I've been shooting in crop mode and noise is really a problem, don't even think of iso 200 unless you can severly overexpose, that's why I'm asking. It's a pain in the ass having to turn historgrams on and off before everyshot. Turning off automaticly globaldraw would help a lot,too. Maybe this is already implemented and I haven't noticed.
It's working but not as we would hope for because it's mainly was designed for Picture shooting from what I've read from sources like @Andy600 & @1% . You are not alone noise is really making it hard for me to shoot in low light it's just an overwhelming amount of noise. your right ISO 100 / 200 are way too noisy. I was messing around with some 5D Mark II footage.. the noise is way way less than on the 50D. I know the 50D was not even designed to shot video, and now having it shoot Raw is incredible, but there is something about shooting Raw that brings overwhelming amount of noise. My thing is we have to use it for what it is & make the best out of it 8)
If you are shooting low light scenes at ISO 100/200 you will of course get noise because you will need to boost exposure a lot in post just to get the mids into anything like a useable place. You wouldn't do that for stills, you would increase ISO which increases the light sensitivity of the camera and the same applies for raw video.
Don't be afraid to shoot at higher ISO values and let the camera do what it was designed to do. There will still be noise but it's not too bad and can be cleaned up in post. I've had nice looking shots at ISO 3200+ where the noise looked quite nice (especially when just the chroma noise was removed in post).
The 5D MkII's sensor is a lot more sensitive than the 50D so low light performance will be better but the 50D is still useable at higher ISOs. You just need to experiment ;)
@Araucaria - Tragic Lantern has a feature to auto-disable Global Draw when you hit record. You should be able to shoot with the histogram on without a big hit to performance. ETTR is a method of shooting. If you are referring to the auto-ETTR module, yes, it does work in the 50D but you shouldn't use it for video. Expose with the raw histogram.
Quote from: fromdecember on July 30, 2013, 09:02:57 PM
Curious question I just thought about.
Would shooting with a 'flat' color profile on top of the Raw video help the grading process instead of shooting the Raw with the default profile, then making it flat via ACR or BMD Film on Resolve?
Raw is raw. There is no picture style. It's raw sensor data ::)
You can apply whatever curve, LUT or look you want in post.
"Mirror Lake" Canon 50D Raw Anamorphic - 4:3 at 1344 X 1008
For this video, I shot with a faster CF Card (100 MBS) that gave me 1344 X 1008 resolution at 24 FPS in 4:3 mode without skipping frames. I could shoot for at least 6 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 2688 X 1008 in Compressor for Vimeo. Anyone else shooting in 4:3 mode? Can resolution go higher than 1344 X 1008? Thank you.
Quote from: Andy600 on July 30, 2013, 09:29:24 PM
@Araucaria - Tragic Lantern has a feature to auto-disable Global Draw when you hit record. You should be able to shoot with the histogram on without a big hit to performance. ETTR is a method of shooting. If you are referring to the auto-ETTR module, yes, it does work in the 50D but you shouldn't use it for video. Expose with the raw histogram.
I mentioned because someone with a 5dmkiii recomended shooting with ETTR on, I thought maybe it set the aperture to the maximum level without burning after taking a shot and before starting to record.
Anyway, I'll try tragic lantern. Btw, is there a way to get rid of the black borders in tragic lantern? I guess it's trivial but I didn't have time to look for the setting.
@araucaria - Press the INFO button a few times
Quote from: pinger007 on July 30, 2013, 01:29:38 AM
@arrinkiiii
The fireworks were done in After Effects using a mix of Red Giant's Particular and some of Video Copilot's Action Essentials II for the smoke effects. I used a mix of Chroma Key and rotoscoping to mask the fireworks to the sky.
https://vimeo.com/71108800
Glad you enjoyed it.
Very nice made indeed. Thank you for sharing your work :D
Soo, I stopped following this thread at like page 80 or something, could someone give me an update on what version people are using and getting the best results? Is it the Nightly Build-version?
Thanks!
So now that the contest is under way, I can finally show this off.
This was shot w/ last month's 50D build (most shots) and also an earlier 60D build. Slo mo was done on 720p video on the 60D as well.
Even in the earlier builds, the color depth, latitude and flexibility was second to none.
Quote from: KahL on July 31, 2013, 04:22:56 PM
So now that the contest is under way, I can finally show this off.
This was shot w/ last month's 50D build (most shots) and also an earlier 60D build. Slo mo was done on 720p video on the 60D as well.
Even in the earlier builds, the color depth, latitude and flexibility was second to none.
Great job Kahl footage looks amazing. I got a question the low light shots like the one where his seating in a room waiting, and when his walking out to fight was that shot on the 50D?
Hello!
All the frames in each of my shot is totally covered in pink hue.
Im using trancend udma 7 64gb 1000X card.
And I was using raw2dng.
I tried formatting, re-installing and warming up the card but nothing helped. all frames are pink.
any ideas?
Quote from: ike on July 31, 2013, 09:49:36 PM
Hello!
All the frames in each of my shot is totally covered in pink hue.
Im using trancend udma 7 64gb 1000X card.
And I was using raw2dng.
I tried formatting, re-installing and warming up the card but nothing helped. all frames are pink.
any ideas?
Are your files larger then 4GB? If so, are you merging them before using raw2dng?
I had a similar problem, and it turned out I was having problems merging spanned files into one big raw file.
Thank u! i think it worked out now. i merged the files together and extracted the dngs with raw2dng
BUT i had some frames that had size of 0bytes??. I could open them and they showed a frame that was intact.
any ideas?
Quote from: goldenchild9to5 on July 31, 2013, 08:59:16 PM
Great job Kahl footage looks amazing. I got a question the low light shots like the one where his seating in a room waiting, and when his walking out to fight was that shot on the 50D?
Yeah it was. I think I stuck to about 1600 ASA for those shots. I'm not a big fan of super high ISO ranges unless it's absolutely required, so I tend to embrace the shadows and express the work with the smaller light sources. I find it gives a lot of personality to the shot rather than blasting to say, 6400 ASA, y'know.
Bah, Cinematography geekery :-p
Could someone explain me how to get 1:1 cropmode out of my 50d since i dont understand if its the same thing as 5x zoom or something else? explaining the 3x zoom would be nice aswell.
When you are zoomed in 5x you record in crop mode which is 3x. The quality is great but the problem is that you can't see the actual framing. You see 5x but record 3x. With tragiclantern you can get a hacked low fps grayscale preview.
@KahL Well done. Great job! Hope you win the contest.
OK thank you!
I have another problem.
All my shots have WB value of 4654 when i extract them with raw2dng. I have tried different values in-camera but nothing helps. So all my shots are a bit to the purple.
Any ideas?
Quote from: ike on August 01, 2013, 11:23:56 AM
OK thank you!
I have another problem.
All my shots have WB value of 4654 when i extract them with raw2dng. I have tried different values in-camera but nothing helps. So all my shots are a bit to the purple.
Any ideas?
That's the way it is, use raw2cdng which fixes it for you.
hello everyone
I've got issue with VERY BAD MOIRE.
Tryed to reintall several time ML and canon firmware but nothing works. I use latest bild of raw modules for my Canon 50d.
Canon 50d Raw ML non-crop MOIRE under spoiler[spoiler] (http://imageshack.us/a/img20/2100/j6m0.png)
[/spoiler]
Canon 50d Raw ML non-crop MOIRE 400% crop[spoiler]
(http://imageshack.us/a/img94/3218/hcz8.png)
[/spoiler]
should moire be SO HEAVY? even eyes don't look natural - red dots are everywhere!
Here are test chards with moire -Hell where pixel DIES[spoiler]
(http://imageshack.us/a/img560/2233/5oc4.png)
[/spoiler]
Any idea?
But I have good news. transcend compact flash 32gb 600x (udma7 and "20" labeled) reach full non-crop resolution (1584x892 with global draw turned on and everything all turned off (even spot meter!)) and it works great. Continuously! Here where I am (Russian Federation, Moscow) there are no komputebay x1000 card in stores, but 600x card can be bought really easily.
in crop mode it looks like it record continuously 1856x776 too!
And good news #2. Image in raw gets REALY close to Red One MX quality!
[spoiler](http://imageshack.us/a/img850/2835/hrey.png)
[/spoiler]
[spoiler](http://imageshack.us/a/img14/5995/e1kx.png)
[/spoiler]
Red Video was shot in 4,5k resolution mode, in red code 36, donwscaled in resolve to 1920x1080p with amazing Angenieux 30-80 lens at T8, ISO 800 to reach whole dynamic range and be comparable with canon 50d ISO 100 with T4 and simple canon 28-105mm 3,5-4.5 lens. everything at 30mm focal range. light setup was 1000w octadome dedolight for key light, and 2 spot dedolight 200w for fill and rim light. no color grading, only white balance, and red color 3 red gamma 3 DRX 1 for Red One MX, and RAWMAGIC->resolve and hunters 5dm3 LUT in BMD colorspace with highlight recovery and -0.19 exposure.
@burton-fzz - The problem is with Resolve. It's demosaicing isn't great for ML DNG or CDNG. Try using Rawtherapee with the AMaZE algorithm. You'll still have moire issues but not the multi-coloured and obvious maze patterns.
Quote from: Andy600 on August 01, 2013, 03:59:28 PM
@burton-fzz - The problem is with Resolve. It's demosaicing isn't great for ML DNG or CDNG. Try using Rawtherapee with the AMaZE algorithm. You'll still have moire issues but not the multi-coloured and obvious maze patterns.
thnks!!!!! never heard about rawtherapee...
i'll try right now!
Quote from: burton-fzz on August 01, 2013, 04:04:41 PM
thnks!!!!! never heard about rawtherapee...
i'll try right now!
After effects also works better than resolve.
Hi Magic Lantern fellows,
I decided to buy a 50d recently thanks to this awesome new feature ML team brought to us, many thanks for that!
I have tried several builds but still can not manage to control the shutter speed in LV even with FPS Overide on. I am probably missing something... Anyone could help me?
Thank you.
EDIT: Sorry I just figured out that the solution was exosure override! Thanks anyway for your job!
Quote from: burton-fzz on August 01, 2013, 03:52:32 PM
But I have good news. transcend compact flash 32gb 600x ....
Transcend 600x 32gb is well known as a stable card for 50D full frame. More than that, in crop mode it runs continuously at 1600x900. You can easily search in this thread to find out other "news" about this card ;)
Also, Komputerbay is absent in a number of countries. But some delivery services can help. Russia must have them, I suppose.
Newest Fstoppers piece. Entirely 50D excluding aerial stuff. Full BTS going up now.
I love that skin tone!
Workflow? Adobe or DaVinci?
Noise is added in post?
Thanks for sharing!
Quote from: riccardocovino on August 02, 2013, 09:37:51 AM
I love that skin tone!
Workflow? Adobe or DaVinci?
Noise is added in post?
Thanks for sharing!
Thank you!
Joined the raw spanned files in terminal, then through RAWMagic, then Davinci. Since it was BTS and I wasn't sure what I was going to edit as it's BTS I graded it all. Edited in Premiere. Grain is from Gorilla Grain.
Skin tones: I softened the entirety of the mid to high range and overexposed for the skintones. Nice bloomy, soft look.
Quote from: artiswar on August 02, 2013, 09:42:05 AM
Thank you!
Joined the raw spanned files in terminal, then through RAWMagic, then Davinci.
first of all - nice video!
do you use rawmagic to convert RAW file to CinemaDNG and then importing it directly into Resolve, of do you use other workflow? Do you have that crazy moire issue? with burning and flashing with red every contrast pixels like I posted before?
Quote from: rommex on August 01, 2013, 11:08:46 PM
You can easily search in this thread to find out other "news" about this card ;)
I have read the whole topic and other before buying 50d, but I cant remember anything about list of "supporterd cards". may be it's time to make it? But I know only two CF which can be used - Komputerbay x1000 (and other x1000 card which COST ALOT) and transcend x600 which I tested yesterday. Komputerbay can't be bought because I can't even google it in russian language - and it mean that there are no shops which want to sell it, neither transcend x600 which is selled for 125 US dollars, or 100Euro for 32GB ver x600. and 230 US dollars for 64gb version.
transcend x1000 costs 20% more. still it's more chipper then Red Mag 1.8" per gigabyte, but 4 times more expensive then really fast SSD from crucial or samsung or ocz... :(
that's all I know about Compact flash capable for RAW recording
Also there is Kingston CF/*U3 Which costs 90 us dollars for 32gb version, but I doubt of it speed capabilities...
Hey Andy made us a new build 8) thanks, going to check it out asap. Can we already expect the new raw format (mlv) in this build?
https://bitbucket.org/andy600/andy50d/downloads/
Quote from: artiswar on August 02, 2013, 09:42:05 AM
Skin tones: I softened the entirety of the mid to high range and overexposed for the skintones. Nice bloomy, soft look.
may I ask you how you did it in davinci? which curves you edited? it looks terrific to me!
Quote from: savale on August 02, 2013, 11:08:33 AM
Hey Andy made us a new build 8) thanks, going to check it out asap. Can we already expect the new raw format (mlv) in this build?
https://bitbucket.org/andy600/andy50d/downloads/
Not just yet.
.mlv is still being developed by g3gg0. It's not yet as fast as .raw and post workflow is a little more involved but we will get it at some point.
Will the new format change the workflow a lot? I got used to RawMagic to Photoshop to TIFF to After Effects. As I see it the benefit would be easier file spanning and metadata in the dng's?
Quote from: johansugarev on August 02, 2013, 01:14:39 PM
Will the new format change the workflow a lot? I got used to RawMagic to Photoshop to TIFF to After Effects. As I see it the benefit would be easier file spanning and metadata in the dng's?
The new format currently requires converting to .raw first so the converter apps will all need changing. There will be limited metadata and I think file spanning will likely be similar to .raw
You can follow the thread here: http://www.magiclantern.fm/forum/index.php?topic=7122.0
I think this development is best left to mature before porting to the 50D as it doesn't currently perform as well as .raw
What builds are people currenty using?
I used Gregory's jul27, but whenever I boot my camera iso jumps to 3200 for no reason.
Also when i adjust iso my camera doesnt use canons iso but the equvailent.
Also when i stop my recording i need to hit info a couple of times to get the screen information back.
There is propably some problems with saving the config file or something. Some settings just seem to stay on every startup even though i have changed and saved the new ones.
Thanks
PS.
Quote from: artiswar on August 02, 2013, 09:42:05 AM
Skin tones: I softened the entirety of the mid to high range and overexposed for the skintones. Nice bloomy, soft look.
Do you mean unsharpening mid to highs? or what do you mean by softening?
@ike - are you using a custom mode (C1 or C2)? If so it will restore ISO, WB etc to what you saved them as.
My latest builds are here:-
Magic - https://bitbucket.org/andy600/andy50d/downloads
Tragic - https://bitbucket.org/andy600/tl50d/downloads
Both stable
Quote from: ike on August 01, 2013, 12:19:48 AM
Thank u! i think it worked out now. i merged the files together and extracted the dngs with raw2dng
BUT i had some frames that had size of 0bytes??. I could open them and they showed a frame that was intact.
any ideas?
When you finish creating the DNG files with raw2dng, in Windows Explorer, some of them appear as 0kb. However, if you change folder and then come back, you'll notice that windows have corrected the size of those files equal of the size of the others. You can check that by ordering files by size.
This happened to me on set, and I was also alarmed. But it was just windows explorer acting funny :)
Quote from: Andy600 on August 02, 2013, 05:24:59 PM
@ike - are you using a custom mode (C1 or C2)? If so it will restore ISO, WB etc to what you saved them as.
My latest builds are here:-
Magic - https://bitbucket.org/andy600/andy50d/downloads
Tragic - https://bitbucket.org/andy600/tl50d/downloads
Both stable
Im using your magic build now and still it doesnt restore ISO or WB and im using C2
@ike - obviously ::) that's why I asked if you were using a custom mode.
Custom modes are a snapshot of how the camera was set up so ISO, WB etc will load exactly as it was stored (it's nothing to do with Magic Lantern). If you want to save the current state you need to write it again to C2.
@Andy
HAHAHA how dumb of me, ok so i'll be using M mode in the future it is working now.
one more thing! is it possible to have native iso values only like 100 200 400 800 1600. The ones in between have canon digital iso value of -0.3 EV. I mean when u are changing iso I would like to have only the native iso values at my disposal
ah nevermind found it incamera. i came from the 60d so the gui is a bit different
thanks agains and sorry :D
https://dl.dropboxusercontent.com/u/18087684/test.mp4
Here is some test footage straight from camera. No grading no nothing (WB and exposure done in Lightroom). I'm really pleased to see how crisp and clean the image is. a bit of antializing but not bad i guess.
settings:
1584x1058
23.976 fps
upressed to
16:9 1080p (+ some 2.35 cropping)
I can shoot that continously. with my trancend 64gb 1000x udma 7
There is one frame drop in the 2.35 crop but my card wasn't warm.
With external monitor this 50d is a BEAST!
BTW: does anyone know a goodway to reduce or completely remove the chroma noise?
Quote from: ike on August 02, 2013, 08:02:42 PM
https://dl.dropboxusercontent.com/u/18087684/test.mp4
Here is some test footage straight from camera. No grading no nothing (WB and exposure done in Lightroom). I'm really pleased to see how crisp and clean the image is. a bit of antializing but not bad i guess.
settings:
1584x1058
23.976 fps
upressed to
16:9 1080p (+ some 2.35 cropping)
I can shoot that continously. with my trancend 64gb 1000x udma 7
There is one frame drop in the 2.35 crop but my card wasn't warm.
With external monitor this 50d is a BEAST!
BTW: does anyone know a goodway to reduce or completely remove the chroma noise?
Looks good, nice frame for the crop too.
I can only blame this thread for quite a bit of unplanned expenses :) ! At this point, I haven't shot any RAW video yet, but I already spent money on
- - Zoom H1 recorder (I'm still hoping for a ML solution for video/audio syncing, like making 50D beep at the start of the video...)
- - Zoom H1 accessories (shock mount from dslrnoob, wind shield)
- - Power adapter for my 50D
- - 200W power converter from 12V to 120V (to be used with the power adapter and the car starter battery I already have)
- - And the latest - I just ordered locally Transcend 32GB 1000x. For Komputerbay 32GB 1000x, shipping to Canada and duties make it as expensive as the Transcend, and from what I've seen the Transcend should be much more reliable.
I am itching now to put all this to good (RAW video) use. I have a few nice lenses to play with (Sigma 17-50 f2.8, Canon 135L, Canon 70-200 f4L, Sigma 10-20mm, Samyang 8mm fisheye, 50mm and 28mm MF lenses).
@pulsar
whatkind of powersolution u have there?
Quote from: ike on August 02, 2013, 11:48:16 PM
@pulsar
whatkind of powersolution u have there?
I haven't received the card yet. I only tried compressed 1080p video on my old Transcend 400x, works fine.
What raw mod can I use that will work with my UDMA 7 Lexar 800x (45mbs write speed) card?
I installed magiclantern-Andy600.Build.2013Aug01.50D109 and I guess it's 70mbs RAW video and it keeps stopping on me. :(
EDIT - I changed Bitrate mode to FW Default and it works now. :)
EDIT 2 - It appears I have no idea what I was doing. lol. Looks like I have to adjust Resolution to my cards capabilities. :P
Full BTS is up.
Converted to CDNGs through RAWMagic. Graded with the BMD film preset. Payed attention to skin tones in terms of color.
For the slight glow on skin tone I created a new node, then used a qualifier to select the skin tones (HSL qualifier), I upped the blur on the qualifier so I could get a bit of bleed on the edges. I then increased the luma curve right around the mid high point and added some blur to it. Usually, I'll maximize the effect to a ridiculous level and tone it down to where I want it using the Gain function in the key tab.
Also, interesting issue. I've been having an issue with one card it seems. While recording long spans, the shutter speed will change. Not only this but when converting the RAW files to CDNGs in RAWMagic, the frame rate is recognized as 21.978. What gives?
A few posts (pages?) back: your camera is overheating.
Quote from: 1% on August 03, 2013, 04:28:04 AM
A few posts (pages?) back: your camera is overheating.
Whoa. Wild. Cures?
Leave A Trail - Canon 50D Raw Short Film, 1920 X 1080
Shooting raw on the Canon 50D. I shot with a faster CF Card (100 MBS) that gave me 1584 X 892 resolution at 24 FPS using the newest Magic Lantern Raw hack without skipping frames. I could shoot for at least 4 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 1920 X 1080 for Vimeo in Compressor.
Comments welcome. Thank you.
Quote from: BT on August 03, 2013, 05:40:14 AM
Leave A Trail - Canon 50D Raw Short Film, 1920 X 1080
Shooting raw on the Canon 50D. I shot with a faster CF Card (100 MBS) that gave me 1584 X 892 resolution at 24 FPS using the newest Magic Lantern Raw hack without skipping frames. I could shoot for at least 4 minutes (I didn't try shooting longer). I did my color correction with Adobe Photoshop and converted to 1920 X 1080 for Vimeo in Compressor.
Comments welcome. Thank you.
Nice video, beautiful place. How do you transfer/workflow the files for color correction with photoshop?
I do most of the cc work in Photoshop before exporting to tiff and then pro res. I do lots of still work, and Photoshop is a powerful tool when working with raw files.
Quote from: arrinkiiii on August 03, 2013, 05:47:50 AM
Nice video, beautiful place. How do you transfer/workflow the files for color correction with photoshop?
Great job real organic footage.. Keep posting more vids.
Quote from: artiswar on August 02, 2013, 09:32:55 AM
Newest Fstoppers piece. Entirely 50D excluding aerial stuff. Full BTS going up now.
Great job on both BTS videos.. footage looks amazing. You really got the grain down pack.
Quote from: BT on August 03, 2013, 06:46:36 AM
I do most of the cc work in Photoshop before exporting to tiff and then pro res. I do lots of still work, and Photoshop is a powerful tool when working with raw files.
Right on.. ACR sure gives the best result. Do you export your .Tiff's through Quicktime 7, or bring them into after effects?
QuickTime 7 to ProRes.
Quote from: artiswar on August 03, 2013, 02:56:34 AM
For the slight glow on skin tone I created a new node, then used a qualifier to select the skin tones (HSL qualifier), I upped the blur on the qualifier so I could get a bit of bleed on the edges. I then increased the luma curve right around the mid high point and added some blur to it. Usually, I'll maximize the effect to a ridiculous level and tone it down to where I want it using the Gain function in the key tab.
thanks for the deep explanation!
I think there-s no solution for heating, how long were those shots? more than 20 mins? (i doubt, you would need a 128GB card!).
If it was heating after 10 mins it's strange, maybe it was already a really sunny hot day?
What kind of sharpness and denoise settings have u been using in Lightroom to get the best out of your shots?
And do you resize in lightroom/photoshop or in video editing software?
Were can i download only the ETTR module?
Thank youuu :D
No real cure for the overheating but maybe needs a warning in FPS override.. if fps = ~21 and set fps !=21 pop up a warning so you don't come back with 21fps deliverables on a project.
I remember some time ago someone posted a link to a guide/tutorial for RAW video on 50D, but I can't find it. Could anyone please repost it? It should probably go to the first post on this thread - it became so long, that for someone in my situation (about to start using 50D for RAW video) it will appear overwhelming.
Thanks!
When I shoot some of my video, say in front of a green screen with steady lighting... my subjects are somewhat 'blinking'. The light is flashing like it's doing automatic quick exposure. How can I fix this?
Quote from: fromdecember on August 03, 2013, 06:11:33 PM
When I shoot some of my video, say in front of a green screen with steady lighting... my subjects are somewhat 'blinking'. The light is flashing like it's doing automatic quick exposure. How can I fix this?
Sounds as if you have the "HDR Video" function switched on. In this mode, the camera will bracket every sequence in different exposure settings, giving you a "flickery" result. See if it's turned on and switch it off to return to normal exposing.
Quote from: pulsar124 on August 03, 2013, 04:31:34 PM
I remember some time ago someone posted a link to a guide/tutorial for RAW video on 50D, but I can't find it. Could anyone please repost it? It should probably go to the first post on this thread - it became so long, that for someone in my situation (about to start using 50D for RAW video) it will appear overwhelming.
Thanks!
I think you are referring to Andy who is still writing a tutorial on this subject. However EOSHD.com released a tutorial on the 50D shooting RAW, it can be found here http://www.eoshd.com/the-eoshd-50d-raw-shooters-guide (http://www.eoshd.com/the-eoshd-50d-raw-shooters-guide) but it will cost a lot.
Shot this yesterday messing around.
I only get a few seconds recording before the buffer maxes out and I get the message. "Recording has been automatically stoppped".
I have a Komputerbay card so why is it only allowing me roughly 45mb/s bitrates before it closes itself down?
I have made a post about it if anyone can please help me. maybe reply on that instead of here or PM me please.. Many thanks!
HDR is off. Still blinks. Any other ideas to check for?
Expo override, auto WB (could have trouble on green screen). Post a video of it maybe?
@ fromdecember - when filming green screen you need to go higher shutter speed to eliminate flicker with all cameras,try raising it to about
between 1/80 - 1/100, also if using some cheaper fluorescent lights this can be issue.
I ve been doing green screen extensivly for past 7 years since mini DV 1/4 inch camcorders were the only option for indy film makers and had to encounter all kind of issues...
Hope this will help out.
Hey folks! I just wanted to share a free Adobe Camera RAW preset that I believe will be very useful for others as it has been for me. An easy to use preset to flatten your footage to kickstart your color-grading.
This plugin will take your footage and flatten your image so you can render into Pro-Res, DNxHD, or Cineform and color-grade in whatever program you wish.
Give it a try and let me know what you think!
Download and read more information here: http://www.dlwatson.net/flatz-preset.html
*footage shown in video is from a Canon 50D.
Latest builds for the 50D
Magic - https://bitbucket.org/andy600/andy50d/downloads
Tragic - https://bitbucket.org/andy600/tl50d/downloads
My understanding is many here are using ACR as part of the workflow. That's what I always use for my raw photos, and I love it. One important reason I like is because it can automatically correct many lens defects across multiple photos - distortion, vignetting, and chromatic aberration. CA is probably not very important for video, but distortion and vignetting are.
In your workflow, at the ACR stage, does it get all the relevant meta data (EXIF)? Is there any meta data in the RAW video? At the very least, one would want to have the lens ID, aperture, and focal length (for zooms) at the start of the video. Better still to have it for each frame. Are there any plans for such feature, if it doesn't exist yet?
[offtopic mode on]
I can hear about this progress with 7D RAW... Damn I sold my beloved 7D because it was the least ML'd camera at the time. Then I bought 550D as the the then most ML'd camera. Then I bought 50D as the cheapest "RAW monster".... Now everything comes back to 7D ;) ML ROCKS
[offtopic mode off]
Quote from: Andy600 on August 04, 2013, 10:31:11 AM
Latest builds for the 50D
Magic - https://bitbucket.org/andy600/andy50d/downloads
Tragic - https://bitbucket.org/andy600/tl50d/downloads
Andy, could you please explain the difference between Magic & Tragic?
Thanks alot!
:)
Quote from: Gekko on August 04, 2013, 10:42:43 PM
Andy, could you please explain the difference between Magic & Tragic?
Thanks alot!
:)
Andy has explained the difference 3 or 4 times by now. Why don't you look up his earlier posts?
Quote from: Gekko on August 04, 2013, 10:42:43 PM
Andy, could you please explain the difference between Magic & Tragic?
Thanks alot!
:)
One begins with the letter 'M' and the other with 'Tr' ;)
Quote from: pulsar124 on August 03, 2013, 04:31:34 PM
I remember some time ago someone posted a link to a guide/tutorial for RAW video on 50D, but I can't find it. Could anyone please repost it? It should probably go to the first post on this thread - it became so long, that for someone in my situation (about to start using 50D for RAW video) it will appear overwhelming.
Thanks!
Is this one it?
Got it from: http://www.eoshd.com/comments/topic/3059-canon-50d-magic-lantern-raw-review/
"So far, a how-to would be:
Format your CF card in the camera, take it out and put it into the card reader of your computer
Download the current stable, unified 2.3.5 MagicLantern release from http://www.magiclantern.fm/download
Download the most current development snapshot for 50D raw video recording either from https://bitbucket.or...tern/downloads/ (Gregory's 50D Magic Lantern tree) or from https://bitbucket.or...tl50d/downloads (1%'s TragicLantern tree)
Create a folder for the Magic Lantern files on your computer
Unzip the downloaded archive of the stable Magic Lantern release into that folder - and trash the file "autoexec.bin" + the folder "ML"
Unzip the 50D development snapshot into that same folder - after which "autoexec.bin" and the "ML" should be visible again.
In this folder, you should now see a number of files ending with ".fir", the manuals "INSTALL.pdf" and "Userguide.PDF", "autoexec.bin" and the folder "ML".
Copy "autoexec.bin", "ML" and "50D-109.fir" onto your CF card (that still rests in the card reader of your computer).
Cleanly unmount/eject the CF card via the software menu of your operating system and put it into your camera.
Make sure that you have a fully charged, preferably original Canon battery inside your camera.
Switch on the camera. Press the "Menu" button (on the upper left), go to the third (olive-colored) menu with the tool icon, go to the "Firmware" entry, press the button and run the Firmware update.
Wait for all installation messages till you get the message that it is safe to switch off the camera. Switch off the camera.
Switch it on again, wait a few seconds, and press the trashcan button on the lower left to enter the MagicLantern menu.
With the joystick, navigate into the menu with the video camera. Scroll down and adjust the entries with the big scroll wheel.
Activate the entry "REC key: HalfShutter".
Scroll down to the very bottom to the submenu "RAW video". Activate this option. Then press the "Func" button on the lower left to enter its option menu.
Start with conservative settings/low video resolutions (like 640x480) first. Activate the entry "Small Hacks".
Press the trashcan button to leave the Magic Lantern menu.
Press the Live View button on the upper left (next to "Menu") to enter LiveView. If this does not work, activate LiveView in the normal configuration menu of the camera (in the second olive tool menu).
If Live View is working, adjust shutter speed and aperture (if you are using a modern Canon lens) by pressing the trashcan button and going in the first submenu of Magic Lantern. Press the trashcan icon once you are done.
In Live View, half depress the normal camera release. You now see an indication that raw video is being recorded. Stop by pressing the release again.
When you are done, switch off the camera, copy the files ending with ".raw" from the DCIM folder of the CF card to your computer, use a program like RawMagic for Mac OS X (http://www.magiclant...hp?topic=6218.0) or ... (don't what is the recommended Windows solution at the moment, so I better leave this blank) to transform the files into Cinema DNG sequences, then grade/transform with your favorite raw conversion/grading tool (AE, Lightroom, Resolve...).
Quote from: rommex on August 04, 2013, 10:57:26 PM
Andy has explained the difference 3 or 4 times by now. Why don't you look up his earlier posts?
NOT very helpful.
Did you try a search on this topic? It's a trillion results. If you know where an explanation may be found, please just be so kind and give a more specific localization. Your answer doesn't even give a hint if it's inside the 104 pages of this topic after all. It's like kindly asking for someone's number and hearing "it's in the yellow pages".
Any real help would be appreciated. Thanks.
Edit: Andy, perhaps it might be a good idea to include a TXT file inside your tragic lantern bin. :-)
Quote from: Gekko on August 04, 2013, 11:06:49 PM
NOT very helpful.
Did you try a search on this topic? It's a trillion results. If you know where an explanation may be found, please just be so kind and give a more specific localization. Your answer doesn't even give a hint if it's inside the 104 pages of this topic after all. It's like kindly asking for someone's number and hearing "it's in the yellow pages".
Any real help would be appreciated. Thanks.
Edit: Andy, perhaps it might be a good idea to include a TXT file inside your tragic lantern bin. :-)
Or you could look at the changes on bitbucket.
Ok, in a nutshell, Magic Lantern is the Unified code as developed by a1ex, G3gg0 et al with the addition of the raw video module and other modules ETTR, Pic Viewer etc.
Tragic Lantern is developed by 1% and it's all of the above plus camera-specific enhancements and additional functionality for the 50D (and 6D, EOS-M, 600D).
The latest Tragic Lantern builds have ADTG shutter control which basically makes the shutter behave itself better than it did, Reslock (currently being tested) and also additional settings for raw video (delayed start, auto-Global Draw OFF etc) and a lot of other clever bit's and pieces that I couldn't even begin to explain because I don't know.
I just compile the code (fresh every time) that is available on Bitbucket and upload builds for you to download IF the developers themselves have not done so.
I'm sorry I haven't yet finished the 50D guide but there is a lot in there about all of this stuff (to the best of my own understanding).
Quote from: Andy600 on August 04, 2013, 11:24:58 PM
Tragic Lantern is developed by 1% and it's all of the above plus camera-specific enhancements and additional functionality for the 50D (and 6D, EOS-M, 600D).
The latest Tragic Lantern builds have ADTG shutter control which basically makes the shutter behave itself better than it did, Reslock (currently being tested) and also additional settings for raw video (delayed start, auto-Global Draw OFF etc) and a lot of other clever bit's and pieces
Many, many thanks for that explanation.
:)
Dogmydog: Thanks, that is a good start.
Quote from: pulsar124 on August 05, 2013, 12:52:18 AM
Dogmydog: Thanks, that is a good start.
You're welcome bro.
I'm a noob myself, so it was a relief when I found this step-by-step instructions.
Personally, I would skip this step:
"Activate the entry "REC key: HalfShutter"."
Since in Tragic Lantern Build you record RAW Video by pressing set button.
And Andy600, don't apologize on you delay writing the 50D guide, since you have no obligation at all on doing it.
All your comments and posts have been extremely helpful so far, so tyvm :D
PULSAR124...
The lens data is not recorded in the current firmware. However, G3ggo is working on an entirely new version of DNG files that includes the "metadata." It will be a great compliment for ACR for sure!
Thanks ML!
Thank you very much for this excellent software. I've used it a few times for testing raw footage for different purposes and it's been fantastic - along with the extended bracketing support which is amazing!!!
I have a question regarding the full frame res vs moire. The current res limitation appears to be from the line/column skipping for video so the camera's native res of approx 4500x3000 becomes approx 1500x1000, skipping 2 in 3 in each direction. This, assumably, is also the reason for the moire. I assume this has been discussed before, but is there a way to skip every 2 - reducing the moire and having the max res be approx 2250x1250, which could itself be cropped to something more manageable. I'm guessing the answer is that the video feed is being determined by parts of the firmware there is currently no access to - but it would be great if this were possible as it could kill 2 birds with 1 stone :)
Thanks
Dan
Filmed this video this afternoon. Definitely have a workflow down now.
To my surprise, when using Bachelor, all of my exported frames came out as an extension of .dp-@ rather than .dng files.
Ill be posting a video tutorial on if this happens to you, how you can fix it as well as a look at my workflow.
Thanks for watching!
Quote from: dan_seddon on August 05, 2013, 07:40:30 AM
...
I assume this has been discussed before, but is there a way to skip every 2 - reducing the moire and having the max res be approx 2250x1250, which could itself be cropped to something more manageable. I'm guessing the answer is that the video feed is being determined by parts of the firmware there is currently no access to - but it would be great if this were possible as it could kill 2 birds with 1 stone :)
Thanks
Dan
Don't dream about it )
Latest Tragic Lantern froze my 50D when I tried to enable Canon GUI to see where the focus box is.
Quote from: johansugarev on August 05, 2013, 08:54:17 PM
Latest Tragic Lantern froze my 50D when I tried to enable Canon GUI to see where the focus box is.
Can you recreate the error and explain what you did?
I shot with the latest TL build today and didn't have any issues.
Here is another video I did just goofing around downtown.
@1% About 7-8 seconds in you start to see the 'flashing' I talked about.
Raw to CDNG
ACR Flattened Image
Color Corrected in AE
I'm doing the same video, except corrected in Resolve to test different looks/feels.
http://www.youtube.com/watch?v=bPMwhRRpem4
i got some dead pixels at f12 with iso 12,800 is this normal ?
used a LA-7200 Anamorphic lens with a diopter output 1080x816
MPEG STREAM CLIP Hides gamma exposure
I saw it brighten/darken on the monument.. that looks like its from ACR.
is that a bug from ACR ? because yes i did use ACR before importing into AFX
Quote from: leojames on August 05, 2013, 11:05:48 PM
http://www.youtube.com/watch?v=bPMwhRRpem4
i got some dead pixels at f12 with iso 12,800 is this normal ?
used a LA-7200 Anamorphic lens with a diopter output 1080x816
MPEG STREAM CLIP Hides gamma exposure
ISO 12800? Are you sure about that? What build are you using?
BTW your video is not working.
fv
Is that a bug currently with the raw>acr transition?
Yea, ACR likes to do expo + wb shifts especially if you move certain sliders. Picking older processes helps... also sometimes gets rid of those debayering artefacts.
Quote from: Andy600 on August 05, 2013, 09:19:50 PM
Can you recreate the error and explain what you did?
I shot with the latest TL build today and didn't have any issues.
After enabling all modules, went into Live View and from there hopped back to ML>Live View settings>advanced settings>kill canon gui>off
Back in live view, ML gui started to flicker and the camera stopped responding, had to pull out batteries.
With the other build, the Magic Lantern one, it still flickers but does not crash.
I am guessing it will be sorted out when the time comes.
Btw, I am getting happy results with RawMagic from the app store and Photoshop CC, where I do corrections then export as tiffs and import in AE CC. No shadows flicker even if I use the shadow/highlight recovery and exposure quite hard. I need to test more and I'll post a video.
This sequence is working fine here.
Quote from: D.L. Watson on August 04, 2013, 06:49:06 AM
Hey folks! I just wanted to share a free Adobe Camera RAW preset
I like the concept D.L. Watson but aren't you throwing away data when you render out? How is preset preserving / optimizing the color values?
Thanks for your contribution!
Hi everyone,
New video online.
I've done quite a bit of low light stuff and so now wanted to have a look at big dynamic ranges and how the 50d could handle. Not too bad me thinks!
Cheers
Quote from: djfremen on August 06, 2013, 05:12:01 AM
I like the concept D.L. Watson but aren't you throwing away data when you render out? How is preset preserving / optimizing the color values?
Thanks for your contribution!
Essentially, you are throwing away data anytime you render to a file format that is not RAW. Log is just a really cool way to preserve your dynamic range and most of your color information into a nice, manageable package.
Here is a quick comparison I did just now.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/flatz_raw.jpg)
This is the Color Corrected DNG file using Adobe Camera RAW
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/flatz_log.jpg)
Here is the DNxHD file using the Flatz Preset.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/flatz_color_graded.jpg)
And here that same DNxHD file color corrected (rather quickly to match the RAW grade)
So, it's optimizing by taking the information that is already present in the raw, and boosting shadows and darks while lowering highlights, essentially centering the histogram like we are all already used to when shooting with DSLR's - but allowing you to render that raw information in a better format than the highly compressed and artifact-y H.264.
If you are limited on space and performance, a ProRes or DNxHD with the Flatz Preset might be more productive for you, and still give you excellent results.
Download here: http://www.dlwatson.net/flatz-preset.html
Quote from: Supermac on August 06, 2013, 05:59:00 AM
Hi everyone,
New video online.
I've done quite a bit of low light stuff and so now wanted to have a look at big dynamic ranges and how the 50d could handle. Not too bad me thinks!
Cheers
Absolutely beautiful. I love the anamorphic look. Good job!
@Supermac
Beautiful
Quote from: D.L. Watson on August 06, 2013, 06:16:48 AM
Essentially, you are throwing away data anytime you render to a file format that is not RAW. Log is just a really cool way to preserve your dynamic range and most of your color information into a nice, manageable package.
Here is a quick comparison I did just now.
...
So, it's optimizing by taking the information that is already present in the raw, and boosting shadows and darks while lowering highlights, essentially centering the histogram like we are all already used to when shooting with DSLR's - but allowing you to render that raw information in a better format than the highly compressed and artifact-y H.264.
If you are limited on space and performance, a ProRes or DNxHD with the Flatz Preset might be more productive for you, and still give you excellent results.
...
Download here: http://www.dlwatson.net/flatz-preset.html
It's the roughly same thing as those flat picture styles for Canon. Trying to squeeze wide DR into 8-bit video by reversed-S curve.
Appreciate your efforts, but this is basically one of the reasons why ML RAW exists -- to avoid using those ugly picture styles 8)
@Supermac - Love it!
Quote from: rommex on August 06, 2013, 01:03:57 PM
It's the roughly same thing as those flat picture styles for Canon. Trying to squeeze wide DR into 8-bit video by reversed-S curve.
Appreciate your efforts, but this is basically one of the reasons why ML RAW exists -- to avoid using those ugly picture styles 8)
Yes, it is like a flat picture style for Canon. And no, it's not trying to squeeze wide dynamic range it into a 8-bit (unless that is what you are rendering your files to). I recommend using a DNxHD 4.4.4. 10bit which is 20 times better than what any camera can provide internally.
Obviously, working straight with DNG's will be better, and there is no denying that. But like I've said in the beginning, this is especially for people who want to save space on hard drives and speed up their workflow.
It's just another option and to be honest - if Magic Lantern was able to somehow allow for the RAW data to be written into a film-log and rendered into a 10bit DNxHD or 12 bit ProRes file in camera, A LOT of people would use it and prefer it over raw DNG's. It would still provide you with your 11 stops of Dynamic Range and give you a more color information than some $6,000 cameras and use half the space.
It's no different than Black Magic Cinema Camera's ProRes option, which graded and compared to it's RAW, you cannot tell the difference between the two.
My latest test used the Flatz Preset, rendered to 10 bit DNxHD 4.4.4. and color-corrected in Resolve, and gave more 20 times more gradability than anything I've ever graded with H.264.
Thanks guys, not possible without ML!
Quote from: Supermac on August 06, 2013, 07:14:39 PM
Thanks guys, not possible without ML!
Great video! Can you please post your equipment specifications and workflow? :)
Thx
Quote from: dogmydog on August 06, 2013, 08:26:12 PM
Great video! Can you please post your equipment specifications and workflow? :)
Thx
No worries,
50D Raw ML 28th June build
ISO 100
1584 X 1056
Zeiss Pancolar 50mm, Zeiss Sonnar 135mm both stopped down quite a bit.
ND8 Filter
Schneider WA Cinelux
Redstan clamp
Workflow
Rawanizer-DNG-After effects-TIFF-Premiere Pro
A few small adjustments done with ACR and scaling done in premiere.
Cheers
I'm having a hard time getting my exposures right. I understand I should use the Histogram in camera, with that I set a ETTR, but my image in my LCD looks blown out.. also when I load the DNGs into ACR my histogram doesn't match what I setup in camera.
Might this be a bug? or am I missing something?
I'm updating to Andy's latest build as we speak..
Quote from: thorstone137 on August 07, 2013, 01:52:39 AM
I'm having a hard time getting my exposures right. I understand I should use the Histogram in camera, with that I set a ETTR, but my image in my LCD looks blown out.. also when I load the DNGs into ACR my histogram doesn't match what I setup in camera.
Might this be a bug? or am I missing something?
I'm updating to Andy's latest build as we speak..
I've done another test with Andy's latest build and I'm getting weird blow outs in my footage.. I follow common rules by prioritizing my shutter speed to 180 degrees of my fps (1/48 to 24fps).. I keep my ISO (160 or 360 to keep the ISO analogue) as low as possible.. and then I adjust my F-stop to get my histogram as close to the right as possible.. I'll push the highlights over a bit and then bring it back.
I can't help but think there is something else messing with my exposure..
My goal is to simply turn my camera on and be able to get usable footage as consistently as possible. Then I'll work on getting creative..
Well flip raw on/off if you're going between movie and photo mode to get correct indicators.
Photo/Video mode the expo will be different and you need to toggle raw video for it to recognize this... officially its only supposed to use movie mode but flipping back and forth can bring write speed up to 80s/max faster.
Someone should check on how well histogram matches from DNG to indicators.
Also watch out for ACR shifting expo. ETTR is supposed to be a tiny bit "blow out" on the LCD.
Quote from: 1% on August 07, 2013, 04:11:57 AM
Well flip raw on/off if you're going between movie and photo mode to get correct indicators.
Photo/Video mode the expo will be different and you need to toggle raw video for it to recognize this... officially its only supposed to use movie mode but flipping back and forth can bring write speed up to 80s/max faster.
Someone should check on how well histogram matches from DNG to indicators.
Also watch out for ACR shifting expo. ETTR is supposed to be a tiny bit "blow out" on the LCD.
Thanks for the tips.. I'm still getting my bearings when it comes to interpreting a Histogram.. I'm realizing that what I'm expecting the exposure to look like and what the histogram to look like aren't necessarily correct.. I'm going to make sure I'm using my waveform as well.. err.. I need a lot more practice..
QuoteAlso watch out for ACR shifting expo.
I think I know what you mean by this.. When I load ACR I make sure to select the default settings before making any other adjustments..
Longtime lurker, first time post...
I've really been enjoying the 50D raw hack, and I truly appreciate the effort everyone has put into it.
Here's a "first test" using the Tragic Lantern july 18 build:
50D raw with a Bolex 8/19/1.5 anamorphic.
I found 2 confusing differences in ML and TL (versions from 2013-08-04).
In ML grayscale preview for 3x crop mode doesn't seem to work.
In TR grayscale works but "normal view" has a black border and resolution is somehow reduced.
Does anyone experience simmilar issues?
The black border is just cropping out extra LV.. I dunno since it goes away with hitting function maybe its just an overlay? Would need a .422 to see. It was supposed to help with speed a-la recording in 640x480 mode.
1% thanks. I'll look closer to these differences and describe them later.
Quote from: Andy600 on August 04, 2013, 10:31:11 AM
Latest builds for the 50D
Magic - https://bitbucket.org/andy600/andy50d/downloads
Tragic - https://bitbucket.org/andy600/tl50d/downloads
Hi, I moved from ML to Tragic TL and tried latest build Tragic.Lantern-2.0-Andy600build.2013Aug04.50D109.reslock.zip
Thank you very much for performance improvement! Now I get more than 40 seconds 1080p.
Previous ML build June 28 I only got few seconds, so this is very good 8)
CF card is 64GB Komputerbay
Thanks
Jorgen
I'm wondering if anyone has found a way to avoid the poor debayering in Resolve WITHOUT passing through ACR.
I tested Rawtherapee and I agree the demosaic algorithms are really good, but a step involving it in the workflow is not a time-wise solution.
I hope Resolve 10 will be better, but meanwhile, there some sort of trick to raise the quality?
Quote from: riccardocovino on August 09, 2013, 12:45:55 PM
I'm wondering if anyone has found a way to avoid the poor debayering in Resolve WITHOUT passing through ACR.
I tested Rawtherapee and I agree the demosaic algorithms are really good, but a step involving it in the workflow is not a time-wise solution.
I hope Resolve 10 will be better, but meanwhile, there some sort of trick to raise the quality?
No, I don't think so. The debayering in Resolve really lets it down.
I shot some low light tests last night and processed everything in Raw Therapee (AMaZE demosaicing), output Jpeg and rendered in AE. The debayering and upscale is very good in RT and doesn't seem to have the flicker problems that ACR has.
These shots don't have any noise reduction. I only balanced and slightly sharpened, not even graded yet :). It was actually a lot darker than it looks.
A few frame grabs (video later) http://imgbox.com/g/YDDntkAGA7 (http://imgbox.com/g/YDDntkAGA7)
(http://i.imgbox.com/acrHsmEE.jpg)
50D ISO 200-1600 F1.4-F4 (Tragic Lantern 2.0 latest build)
Those shots are really good looking, and u're right, they are almost noise free.
Quote from: Andy600 on August 09, 2013, 01:18:08 PM
I shot some low light tests last night and processed everything in Raw Therapee (AMaZE demosaicing), output Jpeg and rendered in AE. The debayering and upscale is very good in RT and doesn't seem to have the flicker problems that ACR has.
These shots don't have any noise reduction. I only balanced and slightly sharpened, not even graded yet :). It was actually a lot darker than it looks.
Do you apply sharpening before or after upscaling the image in the RT?
Here 's same shot with Resolve and Rawtherapee (upscaled both to 1080p)
The difference in detail, aliasing and chroma noise is quite evident in many points.
(http://www.riccardocovino.it/wp-content/uploads/2013/08/comparison.jpg)
Main thing: the debayering on the stick. I was trying like hell to remove those on 6D.
Can anyone please explain to me why there is even a need for demosaicing for the raw video? Especially when it is a non-crop (full sensor) recording? Demosaicing is only needed at the sensor pixel level, but with full sensor video, you are using multiple sensor pixels per one video pixel - so how come it is still mosaiced? Is it just to save on bandwidth and space (so instead of 14*3 bits per video pixel, you only store 14 bits per video pixel, sacrificing color resolution for the framerate and space)? And how is it accomplished - is the sensor data first demosaiced, and then a new (lower resolution) fake mosaic is created by ML (or perhaps Canon)? Or perhaps the raw sensor data is being interpolated/binned, separately for each channel (R,G,B), from sensor resolution to video resolution?
Thanks!
I think you have to de-bayer CR2 as well and ACR does it.
Quote from: 1% on August 09, 2013, 05:14:07 PM
I think you have to de-bayer CR2 as well and ACR does it.
Where CR2 comes from? This is just for photos, not for video.
Quote from: 1% on August 09, 2013, 04:33:21 PM
Main thing: the debayering on the stick. I was trying like hell to remove those on 6D.
Yes, that's the most evident point!
How clunky is RawTherapee in processing shots? The most I would be doing is creating a flat profile and rendering to tiff or dpx.
Still waiting for my fast card, but decided to play a bit with the slower (400x) Transcend I have. I installed the most recent TL build.
I am baffled with the zoom (crop) of the video. I don't see explicit settings for that. Say, I want to use the whole sensor (non-cropped video), 640x480 pixels. How should I do that? When I use grey-scale preview hack, my video becomes cropped by a factor of 2 or more. When I press the LiveView zoom button, it zooms in even further (does it affect the recording as well?), but pressing Zoom out does nothing - it stays zoomed in.
How can I do non-cropped video?
Okay, I think I am starting to get it. I have to choose resolutions like 1500x1000 to use the whole sensor, without cropping - right?
But why can't I set 1920 pixels width, even when I use very low FPS (like 10)? When I try to do that, ML tells me "only 1580 is possible in this video mode"?
Quote from: pulsar124 on August 09, 2013, 08:15:08 PM
Okay, I think I am starting to get it. I have to choose resolutions like 1500x1000 to use the whole sensor, without cropping - right?
But why can't I set 1920 pixels width, even when I use very low FPS (like 10)? When I try to do that, ML tells me "only 1580 is possible in this video mode"?
You need to be in crop mode to get 1920. Press the zoom button once then go back to the raw module menu. You'll see you can then select up to 2000 px ;)
Quote from: Andy600 on August 09, 2013, 08:35:44 PM
You need to be in crop mode to get 1920. Press the zoom button once then go back to the raw module menu. You'll see you can then select up to 2000 px ;)
Thanks! And why is that? With non-RAW video, I can use 1920x1080 resolution. Is it because you hard-wired a certain binning factor - something like 1 video pixel for every 3 sensor pixels, in each dimension? Is it adjustable? I thought cameras like 5D3 can do 1920 in non-crop modes?
Given that Bayer cell has a size of 2x2 pixels, wouldn't the binning factor of two make more sense (should eliminate moire)?
Since @pulsar124 is making those questions, I have a question too about the limit of available resolutions in the 50D.
Why you can select the width up to only 2000px in crop mode (it's not even 2048)? It's because of the sensor or something? I mean, I could use a 3:1 ratio with large width, no?
Quote from: pulsar124 on August 09, 2013, 08:51:09 PM
Thanks! And why is that? With non-RAW video, I can use 1920x1080 resolution. Is it because you hard-wired a certain binning factor - something like 1 video pixel for every 3 sensor pixels, in each dimension? Is it adjustable? I thought cameras like 5D3 can do 1920 in non-crop modes?
Given that Bayer cell has a size of 2x2 pixels, wouldn't the binning factor of two make more sense (should eliminate moire)?
H.264 is line skipping just the same as non-crop mode is with raw video then upscaled to 1080p. It's not resolving full 1080p. Crop mode records 1:1 pixels from a portion of the sensor. There is no inbetween capability. It's not adjustable.
re: Bayer pattern you'll need to address that to a1ex, g3gg0 etc. I'm pretty sure they know what they are doing and what these cameras are capable of. I'm not a dev btw ;)
_________
Just a general comment to anyone reading this. Before you ask questions please credit the developers of ML with some intelligence. You may have a bright idea but the chances are they have already been there, done that and bought the t-shirt. They are already pushing the cameras way beyond the limits of what Canon themselves envisaged.
Quote from: Andy600 on August 09, 2013, 10:14:12 PM
Just a general comment to anyone reading this. Before you ask questions please credit the developers of ML with some intelligence. You may have a bright idea but the chances are they have already been there, done that and bought the t-shirt. They are already pushing the cameras way beyond the limits of what Canon themselves envisaged.
I don't know if that was indirectly addressed to me because of my question, but my doubt was to anyone that can answer me.
I don't have anything to say to the devs, but "thank you". Man, yesterday I made a video with my 50D with an old CF card (get to 30mb/s write speed) and I managed to achieve 1152 x 540 some times. Blowed my mind, I can't wait my 64gb 1000x Transcend to arrive.
But I made a question about the 2000px of width because:
1-
Quote from: Andy600 on August 09, 2013, 10:14:12 PM
H.264 is line skipping just the same as non-crop mode is with raw video then upscaled to 1080p. It's not resolving full 1080p. Crop mode records 1:1 pixels from a portion of the sensor. There is no inbetween capability. It's not adjustable.
And the sensor in 50D have 4752 pixels of width.
2-
There is a comment in the code that says:
Quoteresolution should be multiple of 64x32 or 128x16
this way, we get frame size multiple of 512, so there's no write speed penalty
So, I want to understand the 2000px width, not questioning the reason. Just seams that 2048px would make more sense and I'm not finding an answer in this 100+ pages topic.
edit: I just tried the crop mode. Two seconds on some great resolutions... and there is 2048px there. My bad. So I guess there is no need for answers, although I don't understand everybody writes "2000" instead of "2048".
Quote from: Andy600 on August 09, 2013, 10:14:12 PM
H.264 is line skipping just the same as non-crop mode is with raw video then upscaled to 1080p. It's not resolving full 1080p. Crop mode records 1:1 pixels from a portion of the sensor. There is no inbetween capability. It's not adjustable.
re: Bayer pattern you'll need to address that to a1ex, g3gg0 etc. I'm pretty sure they know what they are doing and what these cameras are capable of. I'm not a dev btw ;)
Thanks a bunch! I didn't realize 50D doesn't do true 1080p in h.264. And indeed, the 5D3 horizontal resolution is exactly 1920*3=5760 pixels (it shows the Canon's emphasis on video in the newest DSLRs).
So is this 3x3 pixels binning (from sensor -> to non-cropped video) built into the Canon's hardware or firmware, and ML is simply piggybacking it?
And is it indeed skipping, or binning? Binning would make much more sense - you reduce noise that way.
Still not clear what happens to mosaicing: Bayer cells are 2x2 pixels, and the video goes in 3x3 binning. Are there any demosaicing/mosaicing happening during RAWvideo recording, or only pure interpolation, separately in R,G,B? I think the latter would be more beneficial - fewer artifacts, and less cpu/memory intensive.
Latest Tragic Lantern 2.0 build is up: https://bitbucket.org/andy600/tl50d/downloads
Includes @Pravdomil's new Auto Exposure module (photo mode only), Crazy Colors which helps setting WB, Raw spot meter and a bunch of tweaks and fixes.
1% has also added code for the Dual ISO module :o but it's not working (yet) so I haven't included it in this build.
I would seriously recommend using Tragic Lantern on the 50D as it has much better shutter control in video mode.
As ever, this is developed for the 50D by 1% and includes all the latest Unified updates and fixes from a1ex, g3ggo and co. So thank them, not me ;)
Quote from: Andy600 on August 10, 2013, 10:20:15 AM
1% has also added code for the Dual ISO module :o but it's not working (yet) so I haven't included it in this build.
:o :o :o
wasn't that impossible on 50d ?!
Quote from: riccardocovino on August 10, 2013, 10:40:53 AM
:o :o :o
wasn't that impossible on 50d ?!
Apparently it was but a1ex is working on it for the 5d2 and if that works there is hope for the 50D
Quote from: Andy600 on August 09, 2013, 01:18:08 PM
No, I don't think so. The debayering in Resolve really lets it down.
I shot some low light tests last night and processed everything in Raw Therapee (AMaZE demosaicing), output Jpeg and rendered in AE. The debayering and upscale is very good in RT and doesn't seem to have the flicker problems that ACR has.
These shots don't have any noise reduction. I only balanced and slightly sharpened, not even graded yet :). It was actually a lot darker than it looks.
A few frame grabs (video later) http://imgbox.com/g/YDDntkAGA7 (http://imgbox.com/g/YDDntkAGA7)
(http://i.imgbox.com/acrHsmEE.jpg)
50D ISO 200-1600 F1.4-F4 (Tragic Lantern 2.0 latest build)
Nice images Andy, were they shot in crop mode? Look forward to the video.
is the 50d raw video capability comparable to a hacked gh2?
I know on paper the 50d would be better, but if you guys had the choice to choose a camera for videography... GH2 or 50d right now, which would it be?
Torn between the 2 cameras, make the decision for me please.
Quote from: rockfallfilms on August 10, 2013, 04:16:17 PM
Nice images Andy, were they shot in crop mode? Look forward to the video.
Thanks :)
I shot about 50/50 crop/non-crop. The first 5 are non-crop.
I'm editing the video atm.
Quote from: oc_masta on August 10, 2013, 04:26:53 PM
is the 50d raw video capability comparable to a hacked gh2?
I know on paper the 50d would be better, but if you guys had the choice to choose a camera for filming video with... GH2 or 50d right now, which would it be and why?
Torn between the 2 cameras.
In my opinion the 50D image is much nice than the GH2, it's more organic and gives you more options in post. It's not nearly as sharp but that's I good thing as far as I'm concerned. I got fed up having to deal with the 8 bit codec and heavily compressed footage anymore so I recently sold my GH2 and will be shooting my next project on the 50D.
Just bare in mind that the 50D does suffer from moire/aliasing whereas the GH2 doesn't suffer from moire. With the right monitor on set, the moire of the 50D can be worked around.
It does depend on what you shoot aswell, for documentary work the GH2 would be better but for narrative I'd go 50D.
Quote from: oc_masta on August 10, 2013, 04:26:53 PM
is the 50d raw video capability comparable to a hacked gh2?
I know on paper the 50d would be better, but if you guys had the choice to choose a camera for videography... GH2 or 50d right now, which would it be and why?
Torn between the 2 cameras.
Tough one but I'd have to say the GH2 for straight-up resolution, cost of media and post workflow. The 50D looks better when shooting raw of course and can handle more extreme grading but there is no on-board audio, moire and aliasing are an issue (especially compared to the GH2) and raw involves huge files. If you're prepared to do the extra work and be more careful what you shoot then the 50D is well worth it.
Personally...I'd want both ;)
Quote from: Andy600 on August 10, 2013, 04:30:36 PM
Thanks :)
I shot about 50/50 crop/non-crop. The first 5 are non-crop.
I'm editing the video atm.
Is this one an anamorphic lens or did you just crop in post?
http://imgbox.com/aclQK8KF
It's a real shame that Raw Therapee doesn't output quicktimes.
Quote from: rockfallfilms on August 10, 2013, 04:43:25 PM
Is this one an anamorphic lens or did you just crop in post?
http://imgbox.com/aclQK8KF
It's a real shame that Raw Therapee doesn't output quicktimes.
All shot on a 50mm, no anamorphic. I shot everything 16:9 but added the crop to hide a couple of framing mistakes ;D
I know what you mean about Raw Therapee :(. There doesn't seem to be a single 'free' app without limitations. ACR flickers (ok, it's not free but I have Adobe Cloud), Resolve lite has dodgy debayering and even the paid apps have problems. Hopefully they will add some other output options to RT but I'm really just hoping Resolve 10 has better debayering.
Thank you for the reply Andy600 and Rockfallfilms.
Would I be correct in thinking the 50d with the latest tragic lantern can do 1920x1080 for at least 1 minute of recording?
Quote from: oc_masta on August 10, 2013, 04:58:04 PM
Thank you for the reply Andy600 and Rockfallfilms.
Would I be correct in thinking the 50d with the latest tragic lantern can do 1920x1080 for at least 1 minute of recording?
Yes, with a fast CF card but full HD is only possible in crop mode so it's 3x crop in addition to APS-C's 1.6x
here´s another video....all is shot on the 50D, mostly with 10 to 12 fps.
still better, than just lamp posts ;-)
i tried, to bring a narrative component to good old timelapse. enjoy:
Quote from: crash-film on August 10, 2013, 06:14:15 PM
here´s another video....all is shot on the 50D, mostly with 10 to 12 fps.
still better, than just lamp posts ;-)
i tried, to bring a narrative component to good old timelapse. enjoy:
Really nice!
I love the 3D mix and the wise use of mirroring plane.
Great architectural shots too!
Quote from: Andy600 on August 10, 2013, 10:20:15 AM
Latest Tragic Lantern 2.0 build is up: https://bitbucket.org/andy600/tl50d/downloads
Includes @Pravdomil's new Auto Exposure module (photo mode only), Crazy Colors which helps setting WB, Raw spot meter and a bunch of tweaks and fixes.
Auto Exposure is great! I can't find what "Crazy Colors" is though. I've searched through commits on bitbucket and browsed options in camera, but couldn't find it
Here's a 1080p shot using the newest Tragic Lantern.
Quote from: caseyinhd on August 11, 2013, 05:53:39 AM
Here's a 1080p shot using the newest Tragic Lantern.
Great Job Casey... Like the colors, the smooth motion pan, and image is just right not too sharp and not too soft. What Was your workflow like? AE, Davinci, or Photoshop / Lightroom? Finally what lens did you use?
Quote from: Andy600 on August 10, 2013, 10:20:15 AM
Latest Tragic Lantern 2.0 build is up: https://bitbucket.org/andy600/tl50d/downloads
Includes @Pravdomil's new Auto Exposure module (photo mode only), Crazy Colors which helps setting WB, Raw spot meter and a bunch of tweaks and fixes.
1% has also added code for the Dual ISO module :o but it's not working (yet) so I haven't included it in this build.
I would seriously recommend using Tragic Lantern on the 50D as it has much better shutter control in video mode.
As ever, this is developed for the 50D by 1% and includes all the latest Unified updates and fixes from a1ex, g3ggo and co. So thank them, not me ;)
Andy what do you mean by "Crazy Colors which helps setting WB"? Does it mean that the color science has been improved, or just pulling out more colors and better colors from the sensor?
Quote from: caseyinhd on August 11, 2013, 05:53:39 AM
Here's a 1080p shot using the newest Tragic Lantern.
It's my good friend Casey. Welcome to the forums!
Great video! Was this true 1080p (5x crop) or did you shoot at 1280 and upscale?
Quote from: goldenchild9to5 on August 11, 2013, 06:13:17 AM
Andy what do you mean by "Crazy Colors which helps setting WB"? Does it mean that the color science has been improved, or just pulling out more colors and better colors from the sensor?
As I understand it Crazy colors will let you see when your WB has too much magenta or green as it amplifies it. You use it by changing your K levels until the magenta and green colors are minimized or removed. I haven't used it and not sure I will TBH but it's another method of setting correct WB.
The colors are only shown in previews, not in the recording.
Quote from: Andy600 on August 11, 2013, 10:17:33 AM
As I understand it Crazy colors will let you see when your WB has too much magenta or green as it amplifies it. You use it by changing your K levels until the magenta and green colors are minimized or removed. I haven't used it and not sure I will TBH but it's another method of setting correct WB.
The colors are only shown in previews, not in the recording.
So it works when you are in LiveView mode while shooting, or when you are processing your DNG's. Is that an option you turn on from the ML menu?
Quote from: goldenchild9to5 on August 11, 2013, 03:59:24 PM
So it works when you are in LiveView mode while shooting, or when you are processing your DNG's. Is that an option you turn on from the ML menu?
It's for setting WB. Preview only so switch on/off when or if you need it.
Does anyone else think the grayscale preview (50D crop) is a bit too crushed?
I just shot some fairly well-exposed close-ups of facial features and could hardly make out any detail in the all the blackness, especially when a face covers the whole frame. It makes focusing a nightmare in what would ordinarily be an easy situation. I think the contrast needs reducing quite a bit or the shadows need raising if possible. What do you think?
I only trust it as far as framing and use the histogram. I just focus in normal preview or 10x.
Quote from: 1% on August 11, 2013, 04:31:05 PM
I only trust it as far as framing and use the histogram. I just focus in normal preview or 10x.
I do too usually but I'm working with very shallow DOF so I have to pull focus. It's guesswork because the preview is totally crushed.
I'm shooting something like this:-
(http://i.imgbox.com/aduPRTY8.jpg)
but the grayscale preview looks like this
(http://i.imgbox.com/abf8p1JN.jpg)
Which makes it difficult to track focus on the eyes especially when she turns to face the camera. Even if I shoot deeper DOF it's the same problem.
Quote from: Andy600 on August 11, 2013, 04:39:14 PM
I do too usually but I'm working with very shallow DOF so I have to pull focus. It's guesswork because the preview is totally crushed.
I'm shooting something like this:-
(http://i.imgbox.com/aduPRTY8.jpg)
but the grayscale preview looks like this
(http://i.imgbox.com/abf8p1JN.jpg)
Which makes it difficult to track focus on the eyes especially when she turns to face the camera. Even if I shoot deeper DOF it's the same problem.
That's a very nice shot..
hey dudes
help me please
i got canon 50d and lexar x1000 16gb card
i try to record raw video it gives 30 fps
i try to FPS override and i get 2 fps
whats wrong?
i need 24 fps anyone know how to get 24 fps?
or which card should i use on canon 50d?
or should i format lexar x1000 in some way to get 24 fps?
What I find very frustrating when it comes to RAW video recording on 50D is the lack of information from ML developers about the most basic things - where to start, how does it work, which camera settings to use. I am good in photography, but novice in DSLR video, and I've been struggling for some time to get some answers here. It is probably here, spread in small bits across 109 pages of this massive thread, which makes it essentially unusable.
Anyway, I did some googling, and here is the number one place to visit if you are new to 50D RAW video:
http://www.eoshd.com/content/10770/canon-50d-magic-lantern-raw-review
This is a great review, aimed at novices like myself. For the first time I figured out what are differences, advantages and drawbacks for the full sensor and crop video recording. Now I know that the actual full sensor video resolution of 50D is 1584 x 1058 pixels, and it has some serious artifacts because of the way Canon does it. From reading other web resources I know now that how exactly DLR sensor is used for 1080p video recording is is not known - it is a "black box", fully hidden inside Canon firmware, or perhaps even done on hardware level. People can only speculate, based on actual video resolution measured from video, and amount of aliasing and moire artifacts. It looks like the best possible approach - binning sensor pixels into super-pixels for video - is not possible because of the limited bandwidth from the sensor. People speculate that some combination of binning and line skipping takes place, to reduce the bandwidth. This is really bad from a photographer's perspective - with huge DSLR sensors you'd expect to gain a lot in terms of light sensitivity (compared to consumer camcorders), but if you only do skipping, you don't gain anything - DSLR pixels are probably as small (or even smaller) than camcorder pixels.
People seem to be obsessed with crop video shooting, with the idea that the image quality should be much better, but as a photographer I can tell you that even the most expensive lenses (like my 135L) don't shine when viewed as 100% crops, especially wide open (and that's how I always use them - for DoF control). In other words, image quality is not great in crop video mode because of the lens limitations. One has to stop lenses down a lot to beat that. The second big negative coming from the crop mode is that you give up on DoF control (if you ask me, the main reason one should do DSLR video, and not consumer camcorder video) - because of the stopping down, and because of the fact that you are effectively working with a tiny size sensor (probably same size as camcorder sensor).
I wish this info, and more (like, details on shutter, aperture and ISO control when shooting raw video) where available somewhere as a single post, for novices. Then your great product would be appreciated even more.
Quote from: Silkway on August 11, 2013, 04:55:05 PM
hey dudes
help me please
i got canon 50d and lexar x1000 16gb card
i try to record raw video it gives 30 fps
i try to FPS override and i get 2 fps
whats wrong?
i need 24 fps anyone know how to get 24 fps?
or which card should i use on canon 50d?
or should i format lexar x1000 in some way to get 24 fps?
Enable FPS override and push the FUNC button. A menu will popup where you can select your desired fps. Anything below 30 works like a charm. You also have to interpret the footage as 24fps in you NLE.
BTW, what mode of FPS override do you guys choose with RAW? I leave it with low light.
@Pulsar124 - that would be an awfully long post.
1 - ETTR.
2 - ISO - If your shot needs it you can increase ISO up to 1600. Noise looks good but can be removed. Any higher and it's hit or miss.
3 - shutter speed and aperture - same applies as for any film/video
The shot I posted above is 3x crop ISO800 at F4 - is that not shallow? I could shoot the same thing again in non-crop and the DOF will be no different. I think the crop vs non-crop argument is more relevant to print resolution. Afterall, there is only a certain amount of pixels on a screen/monitor. Crop mode removes the aliasing/moire problems. Shallower DOF helps with those issues for non-crop modes.
4 - You are right that there needs to be more info. I've been writing a guide covering the 50D, ML and Tragic Lantern, raw video etc but if you cant wait get the EOSHD one.
5 - We are all novices when it comes to raw video on the Canons'. Raw video has only been part of Magic Lantern for 2-3 months. We're all still learning. I learned everything I know from practice and from reading posts and notes in the ML source code.
Quote from: pulsar124 on August 11, 2013, 04:57:40 PM
What I find very frustrating when it comes to RAW video recording on 50D is the lack of information from ML developers about the most basic things - where to start, how does it work, which camera settings to use.
It can be frustrating when jumping into technical details, i agree. But there is a really good strating point for basic explanation of functionality on this site: http://wiki.magiclantern.fm/userguide
It helped me a lot.
:)
That is a big difference on the preview, like the black is crushed. I haven't even looked how it does the playback/preview wonder if it does the black level different.
There is real "crop mode" where DOF is screwed up (EOS-M/600D/650D) and the 5X zoom mode where its just less pixel skipping so DOF is the same, you're just shooting through the middle (hopefully) of the lens. Actually it should be better quality since you're using the center and can cut off vignettes/edge distortion/etc.
Quote from: 1% on August 11, 2013, 05:23:03 PM
...That is a big difference on the preview, like the black is crushed. I haven't even looked how it does the playback/preview wonder if it does the black level different.
The playback contrast is much better so if you could match that for grayscale preview or maybe even have a lower contrast it would be much more useable in tough lighting conditions. I know the grayscale contrast is a workaround to combat the pink screen/half shutter problem and a1ex wrote in the commit that he 'dropped the shadow level' so maybe it just needs pulling up?
I don't know what the hex value in raw_rec is for exactly or I'd try to change it myself.
I think it's line 1144 - 1146 in raw_rec that sets the grayscale and contrast?
Quote from: goldenchild9to5 on August 11, 2013, 04:53:48 PM
That's a very nice shot..
:) Thanks. Just testing an old lens.
For the grayscale preview he does it with digic registers so thats not a raw preview, just regular YUV in grayscale. There is also the 1/2 shutter ML grayscale from display filters, which one is this?
A question for anamorphic shooters:
I've got one of these lenses, which I haven't used for years. I was going to sell it but figured I might as well try it with the 50D as a way to get more resolution.
Does anybody know what is the widest taking lens I could pair it with? It's got a 39mm rear thread if that makes a difference.
Cheers!
(https://dl.dropboxusercontent.com/u/24738031/Photos/moller-anamorphic.jpg)
I have it set to Canon preview. The ML one is too slow for me.
Quote from: rockfallfilms on August 11, 2013, 05:42:07 PM
A question for anamorphic shooters:
I've got one of these lenses, which I haven't used for years. I was going to sell it but figured I might as well try it with the 50D as a way to get more resolution.
Does anybody know what is the widest taking lens I could pair it with? It's got a 39mm rear thread if that makes a difference.
Cheers!
Nice. I'm jealous >:(
I think you can't go much wider than 50mm but it's probably best to ask on the eoshd forum
Quote from: Andy600 on August 11, 2013, 05:51:03 PM
Nice. I'm jealous >:(
I think you can't go much wider than 50mm but it's probably best to ask on the eoshd forum
Yeah it's a pretty good copy of the lens too. I found it in a drawer a couple of months ago, forgot I even had it!
I don't find it that friendly over on eoshd, lots of infighting. :) Also if you ask a question you are just told to buy Andrew's buyers guide. I have a 50mm Nikon here so I'll see how it looks on that.
I guess the canon preview black is too crushed then. Not sure which reg brings down the shadows.
Quote from: johansugarev on August 11, 2013, 05:13:53 PM
Enable FPS override and push the FUNC button. A menu will popup where you can select your desired fps. Anything below 30 works like a charm. You also have to interpret the footage as 24fps in you NLE.
BTW, what mode of FPS override do you guys choose with RAW? I leave it with low light.
Oh yeah! That worked! Thanks a lot!
Function button... I would never think about it is active in menu)
However i had to change aspect ratio to achieve the continuous shooting to narrower.
For some reason the speed of Lexar x1000 is not fast enough? Just 55 mb/sec Or this is okay?
P.S. Thanks for you guys who made this awesome options! Magic Lantern team and Andy600 build.
Which card do you guys use?
And how does the external recorder such as Atomos Ninja 2 work with Canon 50d?
What is the output format? Is it still RAW or going to be uncompressed ProRes?
Quote from: 1% on August 11, 2013, 06:32:54 PM
I guess the canon preview black is too crushed then. Not sure which reg brings down the shadows.
I think it has something to do with 'get_halfshutter_pressed'? I wouldn't know where to look though
Quote from: rockfallfilms on August 11, 2013, 06:14:06 PM
Yeah it's a pretty good copy of the lens too. I found it in a drawer a couple of months ago, forgot I even had it!
I don't find it that friendly over on eoshd, lots of infighting. :) Also if you ask a question you are just told to buy Andrew's buyers guide. I have a 50mm Nikon here so I'll see how it looks on that.
Yeah, it can be a bit intimidating to post there but it seems like only a few of the users who are a bit obnoxious.
It looks like most shooters with that lens tend to go for a Helios 44:2 because of the flare and I have seen it paired with 35mm lenses on nex5's but you're probably best sticking to a 50mm. I personally wouldn't go the Helios route. It's hard to find a sharp V2 and there are plenty of decent, faster and cheap 50mm lenses out there that can flare. I have a 1974 Nikon F2 that would be ideal and it's sharp wide open.
I'm looking for my first anamorphic lens so I'm looking forward to seeing what the Moller looks like with raw on the 50D.
QuoteI think it has something to do with 'get_halfshutter_pressed'? I wouldn't know where to look though
He sets 3 regs, one is 0, one is FFFFFF and another one is some binary looking value like 01010101.
Real ML raw preview I think happens on 1/2 shutter.
Quote from: 1% on August 11, 2013, 09:04:07 PM
He sets 3 regs, one is 0, one is FFFFFF and another one is some binary looking value like 01010101.
Real ML raw preview I think happens on 1/2 shutter.
Just a thought but could the previews (especially hacked) and display filters make use of ADTG?
also i have question
in crop mode the resolution is dropping down or what?
or it is the lens problems start to appear?
coz i experience like
sharpness and noise grain is smaller in non crop mode
how come the resolution goes up to 2000 in crop mode if it actually kills the image?
Quote from: rockfallfilms on August 11, 2013, 05:42:07 PM
A question for anamorphic shooters:
I've got one of these lenses, which I haven't used for years. I was going to sell it but figured I might as well try it with the 50D as a way to get more resolution.
Does anybody know what is the widest taking lens I could pair it with? It's got a 39mm rear thread if that makes a difference.
Cheers!
Hi there,
Those old Moller lenses are very tricky to use and not very good really, also very difficult to sell too. Nobody wants them. I would be more than happy to take it off your hands for a small sum? :)
Ha ha, seriously, 50mm-85mm is the best range for a 2x 16mm Anamorphic on a crop sensor. Any less vignettes, any more you start to lose focus. Personally I'd say 50mm maybe a little wide especially with a 39mm rear thread. Helios is popular as 58mm is optimal focal length and has minimal vignetting. They can be pretty sharp but also "characterful". 55mm Takumar is not bad if you can find a sharp one but still vignettes, especially if you have to stop down. Clamp is really important too, you want to be as close to the taking lens as possible. Hope this helps, would love to see the results.
Cheers
Quote from: goldenchild9to5 on August 11, 2013, 04:53:48 PM
That's a very nice shot..
I know it is a bit off-topic, but since I'm a 50D Raw Video Shooter, here it comes:
I usually my RAW2DNG DNG's as a sequence to AE CC and grade them in ACR at the time of import. Sometimes, the light changes during the my shot, in the same video clip. So the beginning is ok, but in the rest I would have to push its exposure (for example) up a bit.
My question is: after imported into AE, is it possible to return to ACR controls to grade a specific part of my clip? As many times as I need? Or I can only grade it on the import, and then all I have to work with is the Color Controls of AE itself? Does Resolve allow me to do it? What is the best time to color grading my clips, using ACR?
Also, if I color correct the video color inside AE, do I lose data or is it the same as grading DNGs in ACR?
Sorry for the noob questions, but I didn't know where to put these questions...
Quote from: dogmydog on August 11, 2013, 10:23:10 PM
I know it is a bit off-topic, but since I'm a 50D Raw Video Shooter, here it comes:
I usually my RAW2DNG DNG's as a sequence to AE CC and grade them in ACR at the time of import. Sometimes, the light changes during the my shot, in the same video clip. So the beginning is ok, but in the rest I would have to push its exposure (for example) up a bit.
My question is: after imported into AE, is it possible to return to ACR controls to grade a specific part of my clip? As many times as I need? Or I can only grade it on the import, and then all I have to work with is the Color Controls of AE itself? Does Resolve allow me to do it? What is the best time to color grading my clips, using ACR?
Also, if I color correct the video color inside AE, do I lose data or is it the same as grading DNGs in ACR?
Sorry for the noob questions, but I didn't know where to put these questions...
1. I would suggest importing two copies/clones of the same clip with different expo corrections. And then use two different parts from these clones.
2. You don't lose your data of course. The .DNGs stay intact.
Quote from: D.L. Watson on August 06, 2013, 05:12:31 PM
....And no, it's not trying to squeeze wide dynamic range it into a 8-bit (unless that is what you are rendering your files to). I recommend using a DNxHD 4.4.4. 10bit which is 20 times better than what any camera can provide internally.
Obviously, working straight with DNG's will be better, and there is no denying that. But like I've said in the beginning, this is especially for people who want to save space on hard drives and speed up their workflow.
I see your point and I stand corrected in a way )) Please let me know if this DNxHD codec is available free or paid? Thanks
Quote from: dogmydog on August 11, 2013, 10:23:10 PM
I know it is a bit off-topic, but since I'm a 50D Raw Video Shooter, here it comes:
I usually my RAW2DNG DNG's as a sequence to AE CC and grade them in ACR at the time of import. Sometimes, the light changes during the my shot, in the same video clip. So the beginning is ok, but in the rest I would have to push its exposure (for example) up a bit.
My question is: after imported into AE, is it possible to return to ACR controls to grade a specific part of my clip? As many times as I need? Or I can only grade it on the import, and then all I have to work with is the Color Controls of AE itself? Does Resolve allow me to do it? What is the best time to color grading my clips, using ACR?
Also, if I color correct the video color inside AE, do I lose data or is it the same as grading DNGs in ACR?
Sorry for the noob questions, but I didn't know where to put these questions...
Yes you can :D Just go to -interpret footage- and then the sub-menu and then hit the -options- button and will open again ACR.
Quote from: rockfallfilms on August 11, 2013, 05:42:07 PM
A question for anamorphic shooters:
I've got one of these lenses, which I haven't used for years. I was going to sell it but figured I might as well try it with the 50D as a way to get more resolution.
Does anybody know what is the widest taking lens I could pair it with? It's got a 39mm rear thread if that makes a difference.
Cheers!
(https://dl.dropboxusercontent.com/u/24738031/Photos/moller-anamorphic.jpg)
The only way you're going to know is to slap it on a few lenses and see. My guess is probably from 40 to 50mm, but i'd try a 35mm just to see.
1% you sir are a genius!!!! 8)
Just seen the new addition and gonna compile. It will surprise a few 50D users I'm sure.
Quote from: Andy600 on August 12, 2013, 01:05:56 AM
1% you sir are a genius!!!! 8)
Just seen the new addition and gonna compile. It will surprise a few 50D users I'm sure.
Sounds rather exciting....
Mr 1% has done it again! We now have Dual ISO on the 50D 8) \o/ (Tragic Lantern only ATM)
Grab the latest Tragic Lantern build here: https://bitbucket.org/andy600/tl50d/downloads
Dual ISO only works in photo mode on the 50D so don't shoot in Live View.
Read a1ex's thread for how to use: http://www.magiclantern.fm/forum/index.php?topic=7139.msg59687#msg59687
You will need the conversion programs which are downloadable via a link in the first post of a1ex's thread. READ AT LEAST THE FIRST POST!!
Don't ask questions about it here. Follow the other thread and READ IT!
All thanks to 1% for the 50D port and a1ex, g3gg0 for this great feature.
p.s. also check whats under the star icon in the menu ;D
Quote from: rommex on August 11, 2013, 11:27:50 PM
1. I would suggest importing two copies/clones of the same clip with different expo corrections. And then use two different parts from these clones.
2. You don't lose your data of course. The .DNGs stay intact.
Ty Rommex, that helps a lot :D
Quote from: arrinkiiii on August 11, 2013, 11:42:51 PM
Yes you can :D Just go to -interpret footage- and then the sub-menu and then hit the -options- button and will open again ACR.
But does that give me ACR on that specific frame I'm trying to correct or on the first DNG of the sequence?
Thx for the help , arrinkiiii!
Quote from: Andy600 on August 11, 2013, 05:16:37 PM
The shot I posted above is 3x crop ISO800 at F4 - is that not shallow? I could shoot the same thing again in non-crop and the DOF will be no different. I think the crop vs non-crop argument is more relevant to print resolution. Afterall, there is only a certain amount of pixels on a screen/monitor. Crop mode removes the aliasing/moire problems. Shallower DOF helps with those issues for non-crop modes.
Quote from: 1% on August 11, 2013, 05:23:03 PM
There is real "crop mode" where DOF is screwed up (EOS-M/600D/650D) and the 5X zoom mode where its just less pixel skipping so DOF is the same, you're just shooting through the middle (hopefully) of the lens. Actually it should be better quality since you're using the center and can cut off vignettes/edge distortion/etc.
I've come across this and I don't quite understand it,in general terms, dof depends on focal length and aperture. So if you shoot a 12mm at f4 on 3x crop you will get an fov equivalent 57,6 but the dof will be the same as on the 12mm @ f4 but not the same as a 58mm @ f4 on the full sensor, if I remember it right it would be more like a 58mm @ f12. I don't know what lens you are shooting with (andy) but if there is a shallow depth of field in the shot it's because you are very close to the subject in relation to the background.
So actually it "screwes up" the dof. I would also know how this mode is not a real crop compared to what ever distinct mode there is on the 600d,etc... Just curios ^^.
Regarding anamorphics, I just got a sankor 16c on ebay for 150€ (I know, its not the best deal but it's getting harder to get a decent deal, the sankor still is somehow accesible).
I'm looking for a decent taking lens, I asked on eoshd but..., so I'd like to know if anybody has some experience. I think 58mm 44-2 should be right but if anybody has a better idea I'm starving for suggestions!
Quote from: araucaria on August 12, 2013, 04:02:26 AM
I've come across this and I don't quite understand it,in general terms, dof depends on focal length and aperture. So if you shoot a 12mm at f4 on 3x crop you will get an fov equivalent 57,6 but the dof will be the same as on the 12mm @ f4 but not the same as a 58mm @ f4 on the full sensor, if I remember it right it would be more like a 58mm @ f12. I don't know what lens you are shooting with (andy) but if there is a shallow depth of field in the shot it's because you are very close to the subject in relation to the background.
So actually it "screwes up" the dof. I would also know how this mode is not a real crop compared to what ever distinct mode there is on the 600d,etc... Just curios ^^.
Regarding anamorphics, I just got a sankor 16c on ebay for 150€ (I know, its not the best deal but it's getting harder to get a decent deal, the sankor still is somehow accesible).
I'm looking for a decent taking lens, I asked on eoshd but..., so I'd like to know if anybody has some experience. I think 58mm 44-2 should be right but if anybody has a better idea I'm starving for suggestions!
Not a bad deal, they're only going to go up in value! 16c has a 42ishmm rear thread, redstan makes a custom clamp for it which is well worth the money. Regarding taking lens, see my last post. Just as relevant to Sankor 16c.
Cheers
QuoteSo if you shoot a 12mm at f4 on 3x crop
The FOV will be different but the image is still at 12mm f/4, you are just taking a portion of it. So if something was out of focus it remains so, etc.
Quote from: Andy600 on August 12, 2013, 02:07:35 AM
Mr 1% has done it again! We now have Dual ISO on the 50D 8) \o/ (Tragic Lantern only ATM)
Grab the latest Tragic Lantern build here: https://bitbucket.org/andy600/tl50d/downloads
Dual ISO only works in photo mode on the 50D so don't shoot in Live View.
Read a1ex's thread for how to use: http://www.magiclantern.fm/forum/index.php?topic=7139.msg59687#msg59687
You will need the conversion programs which are downloadable via a link in the first post of a1ex's thread. READ AT LEAST THE FIRST POST!!
Don't ask questions about it here. Follow the other thread and READ IT!
All thanks to 1% for the 50D port and a1ex, g3gg0 for this great feature.
p.s. also check whats under the star icon in the menu ;D
Wow!!! Wow!!! That's awesome @1% @Andy600 great job I can't wait to try.. Do you think it might be damaging to the sensor, or all is good? I'm so excited right about now 50D just got a new lease in shooting Raw ;D
I don't think it damages anything.
Quote from: 1% on August 12, 2013, 05:07:43 AM
I don't think it damages anything.
You right haven't heard of any Mark III's being messed up with Dual ISO's. The literature about Dual ISO is pretty long, still trying to figure my way around it. When I figure it out I'm going to do a Walk through video, or tutorial about the Dual ISO. Thank you once again 1% for all your hard work, Woah still excited 8)
Hi is there any Mac version of cr2hdr?
I tried myself with no luck....
studios-mac-pro:dual_iso studio$ gcc cr2hdr.c
Undefined symbols for architecture x86_64:
"_save_dng", referenced from:
_main in ccsnxKis.o
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
studios-mac-pro:dual_iso studio$ gcc -m32 cr2hdr.c
Undefined symbols for architecture i386:
"_save_dng", referenced from:
_main in ccyoodbS.o
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
Quote from: 1% on August 12, 2013, 04:28:01 AM
The FOV will be different but the image is still at 12mm f/4, you are just taking a portion of it. So if something was out of focus it remains so, etc.
I was wondering when the Fov/Dof argument over crop mode would pop up. Reducing the sensor size reduces field of view. When you reduce the field of view you have to move away from the subject or use a wider lens to get the same frame. Depth of field is directly related to both focal length and distance from the subject. Less focal length = more depth of field. More distance between camera and subject = more depth of field. In fact there will be quite a bit more depth of field on crop mode for any given f number. f numbers shouldn't be compared over different formats though as they are only part of the bigger depth of field equation and it gets confusing.
Saying that, it doesn't mean to say we still can't get shallow though. Andy's frame show's just how good crop mode is and getting shallower for that shot wouldn't do anything for the background really. In fact it opens new lens choices for me, I'm quite excited about using wider lenses on anamorphic which would normally vignette like crazy, 35mm Flektogon for example. I'll post some results when I shoot them.
Crop mode is a great option but I think it's a bit unfair calling it crop. It's more like a change of sensor size to a different format. Should call it 2/3 mode or something.
I hope that wasn't patronizing. Arkanoid's great by the way but I think it ate all my battery power! Looking forward to testing dual iso! :D
Cheers
So, Duel ISO is only for photography. It's not a video thing at the moment?
Quote from: D.L. Watson on August 12, 2013, 07:18:36 AM
So, Duel ISO is only for photography. It's not a video thing at the moment?
Not video at the moment. There are some problems in LV where dual iso is not applicable, at least for the moment. 1% is working hard on this. Perhaps it's due to the lack of ADTG registers. I offered help on the dual iso thread, we will see!
Hi,
as Ultra fast CF cards are extremely expensive, I bought CF reader for Android devices which looks like this:
http://dx.com/p/6-in-1-otg-card-reader-for-samsung-galaxy-tab-10-1-p7510-p7500-p7300-p7310-106442
Yes, you can move data directly to smartphone, but this way you save the batteries of 50D because transfering 30GB od data to microSD takes a lot of time.
The problem is there are no tools for playing RAW videos for Android yet afaik.
Anyone got idea how to play/preview RAW videos on Android just like we can with ML plugin in the camera?
Here's a clip I shot yesterday afternoon. Shot with a Tamron 17-55 and the Latest (or one of the latest) Tragic Builds.
If only we weren't limited to 892p in full-sensor mode :(
Cheers!
Quote from: igouroum on August 12, 2013, 12:15:42 PM
Here's a clip I shot yesterday afternoon. Shot with a Tamron 17-55 and the Latest (or one of the latest) Tragic Builds.
If only we weren't limited to 892p in full-sensor mode :(
Cheers!
nice.
you are not afraid to damage the sensor with direct sunlight?
Quote from: Rawolution on August 12, 2013, 12:36:15 PM
nice.
you are not afraid to damage the sensor with direct sunlight?
Not the slightest no :) I just make sure the sensor doesn't get flooded for extended periods of time, and that's about it ;)
Quote from: Andy600 on August 12, 2013, 02:07:35 AM
Mr 1% has done it again! We now have Dual ISO on the 50D 8) \o/ (Tragic Lantern only ATM)
Grab the latest Tragic Lantern build here: https://bitbucket.org/andy600/tl50d/downloads
Dual ISO only works in photo mode on the 50D so don't shoot in Live View.
Read a1ex's thread for how to use: http://www.magiclantern.fm/forum/index.php?topic=7139.msg59687#msg59687
You will need the conversion programs which are downloadable via a link in the first post of a1ex's thread. READ AT LEAST THE FIRST POST!!
Don't ask questions about it here. Follow the other thread and READ IT!
All thanks to 1% for the 50D port and a1ex, g3gg0 for this great feature.
p.s. also check whats under the star icon in the menu ;D
Great news! thanks to 1% & all the devs.
Looking forward to trying this out.
Quote from: Andy600 on August 11, 2013, 08:54:23 PM
Yeah, it can be a bit intimidating to post there but it seems like only a few of the users who are a bit obnoxious.
It looks like most shooters with that lens tend to go for a Helios 44:2 because of the flare and I have seen it paired with 35mm lenses on nex5's but you're probably best sticking to a 50mm. I personally wouldn't go the Helios route. It's hard to find a sharp V2 and there are plenty of decent, faster and cheap 50mm lenses out there that can flare. I have a 1974 Nikon F2 that would be ideal and it's sharp wide open.
I'm looking for my first anamorphic lens so I'm looking forward to seeing what the Moller looks like with raw on the 50D.
Thanks for that, I tried it with my Nikon 50mm AFD it it vignetted. Admittedly I was holding the anamorphic in front of the lens so not the most ideal test! I assume that if it vignettes on one 50mm it's going to do so on them all?
I've read a lot about the Helios 44m but like you said, opinions seem to vary. They sell for around £20 on ebay so I guess it might be worth a go to see what kind of copy I get.
Quote from: Supermac on August 11, 2013, 09:46:54 PM
Hi there,
Those old Moller lenses are very tricky to use and not very good really, also very difficult to sell too. Nobody wants them. I would be more than happy to take it off your hands for a small sum? :)
Ha ha, seriously, 50mm-85mm is the best range for a 2x 16mm Anamorphic on a crop sensor. Any less vignettes, any more you start to lose focus. Personally I'd say 50mm maybe a little wide especially with a 39mm rear thread. Helios is popular as 58mm is optimal focal length and has minimal vignetting. They can be pretty sharp but also "characterful". 55mm Takumar is not bad if you can find a sharp one but still vignettes, especially if you have to stop down. Clamp is really important too, you want to be as close to the taking lens as possible. Hope this helps, would love to see the results.
Cheers
Haha, yeah ok how's £5?! I need to fashion up some sort of clamp!
Quote from: johansugarev on August 11, 2013, 05:13:53 PM
You also have to interpret the footage as 24fps in you NLE.
Thanks too, I was getting confused about the fps in my NLE.
It probably won't work for video, there is one register and changeling it doesn't do anything. Either other regs aren't being recorded in the log or it only uses the one and is a lost cause here.
that is cool thing indeed!
but im facing trouble of post processing this dual iso files
it just doesnt work
(http://s019.radikal.ru/i612/1308/e9/407824467458.jpg)
modified
ah no it works fine! it just doesnt pick up underexposed pictures.
(http://s003.radikal.ru/i204/1308/0e/2e24f283cdad.jpg)
Quote from: 1% on August 12, 2013, 03:28:25 PM
It probably won't work for video, there is one register and changeling it doesn't do anything. Either other regs aren't being recorded in the log or it only uses the one and is a lost cause here.
oh yeah?
but there is HDR feauture in magic lantern
what is difference between dual iso and expo bracketing raw video shooting?
Quote from: Silkway on August 12, 2013, 05:22:55 PM
oh yeah?
but there is HDR feauture in magic lantern
what is difference between dual iso and expo bracketing raw video shooting?
With dual iso you can record with no motion problems, while in hdr video you have to pan slowly and record slow moving subjects, or you must record twice the fps speed you need (for example you must record 60fps if you want normal motion recording tolerance) otherwise strange ghost effects arise. On 50D you cannot do 60fps, so only on 550D you can (intended for a camera in the same price range). On the other hand, with dual iso movies, there is a lot of aliasing... very bad... so with some subjects it is almost unusable... surely this mode is not good at all for production purposes
Quote from: dlrpgmsvc on August 12, 2013, 05:34:08 PM
With dual iso you can record with no motion problems, while in hdr video you have to pan slowly and record slow moving subjects, or you must record twice the fps speed you need (for example you must record 60fps if you want normal motion recording tolerance) otherwise strange ghost effects arise. On 50D you cannot do 60fps, so only on 550D you can (intended for a camera in the same price range). On the other hand, with dual iso movies, there is a lot of aliasing... very bad... so with some subjects it is almost unusable... surely this mode is not good at all for production purposes
so u mean it really cuts down the fps in hdr mode?
yeah seems like 15 fps max if shot on 30 fps
not much for normal video stream.
Quote from: Silkway on August 12, 2013, 05:44:11 PM
so u mean it really cuts down the fps in hdr mode?
yeah seems like 15 fps max if shot on 30 fps
not much for normal video stream.
no, simply with 60fps you can record subjects that moves more fast with no ghosting effects, while at 30fps you can record moving subjects that moves half the speed than at 60fps. otherwise ghosting effects appears
Dual ISO on the 50D will not work in video mode! Use it for stills only.
Quote from: dlrpgmsvc on August 12, 2013, 05:48:31 PM
no, simply with 60fps you can record subjects that moves more fast with no ghosting effects, while at 30fps you can record moving subjects that moves half the speed than at 60fps. otherwise ghosting effects appears
ah you mean there is exposure ghosting effect?
oh that is not a problem to me)
im happy with hdr video then, even without dual iso
but i like dual iso for stills
because shooting hdr bracketing photos is impossible
that is where real ghosting comes up)
this dual iso for canon 50d is amazing!
check this out
a picture shot by me on 6400 iso 100% crop with dual iso from 100 iso
really?
(http://s020.radikal.ru/i711/1308/6c/c0ace5ddf8d6.jpg)
i wanted to buy a full frame camera for stills
because i like the low noise on high iso and high shutter speed
but now with this update for canon 50d from tragic lantern
it is just works like canon 1dx top level class full frame camera!
No dual iso for video :( oh well, how about that anamorphic preview though, really cool. Any chance of a 1.8 option, a lot of the common 2x anamorphics squeeze at around 1.8.
Cheers
Quote from: Silkway on August 12, 2013, 06:07:40 PM
i wanted to buy a full frame camera for stills
because i like the low noise on high iso and high shutter speed
but now with this update for canon 50d from tragic lantern
it is just works like canon 1dx top level class full frame camera!
Sure?
Quote from: ilguercio on August 12, 2013, 06:16:21 PM
Sure?
yeah
if u look image above
its 100% crop
i can blow it up print size 1 meter size and it will still be perfect looking photo
i see no point from now in full frame cameras at all...
???
Quote from: igouroum on August 12, 2013, 12:15:42 PM
Here's a clip I shot yesterday afternoon. Shot with a Tamron 17-55 and the Latest (or one of the latest) Tragic Builds.
If only we weren't limited to 892p in full-sensor mode :(
Cheers!
Great job Igouroum Wow!!! that video is awesome it really shows the potiential of the 50D. Keep shooting and posting new video, by the way what was your workflow?
Quote from: goldenchild9to5 on August 12, 2013, 06:31:04 PM
Great job Igouroum Wow!!! that video is awesome it really shows the potiential of the 50D. Keep shooting and posting new video, by the way what was your workflow?
Thanks! My workflow was very inefficient for this particular edit. ACR -> TIFF -> Final Cut X. Looking for a program to compile those TIFFs into a 422 video.. Any suggestions?
Also, I noticed ACR isn't very multicore optimised.. I'm rocking an 8-core 2006 Mac Pro, and it only seemed to use bout 50% of each core for the export even while reading and writing to an SSD, so yeah.. Kind of frustrating :P
Quote from: igouroum on August 12, 2013, 08:21:37 PM
Thanks! My workflow was very inefficient for this particular edit. ACR -> TIFF -> Final Cut X. Looking for a program to compile those TIFFs into a 422 video.. Any suggestions?
Also, I noticed ACR isn't very multicore optimised.. I'm rocking an 8-core 2006 Mac Pro, and it only seemed to use bout 50% of each core for the export even while reading and writing to an SSD, so yeah.. Kind of frustrating :P
Yeah you can compile them using Quicktime 7 Pro.. it compiles them as ProRes 422 and it's pretty quick also. Yeah ACR is kind of slow processing, but I'm gonna try to see if I'm getting the same thing. By way what version of ACR are you using?
Quote from: goldenchild9to5 on August 12, 2013, 08:52:54 PM
Yeah you can compile them using Quicktime 7 Pro.. it compiles them as ProRes 422 and it's pretty quick also. Yeah ACR is kind of slow processing, but I'm gonna try to see if I'm getting the same thing. By way what version of ACR are you using?
The one that comes with Photoshop CS6.
Quote from: igouroum on August 12, 2013, 09:02:58 PM
The one that comes with Photoshop CS6.
Ok Cool.. but do check out Quicktime 7 Pro to compile your tiffs it's pretty fast..
Well not to pee on the 50D but 600D+ and esp 6D (hopefully 70D, stay away from M/650D) upped the quality quite a bit. I have all these so I can compare and I've taken them out to shoot with.
The AF/exposure/etc is all faster on 6D and even 600D. ISO performance too. I also think we've caught canon in another 1/2 truth... max analog ISO for 50D is 1250 .. for 6D its 6400. Maybe ML thinking its 1600 is causing the green shadows... I know pink/green? highlight come from gain, ie. using ISO 50. Not sure if the numerical value is just a placeholder or actually used in post processing.
Full frame also really effects your lenses and DOF/FOV/etc. You don't *need* it but its nice to have.
The thing is, I never consider canon cameras for stills.
But i was looking towards Nikon new full frame line up.
Because of it's superb low noise in high ISO.
But canons are all good this days because of magic lantern.
Only thing compact flash card must be instead of sd card.
That's why i still look for 5d mark 3 but thats not the stills photo reason at all...
I mean to say - with dual ISO on canon i dont need to buy full frame nikon for stills.
But with magic lantern on 5d mark 3 it is of course has a lots of advantages, however if just compared without magic lantern full frame solutions - now canon 50d is just as good for me and better.
p.s. canon full frame top level 1dx doesnt have magic lantern. isnt it? so good comparison with 50d and its new dual iso capability then...
btw i have a question
there is 1080p compressed H.264 video at 30 fps on canon 50d
and there is a bitrate compression choices such as 1x,2x,3x
how does this show up in mb/sec?
is there any comparison with other DSLR videos?
or for example Panasonic GH3?
Quote from: 1% on August 13, 2013, 01:48:33 AM
Maybe ML thinking its 1600 is causing the green shadows... I know pink/green? highlight come from gain, ie. using ISO 50. Not sure if the numerical value is just a placeholder or actually used in post processing.
oh yeah indeed!
there is a green stuff going on on canon 50d dual iso...
and i dont know if it is suitable hmm...
in some way its not so bad of course
but would be nice to see the solution...
I will post some comparsions of 50d dual iso vs d7000,d300,d800 for you, but I will wait until it's more tested.
And honestly, the 50d is pretty bad at stills, it has a nasty filter (very soft) so it doesn't even stand up against 12mp cameras and the ISO performance is also not up to the task when compared to any modern camera (apsc,fullframe,m43,etc...).
Its not THAT bad but from taking it along I am def. cock blocked by performance on fast moving shots and low light... I wouldn't want to do an event with this camera. I do notice a bit of softness too compared to the higher models. When did this thing come out tho, 5-6 years ago?
The dual feature needs testing for sure, I wouldn't jump into production with it just yet. ESP since the converter is a little bit new. I'm just happy its ported atm and somewhat functioning. Its not going to be green forever.
@1% no matter what happens with the Dual ISO for video, the advances you have made so far are just plain awesome with Tragic 5 @Andy600 thank you as well Andy for compiling. I don't know if it's only me, or not but I've notice a slight improvement in noise using Tragic 5, Davinci seems to handle footage better. Got a serious video shoot coming up this month and I'm jumping all in with my beloved 50D will keep you guy's posted. On the hunt for another 50D body 8), Let the hunting begin...
So, I'm loving the Tragic Build. Great work there guys.
Also, pulled out that cheap nifty fifty to check it's sharpness at 3x crop mode. Absolutely sharp. What a great lens! This is a still from 2K footage at 3x crop. Of course, I used my Flatz Preset to render out a DNxHD and grade in resolve. No post sharpening added. You can download that here: www.dlwatson.net/flatz-preset.html
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/catcont1.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/catcont.jpg)
Click the image to see in full res
Quote from: araucaria on August 13, 2013, 03:52:10 AM
I will post some comparsions of 50d dual iso vs d7000,d300,d800 for you, but I will wait until it's more tested.
And honestly, the 50d is pretty bad at stills, it has a nasty filter (very soft) so it doesn't even stand up against 12mp cameras and the ISO performance is also not up to the task when compared to any modern camera (apsc,fullframe,m43,etc...).
yeah i dont need to see such comparisons coz i shoot myself with d7000 and 50d on daily basis
and i know that 50d is pretty awful in low light at high iso for stills
also not very sharp but kinda soft images compared to nikon d7000 (d800 same pixel density).
but
i like the picture coming from canon 50d, i like its unique and kinda juicy fat look
compared to flat digital and tack sharp look from nikon
thats why i was considering shooting on 50d stills even on awful noisy 1600 iso
but now with dual iso i can shoot 50d and make post processing and add noise reduction to raw images
and i get that nice and fat pictures i want, but with hell less noise on high iso
it is that much good, that really there is not much difference from it and full frame camera images at the end
but only problem is this green shadow and highlights
when this is done, then pretty much it is going to be the killer of all cameras ever...
Quote from: D.L. Watson on August 13, 2013, 09:30:16 AM
So, I'm loving the Tragic Build. Great work there guys.
Also, pulled out that cheap nifty fifty to check it's sharpness at 3x crop mode. Absolutely sharp. What a great lens! This is a still from 2K footage at 3x crop. Of course, I used my Flatz Preset to render out a DNxHD and grade in resolve. No post sharpening added. You can download that here: www.dlwatson.net/flatz-preset.html
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/catcont1.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/catcont.jpg)
Click the image to see in full res
hey can u explane this thing? im interested
what is flatz preset? is it just to make flat unsaturared picture for color grading?
i know u apply it in adobe camera raw in after effects import of dng files
but do you need to apply it to every frame or to sequence?
and why my after effects doesnt have output formats such ad DNxHD
maybe i have to update it?
and what is it unique about da vinci and why use it?
i mean can u suggest after effects plug in alternative to work with your flatz preset
also i cant even export to prores 4444 or anything...
my adobe cs6 is kinda empty...
this is what ive got after using your preset
btw this i did on 640 by 240 resolution raw on canon 50d on iso 1600 or so...
coz i wanted to test raw video on old compact flash card from kingston
it is speed around 6 mb/sec 24fps
compared to my other card which is lexar x1000 55 mb/sec
that can record something around 1585 by 900 or more
(http://s018.radikal.ru/i501/1308/62/8522aa98e4f0.jpg)
not so bad for 6 mb/sec 24fps raw recording isnt it?
hey people what iso you shoot raw video on canon 50d?
Quote from: 1% on August 13, 2013, 01:48:33 AM
Well not to pee on the 50D but 600D+ and esp 6D (hopefully 70D, stay away from M/650D) upped the quality quite a bit. I have all these so I can compare and I've taken them out to shoot with.
The AF/exposure/etc is all faster on 6D and even 600D. ISO performance too. I also think we've caught canon in another 1/2 truth... max analog ISO for 50D is 1250 .. for 6D its 6400. Maybe ML thinking its 1600 is causing the green shadows... I know pink/green? highlight come from gain, ie. using ISO 50. Not sure if the numerical value is just a placeholder or actually used in post processing.
Full frame also really effects your lenses and DOF/FOV/etc. You don't *need* it but its nice to have.
So the 50D is actually 200 - 1250 ISO ??? everything else is digitally amplified?
Quote from: Andy600 on August 13, 2013, 01:06:23 PM
So the 50D is actually 200 - 1250 ISO ??? everything else is digitally amplified?
to me that is just sufficient
and for most pro photographers
if ISO 1250 going to give look of ISO 200 with dual iso upgrade on canon 50d
it is just as good as what high end full frame sensors are giving
or even better than that
shooting ISO 1250 (or 1600) is okay
and if i get picture as if i shot on ISO 200
thats all i need from stills...
Quote from: Silkway on August 13, 2013, 01:14:54 PM
to me that is just sufficient
and for most pro photographers
if ISO 1250 going to give look of ISO 200 with dual iso upgrade on canon 50d
it is just as good as what high end full frame sensors are giving
or even better than that
shooting ISO 1250 (or 1600) is okay
and if i get picture as if i shot on ISO 200
thats all i need from stills...
Good for you :) I know a lot of pros who would disagree with that. For ISO and DR, the 50D is inferior to most Rebels and certainly inferior to the newer cameras but it's still good for the money. TBH I just saw some footage from the Digital Bolex and IMO the 50D easily matches it.... probably betters it.
I highlighted the ISO range not for dual ISO but for raw video (although it will have relevance to Dual ISO too) because if this is the case it will be better to shoot within the ISO limitations of the camera and increase/decrease exposure etc in post. It's all about getting the best SNR and DR from the sensor no matter what it's specific limitations are. Digitally amplifying ISO in-camera can be inferior to doing it in an image editing app AFIK.
duplicate post - ignore
Quote from: Andy600 on August 13, 2013, 01:26:27 PM
Good for you :) I know a lot of pros who would disagree with that. For ISO and DR, the 50D is inferior to most Rebels and certainly inferior to the newer cameras but it's still good for the money. TBH I just saw some footage from the Digital Bolex and IMO the 50D easily matches it.... probably betters it.
I highlighted the ISO range not for dual ISO but for raw video (although it will have relevance to Dual ISO too) because if this is the case it will be better to shoot within the ISO limitations of the camera and increase/decrease exposure etc in post. It's all about getting the best SNR and DR from the sensor no matter what it's specific limitations are. Digitally amplifying ISO in-camera can be inferior to doing it in an image editing app AFIK.
yeah but woops...
i shot this in dual iso 200-800 ("within limitations")
and still green cast is there...
(http://s017.radikal.ru/i410/1308/9a/75a74549e375.jpg)
and yeah this is 100% crop of the raw file processed in dual iso with noise reduction applied
i dont know why, but i just like the way it looks.
all the rebels and even canon full frame cameras such as 5d mark 3 doesnt give this look...
this is fat juicy look from 1dx, 1dc cameras... and kinda shadow blur. canon 50d stills looks warm and professional to me
P.S. sorry for dual post - i hate it too. i accidently did it coz click "quote" instead of "modify" and couln't delete so just modified it.
@Silkway - The green cast is there probably for the reasons 1% described earlier. Dual ISO on the 50D is a 'work in progress'.
For raw video, the 50D certainly does have a 'look' to it. I like it. I love the 5d3's raw video and the 7D is looking like it could be great too.
Quote from: Andy600 on August 13, 2013, 01:37:22 PM
@Silkway - The green cast is there probably for the reasons 1% described earlier. Dual ISO on the 50D is a 'work in progress'.
For raw video, the 50D certainly does have a 'look' to it. I like it. I love the 5d3's raw video and the 7D is looking like it could be great too.
Yeah it has a look in stills as well. A different thing probably, but also unique and fancy.
Yeah i thought 1% said that the reason of green cast is going beyond limits of actual ISO ability of canon 50d.
If thats not the case, looking forward to know what is the reason...
@silkway @andy600
I don't know why but my first video with the latest TL had same green awful colors and it was impossible to recover.
I turned off the camera, checked every setting, shot a second video, and everything was fine.
But first video was exactly like that, awfully green.
So, probably it's a matter of some setting.
Quote from: Silkway on August 13, 2013, 02:21:28 PM
Yeah it has a look in stills as well. A different thing probably, but also unique and fancy.
Yeah i thought 1% said that the reason of green cast is going beyond limits of actual ISO ability of canon 50d.
If thats not the case, looking forward to know what is the reason...
The 50D is probably using different ISO values than what Dual ISO is expecting. Dual ISO was developed on the 5d3 and 7D which have different FW, ISO ranges and sensors than the 50D
Quote from: riccardocovino on August 13, 2013, 02:23:31 PM
@silkway @andy600
I don't know why but my first video with the latest TL had same green awful colors and it was impossible to recover.
I turned off the camera, checked every setting, shot a second video, and everything was fine.
But first video was exactly like that, awfully green.
So, probably it's a matter of some setting.
Was that after trying Dual ISO?
Also uniwb?
[OT]
Just as predicted, the BMPCC is shipping without raw
http://www.redsharknews.com/technology/item/981-redshark-exclusive-first-look-at-the-blackmagic-pocket-cinema-camera?page=1
Should I wait before trying Dual ISO in photo mode? Is it safe enough right now? Is there an easy conversion tool for Mac?
Quote from: Silkway on August 13, 2013, 11:46:50 AM
hey can u explane this thing? im interested
what is flatz preset? is it just to make flat unsaturared picture for color grading?
i know u apply it in adobe camera raw in after effects import of dng files
but do you need to apply it to every frame or to sequence?
and why my after effects doesn't have output formats such ad DNxHD
maybe i have to update it?
and what is it unique about da vinci and why use it?
i mean can u suggest after effects plug in alternative to work with your flatz preset
also i cant even export to prores 4444 or anything...
my adobe cs6 is kinda empty...
this is what ive got after using your preset
btw this i did on 640 by 240 resolution raw on canon 50d on iso 1600 or so...
coz i wanted to test raw video on old compact flash card from kingston
it is speed around 6 mb/sec 24fps
compared to my other card which is lexar x1000 55 mb/sec
that can record something around 1585 by 900 or more
(http://s018.radikal.ru/i501/1308/62/8522aa98e4f0.jpg)
not so bad for 6 mb/sec 24fps raw recording isnt it?
Hey there Silkway.
I'm not sure why your image is cast green - there must be a white balance issue. The preset does not affect your white balance - that you must set yourself using the eye drop tool in ACR.
The flatz preset does not manipulate saturation - it uses tonemapping to get as much detail out of your shadows and highlights to be able to render to a more manageable file format for grading. You apply it to a sequence, but you can also use Bridge to apply it to all of your DNG's at once if you prefer.
To get the DNxHD file formats, you need to download them from AVID here: http://avid.force.com/pkb/articles/en_US/Compatibility/en350875
Davinci is a powerful industry standard color correction software. Naturally, I prefer it for professional work. Unlike Adobe AE, it provides you with a RGB Parade to see if your grades/colors are broadcast legal.
Here is a workflow video I did quickly covering the basics of this preset:
Quote from: D.L. Watson on August 13, 2013, 04:42:57 PM
Hey there Silkway.
I'm not sure why your image is cast green - there must be a white balance issue. The preset does not affect your white balance - that you must set yourself using the eye drop tool in ACR.
about cat from raw video? it is not green. i just color graded it so it looks green
but the dual iso stills are green by themselves
in some way it is good - ready color grading in raw hehe
Quote from: D.L. Watson on August 13, 2013, 04:42:57 PM
The flatz preset does not manipulate saturation - it uses tonemapping to get as much detail out of your shadows and highlights to be able to render to a more manageable file format for grading. You apply it to a sequence, but you can also use Bridge to apply it to all of your DNG's at once if you prefer.
To get the DNxHD file formats, you need to download them from AVID here: http://avid.force.com/pkb/articles/en_US/Compatibility/en350875
Thanks for the link. I will check it out. Also probably the Apple ProRes must be downloaded same way?
Quote from: D.L. Watson on August 13, 2013, 04:42:57 PM
Davinci is a powerful industry standard color correction software. Naturally, I prefer it for professional work. Unlike Adobe AE, it provides you with a RGB Parade to see if your grades/colors are broadcast legal.
Here is a workflow video I did quickly covering the basics of this preset:
Yeah ive seen your workflow tutorial. But this doesnt cover the work in Da Vinci software.
So if you can make one, i would love to learn from you!
because i loaded my DNG files with cat
i applied your preset Flatz
it made it kinda flat
then i try after effects to enhance the sequence
but i couldnt make it shine, as it shown on your tutorial
i need your tips about Da Vinci post processing... to make my raw look like yours (even i used low resolution)
@Silkway - might I suggest you look here: http://www.magiclantern.fm/forum/index.php?board=14.0
Grading and workflow has been covered extensively.
Quote from: Andy600 on August 13, 2013, 02:32:30 PM
Was that after trying Dual ISO?
no, I didn't try dual ISO.
Just put the build in the CF and first video was all green, darker than liveview, with insane contrast.
Quote from: Andy600 on August 13, 2013, 01:26:27 PM
Good for you :) I know a lot of pros who would disagree with that. For ISO and DR, the 50D is inferior to most Rebels and certainly inferior to the newer cameras but it's still good for the money. TBH I just saw some footage from the Digital Bolex and IMO the 50D easily matches it.... probably betters it.
I highlighted the ISO range not for dual ISO but for raw video (although it will have relevance to Dual ISO too) because if this is the case it will be better to shoot within the ISO limitations of the camera and increase/decrease exposure etc in post. It's all about getting the best SNR and DR from the sensor no matter what it's specific limitations are. Digitally amplifying ISO in-camera can be inferior to doing it in an image editing app AFIK.
You right Andy the 50D seems to surpass the Digital Bolex footage.. makes me love my 50D even more now.
Hi everybody,
I am new to raw recording on the 50d and I wanted to ask if any resolutions higher than 2000*1080 will be available to use in future builds.
Thanks
Hey new to the forums, but not to magic lantern :)
Just want to tell you people how awesome you are. Big love for magic lantern.
I have a question to acctually,
How come you can't record in 1080p without crop? Because of the cf card speeds or camera write limitations? Shooting in crop is a hell for framing :p
And can you playback your recorded raw footage? Seems like I can't find that option?
thanks!
Quote from: SebaVuye on August 13, 2013, 10:42:08 PM
Hey new to the forums, but not to magic lantern :)
Just want to tell you people how awesome you are. Big love for magic lantern.
I have a question to acctually,
How come you can't record in 1080p without crop? Because of the cf card speeds or camera write limitations? Shooting in crop is a hell for framing :p
And can you playback your recorded raw footage? Seems like I can't find that option?
thanks!
In tragic lantern there is a ML preview which is a low fps black and white live view hack which shows the exact framing, it has some limitations but it works. You can't record 1080 outside of cropmode.
Quote from: araucaria on August 13, 2013, 10:48:09 PM
In tragic lantern there is a ML preview which is a low fps black and white live view hack which shows the exact framing, it has some limitations but it works. You can't record 1080 outside of cropmode.
Ah thanks! Didn't know that. Is 1080p recording in no crop something realistic to archive or more like something impossible? :p
Quote from: SebaVuye on August 13, 2013, 10:54:13 PM
Ah thanks! Didn't know that. Is 1080p recording in no crop something realistic to archive or more like something impossible? :p
It's impossible. I know it's hard to find answers in such big topic, but that was explained: the RAW image is from the LiveView image, which uses only one line of pixels at each three lines. So, 4752/3 is 1584.
Quote from: Andy600 on August 13, 2013, 03:32:35 PM
[OT]
Just as predicted, the BMPCC is shipping without raw
Oh boy...all my prayers useless.
:-\
Quote from: Andy600 on August 13, 2013, 05:17:44 PM
@Silkway - might I suggest you look here: http://www.magiclantern.fm/forum/index.php?board=14.0
Grading and workflow has been covered extensively.
Oh thank you sir!
Its exciting to get adressed messages from a person who actually compiled our magic software that sits in our favourite canon 50d and makes us happy =)
I find some interesting articles there such as RAW and audio syncing.
But I still want to get the tutorial from D.I.Watson
simply because it is his unique author workflow
and because what i see from his works is exactly what i like
and i would love to be able to do similar stuff in my post production for footage i get from canon 50d raw video)
p.s. also excited about communications with mister 1%
who is actually we expect fixes green cast on dual iso of canon 50d)
a little off topic
when i first heard about magic lantern
i thought deveplopers must be about green lantern the movie
and now when we see green stuff in dual iso raw stills of canon 50d
that thought comes in my mind - its green because its green lantern)
Is it technically possible for 50D to do dual iso raw video?
Actually I have a question that I couldn't find answers to earlier in the forum, why can't we get more than 1080 vertical resolution in crop mode?
Cheers
It seems to use only 1 reg in video mode.. I tried setting it manually and nothing happened.
Okay, there have been popping up presets for After Effects/Adobe to get flat pictures, import or render them to 10bit and apply luts or whatever. I've also read people complaining about flickering in ACR.
So far so good, I remember that on LRtimelapse (nice program) there is a general consens to not use highlight recovery, black , white, shadows,etc... because they are not linear but some "secret sauce" which depends on the scene. This doesn't matter to stills (which it was designed for) but when movement comes into play this can actually generate flicker. It does not always happen, but sometimes you get the flickering.
To avoid this, I have "created" two a camera profiles which give you a very flat picture style and some desaturation. This is just a test as I'm not an expert but I think it works fine (tried out with the 50d raw video with cdng files). I will look into it again when I have some time. Here are the camera profiles:
https://www.dropbox.com/s/sxxj82szbimxn8f/MLfilm%20slight.dcp
https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
You have to put them into c:/users/"your username"/AppData/Roaming/Adobe/CameraRaw/CameraProfiles
Afterwards they should appear under the camera calibration tab.
Quote from: Molinsky on August 13, 2013, 11:05:40 PM
It's impossible. I know it's hard to find answers in such big topic, but that was explained: the RAW image is from the LiveView image, which uses only one line of pixels at each three lines. So, 4752/3 is 1584.
Ah damn. Thanks for the help.
Quote from: araucaria on August 14, 2013, 04:58:11 AM
Okay, there have been popping up presets for After Effects/Adobe to get flat pictures, import or render them to 10bit and apply luts or whatever. I've also read people complaining about flickering in ACR.
So far so good, I remember that on LRtimelapse (nice program) there is a general consens to not use highlight recovery, black , white, shadows,etc... because they are not linear but some "secret sauce" which depends on the scene. This doesn't matter to stills (which it was designed for) but when movement comes into play this can actually generate flicker. It does not always happen, but sometimes you get the flickering.
To avoid this, I have "created" two a camera profiles which give you a very flat picture style and some desaturation. This is just a test as I'm not an expert but I think it works fine (tried out with the 50d raw video with cdng files). I will look into it again when I have some time. Here are the camera profiles:
https://www.dropbox.com/s/sxxj82szbimxn8f/MLfilm%20slight.dcp
https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
You have to put them into c:/users/"your username"/AppData/Roaming/Adobe/CameraRaw/CameraProfiles
Afterwards they should appear under the camera calibration tab.
On a Mac you have to:
- Download and install the DNG Profile Editor (http://www.adobe.com/support/downloads/detail.jsp?ftpID=5493) from Adobe
- File -> Open an DNG image
- Under Base Profile load the custom .dcp camera profile
- File -> Export Profile, which will save it in the correct folder, so you can use it in AE or PS
Quote from: PressureFM on August 14, 2013, 11:43:39 AM
On a Mac you have to:
- Download and install the DNG Profile Editor (http://www.adobe.com/support/downloads/detail.jsp?ftpID=5493) from Adobe
- File -> Open an DNG image
- Under Base Profile load the custom .dcp camera profile
- File -> Export Profile, which will save it in the correct folder, so you can use it in AE or PS
I think you will have to do the same on windows.
Quote from: araucaria on August 14, 2013, 04:58:11 AM
Okay, there have been popping up presets for After Effects/Adobe to get flat pictures, import or render them to 10bit and apply luts or whatever. I've also read people complaining about flickering in ACR.
To avoid this, I have "created" two a camera profiles which give you a very flat picture style and some desaturation. This is just a test as I'm not an expert but I think it works fine (tried out with the 50d raw video with cdng files). I will look into it again when I have some time. Here are the camera profiles:
https://www.dropbox.com/s/sxxj82szbimxn8f/MLfilm%20slight.dcp
https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
You have to put them into c:/users/"your username"/AppData/Roaming/Adobe/CameraRaw/CameraProfiles
Afterwards they should appear under the camera calibration tab.
oh this is cool
but can u also add some samples of your final video
and most important your color grading step by step workflow
The final look is up to you, with this, adjusting your exposure in ACR, and then some curve plus some lut in After Effects you can get a quick grade if that's what you are looking for.
Quote from: araucaria on August 14, 2013, 04:58:11 AM
Okay, there have been popping up presets for After Effects/Adobe to get flat pictures, import or render them to 10bit and apply luts or whatever. I've also read people complaining about flickering in ACR.
So far so good, I remember that on LRtimelapse (nice program) there is a general consens to not use highlight recovery, black , white, shadows,etc... because they are not linear but some "secret sauce" which depends on the scene. This doesn't matter to stills (which it was designed for) but when movement comes into play this can actually generate flicker. It does not always happen, but sometimes you get the flickering.
To avoid this, I have "created" two a camera profiles which give you a very flat picture style and some desaturation. This is just a test as I'm not an expert but I think it works fine (tried out with the 50d raw video with cdng files). I will look into it again when I have some time. Here are the camera profiles:
https://www.dropbox.com/s/sxxj82szbimxn8f/MLfilm%20slight.dcp
https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
You have to put them into c:/users/"your username"/AppData/Roaming/Adobe/CameraRaw/CameraProfiles
Afterwards they should appear under the camera calibration tab.
Do these profiles include the 50D's noise patterns and other things ACR has specifically profiled for the camera, or are just flat profiles?
Quote from: johansugarev on August 14, 2013, 04:24:45 PM
Do these profiles include the 50D's noise patterns and other things ACR has specifically profiled for the camera, or are just flat profiles?
Just flat.
Any way of creating a duplicate of the 50D profile ACR has but without the highlight/shadow voodoo that causes flickering?
Or is it a good idea to use the embeded 50d profile first (i work with cdng from raw magic) to denoise and sharpen, export in dng and run through camera raw again with your profile and adjust the highlight/shadow areas if needed?
Yeah, thats why i want mister D.I.Watson to show his grading workflow.
Coz many people do many stuff, but they never do what he did...
There is no magic key to grading, watch tutorials and learn...
Quote from: johansugarev on August 14, 2013, 04:55:38 PM
Or is it a good idea to use the embeded 50d profile first (i work with cdng from raw magic) to denoise and sharpen, export in dng and run through camera raw again with your profile and adjust the highlight/shadow areas if needed?
Oh, wait! I didn't know about a 50D profile. My test footages are all super-noisy. Where can I find a way to deal with it? Everyone says something different.
You will have to tell us a little bit more about your noisy footage. Anyway, usually, to avoid noise you will try to expose (changing the shutter speed and aperture) to the maximum, and use the lowest iso you can. This will give you the best you can get in terms of noise.
If you are trying to film a concert or anything dark, get another camera.
Quote from: araucaria on August 14, 2013, 06:49:33 PM
You will have to tell us a little bit more about your noisy footage. Anyway, usually, to avoid noise you will try to expose (changing the shutter speed and aperture) to the maximum, and use the lowest iso you can. This will give you the best you can get in terms of noise.
If you are trying to film a concert or anything dark, get another camera.
Well, that sure answers my question. Thanks! Since I'm a day worker, all my test footages had been shot at night. And I exposed to the limit of acceptable, not to the maximum. Looks like it works like the BMCC footage.
Playing around with RAW again. This time using the insanely sharp and quite affordable nifty fifty lens.
Workflow:
RAW > ACR > Apply Flatz Preset (http://www.dlwatson.net/flatz-preset.html) > Render to DNxHD > Edit & Color Correct/Grade in Premiere
@DL Watson Apology for missing it somewhere, but which 50mm lens are you using? I have the 50mm EF 1.8 and 50mm fd 1.4
Quote from: fromdecember on August 14, 2013, 08:01:37 PM
@DL Watson Apology for missing it somewhere, but which 50mm lens are you using? I have the 50mm EF 1.8 and 50mm fd 1.4
The cheap $125 EF 50mm f/1.8 II.
Anyone have suggestions on extra batteries? Mine dies way to fast.
Quote from: fromdecember on August 14, 2013, 11:39:16 PM
Anyone have suggestions on extra batteries? Mine dies way to fast.
Buy some more and swap them over? Or get a battery grip and stick 2 in it.
I bought a couple of these, cheap and work fine.
http://www.amazon.co.uk/Duracell-Replacement-Digital-Camera-Battery/dp/B0015YAER4/ref=sr_1_1?ie=UTF8&qid=1376519234&sr=8-1&keywords=BP-511 (http://www.amazon.co.uk/Duracell-Replacement-Digital-Camera-Battery/dp/B0015YAER4/ref=sr_1_1?ie=UTF8&qid=1376519234&sr=8-1&keywords=BP-511)
Not sure what you're asking really, there's no magic cure for power consumption...
I just had a look at that footage from the Digital Bolex camera that some people mentioned.
Didn't like it at all, could just be the way it was shot but it looked pretty videoish to me. It just doesn't have the same filmic motion cadence that I've come to like with the 50D.
If only we could get Mosaic to make us a filter to take our moire worries away. I never heard back from them, how about anyone else?
I doubt they will do a vaf filter for the 50D, if you think of it there might be 1000people maximum using the 50d for raw video, and most of them just to try out raw for a few $. I don't think they would sell more than 100 vaf filters.
Quote from: araucaria on August 15, 2013, 01:44:06 AM
I doubt they will do a vaf filter for the 50D, if you think of it there might be 1000people maximum using the 50d for raw video, and most of them just to try out raw for a few $. I don't think they would sell more than 100 vaf filters.
If you get some Cellophane, smear some vaseline on it and put it over the sensor it makes a great VAF filter.
I've been in direct contact with Mosaic Engineering. In fact, I am sending them a 50D tomorrow so that they can fit and design the new VAF filter!!! This is going to rock!
Quote from: LEVISDAVIS on August 15, 2013, 03:31:26 AM
I've been in direct contact with Mosaic Engineering. In fact, I am sending them a 50D tomorrow so that they can fit and design the new VAF filter!!! This is going to rock!
awesome!
Quote from: LEVISDAVIS on August 15, 2013, 03:31:26 AM
I've been in direct contact with Mosaic Engineering. In fact, I am sending them a 50D tomorrow so that they can fit and design the new VAF filter!!! This is going to rock!
Great initiative Levis, we should contact them and express interest in buying a filter for the 50D - if there's enough interest for even a single run of them it would be great!
Here's their email address - just de-spam it. contact (then the at sign) mosaicengineering.com, I've sent my enquiry ;D
Hello
im new here
i have 50d on which i installed ML which is working great ,giving me h264 video but im not getting raw video option.As i searched more i came to knw that there was no modules folder in my ML Folder (on my CF card).So i copied them but still im Not getting M option in my ML option mode
Plz Plz help me
shamin
Quote from: shaminkulkarni on August 15, 2013, 08:12:16 AM
Hello
im new here
i have 50d on which i installed ML which is working great ,giving me h264 video but im not getting raw video option.As i searched more i came to knw that there was no modules folder in my ML Folder (on my CF card).So i copied them but still im Not getting M option in my ML option mode
Plz Plz help me
shamin
Welcome Shamin :)
Go here and download the top one: https://bitbucket.org/andy600/tl50d/downloads
Overwrite the files on your card and keep the directory structure intact.
[possible bug] I had a message from a user on Vimeo who has reported that he can't change aperture when 'small hacks' is enabled for raw video (latest Tragic Lantern build). Can anyone confirm this? Try to change aperture with small hacks enabled and disabled. I only have manual lenses so I can't test it myself.
@ andy600
thanks friend i tried doing the way u suggested! it worked it is recording raw ! bt after recodring around 1 gb it is saying 1 frame dropped n its stoping automatically! im using sandisc extreme CFcard (16gb) which has speed of 60mb\ps
whats this new problem coming up?
Quote from: LEVISDAVIS on August 15, 2013, 03:31:26 AM
I've been in direct contact with Mosaic Engineering. In fact, I am sending them a 50D tomorrow so that they can fit and design the new VAF filter!!! This is going to rock!
I'm eating my words rigght now ^^ good news.
Quote from: Andy600 on August 15, 2013, 09:56:16 AM
[possible bug] I had a message from a user on Vimeo who has reported that he can't change aperture when 'small hacks' is enabled for raw video (latest Tragic Lantern build). Can anyone confirm this? Try to change aperture with small hacks enabled and disabled. I only have manual lenses so I can't test it myself.
Andy:
No problem to change aperture with my Canon Lens 24/70mm 2.8
My lenses are: Nikon 50mm 1.4, Bronica 645 40mm, 75mm,150mm and Mamiya 210mm - all manual
I got:
With peak focus enable 62mb with KomputerBay 64
Peak focus disable 76mb
This the best build I have tested, very stable
Many thanks
Clovis
Quote from: Andy600 on August 15, 2013, 09:56:16 AM
[possible bug] I had a message from a user on Vimeo who has reported that he can't change aperture when 'small hacks' is enabled for raw video (latest Tragic Lantern build). Can anyone confirm this? Try to change aperture with small hacks enabled and disabled. I only have manual lenses so I can't test it myself.
No problem here either. Tested on 3 lenses. Do they have Exp. Overide on?
Hello everyone.
@dsManning Exp. Overide was on. Can you change it while recording at the same time when 'small hacks' is enabled ?
I'm using Canon 50mm and the Sigma 30mm 1.4
Quote from: Eran on August 15, 2013, 01:56:12 PM
Hello everyone.
@dsManning Exp. Overide was on. Can you change it while recording at the same time when 'small hacks' is enabled ?
I'm using Canon 50mm and the Sigma 30mm 1.4
Right you are. Sorry for the false info, I don't think anyone specified to test WHILE recording. Does not work here either. Don't mess with aperture while recording much personally, because it is so clunky on auto lenses, it usually gives me camera shake. I wonder if the new cine lenses have a problem with this? Since those are digital, but have a smooth aperture ring. Was going to buy one of those, but just built a new hackintosh, so money is tight!
EDIT A quick upload of some harsh light/shadow shots from yesterday. Editing on a new machine is a whole new experience :)
Someone said earlier that the analog ISO on the 50D is from 200 to 1250; does that mean that 200 is better than 100 (i.e. more dynamic range and not digitally amplified)?
@shaminkulkarni Welcome to the 50D club you will Love it 8)
Quote from: johansugarev on August 15, 2013, 07:33:58 PM
Someone said earlier that the analog ISO on the 50D is from 200 to 1250; does that mean that 200 is better than 100 (i.e. more dynamic range and not digitally amplified)?
From my research 100 ISO is noisier even 200 ISO is noisy.. I would say to stay between 400-800 ISO for cleaner video output.
Anyone to confirm what goldenchild9to5 has tested?
Got the 50D out in the mail today to reach Mosaic Engineering!
Got plenty of time to think about it... But, what would you consider an appropriate testing procedure for the 50D and the VAF?
Quote from: johansugarev on August 16, 2013, 02:25:10 AM
Anyone to confirm what goldenchild9to5 has tested?
Here, I did a 50D ISO test. Click on the image to see in full-res.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1s.jpg)
ISO test with RAW set to normal exposure.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/isos.jpg)
ISO test with RAW Exposure set to 5+
Looks like ISO 100 and 200 are very close. Hope this helps!
Thanks for the ISO test... Definitely keeps things in perspective when exposing to the right. I'm astonished to see how well ISO 500 is holding up. Thanks again.
Quote from: D.L. Watson on August 16, 2013, 07:47:08 AM
Here, I did a 50D ISO test. Click on the image to see in full-res.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1s.jpg)
ISO test with RAW set to normal exposure.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/isos.jpg)
ISO test with RAW Exposure set to 5+
Looks like ISO 100 and 200 are very close. Hope this helps!
Awesome stuff, did you have a look at 1250?
Here is the little music/promo/teaser video i'v made with 50D RAW...this was the first experience and i think i can't go back to H264 mode ever!
Quote from: D.L. Watson on August 16, 2013, 07:47:08 AM
Here, I did a 50D ISO test. Click on the image to see in full-res.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso1s.jpg)
ISO test with RAW set to normal exposure.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/iso.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/isos.jpg)
ISO test with RAW Exposure set to 5+
Looks like ISO 100 and 200 are very close. Hope this helps!
The 3200 looks better than 1600. ???
Quote from: Molinsky on August 16, 2013, 02:15:04 PM
The 3200 looks better than 1600. ???
Looks identical to me... probably because it is ::)
...and ISO 1250 will no doubt look the same too
Quote from: Andy600 on August 16, 2013, 02:39:44 PM
Looks identical to me... probably because it is ::)
...and ISO 1250 will no doubt look the same too
Nah, 3200 looks tightly better to me - or less worse. There's almost a red block above the "1600" tag. But, then again, in
this image. Probably, like you said, the higher ISOs are not practically different.
It seems there is no point of going above ISO 1600 on this camera - they are all digitally amplified after 1250 or so. Also, DxOmark measured ISO 100 to be 157 and ISO 200 to be 158 - so in real world conditions they should be about the same. The question is which has more dynamic range. Oddly enough they start their dynamic range test at ISO 200, measuring 11.4 stops.
It seems many sensors are geared toward ISO 200, and ISO 100 is just negative digital amplification. Don't know if this is the case for the 50D, but I've heard a lot of Nikons are like that. I am still waiting for someone to tell me to forget ISO 100 and always use 200, though.
Quote from: Viente on August 16, 2013, 10:56:52 AM
Here is the little music/promo/teaser video i'v made with 50D RAW...this was the first experience and i think i can't go back to H264 mode ever!
no offense
it looks stupid to me)
Quote from: Molinsky on August 16, 2013, 03:50:03 PM
Nah, 3200 looks tightly better to me - or less worse. There's almost a red block above the "1600" tag. But, then again, in this image. Probably, like you said, the higher ISOs are not practically different.
yeah probably everyone should avoid 1600 iso
better to use 800 and 3200
probably the best way to manage dual iso is
use 200 and 3200
cpz using 800 has no sense
it is clean by itself
Quote from: Silkway on August 16, 2013, 05:21:18 PM
no offense
it looks stupid to me)
I don't think anybody needs a retarded comment like yours, if it
looks stupid (whatever that is) to you, at least explain yourself, otherwise you're a troll.
Greetings
Quote from: Silkway on August 16, 2013, 05:21:18 PM
no offense
it looks stupid to me)
Thx for comment!
Exuse me for OT but what exactly is stupid?
Its my first experience in shooting, so i appreaciate any feedback.
Quote from: Viente on August 16, 2013, 05:39:28 PM
Thx for comment!
Exuse me for OT but what exactly is stupid?
Its my first experience in shooting, so i appreaciate any feedback.
Way to stay positive, but I wouldn't even preemptively appreciate feedback from someone who is going to toss that at you. Such a shame, it has had such a good vibe on these boards for so long....
Colour looks good, it really fits the mood of the scene (especially in the beginning on the stairs). I like your timing as well, good cuts timed well with the audio.
(compliment sandwich part) In my opinion, the second half of the video was TOO far from the first half. I realize it is supposed to be a complete 180 from what is going on in the first half, but at some points I almost forgot about the intro with the car. So this has nothing to do with your shooting or processing, just editing. Perhaps halfway through the second half, sprinkle an element of the beginning in there. As I said, more storyboard/editing than shooting.
Loved the cloud scene when he woke up in the field. Very 'Breaking Bad' super wide, most of the frame is the sky type of shot. :)
Let me explain myself, if you all ask for it.
It looks stupid to me for some reason that is about a person who did it.
I just don't think this is good example of use of such a great tool as magic lantern presented us with canon 50d.
and the clip above i could make it on my old nokia phone =)
but I won't do it. because it is silly) silly storyboard and editing as stated above.
and the silliest thing is the way of using canon 50d in such way.
its like cutting away all dynamic range and 14 bit color and everything
its also post processed and codec and fps was all messed up probably...
i dont know, this just doesnt make any sense to me.
and yes
this clip would be 100x better if the author would not touch color grading at all.
just leave it as its shot and even at that point it would be much better.
Quote from: Viente on August 16, 2013, 10:56:52 AM
Here is the little music/promo/teaser video i'v made with 50D RAW...this was the first experience and i think i can't go back to H264 mode ever!
It doesn't look stupid.
It's not really my sort of video but you do have some nice shots in there and the green grading gives it a kind of Matrix vibe. Didn't see much aliasing or moire either.
Keep it up!
Quote from: Silkway on August 16, 2013, 05:21:18 PM
no offense
it looks stupid to me)
You with your green cat and constant requests on step-by-step colorgrading tutorials think THIS looks stupid??
Please show us some of your work - And not just your tests!
Regards,
ezpRado
also what is stupid is this few things
i was expecting guy to start singing
it is stupid that he didnt
also the people shots are not correct
the camera work is awful composition
editing is awful
u cant stick close up and wide shots after each other with such huge gap
also stupid things is almost everything
only good shot was on 2:08 second and girl on 1:36 look pretty and make sense.
Thx for all your feedback guys, but please not offence each other :)
Stay positive :)
Quote from: ezpRado on August 16, 2013, 06:31:11 PM
You with your green cat and constant requests on step-by-step colorgrading tutorials think THIS looks stupid??
Please show us some of your work - And not just your tests!
Regards,
ezpRado
of coz i might show when i make something on canon 50d
now i can only show what i did on nikon d7000 which is not this topic discussion)
my green cat was made on 640 by 240 pixel
which is less than my old nokia n86 can do
it is raw video 14 bit color 24 frame per second on 6 mb/sec continuous non stop raw video
on kingston 10 years old compact flash old technology card
(http://www.my-batteries.net/images/memory-card/KINGSTON-COMPACT-FLASH-CF-MEMORY-CARD-TDCF01.jpg)
3 times less consuming than h.264 codec compressed on Nikon D7000
which is also very very light and compressed video shooter
so i just set a new record of raw shooting with that green cat shot for most less consuming raw shoot) that was fun
to show that the quality is not so bad
when it comes to a memory card speed for continuous shooting on low resolution in raw
also i dont ask shit people for their step by step color grading
i ask from the master of art like D.I.Watson
i said clip above was stupid except for one shot
so to prove you i just made a screen shot of the 2:08 seconds shot of this clip above
check it and judge for yourself.
(http://s018.radikal.ru/i509/1308/3a/1cb046ec159f.jpg)
i didnt measure it
i just chosed a shot that look nice to me
and i just applied a 3 parts on horizontal and vertical
really straight lines and 3 parts
the eye and nose felt just on 2 of key points
and if you remember for a good camera composition
your objects target must be at least close to one of this 4 key points where lines are crossed
and if u ask why? who made this rules?
God made, when he made our eyes and brain
scientists found that human looks on this 4 cross points of the image automatically at first look
starting fromo top left going to top right then bottom left and bottom right
so if u wana attract attention of a viewer place your message there
otherwise it is stupid composition that is not attracting at all.
oh my god
this shot was GOOOD
but the rest is awful
Here's some footage from a video I still have to edit, I did not see a lot of sport videos shot on 50D raw yet.
For run and gun shooting we found the battery life and data management was quite an issue, we shot over 250GB of raw footage that I will try to edit as a 20 minutes video.
I noticed one corrupt frame in the middle of one of the clips but that's the only issue/bug.
On H264 timelapses (fps override) we found the 50D would get really hot, but we did not get warning messages or shutdowns.
For this project I feel like the 50D was not the rigth tool at all but we got some beautyfull shots. My dream camera would be the 50D shooting prores 10 bit and with embeed audio, maybe the BMPCC would be a better tool for my use...
Anyways here is the footage :
Quote from: Silkway on August 16, 2013, 06:35:46 PM
also i dont ask shit people for their step by step color grading
i ask from the master of art like D.I.Watson
I'm no master at anything.
In regards to your mannerism, there is no reason why anyone should say something is stupid. You might think it's stupid, but have the common courtesy and respect for your fellow filmmakers and give constructive & encouraging feedback. Or don't leave feedback at all.
Quote from: bzhwindtalker on August 16, 2013, 07:39:57 PM
Here's some footage from a video I still have to edit, I did not see a lot of sport videos shot on 50D raw yet.
For run and gun shooting we found the battery life and data management was quite an issue, we shot over 250GB of raw footage that I will try to edit as a 20 minutes video.
I noticed one corrupt frame in the middle of one of the clips but that's the only issue/bug.
On H264 timelapses (fps override) we found the 50D would get really hot, but we did not get warning messages or shutdowns.
For this project I feel like the 50D was not the rigth tool at all but we got some beautyfull shots. My dream camera would be the 50D shooting prores 10 bit and with embeed audio, maybe the BMPCC would be a better tool for my use...
Anyways here is the footage :
I like this, nice to see something with more movement in it. I think the 50D held up pretty well, didn't notice any rolling shutter either. How did you manage your workflow when you were out and about, did you back your cards up to a laptop when shooting?
Quote from: bzhwindtalker on August 16, 2013, 07:39:57 PM
Here's some footage from a video I still have to edit, I did not see a lot of sport videos shot on 50D raw yet.
For run and gun shooting we found the battery life and data management was quite an issue, we shot over 250GB of raw footage that I will try to edit as a 20 minutes video.
I noticed one corrupt frame in the middle of one of the clips but that's the only issue/bug.
On H264 timelapses (fps override) we found the 50D would get really hot, but we did not get warning messages or shutdowns.
For this project I feel like the 50D was not the rigth tool at all but we got some beautyfull shots. My dream camera would be the 50D shooting prores 10 bit and with embeed audio, maybe the BMPCC would be a better tool for my use...
Anyways here is the footage :
Really cool video 8)
Quote from: D.L. Watson on August 16, 2013, 07:41:09 PM
I'm no master at anything.
In regards to your mannerism, there is no reason why anyone should say something is stupid. You might think it's stupid, but have the common courtesy and respect for your fellow filmmakers and give constructive & encouraging feedback. Or don't leave feedback at all.
yeah maybe i sound rude
its just my love to quality of canon 50d
cant leave me careless to crap)
i see your tutorial and thats amazing color grading
thats all i say
btw your skills would be helpful to previous post video about bikes)
the shots was good
but the color grading is missing
it looks like those folks applied your flatz preset and just left it like that)
i understand bleach bypass when u got h.264 shot
but not on 14 bit raw
its not even prores! its more colors and tones
lets respect magic lantern team work and use maximum out of canon 50d
p.s. hey people, seriously, canon 50d can make it better (watch D.I.Watson tutorial for comparison)
hey dudes
you wana see what professional film makers do?
watch this videos
http://www.youtube.com/watch?v=FLZ8L6SZmaA&list=PLA3D67612B92CD08B
pay attention that almost every single scene is shot with a rule of thirds for main characters eye
(that 3 part lines horizontal and vertical i shown above)
and thats not even what u got! a raw machine canon 50d
come on!
what is th max write speed at this moment?
Quote from: lomka on August 16, 2013, 09:07:46 PM
what is th max write speed at this moment?
i use the best card on the planet
lexar x1000
on canon 50d
and i cant make it run faster that 55 mb/sec on continuous green recording not yellow or red thing.
Quote from: Silkway on August 16, 2013, 08:49:00 PM
btw your skills would be helpful to previous post video about bikes)
the shots was good
but the color grading is missing
it looks like those folks applied your flatz preset and just left it like that)
Hey man there is a lot to be said about this video but I don't think you know shit about color correction and grading. My brother did the color correction and color matching, he managed to pull amazing info out of the few H264 clips we used and managed to match them to the RAW files, getting evry bit of info out of the skies using luma mascs.
Go read http://www.amazon.fr/Color-Correction-Handbook-Professional-Techniques/dp/0321713117 then you can talk about CC...
Quote from: bzhwindtalker on August 16, 2013, 09:15:26 PM
Hey man there is a lot to be said about this video but I don't think you know shit about color correction and grading. My brother did the color correction and color matching, he managed to pull amazing info out of the few H264 clips we used and managed to match them to the RAW files, getting evry bit of info out of the skies using luma mascs.
Go read http://www.amazon.fr/Color-Correction-Handbook-Professional-Techniques/dp/0321713117 then you can talk about CC...
yeah man
thats what i said
u matched raw to h.264
i could say that)
Quote from: lomka on August 16, 2013, 09:07:46 PM
what is th max write speed at this moment?
I'm thinking bying myself an old 50D as a spare for y 5D2 and I wanted to know if there is something better in super35 sensor for RAW. (I've found one 50D for 380E) and of course if the max resolution (1584x1058) can be achieve easyly ? What I've seen on EOSHD and on VIMEO with the 50D looks really impressive.... :)
Quote from: xvince1 on August 16, 2013, 09:21:24 PM
I'm thinking bying myself an old 50D as a spare for y 5D2 and I wanted to know if there is something better in super35 sensor for RAW. (I've found one 50D for 380E) and of course if the max resolution (1584x1058) can be achieve easyly ? What I've seen on EOSHD and on VIMEO with the 50D looks really impressive.... :)
if i would be you, i would definently buy canon 50d
coz to me canon 5d mark 2 seems like odd brick
(however 5d mark 3 is diamond)
Well i'm not professional at all. I do other things (music). But i love filiming as well and everything i do, i try to do my best. It was the first experience in shooting and there is a lot of things i did wrong i know. It was posted just to show my experience with Canon 50D RAW module. If it looks stupid for someone, well ok then :) But at least i can be honest with myself that i completed the project and it was a lot of hard work for me (shooting, editing, color grading etc). Cheers!
QuoteWell i'm not professional at all. I do other things (music). But i love filiming as well and everything i do, i try to do my best. It was the first experience in shooting and there is a lot of things i did wrong i know. It was posted just to show my experience with Canon 50D RAW module. If it looks stupid for someone, well ok then :) But at least i can be honest with myself that i completed the project and it was a lot of hard work for me (shooting, editing, color grading etc). Cheers!
That´s true! ;-)
So...long live to eos 50D!!
Cheers...
Asier.
Quote from: Viente on August 16, 2013, 09:30:41 PM
Well i'm not professional at all. I do other things (music). But i love filiming as well and everything i do, i try to do my best. It was the first experience in shooting and there is a lot of things i did wrong i know. It was posted just to show my experience with Canon 50D RAW module. If it looks stupid for someone, well ok then :) But at least i can be honest with myself that i completed the project and it was a lot of hard work for me (shooting, editing, color grading etc). Cheers!
yeah i could say that it was your first experience)
ps canon 50d isnt good for first experience
use phone first
Quote from: Viente on August 16, 2013, 10:56:52 AM
Here is the little music/promo/teaser video i'v made with 50D RAW...this was the first experience and i think i can't go back to H264 mode ever!
Keep doing your thing Viente, keep shooting, your first experience with Raw is pretty good.. it's definitely a learning curve but in time all will fall in place. By the way Welcome to the 50D Club nice video 8)
Quote from: xvince1 on August 16, 2013, 09:21:24 PM
I'm thinking bying myself an old 50D as a spare for y 5D2 and I wanted to know if there is something better in super35 sensor for RAW. (I've found one 50D for 380E) and of course if the max resolution (1584x1058) can be achieve easyly ? What I've seen on EOSHD and on VIMEO with the 50D looks really impressive.... :)
Hi there,
I think the only alternative would be a 5d really. I'm shooting 1584 x 1058 Continously with no problems on 1000x CF Cards. Also can shoot 2000 x 1080 in 3x crop mode.
Quote from: Viente on August 16, 2013, 09:30:41 PM
Well i'm not professional at all. I do other things (music). But i love filiming as well and everything i do, i try to do my best. It was the first experience in shooting and there is a lot of things i did wrong i know. It was posted just to show my experience with Canon 50D RAW module. If it looks stupid for someone, well ok then :) But at least i can be honest with myself that i completed the project and it was a lot of hard work for me (shooting, editing, color grading etc). Cheers!
Well done for putting your self out there. I enjoyed it and can't wait to see what you come up with next.
Summarizing edit from mods: I went back to making videos on my cell phone and won't be bothering any of you with my opinions for the time being.
You know what would be really cool, some kind of zebra stripes or something that warn of moire patterns. Probably impossible though.
Quote from: Supermac on August 16, 2013, 10:15:52 PM
Hi there,
I think the only alternative would be a 5d really. I'm shooting 1584 x 1058 Continously with no problems on 1000x CF Cards. Also can shoot 2000 x 1080 in 3x crop mode.
Hi supermac,
thank's . It's not for a real alternative, just to have a RAW DSLR always with me. In fact the 50D looks very well manufactured and ergonomics like the 5D2. And I could use all my stuff with it...
Quote from: xvince1 on August 16, 2013, 10:26:45 PM
Hi supermac,
thank's . It's not for a real alternative, just to have a RAW DSLR always with me. In fact the 50D looks very well manufactured and ergonomics like the 5D2. And I could use all my stuff with it...
I can vouch for that, very solid indeed. Makes my 550D seem like a cheap toy.
Quote from: Supermac on August 16, 2013, 10:32:58 PM
I can vouch for that, very solid indeed. Makes my 550D seem like a cheap toy.
That looks really cool... Just incredible thing to have RAW and video with it. In March or April, I was thinking about 60D for the rotative screen, but the 50D is cheaper and use CF... What a huge gap now in the canon line (CF vs SD) :)
Quote from: xvince1 on August 16, 2013, 10:44:37 PM
That looks really cool... Just incredible thing to have RAW and video with it. In March or April, I was thinking about 60D for the rotative screen, but the 50D is cheaper and use CF... What a huge gap now in the canon line (CF vs SD) :)
If only the 60D had CF. lol ;D
When I have time, I've been shooting my own tests to get more experience of using the raw hack (though nothing worth posting here yet), and I've just got back on top of the posts to learn as much as I can! I was on an old version for a while but currently using GregoryOfManhattan's 27 June Unified build. It's great to have your settings still there when you turn it back on again! Things just keep getting better. There's no other word for it, for the first time in ages I feel excited shooting raw 2.39:1 with the 50D. It's like filming with a compact little Eyemo 35mm camera, though that camera's internal 100 ft reel of stock lasted just over a minute (at 24 fps), and the clock winding gave you just 20 seconds per take, so I feel quite spoilt even using a fairly modest 64 GB CF card. What more are we waiting for these days?
Got a replica battery grip today, which has overcome the problem of battery drain that I was experiencing with raw shooting on the 50D.
Briefly tested the joys of focus peaking, but when I started to use it for a longer test later, I found my takes were being aborted early. Yes, the constant real time focus peaking was pushing the resources too far; I turned it off and my usual performance was back again. I can always use the usual Canon magnifying buttons to focus before I record.
Moire can sometimes be prominent, though when I shot a test side-by-side with my 60D shooting H.264 video, I can see the particular areas of moire are very similar with both cameras, it's just softer with the 60D -- well, the whole H.264 video image is a bit softer than raw, even when raw processing sharpness is turned down.
One of the great benefits of raw footage is in the post-production; I am currently using ACR but my next area of exploration will be trying Raw Therapy as an alternative.
I always have the live raw histogram on (there is no performance hit) to estimate exposure, but what do the coloured dots actually mean, sometimes with numbers forming inside them?
Many thanks for the big effort of the coders and the support of the frequent forum contributors on here. Very inspirational.
Quote from: Supermac on August 16, 2013, 10:23:30 PM
You know what would be really cool, some kind of zebra stripes or something that warn of moire patterns. Probably impossible though.
@Supermac - to me this is actually a good, constructive idea! I'm not sure if it's possible because the camera wouldn't know how to detect moire but good thinking anyway! :)
@Silkway - I'm not really sure why I feel I have to say something about your earlier dissing of Viente's video when others have so eloquently offered constructive criticism but nonetheless, I hope you can contribute more positively to the thread and the forum. I get that you are enthusiastic and excited by what your camera can do (we all are!) but I'm actually more interested to see what YOU can do with it.
@Viente - Congrats on making your first music video dude! I know from experience that it's a bit scary putting something out there but you did good! I get where you're coming from with it and there are some great ideas and shots there. I agree with earlier comments about the flow of the piece but also there are no rules when it comes to creativity so do your own thing. You'll never please everyone but it's cool to see you pushing forward and making something rather than getting stuck in endless test shots (like some of us ::) ). I know that you understand the market you're aiming at and I'd say this fits. Keep it up mate!!
Quote from: Silkway on August 16, 2013, 09:12:41 PM
i use the best card on the planet
lexar x1000
on canon 50d
and i cant make it run faster that 55 mb/sec on continuous green recording not yellow or red thing.
I searched the lexar x1000 card and in benchmark it had 66 mb/s speed and found a cf card: KOMPUTERBAY x1000 which had 114 mb/s write speed.
Quote from: TrueIndigo on August 16, 2013, 11:31:53 PM
When I have time, I've been shooting my own tests to get more experience of using the raw hack (though nothing worth posting here yet), and I've just got back on top of the posts to learn as much as I can! I was on an old version for a while but currently using GregoryOfManhattan's 27 June Unified build. It's great to have your settings still there when you turn it back on again! Things just keep getting better. There's no other word for it, for the first time in ages I feel excited shooting raw 2.39:1 with the 50D. It's like filming with a compact little Eyemo 35mm camera, though that camera's internal 100 ft reel of stock lasted just over a minute (at 24 fps), and the clock winding gave you just 20 seconds per take, so I feel quite spoilt even using a fairly modest 64 GB CF card. What more are we waiting for these days?
Got a replica battery grip today, which has overcome the problem of battery drain that I was experiencing with raw shooting on the 50D.
Briefly tested the joys of focus peaking, but when I started to use it for a longer test later, I found my takes were being aborted early. Yes, the constant real time focus peaking was pushing the resources too far; I turned it off and my usual performance was back again. I can always use the usual Canon magnifying buttons to focus before I record.
Moire can sometimes be prominent, though when I shot a test side-by-side with my 60D shooting H.264 video, I can see the particular areas of moire are very similar with both cameras, it's just softer with the 60D -- well, the whole H.264 video image is a bit softer than raw, even when raw processing sharpness is turned down.
One of the great benefits of raw footage is in the post-production; I am currently using ACR but my next area of exploration will be trying Raw Therapy as an alternative.
I always have the live raw histogram on (there is no performance hit) to estimate exposure, but what do the coloured dots actually mean, sometimes with numbers forming inside them?
Many thanks for the big effort of the coders and the support of the frequent forum contributors on here. Very inspirational.
Nice post :)
I have the same mindset as you in thinking of raw video like film stock. It really helps you focus on the important stuff when you have limitations. I actually 'think' more with raw before hitting the record button and my shots are improving.
BTW we should have a kind of focus peaking that doesn't have so much impact on resources soon so you'll be able to shoot with it on ;)
Quote from: Andy600 on August 16, 2013, 11:53:01 PM
@Viente - Congrats on making your first music video dude! I know from experience that it's a bit scary putting something out there but you did good! I get where you're coming from with it and there are some great ideas and shots there. I agree with earlier comments about the flow of the piece but also there are no rules when it comes to creativity so do your own thing. You'll never please everyone but it's cool to see you pushing forward and making something rather than getting stuck in endless test shots (like some of us ::) ). I know that you understand the market you're aiming at and I'd say this fits. Keep it up mate!!
Thanks mate! (And all other fellow 50d users out there!). I wouldn't call this music video, im too far away from doing it lol :) Just a little promo video to make watching a track on YouTube a little bit interesting. I realize i know so little about professional things of serious shooting but it was fun and i'll keep learning as much as i can to keep progress! Looking forward to see something cool from you as well soon :)
Latest Tragic Lantern 2.0 (Andy600 intermediate build)
https://bitbucket.org/andy600/tl50d/downloads
Features a1ex's NEW experimental Digic Focus Peaking which doesn't impact on raw video record time/performance.
3 options currently available: Increased sharpness, Edge and Chroma.
Find it in the display menu.
Plus other minor fixes.
Quote from: Andy600 on August 17, 2013, 01:31:40 AM
Latest Tragic Lantern 2.0 (Andy600 intermediate build)
https://bitbucket.org/andy600/tl50d/downloads
Features a1ex's NEW experimental Digic Focus Peaking which doesn't impact on raw video record time/performance.
3 options currently available: Increased sharpness, Edge and Chroma.
Find it in the display menu.
Plus other minor fixes.
Thanks for the build. Aperture changes work during recording now. The new focus peaking is nice, in that it doesn't take a hit to the speed, but it is going to take some getting used to. Useful for 1920x1080 as it provides a nice bump in edges, but I can run Focus Peaking on 1584x892 with continuous, getting 55-65mb/s.
Thanks again! ;D
Why does the preview in all tragic lantern builds not fill the entire screen like all other ML builds?
Also, what is a good way of unloading cards on location? my laptop does not have usb3.0 and 64gb takes forever.
Quote from: Andy600 on August 17, 2013, 01:31:40 AM
Latest Tragic Lantern 2.0 (Andy600 intermediate build)
https://bitbucket.org/andy600/tl50d/downloads
Features a1ex's NEW experimental Digic Focus Peaking which doesn't impact on raw video record time/performance.
3 options currently available: Increased sharpness, Edge and Chroma.
Find it in the display menu.
Plus other minor fixes.
Thank you for new build Andy - @1% & @a1ex I still can't believe the advances for the 50D, it is becoming a movie making machine for less than an XBox Wow!!! I'm soo grateful for everything guy's keep up the great work.. ;D
Hey guy's @Andy600 @1% @a1lex I think it's time for new donations to start rolling in to keep the advances going what do you guy's think? If it's a yes I'm ready to give my share cheers. ;)
Quote from: johansugarev on August 17, 2013, 03:09:46 AM
Why does the preview in all tragic lantern builds not fill the entire screen like all other ML builds?
Also, what is a good way of unloading cards on location? my laptop does not have usb3.0 and 64gb takes forever.
It's a small optimization to increase write speed but you can press the INFO button a few times to get rid of the extra black bars.
re: Offloading. The cheapest option if you want to stick with the laptop is to get an Express card with USB 3.0 ports ;) I think you can also get them for SATA ports. The next (expensive) option would be something like a NextoDI http://www.nextodi.com
Quote from: araucaria on August 14, 2013, 04:58:11 AM
Okay, there have been popping up presets for After Effects/Adobe to get flat pictures, import or render them to 10bit and apply luts or whatever. I've also read people complaining about flickering in ACR.
So far so good, I remember that on LRtimelapse (nice program) there is a general consens to not use highlight recovery, black , white, shadows,etc... because they are not linear but some "secret sauce" which depends on the scene. This doesn't matter to stills (which it was designed for) but when movement comes into play this can actually generate flicker. It does not always happen, but sometimes you get the flickering.
To avoid this, I have "created" two a camera profiles which give you a very flat picture style and some desaturation. This is just a test as I'm not an expert but I think it works fine (tried out with the 50d raw video with cdng files). I will look into it again when I have some time. Here are the camera profiles:
https://www.dropbox.com/s/sxxj82szbimxn8f/MLfilm%20slight.dcp
https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
You have to put them into c:/users/"your username"/AppData/Roaming/Adobe/CameraRaw/CameraProfiles
Afterwards they should appear under the camera calibration tab.
This is the same way I did my log preset, as you said, it works better as you don't get any flicker.
I based mine off the 50D camera neutral ACR profile (available on adobe's site) and changed the tone curve to linear. If you expose to the right and don't clip anything then you'll get an S-Log/BMDFilm style image.
Ideally I'd want to shoot a chart and create a profile based on what we are actually getting from the sensor as I'm not sure how accurate the Canon/Adobe profiles are.
I'm just tweaking my LUT at the mo, in Resolve I use the Offset control to adjust it to suit. So far I'm getting quite consistent results.
rockfallfilms, can you share your preset?
Thanks for the build Andy600 !
@Andy600 "...you can press the INFO button a few times to get rid of the extra black bars"
But do we need to press the INFO all the time before each shot? I personally as @johansugarev prefer to see the entire frame all the time so it's feel like "bug" to keep pressing it over and over. What do you think?
@dsManning the Aperture is still lock for me. Did you try it during recording and with the "Extra Hacks" on?
is it possible on 50d to do pixel binning instead of line skipping so that there will be less aliasing/moire?
i mean it has full resolution of 4752 × 3168 combining 3x3 pixels we will have 1584 x 1056 resolution.
Quote from: lomka on August 17, 2013, 04:37:16 PM
is it possible on 50d to do pixel binning instead of line skipping so that there will be less aliasing/moire?
i mean it has full resolution of 4752 × 3168 combining 3x3 pixels we will have 1584 x 1056 resolution.
Fantastic idea as it is, you really think that it hasn't been suggested dozens of times and hasn't been considered by the developers hundreds of times? )) or you really think you could be the ONE? ))
Quote from: rommex on August 17, 2013, 05:02:17 PM
Fantastic idea as it is, you really think that it hasn't been suggested dozens of times and hasn't been considered by the developers hundreds of times? )) or you really think you could be the ONE? ))
im asking if it is possible not suggesting the idea.
Hmm... can anyone say how to sync audio and video on canon 50d?
Quote from: lomka on August 17, 2013, 05:25:05 PM
im asking if it is possible not suggesting the idea.
Of course it is possible. Just nobody seems to want this feature. Just kidding....
You may try searching the thread and you'll find explicit answers why this is not possible.
Quote from: Monti on August 17, 2013, 06:53:46 PM
Hmm... can anyone say how to sync audio and video on canon 50d?
Clapboard. Or an external monitor with audio recording (check out first post of this thread) ;)
Anyone have any state of the art techniques for dealing with moire and aliasing in post?
Quote from: dogmydog on August 17, 2013, 07:35:57 PM
Clapboard. Or an external monitor with audio recording (check out first post of this thread) ;)
yeah but i heard that it moves 6 seconds from audio to video stream after 2 minutes
huge gap isnt it?
how to set it work fine or adjust to sync?
Quote from: TrueIndigo on August 16, 2013, 11:31:53 PM
One of the great benefits of raw footage is in the post-production; I am currently using ACR but my next area of exploration will be trying Raw Therapee as an alternative.
I just got my D50 last week and am trying to catch up with all the new stuff. I tried to find some tutorials on Raw Therapee, either on the command line or otherwise but couldn't find much. I rarely buy software for anything but I'm sensing that many people on these forums has spent a fair bit of money on something from Adobe. The only other free alternative I've heard of is UFRaw but again finding good tutorials is something that's eluding me. Please let us know if you find anything useful.
so i have read many posts and many people were complaining about aliasing and moire is it really that bad or same as the H.264?
Quote from: Andy600 on August 17, 2013, 01:31:40 AM
Latest Tragic Lantern 2.0 (Andy600 intermediate build)
https://bitbucket.org/andy600/tl50d/downloads
Features a1ex's NEW experimental Digic Focus Peaking which doesn't impact on raw video record time/performance.
3 options currently available: Increased sharpness, Edge and Chroma.
Find it in the display menu.
Plus other minor fixes.
Hello,
Thank you to all the team for your great work on this superb body!
Maybe I missed something with all those testes on all these updates since May! (Thanks Gregory and Andy).
I had fun as a kid with ETTR and intervalometer and I noticed that ETTR only works in live view, is this normal?
Setting in manual mode, iso manual, manual and automatic focus, default settings ETTR (Trigger mode: Always On), with the latest Andy's update
(Tragic.Lantern-2.0-Andy600.Build.2013Aug17.50D109-DIGIC_FOCUS_PEAKING).
Thank you all for your work and thank you for all these findings A1ex!
Cheers !
Tof
Edit : I tried a version of ML
(magiclantern-Andy600.Build.2013Aug04.50D109) and ETTR work only in live view too.
Edit 2: I tried an other version of ML from Gregory
(magiclantern-2013Jul27.50D.109.go.unified.728e571a1276) and this is the same thing. I think is the ETTR module who don't work without live view on the 50D.
Everything works perfectly in raw video <-- live view enabled
Any idea or suggestion?
I forgot to mention that I read and reread the guide: (Auto) ETTR (Exposure to the Right): -- History & Beginners Guide (http://www.magiclantern.fm/forum/index.php?topic=5693.msg60086#msg60086)
Hey guys,
So, I don't know how I did it before, but I had raw video recording working smoothly on my 50D with the 2.3 stable release...
I recently formatted all my cards, and when i reinstalled ML the "M" menu and modules were nowhere to be found. After troubleshooting, the closest I got was installing 2.3 to a card, and then overwriting the EOS_DIGITAL/autoexec.bin and ML/modules files on the card with Andy600's latest Tragic Lantern 2.0 build files-
I got my module menus back and raw video capabilities, but ML kept crashing before I could even try to record.
:'(
Can anyone link me to a self-contained build that has working modules/autoexec.bin so i don't have to rearrange a bunch of crap to get raw_rec working?
I'm really looking forward to trying out a new anamorphic lens.
Thanks all.
you have to replace all folders in ML on your card with the once in the new build. Some would consider this common sense.
some people are nice.
some people are jackasses.
some people have rigged the enemy base with explosives.
thanks for the info and have a great day!
Hi Everyone,
I just wanted to post some footage that I shot a couple of weeks ago while I was out with the family. It was all very impromptu, all hand held with no rig, didn't even have a viewfinder with me (hence the crappy focus!) But I love the look of the 50d, so thanks to the devs who made this possible!
(harustudio is the name of our business, no point in wasting a branding opportunity :)
I shot it on one of the recent Tragic Lantern builds, exported to Prores422 from TIFF sequences made in Lightroom, then cut and graded in Premiere Pro CC. The looks are from the included Lumetri presets, and I really like them. Looks great for things like this.
I've also cobbled together a workflow on OS X that mimics how RAWanizer works, by installing DCRaw and FFMpeg on my computer, then running a shell script in Automator. So my workflow for this has been:
RAWMagic > Batch Create Previews Automator Workflow > Rough edit in Premiere > Basic grade and output from Lightroom > Batch Create Prores422 Automator Workflow > Replace previews, edit, grade and export in Premiere
The batch previews workflow is especially helpful, I can go from downloading a 1 minute sequence to having a viewable preview movie on my laptop in about 5 minutes, so while it's not real time playback, it means I could conceivably watch back a 32gb card's worth of clips in under an hour. It's nowhere near as elegant as RAWanizer, and it's a bit of a mission to get DCRaw and FFMpeg installed in OSX (although I've potentially made it easier now that I've found where I can download the binaries of both those programs. Originally I had to compile them myself), but it works great and I'm in the process of putting together a full step by step tutorial, which I hope will help some of you.
Attended a wedding and tested the duel iso for my 50D. Some beautiful dynamic range.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/duels.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/duell.jpg)
When nighttime hit, I tried to see if I could do something like 800/12800 but even though it was selected, it still defaulted back to 800/1600. Maybe a bug? (I know it would be incredi-noise, but I just wanted to see how bad it would be).
@ jhnkng:
Really nice footage from 50D!
I´ve also recorded alot of RAW clips hand held so these are quite shaky...none the less the image quality IS still INCREDIBLE! :)
I´ll try to make a compilation from my best 50D clips an share it here.
So thanks again to 1%, Andy600 and all the ML team that made THIS possible! :)
@ D.L. Watson:
Really cool picture from Dual ISO!
I´ve also tried to make some but when processing them in cr2hdr, it seems to nothing happen, only an MS-DOS (windows version here...) window that disappears very quckly!.
I have all pictures (*.CR2) in the same root as the cr2hdr.exe is located....
Some help could be nice!
Thanks in advance and cheers...
Asier.
Quote from: jhnkng on August 18, 2013, 07:03:45 AM
Hi Everyone,
I just wanted to post some footage that I shot a couple of weeks ago while I was out with the family. It was all very impromptu, all hand held with no rig, didn't even have a viewfinder with me (hence the crappy focus!) But I love the look of the 50d, so thanks to the devs who made this possible!
(harustudio is the name of our business, no point in wasting a branding opportunity :)
I shot it on one of the recent Tragic Lantern builds, exported to Prores422 from TIFF sequences made in Lightroom, then cut and graded in Premiere Pro CC. The looks are from the included Lumetri presets, and I really like them. Looks great for things like this.
I've also cobbled together a workflow on OS X that mimics how RAWanizer works, by installing DCRaw and FFMpeg on my computer, then running a shell script in Automator. So my workflow for this has been:
RAWMagic > Batch Create Previews Automator Workflow > Rough edit in Premiere > Basic grade and output from Lightroom > Batch Create Prores422 Automator Workflow > Replace previews, edit, grade and export in Premiere
The batch previews workflow is especially helpful, I can go from downloading a 1 minute sequence to having a viewable preview movie on my laptop in about 5 minutes, so while it's not real time playback, it means I could conceivably watch back a 32gb card's worth of clips in under an hour. It's nowhere near as elegant as RAWanizer, and it's a bit of a mission to get DCRaw and FFMpeg installed in OSX (although I've potentially made it easier now that I've found where I can download the binaries of both those programs. Originally I had to compile them myself), but it works great and I'm in the process of putting together a full step by step tutorial, which I hope will help some of you.
Not bad.
Now we can see advantages of canon 50d
Quote from: Eran on August 17, 2013, 03:44:08 PM
Thanks for the build Andy600 !
@Andy600 "...you can press the INFO button a few times to get rid of the extra black bars"
But do we need to press the INFO all the time before each shot? I personally as @johansugarev prefer to see the entire frame all the time so it's feel like "bug" to keep pressing it over and over. What do you think?
Although the black bars in TL2.0 are not a 'bug' I kind of agree that the write performance increase is so small that we can probably lose them. I always hit INFO to do it manually anyway.
@1% can this hack be reverted? Also, any luck finding how to reduce contrast in crop mode grayscale preview?
re: aperture 'bug'. It wasn't intentionally fixed in the last build so I'm surprised that some users no longer have that issue and you still do. There must be something in each user's config that affects things. I can't personally test it because all my lenses are manual aperture. I don't even have a kit lens to play with.
@Andy
There are a bug with yours TL latest update. When you record a raw video, when you finished the video by click on SET, the blue light flashed, the red light too and the display turn off. When you click on live view button you return on photo mode and the display on. When you re click on LV, the display turn off. After turn off the body, click on LV works fine the first time and the second time I've an error 99.
The crashlog:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Aug17.50D109
Mercurial changeset : 74dac53a5f5e+ (build-bot-2.0) tip
Built on 2013-08-16 22:57:26 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 285K + 3183K
And the log: http://pastebin.com/dbkL5nAi (sorry it's too long to copy here)
I hope it's useful for you!
Thanks a lot !
Edit : don't appear on the previous TL update (august 12th Tragic.Lantern-2.0-Andy600build.2013Aug12.50D109-DUAL-ISO)
Quote from: kichetof on August 18, 2013, 01:05:36 PM
@Andy
There are a bug with yours TL latest update. When you record a raw video, when you finished the video by click on SET, the blue light flashed, the red light too and the display turn off. When you click on live view button you return on photo mode and the display on. When you re click on LV, the display turn off. After turn off the body, click on LV works fine the first time and the second time I've an error 99.
The crashlog:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Aug17.50D109
Mercurial changeset : 74dac53a5f5e+ (build-bot-2.0) tip
Built on 2013-08-16 22:57:26 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 285K + 3183K
And the log: http://pastebin.com/dbkL5nAi (sorry it's too long to copy here)
I hope it's useful for you!
Thanks a lot !
good that i didnt install the latest one)
Quote from: kichetof on August 18, 2013, 01:05:36 PM
@Andy
There are a bug with yours TL latest update. When you record a raw video, when you finished the video by click on SET, the blue light flashed, the red light too and the display turn off. When you click on live view button you return on photo mode and the display on. When you re click on LV, the display turn off. After turn off the body, click on LV works fine the first time and the second time I've an error 99.
The crashlog:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Aug17.50D109
Mercurial changeset : 74dac53a5f5e+ (build-bot-2.0) tip
Built on 2013-08-16 22:57:26 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 285K + 3183K
And the log: http://pastebin.com/dbkL5nAi (sorry it's too long to copy here)
I hope it's useful for you!
Thanks a lot !
@Kichetof - I can't say I've had the same problem and can't reproduce it on my camera but thanks for posting the log. Maybe one of the devs can have a quick look through to see if there is an obvious problem.
@Monti - Yes, I would advise you to stick to vanilla ML v2.3 and not use any of the new features. It's far too buggy and as you can see there are pages and pages of unhappy users here ::) - but on a more serious note, if it wasn't for users testing these builds we would never find these bugs/issues/anomalies. The last build is as stable as any of the previous ones AFAIK. It's up to you guys to prove otherwise ;)
@Andy don't worry I try to reproduce them and I've some difficulty. I go on LV, I set on ML Movie Record, I activate Raw video and I turn raw video on and either it crash before displaying the resolution or it crash after displaying the resolution (the screen freezes).
I'll return on the august 12nd build :-)
Quote from: kichetof on August 18, 2013, 01:32:02 PM
@Andy don't worry I try to reproduce them and I've some difficulty. I go on LV, I set on ML Movie Record, I activate Raw video and I turn raw video on and either it crash before displaying the resolution or it crash after displaying the resolution (the screen freezes).
I'll return on the august 12nd build :-)
Did you have the new Digic focus peaking enabled when you had the crashes?
Quote from: Andy600 on August 18, 2013, 01:34:53 PM
Did you have the new Digic focus peaking enabled when you had the crashes?
Nope! I activate all the minimum required to test where the bug come. It's seem to come from the raw_rec module. I've a freeze when I enabled it. (Sometimes on the previous build too)
Quote from: Asiertxu on August 18, 2013, 12:19:55 PM
@ jhnkng:
Really nice footage from 50D!
I´ve also recorded alot of RAW clips hand held so these are quite shaky...none the less the image quality IS still INCREDIBLE! :)
I´ll try to make a compilation from my best 50D clips an share it here.
So thanks again to 1%, Andy600 and all the ML team that made THIS possible! :)
Thanks :) I know what you mean with the hand held shots, I didn't think I'd have time to shoot anything so I didn't pack anything besides the camera and a lens!
Quote from: Monti on August 18, 2013, 01:00:19 PM
Not bad.
Now we can see advantages of canon 50d
Thanks mate :)
For those who want to stick with Unified code here is the latest Magic Lantern build (includes Digic Focus Peaking, Dual ISO, Auto Exposure etc etc): https://bitbucket.org/andy600/andy50d/downloads#download-222424
Quote from: Andy600 on August 18, 2013, 02:20:24 PM
For those who want to stick with Unified code here is the latest Magic Lantern build (includes Digic Focus Peaking, Dual ISO, Auto Exposure etc etc): https://bitbucket.org/andy600/andy50d/downloads#download-222424
oh cool
u doing hard job
but what is unified code?
is it different from tragic lantern?
p.s. im running your 12 august tragic lantern and its so cool
the thing that surprises me
that there is only 40-100 times downloads for each of the builds
is it just 40 people sticking around over this forum topic?
Quote from: Monti on August 18, 2013, 03:02:34 PM
oh cool
u doing hard job
but what is unified code?
is it different from tragic lantern?
p.s. im running your 12 august tragic lantern and its so cool
the thing that surprises me
that there is only 40-100 times downloads for each of the builds
is it just 40 people sticking around over this forum topic?
I'm doing the 'easiest' part of the job. The devs do the hard stuff.
The differences between Tragic and Magic have been posted about MANY times in this thread. Use search.
As for amount of 50D users, who knows? I guess some stick to Canon FW, some are on ML2.3 and a few are using Alpha builds of Magic or Tragic. One thing I'm sure of is that users of ML on the 50D have multiplied recently for some reason ;)
Hi,
Installed Aug 17 build on my 50D today. I can not reproduce the bug above, so is working fine here. I prefer Tragic TL over ML, because it enables more seconds of recording in 1080p. Test today: avg 41 secs with 1920 x 1080 @ 24 fps. With ML is only a few secs. Also for dual iso: if you are using mac, you can use cr2hdr here:
http://www.gerstel.org/images/canon/dual_iso/cr2hdr
This also does not have the " green " issue.
BTW congratulations with the new website 8)
Cheers,
Jorgen
Quote from: johansugarev on August 17, 2013, 03:03:17 PM
rockfallfilms, can you share your preset?
I'm going to shoot some charts to get a true colour/noise profile off the 50D sensor first, then I'll share it.
By the time I've got it sorted Resolve 10 might be out with its new super duper debayering :)
Quote from: jgerstel on August 18, 2013, 03:52:57 PM
Hi,
Installed Aug 17 build on my 50D today. I can not reproduce the bug above, so is working fine here. I prefer Tragic TL over ML, because it enables more seconds of recording in 1080p. Test today: avg 41 secs with 1920 x 1080 @ 24 fps. With ML is only a few secs. Also for dual iso: if you are using mac, you can use cr2hdr here:
http://www.gerstel.org/images/canon/dual_iso/cr2hdr
This also does not have the " green " issue.
BTW congratulations with the new website 8)
Cheers,
Jorgen
Did you compile cr2hdr.exe yourself and did you change anything to fix the green issue?
Congratulations with 777 posts)
(http://s020.radikal.ru/i714/1308/41/0eb4ae6bd4ec.jpg)
btw the only thing that kicks me off in canon 50d
(such old and such great camera - thanks to magic/tragic lantern team)
is the shutter sound when you take photos
it really reminds like a toilet tank cover flaps down hehe
Hi, yes I compiled myself using your 12 august source. The default windows .exe in the dual_iso thread was causing the " green " issue for 50D and I needed Mac version. So ML developer has fixed it in the code already before my compile, but the mac binary was never out there.
Quote from: jgerstel on August 18, 2013, 05:34:56 PM
Hi, yes I compiled myself using your 12 august source. The default windows .exe in the dual_iso thread was causing the " green " issue for 50D and I needed Mac version. So ML developer has fixed it in the code already before my compile, but the mac binary was never out there.
Ok, thanks :)
So, for anyone using Dual ISO on the 50D, I've re-compiled cr2hdr.exe for Windows https://bitbucket.org/andy600/tl50d/downloads (Folder includes exif tool and dcraw).
Not sure if this will have any effect on the green issue though.
Fix confirmed ::), checked your new windows cr2hdr and green issue is also solved here. :-)
Quote from: jgerstel on August 18, 2013, 06:21:30 PM
Fix confirmed ::), checked your new windows cr2hdr and green issue is also solved here. :-)
Amazeballs!
(disclaimer: This is the one and only time I will ever use that expression) ;D
Quote from: Andy600 on August 18, 2013, 06:28:56 PM
Amazeballs!
(disclaimer: This is the one and only time I will ever use that expression) ;D
Amazeballs it is...)
I also tested it - really no green stuff anymore on dual ISO!
so it was not the magic lantern problem but it was a program that converts cr2 to dng
here is test shot on this. however stuff are quite noisy now... seems like previous green was better?
(http://i037.radikal.ru/1308/82/c7bcb16282ac.jpg)
so as i understand
highlights are shot on 200 iso
and shadows on 1600 iso?
Quote from: LEVISDAVIS on August 16, 2013, 07:07:40 AM
Got the 50D out in the mail today to reach Mosaic Engineering!
Got plenty of time to think about it... But, what would you consider an appropriate testing procedure for the 50D and the VAF?
The problem as I understand it with Anti aliasing filters is they work best at one resolution. So which resolution is Mosaic Engineering going to make it for? I got the 50D to shoot raw. As I understand it at the moment Full HD raw is currently not available so I will be relegated to using a lower resolution raw for the time being. Are they going to make a $300 filter for the lower res raw?
Hi Forum, Just sharing my experience recording RAW with a Sandisk Extreme Pro 90MB/s CF card on a 50d, I was able to get continuous recording at the following resolutions.
1584 x 896 @ 24fps
1584 x 1056 @ 24fps
1920 x 818 @ 24fps in 5x Crop Mode
However, in 1920 x 1080 @ 24fps in 5x Crop mode i was not able to get continuous recording, that's not a big deal as the 1920 x 818 in crop mode suffices my appetite.
For countries where the Komputer Bay 1000x or the Lexar 1000x cards are hard to find the Sandisk Extreme Pro 90MB/s card which is relatively easy to find should do the trick.
Cheers
Quote from: Sniper on August 18, 2013, 09:58:16 PM
The problem as I understand it with Anti aliasing filters is they work best at one resolution. So which resolution is Mosaic Engineering going to make it for? I got the 50D to shoot raw. As I understand it at the moment Full HD raw is currently not available so I will be relegated to using a lower resolution raw for the time being. Are they going to make a $300 filter for the lower res raw?
It has to be design for a specific sensor and should be used in the normal mode (no zoom mode). That's it.
The 50d do have fullhd mode, but it is a zoom mode (3x crop) which reads every single pixel so there is no need for an extra aliasing filter.
As you can see it has nothing to do with resolution.
Quote from: araucaria on August 18, 2013, 10:44:43 PM
It has to be design for a specific sensor and should be used in the normal mode (no zoom mode). That's it.
The 50d do have fullhd mode, but it is a zoom mode (3x crop) which reads every single pixel so there is no need for an extra aliasing filter.
As you can see it has nothing to do with resolution.
I have a 600D. Aliasing is markedly reduced in 3x zoom WITHOUT VAF. VAT-TXi works on full resolution 1920sx1080. It does not work on the 720p resolution.
I am seeing a bunch of resolutions for the 50D. Which ones would work with a theoretical VAF?
If someone were to make a VAF it should be calibrated for the max resolution the 50D can handle - 1584 by 1058. Crop mode does not need a VAF in my opinion.
Latest Tragic Lantern 2.0 build (the previous build was an intermediate) plus latest raw2dng.exe and cr2hdr.exe (swap older versions of raw2dng.exe in Windows apps like BATCHelor etc).
https://bitbucket.org/andy600/tl50d/downloads
From now on I will upload the processing apps each time there is a new build so always download the top 2 files.
@jgerstel - Any chance you can compile raw2dng and cr2hdr for Mac? I'm PC based.
Quote from: Sniper on August 18, 2013, 11:35:56 PM
I have a 600D. Aliasing is markedly reduced in 3x zoom WITHOUT VAF. VAT-TXi works on full resolution 1920sx1080. It does not work on the 720p resolution.
I am seeing a bunch of resolutions for the 50D. Which ones would work with a theoretical VAF?
The 50d does not have a 720p mode, there is only Full sensor mode and Crop mode. As I said the crop mode doesn't need a VAF it is the full frame that needs one.
The resolutions you can choose between are nothing but crops out of the full stream. For example, if you choose 1280x720 and you are shooting without zooming in it will be the 1280x720 pixel portion out of the full 1584x1058 stream, but the sensor is still in the same mode, the same lines are skipped, lines that have to be "blurred together" to avoid the aliasing artifacts.
Quote from: Andy600 on August 18, 2013, 11:55:11 PM
Latest Tragic Lantern 2.0 build (the previous build was an intermediate) plus latest raw2dng.exe and cr2hdr.exe (swap older versions of raw2dng.exe in Windows apps like BATCHelor etc).
https://bitbucket.org/andy600/tl50d/downloads
From now on I will upload the processing apps each time there is a new build so always download the top 2 files.
it looks like it takes eternity to render one CR2 file with this new programm cr2hdr.exe
but it looks like a hell less noise than previous cr2hdr.exe test i did today
did you change program?
(http://s018.radikal.ru/i527/1308/5f/3da8860a8e3a.jpg)
P.S. this are 100% crops from a full image so its like magnification to pixel pixel view
Can only say BRAVO! To Andy600 and all devs and who making this coding...
Quote from: Andy600 on August 18, 2013, 11:55:11 PM
Latest Tragic Lantern 2.0 build (the previous build was an intermediate) plus latest raw2dng.exe and cr2hdr.exe (swap older versions of raw2dng.exe in Windows apps like BATCHelor etc).
https://bitbucket.org/andy600/tl50d/downloads
From now on I will upload the processing apps each time there is a new build so always download the top 2 files.
@jgerstel - Any chance you can compile raw2dng and cr2hdr for Mac? I'm PC based.
Thank's for this new release! I only tested few minutes.
- raw video works perfectly! (69mb/s on my lexar 16gb 1000x with global draw off)
- auto ettr works perfectly but only on live view
- auto exposure seem doesn't works (maybe it's too dark now)
I'll try more tomorrow!
Thanks for your work!
I really like the dynamic range and image quality of Duel ISO. Man, I really wish this was possible for video on the 50D.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/yess.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/yes.jpg)
Not the prettiest of photos, but it really shows off the nice range between highlights and shadows.
I love my 50D Thank you Team @1% @Andy600 @a1ex for the advances. Hey guy's just been working diligently on different looks for my upcoming music video I'm so pleased with the results that I've been getting ;D. Let me know what you think...
Shot on Canon 50D with Magic Lantern Raw Hack.
Hack: Tragic 6
Resolution: 1584x586
Global Draw on, Small Hack on, Focus Peaking on, Zebra on, Histogram on, Waveform on..
Lens: super-multi- coated takumar 50mm f1.4 M42
Workflow: RawMagic into Davinci Resolve 9 Color corrected than exported as ProRes 422HQ into Premiere Pro CS6. Filmconvert Plugin on 20% and Grain, than applied additional custom Grain.
Sorry ADJ, I missed your post first time around - here's a link to the RAW Therapee documentation page:
http://rawtherapee.com/blog/documentation
I'm making some notes from the manual and then I'll install it and find out what it's like. The website also has a forum which should be able to answer any specific questions you might have. I'd like to know how well it handles batch processing large numbers of images (for video).
Quote from: kichetof on August 19, 2013, 01:44:07 AM
Thank's for this new release! I only tested few minutes.
- raw video works perfectly! (69mb/s on my lexar 16gb 1000x with global draw off)
- auto ettr works perfectly but only on live view
- auto exposure seem doesn't works (maybe it's too dark now)
I'll try more tomorrow!
Thanks for your work!
Hi,
After some tests everything works well! it was to late yesterday :-)
- - Auto exposure works well with the day light! It was too dark yesterday ;)
- - Auto ETTR works very well but only on live view (it's not great for timelapses :()
- - Dual ISO works well but I need to increase EV +1 to obtain a good result (on dark light) (I took some pictures with dual iso 100/1600, iso 100 and iso 1600 and the result seem like iso 100), the noise is very smoothly when you add 1EV to dual iso compared at iso 100 <-- awesome!
- - Digic focus peaking may be very useful!
- - Arkanoid is funny !
Thank's all for your works!
Hey fellows!
I want to try out Dual Iso but I seem to be doing something wrong when processing my Dual Iso pictures.
The images from 50D´s are O.K (two Isos are in all pictures I take in this mode.....) so:
Is there any good information about HOW TO process these pictures?
I´ve tried with cr2hdr , dcraw and exiftool (Windows XP and 7 wersions...) but nothing seems to happen! :(
Even tried with yout last update Andy600 without sucess!
Some help would be VERY APPRECIATE!
Thanks in advance...
Asier.
Quote from: Asiertxu on August 19, 2013, 03:09:39 PM
Hey fellows!
I want to try out Dual Iso but I seem to be doing something wrong when processing my Dual Iso pictures.
The images from 50D´s are O.K (two Isos are in all pictures I take in this mode.....) so:
Is there any good information about HOW TO process these pictures?
I´ve tried with cr2hdr , dcraw and exiftool (Windows XP and 7 wersions...) but nothing seems to happen! :(
Even tried with yout last update Andy600 without sucess!
Some help would be VERY APPRECIATE!
Thanks in advance...
Asier.
Drag and drop your .cr2 files onto cr2hdr.exe
Quote from: Monti on August 18, 2013, 03:02:34 PM
the thing that surprises me
that there is only 40-100 times downloads for each of the builds
is it just 40 people sticking around over this forum topic?
Yeah, I was very curious about this number. I always thought that the 50D was kind of "winning the world" now.
And my Transcend card never arrives... I think I'll post some tests I made with a 30mb/s "top speed" card. Because it's what I got now.
Quote from: goldenchild9to5 on August 19, 2013, 08:58:05 AM
I love my 50D Thank you Team @1% @Andy600 @a1ex for the advances. Hey guy's just been working diligently on different looks for my upcoming music video I'm so pleased with the results that I've been getting ;D. Let me know what you think...
Shot on Canon 50D with Magic Lantern Raw Hack.
Hack: Tragic 6
Resolution: 1584x586
Global Draw on, Small Hack on, Focus Peaking on, Zebra on, Histogram on, Waveform on..
Lens: super-multi- coated takumar 50mm f1.4 M42
Workflow: RawMagic into Davinci Resolve 9 Color corrected than exported as ProRes 422HQ into Premiere Pro CS6. Filmconvert Plugin on 20% and Grain, than applied additional custom Grain.
Amazing quality!
Keep up the good work! :D
Thank you @dogmydog appreciate it.. I will :D
Quote from: goldenchild9to5 on August 19, 2013, 08:58:05 AM
I love my 50D Thank you Team @1% @Andy600 @a1ex for the advances. Hey guy's just been working diligently on different looks for my upcoming music video I'm so pleased with the results that I've been getting ;D. Let me know what you think...
Shot on Canon 50D with Magic Lantern Raw Hack.
Hack: Tragic 6
Resolution: 1584x586
Global Draw on, Small Hack on, Focus Peaking on, Zebra on, Histogram on, Waveform on..
Lens: super-multi- coated takumar 50mm f1.4 M42
Workflow: RawMagic into Davinci Resolve 9 Color corrected than exported as ProRes 422HQ into Premiere Pro CS6. Filmconvert Plugin on 20% and Grain, than applied additional custom Grain.
SMC 1.4 Takumar legend lens! God that looks good, very filmic, there was a touch of moire/aliasing on the shutters at the end did you do anything specific about that, ie was it worse before. Guess grain helps, I only say because my most recent test is moire crazy and I'm not sure what to do about it. Also why 1584 x 586, were you shooting anamorphic or just cropping to get the look. Great stuff man.
Quote from: TrueIndigo on August 19, 2013, 10:32:05 AM
Sorry ADJ, I missed your post first time around - here's a link to the RAW Therapee documentation page:
http://rawtherapee.com/blog/documentation
I'm making some notes from the manual and then I'll install it and find out what it's like. The website also has a forum which should be able to answer any specific questions you might have. I'd like to know how well it handles batch processing large numbers of images (for video).
Hi True Indigo
Thanks for taking the time to reply. I saw the documentation before your post. I searched for "sequence" and "dng" in their 105 page document but it didn't return anything useful. I've just looked again and realise "batch" and "command" would have been a better searches. I thought I'd be more likely to get a sensible answer on here rather than on their forums since everyone shooting raw video is doing much the same thing albeit with different software. I didn't think many people shooting stills would be trying to do what we're doing. Anyway for the record their documentation is better than I first thought so I'll have a read at p91 on batch processing and p95 on the command line. I think I read somewhere that the batch operations are more stable.
Anyway I'm not in a rush. I have dng files but won't do anything serious until my adapters arrive. I'm going to take a leaf out of goldenchild9to5's book and use some old pentax prime lenses I have which are much faster than my canon zooms. One's an M42 and the other is a PK mount. I took my first real pictures on a pentax s1a many years ago and that didn't even have a light meter of any kind on it. I had to use and old Weston handheld meter. I never thought I'd be using the lenses again but I found them in an old kit bag the other day while I was looking for something else.
Quote from: Supermac on August 19, 2013, 07:20:46 PM
SMC 1.4 Takumar legend lens! God that looks good, very filmic, there was a touch of moire/aliasing on the shutters at the end did you do anything specific about that, ie was it worse before. Guess grain helps, I only say because my most recent test is moire crazy and I'm not sure what to do about it. Also why 1584 x 586, were you shooting anamorphic or just cropping to get the look. Great stuff man.
Thank you Supermac really appreciate your input.. Yeah!!! that SMC 1.4 is a sure winner, but I just ordered a Canon 50mm f1.8 for infinite focusing. You are definitely right moire and aliasing is definitely a problem, but there are ways around it for example focusing a little softer, depth of field, and finally blurring the Chroma channel in Resolve that's what I did It was way worse than what your seeing in the video. I almost forgot one last one grading helps a whole lot with aliasing and moire & don't use any sharpening that would make it worse I didn't use any in this video and still came out nice. I picked that resolution 1. because I wanted to get that aspect ratio while shooting without putting it later in post, and 2nd. because I didn't have my Komputerbay 64GB 1000X card It went bad I sent it back, waiting for the new one.. was forced to work with what I had a Sandisk 30mb/s 4GB 8) I know what your thinking but it did the trick... To tell you the truth I know nothing about Anamorphic shooting I'm clueless. All I'm gonna say is that Tragic 6-7 is the way to go even on that card I was able to get more than 15 seconds of footage incredible and with everything else left on just incredible great job Team Magic Lantern.
@ADJ "I'm going to take a leaf out of goldenchild9to5's book and use some old pentax prime lenses I have which are much faster than my canon zooms" ;) Yep.. The Pentax Prime Lenses are a must have, great thinking go back dust them off and put them back in your toolkit.
With the new Magic Lantern build Auto Exposure does not work for me. I enable it and nothing changes.
I've been using a 17-50mm Tamron zoom lately, and at f2.8 constant, it's not too bad, but really I'm an old lens fan too. I have two sets of 24mm, 28mm, 35mm and 50mm lenses in both Nikon F (AI-S) and Pentax PK. I think the extra clarity when shooting raw (compared to Canon H.264 video) really helps to bring out the character of these older lenses.
Got a call this morning from Mosaic Engineering. Mosaic Engineering is now creating the first beta 50D VAF. Should be ready within a couple of weeks or so...
...Will test the VAF and post some video/images here on ML.
Mosaic Engineering stated that a number of shooters have contacted them to purchase the 50D VAF. Again, I'll have a beta version, but they have mentioned that their goal is to produce an alpha 50D VAF... Will know more later.
This is great news!
Congratulations ML 50D users for the VAF :D less a problem to solve :D
Loving the new and improved site. I think it is going to be much easier for the newbies to find their way around installation and downloads. 8)
Quote from: LEVISDAVIS on August 19, 2013, 10:20:54 PM
Got a call this morning from Mosaic Engineering. Mosaic Engineering is now creating the first beta 50D VAF. Should be ready within a couple of weeks or so...
...Will test the VAF and post some video/images here on ML.
Mosaic Engineering stated that a number of shooters have contacted them to purchase the 50D VAF. Again, I'll have a beta version, but they have mentioned that their goal is to produce an alpha 50D VAF... Will know more later.
Woooooo Hooooooo!!!!! . . . :'( So emotional I could cry . . .)
Firstly! Loving the new site. Looks very clean and professional and makes Magic Lantern feel more legitimate then ever before. Great work. Second, I would like to just extend my thanks to the developers of ML and Andy600 for compiling the builds for the 50D. Much appreciated.
Thirdly, Because I keep hearing people say how absurd it is to use a flattening preset on RAW, saying it's no different than using Cinestyle, I decided to do a quick, ungraded comparison. Click images to see in full-res.
Here we have the H.264 with Cinestyle.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/h264cines.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/H.264cine.jpg)
And here we have RAW, with the Flatz Preset (http://www.dlwatson.net/flatz-preset.html) applied in ACR, rendered to DNxHD.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/rawflatzs.jpg) (https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/RAWflatz.jpg)
So...um....yeah. Thanks for playing. :)
Quote from: ADJ on August 19, 2013, 07:40:53 PM
Hi True Indigo
Thanks for taking the time to reply. I saw the documentation before your post. I searched for "sequence" and "dng" in their 105 page document but it didn't return anything useful. I've just looked again and realise "batch" and "command" would have been a better searches. I thought I'd be more likely to get a sensible answer on here rather than on their forums since everyone shooting raw video is doing much the same thing albeit with different software. I didn't think many people shooting stills would be trying to do what we're doing. Anyway for the record their documentation is better than I first thought so I'll have a read at p91 on batch processing and p95 on the command line. I think I read somewhere that the batch operations are more stable.
Anyway I'm not in a rush. I have dng files but won't do anything serious until my adapters arrive. I'm going to take a leaf out of goldenchild9to5's book and use some old pentax prime lenses I have which are much faster than my canon zooms. One's an M42 and the other is a PK mount. I took my first real pictures on a pentax s1a many years ago and that didn't even have a light meter of any kind on it. I had to use and old Weston handheld meter. I never thought I'd be using the lenses again but I found them in an old kit bag the other day while I was looking for something else.
So I have traveled this road already :) RawTherapee works nicely for batch processing. It is slower than ACR but I like the color handling that can be done with it. I built a batch program which allows you to build a preset in RawTherapee and then select the a preset to use with your raw files. It will allow your to drag and drop a whole directory of raw video, expand them to dng, and then apply presets to each one, after processing it uses ffmbc to make a prores444/yuv444p10 .mov file. Its all batch so feel free to borrow any of the command line code.
The biggest drawback is for some reason in batch mode RawTherapee seems to process white balance, sharpening, and microcontrast on the first file in the sequence horribly wrong your first frame will be unusable.
Your actual batch command might look like
rawtherapee -t -Y -p "%_presetFile%" -o "%CD%" -c "%CD%"
The batch file is going to look for dcraw.exe ffmbc.exe libiconv2.dll libintl3.dll raw2dng.exe regex2.dll and sed.exe in the folder with it. The zips in the linked thread provide those files. Raw2dng.exe is horribly out of date though.
Latest version of the windows based .bat file only I have
https://docs.google.com/file/d/0B2sc-xLyUSKqQWdPdlFHZjlPaU0/edit?usp=sharing
http://www.magiclantern.fm/forum/index.php?topic=5837
Quote from: jgerstel on August 18, 2013, 03:52:57 PM
Hi,
Installed Aug 17 build on my 50D today. I can not reproduce the bug above, so is working fine here. I prefer Tragic TL over ML, because it enables more seconds of recording in 1080p. Test today: avg 41 secs with 1920 x 1080 @ 24 fps. With ML is only a few secs. Also for dual iso: if you are using mac, you can use cr2hdr here:
http://www.gerstel.org/images/canon/dual_iso/cr2hdr
This also does not have the " green " issue.
BTW congratulations with the new website 8)
Cheers,
Jorgen
This link does not work on my mac . . .
Quote from: ADJ on August 17, 2013, 09:40:12 PM
I just got my D50 last week and am trying to catch up with all the new stuff. I tried to find some tutorials on Raw Therapee, either on the command line or otherwise but couldn't find much. I rarely buy software for anything but I'm sensing that many people on these forums has spent a fair bit of money on something from Adobe. The only other free alternative I've heard of is UFRaw but again finding good tutorials is something that's eluding me. Please let us know if you find anything useful.
ADJ and also to trueindigo there are a couple more options in the open source world that I can put out there since I like to experiment to.
Dcraw all platforms - insanely fast minimal options all command line
Photivo all platforms - very detailed and lots of options (eg. 5 types of denoise, 5 types of sharpening, both bayered and debayered methods). When I want the most out of a raw file I use this
Darktable linux mac - great with color with stackable filters (eg. apply the same filter 5x differently each time), my favorite interface besting even LR after setting a few hotkeys, but it does not cache anything kinda slows things down
RawTherapee all platforms - as already mentioned this one is pretty nice
I have been able to do batch processing from command line with all of these except I have not tried with darktable yet. ADJ can you tell me what you use for video editing.
Not sure if the forum is past posting video stills, but I had a great shoot this weekend with my RAW 50D and a Bolex anamorphic lens on a Zeiss 50mm.
http://imgur.com/a/lpE4l#3
Speaking of anamorphic ;) Is there any chance of an anamorphic preview for the 50D RAW? I for one, would greatly appreciate it! 8)
Quote from: menoc on August 19, 2013, 11:18:50 PM
Loving the new and improved site. I think it is going to be much easier for the newbies to find their way around installation and downloads. 8)
Yeah, great surprise today! It's very beautiful.
Hi, guys! I'm having a problem when I'm loading the modules with Tragic Lantern. It's impossible to use with the Global Draw and I don't how to check my histogram anymore.
I tried some builds and the one in this video is the first build with dual iso.
What do I have to do to fix it?
p.s.: sorry about the quality, two hands to record AND manage the 50D.
Hello. Currently me and my crew have been shooting in the RAW format on the Canon 50d
DSLR Camera, that was allowed by the use of Magic Lantern's Firmware. I have a few inquiries
and would like to know some opinions. Currently we have the following as a prototype workflow;
RAW2DNG> Davinci Resolve,Pro-RES files to Adobe Prmiere>(Adobe link is
being used so there is no rendering back out of after effects to be brought back
into premiere) AFter effects for compositing> back to resolve for final grade>
then xml back to prmiere for final rendering.
Is this workflow even possible? if it is, is it efficient? what other worklfow patterns are inb fact possible or even more efficient?
Welcome to the 50D community.. To tell you truth your workflow seems to be really complicated, I always try to keep it simple. For example my workflow is RawMagic -> Davinci (Do all my color grading and upscaling in Davinci) -> Export to ProRes 422HQ, or 4444 all depends on the project -> Into Premiere CS6 do all my editing & put the final touches on footage export for delivery voila..
@Molinsky - Have you tried deleting your config files?
Also, I noticed in your video that you have UniWB? Is anyone else missing this on the 50D because I don't seem to have it on mine ???
Edit: Just looked at the code and UniWB was removed by a1ex in June but I think 1% kept it in Tragic Lantern though it looks like it's now disabled in TL too????
Quote from: Andy600 on August 20, 2013, 02:25:12 AM
@Molinsky - Have you tried deleting your config files?
Also, I noticed in your video that you have UniWB? Is anyone else missing this on the 50D because I don't seem to have it on mine ???
Yes I'm missing the UniWB on my 50D. What does it stand for, or what function does it have?
Quote from: goldenchild9to5 on August 20, 2013, 02:50:00 AM
Yes I'm missing the UniWB on my 50D. What does it stand for, or what function does it have?
http://www.guillermoluijk.com/tutorial/uniwb/index_en.htm I'm not sure if it's intentionally removed from Tragic Lantern but it looks that way.
Quote from: Andy600 on August 20, 2013, 02:25:12 AM
@Molinsky - Have you tried deleting your config files?
Thank you very much, @Andy600! Everything is normal now. :D
Quote from: Andy600 on August 20, 2013, 02:25:12 AM
Also, I noticed in your video that you have UniWB? Is anyone else missing this on the 50D because I don't seem to have it on mine ???
I found the UniWB by accident. I was checking the RGB from a overexposed white picture and adjusted the white balance by the R/G/B multiplier. While the values differ, setting RGB to 1015, 1015 and 1103 respectively made me find the UniWB.
Quote from: goldenchild9to5 on August 20, 2013, 02:50:00 AM
Yes I'm missing the UniWB on my 50D. What does it stand for, or what function does it have?
It stands for "universal white balance". It means, basically, that I don't have to worry about it. My histogram for RAW is as close to reality as possible. I found this answer very good:
http://photo.stackexchange.com/questions/664/what-is-universal-white-balance-uniwb
UniWB was useful when the histogram was only RGB but it's not needed now because we have a raw histogram and zebras (when they are set to raw of course)
So, I don't have to worry about WB anyway?
@Andy600
My screen is all messed again. Everything changed back to default after deleting the configuration file. Then I changed the FPS override to 24, exact FPS. The overlay keeps changing as in the video.
Quote from: Molinsky on August 20, 2013, 03:05:18 AM
So, I don't have to worry about WB anyway?
You should still set correct WB but Raw video and Dual ISO photos are raw so WB can be adjusted in post. UniWB is for setting optimum exposure using RGB meters than actual white balancing which is why UniWB pics often turn out green and need correcting.
Quote from: Molinsky on August 20, 2013, 03:09:50 AM
@Andy600
My screen is all messed again. Everything changed back to default after deleting the configuration file. Then I changed the FPS override to 24, exact FPS. The overlay keeps changing as in the video.
Are you using the latest build?
The only builds I used was the ones from August 4th and 12th. I'll download the latest now.
Quote from: Molinsky on August 20, 2013, 03:19:05 AM
The only builds I used was the ones from August 4th and 12th. I'll download the latest now.
A lot can happen in a week so it's worth keeping up to date ;) but I don't think your problem is related to the build you are using. It must be something in your settings.
Quote from: Andy600 on August 20, 2013, 03:24:52 AM
A lot can happen in a week so it's worth keeping up to date ;) but I don't think your problem is related to the build you are using. It must be something in your settings.
Well, did everything from scratch. Formatted card, updated to ML 2.3, changed the ML folder and the autoexec.bin with the ones in the build and... everything ok until I change something.
I'll try again tomorrow.
Quote from: Molinsky on August 20, 2013, 04:36:58 AM
Well, did everything from scratch. Formatted card, updated to ML 2.3, changed the ML folder and the autoexec.bin with the ones in the build and... everything ok until I change something.
I'll try again tomorrow.
Molinsky try this download Andy's Tragic 7 build after you do don't change anything from it, than simply add the 50D firmware in that folder that's it. That should solve all your problems..
Quote from: paulforte on August 20, 2013, 12:41:26 AM
Not sure if the forum is past posting video stills, but I had a great shoot this weekend with my RAW 50D and a Bolex anamorphic lens on a Zeiss 50mm.
http://imgur.com/a/lpE4l#3
Speaking of anamorphic ;) Is there any chance of an anamorphic preview for the 50D RAW? I for one, would greatly appreciate it! 8)
Bolex looks great, nice ratio and no sign of vignetting too. Very cinematic. Is this the one with 39mm rear thread? What's the filter thread size of the Zeiss 50mm? There's a range of Anamorphic preview's under the display menu on tragic lantern, very useful for framing.
I've been thinking of ways to mount my Moller anamorphic lens to my rails and have I've ordered one of these.
http://www.indanc.co.uk/imagecache/3d48c652-5620-433c-8222-9e9600c02873_400x327.jpg (http://www.indanc.co.uk/imagecache/3d48c652-5620-433c-8222-9e9600c02873_400x327.jpg)
I was going to bolt it to a rail block and then lock it down in front of the taking lens but now I don't think it's going to work because the end of the taking lens is going to move back and forth when focussing.
How have other people mounted their anamorphic's?
(New site looks good)
This is a test I made to see the difference in quality from Raw to H.264.
With Raw I can get much more detail instead of H.264 compression artifacts (macro-blocking), and also the dynamic range is much wider allowing me to see the wrinkles in the chinese papaer lamp and also the details in the shadow areas.
Thanks to magic lantern for this awesome Raw feature!
You can follow my work on my website:
www.riccardocovino.it
@Riccardo - What ISO did you shoot?
Quote from: rockfallfilms on August 20, 2013, 12:09:57 PM
I've been thinking of ways to mount my Moller anamorphic lens to my rails and have I've ordered one of these.
http://www.indanc.co.uk/imagecache/3d48c652-5620-433c-8222-9e9600c02873_400x327.jpg (http://www.indanc.co.uk/imagecache/3d48c652-5620-433c-8222-9e9600c02873_400x327.jpg)
I was going to bolt it to a rail block and then lock it down in front of the taking lens but now I don't think it's going to work because the end of the taking lens is going to move back and forth when focussing.
How have other people mounted their anamorphic's?
(New site looks good)
I use a redstan clamp which is custom made for each of my anamorphics and gives a nice thread at the back for me to screw directly onto the taking lens. No problems with focusing but with the chunkier anamorphics you need to bolt onto rods also.
@Andy600:
I shot at 800 ISO, intentionally under-exposing.
I wanted to saved information on the lamp, and indeed I had them.
You can see here, in this attempt of extreme recovery, that you can see almost every wrinkle of the lamp paper!
(http://www.riccardocovino.it/wp-content/uploads/2013/08/crop.jpg)
yeah darling
i confirm latest build 19 august works better than 12 august
the frame rate changed from 55 to 67 mb/sec
in crop mode now it can shoot something like 2000 pixel and 1920 pixel with aspect ratio cinemascope
continuous non stop recording around 1 minutes
but this stops when comes to 4 gigabyte file size limit
ANYONE KNOWS HOW TO SURPASS 4 GB filesize limit?
also magic zoom and focus peak works
this is color graded noise reduced sample raw video frame on 1920 pixel in crop mode 3x zoom
yeah quite noisy but its coz crop mode and also high iso low light
(http://s003.radikal.ru/i203/1308/92/81869bfe4cec.jpg)
Quote from: Supermac on August 20, 2013, 02:49:26 PM
I use a redstan clamp which is custom made for each of my anamorphics and gives a nice thread at the back for me to screw directly onto the taking lens. No problems with focusing but with the chunkier anamorphics you need to bolt onto rods also.
Ok fair enough, do you reckon my Moller Anamorphot 32/2x is too chunky to hang off a redstan clamp? I was concerned that the weight might stress the taking lens or the lens mount.
Quote from: rockfallfilms on August 20, 2013, 03:55:26 PM
Ok fair enough, do you reckon my Moller Anamorphot 32/2x is too chunky to hang off a redstan clamp? I was concerned that the weight might stress the taking lens or the lens mount.
I'd recommend a support and a clamp, without support it will stress the taking lens, especially the focus barrel and it will make ultra difficult focus pulling almost impossible. Lenses bigger or longer than your standard 50mm and you'll definitely need support. My Schneider weighs nearly 2kg and is okay with a 50mm (Can't focus while shooting though). I can still use a longer lens but without support it picks up the slightest wobble.
Hey people
chill out
my first professional looking music video made by canon 50d and latest tragic lantern from Andy600
watch and learn
Quote from: Supermac on August 20, 2013, 11:20:18 AM
Bolex looks great, nice ratio and no sign of vignetting too. Very cinematic. Is this the one with 39mm rear thread? What's the filter thread size of the Zeiss 50mm? There's a range of Anamorphic preview's under the display menu on tragic lantern, very useful for framing.
Tragic Lantern - good to know; I've been using the July 27th build, but I'll take a look around. It's the Bolex Moller Anamorphot 19/8/1.5 which has a 24mm rear thread. This is mine - http://i.imgur.com/RBPNjRr.jpg - I've been using it with the Zeiss 50.. 1.4 which has a 58mm filter thread. BUT, the Zeiss does create a lot of chromatic abberation which I'm a little disappointed with (especially for a $700 lens) so I may experiment with an older Nikon or Canon FD.
Quote from: rockfallfilms on August 20, 2013, 12:09:57 PM
How have other people mounted their anamorphic's?
I also use a Redstan. Works very well for what I have. Solid - http://i.imgur.com/RBPNjRr.jpg
Seem to be having trouble with TL... Screen overlays such as Histogram and White Frame Boundary are always flickering; sometimes it stops when I activate the ML menu.
HDMI output problem with Unified and TL... HDMI output overlays are offset.
Here are two test examples...
1).TL - - Powered on Camera with the HDMI output connected to monitor and there are offset recording frame boundaries and also flashing overlays.
Results here (http://i.imgur.com/GWnWO16.png)
2). Unified - - Powered on the camera, activated LV and then plugged in HDMI. Here are the second results...
Results here (http://i.imgur.com/wLzdD8Z.png)
Quote from: Monti on August 20, 2013, 07:39:22 PM
Hey people
chill out
my first professional looking music video made by canon 50d and latest tragic lantern from Andy600
watch and learn
:D
finally a music video and not the usual cats and flowers.. ;)
nice grading, but the Parkinsonian shake of the camera is really disturbing!
Quote from: riccardocovino on August 20, 2013, 08:16:22 PM
:D
finally a music video and not the usual cats and flowers.. ;)
nice grading, but the Parkinsonian shake of the camera is really disturbing!
this is camera shake that reproducing old world war 2 times
the song says "oh bird dont sing let the soldiers sleep".
and cat goes to sleep at that moment.
i shot it in cyprus
and the idea behind this music clip is
cats were brought in cyprus to fight snakes in past times by humans
and cats were killing snakes and dying for humans
this is historical fact
so my music clip is like putting the real war song from 1945 from russia
to the cyprus cats as if they are the ones who fights the nazi (snakes) =)
I shot someone in front of a green screen for a few tests and used the 3-point light system usually used for chroma keying. The aperture was open all the way and the subject was a little dark, so I bumped the ISO to about 500 and it was just a little overexposed (by 1 slash whatever that is). After recording, I dropped it in AE to remove the green screen and it was noisy and tough to get a clean cut.
Any tips on chroma keying with Raw?
Quote from: Monti on August 20, 2013, 08:26:26 PM
this is camera shake that reproducing old world war 2 times
the song says "oh bird dont sing let the soldiers sleep".
and cat goes to sleep at that moment.
i shot it in cyprus
and the idea behind this music clip is
cats were brought in cyprus to fight snakes in past times by humans
and cats were killing snakes and dying for humans
this is historical fact
so my music clip is like putting the real war song from 1945 from russia
to the cyprus cats as if they are the ones who fights the nazi (snakes) =)
You're crazy, but I appreciate your crazyness!
Quote from: fromdecember on August 20, 2013, 08:39:31 PM
I shot someone in front of a green screen for a few tests and used the 3-point light system usually used for chroma keying. The aperture was open all the way and the subject was a little dark, so I bumped the ISO to about 500 and it was just a little overexposed (by 1 slash whatever that is). After recording, I dropped it in AE to remove the green screen and it was noisy and tough to get a clean cut.
Any tips on chroma keying with Raw?
Chroma keying and 3 point lighting aren't necessarily related.
To achieve a good chroma key the most important thing is to have uniform lighting on the green background.
So, no shadows, no gradients in lighting, no digital noise due to insufficient light.
Never put the character close to the green screen and if you need him to be dark leave enough space behind to allow you to lighten the greenscreen enough.
Quote from: paulforte on August 20, 2013, 07:53:28 PM
I also use a Redstan. Works very well for what I have. Solid - http://i.imgur.com/RBPNjRr.jpg
What taking lens have you got in that setup?
Quote from: riccardocovino on August 20, 2013, 08:55:12 PM
You're crazy, but I appreciate your crazyness!
There is nothing crazy about this historical fact. =)
read books about Cyprus
nobody doing any movie about it yet
but its very interesting how cats were protecting humans from snakes in cyprus
at least i made use of canon 50d for some cultural and historically valued, maybe spiritual idea)
Quote from: mjneubrander on August 20, 2013, 12:40:40 AM
ADJ can you tell me what you use for video editing.
Thanks for taking the time to post your replies.
What I have been using for SD or HD has been very basic editing with Avisynth, Virtualdub, and sometimes Cuttermarran before encoding for DVD or AVCHD. I haven't needed to pay for a fancy NLE application since I don't do editing on a daily or a weekly basis.
For ML video I'd like to get something free but which can do the job if that's possible. Because of the learning curve with new software I'd prefer to find one I like and stick to it. I downloaded Lightworks and ivsEdits LE last week and had a look at some video tutorials. As with the dng processing I'm finding it hard to find a solution with good tutorial support that isn't payware. Lightworks naturally seems to have the most support. ivsEdits looked good too but they've only added a Tiff importer recently (via Targa) and I haven't seen anyone on here mentioning it. Ideally I'd like a workflow which works on freeware so I can spend any money on cameras, lenses or computer hardware. I was on holiday last week but now I have less time to read. As always I appreciate the help people give on here which can save hours of trying to figure stuff out by myself. Have you used a lot of different editors yourself or do you stick to one in particular?
http://www.lwks.com/index.php?option=com_content&view=article&id=45&Itemid=184 (http://www.lwks.com/index.php?option=com_content&view=article&id=45&Itemid=184) lightworks
http://www.ivsedits.com/default/compare.aspx (http://www.ivsedits.com/default/compare.aspx) ivsEdits
Perhaps I should mention my PC is W7 x64 8GB Ram about 4.3GHz OC in case that makes a difference.
Hey dear Raw'ers ))
Recently I was shooting some footage with Red Epic at 100-200FPS with the resolution 2K.
I thought it would be a good test against our prominent RAW monster )
So please find attached some sample shots from 50D and Red Epic at 2K in comparison.
All shot at 320 ISO
Basically, I congratulate you all with our choice 8)
(http://i44.tinypic.com/23hkkfb.jpg)
50D image (upscaled to 1080p) and RedEpic 2K image (100% crops with my CC - black+white + some sharpening but not too aggressive)
Here are fullsize 100% crops (jpg'ed for web):
http://i40.tinypic.com/258cz0g.jpg (http://i40.tinypic.com/258cz0g.jpg)
http://i40.tinypic.com/295rd6f.jpg (http://i40.tinypic.com/295rd6f.jpg)
The original .DNG and .R3D files are here to play with:
https://copy.com/LlBywFCF7b29 (https://copy.com/LlBywFCF7b29)
here i show how to reduce moire in Adobe after effects, hope this is helpful :)
Quote from: paulforte on August 20, 2013, 07:49:45 PM
Tragic Lantern - good to know; I've been using the July 27th build, but I'll take a look around. It's the Bolex Moller Anamorphot 19/8/1.5 which has a 24mm rear thread. This is mine - http://i.imgur.com/RBPNjRr.jpg - I've been using it with the Zeiss 50.. 1.4 which has a 58mm filter thread. BUT, the Zeiss does create a lot of chromatic abberation which I'm a little disappointed with (especially for a $700 lens) so I may experiment with an older Nikon or Canon FD.
24mm thread, thats amazing that there's no vignetting. Are you shooting 1584 x 1058?
Quote from: lomka on August 20, 2013, 09:56:30 PM
here i show how to reduce moire in Adobe after effects, hope this is helpful :)
It's a bit hard to see which blending mode you pick.
Quote from: lomka on August 20, 2013, 09:56:30 PM
here i show how to reduce moire in Adobe after effects, hope this is helpful :)
Thanks mate, I'll definitely give that a try.
Quote from: PressureFM on August 20, 2013, 10:59:28 PM
It's a bit hard to see which blending mode you pick.
color
Quote from: rommex on August 20, 2013, 09:23:24 PM
Hey dear Raw'ers ))
Recently I was shooting some footage with Red Epic at 100-200FPS with the resolution 2K.
I thought it would be a good test against our prominent RAW monster )
So please find attached some sample shots from 50D and Red Epic at 2K in comparison.
All shot at 320 ISO
Basically, I congratulate you all with our choice 8)
50D image (upscaled to 1080p) and RedEpic 2K image (100% crops with my CC - black+white + some sharpening but not too aggressive)
Here are fullsize 100% crops (jpg'ed for web):
http://i40.tinypic.com/258cz0g.jpg (http://i40.tinypic.com/258cz0g.jpg)
http://i40.tinypic.com/295rd6f.jpg (http://i40.tinypic.com/295rd6f.jpg)
The original .DNG and .R3D files are here to play with:
https://copy.com/LlBywFCF7b29 (https://copy.com/LlBywFCF7b29)
Nice one Rommex, it's a good comparison 50d holds up really well. The Red would trash the 50d in low light though I bet.
Thanks lomka for the tip :D I think making this with real film gain is still better.
Quote from: arrinkiiii on August 21, 2013, 12:10:42 AM
Thanks lomka for the tip :D I think making this with real film gain is still better.
and how is that done?
Search in google for film grain and download it, use the blending mode in after effects and the % in the opacity. I think now you also got filmconverter, plug in.
See also http://gorillagrain.com/ or http://rgrain.com you have others also good. I think real film grain is more organic... but its a good tip.
Quote from: Supermac on August 20, 2013, 10:59:14 PM
24mm thread, thats amazing that there's no vignetting. Are you shooting 1584 x 1058?
24mm rear thread and 39mm front thread. And that image is on a 50. I actually just shot some footage with the Canon 40mm 2.8 pancake (which is as wide as I can go); here's a still, uncorrected - http://imgur.com/a/mAKsR - as you can see there's only a
tiny bit of vignetting here, but basically none. I actually recorded at 1584 x 892. Dang it! Didn't realize I could go higher - haha. I will now. Thanks :)
Quote from: goldenchild9to5 on August 20, 2013, 05:53:07 AM
Molinsky try this download Andy's Tragic 7 build after you do don't change anything from it, than simply add the 50D firmware in that folder that's it. That should solve all your problems..
@Andy600 & @goldenchild9to5
Thank you so much, guys, for all the help. I'm sorry about this late reply. Unfortunately (or not), I work all day and only have the night to test everything in the camera.
I deleted everything I would not use in the card: pdf files, other cameras firmwares, config files... and it works for now after I tested some customized videos.
The thing is: I use a very crappy card. It sucks so bad, has only 29mb/s of write speed. That's why I didn't posted any test, I'm waiting (forever) for my Transcend card. It is possible this card be the reason of such instable interface overlay?
Dammit, the overlay is flickering all over again! It only stops in two situations: either turn the Global draw off or turn the raw video mode off.
Is there a way to go above 1/120 shutter? I'm using tragic lantern and I have exposure override activated. (I don't care about the stutter in movement)
Short comparison video I shot between the Canon 550D's H.264 and the 50D's raw for those who are considering to make the switch :)
DELETED
While at job, I've been making some research and found that my issue (Canon gui flickering over ML overlay) is not new in the 50D raw environment.
Quote from: GregoryOfManhattan on June 08, 2013, 04:13:31 PM
for those following along at home, the empire strikes back and the canon gui is showing up during raw recording in my recent build.
you do NOT want the canon gui during raw recording as it will slow it down.
ideally you'd want to use magic lantern histogram and spot exposure during raw recording.
(waveform is based on YUV not raw so it may not be entirely accurate during raw recording)
Quote from: a1ex on June 08, 2013, 04:14:52 PM
Active and moving? that's not quite good.
The only easy solution that I see right now is to try globaldraw on and all other things disabled.
Or... hack the CONFIG_KILL_FLICKER code so Canon GUI can be disabled from some other tasks too. Not sure what is the best way to implement this; maybe a reference counting like LV RAW mode from raw.c.
Seems there is a CONFIG_KILL_FLICKER ifdefs somewhere (found it instantiated at internals.h?), because the problem occurs when I load the modules. I also tried some stuff already recommended, but nothing solves the bug. Since only myself, apparently, is having this problem and I keep deleting the config file, is there something I have to set in the Canon menu?
ps¹.: funny thing, I also found a lot of overlay bugs reports (i.e. http://www.magiclantern.fm/forum/index.php?topic=3697.msg36245#msg36245 and http://www.magiclantern.fm/forum/index.php?topic=1886.0 )
ps².: if someone is not aware of the problem I'm dealing with, watch this video:
.
Quote from: Molinsky on August 20, 2013, 04:36:58 AM
Well, did everything from scratch. Formatted card, updated to ML 2.3, changed the ML folder and the autoexec.bin with the ones in the build and... everything ok until I change something.
I'll try again tomorrow
Andy
I would like to share this first video test (handheld) that I shot with Tragic Lantern 2.0 and also say many thanks for you guys! I am very happy with the result of the videos I got with may old 50D!
Clovis
[url]http://www.magiclantern.fm/forum/Themes/default/images/bbc/url.gif
ML grayscale preview is fighting with canon overlay. Change the preview mode in the raw module.
Thanks for the reply, @1%. But it's flickering with any of the previews. Actually, I made a very extensive evaluation sequence here and I noticed that it's really something in the raw module only. I let every other module loaded (but the raw_rec.mo), and it's ok.
But load the raw module and try to use it... BAM! I have to shoot without any ML overlay, totaly blind about the right framing, histogram and stuff.
A friend of mine says that I like to play with "Flickr", the camera. Pun intended.
(http://venturebeat.files.wordpress.com/2012/10/flickr-dolphin.jpg?w=558)
I laughed, but I'm getting frustrated.
Its not doing it to me. I think an extra black bar is drawing with raw_rec + movie mode.
I did find some display filters fight with the grayscale preview, ie defish.
Hi,
I copied Modules folder under ML directory, however nothing happens. Please let me know what shall be done in order to enable it in my 50D. Do I have to copy the files raw_rec.o, raw_rec.mo & magic.sym in another folder?
Thanks,
Ed
(http://www.magiclantern.fm/Users/Eduardo/Desktop/xxx.jpg)
@Molinsky - Can't reproduce your problem.
Can you upload your magic.cfg and raw_rec.cfg files?
Quote from: Andy600 on August 22, 2013, 12:45:01 PM
Can you upload your magic.cfg and raw_rec.cfg files?
Oh boy, not now. Just when I get home. :P
Quote from: 1% on August 22, 2013, 05:24:43 AM
Its not doing it to me. I think an extra black bar is drawing with raw_rec + movie mode.
I did find some display filters fight with the grayscale preview, ie defish.
I have no ideas anymore. Having problem with all the previews.
Quote from: Batasuna on August 22, 2013, 06:07:25 AM
I copied Modules folder under ML directory, however nothing happens. Please let me know what shall be done in order to enable it in my 50D. Do I have to copy the files raw_rec.o, raw_rec.mo & magic.sym in another folder?
Did you loaded the modules after started the camera?
Hi,
I decided to try dualISO on my 50D,
I put this Tragic.Lantern-2.0-Andy600.Build.2013Aug19.50D109 on my empty CF
and then used this 50D_cr2hdr.zip + Use these for processing Raw video files or Dual ISO photos.zip
but unfortunately I still have only green/white zebras in highlights - without any other details.
What am I missing here, please?
@Batasuna - Copy everything in the zip to your card including the autoexec.bin ::) DO NOT change the directory structure!
@Orim - You are probably over exposing your shots. Are you using the raw histogram, raw zebras? 'raw' being the important bit ;)
Hey Andy, is there a way to go above 1/120 shutter speed?
Quote from: araucaria on August 22, 2013, 02:54:56 PM
Hey Andy, is there a way to go above 1/120 shutter speed?
Try changing the FPS Override 'optimize for' setting. Hi Jello should let you go a lot higher (maybe1/4000 etc).
I get 1/150 at 24p with 'exact'.
Also, noticed something with FPS under artificial light when shooting last night. The 50D's video mode is NTSC 30p and usually you can trust the shutter speed indicator when it turns green but I had to drop to a slightly lower shutter speed to remove the slow flicker caused by AC in Europe. I don't think this is an issue on cameras that have native 25p PAL so it's worth double checking for that 'out of sync' flickering before hitting record.
Quote from: Andy600 on August 22, 2013, 02:33:49 PM
@Orim - You are probably over exposing your shots. Are you using the raw histogram, raw zebras? 'raw' being the important bit ;)
Andy600,
thank you for your interest.
The best I can have on picture (in lightroom from dng) is a green highlighted window, with green "shadow" on the wall...
It is far away from your results...
I had ETTR on, so I switched it off and used 100/1600 dualISO.
Any advice, please?
Quote from: orim on August 22, 2013, 03:14:06 PM
Andy600,
thank you for your interest.
The best I can have on picture (in lightroom from dng) is a green highlighted window, with green "shadow" on the wall...
It is far away from your results...
I had ETTR on, so I switched it off and used 100/1600 dualISO.
Any advice, please?
Check the Dual ISO thread. I know very little about how to set-up Dual ISO or how to get the best results. Of the shots I have taken using Dual ISO some have worked and others have highlight issues and that (I think) is because I haven't yet read-up on how to shoot with it correctly.
Quote from: Andy600 on August 22, 2013, 03:10:36 PM
Try changing the FPS Override 'optimize for' setting. Hi Jello should let you go a lot higher (maybe1/4000 etc).
I get 1/150 at 24p with 'exact'.
Also, noticed something with FPS under artificial light when shooting last night. The 50D's video mode is NTSC 30p and usually you can trust the shutter speed indicator when it turns green but I had to drop to a slightly lower shutter speed to remove the slow flicker caused by AC in Europe. I don't think this is an issue on cameras that have native 25p PAL so it's worth double checking for that 'out of sync' flickering before hitting record.
Thanks a lot!
Quote from: Andy600 on August 22, 2013, 03:10:36 PM
Also, noticed something with FPS under artificial light when shooting last night. The 50D's video mode is NTSC 30p and usually you can trust the shutter speed indicator when it turns green but I had to drop to a slightly lower shutter speed to remove the slow flicker caused by AC in Europe. I don't think this is an issue on cameras that have native 25p PAL so it's worth double checking for that 'out of sync' flickering before hitting record.
Same issue I noticed. As you say the ntsc mode could not monitoring the image in a way you can get rid of it. Maybe Mr1% can give us some "light".....
You should be able to get whatever shutter speed you want now since its ADTG not head timers.
Syncing to things like lights and screens doesn't work on this camera. On others you can tweak the speed a little bit and make lights/tvs stop flickering. 50D it doesn't work, just starts flashing the whole image.
Quote from: 1% on August 22, 2013, 08:30:41 PM
You should be able to get whatever shutter speed you want now since its ADTG not head timers.
ADTG doesn't solve anything about shutter speed freedom.
g3gg0 wrote to me about this topic when I asked to him if ADTG can solve the shutter speed/jello effect limitations:
"
There are the same technical limitations like before.
Hi shutter speed requires a fast clock. But the timer for fps has a limited range.
So you can only have 1/(adtg_val) 'th of the fps rate as shutter speed iirc.
But thats long ago when i understood that.
Technically nothing new. We access these registers since months, but in a indirect way.
"
Do you all agree ? Or there is something new here ?
How do I change the exposure meter to go a bit the center without affecting ISO and aperture? Is there a way?
Before ADTG you could only select like 1/24 to 1/120, now it lets you select 1/24 - like 1/2000. I'd say that's a bit more freedom, hence no more shutter speed in the FPS menu. Shutters under FPS and ridiculously high shutters are probably not possible.
Quote from: kichetof on August 18, 2013, 01:05:36 PM
@Andy
There are a bug with yours TL latest update. When you record a raw video, when you finished the video by click on SET, the blue light flashed, the red light too and the display turn off. When you click on live view button you return on photo mode and the display on. When you re click on LV, the display turn off. After turn off the body, click on LV works fine the first time and the second time I've an error 99.
The crashlog:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Aug17.50D109
Mercurial changeset : 74dac53a5f5e+ (build-bot-2.0) tip
Built on 2013-08-16 22:57:26 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 285K + 3183K
And the log: http://pastebin.com/dbkL5nAi (sorry it's too long to copy here)
I hope it's useful for you!
Thanks a lot !
Edit : don't appear on the previous TL update (august 12th Tragic.Lantern-2.0-Andy600build.2013Aug12.50D109-DUAL-ISO)
Hi guys,
More informations about my previous problem
(perhaps similar to Molinsky).
With the latest Tragic Lantern 2.0, when I switch from photo mode to live view, the screen come black and the dslr not responding (only the LCD control panel display av,tv,iso..). The solution is to remove battery for reuse.
So, I disable all module and activate one by one and switch from photo mode to live view to identify which one cause trouble. I've the problem when I activate raw_rec module. When it's disabled, no problem appears.
I also had a problem when I leave the live view to return to camera mode (when raw_rec disabled), I get a vsync error.
Do you have some suggestions ? Could I try something to help you ?
Thanks for your works!
Quote from: 1% on August 22, 2013, 08:30:41 PM
You should be able to get whatever shutter speed you want now since its ADTG not head timers.
Syncing to things like lights and screens doesn't work on this camera. On others you can tweak the speed a little bit and make lights/tvs stop flickering. 50D it doesn't work, just starts flashing the whole image.
Thanks for the information. Great work man!!!
Quote from: kichetof on August 22, 2013, 10:17:19 PM
Hi guys,
More informations about my previous problem (perhaps similar to Molinsky).
With the latest Tragic Lantern 2.0, when I switch from photo mode to live view, the screen come black and the dslr not responding (only the LCD control panel display av,tv,iso..). The solution is to remove battery for reuse.
So, I disable all module and activate one by one and switch from photo mode to live view to identify which one cause trouble. I've the problem when I activate raw_rec module. When it's disabled, no problem appears.
I also had a problem when I leave the live view to return to camera mode (when raw_rec disabled), I get a vsync error.
Do you have some suggestions ? Could I try something to help you ?
Thanks for your works!
[sigh] Yesterday, I had all problems possible and wasn't able to post here other tests or the config file.
But it's hard anyway when no one else has reproduced the bug.
The log:
2839: 38239.779 [STARTUP] ERROR ASSERT : Stub.c, Task = LVC_AE
2840: 38239.860 [STARTUP] ERROR ASSERT : Line 29
2841: 38239.903 [STARTUP] ERROR ASSERT : 0
2842: 38240.611 [STARTUP] startupErrorRequestChangeCBR : OverWrite (0x1d => 0x1d)
2843: 38268.795 [GUI] DlgLiveView.c UnvisibleLvDialogItemForBlackout
2844: 38304.212 [LV] FD_SetAfState(7) Mode:2
2845: 38304.234 [LV] AF Mode FACE
Do you use face detection AF because raw module disables it. Also get black screen booting LV if face detection is on w/ raw_rec. I guess you found the side effect :)
Quote from: 1% on August 23, 2013, 03:07:37 PM
The log:
2839: 38239.779 [STARTUP] ERROR ASSERT : Stub.c, Task = LVC_AE
2840: 38239.860 [STARTUP] ERROR ASSERT : Line 29
2841: 38239.903 [STARTUP] ERROR ASSERT : 0
2842: 38240.611 [STARTUP] startupErrorRequestChangeCBR : OverWrite (0x1d => 0x1d)
2843: 38268.795 [GUI] DlgLiveView.c UnvisibleLvDialogItemForBlackout
2844: 38304.212 [LV] FD_SetAfState(7) Mode:2
2845: 38304.234 [LV] AF Mode FACE
Do you use face detection AF because raw module disables it.
Effectly, AF mode was configured with face detection. I change to Quick Mode and no problem with module raw_rec but I always have vsync err on a black box (corner top left). It seem to doesn't affect anything.
Thanks 1% to find this!
Not sure what you turned on to get a vsync error. Would need a way to reproduce it. I tried peaking/spot/histo/zebras all at once and it was ok. AF quick is OK but opens and closes LV every time so I avoid it.
Ok... I think I found vsync err.. its from auto ETTR but that is working here so not sure what is conflicting with it/breaking it.
Yes I confirm. I disabled auto ETTR and I don't have this error.
I saw something strange, I have two lines that blinking every second when movie on with raw_rec enable
(through the two black bands).
(http://oi40.tinypic.com/ief3th.jpg)
Maybe it's normal ;)
Do you have information about the development of auto-ETTR in photo mode?
Quote from: 1% on August 09, 2013, 12:45:21 AM
I want to do 50D raw histos in photo mode but I need to figure out how to make those state diagrams from a good idc and with things named + current fw version.
9x1 is working on 6D with the naming. I'll try some other cams, esp older like 50D.
*prop browser is there and working. Just not as flexible as mem spy. Maybe needs something that builds a whole list of properties + data and then you can search through it. Would be useful to try to find stuff like focus data on M/50D, etc.
Auto ETTR is working here, it opens LV, closes LV and takes an ETTR reading.. so I don't know why its not working for you.
The lines are from ML grayscale preview, I think its bigger under the overlays.
Maybe I have misspoken.
Auto-ETTR works great in live view. It works well in photo mode only by pressing SET button, it doesn't works on Always on or other setting.
This is what I do:
Enable all it's necessary for auto-ETTR in Overlay
(http://oi43.tinypic.com/2hg47kk.jpg)
Enable auto-ETTR and set to Always On
(http://oi43.tinypic.com/256egcy.jpg)
Try with 2s, 4s, 8s and Hold in review time.
So I can not use it to make timelpase
I don't understand what I'm doing wrong...
I think I figured it out. If you close LV before auto ETTR finishes up you get the vsync error. Always on and auto snap I think isn't working for photo mode unless LV is on. I won't have raw data for captured photos (for like raw zebras in photo) until I get a new graph of the state objects. Assume this is where the problem is coming from as it works as expected on 6D (most supported after 5DIII).
I know what's the problem! I've made some test in dark situation... I try now and I can reproduce the vsync problem when I put the lens cap and switch to photo mode before auto-ettr finish and bingo! Err vsync.. so it's not a real problem :)
Ok, so I understood right. Auto-ETTR works only on live view (in photo mode, you need to go in live view to obtain the value).
Do you have any plan to develop this on 50d? Maybe I'll write a little script to take time-lapse with auto-ettr without keep live view on a long time.
Seems like ETTR exposure to the right
means over exposing shot making it too bright
is good thing to get a good low noise captures
check this picture out
(http://schewephoto.com/ETTR/normal-300-after-TN.jpg)
but what about the auto ettr?
what exactly it is auto about?
50D raw test with sports.
Handheld, so little shaky
Canon 50mm 1.8 lens to experiment DOF. This was needed to prevent moire of building behind the sports facility.
ACR workflow and upscaled to 1080p. Added some sharpening, boost lows and reduced highs, no colour grading.
Quote from: jgerstel on August 23, 2013, 09:14:43 PM
50D raw test with sports.
Handheld, so little shaky
Canon 50mm 1.8 lens to experiment DOF. This was needed to prevent moire of building behind the sports facility.
ACR workflow and upscaled to 1080p. Added some sharpening, boost lows and reduced highs, no colour grading.
You really need an ND filter ;)
Fast shutter speeds are ok for sports but I think maybe this is a little too much. Get an ND and you'll have much better control over DOF in daylight.
Good effort though considering it's handheld :)
QuoteDo you have any plan to develop this on 50d?
Yea, I just need to get/make the state diagrams so I know when to grab the raw data.. .works on 5DII so should here... its not identical tho so not super easy :(
Quote from: 1% on August 24, 2013, 01:17:05 AM
Yea, I just need to get/make the state diagrams so I know when to grab the raw data.. .works on 5DII so should here... its not identical tho so not super easy :(
Great news!!! Thanks man for your hard work!
Don't hesitate to ask if you want me to test something ;)
i love you magic lantern people
literally
developers and compilators
you are the best
Latest 50D discovery: It's a tough S.O.B.
So I was out shooting yesterday evening and had the camera on a fully extended tripod while I looked for a spare battery. Stupid me hadn't secured one of the tripod legs and a couple of seconds after turning by back the leg collapsed and the tripod toppled over with the 50D taking the full impact on the asphalt. I was horrified but apart from an unstuck LCDVF frame, a few grazes to the body and a scuffed mode dial it was fine. I'm actually glad the camera hit and not the lens. I doubt my 600D would have survived.
Apart from the accident I got some great test footage that has confirmed to me that the 50D is capable of some seriously good looking images and I don't to upgrade anytime soon 8)
Quote from: Andy600 on August 24, 2013, 05:53:54 PM
Latest 50D discovery: It's a tough S.O.B.
So I was out shooting yesterday evening and had the camera on a fully extended tripod while I looked for a spare battery. Stupid me hadn't secured one of the tripod legs and a couple of seconds after turning by back the leg collapsed and the tripod toppled over with the 50D taking the full impact on the asphalt. I was horrified but apart from an unstuck LCDVF frame, a few grazes to the body and a scuffed mode dial it was fine. I'm actually glad the camera hit and not the lens. I doubt my 600D would have survived.
Apart from the accident I got some great test footage that has confirmed to me that the 50D is capable of some seriously good looking images and I don't to upgrade anytime soon 8)
ameen man
Quote from: Andy600 on August 24, 2013, 05:53:54 PM
Latest 50D discovery: It's a tough S.O.B.
So I was out shooting yesterday evening and had the camera on a fully extended tripod while I looked for a spare battery. Stupid me hadn't secured one of the tripod legs and a couple of seconds after turning by back the leg collapsed and the tripod toppled over with the 50D taking the full impact on the asphalt. I was horrified but apart from an unstuck LCDVF frame, a few grazes to the body and a scuffed mode dial it was fine. I'm actually glad the camera hit and not the lens. I doubt my 600D would have survived.
Apart from the accident I got some great test footage that has confirmed to me that the 50D is capable of some seriously good looking images and I don't to upgrade anytime soon 8)
Don't upgrade the camera, upgrade the tripod ^^. Share the footage :D
Hey guys,
I'm new to the forum, but have been watching / reading up on the 50d Raw stuff for a little while. I decided to register and jump in here to drop a question or two, and to also get more involved with the community! I found a good deal on a 50d and it should be here mid next week! I'm excited, but a little uncertain / lost, as I've never shot RAW before, and really only ever used a t3i for video / photo. I did use ML a good bit, just not the RAW module. I have done some research and tried to figure out as much as I could before it gets here and I can actually dive in and do some tests of my own.
I did have a few questions, if someone would be kind enough to answer, or show me a link where I can read for myself.
I see on the OP of this thread that they got 70 mb/s output on the 50d. I've also seen tests where this number fluctuates and spikes. I ordered a Transcend 32 GB 1000x 160 read / 120 write CF card. Is this fast enough? What max resolution could I get continuous? Is there a need to invest in a 1066x Toshiba card @ 150 mb/s?
I know that 32 GB will go fast, so I'm asking before I make another purchase.
Also, I've seen a lot of raw tests on youtube. Some look incredible @ default 360p. Others look cropped and don't seem to be that great of quality. What are the do's and don'ts here from you experience?
Any recommended settings / advice would be greatly appreciated!!!! This post maybe should've went partially in a introduce yourself section, but considering the 50d is relative, I posted here.
Sorry for the small book, I just unloaded.
Quote from: Andy600 on August 24, 2013, 05:53:54 PM
Latest 50D discovery: It's a tough S.O.B.
So I was out shooting yesterday evening and had the camera on a fully extended tripod while I looked for a spare battery. Stupid me hadn't secured one of the tripod legs and a couple of seconds after turning by back the leg collapsed and the tripod toppled over with the 50D taking the full impact on the asphalt. I was horrified but apart from an unstuck LCDVF frame, a few grazes to the body and a scuffed mode dial it was fine. I'm actually glad the camera hit and not the lens. I doubt my 600D would have survived.
Apart from the accident I got some great test footage that has confirmed to me that the 50D is capable of some seriously good looking images and I don't to upgrade anytime soon 8)
Ouch! I did that with my 550D a couple of years ago, luckily it was on rails and the follow focus took the brunt of it. Horrible feeling watching it fall though!
@abpcl - Most people are using 1000x 64gb Komputerbay cards
abpcl:
You've got a great card to start out with. You'll be able to record at any resolution the camera can record. The card will last about 9 minutes in a 16x9 aspect ratio when using the full sensor. When in 3X mode the recording times and recording lengths are far less. However, if you're into optimizing you can nearly squeeze out a 1920x1080. However, I presume to say your 32GB card will last about 5 minutes in this setting.
The users have been reporting the do's and don'ts with this camera now since about the beginning of the Raw Module development. Seems the highest priority is ETTR (Exposure to the Right). It's possible to record at ISO 200 (the lowest sensor noise setting) and have a lot of noise in the image if the image isn't exposed properly. It's possible to shoot at an ISO 800 and have less noise than ISO 200 if the image is truly exposed to the right. Basically, you'll probably not want to shoot higher than ISO 800 if you're concerned with lots of noise. Again though, every time you shoot you'll want to expose to the right. What happens is the noise embedded in the video is nearly eliminated when you adjust the contrast, exposure, and highlight recovery options in post.
The camera goes through batteries pretty quick, about an hour at best using a 2200mAh.
The camera will overheat and negate your ability to shoot about 22 fps when shooting in high-heat situations (above 90 - 95 degrees).
If you're using Image Stabilization the only way to activate is by half pressing the shutter release button while recording.
For proper testing of the camera - - make sure not to adjust the color profile. I typically stick to Standard or Neutral. Then I will adjust the contrast up to about 1 or 2 out of 4 and also boost the color saturation to 1 of 4.
It's typically a bad idea to use a profile that acts like a color-correction filter because the sensor only records raw information. Exposing your image to the processed color-picture profile usually results in under exposing the image. Remember, in post you want to have an image that is exposed to the right. If you're pushing your image to the right in post you're introducing a great deal of artifacts that could have been avoided in production.
The Canon 50D produces a great image. However, take special care when shooting video of sharp lines and finite detail (especially in the distance). The sensor is only capable of resolving so much detail out of a shot. If there is a great deal of detail in your shot I'd shoot off two shots. One of them the way you prefer and the other with a slightly soft image (some people say using a poor quality UV filter works and other's say to simply adjust your focus so that the image is soft.)
That's about it... It's going to take some time to get used to the rhythm... But hang tight and suddenly this ML page will start coming to life. There's tons of great direction and great wisdom on ML.
you know what?
im using lexar x1000 card 16 gb
and it is enough only for around 4 minutes of raw video
damn it
64 gb komputerbay would be much helpful of coz
also need to at least 2 of them
Thanks Levi! Your post was very informative. I will definitely keep ETTR a priority when I start testing. Thanks!
I'm posting 2 links. And I'd like to know what you think.
In the first video, the guy is shooting a slow card, and shoots at a lower resolution for 1280 x 720p. However it looks great!!! But whats going on, @ :34 and :35. The clarity of the flower snaps @ :35.
http://www.youtube.com/watch?v=Ut02ekKykE4
In this second video, the guy shoots at a higher resolution. It looks great as well.
http://www.youtube.com/watch?v=kx0_Kc6_Jkc
I don't exactly know what questions to ask regarding the difference between these 2 tests, because I'm a noob. But if my card can record continuous at a higher resolution, wouldn't I always want to shoot at the highest resolution possible? And then upscale for uploads to youtube?
Quote from: Andy600 on August 24, 2013, 05:53:54 PM
Latest 50D discovery: It's a tough S.O.B.
So I was out shooting yesterday evening and had the camera on a fully extended tripod while I looked for a spare battery. Stupid me hadn't secured one of the tripod legs and a couple of seconds after turning by back the leg collapsed and the tripod toppled over with the 50D taking the full impact on the asphalt. I was horrified but apart from an unstuck LCDVF frame, a few grazes to the body and a scuffed mode dial it was fine. I'm actually glad the camera hit and not the lens. I doubt my 600D would have survived.
Apart from the accident I got some great test footage that has confirmed to me that the 50D is capable of some seriously good looking images and I don't to upgrade anytime soon 8)
50D is still alive 8) Yeah your right.. the images are just beautiful, hope we see some of your footage posted soon.
Quote from: abpcl on August 24, 2013, 11:53:37 PM
In this second video, the guy shoots at a higher resolution. It looks great as well.
http://www.youtube.com/watch?v=kx0_Kc6_Jkc
in the end he says he shoot it in japan
and ISO is 100-6400
so means he did HDR video isnt it
otherwise no chance to get such clear video in night time shoot
Hey guys,
I wanted to say thanks SO MUCH for Magic Lantern Raw. It's amazing to shoot such sharp images (when you're not missing focus). Here's an example of me missing focus a lot, and pretending to be a nature cinematographer.
No grade. A bit of CA compensation, but you can still see plenty. Some pretty blown out highlights too which I didn't think about, or remove in post. Lots of warp stabilizer.
https://vimeo.com/73021391
or
https://www.youtube.com/watch?v=i95jOiBqyPo
just messing around and can't make file spanning to work on my 50D with 64gb komputerbay card. Allways shuts down after 4gb... Do I miss something?
Quote from: fotto on August 25, 2013, 02:46:11 PM
just messing around and can't make file spanning to work on my 50D with 64gb komputerbay card. Allways shuts down after 4gb... Do I miss something?
yeah thats problem to me too on lexar 16 gb
it shuts after 1 minute that is 4 gb
but that is limitation of file size on this systems
Quote from: doctortran on August 25, 2013, 03:41:18 AM
Hey guys,
I wanted to say thanks SO MUCH for Magic Lantern Raw. It's amazing to shoot such sharp images (when you're not missing focus). Here's an example of me missing focus a lot, and pretending to be a nature cinematographer.
No grade. A bit of CA compensation, but you can still see plenty. Some pretty blown out highlights too which I didn't think about, or remove in post. Lots of warp stabilizer.
https://vimeo.com/73021391
or
https://www.youtube.com/watch?v=i95jOiBqyPo
awesome camera work, awesome compositions, awesome storytelling, awesome editing, awesome music matching
color grade is missing
but how did u make awesome slow motion?
what was your workflow?
p.s. you should get Grammy for that, seriously...
Spanning works here, just tested. It takes 3 shoots to get me to 1920x1038 continuous and I think auto mode isn't returning global draw to on.
okay dudes
a huge present from me to everyone
i made a zoom comparison video on raw canon 50d
this shows how much helpful is to shoot in crop mode
a simple Nikon 70-300 mm VR ED attached to canon 50d
becomes a 3000 mm super tele zoom Full HD video camera
first i shot in 70 mm and then go to 300 mm
then go to 10x crop mode
so in reality that gives me 112 mm and 480 mm and 3000 mm lens.
watch this in HD or Full HD mode only!
p.s. the resolution sucks for unknown reason from VIMEO site
so i am did it another way and soon i update this link to better one
in other words check this is a frame from the video above and how does it magnify
(http://s005.radikal.ru/i209/1308/92/ee5c11b490c1.jpg)
and this is frame from maximum magnification zoom 3000 mm lens
(they dont even sell such lenses in the world. and they cost like 20.000$ for 800 mm or little more)
(http://s017.radikal.ru/i440/1308/5e/f2552abfca1c.jpg)
the above magnified frame is even increased its resolution to 1920 in crop mode
and the first one was like 1572 in normal mode
that crazy thing above is good even for a stills photo
its giving around 2 megapixel raw files
(which is more than I ever use to share my photos online or whatever you want to print it like A3+ size clean)
on 3000 mm lens like 24 burst photos per second with no buffer limitations continuously for 1 minute
then another 1 minute and again until your compact flash card is full with this 4 gb 1 minute files
that is double of what canon 1dx can do (12 burst shots per second)
also buffer size is limited for like 100 shots maybe
only there is no VR and also manual focus only
so you need like tripod to use this construction i made
but this is good for wildlife and sports shooting when u dont want to miss any frame
they do this on canon 1D C that cost like 13.000$ for 4K video but that is compessed H.264 video
and it is not a raw files like in here
so this on canon 50d i made a great opening on magic lantern (tragic lantern) thing.
(http://s019.radikal.ru/i617/1308/bb/8eceb8de5389.jpg)
Quote from: abpcl on August 24, 2013, 07:15:16 PM
I'm excited, but a little uncertain / lost, as I've never shot RAW before, and really only ever used a t3i for video / photo. I did use ML a good bit, just not the RAW module.
Well first things first learning ML on the T3i took some getting used to. Unlearning some of what I learned and figuring out the 50D was a lot more painful. I was actually going to write a guide and put it in this thread to address some of the early pitfalls.
The first thing for raw is get a Komputerbay 64 gb x1000 card. They are relatively cheap and they hit the speed targets you need for raw. Second thing is to make sure you get a 32gb or smaller CF card. You can't install ML the first time with a 64 GB card. I just got a 4gb Sandisk card for that purpose.
Next if you want to do 1920x1080p 23.976 fps that only works in cropped mode. Okay, how do you get to cropped mode? When you are in live view press the button in the far right upper corner. It has a little blue magnified glass with a plus in it as a label. It took me awhile to figure out how to get into this crop mode everyone was talking about.
On the T3i I use the zebras to expose till the highlights are barely clipping or about to clip. On the 50D I use the histogram and EV value. I try to get the historgram as far to the right as possible and make the EV value 0 or as close to zero as I can without clipping highlights.
In the raw menu there is a place to turn on ML Grayscale preview. Use this to line up your shot for 1920x1080. None of the other modes accurately show the scene in crop mode for me. Maybe Iim doing something wrong. Yes the ML Grayscale mode looks horrible but you just need if for framing. Once you have everything framed up then turn global draw off. Then press the "set" button to begin recording. A read out will show you your recording speed. North of 80 mb/s is where you want to be. Don't worry if you are a little blow. A lot of the time it speeds up as you record. There is also a nifty read out that tells you how many frames have been recorded and how many more frames you can expect to record if current conditions prevail. As your card speeds up the expected number of frames will increase even as you are recording.
The worst part about 1920x1080 for me isn't the record time. It's the crop factor. The crop factor is nice because it eliminates most moire/aliasing. But it is like the 3x zoom factor on the t3i except you don't have a live picture to help you follow objects/animals/people that you are zoomed in on.
Crop mode on the 50D is butt ugly compared to the 3x zoom on the t3i. It really makes you appreciate how polished ML is on the t3i. But when you finally see the results out of the 50D you will know it will always have a spot in your stable. When I have the time and the scene is appropriate nothing in the price range touches the 50D... Nothing. Keep in mind if you don't use the ML grayscale preview what is shown in the screen is not an accurate representation of what you will record. I don't know why.
Quote from: abpcl on August 24, 2013, 07:15:16 PMAlso, I've seen a lot of raw tests on youtube. Some look incredible @ default 360p. Others look cropped and don't seem to be that great of quality. What are the do's and don'ts here from you experience?
Well a lot depends on the original resolution, conversion software, compression codec, and how the operator and Youtube beat up the file. I've seen, no lie, compressed SD footage demonstrating 50D raw. Only a psychiatrist can explain that. 1920x1080p 23.976 fps in crop mode looks excellent when processed and exposed properly. Using inadequate available light and underexposing ruins even a good thing. I would rather bump up the ISO than underexpose at a lower ISO. Beyond that use a fast (f/1.4, f/1.8, or f/2.8 in a zoom) lens to get plenty of light. A stabilizer such as a monopod, tripod, glidecam (probably useless for crop mode), or shoulder rig improves shots immensely. I don't understand the plethora of shaky hand held test videos. I mean set the camera on a table, chair, rock, car hood, etc. if you can't afford or be bothered to buy/borrow/steal a tripod. Where did these people learn photography/videography?! They are wasting people's time and bandwidth.
keywords: Canon 50D, Magic Lantern, raw, tips for beginners, instructions, guide, cropped mode, zoom
Quote from: Monti on August 25, 2013, 02:58:01 PM
awesome camera work, awesome compositions, awesome storytelling, awesome editing, awesome music matching
color grade is missing
but how did u make awesome slow motion?
what was your workflow?
p.s. you should get Grammy for that, seriously...
Thanks man!
Slow motion was just warp stabilizer. I don't know how it happened -- it just came out slower.
Workflow was raw2cdng, and lightroom with a jpeg export. Then into gopro studio and used premiere pro for editing. Windows based.
I just uploaded the test I was doing when my camera took a nose dive on the pavement. The video is in 2 parts - ungraded and graded. Description in the video.
I've uploaded the 1080p H.264 version (that Vimeo re-encoded to 720p) if anyone wants to see the full resolution video (500MB) we.tl/wKhNyBjCD7 (http://we.tl/wKhNyBjCD7)
Here are a few 1080p frame grabs from the graded part so you can see the quality: http://imgbox.com/g/IKS6mQOvec (http://imgbox.com/g/IKS6mQOvec)
Quote from: 1% on August 25, 2013, 04:42:02 PM
Spanning works here, just tested. It takes 3 shoots to get me to 1920x1038 continuous and I think auto mode isn't returning global draw to on.
whoa, whoa
1920x1038 continuous ?
:o
Quote from: Andy600 on August 26, 2013, 02:50:50 AM
I just uploaded the test I was doing when my camera took a nose dive on the pavement. The video is in 2 parts - ungraded and graded. Description in the video.
oh yeah
thats canon quality video
i have few questions about it
what is workflow for this smooth frame rate
why there is no color and things are flat
and who is this gorgeous girl =)
btw i found there is no way to upload anything on VIMEO
so i uploaded my previous video to youtube
canon 50d raw video with zoom magnification 112 mm to 3000 mm Nikon lens
you can watch it on this link
http://www.youtube.com/watch?v=k_rUGH0RCWM
also watch it on HD or Full HD only
@Monti
1. A tripod and 180 degree shutter angle (and frame rate conformed to 24p in the NLE)
2. No colour? If you mean why is there less contrast, it's deliberate. I increased the black level a bit to pull up the shadows and give it a more 'film' like look. Film Convert Pro also alters colours to match film stock. I used 'Velvia' for this and played with the colour temperature to get the look I wanted. I was aiming for the cool blues and orange look. The first part of the video is just the DNG files with white balance corrected.
3. The gorgeous girl is my better half. She's very photogenic don't you think? ;)
Quote from: Andy600 on August 26, 2013, 04:47:34 AM
@Monti
1. A tripod and 180 degree shutter angle (and frame rate conformed to 24p in the NLE)
2. No colour? If you mean why is there less contrast, it's deliberate. I increased the black level a bit to pull up the shadows and give it a more 'film' like look. Film Convert Pro also alters colours to match film stock. I used 'Velvia' for this and played with the colour temperature to get the look I wanted. I was aiming for the cool blues and orange look. The first part of the video is just the DNG files with white balance corrected.
3. The gorgeous girl is my better half. She's very photogenic don't you think? ;)
Sure she is...
about color grading
look what i did with your video
and tell me which one is better?
yeah i mean i can understand when someone want to keep certain colors
but look i didnt change that colors
but they just look better at my edition IMHO
(http://s16.radikal.ru/i190/1308/30/f72b59eaef89.jpg)
@Monti - Of course, you can push the colour in all directions with raw files but I was going for a specific film look without harsh sharpening and overly contrasted skin detail. Watch a few movies ;)
As for which I prefer, I'll stick with my original but thanks for the example :)
however personally i woud personally do this color grading to your footage
(http://s020.radikal.ru/i718/1308/b1/fcd5c0693ce6.jpg)
or if i want a final fantasy look
(http://s42.radikal.ru/i095/1308/93/358f3c40d015.jpg)
any of those look pretty to me
and the one you did looks unfinished and flat
however i agree that for certain areas your look is what has to be there
just for me the subject of raw video on canon 50d asks to be something more than "filmic look"
btw all this examples i did not on raw file
it was just screenshot from vimeo video
so not even jpg
Grading is subjective. Everyone has their own likes and dislikes ;)
I prefer to create the look myself based on my own vision of how the shot should look, in the context of the piece. I usually steer clear of preset/instagram/Magic Bullet type looks and just using Film Convert Pro is pushing it for me.
well im also not using all those crap you mentioned
im just working in photography area mostly
and when we come to subject of getting such awesome video from canon 50d raw
i just question myself
why people push themselve hardly to do magic lantern
and then not using its potencial in post production...
p.s. btw u mentioned a major point why people cant or not doing color grading most of the time
coz its not in their head
coz to draw you have to see it in your head
and if you not artist then there is nothing to follow after
thats the key of why people stuck for something and not going further maybe....
I shot a short film over the weekend that I'm calling it Dichotomy. Not only will the short be about the contrast of emotions, but also has been a great example of the dichotomy between H.264 & RAW workflows.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/1-s.jpg)
I purposefully shot the film on the fly, handheld, in bad lighting situations, and entirely with an Rokinon 85mm lens.
Ill be releasing a workflow tutorial along with the short when it's released this week. The above screenshot is only a proxy render from the RAW - I can't wait to the grading phase using the actual DNG files.
@D.L. Watson - Interesting idea! Looking forward to watching it :)
Quote from: Monti on August 26, 2013, 05:15:50 AM
Sure she is...
about color grading
look what i did with your video
and tell me which one is better?
yeah i mean i can understand when someone want to keep certain colors
but look i didnt change that colors
but they just look better at my edition IMHO
(http://s16.radikal.ru/i190/1308/30/f72b59eaef89.jpg)
Personally, I like the look of Andy's original picture. Looks more filmic. A bit like Velvia with the magenta and stuff but obviously flattened as Velvia is much more punchy and contrasty (Always thought Velvia was a bit Garish outside of landscape and fashion anyway).
As for Monti's looks, I think the first one might be more of a music video look, second is a bit "walking dead" although might work for a commercial centered around domestic abuse. The third option looks like you've gone mental with Nik colour effects. Definitely Final Fantasy and I'd like to see the video out of curiosity.
Guess the key thing with grading (as with every other creative decision) is to have a direction and a point to doing it, not just because you can. My favorite shot is probably the air ducts, very filmic looking, although the shoes look great too. Hmmm, I'm in the mood for shooting now... Where's my camera.
A customer can ask for any of those, and hopefully pay for the post work. I don't think any is "wrong". Or they just might want flat.
BTW, raw histos and all that jazz are now working, so you can ETTR with time lapse, etc.
Thanks @Supermac - The Airduct shot was a complete fluke. The light was perfect ::)
I did have a little play in Resolve today for an alternate look (just to try and educate myself a bit) and came up with this:
Grade #2
(http://i.imgbox.com/acsAFB6W)
It was around 16 nodes using power windows and qualifiers. I need to get better at this obviously.
Original
(http://i.imgbox.com/adzLoKAf)
Full size: http://imgbox.com/g/gV925C5RSp (http://imgbox.com/g/gV925C5RSp)
@1% - Just had a look at your TL commits. Nice work dude! I'll compile a new build tonight unless you already have one uploaded.
Quote from: Andy600 on August 26, 2013, 07:14:54 PM
@1% - Just had a look at your TL commits. Nice work dude! I'll compile a new build tonight unless you already have one uploaded.
"photo mode raw for 50d" ? What is this into the details ? :o
Quote from: Andy600 on August 26, 2013, 06:54:48 PM
Thanks @Supermac - The Airduct shot was a complete fluke. The light was perfect ::)
I did have a little play in Resolve today for an alternate look (just to try and educate myself a bit) and came up with this:
Grade #2
(http://i.imgbox.com/acsAFB6W)
It was around 16 nodes using power windows and qualifiers. I need to get better at this obviously.
Full size: http://imgbox.com/g/gV925C5RSp (http://imgbox.com/g/gV925C5RSp)
oh yeah much better)
now you are talking hehe
@1% if it's what I think, you're crazy!! And I like this!
Quote from: Andy600 on August 26, 2013, 07:14:54 PM
@1% - Just had a look at your TL commits. Nice work dude! I'll compile a new build tonight unless you already have one uploaded.
I'm ready to update :)
Quote from: Andy600 on August 26, 2013, 06:54:48 PM
Thanks @Supermac - The Airduct shot was a complete fluke. The light was perfect ::)
I did have a little play in Resolve today for an alternate look (just to try and educate myself a bit) and came up with this:
Grade #2
(http://i.imgbox.com/acsAFB6W)
It was around 16 nodes using power windows and qualifiers. I need to get better at this obviously.
Original
(http://i.imgbox.com/adzLoKAf)
Full size: http://imgbox.com/g/gV925C5RSp (http://imgbox.com/g/gV925C5RSp)
Very nice pics, Andy! Keep it up! :D
Meanwhile I just had a frustrating experience with my first crop shoot and auto ETTR.
I put the camera on the tripod, config Auto-ETTR to half shutter and shot at 3x crop with ML grayscale preview.
I ended up with a baaaad out of focus result. I tried grain and increasing sharpness but it was helpless.
I don't know what happened. I put the 50D on the tripod, magnified 10x to verify focus and everythin was ok.
One thing i know i did wrong is I left the lenses with AF on.
Any hints on what may have happened ,ppl?
Andy has been very kind and shared some his footage with me so I could show off a very nice and simple filmlike workflow I've set up.
On the samples I have done very little grading, just some basic film look I'm happy with.
(http://farm6.staticflickr.com/5451/9600157863_506e24caac_h.jpg)
flat+saturation+curves+lut
(http://farm6.staticflickr.com/5496/9600157045_8260ec989e_h.jpg)
flat
(http://farm6.staticflickr.com/5461/9600156509_08e1c96d86_o.jpg)
flat+saturation+curves+lut
(http://farm4.staticflickr.com/3823/9600156505_ae1a753b0b_o.jpg)
flat
(http://farm6.staticflickr.com/5529/9600156499_e929aad457_h.jpg)
flat+saturation+curves+lut
(http://farm3.staticflickr.com/2819/9603390096_30f5f7f281_h.jpg)
flat
(http://farm6.staticflickr.com/5451/9603389864_4371cecba4_o.jpg)
flat+saturation+curves+lut
(http://farm8.staticflickr.com/7299/9603388952_4f5d3f4e4f_o.jpg)
flat
As you can see, no noise reduction, great 50d footage from Andy.
What you need:
my camera profile for Adobe programs:
for normal dng: https://www.dropbox.com/s/vkdm3uc4n5x7i26/MLfilm.dcp
for cinema dng: https://www.dropbox.com/s/8yhv4qsquaygs3s/MLfilm%20strong.dcp
installation instructions: http://www.magiclantern.fm/forum/index.php?topic=5586.msg66775#msg66775
Once open in Adobe Camera Raw you will leave everything as it is, go to the camera icon (camera calibration) and if you installed the camera profile correctly you will see the camera profile, select the profile and go back to the main adjustment screen, correct exposure and whiteblance if needed. That's it. (make sure you change the color space to a 16bit color space, you can set that at the bottom line in ACR).
If you are using resolve you will export the secuence as a uncompressed 16bit tiff.
If you are using After effects be sure that you are working at least in 16bit.
Apply the lut.
Download the LUTs:
Juanmelara converted these great print emulation LUTs to a Resolve and After Effects compatible format.
http://juanmelara.com.au/print-film-emulation-luts-for-download/
download these from the blogpost:
Fujifilm 3510
Fujifilm 3513
Kodak 2383
Kodak 2393
If you want to use Resolve he will explain how to, I will focus on After Effects.
For the Samples above I used Fujifilm 3510, the blue in the shadows is rather strong but I like it a lot.
So once you have your secuence in After effects you will apply the lut, choose the "Apply Color LUT effect" under the "Utility" section. Search for the LUT you want to use (use the ConstClip ones) and voila ther you go, this is your starting point. If you are not happy wiht exposure or whitebalance , interpret the footage in ACR again, (right click on footage, interpret footage, more options)
There you go, now add some curves and turn the darks down a little, maybe change the curve in some color channel, and add some saturation (+20,+30 works for me).
I hope you enjoy this, have fun.
Rember one thing, in both, Resolve and After Effects, the LUT will be you last node or layer, every adjustment should be done under or before the last layer, node.
yeah baby)
color grading parade started
QuoteOne thing i know i did wrong is I left the lenses with AF on.
When you were doing auto ETTR the lens tried to focus. I moved my AF to AF on because of this.
Yes please, build and post. My internet is sucking today + bitbucket is squirly with uploads.
The latest Tragic Lantern 2.0 for the 50D is up: https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip)
Includes several important fixes.
Raw exposure meters now work in photo mode 8)
ETTR and Dual ISO have some new settings to play with.
There is a NEW 'Modified' menu (nice)
I have also included up-to-date raw2dng.exe and cr2hdr.exe for processing your raw videos and Dual ISO images. The folder is inside the zip so move it to your desktop before copying the autoexec.bin and ML folder to your CF card.
As ever, big thanks to 1% for his sterling work on the 50D specific code that is better known as Tragic Lantern! and to a1ex, g3gg0 and other devs for their hard work.
Don't forget. I'm not a dev. I just build this shit ::)
update: recompiled as new changes were just added
As always, amazing work to the devs, but Andy, I've never seen someone stay so on top of fresh builds and uploads for the community as you. A huge thanks to all.
I was a second shooter for a friend at a wedding recently. Dual ISO worked like a champ later in the evening for low light party time, but I tried to shoot some 'Silent Pictures' which output to DNG files during Live View, and got some frames that were really weird. I remember seeing some of this earlier in the thread, but no solution. Any help on this? Not all frames came out like this, but it would be nice to shoot like this with full confidence.
(http://i.imgur.com/2Hs7WYi.jpg)
A few more frames following the link.
http://imgur.com/a/4Vx1T/#0 (http://imgur.com/a/4Vx1T/#0)
Quote from: dsManning on August 27, 2013, 02:34:20 AM
As always, amazing work to the devs, but Andy, I've never seen someone stay so on top of fresh builds and uploads for the community as you. A huge thanks to all.
I was a second shooter for a friend at a wedding recently. Dual ISO worked like a champ later in the evening for low light party time, but I tried to shoot some 'Silent Pictures' which output to DNG files during Live View, and got some frames that were really weird. I remember seeing some of this earlier in the thread, but no solution. Any help on this? Not all frames came out like this, but it would be nice to shoot like this with full confidence.
It went
3 good frames
1 bad frame (pink lines)
2 good frames
3 bad frames (2 pink lines, 1 green)
2 good frames
2 bad frames (1 green, 1 green & pink lines)
1 good frame
2 bad frames (1 pink lines, 1 green)
over the course of 15 seconds or so. Just uploaded the bad frames as .jpg 700px long egde for the forum. Can upload the entire .DNG sequence if anyone can help resolve.
(http://i.imgur.com/2Hs7WYi.jpg)
A few more frames following the link.
http://imgur.com/a/4Vx1T/#0 (http://imgur.com/a/4Vx1T/#0)
Sorry meant to modify, not quote. Edited in red.
What mode where you shooting in? Zoom? I don't think anyone has been checking the silent pics. Raw video doesn't do this but has different sync, etc.
Ok, I reproduced like this:
FPS to 30.00 + zoom mode + dng burst. This way a shit ton of pics are fucked up.
I disable dialog timers.. gd is on 30fps, no bad pics. I dunno, don't blame me ;)
5x Zoom
Canon 24-70 2.8 II
error
Quote from: scrizz on August 27, 2013, 04:00:55 AM
did you really have to quote the whole thing? lol
I thought I pressed modify :S
Does anyone get any bad frames with timers disabled? I think best shots is all bad frames since no LV focus data.
Quote from: Andy600 on August 27, 2013, 01:33:21 AM
The latest Tragic Lantern 2.0 for the 50D is up: https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip)
Includes several important fixes.
Thanks 1% and Andy600 for the new build! Is there a link where we can see commit changes? Somehow I can't find it on bitbucket.
Cheers
Quote from: Andy600 on August 27, 2013, 01:33:21 AM
The latest Tragic Lantern 2.0 for the 50D is up: https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip)
Includes several important fixes.
Raw exposure meters now work in photo mode 8)
ETTR and Dual ISO have some new settings to play with.
There is a NEW 'Modified' menu (nice)
Does it mean ETTR works in photo mode or has wider range in LV now? I can't check myself as I'm abroad without computer — some heavy use of Dual ISO and Auto Expose here :)
Quote from: derkiki on August 27, 2013, 09:31:50 AM
Thanks 1% and Andy600 for the new build! Is there a link where we can see commit changes? Somehow I can't find it on bitbucket.
Cheers
Only by looking at commits https://bitbucket.org/andy600/tl50d/commits/all (https://bitbucket.org/andy600/tl50d/commits/all). There is currently no change log produced.
@akumiszcza - You will need to read the ETTR thread for more information
Quote from: akumiszcza on August 27, 2013, 09:46:09 AM
Does it mean ETTR works in photo mode or has wider range in LV now? I can't check myself as I'm abroad without computer — some heavy use of Dual ISO and Auto Expose here :)
basicly ETTR (EXPOSURE TO THE RIGHT)
means all your shots will be exposure compensation up for 1.33 stops
that means your shots will be brighter than normal
but when you normalize it in your programm it give much less noise
than if you shoot normal raw files
Are there any 40D builds available, or only 50D? (I'm only asking because of the topic name)
Quote from: Supermac on August 26, 2013, 06:26:26 PM
Personally, I like the look of Andy's original picture. Looks more filmic. A bit like Velvia with the magenta and stuff but obviously flattened as Velvia is much more punchy and contrasty (Always thought Velvia was a bit Garish outside of landscape and fashion anyway).
As for Monti's looks, I think the first one might be more of a music video look, second is a bit "walking dead" although might work for a commercial centered around domestic abuse. The third option looks like you've gone mental with Nik colour effects. Definitely Final Fantasy and I'd like to see the video out of curiosity.
Guess the key thing with grading (as with every other creative decision) is to have a direction and a point to doing it, not just because you can. My favorite shot is probably the air ducts, very filmic looking, although the shoes look great too. Hmmm, I'm in the mood for shooting now... Where's my camera.
if you want to know what is filmic look
look at this new movie from germany with Till Shweiger
and yes, i see lots of colors there and its not flat
(http://s002.radikal.ru/i199/1308/f2/1ae310c44ddb.jpg)
also for those of you
who didnt learnt composition
check this filmic look camera composition on rule of thirds
it is aimed into the eye section to attract our view there
(http://s61.radikal.ru/i173/1308/29/d478f52b31c2.jpg)
and yes
when they shot this scene they told to Till Shweiger to hold and not move his head
Quote from: rufustfirefly on August 27, 2013, 03:51:11 PM
Are there any 40D builds available, or only 50D? (I'm only asking because of the topic name)
The 40D is not currently supported but @jplxpto is working on porting ML http://www.magiclantern.fm/forum/index.php?topic=1452.msg66726#msg66726
Whether it will ever have raw video capability is another matter. If it does there will likely be limitations to frame size and write speeds because of the smaller pixel count of the sensor and slower CF card slot.
@Monti - I appreciate your input here but perhaps we're starting to stray too far from the intended subject matter of the thread which is raw video on the 50D. The cinematography, color, grading, aesthetics, film and other areas of film making are probably worthy of their own thread (maybe there are similar threads here on the ML forum?).
Incidentally, although you are correct with your observations about contrast, colour, framing etc, there are also many other examples where DPs and colourists will do the exact opposite and go for a low contrast/desaturated look and not stick to the rule of thirds at all. As I said, it's purely subjective and individual but obviously it's good to know the theory and always educate yourself.
You did actually make me think more about my grading TBH. I still like what I did because it fits the mood and look I intended, but also I know I can push myself further and be more creative with colour. It's great that raw video lets us explore these possibilities properly.
Quote from: Andy600 on August 27, 2013, 04:30:13 PM
@Monti - I appreciate your input here but perhaps we're starting to stray too far from the intended subject matter of the thread which is raw video on the 50D. The cinematography, color, grading, aesthetics, film and other areas of film making are probably worthy of their own thread (maybe there are similar threads here on the ML forum?).
Incidentally, although you are correct with your observations about contrast, colour, framing etc, there are also many other examples where DPs and colourists will do the exact opposite and go for a low contrast/desaturated look and not stick to the rule of thirds at all. As I said, it's purely subjective and individual but obviously it's good to know the theory and always educate yourself.
You did actually make me think more about my grading TBH. I still like what I did because it fits the mood and look I intended, but also I know I can push myself further and be more creative with colour. It's great that raw video lets us explore these possibilities properly.
yeah i went far coz just answered the previous commenter
and also my intention of pushing this subjects is to open up raw video subject
as those who shoot films in hollywood are doing it on raw video as meant to be on canon 50d
so i just highlighted that if someone shooting on magic/tragic lantern raw video
then it makes sense to follow up the highest standarts of cinematography
if people learn basic of their video job then they may make use of all magic/tragic lantern feautures
otherwise targeting on something small makes the limited thoughts on the rest of job
must push forward
and not to stop on something obvious and simple as can be made on anything else
ps i mean developers work hard here and you also complile new features day by day
it is just not fare not to make use of it in post production
@Andy600
your previous color grading photos is not opening anymore
something happen with links
@Monti - ah, I can see your point now ;D and think you're right. I think most users who are shooting raw are probably just content with the increased IQ over H.264 but raw video gives us so much more flexibility on the colour side. I'm currently doing an alternate grade on my test footage as an exercise in Resolve. It's looking great but there's a lot more work involved.
re: images. Yes, I noticed my images from imgbox were not showing but a browser cache refresh fixed it.
PROGRESS UPDATE:
I just shot the opening day of the US Open yesterday with a week old build. There was one instance where I couldn't change the exposure in time to film a gigantic screen, so the RAW filming saved my ass in a major way. I can't thank this team enough.
Soon I'll be releasing another fashion film using the 50D and I've made sure to include your logo in the end credits. This has now become a standard w/ my team when using Magic Lantern software overall :)
(http://farm6.staticflickr.com/5493/9609338358_3782bc48b0_c.jpg)
Now we are talking! Hehe...
Sorry about the huge quotes but I get the impression that Silkway and Monti are the same person or perhaps twins.
Especially if you look at Silkway's last login day/time and Monti's registration day/time.
Quote from: Silkway on August 16, 2013, 06:35:46 PM
of coz i might show when i make something on canon 50d
now i can only show what i did on nikon d7000 which is not this topic discussion)
my green cat was made on 640 by 240 pixel
which is less than my old nokia n86 can do
it is raw video 14 bit color 24 frame per second on 6 mb/sec continuous non stop raw video
on kingston 10 years old compact flash old technology card
(http://www.my-batteries.net/images/memory-card/KINGSTON-COMPACT-FLASH-CF-MEMORY-CARD-TDCF01.jpg)
3 times less consuming than h.264 codec compressed on Nikon D7000
which is also very very light and compressed video shooter
so i just set a new record of raw shooting with that green cat shot for most less consuming raw shoot) that was fun
to show that the quality is not so bad
when it comes to a memory card speed for continuous shooting on low resolution in raw
also i dont ask shit people for their step by step color grading
i ask from the master of art like D.I.Watson
i said clip above was stupid except for one shot
so to prove you i just made a screen shot of the 2:08 seconds shot of this clip above
check it and judge for yourself.
(http://s018.radikal.ru/i509/1308/3a/1cb046ec159f.jpg)
i didnt measure it
i just chosed a shot that look nice to me
and i just applied a 3 parts on horizontal and vertical
really straight lines and 3 parts
the eye and nose felt just on 2 of key points
and if you remember for a good camera composition
your objects target must be at least close to one of this 4 key points where lines are crossed
and if u ask why? who made this rules?
God made, when he made our eyes and brain
scientists found that human looks on this 4 cross points of the image automatically at first look
starting fromo top left going to top right then bottom left and bottom right
so if u wana attract attention of a viewer place your message there
otherwise it is stupid composition that is not attracting at all.
oh my god
this shot was GOOOD
but the rest is awful
Quote from: Monti on August 27, 2013, 04:03:15 PM
if you want to know what is filmic look
look at this new movie from germany with Till Shweiger
and yes, i see lots of colors there and its not flat
(http://s002.radikal.ru/i199/1308/f2/1ae310c44ddb.jpg)
also for those of you
who didnt learnt composition
check this filmic look camera composition on rule of thirds
it is aimed into the eye section to attract our view there
(http://s61.radikal.ru/i173/1308/29/d478f52b31c2.jpg)
and yes
when they shot this scene they told to Till Shweiger to hold and not move his head
@KahL:
I didn't expect 50D to be involved in such kind of work, great!
Ususally covering sport events requires continuous recording, how did you manage the storage problem?
I guess You had to stop and change cards/batteries so frequently!
Quote from: rockfallfilms on August 27, 2013, 06:59:12 PM
Sorry about the huge quotes but I get the impression that Silkway and Monti are the same person or perhaps twins.
Especially if you look at Silkway's last login day/time and Monti's registration day/time.
yeah coz the moderator blocked Silkway for being too haarch in critic about others works
Quote from: Monti on August 27, 2013, 09:10:48 PM
yeah coz the moderator blocked Silkway for being too haarch in critic about others works
lol
Quote from: 1% on August 26, 2013, 06:41:55 PM
BTW, raw histos and all that jazz are now working, so you can ETTR with time lapse, etc.
@1% you are amazing!! Auto-ETTR works well on photo mode! Amazing!!
Thanks a lot for that!
Hey I've been doing some shots in crop mode and I wanted to say that if you shoot with 1920 horizontal resolution it's actually a 2.5x crop not a 3x crop.
Quote from: araucaria on August 28, 2013, 01:35:54 AM
Hey I've been doing some shots in crop mode and I wanted to say that if you shoot with 1920 horizontal resolution it's actually a 2.5x crop not a 3x crop.
2.475x at 1920p to be precise ;)
2.376x at max 2000px
I didn't actually think about this until you mentioned it ;D
Quote from: Andy600 on August 28, 2013, 01:51:56 AM
2.475x at 1920p to be precise ;)
2.376x at max 2000px
I didn't actually think about this until you mentioned it ;D
I was handholding my sankor 16 anamorphic in front of the 50d to try out crop mode, so I thought, 58mm/3= 18,3mm will do fine but I it was full of vignetting, so I just did the math and there it is ;)
Btw, is there a way to center the crop mode center to the sensor center, it's a pain in the ass to guess because in ML hacked preview you can't move the crop window, or it's super super buggy.
im going to test out the ETTR function soon
curious about it kinda
it may give high shutter speed in photo mode without bumping ISO over 800
or maybe we should use it in Dual ISO mode?
then put the shutter speed even higher...
for those who are not familiar with photography -
high shutter speed gives a tack sharp images without blur or washed out
but it needs high ISO (light sensitivity) that usually kills color depth, dynamic range (contrast) and clarity (noise grain comes).
so to shoot on high shutter speed without going bad maybe good to ETTR it instead of high ISO it?
i know some people do shoot on high ISO on raw underexposed (dark) then bringing up image from shadows in program
but with ETTR can be even better
also if high ISO it maybe ETTR saves it kinda too...
I guess center to 5X raw isn't working?
Quote from: 1% on August 27, 2013, 12:15:15 AM
When you were doing auto ETTR the lens tried to focus. I moved my AF to AF on because of this.
Yes please, build and post. My internet is sucking today + bitbucket is squirly with uploads.
What do you mean by moving your AF to AF on? Using the switch on the lenses or ML menu?
Ty for the reply, 1%. Big fan of your work :)
I mean take AF off of 1/2 shutter. On 50D you can set it to the AF on button.
okay i tested ETTR thing
very frustrating experience
the ISO going up and down as it wish
hard to do something
shutter speed goes to 1/15 by itself
dont know which mode to use
should it be manual or apperture priority or what?
but got one good example though
this is it
(http://s017.radikal.ru/i440/1308/23/de0abc93d450.jpg)
(http://s020.radikal.ru/i707/1308/fb/c080f7c2bd9a.jpg)
also tested ETTR with Dual ISO
show it later
ETTR has settings like set lowest shutter from main dial... auto expo has to be set up too... my lens can't do f1.8.
Quote from: 1% on August 28, 2013, 04:56:09 PM
ETTR has settings like set lowest shutter from main dial... auto expo has to be set up too... my lens can't do f1.8.
oh yeah? i have to learn that...
otherwise really killing
i try to go in function menu but didnt find such tweaks
maybe search later
this is dual iso test on ETTR
(http://i049.radikal.ru/1308/22/8f53cc36b6c4.jpg)
(http://s005.radikal.ru/i212/1308/72/d9000f07d72a.jpg)
Quote from: Andy600 on August 27, 2013, 04:13:14 PM
The 40D is not currently supported but @jplxpto is working on porting ML http://www.magiclantern.fm/forum/index.php?topic=1452.msg66726#msg66726
Whether it will ever have raw video capability is another matter. If it does there will likely be limitations to frame size and write speeds because of the smaller pixel count of the sensor and slower CF card slot.
I had built some snapshot builds for the 40D, 50D, and 5D3, which I have available here:
https://bitbucket.org/rufustfirefly/magic-lantern/downloads
The only issue I still have is that I haven't figured out how to modify the stock FIR file to allow loading Magic Lantern on the 40D, and the instructions on the wiki seem to be a little out-of-date.
Have same issue in 5X. The CANON image (in 5x mode) is always at the bottom right hand side of the 3x composition.
Quote from: 1% on August 28, 2013, 04:56:09 PM
ETTR has settings like set lowest shutter from main dial... auto expo has to be set up too... my lens can't do f1.8.
oh okay i found that setting for minimum shutter
i set it to 1/130 (1/125) so its cool now
not freaking me with 1/15 anymore
however didnt found how to put ISO there
its coming always on 1600 iso
the auto expo is so complicated
couldnt solve it out
so here is another example i made with new shutter speed
the advantage of this function is hilarious and good
but its need some skills to master it
(http://s013.radikal.ru/i324/1308/e2/c4f6c7d52b4e.jpg)
(http://s019.radikal.ru/i617/1308/83/077a9baaae60.jpg)
Quote from: Monti on August 28, 2013, 09:59:32 PM
its coming always on 1600 iso
Try going outside ;)
Quote from: 1% on August 28, 2013, 06:20:00 AM
I mean take AF off of 1/2 shutter. On 50D you can set it to the AF on button.
Awesome! Tyvm
Quote from: dogmydog on August 28, 2013, 10:08:50 PM
Awesome! Tyvm
didnt get it
does 50d autofocus in live view?
Quote from: a1ex on August 28, 2013, 10:05:35 PM
Try going outside ;)
the thing is
i try to shoot on 3200 iso
and ETTR brings it to 1600 iso
so not quite sure that the low light is the issue...
That's because you gain nothing by going to ISO 3200.
Quote from: a1ex on August 28, 2013, 11:10:49 PM
That's because you gain nothing by going to ISO 3200.
yeah maybe...
anyway i have to play more with this things
and its really need skills
this is something more difficult than what normal photographers get used to
I ended up buying a GH1 recently, but im thinking the 50d would be better in video, here are my reasons apart from the 14bit raw and my question at the end.
1. The GH1 has a smaller sensor, in effect a crop size when using say a 50mm 1.8, compared to the same lens which is great on aps-c size sensor.
2. I'm having to buy a smaller focal length lens with wider aperture to get effective video on the GH1.
Now my question, if anyone could be kind enough to help me out. Could I use the 50d in 1:1 cropped 1920x1080 recording and use a small focal length lens, say 28mm or even a 20mm on it, to increase the FOV of the cropped image to something comparable to the 50d's full sensor recording on a 50mm lens ???
hope that makes sense, any help would be GREATLY appreciated.
Quote from: oc_masta on August 29, 2013, 12:43:30 AM
I ended up buying a GH1 recently, but im thinking the 50d would be better in video, here are my reasons apart from the 14bit raw and my question at the end.
1. The GH1 has a smaller sensor, in effect a crop size when using say a 50mm 1.8, compared to the same lens which is great on aps-c size sensor.
2. I'm having to buy a smaller focal length lens with wider aperture to get effective video on the GH1.
Now my question, if anyone could be kind enough to help me out. Could I use the 50d in 1:1 cropped 1920x1080 recording and use a small focal length lens, say 28mm or even a 20mm on it, to increase the FOV of the cropped image to something comparable to the 50d's full sensor recording on a 50mm lens ???
hope that makes sense, any help would be GREATLY appreciated.
Yes, but you'll need something like a 12mm focal length to get 50mm full-frame equivalent in 1:1
Basically, multiply your lens focal length x4 and you'll be 'roughly' correct when the APS-C and raw crop factors are taken into account
Quote from: araucaria on August 28, 2013, 11:59:44 PM
Not maybe, it's actually a fact.
if you mean that analog ISO on canon 50d is 200-1250 and the rest is digital amplified
then we talking about different things...
i will test that thing morning outdoors and share results
until then no point to decide whether it is this or that...
Quote from: Andy600 on August 29, 2013, 12:48:20 AM
Yes, but you'll need something like a 12mm focal length to get 50mm full-frame equivalent in 1:1
Basically, multiply your lens focal length x4 and you'll be 'roughly' correct when the APS-C and raw crop factors are taken into account
Makes me wonder why most people seem to be neglecting the full hd crop mode on here?
Is there a reason why most people are opting to record with the lower resolution, aliasing and moire filled full sensor mode?
Quote from: oc_masta on August 29, 2013, 12:56:40 AM
Makes me wonder why most people seem to be neglecting the full hd crop mode on here?
Is there a reason why most people are opting to record with the lower resolution, aliasing and moire filled full sensor mode?
yeah i covered that few pages ago
there is huge advantage in crop x10 mode on Nikon 70-300 mm VR ED lens on canon 50d raw full hd video
that is equivalent of 3000 mm lens on full frame camera
that is more than anything exist
great for sports and wildlife and candid shoots far subjects
however there is no VR working
so probably if you use high end canon telephoto lens with VR would make even more sense
Quote from: Andy600 on August 29, 2013, 12:48:20 AM
Yes, but you'll need something like a 12mm focal length to get 50mm full-frame equivalent in 1:1
Basically, multiply your lens focal length x4 and you'll be 'roughly' correct when the APS-C and raw crop factors are taken into account
and thats an idea Andy600!
so 18-35 f1.8 sigma lens comes into the game
first part 18 mm it is going to be 28 mm f2.8 on normal and like 85 mm f 8 on crop x5 mode 200 mm f 16 x10 mode
double it with 35 mm gives you 50 mm f2.8 on normal and 180 mm f 8 on crop x 5 and 400 mm f 16 x10 mode
the second one is more narrow depth of field like twice than first one
coz focal length increase and the f stop remains
@oc_masta
important aspect is depth of field must be narrow for filmic scenes
i suggest also Rokinon (Samyang) fish eye 8 mm f3.5 lens which is around 40 mm and 80 mm on crop x5 and x10
but depth of field really goes off probably...
how you going to manage it with super wide angle lens and slow apperture in crop mode?
Quote from: Monti on August 29, 2013, 12:59:09 AM
yeah i covered that few pages ago
there is huge advantage in crop x10 mode on Nikon 70-300 mm VR ED lens on canon 50d raw full hd video
that is equivalent of 3000 mm lens on full frame camera
that is more than anything exist
great for sports and wildlife and candid shoots far subjects
however there is no VR working
so probably if you use high end canon telephoto lens with VR would make even more sense
I actually meant in the opposite sense.
It worried me the zoom was too much in crop mode but that can be worked around grabbing a smaller focal length lens anyway. I see no reason to shoot with the lower resolution full sensor mode? everyone want higher res in full sensor, but its crazy?!? moire aliasing and all that when we can have a perfect picture in crop with the correct lens to make up for the zoom?
Quote from: Monti on August 29, 2013, 01:10:07 AM
@oc_masta
important aspect is depth of field must be narrow for filmic scenes
i suggest also Rokinon (Samyang) fish eye 8 mm f3.5 lens which is around 40 mm and 80 mm on crop x5 and x10
but depth of field really goes off probably...
how you going to manage it with super wide angle lens and slow apperture in crop mode?
wouldn't a very small focal length lens create a very shallow depth of field?
Quote from: oc_masta on August 29, 2013, 01:12:18 AM
wouldn't a very small focal length lens create a very shallow depth of field?
No, the opposite.
BTW, DOF in crop mode is exactly the same as it would be in non-crop when talking about raw video.
Quote from: Andy600 on August 29, 2013, 01:18:04 AM
No, the opposite.
BTW, DOF in crop mode is exactly the same as it would be in non-crop when talking about raw video.
yeah well how does that been worked out?
to my understanding
crop mode multiplies the f stop value for depth of field
Does the DOF change when you zoom in on a cr2?
Quote from: 1% on August 29, 2013, 01:35:03 AM
Does the DOF change when you zoom in on a cr2?
yeah well let me think about it...
we talking about framing the scene isnt it?
so lets say i shoot a person head
my depth of field is like from his nose to his ear
that is shallow one.
now if we zoom in in cr2 we get what?
head is choped half and we need to reframe it
when we reframe it what happens?
depth of field is not narrow anymore
now my depth of field is whole head and much more
not as shallow as it was when i frame just nose and ear
why is that?
because crop mode means 50 mm becomes 250 mm
now i have to shoot from distance not 4 meters but like 20 meters to get kinda same framing
and 20 meters gives me what? huge fat bulky depth of field that i can even bring a bus into it
p.s. of coz u dont get head shot on 50 mm from 4 meters
but u got the point
@Monti - It's a tricky concept to get your head around but DOF does not change when you punch between crop and non-crop because there is no optical difference between the two modes other than framing. It is still seeing the same pixels but in normal mode 2/3rds are thrown away through line-skipping with the remaining pixels brought back together. Of course, if you reposition and refocus you will have affected DOF because you moved further away from the subject. At least, that's how I understand things but it fries my brain to think about it.
Quote from: Andy600 on August 29, 2013, 02:09:28 AM
@Monti - It's a tricky concept to get your head around but DOF does not change when you punch between crop and non-crop because there is no optical difference between the two modes other than framing. It is still seeing the same pixels but in normal mode 2/3rds are thrown away through line-skipping with the remaining pixels brought back together. Of course, if you reposition and refocus you will have affected DOF because you moved further away from the subject. At least, that's how I understand things but it fries my brain to think about it.
yeah i am right
and you got it when you said moved further away from the subject
and that is what im talking about
that is depth of field actually
what about the lens parameters - of coz they remain the same
but to fit into crop frame you have to move further
and this is how your depth of field multiplied to eternity
and you forgetting about narrow DOP forever
What about a wider lens than 50mm? Already a problem with a 1.6 factor so you pretty much need a superwide for this type of thing.
Quote from: 1% on August 29, 2013, 02:19:06 AM
What about a wider lens than 50mm? Already a problem with a 1.6 factor so you pretty much need a superwide for this type of thing.
yeah i covered this on previous page
actually to have wide focal length doesnt help you to have narrow depth of field
coz for long focal length you need kinda any f stop value and you have good thing (beside distance)
and for wide angle - really imposible to have narrow depth of field
coz if u wana know how does this counts
lets say 50 f1.8
divide that u get around 27.5 value depth of field
now we take 18 f1.8 you get 10 value
it means not narrow at all
more the value - shallower is DOP
ps thats why i used the opposite way
and made use of this thing
by doing a super tele zoom shooting on 300 mm f5.6
guess what? the value of it is around 55
and thats even better than 50 1.8 like twice
TBH the only time you need worry about this is if you shoot with a full frame camera and an APS-C and want identical shots. I never worry about it. It's too much of a headfuck. I can get very shallow DOF on an F1.4 on the 50D that's too shallow to use and impossible to keep something moving in focus.
Quote from: Andy600 on August 29, 2013, 02:09:28 AM
@Monti - It's a tricky concept to get your head around but DOF does not change when you punch between crop and non-crop because there is no optical difference between the two modes other than framing. It is still seeing the same pixels but in normal mode 2/3rds are thrown away through line-skipping with the remaining pixels brought back together. Of course, if you reposition and refocus you will have affected DOF because you moved further away from the subject. At least, that's how I understand things but it fries my brain to think about it.
I'm with the green cat on this one. You can't compare a crop image to the original non crop for dof because it will be the same. You need to compare the crop to a reframed full sensor image which matches the crop. To get the full sensor to match the crop you would need to get closer, use a longer lens or a combination. Both of these factors reduce dof quite a bit.
Quote from: Andy600 on August 29, 2013, 02:26:57 AM
TBH the only time you need worry about this is if you shoot with a full frame camera and an APS-C and want identical shots. I never worry about it. It's too much of a headfuck. I can get very shallow DOF on an F1.4 on the 50D that's too shallow to use and impossible to keep something moving in focus.
if you worry about difference in depth of field between full frame and APS-C crop cameras (like canon 50d)
this is not the case
coz there you got what?
canon 5d mark iii 50 mm gives true f1.8
canon 50d 50 mm in reality gives f2.8
hey thats not bad at all!
we dont worry of it.
with 50 mm f 1.4 even better - f 2 on canon 50 d
but when you do like 5x and 10x zoom this is whole different world
now your 50 mm f1.8 is freaking f8 on x5 and f16 on x10
i will make this shots tomorrow and show you guys a real example with Nikon 50 1.8
which is known as sharpest lens on DSLR market
Maybe according to Ken Rockwell it is ;D
...actually, I love my Nikon 50s.
@1% - are you gonna take a look at the .mlv code anytime soon? I've had a play with g3gg0's module and it's slower on the 50D but having the metadata is nice.
BTW
i want to ask developers of magic lantern
would you do the same thing fro Nikon d7000 on raw video?
there is one guy who hacked it for raw video
but just like 1.5 fps for 10 seconds only
i think its gona be too long for him to do it alone
http://nikonrumors.com/2013/07/06/nikon-d7000-hacked-to-record-liveview-raw-video.aspx/
i ask because i have canon 50d and nikon d7000
and of coz the SD card is limited to whatever speed it is 20 mb or 40 mb
but the image quality i think it can be better than canons
You are obviously not going to be able to take the same shot in crop mode as in full sensor mode with a 50 1.4, you would need a 20mm f0.56 to have the same image, I think these f stop comparsions work perfectly fine from an photograpic standpoint.
The d7000 thing is not going to happen, there is just 1 guy looking into it and they are still figuring out basic stuff on the firmwares, don't even think of being able to use the two card slots to give 40mb/s. The test he made was writing around 20mb/s so... And it was just junk, no actual images.
Quote@1% - are you gonna take a look at the .mlv code anytime soon? I've had a play with g3gg0's module and it's slower on the 50D but having the metadata is nice.
How much slower? I was waiting for it to hit the main tree at some point.. even HDMI plugged in makes a difference.
Quote from: 1% on August 29, 2013, 03:15:34 AM
How much slower? I was waiting for it to hit the main tree at some point.. even HDMI plugged in makes a difference.
I estimate between 15-20% slower than raw_rec with Tragic Lantern but he built it for the 5D3 afaik so maybe there are some tweaks that are needed for the 50D!?!. The code is in his repo. If you do decide to take a look can you maybe rename it so we can have both loaded for testing? There is a new build of mlv2dng too.
Does HDMI have a negative impact on performance?
Quote from: 1% on August 29, 2013, 03:15:34 AM
How much slower? I was waiting for it to hit the main tree at some point.. even HDMI plugged in makes a difference.
oh btw what about HDMI tweaks for canon 50d raw video on tragic lantern side?
id rather record on external recordre like atomos ninja 2
than trying to fit in compact flash card footage that takes 4 gb per minute
Quote from: Monti on August 29, 2013, 03:28:09 AM
oh btw what about HDMI tweaks for canon 50d raw video on tragic lantern side?
id rather record on external recordre like atomos ninja 2
than trying to fit in compact flash card footage that takes 4 gb per minute
We all would but no can do! HDMI is 8bit and nowhere near the bandwidth needed for raw video.
Quote from: araucaria on August 29, 2013, 03:11:53 AM
The d7000 thing is not going to happen, there is just 1 guy looking into it and they are still figuring out basic stuff on the firmwares, don't even think of being able to use the two card slots to give 40mb/s. The test he made was writing around 20mb/s so... And it was just junk, no actual images.
yeah thats what im saying
i just didnt want to wait for him to do that nikon d7000 raw video
and went to buy myself a canon 50d to follow up with magic lantern guys for raw video lately
that guy will never make it alone
unless people from magic lantern would go for it and sort that out
20mb/sec isnt too bad
canon 600d is doing raw video on 20mb/sec on sd cards as well
Quote from: Andy600 on August 29, 2013, 03:30:38 AM
We all would but no can do! HDMI is 8bit and nowhere near the bandwidth needed for raw video.
yeah then...
if i wanted 8 bit prores uncompressed HDMI output
i would buy Nikon d800 or Nikon d600
but i went to Canon 50d
coz raw video is raw video ;)
its hollywood standart.
(ARRIRAW: 2880 x 1620, uncompressed 12 bit log without white balance or exposure index processing applied. )
http://www.arri.com/camera/digital_cameras/cameras/camera_details.html?product=8&subsection=technical_data&cHash=177d18e5da12e11481110e620f560c80
but in reality the difference here is
14 stops of dynamic range
it means dual iso in video
like the one on 5d mark 3
also the resulution is like 4 times higher means bitrate 300 mb/sec
and external hard disk for 1 tb or more
other than that - canon 50d is pretty much a hollywood camera
again - it happen thanks to magic lantern team
generally to understand what is raw video dynamic range or HDR video
for those who dont know
is when you see lots of white and black stuff on same screen
and colors are also very different filling up this space
on anything else than raw video you cant go that far
coz raw contains wide range of data between under and over exposed data from sensor
and now some fun for developers
the Matrix remake hehe
Well I started testing my cam and the komputerbay 32gb CF card got corrupted. It's on its way back for a refund..
I wasn't expecting these cards to be so fragile.. What card readers do you use?
Quote from: Monti on August 29, 2013, 01:10:07 AM
and thats an idea Andy600!
so 18-35 f1.8 sigma lens comes into the game
first part 18 mm it is going to be 28 mm f2.8 on normal and like 85 mm f 8 on crop x5 mode 200 mm f 16 x10 mode
double it with 35 mm gives you 50 mm f2.8 on normal and 180 mm f 8 on crop x 5 and 400 mm f 16 x10 mode
Wrong. Totally. The f-number doesn't change at all with crop factor!
Quote from: Monti on August 29, 2013, 01:42:18 AM
yeah well let me think about it...
we talking about framing the scene isnt it?
so lets say i shoot a person head
my depth of field is like from his nose to his ear
that is shallow one.
now if we zoom in in cr2 we get what?
head is choped half and we need to reframe it
when we reframe it what happens?
depth of field is not narrow anymore
now my depth of field is whole head and much more
not as shallow as it was when i frame just nose and ear
why is that?
because crop mode means 50 mm becomes 250 mm
now i have to shoot from distance not 4 meters but like 20 meters to get kinda same framing
and 20 meters gives me what? huge fat bulky depth of field that i can even bring a bus into it
p.s. of coz u dont get head shot on 50 mm from 4 meters
but u got the point
Totally wrong again. If you frame the same size object, the dof is the same at all focal lengths. http://www.cambridgeincolour.com/tutorials/depth-of-field.htm
That's only true if the sensor size stays the same.
Quote from: dlrpgmsvc on August 29, 2013, 10:21:33 AM
Totally wrong again. If you frame the same size object, the dof is the same at all focal lengths. http://www.cambridgeincolour.com/tutorials/depth-of-field.htm
Way off topic at the mo, but this explains it quite well,
"Cropping an image and enlarging to the same size final image as an uncropped image taken under the same conditions is equivalent to using a smaller format under the same conditions, so the cropped image has less DOF. (Stroebel 1976, 134, 136–37)".http://en.wikipedia.org/wiki/Depth_of_field#Factors_affecting_depth_of_field
Since I like a shallow dof myself I prefer non crop mode. But sometimes the moire / aliasing effects are a bit annoying... On the other hand: I am very curious to see some 1920 /1080 crop mode clips with a very wide lens (8mm - 10mm). Anyone here got a wide lens to shoot some footage?
I have a 12mm and focusing is hard in sunlight (the dof is very broad at 12mm f4) so even in when you zoom in 10x youre never sure unless you have a magnification lens (which I don't). Usually when you focus a lens you will see the "pop" of getting into focus, but when you are at 12mm you need very good viewing conditions to see that. Maybe with an autofocus lens this is not such an issue, mine is a nikon 12-24mm fit onto an adapater. I get 48mm equivalent with that, the equivalent f stop (don't read it if you don't like it) is f16 so everything is in focus or slightly in focus unless you are focusing to infinity and have something 50cm away.
Quote from: dlrpgmsvc on August 29, 2013, 10:21:33 AM
Totally wrong again. If you frame the same size object, the dof is the same at all focal lengths. http://www.cambridgeincolour.com/tutorials/depth-of-field.htm
dont mess with this up dude
yiou just confuse yourself
im making real test to show the thing
"Circle of confusion" - yep! that describes this subject nicely ;D
Quote from: robertgl on August 29, 2013, 05:24:50 AM
Well I started testing my cam and the komputerbay 32gb CF card got corrupted. It's on its way back for a refund..
I wasn't expecting these cards to be so fragile.. What card readers do you use?
I'm still using the same card for awhile now. Using Transcend USB 3.0 Card Reader (TS-RDF8K) Moves my ~30GB footage from Card to SSD over USB 3.0 in about 4 minutes tops.
http://www.amazon.com/gp/product/B0056TYRMW/ref=oh_details_o01_s00_i04?ie=UTF8&psc=1 (http://www.amazon.com/gp/product/B0056TYRMW/ref=oh_details_o01_s00_i04?ie=UTF8&psc=1)
Sidenote; Loving DualISO http://flic.kr/p/fE6KrJ (http://flic.kr/p/fE6KrJ)
And Auto Exposure http://flic.kr/p/fEjWBG (http://flic.kr/p/fEjWBG)
Quote from: Andy600 on August 29, 2013, 02:30:44 PM
"Circle of confusion" - yep! that describes this subject nicely ;D
okay i done test
results as i expected
will post soon
Quote from: dsManning on August 29, 2013, 02:42:01 PM
And Auto Exposure http://flic.kr/p/fEjWBG (http://flic.kr/p/fEjWBG)
teach me auto expo plz
ps seems like those komputerbay cards crashing like wallnuts
maybe i should better stick with my lexar x1000 cards
okay here is depth of field test on crop modes raw video with canon 50d
first normal mode then x5 and then x10
i dont know what happen why the framing isnt same
also no VR so shaky video
watch in HD or Full HD resolution
i know this test sucks
but to me i can see what is going about
later i make photo test that is more obvious
that on crop 5x and crop 10x the depth of field becomes wide like table
Hey man wow great test so usefull really.. all that talk about composition for this haha! seems like you where drunk and on acids when you shot this man.
Btw I don't know where you found that komputarbay cards were bad, I shot 400gb+ on two 32gb without a single issue. As for the issue a few pages back, the poster probably could have recovered his card. There is a lot that can happen and corrupt a card/flash memory disck but it can be fixed most of the times with the rigth partitionning/formatting tools.
Quote from: bzhwindtalker on August 29, 2013, 05:59:04 PM
Hey man wow great test so usefull really.. all that talk about composition for this haha! seems like you where drunk and on acids when you shot this man.
Btw I don't know where you found that komputarbay cards were bad, I shot 400gb+ on two 32gb without a single issue. As for the issue a few pages back, the poster probably could have recovered his card. There is a lot that can happen and corrupt a card/flash memory disck but it can be fixed most of the times with the rigth partitionning/formatting tools.
talking about compositions
i just checked it and it looks alright
(the rule of thirds is on the place and other rules of composition too)
there is camera shake coz i didnt use tripod and its manual nikon focus with no image stabilization prime lens 50 mm f1.8 - hard to pull focus with one hand and hold camera with other hand if u know what i mean
especially when this crop mode makes it 250 mm and 500 mm with no stabilization
that is another reason why you dont want to use crop mode while recording motion picture
ps i dont mind crashed and fixed komputerbay cards
i just dont want my footage to be lost during this crashes
@Monti - A little tip. If you don't have a tripod, rig or stabilizer put the camera on a cushion and put that on something solid. This will reduce movement and still allow you some degree of tilt and pan. For handheld you can also use your camera strap - by putting it around your neck or body and pulling it taught. It won't eliminate movement but will reduce shake a little.
Quote from: Andy600 on August 29, 2013, 06:42:34 PM
@Monti - A little tip. If you don't have a tripod, rig or stabilizer put the camera on a cushion and put that on something solid. This will reduce movement and still allow you some degree of tilt and pan. For handheld you can also use your camera strap - by putting it around your neck or body and pulling it taught. It won't eliminate movement but will reduce shake a little.
yeah nice tips
but if i want smooth paning i have a better solution
i just dont use it for crap video tests and keep for serious work)
also i like my shaky style it fits to war songs like in war movies of 1945 year
ps and i have all kind of rigs and stuff too
@Monti : your test is not correct. You are progressively going away from subject (the Matchbox) by lens or by crop factor or by 50D phisically (not important). You have to test at the same framing the normal, the 5x and the 10x, so that the Matchbox occupy the same area on the sensor. It is obvious that more you go away from Matchbox and the more you have DOF. Can you redo the test in this way ? Only in this way we can judge
Quote from: dlrpgmsvc on August 29, 2013, 06:51:31 PM
@Monti : your test is not correct. You are progressively going away from subject (the Matchbox) by lens or by 50D phisically (not important). You have to test at the same framing the normal, the 5x and the 10x, so that the Matchbox occupy the same area on the sensor. It is obvious that more you go away from Matchbox and the more you have DOF. Can you redo the test in this way ? Only in this way we can judge
yeah i noticed that and im going to redo a matchbox in frame test on photo mode another time
but what you can not see then is scale of depth of field magnification
in here its kinda shows that the difference noticeable on wider area or so...
coz i started with matchbox and then realised that next DOP is just too wide for that frame
so need to make framing wider to get other details in frame
simple matchbox wont show much here and there
so i better start from table test from beginning
Hey Monti
A lot of noice on this forum
May you take a brake for a while or take from courses?
muchas gracias
Quote from: rawmania on August 29, 2013, 07:13:39 PM
Hey Monti
A lot of noice on this forum
May you take a brake for a while or take from courses?
muchas gracias
no way
im excited now
maybe when i get bored then i leave
but thanks for your compliment to say that im most active poster here
i hear this on every forum and community i pass by during my life
i like to bring something into somewhere
Quote from: Monti on August 29, 2013, 03:43:46 PM
teach me auto expo plz
ps seems like those komputerbay cards crashing like wallnuts
maybe i should better stick with my lexar x1000 cards
okay here is depth of field test on crop modes raw video with canon 50d
first normal mode then x5 and then x10
i dont know what happen why the framing isnt same
also no VR so shaky video
watch in HD or Full HD resolution
i know this test sucks
but to me i can see what is going about
later i make photo test that is more obvious
that on crop 5x and crop 10x the depth of field becomes wide like table
The DOF changes because you are changing your camera to subject distance!
Seriously, monti or silkway or whatever you prefer to be called, your comments on here are making me think you're just a troll.
This used to be a helpful and polite forum but lately it's turned into dvxuser, such a shame.
Quote from: rockfallfilms on August 29, 2013, 07:49:59 PM
The DOF changes because you are changing your camera to subject distance!
Seriously, monti or silkway or whatever you prefer to be called, your comments on here are making me think you're just a troll.
This used to be a helpful and polite forum but lately it's turned into dvxuser, such a shame.
seriously i didnt intend to move from subject
it happened accidently
but even so you can see the difference isnt it?
just its kind of test for intelligence
coz complaining about this is rude
anyway tomorrow i will make another test
maybe problem is that magic lantern doesnt give you exact framing preview in crop mode?
or you know what? im going to make one photo test right now. just give me couple of minutes
updated:
okay test is done
and its going to blow your minds
im going to post it in a second
apdated:
okay here is the test:
(http://i036.radikal.ru/1308/87/53761570200d.jpg)
Click here for full size review:
http://i036.radikal.ru/1308/87/53761570200d.jpg (http://i036.radikal.ru/1308/87/53761570200d.jpg)
for those who still in doubt
here is x10 crop
(http://s017.radikal.ru/i419/1308/79/e02f60a43fa3.jpg)
the 2 crop images are blurry because of camera shake on long focal distance 250-500 mm with no stabilization
OKAY THE DISCUSSION IS OVER
I WAS RIGHT
EVERYONE CORRECT YOUR BELIEFS ABOUT DEPTH OF FIELD IN CROP MODE =)
(This is real test on canon 50d)
I need a recommendation on the best cheap ultra wide angle (14mm or less) lens to shoot in crop mode . . . under $200 would be nice.
Anybody?
Quote from: menoc on August 29, 2013, 09:01:39 PM
I need a recommendation on the best cheap ultra wide angle.
Cheap means at least $400, when talking about wide angle.
For example Sigma AF 10-20mm f/4-5.6. I'm using it a lot. Nice glass.
Quote from: menoc on August 29, 2013, 09:01:39 PM
I need a recommendation on the best cheap ultra wide angle (14mm or less) lens to shoot in crop mode . . . under $200 would be nice.
Anybody?
this is what u are looking for 249$ Rokinon 8 mm f3.5
http://www.bhphotovideo.com/c/product/769428-REG/Rokinon_FE8M_C_8mm_Ultra_Wide_Angle.html
Quote from: Monti on August 29, 2013, 09:15:20 PM
this is what u are looking for 249$ Rokinon 8 mm f3.5
http://www.bhphotovideo.com/c/product/769428-REG/Rokinon_FE8M_C_8mm_Ultra_Wide_Angle.html
Interesting . . . but I'd like a non-fish eye lens though. How difficult is it to defish video and what would be the results?
Quote from: Rewind on August 29, 2013, 09:06:37 PM
Cheap means at least $400, when talking about wide angle.
For example Sigma AF 10-20mm f/4-5.6. I'm using it a lot. Nice glass.
Try to find a good secondhand Tokina 11-16mm.
@Monti - The 8mm is a fisheye lens and will have barrel distortion
Quote from: Rewind on August 29, 2013, 09:06:37 PM
Cheap means at least $400, when talking about wide angle.
For example Sigma AF 10-20mm f/4-5.6. I'm using it a lot. Nice glass.
Well . . . there's got to be a hidden gem out there on ebay that is around $200. . .
Quote from: menoc on August 29, 2013, 09:25:26 PM
Interesting . . . but I'd like a non-fish eye lens though. How difficult is it to defish video and what would be the results?
first of all when u crop in the lens
you already defish it pretty much
secondly if u dont shoot something very close
then u dont have this perspective distortion that all wide angles giving
like pinnocio long nose etc
so u dont have to do anything about it pretty much
Quote from: menoc on August 29, 2013, 09:27:26 PM
Well . . . there's got to be a hidden gem out there on ebay that is around $200. . .
There might be something vintage. I'll have a think ;)
Quote from: Monti on August 29, 2013, 09:28:33 PM
first of all when u crop in the lens
you already defish it pretty much
secondly if u dont shoot something very close
then u dont have this perspective distortion that all wide angles giving
like pinnocio long nose etc
so u dont have to do anything about it pretty much
The 8mm distorts even in crop mode. I've tried it. The Tokina 11-16mm is also a much better lens.
of coz if u have like 600-700 buck u can get tokina
or get sigma for 400-450 buck
otherwise fisheye rokinon 8 mm is only choise for 249 buck
A Tokina for $400 is very much a possibility. The other option is to get an anamorphic. There are a few 2x for around that kind of money and it will give you a wider field of view with cool bokeh and flares. It's actually a much cooler option in my opinion ;)
Quote from: Monti on August 29, 2013, 09:28:33 PM
first of all when u crop in the lens
you already defish it pretty much
secondly if u dont shoot something very close
then u dont have this perspective distortion that all wide angles giving
like pinnocio long nose etc
so u dont have to do anything about it pretty much
I see what you're saying. There will still be some distortion around the edges . . . the price sounds right though.
Quote from: menoc on August 29, 2013, 09:45:10 PM
I see what you're saying. There will still be some distortion around the edges . . . the price sounds right though.
this is what you going to get on 8 mm rokinon
i love fisheye
im going to buy this one
coz it gives 180 degree view
and normal wide angles only like 110 degree
(http://s020.radikal.ru/i720/1308/80/85fded4dc084.jpg)
ps that little distortion u get on crop mode can easily be fixed in program
and for normal things i can use 18 mm nikon lens i have on crop it gives like 85 mm
18 mm is on any kit lenses. like 18-105 from nikon i have
but if u want to get such thing u can buy even cheaper versions like 18-55 mm
Quote from: Andy600 on August 29, 2013, 09:30:38 PM
The 8mm distorts even in crop mode. I've tried it. The Tokina 11-16mm is also a much better lens.
The Tokina looks good Andy. It's as low as $300ish used on Amazon.
@menoc - http://www.ebay.com/itm/Isco-Iscomorphot-16-2x-Anamorphic-Cinemascope-Lens-/200956832944?pt=Camera_Lenses&hash=item2ec9f5ecb0 right on the money and a seriously nice lens for video. You'll be able to shoot over 2.5k 16:9 with this. I would buy it myself if I could.
Pair it with a Helios 44M-2 or an old Nikon 50mm (as both flare) and you'll get pure Hollywood ;)
Quote from: Andy600 on August 29, 2013, 09:36:33 PM
A Tokina for $400 is very much a possibility. The other option is to get an anamorphic. There are a few 2x for around that kind of money and it will give you a wider field of view with cool bokeh and flares. It's actually a much cooler option in my opinion ;)
i want anamorphic lens for canon 50d raw video
do you know which ones are on sale?
i just have no idea about this thing
id like to buy one from amazon.co.uk or some shop
not familiar with ebay things
There are no solutions for crop mode in order to keep all the features we want (I made a simple compendium) :
[1] Wideangle lens : FOV enlarged (GOOD) - DOF very deep (BAD) - QUALITY good (GOOD) - Record on narrow spaces (GOOD) - Must defish for large FOV losing resolution (BAD)
[2] Wideangle add-on : FOV enlarged (GOOD) - DOF very deep (BAD) - QUALITY worse (BAD) - Record on narrow spaces (GOOD) - Must defish for large FOV losing resolution (BAD)
[3] Normal lens + operator step back to take more FOV : FOV enlarged (GOOD) - DOF very deep (BAD) - QUALITY good (GOOD) - Cannot record on narrow spaces (BAD)
[4] DOF adapter (projection method + macro mode) : FOV enlarged (GOOD) - DOF shallow (GOOD) - QUALITY horrible (BAD) - Record on narrow spaces (GOOD)
@dlrpgmsvc
we can actually record in crop mode with shallow depth of field
but it needs huge distance and telephoto kind lens
I made many in-deep analisys on anamorphic lens: they don't worth the money, at the end of the story. The vertical resolution gain is not worth for our hobby: a wideangle corrected in post is much more viable and with very good results. Anamorphic has so many limitations, also for focus distance limitations, bulkyness, main lens coupling and so on
Quote from: Monti on August 29, 2013, 09:54:06 PM
@dlrpgmsvc
we can actually record in crop mode with shallow depth of field
but it needs huge distance and telephoto kind lens
True, so not viable for normal cinema use (big and bulky tripods, optical stabilizers, and great spaces, not viable for indoor use, and so on)
Quote from: dlrpgmsvc on August 29, 2013, 09:59:13 PM
True, so not viable for normal cinema use (big and bulky tripods, optical stabilizers, and great spaces, not viable for indoor use, and so on)
yeah but good for spy work)
also i see no problem with shooting on 1582xwhatever resolution over 1920xwhatever
its just 20% gain
and 1582 is good enough
if want more why dont go for 4K at once?
Quote from: Andy600 on August 29, 2013, 09:47:00 PM
@menoc - http://www.ebay.com/itm/Isco-Iscomorphot-16-2x-Anamorphic-Cinemascope-Lens-/200956832944?pt=Camera_Lenses&hash=item2ec9f5ecb0 right on the money and a seriously nice lens for video. You'll be able to shoot over 2.5k 16:9 with this. I would buy it myself if I could.
Pair it with a Helios 44M-2 or an old Nikon 50mm (as both flare) and you'll get pure Hollywood ;)
Yeah . . . now I'm feeling like thrashing my 401k . . lol
Quote from: rawmania on August 29, 2013, 07:13:39 PM
Hey Monti
A lot of noice on this forum
May you take a brake for a while or take from courses?
muchas gracias
+1
Quote from: Andy600 on August 29, 2013, 09:47:00 PM
@menoc - http://www.ebay.com/itm/Isco-Iscomorphot-16-2x-Anamorphic-Cinemascope-Lens-/200956832944?pt=Camera_Lenses&hash=item2ec9f5ecb0 right on the money and a seriously nice lens for video. You'll be able to shoot over 2.5k 16:9 with this. I would buy it myself if I could.
Pair it with a Helios 44M-2 or an old Nikon 50mm (as both flare) and you'll get pure Hollywood ;)
yeah if anyone wana sell such thing i would like to buy)
updated:
okay dudes
jokes away
i made a serious video test raw canon 50d without camera shake
(i used my special anti shake tool this time)
u going to be suprised to know what is it in few minutes... or hour
Quote from: Andy600 on August 29, 2013, 09:47:00 PM
@menoc - http://www.ebay.com/itm/Isco-Iscomorphot-16-2x-Anamorphic-Cinemascope-Lens-/200956832944?pt=Camera_Lenses&hash=item2ec9f5ecb0 right on the money and a seriously nice lens for video. You'll be able to shoot over 2.5k 16:9 with this. I would buy it myself if I could.
Pair it with a Helios 44M-2 or an old Nikon 50mm (as both flare) and you'll get pure Hollywood ;)
Do you think we will ever be able to shoot 2.5k in camera?
Quote from: Lukas1221 on August 29, 2013, 10:50:31 PM
Do you think we will ever be able to shoot 2.5k in camera?
Not on the 50D
Hey guys UWA lenses that aren't fisheye do exist. The Sigma 8-16mm f4.5-5.6 is a rectilinear wide angle. It's also a good option for Crop Modes. Better than the Samyang 8mm Fisheye IMO.
There is also a Sigma 10-20mm f3.5 which is another nice option.
I know this will seem like a dumb question but is there a way to LOCK the Shutter at 1/48 on the 50D?
Quote from: 50Deezil on August 29, 2013, 11:09:26 PM
I know this will seem like a dumb question but is there a way to LOCK the Shutter at 1/48 on the 50D?
MENU Expo> Exp Override
Quote from: 50Deezil on August 29, 2013, 10:58:39 PM
Hey guys UWA lenses that aren't fisheye do exist. The Sigma 8-16mm f4.5-5.6 is a rectilinear wide angle. It's also a good option for Crop Modes. Better than the Samyang 8mm Fisheye IMO.
There is also a Sigma 10-20mm f3.5 which is another nice option.
relax i made a test on it
coming in few time
updated:
okay here it is
18 mm f3.5 from Nikon 18-105 lens on crop mode canon 50d gives like 85 mm f16
and this video is shot from distance of 50 cm only.
also if you see focus is able to move here and there
its possible because the distance is small for subject
for simulations of shallow depth of field
that is ISO 3200
anybody knows why video is kinda choppy?
something wrong with frame skipping or shutterspeed or FPS override or what?
Hi all, I recently was shooting on BMCC and decided to make comparison of BMCC vs 50D.
So I decided to evaluate the usable DR of both cameras.
This is not a scientific test -- just practical approach.
I was shooting both scenes in a ETTR way (without ETTR module), so that the whites are nearly overexposed.
Then I tried to push the shadows and see how much that can go until you have unacceptable noise (purely in my opinion)
I'm pretty sure that someone can make more sense from these tests, so welcome!
BMCC was shot at ISO 800.
I decided to shoot 50D at ISO 400. On the one hand, I wanted their ISOs somehow to match. On the other hand, ISO 800 of 50D would be too unfair to 50D, being a no low-light king.
The same 17-50 2.8 lens was used.
(http://i39.tinypic.com/1zn2wba.jpg)
50D. Shot ETTR. ISO 400. Pushed shadows. No sharpening or noise reduction. ACR 6.0
(http://i41.tinypic.com/jb7676.jpg)
BMCC. Shot ETTR. ISO 800. Pushed shadows. No sharpening or noise reduction. ACR 6.0
(http://i43.tinypic.com/302789l.jpg)
100% Crop: BMCC and 50D - The darkest shadows in the scene and my personal view of acceptable noise.
CONCLUSION: Based on the eyedropper tool info in the shadows I estimate that BMCC is 1 stop wider in its Dynamic Range.
As I said, this is a brief non-scientific test. Don't shoot me based on this. Any reasonable comments are welcome.
And yes, the original RAW files are found here: https://copy.com/oG6C31ghjeJ0 (https://copy.com/oG6C31ghjeJ0)
PS Monti, please relax and don't respond to this. You may create your own thread somewhere in the forum and post, post, post... 8)
Quote from: rommex on August 30, 2013, 12:53:57 AM
Hi all, I recently was shooting on BMCC and decided to make comparison of BMCC vs 50D.
how come u make test on ISO 400 of canon 50d?
watch video above i made on ISO 3200
and thats even without ETTR stuff
but thanks for BMCC raw file
i made it look like it should be
here is 100% crop
(http://s006.radikal.ru/i213/1308/1c/eef8c5ef780b.jpg)
and here is full size picture enjoy
http://s54.radikal.ru/i143/1308/8d/a8e845d0e293.jpg (http://s54.radikal.ru/i143/1308/8d/a8e845d0e293.jpg)
(http://s54.radikal.ru/i143/1308/8d/a8e845d0e293.jpg)
ps
dont make things look ugly people
this cameras are pushing maximum to look good in extreme conditions
whats the point to look for noise on ISO 400-800?
better show how u handle it on ISO 3200
Quote from: Monti on August 30, 2013, 01:04:29 AM
how come u make test on ISO 400 of canon 50d?
watch video above i made on ISO 3200
and thats even without ETTR stuff
I explained it in my post. Also note that usually DR is wider at lower ISOs.
And please stop this trolling. Obviously after all the forums and nicks that you've gone through, you've grown some hard forehead of yourself to ignore remarks to your meaningless posts.
I guess soon the time will come when we on the forum will have to address the moderator to keep this forum clean and acceptable for those who are hungry for 50D RAW info, rather than having to sift through someone's egotistic garbage...
Quote from: rommex on August 30, 2013, 01:17:39 AM
I explained it in my post. Also note that usually DR is wider at lower ISOs.
And please stop this trolling. Obviously after all the forums and nicks that you've gone through, you've grown some hard forehead of yourself to ignore remarks to your meaningless posts.
I guess soon the time will come when we on the forum will have to address the moderator to keep this forum clean and acceptable for those who are hungry for 50D RAW info, rather than having to sift through someone's egotistic garbage...
yeah just become professional
and then complain about my posts people)
Hey guys, got a quick question for yall
So recently I began optimizing my 50D for general shooting and took the advice from a poster upon being able to achieve focus easier using LV. He stated to use a combination of focus-peak and the zoom box alongside the digic setting "Cartoon Look" set to number "1". This made achieving focus super easy but recently the setting (though active) did not appear on my LV display regardless of whether or not I re-installed the latest version of tragic lantern 2.0 or disengaged and reengaged the digic setting. All of my other settings have remained the same and I am running a lexar 32gb x100 card.
So whats going on here?
Also I never got the chance to record while the cartoon look was applied, so is it applied to your recorded footage? if so I just assume you disengage the setting before shooting.
Thanks guys,
Any warnings in the menu? When something doesn't work, it usually prints why.
Quote from: rommex on August 30, 2013, 01:17:39 AM
I explained it in my post. Also note that usually DR is wider at lower ISOs.
And please stop this trolling. Obviously after all the forums and nicks that you've gone through, you've grown some hard forehead of yourself to ignore remarks to your meaningless posts.
I guess soon the time will come when we on the forum will have to address the moderator to keep this forum clean and acceptable for those who are hungry for 50D RAW info, rather than having to sift through someone's egotistic garbage...
+1 - Monti's comments are beyond tedious now.
Quote from: rommex on August 30, 2013, 12:53:57 AM
Hi all, I recently was shooting on BMCC and decided to make comparison of BMCC vs 50D.
So I decided to evaluate the usable DR of both cameras.
This is not a scientific test -- just practical approach.
I was shooting both scenes in a ETTR way (without ETTR module), so that the whites are mostly overexposed.
Then I tried to push the shadows and see how much that can go until you have unacceptable noise (purely in my opinion)
I'm pretty sure that someone can make more sense from these tests, so welcome!
BMCC was shot at ISO 800.
I decided to shoot 50D at ISO 400. On the one hand, I wanted their ISOs somehow to match. On the other hand, ISO 800 of 50D would be too unfair to 50D, being a no low-light king.
The same 17-50 2.8 lens was used.
CONCLUSION: Based on the eyedropper tool info in the shadows I estimate that BMCC is 1 stop wider in its Dynamic Range.
As I said, this is a brief non-scientific test. Don't shoot me based on this. Any reasonable comments are welcome.
And yes, the original RAW files are found here: https://copy.com/oG6C31ghjeJ0 (https://copy.com/oG6C31ghjeJ0)
PS Monti, please relax and don't respond to this. You may create your own thread somewhere in the forum and post, post, post... 8)
Interesting test, you could probably push those 50D shadows even further and use neat video. Pretty amazing considering the price difference between the cameras.
I've got that Shot by shot book too!
I'd like to see them both at ISO800. I know DR might be reduced even further on the 50D but it would be a more accurate indicator and show noise levels. Noise is manageable to some extent.
Quote from: Andy600 on August 30, 2013, 10:35:46 AM
I'd like to see them both at ISO800. I know DR might be reduced even further on the 50D but it would be a more accurate indicator and show noise levels. Noise is manageable to some extent.
I could do that next time BMCC is in my hand, but I would disagree it could add accuracy to the test. 800 ISO is basic (native) sensitivity with BMCC. With Canon 50D it is ISO 100. I tend to think that you have to test them in these respective ISOs to be scientifically accurate. Correct me if I'm wrong.
Quote from: rommex on August 30, 2013, 10:46:50 AM
I could do that next time BMCC is in my hand, but I would disagree it could add accuracy to the test. 800 ISO is basic (native) sensitivity with BMCC. With Canon 50D it is ISO 100. I tend to think that you have to test them in these respective ISOs to be scientifically accurate. Correct me if I'm wrong.
So ISO 800 is the lowest setting on the BMCC?
TBH I'm not sure what constitutes native ISO on a DSLR but if it's it's lowest then the 50D would be nearer ISO 200. I'm interested to see them at the same ISO sensitivity mainly to see the difference in noise. I think you'd be pulling the shadows down rather than pushing them up and it should (in theory) be cleaner. At least that's the concept behind the DUAL ISO developments.
Having said that, it's remarkable how close the cameras actually are considering age and sensor development. I've been looking at the BMCC and pocket as a future investment but haven't yet seen anything that makes me want to jump on board. The Kineraw Mini looks to be a better option, albeit a little more expensive. Makes deciding on an upgrade to a 5D3 even harder but I'm in no hurry.
Quote from: dlrpgmsvc on August 29, 2013, 09:59:13 PM
True, so not viable for normal cinema use (big and bulky tripods, optical stabilizers, and great spaces, not viable for indoor use, and so on)
But this is exactly what I'm using raw video for. Low tripod, gimball head, tele lens and x3 magnification in camera — very nice for birds. Video is especially useful for identifying uncommon birds, rarities. Furthermore, even when I don't have tele lens with me, I use my kit 17-55/2.8 lens with magnification and it's enough for documentary. Some additional ML features are great for birding too.
Yes, Andy, BMCC has ISO 800 as its lowest.
And that's why you have to use ND filter more often than not on BMCC.
And this is basically how I would do the test ideally: clean lens on 50D and ND8 on BMCC.
I didn't get your part on pulling shadows down. Usually to increase the visible DR (and to approach the iconic filmic look) I push the shadows up. I guess everybody else does, no? )
And the noise (if pushed in ACR to Gamma 2.0) looks like this: BMCC is cleaner, 50D has surfacing the rectangular pattern. But both manageable to some extent, I agree.
(http://i44.tinypic.com/2a989ds.jpg)
But I do, I do second you -- looking at this difference, I don't see a 5-year gap between these cameras. Nor a $1500 gap )
The noise pattern from 50D can be removed with dark frames. Take a look at the GoPro workflow, they used this method.
Quote from: rommex on August 30, 2013, 11:25:03 AM
...I didn't get your part on pulling shadows down. Usually to increase the visible DR (and to approach the iconic filmic look) I push the shadows up. I guess everybody else does, no? )
Of course. I must have left my brain in bed today ::)
Quote from: a1ex on August 30, 2013, 11:26:53 AM
The noise pattern from 50D can be removed with dark frames. Take a look at the GoPro workflow, they used this method.
Dark frame subtraction works well for the 50D. I've experimented a couple of times by leaving the lens cap on for a second but this eats valuable recording time especially if you change ISO or change from non-crop to crop. Does this noise remain a constant? i.e. you can have a set of pre-made dark frames at different ISO values to use or should it be done every shot? I guess if you're shooting in crop there is the possibility that you're shooting with different parts of the sensor so the dark frames wont match.
I can see this is probably a stupid question but can this be achieved in-camera by not opening the shutter for a few frames at the start of recording? or does the shutter need to be open to produce a dark frame?
I didn't do any extensive testing, so... no idea. Try using a dark frame from a few days ago and see if the pattern changes its place.
There are some tricks to record image data with shutter closed (e.g. quick AF mode, where I had to kill zebras), or on 5D3, by setting shutter blanking time to maximum. Look in the MLV thread, I've just described the data structure for storing dark correction info (nothing implemented yet).
Quote from: a1ex on August 30, 2013, 11:51:55 AM
I didn't do any extensive testing, so... no idea. Try using a dark frame from a few days ago and see if the pattern changes its place.
There are some tricks to record image data with shutter closed (e.g. quick AF mode, where I had to kill zebras), or on 5D3, by setting shutter blanking time to maximum. Look in the MLV thread, I've just described the data structure for storing dark correction info (nothing implemented yet).
I'll have to make new ones to test with. Deleted the others.
On second thoughts, it's probably better to wait for .mlv because I would need to manually log the ISO for every shot as it's not currently saved to exif.
Speaking about the noise, sensors and everything:
DXO Mark have completed the sensor test of the new 70D, which shows that its sensor has gone a tiny step from both 7D and 50D.
In terms of color depth 70D is better than 50D by 3(!)%
In terms of dynamic range -- by 1.7%
And only in low-light performance it has advanced by substantial 33%
DXO Mark aren't by far an absolute truth, but they catch the main trend I think.
It gives both reasons to rejoice and to contemplate the Canon development strategy :P
Proof link: http://www.dxomark.com/index.php/Cameras/Compare-Camera-Sensors/Compare-cameras-side-by-side/%28appareil1%29/895|0/%28brand%29/Canon/%28appareil2%29/619|0/%28brand2%29/Canon/%28appareil3%29/272|0/%28brand3%29/Canon (http://www.dxomark.com/index.php/Cameras/Compare-Camera-Sensors/Compare-cameras-side-by-side/%28appareil1%29/895%7C0/%28brand%29/Canon/%28appareil2%29/619%7C0/%28brand2%29/Canon/%28appareil3%29/272%7C0/%28brand3%29/Canon)
yeah if magic lantern wasnt existing
i would probably buy black magic cinema camera or pocket version for sure
also any developments in new DSLR without compact flash card doesnt interest me in any ways
i have to test that dark frames things
if anyone explain it little bit or send link?
pretty simple: http://en.wikipedia.org/wiki/Dark-frame_subtraction (http://en.wikipedia.org/wiki/Dark-frame_subtraction)
Dark frame subtraction is pretty straight forward.
Shoot a few frames with the lens cap on, remove it and continue your shot as usual.
When you process your raw file you'll have some dark frames. Add one of these (or a composite of several) to a layer above your footage and choose 'difference'. This should help clean up fixed pattern noise. The dark frame should be at the same ISO and be the same frame dimension as the footage you're shooting so you may need to shoot several dark frames at different ISO values and crop sizes.
You can also composite one dark frame with a copy of itself that's slightly blurred as a difference matte.
Dark frames are also useful for creating default, ISO based noise profiles in Neat Video.
hmm thats interesting
i should try that
but now this push me to idea
how about to implement dark frame in magic lantern settings
so that we can get automaticly clean images?
Quote from: Monti on August 30, 2013, 03:41:11 PM
hmm thats interesting
i should try that
but now this push me to idea
how about to implement dark frame in magic lantern settings
so that we can get automaticly clean images?
You obviously didn't read what a1ex wrote above ::)
Quote from: rockfallfilms on August 30, 2013, 10:04:22 AM
+1 - Monti's comments are beyond tedious now.
I have gone through everything and all text present is just the explanation text of what the setting does. I tried using the other digic effects including Cartoon Looks "2" and "3" and they all work. At this point I am at my wits end when it comes to this issue.
Also, if I may post outside the general topic here for a second. Do you guys believe through firmware modifications we can squeeze a few extra trimmings out of say a Hero 3 BE? Nothing crazy just forced CBR and a possible multiplier? Possibly a manual exposure mode? ISO selection alone would be phenomenal.
Quote from: Andy600 on August 30, 2013, 03:48:20 PM
You obviously didn't read what a1ex wrote above ::)
seems like he is just on the way to do this function...
Quote from: Andy600 on August 30, 2013, 10:58:02 AM
So ISO 800 is the lowest setting on the BMCC?
No, 200 is. I've no idea why they say 800 is the "native" ISO (whatever that means). I shot with it at 200 and 800 and 800 was clearly grainier as you'd expect.
Native ISO is the highest such ISO of a camera, at which the analog signal is not amplified before the conversion in digital.
I get nothing from cartoon look 1 and 2, maybe these don't work. I know 3 does... 50D is an early camera maybe those regs aren't present.
Quote from: Andy600 on August 29, 2013, 09:47:00 PM
@menoc - http://www.ebay.com/itm/Isco-Iscomorphot-16-2x-Anamorphic-Cinemascope-Lens-/200956832944?pt=Camera_Lenses&hash=item2ec9f5ecb0 right on the money and a seriously nice lens for video. You'll be able to shoot over 2.5k 16:9 with this. I would buy it myself if I could.
Pair it with a Helios 44M-2 or an old Nikon 50mm (as both flare) and you'll get pure Hollywood ;)
Just got a copy of the KMZ Helios 44M from Ukraine . . . Hope it gets here next week .. :D
(http://i764.photobucket.com/albums/xx289/in1lenin/ebay/lens/helios2/h44m-4/list102/xl_image-1.jpg) (http://s764.photobucket.com/user/in1lenin/media/ebay/lens/helios2/h44m-4/list102/xl_image-1.jpg.html)
Quote from: VideoSauce on August 30, 2013, 04:57:22 PM
Native ISO is the highest such ISO of a camera, at which the analog signal is not amplified before the conversion in digital.
Good to know, thanks.
Quote from: paulforte on August 30, 2013, 04:54:00 PM
... I shot with it at 200 ....
I beg your pardon, what do you smoke?
ISO 800 is the lowest at BMCC, wake up )
Quote from: menoc on August 30, 2013, 06:12:01 PM
Just got a copy of the KMZ Helios 44M from Ukraine . . . Hope it gets here next week .. :D
(http://i764.photobucket.com/albums/xx289/in1lenin/ebay/lens/helios2/h44m-4/list102/xl_image-1.jpg) (http://s764.photobucket.com/user/in1lenin/media/ebay/lens/helios2/h44m-4/list102/xl_image-1.jpg.html)
Amazing. I live in Kiev, Ukraine. No one wants these... ))) I tried them on digital cameras... Ridiculous non-sharpness, CA, etc... Why?
del
I was out today shooting in the mountains and when I got back and transfered the raw files to the PC I noticed this.
-rwxrwxrwx 1 1000 1000 838680768 Aug 30 10:58 M30-1059.RAW*
-rwxrwxrwx 1 1000 1000 789201088 Aug 30 10:59 M30-1060.RAW*
-rwxrwxrwx 1 1000 1000 846102720 Aug 30 11:01 M30-1100.RAW*
-rwxrwxrwx 1 1000 1000 264716480 Aug 30 11:01 M30-1101.RAW*
10:60 ?? Shouldn't this have rolled over to 11:00?
Edit: Tragic Lantern 27.08 build.
Quote from: rommex on August 30, 2013, 07:06:53 PM
Friday night. Shot with 50D ML:
I think your video is..
oh, thank you Rommex, thank you ;)
Quote from: rommex on August 30, 2013, 06:59:14 PM
Amazing. I live in Kiev, Ukraine. No one wants these... ))) I tried them on digital cameras... Ridiculous non-sharpness, CA, etc... Why?
Sharpness isn't everything in video. The classic "film look" isn't a tac sharp look, it's somewhat out of focus. And BTW, this lens is basically a cheaper copy of the Carl Zeiss Biotar. These lenses have a certain film look to them and beautiful bokeh.
This guy on flicker shot this with an EOS 7D. Pretty nice I'd say . . .
(http://farm9.staticflickr.com/8170/7922484124_cac82014b3_o.jpg) (http://www.flickr.com/photos/mattiacam/7922484124/)
Helios 44M 2/58mm (http://www.flickr.com/photos/mattiacam/7922484124/) by Mattia Camellini (http://www.flickr.com/people/mattiacam/), on Flickr
Quote from: menoc on August 30, 2013, 09:20:13 PM
These lenses have a certain film look to them and beautiful bokeh.
I see your point. Nice if it works ok for you )
Hey folks, here is a testimonial video I shot in Magic Lantern RAW on my 50D. Everything featuring Casey Faris is raw video.
Shot on a Cine Rokinon 85mm, Files transcoded in resolve in 10bit 4.2.2. Cineform, edited in Premiere PRO, and graded in DaVinci Resolve.
Quote from: D.L. Watson on August 31, 2013, 01:47:43 AM
Hey folks, here is a testimonial video I shot in Magic Lantern RAW on my 50D. Everything featuring Casey Faris is raw video.
Shot on a Cine Rokinon 85mm, Files transcoded in resolve in 10bit 4.2.2. Cineform, edited in Premiere PRO, and graded in DaVinci Resolve.
Kewl Video! Nicely Edited.
Too bad it isnt in 1080p, the compression seems to have degraded the image.
Quote from: D.L. Watson on August 31, 2013, 01:47:43 AM
Hey folks, here is a testimonial video I shot in Magic Lantern RAW on my 50D. Everything featuring Casey Faris is raw video.
Shot on a Cine Rokinon 85mm, Files transcoded in resolve in 10bit 4.2.2. Cineform, edited in Premiere PRO, and graded in DaVinci Resolve.
Next...
Ok, so frame shutter timer doesn't work for overriding, gradual expo isn't very gradual. Took those out.
Have to see what's up with zoom to 5x raw center as that isn't working either.
Also appears that despite using ADTG shutter blanking the camera still doesn't want to do over 110 shutter... I can't find why as everything else seems to be able to and I went back to the dual iso build to see if its that way.. it is. Weird.
I took out CPU usage too as a1ex said it slowed down write for him... maybe we'll see an MB more? Thoughts?
Quote from: dogmydog on August 31, 2013, 03:09:19 AM
Kewl Video! Nicely Edited.
Too bad it isnt in 1080p, the compression seems to have degraded the image.
Thanks! We sent Rampant Design a 1080p version so I'm not sure why only a 720p, highly compressed version is all that is available.
Quote from: [email protected] on August 31, 2013, 03:26:01 AM
Next...
Well, since you are so eager to see what I have in store next, here you go:
A RAW 50D short film entitled DICHOTOMY. These are some ungraded screenshots. My colorist will be completing the color-grade in Resolve tomorrow. Hopefully will be up by Sunday or Monday.
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/Dychotomy%20%280-00-06-20%29.jpg)
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/Dychotomy%20%280-00-35-06%29.jpg)
(https://dl.dropboxusercontent.com/u/9746153/Site%20Images%20%26%20Files/Dychotomy%20%280-01-17-11%29.jpg)
Ill be posting a tutorial showcasing my workflow on the film as well.
Quote from: 1% on August 31, 2013, 03:49:43 AM
Ok, so frame shutter timer doesn't work for overriding, gradual expo isn't very gradual. Took those out.
Have to see what's up with zoom to 5x raw center as that isn't working either.
Also appears that despite using ADTG shutter blanking the camera still doesn't want to do over 110 shutter... I can't find why as everything else seems to be able to and I went back to the dual iso build to see if its that way.. it is. Weird.
I took out CPU usage too as a1ex said it slowed down write for him... maybe we'll see an MB more? Thoughts?
I could be wrong but I seem to remember that exposure transitions were very smooth when ETTR was introduced. ???
re: shutter. I can get up to 1/140 with FPS overide at exact 24p and up to 1/4200 high jello. With FPS override off it goes up to 1/5900. The ADTG shutter thing you mentioned in the ADTG post doesn't seem to get above 1/60 and actually goes to negative values like 1/-3 (never seen that before)
re: disabling task mon. Probably not a bad idea if we get some gains in write speed because we'll need the extra for .mlv
re: snap to 5x raw center. Yes, it's not working correctly and still requires pressing the joystick for framing.
Just changing the reg isn't going to work, the value in there has to be calculated... it should be doing this because of:
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404B5A2C) // ADTG register 105F
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404B5A30) // ADTG register 1061
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
All the other cameras go to like 1/2k+ with FPS set to 23.976
Gradual Expo is a different feature than ETTR, its supposed to smooth expo changes in LV/H264,etc.
Quote from: 1% on August 31, 2013, 06:36:42 AM
Just changing the reg isn't going to work, the value in there has to be calculated... it should be doing this because of:
#define FRAME_SHUTTER_BLANKING_ZOOM (*(uint16_t*)0x404B5A2C) // ADTG register 105F
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x404B5A30) // ADTG register 1061
#define FRAME_SHUTTER_BLANKING_READ (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM)
#define FRAME_SHUTTER_BLANKING_WRITE (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)
All the other cameras go to like 1/2k+ with FPS set to 23.976
Gradual Expo is a different feature than ETTR, its supposed to smooth expo changes in LV/H264,etc.
Yep, I'm not much help with this. Over my head ;D
Quote from: riccardocovino on August 30, 2013, 08:53:54 PM
I think your video is..
oh, thank you Rommex, thank you ;)
Nice...
Saw it on the iPad, highly compressed artifacts tho. How did you stabilize the shots?
@1% - Been going through more ADTG regs and the camera was getting hot (not unexpected) but I noticed that temperature warnings are masked by ML. Is there a way to indicated over-temps in the ML overlay or let the Canon one show through?
BTW, for anyone reading this and worrying about their 50D overheating etc. Don't! (unless your shooting in the desert or something). We're doing things you wouldn't normally do when shooting so the overheating is expected to some degree.
It really needs the warning when FPS becomes 22 and you're trying to record.
Quote from: 1% on August 31, 2013, 05:43:14 PM
It really needs the warning when FPS becomes 22 and you're trying to record.
Yes, that would be useful
I added the warning (I guess won't help if you're shooting 30fps but who is), see if it trips when your camera overheats. I'm trying to record raw but I've only overheated like 2 or 3 times ever.
Quote from: 1% on August 31, 2013, 07:16:40 PM
I added the warning (I guess won't help if you're shooting 30fps but who is), see if it trips when your camera overheats. I'm trying to record raw but I've only overheated like 2 or 3 times ever.
Cool :) I'll try and get it to overheat.
Quote from: dogmydog on August 31, 2013, 04:32:02 PM
Nice...
Saw it on the iPad, highly compressed artifacts tho. How did you stabilize the shots?
Thanks!
When watching it on YouTube you can set up to 1080p with no visible artifacts.
It was shot either on tripod or handheld with the strap tightly across my neck. No stab in post.
@1% 2x batteries down and still not overheating ???
BTW, have you noticed any performance/write speed increase after disabling task mon? I haven't myself.
Nope, didn't really notice anything except the bin size go down. It still takes 1-3 recordings to get up to continuous.
I couldn't overheat either... even with defish/new peaking and other indicators going... I only got up to 54C.
As I see nightly builds for 50D were merged with Tragic Lantern some days ago, and include raw_rec.mo, dualiso.mo and ettr.mo, is the compilation by Andy600 any different than nightlies now?
Quote from: Monti on August 25, 2013, 10:06:10 PM
that crazy thing above is good even for a stills photo
its giving around 2 megapixel raw files
(which is more than I ever use to share my photos online or whatever you want to print it like A3+ size clean)
on 3000 mm lens like 24 burst photos per second with no buffer limitations continuously for 1 minute
then another 1 minute and again until your compact flash card is full with this 4 gb 1 minute files
that is double of what canon 1dx can do (12 burst shots per second)
also buffer size is limited for like 100 shots maybe
only there is no VR and also manual focus only
so you need like tripod to use this construction i made
but this is good for wildlife and sports shooting when u dont want to miss any frame
they do this on canon 1D C that cost like 13.000$ for 4K video but that is compessed H.264 video
and it is not a raw files like in here
so this on canon 50d i made a great opening on magic lantern (tragic lantern) thing.
(http://s019.radikal.ru/i617/1308/bb/8eceb8de5389.jpg)
good work on pointing out the differences, but you must know, 1D series never experiences buffer overruns and slowdowns even at high burst. I really like the burst silent photo mode on my little EOS M but unfortunately its buffer is too small to handle more than 9 shots
More unnecessary topic bloat ???
Quote from: akumiszcza on September 01, 2013, 12:12:40 AM
As I see nightly builds for 50D were merged with Tragic Lantern some days ago, and include raw_rec.mo, dualiso.mo and ettr.mo, is the compilation by Andy600 any different than nightlies now?
The nightlies will include anything that is pulled into the Unified build. It caught up but you'll need to check if the latest TL commits have been merged and download whichever build is newer.
Quote from: Andy600 on September 01, 2013, 12:57:39 AM
The nightlies will include anything that is pulled into the Unified build. It caught up but you'll need to check if the latest TL commits have been merged and download whichever build is newer.
Whatever that means :o, Andy, hope you will explain everything when an update is up, as you always do. Thanks )
Quote from: rommex on September 01, 2013, 08:40:21 AM
Whatever that means :o, Andy, hope you will explain everything when an update is up, as you always do. Thanks )
It means that Tragic Lantern is usually ahead of the 50D Unified build and any changes that happen in Tragic Lantern are not automatically included in the nightlies.
Developers work on their own synchronized copy of Magic Lantern code (called a 'fork'). Tragic Lantern is the name of one of these forks. Unified is the main fork.
Developers (like 1%) work on forks because they may want to add new features, make camera-specific changes or try out new stuff while keeping up-to-date with the constantly updated parent code.
When a developer has 'committed' changes (i.e. synchronized his local repository with his Bitbucket fork) they may choose to submit a 'pull request' which tells the developers of the main code that there is new/updated code
to be reviewed/considered for inclusion in Unified. After the code is reviewed it may or may not be merged (i.e. the new code may break rules, have bugs or need changes to syntax or other stuff and the dev will be asked to modify it). The process then repeats and only then (if the code is safe for inclusion in Unified) will those updates become part of 'Unified' and the automatic nightly builds.
It is done this way to keep the code cleaner and within the safe parameters set out by a1ex.
Tragic Lantern is fundamentally no different than Magic Lantern. It's shares the same code BUT Tragic Lantern does have extended features (for example: compare the TL raw module with the nightlies raw module) and other 'hacks' that may improve performance on the 50D/6D/EOS-M/600D. Regardless of the merge that happened recently, these features will not be in the Unified nightly builds. They are unique to Tragic Lantern.
Hope that helps you understand :)
I've tried today's nightly and some modules don't work, my favorite ettr autosnap doesn't work (BTW, is the EV range increase for ETTR possible in 50D? It still doesn't work for very bright or dark scenes — even in photo mode). New menu is not present, etc. I'll stick with Tragic Lantern builds then :)
Is it possible to match the central pixel of the zoom mode to central pixel of the cropped video?
I have problems framing movies in zoom mode., they are always extended more to one side.
I need to fix the zoom to 5x raw function, it shouldn't be impossible.
Quote from: 1% on September 01, 2013, 05:27:33 PM
I need to fix the zoom to 5x raw function, it shouldn't be impossible.
Possibility to move around cropped area is very nice, it's nice to have. But optionally to make both centers the same would be great too.
Hitting joystick center is supposed to work like what you're saying.
I tried this:
1. Center in 1x
2. Go to 5x an press it only ONCE... it moves it over a little bit like it should be centered. But hit it repeatedly and it doesn't work. Also not coming from centered box in 1x doesn't work.
Checked, behavior is the same on 6D and others. Is this how its supposed to work? Would have to check with a frame.
Hi folks !
It will be useful if you can share all of your testings about raw video recordings data and card speeds here: http://www.magiclantern.fm/forum/index.php?topic=8000.msg72051#msg72051
So this thread will not bloat ! ;D
Select the first links about the testings ! Many thanks ! ;)
Decided to make up a quick tutorial for lensing on the Canon 50D. It features three lenses; the 24, 50, & 85mm.
http://youtu.be/R6Eot6PBYoY (http://youtu.be/R6Eot6PBYoY)
... Definitely the kind of information every cinema photographer should have on the tip of their tongue. Enjoy.
Just installed Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip on my Transcend 16 GB 1000x and Sandisk 16GB Extreme II 60m/s and everytime I start my 50D I get the error "scripts dir missing".
Everything seems to be working tho.
EDIT: I uploaded the first episode of the webseries I'm making, shot with my 50D with TL.
You guys think it would have make a difference if I shot it on normal Canon video mode?
(Press CC for english subtitles)
http://www.youtube.com/watch?v=9bM6R9iYLzQ
Enjoy :D
So the 5x centering?
Quote from: 1% on September 03, 2013, 07:34:26 PM
So the 5x centering?
Nope. Added a comment to the commit on Bitbucket.
Hello Forum folks,
I've been out of it for about a month. I just wanted to get a consensus about the latest "solid" build you're liking. I was running the July 11 build and I was pretty happy with that but that was awhile ago, not looking for anything crazy more on the stable end. I've got the 32 and 64 gig KomputerBay cards.
Thanks All!!!!
The best piece of art presented here made on Canon 50D raw:
(http://s23.postimg.org/xcyqifwhn/IMG_2723_5_3.jpg)
Quote from: [email protected] on September 03, 2013, 09:23:32 PM
The best piece of art presented here made on Canon 50D raw:
Is that you again Monti? ::)
You do realize Mods can check your IP right?
Apologies if you're someone else but posting pointless images like this and sarky comments like your first post will likely get you kicked ;)
Quote from: Andy600 on September 03, 2013, 09:25:41 PM
Is that you again Monti? ::)
You do realize Mods can check your IP right?
Apologies if you're someone else but posting pointless images like this and sarky comments like your first post will likely get you kicked ;)
It's monti, look at his shitty name, his lack of attention was killing him.
Did he get himself banned again?
A little, if you get banned once I figure you don't do the same thing to get banned again. Waste of emails/proxys.
When I change the preview mode in RAW video on 50D, Tragic.Lantern-2.0-Andy600.Build.2013Aug19.50D109, whatever I choose the result is Always "ML Grayscale" when viewed on the LV as soon as the "SET" recording button is activated. Do this is normal ? :-\
Its normal if you're in zoom mode. There are 2 grayscales and if GD is off the 2nd one won't work.
I'm curious as to how stable it is to shoot 50d raw with a cheap EVF. I really miss the articulating screen of a 60d, and I'm wondering if an EVF would be practical.
Quote from: Andy600 on September 03, 2013, 09:25:41 PM
Is that you again Monti? ::)
You do realize Mods can check your IP right?
Apologies if you're someone else but posting pointless images like this and sarky comments like your first post will likely get you kicked ;)
You have to admit, the toilet paper is a big improvement on the green cat. Just waiting for the red grid lines to explain the rule of thirds again!
On a different note, loving the old pc flash cable on the 50d. My 550d is unreliable firing slave cells because of the preflash.
Quote from: Supermac on September 05, 2013, 03:12:10 AM
On a different note, loving the old pc flash cable on the 50d. My 550d is unreliable firing slave cells because of the preflash.
In the world of flash photography, this is the first time I've seen someone say they love PC sync. Hahah most outdated system in digital photography. Then, even though I curse it every photo shoot, I don't know what I'd do without it for wireless slave.
Anyone test MLV format for USB LiveView output? About to test. Yeah, I'm that guy still resisting buying a HDMI monitor to try to use his Android tablet over USB, since I never figured out why raw_rec stopped the output.
Edit: No go. Was hopeful mlv_rec would solve this strange outlier for the 50D, but sadly it acts the same as raw_rec. MLV format is pretty great though with take#s and all, takes too big a hit for 1080 recording right now, but is fine for full frame even with a few LV overlays on.
Hello guys i was wondering if any1 could help me . I did all the steps and couldnt make it work. Doesnt appear any error, but when i finish all steps i hit the trash button and nothing happens . I am on Lion Imac but i had to use a windows old laptop i had to be able to complete the step that asks for that .exe file . I got a 32 GB Trancend SD . I really want the feature that allows to change WB while recording ! I would appreciate any help ! Thanks in advance !
Hey guys. I have been off the forum for a while now. Whats new? Whats the most recent firmware? Anything cool happen? haha
I been reading warning of very large file. anyone actually know the size of 1 sec footage?
or how long of a footage does a 8 GB CF card fit?
I am talking about the 50D raw video.
Any input is extremely appreciated !
ruanjiayuan, it depends on what frame size/aspect ratio you choose, but shooting say largest frame in 1x (non-crop) mode you'll be lucky to get even 3 minutes worth on an 8 GB card. That's not much even just for testing. Ideally, get a fast large card -- check out buying recommendations on the thread since some brands/sizes are better than others (eg. 64 GB 1000x KomputerBay card is better than their 128 GB card). I have a 64 GB card which allows me to shoot approximately 23 minutes of footage. Not much if you are used to H.264 video -- welcome to the wonderful world of raw file sizes!
Canon 50D Prototype VAF Filter Update...
Now have a tracking number, though the item has not yet shipped. Here is an except from Mosaic Engineering... "Return shipping of Levi Davis' 50D (...) including rev. 1 prototype VAF-50D. (...) please let us know how it goes! --MAV"
... Will post photos and videos for ML users and Mosaic Engineering review purposes.
I'm concerned with the 50D VAF filter interfering with the communication between the body and Canon AF / IS lensing as well as the ability of the camera to resolve detail. Do you have any additional suggestions that should be considered during this prototype testing phase?
Print a test chart with the highest dpi you have available. The filter should work perfectly fine in full sensor mode, and you should do the tests in that mode. For real life tests I would suggest very fine detail in very contrasty situations. Typical are: Trees against the sky, grass against the sky, water (sea,river,etc...) with very small waves and reflection of buildings on it should give terrible moire without the filter, also distant buidlings (sky line),etc...
In 2.5crop mode (5x zoom) you will be able to see how the filter blurs the lines, it's not suited to film that way, if you want crop mode take the filter off.
Exciting news about prototype, :) guys!
Sorry to bump in guys,
I was away from forum a little, have a question if you can help me with.
Current new set up is 2 x 50D and BMCC multi camera set up.
I ll be filming cinemascope 2.39 with all three camera RAW , BMCC will be A camera and 50D'S mounted on Jib and Steady cam and/or slider simultaneously .
Question is can 50D be activated to record RAW from remote button or any other ways, wish to be able to record while keeping an eye on 7" monitor on my jib,
not having to go every time on "Action" and play with camera ,apart from focus thing.
Thanks for your help and yes I am 50D supporter ;) long life to ML!
Hello, Ive been reading the forum for a while, I think all the RAW work is awesome!
Im currently hung up on how to record continuous RAW @ 720p
I have installed ML, and then andy600's TL bin.,
I have changed my settings in camera, to 720p RAW recording, but it just gives me 208 Frames, no more, and stops recording.
is it just that I need a faster CF card? or are there other features I need to make sure are on and off with in the menus
Thanks for read! My current card is 200x.
Quote from: darko on September 07, 2013, 01:59:45 PM
Exciting news about prototype, :) guys!
Sorry to bump in guys,
I was away from forum a little, have a question if you can help me with.
Current new set up is 2 x 50D and BMCC multi camera set up.
I ll be filming cinemascope 2.39 with all three camera RAW , BMCC will be A camera and 50D'S mounted on Jib and Steady cam and/or slider simultaneously .
Question is can 50D be activated to record RAW from remote button or any other ways, wish to be able to record while keeping an eye on 7" monitor on my jib,
not having to go every time on "Action" and play with camera ,apart from focus thing.
Thanks for your help and yes I am 50D supporter ;) long life to ML!
I think you can set recording to start with half shutter, which is remotely triggerable.
Quote from: derkiki on September 07, 2013, 04:47:24 PM
I think you can set recording to start with half shutter, which is remotely triggerable.
Do you have an idea how this can be set (from ML Menu or Canon Menu)?
Quote from: derkiki on September 07, 2013, 04:47:24 PM
I think you can set recording to start with half shutter, which is remotely triggerable.
Great, thank you ,much appreciated.
Thanks Araucaria.
[Delete]
Sooo... Some folks say "Film look, I like Andy's film look" well if you mean cinematic look - it isn't. As Till Shweiger movie was cinematic look.
If you mean film look like those shot on old film then it isn't again exactly that look.
For those who want to see what is real film look shot yesterday on Canon 50d raw video here is it:
"Green Cat Returns"? Any chance to keep offtopic discussion offtopic?
Quote from: akumiszcza on September 08, 2013, 10:40:29 AM
"Green Cat Returns"? Any chance to keep offtopic discussion offtopic?
offtopic disctussion is complaining of useless users here like you
me doing job about the title of the topic and you?
Quote from: omfgandy on September 07, 2013, 04:27:10 PM
Im currently hung up on how to record continuous RAW @ 720p
I have installed ML, and then andy600's TL bin.,
I have changed my settings in camera, to 720p RAW recording, but it just gives me 208 Frames, no more, and stops recording.
is it just that I need a faster CF card? or are there other features I need to make sure are on and off with in the menus
Thanks for read! My current card is 200x.
200x card is too slow for raw. You can get more frames by decreasing fps (eg. to 23.976), turning off Global Draw features, turning on some hack settings in ML. But most probably it will be too slow anyway.
Quote from: rawmania on September 07, 2013, 08:41:54 PM
Do you have an idea how this can be set (from ML Menu or Canon Menu)?
REC key: HalfShutter in movie menu.
Quote from: Da Vinci on September 08, 2013, 10:52:19 AM
offtopic disctussion is complaining of useless users here like you
me doing job about the title of the topic and you?
I like you too, Monti.
Does Andy600 have a guide up? been looking through this thread for it with no luck.
Also,
which tragic lantern build is comfortable running 1920x1080 in crop mode. I have a 90MB/s 16gb Sandisk Extreme Pro for it to record on.
Also what are the recommended settings for it do so please. Ive tried ETTR off, global draw off but no luck.
Any help is greatly appreciated.
Quote from: oc_masta on September 08, 2013, 04:11:30 PM
Does Andy600 have a guide up? been looking through this thread for it with no luck.
Also,
which tragic lantern build is comfortable running 1920x1080 in crop mode. I have a 90MB/s 16gb Sandisk Extreme Pro for it to record on.
Also what are the recommended settings for it do so please. Ive tried ETTR off, global draw off but no luck.
Any help is greatly appreciated.
Nope, sorry I haven't had time to finish it and wanted to include some stuff about .mlv. Can't give an ETA on when it will be ready but there are other guides available that should give you lots of info including a free one for the 5D3 and EOSHD's 50D raw shooters guide.
The Aug27th build seems stable https://bitbucket.org/andy600/tl50d/downloads/Tragic.Lantern-2.0-Andy600.Build.2013Aug27.50D109.zip
I'm uploading a newer build today with .mlv but I don't think you'll get any speed increase.
@1% - Can we lose the vertical black bars in crop permanently. They don't seem to help with speed and I'm always switching them off with DISP. I can't find the code. Can you give me a hint? :)
Also, I've been playing with a new build and crop centering seems better if you center in non-crop first. I think it wasn't working correctly on my previous build (not an uploaded build) so maybe I screwed up somewhere. I've also stripped out the start strings in some modules because they caused compile errors but bolt_rec still has problems. I've also changed your .mlv module to show as MLV Rec in the menu because it may confuse a few users if they have both loaded.
The new build seems better with .mlv but it's still marginally slower than .raw. It's totally usable but every shot seems to have a couple of corrupt frames at the start. I'd like to remove the black bars before uploading it.
oh ok, thanks anyway, if you could put it up as it stands, that would be EPIC of you and sure to help many others I assume. But I understand if you wouldn't want to.
mlv can be played back cant it?
i'm sure I have a codec installed for my pc's media player to play .mlv
Quote from: oc_masta on September 08, 2013, 04:47:53 PM
mlv can be played back cant it?
i'm sure I have a codec installed for my pc's media player to play .mlv
No
Quote from: Andy600 on September 08, 2013, 04:48:59 PM
No
LOL I got it mixed up with mkv. I understand the abbreviation now, totally missed it.
Quote@1% - Can we lose the vertical black bars in crop permanently.
If you want.
Quote from: 1% on September 08, 2013, 04:59:07 PM
If you want.
Doh! I was staring right at that bit of code too ::) Just saw the commit. Thanks man :)
New Tragic Lantern 50D build uploaded
This has the old raw_rec and new mlv_rec modules included. (mlv_rec is the new raw_rec module from g3ggo but renamed for Tragic Lantern).
You must now select which modules to load in the modules menu then reboot. ML will remember your selections.
Although you can have both MLV and RAW modules loaded you should obviously have only one enabled at anytime. The modules appear in the movie menu as usual. Settings are independent so e sure to set up each with your preferred settings.
MLV raw is currently for testing purposes at the moment. You will probably find your write speeds reduce a little but that's the trade-off for better metadata and exif info in the DNGs. You may also experience a couple of corrupt frames at the start of recording.
MLV video will need converting to .raw using mlvdump.exe (look at g3gg0's raw 2.0 thread http://www.magiclantern.fm/forum/index.php?topic=7122.0 (http://www.magiclantern.fm/forum/index.php?topic=7122.0)) or directly to DNG using @gnarr's mlv2dng app. See http://www.magiclantern.fm/forum/index.php?topic=7802.0 (http://www.magiclantern.fm/forum/index.php?topic=7802.0). .mlv files will be saved to your DCIM folder
5xCrop centering now works better. To use you should press the joystick once in normal (non-crop) mode to center the box (it take a moment to center). Then in crop mode press the joystick once again. A dialogue will appear momentarily telling you some coordinates.
The vertical black bars in crop mode are gone :)
There are various other fixes and tune-ups for ETTR, Dual ISO, Digic Peaking and other stuff. Sorry I can't provide a full changelist but a look through the commits will give you a rough idea of what is new/fixed/still problematic: https://bitbucket.org/andy600/tl50d/commits/all
As ever, this code is brought to you by 1%, A1ex, G3ggo and the other amazing ML devs. I'm just compiling it ;)
Download: https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.Build.2013Sep08.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.Build.2013Sep08.zip)
Don't forget to move the extra folder containing raw2dng.exe and cr2hdr.exe to your desktop. These files are for processing Dual ISO and Raw video.
Don't ask dumb questions!! If you haven't kept up to date with developments USE THE FORUM SEARCH
Awesome, I will try the mlv format when back home. Right now I am on holliday in Ireland. I shot some amazing raw scenes, which I will showcase when I am back home.
For now a test of one relaxing scene to test my workflow:
or for better quality, the download: http://www.savale.nl/files/rawTest.mp4
A little FPS Override raw video timelapse from last night :)
Quote from: Andy600 on September 09, 2013, 05:28:09 PM
A little FPS Override raw video timelapse from last night :)
You are basically just using the raw_rec module to save shutter releases or?
Quote from: PressureFM on September 09, 2013, 07:17:24 PM
You are basically just using the raw_rec module to save shutter releases or?
Yes. Also it's a quick method for doing timelapse. I could have shot full-res photos and used the intervalometer but that would have taken longer to set up. I'm gonna experiment with Dual ISO next time. I've already saved a config that's set up for this specific timelapse so I'm hoping for some more fog tonight :)
Could anyone help me with a "issue" I'm having with my 50d?
I've been recording raw with a 5D3 and recently went with a 50D for some aerial work.
- When using FPS ovewrite from 30 to 23.976 I get the maximum recording shutter speed at 1/120. I can only record at above 1/120 when using 30fps, but in this case I need to lower RAW recording resolution to keep continuous recording.
Is there a workaround this? What I'm doing wrong here? I've been shooting at f22 in sunny day to get around this, which is not ideal..
Thanks!
For some reason it won't let you set higher speeds even with ADTG shutters so I dunno whats wrong with it.
Quote from: hugosilva on September 09, 2013, 08:50:57 PM
Could anyone help me with a "issue" I'm having with my 50d?
I've been recording raw with a 5D3 and recently went with a 50D for some aerial work.
- When using FPS ovewrite from 30 to 23.976 I get the maximum recording shutter speed at 1/120. I can only record at above 1/120 when using 30fps, but in this case I need to lower RAW recording resolution to keep continuous recording.
Is there a workaround this? What I'm doing wrong here? I've been shooting at f22 in sunny day to get around this, which is not ideal..
Thanks!
Use an ND filter
When you put it into jello mode it goes up to 1/2000, you told me a few weeks ago and it works.
Quote from: Andy600 on September 09, 2013, 05:28:09 PM
A little FPS Override raw video timelapse from last night :)
Very cool vid, Andy! Smooth moving.
I was about to ask you if you used a crane, but read the details and saw that you did it in after. :)
Quote from: Andy600 on September 09, 2013, 07:21:30 PM
Yes. Also it's a quick method for doing timelapse. I could have shot full-res photos and used the intervalometer but that would have taken longer to set up. I'm gonna experiment with Dual ISO next time. I've already saved a config that's set up for this specific timelapse so I'm hoping for some more fog tonight :)
Pardon my ignorance but ML does have a built-in intervalometer and exposure ramping. I suppose you a fine with the resolution downgrade ;)
Quote from: PressureFM on September 09, 2013, 09:56:15 PM
Pardon my ignorance but ML does have a built-in intervalometer and exposure ramping. I suppose you a fine with the resolution downgrade ;)
Hey, it's 14 seconds long and was a spur-of-the-moment decision to try and capture what I was seeing. Maybe read the description on Vimeo :)
It's not a serious attempt at a timelapse and resolution wasn't my first thought. I know what Magic Lantern can do ;)
I get a lot of hotpixels when doing timelapses at night with 0.2s shutter
Quote from: araucaria on September 09, 2013, 10:47:55 PM
I get a lot of hotpixels when doing timelapses at night with 0.2s shutter
I did too. I used the hot pixel filter in Raw Therapee. It works but also does weird things to stars.
Working with latest Tragic Lantern... Had an instance today where Live View on Canon was flickering with random colors (not during record) (lasted about 2 - 3 seconds)... Exposure Override turned on... 23.976 fps... Global Draw On... 1/48 shutter... Non-Canon 2200 mAh battery... Komputerbay 64 GB 1000X... Raw_Rec Module... ISO 800... That's about it other than the fact that the camera had been turned on for about 10 minutes before the flickering occurred.
Decided to press record even though the screen was flickering... Fortunately, when I pressed Record and Raw_Record was activated the flickering went away. Not even a single frame was corrupted during a 2 minute take... Nice.
Won't be recording again till Thursday... Just looking to help, if possible. FYI: Love how the black side-bars are gone! Headroom is now accurate to the Canon LCD screen. Maybe it's just me but the past couple Tragic firmware updates were a bit off from the Canon LCD (shooting 1584x892 and was cutting off the tops of heads even though the framing left plenty of headroom - like title-safe distances for headroom... Hmm?)... Anyway, thanks for the Sunday compile Andy600 and for the latest updates 1%. Can't say enough how powerful the color-depth and image appears!
Hi there,
I currently use a mkii for dual iso and have cr2hdr mac version, will the same version work for 50D at all? if not is there a mac version as i can only find 50DCR2HDR for windows.
What are adtg_gui.mo, ime_base.mo, ime_rot.mo and ime_std.mo please? not seen these before as iv come from 5Dmkii builds.
Hope you can help,
Cheers.
With the latest (18 august) release of andy's magic lantern compile, (freshly installed on a clean 2.3 installation on a brand new kompoterbay card formatted only once in-camera) I have yet to see how autoexposure works. I enable the module and turn it on in the exposure menu with the camera on M mode. Nothing changes with the behaviour of the camera. Am I missing something?
Quote from: Doyle4 on September 10, 2013, 05:19:30 PM
Hi there,
I currently use a mkii for dual iso and have cr2hdr mac version, will the same version work for 50D at all? if not is there a mac version as i can only find 50DCR2HDR for windows.
What are adtg_gui.mo, ime_base.mo, ime_rot.mo and ime_std.mo please? not seen these before as iv come from 5Dmkii builds.
Hope you can help,
Cheers.
The mac version should work. Try it ;)
adtg_gui = for exploring adtg registers. It's a dev tool. You don't need to load it for anything else.
The ime modules work with the .mlv module for inputting text etc.
Quote from: johansugarev on September 11, 2013, 01:18:22 AM
With the latest (18 august) release of andy's magic lantern compile, (freshly installed on a clean 2.3 installation on a brand new kompoterbay card formatted only once in-camera) I have yet to see how autoexposure works. I enable the module and turn it on in the exposure menu with the camera on M mode. Nothing changes with the behaviour of the camera. Am I missing something?
Works here ??? It's for photos. You need to set it up. See the Auto exposure thread for info. I haven't used it much so can't help.
BTW you're 2 releases behind https://bitbucket.org/andy600/tl50d/downloads
I tried not to fiddle with tragic lantern, but since it works there and there are a lot of exciting stuff, here goes.
It works nice for when someone how can't expose happens to use the camera. I want to configure it so it starts pushing the ISO up only when the lowest shutter speed that I have selected isn't giving it enough light. It sort of does it when I pushed the ISO curve to the right a bit.
So I am giving it a minimum shutter of 1/80, ISO from 100-1600 and aperture wide open all the time and what I want is to keep as low as ISO can go until I run out of light for 1/80 at ISO 100 then jack up the iso for a correct exposure. I am guessing the exposure compensation will work as advertised?
New discovery: Digic Focus Peaking + Cartoon Look 1 = better peaking :)
Johansugarev - If you're referring to the auto exposure module it's for photos. It doesn't work in Live View. I don't think what you describe is possible. You need auto ISO with ramping and that, AFAIK, doesn't work on the 50D.
New 50D user here, iv used ML on my mkii many of times and i spotted a difference instantly and that is the mkii has movie viewer for live view, when using the 50D for RAW video time lapses using fps override, if i use 1fps is what being shown one the display how it will look? i have a ND filter if so as it looks very over exposed. Im wanting to do day time time lapses btw.
Cheers in advance.
Quote from: Andy600 on September 11, 2013, 01:29:55 AM
The mac version should work. Try it ;)
adtg_gui = for exploring adtg registers. It's a dev tool. You don't need to load it for anything else.
The ime modules work with the .mlv module for inputting text etc.
Thanks Andy600, ill delete what i dont need then :)
Quote from: Andy600 on September 11, 2013, 02:41:42 AM
New discovery: Digic Focus Peaking + Cartoon Look 1 = better peaking :)
Johansugarev - If you're referring to the auto exposure module it's for photos. It doesn't work in Live View. I don't think what you describe is possible. You need auto ISO with ramping and that, AFAIK, doesn't work on the 50D.
I am not that lost and was talking about regular stills without live view. I figured it out and it suits my needs. Thanks :)
Quote from: Doyle4 on September 11, 2013, 02:55:54 AM
New 50D user here, iv used ML on my mkii many of times and i spotted a difference instantly and that is the mkii has movie viewer for live view, when using the 50D for RAW video time lapses using fps override, if i use 1fps is what being shown one the display how it will look? i have a ND filter if so as it looks very over exposed. Im wanting to do day time time lapses btw.
Cheers in advance.
Hi Doyle,
What ND filter are you using?
I've found that an ND8 is fine for 2.5 FPS but at 1 FPS the image is over exposed no matter what I've tried to do to stop everything down.
Have a look at this.
The first part is 2.5 FPS and needed little work to correct the exposure, the last scene is 1 FPS and took some work to bring it back.
Of course an overcast day might be OK with an ND8 - try out an ND16 and see what the results are like, I'll be getting one to try slower framerates.
Cheers
Phil
Its a variable one, not that great to be honest, ND2 to 12 i think it is?
footage looks good, i see what you mean at the end, mine where a lot more exposed, screen was almost white.
Think what i need to do is be able to keep shutter speed @1/50 but manage to keep fps low, i noticed when shooting in h264 it became darker about 3seconds in, with RAW i noticed the DNG's opened over exposed and looked like what was on screen.
Quote from: Doyle4 on September 11, 2013, 02:55:54 AM
New 50D user here, iv used ML on my mkii many of times and i spotted a difference instantly and that is the mkii has movie viewer for live view, when using the 50D for RAW video time lapses using fps override, if i use 1fps is what being shown one the display how it will look? i have a ND filter if so as it looks very over exposed. Im wanting to do day time time lapses btw.
Cheers in advance.
isn't turning intervalometer and silent pics on at the same time a good idea?
Quote from: simulacro on September 11, 2013, 01:09:14 PM
isn't turning intervalometer and silent pics on at the same time a good idea?
of course it is, you keep your shutter count but resolution is much much lower than normal.
Quote from: simulacro on September 11, 2013, 01:09:14 PM
isn't turning intervalometer and silent pics on at the same time a good idea?
Yeah true! have to test that one! got a 600D instead now as the 50D was dying unfortunately and had to take it back :(
Has anyone heard of any progress on the Mosaic Engineering VAF filter for the 50D?
Quote from: menoc on September 11, 2013, 08:51:42 PM
Has anyone heard of any progress on the Mosaic Engineering VAF filter for the 50D?
this should fit to 50D, since they have the same size of hole in front of the lens. http://www.mosaicengineering.com/products/vaf/txi/main.html
Quote from: zuzukasuma on September 11, 2013, 11:32:45 PM
this should fit to 50D, since they have the same size of hole in front of the lens. http://www.mosaicengineering.com/products/vaf/txi/main.html
It might fit the hole but it won't work because the sensors are different.
There is a prototype VAF for the 50D in the hands of one ML forum member now. We're just waiting for the results ;)
Quote from: Andy600 on September 11, 2013, 11:43:31 PM
It might fit the hole but it won't work because the sensors are different.
There is a prototype VAF for the 50D in the hands of one ML forum member now. We're just waiting for the results ;)
Awsome! Hopefully it won't impact exposure too much. As it is the 50D is not the best when it comes to low light.
Got the prototype 50D VAF in the mail today. Unfortunately, had to go straight to work... Still there. Anyway, brought the camera to work and was able to take quite a few shots here and there... Will be home in about 3 hours to process footage and upload images to ML Forum. Again though, they are not the original shots that I had planned to shoot with the VAF and 50D.
Will record video tomorrow morning. Plan on a better demonstration of the 50D VAF and proper posts on early Friday morning.
... Thus far...
Appears to be little to no light lose.
No moire and alliasing on Canon LCD screen. The Live View 10x mode image is softer.
The VAF may be adding additional flares from lights - Need to double check - - Noticed this with a Nikon 50mm F 1.4 Non-AI that had a 52mm UV filter. However, the Nikkor 50mm 1.4 has a rear element larger than the VAF filter. Didn't notice this issue with the Tokina 12 - 24!
The VAF looks nearly identicle to the T2i filter. Zuzukasuma may be right. However, I highly doubt it is the same product. Mosaic said that they built this unit specifically for the 50D sensor.
The Tokina 12 - 24 is no longer parfocal. Focus setting are different. It's almost as though the focus setting are reversed. Infinity is now macro and macro is now infinity. Will have to look this over again to confirm, though. I assume that every VAF filter has the same issue.
Finally, the electronic components work with the lens. There are no issues using EF electronic lenses with the 50D VAF.
... Anyway, can't wait to get home and process footage... Will conduct proper tests tomorrow morning with a Test Chart and more appropriate video shots such as a brick wall...
Plan on a video post and ML post on Friday morning... I will be reading posts and comments on ML. Leave some feedback and suggestions... We should share what we think. Mosaic says they want to hear how these tests are working out.
Just so you know, I have watched Mosaic Engineering's video posts on their website and basically plan to do the same tests. This includes post sharpening and non-post sharpening.
Expect images from video posted this morning... Remember, this is the prototype and not the final product...
Quote from: LEVISDAVIS on September 12, 2013, 05:16:07 AM
Got the prototype 50D VAF in the mail today.
Expect images from video posted this morning... Remember, this is the prototype and not the final product...
awesome!!!!
Update: Canon 50D Mosaic Engineering VAF prototype...
https://copy.com/weRtPp0O9A0w (https://copy.com/weRtPp0O9A0w)
Uploaded DNGs in groups of 10. Each sequence is named according to the shot... Was at work all day and had to take a break to make this possible... As a result there is only one comparison shot with the VAF and without. Additionally, there are a number of shots displaying the filter using a Tokina 12 - 24mm lens. I only used 12mm and 24mm. Nothing in between. Looks like I may need to test additional focal lengths as there may or may not be edge-to-edge sharpness depending upon F-Stop and focal length...
Will know more during tomorrow's testing at my studios in Tempe, AZ. Will post more photos and quick video displaying the filter at work. This will be broadcasted on Vimeo & YouTube Friday morning.
Lots of Light! :D
Is the VAF user installable?
Thanks for this Levi, looking forward to the videos!
The VAF is user installable.
The user pinches the AIF filter with a set of custom made tweezers that come with the VAF filter. Basically, the user places / pinches the VAF filter into the body of the camera.... Takes about 10 seconds to install.
planning to get canon 50D for raw video (i'm raising money), so i'm here to ask you guys does it worth it? i have some questions
1. is it true that you cant use over 1/120 shutter speed in 24p mode?
2. does ettr work in video mode?
3. does it worth that money to get vaf?
4. can i use manual canon lens?
(http://i.imgur.com/uIjLbUO.jpg)
Nice results, and i can kill the moire a little. Try it by yourself using this settings, thanks. I want to see more tests.)
p.s.: thanks for the dng file
Quote from: lomka on September 12, 2013, 08:45:15 PM
planning to get canon 50D for raw video (i'm raising money), so i'm here to ask you guys does it worth it? i have some questions
1. is it true that you cant use over 1/120 shutter speed in 24p mode?
2. does ettr work in video mode?
3. does it worth that money to get vaf?
4. can i use manual canon lens?
Answers:
1. No.
2. Yes.
3. Yes.
4. Yes.
Testing the 50D RAW this summer.
Received a prototype VAF filter from Mosaic Engineering yesterday afternoon. Went through a couple tests thus far... Feel free to download DNGs of the 50D with the prototype VAF...
https://copy.com/IOqlwsmWUi8i (https://copy.com/IOqlwsmWUi8i)
Thanks. The company producing/inventing/manufacturing the filter is called Mosaic Engineering. They are headquartered in Pennsylvania, USA. The footage is shot in Phoenix, AZ. I am not affiliated with Mosaic Engineering or Magic Lantern other than I'm trying to put the two and two together... In my opinion, this combination is an incredible opportunity to create an appropriate production camera with high-quality imagery and feel-good results.
Enjoy!
...(Rending raw video results in background...) Video samples available soon.
Thanks for the updates regarding the new filter.
On another update note, DaVinci Resolve 10 Public Beta is live on the BlackMagic site.
http://www.blackmagicdesign.com/products/davinciresolve (http://www.blackmagicdesign.com/products/davinciresolve)
As always, the Lite version is free. Haven't tested new features yet, but from the preview a month or so ago, it looks nice!
aaaand still no AMD support on windows.
Read up that the new Mac Pro is running open GL AMD graphics cards... Wouldn't this warrant a need for AMD support?
Myself, I just lost support for having Mac OSX 10.7... Can't upgrade to 10.8 because of the Mac Pro's build date. Still though it's a 2.66 8 core with 16 GB ram and a 1GB HD5770...
Davinci Resolve Lite Readme file states * OpenCL support for AMD GPUs on Windows
Davinci resolve lite also says nvidia driver required... I saw no mention of AMD, maybe its buried in there.
I think AMD cards are properly supported but I've now got issues with an Nvidia card that has OpenCL. Was working fine on V9 but V10 keeps crashing. Just hope a rollback works :(
Solved my own problem :)
If anyone else gets OpenCl errors when starting Resolve 10, go to the advanced tab and enter:
LsManager.3.NumGPUs = 1
LsManager.3.GPUMapping = 0
LsManager.3.GPUMappingEnable = 1
Alright a report from the field here - shot a promo on a 50D raw the other day. Apologies if it's a bore but may be handy for any thread stalkers like me planning a shoot!:
First things first - the latest versions are getting incredibly stable given what they're doing. equivalent to the red MX i'd say...
I was shooting on 2 x 32GB Sandisk extreme 60mbs (these were fine for the 50D's sizes up to a point, I was shooting 720p or just above to make sure I wasn't burning through cards at a silly rate) & 1x 64gb 1000x komputerbay. Couple of idiosyncrasies with both of these cards - first the Sandisk wouldn't give an up to date read-out of available space and would 'pop' the camera when full requiring a battery pull. I'm guessing this was because they're slower, but overrall I head less crashes with these than the Komputerbay, which I guess comes from build quality.
I'm wondering if you could chance a 400x transcend, anyone have any experience with this? If I was shooting regularly on the 50D I think a Nexto SSD backup would probably be a good investment - you reallllllly burn through the cards so something to just back something up immediately would be fantastic. Obviously no duplicate so it'd be at your own peril. Any idea if a less hungry (12 bit?) format has progressed any further? Or if this is even possible...
Towards the end of the day, having shot outdoors on a relatively sunny one, I had some problems with overheating setting the framerate back from 30.4 to 22. 10 minute break to cool off fixed this.
Battery's, I had 6 - 4 old & 2 new + a battery grip. I bought the two new ones for this shoot and i'm now of the opinion that anyone suffering quick battery drain has got old, dud batts. The two new lasted virtually all of the first day of shooting & I fired through the old 4 in another 2 hours. Given that I already have the grip i'm going to shoot on eneloop rechargeable AAs next time, should offer a good bit more capacity. Really, you're going to burn through your cards at a 5/1 ratio to your batteries at least so it's not too much of a concern.
Exposure, no problems. I generally shot under 1-2 stops outdoors as I wanted to get the sky in & I trusted id be able to pull what I needed out of the blacks - and you can.
Having no playback...yknow, if you need to show clients rushes on set then this camera's ruled out. Dont bother with DaVinci, it can't deal with CDNG's out of the 50D - I went through after effects and pre-graded every shot which was a long process but actually a godsend when it comes to editing as everything is halfway there. Given it took me 3 days to transcode everything for editing - this camera is for labours of love, where you have time in post. But the aesthetic is absolutely, hands down, unbelievable. I much prefer it to blackmagic & i'd say it's closest aesthetic is Alexa. I really cannot rave about the image quality enough - beautiful.
Quote from: Andy600 on September 13, 2013, 04:43:47 PM
I think AMD cards are properly supported but I've now got issues with an Nvidia card that has OpenCL. Was working fine on V9 but V10 keeps crashing. Just hope a rollback works :(
Yep. It keeps crashing on me too.
Quote from: menoc on September 13, 2013, 05:42:08 PM
Yep. It keeps crashing on me too.
Did you try what I wrote above?
It GPFs on me when "loading surface"
[OT] Resolve 10's optical flow is pretty damn good! I can do very passable slowmo on 50D footage now 8)
Love that you can set sharpness in the debayer too and it feels like debayering in general has improved quite a bit. Not sure (yet) if it will replace my Rawtherapee workflow but it's very promising.
Quote from: 1% on September 13, 2013, 06:00:00 PM
It GPFs on me when "loading surface"
Are you using a hardware controller?
Run the CaptureLogs.bat in the Black Magic folder (program files). It will write a zip to your desktop. Look in the zip for ResolveDebug.txt. Might give you some hints.
Quote from: father_v on September 13, 2013, 05:03:41 PM
Alright a report from the field here - shot a promo on a 50D raw the other day. Apologies if it's a bore but may be handy for any thread stalkers like me planning a shoot!:
First things first - the latest versions are getting incredibly stable given what they're doing. equivalent to the red MX i'd say...
I was shooting on 2 x 32GB Sandisk extreme 60mbs (these were fine for the 50D's sizes up to a point, I was shooting 720p or just above to make sure I wasn't burning through cards at a silly rate) & 1x 64gb 1000x komputerbay. Couple of idiosyncrasies with both of these cards - first the Sandisk wouldn't give an up to date read-out of available space and would 'pop' the camera when full requiring a battery pull. I'm guessing this was because they're slower, but overrall I head less crashes with these than the Komputerbay, which I guess comes from build quality.
I'm wondering if you could chance a 400x transcend, anyone have any experience with this? If I was shooting regularly on the 50D I think a Nexto SSD backup would probably be a good investment - you reallllllly burn through the cards so something to just back something up immediately would be fantastic. Obviously no duplicate so it'd be at your own peril. Any idea if a less hungry (12 bit?) format has progressed any further? Or if this is even possible...
Towards the end of the day, having shot outdoors on a relatively sunny one, I had some problems with overheating setting the framerate back from 30.4 to 22. 10 minute break to cool off fixed this.
Battery's, I had 6 - 4 old & 2 new + a battery grip. I bought the two new ones for this shoot and i'm now of the opinion that anyone suffering quick battery drain has got old, dud batts. The two new lasted virtually all of the first day of shooting & I fired through the old 4 in another 2 hours. Given that I already have the grip i'm going to shoot on eneloop rechargeable AAs next time, should offer a good bit more capacity. Really, you're going to burn through your cards at a 5/1 ratio to your batteries at least so it's not too much of a concern.
Exposure, no problems. I generally shot under 1-2 stops outdoors as I wanted to get the sky in & I trusted id be able to pull what I needed out of the blacks - and you can.
Having no playback...yknow, if you need to show clients rushes on set then this camera's ruled out. Dont bother with DaVinci, it can't deal with CDNG's out of the 50D - I went through after effects and pre-graded every shot which was a long process but actually a godsend when it comes to editing as everything is halfway there. Given it took me 3 days to transcode everything for editing - this camera is for labours of love, where you have time in post. But the aesthetic is absolutely, hands down, unbelievable. I much prefer it to blackmagic & i'd say it's closest aesthetic is Alexa. I really cannot rave about the image quality enough - beautiful.
I wrote something about it in my blog. It's going to get a bit easier . . .
http://theindieshooter.com/2013/09/11/native-cinema-dng-support-for-adobe-premiere-pro-cc-coming-in-october-2013/ (http://theindieshooter.com/2013/09/11/native-cinema-dng-support-for-adobe-premiere-pro-cc-coming-in-october-2013/)
50D Prototype Anti-Aliasing Filter Video Test... Available at...
http://youtu.be/0VLn6GzFpzM (http://youtu.be/0VLn6GzFpzM)
Download DNG images and ProRes 422 video of the prototype 50D anti-aliasing filter from Mosaic Engineering at...
https://copy.com/IOqlwsmWUi8i (http://copy.com/IOqlwsmWUi8i)
Thanks for the VAF test Levi. Looks promising.
I'm trying to download a couple of your dngs but they seem way too small and won't open. Are they still uploading? ignore - was a Copy error
Resolve 10 is out and the pink dots are gone!!!
Quote from: Andy600 on September 13, 2013, 05:47:20 PM
Did you try what I wrote above?
Yes. But my system is Ancient - 2008 MacPro 1,1, Dual core Intel Xeon, 10GB RAM, OSX 10.6.8
Same as Levi, can't upgrade to 10.8 anymore and have not found a copy of 10.7. My laptop on the other hand is a brand-spanking-new macbook pro - I'll try on that instead.
Thanks Levi, this looks good for being the first prototype!
One small thing, can you remove the s from the https in your Vimeo link - it will embed in the forum properly then.
Quote from: 1% on September 13, 2013, 03:22:21 PM
aaaand still no AMD support on windows.
Not true. It runs fine with my ATI HD5670. Allows fluid grading oft ML dng sequences. Playback oft HD sequences reaches ab out 10 to 15 fps. It's a Windows7/64bit box with 8GB ram, i5 quadcore.
What do you mean DaVinci doesn't support CDNGs? Maybe you should update your software?
Quote from: PhilK on September 14, 2013, 07:17:00 AM
Thanks Levi, this looks good for being the first prototype!
One small thing, can you remove the s from the https in your Vimeo link - it will embed in the forum properly then.
Quote from: Messerjocke on September 14, 2013, 09:21:10 AM
Not true. It runs fine with my ATI HD5670. Allows fluid grading oft ML dng sequences. Playback oft HD sequences reaches ab out 10 to 15 fps. It's a Windows7/64bit box with 8GB ram, i5 quadcore.
Great to hear. Thanks for sharing. ...may have to look into getting that card. Nice and cheap! Thanks again....
Quote from: LEVISDAVIS on September 13, 2013, 06:57:44 PM
50D Prototype Anti-Aliasing Filter Video Test... Available at...
http://youtu.be/0VLn6GzFpzM (http://youtu.be/0VLn6GzFpzM)
Download DNG images and ProRes 422 video of the prototype 50D anti-aliasing filter from Mosaic Engineering at...
https://copy.com/IOqlwsmWUi8i (https://copy.com/IOqlwsmWUi8i)
Thanks so much for posting LevisDavis! I'm soooo excited that they are working on this. I can't wait to buy one! Have you heard Any expected time frame?
Super exciting Levi, thanks for testing and posting. Any idea if this will be as openly available as the others? Really hoping to get my hands on one but haven't been able to get any response out of Mosaic.
I would not go for that card, even if on a budget. GT640 is cheap as well and should perform much better.
Quote from: HHL on September 14, 2013, 02:12:38 PM
Great to hear. Thanks for sharing. ...may have to look into getting that card. Nice and cheap! Thanks again....
@father_v
Nice writeup. I had a shoot recently and used my app "Son of Batch" on a macbook pro to review clips. You can scrub through raw files and make proxies. It's not perfect yet but usable. It was pretty helpful to show the client stuff or to just make sure a tricky shot was in the can. If you're on a mac, check it out:
http://www.magiclantern.fm/forum/index.php?topic=7266.msg61173#msg61173
derkiki
First test with 50D MLV RAW. Dont mind filmed content, it was just to test the feature.
Lots of corrupted frames. Spanned files joined with FSJoiner, then mlv2dng.exe by gnarr (http://www.magiclantern.fm/forum/index.php?topic=7802.0)
DNGs imported into AE CC and exported to DxHD and H264.
Canon 50D
Canon EF-S 10-22mm 3.5-4.5 (no filters)
Transcend 32GB 1000x CF card
Tragic_Lantern_50D109-Andy600.Build.2013Sep08\
Crop Mode 3x - 1472x828 16:9 29.97fps
ML Settings:
Auto ETTR: HalfS
Exp Override; 29;970, Exact FPS
MLV RAW ON, GD on
Don't record GD on... esp on 50D/7D/5DII. Dialog timers should be off too... slowing them down on 50D isn't enough, it can't even do a burst without a lot of corruption. Canon GUI is all love, stealing write speed and ruining frames.
Also, drop your frame rate unless you're really shooting for US TV broadcast and don't use ETTR, set your exposure manually.
Quote from: 1% on September 14, 2013, 08:01:49 PM
Don't record GD on... esp on 50D/7D/5DII. Dialog timers should be off too... slowing them down on 50D isn't enough, it can't even do a burst without a lot of corruption. Canon GUI is all love, stealing write speed and ruining frames.
Tyvm for the input, 1%! I've recorded with GD on in RAW mode, with no problems so far, but i'll keep that in mind for my next MLV test.
I'll do another one on Monday and post results here :D
Quote from: Andy600 on September 14, 2013, 08:08:37 PM
Also, drop your frame rate unless you're really shooting for US TV broadcast and don't use ETTR, set your exposure manually.
Thank you, Andy! I'm about to do a job shooting heavy machinery on this Wednesday.
I need the 29.97 to capture the movements properly and reduce shutter strobering while I move camera.
Also, about ETTR, pardon my ignorance, but how does it affect the footage since it's not on always on mode?
I appreciate all help and input and apologize in advance for noob questions :)
@dodmydog - the ETTR module alters shutter speed and subsequently can lead to very staccato motion. I prefer to have manual control over the shutter. You can limit how slow Auto ETTR will let the shutter go but not how high.
For raw video exposure I set my shutter speed manually and use the raw histogram. I tend to choose an aperture depending on the light and the DOF I want to achieve, then use ISO or a variable ND to push/pull exposure until the green channel is starting to clip then pull back maybe 1/2 - 1 stop (ISO). I get good exposure every time using this method.
You can have GD just better to let the module turn it off while recording. You may or may not get pink framed.
Quote from: 1% on September 15, 2013, 07:35:02 PM
You can have GD just better to let the module turn it off while recording. You may or may not get pink framed.
Quote from: Andy600 on September 15, 2013, 05:16:08 PM
@dodmydog - the ETTR module alters shutter speed and subsequently can lead to very staccato motion. I prefer to have manual control over the shutter. You can limit how slow Auto ETTR will let the shutter go but not how high.
For raw video exposure I set my shutter speed manually and use the raw histogram. I tend to choose an aperture depending on the light and the DOF I want to achieve, then use ISO or a variable ND to push/pull exposure until the green channel is starting to clip then pull back maybe 1/2 - 1 stop (ISO). I get good exposure every time using this method.
Turns out I had a bad Transcend 32GB 1000x CF Card ... it died on the weekend during a shoot.
I cant get it recognized not by camera, computer or laptop.
Is there a way of skipping corrupt frames in AE? I'm still extracting DNGs from shots, but i have a feeling i might have some corrupt frames due this $#$@!$$## card :(
As usual, thx for help
Sorry to hear about your card :(
You can just delete any corrupt DNGs before AE import. It should still load as a sequence. Hope the corrupt frames were only at the start or end of your shots.
I used to work with my Cinema DNGs on Davinci Resolve 9 and graded several projects. After upgrading to R10 all my 50d RAW clips look just black in Resolve. Any ideas to remedy?
Hi guys,
I have a problem that is freaking me out!! I have the latest tragiclantern build and I am using mlvraw... There is one thing that I dont understand, is how to control the shutterspeed!! Its annoying because it looks like it is locked in one defenition! Ive tried all buttons and combinations and i can move from 1/34
There is any thread to explain how this works? or anyone? searched and didnt seem to find an answer... Thank you guys
Hi to all !
I'm discovering RAW with the 50D...AND It is Awesome !!!!!!!!! Never seen something nicer out of a cam...
I had on my 2nd time test shooting 2 problems with the "This ain't a lv_rec RAW file"
First was with a splitted file so I joined them with terminal and it was OK for use with RawMagic
The second is a clip who had "skipped frame"...the 50D just got blocked on the skippinng frame I had to pull out battery.
Then I have a 4,29 .RAW file and a 807ko .R00 file...
I've tried to change the footer with the 4GB one like before on this thread launched by "Shield"...
I just pasted it at the end of the file with Hexfiend...so the file was recognized by RawMagic but it is all purple crazyness !!!!
Am I doing the procedure bad ?
To finish, As I had this skipped frame I wanted to benchmark my Komputerbay x1000 UDMA7 64Go...the 5min benchmark never ends...
The buffer card bench give me results about 43,7MB/s, 40,1MB/s,44,1MB/s, 46,1MB/s (for this value buffer=19371k)
Should I send it back for exchange ?
For all those asking about graphic cards visit netkas.org, also on same subject Blackmagic official support often answer...
Quote from: joaomoutinho on September 17, 2013, 08:54:04 PM
Hi guys,
I have a problem that is freaking me out!! I have the latest tragiclantern build and I am using mlvraw... There is one thing that I dont understand, is how to control the shutterspeed!! Its annoying because it looks like it is locked in one defenition! Ive tried all buttons and combinations and i can move from 1/34
There is any thread to explain how this works? or anyone? searched and didnt seem to find an answer... Thank you guys
You probably have shutter lock on. Check in movie menu > movie tweaks.
If that isn't the problem delete your config files and restart the camera.
Quote from: rommex on September 17, 2013, 06:10:19 PM
I used to work with my Cinema DNGs on Davinci Resolve 9 and graded several projects. After upgrading to R10 all my 50d RAW clips look just black in Resolve. Any ideas to remedy?
Try re-saving the project. If the problem persists re-import the footage.
Quote from: Andy600 on September 17, 2013, 10:39:57 PM
You probably have shutter lock on. Check in movie menu > movie tweaks.
If that isn't the problem delete your config files and restart the camera.
I dont understand this... Sometimes I manage to change the Shuterspeed value, others I dont. Completely random!! the value that it is locked is not 1/34 but 1/27.3
Really driving me crazy as hell
QuoteI just pasted it at the end of the file with Hexfiend...so the file was recognized by RawMagic but it is all purple crazyness !!!!
Am I doing the procedure bad ?
Record another file at the same resolution and frame rate, take the header from that an change the frame count. Does hexfiend show ascii, because everyone is having problems and getting same results when using it. The headers start with RAWM
Guys, I know that the 50D and 5D II do not support eXFat file format. Does the 7D support eXFat file format? . . . I don't have one so I couldn't try it, but I am considering getting one.
Offtopic, but yes. See
http://www.magiclantern.fm/forum/index.php?topic=6215.msg46857#msg46857
Quote from: akumiszcza on September 18, 2013, 12:17:13 AM
Offtopic, but yes. See
http://www.magiclantern.fm/forum/index.php?topic=6215.msg46857#msg46857
Thanks.
Hexfiend (I'm on Mac) has a "text encoding" menu where you can choose ASCII(strict7bit).
It works !!!! 1% you're so great !!!!!
Indeed it works partially but it is my fault... I think I miss something...when you say change frame count it is about duration of the .RAW...?
The converted wrong file (4,29GB) has given the same duration (number of dngs) as the .RAW (1,64GB) that I've taken header from i.e. only 768 dngs from 4,29GB .RAW...
How can I get frame count easely??
My reference file is 1,64GB .RAW file = 768*2,4Mb = 1,87GB DNG folder... ?? my dngs are 1468/824 pix = 2,4Mb
Anyway... I made 4,29/2,4=1865,...
When I tried to have 1865 in hexfiend with 0749...it gave me a 4 785 920 frames in RAWmagic !!!!!!!!! I stopped it when I see strange pics and so I got my 4,91 GB folder with 2012 dngs from 4,29GB.RAW...
I found statman.info that can help for conversion with the same logic as Shield...but not totally...
hexfiend seems NOT to have same logic as Shield for ex
Shield : 9e 08 = 2206 frames /// Hexfiend 9E08 = -25080 /// Stateman.info 2206 = 89e
Shield : 80 04 =1152 frames /// Hexfiend 8004 = -32764 /// Stateman.info 1152 = 480
Anyway...NOW you all know I'm a looser/piece of... with math... :o... BUT I HAVE MY FILE !!!!! 8)
But I'm sure this can help others so I took the right to write...
AND AGAIN 1% ! WITH YOUR HELP AND KNOWLEDGE IT WORKED FOR ME !!!! Please send me a poster of you !
Quote from: vprocessing on September 18, 2013, 01:10:33 AM
AND AGAIN 1% ! WITH YOUR HELP AND KNOWLEDGE IT WORKED FOR ME !!!! Please send me a poster of you !
+1 lol
Quote from: vprocessing on September 18, 2013, 01:10:33 AM
Hexfiend (I'm on Mac) has a "text encoding" menu where you can choose ASCII(strict7bit).
It works !!!! 1% you're so great !!!!!
Indeed it works partially but it is my fault... I think I miss something...when you say change frame count it is about duration of the .RAW...?
The converted wrong file (4,29GB) has given the same duration (number of dngs) as the .RAW (1,64GB) that I've taken header from i.e. only 768 dngs from 4,29GB .RAW...
How can I get frame count easely??
My reference file is 1,64GB .RAW file = 768*2,4Mb = 1,87GB DNG folder... ?? my dngs are 1468/824 pix = 2,4Mb
Anyway... I made 4,29/2,4=1865,...
When I tried to have 1865 in hexfiend with 0749...it gave me a 4 785 920 frames in RAWmagic !!!!!!!!! I stopped it when I see strange pics and so I got my 4,91 GB folder with 2012 dngs from 4,29GB.RAW...
I found statman.info that can help for conversion with the same logic as Shield...but not totally...
hexfiend seems NOT to have same logic as Shield for ex
Shield : 9e 08 = 2206 frames /// Hexfiend 9E08 = -25080 /// Stateman.info 2206 = 89e
Shield : 80 04 =1152 frames /// Hexfiend 8004 = -32764 /// Stateman.info 1152 = 480
Anyway...NOW you all know I'm a looser/piece of... with math... :o... BUT I HAVE MY FILE !!!!! 8)
But I'm sure this can help others so I took the right to write...
AND AGAIN 1% ! WITH YOUR HELP AND KNOWLEDGE IT WORKED FOR ME !!!! Please send me a poster of you !
Why aren't your spanned files named sequencially? See this post, it might help you . . . BTW, that's good to know about using ascii .. .
Also, RAWMagic 1.0 beta 7b will recognize spanned files - so long as they are named correctly. Just drop the spanned files there.
http://theindieshooter.com/2013/09/17/magic-lantern-raw-how-to-merge-spanned-files-using-a-hex-editor/ (http://theindieshooter.com/2013/09/17/magic-lantern-raw-how-to-merge-spanned-files-using-a-hex-editor/)
Shutter problems.
I am having a huge problem controling shutter. It seems like whenever I change the ISO levels the shutter speed gets a different value.
What should I do? Ive already tried to lock the shutter when its in the disired value but as soon as I change the ISO everything is ruined again!
Really frustrated. Anyone had this issue? It is nervracking.
Quote from: joaomoutinho on September 18, 2013, 11:10:50 AM
Shutter problems.
I am having a huge problem controling shutter. It seems like whenever I change the ISO levels the shutter speed gets a different value.
What should I do? Ive already tried to lock the shutter when its in the disired value but as soon as I change the ISO everything is ruined again!
Really frustrated. Anyone had this issue? It is nervracking.
Switch off ETTR and Auto Exposure if they are enabled.
Quote from: Andy600 on September 18, 2013, 11:16:04 AM
Switch off ETTR and Auto Exposure if they are enabled.
They are both off... And I still have the problem. As soon as I change the ISO value, the shutterspeed value changes...
I cant shoot anything because of this problem! Any idea how to fix this? Really anoying and frustrating issue!! >:(
Quote from: joaomoutinho on September 18, 2013, 01:53:15 PM
They are both off... And I still have the problem. As soon as I change the ISO value, the shutterspeed value changes...
I cant shoot anything because of this problem! Any idea how to fix this? Really anoying and frustrating issue!! >:(
Maybe Expo. Lock enable?
Quote from: kichetof on September 18, 2013, 02:31:18 PM
Maybe Expo. Lock enable?
Thank you very much for the help. The problem pressists. I will post pics of my ML settings, maybe that way it will be more easy to track down the problem and get, with your (forum) help, a solution.
(http://s13.postimg.org/powv6w6kz/SDC10149.jpg) (http://postimg.org/image/powv6w6kz/)(http://s13.postimg.org/x7g0fixxv/SDC10152.jpg) (http://postimg.org/image/x7g0fixxv/)(http://s13.postimg.org/sx1cjxsur/SDC10153.jpg) (http://postimg.org/image/sx1cjxsur/)(http://s13.postimg.org/hn8mozntf/SDC10154.jpg) (http://postimg.org/image/hn8mozntf/)(http://s13.postimg.org/gjt3qrsk3/SDC10155.jpg) (http://postimg.org/image/gjt3qrsk3/)(http://s13.postimg.org/7aqxgnjo3/SDC10157.jpg) (http://postimg.org/image/7aqxgnjo3/)(http://s13.postimg.org/47llzjfbn/SDC10158.jpg) (http://postimg.org/image/47llzjfbn/)(http://s13.postimg.org/b20i2yxcj/SDC10159.jpg) (http://postimg.org/image/b20i2yxcj/)(http://s13.postimg.org/q81yg5xzn/SDC10160.jpg) (http://postimg.org/image/q81yg5xzn/)(http://s13.postimg.org/fze2o2zbn/SDC10161.jpg) (http://postimg.org/image/fze2o2zbn/)(http://s13.postimg.org/x2gujlg0j/SDC10162.jpg) (http://postimg.org/image/x2gujlg0j/)(http://s13.postimg.org/pnrir7u4z/SDC10163.jpg) (http://postimg.org/image/pnrir7u4z/)(http://s13.postimg.org/nx8hpqclv/SDC10164.jpg) (http://postimg.org/image/nx8hpqclv/)
Thank you very much on trying to help me with this issue!
Quote from: joaomoutinho on September 18, 2013, 03:17:53 PM
(http://s13.postimg.org/powv6w6kz/SDC10149.jpg) (http://postimg.org/image/powv6w6kz/)
Expo Lock is enable to change Av with Iso ;)
Also expo override has a problem, since it's grayed out (the help text will tell you why).
Hum... I see! Although I have changed this settings (turned both off) and as soon as I change ISO levels the shutterspeed persists to change to... Not a clue on what is going wrong with my camera.
Maybe it is the camera that is bad! But is a canandrum... I have already thought that it was lens fault! Any other idea on solving this? I will try any and everything!
Thank you for being helping me! I am sure that we are going to sort this out!
I am going to post some pics where you can see what is happening... Please pay attencion to ISO an shutterspeed values. This happens every time. Thank you for helping!
(http://s23.postimg.org/mbpwj0wpz/SDC10165.jpg) (http://postimg.org/image/mbpwj0wpz/)(http://s23.postimg.org/624btvbfr/SDC10166.jpg) (http://postimg.org/image/624btvbfr/)(http://s23.postimg.org/oiyqkordz/SDC10167.jpg) (http://postimg.org/image/oiyqkordz/)(http://s23.postimg.org/x2i4ifzqf/SDC10168.jpg) (http://postimg.org/image/x2i4ifzqf/)(http://s23.postimg.org/ikkxag8fb/SDC10169.jpg) (http://postimg.org/image/ikkxag8fb/)
Quote from: a1ex on September 18, 2013, 03:24:09 PM
Also expo override has a problem, since it's grayed out (the help text will tell you why).
I have liveview enabled and it is greyd out... I thought it was supose to be that way! should I reinstall everything? Thank you a1ex
I think I solved it... In the canon menu, when you go to the submenu that activates "liveview mode" the option bellow "liveview" I set it off, and now I can change my ISO without changing the shutterspeed!
(exposure override is not greyd out any more :) )
Thank you a lot guys!!
And the problems never end... I think I got a faulty card from KomputerBay... Going to send it back! :(
When doing the benchmark test on reading/writting, the camera freezes. here are some examples:
(http://s7.postimg.org/d37tb1a07/SDC10170.jpg) (http://postimg.org/image/d37tb1a07/)(http://s7.postimg.org/du54uk1rb/SDC10171.jpg) (http://postimg.org/image/du54uk1rb/)
now its going to be a lot of waitting until I can shoot again =( Although, in h.264 mode VBR mode at -16 it was running normaly. Raw it drops frames past around 1min
hope it helps if you are experiencing this kind of problem...
What build are you using? If it's the latest Tragic Lantern with MLV and RAW recording, make sure only one is in use.
Have you disabled everything in the Canon menu (HTP, Noise Reduction etc etc) and selected a Jpeg setting (not raw)?
How long have you had the 50D and what's it's shutter count? (see debug menu)
I get Benchmark crashes occasionally but not had any problems recording EVER.
P.s. your pics are tiny. I can't make out any info. If you upload more please make them larger but keep them under 900px wide to keep within forum rules. You can also save screenshots using ML ;)
I've had the benchmark time out, doesn't matter. The benchmark != actual speed recording anyway.
Hey guys!
Just joined the 50D club (400$). I have been reading this forum for 2 years now. I have been following the RAW development since the beginning. I read all about it.
My workflow so far: RAWanizer -> AE -> Premiere.
I love the image. I have to get used to image differences, exposing the RAW compared to 550d h.264.
! I think I noticed something interesting !
When importing the DNG's to AE CS6, everything works fine, Camera RAW works perfectly fine.
Then, when I put the footage in 32bit composition (23,976fps), it is usually scaled up/down, due to being 1584xXXX in size. 2:35 aspect ratio. Normal.
Everything was fine so far. Then, I did RAM Preview on full screen and noticed severe aliasing on the edges. I know what causes aliasing (line skipping and shit). Something was odd though. I went back to Camera RAW, and there was almost none aliasing in 100% or 200% preview.
I went back to my composition. When the preview (in normal workspace scenario) is set to "(76%)" or "fit up to 100%" or "fit" it causes aliasing WHICH IS THEN VISIBLE IN FULL SCREEN RAM PREVIEW.
When you switch it to 100% (too big for workspace window) and then go for full screen RAM Preview again THERE IS LESS ALIASING.
So to minimize aliasing in AE CS6, you have to have your preview on 100%. I tested it three times with different footage, same scenario everytime. It seems like Camera RAW preview is almost smooth, then AE goes apeshit with diagonals and sharp edges.
I change composition for 1920, then set 100%, then RAM Preview.
Anybody noticed this?
Peace.
P.S. Still waiting for faster card to try continuous shooting. Then will post some tests (not cats, I will try to edit something of value).
@Mkolaj - Welcome :)
What you describe is just AE previewing. It doesn't affect renders. You can set AE to use better anti-aliasing but can't remember where the settings were and can't get on AE atm.
Can you run only the benchmark code, without any other ML code? I don't think the freezing is normal.
diff -r 5391dcd668f2 src/boot-hack.c
--- a/src/boot-hack.c Wed Sep 18 19:09:38 2013 +0300
+++ b/src/boot-hack.c Wed Sep 18 22:12:13 2013 +0300
@@ -173,7 +173,7 @@
#ifndef CONFIG_6D
#if !defined(CONFIG_EARLY_PORT) && !defined(CONFIG_HELLO_WORLD)
// Install our task creation hooks
- task_dispatch_hook = my_task_dispatch_hook;
+ //~ task_dispatch_hook = my_task_dispatch_hook;
#ifdef CONFIG_TSKMON
tskmon_init();
#endif
@@ -392,6 +392,11 @@
find_ml_card();
#endif
+ load_fonts();
+ exmem_init();
+ card_benchmark_task();
+ return;
+
#if defined(CONFIG_HELLO_WORLD) || defined(CONFIG_DUMPER_BOOTFLAG)
uint32_t len;
load_fonts();
Also, when it freezes, does this happen on read, write or both?
This trick can be used for troubleshooting pretty much any weird bug - when you have no clue where to start looking. If running the code in this way works fine, you can start enabling tasks, prop handlers, GUI overrides and other stuff like that.
Hi all
Thanks for Magic Lantern!
I have my 50D and follwed the instructions how to install Magic Lantern (2.3).
That worked out fine!
Really cool and I could record video - but just at 640xXXX something... I want to record raw, higher resolution.
So I did some more reading - and as I understand there is something called Tragic Lantern.
There is also modules you can add.
So I checked out my CF-card, and I had no modules-folder in my ML directory on my memory card.
So my question is:
Can I just create a folder in my ML-folder called modules and copy in the raw modules in there?
or...
Do I have to figure out how to upgrade my camera to Tragic Lantern?
(I downloaded it but could not get it installed as I did with Magic Lantern)
I have tried the search function but did not find the answer - I guess it is there somewhere....
Thanks again for your hard work!
If you managed to download it just copy the files to your card ;)
If you can't record 1080p H.264 you have no chance of recording raw video. You need a fast card.
Suddenly there are lots of new 50D users :)
QuoteAlso, when it freezes, does this happen on read
Yep, it happens on one of the later reads. The light just stops flashing... 7D/600D/6D/every other camera its ok same code.
Really the read test is kind of a pain... I don't care about read speed with tiny buffers and it takes a while to get to the benchmarks that actually matter.
Read speed may not be important, but freezing while reading from card is certainly not a good sign.
Quote from: Andy600 on September 18, 2013, 09:32:58 PM
If you managed to download it just copy the files to your card ;)
If you can't record 1080p H.264 you have no chance of recording raw video. You need a fast card.
Oh, so it can understand that I have a crappy card at the moment. Cool!
Thanks for your reply!
I will play some more when my better cards arrive....
Quote from: Andy600 on September 18, 2013, 09:36:06 PM
Suddenly there are lots of new 50D users :)
Yes, I just got mine just because of that I found this cool thing. :)
(and a little bit for the reason that I got hold of a cheap 120-300 2.8 Sigma for Canon)
I know I shouldn't post stupid tests, but I do have a question. I see a little flickering on the left, I like that very much (looks more like film frames with subtle exposure differences). I would like to have control over that, because in well lit scenes, nothing like that happens.
Do we know what causes it? So one could use it as an effect?
Quote from: Mkolaj on September 18, 2013, 10:12:42 PM
I know I shouldn't post stupid tests, but I do have a question. I see a little flickering on the left, I like that very much (looks more like film frames with subtle exposure differences). I would like to have control over that, because in well lit scenes, nothing like that happens.
Do we know what causes it? So one could use it as an effect?
Is this h.264 or RAW? . . . You may have the auto Exposure setting "ON" . . .
Quote from: Andy600 on September 18, 2013, 08:47:33 PM
What build are you using? If it's the latest Tragic Lantern with MLV and RAW recording, make sure only one is in use.
Have you disabled everything in the Canon menu (HTP, Noise Reduction etc etc) and selected a Jpeg setting (not raw)?
How long have you had the 50D and what's it's shutter count? (see debug menu)
I get Benchmark crashes occasionally but not had any problems recording EVER.
P.s. your pics are tiny. I can't make out any info. If you upload more please make them larger but keep them under 900px wide to keep within forum rules. You can also save screenshots using ML ;)
Everything is of and Jpeg is the set of the image... I got my 50D used and it has 54K shuttercount.
Should I debug the camera trying different settings? Thank you for the advice!!
Quote
I know I shouldn't post stupid tests, but I do have a question. I see a little flickering on the left, I like that very much (looks more like film frames with subtle exposure differences). I would like to have control over that, because in well lit scenes, nothing like that happens.
Do we know what causes it? So one could use it as an effect?
Hi Mkolaj!
The reason of that flickering effect that you get is produced because you (probably...) have
the "focus peaking" feature activated!...and you are recording
IN H264, NOT RAW, isn,t it?
I´ve noticed that effect myself on mine!
Try to film without this feature to see the effect!
Cheers...
Asier.
This is RAW, I extracted DNG's with RAWanizer and corrected them in AE. I will try to disable focus peaking, but it is disabled while recording.
Quote from: Mkolaj on September 19, 2013, 09:17:58 AM
This is RAW, I extracted DNG's with RAWanizer and corrected them in AE. I will try to disable focus peaking, but it is disabled while recording.
Probably the ACR flickering, don't use shadow recovery or highlight recovery.
http://www.magiclantern.fm/forum/index.php?topic=7571.0
QuoteThis is RAW, I extracted DNG's with RAWanizer and corrected them in AE. I will try to disable focus peaking, but it is disabled while recording.
It is not focus peaking that is causing that fickering in your footage then ...
It sould be what araucaria is telling you.
Cheers...
Asier.
ACR will absolutely produce/introduce flickering. I'd stay away from using fill light and highlight recovery whenever possible.
Also, I too have actually taken a very similar shot as what you posted. Interestingly enough, when exporting from ACR and using .psd I noticed that there was a great deal of additional artifacts implemented into the image. It looked like there was a heat wave in the out-of-focus BG.
If you don't believe me try rendering out say like 1 second of video using .psd and then render out the same 1 second of video using .tif (make sure to use .tif and not .TIF). Kind of a cool thing, right? But, definitely a definitive process that has to be discovered by shooting a great deal of situations and circumstances... So keep on shooting and enjoy.
After a couple weeks of testing the prototype 50D VAF the one thing that stands out the most about this filter is the ability to push the RAW image in post. When aliasing and moiré occurs in your footage the post-production color correction process has a limitation. That is why I decided to acquire a VAF from Mosaic Engineering. Interestingly, what I wasn't expecting to come about, at least so dramatically, was the range of colors that the 50D could handle with the VAF in place.
The 50D aliasing issue causes post-production color correction limitations. It's a factor that must be configured into the color correction process. However, with the limitation seemingly removed, especially during close-ups & mid shots, the images derived from the 50D become far more capable in post-production processes.
For example, when color correcting footage without the VAF I find that my scopes rest in the 50 - 70% legal television chroma-value range before the image proves qualities of aliasing, moiré, and false color. With the VAF in place I regular find myself beyond television chroma-value limits and the image appears to want to go even further without breakdowns in skin tones and other artifacts. This is a very positive attribute that is only derived from a camera that has a lot of flexibility. So as a result, you know, the prototype 50D VAF is proving very valuable to the workflow.
Not to say that everything is totally perfect. There are some additional issues with the filter that need to be addressed. Currently, parfocal lensing is not possible. The VAF negates the user's ability to zoom in on a subject, adjust focus, zoom out from the subject and maintain focus throughout the entire focal distance. However, that is not an issue with prime lensing. I am currently in the process of speaking with Mosaic Engineering to address the filter's performance.
If you follow the link you will be directed to download sample DNG images as well as video footage. You'll notice that the filter eliminates about 85 - 90 percent of the moiré and aliasing in the chroma channels. The luma channels appear to hold aliasing and moiré but the percentage is about 93 - 97 percent eliminated.
https://copy.com/IOqlwsmWUi8i (https://copy.com/IOqlwsmWUi8i)
So what do you think? Would 92 - 100 percent moiré elimination actually take away from detail & texture? Is 100% moiré and aliasing elimination a better solution because the shooter would never have to worry about when and when not to use filters to block moiré and aliasing? Or, would you prefer more texture and detail with the chance of moiré and aliasing in the image?
More or less that is what I'm thinking about the filter right now. The right thing to do will be to post another response after addressing this with Mosaic Engineering. I presume we all want to know just how much of an impact the VAF can make, right? Until then, thanks for reading and enjoy your time.
NEW TRAGIC LANTERN BUILD FOR 50D
I've uploaded a new build of Tragic Lantern for the 50D.
https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
This update features:
Proportional fonts - looks nice! :) (new fonts folder)
Dot-tune and Silent Pics are now modules - remember to load them from the modules menu if you use them.
mlv_rec appears as 'RAW Video (MLV)' in the movie menu. Remember to only have one raw module enabled at any time and MLV is still experimental.
Numerous other fixes, tweaks and module info pages with forum links.
For more detailed information about updates check out the code commits for eveything upto and including this build: https://bitbucket.org/andy600/tl50d/commits/all (https://bitbucket.org/andy600/tl50d/commits/all)
If you experience module linking errors (you shouldn't btw) make sure your modules folder does not contain any older modules. I recommend deleting your current modules folder before updating to this new build.
To install simply copy the contents of the zip to your CF card.
Thanks to 1% for his 50D work and to a1ex, g3gg0 and others for continuing to develop our wonderful Magic Lantern! :)
Awesome Andy600! THANKS!
However, when I went into crop mode it didn't shoot crop. (1600x900 16:9) Or it did, but didn't frame correctly in the preview screen. My subject's head filled the entire screen, but the RAW files shows his head all the way to the right. Is "ML Gray" the best setting for preview? Thanks. And THANKS again!
Quote from: maxotics on September 20, 2013, 01:09:33 AM
Awesome Andy600! THANKS!
However, when I went into crop mode it didn't shoot crop. (1600x900 16:9) Or it did, but didn't frame correctly in the preview screen. My subject's head filled the entire screen, but the RAW files shows his head all the way to the right. Is "ML Gray" the best setting for preview? Thanks. And THANKS again!
Set zoombox to 5xcenter setting. Press the joystick once in non-crop mode and again in crop mode. AFAIK It works as it did previously.
Preview setting is whatever works best for you ;)
I couldn't figure out the Zoombox setting (okay, I had a beer), but pressing the joystick as you suggested did the trick. Thanks again, Andy! Looks really nice and I just want to say again, your posting of stable builds is worth a lot!
As I've offered elsewhere. I have a 50D and an EOS-M. If you need anything tested let me know through PM etc.
Any tips here for desqueezing DNGs before pulling them into Resolve? Or possibly desqueezing in Resolve 10? This would make anamorphic much easier.
Edit: Should've googled. For future reference: http://forums.creativecow.net/thread/277/19768#19782
Resolve has 2x anamorphic settings. If you need 1.33x, 1.5x or 1.7x you can do it in ACR or Raw Therapee.
Quote from: Andy600 on September 20, 2013, 02:33:17 AM
Resolve has 2x anamorphic settings. If you need 1.33x, 1.5x or 1.7x you can do it in ACR or Raw Therapee.
Thanks Andy. Your post and my edit were seconds apart!
Hey Guys.. I've been having a blast with my 50d raw footage. Thanks again!
First, I've just installed the latest Tragic Lantern from Andy600 and I'm using the Komputer Bay 1000x 32gb card.
That said, I'm having a hard time getting a resolution beyond 1920 wide.. I was hoping that by altering my aspect ratio to something like 2.5:1 I could get 1920 wide and beyond and still get 6+sec shots..
Any clues or ideas.. Is there another build I should use?
Quote from: LEVISDAVIS on September 19, 2013, 11:15:12 PM
After a couple weeks of testing the prototype 50D VAF the one thing that stands out the most about this filter is the ability to push the RAW image in post. When aliasing and moiré occurs in your footage the post-production color correction process has a limitation. That is why I decided to acquire a VAF from Mosaic Engineering. Interestingly, what I wasn't expecting to come about, at least so dramatically, was the range of colors that the 50D could handle with the VAF in place.
The 50D aliasing issue causes post-production color correction limitations. It's a factor that must be configured into the color correction process. However, with the limitation seemingly removed, especially during close-ups & mid shots, the images derived from the 50D become far more capable in post-production processes.
For example, when color correcting footage without the VAF I find that my scopes rest in the 50 - 70% legal television chroma-value range before the image proves qualities of aliasing, moiré, and false color. With the VAF in place I regular find myself beyond television chroma-value limits and the image appears to want to go even further without breakdowns in skin tones and other artifacts. This is a very positive attribute that is only derived from a camera that has a lot of flexibility. So as a result, you know, the prototype 50D VAF is proving very valuable to the workflow.
Not to say that everything is totally perfect. There are some additional issues with the filter that need to be addressed. Currently, parfocal lensing is not possible. The VAF negates the user's ability to zoom in on a subject, adjust focus, zoom out from the subject and maintain focus throughout the entire focal distance. However, that is not an issue with prime lensing. I am currently in the process of speaking with Mosaic Engineering to address the filter's performance.
If you follow the link you will be directed to download sample DNG images as well as video footage. You'll notice that the filter eliminates about 85 - 90 percent of the moiré and aliasing in the chroma channels. The luma channels appear to hold aliasing and moiré but the percentage is about 93 - 97 percent eliminated.
https://copy.com/IOqlwsmWUi8i (https://copy.com/IOqlwsmWUi8i)
So what do you think? Would 92 - 100 percent moiré elimination actually take away from detail & texture? Is 100% moiré and aliasing elimination a better solution because the shooter would never have to worry about when and when not to use filters to block moiré and aliasing? Or, would you prefer more texture and detail with the chance of moiré and aliasing in the image?
More or less that is what I'm thinking about the filter right now. The right thing to do will be to post another response after addressing this with Mosaic Engineering. I presume we all want to know just how much of an impact the VAF can make, right? Until then, thanks for reading and enjoy your time.
Thanks for this thorough review and samples. I think so far it's pretty good. It's hard to say if just a bit more of an aggressive filter in order to get rid of the Moire even more would be too much. I think right now it would be adequate the way it is for most situations, but some people really want to get rid of the colored Moire more than anything. IMO the detail still looks adequate and i'm sure with a bit of sharpening the image would be great.
Do you know if they're going to tweak their formula just a bit more or leave it as is?
Many thanks for the feedback on this Levi!
I've not got time to dive into the files before work (thanks though) but how close to Production quality is it do you think?
All picture taking things appear broken today, don't let it surprise you. I think its from silent pic becoming a module. Tested on 6D/7D/600D
Quote from: Andy600 on September 20, 2013, 12:39:41 AM
NEW TRAGIC LANTERN BUILD FOR 50D
I've uploaded a new build of Tragic Lantern for the 50D.
https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
Great! I've been waiting for this build. But not because of the things you've mentioned, but auto ettr/dual iso link (I hope it's included). See: AETTR + DUAL ISO: The Ultimate Automated Perfect Image Exposure-Beginners'Guide
http://www.magiclantern.fm/forum/index.php?topic=8322.msg76355#msg76355
Auto snap and always on modes don't work on nightlies, but work on tragic lantern. I can't wait to test the new build on the weekend. Thanks!
IMPORTANT
The last build (Sept20th which is now deleted) had a small bug that may have affected photo functions.
Download the fixed one: https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
In last TL build (corrected) if I try to load script.mo all modules fail to load with Err - Linking failed.
The build maintainers should probably try the modules before publishing them ;)
Yep, my bad. I forgot to try that one as I never use it. I'll remove it from the build when Bitbucket lets me. ::)
We still have problems with centering in crop mode.
For the test:-
I centered the image by pressing the joystick in non-crop mode then entered crop mode. I then pressed the joystick again to snap to center and moved the camera until the cross was in center of the spot focus box.
I shot a couple of seconds at 2000x1080, 1920x1080 and 1920x818 (2.35:1) - repeating the centering process for each size.
I loaded the largest frame into photoshop and found dead center with the rulers, then drew a green cross.
I then loaded the other frames and positioned them relevant to the center of the canvas.
You can see that as frame width increases the offset pushes the recordable area further left so that the cross used for centering the camera moves to the right.
The frames with 1080 px vertical resolution also shift the recordable area up so the cross is moved down. This offset decreases with the 818 px height frame which shows there is a percentage based offset at work but the calculation is not yet correct for true (or nearly true) centering.
(http://i.cubeupload.com/kxehIX.jpg)
The image is 1:1 but has been cropped from 2000 x 1080 to show only the center portion.
This has implications for correct framing but having true vertical centering is vital when shooting with anamorphic lenses in crop mode.
Hi Andy!
I´ve installed the last Tragic Lantern Build you recomended and checked the MLV and RAW video modules, as well as Dual Iso ETTR etc..
Then I tryed to go to the menus but they are not there! ie, RAW video and Dual Iso are not there! they´ve dissapeared? or what...??...
Thanks for your great work!
Asier.
Hey!
I finally got all desired modules loaded correctly! :-)
Thanks and cheers!
Asier.
in a time crunch and didn't have time to search... when I recorded my first 30 second clip all I had in the dcim folder was a MVI (MOV) file. no raw files. What did I do wrong? please help. I have a huge project coming monday, the help will be much appreciated.
Quote from: Asiertxu on September 21, 2013, 12:58:09 AM
Hi Andy!
I´ve installed the last Tragic Lantern Build you recomended and checked the MLV and RAW video modules, as well as Dual Iso ETTR etc..
Then I tryed to go to the menus but they are not there! ie, RAW video and Dual Iso are not there! they´ve dissapeared? or what...??...
Thanks for your great work!
Asier.
I think better not enable both mlv and raw modules. And disable, or even remove, script.mo.
Quote from: DonJuan on September 21, 2013, 08:09:27 AM
in a time crunch and didn't have time to search... when I recorded my first 30 second clip all I had in the dcim folder was a MVI (MOV) file. no raw files. What did I do wrong? please help. I have a huge project coming monday, the help will be much appreciated.
It looks like you didn't enable raw video in movie settings (at the bottom). Default is h264 mov, if you just enable video recording. Old module creates .raw (and .r00 etc.) in DCIM folder. New module creates .mlv files in root directory of CF card.
Hi akumiszcza!
Thanks alot for your input mate!
I got all modules loaded because of sissabling that script.mo in the last try, that appears to
be causing all the rests modules not been loaded...
I got MLV.mo, RAW.mo loaded together after removing script.mo... as well as the rest such as ETTR, DualIso etc...
I´ll remove from my CF card that script.mo as you sugest!! :)
Thanks again for your help!
Cheers.
Asier.
@1% - Sorry, I know this is a total PITA but I'm trying to work out the crop centering issue because I'll need it accurate for shooting anamorphic soon.
I've been playing with the gap settings as per the code (below). The center of crop framing that is visible in Live View (using snap to 5x) is fairly accurate to what is recorded (although it's still offset by about 20px in X/Y) but the sensor area being recorded is to the left of the sensors physical center. Any ideas how to snap to its physical center?
/* be careful not to change the raw window */
int gap_left = (raw_info.jpeg.width - vram_hd.width) / 2 - delta_x;
int gap_top = (raw_info.jpeg.height - vram_hd.height) / 2 - delta_y;
int gap_right = (raw_info.jpeg.width - vram_hd.width) / 2 + delta_x;
int gap_bottom = (raw_info.jpeg.height - vram_hd.height) / 2 + delta_y;
if (gap_left < 0) delta_x -= (0 - gap_left);
if (gap_top < 180) delta_y -= (180 - gap_top);
if (gap_right < 0) delta_x += (0 - gap_right);
if (gap_bottom < 180) delta_y += (180 - gap_bottom);
Hi, I switched my 550d for a 50d with KBay 1000x 64GB
First test today with 20sept bugfix build. So much has changed last few months.
I just tried cropzoom 1920x1080 21-23.976 fps
At one point I had a pretty long run 23.976 1080p at 80.6 MB/s
But later on it couldn't continue so I dropped to 21fps
loaded only: MLV, ETTR, Dual iso (set to 100/800)
comments:
- nice new fonts
- MLV and ETTR modules and liveview AF conflict on 50D. I can't run ETTR on set and use halfshutter to start video. With ETTR to set, it also starts on half shutter. I also loose AF in liveview because of the halfshutter. Both half shutter and * start video and both halfshutter and set start ETTR.
- My tamron 11-18 seems accurate framed in hacked cropmode, the 5x zoom display from canon was off when pressing INFO.
The 1080p output is by far the best i've had from canon footage. Great work guys!
Welcome to the 50D club Bart :)
Andy what lens have you in mind for anamorphic shooting? I have a sankor 16c and a Isco Ultra Star projection lens. The sankor has a nice touch but for crop mode the sharpness of the Isco is much better.
Is there a huge benefit shooting with Dual ISO on ? i have it enabled but don't really see much difference in dynamic range
would there be any extra post processing to be done to achieve better picture quality in ACR..or it's all camera ?
Quote from: araucaria on September 21, 2013, 01:38:33 PM
Andy what lens have you in mind for anamorphic shooting? I have a sankor 16c and a Isco Ultra Star projection lens. The sankor has a nice touch but for crop mode the sharpness of the Isco is much better.
I have bought one yet. I found a cheap SankorF which doesn't have rear threads but after a lot of reading and watching videos I can see it's a bit soft. I'll try to get an Isco if I can find one cheap enough but as you know, the prices are a bit crazy atm. I'm watching eBay to see what comes up.
Have you had any framing issues? I assume that it's pretty important for the crop area to be inline with the center of the lens because of the way anamorphic lenses bend the image. I can imagine weird things happening to the image if the crop is offset.
Quote from: leojames on September 21, 2013, 01:40:15 PM
Is there a huge benefit shooting with Dual ISO on ? i have it enabled but don't really see much difference in dynamic range
would there be any extra post processing to be done to achieve better picture quality in ACR..or it's all camera ?
Yes, in some situations. See the Dual ISO thread ;)
I assume you already know it doesn't work for video on the 50D?
Thank you Andy
is this the link ?
http://www.magiclantern.fm/forum/index.php?topic=7402.25
Quote from: Andy600 on September 21, 2013, 01:58:53 PM
I have bought one yet. I found a cheap SankorF which doesn't have rear threads but after a lot of reading and watching videos I can see it's a bit soft. I'll try to get an Isco if I can find one cheap enough but as you know, the prices are a bit crazy atm. I'm watching eBay to see what comes up.
Have you had any framing issues? I assume that it's pretty important for the crop area to be inline with the center of the lens because of the way anamorphic lenses bend the image. I can imagine weird things happening to the image if the crop is offset.
I havent tried it again, I did one month ago and it was almost impossible, specially because in greyscale mode you can't move the window once you zoomed in. Haven't tried the latest builds because I've been busy. If I find a nice cheap projection lens I'll let you know, but remember they don't have the nice touch of the sankor. If you found a good deal on a sankor go for it. The sankor 16f has a small rear. (I consider a good deal if its sub 100€) But yes, the sankor for crop mode is not such a good idea.
Quote from: leojames on September 21, 2013, 02:03:22 PM
Thank you Andy
is this the link ?
http://www.magiclantern.fm/forum/index.php?topic=7402.25
Some good examples there but this is the main thread: http://www.magiclantern.fm/forum/index.php?topic=7139.0
Quote from: araucaria on September 21, 2013, 02:11:06 PM
I havent tried it again, I did one month ago and it was almost impossible, specially because in greyscale mode you can't move the window once you zoomed in. Haven't tried the latest builds because I've been busy. If I find a nice cheap projection lens I'll let you know, but remember they don't have the nice touch of the sankor. If you found a good deal on a sankor go for it. The sankor 16f has a small rear. (I consider a good deal if its sub 100€)
Hmm, that's not good :( I doubt anything can be done about preview modes and if there is no fix possible for centering the crop area to the sensor using the current algorithms it might need something hardcoded purely for anamorphic use. Not sure how to do it.
sub 100€? I'd love to find one for that kind of money :D The one I found is about 220€ but it's in good shape (apparently). I figured I could use a Vid-Atlantic clamp but I'm a bit worried that the rear of the Sankor might come into contact with my taking lens and scratch the glass.
I guess I'll need to get a monitor too... and rails etc :-\
Thanks btw. If you do see something cheap lemme know. I'm steering clear of the larger projection lenses to keep things as small as possible.
I should probably just bite the bullet and get this 2x Isco from Vid Atlantic http://vid-atlantic.com/lensshop.html (http://vid-atlantic.com/lensshop.html) - at least they throw in a clamp LOL
I paid 100€ for that lens 3 weeks ago (the isco, my sankor was 150€ because I didn't want to wait). Anyway, if you are planning to use it in crop mode, I don't think it's worth the trouble (honestly) because on crop level there is a lot of noise and when you stretch it gets very noticable. It's also very hard to focus perfectly. Here is a quick sample, 28mm 1.4 lens @ f 5.6 with isco ultra star 2x shot at 1920x1080, overexposed to the max to get the noise out, and desqueezed streching horizontally. You can see its not easy to get good focus, the unstreched image looks fine but when you strech it you can see the focus errors pop out a lot.
(http://farm8.staticflickr.com/7416/9854477266_a927ed9acb_o.jpg)
@araucaria I'm coming to the same conclusion with everything I've tried on my 50D and EOS-M.
However, there is still a high-dynamic range look that I can't duplicate with H.264. As I try to get wide without moire in crop mode I lose resolution. I just came back from shooting some test footage on an EOS-M using a 22mm with a .20 wide angle adapter. Getting focus was very difficult. I'm so close to quitting this ML RAW stuff :(
But that film look! (God this is killing me). Araucarai, do you think you can get it shooting H.264, natively, or using ML hacks, to get better dynamic range?
Or do you feel the tradeoffs you mention just aren't worth it!
Or maybe, despite all those drawbacks. this is still a setup that is worth the film look?
I suck at grading h264, I come from still photography and I am totally spoiled with raw, thats why I like ML raw. I have only nikon lenses (as I am a nikon shooter) and don't have Autofocus with them on the canon. If I had autofocus I think things would be a lot easier (not with double focus anamorphic but with the rest).
Since I don't do this as a Job I will just wait a year or more and see what happens (or if I get some spare money I'd just get a mk iii, and sell it when something better comes along), meanwhile I will deal with the 50D and it's problems (and pray for nikonhacker to get me raw video on the D800 and say goodbye to canon).
Anyway, I think 50D footage without crop shot trying to avoid moire and correcting it later in AE looks better than anything else we had in the amateur world before BMCC and ML RAW, So you can do a lot of things for the web, youtube and vimeo destroy your stuff anyway. And you can even make a small film with it, your audience won't notice, people watch screeners and xvid videos con 50" screens...
Maybe I'm seeing things, but even the RAW I put on Vimeo and show on our TV through Roku has a more film-like look than I can get with any H.264. I don't think it's grading skills. The color depth is just not there. I can flatten the image. I can add film-like grain. It just looks phony to me. Faces are either white, yellow or orange. BTW, I have a D600. Great still camera. I too wish it had RAW, though I can't expect much since it write SD card only.
Yes, h264 colors are very limited, I was refering to the problems of the 50D with aliasing and moire, they are a big deal, but hey, we are not doing hollywood stuff... Good color on the other hand is very important because it gives you the freedom to do what you want, even if it has some artifacts.
In h264 there is also compression, which gives turns some nice motion blur into something sturreing and ugly, shadows detail is a no go, not because noise but because of gigantic compression artifacts.
As for the nikons, I wish they had 10bit output over hdmi and a nice log-c curve, that would be enough. They certainly have the processing power but nikon is just too lazy (or handcuffed by sony).
@araucaria thanks for heads-up and the pic. You got that lens for a steal of a price :D
Just out of curiosty, why did you shoot 1920 and not something closer to 1440 x 1080? Just wondering if that would change any of the characteristics of the unsqueezed imaged.
I'm a bit puzzled too about the noise you mentioned as it's still capturing pixels in crop and non-crop but one has skipping. Are you saying that lineskipping actually looks better than 1:1 crop video? ???
Quote from: Andy600 on September 21, 2013, 06:41:48 PM
@araucaria thanks for heads-up and the pic. You got that lens for a steal of a price :D
Just out of curiosty, why did you shoot 1920 and not something closer to 1440 x 1080? Just wondering if that would change any of the characteristics of the unsqueezed imaged.
I'm a bit puzzled too about the noise you mentioned as it's still capturing pixels in crop and non-crop but one has skipping. Are you saying that lineskipping actually looks better than 1:1 crop video? ???
Not really, the only diference is that the noise in lineskipping looks more static to me (I refer to normal luminosity noise, not with high isos and darkness).
Shooting at 1440x1080 looks exactly the same as if you crop the sides of the fullhd. The lens streches everything 2x in the wide, so if you shoot @ 500x1080p you will get 1000x1080p, but that image is exacly the same as if you shoot full 1920x1080p, stretch it to 3840x1080 and crop the sides to 1000. Yeah lol.
re: stretching - Of course, that makes sense ;D Thanks.
Well it squeezes und you just stretch it in post to unsqueeze ^^
I don't have modules listed anywhere. image effects is the last option in movie mode. first option says movie record and 1920x1080 30fps. I don't see anything anywhere that says rew video
Quote from: DonJuan on September 21, 2013, 10:07:28 PM
I don't have modules listed anywhere. image effects is the last option in movie mode. first option says movie record and 1920x1080 30fps. I don't see anything anywhere that says rew video
What build/version of ML are you using then? For raw video on 50D get nightly (http://builds.magiclantern.fm/#/) or even better Tragic Lantern builds (https://bitbucket.org/andy600/tl50d/downloads - don't enable script.mo module in last build).
Is there any detailed explanation of the shooting and conversion process with MLV?
i tried tragic lantern and it was even more confusing. I didn't find anything that let me enable raw video. I have a 50d with a shutter count of less than 200. (I got lucky) however I am not gfetting lucky with the raw video. I have a udma7 1000x 64gb card.
Quote from: DonJuan on September 22, 2013, 06:27:22 AM
i tried tragic lantern and it was even more confusing. I didn't find anything that let me enable raw video. I have a 50d with a shutter count of less than 200. (I got lucky) however I am not gfetting lucky with the raw video. I have a udma7 1000x 64gb card.
Read first post here and RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST
http://www.magiclantern.fm/forum/index.php?topic=5520.msg37597#msg37597
You are probably missing some step in installation. Normally you just enable module, restart and set raw video up.
I need some help.
What I want is everything off except for mlv module and digic zebras highlights, histogram with ETTR hints, shortcuts ISO,tv,av
With these settings I want to do 1920x1080 crop at 21fps.
problem.
I can't set exposure. shutter and iso change very little in liveview while the canon top lcd changes iso/shutter in predictable steps. I don't see any change in liveview and can't compensate for ETTR hints. Aperture seems to change the number displayed in liveview but I don't see any change in picture brightness or ETTR hints.
What is wrong? I got the Fn functions all to 0 and the display still reports 'ALO NEUTRAL', I can't set exposure simulation 'ON'
Are you sure you have turned off ALO in the Canon menu?
Maybe also check Live View function settings in the Canon menu too.
I set up everything on C1 using Manual (M) as a base then with C1 selected I made all my changes (disabled everything in Canon menu) and resaved.
I am in M mode and used the "clear all Custom Func" an delete magic.cfg.
just at clean startup and no modification I press 'func' for ISO and it goes from 100 160 eq100 and stays on eq100
Weird :-\
and you definitely haven't got ETTR or Auto Exposure modules on?
Does the Clear all custom func disable HTP, ALO, ISO NR etc?
BTW @bart - Why 21fps?
I see you're using the same card as I have and it 'can' do continuous at 1080p/24p. You need to use raw_rec, not mlv_rec and might need to disable dialog timers (only in Tragic Lantern). I've filled my card a couple of times to test. Some users report differing writing speeds with the KB 64gb 1000x so it might not show 'continuous' in the info bar but you should still get decent recording times from it.
Quotejust at clean startup and no modification I press 'func' for ISO and it goes from 100 160 eq100 and stays on eq100
There is no manual movie mode in reality, you need expo override. None of the controls really apply to LV, only photos.
Quote from: Andy600 on September 21, 2013, 12:09:29 PM
@1% - Sorry, I know this is a total PITA but I'm trying to work out the crop centering issue because I'll need it accurate for shooting anamorphic soon.
The only way to do this is via ADTG/CMOS registers.
Quote from: 1% on September 22, 2013, 07:14:53 PM
There is no manual movie mode in reality, you need expo override. None of the controls really apply to LV, only photos.
ok Thanks, i'll try that
Quoteauthor=Andy600 BTW @bart - Why 21fps?
over 22fps I get these heating warnings. I did get some 1080p24 footage but dropped back to 21fps. I first need to figure out the basics and go from there. My first cropzoom landscape at 11mm looked pretty great.
I want to use 1080p crop just for extreme contrast situations (pitty about the dualiso in video, but it's great in plain raw too)
Then I want to do some tiny cropzoom macroshots with rackfocus and digital dolly. Maybe rack from one tiny mushroom to another all raw with strong backlight where they get transparent.
I'll post some samples as soon as I've got the basics right.
Hi A1ex
Good to see the warning is working... it can be falsely triggered if you select not exact FPS and 22 FPS, have to fix that.
Quote from: 1% on September 22, 2013, 08:12:32 PM
Good to see the warning is working... it can be falsely triggered if you select not exact FPS and 22 FPS, have to fix that.
Well they are gone with these setting: They work fine
- Camera on M mode with all Fn functions disabled
- Only one module enabled: raw_rec
ML enabled functions
- Exposure override
- Shortcuts iso/kel, av/tv
- Global draw on: but off while recording (in RAW submenu set to "off" to work)
- zebras, histogram with ETTR hints for best exposure choice
- movie record 1920x1080
- REC key: half shutter
--FPS override 23,976
- RAW video on 1920x1080
- Dialog timers: disabled
Now I can do 1920x1080@24p(23.976) in cropzoom at around 80-81MB/s on a Komputerbay 64GB 1000x
Hope this helps other to get is working.
From these settings you can try other stuff. This just works.
Oh one thing. Which shutter should I believe: The one in ML liveview that increased in very small increments or the shutter speed on the top LCD that progresses much faster?
When the liveview shutterspeed is at 1/100 the top lcd is 1/500.
[EDIT]found answer through ADTG search: it's the liveview shutter. The top one is for photomode (1%)
Those don't match LV and ADTG shutter didn't fix FPS limits.
RE: the VAF filter - it's just a prototype from mosiac? Can they improve it further? I said on the video comments that the moire banding is reduced but present.. I would much prefer it all removed if possible.
RobertGL:
Mosaic is reviewing the footage and will be in contact shortly. We are playing phone tag the last couple of days in order to properly view footage... I think they are attempting to completely eliminate moire and aliasing all together. But we'll know more this week... (I'll post another update too)...
I'm thinking to go back to the same location on Tuesday and fire off some shots to see just how prevalent the moire and aliasing are under different filters... Will post some results later this week.
Went back to magic lantern. Latest TL kept crashing my 50D and i had to take the batteries out whenever I enabled MLV raw or went to live view with raw video on. Camera just freezes.
Quote from: johansugarev on September 24, 2013, 12:20:34 AM
Went back to magic lantern. Latest TL kept crashing my 50D and i had to take the batteries out whenever I enabled MLV raw or went to live view with raw video on. Camera just freezes.
Hmmm ??? It's working ok here. The only time I've had to pull the battery has been when playing with ADTG registers.
Does the edmac 04 change help... I seem to be writing faster. It also seems to get up to speed better.
Quote from: 1% on September 24, 2013, 01:53:36 AM
Does the edmac 04 change help... I seem to be writing faster. It also seems to get up to speed better.
Just posted on the commit. Seems ok but then speed drops after a few shots.
Are you getting any corrupt frames with mlv? I'm getting them intermittently whatever the frame size.
Could Edmac selection be made selectable in the module temporarily to avoid recompiling?
Its unfortunately in the bin itself.
Corrupt MLV pre/post change? Seems OK here but probably needs more testing.
2000x1000 is continuous for me after 2 records and no corrupt frames in raw. I can't play back the MLV in camera so can't check it for frames. Digic Peaking off/timers off. 23.976/24 frame rates.. 25P isn't so lucky.
No worries. I compiled a bunch of bins with different edmac settings so I could quickly swap them. To me, it looks like #3 is best, #4 works but I think it's marginally slower and does slow down them more the card fills (not sure if that's related though). Is Reslock linked to #7? because I get a "Reslock failed' error.
The mlv corruption was before and after the change. I've tried different cards, different resolutions etc but get random corrupt frames. It's only 1 - 3 frames that are screwed but if they happen in the middle it ruins a take.
I don't have any corrupt frames with raw_rec so I guess it's just the metadata being written during shooting that's causing the corrupt frames?
So 3 was the best for you? Weird, I tested 3 again and 4 still seemed snappier. Maybe need a larger sample.
Resloc failing means the edmac is used.
Yes. I haven't tried with Digic peaking off. Will give it another go with edmac 4.
I'm using g3gg0's mlv player to test.
That peaking is cool but from exp... EOSM = locked H264, 7D = 3-4MB+ off write speed. I should really make it turn off on rec.
I was playing back 7D files with the player today and noticed frame 2 got hit alot, have to record some smaller files on 50D and check.
Tried #4 again and still think #3 is better. #3 seems to have a more stable write speed, only varying +/- 1mb or so. #4 does seem to get up to speed a bit quicker but it fluctuates. Tried it in movie mode and photo mode.
Still getting corrupt mlv frames with Digic peaking off and timers disabled.
I'll try again tomorrow. Need some zzzz's
BTW - check out this ADTG reg http://www.magiclantern.fm/forum/index.php?topic=6751.msg77975#msg77975 (http://www.magiclantern.fm/forum/index.php?topic=6751.msg77975#msg77975) - does very weird things, like dual resolution or something.
There needs to be an edmac speed test or something with error checking... add an invalid edmac and the speed goes up but you're writing empty/dead frames.
mlv is a nice too have, but not something stopping us from making great movies :)
Something that would really help me (and probably others) is to have a toggle to (always) enable image stabilization (canon IS) while recording. Right now I have to keep the shutter button half pressed, but I need my hand for other things actually :P
Quote from: savale on September 24, 2013, 01:39:57 PM
Right now I have to keep the shutter button half pressed, but I need my hand for other things actually :P
Enable Sticky Half Shutter
I can't find an answer for the following question:
What is the status on dual_iso video on 50d?
My primary use of the 50d is crop raw video in situations with a strong backlight. I love those shots and dual iso can push the limits even more. Otherwise dualiso in timelapse is great too, but can't handle moving subjects like video.
Quote from: bart on September 24, 2013, 02:48:16 PM
I can't find an answer for the following question:
What is the status on dual_iso video on 50d?
My primary use of the 50d is crop raw video in situations with a strong backlight. I love those shots and dual iso can push the limits even more. Otherwise dualiso in timelapse is great too, but can't handle moving subjects like video.
It only works for stills on the 50D.
Hi Andy,
I knew about the photomode. And of course the latest build is the latest build. I'll just stick to exploring the latest build properly, before asking any more questions.
Did a quick test with the latest ML TL build. Seems fine for me
thanks
Rolfe Klement
creativesunshine
Card benchmark seems to be working in play mode:
Test 9 is commented out:
//~ card_benchmark_wr(128*1024, 9, 9);
EDMAC3 vs 4
http://imgur.com/a/luL1Q
Little update on latest TL... Recorded 23 GB no corrupt frames on Raw_Record... Super stable User Interface.
Been reading a lot about the MLV_Rec module, particularly about the corrupt frames... With the latest TL build and the last build I noticed in 5x zoom, Canon Live View setting not Hacked or ML Grayscale, that there was an intermittent corrupt frame (about 5 frames into the 5X zoom mode). Perhaps the corrupt frame issue is somehow tied into this phase of the 50D's pipeline?
Seems to happen at least once on every shoot after the camera has been on for some time. Thinking that if I see this again to immediately record in 5X mode as a means for testing the module/pipeline...
Quote from: 1% on September 24, 2013, 06:44:39 PM
Card benchmark seems to be working in play mode:
Test 9 is commented out:
//~ card_benchmark_wr(128*1024, 9, 9);
EDMAC3 vs 4
http://imgur.com/a/luL1Q
Is the top image Edmac 4?
EDMAC is not used in playback mode at all ;)
40D's autoload.bin isn't work...... when I updata ML_40d111.fir (30.Aug version)...It goes black ,but just can foucus without shotable.... How can I solve it?
QuotePerhaps the corrupt frame issue is somehow tied into this phase of the 50D's pipeline?
Some checks are taken out in MLV by g3gg0 and you get the corrupt frame sometimes when it writes the meta data.
QuoteEDMAC is not used in playback mode at all ;)
Yea, should be full theoretical speed. I'll try in LV, make sure it doesn't stop.
Still dying on read test in LV :(
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x308): undefined reference to `exmem_init'
boot-hack.c:(.text+0x310): undefined reference to `card_benchmark_task'
I tried only running the benchmark, cofig_early port compiles but doesn't do anything.
Quote from: LEVISDAVIS on September 24, 2013, 06:46:01 PM
Little update on latest TL... Recorded 23 GB no corrupt frames on Raw_Record... Super stable User Interface.
Been reading a lot about the MLV_Rec module, particularly about the corrupt frames... With the latest TL build and the last build I noticed in 5x zoom, Canon Live View setting not Hacked or ML Grayscale, that there was an intermittent corrupt frame (about 5 frames into the 5X zoom mode). Perhaps the corrupt frame issue is somehow tied into this phase of the 50D's pipeline?
Seems to happen at least once on every shoot after the camera has been on for some time. Thinking that if I see this again to immediately record in 5X mode as a means for testing the module/pipeline...
I have raw_record 1920x960 5x crop fully stable when used in conjunction with "Hacked: No Global Draw" option. I can fill up the card with no skipped frames.
;)
Quote
boot-hack.c:(.text+0x308): undefined reference to `exmem_init'
boot-hack.c:(.text+0x310): undefined reference to `card_benchmark_task'
Remove the static keyword.
Quote from: Stedda on September 24, 2013, 02:32:00 PM
Enable Sticky Half Shutter
Wait, does this feature means I get constant automatic Image Stabilisation on my lenses (OIS) without the need to have the button half pressed? Since when is this part of ML?
tnx
Quote from: Stedda on September 24, 2013, 02:32:00 PM
Enable Sticky Half Shutter
Unfortunately it doesn't help. I enabled the 'Hold during REC' function but still need to keep shutter button half pressed. I tried it on 18-55mm IS II & 55-250mm IS II result is the same. What did I do wrong? Anyone can help me with this?
ML Version: Andy600.Build.2013Aug18.50D109
Off topic: I'm new one on forum but followed this thread for a long time. Anyway I would like to thank everybody who support and help in development of Magic Lantern. You are my heroes :)
Hi there.
For the past days I have been working with the TragicLantern before this new build... It get a little bit time to get used and to get to know how to role everything and make it work as I intended.
So, from my experience, the RAW_REC failed on me in 4 clips, near the beggining of them (20/s aprox). Dont know what it was. Just turned the camera off and started everything again. I got less of this when I taked out the overlays. This is what I have done - Made 4 different overlays, one with histogram, other to focus peak, other to vectorscope and one with nothing. After I stablished the shot, runed the RAW_REC in the "virtual display" that had nothing to it.
Another thing, didnt got used to the ETTR histogram just because I couldnt "read it". I am now reading about it and I am getting familiar with this right now.
The MLV_REC I still dont know what it is and what is offering, so I just stick to the "old" RAW_REC...
In the new version of TragicLantern (that I just downloaded now) is there something that you guys advise to be careful with or to use a lot?
Only one more thing, and I dont know if I am being too noob - There are going to be new cards with increased speeds. Do you think that is going to be possible to have "full hd" or higher framerates with this new cards?
Thank you very much .
Hi,
I've spent a lot of time reading into the 50d and this is what is know so far that might help you.
RAW options for 50d are limited and most of them can already be achieved with a Komputerbay 64GB 1000x.
RAW limitations for 50d
FPS
The camera offers only 1080@30p which means framerate can NOT go faster than 29,97fps. Even with a 150000x CF
RESOLUTION
- normal shooting mode 1584x1058. This is an absolute limit and horizontally roughly 1/3rd of the photo resolution
- cropmode: uses the center of the sensor and is limited to 2000x1080
One very important setting is: [Global draw off while recording]
This is found in the RAW video submenu and the "off" setting makes it work
This setting disables all overlay functions at once (zebra, peaking, histogram etc) to put all resources to writing proper frames to the CF card.
So most RAW functionality is already possible except for framerates between 23.976 and 29,97.
I would advice to accept these limitations and make the best of them. Andy600 clearly showed a while back in this topic that you can shoot gorgeous footage with this camera at both 1584x and 1920x resolutions.
So good luck
Yep, unless something magic happens, this is as far as it will go. What has been achieved is huge, now go and film actual stuff :p
Quote from: bart on September 26, 2013, 09:08:52 AM
Hi,
I've spent a lot of time reading into the 50d and this is what is know so far that might help you.
RAW options for 50d are limited and most of them can already be achieved with a Komputerbay 64GB 1000x.
RAW limitations for 50d
FPS
The camera offers only 1080@30p which means framerate can NOT go faster than 29,97fps. Even with a 150000x CF
RESOLUTION
- normal shooting mode 1584x1058. This is an absolute limit and horizontally roughly 1/3rd of the photo resolution
- cropmode: uses the center of the sensor and is limited to 2000x1080
One very important setting is: [Global draw off while recording]
This is found in the RAW video submenu and the "off" setting makes it work
This setting disables all overlay functions at once (zebra, peaking, histogram etc) to put all resources to writing proper frames to the CF card.
So most RAW functionality is already possible except for framerates between 23.976 and 29,97.
I would advice to accept these limitations and make the best of them. Andy600 clearly showed a while back in this topic that you can shoot gorgeous footage with this camera at both 1584x and 1920x resolutions.
So good luck
Thank you very much for the advice. I think it will help a lot of users! I had already a LV "screen preset" on the 4th screen to have the global drawn off... I have the "first" LV screen to see the ETTR values (histogram) and the spotmeter (raw, afbox), the "second" LV is for Waveform and Vectorscope, the "third" LV is for focus and exposure with zebras (RAW) focus peak (0.6, Local, strong edges, low res, alpha blend) and MagicZoom (+mode) - I am having some issues with this last option. Need to close and open the LVmode in order for this to work...
I cant get continuos video if i am in 3:2 AR and 1584X1058 Res... This would be a nice little bit higher res to work with continusly, thats why I have talked about the speed of the new cards and if they could unlock the camera just a little bit further!
Do you use the Flaat Picture style modes that are referenced in the MagicLantern Manual? I will give them a try. Not sure what they do but I will test them out.
And one more thing, I find it dificult to have a organized shooting plan. Is there any feature to change the name of the clips, IN camera? That would be a really nice feature to have a better workflow.
I get lost with all the clips. I have a pen and a paper, but in a more "professional" workflow, it would be really nice to add this feature. A little thing to do... (I say a little thing but I imagine the work behind it. To achive this) I have the most respect for those who can speak the "CODE" language. Really admire what they are able to do.
Thank you very much.
Picture style has no effect on Raw video, forget about it, you only need it for compressed normal 8bit h264 video which looks horrible on the 50d anyway.
Quote from: araucaria on September 26, 2013, 06:19:25 PM
Picture style has no effect on Raw video, forget about it, you only need it for compressed normal 8bit h264 video which looks horrible on the 50d anyway.
True story!! :(
It does not make any difference to the RAW recording, but there is one thing that I want to achive, and it is to get a less saturated image in the LV screen, just to feel that I am recording in that Flat Raw Environment.
Can I achive that somehow?
The MLV/RAW player is a very nice tool for sorting out shots.
It's not perfect but let's you find which shot is which.
http://www.magiclantern.fm/forum/index.php?topic=8447.0
http://upload.g3gg0.de/pub_files/fa8e04a9820d75f2ea36d54bc2a3e922/mlv_view_sharp.exe
Hey guys,
Quick question regarding 50d video playback . . . and excuse me if this isn't the best place to post!
Regarding playback, well . . . its not working, and I'm just wondering 2 things.
1) Is this the way it is, considering the obvious with the camera and not originally doing video?
2) If so, whats the easiest method you've found to playback clips in the field?
I would just like to know if I got the shot, or if I'll need to take again, and being able to review what I just took would be great.
Thanks, and sorry I'm such a noob.
As well as it plays back is how real time compression would work :)
After your 15 minutes are up, view the files when you dump the card if its too slow.
Hello,
I am new to the world of 50D RAW and was curious as to how much I am supposed to be able to record in a single take. I am currently getting to 1421 frames before my camera shuts off. I am recording 1584x1058 at 23.976 fps (which from my understanding supposed to record "continuously"). Is there anything I could be doing wrong? I know it's not my card running out of room because I have a 16GB CF card that I format before I shoot.
Thank you!
Quote from: jarededitor on September 27, 2013, 09:34:48 PM
Hello,
I am new to the world of 50D RAW and was curious as to how much I am supposed to be able to record in a single take. I am currently getting to 1421 frames before my camera shuts off. I am recording 1584x1058 at 23.976 fps (which from my understanding supposed to record "continuously"). Is there anything I could be doing wrong? I know it's not my card running out of room because I have a 16GB CF card that I format before I shoot.
Thank you!
1st: What model/speed card are you using?
2nd: Set option to turn off "Global Draw" in "RAW Video" menu
Does your camera automatically turn off after a certain period of time? There is a Canon Menu option to turn off "Auto Off" or "Auto Power Off."
Playing around with cropmode in the latest Tragic Lantern August 27 build and a Canon EF 800mm f/5.6 lens.
***NEW TRAGIC LANTERN 50D BUILD UPLOADED***
I've just uploaded a new build of Tragic Lantern for the 50D that should increase raw video write speeds by ~2MB/s when used with a fast card (1000x or more) 8)
This build features minor cosmetic changes and also moves module config files to the ML settings folder. You will need to re-enable modules then reboot.
Download - https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Sep28.go_faster.zip
IMPORTANT - Please remember Tragic Lantern builds are on a rolling release and are independent of the main Magic Lantern code although they are up-to-date with ML code at time of release.
Tragic Lantern is developed by 1% and is based on the main Magic Lantern code but does have several enhancements and additional features not (yet) included in Magic Lantern for the 50D.
WARNING - Certain features such as control over 'Dialogue timers' do not conform to Magic Lantern code rules and although unlikely, may break your camera. Only install a Tragic Lantern build if you understand and are willing to risk your camera for the increase in performance!!!
In my own experience I have used Tragic Lantern without any major issues for over 2 years on the 600D and now the 50D but always beware of the risks.
Tragic Lantern for the 50D is not supported by other Magic Lantern developers so please only post in this thread when addressing issues/problems/bugs etc.
Thanks as ever to 1% for his sterling work on the 50D and to a1ex, g3gg0, stevefal (for the nice new look) and all the other devs who contribute their time and effort to develop Magic Lantern free of charge!
Quote from: Andy600 on September 28, 2013, 11:40:31 PM
I've just uploaded a new build of Tragic Lantern for the 50D that should increase raw video write speeds by ~2MB/s
How did you achieved that? And is it possible to apply such code modifications to other cameras?
I didn't. 1% did. He found better Edmacs. The 7D is faster and I guess other cameras can benefit, though the faster edmacs will likely be different for each camera and need finding.
Quote from: Andy600 on September 28, 2013, 11:47:22 PM
I didn't. 1% did. He found better Edmacs :)
Seems like I miss the thread. Can you point me on that?
http://www.magiclantern.fm/forum/index.php?topic=7503.msg79233;topicseen#msg79233
My benchmark was like 86 or something so ~3-4MB off the top isn't horrible. I think 7D has a little bit more room up to 91. If it ever does the 86 tho, that's pretty much the full LV in zoom.
Hi Andy, doesn't look like enough additional MBs, but just in case. On the 50D, does it record 1856x1044 continuous in crop mode at 24fps now?
Quote from: maxotics on September 29, 2013, 12:47:35 AM
Hi Andy, doesn't look like enough additional MBs, but just in case. On the 50D, does it record 1856x1044 continuous in crop mode at 24fps now?
Try it. The only way to tell what you'll get is to use it with your specific card ;)
Thanks Andy, was trying to stay out of trouble (I'm full on with 1%'s other Canonstein, the EOS-M), but OKAY! :-[
I loaded that module and was able to record at 1792x1008 continuous on a Toshiba 16GB 1000x card. Higher rates did not make the continuous cut. I have been shooting at 1728x972. For all I know i could have done the higher rate, though doubt it.
So 1%, great going! I think my 50D just went up another $25 in value!
Its in the bin, not the module.
1920x1038 - safe for me
1920x1080 - maybe 2nd record or 2000x1000
6D/7D/50D/600D all more stable than EOSM, that camera is quirky as hell and lots of stuff is done a diff way on it. Plus the dots which will probably re-appear on any canon with that af system now on.
Recording Raw Continuous at 1584 x 892 at 30 fps with Komputerbay 1000x with latest Tragic Lantern. ;D
... Wondering if Canon would consider having customers ship back their cameras in order to reduce image noise now that RAW capability has been released.
... What about dark frame subtractions? Is that essentially the same technique to reduce image noise and optimize video?
So, I have 2 50Ds. Both using 64gb 1000x KomputerBay cards.
Just installed latest Tragic Lantern & wanted to give some feedback when shooting in cropped mode for 1920x1080p. This is for both RAW and MLV modes, I get almost exactly the same results. Card hits 78mb/s in both cameras for ~20 seconds on first run. Then, 2nd run gets up to 82mb/s and sometimes peaks at 83mb/s. Every file tops out around 4gb-4.4gb
Also put into test mode and it seems M2 B0 is fastest on both cameras by up to a +4mb/s increase.
This is true when hooking up via HDMI, leaving global draw on, or turning off - none effect performance.
Also, my LV never gets turned off, even when going into Hacked mode.
While recording, no matter what mode I'm in, the screen turns grey once I hit SET for recording.
Hope this helps!
Quote from: krashnik on September 29, 2013, 08:11:01 PM
Just installed latest Tragic Lantern & wanted to give some feedback when shooting in cropped mode for 1920x1080p. This is for both RAW and MLV modes, I get almost exactly the same results. Card hits 78mb/s in both cameras for ~20 seconds on first run. Then, 2nd run gets up to 82mb/s and sometimes peaks at 83mb/s. Every file tops out around 4gb-4.4gb
Also put into test mode and it seems M2 B0 is fastest on both cameras by up to a +4mb/s increase.
Hi, I can't get continuous 1920x1080, even at 24 fps. You're not referencing what it says next to "Move Record" with the frame-size setting after "RAW video", right? I have a 50D with a build from yesterday.
I don't know anything about the test mode and M2 B0. If that's the trick, please tell me more! :)
Quote from: maxotics on September 29, 2013, 09:07:02 PM
Hi, I can't get continuous 1920x1080, even at 24 fps. You're not referencing what it says next to "Move Record" with the frame-size setting after "RAW video", right? I have a 50D with a build from yesterday.
I don't know anything about the test mode and M2 B0. If that's the trick, please tell me more! :)
I get continuous recording at 1584x892 @29.976FPS and in 5x crop at 1920x818 @29.976FPS
I get continuous at 1920x1038, though taps out around 2 minutes on 1920x1080p. This is all in 23.976 fps mode.
It doesn't make sense, though... the buffer is doing fine & then it all of a sudden ends at the 4gb mark like it is a 32-bit related issue as opposed to buffer.
My buffer is only half full and then right at 4gb mark it quickly fills. I've tested this on both cameras and at various places on each CF card, so I dont' think it's a hiccup in the card either. Maybe still not fast enough and coincidentally always capping at that same 4gb spot.
Quote from: krashnik on September 29, 2013, 11:00:08 PM
I get continuous at 1920x1038, though taps out around 2 minutes on 1920x1080p. This is all in 23.976 fps mode.
It doesn't make sense, though... the buffer is doing fine & then it all of a sudden ends at the 4gb mark like it is a 32-bit related issue as opposed to buffer.
My buffer is only half full and then right at 4gb mark it quickly fills. I've tested this on both cameras and at various places on each CF card, so I dont' think it's a hiccup in the card either. Maybe still not fast enough and coincidentally always capping at that same 4gb spot.
It's just not fast enough at 1920x1080. It may do it with the Komputerbay 1050x card . . . But it might also be an issue with the edmacs . . .
1920x818 @29.976 is good if you want to slow down the footage . . .
Quote from: menoc on September 29, 2013, 11:14:36 PM
It's just not fast enough at 1920x1080. It may do it with the Komputerbay 1050x card . . . But it might also be an issue with the edmacs . . .
The Komputerbay 1000x is definitely fast enough. I can transfer 117mb/s through my Kingston 3.0 USB CF Card Reader just fine.
I think there are still some limitations in the programming. Honestly, we only really need to squeeze another 2mb/sec and then we should be good.
In further testing, I switched around a ton of settings and found there may be something eating up memory to control the lenses. I tried out a few Tamron lenses that my camera doesn't recognize and they gave better results than my L-series or nifty 50 Canon lenses.
While recording, I assume there is something in the program that is reading aperture settings or focal points, even when in manual mode on the lens. Has anyone else tested their speed in relation to having a generic lens on or not? I had all lenses in manual mode while testing.
Quote from: krashnik on September 29, 2013, 11:44:52 PM
The Komputerbay 1000x is definitely fast enough. I can transfer 117mb/s through my Kingston 3.0 USB CF Card Reader just fine.
I think there are still some limitations in the programming. Honestly, we only really need to squeeze another 2mb/sec and then we should be good.
In further testing, I switched around a ton of settings and found there may be something eating up memory to control the lenses. I tried out a few Tamron lenses that my camera doesn't recognize and they gave better results than my L-series or nifty 50 Canon lenses.
While recording, I assume there is something in the program that is reading aperture settings or focal points, even when in manual mode on the lens. Has anyone else tested their speed in relation to having a generic lens on or not? I had all lenses in manual mode while testing.
Turn off Global Draw completely and you'll have better results.
...only another 2MB/s ;D
Quote from: menoc on September 30, 2013, 12:47:47 AM
Turn off Global Draw completely and you'll have better results.
As stated in my post, I've switched almost all settings possible and using 2 diff cameras, 2 diff CF cards & giving my feedback on what works best. Global Draw makes no difference & the UI is confusing for novices since you can change the Global Draw settings in at least 3 diff places. I'd personally prefer Global Draw hard-coded into the INFO button. ML is getting crazy with menus & submenus and we really aren't making use of the other buttons we have at our disposal.
Also, remember to align your cards and never format in camera. Unaligned, small cluster size is good for a 2-3MB/s off.
I've got no real issues with 1080P and 2k*1K. Hacked mode won't kill edmacs on 5DII/50D/7D cameras. Only 7D gets to play with dead 10x mode.
Quote from: 1% on September 30, 2013, 02:25:43 AM
Also, remember to align your cards and never format in camera. Unaligned, small cluster size is good for a 2-3MB/s off.
I've got no real issues with 1080P and 2k*1K. Hacked mode won't kill edmacs on 5DII/50D/7D cameras. Only 7D gets to play with dead 10x mode.
I haven't been keeping up but, never format in Camera?
So if I have everything set up perfectly (right card, ML, settings) I should be able to get 1920x1080p, 24fps, in crop mode on the 50D? I'm seeing conflicting posts. Thanks!
I format in-camera but also check occasionally that my cards are aligned using an app called diskat-gui (found online). Not sure what cluster size the camera formats to but I don't have any problems with write speeds.
Quote from: Andy600 on September 30, 2013, 03:14:41 AM
I format in-camera but also check occasionally that my cards are aligned using an app called diskat-gui (found online). Not sure what cluster size the camera formats to but I don't have any problems with write speeds.
Are we talking about defragmenting the card? Or is this something different?
Quote from: menoc on September 30, 2013, 03:33:19 AM
Are we talking about defragmenting the card? Or is this something different?
No, it's different. Some cards are misaligned and this can reduce write speeds. If your card is misaligned you need to align it by formatting it a certain way. The Diskat_gui app (search online for it) does a quick analysis of your card and will tell you if it needs aligning.
Google HD alignment
Here's part of my old post about format alignment and how to do it in Windows (http://www.magiclantern.fm/forum/index.php?topic=6554.msg55959#msg55959):
"I reformatted the card:
diskpart
list disk
select disk [...] <- I chose the disk with 29GB, same order as in diskmgmt.msc
clean
create partition primary align=4096
Then format in explorer - fat32, 64kb, quick.
To check:
wmic partition get BlockSize, StartingOffset, Name, Index
StartingOffset divided by BlockSize should be a multiple of 4096 I think? (...)"
And here's the mentioned diskat_gui (Disk Alignment Test) – I haven't tested it, though: http://download.cnet.com/Disk-Alignment-Test/3000-18512_4-75795945.html
Yup, I do that + format to 64K clusters, default is 32. I always end up misaligned formatting in camera, maybe its just me.
I was wondering if anyone had a quick and dirty time-lapse workflow.. I was thinking of using RAW video.. Off the top of my head, I'm thinking I would set my FPS override to something low like 4-12 FPS and then speed in up in my editor to whatever frame rate I was producing at..
Any tips?
Here's a video I shot entierely on 50D, with a samyang 14t3.1 and a 50mmf1.7
The first timelapse was shotwith fps override at 4fps and sped up 10000% in post
I corrected wb, added saturation and applied a LUT (vision X) all in premiere.
Still no joy for me with Tragic Lantern. With 28sep. build, as well as the previous two, the camera crashes when I turn on MLV recording (movie menu) in Live View, or when I switch to live view with it on. The camera freezes and I can't do anything except take the batteries out. This is on a freshly formatted in camera Komputerbay 32gb x1000 card - installed 2.3 and replaced it with TL.
Any help, please?
Quote from: johansugarev on October 01, 2013, 12:42:38 PM
Still no joy for me with Tragic Lantern. With 28sep. build, as well as the previous two, the camera crashes when I turn on MLV recording (movie menu) in Live View, or when I switch to live view with it on. The camera freezes and I can't do anything except take the batteries out. This is on a freshly formatted in camera Komputerbay 32gb x1000 card - installed 2.3 and replaced it with TL.
Any help, please?
Don't enable raw_rec and mlv_rec at the same time and make sure the IME modules are loaded too.
I would suggest not loading any other modules (ettr, auto exposure etc).
Hi all,
Im very impressed by the awesome work and community here..!
Im new, just got at 50d and Im looking for the best card for the $$. as I have read the "KOMPUTERBAY 64GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 64 GB" seems to be the most stable? i see it costing $130 on amazn but there is a "KOMPUTERBAY 128GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 128 GB" for $170... is there a problem with the larger one? $40 more for twice the memory seems like a better deal (for some pretty damn expensive cards..).
do you have some advice for me? thanks in advance!
Quote from: Andy600 on October 01, 2013, 12:51:03 PM
Don't enable raw_rec and mlv_rec at the same time and make sure the IME modules are loaded too.
I would suggest not loading any other modules (ettr, auto exposure etc).
Which are the IME modules? :o
I enable only mlv_rec
Transcend 16GB 600x (TS16GCF600)
Tragic Lantern 28sep, raw_rec module, format card to 64Kb clusters, сard warm-up 1GB, GlobalDraw off
In crop mode:
1792x1008 24fps - continuos ok
1856x1044 24fps - 791 frames
1920x1080 24fps - 383 frames
Quote from: johansugarev on October 01, 2013, 12:42:38 PM
Still no joy for me with Tragic Lantern. With 28sep. build, as well as the previous two,
Try replacing all of the files from your card with new files from the build. Do not mix old files with new files from updated builds.
I am doing exactly that. Loaded the IMO modules (ones that have imo_..) - still the same. Loading the scripts module gives me some linking error.
Quote from: kimo on October 01, 2013, 12:57:55 PM
Hi all,
Im very impressed by the awesome work and community here..!
Im new, just got at 50d and Im looking for the best card for the $$. as I have read the "KOMPUTERBAY 64GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 64 GB" seems to be the most stable? i see it costing $130 on amazn but there is a "KOMPUTERBAY 128GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 128 GB" for $170... is there a problem with the larger one? $40 more for twice the memory seems like a better deal (for some pretty damn expensive cards..).
do you have some advice for me? thanks in advance!
Yes, there are problems with the 128GB 1000x Komputerbay card! The forum is full of posts about it.
Quote from: johansugarev on October 01, 2013, 01:14:58 PM
I am doing exactly that. Loaded the IMO modules (ones that have imo_..) - still the same. Loading the scripts module gives me some linking error.
Don't load the script module. I forgot to pull that from the latest build.
TBH it can only be 2 things. User/config error or your camera is fucked.
I'll msg you in a minute.
thanks andy,
yeah i have noticed but its difficult to wade thru the posts to find out what works best for the 50d, compared to its data write speed etc.. off hand can you tell me what is the best for the price so far? :-[
Quote from: kimo on October 01, 2013, 01:27:13 PM
thanks andy,
yeah i have noticed but its difficult to wade thru the posts to find out what works best for the 50d, compared to its data write speed etc.. off hand can you tell me what is the best for the price so far? :-[
The Komputerbay 64gb 1000x card is the best bang for the buck atm
Quote from: bzhwindtalker on October 01, 2013, 08:51:09 AM
Here's a video I shot entierely on 50D, with a samyang 14t3.1 and a 50mmf1.7
The first timelapse was shotwith fps override at 4fps and sped up 10000% in post
I corrected wb, added saturation and applied a LUT (vision X) all in premiere.
Very cool video! also, it's good to see that if you know how to pan the camera correctly, there are very few rolling shutter issues
Komputerbay 64gb Not Working
Quote from: kunle on October 01, 2013, 07:33:21 PM
Komputerbay 64gb Not Working
I just bought a cannon 50d and komputetbay 64gb 1000x cf card. Unfortunately the camera can't see the card, well it does but it states that the card needs to be formatted, which the camera can't do. I reformatted the card to fat32 but still have the same problem. The camera reads my other Cf cards. Does anybody have any suggestions or recommend a similar card?
Check that you have V1.09 firmware installed
Quote from: krashnik on September 30, 2013, 01:53:52 AM
Global Draw makes no difference & the UI is confusing for novices since you can change the Global Draw settings in at least 3 diff places.
Which are these 3 places? I can only find one.
QuoteI'd personally prefer Global Draw hard-coded into the INFO button.
Simply configure a display preset (http://wiki.magiclantern.fm/userguide#lv_display_presets) that does just this.
QuoteML is getting crazy with menus & submenus and we really aren't making use of the other buttons we have at our disposal.
Any constructive suggestion?
Thanks Andy600 for the quick response, the first thing I did when I got the camera was to check the firmware (It was V1.09) and I upgraded to the latest magic lantern firmware. The exact error on the camera was "Error CF". The CF was readable on both OS X and Windows operating systems.
Quote from: kunle on October 01, 2013, 08:15:07 PM
Thanks Andy600 for the quick response, the first thing I did when I got the camera was to check the firmware (It was V1.09) and I upgraded to the latest magic lantern firmware. The exact error on the camera was "Error CF". The CF was readable on both OS X and Windows operating systems.
Did you make the card bootable?
Yes I did. I even did a low level format and formatted it fat32 before using eoscard.I have gone through this procedure loads of times my other cameras. Might just be I got one of the bad komputerbay cards I have read about. Will return it to Amazon and order a different card.
Quote from: kunle on October 01, 2013, 08:45:15 PM
Yes I did. I even did a low level format and formatted it fat32 before using eoscard.I have gone through this procedure loads of times my other cameras. Might just be I got one of the bad komputerbay cards I have read about. Will return it to Amazon and order a different card.
Yes, unfortunately it sounds like a bad card.
I got a 32gb Transcend 1000X for $114--I've seen a lot of people complain about the KomputerBay in this thread alone, and I'd hate to see how much it pops up everywhere else. Just seems like it'd be a good idea to minimize the possibility that this could be the problem.
http://www.ebay.com/itm/331027818633
Quote from: kimo on October 01, 2013, 12:57:55 PM
Hi all,
Im very impressed by the awesome work and community here..!
Im new, just got at 50d and Im looking for the best card for the $$. as I have read the "KOMPUTERBAY 64GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 64 GB" seems to be the most stable? i see it costing $130 on amazn but there is a "KOMPUTERBAY 128GB Professional COMPACT FLASH CARD CF 1000X 150MB/s Extreme Speed UDMA 7 RAW 128 GB" for $170... is there a problem with the larger one? $40 more for twice the memory seems like a better deal (for some pretty damn expensive cards..).
do you have some advice for me? thanks in advance!
Is 2000x1080 continuous in crop? Seems like i can only get 250 frames out of it? I have a Komputerbay 1000x...
2000x1000 with 24fps. 2000x1080 should net more than 250 frames tho.
QuoteGlobal Draw makes no difference & the UI is confusing for novices since you can change the Global Draw settings in at least 3 diff places.
2 places, raw module (while recording) and ML menu... I'd say it makes a bit of diff for raw. You're not going to learn all the features in 1 day.
Quote from: 1% on October 02, 2013, 04:01:02 AM
2000x1000 with 24fps. 2000x1080 should net more than 250 frames tho.
Thanks!
@Andy600. Hi man, may I ask you something I did not found any answer yet?
I´ve been shotting RAW with the 50D and I have noticed that the final exposure of the images are quite underexposed, once I open it in ACR, compared with what I saw in the LV camera. My question:
Is there a way to shoot "WYSIWYG" in 50D raw?
I know that the camera is not intended for video shooting and the LV image do not match with the Photo mode shutters values. I use always manual vintage lenses and even the auto ETTR works fine to get the best exposure, I find very difficult to shoot with such a bright image.
I have only found that the only way to get WYSIWYG is turning ON the "Constant Exp" in FPS override menu, but as you probably know it only works with 100 ISO and 1/50 near values.
Pardom my english.
Quote from: Nachelsoul on October 02, 2013, 11:59:25 AM
@Andy600. Hi man, may I ask you something I did not found any answer yet?
I´ve been shotting RAW with the 50D and I have noticed that the final exposure of the images are quite underexposed, once I open it in ACR, compared with what I saw in the LV camera. My question:
Is there a way to shoot "WYSIWYG" in 50D raw?
I know that the camera is not intended for video shooting and the LV image do not match with the Photo mode shutters values. I use always manual vintage lenses and even the auto ETTR works fine to get the best exposure, I find very difficult to shoot with such a bright image.
I have only found that the only way to get WYSIWYG is turning ON the "Constant Exp" in FPS override menu, but as you probably know it only works with 100 ISO and 1/50 near values.
Pardom my english.
Turn on Global Draw and Histogram to see your exposure levels.
Try negative digital ISO to preview a darker image (this one doesn't affect the raw image, just the preview).
I like the UI text improvements in a great way. It's much more legible for me and for my 2nd Ops too.
A few new projects completed using the 50D latest builds :)
SPLIT SCREEN
C3 THE SCIENCE OF BOXING
THE PASSIVE-AGGRESSIVE LITTLE TOASTER
I love you guys for the development strides you've brought to this community as well as to us filmmakers. It has REALLY brought my work to the next level.
Real nice work Kahl.
To all involved with ML nice work all around.
Quote from: KahL on October 02, 2013, 04:33:31 PM
I like the UI text improvements in a great way. It's much more legible for me and for my 2nd Ops too.
A few new projects completed using the 50D latest builds :)
SPLIT SCREEN
C3 THE SCIENCE OF BOXING
THE PASSIVE-AGGRESSIVE LITTLE TOASTER
I love you guys for the development strides you've brought to this community as well as to us filmmakers. It has REALLY brought my work to the next level.
Quote from: a1ex on October 02, 2013, 02:57:26 PM
Try negative digital ISO to preview a darker image (this one doesn't affect the raw image, just the preview).
Works great!!! Thanks Master. You are truly a legendary hero
Quote from: 1% on October 02, 2013, 04:01:02 AM
2 places, raw module (while recording) and ML menu... I'd say it makes a bit of diff for raw. You're not going to learn all the features in 1 day.
Ok, so we have:
#1 - Overlay screen and a master control at top to toggle Global Draw
#2 - MLV/RAW mode screen
#3 - INFO Button on camera
I suggest we eliminate all but the INFO button as we are used to using this already for overlay controls. By default, have GD off, then 1st hit of INFO button turns on normal Canon Overlay. 2nd hit of INFO turns on ML GD, 3rd hit brings up secondary ML menu with quick stats, 4th hit completely disables all GD again.
This is one less toggle to have to think about when setting things up. It is not a matter of whether you can learn it in one day or not, I have had ML installed for years. The problem lies in so many sub-menus which is not a professional approach.
I personally never touch my AF-ON button, the light bulb button, the Exposure Lock button, nor the Shoot Mode button on my Canon 50d. Being able to reroute some ML features to utilize these buttons instead of a ML menu with submenus would be incredible.
For example, give us options in the ML menu to reroute these less-used buttons. Have common options like "GD on/off" "RAW recording on/off" "Video on/off" and maybe another common that ppl are always using while doing a run-n-gun type shoot with the 50D. Hard-coded buttons in the config would really make the setup more advanced and help us all out.
QuoteI suggest we eliminate all but the INFO button as we are used to using this already for overlay
Uhm... I use global draw all the time except while recording raw video... I never use the canon dialogs.
The only other case to disable global draw is for HDMI recording.
QuoteI personally never touch my AF-ON button, the light bulb button, the Exposure Lock button
AF on is like 1/2 shutter, and generates the same events. Expo lock has issues too I think.
Also one thing you may forget is canon redraws excessively on 50D... record without disabling the dialog refresh/canon bmp buffer (tied to gD) and its pink frame city.
I'm not saying I only use the INFO button. I'm saying that Canon uses it in their manuals & Canon users as a whole think of it as a button to go to for "info" on the screen.
I'm suggesting a further change to the UI of the system so we can click the INFO button for a rotation of GD info.
Of course I use GD constantly when doing shots, but right now the only way to turn it on/off is through the ML menu, not with a hard-coded button.
I know AF-ON and Expo lock both have issues, this is why I think we should reroute them to other more useful functions. Overall, we just have many many buttons on the 50D that could be rerouted and used to our benefits as ML shooters instead of browsing constantly through the huge ML menu.
Some people love timelapse, some love ETTR, some love RAW. If we restructure the hard-coded buttons so we can toggle on/off what our fave uses of ML is, then it makes our equipment much more useful. While in stock canon mode, I never take my eye off the viewfinder in my photoshoots. I don't have that luxury when in ML mode due to lack of hard-coded buttons that I'm capable of using.
The few buttons i mentioned with the ability to reroute to a slew of 12 common functions people use would be a weclomed asset by all, I would think?
I know this was discussed already somwhere in this thread, but it's 144 pages...
Anyways the latest TL build, I got this thing:
(http://i.imgur.com/ULflxN9.jpg)
@SebaVuye - mlv or raw?
I get occasional corrupt frames from using mlv_rec on my slower 600x card but non with raw_rec. My 1000x card never has corrupt frames.
Corrupt frames are usually card related. What card are you using?
Quote from: Andy600 on October 02, 2013, 09:15:37 PM
@SebaVuye - mlv or raw?
I get occasional corrupt frames from using mlv_rec on my slower 600x card but non with raw_rec. My 1000x card never has corrupt frames.
Corrupt frames are usually card related. What card are you using?
raw_rec, I have a Komputerbay 32GB 1000x, I used raw with an older build(not tragic lantern) and never had this issue. I filmed in crop mode in 2000x1000 with global draw on. Other modules enabled are: ettr, file_man,dual_iso.
Thanks
You do realize that having GD on while trying to record 2000x1000 (or do you mean 1080?) is really pushing raw rec to the limit...literally!? ???
Disable GD when recording using the setting in the raw module and format your card regularly.
Quote from: Andy600 on October 02, 2013, 09:27:02 PM
You do realize that having GD on while trying to record 2000x1000 (or do you mean 1080?) is really pushing raw rec to the limit...literally!? ???
Disable GD when recording using the setting in the raw module and format your card regularly.
Yeah, makes sense Andy :p, I will disable it next time.
Thanks!
Thats why its in the module, have your cake + eat it too. Any disturbances when using 90% of edmac bandwith will cause issues. Nothing else on the camera writes this fast (or even close).
... Definitely noticing how pushing the cam's write limitations tends to develop corrupt frames.
Got corrupt frames with HDMI connected and Global Draw on. Soon as Global Draw was off the corrupt frames went away. Was shooting at 23.976 at 1584 x 892 with a Komputerbay 64GB 1000X.
... Just to be safe, I started turning Global Draw off when using HDMI, even with very low frame rates. 8)
Out of curiousity.. could you shoot a 'broadcast quality' commercial using the 50d?
Quote from: fromdecember on October 05, 2013, 06:08:36 PM
Out of curiousity.. could you shoot a 'broadcast quality' commercial using the 50d?
If you imply standard definition size, than you can do it even with t2i.
Quote... Just to be safe, I started turning Global Draw off when using HDMI, even with very low frame rates.
Thats why I turn it off while recording :)
HDMI/global draw/etc are all using the edmac or cpu in some way and this means slower writes or corrupt frames.
This might not be the place to post this, but is there anywhere that I can download the dng files from the 50d so I can color grade them myself? It's hard to judge the quality by looking at other people's work.
Quote from: FilmPerson on October 05, 2013, 08:04:49 PM
This might not be the place to post this, but is there anywhere that I can download the dng files from the 50d so I can color grade them myself? It's hard to judge the quality by looking at other people's work.
What is it you want to know? It's raw from a sensor from a very reputable company. There is nothing like it for even three times the price. Either you want it or you don't. The image is like nothing you've ever seen out of 8 bit h264 DSLRs. It still has issues with moire/aliasing in full frame mode but when you go to cropped mode that all disappears or is greatly diminished. It still has rolling shutter and jello. But as far as grading is concerned it's the same as editing a photograph in camera raw. In fact that's what I do. I open the raw file which has a weird purple hue to it and either use the eye dropper or auto to set the white balance in Photoshop CS6 and then go from there moving sliders around to get the exposure I want. A properly trained chimp can grade it. At least grade it to look realistic. If you want to do any type of weird teal and orange stuff you will probably have to export your results to another program. But even then you will be starting off with a much better file.
Really the results are there and there is no competition. Cropped mode 1920x1080 is pretty much unrivaled anywhere near that price point.
I know it's a great value. I just wanted to compare it to raw on the BMPC, mII, etc. Helps to know what you're getting before you spend 500 dollars!
Quote from: FilmPerson on October 05, 2013, 10:11:17 PM
I know it's a great value. I just wanted to compare it to raw on the BMPC, mII, etc. Helps to know what you're getting before you spend 500 dollars!
Well for one thing $500 is too much. I got mine in the US for $350. If you are getting a bare bones body only with one old battery camera then $350. With some accessories maybe $400. Check the sold Canon 50Ds on ebay. With a little bit of patience you will see people picking them up for $350... or less. If you pick the camera up for $350 and you don't like it you can sell it for not much of a loss. Not a bad way to try out raw. You can't compare it to the BMPCC. BMPCC currently doesn't shoot raw. You get a flat Prores file out of the camera which is definitely more difficult to grade than the Canon 50D raw. Any raw workflow is tedious because of all the extra conversion steps. But when you get your DNG files into Camera Raw it is stupidly easy to adjust exposure and color. If you can edit a photograph you can grade your movie and if you want to get funky with things like Magic Bullets you can output your file from Camera Raw and import it into whatever program for more grading.
If your concern is grading then don't worry about it. If you are concerned about moire/aliasing at full frame then yes you should be concerned. If you are worried about rolling shutter then yes you should be concerned. What I will say though is the crop mode 1920x1080p is beautiful. You are going to have to spend a lot more to beat it.
To be honest with you though if you are okay with the smaller sensor on the BMPCC and the issues with IS lenses, etc working with prores files could be nice once you got the grading down. raw workflow is painful. I don't know. I just think all the cameras you mentioned have so many pros and cons. To me grading raw files is the easy and fun part. Ingesting the raw from the camera and the absolutely ridiculous storage requirements are what give me pause. Also you can only shoot 1920x1080p in crop mode. And you can only do that for a finite amount of time. I'm okay with making 30 second clips. Most of mine are a lot shorter so that is not a constraint. The BMPCC has no such constraints but it has other issues.
Thanks for the info on the other cameras, still researching my options. 50d grading is a dream though, so I'm really leaning towards that at the moment.
While I'm here, what's the highest resolution you guys have managed to record at if you had to record for 1min-1.5 min? I'm using this camera for narrative film and I'd like to have semi-long takes as an option. And could I possible change the aspect ratio from 16:9 to something like 2:39:1 so I could record longer, while still having it look like a film? Apologize if these are stupid questions, still making my way through the scattered documentation!
Quote from: FilmPerson on October 06, 2013, 09:43:49 AM
Thanks for the info on the other cameras, still researching my options. 50d grading is a dream though, so I'm really leaning towards that at the moment.
While I'm here, what's the highest resolution you guys have managed to record at if you had to record for 1min-1.5 min? I'm using this camera for narrative film and I'd like to have semi-long takes as an option. And could I possible change the aspect ratio from 16:9 to something like 2:39:1 so I could record longer, while still having it look like a film? Apologize if these are stupid questions, still making my way through the scattered documentation!
You can do that with all resolutions as long as you got a good 1000x card. So you can film in maximum full crop resolution which is 1584*1030 (or something like that) and 1920x1080, the first one is perfectly continuous and the second one is almost continuous. So you will get a lot more than 1.5minutes.
Hey people,
Haven't been here for awhile, so this news may have been here.
Since not long ago the popular still RAW processor Capture One supports Cinema DNGs. (You could import them before, but they would be handled incorrectly).
Besides that it gives another (superior, though cumbersome) way of post-product your movie, it provides some extra tools to handle moire in the footage. I'm not sure how it stands against Raw Therapy, but it definitely outperforms ACR engine.
Below is the footage to compare clean DNGs and ex-CO TIFFs imported to AfterEffects.
Basically, now moire with 50D bothers me much less.
Did anyone succeed to open Cinema DNGs from Canon 50D in Resolve 10 Beta? In my case I have immediate CRASH (
Quote from: FilmPerson on October 06, 2013, 09:43:49 AMWhile I'm here, what's the highest resolution you guys have managed to record at if you had to record for 1min-1.5 min? I'm using this camera for narrative film and I'd like to have semi-long takes as an option. And could I possible change the aspect ratio from 16:9 to something like 2:39:1 so I could record longer, while still having it look like a film? Apologize if these are stupid questions, still making my way through the scattered documentation!
If I were you I would try and get a 50D in hand for cheap and try it out. How much is your time worth? The idea of shooting a narrative film with plenty of actors and dialog on a 50D is a bit scary. If you get it for $350 and decide you don't like it you should be able to unload it for $350 and maybe take a $40-$50 hit on shipping/packaging/ebay/paypal fees. I have a 600D and I shoot a heck of a lot more with that than my 50D. I don't know what you currently own but if I were to shoot a movie I would use both. If you use shallow depth of field, nice lighting and close up shots of things like faces you can do a lot with a 600D. You can even intercut it with raw footage and no one will notice as long as you choose your shots carefully.
The 50D was never meant to shoot movies of any kind let alone 1920x1080 raw. To me it feels like you are fighting the camera. There is a very specific procedure to get 1920x1080 video out of the thing. When you are shooting 1920x1080 and you want maximum record time you have to turn off global draw and you basically have no way to monitor what video is being recorded. I use it on a tripod and set up the shot. Then I hit record and count off the seconds. I don't even look at the camera. Well sometimes I do to make sure the card is "warmed up." I'm not sure what all is involved in the warming up process but for some reason the camera can write to the card faster after it has been recording for awhile. So even with everything set the exact same you won't get the same write speeds to the card between two takes. That's not a problem for me but if you are going for 90 seconds sometimes in the middle of the take the buffer will fill up and the camera will stop recording. Get the camera and see what I mean. It is not as simple as making a couple of basic settings in the morning and then just hitting record whenever you need to do a take and looking at a gorgeous LCD while you film. Like I said... compromises.
Quote from: FilmPerson on October 06, 2013, 09:43:49 AM
Apologize if these are stupid questions, still making my way through the scattered documentation!
It's great you're reading everything but at some point you get the other problem, paralysis-by-analysis. Sniper is right. You can shoot some very nice RAW with the 600D, which is good enough for most people, or you can get a more resolution through the 50D, mostly because it writes to fast (also expensive) CF cards. I've shot a lot of video with both a 50D and EOS-M. From everything you'd said I believe you should start with the 600D. Like Sniper said, it has great H.264 so you can start shooting tomorrow. Also, 1280x720 RAW on that camera, in crop mode, is VERY, VERY good! No moire. I don't shoot much 50D anymore because the 720p is worlds away from 1080p H.264. Dynamic range, NOT resolution, is the reason you shoot RAW. If you just want sharpness, the 600D will deliver.
Anyway, just get any Canon camera that will load ML RAW and start working with it. RAW is a steep learning curve. I estimate it took me about 100 hours just to get comfortable. My guess is that it's the same for any serious shooter here. There are no shortcuts. I wish there were!
I can't stress enough how thankful I am for all this information! It's been very helpful. What I'm hearing is:
The 50d isn't stable enough to record longer takes consistently because the buffer overloads. (I'm getting mixed messages on this one)
You can't look at what you're shooting (even on an external monitor?)
If this is true then I probably won't be getting the 50d. Is this correct info or am I misunderstanding you guys?
I'm getting this camera just to practice for now, if I shoot anything serious on it it won't be for the next year. I'm fine with the awful raw workflow, I've done things similar to it in the past for my non-raw videos. It's grueling but doable. But if the facts above are true, then there's no way I can afford to experiment with this thing.
Again thanks for the info, after this I promise I'll stop hijacking this thread!
Quote from: FilmPerson on October 06, 2013, 06:45:09 PM
The 50d isn't stable enough to record longer takes consistently because the buffer overloads. (I'm getting mixed messages on this one)
Actually, the 50D is VERY stable. You just have to have the right card and almost every feature turned off to get 1920x1080p. However you can upscale any video size and I doubt you lose much IQ shooting 1728x972, which my camera does easily now. Doubt you could tell the difference on Vimeo.
This is the 50D thread I will mention that I have NOT been able to shoot 1920x1080p continuously for more than 700 frames with my Toshiba 16GB 1000x card. But again, I only try it for bragging rights. I can't remember, even when doing that, that the camera has ever crashed.
Quote from: rommex on October 06, 2013, 02:46:12 PM
Did anyone succeed to open Cinema DNGs from Canon 50D in Resolve 10 Beta? In my case I have immediate CRASH (
I just tried and get the same crash.
@levisdavis
Any further developments on the 50D VAF from Mosaic?
Hey guys! Just joined to forum to say thanks to the guys who've been working so hard on the hacks. The developments are honestly amazing, I just sold me t3i and will be scooping up a 50d with some MF glass pretty soon. :)
I downloaded a 50d movie earlier called "kiss" off vimeo and played around with the CC to see what I could do. Even after compression the flexibility is nuts.
Here's the original https://vimeo.com/67351221
(http://imageshack.us/a/img542/9761/qp5b.png)
(http://imageshack.us/a/img94/7559/tftz.png)
(http://imageshack.us/a/img703/6936/4upv.png)
(http://imageshack.us/a/img7/1396/mhlc.png)
(http://imageshack.us/a/img689/3586/lysj.png)
Quote from: tmte on October 07, 2013, 12:09:41 AM
Hey guys! Just joined to forum to say thanks to the guys who've been working so hard on the hacks. The developments are honestly amazing, I just sold me t3i and will be scooping up a 50d with some MF glass pretty soon. :)
I downloaded a 50d movie earlier called "kiss" off vimeo and played around with the CC to see what I could do. Even after compression the flexibility is nuts.
Here's the original https://vimeo.com/67351221 (https://vimeo.com/67351221)
I actually think that has more to do with the weather the video was shot (plus the not over graded footage). If you are fine with that kind of grading you could go with a panasonic gh2 or g6 and save yourself a lot of trouble.
@araucaria Please don't take this the wrong way. I am not knocking the GH2, GH3 or any other consumer H.264 video camera. I have a couple. For many types of situations they are perfect.
However, there are many people who have only shot with a GH2 and don't understand how RAW video is different, much different. Each frame of the 50D is say 1728x972, or 1,679,616 pixels. Each pixel (red, green or blue) has a value of 256, 1 byte. There are 24 frames a second, or 40 megabytes per second. That is all real color information.
Even when the GH2 is running the highest bitrate hack, it's at 175Mbits, that's BITs not BYTES. In bytes that 175/8 or 22 Megabytes.
How can a camera that saves 22 megabytes of color data per second match a 40 megabyte camera? There are many people that would argue that those numbers are distorted (the 50D can actually go quite higher). In any case, no one would question the dynamic range difference between the cameras.
Again, I'm not saying one can't shoot great video with the GH2. Many have. But it's dis-information to say one can get the same dynamic range with a GH2 over a 50D. You can't grade in color data that just isn't there. This is obvious to anyone who has shot both.
Again, not saying your advice, in general, isn't good. It may be the best advice for that reader.
Quote from: araucaria on October 07, 2013, 12:17:58 AM
I actually think that has more to do with the weather the video was shot (plus the not over graded footage). If you are fine with that kind of grading you could go with a panasonic gh2 or g6 and save yourself a lot of trouble.
I understand that what I did specifically only worked because of the overcast and subjects, but I still thought it was fine. :P I've worked with RAW and the GH2 before and I don't think it'll be too bad + a 50D can be had for $300 less than a GH2, which is also nice.
In RAW, each pixel has a value of 16384. Not 256
Quote from: maxotics on October 07, 2013, 12:57:31 AM
@araucaria Please don't take this the wrong way. I am not knocking the GH2, GH3 or any other consumer H.264 video camera. I have a couple. For many types of situations they are perfect.
However, there are many people who have only shot with a GH2 and don't understand how RAW video is different, much different. Each frame of the 50D is say 1728x972, or 1,679,616 pixels. Each pixel (red, green or blue) has a value of 256, 1 byte. There are 24 frames a second, or 40 megabytes per second. That is all real color information.
Even when the GH2 is running the highest bitrate hack, it's at 175Mbits, that's BITs not BYTES. In bytes that 175/8 or 22 Megabytes.
How can a camera that saves 22 megabytes of color data per second match a 40 megabyte camera? There are many people that would argue that those numbers are distorted (the 50D can actually go quite higher). In any case, no one would question the dynamic range difference between the cameras.
Again, I'm not saying one can't shoot great video with the GH2. Many have. But it's dis-information to say one can get the same dynamic range with a GH2 over a 50D. You can't grade in color data that just isn't there. This is obvious to anyone who has shot both.
Again, not saying your advice, in general, isn't good. It may be the best advice for that reader.
Ehm, I think it was pretty clear we were talking about compressed footage downloaded from vimeo... Btw, where do the 150 pixels for 1728x972 come from? Anyway, the GH2 is better in everything but color depth and dynamic range (but only because you loose a lot when compressing) when compared to the 50d in raw mode. The gh2 is definitely sharper and has no moire.
But hey, I don't have a gh2 but I do have a 50D because I like the color depth and the lack of compression, and specially because I hate the way you have to grade non raw stuff.
QuoteBut it's dis-information to say one can get the same dynamic range with a GH2 over a 50D
Where is this coming from?
Ha ha, yea, don't compare with H264 anything... should be 50D vs ari, red, bmcc, etc.. maybe some 4:2:2 or 4:4:4 broadcast cams if you really wanna check vs compressed formats.
Quote from: 1% on October 07, 2013, 02:13:35 AM
Ha ha, yea, don't compare with H264 anything... should be 50D vs ari, red, bmcc, etc.. maybe some 4:2:2 or 4:4:4 broadcast cams if you really wanna check vs compressed formats.
Honestly, this GH3 footage I shot looks better in sharpness and dynamic range than anything I've gotten out of my RAW enabled 50D.
And it only took up 16 gigs of space rather than 200 gigs - and I didn't have to manually change white-balance for every shot - and I didn't have to worry about the camera randomly shutting off, frames becoming corrupted, or frame guess in 5X crop mode.
Quote from: D.L. Watson on October 07, 2013, 02:40:57 AM
Honestly, this GH3 footage I shot looks better in sharpness and dynamic range than anything I've gotten out of my RAW enabled 50D.
First D.L., very nice video. What I'm pointing out is a technical fact, not an aesthetic judgment. I agree, shooting RAW is difficult and time consuming and often, just NOT worth it. But a scene in that video would be a case in point, about the difference in dynamic range between a GH3 and 50D RAW
(http://maxotics.com/images/h264crushedblacks.jpg)
I'm virtually certain that a 50D shooting raw would show a lot of detail under that counter. Again, not saying the video isn't perfect.
@TrulyRAW, as for a pixel having value of 0 to 255, instead of 16384. I'm talking about before de-bayering which is what the camera records to RAW in, either red, green or blue values.
@araucaria I did not mean to imply you were spreading dis-information. Sorry if it came across the way.
Quote from: maxotics on October 07, 2013, 02:53:15 AM
First D.L., very nice video. What I'm pointing out is a technical fact, not an aesthetic judgment. I agree, shooting RAW is difficult and time consuming and often, just NOT worth it. But a scene in that video would be a case in point, about the difference in dynamic range between a GH3 and 50D RAW
I understand technically RAW is better in every way. And yes, I would agree that in some circumstances, RAW does have it's Pros.
And I don't want to beat a dead horse, but the GH3 still holds a lot of information in the shadows. I just pulled this from the ungraded footage. It was my choice when I graded to put the folks in silhouette because I don't have neat video (yet). I'm fairly certain if I put this though neat video, this would be a totally usable shot - in fact - if I added grain to the highlights it could be usable now.
(https://dl.dropboxusercontent.com/u/9746153/ungraded.jpg)
But technically, yes - much more color and luminance information is available in the 50D.
D.L. I just watched a bunch of your video and I'm like "Does he watch his own stuff?" :) When you shot the graveyard with the GH3 it was cloudy (which, of course, is favorable conditions); when you shot it with the 50D it was sunny. Difficult to compare them.
I think what you're saying, and I totally agree, is that the dynamic range is often not worth the 10-times time, money, effort, etc. If you don't need high dynamic range than you're be crazy to shoot RAW, with any camera! Panasonic is the master of consumer video. Even my lowly GF3 with a $30 c-mount TV lens kicks a__, far as I'm concerned.
However, the film about the mechanic, shown in a movie theater, would look fantastic. If shot on GH3, I think the contrast would dilute the emotional feel of the piece. Just my 2-cents.
98% of all the music I love was recording on equipment lower-tech than my phone. I'm a complete old-movie nut. I really couldn't care, when I'm the one wanting to be entertained.
What I love about RAW is that it is close to the film look. I'm good with losing sharpness and picking up noise. Just me.
Your talent deserves a 5D3. If only the world were fair ;)
Quote from: maxotics on October 07, 2013, 03:28:23 AM
However, the film about the mechanic, shown in a movie theater, would look fantastic. If shot on GH3, I think the contrast would dilute the emotional feel of the piece. Just my 2-cents.
Thanks for watching! I guess I should post it here:
"DICHOTOMY" 50D MAGIC LANTERN SHORT FILMAfter being pointlessly confronted, a quiet mechanic must contend with his darker, more sinister self. I'm probably going to keep my 50D and stay with my GH3 for now until Magic Lantern comes out with compressed RAW or something that will write metadata for white-balance settings - etc. If I invested into RAW for an extra stop and half of latitude and post-white balance - I wouldn't have enough money to make my little indie shorts.
Thanks for watching!
QuoteWhat I'm pointing out is a technical fact, not an aesthetic judgment. I agree, shooting RAW is difficult and time consuming and often, just NOT worth it.
This. If comparing H264, 50D sucks straight up. 50D, ~400-500 USD 2008, GH3 2012, $1k? Nobody has been comparing chroma key yet.... where you want short clips and lots of color data. I wouldn't want to shoot weddings or long interviews with raw though...
Quotesomething that will write metadata for white-balance settings
MLV would do that. But the rewrite which was supposed to add speed and hopefully no more dead frames isn't all done.
No new news from Mosaic Engineering. Left a voice message last Friday the 4th offering my assistance and/or just to simply touch base and find out about the progress of the filter.
... Been following 50D ML Forum and reading what other users have asked about Mosaic Engineering.
Here is a link to DNGs featuring the VAF and a $10 Promaster UV filter and also no VAF with the same $10 Promaster Filter. Looks like the moire is nearly completely eliminated (95 - 97%).
https://copy.com/hjxaDziN02ae (https://copy.com/hjxaDziN02ae)
... The last two Fridays in a row I've left a voice message with Mosaic in an attempt to touch base... Still no new news.
Quote from: D.L. Watson on October 07, 2013, 02:40:57 AM
Honestly, this GH3 footage I shot looks better in sharpness and dynamic range than anything I've gotten out of my RAW enabled 50D.
To me, the GH3 looks very video like and if you're getting more dynamic range out of it then I don't think you're exposing the 50D properly.
QuoteIf I invested into RAW for an extra stop and half of latitude and post-white balance - I wouldn't have enough money to make my little indie shorts.
That extra dynamic range could be the difference between blowing out the windows or not, definitely worth it in my opinion.
RAW can't be compared to H264, there's no contest. I see my 50D as a mini Red one.
Quote from: LEVISDAVIS on October 07, 2013, 10:52:59 AM
No new news from Mosaic Engineering. Left a voice message last Friday the 4th offering my assistance and/or just to simply touch base and find out about the progress of the filter.
... Been following 50D ML Forum and reading what other users have asked about Mosaic Engineering.
Here is a link to DNGs featuring the VAF and a $10 Promaster UV filter and also no VAF with the same $10 Promaster Filter. Looks like the moire is nearly completely eliminated (95 - 97%).
https://copy.com/hjxaDziN02ae (https://copy.com/hjxaDziN02ae)
... The last two Fridays in a row I've left a voice message with Mosaic in an attempt to touch base... Still no new news.
Thanks for chasing it. It looks like they have been working on a BMCC filter so maybe they haven't had time for the 50D one lately. Hopefully they'll get to it soon.
Can you shoot a test on some striped fine detail fabric if you have time?
Cheers
Will make time for a test for sure...
Here is a color corrected image from the VAF filter test with the Promaster UV filter in place using Capture 1 trail version to export flat 16-bit Tiff image and then applied Color Correction in AE with Synthetic Aperture to create this look... (Take notice to the detail and the lack of moire! Obviously the color is jumping out in a great way, right?)
(http://i.imgur.com/AbLVII8.jpg)
For me the 50D is a specialist tool. I shoot mostly wildlife and landscapes and my GH2 will remain my main camera for most of the shots. The GH2 can handle most situations very well. The 50D comes in at very strong backlight situations. Like straight or near straight into the sun at sunset situations where preserving some extra shadow detail and subtle tones is preferred over total clipped shadows.
I think ML RAW has a couple more stops headroom over GH2 if you follow the ETTR hints and expose just before the histogram shows "over". I compared that to the ML h264 histogram and the RAW ETTR pushes the exposure way beyond the point I would choose in h264 mode. In post (Adobe RAW converter) there are a lot of options to recover what's needed. RAW dual iso video would be nice but RAW and some noise filter are pretty great too.
So for now I grab my 50D only at strong contrast situations in 1080p cropmode, for instance when skies offer interesting cloud formations to preserve. The 1x mode is nice for 720p.
Quote from: LEVISDAVIS on October 07, 2013, 11:31:33 AM
Will make time for a test for sure...
Here is a color corrected image from the VAF filter test with the Promaster UV filter in place using Capture 1 trail version to export flat 16-bit Tiff image and then applied Color Correction in AE with Synthetic Aperture to create this look... (Take notice to the detail and the lack of moire! Obviously the color is jumping out in a great way, right?)
Strange dimensions. What was the resolution of the original png? Maybe you can share one PNG frame?
Yeah... 2046 by 1152 upscaled using DNG in Capture 1 (enables upscaling images upon export)... Should be a 2048 by 1152; however, Capture 1 stated the resolution of 2046 by 1152 even though I applied a 2048 by 1152 dimension. Interestingly, the 2046 number was highlighted in red (almost as if Capture 1 limited the resolution to this number by default).
Quote from: maxotics on October 07, 2013, 02:53:15 AMas for a pixel having value of 0 to 255, instead of 16384. I'm talking about before de-bayering which is what the camera records to RAW in, either red, green or blue values.
I think you've got that wrong. The Canon DSLR record the uncompressed bayer data from the sensor which has a color depth of 14 bit per pixel. Since it's bayer data, you get 50% green, 25% red and 25% blue pixels and each of them has a value of 0 to 16383, even before the debayering. That's also the reason why a raw video with a reslution of 1728 X 972 at 24 frames per second wouldn't be 40 Megabyte/s but 70 Megabyte/s.
@TrulyRAW and @CFP, there I go, spreading dis-information myself! Just when I think I have a handle on this stuff!
That makes sense! So when ML writes the buffer to the card it's writing each pixel as a 14-bit value?
And does that give something like 14 trillion color combinations? 16k x 16k x 16k?
Thanks!
Max
Quote from: rockfallfilms on October 07, 2013, 11:11:10 AM
That extra dynamic range could be the difference between blowing out the windows or not, definitely worth it in my opinion.
Unfortunately, in the case for my 50D short, in order to expose correctly for my subjects, blown out windows is something I had to contend with. While the 50D has more dynamic range, it's not 14 stops.
Even so, the 50D is a great RAW machine.
Quote from: D.L. Watson on October 07, 2013, 05:49:03 PM
Unfortunately, in the case for my 50D short, in order to expose correctly for my subjects, blown out windows is something I had to contend with. While the 50D has more dynamic range, it's not 14 stops.
Even so, the 50D is a great RAW machine.
Oh I see. Did you shoot without lighting indoors then?
Nothing in the price range of the 50d would perform as well in post production...NOTHING.
You can transform 50d raw video into the most filmic, emotive scene you can imagine. Its just a straight fact, doesn't compare at all to the GH2 or GH3.
Quote from: rockfallfilms on October 07, 2013, 07:22:46 PM
Oh I see. Did you shoot without lighting indoors then?
Ideally, yes - if you spent the time to light the scene to prevent blown out windows, you could extend the dynamic range. But I could do that with any camera.
I don't want to come across like I'm hating on the 50D - it's just 200 gigs for a two minute short film is outrageous. The short film I'm in post-production with would have taken at least 10 terabytes of space. That adds up.
People can talk about how great of a bargain the 50D is, but someone can find a great deal on a high-quality car engine - but you still need to buy the rest of the car for it to actually be functional - and those accessories bloat the actual cost.
is there a big difference in highlight and shadows and noise between 50d and 5d mark 3?
For GH2/GH3/ARII/RED/ETC you still need the accessories. Price will bloat anyways.
Just you'll be buying less memory cards w/ GH3.
I think we need some sort of raw compression after the fact (some stuff tries but its not seamless). And maybe in place playback/render to sweeten the deal. This would push more widespread adoption + usability.
Raw is still raw though... how much space does red footage take up?
People complain about the cons of the raw file sizes as if they had before something nearly as good as 14bit depth raw video. But before, you only had two choices: videotape and celuloid (later h.264, mpeg, dvcpro, etc). The one used in cinema production was of course more difficult to manage than videotapes, but that's the price you had to pay to get the best IQ.
Now, you have an option: work with the equipment you have, learn how to use it, and in my opinion, with ML raw 14bit, you really have to be more accurate every time you press the record button. That's efficiency, and that's what people did before, not wasting meters of celluloid and being precise in your work. The same applies with raw.
I never got to shoot on film but this is 90% similar from everything I read... film scans would be same/larger than this.
Quote from: 1% on October 07, 2013, 09:50:55 PM
I think we need some sort of raw compression after the fact (some stuff tries but its not seamless). And maybe in place playback/render to sweeten the deal. This would push more widespread adoption + usability.
We already have that, RAW to Cineform 422 (raw2gpcf.exe). It hardly adds any time from camera to NLE.
Unfortunately, the world is split between H.264 users intoxicated with sharpness and silly intra-frame CODEC adjustments on the Panny cameras, and RAW "graders" who over-adjust every last bit of color information.
If we had a solution that interpolated focus pixels from raw and created Cineform / ProRes files in one step I really believe the latest Canon cameras, like the EOS-M, would take off. I think they will anyway.
I'm telling you, 1%, that EOS-M has legs :)
Quote from: D.L. Watson on October 07, 2013, 09:37:38 PM
Ideally, yes - if you spent the time to light the scene to prevent blown out windows, you could extend the dynamic range. But I could do that with any camera.
Of course that's true but with more initial dynamic range the lighting package on the 50D would be also be smaller. I tend to light everything, so more dynamic range just makes it easier for me to get the lighting how I want it on set.
What really draws me to Raw are the post options, I just like having more options when it comes to grading.
If I said, "Don't worry about focus, you can fix it in post" everyone would go berserk. But if someone says you can fix missing colors in H.264, people believe it?! ;)
I did some shoots with my 50D in raw and shoot about 6Gb so there where 2 files i converted them with. rawmagic 1.0 beta 4.
but i always get this weird unusable pictures. http://www.flickr.com/photos/39003529@N06/10148008143/
does anyone know how i can fix this problem, because i want to shoot some interviews.
so i need to record longer than 1min 20sec?
Quote from: anuberak on October 08, 2013, 03:44:03 AM
I need to record longer than 1min 20sec?
I'm no expert, but I wouldn't recommend that. As the sensor warms up it gets noisier. I have no proof, but that's what I see. I get similar images to those when something goes wrong with the live view. You may want to turn off live view? A dev could answer that. I wouldn't use the 50D for anything over a minute, 3 minutes max. If you do get long captures, PLEASE share! Eventually I'll try it myself. I just don't think safe for production. If you do that, you should record safe H.264 with a backup camera.
MLV or raw rec?
This camera you *have* to kill the dialogs to not get those when you're recording. It goes off every reboot.
QuoteIf we had a solution that interpolated focus pixels from raw and created Cineform / ProRes files in one step I really believe the latest Canon cameras, like the EOS-M, would take off. I think they will anyway.
But only in crop or zoom.. otherwise its effectively squished 720P. I'm suprised more people don't record 5x there, I guess no display filter
Quote from: 1% on October 08, 2013, 04:22:04 AM
I'm suprised more people don't record 5x there, I guess no display filter
I think that is because of the total cropfactor of 4x. I have a tamron 11-18 and on the canon it is great because in a forest you can capture an image that looks like a forest. The cropfactor makes it a 44mm and trees don't fit in there any more. Walking backwards could work and with a decent centre resolution and with little distortion the image looks great. Very detailed 1080p. If that doesn't work i'll go for a dualiso timelapse on the old fashion shutter.
I don't choose between RAW and H264. I just pick the one that fits the situation best. And sometimes I shoot with both the see what works best in post. My lenses are adapted to canon ef and fit on both cameras. Except for my tamron on the GH2. It lacks control over both aperture and AF. I want to switch that one for a nikon version and use a Nikon G to Canon EF adapter to gain manual control over aperture. Hope that works.
Quote from: rommex on October 06, 2013, 02:46:12 PM
Did anyone succeed to open Cinema DNGs from Canon 50D in Resolve 10 Beta? In my case I have immediate CRASH (
Beta 1 was ok,but since Beta 2 Resolve 10 crash every time I try to open a Cinema DNG, even going to a directory with some of these files with the Resolve 10 file explorer crash it straight !
Quote from: 1% on October 08, 2013, 04:22:04 AM
But only in crop or zoom.. otherwise its effectively squished 720P. I'm suprised more people don't record 5x there, I guess no display filter
Yes, I'm only shooting in crop mode now. On the EOS-M, I believe it's only 3x, because the lens is closer to the sensor. Anyway, my Sigma 10-20mm works well in crop mode, 45mm. On the 50D, it's 5x, so not I'm getting 10x1.5x5 or 75mm. The lens to really have is the Sigma 4.5mm 2.8. On the EOS-M is would be 21mm, the 50d, 34mm. Sweet! I'm SO CLOSE to getting that lens, but the following stops me from pulling the trigger.
1. Used, the lens is $550 and it's not very useful except for this crop-mode purpose.
2. An $800 (new) lens is moving way from the inexpensive nature of ML and the 50D/EOS-M
3. If the BMPCC were available I could put my 14mm MFT on it and for an extra $500 (vs 4.5mm lens) have 1080p and straight to ProRes.
At this point, I'm going to continue my experiments with reducing moire in non-crop mode and use my 10-20mm in crop mode, which I'm very, very happy with.
But for those of you reading this, looking for wide angle on the 50d, I'm pretty sure that camera, with the 4.5mm in crop mode, would be a killer combination. Short of that, you can pick up 8mm lenses for around $200. With an effective 60mm on the 50d, in crop mode, you could shoot an indie film, IMHO.
4.5 isn't fish eye? Wouldn't you have to deconvo the whole thing?
I sent my tokina 11-16 in, want to try that, esp on a FF (its 11*-1.6 factor). I guess on APS-C like M/50D/7D it might not be enough even though the 1x on the 7D is much nicer looking vs both of these.
Quote from: 1% on October 08, 2013, 04:32:27 PM
4.5 isn't fish eye? Wouldn't you have to deconvo the whole thing?
I sent my tokina 11-16 in, want to try that, esp on a FF (its 11*-1.6 factor). I guess on APS-C like M/50D/7D it might not be enough even though the 1x on the 7D is much nicer looking vs both of these.
The "fish-eye" name is what photos look like at that focal length / aspect ratio. A 10mm would be considered fish-eye, but when in crop mode (45mm) does not look that way. Here is some footage I shot yesterday in 2.35:1 with the EOS-M. Straight to Cineform. (sorry this is a 50d thread, but if you like this you'd LOVE it on the 50D).
As you can see, doesn't look fishy at all :) I can't see that the 4.5 would be any different, except that it would look 21mm.
What is the 1x for the 7D you mentioned? Is that a crop mode without moire?
Normal LV... so lenses work as intended. there is moire but only on moire producing stuff.
Its not fisheye in 5x either? Thats good news, I wanted to get the 14mm in case it did but if they jerk me on my repair I can get the smallest maual samyang and just live with defishing the photos.
There was barrel distortion with some of my previous videos where I used the 0.22 Wide-Angle converter lens. You'd definitely need to so some corrections using those converters.
But I haven't experienced any "fish-eye" effects on any "real" lens in crop mode. So your 11mm, cropped to any non "fish-eye" focal length should look perfect. That's a great lens to have with the EOS-M, BTW. I love my 10-22mm.
The only issue, as I understand it, is that lens is tuned to deliver maximum sharpness at its intended focal length. When you go into crop mode, you're stressing the lens optics, so to speak. I believe this is a problem with all these consumer RAW solutions though. The trade-off is well worth it.
In short, you shouldn't need to de-fish, say, the Samyang 8mm in crop mode.
Quote from: vyskocil on October 08, 2013, 01:52:44 PM
Beta 1 was ok,but since Beta 2 Resolve 10 crash every time I try to open a Cinema DNG, even going to a directory with some of these files with the Resolve 10 file explorer crash it straight !
I just got the clarification from BMD Support:
That issue should be sorted in the next Beta release. I don't have a time estimate for when the next Beta will be released.
http://forum.blackmagicdesign.com/viewtopic.php?f=3&t=13534&p=85981#p85981 (http://forum.blackmagicdesign.com/viewtopic.php?f=3&t=13534&p=85981#p85981)
So in order to have the ability to process ex-ML files we have to roll back to R9.
Quote from: rommex on October 08, 2013, 07:23:29 PM
I just got the clarification from BMD Support:
That issue should be sorted in the next Beta release. I don't have a time estimate for when the next Beta will be released.
http://forum.blackmagicdesign.com/viewtopic.php?f=3&t=13534&p=85981#p85981 (http://forum.blackmagicdesign.com/viewtopic.php?f=3&t=13534&p=85981#p85981)
So in order to have the ability to process ex-ML files we have to roll back to R9.
i just reinstalled Beta 1 and it works again now.
Quote from: rockfallfilms on October 08, 2013, 08:53:20 PM
i just reinstalled Beta 1 and it works again now.
Nice to know. Thanks!
Quote from: D.L. Watson on October 07, 2013, 09:37:38 PM
Ideally, yes - if you spent the time to light the scene to prevent blown out windows, you could extend the dynamic range. But I could do that with any camera.
I don't want to come across like I'm hating on the 50D - it's just 200 gigs for a two minute short film is outrageous. The short film I'm in post-production with would have taken at least 10 terabytes of space. That adds up.
People can talk about how great of a bargain the 50D is, but someone can find a great deal on a high-quality car engine - but you still need to buy the rest of the car for it to actually be functional - and those accessories bloat the actual cost.
Shot a short on the MKIII Raw and even with the original .RAW files in combination with CDNGs and graded ProRes 4444 of every shot I only have a single terabyte. That's 17 minutes of edited footage and probably about 2 hours of raw footage.
The biggest advantage creatively with RAW is being forced to shoot like celluloid. We slated everything, got only the shots on the shot lists, and got stellar on location audio. My scripty noted the good takes so in the edit, it flew. Very feasible for creative work.
@1% a 5 minute non performance based music video took up around 200 GBs from the RED ONE in 2k at 120fps.
So 2K at 24FPS would be like 40GB per 5 min?
And people are complaining :)
Quote from: 1% on October 09, 2013, 05:06:22 AM
So 2K at 24FPS would be like 40GB per 5 min?
And people are complaining :)
More like per 7 or 8 minutes. Definitely comparable.
I don't know how you got 200GB for 5 mins 2K on RED, it's more like 1GB per minute at 24p, so 120 should be around 5 GB, so way better than CinemaDNG.
And it couldn't be otherwise, or REDCINE raw compression wouldn't be so famous!
Quote from: maxotics on October 08, 2013, 05:15:47 PM
The "fish-eye" name is what photos look like at that focal length / aspect ratio. A 10mm would be considered fish-eye, but when in crop mode (45mm) does not look that way. Here is some footage I shot yesterday in 2.35:1 with the EOS-M. Straight to Cineform. (sorry this is a 50d thread, but if you like this you'd LOVE it on the 50D).
As you can see, doesn't look fishy at all :) I can't see that the 4.5 would be any different, except that it would look 21mm.
Thanks for the fisheye crop videos and talk. Was just chatting with D.L. Watson about the 8mm Rokinon in crop mode. Seems like a good buy, and that these fisheye lenses are turning out ok for crop shooting. Also noticed you are around Porter Square area. I'm right across the river in Brighton.
Quote from: riccardocovino on October 09, 2013, 02:13:42 PM
I don't know how you got 200GB for 5 mins 2K on RED, it's more like 1GB per minute at 24p, so 120 should be around 5 GB, so way better than CinemaDNG.
And it couldn't be otherwise, or REDCINE raw compression wouldn't be so famous!
Five minute edit. Total amount of shooting was closer to 40-45 minutes. Our figures are the same.
@dsManning. Nice to know I'm not the only RAW nut in New England :) Maybe we can organize a ML Raw and Black magic meet up at some point. Maybe there already is one.
Deleted.
what kind of benchmark do you want? Its a few MB away from recording the whole zoom size at 23.976.
(//)I know. Hit like 89.3 MBs on a KombuterBay 64GB 1000x. GD on.
With the latest Tragic lantern thanks 1% and everyone.
Quote from: rockfallfilms on October 08, 2013, 08:53:20 PM
i just reinstalled Beta 1 and it works again now.
Resolve 10 Beta 3 is out, but I didn't tried it yet
Just to clarify for everybody, because there's a general misunderstanding here:
File size comparison between CinemaDNG and REDCINE at 1920x1080 24P
CinemaDNG: 4GB / minute for 14bit RAW
REDCINE: from 0.4 to 1.5 GB / minute (depending on compression option) for 16bit RAW
So a compression factor would really really be helpful, now we have a "mini"RED that records 4x heavier files (at less quality).
$200 Cineform 4:4:4 or RAW?
Quote from: riccardocovino on October 10, 2013, 03:05:34 PM
Just to clarify for everybody, because there's a general misunderstanding here:
File size comparison between CinemaDNG and REDCINE at 1920x1080 24P
CinemaDNG: 4GB / minute for 14bit RAW
REDCINE: from 0.4 to 1.5 GB / minute (depending on compression option) for 16bit RAW
So a compression factor would really really be helpful, now we have a "mini"RED that records 4x heavier files (at less quality).
Isn't RAW R3D a series lossless jpeg2000 frames?
Yes, it's a variant of JEPG2000.
It has wavelet compression, which leads to virtually zero artifacts and no blocking.
And stores info at 16 bit, allowing for RAW-like grading.
Compression ranges from 3:1 to 15:1 or 18:1, I don't remember, But usually it's used around best quality settings.
Even the long-time hoped 10bit RAW conversion while writing data would be a huge benfit on file size without affecting quality in a visible way, but all efforts went wrong..
Quote from: riccardocovino on October 10, 2013, 04:19:33 PM
Yes, it's a variant of JEPG2000.
It has wavelet compression, which leads to virtually zero artifacts and no blocking.
And stores info at 16 bit, allowing for RAW-like grading.
Compression ranges from 3:1 to 15:1 or 18:1, I don't remember, But usually it's used around best quality settings.
Even the long-time hoped 10bit RAW conversion while writing data would be a huge benfit on file size without affecting quality in a visible way, but all efforts went wrong..
As far as I'm concerned, being able to convert RAW to R3D RAW would be a wonderful thing. From the card, to a console based binary or GUI, to the drive in R3D would be pretty neat, I'd say. Premiere works well enough with R3D files, as do other NLEs.
Even if it means I just have to delete the files on the cards more frequently, preventing unnecessary disk usage could surely be a help to many.
I don't mind creating a more film-like workflow, resulting in tight slating--editing would be a breeze, and it breathes new life into creative storyboarding.
Quote from: maxotics on October 10, 2013, 03:32:37 PM
$200 Cineform 4:4:4 or RAW?
I'm seriously considering this myself. Cineform seems to be what pretty much everyone is asking for in terms of a very good way to reduce file size and keep the quality gains of RAW. I'm still investigating this option but it looks very compelling.
If only they would fix the debayering.
What's the problem with the debayering, 1%?
One could also just use any traditional DNG to TIFF conversion/grading and then to Cineform. My guess is that you'd lose little if you did that and straight to the free 4:2:2: version, through virtualdub or something.
Well after AE I go to cineform.... but I want to just do raw -> cineform straight, not raw -> dng -> ae -> cineform
With the debayering when using raw2gpcf I get lots of artifacts on lines and other areas, esp on digic V stuff like 6D. Its still present on 50D/7D but a bit more forgiving I guess. If you want to delete the .raw files and just leave the cineform AVI its not an option yet so not much space saving.
I just thought of a feature, maybe there is one, but I couldn't locate it.
Framing in zoom mode is troublesome, because it is off sometimes.
How about the camera could take one frame (in crop, with selected resolution, exactly how it is going to look in ML RAW), then display it for a couple of seconds in color and stuff. It would reassure me that the footage is going to be what I had in mind while shooting.
I know I can do that with recording a couple of frames, and then playing them back, but playback is grey, not realtime and I think one fromegrab could also be used as a thumbnail.
What do you think?
That's interesting, I've wondered about that. The moire from the EOS-M seems much worse on Cineform than when I labor through some DNG to tiff stuff. That explains it. They must be using a simple bicubic, instead of Amaze, VHD? or even ACD? Too bad.
Quote from: Mkolaj on October 10, 2013, 09:58:33 PM
Framing in zoom mode is troublesome, because it is off sometimes.
I had this problem too. 1% pointed out that if you press the joystick button it locks the LV into the current framing. That seems to work for me, at least when I remember to do it! :)
I'm stuck with this workflow, simplest and most straightforward for me:
Conversion directly from flash card with RAW2CDNG with 12bit option enabled (saves 15% space) and import in Resolve 10 for CC and editing.
It has its flaws, but it's damn quick!
Will try that Resolve workflow, thanks!
And on the de-bayering 1%, now I know where those blue dots are coming from in 50d footage, in between the leaves of a tree in a bright sky.
I'm new to raw video and trying to decide on a memory card. If I bought the Lexar 16GB 1000x, how long would I be able to record 1920x1080? I've got a 50D.
Quote from: roopepal on October 11, 2013, 03:04:26 AM
I'm new to raw video and trying to decide on a memory card. If I bought the Lexar 16GB 1000x, how long would I be able to record 1920x1080? I've got a 50D.
1920x1080 at 23.976 is 82.9mb/s. Looks to be about 3 minutes and 20 seconds.
(http://25.media.tumblr.com/9e32ad67ac457b9bc8520f6ce58fa581/tumblr_muhcy70Hx31rkqob0o1_1280.png)
Okay thanks. What about how many frames I would get before it stops recording? Or is the 16GB version capable of continuous, I think not?
Quote from: roopepal on October 11, 2013, 03:59:13 AM
Okay thanks. What about how many frames I would get before it stops recording? Or is the 16GB version capable of continuous, I think not?
With the Go Faster Tragic Lantern build, I've been recording continuously, using the Lexar 1000x 32GB.
If you want to find that, search the thread.
Quote from: vyskocil on October 10, 2013, 10:02:03 AM
Resolve 10 Beta 3 is out, but I didn't tried it yet
ML DNG's working fine again in Resolve 10 Beta 3
Had an unexpected break for a few days so just catching up.
@1% - what's up with compiling? Modules don't get added to the zip ???
The delete if failed thing. I think i just fixed it correctly.... the make -C works
Quote from: rockfallfilms on October 11, 2013, 10:29:23 AM
ML DNG's working fine again in Resolve 10 Beta 3
Thanks vyskocil & rockfallfilms for both reporting this broken and fixed!
Quote from: 1% on October 11, 2013, 04:43:47 PM
The delete if failed thing. I think i just fixed it correctly.... the make -C works
I must be doing something wrong.
I used make -C platform/50D.109 zip which made a zip but still no modules. Do modules need compiling individually now?
No, I just ran your command after the commit an hour ago and I have modules in the zip... heheh, I think I'll use this now so I only have to copy modules from 1 place.
@1% - Thanks, working now :)
***************************************************************************************************************************************
50D users - NEW TRAGIC LANTERN 50D BUILD UPLOADED https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip)
***************************************************************************************************************************************
Sorry, no time ATM to post detailed list of updates but here are some brief highlights:-
Great looking new display bar with new 'Histobar' - select in raw histogram settings. (Tip: in the Display menu>Advanced set to auto 4:3)
New modules - Raw_Bolt (bolt_rec is back) Focus Info module (not tested this myself yet)
MLV_Rec seems faster and less prone to corrupt frames (when Dialog timers are disabled) - Not fully tested it.
plus lots of small tweaks and fixes and new stuff in the menu (Lens info prefs, config startup presets, etc)
Download and try it only if you know what you're doing!
As ever, don't thank me, thank 1% for the 50D branch of Tragic Lantern and the other hard working devs for their hard work!
Please don't forget this: http://www.kaizou.org/2013/04/three-golden-rules-open-source/
So MLV rec is working without crashing here?
@a1ex - sorry, I'll read it ::)
@1% mlv is working for me - I renamed it in the menu to 'Raw Video (MLV)'.
No crash on 2nd recording? Its doing that on pretty much everything else, whoa.
Ok dumb question here, but every time I shut my 50d down I have to reset the resolution, turn raw on, turn movie mode on, etc. My camera says there's a directory missing when I start it up, could that be causing it? I just installed this today
Also is there a good crop mode tutorial anywhere? Whenever I follow the ML one my screen shows an extremely pink frame. Thanks
Quote from: Andy600 on October 11, 2013, 06:30:05 PM
***************************************************************************************************************************************
50D users - NEW TRAGIC LANTERN 50D BUILD UPLOADED https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip)
***************************************************************************************************************************************
The new design looks lovely, but the display bar seems to be reporting a different frame rate to whatever I select in the ML menus (1/51 selected, being displayed as 1/74). Is anybody else having this issue?
Quote from: Andy600 on October 11, 2013, 06:30:05 PM
config startup presets
I was thinking of sharing preset files for certain tasks.
Like one just for raw/mlv video and strip everything else from the menu. Just a few relevant items. It's great for newcomers. And another preset for timelapses.
Quote from: bart on October 11, 2013, 11:05:37 PM
I was thinking of sharing preset files for certain tasks.
Like one just for raw/mlv video and strip everything else from the menu. Just a few relevant items. It's great for newcomers. And another preset for timelapses.
Hi there!
Yes, I´m getting the same issue as you and the display is showing some anoying shutter speed numbers than the ones that are selected! :(
VERY STRANGE thing!
Cheers!
Asier.
Finally figured out what caused my freeze problem with the last several builds of tragic lantern. I have a canon 50 1.4 and some m42 zeiss lenses, which all share an m42 adapter with a focus chip. With the canon 1.4 it works fine (although I don't see mlv in the latest build, or it has replaced raw_rec?); when I put the adapter on with one of the other lenses, though, every time I try entering live view with the raw module on, the camera freezes to a blank screen and I have to take the batteries out. Weird, huh?
Quote from: Andy600 on October 11, 2013, 06:30:05 PM
(...)
***************************************************************************************************************************************
50D users - NEW TRAGIC LANTERN 50D BUILD UPLOADED https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip)
***************************************************************************************************************************************
(...)
Great looking new display bar with new 'Histobar' - select in raw histogram settings. (Tip: in the Display menu>Advanced set to auto 4:3)
Does RAW HistoBar work in image review? I have it only in LV, though the info says:
"Will use RAW histogram in LiveView and after taking a pic."
Maybe some other setting is needed too?
Quote from: 1% on October 11, 2013, 07:39:56 PM
No crash on 2nd recording? Its doing that on pretty much everything else, whoa.
Had no crashes with MLV. Have you got the IME modules loaded?. I shot 64GB of MLV footage (over a few hours with reboots inbetween) to test for corrupt frames and they are still happening intermittently even when shooting smaller frame sizes. Sadly, I just can't trust MLV on anything important ATM :( I'm sticking with Raw_rec (never has problems)
Also had an issue where the back wheel stopped working and had to delete configs to get it back. Trying to find what caused it.
@akumiszcza - Histobar is only working in LV for me
@Bart - good idea :) - I had one user msg me having problems for weeks so i sent him my build + config and it fixed it. ML can be a little too techy (or too much hard work) for some shooters ...but they still wanna use it! ;)
Re: shutter speed issue - I had the same thing happen but only with certain config presets. Also, shutter speed readout appears frozen in the ML menu but actual shutter speed can still be changed ???
When it changes on top screen it doesn't mean your actual LV shutter changes.
FPS is still limiting the blanking... still needs expo override.
No I didn't load IME but it worked without those before. Seems like its working on 5DII/50D/5DIII and thats it.
New MLV is still crashing on me.
Ok, found the commits, works now.
Got this crash log today:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Oct11.50D109
Mercurial changeset : dd08a07137b8+ (unified) tip
Built on 2013-10-11 15:48:27 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 200K + 3716K
also this log:
http://pastebay.net/1321285
Are you shooting in M mode?
Yes. M mode, raw.
Auto iso?
Nope. Only White balance is auto.
My settings are the defaults + all the IME modules and raw_rec. Global draw on, small hacks on, exposure override on, fps override off, movie mode on (tried both ways). Could there be something wrong with my card, cause I'm pretty sure I have all other things right, but it still crashes when I go to Lv with raw on or when I turn raw on when in LV?
I have auto power off from canon set to 4 minutes, but turning it off doesn't seem to help.
Try setting a manual white balance. Does that help.... some part of auto exposure is crashing.
Still crashing. I'll do a fresh install on a different card and see if it helps.
Tried a new card - changed nothing on the settings. Still a no-go.
I'll restore the settings in camera to the canon default. (video system in canon menu was set to PAL - I live in europe - does this count for anything?)
I restored the factory settings (video system is still PAL). I think this got it working, not sure if it will crash again, but it didn't the last couple of times. btw, is the raw module the old raw_rec or this is the new mlv format. Cause it produces files with .RAW extensions..
I know why it crashed:
Quote244: 790.282 [LV] AF Mode FACE
245: 790.303 [LVFD] FD_SetFaceSearchState FD_INITIALIZE
246: 790.316 [LV] FD_FACEAF_ON
You set AF to "face detection".
mlv_rec = mlv
raw_rec = raw
Yep - resetting canon settings worked it out. Thanks.
So there's no mlv in the latest build from andy? I guess copying the module from the one before isn't a good idea?
Dunno. Usually its there. You don't have to reset the settings, turn on lv face detection, crash, turn off face detection, no crash.
Yep. got it. You're a lifesaver.
Quote from: johansugarev on October 13, 2013, 12:44:06 AM
Yep - resetting canon settings worked it out. Thanks.
So there's no mlv in the latest build from andy? I guess copying the module from the one before isn't a good idea?
It's in the zip.
Uploaded a couple of ProRes 444 videos of the Canon 50D.
https://copy.com/f7jD7CnQsUZWeO9L (https://copy.com/f7jD7CnQsUZWeO9L)
Each video is the same. However, each video shows very different characteristics that the 50D has to offer, especially considering the VAF from Mosaic Engineering. Footage was debayered and upressed from 1584 - -> 2048 using Capture One trial software. The color correction was finalized inside of After Effects using Synthetic Aperture.
... Each file is about a 160MB if you want to download them. Also, there are some RAW DNGs available for download in this same link. The DNG files are taken from this same test shoot if you want to apply color-correction yourself.
@1% - with the latest commits mlv_rec compile is skipping because of a problem with mlv_dump.
mlv_dump.c:1524:62: error: 'mlv_styl_hdr_t' has no member named 'picStyle'
make: *** [mlv_dump.exe] Error 1
So I compiled mlv_rec separately and recorded a few shots but I can't convert/dump them to .raw
Exception! Header not recognized: 'STYL'
and mlv2dng just crashes out.
Try MLV2dng from g3ggo's package he made for 5DIII. Does that work.
Quote from: riccardocovino on October 10, 2013, 10:16:13 PM
I'm stuck with this workflow, simplest and most straightforward for me:
Conversion directly from flash card with RAW2CDNG with 12bit option enabled (saves 15% space) and import in Resolve 10 for CC and editing.
It has its flaws, but it's damn quick!
Speaking of compression, have you guys tried the lossy option of Raw Batchelor 3 for windows?
It uses Adobe DNG Converted when extracting DNGs from RAW. It's supposed to maintain IQ and decrease File Sizes.
Quote from: 1% on October 13, 2013, 04:31:06 PM
Try MLV2dng from g3ggo's package he made for 5DIII. Does that work.
No mlv2dng in the zip ??? but tried his mlv_dump. It works, kinda though obviously the meta data is stripped and I get
Unknown Block: NULL, skippingJust tried several 1 - 3 GB MLV files and no corruption. Not sure if this is a fluke.
This is just another n00b question which most likely has a very simple answer.
I am recording h264 w/ fps override @ 23.976, ISO 100, f/1.8.
Magic Lantern displays that the shutter speed is 1/48 (the amount I am after, to achieve standard cinematic motion blur) while the analog display on my camera displays 1/80.
Which is the accurate reading, and if ML's is not, how do I get 1/48 or 1/50? Do I use the Canon reading over ML's?
I read the EXIF data from the movie and sure enough it reads that the capture shutterspeed was 1/80. (1/83, to be exact.)
Suggestions are appreciated. Thanks!
the ML info is the useful one
The top screen shutter is photo only. Not tied to LV at all. 50D likes to change your "shutter" by setting digital iso gains and stuff like that so don't forget expo override.
Thanks for the info. Much appreciated.
Hi guys,
Tried this new version of tragiclanter, didnt really worked for me. The screen gets white bars in the "off picture" settings... Got back to the older version.
I've tried to read about "bolt mode" but didnt found many information about that. Although I dont work with this version, got me curious!
By the way, I would love to have the adobe CC just to "pump up" the workflow!!
I thought by working with CinemaDNG in ResolveLite would be fast, but I was really wrong (5/6FPS...)
Only one more thing, it is possible to change the name of the RAW files in camera? If I could do this, it would be a lot easier to get organized all the Post-Prod workflow...
Thank you very much
White bars?
Quote from: 1% on October 14, 2013, 10:27:10 PM
White bars?
Yep... I get the "picture" normaly but the outlines of the image turn all white, making the histogram and waveform and f/number ISO not "seeable"
dont know why, but it runs like this as soon as I've installed this last version. Hum, and another thing that happened, the scrolling weel in the back of the camera stoped working. Now I have to do everything with the "joystick". :-\
Something went wrong...
I have a question about the ".RAW" file:
It is any program or version that automaticly extracts all ".RAR" into one and only ".RAW" file? Just because I am really trying to get organized and in this terms, and because of the "FAT32" data issue, the ".RAW" files break up into 1 ".RAW" and then several ".RAR" files.
How can I manage to "Paste" them in one ".RAW" file and than delete every ".RAR"? I am working in a Windows7 OS...
Thank you very much!
I'm guessing you're seeing zebra or raw_rec cropmarks as "white outlines" but maybe a shot in the dark.
Scroll wheel, not sure, I know there is a lock switch but mine is still working.
Quote from: 1% on October 14, 2013, 11:28:33 PM
I'm guessing you're seeing zebra or raw_rec cropmarks as "white outlines" but maybe a shot in the dark.
Scroll wheel, not sure, I know there is a lock switch but mine is still working.
Thanks for the recomendation. I've shut off the zebras and it still makes the outlines all white. It is like the white is flickering and I get to see in 1ms the specs and than it turns all white again... In a little bit it turns again 1ms the specs "normally" and than white again... Really dont know what is the problem.
Help me out with a pic or screenshot.
Hey here is a fashion short done with the 50D. The quality is really amazing on the camera. I think 800iso is the limit before the noise gets too bad, the quality kind of suffers towards the end because I didn't feed it enough light, but between neat vid and raw I was able to make it usable.
I've been using the ACR--AE--PPro workflow, but I ran into some problems. If you view the video at the highest resolution (original or 1080p) there is some weird stuff going on around the model's face at the beginning (maybe aliasing?). It wasn't there when I transcoded from raw to 444 10 bit DNxHD out of AE, but it showed up with the compression when I exported from PPro to .H264.
I did some test and this doesn't seem to happen when I use the 16:9 resolution, but only when using the 4:3 1280x960 resolution for anamorphic shooting. Maybe the increased 2560x960 resolution has something to do with creating moire when compressed the second time (it does not show up if I go from raw to .H264 out of AE on the first compression).
Other than that, I'm thinking about switching to the Resolve workflow... will that create a cleaner video vs my previous workflow? And is there a source for any tutorials on Resolve, the interface looks like a jumbled mess to me.
Nice images, the name of the author is Edgar ALLAN Poe, you wrote on the video ALLEN (by the way i made a comic based on The Fall of The House of Usher) ;D
http://caidacasadeusher.blogspot.com.es/
Quote from: simulacro on October 15, 2013, 12:02:05 PM
Nice images, the name of the author is Edgar ALLAN Poe, you wrote on the video ALLEN (by the way i made a comic based on The Fall of The House of Usher) ;D
http://caidacasadeusher.blogspot.com.es/
Thanks Simulacro, great catch! Good thing this was a fun side vid and not a paid thing, lol
Nice comic too! I'm curious do you ever incorporate any comic stuff into your filming?
Received a new Komputerbay 128 GB 1000X today and I can't get the card to do a firmware update on my 50D. Wondering if anyone has found a way to make the card work...
Long story short... I had bought a 128 GB 1000X back in July and it work with my camera. However, the write speeds were about 2 - 5 mb/s too slow. Started thinking that with the latest builds that that same card might be applicable...
Any help would be greatly appreciated.
So tell me, I just did the benchmark with the latest nightly build on 50D and Sandisk 16GB Extreme Pro 160, which one of these is the relevant number?
(http://f.cl.ly/items/011n1z0Y373x2a3d182y/TEST.BMP)
The one you see while recording?
Quote from: DJG on October 15, 2013, 09:40:16 PM
Thanks Simulacro, great catch! Good thing this was a fun side vid and not a paid thing, lol
Nice comic too! I'm curious do you ever incorporate any comic stuff into your filming?
Thanks too :) comic is an influence, but i haven't used it for an specific work. It helps when storyboarding or simply putting everything in order in my mind
Quote from: roopepal on October 16, 2013, 07:06:39 AM
So tell me, I just did the benchmark with the latest nightly build on 50D and Sandisk 16GB Extreme Pro 160, which one of these is the relevant number?
Just try recording, if you drop frames then the card is too slow.
Quote from: LEVISDAVIS on October 16, 2013, 02:43:34 AM
Received a new Komputerbay 128 GB 1000X today and I can't get the card to do a firmware update on my 50D. Wondering if anyone has found a way to make the card work...
Long story short... I had bought a 128 GB 1000X back in July and it work with my camera. However, the write speeds were about 2 - 5 mb/s too slow. Started thinking that with the latest builds that that same card might be applicable...
Any help would be greatly appreciated.
Best I can recall, you have to use a card smaller than 64GB to do firmware updates and install ML. The firmware makes it possible to use the 64GB and larger cards.
In addition, you have to prepare 64GB cards a slightly different way, I believe. I suggest starting with step 1 on the ML Install Wiki, so you can see what it suggests, and why. ::)
Hey does anyone know how to get the raw grayscale preview to stop flashing? It only works properly when I'm recording.
Is anyone else seeing this error building from source?
../../src/gui-common.c:29:12: warning: 'bottom_bar_hack' defined but not used [-Wunused-variable]
[ CC ] chdk-gui_draw.o
[ CC ] movtweaks.o
[ CC ] menuhelp.o
[ CC ] menuindex.o
[ CC ] af_patterns.o
[ CC ] focus.o
../../src/focus.c: In function 'focus_stack':
../../src/focus.c:260:29: error: 'focus_rack_enable_delay' undeclared (first use in this function)
../../src/focus.c:260:29: note: each undeclared identifier is reported only once for each function it appears in
make: *** [focus.o] Error 1
It's the same compiling for 600D, everything was OK yesterday and I updated just before I saw this.
Fixed that compile error.
QuoteHey does anyone know how to get the raw grayscale preview to stop flashing?
Flashing? When?
Quote from: 1% on October 16, 2013, 09:11:07 PM
Fixed that compile error.
Flashing? When?
Remember the flickering in the menu? I posted a video showing the issue after load the module. I believe it's a similar problem.
For that, I guess turn on Kill flicker in advanced menu or disable dialog timer.
Quote from: 1% on October 16, 2013, 11:14:59 PM
For that, I guess turn on Kill flicker in advanced menu or disable dialog timer.
Am I blind or is the advanced menu not on the 50d? Sorry to be a bother but I can't find either of these options. Updated to nightly build a couple days ago.
To be clear, the problem is that when you turn on greyscale preview while shooting raw that the grayscale preview only shows up every other millisecond. The camera is showing both the canon preview and the greyscale ML preview, making it extremely hard to use crop mode.
Menu -> Display -> advanced
It does slow down when you're recording by design... but I wouldn't shoot with GD on while recording.
Is there a build that includes bulb ramping also?
Quote from: 1% on October 16, 2013, 09:11:07 PM
Fixed that compile error.
Yep confirmed, thanks. But it took ages for the pull to register the updated file - I first tried when I got in about 3 hours ago and only in the last 30 mins did it register.
Looking at the Bitbucket site you committed the fix yesterday!
Hello,
I'm a 50D ML newbie. I am using Komputerbay 1000x CF card and 50D is constantly giving error when I am trying to transfer the movie files to my mac. Pictures are transferring fine. I am guessing it is because the camera does not understand the movie file types. Has anyone had this experience? When CF is used with a Kingston card reader, I can copy the movie files. But it would be nice if I don't have to take the card out every time.
I did quite a bit of search on this subject, but I am not finding the answers. Maybe I am using bad search words. If this has been discussed earlier, I apologize.
No option yet. Use a card reader.
Komputerbay will sell 128gb 1050x and 128gb 1000x CF cards that are firmware compatible for the 50D. Shipped in the 1000x to tech support yesterday, but found out about an upgrade path to the 1050x. ...Upgrading to 1050x given previous recording results of the 1000x. Will post results...
Hi to all !
I had one time my 50D block after a skipped frame... 25fps 400 iso 1/50 Manual Olympus lens with adapter 1584/892.
So I decided to benchmark my 1000x UDMA7 Komputerbay.
The buffer benchmark gave me results around 40mb/sec.
I've resent it for exchange and now I'm around 30mb/sec.........but it works.
Can someone explain the speed thing 'cause I don't understand how can it works @ 40 or even @ 30...
@ what step the dev of the 40D is ?
THX
.V
Quote from: vprocessing on October 18, 2013, 09:26:08 AM
Hi to all !
I had one time my 50D block after a skipped frame... 25fps 400 iso 1/50 Manual Olympus lens with adapter 1584/892.
So I decided to benchmark my 1000x UDMA7 Komputerbay.
The buffer benchmark gave me results around 40mb/sec.
I've resent it for exchange and now I'm around 30mb/sec.........but it works.
Can someone explain the speed thing 'cause I don't understand how can it works @ 40 or even @ 30...
@ what step the dev of the 40D is ?
THX
.V
You have the RAW picture turned off in the CANON menu? It only works if its JPEG in the CANON menu.
Hope it helps...
Quote from: joaomoutinho on October 19, 2013, 12:45:10 AM
You have the RAW picture turned off in the CANON menu? It only works if its JPEG in the CANON menu.
Hope it helps...
I always shoot with RAW picture turned on in the menu and I've never had a dropped frame. Your card is probably a dodgy one, the komputerbay's seem to be a bit hit and miss.
Quote from: LEVISDAVIS on October 16, 2013, 02:43:34 AM
Received a new Komputerbay 128 GB 1000X today and I can't get the card to do a firmware update on my 50D. Wondering if anyone has found a way to make the card work...
Long story short... I had bought a 128 GB 1000X back in July and it work with my camera. However, the write speeds were about 2 - 5 mb/s too slow. Started thinking that with the latest builds that that same card might be applicable...
Any help would be greatly appreciated.
The 64 GB cards are the best for speed. And as has been said numerous times you need something like a 32 GB or below card for flashing firmware. I just bought a sandisk 4 GB card for firmware flashing purposes.
Buy a 64 GB card and benchmark and use it. See if it hits your speed targets. If not return it. Keep in mind you have to "warm up" your card to get maximum speed.
Is there any way to get the 50D to sync beep? 8)
Hi!
I've tried several newer versions of the nightly builds but don't get the modules to work. When I start the modules it says that the will be loaded on the next reboot. I've tried rebooting and to take out the battery but the same text appears the next time I start the camera. What is wrong?
Quote from: SleeperNinja on October 20, 2013, 06:56:42 AM
Is there any way to get the 50D to sync beep? 8)
Was discussed earlier in this thread somewhere. Quite a few looked into it, but the 50D is missing the hardware on board to produce a similar beep that newer cameras give off.
Another quick brain-picking-
I'm recording h264. I can't seem to get ML back to tethering it's white balance to Canon Custom WB- It's stuck on the Kelvin adjustment. This forces me to manually determine my white balance to match my other camera rather than just using my grey card with Custom WB and tweaking (if need be) from there on the kelvin scale.
How do I get back to just tethering to Canon Custom WB?
Thanks.
Quote from: dsManning on October 20, 2013, 06:54:30 PM
Was discussed earlier in this thread somewhere. Quite a few looked into it, but the 50D is missing the hardware on board to produce a similar beep that newer cameras give off.
any beep would be better than no beep, though, I'd say.
Quote from: rockfallfilms on October 19, 2013, 03:23:01 PM
I always shoot with RAW picture turned on in the menu and I've never had a dropped frame. Your card is probably a dodgy one, the komputerbay's seem to be a bit hit and miss.
Really? This was told to me by a ML developer. So what are you saying is that is possible to shoot RAW video with the RAW picture mode ON? Everyone told me that for the RAW video to work continually, it would be necessary to turn the "RAW" mode OFF in CANON menu and get "JPEG" ON.
So, Im not getting the best quallity? Is that it?
Quote from: joaomoutinho on October 21, 2013, 05:31:43 AM
Really? This was told to me by a ML developer. So what are you saying is that is possible to shoot RAW video with the RAW picture mode ON? Everyone told me that for the RAW video to work continually, it would be necessary to turn the "RAW" mode OFF in CANON menu and get "JPEG" ON.
So, Im not getting the best quallity? Is that it?
My guess is that it won't affect the image's quality, but it may affect the memory usage, limiting resources.
As for the statement, I tend to agree. I've been leaving the camera in RAW shooting mode, and I have yet to have a magenta frame on my 50D, whereas slow cards caused me plenty of bad frames on my 550D.
I would like to note that I leave GD and h.264 video mode off, which may relieve some resource strain.
Quote from: joaomoutinho on October 21, 2013, 05:31:43 AM
Really? This was told to me by a ML developer. So what are you saying is that is possible to shoot RAW video with the RAW picture mode ON? Everyone told me that for the RAW video to work continually, it would be necessary to turn the "RAW" mode OFF in CANON menu and get "JPEG" ON.
So, Im not getting the best quallity? Is that it?
I would guess that your card is causing the slowdown. Which version of ML are you shooting with?
I always use Tragic Lantern and can shoot with Raw photo mode turned on, also global draw on, zebra, histogram & peaking and still get around 8% idle with an empty card. Once the card gets about half full I have to turn off zebra in order to maintain continuous.
I've not experienced any issues shooting this way on a 1000x 64GB Komputerbay.
What frame rate are you shooting at? I shoot at 25fps.
A short film I made shot with the Canon 50D RAW Hack. Thanks so much to the people on here for making RAW on the 50D a reality.
http://vimeo.com/77430368
Quote from: paulforte on October 21, 2013, 11:48:31 PM
A short film I made shot with the Canon 50D RAW Hack. Thanks so much to the people on here for making RAW on the 50D a reality.
http://vimeo.com/77430368
Nice editing. Vignette from the anamorphic, or in post?
The vignette is from the anamorphic for sure, but when I darkened the image in post it made it a little more present.
Quote from: paulforte on October 22, 2013, 01:48:54 AM
The vignette is from the anamorphic for sure, but when I darkened the image in post it made it a little more present.
Do you use Resolve? Could probably tone down the vignette with a softened outside node. Glad it wasn't a post choice, a bit strong in a few shots. Loved the mix of photo/video and the way it was edited. I don't have an anamorphic lens, but I would love to know, how does it behave when you go into crop sensor mode?
I could have fixed it but I just left it, wasn't that bothered. Totally agree about some of the shots being too heavy. The shots of the computer were a different lens which vignetted heavily. The lens is a Bolex Anamorphot 8/19.1.5 which only works on smaller sensors at a maximum of 40mm and full frame about 85mm, so the 1.6 crop is great. In fact, I've been using it with my Blackmagic Pocket and it's even sharper because of the 3X crop, it uses the center part of the lens not the outside, here's an example - https://vimeo.com/77268468
Hi,
can a 50D shoot 23.976/24 fps RAW without fps override?
Quote from: lomka on October 22, 2013, 03:50:34 PM
Hi,
can a 50D shoot 23.976/24 fps RAW without fps override?
no
are there any disadvantages in that? i mean does it skip frames in 30p to get 24 or is it true 24p?
If it would skip frames, it would be called frame skipping, no?
Quote from: lomka on October 22, 2013, 10:41:52 PM
are there any disadvantages in that? i mean does it skip frames in 30p to get 24 or is it true 24p?
It is recording 24 frames in 1 second. Every second of every minute.
It is not skipping frames in 1 second then skipping frames again 4 seconds later. Capish?
Komputerbay 128GB 1050x records continuous raw at...
23.976
- - 1584x1058 (almost 3:2) - - Shows no bars in the metering... Global Draw is off. (Raw photo mode is ON.)
25 P
- - 1584x1058 (almost 3:2) - - Shows no bars in the metering... Global Draw is off. (Raw photo mode is ON.)
29.970
- - 1584x1058 (almost 3:2) - - 864 frames ((Raw photo mode is OFF.)
5X Center Crop
23.976
1920 x 1080 - 1715 frames (results varied a lot) (Hacked - No Preview proved best results).
1920 x 1038 - Continuous (results varied).
Things to consider is that if you are going to push the card to the limit it want to record a short take and then skip frames. After that first short take it will record something fierce and of course continuously. This is different than the Komputerbay 64 GB card. That card seems to just get up and go and if it gets into a recording bind somehow finds a way to lower buffers. ;D
... Saw a serious increase in the 50D's ability to capture frames by disabling raw in the photo mode. However, I too typically shoot with raw enabled because 1584 x 892 at a standard frame rate is not a stretch for the Komputerbay cards. Have never gotten pink frames either.
If you haven't been following... I purchased a 128 GB 1000x card from Komputerbay about a week ago. Unfortunately, the card would not work with ML on the 50D. I contacted Komputerbay support and they had me send in the card for a firmware adjustment. At that point, I asked to upgrade to the 1050x because they stated that the 1050x would also work with the 50D after they made a firmware adjustment. Well, I got the card back from their tech support today and was absolutely able to load the firmware with success. Yes it's a 128 GB 1050x card and yet it will work with ML! Reads as a 119GB card, but it should be able to capture 128 GB without any trouble. If you notice the 64 GB 1000x cards read as a 60 GB card in the Canon 50D and it still captures a full 64 GB worth of data.
If you are interested in the card, you might want to talk to Komputerbay before purchasing the card from Amazon or ebay. They may have some of the firmware adjusted cards in stock. I don't know for sure, but I would think that they would have at least a few. Who knows?
Hello, I'm a newbie here, from Russia.
That's the great thing that you, ML, do. One can get a cinematographic camera for a fraction of a cost, not needing to get an expensive Kodak film for $100/can, to develop and scan/telecine it. All you need to start shooting in almost cinema quality is to install the ML firmware, get the quickest SD or CF card you can, and here is it. Our Russian film cameramen don't agree with me, though.
I've got a few questions and thoughts on shooting raw, the main of those is this one:
If you can get a 50D with ML, two 64 GB 1000x CF cards, a card-reader, and an external HDD connected to the notebook, then you can shoot in raw for how long you want to, for the 2 hours or so. A concert, for instance. All you have to do is to swap CF cards, copying raw files from one card to the external HDD as the second card is working in the camera. Am I right? Will the 50D overheat in a few minutes of almost continuos work?
Jpeg = 219MB
Raw = 195MB
So yea, jpeg quality gives you another buffer at the least.
Quote from: Wlad81 on October 23, 2013, 05:58:43 PM
Hello, I'm a newbie here, from Russia.
That's the great thing that you, ML, do. One can get a cinematographic camera for a fraction of a cost, not needing to get an expensive Kodak film for $100/can, to develop and scan/telecine it. All you need to start shooting in almost cinema quality is to install the ML firmware, get the quickest SD or CF card you can, and here is it. Our Russian film cameramen don't agree with me, though.
I've got a few questions and thoughts on shooting raw, the main of those is this one:
If you can get a 50D with ML, two 64 GB 1000x CF cards, a card-reader, and an external HDD connected to the notebook, then you can shoot in raw for how long you want to, for the 2 hours or so. A concert, for instance. All you have to do is to swap CF cards, copying raw files from one card to the external HDD as the second card is working in the camera. Am I right? Will the 50D overheat in a few minutes of almost continuous work?
Not quite. But possible.
Remember, it might take longer to download 64GB of RAW files, than it does to record the same amount to the other card. Heat is not really an issue when recording at continuous resolutions. If you fill up a 64GB card, in order to download faster than you can write 64GB worth of video to the other card then you have to have very, very fast hardware. Something like a Macbook Pro with a thunderbolt connection and a fast-writiing external (SSD based) hard drive with a thunderbolt port as well for maximum throughput.
Thank you so much. I've studied the topic a little more and found out that overheating is really not the problem. The main problem here isn't even the HDD speed because I really can use the simplest MacBook Pro with a Thunderbolt connection and a SATA III HDD (I think no need in SSD because mechanical SATA III HDD can write at 150 MB/s) plugged to it. The main problem here is to find the fastest card reader that can go the full bandwidth of the 1000x CF card at reading. Because 10 (or so) CF cards costs a fortune.
Oh, and that's when using ONE camera and ONE set of two cards. Professional shooting of the thing such as a concert requires using at least two cameras. I can plug another HDD in the bay to the same Thunderbolt port, but what am I to plug a card reader to, especially when it's USB 3.0 one?
So, a lot of problems...
Quote from: LEVISDAVIS on October 23, 2013, 09:33:27 AM
Komputerbay 128GB 1050x records continuous raw at...
23.976
- - 1584x1058 (almost 3:2) - - Shows no bars in the metering... Global Draw is off. (Raw photo mode is ON.)
25 P
- - 1584x1058 (almost 3:2) - - Shows no bars in the metering... Global Draw is off. (Raw photo mode is ON.)
29.970
- - 1584x1058 (almost 3:2) - - 864 frames ((Raw photo mode is OFF.)
5X Center Crop
23.976
1920 x 1080 - 1715 frames (results varied a lot) (Hacked - No Preview proved best results).
1920 x 1038 - Continuous (results varied).
Things to consider is that if you are going to push the card to the limit it want to record a short take and then skip frames. After that first short take it will record something fierce and of course continuously. This is different than the Komputerbay 64 GB card. That card seems to just get up and go and if it gets into a recording bind somehow finds a way to lower buffers. ;D
... Saw a serious increase in the 50D's ability to capture frames by disabling raw in the photo mode. However, I too typically shoot with raw enabled because 1584 x 892 at a standard frame rate is not a stretch for the Komputerbay cards. Have never gotten pink frames either.
If you haven't been following... I purchased a 128 GB 1000x card from Komputerbay about a week ago. Unfortunately, the card would not work with ML on the 50D. I contacted Komputerbay support and they had me send in the card for a firmware adjustment. At that point, I asked to upgrade to the 1050x because they stated that the 1050x would also work with the 50D after they made a firmware adjustment. Well, I got the card back from their tech support today and was absolutely able to load the firmware with success. Yes it's a 128 GB 1050x card and yet it will work with ML! Reads as a 119GB card, but it should be able to capture 128 GB without any trouble. If you notice the 64 GB 1000x cards read as a 60 GB card in the Canon 50D and it still captures a full 64 GB worth of data.
If you are interested in the card, you might want to talk to Komputerbay before purchasing the card from Amazon or ebay. They may have some of the firmware adjusted cards in stock. I don't know for sure, but I would think that they would have at least a few. Who knows?
Thanks for posting this info. I had given up on the idea of a 128GB card. This is great news. What is the highest write speed you get with it so far?
Quote from: Wlad81 on October 23, 2013, 10:28:22 PM
Thank you so much. I've studied the topic a little more and found out that overheating is really not the problem. The main problem here isn't even the HDD speed because I really can use the simplest MacBook Pro with a Thunderbolt connection and a SATA III HDD (I think no need in SSD because mechanical SATA III HDD can write at 150 MB/s) plugged to it. The main problem here is to find the fastest card reader that can go the full bandwidth of the 1000x CF card at reading. Because 10 (or so) CF cards costs a fortune.
Oh, and that's when using ONE camera and ONE set of two cards. Professional shooting of the thing such as a concert requires using at least two cameras. I can plug another HDD in the bay to the same Thunderbolt port, but what am I to plug a card reader to, especially when it's USB 3.0 one?
So, a lot of problems...
Yes. You are right about the sped of the CF reader's throughput - which I thought about but neglected to mention. In the end, it's the sum of the parts that make the difference - a fast port, an adequate Hard drive and a fast CF reader.
I'd still recommend an SSD over a mechanical drive for data protection and for editing projects - unless money is an issue.
Was also wondering about having an efficient system to record and backup the files on the go, even though short takes are enough for all the work I intend to do.
USB3.0 transfer speeds should saturate the read performance from a 1000x CF card if i'm not mistaken...Around 150mb/s.
Meaning I should be able to copy the whole of my 32gb cf card , in roughly 5 minutes.
Which isn't too bad, could be swapping out to another card in the meantime to get going straight away or just wait out the 5 minutes, format and go.
I think the workflow may be the next: you record ML firmware on both cards, working with the second card as the first card is backing up, then erasing all raw files from the first card and swap the cards. And so on. I think if shooting at 1584x1058 is not nesessary, one could shoot in lower resolutions to get more recording time on one card, if the result is DVD. So the computer could be in time to finish backing up the raw files.
Quote from: Wlad81 on October 24, 2013, 09:32:43 AM
could shoot in lower resolutions to get more recording time
As I understand lowering the resolution will result in smaller frame cover (crop factor). As I see from my experience It will increase the DOF distance, noise level and cut the wide angle lenses. If the shooting condition allows, you can use it. But you must notice it.
Quote from: jcdenton on October 24, 2013, 10:06:32 AM
As I understand lowering the resolution will result in smaller frame cover (crop factor). As I see from my experience It will increase the DOF distance, noise level and cut the wide angle lenses. If the shooting condition allows, you can use it. But you must notice it.
No it won't do that.
Shooting in a lower resolution will just give you a softer image when blown up to 1080P, if you only plan to put it on a DVD then this won't matter. (although, in my experience, shooting a higher res and downscaling does tend to give better results than shooting SD from the outset)
The angle of view, crop factor, DOF, f-stop etc will stay exactly the same regardless of whether you shoot at 1584x1058 or less. All these things will only change if you enter 5x shooting mode, then the crop factor is around 4x I believe.
Quote from: rockfallfilms on October 24, 2013, 10:16:00 AM
No it won't do that.
Shooting in a lower resolution will just give you a softer image when blown up to 1080P, if you only plan to put it on a DVD then this won't matter. (although, in my experience, shooting a higher res and downscaling does tend to give better results than shooting SD from the outset)
The angle of view, crop factor, DOF, f-stop etc will stay exactly the same regardless of whether you shoot at 1584x1058 or less. All these things will only change if you enter 5x shooting mode, then the crop factor is around 4x I believe.
Ok, But when I change the resolution on my 50d in raw_rec module (for example to 1440x890) the shooting frame becomes smaller and don't cover the whole screen. And records only the image that stays within the frame. And it always been this way in every build I tried. Your experience is different?
I think shooting at 900-something by 500-something is enough to get a good picture for DVD, and it gives the time for the computer to copy the raw files from the other card, am I right? I've been shooting on Beta SP (PAL), at the picture was quite good, though it has worse resolution than 50D at that res might have.
Interesting comparison of BMPC against 5dM3 and 7d ML (why not 50d????):
http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3 (http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3)
My 1000th post :o and to think, I only started using Magic Lantern for zebras and focus peaking ;D
I've learned so much. Thankyou guys!
Quote from: rommex on October 24, 2013, 10:54:25 AM
Interesting comparison of BMPC against 5dM3 and 7d ML (why not 50d????):
http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3 (http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3)
Yea, I saw that and thought the same thing. Is it just me or does the 50D produce a better raw video image than the 7D? I think the smaller sensor helps a bit with aliasing and moire compared to the 7D. It's still there of course but there is something very nice and, dare I say, unique about the 50D's image quality (if you treat it right ;) ).
Quote from: jcdenton on October 24, 2013, 10:39:05 AM
Ok, But when I change the resolution on my 50d in raw_rec module (for example to 1440x890) the shooting frame becomes smaller and don't cover the whole screen. And records only the image that stays within the frame. And it always been this way in every build I tried. Your experience is different?
Yes that is how it is going to be.
You are shooting a smaller frame resolution so you would need to expand it to fill the frame. This will result in a softer image because you have less resolution to begin with.
In the same way that if people used to shoot in SD they would have to expand the image to HD.
This chart might help.
(http://a.vimeocdn.com/si/videoschool/resolution_comparison_chart.png)
Quote from: rommex on October 24, 2013, 10:54:25 AM
Interesting comparison of BMPC against 5dM3 and 7d ML (why not 50d????):
http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3 (http://www.eoshd.com/content/11350/depth-test-5d-mark-iii-7d-raw-vs-blackmagic-pocket-vs-gh3)
I think the 50D would have faired pretty well and been quite close to the pocket. Not quite sure why he chose the 7D unless he has sold his 50D. It's like a warzone on those forums so I don't tend to comment there!
Also people going on about the GH3, saying it's better than Raw. To me they are just trying to justify their purchases. Now I've got a taste for Raw I could never go back to 8bit h264.
There is something very nice about the 50D image, I think it's pretty close to the Blackmagic in terms of motion cadence.
I'm still hoping a VAF might materialise at some point.
I was hitting an 81.5 MB/s with the 1050x when shooting 1584x1058. The card was formatted in camera too.
Quote from: jcdenton on October 24, 2013, 10:39:05 AM
Ok, But when I change the resolution on my 50d in raw_rec module (for example to 1440x890) the shooting frame becomes smaller and don't cover the whole screen. And records only the image that stays within the frame. And it always been this way in every build I tried. Your experience is different?
Probably the same and different, at the same time.
You should spend more time reading in the forums, rather than posting. Everything you need to know is here, you just have to digest it.
The point is that it's capturing raw live feed as sequential images. If you capture smaller than the whole frame, where would you take it from? It's not resizing it, it's just capturing as many pixels as you tell it to.
Quote from: SleeperNinja on October 24, 2013, 01:16:49 PM
Probably the same and different, at the same time.
You should spend more time reading in the forums, rather than posting. Everything you need to know is here, you just have to digest it.
The point is that it's capturing raw live feed as sequential images. If you capture smaller than the whole frame, where would you take it from? It's not resizing it, it's just capturing as many pixels as you tell it to.
I know that and that is what I'm trying to tell. You capturing a part of image you suppose to take from sensor. So if you have 30mm lens in FF it will be 50mm on 50d and it will 60mm or even more when you choose to shoot in lower resolution with RAW on 50d. I't will just crop your angle. And in result you will have more noticeable noise. It will just be bigger and softer just like you zoom Full HD on computer. You just began to notice more then with max resolution.
Hi All,
Dual ISO not work on 50D in video mode ? I see Dual ISO update everyday
Quote from: CITY-U1001 on October 24, 2013, 04:39:13 PM
Hi All,
Dual ISO not work on 50D in video mode ? I see Dual ISO update everyday
No it doesn't
Quote from: CITY-U1001 on October 24, 2013, 04:50:30 PM
it isn't planned?
As far as I'm aware, the hardware doesn't support it.
Developer 1% will be able to confirm whether this is correct or not.
Changing the registers in LV has no effect on 7D/50D/5DII, basically that whole generation.
The common question: does ML plan to introduce a 12 bit or on-the-fly lossless compressed version of raw? Sorry for the offtopic
That's not very possible.
Quote from: Andy600 on October 24, 2013, 11:08:38 AM
Yea, I saw that and thought the same thing. Is it just me or does the 50D produce a better raw video image than the 7D? I think the smaller sensor helps a bit with aliasing and moire compared to the 7D. It's still there of course but there is something very nice and, dare I say, unique about the 50D's image quality (if you treat it right ;) ).
Yes it does Andy.. to me nothing right now beats the 50D as far as it's filmic qualities only with the exception of the Blackmagic Cinema Camera.
Guy's I'm back haven't been posting for a while now due to a couple music projects that I was working on. I'm thankful for all the advances I'm seeing @a1ex @1% @andy600 props to you guy's for taking it this far, and let's not forget @gregoryofmanhattan for getting the 50D hacks properly running @ the beginning. I'm currently working on a treatment for a music video shoot that I'm shooting and Directing, if anybody lives close to Connecticut, or lives close to Manhattan shoot me and email or reply this post looking for collaborators for this project. All I can say right now it will all be shot on the 50D, maybe with a couple slowmotion shoots from my GH2. Looking forward for your replies.
GOD Bless
I like the 7D in 1x and 50D in crop. 7D is better for dual purpose photo/video, 50D is better for video only.
I wonder how 40D raw would look, if even possible....
Quote from: Andy600 on October 24, 2013, 11:08:38 AM
Yea, I saw that and thought the same thing. Is it just me or does the 50D produce a better raw video image than the 7D? I think the smaller sensor helps a bit with aliasing and moire compared to the 7D. It's still there of course but there is something very nice and, dare I say, unique about the 50D's image quality (if you treat it right ;) ).
The 7D and 50D have the same size sensor of 14.9 x 22.3mm APS-C - but the Resolution of the sensor in the 7D is 5360 x 3515 and the 50D is 4770 x 3177. They have different amount of pixels 7D 18.84 Mpix and 50D 15.15 Mpix. The Pixel pitch of the 7D is 4.2 and the 50D is 4.7. So it seems they have totally different sensors which could easily explain the difference some think they see.
The strange thing is that the Dynamic Range of the 7D and 50D are almost the same. The most they can muster at ISO 100 is 11.7 for the 7D and 11.4 for the 50D. The 2 cameras track almost identical thru the rest of their ISO range in terms of DR. I don't know about Noise tho. I'd love to see some data on the Noise going thru the ISO range.
Has anyone done a comparison video between the 7D and 50D to prove if the image in indeed different with the same settings?
After doing some technical research on the 7D and 50D I found that the 50D has far more noise in RAW as you increase ISO than the 7D. The 7D also retains more detail and I think this is probably one of the things people like about the 50D. The slight softness is likely more pleasing than the 7D for some. This might also be the same for the 5D3 in some peoples opinion. I think some people like the slightly softer look of the 50D.
Nothing i've seen would suggest that the 50D would be better in low light than the 7D tho. Another issue is how the cameras handle color. From what i've seen they seem to have the same color profile. So I think another issue would be highlight handling. The only thing I see is that it seems the 50D is slightly shifted towards the highlight range and the 7D the shadow range. Not a wide margin but it's there. Throughout the usable ISO range the 50D holds a slight advantage in highlights. The 7D does better in the shadow range. According to DP Review the best they could get from the 7D in RAW was 9.8EV and the best they got from the 50D was 11.6 in RAW. So this could be another aspect that is helping the look of the 50D.
According to ML raw histogram, how much DR do you get?
(it measures DR on the fly, with the engineering definition (http://www.luminous-landscape.com/forum/index.php?topic=42158.0), so it should be objective and comparable across all cameras).
DR shifted to highlights or shadows is nonsense because (1) all digital cameras have a hard clipping point and (2) you are free to meter wherever you want, relative to that clipping point. To compare DR between two cameras, you should make sure the clipping point is the same in both images (otherwise you are comparing apples with oranges).
Quote from: a1ex on October 24, 2013, 11:51:57 PM
According to ML raw histogram, how much DR do you get?
(it measures DR on the fly, with the engineering definition (http://www.luminous-landscape.com/forum/index.php?topic=42158.0), so it should be objective and comparable across all cameras).
DR shifted to highlights or shadows is nonsense because (1) all digital cameras have a hard clipping point and (2) you are free to meter wherever you want, relative to that clipping point. To compare DR between two cameras, you should make sure the clipping point is the same in both images (otherwise you are comparing apples with oranges).
I just did a quick, unscientific test and the max I can get it to show is 11.4EV at ISO 100 & 200 (which proves the Dx0 mark ISO charts) using center weighted average metering.
Quote from: Andy600 on October 25, 2013, 12:04:12 AM
I just did a quick, unscientific test and the max I can get it to show is 11.4EV at ISO 100 & 200 (which proves the Dx0 mark ISO charts) using center weighted average metering.
That's good to know. I did try to provide as much good supporting information as I could find.
a1ex, I don't understand why you think it's nonsense to describe a cameras Dynamic Range as "shifted to highlights or shadows" when all i'm trying to describe is the results of Dynamic Range tests where they determine the mid gray point as 50% luminance and measure the number of stops below mid gray and above. Some sensors have more DR in the shadows and others in the highlight range, thus my saying "shifted to". 2 sensors could have the same DR overall but not have the same distribution of stops above or below mid gray. Its just a manner of speaking not a technical term. The point being that when establishing a mid point as a point of reference you can determine how much a camera sees into the shadows or highlights. Saying a sensor is "shifted" one way or the other is relative to 50% luminance, it may have been clumsy but it's hard to shorten it any other way IMO.
All Canon DSLR sensors are linear throughout the entire range. All of them have a hard clipping point (white). The "distance" from that white point to the darkest shadow that can be captured with a SNR of 0 dB is the dynamic range.
Mid gray is where Canon meter is calibrated. You can (and should) ignore it when shooting raw. Learn to expose to the right and don't look back.
Is it me or does the raw video from the Canon 50d look better than the video from the Blackmagic pocket cinema camera. I own both cameras and I'm extremely disappointed with how soft the BMPCC video is compared to the 50d, almost to the point where I may get rid of the BMPCC if the raw upgrade doesn't beat out the 50d. I honestly think that Blackmagic dropped the ball on this camera.
Quote from: soundwizard99 on October 25, 2013, 05:47:27 PM
Is it me or does the raw video from the Canon 50d look better than the video from the Blackmagic pocket cinema camera. I own both cameras and I'm extremely disappointed with how soft the BMPCC video is compared to the 50d, almost to the point where I may get rid of the BMPCC if the raw upgrade doesn't beat out the 50d. I honestly think that Blackmagic dropped the ball on this camera.
I would wait and see what the BMPCC looks like with raw before deciding. I've seen the pocket up against the 7D (raw) and it holds up well even with prores.
I'm using the Komputerbay 32gb 1000x, I'm receiving what appears to be "dead pixels" or at least that what they appear to be.
Some "dead pixels" are pink and some are just black. Is it my camera or card??
Probably you have dead pixels... I have them on every sensor except I think EOSM.
Quote from: 1% on October 25, 2013, 06:21:51 PM
Probably you have dead pixels... I have them on every sensor except I think EOSM.
I did a few small tests and i don't receive the dead pixels every time i shoot. Sometimes they are their and sometimes they aren't at all.
I did a test last week ranging from iso 100 - 1250, and the dead pixels where in every iso. I did the same test today ranging from iso 100 -1250 and they weren't in ANY shots.
could it still be my camera or CF card?
I have also tried another transcend 32gb 400x with the same tests and haven't received any dead pixels.
i've done 3 tests with my Komputerbay card and dead pixels were random in each shoot.
I've done 1 test with the Transcend card and no dead pixels.
It Appears to be the card, but i need to do further tests to be 100% sure.
Quote from: pags on October 25, 2013, 06:33:16 PM
I did a few small tests and i don't receive the dead pixels every time i shoot. Sometimes they are their and sometimes they aren't at all.
I did a test last week ranging from iso 100 - 1250, and the dead pixels where in every iso. I did the same test today ranging from iso 100 -1250 and they weren't in ANY shots.
could it still be my camera or CF card?
If you could post some photo examples, then it would be easier to help you.
It happens randomly, esp bad at high ISO + long power on time. And yes, they move around/come and go.
Examples of dead pixels:
http://www.flickr.com/photos/pags343/10478227504/
http://www.flickr.com/photos/pags343/10478400313/
http://www.flickr.com/photos/pags343/10478227304/
Quote from: 1% on October 25, 2013, 06:56:04 PM
It happens randomly, esp bad at high ISO + long power on time. And yes, they move around/come and go.
Is there anything I can do to help prevent dead pixels? Anything in proproduction or anything i just need to be cautious of?
Shoot at lower ISOs? Thats all I can think of, its why I think we need dead pixel/finding removal... that thing is 1px big in the actual raw file but it grows when you debayer. Its even worse when you pan and you have all this purple "dust" on your shot.
Quote from: 1% on October 25, 2013, 07:15:34 PM
Shoot at lower ISOs? Thats all I can think of, its why I think we need dead pixel/finding removal... that thing is 1px big in the actual raw file but it grows when you debayer. Its even worse when you pan and you have all this purple "dust" on your shot.
Thanks for the advice and feedback 1%!
Is dead pixel/finding removal currently in the works or line up?
This is my first post here so hello fellow 50D owners and ML users ;D
I think (this is untested as I haven't encountered the problem ;)) a relatively simple POST production 'fix' for the dead pixel issue, if you have Adobe After Effects, would be to use the clone tool to have the dead pixel area replicate the area on one side of it. This isn't a true fix but may help mask the problem somewhat.
Though this would become very labour intensive if the dot is moving, it wouldn't prove difficult if the dot is stationary in the frame.
Quote from: Mirco on October 26, 2013, 09:29:35 AM
a relatively simple POST production 'fix' for the dead pixel issue, if you have Adobe After Effects, would be to use the clone tool to have the dead pixel area replicate the area on one side of it. This isn't a true fix but may help mask the problem somewhat.
Though this would become very labour intensive if the dot is moving, it wouldn't prove difficult if the dot is stationary in the frame.
Do it propagate to all the subsequent frames automagically ? Or do you need to do this frame-by-frame for every frame ?
What is the algorythm of calculating the size (in bytes) of the one minute video file depending on the video resolution? Is that, for instance, (1592*1062*14*24*60)/8?
Quote from: dlrpgmsvc on October 26, 2013, 02:08:31 PM
Do it propagate to all the subsequent frames automagically ? Or do you need to do this frame-by-frame for every frame ?
Not sure for AE, but for Adobe Camera RAW, just use the clone tool on one frame, and synchronize all frames (making sure clone is checked in the popup). Hit Apply, and wait a bit for it to process. Fixed a panning wide shot with a small sensor dust in the sky using this. VERY hard to notice unless you are really looking for it, and with panning motion in the shot, you are not focusing on the sky so much. For a still shot it would be almost impossible to tell.
Of course, you can get unlucky and get a spot of changing colours or lighting that you may have to go back and fix a span of a few seconds worth of frames, but just go back to that section and reclone a different area.
Quote from: Wlad81 on October 26, 2013, 07:35:49 PM
What is the algorythm of calculating the size (in bytes) of the one minute video file depending on the video resolution? Is that, for instance, (1592*1062*14*24*60)/8?
That multiplication looks allright.
I've had 2 issues with my 50d since installing the latest build. When changing the iso the lvf goes to a kind of flashing white, and as far as I can see all I can do is turn the camera off. Also, while I can record much longer clips than before at top resolution, if they're too long (over 3 gigs, I think) I get a file that won't open in raw2dng. I have to stop it at about 50 seconds. And at about 60 seconds the lvf just shuts off and that's it.
I guess that's more than two issues. But god knows I'm not complaining about getting 50-second raw clips!
Love the new build. Very clean and professional. I like how it says how many seconds I've recorded. Nice.
Only issue I've seen, and maybe it's been addressed in the forum someplace else, but when I go to 5x mode, the preview starts glitching. Anyone else have this issue and is there a solution?
Thanks in advanced.
Took my 50D up to Crater Lake a few months ago with some really old dirty lenses.
oops. double post.
Quote from: Wlad81 on October 26, 2013, 07:35:49 PM
What is the algorythm of calculating the size (in bytes) of the one minute video file depending on the video resolution? Is that, for instance, (1592*1062*14*24*60)/8?
I did some calcs for all resolutions, for the EOS-M, what it can do is in green. However, the higher numbers up to the high 70s (MBS) should apply to the 50D
http://www.magiclantern.fm/forum/index.php?topic=8825.msg82948#msg82948
I would use (1592*1062*(14/8)*24*60)
1% sent me this information, on how he does it for the camera messages (he thought my numbers close enough for my purposes):
Frame size * frame rate is what it does.
int frame_size_padded = (res_x * res_y * 14/8 + 4095) & ~4095;
frame_size_real = res_x * res_y * 14/8;
frame_size / 1000 * fps
It does some calculations with the buffer slots too so thats why you're coming up with different numbers.
Hey guys,
here´s a test of my new Slider with 50D Raw.
Infos: http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Hey folks, just wanted to give you a quick look at the differences when using Neat Video on your RAW 50D footage. It's a great and powerful noise reduction plugin and in my experience works much better cleaning and preserving details in the shadows than denoiser.
Quote from: funkysensation on October 28, 2013, 01:45:26 PM
Hey guys,
here´s a test of my new Slider with 50D Raw.
Infos: http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Some nice shots in there and a great location too.
Quotebut when I go to 5x mode, the preview starts glitching. Anyone else have this issue and is there a solution?
What do you mean by glitching? And which preview mode?
Quote from: D.L. Watson on October 28, 2013, 02:40:54 AM
Love the new build. Very clean and professional. I like how it says how many seconds I've recorded. Nice.
Only issue I've seen, and maybe it's been addressed in the forum someplace else, but when I go to 5x mode, the preview starts glitching. Anyone else have this issue and is there a solution?
Thanks in advanced.
Took my 50D up to Crater Lake a few months ago with some really old dirty lenses.
Nice video.
Are you talking about the Magic Lantern or the Tragic Lantern build?
Quote from: 1% on October 28, 2013, 04:18:08 PM
What do you mean by glitching? And which preview mode?
I think he means Live View. I noticed it today while shooting and was getting occasional screen glitches but footage is unaffected.
Quote from: funkysensation on October 28, 2013, 01:45:26 PM
Hey guys,
here´s a test of my new Slider with 50D Raw.
Infos: http://550draw.blogspot.com/ (http://550draw.blogspot.com/)
Hey there! Very impressive video. Some shots are SO filmic that I have to convince myself it was shot on 50D ;D
May I ask you (without being frowned at by others :o ): do you have any special technique/hints how to avoid aliasing when shooting so many straight construction lines? I tend to think that I would have gotten aliasing everywhere in shot should I have shot what you did.
Thanks!
QuoteI think he means Live View. I noticed it today while shooting and was getting occasional screen glitches but footage is unaffected
ok, the pink/purple flashes? I got that on 7D today when ETTR is adjusting.
Quote from: Andy600 on October 28, 2013, 07:44:39 PM
I think he means Live View. I noticed it today while shooting and was getting occasional screen glitches but footage is unaffected.
Yes. Sorry. Live-View mode at 5x crop. I wasn't sure if it would affect video and I was pressed for time so I didn't try it. But it's really bad on my 50D, blinking in and out, purple, pink flashes, hard to frame or pull focus. And it's with the latest Magic Lantern build. Jump to 10x crop or return to normal crop and it's fine.
And it even happens when I disable the ETTR module.
Well the pink glitch is occasional but thats when you're not doing anything, just high CPU usage... its really bad on 600D so to see it on something else seems to say the CPU usage is edging when too many cpu indicators or on working on raw data + ettr is adjusting.
There is the new raw color preview on 1/2 shutter that has a pink flash and sometimes black in between. Hold half shutter on ML grayscale preview, of course it won't work while recording because of GD needing to be off but otherwise OK.. also the LV gray fix comes off when you press 1/2 shutter too, which is really pink now. not sure if it was less pink before.
I've been toying around with Magic Lantern and had a few random questions.
• I'm using the original RAW build, and am having an issue wherein when I try to record in zoomed in, the entire liveview turns greyscale. Is there a reason this happens?
• Tragic Lantern - Is it as easy as downloading the .bin and overwriting the card? I tried but was having a ton of issues with Tragic Lantern not displaying properly, etc.
Thanks in advance.
Quote from: brandonmarsh on October 29, 2013, 05:19:18 AM
I've been toying around with Magic Lantern and had a few random questions.
• I'm using the original RAW build, and am having an issue wherein when I try to record in zoomed in, the entire liveview turns greyscale. Is there a reason this happens?
• Tragic Lantern - Is it as easy as downloading the .bin and overwriting the card? I tried but was having a ton of issues with Tragic Lantern not displaying properly, etc.
Thanks in advance.
TL is still alpha, you want to spend some time reading the threads because you have to do more than "toy around" to get anywhere. Sorry.
The LV turns gray because RAW video works by intercepting the RAW feed to the LV and saving it on a card. So there isn't enough CPU to show a good image. You can get color LV, but it will be so slow as to be useless for focusing.
Nothing is as "it is as easy as". Sorry again! Hope you stick with it. Once you get the hang of it it is pretty reliable on the 50D, if that's what you're using.
I keep a thread on the EOS-M, which covers some issues that apply to the 50D too. (the 50D does NOT have the focus dot issue and can do double the resolution of the EOS-M).
http://www.magiclantern.fm/forum/index.php?topic=8825.msg82944#msg82944
Look for the threads from RenatoPhoto too. He covers a lot of the basics.
I finally decided to make a test for the Dark Frame Subtraction technique.
It's used in photography to reduce noise and remove hot pixels, and somebody claimed it could be used in video too.
The answer is no.
Well, it removes hot pixels, but noise remains the same or even worse.
You can check by yourself in the video below
or read the whole story on my blog and download the high quality video (utube made a awful compression, even in fullhd!)
www.riccardocovino.it (http://www.riccardocovino.it)
How did you capture the dark frame?
If you only take a single video frame, it will increase the standard deviation of the noise by sqrt(2). If you average lots of video frames, it will leave the random part of the noise unchanged, but should help with FPN, hot pixels and black level calibration.
hi a1ex, I shot a video with the lens cap.
same lenght (more or less) of the other, than put it in subtraction mode on it.
so you suggest a single frame made with the average of the dark video?
Quote from: D.L. Watson on October 29, 2013, 03:34:28 AM
Yes. Sorry. Live-View mode at 5x crop. I wasn't sure if it would affect video and I was pressed for time so I didn't try it. But it's really bad on my 50D, blinking in and out, purple, pink flashes, hard to frame or pull focus. And it's with the latest Magic Lantern build. Jump to 10x crop or return to normal crop and it's fine.
And it even happens when I disable the ETTR module.
As 1% said it's probably pushing the CPU to the max. I disable everything other than the histogram. Just noticed I still had zebras enabled yesterday from a different config which I was setting up which probably caused the glitching but it was happening for me in normal (non-crop) mode too. Disabled the zebras and it seems to have stopped glitching but it was never severe on my camera.
Try deleting all your configs and setting them up again.
BTW 1%, mlv_rec is not compiling now ??? but the new player is nice... rec709 playback woohoo! 8) I wonder if this can also be done for 5x preview instead of that god-awful grayscale display filter (would be useful even at very low fps because it's only for framing)??
re: dark frames - We need a set of 50D Neat Video profiles for different ISOs. Anyone know how to do it properly?
Quote from: Andy600 on October 29, 2013, 01:42:59 PM
rec709 playback woohoo! 8)
50D has rec601, so you may need to fix the matrix ;)
Quote from: Andy600 on October 29, 2013, 01:45:06 PM
re: dark frames - We need a set of 50D Neat Video profiles for different ISOs. Anyone know how to do it properly?
I have a 50D and Neat Video (the 720p version--my guess is Neat would upgrade me if I asked nicely), but am consumed with the focus pixel issue on the EOS-M. However, if someone can get me going I have a light-stand setup that is good for taking test images.
Quote from: a1ex on October 29, 2013, 01:56:07 PM
50D has rec601, so you may need to fix the matrix ;)
Ah, ok. Do you by any chance know where the 601 matrix numbers are?
I see it's set in imgconv.c?? Is that right?
See the comments in the source code.
Quote from: a1ex on October 29, 2013, 02:03:23 PM
See the comments in the source code.
martinreddy.net has BT601 as:
Y'= 0.299*R' + 0.587*G' + 0.114*B'
Cb=-0.169*R' - 0.331*G' + 0.500*B'
Cr= 0.500*R' - 0.419*G' - 0.081*B'
I guess this needs to be portable but can I just swap out the numbers on the 50D? Will it work temporarily?
Look at the other code that uses rec709 or 601.
The old Tragic Lantern is rock solid no hick-ups, and I get great results ;D just shot a commercial finishing my edits should post soon.
Quote from: goldenchild9to5 on October 29, 2013, 11:51:19 PM
The old Tragic Lantern is rock solid no hick-ups, and I get great results ;D just shot a commercial finishing my edits should post soon.
Which version of Tragic Lantern did you use? I was using the latest version and it gave me all sorts of issues on a music video shoot that I had never experienced in my previous test, such as the raw video module disappearing and the modules screen disappearing all together. I had to remove the battery in order to reload the raw module. This happened a few times.
Hi All.
maximum Fps for 50D is 30fps ? Why 48fps not supported ?
Quote from: CITY-U1001 on October 30, 2013, 11:58:47 AM
Hi All.
maximum Fps for 50D is 30fps ? Why 48fps not supported ?
Because there is no 720p mode on the 50D.
Quote from: Andy600 on October 30, 2013, 12:10:44 PM
Because there is no 720p mode on the 50D.
Not even a video mode (hinting aside)! It's nice to have accomplished SOMETHING, and 1080p is pretty impressive, all things considered. 8)
Quote from: Andy600 on October 30, 2013, 12:10:44 PM
Because there is no 720p mode on the 50D.
Is that right? I thought the problem is the cameras just won't write to the LV faster than 30 fps and there is no way for the devs to force it. As far as I know, you can choose any res on the 50D that the sensor will allow, like 1280x720
@maxotics: I think what Andy600 meant is not that the resolution 1280x720 can't be recorded, but that there is no 720p mode (i.e., no Canon-firmware-selectable mode that, instead of recording 1080p@25/30fps, records 720p@50/60fps). Selecting this mode in the Canon firmware, on cameras which have it, like the 550d (the only camera I own), and, I believe, all newer cameras, is the only thing which allows LV to be updated at the faster frame rate. Since ML raw is nothing other than "captured" LV video, the 50D cannot do the faster frame rates. At present, there is no obvious path to 48/50/60fps on the 50D. Devs and admins, please feel free to comment if I am incorrect! Cheers!
Certainly, Andy may know a thing or two ;) We all want to be careful when posting something that it won't be mis-understood by a future reader. All of us fall into this ML-shorthand which can easily be misunderstood by people new to this.
For example, we all know, there is no built-in ANYp on the 50D
Quote from: Andy600 on October 30, 2013, 12:10:44 PM
Because there is no 720p mode on the 50D.
Yes. But theoretically, the CF controller is capable of 60fps - given a fast enough card. If so, then the only wall is the firmware. Right?
Any news for the Mosaic Engineering's VAF for 50D ? The 70D version is already available on their website ...
Quote from: menoc on October 30, 2013, 04:31:15 PM
Yes. But theoretically, the CF controller is capable of 60fps - given a fast enough card. If so, then the only wall is the firmware. Right?
That's like saying the only wall preventing one's Dodge Neon from going 200mph is the clutch-box ;)
Every camera's sensor and the chip that reads data from it, has a bandwidth (horsepower) limitation. Canon isn't purposely trying to limit. They made the best compromise for fuel consumption (battery) and heat (cooling). The jello effect, as far as I know, is just how close they cut the corner on what they can do. As it is, they're not able to dump a whole image in 24 fps, which is why you get the jello effect (the top part of the frame lagging the bottom part).
It is a firmware hack that allows ML to get all the horsepower from the sensor, which was possible NOT because the cameras IO became faster, but because CARDs got faster and the card adapter was able to handle it. I don't see a similar bottleneck between the camera's sensor AND the card writing . That's internal. In other words they'd have to go swap out electronics in the camera to boost FPS speed. The devs would know more than me. But that's my understanding.
Quote from: maxotics on October 30, 2013, 05:01:09 PM
That's like saying the only wall preventing one's Dodge Neon from going 200mph is the clutch-box ;)
Every camera's sensor and the chip that reads data from it, has a bandwidth (horsepower) limitation. Canon isn't purposely trying to limit. They made the best compromise for fuel consumption (battery) and heat (cooling). The jello effect, as far as I know, is just how close they cut the corner on what they can do. As it is, they're not able to dump a whole image in 24 fps, which is why you get the jello effect (the top part of the frame lagging the bottom part).
It is a firmware hack that allows ML to get all the horsepower from the sensor, which was possible NOT because the cameras IO became faster, but because CARDs got faster and the card adapter was able to handle it. I don't see a similar bottleneck between the camera's sensor AND the card writing . That's internal. In other words they'd have to go swap out electronics in the camera to boost FPS speed. The devs would know more than me. But that's my understanding.
Actually, ML IS NOT a firmware hack. A firmware hack involves modifying the firmware itself - which ML does not. The other point is that the firmware, if I'm not mistaken, is what controls what mode (720/1080) the camera works in. Therefore, the wall would be the firmware, not the hardware. The speed is there, even if you'd be capturing only 30-60 seconds of 60fps video.
If what you say is right then will get 60fps when 2000x cards come out.
Edit: Actually current cards are capable enough as proven by the 5DMIII . . . .
Quote from: menoc on October 30, 2013, 05:10:57 PM
Actually, ML IS NOT a firmware hack. A firmware hack involves modifying the firmware itself - which ML does not.
Yes and no. I didn't say ML is changing the firmware. I fully recognize that it uses the "firmware update" hook to load additional firmware into the camera, though calling it firmware, may be a misnomer.
Are you thinking about what I'm saying? Forget the card writer for a second. If you could attach any IO device to the chip that reads data from the sensor what is the maximum frames per second you think it can output, and at what resolution?
If you think it can do 60 frames per second, where is the evidence? I'm not trying to be obnoxious. From my readings of other technical people the devs are already capturing the maximum amount. When they have gotten performance improvements it has been by reducing the load their code puts on the cameras processing.
Quote from: maxotics on October 30, 2013, 05:24:09 PM
Yes and no. I didn't say ML is changing the firmware. I fully recognize that it uses the "firmware update" hook to load additional firmware into the camera, though calling it firmware, may be a misnomer.
Are you thinking about what I'm saying? Forget the card writer for a second. If you could attach any IO device to the chip that reads data from the sensor what is the maximum frames per second you think it can output, and at what resolution?
If you think it can do 60 frames per second, where is the evidence? I'm not trying to be obnoxious. From my readings of other technical people the devs are already capturing the maximum amount. When they have gotten performance improvements it has been by reducing the load their code puts on the cameras processing.
Well I have followed the development from the beginning. From what I understand the sensor is capable - I could be wrong - but in order to do this, there has to be code in canon's firmware that enables 720p mode then ML devs enable it with ML code. Without the code you can't do it because there is not enough knowledge about the internal workings of the camera. Just to accentuate my point, remember when devs swore to their graves that RAW wold never happen for the 50D?
For what I can see the 50D and the 5DMII were clones except for the sensor size and audio capabilities. Devs could probably clear this up if I'm wrong but I believe that 720p mode is a function of software not hardware.
I think whats lacking on 50D is video modes in general. There is only one and its a way earlier implementation. If canon updated to a more modern code base then we'd have 60fps. Hardware seems capable but software is not there.
ML is like a program running at start, similar to grub, etc that runs the canon UI and a concurrent ML UI.
Quote from: menoc on October 30, 2013, 05:35:59 PM
For what I can see the 50D and the 5DMII were clones except for the sensor size and audio capabilities. Devs could probably clear this up if I'm wrong but I believe that 720p mode is a function of software not hardware.
Would be a game changer is this is true. I'm not saying it might not be. If there's anywhere I'd LOVE to be wrong :) The biggest handicap these cameras have, in my view, is the line skipping solution to dealing with what is essentially a high resolution readout that must be downsized to 1920x1080, say. I believe the 5D3 uses new chips that sample by pixel, not line, which is why there is little moire in those cameras. If the devs could do the same with the 50d and other cameras THAT WOULD CERTAINLY BE SOMETHING! My 2 cents is the sensors have not been improving much in the past few years, but Canon has been beefing up the signal processing chips. I'm as much in the dark as you ;)
Quote from: 1% on October 30, 2013, 05:39:04 PM
ML is like a program running at start, similar to grub
1%, you are the Yogi Berra of Magic Lantern :)
Quote from: 1% on October 30, 2013, 05:39:04 PM
I think whats lacking on 50D is video modes in general. There is only one and its a way earlier implementation. If canon updated to a more modern code base then we'd have 60fps. Hardware seems capable but software is not there.
ML is like a program running at start, similar to grub, etc that runs the canon UI and a concurrent ML UI.
That's what I'm saying. And I think we should use the right terms - ML is "software add-on" not "Firmware".
Nope, 5DIII just has a good filter to block the aliasing.
To get 50D into the "normal" camera realm you'd need the source for 5DII and 50D then combine them into a franken firmware. Ideally canon should have released a 60fps update when they did the 5DII firmware but they lazed out and didn't. Now its EOL and I doubt they will ever touch it.
Quote from: 1% on October 30, 2013, 05:39:04 PM
I think whats lacking on 50D is video modes in general. There is only one and its a way earlier implementation. If canon updated to a more modern code base then we'd have 60fps. Hardware seems capable but software is not there.
What is the connection, is there any, between rolling shutter and frames per second? I would think if you could do true 60fps you could eliminate jello at 30fps?
Quote from: menoc on October 30, 2013, 05:45:58 PM
That's what I'm saying. And I think we should use the right terms - ML is "software add-on" not "Firmware".
Agreed, I will be more careful in all my posts.
Quote from: 1% on October 30, 2013, 05:46:17 PM
Nope, 5DIII just has a good filter to block the aliasing.
Not to question you, but do you know that as a fact?
Quote from: maxotics on October 30, 2013, 05:43:50 PM
Would be a game changer is this is true. I'm not saying it might not be. If there's anywhere I'd LOVE to be wrong :) The biggest handicap these cameras have, in my view, is the line skipping solution to dealing with what is essentially a high resolution readout that must be downsized to 1920x1080, say. I believe the 5D3 uses new chips that sample by pixel, not line, which is why there is little moire in those cameras. If the devs could do the same with the 50d and other cameras THAT WOULD CERTAINLY BE SOMETHING! My 2 cents is the sensors have not been improving much in the past few years, but Canon has been beefing up the signal processing chips. I'm as much in the dark as you ;)
I give the Devs another year before they trip on their own words again about video modes! ;)
Quote from: maxotics on October 30, 2013, 05:48:41 PM
Not to question you, but do you know that as a fact?
Yes. in fact the 5DMIII has a built in filter which BTW, you can remove if you're brave enough . . . Check out James Miller's post on Vimeo:
Please show some resolution charts to prove it.
I would think that any footage with the filter removed, if it IS the way the 5D3 has reduced aliasing/moire would show tons of it. To me it looks like one of the commentators is right, the filter is more about IR, or something else. Am I missing something? Seems this video proves exactly the opposite, that Canon is using electronics to deal with aliasing issues in the 5D3 (that it didn't do in all cameras previous)
Even Mosaic says take their filter out before doing serious photography.
Quote from: soundwizard99 on October 30, 2013, 08:18:32 AM
Which version of Tragic Lantern did you use? I was using the latest version and it gave me all sorts of issues on a music video shoot that I had never experienced in my previous test, such as the raw video module disappearing and the modules screen disappearing all together. I had to remove the battery in order to reload the raw module. This happened a few times.
I believe I'm using Tragic 6, or Tragic 7 try them both results are phenomenal..
maybe they designed the filter to work with photography too, obviously the vaf filter is stronger and different. when the 5DIII was being reviewed it was mentioned. I don't see anything in the FW that would indicate that anything has changed in regards to how video modes work.
Also where is the magical processing on the 6D which is almost identical to 5DIII firmware and missing the filter. I also don't see it mentioned anywhere from canon itself.
Quote from: Heldico on October 30, 2013, 04:55:02 PM
Any news for the Mosaic Engineering's VAF for 50D ? The 70D version is already available on their website ...
Bump as I'm interested as well.
> On the 50D VAF filter.
I was going to send an EOS-M to Mosaic, to see if they could do a filter, but then I did the math. $300 body plus $300 filter and you might as well get a BMPCC. Yes, they're backordered, but eventually that will end and then where would Mosaic be? I think this the same problem with the 50d. I know they made a one-off for someone, and it worked well. So my guess is Mosaic just doesn't feel the economics justify it going into production for an old camera. That would be my business advice to them, as much as I love ML.
On the bright side, I do believe aliasing can be fixed more in post than it is now. I've been working with the focus pixel problem and think I have a fix for that. We'll see. I'm an old dog and working with 14 bits in an 8/16 bit world is making me cry and these young devs aren't interested in walking old men across the street :)
> As for the video aliasing filter
I just don't see it 1%. It seems if that was possible Sony would have put them into their VG cameras a long time ago. The 5D3 competes with the D600/D800 and it can't afford to lose ground in the RAW photo/image space. The Nikons have higher resolution which isn't for nuthin'. As for the 6D, that is really a consumer 60/70D with a full-frame sensor. EVERYTHING else about the camera is cheap plastic (which is fine for the vacationer). IF there is a new souped up chip, as I believe, why would they put it in that camera?
It's also part of my point above. There are electronics that sit before the firmware that do things which you can neither see nor control. It dumps out pixels. Where those pixels come from, how they are processed, on that level, is all conjecture, far as I can tell.
Just chiming in to say thanks to all the developers, deep gratitude for your efforts. After a long hiatus, back in love with ML.
Just gone out and bought a 50d and a 32GB Komputerby 1000x for a grand total of £255 + £55. Just recorded my first 1920x1080 video using the latest tragic lantern build, card didn't miss a frame. Jaw dropping stuff. Anyone want to buy a 550d? :) Tragic lantern looks beautiful by the way, and the new features are stunning. DIGIC focus peaking is a thing of joy, totally un-expected.
Just a couple of small comments about workflow. First attempts using the free tools have been succesful.
Going raw2dng -> ufraw-batch -> virtualdub (cineform 10-bit codec from GoPro studio). I found using the ufraw gui to correct exposure and white balance, and do some noise reduction then going to config, copying the XML and saving to a file to call from ufraw-batch worked well and gave good results. The noise reduction in Ufraw is very good actually, but slows the workflow down.
Dissapointed to find that Aftershot Pro doesn't pick up the DNG format generated. Anyone have success with that? I would love to use this, because the OpenCL acceleration really is very good on my system
Since been trying raw2gpcf.exe. It's very fast, but only 422 with the free version. Looks like I'd need to spend $1k to get the raw output on the pro version. Is that correct? Looks to me like the 422 version isn't that useful in a raw workflow because you miss the chance to grade in raw. I don't have ACR, so looking for the best workflow to get the best out of the footage.
Exciting times.
I think the Go pro/ Cineform full version is $299.00. Although there is a $1K version but I believe that you can access the full version of Cineform for $299.00. It's not free though.
Quote from: maxotics on October 30, 2013, 06:22:52 PM
I would think that any footage with the filter removed, if it IS the way the 5D3 has reduced aliasing/moire would show tons of it. To me it looks like one of the commentators is right, the filter is more about IR, or something else. Am I missing something? Seems this video proves exactly the opposite, that Canon is using electronics to deal with aliasing issues in the 5D3 (that it didn't do in all cameras previous)
Even Mosaic says take their filter out before doing serious photography.
It gets confusing but the Anti Aliasing Filter in Photo Cameras is not there to prevent Aliasing and Moire in Video. It's just enough for the high resolution of a full sensor output but not strong enough for the needs of video. The reason some DSLR's have avoided major issues with Moire and Aliasing has to do with how they get to the smaller resolution of 1080p video from the much larger output of the sensor. Panasonic in the GH2 was using pixel binning to downsize the image which is better than line skipping. Canon was using line skipping in all their DSLR's until the 5DmkIII which I think they now use Pixel Binning to downsize from full sensor to the much smaller 1080p, which leads to a better final image with less moire and aliasing and more preserved detail.
Quote from: maxotics on October 30, 2013, 08:11:09 PM
> On the 50D VAF filter.
I was going to send an EOS-M to Mosaic, to see if they could do a filter, but then I did the math. $300 body plus $300 filter and you might as well get a BMPCC. Yes, they're backordered, but eventually that will end and then where would Mosaic be? I think this the same problem with the 50d. I know they made a one-off for someone, and it worked well. So my guess is Mosaic just doesn't feel the economics justify it going into production for an old camera. That would be my business advice to them, as much as I love ML.
It would be a shame not to have a VAF for the 50D but you're probably right in what you're saying. It would be interesting to see how many people on this forum would actually buy one if it was available for the 50D. Maybe we should do a poll?
I don't see the BMPCC as an alternative for me as it would require an investment in lenses to make best use of the Super16 sized sensor. I've already got all the lenses I need to shoot on APS-C, so it makes sense to stick with that sensor size. I did think about maybe going for an EF BMCC but even that would require another lens to cover the wide end.
I shall just work around the moire/aliasing as best I can.
Quote from: rockfallfilms on October 31, 2013, 10:37:55 AM
It would be a shame not to have a VAF for the 50D but you're probably right in what you're saying. It would be interesting to see how many people on this forum would actually buy one if it was available for the 50D. Maybe we should do a poll?
I don't see the BMPCC as an alternative for me as it would require an investment in lenses to make best use of the Super16 sized sensor. I've already got all the lenses I need to shoot on APS-C, so it makes sense to stick with that sensor size. I did think about maybe going for an EF BMCC but even that would require another lens to cover the wide end.
I shall just work around the moire/aliasing as best I can.
I'm guessing the solution in this video loses you resolution? Looks quite a nice way of tackling scenes where you know you will face moire:
http://www.youtube.com/watch?v=xIVMvCDOt54&noredirect=1
Quote from: maxotics on October 30, 2013, 05:45:19 PM
1%, you are the Yogi Berra of Magic Lantern :)
Nobody likes a butt kisser.
Quote from: SleeperNinja on October 31, 2013, 02:22:19 PM
Nobody likes a butt kisser.
I meant it as when I read his posts I'm not sure if he's really serious or flippant. These are what Yogi Berra said as a manager
'90% of the game is half mental"
About a restaurant: "Nobody goes there anymore. It's too crowded"
"It ain't over 'til it's over"
Quote from: 50Deezil on October 31, 2013, 06:53:42 AM
It gets confusing but the Anti Aliasing Filter in Photo Cameras is not there to prevent Aliasing and Moire in Video. It's just enough for the high resolution of a full sensor output but not strong enough for the needs of video.
Exactly, it's there because each pixel is separated by some dead space. Video aliasing/more come from skipped lines, or huge spaces between rows of pixels.
QuoteI think they now use Pixel Binning to downsize from full sensor to the much smaller 1080p,
Then why are the modes and behavior the same as 1x and 5x mode on other cams? All I see is rumor posts before the camera was released and people speculating it has 3x3 binning but no official or empirical proof that it is.
Then I see this guy:
http://www.canonwatch.com/eos-5d-mark-iii-hacked-anti-aliasing-filter-removed-more-sharpness/
Filter is blurring/darkening the image... hmmm sounds like that would take down moire just like the VAF. Also the moire issues seem related to sensor size and resolution output + how it divides up and then debayers.
I don't see what the big deal is with the Aliasing and Moire on the 50D, when you create great content the viewers won't even have time to pin point Aliasing and Moire, nor do they care about it. I've seen big time Aliasing in Hollywood movies, in major TV shows do most viewers care "No" they are more interested in the storyline. I am satisfied and thankful for even shooting "Raw" on a camera that didn't even shoot video a big WOW for that, and the images are comparable to camera's 20 - 50 times it's cost ;D just saying.
I don't think its an issue on 50D+ at all. Just don't shoot things with moire in them. To me the hot pixels and FPN is a much much bigger issue than some tiny moire on striped things/roofs.
Well said 1% or we can learn to ignore the moire and aliasing.
i think you can avoid Moire by softening a picture while recording(a bit out of focus) so that it matches 1080p h256 in softness, and then you can sharpen it in the post.
Quote from: 1% on October 31, 2013, 05:16:17 PM
I don't think its an issue on 50D+ at all. Just don't shoot things with moire in them.
1% I have the greatest admiration for you as a developer, but I find this advice not so expert. First, moire is, foremost, a psychological reaction to visual cues. Our brains are wired to move about our environment and abstract a physical reality in which we can move, make sense of. Is that a Jaguar in the shadows? Is this a puddle, or the edge of a canyon wall? When our brain is confused by what it thinks is a line that should connect, we see moire. In short, moire is our brains way of saying 'this doesn't make sense, look harder, or watch out, I don't know what this is!' So moire is a HUGE problem in video because it distracts the viewer from the general image.
Moire is a both a naturally occurring phenomenon and a description of similar aberrations in digital images. It can be produced "technically" by the camera creating artifacts between disconnected pixels (visual information).
Yes, I don't want to shoot things that are known to produce moire. But I have two practical problems. One, I can't see if moire has occurred on the LCD of the 50D. I won't know until I'm off the set and looking on a monitor. If it's there, getting rid of it is not easy. Yes, the effect can be mitigated by choosing better debayering, but NOT eliminated. Second, sometimes I want to shoot a house, say, and I can't do it in non-crop mode without getting a lot of distracting moire/aliasing effects on the siding, say.
Please don't think I disagree with you on how the 5D3 has solved these problems. I do not know. It might be a filter. It might be binning. All I was saying is you were implying it is a filter and not being clear that it is your opinion, not fact. As a very well respected dev your opinions means a lot on these forums. With 'power comes responsibility' :)
I hope we can both work together to figure it out and find solutions in the meantime.
Quote from: maxotics on October 31, 2013, 02:29:15 PM
I meant it as when I read his posts I'm not sure if he's really serious or flippant. These are what Yogi Berra said as a manager
'90% of the game is half mental"
About a restaurant: "Nobody goes there anymore. It's too crowded"
"It ain't over 'til it's over"
You're the one that the fat general called a, "cheeky fellow." 8)
Quote from: SleeperNinja on October 31, 2013, 06:33:01 PM
You're the one that the fat general called a, "cheeky fellow." 8)
Thanks that cheers me up because only posts can I give that impression. In real life I now play the part of the "fat general". And let me say, just to be perfectly clear, without 1% I wouldn't be here. I know, as much as anyone, what he has accomplished with the EOS-M. I'm working hard to make that camera deliver on the promise 1% has made possible.
Quote from: maxotics on October 31, 2013, 06:21:42 PM
So moire is a HUGE problem in video because it distracts the viewer from the general image.
I saw this movie on a 5 meter screen and it had quite visible moire on some shots, but the juries of several film festivals didn't care
We get really obsessed in the technical part, because the rule of trendy cinema is Hollywood, but even there they don't care that much. Wasn't one season of 'House' shot with muddy 5d h264?
@rommex
Thank you for your comments.
There is no special technique, mabe it´s the lens or Davinci Resolve lite 10+fringing workaround. The majority of shots were done with open aparture and the background is slightly blured. Btw still a lot aliasing and moire in the shots but in this case acceptable for me.
Quote from: funkysensation on October 31, 2013, 06:52:22 PM
The majority of shots were done with open aparture and the background is slightly blured.
If your subject has no hard lines, say a face, then this technique will pretty much not show moire. AGAIN, I'm not saying you can't shoot without moire. I'm not saying that 1% doesn't have a point for most film-makers. All I'm saying is it is currently always a risk with the 50D in normal mode. If you shoot a building on a bright sunny day say, stopped-down, you're in for a world of hurt ;)
Quote from: goldenchild9to5 on October 31, 2013, 05:04:49 PM
I don't see what the big deal is with the Aliasing and Moire on the 50D, when you create great content the viewers won't even have time to pin point Aliasing and Moire, nor do they care about it. I've seen big time Aliasing in Hollywood movies, in major TV shows do most viewers care "No" they are more interested in the storyline. I am satisfied and thankful for even shooting "Raw" on a camera that didn't even shoot video a big WOW for that, and the images are comparable to camera's 20 - 50 times it's cost ;D just saying.
It could get pretty bad in certain scenes . . .
Quote from: menoc on October 30, 2013, 06:16:51 PM
Yes. in fact the 5DMIII has a built in filter which BTW, you can remove if you're brave enough . . . Check out James Miller's post on Vimeo:
The picture is almost as good as that of the VistaVision. Same vivid colors, same resolution. Great! Hate to hear that "film is better". Film is not better, it's worse because of grain.
If I want to match the focal length in crop mode to non crop mode can I use 5x wide angle lens adapter? And does they even exist?(I mean the 5x ones)
Quote from: lomka on October 31, 2013, 08:55:17 PM
If I want to match the focal length in crop mode to non crop mode can I use 5x wide angle lens adapter? And does they even exist?(I mean the 5x ones)
I use a Sigma 10-20mm in crop mode and it words great. You could also try a 4.5mm or an 8mm. Some are afraid of those lenses because they are "fish-eye", but in crop mode, they are not.
and i have 1 more question is there only 5x crop on 50d? cuz i have heared of 1920x1080 in 3x crop
Quote from: lomka on October 31, 2013, 09:44:54 PM
and i have 1 more question is there only 5x crop on 50d? cuz i have heared of 1920x1080 in 3x crop
I'm curious too. It looks like 3x. That the LV has issues showing the image correctly makes it seem like 5x. Eventually I'll do a test.
Quote from: lomka on October 31, 2013, 09:44:54 PM
and i have 1 more question is there only 5x crop on 50d? cuz i have heared of 1920x1080 in 3x crop
50D crop is 2.475x (1:1) and yes, there is only one crop mode.
Quote from: Andy600 on October 31, 2013, 10:12:22 PM
50D crop is 2.475x (1:1) and yes, there is only one crop mode.
So is this right, Andy? 10mm x 1.6 native crop = 16mm x 2.475 image crop is 39.60, or 40mm effective focal length? That is what it looks like to me, on both the 50D and EOS-M.
Quote from: maxotics on October 31, 2013, 10:28:55 PM
So is this right, Andy? 10mm x 1.6 native crop = 16mm x 2.475 image crop is 39.60, or 40mm effective focal length? That is what it looks like to me, on both the 50D and EOS-M.
Yes, that's how I work out APS-C + crop focal lengths on the 50D and I'm pretty sure it's correct :)
A full-size raw image is 4752 wide / 2.475 = 1920
Quote from: Andy600 on October 31, 2013, 10:33:37 PM
Yes, that's how I work out APS-C + crop focal lengths on the 50D and I'm pretty sure it's correct :)
A full-size raw image is 4752 wide / 2.475 = 1920
Thanks Andy, one more thing I can cross off my list!
Lens Effective ML Crop
4.5 18mm
8 32mm
10 40mm
15 59mm
20 79mm
24 95mm
28 111mm
40 158mm
50 198mm
60 238mm
85 337mm
Quote from: lomka on October 31, 2013, 09:44:54 PM
and i have 1 more question is there only 5x crop on 50d? cuz i have heared of 1920x1080 in 3x crop
50D only has 5x and 10x crop modes . . .
Edit: Actually, 5x only.
Quote from: menoc on October 31, 2013, 11:01:31 PM
50D only has 5x and 10x crop modes . . .
Edit: Actually, 5x only.
It's only got one recordable crop mode. The 5x and 10x are just zoom magnification for focussing.
Quote from: maxotics on October 31, 2013, 10:28:55 PM
So is this right, Andy? 10mm x 1.6 native crop = 16mm x 2.475 image crop is 39.60, or 40mm effective focal length? That is what it looks like to me, on both the 50D and EOS-M.
My 200mm zoom in crop mode:
200mm x 1.6 = 320mm x 2.475 = 798mm!!!
Quote from: Andy600 on October 31, 2013, 11:12:21 PM
It's only got one recordable crop mode. The 5x and 10x are just zoom magnification for focussing.
Yes. My bad. Live view zoom modes are 5x and 10x.
Quote from: menoc on October 31, 2013, 07:42:16 PM
It could get pretty bad in certain scenes . . .
You right it could get bad when your viewing it on your editing suite, but as soon as you export it to H.264 and upload to youtube, or vimeo you get an automatic softening of the image which works nicely on Aliasing..
Quote from: 1% on October 31, 2013, 04:39:40 PM
Then why are the modes and behavior the same as 1x and 5x mode on other cams? All I see is rumor posts before the camera was released and people speculating it has 3x3 binning but no official or empirical proof that it is.
Then I see this guy:
http://www.canonwatch.com/eos-5d-mark-iii-hacked-anti-aliasing-filter-removed-more-sharpness/
Filter is blurring/darkening the image... hmmm sounds like that would take down moire just like the VAF. Also the moire issues seem related to sensor size and resolution output + how it divides up and then debayers.
The issue of Moire and Aliasing isn't as simple as the strength of the OLPF or the use of Pixel Binning alone. Also there is the sensor and it's megapixel count that seems to also play a part in the process. The Nikon D7100 doesn't have an AA filter and is able to record without producing Aliasing and Moire. I think that it's pixel Pitch of 3.9 helps in this regard as it seems it might help the GH2 which has a pixel pitch of 3.6. I think a smaller pixel pitch plus really good pixel binning may be enough to handle Aliasing and Moire even without an AA Filter. It's all just my theory anyway.
The larger pixel pitch of 6.1 on the 5Dmk3 sensor may require that they have a strong AA filter in place in addition to Pixel Binning or maybe it's enough all by itself. My guess is that Canon isn't line skipping on the 5Dmk3. I think the 5Dmk3 video in RAW is so good that I can't imagine that it's only the stronger AA filter that is doing the job.
Update to Creative Cloud 12.1 is out!
To find out more see my post on my blog:
http://theindieshooter.com/2013/09/11/native-cinema-dng-support-for-adobe-premiere-pro-cc-coming-in-october-2013/ (http://theindieshooter.com/2013/09/11/native-cinema-dng-support-for-adobe-premiere-pro-cc-coming-in-october-2013/)
(http://i.imgbox.com/acg91acH.png)
Quote from: menoc on November 01, 2013, 12:28:53 AM
Update to Creative Cloud 12.1 is out!
(http://i.imgbox.com/acg91acH.png)
Has there been any word about CS6 CinemaDNG support? Or are they keeping this exclusive to CC?
I think all they plan to do for CS6 is bug fixes but no new features. They want people to upgrade to CC!
Quote from: 1% on October 31, 2013, 04:39:40 PM
Then why are the modes and behavior the same as 1x and 5x mode on other cams? All I see is rumor posts before the camera was released and people speculating it has 3x3 binning but no official or empirical proof that it is.
Then I see this guy:
http://www.canonwatch.com/eos-5d-mark-iii-hacked-anti-aliasing-filter-removed-more-sharpness/
Filter is blurring/darkening the image... hmmm sounds like that would take down moire just like the VAF. Also the moire issues seem related to sensor size and resolution output + how it divides up and then debayers.
just one moire comment on this subject
http://www.youtube.com/watch?v=vVXns1R8ACc (http://www.youtube.com/watch?v=vVXns1R8ACc)
"just one moire comment on this subject"
http://www.youtube.com/watch?v=vVXns1R8ACc
[/quote]
Good point! :)
i think it would be cool if some of the companys made adapter for ml crop modes to match focal lenght of non crop one, like taking lens closer to the sensor with magnifying glass or something(like fx and dx lenses)
Quote from: lomka on November 01, 2013, 01:39:03 PM
i think it would be cool if some of the companys made adapter for ml crop modes to match focal lenght of non crop one, like taking lens closer to the sensor with magnifying glass or something(like fx and dx lenses)
It exists and they call it "speed booster" but the flange distance is too big to do so on canons.
Quote
http://www.youtube.com/watch?v=vVXns1R8ACc
Seems like a decent fix.
So how to find out whats going on for real with a test?
I've been wanting to use the Visioncolor LOG ACR profile http://www.magiclantern.fm/forum/index.php?topic=8816.0 (http://www.magiclantern.fm/forum/index.php?topic=8816.0) but obviously raw2dng was using the default model name 'Canikon'. This meant the correct DCP is not used by ACR, even if it is installed.
I've temporarily hardcoded the model name for the 50D and uploaded a new raw2dng.exe that will enable ACR to correctly identify 50D dng files.
https://bitbucket.org/andy600/tl50d/downloads/raw2dng_50DONLY.zip (https://bitbucket.org/andy600/tl50d/downloads/raw2dng_50DONLY.zip)
Personally I use BATCHelor to convert my raw files so just swapped out the older raw2dng.exe with the new one in the relevant app folder.
This raw2dng.exe is for the 50D only!
Has anyone tried both Lexar 16GB 1000x and Transcend 16GB 1000x on Canon 50D? The Lexar is more expensive - I wonder if it provides any practical advantage when used on 50D?
I think the model name should be a command line switch. None of the cams get identified.
Quote from: 1% on November 02, 2013, 06:06:12 PM
I think the model name should be a command line switch. None of the cams get identified.
Yes, that would make more sense but would mean raw conversion apps need to be updated. BATCHelor, RAWanizer and a couple of others seem to have stopped development.
Just saw g3gg0 posted something about model name in mlv. The stubs need to be added or something. Not sure if it would work with raw_rec??
http://www.magiclantern.fm/forum/index.php?topic=7122.msg86447#msg86447 (http://www.magiclantern.fm/forum/index.php?topic=7122.msg86447#msg86447)
Problem is that it never adds the camera name to the footer for raw_rec, AFAIK. Yea, it works 100% in mlv except for the pink frames, etc and there are no batch tools to break compatibility with :(
If you have one cam its easy to hardcode it but for me its a bit of a PITA since I'd have to make a separate batch tool copy + matched raw rec for every cam.
Quote from: 1% on November 02, 2013, 06:43:24 PM
Problem is that it never adds the camera name to the footer for raw_rec, AFAIK. Yea, it works 100% in mlv except for the pink frames, etc and there are no batch tools to break compatibility with :(
If you have one cam its easy to hardcode it but for me its a bit of a PITA since I'd have to make a separate batch tool copy + matched raw rec for every cam.
I'm wondering if the pink/corrupt frame issue with mlv might be because there is a lot of metadata added. We only really need camera model, ISO and WB. Maybe an 'MLV lite' module with stripped down meta/exif would be better for lower-end cams or selectable on/off's for each meta field? It's a pity mlv has issues on the 50 atm :(
I've been up to my eye-balls in sensor pixel data. Do any of you think a raw frame from different cameras can be identified somehow? Perhaps some cameras have min/max values?
One really good trick to remove moiré/color fringing edges is to apply a chroma blur on your footage.
On premiere, make a new adjustement layer, select the blend mode to chroma and apply a small blur.
Quote from: bzhwindtalker on November 02, 2013, 07:30:36 PM
One really good trick to remove moiré/color fringing edges is to apply a chroma blur on your footage.
On premiere, make a new adjustement layer, select the blend mode to chroma and apply a small blur.
Alex has already added that to raw2dng by the way. I don't know where he keeps the master thread on raw2dng, but some discussion here
http://www.magiclantern.fm/forum/index.php?topic=6658.msg85490#msg85490
Yea, maybe too much meta data.. I think the problem is when its written you get a pink frame. Its a problem on 7D too, probably 5DII as well.
I am still yet to try the RAW video feature on my 50D. I was held back by the lack of a fast card, and by high cost of getting one (Komputerbay cards are not really attractive here, due to the ridiculously high shipping costs - 40$; given how likely the card would have to be sent back, this is a non-starter).
I ended up ordering Lexar 32GB 1000x - am I right that this is the card most likely to get the most out of 50D in terms of RAW video? That's what my research here showed anyway. I was thinking of 16GB, but it appears that the 32GB is substantially faster (145 MB/s vs. 95 MB/s rated write speed); I don't really care about the size (I doubt I'll do much video recording with my 50D).
These cards are currently on sale at B&H Photo video (until November 8 ): 67$ and 119$ for 16 and 32GB, respectively (comes to 87 and 147 CAD all in in Canada; the cheapest you can find in Canada is 218 CAD for 32GB, so it is big savings).
Is there a consensus on what build/trunk of ML currently provides the best uncropped RAW video capabilities? I don't think I am interested in the cropped mode, as I am a big bokeh fun, and only consider doing video with my 50D to make use of my fast primes (like Canon 135mm f2.0 lens).
32gb should be ok for like 5 mins of big raw video.
Quote from: 1% on November 03, 2013, 03:59:06 PM
32gb should be ok for like 5 mins of big raw video.
1% Not more like 8 minutes? 4gb/min?
On 32 vs 16. I have a good Toshiba 16gb card and have not been able to achieve 1080p following the instructions on how to shut almost everything off to get it. My gut feeling is yes, the 32gb cards are slightly faster than the 16gb. So think you made a good choice there.
could be 8, I only have the 64s.
I think its possible to have B/W preview + no other indicators and GD on both on 50D and 7D. I didn't see any pink frames from cursory testing.. if you use anything else raw then pink frames or big slowdowns.
@1% - I see you're doing something with your compiler. Will I still be able to compile or do I need to change anything?
I'm testing compiling on windows, it should be working cross platform. Does it? I'm using latest q3 arm but that was updated for linux a while ago.
still working :)
Should be 7.6 minutes for uncropped video. And even that is an overkill for me (I'll probably only try to shoot microstocks video, which is limited to 30 seconds), but 32GB Lexars are apparently much faster than 16GB ones.
Quote from: 1% on November 03, 2013, 04:43:48 PM
could be 8, I only have the 64s.
I think its possible to have B/W preview + no other indicators and GD on both on 50D and 7D. I didn't see any pink frames from cursory testing.. if you use anything else raw then pink frames or big slowdowns.
Stock sites actually worth doing?
Quote from: 1% on November 03, 2013, 06:04:21 PM
Stock sites actually worth doing?
I have no idea. My photo microstocks site (dreamstime, were I already earned 600+$ for ~100 photos I have there) has just started accepting video. Contributors there are still trying to figure out what will sell and what will not.
Hy Andy! I saw your last 50D build uploaded on your repository! What's new? Or I missed your whatsnew post? Many thanks!
Quote from: dlrpgmsvc on November 03, 2013, 11:08:20 PM
Hy Andy! I saw your last 50D build uploaded on your repository! What's new? Or I missed your whatsnew post? Many thanks!
It's mainly about the mlv player (also plays usual raw video via the file manager). Playback can be in grayscale or color and has transport controls (accessed with the pic style button). There is also selectable color preview for raw video but it's very slow so use global draw off.
I'm using Andy's TL (Oct 11) build and shooting in full sensor mode in an aspect ratio of 2.39:1 and setting "1600" as the frame width, which produces a video frame size of 1584 x 674.
Having created DNG files from the ML raw video file, I find that exporting tiffs from these DNGs in Adobe Camera Raw produces frames the same size as the DNGs, but exporting tiffs from RAW Therapee produces a slightly cropped frame of 1576 x 666, which is 8 pixels lost from both height and width. Anyone else get this slight crop with RAW Therapee?
Quote from: TrueIndigo on November 04, 2013, 03:22:08 PM
I'm using Andy's TL (Oct 11) build and shooting in full sensor mode in an aspect ratio of 2.39:1 and setting "1600" as the frame width, which produces a video frame size of 1584 x 674.
Having created DNG files from the ML raw video file, I find that exporting tiffs from these DNGs in Adobe Camera Raw produces frames the same size as the DNGs, but exporting tiffs from RAW Therapee produces a slightly cropped frame of 1576 x 666, which is 8 pixels lost from both height and width. Anyone else get this slight crop with RAW Therapee?
Yep. Raw Therapee does do something weird when exporting. I tend to upscale larger than the intended final dimensions then scale footage back down to fit.
Adobe Camera Raw Does an excellent job..
Good news for those who are waiting the 50D VAF from Mosaic Engineering. They answered my email, and I ordered a final version ! They plan to go into production as soon as they can (I assume that the 70D version was their priority). I will do a video review and share before/after DNGs when I get it.
Quote from: Heldico on November 05, 2013, 11:04:48 AM
Good news for those who are waiting the 50D VAF from Mosaic Engineering. They answered my email, and I ordered a final version ! They plan to go into production as soon as they can (I assume that the 70D version was their priority). I will do a video review and share before/after DNGs when I get it.
That's good news, I've just emailed them to find out when they are available to buy from the website.
I'm tempted too!
Quote from: Heldico on November 05, 2013, 11:04:48 AM
Good news for those who are waiting the 50D VAF from Mosaic Engineering. They answered my email, and I ordered a final version ! They plan to go into production as soon as they can (I assume that the 70D version was their priority). I will do a video review and share before/after DNGs when I get it.
Quote from: rockfallfilms on November 05, 2013, 04:10:59 PM
That's good news, I've just emailed them to find out when they are available to buy from the website.
Great News! How much are we talking about?
QuoteGreat News! How much are we talking about?
Same price as the other APS-C filter, i.e. 295 $.
Quote from: Heldico on November 05, 2013, 05:16:02 PM
Same price as the other APS-C filter, i.e. 295 $.
It's difficult for me at that price because I think sell my 50D with lens for $500 and get a BMPCC for $500 more instead of $800 invested in 50D with VAF. These filters need to be at $200 for them to hit any sort of volume IMHO, at least for the APS-C sized cameras. Might want to check with David if he can do them at that price if he gets X amount of commits.
I'd rather invest the money towards an anamorphic 2x and shoot in crop. The VAF degrades the image to much for me.
Quote from: maxotics on November 05, 2013, 06:55:55 PM
It's difficult for me at that price because I think sell my 50D with lens for $500 and get a BMPCC for $500 more instead of $800 invested in 50D with VAF. These filters need to be at $200 for them to hit any sort of volume IMHO, at least for the APS-C sized cameras. Might want to check with David if he can do them at that price if he gets X amount of commits.
$200 would be awesome, but they do have to make a return on investment. I'd guess that they could come down a bit if enough people ask for them.
Quote from: menoc on November 05, 2013, 07:59:23 PM
$200 would be awesome, but they do have to make a return on investment. I'd guess that they could come down a bit if enough people ask for them.
BTW, have shots been taken with the final model of the VAF? I know there was an ML user testing a pre-production model . . .
Quote from: Andy600 on November 05, 2013, 07:39:39 PM
I'd rather invest the money towards an anamorphic 2x and shoot in crop. The VAF degrades the image to much for me.
Is there a link to the test shots? I'd like to see them . . .
Quote from: menoc on November 05, 2013, 08:08:02 PM
Is there a link to the test shots? I'd like to see them . . .
Levi S. Davis should pop his head back into this thread at some point, he's been testing the prototype.
Here's his video for the prototype: http://vimeo.com/74470756
For me this is worth the money, especially at 200 bucks!
I was definitely interested in buying one but I've just worked out how much it will cost me.
By the time I've paid import tax and VAT to the UK it would cost nearly £300 which is about $480. It's a shame that Mosaic don't have a UK/Europe distributor. Unfortunately I live in Ripoff Britain!
Therefore I'm in two minds now and I'd need to see some more convincing tests before I spent the money.
I cant get why people think that BMPCC is better than 50d.
1. APS-C sensor is way too bigger than the Super 16 one.
2. you cant get that film look effect on BMPCC, users say that it shoots iPhone like video.
3. you can get crop factor similar to BMPCC on 50D in 2.475x crop mode.
4. you can get canon for 300-400$ when BMPCC costs 1000$. (300-400$ + 295$(VAF) = 595-695$ + you get pretty good camera for stills as well)
5. 50d can run ML software, that means you have tons of addons on your camera to make your work easier.
Quote from: Andy600 on November 05, 2013, 07:39:39 PM
I'd rather invest the money towards an anamorphic 2x and shoot in crop. The VAF degrades the image to much for me.
Andy:
I am with you on that, but wouldn't non crop mode suit anamorphic shooting just as well because of the 4:3 sensor?(assuming you are shooting x2). Although On non crop you are not starting out at 1920x1080.
Quote from: lionelp on November 05, 2013, 09:34:29 PM
Andy:
I am with you on that, but wouldn't non crop mode suit anamorphic shooting just as well because of the 4:3 sensor?(assuming you are shooting x2). Although On non crop you are not starting out at 1920x1080.
What Andy is saying is, he's not willing to compromise quality. When you shoot in crop mode, the camera is reading out the entire feed - no line skipping- therefore you get much better quality and no moire and aliasing. Of course, the drawback is that framing is a bit more difficult and you must shoot with the widest angled lens you can get, something like a 10 or 20mm lens in order to have more of a "normal" lens type of frame.
I do agree with Andy when it comes to the quality benefits of shooting in crop mode. But having options is always good as well. Especially in situation where you have to use a zoom lens to get wide or close-up shots quickly and not have to worry too much about aliasing and moire.
Quote from: lionelp on November 05, 2013, 09:34:29 PM
Andy:
I am with you on that, but wouldn't non crop mode suit anamorphic shooting just as well because of the 4:3 sensor?(assuming you are shooting x2). Although On non crop you are not starting out at 1920x1080.
Of course and there is a choice of aspect ratios. Shooting anamorphic also seems to help a little with aliasing and moire. Julian H's shot some 50D anamorphic footage and posted it earlier in this thread https://vimeo.com/67023056 (https://vimeo.com/67023056)
Blargh...
so now shutter displayed is the photo shutter, ie wrong
shutter in the ML menu is for some reason converted to a small version the real ADTG shutter range when FPS override is on, so wrong
the range is like fps - ~100 but you get values like 101.2, etc when checking via ADTG gui it looks like we have the whole range just its displayed completely strange
so....
right now don't trust the shutters displayed so much in video.
So looking at it further maybe something with base frequency + shutter timer.... if you copy the base from other cameras you get different fps calculated stock, right now it shows 29.985 which sounds like its a bit off from 29.97
Is the shutter speed issue just on the latest build? I'm using one a couple of weeks old and the motion seems ok.
Has anyone here tried out the After Effects CC detail preserving upscale on 50D footage? I'm only on CS6 so I can't try it.
Quote from: menoc on November 05, 2013, 10:08:37 PM
What Andy is saying is, he's not willing to compromise quality. When you shoot in crop mode, the camera is reading out the entire feed - no line skipping- therefore you get much better quality and no moire and aliasing. Of course, the drawback is that framing is a bit more difficult and you must shoot with the widest angled lens you can get, something like a 10 or 20mm lens in order to have more of a "normal" lens type of frame.
I do agree with Andy when it comes to the quality benefits of shooting in crop mode. But having options is always good as well. Especially in situation where you have to use a zoom lens to get wide or close-up shots quickly and not have to worry too much about aliasing and moire.
Good point! Makes sense! :)
Got it! I agree with you ( not that I think that I know so much...I appreciate all that you, 1%, Alex and all the others have done with the 50D and ML RAW). Awesome footage. I saw JulianH's post and video as I was reading through the posts. I love the footage from the 50D. It is somewhat different looking (has a slightly different footprint) than the oher Canon ML raw footage. And very film like IMO.
Quote from: Andy600 on November 05, 2013, 10:10:28 PM
Of course and there is a choice of aspect ratios. Shooting anamorphic also seems to help a little with aliasing and moire. Julian H's shot some 50D anamorphic footage and posted it earlier in this thread https://vimeo.com/67023056 (https://vimeo.com/67023056)
QuoteIs the shutter speed issue just on the latest build? I'm using one a couple of weeks old and the motion seems ok.
I think its been an un-noticed issue for a while, the motion will be ok but the numerical values aren't correct. The shutter is just blanking so its not a deal breaker but annoying when you want to know what's really 1/48, etc. Go by how it looks on the screen vs numbers.
Could be a placebo effect (or mentioned earlier)
When I update any setting in ML on my 50D, the first time I shoot in RAW my write speed hovers around 65MBs. However when I make a change and turn the camera on and off (or just the first time I turn the camera on) I get write speeds around 75MBs. Does anyone else experience anything similar?
Quote from: teedidy on November 06, 2013, 09:00:06 PM
Could be a placebo effect (or mentioned earlier)
When I update any setting in ML on my 50D, the first time I shoot in RAW my write speed hovers around 65MBs. However when I make a change and turn the camera on and off (or just the first time I turn the camera on) I get write speeds around 75MBs. Does anyone else experience anything similar?
Typical for cards to need to 'warm up'. If you go to the Movie tab, down to Raw Video, it is now hidden under the advanced (on most recent build), you will find Warm Up Card. You can select a mb size to write to the card at boot.
I usually don't bother. I tend to get my settings right and shoot a 10-20sec test video, and that warms the card up for continuous shooting.
QuoteI get write speeds around 75MBs. Does anyone else experience anything similar?
Yea, the first time I shoot after turning off dialog timers its slowish. Instead of card warmup I shoot till I see 75-80 and then delete the raw file. After that its good until power off.
Quote from: lomka on November 05, 2013, 09:25:55 PM
I cant get why people think that BMPCC is better than 50d.
1. APS-C sensor is way too bigger than the Super 16 one.
2. you cant get that film look effect on BMPCC, users say that it shoots iPhone like video.
3. you can get crop factor similar to BMPCC on 50D in 2.475x crop mode.
4. you can get canon for 300-400$ when BMPCC costs 1000$. (300-400$ + 295$(VAF) = 595-695$ + you get pretty good camera for stills as well)
5. 50d can run ML software, that means you have tons of addons on your camera to make your work easier.
While I would buy a Canon over the BMPCC anytime, you are quite wrong about it's capabilities. It's made for micro 4/3 glass, the crop factor is zero and it can get quite the film look, the sensor has a dynamic range comparable with cameras worth 10x the price, so I have no idea which "users" you refer to.
That being said, a 50D setup would cost you less and as we all see, one can get stunning images from it.
1% - any math we can do to figure out what shutter speed we are using? Is the issue only with the latest build?
Quote from: 1% on November 06, 2013, 10:47:38 PM
Yea, the first time I shoot after turning off dialog timers its slowish. Instead of card warmup I shoot till I see 75-80 and then delete the raw file. After that its good until power off.
Thanks for the tip 1%. I'm going to try that next time!
It is a problem forever but before at least you got the value from the ML menu and could see when the ISO was being adjusted. Now with the new bars (~oct/1) it seems to be showing photo shutter and not displaying digital iso.
Quote from: johansugarev on November 07, 2013, 04:09:24 AM
While I would buy a Canon over the BMPCC anytime, you are quite wrong about it's capabilities. It's made for micro 4/3 glass, the crop factor is zero and it can get quite the film look, the sensor has a dynamic range comparable with cameras worth 10x the price, so I have no idea which "users" you refer to.
That being said, a 50D setup would cost you less and as we all see, one can get stunning images from it.
The mount on the BMPCC maybe be made for micro 4/3 glass, but the sensor is sized for Super16mm glass. There will be a crop factor of around 3 when comparing to full frame. The 50D has a 1.6 crop factor.
Therefore the BMPCC will require an investment in lenses to cover the wide end and also if you are wanting shallow DOF that has a similar look to the 50D then you will need fast lenses.
They are different cameras, personally I see the 50D as a cinema type camera and the BMPCC as more of a documentary camera. That extra DR will come in useful when you are in a situation that you can't light properly.
Quote from: rockfallfilms on November 07, 2013, 10:43:01 AM
The mount on the BMPCC maybe be made for micro 4/3 glass, but the sensor is sized for Super16mm glass. There will be a crop factor of around 3 when comparing to full frame. The 50D has a 1.6 crop factor.
Therefore the BMPCC will require an investment in lenses to cover the wide end and also if you are wanting shallow DOF that has a similar look to the 50D then you will need fast lenses.
They are different cameras, personally I see the 50D as a cinema type camera and the BMPCC as more of a documentary camera. That extra DR will come in useful when you are in a situation that you can't light properly.
I'm surprised people aren't seeing the Metabones Speed Booster with the BMCC as a great alternative, making the BMCC nearly Super 35 and gaining 1 full stop brighter footage. After all, whether you like it or not, you are simply not getting 1080p out of the 50D.
(http://philipbloom.net/wp-content/uploads/2013/05/Comparison.png)
https://www.youtube.com/watch?v=LDD0XTiYXco here you can see the crop factor of the BMPCC compared to the DSLR cameras
Quote from: PressureFM on November 07, 2013, 11:52:08 AM
I'm surprised people aren't seeing the Metabones Speed Booster with the BMCC as a great alternative, making the BMCC nearly Super 35 and gaining 1 full stop brighter footage. After all, whether you like it or not, you are simply not getting 1080p out of the 50D.
If money wasn't an object then yes a BMCC and speed booster is a great option. However, that setup would require me shelling out £1500 for the BMCC £400 for the speedbooster + a set of Nikon lenses to use it.
The 50D provides a low cost option to get into raw shooting. No it's not 1080P but once it's upscaled and sharpened it's fine. In an ideal world of course I'd like to have more resolution but I will make do with what I have for a bargain price.
Basically crop factor battle looks like this:
5DIII 1:1
50D no crop: 1:1.6
50D crop 1:3.96
BMPCC 1:2.88
BMCC 1:2.4
BMCPC 4k 1:1.7
GH2 1:88
GH3 1:2
ARRI ALEXA 1:1.5
RED 1:1.4 (depends on format)
Canon APS-C 1:1.6
Sony, APS-C 1:1.5
Nikon APS-C 1:1.5
Thanks, now I just need to bookmark this! :)
added! :)
and re-modified
You do get 1080 on the 50D in crop. Plain and simple.
Without necessarily investing in all new glass (speaking personally that is). :)
Quote from: PressureFM on November 07, 2013, 11:52:08 AM
I'm surprised people aren't seeing the Metabones Speed Booster with the BMCC as a great alternative, making the BMCC nearly Super 35 and gaining 1 full stop brighter footage. After all, whether you like it or not, you are simply not getting 1080p out of the 50D.
(http://philipbloom.net/wp-content/uploads/2013/05/Comparison.png)
Wow, with that test crop is huge. So 7D is close to alexa in 1x and 50D is pretty much BMPCC in crop.
Question for anyone shooting on the 50D with a monitor - What happens to the monitor display when you shoot in crop mode?
All APS-C cover 90-100% Alexa FOV, being Super35mm which is cinema standard, which is same as APS-C.
Quote
Question for anyone shooting on the 50D with a monitor - What happens to the monitor display when you shoot in crop mode?
I think it just gives you the same image as the LV.
Quote from: Andy600 on November 07, 2013, 03:49:03 PM
Question for anyone shooting on the 50D with a monitor - What happens to the monitor display when you shoot in crop mode?
What 1% said. I shoot w/ HDMI and crop mode displays exactly what LV is displaying. No change.
Thanks guys
I am excited - finally I got my first speedy card (Lexar 32GB 1000x; ordered from US), so I plan to start playing with raw video this weekend (which happens to be a long weekend here in Canada).
Selling my 50D if anyone is interested - http://losangeles.craigslist.org/wst/pho/4177750258.html
I've been using the Tragic Lantern build from 11 October by Andy600. First results were good. I was getting continuous recording at 1920x1080 in crop, with the data rate reported at around 70-80MB/s
For some reason now, it drops out after a second or two at that resolution. Any suggestions what to try. I could try formatting the card, but the thing is, if I have to format the card every time it gets a third full, it's not much use.
Could anyone summarise the difference in the level of support for raw on the 50d between TL and the nightlies. I'm also getting the pink screen on half shutter bug, which I found a report saying was resolved, but it only mentioned the 5d3.
Also I've been reading about auto ETTR with support for automatic dual-iso being available. Is there a build that has that and gives good results for raw on the 50D?
Turn off dialog timers, make sure GD is off while recording. Also use the most memory you can... I think jpeg quality does it.
Quote from: jamesd256 on November 08, 2013, 01:50:50 AM
I've been using the Tragic Lantern build from 11 October by Andy600. First results were good. I was getting continuous recording at 1920x1080 in crop, with the data rate reported at around 70-80MB/s
For some reason now, it drops out after a second or two at that resolution. Any suggestions what to try. I could try formatting the card, but the thing is, if I have to format the card every time it gets a third full, it's not much use.
Could anyone summarise the difference in the level of support for raw on the 50d between TL and the nightlies. I'm also getting the pink screen on half shutter bug, which I found a report saying was resolved, but it only mentioned the 5d3.
Also I've been reading about auto ETTR with support for automatic dual-iso being available. Is there a build that has that and gives good results for raw on the 50D?
Thanks 1% for your reply. I hadn't noticed the FPS override had been reset to off, so it was trying to do 30fps.
However it's actually got worse now. As soon as I enable raw video, the stability takes a nosedive. FPS override starts reporting about 1-2 FPS , the camera becomes unstable and crashes within a minute, needing a battery yank.
I have tried re-formatting, but the problem won't go away. Latest attempt at turning on raw module produced a crash with a crashlog:
ASSERT: 0
at Stub.c:29, task LVC_AE
lv:1 mode:3
Magic Lantern version : Andy600.Build.2013Oct11.50D109
Mercurial changeset : dd08a07137b8+ (unified) tip
Built on 2013-10-11 15:48:27 UTC by magiclantern@magiclantern-VirtualBox.
Free Memory : 200K + 3708K
EDIT: Having tried resetting camera and ML settings, and still having the issue, I simply switched FPS over-ride to a different value (25) then back to 23.96, and the issue went away. Recording 1080p again.
I only did a quick test last night with my my card Lexar 32GB 1000x and TL Oct 11 build, and I had no issues recording uncropped 3:2 video at 24 fps, with ~79.5 MB/s. I'll do more testing this weekend.
An idea - sorry if this was already discussed. Is it feasible to create a "virtual rail system" using crop mode on 50D? Are there any technical reasons which would only allow crop video to be sampled from the center of the frame? If not, perhaps such virtual panning is possible to implement? Say, one can specify how many pixels per frame the horizontal shift should be (could be negative), same for vertical shift. Then the crop area would be initially placed at one end of the full frame, and then would shift every frame by the specified X and Y pixels values, until it reaches the opposite end of the frame. I've seen this effect in some movies, looks very cool. I suspect it won't look real when using a wide angle lens (because of the perspective distortions at the edges of the frame), bur for 50mm and longer this should not very very obvious.
QuoteI have tried re-formatting, but the problem won't go away. Latest attempt at turning on raw module produced a crash with a crashlog:
You have some face detection or auto exposure mode on.
Quote from: pulsar124 on November 08, 2013, 01:07:45 PM
I only did a quick test last night with my my card Lexar 32GB 1000x and TL Oct 11 build, and I had no issues recording uncropped 3:2 video at 24 fps, with ~79.5 MB/s. I'll do more testing this weekend.
An idea - sorry if this was already discussed. Is it feasible to create a "virtual rail system" using crop mode on 50D? Are there any technical reasons which would only allow crop video to be sampled from the center of the frame? If not, perhaps such virtual panning is possible to implement? Say, one can specify how many pixels per frame the horizontal shift should be (could be negative), same for vertical shift. Then the crop area would be initially placed at one end of the full frame, and then would shift every frame by the specified X and Y pixels values, until it reaches the opposite end of the frame. I've seen this effect in some movies, looks very cool. I suspect it won't look real when using a wide angle lens (because of the perspective distortions at the edges of the frame), bur for 50mm and longer this should not very very obvious.
You can choose which area is used in crop by moving the box as usual before you record.
There is a digital dolly setting in the raw menu, which is supposed to let you use the joystick to pan the sampled area during cropped recording. In my case it doesn't work as expected. Once the option is enabled, the joystick ceases to move the focus box at all, recording or not. I've looked for documentation on the feature, but obviously it's not in the user guide yet.
From what I've seen demo'ed, it could do with a softer start. Looks a bit robotic. Also, would be good to be able to set start and end points and speed as you suggest.
Its not that complex but you should be in zoom mode for it to move the box around, otherwise its got nothing to move.
Quote from: jamesd256 on November 08, 2013, 10:45:00 PM
You can choose which area is used in crop by moving the box as usual before you record.
There is a digital dolly setting in the raw menu, which is supposed to let you use the joystick to pan the sampled area during cropped recording. In my case it doesn't work as expected. Once the option is enabled, the joystick ceases to move the focus box at all, recording or not. I've looked for documentation on the feature, but obviously it's not in the user guide yet.
From what I've seen demo'ed, it could do with a softer start. Looks a bit robotic. Also, would be good to be able to set start and end points and speed as you suggest.
Thanks - I wasn't aware of this existing feature. I'll see if it works for me.
Quote from: 1% on November 08, 2013, 11:01:22 PM
Its not that complex but you should be in zoom mode for it to move the box around, otherwise its got nothing to move.
Once digital dolly is on, the joystick does nothing while in zoom mode for me. If I turn it off again, the joystick moves the focus box as normal. I understand this is not the intended functionality, but I'm not too bothered about digital dolly until it improves (yes it's feasible I might have a go at coding some improvements if nobody else has plans for it).
Guess I'll have to check it and see what it does. With the large res on 50D I'm more interested in getting center of the lens.
No news on the final VAF from Mosaic Engineering, as far as emails or phone calls.
... Been on a shoot for the past 5 days in Tucson,AZ. Just shoot a documentary for the 14th conference for the National Scenic and Historic trails. Volunteered for the project and shoot about 1TB of footage.
Had two files in the mix of nearly 200 shots where the 2nd .roo was not finished in the writing due to camera errors. Will look into both the VAF and to find a way to fix a .roo file.
Again, the VAF isn't hitting the 50 d's resolution that hard. Also, I read somewhere about the 5d3 having an anti-aliasing filter and the possibility of removing the filter. Is the 50 d the same?
Quote from: LEVISDAVIS on November 09, 2013, 01:31:18 AM
No news on the final VAF from Mosaic Engineering, as far as emails or phone calls.
... Been on a shoot for the past 5 days in Tucson,AZ. Just shoot a documentary for the 14th conference for the National Scenic and Historic trails. Volunteered for the project and shoot about 1TB of footage.
Had two files in the mix of nearly 200 shots where the 2nd .roo was not finished in the writing due to camera errors. Will look into both the VAF and to find a way to fix a .roo file.
Again, the VAF isn't hitting the 50 d's resolution that hard. Also, I read somewhere about the 5d3 having an anti-aliasing filter and the possibility of removing the filter. Is the 50 d the same?
Surely you mean .r00?
The 5D Mark III has an Optical Low Pass Filter, as the only camera compatible with Magic Lantern. Removing it also introduces problems because that filter, filters light in the infrared (IR) wavelength, which would cause your color balance to shift to a more purple hue (everything black will shift to a slight purple tint). This can be remedied by using an IR Filter in front of the lens though. Oh yeah, and the filter is there to remove moiré in the first place.
I don't think anyone have tried it out with RAW video though.
One more catch, you also remove the ultrasonic dust reduction panel, which is in the OLPF as well. Meaning you can't remove dust any longer and will need to send it in to a professional technician to get it cleaned.
I'd rather add the OLPF from 5DIII to the 50D than remove the one it has already :)
If you do some more research you'll find that people who removed the OLPF from their 5D3's have since had them reinstalled and that can be costly as the original one is destroyed during removal. We actually need a better/stronger one than we have (from memory I think the 50D actually has 2).
A lot of the new cameras don't have OLPF's but that is only viable because of the extremely high number of sensor pixels and only really beneficial for stills. Video from non OLPF sensors usually have a ton more aliasing and moire than low MP sensors.
IMO the VAF is the best choice for reducing moire and aliasing but the VAF image looks like it's half way between native H.264 and raw. It looks pretty bad to my eyes but, without being too critical of Levis's prototype test shots, I would like to see a more detailed test of the 50D with a VAF and a sharp L Lens to be sure. At the moment I feel it's a nice try but not worth the cost for me because as someone said previously, living in Europe bumps the cost up considerably and if I were to spend that kind of money I'd be looking at a BMPCC or a good wide or anamorphic lens.
@1% - got trouble compiling mlv_rec
../lv_rec/raw2dng.c: In function 'main':
../lv_rec/raw2dng.c:72:5: warning: implicit declaration of function '_fseeki64' [-Wimplicit-function-declaration]
[ GCC ] raw2dng
raw2dng.o: In function `main':
raw2dng.c:(.text.startup+0x6c): undefined reference to `_fseeki64'
collect2: error: ld returned 1 exit status
make: *** [raw2dng] Error 1
I tried g3gg0's pre-built module and I swear the raw images look better than raw_rec but still getting random corrupt frames and missing camera model ERR. Does this happen on the 7D too?
Quote from: Andy600 on November 09, 2013, 06:03:02 PM
Video from non OLPF sensors usually have a ton more aliasing and moire than low MP sensors.
I've never seen any moire/aliasing on my Nikon D7100's videos ... (24Mpix and without OLPF)
Quote from: Andy600 on November 09, 2013, 06:03:02 PM
IMO the VAF is the best choice for reducing moire and aliasing but the VAF image looks like it's half way between native H.264 and raw. It looks pretty bad to my eyes but, without being too critical of Levis's prototype test shots, I would like to see a more detailed test of the 50D with a VAF and a sharp L Lens to be sure.
Looking from Levis's test footage the VAF seems to eliminate all the false details, which could give the feeling of loosing details but actually just kill artifacts that were never there. Anyway I will do a detailed test when I get mine and will see if my guesses are true or not.
@1% - Just looking at the EXIFs of some mlv DNGs and 'subject distance' is changing on corrupt frames. I'll dig deeper into the exifs and see what else is being screwed. Maybe if those bits of metadata are voided it might clear up the corrupt/pink frame issues!?
QuoteDoes this happen on the 7D too?
Yea, much worse. Last one I tried it was slowing down LV and causing pink frames all over.
Good news is that the speed seems finally there, maybe better even. Will have to try today's see if there are improvements.
What are you compiling with... btw this is for the tools that aren't compiling.
Quote from: 1% on November 09, 2013, 08:01:30 PM
Yea, much worse. Last one I tried it was slowing down LV and causing pink frames all over.
Good news is that the speed seems finally there, maybe better even. Will have to try today's see if there are improvements.
What are you compiling with... btw this is for the tools that aren't compiling.
Speed sounds good :)
I'm compiling with the pre-built compiler on Ubuntu.
It should be using fseeko then according to the preprocessor.
Weird. Restarted and it compiles now ???
Not noticing any speed increase. What buffer method are you using (mlv)?
Still got f**ked frames but mlv images are brighter and less noisy than raw_rec. Must be because of the metadata.
Yep, it must be ACR interraction with the dng... does the camera model show up? Apparently a log of ACR stuff comes from that. Setting the camera model via command line looks better and better.
I'm using buffer method 4 on MLV usually. I tested it mainly with 7D, there are more resolutions /modes to try.
I hardcoded the model name for now and I'm hoping Chmee adds it to his raw2cdng. Model name seems to be vital for ACR.
Incidentally, just been comparing DNGs converted with raw2dng (14bit) and Chmee's CDNG converter (12bit) in Resolve 10. It debayers the 12bit files much better.
I've noticed a little speed increase in mlv recording after testing but still useless atm because of the random crap frames.
I got my first serious bug on MLraw, the camera could not get into liveview with raw enabled or would crash within seconds with fps override going all over the place, or error messages saying card full even if the format menu said 25gb left. I had to take of the battery at each crash. Then I disabled modules loading and managed to record H264, but as you know quality sucks, and it's very hard to match to raw files. I'm using two komputarbay 32gb without issues since august. I will try to reinstall ML on this card and report results...
I think I've solved the corrupt frames problem with mlv_rec (50D). Shot 50+ takes and not detected any bad frames 8)
@1% see my pull request in the main ML repo and try it. Might work for 7D too!?
Worth a shot, it might be from task priority. 5DII/50D/7D are pretty much the same cam generation.
Shot more and still no bad frames. Just need Camera model fix and we're good to go I think. :)
Lol, finally.
@1% - Are the stubs for camera properties unique or can this https://bitbucket.org/andy600/tl50d/commits/919eb57564ff8036420cf1e941fe38c20696ecd9 (https://bitbucket.org/andy600/tl50d/commits/919eb57564ff8036420cf1e941fe38c20696ecd9) be added to the 50D stubs? Would fix cam model and unique model name.
I did a bit more testing with my new card (Lexar 32GB 1000x), and the October 11 build. In crop mode, I can reliably go up to 1920x1080x24p resolutions in 16:9 ratio (83.0 MB/s; no dropped frames) and 2000x910x24p in 2.2:1 ratio. At even higher res, 2000x1080x24p, I get ~1000 frames before a frame drop. I have to turn Global draw off and enable Hacks to make this work. I am happy about this results.
But many points are not clear to me. I don't see crop marks when doing 16:9 cropped video - is it possible to enable them? I think I got it - it needs to be enabled.
I tried the turning Digital dolly on, but it didn't do anything for me in crop mode (I pushed the joystick around) - neither before nor during recording. Is it supposed to be functional?
I was recording first in C1 mode, but then switched to Av to have DoF control. It looks like in Av mode I can't do any changes to aperture or shutter speed during the recording - is it normal? I am looking wright now at the 1920x1080 crop video, and it looks very noisy - does it mean that ML boosted ISO a lot? How to make sure I use only low ISO? (I am using "optimize for low light" RAW video setting.)
Thanks!
Unique... I never added them? Guess I'll have to go through and find them for everything since MLV is starting to be viable.
QuoteI was recording first in C1 mode, but then switched to Av to have DoF control. It looks like in Av mode I can't do any changes to aperture or shutter speed during the recording - is it normal?
I added that yesterday, expect a speed drop but at least you can adjust expo. Advanced -> freeze exposure
QuoteI don't see crop marks when doing 16:9 cropped video - is it possible to enable them?
When the black crop marks were added they started using GD to draw, guess what happened. Everyone is too 5DIII centric or don't know you get like 10%+ speed increase when GD shuts off.
Quote from: 1% on November 10, 2013, 09:31:09 PM
Unique... I never added them? Guess I'll have to go through and find them for everything since MLV is starting to be viable.
I can't see the in the stubs.
I'll wait a bit before compiling a new download if we can get Cam model working for mlv.
Yup, will have to work on it tonite, I have a bunch stuff to do.. flying out to FL on tuesday. I'll have EOSM/7D/6D (think that's all I can fit)
Actually... done, it was quick. Does it show name now?
Quote from: 1% on November 10, 2013, 09:35:39 PM
Does it show name now?
mlv_rec allocates 85 frames then crashes with those stubs added. Removed them and it's ok again. :-\
Tried undoing your last couple of commits to see if they have anything to do with it but no, it's definitely the stubs.
delete
Yea, oops, see latest. At least if they aren't present on 5DII someone can grab em now :)
(http://i.imgbox.com/accY3kdF.jpg)
Model number is working :D
heh, I tested and I can't get 2000x1080 or 1920x1080.. the speed is still jumpy.
I deleted configs, reformatted etc. Speed is holding up (buffer method 3) and DNGs playing nice with ACR :)
Needs the rec display thing added because it's still old style buffer bar etc.
I'm liking this :D
Yea, I went back to 3 as well... maybe need to clean the card up, I just popped the new one on and started recording. 7D is holding up tho.
Just checked the latest nightly with supposedly mlv_rec. Alas, module does not show up once camera boots. Also, ML still doesn't have the raw capabilities that Andy600's TL build has on my 50D
Sorry if this is a boring question, but are the latest features (AETTR seems missing in TL) coming over to TL as they happen? What are the enhancements that allow such high raw speeds on 50d with TL, and will they ever be pulled back into ML?
Thanks for all the effort to all those who contributed.
The nightly + my builds should have raw_rec + ettr. Nightly doesn't have newer edmac channels (the old ones still gave ~80MB/s) and maybe some raw_rec/mlv_rec features
Raw_rec is in the nightlies and aettr. I don't see mlv_rec in the nightlies, even though it's in the changelog.
I don't know what the edmac channels are, but I get ~75MB/s in Andy600's 50D build, but only ~64MB/s in the latest nightly.
No big deal, happy with what I've got, but looking forward to having aettr with dual_iso support + the speed I'm getting now. Right now, it's one or the other.
Playing with mvl_rec would be a bonus. I'll wait patiently.
Heh, well andy's builds should have all of those... no video DUAL for 50D/7D/5DII they only use one register period.
Hehe, so not to bypass MLV any but:
http://u88.n24.queensu.ca/exiftool/forum/index.php/topic,2750.0.html
download exif tool gui.. look at cr2, save camera model.. .ie "Canon EOS 7D" or 50D, etc. Select all DNGs... watch it added in about 20 seconds.
Also don't forget uniquecameramodel... its the same as camera model
I'm still testing mlv_rec (all resolutions, speeds etc) and mlv_play but will upload a new alpha build later with everything (that is stable) included.
@1% - that looks useful for legacy dng files. I guess we now have an option for pre-filled meta but slightly slower recording (mlv_rec) or faster original raw plus a little exif trickery before post (raw_rec). Nice to have choices ;D
Yea, I dunno whats up with it on 50D... its like 60/70/80/83, 30 and then predicts 2k frames but stops at 1/2. I've diffed it and I've only taken out the 2nd writing thread so it is like it is. On 7D its slightly less jumpy but I got a random stop in 1x in between recording 2 videos where it showed continuous. Haven't tried method 3 yet on 7D so probably it will be almost the same as raw_rec there unless you're recording crop. 50D you can use it if meta data > extra res.
Ok cool, well thanks for the FB. Ain't life a bitch. My damn 550D does dual iso raw video, but only at postage stamp sizes. Sounds like a final answer you gave on the 50D, but then again, I've heard final answers before around here :)
Its pretty final, 7D has *some* tiny hope but I've tried setting the reg on 50D manually and nothing happened.
Ah well, seems fair really. Shooting raw on a £250 camera is already a little unfair. Now, if I sold ALL my gear, plus my road bike and my guitar, could I afford a 5d III? ...hmmm
Austerity sucks.
Ok, I've uploaded a new alpha build of Tragic Lantern for the 50D.
IMPORTANT DISCLAIMER: Please remember this is an alpha build of a fork of Magic Lantern SPECIFICALLY FOR THE 50D and is NOT directly supported by other devs. The plan is to eventually add thoroughly tested and permissible code from Tragic Lantern to the Unified build but as it stands it is purely for testers who want a little bit extra and who understand the added risks. Please do not hassle other ML devs if you experience any problems with this or any other build I upload. Post your findings/problems/bugs in this thread only!
This build includes:-
Tested and working mlv_rec module. The corrupt frame issue seems resolved so now you can experiment with recording mlv raw video which has embedded exif/metadata. This should make using mlv recorded DNGs play better with ACR and allow the use of correct DCP (Digital Camera Profiles) in your editing app.
Use the mlv_rec module in the same way as the raw_rec module but do not have both modules loaded simultaneously or you'll be in a world of pain.
mlv_rec has slightly different configuration settings than raw_rec and does not yet have the nice selectable buffer gui of raw_rec. You also have a choice of buffer methods in this still 'experimental' module. I have found methods 3 & 4 work best.
To convert mlv raw files you need to use mlv_dump (A command line only tool included in the zip) or you can use mlv2dng to drag and drop convert, however, the latter app seems to no longer be supported. You can also playback on your desktop (PC) using g3gg0's mlv player.
For more info on how to convert and playback mlv files please refer to the following threads:
http://www.magiclantern.fm/forum/index.php?topic=7122.0 (http://www.magiclantern.fm/forum/index.php?topic=7122.0) - g3gg0's thread with info and instructions for converting and playing mlv files
http://www.magiclantern.fm/forum/index.php?topic=7802.0 (http://www.magiclantern.fm/forum/index.php?topic=7802.0) mlv2dng.exe - old thread
MLV Play module
The MLV player module (integrated as part of the file manager module - both mlv_play and file_man modules must be loaded!) has been supercharged. You can now play back any raw or mlv file in color, though not in realtime. There is a transport bar accessible with your Picture Style button (under the LCD). You can also now playback a raw or mlv file immediately after recording by pressing the play button (also under the LCD). When play is activated you can skip through your raw files using the top wheel. It will build indexes for mlv raw files before playing but this is very fast.
As usual, there are various other little tweaks and fixes but you may have noticed correct shutter readout is broken. I'm not sure if/when this will be fixed.
Download the latest alpha build (including the latest raw2dng.exe and mlv_dump.exe desktop converters) here: https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Nov11_mlv_rec_and_player.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Nov11_mlv_rec_and_player.zip) 50D ONLY
UPDATE: mlv_rec may still have issues. I've recorded a lot of footage without a problem but I also had a 3gb file that would not dump to dng with mvl_dump and would also crash the player. It did however convert to legacy raw but there seems to be an issue with the headers/footers as debayering is not correct. Needs investigating further so I recommend only using mlv_rec for experimenting ATM
Wow, awesome, thanks Andy600. I won't have time to play with this now for a couple of days, but will be sure to give some feedback.
Great work, thanks! I'll be one of alpha testers for this MLV stuff.
A question: does each frame include things like aperture stop and focal length? This is critical, as that's what lens correction module of ACR needs to get read of those annoying aberrations, distortions and vignetting. (Also, having the lens model would be very helpful; but if not, one could always add it later with exiftools.)
I am trying to come up with a "photographer-friendly" workflow for 50D RAW video PP. Specifically, I want it to be built around Adobe Camera Raw (packaged with PS). It actually works very well, except for one deficiency: my version of ACR (6.x) doesn't provide the upscaling option to get from uncropped video to 1920x1080. (It does provide a few sizes, but no way to customize that - weird!). If not for that, one could have a complete solution in ACR - it'd do all the grading, lens and perspective corrections, then upscale to 1080p and sharpen the frames. No such luck - the last two steps (upscaling and sharpening) would have to be done elsewhere.
Virtualdub is probably the only video tool I know well (have been using it for ages), so I was trying to use it yesterday to supplement ACR. So the workflow is:
- Convert RAW to DNGs
- Load DNGs into ACR, do the corrections, but set the sharpening to 0 - I think this is important, as any sharpening (even the default one) has to be reserved until the end, after upscaling - am I right here?
- Save the frames in ACR as JPEGs - this seems to be the only way to directly bring them to Virtualdub (it doesn't know TIFFs).
- Open the JPEGs in Virtualdub, load two third party filters - Smart resize (I use exact bicubic resize to 1920x1080) and MSU Smart sharpen (I am debating between "Small overall" and "Overall" levels of sharpening), and then save this as an AVI video with the codec of your choice (I use Xvid for now)
At the end, I do see moire/aliasing artifacts, but they seem to be no worse than in the original size video. No flickering AFAIKT. And apparently no new artifacts due to upscaling - e.g. a high contrast diagonal line doesn't appear jagged. I think that's very crucial.
Does this look reasonable?
Quote from: pulsar124 on November 11, 2013, 01:06:07 PM
Great work, thanks! I'll be one of alpha testers for this MLV stuff.
A question: does each frame include things like aperture stop and focal length? This is critical, as that's what lens correction module of ACR needs to get read of those annoying aberrations, distortions and vignetting. (Also, having the lens model would be very helpful; but if not, one could always add it later with exiftools.)
I am trying to come up with a "photographer-friendly" workflow for 50D RAW video PP. Specifically, I want it to be built around Adobe Camera Raw (packaged with PS). It actually works very well, except for one deficiency: my version of ACR (6.x) doesn't provide the upscaling option to get from uncropped video to 1920x1080. (It does provide a few sizes, but no way to customize that - weird!). If not for that, one could have a complete solution in ACR - it'd do all the grading, lens and perspective corrections, then upscale to 1080p and sharpen the frames. No such luck - the last two steps (upscaling and sharpening) would have to be done elsewhere.
Virtualdub is probably the only video tool I know well (have been using it for ages), so I was trying to use it yesterday to supplement ACR. So the workflow is:
- Convert RAW to DNGs
- Load DNGs into ACR, do the corrections, but set the sharpening to 0 - I think this is important, as any sharpening (even the default one) has to be reserved until the end, after upscaling - am I right here?
- Save the frames in ACR as JPEGs - this seems to be the only way to directly bring them to Virtualdub (it doesn't know TIFFs).
- Open the JPEGs in Virtualdub, load two third party filters - Smart resize (I use exact bicubic resize to 1920x1080) and MSU Smart sharpen (I am debating between "Small overall" and "Overall" levels of sharpening), and then save this as an AVI video with the codec of your choice (I use Xvid for now)
At the end, I do see moire/aliasing artifacts, but they seem to be no worse than in the original size video. No flickering AFAIKT. And apparently no new artifacts due to upscaling - e.g. a high contrast diagonal line doesn't appear jagged. I think that's very crucial.
Does this look reasonable?
You'd be better off exporting PNGs than Jpegs. VirtualDub will use those too, and obviously it's lossless compression vs lossy for Jpegs.
Quote from: jamesd256 on November 11, 2013, 02:38:23 PM
You'd be better off exporting PNGs than Jpegs. VirtualDub will use those too, and obviously it's lossless compression vs lossy for Jpegs.
It won't work - ACR can only export TIFF, JPEG, DNG, and PSD. I am using maximum jpeg quality (essentially uncompressed), and I don't see any difference in the video when compared to the one made from PNGs. (I did test another workflow, where I did ACR->TIFF->ImageMagick tools (upscaling + unsharp mask)->PNG->Virtualdub, but it involved more steps, and the ImageMagick step was very slow.)
OK, didn't know that about ACR as I've never used it. Sounds to me like you've optimised your workflow.
I use Aftershot pro for raw conversion, but sadly it won't open the DNGs produced by the tools I've tried.
I did get a satisfactory workflow using raw2dng -> DNG -> ufraw-batch -> PNG -> virtualdub -> Cineform 10bit -> Vegas 12 for edit and grade. What was nice about that was that the denoising in Ufraw was good, but it was slow, and I obviously had to grade on 10bit footage rather than raw.
I have now settled on a workflow based on raw2cdng -> Davinci Resolve -> proxies and round tripping with Vegas (grading after editing for a more joined up approach).
Have you considered Resolve?
I started testing the new release from Andy600. Everything seems to be working better mlv-wise. MLV viewer in the camera works 50% of the time. Sometimes it just gives an error and freezes the camera, so I have to remove the battery. My bigger issue though- I cannot open the mlv file on my PC. I can view it in MLV viewer, but MLV2DNG doesn't work (not recognized header "STYL"), and MLVdump doesn't do anything.
How do I get dngs?
Tried MLV_dump with different parameters, it stops working/gives one frame, generally speaking- my file is useless now :(
Great work on this! MLVViewSharp.exe will work on Mac/Linux through mono. MLV2DNG/MLVdump do not sadly, but still nice to quickly see focus in the field if you have a macbook. Message if you need a hand setting this up.
MLV works in continuos at full frame. At cropped, I get crazy jumping write speeds. Sometimes drops from low 80s to 50s to 40s in just a second. Compared to raw_rec on the same build, MLV is jumping all over the place. When in RAW, I get a few mbs/sec jumps, not the 30mb/s jumps in MLV.
Formatted my card in camera, removing ML, and reinstalled to the card from scratch. Cleared out everything, and using all speed squeezing techniques, but I can't get it to stabilize. Tried a few of the buffer settings in MLV, found 4 (or maybe 3) might be best for me. Any tips?
In the meantime, RAW recording is stable at 1920x1080 for me hanging around a nice looking 82mb/s on this build. Can't wait to see MLV become my daily driver. With all that metadata at the bottom of MLV Viewer, I'm pretty excited!
Quote from: Mkolaj on November 11, 2013, 03:59:30 PM
I started testing the new release from Andy600. Everything seems to be working better mlv-wise. MLV viewer in the camera works 50% of the time. Sometimes it just gives an error and freezes the camera, so I have to remove the battery. My bigger issue though- I cannot open the mlv file on my PC. I can view it in MLV viewer, but MLV2DNG doesn't work (not recognized header "STYL"), and MLVdump doesn't do anything.
How do I get dngs?
Tried MLV_dump with different parameters, it stops working/gives one frame, generally speaking- my file is useless now :(
It's not 'useless'!
I'm having a similar problem with a large mlv file but can still dump to the legacy format using something like this:
mlv_dump -r -o M11-0920.RAW M11-0920.MLV
Yea, you have to give it more parameters than raw2dng.. there is also mlv2dng somewhere here.
Its spanning for me fine, I'm trying the compression out to see what it does.
re: mlv_rec - see update at the bottom of this post http://www.magiclantern.fm/forum/index.php?topic=5586.msg87952#msg87952 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg87952#msg87952)
Problems :-[
Was it crop mode? That seems to be where the main issues are at.
Yea, crashes for me dumping to dng for some reason.. maybe some of the changed functions? I'd have to try a pre-built one from g3ggo to see.
Wonder how much meta data you need to have raw = mlv, I know the 2 cam models are necessary but wonder about ISO too, etc.
Yes crop video. It was 2000x910 (2.35:1). I shot a lot at different resolutions/ratios without issue but that one was screwed up for some reason.
Previously, bar the corrupt frames, I never had any problem with conversion. Maybe the base_prio can be tweaked further? 0x05 was too much so maybe 0x1C is too little? I'm crap with hex :D
re: metadata - WB is needed, ISO I think is important and might be needed if apps like Resolve officially support the format in the future, lens info is useful (though not for me because I only have vintage manual lenses).
I thought of that too, how far can it be pushed... was the 2000x1080 continuous when the base was high?
My conversion to dng gpf'd mlv_dump, mlv2dng still worked though. Also some mlv_dump frames came out all black.
Didn't get continuous at max 2000px res but did at 1080p although I rarely leave it recording for more than 1-2 mins and did have the odd stop. Might be the card though.
I think my problem might not be with mlv_rec but with mlv_dump on Win7 64bit. It won't dump any file :-\
There's an mlv converter for Mac OSX. See jphansen's post below. I have not tried it yet, so don't know if it works . . .
Quote from: jphansen on September 04, 2013, 11:20:41 PM
This is for 10.8.3 Mountain Lion users.. I guess you can install the Lion version the same way... gcc-mlion.tar.gz - Mountain Lion. gcc-lion.tar.gz - Lion version
Found a solution to get the mac versions to work (the absolutely non geeky/I dont know Unix way)... The problem is the "libstdc++.6.dylib". And WTF is that anyway.. My answer I DOOONT know.. Anyway.. I found the missing libraries to install.. Here is what you need to do:
Go to http://hpc.sourceforge.net (http://hpc.sourceforge.net) and download this file http://prdownloads.sourceforge.net/hpc/gcc-mlion.tar.gz?download (http://prdownloads.sourceforge.net/hpc/gcc-mlion.tar.gz?download).
Go to Terminal and cd to the download folder cd /Users/UserName/Downloads/ Then gunzip gcc-lion.tar.gz (if your browser didn't do so already) and then sudo tar -xvf gcc-mlion.tar -C /
I used 7zX because I dont know how to gunzip..
Restart your mac and BOOOOM!!! MLVConverter.app works for me...
Hope this helps some..
Quotemlv_dump on Win7 64bit. It won't dump any file
Ok, then its not just me.
Quote from: 1% on November 12, 2013, 09:42:00 AM
Ok, then its not just me.
Very odd. Tried again this morning and mlv_dump is working on new and older .mlv files. Might have been Windows causing the problem but as it doesn't do anything registry related I can't figure out why it's working/not working.
Used this:
mlv_dump --dng M12-1309.MLV
Following my promo post a while back...here it is if anyone's interested, vast majority shot 50D raw:
Hey guys!
I'm shooting a webseries on my Canon 50D with RAW_REC. Everything was going great, but after a day's recording, I had corrupt frames on some of my videos.
Is there a way to fix it on post? I mean not all frames were corrupted but only 1 frame every 10 or 15 seconds of video. I got no errors on screen while recording.
I was wondering if I could cut off the corrupt DNGs and use an After Effects FX to blend one good frame into the next is that possible? Filling the hole?
I also thought about duplicating the 1st previous good frame and replacing the bad one, but that would make the video stutter a bit. If there is no other resolution, I guess I'll have to settle for that :(
I really don't know what went wrong.
I used Tragic_Lantern_50D109-Andy600.Build.2013Sep08 on a Lexar 32GB 1000x, a Sandisk 16 GB 60mb/s and a Transcend 16GB 1000X on a Canon 50D with an Lilliput external monitor.
Resolution was 1584x892, 16:9, FPS Override 23.976, Exact FPS. GD Off.
Workflow was joining files with FSplitter, Extracting RAWs with RAWBatchelor 3.0, Importing in AE CC, correcting color on ACR and exporting to DxHD 10 bit to edit in Premiere CC.
The cards are still working, so it's not a defective card issue.
Please help me, if you can.
Thank you all,
I see Blackmagic released Raw on the BMPCC. Former 50D alumni DL Watson posted this Prores/Raw comparison on Vimeo.
He said he'll do a moire comparison between the BMPCC and 50D. I'd be interested in seeing how they compare as the BMPCC is showing a bit of moire in Raw mode.
Nice image though.
I think I am converging to use 30p for my attempts at footage stocks with 50D. It looks like stocks prefer 30p over 24p, and they strongly prefer 16:9 full HD. I checked yesterday, and Oct. 11 TL has no problem recording uncropped video at 16:9 and 30p to my Lexar 32GB 1000x. I upgraded my ACR to the newest one (8.2), and now it does have the arbitrary resizing option at the end - meaning I can do almost everything now inside ACR (with resizing and final sharpening). (Still it doesn't output PNG, so I have to rely on JPEGs to deliver frames from ACR to Virtualdub). The workflow now is
DNGs->ACR->JPEGs->Virtualdub->video
The only filter I need in Virtualdub is Crop: upscaled uncropped frames in ACR have the size 1920x1081, so I tell Virtualdub to shave off that one extra row of pixels.
My research also shows that footage stocks frowns upon color grading (it should be left for the buyer to do that, to match their whole sequence of clips), which simplifies life. I just plan to use ACR to fit the dynamic range into 8 bits (lift shadows, recover highlights etc), correct WB, and perhaps increase saturation (especially for landscape and abstract videos).
I'm going to continue working with the EOS-M which I accept will probably always be in Alpha.
I have lots of other stills cameras, so I no longer feel it makes sense to keep the 50D just for RAW video. Without any time-line for a production version of ML on the 50D I'd rather put the money into a BMPCC. I'm not saying this to discourage anyone from getting a 50D and using it for ML. If I was young and this was my only camera I'd be quite happy. Also, there are features that ML offers that the BM cameras do not. However, I feel I should point out to anyone following this stuff what my final conclusion, for me, has been. I just can't trust, when I take this camera out, that something won't happen as I expect it. Last night I took it to shoot an event and though the RAW video recording worked fine, it didn't record a bunch of photos I took. I'm sure there's a good reason. But I'm tired of searching through threads trying to figure stuff out.
Has been a fantastic learning experience! Definitely whet my appetite for a 5D3! running ML :)
Here's the camera if anyone is in the Boston area and wants it.
http://boston.craigslist.org/gbs/pho/4189491469.html
Quote from: rockfallfilms on November 13, 2013, 01:24:38 PM
I see Blackmagic released Raw on the BMPCC. Former 50D alumni DL Watson posted this Prores/Raw comparison on Vimeo.
He said he'll do a moire comparison between the BMPCC and 50D. I'd be interested in seeing how they compare as the BMPCC is showing a bit of moire in Raw mode.
Nice image though.
Looks like a lot of moire in the grills of at least two cars! Wow! Am I wrong?
Quote from: lionelp on November 13, 2013, 08:07:25 PM
Looks like a lot of moire in the grills of at least two cars! Wow! Am I wrong?
Yeah I was surprised to see that much, I thought the bmpcc was supposed to be moiré free as there's no down sampling.
It seems that each camera has its downsides.
Quote from: rockfallfilms on November 13, 2013, 08:12:34 PM
Yeah I was surprised to see that much, I thought the bmpcc was supposed to be moiré free as there's no down sampling.
It seems that each camera has its downsides.
Absolutely agree. I mean it is a great thing that BM is doing. Same for ML!!!.
No camera (that doesn't cost a small fortune) will not have its issues. All cameras will have issues if they don't cost mega money. :)
Just want to point out that moire is a naturally occurring phenomenon and all cameras, in the right circumstances, will show it.
Quote from: maxotics on November 13, 2013, 09:19:10 PM
Just want to point out that moire is a naturally occurring phenomenon and all cameras, in the right circumstances, will show it.
True. Got some crop 50D footage with a touch of moire. It also helps to remember that different debayering methods can help a lot. I flit between ACR and Raw Therapee using AMaZE and DCB. You can never completely rid a shot of it but there are methods/tricks to concealing it. Aliasing is a bigger headache and you have to be very careful what you shoot.
Quote from: Andy600 on November 13, 2013, 09:49:30 PM
True. Got some crop 50D footage with a touch of moire. It also helps to remember that different debayering methods can help a lot. I flit between ACR and Raw Therapee using AMaZE and DCB. You can never completely rid a shot of it but there are methods/tricks to concealing it. Aliasing is a bigger headache and you have to be very careful what you shoot.
Absolutely, on the de-bayering. Have you tried Davinci yet Andy? I suspect it has debayering that it tuned to video. I think I'm going to run DNGs through Davinci in the future to DxHD and just edit from there. I just wish I had more brain cells for that Resolve app. I ran out a few years ago :)
Quote from: maxotics on November 13, 2013, 10:27:46 PM
Absolutely, on the de-bayering. Have you tried Davinci yet Andy? I suspect it has debayering that it tuned to video. I think I'm going to run DNGs through Davinci in the future to DxHD and just edit from there. I just wish I had more brain cells for that Resolve app. I ran out a few years ago :)
Yes. I use Resolve quite a lot but it's debayering of 14bit DNG files is atrocious. Converting to CDNG 12bit seems better but I haven't done a conclusive test.
My current workflow is raw or mlv -> ACR (unless the shot is riddled with moire, in which case I jump into Raw Therapee and play around with debayering options) -> output to scaled 16bit TIFFs then into Premier Pro to edit -> then into Resolve or AE for CC depending on what I want to do (both have advantages and disadvantages). If I need more latitude/highlight recovery I go back to the original DNGs and play more in ACR/Raw Therapee and redump the TIFFs. I seriously don't rate Resolve's debayering algos for ML raw video. It probably sings with BMCC, Red or Alexa footage though.
Interestingly I'm looking at the metadata from a ML raw (MLV) file vs data from a BMPCC DNG. Some differences there regarding CFA pattern etc. I don't pretend to understand the half of it but my guess is that ML raw footage will need metadata similar to BMPCC for debayering to work well in Resolve.
Thanks Andy. I tried RAW Therapee but couldn't figure out a workflow where opening the folder of DNGs didn't slow it to a crawl. Also, the batch processing I never got to work well. Maybe I was just tired. I looked, but couldn't find a good tutorial/info for processing ML dngs in Raw Therapee. Do you know of one? I agree, the image manipulation choices are awesome! I'd actually rather write batch script to RAW Therapee than use Resolve manually!
Quote from: maxotics on November 13, 2013, 10:57:20 PM
Thanks Andy. I tried RAW Therapee but couldn't figure out a workflow where opening the folder of DNGs didn't slow it to a crawl. Also, the batch processing I never got to work well. Maybe I was just tired. I looked, but couldn't find a good tutorial/info for processing ML dngs in Raw Therapee. Do you know of one? I agree, the image manipulation choices are awesome! I'd actually rather write batch script to RAW Therapee than use Resolve manually!
I don't know any, sorry. I just jumped in and messed around for a few hours. As with ACR it's best to only use functions that you don't have in yor NLE or it will a) increase conversion time and b) may introduce flicker. Never use auto WB or auto anything for that matter. If you can't manually get a good WB in your NLE scopes you can Auto WB one shot in RawTherapee then take a note of the settings, then reset and enter the settings manually. When you have the settings you need you can either save a preset (I always do) or hit the copy to clipboard icon. Then go back to the file browser and select all the dngs you want to apply the settings to, right+click and you'll see a 'process' menu in the context menu, then just apply and wait untill all DNGs change to look corrected. Then 'select all' again and move them to the queue. Set your output prefs (tiff/jepg etc), choose a destination and hit start. It does take a while though.
I'm on PC and I had a lot of hassle with Raw Therapee recently after updating it. It doesn't seem to like certain directory structures and profiles made in older versions so I stick to v4.0.11.32.
Always start with the default profile and set exposure to neutral (hit the neutral button). Then play with exposure setting manually. For moire fixing I find the worst frame(s) and then in the raw tab (checkerbox icon) I choose AMaZE, set to about 3-4. It's also worth playing with DCB. The other algos are not that good. I always do this for non-crop ML raw DNGs but I tend to leave AMaZE set to 0 for crop footage as it can cause artifacts.
You can also use DCP files from ACR in Raw Therapee. I have free VisionLog working there. Just remember to set it to use the DCP's luma curve.
TBH It's all a big pain in the ass :D but that's raw for you!
If you're ok working with log I can probably set up a couple of basic profiles for Raw Therapee (one for crop and the other for non-crop). That will mean you only need to play with exposure, WB and sizing. I can set CR and fringing reduction etc to on. Obviously I've tuned it to my lenses but would be a starting point if you want to try it?
My problem was just opening a folder of DNGs. I couldn't stop it from trying to create thumbnails of them all, which took forever. Is that the problem you had with the new version? Okay, I have 4.0.11.32...hmmm. I have a decent i7 PC. I have it set to open the smallest thumbnail, though I wish it wouldn't open any.
Quote from: maxotics on November 14, 2013, 12:00:23 AM
My problem was just opening a folder of DNGs. I couldn't stop it from trying to create thumbnails of them all, which took forever. Is that the problem you had with the new version? Okay, I have 4.0.11.32...hmmm. I have a decent i7 PC. I have it set to open the smallest thumbnail, though I wish it wouldn't open any.
Yes, it take ages and caches thumbnails for everything :-\ I only use it when I have moire issues.
BTW, you can make your changes to your ML raw DNGs in ACR then export as DNGs then IF you need AMaZE/DCB etc you can import an ACR-tweaked DNG, set exposure settings to default and just play with the debayering algos then export to 16bit TIFF (wish there was video export in RT though) ;)
Quote from: Andy600 on November 14, 2013, 12:26:11 AM
BTW, you can make your changes to your ML raw DNGs in ACR then export as DNGs then IF you need AMaZE/DCB etc you can import an ACR-tweaked DNG, set exposure settings to default and just play with the debayering algos then export to 16bit TIFF (wish there was video export in RT though) ;)
Hope I don't sound dumb, but I'm confused on the ACR. You mean Adobe Camera Raw, right? And if so, why would you run DNGs through it again, isn't that what raw2dng is for? What do you mean "ACR-tweaked."
I generally used raw2dng, then if I want tiffs, UFRAW with options.
Quote from: maxotics on November 14, 2013, 12:00:23 AM
My problem was just opening a folder of DNGs. I couldn't stop it from trying to create thumbnails of them all, which took forever. Is that the problem you had with the new version? Okay, I have 4.0.11.32...hmmm. I have a decent i7 PC. I have it set to open the smallest thumbnail, though I wish it wouldn't open any.
It works fast for me making all the thumbnails. and they are maybe around 2 1/2" in size. The end part works quite slow in the queue. I can also change directories and it quickly makes new thumbnails. The programs tends to hang quite a bit though, like in the queue processing time. I have version 4.0.11.32 and I also have the fastest i7 3770k system I built running 3.9 ghz stock speed that i sometimes overclock using a huge heatsink/fan giving me 4.5 ghz. I don't use Raw Therapee a lot, though. It's not the speed in workflow I want to use.
Quote from: maxotics on November 14, 2013, 12:52:42 AM
Hope I don't sound dumb, but I'm confused on the ACR. You mean Adobe Camera Raw, right? And if so, why would you run DNGs through it again, isn't that what raw2dng is for? What do you mean "ACR-tweaked."
I generally used raw2dng, then if I want tiffs, UFRAW with options.
ACR is an equivalent of UFRAW. It can output processed RAW files as JPEG, TIFF (8/16 bit), and as DNG.
QuoteI used Tragic_Lantern_50D109-Andy600.Build.2013Sep08 on a Lexar 32GB 1000x, a Sandisk 16 GB 60mb/s and a Transcend 16GB 1000X on a Canon 50D with an Lilliput external monitor.
Resolution was 1584x892, 16:9, FPS Override 23.976, Exact FPS. GD Off.
Workflow was joining files with FSplitter, Extracting RAWs with RAWBatchelor 3.0, Importing in AE CC, correcting color on ACR and exporting to DxHD 10 bit to edit in Premiere CC.
Did you turn off the dialog timers... every 15 frames sounds like it only slowed them down ... ie from small hacks. Once its broken you can only try to interpolate the frames in twixtor or AE. :(
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Quote from: D.L. Watson on November 14, 2013, 08:22:49 AM
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Buy a Metabones Speed Booster (http://www.metabones.com/buy-speed-booster) to get that Super 16 to Super 35 and gain 1 stop of light! :)
Also, it is very apparent that you didn't ETTR equally. It seems you sacrificed a lot more highlights on the BMPCC to gain better shadow performance or does the BMPCC simply preserve highlights. Try making the same comparison with highlights instead of shadows.
Quote from: PressureFM on November 14, 2013, 09:20:10 AM
Buy a Metabones Speed Booster (http://www.metabones.com/buy-speed-booster) to get that Super 16 to Super 35 and gain 1 stop of light! :)
Also, it is very apparent that you didn't ETTR equally. It seems you sacrificed a lot more highlights on the BMPCC to gain better shadow performance or does the BMPCC simply preserve highlights. Try making the same comparison with highlights instead of shadows.
Actually, I used Zebras to ETTR the same for both cameras. Because of the extra dynamic range, I was able to overexpose more on the BMPCC than the 50D. It wasn't perfect, but I tried to get Zebras telling me I was clipping the same amount of highlight data on each camera.
I plan on getting a Metabones Speedbooster, but I'm not sure how that would improve the dynamic range of the 50D.
Quote from: D.L. Watson on November 14, 2013, 08:22:49 AM
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Thanks for posting this DL. I'm quite surprised by the lack of shadow detail on the 50D. The BMPCC dynamic range definitely impressive, unfortunately you still can't buy it in the UK!
If you have time, could you do a moire test between both cameras on those car grilles?
Quote from: D.L. Watson on November 14, 2013, 10:03:47 AM
I plan on getting a Metabones Speedbooster, but I'm not sure how that would improve the dynamic range of the 50D.
I was talking specifically for the BMPCC, as it won't work on the 50D.
hey guys,
i've been using ml for some time now on a 550d, but i'm still a noob when it comes to nightly builds and raw recording on my brand new very old 50d.
i know this is probably the wrong place to ask stupid questions, but i am overwhelmed by a million of open tabs and i think i just need someone to point me to the best build...
i'm willing to take any risk necessary to record a raw sequence in at least full hd (crop), so far i tried the latest nightly build for the 50d as well as the latest official final release.
in both cases i didn't get to load the necessary modules.
i would be trying this one next:
"UPDATE: June 11th
@GregoryOfManhatten's latest build (70MB/s capable raw video) - note ETTR is not currently working in photo mode
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip"
any other suggestions? thank you!
Quote from: cyberhirsch on November 14, 2013, 04:10:22 PM
hey guys,
i've been using ml for some time now on a 550d, but i'm still a noob when it comes to nightly builds and raw recording on my brand new very old 50d.
i know this is probably the wrong place to ask stupid questions, but i am overwhelmed by a million of open tabs and i think i just need someone to point me to the best build...
i'm willing to take any risk necessary to record a raw sequence in at least full hd (crop), so far i tried the latest nightly build for the 50d as well as the latest official final release.
in both cases i didn't get to load the necessary modules.
i would be trying this one next:
"UPDATE: June 11th
@GregoryOfManhatten's latest build (70MB/s capable raw video) - note ETTR is not currently working in photo mode
https://bitbucket.org/GregoryOfManhattan/magic-lantern/downloads/09june13-50D-45e63064ec08-70MB.zip"
any other suggestions? thank you!
http://www.magiclantern.fm/forum/index.php?topic=5586.msg87952#msg87952 (http://www.magiclantern.fm/forum/index.php?topic=5586.msg87952#msg87952)
The first post hasn't been updated in some time. Best to check the last few pages of the thread for a post by Andy. He is supplying the builds.
thanks for pointing me to it!
i have it running now, but still can't select and load modules. i don't see the tab.
shouldn't there be a tab where i load the modules like raw_rec and mlv rec?
what am i missing?
Quote from: 1% on November 14, 2013, 03:42:10 AM
Did you turn off the dialog timers... every 15 frames sounds like it only slowed them down ... ie from small hacks. Once its broken you can only try to interpolate the frames in twixtor or AE. :(
Thanks for the tip, 1%! Ill definately try the interpolation!
About the dialog timers, I turned them off at first, but it seems like everytime I turn off camera or change card (which happens a lot) I need to turn it off again. Is that correct?
Isn't there an automated way of doing this? Small hacks was definately on all the time.
Sorry for noobin :)
Quote from: D.L. Watson on November 14, 2013, 08:22:49 AM
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Really cool video!
okay, i guess i made some progress, my mistake was looking for an M in the menu!
now i got the first mlv files... is there a way to copy them right off camera instead of going through a card reader?
unfortunately only a couple of frames, the write speed is not as expected, only between 50-60
my komputerbay cf should be fast enough, when benchmarking it is up to 84 write speed. what could be the cause of the low speed? is it the buffer mode?
thanks for your help and excuse my bad english!
-- deleted ---
Quote from: D.L. Watson on November 14, 2013, 08:22:49 AM
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Thanks for this, very interesting. It does kind of reveal what we already know, ie that the BMPCC has much more dynamic range. I look forward to other tests comparing its raw mode for detail, low light capabilities and moire (also noticed there was more moire on the car grill vs BMCCC compressed)
I also look forward to the real shoot out - 5dII with Dual ISO on vs the BMPCC
. It does kind of reveal what we already know, ie that the BMPCC has much more dynamic range. I look forward to other tests comparing its raw mode for detail, low light capabilities and moire (also noticed there was more moire on the car grill vs BMCCC compressed)
I also look forward to the real shoot out - 5dII with Dual ISO on vs the BMPCC
[/quote]
:) Agreed. Appreciate the test. Glad that you like the BMPCC, D.L. .It is definitely a game changing camera!
So from what I understand, the Digital Dolly feature doesn't work in the most recent build, right? It doesn't do anything for me. But even if it worked as intended (I guess by operating the joystick while shooting), I am not sure it'd be very useful - I can't see how one could use it to implement a slow, steady and smooth parallel shift of the window.
How about my original suggestion - would it be too hard to implement a pre-programmed Dolly - you specify the shift (pixels per frame; can be negative), the starting position of the window will be at the opposite end, and when you start shooting the window will start smoothly shifting towards the opposite end (when you reach the opposite end, it can just continue recording)? In simplest case, only one additional input parameter would be required - delta_x (pixels per frame). Ideally, the shift could be made in any or both directions, by using the second parameter, delta_y.
I think such a feature would be really useful - steady, adjustable and very smooth panning, with no jerks and camera shakes from using the joystick.
What do you think?
Hi guys... First of all, I have to pardon me because I am in a workflow that I need to deliver footage tomorow.
Worked on a 50D raw, and now I am with a difficulty that I cant find the tuturial to merge all the .rar files and turn them to a single .RAW file
Working on a PC Win7 64Bit
Please help me!
And again, sorry for my question but I am really in a bad situation!
Some people have experienced problems with RAW Therapee when adding large numbers of files to the queue for processing. On the RAW Therapee forum I read this workaround:
Create a temporary folder with no files in it.
Go into RAW Therapee and add your files to the queue.
Set the browser tab to be open on the empty folder you created.
Close RAW Therapee to refresh it, then open it again.
On the queue tab set your job to process.
Quickly switch to the browser tab which is open on the folder with no files.
For lots of files, RAW Therapee queue processing seems to work better with the queue in the background and the file browser in the foreground (and no thumbnail generation). If you are experiencing processing crashes, give this method a go.
Quote from: joaomoutinho on November 15, 2013, 11:19:49 PM
Hi guys... First of all, I have to pardon me because I am in a workflow that I need to deliver footage tomorow.
Worked on a 50D raw, and now I am with a difficulty that I cant find the tuturial to merge all the .rar files and turn them to a single .RAW file
Working on a PC Win7 64Bit
Please help me!
And again, sorry for my question but I am really in a bad situation!
Hey,
Current version of raw2cdng joins all the parts automatically and converts the bunch into RAW sequence.
Still if you want to do it the old way you can use the prog File Joiner & Splitter. You have to edit file extensions before you use it - the prog explains it.
how convert raw to cdng in LOG ?
Quote from: CITY-U1001 on November 16, 2013, 09:22:26 AM
how convert raw to cdng in LOG ?
These are RAW containers. Why would you need at this stage????
Quote from: D.L. Watson on November 14, 2013, 08:22:49 AM
I'll probably get some hate for posting this, but here it is anyway. A comparison between the 50D and the Blackmagic Pocket Cinema Camera RAW.
50D is still the incredible useful for it's price, but if you like the flexibility of the 5D Mark III RAW video but don't want to pay $3,000+, consider the Pocket Cam. Especially since it's now in stock.
Haha, peace, DL, no hate )))
Basically I did such test with 50D and BMCC, published here some weeks ago. Roughly the same results. No big deal. I estimated the difference in 1-1.5 stops.
These are two awesome tools and I guess a comparison between them would cause hate from some immature guys ;))
One note, though, that when comparing two bodies there must be some reservation about the lenses. I guess when you add to these 'cheap' -- in a respectful way -- bodies some decent 3-4 lenses, the $500 difference would vanish. So it is all about the lens preference and availability. Personally, I have 7 adorable Canon EF lenses, and 50D is a God-send to shoot raw video. Just MHO )
Yes, being able to use EF lenses is a big plus. Does anyone know of a way to see the what the 50D's recording in crop mode. It shoots in 3x but shows 5x on the screen. Good for focusing, of course. Am I missing something easy?
yeah, it seems you can only see the frame before and after you record, not while you are recording...
the other thing is, you don't seem to have manual control over shutter, iso and aperture, am i right?
After playing around with the 50d doing some tests, I decided to make something specific. This is my first attempt. CONTROL shows a day in the life of a man hired to generate chaos:
I did it in one night with an actor (the black and white images are h.264). Done with an old version on ML raw (july 16). Most of the shots with a 58mm Helios 44 in some very dark environments, so you'll se some grain here and there, very visible in 3x crop shots with loss of resolution due to the wide aperture (f2)
Later in front of the screen, the real fight began. Working with raw, specially in an old 2008 macbook is a hassle, but it's worth it. Son of a Batch to create DNGs and proxies, Premiere for the editing, After Effects for the negative development and color correction. The first attempt of color correction was made using the VisionColor profile for ACR recently created, but it lifted more grain than working with the original ACR process, so I applied it only on few shots (ACR recognized the dngs with the "Canikon" profile, not the specific 50d created for this camera)
Later the final touch with the Color Finesse color correction tool for After Effects. lots of options, specially grading the highlights and the shadows. Just amazing. Thanks again for the ML gurus ;D
great idea, recycling footage wisely!
Noise is not so much disturbing, I would have appreciated a better white balance, skin tone was too yellow/green, even for city night lights.
Didn't understand the Kate Upton shot but appreciated it ;)
Thanks Riccardo. The Kate Upton was there because the character is having fun, waiting for the demonstrations ends. It's like showing the character's indifference before the consequences of his job.
The greenish tone... recently i've seen several movies of a danish director, Nicholas Winding Refn, and loved his photography, nothing standard, he like to play with the limits of what you see, and that's my intention also. I wanted to create a disturbing atmosphere.
I have not had the same experience in crop ie iso, shutter, fps, aperture.
Sometimes liveview has been slow or choppy.
"=cyberhirsch link=topic=5586.msg88872#msg88872 date=1384625523]
yeah, it seems you can only see the frame before and after you record, not while you are recording...
the other thing is, you don't seem to have manual control over shutter, iso and aperture, am i right?
[/quote]
Quote from: lionelp on November 17, 2013, 02:54:49 PM
I have not had the same experience in crop ie iso, shutter, fps, aperture.
Sometimes liveview has been slow or choppy.
"=cyberhirsch link=topic=5586.msg88872#msg88872 date=1384625523]
yeah, it seems you can only see the frame before and after you record, not while you are recording...
the other thing is, you don't seem to have manual control over shutter, iso and aperture, am i right?
Hmmm ???, I have full control over ISO, FPS and aperture although there is a bug with the movie mode shutter (it shows photo mode shutter).
Live view choppy? It shouldn't be unless you're using the hack preview mode for crop recording which is has a lower lcd refresh rate
Could have been. It rarely has happened actually. Everything else; full control as you have stated.
:)
Quote from: Andy600 on November 17, 2013, 03:24:49 PM
Hmmm ???, I have full control over ISO, FPS and aperture although there is a bug with the movie mode shutter (it shows photo mode shutter).
Live view choppy? It shouldn't be unless you're using the hack preview mode for crop recording which is has a lower lcd refresh rate
ML froze during recording, saying one frame skipped... i had to remove the battery, after that my flash card is gone now, 50d and windows tell me it needs to be formated.
unfortunely they both can't do it. is the card lost?
Quote from: cyberhirsch on November 17, 2013, 04:18:40 PM
ML froze during recording, saying one frame skipped... i had to remove the battery, after that my flash card is gone now, 50d and windows tell me it needs to be formated.
unfortunely they both can't do it. is the card lost?
What card is it?
There are issues with UDMA7 cards becoming corrupt on USB2.0 readers.
Hello can someone help me figure out why in the x5 magnifier i get a gray screen but it's fine and in color when i go in x10 magnifier
please see the image on this link.
http://i.imgur.com/hQLclih.png
Quote from: leojames on November 17, 2013, 07:40:38 PM
Hello can someone help me figure out why in the x5 magnifier i get a gray screen but it's fine and in color when i go in x10 magnifier
please see the image on this link.
http://i.imgur.com/hQLclih.png
That's normal. You can select different preview modes in the raw module but it will use grayscale or the low res/fps hacked preview when recording. It's due to hardware/firmware limitations.
Quote from: Andy600 on November 17, 2013, 09:14:27 PM
That's normal. You can select different preview modes in the raw module but it will use grayscale or the low res/fps hacked preview when recording. It's due to hardware/firmware limitations.
Thanks that fixed it andy i went into the preview section and changed from auto to Canon now everything is works ;D
It was a komputerbay 1000x 32gb ... I really use a USB reader, but it was corrupted in camera. When I inserted the battery again, the 50d claimed the card was not formatted. Is it possible that the card was corrupted by ML?
The 50D needs the card formatted Fat32, won't work with exFat, etc.
i formatted the card with the 50d so i guess everything was fine, i was using it for a couple of days, even filled it completely one time. but suddenly the 50d froze and when i put the battery back in, it needed to be formatted again. so i tried to format it again, but it won't let me.
Quote from: simulacro on November 16, 2013, 09:14:02 PM
After playing around with the 50d doing some tests, I decided to make something specific. This is my first attempt. CONTROL shows a day in the life of a man hired to generate chaos:
I did it in one night with an actor (the black and white images are h.264). Done with an old version on ML raw (july 16). Most of the shots with a 58mm Helios 44 in some very dark environments, so you'll se some grain here and there, very visible in 3x crop shots with loss of resolution due to the wide aperture (f2)
Later in front of the screen, the real fight began. Working with raw, specially in an old 2008 macbook is a hassle, but it's worth it. Son of a Batch to create DNGs and proxies, Premiere for the editing, After Effects for the negative development and color correction. The first attempt of color correction was made using the VisionColor profile for ACR recently created, but it lifted more grain than working with the original ACR process, so I applied it only on few shots (ACR recognized the dngs with the "Canikon" profile, not the specific 50d created for this camera)
Later the final touch with the Color Finesse color correction tool for After Effects. lots of options, specially grading the highlights and the shadows. Just amazing. Thanks again for the ML gurus ;D
Nice work!!! Really enjoyed it.
Quote from: cyberhirsch on November 18, 2013, 04:00:04 AM
i formatted the card with the 50d so i guess everything was fine, i was using it for a couple of days, even filled it completely one time. but suddenly the 50d froze and when i put the battery back in, it needed to be formatted again. so i tried to format it again, but it won't let me.
Sounds like it's bust. You need to RMA it to Komputerbay. They are usually quite fast to replace broken cards.
Does anybody know where i can find a good tutorial about how to shoot and edit with the ML RAW 4:3 crop with a x2 anamorphic lens is there any benefit shooting in 4:3 ?
Quote from: leojames on November 19, 2013, 09:58:17 PM
Does anybody know where i can find a good tutorial about how to shoot and edit with the ML RAW 4:3 crop with a x2 anamorphic lens is there any benefit shooting in 4:3 ?
www.eoshd.com/comments/forum/5-anamorphic
There's a lot there.
Quote from: Andy600 on November 18, 2013, 06:14:50 PM
Sounds like it's bust. You need to RMA it to Komputerbay. They are usually quite fast to replace broken cards.
yeah, i did, got two new ones already, a 64gb and a 128... i just wonder what caused the trouble though... you think it might have been caused by ML by any chance? or was it maybe a bad card all along... although it worked fine for a week....
Those cards are factory seconds. Which means a testing machine found potential problems. When you buy the card, you put your time into testing them further in the interest of getting a good one. I don't know of many guaranteed "brand" cards failing. IF a card was going to die, then ML would be the thing you'd want to throw at it. You're writing as fast as the camera can, generating heat, etc, and putting all the memory cells through max read/writes. I just don't get it. To ask if ML is somehow busting something that is a factory second? Yes, it was a bad card along, as all of them have the potential to be discovered as such.
Quote from: maxotics on November 20, 2013, 03:33:36 AM
Those cards are factory seconds. Which means a testing machine found potential problems. When you buy the card, you put your time into testing them further in the interest of getting a good one. I don't know of many guaranteed "brand" cards failing. IF a card was going to die, then ML would be the thing you'd want to throw at it. You're writing as fast as the camera can, generating heat, etc, and putting all the memory cells through max read/writes. I just don't get it. To ask if ML is somehow busting something that is a factory second? Yes, it was a bad card along, as all of them have the potential to be discovered as such.
Interesting to know that. Out of interest, I googled around a bit to find more info on this information, but the only reference to "factory seconds" and komputerbay was in posts by you. I didn't look that hard, admittedly.
Would you mind sharing your source for this information? I think it would be interesting given the volume of use of these cards for raw by people using these forums.
Quote from: maxotics on November 20, 2013, 03:33:36 AM
Those cards are factory seconds. Which means a testing machine found potential problems. When you buy the card, you put your time into testing them further in the interest of getting a good one. I don't know of many guaranteed "brand" cards failing. IF a card was going to die, then ML would be the thing you'd want to throw at it. You're writing as fast as the camera can, generating heat, etc, and putting all the memory cells through max read/writes. I just don't get it. To ask if ML is somehow busting something that is a factory second? Yes, it was a bad card along, as all of them have the potential to be discovered as such.
I....
QuoteALL ITEMS SOLD THROUGH komputerbay.com ARE SOLD "AS IS" OR "WITH ALL FAULTS". THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE MERCHANDISE IS WITH THE BUYER. SHOULD ANY OF THE MERCHANDISE PROVE TO BE DEFECTIVE, NOT FUNCTION OR FUNCTION IMPROPERLY IN ANY FOLLOWING THEIR PURCHASE, THE BUYER, AND NOT THE MANUFACTURER, DISTRIBUTOR, OR komputerbay.com, ASSUMES THE ENTIRE COST OF ALL NECESSARY SERVICING OR REPAIR BEYOND WARRANTY IF ANY. THE BUYER SHOULD CONTACT komputerbay.com DIRECTLY WITH ANY WARRANTY ISSUES.
http://www.komputerbay.com/terms-and-conditions :-\
Quick question, searched and couldn't get an answer.
Im using Rawanizer to extract DNG's from the RAW and it creates a brilliant proxy ProRes444 file, which edits wonderfully.
Its my understanding that the DNG's are converted into TIFF by rawanizer and then uses these TIFF's to create the proxy ProRes? is that correct?
Also, why are my TIFF files looking as though they are negatives??
RAWanizer is only an GUI to command line tools which you can find located in its /tools folder.
It uses raw2dng to create dngs
it uses dcraw to create TIFFs from the dngs
It uses ffmpeg or ffmbc to create proxy videos
it uses raw2gpcf to create 422 cineform.
The versions of those programs, and the params sent to them , will change what you get.
Your TIFFs should not look like negatives. They may be bw if you send the -D param to dcraw.
Hi there 50D fans!
I´ve been searching about ETTR thing and info about how to get the best of our camera by boosting the ISO level as much as we can.
I came across with this VERY interesting article that, I think , clears up ETTR thing (Exposure To The Right) and why is important to up the Analogic ISO (NOT DIGITAL ISO or Extended ISO) levels to the maxium If necesary of our 50D etc...
as this concept is applicable to every DSLR etc..
So, I want to share this article with al l of you guys! :)
-DELETED-
What do you experts think of this?
Cheers and THANKS ML Developers/Members!
Asier.
Sorry, the link above is not working.
Please, go to this one:
http://www.guillermoluijk.com/article/iso/index.htm
It is in Spanish but you can convert it to English by clicking the British Flag that is located at the top of the article! ;)
Cheers fellows!
Asier.
Can I have a link to the latest autoexec.bin for the 50D
I downloaded the latest build for the 50D v2.3 then went into the nightly builds and downloaded the files for the 50D, replaced what was in the v2.3 build folder with what the nightly build folder included and ran it on my camera but this is what I came across.
(http://i43.tinypic.com/e63k2b.png)
Or if anyone can point out what I'm doing wrong I'd greatly appreciate it, I'm trying to record raw video soon and I just got a 32gb 1000x cf card.
Looks like you're missing your fonts.dat file, as your error says. You don't just need another .bin file if you don't have a fonts.dat
https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
Download latest, copy over all files, not exe's from latest, and run.
We had this problem with the EOS-M too. Don't believe the fonts file has changed so an old should work too in the /data folder I believe.
test video
Another Canon 50D Raw Test - Tragic Lantern
No Colour Correction made.
Latest tragic Lantern,
Resolution 1584x674 continuous
1984 x844 cropped continuous
Lens used
Moon shots - Sigma 600mm X 1.4 extender x 3 (Magic lantern crop)
all other shots Super Multi Coated Takumar f/1.4
Fotga Slim Wide band fader ND
Workflow
Son of Batch
Davinci Resolve 10 lite beta
FCPX
Latest tragic Lantern,
Resolution 1584x674 continuous
1984 x844 cropped continuous
Workflow
Son of Batch
Davinci Resolve 10 lite beta
FCPX
Quote from: scrizz on November 21, 2013, 02:53:55 AM
I....
http://www.komputerbay.com/terms-and-conditions :-\
That is at odds with the way the cards are presented on Amazon:
- COMPATIBLE WITH DSLR, SLR, AND OTHER HIGH END CAMERAS
- Comes with free plastic case compact flash and Lifetime Warranty
And:
Ultra Reliability
Backed by a lifetime limited guarantee, you can have confidence in the quality of your card and its ability to withstand some of life's toughest conditions to continue to provide you with a long-lasting, reliable memory storage solution throughout its own lifetime and that of your Compact Flash compatible device.
It even says 'professional' on the card.
Bit misleading? The text is in direct conflict with the page you linked to.
Quote from: maxotics on November 23, 2013, 04:14:48 AM
We had this problem with the EOS-M too. Don't believe the fonts file has changed so an old should work too in the /data folder I believe.
Thanks man, worked for me so far, now going out to get some test footage and put it together later tonight.
Quote from: jamesd256 on November 24, 2013, 01:13:36 AM
That is at odds with the way the cards are presented on Amazon:
- COMPATIBLE WITH DSLR, SLR, AND OTHER HIGH END CAMERAS
- Comes with free plastic case compact flash and Lifetime Warranty
And:
Ultra Reliability
Backed by a lifetime limited guarantee, you can have confidence in the quality of your card and its ability to withstand some of life's toughest conditions to continue to provide you with a long-lasting, reliable memory storage solution throughout its own lifetime and that of your Compact Flash compatible device.
It even says 'professional' on the card.
Bit misleading? The text is in direct conflict with the page you linked to.
expect the best but prepare for the worst? lol ;D
KNOCK-KNOCK, anybody out there? :o
I hope you people are fine and okay, just busy enough to drop some posts here....
Anyway, I'd like to share my experiences using the TL of October 11.
Overall I like it -- it is stable and gives good consistent results. But if I may rephrase Leo Tolstoy, we all say the same thing when everything works ok - "happy", but we bring in the difference when there is some glitch.
So, glitch-wise:
1. If I set up "Zoom on HalfShutter", this function works only when the lens is set to MF, and the screen goes purple. When I zoom in by pressing the Zoom In button in Live View, the screen has correct colors.
2. I tried to set new folders from the Canon menu: Manual Reset -> Create folder -> Select folder.
So, I had in the folder 100CANON files M29-1426.RAW and M29-1427.RAW as the ending files.
When I created new folder 101CANON and started recording, it started with M29-1426.RAW and so on... Any clues why? I expected M29-1428.RAW to be the right name for the first file in the new folder.
3. Since I have two 50D bodies right now, I do some comparison in performance. And I noticed that on one body I can set up the shutter at 1/47.8 then 1/50.7, while in the other body I have 1/47.7 and then 1/50.5. I have copied the ML files from one to another, so they have everything equal, including config file. What is the reason for that?
Also, from my wish list: is there any simple solution to somehow rate/ mark files on the go - the ones that I believe will be the best?
Thanks!
Peace ;D
just purchased a 50D + 50mm f 1.4 lens from the amazon and it comes with 16 gb lexar 600x CF card will i be able to record in a raw with it?
With that type of card you will be able to record continuous at lower resolutions such as 1280x720... The full-resolution is not typically available for shooters with less than a 1000x card. However, you will be able to record with the camera's maximum resolutions, but it will have to be utilized with lower frame rates such as 10 - 14 fps and/or time-lapse. Totally worth the shooter's experience just so you know!
Quote from: lomka on November 29, 2013, 04:51:44 PM
just purchased a 50D + 50mm f 1.4 lens from the amazon and it comes with 16 gb lexar 600x CF card will i be able to record in a raw with it?
I was able to record 1600x900 raw continuous at my Transcend x600 32gb card. Not Full HD at crop mode. In any case test your card. However keep in mind it will contain only 3-4 min of raw video.
Quote from: rommex on November 29, 2013, 04:01:40 PM
Also, from my wish list: is there any simple solution to somehow rate/ mark files on the go - the ones that I believe will be the best?
I like this idea. Since we can pre-tag mlv files as; Take1, Take2, etc..., would it be possible to do that in post? 1-5 *'s or even just a 'thumbs up/down' system would help with workflow.
Hey all,
I'm shooting a webseries on my Canon 50D with raw_rec and loving it so far. It's about a husband trying to convince his wife to have sex with him.
Problem is, I'm in Brazil and summer is starting up. This means I got some overheating warnings on my camera last night.
What should I do to deal with it? Put a fan right on top of it? Air conditioner? Constant change cards?
Also, is there a way of auto-turning off Dialog Timers? Everytime I power off the camera to change card I have to turn the Dialog Timers Off again.
Last but not least, is anyone using the 7D for raw video as well?
Is it working as good as it is on the 50D? I'm considering using the 7D as a second camera if the 50D overheats on the set...
Thank you all so much for all the help! :)
hi
When my 50D was overheating in the middle of a shoot i was opening the card slot door and taking the CF card out for a few minutes.
I also thought if that happens again i was going to try and use a can of compressed air and turn the can upside down
so the icy cold air cools the camera. NOTE: i was thinking of closing the card slot door when spraying icy cold air as moisture would get into the card slot.
Or the other method im going to try is a fan from a graphics card or those cheap 6-10volt PC case fans wired up to a 9 volt battery with a switch and maybe use the hot shoe to bolt it to the camera and i could let the fan run while i set up the next shot.
I would NOT use one of those hand held pocket fans as the blades are made of child proof rubber and are rubbish!
It would have to be a fan with hard plastic blades like in a PC tower, im sure that would cool the camera in 2min?
http://www.kenable.co.uk/product_info.php?products_id=6765&gclid=CK6i0fyuk7sCFcVQ7AodwDkAAA
stuart.
Not sure what to do with the overheating, 7D does it too just not as fast and doesn't drop FPS.
How long can camera last without overheating and when does it occur?
In terms of hours not sure, I can record at least a 64 twice over but I haven't tried in extreme heat yet. Maybe need to make some tests.
and is it true that long exposure , live view overheat the sensor and it causes the images to be more noisy?
When the sensor overheats you get more dead pixels, not really more noise. But this is true for everything. Its most visible on digic V + fps override.
7D has another problem that has to be fixed, it has vertical banding that I have to figure out at high ISO... ie 3200, maybe the one below.
Quote from: sick stu on December 03, 2013, 07:04:38 AM
hi
When my 50D was overheating in the middle of a shoot i was opening the card slot door and taking the CF card out for a few minutes.
I also thought if that happens again i was going to try and use a can of compressed air and turn the can upside down
so the icy cold air cools the camera. NOTE: i was thinking of closing the card slot door when spraying icy cold air as moisture would get into the card slot.
Or the other method im going to try is a fan from a graphics card or those cheap 6-10volt PC case fans wired up to a 9 volt battery with a switch and maybe use the hot shoe to bolt it to the camera and i could let the fan run while i set up the next shot.
I would NOT use one of those hand held pocket fans as the blades are made of child proof rubber and are rubbish!
It would have to be a fan with hard plastic blades like in a PC tower, im sure that would cool the camera in 2min?
http://www.kenable.co.uk/product_info.php?products_id=6765&gclid=CK6i0fyuk7sCFcVQ7AodwDkAAA
stuart.
Thank you for the idea. I'll definately try to put a fan on it and turn of camera when arranging the set.
Quote from: lomka on December 03, 2013, 01:51:00 PM
How long can camera last without overheating and when does it occur?
It was real quick last time. I was in a theater stage and about 15min I started to get overheat warnings. We had to turn off the air conditioner because of the noise, so it doesn't affect the audio.
I was also using these batteries, since my original canon are old.
http://www.ebay.com/itm/300909515561?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
Maybe it's battery related? They smelled funny right out of the package, but they worked fine tho.
Quote from: dsManning on October 09, 2013, 07:22:31 PM
Thanks for the fisheye crop videos and talk. Was just chatting with D.L. Watson about the 8mm Rokinon in crop mode. Seems like a good buy, and that these fisheye lenses are turning out ok for crop shooting. Also noticed you are around Porter Square area. I'm right across the river in Brighton.
Let me get my math straight.
If I use 5x Crop with my 50D and the Rokinon 8mm it would be:
8 x 1.6 = 12.8
12.8 x 5 = 64
64mm effective Field Of View without Fisheye effects. Right?
That would give me 14bit RAW @ 1920x1080 with very limited moire / aliasing at almost a "normal" lens.
Quote from: djfremen on December 04, 2013, 01:42:51 AM
Let me get my math straight.
If I use 5x Crop with my 50D and the Rokinon 8mm it would be:
8 x 1.6 = 12.8
12.8 x 5 = 64
64mm effective Field Of View without Fisheye effects. Right?
That would give me 14bit RAW @ 1920x1080 with very limited moire / aliasing at almost a "normal" lens.
Nearly. I worked out the raw crop factor on the 50D (at 1080p) is 2.475x not 5x. It can shoot 2000px but it's near enough for a good approximation.
5x is the live view zoom factor (the recorded area is bigger than what you see in Liveview) so your 8mmm will be equivalent to approx 32mm on a full frame sensor. You may still get some distortion with a fisheye which will need correcting. Unfortunately, the recorded area (in crop mode) is not exactly in the center of the sensor so it will not be uniformed distortion :( You would need to manually correct perspective and pin-cushioning in post.
Other than that and the fact that you can't see exactly what you're shooting in crop, crop raw will give you the best quality. I'm shooting with it all the time. I rarely see moire and very little aliasing.
Tip: To 'roughly' work out what a lens will be when shooting crop video, just add the APS-C and raw crop factors i.e. lens focal length x 4
--dogmydog--
I also forgot to mention details of 50D overheating experience:
I was DOP on a short film and location was in a mens toilet.
and noooo it wasn't one of those movies before anyone asks.
There was a crew of 9 inc 2 actors, no windows, had to turn aircon off
for sound, camera was on a tripod so not getting any heat from my hands.
And it was around the 4th/5th hour when the room was getting its hottest
i noticed the 50D was crashing/freezing every 3rd take using a Komputerbay1000x 64gb
settings was H264 CBR, CBR factor 2.4x that i lowered to 2.0x for slightly better stability.
Batteries were 1x OEM canon, 1x Hamel, 4x Duracell (very good value for money).
Director called a lunch break, memory card was very hot.
After the camera cooled down we shot for another 2 hrs and 50D started crashing again.
Lucky we was filming the last few shots.
Quote from: Andy600 on December 04, 2013, 09:22:26 AM
Nearly. I worked out the raw crop factor on the 50D (at 1080p) is 2.475x not 5x. It can shoot 2000px but it's near enough for a good approximation.
5x is the live view zoom factor (the recorded area is bigger than what you see in Liveview) so your 8mmm will be equivalent to approx 32mm on a full frame sensor. You may still get some distortion with a fisheye which will need correcting. Unfortunately, the recorded area (in crop mode) is not exactly in the center of the sensor so it will not be uniformed distortion :( You would need to manually correct perspective and pin-cushioning in post.
Other than that and the fact that you can't see exactly what you're shooting in crop, crop raw will give you the best quality. I'm shooting with it all the time. I rarely see moire and very little aliasing.
Tip: To 'roughly' work out what a lens will be when shooting crop video, just add the APS-C and raw crop factors i.e. lens focal length x 4
Thanks Andy.
Think that maybe the 14mm makes the most sense @ 55.44 mm.
It also probably won't contain that type of distortion.
So what's your advice for finding the region contained in the 5x? It seems you'd have to roll a test clip and then playback just to see what part of the image is being captured.
Quote from: djfremen on December 04, 2013, 08:25:01 PM
Thanks Andy.
Think that maybe the 14mm makes the most sense @ 55.44 mm.
It also probably won't contain that type of distortion.
So what's your advice for finding the region contained in the 5x? It seems you'd have to roll a test clip and then playback just to see what part of the image is being captured.
Use 10x for focusing and the 'auto' preview mode set in the raw_rec or mlv_rec modules for framing (it's crap looking but accurate for framing a shot). I have Global Draw set to go off when I hit record (for speed) but it means you're stuck with a 5x crop view when filming I'm afraid (i.e. not the full recordable area).
Set focus box to 'snap to 5x raw' and press the joystick once in 5x mode. This will make live view jump to the center of the crop area but you'll have to guess at what is in frame outside of this area.
You can use the color preview full time with this too but does the cam overheat faster?
is fast overheating issue only on 50d and 7d? and can it be "fixed"/resisted somehow?
Its an issue for everything below 600D or maybe 60D. Whatever has that lv_state instead of evf state seems like overheat city.... not running a ton of stuff like histograms/waveforms/display filter/etc especially ones that touch the raw data helps but there is no real way to avoid it. In a hot climate I bet its a nightmare.
http://ghonis2.ho8.com/rebelpeltier.html it would be nice if someone did this to 50d.
Quote from: lomka on December 06, 2013, 05:39:43 PM
http://ghonis2.ho8.com/rebelpeltier.html it would be nice if someone did this to 50d.
So what's stopping you?
Quote from: Andy600 on December 06, 2013, 05:46:43 PM
So what's stopping you?
my camera is still shipping and i don't have skills to do it :X
Happen to see this mentioned on No Film school: raw software called ClipHouse (to copy, manage, colour, export) which it is claimed can also handle ML raw files. Costs $49 for a yearly renewal or $129 for a permanent license:
http://pomfort.com/cliphouse/index.html
Here's the No Film School item I found it from:
http://nofilmschool.com/2013/12/introducing-pomfort-cliphouse-raw-processing-software/
You can try it out for free. I think it's Mac only.
EDIT: I'd better post this in the "Post" section too, though the 50D section is my favourite place!
If heat becomes a major issue... Purchase an inexpensive A/C adapter that fits in the grip of the camera. I had a two camera shoot with the 50D. One camera was on batteries and the other was on A/C. The camera without the battery was typically 3 degrees Celsius cooler. It took the camera nearly an hour to reach the same temp as the camera with batteries. There is a definite advantage with the A/C adapter.
May even consider purchasing two A/C adapter. Then, adapt the second A/C adapter and run it to a secondary battery.
What about grip + AC adapter.
Quote from: LEVISDAVIS on December 07, 2013, 05:16:51 PM
If heat becomes a major issue... Purchase an inexpensive A/C adapter that fits in the grip of the camera. I had a two camera shoot with the 50D. One camera was on batteries and the other was on A/C. The camera without the battery was typically 3 degrees Celsius cooler. It took the camera nearly an hour to reach the same temp as the camera with batteries. There is a definite advantage with the A/C adapter.
Ty for the tips, guys! I really appreciate it.
I already bought a AC adapter on eBay, but it hasn't arrived yet.
I'll have a shoot next Monday. I'll put a dedicated fan on top of camera and ill use the AA batteries adapter on my grip. I'll post results here if it was of any help :)
Thanks again
is there any new developments for the dead pixel problem that happens in high iso values?
Quote from: pags on December 09, 2013, 05:03:54 AM
is there any new developments for the dead pixel problem that happens in high iso values?
there is sensor cleaning option in camera which maps dead pixel.
Can someone please say if that Flickering issue in the Grayscale mood was always there ? On my 5D iii it's working just fine and I can frame my subject in 3xcrop. Also I don't remember that thing happen 4-6 months ago. I was wondering if there is any issue with my 50D camera?
Here how it's look like:
https://vimeo.com/81429160
I'm using Latest Build 2013-12-08
Edit - if that's the "dialog timer" how do I disable it? , Sorry but I can't seem to find it anywhere. Thanks!
Edit 2 - so it was the "dialog timer" thanks 1%, somehow I didn't have dialog timer in the Debug and missed that. I just looked in an older Build in a different card. Also lots of Modules was somehow missing here (like mlv_rec.mo), not sure why. Anyhow thanks!
Thats canon redraw, dialog timer is active.
Quote from: Andy600 on December 06, 2013, 05:46:43 PM
So what's stopping you?
Hi Andy600 - just a quick question.....did you ever publish the ML 50D user manual you were working at?
Regards!
Quote from: hijodeibn on December 11, 2013, 06:23:46 PM
Hi Andy600 - just a quick question.....did you ever publish the ML 50D user manual you were working at?
Regards!
Not yet. Now that MLV is working and I have a reliable post workflow to recommend I'll get it finished but time is always against me ATM. At last count it was 50+ pages without any images yet... still got to do all those bits.
Quote from: Andy600 on December 11, 2013, 06:42:21 PM
Not yet. Now that MLV is working and I have a reliable post workflow to recommend I'll get it finished but time is always against me ATM. At last count it was 50+ pages without any images yet... still got to do all those bits.
I'd hate for time to be against me ass-to-mouth.
I'm going to be on vacation for a week, I might be able to make some images for you.
It would be really great to have a guide, with the .flv workflow and the latest build in your manual... I would pay good money for that! It would get me and whoever I work with a real fast and deep knowlodge about the camera and how to turn them to videos and grade before finally edit... et voi la
=)
Quote from: Andy600 on December 04, 2013, 09:22:26 AM
Nearly. I worked out the raw crop factor on the 50D (at 1080p) is 2.475x not 5x. It can shoot 2000px but it's near enough for a good approximation.
5x is the live view zoom factor (the recorded area is bigger than what you see in Liveview) so your 8mmm will be equivalent to approx 32mm on a full frame sensor. You may still get some distortion with a fisheye which will need correcting. Unfortunately, the recorded area (in crop mode) is not exactly in the center of the sensor so it will not be uniformed distortion :( You would need to manually correct perspective and pin-cushioning in post.
Other than that and the fact that you can't see exactly what you're shooting in crop, crop raw will give you the best quality. I'm shooting with it all the time. I rarely see moire and very little aliasing.
Tip: To 'roughly' work out what a lens will be when shooting crop video, just add the APS-C and raw crop factors i.e. lens focal length x 4
How would I determine the crop factor of 1280x720? I noticed this is also suffering from out of framed material in live view. I'm sticking by the fact that the only sure way to check framing is by rolling a prerecorded shot in the RAW record module.
Any chance we could know the x axis and y axis of the region being recorded in crop mode? Would there be a way to shoot a still, then match a 5x raw dmg against in Photoshop to determine exactly what region of the sensor is being used? Just a thought.
Thanks.
************************************
***New Build of Tragic Lantern uploaded***
************************************
Disclaimer
As the 50D and several other models have been removed from the nightly builds (at least temporarily until the acceptable parts of Tragic Lantern are ported), you have the option of either building your own or downloading my build of 1%'s Tragic Lantern for the 50D.
I regularly receive messages regarding these builds as to their reliability and safety but I can only offer my opinion based on my own experience and daily usage. I am not an experienced coder. I have very basic knowledge (enough to compile and port a few things) and accept that developers like a1ex and g3gg0 would not highlight the dangers of such builds without good cause. I therefore state again that using these builds may damage your camera, although I have never personally had any problems.
By installing an unsupported build of Magic Lantern (as is the case with Tragic Lantern) you do so unsupported and entirely at your own risk. Please do not expect a1ex or other devs to come to the rescue if something breaks.
Hopefully, with a little help from willing users we can begin to commit things back to the main Magic Lantern Unified build and get it back into the nightly releases but for now, if you want the latest features, you will need to use Tragic Lantern.
Tragic Lantern is a rolling release and many features are experimental, specific to certain cameras and not thoroughly tested (although I do try to test as much as possible before uploading a new build). Tragic Lantern still has issues with incorrect shutter readout and problems with digital ISO. Please do not ask me when this will be fixed. I simply don't know and my guess is that it is a fairly big issue that will need a lot of work by a knowledgeable dev.
The latest build
It's been about a month since I last uploaded a build. There have been improvements to mlv_rec which is now, IMO, as useable as raw_rec with the added benefit of metadata, however raw_rec is still included and has an 'experimental' feature of selectable single or double buffering. It is up to you to test and report back here ;)
The Histogram was broken for several months and nobody noticed. A1ex spotted that only the top half of the histogram was being used (probably why the lower half always appeared red). This is now fixed.
mlv_play has had a few improvements and is useable for either .mlv or .raw video playback. You can press the camera play button to instantly access playback of your most recent shot and use the top wheel to scroll through other shots. Pressing the Picture Style button will bring up the player controls with selectable (fast) playback in grayscale or (slow) color. You can also now delete clips using the player.
The issue with pink or corrupt frames (.mlv) was resolved in the last build but has since been found to be overkill, lowering the priority of the writer below what the camera is capable of. The priority has been increased and you can now shoot .mlv with Global Draw ON and use focus peaking. I have tested this feature and not had any pink frames but please report if you have this problem. A balance needs to be found between performance and reliability.
To work around the shutter issue I suggest setting the shutter angle in the main menu and then locking the shutter in the movie menu (movie tweaks) after setting your desired fps with FPS override.
There are also several other minor tweaks and fixes but mostly to backend stuff.
Download the latest Tragic Lantern for the 50D here: https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Dec15_Histogram_fix_&_MLV_Improvements.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Dec15_Histogram_fix_&_MLV_Improvements.zip)
If you have to ask me how to install it you really shouldn't be using it! ;)
OT: You also download my FREE Film Punch LUT: http://www.magiclantern.fm/forum/index.php?topic=9521.msg91376#msg91376
This is great! Love the MLV playback. It's an excellent and fast way of checking framing for 5x zoom.
Also tested the recording module and like the metadata addition.
One caveat is that you can't use mlvdump on any mac below 10.8.
Here's my command in terminal in Mavericks:
"mlv_dump --dng <path/filename.mlv>"
Usually just copy and past mlv_dump in same folder as mlv file, then run terminal.
************************************
***New Build of Tragic Lantern uploaded***
************************************
Thanks Andy, 1%, Alex and everyone!
Got a reply from Mosaic Engineering here at 1:40 PM on 12-16-2013...
"We're writing to you today because you had previously emailed to us inquiring about a Video Aliasing Filter for the Canon 50D. By the way, we apologize for our delay in responding if we've not replied to you previously.
Nevertheless, we'd like to let you know that we do now have the VAF-50D available, for use with Magic Lantern RAW video recording!
The VAF-50D is available now, in our online store: http://store.mosaicengineering.com (http://store.mosaicengineering.com)
A brief with-and-without demo video of this filter -
- has been produced by Mr. Levi Davis. We expect to have additional video example material available before long, and will post that as soon as possible also.
Our product page for this new filter is here - http://mosaicengineering.com/products/vaf/50d.html (http://mosaicengineering.com/products/vaf/50d.html); we'll be adding more information and details shortly.
Sorry again for our delay in responding; anyway we hope this information can help you at this time!
Thank you again for your interest in our filters,"
Looks like 50D shooters are about ready to hit the professional market!!! Been having a lot of success with the prototype filter myself. The filter does a great job of resolving details and eliminating moire. The camera before the VAF displays serious issues with moire. These issues appear in every image in some way shape or form. There is moire on straight lines & fine detail. There is more on skin tones in areas of fine detail. With the VAF filter I'm shooing an image that holds about the same detail as a BMPCC. Albeit there are low-level moire issues with the prototype 50D VAF but the levels are nearly identical to the BMPCC. Technically this quite the accomplishment given the BMPCC shoots pixel for pixel and the 50D is line skipping a 5K sensor...
Picked up the BMPCC about two weeks back after watching a side-by-side dynamic range test with the BMPCC and the 50D. Dynamic range will play a large roll in future sensor development for sure. The 50D resolves about 10.5 to 11 stops in comparison to the 13 stops of the BMCC. However, the 50D appears to resolve a stronger color pallet. Quite simply, the 50D shoots a wonderful image for a colorist. In my opinion, I've got a long way to go before the BMPCC hits my liking... It's as though one unit is happy and beautiful and the other unit is bland and extremely true... Hmm??? Perhaps the 50D appears to hold a more of a mass-market "look & feel?" Maybe in 5 years I'll say the complete opposite?
If the 50D and the BMPCC cameras are going to be compared for their resolution and similar moire issues, then the shooter should be made aware of the sensor's capabilities and limitations...
The noise floor is definitely more apparent with the 50D. The image slightly suffers from what appears to be sensor refreshing / banding, even at lower ISO values and exposing to the right. Adobe Camera Raw typically requires the chroma channels and luma channels to have low-level noise reduction. DaVinci Resolve 10 might actually produce a better noise floor, however, ACR typically produces a much stronger result. Essentially, though, we are talking about a sensor that has so much life in the image! The skin tones in particular are very prominent! The strength of the colors wants to reach out and touch the audience. In particular, the sensor has the great latitude so long as the image is inhibited by moire.
The grain and noise floor of the BMPCC are much more video/filmic. Additionally, there is no allaying issues with the sensor. However, at this point in my venture with the camera, the sensor readout lacks the character that the 50D lends so wonderfully. Having applied 6 months of raw color-correction techniques to the BMPCC, I've found the camera captures nearly exactly what that eye sees. It's almost as though a perfect copy of the real world has transferred into the raw digital realm. Therefore, if you want character with the BMPCC, BMPCC shooters need to push "character" into the image in the production.
With cameras like a "50D + Mosaic Engineering VAF + Magic Lantern" and the "BMPCC + raw" a shooter is able step aside from technical faults and truly produce an image made for high-quality television productions & independent film productions. Let's face it, this level of confidence is absolutely necessary. After all, the purpose of the shooter is to push the sensor to the limits, right? Quite simply, the 50D's limitations come up a bit too quick without the aid of the VAF.
... Continuing with the 50D VAF filter testing... The 3x zoom is soft with the filter in place, but I still shoot 3x with the filter in place...Not that it's a "completely unique look..." It's a usable look without too much degradation.
After about three months of testing the prototype filter, I think it is a very positive/powerful addition to the camera. This statement holds especially true considering BMPC's ability to resolve detail on a sensor shooting "pixel for pixel." Effectively, the 50D is right there with the BMPCC's image detail at 1600x900 when the BMPCC is shooting native 1920x1080.
Feel free to download the CDNG samples of the 50D with the prototype VAF on Copy. There are full-sesor read-out images as well as 3x image readouts. The images were taken with a near mint 35mm Nikon Nikkor F2.8 AI. The lens has a 52mm ProMaster UV in place. Please follow this link to download native CDNG images copy.com/8PP4i3MBODoTiovb (http://copy.com/8PP4i3MBODoTiovb).
The images are of an author named James Hinkley: Jimhinkleystudio.zenfolio.com & route66chronicles.blogspot.com. James has authored a number of books about Historic Route 66 in addition to other solid works of history! Interestingly, I talked to him about the production of the book and he had used the 50D for many of the shots along Route 66. He was very impressed to see the power behind ML! "What comes around goes around, right?"
Special thanks to the ML team and Mosaic Engineering! Feels great to have such a powerful workflow. Enjoy!
Quote from: LEVISDAVIS on December 16, 2013, 10:01:26 PM
Got a reply from Mosaic Engineering here at 1:40 PM on 12-16-2013...
"We're writing to you today because you had previously emailed to us inquiring about a Video Aliasing Filter for the Canon 50D. By the way, we apologize for our delay in responding if we've not replied to you previously.
Nevertheless, we'd like to let you know that we do now have the VAF-50D available, for use with Magic Lantern RAW video recording!
The VAF-50D is available now, in our online store: http://store.mosaicengineering.com (http://store.mosaicengineering.com)
A brief with-and-without demo video of this filter - http://vimeo.com/74470756 - has been produced by Mr. Levi Davis. We expect to have additional video example material available before long, and will post that as soon as possible also.
Our product page for this new filter is here - http://mosaicengineering.com/products/vaf/50d.html (http://mosaicengineering.com/products/vaf/50d.html); we'll be adding more information and details shortly.
Sorry again for our delay in responding; anyway we hope this information can help you at this time!
Thank you again for your interest in our filters,"
Looks like we are about ready!!! Been having a lot of success with the prototype filter myself. I'm positive there is about the same if not less moire than the BM Pocket Cinema Camera... Picked up one about two weeks back after a post demonstrating the incredible dynamic range...! Seriously though, the 50D has an incredible sensor for resolving color detail. The images from raw video, specifically using the Mosaic VAF are completely usable for television productions & independent film productions... Yes, the 3x zoom is soft with the filter in place, but I still shoot 3x with the filter in place...Not that it's a unique look... It's a usable look that isn't degraded by much... Still, after about three months of testing, I think it is a very powerful addition to the camera, especially if you consider the market's inability to resolve detail. Effectively, the 50D is right there with the pocket and the pocket is shooting native full HD.
Awsomew news Levi!!
Andy, thak you so much for the update to tragic lanter. And thank you to all the ML dev team. Great, Great
Work!
Great news about the VAF-50D Levi.
Do you know if there are any differenced between the prototype unit you've been testing and the production units?
I was told they were going to improve upon the prototype over 3 months ago... I also know that they have a Canon 50D to test with... However, I haven't heard anything from Mosaic specifically about improvements or advancements...
I like your question... That was one of my first thoughts regarding Mosaic's email today too.
Is this a bug?
When I boot up my 50d and enter Magic Lantern I am able to use the scroll wheel to jump from one menu item to another. BUT, when I start the Live View and try again to use the scroll wheel it simply does not work anymore. Now it changes the exposure e.g from f2.8 to something else. I tried the last 3 releases from Andy600. They all behave the same. I find it very annoying since I am used to use the scroll wheel and now accidental change the exposure.
I searched this thread and found that joaomoutinho noticed this behavior before.
Quote from: joaomoutinho on October 14, 2013, 11:20:20 PM
...
dont know why, but it runs like this as soon as I've installed this last version. Hum, and another thing that happened, the scrolling weel in the back of the camera stoped working. Now I have to do everything with the "joystick". :-\
Something went wrong...
...
I didn't have a look at the source code, but it seams to me that somewhere a method call to register the scroll wheel when displaying the menu and not the Live View is missing.
@1%
I hope with help of my description you can easily locate where to fix the bug in the code when you find time. I assume you know the code in and out and already know in which class you need to add just a line of code. ;) I'm still trying to understand how Magic Lantern works by reading the code of your branch.
Thank you very much for all the time you spend to add new functions, improve the code and tweak it for maximum performance.
Best regards,
Marco
Quote from: tecgen on December 17, 2013, 08:54:52 PM
Is this a bug?
When I boot up my 50d and enter Magic Lantern I am able to use the scroll wheel to jump from one menu item to another. BUT, when I start the Live View and try again to use the scroll wheel it simply does not work anymore. Now it changes the exposure e.g from f2.8 to something else. I tried the last 3 releases from Andy600. They all behave the same. I find it very annoying since I am used to use the scroll wheel and now accidental change the exposure.
I searched this thread and found that joaomoutinho noticed this behavior before.
I didn't have a look at the source code, but it seams to me that somewhere a method call to register the scroll wheel when displaying the menu and not the Live View is missing.
@1%
I hope with help of my description you can easily locate where to fix the bug in the code when you find time. I assume you know the code in and out and already know in which class you need to add just a line of code. ;) I'm still trying to understand how Magic Lantern works by reading the code of your branch.
Thank you very much for all the time you spend to add new functions, improve the code and tweak it for maximum performance.
Best regards,
Marco
You immediately assume it's a bug ???. Delete your config files and try again. I don't have this problem. Anyone else?
Quote from: Andy600 on December 17, 2013, 08:56:58 PM
You immediately assume it's a bug ???. Delete your config files and try again. I don't have this problem. Anyone else?
I installed the latest stable ML 2.3 on a fresh card. I could reproduce the same behavior, but only when I set
LV Display: Movie. In case of
LV Display: Photo, ExpSim the scroll wheel even works after activating the Live View. So I assume now that its not a bug in ML ;) .
Its interesting, when I set with ML 2.3
LV Display: Photo, ExpSim, shut down the camera and switch to another card with the latest build from December 15, the scroll wheel works as expected when I start Live View. But, when I set
LV Display: Movie with ML 2.3, shut down the camera again and switch to the latest Dec.15 version, I can reproduce the behavior explained before where the scroll wheel stops working after activation of the Live View. I didn't find the switch
LV Display in the latest version, where I can set the values I am able to change with ML 2.3. Is it not available anymore or am I blind? :o
For expsim: define CONFIG_EXPSIM_MOVIE in internals.h (should be like 5D2).
For scrollwheel: you may want to find another GUIMODE_ML_MENU (trial and error). 500D has the same problem.
When setting LV Display: Photo, no ExpSim in ML 2.3 and starting afterwards the Dec. 15 version, the scroll wheel works as expected after switching on Live View. I can live with this because now the scroll wheel works always and the Live View image changes the ISO value automatically when I set it to AUTO, which I prefer.
@a1ex
Thank you for your hint. I'll have a look into the header file for the constant.
best regards,
Marco
Quote from: Andy600 on December 15, 2013, 02:54:53 PM
************************************
***New Build of Tragic Lantern uploaded***
************************************
Are there any improvements to the dead pixel problem?
Haven't had a chance to try the new build, Thanks for all the work done to make my 50D the monster it is!
Hey guys, I did a comparaison between the 50D and a panasonic G6 and it hits hard... only the crop mode can hold a chance!
Skip to 3.15 for the comparaison footage, but there are test shots in the firts half too.
Same lenses, same tripod, same position ext (Samyang 14mm t3.1 and centon 50mm f1.7)
For my use the G6 is a much better camera...
:)
Quote from: bzhwindtalker on December 18, 2013, 02:55:38 PM
Hey guys, I did a comparaison between the 50D and a panasonic G6 and it hits hard...
For my use the G6 is a much better camera...
I like the G6 and the G3. I think you said it all when you said for your use. It is sort of an apples and oranges thing. Not really looking to debate the merits on this forum. Glad that you found something that you like. :)
Quote from: bzhwindtalker on December 18, 2013, 02:55:38 PM
Hey guys, I did a comparaison between the 50D and a panasonic G6 and it hits hard... only the crop mode can hold a chance!
Skip to 3.15 for the comparaison footage, but there are test shots in the firts half too.
Thanks Adam- wish I could have known which lens was on which camera.
The focal length according to my math is about 55mm with that samyang in crop mode. How does it look? Any fringe near the edges?
Thanks.
Quote from: bzhwindtalker on December 18, 2013, 02:55:38 PM
Hey guys, I did a comparaison between the 50D and a panasonic G6 and it hits hard...
For my use the G6 is a much better camera...
Very nice slider shots. But you should work more on the sound design -- couldn't hear well what you say there.
Thanks for the comments guys, it was my first time at using my audio gear and English is not my native language (not hard to guess lol). The samyang 14 is a nice lens but it's not fast at t3.1 if you want to use it as your main lens in crop mode. Also, you have deep Dof so the image won't look very cinematic. I had my 50d for 400€ (+2x70€ for fast cf cards) and the g6 costed me 470€ new with the kit lens.
Quote from: bzhwindtalker on December 19, 2013, 01:45:48 PM
Thanks for the comments guys, it was my first time at using my audio gear and English is not m
y native language (not hard to guess lol). The samyang 14 is a nice lens but it's not fast at t3.1 if you want to use it as your main lens in crop mode. Also, you have deep Dof so the image won't look very cinematic. I had my 50d for 400€ (+2x70€ for fast cf cards) and the g6 costed me 470€ new with the kit lens.
[Quote/]
What are you using to capture images on the G6?
Quote from: lionelp link=topic=5586.msg92239#msg92239
I had my 50d for 400€ (+2x70€ for fast cf cards) and the g6 costed me
Quote/]
What media / cards are you using to capture images on the G6?
H264 on a class 4 sdhc card, 28mb/sec.
Quote from: LEVISDAVIS on December 17, 2013, 08:54:58 AM
I was told they were going to improve upon the prototype over 3 months ago... I also know that they have a Canon 50D to test with... However, I haven't heard anything from Mosaic specifically about improvements or advancements...
I like your question... That was one of my first thoughts regarding Mosaic's email today too.
Great Work, Levi's!
Anyone actually bought the VAF? I'm seriously thinking of getting one in January.
I think it's worth the investment over the BMPCC, since I already bought the three 1000x CFs, own several EF-S lenses and Canon 50D body. Also I need full sensor because I shoot at 16mm-20mm focal distance.
Can someone please tell me how to install magic lantern om my canon 50d just got it.
Quote from: lomka on December 20, 2013, 08:58:08 PM
Can someone please tell me how to install magic lantern om my canon 50d just got it.
Welcome aboard :)
Read this http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0), install v2.3, get used to how it works and only then think about raw etc.
Who tested 'experimental' feature of selectable single or double buffering ? :o
Unfortunately i don't have a card reader, is there a way to install magic lantern without card reader?
No.
Quote from: Andy600 on December 15, 2013, 02:54:53 PM
************************************
***New Build of Tragic Lantern uploaded***
************************************
Disclaimer
As the 50D and several other models have been removed from the nightly builds (at least temporarily until the acceptable parts of Tragic Lantern are ported), you have the option of either building your own or downloading my build of 1%'s Tragic Lantern for the 50D.
I regularly receive messages regarding these builds as to their reliability and safety but I can only offer my opinion based on my own experience and daily usage. I am not an experienced coder. I have very basic knowledge (enough to compile and port a few things) and accept that developers like a1ex and g3gg0 would not highlight the dangers of such builds without good cause. I therefore state again that using these builds may damage your camera, although I have never personally had any problems.
By installing an unsupported build of Magic Lantern (as is the case with Tragic Lantern) you do so unsupported and entirely at your own risk. Please do not expect a1ex or other devs to come to the rescue if something breaks.
Hopefully, with a little help from willing users we can begin to commit things back to the main Magic Lantern Unified build and get it back into the nightly releases but for now, if you want the latest features, you will need to use Tragic Lantern.
Tragic Lantern is a rolling release and many features are experimental, specific to certain cameras and not thoroughly tested (although I do try to test as much as possible before uploading a new build). Tragic Lantern still has issues with incorrect shutter readout and problems with digital ISO. Please do not ask me when this will be fixed. I simply don't know and my guess is that it is a fairly big issue that will need a lot of work by a knowledgeable dev.
The latest build
It's been about a month since I last uploaded a build. There have been improvements to mlv_rec which is now, IMO, as useable as raw_rec with the added benefit of metadata, however raw_rec is still included and has an 'experimental' feature of selectable single or double buffering. It is up to you to test and report back here ;)
The Histogram was broken for several months and nobody noticed. A1ex spotted that only the top half of the histogram was being used (probably why the lower half always appeared red). This is now fixed.
mlv_play has had a few improvements and is useable for either .mlv or .raw video playback. You can press the camera play button to instantly access playback of your most recent shot and use the top wheel to scroll through other shots. Pressing the Picture Style button will bring up the player controls with selectable (fast) playback in grayscale or (slow) color. You can also now delete clips using the player.
The issue with pink or corrupt frames (.mlv) was resolved in the last build but has since been found to be overkill, lowering the priority of the writer below what the camera is capable of. The priority has been increased and you can now shoot .mlv with Global Draw ON and use focus peaking. I have tested this feature and not had any pink frames but please report if you have this problem. A balance needs to be found between performance and reliability.
To work around the shutter issue I suggest setting the shutter angle in the main menu and then locking the shutter in the movie menu (movie tweaks) after setting your desired fps with FPS override.
There are also several other minor tweaks and fixes but mostly to backend stuff.
Download the latest Tragic Lantern for the 50D here: https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Dec15_Histogram_fix_&_MLV_Improvements.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Dec15_Histogram_fix_&_MLV_Improvements.zip)
If you have to ask me how to install it you really shouldn't be using it! ;)
OT: You also download my FREE Film Punch LUT: http://www.magiclantern.fm/forum/index.php?topic=9521.msg91376#msg91376
50d comin in Monday. Staying tuned now with this thread :]
Anyone else experiencing errors with MLV Dump and strange lines since the newest version of TL?
(http://img.tapatalk.com/d/13/12/22/a6ehegev.jpg)
(http://img.tapatalk.com/d/13/12/22/eputuvet.jpg)
Will post footage of the BMPCC and the 50D with the Prototype Anti-Aliasing Filter sometime before Christmas... Will fire off some Raw footage at the same time using a 50mm and a 24mm... Again, I am continually finding that the moire is nearly identical... Surprisingly, I'm finding better noise floor patterns with the 50D in daylight. Haven't worked with the BMPCC long enough to truly understand the sensor... Of course I really want to stress that the 50D has amazing color correction potential!!! The BMPCC is a total different ballgame. For the BMPCC ACR is going to the limits of it's slider adjustments in order to make the image pop, particularly the individual color channels. In some ways this is causing a lot of noise in the image... Then again, why shoot raw if the image isn't going to pop!!!?
The 50D is ready to sing in ACR. Loving how RawMagic provides the user the ability to change the ACR picture profile from Embedded to Landscape, Portrait, and Standard, and Faithful... etc. However, are there any 50D & RawMagic users experiencing issues with RawMagic? I continue to find random occurrences of vertical and horizontal lines. The same RAW file in Raw2DNG doesn't introduce the vertical and horizontal lines... Unfortunately, Raw2DNG does not process the footage as though it were a Canon 50D. Any help in both of these departments would be greatly appreciated... Thanks.
Quote from: HHL on June 02, 2013, 07:19:56 AM
One more example of highlight recovery. Enjoy!
(http://farm6.staticflickr.com/5445/8919875957_d5c6b4d421_o.jpg)
(http://farm4.staticflickr.com/3748/8919875721_50d4e5b268_o.jpg)
Hi, I was reading your post and I saw that you posted two pictures: one really green picture and one really magenta picture.
I'm having problems with getting really green and noisy .DNG files when I convert my .RAW files and import them into Lightrooom 5.
How do I fix this problem? Cam you please help me?
I posted a question about this here: http://www.magiclantern.fm/forum/index.php?topic=9624.new#new, but wasn't able to get much help.
Thanks in advance.
Quote from: lomka on December 22, 2013, 12:15:21 AM
Unfortunately i don't have a card reader, is there a way to install magic lantern without card reader?
Also, if you can, get a USB 3.0 card reader.
It seems that USB 2.0 card readers are damaging 1000x CF cards. I had a damaged Transcend that i sent to RMA, but I'm not sure if its card reader related.
Quote from: dogmydog on December 23, 2013, 01:45:50 PM
Also, if you can, get a USB 3.0 card reader.
It seems that USB 2.0 card readers are damaging 1000x CF cards. I had a damaged Transcend that i sent to RMA, but I'm not sure if its card reader related.
Um . . . probably not. It was probably the USB reader. Been using mine for more than a year now.
I recreated a scene from Memento, shooting 50D raw. The first time I shot on the 50D 'project based'. I shot mostly some test footage, but always just some shots without any kind of precise framing etc.
When we were shooting the camera crashed 3 times (mostly at the end after 8 hours of shooting). The framing of the shot was confusing at times. When loading the footage on my laptop, the framing was a little off. I saw objects in frame on the laptop screen that I didn't see on the lcd. When I disabled the cinemascope cropmarks, the framing seemed fixed. I think? Reviewing your footage also a pain. Post production is long and tiresome but the images the camera produces are great so it's worth it. Personally I just can't deal with that much of uncertainty when shooting, but I wont go back to h264 crap either.
Great effort SebaVuye.
But I would notice some points: I don't understand why, even using RAw, you have some overexposed areas, making the whole thing look digital.
Notice the bed on the right while the telephone is ringing, or the hand on the left while watching the photo.
Also the head in the first shots has a light problem, making it look a bit flat and not enough dramatic.
Last, but not about the quality of filming, is that original actor gives much more tension.
Anyway, an excellent exercise!
Quote from: riccardocovino on December 24, 2013, 09:28:39 AM
Great effort SebaVuye.
But I would notice some points: I don't understand why, even using RAw, you have some overexposed areas, making the whole thing look digital.
Notice the bed on the right while the telephone is ringing, or the hand on the left while watching the photo.
Also the head in the first shots has a light problem, making it look a bit flat and not enough dramatic.
Last, but not about the quality of filming, is that original actor gives much more tension.
Anyway, an excellent exercise!
Thanks
All true. The overexposed area's are the result of ACR and this flickering issue when adjusting Highlights and Shadows sliders :/ I left those two options untouched in ACR because every adjustment resulted in flickering of my image.
Merry Christmas!
Give it some time SebaVuye. You're working with a great camera. Yes, there are some overheating issues that tend to cause issues when writing files... I would agree that the framing may have been off with cinemascopes put in place... Another issue is if you view the LCD screen in a ML Hacked Mode... There can be a slow refresh rate issue too. But, again, it really is a great tool. Maybe a little finicky from time to time, but this camera is well worth the time. It will certainly capture some timeless moments. Enjoy and keep shooting. P.S. Watching your video now.
Posted a 5 minute video featuring the 50D and the BMPCC. It's not your typical camera comparison video... It's more of a get to know your camera for what it's worth type video. I hope it helps you look further into the power of the camera. Here is the link to the video.
http://youtu.be/1eNuxW5fIew (http://youtu.be/1eNuxW5fIew)
Quote from: LEVISDAVIS on December 26, 2013, 08:14:18 AM
Posted a 5 minute video featuring the 50D and the BMPCC. It's not your typical camera comparison video... It's more of a get to know your camera for what it's worth type video. I hope it helps you look further into the power of the camera. Here is the link to the video.
http://youtu.be/1eNuxW5fIew (http://youtu.be/1eNuxW5fIew)
Thanks bro!
Quote from: LEVISDAVIS on December 26, 2013, 07:41:26 AM
Give it some time SebaVuye. You're working with a great camera. Yes, there are some overheating issues that tend to cause issues when writing files... I would agree that the framing may have been off with cinemascopes put in place... Another issue is if you view the LCD screen in a ML Hacked Mode... There can be a slow refresh rate issue too. But, again, it really is a great tool. Maybe a little finicky from time to time, but this camera is well worth the time. It will certainly capture some timeless moments. Enjoy and keep shooting. P.S. Watching your video now.
Yep, I love the camera, not complaining at all :).
Quote from: LEVISDAVIS on December 26, 2013, 08:14:18 AM
Posted a 5 minute video featuring the 50D and the BMPCC. It's not your typical camera comparison video... It's more of a get to know your camera for what it's worth type video. I hope it helps you look further into the power of the camera. Here is the link to the video.
http://youtu.be/1eNuxW5fIew (http://youtu.be/1eNuxW5fIew)
Nice video!
I totally agree with you, 50D produces a very cinematic image. I always will prefer a camera that produces a better image, even with it's issues that the 50D is having.
If you are working the color correction in After Effects, the Color Finesse correction tool has a highlight recovery slider very nice indeed 8)
Quote from: SebaVuye on December 25, 2013, 11:28:15 PM
Thanks
All true. The overexposed area's are the result of ACR and this flickering issue when adjusting Highlights and Shadows sliders :/ I left those two options untouched in ACR because every adjustment resulted in flickering of my image.
Merry Christmas!
Quote from: simulacro on December 26, 2013, 02:17:19 PM
If you are working the color correction in After Effects, the Color Finesse correction tool has a highlight recovery slider very nice indeed 8)
Ah yes, totally forgot about that one! thanks :-)
Thanks for the great work!
I just tried the MLV module, in the newest TL build. I unpacked it with http://www.magiclantern.fm/forum/index.php?topic=7802.0 - is this the proper tool? It did complain about some keywords not recognized (MARK, ...). My newest ACR does read the proper aperture and FL from the DNG files (great!), but doesn't detect the lens automatically. I checked with exiftools, and the CR2 files have these lines:
Lens Type : Canon EF 85mm f/1.2L or Sigma or Tamron Lens
Lens Model : 17-50mm
Lens : 17.0 - 50.0 mm
Lens ID : Sigma 17-50mm f/2.8 OS HSM or Tamron SP 17-50mm f/2.8 XR Di II VC
Lens : 17.0 - 50.0 mm (35 mm equivalent: 26.9 - 79.2 mm)
Whereas the DNG files only had this line:
DNG Lens Info : 17-50mm
But this is not big deal - I can set the lens type manually.
I am not sure if lens correction (vignetting, distortion) works correctly though - the ACR profiles were designed for specific full censor resolution of the camera (I think), and also for a different aspect ratio (3:2). Does anyone know how to modify ACR lens profiles to make them work perfectly with MLV DNG files?
thanks for the video levisdavis, very interesting.
So definition and dynamic range are on BMPCC while colors are on 50D side right?
I would be curious to see a couple of frame grabs from the shot that frames the area under the stairs, it seems full of noise but the compression of youtube makes it look 264-ish.
Can you share two jpegs from it?
The Mosaic Engineering VAF filters made for the 5DII and 7D were designed for the 1080p resolution of their H.264 Canon video output. Does this have any visible impact on their ability to ease the moire effect for raw video which is recorded at a different resolution? Since the 50D had no native video output, my understanding is this new VAF has been specifically designed to work at the 50D's full sensor raw video resolution. If correct, the 50D should have the closest matched VAF for shooting raw video so far made. Looking forward to seeing material shot with the new filter in the new year.
Yes very interesting test. BMPCC definitely has more DR but I definitely like the color from the 50D. It is like a different film emulsion or film stock.
Thank you for taking the time on this LEVISDAVIS. :)
Quote from: LEVISDAVIS on December 26, 2013, 08:14:18 AM
Posted a 5 minute video featuring the 50D and the BMPCC. It's not your typical camera comparison video... It's more of a get to know your camera for what it's worth type video. I hope it helps you look further into the power of the camera. Here is the link to the video.
http://youtu.be/1eNuxW5fIew (http://youtu.be/1eNuxW5fIew)
Checking out the new 50D TL build... Really, really appreciate how the 3X mode is real-time.
Next up is to shoot with MLV. I haven't had a Mac that runs on the latest operating system... But I will say that RawMagic and DaVinci Resolve 10 works in perfect unison if anyone is interested in recording .raw instead of .mlv.
Be sure to give ANDY600's recent LUT a try and/or donate to the cause. That is a really amazing LUT!
Thanks so much.
@ LEVISDAVIS is the 3X mode is 100% real-time now? when I'm recording I still getting kind of strobe affect with some delay.
Thanks for remind us about ANDY600's LUT. I'll give it a try!
Quote from: LEVISDAVIS on December 31, 2013, 03:55:31 AM
Checking out the new 50D TL build... Really, really appreciate how the 3X mode is real-time.
Next up is to shoot with MLV. I haven't had a Mac that runs on the latest operating system... But I will say that RawMagic and DaVinci Resolve 10 works in perfect unison if anyone is interested in recording .raw instead of .mlv.
Be sure to give ANDY600's recent LUT a try and/or donate to the cause. That is a really amazing LUT!
Thanks so much.
Just tested the MLV feature. Already tried the MLV right when 50D was supported and had corrupt frames with my defective Transcend 32GB 1000x card. Send my card to RMA and tried again the MLV with a Transcend 16GB 1000x card and it worked like a charm! No pink frames, great results.
I'm looking forward to shoot with MLV now, but I already have a complicated workflow with RAW:
RAWBatchelor 3.0 (with the raw2dng.exe uploaded by Andy, specially for 50D) with lossy compression using Adobe DNG Converter > After Effects > Color Correction on ACR (no experience with DaVinci Resolve, does the debayering issues got better on these last versions?) > Export to DxHD 10bit 23.976 175mb .mov (since i'm on PC) > Import to Premiere Pro CC, sync with audio > Export to H264 to Youtube.
Feel free to criticize my workflow, I'm very new with raw video :)
Is there a RAWBatchelor for MLV or a alternative? Or a mlv2dng specially designed for the 50D (as Andy uploaded the raw2dng)?
As always, thanks for the great work.
Check here. There should be the same recursive command for PC. http://www.magiclantern.fm/forum/index.php?topic=9679
Quote from: pulsar124 on December 26, 2013, 10:51:58 PM
Thanks for the great work!
I just tried the MLV module, in the newest TL build. I unpacked it with http://www.magiclantern.fm/forum/index.php?topic=7802.0 - is this the proper tool? It did complain about some keywords not recognized (MARK, ...). My newest ACR does read the proper aperture and FL from the DNG files (great!), but doesn't detect the lens automatically. I checked with exiftools, and the CR2 files have these lines:
Lens Type : Canon EF 85mm f/1.2L or Sigma or Tamron Lens
Lens Model : 17-50mm
Lens : 17.0 - 50.0 mm
Lens ID : Sigma 17-50mm f/2.8 OS HSM or Tamron SP 17-50mm f/2.8 XR Di II VC
Lens : 17.0 - 50.0 mm (35 mm equivalent: 26.9 - 79.2 mm)
Whereas the DNG files only had this line:
DNG Lens Info : 17-50mm
But this is not big deal - I can set the lens type manually.
I just had a dng with full info, except it got my lens and focal length wrong.
Shooting on a Rokinon 85mm f1.4 reports as;
50mm lens at f/0 (but it is a manual aperture so f/0 makes sense)
Same thing, not at all a big deal. Just thought I'd put it out there. Will test with other non-Canon lenses to see how it reports.
All the manual adapters can't detect real aperture and you mainly get the adapter name.
Has the ML Grey Preview mode ever worked out the HDMI port for monitoring and framing? Anyone got it working?
WAO !
Now, in the last Andy release, 23,9fps and even 24fps works with 1920x1080 (full HD) continuous !
Double buffering and ML grayscale preview, 1Gb card warming-up option.
1000x 64Gb KomputerBay card (fully tested for uniform high speed >= 1000x and no defects, all this on all the addressable space).
What an achievement !
Many thanks and congratulations to all the people that worked on this ! :o
Hi I picked up 50D testing again.
I have one problem. focus, *, halfshutter and set start RAW or MLV record
How to set it on just one button so I can use set or AFon for ETTR and AF
Thanks
Quote from: dlrpgmsvc on January 04, 2014, 06:18:09 PM
WAO !
Now, in the last Andy release, 23,9fps and even 24fps works with 1920x1080 (full HD) continuous !
To be clear the current TL is 1584x793 (non crop). The full HD crop is what you're referencing.
Quote from: bart on January 04, 2014, 08:09:23 PMI have one problem. focus, *, halfshutter and set start RAW or MLV record
This is set in the video recording menu. Simply disable half shutter to activate recording.
Quote from: dlrpgmsvc on January 04, 2014, 06:18:09 PM
WAO !
Now, in the last Andy release, 23,9fps and even 24fps works with 1920x1080 (full HD) continuous !
Double buffering and ML grayscale preview, 1Gb card warming-up option.
1000x 64Gb KomputerBay card (fully tested for uniform high speed >= 1000x and no defects, all this on all the addressable space).
What an achievement !
Many thanks and congratulations to all the people that worked on this ! :o
Sweet!!
MLV or raw video?
By Full Hd u mean 3x crop mode, right? Since full frame is 1584x1052?
Also, is anyone using the half-shutter button when recording to activate IS, or that feature stopped working? Does it need to be set on in ML menu?
Thx!!
Raw-rec. Not mlv. 3x crop, yes. Dunno about half shutter.
Quote from: dogmydog on January 05, 2014, 03:39:23 PM
Sweet!!
MLV or raw video?
By Full Hd u mean 3x crop mode, right? Since full frame is 1584x1052?
Also, is anyone using the half-shutter button when recording to activate IS, or that feature stopped working? Does it need to be set on in ML menu?
Thx!!
Yes. He meant 3x crop mode.
Half shutter hold works, I've been using it in conjunction with a stabilizer to get pretty good steady shots. Of course, you need a IS lens.
Quote from: dlrpgmsvc on January 04, 2014, 06:18:09 PM
WAO !
Now, in the last Andy release, 23,9fps and even 24fps works with 1920x1080 (full HD) continuous !
Double buffering and ML grayscale preview, 1Gb card warming-up option.
1000x 64Gb KomputerBay card (fully tested for uniform high speed >= 1000x and no defects, all this on all the addressable space).
What an achievement !
Many thanks and congratulations to all the people that worked on this ! :o
BTW, which version are you talking about? I'm guessing that you're talking about RAW Video, not MLV RAW . . . right?
Quote from: dlrpgmsvc on January 06, 2014, 12:33:05 AM
Raw-rec. Not mlv. 3x crop, yes. Dunno about half shutter.
Hey, what page number is Andy's latest Tragic Lantern?
Quote from: menoc on January 06, 2014, 02:36:02 AM
Hey, what page number is Andy's latest Tragic Lantern?
https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
Quote from: Andy600 on January 06, 2014, 03:52:33 AM
https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
Thanks Andy.
Hi guys,
is there anyone that can upload some dngs coming from a 50D, like 50 frames or less?
I'd like to test them in Davinci and see if they have my same problem I explained here http://www.magiclantern.fm/forum/index.php?topic=9826.0 (http://www.magiclantern.fm/forum/index.php?topic=9826.0)
thanks
Quote from: menoc on January 06, 2014, 02:27:12 AM
Yes. He meant 3x crop mode.
Half shutter hold works, I've been using it in conjunction with a stabilizer to get pretty good steady shots. Of course, you need a IS lens.
Thx, menoc! :)
Do I need to switch this feature on the ML menu, or is it just default?
Quote from: dogmydog on January 06, 2014, 12:30:42 PM
Thx, menoc! :)
Do I need to switch this feature on the ML menu, or is it just default?
Switch it on in ML "Movie" Menu. Set the shutter button to "Hold during REC" option.
Quote from: menoc on January 06, 2014, 06:13:09 PM
Switch it on in ML "Movie" Menu. Set the shutter button to "Hold during REC" option.
Thx!! :)
Quote from: p48l0 on January 06, 2014, 08:52:51 AM
Hi guys,
is there anyone that can upload some dngs coming from a 50D, like 50 frames or less?
I'd like to test them in Davinci and see if they have my same problem I explained here http://www.magiclantern.fm/forum/index.php?topic=9826.0 (http://www.magiclantern.fm/forum/index.php?topic=9826.0)
thanks
Uploading some (truly crap) frames to dropbox now. Accidental record while in the storage at work, don't bother downloading unless you are comparing.
https://www.dropbox.com/sh/71ehvj60rep0yha/wd0I3vWWii (https://www.dropbox.com/sh/71ehvj60rep0yha/wd0I3vWWii)
Link should be open, let me know.
Random thought for audio sync. I know the beep from other cameras is out of the question from a hardware stance, but is there a way to make the camera make a significant noise otherwise? After hitting record, would it be possible to force the mirror down then up again, and then start recording to the card? If it were always the same timing when recording began after a mirror lockup, audio sync would be a breeze. I don't have the knowledge to poke around the code and find out, but I was thinking due to the Mirror Lockup options under the Shoot tab including all sorts of options including timing, this might be applicable.
Think the only thing you can do is use a clapper at the moment and the mirror would be a good idea if moving it didn't wear it out.. it would be just like that mirror breaking AF mode
Hi, all, I've started maintaining ML for the 50D, where one goal is to bring it up to parity with TL for the 50D. So, it'd be really useful for me for those of you using TL, especially for RAW video, to try out the latest build of ML – the nightly builds (http://builds.magiclantern.fm/#/) are back! – and let me know what doesn't work as well, or at all, in ML. You can provide feedback in the thread (http://www.magiclantern.fm/forum/index.php?topic=9852.0) I've created. Thanks!
Quote from: ayshih on January 07, 2014, 03:50:28 AM
Hi, all, I've started maintaining ML for the 50D, where one goal is to bring it up to parity with TL for the 50D. So, it'd be really useful for me for those of you using TL, especially for RAW video, to try out the latest build of ML – the nightly builds (http://builds.magiclantern.fm/#/) are back! – and let me know what doesn't work as well, or at all, in ML. You can provide feedback in the thread (http://www.magiclantern.fm/forum/index.php?topic=9852.0) I've created. Thanks!
Thank you very much Ayshih ! Just for me to understand better: do your maintained nightly builds contains all the Andy builds latest features here ? And will also contains more, when new TL features will come up and Andy will not keep updated with his builds ? Many thanks in advance for your clarifications ! ;)
Quote from: dlrpgmsvc on January 07, 2014, 02:19:54 PM
Thank you very much Ayshih ! Just for me to understand better: do your maintained nightly builds contains all the Andy builds latest features here ? And will also contains more, when new TL features will come up and Andy will not keep updated with his builds ? Many thanks in advance for your clarifications ! ;)
I'll still upload 1%'s TL builds for the 50D. I like to live on the edge ;)
The latest TL commits are all about the 7D and sound. All irrelevant for the 50D. I think there was one fix that switches off overlays in .mlv but I haven't compiled yet. I'll upload a new build later today if I get 5 mins.
Good luck Ayshih - it's a lot of work but great to know someone is on it now! I've tried to get my head around porting some TL stuff back to the main repo but it's beyond me. I'm learning though.
Quote from: dlrpgmsvc on January 07, 2014, 02:19:54 PM
Thank you very much Ayshih ! Just for me to understand better: do your maintained nightly builds contains all the Andy builds latest features here ? And will also contains more, when new TL features will come up and Andy will not keep updated with his builds ? Many thanks in advance for your clarifications ! ;)
At least in the short term, the ML nightly builds will still be missing features that are present in the (Andy's) TL build, but I'll be working to bring over everything I can from TL. In the future, as improvements are made in TL, it may take me some time to bring them over to ML. My effort won't be limited to just TL backports, but for the purposes of this thread, it's important for me to get input about what differences, if any, may be keeping you on TL rather than ML.
Quote from: Andy600 on January 07, 2014, 02:34:49 PM
Good luck Ayshih - it's a lot of work but great to know someone is on it now! I've tried to get my head around porting some TL stuff back to the main repo but it's beyond me. I'm learning though.
Hopefully I haven't bitten off more than I can chew! :)
That's a great idea, the porting to ML.
I checked your topic and I was wondering why it's not in the RAW subforum.
Also this current topic should change its title from 50D - 40D to only 50D.
Quote from: riccardocovino on January 07, 2014, 07:49:21 PM
... topic should change its title from 50D - 40D to only 50D.
Done
QuoteUploading some (truly crap) frames to dropbox now.
QuoteLink should be open, let me know.
thanks man, I downloaded your files. They work perfectly in my resolve. So I understand that the problem is my dng's.
I'm encountering a strange error with the first three frames being corrupted with the latest TL build. It happens about the 20% of the time and the MLV is still usable if you delete the black frames.
(http://img.tapatalk.com/d/14/01/09/ajynumu2.jpg)
(http://img.tapatalk.com/d/14/01/09/adytanag.jpg)
Anyone else experiencing this?
Is this a card warm up issue?
Hello djfremen,
I´ve also experienced something similar to what you´re experiencing!
I tried with both MLV and RAW video on the lastest TL build and noticed something like corruped frames on the first 2 or 3 frames on each clip I´ve recorded.
When I checked them in the built-in raw/ MLV video player in cam and they played correctly but when tried to extract the secuence to convert them in DNG secuences
It didnn´t worked and appeared errors so they didn´t converted to DNGs anymore!! :(
Thanks to report your experience and hope this to be corrected and MLV clips with errors to be recoverable!
Cheers!
Asier.
MLV does seem to corrupt the first frame or 2 but just delete them. When converting I don't first convert to legacy .raw. I only dump .mlv straight to DNG using the command 'mlv_dump --dng nameofmlv.mlv' and I've not had any issues except for when I had copied the .IDX files to the same directory. It would then only convert the first frame before throwing an error. So make sure you don't copy the .IDX files from the card.
Hello Andy!!
Thank you very much for your great help!
I´ll do what you say soon to see what happens but must to ask you some questions first.... ;D
How do you delete these problematic first 1 or two frames?
Is that done (deleting frames...) directly in the MLV clip before the conversion to DNG sequences?
How can I do it?
Sorry for so many questions! ;)
Cheers!
Asier.
Delete the dng files perhaps?
Yeah deleting the frames is a solve but the issue is I'm developing a script that calls for the first frame to be imported in ACR so it's a bigger issue for me. Automation needs these first frames intact.
When I try to convert from MLV to DNGs is when the error appears and the only thing I get is one or two DNGs that are corrupted!! :( ...not the whole sequence....so I tought there was a way to delete these problematic frames from the raw MLV clip to allow the conversion app extract the complete DNGs an not to stop at first and get only the corrupted frame only! :-[
That´s why I am asking for that....or may be.... I´m doing something wrong??
I use Windows XP and the lastest version of the MLV2CDNG app and the one that is recomended to 50D users with no results!!
Thanks anyways for your help fellows!
Cheers
Asier.
Hey folks,
I just did a response curve test for 50D in RAW video mode.
Below is the curve that I found. One step is 1/3 degrees. The levels are as displayed in DaVinci Resolve before any adjustment.
Main findings:
1. Usable (my personal view) DR is 9 stops. (Don't kill me on this, I like 50D the way it is).
2. Above the grey point (12.5%) you have 3 and 1/3 degrees of normal contrast, then 1 degree of highlight roll-off.
3. Below the grey point you have 2/3 degrees of normal contrast, then 4 degrees of low-contrast shadow area.
(http://i40.tinypic.com/1s0ec1.jpg)
If you happen to understand Russian, I did a long boring video explaining the curve and what you can do about it:
http://youtu.be (http://youtu.be/CZMd-IxXllg)
Quote from: rommex on January 14, 2014, 04:07:22 PM
Hey folks,
I just did a response curve test for 50D in RAW video mode.
1. Usable (my personal view) DR is 9 stops. (Don't kill me on this, I like 50D the way it is).
Sort of like reversal motion picture film or for still shooting - slide film. (Actually better).
It is good to know the parameters that one should shoot in for best results. Thank you.
Quote from: rommex on January 14, 2014, 04:07:22 PM
Hey folks,
I just did a response curve test for 50D in RAW video mode.
Below is the curve that I found. One step is 1/3 degrees. The levels are as displayed in DaVinci Resolve before any adjustment.
Main findings:
1. Usable (my personal view) DR is 9 stops. (Don't kill me on this, I like 50D the way it is).
2. Above the grey point (12.5%) you have 3 and 1/3 degrees of normal contrast, then 1 degree of highlight roll-off.
3. Below the grey point you have 2/3 degrees of normal contrast, then 4 degrees of low-contrast shadow area.
(http://i40.tinypic.com/1s0ec1.jpg)
If you happen to understand Russian, I did a long boring video explaining the curve and what you can do about it:
http://youtu.be (http://youtu.be/CZMd-IxXllg)
Very cool, rommex!
Do you happen to know how does that curve compares to 7D RAW Video? Or the 5D Mark ii?
Raw is linear on all Canon DSLRs.
This curve is not for raw; you simply revealed the default processing curve (look) in Resolve.
Quote from: dogmydog on January 14, 2014, 09:50:17 PM
Very cool, rommex!
Do you happen to know how does that curve compares to 7D RAW Video? Or the 5D Mark ii?
No, I have no idea about those cameras. If somebody can make measurements...
Quote from: a1ex on January 14, 2014, 10:34:21 PM
Raw is linear on all Canon DSLRs.
This curve is not for raw; you simply revealed the default processing curve (look) in Resolve.
If I draw a curve from the ML built-in spot meter, would that be closer to the truth?
Or if I import those files into Adobe RAW?
UPDATE: I was thinking a little bit about what you wrote. Whatever Canon RAW is inside, I think it is still fair to research how people PERCEIVE the curve in their daily work because this is the form in which it exists for them, and will ever exist.
If you draw a curve with the RAW spotmeter, it will be linear, of course. Just make sure you have the same kind of data on both axis (either both linear or both log, but not mixed).
Quote from: a1ex on January 14, 2014, 11:15:37 PM
If you draw a curve with the RAW spotmeter, it will be linear, of course. Just make sure you have the same kind of data on both axis (either both linear or both log, but not mixed).
With all due respect, it will not be linear. I will give the numbers tomorrow.
50D RAW curve based on ML/TL spot meter:
(http://i40.tinypic.com/6hrnkj.jpg)
X - exposure (1 step is 1/2 EV)
Y - spot meter value
I told you to use the RAW spotmeter, not the YUV one. This graph is Canon's picture style curve.
Quote from: a1ex on January 15, 2014, 01:55:07 PM
I told you to use the RAW spotmeter, not the YUV one. This graph is Canon's picture style curve.
I used spotmeter that is in ML. Is there another, a RAW one? Please explain
9 usable stops? Hmmm think again ::)
Some interesting ML developments happening and should go hand-in-hand with what I am about to release for your raw post workflows. It won't be free but will blow your socks off ;)
You got my attention.
Quote from: rommex on January 15, 2014, 02:11:14 PM
I used spotmeter that is in ML. Is there another, a RAW one? Please explain
Did you look in the spotmeter submenu? One of the choices should be RAW, and the units are in EV.
(I don't know if it actually works in 50D though, maybe Andy can tell)
Quote from: a1ex on January 15, 2014, 03:54:32 PM
Did you look in the spotmeter submenu? One of the choices should be RAW, and the units are in EV.
(I don't know if it actually works in 50D though, maybe Andy can tell)
Yes it works, I use it all the time.
Quote from: a1ex on January 15, 2014, 03:54:32 PM
Did you look in the spotmeter submenu? One of the choices should be RAW, and the units are in EV.
(I don't know if it actually works in 50D though, maybe Andy can tell)
Yep, also found it and it works. But it measures the light in EV. If I put light in EV on X axis, and light in EV in Y axis... Yes I get the straightest line indeed. What else can I get? ;D So you win of course.
But my curve shows the connection between light and the reading from the sensor. We all work with the reading from the sensor in post-production, not with the light itself.
Quote from: Andy600 on January 15, 2014, 02:40:16 PM
9 usable stops? Hmmm think again ::)
Some interesting ML developments happening and should go hand-in-hand with what I am about to release for your raw post workflows. It won't be free but will blow your socks off ;)
Andy please give a hint what is it? My impatience is exploding my mind :) I really need to know that my buying the second 50D and shooting with them both commercial stuff is cool )))))))))
Quote from: rommex on January 16, 2014, 01:05:42 AM
Andy please give a hint what is it? My impatience is exploding my mind :) I really need to know that my buying the second 50D and shooting with them both commercial stuff is cool )))))))))
I read about it on twitter.
https://twitter.com/autoexec_bin
Andy, please don't be mean and tell us! I cant sleep lolol
Wonder if it's for TL only? lol
I would rather not speculate. But the ML tweet indicated the ML release was something to do with the sensor and Andy indicated that his end of the surprise release was something to do with post.
New Codec for the 50d perhaps?
Maybe they figured a way to encoded directly into a QuickTime container. //end speculation.
The ML developments will hopefully gain a little more DR from the sensor but not sure yet if this is coming to the 50D.
My company's product is post-production related and works across a range of cameras, not purely Canon, but ML raw video really benefits from using it. I can't say much more at this stage because it's going out to reviewers over the next week.
@dogmydog - sleep? what is this 'sleep' that you speak of? ;D
I saw that on the "multiples of ISO 160 gaining more DR" or something like that. Everybody should go check that out. Warning, it's pretty techy.
Quote from: rommex on January 15, 2014, 04:43:27 PM
But my curve shows the connection between light and the reading from the sensor. We all work with the reading from the sensor in post-production, not with the light itself.
You curve shows the curve that your post processing software, or Canon picture style is applying to the
linear raw data.
The raw data is always
linear. The connection between light and the reading from the sensor is
linear. Since human eyes are
not linear, a tone curve is applied to make the output more closely resemble what human eyes, see.
Quote from: Audionut on January 16, 2014, 07:28:58 AM
You curve shows the curve that your post processing software, or Canon picture style is applying to the linear raw data.
The raw data is always linear. The connection between light and the reading from the sensor is linear. Since human eyes are not linear, a tone curve is applied to make the output more closely resemble what human eyes, see.
So, from your words, the raw data contains not lighting measurement itself, but log(2) thereof. That's clear.
But if RAW data is only about EV, why such curves from Canon and BMCC (imported in the same way to the same software) differ. Why these sensors have different DR? If RAW data had only linear EV data, all sensors would behave the same way.
Quote from: rommex on January 16, 2014, 10:52:02 AMWhy these sensors have different DR? If RAW data had only linear EV data, all sensors would behave the same way.
All sensors behave differently because they have different pixel well capacities, electronic noise, linear gain, etc, etc.
http://mikeboers.com/blog/2013/11/07/linear-raw-conversions
Quote from: Audionut on January 16, 2014, 11:19:20 AM
All sensors behave differently because they have different pixel well capacities, electronic noise, linear gain, etc, etc.
http://mikeboers.com/blog/2013/11/07/linear-raw-conversions
Noise, sensitivity, calibration and the intended use of the sensor data dictates the curves that are applied by manufacturers and software devs for sometimes not purely technical purposes. Strip away the curves so the readout is linear and they all basically function the same but with +/- sensitivity and noise depending on the sensor.
Quote from: Audionut on January 16, 2014, 11:19:20 AM
All sensors behave differently because they have different pixel well capacities, electronic noise, linear gain, etc, etc.
http://mikeboers.com/blog/2013/11/07/linear-raw-conversions
Thanks!
While being linear in the main section, raw values
do differ in the foot and in the top (judging by dcraw graph). And while some curve is applied in software, these differences just change the form, but they stay.
This is exactly the pivotal point of my curve -- how it ends up and down. And my curve is exactly the thing that thousands of people operate with in their post-production.
So thanks for clarification.
Quote from: Andy600 on January 16, 2014, 06:30:40 AM
.... but not sure yet if this is coming to the 50D.
:-[ :-\ :'(
Quote from: rommex on January 16, 2014, 01:52:24 PM
:-[ :-\ :'(
I haven't looked at the registers but hopefully 1% will get on it ;)
The 50D would probably benefit most from this upgrade because it has the lowest DR of the raw video shooting cameras.
Re: my earlier tease - here's a frame grab from the 50D (crop) with only a hint or NR, a curve and a little sharpening added. Very minimal work to get this. Nice detail?
(http://i.cubeupload.com/avpAAZ.jpg) (http://i.cubeupload.com/avpAAZ.jpg)
click for full size.
Quote from: Andy600 on January 16, 2014, 04:30:12 PM
Re: my earlier tease - here's a frame grab from the 50D (crop) with only a hint or NR, a curve and a little sharpening added. Very minimal work to get this. Nice detail?
wow... was it crop mode? what ISO?
Quote from: Andy600 on January 16, 2014, 06:30:40 AM
The ML developments will hopefully gain a little more DR from the sensor but not sure yet if this is coming to the 50D.
My company's product is post-production related and works across a range of cameras, not purely Canon, but ML raw video really benefits from using it. I can't say much more at this stage because it's going out to reviewers over the next week.
@dogmydog - sleep? what is this 'sleep' that you speak of? ;D
:D
Quote from: rommex on January 16, 2014, 05:11:19 PM
wow... was it crop mode? what ISO?
Looks like crop mode to me.
+1 on the ISO question
This particular area is particularly interesting. It's hell of a dark, it's 50D, and we have such gradations of tonality here...
(http://i42.tinypic.com/mawbc9.jpg)
Yes crop mode (1920x872). ISO 400 on a 28mm at F4. I should have shot at a much higher ISO but the shadow detail is still pretty good.
From my small screen (my phone) I don't see signs of noise.
I'm about to shoot a clip on a beach in the next days.
My worries is the excess of light and DR. Hence some questions:
1) Should I use a low ISO like 100 or try to beam it up to get more DR?
2) Can we get higher shutter speeds then 1/48 when shooting raw or MLV raw? I don't have ND* filters, only a B+W Polarizer I intend to use.
3) Camera heat... I'll use a 7D as a backup, with no magic lantern, shooting H264 if raw on 50D fails. I'm thinking about bringing some ice packs on a box to cool it off when not in use.
Maybe thats a little off topic, but it's 50D and raw video use, so any tips will be highly appreciated :)
You can use the 7D with raw too. The res is only slightly smaller in 1x. The raw still looks good even if upscaled 2x, unlike the H264.
I think with FPS the shutter speeds go to 1/110 or something like that in 24p
Quote from: dogmydog on January 16, 2014, 05:41:28 PM
I'm about to shoot a clip on a beach in the next days.
My worries is the excess of light and DR. Hence some questions:
1) Should I use a low ISO like 100 or try to beam it up to get more DR?
2) Can we get higher shutter speeds then 1/48 when shooting raw or MLV raw? I don't have ND* filters, only a B+W Polarizer I intend to use.
3) Camera heat... I'll use a 7D as a backup, with no magic lantern, shooting H264 if raw on 50D fails. I'm thinking about bringing some ice packs on a box to cool it off when not in use.
Maybe thats a little off topic, but it's 50D and raw video use, so any tips will be highly appreciated :)
Yep, usually lower ISO secures the widest DR available for the sensor.
In my 50D I can set up 1/147s as the shortest shutter speed.
I shot a commercial with 7D H264 in summer 2 years ago. Overheating was huge (
PLEASE HELP!
It's late and I'm slow to find a solution:
I have the latest TL and I used to have this bw playback of raw files. But now I can't find it. Stupid me ((( Tomorrow morning is the shoot....
Quote from: rommex on January 16, 2014, 10:18:26 PM
PLEASE HELP!
It's late and I'm slow to find a solution:
I have the latest TL and I used to have this bw playback of raw files. But now I can't find it. Stupid me ((( Tomorrow morning is the shoot....
Press the play button (top scroll to scroll through takes). Controls for playback are accessed with the PicStyle button. B&W + color is selectable for raw and mlv files.
Quote from: Andy600 on January 16, 2014, 10:23:24 PM
Press the play button (top scroll to scroll through takes). Controls for playback are accessed with the PicStyle button. B&W + color is selectable for raw and mlv files.
I'm doing exactly this, but PicStyle evokes pic styles ((
I have Tragic_Lantern_50D109-Andy600.2013Dec15
Thank you for this swift reply, Andy
It shouldn't if you're in movie mode.
I'll upload a fresh TL build now. I think the shutter readout bug has been fixed :) Can't document the other changes yet but I was recording with it today and seems fine. Try it in a couple of mins and let me know if the problem persists.
edit: Its uploaded
I forgot to load mlv_player ((( I'm a noober >:(
But still, the playback mode turns on when I press Play. When I press PicStyles -- pic style.
I have a commercial shoot tomorrow and really don't want to switch builds. I'll test the new one afterwards.\
THANKS!!!!
Quote from: rommex on January 16, 2014, 10:36:09 PM
I forgot to load mlv_player ((( I'm a noober >:(
But still, the playback mode turns on when I press Play. When I press PicStyles -- pic style.
I have a commercial shoot tomorrow and really don't want to switch builds. I'll test the new one afterwards.\
THANKS!!!!
Delete your config files. Back-up your current settings first if needed.
Quote from: 1% on January 16, 2014, 06:04:08 PM
You can use the 7D with raw too. The res is only slightly smaller in 1x. The raw still looks good even if upscaled 2x, unlike the H264.
I think with FPS the shutter speeds go to 1/110 or something like that in 24p
Quote from: rommex on January 16, 2014, 08:13:18 PM
Yep, usually lower ISO secures the widest DR available for the sensor.
In my 50D I can set up 1/147s as the shortest shutter speed.
I shot a commercial with 7D H264 in summer 2 years ago. Overheating was huge (
Ty for help, 1% and rommex!
I have no idea how to shoot raw with 7d. I'll work on it before the shoot, since ill most likely have overheating. Also, I just bought VAF for my 50D! Should get iron February. Will post results here for you guys :)
7D works just like 50D and the 1x is useable (1728x1152) plus you can do audio. Also waaay less overheating.
does the 50D run any cooler via a battery adapter?
Quote from: robertgl on January 17, 2014, 02:53:10 AM
does the 50D run any cooler via a battery adapter?
Someone posted earlier in the thread that he noted about 3 degrees C less heat when using the battery adapter rather than battery.
Quote from: Andy600 on January 16, 2014, 05:32:54 PM
Yes crop mode (1920x872). ISO 400 on a 28mm at F4. I should have shot at a much higher ISO but the shadow detail is still pretty good.
The image is incredibly clear at F4.
You mentioned higher iso than 400? I shot stuff at 800 and got a lot of noise in my room at night.
But that was with raw not MLV. When the news come out will you let us know it here, Andy?
Or should we keep checking the twitter?
Quote from: 1% on January 17, 2014, 01:18:34 AM
7D works just like 50D and the 1x is useable (1728x1152) plus you can do audio. Also waaay less overheating.
Sure thing, 1%! Does the TL we use here with the 50D works on the 7D also?
I know the installation procedure is different tho.
As usual, Ty all for the amazing job and help!
They are the same code base.
Experienced sustained temp decrease working with A/C adapter. However, the unit will reach normal high-temp operating with continual usage. If I remember correctly, the 50D with an A/C adapter held about a 3 degree C difference for upwards of 30 minutes, but not greater than an hour. I was shooting inside for an interview working with 2 50D cameras.
... We were thinking that the battery grip would also help...
This A/C adapter that I am speaking of is available on eBay for about $10 - 15 US. Thought it would be worth while to purchase two of them and take the second unit and to simply splice the cable right after the A/C to DC converter. It would only be a matter of running the battery shell with positive and negative connection to an external battery source. However, achieving the appropriate voltage and amperage would be another challenge.
I've got a battery grip off amazon (cheapo plastic knockoff that is actually really nice) and I've only had overheating warnings twice. Boston can be a bit cold and I'm usually shooting outdoors, but even with tests inside, or even awhile ago before the winter, I wasn't overheating. I do however get an overheating warning when I connect DSLRcontroller (android app) although I know it is falsely reporting because it happens as soon as I connect, and the camera is cool to the touch.
Quote from: Andy600 on January 16, 2014, 05:32:54 PM
Yes crop mode (1920x872). ISO 400 on a 28mm at F4. I should have shot at a much higher ISO but the shadow detail is still pretty good.
how the hell did you get so good results with 50d...
my problem is that i get so much color noise with this camera, so i was going to sell it ...but this let's me think of a revival for the camera. i am using a quite old november built without mlv record. what would be the advise to get the camera working properly like most of the other users have... ?
still couldn't figure out so far ...
(http://i.imgur.com/I0zmHuul.jpg)
full size: http://imgur.com/I0zmHuu (http://imgur.com/I0zmHuu)
well iso was 2500 i think and f5,6, well i know this is too high for f-stop but the lens couldn't go smaller, damn canon zoom
Avoid shooting with such a high iso. Also, quite a few users on here apply Neat (noise/sharpening) in their editor. Helps quite a bit.
Just finished my paid shoot. It was a little bit of nightmarish...
The camera constantly switched off raw mode and starting recording h264. I was not successful to timely catch that, so some frames were shot totally in h264 in every take ((
The temperature was all the time 45-48C degrees. A lot of errors.
On the exteranl HDMI display there was a black bar near the bottom of the screen -- didn't know where it got...
Still love 50D, but don't know how to deal with these issues. They were totally unpredictable...
What version and how to reproduce the switching off issue?
I have the latest December TL build by Andy.
I only have ideas, not sure about them.
Maybe it's overheating or connecting the external monitor. For some reason the raw_rec module just disappeared. More than that, when I reboot the camera, it doesn't load. The next reboot it's loaded... I had the raw turning off issue earlier on another body -- is it happening only to me? Maybe I do something wrong...
I'll try to push the camera to reproduce the problem. Will give images or video if I happen to catch that.
I'll give it a shot too. It has been working OK for me, the external monitor can reduce write speed but it shouldn't crash anything out.
@rommex - Have you got raw_rec and mlv_rec loaded at the same time?
Quote from: darthvim on January 17, 2014, 08:35:20 PM
how the hell did you get so good results with 50d...
my problem is that i get so much color noise with this camera, so i was going to sell it ...but this let's me think of a revival for the camera. i am using a quite old november built without mlv record. what would be the advise to get the camera working properly like most of the other users have... ?
still couldn't figure out so far ...
(http://i.imgur.com/I0zmHuul.jpg)
full size: http://imgur.com/I0zmHuu (http://imgur.com/I0zmHuu)
well iso was 2500 i think and f5,6, well i know this is too high for f-stop but the lens couldn't go smaller, damn canon zoom
2500 is poor on the 50D. 1600 ISO is the useable upper limit so a faster lens would certainly help. Higher ISOs will produce more noise but I wouldn't recommend deliberately shooting low ISO in low light as it is counterproductive. Lower ISOs may initially look clean but will produce more noise in the shadows and lose detail when 'pushed up' in post rather than a high ISO 'pulled down' in post. Noise can be reduced. Color noise is relatively easy to clean up and noise in the Y channel has a finer grain which can look nice. If you want very clean images get a 5D3.
Quote from: Andy600 on January 18, 2014, 10:59:29 AM
@rommex - Have you got raw_rec and mlv_rec loaded at the same time?
No, I remember they shouldn't be.
BUT I totally remember that I didn't use to have these issues when there was no mlv_pay module loaded..... maybe it is to blame? I'll test....
Quote from: rommex on January 18, 2014, 12:57:30 AM
I have the latest December TL build by Andy.
I only have ideas, not sure about them.
Maybe it's overheating or connecting the external monitor. For some reason the raw_rec module just disappeared. More than that, when I reboot the camera, it doesn't load. The next reboot it's loaded... I had the raw turning off issue earlier on another body -- is it happening only to me? Maybe I do something wrong...
I'll try to push the camera to reproduce the problem. Will give images or video if I happen to catch that.
Rommex, what is the card brand, speed and resolution you're using?
I've been shooting my webseries on the 50D since September with no problems.
Last shoot I got a similar problem with my transcend 16GB 1000x. When I switched card, the camera unloaded the raw_rec module and recorded one take as H264. I turned off and I again and the problem disappeared. My resolution was 1584x896 16:9 and 23.976 fps, no crop.
EDIT: I also monitor video on a HDMI Lilliput 669GL.
@dogmydog, I'm using Komputerbay x1000 32GB and 64Gb
Hey everybody - I'm having a small issue that I'm sure you guys can solve pretty easily.
I'm shooting w/ Tragic Lantern (latest update Andy posted) - everything is working flawlessly except for one small issue with FPS Playback. I seem to have an issue where upon bringing '24fps' footage into Premiere, that it is playing back fast.
I'm shooting w/ FPS Override @ 24fps. When I convert the footage in RAW Magic it shows 24FPS. I bring it into After Effects and transcode to QT/ProRess @ 24FPS - I then bring it into Premiere Pro, in a 24fps timeline, and the playback is fast?! It looks like its close to 24 captured sped up to 30fps.
Can somebody run me through their workflow for 24FPS RAW video on the 50d? I feel like I'm losing my mind. It appears that if I shoot w/ FPS Override off on TL - then export 24fps within AE it works.
Help!
@brandonmarsh: Check your AE project. I'm pretty sure you will find that AE has interpreted your DNG sequence as being at 30fps, which is the default value for image sequences for a new install of AE, if you never change the default. If you select the sequence in the Project panel, you will probably see that it shows as 30fps. Since these sequences are just a series of individual frames, and not a video, you actually have to tell AE what frame rate it should be. As I said, if you don't change the default, AE assumes that all imported image sequences are 30fps. To change the interpretation, right click on the clip in the Project panel>Interpret Footage>Main, and change the frame rate to what you shot it at, which is 24fps.
You can also change the default by going to Edit>Preferences>Import and changing the value for 'Sequence Footage' to whatever you want it to be: if you are always shooting 24fps, then make it 24fps. No matter what the default is set at, you can always change the interpretation of an individual clip with the procedure I describe above. Hope this helps.
Cheers!
Quote from: NedB on January 18, 2014, 11:58:12 PM
@brandonmarsh: Check your AE project. I'm pretty sure you will find that AE has interpreted your DNG sequence as being at 30fps, which is the default value for image sequences for a new install of AE, if you never change the default. If you select the sequence in the Project panel, you will probably see that it shows as 30fps. Since these sequences are just a series of individual frames, and not a video, you actually have to tell AE what frame rate it should be. As I said, if you don't change the default, AE assumes that all imported image sequences are 30fps. To change the interpretation, right click on the clip in the Project panel>Interpret Footage>Main, and change the frame rate to what you shot it at, which is 24fps.
You can also change the default by going to Edit>Preferences>Import and changing the value for 'Sequence Footage' to whatever you want it to be: if you are always shooting 24fps, then make it 24fps. No matter what the default is set at, you can always change the interpretation of an individual clip with the procedure I describe above. Hope this helps.
Cheers!
That was it, thank you so much!
Quote from: rommex on January 18, 2014, 10:55:07 PM
@dogmydog, I'm using Komputerbay x1000 32GB and 64Gb
What resolution were you raw_rec recording in?
Non-crop or 3x crop? What frame rate?
Quote@brandonmarsh: Check your AE project. I'm pretty sure you will find that AE has interpreted your DNG sequence as being at 30fps, which is the default value for image sequences for a new install of AE, if you never change the default. If you select the sequence in the Project panel, you will probably see that it shows as 30fps. Since these sequences are just a series of individual frames, and not a video, you actually have to tell AE what frame rate it should be. As I said, if you don't change the default, AE assumes that all imported image sequences are 30fps. To change the interpretation, right click on the clip in the Project panel>Interpret Footage>Main, and change the frame rate to what you shot it at, which is 24fps.
You can also change the default by going to Edit>Preferences>Import and changing the value for 'Sequence Footage' to whatever you want it to be: if you are always shooting 24fps, then make it 24fps. No matter what the default is set at, you can always change the interpretation of an individual clip with the procedure I describe above. Hope this helps.
Cheers!
Quote from: brandonmarsh on January 19, 2014, 12:27:54 AM
That was it, thank you so much!
One more thing . . . make sure you specify the exact frame rate such as 23.976 for best results. You can enter it manually in after effects. You see, ML gives you the option to set exact FPS. So you should enter the "Actual FPS" in ML RAW video menu. . .
Quote from: menoc on January 19, 2014, 01:12:49 AM
One more thing . . . make sure you specify the exact frame rate such as 23.976 for best results. You can enter it manually in after effects. You see, ML gives you the option to set exact FPS. So you should enter the "Actual FPS" in ML RAW video menu. . .
I second this advice. Also, you can change the default in preferences always to import at 24FPS.
Quote from: dogmydog on January 19, 2014, 01:05:42 AM
What resolution were you raw_rec recording in?
Non-crop or 3x crop? What frame rate?
it was 25FPS, no-crop 1586x8... (standard max res for 50D)
When you guys are using the latest tragic lantern update, is greyscale preview running smoothly for you when shooting in crop mode? Mine has a severe lag when recording on my 1000x card, someone mentioned that they got it to work in real time.
Also, anyone else getting a black bar along the side of their crop-mode clips? it even happens when I'm using greyscale preview.
Quote from: FilmPerson on January 20, 2014, 01:02:39 AM
When you guys are using the latest tragic lantern update, is greyscale preview running smoothly for you when shooting in crop mode? Mine has a severe lag when recording on my 1000x card, someone mentioned that they got it to work in real time.
Also, anyone else getting a black bar along the side of their crop-mode clips? it even happens when I'm using greyscale preview.
You sure the person you're referencing wasn't talking about mlv_play? Playback in grayscale of .mlv videos runs smoothly (with great reduction in detail) as opposed to colour playback, which is rich in detail, but very choppy.
Recording in grayscale preview is very choppy for me.
I set preview to AUTO for recording. You can frame shots with x5 in low res and set focus with x10 then just 'imagine' the rest of the frame when recording with the grayscale, realtime 5x preview.
any news about expanding DR for 50D?
btw, I'm doing CC'ing of the footage I shot for a commercial for a major financial institution of Ukraine. I'm extremely pleased with the gradebility. keying, refinement of shadows -- everything is quite astonishing. even considering I was shooting at 320 ISO.
Quote from: rommex on January 24, 2014, 04:16:40 PM
any news about expanding DR for 50D?
btw, I'm doing CC'ing of the footage I shot for a commercial...
...everything is quite astonishing. even considering I was shooting at 320 ISO.
Alex commented that the DR Upgrade on the 50D was definitely a lower number/ percentage than that found on the 5D3.
We'll see.
Please let us know if you post (if you are able) any footage from your shoot.
Quote from: rommex on January 24, 2014, 04:16:40 PM
any news about expanding DR for 50D?
The latest data (http://www.magiclantern.fm/forum/index.php?topic=10111.msg98051#msg98051) shows small improvements to dynamic range: ~0.25 EV at ISO 100, and about half that at higher ISOs.
Quote from: ayshih on January 26, 2014, 09:49:09 AM
The latest data (http://www.magiclantern.fm/forum/index.php?topic=10111.msg98051#msg98051) shows small improvements to dynamic range: ~0.25 EV at ISO 100, and about half that at higher ISOs.
thanks so much, ayshih!
in your opinion, as you know better this topic for sure, are there prospects that this DR delta will improve, or basically that is it?
My guess is that this will probably be it. While I can't rule out the discovery of additional levers to manipulate, it seems rather unlikely.
Quote from: ayshih on January 26, 2014, 10:07:33 AM
My guess is that this will probably be it. While I can't rule out the discovery of additional levers to manipulate, it seems rather unlikely.
right. is this going to be integrated in the future TL / ML nightly / stable release?
Presumably yes, but as is the way with such things, only "when it's ready".
Quote from: ayshih on January 26, 2014, 06:45:43 PM
Presumably yes, but as is the way with such things, only "when it's ready".
thanks a lot. a good news upon good news )
"CMOS/ADTG/Digic register investigation on ISO" work on raw ? or only for photo ?
ISO 80 ( 11.339 DR ) in RAW its good :)
It may, still brand new and not all the way worked for photo.
Quote from: Andy600 on January 21, 2014, 06:14:48 PM
I set preview to AUTO for recording. You can frame shots with x5 in low res and set focus with x10 then just 'imagine' the rest of the frame when recording with the grayscale, realtime 5x preview.
Hi Andy,
Can you share your ML config file? I'll add a config with ML50D_ANDY_STYLE
I'm struggling with the 50d. I can't get it to work in a convenient way.
Thanks
Quote from: bart on January 29, 2014, 01:21:24 PM
Hi Andy,
Can you share your ML config file? I'll add a config with ML50D_ANDY_STYLE
I'm struggling with the 50d. I can't get it to work in a convenient way.
Thanks
Sure. I'll upload when I get home. I have mlv set-up on on C1 and Dual ISO on C2.
Hi all,
Just about to update my cards from a September-ish build (worked so well I haven't felt the need to) but had to use my CF's on a C300 shoot the other day so my hands been forced.....just wondering what the deal is with .raw vs .mlv on the 50D specifically? Smaller file sizes or anything like that?
Cheers
Quote from: father_v on January 29, 2014, 04:18:39 PM
Hi all,
Just about to update my cards from a September-ish build (worked so well I haven't felt the need to) but had to use my CF's on a C300 shoot the other day so my hands been forced.....just wondering what the deal is with .raw vs .mlv on the 50D specifically? Smaller file sizes or anything like that?
Cheers
Better metadata and Tony Beccar just released his new mlv batch converter (PC only) which makes it a no-brainer now. http://www.magiclantern.fm/forum/index.php?topic=10198.0
Alas, purely Mac! So .mlv does shoot more compressed to the cards? Or just after conversion? Sorry, I have had a look. This forum's a labyrinth if you have no coding chops.
Quote from: father_v on January 29, 2014, 04:42:21 PM
Alas, purely Mac! So .mlv does shoot more compressed to the cards? Or just after conversion? Sorry, I have had a look. This forum's a labyrinth if you have no coding chops.
I think there is a batch script for .mlv on the mac?
.mlv is the same, uncompressed format as .raw but adds metadata and you can record audio (but not on the 50D because we don't have a mic or input for a mic).
Quote from: Andy600 on January 29, 2014, 06:09:24 PM
I think there is a batch script for .mlv on the mac?
.mlv is the same, uncompressed format as .raw but adds metadata and you can record audio (but not on the 50D because we don't have a mic or input for a mic).
Indeed there is, everything can be found in this thread (http://www.magiclantern.fm/forum/index.php?topic=9731.0).
Otherwise users can search for "recursive0.4.command" :)
Hey guys sorry if this has been asked before but I just got a 50D the other day (200 bucks from a photographer friend).
2 questions. Should I be using raw_rec or mlv? I've been suing mlv just to mess around so far.
Also, when go from iso 3200 to 6400 (h1) I don't see a difference on the screen? Same with h2. They look like 3200. Is 3200 the limit for video? I had seen one of the first test videos was supposedly shot on H1 or H2.
Thanks!
MLV is your better alternative for all Canon's alike. However the 50d performs flawlessly on .raw. Thinking that MLV will outlast .raw in the "future scheme of things."
ISO 3200 is all the 50d wrote... When shooting raw you are not processing the signal. ISO 6400 and 12800 are digital / processed algorithms for the 50d... After further review that "original ISO 6400 test shoot" was in fact shot at 3200. Your discovery of H1 and H2 ISO is spot on! Pretty cool, huh?
Can anyone recommend a portable device for recording with acceptable quality?
Quote from: Luzestudio on January 30, 2014, 09:29:34 AM
Can anyone recommend a portable device for recording with acceptable quality?
Audio or what?
Zoom H4n and Zoom H6 is used a lot.
Quote from: LEVISDAVIS on January 30, 2014, 08:59:38 AM
MLV is your better alternative for all Canon's alike. However the 50d performs flawlessly on .raw. Thinking that MLV will outlast .raw in the "future scheme of things."
ISO 3200 is all the 50d wrote... When shooting raw you are not processing the signal. ISO 6400 and 12800 are digital / processed algorithms for the 50d... After further review that "original ISO 6400 test shoot" was in fact shot at 3200. Your discovery of H1 and H2 ISO is spot on! Pretty cool, huh?
I should add that if you're Mac centric, the support to convert the mlv to dng frames is limited - there's better support on the windows platform. Also, I'm not sure if it's my process or the utilities but my mlv dng's didn't play nice with Adobe Camera RAW, I was still getting some magenta cast which I do not get with regular RAW dng's . . . It may have something to do with the metadata, but I haven't been able to figure it out.
Quote from: menoc on January 30, 2014, 03:29:56 PM
I should add that if you're Mac centric, the support to convert the mlv to dng frames is limited - there's better support on the windows platform. Also, I'm not sure if it's my process or the utilities but my mlv dng's didn't play nice with Adobe Camera RAW, I was still getting some magenta cast which I do not get with regular RAW dng's . . . It may have something to do with the metadata, but I haven't been able to figure it out.
To quote myself ... MLV support is fine in OS X.
Quote from: PressureFM on January 29, 2014, 08:36:50 PM
Indeed there is, everything can be found in this thread (http://www.magiclantern.fm/forum/index.php?topic=9731.0).
Otherwise users can search for "recursive0.4.command" :)
Quote from: PressureFM on January 30, 2014, 04:05:32 PM
To quote myself ... MLV support is fine in OS X.
Pressure, I understand what you're saying. "Fine" is probably the right word, but until there's a "RAWMagic" type utility for MLV Raw, the non-techies out there are going to find the current process to convert MLVs a bit difficult.
Quote from: PressureFM on January 30, 2014, 01:11:22 PM
Audio or what?
Zoom H4n and Zoom H6 is used a lot.
. . . TASCAM DR-40, JuicedLink pre-amp, and Audio Technica AT897 shotgun mic. That's my setup.
Quote from: LEVISDAVIS on January 30, 2014, 08:59:38 AM
MLV is your better alternative for all Canon's alike. However the 50d performs flawlessly on .raw. Thinking that MLV will outlast .raw in the "future scheme of things."
ISO 3200 is all the 50d wrote... When shooting raw you are not processing the signal. ISO 6400 and 12800 are digital / processed algorithms for the 50d... After further review that "original ISO 6400 test shoot" was in fact shot at 3200. Your discovery of H1 and H2 ISO is spot on! Pretty cool, huh?
This info on ISOs is pretty cool indeed!
Since there's this MLV batch processing now, I'll probably switch to MLV in my next shoot :)
What are the flaws of the MLV compared to raw now?
From my tests so far, only the first 3 pink frames.
Quote from: dogmydog on January 30, 2014, 08:00:48 PM
This info on ISOs is pretty cool indeed!
Definitely useful!
Quote from: dogmydog on January 30, 2014, 08:00:48 PMFrom my tests so far, only the first 3 pink frames.
This isn't every time. For me, it's like 20% pink / corrupted frames (sometimes as many as 5). This is a big deal because if you write an app to process / convert DNG it will reject the entire string of images. Hopefully this can be addressed in future updates.
Hi, guys
Where is show true shutter speed? In LV or ML menu? Thanks!
(http://i.imgur.com/v0dVm75.png?1)
(http://i.imgur.com/mRCMLA0.png?1)
Looks like you are using an older build? That was a bug and it was fixed a couple of weeks ago.
Download the latest nightly: http://builds.magiclantern.fm/#/ (http://builds.magiclantern.fm/#/)
or
Tragic Lantern 50D users - I've just uploaded the latest Tragic Lantern 50D build: https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
WARNING! - I haven't tested this build thoroughly so only use it if you know what you are doing.
Quote from: Andy600 on February 01, 2014, 03:59:05 PM
Looks like you are using an older build? That was a bug and it was fixed a couple of weeks ago.
Yes, thanks!
Quote from: Andy600 on February 01, 2014, 03:59:05 PM
Looks like you are using an older build? That was a bug and it was fixed a couple of weeks ago.
Download the latest nightly: http://builds.magiclantern.fm/#/ (http://builds.magiclantern.fm/#/)
or
Tragic Lantern 50D users - I've just uploaded the latest Tragic Lantern 50D build: https://bitbucket.org/andy600/tl50d/downloads (https://bitbucket.org/andy600/tl50d/downloads)
WARNING! - I haven't tested this build thoroughly so only use it if you know what you are doing.
Tyvm, Andy! What are the new features of this build compared to the jan 14th?
Quote from: dogmydog on February 01, 2014, 06:32:23 PM
What are the new features of this build compared to the jan 14th?
The two items I'd highlight are:
- The indexing of the 50D's raw buffer was incorrect, which was throwing off RAW histograms and zebras and slightly throwing off black-level estimation.
- The file manager has much better performance for directories with many files.
This is not an exhaustive list; there have been other bug fixes and tweaks.
Edit: oh, there was also the fix to the Calibration Illuminant (see http://www.magiclantern.fm/forum/index.php?topic=10119.0 (http://www.magiclantern.fm/forum/index.php?topic=10119.0))
:) Thanks Andy!
Hey guys,
Thx to the amazing tips and TL updates, I present you my latest raw video.
It was shot on a 50D with Canon 17-55mm 2.8 USM IS (handheld shots holding half-shutter) and Canon 70-200mm 2.8 USM IS II.
I also used a polarizer filter 77mm from B+W.
CF cards were Lexar 32GB 1000x, Transcend 16GB 1000x, Transcend 32GB 1000x and Sandisk 16GB 60mb/s
Software:
Tragic_Lantern_50D109-Andy600.2013Dec15_Histogram_fix_&_MLV_Improvements
raw_rec module only, 1586x896, 16:9, 23.967 fps, Exact FPS, GD Off, Dialog Timers Off
Post:
Unloaded raw files by RAW Batchelor 3.0 Beta (lossy, Adobe DNG Converter)
CC in ACR in After Effects CC
Export to Premiere CC by DxHD 175mb/s 23.976 1080p
Coded in H264 Youtube Full HD Premiere CC preset
Does anyone knows if the issue with cropmarks on external HDMI monitors are fixed in TL? I'm having a hard time monitoring on my sucky Lilliput 669GL 7'' external monitor lol
http://www.magiclantern.fm/forum/index.php?topic=8518.0
As always, ty for help!
There was a fix but I haven't had time to check it.
What's the difference b/w Magic and Tragic Lantern on the 50D?
I shot this https://vimeo.com/85953508
with the v2.3.NEXT.2014Jan28.50D109 Build. Am I better off using TL?
My card started acting up once I got 58GB used up on a 64GB KomputerBay 1000x card. Also white balance may not be registering in the RAWs I have to manually set it in ACR from 4800K. Also I have no idea how raw histogram works it looks the same as regular histograms to me :(
Hello guys,
After a period of shooting H264, because couldnt handle data management of RAW, I now upgraded my PC Rig and can manage to work with RAW.
I have been away from the forum for a considerable amount of time, so, I have one question about the new TLbuild:
Can I manage to give names, IN camera, to the shots that I will be doing?
I used the shane hurlbuts method for h264:
(http://www.youtube.com/watch?v=kF8SnMWGYD0&list=TLQ9JYOjl0n5YubmSjHvnYnCp9izv-A04u)
Its there a way to do this IN camera with the new build?
It is very usefull.. It would be very nice to add this to a future build, if it is not yet in the most recent one!
Think you all very much
Quote from: joaomoutinho on February 06, 2014, 04:17:23 PM
Hello guys,
After a period of shooting H264, because couldnt handle data management of RAW, I now upgraded my PC Rig and can manage to work with RAW.
I have been away from the forum for a considerable amount of time, so, I have one question about the new TLbuild:
Can I manage to give names, IN camera, to the shots that I will be doing?
I used the shane hurlbuts method for h264:
(http://www.youtube.com/watch?v=kF8SnMWGYD0&list=TLQ9JYOjl0n5YubmSjHvnYnCp9izv-A04u)
Its there a way to do this IN camera with the new build?
It is very usefull.. It would be very nice to add this to a future build, if it is not yet in the most recent one!
Think you all very much
Use the MLV module. You can tag .mlv in camera and this: http://www.magiclantern.fm/forum/index.php?topic=10198.0 (http://www.magiclantern.fm/forum/index.php?topic=10198.0) will let you add more meta when processing to DNGs.
Oh... MLV is now working? NICE!! Im going to experiment on it.
The workflow changed with the MLV module? Or can I go straight from the RAW workflow?
really nice this news!
It works for me :)
Use the new app I linked to convert your mlv files. There are a couple more settings you can change in the mlv module but I don't have my camera with me to tell you what I use. I think the default settings should work ok. Just make sure to only enable one raw module at a time.
Andy, later when you have the camera with you, share the specs for me to try out...
In the crop mode, I can only record like, 20secs or so... It used to be working flawlessly with the other "build". Any ideas?
Although, it is pretty nice to be able to see the video on spot! =)
And I dont know, but in the MLV menu - Tag:Text, I cant manage to work with this, I input a name and I go out of this rotation menu an it is always "none" . Tag:Take turns always "off" to... Dunno =S
Ah, and in the "Magic Lantern RAW converter 1.6" I ran the app for 20minutes and the progress was 0%.
Not sure what I am doing wrong, but I clearly need some advise to adapt to this MLV workflow...
PM'd you ;)
Quote from: joaomoutinho on February 06, 2014, 06:12:43 PM
Andy, later when you have the camera with you, share the specs for me to try out...
In the crop mode, I can only record like, 20secs or so... It used to be working flawlessly with the other "build". Any ideas?
Although, it is pretty nice to be able to see the video on spot! =)
And I dont know, but in the MLV menu - Tag:Text, I cant manage to work with this, I input a name and I go out of this rotation menu an it is always "none" . Tag:Take turns always "off" to... Dunno =S
Ah, and in the "Magic Lantern RAW converter 1.6" I ran the app for 20minutes and the progress was 0%.
Not sure what I am doing wrong, but I clearly need some advise to adapt to this MLV workflow...
Quote from: Andy600 on February 06, 2014, 06:23:51 PM
PM'd you ;)
Andy, please share it on the fórum as well :).
I'm about to start shooting MLV next monday and I'd very much appreciate any advice whatsoever.
Hi!
Im making some test in RAW before jumping to real production.
In this clip something happens with the green, the light intensity is "vibrating".
Anyone knows what causes this?
I batch edited the dng in Lightroom and imported them in Premiere as image sequence.
Is this noise?
https://www.dropbox.com/s/iqg48759hx5iyqm/greens.mp4
(Posted in Dropbox, youtube compress the video so much...)
Haven't seen the video (upload to Vimeo or YT please) but it's either that your frame rate isn't set correctly for your country (use 25p for Spain) or it's caused by Lightroom and ACR. Auto WB, Shadow/highlight recovery and a few other things in LR and ACR are 'intelligent' and will change depending on luminance. It's not intended for processing sequential video frames but you can do something about it. See my signature ;)
Quote from: Andy600 on February 07, 2014, 02:11:22 PM
Haven't seen the video (upload to Vimeo or YT please) but it's either that your frame rate isn't set correctly for your country (use 25p for Spain) or it's caused by Lightroom and ACR. Auto WB, Shadow/highlight recovery and a few other things in LR and ACR are 'intelligent' and will change depending on luminance. It's not intended for processing sequential video frames but you can do something about it. See my signature ;)
Here is uploaded to youtube: http://www.youtube.com/watch?v=gM-iULAzGpg
It's definitely flickering caused by Lightroom.
hi guys!
good to see still movement in the develepment and some final touches.
got some new footage. haven´t changed ML on my cards for months. it just works ;-)
aliasing in the last shot is horrible. but, nothing is perfect...
shot with sigma apo 70-200 mm 2.8 (crop mode up to 600mm. that´s why it´s sometimes a little shaky) and canon 28 mm 2.8
Is Dual ISO working for video with the 50D. I've had issues getting it to work and was told that it may not be working yet for video. Any truth to this?
No way to make it work for video. The registers don't work the same. Same for 5DII and probably 7D
Quote from: crash-film on February 09, 2014, 03:03:27 PM
hi guys!
good to see still movement in the develepment and some final touches.
got some new footage. haven´t changed ML on my cards for months. it just works ;-)
aliasing in the last shot is horrible. but, nothing is perfect...
shot with sigma apo 70-200 mm 2.8 (crop mode up to 600mm. that´s why it´s sometimes a little shaky) and canon 28 mm 2.8
Looks great! Its a shame how youtube sometimes spoils the quality by his strong compression. Have you tried with Vimeo?
I see developers have come with a solution to pink frames:
http://www.magiclantern.fm/forum/index.php?topic=10443
Are pink frames the same as corrupted frames (like the 3 first ones in 50D MLVs)?
Or another issue? Also, will this fix work with 50D footage as well?
Thx!
We shall see.
Quote from: 1% on February 12, 2014, 03:50:46 AM
We shall see.
Sorry for noobing, but are "pink frames" the same as "corrupted frames" we get on the 3 first frames in 50D MLVs? Or another issue?
In 1% we trust :). Ty for your patience.
Supposed to stop GD related pink frames and silent pic corruption.
Hi Guys, Thanks so much for all your hard work, i've been watching and reading for a few years now, i've never felt the need to register because I just search the forum for an answer to my question, but in this case my searching has failed, one thread came close to answering, i didn't want to post on zombie threads or make new ones so i'll ask here.
I've been really digging 50d crop mode, so much so that I occasionally use lenses that don't cover the sensor but look nice as crops.
my problem has arisen trying to use an old B4 mount TV lens, i've got it mounted properly and it looks good, but I can't for the life of me work out how to (or if i can) properly centre the focus box. I'm ok cropping out a small vignette in post, but obviously i'm loosing the wide end of my lens, and if I use the nice smooth servo zoom it obviously zig zags off at an angle because the crop isn't centered to the lens. I've tried digital dolly but the joystick just stops working.
I've seen other threads which allude to the box never getting centered but I can't work out what the actual deal is.
I know its a strange thing to want to do, but can anyone help me?
Cheers
PS I don't seem to have this problem on the 550d, but obviously I can only shoot 15 frames before the buffer fills.
Quote from: 1% on February 09, 2014, 07:27:02 PM
No way to make it work for video. The registers don't work the same. Same for 5DII and probably 7D
So Dual ISO video is a lost cause on the 50D? No possible way it could ever work?
maybe something else similar to dual ISO but the way it works now, no.
@ Jackeatley
Hi, I'm curious to know how you mounted the B4 lens, 'cause I have a fuji zoom lens and would like to work with it!
Quote from: riccardocovino on February 13, 2014, 01:06:28 PM
@ Jackeatley
Hi, I'm curious to know how you mounted the B4 lens, 'cause I have a fuji zoom lens and would like to work with it!
Adapter from a ebay store from Singapore.
http://www.ebay.co.uk/itm/181227040910
Obviously works but i'm having a issue with centering the crop, known to work well on the HD crop mode on the 600d.
Quote from: Andy600 on February 06, 2014, 04:27:26 PM
Use the MLV module. You can tag .mlv in camera ....
Hi Andy,
thanks for your invo about the MLV workflow. I just tried it today.
MLV Converter is a very good program. Didn't find any problems in the workflow.
However I couldn't find how to tag clips in-camera. I was clicking the "free text" but somehow didn't figure out how to actually enter the tag.
Could you please help, as always? )
THNX
UPDATE Also in your latest TL build GD suffers in MLV recording. Keeping GD On, if you record MLV video, everything is fine. But then switch RAW off, record some h.264, and switch RAW back on, making sure GD is ON. GD will be deteriorated -- some info is gone, the black upper stripe is gone.... raw_rec behaves well in this regard.
Quote from: Jackeatley on February 13, 2014, 09:46:40 PM
Adapter from a ebay store from Singapore.
http://www.ebay.co.uk/itm/181227040910
Obviously works but i'm having a issue with centering the crop, known to work well on the HD crop mode on the 600d.
I don't have the 600d so I have no idea if the crop factor is the same of the 50D raw crop mode. If it's the same and 2/3" lenses cover it without vignetting that's great!
Unfortunatly the seller you pointed doesn't ship to italy, and other canon/B4 adapters start from 200 euros!
Quote from: Jackeatley on February 13, 2014, 09:46:40 PM
Adapter from a ebay store from Singapore.
http://www.ebay.co.uk/itm/181227040910
Obviously works but i'm having a issue with centering the crop, known to work well on the HD crop mode on the 600d.
Can you post some footage to see how the lens behaves with the crop? apart from curiosity, thniking about getting one of those lenses.
I tried centering the crop in liveview with no success. I did a test with an image on the center of the frame. Without moving the focus box with the "q" toggle, leaving it on the center of the frame, if you hit record, the image isn't centered; it's partially off-center to the left. Then I moved the focus box with the toggle 5 times to the left, hit record, and the image appears in the same spot than the centered one. The last one, from the center of the image, moved the rectangle with the toggle 5 times to the right and this time the footage looks off-center to the right. Funny.
I can post some DNGs tomorrow when its light again in the cold dark UK.
But what i can tell you is that if we can centre the crop the wide end would cover 2000x1080, but at present it causes a hefty vignette at either side, my lens a canon 9.5-143mm will however cover this at 130mm and up with no vignette.
Highest res I can currently get at the wide end is 1728x972 but you can work at single focal lengths only, any zooming and the centering causes the lens to zoom off centre and looks very nasty, zooming out is sometimes OK but doesn't really look right.
But for long tele and wide crop mode it works well for now, and you get a fairly compact cine style lens thats parfocal and constant aperture, normally quick too, mines f1.8. Slight downside being that its really only useful from f3 down due to the softness and aberrations.
It would be interesting to see the DOF at f3 at the wide side of the lens
Similarly to @Jackeately I remember 16mm lenses being briefly covered in this forum, but I can't find. anything definitive for use in crop mode. I know that flange distance might be an issue. Anyone have anything definitive? Is it theoretically possible to use a wide or moderately wide16mm lens in crop mode on the 50d with an adaptor?
Here's some random shooting footage, if anybody wants to look at some:
http://vimeo.com/87060692
@brandonmarsh I really like the filmic quality of your footage. What was your workflow?
Camera - > RawMagic -> AE (ProRess 422) - > Premiere -> Export
I did color correcting w/ Adobe Camera RAW in After Effects. Thanks!
Quote from: lionelp on February 19, 2014, 03:17:20 AM
Similarly to @Jackeately I remember 16mm lenses being briefly covered in this forum, but I can't find. anything definitive for use in crop mode. I know that flange distance might be an issue. Anyone have anything definitive? Is it theoretically possible to use a wide or moderately wide16mm lens in crop mode on the 50d with an adaptor?
S16 PLs on an adapter would work fine, 16mm PLs would probably work fine (Coverage wise). If there was a issue with the rear flange being too long, there are modded PL mount 50ds around that where used for timelapses and production stills. http://www.fdtimes.com/wp-content/uploads//2009/09/canonpl_pic_0403_031web.jpg
C or D mount is obviously a no-go due to registration distance, but work well on the EOS-M.
Hi,
The anamorphic preview on the TL seems to be usable onscreen only. Is there any way to enable the anamorphic preview on an external monitor?
Display filters don't want to work with HDMI on the older cams... btw anamorphic was busted for the last couple of days in branch. Should be good now.
Ah... I see. Thanks for the reply 1%!
Quote from: brandonmarsh on February 19, 2014, 03:08:27 PM
Camera - > RawMagic -> AE (ProRess 422) - > Premiere -> Export
I did color correcting w/ Adobe Camera RAW in After Effects. Thanks!
Try de-bayering in Davinci Resolve. That ugly moire on the building will be less prominent. AE produces a lot of artefacts.
Quote from: rommex on February 20, 2014, 08:14:18 AM
Try de-bayering in Davinci Resolve. That ugly moire on the building will be less prominent. AE produces a lot of artefacts.
Resolve can be pretty bad when it comes to debayering non-crop video from the 50D. It leaves mosaic artifacts in highlights. You can reduce moire quite well in ACR using the adjustment brush or if it's really bad on some shots I would suggest using Raw Therapee with AMaZE demosaicing and output to 16bit TIFF.
Quote from: Andy600 on February 20, 2014, 02:51:54 PM
Resolve can be pretty bad when it comes to debayering non-crop video from the 50D. It leaves mosaic artifacts in highlights. You can reduce moire quite well in ACR using the adjustment brush or if it's really bad on some shots I would suggest using Raw Therapee with AMaZE demosaicing and output to 16bit TIFF.
After Resolve 10 release, I re-rendered lots of footage that in AE showed unacceptable aliasing. In 90% of cases, aliasing was significantly reduced. And I don't shoot cropped.
Quote from: rommex on February 20, 2014, 02:56:13 PM
After Resolve 10 release, I re-rendered lots of footage that in AE showed unacceptable aliasing. In 90% of cases, aliasing was significantly reduced. And I don't shoot cropped.
Aliasing and moire are different things.
Sorry for the duplicate post. Trollville on my part.
@Jackeately
Quote from: lionelp on February 20, 2014, 03:56:35 PM"S16 PLs on an adapter would work fine,....."
Thanks for the help.
Quote from: Andy600 on February 20, 2014, 02:51:54 PM
Resolve can be pretty bad when it comes to debayering non-crop video from the 50D. It leaves mosaic artifacts in highlights. You can reduce moire quite well in ACR using the adjustment brush or if it's really bad on some shots I would suggest using Raw Therapee with AMaZE demosaicing and output to 16bit TIFF.
I have found ACR to be best when reducing moire and ISO noise. Lately, I've been doing it in Lightroom since it has the same engine and better handling of multiple DNGs.
Quote from: menoc on February 20, 2014, 10:03:14 PM
I have found ACR to be best when reducing moire and ISO noise. Lately, I've been doing it in Lightroom since it has the same engine and better handling of multiple DNGs.
hi menoc, thanks for your note. honestly, I watch your posts and value them 8) what version of ACE do you use? I may have an older version...
Hi, i'm new with ML raw and i'm having an problem. When i'm recording MLV raw (latest build) with my 50D and post processing this video in After Effects CS6 and then play this video in any player the video plays too fast. Like it's playing at 30fps instead of 24fps.
This is my workflow:
ML settings: MLV rec module enabled, FPS override ON (Exact fps, 24.000), GD On (only cropmks).
AE: Import DNG sequence (framerate 24fps) -> Composition (framerate 24fps) -> Render H.264
I have only a slow cf card at the moment so I can only record for 15 seconds but frame skipping is off.
Does anyone know what's happening here?
Ps thanks to all the developers working on this nice piece of software!
Quote from: BartvR on February 21, 2014, 03:50:02 PM
Hi, i'm new with ML raw and i'm having an problem. When i'm recording MLV raw (latest build) with my 50D and post processing this video in After Effects CS6 and then play this video in any player the video plays too fast. Like it's playing at 30fps instead of 24fps.
This is my workflow:
ML settings: MLV rec module enabled, FPS override ON (Exact fps, 24.000), GD On (only cropmks).
AE: Import DNG sequence (framerate 24fps) -> Composition (framerate 24fps) -> Render H.264
I have only a slow cf card at the moment so I can only record for 15 seconds but frame skipping is off.
Does anyone know what's happening here?
Ps thanks to all the developers working on this nice piece of software!
AE likes to import footage at 30fps it seems. You have to manually select the sequence and click the interpret footage button then type in 24fps in the frame rate box. I assume you did this already but just wanted to make sure. Not sure what else would be causing the issue.
Question for anyone out there, do yo guys use the absolute zero sharpness feature in the video hacks menu? I wonder if it can produce better quality for sharpening in post instead of inside the camera. I already have the pic style set to 0 sharpness but I noticed this setting in Magic Lantern says its below canons 0 level. Yay or nay?
Quote from: impulse921 on February 21, 2014, 11:46:00 PM
AE likes to import footage at 30fps it seems. You have to manually select the sequence and click the interpret footage button then type in 24fps in the frame rate box. I assume you did this already but just wanted to make sure. Not sure what else would be causing the issue.
Question for anyone out there, do yo guys use the absolute zero sharpness feature in the video hacks menu? I wonder if it can produce better quality for sharpening in post instead of inside the camera. I already have the pic style set to 0 sharpness but I noticed this setting in Magic Lantern says its below canons 0 level. Yay or nay?
yeah I already set the framerate to 24fps indeed..
Quote from: impulse921 on February 21, 2014, 11:46:00 PM
AE likes to import footage at 30fps it seems. You have to manually select the sequence and click the interpret footage button then type in 24fps in the frame rate box. I assume you did this already but just wanted to make sure. Not sure what else would be causing the issue.
Question for anyone out there, do yo guys use the absolute zero sharpness feature in the video hacks menu? I wonder if it can produce better quality for sharpening in post instead of inside the camera. I already have the pic style set to 0 sharpness but I noticed this setting in Magic Lantern says its below canons 0 level. Yay or nay?
No. Don't use it. what are the benefits?
Hey fellas, long time user of the 50D RAW here now.
Wanted to share some still frames from my latest promo project using this system (can we officially call it "digital cinema" at this point now?):
Shot using Zeiss C/Y 50mm 1.7 and Nikkor AI-S 28mm 2.8
(http://farm4.staticflickr.com/3750/12703754063_e513d47920_h.jpg)
(http://farm8.staticflickr.com/7408/12704061614_ea18e91e4d_h.jpg)
(http://farm4.staticflickr.com/3776/12703754013_71ff3195cf_h.jpg)
Hi everybody! I'm late in getting to the 50d party. I own a 550d and was shooting RAW with that. But just got me a 50d and, of course, am very happy. One problem, and yes I've been going through the tread but can't seem to find an answer.
-Is there a way to center the crop mode in the middle of the sensor. It seems to record a region slightly to the upper left of center, and after moving the joystick around a little, it seems to jump around to various regions but never dead center. I did a test on my 550d, and it seems to be in the center. Am I missing something or is this the case with the 50d. Not the biggest problem, but i do have a wide-angle adapter for one of my lenses, and the region crop mode uses starts to include that fuzzy area you get on lame wide angle adapters. Having the crop mode region dead center would help.
Sorry if this has already been covered. Oh yeah, I'm using Tragic lantern (andy600 build 2014.2.1), with preview set to auto, and focus box set to center x5 zoom.
You guys rock! and KahL, awesome stills!
To center you have to go into crop (5x) mode and press the joystick only once.
Quote from: 1% on February 23, 2014, 07:21:49 AM
To center you have to go into crop (5x) mode and press the joystick only once.
Thanks for the quick reply 1%! Yeah I've been trying that, going into crop mode (x5), and pushing the joystick in once. It always jumps a little off center, and then with repeated pushings starts to drift around ending up on an edge.
It can only center the LV preview so you can frame a shot easier. The actual recorded area of the sensor is always off. I wish this could be fixed but it's no biggie for me personally.
What's the purpose of framing liveview if recording is shifted?
This bug makes crop view almost unusable for anything else than simple tests.
I'm using the 50D as B-cam of a BMCC but I'm forced to use it in full view, losing resolution and increasing aliasing, just because I never know what will be recorded in crop mode :(
Shots with short DOF are ok, but wide shots clearly suffer from the limitations of full view, compared to BMCC.
Quote from: riccardocovino on February 23, 2014, 12:24:38 PM
What's the purpose of framing liveview if recording is shifted?
This bug makes crop view almost unusable for anything else than simple tests.
I'm using the 50D as B-cam of a BMCC but I'm forced to use it in full view, losing resolution and increasing aliasing, just because I never know what will be recorded in crop mode :(
Shots with short DOF are ok, but wide shots clearly suffer from the limitations of full view, compared to BMCC.
So that you're at least able to see the center of the crop area. I think 1% said it has something to do with ADTG!? but so far there is no solution.
Quote from: Andy600 on February 23, 2014, 08:48:57 AM
It can only center the LV preview so you can frame a shot easier. The actual recorded area of the sensor is always off. I wish this could be fixed but it's no biggie for me personally.
Cool thanks for clearing that up Andy600, now I can stop messing with it and just use it, :).
Quote from: rommex on February 21, 2014, 08:51:18 AM
hi menoc, thanks for your note. honestly, I watch your posts and value them 8) what version of ACE do you use? I may have an older version...
Thanks. It's Camera RAW 8.3.0.141 (Photoshop CC - Creative Cloud)
QuoteI'm using the 50D as B-cam of a BMCC but I'm forced to use it in full view, losing resolution and increasing aliasing, just because I never know what will be recorded in crop mode
Well you have the display filter to see what you're recording in color. Its hard to have it on while recording but you should be able to easily frame at least the first shot.
Quote from: johnhenryrupe on February 23, 2014, 06:56:37 AM
Hi everybody! I'm late in getting to the 50d party. I own a 550d and was shooting RAW with that. But just got me a 50d and, of course, am very happy. One problem, and yes I've been going through the tread but can't seem to find an answer.
-Is there a way to center the crop mode in the middle of the sensor. It seems to record a region slightly to the upper left of center, and after moving the joystick around a little, it seems to jump around to various regions but never dead center. I did a test on my 550d, and it seems to be in the center. Am I missing something or is this the case with the 50d. Not the biggest problem, but i do have a wide-angle adapter for one of my lenses, and the region crop mode uses starts to include that fuzzy area you get on lame wide angle adapters. Having the crop mode region dead center would help.
Sorry if this has already been covered. Oh yeah, I'm using Tragic lantern (andy600 build 2014.2.1), with preview set to auto, and focus box set to center x5 zoom.
You guys rock! and KahL, awesome stills!
Funny we've just been edging on this discussion, I'm glad a few people are talking about it, i'm really hoping we can find some way of improving things.
I too came from the 550d, which made me assume the crop would be centred, I've tried a few builds and like Andy600 says i'm yet to find a way to do it too, and it seems nobody else does.
I wanted a wide angle in crop but alas canon conspire against us. It seems better in 10x though , can anyone offer an explanation about that one? because the recorded area is the same, but I seem to get less vignetting.
But to point out, it is better in crop, but the aliasing is still there in spades, I've shot a river a few days ago in 2000x1080 that looked like a multi coloured mess. Don't think that shooting in crop will give you a IKON or Digital Bolex on the cheap, I've realized that and it was a real bummer on my day.
Quote from: Jackeatley on February 23, 2014, 09:29:14 PM
Funny we've just been edging on this discussion, I'm glad a few people are talking about it, i'm really hoping we can find some way of improving things.
I too came from the 550d, which made me assume the crop would be centred, I've tried a few builds and like Andy600 says i'm yet to find a way to do it too, and it seems nobody else does.
I wanted a wide angle in crop but alas canon conspire against us. It seems better in 10x though , can anyone offer an explanation about that one? because the recorded area is the same, but I seem to get less vignetting.
But to point out, it is better in crop, but the aliasing is still there in spades, I've shot a river a few days ago in 2000x1080 that looked like a multi coloured mess. Don't think that shooting in crop will give you a IKON or Digital Bolex on the cheap, I've realized that and it was a real bummer on my day.
Well, I don't own a Bolex or BMCC but im very pleased with my 50D raw video.
I don't shoot crop, bought a Mosaic Eng 50D VAF and I'm very pleased with results. Aliasing and moire are almost gone!
Quote from: riccardocovino on February 23, 2014, 12:24:38 PM
What's the purpose of framing liveview if recording is shifted?
This bug makes crop view almost unusable for anything else than simple tests.
I'm using the 50D as B-cam of a BMCC but I'm forced to use it in full view, losing resolution and increasing aliasing, just because I never know what will be recorded in crop mode :(
Shots with short DOF are ok, but wide shots clearly suffer from the limitations of full view, compared to BMCC.
What I'm seeing in 10X Crop is the center of my 5x image. Is it exactly precise? it looks pretty close to me. In film days it would be somewhat akin to using a B&H Eyemo in 35MM or a B&H Filmo in 16MM. You may not have the exact view that you are looking at but you are close, somewhat of/ slightly a parallax view.
-Edit-In 10x Crop I am actually recording my 5x image. But I can critically focus the center of the image. When I view what I shot in my NLE or ACR it is the entire 5x image.
BTW slightly off topic but I believe that Stanley Kubrick shot his first feature film almost entirely with a B&H Eyemo (KILLER'S KISS).
I wouldn't want to shoot looking at a 10x magnification. 5x view is just about useable but is still only around 50% of the captured frame size(=2.475x at 1080p dimensions).
Aliasing and moire seem to be getting confused here. The 50D will alias (sometimes badly) in non-crop but is much less in 1:1 crop mode and totally down to pixel size. Moire is rare in crop mode but can happen. Hey, even the ARRI Alexa suffers from it ;) Moire can only be totally defeated with a huge increase in pixels and a reduction in pixel size but this also has a knock-on effect to low light performance.
Excessive moire can also be down to how you process the DNG files. For extreme cases you really need to use AMaZE debayering (as found in Raw Therapee) or the anti-moire tool in ACR. Aliasing is more difficult to treat. I've tried anti-aliasing plugins but they have minimal positive effect. The only 'ok but not perfect' solution I have found when trying to rescue a 50D shot with bad aliasing is some serious post work, rescaling up to 4k or larger and back to 1080p. This softens the image but reduces aliasing artifacts. You then need to add selective sharpening to enhance areas that are less prone to aliasing and possibly add blur or even do some matte paining to artificially correct a scene. It's a lot of hassle if you're only shooting for fun.
That said, I've found the 50D is actually better than the 7D (which has FPN problems) for raw video and it can just about match the Bolex D16 image. The Black magic Cameras are significantly better but obviously much more expensive than our 5yr old DSLR.
After using 50D raw video for the past 9 months I would offer the following advice:
1) remember the limits of what you are shooting with. Don't expect night vision or 5D Mark III quality. The 50D is somewhere between an S16 and S35 but behaves like Super 16. It has +/- 11 stops of DR (Dx0 tests) but in reality only about 9-10 without excessive noise. However, noise can be cleaned up with Neat Video and can be squeaky clean but retain detail at ISO 1600 with the right settings (i.e. temporal filtering and only reducing noise in the channels that actually have noise).
2) The 50D needs light! It will give exceptional results (considering it's age) if you remember this.
3) Post processing is important. You're shooting raw video so why skimp? If you want fast and easy then shoot H.264 (or, pardon the plug, use Cinelog and a LUT ;) ). It takes some careful steps to even get to a good starting point for grading but it's worth it.
I'll hazard a guess that no matter how bad your shot is, it can probably be cleaned up if you use the appropriate tools for the job but ask yourself first 'is the shot is worth saving?'! Sometimes a re-shoot, after learning how and where aliasing/moire occur in a given situation, is a better option.
Quote from: Andy600 on February 24, 2014, 09:05:58 AM
I wouldn't want to shoot looking at a 10x magnification. 5x view is just about useable but is still only around 50% of the captured frame size(=2.475x at 1080p dimensions).
Aliasing and moire seem to be getting confused here. The 50D will alias (sometimes badly) in non-crop but is much less in 1:1 crop mode and totally down to pixel size. Moire is rare in crop mode but can happen. Hey, even the ARRI Alexa suffers from it ;) Moire can only be totally defeated with a huge increase in pixels and a reduction in pixel size but this also has a knock-on effect to low light performance.
Excessive moire can also be down to how you process the DNG files. For extreme cases you really need to use AMaZE debayering (as found in Raw Therapee) or the anti-moire tool in ACR. Aliasing is more difficult to treat. I've tried anti-aliasing plugins but they have minimal positive effect. The only 'ok but not perfect' solution I have found when trying to rescue a 50D shot with bad aliasing is some serious post work, rescaling up to 4k or larger and back to 1080p. This softens the image but reduces aliasing artifacts. You then need to add selective sharpening to enhance areas that are less prone to aliasing and possibly add blur or even do some matte paining to artificially correct a scene. It's a lot of hassle if you're only shooting for fun.
That said, I've found the 50D is actually better than the 7D (which has FPN problems) for raw video and it can just about match the Bolex D16 image. The Black magic Cameras are significantly better but obviously much more expensive than our 5yr old DSLR.
After using 50D raw video for the past 9 months I would offer the following advice:
1) remember the limits of what you are shooting with. Don't expect night vision or 5D Mark III quality. The 50D is somewhere between an S16 and S35 but behaves like Super 16. It has +/- 11 stops of DR (Dx0 tests) but in reality only about 9-10 without excessive noise. However, noise can be cleaned up with Neat Video and can be squeaky clean but retain detail at ISO 1600 with the right settings (i.e. temporal filtering and only reducing noise in the channels that actually have noise).
2) The 50D needs light! It will give exceptional results (considering it's age) if you remember this.
3) Post processing is important. You're shooting raw video so why skimp? If you want fast and easy then shoot H.264 (or, pardon the plug, use Cinelog and a LUT ;) ). It takes some careful steps to even get to a good starting point for grading but it's worth it.
I'll hazard a guess that no matter how bad your shot is, it can probably be cleaned up if you use the appropriate tools for the job but ask yourself first 'is the shot is worth saving?'! Sometimes a re-shoot, after learning how and where aliasing/moire occur in a given situation, is a better option.
This is a fairly good assessment here.
The 50D isn't really a low light monster, but if you're already used to using the cropped s35 sensors then it shouldn't be too much of a problem. If you're creative you can work around it fairly simply.
One point I'd have to say is that the 60D in raw behaves more like s16 film more than the 50D. I've found from comparative tests that the 50D is more like 3-perf s35 film when upscaled to 1080p, while the 60D (at 1152x490) resolves very similarly to s16 film (more so than the DBolex or BMPCC). I'm also looking into purchasing some super 16 glass to further look into this for the 60D as well.
I'm have a blog post about this soon to give some visual comparisons.
Quote from: Andy600 on February 24, 2014, 09:05:58 AM
I wouldn't want to shoot looking at a 10x magnification. 5x view is just about useable but is still only around 50% of the captured frame size(=2.475x at 1080p dimensions).
Aliasing and moire seem to be getting confused here. The 50D will alias (sometimes badly) in non-crop but is much less in 1:1 crop mode and totally down to pixel size. Moire is rare in crop mode but can happen. Hey, even the ARRI Alexa suffers from it ;) Moire can only be totally defeated with a huge increase in pixels and a reduction in pixel size but this also has a knock-on effect to low light performance.
Excessive moire can also be down to how you process the DNG files. For extreme cases you really need to use AMaZE debayering (as found in Raw Therapee) or the anti-moire tool in ACR. Aliasing is more difficult to treat. I've tried anti-aliasing plugins but they have minimal positive effect. The only 'ok but not perfect' solution I have found when trying to rescue a 50D shot with bad aliasing is some serious post work, rescaling up to 4k or larger and back to 1080p. This softens the image but reduces aliasing artifacts. You then need to add selective sharpening to enhance areas that are less prone to aliasing and possibly add blur or even do some matte paining to artificially correct a scene. It's a lot of hassle if you're only shooting for fun.
That said, I've found the 50D is actually better than the 7D (which has FPN problems) for raw video and it can just about match the Bolex D16 image. The Black magic Cameras are significantly better but obviously much more expensive than our 5yr old DSLR.
After using 50D raw video for the past 9 months I would offer the following advice:
1) remember the limits of what you are shooting with. Don't expect night vision or 5D Mark III quality. The 50D is somewhere between an S16 and S35 but behaves like Super 16. It has +/- 11 stops of DR (Dx0 tests) but in reality only about 9-10 without excessive noise. However, noise can be cleaned up with Neat Video and can be squeaky clean but retain detail at ISO 1600 with the right settings (i.e. temporal filtering and only reducing noise in the channels that actually have noise).
2) The 50D needs light! It will give exceptional results (considering it's age) if you remember this.
3) Post processing is important. You're shooting raw video so why skimp? If you want fast and easy then shoot H.264 (or, pardon the plug, use Cinelog and a LUT ;) ). It takes some careful steps to even get to a good starting point for grading but it's worth it.
I'll hazard a guess that no matter how bad your shot is, it can probably be cleaned up if you use the appropriate tools for the job but ask yourself first 'is the shot is worth saving?'! Sometimes a re-shoot, after learning how and where aliasing/moire occur in a given situation, is a better option.
+1 On this.
I Love the image that comes out of the camera, but you have to be aware of the limits, Putting an extra AA filter doesn't really solve the problem, we still have a big sensor with a very inappropriate pixel density for HD video. No amount of post is going to solve this problem, once its tried to resolve above the nyquist point, its happened thats it, you can try to hide it, but its already happened, the pixel horses have bolted.
The mosaic filter is a really great product that helps us get that little bit extra out, but its not going to turn it into an alexa, the same way a "speedbooster" can't turn this breed of M4/3 cameras into 35mm cameras.
For me the 50d raw package is a great camera, that I would happily pay to rent, but its not digital cinema camera in the true sense, but its a great camera for those shallow detailed shots, and produces an astounding (IMO) amount of color information. This still goes for crop, I've still had it alias in crop when my DOF was too large, it simply couldn't resolve it and it produced artifacts, but the rest of the time, it was a lot better than full sensor mode.
Quote from: KahL on February 24, 2014, 05:20:00 PM
This is a fairly good assessment here.
The 50D isn't really a low light monster, but if you're already used to using the cropped s35 sensors then it shouldn't be too much of a problem. If you're creative you can work around it fairly simply.
Agreed!
Quote from: KahL on February 24, 2014, 05:20:00 PM
One point I'd have to say is that the 60D in raw behaves more like s16 film more than the 50D. I've found from comparative tests that the 50D is more like 3-perf s35 film when upscaled to 1080p, while the 60D (at 1152x490) resolves very similarly to s16 film (more so than the DBolex or BMPCC). I'm also looking into purchasing some super 16 glass to further look into this for the 60D as well.
Interesting point of view. I think of the 50D as 16mm like but can see what you mean.
I have to try 1152x490 on the 60D- Interesting point.
Quote from: Andy600 on February 24, 2014, 09:05:58 AM
I wouldn't want to shoot looking at a 10x magnification. 5x view is just about useable but is still only around 50% of the captured frame size(=2.475x at 1080p dimensions).
Aliasing and moire seem to be getting confused here. The 50D will alias (sometimes badly) in non-crop but is much less in 1:1 crop mode and totally down to pixel size. Moire is rare in crop mode but can happen. Hey, even the ARRI Alexa suffers from it ;) Moire can only be totally defeated with a huge increase in pixels and a reduction in pixel size but this also has a knock-on effect to low light performance.
Excessive moire can also be down to how you process the DNG files. For extreme cases you really need to use AMaZE debayering (as found in Raw Therapee) or the anti-moire tool in ACR. Aliasing is more difficult to treat. I've tried anti-aliasing plugins but they have minimal positive effect. The only 'ok but not perfect' solution I have found when trying to rescue a 50D shot with bad aliasing is some serious post work, rescaling up to 4k or larger and back to 1080p. This softens the image but reduces aliasing artifacts. You then need to add selective sharpening to enhance areas that are less prone to aliasing and possibly add blur or even do some matte paining to artificially correct a scene. It's a lot of hassle if you're only shooting for fun.
That said, I've found the 50D is actually better than the 7D (which has FPN problems) for raw video and it can just about match the Bolex D16 image. The Black magic Cameras are significantly better but obviously much more expensive than our 5yr old DSLR.
After using 50D raw video for the past 9 months I would offer the following advice:
1) remember the limits of what you are shooting with. Don't expect night vision or 5D Mark III quality. The 50D is somewhere between an S16 and S35 but behaves like Super 16. It has +/- 11 stops of DR (Dx0 tests) but in reality only about 9-10 without excessive noise. However, noise can be cleaned up with Neat Video and can be squeaky clean but retain detail at ISO 1600 with the right settings (i.e. temporal filtering and only reducing noise in the channels that actually have noise).
2) The 50D needs light! It will give exceptional results (considering it's age) if you remember this.
3) Post processing is important. You're shooting raw video so why skimp? If you want fast and easy then shoot H.264 (or, pardon the plug, use Cinelog and a LUT ;) ). It takes some careful steps to even get to a good starting point for grading but it's worth it.
I'll hazard a guess that no matter how bad your shot is, it can probably be cleaned up if you use the appropriate tools for the job but ask yourself first 'is the shot is worth saving?'! Sometimes a re-shoot, after learning how and where aliasing/moire occur in a given situation, is a better option.
Absolutely agree!
I was looking through a note I made last year of shooting in crop mode with a slower than normal frame speed - as an experiment to increase the frame size. I was using 2.39:1 aspect ratio and set the speed to 12 fps; I thought I had set some of the larger frame sizes available in the menu but kept getting an actual frame size of 2000 x 852. Is 2000 pixels the largest possible crop width regardless of frame speed, or did I mess up somehow? Thanks.
Quote from: TrueIndigo on February 24, 2014, 08:21:32 PM
I was looking through a note I made last year of shooting in crop mode with a slower than normal frame speed - as an experiment to increase the frame size. I was using 2.39:1 aspect ratio and set the speed to 12 fps; I thought I had set some of the larger frame sizes available in the menu but kept getting an actual frame size of 2000 x 852. Is 2000 pixels the largest possible crop width regardless of frame speed, or did I mess up somehow? Thanks.
Yes. 2000px is the maximum width.
Thanks Andy.
KahL: "I'm also looking into purchasing some super 16 glass to further look into this for the 60D as well." -- can I ask what mount you will be using? I have some C-mount lenses I've had for years, but I can't use them because the lens register distance of a Canon DSLR is too long (44.0mm versus 17.5mm for C-mount).
EDIT: I just saw one of your earlier posts -- you mentioned PL lenses (with a lens register distance of 52.0mm). PL lenses are out of my budget, but I'd be interested to hear how you get on with them.
Hey guys, I haven't been using my 50d for quite some time so today I installed the latest release and loaded the raw module. The problem is that I can't get over 180º shutter (maybe it was a little more, don't remember). I remember being able to use up to 1/2000 speed a few months ago. What am I doing wrong? Thanks
Just posted the comparison video:
http://kahlworks.wordpress.com/2014/02/25/unscientific-yet-fun-50d-and-60d-raw-comparisons/
Quote from: TrueIndigo on February 25, 2014, 01:26:02 AMThanks Andy.
KahL: "I'm also looking into purchasing some super 16 glass to further look into this for the 60D as well." -- can I ask what mount you will be using? I have some C-mount lenses I've had for years, but I can't use them because the lens register distance of a Canon DSLR is too long (44.0mm versus 17.5mm for C-mount).
EDIT: I just saw one of your earlier posts -- you mentioned PL lenses (with a lens register distance of 52.0mm). PL lenses are out of my budget, but I'd be interested to hear how you get on with them.
I've also been looking at b4-mount glass too:
(http://i.ebayimg.com/00/s/NDgwWDY0MA==/z/PmkAAOxy4M5R7spw/$T2eC16h,!yEE9s5jHQbkBR7spwiljw~~60_3.JPG)
With B4 glass and a 2x extender, should be free of vignetting in crop mode, correct? Without 2x extender you would have a somewhat fisheye look.
Or I believe in crop mode (even without extender) you would cover the whole sensor. In full frame, you would get the vignetted fish eye look. It is more the cameras like the GH series that need the 2x extender because they do not have the same sensor zoom we have on ML.
KahL or anyone else using converted lenses care to clarify? Thanks I had actually picked up that J15x9 B4 lens last summer at an antique show/town fair for something like $30.
Quote from: KahL on February 25, 2014, 01:26:02 AM
Just posted the comparison video:
http://kahlworks.wordpress.com/2014/02/25/unscientific-yet-fun-50d-and-60d-raw-comparisons/
Kahl I like the comparison test. I understand what you mean about the 60D, it does feel like super 16, the grain structure particularly indoors.
Quote from: KahL on February 25, 2014, 01:39:45 AM
I've also been looking at b4-mount glass too:
(http://i.ebayimg.com/00/s/NDgwWDY0MA==/z/PmkAAOxy4M5R7spw/$T2eC16h,!yEE9s5jHQbkBR7spwiljw~~60_3.JPG)
Thats exactly what i've been using, beware that you'll get no higher than 1700 without vignette i'm afraid, decent lens for 2080x1080 silent pics on the 550d though.
This particular lens can be a bit hazy wide open, but can get fairly sharp at F4-F8.
Hi Andy, is this related somehow to your hints about some update to cameras? http://www.canonrumors.com/2014/02/hardware-hack-for-eos-cameras-coming-soon-cr1
No. First I've heard of it and as the article says it's just a rumor and there are plenty of those flying around at the moment. I might have been referring to our Cinelog camera profile update that was just released?!
Quote from: Andy600 on February 28, 2014, 12:47:08 AM
No. First I've heard of it and as the article says it's just a rumor and there are plenty of those flying around at the moment. I might have been referring to our Cinelog camera profile update that was just released?!
Oops, missed it. Would be so kind to point?
hi guys,
there are so many ways of convert from RAW to Dng , I am testing all the ways, even MLV (that take to long to convert to be usable in a tight workflow). RawTherapee and Batchelor seems to be the most efficient, but, I could never achive to match the andy600 quality, and thats my goal. To get images with that quality!
One other thing, when I shot, the VF in the 50d was looking nice, with light as I intended to be, and the ETTR meter was telling me that it was the right exposure (the one I wanted), when I got home, and put the images in davinci (after converting the mlv files to DNG in the MLV converter), they turned allmost black, and I dont know what happend here... But is really annoying!
And for the last, I was shooting MLV and the last 3 clips where recorded in h.264! =( really bad situation! I know that the camera is not that "young" and I am not complaining, the only thing I would like to know, is if there are some tips or tricks to work around this problems...
I love the way 50D look. It as a really cinematic feel to it (when you are able to process images like Andy600 does) - Andy600, I would pay for a "50D record, workflow and tips" book.
I am serious!
I'm flattered. I haven't got time to write a whole book but I can offer advice when I'm here ;)
I never finished my 50D guide because, apart from the time and effort involved in writting it, things were moving so fast with raw development that it was becoming outdated as fast as I could write it. If I do find some free time I'll see what needs adding/changing (i.e. MLV, ETTR etc) and try to finish it but not promising anything.
Anyway, It sounds like you are shooting and exposing correctly. Is it only Resolve that makes your DNGs look dark? How do they look in another app?
Maybe Joao applied the bmd film curve. From what i've seen here, that log curve makes look thing darker. Apply Cinelog or Visionlog
Can anyone tell me what fps settings i need to record RAW video on the 50D so i can lip sync music for a music video shoot? I did a test shoot and couldn't get it right.
JIKIJI:
In what was formerly NTSC countries 23.976 and in PAL countries 25 FPS.
Hey guy's just stopping by the forum and letting you guy's know what I've been up to with the 50D. Before I continue I would like to thank the whole team of Magic Lantern @a1ex @1% @Andy600 @gregoryofmanhattan and many many others for all their hard work of the RAW Hacks. Here is a commercial that I just shot for this brand new company called: Reyo all shots where on the 50D all I can say is I love my 50D enjoy it guy's also got a couple more video's on the way.. Side note it was all shot on one of Andy's old RAW Hacks working flawlessly haven't moved up to the new Hacks yet.
Little test of my diy display turntable for video and 360 degree photo. Shot on 50d with x3 crop mode and cheap canon 50mm 1.8 lense
https://vimeo.com/87959265
I AM having issues with the credit card, so I didn't bought cinelog. But I think it is about the log. Still, it isn't quite as well exposed as I have seen while shooting. Maybe have to change the parameters of the EFV...
Have to try it out
Quote from: joaomoutinho on March 03, 2014, 06:37:08 AM
I AM having issues with the credit card, so I didn't bought cinelog. But I think it is about the log. Still, it isn't quite as well exposed as I have seen while shooting. Maybe have to change the parameters of the EFV...
Have to try it out
Can you send me a single frame (DNG). I'll check it with my Resolve setup.
Hey Andy, just checked your uploaded a new Tragic Lantern Update!
Which are the most relevant changes in this one? Is there a place I can check them out?
Thank you!
PS: Just bought the cinelog. I'm running out of space and will try to convert my DNGs using your dcp, wish me luck :D
Quote from: dogmydog on March 04, 2014, 04:55:25 PM
Hey Andy, just checked your uploaded a new Tragic Lantern Update!
Which are the most relevant changes in this one? Is there a place I can check them out?
Thank you!
PS: Just bought the cinelog. I'm running out of space and will try to convert my DNGs using your dcp, wish me luck :D
I think the latest changes are the same as those shown in the nightly changelogs. 1% is now committing code to the Unified build. Tragic is still different but slowly converging with Unified. If there are any significant changes/updates to Tragic Lantern I'll list them in the builds.
Thanks for your Cinelog purchase. I'd wish you luck but honestly, you won't need it ;) If you have any questions about using it just msg or email me.
The main relevant thing is dialog timer disable isn't in main and I don't think it can get accepted.
Hey guys,
Here's a micro short I shot entirely with Raw on the 50D for the Vimeo weekend challenge. I felt a bit creative over the weekend and thought it would be nice to do something other than a test. Very tricky lighting for the camera here but it held out well I think. Overall budget was £2.50 for some candles I bought from ASDA!
Quote from: Supermac on March 05, 2014, 10:58:48 PM
Hey guys,
Here's a micro short I shot entirely with Raw on the 50D for the Vimeo weekend challenge. I felt a bit creative over the weekend and thought it would be nice to do something other than a test. Very tricky lighting for the camera here but it held out well I think. Overall budget was £2.50 for some candles I bought from ASDA!
Nice vid! Fast and simple.
So, I just updated to the latest nightly build. The thing crashed when simply trying to turn on liveview. Here's the log, don't know if it's just something that happened when updating or something, but here we go anyway. http://pastebin.com/xue2GWDH
Quote from: roopepal on March 07, 2014, 03:47:30 PM
So, I just updated to the latest nightly build. The thing crashed when simply trying to turn on liveview. Here's the log, don't know if it's just something that happened when updating or something, but here we go anyway. http://pastebin.com/xue2GWDH
I've just tested the last few nightly builds, as well as Andy's latest build, and I don't encounter any issues with turning on LV. What is the Mercurial changeset on the build you are using? If you do a clean install (i.e., don't preserve any settings), do you still have problems with LV? Can you try the latest nightly build?
Is there anyone else out there shooting Silent Pics? I'd say over 60% of mine get some sort of distortion, be it off-colour, pink lines, or reorganized pixels.
(https://dl-web.dropbox.com/get/corruptedDNGs/51370002ACRedit.jpg?_subject_uid=76154628&w=AADTUEI_-M4cERIvKa-2wYIJ1FjIVBeuQDsj4-jYkV_BEg) (https://dl-web.dropbox.com/get/corruptedDNGs/51300001ACRedit.jpg?_subject_uid=76154628&w=AABhO1iGzFVhTRnxDVOxN1dUBsgUhpqbZXcMzySWUiC4Cg)
(https://dl.dropboxusercontent.com/sh/h520vrzjg0q9sun/zYYK5bHwgB/51290005ACRedit.jpg?token_hash=AAGZLyymS8vBIV0sAQmdFO3eevQUYVdvSV8C96YJnNo1BA) (https://dl.dropboxusercontent.com/sh/h520vrzjg0q9sun/2V21hcEHno/51280003ACRedit.jpg?token_hash=AAGZLyymS8vBIV0sAQmdFO3eevQUYVdvSV8C96YJnNo1BA)
I always had to disable dialog timers to take silent pics.
Quote from: 1% on March 09, 2014, 06:48:48 AM
I always had to disable dialog timers to take silent pics.
Thanks! Works great now. Never thought to disable during shooting, only filming. Now if only the cropped mode were centered, this lens would be great on the 50D.
Thanks 1%
Hi guys, I just bought a second hand 50D, wanted to try out some raw video. I have already installed the ML firmware on it, but some how in my ML menu there are only TWO reording modes ( 1920x1080, 30fps and 640x480 30fps) and it dsnt say RAW video anywhere..
Am i doing something wrong? i dont think these are Raw frame sizes..
Can anyone help :)
cheers
S
Assuming that you've installed a recent build, you need to enable either the raw_rec module or the mlv_rec module. Then there will be a "RAW video" item on the Movie tab of the ML menu for turning on and configuring raw recording. The MLV format has added metadata compared to the RAW format.
Well, i have just updated the firmware of the website.. (ML 2.3)
I havent installed any Nightly Builds or the Alpha Builds..
As u can see, i am very new to the ML Raw workflow.. Do i need to install the builds as well?
ML 2.3 from the website is the stable release, but it's a year and a half old and is missing features like raw recording. If such features are important to you, you can install a nightly build (http://builds.magiclantern.fm/#/). While the nightly builds are not "stable" in the formal sense, they are decently well tested, and you are unlikely to encounter any major issues. Of course, please report any issues that you do have, either on the 50D thread (http://www.magiclantern.fm/forum/index.php?topic=9852.0) or on Bitbucket (https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open).
Quote from: shiv on March 10, 2014, 04:09:48 PM
Well, i have just updated the firmware of the website.. (ML 2.3)
I havent installed any Nightly Builds or the Alpha Builds..
As u can see, i am very new to the ML Raw workflow.. Do i need to install the builds as well?
Nice place to start: http://www.magiclantern.fm/forum/index.php?topic=5520.0
Hi everybody :)
Got my very own 50d a few weeks ago, and while sorting things out and testing it, shot this footage. It's been a cold winter here in the great state of Wisconsin, so i decided to do a themed test compilation video. I used various lenses, including the 18-55 canon kit lens, two vintage m42s (a 55mm and 28mm), a 100-300 telephoto, and a cheap-o wide-angle adapter (on the 18-55). Used batchelor and rawanizer. Then ACR to AE. Still getting the hang of color grading (its a can of worms), and I've downloaded Resolve, so I'll start in on that soon. Thanks everyone for all the hard work! And also all the videos posted, good stuff.
Nice piece :)
Nice work. What resolution did you use ?
Quote from: lionelp on March 11, 2014, 02:30:44 PM
Nice work. What resolution did you use ?
Thanks guys! I shot in 1584x894 (non-crop), and 1920x1080 (crop). Generally the closer up shots are 1920x1080. I used Andy600's latest builds, and after card warm up, had NO issues with recording as long as I felt like it, no drop frames, no bad frames, it totally rocked! In post exported as 1920x1080, scaling up the 1584x894 to match.
Shot with FPS override to 23.976
GD on, with just RAW histogram and focus peaking, Had this set to turn off during recording for the 1920x1080 crop shots.
RAW rec.
And of course...the Komputer Bay 64g 1000x!
Quote from: johnhenryrupe on March 11, 2014, 03:13:52 PM
Thanks guys! I shot in 1584x894 (non-crop), and 1920x1080 (crop). Generally the closer up shots are 1920x1080. I used Andy600's latest builds, and after card warm up, had NO issues with recording as long as I felt like it, no drop frames, no bad frames, it totally rocked! In post exported as 1920x1080, scaling up the 1584x894 to match.
Shot with FPS override to 23.976
GD on, with just RAW histogram and focus peaking, Had this set to turn off during recording for the 1920x1080 crop shots.
MLV or RAW rec?
Quote from: menoc on March 11, 2014, 04:03:31 PM
MLV or RAW rec?
Still using RAW rec, haven't taken the time to mess with MLV yet. I'm pretty comfortable with the RAW rec workflow. Metadata i can live without or take notes while shooting if need be. Do you have any thoughts on this?
Quote from: johnhenryrupe on March 11, 2014, 04:11:54 PM
Still using RAW rec, haven't taken the time to mess with MLV yet. I'm pretty comfortable with the RAW rec workflow. Metadata i can live without or take notes while shooting if need be. Do you have any thoughts on this?
Well, MLV is working fine. The only issue for me is that I find it more time consuming to convert MLV if your using OS X (Mac). There's no GUI conversion utility for it on the mac. On Windows, MLV it is well supported with utilities
MLV Mystic? That's a GUI based app and converts .mlv and .raw on the Mac AFAIK
http://www.magiclantern.fm/forum/index.php?topic=10466.0 (http://www.magiclantern.fm/forum/index.php?topic=10466.0)
Quote from: Andy600 on March 11, 2014, 07:17:16 PM
MLV Mystic? That's a GUI based app and converts .mlv and .raw on the Mac AFAIK
http://www.magiclantern.fm/forum/index.php?topic=10466.0 (http://www.magiclantern.fm/forum/index.php?topic=10466.0)
HA! . . Well, what do you know? :D . . . that's why we need ya Andy!
;)
Hi guys. Could someone please list all the major bugs and limitations that remain to date with RAW recording on 50D? I haven't had the time to read through all the topic yet and I'm sure some things have been resolved. So what should one be aware of when considering buying the cam at this point? Coming from 600D by the way...
...And thanks for your work and effort, much appreciated!
https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open
One more question. When recording RAW what resolution is output via HDMI (600D? 50D?)? I'm considering using it for framing/focusing/monitoring purposes (portable). I can't decide which is better for this: laptop with EOS Utility or ext HDMI monitor. Any thoughts? What do you use?
Quote from: far.in.out on March 17, 2014, 02:32:42 PM
One more question. When recording RAW what resolution is output via HDMI (600D? 50D?)? I'm considering using it for framing/focusing/monitoring purposes (portable). I can't decide which is better for this: laptop with EOS Utility or ext HDMI monitor. Any thoughts? What do you use?
Can't answer your resolution question, but have you tried EOS Utility while the RAW or MLV module is active? Seems that on the 50D USB output is broken when a RAW recording module is loaded. I try it every few builds to see if something in the changelog fixed it, but no luck so far. I have a Nexus 7 with DSLR Controller that I would love to use with my rig (I sometimes do for framing, just shut off MLV or RAW and the image comes back) but that has the same USB issues as connecting to EOS Utility. Good luck!
Quote from: dsManning on March 17, 2014, 11:35:29 PM
Can't answer your resolution question, but have you tried EOS Utility while the RAW or MLV module is active? Seems that on the 50D USB output is broken when a RAW recording module is loaded. I try it every few builds to see if something in the changelog fixed it, but no luck so far. I have a Nexus 7 with DSLR Controller that I would love to use with my rig (I sometimes do for framing, just shut off MLV or RAW and the image comes back) but that has the same USB issues as connecting to EOS Utility. Good luck!
50D Native ratio is a 4:3 image with side columns ( resolution is 1080p - at least that's what my monitor reports ). . . although, resolution I think depends on the monitor . . . but the aspect ratio you can always change in the ML menus.
Quote from: far.in.out on March 15, 2014, 09:34:08 AM
Hi guys. Could someone please list all the major bugs and limitations that remain to date with RAW recording on 50D? I haven't had the time to read through all the topic yet and I'm sure some things have been resolved. So what should one be aware of when considering buying the cam at this point? Coming from 600D by the way...
...And thanks for your work and effort, much appreciated!
I would REALLY appreciate this as well, as Im considering upgrading from 550d\600d and would like to know the hiccups to expect. Does USB output work (for DSLR controller)? DOes audio work with MLV? Do we have on-screen audio levels while recording? Does peaking work while recording? JUst want to know what we are getting into before we jump onboard :)
Many thanks to all
Quote from: Jbowdach on March 21, 2014, 06:40:39 PM
I would REALLY appreciate this as well, as Im considering upgrading from 550d\600d and would like to know the hiccups to expect.
Many thanks to all
QuoteDoes USB output work (for DSLR controller)?
I've heard that it does. But have not tested it myself.
QuoteDOes audio work with MLV? Do we have on-screen audio levels while recording?
There is no audio on the 50D. But you can implement the dual system (external recorder)
QuoteDoes peaking work while recording?
Yes, but no recommended if you want continuous recording. GD is recommended to be off during recording.
QuoteJUst want to know what we are getting into before we jump onboard :)
It has lovely images but you have to give it light (especially indoors). But also remember - it is RAW! So light sometimes is not that big of an issue.
Outdoors:
http://vimeo.com/davidequatela/peopleinfrankfurt
Thank you very much for the answers! Seems like a very usable camera for RAW atm, minus the focus peaking. DOes HDMI out work, so if I can an external display for focus peaking (or the USB and my tablet via DSLR controller) :)
Quote from: Jbowdach on March 21, 2014, 09:14:50 PM
Thank you very much for the answers! Seems like a very usable camera for RAW atm, minus the focus peaking. DOes HDMI out work, so if I can an external display for focus peaking (or the USB and my tablet via DSLR controller) :)
HDMI Out works. I use it with my Lillieput.
Quote from: menoc on March 21, 2014, 09:18:07 PM
HDMI Out works. I use it with my Lillieput.
Thank you for the confirmation. 50d seems like the ideal "affordable" RAW camera to those who can handle beta testing. Also seems like the perfect upgrade from my t2i\t3i :) thanks!!
Quote from: Jbowdach on March 21, 2014, 09:20:24 PM
Thank you for the confirmation. 50d seems like the ideal "affordable" RAW camera to those who can handle beta testing. Also seems like the perfect upgrade from my t2i\t3i :) thanks!!
Hi there. I know about the restrictions, but I have always had GD on with Histo and recording was continuous in my case. I also turned on Ficus Peaking, and it seems to record OK.
Regarding HDMI out: it does work, however it stresses the processor and it may influence recording. This was confirmed by 1% after I had numerous problems with a Lilliput monitor connected. In my case I had broken frames and switching off the RAW mode, incidentally recording in h.264...
Quote from: Jbowdach on March 21, 2014, 09:20:24 PM
Thank you for the confirmation. 50d seems like the ideal "affordable" RAW camera to those who can handle beta testing. Also seems like the perfect upgrade from my t2i\t3i :) thanks!!
Thank you for chiming in about the possible HDMI issues. Im currently using a display on my Nexus 7 tablet using USB out and DSLR controller, so this may be okay, but I greatly appreciate the info :)
DSLR Controller not working while raw video is on
Quote from: simulacro on March 21, 2014, 10:40:36 PM
DSLR Controller not working while raw video is on
Aw man, thats a huge disappointment. Makes focusing quite difficult w/o 100% reliable HDMI or DSLR controller. Guess ill need to test and experiment,
Quote from: simulacro on March 21, 2014, 10:40:36 PM
DSLR Controller not working while raw video is on
Thank you. Said this a few posts back, and it was stated that USB was working after. IT IS NOT WHILE RECORDING RAW (which is what most of us are interested in here)
I've been having issues with shooting long takes in ML Raw on the 50D. If I go over the 4GB file limit and the clip switches to a zip file to continue the raw recording, when I render the ML RAW files into Cinema DNG, I get strange pink frames with lines all through the image. The image is not even recognizable. Any idea why this is happening? Maybe a setting on my camera? I tried many of your latest builds and even different cars and different recording resolution but all the same results if I go over the 4GB file limit. Any help would be great! I can even post a sample frame so you can see what I mean. Thanks for your time and consideration on this.
Quote from: rommex on March 21, 2014, 10:01:39 PM
Hi there. I know about the restrictions, but I have always had GD on with Histo and recording was continuous in my case. I also turned on Ficus Peaking, and it seems to record OK.
Regarding HDMI out: it does work, however it stresses the processor and it may influence recording. This was confirmed by 1% after I had numerous problems with a Lilliput monitor connected. In my case I had broken frames and switching off the RAW mode, incidentally recording in h.264...
Interestingly, I frequently record with my Lilliput for framing with no problems (although you won't get gray scale preview out the hdmi - doesn't work).
About peaking: Keep in mind that it mostly depends on what mode you're shooting - most of the time I shoot in crop mode at 1920x960. Even with double buffering and dialog timers off, if I have peaking on, I do not get continuous recording. Global Draw is one of the most taxing processes in ML. I try to use it mostly for pre-record operations.
Quote from: sync24fps on March 22, 2014, 04:04:03 AM
I've been having issues with shooting long takes in ML Raw on the 50D. If I go over the 4GB file limit and the clip switches to a zip file to continue the raw recording, when I render the ML RAW files into Cinema DNG, I get strange pink frames with lines all through the image. The image is not even recognizable. Any idea why this is happening? Maybe a setting on my camera? I tried many of your latest builds and even different cars and different recording resolution but all the same results if I go over the 4GB file limit. Any help would be great! I can even post a sample frame so you can see what I mean. Thanks for your time and consideration on this.
Was global draw switched on while recording? and where you recording .raw or .mlv?
Quote from: sync24fps on March 22, 2014, 04:04:03 AM
I've been having issues with shooting long takes in ML Raw on the 50D. If I go over the 4GB file limit and the clip switches to a zip file to continue the raw recording, when I render the ML RAW files into Cinema DNG, I get strange pink frames with lines all through the image. The image is not even recognizable. Any idea why this is happening? Maybe a setting on my camera? I tried many of your latest builds and even different cars and different recording resolution but all the same results if I go over the 4GB file limit. Any help would be great! I can even post a sample frame so you can see what I mean. Thanks for your time and consideration on this.
How are you merging the spanned RAW files? Also, which app are you using to render the DNGs?
Hi the global draw was on and recorded in .raw - Its only if I go over the 4GB limit that I see this problem. Also using RAW2DNG for 50D only made by Andy. The files are rendered fine with the RAW2DNG but when they are opened in a program for processing they appear corrupted.
If you are working with a Mac... There is a high-probability that RawMagic will transcode all of the files appropriately. Apparently some of the Raw converters do not accept spanning of files. RawMagic is available for download in the App store. It is a free download.
Hi Andy,
I did some recordings this week after upgrading to latest TL and some times the camera freezed, never seen before.
Next week I'll have to do some shoots on a Piper flying just once, so can you tell me which is the most stable version?
I'm really afraid to miss the shots!
Quote from: sync24fps on March 22, 2014, 07:10:18 AM
Hi the global draw was on and recorded in .raw - Its only if I go over the 4GB limit that I see this problem. Also using RAW2DNG for 50D only made by Andy. The files are rendered fine with the RAW2DNG but when they are opened in a program for processing they appear corrupted.
The reason I asked is that both have caused me pink frames or torn frames in the past, try without global draw on and see what happens. On the 50D i've seen speed loss and one or two pink frames when recording with GD on, on the 550D every clip with GD on would get screwed up somewhere, so its something to check.
Quote from: menoc on March 22, 2014, 04:25:00 AM
Interestingly, I frequently record with my Lilliput for framing with no problems (although you won't get gray scale preview out the hdmi - doesn't work).
About peaking: Keep in mind that it mostly depends on what mode you're shooting - most of the time I shoot in crop mode at 1920x960. Even with double buffering and dialog timers off, if I have peaking on, I do not get continuous recording. Global Draw is one of the most taxing processes in ML. I try to use it mostly for pre-record operations.
+1.
Recording with Lilliput, MLV, with 2 or 3 pink frames only at start (known issue) and the rest runs smoothly.
Quote from: menoc on March 22, 2014, 04:40:14 AM
How are you merging the spanned RAW files? Also, which app are you using to render the DNGs?
Quote from: Jackeatley on March 22, 2014, 03:10:23 PM
The reason I asked is that both have caused me pink frames or torn frames in the past, try without global draw on and see what happens. On the 50D i've seen speed loss and one or two pink frames when recording with GD on, on the 550D every clip with GD on would get screwed up somewhere, so its something to check.
Rename the raw spannned files to .001, .002, in this order, then use FS Joiner Splitter. Then use Andy's raw2dng to process the raw +4GB files.
I had only corrupted frames when tried to process spanned raw files without using this method 1st.
so recording MLV raw video and splitting it will have an empty wav file, im assuming?
OK. So I got myself a 50D. Few questions so far.
How do you do your framing on an external HDMI mon? Cropping doesn't seem to be applied here.
What is the optimal build currently? Link?
To answer one of the previous questions - 50D outputs 1080i on my monitor, or at least that's what it reports... Fills almost entire screen (1920x1080).
Quote from: far.in.out on March 26, 2014, 12:17:57 AM
OK. So I got myself a 50D.
What is the optimal build currently? Link
Most current is usually optimal:
http://builds.magiclantern.fm/#/
or TL
https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_for_50D_Andy600Build.2014Mar03.50D109.zip
The warnings posted elsewhere on this thread apply.
Quote from: far.in.out on March 26, 2014, 12:17:57 AM
OK. So I got myself a 50D. Few questions so far.
How do you do your framing on an external HDMI mon? Cropping doesn't seem to be applied here.
What is the optimal build currently? Link?
To answer one of the previous questions - 50D outputs 1080i on my monitor, or at least that's what it reports... Fills almost entire screen (1920x1080).
As I said, 50D outputs 1080 through hdmi but the native image will be a 4:3 image. To get it to display a 16:9 image, you have to set it in the ML menus. Some monitors, such as my Lilliput have a "Camera Mode" that crops and zooms a 4:3 feed to fit the monitor's 16:9 LCD screen - know your equipment (or research it) before you buy it.
I'd recommend Andy's Tragic Lantern version:
https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_for_50D_Andy600Build.2014Mar03.50D109.zip (https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_for_50D_Andy600Build.2014Mar03.50D109.zip)
I have now moved on to MLV recording. 8)
@Andy600: feel free to create a thread in the Raw Video section, for Magic Lantern (not for Tragic Lantern). This section will be shutdown, as announced (http://www.magiclantern.fm/forum/index.php?topic=11080) last week.
Third party builds are no longer accepted on this forum, so please contribute your changes to the main repository.
Still, I don't get it. When You use external HDMI mon, when you're shooting RAW how do you frame a shot? On internal monitor there's cropping on the screen so you see exactly what will be in the final frame. On ext HDMI mon I don't see any cropping. Am I missing something?
If the 50D maintains 1080i HDMI resolution while shooting raw I'm getting a monitor :) This question was raised several times and I was under the impression that HDMI output on the 50D drops in resolution when you hit record and/or replicates Liveview. As for framing, I guess you could stick some anti-glare film on your monitor and cut out or mark the frame boundaries.
@a1ex - yes I know. I haven't added anything since the announcement and I'm going to lock this thread myself after my final post. I think Albert already has a 50D thread for Magic Lantern so I'll point users to that.
To all 50D Tragic Lantern users.
First, thank you all for contributing to this thread, one of the biggest on the forum. I'm sure, like me, you learned a few things here but apologies to new 50D users who might have found it difficult to find answers among the 180+ pages.
I am now locking this thread ahead of the changes being introduced to the forum. You can read what, why and how these changes affect things here: http://www.magiclantern.fm/forum/index.php?topic=11080 (http://www.magiclantern.fm/forum/index.php?topic=11080)
I completely understand the reasons behind the coming changes but I want to add a personal thank you to 1% for maintaining this third-party mod, bringing features to the 50D and other cameras that may not have made it to the main Magic Lantern builds. As I have always pointed out, I only compile the code that 1% commits to his Bitbucket repository. The 'Tragic Lantern for the 50D' builds are derived from the code maintained by the main developers (a1ex, g3gg0 and others) but tweaked, pushed and pulled by 1% for the 50D.
I personally have never experienced any major issues with Tragic Lantern on the 50D (and originally on the 600D) but, as I point out when notifying you of new builds, Tragic Lantern does not have all the built-in safety fallbacks of Magic Lantern and there is always the potential for irreversible damage to be caused to your camera.
So, third party modifications are no longer being supported in the forum which means we can no longer discuss Tragic Lantern. I will continue to upload TL builds to my Bitbucket repository for the foreseeable future but I suggest 50D TL users begin the transition to using Magic Lantern nightlies http://builds.magiclantern.fm/#/ (http://builds.magiclantern.fm/#/) as the builds I upload will not be supported in any way. Questions about Tragic Lantern will be met with silence and may even result in a ban from the forum so you have been warned. If you choose to download and use a Tragic Lantern build you do so on the strict understanding that you cannot ask for support on this forum!
As suggested in the thread linked to in the first line of this post, it would be helpful to the developers for users to provide bug reports for Tragic Lantern here: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/issues?status=new&status=open (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/issues?status=new&status=open).
To report or request 'missing features' that may be in Tragic Lantern but not in the Nightly builds please use this topic: http://www.magiclantern.fm/forum/index.php?topic=10593.0 (http://www.magiclantern.fm/forum/index.php?topic=10593.0)
To discuss Magic Lantern 50D builds please use this topic: http://www.magiclantern.fm/forum/index.php?topic=9852.0 (http://www.magiclantern.fm/forum/index.php?topic=9852.0)
Thanks for your understanding!
Topic locked by Andy600