PLEASE READ THROUGH THE FOLLOWING LINK FOR GENERAL RAW VIDEO INFO-
http://www.magiclantern.fm/forum/index.php?topic=5520.0 (http://www.magiclantern.fm/forum/index.php?topic=5520.0)
The 600D (T3i) is capable of continuous raw video recording, but on a smaller scale than 5d ii and 5d iii. We're limited to a 21 MB/s sd write speed, even with the top-of-the-line Sandisk 95 MB/s sd card.
All hope is not lost though, seeing that 720p quality is well within our reach. I've had the best results shooting in ntsc 640x480 video mode with the newest build by 1%, recording with continuous frames at 1152x464 (2.50:1), up-rezzed to ~ 1280x512 in post, and 16:9 aspect of 960x540, which also uprezzes nicely. Not sure if it still matters with the newest builds but I leave pic quality on sRaw for a bump in buffer memory. If you accidentally take pics in sRaw and can't get them to open, try Canon's Digital Photo Professional.
As far as which sd card to use, the faster the better. Seems like cards that are 30 MB/s can't quite keep up, so we'll likely have to stick with cards that are AT LEAST 45 MB/s and up. Formatting them as exfat helps with the 4 GB file limit, as well.
I've posted a couple vids in the share your vids forum, and I'll upload some dng's or prores 4444 files if anyone is interested. Drop your suggestions, bug finds, preferred settings, etc in here, and I'll keep this original post updated as new developments come along.
Download various builds here (top is newest)-
Obsolete link removed - Please use the official nightly builds //Audionut
This build is still in testing, PROCEED WITH CAUTION.
Update: The newest build has Dual Iso, ETTR and file manager modules. The nightly 600D build now has raw enabled as well, but some users are reporting corrupt frames.
what about lv hack on vs off?
Quote from: 1% on May 18, 2013, 04:33:31 PM
what about lv hack on vs off?
Just trying it. Not noticing any improvement in frame numbers TBH. The LV hack also doesn't seem to work in 3x crop and crashes the camera if you try to playback the last raw while the hack is still enabled.
Other than that, raw seems to be working as well as 'Edmac Popin' :)
hi,
is the 60D has the same SD capabilities as the 600D or is it on a higher speed?
and i wouldn't mind to test it out on my camera (60D) but is there some build for the 60D?
thanks, you guys are doing a great job for all of us.
@cobyalon Not yet
Nothing for 60D yet as far as raw goes. There may be a thread already on the subject where you can follow it.
no more pink frames tho (haven't seen any more myself)? for me write speed went from 19/20 to 20/21, didn't try in crop mode. yesterday couldn't do 960x540 very long, today got more frames from that.
Tested in 3x crop mode... file played back/recorded fine got 20MB/S and like ~100 frames 1280x540
@1% - I'm still getting the odd pink frame maybe once in 4 shots.
Just tried again and playback doesn't seem to work when in 3x crop mode. It shows the fame count, gets to about 6 frames, flashes then shows live view. Need a battery pull to do anything.
Ok, I did a few more shots and I am getting an increase in frames with the LV hack enabled but it's only once in 4 or 5 shots shooting the same thing. I've got it set to stop recording when the buffer fills but it appears that when the buffer fills it resets giving me another 1-2 secs so shooting exactly the same thing, same settings etc yield different amounts of frames. i.e. some shots are 145 frames and others go above 200.
Also, with the hack enabled it doesn't always freeze LV... never freezes in 3x crop
For me the LV always bounces but its frozen/disabled.
I do have the same issue where first shot will be less frames and consecutive shots will have higher counts... this is from memory allocation I guess.
Tried to play back in crop a few times. First time OK, played back 80 frames... Recorded new longer clip second time played back a bunch of frames but LV was still showing in the background and screwing things up... 3rd time screen black. So yea, something not perfect here.
Although the LV hack is intended to squeeze a few more frames I can't see myself ever using it TBH because I like to see what I'm shooting.
Is the 600d using all the available buffer? I noticed most of my raw files are around 80-85mb (when frame skipping is off) except the ones where I get more frames. Is that because you had to allocate the memory evenly into 3 chunks or something? Can it be pushed a bit further?
The sraw should be giving you 104 available. So 3*~32 is 90. I'd love to kill more photo stuff and get even more memory back.
Maybe also different/rest of edmacs need to get killed. Like kill everything except LV. Wonder if its possible to kill HD buffer and leave LV buffer. Just started this morning so I guess we'll see.
BTW, slight OT but I was just looking at the specs of other Rebel cams on DPreview. The 500d can shoot 11x20MB+ raw photos before slowing down compared to the 3-4 on the 600d. So it must have a bigger buffer (at least 200mb). Could that potentially out perform the 600?
+ they are dirt cheap now :)
Maybe kill everything that's not needed for raw video. A kind of Tragic Lantern LITE version ;D I have a different card for stills and will probably use my new one (when the f**king thing gets here) purely for raw video so no problem having a stripped down ML for this very specific purpose. I only need histogram and fps override.
Quote from: 1% on May 18, 2013, 06:05:46 PMWonder if its possible to kill HD buffer and leave LV buffer.
Nah, the LV one is downsampled from the HD one...
Quotestripped down ML
It has around 500K of code, plus around 1M of memory, so... nothing to gain.
QuoteI'd love to kill more photo stuff and get even more memory back.
I would start by changing the 60D boot method, then locating canon shoot malloc calls and cache hacking them for a much smaller size.
I don't think 500D has exfat support. It may have more space for raws but who knows if that space is available for shoot_malloc without hacks.
I dont' think it needs a lite version, just hacks on/hacks off maybe with a reboot. Not so easy to kill everything and not get an error 70/dead LV, etc. I guess for more memory would have to cache hack things starting in resource manager at boot time?
Quote
I would start by changing the 60D boot method
60D booth method into RSCmgr = no display at all.
Im actually extremely happy with the current results, gonna try to throw together a compilation of footage while I'm at the beach.
One feature that would put this over the top would be to have the ability to delete or preview each of the raw recordings, seems to me thatwe can only preview one right after we record it, right?
Anyways, as of right now its completely useable. Oh and bumping up the shutter speed to 1/190 or so gives the footage a very sharp, crisp look.
@N/A - Yes, I noticed the same thing. I always get sharper images at higher shutter speeds. It's at the expense of filmic motion blur but not noticeable on most shots. I was thinking RSMB might be useful for adding motion blur back in but that's another expense
Yea, would love to be able to at least delete. That way my card isn't filling up with raws I just shot to test write speed. I don't know if it can preview multiple files or only the last one but should definitely delete.
So, this 21 MB/s limit will be removed?
How? That is max speed for controller?
The controller is limited to 21 MB/s? So, if I use a 95 MB/s SD it is totally pointless?
Not totally pointless... you'll have 21MB all the time instead of 21.... 20... 19 18, slower and slower.
Doesn't have to be 95MB/s other UHS cards will work too.
Ok, so even in the future we wont be able to shoot higher than 640*480 or so?
960x480 or 500 and eventually hopefully a bigger buffer.
Hmm, sad news :-\
I need to invest in Film Convert and run the raw footage through it. The demo works wonders on the vids.
Also, the raw histogram is indicating just over 11 stops of DR, is that pretty spot on?
From what I see, up-rezzing in AE from 1152x480 to 1280x533 doesn't have any effect on quality, but this is looking at it on a 13" MacBook, have to check it out on the iMac and be certain.
Seems so... I think the histo is mostly right..
And sad? Before you only had H264.. I can't violate laws of physics for you.
;D lol
Quote from: 1% on May 18, 2013, 07:22:59 PM
960x480 or 500 and eventually hopefully a bigger buffer.
What? Even with the current "Edmac Popin" build i'm able to record continous at 24 fps with these resolutions:
- 720 X 720
- 1280 X 400
- 960 X 540
(With sound and frame skipping both turned off)
I have this SD-Card: 16 GB 45 MB/s SanDisk SDHC | Amazon (http://www.amazon.com/SanDisk-Extreme-Secure-Digital-Capacity/dp/B007XZKMVM/ref=cm_cr_pr_product_top)
The dynamic range of theses DNG files is just insane. I wasn't able to get anything overexposed yet!
You don't have to violate the laws of physics. But we should violate the donation button! Even if my 600D wouldn't have raw video at all I still would love you for showing what the 5D Mark III is capable of. I was just thinking "Well, I guess I'll leave Canon and buy a Blackmagic soon" a couple of weeks ago. And then you guys came up with that amazing raw stuff! You can be really proud on what you've done. :D
I love that we have this on our 600D's. I've been quietly lurking these threads, mainly because I don't know much and have 0 useful information, but I'm curious if our HDMI or USB ports on the cam are usable for anything? I haven't really seen anything about our HDMI speed, and we do have video output through the USB if I remember correctly? Just throwing ideas out there for the smart people, even though I'm certain that someone already answered both of these options somewhere.
I guess depends on the card you have what resolution you'll get. That is what has worked for me, I've shot more on 6D since its UHS.
USB and some WFT hack maybe. HDMI modifies image data so probably not.
nice, I figured something was wrong with HDMI since nobody really talks about it. Thanks for the info
Shutter speed may have been a little too high, still finding the sweet spot settings. I apologize in advance for the shakiness, but at least it lets us know that there's no screen wobble or jitters.
what were you shooting this at under raw settings? I still get random magenta and skipped frames with 960x540. are you running LV in 720 and shooting with 640x360?
Hope, this is the right thread for my observation:
With the latest raw module in EatLV.zip, i get corrupted frames every other frame.
frame 1 is perfect, frame 2 corrupted, frame 3 ok again ...
Quote from: southernstyle on May 19, 2013, 12:58:08 AM
what were you shooting this at under raw settings? I still get random magenta and skipped frames with 960x540. are you running LV in 720 and shooting with 640x360?
Today I shot some short clips to see how well 960 X 540 performs against 1080p H.264 and I haven't seen any magenta frame. And I've just turned the skipping off because I can record continously until the file size reaches the 4 GB limit. So why should I need skipping? :D
I was in 1080 X 1920 24p Movie Mode with "FPS override" turned off. Also every option of "Global Draw" was turned off. And I didn't use audio recording either. I put a link to my SD-card in my earlier post.
So far, everything works quite nice :)
Quote from: southernstyle on May 19, 2013, 12:58:08 AM
what were you shooting this at under raw settings? I still get random magenta and skipped frames with 960x540. are you running LV in 720 and shooting with 640x360?
640x480 mode, 1152x480 raw rez uprezzed to 1280x 533 in post.
Where can i find the patch?????? looked everywhere...... almost! :) Please help!
Just gave the cam a good test and recorded a couple of files. Most of them worked and post-processing them is so much fun. However, some files were corrupt. raw2dng reported:
QuoteError: This ain't a lv_rec RAW file
ls: *.dng: No such file or directory
Nothing converted
this happened for 2 out of 9 files. Settings were the same for all files:
640x480 mode, 1152x480 raw
Are they over 4GB? You need the linux raw2dng
Read something about 60fps recording on 5dmk3...
Tried on my 600D and got almost instant Err70 - guess it wont be possible
anyways i got an raw-file with 39frames, 4 of them were not pink, 3 with a black bar, the first one was good
60fps raw are pretty uninteresting for devs on 600d i guess, but just wanted to say^^
Edit: 50fps seem quite doable... low res but, wow!
Record at 720P and you get 60FPS... I guess someone stumbled on that.
Quote from: 1% on May 19, 2013, 03:05:24 AM
Record at 720P and you get 60FPS... I guess someone stumbled on that.
yeah i know ;) but i tested that earlier, also got err70 in not a sec... just thought it would be possible now, sacrifcing a LOT of res ;)
50fps 640x320 worked... I dunno try overriding it higher/lower.
Hello all,
this is my first post here, and I am interested into buying a Canon camera, and actually maybe a 600D, so here I read this topic with interest.
So I get that you can't record a 1080p raw video in 24ps, but you can record much lower resolution at 24fps (or even higher fps).
What about the opposite? If I stick to 1080p (1920×1080), up to which frame rate can one consistently record without skipping frames with the Canon 600D? Has anyone tested?
Thanks!
Quote from: CFP on May 19, 2013, 01:22:39 AM
Today I shot some short clips to see how well 960 X 540 performs against 1080p H.264 and I haven't seen any magenta frame. And I've just turned the skipping off because I can record continously until the file size reaches the 4 GB limit. So why should I need skipping? :D
I was in 1080 X 1920 24p Movie Mode with "FPS override" turned off. Also every option of "Global Draw" was turned off. And I didn't use audio recording either. I put a link to my SD-card in my earlier post.
So far, everything works quite nice :)
I have that same card, is there a certain way to format it to give you no frame skipping? I only get 20.1 mb/s max out of the card for some reason. I turned off everything and still get frame skipping. I keep seeing the buffer benchmarks, is that something I should be changing? Sorry for all the questions, I'm just lost on why I can't seem to get this working
Quote from: 1% on May 19, 2013, 02:21:03 AM
Are they over 4GB? You need the linux raw2dng
no, not even close. They are all below 1 GB. I ran the mac gui-version, I guess I'll try the command line version.
Hello!
Guys, the latest modules (after 05.16.2013) are not running properly on my 600D. By doing load the modules latest, I can not access the menu "L" (last icon) and also can not choose the resolutions on the menu RAW... any idea what it might be?
Just installed the EatLV version and was able to quickly test it out before bed here. I think I found that because I must record at low resolutions with my card it seems my dead pixels in my camera are very apparent. Not sure if this avoidable in the future or if that will simply be a trade off, but just wanted to mention it in case it hasn't been brought up. Either way, I hope to test it out some more soon enough, thanks guys!
http://www.facebook.com/photo.php?fbid=607134532630198&set=a.534794789864173.125252.209823419027980&type=1&relevant_count=1 (http://www.facebook.com/photo.php?fbid=607134532630198&set=a.534794789864173.125252.209823419027980&type=1&relevant_count=1)
I have some dead/bluish pixels in RAW mode as well. I don't see them in h.264 video mode or taking pictures in RAW. Anyone could tell me what are they?
(https://imageshack.us/scaled/large/689/pixelspqno.jpg)
hello i am new on the forums and just got a 600D, i have ML installed but i cannot see a RAW video tab in the menu? can someone help me ?
@1% - I've been thinking more about the buffer size and I'm probably well off the mark here because I don't fully understand the buffer's relationship to raw video but, if sraw is giving us 106 on the 600d wouldn't 5x21 be better as that's the limit for SD writing and uses nearly all the memory? Not sure if this would benefit in any way. Just curious :)
Just tested RAW files for compression. 7zip gives 60% of volume (using Ultra settings), and fast LZ4 gives 84%.
So, if sometimes someone implements on-the-fly compression of RAWs - we can gain a bit more resolution on our slow SD cameras.
Compressed CinemaDNG would be the way to go but that would take a lot of processing power. I don't think these cameras can handle it, especially the 600d... but then again, I never thought raw video would be possible :)
What about a 650D within UHS-1.Can 650D do more than 600D, which is limited to 20M/S.(sorry for my weak english ::))
Quote from: lucifier on May 19, 2013, 01:31:44 PM
What about a 650D within UHS-1.Can 650D do more than 600D, which is limited to 20M/S.(sorry for my weak english ::))
It should support UHS-1, so it should be faster. Glad if someone tests if it's true, cause I want to exchange my 600D -> to 650D now.
yeah, i was wondering about that either...i have 60D but if 1920x1080 RAW video works on the t4i i'll go get one right away :)
it seems that it'll work based on its faster CPU and the faster SD capabilities. maybe someone of the devs can confirm that ...
Or, mentioning compression, if we can compress (losslessly, or lossy) our footage to 5 bits-per-pixel - then our 22MB/s 600D/60D/etc can handle 1920x810 cinemascope @24fps.
I'd mentioned some algorithms here:
http://www.magiclantern.fm/forum/index.php?topic=5247.msg37207#msg37207
And I don't worry much about resolution, it's more about image crop - on 1280x400 (the maximum I could do on my 600D/UHS-1) - I get only a small center crop of already small 1.6x cropped sensor. Yes, BMCC has ~2.3x crop :-D, but on 600D+18mm - it's still a bit too tight FOV, and with this crop - it's even more tight.
Quote from: Kakuda on May 19, 2013, 09:33:54 AM
I have some dead/bluish pixels in RAW mode as well. I don't see them in h.264 video mode or taking pictures in RAW. Anyone could tell me what are they?
(https://imageshack.us/scaled/large/689/pixelspqno.jpg)
They are gone if you process the Images with ACR
Quote from: vicnaum on May 19, 2013, 01:44:05 PM
It should support UHS-1, so it should be faster. Glad if someone tests if it's true, cause I want to exchange my 600D -> to 650D now.
The controller caps at 40MB/s , so you can't do 720p (1280x560)
i figured it out , but can someone tell me how these the magenta could pop up less frequent is it possible to reduce it?
for this clip i was shooting at 1120x400 with a SANDISK 8GB 95mb EXTREME pro
https://vimeo.com/66497095
It seems that the video "RAW" isn't much the same as the CR2 raw that's used for photo. I don't know is it on all cameras, or just on 600D, so posting here in 600D thread first.
I've shot the same frame in CR2 raw "M" mode, and then in video RAW mode (with the same exposure, f-stop, and iso).
Here are the DNG video raw and canon CR2 (as opened in Lightroom):
(http://img832.imageshack.us/img832/9987/201305191637.jpg)
http://img832.imageshack.us/img832/9987/201305191637.jpg
Only the white balance was changed to (5200, -2) to be equal in both images (somehow video white balance is always 5500, +55, and I don't know how to change it).
Then, if I turn the exposure all the way up (+5 EV) on both images, I see strange things happen:
(http://img713.imageshack.us/img713/903/201305191639.jpg)
http://img713.imageshack.us/img713/903/201305191639.jpg
First - the shadows are tinted green (which can be slightly fixed by Shadows Tint slider in Camera Calibration tab, but not completely).
But the second, and most important - we completely lose shadow details in deep blacks.
And that can't be fixed by any slider - contract, blacks, curve, etc... there seems that there is no information there.
One possible reason for this can be the absense of camera metadata (i.e. camera calibration profiles - DCP) in DNG.
Lightroom doesn't allow using custom DCP, but I tried to import the "Adobe (Canon EOS 600D)" calibration profile into the DNG through RawTherapee - and it all looks the same - almost nothing changes - the shadows remain black/green.
(please scroll the message to the right - the blacks part of the image are hidden by the forum)
@1% - http://www.magiclantern.fm/forum/index.php?topic=5494.msg37153#msg37153 ::)
I'm having the same issues as well, wb and green shadows are pretty easily fixed but pulling up shadows and doing major exposure work is very limited. Maybe the issue is raw2dng, I wonder if dng burst files have the same issues...
I'm 99% sure the skip values are wrong in raw.c, so the black level is overestimated. Enable RAW_DEBUG_BLACK in raw.c and chdk-dng.c and post some dng silent pictures.
Heh, I was just going to say but black level wasn't being detected right for a while. Skip values too high? Because I'm not seeing black borders on the images.
This is skip I have
skip_top = 22; //zoom ? 0 : 22;
skip_left = zoom ? 0 : 148;
skip_right = 0;
skip_bottom = 0;
Also... before we blame skip values:
raw_info.black_level = (2048+32) ;
Otherwise raw histo looked wonkers.
Yes, black level is wrong because skip values are wrong.
If skip is too high, you will not see black borders, obviously. If skip_left is 0, black level will not work at all.
I hard set black level to 2048 before... with new fix its working and magenta cast is gone... on 6D magenta cast is still there.
Ok, so there is a problem with skip level @ zoom, skip top should be 4. Skip left still 0 tho.
Can you post a dng?
Wow, quick fix :-)
Now it works okay:
(http://img827.imageshack.us/img827/2815/201305191758.jpg)
Still needs a correct camera metadata or embedded calibration profile for the greens to be gone, but that is raw2dng job I guess. I can't find any software that can embed the profile into DNG...
Here's the dng:
http://www.sendspace.com/file/vtc3h9
Not 100% fixed yet... I found some extra skips.. was a little too small by like 4px.
skip_top = 26; //zoom ? 4 : 22;
skip_left = zoom ? 0 : 152;
skip_right = zoom ? 0 : 2;
skip_bottom = 0;
Here is the kicker tho... zoom mode has no left skip for real, image data all the way to the end. Black level detection fails and now all pink.
Here is a 5x zoom DNG with these values:
http://www.qfpost.com/file/d?g=wqquewcxi (http://www.qfpost.com/file/d?g=wqquewcxi)
Should I just skip 2px so the calculations aren't done on 0
That didn't work.
Also here's my RAW/H264.CineStyle comparison:
(http://img209.imageshack.us/img209/329/201305191817.jpg)
Yes, raw is much more crisp, but it's also very cropped on 600D. And still doubt what is better in matter of resolution: 1920x1080 h264 vs 960x540 raw.
And right now I can't see any improvements in dynamic range here - CineStyle is really flat and gives pretty much all range it can give from sensor, and in raw - noise eats it all (high-resolution raws (CR2) compensate noise with resolution).
On 5dmk3 raw is superior of course, and on 600d - well, need further testing (if die Sache lohnt die Mühe nicht).
8 bit 4:2:0 vs 14 bit 4:4:4... H264 isn't better for sure but the resolution cut is an issue. Maybe skip top needs to be used for black level instead?
@1% - re: resolution. How about the buffer thing I suggested above?
http://www.magiclantern.fm/forum/index.php?topic=5494.msg37153#msg37153
(speculation of course)
Quote from: southernstyle on May 19, 2013, 05:00:22 AM
is there a certain way to format it to give you no frame skipping? I only get 20.1 mb/s max out of the card for some reason. I turned off everything and still get frame skipping.
Quote from: southernstyle on May 19, 2013, 12:58:08 AM
what were you shooting this at under raw settings? I still get random magenta and skipped frames with 960x540
You haven't set "Pic Quality" to "SRAW" yet, right? Do it and reboot your camera (It's in "Shoot" tab). This will increase the size of your buffer on the 600D.
And since a small buffer results in skipped and magenta frames, the increased buffer size should help you :)
Is it possible, that the issue with the green shadow areas also changed the green tone itself? Because in every H.264 vs RAW comparison I saw so far the color of trees and grass looked quite unnatural in the RAW shots. Or is that just the difference between 8 and 14 bit? :D
While recording I'm also getting 20.1 Megabyte/s. But according to the card benchmarks 21.3 Megabyte/s would be possible too.
If the EOS 650D can get up to 40 Megabyte/s it should handle 1280 X 720 at 24 fps (about 39 Megabyte/s) right? 700D is probably the same ...
Quote from: vicnaum on May 19, 2013, 05:34:42 PM
And right now I can't see any improvements in dynamic range here - CineStyle is really flat and gives pretty much all range it can give from sensor, and in raw - noise eats it all. [..] (if die Sache lohnt die Mühe nicht).
What software did you use to process the raw files?
I haven't tried cinestyle yet. But I compared H.264 with "Neutral" Picture Style and RAW. I overeposed a lot of shots to see how much I could recover in post. On one shot the sky was completly blown out and I was sure that there would be no way to get it back. And for H.264 that was true but with the RAW video I was able to recover the whole sky and even the clouds (Using Lightroom 4. Maybe your software doesn't handle the DNGs so well?) ... So there's a huge difference between H.264 and RAW. At least without cinestyle.
I'll see if the black level fixes helped with the green tones and how much worse cinestyle is compared to raw in terms of dynamic range ...
And are you German? :)
Sorry for this second post :-[
QuoteShould I just skip 2px so the calculations aren't done on 0
You have a valid top bar, so we can use that. Check repo.
You have 106MB... I have 104MB... we need like another ~30MB somehow
21MB buffers would slow down writes and not sure how the chunks are now since its picking all chunks >16MB
For everyone that says 650D is better... the AF points are burned into the DNGs and not easy to remove... plus all the other issues that cameras has (in addition to being EOL)
*Thanks a1ex... its 100% now for video/silent DNGs.
Photo Raw histo needs a check for skip right I think.
Quote from: 1% on May 19, 2013, 05:53:34 PM
For everyone that says 650D is better... the AF points are burned into the DNGs and not easy to remove... plus all the other issues that cameras has (in addition to being EOL)
Good to know. Thank you for the warning. I was really thinking about "upgrading" :D
Well. 1280 X 400 RAW video is still nice enough for the moment.
@1% - Thanks for the reply. Doh, dunno where I got 106 from :-[
First I had 103... then I had 104 and you have a higher amount. Also people are getting the flip/flop with recorded frames based on memory. So basically SRAW amount given back isn't the same all the time.
@1% - understood :)
Fixed already? Hot damn. Gonna test it on the beach later.
@cfp: And not to mention, Cinestyle is utter shit on skin tones.
Got a bug.
600d latest TL 2.0
Modules ->
Load modules now - raw_rec ok
Unload modules now - beep and raw_rec unloaded
Load modules now - ml freezes, no reaction to any key
Turn camera off - camera turned off
Turn camera on - no reaction, red diod blinks
Turn camera off - red diod blinks
Battery out, in - works again
Not sure module unloading works on any camera.
Ah, ok.
Quote from: CFP on May 19, 2013, 05:51:29 PM
You haven't set "Pic Quality" to "SRAW" yet, right? Do it and reboot your camera (It's in "Shoot" tab). This will increase the size of your buffer on the 600D.
And since a small buffer results in skipped and magenta frames, the increased buffer size should help you :)
Thanks a bunch, that's exactly what my problem was. I had no idea that setting was in there, guess I can go test it out for real thanks to you.
Hello everyone! I have a problem with large RAW file. When I drag it to raw2dng.exe it says "This ain't a lv_rec file". I think file is not corrupted, since it played back in camera. File is 13 Gigs, recorded in 960x400 with sound, card is pretty fast Trancend 16Gb(UHS-1). Is there a way to fix this?
Use the linux raw2dng instead of windows or mac.
Quote from: southernstyle on May 19, 2013, 07:34:21 PM
Thanks a bunch, that's exactly what my problem was. I had no idea that setting was in there, guess I can go test it out for real thanks to you.
I'm glad that helped you :)
But keep in mind that you have to switch it back to "RAW" or "LargeFine" before you start shooting stills. Otherwise they may be corrupted.
And be carefull, taking out the SD-Card doesn't reset this setting. It will stay "SRAW" and you can't change it from the Canon menu.
But for video it's really nice when you're using "high" resolutions.
I just did some testing and Cinestyle is better then RAW in terms of shadow recovery because the RAW images get extremly noisy when you bump up the exposure in post. But the Cinestyle is very, very weak in terms of detail. It's even worse then Neutral Picture Style.
And when you try to recover the highlights, Cinestyle doesn't really help at all. Of course, you have a little bit more detail in the highlights then with Neutral, but everything that's blown out stays blown out. With the DNG files I can get back everything I want. And since I overexposed the shot, there was no noise at all. And even in 1280 X 400 the DNG files had much more detail and sharpness then the cinestyle could ever have.
In daylight I would prefer RAW instead of Cinestyle. Just expose right to your subject and bring back sky and highlights in post. Or overexpose your subject a little bit, if there is no sky in the background, to lower the noise. Fixing it won't be any problem (At least not with Lightroom 4. Other programs may have different recovery abilitys).
QuoteAnd still doubt what is better in matter of resolution: 1920x1080 h264 vs 960x540 raw.
Try to compare 1920x1080 h264 with 1280x434 raw (shoot in canon 720p) upscaled to 1920x1080 (without borders)
Quote from: CFP on May 19, 2013, 05:51:29 PM
You haven't set "Pic Quality" to "SRAW" yet, right? Do it and reboot your camera (It's in "Shoot" tab). This will increase the size of your buffer on the 600D.
And since a small buffer results in skipped and magenta frames, the increased buffer size should help you :)
Is it possible, that the issue with the green shadow areas also changed the green tone itself? Because in every H.264 vs RAW comparison I saw so far the color of trees and grass looked quite unnatural in the RAW shots. Or is that just the difference between 8 and 14 bit? :D
While recording I'm also getting 20.1 Megabyte/s. But according to the card benchmarks 21.3 Megabyte/s would be possible too.
If the EOS 650D can get up to 40 Megabyte/s it should handle 1280 X 720 at 24 fps (about 39 Megabyte/s) right? 700D is probably the same ...
What software did you use to process the raw files?
I haven't tried cinestyle yet. But I compared H.264 with "Neutral" Picture Style and RAW. I overeposed a lot of shots to see how much I could recover in post. On one shot the sky was completly blown out and I was sure that there would be no way to get it back. And for H.264 that was true but with the RAW video I was able to recover the whole sky and even the clouds (Using Lightroom 4. Maybe your software doesn't handle the DNGs so well?) ... So there's a huge difference between H.264 and RAW. At least without cinestyle.
I'll see if the black level fixes helped with the green tones and how much worse cinestyle is compared to raw in terms of dynamic range ...
And are you German? :)
I use Lightroom 4 for processing. "Neutral" for sure will blow out everything - lights and shadows, cause it's contrasty.
My point was - I'm shooting a bright window with sky, setting the exposure to the top I can (look at the histogram and false color) - setting the exposure right where the brightest clouds start to overexpose. That means that I can't get them back - nor in h264, neither in raw (histogram now has RAW clipping mode, as far as I remember) - cause it's over the top already. And then I look at the shadows inside the room - how Cinestyle handles them, and how Raw does. The result is on my screenshot - I can't recover more highlights from raw, as from the cinestyle. But the shadows are better in cinestyle, cause the camera does some noise removal or what... and on raw we have individual pixels and banding, and low resolution not enough for a good shadow details.
But, there's one little "but" in all my thinking above.
The point where I was wrong is - I really CAN recover some more highlight from RAW. Even if there is some clipping (or maybe histogram isn't so RAW afterall? need to check this moment).
(http://img35.imageshack.us/img35/1758/201305192158.jpg)
The top one is RAW, and bottom one - cinestyle (you can see the sky is white and I can't do anything to it).
So. Need further testing.
The one thing I can almost surely tell - testing shouldn't be done on one exposure, cause it seems there is some headroom in RAW.
P.S. Nope, I'm russian :-)
Quote from: Rush on May 19, 2013, 09:02:53 PM
Try to compare 1920x1080 h264 with 1280x434 raw (shoot in canon 720p) upscaled to 1920x1080 (without borders)
canon 720p - is it 720p 60fps or some other mode?
Remember using 720P mode you get a downscaled raw image vs 1080P... So better comparison for 720P is 720P. If 720P raw winning or the same as 1080P H264 then what's better?
Quote from: vicnaum on May 19, 2013, 09:03:58 PM
P.S. Nope, I'm russian :-)
Quote from: vicnaum on May 19, 2013, 05:34:42 PM(if die Sache lohnt die Mühe nicht).
I know it's totally off topic but ... What's the deal with it?
"die Sache lohnt die Mühe nicht" is German ... I'm just curious why a Russian uses a German phrase in an English forum ;D
But I see your point. You might be right with the dynamic range ... Or wrong. I don't know. How much steps of dynamic range do the DNG files really have? And how much does the Cinestyle have? Is there a way to measure easily?
Quote from: 1% on May 19, 2013, 09:23:33 PM
Remember using 720P mode you get a downscaled raw image vs 1080P
I thought that in 720p mode there's just even more line skipping then in 1080p? And because of that the image appears streched. But it's just missing lines in horizontal resolution. If you resize it in post to 1280 X 720 you should get a pretty nice 720p image, right?
I haven't tried it yet. But it's a littly bit like recording 720i instead of 720p ...
But I think the problem with comparing the different resolutions is that most people don't change the focal length if they compare 1920 X 1080 H.264 and something like a 1280 X 434 (Upscaled to 1280 X 720) RAW video. But they should, since the cropfactor changes ... Otherwise RAW will
always win when you compare both at 100 % view ;D
How's the 550D looking, guys?
Quote from: CFP on May 19, 2013, 09:43:00 PM
I know it's totally off topic but ... What's the deal with it?
"die Sache lohnt die Mühe nicht" is German ... I'm just curious why a Russian uses a German phrase in an English forum ;D
It's just a good old proverb, that I don't know in English :)
Well, here are the dynamic range tests:
(http://img832.imageshack.us/img832/9494/testis.png)
http://img832.imageshack.us/img832/9494/testis.png
Looks like we have the winner :-)
Without Highlight Tone Priority - cinestyle is not even close to what RAW is.
And with it - it's still too noisy and blurry in the shadows, while the RAW is more clear (even with Lum&Color noise reduction applied in Lightroom).
Now I just need to test it in that ^^misterious^^ 720p mode, and it finally gets more clear to me.
Niiice! These RAW videos are just insane. Thank you for testing it. Maybe I'll try something too ...
Managed to try the 720p mode (finally!).
The results are even more greatful:
H264: http://img43.imageshack.us/img43/7394/test2h264.jpg
RAW: http://img197.imageshack.us/img197/4582/test2raw.jpg
H264 is 1920p.
RAW resolution was: 1600x400 (that's 60% shrinked of 1600x664), and then it was streched to match the 1920p h264 video.
And I think, that even after so much streching - there is still more sharpness in raw than h264!
Well, now the only thing left is - getting a stable recording without frame-skipping, and we can move to tests on field (although I already shot some 1280x400 field tests today, will show later).
P.S. btw I get only trash&garbage when I set 1740px resolution in RAW. So 1600 is max for me.
QuoteIf you resize it in post to 1280 X 720 you should get a pretty nice 720p image, right?
Pretty much...
Zoom > 1080/640P > 720P
Zoom is only 1/2 the height since its a ~1:1, 720P you get more of the vertical at the expense of canon resizing the raw even more.
Holy shit!
I wonder what the 5D Mark III guys are getting when they upscale their 1920 X 1080 RAW files?
(Not that you really need more ... It is just amazing to see what the Canon DSLR are capable of!)
You can't scale a 1600 X 400 image to 1600 X 664 in Lightroom ... So what did you use? Photoshop? :)
This is still sooo excited!
Quote from: CFP on May 19, 2013, 11:13:38 PM
You can't scale a 1600 X 400 image to 1600 X 664 in Lightroom ... So what did you use? Photoshop? :)
Yes, sure, I scaled and matched them in photoshop.
Here are the promised field tests:
(http://img577.imageshack.us/img577/6980/fieldtestolga.png)
http://img577.imageshack.us/img577/6980/fieldtestolga.png
(http://img844.imageshack.us/img844/6554/fieldtestsunset.png)
http://img844.imageshack.us/img844/6554/fieldtestsunset.png
Shot at 1280x400 (1920p mode, so without streching).
Compared to H264 1920p, scaled down in photoshop to match the size of raw.
So now I must admit that raw is fairly usable, even on 600d. Now just need to make it stable, etc... And if you guys manage to do some compression - it will be flawless.
And btw, need to fix those dead pixels somehow (they are seen even in lightroom)
"Tried" to cover the cropfactor too... just quick and dirty, nothing excact!
(http://i.imagebanana.com/img/6rt2cldv/thumb/600D_RAW_Comparison.jpg) (http://www.imagebanana.com/view/6rt2cldv/600D_RAW_Comparison.jpg)
To me, RAW cleary won the race! even with that extreme streching!
Only problem are those "baked in "corrupt" Pixels"
Havent had them in EatLV-Version i think, but not completely sure, could als be because the lower iso i tried yesterday
But about noise... Cinestyle owns it... didn't do any noise reduction to cinestyle.. but for the raw as you can clearly see
The dead pixels add character ;D
Neat video is good for noise btw.
Yeah i know ;)
Just threw both frames in PS and only noise reduction i did was in ACR, in wich i didn't touch the cinestyle file ;)
Yes, noise is a real problem at the moment. This weird LiveView noise is even uglier then normal noise.
Overexposing a bit and turn down the exposure in post seems to work very well to avoid noise. But I bought a DSLR to be able to shoot even in low light so I really hope there's a solution for that ... And of course the colorfull pixels are a little bit distracting too.
And we also need the missing camera profiles. The green tones still look a bit strange in my opinion.
But thinking back to three weeks ago where we just had H.264 and nothing else ... It's really awesome how much progress has been made and how great the results are. Even with the very cheap EOS 600D, an entry level DSLR (Mainly a photo camera!), we are now able to record (fake) 720p raw video at 24 frames per second. That make's the 600D one of the best video cameras under 2000 €!
I mean: The dynamic range is huuuge, the details are stunning, just like the colors. There are no motion artifacts and the freedoms in post are incredible!
I'm sure the issues above can be fixed. Only thing that's left and that will stay forever is rolling shutter.
I think that, for the noise, RAW beats regular recording when you do not need iso of 6400, but didn't test yet, especially cuz we can overexpose
regularly i never go above iso 1600 for video!
"dead-pixel" fix, and the ability to delete recorded files would already make it perfect for me ;)
i just hope that canon doesn't close any door for the really magic- lantern
The noise and dead pixels are all there for H264.. canon just does things to take them out like noise reduction and defect detection.
The bad pixels come out easily with acr spot removal.
Hi
I made a simple test that I would like to share with you.
Not a fair test because the framing was different and I had to stretch the RAW footage a LOT to match the H.264...
Quote from: 1% on May 20, 2013, 01:39:57 AM
The noise and dead pixels are all there for H264.. canon just does things to take them out like noise reduction and defect detection.
then i guess we'll just the same in photoshop!...
Quote from: N/A on May 20, 2013, 01:45:18 AM
The bad pixels come out easily with acr spot removal.
...an automated action in PS kills it after resizing, all automatically :)
made another test... this time in photomode...
killed h264 cinestyle regarding noise, setting iso to 12800 and bring exporure down in post.
also did a second noise reduction after upscaling in acr
need to test this in real life scenarios!
(http://i.imagebanana.com/img/50kgslqu/thumb/ML_02RAW.jpg) (http://www.imagebanana.com/view/50kgslqu/ML_02RAW.jpg)
remember, this was shot on iso 12800!(!!!)
Quote from: gebo on May 20, 2013, 02:25:23 AM
Hi
I made a simple test that I would like to share with you.
Not a fair test because the framing was different and I had to stretch the RAW footage a LOT to match the H.264...
H.264 looks much better here to be honest. Did you up the CBR on this H.264 either?
That's a lot of pink frames. Really low light and high iso.
I also agree that on this video sample the h264 looks more detailed and softer&smoother (cozy) at the same time.
Btw, here's my 1280x400 unstreched raw video sample from fieldtests above:
Quote from: Nspa32 on May 20, 2013, 05:16:43 AM
H.264 looks much better here to be honest. Did you up the CBR on this H.264 either?
RAW in low light has much more noise but at the same time is sharper so it's hard to tell which is best.
Denoising the RAW with neatvideo produced a very clean image without losing detail.
I'm sorry but what is CBR?
Quote from: 1% on May 20, 2013, 06:16:51 AM
That's a lot of pink frames. Really low light and high iso.
The ISO was 800, not that high. Pink frames seem to appear in some clips for no apparent reason. Sometimes I shoot something and there are zero pink frames. The next minute I shoot something with the exact same settings and BANG there are pink frames... no matter if it's ISO 100 or 800... but when they appear there seems to be a pattern, let's say there are 4 pink frames... then 5 seconds without pink frames, then more 3 pink frames, then another 5 seconds ok... and so on...
I haven't gotten pink frames since the first couple builds, even when recording for a few minutes straight.
Faulty card, perhaps?
Quote from: N/A on May 20, 2013, 10:15:17 AM
I haven't gotten pink frames since the first couple builds, even when recording for a few minutes straight.
Faulty card, perhaps?
Not the card. The previous card was slower and I already got pink frames. Yesterday I bought a new one (Sandisk extreme 45 mb/s 16Gb) and keep getting pink frames. Sometimes there are no pink frames at all even when shooting for a few minutes. I turn everyting off in ML menus and have SRAW enabled. I shoot in 1920 24p mode. Am I doing something wrong?
I'm also having pink frames. Same Sandisk 45Mb/s Extreme 16Gb card. sRAW on, Global Draw Off, Hack3D off (cause I can't see what I'm shooting).
How should I format my card? Is in-camera format with "keep ML" enough? Or something else needed?
Try shooting in 640x480 mode. I can have histo on while shooting at 1152x480, fps override on 24.000.
I think I did format the card (sandisk 95) with EosCard before using it, that MIGHT help. I've done a few in-cam formats since then too.
As of now I can manage 364 frames at 1200x480 or 1152x500, 1080 or 480 mode (hack3d mode didn't seem to help). Frames looked good in cam playback as well. Write speeds were around a constant 21.1 mb/s.
Just shot some ocean sunrise footage...
:D
Quote from: N/A on May 20, 2013, 11:16:39 AM
Try shooting in 640x480 mode. I can have histo on while shooting at 1152x480, fps override on 24.000.
640 yes, will try, but I wanted to shot canon720p for stretching...
Quotesetting iso to 12800 and bring exporure down in post.
do you know, that shooting RAW ISO12800 is the same as ISO3200+2 stop exposure up in post? max native sensor ISO of 600D is 3200
Quote from: Rush on May 20, 2013, 03:00:55 PM
do you know, that shooting RAW ISO12800 is the same as ISO3200+2 stop exposure up in post? max native sensor ISO of 600D is 3200
I didnÄt know that! but it somehow looks better than shooting with iso 6400 ;)
So I'm very confused on how people are shooting the RAW videos.
Is the consensus to change the setting in the standard Canon menu to 640x480 60FPS then in ML change the resolution to something like 1280 x 400. Then do a manual frame per second override and set it to 24 FPS?
I ask because I've been shooting at 1920x1080 24FPS and using ML to set reso to 1152x400 which my max continous shooting reso even on my Sandisk Extreme 95mb/s card.
This gives me tremendous results, but the aspect ration is pretty narrow.
How are you guys doing your RAW shooting?
I shot today on 1920x1080p 23.976 default resolution in camera, then in ML RAW mode 960x480, I upscaled it to 1920 in post looks better than h264
I use sundisk extreme 30 mb it doesnt stop or skipp but I got pink frames now and then
You can get continuous 1152x480 on that card.
Right?!
I'm not the only hitting that, am I?
I tried the overexposure trick on some sunrise footage in acr earlier, works beautifully. The new build video quality seems more solid as well, the green/magenta fix did the trick I believe.
Black level fix did that. Its supposed to be more solid with floats now.
Wav encoder is 16 bit, 44.1, 1411 kbps? Wanna run some tests for max rez with sound, if its doable.
Quote from: N/A on May 20, 2013, 03:49:54 PM
You can get continuous 1152x480 on that card. [...] I'm not the only hitting that, am I?
I don't know but on my 600D I only get something between 150 and 450 frames in this resolution.
Continuous recording only works with 1152 X 434 or 1280 X 400 ... At least with 24 frames per second.
Quote from: vfx_junkie on May 20, 2013, 03:26:46 PM
I shot today on 1920x1080p 23.976 default resolution in camera, then in ML RAW mode 960x480, I upscaled it to 1920 in post looks better than h264
Did you count in the crop faktor? Or not? If you haven't, comparing H.264 and RAW in terms of detail is absolutely pointless ;)
Quote from: vfx_junkie on May 20, 2013, 03:26:46 PM
I shot today on 1920x1080p 23.976 default resolution in camera, then in ML RAW mode 960x480, I upscaled it to 1920 in post looks better than h264
I use sundisk extreme 30 mb it doesnt stop or skipp but I got pink frames now and then
Can you please upload some examples ?...
I think wave is 48khz 2 channel 16 bit.
Just tested out the latest build using SanDisk Extreme Pro 95MB/s.
Was able to shoot without any dropped frames at 960x540 and 1280x400.
Great work to all! My first post, just wanted to share.
1%, and how fast is DIGIC on 600D?
I read the sources a bit, and saw that you just flush out the buffers to card via FIO_WriteFile, without altering the stream with CPU in any way.
Just wanted to know - for example, if we run through the buffer, cut the 14bit stream in half (leave the 7 bits, cut the rest), so we have twice less the size, and twice less the bandwidth (and twice, or even less the quality of course) - and then flush it to card - will the DIGIC cpu capable of doing this run-through-array operation 24 frames per second?
If yes - then how much operations do we have time to do in one frame?
I'm still dreaming on some "compression" or maybe line-skipping, or something, to make it fit within 22MB/s...
Its like 200MHZ or so so not so fast... Raw preview does something like this and as you see it drags. Seems worth exploring but then it would still be 8 bit, would it not? Its like back to H264?
Quote from: 1% on May 20, 2013, 06:13:17 PM
Its like 200MHZ or so so not so fast... Raw preview does something like this and as you see it drags. Seems worth exploring but then it would still be 8 bit, would it not? Its like back to H264?
It's was just a hypothetical task. If it can't even skip half the bits, then it couldn't do any more complex compression anyway.
P.S. 1920*1080*24fps = 49 766 400 pixels/sec ~ max 4 ticks per pixel @ 200MHz)
Yup... There's not so much you can do within 4 ticks...
With 720p we are getting a little over 9 ticks from 200Mhz, I don't know exactly how much compression takes but i think canon has some other processor inside only for compression and in future it is possible to take advantage of it
@1% - re: latest build 'Did it break?'
Yes, something did. I have a few raw files where alternate frames are just colored noise. i.e. 1 good frame, 1 bad. This seems to happen at 1280x544 and 1136x480 resolutions
Ok, will check, display filter was broken, maybe from that.
Other resolutions seem to be ok AND I'm getting more frames. On my slooow card, where I was getting 71 frames I now get 90 and there are no more dead pixels that I can see :) Still can't open the DNGs in Resolve though lol. Converting to TIFF does the trick.
Sorry meant: 1152x434 continous.
It's really wide so I've had to step back for framing.
Looking to do something more exciting with my next video and RAW at the1152x434.
Here's my test a few days ago after 1% made this possible to record on RAW on 600D at 960x480.
@1% - re: 'Did it fix' build. Yes it did :)
I finally got chance to pay around and compare the raw footage to h.264 HD. Obviously, the color and highlights of the raw destroy the 8 bit compressed video, but the sharpness of 960x480 compared to 1080p is just off. It was a lot lot closer than I imagined after scaling up in premiere, but there was obvious increased noise and softness on the raw when viewed from about 10 feet on a 32 inch TV (not really concerned with the scientific details of the test, just trying to get a practical feel of the differences).
A few frames of the higher resolution shots were much much closer and I could see myself using raw for cinematic b-roll if the 600d can get to continuous on the higher resolutions. I was looking through the code while trying to think about truncating some LSBs off of the data to get down to like 12 bits or something, but as stated above, that's a lot of operations and a little time to do it (and I also don't have any idea what the data looks like off the sensor).
Find out how to steal more memory and you'll have longer and longer rolls of high res pics.
@1% - re:latest build. At 1280x720 (3x crop) every frame is green. It's not happening at other resolutions
Probably black level related. Have to check if black bars are good in 720P.
Its so damn amazing to see the ML Developers doing amazing things to make the Canon DSLRs outshine other brands and video cams with big price tags, amazing.
A few months back I purchased T4i/650D which is my very first DSLR and I mainly bought for Video Making though later on I found Magic Lantern and was a bit dissapointed that so far T4i/650d doesnt have any ML stuff going on though being very honest I am hopeful that in next few weeks or months there will be a very stable and diversified ML version for the cam (ok I am trying hard to be super positive here :) )
I do want to learn and master the craft of DSLR Ceinmatography and I am sure ML will be one of key supporting tools in this journey for me :)
Thanks ML Team for being so awesome.
@1% - sorry, should have mentioned the green frames were in 1080p mode with crop set to 720p size
So 1080P cropped to 1280x720? Or 3x crop mode cropped to 1280x720?
Take a silent pic @ this resolution and see if there are black borders.
@1% - 1080p mode x3 crop with raw settings of 1280x720. Yes there are black borders on the silent pic
A few mintes ago I posted this question on the wrong thread...so here it goes:
Since shooting larger than 1120x434 RAW at 24fps is causing frame skipping I thought that if I decreased the frames per second then I could increase the resolution. With FPS override on 12fps I was expecting to be able to shoot at 1734x694 (or somewhere near that) but the result I get is dng's with pink noise. It wasn't just noise, it's possible to see parts of an image there but it's not usable.
I wonder if this is happening to others.
Quote from: gebo on May 21, 2013, 08:03:10 PM
Since shooting larger than 1120x434 RAW at 24fps is causing frame skipping I thought that if I decreased the frames per second then I could increase the resolution. With FPS override on 12fps I was expecting to be able to shoot at 1734x694 (or somewhere near that) but the result I get is dng's with pink noise. It wasn't just noise, it's possible to see parts of an image there but it's not usable.
I wonder if this is happening to others.
Also had this idea. On 1740 I get trashy corrupted video. Maybe try 1600.
Great idea on the lower frame rates and higher reso. I'm going to try 720p on lower FPS to see if it is usable.
On another note, I'm getting RAW files that have the error: This Ain't an LV_REC file. I thought that was fixed.
For reference, this happens to 1 out of 3 files and it's happening on the OSX raw2dng.app gui.
Was this fixed for the windows raw2dng.exe application? If windows doesn't have this issue, I might have to switch workflow to windows 7.
@clkvang - I'm on Win 7 64bit and not had that error once. There is also a newer raw2dng.exe available
No chance of getting pink frames, or corrupt pixels for me with latest build from 1%
everythings working perfect, aside from the slow SD-controller... but theres no fix for that
1740 I'm not sure if it works..
Had made some more tests with my 600d and canon720p streched mode.
As far as I understand - in RAW menu you show bitrate needed for clean raw recording (e.g. 25 MB/s), and during REC you show the bitrate that the card is writing with (e.g. 21.0 MB/s). So if the second actual writing speed is less than the first needed speed - then we'll get buffer overflow and => frameskips (at least I've got them). So, when recording 1600x400 I need 25.6 MB/s, and only have ~21.0 MB/s actual speed - then I get around 5 skipped frames every ~1.5s (30mb) of recording.
So, I've got 1440x360 maximum resolution without any frameskips during 4GB recording (I stopped it at 4GB cause I heard it can cause problems if larger than that).
Only one <*..> buffer was used, and sometimes rarely the second one <**.> was flashing for a micro-second.
What's the most important - there are NO pink frames, and NO skipped frames during these >3 minutes of recording! Bravo!!
(and looks that there are NO bad pixels also!)
Uploading to youtube, will post later.
Will try again with some tricky card formatting (using EOStool or smth), maybe can get a bit more of resolution...
Btw, are the resolutions strictly set by the step of 40? I mean 360, 400, 440... Can I do, say, 395?
The resolutions are hard set so they have to be added... better to have a taller image than a wider one, IMO. Sometimes you can get away with using res that says it needs 25MB even though write is only 21 at least for a while.
I'm getting a couple of seconds at 1600x680 (2.35 aspect ratio) on a slow card (10MB/s) and it scales nicely. What can you guys with 21MB/s write speed get at these settings?
I'm not getting continuous 1152x480 with the newer builds, only between 500-600 frames... Hmm, gonna do a full format again.
Definitely better to have more height than width, except for maybe landscape shots. Anyone tried an anamorphic lens to get more width?
@N/A - Andrew Reid has been playing with his anamorphic glass on the 5d3. Looks pretty cool and he's getting 2.5k (width) http://www.eoshd.com/content/10450/2-5k-cinemascope-anamorphic-raw-on-the-5d-mark-iii
Also misalignment of the 1740 might be from that 4K buffer thing. Will have to look at this and the green image issue.
" I'm not getting continuous 1152x480 with the newer builds, only between 500-600 frames... Hmm, gonna do a full format again.
Definitely better to have more height than width, except for maybe landscape shots. Anyone tried an anamorphic lens to get more width? "
whats the best Frame to test out the anamorphic lens 1120x400 ? i have an LA-7200
Here's the 3 minute test:
1440x400 => 1920x800, ISO 640, light source: single 40W table lamp
Added too much grain from FilmConvert, need to be more accurate next time...
Reviewed my other shots yesterday and a couple today - there are still green/pink frames (pic sliced in a half by these colors), around 10-15 frames per 1-2 minutes of recording. Although there were no skipped frames reported and the settings were same (1440x360).
Today I shot a test with 1600x400 again. I can shoot around 170 frames (near ~170Mb) without any skipped frames @24fps = that's ~7 seconds. Nice!
Here are the tests:
First one is super low-light, ISO6400, moonlit clouds, 1440x360, stretched to 1920x800 and then shrinked to 1280x532:
Noise reduction with RAW and Neat Video.
And the second one is sunlit landscape @1600x400, streched to 1920x800 (ratio 1:2.40):
But here you can see horrible aliasing on small contrasty details (that's because of 400 vertical lines skipping).
So, still questionable on detailed scenes. I'd happy to shoot 1280, but it crops the half of sensor (which is already cropped 1.6x by canon). So 1.6x * 1.36x = we get 2.175x crop, so my 18mm lens becomes 40mm - too narrow (as for my taste).
Still need more tests and investigations, though...
Ideally, I'd be happy with 1280x532 (1:2.40 ratio) @24 FPS recording, which covers the whole frame (so no crop). It's 15.58 MPixels/sec. If it'd be 11 bit - then it fitted into 21.4 MB/sec.
So the only (yet unsolvable) problems for these are - how to cover the whole sensor with 1280px image, and how to compress the RAWs to 11bit/pixel.
(P.S. if it's 8bit/pixel - then 1280x720 will fit in 21.1 MB/sec)
Quote from: N/A on May 21, 2013, 11:39:18 PM
Definitely better to have more height than width, except for maybe landscape shots.
Well. I haven't checked how the images look ... The idea is a bit weird, but it works:
In 720p mode, set the resolution to width to 720 and height to 694. And rotate the camera around 90 degrees.
This will give you real 720 pixels height and fake 1152 pixels width, after upscaling (16 : 10 aspect ratio). I can reach the card's 4 GB limit in this resolution at 24 fps, and even 25 fps should be possible too.
The downside of this: It will increase your normal 1.6 cropfactor to 2.4 :(
And like I said, I haven't checked the results yet. Maybe this looks rubbish. But it's at least possible to record continous in this resolution.
Maybe somebody else could give it a try? I have no time now.
@ vicnaum: Wow. The aliasing is horrible :( What did you use to upscale it? Maybe my idea might help a bit, since it avoids horizontal line skipping? I have no idea. Have to try it ...
so I had this idea, it's really usable for ppl who shoot with tripods. So the biggest problem we have is cropping. What if we saved a full size dng every x-seconds and used it as a background to the smaller cropped shots.
So if you are shooting landscape, and you want the center to be your work area, but things in the scene change, but not that much, couldn't you overlay the cropped images to the larger full shot? It wouldn't work for everything, but somethings it could. It wouldn't mess with the buffer too much either, I don't think. Just throwing some ideas out there.
I do a lot of videos from a tripod for other edits that you need it for, like duplicating myself and timelapse, etc. I could see it working for some of the scenes I work with, and possibly for other people. Again, just throwing ideas around that might inspire others.
Quote from: CFP on May 22, 2013, 04:54:39 PM
@ vicnaum: Wow. The aliasing is horrible :( What did you use to upscale it? Maybe my idea might help a bit, since it avoids horizontal line skipping? I have no idea. Have to try it ...
I tried different upscaling methods:
1) Simple AE vertical scaling 166.66%
2) MagicBullet InstantHD
3) MagicBullet Resizer
Honestly - not much difference. This one was done using InstantHD.
The trouble is that the demosaic creates these artifacts - so they are there even before upscaling.
Maybe different demosaic algorithm will help (rawtherapee or smth...), but it's starting to get too complex that way.
P.S. Tried some things to manage this aliasing:
http://img402.imageshack.us/img402/8532/201305221905.jpg
http://img18.imageshack.us/img18/1807/201305221903.jpg
Tried to smooth the image as much as possible:
1) No sharpening in RAW
2) Luminance and Color noise reduction in RAW
3) 2003 RAW process (dunno if it's better, but... It's different)
4) Some RAW grain
5) Gaussian blur 0.3-0.5px (hor,vert)
Anyway, it's still "flashy" on small details, but a bit smoother and there are no colored lines at least. Dunno, maybe I should use a crappier lens or smth (but what can be worse than 18-55 kit?! :-) Maybe something soviet or an old-zeiss).
Quote from: leojames on May 22, 2013, 06:27:29 AM
" I'm not getting continuous 1152x480 with the newer builds, only between 500-600 frames... Hmm, gonna do a full format again.
Definitely better to have more height than width, except for maybe landscape shots. Anyone tried an anamorphic lens to get more width? "
whats the best Frame to test out the anamorphic lens 1120x400 ? i have an LA-7200
I'm not too familiar with anamorphics but wouldn't you want something closer to 4:3 so that you can stretch it out properly in post?
Maybe 720x540?
Read in another thread about using Canon native iso's for raw, so I did a quick test and found no corrupt frames or bad pixels in iso 1600, but 4 or 5 corrupt frames but no bad pixels with iso 1250. Could be a coincidence but it makes sense.
Can someone else test this? Done on the newest 600D build, 640x480 mode, 1152x480, about 200 frames each clips.
Quote from: N/A on May 22, 2013, 06:45:52 PM
Read in another thread about using Canon native iso's for raw, so I did a quick test and found no corrupt frames or bad pixels in iso 1600, but 4 or 5 corrupt frames but no bad pixels with iso 1250. Could be a coincidence but it makes sense.
Can someone else test this? Done on the newest 600D build, 640x480 mode, 1152x480, about 200 frames each clips.
It must be card related. I'm getting 88 frames at 1152x480 and 350+ 640x480 on a 10MB/s card. Some corrupt frames in both. Bad pixels should be fixed in 1%'s last update
Hurray!
Solved the aliasing issue with defocusing the lens juuuuuuuust a bit.
And btw (canon640) 1280x540 => 1920x800 is much much cleaner and sharper than (canon720p) 1600x400 => 1920x800. But more croppier, of course :(
Just tried 1600x680 (1:2.35), it can record only for 2 seconds, but.... The picture is SOOO AWESOME! Detailed, big, crispy!
http://img534.imageshack.us/img534/8125/201305222012.jpg
Just compare it to aliasing samples from my post above, everything is clear without any words.
I'm so jealous to 5D owners right now ;-)
Quote from: vicnaum on May 22, 2013, 07:02:41 PM
Hurray!
Solved the aliasing issue with defocusing the lens juuuuuuuust a bit.
And btw (canon640) 1280x540 => 1920x800 is much much cleaner and sharper than (canon720p) 1600x400 => 1920x800. But more croppier, of course :(
Use a shallower DOF if you can. If you don't have an ND filter increase shutter speed. Better to have something in focus than everything out of focus :)
The small crop does kinda suck but at least we have manageable file sizes, I can render out all the footage I record to 1280x720 prores 4444 and they're still not even outrageously large as full hd files. Not to mention the footage has a film-like quality to it, esp. in a 2.40:1 crop and rendered out at 23.98 fps. Even the uprezzing imparts a bit of film softness onto the clips.
It ain't all bad ;D
Quote from: N/A on May 22, 2013, 07:44:31 PM
The small crop does kinda suck but at least we have manageable file sizes, I can render out all the footage I record to 1280x720 prores 4444 and they're still not even outrageously large as full hd files. Not to mention the footage has a film-like quality to it, esp. in a 2.40:1 crop and rendered out at 23.98 fps. Even the uprezzing imparts a bit of film softness onto the clips.
It ain't all bad ;D
Yeah, the only that calms me down is thinking about BMC having even a smaller crop :-D
Need to manage VM and environment installation, and try to play with sources... 1% are there some special instructions for raw module compilation? Or I just can use general guidelines?
If the Camera Is not able to handle RAW 2k and up. This may sound crazy, But what about a 1DX style encode. Motion JPEG? It'll still be much higher Quality than what we get now from the 600D.
The Cards are just not fast enough to Handle the High Resolution. I Can see 1280x720 Happening at the stable Frame rate but anything else is a stretch, Also Upscaling the Video is a complete waste of time. It just makes the Video look worse. Yes it's a RAW Image but you cannot start with something Small and make it better, You start with something Big and make it better.
Mjpeg is 8 bit. Nah, I'll stick with 14 bit.
If you want bigger, just buy a mkiii.
There's no way do compress the raw images inside the camera. We won't get anything else then what we have now. No Motion JPEG or anything else then .raw files.
Your options: Accept it, film in H.264 or buy a different camera ;)
And of course upscaling does help. It doesn't increase sharpness at all, but it makes it easier to see the details and compare it to default 1920 X 1080 H.264. If you don't believe it, then try it yourself.
Anyway. Let's be realistic: To record continuously at 24 frames per second we can't use resolutions higher then 0.5 Megapixels. Anything above that will stop after a few seconds. So now we can choose: Good colors and huge dynamic range (raw) or "high" sharpness and resolution (H.264)? You don't have to use raw video if you don't want to.
But please don't say it's useless just because it's not 2K ;D
If you are willing to sacrifise the dynamic range then just film H.264 like you did before Magic Lantern enabled this amazing feature. If you want both, get a 5D Mark III or a Blackmagic camera. Pretty easy, isn't it?
Once it sops raining in Germany (It's raining every f***ing day! >:() I guess I'll be happy with raw video because it really gives you a ton of dynamic range to work with!
As if by magic this appears: http://www.magiclantern.fm/forum/index.php?topic=5601.msg38946#msg38946 Things MIGHT get interesting
Any compression would be epic win.
He's had it working on on a 5d2 - Digic 4 so that gives us rebel users hope. This could push the 6d and 5d3 to new heights.
What a month!
@1% - the 600d TL2 doesn't link to a .o file does it? I know it's not currently needed
DigicV and IV speed differences for CPU aren't all that big.
Tl2 doesn't link it but should work if you've used 6D modules on 600D before.
@1% - I'll give it a go. I don't know where your 6d repo is though found it :)
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
It's giving me
tcc error: undefined symbol 'raw_lv_request'
tcc error: undefined symbol 'raw_lv_release'
I put the 6d raw_rec.mo and rawc.o in the modules folder
incompatible with 600d?
Will have to try to make 600D version maybe.
Done.
d mentions in his post that he's working from the May 14th version. Maybe things have changed since then that could affect this working?
Tried the TL2 pull but saw your other post in the 12bit thread. Obviously no change in frames but it still works if that's any help :)
Great! Things started to get moving!
d said on 4AM that he got some errors fixed in pixel shifts.
Can't wait to try 10bit raw with a higher res.
Quote from: N/A on May 22, 2013, 10:54:57 PM
Mjpeg is 8 bit. Nah, I'll stick with 14 bit.
If you want bigger, just buy a mkiii.
Well there you go, Your expecting the same performance of a $3,000 Camera on a $400 Camera. Yeah 14 bit is more color, but the Camera is just not fast enough to handle that Quality at the reslution you want. Therefore you lower the Quality of the Dng than you can properly up the reslution. It's that simple.
I'm not expecting anything close to mkiii perfornance from the 600D, but if we're going back to 8 bit, just use stock video with bitrate maxed and gop3 frames. Besides, mjpeg was a no-go according to the devs.
Although this new 12/10 bit topic might do the trick.
Quote from: N/A on May 23, 2013, 05:28:35 PM
I'm not expecting anything close to mkiii perfornance from the 600D, but if we're going back to 8 bit, just use stock video with bitrate maxed and gop3 frames. Besides, mjpeg was a no-go according to the devs.
Although this new 12/10 bit topic might do the trick.
Fair enough, I agree with what 1% said in another thread. we should have the option to set the Bit. whether its, 14, 12, 10 or even 8.
Even 8 bit will skip the nasty canon resize.
Quote from: DJHaze596 on May 23, 2013, 05:43:31 PM
Fair enough, I agree with what 1% said in another thread. we should have the option to set the Bit. whether its, 14, 12, 10 or even 8.
Yeah, right. Some say about if 8bit - then going back to h264... But I would try 1280x720 @24fps 8bit raw - it's 21.1MB/s - as it was made for SD bandwidth :)
Quote from: 1% on May 23, 2013, 05:56:02 PM
Even 8 bit will skip the nasty canon resize.
What does that mean?
Your H264 is not 1920x1080... the camera resizes it. So either have 8 bit raw and you do the resizing, etc or have luma/chroma thrown away by canon with repeated resizing from raw to yuv to H264, no thanks.
Don't forget about the H.264 compression ;)
Adding these lovely motion artifacts and making editing almost impossible ... Canon really knows how to screw up an image ;D
I'm sure even 8-bit DNG raw files with a resolution of 1280 X 720 would look better than Canon's 1920 X 1080 H.264 videos.
But I don't really understand what's going on with that compression. It seems to do something, but it doesn't seem to increase the max resolution we can get ???
The compression needs to be "fixed" first... its not really compression just throwing extra chroma away.
Quote from: 1% on May 23, 2013, 07:31:51 PM
its not really compression just throwing extra chroma away.
But isn't that a very basic kind of lossy compression? I thought so ...
Anyway, I'm curious to see if this "throwing extra chroma away" will help us with the 21 Megabyte/s write speed dilemma.
It's really stunning to see what's going on here. A few weeks ago nobody even thought that raw video at any framerate could be possible on any DSLR. But you guys enabled it! You made the 5D Mark III a
real beast. And you revived the older cams like the 5D Mark II, 50D or 40D!
And maybe you're able to push the Rebel line to the next level too. I mean, I'm impressed with what we have now. But there may be a way to get even more ... ;D
Seems all that matters is write speed + memory size. So older CF cameras > new digic V cameras.
Quote from: CFP on May 23, 2013, 07:46:43 PM
But isn't that a very basic kind of lossy compression? I thought so ...
Sure it's lossy, but... I own a good old 300D with 12bit raw, and... you know... sometimes I even like its colour reproduction more than the newer 600D! (which is 14bit raw)
P.S. Is there a ML for 300D? :-D
I didn't say that lower bit depths are worse, didn't I? :)
I really like the idea of using 10 or 8 bit instead of 14. Canon's H.264 videos are 8-bit and they do not look bad in terms of color. Only details and dynamic range are pretty bad compared to what's possible with raw videos.
Even the Blackmagic Pocket Cinema Camera has "only" 12-bit raw video. That's still more than enough ;D
But as far as I know compression is defined as an operation that manipulates data to decrease the file's size. And that's exactly what "throwing extra chroma away" is.
Shot using today's build, at 1280x400 global draw off, scaled up to fit in a 1920x1080 frame.
Made it 860 frames before it hit the wall, using a San Disk Extreme Pro 95MB/s
Benchmarks have been consistent 21mb/s
I dont know any other information that may be helpful, but ask if you have any questions.
Lovely detail. Magenta/Green slider needs to be moved to 0.
Quote from: jhall07 on May 23, 2013, 09:16:28 PMI dont know any other information that may be helpful, but ask if you have any questions.
1) What programms did you use? Especially for upscaling?
2) Why did your recording stop? :o I'm able to record continuously with 1280 X 400 (With "Edmac Popin" build) on a 45 Megabyte/s SD-card.
I used Photoshop camera RAW to create the TIFF's, then I actually just threw the TIFFs into FCPX as a compound clip, then placed them on a 1920x1080 timeline and exported as a Pro Res 422 Proxy, then uploaded to vimeo. Not sure why it stopped. It was the lastest build. I had frame skipping off.
I played with a bunch of different resolutions earlier today, but havent really tested any of them to the limit.
For me the latest build seems to drop ~7 frames every 60 frames or so at 1280x400. I use the same San Disk Extreme Pro 95MB/s.
Quote from: jhall07 on May 23, 2013, 09:51:54 PM
I used Photoshop camera RAW to create the TIFF's, then I actually just threw the TIFFs into FCPX as a compound clip, then placed them on a 1920x1080 timeline and exported as a Pro Res 422 Proxy, then uploaded to vimeo. Not sure why it stopped. It was the lastest build. I had frame skipping off.
I played with a bunch of different resolutions earlier today, but havent really tested any of them to the limit.
Hi Everyone, first post Here.
Did anyone try changing the size of the tiff's while exporting from lightroom? just in case we get better results than the NLE upscaling.
THANK YOU very much to the devs for this achievement
Lots of shots today with the newest build, no dead pixels/bad frames. Reformatted the card to ex-fat so maybe that helped. Now, if only I could get those damn dolphins to sit still for a few seconds while I focus.
Quote from: N/A on May 24, 2013, 01:33:51 AM
Lots of shots today with the newest build, no dead pixels/bad frames. Reformatted the card to ex-fat so maybe that helped. Now, if only I could get those damn dolphins to sit still for a few seconds while I focus.
What settings did you use (in detail please) This topic has me completely geeked, and I'm waiting to see if 1280X534 is doable.
Thanks
Quote from: N/A on May 24, 2013, 01:33:51 AM
Lots of shots today with the newest build, no dead pixels/bad frames. Reformatted the card to ex-fat so maybe that helped. Now, if only I could get those damn dolphins to sit still for a few seconds while I focus.
Can you point me to the latest hack download page, or build page I'm new to magic lanterns hack thank you.
First page of this thread has link. Settings were 1152x480 which isn't continuous in the new build but enough to get good shots.
Quote from: N/A on May 24, 2013, 03:28:27 AM
First page of this thread has link. Settings were 1152x480 which isn't continuous in the new build but enough to get good shots.
Went to the first page and downloaded when I opened the 600D folder I only see two other folders "Modules" & "Scripts" is that right? The 5D Mark II folder has additional forders like "Cropmrks" "Data" "Settings" Am I missing something? or should I just use the 5D Mark II extra folders for the 600D? any reply would be greatly appreciated thank you.
I know this is only my second post, so forgive me if anything has been covered elsewhere. I have been watching ML develop over the last few years, and have benefited greatly by all the hard work the Dev's and testers have put into this. I won't even pretend to understand how this was done, as I'm no genius coder like the Dev's.
Basically, what I want to know is how to get this working on my T3i, and what is the maximum resolution for continuous 24fps shooting that yields either a 16:9 and/or 4:3 aspect ratio. Most of my broadcast stuff is still on SD cable. I would love 1280x544ish for 2.35, but anything that would uprez to that well would also be good.
I know this has all likely been covered elsewhere in the thread, but an all inclusive step by step, or at least the basics in one place would help a lot. If I can get this going on my camera, I can post my findings as well, and possibly help in a small way.
Thank you very much in advance, and thank you for all your hard work.
Download the latest nightly build here-
http://www.magiclantern.fm/forum/index.php?topic=3072.0 (http://www.magiclantern.fm/forum/index.php?topic=3072.0)
Make sure you have that up and running efficiently. Then download the newest tragic lantern 2.0 build (in the first post of this thread) and copy and paste whats in that download over whats on the card. Make sure raw_rec is in the modules folder, and the modules folder is in the ML folder.
Profit.
Checked all my footage from yesterday with the latest build, no more bad pixels, and bad frames only showed up on a video done with 5x crop. I'll have to shoot a couple clips with 10x and check those too.
Yup, 10x looks good but 5x corrupts frames. Weird.
I'm not sure if this is supposed to happen, but the ISO is being baked into the raw files and I can't recover any detail at all, even when correctly exposed. I know that I should be able to recover highlights because ISO is supposed to be metadata, but when I look on camera at ISO 80, there is detail in the highlights, but when I look at ISO 320 or 640, there will be detail in the shadows but none in the highlights. But after I run raw2dng and bring the files into ACR, it's a no go. Can anyone chime in on this?
ISO is a physical thing... you can't use iso 100 and then try to "recover" data that would be in ISO 1250, etc.
Anyone else notice total memory go down? I get 90 something on 600D and 144 on 6D now.
Quote from: 1% on May 24, 2013, 10:40:37 PMAnyone else notice total memory go down?
Yes. With the "LatestPull - has rawclinked" build I shoot_malloc is only 96 ...
Btw. when I change the exposure while recording raw, the file breaks :(
96 here as well, was 104
Thats weird with the expo... I've never tried changing while recording.. I record with LV disabled. The speed difference is just too huge.
Quote from: 1% on May 24, 2013, 10:40:37 PM
ISO is a physical thing... you can't use iso 100 and then try to "recover" data that would be in ISO 1250, etc.
Okay, thanks. So because the ISO changes the sensor's actual sensitivity, it gets recorded into the raw file? And yeah the memory did go down.
Doesn't matter if its in the meta data or not.. its sensitivity X and thats it.
For expo changes... HDR video is still working
Or a lens with de-clicked aperture ;)
Well, with "exposure" I meant "shutter speed". I get a normal .raw file which can be converted to DNG frames using raw2dng. And the first couple of frames is OK. But after I changed the shutter speed suddenly every frame is 0 KB and doesn't open with anything ...
I just wanted you to know ;D
But you didn't shrink the buffer on purpose, didn't you? So, is there a way to get it back? :)
And ... how do you focus without LV? ???
Focus before recording. I guess it would be a problem for fancy focus moves.
Interesting that shutter speed would screw it up. In photo? In movie?
I figured a1ex fixed memory calculation with the 4kb alignment thing? I just noticed it go down and was like WTF.
Quote from: 1% on May 24, 2013, 11:50:40 PM
In movie?
Yes. It was in 1080 Movie Mode.
Does this also happen on the other cameras? Or is it just (my) 600D?
about RAW in 600D:
the "width x height" values are fixed to choose from a table of values or can we type any value we want?
would it be possible to try 960 x 520?
14 bits / 8 bits = 1,75
960 x 520 = 499200 x 24fps = 11980800 x 1,75 = 20966400 (under the 21MB/s limit)
I can shoot continously in 960 X 540 at 24 frames per second. An even lower resolution should be no problem.
If that is so I wonder if we can sample alternate rows and columns to preserve FOV?
(OK because of mosaic alternate double rows and columns)
This would be better than a quarter crop; yes?
Quote from: CFP on May 25, 2013, 12:14:45 AM
I can shoot continously in 960 X 540 at 24 frames per second. An even lower resolution should be no problem.
but the 960x540 is reported to have magenta frames, this is why i suggested 960x520, to try to avoid drop frames and magenta frames.
maybe 940 x 530 can work also
I am just trying to suggest some "nearest quarter full hd" options close to 1,777 aspect ratio and under 21MB/s to make the upscaling to 1280x720 or 1920x1080 the best possible.
Would have been easy but now height is from aspect ratio... so what aspect would that be I guess?
Also just tried switching expo with the shutter and no problems.
Hi 1%
the idea is to get the biggest resolution "width x height" in 16:9 aspect ratio (1.77777x)
best option would be 960 x 540, but people are reporting magenta frames, so...
something like 942 x 530 could work good
942 x 530 = 499200 x 24 = 11982240 x 1,75 = 20968920 (under 21MB/s)
or 940 x 528
940 x 528 = 496320 x 24 = 11911680 x 1,75 = 20845440 (under 21MB/s)
So you want to add 942 width and 940 width?
Those don't work.. 920 does.
Don't know if its in the new build but is it possible to have the raw module stay on the same rez, even after the camera is shut off? Like how ML saves the settings.
920 x 518 in 16:9 will be better than 854x480 after croping the 960x480.
yes, enable the 920 width would be good!
920 and 944 added.. they are faster sometimes.
I don't think config files can be used with modules yet.
Hi 1% thanks for the 920 and 944 width!
Sorry for this question, (newbie question) but... how can I install the RAW video feature in the 600D?
I have the ML 2.3 instaled and working ok, so I am wondering the easy way to add the RAW feature (600D)...
Replace bin and add module... lol
ok, thanks! I am already reading the topic about RAW instalation for beginers, I found it!
about the 920 and 944 width, will you upload this new feature into a new zip file with modules in the tragic lantern?
I did the install, was easy.
Maximum resolution I could record was 960x408 at 2.35:1 aspect ratio, around 15.6~16.3MB/s
Anything more than this recording stops
Sound recording off, I did try RAW and SRAW, also did try Hacked mode on off.
I am using Sandisk Extreme 45MB/s (in card reader in computer it works at 28MB/s writing)
The buffer and card writing benchmarks on camera are more than 20MB/s so I do not know what is making the movie recording stops
RAW video playback on camera is always black and white
At 960 x 540, when I enable Skip Frames, many frames skips and recording continues at 18.2~18.7MB/s
At 1280 x 720, also with Skip Frames, recording goes on at 20.2~20.4MB/s and many frames skips
Maximum 16:9 resolution I can record without skip frames is 720x406, lower than DVD quality...
So I think enable 854 width would be good idea, because it will be usefull for 854x480 recording in 16:9, great for DVD work.
any ideas in how to make it works better, using 920x518, 944x532 or 960x540?
thanks
854 x 480 (16:9) will be a great option for sure. perfect for 16:9 DVD quality work.
it is the almost the same data rate of 640 x 640 and in my tests 640 x 640 works ok with frame skip off in continous recording.
854 x 480 = 409920
640 x 640 = 409600
maybe 856 x 480 will work better due to be multiple of 8?
with 640 x 360 and 720 x 406 I can record without skip frames and with simultaneous wav audio.
but...
in all resolutions I always get magenta frames. No matter 640x360, 720x406, 640x640, 960x408... all give me magenta frames.
Maybe some 600D are better than others, or the raw modules and bin need to mature???
Is there a solution?
first post here, thank you 1% for making this possible. now the 600d is a SD raw camera, too bad that the sd speed limitations allow me no more than 16 mb/s, btw since the latest updates I have noticed no more magenta frames and with the latest build the raw file looks more accurate to me (the magenta values are better than before) in photoshop. Hepefully you will be able to kill this speed limit, but it's probably a hardware thing...?
I've noticed that the RPP converter for mac does a bit better RAW processing than ACR & Lightroom - there is no moire or aliasing on small details. It's demosaic algorithm seems better.
Need to test it a bit further though.
We'll get 12/10 bit when we figure out the registers to have canon do the chopping.
No real fix for the SD card speed.
If you're getting pink frames at such low res you need a faster card. I haven't seen any pink frames in a while.
Quote from: 1% on May 25, 2013, 04:35:13 PM
If you're getting pink frames at such low res you need a faster card. I haven't seen any pink frames in a while.
Same here. Purple frames are no problem anymore.
And the shutter speed thing might have been a coincidence ... But I think we have to accept that the 600D is just not the right camera for raw video. Even with "throwing extra chroma away" (lossy) and maybe even with Huffman compression (lossless) I doupt that we would get anything above 1280 X 720 :(
... Still I don't feel like getting a 50D instead of a 600D is a good idea. I would like to have both. Or just a 70D, if it will get a CF-card slot.
May not be the best camera for raw video but if its all people have then it might as well do it. 960x540 works for me and shrinking it just slightly to like 944 makes it even more stable. Upres to 720P or 1080P or letterbox its still nicer than the best H264. Wide lens helps with the crop factor.
720P full would be nice... I dunno, 6D doesn't do that either with 10 extra MB/s on my end. The sandisk 45MB/s people I think can do close to that continuously.
I think a better advance than just compression will be more memory... our buffer is only 96MB now. If it was 200MB you'd get usable takes on much larger sizes. Don't see many cutaways that last more than a minute.... You're probably not going to get raw hour long interviews but for other stuff its fine... and for this cheap too.
Lol... someone want to send me a 50D :) I bet price will be jacked on it real soon.
720x640 will give nice 720x1280 with a 2x scope :)
Quote from: 1% on May 25, 2013, 04:55:36 PM
May not be the best camera for raw video but if its all people have then it might as well do it.
No doubt! Just the fact that Canon DSLR actually
can shoot raw video is more than incredible! I remember the first day when Luke Neumann came up with the 14-bit silent pictures for the 5D Mark III and everybody in the comments was like "You're stupid. There's absolutely no way a 2850 € camera can handle raw videos. Stop dreaming and get a RED EPIC". And you showed them who are the stupid onces ;D
Even at 1280 X 400 the videos are very nice. The dynamic range ... I love it. I love ML. And I have faith that you can make at least the 50D to one of the best video cameras on the market! :D
Quote from: 1% on May 25, 2013, 04:55:36 PMsomeone want to send me a 50D :)
You deserve one ;)
But I don't think that the 50D will get more expensive. It may be able to record video with Magic Lantern. But still most people use it for photography.
I will try another card...
Please, consider enable the 854 (or 856) width, very useful for DVD quality 16:9 (854 x 480)
and also, it is less data rate than 920/944/960
Ok, I'll try it, may not work tho, some res comes out pink or causes corruption. Have to add a pixie dust fix too as from the other thread.
QuoteBut I don't think that the 50D will get more expensive
2 of them on craigslist $600USD. On ebay cheapest was around there too.
50d price is going up. Either that or I got a real bargain. I never took much notice of the secondhand price before actually deciding to get one. 2 are advertised locally for between 600-800 euros which is only slightly less than 5dMk2's are going for.
If you can get one cheap, get it. It's a great camera regardless of it's raw video abilities.
Tip: try to find one locally through classified ads. A lot of older photographers do things the old-fashioned way and advertise in newspapers etc
Well. If the price is rising then I'll have to get one soon ... Hm ...
The German prices still look okay (~ 400 Euro) ...
Thats like $500 usd and some change... so your price is like ~100 bucks cheaper. If I didn't have to get my tokina fixed still I'd probably grab one.
Quote from: 1% on May 25, 2013, 06:14:46 PM
Thats like $500 usd and some change... so your price is like ~100 bucks cheaper. If I didn't have to get my tokina fixed still I'd probably grab one.
You can get a lens fixed anytime ;)
http://youtu.be/0XE2lVwALVQ
actual RAW Module, actual Nightly Build of ML
got dropped frames at 1280x426 25p according to buffer, says the camera... 30mb/sec ultra sd
Please consider my request for 720 x 640 (8:9)
With a 2x scope and 24mm lens should look good 720 x 1280 :)
also its the best vertical resolution !
Btw, somewhere I read that sRAW can be glitchy if I take photos while in this mode or smth.
Just took one picture - got a good sRAW, 2592x1728, 8Mb in size. Took a bayer view of using RawDigger - there is no bayer pattern, just normal pixels. ACR doesn't open it though.
Dunno maybe this info can be useful somehow...
Quote from: JohnBarlow on May 25, 2013, 07:16:21 PM
Please consider my request for 720 x 640 (8:9)
With a 2x scope and 24mm lens should look good 720 x 1280 :)
also its the best vertical resolution !
Why on earth would you want Vertical? We have Pro Cameras, not Cheap Cell Phone Cameras.
The sraw will work but the photos don't look good. I opened them in ufraw
Please service my request for 720 x 640 or provide custom selectable aspect ratio
Thanks
Quote from: DJHaze596 on May 25, 2013, 07:47:21 PM
Why on earth would you want Vertical? We have Pro Cameras, not Cheap Cell Phone Cameras.
Anamorphic lenses for a scope look
I installed everything again carefully and now things are working ok for 640 x 640 in my Sandisk Extreme 45MB/s (I have three of these so I would like to avoid buy another card) It works for 960 x 402 also, but does not work for 920 x 518 (skip frames), so...
Fingers crossed for the 854 x 480 because it is the same datarate of 640 x 640, my only hopes for 16:9 now !!!
Skips after how long? 960x540 works for me the second time... over 1000 frames. The 920 is continuous with some room left over.
You should just turn frame skip off... why bother to have garbage frames in the video.
I need clean pro video, cannot live with the magenta frames or skip frames!
In 920 x 518 when I allow recording with skip frames, it is something about at each 70 recorded frames it skips 5 or 6 frames, than records more 70 frames and skips 5 or 6 again...
Buy a card that can handle it.. no magenta frames here.
Quote from: apefos on May 25, 2013, 09:52:08 PM
In 920 x 518 when I allow recording with skip frames, it is something about at each 70 recorded frames it skips 5 or 6 frames, than records more 70 frames and skips 5 or 6 again...
I also have Sandisk Extreme 45mb/s
Please check if you have everything this enabled:
Video mode: canon 640x480, region PAL
FPS Override on: 24fps
Shooting: sRAW
Global Draw: Off
Hack3D: Enabled (although I have success even without it)
Without zoom or crop (also check for any strange settings in ML, or maybe run a clean install)
Also maybe try to Format card low level in camera or with EOSCard utility.
Hope I didn't forget something...
Love the new aspect ratio menu, 1300+ frames (continuous?) with 1120x468 (2.39:1) ;D
540 frames with 1136x476. Not too shabby.
Did a cam preview and all the frames looked fine.
Hi guys, thanks for the help
I did try everything, but it seems the problem is the card speed or the buffer speed in my T3i camera.
I will stop posting until I can try the 854 width (I hope it can be enabled)
I also suggest the 784 width because it can be a great option also ( I hope it can be enabled also)
After I can try these width I will consider buy a Sandisk 95MB/s, but for now I will wait...
thanks
I'll add some smaller widths for the next run.
Okay, installed and working...sort of. Where do I find the enable/disable frame skipping, and how do I convert this .RAW to something usable in Windows. I downloaded the raw2dng and dragged a raw file to it, but my cmd window just flashes, and goes away.... any help would be greatly appreciated. also what is meant by 640/720/and 1080 recording modes? Is this the canon menu settings? If so, what difference does this make.
So much of this seems disjointed to me. Sorry for my ignorance
Rob
http://www.magiclantern.fm/forum/index.php?topic=5557.0
http://en.wikipedia.org/wiki/High-definition_video
Maybe avoid playing with raw for the moment? If you don't understand the absolute basics you'll have a harder time understanding this level. (no offense intended).
I've been using ML for over a year, but some of the settings are a little harder to find than before. No offense taken. The thing that is confusing me is I read that "so and so" used 640x480 mode, 1280x720 mode, and so on while trying high resolution raw cappture. I'm familiar with all video standards in general, but some of the posts are a tad confusing. I've been shooting professionally since 1984.
Quote from: N/A on May 25, 2013, 10:37:42 PM
Love the new aspect ratio menu, 1300+ frames (continuous?) with 1120x468 (2.39:1) ;D
540 frames with 1136x476. Not too shabby.
Did a cam preview and all the frames looked fine.
which card are you using ?
got skipped frames and iam thinking of buying me a new card. right know i got a class 10 hd video ( 30mbs ) card.
should i buy the sandisk extreme 45 mbs or the sandisk extreme pro 95 mbs ? would like to have 1120x468 resolution.
my card is formated to exfat and iam using the newest builds.
thx for that great software !
btw i had problems with kernel when i was using the movie remap and raw video. when the camera was in idle mode it had problems ...
Sandisk 95, it is pricey but the compatibility/reliability benefits are worth it.
Quote from: robrock_68 on May 26, 2013, 12:58:10 AM
I've been using ML for over a year, but some of the settings are a little harder to find than before. No offense taken. The thing that is confusing me is I read that "so and so" used 640x480 mode, 1280x720 mode, and so on while trying high resolution raw cappture. I'm familiar with all video standards in general, but some of the posts are a tad confusing. I've been shooting professionally since 1984.
I misunderstood your question earlier. My apologies :)
When others are referring to the modes they mean they are shooting raw but video mode (normal Canon video mode) is set to 720p or 1080p etc. In 720p it will line skip and the image will look squashed in a similar way to anamorphic but squashed vertically as opposed to horizontally. You can correct this by multiplying the height by x1.66 but leave the width the same. This is more prone to aliasing but means you save a little on filesize (i.e. get more frames/time or be able to shoot a wider frame). 1080p and 480p will appear in a normal aspect ratio. The video size does not correspond to the raw video size. You set that independently in the raw_rec module.
Quote from: Andy600 on May 26, 2013, 02:22:30 AM
I misunderstood your question earlier. My apologies :)
When others are referring to the modes they mean they are shooting raw but video mode (normal Canon video mode) is set to 720p or 1080p etc. In 720p it will line skip and the image will look squashed in a similar way to anamorphic but squashed vertically as opposed to horizontally. You can correct this by multiplying the height by x1.66 but leave the width the same. This is more prone to aliasing but means you save a little on filesize (i.e. get more frames/time or be able to shoot a wider frame). 1080p and 480p will appear in a normal aspect ratio. The video size does not correspond to the raw video size. You set that independently in the raw_rec module.
Gotcha, thanks a bunch. Not sure I like the crop of the raw, but will be trying other lenses to see what I can get. I get good record times on the low res side, but need to try a reformat to see if I can eek out a little more speed on the card. Oddly, the camera shuts down as if I'm not shooting at all. Guess I need to modify my power saving settings or something.
Okay, RAWanizer doesn't work for me, I've posted on the other thread with the error I get. Is there another option for windows that doesn't have these issues? I would hate to build a linux box just for converting video files.
Maybe I'm missing something, but I'm pretty savvy with computers.
Raw plays back choppy and in black and white on the camera.
Just to say I did some tests in the full hd pc monitor and I found the raw image quality is pretty good in resolution, colors and grade, and the upscaling works good until 250% (2,5x the original size). I did a 250% scale in the image looking to face, landscape, building and I liked the results. more than this enlargement the image does not look good to the eye. also i want to say the 200% (2x) enlargement is just great!
so to fill the 1920 pixels monitor, the smallest width to record would be 768 because 1920 / 768 = 2,5
this way, 768, 784, 816, 854, 888, 920, 944, 960 will be usefull for sure, to each user find the maximum resolution possible without skip frames for his camera/card combo.
Oh yeah, totally useable.
http://www.magiclantern.fm/forum/index.php?topic=5709.0 (http://www.magiclantern.fm/forum/index.php?topic=5709.0)
First of all: THANK YOU VERY MUCH!
Here you can see my first test with this settings:
Video mode: Canon 640x480@30fps.
Lens: Canon EF-50mm f1,8 II.
SD Card: Sandisk Extreme 30 MB/s.
Magic Lantern:
- Shooting: sRAW
- FPS Override on: 24fps
- Resolution: 960x402
The video stops because of buffer problems after a few seconds, I think it's because of the low speed of the SD card. I'll try it with faster cards.
RAW converted using raw2dng_batchelor.exe, frames edited with Camera Raw and merged with After Effects.
Finally!!!!! Getting great quality, no magenta. Getting happy ;D
Quote from: apefos on May 25, 2013, 09:19:28 PM
I installed everything again carefully and now things are working ok for 640 x 640 in my Sandisk Extreme 45MB/s (I have three of these so I would like to avoid buy another card) It works for 960 x 402 also, but does not work for 920 x 518 (skip frames), so...
Fingers crossed for the 854 x 480 because it is the same datarate of 640 x 640, my only hopes for 16:9 now !!!
where do I find these resolutions. I only have the originals mentioned previously, and cant seem to fine the files to enable these other resolutions
Robrock, go to the first post of this thread, to the link where you get TL 2.0. Download the top two on the page, paste the contents of "aspect lock" onto your card, then replace the existing raw_rec module with the new one (edmac kill, have to rename it to just raw_rec.mo).
Hope this isn't too much of a noobish question - a link would be appreciated if it's in the existing posts and I've just missed it in my searching:
Is anyone working on 'column skipping' - i.e. writing only alternate pixel values on the horizontal lines to reduce bandwidth requirement while keeping non-cropped image circle?
Aliasing issues I can see would exist, but it would be a useful option for several scenarios I can think of.
Just wondering, thank you!
Quote from: N/A on May 27, 2013, 01:38:49 AM
Robrock, go to the first post of this thread, to the link where you get TL 2.0. Download the top two on the page, paste the contents of "aspect lock" onto your card, then replace the existing raw_rec module with the new one (edmac kill, have to rename it to just raw_rec.mo).
Got it, thanks a bunch
No prob
Quote from: Anstech on May 27, 2013, 01:57:49 AM
Is anyone working on 'column skipping' - i.e. writing only alternate pixel values on the horizontal lines to reduce bandwidth requirement while keeping non-cropped image circle?
I guess not yet, but that should be a good idea too. If the bit-conversion doesn't succeed, then reducing 1740 to something around 870 will be good. The question is again - how fast it will be...
Thought I'd jump on the bandwagon so bought a 95 mb/s $andisc card.
When in photo mode global draw on, I get read/write around the 20/21mbs mark. Formatted to exfat, downloaded the latest files.
However if I put it in video mode, it drops to 17-19mb/s.
Is that expected?
Only manage about 63 frames before it goes kaput, at the resolution N/A was filming at.
Now, I must say I am not a coder or expert on cameras in any way, but would compressed mathematically lossless raw, like on the BMPCC, not be a better alternative for getting as great quality as possible on to SD cards? Or perhaps the camera processors are too slow to compress the footage? Just 2:1 compression should help alot, and if 3:1 or 4:1 would be possible, the results might actually be very good.
Quote from: N/A on May 27, 2013, 01:38:49 AM
Robrock, go to the first post of this thread, to the link where you get TL 2.0. Download the top two on the page, paste the contents of "aspect lock" onto your card, then replace the existing raw_rec module with the new one (edmac kill, have to rename it to just raw_rec.mo).
If I use the raw_rec.mo edmac kill + res than I can only get about 67 frames no matter the resolution. If I use the raw_rec from the "aspect lock" then everything is fine.
Is this normal?
Quote from: cbmk on May 27, 2013, 07:57:15 AM
Now, I must say I am not a coder or expert on cameras in any way, but would compressed mathematically lossless raw, like on the BMPCC, not be a better alternative for getting as great quality as possible on to SD cards? Or perhaps the camera processors are too slow to compress the footage? Just 2:1 compression should help alot, and if 3:1 or 4:1 would be possible, the results might actually be very good.
Yes, now it looks like too slow even for bit degradation (but I still believe that there was some error, and it should be possible). Compression requires much more CPU power. And loss-less compression - even more, and the ratios wouldn't be 3:1, 4:1. If you can get 20-40% loss-less compression in RAW - that will be a breakthrough.
I'm still getting magenta frames (28 in 1117 on my last test) I'm using the 24 May nightly build and the "600D aspect lock" file.
Shooting in 1080p 24fps 960x408, sound disabled SRAW. Global draw off.
SanDisk Extreme 45 Mb/s 16Gb.
How can I get rid of the magenta frames? Any advice?
Been doing a little more testing.
If I have the hacked mode turned on, no skipped frames at 920x460
Hacked mode turned off, 5300 frames total and 43 skipped frames.
It doesnt skip a whole lot at once, it will skip about 1 in 120 or whatever.
So enough to be annoying haha.
writing at 16.7mb/s is about the best it can manage so far without issues.
If N/A or someone could elaborate as to exactly what they've done to acheive the higher resolutions, would be great
(How the card is formatted, etc... does this make a difference if exfat or not apart from file size limit?)
Did another field-test of 600D with the newest [600D] Aspect Lock.zip build + newest raw_rec.mo
The first bug is there - dunno why, but I think resolutions in line-skipping modes don't have the correct aspect ratios.
I set the aspect ratio of 2.39 (and ML recommends to stretch it by 140%) - but stretching it by 140% gives people a fat look :-D
Stretching it with a good old 166% does the right thing, but then I get 2.01 ratio, instead of 2.39 (which could save us a few more bits).
So please investigate this and check if there is no error in this place
Also on 1734px mode I still (as always) get noise. Do we need this mode anyway? Maybe there is some resolution nearby without the noise, but larger that 1600?
So, here is the video:
Everything is shot with Canon EF-S 18-55mm IS II.
Full-screen fragments are shot using normal (Canon 640x480) modes, without line-skipping, and stretched to full-screen 1920x802 px.
Cropped (with black borders) fragments are shot with line-skipping mode (Canon 720p), and stretched to 166% vertically. Horizontally the fragments are actual 100% size as shot.
RAW conversion was done in RPP (Raw Photo Processor), which eliminates moire, pixel flickering and aliasing (at least not as much as ACR gives), and gives more "film-look" tones and color.
RPP exported to 16bit tiff, and no more processing was done after raw conversion (except 166% vertical stretching).
All fragments are full-length, and are ending at the first frame-skip and buffer overflow (some of the really long fragments are ended manually, cause they can record forever). Thus this is the maximum I can get at every resolution.
List of resolutions and lengths:
1) 1152x482, 254 frames, (10 sec, continuous, should be)
2) 1600x670, 44 frames (1.5 sec)
3) 1600x670, 44 frames (1.5 sec)
4) 1600x476, line-skipped, 86 frames (3.5 sec)
5) 1536x458, line-skipped, 93 frames (3.5 sec)
6) 1536x458, line-skipped, 93 frames (3.5 sec)
7) 1504x448, line-skipped, 143 frames (6 sec)
8) 1440x430, line-skipped, 157 frames (6.5 sec)
9) 1440x430, line-skipeed, 157 frames (6.5 sec)
10) 1440x430, line-skipeed, 157 frames (6.5 sec)
11) 1440x430, line-skipped, 157 frames (6.5 sec)
12) 1440x430, line-skipeed, 157 frames (6.5 sec)
13) 1440x430, line-skipeed, 157 frames (6.5 sec)
14) 1440x430, line-skipeed, 157 frames (6.5 sec)
15) 1440x602, 55 frames (2 sec)
16) 1440x602, 55 frames (2 sec)
17) 1280x536, 141 frames (5.5 sec)
18) 1152x482, 347 frames, (14 sec, continuous, should be)
19) 1136x476, 260 frames, (10 sec, continuous)
These are RAW resolutions. Real converted picture resolutions are somewhat 6 pixels less in each dimension (dunno, maybe it's the way RPP does convertion).
Still need further investigation.
Quote from: Roman on May 27, 2013, 07:16:42 AM
Thought I'd jump on the bandwagon so bought a 95 mb/s $andisc card.
When in photo mode global draw on, I get read/write around the 20/21mbs mark. Formatted to exfat, downloaded the latest files.
However if I put it in video mode, it drops to 17-19mb/s.
Is that expected?
Only manage about 63 frames before it goes kaput, at the resolution N/A was filming at.
The fastest Build buffer-wise was edmac-popin I think. I haven't had a chance to shoot much with the latest one.
I also did a test in edmac popin and it is a litlle bit better in terms of buffer, less magenta frames.
I also found that around 16MB/s is the maximum to work for safe with all versions. I did lots of tests. It seems all 600D cameras works this way because there are some other reports about this here.
Due to this I suggested the list of widths as you can see in my previous post. 1% said he will work on this widths. Maybe he can also compare the code from edmac popin with the new build to compile an improved version in terms of buffer.
I think this is the way, all members give feedback and suggestions to try to help improving the feature.
I got a magenta frame when I didn't kill edmac and tried to use zoom preview while recording... probably an edmac/cpu usage problem.
I write around 18-20.x most modes.
I have a request to fix the 4gb limit.
I have been doing exhaustive tests of 1136 x 694 in 720p camera mode, at 12FPS and 1/53 shutter override.
For me this gives the full height of the sensor and is just perfect for a 2x Scope.
At 12FPS with Twixtor it gives a easy tween to 24FPS for low motion content like interviews and such.
On a cheapo 200x SDHC card it runs effortlessly time after time up to the 4gb limit then stops, so if you nice people can fix the 4gb limit then it would be perfect.
Quote from: JohnBarlow on May 27, 2013, 03:58:06 PM
I have a request to fix the 4gb limit.
That's no firmware issue. If you want to save bigger files, just format your SD-card as exFat.
Thats great, Thanks a bunch
I didnt know Canon EOS worked with exFAT
Quote from: CFP on May 27, 2013, 04:03:50 PM
That's no firmware issue. If you want to save bigger files, just format your SD-card as exFat.
Limit was off... so if it stops feel lucky I guess.
You can see another video test here:
http://www.magiclantern.fm/forum/index.php?topic=5771.msg41320#msg41320
Quote from: 1% on May 27, 2013, 05:00:54 PM
Limit was off... so if it stops feel lucky I guess.
lol
Well unlucky would = corrupted FS on card.
Check for sprinkles on this build.. its using 5d3 like correction... someone on 5D2 got magenta cast but I didn't see it.
With defc off I had sprinkles all over. 6D seems unfixable. I'm seeing sprinkles in all types except default.
ML won't boot from an exFAT card :(
Run it through eoscard (windows) or macboot.
great improvements in the new build.
1440, 1360 and 1320 16:9 will be very useful for 50D owners, under the 50MB/s limit
loved the new playback features, now I can choose which file to play and can erase files also!
I did try the start delay 2, 4 and 10, but it does not avoid frames skip in 920 x 518.
the good news is: frames skips in 920 x 518, but there is no magenta frames
768x432 16:9 works ok, no magenta frames in 600D (768 x 512 works also, but 768 x 576 skips)
time to increase it a little bit... I think 816 x 460 16:9 will be a smart try! because it is under the 16MB/s (users are reporting 16MB/s limit is the safe option)
and of course 854 x 480 the perfect option for DVD, we need to try it!
640 x 640 is working ok, wich proves 854 x 480 will work (same datarate)
all my width suggestions: 784, 800, 816, 854, 888
a tip: put the playback above the delete ( the delete the last thing) to avoid pressing delete unwanted.
many thanks
The features in the new build are awesome, but for some reason at 1120x334 (2.39) I can only record 161 frames where as on the last build I was up to 273 pretty consistently, and at 960x342 (2:1) I could record continuously before but I'm stopped at 600 frames now.
I edited my previous post with more important feedbacks, please read again, thanks.
try erasing everything on your card, in canon menu: erase files, in ml menu erase the raw files. it helps after instaling a new build.
I did two more tests with 640 x 640. big 2GB files, it is working pretty good, no frames skip, no magenta frames.
this proves 854 x 480 will work good, they are the same datarate MB/s
excited to see 854 x 480 enabled, it will be the best thing for DVD
First post of the thread updated.
The new build is nice, the playback/delete will deff come in handy. 1280x533 over 100 frames, hell yeah. Did a couple quick renders, couldn't see and bad frames, pixels, etc. Auto wb in acr was pretty damn accurate too.
Think I found a bug though, if I have a few raw files and I delete one or two of them, the module stops displaying the rest of the raw files, even after a mode switch. Cutting the cam off and back on makes them reappear.
Great work though, wait till I tell the homies I can shoot sprinkle-free video 8)
QuoteI did try the start delay 2, 4 and 10, but it does not avoid frames skip in 920 x 518.
Thats just to see your buffers and let go of the camera,etc.
I tried 854 and it was all corrupt, sorry. Also 844... I can try a few more of the others.
Quotea tip: put the playback above the delete ( the delete the last thing) to avoid pressing delete unwanted.
Playback hopefully getting to be its own module soon along with file management.
Quotebut for some reason at 1120x334 (2.39) I can only record 161
Record twice. That seems to re-do the memory and you can go longer. Second run usually does the trick for me. Buffers are 31, 30, 20something :(
I think 16MB being safe would be on slower cards. I don't hit 21 but I do hit 20 and its fine with LV disabled.
I now have the exFAT working with the new build.
Tested 1136x694 @12FPS and reached 10gb files everytime no frame drops.
All I need now is better write speeds :)
EDIT: tested with Liveview Global Draw and Luma zebras and Luma Histogram. -- works great
Hi 1%
thanks for the answers
please try what you can do to get close to 854, maybe 848, 840, 836, 832... I do not know, but something which can get close to 480 vertical pixels in 16:9
Thanks, latest build is interesting, many new things...
But still aspect ratios on line-skipped modes are calculated wrong:
(http://www.naumik.com/temp/scr4/20130527-7r8-139kb.jpg)
Why the stretch factor is assumed 1.40x and not the usual 1.66x?
(here's the check pattern: http://www.mediacollege.com/video/test-patterns/images/aspect-ratio-circles-1024x768.jpg )
Thats zoomed or not zoomed 720?
Maybe stretch is different for non digicV or something else?
Quote from: 1% on May 27, 2013, 09:29:04 PM
Thats zoomed or not zoomed 720?
Maybe stretch is different for non digicV or something else?
That's a non-zoomed 1280@50fps. Will try zoomed now...
UPD: So, I did a test. Set the ratio to 1:1, then tried it in different 720p modes - and just looked at the cropmark rectangle (which must be a square @ 1:1 ratio).
1) In non-zoomed 720p mode - the 1:1 square is non-square - it's rectangular - more height, than wide.
2) In 5x zoom mode - the screen becomes BW, and very slow - but the square is now perfect square - ideal 1:1.
3) In 10x zoom mode - the screen is okay again - colored and fast, and the cropmark rectangle again is stretched vertically as in non-zoomed case (1).
Btw, on (2) mode I can visually see picture tearing frames sometimes, during live view.
Didn't do any recordings - guess the cropmarks test should be demonstrative enough.
ML assumes that 720p images should 16:9. Is this not true on 600D?
After formatting and recording a couple times I'm recording as much as previous builds were. Thanks.
Quote from: a1ex on May 27, 2013, 09:39:49 PM
ML assumes that 720p images should 16:9. Is this not true on 600D?
How can I check it?
Record something at full size (or take a silent pic), then stretch it so it looks normally. Is it 16:9 or something else?
Quote from: a1ex on May 27, 2013, 09:56:34 PM
Record something at full size (or take a silent pic), then stretch it so it looks normally. Is it 16:9 or something else?
Okay, took it.
The ML tells me it's 1734x694. FastRawViewer tells me the RAW is 1728x694, RawDigger EXIF info tells it's 1888x720.
Here's the silent pic:
https://dl.dropboxusercontent.com/u/9944031/14660049.DNG
Photoshop opened it as 1734x694.
After resizing it to 166.66666% vertically, it became: 1734x1157, and the aspect ratio circle is perfectly right:
(http://www.naumik.com/temp/scr4/20130527-ka1-149kb.jpg)
So we get 1.4987 aspect ratio, which is very close to 3:2 (1.5)
Zoomed 720p modes (5x and 10x) give me 2520x1080 silent pics with correct proportions and no line-skipping (10x has tearing & pink artifacts sometimes).
Video in these modes is capable also max 2520x1080, and has no line skipping.
Huh... who thought Canon would scan the full 3:2 frame when they struggle with line skipping to keep with the high fps...
Anyway, this has to be hardcoded somewhere; can't be solved in a portable way...
Quote from: a1ex on May 27, 2013, 10:41:00 PM
Huh... who thought Canon would scan the full 3:2 frame when they struggle with line skipping to keep with the high fps...
Yup. Well who knows, maybe scanning the full sensor, skipping half of the lines is faster, than cropping the 16:9 region from sensor...
Don't know why I didn't think of this before but the cropmarks that are already included in ML work well with scope ratio. A couple more for different aspects would be handy too.
Problems for me developers. Maybe someone can help me here:
• New modules can not run (no load);
• I can only 65-64 frames with 960x540 resolution. My card accuses constant speed of 20.8-21.3Mb/s (Sandisk Extreme Pro 95MB/s). I'm in 1920x1080; [until then I recorded continuously 960x540]
• With exFAT formatting the firmware is not recognized and can not upload.
Someone answers the reason for at least some of these problems? I attend most of the forum, but I am following all the conversations and following my tests in parallel.
[sorry my english]
(http://img196.imageshack.us/img196/5006/vram0.png)
Try a module together with a bin and modules go in ML folder not root.
Quote from: 1% on May 28, 2013, 03:13:07 AM
Try a module together with a bin and modules go in ML folder not root.
Yes, I do, but does not run correctly.
I was continually 960x540, but now nothing but 64 frames.
Settings (wrong?):
- Mode 1920x1080;
- "Module [600D] Lock.zip Aspect" to "kill raw_rec.mo edmac res +" (renamed and replaced). This module is the only one that works;
- Hacked activated mode;
- Resolution: 960x540;
- Override FPS: 23,976
- Pic Qyality: RAW
- Global Draw Off.
Also, a note: from what I've read, the ML does not run with exFAT. The lease was developed exFAT pala Microsoft in 2006 to replace the FAT32 had some problems. If it was created, leads me to believe that you have the same encoding. Why did not he run?
Pic Quality. Raw, I bet you have 1 or 2 buffer stars
QuoteAlso, a note: from what I've read, the ML does not run with exFAT.
It does.. you have to format <32gb cards out of "spec", so no SD formatter. All SDXC are xfat.
Never mind this as I did not know this was normal. - "Bug I have found with the latest "Still sprinkle free." When hacked mode is on my screen locks up and starts shaking back and forth. It continues to record and I can stop it but it happens every time hacked mode is enabled. Using a SanDisk 30 MB/s 16gb card."
Otherwise I seem to be able to achieve continues recording with (16:9) 944x532. At least to 1000 frames when I stop it manually. At 960x540 I make it just past 500 and then it stops. Thanks guys!
Quote from: zim9000 on May 28, 2013, 05:34:42 AM
Bug I have found with the latest "Still sprinkle free." When hacked mode is on my screen locks up and starts shaking back and forth. It continues to record and I can stop it but it happens every time hacked mode is enabled. Using a SanDisk 30 MB/s 16gb card.
That's what the hacking mode is all about - freezing live-view to gain speed, so it's normal.
Quote from: vicnaum on May 28, 2013, 06:34:51 AM
That's what the hacking mode is all about - freezing live-view to gain speed, so it's normal.
Ahhhh! Haha, alrighty. Never tried it until now....so yeah thanks for the heads up. :)
Hi guys
I have been running with the same issues as everybody. Pink frames, pink frames... and... Pink frames! AH for God sake! pink frames everywhere! Still, it sounds negative, but I'm happy just to try. I managed to get the clean frames and make a short video. Link: http://www.youtube.com/watch?v=Q2qrlV4S27s
I know that a lot of you have cards faster that 20MB/s , but even if that's the limit, the camera is having problems recording at 15MB/s.
I have the champagne ready for when 12 and 10bits allow us to fix this issues. Until then My name is crash dummy #63
The magic lantern team is known to be tireless in making canon cameras rocks. I am sure you all are doing your best for raw.
So here is a list of widths wich are close to the maximum resolution 600D can handle without skip frames or magenta frames in 16:9
856, 854, 852, 850, 848, 846, 844, 842, 840, 838, 836, 834, 832, 830, 828, 826, 824, 822, 820, 816
a tip would be to start from the highest values and go decreasing until find which one works good.
many thanks
Quote from: apefos on May 28, 2013, 12:39:31 PM
The magic lantern team is known to be tireless in making canon cameras rocks. I am sure you all are doing your best for raw.
So here is a list of widths wich are close to the maximum resolution 600D can handle without skip frames or magenta frames in 16:9
856, 854, 852, 850, 848, 846, 844, 842, 840, 838, 836, 834, 832, 830, 828, 826, 824, 822, 820, 816
a tip would be to start from the highest values and go decreasing until find which one works good.
many thanks
I guess only implementing the custom resolution (at least for testing period) can make everyone happy :)
Hi everyone! First of all thanks ML team (and special thanks to1% for porting to 600D) for RAW video. I've been using ML in the past for a long time. But now i'm really excited for RAW possibilities so i decided to register!
Ok, i've tested it on my 600D with Sandisk Extreme 95.
I've got about 6 seconds in 1280x544 res which is nice for my needs :) Awesome!
But during the testing period i've came across some questions
1) Does the different resolution also affect global quality of the image? Or its just the size of crop from the sensor with the same quality for every resolution mode?
2) Is it important to use neutral picture styles now?
3) Is there any difference to use 640x480 vs 1920x1080 canon resolution modes?
I'll very appreciate any answers
P.S. I'm going to upload some test footage soon :)
If you kill LV you shouldn't' get any pink frames... if you don't then I dunno. I've been recording in 24P and in 640x480.
Picture styles don't apply... only black level/wb/iso gain.
@ Luiz Roberto dos Santos:
1) Make sure that your file structure looks like this:
- SD-Card
---- ML
------ MODULES
---------- MAGIC.SYM
---------- raw_rec.mo
2) Set "Pic Quality" to "SRAW" and reboot your camera. After that you should be able to record longer in 960 X 540.
3) If you want to bypass the 4 Gigabyte files size limit, format your SD-card as exFat in Windows. Then use EOScard to make it bootable again.
And for those of you that are still getting magenta frames: You're doing something wrong. I've recorded 1000 frames in 960 X 540 and only 24 of them were magenta. In my opinion that's totally acceptable. And that was even with LiveView ...
Btw. @ 1%: Is there a way to get our 104 Megabyte shoot_malloc back? Edmac Popin was much better than the current build in terms of what was possible. I think it had the best performence until now ... :D
We have to ask a1ex, he made the change. Also voice tags is broken globally.
What change?
excelent to see the 800 and 848 widths in the new build.
I could not record yet, when I press rec button, a message blinks once in LCD "File create error", how to fix this?
also, what is the another module, file_man ?
thanks
I'm getting the file create error too.
There was a change... I think when memory was aligned to 4kb.. suddenly had only 144MB shoot malloc on 6D and only 9X on 600D..
File create error I dunno, fat32 card? Its working fine here thats how I tested 800 resolutions.
* also probably on fat32 long file names aren't supported? I disabled that check since it works on xfat.
I think would be a good idea to make things works on fat32 cards also.
I use the same cards on 600D and on GH2, and I keep ML on cards all the time and no problem using the same card in both cameras, so fat32 is important for me, and maybe for many others.
Quote from: a1ex on May 28, 2013, 05:29:08 PM
What change?
The size of shoot_malloc total used to be 104 Megabyte and suddenly it's only 96 Megabyte ...
That's a really small difference but the performance seems to suffer a lot.
I would really appreciate it if you could increase it again. Maybe even more than before? :D
The LV takes up like 300+ MB... it divides memory into work units (I guess chunks) and sees how many free there are. I can't find where it allocates memory, just checks that free shoot_malloc pool and seems to allocate some then dealocate at startup... I've tried a bunch of ways to make it work :(
We can't even close to compete with 50D/5D2 and even 60D.. they all have close to 200MB.
Fat32 doesn't work for >4gb H264 and 600D can't slice it. So not good FS to use overall. GH2 supports xfat too I think.
Quote from: 1% on May 28, 2013, 07:35:33 PM
We can't even close to compete with 50D/5D2 and even 60D.. they all have close to 200MB.
With its optimal "Pic Quality" setting (Like "SRAW" on the 600D) the 50D has 220 Megabyte shoot_malloc total and the 60D has even 276 Megabyte! At least that's what I've read.
For those cameras you would have to go into shoot malloc after changing settings and see what gives the most memory.
Those numbers make my cry. 600D at least sraw worked (it was the most). On 6D nothing works, only can get less memory.
But at least the 6D has no 21 Megabyte/s write speed limit ;)
I'm still hoping to get at least the 104 Megabyte buffer size back and maybe even some lossy compression ... But I know that the 600D is by far one of the worst cameras for raw video.
Poor 1100D guys. I bet they have something like a 10 Megabyte/s write speed limit and 50 Megabyte shoot_malloc ;D
I think 550D is the worst actually... worse than 500D and no 4gb files. But we are like 2nd worst.
True ... The 550D guys don't even have the option for "SRAW" :)
(I think somebody should try to give it back to them. They are really screwed with their 68 Megabyte shoot_malloc, aren't hey?)
I'm curious: I have no skills in any programming language other than Java and PHP/HTML. But is this actually important? From what I'm reading here I've got the impression that everybody who has an idea of some technical stuff can help with porting and improving Magic Lantern (And I mean not just by testing your amazing work ;D). Is that correct?
(If not, which language(s) are required?)
Its C++ and assembly but if you know ANY programming you can probably figure it out pretty quickly.
Ok, I did the exFAT format and reinstall ML, now the new build is working.
848 x 478 16:9 records without magenta frames at 24fps, but frames skips, something about 1 frame in each 200 frames ( I got 6 skip frames in 1200 frames record).
I did try SRAW, RAW, all canon resolutions in canon menu, fps override, everything... (sandisk extreme 45MB/s)
So my conclusion is: 840 x 472 will be the maximum resolution for 16:9, it is 2% less datarate so it will avoid the skip frames
It would be good idea to enable it. probably it is the final tweaking for 16:9 maximum resolution in 600D
840 won't work.. some of the widths produce pink/static frames.
I'm recording at 920 just fine and even some 11xxx with different aspects. For a slow card yea, I guess keep it like 800 and add more height till it starts screwing up. Also 2nd record usually gives more frames.
I did try successive recordings in 848 x 478 and frames skips... so no solution in the 2nd or 3rd recording session.
I think the sandisk extreme 45MB/s card is fast enough, the limit is the camera buffer.
the 800 x 480 (more height) works, but it is not 16:9, so we are ending at 800 x 450 16:9 at this moment.
what about to try: 842, 840, 838, 836, 834, 832... until find the best possible? in raw each pixel counts for upscaling...
I am just trying to help finding best possible 16:9 for 600D raw...
@ apefos: I think you're doing something wrong.
Like I said: I can record ~ 2000 frames in 960 X 540 without any skips and about 40 magenta frames. With Edmac Popin build I could reach the 4 GB limit (Which is no real limit. I just don't use exFat). If you can't get that, your settings are wrong or your 600D is just worse than mine.
How big is your buffer? ("Debug" tab - Hit "Q" on "Free Memory" - "shoot_malloc total" is what you're looking for.)
Are you sure that you've rebooted your camera after you set "Pic Quality" to "SRAW"? And are you sure that you don't record sound?
I get 960x540 no frame skips no magenta frames with a sandisk extreme pro 95mb/s 32gb card.
I can also do the 1280 x 400 no frame skips, global draw off, with any of the recent builds.
hi guys, many thanks...
my malloc total is 96M, can I increase it someway?
I was not rebooting after changing to SRAW, I did not know it was needed. now the buffer shows <***> instead of <**>
things are working much better now!!! 960 x 540 is working!!! that's amazing!
do you think is it better to let canon menu in 1920 x 1080 24p or would be better to set it to 640 x 480 25p + fps override to 24p?
MANY THANKS!
Quote from: apefos on May 28, 2013, 09:32:35 PM
my malloc total is 96M, can I increase it someway?
do you think is it better to let canon menu in 1920 x 1080 24p or would be better to set it to 640 x 480 25p + fps override to 24p?
Half of this thread is about dev-guys finding a way to increase it :)
Yes, sure 640p with fps override 23.976 (or something near) is needed. Maybe that's your problem also.
And Global draw OFF.
Quote from: vicnaum on May 28, 2013, 09:35:40 PM
Yes, sure 640p with fps override 23.976 (or something near) is needed.
Why? Whats the difference?
Please explain :)
YUV buffer is slightly smaller in 640P so it is slightly better... dunno if that is negated by having to use FPS override or not. Hacked mode both turns off global draw and shuts down YUV buffers.
Thanks again.
I did a 2220 frames recording at 960 x 540 in SRAW, canon menu set to 1920x1080 24p, global draw off, hacked mode off also.
I also can record 1120 x 468, 2.39:1 no problems (did a 1200 frames record)
800 x 600, 4:3 also works, great for anamorphic
No magenta frames (not even one), no frames skip (not even one), WOW!
(one suggestion: 832 x 624 is the maximum possible resolution for 4:3 now, great for 1,33x anamorphic adapters to get 16:9)
Quote from: apefos on May 28, 2013, 09:32:35 PMmy malloc total is 96M, can I increase it someway?
What do you think setting "Pic Quality" to "SRAW" has done? It should have been 68 Megabyte and by changing the "Pic Quality" setting and rebooting the camera you've already increased it. If you want to get even more, just use one of the old builds where we had 104 Megabyte.
But obviously you'll have to sacrifice some of the new features.
Well. I'm glad I could help. Hopefully 1% can concentrate on more important things than adding these uselss 8XX width resolutions ;D
@ 1%: Since I wanted to learn C++ anyway I'll see if I can start with it this weekend and help you improving this awesome firmware addon some day :)
Love the new naming system of the files. Gonna shoot a short music vid with this in a couple days, wish me luck lol.
Here is my VERY quick and hand shaky RAW test. Shot with Helios 58mm/f2 in 1280x544 (ISO 640)
The quality of original uncompressed file is very different. The compression is just killing it :(
I'm so happy with the results! The latitude is amazing!
http://vimeo.com/67164473
Uploaded in original resolution so better to switch Vimeo scaling to OFF
QuoteWhat do you think setting "Pic Quality" to "SRAW" has done?
Crash some canon things using memory or shrink the memory available to photo processes.
Look at the FW dump and try to do some more... I don't think we have to sacrifice any features, just lower memory usage for canon... so maybe cripple photo mode more or something like that.
:-\
I can't get the raw video to create files.
I have 2.3 plus the nightly build (5-29-13) plus the Tragic Lantern build (800 Fileman)
I keep getting "File Create Error" and record doesn't run. I can shoot regular ML video no problem.
I have a fast card (Sandisk Extreme Pro 10).
I've turned off all enhancements and ML options except raw video and set the size to the minimum.
I've also changed RAW to sRAW in the shoot menu.
But just can't get it to shoot video :-(
Have I missed something obvious?
Format your card to exfat, then make it bootable with eoscard or macboot (or re-install ML normally). Put the nightly back onto the card and copy/paste whats in tragic lantern 2.0 to the card. Modules folder goes in ML folder
Quote from: leefie on May 29, 2013, 06:45:35 AM
I have 2.3 plus the nightly build (5-29-13) plus the Tragic Lantern build (800 Fileman)
Hm... I never installed ML nightly builds... just Tragic Latern over ordinary latest 2012 build.
Is nightly necessary?
I also have "File create error" with [600D] 800Fileman.zip.
Tried the latest nightly build from 29 May, but same.
Card is formatted exFat.
Okay yep after a bit of playing around I've got mine recording at 20.5mb/s constant with no dropped frames. woot!
(Havent looked at the footage yet though)
So instructions are:
1. Download the latest nightly build onto a card, from here:
http://nanomad.magiclantern.fm/nightly/
2. Go to https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads
and download the latest file - currently [600D] 800Fileman.zip as of 29th May.
3. Copy the contents onto the SD card root directory, then move the Modules and Scripts folders into the ML sub folder.
4. Put the SD card into your camera, and switch it on. In the Canon menu, set the video resolution to 640x480.
5. Press the trash can button to load Magic Lantern, and scroll across to the 5th menu, 'Shoot'
6. For Pic Quality select Sraw
8. Scroll right to the last menu Modules and select Load Modules now
9. Scroll back to the Movie menu and select FPS override and select 24fps.
10. Scroll down to raw video and click Set
11. Press Q to load the raw video sub menu - select 960x540 resolution (or whatever resolution suits your card speed)
12. Hacked mode - on
Now switch to movie mode on your camera, and press the record button to enable live view if necessary - then press record again to start recording a raw video. All going well, with the SRAW setting you should have three dots/stars for your buffer, instead of two.
If I've missed anything as per above, let me know!
LFN should be going in the next build so no more file create errors.
A quick question I've asked on the 550d thread but no answer, should we be shooting in video mode or photo mode with 550D and 600d cams, does it make any difference? Freeing memory well, I'm limited to 21.5MB/s and achieving no pink frames or drops in 1000's of frames captured, so query is more about 'quality of feed' line skipped or crop, apart from the obvious resolution restriction.
Currently I'm having great success recording 960x408 2.35:1 no drops to exFAT in either Photo (set to RAW) or Video (set to 1920x1080 24fps) mode.
What I'm getting at is the 16GB of raw files I shot the other day in video mode line skipped lower quality than I would have achieved in photo mode?
Sorry if it's a dumb question but this site's like a freaking rabbit warren of threads, plenty of how to build this and that for raw but not so much how to actually use it. :-)
Quote from: y3llow on May 29, 2013, 02:41:51 PM
A quick question I've asked on the 550d thread but no answer, should we be shooting in video mode or photo mode with 550D and 600d cams, does it make any difference?
It doesn't make any difference in picture quality and it should make no difference in performance. But in photo mode you can't set ISO, aperture and shutter speed manually. Sure, you
can change the numbers but the actual aperture doesn't move if you change the number on the display.
So: For manual exposure control, record in Movie Mode.
Or you just turn exposure-override on ;)
The new "[600D] New.zip" build now works okay, without any "File create" error. Thanks!
We got one regression. nanomad made gui-common.c for all cameras but forgot the zoom shortcut for 600D... so its still in the tweaks menu but gone from the file that actually does the work.
I fixed voice tags... its missing the press event on this camera too and had to use unpress.
Quote from: Alia5 on May 29, 2013, 06:25:14 PM
Or you just turn exposure-override on ;)
Right. I've totally forgot that feature since I used it only two times.
Can we just completely get rid of the stock firmware or modes and have a ML build to run everything from?
Hey, a guy can dream, can't he?
Just did a quick test on two SD cards I have.
This is from my (new)
Transend SDHC UHS-I class 10
Write speed------18.5MB/s
Read speed------21.0MB/s
Write speed------16.2MB/s
Read speed------20.0MB/s
Write speed------18.5MB/s
Read speed------21.1MB/s
Write speed------17.1MB/s
Read speed------20.6MB/s
Write speed------19.1MB/s
Read speed------21.2MB/s
Avg write speed--17.9MB/s
Avg read speed--20.8MB/s
960 x 360 24fps Estimate Avg 13.9MB/s
MY MEMORY.COM class 10
Write speed------14.7MB/s
Read speed------19.2MB/s
Write speed------12.2MB/s
Read speed------18.5MB/s
Write speed------15.4MB/s
Read speed------19.7MB/s
Write speed------13.2MB/s
Read speed------19.7MB/s
Write speed------15.6MB/s
Read speed------19.5MB/s
Avg write speed--14.2MB/s
Avg read speed--19.3MB/s
960 x 360 24fps Estimate Avg 12.5MB/s
I was expecting to record a larger frame
with the faster card.
But no.
Why should there be a different reading
for the two SD cards when they are both
recording the same frame size?
hello! I wonder if with a SD 120 mb / s would to improve the resolution of raw video for greater qulidade possible?
http://www.amazon.com/dp/B005025ZXK
Quote from: educosan on May 29, 2013, 09:21:41 PM
hello! I wonder if with a SD 120 mb / s would to improve the resolution of raw video for greater qulidade possible?
http://www.amazon.com/dp/B005025ZXK
Whoa, never seen thise before. But no, sd card controller in the cameras is limited to ~21MB/s. Sandisk makes a 95 MB/s card for way cheaper anyway with great build quality. Maybe in a year or two...
I've been playing around with ML raw on my 600D, just thought I would share my speed tests if it helps the ML team:
SanDisk Extreme Pro 95MB/s 32GB
Write speed------20.7MB/s
Read speed------21.2MB/s
Write speed------19.1MB/s
Read speed------20.9MB/s
Write speed------20.7MB/s
Read speed------21.2MB/s
Write speed------19.4MB/s
Read speed------21.0MB/s
Write speed------21.1MB/s
Read speed------21.3MB/s
Dave Dugdale
LearningDSLRVideo.com
Quote from: CFP on May 29, 2013, 03:42:56 PM
It doesn't make any difference in picture quality and it should make no difference in performance. But in photo mode you can't set ISO, aperture and shutter speed manually. Sure, you can change the numbers but the actual aperture doesn't move if you change the number on the display.
So: For manual exposure control, record in Movie Mode.
Ok, good to know and to be aware of the photo mode restrictions. I've always shot fully manual in every respect prior to testing the raw features. Thanks again.
Quote from: Dugdale on May 29, 2013, 10:35:31 PM
I've been playing around with ML raw on my 600D, just thought I would share my speed tests if it helps the ML team:
SanDisk Extreme Pro 95MB/s 32GB
Write speed------20.7MB/s
Read speed------21.2MB/s
Write speed------19.1MB/s
Read speed------20.9MB/s
Write speed------20.7MB/s
Read speed------21.2MB/s
Write speed------19.4MB/s
Read speed------21.0MB/s
Write speed------21.1MB/s
Read speed------21.3MB/s
Dave Dugdale
LearningDSLRVideo.com
Yes, I get 21.5MB/s max from that card also, it's enough for 960x540 at 2.35:1 (960x408) without dropped frames. But the limitation is the SD controller in the T2i / T3i etc.
photo mode it will probably fake aperture/shutter via expo sim which you can't turn off.
Hello everybody!
Thanks for the help 1% and CFP!
I can record 4GB in 940x540 23,976 fps now.
I'm shooting anamorphic [Senkor 16D], with this resolution and then interpolating algorithm with S-Spline or Lanczos ... is simply stunning!
Anyway, I get up to 4GB 1280x426 nonstop too.
Some points: keep failing formatting in exFAT. Do not know if it's a physical limitation, or is it just my ignorance [most likely :P ]. I'm using the HDD for low-level formatting, and then creating the location with Win8. After that, I run the EOSCard [in Pelican site] and I copy the folders to Boot... but I get nothing, it does not recognize.
Report bug: I made a photographic output this morning and I forgot to do the unload module. I ended up receiving all black frames CR2. So if you are shooting, do not forget to turn off the modules!
Thank you again!
[sorry for my bad english]
Latest is fat32 compatible again. 4gb should be split up into chunks.
Noob to this whole thing, installed Magic Lantern and RAW to my camera for the first time today.
Highest resolution I've recorded at so far is 1440x602 (2.39:1) which looks fantastic. Everything's normal except when I start recording, I can't see anything that's filming, it just freezes on the screen. And I can't seem to have any image size that doesn't start majorly skipping multiple frames after 5 seconds. My card is 30 mbps, and I didn't think that was bad since it will only do 21 mbps anyway. Are either of these problems normal with the T3i?
Turn off hack3d mode lol
1%, how about hack3d mode being off on startup, or labeled like-
Hack3d (LV freeze)
Ah thanks. Still skipping a ton of frames but at least I can see what I'm shooting.
Try lower aspects. 1120x462 is max continuous for me, or 960x540 works well too.
I've tried lower than that and still can't get continuous. It can drop 20 frames at a time.
Quick comparison of H.264 and RAW. Notice the details on the blue towel and wooden block.
[spoiler]H.264:
(http://imageshack.us/a/img11/397/comparisonh264.jpg)
RAW:
(http://imageshack.us/a/img541/7528/comparisonraw.jpg)[/spoiler]
Hi all,
Just found out about this latest update and wow..that is amazing that these cameras can now record RAW of any sort.
Couple questions.. first.. any chance for any sort of RAW compression to help squeeze better res? I would suspect not given the limited processing power of the camera?
Let's say the t3i can't do better than 960x540.. with RAW quality, would uprezzed to 1920x1080 look good or not so good? I would suspect the 4x increase would make it look worse than H.264.
I am also an owner of the Shuttle 2, and using the HDMI out with uncompressed clean (using ML).. would you advise to record that way at the 1620x1080 (then resize and upconvert for 1080p) over shotting the RAW and enlarging?
Lastly, any chance that we'll get a full 1080p clean HDMI out some day?
20 frames dropping after about 50 frames on 960x540, even frames dropping at a pathetic 322p. I'm using a SanDisk 64GB 30 mb/s, but it's recording 12 mb/s. I've seen other people doing better. So the card matters?
The card does matter. Many cards "claim" various read/write speeds but often aren't close to what they claim. This is one reason Black Magic has for example a small list of SSDs that they've tested on their devices, and I proved them right by trying to use a couple other SSDs that were "faster" than the ones they support, that didn't work. I suspect your card may not write near the 30mbs. The cards that seem to be top speed are often the more expensive ones. I've got a Lexar SDXC 64GB with 133x write speed, class 10, I suspect won't be fast enough. I am guessing for the T2/3/4i the 400x should be fast enough, although I wish they'd stick to one rating or another.. like 30mbps or 100x, instead of both. Kind of confusing. I never know what 133x means short of it supposedly means 133 times faster than the slowest SD card.
I am hoping the T3i will get up to 1280x720 RAW in the near future and ultimately 1080p, at which time I'll see how it works on my 133x and probably purchase a more expensive one.
I haven't checked to see if there is a thread yet on what SD/SDXC cards work continuously, but this is so new, I think it's probably best to wait until it's considered near stable to put up a list of cards that work, as I suspect some that work now may not work as well once it gets near stable.
Wow, and I thought I had a good card. Didn't know it was this much of a rip-off before. My Sandisk card is averaging 10 mb/s when it should be 3x that. And yeah, I hope they would just use the mb/s.
Just did another RAW vs. H.264 comparison, and this is the biggest difference I've seen between the two yet. Exact same lighting conditions and exact same camera settings, but the RAW version is at least 10x better.
(http://imageshack.us/a/img835/6590/coinh264.jpg)
(http://imageshack.us/a/img822/2775/coinraw.jpg)
You can tell the difference even more in motion, because even though the ISO is only at 120 the H.264's blurred out background looks just blocky and bad because of the compression. While the RAW version is smooth and natural looking. This is definitely worth getting a new SD Card for.
I have some questions :
1) The resulting dng I get are not clean when I open them up in ACR (of Cineform Studio) ie. they have a green "tint" (or red - depends on what program I am opening the dng's with). why is that ? I see the everyone here displays a "regular" picture...
2) in ACR, the file says : 8bit (on the info line). shouldn't it be like 14bit ?
3) in ACR, how do you turn on the thumbnail display (to the left) so one can synchronize all the photos ?
Noob questions, I know.... but it's hard following everything that goes around here. so, bare with me :-)
I shoot Raw with my 8/16 GB SanDisk Ultra 30MB/s...
Nothing more than 3 seconds still at 960*540...
Doing the ML test and results that it write at 8MB/s...
How it's possible?
This is my first post here, so: Hello everyone :)
Next: thanks to all the ML team. and respect :) You are doing great job here...
and now, to the point:
today I attached 37" TV to HDMI output of my 600d. During raw recording it's great for focus.
2013-05-24 build ([600D] Aspect Lock.zip), standard menu video size 640x480/25, sRAW, 960x540/25 (no fps override), hack on.
Found issues:
- additional-crop-rectangle is not in the middle of the screen and I cannot crop correctly. http://youtu.be/I9foDKlUckw (http://youtu.be/I9foDKlUckw)
- RAW preview with monitor attached hangs up the camera. Need to remove battery.
And sometimes magenta frames... :(
But anyway: thanks a lot for your work... :)
Quote from: neofg on May 30, 2013, 11:50:00 AM
I shoot Raw with my 8/16 GB SanDisk Ultra 30MB/s...
Nothing more than 3 seconds still at 960*540...
Doing the ML test and results that it write at 8MB/s...
How it's possible?
Could be an old card, misadvertised, or your settings may be wrong.
I've updated the first post to include info on cards. I'd say just buy the fastest thing you can possibly find lol, since newer cameras now support UHS speeds.
Quote from: Arthor on May 30, 2013, 12:26:39 PM
- additional-crop-rectangle is not in the middle of the screen and I cannot crop correctly. http://youtu.be/I9foDKlUckw (http://youtu.be/I9foDKlUckw)
- RAW preview with monitor attached hangs up the camera. Need to remove battery.
Change the crop box by turning on panning mode in raw menu and adjust it accordingly.
Not sure about raw preview, sounds like a bug though.
Quote from: AriLG on May 30, 2013, 10:21:21 AM
1) The resulting dng I get are not clean when I open them up in ACR (of Cineform Studio) ie. they have a green "tint" (or red - depends on what program I am opening the dng's with). why is that ? I see the everyone here displays a "regular" picture...
2) in ACR, the file says : 8bit (on the info line). shouldn't it be like 14bit ?
3) in ACR, how do you turn on the thumbnail display (to the left) so one can synchronize all the photos ?
1) At the moment the white balance is just a placeholder. The .raw files have no metadata so raw2dng simply adds fake metadata which results in a wrong white balance. But a1ex is thinking about adding the correct metadata.
2) That's just what ACR suggest you to work with. Simply set it to 16-bit and you'll be fine (If you don't use elements).
3) To synchronize all photos just select all of them and then do the changes. Maybe there's a better way, I don't use ACR but LR.
Quote from: neofg on May 30, 2013, 11:50:00 AM
I shoot Raw with my 8/16 GB SanDisk Ultra 30MB/s...
Nothing more than 3 seconds still at 960*540...
Doing the ML test and results that it write at 8MB/s...
How it's possible?
Your card is simply not as good as advertised by the manufacturer. No real surprise, isn't it? They want to sell these things so they make them look better than they are. A quite cheap SD-card that actually has a write speed of more than 21 Megabyte/s:
- SanDisk Extreme 16 GB SDHC Class 10 UHS-1 45MB/s | Amazon.com (http://www.amazon.com/SanDisk-Extreme-Class-Memory-SDSDX-016G-AFFP/dp/B007M54E08/ref=sr_1_2?ie=UTF8&qid=1369910908&sr=8-2&keywords=sandisk+extreme+45)
I use that myself and it works fine. The 95 MB/s version is said to be good too but ... you know ... 21 Megabyte/s write speed limit ;D
Quote from: Drewton on May 30, 2013, 07:09:15 AMJust did another RAW vs. H.264 comparison, and this is the biggest difference I've seen between the two yet. Exact same lighting conditions and exact same camera settings, but the RAW version is at least 10x better.
Same settings? So you didn't changed the focal length and simply croped the H.264 to match the raw image? If that's true, your comparison is completely useless. To compare H.264 and raw you have to count in the new crop factor you get with raw video! See here:
Width | Cropfactor | Multiple of H.264 crop
1734 = 1.60 | 1
1280 = 2.17 | 1.36
960 = 2.89 | 1.81
720 = 3.85 | 2.41
So if you shoot a video in 1920 X 1080 H.264 at 55mm and you want to compare it with a 960 X 540 raw video you have to change the focal length to 30mm (55 / 1.81 = 30).
Edit: Damn. No I tried to answer that questions and totally forgot what I wanted to ask :D
@1%: Since raw is a dead end on the 600D (Even with 8-bit compression we couldn't record higher than 1280 X 720 :(), what's about recording YUV 422? Is anybody still working on that for the low speed cameras?
I mean, lv_rec still had the option to record YUV 422 "video". It was just to early to be good ... But now, wouldn't it be a nice to make a yuv_rec module for 600D/550D/60D(/6D)?
Has to be investigated, esp lv_save_sndpass size. I wouldnt' say its dead. The 960x540 is about as good as H264.
Quote from: CFP on May 30, 2013, 12:57:49 PM
Your card is simply not as good as advertised by the manufacturer. No real surprise, isn't it? They want to sell these things so they make them look better than they are.
Thanks N/A and CFP.
3 new SanDisk cards, 30MB/s... I thought they're perfect for the job... What a bad purchase. At 8MB/s they aren't even Class 10.
Thanks for the reply.
About the CFP ideas...
Is now possible to shoot H264 video with a 4:3 aspect ratio? I'm asking for this from a lot, but at that time A1ex said it's impossible.
If you shoot with anamorphic lenses in 4:3 and then stretch, you have a 2.35:1 video with the double of pixels...
Quote from: neofg on May 30, 2013, 11:50:00 AM
I shoot Raw with my 8/16 GB SanDisk Ultra 30MB/s...
Nothing more than 3 seconds still at 960*540...
Doing the ML test and results that it write at 8MB/s...
How it's possible?
Same. Cannot get mine to go over 12 mb/s.
Quote from: 1% on May 30, 2013, 01:22:13 PM
I wouldnt' say its dead.
I'm sorry. I am a little pessimist ;D
But if you have faith that there's still space to improve the feature, I'll believe you :D
Quote from: CFP on May 30, 2013, 12:57:49 PM
@1%: Since raw is a dead end on the 600D (Even with 8-bit compression we couldn't record higher than 1280 X 720 :(), what's about recording YUV 422? Is anybody still working on that for the low speed cameras?
I also wouldn't say it's dead. With 8bit we can get a full-sensor 1728x543 with lineskipping. Which then can be stretched to 1728x905, that is just a bit less than 16:9 ratio.
Now it's just that we still have only 14bit, and I'm losing hope that we ever turn it down to 12/10/8...
I have a question: Could you please add a width between 1120 and 960?
Because with an aspect ratio of 2.35:1 these both will give you 1120 X 476 (21.4 Megabyte/s) and 960 X 408 (15.7 Megabyte/s) and that's a big gap between 21.4 and 15.7 Megabyte/s. Especially because 1120 X 476 stops after ~ 1500 frames, even with hacked mode. Something like 1088 X 448 (2.43:1) would be nice. It would need only 19.5 Megabyte/s and it divides by 64 evenly :D
Or 1088 X 463 for real 2.35:1, if the Y-resolution doesn't matter for write speed. Would that work?
1024 X 436 (17.9 Megabyte/s | 2.35:1 aspect ratio) would be nice too since its X-resolution devides evenly by 64 and 128.
1104 x 470 (2.35:1) will be the same datarate of 960 x 540 (16:9)
1088 and 1080 are also great width options.
1024 x 512 (2:1) also deserves a try, almost the same datarate of 960 x 540 (16:9), just a little higher... (or 1016 x 508)
I also have suggestions to add new aspect ratios (1.85:1 was a great add):
2.37:1 because 2560 / 1080 = 2,37 (one of the new digital cinema standards)
2,22:1 because 2400 / 1080 = 2,22
960 x 540 upscales nicely to 1920 x 1080, very close to the quality of H264 MOV files in 1920 x 1080 in terms of resolution. If apply a small sharpening amount and noise reduction in the moment of RAW conversion to DNG, or in the moment of DNG conversion to Cineform (422 10bit avi) the results are excelent.
After some more tests I am still getting magenta frames in 960 x 540. it happens in fat32, exfat, formated cards, hacked mode on or off, sound always off, always in SRAW, magenta frames happens with all the 3 last builds... (but there is no skip frames)
Main development now seems to be to find a way to get rid of magenta frames forever...
Quote from: andjarnic on May 30, 2013, 05:56:44 AM
I've got a Lexar SDXC 64GB with 133x write speed, class 10, I suspect won't be fast enough. I am guessing for the T2/3/4i the 400x should be fast enough, although I wish they'd stick to one rating or another.. like 30mbps or 100x, instead of both. Kind of confusing. I never know what 133x means short of it supposedly means 133 times faster than the slowest SD card.
All of the ratings (minus UHS) refer to minimum MB/s. Manufacturers just throw as many big numbers on them as they can to make them seem better.
Class rating = MB/s (Class 6 means 6 MB/s)
"x" rating refers to times faster than a standard CD-ROM drive speed of 150 kB/s (133x means 133 x 150 kB/s which is about 19.5 MB/s)
and of course MB/s is equal to MB/s
I'm using the "Still Sprinkle Free" build. It works fine. Much less black dots on image.
Unfortunately magenta frames are still there, they seem to pop up in a pattern: 1 magenta....5 normal ... 1 magenta .... 5 normal... I don't know what that means. But afterall it's not that bad, I just have to "hunt" those magenta dng and delete them.
I've been shooting at 960x540. Take a look at my last test:
GH2 / 600D card compatibility (I tested some format options):
when the sdhc is formated in the 600D, it works in GH2 also, even with Magic Lantern instaled on card.
when the sdhc is formated on computer in fat32, it works in 600D, but in GH2 camera says cannot record movies, but it records.
when the sdhc is formated on computer in exfat, and made bootable in eoscard.exe, it works in 600D, but it does not work in GH2.
Using Sandisk Extreme 32GB SDHC 45MB/s original card.
Magenta / Pink frames are the enemy / challenge now.
Everything is working fine, but magenta frames...
It would be good idea all developers concentrate in this major issue from now...
If 960 x 540 @ 24fps works reliable in 600D without magenta frames it will be good enough for a stable release.
I am also noticing exposure changes on the footage (you can see an example on the video I just posted at 0:32 sec).
Exp override is on, shouldn't that take care of it?
Quote from: apefos on May 30, 2013, 07:49:07 PM
Magenta / Pink frames are the enemy / challenge now.
Everything is working fine, but magenta frames...
It would be good idea all developers concentrate in this major issue from now...
Global Draw Off? Do you record in Video mode with 640x480 canon resolution? PAL?
Quote from: apefos on May 30, 2013, 07:49:07 PM
Magenta / Pink frames are the enemy / challenge now.
Everything is working fine, but magenta frames...
It would be good idea all developers concentrate in this major issue from now...
If 960 x 540 @ 24fps works reliable in 600D without magenta frames it will be good enough for a stable release.
There's something wrong ... I do not get magenta frames from a week ago.
What are your settings?
In my first install of the exFat version I got no magenta frames, but after some reinstalls magenta frames went back...
My settings:
camera 600D T3i
card format on camera and on computer (I did try both)
Fat32 or exFat (I did try both)
SRAW (camera rebooted)
global draw off
sound record off
skip frames off or on (did try both)
panning off
hacked mode off (I need to monitore the image on LCD)
960 x 540 (16:9)
canon menu: 1920 x 1080 24p ( I also did try 640 x 480 25p)
fps override off (I also did try on @ 24p)
last three raw video builds
focus frame off
exposure override off
iso: I did try all, from 100 to 6400
malloc total 96M
card: Sandisk Extreme SDHC 32GB 45MB/s
Lens: kit lens 18-55mm, auto focus off, IS off
camera records fine, no skip frames, but magenta frames happens...
It seems magenta frames is a random problem, comes and goes no matter the settings, no explanation yet...
It seems it is related to the "luck" you have in the formating and installing moment...
Advice: I found a bug in Exposure Override: the diafragm in the lens keep pulsing, opening and closing a little bit and exposure changes in recorded file, in raw or mov record, I reported this bug in the bug forum, so I am using Exposure Override off all time, I will use it just to get lower shutter speeds with manual focus legacy lenses without focus chip.
Are the corrupt frames on every raw video you shoot? I still get corrupt frames but only on the first raw video I shoot after start-up.
Quote from: CFP on May 30, 2013, 12:57:49 PM
Same settings? So you didn't changed the focal length and simply croped the H.264 to match the raw image? If that's true, your comparison is completely useless. To compare H.264 and raw you have to count in the new crop factor you get with raw video! See here:
Width | Cropfactor | Multiple of H.264 crop
1734 = 1.60 | 1
1280 = 2.17 | 1.36
960 = 2.89 | 1.81
720 = 3.85 | 2.41
So if you shoot a video in 1920 X 1080 H.264 at 55mm and you want to compare it with a 960 X 540 raw video you have to change the focal length to 30mm (55 / 1.81 = 30).
Edit: Damn. No I tried to answer that questions and totally forgot what I wanted to ask :D
@1%: Since raw is a dead end on the 600D (Even with 8-bit compression we couldn't record higher than 1280 X 720 :(), what's about recording YUV 422? Is anybody still working on that for the low speed cameras?
I mean, lv_rec still had the option to record YUV 422 "video". It was just to early to be good ... But now, wouldn't it be a nice to make a yuv_rec module for 600D/550D/60D(/6D)?
Uh, I don't know about focal length but neither of them were cropped at all. And the RAW video was 1136x640.
Another comparison of some grass (only the RAW was cropped here), with the lower resolution RAW video as the clear winner:
[spoiler](http://imageshack.us/a/img28/4074/grassh264.jpg)
H.264
(http://imageshack.us/a/img812/3735/grassraw.jpg)
RAW[/spoiler]
EDIT: And another with some tree foliage. RAW is definitely better for nature.
[spoiler](http://imageshack.us/a/img33/1801/treeh264.jpg)
H.264
(http://imageshack.us/a/img268/7421/treeraw.jpg)
RAW[/spoiler]
"Are the corrupt frames on every raw video you shoot? I still get corrupt frames but only on the first raw video I shoot after start-up."
I don't believe we should think this way. A reliable system must record correctly since the first shoot and no failures, never.
And there is no time to keep watching every shoot in the set.
Imagine the situation you are paying two actors and one crew assistant for a day work (a minimum situation)... plus transport and food... how many money will you loose if you get magenta frames in an important shoot? for a low budget project, failures must be avoided!
And what about a wedding? there is no replay in a wedding...
The RAW video in Canon DSLR is promissing, but at this moment it is just a toy... We are in early Canon raw days... I believe the developers will find a way to make it reliable enough for serious production,
Shoot LV off = no corrupt frames... memory got some overhaul... resolutions did too. 6D was a champ today... I have to add the changes for 600D.
dont talk about relyability since this is bleeding edge stuff wich is in heavy development >.<
Quote from: apefos on May 31, 2013, 12:04:12 AM
"Are the corrupt frames on every raw video you shoot? I still get corrupt frames but only on the first raw video I shoot after start-up."
I don't believe we should think this way. A reliable system must record correctly since the first shoot and no failures, never.
And there is no time to keep watching every shoot in the set.
Imagine the situation you are paying two actors and one crew assistant for a day work (a minimum situation)... plus transport and food... how many money will you loose if you get magenta frames in an important shoot? for a low budget project, failures must be avoided!
And what about a wedding? there is no replay in a wedding...
The RAW video in Canon DSLR is promissing, but at this moment it is just a toy... We are in early Canon raw days... I believe the developers will find a way to make it reliable enough for serious production,
Trust me, I know all about reliability. My point was, they need specifics about bugs to address them properly. Its hard to tell if raw rec will ever be reliable for paid work, especially on our sd-only cameras.
Not to mention, we get what we pay for ;)
Yea, I dunno whats up with the first boot shot... it gets less frames for me too. First time 960x540 stops... second time continuous. I think something with allocation is amiss.
Either way we need way more than 31*30*28 to get reliable... a bigger buffer will do much to fix some of this.
I can squeeze 10 more frames with new build in 1280x544. Can now shoot 156 frames :)
There's no way the hakers break the limit of 21 mb / s?
Only hacking the WFT interface might yield more MB.
Otherwise its like asking if we can make your USB1.0 as fast as USB2.0
I shot for over 50 seconds in 1080 (canon settings) at 1120x468 2.39:1. First shot no magenta at all. Rock solid... Second through fourth shots progressively got worse, and shorter. Fresh format (exFat) using EOScard, with stable 2.3 and the newest files from 1% as of the morning on the 30th.
The magenta issue seems to be getting worse on my T3i, and I have had no consistency as far as shot reliability. The best luck I had was in 720 mode at 1320x400. a little moire and aliasing, but fantastic dynamic range. then something odd happened. Every other file would read 1320x544, and when played back after importinig into AE, the image would roll like a film projector with a bad film gate. I've tried the 480 mode with several settings with no luck as far as magenta frames, or usable record times. sRAW, hacks on and off. same outcomes. Any thoughts?
Thank you very much 1%.
The new resolutions are working very good :D
For me 960H x 960V @12fps seems to be the sweet spot at about 18MBs. Twixtor is your friend :)
a 1080H x 960V @12fps would make more efficient use of bandwidth coming in just under the threshold for SD controller.
Of course these are for scope uses
I understood the new resolutions in the NewSizing build as an attempt to make things more stable using multiples of 64 or at least multiples of 32. Interesting idea.
I got that behavior other members was talking about: first shoot after formatting with magenta frames, other shoots no magenta frames... I hope we can trust the magenta frames will happens just in the first shoot... It seems everytime when I turn camera on the first shoot is corrupt also...
When I try to record more than 4GB in Fat32 card I get the WinRAR file as a spanning when file reaches 4GB, but when I extract the DNG files using the RAR file drag over raw2dng.exe in computer, all generated DNG are corrupt...
would be interesting idea to enable an option in raw menu to choose:
-allow recording over 4GB
or
-stop recording when file reaches 4GB
(Record over 4GB: on / off) (default off)
also I suggest to make HaCKeD mode off as default, LCD monitoring is needed.
Would be good to see the feature to choose which file to playback enabled again.
I found an issue, but I do not know if it has relationship with the magenta frames. Sometimes the image preview monitoring in the LCD shows some jumps, something like frames was skip in preview... maybe camera is not fast enough to show all frames in the LCD monitoring while recording raw... Sometines this happens, sometimes not... I did not observe if when it happens, if it is in the same moment of magenta frames...
I suggest enable 832 x 608 resolution (useful for anamorphic work), because 832 x 640 is skipping frames.
Would it be possible to make a build with these feature all together?
Video File (to choose wich raw file to playback (from the Still Sprinkle Free build)
Remove the file_man module and make the record stops automatically at 4GB and save the file (for Fat32 cards)
make hacked mode off as default
resolutions from the New Sizing build (with 832 x 608 for anamorphic)
103M malloc 31M+30M+28M from the New Sizing build
make 960x544 the default resolution when we enable the raw rec module
for now these are the best things
thanks
I made 960 default in the next one. Can't chose resolutions that aren't multiples of 64 anymore.
If you use exfat it shouldn't do the spanning. I haven't tested as all my cards are exfat + 64GB. A1ex just tried another fix again. Maybe newer one will do it better. Did you combine all the files before doing raw2dng?
If you want LCD monitoring just turn hacked mode off when you go pick the resolution. I put it on by default because I got tired of turning it on. I got pink frames if I left it on. Since I've been shooting it with it I got no pink frames.
I have to see what size chunk its using for the double and make sure its not using a 32/31MB one.
QuoteI've tried the 480 mode with several settings with no luck as far as magenta frames, or usable record times. sRAW, hacks on and off. same outcomes. Any thoughts?
I haven't had this happen, how fast is the card?
Going to try less aggressive allocation on this camera and see if it helps since now its not eating memory away. 6D is fine with 4MB backup. If pink frames got worse some maybe this is why.
thanks or the answers
please how can I combine the files before doing the raw2dng.exe?
I did a double click on the RAR file but it does not open in WinRar.
It seems after a format and reinstall you can't change the bin and modules more than once, because all shoots starts to get magenta frames again and again.
In that case can you provide 1088H x 960V
thanks
Quote from: 1% on May 31, 2013, 03:32:29 PM
I made 960 default in the next one. Can't chose resolutions that aren't multiples of 64 anymore.
Forgot to add that camera is shooting slightly wider than the indicated crop in 960x960 mode
There is 1088 already. 1088 x 832 is the closest. I'd have to add another aspect ratio.
I just shot 2k frames 960x480 and not a single pink frame... also hacked LV stopped bouncing.
Quote from: 1% on May 31, 2013, 04:11:55 PM
There is 1088 already. 1088 x 832 is the closest. I'd have to add another aspect ratio.
I just shot 2k frames 960x480 and not a single pink frame... also hacked LV stopped bouncing.
I shot 10 Gigabyte of 1088 X 480 and 1280 X 720 (At 12 frames per second), not one single magenta frame.
Used May31 Nightly Build and "New Sizing".
You're doing a great work :D
would it be possible a hacked mode which let the LCD live view monitoring working? hack other things and allow us to see what we are recording.
I kill the LV/HD edmac(pair) and face + some 2K wide edmac. I can kill the last 2 only some way with a setting but IMO the most resource use is from those YUV buffers. Its not just that they make the edmac slower/busy, they interfere with the edmac we are using.
Ideally we need to find another edmac # to use... some stuff got faster when I picked that used edmac. Including rectangle copy. This one is free but may be gimpy. Need to make some sort of looped tester that tries each one and then runs speed test.
ok, good ideas! try it, we need to see what we are recording!
also, as I said, give us a option to record stops automatically when reaches 4GB (spanning must be an option for Fat32 users)
Stop Rec at 4GB: on/off
please do not erase the 960 x 544 resolution, keep it, or keep the 960 x 540. this is the best raw thing from this camera.
You can try enabling the grayscale preview at very low FPS; it's likely to have near zero impact on the recording speed, since it uses the CPU which is probably idle.
I found that other vertical resolutions than 960 gives more moire (dont know why)
so 1088 x 960 would be good even if a new aspect ratio to replace the 9:16 which I cant see a use for
Thanks
Quote from: 1% on May 31, 2013, 04:11:55 PM
There is 1088 already. 1088 x 832 is the closest. I'd have to add another aspect ratio.
I just shot 2k frames 960x480 and not a single pink frame... also hacked LV stopped bouncing.
960 is good, 83something is good. I think I added all x*64.
I know you need to see what you're shooting but whats the point if its all magenta/corrupt?
A1ex is trying to fix the spanning, should be good in the next one; 5d2 guy said it works. Just combine the files into one with file utilities or hex editor. Everyone w/xfat doesn't have this problem and recording 10-20gb files.
Quoteu can try enabling the grayscale preview at very low FPS
So this previews from the raw buffer? That seems like a good option to add for everyone, not just in 5X. Would be a middle ground between blind&fast + seeing if people step out of frame,etc. Hacked mode is turning off GD tho, won't make a difference?
Black and White live view @ 8fps or 12 fps would be ok for monitoring, framing and focusing while recording!
Less than 8fps is useless, 12fps is better for real time focusing!
12fps? you are dreaming :D
1-2 fps is more likely...
1FPS sounds good enough in all honesty. Just enough to see if people stepped away or if your shot got fucked up. Fancy focus moves are not for raw.. maybe on a CF camera.
Please, keep the 960 x 544 (16:9) as is.
and change the (1.85:1) to 960 x 512 (or 528)
so we can compare both in terms of magenta frames and skip frames.
ok, so lets try the 1fps black and white monitoring and see what happens
maybe you can enable an option in menu so we can choose 1fps, 2fps, 4fps, 6fps, 8fps...
FPS Monitoring: 1 / 2 / 4 / 6 / 8
Quote from: 1% on May 31, 2013, 04:58:34 PM
1FPS sounds good enough in all honesty. Just enough to see if people stepped away or if your shot got fucked up.
I love your humor ;D
Even if it was no joke.
Btw. recording 1280 X 720 at 12 frames per second and using an AviSynth script + VirtualDub to make it 24 frames per second in post works very well. I guess Twixtor should work too but I don't own Premiere nor After Effects :(
But AviSynth is amazing for a free software!
I prefer to hurt resolution instead of time. Everything I did until today to change fps in footage gave me garbage results.
960 x 544 @ 24fps or 23.976fps is working ok without skip frames, so we just need to fix the magenta frames (the low fps black white monitoring can be a solution)
Yea, after work I can try it and see if the preview works with dead edmacs. Real time would be nice but if given choice between monitoring + performance I'll take the performance and put down marks.
Just tested the latest build, new sizing. Better than ever recording. 960x544 records the full 4GB without breaking a sweat on a Sandisk Extreme Pro 95mb/s. The only thing is that like you all, I am getting quite possibly more magenta frames than ever. I would say minimum 1 out of every 60 is magenta now. I have to think back but I believe I was achieving good results from "did it fix" in terms of magenta frames.
I can run other tests if anyone has suggestions.
Thanks all and 1%
Probably the aggressive memory did something then.
1088x480, over 2500 frames. Checking now for corrupt frames, didn't see any in playback though. This is a good go-to aspect, height and width is balanced nicely.
I may have missed it, but is there any way to add elapsed time to the raw display, maybe even in place of the frame count? Even if it only updated every 5-10 seconds would be helpful.
Quote from: 1% on May 31, 2013, 03:32:29 PM
I haven't had this happen, how fast is the card?
Going to try less aggressive allocation on this camera and see if it helps since now its not eating memory away. 6D is fine with 4MB backup. If pink frames got worse some maybe this is why.
16GB Sandisk Extreme 45MB/s U1 Class 10
Apologies..... Even though I've been pointing out issues, I want to just say how thankful I am for the work being done, and how absolutely amazing this is.
No magenta frames in the New Sizing build, Fat32, see what I did:
Format card on camera 600D (remove ML)
Remove card from camera and insert on computer
Copy ML 2.3 Stable to card and remove from computer
Insert card on camera and start Firmware update on camera
Reboot camera and check if ML installed ok
removed card from camera and insert on computer
copy the new bin and new directories from New Sizing build
defragmented the card
removed card from computer and insert on camera
global off, 1920x1080@24p, sraw
reboot camera
load modules, set resolution 960 x 544, hacked off
first record, 1GB file, magenta frames happens
second and third record, 1GB each no magenta frames
turn camera off, and on again
first record, magenta frames happens
second and third record, no magenta frames
Everything points to a fresh format and install to avoid magenta frames.
It seems it works better also in defragmented card with all free space.
Is it a free space allocation issue?
I believe the 103M malloc size is helping to avoid skip frames.
In the New Sizing build with 103M malloc I can record 5000 frames at 960 x 544 without skip
In previous build with 96M malloc I got skip frames at 960 x 540 before 2000 frames record (Still Sprinkle Free build)
I think its a memory issue in all honesty. i'll try the larger reserve size.. at this point it shouldnt' cause speed loss or memory loss, just leave more "backup" memory by default.
Something is wrong with the first allocation... or some edmac interferes at first record and then is killed by hack mode and doesn't come back.
Nice thoughts!
Just to say I am using HaCKed Mode "OFF" all the time, with image monitoring in the LCD to see what I am recording.
So is elapsed time possible for raw rec display or would that require the whole module to be re-done?
Try this and you won't get more magenta frames, it worked for me:
Remove the card from camera
Turn the camera on with no card, leave it on
Insert the card
Turn camera off again and count to ten
Remove battery
Turn on the camera (without battery)
Shoot
Now you will get no more magenta frames
8)
I dunno, I didn't get any magenta frames for a week or so (the last one I remember was when I shot Silent Pics with Global Draw On).
Okay, first shot no reformat, in fact I have a question I will pose in a minute because I did a dufus thing. But anywhoo, 1280x382 in 720 mode came out AMAZING!!! no magenta, no skips. decent record time. In fact I stopped it before it quit because I didn't want to wait to see the results. Heading out for more shots. If this one stays consistent, I will be ecstatic, and this will be my primary res for my narrative projects.
forgot to ask the question.... I was in a rush this morning heading to a photo shoot, and forgot to change my card and the quality setting from sRAW. I shot several photos before realizing this, and since it was a timely thing, I cannot replicate the shots for several days. They review fine in camera, but bridge and ACR do not recognize them. Is there any way to save these images, Or am I stuck re-shooting them?
DCRAW or UFRAW should open them. Yea, they are sraw sized.
Also try dcraw -e *.CR2
Quote from: 1% on June 01, 2013, 12:59:37 AM
DCRAW or UFRAW should open them. Yea, they are sraw sized.
Quote from: a1ex on June 01, 2013, 01:01:02 AM
Also try dcraw -e *.CR2
Thanks a bunch....
Apparently my joy was premature. several other shots...all have magenta frames. trying a fresh low level format and reinstall. Fingers crossed
New build has previews + no previews + less agressive 8MB backup. See what happens.
what the less agressive 8MB backup means?
what is bolt trigger module?
I found the previews seems to be useless, recording shows less MB/s and previews just works with global draw on. frames skips in ML preview, and in both ML or Hacked previews there are corrupt frames in recording.
I found when I use canon default preview with global draw off, after I do a playback in a file, next file records without magenta frames.
how can I disable the audio meters in this last build? in the 2.3 stable build there is an option to enable/disable audio meters.
Turn off audio and/or disable override. 4th mode is no preview + hacked mode. This is why I record with LV disabled :)
It would be good idea to re-enable the menu option to have the audion meters on/off as we have in the 2.3 stable version! It is useful for mov files recording also.
did you found the less agressive 8MB backup helps anyway?
@1%
To me it looks like the pink frames are coming from the second buffer usage.
Every time the <**.> second buffer * blinks i get 1 pink frame.
Can the buffer swapping be the cause of our pink frames?
I found some resolution changes that can improve the results. I know WxH must be multiples of 64x32 or 128x16, but these changes I found deserves a try, because it avoid skip frames, best balance between multiples and datarate, please see:
change 832 x 640 (4:3) to 832 x 624 (4:3) because it is the maximum datarate 600d can handle in (4:3). (832 x 640 always skip frames)
832 x 624 will be the best option for anamorphic work, it deserves a try)
keep 960 x 544 (16:9) as it is. this is the best thing 600d can do.
change 960 x 544 (1.85:1) to 960 x 512 because it will be less datarate option when 960 x 544 (16:9) is too much for some cards
change 1088 x 480 (2.39:1) to 1088 x 464 because it is less data rate option compared to 1088 x 480 (2.35:1), and keep 1088 x 480 (2.35:1) as it is.
change 1152 x 496 (2.39:1) to 1152 x 480 because it will be less datarate than 1152 x 496 (2.35:1) and keep 1152 x 496 (2.35:1) as it is.
change 1152 x 464 (2.5:1) to 1152 x 448 because it is the maximum datarate 600d can handle.
change 1280 x 432 (3:1) to 1280 x 408 or 1280 x 400 (because it is the maximum datarate 600d can handle. 1280 x 432 always skip frames.
In the File Browser I can navigate through the files and delete them, but "view" does not work, it just shows some strange caracteres in the LCD.
I would be good to make the "view" works as a playback
Also, re-enable the VIDEO FILE item in the RAW_REC menu would be great, because it allows to navigate trough the raw files and choose which one to playback or delele.
View only opens text files right now.
For resolutions give me a list of aspect ratios to add and I'll add it. I'm not picking the res, its calculated. Realize that if it doesn't calculate out to those X values it will write slower and you'll lose whatever gain (frame size must be a multiple of 512 bytes). Harder to notice on 600D but some sizes write worse whether bigger or not.
So pink frames on 2nd buffer with LV on? LV off? I'll have to test this some more since I haven't gotten any. The buffer situation is sad... only the first chunk is 31MB the others are 30 and 28 which is small and worse on writes. Not sorting them in L -> small results in reduced speeds. On normal cameras they are 32*32*32,etc. We need more memory than this (and without Sraw, which who knows what it crashes in the paths).
the aspect ratios does not change, it is just small adjustments in height values to make them below the maximum data rate 600d can handle.
deleted post, 1280 x 720 in canon menu just gives stretched results... wrong aspect ratios in playback...
after discarding the first shoot after turning camera on, the second and sequential shoots are ok...
960 x 544 @ 23,976 fps works ok (200% to fil fullhd)
768 x 432 @ 37,8 fps (actual fps from 40 fps override) works ok (great for slow motion) 250% to fit fullhd
1344 x 768 @ 11,988 fps works ok (great for twixtor fans and allows 1280 x 720 after some borders crop) 150% to fit fullhd
Here is and example of how the picture is corrupting.
With some Photoshop lines.
Green = Pink part of the frame.
Also the recording area is not what the LV box is showing. (the small red line)
(http://s8.postimg.org/x4595drlx/000684.jpg)
So are the pink frames coming from the crop code or the original sensor data, buffered/unbuffered?
Photos in sraw
I did exactly the same. Photoshop cs6 didn't even work.
Ended up using IranView. But had to convert to jpeg.
Still I got my photos.
Yea, watch out for SRAW.. they kinda look ugly. You can also go to tiff or remake them with dcraw.
My theories on the pink frames:
*Something touches EDMAC and causes this.
*Sync skips
*Something touches memory while recording
*Card too slow
*Too much CPU/EDMAC usage... IE LV is on, GD is on.
Try this: does it fix it? Or worse?
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads/raw_rec.mo%20-%20chek%20Squeeze
Quote from: 1% on June 01, 2013, 06:38:55 PM
*Card too slow
That cant be the reason for pink frames since we have "frame skip" or "end recording" to prevent card write problems.
And the whole frame data is there just not the right part of the picture.
People with slower cards are getting more pink frames tho. It is the least likely one tho.
In "any" constelation im not able to get pink frames since a few versions... in some versions i got 1 in like 1 out of 10 recordings...
"any" since:
Global-draw is ALWAYS off
Card is ALWAYS fat32
Card can reach a max speed of 19.0MB/s
Edit: In Photo-Mode, S-RAW, 24fps, expo. overr., global draw in all modes - fokus preaking + zebras, 960x540, hacked mode off, allowed for frameskips
max write speed about 13MB/s, a LOT of frameskips, 1 corrupt frame (254) of about 400...
guess im not completely immune to them ;)
Here is some thought:
Look at raw preview (ML Grayscale)... in 720P, etc. You see it flash and corrupt... when I record and play back it looks like identical corruption.
Only happens with LV (GD?) on. So something is clearly going on with this. Its like I see the corruption before its happening. Also looks like exposure is changing... see if you guys can repeat.
Hacked with preview - can't see corruption but it happens and looks JUST like above.
Hacked with no preview - perfect.
Regular canon/auto - Same corruption...
so some edmac is drawing on our shit/fucking up sync or cpu usage causes this "jump"
@1%
Trying to compare crop mark and the recorded size i discovered that if you try to take LV screenshot (TL2.0) it just halts the camera.
the new "squeeze" raw rec module works ok (after the first corrupt shoot as always).
just erased all recorded files from card, paste the new module and defragmented the card (in computer)
tested it on 960 x 544 @ 23,976fps = ok
I found that in the first shoot, the monitoring in LCD live view jumps constantly (skiping frames during monitoring while recording)
and after playback this first shoot, when doing the second shoot the LCD monitoring does not jump anymore... maybe this is related to magenta frames?
I am using regular canon / auto LV
Yea, looks like not enough memory to do this. The cam just shuts down. Only 1099K (1366k no modules) with modules loaded... try temporarily moving out file man/bolt rec and see if its enough.
That is 100% related to magenta frames... you can see the magenta frames happening now, see post above.
So for me everything is about GlobalDraw...
All newest of 1% builds...
Canon-Preview, M-Mode, all Movie-Modes (fps ovverride always 24), same settings as in the edited post above...
with global draw-on with zebras and focus-peaking, 2 corrupt of 1000 frames (421, 442)
GlobalDraw of, not any single corrupt frame...
is there any1 that gets pink shit with gloabl-draw off?
Checked 242 frames with GD off.. no pinkerton.
So maybe the bug is from GD CPU usage... so much for cpu not affecting things..
GD off cpu 3.7% gd on CPU 78&
I just did a try with Hacked no preview (working blind), the first shoot is perfect after turn camera on.
Erased the bold and file modules, recorded files, defrag the card (in computer)
I disabled everything I could in ML menu, I also disabled sound in Canon menu, reboot the camera...
keep canon LV on
first shoot: lcd preview monitoring jumps, magenta frames...
playback the first file on camera...
second shoot: lcd preview monitoring NO jumps, NO magenta frames...
So I think we can call this CPU usage issue... turn on CPU usage in debug menu and see where its at when you get pink frames.
LV ON, GD OFF - no ml stuff but seems no pink frames either. Lower write of course (slightly.. do align left to make up a little I guess)
Hacked - Preview off - Perfect frames, turn on whatever you want I think.. gd gets shut off automatically.
So... I think we need 5th mode... gd off, LV on.
94/100% cpu when it jumps.
Tried with a slower, smaller card... formatted exFAT...
Max speed 10.9MB/s
Again same Settings...
Camera crashed at frame 13XX... Canon didn't turn on again, till i did a baterry pull...
smaller files had no pink stuff... didn't look at the crashed one though
So I think I found a way to work more reliable:
install ML and raw rec as I said in one of my previous post... just look back here...
erase every file on card, defrag it (on computer)
turn camera on, disable everything you can in ML and Canon menu. set canon menu to 1920x1080 24p
if you want slow motion or higher resolutions you can use fps override
choose a resolution and fps combination which is below 21MB/s
keep canon LV preview on
shoot a first 500gb file (you will see LV image jumps in this first shoot)
playback the first shoot it until the end
now you are ready to shoot...
you can use the canon LV for monitoring, but keep looking at the LCD, it seems if image jumps you will get magenta frames
cannot see cpu usage while recording, the yellow caracteres showing cpu usage is under the raw rec caracteres in the recording moment...
did another record, no jumps in LCD monitoring and no magenta frames, things points these issues are related to each other.
so... everthing as always... normal canon preview, no hack3d mode(!) but GD-ON
i got CPU of 99%-100% sometimes 97,X%... (cant check in record cuz the "raw-rec-overlay" is just above the cpu usage, just as apefos said)
GD-Off CPU is about 35-37%
cpu usage before recording shows between 38% and 43%
I am keeping the canon LV preview always ON (do not want to work blind!!!)
I disabled everything I could in the camera: autofocus, IS, exposure override, global draw is OFF, sound, fps override, focus frame, and so on... all things on both menus I could disable I did. erased other modules.
another "second" recording and no jumps in canon LV and no magenta frames... (1007 frames file)
raw recording disabled cpu is 30-32%
raw recording enabled cpu is 38-43%
(before recording)
if raw recording overlay is in bottom of screen we can see cpu usage while recording.
Oh! Finally! Fixed the squeeze koeff to 3:2! Thanks, waited for it.
Started getting pink frames, btw :( (even on previous build, just after saying I didn't get any for a moment :))
just threw my littly dslr on my stone-aged tv-capture-card to show my settings... (bad color comes from the capture-card)
first and second recording after reboot... (turned pic quality to sraw before reboot, obviously)
any flickering on the cans comes from 2 crt-monitores
http://youtu.be/otDEKVmMujI
corrupt frames as numbers are cut off in the video...: GD-on #21, 458...
how i installed ml? used to 2.3 stable installer from camera, threw 1%s files on... nothing special...
other card: formatted exfat in windows, used eostool to make it bootable, thre files on it... nothing special again, shows exactly the same behaviour...
not funny defragging or stuff...
@apefos: or @anyone... could you also try like this, since i dont get any pink frames without GD...? videomode or even photo-mode doesn`t matter.
Same story here.. as long as GD off everything is OK.
So to preview I would GD off and just leave the LV on.. it cuts your write but not as much as other modes. You can also cheat and use 640x480 to preview... that YUV is actually smaller so less effect on write speed.
Grayscale preview at rest (ml previews) will be the same CPU as writing, when you see the jump pink/corrupt frame. I can see it flash red sometimes between over draws when recording too. Grayscale preview is made with the CPU and uses GD.
I just have zebras/histo on and its this high.
Funny on 6D cpu usage can't be measured but grayscale nor GD affect write too much... maybe lose like 1MB or less at worst. This is why a1ex took LV killing off of regular hacked mode... but on digic IV its bad news. I'll see how 50D does, expecting something in the middle between this and digic V.
Thanks @Alia5
My first shoot is always corrupt, but second shoot and others are OK
My settings are similar, but other things disabled...
I do not use fps override, I set 1920x1080 24p in Canon menu.
I used 11,988 fps override to record 1344x768 without skip frames, and 37.8fps override in 768x432 no skip also
It seems your card is slow, I can record 20.8MB/s 960x544 @23,976 fps and no skip frames in 4gb file.
I use Sandisk Extreme 32GB 45MB/s, this card performance is perfect for RAW.
From last install (Squeeze build) until now things are ok for me (from second shoot and so on...)
It seems first raw shoot is something like "heating the tires" in F1 first round drive...
bad news, yeah... but i'm pretty happy with wich we already got... have 14-bit raw-video! yeah its cropped but we have to deal with it...
workflow works pretty well for me... instead of color-grading we now just develop some raw files, not a big deal at all...
@apefos: strange that your first record is broken and mine not...
well my card can also get up to that speed, but i need to kill LV :( my other card however can only reach up to 10.9MB/s
My first shoot is corrupt when I leave Canon LV on
I did a try with canon LV off (hacked no preview) and the first shoot was ok
but I need LV, I cannot work blind!
Corrupt frames on first shoot with 640x480 too?
I've got 156 frames with 1280x544 without any magenta frames at all...
Not sure why..
Anyway going to start saving money for 5Dm3 :)
Btw, shoot something today, and noticed that the first frame of the video is the same as the last frame from previous video. Dunno, maybe it's RAWanizer messing something up, can check tomorrow again with raw2dng.
Did another sequence of tests:
By first shoot I mean the first time you hit record after turn the camera on.
When canon menu is in 1920 x 1080 24p, the first shoot is always corrupt. I did a test moving the camera during the shoot and I can say for sure the magenta frames happens in the same moment when there is a jump in image monitoring in LV while recording.
In 1920 x 1080 24p the second shoot is always ok.
The first shoot is ok when using hacked mode - no preview.
Thanks for the advice about 640x480 preview. I did set the Canon menu to 640 x 480 25p and fps override to 24p. So I reboot the camera and start recording 960 x 544 @ 24p and there was no jump in Canon LV monitoring and no magenta frames in the first shoot. No skip frames also.
It seems things are perfect now!!!
more tests using Canon menu set to 640 x 480 25p:
768 x 432 (16:9) @ 37,698 fps (actual fps from 40 fps override) working ok (great for slow motion) 250% scale to fit fullhd, 167% scale to fit 1280. If 37,698 is too much, try 35 fps override.
960 x 544 (16:9) @ 24 fps working ok, best 16:9, 134% scale to fit 1280 (133,33% scale) or 200% scale to fil fullhd
1344 x 768 (16:9) @ 12fps working ok, best highest resolution for 600d, uses almost all the sensor area, 12fps can turn to 24fps in post... also allows a small crop to delete borders to get 1280 x 720 after processing to 24fps, no scaling needed for 1280, 150% scale to fit fulld considering border crop to remove border artifacts after converting to 24p
I have a request which will be usefull for everybody:
The overlays are inside the 1344 x 768 frame, so changing it from three lines for two lines and put it a little more up to be above the 1344 x 768 frame. (I would like to use the frame at center to use the center of the lens)
change this:
Buffer usage: <**.>
Capturing frame 765...
M01-1748.RAW 833 MB, 19.3 MB/s
to this, (and a little more above the 1344 x 768 frame):
Buffer usage: <**.> Capturing frame 765...
M01-1748.RAW 833MB, 19.3 MB/s
or put these two lines design below the 1344 x 768 frame
thanks
I also have a request to enable 1280 x 400 in 3,2:1 aspect ratio and 832 x 624 in 4:3 aspect ratio
(maximum resolution for these widths considering the data rate)
thanks
I'm hoping first shoot might be fixed now :)
Quote from: 1% on June 01, 2013, 11:05:55 PM
I'm hoping first shoot might be fixed now :)
Awesome stuff, thanks for enabling us lowly 600D users to experience the joys of raw.
Also made canon preview turn off global draw when recording. Might make an actual preview mode usable.
Allocate Fix build feedback:
same behavior as before shooting 960 x 544:
if canon menu is set to 1920x1080 24p the first shoot is corrupt and second shoot is ok
if canon menu is set to 640 x 480 25p and fps override set to 24p, first shoot is ok
secret is already found: 640 x 480 25p in canon menu + fps override = no more magenta frames!!!
another feedback: global draw was not turned off while recording. I need to turn it of in ML menu
First shoot still corrupt with GD off 1080P? Wasn't for me.
I replaced the bin and the mo in my card with the alocatte fix version. Maybe my camera is still loading the old one? Is this possible?
I can see a color bar showing the memory when I click Q to see the malloc total.
I think we do not need to worry so much about magenta frames anymore, setting canon menu to 640 x 480 25p and fps override to 24p is enough to solve this issue, at least in the last hours no more magenta frames with these settings.
also auto hide global draw is not so much important, we can disable it in the ml menu.
what about to take a look at the requests I did in last posts? will help a lot. thanks
Height is calculated... I can't add a different height, you have 4:3 already.. I dunno about 3.2:1?
You mean combine buffer with frame count? I'll try but they constantly redraw so we'll see if it looks "interesting" or right.
My request about 3,2:1 aspect ratio is to make possible 1280 x 400 (the maximum resolution for 600d datarate with 1280 width @ 24p)
about make the overlays just two lines, this is to avoid overlays to be inside the white frame when using 1344 x 768 resolution
I found two lines could solve, but if you need to write three lines, try to put them near the top or bottom of LCD, to make them appear outside the 1344 x 768 frame.
when using 640 x 480 25p in canon menu there is image in the top and bottom of LCD so the overlays can be near the top or near the bottom of LCD, leaving the 1344 x 768 white frame clean to see what we are recording.
Sorry 1%... but global draw is not shutting off for me...
Edit: Found out something new for me... Dunno why i didn't try earlier...
Not much about video, rather photography:
Doing lots of Action-Sports photography...
Using 720p-mode in highest res possible at about 16-20fps making that kind of sequences...
https://www.facebook.com/photo.php?fbid=542667595772954&set=a.542667119106335.1073741829.542633299109717&type=3&theater
i got something like working sRAW, i got more fps (even more than a 1dx), and i can get more frames!
Need to sync the flash to it!
Next week i'll graduate, finally, after partying (HARD), i have to set up the compiler again and do some work! :)
Besides magenta frames there is other thing happening: exposure changes during recording. Seems the camera is auto exposing in an inverse way. When I shoot inside, where it's darker and then point to a window the camera adjusts the exposure to even brighter which is the opposite of a normal auto exposure.
Anyway I'd like to get rid of this auto exposure and have control over it. I've seen RAW videos on youtube with the same problem.
Any ideas?
take a look at these two pictures. they show the overlays inside the 1344 x 768 white frame.
my suggestion is to put the overlays a little more to the top to go out of the recording frame and also a little more to the right to get out of the black area of the LCD.
you can also put some information above the white frame, near the top of lcd and some information below the white frame, near the bottom of lcd.
(http://apefos.com/upload/rawoverlay1.jpg)
(http://apefos.com/upload/rawoverlay2.jpg)
QuoteSorry 1%... but global draw is not shutting off for me...
I didn't make a bin auto shutoff for canon preview yet. Its in the source only.
I see what you're saying though... in 640x480 mode its going way over the frame. I think it would have to go on the bottom.
Overlays in the bottom will be good, maybe you can do it in just two lines instead of three as we talk in previous post.
Quote from: gebo on June 02, 2013, 01:31:17 AM
Besides magenta frames there is other thing happening: exposure changes during recording. Seems the camera is auto exposing in an inverse way. When I shoot inside, where it's darker and then point to a window the camera adjusts the exposure to even brighter which is the opposite of a normal auto exposure.
Anyway I'd like to get rid of this auto exposure and have control over it. I've seen RAW videos on youtube with the same problem.
Any ideas?
Set acr to process 2010 instead of 2012
Got a 95 mb/s card today which makes this pretty awesome. I can get at least 440 frames/18s from 1216x512 now which is very usable for film making. No magneta frames for me.
There's something really unique and exciting about this - not being able to properly see what you've shot, or hearing actors' performances, until you process it on the computer. So watching it later is more of a surprise. It reminds me of working with film in that way.
EDIT: Actually have some magneta in 1728w.
Yes, I confirm the bug:
- Some RAW files have the first frame DNG from previous RAW sequence. It's not identical to the last frame from previous RAW, it just somehow is written to the next RAW container instead of the previous one.
Also when I playback some RAWs in-camera - they're displayed very black and over-contrast. And other RAWs does not - displayed normally, smooth grayscale.
Can we have a feature to input custom aspect ratio and frame size via an editable data file?
It seems to me this would remove the need to beg for custom settings to be hard coded, which is a practice that has not worked for me ever, so far :)
Thanks
It would have to be a specific config file for raw_rec. All you would get to set is W and aspect.. doesn't seem worth it.
Playback issue is a bit weird, they seem to play back normally for me, just slow and grayscale.
Have to test 1728... that area had problems originally. Full res would come out at the wrong width (all frames were pink). Hopefully this was sloved with raw rec rewrites. Other pink frames would be from GD.
Quote- Some RAW files have the first frame DNG from previous RAW sequence. It's not identical to the last frame from previous RAW, it just somehow is written to the next RAW container instead of the previous one.
Either this is a converter bug or last "cut off" frame remains in memory. I haven't seen this with in camera playback. Will be on the lookout.
Latest commits are for fseek and playback of any raw vids from file man. Going to make a build with that soon as I can.
Quote from: 1% on June 02, 2013, 05:04:24 PM
Have to test 1728... that area had problems originally. Full res would come out at the wrong width (all frames were pink). Hopefully this was sloved with raw rec rewrites. Other pink frames would be from GD.
1728 works okay now, using it from time to time.
Quote from: 1% on June 02, 2013, 05:04:24 PM
Either this is a converter bug or last "cut off" frame remains in memory. I haven't seen this with in camera playback. Will be on the lookout.
This appears in RAWanizer, and in raw2dng, and even in-camera (btw, if changed resolution of the next recording - then the first frame is garbage). So seems that it remains in memory. Than means that there's a bug there somewhere (maybe causing pinkframes too?)
Quote from: 1% on June 02, 2013, 05:04:24 PM
Playback issue is a bit weird, they seem to play back normally for me, just slow and grayscale.
I will try to picture how it looks on-camera, to test whether it's a playback issue or recorded raw issue. Just need to "catch" it, and also need to have the possibility to playback earlier raw-file, so waiting for new build.
Also I'm having random pink-frames from time to time. Say the first one is with pink one, then I can do 5-10 videos without any pink-frames. And then a couple with. And then without again...
I remember that when I was using "[600D] Aspect Lock.zip build + newest raw_rec.mo" on 27 May (see video in reply #295 http://www.magiclantern.fm/forum/index.php?topic=5494.msg41262#msg41262 ) - I didn't get any pink-frames at any resolutions (all complete recordings from that day are in the video, and there are no pink frames visible)). And on one of the latest builds they appeared again.
If you're going to move recording stats to the bottom, so it doesn't cover CPU usage, then I'll investigate the CPU stats and it's dependency on pink-frames. Maybe some service runs in the background occasionally and loads full-cpu? Or something...
Mainly shooting 720p squeezed, GD off.
Quote from: 1% on June 02, 2013, 05:04:24 PM
It would have to be a specific config file for raw_rec. All you would get to set is W and aspect.. doesn't seem worth it.
It would be worth it to me and anyone who wanted to experiment with custom sizes, but I have come to expect that useless begging wont help me :)
Its such a shame that I have 3MBs of available bandwidth that I am not using
It doesn't work that way, sizes have limitations for writing. You think it will write 3MB faster but it will write slower if not fitting the 64Xw or 512 constraints.
Haven't moved indicators yet but the new playback/GD off in canon preview is up.
Can't add any more widths, used all multiples already. More aspect ratios I can.
Weird if its pinking up in 720P with GD off... I'll have to shoot a bunch of long files and see. I made the memory less aggressive between then but I don't think any other major changes. I can put it back since pink frames are from CPU hiccups. Preview lets you see them real time.. but also causes them..
Quote from: 1% on June 02, 2013, 05:45:15 PM
Weird if its pinking up in 720P with GD off... I'll have to shoot a bunch of long files and see. I made the memory less aggressive between then but I don't think any other major changes. I can put it back since pink frames are from CPU hiccups. Preview lets you see them real time.. but also causes them..
Dunno, maybe worth a try. The videos aren't long. I shoot high res like 1536, 1600, 1728 etc, with 100-300 frames - and sometimes they appear (3-5 of them for 200-300 frames).
Yesterday was a worst pink-day - shot a great thunder-storm from inside on a field, but each and every vid had pink-frames :-(
Today shot kids in a park, and got only 2-3 shot corrupt of around 20 shot.
Maybe it's some electro-magnetism? :-D
---
Btw, raw over-contrast playback is a playback issue. Just caught it:
(http://www.naumik.com/temp/scr4/20130602-iw9-89kb.jpg)
You can see that the same video played twice - first one on the left is very "blacky", and the second playback (and beyond) - on the right - it played back normally.
Then shot a bunch of videos without noticing playback issues (except the first frame from previous happening sometimes), and caught it again, but after second playback it also became normal.
So just some playback problem.
Quote from: 1% on June 02, 2013, 05:45:15 PM
It doesn't work that way, sizes have limitations for writing. You think it will write 3MB faster but it will write slower if not fitting the 64Xw or 512 constraints.
Can't add any more widths, used all multiples already. More aspect ratios I can.
I am running 18.4MBs at 960Hx960V @12p (Scope plus Twixtor to 24p) Looks good :)
I request 21 MBs at (W)Hx960V @12p where (W) is anywhere between 10-20% wider than 960. Surely this is possible while keeping the vertical at 960V?
I found 1664 x 944 @ 8fps useful, maximum possible for 8 frames per second.
the 640 x 480 25p Live View Preview does not cover this resolution at the sides, but raw video records ok, no problem.
no skip frames, no magenta frames.
so the overlays must allow to see this white frame from 1664 x 944 also.
overlays in just two lines, one near top and one near bottom will be the solution.
See the 1664 x 944 white frame and the overlays inside the 640 x 480 LV preview:
(http://apefos.com/upload/rawoverlay3.jpg)
(http://apefos.com/upload/rawoverlay4.jpg)
(http://apefos.com/upload/rawoverlay5.jpg)
(http://apefos.com/upload/rawoverlay6.jpg)
Yep, I know I'll figure out a way to move those.
5 mins solid 960x480 - no pink frames w/canon preview. Going to try higher res.
Would bee good idea to put Canon LV preview as the default when enable the raw rec, to avoid we keep changing it all the time.
Global Draw goes OFF when hit rec, it is working, but just works in canon option, does not work in auto option, so move canon as the first (default) option will be good.
Also it will be good to enable a STOP button when files are in playback. In file browser, when file is playback, the only way to stop is to press half shutter, then we need to navigate again to go to file browser again. a stop button can stop playback and go back to the file browser folder.
Stop is 1/2 shutter, probably need to do the default as you said... auto is useless and will lead to magenta frames in 5x.
But about moving the indicators:
Realized its a little bit impossible.
*Shoot full sized at lower fps.. indicator draws over frame.
*Shoot zoomed 5x and use dolly, indicator will draw over frame
*shoot left, dolly up, indicator draws over frame
There is no place to draw it and have it be 100% in all cases in 640p, 720p, 1080p, zoom. Feels like an exercise in futility. Even one line at the bottom would draw over a full crop. Only option would be to turn it off or turn only buffer on (which can still draw over frame)
1288x720 12fps -3.5k frames no magenta.
Surely it will overwrite something. It's the matter of _how much_ it will overwrite. Now it overwrites the CPU load :-)
One line in the bottom (or top) looks like the best option.
Problem is that the indicators contract and expand... with drawing one line it will draw over or have left over characters and look jacked up.
I'll see what happens just putting it on the bottom.
Remove all the titles and keep just what really matters, just one line at bottom, very low bottom:
<**.> 5247F 3984MB 20.8MB/s 0001.RAW
where:
<**.> is the buffer
5274F is the frame count
3984MB is the file size
20.8MB/s is the datarate
0001.RAW is the filename
Worth a shot but the numbers contract.
So you'll get stuff like this:
<**.> 5247F3984MB 20.8MB/s001.RAW
take a look in this design:
(http://apefos.com/upload/rawoverlay7.jpg)
to avoid numbers contract use two underline between them:
<**.>__5247F__3984MB__20.8MB/s__Jun02-0001.RAW
in the source code like this:
<**.>__
5247F__
3984MB__
20.8MB/s__
Jun02-0001.RAW (between date and number in file name do not use underline, use hifen "-")
Quote from: 1% on June 02, 2013, 08:40:30 PM
Worth a shot but the numbers contract.
So you'll get stuff like this:
<**.> 5247F3984MB 20.8MB/s001.RAW
Then format it :) With spaces, tabs, or whatever. Leading zeroes, etc...
Yea, my plan is to try that and see if its corrupted or not.
go ahead, let us see what you get...
you can also use underline "before and after" in the code:
_5247F_
_3984MB_
_20.8MB/s_
I believe the programing language have solutions to this, but I know nothing about programing...
for the internet this works:
http://en.wikipedia.org/wiki/Markdown
http://en.wikipedia.org/wiki/Punctuation
well, we just give ideas... programing is up to you!...
I see that the problem is that every line of text is called from different function, so it will be hard to combine everything in one line.
But also I see that there are coordinates, so maybe the parts of text can be just spread across the screen horizontally and hope that they won't overwrite each other?
Stuff with coordinates I can just move... but that bmprintf isn't super for this. Trailing characters or underscores don't matter. Either can hard lock it %08d or leave it to contract/expand %d,etc.
Well... it depends on the way how it is coded...
If it all gets into 1 string we would just have to append an extra character on the strings before joining them into one string to draw
if there are 3 seperate overlays, just change coords...
if i wouldn't graduate next week i would do it :(
Quote from: N/A on June 02, 2013, 02:49:14 AM
Set acr to process 2010 instead of 2012
It's already processing 2010...
Any more ideas?
Hacked mode turns off auto exposure and auto white balance.
Quote from: 1% on June 03, 2013, 01:11:46 AM
Hacked mode turns off auto exposure and auto white balance.
Is there no other way? Not being able to see what we're shooting is a pain...
I'm getting exposure changes as well, hasn't happened before the latest build. Think I've found settings for a good preview AND no bad frames.
Sandisk 95MB/s
Rokinon Cine (manual focus/aperture)
NTSC 640x480, override to 23.976fps
Expo override on
Liveview on, Cropmarks on with custom crop found here- www.magiclantern.fm/forum/index.php?topic=3047.0 (http://www.magiclantern.fm/forum/index.php?topic=3047.0)
Raw Video:
1088x480
2.39:1
Framing: Center
Preview: Auto
Delay: 2 sec
Pic Quality: sRaw
Shutter lock on
Force LV: Off
Can someone else check this as well? Also, on the first playback of the raw file, it works fine. On second playback, it starts to play then goes to the "No Image" screen with the raw vid info still at the bottom.
Hi, first post here, so I'm a little confused.
Tried out raw video on the 600d today, very impressive, however I was using the 2.35:1 aspect ratio(If I'm gonna have to crop it I'm happy with 2.35:1, as I'd sometimes use it anyway and it was just a test) at 1152*400 IIRC. I also took a regular video from the exact same spot, at 1280*720, I upscaled the raw video to 1280*xxx(presuming I could just compare) however the raw video was not only stretched horizontally a lot more, but also seemed to be zoomed in further.
I was hoping somebody could explain to me what I've done wrong
Thanks
Magnus, read through this thread.
http://www.magiclantern.fm/forum/index.php?topic=5520.0
Which part specifically? I've read through that thread many times and being pretty clueless on a lot of it I find it difficult to find anything relating to my issue.
Its not an issue, that's how it works. Record in 640x480 mode to avoid stretched files.
I was more meaning what's the correct way to stretch it back to the correct aspect ratio, e.g half the horizontal resolution
Nothing changed in regards to expo in the last build tho. Have to try 50D trick of disabling the buffer.. made 6D write speed with preview on = hacked lv speed.
Have to see what happens.. maybe AEWB has to turned off for all modes.
This isn't a big deal but my 8GB Sandisk 95 shows 7.3GB in LV but 7.9 on my computer.
Quote from: magnusrn on June 03, 2013, 03:43:18 AM
I was more meaning what's the correct way to stretch it back to the correct aspect ratio, e.g half the horizontal resolution
There is no FAQ yet, because changes are evolving constantly. First and most important - raw is a crop from the sensor center (or side), and that's the biggest problem - cause you get even more crop to your 1.6x canon crop.
Also setting different canon modes impacts on how raw is shoot:
- 1920p mode is normal, but can be more slow (cause canon YUV buffers are big and consume more space).
- 720p@50/60fps is squeezed vertically at 166% ratio, so you can record more sensor at the same bandwidth (so less crop). But you loose vertical details and need to stretch it in post by 166%.
- 640x480p mode is fast (cause YUV buffers are small and leave more memory/cpu to raw) - so that's a preferable mode if you don't like squeeze.
Also you need to control fps with FPS Override (cause raw can't shoot long on 50/60fps - too much bandwidth).
That's generally it. Read the whole thread from the beginning, and you'll understand much more about it.
Lots of tests yesterday, Sunday, and things are working ok. Just need to keep Picture Quality in SRAW and Canon menu in 640 x 480 25p. So I do a combination of resolution and fps override below 21MB/s and no skip frames, no magenta frames. I can use canon LV preview always, no problem. The Global Draw off when hit record helps a lot, because I can look at histogram, focus peaking and zebras before start record and it disables when recording and enables again after stop rec. good feature.
Quote from: apefos on June 03, 2013, 01:57:43 PMI can use canon LV preview always, no problem. The Global Draw off when hit record helps a lot, because I can look at histogram, focus peaking and zebras before start record and it disables when recording and enables again after stop rec. good feature.
I must have missed that... how do you do it ?
NM ... found it
BTW
why isn't this thread sticky ? (all other major RAW topic - are...)
Shot my first music video with raw today ;D
The shoot went amazingly smooth, nothing huge but there were lots of tight angles and low lighting shots. The build ran great, I got a few corrupt frames but they're almost always right at the beginning before the action starts.
Biggest concern is if the music will sync with the vids. Guess I'll find out soon.
when i try to "Load modules now" my 600d just freezes
any solution here ,
or is there anything i'm doing wrong to start raw on my 600D ?
Quote from: N/A on June 03, 2013, 07:11:22 PM
Shot my first music video with raw today ;D
The shoot went amazingly smooth, nothing huge but there were lots of tight angles and low lighting shots. The build ran great, I got a few corrupt frames but they're almost always right at the beginning before the action starts.
Biggest concern is if the music will sync with the vids. Guess I'll find out soon.
Great! Post it when you're done!
Quote from: N/A on June 03, 2013, 07:11:22 PM
Shot my first music video with raw today ;D
The shoot went amazingly smooth, nothing huge but there were lots of tight angles and low lighting shots. The build ran great, I got a few corrupt frames but they're almost always right at the beginning before the action starts.
Biggest concern is if the music will sync with the vids. Guess I'll find out soon.
Could you please post your exact settings that let you work continuously. I have tried different variations and the pink frames seem hit and miss. There have been times that I have been able to record continuously @ 960x544 on ocassion and get zero magenta frames and other times it happens one after another.
Another couple of questions I have are as follows:
Is there any degradation of image quality between the options in the Canon menu, 640x480 vs 1920x1080
Second question is, what would make the live view lag when panning. The image seems to lag or stutter when panning around, even at a really slow speed. This had never been an issue on previous builds and I just started noticing it after the latest build. The lag almost always indicates that there will be magenta frames.
The image also seems really grainy when it is finally rendered into video.
The settings I use most are 960x544 (Canon Menu set to 1920x1080)
-SRAW
-GD off
-FPS override off
-Video Hacks off
- freshly low level formatted with EXFAT Sandisk Extreme 45 /mbps
-current build of tragic on top of current Nightly.
-RAWNIZER used to retrieve DNGS
-DNG imported to AE AF and rendered at lossless
Any advice at all would be great. I have read this forum from back to front and still had these questions. I am aware that this is still in the very early stages. I'm just trying to figure out what everyone else that is getting semi stable and consistent video is using. Thanks in advance.
I posted my settings about 10 posts up. Quality is the same. Not sure why it lags, maybe you have something else on?
Next trick will be turn off canon drawing.. Will see if this helps GD situation or if it still pinks up.
After that I need to figure out a way to free the blue memory when NR is off. 6D already has 255MB.. we can have a few more buffers for sure.
Quote from: creativx on June 03, 2013, 07:14:11 PM
when i try to "Load modules now" my 600d just freezes
any solution here ,
or is there anything i'm doing wrong to start raw on my 600D ?
no one ?, i really want to test raw, but it doesn't seems to work for me
Make sure MODULES folder is inside ML folder
This was my problem first, but even with the. Modules folder Insider ML Folder, my. Eos 600D freezes
I've tested CanonPreGdoff + Fileplay.zip and of the 3 clips I shot, one was corrupted (first one) and the other two had NO magenta frames. I shot about 1400 frames and they were all OK! This is great!
Resolution 1024x448 24fps
Canon 1080p 24fps mode
Hacked mode off and everything else off
Hey there, sorry for the noob question but is it possible to shoot at least 6-7 seconds in 720p without upscaling and without magenta frames?
Bin must match modules and you have to have magic.sym from the same zip as the autoexec.
Is 640x480 mode supposed to be better for RAW video? If it's better for performance is it still worse in resolution?
I seem to get more frames and less magneta.
640x480, 1080P both modes are all the same raw input. Just 30fps needs to be overridden.
Crop is slightly different raw, zoom is bigger raw. 720p is squished raw.
You can use any mode you want, with GD off shouldn't get any pink frames.
Quote from: 1% on June 04, 2013, 02:56:01 AM
640x480, 1080P both modes are all the same raw input. Just 30fps needs to be overridden.
Crop is slightly different raw, zoom is bigger raw. 720p is squished raw.
You can use any mode you want, with GD off shouldn't get any pink frames.
I still get pink frames with GD off in resolutions about 1280w. Setting the camera to 640x480 mode with seemed to fix it though.
With those resolutions i think i will quit trying to get Raw videos, i think i prefer the h264 with some amazing lens and filters and then a "perfect" cc. 10bits Would be enough for us and probably we would able to record 1280*720p with no problems.
Quote from: Drewton on June 04, 2013, 03:31:16 AM
I still get pink frames with GD off in resolutions about 1280w. Setting the camera to 640x480 mode with seemed to fix it though.
+1
That is exactly the situation with my camera (at 1920x1080x25p)
Next will have canon drawing off. maybe it helps. Just have to make it.
Hi 1%,
Thanks for all your efforts and great work.
Last build is working ok for me with picture quality in sraw in ml menu, and canon menu in 640x480 25p pal.
I can do 768x432@35p, 960x544@24p, 1344x768@12p, 1664x944@8p all using fps override and global draw "auto off when recording" with canon lv preview
No skip frames, no magenta/pink frames.
Please, remember to set the canon as the default option for lv monitoring in raw menu, it is working flawless with the settings above.
Keep rocking!
Quote from: 1% on June 04, 2013, 08:29:05 AM
Next will have canon drawing off. maybe it helps. Just have to make it.
The latest build seem to have fixed the pink frames when the resolution was switched from 640x480 to 1920x1080 (on Canon's menu).
I thought I did. maybe it got reset. I'll apply commits and try to move the indicators around.
adding 23,976 to be one of the exact fps options inside the fps override feature was great idea.
what about to add:
5,994
7,992
11,988
14,985
29,97
35,964
47,952
59,94
these would be great also to use with raw video in 600d, because different resolutions needs different fps to keep under 21MB/s and using multiples of 23,976 is great for NTSC TV compatibility
I think in terms of stability and reliability you can consider your job done, of course improvements can always happens, but things are already working ok now. I cannot get the first shoot without magenta frames when canon menu is in 1920x1080, but who cares? we all know we need to set canon menu to 640 x 480 25p, picture quality to sraw and reboot camera, these settings solves everything, no skip frames, no magenta frames when keeping fps and resolution combo under 21MB/s.
Go on focusing the job on the overlay (indicators) position as you said, and if you can enable the fps list above in the exact fps override menu it will be great also.
thanks
This is just to celebrate my post number 100. Now I am a Member. Thanks!
Yesterday everything was fine.
Today shooting 960x544... lots of magenta frames... corrupted files... card error had to format card and lost lots of footage...
I'm sad... :(
And the auto exposure thing is still there... is there a way I can "lock" it?
Why I love shooting RAW video:
(http://imageshack.us/a/img196/5293/rawunprocessed.jpg)
(http://imageshack.us/a/img689/5250/rawprocessed.jpg)
With this new build I am shooting continuous 960x544 with zero magenta frames. The videos even seem more smooth and look amazing after processing through AE. Thanks for all the hard work you are putting in on all of this. I know there is the 21mb hardware limitations and all but things seem to be getting better with every build.
*edit- just wanted to add that my speed stays steady between 21.5-21.8 on 960x544
Does tethered shooting bypass the 21mb/s limitation?
Or are the transfer rates too slow?
inside the fps override function, there are some sub-menus (low light, exact fps, ...) maybe would be good idea to put these new fps inside a new category: "ntsc fps". I calculated them to be multiples and submultiples of 23,976 and 29,97, (values below can be turned into these by multiply by an interger, good to fps conversion) (values above divide by 2 or 1,5 good for slow motion)
0,999
1,998
2,997
3,996
4,995
5,994
7,992
11,988
14,985
23,976
29,97
35,964
44,955
47,952
59,94
You can make all of those already with the timers... ever find g3gg0s timing calculator?
Honestly I see no diff between 23.976 and 24... its still seems like 24 individual frames. I thought it would give me more shutter range but on 6D it didn't.
Quotecard error had to format card and lost lots of footage...
6D ate a card... I had to RMA it. I think the SD memory cells only have a certain amount of writes. Its being turned up to 11. 600D actually haven't had these issues but I have all UHS cards. Will see if it pops up.
AE is alredy off at record, something else must be changing expo. Have to find out what. ACR or camera.
ok, maybe these ntsc fps are not so useful considering we can shoot 24p and do interpret footage in post to set the 23,976p frame rate... the same for the other values...
so keep going on improving the overlays and solving the spanning problem fot fat32 cards... (fat32 cards are very useful to use in different cameras, like GH2 and 600D, so a good spanning in raw recording is welcome)
thanks
I was wondering can you change the frame rate to 23.976 or does it only do 30? And if you can shoot 24fps then where do I change it? Thanks...
FPS override can do whatever FPS you want, up to you to remember it tho.
Didn't notice diff between 24/23.976 at either interpreted 24 or 23.976.
Does it not span tho? Its supposed to. Just get annoying chunks.
Quote from: 1% on June 05, 2013, 03:53:54 PM
AE is alredy off at record, something else must be changing expo. Have to find out what. ACR or camera.
Yes I can confirm the exposure shifting is an ACR issue. The recording is ok.
Still have to find a solution... ;)
Recorded quite a few shots at 23.976 fps ovrrride, the sequences lined up with external audio perfectly. Still got magenta frames but it was because I had forgotten to disable histogram before recording. Rookie mistake ::)
Quote from: gebo on June 05, 2013, 08:10:43 PM
Yes I can confirm the exposure shifting is an ACR issue. The recording is ok.
Still have to find a solution... ;)
I've found that if you use the "auto" selection in ACR, it makes the funny exposure shifts. When I have a difficult shot, I open it through bridge first, then ACR and pick the frame I want the exposure a specific way on, and then synchronize the rest.
Through After Effects, it makes it difficult because (unless someone knows otherwise) I can only see the first frame of the clip. Also, by using Bridge, if you have the "carryover" frame from the previous clip, it makes it easy to delete it.
Also, commit to a white balance. If you use auto, it really goofs things up.
shot this yesterday. Though there is moire and some aliasing I can live with it. Did some minor tweaking in ARC but otherwise untouched. Getting great results in 720 mode at 1408x352. scales to 1280x536 just fine. My favorite aspect ratio anyway, so I'm geeked. Just random shots highlighting the dynamic range.
P.S. No magenta and a few shots over 1700 frames in length. Perfect for narrative shooting. Going to run a continuous shot today to see how it holds up over time, but I'm thinking I found my "sweet spot" for my needs.
6/5/13 update. shot several more shots... (2 over 3 minutes in length) only one corrupt frame, but was only the last frame, on only one of the shots. Completely usable now. I'm beside myself with glee. This is the most amazing thing since ML released it's first stable release. Absolutely amazing. Thanks 1% and anyone else for putting so much hard work into this. I'm hoping Canon, if anything, adopts this as a factory option, and compensates your work accordingly.
I will be watching for updates, as they seem to get better with each release. Now I just need a few more 16GB cards and a little more patience and planning while shooting. I was planning on getting the BM Cine 4k cam, but now, I'm going to get another T3i, and rent the other if I need it. going to shoot some more, and pull a favor in from a friend, and get some projected at the local theater to see what it looks like on the big screen. Their Christie system is amazing, and is rather easy to deal with, so when I get this done, I will let you all know how it turns out.
Excuse me for asking again, but right now i can't test it myself. So my question is, is it possible to shoot at least 6-7 seconds 1280 x 720 24fps?
I wish.
mov ind build feedback:
first a question: why changing the default aspect ratio to 2:1? it was great with 16:9 being the default.
globaw draw on / off was a good add
removing the black side bars from the lv in 640x480 mode was great
overlay indicators position improved, but needs a little tweaking to be better: move them more to top and more to bottom a little bit, see the photos showing 1344x768 and 1664x944. Move more to top will solve perfectly for 1344x768 and move more to bottom will solve bottom part for 1664x944. Maybe it will be impossible to solve the top part for 1664x944, but no problem at all.
1344x768 is the maximum resolution for 12fps and 1664x944 is the maximum resolution for 8fps, due to this I chose them.
(http://www.apefos.com/upload/rawoverlay8.jpg)
(http://www.apefos.com/upload/rawoverlay9.jpg)
This is why I'm saying its hard to move them..
Quotewhy changing the default aspect ratio to 2:1
This was an ooops. Added more aspects and forgot to change the default.
ok, so next build it will go back to 16:9
you did well in making one line at bottom with three information, file name, file size and datarate, you used ":" and "," to separate.
maybe you can try to make top information in just one line also, this way it will be ok for 1344x768 at 12fps
I also have a suggestion for you to enable 9:16 aspect ratio, and 544 width because it will be great for 3D stereoscopic work using two 600D fixed bottom to bottom together.
the red skip frame information can be inside the frame, in another line, because it is a warning, not a constant information, and I believe people will try to avoid skip frames using correct resolution/fps combos.
I think looks ok in most cases now.
Sorry, but I can't find Canon t3i firmware in folder downloaded from "http://nanomad.magiclantern.fm/nightly/".
Is this right folder?
(http://img23.imageshack.us/img23/2715/screenshot20130606at707.png)
And there is no "Modules" folder in "ML" folder.
^^^ You need the version found at the link in the first post of this thread
Quote from: N/A on June 06, 2013, 07:28:24 PM
^^^ You need the version found at the link in the first post of this thread
This link you meant?
http://www.magiclantern.fm/forum/index.php?topic=3072.0
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads
Yes, I have got this file. I'm asking about Magic Lantern Nightly Build. There is no "600D-102.fir" for t3i.
best and simple solution would be to put the top overlay in one line and a little more up.
and the bottom overlay a little more down.
if cannot put top overlay in one line, keep it two lines and put it more up and it will be fine.
Nebula, you get that with the v2.3 stable build...
Quote from: N/A on June 06, 2013, 08:25:44 PM
Nebula, you get that with the v2.3 stable build...
Thank you! It works. :)
Is there any hope for a 24 fps 1280x720 raw video on the 600D, 10 or 12 or 14 bit ?
Since there is no Progress in the 12bit 10bit topic, i would guess: NO
But since Upscaling still looks better dann h264 1080p - who cares? just get wider lenses or step away
I don't know, but to my eye, I haven't seen anything from the 600D upscaled that really looks better than 1080p/H.264, especially not worth the trouble that comes with the raw shooting. If we could get 1280x720@ 24fps raw, the yes, it would really be something, but shooting at 960x420 or something like that, I don't think it is worth the effort. Everything that I've seen, has terrible aliasing, and you can tell that it has been shot at a very low resolution, especially on the vertical axis.
Quote from: Critical Point on June 06, 2013, 11:16:57 PM
I don't know, but to my eye, I haven't seen anything from the 600D upscaled that really looks better than 1080p/H.264, especially not worth the trouble that comes with the raw shooting. If we could get 1280x720@ 24fps raw, the yes, it would really be something, but shooting at 960x420 or something like that, I don't think it is worth the effort. Everything that I've seen, has terrible aliasing, and you can tell that it has been shot at a very low resolution, especially on the vertical axis.
A few thoughts on this subject. Keep in mind that these lower tier cams come with lower tier glass as well. A stock 18-55 will display a somewhat negligible difference, but L glass or equivalent will capture color and sharpness much better for raw to work with.
I've shot numerous h264 videos with nice glass, max bitrate and great picture styles. I still prefer working with raw footage for the simple fact that the color is so much easier to denoise, correct and grade. If its a serious paid project then h264 for stability. Raw for everything else.
I don't know, having a webcam type of resolution on the vertical axis, no matter how good it can be for post grading, still gives a bad result at the end of the day, and for the effort that goes into shooting raw, I don't know if it really worth the effort. Maybe for the 600D, tweaking better the H.264 seems the better deal right now.
Between 1%'s slice 87 GOP 1 hack, and 3x h264 zoom recording, its pretty much maxed.
Im not sure if I'm doing something wrong but when RAW is enabled I am still getting a sort of lag on the viewfinder when panning. It just seems jumpy. When it is like this there are almost always magenta frames. I tried it having the Canon menu set to the 640x480 and it doesn't do this. Just when the Canon menu is set to 1080. I have everything turned off in ML. It doesn't seem to happen much on a fresh formatted card, but it seems hit and miss. Is anyone else having this issue? Also, is my understanding correct that there is no image difference between the having the setting on 1080 or 640 in the Canon menu?
Yeah 1080 & 640 is the same. What are your settings under raw video?
960x540
16:9
sound off
GD off
frame skipping off
framing Center
Preview Canon
Start delay 2 secs
ML settings are set for SRAW, everything and anything set to off. I have tried different combos with no luck. The lag is like the picture jumps to catch up with itself. Even on really slow pans this happens. This wasn't an issue before these last four builds or so. I will just start using the 640 mode in Canon menu.
Weird.. just panned around and no lag in either mode.. only lags on hacked w/preview or ml grayscale for me.
Shooting a shortfilm in RAW this week has been fantastic. Most of the shots do not need to be particularly long, so there isn't much worry about frame count and I've been shooting above 720p in 2.39:1 aspect ratio, which is perfect. RAW is definitely looking better than my H.264 shots which I've been using for longer shots. I'm actually preparing less for each shot because I don't need to worry about the exposure or HDR. RAW has made my film look like film, instead of DSLR video.
Quote from: N/A on June 06, 2013, 11:44:15 PM
A few thoughts on this subject. Keep in mind that these lower tier cams come with lower tier glass as well. A stock 18-55 will display a somewhat negligible difference, but L glass or equivalent will capture color and sharpness much better for raw to work with.
I've shot numerous h264 videos with nice glass, max bitrate and great picture styles. I still prefer working with raw footage for the simple fact that the color is so much easier to denoise, correct and grade. If its a serious paid project then h264 for stability. Raw for everything else.
The resolution is too small to upscale properly. Of course shooting RAW gives you more Post process power for Rich nice Color. But I'm still shooting H264 because it does look better in terms of Sharpness compared to the two. A lot of people think because it's RAW, you can do whatever you want to it. You can! But not upscale from 960x540 to 1920x1080p There's just not enough detail in that small 960x540 image even in RAW. Everyone is saying H264 upscales, well it does a hell of a better job than RAW apparently right now. The way the RAW footage is being upscaled just looks pixelated to me instead of being sharp or slightly blurry. If we got it to like 1600xXXX than it would upscale to 1080p nicely, but 960x540 just isn't going to work guys. It sounds like the Camera just can't handle it. Keep it up though. I see 1280x720p atleast coming hopefully. :)
Sharp enough or not, I still trade sharpness for dynamic range and the possibility to work on the footage the way you want:
Quote from: Kakuda on June 07, 2013, 08:58:06 AM
Sharp enough or not, I still trade sharpness for dynamic range and the possibility to work on the footage the way you want:
Fair enough, But i think sharpness and Resolution matters just as much. That's why you shoot raw, So you can see every little detail in someones eyeball. Its like people saying it doesn't matter what camera you have, As long as you capture the moment. That's True, But that moment would be even better if it was shot with lets say a 1DX vs a point and shoot. Meaning it looks great, but imagine Higher Quality.
about upscaling and aliasing, I found a solution to make it look better, from unacceptable to reasonable good.
please, see this topic, try it and let us know if it satisfies your needs.
http://www.magiclantern.fm/forum/index.php?topic=6248
I have to code fixed slice back in (its the easiest)... then when you use sraw should have a bigger H264 buffer.
They're both good. The raw upscales, the H264 is easier to keep on longer.
Hello! Just a quick question, 60D have a same max recording bitrate as 600D, why then on 60D is possible to rec at 720p 24fps but on 600d it's not?
60D has way more memory... nobody said you couldn't record 720P or 1080P or whatever at all.. just its not continuous.
No i don't need continuous i need just 6-7 seconds 720p 24fps footage.Is it possible with the current build?
Try it... see how much you get. It will depend on your card.
Using a Lexar Platinum II UHS-I card (not the fastest by any means), I can get continuous RAW video @ 24 fps with 1088x448 at 2.5:1 (2.46).
I'll be happy if the code guru's here manage to find a way to get 10bit HD output. Not sure how likely that is but that would still be fantastic output.
Quote from: DJHaze596 on June 07, 2013, 08:24:39 AM
The resolution is too small to upscale properly. Of course shooting RAW gives you more Post process power for Rich nice Color. But I'm still shooting H264 because it does look better in terms of Sharpness compared to the two. A lot of people think because it's RAW, you can do whatever you want to it. You can! But not upscale from 960x540 to 1920x1080p There's just not enough detail in that small 960x540 image even in RAW. Everyone is saying H264 upscales, well it does a hell of a better job than RAW apparently right now. The way the RAW footage is being upscaled just looks pixelated to me instead of being sharp or slightly blurry. If we got it to like 1600xXXX than it would upscale to 1080p nicely, but 960x540 just isn't going to work guys. It sounds like the Camera just can't handle it. Keep it up though. I see 1280x720p atleast coming hopefully. :)
Have a look-
http://www.magiclantern.fm/forum/index.php?topic=6268.0
*edit - I apologize, I found someone with the same issue on the second page of this thread. My bad for not reading through more thoroughly before posting.
I have a question a little off topic but still RAW related. I have been following this forum from day one and trying to learn as much as possible about the RAW capability. My question is related to a pixel that I have recently noticed in my videos that kind of stands out. I had never noticed this before until last night after recording 4.5gb of continuous raw @ 960x544 on my 600d. The camera got very hot so I stopped it. I processed the video and noticed this small blue pixel standing out. I freaked out and thought that the camera getting hot may have had something to do with this. So after doing a lot of side by side tests and reading up on hot vs dead pixels I have noticed that I can't see this pixel in regular recording H.264. In RAW pictures I have taken I cannot see this pixel either. I tried the body cap on and manual sensor cleaning option for a couple of minutes multiple times and the pixel is no longer blue but kind of transparent to darkish colored. I can only see this pixel in RAW recorded video. My question is is this due to RAW being so detailed that it is picking this up possibly? It bugs me nonetheless and not sure if I should get it serviced, which I've heard is expensive. Sorry for the wall of text, I can post pictures if anyone is interested in seeing.
Looks like this thread has gone to sleep.
Perhaps a good time to request some more aspects ratios between 1:1 and 4:3 ?
Please consider 9:8 and 6:5
My request is that the camera remembers the last video settings (aspect ratio & resolution) used every time I switch it on/off.
Thank you!!
Its not dead, I had to fix 600D.. was crashing from a commit.
Quote from: 1% on June 09, 2013, 06:04:04 PM
Its not dead, I had to fix 600D.. was crashing from a commit.
Thank you very much!! You're doing such an amazing work!!
Since even upscaling the 960 X 544 videos to 1920 X 1080 doesn't improve the image enough to make it look equal or better than the default H.264 videos, I played around with Avisynth a bit to create a script that should help us to achieve higher quality. It reads TIFF images, combines them into a video and doubles this video's framerate. How does this help? I allows us to record at 12 frames per second with higher resolutions and make it look fluid again in post. I tried it, and it works quite well.
At 12 frames per second we can record 1344 X 768 (16:9) or 1536 X 656 (21:9 | 2.35:1) ... Here's the link for the script:
- Magic Lantern forum: Avisynth script for doubling the framerate | Twixtor alternative (http://www.magiclantern.fm/forum/index.php?topic=6316.new#new)
Of course, if you own Twixtor, you can use that instead. But if you don't have Twixtor, I think that you should try this script.
Also, if you have an idea how this script can be improved, it would be great if you post it.
And @ 1%: Thanks for keeping on the good work. You are great :D
Especially for scenes without much motion the 600D can deliver some really nice videos with your amazing firmware add-on and my not so amazing script ;D
Has anyone tried upscaling 5x zoom footage? Im thinking it could come in handy for sports photographers, wildlife, etc. if the image can be manipulated any.
Theoretically the 5x has slightly better quality.. same with crop mode... probably less aliasing from resizing.
12fps isn't that bad I guess, you can probably do more than that. This camera is pushed to the edge though, almost using all memory/maximum write/etc.
"Still Working" is a great build
some questions:
why did you re-enable the black side bars in the 640x480 LV, did you find it allows better performance?
what does the new "idle" overlay information meas? sometimes it shows 2%, sometimes it shows 49ms...
feedbacks:
enabling a time count while shooting was great idea
the overlays position are ok now for resolutions up to 1344x768 (16:9)
the bottom overlay half line more to down will be even better for 1344x768 and for 1664x944
It depends on the timing for the black bars and when the screen is cleared. I'll have to mess with it so it works... idle I think is idle CPU time.. which we probably have very little.
The only real aspect ratio that I think is still missing is 2.40:1 (Bluray 1920x800 standard), cause 2.39 doesn't divide evenly.
P.S. But assuming that resolutions are equal to multiples of 32, it makes no difference between 2.39/2.40 anyway...
I think this 12-18 fps limitation could led to some new creative use of the camera!
Yeah I'm thinking of shooting some music video scenes at 12 fps for a stutter type effect
Elapsed time, thanks! And frame count updating once per second is much less distracting. This is the most intuitive and stable build yet. Combine this with RawMagic and this is a damn nice workflow. Now if we can get some logs/metadata, I'd be in heaven. Great work man.
I still can't figure out why sometimes it allocates 31M+30M and not 31M+30M+25M. Why is that happening ?
Check out my last video test with the "MovedInd" version: http://www.magiclantern.fm/forum/index.php?topic=6353.msg49379#msg49379
Still a lot to learn, but the camera performed very well, loosing only 5 or 10 frames of 9 minutes of video shot in total, and stopping the recording 2 or 3 times.
I have a question. If I understand things right, the 600D feeds a low resolution image to the H.264 codec, then it is upscaled to 1080p resolution, so basically, this means that the 1080p H.264 it's NOT a real Full HD resolution, isn't it ? Well, in this case, what if we match with RAW the same original resolution that H.264 gets before rescales the video ? In that case, doesn't it mean, that we have obtained the H.264 1080p, only this time in RAW ? We just need to upscale the raw video to 1080p just like the H.264 does. Correct me if I'm wrong on this please.
Quote from: Critical Point on June 11, 2013, 07:44:45 PM
I have a question. If I understand things right, the 600D feeds a low resolution image to the H.264 codec, then it is upscaled to 1080p resolution, so basically, this means that the 1080p H.264 it's NOT a real Full HD resolution, isn't it ? Well, in this case, what if we match with RAW the same original resolution that H.264 gets before rescales the video ? In that case, doesn't it mean, that we have obtained the 1080p ? We just need to upscale the raw video to 1080p just like the H.264 does. Correct me if I'm wrong on this please.
That resolution is 1732 X 974, just slightly smaller than 1080p.
Oh, I see. And for the 720p ?
Our RAW videos are nothing but the images that you see in LiveView. Well, our RAW videos are just a tiny crop of that images ;D
That's the same image which gets feeded into the H.264 encoder. In 1080 & 640 mode the LiveView resolution is 1728 X 1152 and in 720 mode it's 1728 X 672 (The same as in 1080 mode, but with some vertical lines left out. That's why it appears streched).
But yes, in both modes the H.264 encoder streches, crops and resizes the image until it becomes a peace of muddy, pseudo 1080 shit.
(Okay, it doesn't look that bad. But since I saw what the 5D Mark III and even the 50D can do, I'm a little bit more selective than usual ;))
Damn. I wish Canon would have given us 1728 X 1152 H.264, so it wouldn't look so muddy or simply a better SD controler (Or CF card slot) ...
And can't we just set global draw:off, and then record to an external source through the HDMI port ?
What's impossible:
- Get 2K, 4K resolutions
- Get any kind of lossless compression
- Get any kind of lossy compression
- Send the RAW videos out to the HDMI port
- Increase the write speed of the SD-Controller
You see: the 600D is just no good camera for raw video. Film H.264 or get a better one :D
Just a thought, but has anyone really checked if the HDMI offers a better quality than the video that is present on the SD card ? Maybe the HDMI goes through less compression, or through a less number of cycles regarding compression.
From what I understand, the raw video data goes first in the jpeg algorithm, then it is passed through the H.264 chip, and maybe on the HDMI, we get only the jpeg compression, who knows ?
JPEG compression? The H.264 videos have nothing to do with JPEG compression ;)
The 5D Mark III has a clean HDMI output. I suggest to watch some comparisons between the default H.264 video and the "uncompressed" HDMI output yourself. You'll see: There's almost no difference. The uncompressed videos have a very little bit more detail and no motion artifacts. But they are as muddy as the default H.264 videos and they have the same tiny dynamic range and the same bad colors. If the Magic Lantern developers would give us the 422 YUV videos back, we could get these results even withou buying an expensive HDMI recorder.
The Canon EOS 600D doesn't have clean HDMI out anyway ...
Like I said: H.264 is the only choice at the moment. Mabye we'll get some kind of yuv_rec some day. I'm really hoping that the EOS 70D will have an CF card slot ... And the 5D Mark III's anti aliasing. That would be awesome.
Sure, the sd speed is crappy, but between stock & 3x zoom h264 and pic styles, audio features, standard def raw video, full photography capabilities, the whole selection of Canon lenses (catches breath) AND the massive amount of available accessories, you can't find a better all-around camera for what 600D's cost now.
If the .h264 is good enough for broadcast television and feature films**, then this, even though lower resolution, opens up a number of possibilities. There are "optical" ways to limit aliasing and and other issues, plus using higher resolution raw for shorter shots (planning) then this is a viable tool, even on the 600D/T3i. I've gotten wonderful results at higher resolutions in 720 mode, even with the line skipping, and using 40+ year old lenses minimizes the aliasing without additional filters. As with all tools, there is a time and place to use them. Forget about looking at 100% crops, look at the overall aesthetic of what you are shooting. Granted, the 600D/T3i is not as robust as the 7D or especially the 5DII or III, but for my purposes, which are primarily DVD, Standard Def Television, or web, this raw mode is a godsend. I will be using it for very specific purposes, such as greenscreen (where you can never have too much data, and shots that require high latitude. but for general shooting, I will likely stay with the .h264. Granted, the 600D is no 5D, but is close to the 7D in many ways with the exception of dual processors. Same line skipping, same codec, very similar latitude, and if you use high quality glass I would hazard a guess anyone would be hard pressed to tell the difference. I routinely crank up the bitrate (thanks ML team) for certain projects, and raw is just another tool. Remember, a few short years ago, many of us were either stuck with DV or HDV for professional work. Though I've used a Cine-Alta on a few occasions, there are far smaller, and more manageable cameras that yield similar if not superior quality these days. Just trying to keep perspective here.
**Canon DSLR's have been used on:
House - 5D Mark II
24 - 5D Mark II
127 Hours - Canon 1D Mark IV, Canon 5D Mark II, Canon 7D
Act of Valor - Canon 5D Mark II, Canon 7D, & Canon 1D Mark IV
The Avengers - Canon 5D Mark II & Canon 7D
Black Swan - Canon 7D & Canon 5D Mark II
Captain America - Canon 5D Mark II
Iron Man 2 - Canon 5D Mark II
Like Crazy - Canon 7D
The Pirates! Band of Misfits - Canon 5D Mark II
Red State - Canon 7D
Red Tails - Canon 1D Mark IV, Canon 5D Mark II, & Canon 7D
etc...
Quote from: robrock_68 on June 12, 2013, 12:52:09 PM
If the .h264 is good enough for broadcast television and feature films**, then this, even though lower resolution, opens up a number of possibilities.
Absolutely agree.
We tend to see every difference but the average viewer does not. and if he does, then the movie can be already tagged as "bad" because it draws the viewer attention from the MOVIE. I have seen not so long ago a real movie (in the theaters) shot entirely on 7D. I haven't been able to differentiate it from a "real" movie (and believe me I tried). it was great, because I could focus on the movie and not think about aesthetics.
OTOH, the whole first half movie of "Skyfall" (shot with an Alexa), I couldn't stop thinking how old and crumpled Judi Dench ("M") looked. it was overwhelmingly and painfully sharp (for my taste, at least).
Quote from: robrock_68 on June 12, 2013, 12:52:09 PM
There are "optical" ways to limit aliasing and and other issues, plus using higher resolution raw for shorter shots (planning) then this is a viable tool, even on the 600D/T3i. I've gotten wonderful results at higher resolutions in 720 mode, even with the line skipping, and using 40+ year old lenses minimizes the aliasing without additional filters.
Most odds are that the lens is a "natural limiter" on its own (ie. not sharp as modern lenses, and therefore, cannot resolve enough and relay information to make aliasing apparent...)
Quote from: robrock_68 on June 12, 2013, 12:52:09 PM
As with all tools, there is a time and place to use them. Forget about looking at 100% crops, look at the overall aesthetic of what you are shooting....
I wholeheartedly agree.
BUT
Quote from: robrock_68 on June 12, 2013, 12:52:09 PM
I will be using it for very specific purposes, such as greenscreen (where you can never have too much data, and shots that require high latitude. but for general shooting, I will likely stay with the .h264.
From what I have tested, RAW and H264 does not intercut very well on the 600D. the RAW "pops" (resolution wise they are quite the same after you upscale a continuous shot which is in my case 1024x432). color wise, I've tried to quick match them and its not an easy task.
Yes, I agree, the 600D/T3i is a good little camera, especially if we consider that only the 600D and the 5D MK III, can get rid of all the aliasing problems, from all the affordable Canon DSLR lineup. That is a big deal, and it seams few realize this fully. Because of this single reason, in my opinion, 600D is a better camera for video than 60D/7D.
The other cameras should be moire free in 1:1 zoom but you don't get the full frame nor can you do H264 with that.
Also 600D was made when UHS was barely coming out.
On a 600D, you activate the 3x zoom feature, take a few steps back, and done, no more aliasing and moire problems. Not even the mighty 5D MK II can't do that. A 600D is a must have camera if you are in the video business, if you are interested in cameras from Canon that is.
Or you strap a 50mm f/1.8 lens, activate the 3x zoom feature, and presto, you now have a 150mm lens, with no moire and aliasing, and with god night capabilities. On what other camera can I do this ? Can even the 5D MK II do this ? NOT !
The 600D is a keeper, nobody should give up on this little camera, even if he or she buys a much more expensive camera from Canon.
This 1:1 crop video mode in 1080p, was a slip up from Canon, they have now quickly taken it out from the newer cameras, T4i, T5i, none of them have this feature anymore, and probably we will never see it again to soon, because it really hurts their zoom lens business. Just imagine how much money they're loosing if I want to film with a 800mm lens, and instead of buying from Canon a 3000$ lens, I just put on the 600D a cheap 300$ 250mm lens, and activate the 3x zoom feature. A low cost segment, hurts a high dollar segment from the Canon business, so, that is probably why they have taken it out so quickly, and it was not present even on the MK III. The fact that the 3x zoom feature was not present on MK III, says it all.
Probably the guy who put the 3x zoom feature on the 600D was fired by Canon. :)
If you want to film with a 3X cropfactor, just buy a Blackmagic Pocket Cinema Camera or any Canon DSLR with an CF-Card slot.
The 50D, 5D Mark II and 5D Mark III all can film in 3X crop mode too since Magic Lantern's RAW video also works in 3X crop mode (The focus zoom). So you can get 1920 X 832 14-bit RAW (512 Megabit/s) videos without moiré with all of them. With the 600D ... Nah, only fake 1920 X 1080 8-bit 4:2:0 H.264 (45 Megabit/s) ;)
And of course the 650D and 700D have it too, but in slightly lower resolutions = even more crop.
Still, Canon won't loose any money because of this. Seriously, Canon's DSLR are mainly build for photography. And the digital zoom doesn't work for photografy. I doubt that somebody got fired because he implemented the 3X zoom on the 600D.
I'm not saying that the 600D is a bad camera. I own one and I love it! It is really great. But the RAW video on this camera is just for special situations (Still nice to have it! I really like it :D) and no replacement for H.264 like on the 5D Mark III or 50D. And the 600D is by far not the best affordable video camera.
(If I "sound" a little bit offensive, I apollogize. I'm just mad because the only thing that's keeping the 600D from really beeing the most amazing videocamera < 1000 € is the slow SD-Controller. Canon, why? ... We could have 1732 X 1154 14-bit RAW video and the benefits like audio and flipscreen ... :()
Yeah, sure, a great high-resolution flip-screen is the thing missing in 50D.
Yes, well what can I say ? I too am looking forward for the release of the black magic pocket cinema, that sure as hell it's going to put a dent in the Canon DSLR lineup for filming. I just want to see first some more footage from that camera.
Anyway, about the 600D, yes, I agree, you can shoot raw with 3x digital zoom on other Canon cameras, but you can't shoot H.264, so it's either the 600D, or the MK III, so in this regard, the 600D is king of the hill in this price range. And oho, trust me, since the 3x digital zoom doesn't come by default not even with the MK III, trust me on this one, it is a big deal. Just imagine in the paparazzi sector, how much money it's spend on high powered zoom lenses, not only for taking pictures, but for video also. Don't underestimate the importance of that 3x zoom, it is not by any mistake they have left it out in the newer cameras.
Need to borrow my buddy's Tokina 11-16 and shoot a few 3x zoom clips and compare it with stock footage, isn't 3x zoom upscaled less as well?
Anyway, getting off topic. The smaller file sizes we get with raw is extremely convenient, we can do close to half an hour of raw footage with a 32 GB. Uprez it to 720p, put it on Youtube/vimeo, less upload time/faster buffering. And besides, if we're shooting something that absolutely NEEDS 1080p, we shouldn't be shooting with a "Rebel" anyway lol.
Think I'll do a 1080p downrez, raw uprez test to 720p and compare.
I don't know if the 3x zoom is upscaled, but what i know from experience, is that it gets rid off all the aliasing and moire that you normally get from the sensor line skipping, and the quality of the videos, is better in this way. For RAW video, it sure does a good thing, because RAW videos tend to suffer from this aliasing issue because of the low res.
I think that shooting RAW with 3x digital zoom at 960X540, and then rescale it to 720p, will give you the best video quality the 600D can produce right now, and because the image is so clean, and with virtually no aliasing, you can even upscale it to 1080p and get away with it. But first try to upscale it to 720p, that will probably be the best quality.
Is there a way to configure Magic Lantern to start with the raw record mode enabled with frame skipping, in the same way that FPS override is enabled? It is so difficult renegotiating those menus and buttons in the dark every time I start the camera.
Also, is the 600D really 4:4:4 14 bit? I have never used that before and was surprised that the performance in low light was worse than an old point and shoot from 2007. I filmed it a little underexposed thinking I could fix in post just like a raw photo. Nope.
I am thinking about selling this 600D and trying to find a cheap 50D if it would make a difference.
I think we're mixing things here:
5x/10x - 1:1 zoom - basically as much as the camera can sample in 1:1 - all canons have this
3X crop - similar to zoom but scaled/skipped to fit the whole image in one "window" - 600D/1Dc/1DX
raw_rec crop... just a random rectangle cut of whatever mode you're in.
This has 0 impact on canon lens sales... you'll only get that 800mm effect in video/raw mode... and just think how far the real deal will reach.
It does have impact on video cameras though... they want you to just have that muddy crap video and upgrade.
Otherwise why not 100MB/s H264 all the time.. and why the joke all-I (frames too big) mode with crippled IPB (frames too small) on digicV.
P/S.. 50D has same CPU/pink frame issues as 600D.. .from how long I could use it before it died... I got 1/2 way through beep and got display filters working then poof (AA not working)... maybe it will shine with native 24p or something... 600D with CF would eat it up.
So the only option would be some crazy attempt to bypass the sd card controller into a ssd or similar? Even if the hardware worked, would still need additional coding to be compatible, I'm assuming?
600D, the little engine that could ;D
Does the seperate WAV in 600D work ?
I've searched here for "600D RAW SOUND" and the results were of no good to me...
Upon trying to engage seperate WAV in 600D (with RAW engaged) - the camera simply shuts itself. am I the only one with this ?....
Quote from: Critical Point on June 12, 2013, 04:08:23 PM
Probably the guy who put the 3x zoom feature on the 600D was fired by Canon. :)
Ha! ;D Don't laugh, it's probably true. But just when I think the 600d had reach the limit, there come 3x crop factor. Finally, I have the chance to see what that girl is doing in that far away window.
Lol.. 5x raw you'll really see what they're doing..
I know why wav doesn't work... same reason bolt rec "doesn't work"... were so out of memory its not funny... wav can use shoot_malloc... but then we take from H264 or Raw... and we don't have nice resource manager area like 60D to put the bin there and free things up.
Quote from: 1% on June 13, 2013, 01:28:17 AM
I know why wav doesn't work... same reason bolt rec "doesn't work"... were so out of memory its not funny... wav can use shoot_malloc... but then we take from H264 or Raw... and we don't have nice resource manager area like 60D to put the bin there and free things up.
So what are our options regarding RAW shooting + sound recording ?
Oh, BTW... Thanks, man ! for everything you do ! :)
Which options? We ran out of memory and we have extremly slow write speeds. There's probably no way to fix that ...
Quote from: AriLG on June 13, 2013, 09:55:12 AM
So what are our options regarding RAW shooting + sound recording ?
Buy a voice-recorder. Zoom or Tascam. 100-200$ on amazon.
Btw, people, please understand:
Say you want to shot 50mm (on 5D fullframe, normal lens, real 50mm, pretty standard and close to human fov)
To get the same FOV, you will need a 17mm lens when shooting RAW 960x540 16:9 on 600D (because of 2.88x crop factor (1.8*1.6))
And if you also use 3x crop, or zoom, or something - you'll need a 8mm fisheye, or even wider to get an ordinary normal 50mm field of view.
So now all talks about best quality 960x540 stretched to 1080p on youtube fit more to shooting the moon in the sky, birds in the forest and girl in the window next block - very special purpose, not for everyday shooting.
With all these crops, zooms, cropped raw little windows - you're getting a really-really-really long lens which isn't quite suitable for ordinary shooting (especially interior shooting). And if you cut it to cinemascope 2.39:1 - then you get even less space and less fov.
If you like to shoot long-lenses - then 600D is for you. If you're more to shooting wide - then nope.
Although, I can get a full 1728x960 (stretched from 1728x576 sqeeze in 720p mode) at 12FPS continuous recording (19.9MB/s stream) - and that's good for slow-movement shooting.
And btw, if 650D has twice the bandwidth - then we can do 1728x960 stretched in 24FPS, correct? That would be best for me.
Quote from: CFP on June 13, 2013, 09:59:13 AM
Which options? We ran out of memory and we have extremly slow write speeds. There's probably no way to fix that ...
When I say "options" I'm not talking programming wise, dear friend :)
I think I understood that we have reached a bricked wall regarding the limitations of the HW...
Quote from: vicnaum on June 13, 2013, 10:04:28 AM
Buy a voice-recorder. Zoom or Tascam. 100-200$ on amazon.
I have one. Zoom H2N. how do I sync ?
Quote from: AriLG on June 13, 2013, 10:14:41 AM
I have one. Zoom H2N. how do I sync ?
How the big guys do - with a clap.
All this sounds pretty defeatist to me :)
If you want full frame using regular lenses this workflow is for you
1 Shoot 960 x 960 with a 2x scope @ 12p
2 In post stretch to 1920 x 960 and Twixtor to 24p (perfectly suitable for narrative)
The 960 vertical is the same picture height as Canons 1080, also its slightly wider when stretched
PROS: your cards dont fill up so quick and cheaper cards , CinemaScope aesthetic, High vertical aquisition means better sharpness
CONS: you need a 2x scope, Twixtor & some more rendering time
If the devs can see their way to providing 1088 x 960 then true Cinemascope aspect is doable, on both 550D and 600D
Quote from: vicnaum on June 13, 2013, 10:12:37 AM
Btw, people, please understand:
Say you want to shot 50mm (on 5D fullframe, normal lens, real 50mm, pretty standard and close to human fov)
To get the same FOV, you will need a 17mm lens when shooting RAW 960x540 16:9 on 600D (because of 2.88x crop factor (1.8*1.6))
And if you also use 3x crop, or zoom, or something - you'll need a 8mm fisheye, or even wider to get an ordinary normal 50mm field of view.
So now all talks about best quality 960x540 stretched to 1080p on youtube fit more to shooting the moon in the sky, birds in the forest and girl in the window next block - very special purpose, not for everyday shooting.
With all these crops, zooms, cropped raw little windows - you're getting a really-really-really long lens which isn't quite suitable for ordinary shooting (especially interior shooting). And if you cut it to cinemascope 2.39:1 - then you get even less space and less fov.
If you like to shoot long-lenses - then 600D is for you. If you're more to shooting wide - then nope.
Although, I can get a full 1728x960 (stretched from 1728x576 sqeeze in 720p mode) at 12FPS continuous recording (19.9MB/s stream) - and that's good for slow-movement shooting.
And btw, if 650D has twice the bandwidth - then we can do 1728x960 stretched in 24FPS, correct? That would be best for me.
Yeah, anamorph is great, sure.
But to me - it's unreal. Firstly the price, then focusing trouble (two focuses instead of one) so need an assistant (or two), and lens limitations/mounting trouble.
1088x960 is probably too big to record at full speed. 650D should be close to 6D so 720P works, etc. Just 650D has a lot of other "catches".
Quote from: 1% on June 13, 2013, 03:35:02 PM
1088x960 is probably too big to record at full speed. 650D should be close to 6D so 720P works, etc. Just 650D has a lot of other "catches".
Agreed, if by full speed you mean 24p
But at 12p is within the 21MB bandwidth
There are two types of horse race:
One is on the flats
The other is over fences
In other words "Horses for Courses" :)
In both cases you have to be in it to win it
Quote from: vicnaum on June 13, 2013, 03:33:52 PM
Yeah, anamorph is great, sure.
But to me - it's unreal. Firstly the price, then focusing trouble (two focuses instead of one) so need an assistant (or two), and lens limitations/mounting trouble.
Ok starting to figure out this workflow. Boris Color and Tone in Premiere works really well for grading. Even with the low bandwidth this video in 16bit PSD from Lightroom is stunning when compared with AVCHD 4:2:0 and possibly worth the investment in a superwide/fisheye/anamorph.
I almost feel like a real film maker.
Regarding crop factor, for tight shots it can be a pain. But for general shoots, and shooting with two or more cameras, its actually somewhat convenient to have some distance between camera and subject. So really only need two lenses now as videographers: a wide angle and a 35mm. 5x for either is more than enough zoom for most cases. If shooting for scope look, just use a 1088x480 rez.
Dolly mode is really handy as well. I wish I would've had that feature before raw.
Hi guys. I have been playing with the raw function since it became available. I found it very interesting. So this time I decided to play with the frame rate, some of you already know it is a problem to shot moving objects a 12fps. But if you need landscape shots, work for real estate, do music video etc. shooting at 1536x656 is a very nice option as it has been mentioned before here. But I don't like to sit with my arms crossed doing nothing, so I did another test, and this time the camera behaved much better than I expected. See footage with your own eyes.
I got some pink frames in 3 or 4 shots, but it was very decent. The only test I haven't tried is moire and aliasing. I'll get some test charts, still I think the camera reached the limit of what it can do, but I'm happy.
Damn ! Imagine what would have meant to have a faster SD controller and shoot 1080p with the 600D. F*** you Canon !
Anyway, you should try to make 24 fps out of 12 fps with twixtor, see what that will produce.
I never understand this attitude towards Canon ??? The SD slot was perfectly OK for recording until raw video (not a Canon feature) was made possible. Don't forget, the 600d is a consumer DSLR.
Yes, I know, I know, 600D is a good little camera for H.264, but damn, look at that RAW quality out of a 600D !
Quote from: Critical Point on June 14, 2013, 10:58:48 AM
Yes, I know, I know, 600D is a good little camera for H.264, but damn, look at that RAW quality !
You have a 600d for decent H.264 and ability to use Picture Styles to get the most from the camera's DR and a GH2 for resolution. Get a cheap 50d for raw video ;)
We're at the budget end of things on these cameras and non of them will be all things to all people but they can all do amazing things when you think about it.
I've sold 600D for about 500USD and got 50D for 300USD and never regret about this :)
For RAW Video the 5DIII is the right camera, and the price is a joke for this quality. I have the 600D and i'm happy with the 20 MB limit, i don't need 10 x 32 GB SD Cards to get the shots ;)
Quote from: Critical Point on June 14, 2013, 10:58:48 AM
Yes, I know, I know, 600D is a good little camera for H.264, but damn, look at that RAW quality out of a 600D !
Considering the price I (we) paid for the camera, the amount of data generated by the RAW output (not as skull smashing as the 5D Mk III), the quality achieved thus far (first I thought the lower resolution was simply "not there". after comparing countless times RAW vs H264
with my own camera - I do not not think so anymore) - I (WE) should be grateful for what we have. it's nice to have "more" but think of what has been achieved up till now....
One thing, though : workflow is a pain :-\
If I were to shoot full day of something meaningful, as of now I have to devote at least ANOTHER working day just to prepare the material for editing.
(OTOH, coming to think about it - and Philip Bloom talked about it at great length - RAW is pain, PERIOD)
Quote from: Andy600 on June 14, 2013, 11:04:14 AM
Get a cheap 50d for raw video ;)
Neah, for raw I'll buy myself a nice black magic pocket cinema.
But just wondering, will it also be a pain in the but with the b.m.p.c. post work as is with raw on canon ?
Quote from: Critical Point on June 14, 2013, 11:48:01 AM
Neah, for raw I'll buy myself a nice black magic pocket cinema.
But just wondering, will it also be a pain in the but with the b.m.p.c. post work as is with raw on canon ?
The BM Pocket CC doesn't shoot raw video yet and it will not ship with raw recording features afaik. It's a concept and you don't know what additional equipment you may actually need ;) ....but yes, I still want one too :)
The only worry I have, is that the demand will be so high, that they won't be capable of meeting the market demand and the price will go up immediately after release.
Quote from: Andy600 on June 14, 2013, 11:51:15 AM
The BM Pocket CC doesn't shoot raw video yet and it will not ship with raw recording features afaik. It's a concept and you don't know what additional equipment you may actually need ;) ....but yes, I still want one too :)
Where are you seeing this information? Everything I've seen on the camera, including sample footage from the "previews" sent to certain people, show raw recording is functioning on these cameras, and will ship with the feature fully functional.
Quote from: robrock_68 on June 14, 2013, 12:45:00 PM
Where are you seeing this information? Everything I've seen on the camera, including sample footage from the "previews" sent to certain people, show raw recording is functioning on these cameras, and will ship with the feature fully functional.
Where is this raw footage? I've only seen Prores and I haven't seen any official BM announcements about final release specs
Quote from: Andy600 on June 14, 2013, 01:06:12 PM
I haven't seen any official BM announcements about final release specs
Did you see this: Blackmagic Pocket Cinema Camera | Technical Specifications (http://www.blackmagicdesign.com/de/products/blackmagicpocketcinemacamera/techspecs)? Is this not official? :o
But I totally agree with you. The 600D is a great camera and we should be happy with what we have. Of corse, the H.264 video looks way worse than it could if Canon wouldn't want us to have that poor image quality. But it still looks better than most of the camcorders in this price range.
But I'm also thinking that Canon shouldn't waste so much potential of their DSLRs. It makes me sad ...
Look at the Blackmagic Pocket Cinema Camera: It isn't impossible to create an amazing camera with high dynamic range, professional video formats and interchangeable lenses for under 1000 €. And we also know that the Canon DSLR
could have all these features and more if Canon would allow us to have them. Actually the Canon DSLR could be even better than the Blackmagic cameras since they have much bigger sensors.
Now where Magic Lantern has unlocked all these stunning features on the Canon DSLR, they are just one step away from being the best cameras in the affordable film industrie. And it
is sad that Canon wastes this potential completely :(
Quote from: Andy600 on June 14, 2013, 01:06:12 PM
Where is this raw footage? I've only seen Prores and I haven't seen any official BM announcements about final release specs
Final release specs are on the site, and the camera is still scheduled for production release in late July. From what I can gleen, the firmware is still a work in progress, so I guess they better get their butts in gear for the release dates. All point to being able to shoot Cinema DNG (Raw) on high speed SD cards, which is the whole point of the camera and pricepoint. If they don't deliver, then, well, too bad for them. I did find that there are a few "DNG" sequences out there, but they are only available to view as compressed streaming files, and until the firmware is finalized, you won't see camera files released to the public
The pocket cine looks amazing for the price. And for the same price, one could buy two 600D's or 50D's. Either way, we are the ones who benefit from these types of innovations.
I just wonder how sturdy the pocket cine will be. I've put my poor 600D through hell and it still runs like a champ. Not to mention, I imagine with it being so small, it could get lost or stolen quite easily.
I think most people will agree that finding out about the limit on the sd card controller really hurts when you purchased a uhs-1 card. I knew I wouldn't benefit from uhs, but I had no idea how little speed I was getting from those cards.
:-[
Well, no matter how good the pocket cinema will turn out to be, I ain't selling my 600D. I am going to buy a pocket cinema camera, but I'm also going to keep the 600D.
@CFP yes, I've seen those specs and they do include compressed CDNG but weirdly it omits the data rate for CDNG, only Prores is shown (@220Mbps). BM also said in several interviews when it was announced that raw recording might not be available when the camera starts shipping. They could of course be holding back showing raw BMPCC footage publicly to gain the maximum impact from advertising just before it is released but you have to ask yourself why? When most who will get one have probably pre-ordered. TBH I think BM will be shipping on the date they committed to this time but I won't be surprised to find that raw video is in a later FW update.
I'm was waiting to see some real world footage from users to make my mind up about buying one but the 50d bombshell made me rethink. I would still love to get one because I like what I have seen but I'll sit on the fence a little longer.
I made a quick benchmark of a SanDisk Extreme 45MB/s. After formatting it to exFAT file system, it gives stable 20+MB write speeds.
https://www.youtube.com/watch?v=HI4XZPAMoZk (https://www.youtube.com/watch?v=HI4XZPAMoZk)
(http://oi43.tinypic.com/3144dpw.jpg)
Quote from: Jonit on June 15, 2013, 11:55:47 AM
I made a quick benchmark of a SanDisk Extreme 45MB/s. After formatting it to exFAT file system, it gives stable 20+MB write speeds.
https://www.youtube.com/watch?v=HI4XZPAMoZk (https://www.youtube.com/watch?v=HI4XZPAMoZk)
(http://oi43.tinypic.com/3144dpw.jpg)
Hi Jonit,
You just read my mind, yesterday I did two tests with a 64 GB Sandisk Extreme 45MB/s
(http://oi44.tinypic.com/ickaqt.jpg)
(http://oi44.tinypic.com/2vhzm09.jpg)
I also did a test in the computer, with those results:
(http://oi40.tinypic.com/1qmpn7.jpg)
Are we sure those cards are 45 MB/s??? Maybe I also have a bottleneck on my SD card reader, has somebody else tried the 45 MB/s cards on their compurters? I recommend the
h2testw app (http://flashfakecentral.wordpress.com/testing-flash-memory-chips/h2testw-english/ (http://flashfakecentral.wordpress.com/testing-flash-memory-chips/h2testw-english/)), but you can try just transfering big files from the computer to the SD and check the transfer speed.
I think it's quite pointless to post benchmarks of your SD cards in this thread.
Everybody understood that the SD-Controller is limited to 21 Megabyte/s write speed.
@ jordillonch: Your card reader probably doesn't support UHS-1 so it has the same limitation like our cameras.
The SanDisk 45 Megabyte/s cards actually are that fast. Here's a benchmark I found on Amazon:
[Spoiler](http://ecx.images-amazon.com/images/I/61l5E08j7YL.png)[/Spoiler]
@ Andy600: That's interesting. I wasn't aware of the possibility that the Cinema DNG recording might be added with a later firmware update.
Thank you for sharing this thought. But I just used it as an example to show that it is possible to create a good video camera even for such a low price. In my opinion Canon creates good cameras for stills but they waste a lot of potential on the video side, just to protect their expensive camcorders. I mean, look at the 5D Mark III. Canon could have done what Magic Lantern does without any problems.
Anyway. I'll stay with my 600D and its H.264 videos, waiting to see how well the 70D and BMPCC will perform ...
Quote from: CFP on June 15, 2013, 02:16:06 PM
I think it's quite pintless to post benchmarks of your SD cards in this thread.
Everybody understood that the SD-Controller is limited to 21 Megabyte/s write speed.
@ jordillonch: Your cardreader probably doesn't support UHS-1 so has the same limitation like our cameras.
The SanDisk 45 Megabyte/s cards actually are that fast. Here's a benchmark I found on Amazon:
[Spoiler](http://ecx.images-amazon.com/images/I/61l5E08j7YL.png)[/Spoiler]
Thanks men!
"Crop35.com @Crop35com
Now You can edit @autoexec_bin ML RAW files directly in #Premiere and #AE http://bit.ly/1biobfP with #gingerHDR plugin from @19lights."
I installed the lasted version of Ginger HDR from 19lights.com and it works fine so far. It imports to Premiere Pro cs6 the .raw file without having to convert to .dng (I was using raw2dng.exe) then importing to Lightroom to convert to PSD 16bit then importing to Premiere.
I was having problems with Premiere crashing with the PSD files, which were also auto converting to 30fps from 20fps.
Now I just import the raw file itself without converting...the time it saves is hours and hours.
I simply cannot believe how easy this is compared to before. I feel that something HAS to go wrong somewhere, but not at all!!!!
Such a surprise. I bought this 600D on Craigslist for $350 I think just days before Magic Lantern announced raw recording. It has been really fun so far.
Oh I also had several files larger than 4GB that had broken up and I thought they would be useless because raw2dng.exe didn't seem to be able to handle it, or I couldn't figure it out, but now I just import the file into Premiere like any other file.
I am still in shock a little bit this morning....
The broken up files will combine in terminal, rawanizer and I guess ginger hdr.. might give it another go since the dev fixed it.
Hi guys! First I like to thank you all for the great work.
I hope this is the right place to adress my problem. I did not find any useful information in the RAW video beginners guide or with the search option.
I can't run the raw module on my 600d. I installed ML 2.3 on a new sandisk 95 mbps card and then copied the tragic lantern files. When I try to load modules it says "error loading 'B:/ML/modules/600d_102.sym' : file does not exist", which is obviously not the case. I guess I'm doing something wrong. So far I tried these two builds: [600D] MovedInd.zip and [600D] NewSystem.zip.
Thanks in advance
PTo
Make sure you place the Modules folder into the ML directory.
One more 1536x656 footage. Some shots look really pretty ...
Upload it to Vimeo (or do 1080 in YouTube)... can't see much of a quality at 480... :)
Quote from: AriLG on June 16, 2013, 09:40:09 AM
Upload it to Vimeo (or do 1080 in YouTube)... can't see much of a quality at 480... :)
or so ;)
frontloop, it is 12fps + Twixtor?
Thanks !
How were you able to achieve 20 seconds (500 frames) at 1536x656 ?
What are your settings ?
@alephone
Thanks! That was the problem. Missed that completely
Quote from: MD87 on June 16, 2013, 12:43:43 PM
frontloop, it is 12fps + Twixtor?
exact. In that shot it worked fine.
@AriLG
Recording was with 11,988 fps. SanDisk Extreme 45MB/s. Then used twixtor in the post.
@frontloop, thanks.
Are there any shortcomings to using twixtor (as it is, after all, a synthetic process) ?
Hi,
at the 600d of mine, it works. But there is one question:
How to open the *.raw Videos on my Windows PC?
Quote from: AriLG on June 16, 2013, 02:20:42 PMAre there any shortcomings to using twixtor?
Yes. Twixtor and the free alternative MVTools2 (AviSynth Plugin) may create artefacts if the scene has complex patterns, too much detail oder too fast motion. They aren't perfect.
@ BenRott: You have to convert them to any format you want by using a programm like raw2dng or one of its countless modifications.
@CFP Thanks, but how does raw2dng work?
Quote from: BenRott on June 16, 2013, 03:20:53 PM
@CFP Thanks, but how does raw2dng work?
Drop a RAW file onto raw2dng (drag above it - and release the mouse button). the dng files will be created on the same folder.
Hey guys,
a little Twixtor test here :
All informations on the Youtube page .
The same test in the same conditions, without the zoom x5 crop. I wanted to test the reaction of Twixtor with pan/tilt :
I've made my workflow for the shooting of my short :
- H264 1080p@24fps cinestyle for fast moving scenes and rapid workflow (no conversion)
- RAW 1468@12fps 2.35 for static or slow scenes, or pan/tilt camera with static scenes :
- Rawmagic to convert Raw to DNG
- import DNG in AE as 12fps
- insert in 24fps timeline, with twixtor effect to create in-between frames
- export in ProRes 422HQ or 444
- edit in FCPX, export in ProRes
- Uprez to 1080p (for the parts shot in RAW) in AE with Instant HD
With my tests on my MBP core i7 16GB ram, the Twixtor step is x13 real time, and Instant HD is 7,5x RealTime.
Thanks again. What Sd-Kart would you recommend me, for the best qualety I can get?
Good test
Shows almost zero jello from 12p :)
Quote from: romainhc on June 16, 2013, 04:41:19 PM
The same test in the same conditions, without the zoom x5 crop. I wanted to test the reaction of Twixtor with pan/tilt :
I've made my workflow for the shooting of my short :
- H264 1080p@24fps cinestyle for fast moving scenes and rapid workflow (no conversion)
- RAW 1468@12fps 2.35 for static or slow scenes, or pan/tilt camera with static scenes :
- Rawmagic to convert Raw to DNG
- import DNG in AE as 12fps
- insert in 24fps timeline, with twixtor effect to create in-between frames
- export in ProRes 422HQ or 444
- edit in FCPX, export in ProRes
- Uprez to 1080p (for the parts shot in RAW) in AE with Instant HD
With my tests on my MBP core i7 16GB ram, the Twixtor step is x13 real time, and Instant HD is 7,5x RealTime.
I would like to play with twixtor myself, but since some of you finally came back to start doing test, would be bothering someone if I ask you to make a decent test with twixtor?
This time I have to request something like this, now that I got my hand on a t4i, and I want to see how far can it go.
Thanks for trying, happy testing.
Quote from: Edgar Matos on June 16, 2013, 06:36:53 PM
This time I have to request something like this, now that I got my hand on a t4i, and I want to see how far can it go.
Well, I've made some test yesterday, with 24fps 720p and with 12fps 640x480. Yes, sure, 12fps gives you a very decent picture quality. See for example here: http://www.naumik.com/temp/scr4/20130617-vnc-280kb.jpg
But when you have something to move fairy quickly on a textured background - you'll get this:
http://www.naumik.com/temp/scr4/20130617-gj8-256kb.jpg
I know twixtor has solutions for this with manual masking, etc, etc... but it's a too hard workflow already...
And it's not too visible on playback (just looks like blurred edges around moving things).
I've didn't develop all my yesterday's tests, so maybe I'll post an update later today or tomorrow.
But overall I think it's good to shoot slow moving scenes with 12fps, and fast moving thing with 24fps 720p mode.
I tried to shoot my usual style (short scenes, 5-10-15 sec per take), so I've got 1664x704 with 12fps, and 1536x384 (stretched to 1536x640) in 720p mode 24fps. Fairly good as for me.
Here's the difference between these modes:
12fps 1664x704: http://www.naumik.com/temp/scr4/20130617-s49-384kb.jpg
24fps 1536x384: http://www.naumik.com/temp/scr4/20130617-c32-321kb.jpg
Both stretched to 1920px wide using PhotoZoom Pro.
My opinion is - after YouTube applies it's magical compression to it - no one will see the difference (especially if watching from Facebook in 480p mode in little window).
Thank for your time@vicnaum. The results are just what I was expecting.
But here is something I didn't understand. You said "
Quote from: vicnaum on June 17, 2013, 09:38:07 AM
Well, I've made some test yesterday, with 24fps 720p. , and fast moving thing with 24fps 720p mode.
Everybody here know that is impossible to get more than 2 seconds in 720p out of the 600d. Maybe you didn't mean it that way and I misunderstood.
Have you try this?
This is for those who want to try 720p with a (2.35.1)
FPS 24 (24p) {16:9} 1280x720 127-150 27.8MB
FPS 19 (19.001p) {2.35.1} 1280x544 277-4125 22.0MB
FPS 18 (18.002p) {2.35.1} 1280x544 expect 525-10000, 277-10000 20.9MB NO THAT BAD
FPS 17 (17.125) {2.35.1} 1280x544 577-10000, 626-10000 19.9MB GOOD
FPS 16 (16.003) {2.35.1} 1280x544 Continuous 18.5MB SWEET SPOT
Quote from: vicnaum on June 17, 2013, 09:38:07 AM
My opinion is - after YouTube applies it's magical compression to it - no one will see the difference (especially if watching from Facebook in 480p mode in little window).
Check "T3i/600d (H.264 vs Raw) Awesome results!" in share your videos. watch it at 480p and notice the big difference in dynamic range and color.
By 720p I meant the canon mode that uses lineskipping.
By youtube 480p I meant the difference in sharpness between normal mode and line-skipping mode. And it's obvious that the RAW gives better color controls.
These experiments with twixtor are interesting. I think if we can get as much fps as we can it will be better for twixtor results.
I would like to do a request:
enable 19,181 or 19,2 in fps override menu, because:
19,181 / 4 = 4,795 x 5 = 23,976
19,2 / 4 = 4,8 x 5 = 24
so twixtor will create one new frame for each four existing frames
(it is impossible to get 19,181 or 19,2 changing times in advanced menu, so it need to be enabled in the fps menu)
1088x608 works great @ 19fps so enabling 19,2 or 19, 181 will be usefull
when crop to 16x9 it will be 1080x608, a great use of almost all recorded pixels and probably good twixtor results (19,2 to 24)
If you can't get 19.2 with advanced timings it won't happen just setting it in the menu.
This is incorrect
Twixtor has to make 24 frames each sec, because each of those 19 frames is at the wrong temporal position
So the result is 100% Twixtor
12p is best -- Twixtor only needs to tween 1 extra frame per sample 12p --> 24p only 12 frames needed per sec. so the result is 50% Twixtor
Quote from: apefos on June 17, 2013, 12:12:38 PM
so twixtor will create one new frame for each four existing frames
Yes John, I gave it a thought. I understood and agree. better shoot 12fps to do twixtor.
If some software just recreates one frame for each four frames the motion will have some stops, something like a balk, to stumble at each four frames, so it would be annoying, and the footage will looks like a fast speed.
What SD carts do you use?
Me? I use the Sandisk SDHC 32GB Extreme 45MB/s
In the USB 3.0 Card Reader in Windows Computer it shows 28MB/s write and 34MB/s read
Works great for all resolutions and fps in RAW recording in T3i 600D until something around 21MB/s when frames starts to skip
I mean you also, but I thought au YOU all, that are aactive writing
I'm using the same card. And I get the same results. It's a very good card.
Shot some test footage in 720p mode. Aliasing and moire are present, but the added dynamic range is worth it. Had a few "blinky sky" moments, but looking at the individual dng files to see if I can correct them individually in ACR. The other flickering is due to the lens I used... Sigma 18-50 without constant aperture, so zooming is a no no, but hey this was only a test of dynamic range and flexibility in RAW.
***BUG ALERT***
Excuse me if this has already been reported.
When using the camera without ML on a card, my camera will not allow me to change resolution. It says SRaw and I just get a screen with colored boxes even after power down, remove battery etc.
I have to completely reset the camera to gain normal functionality which is a royal pain. Seems like some work has to be done to resume the camera resources.
I have advised countless times against the sraw hack, but that's all I can do. Sorry.
LOL
Quote from: a1ex on June 18, 2013, 11:22:52 PM
I have advised countless times against the sraw hack, but that's all I can do. Sorry.
Quote from: robrock_68 on June 18, 2013, 07:58:26 PM
Shot some test footage in 720p mode. Aliasing and moire are present, but the added dynamic range is worth it. Had a few "blinky sky" moments, but looking at the individual dng files to see if I can correct them individually in ACR. The other flickering is due to the lens I used... Sigma 18-50 without constant aperture, so zooming is a no no, but hey this was only a test of dynamic range and flexibility in RAW.
I agree the dynamic range is sweet but the quality is terrible! It's like you shoot it with your iphone 3gs or something.. For now h264 codec is still the best option if you want to shoot something serious... Damn i hate that 21mb limit on 600d..
Not feeling the twixtor workflow, just one more step in an already complex editing setup. I've been trying out different upscale solutions and ACR's stock crop tool works pretty well, just gotta shoot with a sharp lens and keep sharpness off during editing till the last step.
thinking I'm gonna use raw on the 600D for some greenscreen tests and see what happens... Just went back and looked at some h264 footage, and compared the two directly, and I like the h264 better overall. However, I looked at some footage from the MKIII and OMG. I just don't want to spend that kind of money. I'm thinking the BMPC and tokina 11-16 eos mount and a eos to mft adapter...
Quote from: JohnBarlow on June 18, 2013, 11:21:26 PM
***BUG ALERT***
Excuse me if this has already been reported.
When using the camera without ML on a card, my camera will not allow me to change resolution. It says SRaw and I just get a screen with colored boxes even after power down, remove battery etc.
I have to completely reset the camera to gain normal functionality which is a royal pain. Seems like some work has to be done to resume the camera resources.
I just popped the alpha back on the card, switched it back to RAW Large fine and reinstalled the current supported ML. Good to go.
Remember when you set sraw to set it back. You won't be able to from canon menus. Its not a canon supported mode.
And never use MRAW as the pictures aren't going to come out.
The latest build by 1% is rock solid for me. I did 1024x512 reso without any issues on my Sandisk. Shot over 3000 frames without dropping a single frame. I like that reso better than 960x544.
Thanks for all the work 1%.
Okay, since I seem to have a bit more female in me than I realized, I can't make up my mind. :P With RAW in mind, which camera (Canon DSLR) is the best for using this feature. I would like to avoid the MKIII cost, so which of the "lower" cost DSLR's is best so far (Current product line).
Looking for the biggest bang for the buck and good low light in the h264 modes as well.
Anyone know if there's still development going on for new 600D builds? Aslo I was looking at the other thread re: variable buffering. Anyone try that trick with the 600d? Is it even possible?
Quote from: robrock_68 on June 20, 2013, 07:22:35 PM
With RAW in mind, which camera (Canon DSLR) is the best for using this feature.
If a EOS 5D Mark III is to expensive, get a used EOS 50D. You can get them for ~ 400 €.
Since the 50D has the same write speeds like a 5D Mark II (~ 80 Megabyte/s at the moment, but there's still space for improvements) it's capable of recording 14-bit RAW at high resolutions. Only issue: No audio recording. You have to use an external recorder ... if you don't do that anyway :D
Here's the 50D's RAW thread: http://www.magiclantern.fm/forum/index.php?topic=5586.0
If you need a flipscreen and internal audio, wait for the 70D and keep your fingers crossed for it to have a CF-card slot.
The Rebel cameras are to slow for high resolutions.
Yea coming up... my 600D card got eaten so I have to take a card from something else.
It won't let me upload to bitbucket for some reason:
http://www.qfpost.com/file/d?g=6WfjNBd80 (http://www.qfpost.com/file/d?g=6WfjNBd80)
Quote from: N/A on June 19, 2013, 08:38:51 AM
Not feeling the twixtor workflow, just one more step in an already complex editing setup. I've been trying out different upscale solutions and ACR's stock crop tool works pretty well, just gotta shoot with a sharp lens and keep sharpness off during editing till the last step.
I;m thinking the same. Still, I made some test using 18 and 19 FPS, it allowed me to shot 1280 2.35.1. With out twixtor of course. The result where pretty decent. I was about to upload some footage, but now I see that Alex had another epiphany. So, I'm waiting until dialog timers are disabled in order to see how far can the camera go now.
Quote from: 1% on June 21, 2013, 01:20:50 AM
... my 600D card got eaten
Yeah it happens sometimes
ok, possible game changer.... Expensive, but Is now on my short list of things to get.....
http://store.mosaicengineering.com/VAF-TXi-Moire-Aliasing-Filter_p_14.html (http://store.mosaicengineering.com/VAF-TXi-Moire-Aliasing-Filter_p_14.html)
you tube example
Are we about maxed out on the RAW abilities of the 600D?
Wow great. Now I can shoot reasonable time on max resolution @ 2.39:1 (1728x...).
Around 150-250 frames is usually enough. Both in
[email protected] mode, and in 640@12fps mode.
what about the new streaming that a1ex released? is gonna improve buffering on the 600d?
Why is the file considered "unsafe" ?
Is there alternate download ?
I got 800 frames on 1024x576 before it stopped and about 67 frames on 1280x720, so it did add a small pop to it. The magenta frames are back for me though. The Canon menu is set to 1920x1080 24p. I'm going to try some other variations but these are the first magenta frames I have seen in a while now =( .
Try with dialog timer disabled. Should drop CPU usage and have less pink frames. Also 640x480 with GD off should give the lowest CPU usage.
What is unsafe.. bit bucket won't let me upload to that repo for some reason, it logs me out.
Quote from: NewNoise on June 21, 2013, 01:09:04 PM
what about the new streaming that a1ex released? is gonna improve buffering on the 600d?
Where is that located???? curious about that. I would like to locate someone that has that filter and see what the results are with RAW. Trying to message the maker of the video test to see if they would be willing to try it and see how it does.
Quote from: alephone on June 21, 2013, 01:54:32 PM
I got 800 frames on 1024x576 before it stopped and about 67 frames on 1280x720, so it did add a small pop to it. The magenta frames are back for me though. The Canon menu is set to 1920x1080 24p. I'm going to try some other variations but these are the first magenta frames I have seen in a while now =( .
does 1280x720 is 24 fps?
Quote from: Jonit on June 15, 2013, 11:55:47 AM
I made a quick benchmark of a SanDisk Extreme 45MB/s. After formatting it to exFAT file system, it gives stable 20+MB write speeds.
https://www.youtube.com/watch?v=HI4XZPAMoZk (https://www.youtube.com/watch?v=HI4XZPAMoZk)
(http://oi43.tinypic.com/3144dpw.jpg)
The file was there "600D 102.fir" (70K) on a brand new Sandisk Extreme 32GB SDHC U1, 45MB/s. Have tried exFAT formatted in both Mac and Windows, and with ML 2.3. Same text each time: "Update file can not be found. Please check the memory card andre load battery than try again".
Have also tried another new SD Sandisk Extreme 32GB SDHC U1 95MB/s.
No problems installing ML 2.3 on the cards when formatted as FAT32.
Quote from: 1% on June 21, 2013, 02:58:56 PM
What is unsafe.. bit bucket won't let me upload to that repo for some reason, it logs me out.
Well, I was not able a few hours ago to download this version. now I could...
300 (or so) at 1280x544x25 (1:2.39). DG off. the screen freezes after 1 or 2 second (but continues recording till 300 is reached).
SanDisk 16GB 95MB.
Quick test of color correction capabilities of 14-bit RAW.
1728x692 @ 12fps
Hot damn. 440 frames @ 1280x512, 23.976 fps. GD off.
Quote from: Robbe on June 21, 2013, 08:12:21 PM
Tried the same on my 600D without success. Cant install ML. Says: "Update file cannot be found".
Which version did you install, latest nightly? See that you have 3 version of autoexec.bin.
you need to have "600D-102.FIR" on your SD card. I was testing also other builds of ML at that time, that's why i had 3 different autoexec files on my card.
is there also a way not to recort direct at the SD-Cart, but to send the RAW-Files with HDMI- to my Blackmagic Hyperdec Shuttle?
Sure, just like you can browse the web on your PC via headphone jack.
And like you record 1080p RAW video on a 1100D.
Quote from: Jonit on June 22, 2013, 12:33:35 AM
you need to have "600D-102.FIR" on your SD card. I was testing also other builds of ML at that time, that's why i had 3 different autoexec files on my card.
The file was there "600D 102.fir" (70K) on a brand new Sandisk Extreme 32GB SDHC U1, 45MB/s. Have tried exFAT formatted in both Mac and Windows, and with ML 2.3. Same text each time: "Update file can not be found. Please check the memory card and reload battery than try again".
Have also tried another new SD Sandisk Extreme 32GB SDHC U1 95MB/s.
No problems installing ML 2.3 on the cards when formatted as FAT32.
Use EoSCard to make it bootable
Quote from: N/A on June 22, 2013, 02:10:19 AM
Use EoSCard to make it bootable
Done that in both Mac and Windows. Same result.
Is there any difference in what order it is done? That is, first format exFAT, made it bootable and then copy ML 2.3?
Weird, I have a Sandisk 95 formatted to exFat, works beautifully.
New build, 1152x496, got almost a solid minute of footage. Upscales really well to 720p (1280x552).
I would suggest preparing a "data sheet" in which people would feel in all date they can in order to try and assume the current sweet spot.
If that's ok with everyone, I'll prepare a data list for us to feel (as of now it hard to know what's what as people use different cards, different builds, different fps - 24 or 25 - and the list goes on...).
Quote from: N/A on June 22, 2013, 07:32:41 AM
Weird, I have a Sandisk 95 formatted to exFat, works beautifully.
Ooops! Got to the end ExFAT to work, BUT noticed that I couldn't change the image quality when Canon 600D was "normal", that is when I reset back to basics in my attempts with ExFAT.
This is how it now looks when the camera is "normal" and trying to change image quality back from sRAW:
(http://unttv.teknomedia.se/QualitySetting.png)
Quote from: AriLG on June 22, 2013, 03:42:48 PM
I would suggest preparing a "data sheet" in which people would feel in all date they can in order to try and assume the current sweet spot.
If that's ok with everyone, I'll prepare a data list for us to feel (as of now it hard to know what's what as people use different cards, different builds, different fps - 24 or 25 - and the list goes on...).
Good idea, I'll contribute. Problem is, if our resolutuons change again we'll have to keep it updated constantly.
@robbe
C'mon... read... sraw can't be changed from canon menus.
Quote from: 1% on June 22, 2013, 07:31:05 PM
C'mon... read... sraw can't be changed from canon menus.
What do you mean with "C´mon...read..."?
And how to get back the settings for image quality when using Canon 600D without ML?
You don't... its not a valid mode. But if you look at posts earlier in this thread the issue is discussed ad nauseum.
Quote from: N/A on June 22, 2013, 07:17:51 PM
Problem is, if our resolutuons change again we'll have to keep it updated constantly.
Exactly. that's why a chart is necessary. there are way too many variables and if we want to help each other finding the sweet spot on each given moment (without going through a long trail and error process) this is the place.
We will have to give our : TL version (date), our cards , formatted cards : yes/no , resolution on ML RAW, aspect ratio... anything that COUNTS... (including settings in the canon menu) and - of course - frame count. for example, in some cases I was able to reach higher number of frame count from what users were saying here, and on some others cases - lower count.
Should be unlocked height and the multiples from now on, unless you find a res/aspect I really need to add.
Does anyone here have any experience with using the Ginger HDR plugin with After Effects or Premiere Pro? The quality between the RAW imported directly into Adobe vs. the DNG imported in and rendered seems to be not as good as the DNG imported. It just seems fuzzy, grainy or whatever. It is pretty noticeable too. It's a shame because it is so much easier of a workflow that way. I'm hoping I am just doing something wrong. I have tried it with denoiser and without denoiser and it is still crappy compared to the rendered DNG method.
The latest one should be good, older version was bad. The dev came on here and fixed it I believe.
Quote from: 1% on June 23, 2013, 12:54:06 AM
The latest one should be good, older version was bad. The dev came on here and fixed it I believe.
I'm a bit confused now, which is the latest version for RAW video? The latest Tragic Lantern here https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads or the latest nightly here http://nanomad.magiclantern.fm/nightly/
Thanks.
The latest RAW should be the one that 1% linked a page or so back in the thread due to not being able to upload it to bitbucket.
Quote from: N/A on June 22, 2013, 07:32:41 AM
Weird, I have a Sandisk 95 formatted to exFat, works beautifully.
New build, 1152x496, got almost a solid minute of footage. Upscales really well to 720p (1280x552).
I have a Sandisk 95MB (32GB) formatted to exFat.
New build, 1152x482 [1:2.39] @ 25fps (640x480 + DontClickME hack) --> 45 seconds.
Are you at 24fps ?
Hey guys. Is there a chart of write speeds for Canon cameras somewhere? I wish I knew about the 600D's limitations in this regard before I bought it. Now I'm kinda disappointed (... Also, why is video cropped when shooting lower resolutions? Isn't it possible to... Wait, I just got it, it's RAW... You can't resize it in camera... Dammit... So, is that [optimal settings chart] coming?
Also, what card would you suggest that would allow to use the potential of 600d fully but not cost too much, I feel like my current Transcend 32 GB SDHC Class 10 TS32GSDHC10 isn't up to the task... write speed wise...
Quote from: alephone on June 23, 2013, 03:26:23 AM
The latest RAW should be the one that 1% linked a page or so back in the thread due to not being able to upload it to bitbucket.
ups, I skipped that message. Thanks!
How do you get rid of the pinkies again?
Quote from: AriLG on June 23, 2013, 09:10:30 AM
I have a Sandisk 95MB (32GB) formatted to exFat.
New build, 1152x482 [1:2.39] @ 25fps (640x480 + DontClickME hack) --> 45 seconds.
Are you at 24fps ?
23.976 override, write lengths seem to vary slightly each time as well.
Hey guys, i've been following the progress for a while now and i'm not technical enough to join some of the conversations going on here so I mostly read, learn and test.
Today I did some testing and I got some decent results..
~900 frames (~38 sec.) at 1216x480 (2:67:1), 640x480 mode, FPS override to 23.980, Dont click me hack, Sandisk 16GB Class 10 45mb/s. And ~550 frames at 1216x512 (2:39:1), same settings.
All in SRAW, btw.
I think we're definitely getting somewhere now.
Quote from: N/A on June 23, 2013, 02:52:56 PM
23.976 override, write lengths seem to vary slightly each time as well.
Well, my current dream is of 1280x533 (1:2.40@25fps) for 60 seconds... dreams are not a bad thing :)
Quote from: far.in.out on June 23, 2013, 02:41:04 PM
How do you get rid of the pinkies again?
My problem was fixed by just reformatting my card and that took care of them. I am only getting pink frames when I run a reso that is not one of the sweet spot resolutions. If you change the setting in the Canon menu to the 640x480 that should eliminate most if not all of the magenta frames. It did for me. I am getting continuous at 940x544 w/ no pink frames all the time since a few builds back. With this new build I can go a reso or 2 higher and get a decent amount of frames with no magenta at the 640 setting and even sometimes the 1920x1080 Canon setting. It seems to be hit and miss.
Just to let you know I actually have the Mosaic Engineering filter mentioned earlier permanently installed in the 600D
It is awesome.
It only works for 1080p mode, or anything cropped out of 1080p view, as it were, so I'm not sure how it'd work with RAW.
If the RAW streams are taken from the camera set to 1080p mode it should work. I can test with the latest build if you can point me there.
It's brilliant with the boosted bitrate and I-frame from the other thread though. at 150mbps with the filter there's amazing detail, and ISO 6400 cleans up like you wouldn't believe!
The removal of false detail and aliasing makes the whole encoding process more efficient. It's still not razor sharp, but it's like 16mm film with the right picture profile (VisionColor or similar).
Do these RAW hack builds have the GOP/bitrate adjustments from the other thread in them too? That's about to be daily use for me so I don't want to lose it...
Quote from: jgharding on June 24, 2013, 12:46:42 PM
Just to let you know I actually have the Mosaic Engineering filter mentioned earlier permanently installed in the 600D
It is awesome.
It only works for 1080p mode, or anything cropped out of 1080p view, as it were, so I'm not sure how it'd work with RAW.
...
It's brilliant with the boosted bitrate and I-frame from the other thread though. at 150mbps with the filter there's amazing detail, and ISO 6400 cleans up like you wouldn't believe!
The removal of false detail and aliasing makes the whole encoding process more efficient. It's still not razor sharp, but it's like 16mm film with the right picture profile (VisionColor or similar).
Well, not quite.
I purchased my unit exactly for the use of T3i and TL high bit rate (and removal - even if not entirely - of false color).
First of all, as a1ex said in another thread, the TXi is NOT meant for cropped video (which is how RAW operate). it is intended solely for 1080p footage.
As RAW is a lot of pain in post (especially if you shoot a lot of clips), I thought : what a great solution. I'll kill two birds in one go - moire/aliasing (which is awful in RAW on the tXi's - and in the cases which I shot : REALLY awful) ; false/8 bit color (well, color - according to the videos I have seen - was a lot more "solid" on the VAF-TXi, much more closer to the RAW clips I have shot).
Unfortunately, my unit - while it SEEMS to function (haven't done tests to check if it delivers what I have bought it for) - will not let the mirror on my t3i go down upon shutdown, and gives an err. I have no idea if I can on cannot use it like that but I prefer to NOT use is like that.... which renderes my unit useless.
I also have also a t2i. on it, the mirror goes back as intended upon shutdown. but with my Tokina 11-16 (which SHOULD work) the results were not what I have seen on the net. it might be an alignment thing (which can explain the problems I have with both my cameras), but as I understand, the Mosaic guys are still checking it.
In any case, I have bought the unit solely for my t3i and I can't use it. Bummer :-\
If my problem will be fixed, I'll try and do a real life comparison (video) between RAW on my t3i and clips shot with VAF. at the moment I still await their response.
Quote from: AriLG on June 24, 2013, 02:17:14 PM
First of all, as a1ex said in another thread, the TXi is NOT meant for cropped video (which is how RAW operate).
Huh?!
Quote from: a1ex on June 24, 2013, 02:34:02 PM
Huh?!
Ummm.... didn't you say that ? (I am sure I have seen it. was it a joke ?...)
Exact link please. I don't even know what a TXi is...
Quote from: a1ex on June 24, 2013, 02:44:47 PM
Exact link please. I don't even know what a TXi is...
Can't find it ATM, among the mountains of data here. you started the post with a "LOL" and then said that the anti aliasing filter for the TXi family (T2i, T3i and T4i - hence the T
Xi) is intended only for 1080P video and not for RAW (I'll try and look for the exact link. someone asked for info on usage of the filter in conjunction with RAW).
Found: http://www.magiclantern.fm/forum/index.php?topic=6242.msg48530#msg48530
I actually said exactly the opposite. The filter is for the 1080p video mode (the one you select in Canon menu), no matter what you do with that data (H264, mjpeg, raw).
Crop mode is when you record in x5 zoom.
So yes, the VAF filter works for raw just as well as for H264 1080p.
Think about it: if you cut an image in half in photoshop, does that influence the aliasing? (or sharpness, or softness, whatever?)
Gah...
OK. great to hear that ! :)
So it leaves me even more frustrated with my own personal problem with the VAF-TXi :(
I don't really consider the lack of mirror drop a problem. I only use the 600D for video, so I never need the mirror, the box can stay jammed up for all I care, it functions perfectly as the tool i need it to be.
I did use the TXi filter with a 550D too, and oddly enough it used to error all the time with filter in, getting annoyed and ERRor locking up with the TXi filter in place
The 600D doesn't care about it and has been rock solid.
I can't see how the mirror physically could drop down with it in place though, as the top of the filter rests against the bottom of the mirror, how can the mirror drop down in either model unless it isn't fitted correctly?
***
Back on subject, all i meant is since the filter is designed to cut the 18MP full sensor to 1080p precisely, any other type of cropping or scaling of the sensor won't benefit from the TXi filter. Only cropping from that 1080p feed with those same lines skipped.
For example, 720p scaled from the full sensor is aliased. So if raw mode is cutting a crop from the 1080p image, scaled from the sensor then it'll work, otherwise it'll look different, but not anti aliased. At least that's what I gather. But I can just test it soon.
If properly fitted in 1080p mode though, it's quite brilliant.
(http://i1024.photobucket.com/albums/y308/jgharding/filter-lolz_zps36352f7e.jpg)
In RAW Vid menu, when u choose reso, depending on ur choice the hint at the bottom is either green or yellow... I noticed if it's green ur probably gonna get continuous rec, and if yellow it's limited in length... Is that hardcoded or there is some internal bench that determines what I can get with current set-up and card? I'm just wondering why I can't go any further then 15-16MBps... Am I missing some settings/hacks or my card is just not good enough... It tops out at 15MB when writing from PC cardreader so it's gotta be the card...
What is that don't click me hack someone mentioned here earlier?
Hello. I've been using the nightly builds and updating as they become available. On the last two releases, I noticed that when I used ETTR to set the exposure, I've been getting the error message "WHOOPS" after a period of time where the screen flashes from bright to dark. This feature was working in the version in [600D] NoUniwbCorr.zip (2013-06-12). Has anyone else noticed the same issue?
Also, has anyone had any luck setting the exposure with ETTR in raw video mode, and then turning raw video off and shooting 1080p H.264?
Thanks for everyone's hard work on ML!
Quote from: jgharding on June 24, 2013, 08:17:43 PM
I don't really consider the lack of mirror drop a problem. I only use the 600D for video, so I never need the mirror, the box can stay jammed up for all I care, it functions perfectly as the tool i need it to be.
I did use the TXi filter with a 550D too, and oddly enough it used to error all the time with filter in, getting annoyed and ERRor locking up with the TXi filter in place
Well, I guess we are the exact opposites...
I do consider the inability of the mirror to drop as a problem as I get an ERR30 each time I shut down the camera. and I don't like it.
Back to the topic :
Will the 1024 frame size be back ?
Quote from: AriLG on June 25, 2013, 05:11:54 PM
Well, I guess we are the exact opposites...
I do consider the inability of the mirror to drop as a problem as I get an ERR30 each time I shut down the camera. and I don't like it.
Back to the topic :
Will the 1024 frame size be back ?
How odd :S yes ERR30 was what I got with the 550D.
I tried some raw recording while in 1080p mode and can confirm that the filter seems to eliminate the aliasing. The only issue is the drastically dropped depth of field from the cropping. Despite the dynaimic range, it loses a lot of its DSLR punch (large sensor look)... damned compromises!
If the GOP and slice control could be added into these new builds along with RAW modules I'd be very happy! It's be nice to have the GOP and slice control in a build that also has zero sharpness and so on available...
As it is the raw capable builds have a few things that the older GOP and slice control build I'm using don't, so I have to swap BIN files to try raw, but go back to GOP and slice for general work. It'd be nice to have parity if possible... but I'm not confident building the bits together to be honest...
So now that this has been out and tested for a little while. I'm wondering what peoples opinions are when it comes to H.264 vs the RAW on the t3i. I am by no means a pro and pretty new to DSLR (been doing it for only a year) but it seems like the RAW does look a little more rich and we know that there is more dynamic range with it. I'm obsessed with shooting it I guess because it's new and the whole thing is just fun testing a feature that was never intended by Canon. With the RAW @ (940x544) lower reso vs. the H.264 at 1080p which picture do you guys consider to better when they are both correctly lighted and graded? Is one better than the other or are there pros and cons of each one. I'm not meaning straight out of the camera but rather what the potential end results in post are compared to one another. Is there a winner?
Quote from: alephone on June 26, 2013, 07:35:50 AM
So now that this has been out and tested for a little while. I'm wondering what peoples opinions are when it comes to H.264 vs the RAW on the t3i.
From my own tests I'll be using H264, currently an older build with GOP and slice control.
I stress tested the picture hard and using slice control you can keep the encoder nice and high in GOP 1 (I-frame) mode. This makes ISO 6400 easily usable even in incredibly complex scenes, when using Neat Video to denoise. File sizes are high, but that's OK. It's a full APS-C sensor with a usable codec. It doesn't have full 1080p resolution but it's not bad. I-frame motion cadence is the most film like, as each picture is individual.
You don't have the dynamic range of raw, but raw is very cropped, and kind of removes one of the reasons I started using DSLRs in the first place: the large sensor.
The raw isn't so aliased for me as I have the Mosaic Engineering TXi filter installed, but it's still heavily cropped and low resolution. I could upscale 2.39:1 (I think it was 1024 * something) to 720p with crop bars, but still, the jello appears worse, resolution is lower even after upscaling, and it's really cropped so I'd have to start using crazy wide focal lengths and so on, change lens sets and so on.
The compromises in its current state aren't worth it
for me BUT everything changes in the world of Magic Lantern, so keep an eye on it, keep testing for yourself. 8)
Someone may find a way to round some bits on the way the card, 14-bits is pretty opulent. I'd sacrifice some of that colour info for the improved DR and resolution if we could get a 720p crop or similar. But perhaps no-one will be able to do it, perhaps they will.
Experiments with the 650D show it has the ability to write more quickly, so that model may be the best bet. Keep watching and testing... there's currently compromises.
I'm shooting with GOP1 slice control again on Saturday, a fashion film with lots of macro detailed close ups. Again, without the Mosaic TXi filter a Canon DSLR except the 5D iii would be hopeless with fine detailed cloth, all the extra data would be used by false colour and moire hell, so if you have the cash consider that tool.
That's the best roundup I can give.
thank you for the detailed breakdown it is exactly what I was looking for. I think I'll stick to H.264 unless something new gives in the way of RAW. I really didn't know much about the GOP and slice control features. I'm looking more into them now. What build are you using?
If you want extreme buffer for highest resolution and fps, the last build is better, but...
If the main goal is continous recording, the "New System" is the best build until now, no doubt, it works pretty well for continours recording with canon LV and the RAW menu and overlays are well done.
I would like to request 2 features, using "New System" as a base:
1 - implement 36fps in FPS Override menu, because it will give 1.5x slow motion in 24p video using 896x384 resolution, great for Cinemascope look and upscales pretty good for 1280x548, great for DLP or 3LCD projectors and for WEB. 896x384@36fps will allow continous recording, below 21MBps and intercuts good with 1088x480@24p. (to be honest I did not like the image quality using 720p in canon menu for raw slowmotion, image get lots of aliasing, so 896x384@36fps will be best option for slowmotion in 600d raw cinemascope look upscaled to 1280)
2 - enable a fourth line below the last overlay line in the bottom with the resolution and fps being used in the shoot for we see it while recording.
downloads for the "New System" increased a lot!
Thanks
I can explain these settings in practical terms (ive had a few messages asking me to do just that) but I think ill start a new thread about it
Otherwise I think the recent increase in popularity will result in development threads here being swamped with feature requests and questions about technical terms and their practical applications, which probably won't help devs with shared testing :)
Hello. Today on Vimeo found a video shot with the 60d with the settings 1728x736 (2.35:1 aspect ratio) @ 24 fps. https://vimeo.com/69037192 In the comments, the author recommends the following: "Try turning RAW image quality off and set it to S3 in the canon menu." So the question is: Does this focus on the 600D?
Quoteimplement 36fps
1. I don't think 1080/640 LV goes that fast.
2. Write speed is too low, try 720P at 36 and see what res you can do
QuoteTry turning RAW image quality off and set it to S3
Sraw gave up the most memory, others no change or a bunch less.
hi, thanks for the advice... but I do not like the aliasing from 720p LV
I did some tests setting fps override to 40fps in 640x480 LV and started to change the timings.
640LV at default timings with fps set to 40 it shows 37,7 or so... changing timings values I got 36,477fps continous recording at 896x384, enough for some slowmotion... after some crop it will give me 870x384, 2,26666:1 aspect ratio, the same of 1088x480@23,976 or I can keep 896x384 as is and crop the other to 1088x466 to get both at 2,3333:1
I believe these two settings will works great for 1280 upscaling for widescreen similar to cinemascope, great for 720p projectors.
1%
Have you managed to fix the upload problem you had with Bitbucket ?
Quote from: 1% on June 27, 2013, 06:46:51 PM
<snip>
Sraw gave up the most memory, others no change or a bunch less.
Thank you 1% for reminding us of this tip.
Does the Sraw setting leave the most buffer memory available on all cameras, eg. including the 60D?
600D only so far, every camera is different... on 6D i can shoot raw quality and there is another trick.
QuoteHave you managed to fix the upload problem you had with Bitbucket ?
Nope still kicks me out all the time. *sometimes* i can upload to 6D repo. So I dunno I need a new place to upload or just keep posting mega links.
Quote from: 1% on June 28, 2013, 09:20:14 PM
600D only so far, every camera is different... on 6D i can shoot raw quality and there is another trick.
Nope still kicks me out all the time. *sometimes* i can upload to 6D repo. So I dunno I need a new place to upload or just keep posting mega links.
Could you try a test file ? maybe a simple text file ... maybe BB suspect that the file is "bad"...
Out if interest, can it be that the upscaling process (in ACR) will later make the final file seem like its ghosting ?... when I pan or shoot people walking fast (or running) near the camera, there are "trailing" artifacts, not dissimilar from those seen in the first HDR movie...
It just logs me out and doesn't let me upload or delete anything. The upload box is missing :(
Quote from: 1% on June 28, 2013, 09:35:26 PM
It just logs me out and doesn't let me upload or delete anything. The upload box is missing :(
But you can push commits to TL2-Repo to hold the source up to date? Or is this impossible too?
Edgar
Yea, I can still push commits. Not much 600D beneficial stuff since the last build.
OK, so *best stills setting for most buffer space while shooting raw video, is sRAW on 600D / T3i, and different for other cameras, eg. set to smallest JPG on 60D?
Too, if possible, it would be great if switching on RAW video was able to set GlobalDraw to be on while setting up, off while filming, and perhaps on-demand (push a button, eg. DOF preview) for brief checking while filming.
I am betting that there's no way ML could change the Canon menu setting for stills resolution (i.e. for largest buffer size) when raw video is enabled.
thanks for everything you do, 1% :)
Quote from: Haliburton on June 28, 2013, 09:13:59 PM
Thank you 1% for reminding us of this tip.
Does the Sraw setting leave the most buffer memory available on all cameras, eg. including the 60D?
Quote from: 1% on June 28, 2013, 09:20:14 PM
600D only so far, every camera is different... on 6D i can shoot raw quality and there is another trick.
<snip>
p.s.
It would be great if we had a single thread for optimal settings while shooting raw, for all cameras'. Not sure how many people may have multiple camera models capable of filming in raw as I do; it would be great to see a chart of the differences, like the excellent "Current raw video capabilities - All ML cameras" thread http://www.magiclantern.fm/forum/index.php?topic=6215
Such a thread might be like the excellent, existing, general thread
http://www.magiclantern.fm/bestpractices
...but for RAW film making.
:)
QuoteToo, if possible, it would be great if switching on RAW video was able to set GlobalDraw to be on while setting up, off while filming, and perhaps on-demand (push a button, eg. DOF preview) for brief checking while filming.
It already does the first half of that, just set GD off in the module. The format has to settle down and get finalized before we can write guides.
Hello,
can you tell me which is the best workaround to avoid the pink-pictures?
Have all the latest builds on my 600D.
Thank you
I'm also getting pink frames with the last frame being a complete pure noise. :(
I'm not getting any pink frames on the NewSystem build from the 15th on 960x544. This has been the most stable build for me. I do get pink frames and the lcd lags on the first recorded file but everything after that is a gravy train with biscuit wheels.
Quote from: alephone on June 30, 2013, 01:43:23 AM
I'm not getting any pink frames on the NewSystem build from the 15th on 960x544. This has been the most stable build for me. I do get pink frames and the lcd lags on the first recorded file but everything after that is a gravy train with biscuit wheels.
This version on Bitbucket is not the latest.
As 1% is unable to upload new versions over there (Bitbucket) he uploaded elsewhere in the meantime. the latest one he uploaded contains pink frames (at least for me. and apparently not just me).
Yes the latest build has pink frames for me as well. That's why I reverted back to the last build on bitbucket as it has been the most stable for me. I was just answering Wartburgs question as to a work around (which for me was reverting back to an earlier build). I did not fare well with the latest build at all and I suspect a lot of other people w/ the 600d have went back to the build from the 15th by just looking at the number of downloads it has lol. I did find the latest build to be faster and squeeze a little more umphh out of the 600d but at the expense of littered pink frames here and there. I think we pretty much hit the wall with this camera but who knows. ML devs seem to be consistent about surprising us.
Try now and see if there are pink frames for 640x480 mode with FPS override or one of the other modes w/blackout.
https://bitbucket.org/OtherOnePercent/tragic-lantern-2.0/downloads/%5B600D%5D%20SixThirty.zip
I was also off by 0x4 in the raw type address, this build doesn't set one... any less or more pink frames?
There is only one difference between the autoexec.bins and no module differences.
[600D] NoType.zip
https://mega.co.nz/#!k9JAgTDa!CMfgO0UBWz2YUJLUL2HHt18t9MhqhY0-wDX6VjzJzXM
Just wanted to report that I have tried both of the new posted builds and am still getting pink frames. It does seem to be less but it also seemed to be almost every 1st frame was pink. I tried in 640x480 & 1920x1080 Canon menu setting. The 640x480 didn't lag in the lcd which is how I usually can tell that there is going to be pink frames present, but they were still there. I tried having the extra hacks on and off and same result. I didn't use the kill live view hack because I need live view lol so I'm not sure what the results would be. I'm still a fan of the newsystem ( June 15th) build. Which is strange because it's the last build before the variable buffering was implemented correct? I have tried all variables that I know of on freshly formatted new 45mbps sandisk cards and for now am still going to stick with the earlier build.
Have we reached a brickwall in regards to what the T3i can do (file dimensions) ?
Probably, but I'm not getting pink frames so I'll have to record some more an see if I can reproduce it. I think new system was after buffer changes, not sure.
Well, with this build I'm not getting pink frames, either (up untill now). and 1024 resolution is back... but :
1) I miss the beep on/beep off (good for sync ?)
2) the two versions of Hack freeze my screen entirely.
Is it realistic to hope for 1280 (2.39) ?... :) it's the only resolution up until now that I was more or less satisfied with... (in the realm of the T3i restrictions)
You should be able to turn sync beep on, sound menu is still there, just took off wav because its never going to work while writing.
Hack + GD off = frozen screen and preview doesn't show.
Hack + GD on = frozen screen + preview
2nd hack is if you don't turn off GD while recording, a little bit obsolete with GD on/off handling everything.
Yea, shot 82 frames.. first record (w/ card warmup on) and no pink frames. I dunno if you get one for the very first frame or something but otherwise no issue. 640x480 with FPS.
I meant : is it realistic to shoot for a conceivable amount of time... I can do now 300 frames or so (11-12 seconds) with 1280x535.
is it a dream to hope for 30 seconds ? (yea, I know about the controller...)
Thanks, 1%.
I am using New System (June 15) and see no setting for Global Draw off while raw recording, unless it has a special name?
In other news, both on my 60D and 600D at 23.976 FPS, it seems I have lost the ability to set shutter speeds approaching 360º, with Exposure Override on.
I have already experimented with shutter range settings in FPS over-ride, to no avail. I can set a very few shutter speeds about 360º when undercranking for time lapse (eg 1 fps to 7 fps) when FPS is set to "optimize for low light," but when I set 23.976 FPS, I cannot set shutter speed within ML any lower than 1/31 second.
Does anyone have some suggestions on what may cause this?
Perhaps interaction with other settings?
A tip I discovered, which may be more widely useful (in which case, where should I post it?):
I find the auto white balance feature within ML to be invaluable, and use it with my gray card all the time.
When under-cranking with long shutter speeds around 360º though, the results are completely wonky, with vastly different WB settings taken seconds apart under identical lighting conditions.
My strategy is now to set ML white balance at "normal" shutter speeds, then set long shutter speeds as required, and make test clips of gray card and chip chart (Color Checker Passport).
I use DNGs from the latter to create custom camera profiles for each lighting situation, and expect that it should prove useful for keeping color consistent when I begin to use polarizers, which may not be completely "neutral" density when used with digital cameras.
This is separate altogether from the problem with infrared light—especially with ND filters—affecting digital sensors messing up color and fabric rendition:
http://www.ryanewalters.com/Blog/blog.php?categories=IR
Schneider Platinum IRND filters
https://www.youtube.com/watch?v=v65N4pwWfxI
Quote from: 1% on June 29, 2013, 05:52:47 AM
It already does the first half of that, just set GD off in the module. The format has to settle down and get finalized before we can write guides.
Should be in module settings. If its not there before, it is now.
Quote
Does anyone have some suggestions on what may cause this?
Shutter speeds in movie mode are electronic. The speeds you were using before weren't tied to the electronic shutter at all. Now it shows the real speed, with override you can set a few more from the ML menu and get closest to 180 deg.
The limit was always something like 1/31, just the canon GUI tries to set photo shutter speeds. On 50D it lets you set 30" in movie mode and no way that is a real speed looking at the shutter timer.
Quote from: 1% on July 01, 2013, 10:08:24 PM
Shutter speeds in movie mode are electronic.
Yes, it took me a little while to figure how to work with it. But after you know what speed you want your time lapse you can fix your settings (FPS). Still, is too bad being unable to change the shutter speed. With out mention that you still have the 30 minutes limitation on video mode (this got me by surprise... I hate surprises). Regardless of that, the function is very useful exactly as it is (plus, there is no flickering this way) If you are looking for a specific time lapse setting you have to jump to picture mode.
The settings in picture mode are only valid for shutter click photos, when you set other speeds there the E shutter isn't really at those speeds, it stops where it stops in movie mode..
I can make the indicator say whatever.. but that will not be the actual speed the electronic shutter is at.
Yes.
I meant using a physical shutter or intervalometer for advance settings. Sorry for the confusion.
I wonder. Will it be possible to change the E shutter at will in the future? For example. I was using the raw module to record time lapses last week. and the lower I can get is 1/0.2 Eshutter but I had to go all the way down using FPS. The problem is: If I want to use that FPS in a very fast object/subject, it will be showing blurry things moving like hell all directions. Nothing wrong with that, but sometimes you need exactly the opposite. The other method is to record in a higher frame rate but it will consume a lot more space... A lot.
Thats the only real way to get long exposure in live view, lower the fps (sample longer). The sensor is wide open, nothing is actually moving.
Hey at that moment i don't have the chance to test it myself so i want to ask you, what is the highest possible resolution you can shoot raw at lest 3-4 seconds (i'm NOT interested with continious) at 23.976 (24 fps) ?
Quote from: Sane__ on July 02, 2013, 05:24:28 PM
Hey at that moment i don't have the chance to test it myself so i want to ask you, what is the highest possible resolution you can shoot raw at lest 3-4 seconds (i'm NOT interested with continious) at 23.976 (24 fps) ?
I can get 100 frames (4 seconds with a bit) at 1600x672 (2.39:1) @ 23.976 fps (in 640x480 canon mode).
Or I can get around 120 frames (5 seconds) at 1728x576 => 1728x960 (16:9) @ 23.976 fps (in 720p canon mode, with skipped lines, stretched mode)
So, if you just need a couple of secs - you can already shoot at almost full-res.
Thank You
Hello,
first many thanks for the new files.
Now although I have no more pink pictures, but there are still many images are overlapped to 50% with a noise.
I can record continuously 1088x488.
Currently I use the Canon Preview. - Is it because?
Thank you
Could anyone try recording a short footage in 1280x720 @ 15 fps --> 30 fps with Twixtor? Im really interested in motion smoothness.
QuoteCurrently I use the Canon Preview. - Is it because?
Use 640x480 w/ fps override or try killing LV altogether with hacked mode.
Im a 550d user about to buy a few t3i's and was wondering is raw further along then the 550d I know there was a memory problem with the 550d is this same problem here i remember someone saying the 500d had more memory then the 550d so im thinking the 600d maybe would have more memory then the 550d but i maybe mistaken
Quote from: 1% on July 03, 2013, 03:33:37 PM
Use 640x480 w/ fps override or try killing LV altogether with hacked mode.
Hello,
Unfortunately no success.
Of course I have not tried without LV.
What does that make for a meaning, or who will be working with it?
Greetings from Germany
Quote from: shawnwytch on July 06, 2013, 03:58:35 AM
Im a 550d user about to buy a few t3i's
If you want to film in RAW, don't buy a T3i / 600D. It is limited to 0.5 Megapixel resolutions at 24 frames per second since it has the same 21 Megabyte write speed issue like the T2i / 550D. So if you want to film with a 16:9 aspect ratio for more than a few seconds you have to use 960 X 540 which gives you a crop factor of almost 3 and looks worse than H.264.
If you don't want to film in RAW, get a T3i. It's as nice as the T2i but has the flipscreen.
Otherwise, get a used 50D, a T4i / 650D or a Blackmagic Pocket Cinema Camera.
T4i may be a bad option. I think the LV is permanently 720P squished unless you use crop mode.
The 650D has issues. Like the current 37 Megabyte/s write speed limit and the AF-Points in the image. But are you sure that it's always squished? I thought it would be better than the 600D because it has a better SD-Controller. But it is far away from being perfect and if it really has no option for unsquished images ...
Thats how EOS-M is and they are 90% similar.
The latest nightly build has raw modules in it. When I try loading them I am getting this error:
tcc: error:undefined symbol 'edmac_copy_rectangle_finish ... [E] failed to link modules
has anyone else with a 600d come across this problem and does anyone know what the fix for it is?
Make sure you replaced symbols file.
Forgive me for the stupid question but what am I replacing the symbol file with? I tried replacing it with the Six Thirty version symbol file and I am now getting a memory full error. Ive tried different versions of the symbol file from previous builds and no luck.
If it doesn't come with a symbol file, you can't really use it.
There is a 600d_102.sym file located in the modules folder of the latest build. I just thought I'd ask around to see if anyone else had this problem and had a fix for it. I only found one other post regarding this and it is still unanswered. I'll just stick with what I know works for now lol. Thanks for the quick response.
Hello,
with the niglybuild of 11 July, nothing has done
although the. sym file is from July 11th. :-(
For this, the rest is very stable.
With files from the last weekend I could not shoot.
delete raw_rec.mo in the modules-folder on your sd-card. Then linking should work without problems (and without raw-recording :) )
Edgar
I confirm having the same issue. And yes, removing the raw_rec module solves the error. But that does mean no raw recording as edgar pointed out.
That would mean to me - holiday without RAW. I cry! :-(
And it does not solve the problem!
Memory full message is still
Quote from: Wartburg-Entertainment on July 11, 2013, 07:41:17 PM
That would mean to me - holiday without RAW. I cry! :-(
And it does not solve the problem!
Memory full message is still
Disable autoload modules. Then the memory error should have gone.
If you want raw with your 600D, than use the latest build of TragicLantern2.0
Edgar
As a general comment, I've played with RAW at the max we can do, and it seems to me that using GOP and Slice control as in this post: http://www.magiclantern.fm/forum/index.php?topic=6913 (http://www.magiclantern.fm/forum/index.php?topic=6913) seems to produce the highest quality at a reasonable HD resolution (speaking as someone who needs HD) Thoughts, anyone?
Also great job with tragic lantern 1%, using GOP/Slice on a shoot of a festival this weekend :)
I have now created a map with me as of June 30.
Since all function modules ...
Do we need to wait and see where the journey (RAW) goes.
How do I record RAW stretched with skipped lines??? Can't google out anything relevant...
Hi guys!
Just have made a short test of H264 vs Raw vs CBR3.0x,
As you can see, there is a little or no diff of CBR3.0x with CBR1.0x, and plus what more interesting,
raw has noticeable noise (ISO 100!), don't know what is it, may be result of resize.
Can smbdy please explain me:
- 1. what is the difference between diff native resolutions (1920, 1280, 640) while shooting in raw? What to choose?
- 2. why somebody do resizes raw to some big resolution at first and then downsize it lower?
- 3. how to achieve live view working while shooting with latest build?
Thank you!
I think it's time to put a little FAQ in the first post...
Quote3. how to achieve live view working while shooting with latest build?
Use the canon preview.
1920 + 640 are the same, 1280 is 60P and stretched. 640 is a slightly smaller YUV buffer so a bit better for recording.
Wow, it almost looks like my posts are invisible... no answer again, but the guy who posted right after me got his... this isn't the first time too... The question seems to be on topic... Maybe I have a ghost account... :-\
What do you mean skipped lines? It can only copy a rectangle not every other line. 720P is hella skipped, try that with FPS override.
I'm using RAW + FPS Override to shoot timelapse video. Is there any chance to increase image resolution? 1728 with minimal fps of 0.15 produces 10-11 Mb/s, this means write speed is enough to shoot 1920 with 0.15fps. But I can't switch 1920 on.
is it possible to make interlaced it interlaced?
Quote from: Embosser on July 13, 2013, 06:27:05 AM
I'm using RAW + FPS Override to shoot timelapse video. Is there any chance to increase image resolution? 1728 with minimal fps of 0.15 produces 10-11 Mb/s, this means write speed is enough to shoot 1920 with 0.15fps. But I can't switch 1920 on.
In the 5X zoom mode you can use higher resolutions. But not in the 1X mode.
Quote from: Gimbaringo on July 13, 2013, 10:59:03 AM
is it possible to make interlaced it interlaced?
Why should you want that? It would probably look even worse than it already does ;)
You can use the 720p mode to get more lineskipping. But be carefull: The result may have more aliasing!
Quote from: far.in.out on July 12, 2013, 10:52:20 AM
How do I record RAW stretched with skipped lines??? Can't google out anything relevant...
Wow, it almost looks like my posts are invisible... no answer again, but the guy who posted right after me got his... this isn't the first time too... The question seems to be on topic... Maybe I have a ghost account... :-\
In the Canon menu you have to chose the 720p resolution. That will increase the line skipping from every third to every fith line and give you a nice squished image. I guess since that was mention a few thousand times already nobody answered your question earlier ;)
@ 1% the 650D's videos are just like the 600D's one: Squished in 720p mode but normal in 1080 and 640 mode. I asked it in the thread :D
THanks guys, no I get it... Good to have this option (720p skipped lines)...
Could you also be so kind and tell me what is the command line syntax for raw2dng (Windows)? I forgot it and can't find it anywhere...
The fact that it's not in the first post of the Raw2Dng topic makes me mad... I mean, come on guys! How can you post a cmd app and not specify the commands... Nvm, figured it out...
Please don't torture yourself with the command line. Just Drag & Drop your .raw files onto the RAW2DNG.exe and voilá! Everything starts automatically :) Everything else just makes the workflow even harder than it is already.
Quote from: vicnaum on July 12, 2013, 04:14:17 PM
I think it's time to put a little FAQ in the first post...
Yeah I've been meaning too, been super busy with moving and overtime at work, blah... I'll try to type one up in the next few days, feel free to submit questions.
Good day. Do you plan to in the future to increase the expansion At least up to 2500?I would like to use the RAW video for timelapse at 1 frame per second or 1 frame per 2 seconds
Quote from: Me
Can we make it interlaced?
Quote from: CFP on July 13, 2013, 01:01:40 PM
Why should you want that? It would probably look even worse than it already does ;)
You can use the 720p mode to get more lineskipping. But be carefull: The result may have more aliasing!
Because if we will change skipped lines every frame (tik-tak) may be we can achieve interlaced HD on this camera?
Why not? It will have 1920x540 each frame, and may be somehow we will fit into bandwidth limitation, but with interlaced HD raw video.
I was wondering if anyone knew how to make ML stop the creation of .WAV files? I have sound disabled under the canon menu and searched through the sound menu of ML extensively and didn't see a defnitive "off" option for sound recording. I'm probably just being dumb and have missed it or something. I also tried searching the ML forums before I posted because I didn't want to be "that guy" but I think I ended up being him anyway :-[. I appreciate any response and all the work that has and is going into this!
Thanks again and cheers! ;D
Hi. I tried to prepare my system canon 600D/t3i for recording raw footage on the camera. I did all the steps that are mentioned to get things done. i also instlled the modules of "Sixty Third".
Now all seems well, but when i try to record video even in 832x480 the video recordings stop automaticly or i get effects like in this video where i can´t move my camera around because the first taken frame is "Stuck" to the live view.
When i look into the DCIM Folder then there are some files. but when i try to convert them with raw2dng then i get an empty folder.
so a lot of problems and no idea to fix this.
here are the specs:
canon 3ti / 600D Firmware 1.0.2
ML 2.3
SD Card: Lexar 23 GB SDHC 200x10 & SanDIsk Extreme 45MB/s SDHC
here´s the youtube link to a video of the view finder with my phone: http://www.youtube.com/watch?v=zA67OkgQuF0&feature=c4-overview&list=UUoZglKsrC74PPKhrWFYep2g
Quote from: Gimbaringo on July 16, 2013, 05:16:58 PM
Because if we will change skipped lines every frame (tik-tak) may be we can achieve interlaced HD on this camera?
Why not? It will have 1920x540 each frame, and may be somehow we will fit into bandwidth limitation, but with interlaced HD raw video.
If there's a raw buffer of sufficient size available, it might be possible to memcpy with a stride double the frame width, which will effectively skip half the lines. By offsetting the start of the read by the width of one line, you can then alternate odd/even lines. Not sure if that is possible with EDMAC though, I have no idea how it works.
No suggestion should EVER end with, "...I have no idea how it works."
Quote from: Yuppa on July 20, 2013, 07:07:20 PM
No suggestion should EVER end with, "...I have no idea how it works."
It's not a suggestion, it's an explanation of the feasibility of a suggestion that was mentioned earlier.
Hey guys,
just installed the six thirty build on my cam and tried it out, was only able to record in 960x544 for like 700 frames with 23.976fps with my current card (Samsung Pro 16GB Class 10) and wanted to know how i can stretch/up-rezz (?) it to 720p and if the sandisk 95mb/s would really make much difference since I've read the 600D has some kind of bottleneck limiting the write speed to 21mb/s or so. reaching 1280x544 would be great.
thanks in advance :)
Quote from: CH10R on July 21, 2013, 02:02:04 PM
Hey guys,
just installed the six thirty build on my cam and tried it out, was only able to record in 960x544 for like 700 frames with 23.976fps with my current card (Samsung Pro 16GB Class 10) and wanted to know how i can stretch/up-rezz (?) it to 720p and if the sandisk 95mb/s would really make much difference since I've read the 600D has some kind of bottleneck limiting the write speed to 21mb/s or so. reaching 1280x544 would be great.
thanks in advance :)
The Sandisk 45mb or 95mb will get you higher resolutions. Even more so if you use FPS overide.
Getting Err 70 almost every time I use MagicZoom. Updated the ML nightly build to latest, with SixThirty, but same problem.
Crash Logs here: http://pastebin.com/gRMDBZU6
Quote from: dslrrookie on July 21, 2013, 03:35:42 PM
The Sandisk 45mb or 95mb will get you higher resolutions. Even more so if you use FPS overide.
Never used FPS override and therefore don't know what it does. Would that help with my current card as well?
I found adtg shutters:
http://www.filedropper.com/600dadtgshutter
The raw indicators don't play nice right now, esp with MZ. I have to tweak things a bit. This setup is working fine on digic V right now but on 600D has some issues.
Quote from: 1% on July 28, 2013, 07:07:31 PM
I found adtg shutters:
Could someone tell please what does it mean? I googled the forum and wiki, and only found out that these are some registers, that help with FPS Override... But what exactly should we test practically?
Shutter set via CMOS so it means you can have 1/whatever with fps override. Override should no longer limit you to 1/2000 or 1/110, things like that.
Playing with the raw overlays... wow, just raw histogram is 70-80% CPU.
I tested RAW video at 12.5fps at 1280:720.
Please tell me what you guys think or what i could do better, or email me at
[email protected]https://vimeo.com/71616275
Also the speed increase when going from 12.5 to 24 is there any way to get it back to normal without t looking choppy.
Quote from: Tmassa on August 03, 2013, 04:35:40 AM
I tested RAW video at 12.5fps at 1280:720.
Please tell me what you guys think or what i could do better, or email me at [email protected]
https://vimeo.com/71616275
Also the speed increase when going from 12.5 to 24 is there any way to get it back to normal without t looking choppy.
Kronos, Twixtor, or AE's Time Warp(based on Kronos).
Request for A1ex or 1%:
Would it be possible to allow Auto ETTR (still photos) to do the following:
1. Shutter triggered (via external camera trigger)
2. Auto ETTR reviews histogram and adjusts exposure (works as it currently does) WITHOUT LV enabled.
3. AUTOMATICALLY fire the next photo and so on until the exposure is accurate WITHOUT LV enabled.
4. Delete the photos with incorrect exposure, retain the final image correctly ETTR. This might be asking too much, but it's worth a shot.
I'm a time-lapse photographer running a solar-powered D-SLR rig for long-term landscape time-lapses. You can learn more about me and what I'm doing here: http://blog.planet5d.com/2013/02/making-a-diy-solar-camera-for-multi-month-timelapses-behind-the-scenes-on-mountains-in-motion/ (http://blog.planet5d.com/2013/02/making-a-diy-solar-camera-for-multi-month-timelapses-behind-the-scenes-on-mountains-in-motion/)
I just got a permit at a local state park to capture 4 months of fall foliage change AND fluctuating water levels on a local river. The main subject of my shot is a small waterfall. I'm currently shooting on a 600D with a custom intervalometer in Av mode. All values are locked except shutter speed and ISO (100-800 Limit).
OK... so why does all this matter in regards to Auto ETTR?
I want to use a 6-stop ND filter to ensure silky smooth water movement in all my shots throughout the day (the unit doesn't shoot after dark). As most of you know, in-camera metering is worthless AFTER applying such a dark ND to the lens. As a result, Auto Av metering is not possible to use if I want to run this unattended, multi-month time-lapse with a 6-stop ND filter for silky water exposures.
I have performed tests running the [600D] SixThirty.zip release (the latest posted by 1% for 600D) and Auto ETTR in photo mode plays extremely nice with the ND filter because it's obviously only looking at the histogram. The downside is that I have to manually shoot the subsequent photos after the histogram is reviewed by ML Auto ETTR which is not possible when the camera is unattended. I can only trigger it once per sequence via my custom, external intervalometer unit. If ML could know to continue shooting the scene until the histogram value offers a correct exposure, that would solve the problem.
Auto Snap ALMOST works as-is, but I cannot run the camera in LV due to battery limits on the unattended solar configuration. Technically, I COULD run LV with auto-off enabled after 30 seconds from the photo being shot (camera wake provided by my intervalometer controller) but that will definitely be wasting unnecessary power.
Secondary to the above request, it would be incredible if the incorrectly exposed images from the auto ETTR calculations could be auto deleted after they are shot and examined by the ML Auto ETTR algorithm to free up space on the 128GB SD card since I'm shooting RAW. I can only return to the camera every 3-4 weeks to dump the card and free up space. I'll find a way to work around this space limit if it's too much to implement.
Thanks for taking the time to consider my request. It sure would make for an interesting long-term ML stability test. I should add that I'm doing these long term time-lapses to eventually share with others online for free, this is not a client job that I'm being paid for.
Auto Snap should work without LV. Deleting pics is not quite clean (can give err70).
Maybe a mod can move this post, since it's offtopic.
Quote from: a1ex on August 09, 2013, 12:24:46 AM
Auto Snap should work without LV. Deleting pics is not quite clean (can give err70).
Maybe a mod can move this post, since it's offtopic.
A1ex, I'm sorry for posting here... figured it was a somewhat relevant thread since Auto ETTR is only available in the RAW VIDEO nightly builds.
Just sorted the problem. The camera was set to continuous shooting which breaks the ability for ML to continue shooting. Returned to single shooting mode and it is now working.
Thanks for the additional clarification regarding the deleting err70 issues. Not worth risking that.
It hasn't err70'd on me deleting photos yet but some cameras have not shown the free space until on/off or mode change.
Try looking at the photos after you delete them e.g. from file browser. Though the exact behavior is probably camera-specific (don't remember where I tried this, probably 550D).
The file catalog isn't updated, so the camera is still looking for the photos and can no longer find them.
edit: 5D3 is handling it well, just Cannot playback image, no crash.
hey guys i just installed on my friend's camera and i couldn't make it work
it keep looking for the modules but they don't show.
i first installed the stable ML, than the Nightly and last the SixThirty package.
can someone point me to a step by step to see if i did something wrong?
in my 60d is working as it should
Is your friend's camera a 600d/T3i?
I just now put it on my T3i with no problems: installed latest ML on newly camera-formatted card, placed the SIXTHIRTY stuff where it should go, and it is working fine. I did NOT install the "Nightly" update thing.
I was messing around with the bit rate on the ml settings and bumped it up to 1.4X now if i am getting this right it will give me 11.2 bit video and not 8 bit video.
https://vimeo.com/72168772
Now this might not be raw video but it seems close to it if you use cinestyle and HDR. Also you can record at full hd no problem.
I just thought i would post this because it might not be RAW video but it is the best compromise of H.264 and RAW video.
I hope this helps anyone and any feed back would be great.
bit-depth has nothing to do with bit-rate
Quote from: vicnaum on August 12, 2013, 08:57:36 AM
bit-depth has nothing to do with bit-rate
Oh then what does the Bit Rate option at the top of the video menu do exactly?
The bitrate option applies only to regular h.264 video recording.
If anyone would like too see how the H.264 with 1.4X Bit Rate (CBR) and Cinestyle compares to the RAW video, here is the video.
https://vimeo.com/72230514
My video showcasing RAW's dynamic range in natural light. I think the difference is the gradation and smooth roll-off of highlights that keep me shooting RAW compared to H.264. But it could be a perception thing too.
Quote from: clkvang on August 13, 2013, 05:20:03 AM
My video showcasing RAW's dynamic range in natural light. I think the difference is the gradation and smooth roll-off of highlights that keep me shooting RAW compared to H.264. But it could be a perception thing too.
What settings did you use for this?
That's a really nice looking video! Was the close up on the cook's face done on 3x zoom?
Quote from: clkvang on August 13, 2013, 05:20:03 AM
My video showcasing RAW's dynamic range in natural light. I think the difference is the gradation and smooth roll-off of highlights that keep me shooting RAW compared to H.264. But it could be a perception thing too.
I shot this using 640 mode using 1280 x 544, but shot at 22 FPS. No 3x mode since I was using a 50mm and it was too tight. I used a Pentax 50mm f/4 Macro for the close ups. All natural light and no CC just white balanced.
@ 1% - was A1ex's buffering raw_rec.mo applied to the SixThirty build? Just wondering because I stumbled upon the thread it looked like in best case scenario, frames captured were doubled.
Using RAW video at 1152:624 at 16frps i was able to capture this.
https://vimeo.com/72460366
Quote from: Tmassa on August 16, 2013, 08:59:00 AM
Using RAW video at 1152:624 at 16frps i was able to capture this.
https://vimeo.com/72460366
It looks absolutely terrible...
Quote from: Tmassa on August 16, 2013, 08:59:00 AM
Using RAW video at 1152:624 at 16frps i was able to capture this.
https://vimeo.com/72460366
You need to use a tri-pod. Most of it was out of focus with exception of your foot. Otherwise, have fun with the raw stuff.
Let's keep the video posts to the video section, please (unless it's for examples of glitches, errors in the program, etc.).
Shot a bunch of raw footage yesterday and it all came out damn nice, the dynamic range alone makes me love it more and more, even with the complex workflow. The ability to over-expose is well worth it.
Dual Iso is now available for 600D, the link was in the dual iso thread but it's dead now. Soon as it's back up I'll update the first post of this thread with the link.
Quote from: N/A on September 01, 2013, 08:18:38 AM
Dual Iso is now available for 600D, the link was in the dual iso thread but it's dead now. Soon as it's back up I'll update the first post of this thread with the link.
Could you please tell more about this? I've searched the last few pages of dual-iso thread, but can't find much info about 600D. What's available? Only photo, or video too? What are the drawbacks (there must be some because 600D isn't as good as 5dmk3, right?), etc...
Quote from: vicnaum on September 02, 2013, 12:47:02 PM
Could you please tell more about this? I've searched the last few pages of dual-iso thread, but can't find much info about 600D. What's available? Only photo, or video too? What are the drawbacks (there must be some because 600D isn't as good as 5dmk3, right?), etc...
I tried the feature on the same day 1% released it some weeks ago. It works in LiveView, Photo Mode and even with videos if you film in RAW.
It's a great feature and increases the dynamic range by up to 3 steps thanks to the 600D's native ISO 3200.
There are no limitations on the 600D, it is as good as the 5D Mark III. Well, since the RAW videos of the 600D have really low resolutions using Dual-ISO with videos will probably give you many artefacts. I tried it only two times and the result looked very bad. But A1ex made much progress since that day and maybe he could improve the quality ...
I would have to try it with one of the newer CR2HDR and RAW2DNG versions.
https://www.dropbox.com/s/wh68tmxe0dt1xyn/%5B600D%5D%20DualIso.zip
I've done a few pics/vids with Dual Iso but haven't processed them yet, looks promising though.
Just signed to these forums. Long live MagicLantern, you people are the best!
Does there exist a possibility of reading the raw data directly from the camera RAM and circumvent the memory card bottleneck? I know i can read preview jpegs at 1054x704 resolution continuously from the RAM through the usb connection (very LQ jpegs at least). Maybe it's possible to trick the camera into sending other data than the preview jpegs from the RAM thru the usb connection?
USB is just as slow as the SD card. Can't even do that JPEG at much more than 20fps.
What if you wrote simultaneously to the card and thru the usb connection? Maybe this is impossible.
Anyway thanks for a quick reply, and all the wonderfull upgrades to the 600D.
Tested out the newest nightly but still had sRaw set from the TL Dual Iso build and had 107 MB buffer memory, most I've ever gotten. Interesting...
Yes, same thing here. 107 Megabyte buffer with the current Nightly and the 'Pic Quality' still set to 'SRAW'.
But when I replaced the Nightly's 'autoexec.bin' with the 'autoexec.bin' from the Tragic Lantern 'SixThirty' build it was 103 Megabytes again.
Maybe there's even more space left ... Or is it a bug?
By the way, which raw_rec version is the best? The 'SixThirty' version or the version from the current nightly build?
Or is there a version I'm not aware of because 1% had to upload it somewhere else again?
Quote from: CFP on September 05, 2013, 09:39:13 PM
By the way, which raw_rec version is the best? The 'SixThirty' version or the version from the current nightly build?
Or is there a version I'm not aware of because 1% had to upload it somewhere else again?
I'm still getting the best results with the SixThirty build as far as clean video. I tried the latest nightly again today and back to getting pink frames again.
I'm beginning to think I'm doing something wrong with the nightlies. One day I get good results, the next not so good.
QuoteMaybe there's even more space left ... Or is it a bug?
I updated the sources but didn't compile a latest yet. FYI, you get 103 vs 107 because of different amounts of "backup" memory being allocated. I'll check in main, maybe less backup is being allocated or something changed and didn't merge. 4MB shouldn't make much difference one way or another, its like 2-3 frames at best.
Anyone else trying Dual Iso video on the 600D? I'm getting mixed results, with regular "line-skipping" raw video the (debayering?) artifacts are horrendous. With 5x "no line-skipping", its a bit better but still plenty of bad pixel areas. I noticed when I convert the dng's to CR2 and use the latest CR2HDR for OSX to save them for editing, the .txt file says this-
1 image files updated
Input file : M14-1725_C0000_00000.CR2
Canon EOS 5D Mark III detected
Full size : 1280 x 512
Active area : 1280 x 512
White level : 12500
Black subtract didn't work
ISO pattern : BddB RGGB
Noise levels : 8.00 8.00 8.00 8.00 (14-bit)
Estimating ISO difference...
ISO difference : 2.00 EV (400)
Black delta : 10.25
Interpolation : mean23-chroma5x5-alias
Dynamic range : 10.35 (+) 10.35 => 12.35 EV (in theory)
Matching brightness...
Looking for hot/cold pixels...
Hot pixels : 23
Full-res reconstruction...
ISO overlap : 5.4 EV (approx)
Half-res blending...
Chroma filtering...
Building alias map...
Filtering alias map...
Smoothing alias map...
Noise level : 8.00 (16-bit), ideally 8.00
Dynamic range : 12.35 EV (cooked)
Output file : M14-1725_C0000_00000.DNG
I convert the raw files into CDNG with RawMagic, which indicates that the camera was a 600D, but I'm assuming CR2HDR is automatically reading them as MKIII pictures? Here's an example frame, Dual Iso 100/400, 5x zoom, 1280x512 rez. This frame was rendered from LR but I'm getting the same spots with ACR in AE. I was holding the camera so it's somewhat blurry-
(http://s15.postimg.org/nws4sgw7b/M14_1725_C0000_00150.jpg) (http://postimg.org/image/nws4sgw7b/)
Quote from: N/A on September 15, 2013, 08:04:17 AM
Anyone else trying Dual Iso video on the 600D?
Where can I get the build with Dual Iso? TragicLatern has only july SixThirty download.
Check the first post of this thread
Quote from: N/A on September 15, 2013, 08:04:17 AM
...
I convert the raw files into CDNG with RawMagic, which indicates that the camera was a 600D, but I'm assuming CR2HDR is automatically reading them as MKIII pictures?
...
Camera Model, Canon EOS 5D Mark III, is hardcoded by RAWMagic.
Quote from: vicnaum on September 15, 2013, 09:28:27 AM
Where can I get the build with Dual Iso? TragicLatern has only july SixThirty download.
Or download very latest Nightly :)
RAW Video is so exciting. It's high resolution VIDEO.
1728 x 736 / 23.976p
EF-S18-55mm F3.5-5.6
Sandisk Extreme Pro SD card
Quote from: oreve21 on September 16, 2013, 06:14:33 PM
RAW Video is so exciting. It's high resolution VIDEO.
1728 x 736 / 23.976p
EF-S18-55mm F3.5-5.6
Sandisk Extreme Pro SD card
Is this with 600d? How did you get resolution this high?
Quote from: Sane__ on September 17, 2013, 06:35:37 PM
Is this with 600d? How did you get resolution this high?
I'm sure it was the 600D ... if you notice, each shot is 2-3 seconds ... easily obtained at that resolution, especially if you use Tragic Lantern.
I have a very very stupid question. I already have Magic Lantern 2.3 but my card reader is broken and i'm in a place where i can't buy another.Is it possible to install tragic lantern without a card reader?
Quote from: Sane__ on September 17, 2013, 10:26:23 PM
I have a very very stupid question. I already have Magic Lantern 2.3 but my card reader is broken and i'm in a place where i can't buy another.Is it possible to install tragic lantern without a card reader?
maybe connect your camera (with SD card inside) via USB cable to your PC? Just an idea, idk if it works.
Quote from: Jonit on September 19, 2013, 02:53:53 PM
maybe connect your camera (with SD card inside) via USB cable to your PC? Just an idea, idk if it works.
This is not an idea :) This is the first thought everyone would think of. If you don't know if it works it's bad idea to give an advice
New build released guys ;D
Its real nice... very nice upgrade indeed, i usually use raw video on my mkii but this lil beauty is doing good, im getting continuos 1084 i think it is by at 2:1 ratio.
Quote from: Doyle4 on September 23, 2013, 04:07:46 PM
Its real nice... very nice upgrade indeed, i usually use raw video on my mkii but this lil beauty is doing good, im getting continuos 1084 i think it is by at 2:1 ratio.
Same here, so far no pink frames. Keep your fingers crossed. Love the new look.
i just upscaled a dng to 5k just too see what it looks like... wow.... its pretty damn clean.
yeah.. new look is real nice.
Well, I tested all the functions that I use on a regular basis and all seems to be functioning fine. Raw works well, with very few if any pink frames. Haven't tested the dual iso or auto ettr, but don't really use those features.
Will play with it some more before using on a commercial shoot, but I'm liking what I see.
Very clean, professional looking layout.
cant seem to get dual iso video working, i put it into movie mode, enable raw video and dual iso says needs to be RAW to use this..
Any ideas anyone?
Use movie mode, photo mode is blocked for raw video on 600D as there appears to be no benefit.
Thanks that sorted it, filming on 600D is different from mkii... keep forgetting the 600D has a movie dial on it.
To convert dual iso dng's do i do this:
Convert the raw to dng's, convert the dng's using adobe dngconverter, change dng to cr2, convert, rename cr2 back to dng?
Cheers.
Convert them with cr2hdr after that you can assemble an image sequence in AE or whatever else... but careful, they convert in place.
dragged a dng on and said wrong file type, changed the extension name to CR2 and converted.. footage looked 8bit though.. hmmm,
Update: My fault... didnt expose properly.
Couple of us getting pink frames in silent picture mode.
http://www.magiclantern.fm/forum/index.php?topic=8452.0
I noticed more pink frames while recording raw with several modules enabled. Very few, if any with just raw.mo on.
Otherwise, great build !
I had the same problem awhile back on my mkii, too many modules loaded and caused pink frames, iv disabled all modules except silent and still get pink frames, a1ex did say though "silent pic code probably needs waiting until the next LV frame, as ETTR already does: auto_ettr_wait_lv_frames should probably be moved in the core and used here too." so it could be something in the module code causing, not sure as i dont understand coding.
But like you say, nice build other than that :)
Show us some samples with the newest build :)
Quote from: Sane__ on September 24, 2013, 06:48:59 PM
Show us some samples with the newest build :)
What you mean dude? raw video? if so.. its still the same, just more user friendly and get extra frames :)
Quote from: Doyle4 on September 24, 2013, 07:38:54 PM
What you mean dude? raw video? if so.. its still the same, just more user friendly and get extra frames :)
Hey, thanks , can you tell me what is the maximum resolution and maximum seconds you can get at 24 fps with the newest build? :)
theres big resolutions (not 4k haha) but the 600D is limited to 21mb write, till this is hacked were stuck at that, i shot at 1024x512 2:1 continuos, next one up i didnt take notice but it didnt get continuos. :)
Loving how the new font looks, Magic Lantern has evolved so much in the last year that I'm still having trouble wrapping my mind around all the new possibilities I have with a 2 yr old camera.
So what are the differences now in this newest TL2.0 version and the nightly, besides the sRaw hack?
Quote from: a.d. on September 15, 2013, 01:27:54 PM
Camera Model, Canon EOS 5D Mark III, is hardcoded by RAWMagic.
Finally got around to messing with the Dual Iso Video on 600D. When I convert the raw file with RawMagic, it's indicating that these .dng's, renamed to .CR2 to be compatible with the latest OSX_cr2hdr_app, saves as 600D. OSX preview sees them as 600D pictures, but Cr2hdr is still recognizing them as MkIII shots, though, seen here in the screen shot-
(http://s22.postimg.org/dtextvhld/Screen_Shot_2013_09_25_at_12_11_21_AM.png)
Here's the .dng, converted straight from RawMagic-
https://www.dropbox.com/s/af3mc67aulrj2sl/M15-0939_C0000_00000.dng
its reversed engineered from the mkiii, so its been tricked.. dont worry :)
Also for batch changing extensions i use a program called NameChanger, its fast too.
... only that colors may not be quite right, because 600D has a different color matrix than 5D3 ;)
i noticed a tad bit of green but using ACR and funny enough Remove Chromatic Aberration did a good job of removing some of it too.
I've just checked, cr2hdr bridge supports Canon EOS 600D. I think to minimize failure mode: You should shot only a DUAL ISO Photo (without RAWMagic) and convert it.
btw
Your RAWMagic DNG EXIF shows no Camera Model.
I'm not sure it knows what is what for dual raw video. I don't think 600D is the only one.
Quote from: a.d. on September 25, 2013, 05:16:42 PM
I've just checked, cr2hdr bridge supports Canon EOS 600D. I think to minimize failure mode: You should shot only a DUAL ISO Photo (without RAWMagic) and convert it.
btw
Your RAWMagic DNG EXIF shows no Camera Model.
5x converts a little better since there's no line skipping but the crop factor from raw AND 5x on our sd cameras make it extremely difficult to get tight shots, but might come in handy for something like wildlife footage.
Remember there is real crop mode too.
Yup, been testing out max bitrate/GOP 1 on 720p h264 to see if I can use it with raw clips since we can get a solid 18 secs of 1280x512 and continuous two rez's smaller, upscaled to match. Maybe with a VisionColor ps and their new Osiris luts, who knows.
Wrong post but iv message the creator of Autoexposure and he's unsure why its not working on latest nightly for 600D, could someone with coding skills take a look and if possible make it work on latest nightly please? not been working for while now, the module from NewMem is apparently old and wont load.
Thanks very much in advance!
This thread is so dead... Just delete it and stop our miserable agony called "600d Raw" please...
Quote from: Sane__ on October 05, 2013, 06:18:32 AM
This thread is so dead... Just delete it and stop our miserable agony called "600d Raw" please...
Excuse me, what's exactly wrong with 600D raw? )))
Its not "dead" check the nightly's and you will see how far the 600D has come, this thread is just for RAW and the builds here are stable code taken from nightly's.
I really like the stuff 1% has on 'his' site - newmem.
Will nightly's disturb it?
rick
1% is stable stuff taken from nightly, nightlys are always getting update but bits can unstable.
Quote from: Doyle4 on October 05, 2013, 05:33:48 PM
1% is stable stuff taken from nightly, nightlys are always getting update but bits can unstable.
So if I want to retain as much as possible, do I just overwrite the raw_rec module?
with nightly's you will need to overwrite everything.
I use nightlys on my 600D as its my play camera, i have a mkii for main stuff, id say its personal choice, if something is up with something in a nightly build like autoexposure is atm then if i need i use 1%'s build as it works and the build is stable, personal choice at the end of the day and what you want to be doing.
Hello there :)
I haven't installed the Night Build with RAW yet because I'd like to know some information first, such as:
• Will I be able to record at 60 fps?
I'm used to make a free running videos where is a lot of frames needed for the fluent movement
• What card would you recommend me to buy?
Thanks for answers, I'm still deciding if it's worth it :)
60FPS is waaaay too much data for 20MB/s
I've been shooting h264, qscale -16, flush rate 3 and gop 1 lately, and even with audio off 60p still fills the buffer sometimes. So yeah, we'll never see 60p raw lol. BUT... It's still nice to have raw video for those situations where you absolutely NEED the dynamic range and you can sacrifice some resolution.
The new build is awesome!
Raw on the 600D is very useful, big thanks to 1% and everyone involved!
Small issues I found:
- Framing rectangles in live view are a bit off, slightly too big and the bottom too low, quick example:
https://dl.dropboxusercontent.com/u/12268239/ML-raw-framing-rectangles.jpg
- Options Preview 'HaCKeD' and 'Hacked No Prev' don't seem to work (or maybe I overlooked something?)
are pink dots (or other glitch) often spotted on 600D? I mean how often do they appear? I wish to shoot a short movie with 600D raw, could it be possible? thx A LOT ( :) )!
Quote from: Brawl on October 12, 2013, 04:53:11 PM
are pink dots (or other glitch) often spotted on 600D? I mean how often do they appear? I wish to shoot a short movie with 600D raw, could it be possible? thx A LOT ( :) )!
I personally haven't experienced it a lot, not at all in fact. I recently shot a post-apocalyptic short film in 1408x528 RAW on the 600D and out of the 70 or so shots there was one shot that had a pink first frame, which is easily removed since the clapboard was in the frame so I didn't even need it. I had no aliasing or moire issues either. You have to practice using RAW a lot, test a lot of footage, test your lenses, test what duration works for you, test magic lantern settings, test ISO's, etc.
Quote from: MrMehh on October 13, 2013, 01:10:18 PM
I personally haven't experienced it a lot, not at all in fact. I recently shot a post-apocalyptic short film in 1408x528 RAW on the 600D and out of the 70 or so shots there was one shot that had a pink first frame, which is easily removed since the clapboard was in the frame so I didn't even need it. I had no aliasing or moire issues either. You have to practice using RAW a lot, test a lot of footage, test your lenses, test what duration works for you, test magic lantern settings, test ISO's, etc.
Thank you MrMehh, I was looking here for an answer very often since I asked my question. I really wish to say thanks to your help. Could I ask you some general advice/tips on the 600D raw shooting please? and which sd card do you use?
no aliasing and moire were obtained shooting at 5x? or with which camera settings?
thanks a lot again! have a good day! :)
Some slight issues we are having with with raw shooting;
(http://i43.tinypic.com/9icsbo.jpg)
Notice the Moire on the hands, and the texture " grain like " on the img. "the vertical lines.
(http://i43.tinypic.com/sbujhl.jpg)
also the magenta frames at random.
Res: 1408 x 352
Aspect: 2.39.1
Shutter: 1/48 186 (about)
after conversion we run through Photoshop saving out to jpg. > then Adobe Pr > up res to 1920 x 810
We our unable to run the dng's through DaVinci because of the dead pixel issue.
I wonder if that is caused by the 5DIII vertical banding correction. Its applied to every camera DNG because the camera name is often incorrect. I have to make a raw2dng that excludes this and then it can be tested.
Here it is:
http://www.filedropper.com/raw2dng-nostripe
Does it help or hurt?
Is this for PC? having trouble opening with wine on my Mac ?
Thank you
Yea, its PC. You have to drop files on it or use the command line. I don't have anything with OSX installed.
Ok thats cool, I'll get back with the results.
Thanks
Quote from: Brawl on October 13, 2013, 03:39:29 PM
Thank you MrMehh, I was looking here for an answer very often since I asked my question. I really wish to say thanks to your help. Could I ask you some general advice/tips on the 600D raw shooting please? and which sd card do you use?
no aliasing and moire were obtained shooting at 5x? or with which camera settings?
thanks a lot again! have a good day! :)
I used SanDisk Extreme SDHC 45mb/s cards, 16GB & 32GB. The 90mb/s cards don't make a difference because of the internal write limit of 20mb/s, although it will help copying the files from the card onto the computer via internal card reader or USB3/thunderbolt readers. But I wouldn't go below 45mb/s either just to be sure.
Some tips would be to prepare yourself, know the ins and outs of using RAW, what settings you use, etc. What I tend to do is use ND-filters so I can open up my lenses all the way which purposefully creates a softer image (depending on the quality of lenses you use, I use vintage lenses) which will help a little in getting rid of moire and aliasing. Just as with H264, the lower the ISO, the cleaner, sharper and better your image will look. Also make sure you've got the knowledge and experience of handling the post process (conversion, proxies, grading, editing).
I convert using raw2cdng, note the c which stands for CinemaDNG. Those work natively with DaVinci Resolve which you can use to grade and create proxies. The latest version of Resolve doesn't have any issues with pink dots or dead pixels anymore. My footage looks absolutely wonderful in it. If you have any more questions, feel free to ask :) Maybe other people can learn a thing or two as well.
Settings I used:
Audio OFF (We used a Zoom H4n for external audio)
Canon menu --> Video mode --> 640x480 (30p)
FPS override to 23.976 fps
Global Draw OFF (no ML histrograms, camera settings, waveforms, focus peaking or zebras, etc)
RAW Video: 1408x528 (2,67:1), buffer warm-up 32mb, no extra hacks, canon preview mode (~240-250 frames)
What I also found was that oddly enough official Canon batteries work better. The first part of the shoot I used my original battery which gave me the full 10 seconds I needed but in the middle I changed battery to a cheaper alternative and it all of a sudden couldn't record longer than 100 frames. I don't know if that was my fault or it not being warmed up or just coincidence, but I grabbed the official battery from our BTS camera.
(http://resize.like.cz/images/90_181_36_175_17-10-13-05-53-27_1382025207IMAG0660_resize.jpg)
Have a question. Was there that white cropping border showing what is going to be in the frame since the very beginning? Or did that change in some version? How can I stretch it up on the full screen? The screen is small on itself, not to mention this additional cropping frame and only time when its not showing is when I turn off raw recording.
PS: first time writing on ML forum, but I am a long time reader and fan :).
You have done a lot of amazing work guys!
Quote from: MrMehh on October 14, 2013, 05:47:36 PM
I used SanDisk Extreme SDHC 45mb/s cards, 16GB & 32GB. The 90mb/s cards don't make a difference because of the internal write limit of 20mb/s, although it will help copying the files from the card onto the computer via internal card reader or USB3/thunderbolt readers. But I wouldn't go below 45mb/s either just to be sure.
Some tips would be to prepare yourself, know the ins and outs of using RAW, what settings you use, etc. What I tend to do is use ND-filters so I can open up my lenses all the way which purposefully creates a softer image (depending on the quality of lenses you use, I use vintage lenses) which will help a little in getting rid of moire and aliasing. Just as with H264, the lower the ISO, the cleaner, sharper and better your image will look. Also make sure you've got the knowledge and experience of handling the post process (conversion, proxies, grading, editing).
I convert using raw2cdng, note the c which stands for CinemaDNG. Those work natively with DaVinci Resolve which you can use to grade and create proxies. The latest version of Resolve doesn't have any issues with pink dots or dead pixels anymore. My footage looks absolutely wonderful in it. If you have any more questions, feel free to ask :) Maybe other people can learn a thing or two as well.
Settings I used:
Audio OFF (We used a Zoom H4n for external audio)
Canon menu --> Video mode --> 640x480 (30p)
FPS override to 23.976 fps
Global Draw OFF (no ML histrograms, camera settings, waveforms, focus peaking or zebras, etc)
RAW Video: 1408x528 (2,67:1), buffer warm-up 32mb, no extra hacks, canon preview mode (~240-250 frames)
What I also found was that oddly enough official Canon batteries work better. The first part of the shoot I used my original battery which gave me the full 10 seconds I needed but in the middle I changed battery to a cheaper alternative and it all of a sudden couldn't record longer than 100 frames. I don't know if that was my fault or it not being warmed up or just coincidence, but I grabbed the official battery from our BTS camera.
you are really kind :)
thank you my fiend. I wish to ask you one last advice if it's possible. I'll try to explain in short, have been passed some years since I started to
economize my money to buy a DSLR to make video for cinema. since Magic Lantern has RAW I lost my plans about what to buy, because anything I knew about DSLR body, ISO noise, models, were lost. Now I wanted RAW and my research started from scratch again.
I wish to buy the 600D because it's relatively affordable. And I can use the rest of my money for video tripod, redhead lights, mics. But I have not understand how nice is the quality of the RAW video when it's done and is upscaled to 1080p.
I will try to produce short films and I'll try to show my shots in movie theaters for short film festivals. I believe that sub HD is not a problem because the detail of the RAW is very good also in Sub HD. But I have not understand if we can notice pixel when watching those videos.
how good it's for example 960x540 upscaled to 1080p? can you notice pixel like this image at the edge of the shapes?
I have got the sample from youtube (600D raw video).
(http://s11.postimg.org/3jpe3amvn/image.png)
those pixels moves and can generate distraction to the people who see them.
source: http://www.youtube.com/watch?v=97hdf0lzEbQ
thanks again for help.
Quote from: Brawl on October 17, 2013, 08:58:07 PM
you are really kind :)
thank you my fiend. I wish to ask you one last advice if it's possible. I'll try to explain in short, have been passed some years since I started to
economize my money to buy a DSLR to make video for cinema. since Magic Lantern has RAW I lost my plans about what to buy, because anything I knew about DSLR body, ISO noise, models, were lost. Now I wanted RAW and my research started from scratch again.
I wish to buy the 600D because it's relatively affordable. And I can use the rest of my money for video tripod, redhead lights, mics. But I have not understand how nice is the quality of the RAW video when it's done and is upscaled to 1080p.
I will try to produce short films and I'll try to show my shots in movie theaters for short film festivals. I believe that sub HD is not a problem because the detail of the RAW is very good also in Sub HD. But I have not understand if we can notice pixel when watching those videos.
how good it's for example 960x540 upscaled to 1080p? can you notice pixel like this image at the edge of the shapes?
I have got the sample from youtube (600D raw video).
(http://s11.postimg.org/3jpe3amvn/image.png)
those pixels moves and can generate distraction to the people who see them.
source: http://www.youtube.com/watch?v=97hdf0lzEbQ
thanks again for help.
That was an extreme upscale and don't recommend it for production use. Also, alot of the artifacting is probably due to youtube compression. The original looks much cleaner.
Quote from: 1% on October 13, 2013, 08:56:26 PM
I wonder if that is caused by the 5DIII vertical banding correction. Its applied to every camera DNG because the camera name is often incorrect. I have to make a raw2dng that excludes this and then it can be tested.
Here it is:
http://www.filedropper.com/raw2dng-nostripe
Does it help or hurt?
Hi 1% thanks for all the work you've done.
The link to the raw2dng-nostripe is no longer working. Would love to try it out if it's still available.
Thanks.
Quote from: ultramar on October 18, 2013, 12:04:29 AM
Hi 1% thanks for all the work you've done.
The link to the raw2dng-nostripe is no longer working. Would love to try it out if it's still available.
Thanks.
should be this
http://www.sendspace.com/file/q1r8zm
Quote from: dslrrookie on October 17, 2013, 10:14:00 PM
That was an extreme upscale and don't recommend it for production use. Also, alot of the artifacting is probably due to youtube compression. The original looks much cleaner.
please can you give me some example, something to see with my eyes shot with the 600D? thank you if it's possible.
Quote from: Brawl on October 18, 2013, 12:19:39 AM
please can you give me some example, something to see with my eyes shot with the 600D? thank you if it's possible.
Don't know why you want them, but here are some screen grabs.
Original 960x540 lossless .avi from AE
(http://linkgen.net/1.jpg)
Upscaled to 1080p using Magic Bullet Instant HD
(http://linkgen.net/1b.jpg)
Quote from: dslrrookie on October 18, 2013, 12:33:39 AM
Don't know why you want them, but here are some screen grabs.
Original 960x540 lossless .avi from AE
Upscaled to 1080p using Magic Bullet Instant HD
I'm confused sorry, where did you get those pics? Is you the author of this youtube video (the music is awesome remember me the movie "Paris, Texas") ? http://www.youtube.com/watch?v=97hdf0lzEbQ
Quote from: Brawl on October 18, 2013, 12:53:48 AM
I'm confused sorry, where did you get those pics? Is you the author of this youtube video (the music is awesome remember me the movie "Paris, Texas") ? http://www.youtube.com/watch?v=97hdf0lzEbQ
Yes, that was my video. I got the pics from the orginal files.
Quote from: dslrrookie on October 18, 2013, 01:41:02 AM
Yes, that was my video. I got the pics from the orginal files.
thanks, what a coincidence! :) could I ask you a big favor? could you give me the original DNG so that I can try to make some experiment with it? today is also my birthday would be a great gift for me! :)
thanks a lot if it is possible! :)
Quote from: Brawl on October 18, 2013, 06:10:37 PM
thanks, what a coincidence! :) could I ask you a big favor? could you give me the original DNG so that I can try to make some experiment with it? today is also my birthday would be a great gift for me! :)
thanks a lot if it is possible! :)
Sorry, this was just a test project and the original .dng's were deleted. Happy Birthday!
Quote from: dslrrookie on October 18, 2013, 06:30:17 PM
Sorry, this was just a test project and the original .dng's were deleted. Happy Birthday!
thanks!! :)
if you have anything else shot at that resolution with the 600D that would be great anyway, I just need to test how does it upscale. or if you can describe it to me. you said that the original uncompressed file were way better. and on that still picture of the video upscaled with magic bullet that you posted it looks without any sort of pixel at the edge of the shapes. can we definitely say that if the upscaling work is well done we get no pixel at the edge of the shapes? also good for cinema projections/professional works? thanks -a lot- have a nice evening!!! I'll buy the 600D this week it works (gift to myself)!! :)
Here's two frames from the short film I was talking about earlier. First one's the source file (RAW --> raw2cdng.exe). The second one is a processed one, upscaled to 1080p. That's roughly the color palette i'll be using to grade the film. Click on the picture so see the full resolution ones.
Shot at 100ISO, Hanimex 28mm f/2.8 @ f/5.6 or f/8 (can't remember), 1408x528 (2,67:1, max 240-250 frames)
Source
(http://imageshack.us/a/img443/2201/5lz.png) (http://imageshack.us/a/img405/7497/aa22.png)
Processed
(http://imageshack.us/a/img689/8428/aubr.png) (http://imageshack.us/a/img854/9208/frt7.png)
I think it looks great and the image upscales very well. But I have no shame in admitting my cinescope fetish and I love these widescreen images, which allow me to record longer at higher resolutions. Now obviously that's not always an option. The higher the aspect ratio the lower resolution you're gonna need to use.
Quote from: MrMehh on October 18, 2013, 09:53:30 PM
Here's two frames from the short film I was talking about earlier. First one's the source file (RAW --> raw2cdng.exe). The second one is a processed one, upscaled to 1080p. That's roughly the color palette i'll be using to grade the film. Click on the picture so see the full resolution ones.
Shot at 100ISO, Hanimex 28mm f/2.8 @ f/5.6 or f/8 (can't remember), 1408x528 (2,67:1, max 240-250 frames)
Nice images. Were you using ML or TL for this?
Quote from: MrMehh on October 18, 2013, 09:53:30 PM
Here's two frames from the short film I was talking about earlier. First one's the source file (RAW --> raw2cdng.exe). The second one is a processed one, upscaled to 1080p. That's roughly the color palette i'll be using to grade the film. Click on the picture so see the full resolution ones.
Shot at 100ISO, Hanimex 28mm f/2.8 @ f/5.6 or f/8 (can't remember), 1408x528 (2,67:1, max 240-250 frames)
Source
Processed
I think it looks great and the image upscales very well. But I have no shame in admitting my cinescope fetish and I love these widescreen images, which allow me to record longer at higher resolutions. Now obviously that's not always an option. The higher the aspect ratio the lower resolution you're gonna need to use.
I falled in love watching this photography work. :) please let me know when your film is ready I really wish to see it when is done! :)
about pixel at the edge of the shapes did you have noticed anything at 1408x528 and 960x540? how do you upscale?
for me 960x540 would be useful because reading the clapper boards for taking audio takes several seconds. how do you take audio for sync when you shot at 1408x528 that allow only few seconds of recording video?
my fear (sorry for repeating concepts sometimes I feel like "Sheldon Cooper") is if I show my work to a short film festival in a cinema theater and they see pixels.
I've noticed that running raw footage through Neat Video to denoise it helps with aliasing as well, from the pixel blending method they use I suppose. I have footage shot at 1280x512 that I've pulled up full screen on my iMac (27", 2.5k rez), and could hardly detect any aliasing.
Another benefit of raw is that with the extra picture information, plug ins like noise reduction and stabilization have more info to work with and you can usually get better results than h264 video.
Quote from: dslrrookie on October 18, 2013, 10:22:54 PM
Nice images. Were you using ML or TL for this?
TL2.0; SixThirty :)
Quote from: Brawl on October 18, 2013, 10:58:35 PM
I falled in love watching this photography work. :) please let me know when your film is ready I really wish to see it when is done! :)
about pixel at the edge of the shapes did you have noticed anything at 1408x528 and 960x540? how do you upscale?
for me 960x540 would be useful because reading the clapper boards for taking audio takes several seconds. how do you take audio for sync when you shot at 1408x528 that allow only few seconds of recording video?
my fear (sorry for repeating concepts sometimes I feel like "Sheldon Cooper") is if I show my work to a short film festival in a cinema theater and they see pixels.
I upscaled using Magic bullet instant HD, it's quite easy to use but I have yet to do some tests between Instant HD and just simple scaling in AE.
The clapperboard is indeed a thing to consider. My short film is meant to be a teaser/trailer to a full short film so it's about 1:30 - 2 min. long which means that we shot everything in one day and there wasn't much that could go wrong. But still, if I really need those seconds I would lower the resolution from 1408x528 to 1344x503 which would give me 2-3 seconds extra.
I don't think you'll need to worry about pixelation. If you shoot RAW 1280x512 or lower, upscale to 720p, not 1080p. That's not necessary. In my case shooting 1408x528 gives me a decent amount of resolution to upscale to 1080p. Also when I import my DNG sequences I first apply a BMD Film LUT which flattens out the footage but also removes any sharpening and denoising, giving me a softer image which results in less aliasing and moire issues. I then use unsharp mask in AE to sharpen it up again.
You can't really go wrong with RAW. The worst thing that could happen is that it looks exactly the same as H264 in terms of sharpness, but it gives you the dynamic range, information to pull back highlights and push colors around to your liking resulting in a much better looking film than H264 could have ever given you. Not to mention that back in the days people shot films on DV cams where you could almost count every pixel during a screening in a festival, but that didn't matter, because what matters is the story you capture. I know it sounds cheezy but I wouldn't worry about pixelation or aliasing.
Quote from: MrMehh on October 18, 2013, 09:53:30 PM
Here's two frames from the short film I was talking about earlier. First one's the source file (RAW --> raw2cdng.exe). The second one is a processed one, upscaled to 1080p. That's roughly the color palette i'll be using to grade the film. Click on the picture so see the full resolution ones.
Shot at 100ISO, Hanimex 28mm f/2.8 @ f/5.6 or f/8 (can't remember), 1408x528 (2,67:1, max 240-250 frames)
Source
(http://imageshack.us/a/img443/2201/5lz.png) (http://imageshack.us/a/img405/7497/aa22.png)
Processed
(http://imageshack.us/a/img689/8428/aubr.png) (http://imageshack.us/a/img854/9208/frt7.png)
I think it looks great and the image upscales very well. But I have no shame in admitting my cinescope fetish and I love these widescreen images, which allow me to record longer at higher resolutions. Now obviously that's not always an option. The higher the aspect ratio the lower resolution you're gonna need to use.
I can't wait to see some footage!
I am having the same problems as "Cypressentgrp.com" on my 600D, especially noticable in the areas that are out of focus and/or underexposed. I searched for the cause of it on google and here in the forum. Here is a thread http://www.magiclantern.fm/forum/index.php?topic=5614.msg43075#msg43075 (http://www.magiclantern.fm/forum/index.php?topic=5614.msg43075#msg43075) that says it is solved - for 5DMkIII.
I found this on youtube http://www.youtube.com/watch?v=0J5gYcOA6ME (http://www.youtube.com/watch?v=0J5gYcOA6ME) and some other comments around www, where some people say the banding in 7D, 600D and some other crop canons is due to lack of processing performance of those models.
I started noticing it even when recording H.264, especially in green areas when moving fast.
So my questions are:
Is it possible to write raw2dng wth vertical stripes correction for 600D, 7D, and others separately?
Is it possible that recording in raw makes processor worse, so the banding gets worse?
I ve been using raw just for testing for about a month or so, I tried raw2dng wth out vertical stripes correction - it stays the same, it looks like the script written for mkIII doesnt take any effect...
All in all raw recording is superb, continous size upscaled to 720p is crisp, but the vertical banding for me is why I dont use it for real - no matter all other potential throwbacks like data size or complicated workflow.
Thank you for all the work done and for your help!
The stripe correction for 5D3 is for highlights (slightly different ISO for each column).
If the stripes are in shadows, you have slightly different black level for each column (the 7D has this in photo mode). In this case, you need to use the banding correction from dual ISO.
To see if this will help, try this test:
- put the camera in movie mode
- enable dual ISO 100/200 (or if you get the artifacts at high ISO, try 800/1600)
- take a silent picture (not raw video!) and run it through cr2hdr
- post the results (DNG and JPEG crops showing the artifacts preferred)
Current raw_rec implementation does not record any info about black correction. It will be possible with MLV (though it's not implemented yet, but it's in the spec).
Tried every possible combination, almost gave up, then found what causes vertical stripes in my raw footage! I was using TL called "NewMem"; then tried Nightly from 2 days ago (nice progress though!). When I put "SixThirthy" the stripes were gone... 100% clear now (:
A1ex - thanks for helping!
Quick Question, why does shooting raw in 720 (60fps) video mood cause it to stretch? is there any way to prevent this from happening? we guess this may be causing some of the more serious moire issues? Shooting in 720p gives us more res and less crop.
720p mode skips more lines, so you end up with a "squished" raw file.
720p mode has Downscaling. Awful problems with antialiasing. I wouldn't recommend it
Thanks guys, that makes plenty sense. Out of curiosity, is there any way to strip ML and Canon and or most elements that take up buffer room? Basically do what ever it takes to get the most out of the raw feature.
Quote from: Cypressentgrp.com on October 31, 2013, 07:46:07 AM
Latest Nightly Build.
So I'm not the only one getting dead pixels in raw... Any ideas on how to get rid of these other than flat field correction?
Try a different version of raw2dng. On mac, I was getting a lot of dead pixels with RawMagic, but switched to Son of Batch and don't get any.
Quote from: N/A on November 01, 2013, 06:20:31 PM
Try a different version of raw2dng. On mac, I was getting a lot of dead pixels with RawMagic, but switched to Son of Batch and don't get any.
Tried the one http://www.magiclantern.fm/forum/index.php?topic=5404.0 (http://www.magiclantern.fm/forum/index.php?topic=5404.0) got rid of the dead pixels, but now the FPN is back.
Hello,
I am very new to this forum, as well as Magic Lantern. Sorry taking your time, but i needed some help.
I make my living on shooting video. But i only have 600D, and 50mm 1.8. Why am i telling you this, is because i just started my business and i am stuck with these configuration, since i have a family with a child to look after.
I came across ML and TL. And I used to shoot with older versions without having problems. But right after i installed Tragic Lantern (NewMem) i started to get coloured dots, most of which are blue. And after searching several forums and trying every possible solutions (such as dng convertors, sensor cleaning, various nightly builds, and third party programs) ı got nothing.
Two days passed, and monday is coming. So i need to find a solution as soon as possible. If someone can help me, i would be gratefull.
I can tell, the problem is not about the camera, for i can shoot Canon H.264 dot free. And i doubt the problem is caused by conversion. I tried different versions of raw2dng, raw2cdng, Magic Lantern RAW - 1.2.0. Nope.
PS: I used to get FPN before, but this new version (NewMem) got rid of FPN.
OK, got a strange problem, or I'm doing something badly wrong - I suspect the latter ;)
I compile ML from source and this works fine for the 50D but for the 600D I get SOS flashing on the activity light!
Compile process is make clean && make 50D or 600D in the root and then cd into platform for the camera and make clean && make zip, then copy over the contents to the card.
The 600D works fine when using the nightly builds using the same card for the compiled one (completely removing each ML first), any pointers?
Hi 1%,
please take a look at this topic: http://www.magiclantern.fm/forum/index.php?topic=9145.0
we are talking about the possibility of using dual iso in h264 mov instead of raw, we know the compression can husrt the idea, but it deserves a try... 60i and 50i with even and odd fields video are recorded in avchd in camcorders and works ok...
if you can enable dual iso module to work in h264 mov recording I can help testing it in 600d/t3i
thanks
QuotePS: I used to get FPN before, but this new version (NewMem) got rid of FPN.
Because I think you're using a version with af_raw enabled. Its either af_raw and no dead pix/fpn but sometimes "peaking" style outlines or no defect correction at all. :(
Any new bin's for us 600D users on the way? The nightly's are fun to play with but the extra little hacks TL has in it make it more useable, at least imho.
@1%
please take a look at the dual iso h.264 topic. It is working pretty good with two lines per iso, no magenta frames until now recording in full hd in 600D.
Can I kindly and gentle ask you to give us the code for enable one line per iso? I know nobody is giving cents for this idea, but the results in dual iso h264 rcording are so amazing and we have nothing to lose testing it, this thing is already working in my 600D, so allow us to give it a try, just give us the code please, there is a contributor who can compile!
thanks
@1%
The best stable build for 600D at this moment is your NewMem. Everything works great, including RAW video.
I did a try in the 600D.102 nightly 2013/11/23 but temperature is reaching 82 Celsius and recording stops automaticaly. I also did a try in 2013/09/28 but lots of errors loading modules...
Only thing you could improve is the audio metters layout because it is over the other informations. In this 2013/11/23 build the audio metters is in better layout, smaller and besides the other informations.
Can you just implement this audio layout in your NewMem build? The colors of the displayed informations is not so much inportant, can be colored or white, but reposition the audio metters is a must. If you can, it will be the best build for 600D !
Thanks.
Getting lots of noise in the shadow area's when I increase the exposure in ACR. I know I'm pushing the limits of this as I'm shooting at ISO 160 in a very dimly lit room, but am wondering if there is a list of "Best Settings" for shooting RAW. not including exposure, but just the menu settings that give the best performance.
I have some problems with sound recorder function. After about 3-4 minutes of recording camera freezes till I take out battery. When in video mode sometimes when it freezes I can hear mirror falling down. I tried clean install of NewMem but nothing changed. Can somebody help?
Don't use it. I've removed it from main builds because of a dangerous bug (as in possible camera brick).
Thanks for fast reply. Now I'm just wondering how to get the highest sound quality from 600d. I wont to use it as sound recorder. I turned on recording audio in separate wav during video recording. I think that it is the best solution for me.
I've noticed that when shooting in 720 60p in raw I (or overrode to 50p) it looks like sh*t. However, when put into the 3x 1:1 mode it doesn't downscale anymore thus all aliasing/moire and needing to stretch in post is gone. What sucks however is that it has a bunch of dead pixels (non cropped has this too) and seems to "glitch" on the framing and will throw in an inverted purple frame ever 40 frames or so.
Is there a way to fix this because if so the 60p in raw would look gorgeous ;D
Thanks!
Quote from: Shawn_Lights on May 23, 2013, 09:21:10 PM
Lovely detail. Magenta/Green slider needs to be moved to 0.
Where is this slider? I' having trouble with this on my 600D
Does anyone had problems with colored dots in their RAW footage? I've already posted a question about it, but the awnsers are a bit unclear for me, since im just starting with ML.
I've shot with the latest version of ML and with [NewMem]. But my footage turn up to be 'color dotted'. After procesing them in ACR most of the dots are gone, exept for 3 dots, one white, a yellow one and a purple one. Here is the link to the RAW video i shot of my dog, maybe you guys know what to do. Hope to hear from you!
http://www.youtube.com/watch?v=I_t7HEy-JOs
By the way, here is a screenshot of some blue pixels/dots. Anyone got a solution for it? An aplication some ppl here mentioned, but that didn't work.
http://imgur.com/0hPzar2
The blue dots seem to appear in very dark area's/shadows.
Hi All
So I have a 600D and want to know what are the best setting for Video with ML & which version ? ? I have a rode mic attached and I am told to use tragic lantern to help get rid of the hiss ? Also is it better to record in h264 or raw on this camera ? I am looking to film short films on it
Thanks
You'll get higher resolution with h.264, but more dynamic range/color with raw. For short films I'd say Raw if you want that "film" look, but you'll have to shoot at a low rez and upscale for decent results.
Just search around the forum, these questions have been answered numerous times.
Unfortunately only 960 x 544 is possible continuously with the 600d :(. 1280 x 720 only records ~100 frames.
Here is a video shot with Raw on the 600d.
Raw is very easy to grade but I feel that you should try it out in some tests before shooting a short with it...
Hello,
I just started using the ML hack and I'm bit confused at the results I'm getting. I have the 600D, 50mbps 32GB SD card. I'm running into two issues. When set to the lowest resolution, I'm still getting the error code "recording stopped automaticlly" and my footage is either extremely zoomed in or excessively cropped. Can someone post a simple check list for the best working settings for this camera? I'm sure that I'm just overlooking something.
Thanks!
Quote from: Ronn on February 22, 2014, 01:58:10 PM
Hello,
I just started using the ML hack and I'm bit confused at the results I'm getting. I have the 600D, 50mbps 32GB SD card. I'm running into two issues. When set to the lowest resolution, I'm still getting the error code "recording stopped automaticlly" and my footage is either extremely zoomed in or excessively cropped. Can someone post a simple check list for the best working settings for this camera? I'm sure that I'm just overlooking something.
Thanks!
Unfortunately 600D has quite a low write speeds (max 21 mb/s), so it is not possible to shoot in high resolutions and if it is too big, you can shoot only limited frames. At tme moment you can check best settings (for 16:9 aspect ratio) in this web file:
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=5
You have to experiment and find what suits you the best. You have to decide what aspect ratio you want either, as it is possible to shoot higher resolutions if you set more wide aspect ratios (like 2.35:1 to 2.67:1).