You can build from source and look for bugs. Taking off the pitch did not fix it. Its like FS buffer address is off.
Threw my commits in here:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/all
You can copy into ML repository whatever is good.
Which firmware version are you using the fir on?
Merry Christmas :)
Quote from: sparedog on December 25, 2012, 12:17:58 PM
Which firmware version are you using the fir on?
Merry Christmas :)
good rule of thumb for ML: always asume we're using the latest FW version ;) v1.1.2
I've fixed MZ vsync using 5d3 method.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/f4d541ce36dfa7954dd5d6ce7d92010956bf58e3
On 600D I can use either 5d3 or 60D vsync method and get "acceptable" results in 24p and 30p.
I had to change
msg_queue_receive(vsync_msg_queue, (struct event**)&msg, XXX);
to 10. Its still not perfect with either one and I get a flicker seemingly randomly or sometimes it seems to get off sync and go crazy for a few seconds. I can't get this value right, I've tried 1-10 and 24, 12, 30, 60, etc. The signal appears right, just not the timing of it.
Audio should at least play, it records already. I think I've got the functions right on the latest commit. There are 2 options for some functions like SetAudioVolumeOut. I made a log, audio_ic_write is right, I don't know about read. Stuff is happening but I hear nothing or audio locks up. Supposed to be AK4646 like the older cameras just can't override sound dev task in new firmware the same way.
http://pastebin.com/57diJcHY
http://www.qfpost.com/file/d?g=UtFh586in
For new stuff:
FF6D2A00: '***** ConvertKeyEventToLvDZoomKey(%d)'
FF1A98D4: '***** GUI_SetLvDZoomKey handle NULL'
Is this for regular zoom or dzoom?
NSTUB(0xFF35E2CC, str:X3_current_x1_x3_x10_X10_X1)
How does this work? These all look the same as 600D.
FF19350C: STRING: 'PROP_MOVIE_SERVO_AF [0x%x]'
I guess this property has to be changed to enable movie AF?
All the touch screen stuff is there too.
Fixed MLU, HTP, ALO and put/relocate things on the info screen.
Nice, I found dma_memcpy, need to find the rest of the jpeg stuff. I wonder if it will save them with wifi on.
Quote from: 1% on December 29, 2012, 07:48:11 PM
I had to change
msg_queue_receive(vsync_msg_queue, (struct event**)&msg, XXX);
to 10.
Don't change that, use msleep instead. If you use msg_queue_receive, make sure you send the sync message from the other end (from some LV state object). That call should not timeout in normal operation.
I used the 5d3 EVF sync from the other end. Msleep makes it flicker worse. 6D didn't need anything changed at least.
There are 2 dma memcpy, both look like the 600D one but neither seems to work.
NSTUB(0xFFCD0ABC, dma_memcpy) // V1: FFCD0998 V2:FFCD0ABC
Maybe the parameters are switched arround. When I was decompiling I saw arguments listed in the function names but now I can't find them, its like they got cut off. I even dumped the names to a file.
I tried changing slices and again nothing happens. Qscale and current slice show 0 everywhere I look. I/P numbers change too but nothing seems affected. Could be somewhat like 7D and video runs on slave processor? I figured out how to activate dzoom like on 600D but camera freezes and then "bricks". I can't find the value of PROP_MOVIE_SERVO_AF, seems like an easy one to activate.
Logs show:
1204: 969.786 [LV] PROP_MOVIE_SERVO_AF_OFF
1197: 967.956 [GUI] PROP_MOVIE_SERVO_AF [0x0]
Dzoom now has dzoom ratio and dzoom step and property manager makes it seem like video_mode property is longer with 7 entries and size of 24.
Log still shows:
968.287 [PRP] mode 0 size 0x0 , framerate 0x1e , type 0xf zoom 0x0
The last 2 entries seem to be same as video_mode[3] and video_mode[4] but it didn't allow me to write with len of 20.
Fixed the assert. 6D has a X1 zoom mode that makes lv_dispsize == 129.
Shoot.c
PROP_HANDLER(PROP_LV_DISPSIZE)
{
#if defined(CONFIG_6D)
ASSERT(buf[0] == 1 || buf[0]==129 || buf[0] == 5 || buf[0] == 10);
#else
ASSERT(buf[0] == 1 || buf[0] == 5 || buf[0] == 10);
#endif
zoom_sharpen_step();
zoom_auto_exposure_step();
if (buf[0] == 1) zoom_was_triggered_by_halfshutter = 0;
}
Went back to EVF "60D" style sync for MZ because 5d3 sync was flashing while recording.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/278f7901682d88a0bb41d6d5d613d91be7018a98
Beeps work.
Sometimes I get error 70 after multiple beep sounds. Play test tone seems to work repeatedly. Wavs also get error 70 on playback. It worked better with LV off.... I think its a memory issue. Only 42k free. Trying to relocate memory pool like 600D failed, LV/GUI doesn't come up. Camera still starts and takes pictures.
Good news!
6D will load H264.ini files. The settings actually take effect. Encoding mode changes, DRF changes Slice hacking set the DRF, this lets you set a range at least. Maybe these parameters can be changed on the fly too. So far tested all-I without issues with a DRF of 7-20. Most frames were 7. No stops yet, wonder if it will on a full scene or static. Cache hacks will probably do wonders here. Probably can go till the camera freezes.
Even Better, DRF of 1 is possible. There is CBR, VBR and buffer save written by canon. Needs more experimentation.
You can even change the profile level lower.
I can record 120mbps (constant, cbr is mostly CBR) at drf 1.
I don't think qscale and the cbr numbers will work on this camera. Better to expand 5d3 config to auto load different configs or directly change IVA parameters.
Dma Memcpy works on all new cameras. Just have to rename:
AJ_HP_Copy_n_DMA_channel_n_BLTDMA which has the ram offset.
I found the actual function and using it without the offset did not work. I wonder if this holds true for the get jpeg buffer functions too.
High res silent pics work.
Hey 1%,
i'm absolutely amazed by your fast progress, and i'm following with a lot of interest all your posts about 6d developing, keep the good work, i'm your fan ;)))
hi,
and thanks a lot for the work so far!!! i have one short question:
- will it be possible with the 6d ML to customize the 'magnifying button' function in live-view, as it is in ML for 5d2? precisely, change it so you press ONE time and it magnifies (5x OR 10x) and one more time for it to go back to 'normal'?? (because by now they changed it to be pressed 4x to get back to 'normal' again, and that's a real pain when you work with manual focus)
thanks from berlin!!, and looking forward -
jan
It should be possible with zoom shortcuts. Right now I have it bringing up magic zoom. MZ on half shutter is super annoying.
If you turn of MZ right now and disable 5x or 10x it will zoom to the one you have enabled.
QuoteMZ on half shutter is super annoying.
nooooooooooooo.................... :(
You rather have it on half shutter and then zoom button doesn't do anything while recording and only brings up regular zoom?
Right now:
Zoom button can be configured to either magic zoom or no MZ and regular zoom.
You can still regular zoom on half shutter.
I'd rather be able to zoom with the old star buttons, maybe its possible to remap it.
Here are my plans for the bit rate menu.
*Auto Loading of 4 configs.
CBR - CBR Mode ml/cbr.ini
VBR - VBR Mode ml/vbr.ini
RC - Canon rate control /ml/rc.ini
H264.ini - User config with load button.
We can override InitialQP and target Bit rate. Yes it does work, yes it will freeze camera on IPB if you go over 60mbps and violate the spec until you load a level 5.1 config.
I will make an auto loader with OFF, ON, Override.
Without the auto loader on you can adjust target bit rate *OR* record at a fixed qp with the initqp toggle.
Everything else can be set in the text files, following what I wrote in the RE thread. This puts video quality on par with 600D and cache hacks, maybe a bit better if you pixel peep. When the matrix loading is figured out this will be an ideal setup. I can't find where the other parameters can be adjusted on the fly, I think they get sent to a second proc or are in registers/ram. Maybe buffer save can be ported over for another rate control mechanism if initQP can be changed on the fly, mine seems to be better at stopping stops than canon's.
You an set the predictors like the old X values too but the scaling is different and they are sent to the jpcore like the old JPCORE set I/P function which i wasn't able to figure out. It had pointers to an address when being called.
What do you think?
What I need to fix before alpha:
*ASIF will not stop and causes error when its done playing. I don't think it stops well even recording.
*Frame ISO seems like the right address, I think eos M has the values backwards but changing them doesn't seem to be working. When I spy that address after dereferencing it changes the numbers when I move shutter/iso/aperture,etc.
*Zoom with focus ring doesn't want to work. Lens is reporting no changes to focus distance.
*ISO changing is (slightly)broken. Hitting ISO while recording just displays it, it will have to bring up ML menu now. ISO changing also stops at 6400 and it should do 10000. Canon is changing and using the digital component now just like ML So I so 640, etc are regular isos you can use. You can even take off more from the canon digic or ml digic menu and make funny ones.
I'd like to get audio monitoring working so audio is useful. Gain can be turned off from canon menu, volume can be set too. Some of this stuff can be done with canon functions now too, no need for low level IC access. But this stuff isn't needed for the alpha.
New Bit Rate Menu.
Time is displayed where qscale was right now. The display bar makes time flicker if placed in the upper right corner. It covers up free space which shows all the time. I'm thinking maybe put active config in place of qscale or Initial QP.
Also I think QP/BR and autoload options can go in submenu. Load Config and Config loaded should be visible with 1 click, otherwise it gets annoying.
I'd make it simple for the user, without complications.
For example:
Bit Rate: click to adjust the main parameter (usually bit rate). Display the preset name and the bitrate + unit (12 what?)
Submenu:
- Preset: CBR / VBR / Canon default / User / etc -> this will choose the config file
- Target bit rate: X mbps (what about saving the new value in the config file, every time you change it?)
- InitQP
- other parameters
Loading should be automatic, maybe from a background task. Too many overrides will confuse the users (I'm already confused). Keep it simple.
Problem is they're all exclusionary.
I.e initqp and bitrate will override what is in the configs. But they behave differently depending on which mode you're in.
In CBR mode this means everything at QP you set. This is as good as setting the config.
In VBR mode it might block flipping of QPs too, then VBR is broken.
In RC mode everything will be at that QP too, I think and recording will overrun as it won't be able to kick it down.
Wish we could just set the parameters from the screen and not load anything from the card but I only found the 2 in memory.
I have to do more testing to find out exactly what blocks what and go from there.
great progress! hope to join you again soon :D
Hehehe, new bug. Zoom box is trapped on "x1" canon zoom.
Seems to be working again. Added flexinfo but need to add more infos like 600D has.
:(
ASSERT: pSuite
at ./PackMemory/PackMem.c:511, task RscMgr
lv:0 mode:16
Magic Lantern version : v2.3.NEXT.2013Jan09.6D112
Mercurial changeset : 7066eb7b8af6+b27fff222522+ (unified) tip
Built on 2013-01-10 00:57:04 by user@D610.
Free Memory : 0K + 2928K
*HDR is fixed.
Very fast work you are doing, well done!
Free memory 0K?!
Check ML binary size, it's probably too big. What are the numbers under normal usage?
Its only like a 300 some K binary. I had like 40k when I enabled all of the features. I can't figure out how to use the second pool or do a cache hack startl. On 600D now both are completely. free for some reason after the proper cache hack.
BTW: H.264 configs are here: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
On 600D, can you try with a smaller binary (disable most features) and see if the amount of free RAM changes? It should.
On 6D, you need to find where the buffer for AllocateMemory is initialized, and adjust its limits. This isn't easy. The 5Dc/40D use the same trick - they shrink the buffer with 512 K and ML is inserted into the free space created in this way.
It doesn't seem to change the debug printouts on 600D but I tried loading a 500K+ binary and then I'm out of memory, err70.
On 6D the places where 600D was setting the pool are now 0 so it must do it somewhere else.
wait didn't we have like 3mb of free memory before?
In the other pool. It boots in the first.
in 5dc it looks like this, we modify the 0xA00000 to be 0x980000:
not sure if it will be this easy for 6D, im digging now.
I doubt it.
I did that already, it didn't work.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/8d32987bf2b5808cd96e726abfa9219e278898dc
Here is a test sample of RC.ini with initqp overwritten and ALL-I. It basically becomes CBR wtih fixed QP. But I wasn't using the UHS card so it kept stopping on default, I'm thinking about buying another card but want to test on what most people will have (and I bring the 600D to work).
http://www.qfpost.com/file/d?g=07XWtMQer
Here is VBR @ 5.1 with IPB compression. My stream analysis tools don't like opening these. Maybe someone will have better luck.
http://www.qfpost.com/file/d?g=gLPkQ8MdJ
Here is ALL-I with the 4x4 luma matrices. The atoms are screwed up so it won't play back. Maybe someone can find out what is wrong with it and we can make the 4x4 stuff work.
http://www.qfpost.com/file/d?g=3TjJxDJYB
I had similar result trying to play back your files, only first one plays
MVI_6990 148 mbits/sec TREES
MVI_6981 187 mbits/sec BLACK
MVI_6977 2.68 mbits/sec BLACK
I have the 30MB/s sandisk Extreme cards. I would happily upgrade my cards, if need be, to faster ones should they allow a higher video bitrate to be implimented.
I think its important to try to encourage results/tests from people with faster cards. On a 2000 euro camera, the price of a decent card is quite small, and a small outlay for the potential of what full frame can be unlocked to offer.
#2 should be trees too. It plays back for me. Only the last one doesn't. What player did you use. MPC-HC worked for this one. Last one is screwed up and won't play, some atoms are missing, so is SPS/PPS. Maybe those matrix addresses are required to keep the atom writer function happy.
I can record longer clips but a few seconds is like a 100-300mb already.
I only tried to open them in quicktime pro on windows 7. DLed the second one again, still plays only black, no picture or sound.
Don´t worry about recording longer, its only proof of concept at the moment, right?
None have audio. Try VLC or Media player classic. It plays fine on linux too. Only videos with custom matrices don't play back for me. Maybe quicktime can't play back profile 5.1 IPB or something out of spec is set that it can't interpret. Yes its still in testing phase but I found something cool:
http://processors.wiki.ti.com/index.php/DM36x_Rate_Control_Modes
Encoder is similar to this. The other rate control mechanisms (3/4/5/6) didn't work but setting initqp to -1 made it pick auto. I'm going to look at this doc and test things.
Does anyone have a possible time frame on when ML firmware will be release for the 6D?
Thanks!
I think 1% says we're close, mainly audio / bitrate to finish seems like.
I used it the other night when I went out, it feels very stable now, much better than when I last pushed a code commit. great work to 1%!
Would be nice to have it on jan. 24th 8)
I could test it exhaustively then for a long weekend vacation..
But I understand it's all charity ;D
I'm looking out for the first Magic Lantern version for the 6D.
Keep up the good work guys!
Quote from: 1% on January 08, 2013, 09:05:47 PM
New Bit Rate Menu.
Hi, I'm planning to get a 5DM3 or 6D.
I see on that picture of the new bit rate menu that CBR can now go up to 12 ? is it the maximum ?
With ML 2.3 that I use in my 550D, CBR goes up to 3, and most of the time just stop recording when there is too much complicated stuff going on in the screen, I understood it has do with the buffer of the camera. (my card is a sandisk extreme 30mb/s).
How do the 5DM3 or a 6D compare to that, since they can use faster SD / CF cards ? Do they have a bigger buffer ?
How much bit rate is 12 on the ML menu ?
It says on the bottom help if you run it.. Its rate X10 so 12 is 120MB/S but this is just the target rate, lowering will cap it but raising it won't necessarily raise it. Really you want to use one of the configs and set up a bit rate that your card can handle. Canon rates aren't fixed and your maximum is max sustained write for the card. 6D uses UHS-1, 5d3 uses faster CF cards. When you set it higher than the card can handle recording stops. Hence you're not having much luck at 3x on your current camera (try a really low ISO it will probably record).
I'll try to speed up dumping rate and see what it does. I guess that is next up. Won't help ALL-I but gop of 3 on IPB should be interesting (or crash).
We users are cheering you on! Looking forward to trying ML - is it too much to hope that I'll be able to monitor audio through my AV ouput while using a HDMI monitor?
Quote from: 1% on January 15, 2013, 04:17:06 PM
It says on the bottom help if you run it.. Its rate X10 so 12 is 120MB/S but this is just the target rate, lowering will cap it but raising it won't necessarily raise it. Really you want to use one of the configs and set up a bit rate that your card can handle. Canon rates aren't fixed and your maximum is max sustained write for the card. 6D uses UHS-1, 5d3 uses faster CF cards. When you set it higher than the card can handle recording stops. Hence you're not having much luck at 3x on your current camera (try a really low ISO it will probably record).
I'll try to speed up dumping rate and see what it does. I guess that is next up. Won't help ALL-I but gop of 3 on IPB should be interesting (or crash).
I've been trying to find an answer, but i can't find it anywhere. At what bitrate does it record without ML with just ALL-I turned on?
Quoteaudio through my AV ouput while using a HDMI monitor?
its still a ways off. I should see what happens when i do this on 600d. Never thought of trying it even though its obvious.
QuoteAt what bitrate does it record without ML with just ALL-I turned on?
Like 70 or 80 something is the highest I got. Not too bad but QPs are fairly high, above 10. IPB is locked to 60 without ML because of the profile.
Quote from: pontus on January 16, 2013, 05:36:14 PM
At what bitrate does it record without ML with just ALL-I turned on?
I get about 80 too for my top bit rates. But this is 80mbits per second.
Quote from: 1% on January 15, 2013, 04:17:06 PM
Its rate X10 so 12 is 120MB/s
Did you actually mean 120 MegaBytes/s, because that is a huge increase. Am I right in thinking there are 8 bits to a byte, so that would be 960mbits/sec. That´s impossible right?
Bits. bytes would be impossible.
Talking of the impossible, how likely is 4:2:2 with this codec from the 6d, or is that only doable with codecs like mjpeg?
1080 4:2:2 at 120mbits would be great for broadcast projects.
Quote from: 1% on January 16, 2013, 05:54:51 PM
its still a ways off. I should see what happens when i do this on 600d. Never thought of trying it even though its obvious.
Like 70 or 80 something is the highest I got. Not too bad but QPs are fairly high, above 10. IPB is locked to 60 without ML because of the profile.
Oh that's great even without ML. :D When you test out the x12 (120mbps) bit rate, what card do you use? I'm thinking about getting new cards and the fastest UHS-1 cards from sandisk should do the trick, right? Even if it's not a fixed bit rate, it should keep up pretty good and stay there with no problem probably. [spoiler]http://www.ebay.com/itm/SANDISK-EXTREME-PRO-SDHC-95MB-633X-16GB-16G-16-G-GB-SD-HC-UHS-I-CLASS-10-NEW-/320785302234?pt=UK_AudioTVElectronics_PDAsAccessories_MemoryCards&hash=item4ab04b42da[/spoiler]
Get UHS, its worth it. I tested on both a stock card and UHS card, did a bunch today. Rate control with low QPs is probably the best config so far. Still do 80-120Mb/s but its stable. I'm liking
[email protected] over all I for some reason. All I seems to hit lower rates and stop more. I think technically speaking
[email protected] is supposed to be better quality. Real world tests with more than just shooting out the window are needed.
Setting the target rate/init qp isn't really the best option for all modes. You'll want to edit the config files. Its mostly handy for CBR, that mode goes by those parameters. The other ones will stop switching QPs in essence becoming CBR.
I fixed vsync for magic zoom, focus peaking, and zebras. Things are running smooth now, MZ only flickers for a second after starting recording then it's fine. It flickers in 60fps mode but Alex says all cameras have some flicker with high framerates, so it's fine.
good to see that stuff make the repo.
iso selection should be fixed as of latest commit
*isn't this broken on 5D3/M/650D too? The commit is camera independent or at least tries to be.
You guys ROCK!!! Geniuses ...
Quote from: 1% on January 19, 2013, 02:40:51 AM
iso selection should be fixed as of latest commit
*isn't this broken on 5D3/M/650D too? The commit is camera independent or at least tries to be.
Which commit?
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/c4c5b6ecf96b3a0d211041f69faf567ab1f7a71c
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/e98183cefd38fb2bd22d85b3781112a35cedfb0a
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/74cd89627f93eb83aa8404eb7e5dde040c592086
Here is all 3 that deal with iso.
Extended HDR bracketing is working now.
*For new peaking, found that it draws to the LV if 'can redirect buffers easily' is turned off. unfortunately it draws only 1/4 of the screen and flickers. will have to investigate it more.
@ 1% and Coutts,
Does this camera worth your time? I was shocked by what I saw: http://www.youtube.com/watch?v=_eJK-opJVDA moire is so bad that it is impossible to use it professionally. Can anything be done about it?
Thanks!
Quote from: DTSET123 on January 22, 2013, 05:53:18 AM
@ 1% and Coutts,
Does this camera worth your time? I was shocked by what I saw: http://www.youtube.com/watch?v=_eJK-opJVDA moire is so bad that it is impossible to use it professionally. Can anything be done about it?
Thanks!
all it would take is mosaic engineering to develop a filter
and i've seen other videos that showed the 5D MKii having worse moire than the 6d
I had 3 mark ii for almost 4 years, trust me - it was not worse... 6d is a disaster!
if you don't like the 6d, then don't buy it, nobody is making you
get a MK 3
G..., thank you for the suggestion! Already have it thou...
Quote from: gravitatemediagroup on January 22, 2013, 06:43:50 AM
all it would take is mosaic engineering to develop a filter
and i've seen other videos that showed the 5D MKii having worse moire than the 6d
Hello people, I have just registered to jump into the conversation.
I have just bought the 6D and since I have replaced the 5D mkII with the 6D for shooting as a second camera for an american feature film.
A couple of facts:
1. 6D does have a moire problem, but like on every professional job, you must handle moire by being smart about costumes and sets. It does not appear on my footage.
We have tested the raw material in BlackMagic DaVinci Resolve and compared it with footage from 5D mk2, 60D, ARRI Alexa and it is much better for grading than all the material that we got from HDSLR cameras, when you shot ALL-I frames. It makes much bigger files, the SDXC cards are really fast (90MB/s) so the whole workflow just got better and faster with better results. You can do wonders in grading now.
IT IS USABLE PROFESSIONALY and we mix the footage with ARRI ALEXA footage and in the end result you really can't see the difference. Don't forget, that not all is depending on the camera, but also the lens, the lights, sets and locations, costumes, movement, smart settings so you make the footage really look alike ARRI Alexa footage. I am not an advocate for 6D, I also use mk2, but since 6D i find it much more usable because of the price, weight, framerate, ALL-I, etc...
The low light conditions and low noise are much better than the mk2 and even 5d mk3, i guarantee. This is more important because when shooting video, you don't really want to play with the shutter (you shoot in the range 50-200), and I use the aperture creatively so I can choose DOF, then I am left with ISO range and it becomes so important believe me!
I think the moire problem will be resolved by software and i hope Magic Lantern can help with this. Also, I see that moire is less of a problem when you shot with flat profiles, cinestyle etc, it becomes visible when you shoot with strong contrast, but all you have to do is move, change your position or lens, a little bit and its gone.
AF system - video does not need it! whoever shots video does it manualy, and focusing is also a creative tool, so i really can't see who needs so many AF points, since i use AF occasionaly with one AF point, the center and use it for preview, not actual filming/focusing.
I really would like to see a magic lantern alpha release and i hope you focus on:
1. Clean HDMI output - this is terrific and you can choose a recorder like Atomos Ninja-2, I would like to see it without resizing and cropping later, if its possible 1920x1080...
2. Focusing tools
3. Frame rates and formats - maximizing bitrate and raw data
4. Changing aperture smoothly, not by steps, but i feel somehow 6D already does it pretty good just outside the box.
5. would it be ever possible to watch the lcd on camera and hdmi output simultaneously?
6. Look into the wi-fi and see if its possible to send the monitoring video while recording and in preview? it does not matter what resolution is sent wirelessly, but wireless monitoring would help all of us alot.
I will stay tuned and see the progress
Thanks alll of you guys for this work, I hope I can help...
Vladimir
Quote1. Clean HDMI output - this is terrific and you can choose a recorder like Atomos Ninja-2, I would like to see it without resizing and cropping later, if its possible 1920x1080...
maybe when the update comes out. right now its got the same HDMI as digic iv cameras.
Quote2. Focusing tools
Everything works except the lens info so no focus ring zooming.
Quote3. Frame rates and formats - maximizing bitrate and raw data
all done, I get all I rates in IPB, can record at fixed QP (makes high rates like digic IV)
i have some IPB vs samples but everywhere i go upload either has file size limits or times out.
Coutts is working on raw recording.
Quote
4. Changing aperture smoothly, not by steps, but i feel somehow 6D already does it pretty good just outside the box.
gradual exposure change works already.
Quote
5. would it be ever possible to watch the lcd on camera and hdmi output simultaneously?
i don't think you can on any canon. at least it doesn't downscale to sd when recording.
Quote6. Look into the wi-fi and see if its possible to send the monitoring video while recording and in preview? it does not matter what resolution is sent wirelessly, but wireless monitoring would help all of us alot.
Have to see why movie mode turns off wifi. probably i/o related if encoder is on separate proc.
*the low light performance isn't half bad. not sure if i get less noise or the same at high isos tho. not really sure what a *safe* iso is. in 600D it was 1250 before the noise started creeping up. here its like 128k or 6400 something.
Quote from: 1% on January 22, 2013, 03:37:43 PM
not really sure what a *safe* iso is. in 600D it was 1250 before the noise started creeping up. here its like 128k or 6400 something.
This is really interesting, need to try it soon or later...
Just popping in to cheer you guys on! coutts, 1%, and others, i am super impressed with the ingenuity and dedication i see you guys investing in this project! Also, while perusing the ML homepage, I notice that the banner at the top already includes 6D in the list of supported canons. I thought to myself, they must be close! Looking forward to loading ML onto my 6D - any chance for a working download before the weekend? I have a shoot I'd like to test this out on...
You can run it right now if you are not afraid of the command line.
http://www.magiclantern.fm/forum/index.php?topic=3697.msg24065#msg24065 ;)
http://www.magiclantern.fm/forum/index.php?topic=991.0
Quote from: a1ex on January 22, 2013, 05:34:23 PM
You can run it right now if you are not afraid of the command line.
http://www.magiclantern.fm/forum/index.php?topic=3697.msg24065#msg24065 ;)
http://www.magiclantern.fm/forum/index.php?topic=991.0
Thanks Alex for the useful and challenging info, as well as the gentle reminder on manners (I'm a noob!)
Update: aah, wow, all skills I desire and admire, but I confess this is over my head for today... so i will stand-by while more knowledgeable and capable people do their work...
Quote from: 1% on January 22, 2013, 03:37:43 PM
Coutts is working on raw recording.
Wow.
Coutts, what do you think the likelihood of this working. This could be amazing!!
Quote from: gravitatemediagroup on January 22, 2013, 06:43:50 AM
all it would take is mosaic engineering to develop a filter
I received an email today from mosaic engineering saying that they are going to be releasing an official VAF-6D very soon for the 6D.
Quote from: sparedog on January 22, 2013, 11:38:56 PM
I received an email today from mosaic engineering saying that they are going to be releasing an official VAF-6D very soon for the 6D.
I figured they would, and this is GREAT news
Quote
Coutts is working on raw recording.
What did you smoke?!
I guess he looked in debug.c where there's a raw video test (that actually tries to dump frames as fast as possible)
That's uncompressed, not raw. Should be doable at reduced vertical resolution (how much... depends on card speed).
Yeah, my usual mistake...altough I'm sure people would be happy enough with uncompressed video
Quote from: sparedog on January 22, 2013, 11:38:56 PM
I received an email today from mosaic engineering saying that they are going to be releasing an official VAF-6D very soon for the 6D.
I have got a similar email, so i will copy it here:
QuoteHi Vladimir--
Thanks for writing! Yes, we are certainly going to be releasing an official VAF-6D very soon; currently we are receiving a large number of inquiries in relation to this camera, and we are making it a high priority. At this point, we've just this week obtained a 6D here ourselves, and have begun evaluating some prototype optical parts for it, as well as the VAF-5D2b itself; we should have a final informations or an optimized design confirmed soon, with production parts to follow as soon as we can manage.
We'll keep your email address here, and let you know directly as things progress!
Thanks again and best regards--
--Dave Cubanski
I am aware that this topic is not about moire, but i feel compeled to put it here, since I hope there will be a software solution for moire, and we don't need to buy a $350 part of equipment which have some trade-offs (jams the shutter, mirror and changes focus)...
Vlad
Quote from: a1ex on January 23, 2013, 12:03:49 AM
That's uncompressed, not raw. Should be doable at reduced vertical resolution (how much... depends on card speed).
Sorry, but what is the difference between uncompressed and raw, since I use both terms when speaking about uncompressed video?
Vlad
More or less:
RAW = full sensor bit depth
Uncompressed = YUV422 color space but no jpeg/mp4 compression (= less artifacts in theory)
Google RAW vs jpeg, BMCC, RED etc. Raw can be compressed or not. Jpeg is compressed, but the same image data (8 bit in our case) can be uncompressed. Here we have uncompressed YUV 422 8-bit (the same data as in normal video, just without compression artifacts).
Hi Vlad,
The quick answare is this example: it's like for the stills images. In the images you can have a .jpg (compressed) or you can have a .bmp (uncompressed) or you can have a .cr2 (raw).
For the video is the same.
compressed, uncompressed and raw, where raw is not only the video uncompressed, but a lot of other datas directly from the sensor. I mean, for shure more bit depth, and a lot of other information. Actually (if i remember well) in the canon lineup only the c500 can shoot raw: http://cinemaeos.usa.canon.com/products.php?type=Camera-c500
Quote from: nanomad on January 23, 2013, 12:13:37 AM
More or less:
RAW = full sensor bit depth
Uncompressed = YUV422 color space but no jpeg/mp4 compression (= less artifacts in theory)
This is the holy grail for every cinematographer out there, we are able to record 444 only with ARRIRAW recorder attached to ALEXA, but 422 uncompressed is what every cinematographer/editor/digital imaging technician would piss in their pants if its achieved in DSLR camera.
Somehow I think if Magic Lantern succeeds in this, all the cameras would be much cheaper and Canon and all the manufacturers would have to improve on other stuff, it would surely be an industry-changing event.
Until now, it was possible to film directly from the hdmi output, not sure why you can't make a hack to display 1920x1080 but I hope it will get there soon...
Can somebody tell me what is the maximum speed achievable in the SDXC slot? Is it this that is limiting the quality and bitrate and can you embed an option in the firmware so it recognizes what type of the card is in the slot so the bitrate can be better with faster cards?
Don't get too excited... The key word is reduced vertical resolution ::)
So what is theoretically the best bitrate/lowest compression you can achieve if you have the fastest available card and you shot on 6D or 5Dmk3 (i guess they are same regarding this question)?
What is needed to get there?
yea, uncompressed YUV, not raw RAW. my bad :)
best compression would be all-I or IPB at QP of 1 and whatever rate the scene produces. i have a bin up already if you want to start using it and pointing out the bugs.
Quote from: 1% on January 23, 2013, 04:43:55 AM
yea, uncompressed YUV, not raw RAW. my bad :)
best compression would be all-I or IPB at QP of 1 and whatever rate the scene produces. i have a bin up already if you want to start using it and pointing out the bugs.
Yes, it would be great. I am working on a movie right now and using the camera, so this is a good opportunity to check it in real world... if i don't brick it in the meantime :)
1% where is the bin? I would like to play with it.
Yeah, is there a beta version we can use now on the camera now? :)
Also, I did try the VAF-5D2b filter on the 6D. The moire is gone but you have to tone down sharpness and contrast, otherwise, the filter is useless. For close-up, is great, but for wide shots not so much. The background appears too soft, not enough details captured by the camera. No moire thought. Maybe it can be fixed with ML higher birate?
Anyway, point is, I think Mosaic will fix the moire problem with a new filter. The only issue for meis the smoothness of video.
its up in my repo with the other 6D stuff.
Quoteif i don't brick it in the meantime
haven't had that problem with normal use. if experimenting with properties you should remember what you set so you can set it back if you soft brick.
here are some samples:
rate control config
https://mega.co.nz/#!hhgXxLbA!MB-_egDLa_AVjSTyV7nFxnF1aPd1rZqpRJ9ej2Dnydg
vs stock ipb on same scene
https://mega.co.nz/#!A4wFjL5Q!fcfZ2lGdUlQiU_swlipc6XZgKOMjNiYkYhISMP0zHDY
Quote from: 1% on January 23, 2013, 04:15:47 PM
its up in my repo with the other 6D
Well since I'm new here, i dont what or where your repo is? In your profile?
These should fix the cache hacked boot and fix memory issues... in theory:
HIJACK_CACHE_HACK_BSS_END_ADDR ff0c3470
HIJACK_CACHE_HACK_BSS_END_INSTR CBC000
RESTARTSTART CBC100
from:
ff0c318c: e59f12dc ldr r1, [pc, #732] ; 0xff0c3470: pointer to 0xd3c000
ff0c3190: e241088f sub r0, r1, #9371648 ; 0x8f0000
ff0c3194: eb3d1b3f bl =0x9E98 (mem_pool_init)
didn't fix cache hack boot yet but the allocate memory pool thing worked! we now have 400kb+ free (instead of <50k). great news! no more worrying about running out of space
i will have to retry cache hack boot. that gui cache hack made it boot to a black screen when i first did it
ok, tried it. ml boots up but erase menu is not working. I can see mL graphics on screen though so it did start. non cache hack method is working and I see lots of memory :)
QuoteAlso, I did try the VAF-5D2b filter on the 6D. The moire is gone but you have to tone down sharpness and contrast, otherwise, the filter is useless. For close-up, is great, but for wide shots not so much. The background appears too soft, not enough details captured by the camera. No moire thought. Maybe it can be fixed with ML higher birate?
Thank you! So you recommend to wait for a new filter? Do you by any chance have a sample video up using this filter?
Quote from: DTSET123 on January 24, 2013, 02:10:09 AM
Thank you! So you recommend to wait for a new filter? Do you by any chance have a sample video up using this filter?
You should wait for the new filter if you're not in a hurry. While the VAF-5D2b is usable on the 6D, I believe Mosaic will make a proper/better filter especially for the 6D.
I don't really have good footage to show. I only did quick tests : http://www.youtube.com/watch?v=UPrHhsaKZEs, http://www.youtube.com/watch?v=QVYGT7S9FkM.
I'll try to post more when I'll get ML.
I agree, I don't see a filter designed for another camera doing the 6d any justice.
Also, the 6d is naturally produces a somewhat soft image, so from here a slight bit of unsharp mask will always be applied to my 6d footage.
Also, I don't want to sound like I'm rushing, because greatness should never be rushed, but is their a rough estimate for win ML will be ready for the 6d? a week? a month?
I have avoided using the camera full throttle because I don't want to shoot a bunch of quality footage, and then turn around and wonder "what would this look like with ML on it?" and re shoot everything all over. also, sorry if I overlooked a status update in a previous post.
you can use it already but its not super stable yet and some features don't work and it can crash so you might have to restart or pull the battery. judge for yourself
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
I've been trying to find out on my own, but what does qp mean? It would be great if there was a terminology page available for teh n00bs :)
Quote from: 1% on January 25, 2013, 07:47:37 AM
you can use it already but its not super stable yet and some features don't work and it can crash so you might have to restart or pull the battery. judge for yourself
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
I do not wish to waste your time, but is there a page or somewhere with instructions how to install this? Is it just a case of putting all the files on the root of the sd, and then following the normal ML installing guide?
I am very interested in helping find bugs by testing, but maybe downloading it at this stage, having no previous experience with ML, would be a hinderance to your development, and best for me to wait till there is an alpha release to test?
Which firmware is required? I have a feeling that I should not have installed 1.1.2 - ML did not work.
the bin is the executable. put ml 2.3 ml folder on the card and make it bootable. besides that not much to it.
this is using the latest firmware, you can set the boot flag with the fir in this thread.
soooo....
1. download all files from bit bucket
2. put those files along with ML 2.3 in a folder (does the folder require a specific name?)
3. install just like a normal firmware update?
also, I'm guessing the .ini files DON'T go on the SD card
or do they need to stay located where the .bin is?
I attempted to load it and I get "memory card containing firmware is required to update"
Make sure you download the .fir from this thread after you are updated to 1.1.2, run that to set the boot flag.
ml folder from 2.3 goes in root. the .ini files go in the ML folder (yes you need them).
Its not like 5d3 where you have to run it every time.
alright, about to make the 2nd attempt, i'll let you know shortly how it goes
is EXT HDR 6D and Flashy Peaking supposed to stay in the root folder as well?
alright SUCESS lol
now what hahahaha
can't get the ML menu to pop up
make sure of 2 things.
1. card is bootable
2. you renamed the bin to autoexec.bin
you have 2 different versions there
oh and here is a frowny browny:
LVx1_GetVramParam(W:1620 H:1080)[ff0c0fd4]
this means hdmi output is only 1620x1080. taking a lv screen shot and cropping it confirms its not CRAW buffer sized.
so I should try to install again for the 2nd time nameing autoexc with .bin
and should I use the autoexec that comes with ML or the one located on bitbucket?
or use both and add .bin to the bitbucket version?
lol, the one that come with it is from 2.3 6D didn't even exist. :o
you only have to do the firmware thing once. After that you just copy over the autoexec.bin
structure is:
/ - FOLDER
autoexec.bin
ML -FOLDER
- ini files/help/config files
DCIM -FOLDER
- pics go here
the bins are renamed because I can't upload 50 autoexec.bin files and a history of previous version is good when you need something that worked before or features that changed, etc
just curious, but why is there a autoexec on bitbucket? they are different sizes from each other
alright, I've done it what I believe to be "the right way"
now I can't figure out how to load the ML menu
well the first one can be named autoexec.bin so that is the first bin i compiled.
since we add/remove things the binary size changes (up to 500kb). autoexec.bin *is* ml the rest are just support files. the fir just enables the boot flag and nothing else. The reason 2.3 bin is so big is because it all of the camera autoexec.bin put together into one. since this is the 6d port its only the 6D bin.
ml menu should load on erase
I am having some exact problem. I get to the page where it says success and when I restart nothing happens. erase does not respond
Are your cards set bootable with eoscard?
the fir set the boot flag in the camera (it will load bin from bootable cards)
eoscard sets boot + develop flag for the individual cards
when you reboot it will ONLY start if you already made the card bootable and copied all the files.
so disable bootflag at the "success" screen?
sorry for being a noob
i'm just not trying to destroy my $2000 camera
2 weeks ago I killed my $1000 nvidia geforce 690 lol
what is the process to make a card bootable?
yes, it is. I just checked. Im still confused to as what to rename to what. I put 6D-112.fir from this thread. I copied it to the rood of my card. I extracted ML 2.3 and replaced the old autoexec.bin with the one from bitbucket. Then I put all the fines (except for autoexec.bin) to ML folder. Then I updated and it says success: "BBOTDISK flag enabled AUTOEXEC.BIN found. Magic lantern Installed you may restart". But when I restart nothing happens, and erase does not work
You have to download EOScard. I got it from the original ML website
Ops, I may have lied. I just double checked and DISBOOT.BIN is not comming up in EOScard. What do I do?
ive now made it bootable, still no luck
autoexec.bin is named exactly that, nothing after it? and its in the root folder/
http://pel.hu/eoscard/
set eos-develop and bootable
bad new folks, camera won't turn on now
even after i take battery out
o no...
i'm going to charge my battery for a bit and see what happens.
when I ran EosCard It created a new (2nd) autoexec on the card? I'm guessing it stays
I think this whole thing would be easier with a detailed step by step guide. just not know to add a .bin on the end of autoexec can throw the whole thing off
1 bin at a time.
not starting with card in is good (bootflag is set, card i bootable). take out the card and the battery. put back only the battery but close the card door. should start up now.
eoscard should not write any bin to your card.
the steps are the same as any other ML
nope, camera is dead
but it did, it took about 10 seconds to transfer files to SD, and then it created a new autoexec
EOScard did write some files. Im glad I checked
i'm thinking eoscard is what has F'd my camera
BACK ON!
JESUS CHRIST that was a close call
lol...
its kinda ODD that 2 people are having the exact same issue
we get get the "success" screen, and nothing after that. and I would guarantee we are both following the steps exactly
eoscard isn't supposed to be writing files just setting flag on the card. bin are the same as i run here. so i dunno what you did. it the same as setting up ml for any other camera.
I originally had trouble setting the boot flag in the camera and getting the fir to be recognized but that's it, no troubles since then.
http://wiki.magiclantern.fm/install
you jut need autoexec.bin (named autoexec.bin) from the repo and fir from this thread in place of the ones from 2.3. i dunno how to explain it any simpler :(
when I hit SAVE in EOS card it writes the ML files.
follow all the steps as earlier and replace autoex with the autoex from the 6d download page?
but it is writing files..the ML files
So if I understand correctly:
Firmware update.
Step 1. Make SD card bootable with EOScard (EOScard is not suppose to create bin file on SD Card)
Step 2. Download 6D 112 fir and copy to SD card.
Step 3. Download ML 2.3
Step 4. Download files from bitbucket
Step 5. Add .bin to autoexec from bitbucket and copy/transfer it to SD Card
Step 6. Copy/transfer all other files downloaded from bitbucket to ML folder from ML 2.3
Step 7. Copy/transfer ML folder to ROOT folder on SD card.
Step 8. Use EOScard to make boot flag with 6D 112 fir?
Step 9. Insert SD card in camera. Start camera. Press ERASE to start ML. Reboot. Done.
Is that right?
The only thing I'm not sure is 6d 112 fir as boot flag. What does that mean?
I give up! I will wait for Alpha. Thanks 1% for your help. Sorry if we where pain :)
I think you left out doing the firmware update?
Everyone involved here is awesome. I only wish that I could help somehow. I took my camera out in a snow storm at night last week and was amazed by the results. Really a step above my 600d. Plus with my 105mm f2.5 it was bokeh heaven. I can't wait for the alpha to be released, magic lantern for the 5d mk ii was awesome to work with.
I only wonder why the moire is still so present when it has been eliminated from the 5d mk 3. I feel like integrating the electronic level with the video could be interesting too. Trap Electronic level shutter? And of course, if someone could write an app for the iphone (maybe that will be me) that works with video as a follow focus that would be unreal.
I GOT IT TO WORK!!!!!!!!!!!!!!!!
what? how?
Step 1. Format SD with PC then Make SD card bootable with EOScard (delete anything it writes to SD)
Step 2. Download 6D 112 fir and copy to SD card. (located at in the first post of this topic)
Step 3. Download ML 2.3
Step 4. Download files from bitbucket
Step 5. Add .bin to autoexec from THE bitbucket VERSION only, copy to SD
Step 6. Copy/transfer all other files downloaded from bitbucket to ML folder from ML 2.3 (leave AUTOEXC PEAKING / HBR on root)
Step 7. Copy/transfer ML folder to ROOT folder on SD card.
Setp 8. Install Firmware like normal
Step 9. Turn camera off and back on.
you will know it worked because you will see new items on the display
if it doesn't work the first time, try again, but don't try anything different
gravita. What about the boot flag (6D 112 fir)? Just copy it to SD card and that's it?
Heh, you'll have to do the same stuff to the alpha more or less.
1. copy canon firmware update to the card, run it. now your camera is at 1.1.2
2. copy 6dfir from this thread to the card
3. put camera in M mode and run the 6dfir just like you did with the canon one. it should give you the green screen and say ml is intalled, yada yada
4. take out the card; you're half way there
5. download ml 2.3 zip file and extract it to a folder on the desktop
6. copy ONLY ml folder from what you extracted and put it on the sd card
7. download bin from bitbucket, rename it to autoexec.bin
8. copy autoexec.bin named only autoexec.bin not autoexec.bin.someshitiwrote to the sd card
9. copy ini files to ML folder on sd card
10. run eoscard and select only boot flag and eos develop, hit save
Now it should run.
Here is where I see the problem (and why you crashed). Pel updated newest eoscard to make it place ml 2.3 or some other bins to the root. Easier for some, PITA for others. You *could* just install 2.3 and overwrite autoexec.bin if you loaded the fir files already.
my older version of eoscard ONLY set the flag. the easy way to check is to see the size of autoexec.bin and compare to what you downloaded from bitbucket
mine looked like this http://vimeo.com/38964397 (at ~1:19) so i guess look for v1.2
Quote from: ManixLiquid on January 26, 2013, 04:12:26 AM
gravita. What about the boot flag (6D 112 fir)? Just copy it to SD card and that's it?
yes
and leave it running obviously
i really think I got lucky
ML wasn't loading after I installed the firmware
while leaving the firmware installed
i formatted the card using the PC, then eos card
then followed all the instructions as I posted
then and only then did it work after I did a 2nd format of the SD
not sure what would have made the difference
@ 1%
is the alpha ready? or are you saying when it is released?
I'm new here, hello everyone. It's been laid out quite well in the past few posts, but I already started typing... I've never used Magic Lantern before but I got it working fine last night using this method:
*Make sure you start with Canon firmware v1.1.2
*Format SD card using camera
*Download the .fir from the first post (http://www.magiclantern.fm/forum/index.php?topic=3904.msg21154#msg21154) of this thread and put it in root of SD
*Download the latest autoexec.bin from https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads . Rename it to autoexec.bin and put it in root of SD
*Download the main Magic Lantern 2.3 (http://www.magiclantern.fm/download) zip and extract the ML folder to the root of the SD card (i.e. there should be a folder called ML in the root of the SD)
*Open EOScard and click the ML button. Your settings should now look like this:
*Put the card in the camera and update the firmware using the .fir
*You will see the black and green installation complete screen. Restart the camera.
The ML menu is accessed using the erase button.
I do embedded development for a living and might be interested in helping with development on the 6D once I familiarize myself with magic lantern some more.
I also just looked at the first test clip, it MAY be because of the camera settings
but at bitrate 40 I see squiggly lines in details, is their another setting in ML I should
change when the bit is increased?
Yeah...!!! I got it to work. The only different thing that I did was that I formatted in camera with Low Level and it worked!
set one of the configs to autoload, don't just set bitrate.
bitrate and initqp will only give you CBR at one fixed quality, good i guess if your card can keep up. 40 is also 400Mbps target rate. if you really want to go the constant route set a qp between 5-15 and bit rate to 10
don't change bit rate for VBR as max bit rate and target have to match or you'll have to pull the battery (to be fixed once i figure out how to hard reboot the camera)
all you have to do is set autoload to on and pick a config (that you should have put in ml folder)
you can edit the with a text editor. hoping to be able to set all these in the camera at one point but they seem mia from the firmware and its like the encoder is a separate processor/core/etc. i only see the 2 parameters in memory
Quoteis the alpha ready? or are you saying when it is released?
this is where we're at. the only difference with alpha is that features that are gimpy or broken are turned off. i.e if you select alpha blend peaking or anamorphic on the most recent bin you'll see it bouncing, etc. for a release this would be missing option from the menu but i want to fix it since its working fairly well on 600D (i think LV or HD buffer is changing/refreshing and it not getting drawn fast enough or to the right buffer; but all 3 of us with 6D care or have even seen it)
@dube
I would agree that formatting IN CAMERA may solve some issues. I didn't go this route, but I can see why it would work. Its what i was going to do initially but was told otherwise, either way, It still ended up working.
I have to leave for 20 min. I'll be back to help to the best of my ability
Can someone confirm: Magic zoom - full screen not working properly or is it just my cam.
Quote from: DTSET123 on January 26, 2013, 05:01:05 AM
Can someone confirm: Magic zoom - full screen not working properly or is it just my cam.
I would say it's NOT your camera
i'm sure there is a few things that still need some work
that is a confirmed bug. it looks just like full screen zoom on 600d in crop mode.
something is wrong here:
EngDrvOut(0xc0f140e8, vram_hd.pitch - vram_lv.pitch);
or the offset of the HD buffer is wrong and that's why it drawn all squashed.
just did a test a 30 bit (roughly 125 mbs) and it looks pretty dang good
tomorrow I'm going to experiment with a extreme pro 95mbs card and see what happens
1% and Gravitatemediagroup thanks for help!
not sure how much help I really was, I think we all kind of helped each other
1% i'm sure was thinking 'why the hell can't they figure this out" lol
Im trying to understand best settings that my card can write. If I understand it right the idea is to record CBR at highest possible Bit Rate with lowest QP with autoload: on - right? Am I understanding this right? Also, I remember one of the guys saying that IPB may be better over All-I?
I think the very first post of this topic should include the steps like this
BEFORE YOU BEGIN, MAKE SURE FIRMWARE 1.1.2 IS INSTALLED
Step 1. Format SD card from the camera then Make SD card bootable with EOScard (delete anything it writes to SD)
(try formatting SD card from PC then EOScard if the rest of the steps have no results)
Step 2. Download 6D 112 fir and copy to SD card. (located in the first post of this topic)
Step 3. Download ML 2.3 - http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
Step 4. Download files for 6D from bitbucket - https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Step 5. Add .bin to autoexec from THE bitbucket VERSION only, copy to SD (delete any other autoexec that didn't come from bit bucket)
Step 6. Copy/transfer all .INI files downloaded from bitbucket to ML folder from ML 2.3 (leave AUTOEXC PEAKING / HBR on root)
Step 7. Copy/transfer ML folder to ROOT folder on SD card.
(remove all the other .FIR files and the 6D .FIR file should be the only)
ROOT OF SD SHOULD CONTAIN THESE FILES AND LOOK LIKE THIS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ML FOLDER (put the .ini files from bitbucket here)
6d-112.fir
autoexec.bin (don't forget to add .bin)
autoexec.bin-EXT-HDR-6D
autoexec.bin Flashy Peaking
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
if this looks right, insert SD card to camera
Setp 8. Install Firmware like any other firmware & DON'T do anything until you see the SUCCESS screen.
Step 9. Turn camera off and back on.
you will know it worked because you will see new items on the display
if it doesn't work the first time, try again, but don't try anything different
_______________________________________________________________________
WHEN ALPHA IS RELEASED
1. copy canon firmware update to the card, run it. now your camera is at 1.1.2
2. copy 6dfir from this thread to the card
3. put camera in M mode and run the 6dfir just like you did with the canon one. it should give you the green screen and say ml is intalled, yada yada
4. take out the card; you're half way there
5. download ml 2.3 zip file and extract it to a folder on the desktop
6. copy ONLY ml folder from what you extracted and put it on the sd card
7. download bin from bitbucket, rename it to autoexec.bin
8. copy autoexec.bin named only autoexec.bin not autoexec.bin.someshitiwrote to the sd card
9. copy ini files to ML folder on sd card
10. run eoscard and select only boot flag and eos develop, hit save
Quote from: DTSET123 on January 26, 2013, 06:19:20 AM
Im trying to understand best settings that my card can write. If I understand it right the idea is to record CBR at highest possible Bit Rate with lowest QP with autoload: on - right? Am I understanding this right? Also, I remember one of the guys saying that IPB may be better over All-I?
what card are you using?
SDHC Patriot LX Series 32gb
what speed is it
if you are going to be using ML for some high bit rate stuff
the only suggestion I can make,and they aren't cheap is sandisk extreme pro 95mbs
I'm still having an issue with ML where sometimes the camera won't turn on.
I'm guessing to use a different SD card with ML you have to start from scratch, and run the same process
with the new sd card?
For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML, see below).
If you use SD/SDHC/CF cards, you may simply repeat Step 2 on every card you would like to use Magic Lantern.
If you use SDXC cards, or if you prefer to skip the firmware update step and prepare all your cards from the PC, you may copy ML files on your card and make it bootable with a special utility: EOScard for Windows, MacBoot for Mac, or make_bootable.sh for Mac/Linux in command line.
Basically, you have to install ML on every SD card you want to use ML on. Just repeat all the steps on your new card.
Am I correct in thinking that autoboot is not enabled on the 5d mark3 alpha and the 7d alpha. Why is it safe to use on the 6d?
It's just as safe (or unsafe) as on the other cameras. It's normal to be a bit cautious when the camera body is more expensive (5D3), or when the boot process is quite different from what we already know (7D).
Quote from: gravitatemediagroup on January 26, 2013, 04:09:27 AM
Step 1. Format SD with PC then Make SD card bootable with EOScard (delete anything it writes to SD)
I cannot get eoscard 1.32 to work, it starts to write then comes up with an error
Cannot create file Ï:\ML\README¨. The system cannot find the path specified.
should I select
Unified stable release v2.3
or
Ports in progress
If you want to make the card bootable you only have to check the EOSDEVELOP, BOOTDISK and SCRIPT flags. (and then hit save)
@sparedog
are you clicking refresh in top right corner to make sure it's located on your card
and there is no other cards inserted into your pc?
Quote from: gravitatemediagroup on January 26, 2013, 05:31:53 PM
@sparedog
are you clicking refresh in top right corner to make sure it's located on your card
and there is no other cards inserted into your pc?
Quote from: nanomad on January 26, 2013, 05:26:02 PM
If you want to make the card bootable you only have to check the EOSDEVELOP, BOOTDISK and SCRIPT flags. (and then hit save)
Sadly I am doing both of these things, and no success. After I press save, Eoscard updates the message at the bottom of it´s window that says ¨write succesful¨, but ML still doesn´t come up on pressing erase (the dustbin/trashcan button right? lol)
On the ML Success! screen, which is green writing on black screen, In white writing in the bottom right hand corner, there is the following.
firmware 0
bootdisk-1
RAM_EXE -1
update -1
What should this reed to know if the disk has succesfully been made bootable?
Quote from: ManixLiquid on January 26, 2013, 02:14:46 PM
For first install, use a simple SD/SDHC/CF card (32 GB or smaller). 64GB cards and larger will not work for first install (but you can use them with ML, see below).
If you use SD/SDHC/CF cards, you may simply repeat Step 2 on every card you would like to use Magic Lantern.
If you use SDXC cards, or if you prefer to skip the firmware update step and prepare all your cards from the PC, you may copy ML files on your card and make it bootable with a special utility: EOScard for Windows, MacBoot for Mac, or make_bootable.sh for Mac/Linux in command line.
Basically, you have to install ML on every SD card you want to use ML on. Just repeat all the steps on your new card.
Tried this with a 32gig extreme pro, no luck
sparedog
you will turn camera off and on and you will then notice things look different
if it doesn't work, follow the steps exactly the same. it took my about 10 times last night before the camera finally just "worked" out of nowhere.
don't lose hope yet
but start from scratch
are you formatting sd from camera or from PC?
Quote from: gravitatemediagroup on January 26, 2013, 05:52:40 PM
are you formatting sd from camera or from PC?
I formatted from pc on a slow format, then after in camera, but not low level. I will try again with a low level camera format.
To be honest I suspect it is eoscard, as it hangs when I try to close it. I´ll try re downloading it.
Your instructions were clear and easy to follow, and I get the green/black success screen everytime. its just making the card bootable that´s tripping me up.
NEW THEORY??
I had trouble getting the new card to work, and this is what I did, and I think it will apply to anybody having trouble with the initial installs
follow the steps as is, but after you get all the files on the card and ready to load on camera, run EOScard 1 more time and hit save, THEN put the card in camera.
2 times now I have found that using eoscard 2 times in the process seems to work.
ORRRRR........the first eoscard step is unnecessary and only needs to be done as a last step before moving to camera "RUN EOSCARD & SAVE BEFORE PUTTING SD IN CAM"
false alarm, the new memory card finally worked as far as "the camera turned on"
but ML doesn't work
i'm pretty sure I don't need to follow the firmware install again do I?
Working!
It was Eoscard. I downloaded it again, restarted my computer and ran it without changing anything on the SDcard.
Shall try to do a report for the developers tomorrow
tested force 444 on 6d... did not work... must be using different functions. i saw something about hDMI image quality, willl have to investigate further.
in the LV buffer, the black bars are on one side only it seems, at least they are when lv is dumped.
You don't really want to do cbr at fixed qp. it stands a good chance of stopping recording as there is no rate control. VBR is good for lowfi and rc config is good for set it and forget it. that i think is the best part of the new encoding. You don't have to set 1 scene at 2x, just set up the config and it will always encode like that. bit rate and init qp is only there to modify cbr config on the fly. once you set up vbr and rc you don't have to mess with it further, that is their point.
I have to see if min bitrate affects rc because it likes to hover around 60-70 (what I set for min) but goes up to 140 even when it needs it.
you can generate high rate if you want on any mode but most scenes don't require 150Mb/s, the quality won't be much better. if you look at the raw samples i uploaded canon would record the 60mb/s scene at like 20 or 30 which is unacceptable. recording that same scene at qp1 would probably give you like 120mbps or more but its more or less overkill on digic V as it uses high 5.1 profile.
comparing to digicIV, if canon made the 6d sensor in the 600d body they'd have a real winner. only gain for digicV is the stability. I don't see much quality difference between the hacked 600d vids and the 6d vids. especially not $2k difference. either we did a really good job on 600D or canon image quality hasn't changed all that much.
Thanks for all the detailed instructions for the noobies on how to get this build on our cameras without much experience; having ML on my 6D is amazing already! Thanks again!
Quote from: 1% on January 26, 2013, 06:37:34 PM
tested force 444 on 6d... did not work... must be using different functions. i saw something about hDMI image quality, willl have to investigate further.
in the LV buffer, the black bars are on one side only it seems, at least they are when lv is dumped.
You don't really want to do cbr at fixed qp. it stands a good chance of stopping recording as there is no rate control. VBR is good for lowfi and rc config is good for set it and forget it. that i think is the best part of the new encoding. You don't have to set 1 scene at 2x, just set up the config and it will always encode like that. bit rate and init qp is only there to modify cbr config on the fly. once you set up vbr and rc you don't have to mess with it further, that is their point.
I have to see if min bitrate affects rc because it likes to hover around 60-70 (what I set for min) but goes up to 140 even when it needs it.
you can generate high rate if you want on any mode but most scenes don't require 150Mb/s, the quality won't be much better. if you look at the raw samples i uploaded canon would record the 60mb/s scene at like 20 or 30 which is unacceptable. recording that same scene at qp1 would probably give you like 120mbps or more but its more or less overkill on digic V as it uses high 5.1 profile.
comparing to digicIV, if canon made the 6d sensor in the 600d body they'd have a real winner. only gain for digicV is the stability. I don't see much quality difference between the hacked 600d vids and the 6d vids. especially not $2k difference. either we did a really good job on 600D or canon image quality hasn't changed all that much.
So you're saying filming with higher birate on 6D with ML won't make a difference even without ML installed?
Agree with all the people thank you for give us the chance to test ML on 6d, i'm amazed to have ML again. hope to do another donation soon guys, you really deserve all our gatitude and help ;))
great work
I can't install it on my camera.
I followed 1% instruction on page 8. ML installed. I restarted the camera but it wouldn't boot.
I removed SD card and battery. Try to put them back in. No boot. I only put battery back in with another sd card. Camera boot.
But every time I put the SD card where I copy all ML, ini, autoexec, etc files in the camera, it doesnt boot.
I formatted that SD card but in back in the camera with all ML sutffs and camera boots.
I then followed gravity methods, same problem. Either the SD card is damaged or I'm doing something wrong.
QuoteSo you're saying filming with higher birate on 6D with ML won't make a difference even without ML installed
I'm saying that at some point its diminishing returns. Basically don't just record CBR 120mb+ when the scene will be the same at 70. Stock rates are actually pretty terrible.
if the camera didn't boot and you had the bootflagS set on both card and camera you probably have the wrong bin. don't try to use the 2.3 bin. make sure eoscard didn't overwrite it with its own.
when you formatted the card you took of the boot flag so it stopped trying to load the wrong bin.
Ok. I installed ML on me camera but I can't find the ML menus. I pressed the trashcan button. Nothing.
I used ML all day today. Shot a breast cancer walk event where thousands of people walked to raise awareness, and I did not have any problems with ML. I was using H.264 configuration thou. Question: is H.264.ini modified or is it canon's? Also, changing bit rate and qp on RC.ini will influence the recording or they dont effect it (are those only for CBR)?
Today was a very bright day here in Florida and it was very difficult to see, and I wished the full-screen zoom on half-shatter worked or at least on focus like on 5Dm3. Other then that it was a pleasurable experience. Thank you guys for all your hard work. I will be donating to ML project as soon as I get paid :)
card isn't bootable if you formatted it.
you ran the fir successfully before and set the flag on the camera, right?
H.264.ini is scratch file for you to customize, I don't remember what i put there, probably stock or rate control.
bitrate is just a target rate.
VBR has min/max BR (must match target) and high+ low qps (may not stay within them)
RC uses the min/max qps only i think. if you set the target lower it will try to stay under it. if you set it higher it will just record what it can
don't change initqp from -1 on the dynamic configs because then they just record at that 1 qp and become cbr
RateControlEnable = X this line sets the mode. VBR/CBR/RC
Those .ini files are for us to play with? OK, i see. I think thats what GH2(3) hackers are doing: they configure their own settings and then they share those files. 1% from your own experience so far, which compressions looks SEXIER All-I or IPB whit RC.ini?
Quote from: 1% on January 26, 2013, 10:54:51 PM
card isn't bootable if you formatted it.
you ran the fir successfully before and set the flag on the camera, right?
Every time I run the fir file from ML link you posted, it says ML/DADA/FONT retry not found and to copy ML files to card.
@manixliquid
have you tried a different SD?
Ok. I tried a different card. I format on my PC. Then format it with the camera (low level). I put the Card on card reader, copy the 6D 112 fir file on the card.
I put the card on the card, update firmware. Now it says "Update file cannot be found. Please check the memory card and reload battery and try again.
I give up. I tried everything, follow instructions carefully, still nothing. It just doesnt work.
put the card on the card
1% is there any area you would like us to test specifically.
for example, if i concentrate on testing everything in the focus and exposure menus and write my results, is that helpful, or do you know what the results will be already?
Quote1% is there any area you would like us to test specifically.
for example, if i concentrate on testing everything in the focus and exposure menus and write my results, is that helpful, or do you know what the results will be already?
Yes, good question. What would you like us to do?
look for other things that don't work besides what is posted in this thread and I guess do some video tests and see how the quality is affected in real world application. are there repeatable crashes, especially for stills shooting. see if time lapse intervalometer and bracketing work as they should, etc.
right now I've shot some samples to get it working but that's it. Nobody has been pixel peeping the videos yet.
focus info is broken, the property is different. but other stuff like FF should work, etc.
Great work so far!
Focus peak: In display type only blinking dots seems to show anything on the screen
In each type of LiveView focusing mode FLEXIZONE/LIVEMODE/AFQuick, ML menu screen flashes once after about 5 seconds after pressing trash button...
BUT
In AFQuick focusing mode
After the 5 seconds the screen flashes, however the menu is no longer usable, but it still stays on the screen. The focus points appear on the screen conflicting with the ML menu.
It is so good to have zebras and magic zoom!!
Is it possible to have magic zoom always on and zebras work at the same time
In the right corner: what is the difference between A and B? And what is next to it xx%
still trying to get a 2nd SD card to work.
Do I need ALL of the exact same files as required for the initial install
or does something need to be removed because the ML firmware is already loaded on the camera and the new SD and Cam are causing confusion with each other?
Getting a second card to work is more frustrating that the initial install lol
I dont think ML writes on camera. I think you still need to put ML-6D112 on to your sd
so leave ML-6D112 and ONLY 6d112 or what?
I deleted the ML folder and it was a fail also
that didn't work either (leaving the .fir by itself)
this is INSANE that this is so difficult to get a second card capable
i'm not even joking when I say it's more difficult than initial install
20+ attempts/variations and still no luck
install took make 8 to 10 trys
I need some serious help before I throw my 6d out the window and rob a bank for a c500
are alpha versions this difficult?
autoexec.bin and other ML files have to be on the card. card has to be bootable. that's all there is. you only have to do the fir once. after that you can delete it.
[/quote]
After the 5 seconds the screen flashes, however the menu is no longer usable, but it still stays on the screen. The focus points appear on the screen conflicting with the ML menu [/quote]
in latest bin?, i can't reproduce this. it comes up instantly for me in all the modes.
QuoteIs it possible to have magic zoom always on and zebras work at the same time
mz disables the other overlays. I don't think it can zebra + peak + MZ at the same time. i don't believe any of the other camera do this either.
QuoteFocus peak: In display type only blinking dots seems to show anything on the screen
Latest bin (flashy peaking) it should be flashing in occasionally. turn on anamorphic, they draw the same way and redirect the buffer. The only usable mode right now is the blinking dots. Ironic because the new modes came from 5d3.
The corner has average bitrate, instant bitrate, buffer fill % and time indicator.
ok, well....the latest bug report will have to be ML does not work with extreme pro 95mbs cards
as ANYBODY else tried using ML with a different/second SD other than the one they use to set up the first time around?
if so, I challenge them. Just tried it with a card other than sandisk Ext Pro and it also doesn't work
i've made it bootable
i've done EVERYTHING exactly how I did to make ti work on the original SD card
some methods I try attempting a 2nd memory card will turn the camera on, some methods WON'T turn the camera on.
I dont know whats wrong but here are the steps that I did:
1. Low level format the sd and run through EOScard (delete anything it writes on to the card)
2. put ML6d112 on root
3. copy ML2.3 (root) and delete autoexec.bin from (root)
4. put all the new files to ML folder (except aoutexec, flashy and HDR - those go to root)
5. Update, after success message restart and then pray
Thats how I did it
Note:
I also renamed autoexec.bin to same exact thing "autoexec.bin" and then PC says that you are about to change file "bla-bla" I press ok. I dont know if that did anything but my ML is working.
See if you guys are doing something else...
1% says the .FIR isn't necessary, i've tried with it and without
dtset
are you refering to your FIRST time you did the install
or this is what you have done to get a SECOND SD card to work?
Quote from: 1% on January 27, 2013, 03:58:14 AM
in latest bin?, i can't reproduce this. it comes up instantly for me in all the modes.
I was using EXT-HDR-6D, I will try with flashy peaky tomorrow
fir is only the first time you install, ever. subsequent sd card just need eoscard and the files
coutts has the sandisk pro 95 mb, guess its working
Quote from: DTSET123 on January 27, 2013, 04:08:31 AM
4. put all the new files to ML folder (except aoutexec, flashy and HDR - those go to root)
These are just newer versions of the autoexec file, that' s what they mean by rename to .bin.
On your sdcard, delete the current autoexec.bin and autoexec.binEXT-HDR-6D and move autoexec.binFlashy to root and change from .binFlashy to .bin
nobody is answering my question
has anybody got a "SECOND" SD card to work. NOT the original SD that was used to install ML?
sorry double post
Quote from: gravitatemediagroup on January 27, 2013, 04:23:17 AM
nobody is answering my question
has anybody got a "SECOND" SD card to work. NOT the original SD that was used to install ML?
I will try for you now
1% I know we are driving you crazy but we are learning and hopefully will be of some assistance.
when modifying .ini files what are the things that we can change and what should we not touch?
I have a slower card (max: All-I write speed in h.264 is 70-75bm/s) and when I try to use cbr.ini it stops recording. can i change Bit Rate in the cbr.ini file to say 75000000?
do I need to disable the boot flag with the original SD before a different one can be used?
Quote from: gravitatemediagroup on January 27, 2013, 04:27:00 AM
do I need to disable the boot flag with the original SD before a different one can be used?
OK, so it worked straight away with another card, a class 4 sandisk 4GB
Heres what I did.
format card low level in camera
Take autoexec.binFlashy and renamed it to autoexec.bin
drop onto root of card
drop ML folder onto root.
drop inis into ML folder
Finally run Eoscard 1.32 and turn on EOSDEVELOP + BOOTDISK + SCRIPT and press save
That worked for me, hope this helps
I didnt do anything with the camera, like disable the boot flag with the original SD. I just swapped the cards and it loaded straight away
QuoteBit Rate in the cbr.ini file to say 75000000?
yep and raise initqp.
where cbr is useful... fps override for time lapse. when you drop the frame rate you can record qp1. maybe a nice way to compare quality... take a silient pic while doing 1fps in override
@sparedog
how in the hell?
still not working for me
I think I got it
WTH
I have no idea why that process is so much different
I think renaming the flyshy file did it
@gravitatemediagroup & @DTSET123
Some help, maybe: http://www.magiclantern.fm/forum/index.php?topic=2522.0
Ghost Image: Overlay is only quarter of screen. I cant work out how to make it full screen
[edit]
also Gradual exposure has flickering in bottom part of recorded clips when aperture changes.
Quote from: 1% on January 27, 2013, 03:58:14 AM
After the 5 seconds the screen flashes, however the menu is no longer usable, but it still stays on the screen. The focus points appear on the screen conflicting with the ML menu
in latest bin?, i can't reproduce this. it comes up instantly for me in all the modes.
Yes even with Flashy.
Change focus to AFQUICK
Bring ML menu on screen
after 5-10 seconds, ML menu becomes unusable
Defishing and anamorphic dont draw correctly
Are custom focus patterns available in this version of ML? I can´t seem to find an option for them
QuoteAre custom focus patterns available in this version of ML?
Not yet, they break af when i tiried to use them.
Quoteafter 5-10 seconds, ML menu becomes unusable
i see the af points go on top and you can't work the menu. half shutter fixes it though, at least temporarily.
QuoteDefishing and anamorphic dont draw correctly
Same as the new peaking. they are drawn the same so the same bug.
Ghost image looks fine to me at first, then bottom bar draws over it and takes a line out. i tried a video and a raw
lol, it looks like we have some drawing bugs.
seems if you do the gradual expo it changes the aperture first then goes back to gradual expo o the frame gets dark for a sec and then starts the gradual expo sequence. most visible on the bottom. heh, i should make a list of these and what I've attempted to do to fix them. all seem related to canon drawing fighting with ml actions and drawing
Ok. ML works on my SanDisk 64GB SDXC extreme card. I followed sparedog instruction. It seems ML was installed on my camera all this time but it wouldn't boot from my 32GB card where I make installed 6D 112 fir, eoscard boot flag, etc.
Now I just need to find how to select resolution (1080p) and record display (record notification and time.
I looked into the gradual ISO bug... it is present on all cameras. There is no aperture handling in the gradual iso code. it only does shutter and iso. it flashes on my 600d too.
*Its stuck on now forever. I went to the store and played with a 650D, the servo af is just a toggle in the menu. When I turned it on and moved the camera, the af didn't move. I couldn't record as they had no cards in the cameras. So same behavior as 6D. I don't know how to use this fucking thing.
*Here is ghost Image and how it looks for me with a raw pic queued up.
Gradual exposure should handle ISO, shutter and aperture changes (all 3). If it doesn't, check FRAME_BV (it should react to all 3 parameters, Bv = Tv + Av - Sv). It's also nice to have CONFIG_FRAME_SHUTTER_OVERRIDE, helps with reducing pink highlights.
When you change aperture, it's normal to flicker, because aperture is some slow mechanical device.
I thought frame BV could be wrong, it has to be checked. I will try the frame shutter override. It was in 5d3 internals.h and didn't know I could turn it on.
*ok, slightly less flickery. will look at BV, its the same as the one displayed, right?
BV seems to match the math. It can be negative, right?
Canon keep overriding the 1/8000 shutter when I use it, I can only get it on for a short while even with override. But all shutter values between 1/4k and 1/8k change the LV.
Here is a vid of the anamorphic/new peaking drawing bug. This is without redirect display buffer easily. Otherwise you see nothing:
(http://videobam.com/rIcED)
Probably related to the info screens not drawing on the photo display too.
Can't watch, I only get a ton of ads and popups (both ff and chrome).
You need to define CONFIG_CAN_REDIRECT_DISPLAY_BUFFER_EASILY and make sure you can redirect the display buffer by changing YUV422_LV_BUFFER_DISPLAY_ADDR. This trick only works when called from display state object, from the right spot.
e.g. this will work (and will display gibberish):
stateobj_spy()
...
if (self == DISPLAY_STATE && input == INPUT_ENABLE_IMAGE_PHYSICAL_SCREEN_PARAMETER)
YUV422_LV_BUFFER_DISPLAY_ADDR = rand();
but this will not work (maybe just occasional flicker when it catches the right moment):
run_test()
{
while(1) { YUV422_LV_BUFFER_DISPLAY_ADDR = rand(); msleep(10); }
}
If you don't define CONFIG_CAN_REDIRECT_DISPLAY_BUFFER_EASILY, it will probably flicker a lot. You will have to find some other hack for changing the liveview image address. See display_filter_lv_vsync and display_filter_get_buffers - those two should work in pairs, one does the hack and redirect the buffers, and the other one tells the buffers that should be used - source and destination image.
Nothing is displayed if I enable redirection. The new peaking overlays do end up in photo review after I take a picture. I'm pulling the LV address from the register and I think it goes into LV buffer 1 per the code. I think the redirection part is what doesn't work except for photo review.
Should I try to find actual BV like it is on 60D? Found frame shutter timer in 600D (ext HDR works). Seems not many cameras have frame bv location and just do subtraction.
I am looking for a video host now that doesn't need a signup and will actually upload. I'm on wifi so the uploads like to time out.
Also its hard to see but flexinfo actually draws over LV and you can see LV moving in the transparencies. On the photo screen it still has LV artefacts in the transparency and never draws what it actually is supposed to. So our LV buffers are switched or wrong order? Or the register returns the wrong thing?
(http://imgur.com/bBk8ybB)
(http://imgur.com/HWR1Vwk)
Quote from: 1% on January 27, 2013, 10:33:28 PM
I am looking for a video host now that doesn't need a signup and will actually upload. I'm on wifi so the uploads like to time out.
You could sign up to hushmail, and use that to sign up to vimeo. Its a bit of a tedious solution process, but at least that way your normal email addresses wont be flooded with spam. I´m pretty sure someone else can come up with a better solution =D
Is it possible to make an option to set the LumaFast zebras´ alpha?
I like to shoot with the monochrome picture style on the LV whilst recording in a color picture style.
So I think I could get away with setting the alpha of lumafast zabras very low, maybe as low as 20%, as it would be the only color on the screen (except when using focus peaking, etc)
Sparedog why would you want to see in monochrome while recording color? Just curious, what's a benefit of that?
Quote from: DTSET123 on January 28, 2013, 02:43:56 AM
Sparedog why would you want to see in monochrome while recording color? Just curious, what's a benefit of that?
I do that with RAW pic to have a better control of forms, framing etc. without colors distraction
Quote from: scrax on January 28, 2013, 10:22:21 AM
I do that with RAW pic to have a better control of forms, framing etc. without colors distraction
Its a throwback from shooting with television. Older tv cameras often had a monochrome electronic viewfinder, and as scrax says, some people find it much easier to control focus, framing, exposure etc. I scan the scene for color with my naked eye.
Once you hit record on the camera, ML automatically changes the picture style to the chosen color one, so whilst recording the viewfinder is in color. It´s only during setup and framing, but I still find it suits my working style better.
Zebras got turned into zebras in latest commit. I have to see how it looks. This would apply to all cameras not jut 6Db
*made the bin... i think it does more of what you want. The blinking dots peaking is a little less all over the place too. if you turn on grayscale image only zebras and peaking will show up.
Quote from: 1% on January 28, 2013, 06:31:02 PM
Zebras got turned into zebras in latest commit. I have to see how it looks. This would apply to all cameras not jut 6Db
*made the bin... i think it does more of what you want. The blinking dots peaking is a little less all over the place too. if you turn on grayscale image only zebras and peaking will show up.
I like the zebras much better in this new version.
Also on FastLuma Zebras, would it be possible to put in an option to show both highlight and lowlight at the same time, instead of the display flickering between the 2?
I think that was done for CPU reasons. they do look more classy now :)
I cant seem to get the Arrow / Set shortcuts to work, but that might be my own user error. The buttons just move the focus box around, and dont change the white balance
So yesterday I was checking out the .ini files and I got RC (no modification) to record stable at 75bm/s (average) in IPB compression on my Patrion LX card, but cant determine if it is any better then regular All-I. My settings were:
Bit Rate: 8
InitQP: 15
Autoload: on
Config Loaded: yes
Config select: Rate Control
When I tried to lower QP some other values would work but as soon as you start moving the camera it would crash. I guess its because of the nature of IPB and the way it compresses frame to frame. Did anyone tried this and did you see any visual benefits?
QuoteBit Rate: 8
InitQP: 15
don't set these from the menu for rate control or vbr or it will record at fixed qp. initqp and bitrate shouldn't actually be set unless you do autoload override though so you kinda lucked out, changing these should have done nothing. :)
hehe, another bug too, lv power save key puts the display to sleep and it wakes up right away.
I think i have an idea on why peaking won't draw.
canon changed the buffer override function to SetImageOverrideParameter
it used to be EnableImagePhysicalScreenParameter
how do i find out what INPUT_ENABLE_IMAGE_PHYSICAL_SCREEN_PARAMETER should now be?
I finally got ML installed on my 6D last night with your new autoexec.bin from yesterday. Great work so far.
Remote shooting via WIFI(Using the smartphone) crashes the camera hard. This is repeatable.
Also I noticed that Zebras and focus peaks don't work in LV if WIFI is turned on.
Lol... Thank you for clarifying that! I spent two hours outside trying to figure it out lol... at least I got a nice tan :)
In theory thou, shouldn't IPB at higher bit rates compress better then All-I? YES, NO or MAYBE?
yea, all I is kinda disappointing. IPB at the higer rate should get you better quality according to h.264 theory.
i have to try out the wifi again with my phone and see what happens with those crashes. It turns off movie mode, it may do other funky stuff.
hmmm.. none of the overlays work when wifi is enabled
but new peaking is fixed
Quote from: 1% on January 28, 2013, 10:01:58 PM
yea, all I is kinda disappointing. IPB at the higer rate should get you better quality according to h.264 theory.
I don´t know, I am liking All-I. I like the grain, so long as there are no visible compression artifacts.
I´m going to experiment with intraframe for a while.
I know nothing about how compression works. With the .ini files that you have provided, is there a way for me to mess about with All-I to get a higher bitrate?
Set the camera to ALL-I and it will shoot all I. you can use the configs for both.
I tried doing fa_movie with wifi on, i can probably kill the dialog and got the rec button back already I think. It switches out of movie mode or something expsim went to off or to photo. Neither the rec button nor FA movie actually started a movie. Or maybe not enough dmas to send to the phone and record? i have to see why its turning off global draw.
dm.log
https://mega.co.nz/#!x4QViQzB!F9Agtl4dmQQqDS11SklHd33cXf9uJ9FCLYIRkyp2pcc
Quote from: 1% on January 29, 2013, 03:24:21 AM
Set the camera to ALL-I and it will shoot all I. you can use the configs for both.
Sorry with the ini files, which one would I change? They all look the same =D
And which bit do I change, or do you mean the options in the ML menu?
ALL I is on the q menu you select IPB or ALL-I or 24p or 30P, etc normal canon thing.
I made the INIs by what mechanism they use to control rate. if you edit RC it will have an effect when you load up RC. some parameters don't work for a given mode.
BTW, full screen MZ works now. I didn't do anything.
how do we know if the latest autoexec is running?
or it doesn't have a choice? lol
1%, how do you select birate with ML? If I want to film at 80 MBps, how do I do that?
Quote from: ManixLiquid on January 29, 2013, 04:47:51 AM
how do you select birate with ML? If I want to film at 80 MBps, how do I do that?
there is an option in the ML menu for it, but you have to change a few other the options below it as well
to shoot at 80mbs i'm gonna guess maybe 15 or 20 is what you should be on
Quote from: gravitatemediagroup on January 29, 2013, 05:02:11 AM
there is an option in the ML menu for it, but you have to change a few other the options below it as well
to shoot at 80mbs i'm gonna guess maybe 15 or 20 is what you should be on
Like this?
Bit Rate: 8
InitQP: 15
Autoload: on
Config Loaded: yes
Config select: Rate Control
yeah, try that
and then do you know how to test what the clips bit rate ended up being?
No, 1% said that unless auto load is set to override the bit rate and qp have no effect at all. From what I understand you should be modifying settings in the .ini files using notepad to configure best settings for your card. I opened RC.ini and changed Bitr Rate and max target bit rate to 750000000. Also, I changed maxqp for all three I P and B to 16 it works but dont know if thats the best setting. I'm still experimenting as I know little about H.264 codecs.
i made changes in camera and when I checked the file I had 80mbs and another was 125mbs
weather it REALLY was or not, my computer was showing them as being that
Well yeah cause it is defined in the ini file target 110000000 and it jumps around. does not mean that u did it. now try set it say 50mb u will see that it will still be recording in high mb/s cause ur not controlling it.
all-i or ipb?
Quote from: gravitatemediagroup on January 29, 2013, 04:28:32 AM
how do we know if the latest autoexec is running?
or it doesn't have a choice? lol
You should have only one autoexec on the card at one time, so it will be the one running. So for example,
download autoexec.bin.FixRedirection
change the name to autoexec.bin
drag that onto the root of your sd card, and it should overwrite the previous one.
Anyone manage to get white balance to work with the arrow/set buttons?
1%, is it possible to display white balance value in Kelvin from auto white balance? That would give a quick ball park figure to work with, when setting white balance manually.
Quote#define ARROW_MODE_TOGGLE_KEY "IDK"
Looks like it wasn't enabled. You should either find a button to enable the shortcuts, or remove that feature from the menu.
If we shoot with high bitrate, we use ipb mode, right?
I'll find a key. we have no disp button so maybe the af button as its kinda useless with no patterns.
Is setting InitQP to 1 the highest bitrate the camera is capable of? In field tests I can record up to 202mb/s with Bit Rate: 0, InitQP: 1
[edit] on a sandisk 30mb/s class 10
Sometimes with higher bitrate recording the camera freezes. Should I take the battery out immeadiately or is it safe to leave the camera to unfreeze itself?
If it freezes, yes. IPB is tricky. If you set high bit rate and it works, then if you point at a complicated scene the buffer fills up an it crashes. The first few frames jump to some ridiculous rates and then it will try to come down to target rate. If buffer does not fill right away you good. Keep in mind the first few frames are extremely high. I have been using star chart bars for testing as it is complex and requires high bit rates to encode the footage. Point your camera at it and try to record, if it does not crash then you good (make sure you hand hold it).
Quote from: DTSET123 on January 27, 2013, 02:58:02 AM
In the right corner: what is the difference between A and B? And what is next to it xx%
I would also like to know this, as it doesnt seem to match recorded bitrate. Is it buffer?
QuoteThe corner has average bitrate, instant bitrate, buffer fill % and time indicator.
if it crashes or starts making bitrate 0 without writing then pull battery or reset. otherwise you'll drain your battery. I'll have to work on that.
Heh, for timelapse you can probably do qp1. The indicators are approximations so they aren't 100% on any camera, its like +/- 10Mb/s or something. Unfortunately we can't open these with bitrate viewer and see the graph yet, even canon stock for the most part.
i did check what it was doing when I could with avi-naptic and thats how i found out RC has a range of 13 QPs, cBr only encodes at 1 QP, vBR picks its own, i think 0-26. and overriding qp (andd usually bitrate) settings turns off vBR/RC qp modification.
Heh, actually want to put the shortcuts on light button but i don't know the name.. I tried "light" but that didn't work, can i just use a button code without the quotes?
The button string is just for help menu; you need to add some handling code in tweaks.c, as each camera has a unique method for these shortcuts.
Quote from: 1% on January 29, 2013, 07:06:01 PM
Heh, actually want to put the shortcuts on light button but i don't know the name.. I tried "light" but that didn't work, can i just use a button code without the quotes?
Putting it on the light button is definately better than putting it on AF button =D
af pattern button it has to be, light button doesn't give an event in movie mode.
Can you hook on AF button?! No other camera can do this.
Pattern button, next to the star. I haven't tried the AFon button or af mode button but i could.
Speaking of patterns, how do we find the right values for digicV cameras? Right now it breaks af. Also, I think the wifi crash is from movie mode being stuck on, reset setting for that mode to fix.
It will not hook on * key, or AF-ON. i guess we can have this button for shortcuts or for zoom if we wanted. Maybe if star or AF-ON are customized they will make unique events. Right now they do 50,54,69, etc.
Ah, the old "zoom in" button. On 5D3, this sends GUICMD_PRESS_BUTTON_SOMETHING (like a few others), so it's pretty much useless. I've tried to detect a double-click on that button to make the camera zoom in, but it still has false positives when you turn the scrollwheels.
I didn't investigate the AF patterns on digic V yet. Check the property values and length, maybe current code expects something else.
current code breaks aF, sets the patterns to some weird pattern.
i have an unpress event only on that button but its good enough for shortcuts. I can do it for zoom in theory and make zoom zoom in or mz come up... then I could use zoom button for the shortcuts... but I think real zoom has more events.
Need to have a way to customize h/S so it either brings up MZ or zoom and same for zoom button. that way people have a choice.
Flexinfo still not drawing for some reason.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/86f5a4cf395bcb8432e425fef98b1d564e32e331
maybe problem is in bmp.h/c returning LV bmp instead of photo screen?
holy fuck holy fuck holy fuck!!!
i dumped ram with wifi on (phone connected but not displaying) and there is a 5k 4:2:2 jpeg in there... maybe several (looking at them now), its only 1.2MB
Quote from: 1% on January 29, 2013, 09:36:41 PM
holy fuck holy fuck holy fuck!!!
i dumped ram with wifi on (phone connected but not displaying) and there is a 5k 4:2:2 jpeg in there... maybe several (looking at them now), its only 1.2MB
I don't quite get all that tech-talk, do you mean there is a 5k video or something? What does qp mean, i'm so confused over all these short for's.
1% what's going on? Talk to us, I'm about to pee in my pants from excitement!
well there are 2 of them, but they came from clicking the shutter (a1ex says it does put the preview in ram). not finding image going to the phone, however. gonna dig through the ram dump some more
Are ISOs lower than 100 available for video on the 6d, and if so are they usable or do they have the pink highlight problem?
Turn down magic lantern and canon digic gain on the iso menu... see how low you can go. You can make all kind of gain reduced isos. I just did 25 but its pink.
Yey, Shortcuts work, thank you!
By the way, the info line says that it is activated with the light button and not the focus points button
level indicator freezes on record
I dont like just writing what does not work, as there is so much that does work very well and is amazing. The amount of work you have done so far has been awesome, ML really improves the 6D!
good catch, level indicator also freezes when you switch between it and the canon menu. I have to find out why, I have it set up like 5d3 with the handler.
Text will be fixed in the next build.
On 5D3, level indicator doesn't work well either (conflicts with Canon's). I couldn't fix it, so I've disabled the feature.
another bit o crappy news, most of the buttons don't give off events while recording. some give you a number in the other fields but the keys are like 54, 69, 51, etc.
there has to be a reason while it stops sending level data or maybe a way to reboot it.
I updated the bits in dispmode param like it was commented out in zebra.c, did not help. Maybe I should cache hack canon from starting/stopping it.
*canon stops it when recording too.
I found a fix or 1/2 the level issue. If I disable it while recording it springs back to life as soon as recording stops. i should clear it from the screen too though.
if you leave it on and F with the canon dialog it will freeze up like that too, this needs a fix. I could cache hack it from starting at all but i don't know if that is a fix.
Ok, I have it working very nicely in movie mode. Problem is in photo mode. I need to disable it before live view closes otherwise it freezes. It can only be on when LV is on otherwise it dies.
QuoteYey, Shortcuts work, thank you!
There is a new bin? Where?
When MZ (small or medium) in left-bottom corner is set to "always", it's gets buggy. The stutter values slow down significantly and it gets weird. Also, out if curiosity, what is the stock QP value in IPB? Is there a .h264 thread? I have a feeling I'm asking questions in a wrong place.
Quote from: DTSET123 on January 30, 2013, 06:53:42 PM
There is a new bin? Where?
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
:)
Quoteleft-bottom corner is set to "always", it's gets buggy.
Its some sort of redraw issue related to MZ being on always. Its out of sync with the other ML overlays. I'm using a different method to sync it.. needs some investigation
*OK, I see that shutter updating gets slow so you turn the shutter key and it takes like 2-3s to update.
New Icons! Me like it :)
OMG! You fixed MZ full-screen!!! This is huge, thank you!!!
i fixed level for movie mode only too. I can't turn it off before the LV screen powers off. ML only handles lv on or not and I don't know how to shoot it that level off command before it closes.
this I think is what is breaking our powersave
I keep seeing that aEWB message and event 19. card lights up right away... thing is i reproduced it on 600D too but it only happens once every blue moon and usually goes out the second time.
[PM] DisablePowerSave (Counter = 4)
[PM] EnablePowerSave (Counter = 3)
[PM] DisablePowerSave (Counter = 4)
[PM] EnablePowerSave (Counter = 3)
[FENM] _ProcessFencingA
[FENM] _SetRDDMAC Out RD=0x1450c000
[PM] DisablePowerSave (Counter = 4)
[PM] EnablePowerSave (Counter = 3)
[AEWB] aewbProperty ID=0x80050000(0xc03f3b)
gmtProperty ID=0x80050000(0xc03f3b)
Event 19 Result State 6->6 ID 0x80050000(12599099)
[DETFEN] _StartRDDMAC(12)
DlgLiveView.c LOCAL_DIALOG_REFRESH_LV
srmEventDispatch: Current = 0, dwEventID = 29, dwParam = 62 S
srmRequestCalcAvailMovie
srmRequestCalcAvailMovie 1 24895768 0 11 1799
srmEventDispatch: Current = 0, dwEventID = 29, dwParam = 62 E
btw, not a fan of the little blue shortcut hints on the side but the 2 line help on the bottom is classy.
full log from hitting power save over and over:
dm-Powersave.log (519 KB)
https://mega.co.nz/#!ptI3zBaT!YMJdqFMKp4lIsQTVD6YiRmSvS-JyIf89CYy12Xc3zfA
If I already have ML on ym SD card, I can just add the new bin on the card or I have to re-install ML all over again?
yep, just keep updating the bin.
what's the benefit of full screen? i've not added it yet?
lol, its big
what is the full screen under, i'm not seeing it in latest .bin
I see a zoom
Where is the Donate button?
mZ size is in the mz submenu... wow, my s key is dying
any suggestion on getting the most out of ML?
I don't need an overkill of bit, and so on, but the highest bit possible with out causing an issue, or swallowing card space. I feel like I'm not getting the most of my camera, and I had a glitch today where the camera froze while shooting video, and I think it's happened because of the current settings I'm using.
I'm not sure if it's just somebody that's on some bad drugs or not, but on another forum I seen the guy say that 2k/4k should be possible on a 6d just as it should be possible on a 1dx. They say the firmware of the 1dx and 1dc is basically identical? Any thoughts on this?
Also, what are the possibilities of getting LOG on the 6d via magic lantern?
Quote from: gravitatemediagroup on February 01, 2013, 01:38:20 AM
I'm not sure if it's just somebody that's on some bad drugs or not, but on another forum I seen the guy say that 2k/4k should be possible on a 6d just as it should be possible on a 1dx. They say the firmware of the 1dx and 1dc is basically identical? Any thoughts on this?
It's a hardware limitation preventing devs from exploring the 2k/4k path... you just can't put that much data on a SD card fast enough.
There is also a risk of Canon raising the gun with lawsuits ...
Quote2k/4k should be possible on a 6d just as it should be possible on a 1dx.
Technically its feasible with jpeg compression but the low level stuff is not that easy. Right now just hoping to save jpegs from LV in HD buffer size and write out those. Efforts to do this on most cameras have failed.
See RE: MJPEG thread... right now 6D is in the 5d3 boat.
even a sandisk extreme pro 95mbs? lol
The camera doesn't normally make a 2k or 4k yuv buffer... in crop mode which we don't have (or at least not for a while) the zoom window is 2k sized so if you zoomed at 1x in crop mode maaaaybe.
so what if you could get the 6d to shoot 23fps raw? HAHAHAHA this is 50% a joke...
and then merge as a video in post
1%, WE HAVE FAITH AND KNOW YOU HAVE THE POWER ; )
I know canon has been throwing around the canon lawsuit talk about ML on the C series cameras
so does this mean ML will never touch a C100?
It seems like Canon "knows something" about the C series (c100 in particular) that they don't want to be exploited because
they will lose a lot of money on c300/c500 sales
The REC indicator: only time elapsed works. Is that fixable? It would be nice to know how much Gb or time left on card as we only have one SD slot and constantly under pressure as to when will it be full and stop recording. Its nice to know and have a peace of mind.
Also, just curious, does anyone know how many TV lines does it scan? Is it like mark 3 at 850?
Quote from: DTSET123 on February 01, 2013, 02:08:56 AM
Also, just curious, does anyone know how many TV lines does it scan? Is it like mark 3 at 850?
i'm sure a google search can find this out, or maybe canon website?
back to my question from earlier, what are best settings for highest bit without being an overkill to an SD card.
I seen somebody say in an earlier post about manually make changes to a .ini file, not sure I want to experiment with this method lol
Quoteback to my question from earlier
wow...
why not? thats the point of those ini files. My $22 card writes at 90mb/s Im sure u could push your Sandisk to higher
I think you're missing my question, and missed my post earlier
my camera froze earlier and I'm sure it was because I was pushing to hard, or had a setting wrong
so what is the proper setting for best results/highest bit.
1% said in a earlier post "past a ??? bit, there is no noticeable difference in quality"
and yeah, i'm using the 95mbs extreme pro and the camera still froze
Quote from: gravitatemediagroup on February 01, 2013, 02:42:44 AM
I think you're missing my question, and missed my post earlier
my camera froze earlier and I'm sure it was because I was pushing to hard, or had a setting wrong
so what is the proper setting for best results/highest bit.
1% said in a earlier post "past a ??? bit, there is no noticeable difference in quality"
and yeah, i'm using the 95mbs extreme pro and the camera still froze
Nobody knows, thats why it is development. It is for the people at the beginning to find out and share their results. I dont have your card speed, so my results wont work for you
there has to at least be a good "starting point"
should the bit be higher than qp, or the other way around? or the same?
Quote from: gravitatemediagroup on February 01, 2013, 02:56:54 AM
there has to at least be a good "starting point"
should the bit be higher than qp, or the other way around? or the same?
This should help
http://www.vcodex.com/files/H.264_overview.pdf
¨Setting QP to a high value means that more coefficients are set to zero,
resulting in high compression at the expense of poor decoded image quality. Setting
QP to a low value means that more non-zero coefficients remain after quantization,
resulting in better decoded image quality but lower compression.¨
Quote from: gravitatemediagroup on February 01, 2013, 02:27:08 AM
back to my question from earlier, what are best settings for highest bit without being an overkill to an SD card.
Run a benchmark in DEBUG-BENCHMARKS-CARD BENCHMARKS and post your results
full screen magic zoom is so nice :)
is it not possible to record that, so we get a cropped image with no pixel binning? like on panny gh series
it's a 700mb file? sound right?
Quotefull screen magic zoom is so nice
I know... :) Initially I hated 6d because of moire, but now Im in love with it! I have not touched my M3 since I installed "Tragic Lantern" Thanks 1% and everyone involved!
try out pickbox menu
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/autoexec.bin.pickbox
comment here:
http://www.magiclantern.fm/forum/index.php?topic=4386.msg25261
Quote from: 1% on February 01, 2013, 06:22:57 PM
try out pickbox menu
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/autoexec.bin.pickbox
comment here:
http://www.magiclantern.fm/forum/index.php?topic=4386.msg25261
Very sorry, but I couldnt work out what is different... what is a pickbox?
Magic zoom doesnt work for me on focus change with tamron 24-70 2.8
Hi,
i'm trying the new bin, and seems to have some "graphical glitches" in the interface. All is ok when normal navigating the menu, but when i open up a submenu (with q or with set or with other buttons) there are some strange graphical glitches, changing in time. Here is a screenshot of what i mean, can you see that lines? they are not still, but moving at a framerate something like 2 fps. All the other older versions of bin is ok here, so this glitches are related to pickbox version. And just for information, the lines are always inside the submenu box, and always of the same color of the bg of that box
hope it helps
what i wrote before is not completely true. Looking better, i have that rendering problem also when i'm not in a submenu, but when i'm simply over every voice of the main menu (the blu bg on the active line). But the glitches are very rare, only sometimes i see a little black line breaking the pure blu bg of the line selected. When i open the submenu the rendering issue is more evident, and seems that when i close the busmenu the problems stay more strong for a while and then calm down (but never disappear completely)
it's difficult to explain better the problem, don't know if is only on mine 6d or not...
QuoteMagic zoom doesnt work for me on focus change with tamron 24-70 2.8
Im using the same lens and it works! Did u install the latest bin>?
Quote from: DTSET123 on February 01, 2013, 09:35:41 PM
Im using the same lens and it works! Did u install the latest bin>?
I am being dumb, which trigger mode are you using?
[edit] deleted
At last found some time to install ML on my 6D, exciting moment ;)
Just followed the instructions in this thread and Succes!!
Thanks guys, will be testing this weekend.
menu is brand new being worked on, I think latest commits make it better
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/autoexec.bin.newmenu2
slightly less glitchy
Quoteme on focus change
Lens info and focus ring is broken, i have to look at the properties an fix all that. there is also a doubleclick we can use for either mz or shortcuts while recording.
glitches might be from enabling dma memcopy to draw menus or to new changes, i'm not sure
I confirm, with the newest version the glitches are less (not completely gone btw).
Another thing i've noticed (not related to the version i think) is that if i change the whitebalance from say "auto" to something else, there is'nt no more the voice "auto" in the ML menu. The only way to return in auto whitebalance is to do it in canon standard menu.
not shure if this happens in all the versions of ML or only with the 6d version, tomorrow i will try a comparison of features with 60d and 6d. btw thank you for your great development ;)
free space is fixed now.
Quotenot shure if this happens in all the versions of ML
Yea, all versions. they like kelvin. i shoot raw so it makes no difference
new info:
vbr qp is 1-26, camera may freeze if current mode cannot generate the minimum rate. i.e
I set minimum of 60 by default and right now, indoors, 1080P30 IPB will record, 1080P24 ipB will not, locks up.
If I raise the iso to h, both modes work. if I set minimum to 80, 30fps all-i modes freeze too but 60fps modes ipB or not keep working without issue.
additionally, while iso effect is not as pronounced as on digic IV, higher iso will still = higher rate possible.
another bug; new fps timer a only method never seems to set sound recording to off:
i put a message box
// take care of sound settings to prevent recording from stopping
NotifyBox(1000, "woowowow");
update_sound_recording();
an i never see it. I thought the property was broken but nope, just us
I've been experiencing a lot of "stopped recording" errors where I have to take the battery out.
I'm guessing it's my settings causing this?
also, it looks like HDR is gone in the newest .BIN ?
Quote from: gravitatemediagroup on February 02, 2013, 10:35:15 PM
I've been experiencing a lot of "stopped recording" errors where I have to take the battery out.
I'm guessing it's my settings causing this?
what settings are you using and what did your benchmark test say?
Bit 15
Qp 1
Autoload On
CBR Fixed
now sure how to view the benchmark
I ran it, but it just ends up some 700MB file
Quote from: gravitatemediagroup on February 02, 2013, 10:45:04 PM
Bit 15
Qp 1
Autoload On
CBR Fixed
now sure how to view the benchmark
I ran it, but it just ends up some 700MB file
No, you should be running DEBUG-BENCHMARKS-CARD R/W BENCHMARK (5 MINS)
Click it. It will show a photo on your card and 5 minutes later it will write a bmp to your card. post it here :)
QP 1 is going to give you a huge bitrate, what are your bitrates? open in quciktime and select SHOW MOVIE INSPECTOR and look for DATA RATE.
sandisk 30MB/ class 10
I want a bitrate between 80-120
Write Speed (buffer=128k) 12.1 MB/s
Read speed (buffer=128) 14.0 mbs
Write speed (buffer=16384k) 39.3 mbs
read test skipped: buffer=16777216
VBR config change min qps to 1, max to 26
edit min bitrate to like 80 (have the right # of 0s) and max to 120
max must match "bitrate'
it will record around 80-120 or freeze if it can't
Quote from: gravitatemediagroup on February 02, 2013, 11:38:17 PM
Write Speed (buffer=128k) 12.1 MB/s
Read speed (buffer=128) 14.0 mbs
Write speed (buffer=16384k) 39.3 mbs
read test skipped: buffer=16777216
Is this with the Sandisk pro card? This is your problem, 12MB/s = 12*8 mb/s so around 96mb/s, so a Qs of 1 will trip this. I am getting 200mb/s with Qs of 1
Quote from: 1% on February 02, 2013, 12:44:52 AM
menu is brand new being worked on, I think latest commits make it better
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/autoexec.bin.newmenu2
slightly less glitchy
I like the new UI
I fixed LV powersave, there is a constant event 0. but now I think it doesn't reset the counter first time and powers off lcd instead of dimming first. subsequent powersaves are ok :o
Quote from: sparedog on February 03, 2013, 12:23:49 AM
Is this with the Sandisk pro card? This is your problem, 12MB/s = 12*8 mb/s so around 96mb/s, so a Qs of 1 will trip this. I am getting 200mb/s with Qs of 1
extreme pro 95mbs card
so if you are getting 200mbs
what is my bit supposed to be at if my Q is at 1?
Try it, nobody can predict it as it changes per scene. Burst rates can go higher for a tiny bit too. Haven't been able to throw these in bitrate viewer to see what it does per frame.
Quote from: gravitatemediagroup on February 03, 2013, 07:59:53 PM
extreme pro 95mbs card
so if you are getting 200mbs
what is my bit supposed to be at if my Q is at 1?
please try this for me
set bitrate: 0
initQp: 1
record a clip of 10 seconds of something outside, a wide shot with lots of detail but no movement of camera
post file on putlocker or somewhere where I can download and analyse it
should be pretty interesting!
being that it's 20 degrees outside with snow on the ground, might be a few days on this one
I just did another little test in the house with it at 0 and 1
and it's unusually NOISY even at lower ISO
Quote from: gravitatemediagroup on February 03, 2013, 10:53:22 PM
being that it's 20 degrees outside with snow on the ground, might be a few days on this one
I just did another little test in the house with it at 0 and 1
and it's unusually NOISY even at lower ISO
haha sorry about that. That´s the thing with the internet, I live in Spain =D
would you like to upload the house test? is it ipb or allI?
all I
i'm not all that worried about it, doing test is pointless IMO until alpha is released.
but the more I use the 6d as my "canon video camera" the more it makes me want to stop playing games and get the c100 w/atomos ninja2
Quote from: Chair on January 16, 2013, 05:11:43 PM
... is it too much to hope that I'll be able to monitor audio through my AV ouput... ?
Hi developers, I am following the action from the sidelines, but in the meantime I have been working in the field with my 6D. I just want to reiterate my sincere hope/request that you guys will be able to enable audio out for monitoring through the A/V port while recording video. Thanks and keep up the great work!
I've been experimenting on audio so far all I can do is send commands. i got the screen to go off for headphone but the ic has to be configured to send audio there.
not sure how anybody is having success with high bit rate video, but I can't shoot anything for longer than 3 seconds without the camera crashing, and I've tried MULTIPLE variations.
VBR has no issues as far as I can tell.
I honestly had better looking video without ML, now I end up with a lot of noise and vertical lines.
noise isn't affected by bitrate but by iso. Only time I had lines was when fps override was too high/low on older versions.
I think you are expecting too much out of 6d. Achieving high bit rates does not necessarily mean that you will see visual improvement in quality like gh2 did. After all, we are still in 8 bit world and h.264 has limitations. 6D has severe moire issues and software won't fix that. If you can't live with this quality then maybe c100 is justifiable for you (if you can afford it).
Speaking of quality, 1% do you know if anybody is working on mjpeg or is that dead in the water?
dead for now. need to figure out the jpeg saving functions just like 600D/5d3/etc
lots of other things to fix too
Quote from: DTSET123 on February 05, 2013, 05:02:02 AM
I think you are expecting too much out of 6d. Achieving high bit rates does not necessarily mean that you will see visual improvement in quality like gh2 did. After all, we are still in 8 bit world and h.264 has limitations. 6D has severe moire issues and software won't fix that. If you can't live with this quality then maybe c100 is justifiable for you (if you can afford it).
I don't want 400mbs, I just want something realistic that doesn't crash, and the fact that it's crashing at the lowest possible setting is a little messed up, although I'm going to see if what 1% said solves the issue.
8bit is not an excuse I will ever use.
the 6d in theory should be able to produce a better video than the 5d MKII, and there has been some AMAZING stuff come from a MKII.
moire isn't an issue that I have had an issue with so far, and if i did, the mosaic engineering filter is AVAILABLE.
my extreme noise is happening at lowest iso 200
Quotemy extreme noise is happening at lowest iso 200
That's strange. I use stock all-i for now until better days but it is very clean at 200
some examples would be nice tho. I haven't had an issues like this.
Quoteuntil better day
not much better is going to happen on this front, except maybe a better interface. After 5d3 this is the furthest port along. the only thing left on H264 is directly setting frame settings (there's one more test function) and the adaptive 4x4 matrices which produce unplayable video now.
I´m getting clean results right up to 150mbs. at 200mbs the camera freaks out. Im going buy a faster card and test
maybe he left focus peaking on.
with new build: autoexec.bin.refactoring
HIGHLIGHT TONE PRIORITY when selected in menu, menu flashes
in SOUND RECORDER, PLAYBACK SELECTED FILE crashed the camera
I cant get CROPMARKS to show up
will look. everything that was old is new again with the menu api change. advanced HDR bracketing -- changing the iSO will also hang it.
maybe its something in the config... Its working for me from the ISO menu. Both photo and movie. However now picture styles edited from ML menu don't survive a reboot.
Quote from: 1% on February 06, 2013, 01:38:10 AM
maybe he left focus peaking on.
A question about freeing up the processor. it is possible to turn off recording sound and use the little bit of extra processing for video? or do they get processed in different parts of the chip so it wouldnt achieve anything?
You can try but it recorded sound even at 100mbps unlike the older cameras. It should save a tiny bit only.
So these are my results, with a class 30 MB/s
I can record up to 150mb/s no problem
150-175mb/s is tricky, I have to watch the buffer and keep it out of the red
200mb/s it records and stops after a few seconds
the buffer seems to go red at 51%, is this due to it not updating the number on screen fast enough?
Shit, its editing the picture style bellow it. so I edit neutral and faithful gets the edits.
Yea, buffer/overlays doesn't update fast enough. by the time you see it, its already stopped. On 600D I sped it up, here its still up in the air on whether its worth it.
Quote from: 1% on February 06, 2013, 01:57:49 AM
Yea, buffer/overlays doesn't update fast enough. by the time you see it, its already stopped. On 600D I sped it up, here its still up in the air on whether its worth it.
no its cool. it is still enough of a guide to ride it and keep the dial out of the red. certainly for testing purposes, so i can see what the cut off point is for my setup.
i´m going to buy a 90MB/s and see what it gives me. anyone else tried one? please post.
I had similar results with my Patriot LX card but every time i pointed camera to complicated scenes, it would burst to crazy bit rates and stop recording. I have tried many configurations but could not get it stable so I have decided to stick with stock. Besides, for those few seconds that I was able to record, I did not see significant improvement in quality but I did not try color grading.
I think that Tragic Lantern is ready for Alpha, maybe if more people play with settings they will prove me wrong.
i haven't had too many stops on rate control even with sound mostly on vbr and cbr. the IPB@ ~60-70mbps isn't too bad but haven't tried to grade any yet. pretty much up to stock all-I. if you can get steady 200 on a 90MB card you could just record qp1 all the time. technically 200 is only 25MB/s but i'm betting the lower tier cards can't keep that up for the gigs and gigs that gets recorded. I think the ML test is only on 1gb and that's not even a full minute.
would be interesting to see the 'pro' cards graph of sustained write over time. like after 15gb where's it at.
Quotemaybe if more people play with settings they will prove me wrong.
I think the menu change set us back a tiny bit. but "alpha" is ongoing.
Quoteit would burst to crazy bit rates and stop recording
sounds like fixed qp recording. rate control kept it real even on a cheap 32gb card.
Quotesounds like fixed qp recording. rate control kept it real even on a cheap 32gb card
When I tried RC at first, without any overrides, it still crashed. I will do some more testing later.
Question, when arrow shortcuts are on, for automatic white balance it says push but how? The SET button does not do it. How do you use that feature?
is it ML or canon who puts the four white blocks on the screen when the buffer is full and recording stops?
I think thats canon.
Quote from: DTSET123 on February 06, 2013, 02:22:20 AM
When I tried RC at first, without any overrides, it still crashed. I will do some more testing later.
Question, when arrow shortcuts are on, for automatic white balance it says push but how? The SET button does not do it. How do you use that feature?
push focus points (far right button) and then set. but you cant have af in quick mode
Canon puts the white blocks. Shortcuts are on the focus pattern key. have to make them switch while recording, all buttons go dead. will need to rewrite the 5d3 double click feature for that.
If you overrode initqp or bit rate while on rate control then it will crash. Just autoload on an rate control config. make sure its in the ML folder.
Need to make the patterns work again, one point or all points is pretty worthless.
QuoteIf you overrode initqp or bit rate while on rate control then it will crash. Just autoload on an rate control config. make sure its in the ML folder.
That's what I meant. No override and auto load on still crashed and ini is in ML folder. I am going to modify the ini and lower Min and Max bitrate and see what happens.
I have the short cuts on the display and everything works except pushWB. Is that because I have ISO assigned to it in canon?
probably will have to test
Dont bother, yes it was because of that. THX anyway!
FPS table is at 0x82e14 with timer B on you get 77FPS in 60 and 40 in 30P... too bad b isn't changing and makes purple screens.
Prop LV lens is still there but the offsets are wrong. on my 35-135 I get 135mm at 35mm and 106mm at 135mm, this tells me the count isn't right. maybe something a uint8 instead of 16.
why is it so hard to post a photo on here, I'm gonna show you guys something that will BLOW your mind
take a look at this image of what my 6d footage looks like
http://www.sendspace.com/file/0kmtu0
such a joke, and I can't believe nobody else is having this issue
the BMCC can't get here fast enough
Is that ISO200?
I think 400, but that should NOT even matter. I have take pictures with this camera in PITCH BLACK, LITERALLY PITCH BLACK and had nowhere NEAR this kind of noise or lines
before I put ML on the 6D I never had such an issue.
I shot a really dark scene of my brother driving at night and there was no noise and it was at a pretty extreme ISO
I've done testing with all-i, ipb, no bit or q increase, VBR, CBR, low iso, medium iso, and I'm getting the same results.
ML is causing a major issue, or I have a setting that isn't right. I wish people would post some low light test videos or screen shots of.
are using peaking? if so turn it off. What if u dont use ML and reset camera settings, you still get that?
I tried with peaking off and it was the same
do I have to completely remove ML or can I use a different SD card that doesn't have ML on it.
because I tried a SD without ML and it was the same.
weird, there is something wrong with your cam
can you upload short clip at ISO 400 so we can take a look
This looks like a hardware defect. those are vertical lines. do they show up in pics? at least you found out now, not next year
no, only in video
I bought the camera from BH, but if it is a hardware issue, do you think canon would issue a full refund?
but the thing is, I didn't have these lines before ML, so i'm still not gonna blame canon just yet.
this is BEFORE ML
http://www.sendspace.com/file/x7743u
Quote
I bought the camera from BH, but if it is a hardware issue, do you think canon would issue a full refund?
dont expect him to answer that question, you know the rules. If this is a hardware problem it would happen regardless, it just happens that you had ML when it happened. ML does not write anything to cam's ram so if you take out ML and it is still messed up, well at least you have options.
mine doesn't have the lines. I've used ml too and done worse things. use a non bootable card and reset all settings but this is probably a has to go back to seller or manufacturer kind of thing. it does it with no ML. if you're going to get the bmcc just try and get your money back. you used the shit out of the camera testing it, if you hadn't it might have failed out of warranty
Quote from: gravitatemediagroup on January 26, 2013, 03:34:49 AM
nope, camera is dead
but it did, it took about 10 seconds to transfer files to SD, and then it created a new autoexec
maybe it was when this happened?
Quote from: gravitatemediagroup on February 06, 2013, 05:45:33 AM
the BMCC can't get here fast enough
can you use canon lenses on the BMCC, I dont know much about it.
Yea, its ef mount.
*made the bit rate more user proof and informative with new api
*pic style editing fixed, the const was never checked
*double click dead button to toggle zoom or shortcuts (pick in lv zoom settings0
*Kill canon dialogs
Quote from: sparedog on February 06, 2013, 12:49:03 PM
maybe it was when this happened?
possibly, but then that would be a result of ML causing the issue.
if you see the picture I posted of a clip shot before installing ML. that was at a extremely high ISO.
i'm gonna try a different card, and take ML off the camera and see what happens
why do my pictures not display the same lines that the video is?why has nobody posted any test footage yet?
Quote from: sparedog on February 06, 2013, 01:02:20 PM
can you use canon lenses on the BMCC, I dont know much about it.
yes, if you have't seen the video "meet me in big sur" shot with the BMCC I HIGHLY suggest it.
I really hope that the bmcc forces canon to be a little more realistic with their prices from here on out.
I found one that I'm going to buy but it's going to cost me $4100, that's $1100 over retail, but it's brand new. I
That is weird.. but they are 2 different ways of sampling the sensor
1. really fast, change cmos clock, skip every x lines chroma/luma
2. take a pic, read every line slowly
that's all I can think of.
I posted test footage a ways back, do you want black or something. My footage now looks like your "pre ml' footage
RC_IPB_STOCK_MVI_7291.MOV (145.8 MB)
https://mega.co.nz/#!A4wFjL5Q!fcfZ2lGdUlQiU_swlipc6XZgKOMjNiYkYhISMP0zHDY
vs rate control on the "same" realistic scene
MVI_7293.MOV (321.3 MB)
https://mega.co.nz/#!hhgXxLbA!MB-_egDLa_AVjSTyV7nFxnF1aPd1rZqpRJ9ej2Dnydg
I also think that one of the first version of the ML beta was fine other than crashing, but somewhere in the past 8 to 10 updates is when the issue started to happen.
i dunno, I guess you could get your money back or try to run the camera into the ground. like record hours of timelpase at QP1 with fps override to where it no longer stops. let it get hot and see if defects get worse, they probably will.
Kill-Flicker update is solid. Short keys are working fine except when its gone there is no way to bring it back when recording. Magic Zoom on focus ring still not working.
Can I make a feature suggestion here?
only doubleclick works while recording.
zoom ring is from prop lv lens.. it has to be decoded. focal length and all that is wrong too
Sooooooo.....
Hey gang! Noob here.
I've installed ML with success. :) (Great Work!)
I understand this is a developmental thread, but amidst the onslaught of acronyms, I'm really lost on how to achieve the highest quality
in the bit rate category here... I know VBR is a variable BR that's self adjusting within a set of parameters based on the complexity of the scene(?)
CBR is kind of a sustained BR I assume? ... From what I have read, it "caps" at the selected level?
RC is where I'm confused. I don't understand what this is doing, or whether it is better.
My train of thought is: Fixed CBR around 20-30. QP: 1. I've done these settings within ML on the camera, but somewhere in here I read someone adjust from the .ini file on the card?... So- High Constant Bit Rate, with a Low QP...? Least I thought that was the ideal approach for maximum badass.
and what is h.264.ini doing? I thought that was the native format anyway regardless..?
I'm using a Sandisk Extreme Pro 64gb / 95mbps SD card.
It would be really cool if someone could help me out here. I thought I was maximizing this thing... Now I'm not so sure.
Once again, great work!
qp1 is best if it works. The conig also sets profile level and cavlc or cabac encoding, transform flags too when they are figured out
rc and vbr exist because most of us can't qp1 all the time.
Quoteonly doubleclick works while recording.
no go for me... what am i doing wrong?
where has the tinypic (or what ever its called) button gone to post images into posts?
So today I bought a 90MB/s sandisk extreme pro 8MB card. But I may have some bad news about bit rates
I need to be able to post some pics :(
* found it by using tinypic.com
ok this is with the 90MB/s card
Not very different to the 30MB/s card - the 128k read speed has actually decreased in the 90MB/s card... wierd
So the 90MB/s card can only write at 39.3MB/s? Is this because of the camera limitations?
Basically the card has given me no difference what so ever with amount of bitrate I can stabily record at - Which stands at about 150-160mb/s. Any thing over 170mb/s stops the recording. Sure you can start the camera, but after 3 or so seconds, that recording stops.
QuoteRC is where I'm confused
I am in the same baot as you are but I think RC is like VBR, but with the -1qp which attempts to record at lower qp.
qp 1 is the best quality but it requires very high bit rates, so we are all curious if it will work on your card.
try this and let us know:
bir rate: 0
Initqp: 1
Autoload config: override
Configselect: Rate Control
Config loaded: yes
See if it will crash and what rates is it showing. If this will crash, try raising iniqp until it will stop crashing. Oh, and make sure you are using IPB compression.
you should really load cbr config for that, doesn't make a big diference tho, end result is fixed qp recording.
vbr and rc only change the qp dynamically if you don't override the parameters.
QuoteIs this because of the camera limitations?
could be... that card could also be 90mb burst, not sustained. ep pro boasts 50MB/write but does like 46 in reviews. you're getting 40 which sounds about right.
another thought... is the write light solid at the top speed you're getting. our flush rate is set dynamically and i think g3ggo's address put me in the middle of some unrelated functions. If we increase that maybe top rate will go up.
digic IV stops at similar speeds.. actually 600D seems to get higher rates than 6D just not as high of a profile.
also try recording black or easy stuff for the first second and then pan to the scene causing the stop. you can physically control it this way an pan away right before the stop, etc. not really helpful for shooting but for testing its win.
I can't figure out the shortcuts, once they disappears (during recording); I can't get them to show up again. Just to verify, you said to double click, but it is not responding and they don't come back up. Is it just me or thats how it is?
Quote from: 1% on February 07, 2013, 03:27:53 AM
another thought... is the write light solid at the top speed you're getting. our flush rate is set dynamically and i think g3ggo's address put me in the middle of some unrelated functions. If we increase that maybe top rate will go up.
also try recording black or easy stuff for the first second and then pan to the scene causing the stop. you can physically control it this way an pan away right before the stop, etc. not really helpful for shooting but for testing its win.
No the light is still blinking when the recording stops
Here´s my test. I start on a white wall and slowly tilt down to a very busy patterned floor. When the floor fills the screen, it easily pushes the record bitrate to 200mb/s, so as I slowly fill the screen by tilting, i can watch the bitrate go up and note when the recording is stopped.
With Q set 1 and bitrate set to 0, the recording normally stops at about 165, 170 if I am lucky and can ride the bitrate by the wall/floor ratio :)
If i lower the Q to about 15, I can control the top bitrate to not stop the recording, but the average bitrate drops. How would I set the bottom bitrate to not drop below a certain figure?
you have to enable it in the menu where you disable 5x/10x zoom and do zoom with focus ring, etc.
its a little hard to get the timing right for the clicking but light/af patterns and probably other buttons will do it.
you can try VBR to do that but its a little freezy and you can't override it in camera. it will pick 1-26 and go over the minimum rate. so if you set min to say 80 it will hover around 80 and slightly above.
Quote from: 1% on February 07, 2013, 06:46:50 PM
you can try VBR to do that but its a little freezy and you can't override it in camera. it will pick 1-26 and go over the minimum rate. so if you set min to say 80 it will hover around 80 and slightly above.
what I hadn´t considered is:
if the stock canon bitrate drops to the same amount as when Q is set to 15, ie they both drop to the same on similar scenes, but the enhanced ML version can record up to 150mbs when it needs to, then it might be an almost perfect solution
kinda why i like rate control. bit rate stays 60-80 average and jumps to whatever when necesary. i've seen it write 135 instants.. qp stays between 1 and 13... and tends to favor the lower numbers. really need to find out why none of the videos work in bitrate viewer... stock or not. it would be nice to have the graphs.
Quote from: 1% on February 07, 2013, 07:03:52 PM
kinda why i like rate control. bit rate stays 60-80 average and jumps to whatever when necesary. i've seen it write 135 instants.. qp stays between 1 and 13... and tends to favor the lower numbers. really need to find out why none of the videos work in bitrate viewer... stock or not. it would be nice to have the graphs.
I don´t want to waste your time, but are those setting written anywhere - explicitly and easy to follow? I would like to test it against what I am trying
configs are plaintext and fairly easy to figure out.
also in the reverse engineering forum are all the settings
http://www.magiclantern.fm/forum/index.php?topic=4124.0
Hi there! I'm interesting about wifi: could it be work in video mode in future ML?
So, I modified the RC.ini and got some great results averaging 60-70mb/s (IPB) stable. TheSe were my settings: http://i48.tinypic.com/f9i9hf.png
Everything was looking good until I tried to use FPS Override @ 5 and this is what happened: http://www.youtube.com/watch?v=kFnQBHubu0s&feature=youtu.be
Notice that it was doing ok until I started to push the slider. It is fine with stock rates.
QuoteI'm interesting about wifi: could it be work in video mode in
It needs more investigation but probably not. its either communicating with the wifi chip on the same channels as encoder or can't make the preview frames and video at the same time.
QuoteNotice that it was doing ok until I started to push the slider. It is fine with stock rates.
I'm guessing rate control mechanism is non plussed with the lag created by fps override. Needs more testing to see exactly which modes get affected by timing changes. I've always done them at fixed quality. its like it set qp to 50 for the bottom half... maybe transform related or the quality switching is off from actual frame writing. IPB mode frames are referenced to each other
may have to figure out how to manipulate eko mode for rate control under FPS override... that is what canon uses by default
any way to repeat it?
heh, vbr more freezy too with low FPS override. seems anything dependent on timing will not be happy.. just like sound recording. fps of like 10 was fine but the lower you go the more interesting it gets. I'd be wary of canon stock too and the QPs it sets under fps override will have to be checked out. also all-I might be better here too because of motion blur, or lack thereof.
Quote from: 1% on February 07, 2013, 10:11:25 PM
It needs more investigation but probably not. its either communicating with the wifi chip on the same channels as encoder or can't make the preview frames and video at the same time.
(((
So, it will not work even when camera display automaticly off (like hdmi or AV out)? It's uncool. Uncool. Uncool. Uncool.
I blocked the dialog and tried to record a movie. It cleared the screen like it was going to record but nothing happned. When I pressed rec again it stops. Like encoder is disconnected or that path is turned off.
Anyways, my wifi LV is freezing after like 30s. On the phone, on the camera or both at the same time. I think 6D still has bugs. ML doesn't alter that area and PTP is not compiled in, same thing without it too. I guess QC isn't worked out for 6D yet.
I was unable to reproduce the glitch but I think the complexity of the scene has to do something with it. I tried just now at home and it worked fine. When I did it earlier today the scene was much more complex. I did make several of those clips earlier with the same bad result. Right now I tried VRB, RC and H.264 and they all worked. Also, I noticed that at lower frame rates like 4 and 5, I get vertical lines but not at 7 and higher.
QuoteWhen I did it earlier today the scene was much more complex
You can't fuck with the grass. Same kind of grass like that made 200MB/s on 600D.
I get the lines too when using low FPS override and dynamic quality. FPS override for us is missing register B and timer A is very unstable. With timer B we'd probably get 77FPS in 60P and 40 in 24P/30P and of course the really slow ones that make cool time-lapse. This is needed for all digic V tho.
*canon stock too. underexposed + fps under 7 and you get the lines. this is probably more related to fps override... also aggressive and fps time A only don't get set from internals.h anymore, I had to manually put it in the config.
Quote from: 1% on February 07, 2013, 10:46:22 PM
I blocked the dialog and tried to record a movie. It cleared the screen like it was going to record but nothing happned. When I pressed rec again it stops. Like encoder is disconnected or that path is turned off.
Anyways, my wifi LV is freezing after like 30s. On the phone, on the camera or both at the same time. I think 6D still has bugs. ML doesn't alter that area and PTP is not compiled in, same thing without it too. I guess QC isn't worked out for 6D yet.
As i see, it's freezing when phone go to lock mode (when you not touch it). If change some camera settings from phone - all is ok.
But it would be so cool - would not need HDMI monitors and cables, and you can control the focus of steadicam (better than nothing), online broadcast ... I will not survive if the ML dont make it ((
wifi could be dropping but the camera locks up to a battery pull...
overriing 720P much worse than 30p or 24p, I get lines at like 5-10fps, even more. video comes out green. windows says its 1280x1792. need to test override and find out what is good. so far 7 for 24/30p i got up to like 24 in 60p
I think I fixed my noise/lines issues.
lowest ISO possible seems to be the issue. 600 or above looks better
Quote from: gravitatemediagroup on February 08, 2013, 01:12:28 AM
I think I fixed my noise/lines issues.
lowest ISO possible seems to be the issue. 600 or above looks better
unfortunately that doesnt sound ¨fixed¨. ISO 100 is perfect on my camera, and the noise only comes in at 6400
The issue is from sensor timing. fps override at fault here, does it in all modes. I did more testing and you can tune it down to lines/no lines when it oscillates. Unfortunately leaves us at 7fps for 24p and 15fps for 60p :( if you set it lower, stock or not, you'll get defects.
Here are some examples, green is 60P
http://imgur.com/a/k23Qg
actually, green happens when transform + scaling flag is changed for 60P but line behavior is the same.
is it possible to add kelvin values somewhere in the corner when using shortcuts? Since canon took out WB it is a pain to dive in to menu just to check you wb temperature
Quote from: 1% on February 08, 2013, 01:40:01 AM
The issue is from sensor timing. fps override at fault here, does it in all modes. I did more testing and you can tune it down to lines/no lines when it oscillates. Unfortunately leaves us at 7fps for 24p and 15fps for 60p :( if you set it lower, stock or not, you'll get defects.
Here are some examples, green is 60P
http://imgur.com/a/k23Qg
actually, green happens when transform + scaling flag is changed for 60P but line behavior is the same.
All I care about is 24p, so what can I do to always avoid the lines?
Im a little confused, I never use the override (unless ML kicks it in automatically)
Does anyone know how many lines the 6d resolves at in video mode?
FPS override never kicks in automatically.
QuoteAll I care about is 24p, so what can I do to always avoid the lines?
For me its as simple as not using fps override that low.
if its happening all the time like you said:
do a dimly lit scene, turn on peaking in sharpness mode. you should see the lines when there is a timing problem. adjust fps override till you don't see them anymore. then you'll get an idea about how much its off. I don't notice them on fully exposed scenes even at fps 1.5... but then I there is a chance of video defects like dtset got.
Have to get to the bottom of this eventually, kinda looks like vertical lines being skipped in all honesty. Our res is 1808x1206... 6d has more than usual moire for many... I somehow feel this is all related.
QuoteDoes anyone know how many lines the 6d resolves at in video mode?
and when you get the lines, does it resolve less.
More I read this thread, more I get confused. I would like to shoot/test around 80mpbs. I have the scandisk extreme 95MB/s 10 card. Here the config I made:
On Camera:
BitRate: 8
InitQP: 10
Autoload Config: Override
Config Loaded: Yes
ConfigSelect: Rate Control
FPS overide: 24.000
FPS ramping: off
RC.ini notepad:
Transform8x8Flag = 2
Profile = 100
Level = 51
BitRate = 80000000
EntropyCodingMode = 1
IntraPicInitQP = -1
InterPicInitQP = -1
QpOffsetForB = 0
MinQpI = 1
MinQpP = 1
MinQpB = 1
MaxQpI = 16
MaxQpP = 16
MaxQpB = 16MinBitrate = 60000000
MaxBitrate = 80000000
SarWidth = 0
SarHeight = 0
AspectRatioIdc = 1
VideoFmtAndVspFlag = 81
VideoFullRangeFlag = 1
TimingInfoPresentFlag = 0
RateControlEnable = 2
ScalingMatrices = 0
pScalingMatrixAddr[0] = 0
pScalingMatrixAddr[1] = 0
pScalingMatrixAddr[2] = 0
pScalingMatrixAddr[3] = 0
pScalingMatrixAddr[4] = 0
pScalingMatrixAddr[5] = 0
Good? Not good?
follow focus and shortcuts seem to conflict with each other?
it works, you can toggle between them but its a doubleclick while recording, feature is in zoom prefs
QuoteBitRate: 8
InitQP: 10
Autoload Config: Override
Making fixed qp cbr with a target of 80 which may or not be ignored depending on what qp10 makes.
Just set the config and don't override it if using a rate control mechanism. what you want, VBR will give you but that mode is a bit unstable, freezes if camera can't provide requested rate. don't think you get the buffer squares either, just stops like nothing happened. there should be VBR 20, 30, 60, 80 but those would all have to be separate configs :(
I thought of a possible solution to the level problem. Make it only appear for like 10 seconds or until level is achieved. After that it dissapears until the camera isn't level again.
*Powersave + expo lock fixed. Maybe ML auto ISO too? bulb ramping calibration seems fixed from this too.
#define ISO_ADJUSTMENT_ACTIVE 0 this function isn't used anymore.
Quote from: DTSET123 on February 07, 2013, 02:45:36 AM
I am in the same baot as you are but I think RC is like VBR, but with the -1qp which attempts to record at lower qp.
qp 1 is the best quality but it requires very high bit rates, so we are all curious if it will work on your card.
try this and let us know:
bir rate: 0
Initqp: 1
Autoload config: override
Configselect: Rate Control
Config loaded: yes
See if it will crash and what rates is it showing. If this will crash, try raising iniqp until it will stop crashing. Oh, and make sure you are using IPB compression.
I tried this on my card, and it was successful... - provided you didn't point it at a death chart, lol.
A 30 second clip with those settings in IPB was 541.56 mb. Quicktime Inspector showed an average bit rate at 143.28 mbits.
I have a screen over my window, and the blinds are made of small-intertwined rope and wooden slats.. the kind that roll up.. (not sure what the technical term for them is).. Very, very fine detail that when focused in on, made the camera go apeshit and stop recording immediately.
I actually tried those settings with All-i. The second I hit record, it shot a bolt of lightning across the room, farted, and rebooted. So I assume that's why you said "IPB".. ;D
So "QP" as I understand it is like a compression ratio? level 1 must be borderline raw, lol.
I would explode in a harmonious display of rainbows and kittens if ML would one day offer clean HDMI at full res..
I just tried the above settings and ended up with a twitchy clip, almost like it would skip 3 or 4 frames during playback every couple seconds.
out of about 4 test shots, the shots with the most detail obviously were affected the most. this was with an extreme pro card.
it never crashed, which is a step in the right direction.
go shoot a clip of a bush or a tree and you will probably be able to emulate the twitching
2 clips were 130 mb/s
1 clip was in the 140's
the twitch clip was 158
I'm gonna up the Q to 5 or higher. some of the best clips I got with ML was when the bit was between 80-100, any higher and it appears to fall apart and go back to stock FW quality. lol
UPDATE:
QP 5 = crash issues
I'm gonna stay between 1-3 for now I guess. Still not happy with the overall look of the video quality. just looks like mud, stock or ML.
As a stills camera, I like it a lot.
Y'all doin it wrong.
Fixed qp is fixed qp.
Quotesome of the best clips I got with ML was when the bit was between 80-100, any higher and it appears to fall apart and go back to stock FW quality.
Nothing is going back to stock anything, DIGIC IV ml changed values which influenced the picked 'qp'. Here we are setting qp directly.
Quoteyou will probably be able to emulate the twitching
2 reasons to have twitching.
*Playback from card, your player can't read enough data fast enough and glitches out or frame skips
*Camera is overloaded at current quality and starts losing frames... the TI soc has frame skip, CBR fixed mode has NO rate control.
when in doubt open up in virtualdub and go frame by frame, post examples of defects
twitching in media player classic happens a lot playing directly from the card, opening the clips in VLC or copying them = no twitching.
QuoteQP 5 = crash issues
1 and 3 better than 5, scene too complex for 1,3,5 try like 10 or 15 the lower qps just stop it sooner.
this is why you don't do fixed qp.
compare h264 to .422 frame, its what is input to the encoding sOC
gravitatemediagroup - Im confused. Did you fix your camera, get a replacement, or decide that the noise and strange lines are liveable with?
my twitching clips happened in VLC, I never watch footage in media player
Quote from: sparedog on February 11, 2013, 01:21:10 AM
gravitatemediagroup - Im confused. Did you fix your camera, get a replacement, or decide that the noise and strange lines are liveable with?
they aren't as noticeable at higher ISO and it creates more noise I guess that just blends into the lines, bought a BMCC for above retail from somebody that had an extra for sale, and the 6d is now a good stills camera.
i'm gonna follow the progression of ML for it, for now, it's just a good stills cam ; )
when I considered the c100, I pretty much remembered that it's extremely overpriced and can get a BMCC right now for $3000 less
how does it play in the NLE? what's a twitchy frame look like?
gravity, does 6D a good b-roll camera with BMCC in terms of "matching colors"?
Quote from: ManixLiquid on February 11, 2013, 02:25:46 AM
gravity, does 6D a good b-roll camera with BMCC in terms of "matching colors"?
wouldn't ever even attempt to B roll the 6D with it. gh2...probably
Quote from: 1% on February 11, 2013, 02:25:27 AM
how does it play in the NLE? what's a twitchy frame look like?
didn't even waste time pulling it into a a NLE
it would skip about 3 or 4 frames every couple of seconds, like it was jumping forwards like frames were dropped, and was pissed about it so I deleted the clip and jumped up to QP 3 and it hasn't done it since.
Yesterday worked 6D for 10 hours - no issues at all!
Quote from: DTSET123 on February 11, 2013, 02:56:27 AM
Yesterday worked 6D for 10 hours - no issues at all!
without sharing settings, you're not helping anyone out much ; )
Quotewithout sharing settings
You have to read up on how encoding works and why you're setting the things your setting.
This is pretty much configuring x264 with a 422 YuV input. the frames have to go from 4.4MB to <1MB. The uncompressed silent pics don't differ so much from H264 frames (not counting 422 -> 420). I can't fix the resizing+moire unless we change the yuv buffer created. I get moire and same "poor" quality shooting 4.22s.
600D vs 6D, better resolution vs way better ISO.
Quotewithout sharing settings, you're not helping anyone out much ; )
Oh, sorry... I did not fuck with ini files because I was shooting a wedding and was too afraid it would stop in the middle of something important. I used stock rates but will continue experimenting and let you know as soon as I get something stable. Other then that ML was excellent, and full-screen zoom is just a life savior when you run and gun!
Quote from: gravitatemediagroup on February 11, 2013, 02:20:05 AM
bought a BMCC for above retail
Whats above retail mean? Translates to more expensive than the retail price... but I dont think you mean that =D
Yay, Mosaic Engineering has now released it´s anti-aliasing / anti moire filter for the Canon 6D, the VAF-6D.
I´m going to get one in a couple of weeks and test it out
I managed q = 1 and bitrate = 12 on all-i 24p, but when I switched to 720p all-i it lasted maybe 3 seconds before quitting out.
Any idea why? Also, the variable framerate function is really awesome, switching between 60 and 24 on the fly, very chill.
When I set frame rate to below 5, it still looks okay, or it gives the ol battery freeze. However, the jello-cam is godawful. Not sure what's going on there, not a huge deal, I have the 600diz for that.
QuoteI´m going to get one in a couple of weeks and test it out
It looks promising but Im afraid it will ruin the photos as 6d is an amazing stills camera. Can't wait to see some real world tests and hear your overall opinion. I'm reviewing the wedding footage that I shot and so far, Im really liking it! The ceremony was incredibly dark but 6d had no problem there- footage looks beautiful! Also, I did not run into moire problems on this particular shoot so I'm very happy :)
Quote from: sparedog on February 11, 2013, 03:46:54 PM
Yay, Mosaic Engineering has now released it´s anti-aliasing / anti moire filter for the Canon 6D, the VAF-6D.
I´m going to get one in a couple of weeks and test it out
it's been out a week or two, the price is a bit too much for me.
is their any 6d clips showing that it works?
Quote from: sparedog on February 11, 2013, 03:43:41 PM
Whats above retail mean? Translates to more expensive than the retail price... but I dont think you mean that =D
yeah, being that they aren't just shipping left and right I went ahead and bought one for a little more from somebody. worth
every single penny over retail that it cost. the image from it is NO joke.
Quote from: DTSET123 on February 11, 2013, 10:47:17 PM
It looks promising but Im afraid it will ruin the photos as 6d is an amazing stills camera. Can't wait to see some real world tests and hear your overall opinion. I'm reviewing the wedding footage that I shot and so far, Im really liking it! The ceremony was incredibly dark but 6d had no problem there- footage looks beautiful! Also, I did not run into moire problems on this particular shoot so I'm very happy :)
can you post a frame from it?
Quote from: fotojohni on February 11, 2013, 10:27:18 PM
I managed q = 1 and bitrate = 12 on all-i 24p, but when I switched to 720p all-i it lasted maybe 3 seconds before quitting out.
Any idea why? Also, the variable framerate function is really awesome, switching between 60 and 24 on the fly, very chill.
When I set frame rate to below 5, it still looks okay, or it gives the ol battery freeze. However, the jello-cam is godawful. Not sure what's going on there, not a huge deal, I have the 600diz for that.
the rolling shutter/jello footage is one of my biggest complaints about the 6d, has nothing to do with ML.
anything I've shot handheld has been pretty much useless.
QuoteHowever, the jello-cam is godawful.
same as 600d but ya.. weak.
I was able to reproduce dtset's grass effect on similar grass. Rate was crazy, not normal RC rate. clips are 120+
so now we can find out wtf happened and figure out a way to make sure it doesn't.
Ok, solved your defect:
It occurs when target rate < rate produced from qp range. Set bitrate to 50 in the RC config and record iso 512k... now your rate limited to 50 but the defect is on every clip.
The solution: Set target rate in config to like 300 or 250mb/s... this way the camera will never exceed it.
I should have something to post tomorrow, I've not experimented yet with how complicated a raw workflow will be, but I'm going to shoot a short commercial for my wife's father's company. look up the "meet me in big sur" video if you haven't yet, AMAZING
QuoteThe solution: Set target rate in config to like 300 or 250mb/s... this way the camera will never exceed it.
Interesting... Will try
Thank you for adding Kelvin temps - very helpful!
hehehe, I think that was a1ex...
i set it to 180 on my own config. i don't think IPB ever exceeded that. Another interesting thing tho is that ipb pretty much never stops. I can record static from my 42" with it but when I switch to all-I it stops after like 1s.
QuoteSet target rate in config to like 300 or 250mb/s
just to be sure, how many 0s is that?
180000000 mbp/s... I kno too many 0's
FYI, 6D only supports 100MHZ uhs so UHS50 works UHS104 does not... and from sparedog's tests 100mhz performance of 208mhz cards is terrible.
So what is everyone's verdict on the quality of the footage? In my opinion with a pentax 1.4 smc this is some of the nicest footage I've ever seen.
I like the noise profile way better then the ccd cameras currently used in big productions. The footage is just inherently deep in color. And it lends itself well to color correction. It seems like the dark areas of the scene especially have a very nice neep roll off into black. Whereas what I've seen from ccd cameras such as the red is there is always some noise unless you truly crush the blacks in post (cutting at least a few stops off the dynamic range).
Even with bitrate not being anything close to true raw, it seems that ultimately you are getting a more honest dynamic range and color depth solely based on the noise profile.
on thing I can't complain about is iso performance.
But red is 4:2:2+ and not 8 bit and the moire... oh the moire :(
Hate moire!
Triple that! It makes 720 really hard to use, any wide shot seems to get it. I hope the filter helps
But I too love the noise. In all I, it´s really nice, and all the ISOs are useable which is extremely cool
Quote from: gravitatemediagroup on February 11, 2013, 11:54:58 PM
can you post a frame from it?
keep in mind this is my first time attempting RAW
Quote from: sparedog on February 12, 2013, 01:50:57 AM
shoot something and post it
keep in mind this is my first time attempting RAW video and i'm not quite a wizard with resolve yet
jpeg compression isn't doing it any justice, just an example of it's DR
http://www.sendspace.com/file/16ayef
i haven't noticed more noise in all I vs IPB but with inter-frame who knows. maybe the noise pixels are getting compressed across frames, lol.
is that 1080P or downscaled. Looks like 6D/600D sans moire and with good color
Quote from: 1% on February 13, 2013, 04:05:03 AM
i haven't noticed more noise in all I vs IPB but with inter-frame who knows. maybe the noise pixels are getting compressed across frames, lol.
is that 1080P or downscaled. Looks like 6D/600D sans moire and with good color
is this question asked about my print screen, copy/paste in PS jpeg compression frame grabs? lol
trust me, BMCC is in a whole different galaxy from any consumer priced canon
i've owned the bmcc for about 72 hours, and today was my first time using it's RAW video.
I own a 6d, and returned a junk t4i. no cotest
if you own a 2k or 4k monitor I would be more than happy to mail you some footage that wouldn't appear 1080
you could probably give a more honest judgment that way
all you have to do is watch the meet me in big sur video to know that the bmcc is NO 6d or t?i
Only have 2k. Why not take some actual frame grabs?
do you want me to upload one of the dng files? because that is a frame
You could. Would be nice as png or jpeg too. I can just save frames out of h264, not the case for bmcc video?
why would you want a tiff or a jpeg when the clips coming right out of the bmcc are DNG?
a 1 minute RAW clip is roughly 6-7GB and 300-500 dng files
Quote from: gravitatemediagroup on February 13, 2013, 04:19:06 PM
do you want me to upload one of the dng files? because that is a frame
yes please a couple of dngs would be great - different subjects
don't expect to be able to blow them up and zoom in on them like it was shot as a still image with 40MP
you will notice some are over exposed on purpose, grade and play with them however you wish....it's raw for a reason lol
http://www.sendspace.com/file/gfxj3o
Quote from: gravitatemediagroup on February 13, 2013, 07:52:01 PM
don't expect to be able to blow them up and zoom in on them like it was shot as a still image with 40MP
you will notice some are over exposed on purpose, grade and play with them however you wish....it's raw for a reason lol
http://www.sendspace.com/file/gfxj3o
Ok, that is officially very cool!! =D Would be interesting if you do a blog on it as you find pros and cons.
But the rest of us, we can´t give up on the 6D, I think it still has a lot of potential!
compare the price of the 6d to the BMCC and there is no competition.
have you not followed any of the BMCC stuff?
all of the pros and cons are already known, last thing I have time to do it run a blog to state an opinion that people really shouldn't care about
http://www.blackmagicdesign.com/products/blackmagiccinemacamera/techspecs
while you look at this think to yourself 6d=an 8bit turd
canon really messed up big time with the 6d. canon is the only company than can release a newer camera, the performs worse than
a camera that's a year older. I sold off all my Nikon gear to switch over to Canon for photography reasons. And from what I always hear, the Canon does a great job with video so I was looking at it as a 2 for 1 deal. For DSLR video from here on out, the GH2 gets the pick. If the 6d is ever capable of hdmi clean, then I might really consider some things.
The only cons I heard about BMC is moire issues.
Quote from: ManixLiquid on February 13, 2013, 11:55:46 PM
The only cons I heard about BMC is moire issues.
there are others, and moire isn't really an issue. it IS present, but i've seen broadcast cameras present moire. and if you want to talk about 6d moire vc bmcc moire lol
QuoteBut the rest of us, we can´t give up on the 6D, I think it still has a lot of potential!
the video isn't much worse than other canon cameras I've tried. Moire from 5d2 would be interesting to compare. Its definitely worse than 600d crop or not. the bigger sensor is probably to blame. same resize, more lines skipped.
But I know, you paid $2k+ for this camera and at that price I'd be disappointed vs BMCC
from the compare videos of 5d2 vs 6d moire, 5d2 was worse. but I guess it all depends on how scientific you are doing it.
the 6d was a "i hope I can get good video from it" but as a stills camera I can't really complain. and I thought ML for the 6D would break it wide open, but I have yet to have the 6d blow me away. and even if I do shoot anything I can live with, it's on a tripod or glidecam. ive yet to shoot anything handheld with the 6d that I could actually use. with the gh2 being a lighter and way less of a camera body to grip, I can shoot handheld and live with it
Quotefrom the compare videos of 5d2 vs 6d moire, 5d2 was worse
Strongly disagree! I shot with mark ii for 4 years and even though it had moire - it was NOT as bad as on 6d. On the contrary, I feel like photos are better then mark ii.
so why did you buy a 6d?
bmcc 3 clip quick test
http://www.youtube.com/watch?v=bnKxDvXUf6Y&feature=youtu.be
Quoteso why did you buy a 6d?
ISO... and only that
nobody was expecting the moire
Couple of things:
Movie Differences
1: The moire is not as bad as the 5d mk2, they are the same at worst.
2: 720p 60 fps is HUGE with the ultra high ISO capabilities means twixter footage in way different situations then ever before.
3: the screen is WAY better the 5d mk2, which hurt my eyes
Photo differences
1: ACR 7.4 hasn't come out yet, so we won't be able to see the raw files yet.
2: extra fps is nice
3: auto focus is way better, center point is the best of any camera I've ever used (probably 1dx is better, but no one I know has one)
I have, out of about 200 clips, only one clip where the moire is truly bad, it's mostly because of multi color, it's as if the rgb pixel arrangement is vertical, as a result horizontal lines get destroyed, I'm experimenting with a method of removing this in premiere Basically, I want to vertically blur the color channels, while sharpening the black and white. In camera: Try turning the noise removal off and setting sharpness to 0. I've noticed this helps.
QuoteACR 7.4 hasn't come out yet, so we won't be able to see the raw files yet
What are you talking about? I have shot in RAW and delivered to clients already.
QuoteI have, out of about 200 clips
200 clips of what? Did you shoot to test moire or you just shot whatever?
Do you have a m2 right now? Shoot a brick wall or something that has lines (wide angle) and compare the two.
Anyway, we all know the specs- can we move on with testing?
1% what was updated in latest menu bin?
Quote from: gravitatemediagroup on February 14, 2013, 05:12:28 AM
bmcc 3 clip quick test
http://www.youtube.com/watch?v=bnKxDvXUf6Y&feature=youtu.be
Love the look of the flag in the snow, really low contrast
But the opening shot has really weird movement / it is like the video has been reconformed. What frame rate did you shoot and what frame rate did you set Resolve to?
I think something has gone wrong somewhere (maybe just youtube but I dont normally see this kind of framerate stuttering on youtube)
Quote from: 1% on February 14, 2013, 06:24:16 AM
nobody was expecting the moire
so when people realized it was a major issue, why didn't they return? lol
Quote from: sparedog on February 14, 2013, 06:31:00 PM
Love the look of the flag in the snow, really low contrast
But the opening shot has really weird movement / it is like the video has been reconformed. What frame rate did you shoot and what frame rate did you set Resolve to?
I think something has gone wrong somewhere (maybe just youtube but I dont normally see this kind of framerate stuttering on youtube)
it was all 23.97
the weird movement was because I was too close panning too fast lol lesson learned. that's the speed I'm used to panning with lesser quality cameras. lol
also being that I didn't want to spend 5 hours uploading 3 clips I exported to wmv highest quality possible, but even it at top quality doesn't compete. where I live the internet is TERRIBLE
Quoteso when people realized it was a major issue, why didn't they return? lol
I bet people did. But the whole point of this is to have a dual use cinema/still camera. the concept is win, what canon is doing is not.
Quoteso when people realized it was a major issue, why didn't they return
Good question:
In my case, I am a wedding cinematographer, and a photographer. I shoot both, photos and video, and a lot of those shoots are in candle light so I need to maximize ISO. BMCC is a great "cinema" camera but it is not for events mainly because of the file size. Also, it is not ergonomic for running and gunning. If you loaded and get the rig and all that, well, then it is not that affordable is it? :)
I wish we had DNG goodness but hey, - life is a bitch :)
Here is the wedding that I shot over the weekend with 6D: http://www.youtube.com/watch?v=cBtEPLGB2bY
Keep in mind, weddings are crazy and stressful and you almost never have time to do everything right so don't judge - running and gunning baby :)
I wouldn't use a BMCC for a wedding, although it can be done.
Quote from: DTSET123 on February 14, 2013, 08:42:14 PM
Here is the wedding that I shot over the weekend with 6D: http://www.youtube.com/watch?v=cBtEPLGB2bY
For me, this is where DSLRS come into their own, the footage looks great.
If you think back to only 5-6 years ago what you could shoot on for 2000$, it was extemely difficult to get results like this, and then you had to use things like a letus adaptor etc - nightmare
The bmcc is a great product, but as you say, you bought it for more than retail. Add in the price of ssd cards, external battery - due to the 90 minute internal, also add a rig to use it off sticks, and a new lens to get wider than what your EF lens will provide because of the crop, and it probably is in the region of 4000$-$5000 or more?
The 6d, whilst not perfect by any means, cost me the price of the body, everything else I had left over from previous cameras. And that, for me, is it´s strength
Quote from: sparedog on February 14, 2013, 09:34:18 PM
For me, this is where DSLRS come into their own, the footage looks great.
If you think back to only 5-6 years ago what you could shoot on for 2000$, it was extemely difficult to get results like this, and then you had to use things like a letus adaptor etc - nightmare
The bmcc is a great product, but as you say, you bought it for more than retail. Add in the price of ssd cards, external battery - due to the 90 minute internal, also add a rig to use it off sticks, and a new lens to get wider than what your EF lens will provide because of the crop, and it probably is in the region of 4000$-$5000 or more?
The 6d, whilst not perfect by any means, cost me the price of the body, everything else I had left over from previous cameras. And that, for me, is it´s strength
The lenses I use for the bmcc are lenses I already own, or was going to buy anyways.
I didn't HAVE to pay over retail, I was just sick of waiting around.
Even at $5000 it's worth every penny, the image it produces is amazing. It may have it's issues here and there, but
this is their first run, and I would say firmware updates will address 90% of the issues in the near future. The cost of SSD's
are dropping everyday, I would rather pay for SSDs over P2, RED mags. And don't get forget, an extreme pro SD isn't that cheap either.
The cost of 4 extreme pro SD's to equal the size of an SSD would come out to the same cost.
A 6d would ALSO require a rig or stabilizer to produce quality handheld.
If you already have lenses, the cost to quality ratio trumps the 6d by a million...IF your main focus is video.
low light is the ONLY thing the 6d has over the bmcc as far as video. but a majority of the things the bmcc will be shooting
is properly lit settings for shorts/commercials and so on.
has anybody on here ever used a GH2 or is it just live by Canon die by Canon around here?
The only caveat is that you can get a 600D and have mostly everything besides low light performance. 600d $500, 6d $2k... that extra 1500 into lenses/rigs/etc isn't going to do canon any favors.
I really can't understand why you keep comparing a t2i to a 6d. maybe the ML build for the t2i makes it better than 6d?
t3i... I have both of these cameras to compare. Hacked video on both.
have you used a t4i
I had one for about 48 before I sent it back. I about threw up.
and have you ever used a gh2? because I've not seen any canon dslr come close.
I thought the 6d would be able to compete, but it's not even close
Quoteow light is the ONLY thing the 6d has over the bmcc as far as video. but a majority of the things the bmcc will be shooting
is properly lit settings for shorts/commercials and so on
Nobody is arguing that! People pick cameras based on a job. You like BMCC - that's great, as it is indeed a good option but let's stay focused here please. I am following this thread for ML development not camera debates- I already heard all that bla-bla-bla...
Quote
If you think back to only 5-6 years ago what you could shoot on for 2000$, it was extemely difficult to get results like this
Amen to that brother!
Quote from: gravitatemediagroup on February 14, 2013, 10:25:56 PM
The lenses I use for the bmcc are lenses I already own, or was going to buy anyways.
I didn't HAVE to pay over retail, I was just sick of waiting around.
Even at $5000 it's worth every penny, the image it produces is amazing. It may have it's issues here and there, but
this is their first run, and I would say firmware updates will address 90% of the issues in the near future. The cost of SSD's
are dropping everyday, I would rather pay for SSDs over P2, RED mags. And don't get forget, an extreme pro SD isn't that cheap either.
The cost of 4 extreme pro SD's to equal the size of an SSD would come out to the same cost.
A 6d would ALSO require a rig or stabilizer to produce quality handheld.
If you already have lenses, the cost to quality ratio trumps the 6d by a million...IF your main focus is video.
low light is the ONLY thing the 6d has over the bmcc as far as video. but a majority of the things the bmcc will be shooting
is properly lit settings for shorts/commercials and so on.
has anybody on here ever used a GH2 or is it just live by Canon die by Canon around here?
I agree with what you say, but we have to get back to topic. This is a forum for hacking the 6d. And we have been distracted (although interestingly) and I am as much to blame as anyone BUT
Please keep the comments ML 6d hack related.
the real question is HAS the 6d been officially hacked?
or do I have to worry about it crashing every 10 seconds?
1% - Do you think quick af will always interfere with ML? It is useable, but a little bit of a pain
1% - I had this error today
I think with autoexec.bin.event0 build
Quotethe real question is HAS the 6d been officially hacked?
or do I have to worry about it crashing every 10 seconds?
You mean the ini files? cause my 6D does not crash...
hehe,
Quotehave you used a t4i
No crop mode :( Maybe squeeze a few more frames out because off UHS. touch screen is meh. I had hoped t4i would be an improvement on 600d.
GH2 is nice for video I guess but stills are a diff matter plus there are other drawbacks.
QuoteIf you think back to only 5-6 years ago what you could shoot on for 2000$, it was extemely difficult to get results like this
Thats spot on. All of these cameras aren't terrible and more than enough resolution to be projected pretty big or go online. Something to be said too about just how much disk space you will be using with that raw workflow on any decent length project. everything has drawbacks you have to live with
... looks like something happened to the fonts? how do I reproduce it?
af will interfere, it drops the mirror
QuoteHAS the 6d been officially hacked
no, we all been faking it
Quote from: 1% on February 15, 2013, 12:40:37 AM
... looks like something happened to the fonts? how do I reproduce it?
af will interfere, it drops the mirror
no, we all been faking it
doing a fine job
99% of the people using the gh2 are using is for video. and what other drawbacks are you speaking on?
and you said "for video I guess" ? it goes toe to toe with a RED as far as detail and "you guess?"
Quotet goes toe to toe with a RED as far as detail and "you guess?"
lol...
Quote from: DTSET123 on February 15, 2013, 01:30:49 AM
lol...
evidence that you don't know much about the GH2
http://www.youtube.com/watch?v=V_A6cZ50Lqc
Iso performance for one.
Quote from: 1% on February 15, 2013, 01:37:51 AM
Iso performance for one.
gonna need more than one. neat video does a pretty good job
not to mention not too many people are out shooting vampire documentaries
the fact that the gh2 was included in "the great shootout" says a lot as well
http://www.imaging-resource.com/news/2012/07/24/panasonic-gh2-video-better-than-red-arri-says-coppola
watch the 2nd video from where they say, and then after listen to what people wilth more credit than anyone here
has to says about the gh2
smaller sensor, way worse low light... lack of electronic lens mounts, sure you can adapt "anything" but have fun with manual or non existent aperture control
Quote from: 1% on February 15, 2013, 01:45:02 AM
smaller sensor, way worse low light... lack of electronic lens mounts, sure you can adapt "anything" but have fun with manual or non existent aperture control
that "smaller sensor" argument is pointless and overrated...."smaller sensor & worse low light" fall in the same category
http://admiringlight.com/blog/full-frame-equivalence-and-why-it-doesnt-matter/
and what do you mean manual or non existent aperture control? lol
Quotethat "smaller sensor" argument is pointless and overrated
Its a drawback you have to work around, as much as canon resize problems and lack of 4:2:2.
unless you use gh2 native lenses you won't have any electronic aperture control (or AF, same principle).
Quote from: 1% on February 15, 2013, 01:59:39 AM
Its a drawback you have to work around, as much as canon resize problems and lack of 4:2:2.
unless you use gh2 native lenses you won't have any electronic aperture control (or AF, same principle).
most lenses I own have de clicked aperture, and the ones that don't I use a variND and it works perfect
GH 2 is still h.264 8 bit good luck color grading that shit. Why is it that I don't see motion films shot on it? I know a lot that was shot with RED- maybe there is a reason? In the shoot out that you are talking about there was 5D and 7D too- so? It is just another tool. You can shoot with iPhone for that matter, if you have a good content.
no, the shootout i'm talking about didn't have a 5d
go to the link I posted above, they used the 7d
and if you listen close to the comments it was "gh2 really surprised me" and "typical canon moire"
the gh2 grades just as fine as any canon dslr
shot on gh2, premiered at sundance
http://vimeo.com/user726396/headlikethesun
http://vimeo.com/53483898
to say the gh2 can't be color graded...this was done by a person that has NEVER made an attempt at grading with 3 way color
AMAZING
http://vimeo.com/59502661#at=0
it is alright to leave the canon bubble for a little bit and experience and learn about some other cameras from time to time guys
these comments are what makes me think canon truly has their customers brainwashed to buy their underachieving overpriced cameras
QuoteWhy is it that I don't see motion films shot on it?
When money matters you rent a camera that you don't have to mess around with.
I never said GH2 sucks, just has drawbacks like canon in different areas. Neither camera is a hassle free solution.
Quote from: 1% on February 15, 2013, 02:30:46 AM
When money matters you rent a camera that you don't have to mess around with.
I never said GH2 sucks, just has drawbacks like canon in different areas. Neither camera is a hassle free solution.
is there a camera that's hassle free? lol
Quote from: DTSET123 on February 15, 2013, 02:15:31 AM
GH 2 is still h.264 8 bit good luck color grading that shit. Why is it that I don't see motion films shot on it? I know a lot that was shot with RED- maybe there is a reason? In the shoot out that you are talking about there was 5D and 7D too- so? It is just another tool. You can shoot with iPhone for that matter, if you have a good content.
the sad part about the gh2 competing in this shootout vs is a RED Epic (as far as detail) is he wasn't even using the highest bit patch
http://vimeo.com/30751603
i got 176mb video out of 600D too.
all of these cameras give you more than enough. sd is barely dead. many displays not even 1080P. grading at 4:2:0 8 bit is the same problem for all
Quote from: 1% on February 15, 2013, 03:18:50 AM
i got 176mb video out of 600D too.
all of these cameras give you more than enough. sd is barely dead. many displays not even 1080P. grading at 4:2:0 8 bit is the same problem for all
I've never really had an issue where I couldn't do enough with 8 bit. If a shot was over exposed and blown yet, yeah. but as far as doing some color tweaking, no. I don't do any green screen or crazy special effects, and outside of those to things, 8bit color is just an excuse people give and they don't even know why.
8bit is pretty much still broadcast standard, by the time it makes it's way to the television and what not.
the canon 70-200 is on sale for 1100 on amazon if anybody cares ; )
See you keep saying I use this and I use that... I, I, I, me, me, me. It's all matter of preference. It is all about the job and what DP wants to accomplish. Stop trying to change people's opinion on what equipment to use. If GH2 works for you, then return your BMCC and stick with it. I love the look canon gives me (for what I do) but I don't go to Sony or Panasonic forums and tell them how their cameras suck and that it is OK to leave it. Everything that you said (wasted your energy on typing) is a waist! You did not change my mind as everything you told here is old news. Yes, I like canon look and I am sticking with it (for now). I take canon 5d or 6d over GH2 anytime of the day, so would you please give it a rest. You have made some decisions for yourself - that's great! Don't force them to people who have made theirs! Keep shooting and have fun!
Men,
Isn't this post about Canon 6D ML port ?
So why feeling it with comments about GH2 (a great cam i own too) or BMCC (a great cam i'll never own) ?
Can we focus on the Canon 6D ML port ?
Tech concerns, status of porting ? Bug tracking ? Estimate date of 1st alpha #1...
Would be greater, in my opinion...
Christophe
you can use it now, you can call it an alpha or beta if you want.
Quotestatus of porting
Audio - needs work/datasheeet, asif needs to stop properly
prop lv lense - needs checking so the lens info stuff woks
bulb ramping calibration failed with silent pics, have to see why
besides that most things work. pretty much where 600D was on 2.3 release
Great news ! (i own a 6D).
A place we can DL a compiled version to try ?
Thanks
On bitbucket since jan:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Sorry to bother, to make it work, i need to have on SD card:
- 6d-112.fir
- autoexec.bin
And make a firmware update, right ?
+ ml support files like fonts. you can use ML folder from nightlies or 2.3
also h264 configs from bitbucket go in the ML folder
Quote from: DTSET123 on February 15, 2013, 06:22:35 AM
See you keep saying I use this and I use that... I, I, I, me, me, me. It's all matter of preference. It is all about the job and what DP wants to accomplish. Stop trying to change people's opinion on what equipment to use. If GH2 works for you, then return your BMCC and stick with it. I love the look canon gives me (for what I do) but I don't go to Sony or Panasonic forums and tell them how their cameras suck and that it is OK to leave it. Everything that you said (wasted your energy on typing) is a waist! You did not change my mind as everything you told here is old news. Yes, I like canon look and I am sticking with it (for now). I take canon 5d or 6d over GH2 anytime of the day, so would you please give it a rest. You have made some decisions for yourself - that's great! Don't force them to people who have made theirs! Keep shooting and have fun!
Woah dude, nobody is putting a gun to your head.
I will use the gh2 for this and BMCC for that. I'm just thinking that living in a canon bubble isn't very healthy.
I'm sorry that you and I bought the underachieving 6d and it's only TRUE strength is low light.
I would bet $100 if you used a gh2 for a week and got familiar with it using the latest patch
Your opinion of canon might change. Are you upset that the gh2 does in FACT go toe to toe with the detail of an epic?
Like I said way earlier, I'll continue to follow the ML development for the 6D, and will dump the 6d in a heart beat
When the 7d mk2 is released. I see people dump canon for the gh2 and never look back (for video) where as I was looking for something from Canon to accompany my gh2 (6D) and have been pretty disappointed. I've yet to see anything from the 6d look as nice as a 5d or 7d. How can canon allow this to happen? For $2k
and a newer model camera it underachieves compared to older models? What's the extra money for? Wifi that is only useful for photos?
Me... again !
After updating firmware,
Firmware 0
Bootdisk -1
RAM_EXE -1
Update -1
After camera restart, no ML under delete button in LV mode.
Quote from: teo770 on February 15, 2013, 06:40:17 PM
Me... again !
After updating firmware,
Firmware 0
Bootdisk -1
RAM_EXE -1
Update -1
After camera restart, no ML under delete button in LV mode.
go back to pages 5-9 of this topic and look for the instructions
Quote5d or 7d
Its on par with those but not 600D crop. Also the NR works in movie mode so turn it off
so you're saying the 600d is better than the 6d? obviously with the help of ML?
QuoteYour opinion of canon might change
What makes you think that I have never shot on a hacked GH2? Stop this nonsense please!!! THIS IS A DEVELOPMENT THREAD!
600D crop is better, 600D regular video about the same with a little less moire
Quote from: DTSET123 on February 15, 2013, 09:24:41 PM
What makes you think that I have never shot on a hacked GH2? Stop this nonsense please!!! THIS IS A DEVELOPMENT THREAD!
you are going to give yourself a heart attack.
do you notice how me and 1% have had a sub conversation like adults?
how do I know you HAVE shot with a hacked GH2, and if so, what patch was you running.
no sense in fighting... panasonic isn't perfect either. I bet GH2 resolves better than cameras like HMC-150 which cost way more.
Quoteif so, what patch was you running
OMG.., here we go again - relax kid! I have tried cedna, cluster vanilla and i have tried configuring my own. I have followed vitaly and driftwood for some time now. I do like HG2 and 3, I just don't like you being annoying about it! It is just another camera and just another tool- that's all. What's best is subjective and a matter of preference for the given job. People here want to learn about ML. Why don't you start a new thread and talk the opinions there and leave this for Tragic Lantern development- PLEASE!
Anyone test built in NR effect on moire?
Quote from: 1% on February 15, 2013, 11:23:40 PM
no sense in fighting... panasonic isn't perfect either. I bet GH2 resolves better than cameras like HMC-150 which cost way more.
it does, I've had a 150 and ac130 and didn't care for them. It was nice having built in ND filters and XLR, but other than that is was just crap
People come here for 6d ML information; all they gonna find is pages and pages of gh2 nonsense. Be considerate of others please!
Quote from: DTSET123 on February 15, 2013, 11:27:19 PM
OMG.., here we go again - relax kid! I have tried cedna, cluster vanilla and i have tried configuring my own. I have followed vitaly and driftwood for some time now. I do like HG2 and 3, I just don't like you being annoying about it! It is just another camera and just another tool- that's all. What's best is subjective and a matter of preference for the given job. People here want to learn about ML. Why don't you start a new thread and talk the opinions there and leave this for Tragic Lantern development- PLEASE!
you say "OMG" and then call me "kid" makes me curious to how old you are.
I'm not being annoying about anything, it's called a debate "kid" if you don't like what I'm talking about, you are not being forced to comment.
This still is a ML development thread, and when news comes about, we can discuss. But I don't see you blowing the topic up with pros, cons, what works, test shots, frame grabs, or any other discussion regarding ML. All I see is you becoming defensive on Canon's behalf.
oh, BTW GH2 video>6D video forever and always. xoxo lol
Quote from: DTSET123 on February 15, 2013, 11:44:12 PM
People come here for 6d ML information; all they gonna find is pages and pages of gh2 nonsense. Be considerate of others please!
what are you contributing to the testing of ML?
your wedding video description on youtube says 6d with ML....but you told us you didn't really use ML at the wedding?
Quotewhat are you contributing to the testing of ML
and you?
Quote from: DTSET123 on February 15, 2013, 11:51:31 PM
and you?
i've made it known several times that several combinations of settings are causing the 6d to crash, rending it useless to EVER attempt using it for anything professional. If I can't get a solid 90-120mb/s to fully function properly without crashing every other rec/stop then what's the point?
I've tried the suggested combinations.....same ol' same crash crash crash
gh2 at 144mbs and higher = never crash
the 6d with ML for high bit isn't dependable yet.......the reason you didn't even dare think about using it at the wedding
just reviewed a 6d clip that showed moire in dirt lol
QuoteI've tried the suggested combinations.....same ol' same crash crash crash
You still must be setting something wrong if you haven't been able to record any clips. Maybe has an error once every 20 clips, mainly when you start recording before the config is loaded. Wait till text clears the screen.
a lot of the problem is from canon. it only lets you load configs or record fixed qp.
Quotegh2 at 144mbs and higher = never crash
Software vs hardware encoder so some blame on ti's chip falling apart when stressed. the default rates for IPB are barely 30MB/s and we're pushing over all I rates. Stock IPB not good for much but youtube delivery
Quotehttp://www.eoshd.com/content/3498/gh2-avchd-vs-mjpeg-which-is-best
So when jpeg is figured out here, we'll see who's laughing.
Quote from: 1% on February 15, 2013, 11:39:34 PM
Anyone test built in NR effect on moire?
sorry did I miss this? Its getting tricky to see development now. Please explain what you mean - or point me to the thread :)
I don´t get a problem with recording 150mbits pretty much everytime. I only change the quantising, nothing else - that way I can learn what will spike the bitrate pretty reliably and adjust accordingly. I find it is easier when I have to deal with only one number
MAGIC ZOOM is now corrupted on latest build
autoexec.bin.new iconsautoexec.bin.new icons
It does weird flashing and eventually loads/or doesnt :(
in fullscreen mode, havent tested other modes
in other modes, unsuable
and greyed out
QuoteSo when jpeg is figured out here, we'll see who's laughing
can't wait!
I set target rate in RCini to 300000000 like you suggested and it still crashed at complex scenes, but it is stable at 60-65 if I override bit rate to 8 tho. Does that make sense?
QuoteIt does weird flashing
yep, same here!
Quote from: sparedog on February 16, 2013, 01:14:29 AM
MAGIC ZOOM is now corrupted on latest build
autoexec.bin.new iconsautoexec.bin.new icons
It does weird flashing and eventually loads/or doesnt :(
in fullscreen mode, havent tested other modes
in other modes, unsuable
and greyed out
@ 1% yeah, we will see who's laughing lol
the gh2 can shoot in mjpeg that is ALMOST 2k, it's not TRUE 2k, but it's damn close
plus thats a fairly old article and way better patches have been developed since.
notice where Andrew says "Disclaimer: things change fast in the hack world. What may be true today may not be true tomorrow. Always check the latest developments."
I'm currently uploading my 6D test edit, please tell me the 6d is better than the gh2 when you notice the massive amounts of moire in dirt lol
On the ML vectorscope, is the line between red and yellow calibrated to be the skintone line?
QuotePlease explain what you mean - or point me to the thread
the canon "high iso noise reduction"... it looks to me to be adding moire
QuoteIt does weird flashing and eventually loads/or doesn
I see, does it for 60P. Its from kill flicker killing the zoom box. Going to check this out. Its grayed out from the menu stuff going down in the nightlies.
QuoteI set target rate in RCini to 300000000 like you suggested and it still crashed at complex scenes, but it is stable at 60-65 if I override bit rate to 8 tho. Does that make sense?
overriding rC makes it not RC anymore. try for 180 instead of 300. all I has been stopping with it but IPB has not. maybe need a limited config for all-i and raised limit for IPB. I think IPB only had the defect
Are there color bars in ML and if not is it possible to add my own jpegs to ML?
Quote from: 1% on February 16, 2013, 01:34:36 AM
the canon "high iso noise reduction"... it looks to me to be adding moire
Dont know, seems to be just as bad without. but its dark outside so I will test some more tomorrow in the day
http://www.youtube.com/watch?v=bv_aBg3m_ag&feature=youtu.be
Nice roomba :)
the kill flicker bug present on 600D in 60p too :(
did you see the moire in the dirt?
it's the shot where there is a tree and a wide open field in the background
the only other thing I KIND OF give credit to the 6d for other than low light is close up shots. even when focused to infinity
things in the background just get smashed into mud
in 720P mode I see moire in a stack of papers. Its definitely from the resizing... look in MZ the moire increases, that is MORE scaling for YUV..
I don't see the defect in all-I so rate control does slow down all I without causing the temporal destruction from cursory testing. I'm going to have to have it load a different RC based on mode. For now you can place contents of RC in h264.ini and manually load it. I'll check to see if overriding just bit rate will accomplish the same thing or if it stops switching qps.
anyways, apparently the mjpeg stuff is ready, we just have to make the camera create a jpeg in memory. so blocked by low level complications again :(
Heh, found defects in all-i too. Maybe can expand the QP range somehow? The overriding for target rate might be working, however. It looks to be switching.
will opening up jpeg allow it to be pushed to a 2 to 4K resolution?
and i'm guessing it's impossible to up the cameras burst rate to like 18fps in either jpeg or raw
I'm guessing over time it would destroy the shutter?
did you ever see that video of the 1dc shooting stills at 18fps and pieced together into a 18fps video? no audio, but had a pretty cool/unique look about it.
I already did that with .422s. We only got like 15fps or less on both 600D and 6D.
The jpeg would be in the buffer so no clickety click.
LV window I think is 2k only. Canon created jpeg on 600D was only 1024x760. Will depend on how much control there is over the process. Right now the hard part isn't figured it out.
Another way to lick the temporal defect bug is to expand the QP range. It looked like it would only take 13 QPs from analysis before but looks to be working now:
Before you ask, I had bit rate overridden to 50(thats 500Mb/s) so of course it favors QP1. Had to make sure it still went there.
average DRF 1.376552
standard deviation 2.334214
max DRF 23
DRF=1 701 ( 96.690 %) ###################
DRF=2 2 ( 0.276 %)
DRF=3 0 ( 0.000 %)
DRF=4 1 ( 0.138 %)
DRF=5 1 ( 0.138 %)
DRF=6 1 ( 0.138 %)
DRF=7 2 ( 0.276 %)
DRF=8 1 ( 0.138 %)
DRF=9 1 ( 0.138 %)
DRF=10 1 ( 0.138 %)
DRF=11 1 ( 0.138 %)
DRF=12 1 ( 0.138 %)
DRF=13 1 ( 0.138 %)
DRF=14 1 ( 0.138 %)
DRF=15 1 ( 0.138 %)
DRF=16 2 ( 0.276 %)
DRF=17 1 ( 0.138 %)
DRF=18 1 ( 0.138 %)
DRF=19 1 ( 0.138 %)
DRF=20 1 ( 0.138 %)
DRF=21 1 ( 0.138 %)
DRF=22 1 ( 0.138 %)
DRF=23 1 ( 0.138 %)
DRF>23 0 ( 0.000 %)
I tried many different values for target rate. 300 works until I point it to this resolution star to simulate complex scene. So far none of the different combinations that I have tried with ini modifications (override or not) have survived the star more then a minute:(
Does it defect or just stop?
Transform8x8Flag = 2
Profile = 100
Level = 51
BitRate = 110000000
EntropyCodingMode = 1
IntraPicInitQP = -1
InterPicInitQP = -1
QpOffsetForB = 0
MinQpI = 1
MinQpP = 1
MinQpB = 1
MaxQpI = 25
MaxQpP = 25
MaxQpB = 25
MinBitrate = 60000000
MaxBitrate = 110000000
SarWidth = 0
SarHeight = 0
AspectRatioIdc = 1
VideoFmtAndVspFlag = 81
VideoFullRangeFlag = 1
TimingInfoPresentFlag = 0
RateControlEnable = 2
ScalingMatrices = 0
pScalingMatrixAddr[0] = 0
pScalingMatrixAddr[1] = 0
pScalingMatrixAddr[2] = 0
pScalingMatrixAddr[3] = 0
pScalingMatrixAddr[4] = 0
pScalingMatrixAddr[5] = 0
That should expand the QP range enough to avoid the defect at most normal rates (ie, you're not kicking it down to 10). I don't get a frame by frame of QP on IPB, I need to find different analysis tools or change container to something else. Try the chart with that. Also try the chart with it kicked down to 80Mb/s from the ml menu. Do you get defects or any quality loss?
*PS this chart kicks ass. Seems to really stress the camera, especially moving it around the image.
Changing containers lets you open the files in bit rate viewer. I still can't see a quant analysis for IPB :(
The graphs look like 600D graphs but this time canon is doing the QP switching. Guess we're both on the same page with that.
Shooting the chart... the drop is when my screen turned off:
(http://imgur.com/Sikxuyd)
Ok, while you guys are figuring out the 6d issues, I thought I would share this amazing music video shot with gh2.
Probably the last thing gh2 related I post.
http://youtu.be/YhqTsAmPYYs
You can see why it holds it's own against cameras 10x the cost.
There is no more denying the gh2 grading ability.
No need to reply to this. Continue developing.
Works great! Both IPB and All-I. As far as quality, don't know. It is hard to tell. I do not see any difference between the stock or this configuration to be honest. Someone with more knowledge would have to check but the good news is that it is stable! I have been using this chart for a while and if ini can survive this then it will survive the grass. QP jumps between 1-25 in your config right? So the next question comes to mind is: What is the stock qp? Is it also variable?
Wow, how did they get a gh2 in space?
anyway...... Excited to see the development of the 6d, I thoroughly enjoy it as a still camera, and use the video function as more of a hobby, but this is definitely fun to watch this ml development process. I've still never encountered any moire (though i've only shot in 24p, no saturation etc.)
But I've had a few rolling shutter issues. I do enjoy it more than my 600d.
And keep in mind in this "what camera is really cool" ordeal. I've seen amazing projects shot on mini dv, and non amazing projects on red's. It's about content, non the equipment. Give edvard munch a crayola and he'll probably impress you.
QuoteWhat is the stock qp? Is it also variable?
Like 15-50. To get those low IPB rates it must not be very good. The all-I opens in avi-naptic and you can see the qp distribution. The IPB I hope follows the same deal. All I can see is average qp, but that seems to just be the max.
I guess one can compare the 2 config and stock. Nothing wants to analyze the IPB though. I want to avoid the defect but not make it pick worse qps in the process.
QuoteIt's about content, non the equipment.
Truth, you don't want to be limited by equipment but it doesn't make the production.
Quote from: 1% on February 16, 2013, 01:34:36 AM
Its from kill flicker killing the zoom box.
Why do you need kill flicker? That's a ugly workaround for 50D, where I couldn't draw anything on screen without Canon erasing it...
it kills the stuff that comes up when you press h/s
And also other useful things (temperature warning, whatever pops on the screen without creating a new dialog box).
On most new cameras I chose to leave that stuff on the screen, and just pause ML updates until it disappears.
scroll wheels didn't work either. any ay to just kill the half shutter dialog?
Scrollwheels in menu? check GUIMODE_ML_MENU.
Halfshutter stuff can be cache hacked (around JudgeBottomInfoDispTimer stuff). Didn't try, because I like non-invasive solutions when possible.
I finaly success in instaling ML on Canon 6D, thanks all !
For other newbies like me, steps are:
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
- Get 6d-112.fir from:
http://bit.ly/ZgvGUf
- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini
- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card
- Put SD card in camera and update firmware while in M mode. Restart. That's it.
Bug tracking
Is it the better place to submit bugs ?
Cause i don't want to submit already knows issues
Thanks
There seems to be almost no known bugs, so post them here.
Quotebesides that most things work. pretty much where 600D was on 2.3 release
I'm not so sure.
Quote from: teo770 on February 16, 2013, 10:09:52 AM
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
I don't have a windows machine around to run this step on, does anyone know how to do this on a Linux box? (or if someone can point me at a _small_ image of a card that's been treated this way I can try to dig into it myself)
Lack: Audio / Headphone Monitoring
On the 5D Mark II, there was a jack 3.5 AV output, you could get headphones monitoring by using the AV cable supplied with camera or SESCOM cable.
On 6D, the AV output uses the USB port and without ML, just plugin the cable disabled the Liveview.
With ML, plugin the cable doesn't disable the Liveview, ML detect the plugged cable "headphones connected" but no sound is coming out on Red and white wires.
Dlang: i made you an iso of my SD card with ML 2.3 on
http://ge.tt/204RWcY/v/0
Quote from: teo770 on February 16, 2013, 11:33:08 AM
Dlang: i made you an iso of my SD card with ML 2.3 on
http://ge.tt/204RWcY/v/0
hmm, something went wrong. I unzipped the file I downloaded then wrote it to a SD card (via dd) and the camera says it can't read the card.
digging a bit more, this is a udf formatted card now, which makes sense if you made the contents of the card into an ISO, but as I understand it, there needs to be some specific things at specific places on the card for the camera to read it, which is what the eoscard tool does, so making an ISO of the contents won't work.
See the install guide and click on the links ;)
Any rough ETA on 6D alpha1?
Bug displaying ML menus on LV
When not in LV, ML menus display normaly
When in LV, ML menus crash after 8 seconds every time
In the down right corner appears a kind of little red wheel and ML menus don't work anymore. You have to exit ML with del button and re-enter in ML menus.
Same thing happend in all modes: M, P... etc
I'm using "autoexec.bin.new icons"
That's like EOS-M (probably 650D needs it too). I've enabled the M workaround for all cameras, but it's still not very clean.
I get the red wheel and it just kills the scroll wheel. Menu doesn't cash tho (still works with arrows). this is in the latest though with no kill flicker. The piggybacked menu dies out?
also... on 6d MZ seems to work just fine in 60P. warning doesn't apply
you can post reproducible bugs on the repo issue page... probably better then losing it in here
QuoteI'm not so sure.
I've tried to test everything as best i can, even stuff i don't normally use.
QuoteML detect the plugged cable "headphones connected" but no sound is coming out on Red and white wires.
making audio work is on the agenda. can somewhat communicate with the IC but no datasheet or anything yet
And, from direct experience with ~10 ports, I know that it's way too easy for one person to miss things when testing. Especially that (you just said it) even basic menu navigation has problems...
For reference, here's some of the tests I've ran for the 5D3 alpha 1: https://docs.google.com/spreadsheet/viewform?formkey=dFRxbGZlUHYyOHB6SDZWZFVpUlVRTUE6MA#gid=0
and for 2.3: https://docs.google.com/spreadsheet/viewform?formkey=dG1FMjVQUEtjWV8zSlpaeEZtZDBQZ2c6MQ#gid=0
The menus changed a bit since then, so those checklists in google forms aren't quite up to date. I'm also pretty sure that current code base fails some of the valid tests described there. Maybe you can suggest something a bit easier to maintain (editing them is not quite easy).
Also take a look at the big bunch of fixes commited when I've got the 5Dc and the 7D. I've noticed a LOT of stuff present in menus and not working at all.
No offence to anyone, it's just that I know what I did to get something that doesn't crash every time you go out in the field. And it seems that I'm not there yet (still having problems with 5D3 ML, like random lockups or black pictures every now and then, and I can't quite reproduce them).
I've had no issues with stills, mainly things that push the camera in LV.
QuoteI've noticed a LOT of stuff present in menus and not working at all.
Most of my menu stuff working working now, I've tried to comb through it and make sure. Some things aren't perfect. There is also the difference between someone like us operating the camera and someone unfamiliar with internals just wanting to shoot and go home.
Main thing with this is that I don't shoot in 720P nor use the wheels most of the time, was just happy to lose the canon dialog. But yea, kind of a big thing to miss. I have past bins up so if there is a regression please inform me about it and use a past bin till its fixed.
Before we hit a stable main page release, a lot of testing will have to be done and I'll probably need to make something like what you have here for 2.3 Its still the most working digic V port right now because it absorbed all the hard work from 5d3/m/650d, etc.
I've been implementing something or testing almost every day and have not had any failures when I really needed the camera. Nobody has done like a 14hr balls to the wall shoot with it though.
Bug: ML crash in LV
autoexec.bin.a1exscrlwheelfx kind of fixed the problem. Always the 8seconds gap, but instead of crashing, ML blinks as if it was restarted.
Bug: Central focus point gone
Just noticed this, either with autoexec.bin.a1exscrlwheelfx or autoexec.bin-nokillfflicker, central focus point disapears after ML loads or after focusing.
>>Bug: Central focus point gone
That's a feature to hide the AF box.
:) sorry
A feature we can disabled ?
Yep. go to focus box settings, same as other ML variants.
Some test shots from this morning, stabilized with ae
http://youtu.be/EoexeSf4JAk
QuoteNobody has done like a 14hr balls to the wall shoot with it though.
I have (kind of)! The wedding that I shot, it was 10 hours of shooting. I shot 115GB of material and Tragic Lantern did not fail once.
I fixed high res slient pics and preview for zoom pics. Does the intervalometer seem too fast? i set to 10 seconds and seems like 1s at least for silent pics.
needs a couple more tweaks for 5x5/4x4, not moving zoom box to correct spot.
went out to shoot some gh2/bmcc/6d compare shots today, and would't ya know it. 6d was crash city. bit 0 qp 0 CRASH. lol how is this even possible?
I dunno, do you have configs in the ML folder and are they right? Did you leave autoload on?
I think I found a new bug: when follow focus is set to arrows, you can control focus electronically but if you accidentally hit play button instead of zoom (while recording) the focus motor goes bananas.
That's rack focus.
Set the focus you want, set steps to 0 (here). focus somewhere else with buttons. when you press play it should return the 0 position. Only works while recording though unless you activate it from the menu.
Ops.., sorry!
hehe, no worries, I didn't even know it did that till you told me. Actually kind of cool, will use it.
Quote from: 1% on February 18, 2013, 12:54:05 AM
hehe, no worries, I didn't even know it did that till you told me. Actually kind of cool, will use it.
if you can work out an easier way to set it up, I´ll worship you forever. i have tried to use rack focus since the beginning of this hack and it is so convoluted to setup, i give up most of the time
Its usable when you set the start/end point before recording, otherwise good luck doing it on the fly. It just steps x in a direction. I think its a problem for all of ML but I can't think of a better way to do it.
why is there no MZ half-shutter? I miss it. I loved it on 5dmii
I found three differences from ML to 550d.
1. In Live View focal length is not displayed correctly.
2. In Live View exposure does not appear, I mean 2, 0, -3
3.Tak same in Live View used to be easy to expose the white balance, any plans to do so as it was before? Previously, you could quickly with a few clicks to set the white balance and you want to enter the white balance, Q, go down and press auto adjust kelvin + G / M. Previously, it was just the way auto adjust kelvin without G / M, is it possible to do as it was before?
Sorry for the English, translated by google translator
QuoteIn Live View focal length is not displayed correctly.
Thats prop LV lens, its different has to be re checked. Its on the list to fix.
QuoteIn Live View exposure does not appear, I mean 2, 0, -3
Download newer build without kill flicker. Is that exposure even right? I use the spot meter or just look at the scene usually.
Quoteit was just the way auto adjust kelvin without G / M, is it possible to do as it was before?
Probably the result of the new menus. You can use the shortcuts and press set and it will pick a kelvin.
Quotewhy is there no MZ half-shutter? I miss it
This is a ML problem in general. Its only set up to use either the zoom button or half shutter. I think it should let you chose canon zoom or mz on half shutter. You can choose mz or shortcuts for doubleclick. Eventually plan on doing the same thing for h/s. Its from the "no zoom button while recording" in internals.h
Hello everybody,
first off, let me say that I'm really impressed by the porting progress to the 6D! I've used ML already at the 60D and it worked like a charm. As I preferably do time lapse sequences, I came across an issue yesterday when testing the bulb ramping feature (both the regular feedback controller and LRT) of which I'm not sure whether it is a bug or not. Therefore, my question: Is it desired that ML takes "bulb" ramping literally, i.e., should it _always_ shoot in bulb mode? This means that exposures faster than BULB_MIN_EXPOSURE (0.5 sec) are not possible. In turn, without ND filters this feature is pretty useless... As well, at the 60D I didn't have this problem.
What is strange as well is that if the scene is obviously too bright, ML shortens the exposure time step by step (as shown on the LCD display), but for the next picture, it again switches to bulb mode and exposes 0.5 seconds. Again, the picture is too bright, and the shutter time is shortened, at least in theory :)
Thanks and best regards from Austria!
Johannes
The bulb ramping calibration failed for me too, could be related. I have to look at those functions and find out what is going on but good catch as I generally don't use this.
Normally, taking a normal picture at 0.5 seconds and a bulb one at 0.5 seconds should result in the same exposure. If not, you need to adjust BULB_EXPOSURE_CORRECTION.
Some code that does this automatically:
int measure_brightness_level_at_median()
{
msleep(500);
struct vram_info * vram = get_yuv422_vram();
hist_build(vram->vram, vram->width, vram->pitch);
int ans = hist_get_percentile_level(50);
return ans;
}
static int ref_bulb_level = 0;
int crit_bulb_calibrate(int cor)
{
bulb_take_pic(500 + cor);
ensure_play_or_qr_mode_after_shot();
msleep(500);
int bulb_level = measure_brightness_level_at_median();
NotifyBox(1000, "ref=%d cor=%d => err=%d ", ref_bulb_level, cor, bulb_level - ref_bulb_level);
msleep(1000);
return ref_bulb_level - bulb_level;
}
void bulb_calibrate()
{
msleep(2000);
lens_set_rawshutter(64); // 0.5 seconds
lens_take_picture(64,0);
ensure_play_or_qr_mode_after_shot();
msleep(500);
ref_bulb_level = measure_brightness_level_at_median();
NotifyBox(1000, "ref=%d ", ref_bulb_level);
msleep(1000);
int cor = bin_search(-500, 500, crit_bulb_calibrate);
beep();
NotifyBox(20000, "def BULB_EXPOSURE_CORRECTION %d", BULB_EXPOSURE_CORRECTION + cor);
}
Returned 649 for me. Going to set it to that and see if calibration fails.
Wow, that's huge...
Calibration passes with photos, doesn't want to do it for silent pics tho.
Silent pics don't work with bulb ramping.
I used ML with my 550D close to the beginning of ML and loved it but recently sold it and purchased the 6D. I finally decided to install ML yesterday using the autoexec.bin-SilentPic build and it seems to be fairly unstable. I would imagine that this is primarily due to it being still in the development stages.
The question I have is being that it is still in development will I ever need (baring a new firmware update from Canon) to upgrade the 6D-fir file? Is that still being developed? It seems that the only file I will need to update is the autoexec.bin file as it changes and continues to be developed ... is that correct?
Thanks for your efforts and I've always enjoyed following the development of ML!
Quote from: rktaylor on February 18, 2013, 11:44:52 PM
I used ML with my 550D close to the beginning of ML and loved it but recently sold it and purchased the 6D. I finally decided to install ML yesterday using the autoexec.bin-SilentPic build and it seems to be fairly unstable. I would imagine that this is primarily due to it being still in the development stages.
The question I have is being that it is still in development will I ever need (baring a new firmware update from Canon) to upgrade the 6D-fir file? Is that still being developed? It seems that the only file I will need to update is the autoexec.bin file as it changes and continues to be developed ... is that correct?
Thanks for your efforts and I've always enjoyed following the development of ML!
yes, just drag and drop autoexec file as they are released.
not sure what the process is when Canon releases new firmware.
and also, currently unstable is a very nice way of putting it.
ML Audio menu
Things that do not work for me:
- Beep, test tones: everything is ok except red light keep on a while
- Sound recorder: recording is OK but playback crashes with this error in log file:
ASSERT: FALSE at ./ASIF/ASIF.c:444, task beep_tasklv:1
- Voice Tags: crash the camera when recording the tag with this error in log file:
ASSERT: FALSE at ./ASIF/ASIF.c:444, task beep_tasklv:0
- Headphone monitoring: already talked before, no sound yet
- Audio meters: Works just fine !
Thanks 1% and a1ex for the fast response! Just asking, are you working on that 1%? Otherwise don't worry, maybe I'm going to fix this on my own and let you know what I found out.
Again speaking about intervalometer / time lapse: How do you see the chances to implement a feature that allows capturing a time lapse sequence series without flipping the mirror for each picture? Similar to LV, just without enabling the screen (for battery reasons obviously). I think this could be useful because it goes easy on the fragile parts of the camera. And one major drawback of serious time lapse photography is that it needs thousands of shutter releases which drops the value of the camera significantly :/
Thanks and regards!
Johannes
ML: SDCard format issue
Last time i tried with a 5D Mark II, when formating the SDCard, a ML process was backuping ML from the card and restoring it just after.
On the 6D, 2 messages and a kind of beep:
Restart your camera
Shoot_malloc err
You can format the card but ML is gone
ML: Flickering ML menus
I can confirm the 8 seconds ML menus flickering occurs only when LV is on. Either in photo or video.
- When you start the camera and directly enter ML menus with DEL button, no flickering at all.
- Even later, after a few shots, flickering occurs only in LV photo/video modes.
- when in LV, you scroll in ML menus, it doesn't flicker every 8 seconds
You stop scrolling, 8s flickering restart.
A timer issue somewhere ?
QuoteYou stop scrolling, 8s flickering restart.
A1ex's fix is just restarting the canon dialog so you have scroll wheels.
QuoteML: SDCard format issue.
I haven't even tried formatting from within camera. Worth checking out. I don't think I've ever used this on any camera.
QuoteAgain speaking about intervalometer / time lapse: How do you see the chances to implement a feature that allows capturing a time lapse sequence series without flipping the mirror for each picture?
Use silent pics. The regular ones work. The high res I just got lined up last night. Have to fix the menus up.
QuoteBeep, test tones: everything is ok except red light keep on a whil
Asif needs to be properly stopped. For beeps I just applied a patch, for recording its not possible. A good solution has to be found.
Just to be clear, i'm not complaining about issues or ways ML does something or somethingelse,
just testing and reporting weird stuff or bugs. Is this OK ?
I'm just so glad ML already work an Canon 6D !!
Its good to find the bugs. I probably would have never thought to format my card in camera.
Quote from: 1% on February 19, 2013, 03:33:04 PM
Use silent pics. The regular ones work. The high res I just got lined up last night. Have to fix the menus up.
Ah, nice feature, I should have tried this ^^ Anyway, is there a possibility to disable LV monitor but just keep the shutter open? The current mode reduces the shutter count indeed, but eats up the battery about 5 times faster than otherwise (according to Canon). And as the camera is usually left as is during a time lapse sequence, there is no necessity of the LV at all. Again, I'm just asking, besides that I'm perfectly happy with ML on the 6D (besides the bulb-exposure issue i mentioned earlier) :) However I think this feature could be useful for TL photographers that want to save shutter counts.
Regards!
EDIT: I looked up some DSLR life expectancies regarding the shutter count [1] and came to the conclusion that saving shutter counts is maybe not that essential as I thought :)
[1] http://www.olegkikin.com/shutterlife/
One suggestion
In menu Expo / White balance, at the beginning, it's on AUTO,
then you can scroll from 1500K to 15000K but you can't reset it to AUTO.
Would it be possible after 15000K and before 1500K to have the AUTO choice ?
Like in ISO choice.
ML does not remove Canon menus ;)
Quote from: teo770 on February 19, 2013, 02:22:40 PM
ML: SDCard format issue
Last time i tried with a 5D Mark II, when formating the SDCard, a ML process was backuping ML from the card and restoring it just after.
On the 6D, 2 messages and a kind of beep:
Restart your camera
Shoot_malloc err
You can format the card but ML is gone
This sounds right to me, ML is quite few files on the card, formatting the card would eliminate all files from the card, and since the camera doesn't have a place to stash the files during the format, the newly formatted card won't have the ML files on it any longer.
Quote from: jgruen on February 19, 2013, 05:20:04 PM
I looked up some DSLR life expectancies regarding the shutter count [1] and came to the conclusion that saving shutter counts is maybe not that essential as I thought :)
[1] http://www.olegkikin.com/shutterlife/
well, if a single time-lapse sequence uses 1K shutter activations, then a 5D is only good for about 100-300 such sequences, that seems like a rather short lifetime, so if there is a way to avoid exercising the parts, it seems like a good thing.
Unless you use an older CCD sensor DSLR, you are stuck with a physical shutter. Shutters are replaceable by Canon services. From what I have read, it is not very expensive.
how do they do video recording? I'm sure they don't do 30 shutter clicks/sec, that would hit the 100K shutter activations in only 55 minutes of video
Shutter opens, camera records movie, shutter closes.
Quote from: DTSET123 on February 20, 2013, 11:55:59 AM
Shutter opens, camera records movie, shutter closes.
so we should (in theory) be able to do the same thing for time-lapse sequences, right?
@dlang: i think what you need is fps override, with a low framerate (like 2fps or less).
Quote from: screamer on February 21, 2013, 12:42:09 AM
@dlang: i think what you need is fps override, with a low framerate (like 2fps or less).
Indeed, that's my point :-) frame rate would be very low though. As far as I know, fps override is already working on the 6D, so basically everything should be there already. Merging it with bulb ramping and disabling resources that go into the unnecessary LV could be a considerable task though. However the result would be a unique shutter-relaxing time lapse mode none of regular intervalometers/brampers can ever realize. Lets see what 1% thinks about. He seems quite busy :-)
You can use FPS override and shut the screen off... the powersave works. Set a shortcut key and and hit it. Can also do silent pics and intervalometer but not sure what will do 2fps better, will have to check. Also mind that low fps movie speed + underexposure gives vertical lines of noise when you zoom in on it, our unique defect because of the missing timerB control.
I've always used FPS or silent pic and never hit the shutter, that's too many actuations for me. Used auto iso or exposure to compensate instead of bulb ramping. Results were pretty good but clickety click gives you 5k resolution. Maybe the middle ground is high-res silent pics when those get 100% fixed. Yea, work has kinda interrupted what I was working on :(
Did some testing tonight and was able to repeatedly hard lock the camera.
Did a remote shoot test using the 6D remote app.
Hit the Zoom button on the camera.
Hard lock.
Also, I *think* zooming using the app was causing the same issue.
Additional detail, I was using the ML extended bracketing functionality.
It seems to be extra twitchy if using WiFi. I got another lockup while taking a long sequence of HDR shots while trying to pull files via ShutterSnitch.
Edit:
Oh. I do have magic zoom enabled as well, as well as focus highlighting in live view.
My wifi just hard locks after a few mins, dunno if its my phone or the camera. ML shouldn't alter that functionality but it still has to be explored further to see.
1% what's next?
A1ex's fix maybe solved the card format problem? I ported the afma stuff. Still trying to fix the big silent pics.
Maybe should figure out the af patterns.
Quote from: 1% on February 23, 2013, 07:33:39 AM
A1ex's fix maybe solved the card format problem? I ported the afma stuff. Still trying to fix the big silent pics.
I have a basis question ... I've been downloading the autoexec.bin file from you compile it. What do I download to benefit from A1ex's fix (maybe) for the format problem?
Thanks
Lens info is fixed, don't have rotation and all that jazz but its wrong for 600D too, first value doesn't move. Focus distance and lenght work so the zoom ring does its thing for zoom.
I investigated af patterns and I don't think they can work this way. When I xor top/middle/bottom and put that in for the af point it acts like you set it to auto. I think the only way we will have patterns is from 5d3 properties. Don't know how that works yet or the values.
Quote from: 1% on February 24, 2013, 06:07:29 AM
I investigated af patterns and I don't think they can work this way. When I xor top/middle/bottom and put that in for the af point it acts like you set it to auto. I think the only way we will have patterns is from 5d3 properties. Don't know how that works yet or the values.
Doh, maybe (conspiracy theory) Canon disabled the current ml approach for a reason? The af patterns at least would change the 6d af system from the intended 100% idiotic to only 90% outdated, I often use the patterns on my 60d so I hope you'll find a solution for the 6d :-o
There might be code for patterns somewhere just its not easy to find as the UI parts are gone. Same as the afma problem for 60D/600D. Trying 5d3 props may work like it worked for 50D AFMA. I use them a lot too, those end points like to catch and screw up what you're really focusing on.
Posted a new build so you can enjoy focus ring zoom and afma while I work out the silent pic stuff. Feels like I'm trying to fit a square peg in a round hole
Quote from: 1% on February 24, 2013, 07:04:30 PM
There might be code for patterns somewhere just its not easy to find as the UI parts are gone. Same as the afma problem for 60D/600D. Trying 5d3 props may work like it worked for 50D AFMA. I use them a lot too, those end points like to catch and screw up what you're really focusing on.
Posted a new build so you can enjoy focus ring zoom and afma while I work out the silent pic stuff. Feels like I'm trying to fit a square peg in a round hole
I used the 5d2 cfn.c code with the 5d3 property number, it kind of works. I calibrated 3 of my lenses last night, but when I tried to do my fourth one but now it won't actually confirm focus at all (don't beep), and reports 0. The menu setting for microadjust just reports "(err)".
Property is from 5d2, offsets are unique to 6D. 5d3 prop is dead, doesn't work here even though its set "correctly".
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/8c48801169b93aa1f26267a0f706a47357e6d2d6/platform/6D.112/cfn.c?at=unified
AF pattern properties from 5d3 will probably have more success... I hope.
http://www.youtube.com/watch?v=VlRvtsbVMr4
Made a little video, youtube cmpressed it of course, but all in all, very impressive. Used 24p set bit rate to 100. For some reason that's the only time it works otherwise I have to go to canon defaults.
I used marvels advanced, btw this is in fact better then technicolor cinestyle as I have looked closely and noticed clipping in the shadows on the cinestyle (spot meter never goes below 3% even in pitch black) but I have an older version of the technicolor.
This is strait out of the camera.
Probably need to download the h.264 config files and put them on the card. Get the rate control from a few posts back.
Wow, everything is fixed, thank you 1%! This is excellent.
Vertical lines at fps = 2.5 but rolling shutter greatly reduced.
Should be perfect in time for the summer. I can't wait to put it to good use. Donations in the future (I'm struggling to pay heating bill at the moment, February has been ridiculous).
I still dont know how to donate! There used to be a "donate" button but now i dont see it.
Quote from: DTSET123 on February 25, 2013, 01:31:33 AM
I still dont know how to donate! There used to be a "donate" button but now i dont see it.
[10:47] <yoyoyo> where has the donate button gone?
[10:48] <yoyoyo> there is none on the hp
[10:56] <SDX> we don't need money at the moment
Well.. good and bad:
It does encode jpegs when tethered:
### REMOTE - TVAF MF - ###
[LVDV] deliverProcessJPEG: 0x40c47a58
vramPostJob: Encode JPEG: 0x2
vrmProcessJob[0xa0d48]
[LVDV] ssdevProcessJob[0xa0db8][0]
[LVDV] ssdevProcessPath:0x0(0x0)[0x0]
[LVDV] deliverProcessJPEG: 0x40c33a3c
but for some reason after like 30s I get error 80 and eos utility + camera freezes. I've been trying to catch what is going on but it seems impossible to log it. Without a card in it doesn't seem to freeze.
Some progress: When I open the canon menu, image in EOS utility freezes. When ML is running dialogs are opened all the time in the background. I'd have to disable this and see if its causing the freezes.
QuoteIt does encode jpegs when tethered
Sorry, I don't understand: encode jpegs into movie?
It makes jpeg frames for the preview. If you were to record those and put them together you'd have a movie but I'm kinda stuck as it freezes on tether or wifi. Have to figure that part out. Must only be my camera though, other people using wifi and tether without issue.
QuoteIt makes jpeg frames for the preview. If you were to record those and put them together you'd have a movie
it records all 24fps?
It looks to be smoother than it was on 600D. I can't keep it from crashing long enough to analyze. I don't know if they're 1024x768 jpegs or what. I have to either fix my error 80 or someone with a camera who can stay tethered has to look.
Iphone:
it freezes frequently and still says that can't record when wifi is enabled. I was not able to record anything.
PC:
have a hard time connecting to eos utility. I go through connection process successfully but all the features are greyed out in eos ustility
Maybe need a newer eos utility? Also found wifi turns off usb too.
u right! testing right now
Nope, can't record :( it freezes
Does it freeze by itself too? Does it freeze with card out? If you leave it frozen for a minute it should turn into error 80.
when its in movie mode and i switch it to lv in eos utility sometimes it freezes before i press record, sometimes after. I have not seen err 80. When it does not freeze right away, i can see it as it is recording but does not last too long - no record of those few seconds either :(
LV in eos utility (movie mode) does not look like 24fps, more like 15 (unless i'm doing something wrong).
If i take out card it says "card required to record movie"
You don't have to record at the same time. Just need the remote LV to work and then frames can be saved from it. It goes a little faster than it updates on the screen. But dunno if its 15fps or 20 fps or what since I can't get it to not freeze.
On 600D the jpegs are 1056x704, on 6D size is unknown. I can try to dump the ram while its connected and see if it finishes before it freezes. Ideally though would be to figure out how to start the jpeg function and have it not send jpegs then feed it a custom sized buffer.
So, I'm trying to figure out if I'm using it wrong, if something has changed, or there's a bug. :)
I use LV for focusing with my Rokinon 35mm, and use the focus peaking overlay. On the T3i, once it is switched on, it is always there. With the 6D port, I only see it if I hit the LV button while in the ML menu. When I do that, it works, but flickers a lot between the menu and the LV.
What is the proper order of operations I should be using to make this work reliably? (I am on the Feb 16 build currently)
Thanks!
Upgrade to the latest, that fixed focus distance and focal length.
autoexec.bin.DebugCleanup 452.8 KB 2013-02-25
Which focus peaking? Blinking dots? It should work in movie and photo live view. In play mode you have to hit light to get it to show up. I've been using alpha blend though and like it much better despite the slowdown.
Blinking dots doesn't place a lot of points now, used to be all over the place.
Also feb16 builds were in the middle of taking out kill flicker so maybe that has something to do with hiding peaking, I always used the re-directed buffer and probably didn't notice.
Hi, I just baught the 6D+24/105 lens online, can't wait it get it, I'll be donating for ML dev and I'll install the alpha/beta ML on it, I'll report bugs too.
I have ML on my old T2i, and I can't use it without ML, so I'll be doing the same with the 6D.
I'm just wondering if you have an idea of how long it will take you guys to have the 1st official release of ML for 6D out ? is there a page where you annonce it ? will it be in weeks ? months ? days...? :D
In the actual version, are those features working ?
-peaking (I read it flickers)
-magic zoom
-zebra
-HDR video
-white balance Auto adjust Kelvin
-movie restart
-Bit Rate (I read it's hardest to understand, it's not as simple as on my t2i with just the CBR factor ?)
I'll get the sandisk extreme 95mb too, it's the best card out there isn't it ?
In the actual version, are those features working ?
-peaking (I read it flickers) - It flickered for one guy, doesn't flicker for me. Blinking dots is supposed to blink.
-magic zoom - Works, had problems going back and forth while we were killing canon dialogs for 2 versions.
-zebra - Never had a problem.
-HDR video - Extended with shutter + iso is broken by new menus on all cameras. Regular works fine.
-white balance Auto adjust Kelvin - That worked from the start
-movie restart - Works but no limit killing yet, needs another go I guess on that.
-Bit Rate (I read it's hardest to understand, it's not as simple as on my t2i with just the CBR factor ?) - Its not hard to understand. Pick a config and load it is all you have to do in theory. Old way doesn't apply to this camera or 5d3.
I'll get the sandisk extreme 95mb too, it's the best card out there isn't it ?
50Mb/s write is the best UHS card we can use. No 208MHZ, only 95mhz. 95Mb/s uses the first one so save your money.
Need more testing under diverse conditions to be bug free and throw it on the website. Still need audio stuff and a few things fixed here or there as they come up. Probably a couple of flex info things need to be aligned too + high res silent pics.
Thank you for your answer, that is good news for all the stuff already working! Now I'll just wait for my new toy to arrive!
-Bit Rate (I read it's hardest to understand, it's not as simple as on my t2i with just the CBR factor ?) - Its not hard to understand. Pick a config and load it is all you have to do in theory. Old way doesn't apply to this camera or 5d3.
I bought a 64gb uhs1 card @ 35mb per second, I haven't had issues with it getting bit rate to 12 (120mb/s) and initial qp to 1 aside from a very occasional auto stop (once every 30 minutes or so of recording) For high importance footage just turn it down to 80 initial qp to 2. For the first install you must use a small card (16gb worked for me) then just copypasta the ml folder and .bin file to your 64gig or 128gig, format with eos card and you're good.
This release is as stable as the official release for my 600d. Haven't had any battery locks since I updated to the most recent .bin (thank you very much 1%)
Quote from: fotojohni on February 28, 2013, 08:21:32 PM
This release is as stable as the official release for my 600d. Haven't had any battery locks since I updated to the most recent .bin (thank you very much 1%)
what are your video settings set to? because I still have issues.
Are you guys saying the 95mb sandisk is useless with the 6D? How its possible to record a120mbps video on a 35mb card!!??
Quote from: ManixLiquid on February 28, 2013, 11:17:58 PM
Are you guys saying the 95mb sandisk is useless with the 6D? How its possible to record a120mbps video on a 35mb card!!??
I have to question this as well. At the same time, I have had issue after issue with a extreme pro, and have questioned if it may be the root of some of my issues.
Bits vs bytes.
From what sparedog found, the 208mhz cards perform poorly at 95mhz. On digic IV the UHS cards still worked well at non UHS speeds. Not the case anymore, seem optimized for highest speed and nothing else.
I looked at bunch of cards and non of the manufactures specify mhz. How can I make sure that my next card is 95mhz? Is that what UHS stands for 208mhz?
You want UHS 50 not UHS ~100. So basically anything that only does around 50 write.. means no 90MB/s cards. Go for SDR50, DDR50 but no UHS-104.
https://www.sdcard.org/developers/overview/bus_speed/
Need to find out what chip is doing the card writing like I did on digic IV. Then we can see if 208mhz can be hacked in but not too likely.
Quote from: 1% on February 28, 2013, 04:28:35 PM
In the actual version, are those features working ?
-peaking (I read it flickers) - It flickered for one guy, doesn't flicker for me. Blinking dots is supposed to blink.
-magic zoom - Works, had problems going back and forth while we were killing canon dialogs for 2 versions.
-zebra - Never had a problem.
-HDR video - Extended with shutter + iso is broken by new menus on all cameras. Regular works fine.
Last time I checked (I don't have my T3i handy, it's with a friend right now), focus peaking with blinky dots worked.
The thing is, it DOES work for me, but not in a normal way.
Live view ML menus *only* show up if I am in the ML menu and hit the Live View button. (And then it is glitchy, jumping between the menu and live view periodically)
On the T3i, If I boot the camera and go into LV, the focus peaking still shows up if I had it enabled last time I turned on the camera. Edit: To clarify, the ML LV overlays in general only show up if I used the Erase button to bring up the configuration menu, and then hit LV from there. If I hit LV from normal shooting mode, ML is not enabled.
Global draw is on for all modes? It should be showing up.
I dunno if its set to on by default.
QuoteYou want UHS 50 not UHS ~100. So basically anything that only does around 50 write.. means no 90MB/s cards. Go for SDR50, DDR50 but no UHS-104.
I suppose the next best thing would be one of these cards: http://www.bhphotovideo.com/c/product/839982-REG/SanDisk_SDSDRX3_064G_A21_64GB_SDXC_Memory_Card.html
can someone (who has one of these 45BM/s cards) run this through benchmarks and report.
That will work, so will patriot EP (20 bux cheaper), pny pro elite is UHS-50 as well... I was going to get the 128gb card.
BTW, fixed cache hack boot, we gain a little bit of memory and its a better way to start up.
QuoteBTW, fixed cache hack boot, we gain a little bit of memory and its a better way to start up
Sweet..!
1%: Yup, global is turned on for all modes.
If you have a complete filesystem tree w/configs you want me to drop on and see if there's an issue with my install, I can give that a shot.
Ok: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/My-ML-Folder-6D.zip
This is what's on the non-uhs test card right now. Exactly as I finished up with it last night minus my pics and some log files.
I can't reproduce menus not showing up unless I turn global draw to play mode only.
Thanks, I'm going to have to dig in on this more later, because I'm still not seeing menus with your settings.
This is a UHS card. Does that make a difference?
Not really, might want to not override the bit rate down.
Try hitting info... are any canon dialogs on the screen?
If I toggle through the various info modes, all the canon menus show as usual, and one blank screen, where I presume ML should appear.
Do I need to (ergh...) reset the camera settings to default and try that?
Quote from: Warren on March 01, 2013, 06:28:34 PM
If I toggle through the various info modes, all the canon menus show as usual, and one blank screen, where I presume ML should appear.
Do I need to (ergh...) reset the camera settings to default and try that?
You are in liveview correct? The blank screen as in the liveview display with no overlays, or blank as in turned off?
Sorry, yes. Liveview with no overlays.
Weird because nobody else has had this problem, if you're using the same bin as me then I'm confused.
Perhaps your firmware version.
On my 6D, I had to apply again the original Canon firmware 1.1.2 before ML can work....
(i was already in 1.1.2, from factory)
Hope that helps
Hm. Interesting. Let me give that a go. I am also running 1.1.2 from the factory.
Thanks!
Edit: Unfortunately, no, that wasn't it.
Warren: when Canon overlays are disabled, do you get any warning messages in ML menu at the bottom?
1%: try creating a test bin that prints the value of zebra_should_run() => this should return 1. If it doesn't, see which component returns zero. There are lots of them, if you break down those functions, but here are some likely candidates:
- DISPLAY_IS_ON
- LiveViewShutterApp_handler (maybe sometimes there's other app at the top of the dialog stack?)
- lv_disp_mode (has problems on M)
To make sure I'm not making an ID10T error, when you say "Canon overlays are disabled" do you mean by way of using Info to switch them on/off, or is there a menu setting to completely disable them that I missed?
(But no, no warnings that I have seen as currently configured)
Quote from: gravitatemediagroup on February 28, 2013, 09:39:49 PM
what are your video settings set to? because I still have issues.
I set it to all-I 24 fps, it does seems to be a bit more finicky when set to IPB. I have no idea why this is.
Quote from: ManixLiquid on February 28, 2013, 11:17:58 PM
Are you guys saying the 95mb sandisk is useless with the 6D? How its possible to record a120mbps video on a 35mb card!!??
because 35 MB is 8 times more than 35 Mb, sorry for the megabyte, megabit thing.
Here is asif improperly stopping:
[ASIF] StopASIFDMADAC : EV_STOP_DMA_DAC (time out)
[ASIF] StopASIFDMADAC Err END
[ASIF] asifEventDispatch : (ST=1, EV=0, P=0x101)
[ASIF] asifAStopDmaDac
[ASIF] asifEventDispatch : (ST=0, EV=2, P=0xd09358)
[ASIF] asifAFuncIgnore : Give FuncSync
[ASIF] asifEventDispatch : (ST=0, EV=2, P=0xd09358)
[ASIF] StopASIFDMADAC END
For the overlays they are drawing in every mode I went through them, zebras, peaking histogram, whatever, appear to be working properly. Bulb mode photo LV isn't working today, looking to see if cache hack or left wifi on or some other reason.
This is the error(s) I get
ASSERT: 0
at ./LvCommon/LvSaturateController.c:130, task Evf
lv:1 mode:4
Magic Lantern version : v2.3.NEXT.2013Mar01.6D112
Mercurial changeset : 4e7d166f0bfe+ (unified) tip
Built on 2013-03-02 04:43:50 by user@D610.
Free Memory : 450K + 1979K
ASSERT: ControlIso <= LVGAIN_MAX_ISO
at ./LvCommon/LvGainController.c:837, task Evf
lv:1 mode:4
Magic Lantern version : v2.3.NEXT.2013Mar01.6D112
Mercurial changeset : 4e7d166f0bfe+ (unified) tip
Built on 2013-03-02 04:43:50 by user@D610.
Free Memory : 450K + 3004K
Ok, this is from expo sim being on + expo override being auto.
Turns into error 80 so might be related to tethering, phone app still froze but seemed to last longer. Problem on 5d3 too?
Aha! Your last comment was the key. Wifi was on. As soon as I turned that off, menus came back.
Somehow through the course of reading the entire thread I must have missed that detail.
Thank you!
So, now that I've got it working... :)
Seeing something I don't remember from the T3i build.
In focus peaking, there are marching ants at the top and bottom of the screen, as if it is doing detection on the screen edges. Also, the framerate seems much lower than I recall. Could these things be related?
Edit: I realized I'm using your preset with alpha blending instead of blinking dots. Don't know if the question is still relevant since the description notes that it lags. :P
Alpha blending introduces a little bit of lag since it redirects the buffer. Blinking dots is the only real-time one. Personally I like it and don't mind the choppiness but some people will probably prefer the other one. Sharpness is an interesting one too.
*will have to see what stops the drawing with wifi. I just looked and it clears everything. will be useful once I figure out the web service stuff. shoot to ftp instead of shoot to card would be nice.
What about this card
http://www.bhphotovideo.com/c/product/876410-REG/Transcend_ts32gsdhc10u1_32GB_SDHC_Memory_Card.html
How many mhz is it?
Hi all. I have a 6D, I have read this thread mostly and I have the will to support the port for this model. What should I do now?
Quote from: Hb on March 02, 2013, 06:39:56 PM
Hi all. I have a 6D, I have read this thread mostly and I have the will to support the port for this model. What should I do now?
I am not sure, and let somebody confirm this before you start, but you could download the developer version, run it on your 6D and use it, then report errors when you've found any..!
That card should work. Don't know what it benches at, read speed of 90 is suspect tho, might be using 208mhz. Not all cards will under-perform at 95mhz just the sandisk "pro" card was tested. Don't pay $200+ for something that a $40 card will do as well or better.
All you guys have to do is use it and enjoy it :) Install process is pretty simple if you've used ML before.
Ha! I just noticed that I don't know where to download it from? It's not on the nightly build page...
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Its probably buried in the middle of this giant thread now.
Thanks. Maybe tell coutts to put the link into the first message of the thread.
Ok, about menus with wifi on...
zebra_should_run returns 0... removing liveview_display_idle() brings back the overlays but still returns 0. get_global_draw is the culprit on that.
Also HD buffer is 1816x1210 in photo mode... maybe the resizing is different and its possible to feed this to the encoder?
Wifi drawing fixed. Added wifi app handler... it confirms wifi is off before letting you start movie mode.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/aea6fd454956355802673d3231f01d306b64a4cf
Great news, thanks for hunting that down.
I'll give the next build a shot when posted.
I've got a rather significant photo/camping trip next week, so I need to get some time to test for stability before I head off the grid :)
Quote from: fotojohni on March 02, 2013, 04:17:41 AM
because 35 MB is 8 times more than 35 Mb, sorry for the megabyte, megabit thing.
So If I aim for 90 MB per sec video, I should set ML to what? 1800 Mb? 11.25 Mb? Is it even possible to reach 90MB? I'm lost.
Its set in megabits. You can't do 90 megabytes. If we could we'd just save uncompressed and call it a day.
Quote from: 1% on March 02, 2013, 07:19:51 PM
All you guys have to do is use it and enjoy it :) Install process is pretty simple if you've used ML before.
Hey 1%
I don't expect you to explain to me the actual instructions on how to do this as you clearly have enough on but I'm also willing to help test for you :) Gonna be totally honest here, I haven't got a damn clue about programming, coding, developing mind but I have a 6D I'm willing to test on and will report back any bugs I find.
If somebody could just point me in the right direction of what I need to get started (possibly explained in English or even English/Caveman) then that would be super bad!
If this is asking too much then I totally dig it. It must be exhausting having n00bs like me asking the same questions all the time so please feel free to just disregard this if my etiquette is out of turn. That said I'm completely blown away by how patient and understanding this community is. I think it's too easy for people to get on their elitist high horses when they are sat behind their keyboards at home but it's something you really don't see on here! The world needs more of this so a huge shout out to all involved :)
Being as I can't technically contribute (horrific Attention Deficit takes care of that!) I'll most definitely be donating what I can to the cause and I seriously do use my camera A LOT so at least it'll be put through it's paces a bit!
Thanks again! Cheers :)
Read the install guide + this thread. There is a zip up now so all in one place I guess.
Quote from: 1% on March 03, 2013, 04:55:23 AM
Read the install guide + this thread. There is a zip up now so all in one place I guess.
Amazing, thanks dude!
Sorry but one last question - where might I find this zip? Sounds like a crappy excuse but bad attention problems + 30 pages of thread I struggle to understand is really quite difficult :P
Thanks again man and the best of luck to you!
Download link is on the previous page for zip/bins/etc.
Thank you so much man and cheers for being cool about it :) Take care!
Quote from: teo770 on February 16, 2013, 10:09:52 AM
I finaly success in instaling ML on Canon 6D, thanks all !
For other newbies like me, steps are:
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
- Get 6d-112.fir from:
http://bit.ly/ZgvGUf
- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini
- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card
- Put SD card in camera and update firmware while in M mode. Restart. That's it.
This is for anyone else as dumb as me! Props to the original poster! All working! Thanks guys.
Oh and in addition to this - 1% has handily put the ini's plus autoexec all in a tasty bite-sized zip folder which you'll find here: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads :)
Quote from: 1% on March 03, 2013, 03:50:06 AM
Its set in megabits. You can't do 90 megabytes. If we could we'd just save uncompressed and call it a day.
So what the max megabits we can set?
Quote from: teo770 on February 16, 2013, 10:09:52 AM
I finally succeeded in installing ML on Canon 6D, ... For other newbies like me, steps are: ...
@teo770
Which firmware version had your 6D before installing ML?
Is there a minimum firmware version as read elsewhere in this thread?
There is no real "max" and the setting is a target so its not 1:1. I've used 110megabits and 90megabits. Highest rate achieved so far has been around 200 just like the digic IV cameras... me thinks it doesn't all fit in the buffer... on ALL-I the frames are doubled so I think it legitimately has trouble. I'm digging around trying to crib the flush rate adjustment from 5d3 and maybe gop too.
Hb: i had factory firmware 1.1.2 but ML firmware update didn't work #1st time so i had to update firmware again with Canon's 1.1.2, then ML firmware did update.
Did a simple decompile of 5d3:
Flush Rate/Gop are in an area full of garbage strings.. then again I only have the update bin and not a real camera dump.
Everything is weirdified so its hard to tell what is what without some function names like from an .idc... Will have to do stronger analysis to find....
For af patterns:
PROP_AF_SELECT_FOCUS_AREA(%d)'
PROP_AF_METHOD_SELECT_FOCUS_AREA(%d)
These are probably what is necessary to make the patterns work.
We don't have:
'GetSelectPositionAfPoint SELECT_FOCUS_AREA_WIDE(%#x)' F8BEDBA8
'GetSelectPositionAfPoint SELECT_FOCUS_AREA_EXT(%#x)' F83CFA54, F8BEDC44
'GetSelectPositionAfPoint SELECT_FOCUS_AREA_SPOT(%#x)' F8BEDD1C
'GetSelectPositionAfPoint SELECT_FOCUS_AREA_EXT_AROUND(%#x
But those all seem to be from gui dialogs so I guess no changing it with the canon menu. Now just need to find the prop numbers and values for 5d3 and compare.
Just noticed the black level adjustment gets worked into the videos. Most noticeable at -100 and + 100. Seems to give some extra lift. Needs to be tested.
has their been a clear answer or not regarding extreme pro SD cards causing issues?
Performance would be lower, it wouldn't make your camera crash. Pebkac
yeah, i'm about to test a 45mbs card without ML and see if it helps.
my 6D is slowly becoming the worst investment of a camera I've ever made.
I have a wedding coming up this Saturday that I would like to use it as a B/C cam
but I just don't think I can trust it.
Am I supposed to have 2 versions of Autoexec on the card?
1 of them is the latest with a .bin
the other is an older (possibly original) that doesn't have a .bin
without "the original" the camera won't turn on.
yep, I'm over it.
anybody wanna buy a 6D?
first couple weeks of having it I got great low light performance. post ML has been garbage.
it will only load autoexec.bin you can have as many of whatever on the card.
ml isn't changing the hd buffer or iso performance so it is what it is.
Quoteyeah, i'm about to test a 45mbs card without ML and see if it helps.
Can you please run it through ML benchmarks and post results
Thanks!
I've been using slow non-uhs card since the 6D ep card fell apart and it still records video... I mean it stops more often but not a disaster or anything. When I finally send it in for rma (have to put the 50gb of stuff somewhere), I'm sure it will pick higher qps and have nicer video again but not like it will get more stable or tell you how to pick correct settings ;)
then I guess I got a bad camera
Quote from: gravitatemediagroup on March 05, 2013, 06:12:25 AM
then I guess I got a bad camera
I just baught a 6D I'm still waiting for it to arrive, even though I didn't receive it yet I'm glad to get my 1st full frame camera, I got it mainly because of great low light performance, and because I knew I could install ML.
I read that you are not happy with it, and I'd like to understand why ? (I hope everybody is not feeling like you...)
Quote from: 1% on March 05, 2013, 12:37:35 AM
I've been using slow non-uhs card since the 6D ep card fell apart and it still records video...
What do you mean "6D ep card fell apart and it still records video..." ? Sounds like your 6D broke but still works a little, it's scary...
Malex: I got the 6D after having a 5D Mark II and a Nikon D600. To summup, for this price tag, this is the best full frame camera available right now. D600 is great (focus points, mpixels, headphone jack...etc) but for the video, the 6D, as the 5D mark II&III support MagicLantern, let you change the aperture while recording (no Nikon cam allow this) and in my opinion features as moire/aliasing as the 5D Mark II, no more. 5D MarkIII is an alternative is you want to spend extra $1000.
Add to the 6D body features (low light perfs +++) the power of MagicLantern, you've got a realy great camera. Great for photos great for videos.
Only my opinion.
Hello,
I try the silent picture mode in ML and I get 422 file. So far so good :-).
My problem is, what ist the correct resolution from the yuv422 files. All programs that i have tried (yuv tools, 422toimage, xnview...and many more), dont' recognize the picture. The best result with wrong colors so far is 1816 x 1210.
Is there a solution for my problem?
thanks
I stepped out for a while and I come back to see the autoexec.bin.WifiOverlay
Are you working on getting video into the eos remote app via wifi? Excited =D
Earlier, in another thread, I wrote and received the reply:
Quote from: xcreativ on September 10, 2012, 01:40:46 AM
Is it possible to make a setting "Audio" in the section "Input Source", reversed L: int R: ext, so that a record was with L: ext (external) and R: int (internal)? Is it possible to implement a new version of the firmware? If not why? The fact that I have an external microphone, which provides mono sound on the right to the left channel.
Quote from: a1ex on September 10, 2012, 08:06:41 AM
On AK4646 cameras it's not possible, it's a hardware limitation.
Quote from: 1% on September 11, 2012, 05:51:27 AM
What about L to L external. R to internal? R could be broken or not exist.
Is it possible to implement this function in 6D or he, too hardware limitation?
Quote
What do you mean "6D ep card fell apart
64gb Patriot EP card I used on 600D then 6D fell apart from too many insertions. Have another for 600D but have to rma this one. Until then stuck with the crappy 32gb card.
QuoteIs there a solution for my problem?
Yes, an easy one. Get the gimp .422 plugin and manually set the size per image or use 422 to image and edit the xml file to have all of your sizes. We have likie 3 of them. Zoom size, photo size, movie size. High res pics aren't fixed yet so don't use those.
QuoteAre you working on getting video into the eos remote app via wifi? Excited =D
I've tried. Seems like encoder is cut off to communicate with the wifi IC. This is just fixing another guy's problem of leaving wifi on and trying to use ML menus. It might work to capture .422s or lv jpegs over wifi and make a movie that way. Don't know how fast the throughput really is yet.
Quotein my opinion features as moire/aliasing as the 5D Mark II, no more
I got way less moire on 600D but its not full frame. I bet digic IV resizing was worse on full frames. 6D is probably an improvement... I think still not enough. They really really should have kept the crop-mode.
QuoteIs it possible to implement this function in 6D or he, too hardware limitation?
Not sure yet... appears to be separate L/R audio at least in canon functions. IC is labeled AK4646 but registers appear different and using the IC over serial is not shown in the data-sheet. 650D does include serial in the datasheet and uses a similar IC. I got as far as trying to see breakdown pics to check if they lied on the IC label too. Did not find any.
First we need to have some control over this thing before we try separate channels and all the good stuff. I want to have headphone and canon free recording like 600D too. Still work in progress though. I got this camera like 2 months ago maybe.
Quote from: Malex on March 05, 2013, 10:50:42 AM
I just baught a 6D I'm still waiting for it to arrive, even though I didn't receive it yet I'm glad to get my 1st full frame camera, I got it mainly because of great low light performance, and because I knew I could install ML.
I read that you are not happy with it, and I'd like to understand why ? (I hope everybody is not feeling like you...)
when you get it, shoot in some low light with various ISO and see if you get some crazy vertical lines in your footage.
gravitatemediagroup: You're perhaps talking of "banding". I had this problem with one of my 5D MarkII. If you see banding in iso <or= 6400 you'd better return the camera. Banding in low light areas is a well known Canon issue. My 6D is not affected this time.
Be sure to use a genuine Canon battery whyle testing banding cause some chinese battery can cause weird stuff sometimes. (As banding is a kind of electronic waved noise)
it is vertical banding, is not is?
vertical banding is enhanced when the "priority of lights", and is typical of the lack of ALL Canon FF cameras. CROP on too, but less. I, too, was angry about this, here is my petition:
http://www.change.org/ru/петиции/firmware-correcting-the-defect-vertical-banding-canon-5d-mark-2-in-videorecord
I wrote about this in the Russian representative Canon, they was told that would deal with the issue, but that this effect is a design feature of the Canon cameras.
Once you talk about it, I suggest that the joint efforts to seek solutions to problems Canon vertical banding. Like I said - this is not an isolated incident, and not a single marriage - vertical banding appears on all 5d Mark 2 that I tested (5-6), many other owners have reported this problem. On 5d Mark 3, which I held in my hands also observed vertical banding. At 6d, at first glance, the vertical banding is less visible than 5d Mark 2.
Magic Lantern team may be able to do something about it.
I think the banding he has is the sensor timing banding. Turn fps override to 2fps and point at dark area. Zoom in and you see vertical color cuts in the image spaced at regular intervals.
I said to try fps override like 24/25/26, etc to see if it goes away at one point. There is probably a service mode adjustment for this and canon would be able to fix it. That or sensor is really busted.
Great work so far!
Quote from: gravitatemediagroup on March 05, 2013, 07:32:32 PM
when you get it, shoot in some low light with various ISO and see if you get some crazy vertical lines in your footage.
Malex, dont worry, your new camera will be awesome in low light, just as everyone else´s 6D is performing. My low light footage is stella
Yep, he is the only one with that problem. I can see if it was something ML changed but its not. Unless he has FPS override on the whole time.
Maybe try the whole zip as configured.... I dunno, I'd be altering the timing and see if it would go away if this happened to me. Barring that I'd sent to service or look into that service software that does the adjustments.
Quote from: gravitatemediagroup on March 05, 2013, 07:32:32 PM
when you get it, shoot in some low light with various ISO and see if you get some crazy vertical lines in your footage.
Ok I'll do that, without ML, and with ML.
Quote from: 1% on March 05, 2013, 04:56:59 PM
64gb Patriot EP card I used on 600D then 6D fell apart from too many insertions.
Ha Ok, I understand now, your Sdcard broke, not your 6D.
@teo770 and @sparedog : Yup, I checked many reviews before I finally decided to get one (not only reviews of 6D, I checked 5Dm3, Gh3, Blackmagic, Sony VG900 and A99) and 6D won my choice for different reasons, and you guys are confirming it's a great camera, so yeah I'm not worrying.
Its big flaw for me and many people is still no 1080@60p! It's a shame! But well, we can't have it all...
If I really need to do slowmotion, I'll get a GoPro 3 BlackEdition or rent a Fs700.
Quote from: Malex on March 06, 2013, 12:12:37 AM
Ha Ok, I understand now, your Sdcard broke, not your 6D.
Yeah, that was scary. Glad it's not the camera.
I've worked with the 5d mark ii and I can honestly say the low light performance makes it worth it. The 5d mark ii has this weird quality where the footage looks slightly fuzzy in low light if you don't nail the focus perfectly (something that's very difficult to do with open aperture in low light). It can be very annoying, the footage is still great, and the fuzziness is vaguely reminiscent of film, but the 6d doesn't suffer from this problem, at least until you start under exposing at 12800, and for that reason the footage looks much cleaner.
I don't know about event shooting, or documentaries, but for narrative film work sharpness issues and moire should be the last thing on anyone's mind with a full frame camera. I never really understood the issue. You buy a full frame to shoot open aperture and get that magic look, moire is an issue when your actor wears a weird shirt, not for your background, I mean the only time I am seeing moire is for footage that I would never use anyway and fortunately for narrative work you will likely have that choice. Just my humble opinion as a university film maker.
I'm still waiting on this notoriously bad New England winter to break. Then I will upload some nature. I have some night snowstorm video, the camera is indeed semi-weather proof as I had a good deal of water soaking on mine. The snow looks magical in the rays cast by various lights. Wouldn't have been possible to capture on my budget with any other camera. The $1000 savings over the mk iii was invested in quality film era glass. Pentax 50mm 1.4 (manually removed the aperture pin, declicked aperture, absolutely the nicest lens I have ever used in filmmaking and I've used some nice ziess 35s and 50s, nothing can touch the bokeh on this guy), nikon 35mm f2, tamron 105mm f2.5 pentax 135mm f2.5 and tamron 17-35mm f2.8-4, all for $800, I'll put the last $200 into quality sound recording (can't wait for the audio monitoring)... AND... magic lantern running at 120mb/s on a massively cheaper 64gb sd card instead of a stupid compact flash.
That compact flash would let us save uncompressed most likely. :(
I like that SD is cheaper but I want 4:2:2 color out of a $2k+ camera. I think they want to fsck all the fx people and shake em down for some higher end packages.
Look at moire on this vid: http://www.youtube.com/watch?v=zpNVUzXiZFY
Defect is one thing but the moire on the fences and grates kinda annoys me. Yes you can shoot around it but you'll never know what will start doing it until you start filming a scene... and then what you tell your whole team to move or buy that filter that jams up the mirror box?
IMO we need an update too to fix the resizing. I need to find a moire scene and check on HDMI since the resizing is different.
Do you think Canon will release the update gets rid of moire in the coming year? I think 6D selling well, and they have yet to release updated lack of motivation to get rid of moire. Even in spite of discontent videographers. Through which all "channels" users should refer to the Canon? Hard to believe that they meticulously study all forums.
I think they might release an update but I doubt they will tackle the moire. I don't know what market they're really aiming for here with a $2k camera with all of these consumerish features. That could have been better channelled into making it a real competitor in the broke ass pro segment actually buying it.
I don't think there is any way to convince them. They do look but don't seem to "get it". If they're aiming at photographers why leave out things like af patterns. Every camera has newer hardware features I don't know why they're so bent on software being limited. Every version should be a real reason to upgrade. UHS/FF/Faster proc.. that wasn't enough? We have to have headphone jack taken out and artificial limits?
Quote from: 1% on March 06, 2013, 04:57:49 PM
Look at moire on this vid: http://www.youtube.com/watch?v=zpNVUzXiZFY
Defect is one thing but the moire on the fences and grates kinda annoys me. Yes you can shoot around it but you'll never know what will start doing it until you start filming a scene... and then what you tell your whole team to move or buy that filter that jams up the mirror box?
yeah, I knew the 6D was pretty bad news when I seen moire IN DIRT!!! no BS....DIRT
oh, but don't worry, $400+ more for an adapter (that much closer to a MK3) and you can be moire free.
Quote from: gravitatemediagroup on March 06, 2013, 09:49:50 PM
yeah, I knew the 6D was pretty bad news when I seen moire IN DIRT!!! no BS....DIRT
oh, but don't worry, $400+ more for an adapter (that much closer to a MK3) and you can be moire free.
;D
but wait, what adapter?
http://www.mosaicengineering.com/products/vaf/6d.html
What language do you program arm processors in, I was digging around CHDK and it looks like ubasic? About the HDMI, basically, from a conceptual standpoint, the sensor is spitting raw data into the digic 5+, which is supposedly 17x faster than the digic 4, though seriously how is this possible?. And at this point there is probably a compression algorithm. The digic 5+ is programed to line skip in this camera, where as in the mk iii it is programed to do a 3x3 average or possibly some kind of Gaussian average from a much bigger pixel area and some sharpening algorithm. Then (maybe, I think) the processor compresses the color into h.264 according to the picture style. So, it is conceivable that fixing the moire is even tricker than getting uncompressed color.
It's unfortunate that HDMI doesn't come directly off of that first step for 5.5K video, that would be nice but unfortunately impossible with the current specification (v1.4, max 4K @ 24).
I'm hoping that the HDMI can come off in uncompressed color, that would be very, very cool. However, unless canon is waiting on the new HDMI 2.0 specs and somehow has some kind of magic built into their HDMI, I wouldn't expect too much in terms of uncompressed resolution.
Quote from: gravitatemediagroup on March 06, 2013, 09:49:50 PM
yeah, I knew the 6D was pretty bad news when I seen moire IN DIRT!!! no BS....DIRT
oh, but don't worry, $400+ more for an adapter (that much closer to a MK3) and you can be moire free.
Please note that the screen is not 1080, it's cropped to something close to 720x1280. Also, recording in 720 you will have ridiculous moire, I mean, in every sense of the word ridiculous. It looks like they are taking each pixel color from different lines, so that the color moire is absolutely absurd.
edit: also, the mosaic engineering solution is overpriced. It made sense in the days of the 5d mk ii domination, but now that the 5d mk iii is out it is just annoying. For $200 it makes sense.
I don't shoot 720 and I'm not talking about seeing it on the camera screen.
Quote from: gravitatemediagroup on March 06, 2013, 10:37:48 PM
I don't shoot 720 and I'm not talking about seeing it on the camera screen.
yeah I agree, its real bad. Mosaic is a very cool solution, I hope they adapt to the lower demand (from people shifting to the 5d mk iii) by lowering the price to $200
Most importantly, this filter - the mechanical implementation of the camera, which prevents its parts. First, it reduces exposure to some level. In their advertising on Vimeo, they refer to the non-permanent cloud of light conditions. However, why the clouds covering the sun is, when there is a filter test, and not without? Secondly, I think the filter to reduce the sharpness.
Quote from: xcreativ on March 06, 2013, 11:04:18 PM
Most importantly, this filter - the mechanical implementation of the camera, which prevents its parts. First, it reduces exposure to some level. In their advertising on Vimeo, they refer to the non-permanent cloud of light conditions. However, why the clouds covering the sun is, when there is a filter test, and not without? Secondly, I think the filter to reduce the sharpness.
Yes, I noticed it, too. The picture got darker with the filter. Didn't like the outcome anyway...
Quote from: xcreativ on March 06, 2013, 11:04:18 PM
Most importantly, this filter - the mechanical implementation of the camera, which prevents its parts. First, it reduces exposure to some level. In their advertising on Vimeo, they refer to the non-permanent cloud of light conditions. However, why the clouds covering the sun is, when there is a filter test, and not without? Secondly, I think the filter to reduce the sharpness.
I believe the filter slightly reduces sharpness, however, this reduction is only very small. I need to test the optical attenuation, I wouldn't worry about it though, the cameras low light capability is not a problem.
all in all it's a very good solution, albeit an over priced one.
QuoteSo, it is conceivable that fixing the moire is even tricker than getting uncompressed color.
Not really, just have to sample the sensor differently. They CAN do it... they did it for 600D. Basically a 4:2:2 YUV buffer is created by sampling sensor (skipping some lines) and interpolating. The buffer sizes come out different on each camera because of the math that goes into this and different sensor sizes/timings/etc.
The main problem is you can't fit that 5k image onto <2k sized buffer without skipping a lot of data. They only have a given # of lines they can read fast enough. Then this gets sent to the TI h264 encoder and color sub-sampled to 4:2:0.
Reading the whole thing you get the FPS you get shooting stills.
Without dual digic the best "res" you get is 2k.. that is the size of the zoom window.. we got raw dumps that were 2k as well. Problem is the encoder only takes fixed sizes... so after scaling the whole thing it gets scaled again to 1080P. Effects are applied somewhere in this line... probably onto the original 2k sized window it makes. All this is done to present the "1080p" fixed image to the consumer.. If they got some weird ass 4:3 resolutions in their videos they would be confused. Also the LV not being 100% coverage would be confusing as well.
Some folks want an imaging device, dummies want a packaged product that's ehhhch Deee. There is some wierd sizing stuff that goes with this camera as evidenced by the folding image in FPS override and movie/photo buffer differences of a few pixels. Wish canon would make a 6D pro firmware and leave us with un molested video.
As I figure more low level stuff out and get better I'm going to try to fix some of these shortcomings but its still a long road ahead and only a few people care. I did manage to blow up the photo buffer on 600D and get it to zoom while recording and all that fun so this stuff IS possible just very complicated.
And guess what... 1dc? From BH photo:
4K (4096 x 2160), Full HD (1920 x 1080)
so... still not fixed. They just let you play in the zoom window which btw.. that 2160 is one of its sizes, they just increased vertical resolution by increasing sampling speed (and putting a big ass heatsink). Maybe 1/2 the height is on 1 digic and the other half is on the other?
Sensors are almost the same size but different effective megapixels and orientation... so they cut it down to sample faster. Also probably why we have tall HD buffer, bigger than 1080p
CMOS, 35.8 x 23.9 mm 6D
CMOS, 24 x 36 mm 1DC
I care x3!
Am I missing something?
With the latest autoexec.bin-TodayCommits I'm still getting the flicker every 6 to 7 seconds when I use ML in LV?
It looked like that had been resolved under issues.
BTW ... GREAT JOB 1%!!!!
Quote from: rktaylor on March 07, 2013, 03:25:08 AM
Am I missing something?
With the latest autoexec.bin-TodayCommits I'm still getting the flicker every 6 to 7 seconds when I use ML in LV?
It looked like that had been resolved under issues.
BTW ... GREAT JOB 1%!!!!
I just got my 6D in today and this is my first time posting.
I've used Magic Lantern on the 550D and 600D for over a year now and love it.
I just made an account to report this same issue. The menu seems to flicker every 10 seconds or so? And it flickers to an overlay of a standard canon menu. Typically its so quick I cannot tell what menu it is.
also thank you for the development! I'd love to donate to keep your spirits high or just show my appreciation.
It is probably the picture style menu, as it is a little trick to allow the use of the scroll wheels.
Quote from: gravitatemediagroup on March 05, 2013, 07:32:32 PM
when you get it, shoot in some low light with various ISO and see if you get some crazy vertical lines in your footage.
I received my 6D yesterday, I don't have crazy vertical lines, without or with ML,
ML is working fine for me, except that one flicker now and then, and the waveforme set as small is smaller than on the 550D.
I didn't play much with bitrate yet.
I'm having a big issue though but not related to ML or the 6D, the 24-105mm Canon that I received with the 6D isn't working properly!
I get Err 01 from time to time, and if I try to turn OFF IS (stabilizer) I hear some noise inside the lens, like if something is stuck!
If the 6D is OFF and set on movie mode and IS is OFF , when I turn back ON the 6D it crash directly! Err 70! WHYYYYYYYY
it's my 1st L serie lens, and it's doesn't work well! :(
New lens, used lens?
The flicker is from the dialog opening in the background so you can use scroll wheels. This was a1ex's fix. Someone complained the wheels were timing out. Its like this on 5d3/m/650D i believe.
Quote from: 1% on March 07, 2013, 03:34:14 PM
New lens, used lens?
Brand new lens, it came as a kit lens with the 6D, I'll call the shop and see what they tell me.
I don't have any IS lenses to test but get similar error when an iffy lens I have loses contact with the body.
Post the log from the error 70 too. There should be an assert and/or log file.
Quote from: 1% on March 07, 2013, 03:34:14 PM
New lens, used lens?
The flicker is from the dialog opening in the background so you can use scroll wheels. This was a1ex's fix. Someone complained the wheels were timing out. Its like this on 5d3/m/650D i believe.
Are you says that if flickers based on the lens? I have four lenses of which I bought three new and one used. I will test it on each lens tonight.
So the solution for now is to delay the flicker is by turning the wheel before it flickers? When I do it still flickers after 7 seconds.
Quote from: 1% on March 07, 2013, 03:43:27 PM
Post the log from the error 70 too. There should be an assert and/or log file.
this is from error 01
https://dl.dropbox.com/u/2478549/LOG000.LOG
this error 70
https://dl.dropbox.com/u/2478549/CRASH00.LOG
do you understand that language...? is it ML related ?
The color calc (internal to canon fw) crashed. Make sure expo override is off but that's about all I can think of.
Quote from: 1% on March 06, 2013, 11:27:04 PM
Not really, just have to sample the sensor differently. They CAN do it... they did it for 600D. Basically a 4:2:2 YUV buffer is created by sampling sensor (skipping some lines) and interpolating. The buffer sizes come out different on each camera because of the math that goes into this and different sensor sizes/timings/etc.
So the problem is the buffer isn't large enough... That seems weird that they would spend all that money making a new digic processor and they wouldn't increase the buffer size/speed. Maybe it's just me but something must be going on here.
Edit: I own a 600d as well, are you saying the same moire fix exists in that camera? Arg... I never imagined this could be such a difficult problem, after all we are 5 years after the 5d mkii, you'd think technology would have caught up by now for 4k imaging to be a breeze.
Undoubtable they are not skipping lines in the 5d mkiii, so they must be able to processes the entire sensor at some point. Meaning the buffer is large enough for at least part of the data (maybe just luma channel perhaps) Is this possible, and if so it would technically be possible to create a sort of faux 4k with the 5k luma but 2k chroma.
Maybe this is complete bunk though, I don't really understand image compression that well. Though I am actively researching. I appreciate that you are one of the only ones who understands the internal coding structure of the camera. I am studying computer science, but this is not the sort of coding that I'm used to. Perhaps I can be to some assistance later on.
Additional Edit (19:41 utc): Wait, 4:2:2 already does this! never mind. So actually the color channels are considerably less resolution already. Okay, so maybe, all the 5d mkiii is doing is making an average before it even converts to YUV 4:2:2 color space. This makes considerable sense as to why the moire is completely ridiculous on 720, the chroma is only 360!
Additional Edit (20:00 utc) I am very interested in what the moire reduction is on the 5d mk iii on 720p mode. Is there someone who can look into this? Also, the fact that they went through all this trouble in 2008 to develop the 5d mkii video and they didn't think it would have an effect on the industry, not even enough to warrant 24p (24p clearly has some kind of magical power considering that magic lantern was originally developed to address
that [among other problems] problem)? Honestly, is the entire global imaging production controlled by some kind of hidden force or are they just completely out of touch with reality?
600D has a smaller sensor and crop mode so I've never noticed any moire... I can moire out 6D in a heartbeat.
We have 2 different sensor sizes here that have to be sampled with line skipping... even 1dC still skipping. 5d3 has a different sensor and a different resizing algo. Thats probably why they have less moire.
They can make the buffer as big as they want but have to fill it with image data at reasonable speed. The uncompressed we can record shows cuts because the card can't keep up. This is similar to the problem canon faces with these sensors. If they go too fast they get image aberrations... When we increase the timing and sample faster image falls over.
Add data transfer limitations on top. SD is slower than CF and even new CF is not fast enough.
Quoteso they must be able to processes the entire sensor at some point.
Yes, reading line by line when you take a photo.
5d3 sensor is 36 x 24 mm so similar orientation to ours. Weird that it and 1dc have even numbers while we do not. Odd #s of line skips could be doing this.. maybe it doesn't fit perfectly? I certainly have this problem with the high res silent pics.
Only way to fix this is going to be altering what is skipped and what is not. Leaving off crop mode was quite cruel on their part and I know they tested the camera and saw these issues.
QuoteI appreciate that you are one of the only ones who understands the internal coding structure of the camera.
A1ex, aj, indy, and g3gg0 probably have it figured out much more than I do.
Bug:
Set electronic level in Display (not in Liveview tested), then you turn of the camera and then turn it on, the system can crash and the electronic level freeze or is very slow. Reinstalling of the firmware is possible because bootflag is defekt.
The level is bound to live view instance. So yea, it crashes out when you do that. Will have to make sure ML isn't doing anything with it at startup... its not supposed to be. Didn't even think to turn off the camera with level dialog up :)
Just tested it. It didn't do anything but blank out the level. I have this dialog turned off for photo. When I hit erase with the frozen level, ML menu comes up and going into a different mode or movie mode fixes it.
Quote from: 1% on March 07, 2013, 11:46:52 PM
We have 2 different sensor sizes here that have to be sampled with line skipping... even 1dC still skipping. 5d3 has a different sensor and a different resizing algo. Thats probably why they have less moire.
The 1dc doesn't line skip, it resizes to something a little smaller than aps-h(whatever is exactly 4K) so there is literally not going to be moire as long as someone doesn't remove the AA filter from inside the camera. The 1dc is for all extensive purposes a very good option. The thing I don't get is that there must be full sampling at some point for the 5d3. Why can't the 6d do this? Is it really a sensor level problem? I think it must be a firmware issue.
Also, dose the camera convert to YUV just because of subcolor sampling allowing for half the resolution in the color channels? Or is there some other reason?
Also, I have a bug, my magic zoom flikers when using on 720p
Quote from: fotojohni on March 08, 2013, 07:49:53 AM
Also, I have a bug, my magic zoom flikers when using on 720p
I think it's not a bug, it's the same on all Canon @ 720p 60p
It looks in sync to me on 720. I tried 1080/720/640 both large and full screen. maybe flickers once when it starts. And yea, other cameras have it much worse.
QuoteThe 1dc doesn't line skip, it resizes to something a little smaller than aps-h
The crop mode doesn't line skip. If they have any regular mode then it line skips. Still same tech from 6D/600D/etc.
QuoteAlso, dose the camera convert to YUV just because of subcolor sampling allowing for half the resolution in the color channels?
Probably not the only reason. Most cameras have native YUV instead of RGB. I know red might have native RGB, what about bmcc?
No full sampling at any point, nor does there have to be. It sees the whole image with the skips. If they could sample the whole thing why even bother. It *is* a firmware issue, the video should always have been cropped and the full view should have been a secondary option.
Fallen over FPS override image gallery: I straightened them up so they weren't all just garbage. Everything has a different image size. Some are 1804, 1814, 1690 for one even.
http://imgur.com/a/RBBtm
Quote from: Malex on March 08, 2013, 08:20:00 AM
I think it's not a bug, it's the same on all Canon @ 720p 60p
Quote from: 1% on March 08, 2013, 04:18:29 PM
It looks in sync to me on 720. I tried 1080/720/640 both large and full screen. maybe flickers once when it starts. And yea, other cameras have it much worse.
okay, I've seen this in my 600, I also want to note, I was able to record 720 @ 120mb, not sure what's actually happening. First time I tried the buffer filled up in about 2 seconds. Second time was gravy. More snow video :) I'm getting real tire of snow.
Quote from: 1% on March 08, 2013, 04:18:29 PM
Probably not the only reason. Most cameras have native YUV instead of RGB. I know red might have native RGB, what about bmcc?
No full sampling at any point, nor does there have to be. It sees the whole image with the skips. If they could sample the whole thing why even bother. It *is* a firmware issue, the video should always have been cropped and the full view should have been a secondary option.
Fallen over FPS override image gallery: I straightened them up so they weren't all just garbage. Everything has a different image size. Some are 1804, 1814, 1690 for one even.
http://imgur.com/a/RBBtm
what's going on there? That's crazy! Maybe that would work for some art house work. It looks as if for part of the image both the U and V channels are set at full, resulting in the magenta.
edit: Okay, I've just done a test with the camera and found that shifting to black and white makes no difference with moire. Does black and white occur after h.264 codec or is it truly just the Y cannel?
maybe this video will answer your question
https://vimeo.com/23508129
Black and white is probably just saturation at 0. It re-sizes all the channels, its not just the color.
So, if anyone cares, I just tested this card: http://www.bhphotovideo.com/c/product/854368-REG/SanDisk_SDSDX2_032G_X46_32GB_SDHC_Memory_Card.html
It benches: 39.2 (x8=313.6mb/s)
Override RCini to qp 1 and it averages about 135-140 (IPB) Looks dam GOOD!
However, it crashes when pointed to complex scenes :( it goes over 250 and CRASH! It did not pass the resolution chart test!
Any suggestions?
Don't force QP :)
I just installed it on my 6d.
I had previously used the 2.2x version of ML on my 50d.
The 2.3 version on the 6d is /amazing/.
I love the new menus!
The features I love work, thanks all for the hard work.
Except - audio tagging doesn't work (after photo taken press 'set'). Looks like the microphone doens't work if video mode is off.
*shrug.
Except - Rating the photos on review results in them simply being rotated. :)
Aside from that, I'm a very happy customer.
Yay!
I also love the exposure adjust on review.
The voice tags/wav will work as soon as I figure out how to send the stop dma command correctly. I think its function(address, dma code, something else). I need to be able to pass current buf though and I don't know how.
Also, my tokina cracked in half last night :'(
Found some interesting functions:
NSTUB(0xFF588630, str:[EffectWorkResizePath]_SetParameterEffectWorkR)
NSTUB(0xFF74C134, str:[EffctDrv]_ResizeHdVram_base)
I also found out the ML breaks my wifi remote shoot (via phone). I can view the image to remote shoot, but then it dies when I take a photo - the photo isn't saved.
if I boot the camera pressing the 'set' button and it says "Magic OFF" ... wifi remote shoot (to phone) still crashed in the same manner.
Not a huge issue, i'll take batt off and then shoot instead with oldschool 10sec timer and then use the android app to transfer pics successfully.
I haven't had time to assess whether it still works with a non ML memory card, but even if it doesn't, I still like shooting video at low frame rates :D. Sometime the buffer gets full ridiculously quick, meh, I just pick another FPS override. It seems to like as low as 10 fps, and stuff below that just makes it go poop.
Upload to webservice still works.
I dunno yet if GPS works. I hope it does.
I fixed the level at startup thing, still needs work for mode switches and photo mode. I know remote shoot is wonky. I have to work on that + hacking it into something useful. GPS should work.
8fps is as far as we got before getting the low light defects.
I just shot 16gb of material last night at 120mb/s, it looks nothing short of amazing. I used almost exclusively macro shots in a new kind of cooking video type thing. I think I will put music to it. The dinner tasted damn good, I shot the thing in real time and it didn't crash once! I reviewed the footage, I'm going to review in more depth on my eizo photo monitor but shooting low depth of field there were no problems anywhere. God the noise profile on q=1 is so nice.
I'm so happy with this.
edit: oh my god. I have the vertical bands. On a macbook it looks excellent, but upon closer inspection, 200% viewing magnification they are unmistakable in dark, low contrast areas when shot on marvels advanced... Still screen shots it looks great, but when it is moving you can see it. Only there when you look for it. But wow, I might be driven mad by this. I shot at iso 3200, all-i 24p
edit: Okay, I did some tests and found that the banding only exists when the shutter is manually overridden to 1/48, and not when it is at 1/44 or 1/60. I would love to have 180 degree footage, but I think I can make due with 1/44. Though I don't know to what extent this will make my footage bad (it could be a lot), in any case, that's where the vertical banding problem lies.
Post screen shots. I don't seem to get any lines at 1/48.. The lines are from fps override and sensor timing. They show in photo lv too.
Might have another issue with shutter values if I can reproduce it somehow.
This is at 1/63 of a second. All-i, vbr @bitrate = 12 initq = 1, iso = 3200
This is at 1/48 of a second. All-i, vbr @bitrate = 12 initq = 1, iso = 3200
I want to note that they look exactly the same pretty much. You will not see a difference on a monitor that's not a photoeditor. It looks excellent on a macbook, maybe this is to be expected and perhaps this was gravity's issue from before. His monitor was "too good"
Quote from: fotojohni on March 10, 2013, 12:56:15 AM
edit: oh my god. I have the vertical bands. On a macbook it looks excellent, but upon closer inspection, 200% viewing magnification they are unmistakable in dark, low contrast areas when shot on marvels advanced... Still screen shots it looks great, but when it is moving you can see it. Only there when you look for it. But wow, I might be driven mad by this. I shot at iso 3200, all-i 24p
edit: Okay, I did some tests and found that the banding only exists when the shutter is manually overridden to 1/48, and not when it is at 1/44 or 1/60. I would love to have 180 degree footage, but I think I can make due with 1/44. Though I don't know to what extent this will make my footage bad (it could be a lot), in any case, that's where the vertical banding problem lies.
I have this too! I seem to have it on ANY settings in LV. When in video mode, just pop your body cap on so no light is getting in and then slightly ease it off to let in just a tiny bit of light and you can see loads of vertical lines appear. If you can't recreate it this way then I'll just try and upload a vid tomorrow (need sleep now). Don't think this has anything to do with shutter speed and I didn't enable FPS override.
I can't tell a difference on this laptop. Going to try a 1080P big lcd. Can you process it to be more noticeable?
If you can see it on the LV... its pre-encoder. FPS override stuff is way more visible.
Tried the lens or body cap thing, zoomed in on LV, no lines.
Quote from: 1% on March 10, 2013, 05:27:46 AM
I can't tell a difference on this laptop. Going to try a 1080P big lcd. Can you process it to be more noticeable?
If you can see it on the LV... its pre-encoder. FPS override stuff is way more visible.
I'm not sure. It's very hard to see in LV even with a low contrast picture style like marvels. I'm not sure if its placebo honestly. But it's unmistakable one the monitor. I'm really kind of over it, I can get rid of it by crushing a stop of black, I'm not going to get frazzled by it.
Here's the 1/48th with a massive contrast boost and shadows luma boost.
The noise profile is fascinating on this camera.
Hello.
Sorry for interacting but I have one really basic question. Right now I am in Nepal filming documentary about street children with my 6d camera. I realized that I need time lapsing for the film but the problem is that shutter release for 6d is imposible to get in kathmandu.
Can you be so kind and tell me how can I install the latest development kit on my canon 6d. I have been working with ML for long time but I never installed the developer kit and that is the only option I have at that moment. Please tell me the steps how can I do it (I know that is not final version but at least I will be able to use a few features).
Thanks again and again sorry for interacting.
Best regards, Miha
Quote from: miha.mohoric on March 10, 2013, 06:19:12 AM
Hello.
Sorry for interacting but I have one really basic question. Right now I am in Nepal filming documentary about street children with my 6d camera. I realized that I need time lapsing for the film but the problem is that shutter release for 6d is imposible to get in kathmandu.
Can you be so kind and tell me how can I install the latest development kit on my canon 6d. I have been working with ML for long time but I never installed the developer kit and that is the only option I have at that moment. Please tell me the steps how can I do it (I know that is not final version but at least I will be able to use a few features).
Thanks again and again sorry for interacting.
Best regards, Miha
As far as I know 1% has single handedly made this a reality. Many, many sincere thanks.
Thanks to coutts as well
Quoted from Teo770:
I finaly success in instaling ML on Canon 6D, thanks all !
For other newbies like me, steps are:
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
- Get 6d-112.fir from:
http://bit.ly/ZgvGUf
- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini
- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card
- Put SD card in camera and update firmware while in M mode. Restart. That's it.
quoted from Noisyboy:
This is for anyone else as dumb as me! Props to the original poster! All working! Thanks guys.
Oh and in addition to this - 1% has handily put the ini's plus autoexec all in a tasty bite-sized zip folder which you'll find here:https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Thank you sooooo much. I really appreciate that.
Good luck and thank you all for doing amazing job.
Miha ;)
Quote from: fotojohni on March 10, 2013, 05:42:43 AM
I'm not sure. It's very hard to see in LV even with a low contrast picture style like marvels. I'm not sure if its placebo honestly. But it's unmistakable one the monitor. I'm really kind of over it, I can get rid of it by crushing a stop of black, I'm not going to get frazzled by it.
Doesn´t seem to be any of the lines on my stuff, shot at 24p, 1/50. I am using an eizo coloredge, but would be interested if you see them on your monitor, please take a look at this still.
http://postimage.org/image/q50p5zfrx/
Getting the image out of quicktime was a PITA and probably has introduced all sorts or artifacts converting it to a pct then to a jpeg - and it shrunk it to this small size, it was shot at 1080 :(
One thing, might it be from using a flat profile? Stretching the darks out could actually introduce banding? This was shot using the vision profile from milk.
edit: why cant i get the img tags to work here?
Looking at it on the on the big monitor I can kinda see it... but it looks like a noise pattern if anything. It is vertically shaped.
Noise reduction on/off makes a difference? I also set my marvels down to sharpness -1.
Here is the FPS noise comparison. Very easy to see.
(http://imgur.com/7m0433l)
Looking with a more detailed screen does the pattern match?
HAHAHAHA
welcome to my world
6D = garbage but I don't think it has anything to do with ML, possibly the sensor gets hot?
Well that's from FPS override. The other noise patterns don't appear on normal screens. Makes me thing canon made some sacrifices to get 6D sensor so sensitive.
I don't think its heat. Could be something ML does or brings to light. Maybe related to freezing in tethered modes. Either way seems fixable in software. regular 6D video is such paltry bit rates that all of this stuff could be masked. It shows in the silent pics pre encoder.
I agree, on the something being masked.
I will do more extensive tests on different bitrates, noise settings, picture profiles, sharpness settings etc. It is very subtle and I believe that there will be a way to get the footage looking perfect.
The images posted before were marvels advanced, sharpness to 0, contrast to 1, saturation to standard, noise reduction to standard.
I will test with different contrast, saturation and noise reduction later this week.
Feature request...
Would it be possible to have, under Photo options, a "reset at start-up" feature ?
This option would be activated only when camera is powered on, NOT when waking up from sleep, and would reset selectable things: white balance, exposition, drive, AF, iso ... all to default/auto or a custom setting ?
I don't know if ML can find out if it's a fresh start or a waking-up.
Could be usefull in my opinion.
Detecting a cold boot might be a problem, especially vs a mode change. You can already kind of do this. Register a C-Mode and turn off auto update. It should go back to what you originally registered at every restart.
I have C1 for P mode photos.
C2 for manual & movie.
with auto update.
I don't really reset settings often, reserved for messing something up.. i.e starting a movie in photo mode and not being able to go back (stays movie mode through power off).
You can also turn off config saving for ML and it will always go back to whatever is in the config.
I've been using the intervalometer through the last few .bin versions and it seems that it isn't quite stable yet.
Some of the problems i've been having are an error 80 for the first time today, also the camera will stop taking pictures and freeze (I noticed the "pictures left" # value blinking in the lcd if that means anything, and I still had plenty of room on the card) and the red LED will also blink when the camera is in the off position when this happens. I have to take out the battery to reset the camera.
I'm also using a 3rd party battery that the camera doesn't recognize, and on start up the camera asks wether I would like to continue using the camera with this unknown battery. Maybe just coincidence, but the intervalometer seems less stable with the 3rd party batteries.
I've been shooting in AV, mRAW, continuous shooting silent mode
Also, THANK YOU! I really appreciate the time the programmers & others put into making this awesome tool!
I only tried it with silent pics and it seemed to take them very fast. Will need more testing, did you get a log from the error 80?
Came here and notice that the early build is already kinda working in this new camera, good work! ;)
Would love to report back some logs when I found some errors. :)
Quote from: coutts on December 19, 2012, 12:17:55 AM
HD buffer resolution: LV mode: 1816x1210 pixels!!
So that's what silent pic size would be like? 100 pix focus stacks, here I come :-))
On another note: Any luck overriding the 1/4000 shutter and 1/180 x-sync limits? I'd be surprised if a little faster shutters and at least 1/200 x-sync wouldn't work, that seems to be marketing to separate the 6d from the 5d3... or does this fall under the (correct!) "do not backport 1dc->1dx" policy?
Haven't tried yet. Have no flash. Could work in theory. I tried 1/8k shutter in regular modes and it keeps getting overridden by canon code. Does look darker when its set.
Quote from: 1% on March 15, 2013, 03:03:24 PM
Haven't tried yet. Have no flash. Could work in theory.
Please do try - on comparison to alex and you many, many photogs use flash regularly, either for fill or as essential accessory for portraits. Canon knew what they did when they lowered x-sync on the 6d to 1/180s since the slow 1/200s on the 5d is really the absolute minimum to freeze non-posed portraits with the usual portrait focal lengths (i.e. 85 or 135).
Quote from: 1% on March 15, 2013, 03:03:24 PM
I tried 1/8k shutter in regular modes and it keeps getting overridden by canon code. Does look darker when its set.
I don't understand this - does it work or does it get overwritten (and if so, how were you able to discover the shots look darker)? Do intermediate values between 1/4000 and 1/8000 work better? Imho 1/8000 is pretty esoteric, but I do use 1/5000 or 1/6400 sometimes, esp. on bracketing for the -ev pictures.
QuoteFrom 1%: I have C1 for P mode photos.
C2 for manual & movie.
with auto update.
Yes, tested, it works (settings reset). Having C1 and C2 in photo mode is pretty cool to switch between personal settings.
I always used M mode to record movies to ensure shutter speed is 1/48 and control depth of field with aperture....
Thanks to you i just figure out we can also use C modes in Manual control !!!
Damned, why don't you guys write the Canon manuals !!!!!
Would be crystal clear !
Quote from: teo770 on March 16, 2013, 12:41:14 AM
Damned, why don't you guys write the Canon manuals !!!!!
Canon should employ them to write both the manuals, AND the firmware. ;)
Quotedoes it work or does it get overwritten
It works with expo override but as soon as canon does any kind of update it goes back to 1/4000. The intermediates work too. So impossible to keep that 1/8k... all you can do is see it on the LV for a little bit.
Quoteon comparison to alex and you many, many photogs use flash regularly
Gotta buy a cheap-o flash then.
1%, i don't know where you live but i can ship you a speedlite 90EX for 89€ + shipping.
Tiny, pockectable, perfect fill-in flash and fixes the lack of flash on 5D/6D, i love it !
My local photo shop gets them from splited EOS M packages so the price is low.
Let me know.
QuoteIt works with expo override but as soon as canon does any kind of update it goes back to 1/4000.
Good, so all you need to do is to change expo override code so it doesn't sync with Canon shutter speed above 1/4000. Currently it only syncs if the difference is larger than 0.5 EV or something like this.
Quote from: 1% on March 16, 2013, 04:25:53 AM
Gotta buy a cheap-o flash then.
I dont think you can go wrong with Yongnuos. Cheap as chips and high gn ratings. I have 4 YN460-ii and use them all the time for multi-light portrait shoots
I'm in the USA so shipping would kill from europe. Yongnuos look fancy and I'm a fan of chinese goods. YN560 looks fancy for only $72 bucks. The high speeds still look to be around ~$200 a little too much.
Heh, also when advanced HDR bracketing worked for video I could get crazy shutter speeds like 1/20k, etc.
Is this where it syncs with canon?
#ifdef FEATURE_EXPO_OVERRIDE
else if (buf[0] // sync expo override to Canon values
&& (!shutter_was_set_from_ml || ABS(buf[0] - lens_info.raw_shutter) > 3) // some cameras may attempt to round shutter value to 1/2 or 1/3 stops
// especially when pressing half-shutter
#ifdef CONFIG_500D
&& !is_movie_mode()
#endif
)
{
bv_set_rawshutter(buf[0]);
bv_auto_needed_by_shutter = 0;
shutter_was_set_from_ml = 0;
}
bv_auto_update();
Good point, I wanted to re-add those shutter speeds somewhere, maybe in the image effect menus.
I've just ported most changes in the main ML tree, but didn't test anything. At first sight, most things look alright, maybe the prop_lv_lens applies to M and 650D too.
Noticed some ugly things in bitrate code:
- some changes are applied even if no bitrate settings are enabled for menu. In this case, the user expects to get the default settings. Maybe the changes are harmless, but I just couldn't understand the code.
- it may reboot the camera in the middle of recording (?!?!)
So... my advice is to review the code carefully before you run this thing on your camera.
Shouldn't reboot in the middle of recording. Only reboots when recording "starts" but there is no writing. So if buffer level ever drops to absolute 0 in the middle of recording its possible but I haven't seen it happen yet.
Basically there is a problem when encoder isn't ready it doesn't write but says it does and you can't stop it without pulling the battery. This just reboots the camera so you don't have to do that. That can happen from bad settings or if user presses record before the config is fully loaded.
It does write 0s to target rate and init qp if override isn't set but those values are 0 by default so other than needless writing....
*also canon never writes to those locations so if you set an initqp and then don't zero it out it will keep it, maybe even across reboots.
Also noticed the 1/8k shutter stays if you override P mode but not if you override M mode.
Wait a minute, are you writing to ROM?!
I'd try to avoid the bad setting situations (e.g. block the record button if pressed too early) rather than rebooting the camera in the middle of recording.
Ram but not sure if those locations are initialized. I've written to some spots in ram and had it survive a reboot... ie the lv jpeg dumping function that is no longer used. I set the flag to write to B:/ and when I rebooted it was still there.
Also, one way to reproduce the not writing error 100% is to use real VBR mode and set a different target rate from max bit rate. I have no way to prevent the user from doing that since the configs are on the card.
It has never screwed up and just rebooted while recording. I don't think its possible to have a bytes written of 0 and still have a movie file.
When the encoder is locked like this an assert will not clear the busy error or stop the camera. Only the reboot or a battery pull.
I should make a video of how this state looks, maybe it will be easier to understand.
Partial fix for 1/8k in manual mode:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/0904f594e2503f4b44b72280ccba533247c6a8d5
I noticed when you step the camera down to 1920 x 1080 resolution in still mode, the moire simply does not exist. But when you shoot 1920 x 1080 motion, it's out of control. Maybe I am just confused how it is sampling, is there a way to utilize this some how?
Can you post some silent pics to confirm that?
Hi, I just want to inform you that I had to return my 6D+24-105mm because of the errors I was having (Err01 - Err70)
Also one night when I used it intensely to shoot a small concert, it was horrible because the 6D would randomly turn off by itself while recording, or it would freeze, I had to remove the battery to turn it off. I once played with the bitrate menu but recording would stop so I gave up and put back normal settings.
I was using a Sandisk 95MB/s.
I don't know why it did this, I assume I received a broken camera... So I reinstalled Canon firmware and sent it back. I'll get a new one in 3 weeks... :(
Did you try to use it a while without ML?
Quote from: a1ex on March 19, 2013, 12:24:11 AM
Did you try to use it a while without ML?
I was having the errors with the 24-105mm on my 550D also, (which had ML installed)
Then I reinstalled Canon firmware in the 6D and still had the errors! Then I took it to a canon repair place and the guy
put my 24-105 on a 500D (without ML) and the lens was working fine, I couldn't get the errors on it.
And my old lens worked fine with the 6D (at least no errors), so it was weird, so the repair guy told to return it.
My question : after having ML installed, then Canon firmware installed back, are there some ML foot print still in the camera?
Does the SD cards I got sucks?
Quote from: a1ex on March 18, 2013, 09:01:10 PM
Can you post some silent pics to confirm that?
Oh sorry, I just meant in regular stock firmware.
I am not even sure myself how silent picture works.
1920x1080 jpeg is read differently from the yuv video.
I got error 01 and error 70 together when my lens contacts weren't making contact. I would lose aperture on the screen and then it would do that when I took a pic. I cleaned the contacts and it went away... now the lens fell apart the rest of the way.
Any logs from shutdowns?
Quote from: 1% on March 19, 2013, 05:25:51 AM
Any logs from shutdowns?
some logs, and one crash log : https://dl.dropbox.com/u/2478549/logs.zip
Quote
at ./ColorCalc/ColorCalcState.c:387, task CLR_CALC
Same error I got from expo override being auto in certain modes. It would crash out bulb mode all the time till I set it to off. Were you changing any settings while shooting? Some high isos from photo mode don't work in movie mode and cause a freeze... but it would be right away. Only 1 log was loading config, others using eko.
Quote166.033 [WFT] PROP_NETWORK_FTP (1)
Did you ever configure/use FTP. I tried to add online services it would give me a certificate error in eos utility. I should check my logs for this too... maybe related to wifi/tether freezes.
I also see a couple of busy errors which I have the reboot for but they seem to clear and then log cuts off after a while without anything too informative.
Thats all I can think of for now.
QuoteIt would crash out bulb mode all the time
Probably it tries to adjust exposure according to bulb timer setting. This happens in lens.c, bv_expsim_shift - try commenting out its contents and see if it gets better.
This thing also kicks in when you use M mode and very slow shutter speeds (where Canon LiveView would be darker than the actual picture).
It only changes CONTROL_BV_TV, CONTROL_BV_ISO and display gain - maybe these are pointing to wrong locations?
Will check those. Works fine in M + P modes. Only bulb mode had the problems until expo override got turned off. Will also check FTP prop # and make sure its not being set by something else.
Its also strange that I can't get as high of an iso in movie mode as in photo mode. If I try, camera locks up. One of these goofy things must be causing the freezing, it seems the same accross the board, wifi, tether and sometimes video. It would happen before any bit rate hacks were even made so something somewhere is wrong.
*The offsets are right.
bulb mode error is
ASSERT: ControlIso <= LVGAIN_MAX_ISO
at ./LvCommon/LvGainController.c:837, task Evf
lv:1 mode:4
Have to keep investigating.
Quote from: 1% on March 16, 2013, 04:25:53 AM
Gotta buy a cheap-o flash then.
Good idea, just be sure to get a ettl one (like a cheap Yongnuo) because my impression is some ml features currently screw ettl metering (like auto-iso, expo lock) - but I didn't have time to track this enough to post a bug report.
Quote from: a1ex on March 16, 2013, 09:44:54 AM
Good, so all you need to do is to change expo override code so it doesn't sync with Canon shutter speed above 1/4000.
Amen :-)
Second one is done already. But its still just digital shutter.
Well, here's how you can all get vertical lines:
Go into photomode and set the camera to manual.
Set the magic lantern menu up to have a key shortcut that allows you to adjust the brightness with the arrow rocker.
Set the screen brightness up to +3 ev.
Point at something dark.
Doesn't matter the iso or the noise profile, actually it is most strongly noticed at iso 100. The interesting thing is that the noise is very constant I believe that if you pull a frame out from a small video clip of a perfectly regular black wall you could overlay the reverse of the pattern on top of your footage.
Keep in mind that you are viewing this at +3 ev, it's a pretty intense boost.
You are the best guys! :)
Messing with the digic registers that pattern starts to show up a lot. I really really hope the update fixes the resizing/timing issues.
Also it is possible to get fps override .2fps and NOT have lines which is really weird..
update from you or update from canon?
We're supposed to get the 4:2:2 hdmi software update like 5d3. Otherwise have to find the cause on our own and that isn't easy. They're in photo LV where encoder is disconnected and processing paths are different.
Quote from: 1% on March 21, 2013, 10:35:47 PM
We're supposed to get the 4:2:2 hdmi software update like 5d3. Otherwise have to find the cause on our own and that isn't easy. They're in photo LV where encoder is disconnected and processing paths are different.
Wow, that's amazing. Confidence restored. But seriously, the camera is a beast and has more than won my heart.
The solution is to do an image overlay or a burn or whatever photoshop calls their process that only touches the shadow portion of the image negatively. You overlay your reversal of the very clearly defined image pattern for each shutter speed. For us we really only have to worry about 1/48 for 99% of the time. If this can't be done in camera it can be done in post.
Quote from: 1% on March 21, 2013, 10:35:47 PM
We're supposed to get the 4:2:2 hdmi software update like 5d3. Otherwise have to find the cause on our own and that isn't easy. They're in photo LV where encoder is disconnected and processing paths are different.
Just out of curiosity, what makes you believe this is coming to the 6D dude? Haven't seen anything about announcements wise.
Would be SO happy if this were true though :)
I read it here.. hopefully they're not wrong
http://www.thefilmmakersworkshop.com/movie-cameras/canon-6d/
Quote from: 1% on March 22, 2013, 04:32:58 AM
I read it here.. hopefully they're not wrong
http://www.thefilmmakersworkshop.com/movie-cameras/canon-6d/
Yeah, I hope so too! That would be ace :) I do have my doubts by the fact that they also say that it should have no or close to no moire or aliasing issues though ;)
I think nobody expected the moire since 5d3 didn't have it (or as much). 720P especially with MZ... wow.
Maybe with digic registers I can expand the image correctly. Crappy crop is already possible.
http://youtu.be/Q5D8JcgHJck
Maybe its not so much crop as orientation flip.
Hi, I run ML on my 6D as well. First I had a jittering when using live view, so I deleted the config file, after that ML was running fine. I was only using the focus peak function, but after a couple of days it stopped working, the red/blue points don't appear any more while focusing in live view, and I have no clue what it could be. I tried to delete the config file again, and even reinstalled ML, but focus peaking still doesn't work. The ML version I am running is the one from the zip, built 03-01...
You had alpha blend on.. that uses overlay so it jitters. Check the focus peaking submenu, all the modes should work. Blinking dots is the one without jitter.
The jittering was gone after I deleted the config file, and I've had no problems since then. I didn't even change any settings in ML. It's just that focus peaking doesn't work any more, well I just noticed that all overlays are gone..? And yes, the canon menu is off in live view.
Check global draw settings. Make sure its on all modes.
The jittering is just the overlay, its normal, same on all cameras.
Global drawing is all on. I also tried with a different SD card. And last but not least I reset the camera settings and now it WORKS again! 8) Thanks anyways..
EDIT: Could you plese tell me where this alpha blend setting is? Because now it jitters again..
Focus peaking -> q -> pick blinking dots... alpha blend.. small buffer.. big buffer..
Also you should update the bin.
just got a 6d, after using a mk2 for a while.
check out my moire video though.. its really bad on mine.
Quote from: Versus on March 23, 2013, 06:19:35 PM
check out my moire video though.. its really bad on mine.
Moire is very bad on the 6d, it's a known problem (you can put an anti-aa filter in front of the sensor, but for the cost you could nearly get a 5d3). The reason is that the 5d3 used pixel binning - full hd is an exact full fraction of the original sensor size, while the 6d has to compute intermediate values.
My guess is that Canon designed this 20mp sensor not only to be lower than the "pro" cameras 5d2/5d3 but also to do worse for video, they want to sell their 5d3 after all ... there's no other explanation for the bad moirse performance :-\
So the short version: If you shoot video for a living, get the 5d3.
I don't know if its about competing vs 5d3 as much as it is about low light performance being a tradeoff vs the moire.
How does 6D low light stack up to 5d3 low light... they are definitely different sensors.
With timer A/B control FPS override can be tuned to get rid of the lines. Unfortunately the side effect of timerB is dark noise.. The specs might be dust on the sensor? I'm not sure... Purple cast in the corners is part of the dark noise.
The noise pattern and noise pattern with curve to make it more visible.
http://imgur.com/a/ceynY#0
Exact FPS tends to be line free. Adjust shutter (in adv menu) up until you reach one you can actually use or until speckle/lines/etc disappears.
Maybe there is a way in post to remove both this and the lines. I tried AE and color exclusion.. maybe better to matte it somehow?
*TimerB over 2000 gets rid of the lines at extreme fps. YMMV
Quote from: 1% on March 24, 2013, 05:48:51 PM
With timer A/B control FPS override can be tuned to get rid of the lines. Unfortunately the side effect of timerB is dark noise.. The specs might be dust on the sensor? I'm not sure... Purple cast in the corners is part of the dark noise.
The noise pattern and noise pattern with curve to make it more visible.
http://imgur.com/a/ceynY#0
Exact FPS tends to be line free. Adjust shutter (in adv menu) up until you reach one you can actually use or until speckle/lines/etc disappears.
Maybe there is a way in post to remove both this and the lines. I tried AE and color exclusion.. maybe better to matte it somehow?
*TimerB over 2000 gets rid of the lines at extreme fps. YMMV
I just use Neat Video in post and it gets rid of the crazy noise pattern so it ain't bothering me no more as realistically I denoise everything when doing the old 10-Bit up conversion technique, otherwise trying to grade is pretty useless.
Sucks that you should HAVE to do this but I'm doing it anyway (and I recommend anybody else should be as well) so it doesn't really matter :)
Still interested to see more of your findings though 1% and if by any miracle we one day have less moire or crazy noise patterns due to yours or anyone else's efforts then awesome!
Keep up the inspiring work man! You're a damn hero!
Quote from: noisyboy on March 25, 2013, 03:04:59 AM
I just use Neat Video in post and it gets rid of the crazy noise pattern so it ain't bothering me no more as realistically I denoise everything when doing the old 10-Bit up conversion technique, otherwise trying to grade is pretty useless.
Sucks that you should HAVE to do this but I'm doing it anyway (and I recommend anybody else should be as well) so it doesn't really matter :)
Still interested to see more of your findings though 1% and if by any miracle we one day have less moire or crazy noise patterns due to yours or anyone else's efforts then awesome!
Keep up the inspiring work man! You're a damn hero!
Is it a real possibility that moire could be reduced via ML? Or should I just buy the mosaic engineering filter and save some struggles?
Quote from: fauxtographer on March 25, 2013, 04:55:59 AM
Is it a real possibility that moire could be reduced via ML? Or should I just buy the mosaic engineering filter and save some struggles?
Yeah, I think I'm gonna get one myself dude. Done enough work with it now to realize it's actually a pretty boss camera, despite it's flaws. Seriously, the low light capability of this camera has saved my ass a good few times already so it's sticking by my side from now on for that reason alone. I would really like to see some more demo vids of the filter with the 6D first though (would especially like to see a demo with some post sharpening and grading). There only seems to be one demo on the net I can find so I guess that speaks volumes about how many people are coughing up for it!
In fact, I keep meaning to try this plugin out: http://www.isp.co.jp/en/products/tools/filmcolor/falsecolor/
Looks like it might go some way in helping fix some shots that have horrid patterns in them? If anyone else gets a chance before me, give it a shot and let me know what happens :)
Quote from: 1% on March 23, 2013, 11:03:55 PM
I don't know if its about competing vs 5d3 as much as it is about low light performance being a tradeoff vs the moire.
How does 6D low light stack up to 5d3 low light... they are definitely different sensors.
Fyi: The sensors are the same generation and overall the same, though the 6d has a tiny little bit more dynamic range at low iso and received some further readout optimizations and thus has even less banding than 5d3 (and way less than 5d2). The iso noise advantage of the 6d vs 5d3 is *maybe* 1/3 stop, but the tradoff is less sharpness (!) than 5d3 (even after downsizing 22->20mp) because the 6d seems to have stronger forced noise reduction even in raw.
Btw the 5d2 still has the sharpest sensor due to a weaker aa filter ... Nikon thus has two versions of the d800 and removed the aa filter in the d7100 to get more still shooting sharpness, but more moire.
In real life shooting, the only difference 6d/5d3 is a bit more usable iso12800 if you want it with the severely reduced dynamic range. The real low light advantage of the 6d is the center point af that goes down to -3lv (5d2: -2lv), but this has nothing to do with moire or the sensor.
Quote from: Versus on March 23, 2013, 06:19:35 PM
check out my moire video though.. its really bad on mine.
I checked the video in 1080p fullscreen, and I don't see the moire you're talking about ???, you guys are exaggerating a bit, aren't you?
Its not *that* bad... but I see it in vents, grates and roofs... 600D didn't have this. Its still quite usable just annoying.
Quoteoverall the same
Agree with the points but I think the weird decimal sensor size has something to do with the moire.
6D: CMOS, 35.8 x 23.9 mm
Actual: 20.6 Megapixel
Effective: 20.2 Megapixel
5d3 CMOS, 36 x 24 mm
Actual: 23.4 Megapixel
Effective: 22.3 Megapix
BTW... TTL flash is on the way.
what can/do I have to do to help w/ the 6d port? Got my cam here and im ready to do what I can!
Use it and have fun :)
Find reproducible bugs.
Quote from: DTSET123 on March 06, 2013, 10:12:48 PM
http://www.mosaicengineering.com/products/vaf/6d.html
I just watched the 6D demo video (https://vimeo.com/58335679) with/without VAF filter.The result looks great but the price is not to low.I was wondering is there any good alternative to remove moire by using software for example ?
Not yet, hopefully in the future.
I have seen a plugin for FCP that is "supposed" to do "something" as far as moire, but I have no personal experience.
VAF can be an option for the moment but unfortunately ,the annoying part will come when you take photos.You have to remove the filter in order to get the best quality , the filter is made for movie mode only.
Remove VAF filters for still photography. VAF-series filters are specifically designed for HD video -and should be removed to shoot high-quality still photography at your DSLR's full, native sensor resolution....
Quote from: Marsu42 on March 23, 2013, 10:52:55 PM
MMy guess is that Canon designed this 20mp sensor not only to be lower than the "pro" cameras 5d2/5d3 but also to do worse for video, they want to sell their 5d3 after all ... there's no other explanation for the bad moirse performance :-\
So the short version: If you shoot video for a living, get the 5d3.
But one level below, if we compare 6D vs. 5DMK2 the results are pretty much the same and I saw a few videos made with 5DMK2 looking amazing .Do you agree ?
Quote from: canonuser78 on March 28, 2013, 11:57:55 AMBut one level below, if we compare 6D vs. 5DMK2 the results are pretty much the same and I saw a few videos made with 5DMK2 looking amazing .Do you agree ?
Sure, the 5d2 had excellent video quality at that time, and both 21/20 mp chips don't like pixel binning like on the 5d3 so you have to expect some moire. Problem is: The world has revolved some times around the sun, and there are not-so-expensive cameras with ef lens mount that blow even the 5d3 out of the water (but lack Magic Lantern...): http://www.canonrumors.com/2012/09/canon-eos-5d-mark-iii-vs-blackmagic-design-cinema-camera/
Quote from: Marsu42 on March 28, 2013, 01:18:42 PM
Sure, the 5d2 had excellent video quality at that time, and both 21/20 mp chips don't like pixel binning like on the 5d3 so you have to expect some moire. Problem is: The world has revolved some times around the sun, and there are not-so-expensive cameras with ef lens mount that blow even the 5d3 out of the water (but lack Magic Lantern...): http://www.canonrumors.com/2012/09/canon-eos-5d-mark-iii-vs-blackmagic-design-cinema-camera/
good video, whoa.
Quote from: 1% on March 24, 2013, 05:48:51 PM
With timer A/B control FPS override can be tuned to get rid of the lines. Unfortunately the side effect of timerB is dark noise.. The specs might be dust on the sensor? I'm not sure... Purple cast in the corners is part of the dark noise.
The noise pattern and noise pattern with curve to make it more visible.
http://imgur.com/a/ceynY#0
Exact FPS tends to be line free. Adjust shutter (in adv menu) up until you reach one you can actually use or until speckle/lines/etc disappears.
Maybe there is a way in post to remove both this and the lines. I tried AE and color exclusion.. maybe better to matte it somehow?
*TimerB over 2000 gets rid of the lines at extreme fps. YMMV
Reminds me of back when I had a powershot and used chdk, one effect of using >30second exposures made purple / pink distortions like that in the same manner (usually in one corner), they determined it's due to sensor heat.
what do the temps look like when this happens (higher than normal)?
18C when camera started went up to 36C with fps on after a while. Iso 800... minimal defects. ISO 1250 pink corners.
So loosly related to temperature but also to ISO.
Left it at 2fps for a while temp went up to 54c but number of defects didn't change. Have to see what temp is when I get a video like that with defects everywhere. Turning down digic gain helps too.
Great work 1%, you are my hero!
I have installed ML on my new Canon 6D. All works fine but it freezes my camera when trying to make it work with DSLR Controller android app.
Is there any reason why DSLR Controller should not work on the 6D? It works great on my t2i...
Guys keep the great work!
I have issues with sending LV over wifi or usb... camera just freezes. Looking into it, eventually gets an error 80 but unable to find what the actual error is. Want to try sending DLNA lv.. that might be worth recording and might help solve this problem too (canon docs say its possible but only see an empty canon directory). Any error messages would be helpful too.
The other functions like sending ptp commands and shooting over web should work. For now turn off the live preview.
*got the adapter today. Expo sim doesn't know what to do so its either over or under... have to try the patch.
Patch helps but I bought the adapter with movable aperture and setting it to anything but the widest setting results in darkening by expo sim. So I set lens to 8.0 and adapter to 8.0 and get an F16 exposim.
[DUPE]
Is the headphone monitoring working? Just waiting for my battery to fully charge so I can load ML on to it...
Is it much like the 5D mark 3 in the way you control it?
Monitor only enbles the screen. Headphones still not working.
The M seems to suffer the vertical line thing too, here you can see it starts at about 0:04 and gets progressively worse through the timelapse. I shot this for about 9 hours.
now I know I'm not crazy lol
All new sensors probably have the lines. Did the sensor get hot?
In the Sony FS-100 the 60 fps mode is at 28 mbps CBR, and since the 6D has a 100 mbps ALL-i mode at 24 fps and 30 fps.... It seems as though the cameras processor is capable of high bit rates, but is it not capable of high frame rates? What would be the limiting factor in regards to that? Is it purely something to do with the architecture of the encoder? Or something that can be bypassed with enough digging?
I for one would be happy with 28 mbps 1080 60p.
Its 2 things. Sensor timing and HW encoder.
Sensor does like 38/39 fps before it falls over.
Encoder starts jerking much earlier than that.
60P doesn't seem possible... maybe at some reduced resolution between 720p and 1080p and it can't be H264. I'd be happy to find timings that don't produce lines or the overheating?/dark noise.
The above timelapse video should be sent to canon.
They will probably just laugh at our method for pushing the sensor beyond limits (pretty sure we have missed some parameter when configuring sensor timers).
When you alter the parameters way beyond the normal operating ranges, you should no longer blame the manufacturer ;)
I feel like it isn't impossible, I wish I knew a little more than what I was talking about...
I just don't see how a sensor that can take in 100mbps at 30 fps.. can't take in 60 fps at something like 20-30 mbps.
How can I help research this?
By reading the sticky threads, especially this: http://www.magiclantern.fm/forum/index.php?topic=950
Quote from: a1ex on April 02, 2013, 10:22:00 PM
They will probably just laugh at our method for pushing the sensor beyond limits (pretty sure we have missed some parameter when configuring sensor timers).
so does this mean the vertical lines issue may eventually have a solution?
Hello,
I'm french and don't practice fluent english.
By the way, is ML for 6D ready or enough ready to be used without risk ?
If the answer is positive, where can it be downloaded ?
Thanks by advance
Yann
Quote from: 1% on March 24, 2013, 05:48:51 PM
With timer A/B control FPS override can be tuned to get rid of the lines. Unfortunately the side effect of timerB is dark noise.. The specs might be dust on the sensor? I'm not sure... Purple cast in the corners is part of the dark noise.
...
Quote from: coutts on April 02, 2013, 04:13:35 AM
The M seems to suffer the vertical line thing too, here you can see it starts at about 0:04 and gets progressively worse through the timelapse. I shot this for about 9 hours.
Did you guys experienced the same situation without ML in a regular timelapse shot through 6D ? if not, sorry if sounds stupid ( dooh! ) but why do we need ML on timelapse ,to improove what ? ISO is pretty good at high rates, ... what else ?
thanks
Can't do timelapse without ML.
oh, I got it. thanks 1%
So the ML will do what we can do with an Intervalometer (http://opteka.com/itc50-c3.aspx) for example right ?
In this case, I will reformulate the question : If I use an intervalometer , the result will be the same (dark noise/lines on the final video) ? I am counting the worst case when this option of ML will be impossible to be fixed on 6D .
The dark noise problem appears only when you use FPS override.
There may be a solution to this at some point but not yet. Affects all digic V class cameras. We're not the only ones. Either tinker with the timers till you get neither kind of noise or shoot stills.
Thanks 1% for all the time you've put into this!
I've been following this thread since the beginning, but may have missed this one if it came up: should the movie mode intervalometer work? The user manual says that it should show a "duration of a movie clip" option, but I don't see it anywhere.
I think that feature got cut with new menus. I have stop movie after X minutes and record on startup.. an intervalometer this isnt.
Ah, thanks. I tried using stop after X with movie restart to cover what I wanted to do for now, but it doesn't look like it restarts after the timed stop. I'll use an external intervalometer + stop after X until I figure out how to make ML changes for myself.
Movie restart is for when recording stops from canon. Stop after is like pressing the record button. I suppose the 2 could be combined.
You can just write a script that implements movie intervalometer.
I'll also include the best scripts in the ML zip.
No body to answer me ?
May be this subject is for developpers only ?
Thanks to give me one confirmation.
Bst Rgds
Yann
@yannlesaout:
If you really interested to try ML on the 6D read the thread from the beginning to learn..
see post #832 (short instruction) http://www.magiclantern.fm/forum/index.php?topic=3904.msg28473#msg28473
Its a developer version and risky!.
I just got flush rates working... might help the fixed QP people.
Well, I get 200+ megabits and recorder shows no sign of stopping... but I'm stuck at
ASSERT: pHeader->pcsSignature == m_pcsSignature
at ./MovieRecorder/MovRecResource.c:471, task MovieRecorder
lv:1 mode:3
If I just patch it recording never stops and camera stays busy. Need to see what calls it and maybe patch that. So far no luck.
*ok.. we can do 4 frames of flush... no crashing... slightly better than stock?
Gop changing doesn't seem to do anything to the meta data, would have to see if real gop is changed in files.
Also maybe a thing on where the 30 minute limit comes from for real:
NSTUB(0xFF0EA298, str:MOVW_GetMaxFrameCount_FramePerSec)
*(arg0) = 1800*(*0x74F94)->off_0x18C
So need some more testing before I give it to you all.
Exmem chunking works:
Ok thank you for the answer.
I'll wait a safe version, I'm not a developper at all ;)
Yann
It records fine but it does not play back. It seems that when it hits 150mbs or higher the playback gets stuck
Same problem as 600D with higher rates... I think we've topped out the player finally. Flush 1 allowed QP 1 recording without stopping and went over 200, wish it worked to write out the files.
Maybe its possible to comment out the avi conversion and convert the dats on the computer.
Wait whats happening???
Flush rate is working... but not flush <4.. at least that won't close/convert files.
So... I made a 400Mb/s video hardly anything wants to play it back. Frame by frame most stuff is there... a few are glitched out. I was overriding rate control, maybe will have better luck with real CBR config since they look like when RC was running out of QPs.
That recently posted lvrec + encode Jpeg function would be absolute win here. I think this is violating H264 spec by a metric assoload.I think spec is only 120. I set target @ 200 so maybe that needs to be adjusted when overriding since its almost twice that all the way through. 15 seconds was 800MB. But good to see camera performance is there to do what we want.
CBR and setting target higher seems to help... maybe all_I would be good here as I think the damage is from inter frame compression.
Good frame:
(http://imgur.com/Y627vOh)
Damaged Frame:
(http://imgur.com/XBiUhE6)
I think at 400Mb/s the IPB vs I might not matter anymore.
All I has problems stopping due to complexity. Just increasing target (without init QP) on rate control to like 200 or so and speeding the flush rate is producing really nice results on IPB24 rate control.
I had similar results when I tried qp1, but again if the scene is complicated (like moving grass) it wont even start recording(flush set to auto). I just recorded at 160mbs at qp 1-5 modified in RCini. It plays back in premiere but skips frames. Now Im trying to convert to yuv422 using mpeg streamclip to see if it will play smoothly but it is a SLOW process
Auto flush is just regular canon dynamic flush rate. 4 is max speed. Also... all I with upped flush rate runs out of QPs and has defects. IPB24 with rate control and increased target (maybe even past 200) seems to be winner in terms of not stopping and not seeing defects.
Playback from the card is skippy, playback from HDD isn't (I only have USB2 reader). I usually check everything in virtualdub and go frame by frame to see if anything skips or if there are missing lines... As with increased flush 600D video the rolling shutter is more noticeable.
QuotePlayback from the card is skippy, playback from HDD isn't
mmm..., I don't know. I copied the file to my hard drive which is SSD before playing it. It finished converting and it is still skipping except that a file is 10gb instead of 2. Maybe like you said the flush needs to me at 4?
Its nice to be able to record at qp1, But im out of ideas as how to play it back. I tried converting but all attempts failed. windows media player and vlc attempt to play it but it is not smooth at all and in premier it is just blank green. Any ideas?
So increasing to 200, what could that help improve? Overall sharpness, perhaps better moire control?
Bug report .. maybe.
Gday.
I'm holidaying in Egypt now and wanted to take a bulb timer photo of the Nile at night. Which I am, right now, thanks to ML.
I get a live-view crash, and if I off-on the camera, then I get error 80. Taking out the battery and putting it back in helps.
What I did is as follows:
- Set Bulb mode on Mode dial (which also, incidentally lost the thingy with the letters. It fell off)
- Set a 1minute exposure on ML.
- Take a photo. (this step may not be necessary)
- Activate Live view while on Bulb, with ML set to 1minute.
Result: LV does not actually show up on screen. The mirror does flip up but nothing is displayed.
Through the canon menu I have the exposure simulation on, and on ML I had the exposure overide on, then off - and it crashed on both cases.
Nevertheless, a battery out and in fixed it. Yay.
There's a crash00.log that says:
Quote
ASSERT: ControlIso <= LVGAIN_MAX_ISO
at ./LvCommon/LvGainController.c:837, task Evf
lv:1 mode:4
Magic Lantern version : v2.3.NEXT.2013Mar16.6D112
Mercurial changeset : 0904f594e250 (unified) tip
Built on 2013-03-17 02:28:28 by user@D610.
Free Memory : 448K + 3012K
Disabling exposure override should fix it. Sounds like ML tried to simulate the bulb exposure (according to the bulb timer value), but it tried to set a very high ISO which Canon code didn't like.
With expo override off, ML doesn't touch the ISO in bulb mode, so you may want to repeat the test. If it still crashes, it's probably a bigger bug hidden somewhere.
Lowering MAX_ISO_BV in lens.h should help.
Edit: for 6D, MAX_ISO_BV is 136.
Yep, bulb mode is the one with the problem on override. Max ISO is good for the other modes. If I just lower it then it will cripple the other modes & video, will it not?
Maybe need to add if something like if mode == bulb max iso = X type of thing...
I drove around and shot more video, have to check it. Stock IPB is garbage but rate controlled 60-80 looks good and with flush rate it handles scenes where the rate goes into 100s-140s for as long as it needs to. I haven't had a stop with it yet. Its a balance between stability and super high rates. I dunno what scene really needs 400Mb/s. I did take some ~300Mb/s stuff that didn't have defects and seemed to play back.
Look at all the videos you have and make sure they aren't skipping because of defects. Check it out real fast frame by frame in virtualdub. These vids violate specs for ANY player. Also convert to PNG and make an image sequence that way
Still need to patch audio somehow... maybe 600D will shed light on it with working 25p mode. Separate wav is working but only for under 2 mins. I haven't tried to shoot concurrently with video yet.
Reboot needs a fix to detect if recorder really stopped other than bytes written and bitrate, with flush sped up that instant rate is 0 a lot and buffer is pretty empty. A reliable detection method will kill all false positives.
P.S. The moire is unaffected by encoding. Its present in the 422 buffer which is theoretically MAX image quality.
Yep!
You were correct.
With bulb timer on at 1m with expo override on = hang.
with bulb timer on at 1m with expo override off = no hang - ok
Well, 136 is Canon's limit (that's ISO 25600). You still have digital ISO of +1EV (so you can still get ISO 51200).
You won't get obscene ISOs like 819200 in movie mode, but you will still have them in photo mode via display gain.
51200 is the most I get from movie mode. Double that with HTP enabled and that 1EV of canon gain. I get higher from the canon menu in photo mode LV.
So worth looking at the limit.
You can also boost ISO from vignetting correction (probably 2-3 EV), see lv-img-engio.c:512.
I just tried the fix and movie mode is unaffected. You can't make H1 and H2 isos in photo mode anymore but you can select them from the canon menu. Also lose one ISO with HTP. But these high ass ISOs... I don't think anyone uses them.
I think the problem is bub mode doesn't allow iso expansion, you can't select H1/H2 from the canon menu either. 5d3 should be affected by this bug too in theory.
Nope, only the 6D has this limit. When I wrote the bulb expsim feature, I've used the 5D3.
Odd.. I wonder what is different and if it could be patched to uhm... match 650D, lol.
Hi! How to use this firmware? after installing it in my camera I have it does not respond to the power button.What am I doing wrong? or firmware is not yet ready to be released? Willing to help with testing and do not know how? Thank you!! :(
sorry - the answer on page 8 :D
You use it just like ML on any other camera.
.fir file to set boot flag. autoexec.bin is the executable. card has to be boot/dev flagged with something like eos card. ML folder for support files.
If you read the thread this question has been asked/answered like 50 times.
Hi
here is a short film i shot with my Canon 6D, 24-105 f4 L, cinestyle profile and Magic Lantern !
Works really fine !!
I just missed the headphones.
http://vimeo.com/63472625
+1 for headphones
Also, what are the odds that if you guys get your hands on the 5D3 firmware and rip it apart, that we could see a similar HDMI output on the 6D.. are the internals of the two cameras really that different? Does the 5D3 have a different GPU etc?
5d3 and 6D are pretty much identical in the FW.
Headphones are hard because I can't figure out the real audio chip and the only "headphone" related stuff pertains to the actual headphone jack. So I can enable that but its useless (maybe if you rip your camera apart and wire it in then it will work). I need to actually route audio from ADC -> DAC to be able to hear anything.
Once the chip is identified I can look through the datasheet and try to send commands to see if audio_ic_read/write are correct.
The update will possibly come out for both cameras, right now its just vaporware on 5d3 too.
1% this is simply just a stupid question.
In the firmware, is there code that is controlling the way the encoder is gathering the data off the sensor. Or is it purely hardware that is doing this? I ask, because as well all know, the 5D3 has a base resolution of 5760 x 3840 which is roughly 22 Megapixel, which we divide by 3 and that equals 1920 x 1080. But with a total photo receptor count of 23.4 Megapixel we have roughly 1 and a bit megapixel that isn't used. How is that controlled? Is there a way to change that number? would that screw things up.
I only ask as the 6D doesn't have these magical sensor numbers, but can we make it have more appropriate numbers for sampling to 1080p? or is this some serious stuff...
I only ask this as an end user... with no knowledge of what I am talking about. haha
http://www.atomos.com/whats-new/#Atomos
Also, Atomos will be demoing the Ninja 2 with a 5D 3 this week at NAB, firmware out in May.
The H264 encoder just encodes the LV HD buffer. It doesn't sample anything.
So you start with the same .422 image(s) in the buffer and then encode to
1. Really compressed H264 -throws lots away
2. Not so compressed H264 - doesn't throw as much away
This part is fine.
Other functions configure digic to read and make that HD buffer. So yes its possible to change those just how? Registers? A cache hack? Its not discovered yet.
It is possible as I somehow hacked 600D photo mode buffer to be video sized. Eventually that went away (i think it got reconfigured when HDMI was plugged in) but I have the hacks saved somewhere and I'll have to try again. Might be easier to do it through digic regs, that bootleg crop mode did zoom the image.
Oh okay, I definitely learned something now. That actually makes a lot of sense. So it is basically takes all these .422 images and then encodes them with the H.264 encoder, I understand now.
So with the 600D, the digital zoom is the very idea I am think of...if it could somehow be ported, hacked or smashed into the 6D.
http://www.youtube.com/watch?v=AixwZupTyeA
This video is what I am talking about, I wonder if besides a 3x leap in crop, if there is a way to choose a different value. This could possibly reduce the moire quite a bit.
Its a live constantly updating .422 but other than that pretty much right.
Some of the crop mode stuff is in 6D firmware but so far all it did was make a brick when trying it.
Resizing LV/HD is on the list, just very hard.
It's best I don't even try helping with this stuff, I already hard bricked my Galaxy S3 and can't handle wrecking something else.
Just let me know how to help.
Just for Info:
New little firmware update from Canon
http://www.canonwatch.com/canon-eos-6d-firmware-update-released-version-1-1-3/
I hope with this update ML is working :-/. Should I try it ?.
No, it will just refuse to boot.
Ok thanks for the info. I'll wait for an update from ML or downgrade the original firmware.
I used the 6D extensively this weekend using the autoexec.bin-Flush_tester release, seemed to be pretty stable - minus shoot malloc error with format dialog (could ignore, had another card with me).
Looking great 1% ;)
Quote
1. Fixes a phenomenon in which the Date/Time/Zone settings screen appears on the LCD display, after the user has already configured these settings. The values for the Date/Time settings may reset if the backup functions which retain those values do not perform properly.
That's it? Of all the bugs that is what you fix?
How do I go about porting/checking?
Quote from: 1% on April 09, 2013, 04:39:15 PM
That's it? Of all the bugs that is what you fix?
How do I go about porting/checking?
I can do it later today if you'd like, i like doing grunt work like checking stubs by hand :D
All you've gotta do is verify the stubs. Most likely stubs towards the start of the rom (cstart, etc) won't change but at some point canon added some code so everything after that point is shifted by a fixed amount. It's best to just check them all by hand though.
Yes please. Good thing I can use some stubs to verify image position so I don't get mis aligned like with 5d3.
I really really hope they fixed some other things and didn't just pull a 600D where they fixed nothing.
* also need to know how to dump ram segment since I'll probably need a new one.
Quote from: 1% on April 09, 2013, 04:55:39 PM
Yes please. Good thing I can use some stubs to verify image position so I don't get mis aligned like with 5d3.
I really really hope they fixed some other things and didn't just pull a 600D where they fixed nothing.
* also need to know how to dump ram segment since I'll probably need a new one.
I highly doubt the ram segment has changed but I'll verify that tonight. If anything the position of it just changed. The ram functions seem to all be the same, like some kind of "library package" for use on multiple platforms.
most likely the rom will be like:
before:
[=start===============end=]
now:
[=start=======[newcode]========end=]
just a slight shift (if anything new added)
Have you noticed if increasing the bitrate, reduces aliasing and moire? At least in the 6D?
They are not related, see http://en.wikipedia.org/wiki/Aliasing
Hi all,
long time lurker who has used ML on the 60D for ages with manual lenses.
Now I have a 6D I was wondering if this current release has a similar exposure override fix have proper live view exposure sim with manual lenses, and if there was currently any downside to using it?
Thanks in advance.
I turned the fix for that on. It mostly works.
Fantastic. Thanks 1%.
'Mostly works' is my 2nd favourite type of 'works'. :)
On the adjustable adapter moving the "aperture" still darkens the screen.. at wide open it seems to keep correct exposure.
Just out of curiosity (and I plan to buy a 6d): Did you give up on the af patterns, or is there still hope for progress. I like this feature on my 60d and would miss it ...
I have to see how it works on 5d3 and try to implement it that way. Xoring the af points does nothing and there are 2 orientations of them. So if you turn your camera sideways it will change to a different pattern via cfn.
In the 5d3 file it says they are available but I have no clue how it works and we have some of the same properties. Someone with 5d3 has to enlighten me or maybe I can figure something out from the FW, I haven't so far.
I miss them too.
They are not working in 5D3, it has a gazillion of AF points, so the old code won't work.
This latest .bin is really, really good. I almost wish that it would default to vbr flushrate = 4, qp = 1, bitrate = 8 because it's very reliable at that rate and produces good footage.
I have one feature request. Canon in it's infinite wisdom removed the flash on rear curtain functionality from it's menus. As a result I can't take great motion trail shots with a rear curtain flash if I'm using a non-canon flash. I'm using a yongnuo speedlight, which is really excellent for the money. The thing doesn't sync past 1/180 shutter, which is fine, but I would really like it to take rear curtain shots on 1/4 second shutter, which has produced fantastic results in the past.
Also, Is there a way to do shutter sync through the remote trigger port in movie mode?
The settings you use are saying:
VBR method
Fixed QP 1
Target rate 80.
So theoretically you have a vid thats just QP1 all the way. Should be same for CBR/RC/VBR. Not loading a config should produce same video except with CAVLC & profile 4.1.
I think someone needs to do low level analysis and find what mode is really best for what. You can make videos from 20Mb/s to 400Mb/s. Have to find where the cutoff is, my default is RC because it handles most situations and does 60-120Mb/s, flush rate or not. Other people like fixed qp, other people like this or that.
For flash, still working on it. YN-468-II has a HZ on the box but HZ won't activate from canon menu. Rear curtain does seem to work tho. An array in memory gets filled with all prop data, its written to the prop and then the whole thing is erased. I have to try canon functions to change parameters, the prop won't work for curtain/sync/etc.
What? I am using the new Yongnuo flash triggers. I can see front/rear curtain in the camera menu. I am even using a vivitar ETTL flash and the trigger works with it. With this trigger you can sync past 1/180th also using HSS(if the flash support it).
Quote from: fotojohni on April 10, 2013, 08:08:20 PM
I have one feature request. Canon in it's infinite wisdom removed the flash on rear curtain functionality from it's menus. As a result I can't take great motion trail shots with a rear curtain flash if I'm using a non-canon flash. I'm using a yongnuo speedlight, which is really excellent for the money. The thing doesn't sync past 1/180 shutter, which is fine, but I would really like it to take rear curtain shots on 1/4 second shutter, which has produced fantastic results in the past.
Yea, I have all menus enabled but some do not activate. Rear curtain is one thing that works. High speed does not, just kicks me back to previous screen.
so just compile from the nightly build and load it as normal? (sorry, new to the Dev versions)
6D
Main ML repo might be behind. Compare with my repo first or grab a pre-made bin.
todo: merge 1%'s repo with main (and update to newest firmware version in the process)
Have to make sure that doesn't wipe the platform folder just rename it on my side. Hopefully the update fixes wifi tethering and lv sending for me. That would make things complete. And of course have to disassemble/decompile new bin.
Quote from: coutts on April 11, 2013, 05:26:23 PM
todo: merge 1%'s repo with main (and update to newest firmware version in the process)
Hi I got a new 6D + 24-70mm (the 1st I received was acting weird) this one works fine.
This new 6D is on 1.1.3 , so is it ok to install ML on it?
Should I install 1.1.2 and this install ML, then update to 1.1.3??
I don't think the updater will pass the checksum check. Wait till we 1.1.3.
Quote from: zhound on April 11, 2013, 02:06:09 AM
What? I am using the new Yongnuo flash triggers. I can see front/rear curtain in the camera menu. I am even using a vivitar ETTL flash and the trigger works with it. With this trigger you can sync past 1/180th also using HSS(if the flash support it).
Interesting, I have a wireless flash trigger and when I try to pull up the menu it tells me: "flash not connected or not recognized" I will update my .bin to the latest and see if that fixes it.
yeah, I can push the shutter speed to whatever I want, but when I push it past 1/180, the shutter curtain starts to cut part of the flash off. I'll play around with it and see what works.
Thanks guys.
All flash tweaks do so far is enable higher expo correction ad flash/no flash.
If your wireless trigger is not ETTL you won't have any access to the flash menus. All manual.
If I put my Vivitar flash directly on the hot shoe I also have limited functionality in the camera menu. It does let me do rear/front curtain, and flash EV compensation. Using the ETTL trigger allows for higher sync speeds and all the flash menus are open including flash bracketing etc. And remember to sync higher than 1/180th your flash has to support high speed sync.
Quote from: fotojohni on April 11, 2013, 10:31:04 PM
Interesting, I have a wireless flash trigger and when I try to pull up the menu it tells me: "flash not connected or not recognized" I will update my .bin to the latest and see if that fixes it.
yeah, I can push the shutter speed to whatever I want, but when I push it past 1/180, the shutter curtain starts to cut part of the flash off. I'll play around with it and see what works.
Thanks guys.
Same here with a Vivitar flash. I suspect that 6D is tuned to work with canon's new flashes. Which makes these third party flashes not work so well. Using a ETTL trigger though seems to open all the menu functions whether your flash supports it or not.
EDIT: For your YN-468:
http://speedlights.net/2010/10/10/yongnuo-yn-468-flash-review/
""The YN468 has a sync mode button as well, unfortunately there is no HSS setting available. But there is another option to activate high speed sync apart from setting it on the strobe itself: you can change the sync mode in the camera menu, navigating to the yellow menu group, "Flash control" and then "external flash synch. setting". And yes, with the Yongnuo in the accessory shoe you can switch the 40D to Hi-Speed too! Unfortunately, it instantly jumps back to "1st curtain", so no high speed sync available. Sad news. But not unexpected."
Quote from: 1% on April 11, 2013, 02:53:29 AM
Yea, I have all menus enabled but some do not activate. Rear curtain is one thing that works. High speed does not, just kicks me back to previous screen.
That sucks. Its got the high speed icon on the box.
I figured out some props for shutter and shutter range.... I am able to set 1/200 on screen but the photos still come out at 1/180 when TTL/metering kicks in.
Looking more into props... maybe can unlock 1/8k shutter and stuff like that. We'll see.
I will personally send you beer if you do this. Dead serious.
Quote from: 1% on April 12, 2013, 03:27:28 AM
Looking more into props... maybe can unlock 1/8k shutter and stuff like that. We'll see.
I bought a 6D. It is with firmware 1.13, and I can not install the Magic Lantern.
The message: Update file can not be found. Please check the memory card and reload the battey and try again.
Can someone help me how do I install?
Have to wait till we update. I don't have new signed updater.fir to give you.
So far no go.
Flash off camera: can change shutter prop 2, and range, prop 1 won't change.
Flash ON: can't change range or prop 2 but can change prop 1 and it shows on the screen but resets with h/s press.
Valid values take the changes.
But as the home site has a banner saying it has the magic lantern to 6D?
you need 1.1.2
Quote from: DTSET123 on April 12, 2013, 06:42:59 AM
you need 1.1.2
Yes I just installed the 1.1.2 that's the same warning, not work.
Would this, ok?
http://www.magiclantern.fm/download
no, you need to go back - instructions on this post have been given like 25 times
Quote from: 1% on April 12, 2013, 03:27:28 AM
Looking more into props... maybe can unlock 1/8k shutter and stuff like that. We'll see.
* I still don't quite understand what ml is able to do: If the Canon code resets the shutter (marketing kludge), can ml disable this by patching the Canon code?
* 1/200 x-sync doesn't seem to work by just enabling it, only as "hypersync" since the 2nd shutter comes down after 1/180s: http://www.canonrumors.com/forum/index.php?topic=14095.msg255627#msg255627
* Edit: While you're at it, feel free to try to circumvent the f8 limitation for Canon extenders (with Kenko extenders that cheat the camera it works) :->
Hi, first of all thank You for your GREAT work!!
I am using ML on 550d from the beginning. Now i have also 6d.
Is HDR video feature works in latest build or not yet?
HDR works fine.
I will probably have to cache hack it as changing props isn't working for out of range values. The key is finding what is setting the prop and so far I've come up empty on most of it. I'll probably have to look for the addresses that get loaded into the props.
This is where it turns the range into props:
NSTUB(0xFF1C1CA4, str:tv_range_lx)
You can try to find this stub on other cameras, its probably similar.
600D: NSTUB(0xFF0BC694, AJ_guess_GUI_force_lock_display_tv)
New stream analysis tools are opening 6D files!
Found out a few quick things:
* Gop seems to affect what QP is picked by dynamic configs. I have to investigate more
* Flush of 4 will produce high rates but be careful... it can drop frames. I proved with virtualdub.
The 4x4, 16x16, and 8x8 matrices seem to be used dynamically throughout the file. This would be the parameter to attack a la gop and flush rate.
*Gop setting has an issue, there are dwords in there and it does different things based on them.
Quote from: 1% on April 14, 2013, 08:20:20 PM
New stream analysis tools are opening 6D files!
Found out a few quick things:
* Gop seems to affect what QP is picked by dynamic configs. I have to investigate more
* Flush of 4 will produce high rates but be careful... it can drop frames. I proved with virtualdub.
The 4x4, 16x16, and 8x8 matrices seem to be used dynamically throughout the file. This would be the parameter to attack a la gop and flush rate.
*Gop setting has an issue, there are dwords in there and it does different things based on them.
Looks like you're digging deeper dude!
Just a quick off topic question 1% (mostly for my own curiosity): In your opinion, what would be
your own choice if I asked you which feature excites you the most that has yet to be unlocked. Of course I base this on feature that you could potentially unlock based on theory. Just wondered how far you wizards aim to push this baby :)
Still inspired by your great work!
Cheers :)
Probably most exciting and hardest things are:
*Mjpeg -Kill H264
*Resizing/Cropping - No more Moire
*New Audio - incl headphone and patching it for flush.
Ps. I think gop not working... I tried several locations. needs more tracing.
I am excited for all of those things as well, guess I will just cheer you guys on from the side.
Still waiting to run ML on my 6D, just waiting for you guys to thumbs it up for us laypersons.
QuoteKill H264
Die h.264, die!!!
I got gop changing to work.... so far its not user proof... i.e. if you pick gop 11 for 24p it won't write. But other gops work like 24, 3, 6, ... basically divisible ones. Sound works too if you don't mess with flush rate... I have to work on a patch for that.
So now we can have some interesting scenarios.
24p rate control with long gop... so far only 24, 48 will break timecode (will patch and see what it does).
QP1 with flush and short gop... like 3. This may help with the skipping if encoder doesn't try to work on gop of 12 when frames are already written out at 4/5/6,etc.
Still have to find a way to undo and account for all-I mode where changing the gop would be ridiculous. It is written to metadata this time too.
*Gop 3 records without P frames.. only I and B
*Gop 24 seems to produce higher qps... most are 1 - 3 but overall rate is lower. This is supposed to be a benefit of longer gop encoding. Lower rate at same quality.
Quote from: 1% on April 15, 2013, 01:42:38 AM
Probably most exciting and hardest things are:
*Mjpeg -Kill H264
*Resizing/Cropping - No more Moire
*New Audio - incl headphone and patching it for flush.
Ps. I think gop not working... I tried several locations. needs more tracing.
Amazing!
I love it :) Reach for the stars brother! Reach for the stars ;)
If you manage to do either one of the first two I will personally build a statue in your honor.
Ok, got 113... stubs are all in different spots so it will take a little bit to get up to speed... but good news is you might not have to re-run a fir.. boot flag stays enabled.
Gop is up.. still 112, hopefully this the last 112 bin.
Not seeing jerking just loading CBR and setting flush of 6, gop of 3. This is at QP-5.. qp1 recorded like 200Mb/s and doesn't play back in camera.
Will have to check outdoors stuff when the main rig is free.
Shooting with transform8x8 flag to 1 for a bit... going to see if forcing it on every frame helps or hurts.
Hello everyone,
First, thank you all for your great work, I used to have ML on my 5Dmk2 and it is awesome.
I tried to install it on my 6D but I can't start it. When I update it says ML is installed, nothing happens when I restart.
Do you have any idea of what I did wrong?
I made the card bootable, copied all the files at the right places I think.
Thanks!
EDIT: I did that EOSCard utility thing again and it works now! I unchecked the boxes, saved, checked them again, saved, and it launches ML
Have to make sure eoscard isnt' copying files from wrong ML since it has that option in the new version.
Hmmm... so I'm playing with 6D 113 and it doesn't look good.
Menu and state object hooks are broken. Working on a fix for that.
Configs are loading but nothing is taking effect. Flush rate not working either yet the address is the same. So either this is some growing pains or canon fucked us. Wifi is still broken for me and now IPB rates are lower than ever.
Really hoping that something is set wrong... otherwise its back to 112.
I'm trying to D/G now... seems to be working. D/G is successful so going to see what happens as I can go back & forth... so can you.
I had a feeling they would >:(
Until the menu starts working at least 112 is the only option. I'll make it so that I can build for both and fix 113 hopefully. It didn't add or really fix anything which sucks.
I went 112->113->112 so as long as your battery doesn't die in the process I think its not that big of an issue. You would probably have to do 112 to set the boot flag either way.
It always seemed a bit suss to release a firmware update to fix a seemingly very minor issue.
Hi.
I can't seem to make audio remote shot work.
In live view photo mode it stays at 0/x, in video mode it works and triggers the recording. Am I doing something wrong or is it just not working yet on 6D?
May be a bug... it needs to turn on audio... I know how to do that but function may not be... will test/fix
Fixed!
ooh. Yay Audio remote shoot works.
Does that mean that audio tag, ie "set" after shooting, now works also?
If you can keep under a minute or so yes.... after about 2 mins it locks up. There is a state object for asif now. Playback I hacked to work well tho.
Whoa!
That's awesome.
Thanks for the fantastic work.
< 1 minutes is good enough for me.
I mainly want it to jog down brief information of the photo. like a phone number, or the name of a bird, etc.
Quote from: 1% on April 17, 2013, 07:25:07 AM
Until the menu starts working at least 112 is the only option.
Hi, I did a downgrade to 112, ML worked fine, but I just had a bug that I already got before with the 1st 6D that I got that was acting weird, when I am in movie mode, the 6D might turn off by itself at random moment (still rare but still not so cool).
I had peaking on (blinking dot) and zebra on, auto iso, ipb 24, I wasn't recording, I was just walking around in my home without looking at the screen , and it just turn off :(
do you think it's the peaking and zebra overheating the cpu or something ?
here is my log : https://docs.google.com/file/d/0B7_a_g2Q7BIra2FRWE5KaGZ0OGs/edit?usp=sharing
I've never had it turn off by itself... in fact had it running all night trying to catch some lightning.
1582: 2184.160 [DL] exitDL
1583: 2184.175 [DL] stopDL
1584: 2184.206 [DL] checkNormalSpeedADC : Last A/D (Max:2a3, Min:ab)
1585: 2184.380 [RSC] RealClearBusy(0x8000000) 0x8000000->0x0,0x0(0x0)
1586: 2184.788 [MC] PROP_LV_LOCK : LVLOCK_PERMIT
1587: 2184.942 [LVGMT] Start:0x2
1588: 2204.511 [DL] PROP_DL_ACTION (0)
1589: 2204.528 [DL] ReqStartDL
1590: 2204.568 [DL] ReceiveMessage : 0
1591: 2204.651 [DL] selectWaveType 0 -> 0
1592: 2204.670 [DL] executeDL
1593: 2204.695 [DL] startDL 0 0 0
1594: 2204.841 [RSC] SetBusy(0x8000000) 0x0->0x8000000,0x0(0x8000000)[0,0]
1595: 2204.884 [RSC] RealSetBusy(0x8000000) 0x0->0x8000000,0x0(0x8000000)
1596: 2205.208 [MC] PROP_LV_LOCK : LVLOCK_PROHIBIT
1597: 2205.363 [LVGMT] Ignore (st:1 ev:4)
1598: 2206.927 [DL] getPhaseDiff 0 -> 0
1599: 2207.021 [DL] startFreqChange : 1000000(usec) 943(usec) 1060(times) 0(times)
1600: 3206.637 [DL] EndChangeFreqCBR 1060
1601: 3206.687 [DL] exitDL
1602: 3206.704 [DL] stopDL
1603: 3206.735 [DL] checkNormalSpeedADC : Last A/D (Max:293, Min:aa)
1604: 3206.919 [RSC] RealClearBusy(0x8000000) 0x8000000->0x0,0x0(0x0)
1605: 3207.347 [MC] PROP_LV_LOCK : LVLOCK_PERMIT
1606: 3207.605 [BIND] ACTIVE_SWEEP_STATUS : 0 (0)
1607: 3207.630 [DL] PROP_ACTIVE_SWEEP_STATUS (0)
1608: 3207.643 [DL] TerminateDL
1609: 3207.676 [DL] ReceiveMessage : 2
1610: 3207.697 [DL] Terminate...
1611: 3207.709 [DL] dlMain : End
1612: 3207.727 [DL] localDeleteSerialIOChannelForDLIC
1613: 3207.747 [DL] localSendSerialDataToDLIC 0x2
1614: 3207.830 [DL] exitDL
1615: 3207.842 [DL] stopDL
1616: 3208.048 [LVGMT] Start:0x2
1617: 3208.358 [GUI] DlgActiveSweepExcute PROP_ACTIVE_SWEEP_STATUS[0]
1618: 3208.400 [GUI] StopActiveSweepExcute
1619: 3208.447 DL_ReportActiveSweepEnd Time(1366189587s)
1620: 3208.469 DL_ReportActiveSweepEnd OldTime(1366189577s)
1621: 3208.531 [GUI] GUI_SetASDoneRecord (T=1366189587, C=1)
1622: 3297.636 [CTRLSRV] WARNING: Cancel Timer Search 2
1623: 3299.918 [DISP] [Post]CtrlSrv ChangePhysicalScreen(ON)(0)
1624: 3300.069 [DISP] SetBitmapVramAddress BitmapAddr:0x40d3c008
1625: 3315.567 [CTRLSRV] WARNING: Cancel Timer Search 1
This is what happens so its something related to prop active sweep & gui. I'll have to see what that property does.
I see this: PROP_ACTIVE_SWEEP_STATUS:
// Let us know when the sensor is done cleaning
So... are you sure power save is turned off?
Actually I answered my own question from your log file:
emSlaveChangeCBR : AUTO_POWEROFF (1) also:
[GUI] PROP_ICU_AUTO_POWEROFF (1)
I think power off has to be disabled for every mode too. I have a different one for M mode I use for movie and P mode for photos.
ah ok thanx, I'll check this later when I get home.
Also when it shuts down... hit h/s it should wake up in theory. It will look like its off completely but its not. That log looked like a clean shutdown.
Quote from: 1% on April 18, 2013, 05:30:43 PM
hit h/s it should wake up in theory.
What button is h/s ?
I just checked in canon menu, it was set to turn off after 1 minute... I feel like a noob now... lol
I just discovered that new UI in ML menu when we press <Menu> button, it's pretty cool!
Thanx
I'll play around with bitrate and see if I understand it, I guess it must be explained somewhere in the forum... But where...?
H/S -> Half Shutter press
Maybe bug:
I'm on that 112 ML version that fixes the audio remote shoot.
My liveview no longer shows the focus peaking dots. But they are visible on the review window when I review a photo. The ML draw mode is set to all modes, not just review xor liveview.
Also,
attempting to 'Format' the camera results in a Beep, and a shoot_malloc failure on the format dialogue.
The "free memory" report window shows 6M as contiguious shoot_malloc and 113M total shoot malloc, 445K for malloc, 3050K for allocate memory and 540K for stack space.
the shoot malloc won't work till we enable chunking. ill check focus peaking.. maybe some eos m stuff got in
a 23 got changed to a 24, so fixed now.
Awesome 1% man.
I'll re-download and deploy on my camera. I'll report back any bugs.
At least I have "erase images" to use instead of "format".
btw: headway is made on wifi bug... its the cache hack we use to take over the gui task and let you press buttons for ml menu, etc.
without it no ml menu but also lv and wifi lv work. so need a new method to fix this.
113 is almost all up for me except this last part and ivaparm mode. once this bug is fixed i can see if ivaparams can be enabled/used on 113 or if canon screwed us.
Gday again.
I got your new version and it still didn't work.
For whatever reason, suddenly, (and on a release a month versions ago), I stopped seeing all ML overlays on LV or video mode. This means, none of the little battery icon, nor numbery thingos ML does, nor focus peak, nor nothing would display when on LV (even if 'draw on all modes' was on).
I thought the new version would fix that, but it didn't.
Then i started activating ML features on/off at random.
Eventually I touched upon False color, activated it, and went to LV ... and things were drawing again!
Then I turned false color off, and things (zebra,peak, etc) were still being drawn in the UI as they should be.
So, I think ML, at some point in time set some setting in the camera that stopped it from drawing over the LV. This setting, whatever, was not stored on the memcard since I've wiped that clean already. But, however, turning false color on/off made it all work again. There were no logs on the memcard after things started working again.
It might also be a canon problem. While holidaying I was on the "raw processing" menu of the canon menu, doing some 'raw processing' of an image I had just taken. And the camera froze. I re-batteried it and it booted ok, but then the LCD was refreshing slower than usual and I could see it flicker. I left the camera by itself turned off and later used it again and it was back to normal. Maybe when that happened some muck occurred. Dunno. I'm not too sure when exactly LV overlays died.
But its all back now.
Another thing, when using audio tags after a photo is taken the screen has a time-elapsed counter. if image review time is < "HOLD" then the screen will turn off after image review time but the audio will keep recording until i press set again. Minor issue. Ideally, the screen should remain on while recording.
I like the chipmunk-voice play-back-audio-recording feature.
Weird, I have no drawing issues. Lemme look around. BTW patched the voice tags to record forever without freeze.
Think wifi and LV sending is working this morning. I just tried both 113 and 112.
got lots done since yesterday, working on fixing up the audio stuff now.
Good news... bit rate hacks ARE working with 113. A lot of things moved up by 0x4... so I already see a bug.. the focus box isn't hiding... but working on it. Canon didn't mess with us after all...
Better news: I *think* i can set individual ivaparams. So far just reading source and have to work a method.
Audio *is* working with cache patches but there are a few new things we can try:
1. Use play_wav_data... oldy but a goody
2. Use the voi built in voice recorder
Top 2 may interfere with things and may be inflexible in terms of # of channels or 16/8bit..
3. Figure out state object for asif and give it the semaphores it wants so the patches are no longer needed.
Also:
Can make IPP or IBB encoding modes... IPP is a bit dangerous as you can't change stuff via canon menu when its on.
IBB is easy, just set gop to 3. Those P frames take up a bit of data.
*Foucs box isn't hiding when display filter (new peaking) is enabled.
1% - Just wondering, are the recent Autoexec's you have been uploading for firmware 112 or 113?
Cheers :)
All have been 112... I have not released a 113 yet. Working on a redraw issue then it *should* be good to go. I'll label the first with 113 and then stop supporting 112 I guess.
Quote from: 1% on April 20, 2013, 07:15:23 PM
All have been 112... I have not released a 113 yet. Working on a redraw issue then it *should* be good to go. I'll label the first with 113 and then stop supporting 112 I guess.
Great thanks man!
Just checking as I didn't want to go ahead with 113 until I figured it was a safe bet.
Also, I'm still getting to grips with the deeper side of ML and wondered how I give you a log if things go weird on me. Have been using it on a few gigs and weddings and getting quite a few crashes throughout the day. Not been using anything fancy, just focus peaking and zebras as far as I am aware (oh and the odd HDR here and there) but would like to give you the logs to contribute towards getting this puppy stable.
Thanks!
It should generate an assert or log001, 2, 3 etc. What kind of crash are you getting? Does it error 70 or freeze?
Movie or photo?
Video. Can't remember what the errors have been as I was in such a panic to get it working again I just pop the battery out and carry on as quick as I can but if I remember correctly it would stop recording and freeze with some error. Until just now though I have been using an Autoexec you posted around 03/03/2013 so I could just be due to it being a buggy version. I currently have my camera sat recording away with "restart movie" enabled so if I can replicate it I'll let you know. Fingers crossed your latest version should make a change but where exactly do I pull the log from if it doesn't?
Cheers :)
They should be in the root of the card.
That is an old version so I'd update. A month of changes went in since then.
Spent some time studying audio code in the 6d, it appears the code is almost identical to the 5D3, except for the addition of a new StateMachine, AsifState, and a slew of semaphore checks which is what's breaking beeps / test tones on the 6D. These semaphores aren't in the 5d3 so there's no issues.
Either we need to patch all of the semaphores out (last resort way, hacked), or study the state machine and see if we can inject some state changes required to stop Asif successfully.
Using the built in function to start/stop a beep works:
call( "StartPlayWaveData" );
msleep(5000);
call ( "StopPlayWaveData" );
but we can't play custom beep tones with this method, and my attempts to change the buffer used for the tone didnt' work either. This is how Alex implemented beeps, by studying this function and seeing how it works underneath this wrapper function (so he could pass custom tones to it).
Start asif works, but StopASIFDMADAC doesn't return, so at some point a semaphore check is timing out and causes err70. In StopASIFDMADAC, the call to (i think it's) TaskClass_TryPostEvent() returns 0 which causes the lockup. It returns 0 probably because the states are all messed up with AsifState, since we didn't trigger any state changes to start the wav playing.
I'm gonna try to work on this more this week, but at least we're making some good progress to understanding the real underlying problem.
This will really apply more to EOS M as I even have wav recording with video now. Yes I patched those semaphores and patched asif to continue correctly.
One EOS M this does NOT work at all and the camera hangs after finishing playing wav data or after finishing recording.
Need to add input volume setting and mic selection for separate wav as those aren't available from canon menu when audio is turned off.
Now only thing keeping me from an update is that stupid flicker bug... was it present on 112? Did you guys have focus box clear using display filters in movie mode? Did spot meter flash in movie mode?
First 113 is here!
I found some state objects have moved by +4... this may be a problem in other areas but I haven't found any more.
If you started with 113.
1. Downgrade to 112, set boot flag.
2. Upgrade to 113
If you started with 112 and boot flagged just upgrade to 113 since the boot flag will remain set.
DO NOT RUN BINS FROM 112 on 113 and vice versa. They will not boot and bad things will happen.
Everything *SHOULD* be working as in the previous version with addition of 2 features.
Raw Histo/Zebras -> Hot off the presses from a1ex
Wav recording. For when you want to modify flush rate and sound causes crash.
Please test if this works with external mic. I have to account for audio source if it does not. I'll also have to put an input volume menu item. For now just set it up in the canon menu, the settings *should* keep. Test it.
hi,
first thanks for the great job supporting magic lantern, i already use it on the 600d, so today i tried to install it on my 6d and i have a lot of problems,
so my steps are
1. formatted card with the 6d
2. card made dslr bootable with macboot
3. Download 6D 112 fir and copy to SD card
4. Download ML 2.3 make a folder on the card ML and copied all the files here
5. Download the latest autoexec.bin [113] Raw Histogram Wav Recording renamed it to autoexec.bin und also copied
on the sd card - root
so this is the way or?
put the card in the 6d and go for the firmware update, then i got the message ml installed , 6d turned off and then on but nothing happens, so i put the sd card out, battery out then battery in, camera is working, as soon as i put a sd card with ml camera is not working, is the sd card a normal sd card without ml camera is working,
so any ideas?
thanks!
drsmusic
Can't run a 113 bin on 112. Try the bin before and see if it boots then update to 113.
ok now camera is working but i have this message
ML DATA FONTS Retry
Pleasy Copy all ML Files,
so what files do i need? i read also the instructions on site 8 but i have still big problems,
thanks
drsmusic
You need the ML folder from 2.3 or the one I have posted. Also need the H264 configs in there.
ok now i made it! thanks for your help,
i took the 6d zip folder, there is a 6d ML Folder,
but i have some issues, when i pan the 6d and use ML live view i have some lines and delay's on the screen no smooth
liveview
also i have one message
B/ML / rec. ini
also when i am using the ml menu to set some points i am getting at once a liveview screen,
any ideas?
thanks
drsmusic
You have focus peaking display filter enabled and rate control encoder config is set to load at startup.
for me that have upgrade firmware 113 is enough put the new autoexec.bin [113] Raw Histogram Wav Recording renamed it to autoexec.bin in sd (not in ml folder) to have ml on my 6d? i tryen but i see black display and need take out battery to restart.. :(
may i need downgrade my firmware? how can i do , where i can find original 112 6d firmware please?
I think it's time to update the 1st post with a "101 ML on Canon6D" article....
I just want to remind you the "how big update !!!" the firmware 1.1.3 brings you: a bug fix to a date/time issue (i never had personaly). Great ! Canon, who cares about focus peacking ???
Steps for ML on Canon 6D with firmware 1.1.2 are:
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
- Get 6d-112.fir from:
http://bit.ly/ZgvGUf
- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini
- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card
- Put SD card in camera and update firmware while in M mode. Restart.
That's it.
so i have to downgrade to 112 if i want ml? if yes how cai do that?
Flash your cam with canon original 1.1.2 firmware first, then follow steps to get ML working on 1.1.2
thanks but where can i find 112 original _ and more what mean "flash"? :-\
Flash means update :D
New bins are going to be for 113 but at the moment you have to set the boot flag on 112 so you have to downgrade first to update. Those already using ML will have an easy time, you just upgrade to 113 and run the newest bin.
Hope to have a new 113 boot flag fir at some point. Has to be signed.
Updating the first post would be a good idea with repo link and eventually the new boot flag fir.
is limitlessasif.bin for 112 or 113
That is final 112.
Wav playback on 113 for some reason is sped up... on the PC in audacity the files play fine. Not sure what's up, tried to fix it but as long as it works on the PC its ok.
Hi
i cannot install ML. I have tried everything from above.
I am using 16Gb class 10 toshiba SDHC card.
I formatted it from the camera menu.
I downloaded every files from the links above - 6D000112.FIR and autoexec.bin-LimitlessAsif (renamed to autoexec.bin) to the root folder, four *.ini files to "ML" folder
I made card bootable - tried older and a new version of eoscard app. looked OK.
My Camera firmware-1.1.2.
So i put card to the camera, choose firmware update 1.1.2 ->> 1.1.2 = OK, firmware update OK, camera is back to canon menu.
I restart. Nothing. The same canon menu. Trash bin button doesnt work.
I tried over 10 times with no result. I am using ML 2.3 on my old 550d, there was no problem with installing it from the same toshiba card.
i googled some posts with similar problems but their solutions wasnt good for me.
Really interesting, any thoughts and ideas what i am doing wrong???????
Are you using a 113 bin on 112?
Hi guys, back from a long shoot. I have great news, using adobe speed-grade (I finally broke down and got the adobe cloud deal, I'm a student so this is awesome) you can really bring out the footage. It looks really good and because it works so well I would recommend shooting underexposed by 1.5 stops, unless there are no blown highlights. By doing this you save the highlight data and speedgrade can bring back the underexposed mids, then you just leave the shadows crushed for a cinematic look. For the highlights you simply lower the gain and gamma, and slightly increase the blur for nice highlight bokeh that has a smooth roll off.
I recommend setting the camera to 120 Mbit per second with initial qp at 2 or 3 on vbr. The result is that it is pretty reliable and very color gradable. I've gotten footage that looks a lot like the BMC. The BMC has 13.5 stops while the cannon has 11.3, so by under exposing by 1.5 stops you can bring the highlights just about to where the BMC is.
**Do not attempt this if you want to colorgrade inside you non-linear editor, use a dedicated colorgrading program, it makes a big difference.
For internet streaming I recommend setting the camera to 30-40 Mb/s, init qp at 4 or 5. it saves a lot of space and will look identical after compression on the internet.
And for presentations with projectors shooting 800x600 I recommend setting at 20 Mb/s init qp = 8.
Hope this helps a bit.
Ah.
So if I don't want ridiculously sized movies and have to recompress using handbrake later, I should shoot at initqp = a value near 10? and non HD.
That's awesome to know.
Yay.
Shoot with fixed qp = large movie.
Shoot with dynamic QP and you get a "normal" sized movie. So I just use rate control unless aiming for quality. I bumped up the max QPs to 30 actually.
720P is a moire mess and 60P.
Quote from: 1% on April 23, 2013, 02:02:57 AM
Are you using a 113 bin on 112?
"bin" you mean autoexec.bin?
I used limitlessasif.bin, I thought you said this is ok for 112
Quote from: kgv5 on April 23, 2013, 09:55:08 AM
"bin" you mean autoexec.bin?
I used limitlessasif.bin, I thought you said this is ok for 112
Gday.
You're meant to rename whatever bin you use to "autoexec.bin" before using.
Thanks for the reply but that was exactly what i did in the beginning. I renamed "limitlessasif.bin" to autoexec.bin, put it in SD root, no result :(
Well you have to load the developer fir from the first post in this thread to get it boot flagged. I think you're loading canon update I posted to let people downgrade.
You had the bin right the first time calling it autoexec.bin
Yeeeaahh, that was the problem. Now it works !!!! :D Thank you so much :D
Thanks for all the great work.
I have the latest autoexec.bin with the new firmware. I noticed HDR video is not working. Seems like ISO is stuck. Changing the ISO from canon menus/buttons does nothing. But you can change it in ML menu and there's no AUTO option there. I'm doing this in LV. Maybe I missed something?
You're right, its not flipping have to take a look... I bet its short by +4.
Yup that was it... I know display state is the same (checked, evf wasn't) .. hopefully malloc struct too.
Gradual Expo should be fixed from this too.
Anyone interested in whats going on with IPB and GOP and all that, take a look at this: http://dvd-hq.info/data_compression_3.php
Very comprehensive explanation for how video encoding works.
I have a question about the difference between rate control and vbr. How does rate control differ? CBR sounds like it already is rate control no?
CBR and setting init QP mean no rate control at all. QP is fixed to what you set it.
Rate control switches QP based on I think frame size and buffer usage tries to go towards target. Uses Min/Max QP
VBR switches QPS trying to stay within Min/Max bit rate at around target.
Find the latest streameye and you'll be able to see what everything is doing.
This is why VBR is freezy (at least from my testing).. .can't generate min freezes, can't limit itself to max stops recording (no buffer message just break).
RC + and sometimes fixed QP will just throw away data, I bumped RC up to max QP of 30 when I implemented flush rate as that is what it was doing. You have to edit the config as I haven't made a new zip yet. Won't do it under most circumstances but we're trying out extremes here :)
On 5d3 they aren't having the green frame/truncated frame problems at QP1 because of faster CF cards it seems.
Quote from: fotojohni on April 24, 2013, 04:33:19 AM
Anyone interested in whats going on with IPB and GOP and all that, take a look at this: http://dvd-hq.info/data_compression_3.php
Very comprehensive explanation for how video encoding works.
I have a question about the difference between rate control and vbr. How does rate control differ? CBR sounds like it already is rate control no?
Great read- thank you!
From what I'm reading the IPB method could be used to encode extremely high quality video, the problem is that the encoder memory is limited to the memory of all the frames in between the I frame and the P frame. Basically, it has to encode it all in a chunk like that because the B frames are based on the I frame (what comes before) and the P frame (what comes after). If you want higher bitrates the number of B frames needs to be limited so that the buffer isn't overfilled.
Ideally a simple algorithm could be implemented such that 2.0x bit rate would make IPB at half the number of B frames as the normal compressor aims for, 3.0x would be a third, while .5x could have twice the number of B frames, etc.
I really liked the 600d method of setting bitrates, but the IPB compression in this camera is also a huge advantage
From that article that I recommended earlier
"For high bitrates, it's usually preferable to use a GOP without any B-pictures"
How would this be done?
I made IPP it was way harder on the processor than IPB or even IBB. Its also not canon menu friendly.
2.0x 3.0x that is all bullshit. What it does on 600D is trick the frame prediction function to go for larger frames and thus lower QP. I found the real QP on 600D but digic V doesn't use the JPCORE any-more. Neither method will work, we're not tricking anything here just setting the actual parameters.
You can set a QP offset for the B frames and then they will encode at a lower (or I guess higher) QP than the I frame. Right now all the frames are the same and there is no offset.
If you shrink the gop it will skip the P frame and encode IBB. You can also increase the gop and that seems to lower the load on the CPU and produce lower rates at similar QPs.
Really we need to do a bunch of tests and do some sort of SSIM comparison on actual quality, esp vs the 422 input. What works on x264 or PC encoders may not apply or even degrade quality. Those are the breaks of reversing a closed source black box solution.
Can someone post me link for canon original firmware 1.1.2, seems impossible find it onhte web and i need for downgrade my 6d :-\ sorry if i m boring
thanks to all
Its in my repo. Boot flag and go back to 113. I'm done with new 112s. Hopefully someone signs a bin for me soon so we don't have to mess about.
Quote from: 1% on April 26, 2013, 02:02:08 AM
Its in my repo. Boot flag and go back to 113. I'm done with new 112s. Hopefully someone signs a bin for me soon so we don't have to mess about.
you are very patient 1% i m italian and maybe my english understanding is not so good...i download 6D-112 from page 1,
what i have to now?
i've to put it the sd directory alone or with ML and various .bin?
1. Downgrade to 112
2. Run "developer" fir and set boot flag like any other ML release.
3. Upgrade to 113
4. Make card bootable and add autoexec.bin and ML files.
i finally found on your repo thanks!
I have to throw them all in the post signature or something.
now that i have downgrade to 1.1.2 , i put on sd file of 1st page, ml folder and various .ini, but i doesnt appear correct , bad sign on lcd appear but not ml menu...what i wronging now?
You can't use 113 build on 112. If you never upgraded back to 113 you're stuck with the last 112 bin.
s thanks , so i have to easy upgrade to 113 from canon firmware and after install ml?
Quote from: savanaking on April 26, 2013, 05:04:58 PM
s thanks , so i have to easy upgrade to 113 from canon firmware and after install ml?
just install the firmware update from canon and put a prepared card back in with a 113 bin on it, no need to enable the bootflag again (it isn't affected by firmware updates)
canon firmware 113 and ml on same card together? :)
First get it working on 112 with a 112 bin. When it works THEN upgrade to 113 firmware and 113 bin.
Seems like 6d has it little bit worst then 5diii
Hmm... 1/2 the frame isn't gone on mine.
(http://imgur.com/ZsvFAxP)
*I've not tried on windows yet.
If 24 fps will happen somehow (fingers crossed), then ML will save Canon's ass from Cinema Pocket invasion! I really hope you guys make shit loaded of $$$ on your daytime jobs because this is so unfair! You guys work so hard and all you get is THANKS? Thats just f..... up!
happy that I make what I do and get time to work on ML. Could have it better but I know other people have it much worse.
33 frames before buffer fills and it stops.
These go in ML folder: lv_rec.mo and MAGIC.SYM ?
in ML/MODULES has to be caps or it won't find it.
where is the script to convert 422 to jpeg? Also, I got one MOV 422- how do I play that back?
Open them with gimp + 422 plugin or 422toimage. Not sure on how to play back the solid file movie yet.
Quote from: DTSET123 on April 26, 2013, 11:08:43 PM
Seems like 6d has it little bit worst then 5diii
This is because yo have taken it in photo mode with 5x or 10x zoom. It's only 1/2 of screen :-( but this type of pictures are zoomed :-).
Also 720P mode.
Can you tell us what's ur goal 1% ?
Get a 422 movie file 720p or 1080p ?
With a container or just a bunch of files in a sub directory ? then make a movie from those files on computer.
Would it be real 4.2.2 ?
6D hardware can handle 24x4.26Mb = 102Mb/s ? I presume he can..
Thanks
Quote from: 1% on April 26, 2013, 10:52:36 PM
First get it working on 112 with a 112 bin. When it works THEN upgrade to 113 firmware and 113 bin.
thank u , i finally see the green test on black ,done 112 and ml is enabled but menu doesnt appear after installation, can i upgrade anyway and after upgrade i can have ml menu too?
WOW! This is incredible! How likely does this look for us SD card users? Fingers crossed that we get clean HDMI eh! Hats off the ML team once again :D
Quote from: noisyboy on April 27, 2013, 04:37:11 PM
WOW! This is incredible! How likely does this look for us SD card users? Fingers crossed that we get clean HDMI eh! Hats off the ML team once again :D
Of course I mean RAW shooting.
Quotecan i upgrade anyway and after upgrade i can have ml menu too?
Since you have the boot flag set update to 113 then get a 113 bin and support files and set the card bootable. Either you're using a 113 bin on 112 and not getting a menu or you have the right bin but the card isn't bootable.
You can set it with eos-card, just don't let it overwrite the ML files. You can cheat and just load 2.3 and then overwrite the autoexec.bin + add the H264 files.
QuoteWould it be real 4.2.2 ?
Yup, its real 422... just can't push a high fps just like every other 422 recorder before it. It will shoot small burst though. I don't know what you want to use them for. DNG data as one file I don't know how to play back yet. Main benefit of this is we now have TCC to load other modules and also the silent pic DNGs.
I just updated to the newest 113 bin successfully and I get a "Scripts Dir Missing" message when booting. I added an ML/SCRIPTS directory and the message goes away so apparently there is something to goes there. Are there any files to put in that directory?
Thanks
Yea, just make a scripts dir. Eventually scripts can go in there. I opted for TCC instead of picoC but for some reason it still wants a scripts dir.
Thanks !!!!
Great work
Also, I guess this means you are a step closer to ticking these two off your list? ;)
RAW is very exciting but am I right in thinking that this is a step towards killing the awful Moire issues and you could potentially output 2k 4.2.2 files?
Well done to you and the team AGAIN! You are smashing it!
Quote from: 1% on April 15, 2013, 01:42:38 AM
Probably most exciting and hardest things are:
*Mjpeg -Kill H264
*Resizing/Cropping - No more Moire
Not exactly 2k, buffer sized. The raw isn't that big... but we're struggling for decent FPS on 720P. I think the moire is there no matter what. Take some raw pics when you see moire and check.
:-[ my 6d is not booting at all. no power at all. what can i do?
Pull out card... pull out battery.
Put back only battery. Try then... I think you cross loaded a bin there.
You should really implement the signature check... Look at reboot.c and fw-signature.h
I placed a function in debug.c to print the correct value ;) I
Does it skip all digic v if not fixed then? I put the signatures and IFdefed them for both 112 and 113 and the bins were still cross loading. I'll try to fix it as soon as possible.
Well sig still computes as 0x6B6A9C6F... its set to check it too unless I'm missing something. Same stuff defined for 650D as 6D and all. So maybe sig check is failing.
Hi, I'm now using ML with 113 and it looks like the ML menu flickers more often.
I have a feature request : wouldn't it be cool to be able to change the audio level easily with the Arrow/Set shortcuts?
Right now it only works for iso/kelvin , shutter/aperture, and LCD bright/saturation.
How about mic level/headphone volume (for 5DIII) ?
Quote from: 1% on April 29, 2013, 12:26:44 AM
Does it skip all digic v if not fixed then? I put the signatures and IFdefed them for both 112 and 113 and the bins were still cross loading. I'll try to fix it as soon as possible.
Well sig still computes as 0x6B6A9C6F... its set to check it too unless I'm missing something. Same stuff defined for 650D as 6D and all. So maybe sig check is failing.
IIRC it uses CONFIG_6D which is the same regardless of the FW version
Quotewouldn't it be cool to be able to change the audio level easily with the Arrow/Set shortcuts?
I could probably code this.. I can set input volume and ALC Off, right now its only set up for separate wav. I don't know if canon will override what I set when audio is enabled.
QuoteIIRC it uses CONFIG_6D which is the same regardless of the FW version
I made CONFIG_113 and CONFIG_112... it was ifdef'd out. Now I went back to only using 113 and only the 113 sig so latest bins should ONLY run on 113... but do they?
QuoteHi, I'm now using ML with 113 and it looks like the ML menu flickers more often.
Its redraw flood... constantly pops menu in the background. If I stop it from flickering then you won't be able to use scroll wheels in the menu. I didn't make this part: noticed it flickers more on every camera now.
Cool - I just had a lightbulb! Only thing stopping me getting a Mosaic Engineering filter was having to take it out for stills and soon I'll be able to shoot RAW without having to remove it at all thanks to the new developments with ML! Woohoo! The gift that keeps on giving ;)
Well the raw works now but like 2 second bursts. How is the moire in it? I haven't had any crop up that I could consistently test with.
In the latest .bin? Sweet! I shall have a go and let you know what happens.
Damn you 1%, just when I thought I'd get an early night you have to go and make Christmas come early *shakes fist* ;)
Quote from: noisyboy on April 30, 2013, 01:30:20 AM
I shall have a go and let you know what happens.
As in regarding the moire I mean.
Ooo! In fact - before I begin is this for 113?
Yep, you're good to upgrade now. No more 112. It will keep the boot flag.
Probably easier to upgrade on a non-bootable card to avoid the chance of cross loading bins.
Cool! Wish me luck :)
Good luck :)
Well you don't really need it, I went back and forth a few times. Just cross loading is annoying because you have to pull the battery, take out the card and then put the battery back in with no card. Nothing broke tho. You can also hold set while starting up and do magic off, then just turn it off after its finished and change the bins.
Amazing! And thanks by the way. Really :)
Will run a few tests in a mo.
Hey man. Any idea why AE might not be giving me the option to import the DNG's as a sequence? The box is grayed out and says "sequence not available"... Hmmm...
Ps. first attempt got me about 29 frames and now I cant seem to get over 15. Wonder if I changed something?
It does that for me too. I dunno why. Import all files as footage then create a comp out of them. I think you only have to select 1... not sure computer is being used. This morning I selected all and it made a sequence but it kept repeating.
Its dependent on res and card speed. 29 is average for me... more in 60P overriden to 24fps.
shot few short dng clips and payed with the footage in AF- wow!!! I am just blown away!
Adobe labs used to have dng importer for premier what happened with it? Why did they discontinued it?
I just tried wrapping with Ginger and it worked a treat. Hassle free :)
Only problem I have now is that it doesn't give me the Adobe Raw options :(
By the way just incase anyone was wondering the card UI tried with was a Sandisk Extreme 45MB/s Class 10. Will have another go now and play around.
That explains why I'm not seeing the import dialog: Ginger HDR
I think the problem I had getting lower frames captured was due to being in stills mode as opposed to movie.
Quote from: 1% on April 30, 2013, 02:34:47 AM
That explains why I'm not seeing the import dialog: Ginger HDR
Ahhhh! You think that being installed screwed it up? Was my first thought but thought it should affect importing but I figured it might be a problem as my PC recognizes them as Ginger files. Maybe I'm wrong?
I think photo mode is 30P by default.
I dunno, ginger is working fine, other people are complaining about seeing the dialog every frame.
Is it just me or does the image out of this seem really broken down? Especially in Cb Freq/Blue channel? Still - fun though :)
In fact it looks a bit like it's been up-sized from a lower res image. Like it's a bit pixelated. Not shitting on peoples hard work here or being ungrateful - I just wonder if it's something I have set wrong I guess. Does yours look fine?
I'll found out when I look at what I shot today. It does seem to have a little pink cast.. The stuff this morning had no pixelation. Post some examples of where you see problems.
Okay - problem solved. When importing my DNG files into After Effects they were looking... well... shit! When opening in Photoshop they looked sweet :) So basically I thought "stuff it" and removed Ginger HDR from my Plugins folder and BINGO, I can import DNG's as a RAW sequence and it looks great! It also brings up the Adobe RAW interface and I only have to set it ONCE. Not press Okay for every file. I am almost certain that the reason people are having problems with this is because they are highlighting multiple files and pressing import (which *will* cause that to happen) instead of just selecting the very first file of the sequence and checking the Camera Raw Sequence option at the bottom. I can pretty much guarantee that this clears up all the bother. Have fun :)
Cb still looks very mushy though. Even to the point that Neat Video only struggles to clean up just those frequencies.
Have found though that some of this is due to Adobe Camera Raw adding some sharpening.
I got the latest bin, how do you do the RAW burst ?
Turn silent pic. Hit q menu and select burst.
I think I have to pull ginger HDR too.. now the files are all blurry.
Thanx, mine too just records 29 frames.
These frame numbers actually sound very reasonable. When I first got my 6d I did some testing to see how fast I could shoot before the camera slowed down because it needed to write to the CD card (including some testing with different speed SD cards)
I suspect that what's happening is that right after the camera is turned on, when it hasn't done anything else, you can fit 29 raw frames in memory, and then after it starts working it never completely flushes those frames from memory (after all, you may want to bring them up on the back of the camera, view info, etc), and probably also stores a low-res jpg (for the camera display), so after you have stared shooting, there's only room for 11 raw frames in memory
I think it's memory fragmentation - the burst algorithm is not able to handle the fragments, so it just looks for large contiguous blocks.
One problem is that EDMAC (the thing that outputs image data) can only write the full image in a contiguous block (I don't know yet how to program it to skip lines or to switch chunks in the middle - g3gg0 has some ideas though). So, we have to reserve memory for full image blocks, even if we crop the image - otherwise the EDMAC will overwrite who knows what.
And the second problem is that, if you can allocate say 180MB, you only get it in small chunks (between 1-20 MB each).
If you also want to crop the image for faster write speeds, you either allocate memory for full image blocks (the safe route), or you can overlap them a bit (I'm doing that in the burst implementation). The simplest case is when you only crop the bottom part of the image.
Example: let's say a frame has 20 memory units, and we crop 10 units from bottom:
____________________________________________________________________________________________________
|memory chunk 1 |memory chunk 2 |
|*****************************************|**********************************************************|
|[frame 1][frame 2][frame 3]--unused---|[frame 4][frame 5][frame 6][frame 7]-------unused-----|
|[frame 1 from EDMAC] |[frame 4 from EDMAC] |
| [frame 2 from EDMAC] | [frame 5 from EDMAC] |
| [frame 3 from EDMAC] | [frame 6 from EDMAC] |
| [frame 4 doesnt fit] [frame 7 from EDMAC] |
| | [frame 8 doesnt fit]
|_________________________________________|__________________________________________________________|
So, in this simple example, 29 memory units out of 100 were wasted. If the chunks are small - say 1 or 2 frames per chunk - there will be a lot of memory wasted because of fragmentation.
Edit: just committed this explanation: https://bitbucket.org/hudson/magic-lantern/commits/4af113da963c
I'm pretty happy with the 720P burst... but this does suck. On 600D it only takes the first memory chunk so like 100+ MB is wasted.
600D is real simple.. only 2 chunks. 1 is 60MB the other is the big one. I wasn't aware this much was wasted on 6D too.
I'm glad to see there's some headway going on the 6D! Based off of other cameras with ML, do you guys anticipate ML ever cracking the moire issue? It really does suck to see it's downsampling from a sensor that isn't quite proportionate, like the 5DMK3. I think it's the one thing that is making me hesitant about my purchase between this and the 5DMK3.
Lol, some headway == pretty much fully working.
I don't know, someone shoot something really moire filled with raw and let us know. I did get some moire on the tracks shooting lvrec 422.
http://www.youtube.com/watch?feature=player_embedded&v=zAzvHm4q6r4
Hi
in 6d i have now 6D113NewLvrecPack and i cannot find burst mode, it was in previous version but now in silent picture when you press Q there is only on and off.
When i am pressing shutter button halfway, DNG are saving but slow - about 1 fps. Is it normal?
Thanks
EDIT: Ok, i found it, 6D113NewLvrecPack doesn't consit of "burst" under Q button (silent pictures on/off only), i had to add [113]RawBurst-Wav-PerfectRawHisto
Hello everyone,
I have a 6D and a 600D. I have a series of cards that I interchange between them. Until now I used all my cards with bootflag and ML because it works on the 600D and the 6D ignores it.
Now if I install ML on the 6D, what should I do? Should I have cards with ML for 600D and another set of cards for the 6D?
Focus confirmation had a regression. Fixed.
The unified bin would be too big at this point and the ml config settings don't match. Kind of hard to make the bin to where you won't spend an hour loading it.
Quote from: 1% on May 02, 2013, 05:23:28 PM
Focus confirmation had a regression. Fixed.
The unified bin would be too big at this point and the ml config settings don't match. Kind of hard to make the bin to where you won't spend an hour loading it.
And isn't it possible to have each camera model load a different ML version from the card with the right settings? Like a folder for 6D, another for 600D, that way I can use whatever card I pick from my bag. Maybe I'm not the only one doing this?
Also, all my cards are Sandisk Ultra 30Mb/s - will they work fine with higher bitrates and 422 footage?
I wish. Unified puts all the bins in one file and only loads the one that matches the camera. No account for folders.
On top of that if you wanted 6D + 600D it would alone be over 1 MB (2.3 was this big with all cameras) and the loader would have to go through that whole file and pick out the section that is 6D or 600D bin. Load times would be insane. I think ML might be going to single bins too so I'm not the only one with this problem.
Oh well, it's a shame but it's not the end of the world. Guess I'll have to label my cards then ;D
And what about the cards I mentioned? Are they good to use?
Do a benchmark and find out it will measure sustained write. I think these are UHS cards from what I read on google? My patriot card only does like 32-4. I'd like to find a cheap 128gb that will do the whole 50. Its not the sandisk pro.... its optimized for 208mhz and a rip. Hell... even the high 40s would catch us up to somewhere closer to 5d3 writing.
Quote from: 1% on May 02, 2013, 05:59:16 PM
Do a benchmark and find out it will measure sustained write. I think these are UHS cards from what I read on google? My patriot card only does like 32-4. I'd like to find a cheap 128gb that will do the whole 50. Its not the sandisk pro.... its optimized for 208mhz and a rip. Hell... even the high 40s would catch us up to somewhere closer to 5d3 writing.
I'm not sure what to think of this gathered info, but a test made in HD Tune returned 5500KB/s. Is this any good?
That is like 5MB/s very bad.... I think HDtune test is flawed... run the card benchmark in camera.
Quote from: 1% on May 02, 2013, 06:33:43 PM
That is like 5MB/s very bad.... I think HDtune test is flawed... run the card benchmark in camera.
I can't find that option on 2.3 on my 600D (haven't installed ML on the 6D yet)
2.3 is a bit old... 600D build with RAW is in the YUV thread, has the test.
Quote from: 1% on May 02, 2013, 06:44:21 PM
2.3 is a bit old... 600D build with RAW is in the YUV thread, has the test.
I got 12MB. It's a Sandisk Ultra, not a Sandisk Extreme. Well, that settles it. I'm going to have to buy some new cards.
Yup, just make sure they are UHS 100MHZ and not 208mhz... so those 90MB/s cards are probably out... at least "pro" ones from sandisk.
Quote from: 1% on May 02, 2013, 06:55:42 PM
Yup, just make sure they are UHS 100MHZ and not 208mhz... so those 90MB/s cards are probably out... at least "pro" ones from sandisk.
Ok, thank you!
Don't want more people to make that mistake and spend $200 on a card that does worse than $40 35MB/s offerings.
Personaly, Sandisk Extreme Pro 32 Mb (90Mb/s): 40.9Mb/s with ML benchmark
Thats a good sign... but sparedog got 30 something. Maybe we need a larger sample to find out the real deal.
Right now 1 for, 1 against.
I know SANDISK Extreme Pro 32 and 64 are different (but same commercial 90Mb/s). 64 SD handles higher bitrates.
From old times i was using them with my hacked GH2....
Another card: LEXAR 64 gb SDXC UHS-i, given for 30Mb/s:
33 Mb/s to ML benchmark
I think I passed on the lexar.... wondering about patriot pro EP... its a 90MB card.. wonder if it will crack 40.
Can you estimate the 6D real needs ? For HD1080p ALL-i for example.
When would we need more than 40 Mb/s ?
At least 30MB is nice... The highest possible is best esp for raw burst and YUV recording.
50MB/s is the interface limit.
You can tune bit rate to wherever it needs to be so you could even make it run on class 10 card and be better than canon stock IPB.
My cards benchmarks :
- 16GB sandisk extreme HD Video 30MB/s. = ML benchmarks 33MB/s
- 32GB sandisk extreme pro 95MB/s. = ML benchmarks 37,9MB/s
Almost the same result...
I'd like to know ML bench result of the sandisk extreme 45MB/s, anyone got this one?
QuoteI'd like to know ML bench result of the sandisk extreme 45MB/s, anyone got this one?
Yes, i have 128 Gb 45MB and it benches 35MB/s
the 95MB/s extreme is expensive juste for 3MB/s more...
too bad the 6D isn't 100% compatible with it! Canon doing that on purpose to stop us from getting crazy bitrates!
Anyone knows if an utility like streamparser (Panasonic's GHx hack tool) exists for Canon's MOV ?
It's a really nice tool to see what's in a movie (frames, frame drops... etc)
Would help "qualifying" SD cards for ML... no ?
Elecard streameye.
$1795 ! I should have specified a free tool !!! ;D
I'm googling, will tell u if i find something usefull.
-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
SANDISK ULTRA SDHC CLASS 10 32GB 30MB/SEC UHS-I
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
Sequential Read : 44.069 MB/s
Sequential Write : 11.137 MB/s
Random Read 512KB : 39.031 MB/s
Random Write 512KB : 7.748 MB/s
Random Read 4KB (QD=1) : 3.368 MB/s [ 822.3 IOPS]
Random Write 4KB (QD=1) : 1.158 MB/s [ 282.7 IOPS]
Random Read 4KB (QD=32) : 3.454 MB/s [ 843.3 IOPS]
Random Write 4KB (QD=32) : 0.641 MB/s [ 156.5 IOPS]
Test : 1000 MB [J: 0.0% (0.0/29.7 GB)] (x5)
Date : 2013/04/13 21:12:51
OS : Windows 7 Ultimate Edition SP1 [6.1 Build 7601] (x64)
I bought one such card (and 3 more ordered), tried to record video in ALL-I.ALL-I (normal to the native firmware 1.1.3) recording is not possible, constantly interrupted recording, a buffer overflow. I will return 3 cards ordered.
For comparison with the memory card Transend class 10 (normal, not UHS-I) 16 GB recording speed (Sequential Write) - 13-14 Mb \ s. By the way, the maximum bit rate of some of my files stored in the ALL-I - 95 Mbit / s. If we translate this into megabytes per second - 11,875. That is, card need write speed not less than 12 megabits per second.
Here is my workflow with DNGs:
Use photoshop image processor to convert your dng into jpeg. It will let you open the first image in photoshop raw where you can apply your color corrections. Then import in premiere, just select the first jpeg and check the sequence box. It will import as one move file. Then in project, right click and select "Modify"->"interpret footage" and set it to 24 fps. No need for AF.
Hello,
someone can give me a hint, where to download the old 1.1.2 firmware?
Can't find it on canon websites and also not here in the thred...
Thx! :)
Quote from: dimes on May 04, 2013, 10:53:09 AM
Hello,
someone can give me a hint, where to download the old 1.1.2 firmware?
Can't find it on canon websites and also not here in the thred...
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
look at the file 6d112.zip 8)
Thanks! :)
Gday.
Quick question:
- Has DotTune AFMA been fixed?
For me it goes and invokes the horizontal level display and then beeps and says restart and try again
- Has remote shoot been fixed?
- Has format been fixed?
It worked for a version and then it stopped working.
I'm still on the last 112 version I think. I won't upgrade till 113 unless I really have to. I like the idea of being able to set/disable the boot flag on the camera. The 'set' to override ML on bootup (at least on my current version) doesn't seem to always work.
My current ML version: autoexec.bin-LimitlessAsif
Thanks for all your efforts.
Afma works for me... it runs the grid and adjusts focus. It may have been broken on 113 until focus confirmation got changed to the correct value. Should have worked in 112.
Remote shoot? LV and wifi you mean? That's fixed.
Format can't be fixed, shoot malloc doesn't have a contiguous chunk big enough. Would have to use shoot_malloc(0).
It might work off and on if you get lucky with the memory.
*tried to fix it, next build try it I guess... well its going to be 113. I have gigs and gigs on all cards so I've never used this function.
Okiedokie.
Thanks for the status report.
Meh at Format then, it's not that important. "Erase pictures" is good enough.
Well next release you can try it, see if it did any good.
Gday
I'd rather not update to 113 until I can set the bootflag from on the camera.
However, my camera is going in for warranty repairs tomorrow. I'll tell Canon to NOT update the firmware. But if they ignore me, then, well .. I guess I'll try out 113.
Question: Is setting the bootflag through the camera body the same as setting the bootflag from eos card?
There are 2 "boot flags" one is for the card, kind of like making your hard disk bootable. The other is in the camera which tells it to load autoexec.bin if the card is bootable.
They can upgrade it all they want, all you have to do is downgrade. Right now the procedure is to downgrade, set boot flag on the camera and then upgrade. So you can still set/unset if you have 113, just more of a pain.
Need to make a new 113 fir to avoid this but I don't have the signing stuff.
Ah.
I understand. Thanks 1%
New nightly builds says:
fixed raw resolution and added footer per image file / movie sequence. Is this also available for 6D?
Based on some recent tests I can tell you that increased bit rate has a marked effect on the observed image quality. Best way to test this is with an image with a few flat gradients and a good amount of detail particularly in the shadows. You will see heavy macro blocking in the shadows and banding in the gradients. This is reduced continuously as you use higher bitrates, even the difference between 100Mb/s and 200Mb/s is going to show a difference in the banding and macro blocking.
The settings that I use for my camera right now for actual shoots where I need 100% reliability is IPB: VBR: init qp = 6 (any lower and its a risk of it blowing up) max bitrate = 10. This gives good results and has been 100% reliable thus far.
The biggest test on the encoder is to aim a something continuously moving with massive detail. The encoder will have lots of trouble. In low depth of field situations where one will be aiming at faces for example and other things that don't move erratically, one can easily push to qp=1 max bit rate =20 and still maintain reliability.
In other news I've found the best picture style. http://cinescopophilia.com/download-the-vw-158-canon-dslr-picture-styles-picture-profiles/
The CrookedPathFlat_3.0_HilightHelp.pf2 maintains excellent saturation and detail in the highlights. It's really amazing. I was shooting out my window on a sunny day and I had usable detail in the room and still had a blue sky outside.
Quote from: fotojohni on May 07, 2013, 02:26:56 AM
Based on some recent tests I can tell you that increased bit rate has a marked effect on the observed image quality. Best way to test this is with an image with a few flat gradients and a good amount of detail particularly in the shadows. You will see heavy macro blocking in the shadows and banding in the gradients. This is reduced continuously as you use higher bitrates, even the difference between 100Mb/s and 200Mb/s is going to show a difference in the banding and macro blocking.
The settings that I use for my camera right now for actual shoots where I need 100% reliability is IPB: VBR: init qp = 6 (any lower and its a risk of it blowing up) max bitrate = 10. This gives good results and has been 100% reliable thus far.
The biggest test on the encoder is to aim a something continuously moving with massive detail. The encoder will have lots of trouble. In low depth of field situations where one will be aiming at faces for example and other things that don't move erratically, one can easily push to qp=1 max bit rate =20 and still maintain reliability.
In other news I've found the best picture style. http://cinescopophilia.com/download-the-vw-158-canon-dslr-picture-styles-picture-profiles/
The CrookedPathFlat_3.0_HilightHelp.pf2 maintains excellent saturation and detail in the highlights. It's really amazing. I was shooting out my window on a sunny day and I had usable detail in the room and still had a blue sky outside.
Dude that was a GREAT post! Thank you :) Clean , concise and in a language I understand ;) Cheers! In return I hope to upload some ISO tests in a couple days (following a discussion in another thread with 1%) to see how much things have changed since the days of the T2i and "native" ISO's. Would be good to figure out what the "safest" maximum ISO to shoot at is.
On an entirely different note, I've never had so much enjoyment in grading DSLR footage as I have been doing with my 6D and VisionTech Picture Style (a slightly flatter version of VisionColor). These dudes really know what they are doing and have created a PP that holds onto skin tones like no other I have used! Oh and they're real nice people as well :)
Ps. Thanks for that link 158 Picture Styles!!! Holy Crap!!
I will most definitely check out the PP you recommend but honestly, the $6 or whatever it is for VisionColor is totally worth it and it's also now supported by FilmConvert too! Yippee :)
One thing I do wonder... Coming from a sound background, I have often wondered if it's possible to "Limit" the highlights so you could almost roll off at the top (before the image is compressed) so you could raise the gain and not clip the highlights? Wonder if this is possible with a custom curve?
That's basically what they are doing with the newest sensors for the Black magic. You can adjust dynamic range in camera believe it or not. The trade off is noise and less accurate color representation I think. They're getting crazy DR of 20 stops now, but the latest BMC is tuned for 12 out of the box.
There's a company in the Netherlands called Cmosis that is devoted to producing only sensors. They make all the sensors for Black Magic and Leica. They're making full frames now too, won't be long until we'll start seeing full frame cameras with crazy high DR in pocket cameras. It's pretty much a game changer. It would be cool if magic lantern could somehow team up and get one of those in a 6D. Would be pretty ridiculous.
Quote from: noisyboy on May 07, 2013, 03:28:07 AM
Dude that was a GREAT post! Thank you :)
I appreciate it, I'm glad you found it useful.
Quote from: noisyboy on May 07, 2013, 03:37:05 AM
The $6 or whatever it is for VisionColor is totally worth it and it's also now supported by FilmConvert too! Yippee :)
Wow, this is impressive. Thanks I'm going to get this.
I have noticed some repeating problem with latest tragic lantern 6D [113] LV_REC footers.zip. No matter what I do after pressing load module it freezes my camera. After module is loaded it's working for about one second ( I mean I can go up and down in menu with blue bar) and then is out - I have to pull battery out.
Did you update module + magic.sym. Its loading here.
Ok, sorry, my mistake. MODULES dir just went to the card's root, not to ML folder. Thanks, I am such an ass...
Every now and then I get "scripts dir not found" on boot. Anything to worry about? Using 113 from 28/02/2013 and scripts folder lies in the root of card.
Quote from: fotojohni on May 07, 2013, 07:39:23 AM
Wow, this is impressive. Thanks I'm going to get this.
Hope you enjoy it :) You'll might get the new CineTech PS for free too if you are lucky which is apparently based on Eastman 100T 5247 stock (cool to see Picture Styles finally being used to emulate different films stocks).
Modules and scripts go in the ML folder.
Quote from: fotojohni on May 07, 2013, 02:26:56 AM
The settings that I use for my camera right now for actual shoots where I need 100% reliability is IPB: VBR: init qp = 6 (any lower and its a risk of it blowing up) max bitrate = 10. This gives good results and has been 100% reliable thus far.
Hi, thanx for sharing your settings ^_^ , you say it's 100% reliable with your 6D but we don't know what SD card you're using, can you tell which SD card you're using and also its score with the ML benchmark please?
And thanx also for the picture styles!
Quote from: noisyboy on May 07, 2013, 03:37:05 AM
the $6 or whatever it is for VisionColor is totally worth it and it's also now supported by FilmConvert too! Yippee :)
I just got myself the Visiontech, I'll do some test with it and with Filmconvert too.
How to video recording in DNG format at 6d :'(
Sorry for bad english
Quote from: exflyer on May 08, 2013, 11:22:03 AM
How to video recording in DNG format at 6d :'(
Sorry for bad english
Hi
I assume that you are already using ML.
you need the newest tragin lantern 6D.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
There is an option "silent pictures"
set to burst, press shutter halfway - camera will record DNG's.
To get the maximum number of frames (in this moment on 6D i have 63 frames) in canon menu you need to set 1280x720 60fps, pictures qulity - no RAW, just JPEG, in ML menu set FPS override to 24 fps. With this settings you will get sequence of 63 1820x634 RAW DNG files. Than you will have to import this sequence to after effect and make some post.
silent pictures, of course :)
Kgv5, Thank you very much
Hi, I am on vacation and would like to copy the new files to my SD card, to fix the focus confirmation.
However, I have only my 6D and the usb cable with me, and access to a desktop computer without card reader.
Is there a way to overwrite the old with the new files? As you might know, when connecting the camera, it only shows
the picture files....Any ideas how to do it? Thanks.
That won't work :(
Your only hope is to get a reader somewhere.
Well, thanks for the quick answer. Now my last hope was when I put the SD card into a compact camera from Panasonic and connected it to the PC. Now I could see the ML files, but the the card was read only, how is that possible? (I checked the lock switch already.)
Dunno... maybe it doesn't allow writing to foreign cards.
Don't know if this was raised but using the zoom function with FPS override enabled makes the display screen go crazy. Sorry if that has already been brought up! Still using version from 28/02/2013.
Yep, saw that a few times. Maybe should disable FPS override in zoom mode somehow or have it change timing values when zoomed. Image size is different and so timings will be different.
28/02 or 28/04? The latter I think had af confirmation changed so no trap focus, etc.
Can you show a screenshot or a small video? It's probably from vsync.
Quote from: a1ex on May 09, 2013, 09:10:19 PM
Can you show a screenshot or a small video? It's probably from vsync.
Hey dude - not sure how to produce a screenshot so I'll just take a pic of the back of the camera with my iPhone and upload it in a sec :P
Zoom function when using FPS Override
http://postimg.org/image/awrvci3p3/
I remember the lines were changed for FPS overried to get rid of the lv_dispsize >1 deal. And by that pic its bad timings. I guess EVF sync could be not working for zoom but it does for LV_REC and get no corrupt images when zoomed in.
Timer A is 730 stock in zoom at 1080p24... 500something in regular lv.
Ah, FPS_TIMER_A_MIN or FPS_TIMER_B_MIN is too low.
Min is 706 in zoom mode for 1080P, lower than that and I get image collapse.
Should fix it, have to build and test:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/307c5c3dcd1936c9339e0d6cb797525d8971e4be
*Tested both modes, fix is up.
Totally have no idea what any of that means but it sounds great ;) Hope I've helped somehow!
Cheers :)
Well now people can LV_REC/dng with with zoomed image I guess.
Quote from: 1% on May 09, 2013, 10:16:11 PM
Well now people can LV_REC/dng with with zoomed image I guess.
Very quickly, thanks :)
Hooray - works great :) Cheers 1% :D
Oo - one other thing... Is it just me or is it a common problem that after a DNG Burst, once it's finished saving it automatically shoots another burst but then gets to saving about 2 pics before beeping and saying Saving Cancelled.f?
Ps. Something interesting I've just been playing with is the zoom function while shooting DNG Bursts. I guess you already know this being all badass and all but it's interesting that it works (while saving me about 25 frames at 258x963) and I guess what I'm wondering is - is this a direct crop of the sensor? As in there isn't much going on in terms of huge amounts of downsizing the image therefore giving us less moire/aliasing artifacts? I know it would be a pain in the ass having to be cropped in all that way for this to work but I think I could live with it on certain shots if it meant less horrific moire/aliasing.
If you move the zoom box down you get the rest of the height. So you can take real high res silent pic. For video that's not going to help much.
Burst seems to be working ok here, it didn't take any more pics after it was done saving.
67 frames... 720P24 (fast TV.. no dots in the dark)
Weird. It didn't do it at first but now it happens after ever burst.
I'll format the card and start again ans see if that fixes it.
As for getting the 67 frames, I'm just curious - what are you doing to "un-stretch" the images you get when shooting at 720?
Resize a little in after effects.
Maybe sticky half shutter is on? I'll see if it happens.. only burst mode? There are a few new ones now.
Is there a way to download DNG files directly from the camera to the computer?
Do they show up when you connect via usb?
Quote from: 1% on May 10, 2013, 05:05:23 PM
Do they show up when you connect via usb?
No, I do not see them
Quote from: 1% on May 10, 2013, 07:11:41 AM
Maybe sticky half shutter is on?
Turns out that I had trap focus set to continuous which was the cause of the problem. Thanks :)
So with resizing, I've kind of been doing that at the moment but I wondered if anyone had mathematically worked out what percentage it needs to be horizontally transformed by within a 1280 wide comp to get a "correct" image. I'll have a play and share my results.
Okay - so now I AM impressed!
Just been playing with the zoom function with DNG Burst and man - the image is amazing! Pointing at a load of trees I see no noticeable aliasing at all and post sharpening seems to work amazing on it!
If you don't see the pics when connected VIA usb then you have to use a card reader.
I've just been doing it by eye until it doesn't look stretched.
The images from 720p should be 16:9, so just enter that ratio in your image editor.
How do I find the location for CBR handler... I can't find the register interrupt function for edmac.. for write edmac I found some stuff but it only gave me FFXXXX and not names.
Quote from: a1ex on May 10, 2013, 06:17:13 PM
The images from 720p should be 16:9, so just enter that ratio in your image editor.
Sweet - so I guess just create a 1280x720 or 1920x1080 comp and just "fit to comp". Great - cheers a1ex and 1%. Again 8)
I don't know what improvements have been made in this area, but I want to do an update on the bitrates. IPB is not safe to use with ANY bit rate modification. It will drop frames when put under pressure, it happens very rarely, but I was photographing a tree on a windy day and everytime the wind blow and started rustling the leaves the read out would tickle 80%. I looked back at the footage and sure enough, it had dropped frames.
On All-i with the same settings it never worked for more than a second. So I turned it up a tiny bit to qp8 and it was pretty good, same sized footage though, which is a large ~1GB/min.
http://www.youtube.com/watch?v=wcY_WotjwLE
Yea, you're recording fixed QP so it will drop frames when it can't save them at QP whatever. Thats why I increased the max qp in the configs and don't do fixed QP in general.
Quote from: 1% on May 12, 2013, 03:39:38 AM
Yea, you're recording fixed QP so it will drop frames when it can't save them at QP whatever. Thats why I increased the max qp in the configs and don't do fixed QP in general.
Right, I just recorded two files, one minute long on RC at bitrate = 60 Mb/s. Calculated out that's exactly 450 MB for one minute. I looked at the files and sure enough, exactly 468MB and 471MB. What would be nice is if there was an RC where you set the target bitrate at something like 30Mb/s but have a max of something like 120Mb/s. I thought that's what VBR was doing because of init QP, I assumed it just aimed for the init QP then altered if it went over the max bitrate. I can imagine that kind of algorithm is ridiculously hard to implement on the fly though, and probably takes a few passes to get right, which is why arri, red, and BMC guys just say eff it and record the raw.
It's nice to be able to fall back on RC though if you just can't get the VBR to a nice number without it blowing up.
Run vbr without any overrides... try 30P if it freezes in 24 :)
The algos are all in the encoder part of the digic, I'd have to find where to manually set current QP, I don't know if you can just do it on the fly... that location is "init" or start qp and is probably only read once.
CBR config is for fixed QP/override like you're doing. If you look in the IVA params thread on 5d3 some "max" rates were found before it starts overloading the endoder/writing. That point for CABAC/CAVLC is different and ALLI/IPB/IBB too.
The way this works is QP is quality, so QP 1 can be 30mb/s to 400mb/s depending on your scene. Running fixed QP with VBR gives you the extra profile stuff and CABAC but when you look at the files, every frame will be at that QP you set. (Why I kept saying don't set initqp with configs) When the frame becomes like 2MB and the buffer gets hit with 24 of them, if the writing can't keep up the encoder drops frames. It can't really do anything else, it can't lower QP, you told it not to.
The RC will go up to 100MB/s and over if your scene is complex enough. Some scenes are just 60mb/s, they are static with not much going on. When you look in the file, QP is 1 already.
Tested it before flush rates and evened it out. The old one had a limited range of QPs and then when scenes got big and it ran out it did something similar (truncated frames). You can tweak the min/max to give you higher rates but I kept it 1-30 so it wouldn't run out, esp with upped flush rate.
BTW it is possible to get a clean file at ~300-400Mb/s fixed QP1, just its very hit or miss.
Funny: i quit the GH2, tired of looking for "the ultimate hack" to have a good compromise btw image quality and stability, telling myself, with new Canon's high bitrate encoding.... it can only be better out of the box and..... bitrate hacks are coming to ML too !
External encoders like the Atomos Ninja records at 220MB/s (4.2.2)
Canon 6D and 5D Mk III share the same bitrate of 90MB/s (4.2.0), no ?
How far could be pushed the bitrate on those cameras ? twice 90MB/s ?
With what kind of stability ? Would depends of memory card speed too, of course.
What's the "reasonable" goal ?
Reasonable is to just use RC and get 60-120Mb/s depending on scene. The SD card writes up to 50MB/s only.
Quote from: 1% on May 12, 2013, 03:53:58 PM
The algos are all in the encoder part of the digic, I'd have to find where to manually set current QP, I don't know if you can just do it on the fly... that location is "init" or start qp and is probably only read once.
well if you do find it this is what the algo could look like:
if (currBitRate > maxBitRate){
...currQP = currQP +1 //try to get below max bitrate
...//alternatively: currQP = currQP + (currBitRate - maxBitRate)/K (just to really cut it down if it needs to)
}
else if (currBitRate < maxBitRate & currQP > initQP){
...currQP = currQP - 1 //try to get to target qp
}
else{
...//it's all good (or maybe there could be a statement for a min bitRate if you wanted and it would bump the QP for that)
}
I'm not trying to be condescending or whatever (if this looks crazy just call me a moron and move on), I only understand the concept barely myself, and I have no idea how QBasic or whatever the firmware language is works. I just think that this is a good way to do it because generally, the camera gradually comes into a complex scene, when you pan or focus pull into it, it usually doesn't just happen and if the current bitrate was signifigantly higher than the max then it would need to really cut the QP fast, so there could be a scaling factor for that. It might be a good idea to start the currentQP signifigantly higher, like around 40 higher, than the target and then work it's way down, it would take not more than 2 seconds at 24p. I don't know, just a thought. I can't do any tests right now because I lent all of my cards and 600D out to a friend, I'll do more tests when I get those back.
That stuff is inside the encoder. Don't have that kind of control yet. If I find something like slice in this encoder I can do that.
Cheers for the bin dude. What do I have to do to test this baby out? Got it all loaded up but having a wee bit of bother finding the hidden treasure.
Ps. Please feel free to tell me to sling it if it isn't ready yet - I know you don't need the hassle of being tech support to the n00b when you're trying to get this done. I'm cool with that.
In fact I have it! Thanks again!
Load modules... its on the bottom of the movie stuff menu.
shot 8gb of 720p 24fps sample footage, working on processing this now I'll post it up when it's done. Just some night shots and random footage at a store.
One of the 960s is pretty much continuous. Sucks we're stuck with this crappy card speed.
Works great (as does the raw2dng extractor) so congrats :)
I take it the number of frames I'm achieving (59 at 30fps on first tests) is to do with the limitations of my cards read/write speed? Sorry if I misunderstand that.
Also, are there "optimum settings" for achieving longer record times as with the Silent Burst method?
I also noticed that the default frame skipping is set to 1. Does 1 mean it isn't skipping any or that it's skipping every other 1?
Finally, if I disable RAW and shoot YUV am I likely to achieve similar record times or possibly longer?
Again - this is incredible. To the many budget film makers like myself out there - you are all officially superheros!
Ps. It stopped recording automatically so didn't encounter any freezing.
Quote from: 1% on May 13, 2013, 04:35:23 AM
One of the 960s is pretty much continuous. Sucks we're stuck with this crappy card speed.
I posted just after you did so sorry I missed this as it answers one of my questions :)
LV_REC and Raw_REC are different... you have both. Raw rec only has settings for W/H
Ah! Super cool :) Cheers!
1320x540 seems to give me the highest continuous recording capability without interruption. And oddly, I get better performance with 1320x720 than I do with 1280x720. In fact I get about 17 seconds @ 25fps with 1280x720 and about 30 secs before I start getting the odd frame skip with 1320x720. This is pretty impressive!
Quote from: noisyboy on May 13, 2013, 07:08:31 AM
1320x540 seems to give me the highest continuous recording capability without interruption. And oddly, I get better performance with 1320x720 than I do with 1280x720. In fact I get about 17 seconds @ 25fps with 1280x720 and about 30 secs before I start getting the odd frame skip with 1320x720. This is pretty impressive!
Oh yeah - using Sandisk extreme 45mbs.
Shame there isn't a 562 as that would be 2.35 and I pretty much crop everything in anyway with what I would use it for. Ah well! It's only -22px 8)
Great job 1%
Night!
Is the maximum available res width 1840? It say's "can't do 1920".
LV_REC frames come out 1920. Counting this way its 1840. Zoom mode will do bigger.
6D
So LV_rec raw mode outputs 1920 and rav_rec 1840? What do you mean saying "Counting this way its 1840"?
After capturing raw I cannot use it second time until I reebot camera (I mean I am pressing "start" and nothing happens) is it normal?
Seems we have to find the fastest SD solution for a 6D to squeeze everything from the new RAW_REC module.
As far as we know maximum speed for the hardware is 50mb/s. 45mb/s card gives 32-37 so maybe we could speed things up a little bit with those 95mb/s cards.
Another thing which I think could help a little bit is to get 2,35:1 aspect ratio for the 1840 so we would need 780 pixel height preset (now 840 and 720 are the nearest). 780 pix height will give exactly 105% (from 1920x817) scaling in AE which shouldn't give much quality loss. Someone said before, that this is easy, just need to enter new values. I don't know how to do this so maybe someone could help.
Maybe there is a way to get continous (or couple houndreds of frames) 1840x780 raw recording (maybe with FPS override somewhere around 20-21 fps and twixtor).
How to use module RAW_REC
PS formatting sd card (in camera) disappear MODULES folder and SCRIPTS
Formatting will erase all data including ML files and folders.
Download latest build of tragic lantern [113]RawRec.zip
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
You have to put ML to your card once again, just remember to put MODULES folder into ML folder.
in ML menu go to M tab, press "load modules now"
now go to movie tab and go all the way down - there is RAW video option.
Is anyone here on this forum who has 6D with 95mb/s SD card in it?
Quote from: kgv5 on May 13, 2013, 11:44:43 AM
Formatting will erase all data including ML files and folders.
No, only MODULES and SCRIPTS, ML is saved
"in ML menu go to M tab, press "load modules now"
now go to movie tab and go all the way down - there is RAW video option."
Thanks for the answer :)
HD720p 14 bits 4.2.2 video with full frame pixel size... DXOMark will have to create a new category !!
You think we will be able to review DNG files on LV ?
The freezing is when it can't free the memory... sometimes it happens.
New memory detection is in the repo, will have to try it.
*also what sizes do you want to see added.
My memory card got trashed yesterday too so in the market for a new one that is faster than 32-35MB/s
Guys, I can not sleep now
I'm your fan
In mode "raw video", I have to get a single file or sequence files? And how to open these files (*.RAW)?
Sorry for the noob questions
Quote from: 1% on May 13, 2013, 03:21:45 PM
*also what sizes do you want to see added.
Good afternoon!
Having 1320x562 would be nice to try. Would be cool to see if I can achieve continuous recording on that.
Mad sunny out today so actually get to try it! Woohoo! 8)
Quote from: 1% on May 13, 2013, 03:21:45 PM
The freezing is when it can't free the memory... sometimes it happens.
New memory detection is in the repo, will have to try it.
*also what sizes do you want to see added.
My memory card got trashed yesterday too so in the market for a new one that is faster than 32-35MB/s
1%, thanks for the reply
Great thing would be to have the possibility to set picture w/h by hand from ML menu like was in LV_rec module. It would be very flexible and help to find maximum picture size due to card writing speed and due to framerate. I know, that this can be time consuming so just for now could you please add:
780 pixel height preset for 1840x780
1740 pixel width for 1740x720
Both are ~2,35:1 aspect ratio.
I think such settings could be somewhere between quality and performance.
If someone confirms 95mb/s SD card is faster than 45mb/s even by 10mb/s or so I will also buy one so please let us know :)
Well you can change resolution to the presets... if you can't you're using LV_REC not raw rec... some sort of 1 by 1 changing won't work tho.
I can add those sizes and we'll see what happens. If the ratio is wrong it will be pink.
Yes, I can like width , 640, 720, 1280, height 720, 840, 960 etc. I thought that with such flexible settings we could reduce or increase bitrate to make it exactly match the card speed. But maybe it is not really necessary for now, if you could add setting from above posts it would be great. Thanks
Thats all the ones you want? I can put a bunch at once.
static int resolution_presets_x[] = { 640, 720, 960, 1280, 1320, 1920, 2048, 2560, 2880, 3592 };
#define RESOLUTION_CHOICES_X CHOICES("640","720","960","1280","1320","1920","2048","2560","2880","3592")
static int resolution_presets_y[] = { 320, 360, 480, 540, 720, 840, 960, 1080, 1152, 1280, 1320 };
#define RESOLUTION_CHOICES_Y CHOICES("320","360","480","540","720","840","960","1080","1152","1280","1320")
Those are already there...
Ok, please wait a sec :D
EDIT:
Ok, we could have also:
1738x740
1644x700
1598x680
1504x640
1410x600
It might look kinda strange but these resolutions are 2,35:1 and can be simply scaled in after effects, we will see quality/writing speed ratio. Many thanks :D
Ok, will add them and post a module. I guess try and see if they're pink. Funny that 1738 is the size of 600D.
Does it work?
static int resolution_presets_x[] = { 640, 720, 960, 1280, 1320, 1410, 1504, 1598, 1644, 1738, 1920, 2048, 2560, 2880, 3592 };
#define RESOLUTION_CHOICES_X CHOICES("640","720","960","1280","1320","1410","1504","1598","1644","1738","1920","2048","2560","2880","3592")
static int resolution_presets_y[] = { 320, 360, 480, 540, 600, 640, 680, 700, 720, 740, 840, 960, 1080, 1152, 1280, 1320 };
#define RESOLUTION_CHOICES_Y CHOICES("320","360","480","540","600","640","680","700","720","740","840","960","1080","1152","1280","1320")
Quote from: exflyer on May 13, 2013, 03:51:08 PM
Guys, I can not sleep now
I'm your fan
In mode "raw video", I have to get a single file or sequence files? And how to open these files (*.RAW)?
Sorry for the noob questions
Hey buddy!
You need raw2dng.exe which you can find here: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Simply drag your recorded file onto the raw2dng.exe icon and it will automatically extract all your lovely little DNG's. Just make sure you have the exe in the folder you wish to extract them to as all the DNG's end up in the same folder :)
I have just been playing doing some dolly shots and in the motion I have noticed what looks like the odd single frame skipping every couple seconds. I'll upload and show you. It isn't the smoothest slide in the world but pretty sure I wasn't THAT bad :P
It looks almost as if the comp frame rate isn't the same as the footage but have double checked - both running at 25fps.
If you have to turn on raw mode you're in LV_REC and not Raw_rec
Quote from: 1% on May 13, 2013, 05:14:47 PM
Ok, will add them and post a module. I guess try and see if they're pink. Funny that 1738 is the size of 600D.
Does it work?
static int resolution_presets_x[] = { 640, 720, 960, 1280, 1320, 1410, 1504, 1598, 1644, 1738, 1920, 2048, 2560, 2880, 3592 };
#define RESOLUTION_CHOICES_X CHOICES("640","720","960","1280","1320","1410","1504","1598","1644","1738","1920","2048","2560","2880","3592")
static int resolution_presets_y[] = { 320, 360, 480, 540, 600, 640, 680, 700, 720, 740, 840, 960, 1080, 1152, 1280, 1320 };
#define RESOLUTION_CHOICES_Y CHOICES("320","360","480","540","600","640","680","700","720","740","840","960","1080","1152","1280","1320")
With new settings i get (for 23,976 fps):
1738x740 ~~100 frames
1644x700~~150
1598x680~~200
1504x640~~ over 500, i think almost continous
1410x600~~continous
Now I will check if there is a pink color. Write speed was about 38mb/s all the time.
EDIT: Its great, i dont't have to reboot, I can shoot one after another :)
Quote from: 1% on May 13, 2013, 05:39:27 PM
If you have to turn on raw mode you're in LV_REC and not Raw_rec
Not sure if that was meant for me but I'm using the mode found at the bottom of the movie stuff.
Here's what I mean anyway:
Didn't indicate any frame skipping when it was recording. Buffer seems fine.
Cheers.
*Learns he doesn't know how to embed vimeo* :P
Nah, not for you. Someone else was using LV_REC instead of raw rec... ok, going out to buy a new SD card. Samsung this time... hopefully performance is better than patriot for extra $10
Quote from: 1% on May 13, 2013, 05:59:51 PM
Nah, not for you. Someone else was using LV_REC instead of raw rec... ok, going out to buy a new SD card. Samsung this time... hopefully performance is better than patriot for extra $10
So maybe buy sandisk 95mb/s ;) , we would see how fast is it with 600d and 6d
We need to implement double-buffering to fix those double frames.
Quote from: 1% on May 13, 2013, 05:59:51 PM
Nah, not for you.
Ah - okay :)
Quote from: a1ex on May 13, 2013, 06:11:30 PM
We need to implement double-buffering to fix those double frames.
Is double frames the problem I'm having? Looking at my footage I guess it probably is as it doesn't look like frames skipping but almost as if their is a frame followed by another frame with half of the last frame and then another with the last half of the second frame. If that makes sense?
Yes, try a high resolution to see how skipped frames look like.
Quote from: kgv5 on May 13, 2013, 05:51:26 PM
With new settings i get (for 23,976 fps):
1738x740 ~~100 frames
1644x700~~150
1598x680~~200
1504x640~~ over 500, i think almost continous
1410x600~~continous
Now I will check if there is a pink color. Write speed was about 38mb/s all the time.
EDIT: Its great, i dont't have to reboot, I can shoot one after another :)
I have checked and only 1504x640 seems ok, the rest gives "after effects error: photoshop file format error, unexpected end of file (-39). (45::35), sometimes they open as corrupted and pink but after a moment they gives above message.
For 1504x640 AE scaling is 128% (to 1920x817).
EDIT: this was made with sandisk extreme 45mb/s
Quote from: a1ex on May 13, 2013, 06:23:49 PM
Yes, try a high resolution to see how skipped frames look like.
Will do boss! Back in a jiffy.
Maybe 2 jiffies.
On my Sandisk 32GB 95MB/s, i'm able to record raw à 1280x720 unlimited. 38-40 Mb/s displayed, about 15-20 frames skipped every 1000.
Wish a shorcut to start/stop RAW recording !
Quote from: teo770 on May 13, 2013, 06:43:51 PM
On my Sandisk 32GB 95MB/s, i'm able to record raw à 1280x720 unlimited. 38-40 Mb/s displayed, about 15-20 frames skipped every 1000.
I am interested in buying 95mb/s (i have 45 now) card so could you please check 1738x740, 1644x700, 1598x680 from the newest mode?
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Thanks
1840x720 had same (if not worse) frame skipping/doubling problems.
Same again shooting 1320x720
Forgot to mention - this is *before* any indication of actual frame skipping ;)
Quote from: noisyboy on May 13, 2013, 05:31:50 PM
Hey buddy!
You need raw2dng.exe which you can find here: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Simply drag your recorded file onto the raw2dng.exe icon and it will automatically extract all your lovely little DNG's. Just make sure you have the exe in the folder you wish to extract them to as all the DNG's end up in the same folder :)
I have just been playing doing some dolly shots and in the motion I have noticed what looks like the odd single frame skipping every couple seconds. I'll upload and show you. It isn't the smoothest slide in the world but pretty sure I wasn't THAT bad :P
Thank you very much.
Tomorrow - the day of the big test :)
6D and 5D mark III
Quote from: exflyer on May 13, 2013, 07:15:48 PM
Thank you very much.
Tomorrow - the day of the big test :)
6D and 5D mark III
You're very welcome!
Enjoy it dude :)
And GET SOME SLEEP! ;D
Quote from: a1ex on May 13, 2013, 06:23:49 PM
Yes, try a high resolution to see how skipped frames look like.
Just to clarify for you a1ex and 1%, (I'm sure you already know this but just incase you don't), there appears to be tearing in certain frames while it catches up with itself. Only slight but enough for it to jar.
Samsung UHS-1 64GB
No pro.... its like $200 and some people had issues with it. Need a card that can do 50/MBs and doesn't cost as much as a lens.
(http://imgur.com/PCX6UAN)
Speed about the same as the patriot... seems to keep it up longer though. 40MB/s my ass.
:( Not good, hoped, that we can get over 40-45mb/s but maybe samsung just screwed this up...
Someone should try sandisk 95.
I am testing 1504x640, looks very good, crop factor is 1.28 so need for wider lens ;) Probably for 2.35:1 aspect ratio this is the max res for continous recording. Is there something you could do 1% with the pink corruption in 1598x680 or 1644x700 res? It gave 100-150 frames so could be usable sometimes.
If its pink the sizes are screwed up... We need to find some resolutions that work and add those I guess.
Just wondered if anyone had yet tried the Delkin 633x? If not I'm gonna get one and see how it works out for us. Can't really afford it, I'm only getting it for the sake of helping make this better so don't really want to waste my money if this has already been tried. Thanks!
Sod it. I'm getting it :)
Question: when recording RAW, what tweaks are applyed to the video ?
- Lens distortion correction ?
- Vigneting ?
- WB ?
- Picture profile ?
In my opinion.... noone ? Am i right ?
I'm uploading to vimeo my 1280x720 raw converted to x264, the 1/4 upper part is showing some flicking... dont know why.
I just raw2dng the .raw file then imported the DNG sequence in AE and rendered it as x264.
The video: http://vimeo.com/66094923
I'll try to color grade it later but colors seems already deep to me.
Any of you guys finding that the aliasing and moire is worse when shooting Raw? Must be due to shooting lower resolutions. Seems to really stand out even after removing and Adobe Raw sharpening and taking contrast to -100.
Maybe black level and ML digic ISO corrections apply... I dunno about vignetting, check.
Would be funny if there was a moire cleaner in the path from raw to h264
Quote from: teo770 on May 13, 2013, 06:43:51 PM
On my Sandisk 32GB 95MB/s, i'm able to record raw à 1280x720 unlimited. 38-40 Mb/s displayed, about 15-20 frames skipped every 1000.
Wish a shorcut to start/stop RAW recording !
teo770 could you please make a 5min benchmark with latest ML build and your sandisk 95mb/s and post the results?
Help
raw2dng not working :-\
https://docs.google.com/file/d/0Bza6BOlmhEtkWlZNTk85b1NTWk0/edit?usp=sharing (https://docs.google.com/file/d/0Bza6BOlmhEtkWlZNTk85b1NTWk0/edit?usp=sharing)
Quote from: noisyboy on May 13, 2013, 09:53:14 PM
Any of you guys finding that the aliasing and moire is worse when shooting Raw? Must be due to shooting lower resolutions. Seems to really stand out even after removing and Adobe Raw sharpening and taking contrast to -100.
but lower resolution raw is a crop from 1080p so theoretically should be better than line skipping from whole sensor. In fact it depends how much you have to stretch the picture to cover your target resolution. Recently i was testing 1504x640, had to upscale it by 128% in AE to cover 2,35:1 1920x817. I will post this test later but in my opinion aliasing of the stretched picture is very similar to canon's full HD (maybe just a little worst than h.264 but not much). 1504x640 is more detailed for sure, obviously has a better dynamic range and gives continous shooting on 6D with 45mb/s card.
Quote from: kgv5 on May 13, 2013, 10:15:23 PM
but lower resolution raw is a crop from 1080p so theoretically should be better than line skipping from whole sensor. In fact it depends how much you have to stretch the picture to cover your target resolution. Recently i was testing 1504x640, had to upscale it by 128% in AE to cover 2,35:1 1920x817. I will post this test later but in my opinion aliasing of the stretched picture is very similar to canon's full HD (maybe just a little worst than h.264 but not much). 1504x640 is more detailed for sure, obviously has a better dynamic range and gives continous shooting on 6D with 45mb/s card.
I see what you mean but (and correct me if I'm wrong anyone) the 1080p image is already downsized with line skipping? Otherwise how are we ending up with a 1080p image and not an enormous image at 22mp?
Again - I ask this to try and understand, not that I think I know better :P
I'll upload the test I just shot and you can see what I mean about moire/aliasing. It looks riddled with what looks like false colour patterns.
Quote from: 1% on May 13, 2013, 09:54:43 PM
Would be funny if there was a moire cleaner in the path from raw to h264
Haha! Would be ironic for sure! :D
If you zoom in I think there are fewer line skips. Whole image is 2 or 3 "frames"
Quote from: noisyboy on May 13, 2013, 10:38:37 PM
I see what you mean but (and correct me if I'm wrong anyone) the 1080p image is already downsized with line skipping? Otherwise how are we ending up with a 1080p image and not an enormous image at 22mp?
Again - I ask this to try and understand, not that I think I know better :P
I'll upload the test I just shot and you can see what I mean about moire/aliasing. It looks riddled with what looks like false colour patterns.
I think that 720p is much more "line skipped" than 1080p, that's why aliasing and moire is so bad in 720p
Recording in lowest mode and overriding FPS to 24... I guess I'll see how it goes. Also wonder if there is any difference between 5x/10x zoom. 1320 x 540 was continuous for me. Have to see if it opens.
Quote from: kgv5 on May 13, 2013, 10:50:27 PM
I think that 720p is much more "line skipped" than 1080p, that's why aliasing and moire is so bad in 720p
Yeah I guess so :)
What my point was though is that our lovely little 6D's aren't the best when it comes to moire and aliasing even when shooting 1080 All-I so I wondered how it would be better because it's a crop of a raw image. I was led to believe that moire and aliasing are mostly caused my down-scaling the image which we are doing anyway where it's Raw or h.264. Once again I'm probably way off the mark but just found it interesting that the image I'm getting now seems to enhance it further.
The experts will set me straight I'm sure :)
Quote from: 1% on May 13, 2013, 10:54:51 PM
Recording in lowest mode and overriding FPS to 24... I guess I'll see how it goes. Also wonder if there is any difference between 5x/10x zoom. 1320 x 540 was continuous for me. Have to see if it opens.
I tried a 5x zoom and it came out all messed up (kinda like my display looked in real time when using the zoom function with Silent Burst mode before you fixed it. I know that with Silent Bust the 5x zoom images looked incredible. Hardly any aliasing or moire at all that I could see.
That's not to say it doesn't work. Will have another go.
Ps. Did you get a chance to try the tearing fix on 6D? Had a lovely sunset shot which was sadly a bit ruined by the bloody frame skipping thing :P
Raw 1280 x 720 25fps: http://vimeo.com/66094923
All-I does nothing about aliasing... just gives you inefficiently compressed frames.
The new module is double buffered so shouldn't tear anymore.
1320x600 works too... I used at 10x zoom. Don't see any fucked up frames out of the 321 I took. Have to test 5x vs 10x, maybe 10x really has more reach.
Quote from: 1% on May 13, 2013, 11:17:16 PM
All-I does nothing about aliasing... just gives you inefficiently compressed frames.
The new module is double buffered so shouldn't tear anymore.
Ah! The one you uploaded a couple hours ago?
In fact I think that's what I shot with just and still had tearing. Hmm... Let me just check...
Quote from: kgv5 on May 13, 2013, 09:59:15 PM
teo770 could you please make a 5min benchmark with latest ML build and your sandisk 95mb/s and post the results?
Sandisk SD 32GB (95MB/s)
Movie mode, global draw OFF
Write speed (buffer:2048k): 35.8MB/s
Read speed (buffer:2048k): 37.4MB/s
Write speed (buffer:1953k): 30.6MB/s
Read speed (buffer:1953k): 36.1MS/s
Write speed (buffer:3072k): 35.8MB/s
Read speed (buffer:3072k): 36.0MB/s
Write speed (buffer:2929k): 33.6MB/s
Read speed (buffer:2929k): 36.2MB/s
Write speed (buffer 4096k): 37.9MB/s
Read speed (buffer 4096k): 38.3MB/s
Write speed (buffer 3906k): 35.7MB/s
Read speed (buffer 3906k): 38.1MB/s
Write speed (buffer 16384k): 38.9MB/s
Read speed (buffer 16384k): 39.7MB/s
Write speed (buffer 15625k): 38.7MB/s
Read speed (buffer 15625k): 39.7MB/s
Thanks teo770
Damn, almost the same results as on 45mb/s sandisk extreme... :( So for now I think we cannot find faster solution.
Quote from: kgv5 on May 12, 2013, 11:50:57 PM
ML benchmark 6D + sandisk extreme 64GB 45mb/s
With my 45mb/s I even had 39,3 writing speed...
Lexar seems to have good cards too. I know a 64GB UHS-1 600x (90MB/s) exists (90 euros).
Need to be tested.
After.... the only solution is the 800x or the 1000x lexar CF cards.... in a 5D Mark III
:(
I think the quest for speed will end with the Sandisk....
Perhaps with a raw mode in 1200x665 24/25p scaled 1.6x we could get descent result ?
Try 1504x640 - scaling 1,28 to match exactly 2,35:1 without losing lines and continous shooting. Looks nice but damn, I cannot stop to think about 1920x817, that would be the ultimate solution
Quote from: kgv5 on May 13, 2013, 11:32:43 PM
So for now I think we cannot find faster solution.
http://www.amazon.co.uk/Delkin-32GB-ELITE-UHS-1-Memory/dp/B004VXK3PY/ref=sr_1_6?s=electronics&ie=UTF8&qid=1368482477&sr=1-6&keywords=Delkin+32gb (http://www.amazon.co.uk/Delkin-32GB-ELITE-UHS-1-Memory/dp/B004VXK3PY/ref=sr_1_6?s=electronics&ie=UTF8&qid=1368482477&sr=1-6&keywords=Delkin+32gb)
If we could have 50mb/s of real write speed on 6D we could use around 1700x720 which needs only about 113% upscale
Quote from: 1% on May 13, 2013, 09:54:43 PM
Maybe black level and ML digic ISO corrections apply... I dunno about vignetting, check.
Would be funny if there was a moire cleaner in the path from raw to h264
Vigneting checked !
If you place DNG files in Lightroom and apply some lens corrections (you have to manually select the right lens),
you will see Lightroom corect the pic for distortion and vigneting so the DNG are really RAW 100% pure.
I'll check for the PictureProfile tomorrow but i almost sure it's the same.
Aliasing.
Sad face :(
Would someone in a part of the world which can still see daylight be kind enough to try pointing their camera at a bunch of trees and grab a couple shots comparing the highest res Raw footage they can squeeze out vs. h.26? Otherwise I'll just have another play tomorrow :)
Might have to get a mosaic engineering filter after all!
Ps. YEP! Totally mean Lv_rec not lv_raw :-[
Quote from: teo770 on April 22, 2013, 01:47:19 PM
I think it's time to update the 1st post with a "101 ML on Canon6D" article....
I just want to remind you the "how big update !!!" the firmware 1.1.3 brings you: a bug fix to a date/time issue (i never had personaly). Great ! Canon, who cares about focus peacking ???
Steps for ML on Canon 6D with firmware 1.1.2 are:
- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software
- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip
- Get 6d-112.fir from:
http://bit.ly/ZgvGUf
- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini
- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card
- Put SD card in camera and update firmware while in M mode. Restart.
That's it.
does this still link to the current build? I want to join the testing on the current stuff.
Quote from: noisyboy on May 14, 2013, 12:34:35 AM
Would someone in a part of the world which can still see daylight be kind enough to try pointing their camera at a bunch of trees and grab a couple shots comparing the highest res Raw footage they can squeeze out vs. h.26? Otherwise I'll just have another play tomorrow :)
I would if I could figure out how to install it. Can I still follow the instructions from page 8?? lol..I've been following this thread for a while, but there have been so many changes I got kind of confused..
Quote from: electrichobo on May 14, 2013, 12:39:52 AM
does this still link to the current build? I want to join the testing on the current stuff.
Yup :)
1% - still definitely getting frame tearing/skipping with the latest lv_rec.mod dude. Just tried.
Quote from: OriginalClone on May 14, 2013, 12:41:17 AM
I would if I could figure out how to install it. Can I still follow the instructions from page 8?? lol..I've been following this thread for a while, but there have been so many changes I got kind of confused..
Follow instructions from just above you my friend!
How was that for timing eh! ;)
Thanks...I'll install now.
Note the top of the back of the bus. Cheers :)
Thats the digital pan. So it has potential... Does it tear at low res where the card isn't taxed? I surprisingly managed to convert the video on the laptop, lol.
Quote from: 1% on May 14, 2013, 01:36:46 AM
Thats the digital pan. So it has potential... Does it tear at low res where the card isn't taxed? I surprisingly managed to convert the video on the laptop, lol.
Lol! Thought it was gonna pan on forever! Looks promising :)
If it moves the zoom box it could pan vertically too.. so you could have programmed camera movements or something. Holding down h/s shakes the camera.
Quote from: 1% on May 14, 2013, 01:36:46 AM
Thats the digital pan. So it has potential... Does it tear at low res where the card isn't taxed? I surprisingly managed to convert the video on the laptop, lol.
Will test now.
Just waiting for my card to format. Thought I'd do a proper format of a card and compare before and after.
Was interesting to find that global draw really does affect recording performance. Managed to bump up to 400 frames from an average of 300-320 when using "some" combination. Will test again in a mo.
Quote from: 1% on May 14, 2013, 01:48:09 AM
shakes the camera.
Like a "camera shake effect"?
Quote from: noisyboy on May 14, 2013, 12:42:33 AM
Follow instructions from just above you my friend!
How was that for timing eh! ;)
Thanks! I get the success screen, but when I restart the camera I can't access the ML menu. I am supposed to press delete right?
Yeah - I might be losing it here but I think you have to re-start your camera in like M mode or a manual custom mode or something. This might be old school now I dunno :P
Quote from: noisyboy on May 14, 2013, 12:34:35 AM
Aliasing.
Sad face :(
Would someone in a part of the world which can still see daylight be kind enough to try pointing their camera at a bunch of trees and grab a couple shots comparing the highest res Raw footage they can squeeze out vs. h.26? Otherwise I'll just have another play tomorrow :)
Might have to get a mosaic engineering filter after all!
Ps. YEP! Totally mean Lv_rec not lv_raw :-[
Ugh - I am a complete moron! I mean raw_rec sorry :-[
Yes!!! ;D 8) thanks guys!
I smell digital image stabilization possibility with crop video.
Quote from: coutts on May 14, 2013, 03:31:19 AM
I smell digital image stabilization possibility with crop video.
Lol! I thought I'd get lynched for saying that! Thank god for you :P
Quote from: coutts on May 14, 2013, 03:31:19 AM
I smell digital image stabilization possibility with crop video.
Also - if you have an iPhone - you should check out an app called Luma. It does realtime software IS and does a pretty damn good job of it too! Might be a nice source of inspiration ;)
1% - Finally managed to irradicate the frame tearing/skipping by formatting my cards and just starting over with latest builds etc. Found that using x5 or x10 zoom still has this issue (and possibly a few other combos but have yet to test all) but either way - after a load of testing I have a working solution to shoot with (for now) ;)
I found shooting at 1504x600 is the highest I can shoot continously (bar reaching the 4GB limit - any possibility of that being lifted for tomorrow so I can do some
real testing?).
From there I find using Red Giant Instant HD does a nice job of upscaling the image to fit a 1920x817 (2.35) comp while doing good work on reducing aliasing from stretching the image. In terms of overall image quality - after a bit of de-noising an unsharp masking etc I can finally say I think you end up with a pretty nice image:
Ps. Card was Sandisk Extreme 45MB/s
Quote from: noisyboy on May 14, 2013, 06:31:13 AM
I found shooting at 1504x600 is the highest I can shoot continously (bar reaching the 4GB limit - any possibility of that being lifted for tomorrow so I can do some real testing?).
I just remembered when i received my last SD, it was not formated in FAT32 but in exFAT and it worked in the camera. It didn't worked in my TVIX media player so i reformated it in FAT32.
I've just read on Wikipedia that 4GB limit is due to FAT32 and the exFAT format wouldn't have this limitation......
(http://fr.wikipedia.org/wiki/ExFAT)
So... i'm trying.
:( "Movie stop recording automaticly" .... it doesn't sounds like a Canon text.... by chance, maybe a ML file size limit somewhere ?
Good to know: benchmark on card formated as FAT32 or exFAT is the same (0.1 difference sometimes)
Another thing to be verified, when formating exFAT the SD card, using higher cluster size make better benchmark.
Cluster size: 4096k => +0.3 to +0.5MB/s in benchmarks
I tested 1024k,2048k,4098k,8192k cluster sizes my best result (in bench) is 4096k
When recording RAW video @ 1540x600 24/25p, what buffer size is used ???
We could directly adjust SD card cluster size to better fit the buffer, no ?
teo770 did you try 1504x640? I tried and get continous recording, 40 more pixel and already in 2,35:1 so very easy scaling by 128%.
The same card and cam so check it out. I wil try with formatting card, maybe could squeeze a litlte bit more speed out of it.
Quote from: kgv5 on May 14, 2013, 10:19:50 AM
teo770 did you try 1504x640? I tried and get continous recording, 40 more pixel and already in 2,35:1 so very easy scaling by 128%.
The same card and cam so check it out. I wil try with formatting card, maybe could squeeze a litlte bit more speed out of it.
Just tried 1504x640, worked fine till the 4GB file limit.
This 4GB limit will now be a serious issue, cause at 1504x640, the 4GB is reached in 3.20 minutes only !
Other things:
How much frame skipping is important ? Could we have a live indicator of % frame skipped ?
Perhaps would be good to have (even as a debug option) live sensor/digic temperatures ?
Quote from: kgv5 on May 14, 2013, 10:19:50 AM
I wil try with formatting card, maybe could squeeze a litlte bit more speed out of it.
Can you confirm the gain with cluster size = 4096k ?
When benchmark starts, it seems to reserve 4MB, that's perhaps why the 4096k cluster size is ideal...
My steps:
1- format the SD card in ExFAT
2- EOScard
3- put back ML files
Quest for ultimate speed !
I remember couple days ago most pople wanted just 4-5 seconds of raw footage to be completely satisfied ;)
I will try formating when I come back home.
Imagine where we will be next month !
Just shooted a new video 1504x600 outside, just uploaded it.
Only modified WB in AE, set it to AUTO WB
During video, i changed aperture from f/4 to f5.6
Last frame (pinkish) is not due to crash, i just normaly stopped recording.
Double buffering did correct well the problem in the 1/4 upper part !
Tons of skipped frames.... how to reduce them ?
Makes me realise a few things:
- you need to disable the sleep mode !
- raw files would benefit a unique name (continuous numerotation) cause every cam restart cause the name restart to M0000.raw
- as for the regular recording, a log file with ISO, aperture, LENS NAME (cause we can remove disto and vigneting when importing in AE), would be great
There is already an indicator for # of frames skipped. You can write over 4gb files... try it.. maybe need to modify the converter too. I haven't tried yet.
When it reaches 4GB, movie record stops.
Quote from: 1% on May 14, 2013, 04:35:00 PM
There is already an indicator for # of frames skipped. You can write over 4gb files... try it.. maybe need to modify the converter too. I haven't tried yet.
On my couple attempts (been at work today so not much chance for testing) it stopped at roughly 4GB.
Just wanted to pop in and say that I got it working on my 6D and I am so appreciative of everything y'all are doing. Thank you for all of this!
Quote from: kgv5 on May 14, 2013, 10:19:50 AM
teo770 did you try 1504x640? I tried and get continous recording, 40 more pixel and already in 2,35:1 so very easy scaling by 128%.
The same card and cam so check it out. I wil try with formatting card, maybe could squeeze a litlte bit more speed out of it.
Did you manage to get 640 height dude?
I did but dropped frames incrases too.
I'm converting right know
Quoteraw files would benefit a unique name
What about DDhhmmss.RAW (day, hour, minute, second) ?
We are limited to 8 characters.
awesome !
Ok, try over 4gb now. I forgot to patch the limit.. only made written 64bit
Quote from: a1ex on May 14, 2013, 05:08:17 PM
We are limited to 8 characters.
It smells like FAT32 limitation no ?
Does it apply to exFAT ?
Wikipedia says you can't use long names on FAT32 without paying Microsoft but waht about exFAT ?
Quote from: a1ex on May 14, 2013, 05:08:17 PM
What about DDhhmmss.RAW (day, hour, minute, second) ?
We are limited to 8 characters.
I think a counter similar to how canon does it would be wise, does canon use the same image counter as images for movies, just with MVI instead of IMG? Maybe we could just affix RAW_ and use canon's naming convention (i think there's a property saying what number to use next).
Quote from: 1% on May 14, 2013, 05:30:43 PM
Ok, try over 4gb now. I forgot to patch the limit.. only made written 64bit
Hehe, working now (on my exFAT SD card) !!!!!!!!!! Congrats !
Waooo: 16.519.913Ko / 10692 skipped frames.
Stopped it cause of low battery ! Pretty sure new try it will feed the card completly
Quote from: a1ex on May 14, 2013, 05:08:17 PM
What about DDhhmmss.RAW (day, hour, minute, second) ?
We are limited to 8 characters.
or preferable timecode.
Nobody try on fat32 sd card or you'll corrupt the whole thing and have to format it.
Limit is actually 16GB.. .seriously someone wants bigger files than that... putting all your eggs in one basket.
Hi guys!
have a strange problem here! But firstly: I'm not a noob, used ML on 5dmkII, 7d, 550d and I've read all 55pages!
Yestarday, after hours of pain, I've installed ML on my new 6d, all ok! My problem is when I enable Focus peaking
the video on LCD is something like 10fps, recording is fine! So I disabled all overlays but Focus peaking, have the
same result! I enabled all overlays but Focus peaking and have no problem! My maybe only goal using ML is the
Focus peaking function! Please help!
Thanks and exuse my english!
Yeah, feel free to overclock the CPU and make it 3 times faster. Or optimize the algorithm, might be easier ;)
If you don't mind blinking dots use that... its real time.
Ok, so big question... what resolutions are working, what resolutions are not working (pink/dead). 1152x640 is continuous for me. Seems better than 1360x500... remember I've got the 10Mb/s slower card and I'm sure plenty of people do too. Also some more resolutions will probably help you even if you have faster cards.
I want to take out the ones that produce corrupted files and replace them with good ones.
Quote from: 1% on May 14, 2013, 07:02:40 PM
Ok, so big question... what resolutions are working
I'll join in the fun :) To make it less boring for everyone I'll take on 640xHight first. My first contribution is 1540x600 working perfectly with no frame skipping on a 45MB/s card. 139 other configs to go :)
Would you rather I test them out on a slower card first?
Speed is a card issue so as long as its readable... I just don't want dead resolutions in there that produce corrupt files and then someone shoots it on accident.
I know 1320 works... also 1280... what about 1598, 1644, 1738
Its a crop too so as long as a vertical or horizontal works at all it should be fine. Like if 1280x400 works then Xx400 should work, etc. Same for the reverse.. if 1598x400 works, should work with the other vertical resolutions.
Also what should be added...
1504x640 works as well
Hello everyone!
I just heard of Magic Lantern a few days ago, and got super excited. I read through the 55 pages and have now installed ML on my 6D! I will begin testing stuff as soon as I get a card reader that supports SDHC! For now I'm just testing with my 1GB SD card (with 500kb/s write speed...) that I only got to flash my Wii a few years back.
Will follow this thread closely and contribute when I can.
Cheers, and much <3 to the developers!
1598x600 - Could not Pars File (corrupt).
Hmm... Scrap that. Tried again to be sure and it worked. Wonder why this error occurs?
How fewer frame drops can we condider a resolution valid ?
Personally I think it's worth just getting rid of the completely buggered ones but that's just me (as in pink scramble frames).
1644x600 is buggered (so 1644)
So 1644 can go. And 1504 stay or go?
This is what I got so far
static int resolution_presets_x[] = { 640, 720, 960, 1120, 1136, 1152, 1200, 1280, 1320, 1360, 1440, 1504, 1536, 1738, 1920, 2048, 2560, 2880, 3592 };
#define RESOLUTION_CHOICES_X CHOICES("640","720","960","1120","1136","1152","1200","1280","1320","1360","1440","1504","1536","1738","1920","2048","2560","2880","3592")
static int resolution_presets_y[] = { 320, 360, 400, 480, 500, 540, 580, 600, 640, 680, 700, 720, 740, 768, 840, 900, 960, 1024, 1080, 1152, 1180, 1280, 1320 };
#define RESOLUTION_CHOICES_Y CHOICES("320","360","400", "480","500", "540","580","600","640","680","700","720","740","768","840","900","960","1024","1080","1152","1180","1280","1320")
What pink frames?!
1504 stay, please
Ok, 1504 stays... what do you want to add?
1738 is no good.
Sorry - when I say pink frames, they are only pink due to the color balancing in Adobe Raw but what I have been calling "no good" resolutions are ones that spit out this:
Quote from: kgv5 on May 14, 2013, 08:42:23 PM
1504x640 works as well
Dude, when you say it works do you mean continues with
no frame skipping at all?
What card? Cheers :)
Can you send me one corrupted video? A small one (30MB or so) should be enough.
1504x640, I tested this and some frame skipping can happen. should be good for slower action though, it gives continous recording so might be usable I think.
Card sandisk extreme 64gb 45mb/s
Quote from: a1ex on May 14, 2013, 09:58:47 PM
Can you send me one corrupted video? A small one (30MB or so) should be enough.
I have 2 levels of fucked up files at the moment. Openable but scrambled as above or completely unopenable (cannot pars file).
I'll send you a file you can open first.
Ok, so this is whats up with 64 bit.. ie over 4gb.
%d will only print integers so it ends up printing file size over all the integers.
%llu is supposed to work in this application but we don't have that macro. So I'm at a loss as to how to print everything w/ 4gb limit... the only other option is to just disable the limit and let the numbers max out after 4gb.
Ok, so I patched it to reset every 4gb but still continue. Still writes footer to the correct spot it seems. Now just need to recompile binaries for windows.
Quote from: a1ex on May 14, 2013, 09:58:47 PM
Can you send me one corrupted video? A small one (30MB or so) should be enough.
a1ex: http://ge.tt/4ro6teg/v/0?c (http://ge.tt/4ro6teg/v/0?c)
They look almost like the zoom did before you fixed it with this:
Quote from: a1ex on May 09, 2013, 09:53:18 PM
Ah, FPS_TIMER_A_MIN or FPS_TIMER_B_MIN is too low.
Prob has sod all to do with it though.
Incorrect pitch/horizontal resolution.
1504x640 no good on Sandisk Extreme 128Gb 45MB- skips
Quote from: 1% on May 14, 2013, 10:39:47 PM
Incorrect pitch/horizontal resolution.
Cool! Okay - so just to clarify, for now this is what we are calling a fucked resolution? :)
Frame skips are OK.. .busted frames like what you showed are not OK. So those come out.
Can you bench the 128GB card... I've wanted one for a while and seems like sandisk is the winner here. Wonder about patriot EP pro but the price isn't nice. So far regular EP and Samsung are duds.
Okay - deal 8)
Damn, almost the same as 45mb/s :(
Checked mine 45 again with LV photo this time:
best write speed was 38,6 for buffer=16384.
Carreful, bench values are different when in video mode. Don't know why.
And for now, frame skipping is ok but i shot threes in the wind this afternoon and..... i think you won't find it ok anymore !
Alex, 1%, what is the frame buffer size when recording raw video please ?
Select some huge resolution to find out.
OK, "threes in the wind": http://ge.tt/2UsyIfg/v/0?c
1504x600, just autoWB modification
The problem is in the lower right part. I don't think it's a macro block issue, rather too many skipped frames. Cause it happends on a regular basis. No ?
And in the center of the frame, i think it's a nice aliasing issue in the three ?
No problem with leafs at least !
I've had some luck using 720P buffer with override. I can record higher verticals with it. Its less crop too but I dunno how bad the moire gets on the raw.
So 1504 is hit or miss? The 1440 works... back to the days of HDV :)
Quote from: 1% on May 15, 2013, 12:11:33 AM
I've had some luck using 720P buffer with override. I can record higher verticals with it. Its less crop too but I dunno how bad the moire gets on the raw.
So 1504 is hit or miss? The 1440 works... back to the days of HDV :)
Nice work. please share your wisdom oh mighty sage :)
1504x600 works
perfectly for me. As in no frame skips, continuous recording with no tearing up to the 4GB limit.
Just to summarize my findings so far as it all got a bit lost in the thread:
*all based on tests with global draw off (for what it counts).
1540 = good (with no skipping up to and including 600(h)
1280 = good
1738 = bad (fucked image)
1644 = bad (fucked image)
Back on the testing now anyway (sorry, had to spend a couple hours with my girlfreind before she thinks I'm running off with a load of dudes on a forum).
Gonna try 1598(w) again now as had mixed results.
Quote from: teo770 on May 15, 2013, 12:01:38 AM
OK, "threes in the wind": http://ge.tt/2UsyIfg/v/0?c
1504x600, just autoWB modification
The problem is in the lower right part. I don't think it's a macro block issue, rather too many skipped frames. Cause it happends on a regular basis. No ?
And in the center of the frame, i think it's a nice aliasing issue in the three ?
No problem with leafs at least !
Great test dude :)
For me (and I'm probably just being picky here) I can see a lot of discoloration from aliasing artifacts particularly in the middle tree (with no leaves). Maybe it was bought out more in my own test by motion from the dolly pan I did?
Again - probably just bein' picky but I'm still convinced (if only a little) that the artifacts appear worse from RAW data. Probably because it's cleaner though and has lost no detail from the compression which would make it appear softer.
On the other hand, Amazing to see how much detail can be retained though :)
Anyone here with a Mac and Final Cut care to give this free anti-moire plugin a try? If it works (apparently it's rather good) I might look into reproducing the same results in AE. Guess it's just chromatic blur or something right? Might save a lot of our poor 6D footage.
The only time I wish I have a Mac :P
http://colorbyjorg.wordpress.com/plugins/ (http://colorbyjorg.wordpress.com/plugins/)
Wow! :o
http://youtu.be/JtOvf8oNi-U (http://youtu.be/JtOvf8oNi-U)
You don't need a mac... just put OSX on your PC.
My wisdom is I bought a crappy card and wondering if I should return it and just buy the sandisk... that extra 10MB really hurts.
Quote from: 1% on May 15, 2013, 01:36:33 AM
You don't need a mac... just put OSX on your PC.
My wisdom is I bought a crappy card and wondering if I should return it and just buy the sandisk... that extra 10MB really hurts.
So take sandisk 95, you will have possibility to test it with 6d and 600d, who knows, maybe you will find some way to put more data through SD controller...
The sandisk 95 isn't going to gain anything over the sandisk 45 here... maybe on the "8D" or some future camera that supports UHS-208mhz. I can probably get 2 64gb cards or the 128 for the price of a 32gb "pro". At that patriot's 50MB/s card seems worth trying... it would be like 45MB I guess... seems with these manufacturers its like take off 5 or 10 MB from the rating.
Quote from: 1% on May 15, 2013, 01:36:33 AM
You don't need a mac... just put OSX on your PC.
My wisdom is I bought a crappy card and wondering if I should return it and just buy the sandisk... that extra 10MB really hurts.
If I could achieve that without spending a week flattening my PC and then wanting to smash it to pieces cos the dual boot fails I would 8)
There just isn't enough time between jobs to tackle it.
Just bought the Delkin 633x 32GB. Let's hope they live up to being the "fastest SD cards in the world"! That or I'm gonna be pissed off that I just spent £60 on a pissing memory card :p
I'm looking at benchmarks and patriot EP pro 64 is like $69, Sandisk is $65... sandisk we see does ~39MB.. the patirot aparently does 41, lulz.
Just had some success in removing the horrible color artifacts from moire in post!
For anyone interested I basically found a plugin that would allow me to blur JUST the chroma and realised RE:Vision Smoothkit allows you to do just that! Works amazingly well! Of course you still have the problem with the pattern in luminance but I managed to get some very impressive results in just getting rid of the ugly-ass colours!
If anyone here is shooting 25fps - try 24 instead! Getting a much bigger performance!
Luuuuulz ;D
After all this time using ML I never knew I had PushWB!
Forget RAW... I'm made up now 8)
Ugh... I give up! Shot some random handheld shit earlier while testing stability and reliability etc and have just been going through it all.
This time I have absolutely no Moire issues and have brickwork AND trees in the shot! It should be horific! Soooooo Confused.
Uploading now: http://ge.tt/6jRVggg/v/0?c (http://ge.tt/6jRVggg/v/0?c)
I think having a properly exposed shot makes a huge difference! That or there really is THAT big a difference between shooting 1320x600 and 1540x600.
Damn it! Just realized there was a frame tear in there too! Just when I thought I had it all sorted :)
Quote from: noisyboy on May 15, 2013, 02:18:11 AM
Just bought the Delkin 633x 32GB. Let's hope they live up to being the "fastest SD cards in the world"! That or I'm gonna be pissed off that I just spent £60 on a pissing memory card :p
Great! We will see if there is a difference (so keep your fingers crossed). Run a benchmark ASAP
Hey guys, great work so far with the RAW video feature!
I was just wondering if this card would be suitable to use with the RAW function:
http://www.sandisk.com.au/products/memory-cards/sd/extremepro-sdxc-sdhc-uhs-1-95mbs/
I'm kind of new with all this stuff, so please bear with me a bit. Thanks in advance
Quote from: 1% on May 15, 2013, 01:06:39 AM
Yea. The memory thing is weird. On 600D I get 3X30MB buffers and I have 104MB.. on 6D its the same... but technically we should have 5 buffer stars there. If this is fixed I think a whole lot more resolutions will be usable.
I remember in some of the earier builds there were 4 stars... I think so but i am not quite sure.
1%, so with 3 stars 6D isn't alocating 152 mb like in the old LV_rec module?
I know, that these are different modules - I came back to the old LV_rec and it's only utilizes about 30mb/s write speed instead 38-39 like raw_rec.
So correct me if I am wrong: for 6D
old LV_rec allocates 152mb and writes ~28-30mb/s
newest raw_rec allocates 104 mb and writes as we know 38-39 mb/s.
Is there any way to somehow combine those things? Or maybe they already are...
One more quite dumb question, devs, sorry for that - LV_rec has a raw 1920 res width. Raw_rec has max 1840 (it says that can't give more). Despite of low speed card couldn't we use 1920x800 in a 6D even in shorter sequences? I know, we can always use older LV_rec but maybe with 38-39mb/s we could get ~100-120 frames (now ~70 frames).
Thanks
Quote from: noisyboy on May 15, 2013, 06:37:47 AM
Ugh... I give up! Shot some random handheld shit earlier while testing stability and reliability etc and have just been going through it all.
This time I have absolutely no Moire issues and have brickwork AND trees in the shot! It should be horific! Soooooo Confused.
Uploading now: http://ge.tt/6jRVggg/v/0?c (http://ge.tt/6jRVggg/v/0?c)
Did you import it with After Effect ?
If so, you can apply lens correction (distortion and vigneting) when Camera Raw opens the 1st DNG
Quote from: teo770 on May 15, 2013, 01:50:35 PM
Did you import it with After Effect ?
If so, you can apply lens correction (distortion and vigneting) when Camera Raw opens the 1st DNG
Yo Teo :) Yeah I always start with Camera Raw in AE. I don't think lens corrections are going to do much in terms of helping moire and aliasing though.
Just about to go out and shoot some tests to compare moire between 1320 and 1540 width as from what I can tell in the two previous tests this is the only real thing that was different.
Quote from: kgv5 on May 15, 2013, 09:43:15 AM
Great! We will see if there is a difference (so keep your fingers crossed). Run a benchmark ASAP
Yeah man - fingers crossed 8)
I don't know how you guys do but personaly, i have "skipped frames" in every definition
even at 1152x500 (<20MB/s)
:(
Are my sandisk cards too old ? (SD Extreme Pro 95MB/s)
You really have 0 skipped frames (1st line when recording) at all ?
Yea, some resolutions are skip free for me even at 30MB/s. I wonder if instead of fps override it would be better to skip frames for something like 60P to get a 24fps rate.
I did notice card perf drop a little after a few writes. LV_REC and raw_REC use different methods for both memory and size.
Quote from: 1% on May 15, 2013, 03:07:24 PM
Yea, some resolutions are skip free for me even at 30MB/s. I wonder if instead of fps override it would be better to skip frames for something like 60P to get a 24fps rate.
I did notice card perf drop a little after a few writes. LV_REC and raw_REC use different methods for both memory and size.
Speaking of fps override dude - if shooting selecting 24fps in canon menu to shoot 23.976 - do I have to use fps override to achieve true 23.976? It's just that when extracting with raw2dng I'm seeing that it it says the frame rate is 23.970. I know it's not off by much but for consistency and audio syncing etc it would be cool if I know I'm getting it right in camera to begin with.
Thank man!
Ps. Like the idea of frame skipping 60p footage. Will give it a blast!
I think at 23.X its going to be 24 regardless... its kind of like a film camera there is one frame per file. I guess you could slow it down to 23.x or speed it up to 24 and it shouldn't make a difference
Good news: no skipped frame anymore in 1504x600
I forgot to set Picture quality in Canon menus ! Set it to jpeg S3
Inside or outside, only the 1st buffer * blinks, no frame drop.
I presume the 3 * represents the 3 30MB buffers ?
Know.... i'd need a minimal audio track (8bit 22 Khz ?) ! To synch audio easily with external recorder
And a timecode, start/stop recording shortcut.... etc
Will write my big list to Santa !
Record wav with it and see what happens... We should have more buffers... working on it... I swear S3 lowers total memory amount tho.
Quote from: 1% on May 15, 2013, 05:16:22 PM
I swear S3 lowers total memory amount tho.
which one do you recommand ?
Quote from: teo770 on May 15, 2013, 05:13:25 PM
Know.... i'd need a minimal audio track (8bit 22 Khz ?) ! To synch audio easily with external recorder
Or you could sync with something visual that makes noise like a clap, no? :)
I've enabled 4 buffers now for 6D :)
i'm going to try for 5 but doubt the math works out.... so you'll enjoy some longer recording I believe.
The recording is better with larger frames now.
cool ! will try it.
Actually, Wav record doesnt work with RAW recording.
For sound synch, i'm using a "cliquet" from WWII.... very little, discret, "hearable" at 1 mile ! So i need a minimal cam soundtrack...
Perhaps, with the 4th buffer we would find place for a crappy soundtrack ?
Meanwhile, i'll use my big clap :)
The wav will take away writes no matter what :(
And for now image is the top priority, i agree !
Quote from: teo770 on May 15, 2013, 05:31:43 PM
cool ! will try it.
Actually, Wav record doesnt work with RAW recording.
For sound synch, i'm using a "cliquet" from WWII.... very little, discret, "hearable" at 1 mile ! So i need a minimal cam soundtrack...
Perhaps, with the 4th buffer we would find place for a crappy soundtrack ?
Meanwhile, i'll use my big clap :)
I knew I was onto something with my whacky "beep on first frame" idea ;)
Quote from: teo770 on May 15, 2013, 05:13:25 PM
Good news: no skipped frame anymore in 1504x600
I forgot to set Picture quality in Canon menus ! Set it to jpeg S3
Hmm... I haven't been doing this and have been getting that res with the card I have anyway. Wonder if this will make a difference to me...
Well done though! Enjoy it :)
Quote from: teo770 on May 15, 2013, 05:13:25 PM
Good news: no skipped frame anymore in 1504x600
I forgot to set Picture quality in Canon menus ! Set it to jpeg S3
Well blow me down! Good discovery! Just managed to push my 1540x640 recording from recording 2000 frames to recording up until I hit the 4GB limit with NO frame skipping! Could probably have gone on a lot longer too!
Exciting! Thanks dude!
Confirmed! there is a difference with S3 setting, 1536x640 is now continous :D
For realz? Maybe that path is less intensive on the CPU? I don't see a single MB gained from S3.
1320x540 is working for me in 640x480 mode + S3 only using 2 bars of buffer @ 28MB/s write
Quote from: noisyboy on May 15, 2013, 05:54:47 PM
Well blow me down! Good discovery! Just managed to push my 1540x640 recording from recording 2000 frames to recording up until I hit the 4GB limit with NO frame skipping! Could probably have gone on a lot longer too!
Exciting! Thanks dude!
In fact - that said - just changed back to L-Jpeg and am getting same results. How very strange.
I must have changed something else between last night and now coz yesterdays testing gave me a much lower performance. Maybe even I have a different (but same model) card in? Back to the testing
My best perf at the moment: bullet proof 1504x600 24p, inside and outside 100-6400 iso, from f4 to f22
with jpeg only both L or S3, no RAW at all, Global draw ON, with focus peaking.
About vignetting in AE, i'm dumb ! We are using center part of the frame ! Useless !
Update: with the last raw_rec.mo - buff, 1536x600 24p is rock solid too
In my cam, 4th buffer is 14Mb
Quote from: teo770 on May 15, 2013, 06:40:04 PM
Update: with the last raw_rec.mo - buff, 1536x600 24p is rock solid too
In my cam, 4th buffer is 18Mb
Sweeeeet! Gonna try that :)
We are not far away from 1536x640 (2.35 aspect ratio) because frame drops are only 50 per 1.5GB !
(turned off EVERY canon enhancement)
update: 4th buffer is somtimes 14, sometimes 18Mb
Sometimes its 14, sometimes 18.
What would be good to do is allocate 4x30MB and then allocate 10MB at the end. Right now its doing 10MB, 30, 30, 30, 14/18.
splitting buffers in 20 or 25 Mb is possible ? (to try)
or even in 10Mb chunks
I missed a bit of discussion. Prompt, Magic Lantern already "learned" to write Jpeg sequence, instead of RAW?
Hey.
I can't figure out how to use the raw_rec module. I can click "load modules" in the ML menus, and I see it in the list. But I can't configure it or use it. What am I missing here...?
Thanks!
EDIT: Figured it out!
You could but you want the biggest ones possible so that it writes faster.
So latest I shrunk the double buffer to 5MB as that is the largest likely frame... then first time I get 4x30MB and everything is great... second time it goes down to 28MB chunks and only makes 3 of them. WTF.. like its not being freed properly?
Allocating 4MB gives us back 30MB buffers consistantly... I dunno if that covers bigger frames though.
Frames seems to be around 1.5Mb
An ideal 1920x1080 frame would be 2.1Mb max, no ?
Not sure, take one and check. You can try the latest module and see if it speeds things up... For 600D this doesn't work so well I think. 10MB left over only so no difference. But on 6D we're now using most of the mem. We'll never record at those bigger ~2k frames anyway without skips.
Dude - would you mind popping the now module in a url on ge.tt or something? Can't get at it for some reason but have no problem with the others. Thanks :)
God knows what I've changed now but seem to have lost the ability to record up to the 4gb limit on 1540x640. It's back to an average of 2000 frames. Gonna start logging everything now.
Last "raw_rec.mo - 4 buffers, no worries":
1536x640 is ok till 1750MB, after that, all buffers full, frame drops begin.
So better or worse... seems better on my end.
http://ge.tt/9Co39kg/v/0
Of course better.
Tell me, when recording RAW, which parameters can you modify/adjust appart buffers size and resolution ?
Quote from: 1% on May 15, 2013, 07:50:27 PM
So better or worse... seems better on my end.
http://ge.tt/9Co39kg/v/0
Will try now :)
This is messed up though.
Seriously don't understand this but basically when I put the card back in my camera with the "raw_rec.mo - buff" version it gave me much less performance in recording 1504x640 (which I could do previously since this afternoon but now get about 300 frames). So anyway, just for shits and giggles I tried to record 1536x600 and it allows me to pretty much hit the 4gb limit.
Would love to know what gives
Buffer is in raw_rec.c... resolution is there too. Also finding that certain frame sizes will record better and there is something happening at 1.5gb.. drops write by 2MB and then skipped 14 frames after recording many many with only 1 buffer bar.
I was definitely not doing 1320x540 last night with this few skips.
1280x540 = buffer full and many dropped frames... perhaps we need an indicator for frame size like LV_REC had not just predicted speed needed. That way we can find the best frame file size to write. I have a feeling after trying different allocations for double buffer that even or specific sizes will do better and its not just resolution.
Quote from: 1% on May 15, 2013, 07:50:27 PM
So better or worse... seems better on my end.
http://ge.tt/9Co39kg/v/0
For a start - this is MUCH better when recording 1536x600 - it now stays on one star throughout! :D
Dude - you are a god damn genius! Just got 1500 frames with 1536x640!
Back to capturing up to 4GB limit on 1504x640 now (I say that - it stopped recording at about 2,500 frames so guessing that was what it was).
4gb limit is not in the module.. if something happens with memory then it stops... files bigger than 4gb I'm having a problem breaking up still but it will do it. I recorded a 27gb file yesterday.
Quote from: 1% on May 15, 2013, 08:31:25 PM
4gb limit is not in the module.. if something happens with memory then it stops... files bigger than 4gb I'm having a problem breaking up still but it will do it. I recorded a 27gb file yesterday.
Wowzer!
I wonder what is changing performance for me. It's like the first attempt after a re-boot is always a bit crap but then it kicks in the second time and works fine.
Good work anyway man and thanks for the url link!
Quote from: 1% on May 15, 2013, 08:31:25 PM
4gb limit is not in the module.. if something happens with memory then it stops... files bigger than 4gb I'm having a problem breaking up still but it will do it. I recorded a 27gb file yesterday.
By the way - only point in mentioning the limit was just pointing out that I seem to have randomly returned to getting longer recordings at 1504x640
Try using 640x480 overriden and either raw or L quality. When in doubt check memory menu and make sure you have 30 mb chunks and 152MB total
new discovery. Selectin sraw and no jpeg makes mem allocation fail (or whatever it's doing before it records).
Basically it makes it not record.
same with mraw
yes, no RAW at all !
Quote from: teo770 on May 15, 2013, 09:27:57 PM
yes, no RAW at all !
RAW (as in max quality) works for me just not the lower two raw quality shooting modes.
Quote from: 1% on May 15, 2013, 08:38:09 PM
Try using 640x480 overriden and either raw or L quality. When in doubt check memory menu and make sure you have 30 mb chunks and 152MB total
Just tried this for you with 1536x640 selected on NTSC 640x480 overridden to 24fps with every different photo shooting quality and have the following results:
RAW and every jpeg option gives me about 1,300 frames apart from Jpeg S1 (high quality) which gives me about 1,500 frames before skipping any. Ran all of them again just to make sure and had the same results again. Jpeg S1 (high quality) definitely gave me longer (if only by a few seconds) performance.
(global draw off).
Quote from: 1% on May 15, 2013, 08:38:09 PM
When in doubt check memory menu and make sure you have 30 mb chunks and 152MB total
Where do I find this dude?
Those MRAW/SRAW modes reduce memory... look at it. Its in the debug tab like 400K + 2000K. Select to see shoot malloc.
Raw and S1 or L or S3 all 152MB... any increase would be from reduced cpu usage... which we can't see (cpu meter broken).
720 vs 1080 vs 640 should all be different as YUV buffer is going to be different. 720P actually shrink the vertical height and so does zoom mode. 1080 vs 640 the raw image is the same but the HD buffer is remapped to 640X480 so seems a little less intensive on the camera.
On 600D gains from sraw and using lower res are really noticeable because its more resource poor. Ie raw or L or S will give you 70MB only and sraw gives 100MB.
Ideally we want to take YUV buffer and any other edmac down to 1 line when recording then it should be faster and free up some memory. But this part isn't figured out yet.
With 720 60fps selected and overridden to 24 fps - 1536x639 (coz can't select 640) will give me up to 1800 good frames so better performance there.
Almost there !
1504x640: 37.3 MB/s => 47 frame drops during 4GB record !
1536x600: 36.9 MB/s => no frame drop at all
1840x500: 36.8 MB/s => no frame drop at all
Two way: wider or higher....
The problem know is only about cards speed.... remind me GH2 old times !
In the benchmark, could you add buffer=8192k read/write test please ?
and even buffer= 30720...
Still playing with cluster sizes in my exFat SD trying to find extra 0.1 or 0.2 MB/s !
Next week i'll receive my new sandisk 128GB 45MB/s, will bench it too.
a quick test
Raw - off
Jpeg - S2
video 1280*720
FPS override 25
RAW video 1840*540
SDHC SanDisk Extreme Pro 32 Gb
get about 300 frames, then dropped frames
Wow, picking the "other" resolutions in adobe raw they don't look so bad. 2048*889 is passable out of 1152x500
Quote from: 1% on May 16, 2013, 05:08:16 AM
Wow, picking the "other" resolutions in adobe raw they don't look so bad. 2048*889 is passable out of 1152x500
Sweet! Have you figured out how to choose them in AE yet? I can select them in PS but that's looooong.
Also (sorry - continuing my moire/aliasing obsession here). Is the sensor the same in a 6D as a mk3? Are we getting screwed due to a different sampling method or is the hardware just not up to scratch? I just noticed on some mk3 vs 6d footage that even though the mk3 footage looks like there is no moire and aliasing in comparison, it does seem softer. As if the mk3 footage goes through a guassian blur or something. It's really standing out to me on raw footage and I'm convinced that it's because there is no codec softening the image (which to be fair was never that fantastic in terms of moire anyway).
Also - noticed the [113] Module Refactor .zip
Worth getting? :)
Quote from: 1% on May 16, 2013, 05:08:16 AM
Wow, picking the "other" resolutions in adobe raw they don't look so bad. 2048*889 is passable out of 1152x500
Yep.
I can dig it 8)
Quote from: noisyboy on May 16, 2013, 05:48:08 AM
Also - noticed the [113] Module Refactor .zip
Worth getting? :)
Update: recording times seem significantly reduced for me in this version for some reason. Loving the new start record method though :)
Did not seem reduced... just stops when buffer gets full instead of skipping.. there is a setting. Still getting 4*30 buffers and seems to be writing at same speed.
Agree with Noisyboy, even 1504x600:34.5MB/s (continuous shooting before) stops or frame skip after around 1GB
Very nice start/stop function guys !!!!
Buffers seems to have grown: 4 x 32 ?
And in every resolution, recording display less MB/s. Normal ?
Toshiba seems to have a new 64GB SD card annoncing 60MB/s write speed:
http://www.ebay.fr/itm/TOSHIBA-EXCERIA-SDXC-TYPE-2-64GB-SD-XC-UHS-I-CLASS-10-64G-64-G-GB-95MB-SEC-NEW-/330877223154?pt=UK_AudioTVElectronics_PDAsAccessories_MemoryCards&hash=item4d09d1c0f2
Love the new feature with LV button, its great!
1%, could you make this white cropmarks box which is visible during recording to come out earlier just when "READY press LV button to start recording" appears? There will be easier to get a subject into a frame properly.
Does 6D have 1:1 crop with any resolution or zoom? Somehow I cannot find any info about it, found only for 5d3.
I've also noticed, that with the newest build write speed dropped a little bit. Before I had 37-38 mb/s, now mostly 35,2-35,5.
Now (freshly formatted card)
1504x600 ~1000frames
1504x640 ~400 frames
1534x640 ~370 frames
This "buffer full-stop recording" feature is great for me - don't have to look for the start of frame drops in post.
teo770, where is the thing to set memory card cluster size?
It's not in ML.
You can format the SD card either in FAT32 or in ExFAT
When formating in ExFAT:
- you get no more 4GB file size limit
- can use long file/dir names instead of FAT32's 8+3
- choose btw more cluster sizes when formating
I have 2 Sandisk Extreme Pro 32GB 95MB/s and testing/benching both in FAT32 and ExFAT with each update
For now, i can say you gain a few 0.1 to 0.5MB/s in the benchs.
The idea is the same: in ML higher buffer sizes offers higher write speed
Higher cluster size should offer higher write speed too.
My best shots are with a 4096k cluster size actualy.
But this is a TEST, i'm not recommanding exFAT yet, neither is ML team !
Quote from: teo770 on May 16, 2013, 10:16:39 AM
It's not in ML.
You can format the SD card either in FAT32 or in ExFAT
When formating in ExFAT:
- you get no more 4GB file size limit
- can use long file/dir names instead of FAT32's 8+3
- choose btw more cluster sizes when formating
I have 2 Sandisk Extreme Pro 32GB 95MB/s and testing/benching both in FAT32 and ExFAT with each update
For now, i can say you gain a few 0.1 to 0.5MB/s in the benchs.
The idea is the same: in ML higher buffer sizes offers higher write speed
Higher cluster size should offer higher write speed too.
My best shots are with a 4096k cluster size actualy.
But this is a TEST, i'm not recommanding exFAT yet, neither is ML team !
Thanks, yeah, I know it is not in ML, I thought that such an option is somwhere in EOScard. I have already exFAT, so is default cluster setting 4096k? If not - where can I change it?
You can change that only in formating.
When formating ExFAT, you can choose cluster size.
Ahhh, alright. I formatted it with camera, I shoud have done this via windows.
PREVIEW question.
When recording RAW, we've seen that selecting JPEG only in Canon's menus allow us to gain more writing speed.
If we choose Jpeg S3, what happens to this jpeg when recording ?
Is it generated and discarted when writing on card ? or just not generated at all ?
If it's generated and discarted at each frame... perhaps we could keep one s3 jpeg (0.3Mb) every 100/200 frames
so we could have a kind of sequence "preview" ?
Quote from: kgv5 on May 16, 2013, 10:34:01 AM
Ahhh, alright. I formatted it with camera, I shoud have done this via windows.
Most people uses in camera format (recommanded by each cam manufacturer)
and not all cameras are exFAT compatible.
Make me think we would need a sheet about cameras compatible with exFAT !
I start it ! Canon 6D IS compatible with exFAT !!!! ;)
QuoteWhen recording RAW, we've seen that selecting JPEG only in Canon's menus allow us to gain more writing speed.
The quality setting in Canon menu affects how much memory is free for ML to use.
Fun stuff to try:
- alloc as much RAM as you can, by calling shoot_malloc_suite(0)
- take a burst photo sequence
- free the memory suite 10 seconds later
Result: the burst will work correctly, and the display will say BUSY until you free the mem suite. After that, all the frames will be developed and saved correctly to card.
Conclusion: Canon code reserves a large amount of memory just for this.
Quote from: a1ex on May 16, 2013, 10:42:38 AM
The quality setting in Canon menu affects how much memory is free for ML to use.
So more room for ML's frame buffers...
Is there a known list of Canon daemons running when camera in ON ?
Perhaps, like Windows services list, we could shutdown selected ones ?
For example, even powered off, wifi should have a driver daemon running somewhere waiting for wifi power on, no ? same for GPS.
Could free some mem perhaps.
In Debug menu. The AEWB task eats a bit of CPU (at least on 5d3) and I think it's worth killing it.
An extremely mean hack would be to disable photo shooting and use almost all of the 512MB for video buffering. I'm not that adventurous though, so I'm not tempted to try it. I prefer clean solutions that don't affect normal camera behavior.
Quote from: a1ex on May 16, 2013, 11:15:20 AM
In Debug menu. The AEWB task eats a bit of CPU (at least on 5d3) and I think it's worth killing it.
An extremely mean hack would be to disable photo shooting and use almost all of the 512MB for video buffering. I'm not that adventurous though, so I'm not tempted to try it. I prefer clean solutions that don't affect normal camera behavior.
A1ex,
There are some(like me) that are not really concerned about "normal camera behavior" . Especially some 5D2 shooters who have a VAF filter installed, we can't take normal photos now since the mirror is fixed in up position due to the VAF.
I bought these cameras for video and I think a lot have too. So if by disabling some of the "normal" behaviors to allocate more resources to ML gives better Magic Lantern performance, so be it.
I'm sure you can also have a menu option to toggle that on or off?
Ted
The kind of hacks I'm thinking about may require changing stuff in Canon code at boot time. So it's not about a menu option or a loadable module, but a separate autoexec that does only this. I also don't want people saying "I've installed ML and now I can't even take pictures..."
Quote from: a1ex on May 16, 2013, 11:15:20 AM
An extremely mean hack would be to disable photo shooting and use almost all of the 512MB for video buffering. I'm not that adventurous though, so I'm not tempted to try it. I prefer clean solutions that don't affect normal camera behavior.
I agree but if you just kill some running daemons, will a simple hard reboot (battery pull) not restart all daemons/services ?
I'm not at all to modify normal boot sequence cause we're not speacking about $100 cams, clearly !
And this would be usefull only if those killed daemons would free some mem. If just CPU time... not sure we would gain something.
Quote from: a1ex on May 16, 2013, 11:30:34 AM
The kind of hacks I'm thinking about may require changing stuff in Canon code at boot time. So it's not about a menu option or a loadable module, but a separate autoexec that does only this. I also don't want people saying "I've installed ML and now I can't even take pictures..."
You can have this as another version then, lets call this "Magic Lantern Extreme Version" ! Heck, there are businesses out there already permanently removing the mirror assembly to mount PL mount, those are extreme hardware hacks already. Several physical mods like the Hotrod cameras do this, even boarding up the viewfinder already.
With a stable "extreme hack" focused toward film making, an ML raw capable canon DSLR will make a compelling challenge to the big boys like red, or sad to say even to the BMCC.
Besides, RAW DNG video IS a series of RAW stills already. This is what some fashion photographers are doing with the RED cameras.
Perhaps good news for Moiré issue with 6D.... needs testing !
When importing DNG sequence in After Effect, it uses Camera Raw.... so same tools are available than in LightRoom....
You can create a filter to apply to the whole frame and... push the anti-moiré slider to the right.
In my "threes in the wind" sample, Moiré is just gone !
Of course, this kind of filter applied on the entire frame and all frames can change all colors so....
need deep testing to see if after this anti-moiré filter we can still color grade enough...
update: Good for moiré, but still aliasing to be treated...
QuoteAn extremely mean hack would be to disable photo shooting and use almost all of the 512MB for video buffering. I'm not that adventurous though, so I'm not tempted to try it. I prefer clean solutions that don't affect normal camera behavior.
A config option? Like If video_only = 1 run these cache hacks in boot-hacks.c And then flip it on/off and reboot.
On 5d3 this isn't needed so much but on SD cameras we have less than 1/2 of CF write speed. On 600D you already "kill" photo mode by having to use sraw. So IMO this is kind of necessary.
I'll see what is happening with the writing... it shouldn't have slowed down but who knows.
Since updating to the latest 113 .bin the help mode in camera no longer works for me. Pressing the INFO-button has no visible effect, except for disabling display updates. If I press the button and try to change the menu item with the main dial, nothing happens. After I press the INFO-button again, the menu item I tried to navigate to is selected and controls work as normal again.
I did already try to replace the doc-folder, then the whole ML-folder (plus the MODULES, SCRIPTS, etc.) with a freshly downloaded copy, unfortunately this did not resolve the issue.
Did anyone else encounter this problem?
So ML is running and the FW on your camera is 113?
I know why write speed is lowered.. using 32MB buffers instead of 30MB
Yes, i noticed 30->32 Mb buffers but frame drops happens really early now,
even @ 1504x600 vs no frame drop before
Problem is since [113] Module Refactor .zip
The 32MB chunks are too big and too slow... I tried to fix it not sure how it divides now. Really we should be using 28.. that was the fastest for this camera but it wasn't freeing properly when allocated with the old method.
Fine tuning, fine tuning !
Which i knew enough C to help somehow....
So, has anyone ever taken their camera apart so that we actually know what kind of SD controller is being used? if the controller has a maximum of 50MB/s , we have a known limit and know where we can go from here.
If the Controller is in fact better but SD cards are not up to speed yet, we can maybe hardware hack an SD card--> SSD (or CF) Adapter, the controller should be able to handle that, I am looking into how Sd cards work but I should be able to run wires from a "blank" Sd Card to direct Sata Pins or IDE.... if there are CF->SD adapters, making it work the other way SHOULD be possible, maybe we need external power to run the CF but that should be the least problem...
UHS-1 Specs: 50 Mbyte/s (SDR50, DDR50)
104 Mbyte/s (SDR104)
if its a SDR104, we can make 1080p work Theoretically
If that does not work, another idea is to externally Raid0 SD cards
And then there is also the HDMI port, which is by far the fastest port we can use, I have all kinds of testing equipment for that stuff at hand, so if you can somehow get the raw signal out the HDMI port, I can probably build something to receive it.
Also: I can confirm that with the latest Autoexec.bin I am seeing Frame drops way more early than I did with the previous version
One more thing: I Have really nasty pink/Green spots when filming in ISO 25600
http://www.youtube.com/watch?v=_HVfljMyWZE
HDMI is an off the shelf solution it works on the image too. Doubt we can make it just pass regular data.
Obviously its not SDR-104 or sandisk pro cards would be getting 90MB/s and we wouldn't have a problem. 208mhz speed not listed in the firmware.
Adapters aren't going to work... what could work is
*WIFI - if buffer sizes + write speeds are high enough
*WFT like USB disk through USB port or the grip.
*Opening camera and finding where the CF card connection is and if there is one on the 6D board (might as well install the headphone jack while you're in there)
6D is basically 99% 5d3 with a different sensor.
Quote from: 1% on May 16, 2013, 04:38:40 PM
*WIFI - if buffer sizes + write speeds are high enough
*WFT like USB disk through USB port or the grip.
*Opening camera and finding where the CF card connection is and if there is one on the 6D board (might as well install the headphone jack while you're in there)
I Like the Grip Idea, totally forgot about that, is there any documentation on the Pins/controller?
I don´t think Wifi will work we will really only see 240 Mbit/s (if that) and the WTF adapters uses the USB 2.0 Port (480Mbits) , maybe we can ghetto-Raid the SD and the USB card and then Merge the files , best solution I am seeing right now
Any chance we could use USB port to plug a USB CF card reader ?
;)
I already know the answer.
Damn those cams doesn't run linux inside !!!
We could mount anything on this USB port !
Quote from: teo770 on May 16, 2013, 04:55:14 PM
Any chance we could use USB port to plug a USB CF card reader ?
;)
I already know the answer.
Damn those cams doesn't run linux inside !!!
We could mount anything on this USB port !
The WFT adapter (WFT-E7 i.e) has a USB Host (and Gigabit lan..) But the maximum Speed will be limited to 480Mbits (60MByte/s) (Theoretically)
So yes, you can connect a SSD Raid if you really want but it wont be any faster than a fast SD Card.. (USB Bottleneck)
Yea but how much does a "fast" usb card cost vs a plain old USB hard drive? Sure it would have to be powered externally.. you could also use USB to CF but I think that would be too slow. If we get anything around 30-40MB/s its a workable solution.
Wfi does use memory and may not be so good performance wise, who knows. I think someone tried sending files and couldn't get much more than 20MB off.
I tried changing minimum chunk size to different things and we can only go worse.. Using the 32MB buffers cut at least 1MB off of write.. I'm writing at 27.x now where I was writing at 28.x-29... if 28MB works now I bet it will do the whole 31MB for me... it did when 28MB buffer size was previously elected. I think we need to hear from a1ex on how to fix it so it doesn't use values good for CF.
The question is, if we can send Every second frame out via the USB port, we will just need something with a USB host to wait and catch that Data (like a Laptop..)
Yep, laptop or external drive. Will need stuff anyway as the camera probably doesn't have USB host and the WFT does.
Quote from: 1% on May 16, 2013, 05:38:44 PM
Yep, laptop or external drive. Will need stuff anyway as the camera probably doesn't have USB host and the WFT does.
We will somehow have to make it work without the WFT adapter, that thing costs $700 , I cant really figure out what kind of electronic magic the WFT has in order to pull data off the Camera and then send it to the USB Host controller.
Anyway, I would think that as in many tablets the 6D has a "hidden" Usb Host built-in to the mini usb port just like the Nexus 7.
Just discovered that when 6D is USB plugged in computer, you can't see the .RAW files.
Only .jpg and .cr2 files ....
Just tested Sandisk Pro Extreme 95MB/s 32 GB in a USB3 reader....
83 MB/s write speed
94 MB/s read speed
Now we are sure Canon 6D UHS1 is limited to 50MB/s !
For me, recording higher than 38 MB/s starts frame skipping so there are extra 12MB/s left to find !
;)
Having a good/rock solid 40MB/s would be really just fine.
1536x640 24p, ratio 2.35, easy upscalable to 1920x800
We have to find what interface WFT is using to connect to 6D/600D, etc. If its USB we can just use the USB port, if not then we have to use the grip pins.
Popular software DSLR controler used from an android connected to 5D Mrk II by USB wire:
Liveview display is 15 fps...
Just tested on 6D by Canon EOS utility, same fps
Transfert of a movie file 200MB by USB to PC is about 15 seconds so 13-15MB/s :(
But that is a transfer through whatever wrapper + other canon stuff. Also connecting to PC may start LV jpegs reducing camera memory and using CPU.
Last raw_rec:
no beep
1504x600 24p stops after 1.6GB
The last really working for me was the one with 4x30MB buffers
At 1504x600, the 1st star only was blinking, never stops/frame drop
Hang on - isn't there already a program that does this? I used to have it on my PC with my 550D or whatever it was years ago. Plugs into laptop and records video from the live view.
Yeah - here http://sourceforge.net/projects/eos-movrec/ (http://sourceforge.net/projects/eos-movrec/)
Quote from: noisyboy on May 16, 2013, 08:19:23 PM
Yeah - here http://sourceforge.net/projects/eos-movrec/ (http://sourceforge.net/projects/eos-movrec/)
Tested it this afternoon, can't see the 6D...
On the wifi side, a few elements. A web site tested diferent solutions to transfert some files (Raw, jpeg...etc):
Transfert by USB
Transfert using a Eye-fi Pro X2 card
Transfert using Canon's WFTE2
Page is in french but i think you ll understand the sheet "2) La vitesse de transmission"
http://www.cyrilbruneau.com/dossier-photographe-professionnel/eyi-fi-pro-x2-photographe-professionnel.html
Hope the wifi part in the 6D is more efficient !
I'm starting to love that USB idea !
Update: Funny, Amazon seems to read ML forums, they are offering you US buyers up to 60% off on Sandisk cards !!
http://www.amazon.com/gp/feature.html/?ie=UTF8&docId=1001046141&ccmID=380205
.... slow ones !!
Quote from: teo770 on May 16, 2013, 08:29:03 PM
Tested it this afternoon, can't see the 6D...
Pitty! Does this bridge any gaps in what you a re trying to achieve though. I remember it working very well when I used it in the past. Considering at the time there was no video capability on my camera :p
Yep, that recorder doesn't work. 6D the live view sending changed a little.
Sucks that its stopping sooner now. I tried other buffers, not sure what to do.. I think the small blocks are slowing things down. I don't see what its allocating anymore, it does an average. How much did the write slow down by?
Fixing a few things with wav.
Quote from: 1% on May 16, 2013, 08:41:32 PM
Yep, that recorder doesn't work. 6D the live view sending changed a little.
Ah okay! Might help with your other cameras though maybe! Nevermind :)
Will check how much it changed in a mo. It was quite a big change for me personally. I'll load both versions on separate cards and compare.
Quote from: 1% on May 16, 2013, 08:41:32 PM
Sucks that its stopping sooner now. I tried other buffers, not sure what to do.. I think the small blocks are slowing things down. I don't see what its allocating anymore, it does an average. How much did the write slow down by?
Still 1504x600@24p stopping: 1000 frames around 1.5-6 GB.
Can you display buffers size too like before ?
That should be displaying, not sure why its not popping up anymore.
QuoteStill 1504x600@24p stopping: 1000 frames around 1.5-6 GB.
mine stops at 1500 frames. Deff slower now
But what about write speed during recording? Lower?
For me it usually sticks around an average after ramping up. 27.something. Before it would skip frames and not stop, what does it do if you make it skip frames?
cant remember before speed but now:
@35.1 MB/s it stops after 1500 frames
when set to skip frames it stays at 35.1MB/s and skipped 36 frames until 4GB
Try the older module to compare I guess.
That would suck if you're losing 3MB.. Before it wouldn't allocate all of the memory just use the 30MB chunks. Now it does the whole thing... maybe the double buffer is too big? Putting it back to the old way causes overflow in zoom 10x/5x
in photo mode I get 35.4 and got 2128 frames with global draw on.
exp sim off. with exp sim on it is back to 35.0
But with the older (4x30) module it was?
Yep.. .getting slightly higher speeds in Photo/720P (worse image)/ and 640x480... really going to help to kill photos and get more memory.
QuoteNow it does the whole thing...
Only 16MB and higher blocks. Maybe 16 is too small?
Quotemaybe the double buffer is too big?
Now it's as small as it can be (the size of one frame). In crop mode it's bigger, in 1x mode it's smaller. For safety, recording stops when you change the video mode.
I tried minimum blocks of 30,32, 4, 8, 16, 28... did not see a difference... In fact with this one all I've been able to do is slow it down. So maybe its as good as it can be until we can allocate at least 200MB or something.
BTW, panning is working pretty well. One time it tried to move the zoom box first and there was a jump... I guess only move the zoom box with the set button? But how to center the frame again?
Speed for me went from 38.5 to 35ish
Quote from: noisyboy on May 16, 2013, 11:14:15 PM
Speed for me went from 38.5 to 35ish
I think that was when shooting 1536x640
- With "[113] Wav fixes.zip":
1504x600@24p: 34.6MB/s
frame drops after 1050 frames/around 1.55GB
- With "raw_rec.mo - 4 buffers, no worries"
1504x600@24p: 36.1MB/s
continuous recording, no frame drop, only 1st star is blinking
4 x 30MB buffers displayed
Shit I dunno, I've tried everything besides going back to the old way.
Deep breath... have a coke and clear that mess ! 8)
Problem is in raw_rec.mo, it's the only thing i changed.
[113] HDR Raw.zip: 34.8MB/s
1504x600@24p: frame drops after 1050 frames 1.631GB
55 frame drops for a 4GB file
No synch beep
Playback in black & white working ! waoooo (need press shutter release or AF-ON to stop it)
FREE MEMORY: 450K + 2077K
It was 450K + 2154K with "raw_rec.mo - 4 buffers, no worries"
Shoot malloc contig and total are the same: 30 and 152MB
So sync beep stopped working? Still beeps for me.
There are 3 memories:
Malloc - like 400-800k
allocatemem - where ML loads and that 2M value...
shoot malloc - where the buffers are. now I think you can't see free anymore because it crashes. maybe it means 0 free :)
Synch beep is playing but it's a "shttt", definatly no a "beep".
Like an aborted beep
Weird... check settings in beep. Sounds the same here.
Just for my info, what's in the MAGIC.SYM file ?
All of symbols for canon and ml functions, etc.
Open it with a text editor to see.
Also wondering... sandisk 128gb or 64gb... any rate difference?
The test tones seems working fine.
The beep is a 1/5 sec "shtt"
For the Sandisk, i've read tests saying the 64GB would be better than the 32GB.
I wouldn't be surprise. If you read SSD tests sometimes, 128GB are often faster than 64GB
Can't say about the 128 yet.
Change it to sine and change the KHZ to modify it. I guess it does kinda make the shit sound... its the default ML beep forever.
Sine + 1760Hz works: welcome back to the beep !
Thanks
Next SD card i ll try is the Toshiba, annoncing 60MB/s write speed:
http://www.ebay.fr/itm/TOSHIBA-EXCERIA-SDXC-TYPE-2-64GB-SD-XC-UHS-I-CLASS-10-64G-64-G-GB-95MB-SEC-NEW-/330877223154?pt=UK_AudioTVElectronics_PDAsAccessories_MemoryCards&hash=item4d09d1c0f2
They even have a EXCERIA I announcing 90MB/s write speed ! But now we are sure it's useless on 6D...
But if you read my last posts, i bench the Sandisk Extreme pro to +80MB/s write speed in a USB3 reader so...
I don't plan getting higher write speed from SD card.
Wow, this card is cheap.... I hope its not only for 208Mhz.
Ok, maybe type 1 is for 208 and type 2 is for 100
The version II was released march 2012 so i think it's more modest (and cheap !): 60MB/s would be perfect price/perf for the 6D.
If it does any better than 40MB/s then its winner.
The type 1 2 says 90 read/write?
Too bad all of these are in HK... would get here in like 3 weeks.
Yes but for that price tag.... you can only have a good surprise (write speed)
or a good 64 GB card for photos !
Quote from: teo770 on May 16, 2013, 02:06:52 PM
Perhaps good news for Moiré issue with 6D.... needs testing !
When importing DNG sequence in After Effect, it uses Camera Raw.... so same tools are available than in LightRoom....
You can create a filter to apply to the whole frame and... push the anti-moiré slider to the right.
In my "threes in the wind" sample, Moiré is just gone !
Of course, this kind of filter applied on the entire frame and all frames can change all colors so....
need deep testing to see if after this anti-moiré filter we can still color grade enough...
update: Good for moiré, but still aliasing to be treated...
Like your style 8) Didn't think of doing it that way. Basically a MUCH much easier version of what I was attempting with Gaussian Bluring Chroma so scrap my idea. Works great anyway so props dude!
As for the aliasing "stepping" been having great results with "SK Staircase Suppress" from the RE:Vision Smoothkit bundle. It works by intelligently bluring aliasing artifacts so of course it's not ideal as it softens the image so only used if necessary but most of the sharpness can be regained by adding an "unsharp mask" or "sharpening" filter in AE.
Again - not a perfect solution but for my money (and I'm a real anal bastard when it comes to quality) I would rather have this image with all the benefits of higher color data and dynamic range retention than having h.264 anyday and I'd also rather have a slightly softer image than an ultra sharp image which consequently distracts the shit out of you with horrific shimmering artifacts from aliasing.
If anyone wants to see before and afters then I'll happily oblige but it's worth trying yourself I think.
Anyway - tomorrow morning I receive my super fast Delkin card so fingers crossed for some improvements :)
Ps. Not suggesting that the Delkin is a good solutions even if it DOES work as it's fucking pricey but at least we'll know if it expands possibilities.
I won't even begin to act like I understand what you guys are doing, but I've been watching the forum and I have a question.
From what you guys know so far, is 1920x1080 RAW theoretically possible on the 6d? I know the processor is the same as the Mk III, but I know there are a ton of other factors there too.
Also, is the highspeed SD card from sandisk (95mb/s I believe) not really writing at 95mb/s?
Thanks for what you guys do. Looking forward to a ML build for my 6D!
slight increase on 128Gb card: 35.3 got 1800 frames
I guess you prob already know this but just incase you wanted feedback, still suffering huge dip in performance with latest module + autoexec. 1536x640 is giving me average 450 frames as opposed to the previous version giving me 1,500.
Cheers :)
*Just to clarify - best version for me is still "4 buffers no worries" and my last comment was regarding "New Routines".
Version: [113] New Routines.zip
1504x600@24: 34.9 MB/s
Drop frames after 1250 frames/1745MB
My tests process:
Battery pull to really clear older ML modules loads
Load modules
Select 1504x600 with "skip frames" option
Shoot
The buffers are acting differently at the start.
The 1st buffer is feeded very quickly instead in the version "4 buffers no worries" where the 1st buffer always blinks along 4GB recording.
A problem freeing buffers ?
I'm in EU so PAL zone, i tried changing to NTSC as you guys but acting the same.
1% and all ML devs, it seems developping is pretty intance the last days. We were on a .bin every 2 days way, we are now at 2 .bins/modules a day !
We are available for testing but it must not enhance pression on you ML developpers.... so take your time. You know a lot of people are watching/waiting for this 6D raw video feature but you can't turn NOLIFE now ! (we need you for support too !!!) ;)
Quote from: dmg09 on May 17, 2013, 04:37:08 AM
I won't even begin to act like I understand what you guys are doing, but I've been watching the forum and I have a question.
From what you guys know so far, is 1920x1080 RAW theoretically possible on the 6d? I know the processor is the same as the Mk III, but I know there are a ton of other factors there too.
Also, is the highspeed SD card from sandisk (95mb/s I believe) not really writing at 95mb/s?
Thanks for what you guys do. Looking forward to a ML build for my 6D!
I doubt 1920x1080 possible with 6D cause of SD card speed. Sandisk 95MB/s is writing 80+MB/s in a card reader on PC but the 6D seems limited to max 50MB/s. According to Alex, 1920×1080 RAW video requires 83MB/s at 24fps in 5D Mark III.
Having a stable format like 1536x640@24/25/30p easyly upscalable to 1920x800 with a 1.25 factor would give us a really good 2:35 movie mode.
Comparing with the 1920x1080 with x264 compression, the RAW, even scaled, should be as sharp with many more Dynamic Range.
And.... it's RAW ! With the same benefits as raw photos !
And last but not least, you can buy Froknowsphoto's T-shirt: "I shoot RAW !" :) :) :)
Hi guys! I know all you are now busy with the raw staff, bat can I ask you if it would be possible to make record 2 channels like on 5dmkII? I mean one channel from internal mic and one from external mic?
Thanks!
[113] Improv.zip:
1504x600@24p: 34.8MB/s
Frame drops after 1300 frames/1890 MB
I got slightly higher speeds on this one... 2K frames of 1320x540.. last time only 1300 or less. 27.9MB/s vs 27.2 and no more dropping into the 26s and 25s.
We need a debug log somewhere which register all things till frame drops.
Both for last update then on the good raw_rec "4 buffers no worries" to find out what has so changed.
No ? Possible ?
For example: every 1 sec CPU usage / memory / buffer content
I still have a problem with raw2dng with files larger then 4gb (windows). I though I read somewhere that Alex fixed it... 1% is there a new version that I missed? Can you upload it because the one you have up there is not opening
never mind GOT IT :)
For some reason it won't read over 4GB files... I dunno why. The header is there and i compiled for 64bits and even updated stuff to long long int.
CPU can't be measured, we can't take over tasks. I think what changed is allocating all the memory at once vs using single large chunks. I think we just need to take more of the 256 or whatever memory and shut down camera processes.. those mean hacks that were talked about.
So...
Just got my Delkin 633x which is supposedly the fasted card on the market and I'm sad to report that it gives me absolutely no improvement in performance vs my Sandisk Extreme 45MBs. Even benchmarks the same. If anyone has any suggestions on fun things to try to make it perform better then holla 8)
Ps. Tried formatting both fat32 and exfat (with different unit allocation sizes) and still pretty much the same - if anything is performing worse than the Sandisk. Will try a full format but not that optimistic. Don't waste your money and stick with Sandisk Extemes for now - they're like a 3rd of the price.
Quote from: 1% on May 17, 2013, 03:51:46 PM
I got slightly higher speeds on this one... 2K frames of 1320x540.. last time only 1300 or less. 27.9MB/s vs 27.2 and no more dropping into the 26s and 25s.
Weird man. I wonder why you get better performance than I do? I lose about 3MB/s on this vs "no worries" version.
Could we have a kind of "4buffers no worries" + white frame + start/stop button + bip sound raw_rec.mo ?
So we can deep test the 1504x600. Night, day, trees, inside/outside.... etc, moving kids, the SEA ;)
You talking about freeing more mem disabling photo functions but with the fastest SD card, we would top at 50MB/s in the 6D.
So resolution about.... 1840x680 (640 to be sure), right ? Approching too close the 50MB/s write speed... what about sound ?
QuoteSo...
Just got my Delkin 633x which is supposedly the fasted card on the market and I'm sad to report that it gives me absolutely no improvement in performance vs my Sandisk Extreme 45MBs. Even benchmarks the same. If anyone has any suggestions on fun things to try to make it perform better then holla
Ps. Tried formatting both fat32 and exfat (with different unit allocation sizes) and still pretty much the same - if anything is performing worse than the Sandisk. Will try a full format but not that optimistic. Don't waste your money and stick with Sandisk Extemes for now - they're like a 3rd of the price.
that sucks!
looks like that is the best it gets for 6d. I doubt that we can find a SDR50 card that can write that fast :(
Quote from: DTSET123 on May 17, 2013, 05:00:10 PM
that sucks!
looks like that is the best it gets for 6d. I doubt that we can find a SDR50 card that can write that fast :(
Yeah man. Gutted :(
On the plus side - it's nice to know that I don't have to spend £65 per 32GB of data :)
1% - Where in the world are you bro? I would gladdly send you my new Delkin card so you can test shit out and not be limited by your card if that helps? Of course eventually I'd want it back but if you wanted it for a couple weeks before I need it again then I don't mind sending it your way at all dude :)
Quote from: noisyboy on May 17, 2013, 05:14:44 PM
... then I don't mind sending it your way at all dude :)
I see... corruption is growing everywhere !!! ;D
Quote from: teo770 on May 17, 2013, 05:18:05 PM
I see... corruption is growing everywhere !!! ;D
Lol - not entirely sure what that means but cool! ;)
There is probably a card that can do 45/6 or something like that, not sure what that would be. Maybe that toshiba card or ep pro.
The memory managment is different, would have to rewrite it back to that. New benchmark will run for a while and is supposed to be used to find best buffer size... still WIP, need to fix it not just put it back to the old way.. .which will crash out zoom recording when finished.
With more memory maybe higher res won't be continuous but you will have lots of buffer. A minute of full size raw is better than it just stopping.
I don't know you'd get the card back in 1 piece... these writes really take a toll. For all we know the cards are getting worn down, esp writing raws then moving and deleting and writing over the same spot again.
Don't worry man - I understand the risks :)
Just trying to do my part to contribute as I no fuck all about coding this bad boy and am pretty much learning all of this from you guys as we move along (seriously - learned so much the last couple weeks so thanks).
Anyway, the offer still stands. Or even if it makes you feel less guilty I can send you a Sandisk Extreme. Honestly don't mind man :D
Are you in the US? Try the benchmark for like 1/2 hr and see what it says about buffers.
Which benchmark ?
Hey guys, I recently upgraded from a 600d to a 6D & the first thing I did was look up to see if I could put ML on it. I see its still in development and I've seen a few guys with it on their 6Ds. Can someone please instruct me how to get the current build running on my 6D? I understand the risks. I dont know a lot of about code but I will play around with ML and report and feedback on anything worthwhile that I find. Thanks in advance.
Quote from: 1% on May 17, 2013, 06:07:20 PM
Are you in the US? Try the benchmark for like 1/2 hr and see what it says about buffers.
I'm in the UK but it's only a memory card. Wont cost much to send. I'll even pay to get it back dude. It benefits us all so I honestly don't mind. You spend night and day on this thing and consequently I will use these features to make money which will eventually far supersede the cost of a memory card. That or the donations really should start up again. Even if it buys all the devs a decent card each cos you deserve to at least have the tools to do the job :)
I know you guys do it for the fun of it anyway but I'm just saying you shouldn't feel bad about people funding the work you guys do, even if it only covers the cost of development. That's what's so fucking awesome about the internet :)
About that Benchmark test, could you point me in the right direction? Not sure how to do anything more than a standard 5 minute write/read test.
I will be getting this for my 5Dm3
http://www.engadget.com/2013/04/26/toshiba-compact-flash-exceria-pro-150MBps/
Latest has card benchmark infinite.
God ! By mistake tried for 1st time benchmark in photo and "playback" mode, global draw off !!!
(no modules loaded)
Results
Writ 2048k: 39.9 MB/s
read 2048k: 42.5 MB/s
writ 1953k: 35.1 MB/s
read 1953k: 41.3 MB/s
write 3072k: 40.6 MB/s
read 3072k: 43.2 MB/s
write 2929k: 36.6 MB/s
read 2929k:42.2 MB/s
write 4096k:41.1 MB/s
read 4096k: 43.3 MB/s
write 3906k: 38.6 MB/s
read 3906k: 43 MB/s
write 16384k: 41.7 MB/s
read 16384k: 44.1 MB/s
write 15625k: 41.5 MB/s
read 15625k: 44.1 MB/s
Soooo 41.7MB/s write speed is possible... with Sandisk !
My new question..... can we record RAW while in photo mode ???
Wrong bench but yea, photo mode will work with LV open.. Photo mode without LV nope
ahhhhhhhhh i know this is not what you want but:
Photo mode LV open, recorded 4GB 1536x640@24p
only 5 frames drops !!!!!
... with the "4buffers_no_worries" raw_rec.mo !
I try imediatly with the last [113] Improv.zip !!!!
Damned, with [113] Improv.zip in photo mode LV open, the RAW video menu offers only width: 611 and heigh: -22 ??????
And of course LV button, does not record !
Lv button records on newest but yea, we're trying to figure out the speed issue. Also remember LV and zoom modes have to be overriden otherwise its 30FPS.
With the 113 versions, do I just update my camera firmware, I am on 112, and then start using the new autoexecs? Or is there more to it? Eager to test again :)
Quote from: sparedog on May 17, 2013, 08:30:44 PM
With the 113 versions, do I just update my camera firmware, I am on 112, and then start using the new autoexecs? Or is there more to it? Eager to test again :)
Update to 113 and format card (just to save any bother). Then run eoscard and replace autoexec . There are files you have to put on which adds the raw shooting capability in the form of a "module". Basically you'll be good to go if you get everything from the [113] Auto Allocate.zip and then just update files as they become available: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
1% is it bad form if I basically share everything people will need to get going using the "4 buffers no worries" version? I started writing instructions for "leenks" who was asking for help getting started further up the thread but it ended up being a full on guide with loads of different links so I figured I might as well just throw everything needed into a zip for people to get going and upload it to my ge.tt instead of people having to drudge through a load of stuff they probably don't quite understand. It literally took me about two days to work out getting started with ML so I know what it's like when you have never done this before.
Thought I better ask before I share anything myself as I know it's all openly available to whoever wants to use it but I don't know what the etiquette is on sharing myself.
Quote from: noisyboy on May 17, 2013, 09:22:30 PM
Update to 113 and format card (just to save any bother). Then run eoscard and replace autoexec . There are files you have to put on which adds the raw shooting capability in the form of a "module". Basically you'll be good to go if you get everything from the [113] Auto Allocate.zip and then just update files as they become available: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Thanks, it works :D
I loaded the modules, selected to record raw in the new L menu, but didnt manage to record raw... hmmmm Is there another thing to do?
EDIT - I got it, I didnt see the Start Raw :D
Share it... will help to avoid the "when is ML for 6D coming out" posts. If you feel like making a link with 113/112 and all that stuff go for it. More time for me to mess with other stuff.
Quote from: sparedog on May 17, 2013, 09:58:35 PM
Thanks, it works :D
I loaded the modules, selected to record raw in the new L menu, but didnt manage to record raw... hmmmm Is there another thing to do?
EDIT - I got it, I didnt see the Start Raw :D
Good stuff :) Enjoy it man and share your progress. We are currently seeing a pretty much continuous recording on faster cards by selecting 1536x600 or 1504x640 @24fps (there really is quite a significant difference between 24 and 25 if you are in the EU so just stick with 24fps if you want better performance.
Quote from: 1% on May 17, 2013, 10:17:29 PM
Share it... will help to avoid the "when is ML for 6D coming out" posts. If you feel like making a link with 113/112 and all that stuff go for it. More time for me to mess with other stuff.
Cool! Yeah that was my thinking :) Admittedly I don't know the deeper side to using ML but at least I've got the experience of being a n00b so if I can somehow take the strain off by helping people get going then you can pretty much not have to worry about it. That and the more people testing the better! I'm an ios and android app designer (I basically think of cool ideas and my clever-ass-smarter-than-me coding wizard Andrew makes it all come to life) so I fully understand the importance of beta testing.
I'll start it on another thread and if anyone asks how to get going with it then you can always just copy and paste my post as a reply. Simples ;)
Recording Raw 720* 1920 on a Sandisk Extreme Pro 8gb 95MB/s (previously tested to 50Mb/s)
with these settings
frame skip 1
single file on
raw recording on
gives me
allocated 152 Mib
76 saved, 29.1MB/s
Is this expected or should I be getting more from this. Do I need to tweek the settings to get longer recording times?
Yes !!
First success with version [113] Improv.zip:
All in PHOTO mode, all testings: 4GB recorded
1504x600@25p: 35.1 MB/s, 0 frame drops during 4GB !!! NO fps override and Global Draw OFF
1504x600@25p: 35.1 MB/s 32 skipped frames if Global draw ON in a 4GB record
1504x600@25p: 35.6 MB/s 0 skipped frames if FPS override set to 24fps and Global Draw OFF
1536x600@25p: 35.9 MB/s 31 skipped frames if FPS override OFF and Global Draw OFF
1536x600@25p: 35.4 MB/s too many frame drops if FPS override OFF and Global Draw ON
1536x640@25p: 36.1 MB/s too many frame drops if FPS override OFF and Global Draw OFF
1600x540@25p: 34.5 MB/s 0 skipped frames if FPS override OFF and Global Draw ON
1600x540@25p: 36.1 MB/s too many frame drops if FPS override OFF and Global Draw ON
Global draw and FPS override consumes time and/or memory i see.
1%, it's because of what you told me earlier: "if not using FPS override, it will record at 30 fps".
I presume 30fps is for NTSC zone... so in PAL, if no FPS override, should record at 25fps, right ?
Quote from: sparedog on May 17, 2013, 11:37:51 PM
Recording Raw 720* 1920 on a Sandisk Extreme Pro 8gb 95MB/s (previously tested to 50Mb/s)
with these settings
frame skip 1
single file on
raw recording on
gives me
allocated 152 Mib
76 saved, 29.1MB/s
Is this expected or should I be getting more from this. Do I need to tweek the settings to get longer recording times?
Hi.
With those settings it sounds like you're using lv_rec.mo and not raw_rec.mo? The settings for using raw_rec.mo after loading it is in the bottom of the Video tab in the ML settings!
Also, 1%; I found a bug. If you set LV-button to "Rate Image" when in playback mode it will rotate the image instead. I guess the order in the quick settings menu for playback mode got changed with the 6D. It need to go down two steps instead of one, before going left. I hope that made sense...
Not improved for me :(
is it possible to add time elapsed as well during recording?
Quote from: teo770 on May 17, 2013, 11:47:21 PM
Yes !!
First success with version [113] Improv.zip:
All in photo mode
1504x600@25p: 35.1 MB/s, 0 frame drops during 4GB !!! NO fps override and Global Draw OFF
1504x600@25p: 35.1 MB/s 32 skipped frames if Global draw ON in a 4GB record
1504x600@25p: 35.6 MB/s 0 skipped frames if FPS override set to 24fps and Global Draw OFF
1536x600@25p: 35.9 MB/s 31 skipped frames if FPS override OFF and Global Draw OFF
1536x600@25p: 35.4 MB/s too many frame drops if FPS override OFF and Global Draw ON
1536x640@25p: 36.1 MB/s too many frame drops if FPS override OFF and Global Draw OFF
1600x540@25p: 34.5 MB/s 0 skipped frames if FPS override OFF and Global Draw ON
1600x540@25p: 36.1 MB/s too many frame drops if FPS override OFF and Global Draw ON
Global draw and FPS override consumes time and/or memory i see.
Cool man! Interesting... So are you getting better performance on 25fps? Coz the difference between 24 and 25 for me is HUGE I can shoot way longer on 24fps!
Good testing :)
Quote from: noisyboy on May 18, 2013, 12:26:53 AM
Cool man! Interesting... So are you getting better performance on 25fps? Coz the difference between 24 and 25 for me is HUGE I can shoot way longer on 24fps!
Good testing :)
You succeed in PHOTO mode LV ON, registering 4GB with FPS override set to 24 ?
In which definition ?
Quote from: teo770 on May 18, 2013, 12:29:35 AM
You succeed in PHOTO mode LV ON, registering 4GB with FPS override set to 24 ?
In which definition ?
Sorry man- what do you mean by registering 4gb?
Also, how do you manage to get 25p in photo mode with FPS override switched off?
1% told me if i don't do FPS override in PHOTO mode, it will record at 30 fps...
But 1% is in a NTSC zone (US). We in EU, use PAL so 25fps
For each resolution test, i have registered recorded 4GB..
Sorry my crappy english !
i'd love you long time!
Quote from: noisyboy on May 17, 2013, 09:22:30 PM
Update to 113 and format card (just to save any bother). Then run eoscard and replace autoexec . There are files you have to put on which adds the raw shooting capability in the form of a "module". Basically you'll be good to go if you get everything from the [113] Auto Allocate.zip and then just update files as they become available: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
1% is it bad form if I basically share everything people will need to get going using the "4 buffers no worries" version? I started writing instructions for "leenks" who was asking for help getting started further up the thread but it ended up being a full on guide with loads of different links so I figured I might as well just throw everything needed into a zip for people to get going and upload it to my ge.tt instead of people having to drudge through a load of stuff they probably don't quite understand. It literally took me about two days to work out getting started with ML so I know what it's like when you have never done this before.
Thought I better ask before I share anything myself as I know it's all openly available to whoever wants to use it but I don't know what the etiquette is on sharing myself.
Quote from: Veggietech on May 17, 2013, 11:50:00 PM
With those settings it sounds like you're using lv_rec.mo and not raw_rec.mo? The settings for using raw_rec.mo after loading it is in the bottom of the Video tab in the ML settings!
I must be missing something, I load the modules, and both LV-rec and Raw-rec come up OK.
Then I switch the the LV Rec menu, and change RAW recording to on.
But it still records only 71 frames.
It records the same amount of frames for both YUV and RAW, just the extension changes for the file.
On my card, I have the following:
ROOT/ML/MODULES
raw_rec.mo
MAGIC.SYM
lv_rec.mo
ROOT/ML/SCRIPTS
(EMPTY-Should there be something in here?)
ROOT
Latest autoexec.bin
Hey dude! What he means is you are using something totally different to everyone else to try and record RAW video. I did it - we all did it, it's cool 8)
The place you need to look for this feature is not in the L tab but if you scroll over to the Movie tab (looks like a video camera) and then scroll all the way down (you can't see it unless you scroll down off the screen) and you will see "raw video". There you will find he hidden treasure ;)
Let us know how you get on!
Quote from: electrichobo on May 18, 2013, 02:34:13 AM
i'd love you long time!
On it dude :) Have just written it - just need a Pro to proof it for me, give me an hour or so and it'll be posted here and then in it's own thread. :)
Quote from: teo770 on May 18, 2013, 12:53:53 AM
1% told me if i don't do FPS override in PHOTO mode, it will record at 30 fps...
But 1% is in a NTSC zone (US). We in EU, use PAL so 25fps
For each resolution test, i have registered recorded 4GB..
Sorry my crappy english !
Ah! Lol :) You're English is good man - no worries!
Okay! My camera records 30fps in Photo mode with no override so that's interesting. Mine is potentially an imported version though so who knows?
Quote from: noisyboy on May 18, 2013, 03:55:30 AM
Hey dude! What he means is you are using something totally different to everyone else to try and record RAW video. I did it - we all did it, it's cool 8)
The place you need to look for this feature is not in the L tab but if you scroll over to the Movie tab (looks like a video camera) and then scroll all the way down (you can't see it unless you scroll down off the screen) and you will see "raw video". There you will find he hidden treasure ;)
Let us know how you get on!
Thanks! This is too awesome =D
Quote from: sparedog on May 18, 2013, 04:25:10 AM
Thanks! This is too awesome =D
Ya damn right it is Sparedog! Ya damn right 8)
With the possibility that the Canon 6D can shoot RAW, it is more suitable to be a B-Roll camera with my Black Magic Cinema camera?
First thing sorry for my bad English. Just want to help you guys to test 6D raw.
With me 1440*600 is great, no frame skip at all. I think this will be best way right now for us.
133% upscale is enough for me right now (Sandisk 95mb/s card)
https://www.youtube.com/watch?v=D0-NjjBel4o&feature=youtube_gdata_player
This is my short grading test raw...
Quote from: noisyboy on May 18, 2013, 04:00:29 AM
Okay! My camera records 30fps in Photo mode with no override so that's interesting. Mine is potentially an imported version though so who knows?
Even imported (mine came directly from Japan with a stop by London: purnimadigital.com),
i can choose btw PAL and NTSC in Canon menus. You can't ?
Quote from: teo770 on May 18, 2013, 09:44:01 AM
Even imported (mine came directly from Japan with a stop by London: purnimadigital.com),
i can choose btw PAL and NTSC in Canon menus. You can't ?
Yeah I can select PAL or NTSC but it only affects the frame rate in video mode. My understanding (which could be wrong) is that when you switch to
photo mode it defaults to 30fps anyway, no matter which zone you select. I thought this because that's the frame rate that is displayed at the bottom of the screen in the Magic Lantern "RAW video" sub-menu displays 30fps (well, 29.xxxfps),
That's why I have been using fps override :)
Quote from: pio_hyun on May 18, 2013, 05:28:04 AM
First thing sorry for my bad English. Just want to help you guys to test 6D raw.
With me 1440*600 is great, no frame skip at all. I think this will be best way right now for us.
133% upscale is enough for me right now (Sandisk 95mb/s card)
https://www.youtube.com/watch?v=D0-NjjBel4o&feature=youtube_gdata_player
This is my short grading test raw...
Looks good man :)
Quote from: noisyboy on May 18, 2013, 02:52:47 PM
I thought this because that's the frame rate that is displayed at the bottom of the screen in the Magic Lantern "RAW video" sub-menu displays 30fps (well, 29.xxxfps),
That's why I have been using fps override :)
Mine displays 23.976fps WITHOUT FPS override... strange !
In Canon's menus: PAL and 1920 / 24p IPB selected in movie mode.
Quote from: noisyboy on May 18, 2013, 02:54:24 PM
Looks good man :)
thanks. can you tell me how to test card write speed with newest update? Download and copy Autoexec.map into Root folder but nothing happen in ML Menu @.@ Really confuse now...
In theory:
PAL - no 30P in menu, movie mode @25P, photo mode at 30P, zoom at 30P
NTSC - 30P in menu, movie mode 24P, photo mode at 30P, zoom at 30P
You're never supposed to be recording "officially" from photo LV so I think canon just sets 1 fps for everyone. The HDMI outputs at XXXXi resolutions (and buffer is separate) so never a problem for external display. 30P seems like a default.
*autoexec.map? did i put the wrong file in? Ha yes. I did, fixed now. Yesterday was fuct.
Quote from: 1% on May 18, 2013, 03:28:07 PM
In theory:
PAL - no 30P in menu, movie mode @25P, photo mode at 30P, zoom at 30P
NTSC - 30P in menu, movie mode 24P, photo mode at 30P, zoom at 30P
You're never supposed to be recording "officially" from photo LV so I think canon just sets 1 fps for everyone. The HDMI outputs at XXXXi resolutions (and buffer is separate) so never a problem for external display. 30P seems like a default.
*autoexec.map? did i put the wrong file in? Ha yes. I did, fixed now. Yesterday was fuct.
just downloaded newest *.zip file. testing right now :)
Quote from: 1% on May 18, 2013, 03:28:07 PM
In theory:
PAL - no 30P in menu, movie mode @25P, photo mode at 30P, zoom at 30P
So in RAW video section, the ML displayed fps is wrong ?
(While in recording PAL in photo mode without fps override)
I forgot the .map !! Need to be placed with the autoexec.bin i presume.
No change with autoexec.map, same perfs.
Something happens with the 4th buffer... since it exists i would say.
Once the 3rd buffer is full, it starts skipping frames like if the 4th buffer just didn't exist... The 4th doesn't have time to blink like the others.
Testing [113] HackLV.zip
1536x600, photo mode fps overide off: 35.7MB/s: skips frames after 1273 frames
Buffer size experiment
ML v2.3.NEXT.2013May18.6D113, 25d36d43a82c (unified) tip
Mode: playback, Global Draw: ON
10312704 407
15885312 419
80896 145
8949760 409
28661760 411
16264192 411
24521728 413
16424960 415
13148160 411
15619072 411
1658880 379
21001216 411
8548352 407
19760128 408
5965824 404
24906752 414
13968384 410
16770048 412
4542464 402
13063168 409
33263616 412
30312448 417
16713728 412
3887104 399
21841920 409
12846080 416
16192512 409
3333120 395
6719488 404
17313792 413
23374848 409
2865152 393
32488448 412
18588672 411
4186112 402
821248 349
3661824 400
18359296 408
19875840 409
22754304 414
13665280 410
24957952 412
28555264 414
33442816 411
10708992 408
20242432 410
8774656 406
11216896 412
23156736 411
12750848 410
12369920 415
2157568 386
15279104 409
29943808 416
30321664 412
19004416 409
268288 266
23778304 409
467968 312
1905664 383
32368640 410
19829760 411
26281984 410
24153088 412
11364352 407
32160768 409
5944320 402
24118272 407
28511232 414
31526912 414
15956992 413
1732608 380
13881344 410
6106112 403
17367040 411
21693440 408
30835712 417
1139712 307
test about 10mins :)
Card: Sandick Extreme 95mb/s
Post results to the other thread where al1ex is making the graph.
I dunno about FPS then, maybe I should leave the indicator up and look in both NTSC/PAL... either way its probably going to be fps you're not trying to use.
The map file was the wrong file dragged into the zip so shouldn't work for anything... ooops. Today's ver is fixed.
4th buffer may be getting composed of smaller chunks. Memory allocation still needs more work. Try a recording test with LV edmac disabled. It helped me a bunch.
Testing raw_rec.mo - 4gProper: LV on, photo mode
1504x600 35.1MB/s Global draw ON, FPS override ON: 20 skipped frames in a 4GB record
1504x600 35.3MB/s Global draw ON, FPS override OFF: 16 skipped frames in a 4GB record
1504x600 35.6MB/s Global draw OFF, FPS override OFF: 0 skipped frames in a 4GB record
1504x600 35.6MB/s Global draw OFF, FPS override ON: 0 skipped frames in a 4GB record
1536x600 36.0MB/s Global draw OFF, FPS override ON: 24 skipped frames in a 4GB record
1536x600 35.9MB/s Global draw OFF, FPS override OFF: 24 skipped frames in a 4GB record
1536x580 35.6MB/s Global draw OFF, FPS override OFF: 0 skipped frames in a 4GB record
1600x580 35.6MB/s Global draw OFF, FPS override OFF: 65 skipped frames in a 4GB record
1536x580 35.6MB/s Global draw ON, FPS override OFF: 0 skipped frames in a 4GB record
what about lv hack on vs off
its supposed to. to get better write. i get 28mb vs 27
Excuse me and sorry for my bad English first.
I am a new 6D user and upgraded from 60D with ML.
I have tried to install the ML on my 6D many time but it is still unable to boot ML after flash 6d firmware.
I don't know which part i did wrongly.
May you professionals share the right step for installing ML on 6D?
Thank you so much!
With raw_rec.mo - 4gProper, hack ON:
1536x600 36.8MB/s Global draw OFF, FPS override OFF: 0 skipped frames in a 4GB record
1536x640 Global draw OFF, FPS override OFF: stopped recording
1600x580: 36.5MB/s Global draw OFF, FPS override OFF: 0 skipped frames in 4GB recording but stopped just after
in a future modif, could you add height: 620 ?
Quote from: RYAN2310 on May 18, 2013, 05:11:25 PM
Excuse me and sorry for my bad English first.
I am a new 6D user and upgraded from 60D with ML.
I have tried to install the ML on my 6D many time but it is still unable to boot ML after flash 6d firmware.
I don't know which part i did wrongly.
May you professionals share the right step for installing ML on 6D?
Thank you so much!
Did you use EOSCard ?
Ok, will add 620.. so slight increase at the loss of seeing people step out of frame, etc.
Quote from: teo770 on May 18, 2013, 05:21:58 PM
Did you use EOSCard ?
Yes, and my firmware is 113
Did you downgrade to 112, run developer fir and then upgrade to 113?
Hello
someone who can write me step by step how to install ?
My firmware is 113
Cheers
Naming convention idea
Yesterday, I was thinking (!):
M-jpeg exists to name a movie based on jpeg files.
We are doing raws (DNG).... ML raw video format sould be M-RAW !
Perhaps MRW because of FAT32 limited 8+3 chars...
Or you plan to package it as CinemaDNG ?
(bunch of DNG files in a dir or mutiple DNG concatened in a file + meta infos)
Not sure where its going... Been thinking about different naming schemes, date/time, mraw, etc.
Right now it kinda works. Cinemadng would be decent and a better format vs, record solid file, breakup solid file, recombine. I guess we'll see what happens on 5d3.
Quote from: 1% on May 18, 2013, 05:25:10 PM
Ok, will add 620.. so slight increase at the loss of seeing people step out of frame, etc.
\
how about separate WAV sound record? i have updated to lastest raw_rec.mo file but seem not possible :'( still drop after 5 or 6 second :)
Separate wav works fine... if you drop the resolution (at least it did yesterday or day before). We're struggling to write out video so audio kinda kills it. You have to set separate wav in the module either way, can set it on the audio menu to see meters.
with lastest .mo file:
1360x600 with WAV is fine, sound was droped after 650 frame~
in the next commit could you add 1410 in width :D Just like 2,35:1 ratio :)
FPS override behaviour...
In PAL zone, we can choose btw 1920-24p IPB and 1920-25p IPB in Canon's menus.
If i set 24p, FPS override tells me:
Desired FPS: 24 (from 24)
If i set 25p, FPS override tells me:
Desired FPS: 24 (from 25)
Quoteyou add 1410
Didn't we try this res and it was bad?
That FPS behavior makes sense... but what is FPS in photo mode? It should show you in the override menu I guess.
Quote from: 1% on May 18, 2013, 06:41:34 PM
That FPS behavior makes sense... but what is FPS in photo mode? It should show you in the override menu I guess.
Same in photo and video modes.
But i just discovered a new thing....
I make all my tests in a personnal mode C2, which is a copy of the M mode in my cam.
Both in photo & video mode, if i use liveview inside with bulb lighting, C2 and M are not acting the same at all !
In C2, liveview seems 24 or 25p, clean image, in M liveview is running at 30p (can see light waves) !
In M mode FPS override tells it's 24p but i can see the liveview is in 30p !
So... using personal modes... we wouldn't need FPS override to get real 24p ?
So I guess does lots of weird stuff in pal mode? I always use C1p, C2m or something like that for safety. Zoom and photo is always 30P for me set to NTSC.
Perhaps you sould try C2m in PAL to see if it's acting the same as mine ?
Diferently than M mode i mean.
Perhaps it's only a LV shooting convenience only.... showing 25p, but ML recording 30p. That's possible ? No IMO cause you are recording liveview frames... at liveview's fps.
Look at what the timers say in FPS override I guess.
Mode C2m
Photo mode: timer A 532 (-14) timer B 2005 (+49)
Video mode: the same
Mode M: same timers
Photo mode: timer A 532 timer B 2005
Video mode: timer A 532 timer B 2005
It's chinese to me
Don't want to bother, just whiling to see if it could help in devs.
If it's just a weird acting due to PAL, forget that.
Override it and it will say xxfps out of XX fps.
Ok. I'm kinda lost to how to update to 113.
I currently have the developer firmware (1.1.2) and ML firmware (6D-112.fir) installed. To upgrade to 113, I upgrade to camera to 1.1.3 (developer). Now is there a ML 6D-113.fir or I simply reinstall 6D-112.fir?
Once I upgraded ML, there is a lot of files on bitbuckets. Do I update each files one by one (or all together?)
Once you have the bootflag set on 112 and you're using ML you can just put 113 file on the card and upgrade. Then when its done turn off the camera and get the latest 113 bin to make ML work again.
Quote from: 1% on May 18, 2013, 07:53:39 PM
Once you have the bootflag set on 112 and you're using ML you can just put 113 file on the card and upgrade. Then when its done turn off the camera and get the latest 113 bin to make ML work again.
Ok. Sorry to bother you again but...
1) Which 113/113 bin files precisely? I look at bitbucket and theres like 50 files on it.
2) Where do I put the RAW files on the card? Root? On Modules? Or ML?
Latest is greatest in theory.
113/112/developer fir are all fir files.
I updated the camera. Just a few problems. One, display infos (iso, aperture, grid, picstyle) doesnt come up in normal mode. I have to use ML to see them.
Second, I have RAW files missing when I tried to loads the modules (raw_lv_disable. raw_set_geometry)
Info's come up from the info button. You can either have ML or info... H/s is set to block canon drawing by design.
Raw files missing? Its in movie tab: raw video.
I get a tcc: error: underfined symbol (all the raw stuff: raw_force_aspect_ratio, raw_info. etc) with [E] failed to link modules.
Yeah, I press info but noting comes up.
You need to make sure MAGIC.SYM and autoexec.bin version match.
Ok. Nice. It worked. The only thing is I have a blue sky like bar at the bottom of the screen that wont go away. Something called kel? And I can't record more then 4 seconds in normal mode.
Now, how do I record RAW? I put up ML, then LV, and record?
Go in ML menus, M choice, then Load modules now
Then ML Movie menu, last choice, RAW video, btn SET
Btn Q to set a width and height dipending of your SD card speed, try 1360x580 first
Quit ML menu then hit Start/stop recording as usual
Quote from: teo770 on May 18, 2013, 11:33:39 PM
Go in ML menus, M choice, then Load modules now
Then ML Movie menu, last choice, RAW video, btn SET
Btn Q to set a width and height dipending of your SD card speed, try 1360x580 first
Quit ML menu then hit Start/stop recording as usual
I seem to have to do this after every power down. Is this how it works at the moment?
You can set the modules to load at startup.
Can someone please tell me where I can download the 6D 1.1.2 firmware? I'm on 1.1.3 and want to downgrade so I can install ML. Thanks.
Quote from: benratner on May 19, 2013, 02:57:32 AM
Can someone please tell me where I can download the 6D 1.1.2 firmware? I'm on 1.1.3 and want to downgrade so I can install ML. Thanks.
Hey man, if you (and anyone else who wants this) can hold out 'til later on tomorrow bro then I'll be uploading everything you need in a zip and a simple to follow guide for those who don't know where to start with this. Best this way so the Devs can carry in kicking some Magic Lantern Ass :) Just need to test my own guide a few times to make sure I don't ruin anyone's day. Just hold tight a little longer bud :)
Peace!
Quote from: noisyboy on May 19, 2013, 05:01:53 AM
Hey man, if you (and anyone else who wants this) can hold out 'til later on tomorrow bro then I'll be uploading everything you need in a zip and a simple to follow guide for those who don't know where to start with this. Best this way so the Devs can carry in kicking some Magic Lantern Ass :) Just need to test my own guide a few times to make sure I don't ruin anyone's day. Just hold tight a little longer bud :)
Peace!
Thanks dude!
Quote from: noisyboy on May 19, 2013, 05:01:53 AM
Hey man, if you (and anyone else who wants this) can hold out 'til later on tomorrow bro then I'll be uploading everything you need in a zip and a simple to follow guide for those who don't know where to start with this. Best this way so the Devs can carry in kicking some Magic Lantern Ass :) Just need to test my own guide a few times to make sure I don't ruin anyone's day. Just hold tight a little longer bud :)
Peace!
Thank you so much :'(
can you guys help me out? where can i get the build for the 6d?
It took me one hour to figure out how to install with 113, I switched between 112 and 113 at least 3 times trying to figure out if I had to do something in a particular order, that and the EOScard thing, formatting etc... I'm still not 100% sure how I did it but it works.
If someone can make a zip with everything included and a quick step by step guide it will help a lot of people. Then updating the modules and bin is very easy.
Thanks to everyone working on this, you're doing an amazing work.
Quote from: Virindi on May 19, 2013, 09:44:29 AM
It took me one hour to figure out how to install with 113, I switched between 112 and 113 at least 3 times trying to figure out if I had to do something in a particular order, that and the EOScard thing, formatting etc... I'm still not 100% sure how I did it but it works.
If someone can make a zip with everything included and a quick step by step guide it will help a lot of people. Then updating the modules and bin is very easy.
Thanks to everyone working on this, you're doing an amazing work.
Cool to see you joined the party:) I have just walked in from a 22 hour shift so for now I need to sleep but the guide is sorted and the zip sorted too, as soon as I'm awake and feeling a little more like a human being I'll post/upload it to a new thread and link to it from here. Cheers :)
In some resolution tests, got an error: Footer save error
Quote from: Versus on May 19, 2013, 08:54:05 AM
can you guys help me out? where can i get the build for the 6d?
Lol ;D come on dude, you only had to read the post before yours to get your answer to this question. Just a little patience and all shall be revealed 8)
Is there any difference between photo mode and video mode when recording RAW?
QuoteIn some resolution tests, got an error: Footer save error
How do I reproduce it?
Photo mode is slightly faster if you override FPS.
Quote from: 1% on May 19, 2013, 02:40:37 PM
How do I reproduce it?
Photo mode is slightly faster if you override FPS.
Try to record 1600x544
I did... worked, frames opened up. Only 272 frames.
QuoteFooter save error
4GB limit reached, or card full.
Photo mode, recording 4GB on Sandisk Extrem Pro 32GB
1440x620 global draw off : 0 skipped frames
1440x620 global draw on : 0 skipped frames
Question: when recording, speed displayed is the MB/s issued from liveview of the write speed to the card ?
In RAW video menu choice, there is an estimated write speed needed. If global draw is OFF or ON, it displays the same MB/s.
Global draw normaly only consumes CPU, no ?
Probably 32GB card is fat32?
No, exFAT 4096k clusters
Got 2 same cards Sandisk Extreme Pro 32,
1 formated FAT32
1 formated exFAT 4096k clusters
i try all tests on both but till now, the exFAT always ends first so i report only his results.
Lastest raw_rec.mo:
In Video mode, recording 4GB on Sandisk Extreme Pro 32GB
1440x620 global draw off : 0 skipped frames
1440x620 global draw on : 0 skipped frames
The raw clips I am shooting are not playing back real time in after effects. They are slightly sped up. Anyone else had this problem?
Quote from: sparedog on May 19, 2013, 04:51:12 PM
The raw clips I am shooting are not playing back real time in after effects. They are slightly sped up. Anyone else had this problem?
change your DNG clip framerate from 30fps to 24fps. Default value of After Effect always 30fps so you need to change it.
Quote from: pio_hyun on May 19, 2013, 04:58:22 PM
change your DNG clip framerate from 30fps to 24fps. Default value of After Effect always 30fps so you need to change it.
Thanks, it´s better now
@1% Would it be possible to remember the last size setting set, so for example, if I want to shoot 720*1280, it returns to that on next startup?
I think the config file must not be working for modules, they are commented out. I'd like sync beep off by default and LV hack on too. Will try and see.
Photo mode, recording 4GB on Sandisk Extreme Pro 32GB
1440x620 global draw off : 0 skipped frames
1440x620 global draw on : 0 skipped frames
1840x480 global draw off : 0 skipped frames
1840x500 global draw off : 48 skipped frames
So getting a little better?
Quote from: teo770 on May 19, 2013, 04:24:23 PM
No, exFAT 4096k clusters
Got 2 same cards Sandisk Extreme Pro 32,
1 formated FAT32
1 formated exFAT 4096k clusters
i try all tests on both but till now, the exFAT always ends first so i report only his results.
Exfat for me worked worse than FAT32. Bizarre.
Sorry - should have made that clear... I know FAT32 gives us problems recording over 4GB but my Delkin card was exfat 4096 clusters and was not recording as fast as my Sandisk Extreme which was FAT32
FS shouldn't make a difference in speed.
Quote from: 1% on May 19, 2013, 02:40:37 PM
Photo mode is slightly faster if you override FPS.
Sorry stupid question but is it faster because of lowered FPS, or still faster even at same FPS and resolution?
Some movie mode stuff doesn't run in photo mode. Also 640x480 mode is faster.
It seems that I have been able to record RAW on 1280x720 (30MB/s??) until the 4GB record limit, with no skipped frame. The RAW file is recorded into one single frame (M0000000.RAW). I can't open the file on Resolve, AE or Adobe premiere.
And I don't know how to record in DNG Raw files? Might need some help with the settings.
Bust it up with raw2dng(.exe)
<4gb windows
>4gb linux
Quote from: noisyboy on May 19, 2013, 05:01:53 AM
Hey man, if you (and anyone else who wants this) can hold out 'til later on tomorrow bro then I'll be uploading everything you need in a zip and a simple to follow guide for those who don't know where to start with this. Best this way so the Devs can carry in kicking some Magic Lantern Ass :) Just need to test my own guide a few times to make sure I don't ruin anyone's day. Just hold tight a little longer bud :)
Peace!
Thank 3 !!!
Right - finally up and alive again! Gonna finish up the guide and start a new thread in a jiffy. Just got to update the zip with all the latest files and run through it again and see if I break my camera. If I don't then we're good to go my fellow newbies.
teo770 and 1% - was gonna basically give the latest bin with the "4 buffers no worries" module as that even though it's not entirely up-to-date, it seems to still give me the best performance and record times when shooting RAW (which lets face it is the reason a lot of people want this). Can either of you think of any reason not to give this one and to give a different version before I continue? After all, they can always update the modules as they are released.
Cheers.
Other than missing features not really. They all work, use the one you want. Hopefully we'll figure out a way to fix it so newer modules get faster. The edmac shutting helps already.
Okay - cool. In the mean time...
Any idea why my benchmarks are looking like this?
Screen goes to black halfway through the 5 min reed/write test and then I get this at the end
Thats all the tests which are enabled I think. Why test at like 128k and wreck your card?
I'll have to see if there is some drawing bug with it turning black and not showing the other stuff.
This is with the latest, first part of write test seemed to show for me, started with 2M buffers.
Is there any chance I might be able to test the 4 buffers no worries with the LV Hack enabled? I think it was the screen shutting down that gave me such high results :) If you get time that is.
In fact it definitely is giving me much better benchmarks. I have no idea why my screen is going to sleep (if it's a feature on the camera I never used it before so maybe I activated something when I rolled back to 1.1.2 and cleared settings?) and I have no idea why when I push a button to wake the screen I loose half of the data drawn on screen but I guess this is the same reason that the Live View hack works?
Also, I have been wondering, is it possible to disable the real-time previews of Picture Styles? So we just go straight through them? Do you think they would affect performance?
There is powersave in canon menus, is that off? Also ML can dim/shut down the screen after x mins in lv power-save menu. Something else has to be worked out with the memory to get stability + the performance back. Maybe need to print what chunks are being used.
Picture styles won't make a difference. I don't think they use a separate edmac.
Quote from: 1% on May 20, 2013, 03:49:10 AM
There is powersave in canon menus, is that off? Also ML can dim/shut down the screen after x mins in lv power-save menu. Something else has to be worked out with the memory to get stability + the performance back. Maybe need to print what chunks are being used.
Picture styles won't make a difference. I don't think they use a separate edmac.
Ah - I see! Fair enough!
Yeah - LV Powersave was on - thanks! Crazy that it benchmarks that much better with the screen shutdown though eh!
Any newbie lurkers that like dicing with death want a quick go of this installation guide before I post it publicly then PM me. I have tested it and the files like 5 times and only broke 2 cameras so it's cool.
Of course I'm kidding - I have tried it 5 times and it worked fine but please remind yourself that you do this at your own risk before you commit to it 8)
Ps. Windows only at the moment.
Thats why I say to shut down more edmacs....
I looked at buffers, the double is only a 6MB chunk... but I think the other chunks are not even. 124MB is allocated total.. buffer 4 prints as 31MB... buffer 3 says 32Mb. I can't see buffers 1 + 2 so I wonder if chunks are all different sized now causing the slowdown.
And I guess make a new thread so it can be added to the raw recording thread under 6D.
with lastest build I have some kind of crash when try to playback .RAW file on camera.
LV not work at all and when i turn off camera and turn on again, it shows Error 70. So I have to pull the battery to turn on camera again.
Here is LOG file:
ASSERT: 0
at ./Capture/Capture.c:526, task EventMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013May18.6D113
Mercurial changeset : 25d36d43a82c (unified) tip
Built on 2013-05-18 12:57:24 by user@D610.
Free Memory : 450K + 2097K
Couldn't reproduce it. I could play back in photo mode and movie mode and zoom 5x.
Maybe order of the chunks matters.. the short chunks are at the beginning and buffer 1+2 get filled quickly. In the other bin putting the smallest buffer on the end as better.
Quote from: noisyboy on May 20, 2013, 04:28:25 AM
Any newbie lurkers that like dicing with death want a quick go of this installation guide before I post it publicly then PM me. I have tested it and the files like 5 times and only broke 2 cameras so it's cool.
Of course I'm kidding - I have tried it 5 times and it worked fine but please remind yourself that you do this at your own risk before you commit to it 8)
Ps. Windows only at the moment.
ill take a peek. and mayhaps adapt for an OSX
Sensor size...
In this BMCC review, you will see compared sensor sizes btw Canon 5D/6D and Pro cinema cameras...
BMCC has a sensor 5 times smaller than 6D...
http://www.focus-numerique.com/test-1690/camescope-blackmagic-cinema-camera-sur-le-terrain-2.html
Google translate is your friend...
I'm wondering... what could be the pixel size on the BMCC !
There are also crop factor issues with those cameras due to sensor size.
I LOVE my 6D ! So bad they didn't include a damned CF card slot !
Amazing too, at the end, using BMCC or 5D/6D RAW video, you will get same workflow (speaking about PC for myself):
DNG files + audio as a wav file => imported in your fav NLE, After Effect / Premiere and so on.
I wonder, how 1504x640 raw (or similar) upscaled to 1920x817 looks in comparison with BMCC's ProRes4444 or 422HQ in terms of quality, sharpness, detail etc. I've found some info about BMCC bitrates:
2048x1080 24fps - Prores422 HQ 201Mb/s, prores4444 302 Mb/s
1504x640 24fps RAW ~ 300Mb/s
Did you guys see such a comparison somewhere?
Quote from: kgv5 on May 20, 2013, 12:43:32 PM
I wonder, how 1504x640 raw (or similar) upscaled to 1920x817 looks in comparison with BMCC's ProRes4444 or 422HQ in terms of quality, sharpness, detail etc. I've found some info about BMCC bitrates:
2048x1080 24fps - Prores422 HQ 201Mb/s, prores4444 302 Mb/s
1504x640 24fps RAW ~ 300Mb/s
Did you guys see such a comparison somewhere?
Yeah that would be nice :) Haven't seen anything other that 1080p comparisons on mk3 yet though.
Might be renting a couple on next shoot so if I do I'll do a comparison.
Quote from: teo770 on May 20, 2013, 10:14:24 AM
I LOVE my 6D ! So bad they didn't include a damned CF card slot !
Hellz yeah brother 8)
6D perfs
As we've seen, a good card as Sandisk Expreme pro xxGB can write at 82-3MB/s in a SD card reader.
As you discovered, the chip managing SD card I/Os in the 6D seems limited to 50MB/s (SDR50 or something)
Why in the benchmarks can't we bench at 50MB/s ? But only at 41-42MB/s max...
Is it because of CPU power ? Or ML can't free enough memory (yet) for buffers to sustain higher write speeds ?
That is a good question, hope it's not a some kind of canon's hardware limitation
I would guess 2 things:
1. Overhead.. cpu, etc
2. Card only supports speed X in SDR50 mode.
SD cards speed description:
https://www.sdcard.org/developers/overview/bus_speed/
Sounds like 6D is UHS-1 SDR50
Actually by MHZ I think DDR50
If we had full UHS-1 people would be wondering why they are only getting 80MB write instead of 90, etc....
It seems recording sound as separate wav makes a very big difference in performance.
At 24FPS, I can get good results at 1440 x 640 without audio (it says 36.9Mb/s), the buffer fills up slowly.
But only 1200 x 600 with separate wave (28.8Mb/s) the buffer stays empty. If I try any higher resolution it breaks the sound recording in less that 10 seconds.
Is it normal?
Pretty much.. sound takes up a bit of write. We're short as it is. 5d3 is the only lucky one that can record audio to SD while recording video to CF.
Does "beep" sound works in the newest "raw_rec.mo -shrinkwrite" build? I have it ON - there is no sound but maybe there is some setting I missed. In some of the previous versions it was ok.
Quote from: kgv5 on May 20, 2013, 04:36:11 PM
Does "beep" sound works in the newest "raw_rec.mo -shrinkwrite" build? I have it ON - there is no sound but maybe there is some setting I missed. In some of the previous versions it was ok.
For bip sound, use
Waveform: Sine
Tome frequency: 1760 Hz
Worked like that for me.
I just checked.. its not beeping for some reason. Wav is recording tho.
5X framing preview not working either... wonder if it was taken out.
1%, about buffers. Has i understand, you have the ability to dim a few buffer chunks, around 30MB, and the last buffer is made of the last free memory adressable so size may vary. Right ?
You allocate buffer chunks dynamicly at the beginning just before recording ? Acording to free mem available ?
During recording, you have the hability to resize buffer chunks ?
Another dumb question:
For testing purpose, is it possible to record black & white DNGs ?
Without color data, DNGs would be smaller we could record full HD perhaps... I know it sounds silly recording RAW in W&B but, it's a test, to see how far the 6D can go in resolution...
lastest file:
Global Draw ON: 1440x620 drop frame after 1780 frames
Global Draw OFF: 1440x620 drop frame after 2280 frames :D
Not sure how you would throw away all the chroma.. I know a1ex did it for playback.
You can't really resize the memory while recording.. I think the problem now is that smaller chunks are being used first and larger chunks end up at the end. Should be largest first and smallest last... that's how that 4 buffers module worked. The double buffer size is still 6M so that's not the problem.. its better actually.
But if you're blinking on buffer 2 and that chunk is 27MB only then I can see how that slows down writes. Maybe on 5d3 all chunks are >30MB? Even taking off the 4th star (expanding double buffer) and recording with the 3 larger buffers sped things up.
And buffer chunks are feeded sequencialy ?
When buffer 1 full, buffer 2 start to be feeded.. etc
As raid 0, to enhanced write speed, you can't create 2 buffers writing at the same time ?
Having 2x30MB + 2x30MB buffers feeded in the same time ?
I don't know if i am clear, perhaps it has already been explored ?
Probably cpu limitations/multitasking applies too.
There is probably a botleneck somewhere slowing down writing ops.
You can't get 2 writes at the same time.. this would work on a PC but we don't have bandwidth as it is. Want as few of most efficiently sized writes. If writing ~2X mb is causing problems vs 31, 64MB write would be worse.
New thread for general discussion of Magic Lantern and RAW shooting on 6D can be found here:
http://www.magiclantern.fm/forum/index.php?topic=5530.msg37766#msg37766 (http://www.magiclantern.fm/forum/index.php?topic=5530.msg37766#msg37766)
Installation guide can be found on first page.
*If anyone who is using this thread for it's intended purpose wants to bookmark this page you can just copy and paste the above text to any queries relating to installation.
Thanks.
(now I can return to actually testing this thing myself! Hooray) :)
Interesting benchs about some popular SD cards:
http://www.hjreggel.net/cardspeed/cs_sdxc.html
Looks like 1% was right about them taking about 5% off the actual theoretical rate lol
(just realized how stupid that sentence sounded considering 1%'s name! Haha!)
Hi, since las saturday commits till today last commits I've found two issues, on the downloadable bins or on the bins compiled by myself.
1) After I take the first raw video, the AF is gone: I can only do manual focusing after that. No AF on "AF-ON" nor the shutter button or whatever button with AF configured into.
2) After previewing raw video, I can no longer do 5x zoom: the magnifier button do nothing. But, as workaround if I activate silent pics burst and after doing a burst, 5x zoom comes alive. I think this was previously reported
And since last builds, the brilliant pixels on fps override on underexposed LV, are gone!!!!.
Perhaps it's because this commit:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/01b2a6799e16989f532086c37131acb4ce7d9c0a
I can't reproduce again, it's a pity.
Release: [113] Sorting.zip
Card: Sandisk extreme pro 32gb (95MB/s)
Mode: Photo LV
Recording: 4GB
1536x580, global draw off: 0 skipped frames
1536x580, global draw on: 0 skipped frames
1536x600, global draw off: 39 skipped frames (and 46/55 skipped frames in video mode)
A1ex took off the AEWB hack and overlays are fixed so zoom button/af is hopefully not fucked up any-more.
Buffers sorted better?
OK, after last commits the two issues were gone!!!
I not found any difference with previous versions (Sandisk Extreme-Pro 95 MB, 32 GB, FAT32 formated in camera):
105 frames 5x in photo mode 1880x680 24 fps (override)
113 frames in photo mode 1880x680 24 fps (override).
208 frames 5x in photo mode 1600x680 24 fps (override).
4th buffer still an issue imo.
Any possibily we could choose buffers size in debug menu ?
So we could test 25/26/27/28/29/30 all sizes ?
If we get a given size of free memory (ex 100MB),
we set 25MB, would use 4 buffers
we set 20MB, would use 5 buffers
and so on...
Perhaps even buffers numbers so we could test every combination.
Hard/long to add or you already tested all possibilities ?
5/6 persons testing all buffers combinations.... we would definatly clear this question.
And verify card speed dependance. Perhaps some buffer size works better with faster cards, some other better with slower cards.
I tried a bunch. There is data on buffer sizes in the thread where everyone ran tests. Right now its using 31 and some.
I tried both orderings, small to big and big to small. Got more frames regularly on the one thats in now, it was +/- 100 frames. Doing it the opposite way I got less frames most of the time but one time I hit a burst write of 30MB/s. Seems to do *something*
1600x680 photo mode fps overr24 no zoom 209 frames, hack 225 frames
I tried dozens of combinations disabling Canon features and enabling no ML features but RAW_rec....
ExFAT vs FAT32
Gain = 0 frames or so few :(
I know Sandisk Extreme Pro can handles up to 80MB/s
It seems that all is in your hands 1%.... (!)
Too bad we can't help more.
Will continue to test and report every update !
Hack definitely helps but buffer order still up in the air. *seems* to be doing something...
I'm kinda out of things to try. Only thing left is more memory.
Think the issue with the last buffer is this:
Star means the buffer is full. Last buffer is the one its using.. that buffer fills and it either has to stop or skip frames.
Do you know if the DNGs contain a jpeg preview ?
Without preview, files are 5-8% smaller...
Could gain some write speed.
I think preview was taken out... for this it just saves raw data. raw2ng was making the jpeg previews, etc.
Another way:
Use that kind of adapter and solder a S-ata port at the end !
http://www.ebay.fr/itm/SDHC-SD-Card-Reader-Extension-Cable-KZ-B19-FPC-/161027485292?pt=LH_DefaultDomain_0&hash=item257dfc6e6c
:)
Whoa, I wondered if such thing exists and here it is :)
Quote from: teo770 on May 21, 2013, 08:36:27 AM
Another way:
Use that kind of adapter and solder a S-ata port at the end !
http://www.ebay.fr/itm/SDHC-SD-Card-Reader-Extension-Cable-KZ-B19-FPC-/161027485292?pt=LH_DefaultDomain_0&hash=item257dfc6e6c
:)
haha! Good find! Doubt the camera would write any faster though even if you did use that.
This is interesting from a1ex over in the "uncompressed 14-bit RAW video recording" thread:
Quote from: a1ex on May 21, 2013, 08:49:45 AM
There was some slowdown in 5x after fixing the tearing (this required some more memory). Just pushed a fix that should restore the old speed (almost).
Quote from: noisyboy on May 21, 2013, 10:51:23 AM
haha! Good find! Doubt the camera would write any faster though even if you did use that.
Not faster for sure but there would be an option to have much more data storage.
Quote from: kgv5 on May 21, 2013, 11:00:08 AM
Not faster for sure but there would be an option to have much more data storage.
Very true! Just ordered one ;)
About SD to S-ata adaptator...
Faster perhaps not in burst but perhaps a SSD would have write access times lower than SD cards... who knows.
And price for a 256GB SSD is lower thant fast 256GB SD card !
I'm not for this solution.... made of wires out of the cam and scotch/taped.... burk !
I know 1% wants to explore the grip way, much better solution IF the usb wirering inside is fast enough.
Even if we had the same speed of actual SD slot.... would add another SD card slot in the grip for example and guess what ?
Canon 6D + 2 SD card slots..... i'm pretty sure ML would figure out how to write on both so we would have 2x35MB/s ! ;)
After, 1st frame on internal SD card, second frame on grip SD card.... and so on.... audio....
Why not ?
Wouldn't be surprised that "gigabit lan" interface in the WFT-E7 Wireless File Transmitter is wired with a kind of USB to LAN
interface.... Would be a bad news....
Quote from: teo770 on May 21, 2013, 11:08:41 AM
I'm not for this solution.... made of wires out of the cam and scotch/taped.... burk !
I know 1% wants to explore the grip way, much better solution IF the usb wirering inside is fast enough.
Yeah - no doubt! I'm just fastinated about whether it can be made to work :)
Its great we have one of those adapters. Unfortunately SD isn't like CF. CF is pretty much IDE so its plug and play. SD is a different serial interface. Don't know if there is any kind of SD to IDE adapter, I haven't seen one.
The recovery commit won't do us much good I think... the double buffer is using a 6MB chunk. Next chunk is ~30MB, next smallest is 2MB.
Quote from: 1% on May 21, 2013, 02:52:35 PM
Its great we have one of those adapters. Unfortunately SD isn't like CF. CF is pretty much IDE so its plug and play. SD is a different serial interface. Don't know if there is any kind of SD to IDE adapter, I haven't seen one.
The recovery commit won't do us much good I think... the double buffer is using a 6MB chunk. Next chunk is ~30MB, next smallest is 2MB.
Potty :) Ah well - I'm just stoked to use what I already have anyway now so whatever else you manage to get is a bonus for me!
Thought you can pretty much stuff an SD car into an IDE cable? Sure I saw that somewhere once?pretty sure its possible and that the sd connectors line up like half way down the IDE connection.
I bet i could use that adapter i ordered and snip the end off then solder it 1 to 1 with the SD socket on this http://www.ebay.co.uk/itm/SD-SDHC-Secure-Digital-MMC-to-SATA-Converter-Adapter-/171028513929 or I could get two cables and make like a male to male SD cable.
That adapter goes the wrong way.
Lots of SD card to IDE/SATA but no sata/IDE to sd card. Male to male not going to work.
Noisyboy, soldering something to the cable i talked earlier was neer a joke.
The cable itself would help but we first need a female S-ata device which can deal btw a S-ata on 1 side and SDcard on the other side... It's not simple... Perhaps a external hardrive with a SDcard slot like a card ripper but i remember my last one, tried with a SSD in it.... damned slow !
It's because of his design. Mainly, the card reader part in built like a USB reader and interfaced to the S-ATA disk...
I never saw another kind of design.
Perhaps the need of more memory will leads ML to disable any photo features in C2m mode (for example)...
I mean, while recording video in C2m ... noone needs photo ability. Can we disable photo features ONLY in C2m... that's the question.
Or disable all photo features in video mode in general. I tried some memory hacking last night and to resize the resource manager... just got corrupted screen.
Okay - so basically the connection would run the wrong way? Think I see what you are sayin'. Basically I thought it would be a case of connecting the 9 pins on the SD to corrisponding pins on the SSD as my limited understanding was that SSD basically behaves like SD. You dudes are clearly more clued up on this though so I'll take your word for it. Certainly not gonna let it stop me having a bloody good go at something though :)
Found the page I was talking about with SD-IDE and looks like I had it wrong *slaps forhead*
http://hackaday.com/2006/09/12/floppy-connector-mmc-card-slot/
Just gonna slowly walk away from this conversation and forget it ever happened ;)
Imagine if we could record to this via wifi in your backpack: http://www.bestbuy.com/site/WD+-+My+Net+N900+802.11a/b/g/n+Dual-Band+Wireless+Router+with+Built-In+2TB+Hard+Drive/5720675.p?id=1218686490710&skuId=5720675&st=hard%20drive%20wireless&cp=1&lp=2
too bad 6d wifi is slow and cant stream video :(
And the car battery to power it up in ur backpack ! ;)
there are other ones much smaller and with built in batteries. What Im trying to figure out if you can record to these hard drives or they are just for streaming
I think you could, this dude just copied files from ipad (5:25) to the hard drive so it goes both ways- right? http://www.esorun.com/wireless-hard-drive/49-wireless-external-hard-drive.html
I'm going to try a simple thing, got a Wifi dongle on a PC, will try to transfer from the 6D, to check the speed.
I think 1% said it is around 15-30
Quote from: teo770 on May 21, 2013, 05:10:11 PM
And the car battery to power it up in ur backpack ! ;)
LOL but.. also needed to run the cam in RAW video mode.
Tethered wifi N using EOS utility.
Liveview is 10-15 fps i think.
When shooting a burst of 5 jpeg S2 (2.5MB each), transfering is rather SLOW...
Transfering a single RAW (22.2MB) => 11 seconds
Wifi will be a hard option. Imagine, while testing RAW video, i m pleased to have 2 batteries cause LV consumes a lot of power,
add wifi function to that... even the grip + 2 batts will be... for real short shooting !
The real good surprise would be that the USB port in the 6D also acts as USB Host.... who knows ? ;)
1%, you think testing this would be riscky for my 6D ?
http://www.ebay.fr/itm/Cable-Adaptateur-USB-A-Femelle-vers-Mini-B-USB-Male-/280784513642?pt=FR_C%C3%A2bles_adaptateurs_audio&hash=item41600faa6a
(to plug a usb key for example)
Quote from: 1% on May 21, 2013, 04:33:44 PM
Or disable all photo features in video mode in general. I tried some memory hacking last night and to resize the resource manager... just got corrupted screen.
I think this is a good idea. switch to photo mode for photos, video mode for raw video. its easy and if it enables full frame raw video, that would be worth the trouble
Haven't updated modules or bin for a few days as I'm away but have of course read about playing back raw in camera. So is this true - you can now view raw previews or have I read wrong? Probably another bold idea but just wondered - do you think it's possible at all to run this playback through a LUT in camera?
My bad! Just realized I posted this in the wrong thread! Eek!
The adapter is worth a try but not sure if USB hdds work on that port or if there is host mode... I guess you'd have to power the HDD externally and try it. Its only like $2
The playback is only for the last raw.
Quote from: 1% on May 21, 2013, 04:33:44 PM
Or disable all photo features in video mode in general. I tried some memory hacking last night and to resize the resource manager... just got corrupted screen.
Yeah, I would like to try, I bought my 6D mainly for video.
We were discussing such thing before - maybe it would be possible to have ML in two versions on two different cards - first the one we have now - photo + video, second - everything disabled besides RAW video. It would be interesting...
There needs to be a way to do it without switching versions... I shoot photos then shoot video then photos again. Seems possible, just needs research.
QuoteYeah, I would like to try, I bought my 6D mainly for video.
should have gone with 5dm3 for camera A. Moire is so bad on wide angle that I never use it. I use 6d as camera B and only 35mm and up. Speaking of moire, I read an article http://www.eoshd.com/content/10450/2-5k-cinemascope-anamorphic-raw-on-the-5d-mark-iii where this guy is saying that there is no moire with raw cause it scans all 1080 lines and it is not skipping anything. He was talking about 5d but if that was the case then in theory 6d would also have no issues. Is he right about 1080 TV lines I wonder or am I mixing things up cause I still have bad moire...
Quote from: 1% on May 21, 2013, 10:56:18 PM
The adapter is worth a try but not sure if USB hdds work on that port or if there is host mode... I guess you'd have to power the HDD externally and try it. Its only like $2
Just baught one. Will try to plug an USB key at first. If it would work... I should see something with no card in the SD slot
If not working, will mail it to you... perhaps you will get something of it.
Quote from: DTSET123 on May 21, 2013, 11:32:13 PM
should have gone with 5dm3 for camera A. Moire is so bad on wide angle that I never use it. I use 6d as camera B and only 35mm and up. Speaking of moire, I read an article http://www.eoshd.com/content/10450/2-5k-cinemascope-anamorphic-raw-on-the-5d-mark-iii where this guy is saying that there is no moire with raw cause it scans all 1080 lines and it is not skipping anything. He was talking about 5d but if that was the case then in theory 6d would also have no issues. Is he right about 1080 TV lines I wonder or am I mixing things up cause I still have bad moire...
I tried a few records at 1504x600 on the 6D and i can say moiré is there. So is aliasing... You can shoot even in HD, they probably still stand... Lines skipping side effect...
check my moire test:
http://youtu.be/TTljSZUru6g
its not pretty
Update: [113] Updates- Bracketing Prefix in Transition .zip
Card: sandisk extreme pro 32GB 95 MB/s
Recording: 4GB
Mode: Photo LV
1536x600, global draw off, fps override 24, 0 skipped frame !!!
1536x620, global draw off, fps override 24, 0 skipped frame !!!
1536x620, global draw ON, fps override 24, 0 skipped frame !!!
1536x640, global draw off, fps override 24, 3 skipped frame only !!! 1 skip on 2nd and 3rd try
1600x600, global draw ON, fps override 24, 0 skipped frame !!!
I don't know what you did, but it's the good path !
Displayed speeds: from 38 to 38.9MB/s
Yay, its getting faster.
For the USB thing... usb may not have ANY power there. Even a thumb drive needs something.
The moire hasn't been *that* bad in 1080P/480P... 720P is barely usable.
much faster yey..........
I saw 30Mb/s today even before commits
[113] Updates- Bracketing Prefix in Transition .zip
Significantly faster :)
6D, photo mode, global draw off
1600x680 265 frames vs 193 frames in earlier build
1536x640 over 1400 frames vs about 500 frames
average speed is over 38mb/s, I saw 41,5 for a second :)
Beep is working now :D
1600x680 becomes kind of usable
1536x620 no skipping Sandisk Extreme 128Gb
Amazing!! Good work 1%. I'll add an update on other thread if that's cool?
1600x600 => 0 skipped frames => upscaled 1.2X = 1920x720 24p...... waooo
93 frames at 1840x768.
Movie mode has the same frame amount IMO,
movie mode, global draw off
1600x680 265 frames
1536x640 1450 frames
Quote from: teo770 on May 22, 2013, 12:21:22 AM
1600x600 => 0 skipped frames => upscaled 1.2X = 1920x720 24p...... waooo
yeah but.... 2,66:1 is to wide for me.
BTW what is the widest aspect ratio in cinema ? I read somewhere that 2,39:1 in now cinema standard. 1840x768 is like that exactly :D
Quote from: teo770 on May 22, 2013, 12:21:22 AM
1600x600 => 0 skipped frames => upscaled 1.2X = 1920x720 24p...... waooo
Holy crap dude! :o
Weird: some lower res seems to have higher birates
Higher resolutions display lower rates MB/s but frame skips
The frames are all different sizes and the "double" buffer is calculated from them.. so yea, sometimes even a higher size will write better than a lower one and vice versa.
I tried shooting some RAW video and it keeps giving an error.
ASSERT: FALSE
at RscMgr.c:2920, task InnerDevelopMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013May18.6D113
Mercurial changeset : 25d36d43a82c (unified) tip
Built on 2013-05-18 12:57:24 by user@D610.
Free Memory : 445K + 2098K
Don't know what this means.
I guess bug from saturday? Old bin + new module or v/versa
Is it still necessary to have the "Lv_REC.MO" file in the Module directory or can I delete it?
Never mind ... I can see that it is necessary.
thanks
If you want to use LV_REC then keep the module. If you just want raw_rec then only that module.
When I record in 1504x639 all the images are stretched. Instead of having that 2.35:1 aspect ratio, I'm forced to stretch the image to 16:9. Does this stretching occur for everyone?
EDIT: I noticed that the footage on the 5D MK III isn't stretched. Am I doing something wrong on the camera?
Fixed the problem. When the camera was set to 1280x720 60fps, the images were pink and stretched.
impressed with newest update. now I can shot 1504x640 without single problem.. no skipped frame at all, and write speed about 38.9mb/s. dont know what you have done 1%, but this update is very good for me!!!
Default card format:
If formating card inside the 6D,
16/32/64GB will be formated FAT32
128 GB and more will be formated exFAT
.
want to try that new raw_rec.mo linkedrawc.o but im scared
1% your cam still alive?
Yea, it still works. Worst its linked wrong and does nothing.
Hello, i must make a short film this weekend for the end of my studies.
Can you tell me what are the best options of encoding?
Bit Rate:
InitQP:
Flush rate:
GOP size:
Autoload Conf:
Config Select:
Raw recording is better? Why i can't record 1504 x600 with Sandisk 35GB 95MB/s ?
Thanks a lot and sorry for my approximate english.
set autoload to on and pick rc.ini
gop of 24 for long gop or use defaults
change flush rate to be lower if you don't need sound.
make sure you have h264 configs in ML folder.
Raw is better but you'll only be able to record smaller sizes. Dunno how fast that card benches.. see what other people recorded and start there.
I've noticed my battery depleting rapidly lately, using your latest bins etc.
In LV? In photo mode its still the same I think. Turning on all the raw stuff probably uses more resources.
Yeah in LV. I am sitting at 60%/h battery. I don't really need to use the RAW feature.
Is there a way I can slim down ML? Or should I just remove the module folders and such?
Well I used LV all day today for testing HDMI and battery drained as expected. I never got good mileage out of the 6D compared to 600D with cheap grip batteries.. even now with the raw, 600D still seems to last forever.
What you could do is turn off:
* focus peaking, or only use blinking dots
* don't auto load modules
* Turn off raw histogram/zebras/spotmeter in LV
Really there should be a separate config for stills/video now. I want all the fancy stuff for the 2 seconds when I take a raw CR2 but then I want a lean LV to get fast raw writing.
Here is my test 1600x600 http://youtu.be/7HfXJ-20FrU
Aspect ratio....
Good idea but i think it's too early to limit resolution to "usual" aspect ratios.
For now, we rather need freedom to test every update in as many resolutions possible.
No ?
Quote from: teo770 on May 23, 2013, 06:04:43 PM
For now, we rather need freedom to test every update in as many resolutions possible.
Agree... so with the newest file i can do 1600x640 about 200-250 frame then skipped
It is a bit limiting ... and 2.35 is freezing @1320. I just pulled the latest and greatest to test it out. Only benefit is having a known aspect ratio when resizing.
Quote from: DTSET123 on May 23, 2013, 05:56:19 PM
Here is my test 1600x600 http://youtu.be/7HfXJ-20FrU
Really nice test man! Interesting to see how moire-less and aliasing-less your test was at that resolution!
Just so you know by the way - we have a new thread going over here for general 6D and raw shooting discussions etc so if you wouldn't mind sharing you sexy-ass tests over there then that would be cool (just keeps this thread cleaner for Dev discussions):
http://www.magiclantern.fm/forum/index.php?topic=5530.msg39370;topicseen#msg39370
Cheers man 8)
Quote from: DTSET123 on May 23, 2013, 05:56:19 PM
Here is my test 1600x600 http://youtu.be/7HfXJ-20FrU
Awesome ! Which lens did you use ?
Quote from: 1% on May 23, 2013, 06:18:12 PM
It is a bit limiting ... and 2.35 is freezing @1320. I just pulled the latest and greatest to test it out. Only benefit is having a known aspect ratio when resizing.
We knew it already when setting width and height before, it was live calculated in the footer...
I preefer the old way definatly. At list while ML is beta on 6D
Just try to convince this guy ;)
http://www.magiclantern.fm/forum/index.php?topic=5596.msg39381#msg39381
Why not both? Lock to aspect or not.
I for one quite like it! I see what you mean in terms of squeezing out optimal performance but damn it makes life easier!
Quote from: 1% on May 23, 2013, 06:40:10 PM
Why not both? Lock to aspect or not.
maybe you just need to add an option to lock or not in Menu..
Yep, and esp on other cameras that need smaller sizes.
Just a heads up that I'm seeing that (http://www.magiclantern.fm/forum/index.php?topic=5614.msg39149#msg39149) hot pixel problem as of latest build ([113] AspectR.zip).
hmm... I guess we'll have to see. Nothing changed except defect detection was enabled.. it was worse before.
Maybe it was the same before and I hadn't noticed. What does defect detection help with by the way?
Lines/hot pixels/dust.
I just saw that with its CF card slot the 5D3 with can manage RAW at 1920×1080 for a limited number of frames and at 1920×840 it can record until the 4GB file size is reached.
It's pretty cool! (For 5D3 owners...) I felling bad now because I chose the 6D over the 5D3!
Anyway, with all that new knowlegde that you've got developing RAW at different resolution, do you think it will be possible to have one day 60fps at 1920x1080 even with lower bitrate?
OK to have a lock and an unlock feature for resolutions.
You must think to people with slower cards too... perhaps a 1600x600 won't work for them but a 1600x580 or 540 would work so....
unlockable resolutions would be cool.
If you guys want to try 12-bit recording, here are my raw_rec.mo and 12bitraw2dng.exe (for win32)
https://docs.google.com/file/d/0Bw98R-sUdECPang2ZkVDUElfZU0/edit?usp=sharing
I only tried in 1840x1228, and it was worse than 14-bit for me (35 frames instead of 40 frames on a Sandisk Extreme Pro 95MBs).
Maybe it's better in lower res, and the raw14to12 routines should have their own task as 1% said.... But I need to take a break for now :P
Quote from: 1% on May 23, 2013, 07:23:25 PM
hmm... I guess we'll have to see. Nothing changed except defect detection was enabled.. it was worse before.
My bad. Looks like it exists in footage from previous versions too. Must just be something we live with I guess.
5D Mark III (think 6D too) is definatly kicking GH2's ass ...
http://www.youtube.com/watch?feature=player_embedded&v=SFBc7i1Q_0w
Hi people! can you please help me with a link to some tutorial on how to install this on my 6D?
I have had magic lantern on my 60D, and i hopelessly need RAW Video :( check out my rig:
but i cant figure out how to make magic lantern run/boot from my sd with this dev kit :S sorry plz help
Quote from: smoli4 on May 24, 2013, 12:14:16 AM
Hi people! can you please help me with a link to some tutorial on how to install this on my 6D?
Here (http://www.magiclantern.fm/forum/index.php?topic=5530.0) :)
Quote from: noisyboy on May 24, 2013, 01:21:58 AM
Here (http://www.magiclantern.fm/forum/index.php?topic=5530.0) :)
Thank you so much ;) :D
followed the steps and there ya go! much appreciated.
Quote from: smoli4 on May 24, 2013, 04:22:08 AM
Thank you so much ;) :D
followed the steps and there ya go! much appreciated.
That's good to hear but please keep to the other thread unless it's Dev related. Cheers.
Welcome to the party 8)
Hi, I asked about audio shortcuts fews weeks ago, but then today I just saw this video : http://www.magiclantern.fm/forum/index.php?topic=2571.0
is it harder to add this shortcut on the 6D ? because it's really helpful :)
Quote from: Malex on May 24, 2013, 09:35:01 AM
is it harder to add this shortcut on the 6D ? because it's really helpful :)
+1 , it will be very usefull when headset output will work on 6D !
Quote from: Mayo on May 23, 2013, 09:16:33 PM
If you guys want to try 12-bit recording, here are my raw_rec.mo and 12bitraw2dng.exe (for win32)
Lol - just realised nobody thanked you for this! Cheers man.
Leaving it to the Pro's for now until this beast is ready for the wild ;)
I have to add audio shortcuts, it is doable but have to make sure it works when canon messes with the sound.
Right now wokring on raw.
Anyone try that pre-built module? Does it stop or keep going on the 12 bit?
I think we've kicked GH2s ass back to the stone age at this point.
Quote from: 1% on May 24, 2013, 04:26:40 PM
I think we've kicked GH2s ass back to the stone age at this point.
Lol! I think I need to get plaque made with that on.
I compiled the last commits and try the 12 bit thing. It stops after a few seconds. Seems as the buffers where eated quickly... perhaps not cleared?
Also the raw saved as 14bits cannot be processed by current raw2dng.exe at windows. The program crashes. I don't try yet the compiled linux version.
So the 14 bit is failing? Lemme try.
Also thats why I didn't make a bin yet... still testing.
Yea, 14 is acting funny. I need to put a proper menu update function.
Should we dare to hope to record at higher resolution with 12 bits?
Yea... working on it.. this stuff is coming out and I have to find the address for 6d and 600D. only have 5d3 listed.
1%, when is all set and done, what do you think will be the recording time without interruptions for Raw? Like on a 32gb card? 15 minutes, 25 mins?
It already runs till your card fills on some resolutions.
PS. If you fill the card and your footer is missing, shoot a quick shot at the same settings and then copy pasta the footer from that file to the end of the huge file.
ASSERT: 0
at ./MovieRecorder/EncDrvWrapper.c:1926, task MovieRecorder
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May23.6D113
Mercurial changeset : bbe5462826b9+2c2ee3590af5+ (unified) tip
Built on 2013-05-23 14:59:33 by user@D610.
Free Memory : 445K + 2291K
Dunno what happened... Just crapped out.
Quote from: fauxtographer on May 25, 2013, 05:45:27 AM
ASSERT: 0
at ./MovieRecorder/EncDrvWrapper.c:1926, task MovieRecorder
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May23.6D113
Mercurial changeset : bbe5462826b9+2c2ee3590af5+ (unified) tip
Built on 2013-05-23 14:59:33 by user@D610.
Free Memory : 445K + 2291K
Dunno what happened... Just crapped out.
What codec did you have used? All-I or IPB?
Quote from: 1% on May 23, 2013, 05:32:55 AM
Really there should be a separate config for stills/video now. I want all the fancy stuff for the 2 seconds when I take a raw CR2 but then I want a lean LV to get fast raw writing.
I agree. I am mainly shooting stills and then switching to video. It doesnt seem too problematic to have 2 modes, so long as it's clear which mode your are in.
For me, the photo/video switch would be the most intuitive.
1%, I've a modified version of last commited raw_rec.c, with some (very tiny) contributions:
* added aspect ratio 2.66
* added horizontal resolutions 1680 and 1720
* added recording start delay menu option to have time to activate stabilization on photo mode
* correct aspect ratio on photo mode if video mode is 720p (the video in photo mode is not squeezed, don't need 9/16 factor)
https://dl.dropboxusercontent.com/u/76801199/raw_rec.c
could you send the audio info over the wifi connection while using the SD card for the video?
Quote from: dlang on May 25, 2013, 01:41:16 PM
could you send the audio info over the wifi connection while using the SD card for the video?
impossible, i think? wifi is use more memory than others action.
Wifi performance from the one guy who tried is really bad. Also wifi eats like half the memory.
Quote from: 1% on May 25, 2013, 04:36:58 PM
Wifi performance from the one guy who tried is really bad. Also wifi eats like half the memory.
And kills your battery time 2 or 3x faster....
Yep... although for raw or anything long I think its best to be plugged in.
Quote from: 1% on May 25, 2013, 05:27:59 PM
Yep... although for raw or anything long I think its best to be plugged in.
Made me wonder something. Would the wifi in Canon6D have a "power saving" mode...
Acting at different speeds/power... like on notebooks if powered or batt. or plugged in....
Will try this afternoon. More power.... more speed... perhaps.
The memory hit is too big. We don't have enough as-is.
I have a question, and I dont know if here is the right place to ask or if you can point me to the right place to find out. I am unsure what is happening when we record c-raw as regards to cropping, pixel binning etc.
What is happening when i set the camera to record 720x 1280 c raw? Is it a 1:1 crop of the sensor, or resized via pixel binning? And why is the top resolution selectable in c raw mode much smaller than the width and height of a full resolution cr file, yet it fills the liveview frame?
Thanks, and appologies if this is posted in the wrong thread
Its a rectangle crop of whatever mode you're in.
So could be a 720P crop of 1080P or 2k (zoom mode) or real 720P (which is doing binning, etc)
Quote from: 1% on May 25, 2013, 11:06:39 PM2k (zoom mode)
zoom mode - magic zoom or something else?
I was hoping to shoot 720p but with the camera orientated in portrait mode, as that is how i am shooting stills currently. It is a few pixels short, will this ever be possible?
I dont think the histogram shows what is only in the raw box, I think it shows what is in all the liveview, regardless of the raw file resolution being regarded. Can this be modified?
Is it possible to have an option with magic zoom to zoom the box to fill the screen with the largest side? so the bounding box becomes smaller
If it is recording what is in the liveview, why doesnt it zoom in when recording with full screen magic zoom enabled. Turn that 100mm lens into a 400mm =D
Magic zoom is an overlay... this isn't YUV. Real 5x/10x zoom is a 1:1 crop.
Every mode has its own raw image that is generated (canon path... we can't change it yet)... take a silent pic to see the whole size. It isn't live view... it is the precursor to liveview. Hacked mode kills both LVs.
If you want to turn it sideways you can just pick a mode that is close to 1280 tall.
Histogram is for the whole image, I dunno if you can take it out of the crop, I don't think it would change. Zoom 5x will already turn that 100mm into 400mm+...
I shot from a sky scraper and could zoom really really far even with 135mm. It gets really bouncy.
Thanks, 1%. it is much clearer to me now
Height seems to need more MB than width so I wonder about this sideways idea.
I have been consistently shooting 1536 x 640 till I fill the card. Amazing stuff.
Using an SanDisk Extreme 45MB/s card. Not even the Pro card.
Quote from: 1% on May 25, 2013, 11:33:24 PM
Height seems to need more MB than width so I wonder about this sideways idea.
I ve been testing it, it seems ok on first glance
I added 9:16.. there should be some flip x/y option so we don't have all of these dupe ratios. Didn't seem smaller according to the MB calculator. Wonder what happens to the moire...
New build - 113 Deleteting - I love the new features, new res presets can be useful, 1720x720 gives me 147 frames., 1680x702 187 frames
Start delay - I wanted this from the beginning :D Great with glidecam, jib crane etc
found that hacked mode doesn't give more frames anymore 147 hack on vs 147 hack off (tested with 1720x720), 187 vs 187 (1680x702)
Quote from: 1% on May 26, 2013, 12:10:48 AM
I added 9:16.. there should be some flip x/y option so we don't have all of these dupe ratios. Didn't seem smaller according to the MB calculator. Wonder what happens to the moire...
thanks for the ratio add- this is what i have been testing, moire. I will let you know more tomorrow
I still get slightly higher write with hack on. Doesn't really help for something the camera can't keep up with. .5MB gain won't help when requirement is 5-10MB over.
Guys
is it normal?
113 deleting
Everytime (raw module OFF, autoload on startup OFF, no modules loaded) I set anything different than standard h.264 in encoder settings and trying to shoot camera crashes (err70)
Here is log:
ASSERT: 0
at ./Fcreate/FcsMaker.c:2314, task MovieRecorder
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May25.6D113
Mercurial changeset : 6e49faa5b226+ (unified) tip
Built on 2013-05-25 19:10:51 by user@D610.
Free Memory : 450K + 2371K
canon 1920x1080p 24fps IPB encoder flush auto, gop24, autoload on, rate control. Crashes every time after stopping recording, got the same crash log.
Quote from: kgv5 on May 26, 2013, 07:53:33 AM
Guys
is it normal?
113 deleting
Everytime (raw module OFF, autoload on startup OFF, no modules loaded) I set anything different than standard h.264 in encoder settings and trying to shoot camera crashes (err70)
Here is log:
ASSERT: 0
at ./Fcreate/FcsMaker.c:2314, task MovieRecorder
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013May25.6D113
Mercurial changeset : 6e49faa5b226+ (unified) tip
Built on 2013-05-25 19:10:51 by user@D610.
Free Memory : 450K + 2371K
canon 1920x1080p 24fps IPB encoder flush auto, gop24, autoload on, rate control. Crashes every time after stopping recording, got the same crash log.
Just try all-i 24p. I have same crash with this setting...
Yeah, but I thought of shooting best possible h.264 quality when not shooting raw and the best settings are probably with ipb and gop24. If its because some memory allocation things or so connected with raw its ok, but maybe is just some bug.
I'm going to literally go insane with this memory write speed limitation. If someone would post a guide on how to replace the bottle necking hardware (108mhz bus or whatever to a 208mhz) I would try and test. I want 1880x760 so bad.
Its getting too late here 1AM, I'm gonna lose my mind. Good night folks.
1%, is there a way to activate continuous lens stabilisation in Photo mode too ?
When u are in video mode, lens stab is running all the time.
Perhaps there's a Canon command for that ?
Heh, it is crashing, have to check.
* found it... I got rid of config_113.. just have to change it to config_6D
Quote from: 1% on May 26, 2013, 03:31:51 PM
Heh, it is crashing, have to check.
* found it... I got rid of config_113.. just have to change it to config_6D
so what should i choose at Encoder Menu to have a best result with bitrate ~ 100mbps? :)
100MB/s you can do with fixed QP of like 10 or 15. RC will give you 60-100 depending on the scene. Try some stuff and see what you get.
Quote from: pio_hyun on May 26, 2013, 04:05:57 PM
so what should i choose at Encoder Menu to have a best result with bitrate ~ 100mbps? :)
We've discussed this previously, good settings would be probably IPB, flush auto (to have sound), gop24, rate control, autoload on. I get about 60-80 mbps with these settings but for IPB it should give better quality than the same bitrate with All-I
thank you for fast reply :D Just do it and result is good
@1%: By the way, love the new function that you added in newest file. But problem when i shot in 1504x640, i cant playback when resolution is set in another number (like 1440x612 etc)
Yea I know. You have to rmember what it was. Its listed under the bugs for the 5DII module I got this from. At least you're good when shooting the same res and can delete.
Funny, ML discovered a RAW video function 2 months ago... develop,develop, develop.....
We know have a damned good RAW video function.... even RAW file management (ended in 2 weeks) !
Meanwhile, after monthes of developpement with $$$$ ingeneers, Canon releases 2 firmware updates for 5D Mark III and 6D....
To allow "clean" HDMI.... and correct a date issue.....
Wao.... Canon !
Are u somewhat paying too much your 200 engineers
or
just using the same very powerfull sensor/processors and market segmenting that much !!!
So.... ML team has genious geeks or Canon has genious marketing teams....
BOTH !! no ?
Hi, it's necessary to check lv_dispsize in this line of raw_rec.c, to avoid 9/16 desqueeze on zoom modes:
static float get_squeeze_factor()
{
if (video_mode_resolution == 1 && is_movie_mode() && lv_dispsize <= 1) /* 720p and movie mode and not in zoom mode, the image squeezed */
{...
Hey 1%, so 10 and 12bit video is dead for now or is there hope?
Quote from: 1% on May 24, 2013, 10:42:06 PM
It already runs till your card fills on some resolutions.
PS. If you fill the card and your footer is missing, shoot a quick shot at the same settings and then copy pasta the footer from that file to the end of the huge file.
Any hints on how to do this?
Thanks,
Shawn
The module isn't fast enough.. 10/12 bit will probably have to be done via registers.
Quote from: 1% on May 27, 2013, 02:34:01 AM
The module isn't fast enough.. 10/12 bit will probably have to be done via registers.
Registers? What are those?
Quote from: Shield on May 27, 2013, 02:18:56 AM
Any hints on how to do this?
Thanks,
Shawn
Well, I've pulled down a free hex editor (HxD) and replaced what I believed to be the footer from footage recorded just after the "big" one. Only problem is I can only extract the same number of dng files that I can with the "new" raw file - meaning the new raw file was very short just to grab the footer.
Short of recording a really long video and grabbing it's footer, what else can I do?
I did a replace insert beginning with the line that looked like this (and everything after it):
@bYÈ($b†È:$L,,(LÂ
Any other programme is able to make raw to dng?
When i open the raw2dng.exe (win), it popped a second and closed. What is the reason of it? :'(
Quote from: RYAN2310 on May 27, 2013, 03:05:41 AM
Any other programme is able to make raw to dng?
When i open the raw2dng.exe (win), it popped a second and closed. What is the reason of it? :'(
Drop your raw file directly on the raw2dng file; it'll create .dng files. You have some reading to do brother..:)
Quote from: RYAN2310 on May 27, 2013, 03:05:41 AM
Any other programme is able to make raw to dng?
When i open the raw2dng.exe (win), it popped a second and closed. What is the reason of it? :'(
Just move .raw file above raw2dng.exe.
Quote from: RYAN2310 on May 27, 2013, 03:05:41 AM
Any other programme is able to make raw to dng?
When i open the raw2dng.exe (win), it popped a second and closed. What is the reason of it? :'(
Does this happen with all files?
thank you. I have tried to move .raw file above raw2dng.exe but there was no created dng file in the folder. :'(
really frustrated...
I'll post a layman's "how to" to replace the footer information. This wasn't that tough.
Quote from: Shield on May 27, 2013, 03:46:18 AM
I'll post a layman's "how to" to replace the footer information. This wasn't that tough.
Cool - thanks man. Could you possibly post that in the post processing (http://www.magiclantern.fm/forum/index.php?topic=5404.0) thread and just link to it from here? It's just a bit off topic for here. I know 1% started the conversation but don't want traffic coming this way regarding it so we keep the forum cleaner.
Thanks Shield :)
Ps. Could really know about this myself right now too so nice work :P
Quote from: RYAN2310 on May 27, 2013, 03:21:51 AM
thank you. I have tried to move .raw file above raw2dng.exe but there was no created dng file in the folder. :'(
really frustrated...
Have a read in the post processing (http://www.magiclantern.fm/forum/index.php?topic=5404.0) thread dude and if you don't find your answer then ask in there. Cheers!
Quote from: RYAN2310 on May 27, 2013, 03:21:51 AM
thank you. I have tried to move .raw file above raw2dng.exe but there was no created dng file in the folder. :'(
really frustrated...
It happened to me once only with a full 4Gb file during tests. When I end the recording manually I never have this problem.
https://www.dropbox.com/s/eoakcgill3h0xou/RAw2dng%28Over4GB%29.exe
try this file, maybe better :-?
I have a few questions with the current releases
1. Is it possible to set a default resolution of 1504x630 so when I turn the camera on it's already set?
2. When I record I don't get a live view. I just get a still of from when I started taking the picture. Am I doing something wrong?
3. When I change to video it displays B:/ML/rc.ini ... should it do that or is the file not required?
4. I'm also guessing that the flicker every 5 seconds (if I'm not using the menu) is normal unless I don't have the setting correct.
thanks for the help and the great development work by all involved!!!
Quote from: rktaylor on May 27, 2013, 06:32:42 PM
I have a few questions with the current releases
1. Is it possible to set a default resolution of 1504x630 so when I turn the camera on it's already set?
2. When I record I don't get a live view. I just get a still of from when I started taking the picture. Am I doing something wrong?
3. When I change to video it displays B:/ML/rc.ini ... should it do that or is the file not required?
4. I'm also guessing that the flicker every 5 seconds (if I'm not using the menu) is normal unless I don't have the setting correct.
thanks for the help and the great development work by all involved!!!
1. I don't think this is possible
2. Turning off HaCKed mode will enable liveview again
3. I believe rc.ini is needed... rate control? or something like that.
4. Don't know what you mean?
rc.ini ,etc are for H264.. you can turn autoload off or leave it on, won't make a difference until you record H264
BTW how is the noise... any more like banding/etc... you should be random color pixel free tho.
Did a quick test with the latest bin
Photo Mode
HaCKed mode off
Global Draw on and Focus Peaking
1720 x 646 upscaled to 3072 x 1154 output with Maximum render quality to 1920 x 1080
Quote from: fauxtographer on May 27, 2013, 06:47:50 PM
1. I don't think this is possible
2. Turning off HaCKed mode will enable liveview again
3. I believe rc.ini is needed... rate control? or something like that.
4. Don't know what you mean?
Thanks ... in video mode if I don't use the ML menu it goes away after 5 to 6 seconds. It continues to display as long as I'm moving around in the menu. It does not do that when I'm using my camera for still ... only in the video mode.
I've just started playing with the RAW video side this weekend.
Quote from: 1% on May 27, 2013, 07:09:42 PM
rc.ini ,etc are for H264.. you can turn autoload off or leave it on, won't make a difference until you record H264
BTW how is the noise... any more like banding/etc... you should be random color pixel free tho.
Sweeeeet! Can't wait to try this :)
By the way... PRO TIP: Don't film a wedding with a version of raw_rec that is from the middle of May. It will ruin your day :P
Long file names work on 6D. This breaks deletion tho :(
Hey 1%, is there ever gonna be a 2x 3x 4x mode for liveview zoom?
I played around with the 5x zoom liveview recording and it is nearly 100% clean in regards to moire and shit.
Maybe.. no success with real crop mode just crashes.
There is no 10X zoom either, the raw is the same. So I guess its resize or 1:1 mode for now.
Gday.
Quick question.
is PicoC support avail on the ML for 6d for 1%'s builds?
Or will it simply be the TinyPy whenever it comes around to happening?
Thanks in advance.
could you add choosing raw file playback function in the new file. love this function in [113] H264CrashFix.zip ^^
Nevermind.
I just got my camera back from warranty and they put 1.1.3 on it, so i updated ML to that and I see it does scripts, the TinyCC ones. I'll give that a go later with the int main(){} wrapper from the PicoCC ones and use the hello world example for the PicoCC one.
I also note voice tags broke :(
When in just-took-a-pic-in-review mode with focus peaking enabled, pressing the set button causes more red dots to appear. Pressing it again causes even more red dots to appear. Instead of recording audio, or at least giving an indication that its recording. Version: [[113] NoDefc.zip]
Also, the "press LV to rate" while on review (play button) mode remains disfunctional by rotating the photo instead of rating it.
Quote from: 1% on May 28, 2013, 04:41:37 AM
Maybe.. no success with real crop mode just crashes.
There is no 10X zoom either, the raw is the same. So I guess its resize or 1:1 mode for now.
glad to see its not just me, I was wondering why x10 and x 5 gave the same results
LV to rate broke again? Ill look at voice tags.
Ok, voice tags are broken globally, 600D they don't work either. The shortuct isn't being used. LV rate in photo mode isn't detecting it needs to press twice for some reason.
Found it... there is another dialog handler when the q menu comes up in play mode.
I have made a small research and according to this video bitrate calculator:
http://web.forret.com/tools/video_fps.asp?width=1720&height=720&fps=24&space=raw&depth=14
when 12 and 10 bits became reality, theoretically speaking we could get:
(calculator bitrate estimation is different from ML, shows 2 to 3 MB/s more than ML)
Example calculations I made with VBC:
for 2,39:1
1600x670 14 bit - 45 MB/s; 12 - 38,5; 10 - 32
1680x702 14-49,5; 12-42,5; 10-35,5
1720x720 14-52; 12-44,5; 10-37
1816x760 14-58; 12-50; 10-41,5
for 16:9
max for 6D - 1816x1022 14-78, 12-67, 10-56.
This shows, that IN THEORY (and if somehow ML will be able to get SD card 50MB/s write speed) 6D would be able to shoot continously 1816x760 in 12 bits.
If we have still ~38-40 MB/s write speed than 1720x720 12bit should give very usable 350-400 frames.
with an exfat formatted sd card, i cant recorded files larger than 4gb. Is this correct, or do I need to do something after formatting it on windows
I've merged code with the main repo, let's try to wrap this up and be stable :)
Gday.
Using: [113] Fbrowser1.zip
* Voice tag after photo take (using set) still don't work. However, recording audio via audio menu and record audio, does work.
* LV rate is still broken. Still rotates the picture.
* When the camera is "sleeping". Pressing the Delete button doesn't wake it up. It just makes the little red light flash for a bit
I got a simple TinyCC script running that does printf's. But how do I do useful stuff? I couldn't find any doco nor API. I saw the PicoCC API forum page, but using those functions result in not finding the API function. I'm starting to think that TinyCC requires direct including and using the functions that ML uses internally rather than a new fake API, is this correct?
I grabbed the Hello.c example from the picoc examples. I removed the takepic and sleep calls, and left only the printfs. I wrapped it around an int main(int n) {} and kept the comments at the top. ML then reads the comments properly and prompts me for a 'number of shots to take'. But then this 'number of shots to take' isn't passed into my int n on the main function.
I also had some difficulty with Auto ETTR but it was because my 'exposure simulation' was turned off. D'oh! All good now. A very handy feature!
*shruggles
I confirm the format works :D and that the wifi remote shoot still works. Yay. Thanks
Quote* Voice tag after photo take (using set) still don't work.
I'm working on it. Something with set button handling while in QR mode.
QuoteLV rate is still broken. Still rotates the picture.
It worked and then it didnt... worked on movies (I guess useless)... fixed it today after I read it was a problem. The tweak task was updating too fast.
QuoteWhen the camera is "sleeping". Pressing the Delete button doesn't wake it up. It just makes the little red light flash for a bit
I think this is related to voice tags... same as set in QR mode.. flashes the light and does jack shit.
I have to add Tinypy to the next build for it to work I think. A1ex is working on moving the scripts over I think.
BTW, coutts got wakeup from set button.
Yay.
Thank you.
I'll update again in a few weeks and re-test.
I think I have it mostly fixed. have a weird issue with the set button, other than that should be done soon.
I don't know if I'm doing it wrong, but in movie mode, pressing the "focus points" button still wants you to choose focus points (but brings up the menu for iso/kelvin aswell). Is there a way to ignore the focus point box completely? It kind of works if you set focus to manual, but it stills bring up the focus point selections on the first press (and after hiding it with a second, you can change iso/kelvin).
Cheers.
You have to doubleclick (also enable in menu) while recording. Shouldn't bring up focus point selection except in photo mode.
So does this mean the first stable release, available from the homepage, will be released?
Maybe... its pretty much the same release with some stuff turned off (I think br and you get the un-updated help menu)... I'm not sprinkling instability dust on the builds.
QuoteI don't know if I'm doing it wrong, but in movie mode
Found your bug... don't use AF "quick" in live view. I'll have to disable shortcuts for af quick mode.
Sweet!
Thanks 1% .. voice tags work again.
Buut ....
"RAW Processing" through the canon menu dies with error 70.
Log/assert files at: https://www.dropbox.com/sh/syogzdreypjre2f/rbMS0D3eDQ
Also, it seemed that deleting a file in a directory (via the file browser) and the directory there ending up empty results in the directory being removed. I had a script in SCRIPTS and del'd it via the filebrowser. Next reboot and ML says script dir is missing.
Quote from: 1% on May 29, 2013, 03:27:33 AM
Found your bug... don't use AF "quick" in live view. I'll have to disable shortcuts for af quick mode.
Thanks man! It's only like this when
not recording in movie mode! But it's convinient to change the iso/kelvin with shortcuts before starting recording :)
I'll try changing to another focusing mode then. Although AF Quick is the one I prefer to use :/
Cheers.
Quote from: Veggietech on May 29, 2013, 10:40:40 AM
Thanks man! It's only like this when not recording in movie mode! But it's convinient to change the iso/kelvin with shortcuts before starting recording :)
I'll try changing to another focusing mode then. Although AF Quick is the one I prefer to use :/
Cheers.
I use af quick too, so I just change it to another focussing mode only to get white balance and then switch it back afterwards.
Another thingo, maybe not a bug:
When using the colour schemes, Ie "Dark Red", and a photo is taken, the quick review is toned as per the colour scheme.
But later, in the review screen, it is untoned.
It would be swell if it was untoned in quick review and image view.
Also ...
When going to ML menu, through "trashcan" and then pressing "menu" so as to invoke the colourfulsquares menu style I notice that the background of some of the squares are not filled-in with a solid colour. Instead, they're filled with the scene of the last taken photo. This does not occur when the colour scheme is Default. The colours that map to the last taken photo are the acqua-ish ones and dark green ones.
Also ...
It would be nice if one could view the focuspeak+histogram while on the image-review screen, rather than just LV and quick review.
Image review/play you press light and it should draw.
Looking into crashes, but have work today.
Raw processing works with magic:off. Guessing its a memory issue. Have to see if it worked previously.
Ah! The light button! Haha. I never knew you guys overloaded that button also.
I see it working with the light button! Thanks.
Have fun at work.
Was playing with making live view power off with the ML power-saving menu to see if making it turn off when recording raw would increase speeds when recording (as it improves quite a bit when bench-marking) and accidentally discovered that the liveview doesn't switch off when recording h.264 even if "recording" is selected in the sub menu. To be honest it doesn't affect anything I do but figured you'd want to know if you're pushing for a stable release. Didn't cause any problems - just didn't switch off. Maybe I'm using it wrong.
(running [113] Check4Regression.zip).
Cheers.
Ps. If anyone was wondering - making liveview switch off while recording raw had no impact on performance.
Also - getting err 70 crash when trying to use the in camera raw image processing from the Q menu when previewing images.
[113] Check4Regression
Crash logs: http://ge.tt/2E4rhxh/v/0?c
Thx :)
Edit: My bad - didn't see this:Quote from: oscaroo on May 29, 2013, 10:27:56 AM
Sweet!
Thanks 1% .. voice tags work again.
Buut ....
"RAW Processing" through the canon menu dies with error 70.
Log/assert files at: https://www.dropbox.com/sh/syogzdreypjre2f/rbMS0D3eDQ
Also, it seemed that deleting a file in a directory (via the file browser) and the directory there ending up empty results in the directory being removed. I had a script in SCRIPTS and del'd it via the filebrowser. Next reboot and ML says script dir is missing.
The raw processor might as well become a write-off... seems that memory it uses is used by ML.. it has been doing ERR70 for pretty far back. I tried patching the error it still dies.
Kind of a choice between raw processor all the time or raw video. Right now all you can do is boot magic off and do any raw processing thats needed there.
Also, I enabled tiny py but the modules is 180KB and also not enough memory to load it. I dunno how much of tinypy can run without the module.
Actually found a middle ground... you can have raw processor at the expense of dm log and tp log. Those will now have to be started in photo mode and may or may not have enough memory to do their thing.
<--- kind of an idiot, so forgive my stupid question but...
Do I simply replace the bin & the rec_mo on the SD card with the updated ones from 1%'s bucket? There's a lot of files on there and I don't want to eff it up on my end so that I can keep testing.
Replace modules in ML folder (don't forget magic.sym) and autoexec.bin.
I get an error when I change the RAW size in the Canon menu... is that supposed to happen?
Quote from: 1% on May 29, 2013, 08:29:10 PM
Kind of a choice between raw processor all the time or raw video. Right now all you can do is boot magic off and do any raw processing thats needed there.
Cool. Well my vote goes to keeping it this way then if it means I get more memory allocated for raw_rec. Booting the camera with the Set button depressed isn't exactly the end of the world and I only ever use it ever now and then if I get paranoid so I can see if the highlights pull back okay.
Regarding the sprinkles dude. Obviously with a1ex's pixel peeping test not being for 6D I haven't been able to run it but I have been goin' oldschool and testing by just shooting the shit out of things and I still haven't seen them come back since [113] Check4Regression.zip.
Tried to work out from the threads if it had been confirmed as being fixed or not (still seems up in the air) but just thought I'd let you know that it seems cool for me now and I even tried using the old module to shoot with the same setting to compare. The old has them - the new one doesn't.
As for banding though - I haven't noticed it myself but if you tell me what settings you have shot on when you see it and I'll do the same and see if I get it too. If I don't maybe I can send you my config or something and you can see if you can see why?
Quote from: fauxtographer on May 30, 2013, 01:54:12 AM
I get an error when I change the RAW size in the Canon menu... is that supposed to happen?
raw_rec doesn't shoot when using anything but the largest raw photo size dude. Wouldn't exactly say it's "supposed" to happen but I don't think it was a concern to fix it as the other sizes use too much memory. As far as I can remember at least. But then I do have the worlds worst memory :P
I got some shoot malloc back... I can fix or unfix the raw converter. prev build needs tiny py module (someone wanted tiny py).. I dunno hard to get that sucker into memory.
Now have 4x32.. dunno if card format still works. Does it?
Nice dude - squeezing quite a bit more out when shooting at 1536x642 (was getting around 1,200 frames before and now up to 1,508).
Format cleans all shots of card and keeps ML as expected although raw_rec still lists files to playback even tough it doesn't have anything there. I guess that this is something stored in the module and not that it's reading from the card?
1536x864 has gone from 108 frames to 127
Quote from: noisyboy on May 30, 2013, 05:15:56 AM
Nice dude - squeezing quite a bit more out when shooting at 1536x642 (was getting around 1,200 frames before and now up to 1,508).
Format cleans all shots of card and keeps ML as expected although raw_rec still lists files to playback even tough it doesn't have anything there. I guess that this is something stored in the module and not that it's reading from the card?
1536x864 has gone from 108 frames to 127
How did you manage to increase the frame counts? Nice job man, please keep an eye out for more.
Holy crap! In fact - card write speed when shooting 1536x642 has gone from 38.0/38.2 to 38.7/38.8 and now allows me to shoot 2,546 frames as opposed to 1,332
The figure I put in my last post was wrong! Yes it was 1,508 frames but that was actually compared to 779 frames when shooting 1536x654! Not 1536x642. This must have been some kind of fluke though as it's averaging about 1330 frames now. This is still nearly double though at this res :)
Quote from: xNiNELiVES on May 30, 2013, 05:34:28 AM
How did you manage to increase the frame counts? Nice job man, please keep an eye out for more.
Just testing the latest module https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
Also - I know we have discussed this a lot but choosing S1 jpeg def increases writes speed. EVERY time I choose it the speed jumps straight to 39+ then levels out at about 38.9-39.1 (never had these speeds before).
When I choose S3 for example - levels at about 38-39 but takes a while to get there. dunno if it's simply switching between the modes or the modes themselves but there's a noticeable difference and a solid pattern to prove that s1 wins.
Can other people try this so we can see if there is a difference? Which is better for you? S1 or S3? (S1 Higher quality by the way).
In fact if I keep on recording with it - it does eventually fluctuate. I know this seems a bit far fetched but the way I seem to get the higher speed seems to be when I shoot with S3 first and then switch to S1. Then it pretty much always gives me 39MB/s
Weird huh?
Maybe I'm just getting lucky which is probably the case. Still interested to see other peoples results though - if anything just to see if there is simply a difference between cameras.
Anyway - wicked work 1%
This is pretty much good enough for me to risk using it properly now :)
One last thing - am I right in thinking that previously you could select different raw files to preview or delete? Am I being thick or is it no longer an option?
Quote from: noisyboy on May 30, 2013, 05:49:32 AM
Also - I know we have discussed this a lot but choosing S1 jpeg def increases writes speed. EVERY time I choose it the speed jumps straight to 39+ then levels out at about 38.9-39.1 (never had these speeds before).
When I choose S3 for example - levels at about 38-39 but takes a while to get there. dunno if it's simply switching between the modes or the modes themselves but there's a noticeable difference and a solid pattern to prove that s1 wins.
Can other people try this so we can see if there is a difference? Which is better for you? S1 or S3? (S1 Higher quality by the way).
Wait. So you're saying that if you change the picture size; which, to my knowledge is irrelevant; allows the camera to write faster during raw video recording?
I'm not scientifically saying that this works (really must stop using words like "definitely and proof" lol) but in my repeated testing this seems to work out better for me. No idea why but when I switch from s3 to s1 it works better. Best thing you can do is try dude. If it doesn't affect it then I'm just getting lucky.
Quote from: noisyboy on May 30, 2013, 06:40:35 AM
I'm not scientifically saying that this works (really must stop using words like "definitely and proof" lol) but in my repeated testing this seems to work out better for me. No idea why but when I switch from s3 to s1 it works better. Best thing you can do is try dude. If it doesn't affect it then I'm just getting lucky.
I haven't installed ML yet. I waiting for advancements in Raw video. Or until the stable official release of ML comes out for the 6D.
It's pretty damn stable dude. Wont be long for stable release though.
Checked [113] mememe [no raw con], I see now 4 buffers 32MB :)
1600x670 - before 348 frames, now 374 :)
Checked also the thing with S1 and S3 which noisyboy was talking about:
S3 [113] Sacrifice Debug build --------------- 348, 348, 348
S3 [113] mememe [no raw con]-------------- 374, 374, 374
S1 lower Q [113] mememe [no raw con]-----357, 357, 374
S1 higher Q [113] mememe [no raw con]----374, 391 (!!!), 374.
It's hard to comfirm that S1 higher Q can give slightly better results. Only once for many tries get better frame number than S3.
Wow, what a difference like 3-4MB made.
S1 doesn't look to make any difference to the memory.. maybe it speeds up some internal processes? Placebo? Can't tell. At one point I strated killing the rest of the edmacs like face detection, etc.
The preview got broken by the name change so now it only lets you delete the last one (it can't find names anymore).
File manager you can delete whatever else. I could never preiview what I shot anyway as I didn't remember what size I shot.
Quote from: kgv5 on May 30, 2013, 08:32:24 AM
It's hard to comfirm that S1 higher Q can give slightly better results. Only once for many tries get better frame number than S3.
Thanks for checking dude!
Quote from: 1% on May 30, 2013, 01:45:16 PM
Wow, what a difference like 3-4MB made.
S1 doesn't look to make any difference to the memory.. maybe it speeds up some internal processes? Placebo? Can't tell.
I know man! Mad isn't it! I seriously believe that at this point it's a usable feature now. I'll share some of the shots in the general 6D thread that have been shot in a real world environment when I get a chance and I think people will see how usable this camera is with raw now. Yeah it's not 1080p but seriously - it's damn good man. Since raw was announced I never really bought into the hype. I saw the potential and was mega excited at the possibilities but also saw the limitations and didn't want to get too carried away until it developed more on our lovely 6D's but after throwing caution to the wind and using it on an actual shoot I can honestly say that this is amazing! I know the dust has started to settle a bit now but seriously man - you, a1ex, g3ggo, coutts and all the other Devs need to hold onto this achievement a little longer (I know that this is still early days but still...). It's a shame you aren't all based in the UK - I'd buy you all a pint :)
Oh and about the jpeg quality - okay, I'll let it go now and just enjoy it!
Quote from: noisyboy on May 30, 2013, 05:49:32 AM
Also - I know we have discussed this a lot but choosing S1 jpeg def increases writes speed. EVERY time I choose it the speed jumps straight to 39+ then levels out at about 38.9-39.1 (never had these speeds before).
When I choose S3 for example - levels at about 38-39 but takes a while to get there. dunno if it's simply switching between the modes or the modes themselves but there's a noticeable difference and a solid pattern to prove that s1 wins.
Can other people try this so we can see if there is a difference? Which is better for you? S1 or S3? (S1 Higher quality by the way).
I see no difference between any of the S's. about 33.1 on a card rated for 35 right off the bat for everything. I finally found a card that has a claimed write speed of exactly 50MB/s, comes in tomorrow, hopefully it works. I wonder if there is a way to hack the camera to not record images at all?
The moire thing is pretty much clean actually with ACR anti moire brush and it upscales really nicely, but now the biggest thing I'm noticing is aliasing. Where are we posting workflow? I think I have a pretty good setup, can't wait to finish editing. When we can get sustained burst of 1720x720 that's when this will become a boss feature.
Ooo one more thing, any chance on a config file for raw settings? I'd really like it if it would pop up everytime with my settings.
Thanks Devs! Great job on this. Never thought raw would be more reliable than h.264. My camera has not crashed, at all.
Cool man. If you are wanting to discuss specifically processing 6D footage and also want to discuss fighting the moire and aliasing issues then maybe a new thread in the Post-processing Workflow board and I can link to it from the 6D General Discussion.
Looking forward to it :)
Quote from: 1% on May 30, 2013, 01:45:16 PM
At one point I strated killing the rest of the edmacs like face detection, etc.
Are there any things left to kill? We can see now how every megabyte is important.
I found such thing concerning 6D's buffer size
http://www.dpreview.com/forums/post/51192126
I known that you certainly know that guys but that's interesting... During the test (raw stills) guy calculated write speed at about 38MB/s... Is buffer size really about 300MB? ???
Is it possible to allocate other system memory to the buffer memory, effectively increasing the time it takes for the buffer to fill?
1680x630 - little bit wide - 2,67:1 but now gives more than 400 frames (and hacked over 480). Just needs 114% of upscale.
1720x646 - 220 frames, 111,5% upscale
Sweet :D
Couple more MB and we are at home ;D
Quote from: xNiNELiVES on May 30, 2013, 07:20:05 PM
Is it possible to allocate other system memory to the buffer memory, effectively increasing the time it takes for the buffer to fill?
That's pretty much what is happening already dude :)
Quote from: noisyboy on May 30, 2013, 07:43:15 PM
That's pretty much what is happening already dude :)
What about advancements in actual write speed?
Well I have the sankdisk 95 card (can write up to 90 mpbs). I guess its useless with the 6D, right?
Quote from: fotojohni on May 30, 2013, 05:39:54 PM
When we can get sustained burst of 1720x720 that's when this will become a boss feature.
Now with 1720x720 I am getting 165. frames (hack on an off gives exactly the same).
Quote from: ManixLiquid on May 30, 2013, 07:58:11 PM
Well I have the sankdisk 95 card (can write up to 90 mpbs). I guess its useless with the 6D, right?
It would give you about 40MB/s write speed. Somebody mentioned before that it could give 1-2 MB/s more than sandisk extreme 45.
Tried multiple resolution with sandisk extreme pro card.... very hard to record sound on a separated wav file....
Would lead to extreme low resolution.
Would it be possible to use x264 to compress sound (only sound) so it will use less space / less needed write speed.
Quote from: fotojohni on May 30, 2013, 05:39:54 PM
I finally found a card that has a claimed write speed of exactly 50MB/s, comes in tomorrow, hopefully it works.
Could you reveal the secret and tell us what card it is? I will keep my fingers crossed again for this 50...
Quote from: kgv5 on May 30, 2013, 09:01:27 PM
Could you reveal the secret and tell us what card it is? I will keep my fingers crossed again for this 50...
I don't want anyone to go out and buy it then find out it sucks. It's a patriot card. http://www.patriotmemory.com/product/detail.jsp?prodline=4&catid=88&prodgroupid=238&id=1275
As I understand it, they all read at 90MB/s but only the 32 writes at 50, the rest are 35. Makes my mouth water when they talk about recording 4K HD video.
Wow, I print photos for a lot of people as a hobby, 19x11's, I had access to the print lab at my university and I took full advantage :} People go bananas but I get my results only using ACR. Now that I can use ACR for video, it's making me a little crazy.
Don't want to bother but i own 2 sandisk extreme pro 32 GB (95MB/s)....
On a USB3 reader, it reads at 93MB/s and write at 81MB/s
On the 6D.... writes max @ 38.7MB/s so limitation seems to be in the camera... whatever card you use...
I noticed that sometimes write speed are little bit higher than that. Depends on resolution (size of the frames). Sometimes I get even 40-41 for a second or so with sandisk 45 64GB so it's hard to say what is the exact real limit. So fotojohni I really hope the patriot will be better than sandisk and there is only one way to find out.
Waiting for a benchmark then, fingers crossed.
Anyone having this problem with frame inversion? It looks like it drops a frame temporarily then writes it one frame late. It doesn't ruin footage, but it's an issue. Might just be an earlier version though. I'm going through the 200GB I shot earlier this week.
I too have the Sandisk pro 95Mb, it writes perfectly until the card is full up to 39MB and at 40Mb it fails after a certain amount of frames - depending on frame size.
Would it be possible to set the default to 720*1280 16:9, as this is acheivable every time recording until the card is full, and seems to be the highest useable frame size in a broadcast standard. The perfect scenario would be if the could be a log file that could remember the previous setting before power down and keep it at that setting.
Is the moire brush on the new version of acr? I cant seem to find it
I can set 1 default... the modules don't read from a config... it can be that I guess. Right now it defaults to 1216x704 for me. Also have to get rid of the hard coded stop beeps.
Quote from: 1% on May 30, 2013, 01:45:16 PM
I could never preiview what I shot anyway as I didn't remember what size I shot.
Me too, it needed an on screen reminder or something
Quote from: 1% on May 31, 2013, 01:17:35 AM
I can set 1 default... the modules don't read from a config... it can be that I guess. Right now it defaults to 1216x704 for me. Also have to get rid of the hard coded stop beeps.
Yes, 720 would be better for me, as that is achievable and a broadcast standard
Hopefully file manager can eventually read footer and invoke playback.
[113] NewRes [no raw con] 24fps
This is so great!
1792x672 180, 180, 180 frames (hack on 180, 195, 195) upscale 107% 107% man!!!, it's AMAZING and almost 200 frames!!!
1728x672 225, 225, 225 (hack on 240, 240, 240) upscale ~111%
1664x624 612, 648, 630 (with hack on - 730, 738, 756) upscale 115,5%
1664x704 225, 224, 224.
I am going to sleep but this is awesome! Seems new default resolution for me would be now 1664x624 :D
And can now shoot ~8 sec with resolution with upscale factor 107% :D
Quote from: kgv5 on May 31, 2013, 02:00:02 AM
[113] NewRes [no raw con] 24fps
This is so great!
1792x672 180, 180, 180 frames (hack on 180, 195, 195) upscale 107% 107% man!!!, it's AMAZING and almost 200 frames!!!
1728x672 225, 225, 225 (hack on 240, 240, 240) upscale ~111%
1664x624 612, 648, 630 (with hack on - 730, 738, 756) upscale 115,5%
1664x704 225, 224, 224.
I am going to sleep but this is awesome! Seems new default resolution for me would be now 1664x624 :D
And can now shoot ~8 sec with resolution with upscale factor 107% :D
Once 12 and 10 bit raw comes out I believe that you will be able to shoot full 1080p with the same amount of frames. 12 bit vs 14 bit is negligibly different.
Damn dude! You done it again? 1% smashin' them out the park right about now 8)
What did you switch off this time lol ;)
Just a thought on this issue with the module not reading a config to set the default res/settings etc. Is it possible to have a menu feature that you can enter what you want the default to be and it'll write it in to the module (as in it edits the module itself)? Or is that just a recipe for disaster?
Quote from: fotojohni on May 31, 2013, 01:12:49 AM
Anyone having this problem with frame inversion? It looks like it drops a frame temporarily then writes it one frame late. It doesn't ruin footage, but it's an issue. Might just be an earlier version though. I'm going through the 200GB I shot earlier this week.
This frame skipping/doubling used to happen with older versions of the module. Have a tone of stuff I have to fix myself coz I foolishly used an older raw_rec for a shoot but I think it's fixed now (maybe 1% can confirm?). How long ago did you update the module or are you using the one from the zip file I shared (that one will definitely give you this issue as that's the one that fucked up all of my footage).
Quote from: sparedog on May 31, 2013, 01:15:40 AM
Is the moire brush on the new version of acr? I cant seem to find it
The brush you want is the Adjustment Brush along the top bar of ACR. from there you can perform all kinds of adjustments by moving the sliders on the right (moire filter being one of them) and you simply use the brush to paint the mask on (so basically just fill in the whole frame unless you have a locked of shot) and then play with the slider but don't go too far or it will blur the colour too much and desaturate the image (I always add a touch of saturation back after using this brush).
not sure if anyone has reported;
mememe - when using the focus ring on a lens that reports to the camera - 24-105 IS L series II - the focus assist pops up automatically, at 5% is corrupt image, functions fine at 10%, but any time the focus ring is touched this happens.
also the ML settings screen vanishes by itself on occasion.
side question - what frame size/aspect has given us the longest record time / greatest amount of frames?
Quote from: electrichobo on May 31, 2013, 06:24:00 AM
not sure if anyone has reported;
mememe - when using the focus ring on a lens that reports to the camera - 24-105 IS L series II - the focus assist pops up automatically, at 5% is corrupt image, functions fine at 10%, but any time the focus ring is touched this happens.
also the ML settings screen vanishes by itself on occasion.
side question - what frame size/aspect has given us the longest record time / greatest amount of frames?
Well there isn't one exact frame, its just a resolution at which point the card can write the same speed of the file size of the video. We calculate this by MB/s. The maximum length of video is when the file hits its 4GB cap. There are settings which can restart the video when this point occurs. The maximum resolution keeps increasing, I don't know the current highest. Wait for other members to respond with this information.
I've never seen frame inversion so not sure.
Quotet 5% is corrupt image
You mean the raw preview where its B/W? You can turn off zoom with focus ring.
Hi 1%
I'm happy to live without raw processing.
I can always boot with Magic:off.
Thanks for letting me know why it was dying.
I have yet to update from "[113] Check4Regression.zip".
I'll do that next week after a few photoshoots I have this weekend.
Quote from: electrichobo on May 31, 2013, 06:24:00 AM
not sure if anyone has reported;
side question - what frame size/aspect has given us the longest record time / greatest amount of frames?
With a 16:9 aspect ratio, you can record 24 fps at 720x1280 continues without frame skipping. With exfat formatted SanDisk pro card, it keeps recording till I decide to stop
Others are trying other aspects. Basically at the bottom of the screen ML will tell you the bit rate needed. Any size resolution that keeps the bit rate under 40mb seems to record continuously on the pro card
Quote from: sparedog on May 31, 2013, 06:18:54 PM
With a 16:9 aspect ratio, you can record 24 fps at 720x1280 continues without frame skipping. With exfat formatted SanDisk pro card, it keeps recording till I decide to stop
Others are trying other aspects. Basically at the bottom of the screen ML will tell you the bit rate needed. Any size resolution that keeps the bit rate under 40mb seems to record continuously on the pro card
I just got that patriot 32GB, It's getting 39.5MB/s formatting is fat32, does exfat help? It really seems like 40 is the speed limit. Sandisk is still the best bet I think.
Damn :(
I just got that patriot 32GB
Pro or EP?
I'm getting my EP back maybe today... will try it in fat32 I guess.. only gave me 30 regular, probably have to cut 64GB card to 32. If the pro is only getting 39 then sandisk 45Mb/s is equal. maybe this is where SD tech on SDR/DDR50 is at.
Exfat/fat32 should be no difference in performance.. only the 4gb thing.
The pro definitely gives a better result than the extreme, by about 4mb second I seem to remember.
Ex fat only gives larger file sizes, I think, I don't see any real speed differences. But files sizes above 4gb are worth the reformat
I know I sound like a broken record but I bought the best sd card you can get for speed (Delkin 633x) when we first started this adventure and it performs no better than my Sandisk Extreme 45MB/s cards. Don't waste your money - trust me, the 45MB/s' are gonna work just as well under the limitations. At least unless some breakthrough makes thinks better for us. Once you realize that the highest res we can shoot continuous raw with is actually pretty damn tasty - it's quite liberating! Mostly because you can get a 64gb card for $65 (or 50 quid) which makes shooting raw very cheap for us :)
Time to go out and enjoy shooting raw 8)
Quote from: sparedog on May 31, 2013, 08:06:20 PM
The pro definitely gives a better result than the extreme, by about 4mb second I seem to remember.
Ex fat only gives larger file sizes, I think, I don't see any real speed differences. But files sizes above 4gb are worth the reformat
Do you have any benchmark for this?
With extreme 45 I am getting sometimes 41,5 (for about a half a second) and normally 38-39,5. Did you have 42-44 with pro? I don't think so, other users with pro have the same 38-40.
Quote from: kgv5 on May 31, 2013, 09:10:41 PM
Did you have 42-44 with pro?
If this is the case the leap with recording times would be
huge. I'd love to proven wrong (I would SERIOUSLY love to be) but I wouldn't hold out much hope.
Quote from: noisyboy on May 31, 2013, 09:09:53 PM
Once you realize that the highest res we can shoot continuous raw with is actually pretty damn tasty - it's quite liberating! Mostly because you can get a 64gb card for $65 (or 50 quid) which makes shooting raw very cheap for us :)
Yeah, well said. Even if I had 5D3 now I couldn't afford 1000x cards, 128GB costs as much as a nice lens :o
We need to make some good comparison video with the res we have now vs 1080p. (I think we could use LV_rec module to get couple of frames in real 1080p raw on 6D as a benchmark) There are plenty of comparisons videos but always ungraded, wrongly exposed h264 with no sharpness/cinestyle with no lut applied vs nice raw.
I think the resolution is fine. I upscale the images, then lightly sharpen. Then downscale in premiere, I have no complaints. I shot some stuff @ 12800 3 ev under exposed and it's pretty impressive, plus no banding!!
I honestly believe that for most shots, as long as it's raw and you upscale correctly, you could easily upscale to 3K and it would just look a teeny-tiny bit soft up close.
Only issue I have is that it's not full frame. How does the 720p 24fps override work?
Quote from: kgv5 on May 31, 2013, 09:34:46 PM
Yeah, well said. Even if I had 5D3 now I couldn't afford 1000x cards, 128GB costs as much as a nice lens :o
We need to make some good comparison video with the res we have now vs 1080p. (I think we could use LV_rec module to get couple of frames in real 1080p raw on 6D as a benchmark) There are plenty of comparisons videos but always ungraded, wrongly exposed h264 with no sharpness/cinestyle with no lut applied vs nice raw.
I have some examples I'm working on now. The difference in sharpness is stunning especially with good upscaling and sharpening. Night and day.
Quote from: fotojohni on May 31, 2013, 09:41:51 PM
I have some examples I'm working on now. The difference in sharpness is stunning especially with good upscaling and sharpening. Night and day.
Sure thing, I don't want to make an OT here, let's make a new thread something like "Shooting raw in lower resolution than fullHD and then processing them". I am curious how do you guys make proper upscaling for example.
Lol - like the thread title ;) Catchy!
Yeah - something I was gonna post in the 6D - Magic Lantern and raw Shooting General Discussion (http://www.magiclantern.fm/forum/index.php?topic=5530.msg43161#msg43161) about the lack of 6D raw videos. There are tonnes of vids showing off the other cameras but none of our beloved 6D's. I'd like to start a thread called "Raw Vids Shot on 6D" under Share Your Vids (http://www.magiclantern.fm/forum/index.php?board=19.0) but haven't got anything to post myself 'til probably tomorrow night so seems a bit silly :P In fact I'll start it and then link to it from here and the 6D general thread. 8)
Quote from: noisyboy on May 31, 2013, 10:47:06 PM
Lol - like the thread title ;) Catchy!
Yeah - something I was gonna post in the 6D - Magic Lantern and raw Shooting General Discussion (http://www.magiclantern.fm/forum/index.php?topic=5530.msg43161#msg43161) about the lack of 6D raw videos. There are tonnes of vids showing off the other cameras but none of our beloved 6D's. I'd like to start a thread called "Raw Vids Shot on 6D" under Share Your Vids (http://www.magiclantern.fm/forum/index.php?board=19.0) but haven't got anything to post myself 'til probably tomorrow night so seems a bit silly :P In fact I'll start it and then link to it from here and the 6D general thread. 8)
I'm too much of a perfectionist to post just any video. Hopefully all the work I've done will show how great the 6D is.
720P is OK.. just don't shoot anything that could possibly even think about giving you moire..
There are a couple of different cards:
Sandisk Extreme Pro
Patriot EP Pro
Patriot EP not pro
Both have pro and "similar" specs... IMO patriot EP not pro gave pretty good performance for the money... still didn't come in the mail today. I was getting 31/30MB on it before it broke. I would hope the pro gives as good or better results as sandisk pro or at least sandisk 45MB/s...
I am only showing 2 of the former 4 buffers now. What did I press?
Quote from: fauxtographer on June 01, 2013, 01:41:49 AM
I am only showing 2 of the former 4 buffers now. What did I press?
Hey man!
You probably have Raw photo selected in canon menu instead of just jpeg.
Just leave raw.
Wifi + (raw+jpeg) takes memory... raw/jpeg by itself doesn't make a memory diff.
Quote from: 1% on June 01, 2013, 07:42:27 PM
Just leave raw.
Wifi + (raw+jpeg) takes memory... raw/jpeg by itself doesn't make a memory diff.
Just to clarify you are saying that raw or jpeg on it's their own affects nothing but I'm right in thinking that raw PLUS jpeg when selected at the same time affects memory?
If I have this wrong then I'm very confused now :p
Cheers.
You got it... raw + jpeg uses twice the memory... Got the patriot card back. I'm getting 32.0MB now with LV hacked off (previewless mode is back in next release). So that means you guys will hopefully get 40/41/42/etc.
So do you mean this is ~2 MB/s faster than the fastest card tried before (and sandisk 45/95) ? Could you please check it with a 6D?
I only get 32MB ... I don't have the sandisk (supposed to be 38/39?)... but maybe your cards will go up a bit too (check)
Sorry, I don't understand... I thought this speed was not on 6D.
Quote from: 1% on June 01, 2013, 09:33:47 PM
So that means you guys will hopefully get 40/41/42/etc.
You mean on 6D with this particular card? Yes, now getting 38-39 so 41-42 would make a difference, It would be worth to buy such a card to check that 2 MB/s speed increase.
Hey guys.
I'm still on "[113] Check4Regression" version.
I was out using my camera a lot yesterday.
I had some issues which I can't repeat successfully.
- I got an error 65. I restarted, then it was ok. I'll upload log later.
- My camera kept beeping at me during a shoot. I dunno why it would just beep at random. But it would. Most of the time, with each photo taken, no beep would be there. Randomly, as I took a photo - beep. Maybe my forehead kept hitting some button? Dunno.
- Once, the top spinny thing control (The one that moves the A in AV or T in TV) stopped responding completely.
I tried to boot with Magic off, but it refused. Magic wouldn't go off!. Eventually, after a few reboots Magic was off, but the top spinny was still dead. Luckily, I had the battery grip and moving the battery grip spinny worked and then the top spinny came back to life also.
Weird!
I have some more photos to take today and some more next weekend.
I'll upgrade version and see what happens.
Voice tags? Auto ETTR? Those things beep.
QuoteYou mean on 6D with this particular card?
Yep, before it only got bursts of 29 or 30 at most... now doing much better (32.x). So align left + kill LV might give you better speeds from the other cards. From 35MB/s that is only 3MB missing vs like 4 or 5.
Quote from: 1% on June 02, 2013, 12:36:49 AM
So align left + kill LV might give you better speeds from the other cards. From 35MB/s that is only 3MB missing vs like 4 or 5.
I checked, forcing left and LV hack : for 1664x624 ------ 612 vs 756 frames
Write speed increased from 38,5-38,8 to 39.0-39,5. Increase by about 0,5-1MB/s gave almost 150 frames more so seeking proper card for 1-2 MB/s more makes sense.
Oh yeah!
i think it could have been my face pressing the 'set' button and thus causing voicetags to occur.
yepyepyep.
I should disable voicetags when I'm not planning on using them.
Thanks 1%
Quote from: oscaroo on June 02, 2013, 02:58:27 AM
i think it could have been my face pressing the 'set' button and thus causing voicetags to occur.
loooooooooool 8)
Daaaayyum!
Just tested [113]Previews with HaCKeD Live View and centered to the left and got 2128 frames at 1536x656 24fps as opposed to 1508 frames!!
Just a shame you must sacrifice Live View to achieve this. Still though - good to know there is a way to squeeze more out :)
By the way - I noticed that when choosing between 2.35:1 and 2.39.1 when you have 1536 width selected, the hight resolution stays the same (656). Is this me just being dumb at maths or is that incorrect?
Cheers!
Is there any way to save the settings of raw video? setting aspect ratio, resolution, hacked mode, delay, frame skip every time.. :/
Also it would be nice to have the arrow shortcuts available to adjust ISO WB in RAW.
Finally, still in RAW record, in zoom x5, the frame showing the area you are recording is wrong
Quote from: Virindi on June 02, 2013, 11:37:42 AM
Is there any way to save the settings of raw video? setting aspect ratio, resolution, hacked mode, delay, frame skip every time.. :/
Also it would be nice to have the arrow shortcuts available to adjust ISO WB in RAW.
Finally, still in RAW record, in zoom x5, the frame showing the area you are recording is wrong
There is but it has to be hard coded. I tried but I deleted my xcode to make room for raw footage so I couldn't open it LOL! What I could open was too difficult for a mortal to decipher.
Why would you need WB, this is raw? Also, there are. MAKE SURE YOU LOCK ISO, lol. It's way more obvious in RAW when it's changing.
Zoom feature works, it's doing a lot of really crazy processing. I only get a black and white image but it IS the correct recording area.
I wanted to make a suggestion. At 5x zoom level, we have the ability to shoot 2.6K. I'm wondering if some kind of rudementary pixel binning could be possible to get 1.3K. If that was possible it would solve the moire thing. And still give very nice footage. Crop would be M4/3.
Quote from: fotojohni on June 02, 2013, 03:12:54 PM
There is but it has to be hard coded. I tried but I deleted my xcode to make room for raw footage so I couldn't open it LOL! What I could open was too difficult for a mortal to decipher.
Why would you need WB, this is raw? Also, there are. MAKE SURE YOU LOCK ISO, lol. It's way more obvious in RAW when it's changing.
Zoom feature works, it's doing a lot of really crazy processing. I only get a black and white image but it IS the correct recording area.
Oh yeah of course WB is useless. But about changing ISO, to me it would be useful. I can use my 6D for some random crap handheld video, or just play with it.. but still want high quality crap lol so I would use RAW recording and it doesn't matter if I see ISO jump.
For me after I select my resolution and zoom x5 I see right the white rectangle for 2 seconds, then it becomes like 2 times smaller and what I record is not what is in this rectangle.
:( I remember not having this issue a few days ago.
Odd... zoom rectangle in 5x will be wrong without the preview no matter what... you can't see close to the whole frame.
No saveable settings yet, all hardcoded.
WB: I just use uniwb so there are no multipliers. ISO is a physical sensor parameter... Make sure expo changes aren't from ACR, try gradual expo see if it helps any. Not much can be done about real expo changes... they were always obvious.
Quote from: Virindi on June 02, 2013, 09:57:19 PM
But about changing ISO, to me it would be useful.
You want to buy variable ND filters for your lenses dude. They are real cheap off ebay. Like £10/£20. Don't do what a friend of mine did when I suggested variable ND's and go out and spend £200 on 3!!!!
with newest build I cant find 1504x640 in 2,35:1 aspect ratio.. is this some kind of mistake?
As far as I know some resolutions were changed a little bit in newest builds, with the new ones we can get a better performance.
Guys! Baller baller baller...
We can get 255MB shoot malloc in photo mode.
Quality -> jpeg... Multi shot noise reduction... just like EOS-M!
I patched the errors and its working! I have like 6 buffers! Now need to run this function in movie mode
Thanks 50D!
This is just unbelieveble ;D
But unfortunatelly something is wrong because on my 6D with [113] BigMemPhoto.zip it is still 151 MB (4 buffer stars) in photo and movie mode. Quality set to just JPG
Maybe I set something wrong...
on... 6D ? with [113] BigMemPhoto.zip ?
Photo mode LV. Q jpeg... high speed NR to multi shot.. wait for busy to clear. You need hacked mode to disable the aewb which now turns on, plus fps and expo override.
Hi.
I'm still on that old stable-ish version,
I get this assert. Should I be worried? I presume not.
ML ASSERT:
(int)state <= max_job_state
at ../../src/lens.c:1966 (_prop_handler_PROP_LAST_JOB_STATE), task PropMgr
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013May28.6D113
Mercurial changeset : 2be778c251b7 (unified) tip
Built on 2013-05-28 22:42:05 by user@D610.
Free Memory : 430K + 2231K
Thats a weird one and happens at random. I couldn't figure out why yet. I just end up with this assert on my card and think WTF and when did it happen.
Coolies 1%
There's also this crashlog
ASSERT: FALSE
at ./ASIF/ASIF.c:486, task ASIF
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013May28.6D113
Mercurial changeset : 2be778c251b7 (unified) tip
Built on 2013-05-28 22:42:05 by user@D610.
Free Memory : 445K + 2255K
and this one, which I think is the raw develop one I forgot to clear out of the memory card. Meh @ rawdevelop
ASSERT: FALSE
at RscMgr.c:2920, task InnerDevelopMgr
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013May28.6D113
Mercurial changeset : 2be778c251b7 (unified) tip
Built on 2013-05-28 22:42:05 by user@D610.
Free Memory : 445K + 2265K
Damned, never get 255M free mem, still 151M...
Quality JPEG
Exp override ON
FPS override 24
Global draw off
Preview hacked
Quote from: teo770 on June 03, 2013, 04:57:15 PM
Damned, never get 255M free mem, still 151M...
Photo mode LV
Quality JPEG
Exp override ON
FPS override 24
Global draw off
Preview hacked
High ISO speed NR to multi, If you have this option greyed out set Long Exp. Noise Red. to OFF in the first place.
255 MB - hell yeah - 1728x736 >>> 342 frames!!!! with hack OFF, hack ON - 357 frames :D
This is huge
6D max resolution (1792x752) in 2,39:1 aspect ratio: 280 frames hack ON, 280 hack OFF
1792x672 2,67:1 421 hack OFF
1664x704 2,39:1 528 frames hack OFF
1664x624 2,67:1 1548 frames hack OFF
Quote from: kgv5 on June 03, 2013, 05:04:58 PM
High ISO speed NR to multi, If you have this option greyed out set Long Exp. Noise Red. to OFF in the first place.
255 MB - hell yeah - 1728x736 >>> 342 frames!!!! with hack OFF, hack ON - 357 frames :D
Thanks, yes, got 255M now... 6 buffers... nice
Euh..... 7 buffers !
Recording @ 1600x640 => 1 skip frame only in 4GB recording (no hack)
Ya turn ya back for 5 minutes :o
Well done dude! Just made my day 8)
Setting up "My Menu Settings" Got three crash logs in one go.
ASSERT: FALSE
at RscMgr.c:2843, task GISMgr
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun03.6D113
Mercurial changeset : 6252dc26a42a+ (unified) tip
Built on 2013-06-03 13:36:27 by user@D610.
Free Memory : 444K + 2011K
ASSERT: FALSE
at RscMgr.c:2843, task GISMgr
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun03.6D113
Mercurial changeset : 6252dc26a42a+ (unified) tip
Built on 2013-06-03 13:36:27 by user@D610.
Free Memory : 445K + 2068K
ASSERT: FALSE
at ./ASIF/ASIF.c:486, task ASIF
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun03.6D113
Mercurial changeset : 6252dc26a42a+ (unified) tip
Built on 2013-06-03 13:36:27 by user@D610.
Free Memory : 445K + 2057K
Also managed to shoot 1792 x 1008 for 120 frames... Decided I might as well point it at a sharpness chart... Not too good.
I mean it is sharp... but WTF is in the middle??!
Full frame 1.8K @ 2.39 I'm getting 266 frames, (global draw on/off, magic zoom on/off, focus peak on/off, hacked on/off, zebras on/off).
Edit: hacked no preview give ~10% more frames, hacked shows no difference.
NICE!!!!!
Crop mode I get 137 frames @ 2K! moire free and it's definately big enough with my 17mm 8)
crash log:
ASSERT: FALSE
at RscMgr.c:2843, task GISMgr
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun03.6D113
Mercurial changeset : 6252dc26a42a+ (unified) tip
Built on 2013-06-03 13:36:27 by user@D610.
Free Memory : 444K + 2009K
This error is patched but I have to investigate it more.. sometimes it happens.
Need to find out how to free this memory in movie mode and what happens. Right now this is still alpha but as you see, potential is huge. Ie. 2k recording for short bursts, etc.
I'm also going to investigate these stupid color peaking things... I think no af_raw isn't working for us, neither is af_raw.
I wonder, how much memory does 6D really have...
The things you guys make are really huge.
Now we need to check every card available on the market, maybe we could find any with 2-3 MB/s more write speed. Maybe we should make a new thread where we could list every SD card people have tried with ML and speed they had.
512MB total. 600D/550D is 256 only. We're lucky to have the multi shot NR... otherwise it stops using the memory but doesn't free it.
Also works in older LV_rec. Now we can capture 120 frames of true 1920x800 :D
1920x1080 - 100 frames
Hi, i am new on this forum, but i am watching this post since few months...
Anyway... if now we could use this memory to save continuus video file (120 frames) at high resolution in RAW, maybe there will be a way to use it to save not all, but only 1/4 frames from video, while other 3/4 frames will be saved to the SD card. So it will be possible to save bigger resolution and 4 times longer video with this resolution and merge it after all? (480 frames)
Correct me if i am wrong :)
kgv5, what SD card are you using? SanDisk Extreme Pro 64 or 32? I´ve seen one is sdxc the other sdhc, does it make any difference?
Thanks.
This above was about the ancient LVrec module. From couple of weeks we have much more sofisticated RAWrec module which gives 6D and other cameras ability to shoot continous raw in some resolutions (for 6D about 1600x640 or so) but doesn't give 1920x1080. Today we get buffer size update from ~150 to 255 MB. Cameras with CF cards like 5d3, 5d2 or even 50D have better raw performance due to much faster writing speed than SD cards.
Quote from: Gobian on June 04, 2013, 12:07:18 AM
kgv5, what SD card are you using? SanDisk Extreme Pro 64 or 32? I´ve seen one is sdxc the other sdhc, does it make any difference?
Thanks.
Hi
I am using sandisk extreme UHS-I 45MB/s 64.GB and I can honestly recomend it.
today as an addition I ordered Patriot something something PRO 90/50 32GB but I don't expect much more of writing speed though (but please card, give me 3 MB more, we will see...)
So on the current version we cannot select 1920 as a horizontal resolution? On the older versions we can? Anyways the 120 frames you got actually will be a little less with people who have a faster memory card. That's about 6+ seconds. I say a good ending goal should be 30 seconds. This of course is with the thought that 12 bit raw will be implemented. That would be under 50mb/s. Hopefully around 45.
Quote from: shdster on June 04, 2013, 12:03:38 AM
So it will be possible to save bigger resolution and 4 times longer video with this resolution and merge it after all? (480 frames)
The buffer is like a bathtub. There is water being poured in and at the same time water being drained (into the card) The card is already draining the bathtub as fast as it can.
http://www.magiclantern.fm/forum/index.php?topic=5601.0 This is a better way. Wish I knew what was wrong :/
Old LV_REC just added up to 1920 the way it did the math.
I don't know how that works because in non zoom its smaller than that (1792)
Quote from: 1% on June 04, 2013, 01:36:44 AM
Old LV_REC just added up to 1920 the way it did the math.
I don't know how that works because in non zoom its smaller than that (1792)
I have no idea what this crop mode is. I know what live view zoom is, but I have no idea what it has to do with recording...
Old lv_rec had 1 fixed size, it happened to calculate to 1920xwhatever
Raw rec seems to guess actual size.
Not working in movie mode yet:
Movie:
http://pastebin.com/ZEXmY4j3
Photo Mode... I just hit don't click me and 255Mb happens
http://pastebin.com/JzSZHqk4
Is this to be expected in the current builds ...
With the ML menu on in LiveView it kicks me out of the ML menu after about five to seven seconds. If I keep turning the wheel or moving the cursor the menu stays up until I stop and then after five to seven seconds the ML menu shuts down.
Is this normal?
Thanks
Yea, I think thats the new menu. Before it would flash.
Its annoying with the file browser, yet helpful for EOSM when it chokes on file seeking.
So for those "peaking" lines on the chart does AF off help? I tried lv_md_visible to 0 and it didn't help for af_raw. I just hope the default raw type doesn't have it.
This new/current RAW module is very polished right now and easy to use, old module because of it's limits is almost unusable in most situations and the current ones performance makes its good even for every day shooting (if you like post production process a lot ;) ). Especially now when we can really use say 1664x704 (over 1500 frames), 1792x672 (over 400 frames) or even 1792x752 (280 frames) with slight amount (~115% with 1664 or 107% with 1792) of upscale. With such a small upscaling you really cannot easly see the difference in comparison with 1920x720 or 800, maybe when you put it side to side with 200/400 magnification.
It's obvious that the more you have, the more you want but remember, that on 6D you can have such a quality really cheap (when compared with 5D3 and CF cards) so we shouldn't grumble especially that lowering 14bits to 12 and 10bits which will extend recording times again. So be patient.
1% and the rest of the devs - you are doing great work.
Quote from: kgv5 on June 03, 2013, 05:04:58 PM
High ISO speed NR to multi, If you have this option greyed out set Long Exp. Noise Red. to OFF in the first place.
255 MB - hell yeah - 1728x736 >>> 342 frames!!!! with hack OFF, hack ON - 357 frames :D
This is huge
6D max resolution (1792x752) in 2,39:1 aspect ratio: 280 frames hack ON, 280 hack OFF
1792x672 2,67:1 421 hack OFF
1664x704 2,39:1 528 frames hack OFF
1664x624 2,67:1 1548 frames hack OFF
What settings did you use to obtain 255mb buffer size.
Edit:
Well sometimes it works, sometimes it doesn't odd...
I only got 180 frames with 1792x672 (or something close to these numbers. I forgot the exact amount), with apparently 255mb buffer size but then I checked again after I took the video and it went back to 151mbs. Kgv5 how did you get 380 frames!? I never saw any Hacked mode. What other settings are you using.
So I can get a 255mb buffer size but not in live view. In live view it goes down to 151mb. Raw video is supposed to work on the video live view right? Not the photo live view?
Edit:
Ok I've repeatedly gotten 255mb buffer size in non live view. As soon as I go to live view the buffer size reduces...
Also I'm experiencing a decent bit of crashing every so often from switching to video live view from still live view...
EDIT:
Oh my god, I just read back to finally put the nail in the coffin in my suspicion that it only works in photo mode, hence the release name...
1% seems to have released something new regarding the buffer memory: [113] ETTR-MemDontclick.zip
Care to explain this 1%.
Thanks
Yea, make sure you open LV first otherwise you'll never open it.
Its not bulletproof but I got 700 frames of 720P with the 32MB/s card, sometimes more... global draw also has more of an effect in photo mode and you have to override everything (I guess camera goes into dummy mode). Doesn't work in movie mode yet, when I used it there it just added high ISO NR menu to movie mode... but no mode 4 there.
Quote from: kgv5 on June 03, 2013, 05:04:58 PM
High ISO speed NR to multi, If you have this option greyed out set Long Exp. Noise Red. to OFF in the first place.
255 MB - hell yeah - 1728x736 >>> 342 frames!!!! with hack OFF, hack ON - 357 frames :D
This is huge
6D max resolution (1792x752) in 2,39:1 aspect ratio: 280 frames hack ON, 280 hack OFF
1792x672 2,67:1 421 hack OFF
1664x704 2,39:1 528 frames hack OFF
1664x624 2,67:1 1548 frames hack OFF
I just got 241 frames at 1664x624. This is with force left, global draw off, at 24p with a sandisk extreme pro 32gb. WTF!
EDIT:
Well I actually compared my results to an older test he did and got 100 frames more. I guess Kgv5 you're doing this theoretically if we get a 255mb buffer size?
Yes, it is with 255 buffer, photo mode. Every time you switch yor cam on you have to set high iso noise reduction to multi because its always gets back to "single" setting. I don,t use hack mode, I have to see what I am recording. Other settings its force left. Remember, that every first time shooting (after switching on) is shorter, second time its getting full lenght. On sandisk 45 64GB I have 38-39,5 write speed.
Hacked mode is when you press Q on raw options there is canon, auto, hacked, something. Hacked mode freezes LV screen on the first frame so I beleieve It would be good only for static shots because you cannot frame properly. Sometimes its improving write speed and sometimes not, seems it depends on the resolution.
with photo mode set to jpeg only!
To reiterate: you must be in photo mode with live view running, before doing anything. Then go into high iso speed NR and switch to NR.
set fps overide to 24 because default is 30.
To make sure the camera doesn't stb when you are recording, set exposure overide to on.
So .. you guys are taking a video while not seeing what is being seen through the camera?
how do you focus/view what you're recording?
craycray
In photo mode with 255MB buffer
Recording @ 1600x608 with GlobalDraw ON, Exp override ON, FPS override 24, it can record limitless.
I just recorded 100GB on a 128GB Sandisk Extreme 45MB/s
1600x608 (ratio 2.67) with factor 1.2x = 1920x730 endless recording
Very stable, no matter the scene kind you shoot (inside/outside/day/night/moving/stay...etc)
Tested more than 50 times.
1536x636 (ratio 2.35) with factor 1.25x = 1920x795
Very stable too but start skipping frames after 3500 frames (2.3 minutes)
I'm very happy with that already !
1%, would it be possible to record sound using very low quality ?
In Canon default, it records in PCM so... high quality, so does ML with separate wav.
Could we for example modify wav recording parameters ? 8bits, lower bitrate ?
Other way: have an optional 2nd synch beep after recording ends
Synch beep when start, then synch beep just after or when stopping recording.
This way, you can record sound with external recorder (Zoom, Tascam, wathever) cut the audio file in sub files
starting and ending with beeps then synch them with video sequences in your NLE.
With 2 beeps, would be easier to synch... am i wrong ?
Funny thing:
When u start the cam in photo LV, with Noise reduc OFF, memory available: 151MB
You change Noire reduc to NR, memory available: 255MB
You change back Noise reduc to OFF, memory available: still 255MB
Does it tell something ?
Oh! Thanks!!!! I'm successfully installed ML!!
But ML is suspended when use WIFI REMOTE (at review)..
Is it just me? T.T
ASSERT: FALSE
at ./ASIF/ASIF.c:486, task ASIF
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013May31.6D113
Mercurial changeset : 28a4eab0513e+63d5922fdcd9+ (unified)
Built on 2013-05-31 23:07:58 by user@D610.
Free Memory : 445K + 2286K
Wifi + Liveview = problem
Can't work together yet
Quote from: teo770 on June 05, 2013, 01:39:58 PM
Wifi + Liveview = problem
Can't work together yet
oh.. that's so sad..
I think just WIFI Photo Transmission is problem too...
Quote from: ckstoa on June 05, 2013, 11:35:49 AM
Oh! Thanks!!!! I'm successfully installed ML!!
Hello, what exactly is the file to download for the 6D ?
For 5D mark III
For 7D
For EOS-M ?
I guess it could be the 5D mark III, because they are so closed.
Bst Rgds
Yann
I monitored successfully with the phone while recording video. I dunno about photo transmission or any of that. Will have to see.
Also will try to turn off NR and see if the memory stays/can flip to video mode.
Its a hack... having bvram_mirror in shoot_malloc crashes out the multishot just like raw converter and makes it give up the memory.
*Other than Busy error on screen it looks to stay in video mode too. great find.
Managed to get into 60fps mode...
Override to 24.
Photo mode NR ON
wait... NR off ... wait
Switch to 720P... wait
Push up fps to where it doesn't crash... I was able to do 48.
Feels like getting there was a contra cheat code.
When is it going to be possible to not have to turn on and off noise reduction in some ritualistic procedure every time to o tain 255mb buffer size?
When I figure out how.. so far no luck.. at least I got into movie mode with it.
Quote from: 1% on June 05, 2013, 03:14:13 PM
I monitored successfully with the phone while recording video.
Is this a new test you've done? As in you managed to get it working stable? I take it that's when shooting h.264 is it? If so that would be awesome man!
Not H264... no movie mode with wifi still.. With raw video +memory hack.
Stable... not yet. got it to stop doing busy when entering nr mode... leaving it is another matter and still hard. Probably have to patch the semaphore of it quitting. Every you hit h/s in movie mode it gets "busy".
Likes to crash alot too..
I guess semi-stable in photo mode if you leave the NR on, it doesn't actually do the NR.
HDR does it too... needs diff patch. Also there is Change memory for factory.. hopefully it frees the memory too.
Factory mode takes memory....
If SRM_ChangeMemoryManagement functions are understood then this might be doable trouble free.
3 Canon functions seems to free 255MB:
- high iso NR
- multiple expo
- HDR
Noone of these are available on video mode.
Using those functions, firmware seems to "makes room" to prepare incoming of multiple pictures...
I can try to force them on in movie mode like I did with the NR, don't remember seeing it in the menu unti I forced it.
*Tried them all.. the properties don't change in movie mode... at best some blue blocks appear but they are fragmented as hell.
I think just NR off makes some blue blocks in movie mode... but how to free them and recover them.
Quote from: 1% on June 06, 2013, 12:58:31 AM
I can try to force them on in movie mode like I did with the NR, don't remember seeing it in the menu unti I forced it.
Try it, can't hurt right?
We are kind of lucky that 6D had in camera HDR (jpeg), if it would have the RAW HDR function only.... wouldn't had to make room in memory to calculate the HDR directly onboard !
+1 to 6D !
Quote from: 1% on June 06, 2013, 12:58:31 AM
I can try to force them on in movie mode like I did with the NR, don't remember seeing it in the menu unti I forced it.
You've got the NR choice in high ISO nr menu while in video mode ?
In a not yet released update i think.
Not sure activating the 3 functions in video mode will free more mem. They must have defined the same reserved mem space for multi pics functions but.... who knows !
We are now at 7 x 32Mb buffer.... but 255MB free would normaly contain arround 8 x 32
The buffer line displays only 7 stars... There is a problem with the 8th ?
To go forward: getting more and more free mem for buffers will allow us to film longer time without skipped frames, ok.
Perhaps we will someday get 10x32MB buffers. But about writing speed, we know the 6D is running at 50MB/s top.
We can actually record at max 39MB/s on cards handling twice this write speed...
Is there any way to investigate where is the bottleneck in camera ?
Yea.. I forced on NR in movie mode by altering the property and now have NR in movie mode... except #4 is missing.
Also, NR and multi expo + hdr are all 3 separate memory functions... there is also inner develop configuration and image configuration... inner develop seems to do something but it gives me assert #5 and I can't find it anywhere in the firmware.
On EOSM NR dumps the memory no patches... on 6D not sure if it did without bvram mirror causing some error to make it free the memory. Just configuring the memory doesn't free it but usually turns it into blue blocks
Quote from: teo770 on June 06, 2013, 01:15:11 AM
You've got the NR choice in high ISO nr menu while in video mode ?
In a not yet released update i think.
Not sure activating the 3 functions in video mode will free more mem. They must have defined the same reserved mem space for multi pics functions but.... who knows !
We are now at 7 x 32Mb buffer.... but 255MB free would normaly contain arround 8 x 32
The buffer line displays only 7 stars... There is a problem with the 8th ?
To go forward: getting more and more free mem for buffers will allow us to film longer time without skipped frames, ok.
Perhaps we will someday get 10x32MB buffers. But about writing speed, we know the 6D is running at 50MB/s top.
We can actually record at max 39MB/s on cards handling twice this write speed...
Is there any way to investigate where is the bottleneck in camera ?
I 100% agree with Teo, why are we getting 39mb/s when uhs-1 standards are supposed to be 45mb/s and the camera apparently has the ability to shoot 50mb/s. We need to find the bottleneck...
I believe aspect ratios are off as of right now. 1728 at an aspect ratio of 2.67 has a vertical resolution of 672, it should be 648.
8th may be the double buffer chunk. When I looked at the readout there were only 7 big blocks.
We'll see what happens with the write, not sure how to make it go any faster. Maybe this is realistic performance of the SD controller they chose. USB 2.0 also specced at 50MB/s and usually you get much less.
Dunno where we could get any more memory from. The other memory isn't blue so something is indeed writing there.
I know this seems unlikely but couldn't we just look for a pcb that supports higher write speeds thats compatible with canons DSLRs? I mean isn't there ways to look up internal parts for electronics such as this? If some type of semi-specialist (a person who works in this type of field) could get a copy of a 6d or other dslr, and find the pcb that does the writing, could they replace it with one that supports higher write speeds?
Edit: What we need is a service manual to find out how to disassemble, etc.
For example with a quick google I found the 5d mark ii's service manual, can't seem to find a 6d's...
Here's where I downloaded it from: file:///C:/Users/Brandon/Downloads/Canon-5D-Mark-II-Parts-Lists-and-Schematics.zip (http://file:///C:/Users/Brandon/Downloads/Canon-5D-Mark-II-Parts-Lists-and-Schematics.zip)
Service manuals for canon are hard... they have to be leaked. Maybe if someone asks nicely they will leak the 6D one.
I do this kind of thing... and I don't think its feasible. We would have to be damn lucky to have the IC just work in place without major canon FW rewrite at regular speed. Someone would probably have to design a new IC as a drop in replacement and fab it. Then you get the fun of reworking/aligning it.
If we find the SD controller we could at least see what the next model up does... btw 208mhz strings are not in the firmware so the camera would have no clue about even using the higher write speed. CF this is apparently "easy".. mainly because CF behaves 90% like IDE... micro-drive is powering my router right now.
We're just not going to squeeze any more out of this without throwing away data. SD is a shitty solution. With enough memory at least "almost" hd sizes are possible and its like 10x better than H264. We basically have a mini BMCC at this point. Audio is a sticking point... no matter how far you reduce the wav, writing will still be taken from the video.
Quote from: 1% on June 06, 2013, 03:25:25 AM
Service manuals for canon are hard... they have to be leaked. Maybe if someone asks nicely they will leak the 6D one.
I do this kind of thing... and I don't think its feasible. We would have to be damn lucky to have the IC just work in place without major canon FW rewrite at regular speed. Someone would probably have to design a new IC as a drop in replacement and fab it. Then you get the fun of reworking/aligning it.
If we find the SD controller we could at least see what the next model up does... btw 208mhz strings are not in the firmware so the camera would have no clue about even using the higher write speed. CF this is apparently "easy".. mainly because CF behaves 90% like IDE... micro-drive is powering my router right now.
We're just not going to squeeze any more out of this without throwing away data. SD is a shitty solution. With enough memory at least "almost" hd sizes are possible and its like 10x better than H264. We basically have a mini BMCC at this point. Audio is a sticking point... no matter how far you reduce the wav, writing will still be taken from the video.
Ok. Thanks for the input :). Can't parts run faster than what they are spec'd for but at a slight risk (if not forced too hard) of damage? Thus couldn't we make it run faster? Or at least could we change how the firmware is coded to allow for higher transmitting speeds?
I'm just thinking of anything to possibly lead anywhere, many others and I have their fingers crossed that we'll get higher resolutions. I know we won't get 1080p, I'm totally understanding that that won't be possible (unless we get a whole new IC). I think people (including me) want around 1800 horizontal resolution with a high aspect ratio (around 2.5+ maybe 2.35). Or 1700 or so with a 16:9 ratio for those who don't want too much letter boxing.
Its not like CPU with a few clocks... its like DDR2 vs DDR3, etc. Completely different timings.
[113] Today.zip crashes a lot Err 70.
Both photo and video mode
Quote from: 1% on June 06, 2013, 03:25:25 AM
If we find the SD controller we could at least see what the next model up does... btw 208mhz strings are not in the firmware so the camera would have no clue about even using the higher write speed.
I presume u already know this page:
http://www.lensrentals.com/blog/2012/11/a-peek-inside-the-6d
One more guess... maybe there is a way to save data by the USB port ? It should have 60MB/s if it is 2.0 standard, so it is also interresting. Maybe we could connect external SD card or some kind of drive? I know that problem will be in drivers and software to save via USB... but it's worth to look into it :)
with update: [113] ETTR-MemDontclick.zip
Photo mode, High iso to multi NR
Exp override, FPS override, global draw off
1536x656 (2.35): 7.5GB, 4500 frames, 3.12 minutes till frame drops
With framing force left, even better:
1536x656 (2.35): 8.7GB, 5300 frames, 3.40 minutes till frame dropts
I don't mean to sound like a broken disc lol but can't we do anything to improve separate wav audio?
I can record at 39MB/s video but less than 29 with separate wav.
It can't be write speed, the wave files are tiny compared to RAW files. Is it too much work for the processor or something?
Quote from: sparedog on February 11, 2013, 03:46:54 PM
Yay, Mosaic Engineering has now released it´s anti-aliasing / anti moire filter for the Canon 6D, the VAF-6D.
I´m going to get one in a couple of weeks and test it out
Sparedog, do you have VAF-6D? I am very interested in it, seen couple of tests and looks very good IMO but I would like to hear about it from the actual owner. Is picture with this filter comparable with the one from 5D3?
VAF-6D owners - please give your honest opinion :)
Quote[113] Today.zip crashes a lot Err 70.
What error is it?
Quotehttp://www.lensrentals.com/blog/2012/11/a-peek-inside-the-6d
No closeup of SD chips.
For audio, not really. It will take CPU + write.. when it dumps the wave every X times the edmac write is slowed down.
Quote from: 1% on June 06, 2013, 05:40:19 PM
What error is it?
Sorry, my mistake !
Photo mode, Global draw off, override exp ON, override FPS 24
1536x656 (2.35): 8,5GB, 5200 frames
Some trouble on 2nd or 3rd recording somtimes. The LV button is getting his function back (LV)
I never get 255MB buffer in video mode. If coming from photo mode, always trun in Busy state
Quote from: 1% on June 06, 2013, 05:40:19 PM
For audio, not really. It will take CPU + write.. when it dumps the wave every X times the edmac write is slowed down.
IMO, audio is really a non issue for now...
You NEED to go on your computer to develop the DNG's and convert image sequence to a movie, color grade....
Recording sound on the camera.... With the synch beeps.... worth the money to buy a Zoom H1 and synch in post.
Video mode is hard... I got into 720P 60 like twice. Usually it errors out unless you wait out all the busies.. and then h/s makes it busy again.
[113] Just small Changes with addition of H264inis
In raw menu when pressing playback camera hangs every time - red light blinking, no response, taking out battery.
Those new H264inis are required with the latest build?
I've the same problem, I think it's related to memory hack that gets 7 buffers when we go into multiple shot noise reduction.
So, with this hack, no preview is available. It's a pity. I don't know if it will be any workaround.
But you don't need any hack to have 7 buffers, just high iso NR multi.
Buf, well the situations it's a bit confused for the tests. Whe have two improvements at once implemented in SW that provide more buffers:
Today's Alex one "raw_rec: added a memory allocation hack: on 5D3, this brings 2x32M extra :D" and the previous (two days?) "multishot noise reduction" from 1%. This one it's OK in photo mode but I found caveats: no play mode, no simultaneous raw photo , movie mode erratic, change noise reduction on each restart, etc...
The play mode problem arises for me in every circumstances, for example if I was reviewing the raw video I cannot preview anymore: red light blinking is because of raw preview processing, but no image on screen".
Well, then I try the today's version from 1% repository that includes Alex hack. First try I don't obtain more buffers but now (?) whitout change, I obtain 7 buffers (3 more) automaticaly!!! (only the default memory hack on: new raw_rec menu option), but:
I don't need change iso noise reduction, so I have raw. Video mode OK and playback OK. I don't understand why I cannot obtain more buffers at first try.
Quote from: nandoide on June 06, 2013, 10:34:44 PM
Well, then I try the today's version from 1% repository that includes Alex hack. First try I don't obtain more buffers but now (?) whitout change, I obtain 7 buffers (3 more) automaticaly!!! (only the default memory hack on: new raw_rec menu option), but:
I don't need change iso noise reduction, so I have raw. Video mode OK and playback OK. I don't understand why I cannot obtain more buffers at first try.
I catch it: If photo quality is L, Alex hack don't throws more buffers, if photo quality is raw we get 3 more buffers!!!!
1%, Alex, contratulations once more, this transforms the 6D in a very capable raw video camera.
Quote from: kgv5 on June 06, 2013, 05:35:41 PM
Sparedog, do you have VAF-6D? I am very interested in it, seen couple of tests and looks very good IMO but I would like to hear about it from the actual owner. Is picture with this filter comparable with the one from 5D3?
VAF-6D owners - please give your honest opinion :)
I didnt buy one in the end, only because my short film project has been postponed... script problems :(
1% in the latest ML releases in raw video we can't choose higher vertical resolutions than 1792. Why can't you let us choose higher than this? Also when will the release be hardcoded so my settings don't disappear every bloody time I reset my camera. And what about keeping the 7x32mb buffers enabled from the start without having to do some ritualistic procedure every time.
Sorry to nag, just curious.
The settings don't save because I think modules don't support config files.. I know, bummer.
You can't chose over 1792 because that is about where canon size is. "full" size is only 1824. 28x64 is already 1792.
BTW, got the card from noisyboy (BIG THANKS!)... I can finally join the HD club. Its writing at 40MB/s... will format it to exfat and see if that makes any difference. As a plus I can test the 113 updater fir I got this morning.
A1ex hack is working! Thanks nanotide... I wouldn't have figured it out.. have to see what it does on 600D with no sraw.
No 600d... but maybe EOS-M
Quote from: 1% on June 07, 2013, 03:07:42 AM
The settings don't save because I think modules don't support config files.. I know, bummer.
You can't chose over 1792 because that is about where canon size is. "full" size is only 1824. 28x64 is already 1792.
BTW, got the card from noisyboy (BIG THANKS!)... I can finally join the HD club. Its writing at 40MB/s... will format it to exfat and see if that makes any difference. As a plus I can test the 113 updater fir I got this morning.
A1ex hack is working! Thanks nanotide... I wouldn't have figured it out.. have to see what it does on 600D with no sraw.
No 600d... but maybe EOS-M
Thanks for the response. How does exfat benefit write speeds? Of so can I just remove the current files to my computer, format my sd card, and drag the files back on again? Do I have to make my card bootable again?
All the test I have done were with a card formatted exFat and I have not seen much difference with your results tho.
Gain from exFAT formating, in my experience, is +0.2 to +0.3MB/s using 4096 cluster size.
The major gain is exFAT can handle files bigger than 4GB !
have you looked at the HDMI interface? according to the wikipedia page even hdmi 1.0 can do 1.6Gbit/sec (around 200MB/sec) or more depending on the mode. it may take special software or hardware to receive the data, but if it's even possible to dump it out at those rates it could be very interesting
if nothing else, for those looking for audio, this may be a way to get the audio out of the camera
This was discussed many times and as far as i know not possible due some to technical limitations
hi,
i have a simple question: i'm using ML on my 6D mainly for things like magic zoom, zebra etc. so i am generally fine with the 'classic' 1920 or 1280 video recording settings.
now i noticed that with ML 'on' (no modules loaded, no raw recording), the data rates of the clips recorded are very different from when i shoot with ML 'off' -> esp. the 'IPB' doesn't seem to work / compress anymore, the files are just about as big as with 'ALL-I'.
is that a regular behaviour? is that because i'm using the developer kit (version from june 1st)? thanks a lot!
jan
Maybe you have changed something in the ML encoder settings, with encoder set to default/stock canon h.264 it should't affect stock all-i or ipb bitrate.
Quote from: xNiNELiVES on June 07, 2013, 07:36:33 AM
Do I have to make my card bootable again?
yes, after you have dragged the files on, make it bootable
Quote from: 1% on June 07, 2013, 03:07:42 AM
You can't chose over 1792 because that is about where canon size is. "full" size is only 1824. 28x64 is already 1792.
in which mode are you getting 1792 vertically, the most i get is 1216 when i choose 9:16
Quote from: sparedog on June 07, 2013, 11:47:41 AM
in which mode are you getting 1792 vertically, the most i get is 1216 when i choose 9:16
I meant horizontal resolution sorry... I can't get above 1792 horizontal resolution...
1% there's a bug when we use 7 buffers. We have to use the camera in photo mode, I can't seem to even expose my own videos. The camera chooses automatic settings, there's also no live exposure (I believe this is caused by the multishot noise reduction). Then when I shoot videos the camera changes exposures on the fly to update for each scene. This looks obviously really ugly, plus I can't even control my own camera!
Expo override. Or use quality raw + a1ex hack in video.
Clusters are funny.. I tested with the 32gb sandisk.
Fat32 seemed faster at first but with more testing it now looks to write about the same.
Fat32 clusters were 32, card native is 512 (ok reults)... 128k (better), 2048k(same) seemed to give good results... 4096 didn't seem to help, 32MB clusters only slowed it down. 32k like fat 32 seemed to ideal.
Highest write was 41.something MB, usually 38.8-39.9.
Quote from: 1% on June 08, 2013, 03:18:25 AM
Expo override. Or use quality raw + a1ex hack in video.
Clusters are funny.. I tested with the 32gb sandisk.
Fat32 seemed faster at first but with more testing it now looks to write about the same.
Fat32 clusters were 32, card native is 512 (ok reults)... 128k (better), 2048k(same) seemed to give good results... 4096 didn't seem to help, 32MB clusters only slowed it down. 32k like fat 32 seemed to ideal.
Highest write was 41.something MB, usually 38.8-39.9.
Ok. I get everything except what you meant by quality raw + a1ex hack. What's that?
The 5d3 memory hack for video mode.. its on by default just set pic quality to raw and try it in video mode.
Quote from: 1% on June 08, 2013, 04:41:52 AM
The 5d3 memory hack for video mode.. its on by default just set pic quality to raw and try it in video mode.
It gives 255mb buffer? Is this in the newest release? Never heard of this...
I think its only 6X32 but close enough and not hard to use 60P.
Quote from: jankyy on June 07, 2013, 09:44:51 AM
hi,
i have a simple question: i'm using ML on my 6D mainly for things like magic zoom, zebra etc. so i am generally fine with the 'classic' 1920 or 1280 video recording settings.
jan
Hello Jan,
I'm happy to read that you use without problem ML with your 6D without problem regarding magic zoom, zebra. I'm also interesting by classic 1920 x 1280, I own a 6 D and a 60D, on my 60D I've Magic Lantern, and I'd like to get it like you on my 6D.
So could you confirm to me the good file to download ?
I suppose it's the Alpha for 5D Mark III ?
Thanks by advance :)
Yann
Canon's RAW CR2 format details: http://lclevy.free.fr/cr2/
Might help but i think u already know that
Quote from: yannlesaout on June 08, 2013, 09:37:58 AM
I'd like to get it like you on my 6D.
So could you confirm to me the good file to download ?
I suppose it's the Alpha for 5D Mark III ?
Thanks by advance :)
Yann
Go back in previous pages, Noisyboy started a "6D How to" dedicated thread... here:
http://www.magiclantern.fm/forum/index.php?topic=5530.msg39370;topicseen#msg39370
Quote from: 1% on June 08, 2013, 05:02:04 AM
I think its only 6X32 but close enough and not hard to use 60P.
the clusters are 7x32M
1920x720 10" (247 frames) 24 fps override on 5x video mode (compiling latest sources)
1808x678 14" (330 frames) 24 fps override (really no necessary so canon video mode 1920x1080 24 fps gets the same) on 1x video mode
sandisk extreme pro 95 32 GB (FAT32), global draw on with focus peaking
Quote from: 1% link=topic=3904.msg47883#msg47883
Highest write was 41.something MB, usually 38.8-39.9.
Did you have consistent 41 or only half a second peak?
With Sandisk Extreme Pro, got 40MB/s peak too, but filming continuously works till 39.2MB/s
Quote from: nandoide on June 08, 2013, 10:32:25 AM
the clusters are 7x32M
1920x720 10" (247 frames) 24 fps override on 5x video mode (compiling latest sources)
1808x678 14" (330 frames) 24 fps override (really no necessary so canon video mode 1920x1080 24 fps gets the same) on 1x video mode
sandisk extreme pro 95 32 GB (FAT32), global draw on with focus peaking
That's very good result IMO and I think fully usable.
So 5x zoom gives 1920x720 and not 1792x something?
did your write speed exceeds 40MB/s for a longer time than a one second?
Quote from: teo770 on June 08, 2013, 11:15:20 AM
With Sandisk Extreme Pro, got 40MB/s peak too, but filming continuously works till 39.2MB/s
Yeah, its like sandisk 45. damn, I would buy pro if it has additional consistent 1-2 MB more. CF guys probably are laughing when reading such posts ;)
Like sandisk 45? I expected that :-( but it's good to confirm :D, because I'm thinking on buy the 64 GB 45 one cause it's a lot cheaper than 95.
These raw videos eat the card :-)
My rates are sustained 39.x, sometimes on a veeeery short lapse 40 ... I think 45=90 for this cam. It's a pity (the bus, the clock bus, ...)
Hi, I´m trying to do some tests with a Sandisk Extreme Pro 32Gb
I see the only way to get 32x7 is using still mode the go to NR and selecting Multi, then I can see the 32x7, but on this lastest version ([113] Just small Changes.zip) I can not go higher than 1792 width, could you let me know how to try higher than that?
Alex is doing continuously changes on image sizes searching for speed improvements. The version i try has 1920 on 5x but could not be the last word. I compiled the sources.
I shot 200+ Raw sequences. 100GB the biggest.
Whatever resolution or ratio u choose,
in movie mode, continuous recording (without frame skips) with global draws.... seems very stable under 39MB/s.
In photo mode, major problem (the only one for me) is the lack of IS (lens stabilisation).
But you can go a bit forward cause it seems to use less canon functions....
It's not night & day neither.... from 39.2 to 39.5MB/s for myself.
1%, on the line "Capturing frame XXXX...", could we add another counter: frame count devided by FPS ?
So we'd know immediatly how many secondes we're recording.
Gobian, in order to get the memory hack from Alex you need select Memory hack ON on RAW menu and photo quality RAW, not jpg (the oposite as nr noise reduction, that needs jpg). Because that trick I thought at first (and I think 1% also) that the hack didn't go on 6D.
And really is better than 5Dm3. We have 3 more 32m buffers. 5Dm3 only 2 (but they have CF...) (Then with this hack you can take RAW photos and RAW videos without changing configuration)
Doing so, you get 7 buffers on raw recording, video or photo
For raw video stabilization in photo mode I use start delay to 2 sec. on raw menu, to get time to start pressing the shutter button all the time while recording (M mode)
Thanx so much nandoide, i´m doing tests now with Alex hack. :)
Counter is in... that was a good idea to take care of the seconds. No extra counting.
Quote from: teo770 on June 08, 2013, 10:17:12 AM
Go back in previous pages, Noisyboy started a "6D How to" dedicated thread... here:
http://www.magiclantern.fm/forum/index.php?topic=5530.msg39370;topicseen#msg39370
Thanks a lot !!!!! ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D
Yann
Quote from: 1% on June 08, 2013, 04:36:46 PM
Counter is in... that was a good idea to take care of the seconds. No extra counting.
Umm I tried the new version and the its good and bad. You fixed the aspect ratios which is good, you also put a time counter in seconds of how much footage we have. I know there are numerous other additions that I noticed, they're all good. The bad is that whenever I take video (even without the 2 second delay) the live view temporarily freezes goes to black and then starts. Recording is delayed. Also I don't know why you allow us to see all these other resolutions in which we apparently can't use. It seems a bit unnecessary, this part is my 2 cents though... I know you explained it before, but I still don't see why we can't record above 1792...
The LV blanks to grab the memory... the other resolutions are for zoom mode.
Quote from: 1% on June 08, 2013, 08:38:49 PM
The LV blanks to grab the memory... the other resolutions are for zoom mode.
When I told you earlier about how in photo mode the camera uses auto exposure. You told me to use exposure over ride. I did but exposure simulation isn't fully working. The aperture simulation is working but iso exposure simulation isn't. Can you forcefully enable this? It's detrimental to taking video.
Also in previous versions the screen didn't turn black as long as the new versions. That's my complaint about this new version...
Quote from: xNiNELiVES on June 08, 2013, 09:59:17 PM
Also in previous versions the screen didn't turn black as long as the new versions. That's my complaint about this new version...
With short blackout when beginning recording: 7x32MB buffers
Without: 4x32MB buffers
More buffers => more resolution or time ...
Quote from: 1% on June 08, 2013, 04:36:46 PM
Counter is in... that was a good idea to take care of the seconds. No extra counting.
Thanks for that 1% !
Next: the format
... Hours:Minutes:Seconds:frame (1-24) with a "timecode font" ::)
i know, i know..... don't tell it !
ISO has to be adjusted from ML menu in expo override.
Latest build is incredible! So much data on the screen and ETTR histogram is amazing, plus the raw zebras... I feel like it'll be impossible not to get perfectly gradable footage now! Memory hack and everything working smoothly.
Many thanks!
One bug to report. Sometimes, after I record, global draw is forced off and my record button no longer works. Switching from movie to photo and back to movie fixes this immediately.
Yep, had that on 600D, have to see why... and now 600D build is broken, or I'm out of memory :(
Quote from: 1% on June 09, 2013, 01:45:40 AM
Yep, had that on 600D, have to see why... and now 600D build is broken, or I'm out of memory :(
Ok got exposure simulation to work with ML iso. Thanks. Still though there is still a issue with how it blacks out and freezes temporarily. On the bigmemphoto version there is none of this. I might just post a video to show what I'm talking about.
1% I still don't understand why anything over 1792 horizontal resolution isn't possible. I see that in 5x and 10x mode it is. Why is this? How can the 5D Mark III, besides it's insane write speeds, pull off 1920 x 1080 continuous video. Does the Mark III have to use 5x mode or something?
This is what you said:
"You can't chose over 1792 because that is about where canon size is. "full" size is only 1824. 28x64 is already 1792"
-1%
What the hell are you even saying? >:(
When I tested old module lv-rec which theoretically gives an option of 1920x1080 raw, when I checked it in AE it showed 1824x something resolution.
-
It has to black out... no blackout = no memory. Just disable that hack and use the photo mode one if you want. Its in the raw_rec menu... Either 5d3 HD buffer is bigger or they are shooting in 5x like every other camera. I'm guessing latter.
Quote from: 1% on June 09, 2013, 10:01:13 AM
It has to black out... no blackout = no memory. Just disable that hack and use the photo mode one if you want. Its in the raw_rec menu... Either 5d3 HD buffer is bigger or they are shooting in 5x like every other camera. I'm guessing latter.
Does 5x mode actually crop the image?
It doesn't scale as much... basically a 1:1 of the sensor in a few pieces.
Where are we at as far as ratio vs continuous shooting? I'd like to work on filling in the "matrix" chart that's been floating around but would like to start at where we see our tops right now.
Quote from: xNiNELiVES on June 09, 2013, 08:36:11 AM
This is what you said:
"You can't chose over 1792 because that is about where canon size is. "full" size is only 1824. 28x64 is already 1792"
-1%
What the hell are you even saying? >:(
Mate - I really don't want this to be awkward or anything and we like to keep things nice around here so I'm only gonna politely request this but will you please try and be a little more mindful of your tone dude? You probably don't mean it to come across as rude but it does. There is no tonality in text so I get that you might not mean to come across as impolite but your comments often come across as being very demanding and negative. Remember this is a development forum and positive/constructive feedback is king, not complaining that things don't work. It's not a big deal, just asking you to be conscious of the fact 1% is helping you out MASSIVELY by doing all of this in his spare time and asks nothing from you in return. Just be nice man. Simples :)
Quote from: 1% on June 09, 2013, 07:29:10 PM
It doesn't scale as much... basically a 1:1 of the sensor in a few pieces.
Does anyone know if moire is less in 5x mode. I tried testing, but my place of moire - some local buildings - have been out of bounds for me for a while lol
Is there any setup where we can do 720 60p in rawc. I saw some mention of it earlier in this thread, but nothing more was said about it.
[edit] if not 720 60p can we do 720 48fps in rawc? if so, how?
Dumb question, is this file only for EOSm or is it also for 6d [EOSM] - 5D3 Rawtype.zip
on 5x mode the moire is 0x, or nearly.
Quote from: nandoide on June 09, 2013, 09:55:53 PM
on 5x mode the moire is 0x, or nearly.
so let me try and get my head around this. with 5x a 24mm becomes a 120mm, plus the crop factor of 720 vs using the whole lv frame, maybe half?...240mm? But all this, with the distortion characteristics of a 24mm at the center of the lens? Ive gotta test this, does it look cool, or does it look freaky?
=D
Quote from: noisyboy on June 09, 2013, 09:03:31 PM
Mate - I really don't want this to be awkward or anything and we like to keep things nice around here so I'm only gonna politely request this but will you please try and be a little more mindful of your tone dude? You probably don't mean it to come across as rude but it does. There is no tonality in text so I get that you might not mean to come across as impolite but your comments often come across as being very demanding and negative. Remember this is a development forum and positive/constructive feedback is king, not complaining that things don't work. It's not a big deal, just asking you to be conscious of the fact 1% is helping you out MASSIVELY by doing all of this in his spare time and asks nothing from you in return. Just be nice man. Simples :)
Sorry :(.
Edit:
1% are there changelogs for all your versions? For example whats in: [113] Its New.zip?
sparedog, 5x is a digital teleconverter of 3x, 24 mm becomes a 72mm equivalent
we call this 5x because we get that with the 5x mode zoom of the cam, but the image we obtain is 3x.
but no more than 3x: 5x mode is not linked to video mode.
the good, the image is on the center of the lens. distortions. less than full frame image
optical quality better than full frame image but image quality less than a raw photo image: it's a 100% crop of a raw photo image, but better than full frame raw video image, because this one is "like" a crop of the sensor (same number of points selected) but getting points sparsely over all the surface of the sensor = moire and aliasing.
The best cams for 5x mode: the cams with the less sensor density of points: full frames, ... 6D perhaps the best
xEightLives, you have lost one live in this forum :P ;)
The developers have chosen 1792 over 1824 for optimization purposes: more frames saved on disk without skips. There is a mathematical-algorithmic trick based on getting sizes multiples of certain number.
And 1792 scales very well to 1824.
Quote from: nandoide on June 09, 2013, 10:53:27 PM
xEightLives, you have lost one live in this forum :P ;)
The developers have chosen 1792 over 1824 for optimization purposes: more frames saved on disk without skips. There is a mathematical-algorithmic trick based on getting sizes multiples of certain number.
And 1792 scales very well to 1824.
lol ok, thanks for the explanation. ;D
Commits are right where you get the downloads from... pretty much full changelog.
720PXX is doable... I dunno if 60 crashes it, I think on digic V it doesn't.. I already did 48fps no problem... not sure if it will work at full res, I guess just follow the MB/s indicator.
Quote from: 1% on June 09, 2013, 11:05:55 PM
Commits are right where you get the downloads from... pretty much full changelog.
720PXX is doable... I dunno if 60 crashes it, I think on digic V it doesn't.. I already did 48fps no problem... not sure if it will work at full res, I guess just follow the MB/s indicator.
What? Where? All I see is tags and branches...
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/all
Some more descriptive than others.
Quote from: 1% on June 09, 2013, 11:23:22 PM
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/all
Some more descriptive than others.
Thanks. I've noticed that you seem to compile new versions in the morning, why is this? Just curious.
I wake up.. compile/test and then go to work, use the camera, etc.
Quote from: 1% on June 09, 2013, 11:39:21 PM
I wake up.. compile/test and then go to work, use the camera, etc.
Oh lol
does 5x mode use more memory? at 720 24fps normal mode I can record for ever, but with 5x mode, I can only record 780 frames
Quote from: xNiNELiVES on June 09, 2013, 10:29:01 PM
Sorry :(.
You're cool big dog, don't worry! We're all friends here 8)
1% - Dude, what does this (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/bd8d1fb96854fc25f710c49e4824a1464783e647) commit do? I see it seems to get rid of auto iso judging by the description but what actual effect does that have on shooting? Or is this to do with ETTL? Cheers bro!
Quote from: noisyboy on June 10, 2013, 12:15:00 AM
You're cool big dog, don't worry! We're all friends here 8)
Ok :)
Quote from: sparedog on June 09, 2013, 09:47:05 PM
Does anyone know if moire is less in 5x mode. I tried testing, but my place of moire - some local buildings - have been out of bounds for me for a while lol
Is there any setup where we can do 720 60p in rawc. I saw some mention of it earlier in this thread, but nothing more was said about it.
[edit] if not 720 60p can we do 720 48fps in rawc? if so, how?
Dumb question, is this file only for EOSm or is it also for 6d [EOSM] - 5D3 Rawtype.zip
EosM only bud.
where do i get the scripts from, i always have this dir scripts missing message on start up. What do they do?
Just add an empty scripts folder in ML... I haven't seen any TCC scripts.
The commit is for ML auto iso which is superseded by auto ettr. A1ex pulled it out.
I am not sure that bulb timer works any more in b mode
Ahhhh - got ya!
Quote from: 1% on May 27, 2013, 07:09:42 PM
rc.ini ,etc are for H264.. you can turn autoload off or leave it on, won't make a difference until you record H264
hi, can somebody explain in a little more detail how the encoder options 'off/h264.ini / CBR fixed QP / VBR / Rate Control' relate to the settings IPB / ALL-I in the canon menu? just in case one doesn't want to do raw recording (yet), but 'classic' 1920 or 1280 video on a fast card, what's a good setting to start with?
i seem to get confused by the new encoder menu, since the options are different from the ones described in the user manual. thanks so much!! jan
Do you think exifs data could come in the DNGs ?
Lens used, aperture, shutter, iso ?
So we can for example split main movie in sub sequences based on Aperture value, apply different parameters according to aperture.
Would be very cool when you change aperture or shutter value while recording... (changing shutter value is a non sens to me).
thats not a bad suggestion.. .raw.c will have to take that into account at some point.
Quote from: 1% on June 10, 2013, 07:05:45 PM
thats not a bad suggestion.. .raw.c will have to take that into account at some point.
So modules don't save settings because they don't have config files. Won't raw recording be part of the ML auto exec so it will save settings? It's a huge pain. Thanks.
ML team, thanks again for your work
Next video shot in the RAW on Canon 6d
With the last release [113] Unified Raw Module.zip, i see quasi no more difference btw photo and video mode.
It's like if video mode as reach the photo mode in terms of buffers, time recording... etc
You agree ?
Good thing....
Quote from: teo770 on June 12, 2013, 12:09:19 AM
With the last release [113] Unified Raw Module.zip, i see quasi no more difference btw photo and video mode.
It's like if video mode as reach the photo mode in terms of buffers, time recording... etc
You agree ?
Good thing....
Are you saying video mode has 7 buffers now?
Yeah, speed seems to be the same (and IMO the same like the previous build) - it is still (very satisfying for me) 280 frames (hack OFF) in 1792x752.
Quote from: kgv5 on June 12, 2013, 12:30:27 AM
Yeah, speed seems to be the same (and IMO the same like the previous build) - it is still (very satisfying for me) 280 frames (hack OFF) in 1792x752.
What about 1792 vs 672?
It will give ~ 420 frames, little bit too wide for me.
Quote from: kgv5 on June 12, 2013, 01:00:06 AM
It will give ~ 420 frames, little bit too wide for me.
420? Thats less than the current version, unless thats just my memory card or optimized cluster size... I get 450 sometimes 434. About 70 30, I'm trying a new cluster size it may be more promising...
Yea, no point in photo mode now that the normal hack works... but this isn't true for everyone else....
Quote from: 1% on June 12, 2013, 02:39:00 AM
Yea, no point in photo mode now that the normal hack works... but this isn't true for everyone else....
the ml team truely are amazing, thanks for all your continuosly awesome work!
What is the current thought on 10bit raw, is it possible, and is there an easy way to calculate how much bitrate it´ll save?
possible if someone finds the setting to force it to 10bit. on the CPU, doubt it.
Quote from: 1% on June 12, 2013, 02:39:00 AM
Yea, no point in photo mode now that the normal hack works... but this isn't true for everyone else....
In video mode what do I select to get the 255mb buffer? NR multishot isn't there...
First go to canon menu and change the image quality to only RAW, no jpeg. The rest is made by memory hack ON in latest builds I believe.
Quote from: exflyer on June 11, 2013, 10:07:49 PM
ML team, thanks again for your work
...
hello there,
I am just curious , it was 1280x720 RAW 24fps or this is an upscaled resolution ?
LE: thanks, great commercial by the way.
Quote from: canonuser78 on June 12, 2013, 09:43:21 AM
hello there,
I am just curious , it was 1280x720 RAW 24fps or this is an upscaled resolution ?
thanks,
1792x624 raw 25 fps rescale to 1280x720
Noob question:
the difference between used height dimensions (upscaled 720px - 625px original =95 px) ,is black area - right ? The image doesen't look stretched .thanks
Quote from: sparedog on June 12, 2013, 02:55:37 AM
the ml team truely are amazing, thanks for all your continuosly awesome work!
What is the current thought on 10bit raw, is it possible, and is there an easy way to calculate how much bitrate it´ll save?
http://www.magiclantern.fm/forum/index.php?topic=6306.0 ;)
The way the devs have described it, it doesn't seem to be possible at the moment. Even with hex level conversion, the area of the cpu that magic lantern has access to simply isn't optimized to deal with that level of data. It's unfortunate because the area of the camera optimized to do h.264 conversion would be able to do it with remarkable ease, but getting access to that by analyzing camera dumps is close to impossible/needs a totally different method from current methods.
Quote from: kgv5 on June 12, 2013, 09:02:04 AM
First go to canon menu and change the image quality to only RAW, no jpeg. The rest is made by memory hack ON in latest builds I believe.
Where's "hack on" located?
Latest build: ML menu>raw video>memory hack>ON
OK had some difficulty [n00b issues] but just updated to latest build and seem to be getting around much easier and got 842 frames of raw to process 1792 x 752
As soon as I get some confidence with shooting settings and post processing I intend to share some video - getting there [i think :)]
Awesome work and kudos to all that make this possible, very exciting stuff
Quote from: nativeridge on June 12, 2013, 10:44:29 PM
OK had some difficulty [n00b issues] but just updated to latest build and seem to be getting around much easier and got 842 frames of raw to process 1792 x 752
As soon as I get some confidence with shooting settings and post processing I intend to share some video - getting there [i think :)]
Awesome work and kudos to all that make this possible, very exciting stuff
842 frames in a whole outing? It wouldn't be possible in one shooting. Its around 300 I believe for that resolution. You'd need a 5d mark ii to get that many frames.
Memory hack should be on by default for digicV. Is it not?
Quote from: 1% on June 13, 2013, 12:01:58 AM
Memory hack should be on by default for digicV. Is it not?
its on at default.
YEP ;D "sweet"
now if i could just get my head around importing into Premier after converting from DNG [sorry off topic]
realise it has already been mentioned, but the time that is given to access settings within sub menu [Q] (believe it is only within sub menu that this occurs) before reverting back to live view does give the feeling that camera is impatient with User and decision making process lol
"Maybe I should just get my shit together quicker :D"
You can use AfterEffects to convert the footage to lossless quicktime .mov. Then import this into Premiere.
Ref: http://tristatefilms.com/magic-lantern-canon-60d-14-bit-raw-video-and-workflow-by-nick-driftwood/
Quote from: nativeridge on June 13, 2013, 02:28:01 AM
now if i could just get my head around importing into Premier after converting from DNG [sorry off topic]
gday mate thankyou for the link - I think the issue I have although proficient at photoshop the shooting for video is very new to me and foreign..
I did follow that guide and at least I could find the import - multiple files and set for alphabetical sorting (I have tried the other processing RAW post by noisy boy but am stumped at understanding why at a standstill]
Only thing was that on starting import camera raw opens then after changing settings same occurs over and over on the same file name ?????
There is probably basic settings that I have overlooked but for the life of me can't get a workflow as yet [ although am getting closer and closer lol]
Think this will be a hurdle for most who just see the works of others but don't have the insight on how to get there - its a whole new ball game unless you are coming from a video/cinema processing background.....
Quote from: nativeridge on June 13, 2013, 02:28:01 AM
now if i could just get my head around importing into Premier after converting from DNG [sorry off topic]
Yup - wrong topic ;)
This might help: http://www.magiclantern.fm/forum/index.php?topic=6021.msg44250#msg44250
8)
Quote from: nativeridge on June 13, 2013, 10:55:43 PM
Only thing was that on starting import camera raw opens then after changing settings same occurs over and over on the same file name ?????
Sounds like you might be selecting all of the dngs in the sequence when importing instead of only the first, which will do this. What program is this in by the way? If in After Effects you should only select the first dng file in the sequence and then make sure the "raw sequence" checkbox is selected at the bottom of the import window. This will then only bring up ACR for the first frame and then when you click done the settings will automatically be applied accross the whole clip.
Any more questions ask over in the 6D raw shooting thread dude :) http://www.magiclantern.fm/forum/index.php?topic=5530.0
Cheers and good luck! 8)
Thankyou SIR ;D ;D ;D ;D ;D
that was it just select first one - wasn't a question :P JUST A HUGE THANK YOU TO ALL!!
Quote from: nativeridge on June 14, 2013, 12:48:34 AM
Thankyou SIR ;D ;D ;D ;D ;D
that was it just select first one - wasn't a question :P JUST A HUGE THANK YOU TO ALL!!
Lol! You're welcome dude! 8)
Ok, you guys have config files for modules meow.
Quote from: 1% on June 14, 2013, 02:36:59 AM
Ok, you guys have config files for modules meow.
In the newest version? Thank the Lord! That saves soon much time thank you so much.
THANK YOU!!
using magic lantern with canon 6D, there's problem transfering files when using Wi-Fi option. is there any updated or revised version for that?
Quote from: ckstoa on June 14, 2013, 05:16:40 AM
THANK YOU!!
using magic lantern with canon 6D, there's problem transfering files when using Wi-Fi option. is there any updated or revised version for that?
Gday.
I'm using version "[113] Check4Regression.zip"
In that version I'm having no issues xferring files with wifi through DSLR Controller on Android, or the computer, or the canon app.
If you really want wifi over whatever improvements have occurred since, you can use that version in the meantime.
New versions wifi monitoring works but I didn't test file transfer.
Bug: (since NR multi available in video mode i think)
Very often, but not always ! in C2m Mode, powering on the camera directly in video mode, when loading modules, camera crashes.
But no ML crash log, and it's probably a Canon crash. Need to pull out the battery.
Quote from: 1% on June 14, 2013, 07:35:57 AM
New versions wifi monitoring works but I didn't test file transfer.
ASSERT: FALSE
at RscMgr.c:2920, task InnerDevelopMgr
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Jun13.6D113
Mercurial changeset : de82482a9951+5fe5e30b455a+ (unified) tip
Built on 2013-06-14 00:19:01 by user@D610.
Free Memory : 445K + 1458K
T.T... WiFi transfer is still not work.. in "[113] ETTRModduleConfigSave.zip" and "[113] Check4Regression.zip"
I'm installed ML references for noisyboy's guide.. ( http://www.magiclantern.fm/forum/index.php?topic=5530.0 )
Is this correct way?
What am I going to do..?
I don't know about that matter well.. help me..
Ok, will investigate. Will have to try some smaller memory usage... canon really doesn't like using shoot_malloc for bvram mirror.
Question is:
Do you want more canon crap working or modules working? Wifi transfer actually the first "usable" feature that gets turned off.
I think memory usage is getting a little excessive though as I had a crash in raw_rec zoom mode today. So no more O3 for modules and maybe O2 for bin.
*if you !need! wifi transfer now just hold set at boot and magic off.* The wifi transfer is to EOS utility or what. I've yet to set this up, have just used the phone app.
Just to send support and gratitude from malual-lens photographers / videographers in my area, we were usng/supporting ML on 550d and now we all got 6Ds and cannot wait for release... Thank you Alex. If I understood there is semi-stable release out there for 6D but I cant seem to find the link ? Any idea how close are you to stable release ?
Will keep supporting 6D progress as this is one amazing camera.
Cheeres guys. sorry for off-topic :)
Well it does seem like a choice between canon and modules. I "sometimes" can get them loaded without using malloc but usually not. I'd like to put an option in the menu but I think menu choices load after bvram is allocated.
Quote from: 1% on June 16, 2013, 02:49:38 AM
*if you !need! wifi transfer now just hold set at boot and magic off.*
OH!! Thanks!! I didn't got that turning off the magic with set button by now cause i'm such a loser.....T.T
problem solved. thx for the help.
Quote from: 1% on June 16, 2013, 02:49:38 AM
Do you want more canon crap working or modules working? Wifi transfer actually the first "usable" feature that gets turned off.
for my vote, switch all canon stuff off, and see how much we gain, then we can turn back on some of the canon stuff if the gain isnt worth it.
we can always boot with ml off when we need those features =D
Whoa whoa.
So ... what "modules" are there available now?
Is it still raw rec + file browser? or are there more now?
And, are you guys proposing disabling canon functionality so that modules can be loaded? like rawrec+filebrowser? Is the canon-killing to actually load the modules? or to only allow the modules to be loaded? Ie, will my loved canon features be dead even with no modules loaded?
If so .. that's crazy man!
I myself, have no interest what so ever in raw rec.
As such, I don't deploy raw rec with ML onto my 6d.
Thus, it would be "unfair" for my camera to then be "crippled" for canon functionality and to require me to switch off ML when I want wifi or whatever other features have been disabled.
Also, boot with MAGIC OFF sometimes is unreliable. It seems that the camera poweroff process sometimes takes a bit longer and if I turn on while it hasn't finalised then I can't activate magic off, etc. Then also, ML appears on power-on from sleep (from sleep timer+shutter button) even though it was magic-offed from power-on (switch). Which is annoying.
On a separate note, is there any manual on how "raw zebras" work? On my, admittedly old version, they look just like normal zebras, so I don't know if they're actually working.
I'm scared to upgrade to a newer ML since there's talk of wifi-whatever not working.
According to this chart, 6D has plenty of free memory, so there's no need to use ugly hacks and disable Canon functionality.
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdFFIcFp1d0R5TzVPTVJXOEVyUndteGc#gid=2
You don't have to use -O3 unless you really like wasting memory.
Quote from: sparedog on June 16, 2013, 01:02:59 PM
for my vote, switch all canon stuff off, and see how much we gain, then we can turn back on some of the canon stuff if the gain isnt worth it.
we can always boot with ml off when we need those features =D
I second this, if we wanted the canon features we can boot without ML.
I went down from O3 already but there isn't enough free memory to load modules and have bvram_mirror in allocate mem. Ideal solution to make everyone happy would be to chose where it loads via config file. But I think config loads after bvram is already initialized.
Its not that it disables the features as much as image processing features, ie transfering files, converting files, etc require a completely empty shoot_malloc for some reason.
3600K - bin - bvram leaves about 1800K... I load modules (raw rec+fileman+boltrec+picview+ettr) and I get a nice fat memory crash. I think the modules still reserve 2x the mem they need, they aren't even optimized anymore. You *can* load maybe raw_rec by itself or something like that.
3600K - bin *no bvram* leaves over 2MB and you can load all modules + dm log and have a good time.
I've used file man and pic view + ettr tons of times.. I've used WFT, raw->jpeg, like 0 times... but everyone is not me. And like someone said above they never even used raw videos.
So I don't want to have to fire off 2 bins per release nor inconvenience people who need these features. Also don't want to have to re-build every time I need a DM log. Need to find a way to make it an option.
What's "bvram" ?
A mirror of the graphics stuff. I think BMP vram.
Quote from: 1% on June 17, 2013, 01:50:40 AM
So I don't want to have to fire off 2 bins per release nor inconvenience people who need these features. Also don't want to have to re-build every time I need a DM log. Need to find a way to make it an option.
Sounds like a pain in the balls to sort out dude so massive thanks if you manage to get it working like that someday. Would def be a nicer way of doing it, not just for yourself and the extra work in making double the builds but also in terms of having to keep swapping cards out for different bins on a shoot. I must admit that even though I want as much performance out of raw_rec as pos, it seems a bit counter productive to do it at the expense of killing ML completely if you want to do anything else with it (if we went
that extreme with the hacks). Lol - I'm probably the only one here that likes the idea of wifi monitoring and raw_rec working together properly :p Call me old fashioned but I actually like to light a scene sometimes and being able to adjust lamps while monitoring from the screen on my ipad/iphone and not going back and forth to the camera would be massively helpful. It works a treat on photoshoots!
What about having like a "master" hack menu item that you can enable/disable and then you can "Q" into that submenu and enable/disable individual hacks that you want but the enabled hacks are all controlled by the master hack parent?
Haven't upgraded my modules for a while so appols if this is already working like this...
(ps. feeling the Supertroopers reference!) 8)
TCC uses 150K and the modules are even smaller. So if you have 1800K free, the problem is somewhere else.
Why do I get a memory.c assert then? I load only a few and its fine.
I made a zip with where canon stuff is working and you can pick and chose what to load... betcha its the huge number of bolt_rec scan lines.
Next will probably go back to canon broken and I'll try to figure out a way to make it a setting somehow.
In what task? You can replace AllocateMemory with your version and keep track of calls, print how much each task allocates, how much is free and so on.
Back then I had memory assert errors because ML was overwriting some Canon data structures, so the movie recording task was trying to allocate 20MB or so with AllocateMemory...
Like this:
ASSERT: FALSE
at ./Memory/Memory.c:187, task module_load_task
lv:1 mode:3
Magic Lantern version : v2.3.NEXT.2013Jun15.6D113
Mercurial changeset : 57cd362ac2f5+ (unified) tip
Built on 2013-06-16 01:40:27 by user@D610.
Free Memory : 445K + 1676K
Yea, its bolt rec, otherwise it loads. No DM/TP logging though.
Bolt_rec is huge (~500K) and should be optimized.
In the bolt_rec for 550D thread I think it was found to use way too many scan lines.
Possible, also MAX_WIDTH seems a bit too big; it seems to be pixels, so 2000 should be enough... unless you have a 6K camera :D
Also I recommend allocating that big matrix dynamically, otherwise TCC will allocate double size.
Still kills debug intercept but I guess that can switch over to shoot_malloc.
Quote from: 1% on June 16, 2013, 02:49:38 AM
Question is:
Do you want more canon crap working or modules working? Wifi transfer actually the first "usable" feature that gets turned off.
As much as I can see the benefit to getting the extra memory available for new ML features, I think one of the most important things about projects like this and CHDK is that they are SUPERSETS of features the cameras come with by default, and they don't require a sacrifice of the cameras' stock features in order to work.
Even in the ML FAQ (http://wiki.magiclantern.fm/faq#does_magic_lantern_completely_replace_canon_firmware) it says:
QuoteDoes Magic Lantern completely replace Canon firmware?
No. Magic Lantern runs from the card, as an add-on over standard firmware. You will still be able to access all Canon functionality.
(emphasis mine)
So I would put in a vote for "keep all stock features working, no matter how pointless they may seem to some users" to keep in line with the "add-on" ideology.
+1.
Also, disabling Canon stuff without fully understanding what's going on, can be dangerous. I've learned it the hard way (completely bricked my 60D, soft-bricked my 5D2 and a tester's 5D3 and so on).
Owie :o
Quote from: a1ex on June 17, 2013, 05:21:04 PM
+1.
Also, disabling Canon stuff without fully understanding what's going on, can be dangerous. I've learned it the hard way (completely bricked my 60D, soft-bricked my 5D2 and a tester's 5D3 and so on).
What does soft bricked mean? Never heard of that lol. Anyways can you guys leave the option available to allocate extra memory with the loss of canon features?
soft brick = something that took only 2 hours to unbrick :P
Quote from: a1ex on June 17, 2013, 06:53:09 PM
soft brick = something that took only 2 hours to unbrick :P
Oh, I thought bricks were permanent...
Bug I think, quite annoying in fact
1. [113] ETTRModduleConfigSave - after shooting raw when I want to record h264 (with encoder settings bit rate off, initQP off, flush rate auto, GOP24, autoload override, config select rate control) sound recording sometimes (quite often) goes completely off (stock audio meters shows zero sound). You have to go to canon menu "sound recording" - it is enabled of course but you have to click it once more - now h264 sound is ok.
2. [113] ETTRModduleConfigSave saves config very nicely but I noticed it doesn't save "start delay" - it's always 2 sec on start, would it be possibe to save 0ff, 2, 4, 10 etc?
3.[6D]DontLoadAllModules - I make everything like with previous builds but almost every time when I turn the cam ON (movie mode) I get err70 right away. Bin is in root, modules in the right folder as usual :-\
What does this build gives? I assume more memory, does it give any increase of raw performance?
Thanks
Gday.
Any updates on the 113 fir?
Ta.
Coutts made one.. it didn't work.
I'll check on H264. It disables audio when flush rate is set to something. Maybe there is a bug with auto. On the latest don't load bolt_rec and you shouldn't get a crash.
I just put bvram into shoot_malloc, I didn't really disable anything. That is what makes those canon features not run.
When flush rate is changed it disables audio.. I'll try to acount for audio but i you flip it around it will disable sound as it applies changes immediately.
Quote from: 1% on June 18, 2013, 03:27:54 PM
On the latest don't load bolt_rec and you shouldn't get a crash.
Yeah, setting bolt_rec to off (via photo mode) solved the start-up err70 issue.
Quote from: 1% on June 18, 2013, 03:27:54 PM
I'll check on H264. It disables audio when flush rate is set to something. Maybe there is a bug with auto.
When flush rate is changed it disables audio.. I'll try to acount for audio but i you flip it around it will disable sound as it applies changes immediately.
Yes I remember, I didn't touch flush rate setting (always on auto), just turn the cam on, audio meters are working, shoot some raw (audio meters obviously are dead during raw recording), than raw off (audio meters dead) , shoot h264 - no sound (audio meters still dead) - so going to canon menu - checking - sound IS MANUAL - back to h264 - sound ok. I am having this every time now ([113] ETTRModduleConfigSave)
EDIT: I have just discovered that entering the canon menu, doesn't matter which tab, activates sound again (audio meters works).
I think beep also undoes sound recording... if you have raw_rec set to beep anyhere it will kill the meters till audio redoes itself.
I shrunk bolt rec, changed over DM/TP so all should be well now, have your cake and eat it too.
DM/TP? these are hacker modules, not for end-users...
DM log can be useful to anyone to diagnose an error tho.
TP log, yea not so much.
TP log is quite dangerous. It hooks directly in the property task and pretty much all other Canon tasks that send messages.
DM log will flood the CPU with processing all those debug messages (of course, if enabled). In LiveView it can't run without disabling a bunch of them, at least here.
They were written for developers to understand how Canon firmware works; they are not designed for the end-users (not even as diagnostic tool).
Runs fine in LV.. but I had taken TP log out a bit ago because of uselessness. Right now everything should be good from now on since I shrunk bolt_rec don a bit and these issues should be gone so everyone has the stuff they want canon or otherwise.
Cool 1%, and thanx. Will that be in the next build?
Yay 1% Yay!
I love cake. Nomnomnom
Quote from: 1% on June 18, 2013, 11:26:04 PM
Runs fine in LV.. but I had taken TP log out a bit ago because of uselessness. Right now everything should be good from now on since I shrunk bolt_rec don a bit and these issues should be gone so everyone has the stuff they want canon or otherwise.
Nice 8)
I'm not sure how in depth this stuff is. But I was looking into Moire on the 6D and I saw this post on the downsampling algorithm that the 6d uses as opposed to the 5d3 and I was wondering if this was something that could be addressed in a magic lantern build or not. Here is the quote I found on it.
"The 5D3 is, when cropped from 3:2 to 16:9, is essentially a QFHD sensor -- exactly 4 times the size of standard 1080p HD. The reason it looks good in 1080p mode is because the camera only has to combine 4 pixels into a single pixel (pixel binning). This is the exact same thing the C300 does to look so good. The 1DX has a smaller sensor that isn't a simple multiple, but it has very powerful processors to downsample in a high quality way. The 6D has a smaller sensor but doesn't have the processing power to downsample correctly (presumably) so Canon just throws out various lines to create the smaller image. It's less processor intensive but results in interference patterns. That's why the 5D3 looks great with moire, the 1DX looks almost as good, and the 6D still has the same problems that the 5D2 had.If it turns out that the processor is strong enough to downsample properly, it could possibly be adjusted in a firmware update that rewrites the downsampling algorithm. Is it likely that Canon will do that? I'm not counting on it."
Just a thought. Thanks for all you guys do.
Quote from: dmg09 on June 19, 2013, 04:42:50 AM
I'm not sure how in depth this stuff is. But I was looking into Moire on the 6D and I saw this post on the downsampling algorithm that the 6d uses as opposed to the 5d3 and I was wondering if this was something that could be addressed in a magic lantern build or not. Here is the quote I found on it.
"The 5D3 is, when cropped from 3:2 to 16:9, is essentially a QFHD sensor -- exactly 4 times the size of standard 1080p HD. The reason it looks good in 1080p mode is because the camera only has to combine 4 pixels into a single pixel (pixel binning). This is the exact same thing the C300 does to look so good. The 1DX has a smaller sensor that isn't a simple multiple, but it has very powerful processors to downsample in a high quality way. The 6D has a smaller sensor but doesn't have the processing power to downsample correctly (presumably) so Canon just throws out various lines to create the smaller image. It's less processor intensive but results in interference patterns. That's why the 5D3 looks great with moire, the 1DX looks almost as good, and the 6D still has the same problems that the 5D2 had.If it turns out that the processor is strong enough to downsample properly, it could possibly be adjusted in a firmware update that rewrites the downsampling algorithm. Is it likely that Canon will do that? I'm not counting on it."
Just a thought. Thanks for all you guys do.
Lol - was just staring at a shot I did with my 6D and weeping at the moire. I do wonder how much of what we are seeing is subject to crazy debayering though. Thanks for the quote though. Where is this from by the way?
Quote from: noisyboy on June 19, 2013, 04:51:24 AM
Lol - was just staring at a shot I did with my 6D and weeping at the moire. I do wonder how much of what we are seeing is subject to crazy debayering though. Thanks for the quote though. Where is this from by the way?
I got the quote from the Canon Rumors forum. I know Mosaic makes an AA filter for it, but it's like $370. Which would be worth it, but if there is a better way to fix it then I would much rather save my money.
Yeah, It's definetely worth it.
I know, that the price makes the price difference between 6D and 5D3 much smaller but right now I cannot change, I have my 6D couple of months now, I was buying it before all the raw stuff appeared so it was very good decision then and selling it now doesn't make sense.
With this filter you can sharpen the picture much more without any color artifacts. I have it couple of days, still lack of time to make a proper comparison but I think it's brilliant.
If you have any request regarding some short test footage (something vs something) just tell and I will make it next week. I can than upload it via dropbox or something because YT compression kills a difference mostly in things we are interested in.
Quote from: kgv5 on June 19, 2013, 06:05:58 AM
Yeah, It's definetely worth it.
I know, that the price makes the price difference between 6D and 5D3 much smaller but right now I cannot change, I have my 6D couple of months now, I was buying it before all the raw stuff appeared so it was very good decision then and selling it now doesn't make sense.
With this filter you can sharpen the picture much more without any color artifacts. I have it couple of days, still lack of time to make a proper comparison but I think it's brilliant.
If you have any request regarding some short test footage (something vs something) just tell and I will make it next week. I can than upload it via dropbox or something because YT compression kills a difference mostly in things we are interested in.
What is the install like on that filter? That was one of my reservations about getting one. I don't want to open up my camera.
Turn the cam off
remove the lens
turn the cam back on
press LV button (mirror goes up)
slide VAF filter in
turn cam off
put the lens back on
that's it.
http://www.youtube.com/watch?v=QYmL53LzURI
Quote from: kgv5 on June 19, 2013, 06:20:11 AM
Turn the cam off
remove the lens
turn the cam back on
press LV button (mirror goes up)
slide VAF filter in
turn cam off
put the lens back on
that's it.
http://www.youtube.com/watch?v=QYmL53LzURI
Awesome! Definitely buying that.
Yea, should be like this from now on.
Quote from: kgv5 on June 19, 2013, 06:20:11 AM
Turn the cam off
remove the lens
turn the cam back on
press LV button (mirror goes up)
slide VAF filter in
turn cam off
put the lens back on
that's it.
http://www.youtube.com/watch?v=QYmL53LzURI
Can't it break the camera if you take pictures with the filter in?
If not do pictures come out alright?
Quote from: xNiNELiVES on June 19, 2013, 07:02:38 AM
Can't it break the camera if you take pictures with the filter in?
If not do pictures come out alright?
I don't think you can take pictures with the filter.
I tried to use the DotTune process last night but it doesn't seem to work, just tells me to "press Info to try again". Am I doing something wrong or is it not working yet?
Quote from: kgv5 on June 19, 2013, 06:05:58 AM
If you have any request regarding some short test footage (something vs something) just tell and I will make it next week. I can than upload it via dropbox or something because YT compression kills a difference mostly in things we are interested in.
DUDE! You are my new bezzie :D I've been hassling Mosaic Engineering for ever about actual providing me with some decent comparison footage so I could buy one of the damn things (they are clearly not that bothered about selling them ha!).
If you could just shoot something you know is gonna be a problem ie. busy water, a bricked wall in the distance, telephone/power cables, trees with LOADS of leaves (far off enough for the moire to be visible) then that would be IMMENSE and I'll love you for ever! ;)
Also, having some footage with no sharpening added and then some with an unsharp mask of say 60% and 1.1 would be cool to compare too :)
Will do :) Give me couple of days and I will post the links to my dropbox.
Quote from: Veggietech on June 19, 2013, 12:05:42 PM
I don't think you can take pictures with the filter.
mirror stays blocked in the upper position but you can take pictures. Unfortunatelly they are blurred because filter was designed to work with line skipped image, not the whole sensor. There is also a problem with sharpening via zoom mode - zoom mode changes line skipping so the filter cannot work properly and in the end zoomed picture is also blurred. You can search for the less blurred focus ring position - it would give you sharp picture when zoomed 1x but it is not comfortable to use. These are drawbacks but you get better picture quality in the end product and this is the most important thing.
oh, one more thing, the filter is changing focus distance, for example in tokina 11-16 infinity without filter is where infinity mark is (when you are turning focus ring). With the filter infinity is much closer (i dont remember exactly but say on 1-1,5 meters mark or so). Its not a big issue, i can live with that.
Quote from: kgv5 on June 20, 2013, 12:04:58 AM
mirror stays blocked in the upper position but you can take pictures. Unfortunatelly they are blurred because filter was designed to work with line skipped image, not the whole sensor.
Ah, okay! Thanks for clarifying.
Quote from: noisyboy on June 19, 2013, 05:38:19 PM
DUDE! You are my new bezzie :D I've been hassling Mosaic Engineering for ever about actual providing me with some decent comparison footage so I could buy one of the damn things (they are clearly not that bothered about selling them ha!).
If you could just shoot something you know is gonna be a problem ie. busy water, a bricked wall in the distance, telephone/power cables, trees with LOADS of leaves (far off enough for the moire to be visible) then that would be IMMENSE and I'll love you for ever! ;)
Also, having some footage with no sharpening added and then some with an unsharp mask of say 60% and 1.1 would be cool to compare too :)
ok, I am going to use the non destructive workflow AE-Pr for my tests but which codec do you guys think I should use for final output (from premiere): h264? what mbps: 40, 60? I would like the footage i will create to be usefull for people interested in buying the filter.
Amazing - thanks bud :)
Are you planning on putting on Vimeo or just sharing a file? Either way a decent bitrate mpeg4 h.264 should surfice.
Thanks again!
Afma was working... haven't tested it recently, don't think anything changed.
Dude is variable buffering implemented in the latest 6D module yet?
Edit: In fact looking at dates I guess not yet :) No worries 8)
It is. and the hack on don't click me. It writes longer at high res.
Ahh - sweet! That'll keep me occupied tomorrow then 8) Cheers man!
Quote from: noisyboy on June 21, 2013, 12:18:21 AM
Amazing - thanks bud :)
Are you planning on putting on Vimeo or just sharing a file? Either way a decent bitrate mpeg4 h.264 should surfice.
Thanks again!
I think sharing is the only way (dropbox or something). I will record short 4-5 sec clips second to reduce size but retain max quality.
I have very busy weekend but I think I will do this till next wenesday.
cheers
I'm looking over some footage I shot last year on the 5D mk2, almost every shot @ iso 1600 is marred by checkerboard noise patterns in the shadows. So, 6D + bitrate override = way better for like 80% of all shots. Get pumped!
Can't wait to see what you get kgv5!
1%, what's behind this "don't click me" function ???
Cause without it, i can record 2.15 min @ 1600x640-24p
And with... 5,35 minutes !
Quote from: teo770 on June 21, 2013, 11:02:38 AM
1%, what's behind this "don't click me" function ???
Cause without it, i can record 2.15 min @ 1600x640-24p
And with... 5,35 minutes !
http://www.magiclantern.fm/forum/index.php?topic=6662.0
8)
Some issues I'm having with ML on the 6D:
- Set button sometimes gets 'disabled' in ML menu (you cannot switch options on/off as it does nothing)
- ML menu randomly quits (back to live view)
- Quick options (which allow you to change kelvin, ISO etc on the fly using directional keys) appear randomly (for example when starting recording)
- Picture style name appears when starting/stopping recording
Is there any way these can be tackled? I know that this build is intended for developers, but it would be handy to have one which is stable enough for day to day use (doesn't need to have raw and modules), especially when my 2nd body (5d2) has ML loaded.
Quote from: Malcolm Debono on June 21, 2013, 01:39:19 PM
Some issues I'm having with ML on the 6D:
Yeah - drawing issues are just things we've (certainly I anyway) have just gotten used to as I think there was a problem with it quitting out every 5 seconds unless you keep moving around the menu that couldn't be resolved (might be wrong on this - maybe I misunderstood). Pain in the arse I know but it's certainly better now than it was. It was something I kept meaning to ask 1% anyway but I know his hands are mad full at the min :)
Would be much nice to use when/if it gets resolved though!
About to take the new hack for a spin! Can't wait :)
The don't click me is the dialog timer hack.
QuoteSet button sometimes gets 'disabled' in ML menu (you cannot switch options on/off as it does nothing)
- ML menu randomly quits (back to live view)
- Quick options (which allow you to change kelvin, ISO etc on the fly using directional keys) appear randomly (for example when starting recording)
- Picture style name appears when starting/stopping recording
Do you have set button remapped to something else, maybe in canon menu... its never done that to me.
ML menu quits when dialog in the background times out.. a1ex did this by design.
Quick options, yeah... sometimes the double click must be triggering at record start. Have to check on this.
I think picture style names appear if you have rec picture style enabled. I'll check what happens without it.
Its this version, not repo version you're using, right?
Quote from: teo770 on June 21, 2013, 11:02:38 AM
1%, what's behind this "don't click me" function ???
Cause without it, i can record 2.15 min @ 1600x640-24p
And with... 5,35 minutes !
I don't know if it's working correctly for me as I still only get about 2:20 when recording at that res and frame rate. That is with Canon Preview, Memory hack on (with Raw in canon menu of course), Framing forced left and I had selected Don't Click Me...
Hard to tell if Don't Click Me has done anything though as nothing happens on screen :)
This is all with "The Hacks" build. A couple other problems I had was when I dragged the contents of the Modules folder in the zip to my SD card and had overwritten the old files, I put it in my camera and it wouldn't start (Err70), so I had to completely delete everything within the modules folder and now it contains
only the files from within the new build and not bolt rec etc...
Is this normal?
And other problem was that I ended up with a problem where whenever I exited the ML menu, I ended up not being able to record and all the drawn stuff had gone although if I pressed the shutter and took a still it would go back to normal again but then if I'd film and then go back in to change settings, the same thing happened again when I exited the menu. I appreciate that this is a shit example of bug reporting so I don't expect anything to happen with this until I see it again (as after a battery pull the problem went away) but just thought I'd post it incase anyone else has the same problem so we know whether or not it's a one off :)
Its bolt rec, new build doesn't have it, you probably had it left over from older builds.
You have to don't click me before you open LV. Then second record should be faster... on CF cameras this is dramatic, sd cameras we were already writing like 38 and now writing 40ish so not a huge jump.
Ah okay cool - I'll have another go thanks.
Just thought I'd mention I added a bit more to my previous post which you may or may not be interested in. If I replicate the problem I'll report back.
Thanks for the info guys. Is this build the latest one? I'll re-download and test it out thoroughly tomorrow as I've got some time off :)
Quote from: 1% on June 21, 2013, 03:03:50 PM
Its bolt rec, new build doesn't have it, you probably had it left over from older builds.
You have to don't click me before you open LV. Then second record should be faster...
Forgive my stupidness but if I'm in movie mode already - live view starts as soon as I power the camera so not sure how I can do that dude? Other than swithing to photo mode first?
Also - what about the other files sorry... should they remain in modules folder from previous?
LOADING.LCK and MAGIC.SYM?
No, delete those.
Yes, start in photo mode and switch to movie mode.
@Malcolm.. yes, latest is up... I still have to try today's changes. Have to go to work :(
I haven't had a lot of time to test everything recently because well.. lots of jobs and 4 cameras. But usually bring 6D with me so when I see something I try to fix it.
Trick that may fix the menu issue: open the file manager and view a picture (a DNG silent pic or a 422 screenshot).
You will lose the LiveView functionality behind the menu, but it will stop the flicker.
Maybe can disable the dialog timer for the dialog opened somehow? Or do they all use that one timer?
Quote from: teo770 on June 21, 2013, 11:02:38 AM
1%, what's behind this "don't click me" function ???
Cause without it, i can record 2.15 min @ 1600x640-24p
And with... 5,35 minutes !
Dude - what settings did you have for getting over 5 mins? I'm shooting global draw off, canon preview, mem hack on, fps overide to 24fps and I switch to photo mode and run don't click before switching back to movie and recording and I still only get 2:15-2:20 whereas you got like double this? Cheers mate :)
No idea how it works, none of my camers has timeout for dialogs...
Canon menu (gui mode 2) should not have any timeout, but you have to close LiveView (annoyance on HDMI) and lose the ability to change settings while previewing the image.
Plus... ML will think you are in photo mode, so the menu stuff will be grayed out in the wrong way.
Quote from: noisyboy on June 21, 2013, 04:03:11 PM
Dude - what settings did you have for getting over 5 mins?
With last update 6D hacks
Start in C2m mode, LV directly in video mode.
Load ONLY raw-rec.mo
Exp ovirride ON
Raw video @1600x640
FPS override 24
Global Draw OFF
Framing CENTER
Preview Canon
Memory hack ON
last result: 5.05 minutes , 40.2 MB/s
i confirm: not only 1 extra second using "force left"
1600x640 with "don't click me" AND Preview "Hacked":
9.08 minutes without frame skip !!! 22GB wao ! 40.6MB/s
Lead me to a LV question...
If you cut LV display (turn it off by soft) when recording... do we get extra MB/S or buffer size ?
If you cut LV off, would external HDMI monitor continue to display something ?
If you want to try that, got an external hdmi monitor.
Perhaps, reactivating LV every.... 15sec ? ;)
Wait so the don't click me function, in addition to the variable buffer modification implemented into the newest version allows even more frames?
definatly !
Quote from: teo770 on June 21, 2013, 08:37:01 PM
definatly !
What are the steps to use this dialogue timer hack? On the steps you said we can't even use other modules. Is this necessary?
Edit: well I just enabled it and got 700 frames. 100 more than without. 1% can you make this set to default. Also I would suggest moving this to the raw menu with a rename to something more friendly.
Quote from: teo770 on June 21, 2013, 06:32:35 PM
Load ONLY raw-rec.mo
Do you mean actually remove the other modules? Not sure how to load individual modules?
Go to modules tab, on every module you can press Q and select "autoload OFF". Than startup your cam again and that's it.
I tried and I don't think it has any influence on frames amount.
Quote from: kgv5 on June 21, 2013, 09:25:05 PM
Go to modules tab, on every module you can press Q and select "autoload OFF". Than startup your cam again and that's it.
Ah - thanks :)
Damn it though! Still getting nothing more than 2:20 with that res... Wonder what else is stopping it?
What card you on teo77?
Quote from: noisyboy on June 21, 2013, 11:53:36 PM
Damn it though! Still getting nothing more than 2:20 with that res... Wonder what else is stopping it?
Card: Sandisk Extreme 45MB/s 128GB
With last update: 6D hacks
Start in C2m mode, LV directly in video mode.
Load ONLY raw-rec.mo
Debug menu -> Don't click me
Exp override ON
Raw video @1600x640
FPS override 24
Global Draw OFF
Framing CENTER
Preview Canon
Memory hack ON
Nothing else
Anybody else finding that the Q menu is completely screwed when using the latest hack? As in I can bringit up but the navigation keys don't want to play. I can press Set and enter the Photo Quality menu (as it's already highlighted) but then can't move left or right to choose other options.
Edit: I think I can actually move around but it's just not displayed graphically on screen. If I move left or right and press set I see the changes when I recall the menu but I'm having to do it blind.
That or I somehow screwed up my build 8)
Also - since the latest build, I'm ending up with some files (raw videos) that windows is recognizing as .rar files. I know they aren't .rar files but wondered if anyone else is experiencing the same and knew what the deal was?
Nice 8)
Edit: Ignore... Answered my own question.
Hoho: Card format tric !
1%, as i already said, got 2 cards Sandisk Extreme PRO (95MB/s) 32GB.
1 formated FAT 32
1 formated ExFAT
I test every update on both and....
FAT32: 2.20 minutes @1600x640-24p till frame drops
ExFAT: 7 minutes @1600x640-24 till frame drops 17GB !!!!!
It's even better than my 128GB Sandisk Extreme (not pro) 45MB/s which can record 5.05 minutes without frame drops
Is it due to a 4GB file splitting issue ? (diff. btw fat32 and exfat recording times)
Can someone confirm the recording time diff btw fat32 and exfat too ?
What cluster size bro? 7min!!!!!
4096K but not important i think
Also - what canon settings you shooting with bro? I've set to NTSC, 1080p, 24fps All-i. Photo quality set to raw for hack.
Quote from: teo770 on June 22, 2013, 12:59:03 AM
4096K but not important i think
K - will try when I figure out what I'm doing that is so stupid :P
No All-i ! IPB
Pictures: RAW
1600x640 with preview: Canon => 7min01 till frame drops !!
1600x640 with Preview: Hacked or Hacked no prev, i have continuous recording no frame drop till card full (32GB) !
1600x672 with preview: Canon => 1min25 till frame drops
1600x672 with preview: Hacked => 1min35 till frame drops => interesting no major gain from Hacked preview
1664x624 with preview: Canon => 3min40 till frame drops
New live optimizing buffer algorithm is very promising !!
1600x640 * 1.2 = 1920x768 .... miam !
If I make the hack default... ISO dialog broken, q menu, broken, etc etc.
It basically makes sure no canon dialogs can work so you gain 10% cpu + a bit of write speed...
I have to build for this and M today... height restriction goes away... the other optimizations didn't really help any on 50D, just tried it.
P.S. R00, r01, etc are all 4gb cuts of the same raw file, concatenate them before developing.
Quote from: 1% on June 22, 2013, 01:24:51 AM
If I make the hack default... ISO dialog broken, q menu, broken, etc etc.
It basically makes sure no canon dialogs can work so you gain 10% cpu + a bit of write speed...
I have to build for this and M today... height restriction goes away... the other optimizations didn't really help any on 50D, just tried it.
P.S. R00, r01, etc are all 4gb cuts of the same raw file, concatenate them before developing.
Could you temporarily use this hack when taking raw video and disable it after? Also could you disable the width restriction? I understand that the 6D can't handle higher resolutions well but might as well allow users to use higher resolutions. I mean it isn't hazardous to our camera's...
Thanks
Can you make it default only when using raw video module ?
And cancel it if we unload raw video module ?
Cause ISO can be setted in ML menu, Q menu.... (personaly useless)
Q menu allows you to modify Picture style, WB, drive .... all things useless when recording RAW video, no ?
Quote from: noisyboy on June 22, 2013, 01:00:43 AM
K - will try when I figure out what I'm doing that is so stupid :P
It does matter. Sometimes you get 30 less frames.
I see that the community is switching for measuring time of footage from frames to (now) minutes and seconds
Quote from: teo770 on June 22, 2013, 01:29:19 AM
Can you make it default only when using raw video module ?
And cancel it if we unload raw video module ?
Cause ISO can be setted in ML menu, Q menu.... (personaly useless)
Q menu allows you to modify Picture style, WB, drive .... all things useless when recording RAW video, no ?
Exactly. Hopefully 1% can implement this.
Woohoo! Figured it out! I think the key here (in idiots terms...) is the first thing you do when you boot the camera is go into ML menu, load modules and then immediately go into debug and click Don't Click Me. Then record when it sends you back to live view. Just to clarify - didn't have to start in photo mode first... video mode is fine :)
Achievement Unlocked 8)
Sandisk Extreme 45MB/s Exfat @ 1600x640 = 06:20 mins :)
Quote from: noisyboy on June 22, 2013, 01:33:47 AM
Woohoo! Figured it out! I think the key here (in idiots terms...) is the first thing you do when you boot the camera is go into ML menu, load modules and then immediately go into debug and click Don't Click Me. Then record when it sends you back to live view. Just to clarify - didn't have to start in photo mode first... video mode is fine :)
Achievement Unlocked 8)
Why would it matter? What made you think that. Lol :P ;D
Hmmm.... Might be wrong here. Tried to re-create all the dicking around I was doing previously before I would press record and it still works okay... I think I disabled a couple things first though and also re-formatted to exfat so will have to see the difference. Could be the files being split in fat32?
Comparing now... Looks more and more like Fat32 is the problem here. Exfat 6min plus. Fat 32 02:20 max everytime! Good find teo77
2.20 minutes => 7 minutes a good 3x ratio.....
But.... would be nice to have more people confirming before champagne !
And.... perhaps an issue for older cams not supporting exFAT....
I know 6D and 5D Mark III does.
Other cams with CF cards can already handle higher write speeds....
A sheet with exFAT compatible cameras is needed !
There's always time for Champagne 8)
Just tried again... Fat32 - 2:15. Formatted back to exfat - still recording as I type but already on 04:25 and still got loads to go by the looks of the buffer indicator :)
Just someone more to confirm now...
Or they will think of us as European fools !
;)
I already got into the champagne... next built will have height restriction off. Its not so easy to have it on/off with recording... well undo would probably work but it really needs to be on before LV opens for max gain.
Actually, we fire "Dont click me" after powering on the cam in VIDEO mode so LV opens immediatly.
Then, we load raw_rec, then we fire "Don't click me"....
You mean, we can have even more starting in PHOTO mode, loading raw rec, then firing Dont click me,
then switching to MOVIE mode ?
Quote from: teo770 on June 22, 2013, 02:03:33 AM
Just someone more to confirm now...
Or they will think of us as European fools !
;)
Haha! I AM a European fool 8)
Me too, that's why i say it !
Now to see how this puppy performs on higher resolutions :)
Wait......
1600x640 with preview: Canon => 8minutes30sec !!! 20.8GB till frame drops
As suggested 1%:
- start the cam in PHOTO mode
- load the raw_rec.mo
- fire "Don't click me"
then switch to MOVIE mode and.... roll on !!! => 8.30 minutes !
2nd try: 8.45 minutes if u stay in PHOTO mode
Noisyboy.... confirm ?
It blocks LV dialogs so any mode before LV... but if its on when LV is open the effect is less.
When I turn it off things should go back to normal but then to run it again should close LV... so right now its OK on don't click me. Maybe should be its own debug option with on/off. I think thats where its headed.. I dunno if stuff from today helped any. So far not really on EOSM.
We would really need something btw
Preview: Canon and Preview: Hacked (freezed)
It s not possible to display only the recorded frame ? (1600x640 for example)
Wouldn't help no ?
Or.... display LV at 5 FPS... ;)
Meanwhile, tried my HDMI external monitor.... It displays exactly the LV display so when freezed -> freezed too.
So i presume if you turn off the LV, will turn black too.
Quote from: teo770 on June 22, 2013, 02:21:32 AM
Noisyboy.... confirm ?
Amazing! I shall have to try tomorrow now dude as I got carried away again and have to be up for a shoot in 5 hours so really do need to sleep or I'll be useless ;)
Speak tomorrow bud! Thanks again for helping me solve that problem though - appreciated!
Ps. +1 vote for on/off dude :) I'd use it tomorrow if it meant I didn't have to re-boot the camera to disable it every time ;) An indicator to let you know whether it's on or off might be a nice addition too maybe?
Is it just me or has this don't click me hack been here before raw video has been around. Why is it now that teo777 or whoever found it to give a lot more frames today. Weird lol.
I get busy on set for 4 days and i come back to this?! Okay, I'll test what I can tomorrow, here in the states, using Teo's set ups.
I'll report back. Unless you all have more options.
(side note, and maybe I'm an idiot, but why would I stay in photomode? and how would that work, just set frame burst to continuous?)
Quote from: electrichobo on June 22, 2013, 04:50:44 AM
I get busy on set for 4 days and i come back to this?! Okay, I'll test what I can tomorrow, here in the states, using Teo's set ups.
I'll report back. Unless you all have more options.
(side note, and maybe I'm an idiot, but why would I stay in photomode? and how would that work, just set frame burst to continuous?)
Video mode works fine. I don't know why you would enable continuous frame bursts. I just turn on the camera like usual and use this new hack and it works fine.
Teo770, could you please try 1792x752 at 23,976fps and tell how many frames you acquired?
Quote from: kgv5 on June 22, 2013, 06:07:06 AM
Teo770, could you please try 1792x752 at 23,976fps and tell how many frames you acquired?
Or a 1792x672. I get on average 675 frames. Once I got 663 once I got 699. Twice I got 673. If I enable hacked mode I get 735 frames or so. Forgot the exact number.
Thanks, but please check also x752 when you will have some time.
Quote from: kgv5 on June 22, 2013, 06:22:50 AM
Thanks, but please check also x752 when you will have some time.
I will in a few...
Ok 414 frames.
1% - I can take video fine with the don't click me setting. After I take the first video nothing shows on the screen and when the record button is pressed video won't record. I've found that by switching from non live view mode and back into live view video mode resets the glitch. Just a bug I've found. Thanks.
Quote from: kgv5 on June 22, 2013, 06:07:06 AM
Teo770, could you please try 1792x752 at 23,976fps and tell how many frames you acquired?
With Sandisk Extreme pro (95MB/s)
1792x752: 405 frames about 10sec without frame drops
1600x672: 2000 frames about 1.25 minutes without frame drops
But guys, recording less than 2 minutes... does it make sens ?
With a good 1600x640, able to handle 8+ minutes recording..... you can make 2 sequences only on a 32GB SD card....
That's not bad and easy upscalable to 1920x768 (x1.2)
For me resolutions causing frame drops before 5 minutes is just not usable.
With multiple 5 minutes sequences (10 sequences on a 64GB), you can really create something !
With 8.30 minutes (my longer sequence without frame drop), we are very close to continuoous recording @1600x640.
OK, not full HD but i m pretty sure in the next few days Alex will optimize his new algorithm and we will gain
more and more recording time/resolution.
http://www.qfpost.com/file/d?g=idJOaYl0E (http://www.qfpost.com/file/d?g=idJOaYl0E)
Added real shutters w/fps override. Made the timer hack undoable.. you still have to get out of LV for it to reset tho.
Quote from: 1% on June 22, 2013, 03:42:05 PM
http://www.qfpost.com/file/d?g=idJOaYl0E (http://www.qfpost.com/file/d?g=idJOaYl0E)
Added real shutters w/fps override. Made the timer hack undoable.. you still have to get out of LV for it to reset tho.
Good thanks. What is the link for though?
Well it was the latest build but QFP seems to have deleted it... maybe it will let me upload again. I saw the box once on bitbucket again.
badzip
It keeps going in and out.. I unno. gonna email bitbucket and ask wtf.
the autoexec.bin is in MODULES now ?
Got Err 80 using that update.
Quote from: 1% on June 22, 2013, 08:58:14 PM
Well it was the latest build but QFP seems to have deleted it... maybe it will let me upload again. I saw the box once on bitbucket again.
http://speedy.sh/hEP2P/6D-ShutterTimer.zip
It keeps going in and out.. I unno. gonna email bitbucket and ask wtf.
Umm why don't you just upload it to the tragic lantern page?
It won't let me upload 75% of the time: I have to email them.
This one worked:
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B6D%5D%20Not%20messed.zip
I think wrong bin got dragged to the wrong spot for that one... I found out at work :(
Better and better... and better !
With update: [6D] Not messed.zip
Sandisk Extreme Pro (95MB/s) formated exFAT - Exp Override ON - Global draw OFF - FPS Override 23.976 - Preview Canon
[email protected]: 9.58 minutes / 24.9GB without frame drop !
[email protected]: 1 minute without frame drop - useless to me
[email protected]: 55 seconds without frame drop - useless to me
[email protected]: 45 seconds without frame drop - useless to me
[email protected]: 42 seconds without frame drop - useless to me
[email protected]: 10.30 minutes / 26.56GB without frame drop ! if you activate
"Dialog Timers: disabled" in ML debug menu..
Quote from: teo770 on June 22, 2013, 08:34:58 AM
But guys, recording less than 2 minutes... does it make sens ?
It depends on what you are shooting.
For me anything above 10sec is usable, 15sec is perfectly usable - especially for music videos with fast cuts. 15 sec is quite long actually when you watch it, I agree, that it could be not usable for interviews unless you have some good idea and planning.
EDIT
One thing which bothers me: you remember the old LVrec module? I know, that it was completely different and obsolete thing. But I liked it because with it you could shoot 1920x800 (It was really 1880x800 according to AE). 1880x800 raw with 1x magnification (unfortunatelly with 255MB hack it was 130frames, 4-5 sec).
To be clear on this: 15sec 1792 with 2,39:1 aspect ratio is awesome for me and I am gonna work comfortably with this but theoretically is this technically possible to have more than 1792 ? With current memory hacks maybe we could get around 10-15 sec 1880x something...
I think i will be part of your family this week, i want to pull the trigger on a 6D but i would love to sell my two cameras and a few other things to feel a bit less guilty.
So, to recap, max speed of the 6D controller is 40ish MB/s, right?
Quote from: ilguercio on June 23, 2013, 11:20:22 AM
I think i will be part of your family this week, i want to pull the trigger on a 6D but i would love to sell my two cameras and a few other things to feel a bit less guilty.
So, to recap, max speed of the 6D controller is 40ish MB/s, right?
Yep, I hope that you not buying 6D only for raw. Me and a bunch of guys from the forum were buying 6D when nobody dreamed about raw. It is an astonishing low light camera, great stills, full frame etc. But unfortunatelly SD drive is limited to 40MB/s and thats why we have to treat a raw recording like a nice addition. If you want long recording you will have 1600x something resolution with upscale factor 120-130% (to fullHD) When you need short clips up to 15 sec then 1792x670 with 107% is fully usable. For my 6D I recently bought VAF-6D filter (i will post some samples in a couple of days) because of the moire and aliasing (only 5d3 doesnt have that issues). If you care about the highest possible picture quality better count 400$ more to the final price. I think 6d is a great multi-purpose machine at good price/quality ratio.
If you care only about raw (in good light conditions) then there are some better (and cheaper) options.
Cheers
SD Cards i tested:
32GB Sandisk Extreme PRO (95MB/s)
128GB Sandisk Extreme (45MB/s)
64GB Lexar 200X (30MB/s)
Waiting for 64GB TOSHIBA EXCERIA Type 2 (60MB/s)
For now, the Sandisk Extreme PRO (95MB/s) gives the best writing speed. But it's limited to 64GB, no 128GB yet.
Anyone got a SD LEXAR PRO 600X (available in 16/32/64/128/256) ?
Hehehe, 6D is a better camera then 50D for everything but raw. Raw 50D is like 1920x1038 pretty much continuous. But 6D can get away with recording on batteries... 50D not so much.
FF also made many of my manual lenses or "FF" designed lenses work better than on APS-C.
And due to APS-C crop factor... cropped raw video are not very wide !
I make my tests with the 20mm f2.8 on the 6D..... and not that wide finaly.
Thinking about buying the 17-40 f4 now....
Advantage: it's parfocal..... Focus point doesn't change while zooming... vertigo effect, here i come !
Would be nice to have DXOMark rank Raw video capabilities of Canon cams....
DR, low light, color depth...
The day it'll happen....
Well I still have to drop the money to have may 11-16 fixed.. I get the feeling it will be a winner at 11mm since now we crop so hard, that vignette will just go away.
On FF the 11mm is like what 8mm? 6mm?
Divide focale by 1.63
11-16 mm in APS-C => 6.75-10 mm in FF
(for APS-C lenses only)
Ok, vignette has gone but welcome distortion !
How bad is the distortion? Seems like it would just be fish-eye effect. At 15MM when I could use it for full size raw it was OK
I shot a load of stuff on a 15mm with raw as it was corpped in and it worked great. just cropped in enough for the distortion not to be too bad in the recording area and also just enough for it to be passable with a bit of lens correction :) I'll see if I can find the footage and show you...
Hey, turns out I was off by 0x4 on the raw type address: we can run the tests again now without interruption.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B6D%5D%20RawtypeTEST.zip
So find the one with 0 noise/weirdness.
22 is what we have by default.. the images are img#-1 = type.
so 05210002.DNG is type 1.
Quote from: 1% on June 24, 2013, 01:52:39 AM
Hey, turns out I was off by 0x4 on the raw type address: we can run the tests again now without interruption.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5B6D%5D%20RawtypeTEST.zip
So find the one with 0 noise/weirdness.
22 is what we have by default.. the images are img#-1 = type.
so 05210002.DNG is type 1.
Excuse me but what are you talking about? This is a ML update so I'm guessing you fixed how the naming system works with Raw Video?
I'm also kind of lost
Quote from: teo770 on June 24, 2013, 02:27:10 AM
I'm also kind of lost
Ok good to know that I'm not alone lol. I was kinda embarrassed. ;D
Understood, with last update, when clicking "don't click me", a bunch of raw tests begin
So it generates DNG files of different type.... (resolution ?) to let us check what is the best moireless type, right ?
Quote from: teo770 on June 24, 2013, 02:43:45 AM
Understood, with last update, when clicking "don't click me", a bunch of raw tests begin
So it generates DNG files of different type.... (resolution ?) to let us check what is the best moireless type, right ?
Is this to find the next highest resolution?
Remember af_raw and the pixel defects? 5D3 had a bin that let you try all of them and then they picked one to use... my cineform conversions all have yellow and purple pixels around sharp edges. they do not on 50D footage.
Quote from: 1% on June 24, 2013, 03:58:11 AM
Remember af_raw and the pixel defects? 5D3 had a bin that let you try all of them and then they picked one to use... my cineform conversions all have yellow and purple pixels around sharp edges. they do not on 50D footage.
Ok so does it save a custom profile on the camera? Or do you want us to send the logs to you, where you'll then analyze the results and choose the best setting?
So we get 100 DNG files.
71 of them are breaked => trash
29 of them seems to have different expo/noise level
The goal is to find which one is the best ?
Less noise ? Best details ?
for myself, it's the #25
Sharpest, lowest noise, bit of vertical banding in blacks
So... we can modify a setting according to this choice ?
Pretty much. Looking to not have any edge damage like this, then I'll add it to the next build.
http://s14.postimg.org/t6vuw7std/M30_1221_proxy_avi_snapshot_00_02_2013_06_02_12.jpg
In which order is it important ?
#1 - the less moiré (i presume)
#2 - the less banding
#3 - the less color noise
#4 - the less b/w noise
Will this pic choice be the same for all 6D cameras ?
Should be the same for all 6Ds.
Remember its n-1 too for type vs image so specify image or rawtype
Probably shouldn't affect morie but will affect #2 + 3, maybe 4.
See what is easiest to correct... these color outlines are hard and ruin cineform workflow. I dunno what the banding will do or how hard it is to get rid of, etc.
Hmmm... 25 was a trashed file for me. 35 and 73 were best/least noisy at my end.
I'll run the test a couple more times tomorrow. Just a bit late now :)
Quote from: 1% on June 24, 2013, 04:50:55 PM
Pretty much. Looking to not have any edge damage like this, then I'll add it to the next build.
http://s14.postimg.org/t6vuw7std/M30_1221_proxy_avi_snapshot_00_02_2013_06_02_12.jpg
Sweet! Didn't realise you were trying to combat this! Thought this was just something we were stuck with :p
Will definitely run a couple more times when I get up and make sure to shoot something that might give use that problem.
Thank you 1% and friends.
I deployed "[6D] RawtypeTEST.zip" on one memory card and found:
- format works
- audio tags work
- wifi works
- file browser works
- raw zebras work in LV but not review (I assume by design)
- in camera raw processing works.
- focus peaking works
Everything I ever wanted works! YAY.
Quote from: 1% on June 23, 2013, 08:35:13 PM
Well I still have to drop the money to have may 11-16 fixed.. I get the feeling it will be a winner at 11mm since now we crop so hard, that vignette will just go away.
On FF the 11mm is like what 8mm? 6mm?
Not to be annoying but, when or are you going to unlock the width to 1880? I don't see the purpose of the child locks.
With update: [6D] RawtypeTEST.zip
Sandisk Extreme Pro (95MB/s) formated exFAT - Exp Override ON - Global draw OFF - FPS Override 23.976 - Preview Canon
Debug: dialog timers disabled
[email protected]: 12.15 minutes / 30.31GB without frame drop ! => Card full (32GB)
[email protected]: 1.24 minute without frame drop
[email protected]: 1.12 minute without frame drop
[email protected]: 3.50 minutes without frame drop
[email protected]: 55 seconds without frame drop
[email protected]: 50 seconds without frame drop
[email protected]: 30 seconds without frame drop
[email protected]: 1.27 minute without frame drop EXTREME !
Quote from: 1% on June 24, 2013, 04:50:55 PM
Pretty much. Looking to not have any edge damage like this, then I'll add it to the next build.
http://s14.postimg.org/t6vuw7std/M30_1221_proxy_avi_snapshot_00_02_2013_06_02_12.jpg
In fact - taking a closer look at that image - I thought you meant the discoloration (which I guess is moire?) but I have never seen the horizontal dots in anything I've shot before...
Quote from: noisyboy on June 25, 2013, 02:56:15 PM
(which I guess is moire?) but I have never seen the horizontal dots in anything I've shot before...
This is a kind of moiré/artefact affecting edges.
"Real moiré", you can't miss it, just shoot something with a lot of vert/horz. lines.... you will find it easily...
You will also easily see aliasing...
Here, my favorite target is my slate roof.... I always know where to find some moiré & aliasing ....
In the 100 dng files.... quasi no difference concerning "real moiré"... :(
Quote from: teo770 on June 25, 2013, 03:57:37 PM
This is a kind of moiré/artefact affecting edges.
"Real moiré", you can't miss it, just shoot something with a lot of vert/horz. lines.... you will find it easily...
You will also easily see aliasing...
Oh yeah I know :) I just never saw the dots before. Is it actually a problem on the 6D?
I think while RAW video doesn't path thru Canon optimisations... it's part of raw data.
Testing those 100 dngs, i presume it's in fact testing diferent timer options to find
the best producing the less artefacts, no ? (1% ?)
Getting raw data, you also get sensor/electronic weirdness like color shift, artefacts....
Once you know them, some can be fixed while recording file in cam or while converting DNG
with raw2dng.
Its testing different raw types like 5d3 to try to get rid of any dots like that, banding, etc.
Quote from: 1% on June 25, 2013, 07:09:50 PM
Its testing different raw types like 5d3 to try to get rid of any dots like that, banding, etc.
I'll be honest dude - I haven't noticed any banding or dots. That all disappeared for me a while back.
Just ran the tests and the only differences I noticed were exposure changes and differences in noise that are so negligible that I can barely tell which is better :P
I shall continue to try the tests in different environments though.
In other news!!
I think I just made some kind of breakthrough! I shot some rooftops etc to try and replicate to the orange/blue color moire artefacts to see if any DNG's from the test would yield less moire than others and sadly there was no real difference between them...
However! I just played around a bit more with the settings inside of lightroom and found that choosing 2003 Camera Calibration Process pretty much gets rid of it all together!
If anyone else could try this out in ACR or Lightroom then let me know it would help me work out if this really does help or I just got lucky on one shot :P
Cheers! 8)
Damn... Tried on some other footage and didn't work :'(
Is this test definitely working correctly? If 25 was the best for teo770, that frame for me was completely unusable (scrambled image).
Okay - so fully aware that I'm talking to myself now but anyway :P
Choosing 2003 process does actually make a difference. Doesn't get rid of it entirely in the second lot of footage I tested on but definitely reduced it quite a bit. One thing I'm wondering though... when I tested this on the DNG's generated by the Don't Click Me test (which of course haven't been wrapped up into a .raw file), I get more options in ACR and Lightroom for camera calibration (difference profiles etc) which I don't get from DNG's extracted with Rawanizer. This makes me wonder if Rawanizer/Raw2DNG etc are playing a part in the artifacts?
Personaly, banding is present in shadow areas. Make the test in a room with low ligh, you ll find it.
Edit: .... perhaps the best banding test is "cap on" :)
Quote from: teo770 on June 25, 2013, 08:48:13 PM
Personaly, banding is present in shadow areas. Make the test in a room with low ligh, you ll find it.
Edit: .... perhaps the best banding test is "cap on" :)
Cool - will have a go :)
Continued testing shows that selecting the 2003 process does go a long way to removing the orange/blue artifacts.
This is a crop in of something I shot a while back
http://ge.tt/5etrxFk
Notice around the railings that there is the orange/blue madness.
Now look at the same image with 2003 selected:
Gone!
The only thing I notice is that it seems to like to stay around anything that is green which is weird but rooftops, brick walls etc it pretty much gets rid of it!
EDIT: Whoops! I mean 2012 not 2013 :p
Interesting so let's start googling what adobe changed btw process 2012 and 2013 !
Quote from: teo770 on June 25, 2013, 11:05:29 PM
Interesting so let's start googling what adobe changed btw process 2012 and 2013 !
Yeah! 2003 is the one that seemed to help things ;)
Was it 25 or type 25?
type 25 is image 26
img 25 is type 24
The test i made: the best noise & banding test i think
Cap on the lens, 1600 iso, f4 (full open)
In Lightroom +4 clicks on expo.
The best are imgs:
- 25 and 27 exactly the same pictures
- 36 and 38 exactly the same pictures
- 57 and 58 exactly the same pictures. Perhaps an issue here. Pictures even with +10 clicks on expo are full black... as if the pic wasn't take.
I would choose img #25. Banding and color noise is in every pictures but imo, the #25 img shows less banding and color noise.
Others are breaked or show way too much color noise.
Quote from: noisyboy on June 26, 2013, 12:25:08 AM
Yeah! 2003 is the one that seemed to help things ;)
Noisyboy, take a pic @ 1600 iso with cap on, then push expo to +4 clicks in LR.
You can compare image switching processus 2012 and 2003....
For me a LOT of color noise added by processus 2003.
It's a lab test... perhaps acting differently with real life pics so... deep test it.
was using EOSM address.. but 24/25 freezing LV
I dunno if there is a difference between AF On/AF off... I took another shot at AF off and didn't see dots but maybe it was not bright enough.
Ok... this might be more "fun" than the images.
Go to debug -> memory browser. Select 7e024.. turn on raw video, then you can try out raw type on the fly.
int32 type 16 is what 5d3 uses, default is hex 22 which is int 34 to keep it consistent.
check out raw zebra on int 23, which is close to the non working img25... also 28 is one up from img27.. they both seem to "clean out" the shadows.
Speaking of noise! this looks very cool:
http://www.magiclantern.fm/forum/index.php?topic=5479.msg53821#msg53821
Ps. I will run these tests, just wont get my camera back for another half hour or so :p
Thats how I've been finding the dots... but the problem is the silent DNG doesn't seem to match what happens w/ raw video. The img25 type froze LV. I think better to test by just setting it.
The 2003 process also removes color shifting. In 2013 process adobe added in automatic settings that you don't even get to control. They apparently automatically add sharpness etc. There, I believe, are ways to remove these changes. Dunno how though. Just google...
Here you have the raw DNG's for comparing the picture with and without VAF-6D.
http://www.magiclantern.fm/forum/index.php?topic=6577.msg55134;topicseen#msg55134
Quote from: 1% on June 26, 2013, 03:49:16 AM
Go to debug -> memory browser. Select 7e024.. turn on raw video, then you can try out raw type on the fly.
int32 type 16 is what 5d3 uses, default is hex 22 which is int 34 to keep it consistent.
check out raw zebra on int 23, which is close to the non working img25... also 28 is one up from img27.. they both seem to "clean out" the shadows.
Humm, only thing i can change in memory browser is select "5024" for Hexdump
Change that address with the arrow keys, right below it is the position you're on.
OK, same test with HEXDump @ 5028
The test i made: noise & banding test
Cap on the lens, 1600 iso, f4 (full open)
In Lightroom +4 clicks on expo.
The best are imgs:
- 18 and 25
- 57 and 58, as you think, histograme is empty, so breaked pic.
It's hard to say again btw img #18 and #25. Noise and banding are there in both... but very close.
5028 is the address hexdump goes to by default, its not raw type.
7e024 is raw type, you have to set hexdump to go there, its a memory browser, it'll change right away.
Sorry, definatly out of my understanding...
The HexDump is 6 digits
Quote from: 1% on June 26, 2013, 09:23:40 PM
7e024 is raw type, you have to set hexdump to go there, its a memory browser, it'll change right away.
Where must i set the raw type 7e024 ?
Once i reach the Raw type mem address, what do i have to modify ?
Top line, move the scroll wheel.
second line move left to right and then go back up to change the numbers
that is where you're at, then contents is below
default raw type is 22 so
I love comics ! Books with pics !!
Thanks !
As an ideal i shall test from rawtype 20 to 30 ?
And with the "best raw type", in the 100 dngs i would get...
Overall less noise/banding ? Less breaked pics ?
You can go from 0-100 (higher, probably won't work), the int32 would be pic number you got in raw - 1
You can change by int or hex... looking for no "hot" pixels/banding and no yellow + purple artifacts around sharp edges. I guess you can take a silent pic or shoot a few frames.
God, lots of combinations !
Just get the best result with rawtype hex32 = 1e
Quasi get rid of banding in every non breaked pic.
What's behind "rawtype" ?
Some canon function to chose edge outlining and to apply correction or not.
Tried 1E on some silent pics, no issues.. have look at video + try sharper edges.
Seems that this is possible to use 6D and EOS app remote shooting with raw. It's getting about 15fps but at least we can see the picture while it is recording which can be very helpful with crane or slider for example without any cables. EOS app has only shutter release, doesn't have LV on/off button. Could we somehow emulate this or just make full shutter release button press to start raw recording (as an option)? (stopping is not so necessary whilst recording in hi res gives only short time recording so it will stop automagically :) Other thing is when touching the screen we can choose the spot to focus on - so eos app is sending some othe signal to the cam - maybe we could somehow trigger ETTR this way?
Tested rawtypes 0 to 9 this morning...... very long.
A script firing "Don't click me", changing RawType +1, firing "Don't click me" ... etc would be nice.
5 scripts to test let's say 0-20, 21-40, 41-60, 61-80, 81-100
20 series x 100 dngs x 4MB = 8GB
Then another script to analyse results.... mesuring noise (counting non black pixels ?)
Moiré, banding... harder to mesure softly...
:)
Yea, could have done it a little easier and just changed type on don't click me. Going to give 1E a try and see if the yellow stuff is gone.
Checked 1e in video, has dead pixels marked on the frame.
Real sorry I haven't been able to assist with this yet :( Loaned my camera for the day and still trying to get it back! What are friends for if not to be a complete pain in the ass eh?! 8)
In fact - while I'm here - do you know how we get the camera name correctly written into the metadata of the DNG's 1%? I guess this is supposed to happen when they are extracted - not recorded but I don't know how I approach asking about it? Is is something that needs to be changed with raw2dng? Or Rawanizer? I know mkII users are having no problems so I guess our camera just needs adding does it?
I have to look at a bunch of stuff so I'll see. Its supposed to be writing the data already... I thought EOSM was the only one... is it showing up on DNG and not on video?
Sorry man - not showing in DNG's. If you put into lightroom or ACR it shows as Canikon under the models which means you can't select the different camera calibrations.
Looked at the silent pics... its supposed to be using the camera name as camera model for photos when built inside ML.
I looked at EOSM and it had "Canon EOSM" string in the silent DNGs... for raw2dng I'm not sure that it can put the camera string in DNG header.. but its supposed to be in the raw header. I'll look at it again but the corrections from software may not be accuarate for the ML raw.
* Says canon EOS 6D and magic lantern in silent DNG... also magic lantern.
Here is a new one, bit bucket not letting me upload again:
[6D] NewRecOpt.zip
https://mega.co.nz/#!wxxQ1TgS!UuP2tVxSS99zr0M-nXPSp3Cc8R1F3SwgVndA5dlyrJs
Quote from: 1% on June 27, 2013, 05:47:42 PM
Looked at the silent pics... its supposed to be using the camera name as camera model for photos when built inside ML.
I looked at EOSM and it had "Canon EOSM" string in the silent DNGs... for raw2dng I'm not sure that it can put the camera string in DNG header.. but its supposed to be in the raw header. I'll look at it again but the corrections from software may not be accuarate for the ML raw.
* Says canon EOS 6D and magic lantern in silent DNG... also magic lantern.
Here is a new one, bit bucket not letting me upload again:
[6D] NewRecOpt.zip
https://mega.co.nz/#!wxxQ1TgS!UuP2tVxSS99zr0M-nXPSp3Cc8R1F3SwgVndA5dlyrJs
Sorry dude - I'm having a dumb day... so do you mean the exif data is supposed to be there?
What tasty goodness is to be found in the new build dude? Gonna hopefully use my camera a lot tomorrow so wondering if it's worth putting on all my cards?
[6D]NewRecOpt - I get higher write speed - 40,2-40,7 MB/s, sometimes it dropps to 39,7ish.
1808x756 - usually ~370 frames, sometimes getting 392! it is ~ 2sec (30-40 frames) more than previous build but frame numbers are not consistent and varies every time +/- 20. But it's definetelly another step up :) 15sec vs 17sec :)
EDIT: I am getting 392 frames quite often really, with hack on -400 frames.
Quote from: kgv5 on June 27, 2013, 11:23:10 PM
[6D]NewRecOpt - I get higher write speed - 40,2-40,7 MB/s, sometimes it dropps to 39,7ish.
1808x756 - usually ~370 frames, sometimes getting 392! it is ~ 2sec (30-40 frames) more than previous build but frame numbers are not consistent and varies every time +/- 20. But it's definetelly another step up :) 15sec vs 17sec :)
EDIT: I am getting 392 frames quite often really, with hack on -400 frames.
That's really promising! Just pulled the trigger on ordering the 6D so am anxious to help on the testing side. ;D
So I have been trying to record at 50fps 720p. Why is there a 1.6 stretch needed, could we not just record 720*1280 at 50fps for shorter periods? thanks
Play it back, its squished.
That´s on drugs =D Is there not a way to record unsquished?
I think the best you can do to have unstretched image is to record 1280x720 cropped from 1920 and fps override set to 35fps. You will get 68,5% slowmo.
Thanks, I shall test it
[edit] Ignore below, I was using a version of raw2cdng from the 1980s =D all fixed
Has anyone managed to open 6d raw video in davinci resolve? Mine come out weird, losing all contrast and completely blown highlights.
just got a 6d is there a Public ML download or is it still in prestage's ? ive got ml on my 650d
cheers.
Read the other thread with the guide, it has been public forever just not promoted.
Teo777 where did you obtain "[6D]NewRecOpt"?
edit- Jesus, I just scoured the thread a bit and found it. My bad, sorry...
Some bugs:
-There are two frame skipping entries.
-When under 1808 horizontal resolution the bottom note says its at 1856 or something of this sort and that it isn't possible.
1%- Bolt.rec and LV.rec are outdated in the current version. They expect higher versions, are they dead because of new advancements that broke the modules? Or am I just outdated. If so where do I obtain the new versions. Thanks.
------------------
1808x682 (GD OFF, Don't Click me, Mem Hack On, 23.976p with Override) Sandisk Extreme Pro 32gb - 626 frames. Looking good!
They are dead, new buffer system. Hahah fuck you're right tho, frame skipping is doubled, will fix that.
Quote-When under 1808 horizontal resolution the bottom note says its at 1856 or something of this sort and that it isn't possible.
This is normal... if you have 1920 selected it will say 1920 is not possible can only do 1808, etc.
Quote from: 1% on June 28, 2013, 08:54:16 PM
They are dead, new buffer system. Hahah fuck you're right tho, frame skipping is doubled, will fix that.
This is normal... if you have 1920 selected it will say 1920 is not possible can only do 1808, etc.
I know about that its just the point that it says it can't do 1856 not 1808. Minor inconsistency error thats all, or is it just me?
1856 is the size before 1920
raw_rec.mo
https://mega.co.nz/#!o5wWiZiA!eZLJEF4EesP6OuxIyM3hJHVllKMEIaN67jbGoJoegKY
Quote from: 1% on June 28, 2013, 09:17:39 PM
1856 is the size before 1920
raw_rec.mo
https://mega.co.nz/#!o5wWiZiA!eZLJEF4EesP6OuxIyM3hJHVllKMEIaN67jbGoJoegKY
Yes but, its 1808 not 1856. On the bottom note saying it can't do the resolution it should state that at 1808x[X] it can't record continuous. Not that at 1856x[X] it can't record continuous.
Whats with the Raw_rec.mo
fixed that doubled frame skip.
Quote from: 1% on June 28, 2013, 09:33:01 PM
fixed that doubled frame skip.
Oh, got you. Why did you increase the max horizontal resolution to 1808 from 1792?
I took out limits for height so it goes back to full size. It was already writing with 4096 alignment anyway so restriction just gave you a few more heights thats it, at expense of width.
Shoot a silent pic to get full size of raw buffer.
Quote from: 1% on June 28, 2013, 09:38:40 PM
I took out limits for height so it goes back to full size. It was already writing with 4096 alignment anyway so restriction just gave you a few more heights thats it, at expense of width.
Shoot a silent pic to get full size of raw buffer.
Ok. Thanks for the explanation.
Where do you enable silent pics? Aren't silent pics just pictures taken without the mirror flapping. Basically one frame of video?
Its 1 frame of raw, in the shoot menu. Used to be shots of 422
Quote from: 1% on June 28, 2013, 10:00:00 PM
Its 1 frame of raw, in the shoot menu. Used to be shots of 422
Can you create a timelapse feature in the silent picture section. Using fps override with raw video doesn't allow us to:
1) Can't shoot full res.
2) Only allows 1/48 shutter, not long shutter speeds for night time lapses.
3) Have an easy way of delaying shots. There should be a delay setting just like the time-lapse feature already implemented into ML.
Maybe you could just insert the silent pic timelapse option in the timelapse section.
-------------------
I've noticed you've fixed the issue when the last picture in an image sequence was pink/artifacty. Nice job.
One last question: What does the new extra hacks option do?
You can time lapse with the silent pics using intervalometer. Also you can do fps override with the problems you said... same problems as H264.
Quote from: 1% on June 28, 2013, 10:07:22 PM
You can time lapse with the silent pics using intervalometer. Also you can do fps override with the problems you said... same problems as H264.
Ok. Oh well then :-\
----------------
Getting a bit of color artifacting on my carpet in my room. Just letting you know. Would you like to see the dngs?
Plain old intervalometer with silent pic takes care of 1+2+3 tho.
Quote from: 1% on June 28, 2013, 11:33:15 PM
Plain old intervalometer with silent pic takes care of 1+2+3 tho.
Ok I used the silent pics option. I couldn't find a way to set the picture quality/resolution. It says the picture format is a 14 bit dng. This is fine but it only shoots 1808x11-something. Where do I find the options to modify this? Also is there a way to take pictures by pushing down the shutter button all the way? Not a half click.
Turn on intervalometer + silent pic it takes a full sized pic by itself. In zoom they will be whatever zoom is, 2k, 3k? * 10XX res. That is as tall as we go I think.
Quote from: 1% on June 29, 2013, 01:29:30 AM
Turn on intervalometer + silent pic it takes a full sized pic by itself. In zoom they will be whatever zoom is, 2k, 3k? * 10XX res. That is as tall as we go I think.
So I can't choose any other format. I can't shoot even 1080p at 1x, and the only way I can shoot anywhere higher resolutions I have to shoot in 3x mode.
Before this it was silent pics which were way smaller. If you turn on the raw module it may clip the silent DNGs to whatever size you pick but dunno if it works with intervalometer. Otherwise shoot H264/RAW/Photos. Same for every other camera.
Quest for speed, act II:
This morning, i received 2 new SD cards and i can now recommand the BEST SD card for the 6D (in my case).
I tested every card formated exFat in a USB3 card reader with ATTO software.
Lots of benchs but one very important: 2048MB file read/write (numbers are the same with 4096MB files)
SANDISK Extreme PRO 32GB (95MB/s) => Read: 89.677MB/s Write: 76.983MB/s
SANDISK Extreme 128GB (45MB/s) => Read: 49.765MB/s Write: 42.881MB/s
LEXAR Professional 64GB (600X) => Read: 85.488MB/s Write: 26.951MB/s
LEXAR 64GB (200X) = > Read: 45.420MB/s Write: 34.195MB/s
TOSHIBA EXCERIA Type2 64GB (95/60MB/s) => Read: 88.690MB/s Write: 64.839MB/s
The Sandisk Extreme PRO is just the best, as i expected but is, for now, limited to 64GB and cost a leg ! The extreme version costs lots less but... we could be limited speaking of RAW video recording... one day.
The LEXAR PRO is.... very disapointing in term of writing speed...
This TOSHIBA card is very promizing and in my opinion gets the best price/performance !!
With a write speed of 64+MB/s, we could get a lot of room to let ML grab some more MB/s !!!
Next episode: all those cards recording Raw... how long can they record... ??
Edit: Damned ! In camera, the Toshiba doesn't handle high writing speed as good as the Sandisk Extreme PRO....
At the end, it's a good 64GB card but.... not enough for raw video ! On the distance, the Sandisk Extreme PRO seems to handle better raw video by allowing about 10% more recording time.
For now, we are stucked with Sandisk !
Quote from: teo770 on June 29, 2013, 02:54:56 PM
Quest for speed, act II:
This morning, i received 2 new SD cards and i can now recommand the BEST SD card for the 6D (in my case).
I tested every card formated exFat in a USB3 card reader with ATTO software.
Lots of benchs but one very important: 2048MB file read/write (numbers are the same with 4096MB files)
SANDISK Extreme PRO 32GB (95MB/s) => Read: 89.677MB/s Write: 76.983MB/s
What kind of results did you get in camera? I picked up an Extreme pro 32 a few weeks back to be my go to RAW card so I'm glad to hear you are finding it was the right purchase. Now just crossing my fingers for the price on the 64gb to drop. I am hopeful that the variable buffering in conjunction with the 6Ds highspeed buffer and the Sandisk pro we might start seeing some 1080 records around 12-20 seconds.
Quote from: teo770 on June 29, 2013, 02:54:56 PM
On the distance, the Sandisk Extreme PRO seems to handle better raw video by allowing about 10% more recording time.
So what maximum write speed did you get? I have sandisk extreme 45mb/s, with the newest build and 1808x756 res I am getting 40,2-40,7. Did you get more than that with Sandisk 95?
Also with display timers off completely before LV. Any difference between pro and 45MB/s in camera after a few records like this? GD off @ rec, etc.
Theoretical on the sandisk in a PC is 42MB from that.. the pro doesn't have this limit.
32GB Sandisk Extreme PRO (95MB/s): video mode, all hacks activated except preview Canon, disp timers disabled before LV
1600x670 40.1MB/s: 1m20, 1930 frames till drops
1600x680 40.4MB/s: 1m12, 1500 frames till drops
1664x666 40.4MB/s: 1m01, 1400 frames till drops
1792x750 40.4MB/s: 15s, 400 frames till drops
1808x756 40.5MB/s: 15s, 400 frames till drops
1808x770 40.3MB/s: 14s, 280 frames till drops
Make me wonder.... with the ultimate card (this Sandisk 95MB/s), it always displays 40.xMB/s in every resolution....
How is calculated this speed ? It is writing speed to the card (out of buffers) or the speed used to feed the buffers ?
Re-tested the Toshiba EXCERIA with ML benchmark, it seems non stable concerning writing speed...
I don't have those jumps from... 22.5MB/s to 40.7MB/s while testing the card with ATTO on PC... only happends in the cam....
I'm testing with files of 2048MB and 4096MB.... same result. Strange.
There's also another thing: Toshiba Exceria, Lexar Pro 600x, lexar 200X .... are all SDXC cards... The sandisk extreme pro is SDHC...
Still this PC50 PC104 thing....
It calculates what is going to the card from the buffers.
Does it get any better with LV hacked out?
On the sandisk 45MB/s the fastest I've seen is 41MB
Quote from: DerekDock on June 29, 2013, 06:34:02 PM
What kind of results did you get in camera? I picked up an Extreme pro 32 a few weeks back to be my go to RAW card so I'm glad to hear you are finding it was the right purchase. Now just crossing my fingers for the price on the 64gb to drop. I am hopeful that the variable buffering in conjunction with the 6Ds highspeed buffer and the Sandisk pro we might start seeing some 1080 records around 12-20 seconds.
Yeah I already can except you have to be in 3x mode. I don't understand why though, the cameras processor is just as powerful as the 5D3s...
Well 12-20 seconds of 1920x720.
Quote from: 1% on June 29, 2013, 09:14:12 PM
It calculates what is going to the card from the buffers.
Does it get any better with LV hacked out?
On the sandisk 45MB/s the fastest I've seen is 41MB
After using my extreme pro the fastest I've seen is 40.7. I haven't taken any benchmarks via the debug page, so I don't know if it can go any higher.
Normal writing, not benchmark.
Quote from: 1% on June 29, 2013, 10:26:49 PM
Normal writing, not benchmark.
Ok. That 40.7 mb/s was from canon framing mode btw...
Yeah my card fluxuates a bit. Right now it's getting 40.5mb/s even with hacked2.
Hi, anyone tried samsung's pro seris sdhc card yet?
I just bought one of these: http://www.samsung.com/us/computer/memory-storage/MB-SGBGB/AM (http://www.samsung.com/us/computer/memory-storage/MB-SGBGB/AM)
Quote from: csoller on June 30, 2013, 03:01:55 PM
Hi, anyone tried samsung's pro seris sdhc card yet?
I just bought one of these: http://www.samsung.com/us/computer/memory-storage/MB-SGBGB/AM (http://www.samsung.com/us/computer/memory-storage/MB-SGBGB/AM)
Yeah I believe it was tested a while back by a member here. From what I remember
it performs the same as the SanDisk extreme. All of these cards do, unless of course we remove the bottlenecked hardware in the camera to remove the 41mb/s limit.
I have a samsung 40MB/s.. it only does 29-30. Don't hold your breath on their pro cards. It is well built tho, unlike other faster cards.
Quote from: 1% on June 30, 2013, 05:46:34 PM
I have a samsung 40MB/s.. it only does 29-30. Don't hold your breath on their pro cards. It is well built tho, unlike other faster cards.
Wow that's pretty bad. I don't know why everyone keeps searching for a better card. The SanDisk extreme pro blows anything out of the water. The only way any card could give it a run for it's money is buy purchasing a card with similar specs. Not one that had a 30mb/s lower specified write.
Quote from: xNiNELiVES on June 30, 2013, 07:09:09 PM
Wow that's pretty bad. I don't know why everyone keeps searching for a better card. The SanDisk extreme pro blows anything out of the water. The only way any card could give it a run for it's money is buy purchasing a card with similar specs. Not one that had a 30mb/s lower specified write.
The problem is that when used on the 6D the SanDisk extreme pro does not blow anything out of the water, it doesn't preform noticeably better than any other card. nothing is doing better than around 40MB
now, there may be some advantage in that if you pull the card out of your camera it takes less time to read things from the card on your computer.
But for purposes of capturing raw video it's not any better than other cards.
Quote from: dlang on July 01, 2013, 12:31:58 AM
The problem is that when used on the 6D the SanDisk extreme pro does not blow anything out of the water, it doesn't preform noticeably better than any other card. nothing is doing better than around 40MB
now, there may be some advantage in that if you pull the card out of your camera it takes less time to read things from the card on your computer.
But for purposes of capturing raw video it's not any better than other cards.
Yeah, I know... My point was that the SanDisk extreme pro kills anything so nothing can perform better in camera. A community favorite to max out the cameras right speed is the extreme series card.
Quote from: dlang on July 01, 2013, 12:31:58 AM
The problem is that when used on the 6D the SanDisk extreme pro does not blow anything out of the water, it doesn't preform noticeably better than any other card. nothing is doing better than around 40MB
now, there may be some advantage in that if you pull the card out of your camera it takes less time to read things from the card on your computer.
But for purposes of capturing raw video it's not any better than other cards.
I've found the Pro much more reliable when it comes to corrupt frames and such. So maybe it's the extra speed of the card that is helping the buffer refresh?
The pro is better for sure but the price of the pro vs several sandisk 45MB/s cards doesn't work.
Long time since I've had anything but the stupid edge colors, also on slower cards didn't have any issue either.
Are there any more nightly builds other then 'NewRecOpt'? I down loaded it from this discussion group but I have not found anything after that. I read somewhere that this is a problem with the general download site.
Thanks
Gooday. I have a maybe-bug.
When reviewing photos and pressing the backlight button to get the focus peaking and histogram there is inconsistent behaviour between rear wheel dial and right/left cursor.
If, while the focus peak/histogram is displayed in image review, rotating the scroll wheel results in the peak/histogram vanishing and the previous/next image appearing. If I use the cursor keys then the display gets all jumbled with it trying to do peaking/histogram on the peaking/histogram.
I have tested this in particular with the "raw" focus peaking method. Where the image is b/w and the focused bits are white dots.
Also, although I love the raw mode cos it's easy to tell what's in focus, it gets annoying having to press the play-button-twice to exist image review mode and go back in so that the normal image is displayed. It would be most preferable to have the light-button to enable the peak/histogram mode and then upon another keypress to have it disable the mode. Currently, pressing the light-button over and over again seems to accumulate the histogram/peak results.
I also have a question about the raw histogram. It seems to only be present in LV and not when reviewing, even though a raw pic was taken. (Large Raw and S Jpeg).
Also, the blue and red zebras are underexpose and over expose right? Are these under/over in terms of the raw file or the jpeg?
Thanks for your fantastic work. I really love the 'raw' focus peaks. It's like having a RGBD cam
FYI: I'm running version [6D] RawtypeTEST.zip
QuoteCurrently, pressing the light-button over and over again seems to accumulate the histogram/peak results.
The arrow keys move raw spot meter around this is why it acts different. I know it keeps redrawing, I need to find a fix for that.
Raw data is only present in QR mode right after you take the picture, sucks I kno.
There is some new stuff so I can update today. ShotAsNeutral got updated in raw parameters and I let the volume controls work with tape recorder if separate wav is set.
Is it correct if I see only 4 buffers lines while recording RAW? I think there were about 6 of them in previuos versions, no?
In this way it only can do 1808x770 40.1MB/s: 197 frames with SanDisk 32 Ext.Pro
Memory hack is on and quality is raw?
I've got a Canon 7d and I'd like to buy a 6d and using ML. I'd like to know if this version is total functionally. Does it has all functions I use on my Canon 7d with Alpha 2? Thanks a lot.
No headphone monitoring.... but that is pretty much it. Then again I don't know what you're using on 7D.
Quote from: 1% on July 02, 2013, 11:08:34 PM
Memory hack is on and quality is raw?
FPS override 24
RAW on
Resolution 1808 x 770 2.35:1
Global Draw Off
Preview Canon
Memory Hack On
Used this one - [6D] RawtypeTEST.zip
Maybe I have to do a clean setup? I mean to delete everything comcerning ML from my SD card and again copy all the files with [6D] RawtypeTEST.zip unziped ?
I'll make a new one soon anyway, I guess the easiest thing to do is to see alloc XX frames and multiply by frame size. Picture quality needs to be raw too for this to work, make sure you didn't change it. The latest compile I have on right now shows all buffers.
Quote from: 1% on July 02, 2013, 11:53:16 PM
I'll make a new one soon anyway, I guess the easiest thing to do is to see alloc XX frames and multiply by frame size. Picture quality needs to be raw too for this to work, make sure you didn't change it. The latest compile I have on right now shows all buffers.
Shit! Sorry. It was not RAW. I thought you were talking about video mode.
Now i Get it like this:
FPS override 24
RAW on
Resolution 1808 x 770 2.35:1
Global Draw Off
Preview Hacked No Prev
Memory Hack On
1808x770 40.3-40.5MB/s: 352 frames with SanDisk 32 Ext.Pro
[6D] NewRecOpt.zip
Thank you!
Also noticed that if I turn On the frames skiping it runs continuously and skips 8 frames every second (8 out of 24 FPS) according to what I see on LV monitor
I just turn skipping off.. whats the point of having jerky video.
I always turn frame skipping off. This time it was just for test.
Could you please explain me a thing:
1808x770=1 392 160 and multiplied by 24 fps is 33 411 840. Correct? Or 33,4 MB/s?
I don't think it works like that... each frame will have a file size. Don't think you can just multiply the res.
New one is up, volume controls using wav recorder if you set it to separate wav. Also corrects some WB entries in the DNG header.
If each pixel has 14 bits of data then it's 1808*770*24*14bits = 55.76 MB.
Is bulb ramping implemented yet? I cannot find it on my camera, maybe I am using an old ML build.
Is it possible to unlock 1856 x ...... resolution with some upcoming builds? I think this would be the highest possible resolution for 1x magnification. Maybe we could get 12-13 sec (2,39:1) with it.
jmanord,
Thank you for your answer.
1%.
What is My_Rec and what is My_Trigg?
Tried Raw record and got 344 frames with 1808*770 and 24FPS
Tried My Raw and got about 177 frames
Maybe I missed the answer but there was a question here about why it shows ML menu dialog only for 3 seconds and if i don't press any button on my camera the menu goes away?
Hello all! I am read this topic for about 2 month. I`ve tried the raw video, and acquired some strange result. There are some color short lines and dots on images. It is known bug or no? What
should can i do with this?
I`ve tried both rawanizer and raw2cdng, and this color dots exists after both of program.
Under spoiler there are 2 sample images.
[spoiler]
[/spoiler]
Seems like some colour moire issue.
I think you shoud try to find some info here:
go to reply #2010 http://www.magiclantern.fm/forum/index.php?topic=5586.msg56964;topicseen#msg56964
go to reply #9 http://www.magiclantern.fm/forum/index.php?topic=6577.0
My_rec and My_trigger are bolt rec.. it doesn't work with new raw_rec but I figured people in the US might want to get some fireworks.
1%, what do you think about 1856x.... res (or so) - possible? I mean is 1808x... max or we could have a little bit more?
Quote from: kgv5 on July 03, 2013, 11:57:17 PM
1%, what do you think about 1856x.... res (or so) - possible? I mean is 1808x... max or we could have a little bit more?
Thank you for asking. I've asked 3 times or so that I thought I'd get on people's nerves... As I've said before:
"could you disable the width restriction? I understand that the 6D can't handle higher resolutions well but might as well allow users to use higher resolutions. I mean it isn't hazardous to our camera's... "
There are quite a few other times I've inquired about this... I just don't see the need for this child lock...
I understand that 6D sensor res 5568 x 3708 / 3 is 1856x1236. So maybe technically is possible but there has to be some reason that this is unavailable right now.
1856x776 would give ~103,5% of upscale to 1920x800, but probalby reduce recording time from ( i guess from ~16 to ~11-12sec).
Did you take a raw photo and got 5568 x 3708 pixels with valid image data?
Or it just feels good asking nonsense?
The source code is available, feel free to remove any "child locks" or whatever you think it shouldn't be there...
Sorry a1ex and other devs, I didn't want to upset you. I thought that there are some technical issues, i was just courious if there is a chance for improving, thats all...
I just don't get it... since the menu goes until 3.5K horizontally, why would anyone think there are child locks at 1808 or whatever other resolution?!
The resolution is auto-detected from the image buffer obtained from Canon code. You can crop that to something lower, but you can't create pixels out of nowhere. Isn't that obvious?
Ohhhh. So that's why... I'm guessing then the h264 1080p offered by canon is an upscale of the 1808 by x resolution? How would the 1dc create sharp 4k when it has a 18 mp sensor?
Quote from: a1ex on July 04, 2013, 01:32:31 AM
I just don't get it... since the menu goes until 3.5K horizontally, why would anyone think there are child locks at 1808 or whatever other resolution?!
The resolution is auto-detected from the image buffer obtained from Canon code. You can crop that to something lower, but you can't create pixels out of nowhere. Isn't that obvious?
I thought this because 1% just allowed us to get 16 more pixels in one of the previous releases. It was from 1792 to 1808.
Guys, u can't be serious !
You are again talking about the last ****ing pixels from HD when, 2 month ago, we were able to shoot only 34 frames YUV422 by sequence....
Look around you, search another camera with a ML project equivalent, adding more and more features to your camera, days after days.... for free ! Look any camera firmware update to realise what ML team already gave to us...
IMO, be patient or buy a 5D Mark III...
My bad. Sorry I asked a question. :'(
The 4k?
My theory... dunno if its right or close.
Full time 1:something crop mode, one digic takes 1/2, another digic takes 1/2 of the image height.. otherwise one digic makes the YUV and one compresses to jpeg. Some combination like that.
Now I am confused, 5472 x 3078 divided by 3 is 1824 x 1026, not 1808 x 1018
Is this why the 6d has moire?
Yeah kgv5 the effective pixels seem to be less than what you stated. But 5472/3 is 1824 which is higher than 1808. Of course I don't know if these extra pixels are actually usable.
@1% - Interesting theory thanks for the response. I always appreciate them. :)
Don't forget the frame skips too.
Quote from: 1% on July 04, 2013, 06:30:11 AM
Don't forget the frame skips too.
I don't quite understand what you are refering to...
Also: on bitbucket you repeated the name of the newest version twice. Might wanna rename that.
;D
Quote from: nativeridge on July 04, 2013, 10:13:23 AM
;D
Unfortunately I have absolutely no experience with coding. I don't even know what program to use... I read the guide by audio nut but I still am left clueless. I guess I'll take a course in college lol.
I am still having problems with auto exposure coming on when in M mode and filming at 48fps. Is there a way to stop auto exposure taking over? I want it completely manual.
To show this problem I made a quick video and stuck it on Youtube. But youtube only uploaded it at 480p, does anyone know why?
The video is shot 48fps at 634*1808, up rezed to 1080*1920 and conformed to 24fps. In real life it is sharp :)
Notice the auto exposure change at 2 seconds even though it was set to full manual in M mode
[edit] deleted video until I can sort out uploading to youtube better :(
Might be ACR, it shouldn't be changing expo at all.
Quote from: 1% on July 04, 2013, 07:01:26 PM
Might be ACR, it shouldn't be changing expo at all.
I've had this problem before. You have to turn on exposure override. Autofocus makes the image temporarily brighter to allow itself to focus better. With exposure override this won't happen which then leads to worse autofocus in low light. In bright areas it's the same. The camera used to also expose itself automatically even without autofocusing... Nevertheless exposure override does the trick.
Thanks I will try exposure override.
The youtube problem is bizarre, never happened on anything else I´ve uploaded
With zoomed in mode, is it possible to fps overide to 48fps, it only seems to record at max 30fps?
Quote from: sparedog on July 04, 2013, 08:31:21 PM
Thanks I will try exposure override.
The youtube problem is bizarre, never happened on anything else I´ve uploaded
With zoomed in mode, is it possible to fps overide to 48fps, it only seems to record at max 30fps?
I believe it was tested a month ago and I think it turned out to not be possible.
And I dont want to bash a dead horse, but would it be possible to have an option to set our own custom resolutions, one that isnt standard? Say, for example, I am designing something like an art installation and I want to make a video of exact dimensions, 118x956 - (an example not the exact specs of what I want to design), would this be possible one day in the future? I would like to be able to type in the height and width to suit my project.
or I could crop, i suppose, but I am trying to get the maximum out of the 40bps record limit issue
Quote from: xNiNELiVES on July 04, 2013, 08:41:39 PM
I believe it was tested a month ago and I think it turned out to not be possible.
Big shame, as there is virtually no moire or jaggies in my tests. Looks really nice, just wish i could over crank it =D
Custom res is possible just a bit annoying to merge with current raw source. Plus picking it via pixels would be time consuming when you just need 720P or something.
No overcranking in zoom mode except a few fps, otherwise image collapses, etc.
Quote from: 1% on July 04, 2013, 11:24:59 PM
No overcranking in zoom mode except a few fps, otherwise image collapses, etc.
boo hoo, the difference zoom mode makes is huge
1st shot, test for real world filming conditions, no zoom mode - unusuable, moire everwhere
2nd shot, test to induce extreme moire conditions, zoom mode - no moire
[edit] deleted video until I can sort out uploading to youtube better :(
Remind me, I am being dense, but do you know why LV does squash the 50/60fps footage? Thanks :)
Its a resize and not a crop :(
Quote from: 1% on July 05, 2013, 12:52:58 AM
Its a resize and not a crop :(
Do you know if this is also happening when recording 720/50/60 in h264?
I dont get why canon decided that the lv feed needs to be squishy only for fast fps, after all the sensor is 3;2, right?
H264 probably does another resize.. or raw -> yuv unsquishes.
Hi, time to use RAW on field: macro video for flying insects (lepidoptera, odonata, neuroptera, ... )
I've shooting compiling latest 6D sources. A resume of my configuration-equipement
6D, of course
canon 300mm F4L
teleconverter kenko 1.4x
sandisk extreme pro 95 32 GB exFat
sandisk extreme 64 GB (exFat) (note: no difference with pro)
raw modes I prefer 1808x678 (2.67) or 1792x762 (2.35) at 1x or 5x and 2560x958 (5x)
24 fps or 18fps (duplicating frames in post, no resampling in vegas, no interpolation (twixtor))
tripod manfroto mkc3-h1
Well, I take photos and video, depending on shot conditions. It's very difficult take a long (or short) video to a flying insect, because they remain only a few
seconds over a flower (then for me a few seconds (7"-10") of RAW continuous shooting is a extraordinary gift)
Then, most of the time I take photo, but if I think I've a chance to take a video I need switch modes speedly,
reusing camera settings (focus, aperture, ..., framing and so on). And camera on tripod all the time.
My present field workflow is focus and framing with evf in photo mode, (take a photo sometimes), swhitch to video mode (perhaps another framing in 5x), and take a video.
Manual mode, shutter and aperture fixed, iso auto.
I've been in field for 12 hours, four different days. A lot of GB of raw video and photos on the cards and I can say I've no stability issue.
Perhaps one time I remember need to take off the battery. Truly very very good job!!!
I've some problems.
1) Flickering. See video. The exposure changes as the butterfly covers more or less frame surface, opening and closing the wings. ¿It's a expected result from iso auto?. These are 5x takes.
Note: Perhaps expo override is the solution. I need to try it more. I shot without expo override, because for that I need change my workflow (no autoiso), no valid photo configuration.
http://www.youtube.com/watch?feature=player_detailpage&v=U14qXH2X-L8
2) With fps override I need to check Fast Tv, to match photo settings because this mode has the most shutter range to match my phot settins (Tv < 1/800, 1/1000, ...).
Exact FPS and low light don't have so shutter range. But Fast Tv is high jello and sometimes brings to undesirable results last shot in video (2560x958 18fps has apparent jello effect). But in previous builds I think it was
possible to have high shutters with Exact FPS or Low Light. ¿It will be possible to have fast shutter speeds on these modes?
Best regards
Quote from: nandoide on July 06, 2013, 09:27:10 AM
1) Flickering. See video. The exposure changes as the butterfly covers more or less frame surface, opening and closing the wings. ¿It's a expected result from iso auto?. These are 5x takes.
Note: Perhaps expo override is the solution. I need to try it more. I shot without expo override, because for that I need change my workflow (no autoiso), no valid photo configuration.
Yes I have had the same problem with auto iso. is is better to video using fixed iso and manual exposure/shutter
FPS wasn't locked to real shutter speed previously. So you could pick whatever you wanted and there was no effect.
Is there a way to have ML alert the user before the battery dies? I enjoy timelapses, and it would be very convenient if the camera would alarm prior to the camera shutting off. That way, the user could seamlessly change out batteries and not have to worry about the potential gap in the time lapse. Would it be possible with a third party battery that do not have the capability to report battery percentage?
Cheers!
Many congrats to the ML team for pulling off RAW video, you guys brought on a revolution.
I'm beginning to wonder though if it's all a 5D3 thing...looks like 6D will never get 1080p RAW, for example. I'm shooting H.264 1080p with CineStyle profile on my 6D and getting decent results and am wondering if messing with lower res RAW on 6D and then up-resing is worth the effort. Any comparisons?
Sorry if this has already been discussed.
You can see this (reply #93)
http://www.magiclantern.fm/forum/index.php?topic=6215.75
Shooting raw in 1600x... resolution in terms of sharpness is comparable to 1080p h264. Raw gives much more flexibility in color grading but introduces many workflow problems. 1808x756 (the highest 2.39:1 res available for 6D in 1x mode) or even 1726x724 gives more details and sharpeness. Not as much as 1920x800 though but the difference is not significant IMO.
Quote from: kgv5 on July 08, 2013, 01:14:35 AM
You can see this (reply #93)
http://www.magiclantern.fm/forum/index.php?topic=6215.75
Shooting raw in 1600x... resolution in terms of sharpness is comparable to 1080p h264. Raw gives much more flexibility in color grading but introduces many workflow problems. 1808x756 (the highest 2.39:1 res available for 6D in 1x mode) or even 1726x724 gives more details and sharpeness. Not as much as 1920x800 though but the difference is not significant IMO.
Do you think 1880 x 1012 is almost as good as 1920x1080?
I think it is hard to see without putting such a footage side by side on one screen, magnyfing it 200-400% and making comparison one spot after another.
I bet 1880x.... looks almost the same (~98% of pixels), 1808x.. or even 1726x.. looks very similar (94, 90%), just little bit softer, really not much.
http://www.youtube.com/watch?v=bY-7UspVUb8
https://www.dropbox.com/s/jvewws2bsal63gc/resolution%20comparison%20HQ.mp4
PS: so maybe you xNiNELiVES have some 6D raw footage left and now you could make some similar comparison 6D and 5D2 ? Thanks
The camera will come soon. I think depending on how quick I sell my 6D on eBay, I'll have both cameras at once. So I should be able to test... The thing is though I don't know how to edit for shit. I'll upload .RAW files here once I have em'. I'm guessing someone here has a bit of spare time on their hands and is good with After effects and premiere pro...
kgv5 I didn't know you're from Russia, pretty cool... Senior. lol
Not from Russia, Poland.
Cheers
Good think is to upload raw files but please make them not heavier than 100-200MB each. Thanks.
Quote from: kgv5 on July 08, 2013, 07:16:32 AM
I bet 1880x.... looks almost the same (~98% of pixels), 1808x.. or even 1726x.. looks very similar (94, 90%), just little bit softer, really not much.
I am going to quote myself :)
I just discovered InstantHD upscaling (I know, better late than never :). With this the image is not softer anymore like it was with stock AE resizing . Now even 1726x.... is just the same to my eyes like 1920x800 obviously except slightly different framing. It's just awesome!
Quote from: kgv5 on July 09, 2013, 12:13:59 AM
I am going to quote myself :)
I just discovered InstantHD upscaling (I know, better late than never :). With this the image is not softer anymore like it was with stock AE resizing . Now even 1726x.... is just the same to my eyes like 1920x800 obviously except slightly different framing. It's just awesome!
Yeah why does framing change. I've been wondering why since I've started using it.
Quote from: xNiNELiVES on July 09, 2013, 12:53:43 AM
Yeah why does framing change. I've been wondering why since I've started using it.
because lower resolution means more crop (quality is exactly the same but the picture is smaller) and to have fullHD you have to resize it, make it bigger to fit the whole screen. Normal resizing just makes pixels bigger/stretched (which add bit of softeness) apps like instant HD makes an interpolation-simply they are adding new pixels between existing ones.
Hey guys, here is my first test with the 6D. I found it really unstable compared to the 60D and 5Ds. Hopefully it will get smoothed out later. Main thing was it would think I wanted to record RAW even if I disabled it. At least I think that is what was happening. This would prevent from recording in normal h264 or at least the data wouldn't write to the card. Other issues I had at the high ISOs of the firework footage where a ton of bad pixels and shimmering that never appeared before in RAW2DNG. Still turned out cool though and it's really short so check it out. I'm attaching my error logs.
https://www.dropbox.com/s/he6nmk8mll94k50/Archive.zip
alright installed ML last night and there is one issue I noticed:
I'm getting error "Movie stopped recording automatically" when trying to record in 60p (all-I or IPB), tried formatting the card (exfat), works fine when ML not installed, with ML installed it drops after few seconds: focus peaking will freeze and shortly after the msg appears and it stops recording. tried with global draw off and its the same thing.
card is sandisk 32gb 30mb/s class 10
i have 2 of those cards and its the same on both.
is that a known issue?
cheers guys
The card you have is a bit weak. I think even awful on 21MB/s cameras. But you can lower H264 settings and be ok, horrible moire aside. The configs are set up for people who want 60-100Mb/s 24/30P and 60fps is 2x the frames.
QuoteI found it really unstable compared to the 60D and 5Ds
What parts? I only had 2 problem.
1. Error from modules being too big a few builds back. I was recording raw in crop mode and it kept pooping out.
2. Loaded wrong bin, I think 50D and had no use of the camera until I went home :(
So is there much of a difference between 1x vs 3x CBR?
I appreciate how you guys are enthusiastic about raw video but there seems to be no talk about other ffeatures of ML on 6D. Could someone tell me are functions like intervalometer ,focus peaking , magic zoom , focus stacking, audio shot etc stable on 6D and also could you point to the latest stable beta and install procedure cuz I dont want to break something... didnt care that much ehen I was on 550D .:)
Quote from: STELYA on July 12, 2013, 01:17:05 AM
ICould someone tell me are functions like intervalometer ,focus peaking , magic zoom , focus stacking, audio shot etc stable on 6D and also could you point to the latest stable beta and install procedure cuz I dont want to break something...
You can find instructions on how to install here: http://www.magiclantern.fm/forum/index.php?topic=5530.msg37766#msg37766
You can find information about the various functions of ML in the manual here: http://wiki.magiclantern.fm/userguide
Quote from: STELYA on July 12, 2013, 01:17:05 AM
I appreciate how you guys are enthusiastic about raw video but there seems to be no talk about other ffeatures of ML on 6D. Could someone tell me are functions like intervalometer ,focus peaking , magic zoom , focus stacking, audio shot etc stable on 6D and also could you point to the latest stable beta and install procedure cuz I dont want to break something... didnt care that much ehen I was on 550D .:)
They're stable its just that no body has tested them that much.
Thanks guys .. will be testing asap.
What about the fact that the 6D disables video recording while WI-FI is on?
What's the theory behind it? I guess it's not a HW limitation but more a way to prevent videographers to use a fully functional wireless monitor when they shoot videos.
Ideas?
Hi. Currently i have some bugs in ML. In photo mode, mode AV when i shoot stills in exif DPP shows me that there is exposure comensaition +1/3. On same image in Canon 6d, when i view that image shows me, that +1 compensation. But i`ve not set any compensations. In ML menu ETTR are off. Also ML can`t do screenshot, - after 10 sec blinking error70 popuped. I`ve try to on-off camera, pull ot - pull in the battery, but screenshots still shows me error 70.
(sorry for my english, it is not native for me)
Quote from: ilguercio on July 13, 2013, 06:34:11 AM
What about the fact that the 6D disables video recording while WI-FI is on?
What's the theory behind it? I guess it's not a HW limitation but more a way to prevent videographers to use a fully functional wireless monitor when they shoot videos.
Ideas?
Raw recording works wirelessly (wifi) with EOS remote (although you cannot control start/stop, only iso etc, its about 15fps). H264 does't work. Seems, that camera or app doesn't treat raw recording as a movie mode or so.
There is an info on the cam screen "movie recordind is disabled when fifi is on" - disregard this :) Just turn raw on and start shooting. Sometimes this "disabled" information is visible during recording, sometimes (more often) is not. Switching between screen modes (with info button) somehow helps to remove the text.
EDIT: Important - have to set my phone screen / power saving settings to turn off the screen not after 15sec or so but much longer, depending on your shooting needs. Every time when my phone turns the screen off, it cancells monitoring and the camera just stops recording.
Quote from: kgv5 on July 13, 2013, 11:20:38 AM
Raw recording works wirelessly (wifi) with EOS remote (although you cannot control start/stop, only iso etc, its about 15fps). H264 does't work. Seems, that camera or app doesn't treat raw recording as a movie mode or so.
There is an info on the cam screen "movie recordind is disabled when fifi is on" - disregard this :) Just turn raw on and start shooting. Sometimes this "disabled" information is visible during recording, sometimes (more often) is not. Switching between screen modes (with info button) somehow helps to remove the text.
EDIT: Important - have to set my phone screen / power saving settings to turn off the screen not after 15sec or so but much longer, depending on your shooting needs. Every time when my phone turns the screen off, it cancells monitoring and the camera just stops recording.
Yeah, this is basically my point.
If you can open LV and record some raw footage it means that WI-FI monitoring is disabled just on FW side and i guess it should be unlockable.
H264 is disabled for real when wifi is on. Just shoot in photo mode (toggle raw). Which version did screen shot die in? Just took one.
What's the easy way to installa magic lantern on 6d? Which functions work on this camera? Thanks a lot.
Quote from: 1% on July 14, 2013, 07:38:40 AM
H264 is disabled for real when wifi is on. Just shoot in photo mode (toggle raw). Which version did screen shot die in? Just took one.
Yeah, i am just saying that it's not due to an excessive computational load onto the camera but because Canon does not want people to use a smartphone as an external monitor.
I can't imagine any other reason.
The H264 encoder and the wifi chip share the same edmacs maybe... something along those lines. I tried recording video while wifi was on. It acts like it records and doesn't write. Its really kludgy to pop up that message, I think canon legitimately can't get both to work at the same time.
It makes more sense now.
Also, i was thinking about the 50D. It was given UDMA7 support only with the last FW update so maybe in the near future Canon will allow us to get the most out of those UHS cards. Who knows...
Its UDMA7? I thought it was UDMA 6.
QuoteAlso, i was thinking about the 50D. It was given UDMA7 support only with the last FW update so maybe in the near future Canon will allow us to get the most out of those UHS cards. Who knows...
Huh? So you think that's a software issue and not hardware?
we're accepting patches for cf drivers if you know how to write them ;)
Quote from: 1% on July 14, 2013, 05:19:55 PM
Its UDMA7? I thought it was UDMA 6.
Yeah, i might be mistaken.
Can we consolidate settings somewhere so we can find what people are using on their 6D?
edit: i guess reading this side of the forum (http://www.magiclantern.fm/forum/index.php?topic=5530.350) is kind of helpful. Just had to read through all of it :)
Just trying to extract the current highest resolution for continuous recording right now. I have a feeling my card is a teeny bit of a bottleneck, and not the camera BUS itself
Quote from: 1% on July 11, 2013, 11:40:43 PM
The card you have is a bit weak. I think even awful on 21MB/s cameras. But you can lower H264 settings and be ok, horrible moire aside. The configs are set up for people who want 60-100Mb/s 24/30P and 60fps is 2x the frames.
hey 1% you were right. Bought a lexar pro 90mbps and it worked like a charm (focus peaking that is, didnt try raw yet)
will be returning this card and will be buying it online instead (paid 115$ cad lol)
With the newest builds your card should give 40-41MB/s. It is the maximum right now.
On 6D continous recording is possible with quite low resolution, 16:9 - 1344x756, 2,39:1 1536x642. If you are shooting very long takes it will look not much better or even the same like 1080p h264 in terms of sharpness. Everybody are obsessed with having CONTINOUS recording but I found shorter takes with higher resolutions very usable because:
1) i don't shoot interviews (i mean not in raw)
2) right now there is no way to trim raw clips i prefer to have many shorter clips on the card than one very long
3) in any film on this forum i have never seen takes which are longer than couple of seconds.
I am trying to plan my takes to match recording time. If I want the maximum resolution (for 2,39:1 - 1808x756 - than upscale with instantHD to 1920x800) i know than i will have 15 sec (for example i set my motorized slider to make full lenght slide in 15sec, 15sec is also very sufficient for most of crane shots) If I need 30 seconds I use 1700x something. If I want to shoot couple of minutes - well, i am using h264 with ML best encoder settings.
Other way to extend recording time is to set lower fps (and use some frame blending solution in post - like twixtor) - every frame per second less makes a HUGE difference.
Quote from: kgv5 on July 17, 2013, 10:01:06 AM
With the newest builds your card should give 40-41MB/s. It is the maximum right now.
On 6D continous recording is possible with quite low resolution, 16:9 - 1344x756, 2,39:1 1536x642. If you are shooting very long takes it will look not much better or even the same like 1080p h264 in terms of sharpness. Everybody are obsessed with having CONTINOUS recording but I found shorter takes with higher resolutions very usable because:
1) i don't shoot interviews (i mean not in raw)
2) right now there is no way to trim raw clips i prefer to have many shorter clips on the card than one very long
3) in any film on this forum i have never seen takes which are longer than couple of seconds.
I am trying to plan my takes to match recording time. If I want the maximum resolution (for 2,39:1 - 1808x756 - than upscale with instantHD to 1920x800) i know than i will have 15 sec (for example i set my motorized slider to make full lenght slide in 15sec, 15sec is also very sufficient for most of crane shots) If I need 30 seconds I use 1700x something. If I want to shoot couple of minutes - well, i am using h264 with ML best encoder settings.
Other way to extend recording time is to set lower fps (and use some frame blending solution in post - like twixtor) - every frame per second less makes a HUGE difference.
cool bro,
ill be shooting mostly music videos, so i need the recording time to be at least long enough for 1 verse, so about a min or so depending on tempo
and ill mostly use an aspect ratio of approx 2.4:1 should be good for me, since most of the time im adding black bars in post anyways
but since we cant record audio yet (dont have an external recording system yet, and not sure how to properly sync)
and we cannot replay the videos in camera after its been shot correct?
this will make it hard for usage in the field, FOR NOW
but still I am extremely excited about all the recent ML developments, still wishing i would've went with the 5d3 though :p
might try a few takes here and there in raw, like B rolls
RAW video aside, i'm happy with the ML development. Great job guys! I'd love to donate a beer to you guys or something. haha
New shutter method seems to give a much better range with FPS override. As for playing back clips, you can, in black and white. Close enough for me :)
Also... wow, a lot of the noise & dead pixels appear to be gone, holy shit. Even at 3fps.
Do you guys think that recording black/white might make it closer for us to record 1080p RAW for a little longer? Or, is it more since it would have to convert from color to b/w?
I'm willing to do film noir :)
Hey 1%.
I saw in the commit logs that
"One Percent c9d4aef ADTG shutter! Dual ISO soon!"
Does that mean that you think the 6d will have Dual ISO also?
If so .. Yay! YAY!
That thing with the moiring on highlights/dark areas that Alex was on about ... is that avoidable if one simply shoots at half the resolution?
We'll see... REG3 moves for ISO so I have to try stuff... I just figured out addresses + shutter last night. Have to find the reg in photo mode too.
Thanks for your work! Really excited and I hope we can also get dual ISO.
ADTG shutter, what is that? Can you dumb it down a little for people like me? :)
I'm guessing there is only dual ISO on the newer cameras? No Dual ISO for the 5D Mark II I presume?
I'll try on 50D first, it might actually be easier.
ADTG shutter speeds are set via cmos reg addresses... and from the little time I had to play with it, it fixed fps override. Need to let it run for a while and see if you still get dots/stripes etc.. but so far so good.
Quote from: 1% on July 19, 2013, 03:36:18 PM
I'll try on 50D first, it might actually be easier.
ADTG shutter speeds are set via cmos reg addresses... and from the little time I had to play with it, it fixed fps override. Need to let it run for a while and see if you still get dots/stripes etc.. but so far so good.
Basically, to make shutter speed NOT equal to 1/fps?
Also, do you thing there is a chance to "borrow" some pixel binning from the 5DIII?
Hi, guys. Been a long time ML user, first time poster.
I'm not sure where to begin in this thread to find answers to my questions, so I thought I'd just ask.
1. What SD cards do you recommend, and is that the current bottleneck? I tried RAW video and couldn't get anything for more than a second at resolutions around 1280x720 and above. I'm using this Transcend card: http://amzn.com/B008CVHLT2. Would the Sandisks work better?: http://amzn.com/B007NDL56A. Or anything else?
2. When I had the build with RAW video installed, the ML menu would spontaneously close itself out after only a few seconds - quite annoying. Had to switch it back to a previous release (glad I kept those file and their instructions on my computer!). What am I doing wrong?
Quote from: Cloud_Walker on July 22, 2013, 10:55:58 AM
1. What SD cards do you recommend, and is that the current bottleneck?
2. When I had the build with RAW video installed, the ML menu would spontaneously close itself out after only a few seconds - quite annoying. Had to switch it back to a previous release (glad I kept those file and their instructions on my computer!). What am I doing wrong?
1. Forget Transcend, use Sandisk Extreme 32/64/128GB or Extreme PRO 32/64GB
2. Long time bug... When ML menu is displayed, if you don't click any button, it quits. Normal behaviour for now.
(you can record continuously only at resolutions like 1536x636 or 1600x640)
Many thanks!
I installed on my 6D ML. I made some RAW video test's whit supermoon https://vimeo.com/68936611 (https://vimeo.com/68936611)an made some good pictures, etc, etc. But one day in photo mode i shoot again some pictures in cr2, but pictures are not recognized by LR and DxO this time. I reinstall apps on osx 10.8.4 i update osx. Nothing. Only DPP read cr2 files. It was frustrating, and i think and think... I change cards, lenses, try all combinations. Exif was correct in terms of lens, camera, aperture, iso, etc. At the end i go to reinstall firmware 1.1.3. on my 6D and I try to read first cr2 and everything was OK.
Does anybody knows why and what was corrupted? Very often i have error 70.
Quote from: brdski on July 22, 2013, 11:28:56 PM
I installed on my 6D ML. I made some RAW video test's whit supermoon https://vimeo.com/68936611 (https://vimeo.com/68936611)an made some good pictures, etc, etc. But one day in photo mode i shoot again some pictures in cr2, but pictures are not recognized by LR and DxO this time. I reinstall apps on osx 10.8.4 i update osx. Nothing. Only DPP read cr2 files. It was frustrating, and i think and think... I change cards, lenses, try all combinations. Exif was correct in terms of lens, camera, aperture, iso, etc. At the end i go to reinstall firmware 1.1.3. on my 6D and I try to read first cr2 and everything was OK.
Does anybody knows why and what was corrupted? Very often i have error 70.
What LR version are you using? Old LR don't read 6D cr2s. You need at least LR4. If you're a cheapie and don't want to buy LR4 you can use the free Adobe Camera Raw (ACR) converter to convert the cr2s to a standard DNG that every program can read.
Quote from: Cloud_Walker on July 22, 2013, 10:55:58 AM
Hi, guys. Been a long time ML user, first time poster.
I'm not sure where to begin in this thread to find answers to my questions, so I thought I'd just ask.
1. What SD cards do you recommend, and is that the current bottleneck? I tried RAW video and couldn't get anything for more than a second at resolutions around 1280x720 and above. I'm using this Transcend card: http://amzn.com/B008CVHLT2.
On this transcend i get continously raw video 1280x720. And ML shows me the 36-37 mb/sec speed. Using exfat 4kb clasters.
Quote from: oscaroo on July 23, 2013, 02:09:06 AM
What LR version are you using? Old LR don't read 6D cr2s. You need at least LR4. If you're a cheapie and don't want to buy LR4 you can use the free Adobe Camera Raw (ACR) converter to convert the cr2s to a standard DNG that every program can read.
I use LR4. Problem was in 6D after using ML, after "errors 70" camera dont write correct cr2 file. I solve problem whit reinstalling original canon firmware 1.1.3. After that action cr2 is recognized by LR4 and DxO. ;)
@:1% mostly
Is it possible to detect the state of the LOCK slider?
I am asking because i don't use it and i find it a bit useless so we might as well reutilize it for some other function.
What do you think about it?
Guys
I compared the footage from 5D3 and 6D with the VAF-6D filter.
I have posted original DNG's.
http://www.magiclantern.fm/forum/index.php?topic=6577.0
I might have found a weird behaviour when shooting videos with FPS override.
My case today:
Full HD ALL-I and FPS override set to 35 fps.
When going past 1/250 i get a very bizzarre flickering, as if i am shooting HDR video but i am not.
Any ideas? Shutter speeds are fine, FPS override allows me to go all the way up to 1/43xx but as soon as i choose 1/320 i get epilepsy.
The safe timer limits need to be adjusted (35fps is too much). Adjust the timers manually and see when the image gets restored.
Quote from: a1ex on July 25, 2013, 05:38:17 AM
The safe timer limits need to be adjusted (35fps is too much). Adjust the timers manually and see when the image gets restored.
Cool, so what is basically happening at those shutter speeds?
1/250 is fine for that FPS setting while 1/320 makes it flash.
If i can help in any way...
Also, as i asked above, is the pixel binning method portable from the 5DIII?
One more thing, i noticed that the crop window when shooting raw is a tiny bit narrower than the full frame at maximum resolution.
Not sure if it's a problem with the framing or what.
Yeah, use the menu and find the safe timer values.
I guess i need to find the timers for every Canon FPS option.
If i select 24fps from Canon menu and i set 35fps with override i get 1/80 max while i get 1/250 max when i start from 30fps in canon menu.
Hey Guys
I have been out of the loop for some time, what is NEW and FUN?!
Can I find all the necessary files somewhere to get this up and running? I have only really old files, where is noisyboy when you need him!
I have to compile a new version. It has lower fps timers (they had a rework when 5D3 did, fixed the flashing mentioned) and uses adtg shutters so no more funky dots/lines, etc.
A slight down side is the higher shutters flip with fps. Mainly its annoying to see 1/1600 flip to 1/1800, etc.
Quote from: 1% on July 27, 2013, 07:17:49 PM
I have to compile a new version. It has lower fps timers (they had a rework when 5D3 did, fixed the flashing mentioned) and uses adtg shutters so no more funky dots/lines, etc.
A slight down side is the higher shutters flip with fps. Mainly its annoying to see 1/1600 flip to 1/1800, etc.
Where can I download newest .bin file please? I have go to bitbucket, but the newest file is from July 02? :<
Hey Pio
Those are the latest bins.
My guess is 1% is busy with RL.
Unfortunately its true and I'm not having any fun. :)
One project has 2 more days on it I think, and then I'll get some free time.
Bitbucket is being a pain again.
http://www.filedropper.com/6dadtgshutter
I was hoping some people would self compile while I was out but that only happened for 50D. Check low FPS like 2-3 fps, should have less or no defects but I didn't try for a really long time.
Why is 25600 iso rated as H in video mode and as a normal iso speed in photo?
I will offer my firstborn for the stable release of ML for Canon 6D ʕु•̫͡•ʔु
In the meantime, my paypal support will have to do.
Here is hoping the DotTune makes it into the release. ♥
Awesome work ML team
Video mode doesn't allow as much gain... its shit anyway. Technically can push it up a wee bit higher but it causes err 70/lockup in bulb mode.
Level seems good in photo mode and switching now, yay. FPS is fixed?
Quote
I will offer my firstborn for the stable release of ML for Canon 6D
So all these months of subsequent versions are....? 6D is pretty good... wish the dual ISO worked.. or headphone.. what else is missing?
EOS-M and 600D are a bit jacked ATM.
So no dual iso? Ever? What can you say as of right now, haven't read up in a while about it working on other cameras.
doing a paid shoot with the 6d w/ ML non-raw this weekend. ((will safety shoot with the 5dmarkiii no ML))
I'll report back.
Does the audio that we can record separately have embedded timecode?
If not, is it possible to "burn" it in the audio file?
Also, what happens to the timecode when we are using FPS override?
Audio is plain wav data. Doesn't have timecode.
I never looked at timecode on fps override clips, figured it was wrong but who knows.
What about the LOCK slider? A few posts ago i was suggesting to use it as a custom slider for whatever, since i don't use it and i am sure many don't as well.
It generates a generic 0x54 event so pretty useless.
QuoteSo no dual iso? Ever?
Every cam I have, there are only a few values for iso and the extra channels are missing. I'll of course try some more but I don't have high hopes.
Hi folks, this may be a tad a off... I read the topic on a daily basis, but have not found any news about 1.1.3 bootability recently.
Is this something impossible to do right now? Is there a chance that 1.1.4 or whatever comes next will be fully compatible with ML and we wont need to use 1.1.2 to make our cards bootable?
Thanks! :)
I am on 1.1.3...
You just need 1.1.2 to set the bootflag, once you've done that (one single time) there is no difference.
Please don't hit me if my idea is stupid: how about faking a dual iso with 2 quick liveview captures, each one at different iso.
For this You have HDR mode, it alternates iso values, say one frame iso 100, next iso 1600, can be very useful but produces some motion artifacts. It is great though, i've been using it a lot.
Yes, I understand, but you could capture just only 2 frames as fast as possible to make it more like a photo.
I will do one test tomorow with highest HDR RAW video resolution and highest framerate, and combine the first 2 DNGs.
You can already do that with photo HDR or video HDR. Dual ISO is I think 2 isos in 1 exposure.
What's good 6Dizzle peeps!? Been out the game working away for a while so god knows what's happened the last few weeks (that's a lot of board to read in 3/4 weeks). Anything new that needs help testing?
8)
Quote from: noisyboy on August 03, 2013, 02:28:26 AM
What's good 6Dizzle peeps!? Been out the game working away for a while so god knows what's happened the last few weeks (that's a lot of board to read in 3/4 weeks). Anything new that needs help testing?
8)
Well did you hear about the dual iso?
Yeah I kept an eye on it as much as I could! Seriously cool work but not holding out much hope for my trusty 6D. Might breath a little life back into my old 7D yet though eh! Saw that A1ex had located the raw buffers :) Nice work all round! Standard procedure 8)
Yeah I sold my 6D for a 5D2. I can record 1880x940 continuous but I can't set a minimum shutter speed (yet) for photos! Well at least the pros outweigh the cons...
Quote from: 1% on August 03, 2013, 12:03:21 AM
You can already do that with photo HDR or video HDR. Dual ISO is I think 2 isos in 1 exposure.
Yes of course, but I mean a real HDR photo it's not as quick as 2 captures from LV, which is not as quick as the real dual ISO... oh well.. I guess it was a silly idea, it doesn't work with a slow shutter speed anyway. hehe.
So here is my test of a fake an "instant" HDR photo using 2 RAW HDR video frames at maximum resolution and FPS. iso 100 / 1600
Handheld with a 100mm lens.
Hey 1% n co.
I was out travelling with the fam these last few days and have experienced a few crashes.
Logs are at:
https://www.dropbox.com/sh/syogzdreypjre2f/rbMS0D3eDQ
I'll have them there for a week or three.
In one instance, I took a photo and started an audio tag. Then I stopped the audio tag and it started playing back, but, I didn't want it to play back so I wanted to shut it up prematurely. So I switched off the camera and the audio that was playing became chipmunk, ended, and the camera crashed.
Another time where it crashed, I was trying to do a video and it crashed. I think it was cos I accidentally had it set to record wav separate to vid and it wouldn't end recording a video - instead it would crash. It also crashed later doing a second video with normal wav recording - ie not separate.
*shrug
Thanks nonethless, i'm still a happy customer.
I see some memory errors which I haven't before, have to figure out how to reproduce them.
Then a bunch of times it couldn't create the wav file.
Try latest build thats up and see if there is a consistent way to crash out.
These are the interesting ones. From task manager? Some property? NPE?
Quote
ASSERT: IS_ERROR( Err ) == FALSE
at ./Multicast/PropertyMgr.c:50, task AeWb
lv:1 mode:3
ASSERT: IS_ERROR( Err ) == FALSE
at ./Multicast/PropertyMgr.c:50, task clock_task
lv:1 mode:0
Gday.
I'll update once I'm home. I won't update to the new version while on hols in case it regresses.
Once I'm home i'll have another mini holiday two weeks later, so i'll work the 6d hard again.
Makes sense.
so the shoot is over from last weekend, we weren't shooting raw, a few issues, but ill credit that mostly to the shitty cards the producers bought.
* Could not get guide track audio to record on the clip. in Normal or Separate WAV settings - clearly I was doing something wrong, but Id like to know what. the guide track was to help the editor sync in addition to the slate. he said that occasionally there would be the wav files on the card (separate wav setting) yet they all read 6mins :15 seconds and were blank/empty
* the framerate override didn't work, or appear to do anything (which is fine, we just did a base canon OS 60fps) but I'm probably using this wrong as well - is there a hidden step im missing other then enabling & setting the rate and whatnot within the submenu?
[6D] ADTG Shutter build.
The wav should work, you see the file name on the screen when it records. External mic or internal mic? I just recorded 2 of them and I used the sound recorder to do adr with an external.
Also should note, one problem I had was the mono jack I was using kept disconnecting and causing blank/empty wavs. I could easily see it until I played back the sound files and killed the meters.
FPS should also change the FPS, it does here. Look at the top right corner you should see fps.
If you play the WAV from camera everything is good.
If you play it on the computer they all have a lenght of 6 min and 15 sec and if you try and scroll further to the end you get an error.
I don't understand it :/
Hmm.. open it with audacity (or sound forge, sonar, pro-tools?) and re-save first.
The header is static so the real length isn't in there and may confuse plain old wav players.
Quote from: 1% on August 06, 2013, 03:12:51 AM
Hmm.. open it with audacity (or sound forge, sonar, pro-tools?) and re-save first.
The header is static so the real length isn't in there and may confuse plain old wav players.
Cool, i didn't know this.
right, but recording seperate is another step for our editor/assist editor - all Im looking for is the audio married to the video track, not separate so that its a quicker sync to the externaly recorded audio. the internal mic is fine as its mostly there to just hear the slate.
You can't do flush rate or gop + embedded audio, nor fps override. Otherwise its should work from canon menus as normal (even at like 120Mb/s +). To get those 3 I have to figure out how to patch the audio so the sync functions don't crash the camera.
The begining of the wavs should be in sync with the start of the video clip. After a while they seem to drift someone said that it was in sync with 25P and 600D TL1 working with all audio functions in 25p seems to support that. Alternately I think you can change the wav length to like 103%... if you beep 2 separate times throughout the clip you can probably get figure out the stretch/skew, it should be the same every time.
I also can't just turn on embedded audio for like 3 seconds and turn it off, same crash issue. I can mute it but it will keep writing a blank stream/or crashing.
P.S. this isn't a 6D exclusive issue.. every camera looks affected by it.
Hey, does anyone know how to make a custom version of ML? I will explain.
I don't have a use for RAW in my professional life, or intervalometer or anything other than Focus Peaking and On screen audio meters.
Is there are way I can get someone to help me just narrow ML down to those features? Or is it an all or nothing thing.
There is an option for a custom menu.
Quote from: 1% on August 07, 2013, 11:06:30 PM
You can't do flush rate or gop + embedded audio, nor fps override. Otherwise its should work from canon menus as normal (even at like 120Mb/s +). To get those 3 I have to figure out how to patch the audio so the sync functions don't crash the camera.
The begining of the wavs should be in sync with the start of the video clip. After a while they seem to drift someone said that it was in sync with 25P and 600D TL1 working with all audio functions in 25p seems to support that. Alternately I think you can change the wav length to like 103%... if you beep 2 separate times throughout the clip you can probably get figure out the stretch/skew, it should be the same every time.
I also can't just turn on embedded audio for like 3 seconds and turn it off, same crash issue. I can mute it but it will keep writing a blank stream/or crashing.
P.S. this isn't a 6D exclusive issue.. every camera looks affected by it.
copy, so it wasnt my ineptitude it's a software hurdle. cool. let me know how I can help.
Quote from: ilguercio on August 08, 2013, 05:18:47 AM
There is an option for a custom menu.
But I mean, make it so those other features aren't even part of the package. Just focus peaking, and audio meters.
Limit what can go wrong when I am shooting a wedding and the camera errors out.
Quote from: fauxtographer on August 08, 2013, 06:16:30 AM
But I mean, make it so those other features aren't even part of the package. Just focus peaking, and audio meters.
Limit what can go wrong when I am shooting a wedding and the camera errors out.
Yes, build your own ML autoexec if you want this.
It doesn't run much better when you take everything out.
I also have had the separate wav recording crashes. I switched one of my cards back to the Rec w Vol, build on 7-2-13, and I have less trouble out of that build as far as being able to switch between Raw, and then wanting some reg footage with a separate wav. But with the current build it says my card is not fast enough to record a separate wav, I switch it back to the older build, same settings and it records video and separate audio fine. Seems like a strange glitch, wish I knew more. I hardly understand the meaning of the newest build, but like to try them as they are updated.
If you're getting that message it means the writes from wav are timing out. Are you switching raw off between recording H264?
That is what it seemed like. Immediately they, timed out. It happened either way. I could turn the camera on and try straight for the H246, wav crash. Same happened if I recorded raw, then switched. I changed another card back to the modules of 7.2.13, same result. The wav file did not time out, but recorded just fine.
I just went back and forth between 24P raw and H264 with separate wav and a config loaded and nothing timed out tho. Are you sure you had same .sym file as autoexec.bin?
You must have been correct. I went and downloaded the updated files again to make sure I had everything correct. Switched out the files on my card. It is working just fine now. Thank you. I am slowly still trying to learn what I am doing with the Encoder options. I had been bypassing and using the H246 from the camera for my vaf tests yesterday.
There's a bit of files to keep straight now. Also with the sym file you can get a 1/2 working version and you won't notice until you go use that one thing which crashes it. I've done this to myself too.
So it's late and I'm trying to dig through the 104 pages of posts to varying degrees of success.
I'm hunting the best settings for continuous raw recording. 2.35 is fine with me w/ the upscale needed.
what modules in, what settings? ideally live view enabled.
Thanks 1% for the fullpack zip.
I'm quite happy to see script examples, inc a clock! Yay a clock.
I haven't tried them out yet but I'm sure gonna do that tomorrow when I get home.
Good work on 50d Dual ISO also, I hope it comes to 6d too one day, no hurry. Yay.
PicoC is off so i dunno how much use the scripts are... but dual iso is working. Photo and LV.
ooooooh. Yay at Dual ISO.
Boo at PicoC. Meh. One day i'll have a clock on my camera, one day. I'm patient.
Quick Q:
To do developing for the 6d, is there a virtualbox linux image I can just grab, check out code, and modify and deploy?
Yay. I found the VM image.
http://www.magiclantern.fm/forum/index.php?topic=991.0;all
D'oh
Bug?
"ML ASSERT:
raw_lv_request_count >= 0
at ../../src/raw.c:1310 (raw_lv_release), task livev_hiprio_task
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Aug11.6D113
Mercurial changeset : 90a269a7cd8f+ (unified) tip
Built on 2013-08-11 18:24:55 UTC by user@D610.
Free Memory : 450K + 1441K
"
On the latest version. ETTR wouldn't work. It just didn't do anything. Eventually I twiddled the knobs till it worked. I did stuff like turn on Expo Sim (was on DOF button only, now always on). Then it was doing something, but after some fiddling around it said Whoops and gave up. I think the scene was too dark for it to ETTR.
Sometimes that happens and auto ettr doesn't want to work. It means tried to turn on raw and still waiting/couldn't.
I have to figure out why, its hit or miss. It will do this a bunch in a row and when you restart it goes back to working.
You have a clock on the photo screen. I thought date used to be there too tho.
Good job with Dual ISO.
Does it work the same as the 5DIII regarding the processing of the files?
Great job with the dual ISO 1%!!
Only tested with stills, but this is awesome!
Thanks for the Dual ISO 1% great work !
Just tested dual iso. That's fantastic! Thanks!
I got a few crashes after taking some photos, if you guys have any clue.
Hi 1%! I'm reding every day this topic so I've done all 105pages!
I have a question about HDMI out (don't find answer on this question yet)! Do you think a day it will possible to have uncompressed HDMI out?
OR better to embed dng or raw or LV image in hdmi stream in cam, record it with Ninja and then extract dngs from it on pc/mac?
May be stupid/futuristic question but I am curios about this possibility becouse our SD controller is too slow to record dngs to SD card and HDMI specs are (from wiki):
-HDMI permits sRGB 4:4:4 chroma subsampling (8–16 bits per component), xvYCC 4:4:4 chroma subsampling (8–16 bits per component), YCbCr 4:4:4 chroma subsampling (8–16 bits per component), or YCbCr 4:2:2 chroma subsampling (8–12 bits per component).
-HDMI 1.4 was released on May 28, 2009, and the first HDMI 1.4 products were available in the second half of 2009.[111][143] HDMI 1.4 increases the maximum resolution to 4K × 2K, i.e. 3840 × 2160p (Quad HD) at 24 Hz/25 Hz/30 Hz or 4096 × 2160p at 24 Hz (which is a resolution used with digital theaters); an HDMI Ethernet Channel (HEC), which allows for a 100 Mbit/s Ethernet connection between the two HDMI connected devices so they can share an Internet connection;[60] and introduces an Audio Return Channel (ARC),[59] 3D Over HDMI, a new Micro HDMI Connector, expanded support for color spaces, with the addition of sYCC601, Adobe RGB and Adobe YCC601; and an Automotive Connection System.
In this thread:
http://www.magiclantern.fm/forum/index.php?topic=6215.0
I see it would be possible to have Max resolution in crop mode 2560x944...
Just curios....
Thanks!
QuoteDoes it work the same as the 5DIII regarding the processing of the files?
Exactly the same.
QuoteDo you think a day it will possible to have uncompressed HDMI out?
Its already uncompressed, just needs to be like 5DIII and progressive. Maybe something from that new FW will help.
Quote from: Virindi on August 12, 2013, 07:29:15 PM
Just tested dual iso. That's fantastic! Thanks!
I got a few crashes after taking some photos, if you guys have any clue.
Well, if you don't post the LOG files how can people help you?
Also, describe what you were doing.
@1%:i am getting some pink in my dual iso images. I asked that question because MAYBE some of the values in cr2hdr are hardcoded to the 5DIII and thus they require some dual iso files from the 6D to be perfected.
What about video mode? I mean, if ISO is alternated every 2 lines doesn't it follow Canon line skipping or what? I thought we would have the same aliasing in video mode because the line skipping and the alternation match but i might be wrong.
Yep, a bug has to be reproducible at least. If I can't crash it, how can I fix it?
For dual iso, try a newer raw converter. The one with the package might be a bit old. A1ex said something about the packaged version not supporting 6D yet. Mine is like 9.17 on linux, there are windows binaries compiled up somewhere..
After that I guess we check the utility. I know white level on 5DIII is for sure different but I'm thinking it pulls this stuff from meta data, maybe not?
Check video mode, I haven't yet. It should have the right white level at least.
For skipping.. it still reads the sensor the same way, just 1/2 at a different iso. So you end up with the same proportion of skipped/read over the whole sensor.
But then you have to deinterlace it which will lead to half the resolution again, right?
I think you can calculate most of it back. Interlaced takes I think 1/2 for frame 1 and then 1/2 for frame 2 so more like normal HDR.
With fps override when i change between 1x and 5x modes sometimes I get false colour on display. This issue also happens sometimes when i stop record raw video.
Thanks a lot for this very good job. Dual iso is a new gift.
Can you take a shot of it? Its not zebras?
*I may have seen what you are talking about*... it corrupted for a second when I switched but didn't stick around.
I kinda want to get rid of 1x somehow... does anyone find it useful for anything?
Nope, get rid of it.
Why does it come up anyway?
I'm not sure what canon intended this mode for. It seems like it has the same timings as normal mode and the same raw size. FPS override is probably getting confused and thinks its in zoom mode. At the least I need to check/fix that.
No its no zebras sometimes pinkish or greenish. Its there i think after adtg fps override.
If I repeat zoom with the loupe button one or more times from 1x to 5x its ok. Sometimes its not only false color, also the image becomes half image. Changing from photo to video it happens also.
Fps override whatever the override mode and whatever the fps.
Anyone compared dualISO with a regular 2 expo HDR picture ?
Cause dualISO is fine, you don't need a tripod (!) but it costs in aliasing and resolution.
As read in posts, dualISO enhance pic's DR.
Anyone knows how DR can be estimated from a HDR (ISO shift, not aperture shift) of 2/3/5 pics ?
On the video side, would be interesting to test DualISO with Mosaic Engineering filter...
About aliasing mainly.
Update: Spent a few hours in Photomatix Pro, mixing 2 or 3 expo "classical" HDRs..... (ISO shift)
i never get even close to the result of DualIso....
How are mixed the 2 expo in cr2hdr ???
It's a fusion, of course, not a tone map but i sould miss something !
Someone knows ?
Hey,
I have ML(raw video version) installed (http://www.magiclantern.fm/forum/index.php?topic=5530.0) and now i want to try the dual iso version. Does anyone know if i can simply replace the ML folder and the autoexec.bin file? Or do I also have to delete the 6D000113.FIR file?
Quote from: teo770 on August 14, 2013, 05:16:08 PM
On the video side, would be interesting to test DualISO with Mosaic Engineering filter...
About aliasing mainly.
I tried but on 5D3 with VAF-6D. The 6D filter fits 5D3 physically (in terms of dimensions) but there was no difference. VAF is designed for certain type of line skipping, i believe something like 1 line stays, two lines out (so blends those non existing lines or something) Dual ISO lines are one by one dark and light so the filter cannot do anything.
It is worth to try on 6D though, Noisyboy will tell us in the next week ;)
Hi Guys
I went bike-filming with the 6D today. While Filming i found that - in replay (not in LV) - after about 25 secs, the picture starts to look like this:
seems that the lowest fifth gets way higher compressed than the rest...
[6D] AEValue2.zip | 720p | 50 fps | low Comp | SanDisk ExtremePro 95mbs-1 32G | M mode
Yes Noisyboy... give up the beach, come back to work on ML !!!
I'm with "sim3213" on this.
I also experienced this with the DualISO while filming with the bitrate set to 1, ie 10mbps.
It would happen now and then.
I am struggling with Motion Detect -> Frame difference mode. I think it was working when I first installed (http://www.magiclantern.fm/forum/index.php?topic=5530.0) , but not with the current ISO zip. Thoughts?
Confirmed Shot -> Motion Detect -> Frame Difference is working here "ML For 6D with RAW Shooting 19-06-2013" but not working with "[6D] DualIso-FullPack.zip"
This Project is incredible CHDK, and now ML. Thanks for all the hard work!
I've put 1%'s dual iso full pack ML version available to EOScard so it can download and install to your card.
Right click on ML button, choose ports in progress, then 6D 1.1.3 alpha by 1%
Wait until the download finish, then click Save.
If a previous version exists on the card remove it first (uncheck ML button, click Save, enable to delete ML files)
Download EOScard, bug report here: http://pel.hu/eoscard
First, thanks to the whole team for Magic Lantern. Fantastic.
Second, since installing ML on my 6D, I'm having problems with the camera not saving automatically created files on recordings that are longer than the maximum 4GB file size. Instead, the automatically created consecutive files are sometimes just .DAT files that read as having zero bytes. I am guessing that this is due to Magic Lantern since I don't seem to have the problem when it isn't running. I lose the entire recording, but the camera never registers the problem. I am using 64GB Sandisk Extreme cards.
Dual ISO have some problems on my 6D, when I select alternate normal and dual iso photo. Sometimes I get 2 or 3 or 4 normal photos, then one dual; or sometimes the opposite.
The name of the files captured in dual iso is also not accurate, normal photos named dual or the opposite. doesn't seem to be related to the issue I described before..
Finally, on rare occasions, the WB recorded on normal photos (still with alternate function) is really high for no reason. Not a problem since it's raw, just looks weird when you open a series of photos.
I'm with virindi in that I've also gotten normal photos as DUALS and DUALS as normal photos and that the alternative DUAL-nonDUAL isn't reliable.
I thought I was going crazy.
Gday.
A word of warning here.
I took the memory card out of my 6d to update ML on my memory cards and went to watch a movie.
Two hours later, after watching a movie, and updating the ML on the cards I come back to my camera.
I notice it's a bit hot.
I note that the on/off switch is at off.
The camera won't boot when I go to on.
i go off/on/off/on ... no boot.
I put a memory card in and go off/on and it goes on.
I check the battery level, and its got one battery at 20% and the other at 7%. When I went to watch a movie it was at 20% and 100% !! (i had a Meike grip on it)
I think that the 6d has the same problem as the 50d where you have to wait for the card busy light to stop flashing after you open the lid and before you remove the memory card.
boo. *off to charge my camera again.
where can i find a 6D dual iso build ? can someone can give me a link please ^^ cant find it anymore
Quote from: oscaroo on August 18, 2013, 01:14:13 PM
Gday.
A word of warning here.
I took the memory card out of my 6d to update ML on my memory cards and went to watch a movie.
Two hours later, after watching a movie, and updating the ML on the cards I come back to my camera.
I notice it's a bit hot.
I note that the on/off switch is at off.
The camera won't boot when I go to on.
i go off/on/off/on ... no boot.
I put a memory card in and go off/on and it goes on.
I check the battery level, and its got one battery at 20% and the other at 7%. When I went to watch a movie it was at 20% and 100% !! (i had a Meike grip on it)
I think that the 6d has the same problem as the 50d where you have to wait for the card busy light to stop flashing after you open the lid and before you remove the memory card.
boo. *off to charge my camera again.
What do you think the led flashes for?
You didn't mix it with bracketing? Maybe the key system for file prefix is a little off. Should affect everyone, I also noticed a few were IMG instead of DUAL.
Quote
Instead, the automatically created consecutive files are sometimes just .DAT files
I tried last night and got a split file.
Quoteafter about 25 secs, the picture starts to look like this:
If you loaded a config, increase the max QPs by like 2. Complex scene + 50/60P probably it ran out.
I did a quick test:
I shot 8 photos with alternate frames ON, prefix name ON. 1 3 5 7 and 8 turned out dual iso in exposure. 8 should have been normal.
For prefix: 1 3 5 8 named dual. 7 missing prefix
:)
And its hit or miss too because I shot 6 in rapid succession, 3 were prefix, 3 were not. i'm not sure if they matched but the number was right at least.
Probably not only a 6D bug. There is some conflict with named bracketing but it shouldn't matter if its off or if dual ISO changed the name first(only 1 thing can change the name at a time, if it has no key its locked out).
Quote from: JusT92 on August 18, 2013, 04:35:56 PM
where can i find a 6D dual iso build ? can someone can give me a link please ^^ cant find it anymore
Start EOScard and follow the instructions I gave a few reply before...
I found a bug with 720P and fps override, after recording finishes, it does something with timing and messes up the LV, you have to press play to get it back.
I think this is what nanotide was talking about. Its like FPS doesn't update some times when mode changes. Also happens going from 720 -> 24 and its most prevalent at exact FPS, 23.976. I never saw it from those other FPS modes.
Regarding my consecutive files bug: it is intermittent. It probably has something to do with my settings in ML of the way it is accessing the SD card. If I track it down, I will post the fix. But, right now, I wouldn't trust ML on the 6D for covering events as the file doesn't appear to be recoverable.
I've also had DualISO fail to activate sometimes.
It's intermittent when the camera wakes up from sleep and dualiso was set before it went to sleep. The first shot that wakes it doesn't have dual iso on it.
Also, Defishing is broken, it err70's Memory.c # 187 task livev_hiprio_task. lv:1 mode:3 (assert false)
Motion detect wit image diff seemed is dead. The diff square is always black.
Motion detect still works fine with expo diff.
I also had trap focus being a bit unreliable, but it could be cos i had the fisheye on it. *shrug. I'll try with another lens later.
And yes, next time I will heed the blinking light to not remove the MC.
Not enough memory to run it + modules. Maybe I'll switch it to shoot malloc.
So that works but defish never frees the memory so you lose the raw converter and stuff like that.
Hehe, we're back to that. What stopped working besides raw converter?
For now can throw it in malloc. It still never frees the memory.
Haha. Back to the raw converter win/lose.
I'm happy with defish to never work. I never use it anyway. I was demoing ML to a friend. I even had my fisheye for the spesh occasion.
When raw converter died, I don't think anything else died.
But I love my raw converter.
BTW pretty much any assert at memory.c, especially from ML tasks means you ran out of ram. Now I know why a1ex made the _allocate memory_do deal.
Okiedoke.
I have the combination of these two errors:
ASSERT: FALSE
at ./Memory/Memory.c:187, task lv_playback
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Jun18.6D113
Mercurial changeset : f9fa26941115+ (unified) tip
Built on 2013-06-18 13:49:43 by user@D610.
Free Memory : 445K + 1446K
ASSERT: FALSE
at ./ASIF/ASIF.c:486, task ASIF
lv:0 mode:2
Magic Lantern version : v2.3.NEXT.2013Jun18.6D113
Mercurial changeset : f9fa26941115+ (unified) tip
Built on 2013-06-18 13:49:43 by user@D610.
Free Memory : 445K + 1435K
From what i've read from the past few pages, we should be switching to m_alloc or something? (i have no idea what that means, haaha)
Edit: nevermind, this was frmo an old card! woops. This is my current error on the dual ISO one:
ASSERT: FALSE
at ./Memory/Memory.c:187, task menu_redraw_task
lv:1 mode:0
Magic Lantern version : v2.3.NEXT.2013Aug11.6D113
Mercurial changeset : 90a269a7cd8f+ (unified) tip
Built on 2013-08-11 18:24:55 UTC by user@D610.
Free Memory : 445K + 1473K
Both of those are memory errors, try to load less modules at a time... asif happens after the memory error when CPU is reset and patches are de-applied. I did malloc for de-fishing but there isn't enough room there for anything else atm.
Quote from: 1% on August 18, 2013, 11:15:17 PM
I found a bug with 720P and fps override, after recording finishes, it does something with timing and messes up the LV, you have to press play to get it back.
I think this is what nanotide was talking about. Its like FPS doesn't update some times when mode changes. Also happens going from 720 -> 24 and its most prevalent at exact FPS, 23.976. I never saw it from those other FPS modes.
Yes it seems the same issue, but I found it on other FPS modes. Perhaps it's necessary to set a sleep time somewhere.
Quote from: teo770 on August 17, 2013, 11:26:59 PM
Yes Noisyboy... give up the beach, come back to work on ML !!!
Haha! I'm still alive just been very busy :) Had a TV pilot, a music video, two commercials and to top it off an edit of what seems to be the LONGEST wedding video in the world and that's in the last 6 weeks alone! Can't complain though, business is finally good and it allowed me to buy kgv5's VAF filter for my 6D so now that the dust is starting to settle I can nerd out with it and ML Raw starting from Sunday! Woohoo! 8)
In regards to Dual Iso, would this really make a difference as surely this all happens
after the data is captured from the stream? Only one way to find out I guess! Got a shoot on Sunday so I'll really put it through it's paces! Started doing a few weddings which I always like to test out new ML stuff on! Was saying to Audionut, if only the couples knew that I was shooting with an experimental hack that could potentially ruin everyone's day ;) Already screwed up capturing someone's first dance with earlier raw builds like a god damn boss 8)
I'll test this sucker out and report back after Sunday! Can't wait to get my nerd on again!
Ooo! Ps. Anyone else got a problem with like all the drawing disappearing and then not being able to do anything unless you press the shutter down? Seems to happen every now and then after recording raw but no crash so no log I'm afraid.
Thanks ML
My weekend fun has been great.
Auto ETTR is great when on sand dunes, or snow as you get all the deets w/o blownouts and can later fix.
Sadly, it sometimes fails to work and this time it took me a while to make it work again after some fumbling.
Intervalometer is better than the built in time, and the take several pictures at a time feature is great for group photos and getting everyone with their eyes open.
Yay! Thanks ML.
Auto preview in raw module? It wouldn't turn on global draw, should be fixed
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/61864b3f981a8f91866849265685533eac10d37b
Need to try dual iso for video... work flow seems a bit complicated.
am I reading this right that there is an alternating dual/single iso mode?
does this mean that if I set this mode I should be able to just hold down the shutter and it will alternate between the two modes?
If so, this is fantastic!!
(if not, any chance of creating such a mode? something like switching between single ISO 3200 and dual ISO 1600/6400 for example)
It works, set it to every other shot in the module... just the prefix may be mixed up between them. So set to 3200, take a shot and then set to 1600 and the next pic should be dual iso...
Enjoying ML lots - thanks for all your efforts! I ran CHDK on my compacts back in the day and really missed the 3rd party love on the 450D.
I thought I'd post some benchmarks to add to the pool of knowledge:
16GB 45MB/sec Sandisk Extreme (not pro)
http://imageshack.us/a/img13/2299/9mxh.png
Class 10 Verbatim 32GB SDHC
http://imageshack.us/a/img821/5386/vtwd.png
Quote from: 1% on August 26, 2013, 03:42:14 PM
It works, set it to every other shot in the module... just the prefix may be mixed up between them. So set to 3200, take a shot and then set to 1600 and the next pic should be dual iso...
I was thinking in terms of continuous shooting where you don't have a chance to change settings. I was imagining something along the lines of the auto-bracketing setup, where you set the number of steps +- for the dual-ISO shot, and then it adjusts automatically from whatever ISO you have set for your single ISO shooting (ideally including the value picked by auto-ISO)
Quote from: 1% on August 26, 2013, 01:12:54 AM
Auto preview in raw module? It wouldn't turn on global draw, should be fixed
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/commits/61864b3f981a8f91866849265685533eac10d37b
Need to try dual iso for video... work flow seems a bit complicated.
Cheers 8)
any updates on having the wav/audio record with the video clip in one file (non separate)
For raw? You can record H264 with embedded audio, just don't turn on stuff like FPS override/flush rate
Quote from: 1% on September 02, 2013, 07:31:48 PM
For raw? You can record H264 with embedded audio, just don't turn on stuff like FPS override/flush rate
I am using the nightly builds and i am missing the BR controls and all the stuff.
Why?
I'm missing all the audio controls.
A1ex didn't like it so he commented it out from the nightlies.
More audio controls will happen when I figure out how to use those i2c commands/find out what IC we have in there for sure. The monitoring is really the big stinker as you already can set the input from canon. That and maybe audio shortcuts.
I recently installed ML on my 6D. It works but when the camera is carrying out automated AF dot tuning, the graphical display on the LCD goes blank. It'll show up again when the job is done. Am I the only one to experience this? Or is this behavior perfectly normal since the 6D is not fully supported?
Thank you 1%!
QuoteOr is this behavior perfectly normal since the 6D is not fully supported?
I think this is normal for afma. If you want to see the screen turn off the canon feature that blanks it when you press 1/2 shutter.
Quote from: 1% on September 05, 2013, 03:03:26 PM
I think this is normal for afma. If you want to see the screen turn off the canon feature that blanks it when you press 1/2 shutter.
Coool. 8) That works.
Would be nice to suggest it in the menu. None of my cameras have this feature though; you press INFO to turn off the display.
Probably not a bad idea. I thought all cameras without LCD sensor had the option to off the screen when you press half shutter or let it stays on, it got me when it was first being developed.
How stable is the latest release?
Last time I tried it (about 2 months ago) it crashed every 5 mins or so.
Question about downloading from the Nightly Builds instead of from OtherOnePercent/TragicLantern
Do we now download from the Nightly Build section on this web site rather then from OtherOnePercent/TragicLantern? If we do then I noticed that the dual_iso.mo is not in the build. Were do we get the current version for the 6D? Currently I downloaded it from the OtherOnePercent/TragicLantern site. Is that correct or is there a more current/updated version for the 6D?
Once again, your team is AMAZING! I need to make a more current contribution. THANKS!!!
Latest isn't compiled as I've been working on 7D. You're free to try the nightly, its not missing all that much. Dunno if the crashing is getting any better since memory is at a premium with all these modules. Recent commits I've had less startup memory crashes... but thats pretty much the only kind I've had recently.
Thanks 1%
So it looks like I can continue to download from the Nightly Build until you produce one. When you compile yours wouldn't it be the same one from the Nightly Build on that date or are they different? Sorry ... I'm just trying to understand where they are different.
Thanks again!
The nightlies for 6D from the main page are completely untested, so be careful ;)
QuoteI'm just trying to understand where they are different.
The nightly may have 1 or 2 consts left over from 112 so something like trap focus (remember fixing it) didn't work. Nothing that would cause serious problems or people would be complaining already.
Hi 1% and others!
Maybe it was already asked but anyway I have a question...I quite sure the answer is no, but:
is digic cpu capable to dng compression, maybe via script? Too slow?
Asking couse a dng at 1792x1008 is about (in my case) 3.2MB, and a lossy dng is 580KB!!!
Thanks!
It would work about as fast as the raw preview updates.
What you mean 1%? So, in theory, is it possible? Would be marvelous, I'have read that lossy dng are quite same quality
as lossless! Not shure about, but maybe it is better then sqeezed images...
How fast is the raw preview... like 5fps? Thats how fast its possible.
Hello 1%.
Here is my question: as I understand, in 6D throughput SD card does not exceed 40 MB/s. Therefore cards such as SanDisk Extreme Pro with 96 MB/s virtually useless obtained and uninterrupted record in the maximal mode is equal to 1600х600. This is due to the circuitry of the device? A limitation of the hardware? Or is it possible to programmatically work around, increasing the capacity?
Sorry for English, I write through a translator. I hope that translated clear.
Hey Kaktus.
Yeah, I think a 96MB/s card would be "wasted" on the 6d if you're recording stuff onto it.
However! downloading the data to your computer through a usb3 card reader would definitely benefit from a higher-speed memory card.
I personally hate being stuck on USB2 land and downloading photos at 20MB/s. One day i'll get my usb3 laptop, one day.
1%, I don't understand your point! My question was: If I can do 24fps continuously or not at some resolution, would it be possible take this 24 dngs and compress them to lossy dng on the fly using internal resources?
Thank you!
Quote from: Rikoshet on September 19, 2013, 11:44:47 AM
1%, I don't understand your point! My question was: If I can do 24fps continuously or not at some resolution, would it be possible take this 24 dngs and compress them to lossy dng on the fly using internal resources?
Thank you!
Im afraid your question has already been answered by 1%. And the answer is no.
Waaaaaahhh, my new 6d arrives tomorrow, and the 6d ml build is broken for nearly a week :-o ... anyone care to fix this free_space_show thingy?
make -C /cygdrive/H/SHARED/ml/ml-mod1/platform/6D.113
make[1]: Entering directory `/cygdrive/H/SHARED/ml/ml-mod1/platform/6D.113'
[ VERSION ] ../../platform/6D.113/version.bin
[ VERSION ] ../../platform/6D.113/version.c
[ CC ] version.o
make -C ../../tcc
make[2]: Entering directory `/cygdrive/H/SHARED/ml/ml-mod1/tcc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/cygdrive/H/SHARED/ml/ml-mod1/tcc'
[ LD ] magiclantern
../../src/Makefile.src:176: recipe for target `magiclantern' failed
make[1]: Leaving directory `/cygdrive/H/SHARED/ml/ml-mod1/platform/6D.113'
Makefile:18: recipe for target `6D' failed
/bitrate-6d.c:480: first defined here
lens.o: In function `free_space_show_photomode':
H:\SHARED\ml\ml-mod1\platform\6D.113/../../src/lens.c:889: multiple definition of `free_space_show_photomode'
bitrate-6d.o:H:\SHARED\ml\ml-mod1\platform\6D.113/../../src/bitrate-6d.c:506: first defined here
lens.o: In function `free_space_show':
H:\SHARED\ml\ml-mod1\platform\6D.113/../../src/lens.c:911: multiple definition of `free_space_show'
bitrate-6d.o:H:\SHARED\ml\ml-mod1\platform\6D.113/../../src/bitrate-6d.c:399: first defined here
lens.o: In function `free_space_show_photomode':
lens.c:(.text+0x24b8): undefined reference to `cluster_size'
lens.c:(.text+0x24bc): undefined reference to `free_space_raw'
lens.o: In function `free_space_show':
lens.c:(.text+0x2590): undefined reference to `cluster_size'
lens.c:(.text+0x2594): undefined reference to `free_space_raw'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make: *** [6D] Error 2
So just compile of mine or use the pre-built I just made. Main is going to be missing out on audio controls/headphone and a bunch of stuff.
Quote from: 1% on September 22, 2013, 08:54:48 PM
So just compile of mine or use the pre-built I just made. Main is going to be missing out on audio controls/headphone and a bunch of stuff.
Where's your repo and/or your 6d nightlies (sorrry if I'm overlooking the obvious)?
The reason why I want a working trunk is because my own fork with some personal modules is based on that, thus with the official builds our yours I for example couldn't use ml auto iso which I also will use for the 6d a lot because I can set min. av shutter speeds of > 1/250s.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d
Modules should be ok unless you have some xtra symbols you added. Did you pull req them to main?
Quote from: 1% on September 22, 2013, 10:01:56 PM
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d
Thanks!
Quote from: 1% on September 22, 2013, 10:01:56 PM
Modules should be ok unless you have some xtra symbols you added. Did you pull req them to main?
Yes, unfortunately my modules need some get functions for model-specific defines from the core. I once did a pull request and it was going nowhere, because where I put these functions (in a new file module-glue.c/.h) wasn't universally appreciated and I didn't have the enthusiasm to see this through.
Since then I keep mentioning that there is no commonly accepted solution what to do with model-specific variables and if these functions will be accepted into the core even if only one 3rd party module uses them... I hope once module mature this problem will be addressed.
One more question before I'll be bold enough to try to put this repo onto my new 6d (I cannot help but to ask): Is the 6d release as stable as the main dev trunk? i.e. were there any backend changes that affect stability other than plain feature porting?
I'm asking because some people just had a near death experience with the 60d - a recent trunk change introduced a memory bug that was only caught by ml's built-in safety net - see here: http://www.magiclantern.fm/forum/index.php?topic=8473.msg78027#msg78027 ... it's a bit like the old movie-remap which turned out to be brick-risky :-o
Is the potential of the Tragic Lantern repo to brick my camera larger than say the recent 5d3 builds? I have to admit I'm rather nervous here, I've been running ml on my 60D for 3 years even when the port was very fresh, but I don't want to use a port with known stability issues.
As I'm currently in the middle of porting some changes from Tragic Lantern, here's my detailed code review, based on this diff (http://a1ex.magiclantern.fm/bleeding-edge/tl6d.patch) (ML 4b3129d vs TL 7a5ccc6). I hope it answers the questions about safety and about the differences between TL and ML.
Cool stuff - this will get merged sooner or later
- various features (dual ISO, raw overlays, ResLock) ported
- stubs/consts updated
- advanced HDR video updated for new menus
- installer fix for new cameras
- FPS timer tweaks
- bracketing prefix (this is my code, I just didn't fully test it)
- some little bugs caught (e.g. EOS M menu not working while recording, or debug messages forgotten in the Protect/Rate shortcut)
- EOS M updated to 2.0.2
- 50D FPS warning
Major concerns:
- In many places, Canon error checking code is disabled (examples: beep.c (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/tip/src/beep.c#cl-1118) or bitrate-6d.c (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/tip/src/bitrate-6d.c#cl-137), especially the second one). This is a no-no for me, and it's like running with a bike downhill at full speed without brakes. Just try understanding that code if you don't believe me.
- ROM backup (which g3gg0 created so we can unbrick the cameras if something really bad happens) is commented out:
+#undef CONFIG_AUTOBACKUP_ROM //WTF, Batman?
Okay, I know we never actually used this, but who knows?
- The stability tests from ML (which I wrote, and ran them hundreds of times), were disabled without reason:
+#undef CONFIG_STRESS_TEST // Not Needed
- Movie mode remap (which I know it's dangerous (http://wiki.magiclantern.fm/faq#what_happened_with_movie_mode_remap), because I've soft-bricked my 60D with it) it's enabled here.
- GUI timers are completely disabled (FEATURE_TIMER_HACK). I'm OK with slowing down the refresh rate, but completely disabling them isn't safe IMO.
- Some debug tools that I consider dangerous and were written for developers only (DIGIC poke, prop browser, dm/tp intercept) are enabled in TL builds (so users without proper knowledge have access to these tools, and they shouldn't IMO).
- Picture quality hacks (SRAW, MRAW) are included. I've bricked my 5D2 with wrong picture quality settings (ERR70 even without ML). I've unbricked (http://magiclantern.wikia.com/wiki/Unbricking) it successfully.
- Error handling in bitrate code is done by rebooting the camera in the middle of recording! (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/src/tip/src/bitrate-6d.c#cl-703)
Minor concerns
- raw_rec also records in photo mode (it shouldn't (http://www.magiclantern.fm/forum/index.php?topic=5888.msg42850#msg42850))
- boot methods changed (any reason?) [OT: remember the early days of 6D when ML was running without even allocating memory for it?]
- no checks before patching Canon code
- code changes are very hard to follow (very short commit messages, often the commit alters totally unrelated stuff, changes that do nothing but add commented code)
- ML warnings are disabled (hint: some people are under the impression that Tragic Lantern is actually a stable release (http://www.magiclantern.fm/forum/index.php?topic=3648.msg77412#msg77412)):
+#define FEATURE_NOHELP //No one can help you now
Neutral
- some more things optimized with -O3 (can anyone show the difference, maybe with a video?)
- new peaking (I feel it's too slow, and the bug reports I've received from 5D3 alpha were enough for me to disable it until the code will be optimized)
- dma_memcpy
- uniwb (my old code, nothing wrong with it, it was useful when we didn't have raw histogram, but now it's no longer needed)
- REC_ON_RESUME and MOVIE_AUTOSTOP_RECORDING: these should be done with scripting (yeah, I know, somebody should revive the scripting engine first)
Not reviewed (some of these things are cool, but I just didn't take a closer look):
- video hacks
- feature additions to raw_rec
- mlv_rec (it's on the todo list, but it's very complex)
- audio
- QEMU changes
- a lot of stuff in debug.c that is impossible to understand
Conclusion: personally I'm afraid to run Tragic Lantern on any of my cameras. Sure, I don't remember anyone bricking his camera with TL code, but I've learned about some dangerous things the hard way, by bricking my own cameras (and then learning how unbricking them). Of course, you should not trust me blindly, you should review the code on your own (even the code from the main repo).
Sorry if I sound like bashing or underestimating the contributions from 1%. I've just tried to do an objective review of Tragic Lantern, especially regarding code safety, and I've tried to back every argument with a link or a code snippet. These are the main reasons TL code didn't get merged into main repo; I've pointed them out many times, but the issues were not solved, so a little reminder shouldn't hurt.
Now, I have to admit I don't have a better solution. The main repo for 6D (and other cameras, e.g. EOS M) was not touched for months, so it's completely untested. I can't help with that, because I don't own these cameras, and I already have too many of them). I just want people follow some really basic development guidelines (http://www.magiclantern.fm/forum/index.php?topic=3624), and submit their changes to the main repository, where they will be subject to code review from me, g3gg0, nanomad and many others - both devs and nondevs). Now, the entire 6D/EOSM/7D development is done in a fork where the core ML developers have absolutely no influence, and most people are not aware of that.
Quote- The stability tests from ML (which I wrote, and ran them hundreds of times), were disabled without reason:
After completing the test successfully, why keep it. Just added bloat.
Quote- Movie mode remap (which I know it's dangerous, because I've soft-bricked my 60D with it) it's enabled here.
Only useful on 600D, other cameras its pointless. i.e Softbricked 60D. 50D the modes don't support LV.
QuoteML warnings are disabled (hint: some people are under the impression that Tragic Lantern is actually a stable release):
I'd tried running with the warning it just got too naggy. I don't need to be reminded with popups every day. And what is the solution? Not use ML? The only one without is technically 2.3
QuoteCONFIG_AUTOBACKUP_ROM
The files it produces are not a great backup on many cameras, some parts of the rom are doubled.
DIGICV/IV have different addresses. I wouldn't flash this stuff back.
QuotePicture quality hacks (SRAW, MRAW) are included. I've bricked my 5D2 with wrong picture quality settings (ERR70 even without ML). I've unbricked it successfully.
It only has these modes on 600D. Other cameras either have SRAW/MRAW or it just doesn't work.
Quoteboot methods changed (any reason?) [OT: remember the early days of 6D when ML was running without even allocating memory for it?]
The reason was 640K bins... EOSM/6D are the main changed boot deals. 5DIII is lucky with the giant malloc. They are already booting with cache hacks, just with bigger bin space.
Quoteno checks before patching Canon code
A BL isn't going to change, nor is the position in rom. Its ifdefed to only run on the camera it belongs too.
Quote- Error handling in bitrate code is done by rebooting the camera in the middle of recording!
That error is funny, resource manager doesn't want to start recording and leaves the camera in a "busy" state where the only other option is a battery pull. You're not in the middle of recording anything, it doesn't write anything but a blank dat file. Usually its from pressing rec too fast before the config fully loads. I kinda want to find this one and fix it.
Quote- uniwb (my old code, nothing wrong with it, it was useful when we didn't have raw histogram, but now it's no longer needed)
Uniwb for video, esp raw video is nice. Leaves the WB for post but you still get to see some of the color in your image.
Quote- code changes are very hard to follow (very short commit messages, often the commit alters totally unrelated stuff, changes that do nothing but add commented code)
Thats just testing stuff from things I tried, more or less notes for me. Same for debug.c, its just reverse engineering testing.
Quotebut completely disabling them isn't safe IMO.
The worst it does is graphical glitches. Saves 50D/7D/5d2? silent pic bursts, otherwise you get massive pink frames.
Quote+#define FEATURE_NOHELP //No one can help you now
Yep, ripped out the help system, the instructions aren't updated and you get a nice 10kb or so of bloat.
QuoteNow, the entire 6D/EOSM/7D development is done in a fork where the core ML developers have absolutely no influence, and most people are not aware of that.
There are some things which would benefit from code review... ie a clean fix for audio IC read/write on digic V where a better coder would have an easier time fixing the warnings.
Quotebeep.c
No wav without patching out the state machine. On EOSM this doesn't work. Canon really didn't want asif use on digic V. I guess they don't want a camera that doubles as an audio recorder. They're touchy about the audio monitoring too.
QuoteI have to admit I'm rather nervous here, I've been running ml on my 60D for 3 years even when the port was very fresh, but I don't want to use a port with known stability issues.
I don't just write stuff that will brick your camera wily nily, I try it on the one here first. So far haven't had a single brick. The biggest danger is crashes but people have been running it on their pro shoots and not having too many issues or they would have complained loudly by now. Only thing thus far have been crashes or user error. Thats why I say test it first before you go and depend on it. Main hasn't been perfect with this either.
Well 1%, alex. As an user, I've been compiling and intensively using the magic lantern unified branch for 550D, and the tragic lantern branch for 6D for a lot of months, and I only can say that stability never be an issue in none of them. It's indeed astonishing, because of continuous changes on the code that arised almost every day, and the reverse engineering nature of designs.
Risks, if there are, were primarily related to my own experiments with the code :-(
What I believe is that it's a pity, the fact that there are not a consensus between you two, to unify the two branches. Perhaps you need to accept the point of view of the other in some items, a posible way for that it's refactoring some things in 6D as modules (birate...?), I don't know but I think it will be a great benefit for the project.
I want to encourage you to reach that consensus.
Whatever happens, I have only thanks to both of you and all the team of developers and testers.
Quote from: 1% on September 23, 2013, 05:31:42 PM
I don't just write stuff that will brick your camera wily nily, I try it on the one here first. So far haven't had a single brick.
Not to be misunderstood: I wasn't implying you don't test your fork, not at all! My curiosity was just based on seeing that your 6d repo has moved further away from main as I expected, at first I thought it'd be just the usual number of test commits that are regularly dispatched to main - thus the question about the stability, it's marked as "dev kit" after all.
I cannot comment on the dev specifics, but I'd also suggest to enable the ml warnings in the binary releases you distribute to avoid confusion about the dev state - personally I also disable them in my local compile because I know I'm compiling trunk, and so can you on your own camera?
Quote from: nandoide on September 23, 2013, 08:06:02 PMWhat I believe is that it's a pity, the fact that there are not a consensus between you two, to unify the two branches. [...] I want to encourage you to reach that consensus.
I can only concur, forking is great and the basis of distributed sources, but the main focus should lie on re-merging changes to be able to get one trunk... wherever that is. Until I looked closely, I didn't realize the main 6d code is outdated, currently it's even completely broken.
The specific list of issues seems like a great way to sort out concerns, either in this thread or via pm - I'm always willing to listen to alex since he has so much experience with the code, but I am happy to see 1% is also putting a lot of thought into this - that's because imho the most important thing is never to brick cameras, though of course crashes are to be expected and can be fixed by removing the battery, I'm used to this :-) ... don't forget the main fud with ml out there seems to be that it's a "hack" and "dangerous", so no need to feed this misinformation.
Also, if there should be any hierarchy problems like who has access to what and who gets to decide what the only way to solve this is to openly discuss any concerns, either the dev group or with all users, I'm absolutely sure we're all on the same side here. So I'm eager to see how the 6d development progresses, looking at the popularity of the 6d it's a very important platform for the continued success of ml!
Quotebut I'd also suggest to enable the ml warnings in the binary releases you distribute to avoid confusion about the dev state - personally I also disable them in my local compile because I know I'm compiling trunk, and so can you on your own camera?
You turn them off... so does everyone else who compiles. I see no need to nag users who read the guides on how to get it working and know the implications of rolling release. The L.C.D will not read any warnings, they don't even read instructions. I see them as valid if the downloads were on the main page but they are in the forums so I'm assuming they are *somewhat* familiar with ML and everything else. I can see the warning coming up once on first run, that would be OK, but it comes up way too much. Nobody needs to be reminded every day or every few power ons or worse yet have a shot blocked/hindered by the popup. I run the same exact thing I release (+/- some commits), for photos it really needs to be up and running quickly or the shot is gone and frowns all around.
Why punish the users while disabling it for yourself? Because they didn't want to download a few 100MB of toolchain to obtain 2MB of binary?
Would you want your linux distro to do this every start up or every update? I've seen those updates down production servers. People who rolled them out without looking were sorry afterwards and never did it again without testing. Basic computer stuff.
Everything since 2.3 has been tested in place, one would hope until 2.4 people will understand rolling release didn't get the same 100s of hours of testing that a full stable release did.
The main issue here is that development takes place in a fork that went far away from the mainline, without any code review, and people have no idea what they are running on their cameras. Of course, it stays up to date with the mainline (and that's a good thing), but the reverse doesn't happen (so the knowledge is shared mostly one way, and it's supposed to happen in both directions).
Normally, fork authors submit their changes to mainline via pull request, we review them, point out stuff that can be improved, and merge them. Here I've tried to import the changes from 1% a few times, but it's a lot of work because of huge diff and changes difficult to follow, and there are major technical issues in the code, as I've pointed out earlier.
Now, the nitpicks:
- stability test: the backend is changing, so these tests may point out some problems that are hard to notice in actual usage
- remap: if it worked for you, but not for me, it doesn't mean it's safe to use; you are creating a mix of movie mode with settings from the mode you come from, and that mix is out of control.
- ROM backup: can you show a specific example where they are wrong? Covering a 8MB ROM twice isn't a problem, it's just for code simplicity (one size fits all).
- checks before patching: you have so many of them in the code that it's impossible to tell if all of them are correct or not. What I'm telling you is to let the computer catch your mistakes. It's also for other people that may play with your code. I did a single code patch in raw_rec, and the checking code was triggered (there's a screenshot in the 7D thread).
- error handling: I'd rather print something like take the battery out. Properties are a touchy area, as you know.
- help: if the instruction are not updated, why not update them, instead of removing them completely?
- beep: I'm sure we can find a cleaner solution.
About code safety: of course, things working on your camera it's a good thing, and nobody denied it. But if some things can result in random code execution, even if the chances are like 0.001%, and I point them out, why refusing to do something about it? Instead, you are simply dismissing my remarks.
A recent example: I've asked you to run some test code on 50D (http://www.magiclantern.fm/forum/index.php?topic=5586.msg76991;topicseen#msg76991), because FIO code stopping in the middle of reading a file is a major issue IMO (it's likely to indicate a bug somewhere else), and you dismissed it with "I don't care". Enough said.
Don't forget that we are running without a MMU unit, so a mistake in our code can overwrite Canon code or data structures. The reverse is also true - g3gg0 and me have patched a Canon bug that was overwriting ML code on many cameras. So, a little extra care doesn't hurt.
Regarding warning: of course, a lot people don't read instructions, as you said, and this is why they should get something that is less likely to contain dangerous options. If they want some bleeding edge stuff (e.g. advanced bitrate control), and they understand the risks, you can point them to your fork. Maybe we can create a separate forum area for forks, so it no longer causes confusion.
But right now, the mainline development was abandoned, there was no attempt from you to merge your changes into mainline (I've been trying to do that myself, also nanomad, but we had difficulties), and people are running your fork thinking it's the mainline, while that fork contains stuff that I consider dangerous.
This is not nice.
Quote from: 1% on September 23, 2013, 10:19:53 PMI can see the warning coming up once on first run, that would be OK, but it comes up way too much.
Well, so there's your solution - just add a version tag to the config file and enable the warning only once per build!
Of course the warning is tiresome for a lot of users, but as in "better safe than sorry" and "We told you so" it's made for people who are pointed at the "How to install ML" thread from somewhere else & just skip all warnings like we ignore health warnings on our favorite food items :-p ... I also directed people to the forum to the 6d port because I knew it was more mature than other early ports, but there still should be a difference to a "stable" version. But I think the one-time warning per trunk tag could be a consensus?
Quote from: a1ex on September 24, 2013, 07:55:27 AM
The main issue here is that development takes place in a fork that went far away from the mainline, without any code review, and people have no idea what they are running on their cameras. Of course, it stays up to date with the mainline (and that's a good thing), but the reverse doesn't happen (so the knowledge is shared mostly one way, and it's supposed to happen in both directions).
I don't want to get between people, but I can understand some frustration can be generated by such a situation if there is no timeline or understanding when a re-merge will happen and who has to sort out incompatibilities. The nitpicks alex mentioned seem to be not that many, and if he from his experiences thinks these are serious issues I don't see any reason for not enabling these safety measures, even if some other people think they're not necessary?
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- stability test: the backend is changing, so these tests may point out some problems that are hard to notice in actual usage
Sounds reasonable to me...
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- remap: if it worked for you, but not for me, it doesn't mean it's safe to use; you are creating a mix of movie
mode with settings from the mode you come from, and that mix is out of control.
I was very disappointed when alex pulled the "movie mode remap" feature from trunk, but in hindsight as a user I have to say I'm very happy he's that determined on catching every small bricking possibility.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- ROM backup: can you show a specific example where they are wrong? Covering a 8MB ROM twice isn't a problem, it's just for code simplicity (one size fits all).
Ok, 1% doesn't think it's actually working, but it doesn't hurt, so why not just enable it? This is about reaching an understanding, and this certainly doesn't seem to be a crucial point.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- checks before patching: you have so many of them in the code that it's impossible to tell if all of them are correct or not. What I'm telling you is to let the computer catch your mistakes. It's also for other people that may play with your code. I did a single code patch in raw_rec, and the checking code was triggered (there's a screenshot in the 7D thread).
Ok, this is a serious code architecture difference, I hope both a consensus can be reached here, I wouldn't want to comment right now. But this shouldn't be a reason for permanent forking.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- error handling: I'd rather print something like take the battery out. Properties are a touchy area, as you know.
Me too, even though I'm quick at taking the battery out by now :-p ... but back when I first started using ml I nearly had a heart attack every time if my very, very expensive dslr just froze.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
- help: if the instruction are not updated, why not update them, instead of removing them completely?
Hmmyes, I have to admit since since there is no one around to update the help text, it probably doesn't matter to 404 all of them or remove them - when (and if :-p) someone is found to write the texts for the next "stable" - if that should ever happen - re-patching them in won't be a probem?
This is esp. since there seems to be no schedule or idea about further ml "releases", are you going to branch a stable and only bugfix, will it be rolling releases only, or will it be the Linux model with a merge window and then bugfixing/testing only for a certain time? But of course this is an issue for another thread.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
About code safety: of course, things working on your camera it's a good thing, and nobody denied it. But if some things can result in random code execution, even if the chances are like 0.001%, and I point them out, why refusing to do something about it?
I wouldn't know about probabilities, but when alex recently messed up the code I was very happy the error was caught rather than bricking my camera (or crashing it) - so +1 for safety nets, and publicity-wise ml bricking or freezing is very bad since this is what a lot of fud is about.
Quote from: a1ex on September 24, 2013, 07:55:27 AM
Maybe we can create a separate forum area for forks, so it no longer causes confusion.
I still am positive that you guys sort this out and a re-merge will happen in the near future! Meanwhile, if TL remains a fork and not just a branch in the main repo, to avoid confusion that doesn't sound like a bad idea so responsibilities are sorted out. I for one didn't realize there were any differences between the 6D port and the rest of ML I'm currently running on my good ol' 60d.
Quote from: a1ex on September 24, 2013, 07:55:27 AMBut right now, the mainline development was abandoned, there was no attempt from you to merge your changes into mainline (I've been trying to do that myself, also nanomad, but we had difficulties)
What I don't quite understand right now, maybe someone can enlighten me: How did this happen at all? Is TL intended as a real, permanent fork, or is the intention to first develop a complete 6d port and then re-merge, or was more often re-merging with trunk hindered by some problems?
Since this is GPL nobody can do anything about a (semi-)permanent fork, but without very good reasons this is always a pity and sub-optimal from a user's perspective in oss - as I'd be running *two* different ml distros on my cameras, ML on 60d and TL on 6D which makes putting my own patches into them very tiresome and makes it much more difficult to report bugs and test features.
как установить [6D]Audio_Controls.zip, МЛ 1,1,3 уже установлена, это новое обновление нужно просто скопировать на флешку, или ее нужно прошить 6D000ML.FIR ?
how to establish [6D]Audio_Controls.zip, to ML 1,1,3 it is already established, this new updating needs to be copied simply on a flash card, or it needs to be stitched 6D000ML.FIR?
Quote from: NikeFreak on September 24, 2013, 11:42:17 AM
how to establish [6D]Audio_Controls.zip, to ML 1,1,3 it is already established, this new updating needs to be copied simply on a flash card, or it needs to be stitched 6D000ML.FIR?
The ML .fir is *only* required *once* to enable using ml at all - from then on, just copy the appropriate files, mainly autoexec.bin & the modules to the card.
Quote from: Marsu42 on September 24, 2013, 12:08:12 PM
The ML .fir is *only* required *once* to enable using ml at all - from then on, just copy the appropriate files, mainly autoexec.bin & the modules to the card.
я это знаю, просто не понял зачем тогда положили в эту сборку fir файл.
I know it, simply didn't understand why then put in this assembly fir the file.
Its there if someone is a first timer and needs to boot flag/remove the boot flag.
The movie remap on 600D was the reason for the fork. It was working great there and still is for 2 years. On everything else it mostly doesn't. Its not enabled on any other camera for that reason.
For help, you just comment out FEATURE_NOHELP and they're back.
I agree that stuff should be merged back, ie 7D display filters. Some stuff like that is easy to port back from the source. Some stuff like audio controls, yea, it would be harder to find all of the pieces.
TLDR: I need to figure out pull requests.
I do run the stability test every once in a while... I just don't put up bins with it enabled.
Main thing that keeps me from working on merging is that I port/build/test changes coming from main or work on something new instead. My programming is pretty simple, didn't think anything was hard to follow, esp for a more experienced coder.
Quote- beep: I'm sure we can find a cleaner solution.
I hope so, it was meant to be a temporary thing and needs to be done for EOSM, that solution should work for 6D too. EOSM/650D will need it too since audio controls can now be done for it.
QuoteInstead, you are simply dismissing my remarks.
I'm not dismissing anything. I just never got to it :( The flip side is when something is broken by main I also have try to figure it out with usually little help ie. 7D master stuff right now or voice tags being broken... I didn't apply set unpress fix on 7D and its broken there right now
QuoteCovering a 8MB ROM twice isn't a problem, it's just for code simplicity (one size fits all).
Don't digic V and digic IV have the rom on different addresses? At the least rom1/rom0 are flipped at the worst its backing up garbage.
Quoteerror handling: I'd rather print something like take the battery out. Properties are a touchy area, as you know.
True, I just did the reboot since nothing else worked, I can set it up the other way, its not a big problem for me (comment out one line), I want to solve the bug so it doesn't happen.
QuoteMaybe we can create a separate forum area for forks, so it no longer causes confusion.
I would hope they can figure this out, the name is different, you've explained it 100 times like this. Its not on the main page even. Some people still don't read.
Quote
This is not nice.
I'm not trying to be a pain in the ass. My main goal is to have working bins for these cameras that people enjoy.
Just reproduced the voice tags bug, SET is getting trapped by the "moving spotmeter" feature. Will fix.
For bitrate error, if it's caused by loading the config file in the middle of recording, you could just skip loading it if you already started recording. If this is not enough, try locking the buttons (ui_lock) while loading the config, so you can't start recording with incomplete configs.
I added MSLEEPS, will try UI lock and see if it goes away.
Thanks, so far its gone, knock on wood.
Ok, since with my new 6D I again discovered how unusable the camera is w/o ml, I boldly put 1%'s port on it, and (knock on wood) everything works fine so far - apart from one crash and some assert logs, that is. But thanks a lot all for making this work on the 6D, ml being not available prevented me from buying it earlier.
Question 1: Where do I post bug reports for the 6D: In the main repo bugtracker or on 1%'s bitbucket repo?
Question 2: 6D related feature requests still go into the Magic Lantern forum, even though the work is currently being done in the Tragic Lantern fork?
Quoteapart from one crash and some assert logs, that is
You can post bug reports here or in the repo for it. What crash tho?
Quote from: 1% on September 24, 2013, 07:48:10 PM
You can post bug reports here or in the repo for it. What crash tho?
I deleted the crash log, sorry - it was in raw.c and had something to do with me trying raw ettr & raw_rec - I'll try harder next time to give a proper report :-\
I had some assert logs with ETTR on 5D3 (I know I had it on SET button in LiveView), but I couldn't reproduce them. So, if you get these errors again, I'm interested.
The too many requests for raw_lv error? That is what asserts with ETTR... I thought that bug was gone :(
Yeah, that one. How to get it?
For me it happened on cold boots, hitting set for it to go into live view. It opens/closes real quick and gives up/asserts.
ML ASSERT:
raw_lv_request_count >= 0
at ../../src/raw.c:1368 (raw_lv_release), task livev_hiprio_task
lv:0 mode:3
Magic Lantern version : v2.3.NEXT.2013Sep24.6D113
Mercurial changeset : 18cfee2de867+ (unified) tip
Built on 2013-09-24 16:55:44 UTC by user@D610.
Free Memory : 380K + 1828K
Cold boot half shutter double click, almost every time.
Narrowed it down, if AF is on and it afs a little then you get the error.
Nope, still can't reproduce (5D3, 50/1.8, M, AF on halfshutter, ETTR with SET or halfshutter double-click, cold boot, all fine).
Just merged some changes from TL into mainline. It's still work in progress, as I've merged mostly the easy part (what was pretty obvious). Will continue tomorrow.
I've updated the official nightly builds (http://builds.magiclantern.fm/) too (but didn't try them, obviously). Can you check if it actually works?
Nightly is working and not doing anything bad. I think audio remote shot might not be working because audio controls aren't in.
You think a DM log would help? I can log and wait for a couple of the asserts ( i see them flash the LED).
Excellent work guys! I just found this discussion and wanted to say that:
1brain + 2 brains + ... nbrains = MLbrains
Find a way to make sure this little equation remains true.
I love your work and I am happy to see that you are working towards a bigger joint MLbrain!
Where do you want crash/assert logs posted - here or in the bug tracker? Is this helpful at all without a detailed way to reproduce it (which I am not likely to provide, I'm not keen on *deliberately* crashing it, and it seems the crashes occur with me not doing anything extraordinary)? Here's a sample from today:
ASSERT: 0
at Stub.c:29, task CtrlSrv
lv:0 mode:2
and this crash twice:
ASSERT: FALSE
at ./ASIF/ASIF.c:486, task ASIF
lv:0 mode:2
all from
Magic Lantern version : v2.3.M42.ml1p6d.2013Sep24.6D113
Mercurial changeset : ef54670e2db6+ (unified) tip
Built on 2013-09-24 10:22:59 UTC by USER@HARRIS.
Free Memory : 352K + 1967K
I've seen the ctrlserv one before, but not sure how to reproduce it either, after that the asif patches get taken off with the CPU reset and it beeps.
I've been testing the nightly build of 6D an I found:
1) raw_rec Small hacks don't work. "Hack Error on screen expected xxxxxx, obtained yyyyyy". Tragic Lantern compiled version is OK (well, no error on screen).
2) fps override 18 fps on 24 1920x1080 IPB video mode, for example, High FPS for example, high shutter speed < 1"/800, when I change from 1x to 5x, sometimes image on "false color" (see example images on URL). Changing modes, image recovers, then no big issue. The problem arises in callings to function set_lv_zoom . The problem is most important when activating memory hack in raw_rec or mlv_rec, because callings to ResumeLiveView that calls itself to set_lv_zoom. Then sometimes when start recording the image gets "false color" and record is KO.
As a workaround I modified raw_rec calling fps_disable and fps_enable before and after calls to ResumeLiveView. It works but it's ugly and frames 3 and 4 are overexposed (perhaps because fps_enable is not instantaneous).
The issue is on ML and TL versions.
https://www.dropbox.com/sh/0s7ayi40o6w4ted/fvPZXHrIZt
That makes sense, the problem is its not catching mode changes and applying zoom/different mode timings to the wrong mode. If you go back to the mode it thought it was in, the image will be right.
Also another great way to get messed image:
Leave autoexpo on, it will expose right when the lv is paused.
Ie. you set iso 6400, it sets iso 128k when doing the memory hack and your shot is shot.
Question concerning usability: Can ml catch the START/STOP key and tie lots of useful functions to this virtually unused key just like M.fn on the 5d3 behaves?
EDIT: Answering my own question: No, obviously not, it just throws a 54 gui event :-\ ... but still the RATE function in play mode should go somewhere, after all the 5d3 has a dedicated button for it so it's really missing on the 6d!
Rate works from play mode. I dunno how its not working for you.
Don't know if this has been covered, but undercranked 720p @ 23.978 fps raw looks sharper than 1080p H.264 (with VAF filter) and records continuously @16:9.
It has very little rolling shutter (less than half from my initial tests).
It has much higher latitude with the colors. Basically looks like film.
Pretty cool, good job guys. You have my thanks.
Quote from: 1% on September 25, 2013, 10:26:22 PM
Rate works from play mode. I dunno how its not working for you.
Wa-whaaaat? However do you do that - could you please describe the steps? Here's what I do: Enable rating in the ml config, go into play mode with the lower blue button, press START/STOP - result: nothing.
Image review -> lv button -> rate
Press play, press start/stop, says rate +1 on the screen.
Quote from: 1% on September 26, 2013, 09:56:22 PM
Press play, press start/stop, says rate +1 on the screen.
A-ha, now I've got it - it only works if lv is enabled, obviously ml doesn't catch START/STOP outside lv :-\ ...
... well, better than nothing I guess, but I hate enabling lv, flipping the mirror, exposing the sensor & draining the battery just for this (I usually take a lot of time reviewing the images) - maybe we should add an option to tie rate/protect to another button that does work outside lv?
Edit: Can you tell which of the existing buttons do send gui events outside lv? I'd like to know because I'm currently working on an "outside lv" hotkey module.
It works outside of LV... but now protect image is not.
1%, is it possible to add functionality to AUDIO menu, at least "selectable input source"? It is very usable feature.
Quote from: Marsu42 on September 26, 2013, 10:18:45 PM
exposing the sensor & draining the battery just for this (I usually take a lot of time reviewing the images)
In playback mode, the sensor is not exposed (this is how I found the key to implementing powersave in LV), and afaik it does not need any power to keep the mirror up (hint: some crashes will leave the mirror up and it will go down at next reboot).
Leave the camera in playback (outside LV) for 10 minutes, then read the battery life estimation from Debug menu, and then do the same thing in LiveView's playback. Then post the results; they should confirm or invalidate my theory (I didn't try).
so what ended up getting merged and what is left to merge?
Quote1%, is it possible to add functionality to AUDIO menu, at least "selectable input source"? It is very usable feature.
The audio stuff is in the last bin. I ended up reverting edmac wav tho because it had problems outside of LV.
any chance to unlock Aperture priority mode in video ?
Hi Guys, Anyone having problem with H.264 low fps? I tried using this feaure for timelapse but I get lots of dead pixels. And after recording everything goes white. Need advice please.. :(
что нового в этой [6D] WavTemFix.zip сборке?
what new in this [6D] WavTemFix.zip to assembly?
I just discovered that ISO_ADJUSTMENT_ACTIVE is not working, with the comment "That Function is dead.".
Does this mean there is no known way to detect Canon AutoISO on the 6D, or does it simply mean nobody has yet taken the pain to search for the correct memory address / function on the 6D? I need this for the auto_iso module.
https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/issue/18/iso_adjustment_active-is-dead
Canon AutoISO is lens_info.raw_iso == 0. The above constant is about the ISO adjustment dialog (when you press ISO and a box pops up).
I use it in a few places, so it's a good idea to find it. Should be true when the dialog is active (LV or photo), and false if not.
Quote from: a1ex on October 06, 2013, 04:25:15 PMThe above constant is about the ISO adjustment dialog (when you press ISO and a box pops up).
Unfortunately this is exactly how I use it :-\ ... because as I've just discovered:
* (ISO_ADJUSTMENT_ACTIVE && !lens_info.raw_iso) means that the iso button is pressed on "A"
* (ISO_ADJUSTMENT_ACTIVE && lens_info.raw_iso) means that the iso button is pressed on any numerical iso value
I use this to quickly enable/disable the auto_iso module w/o entering the menu and to completely replace Canon Auto ISO, it works great on 60d, but on 6D as stated ISO_ADJUSTMENT_ACTIVE always 0.
Also, I have not the slightest clue on how to find these things, so It'd be really great if 1% or someone else could attempt it :-o
Love the build for the 6d. One thing that is missing is the magenta/green shift icons while in live view. All I see is kelvin. Its easy to forget that its shifted sometimes!
I think you need to ask in the new info bars thread for that :)
QuoteI use it in a few places, so it's a good idea to find it. Should be true when the dialog is active (LV or photo), and false if not.
Is it really changing on 5DIII? On 6D this location is always 0 and xrefs to the same spot as 5DIII/600D/etc. It actually caused bugs when enabled
Yes, both LV and photo. It doesn't react to other Canon dialogs.
How does your dialog look? Mine is a rolling strip and 7AAD0 (thanks marsu, I memorized it now :) is always 0.
http://www.adorama.com/alc/files/73d0b2132d5fbfde5f83fc5ccb47d931.jpg
In LV it looks similar, just transparent.
Quote from: 1% on October 08, 2013, 04:47:23 PM
How does your dialog look? Mine is a rolling strip
The rolling strip of the 6d is a real pita if you ask me - good thing I nearly never use this menu to set anything :-p
Quote from: 1% on October 08, 2013, 04:47:23 PM
How does your dialog look? Mine is a rolling strip and 7AAD0 (thanks marsu, I memorized it now :) is always 0.
Maybe we could ask Canon not to rush their firmware and fix this in the next update... it's really annoying, I am still working to get around this in the auto_iso module & I didn't find a reliable replacement yet...
That looks like the classic dialog.
6D looks like this:
Maybe you can try with get_current_dialog_handler()?
I think I tried that when I was removing it long ago. Nada
The 6D ignores lens_set_rawiso() if it's out of bounds of the manual iso limits in the Canon menu :-o ... I expected the Canon fw to set an in-bounds iso, but it simply does nothing.
Is there an equivalent to auto_iso_range on 5d3/6d that enables me to get the min. & max. values for "ISO speed range" form the Canon menu?
If so, lens.c could be amended with a function lens_set_rawiso_coerce() that forces the requested iso into Canon bounds.
It should be in LVAE_ISO_HIS.. also check the min. That's where the auto iso range is.
Quote from: 1% on October 09, 2013, 07:41:59 PM
It should be in LVAE_ISO_HIS.. also check the min.
Nope, at least not by using the autoiso method (LVAE_ISO_HIS && 0xFF) and (LVAE_ISO_HIS >> 8 ) ... LVAE_ISO_MIN also doesn't work. Also when using the memory browser (I used it for the first time :-)) to look at the LVAE_STRUCT 0xc4d78 -> LVAE_ISO_HIS 0xc5266 is only see blank memory with all 0...
Sorry if I'm doing it the wrong way, I really like to try to discover these for myself and be of help but I'm not used to finding these things on my own (yet).
I believe these are some properties. 5D3 behaves the same, it refuses everything outside Canon range.
The routine from Expo menu simply tries them all, until one succeeds.
Edit: on 5D3 it seems to be 80040033, uint8_t data[4] = (uint8_t*)buf; data[0] is max iso, data[1] is min iso, data[2] is 1 with isos astronomicos, 0 with normal ones.
Quote from: a1ex on October 09, 2013, 10:23:23 PM
The routine from Expo menu simply tries them all, until one succeeds.
A, well, that's a method, too :-> ... I hope 1% finds the 6d version of these min/max iso values, he seems to be about 1000% better at that than me.
Its not in that struct any more.. its somewhere like offset 0xee around 0x81A90/81A88, I have to look at the decompile to see where.
I also rechecked the other offsets and they are good.
Quote from: 1% on October 09, 2013, 11:57:48 PM
Its not in that struct any more..
Great you're having a look at it, getting these values and a "proper" way to choose an working in-range iso value would be really nice. Obviously Canon did some more changes than just to replace the old-school iso menu to the new 6d iso stip (it's also on 70d, I just had a quick look at the manual, page 120).
Imho ml lens.h should contain these portable functions: 1. get min. manual iso, 2. get max.manual iso, 3. change lens_set_rawiso to auto-coerce into these bounds instead of just failing (but return an error code if it didn't set the exact requested iso).
Please excuse my ignorance everyone but I actually just made an account to ask this question. I was looking through youtube and forums on instructions on how to install ML. If that wasn't confusing enough I learned that ML was even available for my 6D. After reading the intro on this post "file to dump the firmware, set your bootflag, and dump the debug log" i'm now way in over my head in trying to figure this out. Can someone please help me with direct step by step instructions in how to install ML on my 6D?
Info (if it helps)
Canon 6D
64 GB Sd card (I have smaller ones available if needed)
I have downloaded Magic Lantern-v2 from the official site
I have downloaded 6D-112.fir
PS. I did open and read the instructions that came bundled in the Magic Lantern-v2 bundle but the whole "file to dump the firmware, set your bootflag, and dump the debug log" has be going off the walls.
Thank you in advance guys!!
Quote from: wrestler31 on October 12, 2013, 02:27:17 PM
Please excuse my ignorance everyone
This link should be in the 1st post, I also needed a bit to find the current instructions: http://www.magiclantern.fm/forum/index.php?topic=5530.msg37766#msg37766
Forget the v2 bundle... there is a guide on here for install that answers your questions.
Hi 1%! In latest [6D] Tragic.2013Oct14.6D113.zip audio metter does not work!
Has only min and max indication, gray or green bars!
No more dat file problem! Thanks!!! :D
Sorry if missing something obvious, but is (auto)ettr supposed to work in photo mode on the current TL trunk? If I select "always on" or "auto snap" it does absolutely nothing over here, it works in lv though.
If raw zebras are working in photo mode, ETTR should work too. If not... not.
Quote from: 1% on September 24, 2013, 05:54:39 PM
Don't digic V and digic IV have the rom on different addresses? At the least rom1/rom0 are flipped at the worst its backing up garbage.
backup_region(CARD_DRIVE "ML/LOGS/ROM1.BIN", 0xF8000000, 0x01000000);
backup_region(CARD_DRIVE "ML/LOGS/ROM0.BIN", 0xF0000000, 0x01000000);
this covers all.
we simply can extract properties, main firmware and anything else we need to recover bricked cameras,
as long the bootloader is intact and loads autoexec.bin.
please dont ask me to explain again why 0xF8000000-0xF8FFFFFF is enough for all models :)
except there are models with 32 MiB flash - then we would have to write 0x02000000 bytes.
Quote from: a1ex on October 19, 2013, 08:29:00 PM
If raw zebras are working in photo mode, ETTR should work too. If not... not.
... not, I checked it. I'll project the big bat to the sky to call 1% to the rescue! :-)
I also added a bug ticket to the TL fork: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/issue/20/auto-ettr-doesnt-work-in-photo-mode
Still works as far as I can tell:
hey team,
I'm currently running ML using the updated version from the 1st post of the install guide from noisy boy (24/08/13).
one thing thats currently bothering me and can't figure out is when I'm in live view and press the Q button and then press any arrow keys i get some codes that pop up on the screen eg:
c0f079dc:
= 0
= 0 0
= 0 0 0 0
and pressing different arrow keys seem to give me different values.
how to i disable this and regain control of my Q button? :)
Im pretty sure its something simple that needs to be disabled but i cant figure what.
thanks guys
You turned on digic poke. Its in the debug menu.
Quote from: 1% on October 22, 2013, 12:24:55 AM
You turned on digic poke. Its in the debug menu.
ahh i knew that was it,
its just that it said DANGER! on that option so I didnt have the guts to press it ;D
thanks 1%
Yea, digic poke has maybe outlived usefulness.. memory browser I use all the time but digic poke hardly ever.
For me it's the opposite. Last time I've used digic poke was when I discovered the DIGIC peaking (pretty recent).
Here is a new 6D, fixes ocassional defects in dual iso preview and the meters:
http://www.filedropper.com/magiclantern-tragic2013oct226d113
Bitbucket upload is broken atm.
I noticed somewhere in this thread that banding is something that Canon should look at?
Should i send in my camera to them to take a look, or is that something that we're stuck with? Should i try some different settings on ML? I notice it a bit under 3200 ISO.
Edit: nevermind, it's horizontal banding. Clearly I don't have enough coffee this morning.
Hi. I updated to the last version and the modules won't load. I select them and it says that they will load during next boot but it doesn't happen.
Any ideas? Thanks
make sure they aren't disabled in module debug, also check that the sym files match.
Yep I just found that: "disable all modules". It's ON by default.
I haven't updated for like 2 months, lot of changes in the menus. ;)
Thanks
Hey! Haven't been here in a while, just come to see what's up everyonce and a while.
Anything big happen? RAW a little more stable??
Quote from: fauxtographer on November 02, 2013, 03:43:13 AM
Hey! Haven't been here in a while, just come to see what's up everyonce and a while.
Anything big happen? RAW a little more stable??
RAW footage is awesome, and yeah! Check out Dual_ISO! It's incredible!
Frame guide keeps going away in raw. Any thoughts?
Also ending up up with x.r00 files.
Quote from: electrichobo on November 02, 2013, 10:05:10 PM
Frame guide keeps going away in raw. Any thoughts?
Also ending up up with x.r00 files.
Do you have frame skipping enabled?
Fat32 card? That makes .r0X files, they are your clip continued.
The guide does go away with global draw now. Was kinda opposed to the black crop marks, go figure.
Quote from: 1% on November 02, 2013, 11:04:32 PM
Fat32 card? That makes .r0X files, they are your clip continued.
The guide does go away with global draw now. Was kinda opposed to the black crop marks, go figure.
so can i enable it with GD on?
exfat cards.
Yea, you can but throughput might be meh. I can pull off 1280x720 in 1x at 24p with the raw color preview full screen (ml preview) or crop marked (hacked).
The latest: bitbucket still blocking me
http://www.filedropper.com/6d-tragic2013nov036d113-win
Hello everyone!
Long time lurker (been following this thread since it was only 1 page!) , first time poster here.
I just installed the Nov 3rd ML build on my 6D. I just noticed in addition to the Raw_Rec module, there is a MLV_rec module. Is there a difference other than the metadata of the MLV format? I assume I'm going to want to use the MLV rec since it's the one that's really being developed right now? Sorry if this has been discussed elsewhere. This thread is my primary link to all things new in ML, and I don't remember reading anything particular about it.
Finally, I hadn't noticed that MLV_player module until tonight either. I spent, like, 15 minutes going through all the ML menus and I cannot for the life of me figure out how to access any kind of MLV player. I know it sounds stupid, but maybe someone can give me a little direction?
BIG thanks to the ML team for all their hard work! I'm especially grateful for color RAW previews at 720!
Thanks!
-Daniel
Quote from: RTLdan on November 04, 2013, 05:59:46 AM
I cannot for the life of me figure out how to access any kind of MLV player
In Modules Menu select mlv_play and press Q. Read the description.
Quote from: 1% on November 03, 2013, 06:01:39 PM
Yea, you can but throughput might be meh. I can pull off 1280x720 in 1x at 24p with the raw color preview full screen (ml preview) or crop marked (hacked).
The latest: bitbucket still blocking me
http://www.filedropper.com/6d-tragic2013nov036d113-win
how this build stable?
You have to see what it does with your shooting style + features used. It hasn't crashed using it how I use it.
cheers 1% really appreciate your work :D,
will try it when i get home from work.
Just one feature i think that will help me is that, when shooting bracketed shots it is limited to 15 can that be higher? like 21? also i think more importantly is there away to shoot bracketed shots with mirror lock up?
-this will help get an clearer image( because no vibration from mirror)
- will speed up capture process? no waiting time for mirror to come up. **not sure about this
im a VFX artist so the more shots i get to create an hdri image the better/ accurate the light source will be in CG.
thanks
I think you can shoot more bracketed shots than 15, something was done with that to make it infinite and then it was reverted to a more reasonable number. I mainly use auto so it just takes what it needs to.
Mirror lockup will slow down the shots but it will cut the vibrations like you said, there is a handheld mirror lockup that works between 1/x and 1/1XX, its in the shoot menu.
Hello I'm kind of new here. Not sure if I need to introduce myself somewhere else or here is enough: I have a canon 6D and 550D
A1ex, about my question to you of the DNG file: Well it worked, so I can see the picture in Windows when I open it. I installed some codec from Adobe, but not really sure it was necessary. Then it would be really nice to have the correct preview in the camera LCD when shooting Dual ISO.
BTW, I installed the development environment and produced my first build ;D
One issue apart: I noticed that the Kelvin (WB) cannot be reset to Auto. I modified a little the code so it shows now Auto (when cycling temperature, however it's not really set back to the camera. You know what I mean? How can we set this Auto WB in the camera. I know there is set_kelvin... but it needs a temperature, what is the temp for WB Auto?
Best Regards.
R.
It could be a property. Log what happens when you change WB to auto from Q. None of the cameras can be set back to auto through the ML menu, it has been a minor issue for me but a bit annoying.
Quote from: 1% on November 04, 2013, 04:56:13 PM
Mirror lockup will slow down the shots but it will cut the vibrations like you said, there is a handheld mirror lockup that works between 1/x and 1/1XX, its in the shoot menu.
Sorry im abit of a noob to ML what does that mean 1/x and 1/1xx?
Quote from: 1% on November 04, 2013, 05:40:12 PM
It could be a property. Log what happens when you change WB to auto from Q. None of the cameras can be set back to auto through the ML menu, it has been a minor issue for me but a bit annoying.
Hi 1% thanks for the answer. I will investigate a little bit. Could you tell me shortly how to "log"? sorry I'm quite new.
Regards.
Quote from: Rewind on November 04, 2013, 09:29:21 AM
In Modules Menu select mlv_play and press Q. Read the description.
Hmm... Might have a bug to report in the Nov 3rd build then?
When I hit the Q button I get a black display that says
"License: GPL
Authors: g3ggg0, a1ex
nd,ilt. on 2013-11-03 15:54:04 UTC by '{' is not recognized as an inter"
And then the pressing the arrow key I get this page...
"Information:
Name: MLV Player
License: GPL
Summary: Play MLV/RAW
Authors: g33g0, a1ex
Build date: 2013-11-03 16:04:35 UTC
Callbacks:
CBR_KEYPRESS: mlv_play_keypress_cbr"
Not sure if this is just me, or if I just need to reinstall ML or something?
Similar results when pressing 'Q' to get info about any module.
Thanks!
-Daniel
QuoteCould you tell me shortly how to "log"? sorry I'm quite new.
DM log to start, dm log to stop in the debug menu.
For above I think a module description got messed up, didn't have truncate. Shouldn't affect actual functionality.
Hi,
I think the Set Auto WB is now working, let me know what you think. Didn't use the logs, (I have to look at it yet) I modified the shot.c and added some function I found in lens.c and added the GUI stuff: "Auto" for the cycle. Here is the function I modified in shot.c :
void
kelvin_toggle( void* priv, int sign )
{
int k;
switch (lens_info.wb_mode)
{
case WB_SUNNY: k = 5200; break;
case WB_SHADE: k = 7000; break;
case WB_CLOUDY: k = 6000; break;
case WB_TUNGSTEN: k = 3200; break;
case WB_FLUORESCENT: k = 4000; break;
case WB_FLASH: k = 6500; break; // maybe?
default: k = lens_info.kelvin;
}
//begin raiky - set auto wb
if (!lens_info.wb_mode) { //if we are in auto
k = sign>0? KELVIN_MIN : KELVIN_MAX;
lens_set_kelvin(k);
return;
}
else if ((k == KELVIN_MIN && sign<0) || (k == KELVIN_MAX && sign>0)) {
lens_info.wb_mode = 0;
int mode = WB_AUTO;
prop_request_change(PROP_WB_MODE_LV, &mode, 4);
prop_request_change(PROP_WB_MODE_PH, &mode, 4);
return;
}
//end raiky - set auto wb
int step = KELVIN_STEP;
if (k + sign * step > 7000)
step *= 5;
k = (k/step) * step;
if (priv == (void*)-1) // no wrap around
k = COERCE(k + sign * step, KELVIN_MIN, KELVIN_MAX);
else // allow wrap around
k = KELVIN_MIN + mod(k - KELVIN_MIN + sign * step, KELVIN_MAX - KELVIN_MIN + step);
lens_set_kelvin(k);
}
I guess it should be quite straighforward to add the rest of White Balance values (Cloudy, Sunny, etc)
R.
Quoteprop_request_change(PROP_WB_MODE_LV, &mode, 4);
prop_request_change(PROP_WB_MODE_PH, &mode, 4);
These are your WB properties. Some value here is "auto", you can find the number values to these in something like property.c/h and then look at it with prop browser.
Hi, well the code that I show you is the code already modified. The value is WB_AUTO as you can see.
Can someone test that? It seems to be working for me.
The kelvin_toggle function in shot.c shall be replaced with the one provided in previous post.
Regards.
Well, I guess this is not the right place for my previous posts since nobody answers. Sorry I'll open a new thread.
Cheers.
Its merged today on my side and works on 6D/7D
Ok, good to know! :D
What do you think about adding other WB, such as Sunny, Cloudy, etc. to the GUI?
R.
Not worth it, might as well set K or let ML auto set it at that point. Auto is important though since I'm sure many people set it and forget it. For raw photos or video you can change it later anyway.
I am new to my 6D and going to travel to Italy shortly. Is this stable enough to try this out? It seems like it is... ! I haven't used ML yet and am not sure if its easy to just go back to the stock firmware. Looks like there are some great features I would love to use. Thoughts? BTW I am a developer and not intimidated to play with new things
thanks in advance.
-B
Boot holding set and it skips loading ML.
Does not work fokuspeak. The main menu is on (on,3,5,R), Global draw "on, all modes", but does not produce the sharp area. He previously worked. What I could "break"?
I found the reason. It is eliminated with pressing "info" button.
Unfortunately, it isn't present in FAQ.
Hi 1%!
Can I report 2 maybe bugs here?
So, the first is: when I enable LV Digic peaking it's working only before Rec button is hitted, once I hit Rec button this function is disabled...is it normal?
The second: it is known that first second is louder in some canon models, but I have for firsts 3-4 frame a noise peak in left channel (right channel is just louder for the same period) in all clips, and in some clips I have another noise peak at 18-20th sec... Do you think it will possible to find the problem? Sometimes I do interviews and record audio in cam, don't wont to use mixers and external recorders, and I need clean audio...
(http://imageshack.us/photo/my-images/41/xzlp.jpg/)
Another audio "thing" is that even using it in manual, not auto, audio waveform is not uniform:
(http://imageshack.us/photo/my-images/13/0tau.jpg/)
Using Magic Lantern v2.3.NEXT.2013Oct05.6D113 (unified) . Sorry for my english, just learning!
Thanks!!!
Yea thats normal, its an option now in the source.
Not sure from the noise/uniformity issue. I'll have to test it. On mine sometimes it does weird things from the stereo jack. Then again I've been recording wav not video/w audio so maybe something happens when its recorded with H264. In manual AGC is already off and when you turn it on you'll see it raises/lowers volume much quicker than this.
Ok, I do get some noise squiggle in the left channel while its configuring audio up to frame 2. Haven't experienced the level issue though. Will check some more. Audio seems level from what I'm recording and much different if you turn on the AGC. Only thing I can think of is you changed volume or went into the canon audio menu while recording.
So if I want to run magiclantern on a 6D - I should download the source from "Tragic Lantern" for working code...SRY it's my first time.
I uploaded a binary on the 9th so its up do date, fastest way is to compile yourself though if you want updates every day.
hey guys, when viewing back the footage on the camera, is there a way now to stop the playback? right now i have to wait till the video is done before i can use the camera. using raw not mlv and not using mlv play (not sure how to add modules hehe)
cheers guys!
Try to press the shutter button halfway.
I want to update ML on my card to the November update but am wary about proceeding without asking this basic question:
I read that an ML update simply involves copy/pasting the files from the November update onto the card.
But some of the folder names are different - eg some with capital letters, some not (eg cropmks versus CROPMKS). Aren`t these folders simply going to sit alongside each other on the card?
And the folder names are not all the same:
In the update: cropmks, data, doc, fonts, logs, modules, scripts, settings
On the card now: CROPMKS, DCIM, DOC, MISC
This doesn`t seem like a clean copy/paste/replace to me. I`d be grateful to know whether I am ok to go ahead and do this without causing myself problems.
Thanks. I can`t wait to point my camera at the sun with dual iso and see what I get!
Quote from: Ian on November 12, 2013, 01:01:22 PM
Thanks. I can`t wait to point my camera at the sun with dual iso and see what I get!
Post a pic on the dual ISO thread!
Quote from: Ian on November 12, 2013, 01:01:22 PM
I want to update ML on my card to the November update but am wary about proceeding without asking this basic question:
I read that an ML update simply involves copy/pasting the files from the November update onto the card.
But some of the folder names are different - eg some with capital letters, some not (eg cropmks versus CROPMKS). Aren`t these folders simply going to sit alongside each other on the card?
And the folder names are not all the same:
In the update: cropmks, data, doc, fonts, logs, modules, scripts, settings
On the card now: CROPMKS, DCIM, DOC, MISC
This doesn`t seem like a clean copy/paste/replace to me. I`d be grateful to know whether I am ok to go ahead and do this without causing myself problems.
Thanks. I can`t wait to point my camera at the sun with dual iso and see what I get!
I installed ML yesterday for the first time, as described in the install guide thread, to update i just replaced the folders on my SD card with the new ones - all worked fine.
P.S.
I'm not sure it's relevant to this thread, but using LV with ML seems to heat up the camera pretty fast (I was playing with it browsing the menus and stuff, temp got to 55C in like 5-10 minuts) also battery goes down fast. Is it ok with ML?
Quote from: RTI on November 13, 2013, 07:56:59 AMI'm not sure it's relevant to this thread, but using LV with ML seems to heat up the camera pretty fast (I was playing with it browsing the menus and stuff, temp got to 55C in like 5-10 minuts) also battery goes down fast. Is it ok with ML?
Yes, this is what happens - ML disables some power saving, and some feature like peaking are rather cpu intensive.
I used the 6d w/o ML only for one day, so I cannot say how high the battery drain would be otherwise because "browsing the menus" turns the lcd on which eats a lot of power, so browsing though pictures or the Canon menu might nearly have the same effect.
Quote from: Marsu42 on November 13, 2013, 08:30:55 AM
Yes, this is what happens - ML disables some power saving, and some feature like peaking are rather cpu intensive.
I used the 6d w/o ML only for one day, so I cannot say how high the battery drain would be otherwise because "browsing the menus" turns the lcd on which eats a lot of power, so browsing though pictures or the Canon menu might nearly have the same effect.
Yep, I figured about peaking and zebras would eat a lot of resources and be CPU intensive, turned that off. Ultimately what bothers me is not power consumption but the fact that the camera gets warm to hot, and I didn't have that even when shooting a full time wedding. I didn't expect it, or maybe it's just my camera.
Hey guys I shot a documentary on the 6D with magic lantern and it was great. Almost no problems accept for one. Sometimes it would corrupt cards!! (Scary I know) Fortunately I was able to save all the data by going into diskutility on the mac and doing a repair. I happened twice during the whole time. I went through about 30 cards the whole trip, so low incidence of failure.
Recreating the issue, it really only happened during bitrate overide options. I ended up restoring magic lantern on that card because I couldn't adequately turn it off. It wasn't a real issue as I had 2 extra 64GB cards on me at all times.
I've had 2 cards corrupt, 1 on 6D, one on 600D. Both were unusable afterwards (sector 0 ruined), all files recoverable. On 6D if you fail an H264 and produce a .dat file it can crash the player or the media catalog. But besides that no reason it would mess up the card, the raw writes way more than H264.
What cards? They were usable afterwards? Settings used?
Mine were patriot EP UHS 64gb.
Quote from: kgv5 on November 12, 2013, 12:45:25 PM
Try to press the shutter button halfway.
hehe, now i feel stupid :p
thanks man
Quote from: 1% on November 14, 2013, 02:56:42 AM
I've had 2 cards corrupt, 1 on 6D, one on 600D. Both were unusable afterwards (sector 0 ruined), all files recoverable. On 6D if you fail an H264 and produce a .dat file it can crash the player or the media catalog. But besides that no reason it would mess up the card, the raw writes way more than H264.
What cards? They were usable afterwards? Settings used?
Mine were patriot EP UHS 64gb.
They are sandisk 64gb pro. They were completely fine afterwards I think any program that can restore the partition table should be able to repair the cards. It took less then a second so I doubt it was a major issue.
Is anyone else getting crazy noise when using fps override? There is insane amounts of green shadow and just hotpixel like noise when i crank it below 1fps.
Yes, digic V all have this issue with FPS override. It gets worse as the sensor gets hotter. Dead pixel removal would solve some of it or dark frame subtraction... but it is pattern noise so not super easy.
I haven't had the partition table go yet, could have been the cards themselves or a bad set of circumstances.
Quote from: 1% on January 08, 2013, 05:44:12 PM
Here are my plans for the bit rate menu.
*Auto Loading of 4 configs.
CBR - CBR Mode ml/cbr.ini
VBR - VBR Mode ml/vbr.ini
RC - Canon rate control /ml/rc.ini
H264.ini - User config with load button.
We can override InitialQP and target Bit rate. Yes it does work, yes it will freeze camera on IPB if you go over 60mbps and violate the spec until you load a level 5.1 config.
I will make an auto loader with OFF, ON, Override.
Without the auto loader on you can adjust target bit rate *OR* record at a fixed qp with the initqp toggle.
Everything else can be set in the text files, following what I wrote in the RE thread. This puts video quality on par with 600D and cache hacks, maybe a bit better if you pixel peep. When the matrix loading is figured out this will be an ideal setup. I can't find where the other parameters can be adjusted on the fly, I think they get sent to a second proc or are in registers/ram. Maybe buffer save can be ported over for another rate control mechanism if initQP can be changed on the fly, mine seems to be better at stopping stops than canon's.
sorry, but really can't find out the RE thread for reference. Hope that someone might paste here a link of this thread.
BTW, thanks 1% for such a wonderful hack, ML and TL ROCK!
I'm not sure it's the right place to ask, but still I'll give it a try. Since we're limited in raw vide resolution, what would be the most apropriate encoder setting to achieve the best results with h264? I've searched the forums, but so far I've seen stuff related to 600D, and I think those settings aren't relevant to the current build. I someone has experience with this, maybe they could share the info.
Quote from: keba on November 18, 2013, 09:41:48 AM
sorry, but really can't find out the RE thread for reference.
Probably this (reverse engineering): http://www.magiclantern.fm/forum/index.php?topic=4124.0
Quote from: RTI on November 25, 2013, 11:01:15 AM
Since we're limited in raw vide resolution, what would be the most apropriate encoder setting to achieve the best results with h264?
+1 for a dummy's guide to optimal (20mb/s) iq non-raw video shooting with TL for the usual suspects video resolutions (I guess 1080p/30 and 720/60).
Quote from: Marsu42 on November 25, 2013, 10:29:40 PM
Probably this (reverse engineering): http://www.magiclantern.fm/forum/index.php?topic=4124.0
+1 for a dummy's guide to optimal (20mb/s) iq non-raw video shooting with TL for the usual suspects video resolutions (I guess 1080p/30 and 720/60).
Thanks Marsu42 for the RE link!
BTW, do we have any official way to fully uninstall ML or TL? now with the latest TL my 6D did not detected by PC anymore via USB cable (already change to the empty SDHC card) but result still the same.
Quote from: keba on November 28, 2013, 04:43:40 AM
BTW, do we have any official way to fully uninstall ML or TL?
I don't know of any way to remove the camera bootflag from the 6d (same as 5d3 I guess) - as for the card simply format the card to remove the card bootflag (or disable it with eos utility), remove ml files, done. I admit that's rather "deactivate" than "uninstall" and the camera will still have the 1s delay on boot.
Quote from: keba on November 28, 2013, 04:43:40 AM
Now with the latest TL my 6D did not detected by PC anymore via USB cable (already change to the empty SDHC card) but result still the same.
Wa-what? That's the reason? I was already wondering, you're saying the 6D isn't detected by the PC if a card with ML/bootflag is inside, and you have to put in a dummy non-bottflag card? If so, I'd put this in the "bug" category.
Quote from: Marsu42 on November 28, 2013, 11:44:43 AM
I don't know of any way to remove the camera bootflag from the 6d (same as 5d3 I guess) - as for the card simply format the card to remove the card bootflag (or disable it with eos utility), remove ml files, done. I admit that's rather "deactivate" than "uninstall" and the camera will still have the 1s delay on boot.
I think there's a way to remove the bootflag, by downgrading firmware, the procedure is described here http://www.magiclantern.fm/forum/index.php?topic=5530.575
Quote from: RTI on November 28, 2013, 03:04:25 PM
I think there's a way to remove the bootflag, by downgrading firmware, the procedure is described here http://www.magiclantern.fm/forum/index.php?topic=5530.575
Right, thanks, that deserves a sticky. The direct link to the description is here: http://www.magiclantern.fm/forum/index.php?topic=5530.msg57496#msg57496
If its not detecting via USB then probably turn off headphone monitor. Thats all I can think of blocking it.
Wait what? Headphone monitoring is working?!?!
Yea, since audio controls went in pretty much.
Quote from: 1% on November 29, 2013, 04:32:17 AM
If its not detecting via USB then probably turn off headphone monitor. Thats all I can think of blocking it.
Guys my usb port is also dead :(
I tried the above but no success
The pc doesnt detect the camera, but the camera does detect that a usb cable is connected to it (wifi option becomes greyed out and becomes available as soon as the cable is unplugged).
Tried several cables, usb ports etc.
Same cable works fine on 60d
Any ideas?
Quote from: darkstarr on December 02, 2013, 03:58:40 PM
The pc doesnt detect the camera, but the camera does detect that a usb cable is connected to it
Have you tried it on a different OS?
Quote from: sim3213 on December 02, 2013, 08:04:35 PM
Have you tried it on a different OS?
forgot to clarify
yes xp, win7
also my 6d was last working with dslr controller
saw no field use just testing at home before it suddenly stopped working
Check drivers in the OS, especially if you have multiple cameras.
Quote from: 1% on December 03, 2013, 01:49:12 AM
Check drivers in the OS, especially if you have multiple cameras.
yea i highly doubt its a driver issue since its the same thing with dslr controller: when i hook the tablet up to the camera it is no longer detected by the tablet (confirmed by running usb host diagnostic utility), but on the camera the wifi section does before unavailable, until the cable is unhooked from the camera then it becomes available again.
tried to connect the 6d to 2 computers which never had the 6d / eos utilities installed on it, and nothing happens, no device nothing.
when using the same cable on the 60d and connecting to those same 2 computers, camera is detected and the default canon drivers are automatically installed.
not sure if problem was caused by ML or not, or if DSLR controller somehow fried the USB board on the 6d...
and headphone is off? thats the only thing, mine still detects so dunno and I've been using it all month, could be fried. you can try without a card inserted too.
yea i tried pretty much everything i can think of :(
oh well, back to canon, thank god its under warranty
They should all still be under warranty... but some maybe not much longer.
Can you guys reproduce this? https://bitbucket.org/hudson/magic-lantern/issue/1763/disabling-cropmarks-in-photo-mode-does-not
Yep, its a bug lol.
About the USB issue: are you sure that you've turned off WiFi?
Quote from: tzobor on December 04, 2013, 10:11:26 AM
About the USB issue: are you sure that you've turned off WiFi?
lol yes very sure
Hello everybody.
I have same issues with the magiclantern-Tragic.2013Nov30.6D113
When i press REC for filming the little menu for the iso and audio
functions pupping up and i can increase or decrease the values.
When im pressing the button again the menu closed. normally it is
set to the Set button.
The second is that the ML menu close after 6-10 seconds when i
do nothing and just have a look at the menus. When i scrolling or
change settings this is not happend.
Does anybody know why ? the nightly build have same problems.
Quote from: darkstarr on December 02, 2013, 03:58:40 PM
Guys my usb port is also dead :(
I tried the above but no success
The pc doesnt detect the camera, but the camera does detect that a usb cable is connected to it (wifi option becomes greyed out and becomes available as soon as the cable is unplugged).
Tried several cables, usb ports etc.
Same cable works fine on 60d
Any ideas?
Update: well, within 2 weeks, both the usb on the 6d and 60d are now dead.
I don't believe its caused by ML now since the 60d has been running 2.3 for over a year with no issues whatsoever
its either DSLR controller or the cables.
i've opened a bug report thread in the hope of a solution:
https://bitbucket.org/hudson/magic-lantern/issue/1780/wtf-dead-usb-on-both-60d-and-6d-please
Sucks it took out both :( Maybe some short inside put the 5V where it didn't belong and popped a micro fuse or worse the IC.
Quote from: darkstarr on December 09, 2013, 12:41:08 AM
Update: well, within 2 weeks, both the usb on the 6d and 60d are now dead.
You used the *same* cable and hub on both cameras? Doh, I also don't think it's ml but a hardware failure - you could try to isolate if the hub or cable is the problem by frying anther couple of cameras :-p ... but my money would be on the hub being broken if you don't see any physical damage or dirt on/in the cable after close inspection and it has worked before.
Quote from: 1% on December 09, 2013, 04:21:22 AM
Sucks it took out both :( Maybe some short inside put the 5V where it didn't belong and popped a micro fuse or worse the IC.
yea it sucks big time, i just want to curl up in a ball and cry lolll
Quote from: Marsu42 on December 09, 2013, 08:35:48 AM
You used the *same* cable and hub on both cameras? Doh, I also don't think it's ml but a hardware failure - you could try to isolate if the hub or cable is the problem by frying anther couple of cameras :-p ... but my money would be on the hub being broken if you don't see any physical damage or dirt on/in the cable after close inspection and it has worked before.
lolll, yea i cant afford a few other cameras loll
yea no physical damage whatsoever
thing was barely used / tested
then one morning, nothing....
anyway im going to create a new thread in the hardware section, dont want to hijack this one!
cheers all
can someone confirm that Dec. 8th build does not boot.
i'm currently running the Nov 30th which is working fine.
The 8 december build is for the 5DIII.
Has anybody worked out how to get 255M of buffer instead of 155 while recording?
Seems like it's similar to 5DIII where you can allocate more memory with LV off.
Quote from: Kathode-Ray on December 21, 2013, 11:29:14 AM
The 8 december build is for the 5DIII.
lol color me stupid!
how do i build the latest myself? or is it best to wait.
Is there anyone here who did some testing with their 6d and the MLV-rec module and the new sound module ?
http://www.magiclantern.fm/forum/index.php?topic=7122.1025
I'm using the tragic lantern build from 30 November and the new MLV-rec and sound build from the topic above.
The first clip after switching the camera on has sound recorded along with the raw clip. Every clip after it doesn't have sound and shows the error message "sound failed to stop, state 4".
Hi guys! Here I am...again. :)
Would like to report some minor bugs refering to last build Tragic.2014Jan03.6D113. So what am I doing?
I'm hit rec with default settings until my 16gb sandisk became full (for 6 times) and:
-
I was sure the 29:59min limit was bypassed ( I was forget to enable MovieRestart, may be it'll help...Yes, it helps, anyway there is a 2 frames audio drop only at 29:59)
(https://imageshack.com/i/f7p11qj)
-when I put in Encoder menu Bitrate=35, InitQP=1 and ConfigSelect=VBR the indication of bitrate (A=~130, B=~130) is right only for, I think, for the first 4GB file...the indication of A on others files it's...like a countdown, from something like 98 to something like 38 on my 16GB card, and B is always=0...same thing is with default settings: indication on first 4GB file is ok, on others it is not...may be I miss something...
-*.dat file problem when the card became full...it's happen again...only once but...
Great work guys!!!
I had a problem with the 6D not completing mov files and just leaving .DAT without information when shooting over the 4GB file size. Is this what you are talking about? I actually decided that it might have something to do with having autorestart enabled or some other conflicting menu item enabled that hindered the 6D from completing the file.
Quotemay be I miss something...
Probably a math problem that has to be fixed. H264 used to stop at 4GB because of fat32.
Quotethere is a 2 frames audio drop only at 29:59)
So i'm guessing that the movie restart takes 2 frames to restart.
Quote"sound failed to stop, state 4".
This was fixed early january but I can't upload anything else to bitbucket, ATM. The bot-fly only does EOSM and 7D.
I can't seem to unzip the four most recent downloads from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads The earlier downloads from October and earlier work fine for me. I'm working on a Mac. Is this my problem or a problem with the downloads?
Quote from: cpreston on January 14, 2014, 07:02:59 PM
I can't seem to unzip the four most recent downloads from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads The earlier downloads from October and earlier work fine for me. I'm working on a Mac. Is this my problem or a problem with the downloads?
download Unarchiver and it'll do it for ya. I had the same issue. The files are fine but for some reason mac doesnt like me this time.
Hi everyone,
I have a question and i can't find the answer in this forum.
Does ML for 6D gives a clean HDMI output ?
Thanks
Nope
The 6D Tragic Lantern could really use the Magenta/Green number next to the Kelvin value in Live view. For those of us that dial out green under fluorescent lights this feature saves us when we go back into daylight and would otherwise forget to set it back to zero. Im begging you.
Quote from: matthew19 on January 29, 2014, 11:46:37 AMIm begging you.
Now, if I ever saw one here's someone motivated enough to look at the source code himself and submit a patch :->
Hi 1% & all the rockstar devs and supporters! ;)
Great work on TL so far - loving playing around with it. Peaking, Zebra, Magic Zoom & Audio Monitoring rock!
I had a couple of recent problems when testing TL on my 6D. I installed Jan 18 build about 10 days ago.
1. SD Card/30 Mins+ Recording Issue:
I tried recording for 32 mins continuously on to my 64GB San Disk Extreme Pro SD card, to test what would happen. It seemed to process ok (camera didn't freeze as Nov 30th build had done sometimes), but when I ejected my card and put into the card reader my macbook could no longer read the card.
2. Audio Recording - File Length Issue:
I had Canon audio enabled because my rode video mic was out of battery. However the rode was still connected via the minijack port. Result: the length of the associated separate .WAV file when imported into Premiere Pro was just over 6 hrs, irrespective of the length of the video clip taken. When the rode's battery was replaced, the problem disappeared. I know I could've just disconnected the mini jack, but thought this may be of interest.
For now I've scrubbed the 2 cards I was running TL off, as a safety measure, because I have to use the camera for video work and can't risk corrupting them.
Cheers,
Keep up the good work!
Quotebut when I ejected my card and put into the card reader my macbook could no longer read the card.
Quite weird because none of that is touched. Canon is writing the files and all we have for >30 mins is movie restart.
Did your card read in the camera after it didn't read in the macbook? Also... exfat + macos, any issues there?
Quote
hrs, irrespective of the length of the video clip taken.
The wavs do not have an end because of the way they are saved.Open in audacity or soundforge and resave... also use the clapper because you may have to stretch/shrink the actual wav.
1% is it possible to have the green/magenta show in the overlays as it does on the 5d? I'd be happy to pay $100 for this feature.
Quote from: 1% on February 04, 2014, 11:47:47 PM
Quite weird because none of that is touched. Canon is writing the files and all we have for >30 mins is movie restart.
Did your card read in the camera after it didn't read in the macbook? Also... exfat + macos, any issues there?
- No, when I put card back in camera TL did not boot. On the macbook the card was showing up as "NO NAME" and there were no files at all.
Had to reformat the card and it works fine again now (without TL as already stated). Sorry needed to use it again, so not sure if I can remember anything else that might have been of use to you.
Heh, I'd be careful with that card and the macbook reader.
Noted ;)
Hadn't formatted card to exFAT, so will do so and try again.
Thanks!
I've had a few crashes recently with the magiclantern-Tragic.2014Jan18.6D113.zip build. Whenever I load ML, it says the camera did not shut down correctly, skipping module loading.
Here's a few crash logs.
https://www.mediafire.com/?gsdipqqecsdeqhl
https://www.mediafire.com/?pkx3hexqj96d7rx
https://www.mediafire.com/?gb0tdcgv1fetxe6
https://www.mediafire.com/?db6qqsb6npmlhz3
Memory
at ./Memory/Memory.c:568, task RscMgr
try loading less modules.
Quote from: 1% on February 09, 2014, 05:10:52 AM
Memory
at ./Memory/Memory.c:568, task RscMgr
try loading less modules.
Problem solved, thanks
Sorry if this is a stupid question.
magiclantern-Tragic.2014Feb08.6D113.zip?
What has changed to the magiclantern-Tragic.2014Jan18.6D113.zip version?
a whole ton of commits. read through the repo.
Reason for white screen when fpsoverride used? No, not the too long exposure;)
Quote from: 1% on February 09, 2014, 07:26:07 PM
a whole ton of commits. read through the repo.
OK, will do, thank you.
Hi all,
Just a little confused over the whole TL vs the new 6D ML builds.
1% has done an awesome job for the 6D and I've been really getting so much use out
of TL while ML's version has been "unmaintained". Everything has been incredibly stable and very up to date with new features. I guess what I'm wondering is, will I be losing some of the features I've come to expect from TL if I begin using builds from ML? I want to respect the "unity" that ML is asking for by using those builds, but on the other hand if no one is really working on the ML 6D build, it's asking a lot to sacrifice all the work, testing, and features for my 6D that 1% has already provided.
Really just not sure what the story is or what I'm supposed to do?
Thanks to all the developers for making any of this even possible!
-RTLdan
I think the whole deal will be to take what is really stable and port it back to main so code there is actually up to date not 4 months behind. Plus I get to see if bugs are related to me or not and everything remains coherent and together. Plus get some code review from better programmers and things end up being more efficiently done.
Well, not exactly. The community split caused by Tragic Lantern only serves to cause confusion, and since it diverged a lot from the main builds (and keeps diverging), merging back is getting more an more difficult (almost easier to code these things from scratch).
For me, the lack of a positive answer from you, 1%, for more than one month in our private discussions, more than 4 months in this public discussion (http://www.magiclantern.fm/forum/index.php?topic=8900) and more than one year since Tragic Lantern exists counts as refusing to collaborate (and just talking is not enough; I've expected you to take some action). I'd prefer to avoid making use of my admin superpowers to prevent further damage to the ML community, but it looks I have no other choice.
Quotewill I be losing some of the features I've come to expect from TL if I begin using builds from ML?
Since we have done a blind backporting (without a 6D in our hands), you are the one who should answer this question and tell us what else to backport: http://www.magiclantern.fm/forum/index.php?topic=3904.msg101892#msg101892
You should be aware that 90% of the features from Tragic Lantern come actually from Magic Lantern (some features need fine-tuning for each camera). There are some things implemented in unclean ways (mostly bitrate control), but these are going to be cleaned up at some point and merged back once we have a solid port with the basics working really well.
QuoteEverything has been incredibly stable and very up to date with new features.
From my code review attempts while trying to backport the changes, and from the feedback from power users (e.g. Marsu42), I wouldn't call it incredibly stable. I've tried to do my best in disabling the unstable bits (especially the code that - instead of fixing the root of the problems - simply disabled the error message in either Canon or ML code), but I have no 6D to test the changes on (so your detailed feedback is essential).
http://www.magiclantern.fm/forum/index.php?topic=9510.msg78084#msg78084
http://www.magiclantern.fm/forum/index.php?topic=7503.msg83832#msg83832
http://www.magiclantern.fm/forum/index.php?topic=8900
http://www.magiclantern.fm/forum/index.php?topic=9508.msg101507#msg101507
More details coming soon.
Quote from: 1% on February 16, 2014, 08:02:26 AM
I think the whole deal will be to take what is really stable
If it would be you managing to submit dedicated backport pull requests for code review & integration, great, and you indicated such before... but if it's "I'm developing my own fork as it's most convenient, but feel free to dissect it and copy/paste to ML" this won't work, and you know it.
It's perfectly legit to do it your own way of course, and I'm absolutely grateful for all the 6d work you've done as I'm using it right now - but as time passes & the more the TL code base differs, the more pressing is the need for you to decide for one approach or another.
The only way I can currently see to save this is for you to start submitting small pull requests once you update new ML features to the 7d/600d/6d, like stub addresses or such - so you'd help "maintaining" these for ML and don't just keep them in your fork. If that's covered, surely a schedule could be worked out what features need to reach what stability for a backport pull requests, of course it's fine to work on unstable features in an experimental fork for some time.
However, unless you indicate with action you're going to be a part of the *ML* community, as a long-time ML user I can only side with alex and say the split in the community merits stopping users being confused, i.e. separate ML & TL entirely.
I know maintaining an own fork is much more fun, submitting pull requests is tedious and having them torn apart by smart-a** comments by the big devs can be very annoying as you're not in control of what gets merged. But I do hope that if you should decide to take up the offer to make a schedule for TL re-integration, I can only hope the ML devs will acknowledge that this might not be easy for you and will strive to let you put your ideas into ML - all factual disputes I've ever read about can be mediated or solved quickly.
Hi guys,
Sorry for my earlier post... I didn't mean to stir anything up, just really wanted to know what the difference was and what was recommended to do for 6D owners.
I should have clarified too that when I said "incredibly stable", I meant that the features I use Magic Lantern for (mostly the meters and intervalometer so far) it has been reliable. No crashes to report. I understand there may be instability in some of the newer features that I have not been using much.
Anyhow, I really do appreciate all the work that every one of you developers have done for the community, and while I'm not a coder, I'll download the ML 6D nightly and test it as best I can to help with the development. As an outside voice though, I just want to say that I'm glad there is someone like 1% with a 6D AND coding skills to keep this camera in the mix. It's been a blessing to me to have access to these amazing features.
Thanks again everyone!
I'll watch these threads closely.
-RTLDan
So I have been using ettr for quite while now and usually it works really well. However, I must have done something as it is not behaving itself.
When I try to ettr in manual mode, ML only tries to change the iso settings, and nothing else. Before.
, it seemed to change the shutter settings first and if it couldnt get within range, it would then change iso. now it just changes iso, no matter what I do or what the camera is set to exposure wise.
I have even tried to test it by manually ettr ing and then auto ettring, only to watch the camera ramp up the iso until the max it is allowed to do and coming up with an error.
Has anyone had this experience and know the fix?
Are you sure auto expo isn't on too?
my 6d stops responding everytime I try to preview the raw image and try to adjust the exposure by holding set btn while scrolling the wheels. anyone has thesame issue?
Works fine as of todays compile... might be issues from conflicting shortcuts in canon or more left over stuff from "new lv buffer detection"
Hi all.
I'm a new 6D user and tempted to install TL. First of all, kudos to 1% and others working on the 6D fork, probably noone would deny the great work done here.
But I haven't installed TL for now, and hesitating to do so mainly because of the unclear future of TL. To me, a community supported version merged to ML is far more important than having bleeding edge features. 1% you're very reactive to fix bugs or integrate new features, why not use this workforce to freeze TL for a while and merge it ? For what it's worth, I would be ready to donate if it can make this merge happen. On the other hand, I won't donate for TL if it continues to diverge, one could wonder what's the TL goal actually.
Cheers
Quote from: bjacklee on February 28, 2014, 09:58:00 PM
my 6d stops responding everytime I try to preview the raw image and try to adjust the exposure by holding set btn while scrolling the wheels. anyone has thesame issue?
Same over here, problem disappeared after switching to ML.
Quote from: hagar-dunor on March 03, 2014, 02:48:04 PM
1% you're very reactive to fix bugs or integrate new features, why not use this workforce to freeze TL for a while and merge it ?
Amen - though looking at the commits, the merge seems to be on a better track now.
Its working here, I haven't been able to reproduce it. Do you have the set button mapped to something else? I'm merging 7D at the moment + a lot of the stuff in 6D is already merged and the rest is not accepted in main (i.e cache hacks). What are you missing in ML? Have some bugs?
QuoteOn the other hand, I won't donate for TL if it continues to diverge, one could wonder what's the TL goal actually.
I don't take money donations. ML takes BTC donations. No workforce, its just me and 5 bodies. My goal is a fully featured camera that I can use, its never been much more than that.
Quote from: Marsu42 on March 03, 2014, 03:01:51 PM
Same over here, problem disappeared after switching to ML.
This issue is now fixed on the latest build. :)
@1%, Whats the status of the Digic 5 issue with low fps video? it is still very buggy everytime I use this feature in 6d. but with my 60d, everything works fine.
Weirdly, I just did a professional shoot and not one single problem with ettr, it worked every time, and I don't think that I've changed any settings. I will write everything down if it starts working strangely again.
Quote from: 1% on March 03, 2014, 05:31:55 PM
I don't take money donations. ML takes BTC donations. No workforce, its just me and 5 bodies. My goal is a fully featured camera that I can use, its never been much more than that.
I, for one, think you are doing an amazing job on this 1%, and dont really see why you should change what you're doing.
Btw 1.1.4 is out. Yawn. I'd advise not to upgrade until some people figure out if there are hidden regressions like Canon blocking 3rd party batteries like on newer 5d3 fw.
http://usa.canon.com/cusa/professional/products/professional_cameras/digital_slr_cameras/eos_6d#DriversAndSoftware