ML now has support for 6D.116: Nightly download (https://builds.magiclantern.fm/#/)Please report any new bugs via the issue tracker (https://bitbucket.org/hudson/magic-lantern/issues/new). Please include the firmware version in your bug report.
You can find known (and partly obsolete) bugs here (https://bitbucket.org/hudson/magic-lantern/issues?status=open&status=new&version=6D).
(http://a1ex.magiclantern.fm/bleeding-edge/new-installer.png)
Installation:1) Format the card from the camera.
2) Make sure you are running Canon firmware
1.1.6 (http://www.canon-europe.com/support/consumer_products/products/cameras/digital_slr/eos_6d.aspx?type=firmware).
3) Copy ML files (http://builds.magiclantern.fm/) on the card and run Firmware Update.
Uninstallation:1) Run Firmware Update from your ML card.
2) Follow the instructions.
ML for the previous firmware version 1.1.3 (won't be updated):
- forum: Canon 6D / Firmware 1.1.3 thread (http://www.magiclantern.fm/forum/index.php?topic=3904.0)
- old nightly: 6D113 nightly .zip (https://builds.magiclantern.fm/jenkins/job/6D.113/296/artifact/platform/6D.113/magiclantern-Nightly.2015Jun09.6D113.zip)
The battery Phottix Titan 2000 mAh works well on 1.1.6
In video mode menu ML turns off quickly.
In photo mode menu is not turned off by yourself, just by pressing a button.
These are the first impressions. :)
Quote from: gooolg on May 01, 2015, 11:38:37 AM
The battery Phottix Titan 2000 mAh works well on 1.1.6
In video mode menu ML turns off quickly.
In photo mode menu is not turned off by yourself, just by pressing a button.
These are the first impressions. :)
Thanks! I think the menu problem is this one (https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out). I'm still trying to find a solution to that. It affects the 70D and 6D 1.1.3 as well.
Quote from: Maqs on May 01, 2015, 11:47:23 AM
Thanks! I think the menu problem is this one (https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out). I'm still trying to find a solution to that. It affects the 70D and 6D 1.1.3 as well.
and the M :(
Quote from: Maqs on May 01, 2015, 09:56:15 AM
For those willing to test 1.1.6, here's a nightly-like .zip: download (http://37.221.193.59/~marcus/magiclantern-6D116.zip).
Please report the results of your testing in this thread. Thanks in advance!
As for ML itself, using those builds is at your own risk. I use those (and more unstable/testing ones) on a daily basis, but not for important work. You can always start your camera without ML by keeping SET pressed while turning it on. This also comes in handy dealing with April's fool jokes. If you experience any strange behaviour like freezing, crashes, stuff turning weird, the best way usually is to take the battery out and put it back in.
Here's the pull request (https://bitbucket.org/hudson/magic-lantern/pull-request/634/support-for-6d-firmware-version-116/diff). See also Canon 6D (http://www.magiclantern.fm/forum/index.php?topic=3904.0) for general discussion.
Known problems:
- LV menu times out (https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out) (also affects 6D.113, M and 70D)
- ... to be continued ...
I can help you in testing. I have 70D + 6D. I mostly use them for video. H.264+ some times RAW.
Quote from: grey on May 01, 2015, 04:17:42 PM
I can help you in testing. I have 70D + 6D. I mostly use them for video. H.264+ some times RAW.
That would be great! Just grab the latest .zip from the first post, try whatever you like and post your experiences. Please also report success or anything different to v1.1.3 that could be a bug in ML for v1.1.6. :)
I pulled from the nightly build link today (2:44pm EDT).
The install ran without a hitch, while I was on the AC Adapter.
I can navigate the menu (saw the timeout you all mentioned).
Since focus peaking is my personal favorite feature, I went straight for that. I also remember someone saying that Global Draw had to be On, which it was already. After turning on Focus Peaking, I see no indication of it in Live View. I have tried out a number of settings, but see no effect at all.
Is there another setting I should also be checking?
UPDATE: I looked in the forums and found http://www.magiclantern.fm/forum/index.php?topic=4081.msg22513#msg22513 which talks about pressing the Info button a few times to change the overlays, and voila - there is a mode in which FP IS working after all.
I don't know if it was mentioned elsewhere, but the menu timeout only happens when you press the 'trash-can' button with LV on; if its off, the timeout is either absent or much longer.
Tried this morning !
For the moment, it's works like a charmed. I use ML for Intervalometer, focus stacking, rack focus and audio remote shot.
I have a factory firmware with a Factory Menu but I'm not able to change it. If you want some info from this firmware tell me.
(http://image.noelshack.com/minis/2015/18/1430647040-vram0.png) (http://www.noelshack.com/2015-18-1430647040-vram0.jpg)
(http://image.noelshack.com/minis/2015/18/1430647063-vram1.png) (http://www.noelshack.com/2015-18-1430647063-vram1.jpg)
/me now also runs 1.1.6, works fine though I'm just using a subset of ML features atm. Thanks to Maqs and JLGW for all the work, it's hilarious tedious it is to get ML from one minor fw version to another :-\
Imho it's time to push this to the main repo, get it merged and do nightly 1.1.6 builds before 1.1.7 is released :-p. If nobody complains, I'd even vote to dump 1.1.3 unless major problems with batteries being blacklisted by Canon pop up. I guess most people will want to run the most recent fw and downgrading just to make ML work preventing some to try it.
Quote from: kikislater on May 03, 2015, 11:58:27 AM
I have a factory firmware with a Factory Menu but I'm not able to change it. If you want some info from this firmware tell me.
Ugh? So this firmware of yours works with the 1.1.6 ML port, but contains this additional "Factory" menu? What does it contain, and what does "not able to change it" mean exactly?
Before I have a 1.1.3 but with an another name ... Now I have updated to the 1.1.6 provided on the official Canon website support.
I bought this camera with this factory firmware but I didn't pay attention it was in my camera. Just one day, I push the Menu button, I move to another menu, quit the menu and then push menu again and the menu was back on this screen I show you before (blue one with factory menu).
In this menu there is some test to do ... Watch below
(http://image.noelshack.com/minis/2015/19/1430771580-vram0.png) (http://www.noelshack.com/2015-19-1430771580-vram0.jpg)
I'm not able to remove this firmware and put the customer firmware without this "factory menu". I don't want to send it back to Canon because I don't want to wait to have my camera back (wasting time) and now I don't care about this menu
Quote from: kikislater on May 04, 2015, 10:33:25 PM
Before I have a 1.1.3 but with an another name ... Now I have updated to the 1.1.6 provided on the official Canon website support.
Interesting, I'd like to know if it's some hardware change on your specific camera that enables this menu or a flag in the nvram. I've asked on CR, maybe someone happens to know over there: http://www.canonrumors.com/forum/index.php?topic=26242
Quote from: Marsu42 on May 05, 2015, 01:23:35 AM
Interesting, I'd like to know if it's some hardware change on your specific camera that enables this menu or a flag in the nvram. I've asked on CR, maybe someone happens to know over there: http://www.canonrumors.com/forum/index.php?topic=26242
It's just some flag somewhere, no hardware change. You can also hijack some useless sub menu (like the one showing certification information) to the firmware test menu. You can do all kinds of funny tests from there, for example a button test that shows you every button (including the sdcard/battery door buttons, power switch etc.), rendering it impossible to turn off the camera without taking out the battery while the test is running. :-)
Hello. Big thanks to developers who made this software.
Just updated from 1.1.3 to 1.1.6, and installed fresh ML. Atm everything works fine, tracking focus starts with center point and holds objects.
Sometimes there is a need to switch from Tracking focus to Single, and temporary switch between two can be set to hotkey.
I'd appreciate a feature that also switches focus points from Auto when Tracking focus is active to Center Point, when OneShot focus occurs.
Or make independent FP choice as it is done in vertical/horizontal orientation..
Can it be implemented in ML?
Thank you Maqs! I just upgraded to 1.1.6 and installed this and I will report any issues I run across.
Quote from: madcat on May 08, 2015, 11:24:54 PM
Sometimes there is a need to switch from Tracking focus to Single, and temporary switch between two can be set to hotkey.
I'd appreciate a feature that also switches focus points from Auto when Tracking focus is active to Center Point, when OneShot focus occurs.
Or make independent FP choice as it is done in vertical/horizontal orientation..
Can it be implemented in ML?
All these three things could be implemented by ML, the core code is there so you just need the logic to do "if button x is pressed do this" or if "level changes do that" or "if one-shot focus do thisandthat". Seems it's time to learn how to code a module for you :-)
Thanks ! I would love to see the focus patterns feature.
I gonna test this version ;)
Quote from: carlosvega on May 11, 2015, 08:44:52 PM
Thanks ! I would love to see the focus patterns feature.
I guess there's no end to potential little helper functions and features (button-feature mapping and simple if-then). It's clear that for every feature desired by one user ten more will pop up deeming it unnecessary and are against merging.
Thus problem is how to integrate 'em all in a general way into ML: it's either via a big usability module with a huge workload on the gui interface or with user scripting. At least with the latter there seems to be hope again looking at the lua branch. If there's a good api to the ml features, you might be able to write most simple automatizations yourself w/o coding C.
Note that in this context it isn't well placed in a 6d thread anymore.
Hi Guys,
I have just installed 1.1.6 FW and updated ML.
As I would like to help you guys in testing, first thing I did was running card speed benchmark. Two issues noted:
1. after a couple of seconds, display turned off and generally benchmark terminated
2. during secon try i ocassionally pressed any buttons to keep the display on; benchmark finished but no BENCH0.something file was saved.
Any hints?
I just bought my 6d and it came with 1.1.6, I need magic lantern for video can I degrade to firmware 1.1.3?
any help is definitely appreciated.
Thank you,
Jack
Quote from: JackMasonCo on May 16, 2015, 08:37:12 AM
I just bought my 6d and it came with 1.1.6, I need magic lantern for video can I degrade to firmware 1.1.3?
any help is definitely appreciated.
Thank you,
Jack
https://builds.magiclantern.fm/#/
Just follow the instructions
If you want to use the nightly build for 1.1.3, just download it, it contains a 1.1.3 firmware update file.
To downgrade to firmware 1.1.3, just use the firmware update which is in the download.
One thing I was not clear on after reading the docs -- if I want to pull down the latest nightly build of 6D 1.1.6 and put it on the card (which already has a prior build), do I need to re-run the firmware update? Or is putting it on the card enough?
Delete Autoexec.bin and ML directory from card. Extract files for 1.1.6 and copy contents to card. Startup cam.
Thanks Walter. There were no problems; after re-applying some ML settings, I'm back up and running. :)
Hi Guys
I have just got my 6D after using a 600D (with magic lantern) for the last 3 years. My 6D came with 1.1.6 installed so I downgraded to 1.1.3 to install magic lantern. I have just come across this post, am I right in thinking I can now upgrade to 1.1.6 and download this build? It seems the firmware upgrade was fairly small and no one is noticing any major issues with ML running on 1.1.6?
Ryan
Hi folk.... boy I think I am in trouble....
I forgot to take off ML from the SD card during the firmware upgrade and now after the upgrade.... The 6D now does not turn on...
OMG...
Is there anything I can do?? Or I must bring it back to Canon??
Thanks for any feedback!!!
Do detail exactly what you did.
you had what in the camera?
you had what on the card?
you did what?
Ryan,
I've only had it on my 6D (1.1.6) for a couple weeks, but it has given me no problems.
I have not tried any of the RAW/video stuff; I mostly use the Focus Peaking, Magic Zoom, and the ETTR hint meter, and the like.
There is a separate download link for the 6D 1.1.6, posted a couple of times somewhere in this or the other forum.
Steve
Thanks Steve. I'm assuming that's the link from the first post?
If so I will give it a download tonight and try it out. Will obviously report any issues. I'm the same, I just want focus peaking really and the crop marks, need to try RAW video too
Hi folks, can i copy my 1.1.3 nightly settings file to the 1.1.6 folder?
Yes, you can copy all the settings from the settings directory.
Quote from: wss on May 18, 2015, 06:22:47 PM
Hi folk.... boy I think I am in trouble....
I forgot to take off ML from the SD card during the firmware upgrade and now after the upgrade.... The 6D now does not turn on...
OMG...
Is there anything I can do?? Or I must bring it back to Canon??
Thanks for any feedback!!!
First, take out the battery and the card. Then re-insert the battery and turn on your camera without a card. Does it work?
Ryan,
The first post in this forum, Yes. 8)
Hope it goes as smoothly for you as it did for me.
Steve
To developers: What about new features in ML for 6d 1.1.6? Audio features is still not implemented. Framing in MLV for 1824*xxx resolution is incorrect. Pressing Zoom button while recording MLV crashes the camera. Level indicator is green only in center, why?
Hi,
first of all thank you so much for investing your time and knowledge. I do have to say you seem to have a good taste in local radio stations ;-)
I've been playing with ML on 1.1.6. for a couple of days already and so far everything is working just fine for me (I mostly use it for the Focus Trap).
However, today I managed to drain my battery completely and discovert a strang behaviour. When the camera powered off due to the lack of energy, the LED and the empty-battery-indicator symbol on the shoulder display kept flashing indeffinetely eventhough I switched the camera off. I swaped the ML-SD Card with a regular one and it stopped. But when I put the ML-SD Card back in, the LED and symbol started to flash again though the camera was still switched off.
This happened never before and only occured now after I updated, therefore I thought this could be connected to ML. Definetely no dealbreaker though ;-)
Once again: awesome work!
Greetings
Dennis
Check Prefs tab -> Warning for bad settings. Anything ON there?
Quote from: grey on May 20, 2015, 06:24:11 PM
To developers: What about new features in ML for 6d 1.1.6?
It's "just" a port, therefore there won't (and shouldn't) be any new features in it. We need to take small steps. The main reason for the port are the auto focus bug fixes by Canon. Bugs that are in ML for 1.1.3 as well need to be found, but can be fixed later.
Quote from: grey on May 20, 2015, 06:24:11 PM
Audio features is still not implemented.
The new sound system is supported. It does not make sense to implement the old one when a new one is already in development. Once new-sound-system is merged, everything should just work.
Quote from: grey on May 20, 2015, 06:24:11 PM
Framing in MLV for 1824*xxx resolution is incorrect. Pressing Zoom button while recording MLV crashes the camera. Level indicator is green only in center, why?
Are those 1.1.6 only or do they happen with 1.1.3 as well? Has anybody else experienced the crash?
Crash on zooming while recording in MLV happened a lot to me, on 1.1.3
Has to do with global draw settings in the raw recording menu, it must be set to allow or something.
When global draw settings are ok, you can record and press zoom without crash (on 1.1.3)
Just did a quick test, the camera freezes here as well when the zoom button is pressed during MLV recording.
Global draw OFF or Allow doesn't make any difference, even if I disable it in the Overlay menu. MLV_snd loaded or not also doesn't matter.
The camera locks up, but the AF keeps working. Eventually, Err 80 shows up. The LCD stays on, even if the camera is switched off, I have to pull the battery.
You did try both global draw settings?
There's on in the 3th tab in the ML menu, Global draw - ON, all modes.
And there is one in the raw video(MLV) menu, Global draw - Allow.
The settings above work for me on firmware 1.1.3
Although I must say that I have the option magic zoom enabled, so pressing zoom while recording gives me the magic zoom 1:1 window.
Without the right global draw settings, the 1.1.3. build also crashes on pressing zoom with magic zoom enabled while recording.
Yes, I tried all settings. It doesn't seem to matter with 1.1.6.
Hi Folks
I am new to the ML forum, but from some experience of other forums, it seems that people ask a question via a new thread, ans often get told to look at some other thread previously posted, and then other times, someone asks a question within an established thread, and get told off for hijacking the thread. So, my apologise if I am one of the above, and I hope I am asking in the right place.................
I have been a Canon user for some 30 years, and yesterday spashed out and upgraded from a 50D to the 6D :D
I have heard of ML for a long time but as yet never gotten round to trying it.
My issue is 2 fold:
1: I have that annoying issue with the GPS, remaining on and draining the battery, so ML is the answer as I believe you can use ML to overcome that and trun GPS off properley when turning the 6D off.
2: My new 6D is of course pre loaded with Firmware 1.1.6. A: Is it now reasonable to believe that using ML with the Firmware 1.1.6 is OK B: From what is said on the ML downloads page for the 6D download (Make sure you are running Canon firmware 1.1.3. (not latest!)) I am assuming that maybe there is a different file to download, so please can someone give me the 'easy' guide as to what I need to do to install this ML for 6D'.
Adge
The safe way (if there is any with ML :P ) is to go to the downloads page.
Then click the button 'Download the nightly builds' and download the latest 6d 1.1.3.
Inside your download is a firmware update to 1.1.3.
You also need to make your SD cards bootable.
Here's the complete install guide:
http://wiki.magiclantern.fm/install
Thank you Levas.
The following 3 lines do confuse me though:
Make sure you are running the right Canon firmware version, specified on the download page
You can check your firmware version by setting your mode dial to Manual (M) and looking in the Canon menu.
Nothing bad will happen if you try to run ML on a different firmware version - the card LED will start blinking and you'll have to take the battery out. Magic Lantern checks firmware version before attempting to run.
Does that mean I have to change my camera Firmware version from 1.1.6 backwards to 1.1.3 for it to install? Or is it simply telling me that with 1.1.6, when the LED starts blinking, I remove the battery, put it back, and the install will occur?
Thank you.
Adge
Quote from: trinitypics on May 25, 2015, 07:06:45 PM
Does that mean I have to change my camera Firmware version from 1.1.6 backwards to 1.1.3 for it to install?
Yeah that's exactly what it means u need to downgrade ur firmware to 1.1.3 if u've downloaded ML from the nightly builds.
Unless u're trying ML for the firmware 1.1.6 that u can find in the 1st post
Yup, what keepersdungeon says.
Use the firmware file that came with the magic lantern download, it's the .fir file.
You can put it on a SD card and and run the firmware update on your camera(it's in the canon menu, see your camera manual).
If you wanna go back to 1.1.6, download the firmware update from the Canon website. (but then 1.1.3 magic lantern won't run anymore)
Quote from: Levas on May 25, 2015, 07:56:20 PM
Yup, what keepersdungeon says.
Use the firmware file that came with the magic lantern download, it's the .fir file.
You can put it on a SD card and and run the firmware update on your camera(it's in the canon menu, see your camera manual).
If you wanna go back to 1.1.6, download the firmware update from the Canon website. (but then 1.1.3 magic lantern won't run anymore)
See first post for ML for 1.1.6. It should have about the same bugs as 1.1.3, otherwise feel free to contact me with details. I'll start fixing them (and adding new features) once 1.1.6 has been merged. If everybody decides to use 1.1.3 instead, there will be nobody testing the fixes anyway. ;-)
Quote from: trinitypics on May 25, 2015, 07:06:45 PM
...
Does that mean I have to change my camera Firmware version from 1.1.6 backwards to 1.1.3 for it to install? Or is it simply telling me that with 1.1.6, when the LED starts blinking, I remove the battery, put it back, and the install will occur?
Thank you.
Adge
Hi Adge,
You can safely run ML with the 1.1.6 firmware. Just download the nightly-like zip from the first post.
It works fine :-)
Hi, I just would like to report that I upgraded my 6D's firmware version to 1.1.6 and reinstalled MagicLantern afterwards, with no issues whatsoever.
Thanks for the great job,
Albert
Coming from 1.1.3 Do you simply fomat card with ml on, then update firmware to 1.1.6 and then put ML for 1.1.6 on your card?
Thans in advance
Thank you for your time spent on this already.
I had a feature on my 60 magic lantern that allowed F and ISO ramping for sunset to night sky timelapses etc...
Is this on the to do list?
Would save me getting the rasbery pi kit into the mix.
Will also be testing the latest out this weekend, hoping the weather is nice.
Please help!!! I have been trying to downgrade back to 1.1.3 but when I try to, with the ML-6D113.FIR in the nightly zip, my camera briefly says loading with the gray screen, then goes black and the LED flashes! How do I get back to 1.1.3?
When initially trying to downgrade back to 1.1.3 i literally had to uninstall ML 1.1.6 to even be able to get 113 on my card!
HELP, i'm stuck on 1.1.6 with no ML
Format card using cardreader.
Format card using cam.
Copy Canon's firmware 1.1.3 to card.
Run firmware update from canon's menu.
Delete Canon's FIR from card.
Copy extracted nightly build content (for firmware 1.1.3) to card's root.
Run firmware upgrade.
Is there a problem with "White balance" in ML1.1.6 ?
With ML 1.1.3 on my 6D, using ML white balance function (not Canon one) results where ok, but now, outside/inside/anywhere the "White balance" is tinting hard blue/green, no matter what.
Is there anything I'm doing wrong here?
Quote from: Walter Schulz on May 30, 2015, 06:18:53 AM
Format card using cardreader.
Format card using cam.
Copy Canon's firmware 1.1.3 to card.
Run firmware update from canon's menu.
Delete Canon's FIR from card.
Copy extracted nightly build content (for firmware 1.1.3) to card's root.
Run firmware upgrade.
I understand that, where do I get 113 from?? The one that comes in the download is modified right? As it does not seem to work.
Look at the opening post of the 1.1.3 thread.
Quote from: erox76 on May 31, 2015, 10:10:22 AM
I understand that, where do I get 113 from?? The one that comes in the download is modified right? As it does not seem to work.
http://www.magiclantern.fm/forum/index.php?topic=3904.0
Quote from: keepersdungeon on May 31, 2015, 10:13:40 AM
http://www.magiclantern.fm/forum/index.php?topic=3904.0
Thanks SOO much! That scared me!
Just tried it out yesterday (1.1.6), seemed pretty solid, camera only locked up once and that was while playing arkanoid. It was my first time using the dual-iso module, and it looked like it was trying to alternate the light version and the dark version when it popped up after shooting, but failing miserably, i'm not sure what normal behavior for dual-iso looks like. Also... should the various overlays (highlights, focus, etc) be visible during normal playback or only when the camera first reviews the image after it's shot?
http://magiclantern.fm/forum/index.php?topic=7139.0
http://magiclantern.fm/forum/index.php?board=56.0
I hope I understand the upgrade of my firmware correctly going from 1.1.3 to 1.1.6.
I've had 1.1.3 installed for the last few years and it's worked fine. I want to upgrade to 1.1.6.
It appears that all I need to do is:
1. Upgrade 6D's firmware to 1.1.6
2. Copy the following over to my SD card
a. Autoexec.bin
b. ML directory
c. ML-6D116.FIR
Is that the necessary steps with a camera that already is using 1.1.3?
thanks
Although have been a Canon SLR/DSLR user for a very long time, have only just discovered Magic Lantern and decided to give it a try in my 6D. Although I have played around with it very little at the moment, have found that the Help files are missing. I admit that because they were PDF files, I didn't copy them across to the SD card when I installed ML initially. I have since copied the unzipped help files across to the card but still nothing comes up when I click any help topic. Any ideas?
Yes, read nightly build instructions ...
=====
What are the disadvantages of nightly builds?
[...]
- No documentation - the only help for new features is a small line of text, and ML source code.
=====
BTW, regarding the menus disappearing quickly in LiveView, there is an old post (10/24/12) by A1ex on the subject of AF Confirm Chips, on cameras with newer than Digic4, where the menus were closing quickly. (Grasping at straws here, but I thought I'd mention it in case there is a hint of a clue in there somewhere.)
About 10th post on page 1/1:
http://www.magiclantern.fm/forum/index.php?topic=3312.0 (http://www.magiclantern.fm/forum/index.php?topic=3312.0)
To be clear, I'm not saying that the presence / absence of the electrical contacts causes it. (In fact, on my 6D, the timeout is the same 6 seconds whether a lens has the contacts or not). But if the 5D3's AF logic was sending some signal one to two seconds (after the menu button press), maybe there is something in the 6D sending a signal 6 seconds after the last button press. (What waits 6 seconds in the 6D, I wonder.)
Also, although repeatedly pressing the Q button will NOT delay the timeout at all, spinning the back control wheel will delay it indefinitely, until about 6 seconds after you stop.
First post in here, just downloaded and installed ML 2 days ago, just became a member of the forum.
All I can say is 'holymotherofgod', this just opened the door to what my 6d will do!
I just bought a 6d three weeks ago, stepping up from a 7d. I am interested in getting started in astrophotography, and needed an intervalometer. After weighing all the options (and figuring out the risk-to-reward ratio), I decided on installing MagicLantern. This meant installing 1.1.3 on the body, which probably took the longest, as I had real fun trying to find it!
I don't shoot video, just stills. Already the ETTR and dual-ISO features have me HOOKED. Amazing the dynamic range that exists on the camera, it just needed to be unlocked.
I am not very computer-savy, but within a less than an hour, I downloaded and installed CR2HDR, and BarracudaGUI, just for post-processing the dual-ISO files, which I then play with in Lightroom6. Easy, and sweet results.
Haven't had time to try the 1.1.6. ML.
But what did you early beta testers find out ?
Does it work as good as 1.1.3 or are there some things missing/ not working in 1.1.6 compared to 1.1.3 ?
If it works as good as 1.1.3, maybe 1.1.6 can be put on the nightly builds ?
And a very good morning to you, too!
Top of page -> Downloads -> Download nightly builds -> 6D.116
Missed that :P
Just the first day it's availanle...
Does it offer the same functionality as the 1.1.3?
Might try 1.1.6 later today too. Is it working okay for everybody???
Will try it soon. First time to uninstall magic lantern, format all the cards, update the firmware and after that reinstall magic lantern.
Just format one card in cam (Q=delete ML option), update Canon firmware. Delete Canon firmware, copy latest nightly build contents to card and run firmware update.
On other cards it is sufficient to delete ML directory, *.FIR and autoexec.bin and copy extracted nightly build contents to cards.
I should have written: First, time to uninstall.
Everythings works as it did before. I have a new one, Load H264.ini in video mode, but it is emty.
Quote from: Sapporo on June 21, 2015, 12:42:12 PM
I should have written: First, time to uninstall.
Everythings works as it did before. I have a new one, Load H264.ini in video mode, but it is emty.
This should work as for the 5D3 and loads bitrate settings from ML\H264.ini. The tragic lantern bitrate functions had been removed from 6D113, so I thought it may be a good idea to at least enable .ini loading (again?) in 6D116, as it seems way more safe.
See for example H265-alli.ini (https://bitbucket.org/hudson/magic-lantern/raw/db3ebdf8fd056772f058f9ac88d7773009708573/platform/5D3.113/H264-alli.ini) and H264-ipb.ini (https://bitbucket.org/hudson/magic-lantern/raw/db3ebdf8fd056772f058f9ac88d7773009708573/platform/5D3.113/H264-ipb.ini) (for 5D3).
Quote from: Sapporo on June 21, 2015, 12:42:12 PM
Everythings works as it did before.
Yippeee! Clap your hands for the work of Maqs and JLGW! And thanks to Alex for clicking the "Accept pull request" button! Popcorn! :-)
According to the Canon webpage having the firmware update, it appears that the Micro AF settings can be zeroed:
http://usa.canon.com/cusa/professional/products/professional_cameras/digital_slr_cameras/eos_6d#DriversAndSoftware
> From Canon:
Please note:
If the firmware is updated from version 1.1.3 or before, the following setting will be reset to default.
Menu > Custom Function> C.Fn II: Autofocus > AF Microadjustment> 1: All by same amount
However, that doesn't seem to have happened with the lens now on the 6d ... settings were retained (whew).
And the Build June-19 seems happy with 1.1.6, but that's just after a minute or so of quick testing (smoke test?).
Quote> 2. Copy the following over to my SD card
a. Autoexec.bin
b. ML directory
c. ML-6D116.FIR
Is there such a file as ML-6D116.FIR? I didn't notice it with the June-19 build. Unnecessary even if it does exist somewhere?
Updated install instructions are in the OP and the download page.
FYI: I updated my GPS Info module (http://www.magiclantern.fm/forum/index.php?topic=11209.msg108967#msg108967) to support 6D.116 in addition to 6D.113.
Just wondering... does FPS Override work on this yet?
love Magic Lantern on my 6D but hate not being able to bump down to 1fps and focus when shooting astrophotography like on my t2i...
116 users: any problems with using 3d party batteries? I read somewhere canon totally blocked to use it.
I tried two different 3rd party batteries and no prob so far. Didn't even get the msg that most talked about.
No problems from my side also.
What about sound in this version of ML?
This is just a port ...
Was meant as an answer to grey. New sound system still in development.
gotcha... what is a port? :o
https://en.wikipedia.org/?title=Porting
gotcha. thanks. so im guessing the original coding is for the 5d3?
Grey asked about porting ML from 6D.113 to 6D.116, I'm sure.
ML's origin is 5D2 with roots to CHDK.
Quote from: grey on June 25, 2015, 06:21:32 PM
What about sound in this version of ML?
For sound in the nightly, we need to wait for new-sound-system to be merged. Otherwise you'd have to compile a version by hand and merge in the new-sound-system branch. Maybe you can find somebody who's willing to share his/her compiled version every now and then.
No problems here with the third party batteries I was using with 1.1.3.
I'm using two Minadax third party batteries (beside the original one) and have no problems so far @firmware 1.1.6
Hello, I'm new to the ML. I have 6D and I'm looking for the Audio menu in 6D ML but there isn't one.
I'm trying to use Audio from USB port without getting black screen when connecting USB connector.
Any ideas?
I tried using 2 different after market batteries, one I don't even know the manufacturer, the other is a Wasabi . . . neither one of them are recognized and each gives me a different message when I power up:
Unknown - "Cannot communicate with battery, Use this battery?"
Wasabi - "Communication with Canon LP-E6/LP-E6N battery is irregular. Continue to use this battery?"
They power the camera if I choose to continue but I'm not sure how correct the battery percentages are. I'll stick with the original OEM Canon batteries just to be safe.
Mine are two Patona batteries and no problem whatsoever. I almost bought Wasabi, good thing I didn't ☺
Quote from: thedvsmonkey on June 27, 2015, 07:36:26 AM
I tried using 2 different after market batteries, one I don't even know the manufacturer, the other is a Wasabi . . . neither one of them are recognized and each gives me a different message when I power up:
Unknown - "Cannot communicate with battery, Use this battery?"
Wasabi - "Communication with Canon LP-E6/LP-E6N battery is irregular. Continue to use this battery?"
They power the camera if I choose to continue but I'm not sure how correct the battery percentages are. I'll stick with the original OEM Canon batteries just to be safe.
I have the same warning every first time I start the camera after inserting the battery, but I can choose "yes" and the camera works just fine. I don't think that there's any further impact.
Yes, I agree. I choose yes/continue and the camera works just fine. I would just be wary of the percentage left. I use the Canon batteries first then keep the other two for "just in case" scenarios.
That warning started after you instaled ML or it was there also before?
Do I understand it correctly that custom focus patterns are not available for Canon EOS 6D? This would really be a pity!
Thanks
Lory
https://builds.magiclantern.fm/#/features
Thank you, will try NightBuilds!
Still experiencing this issue (http://magiclantern.fm/forum/index.php?topic=15220.0) with 1.1.6 build :-\
Hi
why i can,t find audio options in ml in 6d
i need it :'( :'( :'( :'( :'(
i was have ml in 60d
I can fairest my choices in audio and can enter headset and hear the sound
But here I can,t find these options
So why??????
I want a solution please :'( :'( :'(
It did that before ML installed in both 1.1.3 and 1.1.6. Again, no big deal.
hi
i have been with the 60D with ml and i just love the audio controls there.
i cant find it in my 6d, any idea how to incorporate that in?
Current state: there are (almost) no audio features implemented.
Nightly ML for the 6D has almost NO audio support yet (with audio meters being an exception, see feature page (https://builds.magiclantern.fm/#/features)), however there's a new-sound-system branch (https://bitbucket.org/hudson/magic-lantern/branch/new-sound-system) that fully supports 6D.116 and can help bringing more audio features to the camera. I only helped implementing here what I could test, so at least playback (e.g. beeps), recording and input source selection are supported. In theory, as the audio ic is the same as in the 5D3, everything available for the 5D3 should become available as well, as long as it uses the new-sound-system API (g3gg0: correct me if I'm wrong). The new sound system is still under development and not in the nightly yet.
I don't use the camera for filming, which is why I don't have any audio equipment to test the more advanced features. Therefore those features are not on my to-do list. As you can hopefully understand, I don't want to make code or binaries available to the masses that are not tested extensively, since I don't want to risk being responsible for bricked cameras.
Of course, anybody willing to contribute to ML is very welcome. You can be the one to change this. ;)
thanks maqs
hopefully the new sound system will arrive soon.
the only help i can offer is donations...
no codeing skills
Just noticed that H264.ini was included in this nightly build. Could anyone explain more about this setting? Does it work with normal recording, or MLV RAW? Does it actually improve the quality of footage? (e.g decrease compression & increase quality). It seems to be a lack of information in regards to this setting.
Many thanks!
Overall, is it safe to say magic lantern is working as well as it did on 1.1.3? No major issues or anything? Is there any need to downgrade firmware anymore?
My question also, and as I see most of the problems are video related and I really rarely use camera for video. So is there any photo related issues?
Hi,
I have a Canon 6d and used magic lantern previously and worked great. I updated to 1.1.6 and downloaded the latest build, and now I'm getting the error message "movie stopped automatically" or It stops after a few seconds.
Forums said it was the card so I got a 280 mb/s card and still having the same issue.
ML worked on this camera before... what can I do to fix this?
It was and still is happening to me on my old T3i/600d, bought faster card and it was slightly better. Without ML all was ok.
Quote from: toursbrun on July 07, 2015, 02:12:51 PM
Hi,
I have a Canon 6d and used magic lantern previously and worked great. I updated to 1.1.6 and downloaded the latest build, and now I'm getting the error message "movie stopped automatically" or It stops after a few seconds.
Forums said it was the card so I got a 280 mb/s card and still having the same issue.
ML worked on this camera before... what can I do to fix this?
Sorry to tell u but 280mb/s is kinda useless for the 6d, the cam can only rec at 40mb/s or 45 max.
If u're recording in raw it's normal the recoding stops after few seconds, it u want more time u need to lower ur resolution or disable raw recording and use H.264
@nikonja: H.264 recording with 600D will require 6 MByte/s write rate. You're mixing apples and oranges.
@toursbrunn: If it is a Sandisk it will have quite mediocre performance in UHS-I mode. Write rate in this mode will be about 46 MByte/s which is about half the performance UHS-I is able to deliver. Other UHS-II cards will do better but max out at about 90 MByte/s (give or take) in UHS-I mode.
Bottleneck when used in 6D is still SD card interface in cam. As keepersdungeon wrote.
But I had that problem when I did normal movie record not raw. After I removed ML all was ok, and than i put it back and same problem is back.
Quote from: nikonja on July 07, 2015, 02:32:34 PM
But I had that problem when I did normal movie record not raw. After I removed ML all was ok, and than i put it back and same problem is back.
Did u disable raw/mlv recording module?
I don't think so, will try when I get back home.
Anyone faced these problems b4?
1-Some times if u were taking a video and u switch to photos and try to focus the cam says it's busy and doesn't focus until u turn it off and on.
2- while in video mode, and the LCD screen dim light goes down, the brightness won't come back up no matter what u do, also need to turn off and on
Thanks
The "busy" bug seems to be common from builds starting from May. It started from 113 builds. Random thing, sometimes it can work fine for hours, sometime it says "busy" and you have to turn camera off. This is a bug, has nothing with "busy" message when buffer is written to card.
Quote from: KelvinK on July 14, 2015, 09:15:59 AM
The "busy" bug seems to be common from builds starting from May. It started from 113 builds. Random thing, sometimes it can work fine for hours, sometime it says "busy" and you have to turn camera off. This is a bug, has nothing with "busy" message when buffer is written to card.
Oh ok, it never happened to me b4. Thanks for ur reply
Quote from: keepersdungeon on July 14, 2015, 12:32:32 AM
Anyone faced these problems b4?
I don't do the video thing and thus haven't encountered these before. One question though: Is this with vanilla Canon h264 video, or with h264 and ML tweaks, or with a custom ML raw video module?
In any case, imho good thing 6d.116 is merged and there's more widespread testing - with the multitude of configs and use scenarios out there it's virtually impossible to finalize some beta build only through a handful of daring testers compiling it themselves or grabbing it of a buried forum thread.
Quote from: Marsu42 on July 16, 2015, 01:56:42 PM
I don't do the video thing and thus haven't encountered these before. One question though: Is this with vanilla Canon h264 video, or with h264 and ML tweaks, or with a custom ML raw video module?
In any case, imho good thing 6d.116 is merged and there's more widespread testing - with the multitude of configs and use scenarios out there it's virtually impossible to finalize some beta build only through a handful of daring testers compiling it themselves or grabbing it of a buried forum thread.
Was using MLV
Apologies if this bug has been discussed previously, but I just upgraded from a T3i to a 6D and don't recall this happening on my old camera.
When I half press the shutter to meter (in M mode), the light meter shows for a split second and then is covered up by the bottom bar in ML view (the one with shot settings, battery level, etc.).
Not sure if this is a known bug or not but I figured I'd shoot it out there!
Hi there!
I understand there are no audio features currently available in the nightly builds of Magic Lantern for the Canon 6D. Is there any suggestion about how to get them until they become fully available in the nightly builds?
Install the "new-sound-system" branch? Any other options, besides the "wait and hope"?
thanks!
Quote from: giocomai on July 17, 2015, 10:02:36 PMAny other options, besides the "wait and hope"?
The nss branch currently doesn't even merge, there's a conflict in mlv_sound and the collisions are such that I personally cannot figure out what is vanilla-updated or nss. If you look at the commits, it's safe to say w/o new dev resources you're in for a longer wait: https://bitbucket.org/hudson/magic-lantern/branch/new-sound-system
Quote from: giocomai on July 17, 2015, 10:02:36 PM
Any other options, besides the "wait and hope"?
Other than that specific mlv module, I can offer to share my personal 6d build with nss on a 100% absolutely strictly "no warranty at all" and "no questions asked ever" basis if forum policy allows for it.
The build works fine for me and Maqs somewhat tested a merged build, too - that's why my idea is to merge the nss branch at least as a 6d compile-time feature so it goes straight to nightly as the lack of audio is such a severe drawback.
Ok, here you go if you want/need audio: UNSUPPORTED 6D NSS TEST RELEASE
1. Download official 6d nightly, unpack & install: https://builds.magiclantern.fm/
2. Delete /ML/modules/ directory to be on the safe side
3. Download my 6d nss build, unpack & overwrite: link removed
4. Smell the sensor burning :-p
This has been built with the latest gcc 4.9 and launchpad's libc_nano library, so I would advise against mixing these binaries with others with the stock toolchain. Don't expect me to update this regularly, if at all. I didn't test video, and it contains an older mlv_play module from the nss branch since I was unable to merge trunk to it. But stills shooting is just fine for me, and you can even listen to mp3 audio with your 6d now :-)
I have downloaded 1.1.6 and updated firmware on two of my 6D's - and then put ML 1.1.6 onto the SD. However, I cannot install it once it's on the SD card - the Menu is the same that came with the Canon. I reformatted a 32 gig and 16 gig SD and neither will Install the ML - although the 1.1.6 is on the card - and the firmware is updated. Please help - I can't install? I am a bit confused about all the talk about "downgrading to 1.1.3 - when it appears 1.1.6 is the latest version." Thanks much - going to Paris tomorrow - so I'm in a bit of a hurry.
Top of page -> User Guide -> FAQ
Hi there,
i update canon firmware from 1.1.3 to 1.1.6 and magic lantern too.
I have problem with features "FPS override". Sometimes the live view screen becomes all (sometimes partially) white.
To solve the problem, i should turn off the camera.
You know how to fix it?
thank you!!
Since I upgraded to Firmware 1.1.6, I notice that the GPS Power Save feature of ML behaves slightly differently. With 1.1.3, Power Save kept the GPS active as long as the 6D was switched on, and deactivated it when switched off. Now with 1.1.6, Power Save will deactivate the GPS whenever the 6D goes to sleep mode, even if it is on. As a result, each time the 6D is reawakened, the GPS has to look for the position again, resulting in loss of information due to the time it takes to make a fix.
Has anyone else noticed this? Is the change intentional and may we ask for reversal to the previous behaviour?
Quote from: riccalisci on July 24, 2015, 08:22:06 PM
Hi there,
i update canon firmware from 1.1.3 to 1.1.6 and magic lantern too.
I have problem with features "FPS override". Sometimes the live view screen becomes all (sometimes partially) white.
To solve the problem, i should turn off the camera.
You know how to fix it?
thank you!!
It's
"normal" casual behavior how it works on 6D, same with 113. Just press zoom button to get normal look.
Quote from: KelvinK on July 30, 2015, 11:44:00 AM
It's "normal" casual behavior how it works on 6D, same with 113. Just press zoom button to get normal look.
thank you very much KelvinK!
I don't have a audio Menu. Is this the way it is with the 6D?
I'm not sure if my external mic is used by the camera. Kinda sounds the same as the internal... How can I prove it?
Is there a way to level the audio manually without going into the canon menu?
Thanks
can you record sound using mlvrec raw video with the latest nightly build? also can someone whos expriemtning with raw video tell me, if its possible to make at least 7 minutes raw footage without any hickups in the ML? thanks
Quote from: Levthon on August 05, 2015, 11:56:51 PM
can you record sound using mlvrec raw video with the latest nightly build? also can someone whos expriemtning with raw video tell me, if its possible to make at least 7 minutes raw footage without any hickups in the ML? thanks
For longer recording U need to lower the resolution
i want to know whats the highest continues recording raw video time(and with what resolution) with sound on 6D . i want to record straight footage until my card is full (128gb)
Update on corrupt SD cards. It seems my problem lies in PNY memory. But now a bigger issue has cropped up. The recovery of these Sd cards use to be a snap with OS X up to Yosemite now with El Captain they totally revamped disk utility and it won't even fix the cards now. Had to locate an older Mac mini to fix the corrupt card. (One click on Repair) I will update as Apple keeps updating their software that is in public beta.
Quote from: Levthon on August 06, 2015, 10:07:27 AM
i want to know whats the highest continues recording raw video time(and with what resolution) with sound on 6D . i want to record straight footage until my card is full (128gb)
http://www.magiclantern.fm/forum/index.php?topic=6215.0
Try 1500x640
1280x720 resolution in combination with 24/25 frames per second is about the max resolution for continuous shooting.
My 64gb card has gone awry and demands format, in camera and in Windows. 32GB works as it should. I format it or what? It has/had Magic Lantern on it and I'm not sure how to wisely reinstall.
Format card in cam, copy extracted nightly build contents to card and run firmware update.
Jankocbek do you need the data on the card?
Thank you, i wasn't sure about the bootflag. Supermouse, thankfully no.
Does anyone have a solution for jaggy edges (moire) in raw video? is it possible to make it less visible in after effects?
Quote from: Levthon on August 12, 2015, 04:59:37 PM
Does anyone have a solution for jaggy edges (moire) in raw video? is it possible to make it less visible in after effects?
It's not just in raw mode. U can try with raw therapee but no matter what u do there will always be visible.(well u can take that part on a single frame and track ur video, but that doesn't work in all cases) so U need to avoid this by taking less sharp footages while shooting or get a filter for moire that u put over ur censor or crop mode. Gd luck
Avoiding would be possible, too:
- VAF in non-crop mode
- Crop mode
what is VAF?
Quote from: Levthon on August 12, 2015, 05:11:24 PM
what is VAF?
It's the filter I mentioned try to google it.
Or use search (left sided one between "Help" and "Profile".
found it. damn it costs a lot 330 euro. wtf
hey guys been awhile since i have updated my magic lantern on my 6D.
Im kind of lost basically, what i have is tragic lantern last build from sept 2014-09-26 6D FW 1.1.3,
I have the SD card set with working tragic lantern.
What is the process to update to 6D FW1.1.6 with the latest ML build?
Also if i update to the Latest ML build for FW 1.1.3, can i just replace the bin exe files on the SD card?
Is it worth going over to FW1.1.6? or i can just use the ML FW 1.1.3 build
Thanks in advance
Quote from: boogotti84 on August 13, 2015, 11:07:12 AM
What is the process to update to 6D FW1.1.6 with the latest ML build?
Update Canon firmware = 1.1.6
Delete ML dir, Autoexec.bin and *.fir from card and copy extracted nightly build contents to card.
Quote from: Walter Schulz on August 13, 2015, 12:32:27 PM
Update Canon firmware = 1.1.6
Delete ML dir, Autoexec.bin and *.fir from card and copy extracted nightly build contents to card.
Thank you, will try when im home tonight. what new goodies are there to play with since sept build?
https://builds.magiclantern.fm/jenkins/job/6D.116/changes
- Seamless MLV/RAW recording for > 30 minutes.
- Full resolution silent pics
- New installer
...
Abergon said:
QuoteNow with 1.1.6, Power Save will deactivate the GPS whenever the 6D goes to sleep mode, even if it is on. As a result, each time the 6D is reawakened, the GPS has to look for the position again, resulting in loss of information due to the time it takes to make a fix.
This is the same behavior as with 1.1.3. Then and now... the GPS in the 6D turns off when the camera goes to sleep OR when the 6D is turned off.
Jim in Boulder
hi friends there!
Just installed: magiclantern-Nightly.2015Jul02.6D116
can't find the audio ML menu??! it starts (from left) with the EXPO menu..really missing the manual audio control feature!!
tips?
Load MLV_REC.mo and MLV_SND.mo and restart camera. Not that much options, though.
https://builds.magiclantern.fm/#/features
thanks Walter, very sorry for that..it would be so useful!
Hello friends.
I have a problem with a sd card running this nightly but I don't know if magic lantern was the problem.
I have worked some days with it. Sandisk Extreme 32gb. Suddenly the camera doesn't work, I have to remove the sd, change it and remove the battery, then the camera turn on again.
When I put the sd in the camera again, the camera did not turn on. The pc does not recognise the sd too, and I cannot recovery data from sd.
I need to know if it's a problem from sd (2 week since I buy it) or might be a magic lantern problem with my 6D
Sorry for my bad english. Thanks for all.
P.S. I have one more of this Sandisk Extreme 32 gb, and I have no troubles
ML doesn't reprogram SD-card controller. So it's unlikely ML caused this error.
If you remove card too quickly after opening compartment door there is in fact a very good chance you might get corrupted data. After opening the door the cam will access the card and it doesn't matter if the cam is turned off.
It could be a fake/counterfeit card. This practice is very rampant nowadays. Make sure you only purchase SD cards from reputable, trustworthy sources. If you see a deal too good to be true, it probably is.
Trustworthy sources won't prevent from purchasing fraudulent flash memory. Dealers are not able to check each single item on the shelf and "product pirats" are sometimes not that bad matching visual/appearance.
My recommendation: Use h2testw (windows) or f3 (OS X) on all cards at home. This will tell if card's storage size is faked, which will cause data corruption if real size limit is reached.
I have not removed the card from camera. I just turn off the camera, when i tried to turn on came the problem.
I bought the sd card in amazon.es, and were distributed by amazon.es , so I know that they are not fakes. I have fully filled it in another works and nothing happened.
thanks for all... I still trying to recover the clips, and searching for the mistake.
There is nothing to be called trustworthy in flash memory market.
Always test your memory cards before going productive.
Even amazon has sold faked memory cards: http://petapixel.com/2012/12/09/beware-counterfeit-memory-cards-being-shipped-from-amazon-warehouses/
Has anyone else experienced any camera lock-ups? I don't think mine is related to ML, and actually doesn't even require that there be a card in the camera. but almost every time I pull my camera out of the bag now (it's gotten progressively more frequent over the last month), it will take one photo, and then hang, as if it's writing the image to the card. I've tried the newest versions of ML, no version of ML (factory reset), no card even, and it still always hangs. the LCD on top of the camera will flash "Busy" and if I switch the camera off, I get the blue disk saying that it's writing "1 image to card." But it never writes, and I eventually have to pull the battery to get it to reset. Any ideas?
Paul
have you tried different batteries? i've had some weird problems crop up with dying aftermarket batts.
Yes, I have 4 batteries, the original and another 3 more., and I have the same problem with them. I tried a lots of softwares as well as linux SO unsuccessfully. The memory card is dead I think.
You are right, it is very difficult to know if it is a fake, but the item is sold and dispatched by amazon, as well as packed by amazon and sandisk with a special cheap packaging, not the usual. Then Sandisk send the memory card directly to amazon and amazon pack the memory card. I Think that it is difficult to be a fake
Quote from: gatocosmico on September 01, 2015, 02:06:18 PM
Yes, I have 4 batteries, the original and another 3 more., and I have the same problem with them. I tried a lots of softwares as well as linux SO unsuccessfully. The memory card is dead I think.
You are right, it is very difficult to know if it is a fake, but the item is sold and dispatched by amazon, as well as packed by amazon and sandisk with a special cheap packaging, not the usual. Then Sandisk send the memory card directly to amazon and amazon pack the memory card. I Think that it is difficult to be a fake
If u format it, it will work but u'll lose all your data... Happened to me once and not sure what caused it, could be removing it fast after u open the lid
Guys, any suggestions about how to remove this black bar on top of the video frame?
(http://i.imgur.com/p5FwawT.jpg)
My 6D connected to external monitor via HDMI and i've tried all layout modes (16x9, 16x10, 3x2 etc) and to disable everything info except bottom and top lines.
Everything looks good on camera screen, only on external one i have this bar.
Awesome I'm excited to update to 1.1.6. Good work!
hi guys,
I understand that the current build can only record up to 120 frame (around 5secs) with RAW video (near 1080p). May I know if there's any stop-gap measure to record for at least 30s, but perhaps in compressed RAW mode? I would love to stick to the near-1080p resolution.
In addition, is there a way to use 1:1 crop mode without using RAW video? Couldn't find a way to enable crop mode without using MLV.
Nope. https://builds.magiclantern.fm/#/features -> Movie -> CROP_MODE_HACK
QuoteMy 64gb card has gone awry and demands format, in camera and in Windows. It has/had Magic Lantern on it and I'm not sure how to wisely reinstall
QuoteJankocbek do you need the data on the card?
Last time SD got corrupted I didn't need the data. Now it got corrupted at the end of a long timescape. Any solution to save the data?
Does anyone know where the seperate wav sound recoding feature has gone to?
I just updated to the latest nightly. The last update I done was a few months ago so guess a few things have changed, but sad to see some features disappearing.
?
Load MLV_SND.mo and do postprocessing to extract sound.
hmm, true. That could work. Guess I just miss the old way of doing it.
Speaking of mlv_snd.mo, is it normal to have 2 black frames at the end of ur shots when sound is on?
sound recording with MLV is a little longer than actual videoclip (at least with 6d that is ;)).
If you trim the audio file at the end to match your video, it's perfectly in sync.
Quote from: Levas on September 14, 2015, 04:11:00 PM
sound recording with MLV is a little longer than actual videoclip (at least with 6d that is ;)).
If you trim the audio file at the end to match your video, it's perfectly in sync.
Alright cool thanks @Levas!
I have been looking through the ML website, and trying to locate the resolutions. On a Canon 6D, when using ML, what resolutions are you able to utilize?
http://rbrune.github.io/mlraw/
is it possible to do in camera cropping of still images? AKA, Digital Zoom?
Howdy, new account here, but i've been reading these forums about every 6 months for the last few years. I've never installed ML. I know that cropping was an issue before but now see that it has been worked out for video. Hoping this means it is available for stills too. I need a 2x crop to make a 200mm lens a "400mm lens" ... don't need the extra pixels/resolution, just need straight out of camera crop.
edit: this question is 6D specific, I have older firmware right now, but am willing to update to 1.1.6
Guys, i just installed latest nightly on my 6D.
In 25 fps , and 50fps , its working fine. However, when in 24fps mode , in the upper bar , where it should be showing current FPS , instead od 23.976 , its constantly changing between 23.971-23.981.
Does it show with these numbers changing during playback on MLRV as well?
@hes gone, I just recently upgraded to the latest version of ML (2015-08-18) on my 6D, and used to do a bit of raw cropped video recording, but haven't come accross this feature with static shots. But I've not looked for the feature so it might be there.
I'm having naming prob on my cam for the photos instead of IMG_xxxx it's _MG_xxxx and same for dualIso instead of "Dual... " it's "_ual..." anyone knows how to fix this. Thanks
For movies it seems fine (raw or h.246)
Color Space aRGB -> _MG
Color Space sRGB -> IMG
Use Google, please. Or read page 140 of your manual.
Quote from: Walter Schulz on September 19, 2015, 05:27:57 PM
Color Space aRGB -> _MG
Color Space sRGB -> IMG
Use Google, please. Or read page 140 of your manual.
Of course, will do. Thanks anyway for your reply
Hey all - just a cpl questions I'm stuck on. I have 6d with 116 firmware and lates1 ML nightly build.
1) I'd like to shoot h264 thru ML but when I try to load h264 it says that the module not loaded. How do I access h264 or install it on ML?
2) If I shoot H264 can I adjust the bitrate - is it an improvement over stock Canon 6d video recording?
3) If I shoot H264 will it also record audio?
4) If I shoot RAW will I record audio?
5) don't kill me...but what is the difference between mlv_rec.mo vs mlv_snd.mo
THANKS!!
1. Don't activate RAW settings in Movie tab and you will record movies in H.264. No module needed.
5. https://builds.magiclantern.fm/#/features
2, I believe you can change the bitrate in the h264.ini file that you can load in Magic Lantern.
Also take a look at this page: http://magiclantern.wikia.com/wiki/Bit_rate
3, Yes, if you record normal h.264 it will record audio too, unless disabled in the Canon or ML menu.
4, Not by default, I belieave thats what the mlv_snd.mo file is for. Sound gets recorded in a seperate file as to video.
Remember that if you do shoot raw, your post work will take longer as there are a few extra steps you have to take before you can start editing the raw footage.
Quote from: 8k on September 24, 2015, 09:16:40 PM
Remember that if you do shoot raw, your post work will take longer as there are a few extra steps you have to take before you can start editing raw the footage.
The upside is that the other parts of the editing workflow are finished much quicker - because you can just record a few seconds of consecutive raw video on the 6d :-> (well, in a somehow reasonable resolution that is).
" I believe you can change the bitrate in the h264.ini file that you can load in Magic Lantern."
That's the problem; when I try to load the h264.ini file in ML it tells me there is no h264.ini file to load :(
Hi pointbob,
What's your end goal here?
I have a feeling just changing the h.264 bitrate isn't going to be enough. While it will give less compressed footage, I don't think it will get any shaper, like the Canon raw footage does. (and you'll also need a fast SD card, like with RAW).
The downside of recoding raw (with the 6D) is that you can get quite bad aliasing and the shot length and resolution is limited (read about it in the blog post below). But that aside the footage you get with raw is truly amazing to work.
Check out this blog post - http://djisupertramp.com/journal/canon-6d-video-raw-vs-h264/ (It's in French, but if you're in Chrome it will translate it for you)
--
As for the "no h264.ini file to load", that is because you need to create the file on the SD card, there are some examples floating around this forum, do a search. (I have never done this, so I can't really comment any further)
For plain h.264 recording, you dont need ML( with 6d that is)
The 6d has the ALL-i option in canon menu, 90mbit/s all-i h264 compression.
H264 wont be going any better/sharper than that.
For the best possible video image quality use magic lanterns mlv recording and accept the recording limits of about 10 seconds to 20 seconds per clip(SD card limit and depends on speed Sd card.
There's one thing though, for mlv/raw recording you do need to know your way around in raw image processing, otherwise your better off with plain h264
Your cam is configured to use Adobe RGB instead of sRGB.
Oooops, sorry, wrong post... :-(
Quote from: Levas on September 26, 2015, 01:15:01 AM
The 6d has the ALL-i option in canon menu, 90mbit/s all-i h264 compression.
To add another random comments: You have to give it to Canon, adding a 90mb/s video mode to a cam equipped with a 20mb/s card interface and a very small buffer nominates them for the "most useless specs" award :->
90MBit/s not 90MB/s...
Different things, 8 times different
90MBit/s = 11MB/s
Easy to handle for a 20MB/s card interface...and the 6d has even a 40MB/s card interface :)
Nothing wrong with 90Mbit/s h264 video
Most HD camcorders around only use 24Mbit/s H264
For reference, the panasonic GH4 use 100Mbit/s H264 for 4k recording.
So canon uses almost the same bitrate for HD, you do the math if 90 Mbit/s is enough for HD ;)
I have a question.
6D with firmware version 1.1.6 and ML version Nightly.2015Aug18.6D116
Apart from few bugs like ML menu going off by itself everything seems to work.
However, what I cannot figure out is why the card led keeps flashing.
can be seen at this YT link: https://www.youtube.com/watch?v=EsxIcOdN_hg
Timing of the blinking varies a little also, so I dont know what to think.
Googling around only suggest that it happens when FW version is not correct - but in that case the installation would hang, as I understand.
Any ideas ?
I install the last firmware (magiclantern-Nightly.2015Aug18.6D116) and didn't find the "silent picture" function. It isn't present now?
@V2lek random LED flashing on 6D is common thing/bug.
Quote from: oleg1959 on September 28, 2015, 03:35:57 PM
I install the last firmware (magiclantern-Nightly.2015Aug18.6D116) and didn't find the "silent picture" function. It isn't present now?
You did venture to enable the "silent" module :-> ?
Quote from: Levas on September 26, 2015, 10:02:53 PM
90MBit/s not 90MB/s...
Different things, 8 times different
90MBit/s = 11MB/s
Easy to handle for a 20MB/s card interface...and the 6d has even a 40MB/s card interface :)
Right, thanks for correcting me, mean of you to use strange denominations lime MBit/s for the simple people over here :-p ... and sorry everyone for spreading wrong information.
It was because my card did block when using all-i frames, but in hindsight that was when it was nearly full and probably badly fragmented - so in these cases it probably pays to have a card spec'ed far beyond the interface limit so it'll keep the speed until the very end.
Quote from: Marsu42 on September 30, 2015, 10:01:37 AM
You did venture to enable the "silent" module :-> ?
Why such question?
Looks like a hint to solve your problem. Why not answering his question?
Sorry, my English is very bad.
I only start studying ML. The "hi-res silent picture" function caused interest to me. Marsu42 say to me that this function is dangerous. It is interesting to me, why.
? Can't see anything in Marsu42's post about danger. In his last post he asked if you enabled "Silent.mo".
No danger here, i use it on my 6D ! 8)
Using ML is always dangerous :P
Always be prepared to take out the battery if things go weird 8)
But seriously, I'm using ML for two years now and only did the battery removement thing a few times.
I'll take time lapses with silent pictures and leave the camera for a few hours...it didn't catch fire, so I'll think it's reasonable stable.
Thanks for answers
Hello. I am new and do not know the English language because I support a google translate. Before you translate and read the whole thread about the body 6d I ask a few questions. I now have the camera 6d fimware 1.1.6., I'm going to shoot ML independent films / feature:
1. Is the ML 1.1.6 there is any problem with the audio via mini-jack input?
2. Are there any problems on video recording?
3. Should, however, return to fimware 1.1.3, if so, please detailed instructions, maybe there is a video on youtube with the instructions step by step how to proceed?
4. What should be the minimum speed of the card in writing, or 30 MB / s is enough?
5 Is there a link to the video on youtube how to set maximum parameters in the ML (manual) to get the best quality panoramic image?
::)
for maximum record time you need at least 40-45MB/s cards, it's a max write on 6d
Thank you for answering question- remaining 4 are only 4 questions :) Thank you in advance for your answer :) :D
Hi,
I think I may have found a bug.
I can't get the Arrow/SET shortcuts selection to work during movie recording. It works in live-view, but as soon as I hit record I can't change the selection anymore with the AF points button. The arrow itself works fine.
SET button is not assigned in Canon menu.
Could anyone confirm this, before I enter a bug report? Thanks in advance!
Ray
I have a new 6d and an older, the old recording over 30 minutes is no more than 51 degrees, but the new camera reached 60 degrees with 30 minutes to Magic lantern which could be?
pointbob, did you find any information to obtain better quality in video mode?
I'm looking for decrease compression & increase quality, without use RAW.
The movie quality on the 6D is very poor. :(
Moire is horrible. Video compression is too high.
Please, do you have information to setup a good compression?
Thanks.
I'm looked during hours to find any info about increase bitrate/quality in the 6D.
I found the bitrate control was deleted in ML's menu (because it's crashing the 6D).
But, I don't find any other information. I was thinking it's possible to create a h264.ini with good configuration in this file, but I don't found any information.
Please, do you know if it's possible ? If yes, how?
Thanks a lot.
Quote from: Jey on October 19, 2015, 09:30:07 PM
pointbob, did you find any information to obtain better quality in video mode?
I'm looking for decrease compression & increase quality, without use RAW.
The movie quality on the 6D is very poor. :(
Moire is horrible. Video compression is too high.
Please, do you have information to setup a good compression?
Thanks.
The moire for the 6d is normal, the only way to remove it is with a filter that u put on ur censor. Try to google it.
For h.264 u can use the All-I (low compression) that's the best u can have with it. Or just use raw from ML.
Hello, was using intervalometer with 5 second exposure (no AETTR) and a 7 second interval and faced a lot of bugs, for instant if I was taking one and stopped it by going to the menu and starting it again the cam goes crazy sometimes it Adds lots of noise and freezes or it will starts counting the 7 seconds after the image is taken not when the shutter is pressed. Is that something known or due to the new migration to 1.1.6. Thanks
"Long exposure noise reduction" at work by any chance?
Quote from: Walter Schulz on October 26, 2015, 07:50:45 PM
"Long exposure noise reduction" at work by any chance?
No it was off, sorry forgot to mention it.
I don't have a 6D at hand. Maybe others want trying to reproduce your issue.
And/or you want to check latest 1.1.3 nightly after downgrading.
Quote from: Walter Schulz on October 26, 2015, 08:10:56 PM
I don't have a 6D at hand. Maybe others want trying to reproduce your issue.
And/or you want to check latest 1.1.3 nightly after downgrading.
Alright, well thanks anw Walter
Are you using a (too) slow card?
7 seconds interval and 5 seconds exposure only leaves two seconds for writing the image to the card.
Normally this should work, but with a slow card...?
Quote from: Levas on October 27, 2015, 05:54:53 PM
Are you using a (too) slow card?
7 seconds interval and 5 seconds exposure only leaves two seconds for writing the image to the card.
Normally this should work, but with a slow card...?
I have the Sandisk extreme 60mb/s, it does 45 write speed, I think it's enough no? plus the 6d can't write faster
In that case, it's not your card. That should be fast enough to write the image in one second to the card.
Mirror lock up or self-timer on ?
Quote from: Levas on October 27, 2015, 06:14:16 PM
In that case, it's not your card. That should be fast enough to write the image in one second to the card.
Mirror lock up or self-timer on ?
The mirror wasn't locked up, the self-timer u mean the one for when u take a single image? I don't remember coz I used the 2 second timer and can't remember if I left it on... Hmmm it could be from that... Doesn't ML overrides it when u set the interval?
As far as I know ML only gives the signal that is the same as the photo-button-press.
So if the selftimer was on, ML gave a signal and then the camera waited 2 seconds because of the self timer.
Had som problems with mirror lockup in the past, I ended up with only half of the amount pictures I expected :P
Quote from: Levas on October 27, 2015, 06:30:30 PM
As far as I know ML only gives the signal that is the same as the photo-button-press.
So if the selftimer was on, ML gave a signal and then the camera waited 2 seconds because of the self timer.
Had som problems with mirror lockup in the past, I ended up with only half of the amount pictures I expected [emoji14]
Damn that sucks for the pics lol thanks for the info [emoji14], well that must be it for me,I must have left it on... it makes sense too. Thanks again for the help
Installed the latest ML from magiclantern-Nightly.2015Nov07.6D116.zip yesterday. It did pass a quick stability test with only MLV video & audio modules on and RAW recording worked fine. I gave it a try in the field shooting raw footage today. Unfortunately, after the first RAW MLV clip shot at 1824x776 / 24fps, 6D froze up with no response to any button press. Turned off the camera. Turned it back on and the warning message came up saying the card is not readable and a format is required. After the format, camera recognized the card and shot images and h264 video as usual without a hiccup. I couldn't reinstall ML since I didn't have it on my second SD card. Nor would I dare to risk losing any footage today. I can't reproduce the behavior now again. But it did happen to me before with a previous build a couple of times. The card is SD Lexar Pro 1000x. What would be the best procedure for reporting the issue with a corrupted card due to RAW recording? PC card reader does not recognize it and prompts for a format as well. Any chance of pulling log files? How would one restore any footage/images lost due this behavior?
Hi folks,
I shot a few MLVs today, and the final frame doesnt match the one displayed while recording.
I used 1536x768 2:1, and the frame displayed had a wide black frame, which I assumed is the final crop. It is not, the actual footage has a smaller angle of view. Bummer...
What am I doing wrong? Or ill have to live with it?
Update: Ok, feel stupid now. The issue comes from ML Raw Viewer 1.3.3. If I watch the file fullscreen it gets cropped. No issue watching in a small window.
Ive been using this software for months, and I havent come across this so far.
Anyone else noticed this?
Pronin:
Im no dev, but sounds like a faulty sd card. If u have valuable information on the card, dont write on it, because u could overwrite and lose something valuable. U will have to restore the partition table of your sd card. Effectively unformat it. :)
I havent used this software, but found a tut that seems to be fine. http://www.partitionwizard.com/partitionmanager/how-to-restore-partition-on-sd-card.html
csoller, thanks for a tip on the partition table restoration! I'll give it a try next time the card becomes unreadable.
Lexar Pro 1000x never had problems before with writing and reading on a "stock" 6D for over 5,000 frames (stills) for half year. It still performs well with no ML installed. I'll use another SD card as well to rule out the card poor compatibility with ML.
I do get a couple of black frames at the end of a RAW clip sometimes. Didn't pay attention at their resolution since I discard them (DNGs) before editing .
Keep a close eye on that card, no matter what manufacturer or model, they can go nuts very quickly...
If u disabled frame skipping and still have some black frames thats weird as well.
Im no dev, but I dont know of any reason a card shouldnt work with ml but without. I think the protocol is the same. Maybe a dev will correct me.
I would be scared to use it for production tho...
I have "Frame Skipping" disabled. FPS override is set to Exact FPS - 23.976. No more than 2 black frames get through sometimes. No big deal for me.
Quote from: csoller on November 09, 2015, 01:52:22 PMI would be scared to use it for production tho...
I wouldn't use ML on 6D for any valuable personal or production work yet. There is no stable version available for 6D. We are doing beta testing here.
I'm using ML FOR 2 years now on a canon 6d.
In my experience, the behaviour is very predictable.
Once you've tested the ML stuff you use on a certain ML build/version, it's for 99% safe to use without any problems.
So test the stuff you want to use, if it's working fine, don't switch to a newer ML versions.
I have two memory cards, long time I downloaded the newest ML version on one card.
And a tested version (which for me is considered stable) build on the other card.
If I want to shoot something important, I'll grab the memory card with the 'stable' build.
Hi all,
I just switch to the 1.1.6 with the last Nightbuild (on a 6D of course).
It works pretty good so far EXCEPT about a small but major issue concerning the headphone audio playback thru the SESCOM cable...
Until here, when I connected the USB, ML told me that a headphone was connected and I was able to heard the audio.
Now, when I connect the USB, the screen is turning black like I connect the HDMI cable for a external LCD screen.
I understand that this release of ML don't really need an audio menu but the possibiliy to have the palyback thru the USB IS THE BASIC FEATURE I need like a lot of people !
Do somebody can help me about it ?
Cheers
(http://static-malinadz.com/ml/RAW-iso6400-C-Log-001.JPG)
Are these weird artifacts at iso6400 in a form of color dots/stripes normal for RAW recording? This is not chroma noise. Noise reduction does not fix it.
At iso12800 IQ gets worse accompanied with severe banding.
In-camera noise reduction does not apply to RAW video recording.
Looks like artifacts caused by line skipping. You may want to use crop mode.
(You may add some details about settings and what we are actually seeing (processed footage?)).
@Walter Schulz
this short clip was recorded at 1824x776 @ 23.976 FPS.
I use MlRawViewer_1_3_3_win32 for raw conversion.
Similar artefacts are present in Audionut's iso6400 raw samples in this thread:
http://www.magiclantern.fm/forum/index.php?topic=11899.msg130716#msg130716
They appear around sharp edges of objects in focus. 6D's native H264 mode doesn't have them. I wonder if it's a know defect and is attempted to be fixed?
Here are two raw samples from me of a scene with a focus on a foreground and background:
6D, MLV, iso6400, 1824x776px @ 23.976fps
https://goo.gl/UhBUcl (https://goo.gl/UhBUcl) (170MB)
https://goo.gl/lpkOyW (https://goo.gl/lpkOyW) (163MB)
Pretty well known issue.
Please look up for artifacts caused by line skipping.
Canon's H.264 implementation uses rather strong de-aliasing algorithms. And that's why (together with other noise reduction + upscaling + sharpening) Canon's video output isn't holding up compared to other brands.
Try crop mode.
These artifacts happen more at higher iso's like 3200 and 6400.
It's caused by a combination of line skipping and dead/hot pixels (which only become hot/dead at the higher iso's and random, because they are moving).
You need software that deals with the dead/hot pixels.
This one will save your content ;D
http://www.magiclantern.fm/forum/index.php?topic=13152.0
Hey guys. I moved from a 550D to a 6D (116), and I am having some "issues" with the focus box in LV mode. On my 550D that white rectangle was present in auto and manual focus. Now with the 6D, once I select manual focus, it disappears.. Is this normal? and if yes, is there a way to make it appear in manual mode? My current workaround is activate the MagicZoom feature, and leave it always on, on focus box. That way I get a rectangle (even if it's with a zoom preview on small) to see where my focus point is.
ML is the only reason why I chose the 6D over a Sony a7. :) ( i use MF Samyang lenses, and ML offers much better flexibility.. the half shutter zoom-in is ingenious).
It would be great to be able to move that box much faster, because it takes quite a few clicks to get it from one part of the screen to another (holding the D pad won't work.. you have to press for each movement separately). So if you could implement a speed booster for that, it would be superb! like move 2x speed / 4x speed (like in zoom on playback).
Quote from: norbi_nw on November 16, 2015, 04:25:31 PM
Hey guys. I moved from a 550D to a 6D (116), and I am having some "issues" with the focus box in LV mode. On my 550D that white rectangle was present in auto and manual focus. Now with the 6D, once I select manual focus, it disappears.. Is this normal? and if yes, is there a way to make it appear in manual mode? My current workaround is activate the MagicZoom feature, and leave it always on, on focus box. That way I get a rectangle (even if it's with a zoom preview on small) to see where my focus point is.
ML is the only reason why I chose the 6D over a Sony a7. :) ( i use MF Samyang lenses, and ML offers much better flexibility.. the half shutter zoom-in is ingenious).
It would be great to be able to move that box much faster, because it takes quite a few clicks to get it from one part of the screen to another (holding the D pad won't work.. you have to press for each movement separately). So if you could implement a speed booster for that, it would be superb! like move 2x speed / 4x speed (like in zoom on playback).
It's weird, if I press and hold the focus points keeps moving. No need to press the arrow keys for each move
In manual focus mode? (in auto focus, the rectangle shows up and moves quite fast - would prefer even faster movement tho) If I use my Samyang lens the white rectangle isn't visible.. And the magic zoom box only moves 1 at a time, and not diagonally :/ (manual focus)
For quick focussing I use snap points for the focus box and the 'set' button.
You can activate snap points in 'focus box settings' in the ML 'Prefs' menu.
I have those too, but again, if you set it to 8 points + center, you have to press it quite a few times to snap to the right side and then the D pad to move up or down.. It's OK, but would be perfect with ability to change movement speed. The position of the eyes vary from shot to shot, and at f1.4, you can't risk to focus and then re-frame.
IF the white rectangle would stay ON in manual focus too (not only AF), then yes, it would move faster, because with AF lens the white rectangle moves faster and I can keep the D pad pressed and will still continue to move. Even diagonally.
But I doubt that is possible... so only workaround would be magic zoom box to move at same speed and continuously.
This method would shave off a good 2-3 seconds from every shot (with MF).
Hi.
Just downloaded 6d firmware. Noticed there is no Audio - Is this correct, or did I miss it? (I'm used to using ML of 5d MarkII...Thanks!
Audio is there but
Top of page -> Downloads -> Download nightly builds -> Features -> Audio section
I See. So we can see the meters, but can't adjust gain via ML, like in the 5d MII...is this correct?
Correct. Applies to all cams with DIGIC 5.
The 6d has standard build in option to manually set the gain in canon menu.
So in the canon audio menu, you can control gain manually.
I have seen videos on YouTube using focus stack bracketing and it will calculate the number of pics that will be take in the bracket based off your step setting between pictures. I have the latest build but it does not show this calculation. I am having to take the total steps in the bracket, than divided the number of steps between pictures to get number so I can input the number of pic's to be taken.
What am I doing something wrong here, or is this calculation not available on the 6D?
Has anyone been able to use focus peaking while recording in RAW? Seems like I can't make this happen...
No overlays at all or just focus peaking?
None: Movie tab -> RAW video (MLV) -> Global Draw ON
@ricky_005: You're still with us?
Thank you for your quick response. Just Focus Peaking. Wow. I'm usually hanging out on the FL Studio Forums. My first love is music production. Anywho, I leave Clear Overlays "Off" and turn on "Global Draws". It seems that it comes and goes randomly, but for the most part, it goes. I have to toggle Live View On and Off to bring it back sometimes. It is not very consistent.
Small update regarding boot method and task internals:
https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d
Hi All,
I need some help please.
1, I updated my canon factory firmware from 1.13 to 1.1.6
2, I Formated the SD card and copied the 3 pieces of ML 116 file
3, I updated canon factory firmware 1.1.6 to ML 116
It's wrote - It's DONE - please restart... etc...
I restarted but there is the canon menu again! No any ML menu only changed the SD slot red led flash in every 5-10 second...
What is the problem?
Thank you!
-széna
Press trashcan button after startup.
... :)
THX!
OK, I'm a beginer - I think it's a really useful information for beginers. It should to write the end of the install info maybe... :)
Thank you again Walter!
FAQ + Install Guide. See top of page.
Hello again... :)
No RAW video option in my video menu. What I do wrong?
SD card is sandisk ultra 32 mb/s 80mb/s - is it enought?
THX!
-széna
Quote from: széna on November 28, 2015, 07:18:59 PM
Hello again... :)
No RAW video option in my video menu. What I do wrong?
SD card is sandisk ultra 32 mb/s 80mb/s - is it enought?
THX!
-széna
Activate the module mlv_rec in modules then restart the cam. Make sure u activate the mlv_play for playback
Audio track (recorded with in camera mic) gets out of sync with video quite often on 6D when Use SRM Job Memory & Extra Hacks are enabled for MLV RAW recording.
Anyone else noticing this behavior?
Only thing I notice is that the audiotrack is slightly longer then the video track.
But if you trim of the end of the audio to match videolength it's perfectly in sync.
In my case it's worse - last seconds of audio track play in the beginning with the "actual" audio beginning somewhere in the middle of the video clip.
Upload a sample MLV file that exhibits the problem.
Uploaded a 27 seconds long clip in both MLV (825MB) and MOV (373MB) formats that conveys the out of sync issue really well.
Counting duration seconds:
https://drive.google.com/folderview?id=0BzDJkyUbS4xgR2RJZ0hscWtmVk0&usp=sharing
Ah the audio is messed up. Been there...
Depends on your software choice for MLV.
Mlrawviewer messes up my sound.
I'm using mlv_dump on OSX, this gives normal wav files.
Levas, thanks for the tip. It's the mlrawviewer in deed that is at fault. I tried RawFlow (http://www.magiclantern.fm/forum/index.php?topic=13338.0) for the same MLV file, and it extracted the audio with no out-of-sync issue.
Just asking since i am still a little unsure how I should go about it.
I installed magic lantern a long time back on my 6D with the 1.1.3 firmware.
But how do I update the firmware and magic lantern?
Sorry if it have been asked before.
Format a blank card in cam, copy Canon's firmware file to it, run firmware update with Canon's firmware.
Delete ML-card's ML directory and *.fir and autoexec.bin and copy extracted nightly build contents to card. Startup cam with ML-card inserted. Done.
Hello.
Somebody tried Advanced Intervalometer?
I've used the intervalometer. Works perfect.
Thanks for the answer.
Whether the module (adv_int.mo) downloaded from reference (https://bitbucket.org/dmilligan/magic-lantern/downloads/adv_int.mo) for a cam 6D will work? Confuses me that for different cameras at night builds there is the set of modules, not the absolutely identical.
?
Which nightly build (for which cam) contains a different set of modules?
I never loaded/used a module for intervalometer.
I'm using the standard magic lantern intervalometer, which is available in the 'shoot' menu.
Give it a try.
I wrote the module in question. Thread here: http://www.magiclantern.fm/forum/index.php?topic=8431.0
It extends the ML intervalometer with additional features, mainly having to do with ramping exposure parameters during the intervalometer sequence. It is probably not something that everyone would need, so I created it as an add-on module rather than submitting it to be part of the ML core. Therefore, this module is not included in nightly builds, it is distributed separately (which was the original intent of modules anyway). It should work with the nightly builds, but the only way for you to find out if it works is to:
Quote from: Walter Schulz on December 04, 2015, 04:30:46 PM
Give it a try.
If you have a specific problem with the module, it is probably better to post it in thread for this module (linked above).
I use the Advance Intervalometer module on all my cameras and works fine. Go ahead and give it a try @oleg1959!
Hi,
I have Sandisk ultra 80MB/s card in my 6D.
I can record only 5 sec in 1728x972 resolution.
Can me help somebody why is it?
THX!
-széna
Quote from: széna on December 04, 2015, 08:17:00 PM
Hi,
I have Sandisk ultra 80MB/s card in my 6D.
I can record only 5 sec in 1728x972 resolution.
Can me help somebody why is it?
THX!
-széna
6D can support max around 45 mb/s write speed. It's normal to get only 5 sec if u want more u need to lower ur resolution.
I think I just bricked my Canon 6D.
Here is the steps that I did:
1. I updated my camera firmware (Canon) from 1.1.4 to 1.1.6. Sucessful
2. I removed the Canon update from my SD card and put the ML files on it.
3. I ran the ML update and it finally said to restart my camera.
4. I removed the card, moved the ML files to my laptop machine.
5. I then replaced the SD card and turned my camera on.
6. Nothing happens. It seems very dead.
Is there hope? Or is my camera "bricked"? :-[
HELP!
Remove battery at once!
Second:
Either format the card in cardreader and run without ML
or
copy extracted nightly build contents to card and run ML.
Top of page -> User Guide -> Install Guide -> Very important
Ok, I found out what actually fixed the issue.
It seems that a full reset is needed before it would do anything. By removing the battery for 30 seconds and restarting with ML SD Card back into the camera, I was able to "un-brick" the camera. Once the card with Magic Lantern was run and the camera was reset, the camera operated normally. Normally means that the Camera would start with or without an SD card.
I hope that this is something that can help others with the same issue.
Thank you.
Heard that ML has motion detection, so I installed the Nov 15 nightly on my 6D. Everything works except frame-difference motion detection.
EDIT: Created an issue for this bug.
https://bitbucket.org/hudson/magic-lantern/issues/2418/frame-difference-motion-detection-always
Hi all,
I just switch to the 1.1.6 with the last Nightbuild (on a 6D of course).
It works pretty good so far EXCEPT about a small but major issue concerning the headphone audio playback thru the SESCOM cable...
Until here, when I connected the USB, ML told me that a headphone was connected and I was able to heard the audio.
Now, when I connect the USB, the screen is turning black like I connect the HDMI cable for a external LCD screen.
I understand that this release of ML don't really need an audio menu but the possibiliy to have the palyback thru the USB IS THE BASIC FEATURE I need like a lot of people !
Do somebody can help me about it ?
Cheers
I reported this in the bitbucket but i also like to share my experience with you guys here.
The nightlys for the 116 do not work well for me. I made one project and i had some struggles. Now switched back to 113 for my next project and things work way smother there.
The RecPicStyle only works at the secont take in the 116 bulds. At 113 it never failed me so far. If you shoot with cinestyle, wich makes your movies way more usable, this is important.
Even if raw is not a strenght of the 6D i can shoot up to 1344 continuous on 113. At the 116 builds the fun stops at 1280. So again the older build fit my needs better.
I know i can only speak for me but at this point the 116 is not usable. I would love to see stuff like the follow focus (arrows) be fixed but in the 116 there are more problems than solutions at this point.
Hi all, recently went from my 5d mk2 to a 6d, I was wonder where the audio menu is for ML on 6d.
Back on my 5d mk2 I had heaps more options in my audio tab, like audio gain. But all the 6d 1.1.6 has is just MLV on and off.
Cool if it's not available on 6d just wanted to know if I did something wrong.
Top of page -> Downloads -> Download Nightly Builds -> Features -> Audio
Ah I see thanks, but it seems like the 6d doesn't have audio gain yet.
Quote from: ultimatemarker on December 21, 2015, 12:30:38 PM
Ah I see thanks, but it seems like the 6d doesn't have audio gain yet.
U can find that I think in the main Canon menu if I remember well
Quote from: keepersdungeon on December 21, 2015, 12:32:41 PM
U can find that I think in the main Canon menu if I remember well
Thank you, I just realized there is an option in the menu when I turned it to video mode.
Hmm I think I prefer the ML audio menu :(
Anyone gotten the focus check box to work? Loved this feature on my t3i, can't get it to work here.
I noticed that audio recording sporadically becomes disabled when trying to record a regular h.264 video with RAW video (MLV) turned OFF while mlv_rec & mlv_snd are OK / loaded. Has been happening with the latest 3 builds, including "2015-12-20" one. Restarting a camera doesn't always help leaving only one option for recording H.264 with sound by bypassing ML loading upon camera start up.
Quote from: Pronin on December 26, 2015, 07:35:37 PM
I noticed that audio recording sporadically becomes disabled when trying to record a regular h.264 video with RAW video (MLV) turned OFF while mlv_rec & mlv_snd are OK / loaded. Has been happening with the latest 3 builds, including "2015-12-20" one. Restarting a camera doesn't always help leaving only one option for recording H.264 with sound by bypassing ML loading upon camera start up.
This issue presents in older builds as well (113). Sound records with MLRAW, but not with H.264 when ML_SND module is loaded.
Canon 6D in a magic lantern turns off after 5 sec recording ??? :-[
Yes. Can happen. If you are able to tell some details you may get some helpful answers.
In the meantime some default answers:
- Card interface bandwidth is limited to about 41 MByte/s and it doesn't help inserting a faster card.
- Use ExFAT filesystem.
http://www.fotosik.pl/zdjecie/pelne/cbe752d8b7e048f4
http://www.fotosik.pl/zdjecie/pelne/39a95898f993658b
http://www.fotosik.pl/zdjecie/pelne/9b591bf6dd1c666c
http://www.fotosik.pl/zdjecie/pelne/37651c2020b2a68a
http://www.fotosik.pl/zdjecie/pelne/98285031de1dcfc1
http://www.fotosik.pl/zdjecie/pelne/605dfb87177c2c98
http://www.fotosik.pl/zdjecie/pelne/c07a0c0d6056df0a
http://www.fotosik.pl/zdjecie/pelne/dc29a5ceb3864f4b
http://www.fotosik.pl/zdjecie/pelne/7aac7408a77cd0d2
http://www.fotosik.pl/zdjecie/pelne/f78eeb4029b0bda3
Thank you for the quick reply. I card SanDisk 64GB 80MB / sec. How to set the exFAT file system? I set the record in RAW and Dual ISO 100/1600, frame 25, White Balance Auto, Manual Mode. It would be easier if at the forum was given a link to the video how to optimally set the parameters of the ML menu for recording in Canon 6D- so as to obtain the best possible picture and be able to record videos with a length of 30 minutes Tests for two days ML 6D of 1.1.6 and the impression that ML is a test version in which no action themselves short, the menu switches off automatically after a few seconds and the camera turns heat up to 56 C is excluded recording after 5 seconds. The display image interferes with horizontal stripes and so I enclose pictures of my setup ...
41 MByte/s will get you 720p25 continuously recording. The resolution you selected is good for a few seconds only. 75 MByte/s ...
Check filesystem on card first.
If it is not exFAT (FAT64):
You have to format it with exFAT filesystem, then use EOScard/MacBoot to make card bootable. Delete ML directory, Autoexec.bin and *.FIR from card. Copy extracted nightly build contents to card and startup cam.
Thank you for your answer - so I formatted in exFAT. I do not understand, however, until the end of the final command:
"You have to format it with exFAT filesystem, then use EOScard/MacBoot to make card bootable. Delete ML directory, Autoexec.bin and *.FIR from card. Copy extracted nightly build contents to card and startup cam."
Whether it is for an additional program in which I make changes? How to do it - you can explain it step by step?
OS X or Windows?
Windows 7 64 bit
Try this:
Just copy extracted nightly builds to card and run firmware upgrade once again. Reboot.
Conclusion after 4 whole days of fighting with ML Canon 6d is that ML is a development version, which is unfinished and unstable. At least for Canon 6d. I ScanDisk memory of 80 Mb / s, so in theory very fast and quietly should cope with the task. If you just had bad luck and bought a memory of hidden undervalued record that would be the only explanation interrupting the recording after 5-7 seconds, Ful HD resolution. When you reduce the resolution to 800x 600 is a recording is continuous. But excuse me, not after it installs ML to lower quality video at its original recording in Full HD. It should be added that the same file is saved in RAW creates additional problems such as Media Composer, Adobe Premiere or need ofcourse additional Ethernet cards in the form of a plug-in, which of course is paid. At the moment ML the same problems and not worth this software installed on canon 6d. :-[
How often do I have to repeat it? Card interface in 6D is limited to about 41 MByte/s. You should get 720p25 continuous. My 650D does ...
Do the math, take your time ...
RAW/MLV workflow is not that simple, that's right.
And how to work on RAW since the introduction of Media Composer and Adobe Premiere require an additional plugin for minimum $ 150? On the limitation of bandwidth card in 6D to 41 Mb / s I did not know.
Quote from: beduinnn on December 30, 2015, 02:16:32 PM
And how to work on RAW since the introduction of Media Composer and Adobe Premiere require an additional plugin for minimum $ 150? On the limitation of bandwidth card in 6D to 41 Mb / s I did not know.
http://www.magiclantern.fm/forum/index.php?topic=5520.0
Check this.
There are many workflows to work with raw videos. I convert to dng using mlrawviewer then important them to what ever soft I need.
@Bedduinnn
You have to learn to work with the limitations : ;D
For serious production work or longtime filming in HD resolution, you need a DSLR with compact flash interface (5dIII, 5dII, 7d)
All the DSLR's with SD interface have their limitations.
But if you know them and you know your way around in post processing DNG files, you can get badass picture quality 8)
First, better forget 16:9 aspect ratio, 1:2,40 is very nice too :D (and needs less bandwidth)
With a 6d you can record about 16 seconds in 1728 x 724 resolution, which scales up to 1920 x 800 without problem and in superior quality.
And 16 seconds is a very long clip time, watch a movie or TV show and count the seconds you are seeing the same shot without switching to another shot... I bet there aren't much shots longer then 16 seconds :P
I might be crazy but i can't find any mention of this online?
When in live view mode shooting photos using any overlay, the picture seems to have a slight lag which i don't mind, but its also tearing horizontally a lot. as if i was playing a game and Vsync was turned off.
If this is a simple fix please help me this is driving me nuts! I shoot with mostly manual lenses and was looking forward to giving ML a shot.
Ok, I read a lot about ML and the Canon 6D with V1.1.6 . Now I really want to test it ...BUT... one thing remains: Until now I couldn't find a final answer to the following two questions:
1) Is it possible to disable the bootflag of the Canon 6D once it has been enabled - and if yes, how?
2) Is it possible for Canon or anyone else to detect if ML was installed in the past after disablind the bootflag again? So, is every single bit of the cam firmware set to the original value once the bootflag is disabled again - or are there also other changes to the original firmware/memory of the cam?
Many thanks in advance,
Chris
In the first post it says how to install and uninstall.
Never tried to uninstall, but uninstalling means disabling the bootflag I guess, in other words, returning the camera to it's original state.
So (unless Canon has some secret/unknown logfile within the camera that holds track of enabling and disabling the bootflag) nobody can see ML run on it in the past.
And because there is no reported issue with cams sent to Canon support (bootflag set or not) I don't even see the point in 2).
I doubt that they are looking into this that strictly as Samsung does on their mobiles.
Thank you for your help so far. Now I know that my Canon 6D has a limited capacity on the card for 40 MB / s. Currently struggling with two problems, the first is such that the video image in RAW and Dual Iso records in purple colors, just pictures taken are colored purple. What is the cause? The second problem is what is the best way to import into Adobe Premiere RAW files so that the material does not lose its money? A link to the program or a free plug-in?
Your raw files don't contain white balance settings.
So some programs are setting the white balance conpletely wrong by default.
If the images are purple you need to move the 'tint' slider from purple to green.(in the software where you edit your raw files)
I want to shoot a feature film on the ML so interested in me shots up to 2 minutes. No problem, it runs at a lower resolution, but why not record my image quality (violet) and how to convert to Adobe Premiere (trial) to check the quality of recorded material in RAW? :-[
You need to convert the raw files to be able to edit them.
Most people convert the raw files to DNG images sequence.
You can use this for example, but there are many other software options created by ML users:
http://www.magiclantern.fm/forum/index.php?topic=9560.0
The DNG files can be edited in many raw(photo)editors.
And there are video editors where you can import the DNG sequence directly.
Blackmagicdesign offers a proffesional video/color editor for free, called Davinci Resolve (not Studio, that's the payed version)
https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion
for many more options, search for:
magic lantern raw workflow
on youtube or google
Has anyone used the focus ramping in the intervalometer? I've been testing it out a bit and it seems to stop after 3-4 images after that the LV of the cam just goes black and no shutter release. Is it a bug? Or am I doing something wrong
Howdy,
New user--just installed on my 6D with 1.1.6 firmware. Under the Expo menu there's no Auto ETTR menu item. Any suggestions?
Yeah: Modules tab.
thanks, that worked!
I have used 1.1.3 with ML and it were rock solid for me, though 1.1.6 seams to be not quite that smooth yet. But some of that might be that I have recently tried more advanced features. ML is really great and makes the 6D into a vastly better camera than it would be without ML.
After I reapplied the 1.1.6 firmware update and installed the dec.20 ML, things seam to have improved.
I notice some oddities.
When I set the FPS to 2.5 (in the movie tab) with live view active it jump from just below 30 to 2.5 (as it should),
the exposure jumps from f/2 1/80 ISO1000 to f/2.8 1/100 ISO200 for stills (as it probably shouldn't)
and test exposures is massively underexposed. Half of the times I try a test exposure the screen show the overexposure
pattern over the entire screen after it is finished showing the photo, and the true image might move downwards from the
top within a few seconds (or not), but I'm wary of letting it stay on in a crashed state so I turn the camera off and take the
battery out for a few seconds.
Modules that I have loaded but not activated is: silent, file_man, pic_view.
Edit:
Silent pic with FPS override also produced artifacts, flickering with parts of image and "modern art" after I tried to take a picture.
Movie with FPS override worked as should. It were slow to adjust the exposure correctly but that is OK and probably just a
result of the slow frame rate :-).
All the testing so far were done in Program mode.
Hello,
Latest nightly builds (2016.01.25) has some problems with loading modules.
I get undefined symbols error when ML try to load modules.
You get undefined symbols messages when you try to load MLV_SND.mo without MLV_REC.mo ...
Hi
I'm new to this forum, and posting! and can't seem to find how to post a new thread.
So...
I have a canon 6D, and due to lack of ML full HD capability (?) have been shooting on native h.264 modes. However I need to be able to shoot for longer times that the 29 min 59v sec options it offers, up to an hour and over some times as much of my work is in videography. Does ML allow for this on the newer version? And is it anywhere nearer full 1080 capacity? Some posts on here speak of the full 1080 but only on RAW mode and it seems for short bursts?
Does the raw at the lower than 1080 res 'down' convert well to full HD? Comparisons on youtube suggest the native thing is better.
Any ideas or suggestions for solutions to these problems much appreciated.
Many thanks
Hi all,
I'm trying to figure out how this works with my 6D.
I've started mlv_play, mlv_rec, raw_rec in modules and i can take RAW videos for 6-8 sec before it says "Frame skipped stopped". As i read above i should lower my resolution to take longer clips but how can i do that? When i'm trying to do this in video settings i can only switch between on/off and when it's on, it seems to highest resolution?
Best regards
While using the 'set' button to toggle raw video on and off just try pushing the 'Q' button once ;D
RAW_REC.mo -> First RAW recording implementation by ML. Fast. Sound recording: Nope. Metadata: Not that much. Support status: It's there, it works but take it as it is.
MLV_REC.mo -> "ML video" format. Slower. Sound recording supported (requires MLV_SND.mo). Metadata: Yes! Support status: At your service.
Don't use both together. Both will try to write vast amounts of data to the card and will have to share 6D's rather limited SD-card interface limit (about 41 MByte/s writing) if used simultaneously.
You can expect about 720p24 recording (continuous) or shorter clips for higher data rates.
Use ExFAT file system.
Levas & Walter Schulz
Thank you for your help! Now it works like a charm.
Hi Guys
I recently just got my 6D and have loaded up ML 1.1.6.
I want to just use ML for personal "creative" videos. I have the Lexar 150mb 1000x 32GB SD cards - I only upload to vimeo so can I get 14bit raw while recording 720p 25fps? I see it says 720p 16:9 1.42x (what does that mean the 1.42x?)
Or can someone give me some info on the best settings for 720 HD for vimeo?
Thanks
Wade
Did a little testing. Times are accurate to a second or two.
http://i.imgur.com/gBp9gfy.png
To record 720p you don't need to switch your camera in the canon menu to 720p 50fps.
That setting is for high fps video, 50fps. The sensor is readout with a trick, if you record that in raw with ML then it needs unstretching vertically, because the sensor readout skipped some extra lines.
Just keep it in 1080-25fps mode in Canon menu.
You can set resolution and aspect ratio in ML raw video menu.
There you can set it to 1280 wide resolution, which gives 720p resolution in 16:9 aspect ratio.
This gives you 14bit raw 720p recording
Quote from: Levas on January 31, 2016, 12:08:59 PM
To record 720p you don't need to switch your camera in the canon menu to 720p 50fps.
That setting is for high fps video, 50fps. The sensor is readout with a trick, if you record that in raw with ML then it needs unstretching vertically, because the sensor readout skipped some extra lines.
Just keep it in 1080-25fps mode in Canon menu.
You can set resolution and aspect ratio in ML raw video menu.
There you can set it to 1280 wide resolution, which gives 720p resolution in 16:9 aspect ratio.
This gives you 14bit raw 720p recording
Thanks Levas! Yeah my canon setting is 1080 25fps ALL - i , then 720 in ML 16:9 - Shot a few clips this morning will see how they look :)
Hi, i have a problem with my 6D using Magic lantern.
After I installed ML on it sometimes the battery is drained completely whitin a couple of dayя whitout using the campera.
I used ML on my 550D without any problem like this.
Does
Until now we had several issues with battery draining but none of them was reproduceable.
Do you have this problem after removing the card? You have to shutdown your cam first and wait some time *after* opening card compartment door before removing card.
The GPS in the 6d is known for battery drain.
Look in the canon menu if you have GPS on, if so turn it off and see if the battery is not drained.
I doubt it has something to do with ML.
The GPS is known for battery usage, even if the camera is turned off
Need assistance to hunt down a - possible - bug. Please see
http://magiclantern.fm/forum/index.php?topic=16572.0
and try Motion dectect option "Frame diff.". And report back, please.
Good evening,
is it possible with ML to setup the 6D, so that only ISO 160/320/640/1250/... can be activated by the ISO button? Like the 1-stop feature in the original firmware but instead of switching from 100 -> 200 -> 400 -> 800 -> ... the Canon 6D would switch in the order 160 -> 320 -> 640 - ... ??
Best regards,
Chris
I had ML on my T3i a while back, and when I upgraded to the 6D ML was still in development. Forgot about it for a while and just discovered there are builds of the 6D available.
Question:
Is the only way to get ML now through nightly builds? I remember on my T3i there was the option for 'stable' builds and nightly builds with new features. Is that not an option for the 6D? Couldn't find this on the site anywhere.
How stable is the most recent nightly build? released on 1/14/16
There is no more "stable" release.
But you can use the latest nightly without problems, it's quite stable.
Walter Schulz and Levas, Thank you for your reply.
The GPS was Off. I don't use it.
Since then I didn't experienced the same problem with battery drain.
Thank you again.
QuoteNeed assistance to hunt down a - possible - bug. Please see
http://magiclantern.fm/forum/index.php?topic=16572.0 (http://magiclantern.fm/forum/index.php?topic=16572.0)
and try Motion dectect option "Frame diff.". And report back, please.
Just posted here.
Hello,
I have a quick question about expo Override and exposure sim. If I remember well when I used them before and blow up my parameters the live view mode gets really overexposed. But recently I found that the module works at a certain normal value and when it starts to get over exposed it kinda gets clamped to the latest value.
For example if I put 30' iso 6400 in a good light condition room is the same at I put 2' and 800 iso.
Did I mess up something? Or it has always been like that and I'm just hallucinating? Or it's a bug?
Thanks in advanced for ur reply
I have installed ML 116 Yesterday and the battery is ok.
About headphone monitoring by usb on ML 1.1.6 - is it possible or not? Maybe some beta versions?
I remeber this feature just on Tragic Lantern 1.1.3 - no another way?
Anyone out there know this answer. Canon 6D magic lantern is not showing any audio controls in the upper main menu. The microphone that shows all audio controls doesn't existopn both of my formatted cards. Everything else works. latest build with the correct firmware. SHOOT Tomorrow HELP!
Firmware 1.1.6 nightly build jan 14.6d116
same problem.
i cant control the microphone level.
https://builds.magiclantern.fm/#/features
No audio-features on 6D (yet), use the Canon menu instead.
Quote from: RIDE WITH CORE on March 02, 2016, 03:16:31 AM
Anyone out there know this answer. Canon 6D magic lantern is not showing any audio controls in the upper main menu. The microphone that shows all audio controls doesn't existopn both of my formatted cards. Everything else works. latest build with the correct firmware. SHOOT Tomorrow HELP!
Firmware 1.1.6 nightly build jan 14.6d116
Quote from: falusi on March 02, 2016, 09:06:39 PM
same problem.
i cant control the microphone level.
Yep, no audio controls during recording is a real bummer on 6D. Unfortunately I had to downgrade my 5D3 to a 6D. And some of missing features are driving me nuts :S. Ofc not ML related. ML makes this cam half decent.
P.S.
Don't hit me too hard, is the menu exiting by itself a known reported issue for 6D?
Quoteis the menu exiting by itself a known reported issue for 6D?
Mine does it too -- I thought it was an intentional timeout.
It's my first posting here, incidentally: I've just started experimenting with ML on my own 6D. To say it transforms the camera's usefulness, especially for video, is an understatement. So much to learn, but I'll put in the effort as it's obviously worth it.
Very grateful for all the hard work that's gone into this. Reverse engineering Canon's F/W is not for the faint-hearted, and this, frankly, is quite superb.
My own interests are occasional 360 (immersive) panoramas using Hugin (Panotools) and occasional documentary making. It's going to change my workflow, undoubtedly, but the results will be worth it.
Thanks people - really appreciated here.
S.
Hello anyone know how can i modificate the audio in Magiclantern with canon 6D
Hi guys,
I must be blind, but is there a list of features on the 6D build of ML?
I'm interested in starting to do AFMA tuning for my lenses and I saw somewhere that ML can run dottune and get AFMA values automagically?
Is that really a working feature?
@grassetoni:
See top of page -> Downloads -> Download Nightly Builds -> Features. Not that much audio options in ML. Use Canon menu.
@trojannemo:
See top of page -> Downloads -> Download Nightly Builds -> Features. Some features are implemented as Modules and have to be activated in Modules tab first.
[mods - if this is in the wrong place, please move it and accept my apologies!]
This is only my second post - please be gentle, as it's not really a Magic Lantern thing, but I've Googled a lot, and accurate info is VERY hard to find. If anyone has done tests or knows the answer definitively it will likely be an ML user, so please indulge me...
Questions:
1. Does the 6D embed timecode in its HDMI output under any circumstances?
2. Does the 6D emit record start/stop pulses over HDMI?
Reasons for asking
I'm seriously considering a Tascam under-camera recorder/mixer, either the DR-70D or the DR-701D.
Speaking as an ex-broadcast professional of many years, both appear to have really poor software (stupid menu structure, etc.) and are physically fragile, but they are cheap, and seem to have reasonable audio specs (for semi-domestic kit). I want them for one-man-band interview recording mostly, where they'll do just fine, as long as I'm patient and gentle.
The important difference between the two for me seems to be in the timecode handling. The more expensive unit has HDMI pass-through and a BNC for LTC, allowing it to jam-sync (input only, sadly). Apparently it will also detect the record start from some Canon DSLRs (emitted over HDMI). Tascam support the 5DIII and 1D as emitting both jam-sync-able timecode and start/stop over HDMI, but are silent about the 6D.
I can't possibly afford to upgrade to a 5DIII, and anyway I quite like my 6D (for stills, at least!). I knew it had limitations, but it's comfy to hold and it's great to get back to full-frame DoF after years with APS.
I go back to the days when real film -- the funny stuff you could look through, with holes down the edges -- was the weapon of choice for TV news, and I used to dub films and video for TV ("rerecording" if you live West of the pond). So clapperboards (or even just hand claps in vision) don't frighten me, but they are a nuisance when working single-handed (and in post, later on). Both Tascam mixer/recorders will fire an audio slate tone towards the recording and the camera's audio tracks simultaneously on a button push, so sync is possible that way, but it's functionally worse than a handclap - you'd have to find the leading edge of the tone on both recordings, and retain the camera's audio track in post, just in case.
So, if anyone knows the answers on the 6Ds behaviour, please say.
Many thanks.
S.
PS: last time I asked Canon UK a simple technical question they were basically rude and unhelpful, so I haven't emailed them this time. It's not laziness - I'm happy to do so, but on past experience I don't think it's worth the effort. I like the kit, but find the company rather frustrating.
I've been playing with h264.ini and basically I have no idea what I'm doing, even after reading this (http://"http://magiclantern.fm/forum/index.php?topic=8949.0") thread. lol so, I was wondering, what do y'all people use for your h264.ini?
Thanks
Thank you for the 1st april joke (in the source code).
Impossible to work with our 6D...
https://bitbucket.org/hudson/magic-lantern/issues/2490/stop-error-screen
If you can read source code you know what to do to avoid this one ...
Download the nightly from march 31 ! ;-)
Quote from: vertigopix on April 01, 2016, 01:39:30 PM
Download the nightly from march 31 ! ;-)
March 31, 2015
Nope. You have to use build March, 19th, 2015 (or older).
I can't read source code.
My girlfriend can't change firmware where she is.
No rebuild necessary.
I will tell how to solve the riddle: Tomorrow.
If i'm clicking at magnifying glass while i'm recording, it hangs up.
Build used? MLV/RAW or H.264 recording? Does error happen after single press (5x) or double (10x)?
was the 3x magnified recording facebook post also a 1st april joke? I was also very happy seeing the BSOD 1st april "joke" :)
QuoteBuild used? MLV/RAW or H.264 recording? Does error happen after single press (5x) or double (10x)?
Latest build I think, will check when i'm at home.
RAW_REC mode.
What I can remember, it appear in both view (5x & 10x) Liveview is freezing
First time nothing happened, when I was shutting down camera, the liveview is still there (freezed pic) and when I started it, it says "Busy" but nothing happens. After 10 minutes or something like that ML Video Mode wasn't active, so I had to start it again (RAW_REC) Was curious if it was one time thing, so i tested it again.
Second time, it also died with same symptoms, i couldn't do anything and the video was freezing in liveview, so i took out the battery and restarted the camera. Had to reactivate RAW_REC.
Note:
Magnifying glass is working when i'm not recording but when i'm trying to use it while i'm recording it freezes/hangs up.
I'm currently struggling getting the RAW Histogram to work.
Cam Settings:
- Image Quality: RAW only
- Image review: Hold
- ML Histogram Settings: RAW-based (RGB), ETTR hint, Log scaling, Clip warning
Now there are three scenarios:
1) Live View
Here the RAW Histogram works
2) View recorded images (Play Button)
Here the histogram is not a RAW histogram. It is based on the JPG preview and the Picture Style settings
3) Quick Image Review after taking a picture
Here I would expect that the same result as in LiveView is displayed. But this is not the case. This also seems not to be a RAW histogram. It is even worse. It seems like I'm getting a clipping warning way earlier, even before the JPG image goes into clipping. So e.g. I get a clipping warning in the QuickReview after taking the picture, and when I then hit the play button to view the picture the histogram has plenty of room to the right?!
I would have expected that at leat scenario 1 and 3 would show the exact same result, so that it would be possible to judge the RAW histogram without going into live view every time. If scenario 2 is also capable of displaying RAW data, I don't know. But as I have said, at least in the QuickReview I would like to see the real RAW histogram.
Any suggestions?
Best regards,
Chris
Screenshots?
Posting the raw images may also help (for example, a CR2 and a DNG silent picture from LiveView).
Does the quick review histogram show the ETTR hint?
Everything works fine here.
Hello,
I have quasten, is possible to have autofocus via Magiclantern on my Canon 6d ?
Thanks for your answer
Is anyone able to find/use the Dual ISO in Photo mode of canon 6D? Thank you very much
Quote from: vohkiem on April 15, 2016, 09:35:26 AM
Is anyone able to find/use the Dual ISO in Photo mode of canon 6D? Thank you very much
Install nightly build, go to module and activate it from there, restart the cam should be good
http://www.magiclantern.fm/forum/index.php?topic=12713.0
Quote from: Audionut on April 15, 2016, 11:07:03 AM
http://www.magiclantern.fm/forum/index.php?topic=12713.0
Thank you keepersdungeon and Audionut so much for pointing out the modules. I will try it to night.
i understand that the option to enable cbr was removed, what i can't figure out is why in 1080p all i my videos looks so bad, i tested a sandisk ultra and a sandisk pro ultra (one is 45MB/s and the last 85MB/s tested by me) more than enough to manage the 91 mbps claimed by Canon, but if i check on ML the instant bitrate on the display it's very difficult to see it going above 50mbps, sometimes go to zero. I can see in different scenarios, with some imagines more busy than others, an average of 35/37 mbps. Is there someone finding the same behavior?
Recording in ALL-I?
Bug or feature?
I can not change the color of the focus peaking. No matter what color I select, the focus peaking color remains always "red". Tested on my Canon 6D with Firmware 1.1.6 and the newest nightly of ML.
60D: seems to work fine (tried yellow and green).
Can you find out which was the last good nightly build, regarding this feature?
Just found out:
Display type: Blinking Dots works fine with the different colors. But when setting "Fine dots" or "Alpha blend" only the red color works.
Hi ML 6D Users!
I updated ML on my 6D to the latest build (May 7th) yesterday, and I encountered a problem where I was
unable to change iso/kelvin using the d-pad, and also unable to hide the iso/kelvin overlay using the toggle button.
I was on a shoot, so I quickly reverted to an older build that worked fine.
Has anybody else encountered this issue? I haven't had time to go back and do a more thorough test, but I wanted to see if there
are any other reports?
Thanks!
-Daniel
Backup ML/Settings
Delete ML directory and autoexec.bin
Copy extracted nightly build to card
Retry and report back
Hi,
after some trouble I would
really recommend to add this text:
QuoteVery important
Never delete the Magic Lantern files from the card! Format the card instead.
After opening the card door, always wait for LED confirmation (or for 5 seconds) before removing the card, even if your camera is turned off!!!
Right after opening the card door, Canon firmware accesses the card without turning on the LED (yes, with the main switch turned off). If you remove the card too early, the camera will freeze and will drain the battery, or even cause permanent damage! You will be running random code (remember you are loading executable code from the card), and we can't do anything about it without reflashing Canon firmware with our own code
to the download page as well, or the LINK below with message IMPORTANT BEFORE INSTALLING. If I had know before, this software can ruin the camera, and that one should not remove SD card the first 5 seconds, I wouldn't have had the big problems I had last 30 minutes (6D did not start up, had to remove battery, wait for 15min, getting worried and so on)...
I really don't understand why there is no link for newbies coming directly from the main webpage to the download section:
http://wiki.magiclantern.fm/install
Or have I missed it? I do not see any link, just information you are not responsible... :P :)
Regards Chris
@Sierra: does the 6D access the SD card without turning on the LED? I doubt it; to my knowledge, only 5D2, 50D and 500D do that.
Detailed info about how to test for this: http://www.magiclantern.fm/forum/index.php?topic=1455.0
About removing the SD card while the activity LED is on... I think it's obvious it shouldn't be done.
@RTLdan: which is the last good nightly build, regarding your issue?
@a1ex: Well, I assume it was also a problem of not using the right SD card (had one without boot partition).
My problem at the moment is to get maximum video quality. My SD controller in 6D locks me to 40MB/s (my SD card could offer more I guess), but this would mean I can only shoot 1280x720 (38MB/s is said in the ML Menu) - everything else is more than 40MB/s. How do people shoot higher resolutions with the 6D? I mean, nobody can use other SD slot, so I'm quite surprised how people do... ? I also cannot enter 1600x400, as the aspect ratio forces me to some certain ratio...
Could someone please help me how to enter maximum video quality settings with ML?
In short, you cannot use the higher resolutions with uncompressed formats (RAW or MLV). The SD card CONTROLLER in the 6D is not fast enough to do it. You can use normal H264 compression, but it is lossy, so there will be some artefacts.
A faster SD card (above 40 MB/sec) will not help - the limitation is Canon hardware.
ML will let you try: the higher the resolution, the quicker the buffer runs out and recording stops with a "skipped frame" error (when I try it). You can record a few seconds of full-res raw video, but that is not long enough for serious work.
This is all documented here on the forum: use the search function.
There is also a discussion about writing new code for recording raw in lower bit depth (12-bit or 10-bit). You cannot do this now.
IF, and only if, this can be done by controlling other parts of the camera hardware, it MIGHT reduce the data rate going into the SD controller enough to permit higher resolution raw recording, but that would take a lot of work, and I would guess a new raw storage format just for cameras like the 6D.
I understand the issues, but don't have the skills to help the project. I wish I could help, but it sounds quite hard (turning off bits for the pixel data is fairly easy, but making effective use of that to get more frames to the SD card per second is hard).
I am very grateful to the team for what we do have, and for free.
S.
- wrong place -
@Sierra, if you want perfect raw video on the 6d, you have to get used to limited recording times and an aspect ratio wider then 16:9.
I'm shooting video on the 6d a lot in 1728 x 724 at 25fps in 1:2,39 aspect ratio.
This settings will give you 16 seconds of recording time on the 6d.
Use DaVinci Resolve to scale the 1728 x 724 resolution up to 1920 x 800 and there you have the best quality HD from your canon.
Want more time, 1600 x 670 at 25fps gives you about half a minute of recording time.
16 seconds is long enough to take many short clips and edit a nice video out of it.
If it works for you, depends on what you want to record...it won't work to record interviews or presentations and stuff :P
Quote from: a1ex on May 14, 2016, 03:59:15 PM
@RTLdan: which is the last good nightly build, regarding your issue?
Hi Alex!
Thanks for your reply. I've had a chance to re-test the issue I was experiencing.
What is happening for me on the May 7th, 2016 build is that pressing the d-pad in any direction
has no effect on kelvin or iso when that menu overlay is pulled up. The d-pad does change the position of the spot meter overlay, however. In fact, if spotmeter is enabled, and also the kelvin/iso overlay is pulled up, the d-pad still moves the spotmeter.
I'm not sure what the most recent working build is, but the last working build I had on another card was Feb 13th, 2016.
Thanks for your help, and all the work you do for this project!
-Daniel
Reproduced; all cameras have this bug, but maybe arrow shortcuts are not that widely used?
Quote from: a1ex on May 15, 2016, 06:37:54 PM
Reproduced; all cameras have this bug, but maybe arrow shortcuts are not that widely used?
Can't speak for others, but personally this is the exclusive way I've been changing iso and kelvin values! :)
For now I will stick with the older build to keep this ability. Just my two cents...
Best,
-Daniel
Hi Alex,
Just want to say I tried the latest May 16th, 2016 build today, and that solved the problem I
had described above. I am once again happily updated to the most current build.
Thanks for all the time and attention you devote to ML!
Best,
-Daniel
I wonder what ML would bring to a still photographer. I know one limitation of the 6D that I'm darn eager to overcome. When using auto ISO (in aperture mode) I can't set the minimum shutter speed over 1/250. I'd like to be able to set it to 1/320 and above. Does installing ML make this possible?
Quote from: m!!! on May 17, 2016, 01:00:22 PM
I wonder what ML would bring to a still photographer. I know one limitation of the 6D that I'm darn eager to overcome. When using auto ISO (in aperture mode) I can't set the minimum shutter speed over 1/250. I'd like to be able to set it to 1/320 and above. Does installing ML make this possible?
I have never used video on my 6D, strictly photography! I bought the 6D only after confirming that ML was available for it after using it on my 70D. The camera is very seldom used in anything other than full manual. Features I use all the time: 1) exposure lock; 2) RAW histogram; 3) zebras - the ability to see when highlights are getting clipped, I use ETTR 99% of the time. 4) DualISO 5) timed exposures longer than 30secs in Bulb. The camera has many more features(which I seldom use), but I'm extremely happy with just these features.
Quote from: Chele on May 17, 2016, 01:43:46 PM
I have never used video on my 6D, strictly photography! I bought the 6D only after confirming that ML was available for it after using it on my 70D. The camera is very seldom used in anything other than full manual. Features I use all the time: 1) exposure lock; 2) RAW histogram; 3) zebras - the ability to see when highlights are getting clipped, I use ETTR 99% of the time. 4) DualISO 5) timed exposures longer than 30secs in Bulb. The camera has many more features(which I seldom use), but I'm extremely happy with just these features.
Thanks! Could you check to see if the auto ISO features I'm asking for are there? Another thing that comes to mind... Is exposure compensation in manual mode (http://www.magiclantern.fm/forum/index.php?topic=10573.0) working these days? By that I mean: if I've set a shutter speed and aperture and auto ISO in manual mode I'd like to be able to use exposure compensation. Would that be possible?
Hi, I don't know if this is a known problem but I found that Focus End Point doesn't work from the Custom menu. It works only from the Focus menu. This is not a big problem, but is there any chance to correct this? Thanks for your great work, Chemik.
Sorry, but can you explain what you mean by "Custom menu"? Screenshot might be helpful.
OK, maybe I'm not precise enough, I mean this menu with the star (just before that with delta sign), which one can customize with favourite functions. Maybe the name is "My menu" (as Canon's) or something like this :)
Okay, got it!
You're saying Focus End Point behaves different in Focus menu and MyMenu. Can you take a vid showing working/nonworking? Quality doesn't matter, smartphone lowres will do.
Sure, MyMenu - there is even the name at top of the screen :) I can make video but it looks 100% the same as in Focus menu but no action. There is "0 (here)" and after SET or Q button click left and right arrows don't work. After changing to the Focus menu everything is ok. After setting some steps at Focus menu, I can see the same value at MyMenu, SET still doesn't work but Q resets to "0 (here)". I'm using 2016Apr30 ver.
Hmm,
I'm missing the "Highlight Tone Priority" setting within the ISO submenu of the latest nightly of ML.
Bug or feature?
I noted in a February 20, 2016 posting that the 6D build (August 2015) did not interface with the Sescam DSLR-550D-HOCF A/V Out Cable. In reading entries on or about October 14, 2013, it appears a developer (1%) released or compiled a source code at https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/magiclantern-Tragic.2014Jan03.6D113.zip to allow 6D audio headphone monitoring using the Sescom A/V Out Cable.
It appears the latest 6D build (May 2016) did not incorporate the source code to fix the audio monitoring using the Sescom A/V cable. I await any suggestions to fix this issue.
Hi , just a quick question. I'm looking to upgrade my 7D to a full frame such as a 6D (was going to go for a older 5D mkii), as I tend to shoot RAW videos in low light.
I haven't been able to find many RAW videos where the 6D is in 2K? Is the 6D able to shoot well in 2K or isn't its buffer quick enough.
Matt
SD-card interface limited to about 41 MByte/s writing. 720p24 continuous.
Quote from: squidman90 on June 05, 2016, 03:00:35 AM
Hi , just a quick question. I'm looking to upgrade my 7D to a full frame such as a 6D (was going to go for a older 5D mkii), as I tend to shoot RAW videos in low light.
I haven't been able to find many RAW videos where the 6D is in 2K? Is the 6D able to shoot well in 2K or isn't its buffer quick enough.
Matt
If you want to shoot raw, dont get 6D like me. save up for 5d3.
raw @max resolution only like 8sec
and wait time inbetween shoots to clear the buffer.
I am so regret that I picked 6D for shooting wedding for raw. (it didnt works well at all)
btw shooting raw in high iso is not even a good ideal tho.
Great advice, save 2.000 more to replace camera worth 1.000 or save some extra 2.000 and buy RED maybe.
Sent from my SM-G920F using Tapatalk
I just installed ML on my 6D. The lens (16-35mm f/4) makes a funny noise when the IS is turned on on the lens.
When I press the shutter halfway, there is a weird whir/vibration, which is then repeated after about 2 or 3 seconds. It only happens when I press the shutter halfway down and only when the IS is turned on. I don't remember this when Magic Lantern wasn't installed.
Anyone know what this could be?
Thanks
That'll be the IS working normally then, won't it?
I doubt Magic Lantern is affecting it at all.
I have a 300mm f/4, and on that the IS sounds like a Vespa with worn piston rings. I used it for some video experiments a few weeks ago, and it was obvious the built in mic would be quite unusable if the IS was turned on (but it recorded the sound of the IS really well!).
On a 16-35mm lens, do you really need IS anyway? You hardly need focus most of the time!
On the 2-sec thing, it's probably the IS dropping out again after a timeout. It will come back on when you half-press the shutter.
squidman90, there are only like 3 maybe 4 canon DSLR cameras that are worth installing and using ML where you can record continuously ML RAW or MLV (RAW 2.0) because of the memory buffer limits. Check out this comparison chart of Canon models with ML:
https://docs.google.com/spreadsheets/d/16cgnRivbUv7nA9PUlCLmLdir3gXdIN3pqzCNAAybepc/edit#gid=5
The 6D even though it has a full frame sensor also has a 40mb memory buffer limit so it can only record for about maximum resolution of 1792x1008 for like 5 seconds with RAW or MLV video. This is such a heartbreak because of the Canon 6D's full frame sensor ... can you imagine being able to record (hell even 30 seconds continuously would've been doable) continuously RAW video?! So for full frame RAW recording the only one that can is the 5dIII, even the 5dii records at a slightly lower resolution than 1920p. The third option that can record continuously RAW/MLV video is the 7D but it has a smaller APS-C sensor and it records at a maximum resolution of 1728p which about 9% smaller than 1920p but scaling up in post fixes it and because of the extra sharpness with RAW video you really do not notice and still looks great.
Hi all,
Im running magiclantern-Nightly.2016Jun13.6D116 and Im not getting global draw when in live view, I noticed when I turned on crop marks, I dont get any crop marks or zebras at all, from what I can tell it should be turned on, is there some other setting i may have turned on that conflicts ?
or is it not working in this build?
I checked the bug tracker and couldnt see anything..
Quote from: CountParadox on June 26, 2016, 12:35:20 AM
Hi all,
Im running magiclantern-Nightly.2016Jun13.6D116 and Im not getting global draw when in live view, I noticed when I turned on crop marks, I dont get any crop marks or zebras at all, from what I can tell it should be turned on, is there some other setting i may have turned on that conflicts ?
or is it not working in this build?
I checked the bug tracker and couldnt see anything..
It's working fine in this build, have u checked if it's turned on in the settings? Do u have magic zoom on?
Press INFO button to toggle screens until ML screen pops up.
Quote from: CountParadox on June 26, 2016, 12:35:20 AM
Hi all,
Im running magiclantern-Nightly.2016Jun13.6D116 and Im not getting global draw when in live view, I noticed when I turned on crop marks, I dont get any crop marks or zebras at all, from what I can tell it should be turned on, is there some other setting i may have turned on that conflicts ?
or is it not working in this build?
I checked the bug tracker and couldnt see anything..
There are two Global Draw settings: one Global Draw setting in the easier-to-find "Overlay" menu, and another Global Draw setting in the actual "RAW Video" menu. Ensure that at least the Global Draw in the "RAW Video" menu is on?
Hey all,
I just installed ML the first time on my 6D. I tried to use Focus peaking but it isn't working at all. After I took a photo I can see a pattern of the focus peaking for a few seconds, but while looking at the Live View I can't see anything from the focus peaking. Even when I activate the grayscale the live view stays in colour.
Am I doing something wrong?
Kind regards,
Daniel
I wouldn't recommend using focus peaking at all. I use the Digic peaking "slightly sharper" setting, it's enought to see where the focus is - just give it a try, it has little to no impact on the performance. Other setting that you might find useful, in case you are shooting a flat profile is to boost the Live view contrast/saturation while maintaining a flat recording picture.
I had the June NB loaded on a SanDisk 32gb 60MB/s? card and it was working fine. So I loaded it on to 5 NEW Lexar Platinum II 32GB SDHC cards I got from Costco.
Focus peaking was hit and miss. Had some time to troubleshoot. The SanDisk 32gb 60MB/s cards ALWAYS worked. Only ONE of the Lexars worked. So I downloaded the July NB on to the Lexar cards. Still can't get them to work.
I do a low level format whenever I install ML. I'll try the digi peaking thing. But I'm taking the Lexar's back to Costco.
Update: I just looked at Digi Peaking effect, and that's what I've been getting anyway, INSTEAD of Focus Peaking. At one time, quite a while ago it was working, then stopped. Removing the battery would get it to work again. Now nothing will get REAL focus peaking to work.
Digi peaking will work on the Lexar disk though.
Essential information about the Lexars missing.
Manufacturer's speed rating? 200x or else?
Numbers verified by benchmark in cam and USB 3.0 cardreader?
"Not working" = ML won't run at all?
That did it for me. I'll checkout that link.
Guys?
Does this build support audio from USB port? I have the converter cable.
*EDIT* - I forgot the registers I had to port over from Tragic Lantern in audio.h. All better now.
I got tired of not having headphone monitoring on my 6D, so I hacked it in over the course a few evenings. Turns out people have already done some work in this space, so once I figured out how the code works I was able to complete the exercise. It works on my 6D, but try at your own risk. Any comments or feedback is welcome - I haven't coded in C in a long time, so I probably did something dumb in the process. There is still some sketchiness in its operation - don't take a picture while you're in video mode, for instance - but it does work. You may need to cycle the headphone monitoring configuration option once before you plug in the cable.
For those that are interested in doing this yourself on your version of the source code, the following changes had to be made:
* /platform/6D.116
** features.h
*** Enable headphone monitoring by adding
#define FEATURE_HEADPHONE_MONITORING
#define FEATURE_HEADPHONE_OUTPUT_VOLUME
*** I only enabled headphone monitoring because other parts of code are broken on the 6D, or in the case of analog gain, the registers or values to put in them are incorrect and would cause the input gain to be basically zero.
** internals.h
*** Uncomment #define CONFIG_AUDIO_CONTROLS
*** This is necessary because there are various checks in the code to ensure that the *entire* audio subsystem is enabled, like in audio_configure(), not just one part of audio subsystem.
* src
** all_features.h
*** Comment out the following lines, as they are not working yet, but the #define for the *entire audio subsystem mentioned above is required for the audio subsystem to function at all
//#define FEATURE_ANALOG_GAIN
//#define FEATURE_DIGITAL_GAIN
//#define FEATURE_AGC_TOGGLE
//#define FEATURE_WIND_FILTER
//#define FEATURE_INPUT_SOURCE
//#define FEATURE_MIC_POWER
** audio.h
*** Added the following method to be able to write to the audio-ic - turns out somebody already figured out the how to write to this interface.
inline void _audio_ic_write(unsigned cmd)
{
extern void _audio_ic_write_bulk(uint32_t spell[]);
uint32_t spell[] = { cmd << 16, 0xFFFFFFFF };
_audio_ic_write_bulk(spell);
}
Add the following #elif block to the register definitions - ported from Tragic Lantern
#elif defined(CONFIG_6D)
#define AUDIO_IC_PM1 0x8000
#define AUDIO_IC_PM2 0x8100
#define AUDIO_IC_SIG1 0x8200
#define AUDIO_IC_SIG2 0x8300
#define AUDIO_IC_MODE3 0x8E00
#define AUDIO_IC_PM3 0x9000
#define AUDIO_IC_ALCVOL 0x8D00
#define AUDIO_IC_ALC1 0x8700
#define AUDIO_IC_IVL 0x8900
#define AUDIO_IC_IVR 0x8C00
#define AUDIO_IC_MODE4 0x8F00
#define AUDIO_IC_FIL1 0x9100
I'm on the latest ML build for 6D. Was shooting a project as a B-cam, and the camera kept stopping recording. I was using a Lexar SDXC 128Gb 633x, which covers the max transfer rate of the 6D's SD interface (also tested on PC - has 90MB/s transfer rate bot reading and writing), I've formated the card natively in camera - same results, also noticed the problem occurs when there is more motion in frame, like small details - foliage or high ISO shooting, in other words when the codec is stressed.
Has anyone experienced such issues? Forgot to mention, I was shooting ALL-I. IPB solves the problem, but it's a good choice for me.
Thx
P.S.
Tried other card, have the same problems.
Hey. I have a Canon 6D with firmware 1.1.6 . I installed according to the instructions for ML 1.1.6 . The installation completed successfully , but the Magic Lantern does not work as it should. When shooting does not display the function ML . It shows only the menu by pressing the trash can and that's it . Any idea? :(
Delete Autoexec.bin and ML directory from card and copy extracted nightly build content to card. Retry and report.
Hello I installed on my canon 6D MAL 1.1.6 and I feel the same as Mario_DSLR
Photo mode M. Startup cam. Use wheel (the on on top) to toggle screens. Report back, please.
Me too.
Installed Firmware 6D116, but not work.
Into my sd card not exist autoexec.bin
Simone
If there is no autoexec.bin it is not our fault ...
It's included in the zip file you downloaded ...
Hi there,
I recently bought a 6D and I just found out that there's no Tv mode while in video mode. I'd like to set the shutter speed to 1/50 and let the camera do the rest. I know that the 5d mark 3 has that ability. Apparently you can either have full control over the camera while filming or none. Nothing in between. Does anyone know if Magic Latern will change that?
I hope you understand me. English is not my first language
Hi I uninstalled and have returned has installed ML and can not see the raw histogram vivo.Por please someone can tell me I'm wrong or I have to set the camera to lograrlo.Tengo to say that several days ago I installed this version magiclantern- Nightly.2016Aug15.6D116 and seeing that he could not see the histogram I left and it then several days I downloaded the current version there magiclantern-Nightly.2016Aug24.6D116 and installed it and if I appeared as the histogram and the strange thing is that the next day no longer appeared to me and I get no longer do so after uninstalling and reinstalling several veces.Gracias and hope your ayuda.Saludos
Hi,
Still no way to capture true 1080p raw? Only 21:9 crop variant?
Unless you own an EF 70-300mm f/4-5.6 IS II USM lens, I can't see any reason whatsoever to download and install Canon firmware version 1.1.7. In fact, ML may not be compatible.
Hi,
I've been using ML on my 6D over the past year and have noticed that when I look at the DNG files or the processed MOV files, they are significantly cropped.
A varying amount of the frame is lost depending on what lens being used. My Zeiss 85 ZE.2 loses a small/moderate amount of the frame. My Canon-adapted Nikkor 35mm and 50mm lose MUCH more of the frame. I wish I could give more exact numbers but I really don't know how to tell how much of the frame EXACTLY is being lost or why this is happening.
Does anyone have any info on WHY this is happening or HOW to fix it? Thanks so much.
Hey folks-
Have a 6D with firmware 1.1.3 that I need to update to 1.1.6, but for the life of me I cannot find an official Canon download link. Seems like Canon is really wanting people to adopt 1.1.7. I managed to find a zip file on another site, but I'm being very cautious about throwing that on my camera. Can anyone confirm the checksums of the real file, so I can be sure of what I have? What I have is:
File: 6D000116.FIR
20.3 MB (21,325,152 bytes)
CRC-32: 5c4c81d1
MD4: 54f6a3cc61b4d16d741d1e7cede79edb
MD5: ccce3d6b0234b06a9b1ce645ad7c8bb2
SHA-1: 38ddeecc3b4cd2aaacdeda062b00bef77ea28b55
EDIT: I was able to find the file on Canon Canada's site and can confirm that the checksums above are correct for the firmware file.
Hope this saves anyone the trouble!
http://www.canon.ca/InetDD/downloadDisclaimer.htm?contrl=disclaimer&contentid=0400177202&URL=http://pdisp01.c-wss.com/gdl/WWUFORedirectTarget.do?id=MDQwMDAwMTc3MjAx&cmp=ACY&lang=EN&LANGUAGE=ENG&Products=2200993&sessionid=null
Hi, I want to install ML on my canon 6D, but I've an old firmware 1.1.4 and now I can't download the 1.1.6.
I contact coustomer care and they told me that 1.1.6 and 1.1.7 are the same.
Can I try to install ML on 1.1.7 firmware?
Have someone try this?
When the comunity will test the new firmware?
Thank you.
Top of page -> Downloads -> Download nightly builds -> 6D.116 and follow instructions.
I found a link to 1.1.6 at Canon Canada, see below
http://www.canon.ca/inetCA/en/serviceDetail?m=load&id=45&sid=7&mid=2200993&type=D&opt=1
Cheers
Hi guys, I just purchased a used canon 6d, the guy I bought from told me he just upgraded the firmware from 1.1.3 to the latest one 1.1.7, I just realized that magic lantern only works on firmware 1.1.6, the firmware can be found on canon Canada.
My question is : has someone downgraded his camera from 1.1.7 to 1.1.6 succesfully? or should I wait until Magic lantern upgrade the tool to support 1.1.7, I have read that some guys downgraded firmware on the canon 5d mIII, but so far I haven't found someone talking about canon 6d
Al
Canon has blocked firmware downgrade in cam for 5D3 running fw1.3.3. And now guess why you haven't heard about troubles downgrading with 6D ...
Thanks for your response Walter.....damn, I have to wait for a long time before ML team upgrade the software to work with fm 1.1.7.
And exactly why do you have to wait before using ML?
Quote from: tigerbengal2009 on October 19, 2016, 05:24:56 AM
Thanks for your response Walter.....damn, I have to wait for a long time before ML team upgrade the software to work with fm 1.1.7.
I might have firmware 1.1.6 backed up on my pc. I'll let you know tonight if I still have it
You don't have to look:
All you need is covered by pelican
http://pel.hu/eoscard
Quote from: Walter Schulz on October 19, 2016, 09:27:55 AM
You don't have to look:
All you need is covered by pelican
http://pel.hu/eoscard
Or that! :) thanks Walter
Hello, am new to ML. In the case of ML corrupting the camera, is it simple enough to just reformat the card and reboot the original 1.1.6, or am I supposed to backup some files somehow?
The FAQ suggests:
As a precaution, the installer asks you to make a backup copy of your ROM files on the PC.
Thanks,
Zander
There is no guarantee ML installation will *not* brick your cam permanently and unrecoverable.
I recently upgraded my 6D from stock 1.1.3 to 1.1.6 and installed ML.
However I cannot find any setting to change the video recording bitrate which I recall existed on my T3i with ML.
I would like to lower the bitrate so my recording files don't get so large so quickly.
Does this setting no longer exist?
That feature no longer exist, since raw video is way more exciting ;D
And the 6d has the ALL-I recording option available in Canon menu, so for best H.264 video, use the ALL-I option. No need for nitrate increasement.
I've moved to the 1.1.6 today and i'm missing some resolution options in the MLV recording menu.
It goes from 1600 pixels wide to 1920 pixels wide.
I would like to get the 1728 and 1792 pixels wide options back in the 6d build, they were there before, or at least in the 1.1.3 build.
Can somebody get these options back in a new nightly build ?
Movie tab -> RAW video (MLV) -> Q
Use upper wheel to change resolution in 32 pixel increments.
Thanks Walter!
Didn't know about that option to change it with 32 pixel increments.
Works perfect :D
Hi everybody, I just wanted to share my experience, I bought a used canon 6d which was already on latest canon 1.1.7 firmware, after posting question in this forum with the great help of Chris_overseas, Walter Schulz and other members I download the firmware 1.1.6 and did the downgrade without any problem, then installed magic lantern and using it....very excited to have all these ML features in my canon camera!!!
Quote from: tigerbengal2009 on November 13, 2016, 09:47:01 PM
Hi everybody, I just wanted to share my experience, I bought a used canon 6d which was already on latest canon 1.1.7 firmware, after posting question in this forum with the great help of Chris_overseas, Walter Schulz and other members I download the firmware 1.1.6 and did the downgrade without any problem, then installed magic lantern and using it....very excited to have all these ML features in my canon camera!!!
Hey, I have the same problem and it would be great, if you can tell me what you have done to downgrade to 1.1.6. On the webpage of pelican the firmware 1.1.6 is not availible and I don't know how EOScard can help.
Quote from: n3 on November 14, 2016, 02:48:35 PM
On the webpage of pelican the firmware 1.1.6 is not availible
Sorry? http://pel.hu/eoscard/
The link for 1.1.6 gives a 404: http://pel.hu/down/eos6d-v116-win.zip
Quote from: Walter Schulz on November 14, 2016, 11:22:12 PM
Sorry? http://pel.hu/eoscard/
Thanks for pointing out. Use this one instead
http://gdlp01.c-wss.com/gds/2/0400001772/01/eos6d-v116-win.zip
Just got a message from pelican. He fixed the link. Thanks!
Thank you very much.
Now I've the 1.1.6 firmware version
you can get the 1.1.6 firmware from Canon Canada....here is the link
http://www.canon.ca/inetCA/en/inFrame?m=showInFrame&url=http://canoncanada.custhelp.com/
I'm new here and my english is not very well. So I'm sorry for that.
I wanted to test ML for my 6D.
I loaded it on my SD-card and installed it an my 6D.
The installation worked and boot-flag was set.
But after starting the cam it doesn't work.
Nothing changes. Still the original Canon-Firmware is loading.
Top of page -> User Guide -> Install Guide/FAQ
Hello,
i am new on this forum. and hoping to find some answers.
i have the following problem whit my camera. when connecting through USB it will not recognize the camera in Eos utility.
and i have a strange Firmware on the camera. 5.8.6 7D (f1). and i have the Factory menu
is there someone who have fixed this problem? if not i have to sent it back to canon.
it's bought second hand. whit 30.000 shutters Clicks and is function pretty good. the old owner never used the USB cable and dit not know that the camera was in factory mode.
hope someone can help me whit this problem.
Regards Simon
Hi, I tried installing magic lantern onto my 6D but it didn't work because my camera's firmware was 1.1.7
What can I do to make magic lantern work on my 6d?
I also downgraded from 1.1.7 to 1.1.6. If you can't find the 1.1.6 firmware, use the filename from the link on the Canon site and change the version number and paste into a search engine.
Install process is exactly the same. If running from sd card the camera will say it is upgrading from 1.1.7 to 1.1.6.
I can't claim this works in every downgrade scenario. Some firmware may potentially not be suitable to roll back.
In my case I had actually upgraded to 1.1.7 before checking the nightly build page to realise I shouldn't upgrade the Canon firmware. So I thought that it would be worth trying the roll-back.
I have magic lantern running okay.
I am watching a storm and hoping to photograph a lightning bolt.
Has someone installed ML on 6D which has firmware 1.1.7. Does it work or do you really have to downgrade to firmware 1.1.6.
You need firmware 1.1.6.
It's still available on the canon website from Canada.
You can download the firmware and run it as a firmware update in camera
Hello Everyone,
This morning I tried to use the GHOST OVERLAY feature in ML and it has seemed to have stopped working. I use it all the time to do time lapses.
I removed Magic Lantern, formated card, reset camera, updated ML to a newer nightly build (whatever I was running was a few months old), reinstalled ML and after pushing LV on an image it will show it desaturate and say "OVERLAY SAVED." But no overlay.
Any advice would be awesome, I use this feature for work.
Thanks,
Chris
PS I have 1.1.6 on camera
Overlay works in ML LV screen only. Press INFO button to switch screens.
For those of you that didn't know...
10 bit and 12 bit raw recording is now available on 6d, with working live view :D
10 or 12 bit gives lower data stream which makes it possible to have longer recording times or use higher resolutions with the same recording time as before in 14 bit.
For example:
1728 x 724 resolution (1:2.39 aspect ratio) x 25 frames per second in 10 bit should give continuous recording
1728 x 972 resolution (16:9 aspect ration) x 25 frames per second in 10 bit gives about 20 seconds recording time
See this post including the download link:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg176940#msg176940 (http://www.magiclantern.fm/forum/index.php?topic=5601.msg176940#msg176940)
Direct link to the builds:
https://bitbucket.org/daniel_fort/magic-lantern/downloads (https://bitbucket.org/daniel_fort/magic-lantern/downloads)
Happy testing ;)
Quote from: Levas on December 24, 2016, 10:47:56 AM
For those of you that didn't know...
10 bit and 12 bit raw recording is now available on 6d, with working live view :D
10 or 12 bit gives lower data stream which makes it possible to have longer recording times or use higher resolutions with the same recording time as before in 14 bit.
For example:
1728 x 724 resolution (1:2.39 aspect ratio) x 25 frames per second in 10 bit should give continuous recording
1728 x 972 resolution (16:9 aspect ration) x 25 frames per second in 10 bit gives about 20 seconds recording time
See this post including the download link:
http://www.magiclantern.fm/forum/index.php?topic=5601.msg176949#msg176949 (http://www.magiclantern.fm/forum/index.php?topic=5601.msg176949#msg176949)
Direct link to the builds:
https://bitbucket.org/daniel_fort/magic-lantern/downloads (https://bitbucket.org/daniel_fort/magic-lantern/downloads)
Happy testing ;)
Great been a while haven't checked the progress on this. Thanks for the update!
Resolution setting is a little different compared to older builds.
in the raw video settings menu you can choose resolution, as you will see there aren't many options in the resolution menu anymore.
But you can finetune resolution by using the scroll wheel on top of your 6d, the resolution is adjustable in steps of 32 pixels.
I cant find 1.1.6 on any canon sites any more, has someone got a link?
http://www.canondriver.net/tag/eos-6d-firmware-version-1-1-6-windows/
Why does Canon (and, apparently, all other manufacturers) set different grey point EV between jpgs and RAW ? It's been so frustrating, until I finally started paying attention to ML. Thank you ML !
While, the RAW histogram is available in LV mode, it's not always the perfect solution (for instance, using flash where the EV is checked after the capture). Having the RAW histogram in the image review is beautiful. I'm nailing moments that would have been more of a challenge. W/o accurate EV, I'm dependent on the jpg histogram, which is about +1.5 EV over the RAW on my 6D.
Just saying thank you.
the EOScard website (which you'll need for making your SD cards bootable) has firmware for many different Canon cameras way at the bottom of the page
http://pel.hu/eoscard/
Hi,
I cannot find ML for 6D with 10-bit RAW possibillity.
Even here https://bitbucket.org/daniel_fort/magic-lantern/downloads
Did I miss something?
@ajax.d
Experimental builds moved to here:
https://builds.magiclantern.fm/experiments.html
dfort: Thanks a lot!
@dfort This webpage is not available
It seems fine here on iOS Safari:
(https://uploads.tapatalk-cdn.com/20170112/746d54556280f55d4b6d44aab36f3eaa.jpg)
Home Page -> Downloads -> click on "Download Nightly Builds" -> click on "Experiments" on the top right
@dfort yeah, works as http
so i finally joined the modern age and update my 6D from firmware 1.1.3 to 1.1.6 8) Everything went smoothly, and I'm looking forward to using the most up to date ML!
Thanks to the devs for all you do!
Hi All,
I've been using ML in my 60D for many years, no problem what so ever, to me the Live Histogram in video shooting is a valuable tool that I used most. Just got a new 6D body and trying to set up ML with live histogram in LV, but it never show up, other functions work fine. I tried diff. nightly builds, but no help. What do I miss? Since I have the setup similar to my 60D, and it works fine in 60D body with all builds. Please can some body help?
H.264 or RAW/MLV? MLV surpresses Global Draw functions by default.
For H.264 toggle screen by pressing INFO button in Liveview until ML overlays are visible.
Aha! Thank you Walter. The 'Info' button to switch between display overlay modes did the trick. How could I missed that. Thanks again.
@schedonnardus
You don't need to make your SD card bootable via your PC. I just went through this issue for a second SD card for my camera and all you need to do is extract the nightly (or whatever build of ML you want) to the SD card and run the cameras firmware upgrade. The ML install will make the SD card bootable for you.
Quote from: spmy2792 on January 23, 2017, 06:22:24 AM
Aha! Thank you Walter. The 'Info' button to switch between display overlay modes did the trick. How could I missed that. Thanks again.
Time for blinking the warning messages in menu? The issue is very common, so maybe there's something wrong with ML UI.
Maybe only when user enables a setting which is grayed out?
Quote from: Jokemeister on January 23, 2017, 11:26:12 AM
@schedonnardus
You don't need to make your SD card bootable via your PC. I just went through this issue for a second SD card for my camera and all you need to do is extract the nightly (or whatever build of ML you want) to the SD card and run the cameras firmware upgrade. The ML install will make the SD card bootable for you.
good to know. Still the eoscard website has all the old firmware. since canon's website only has 1.1.7 on it now, ppl will need access to 1.1.6. I installed 1.1.6 from there and it worked fine.
The Canon 6D version 1.1.6 firmware is also available from my website here https://thatphotowebsite.com/wp/wp-content/uploads/files/eos6d-v116-win.zip (https://thatphotowebsite.com/wp/wp-content/uploads/files/eos6d-v116-win.zip). If I recall correctly I downloaded this from Canon Canada before they took it down. Hope this helps people.
Lookup link in download page for 6D. It is linked to firmware 1.1.6 hosted by member pelican.
been using 1.1.3 with some nightly build from may 2014 and im quite happy with it except for the dissapearing ML when idle more than 1-2 seconds :D
I need advice, would you upgrade to the new firmware and new ML as I'm quite satisfied with my camera? is there any list of changes that came with the new version of ML for 1.1.6 FW?
You can try it and rollback any time. Unofficial repository for outdated Canon firmware is http://pel.hu/eoscard hosted by member pelican.
Changes will be found at https://builds.magiclantern.fm/jenkins/job/6D.116/changes
FYI, the full change log is also present on the nightly page when you click on Older builds.
For 6D: http://builds.magiclantern.fm/6D-116-all-builds-changes.html
sorry my english-/ ...I could pass its parameters, I downloaded it, but using a version with a module to 10bits, you as it does to activate the audio, I have been able to shoot continuously 10m without problems (without audio)
my settings
REC Key ( halfShutter), RAW video ON 1600x680 / 2.35:1 10bpp**, Movie Tweaks ?
Focus settings
Config Files, Focus box settings, Arrow/Set shortcuts
mlv_play, pic_view, raw_rec
** link ML 10bpp https://builds.magiclantern.fm/experiments.html
SDXC SanDisk Extreme Pro 64 Go Classe 10 U3
Hey,
I have successfully installed and using ML on my 6D, however there is a glitch every few seconds whilst in the ML menu, it glitches between the ML menu and live view and a couple of Canon menus, without me doing anything.
Anyone know what is causing this and how to fix it?
Thank you
Quote from: zz77yy on February 25, 2017, 04:10:17 AM
Hey,
I have successfully installed and using ML on my 6D, however there is a glitch every few seconds whilst in the ML menu, it glitches between the ML menu and live view and a couple of Canon menus, without me doing anything.
Anyone know what is causing this and how to fix it?
Thank you
This is normal when ur live view is on this happens. To fix it simply turn off live view before entering ML menu
Does your latest magic firmware update support an EOS Rebel T6i Camera? I am seeking a solution to monitor my audio. I am using a wireless mic and there does not seem to be a way to monitor the audio while using headphones. Any suggestions would be welcomed.
"The Canon 6D version 1.1.6 firmware is also available from my website here https://thatphotowebsite.com/wp/wp-content/uploads/files/eos6d-v116-win.zip. If I recall correctly I downloaded this from Canon Canada before they took it down. Hope this helps people."
thanks for this link.
Do you know wher i can find this firware 1.1.6 for mac? Because there is only 1.1.7 on Canon website...
Thanks
DocJustice
Unzip it and "Firmware 1.1.6 for mac" is there (there is no Firmware for macOS, cams don't run macOS or Windows). You can use file linked in Download section as well (pel.hu).
Thank you!
I try this.
a question I wanted to ask a long time ago.
this is about shooting fps override timelapse in video mode, for low light situation.
I bought a 6D last year and installed ML and it works fine... except for the one specific feature I wanted it .
let me explain: before , I had the 600D, and in video mode the 'fps override' in 'low light' selection works great, so I could shoot e.g. at ISO 1600 some timelapses at night e.g. of the northern lights . Using a fast lens it works really good. But ISO 1600 is sort of the limit... beyond that there's too much noise...
if I choose ISO 800 on the 600D the video has even less noise but the shutterspeeds must be longer.
Now, since the 6D has better low-light capability, I was hoping I could use the same feature, in video mode, fps override, 'low light' setting, e.g. at ISO 2500 or 3200 ... but no, it results in horrible noisy mesh... even at ISO 1600... the 'low-light' setting ( long exposures of each frame in fps override ) is a mess on my 6D .
any idea what I would need to change in settings ?
Never used FPS override in video mode for timelapses on the 6d, so could be that it doesn't work that well :-\
But why not using silent picture module in combination with intervalometer ?
Works perfect, you can even use full resolution silent pictures (so 20 megapixel frames :) ).
Only thing with full resolution silent pictures is, that the camera needs to write them off to the SD card so you need too have at least 3 to 5 seconds time interval between pictures.
I use it for timelapses of the night sky.
Silent picture module and intervalometer
Full resolution silent pictures
15 seconds exposure
5 seconds between pictures
Probably a lot of you already heard the news, but there are some very interesting things going on for raw video.
14 bit compressed(lossless) raw :)
And now it even works with lower bit depths :D (unfortunately that is on the 5dIII only, :'( )
http://www.magiclantern.fm/forum/index.php?topic=19300.msg183231#msg183231 (http://www.magiclantern.fm/forum/index.php?topic=19300.msg183231#msg183231)
This could help for longer raw video recording times, or continuous recording on high resolutions.
For instance, max resolution (full frame, no digital zoom) on the 6d is 1824 x 1026.
With 12 bit compressed raw that would give about continuous recording times.
Or about one minute recording time in 11 bit 2400 x 960 resolution in zoom mode.
Does anyone here has the knowledge or the knowhow how to port this to the 6d ?
The source code is in the compressed raw branch:
https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e?at=compressed_raw (https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e?at=compressed_raw)
It's in the silent picture module:
https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e/modules/silent/?at=compressed_raw (https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e/modules/silent/?at=compressed_raw)
Some info about the process TwoInTwoOutLosslessPath:
http://www.magiclantern.fm/forum/index.php?topic=18443.0
And some info about development for it on the 5dIII:
http://www.magiclantern.fm/forum/index.php?topic=19300.0
On the 5dIII there is some improved crop recording mode for achieving the higher resolutions for 4K, this newer crop recording isn't yet developed for the 6d, but for as far as I know, the compressed raw part can be used separate from the crop recording mode.
Some more guiding:
http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989 (http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989)
http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168 (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168)
https://vimeo.com/212953671 - About Clasico Argentino
Shot on the Canon 6D in RAW 1600x900 scale 1080p 16/9 - Magic Lantern raw, MLVtoMovie / Lenses : Sigma 50mm Art, CANON EF 100 mm f/2.8 Macro USM, Canon 24mm f/4L - FCPX, LUT Utility : Osiris Canon C LOG + C LOG to Rec709
Aunque ayer descubri Footage y trata directamente el MLV pudiendo retocarl la imagen convertirlo en ProRess 4444 / 422
https://rink.hockeyapp.net/apps/3ed6ecf60e684239a6aba3d407cf3935/app_versions/57
When is ML for firmware 1.1.7 available?
best regards
mcinternet
April 1st, 2018
@mcinternet
ML for the 6d is, for now, only available for firmware 1.1.6
If you have a 6d with firmware 1.1.7 and want to make use of ML, you have to downgrade the firmware to 1.1.6
If you look a few pages back in this topic, you will see some other 6d users who did the same.
The 6d 1.1.6 isn't available on the official Canon websites anymore, but a few pages back in this topic there are some people who have a download link to it.
Semi-official download site is linked in 6D nightly build download page.
Hi Guys
I hope this is the right place to post, I have a Canon 6D running 1.1.6 on the latest build of ML, however I have never seen the bit rate adjustment setting on my 6D in the video settings of ML. any ideas why not?
I say this because I have that option in my 100D.
Thanks
Kaves
100D really profits as it doesn't have ALL-I option to chose from. It's simply not available with original firmware.
For 6D I don't think it would make much of a difference due to the ALL-I option being available. You can ofc compile from source and just enable it but please also read this:
http://www.magiclantern.fm/forum/index.php?topic=15988.msg155226#msg155226
The 6d has the all-I option in canon video menu.
H.264 in all-I format is the best possible option for H.264, it doesn't get any better then all-I
The same is done with sound recording, Canon menu on the 6d offers full manual audio control.
So no extra audio options in ML menu.
Quote from: Levas on April 15, 2017, 05:31:15 PM
Probably a lot of you already heard the news, but there are some very interesting things going on for raw video.
14 bit compressed(lossless) raw :)
And now it even works with lower bit depths :D (unfortunately that is on the 5dIII only, :'( )
http://www.magiclantern.fm/forum/index.php?topic=19300.msg183231#msg183231 (http://www.magiclantern.fm/forum/index.php?topic=19300.msg183231#msg183231)
This could help for longer raw video recording times, or continuous recording on high resolutions.
For instance, max resolution (full frame, no digital zoom) on the 6d is 1824 x 1026.
With 12 bit compressed raw that would give about continuous recording times.
Or about one minute recording time in 11 bit 2400 x 960 resolution in zoom mode.
Does anyone here has the knowledge or the knowhow how to port this to the 6d ?
The source code is in the compressed raw branch:
https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e?at=compressed_raw (https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e?at=compressed_raw)
It's in the silent picture module:
https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e/modules/silent/?at=compressed_raw (https://bitbucket.org/hudson/magic-lantern/src/ad3969261ccf44db198ae01d863ec3062d9d640e/modules/silent/?at=compressed_raw)
Some info about the process TwoInTwoOutLosslessPath:
http://www.magiclantern.fm/forum/index.php?topic=18443.0
And some info about development for it on the 5dIII:
http://www.magiclantern.fm/forum/index.php?topic=19300.0
On the 5dIII there is some improved crop recording mode for achieving the higher resolutions for 4K, this newer crop recording isn't yet developed for the 6d, but for as far as I know, the compressed raw part can be used separate from the crop recording mode.
Some more guiding:
http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989 (http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989)
http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168 (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168)
No idea of how to port this, but if needed I will be glad to help with testing.
On the 6D, being able to get a RAW histogram is essential (the gap between YUV and RAW is about 1.5).
On my 550d, with ML, I can get a RAW histogram in the review mode as I cycle through images. All I do is select the Q and up pops the RAW histogram.
On my 6D, with ML, the RAW histogram only shows up in the immediate delay after capturing an image.
I've (1) skimmed through numerous forums and (2) tried lots of different ML configurations, but the 6D doesn't expose the RAW histogram after I've gone on to capture another image and then look back at older ones.
Am I missing a subtle configuration requirement ?
Thanks
So i just installed ML on my 6D, the problem is when im within the interface it keeps flickering. There seems to be another menu that keeps flickering in and out. It's a bit troubling or is it normal? please let me know.
Quote from: kumsa on April 28, 2017, 09:43:10 PM
On my 550d, with ML, I can get a RAW histogram in the review mode as I cycle through images. All I do is select the Q and up pops the RAW histogram.
I'm pretty sure you can't.
The shortcut key for overlays should be listed in the Help menu. Whether that key actually works or not, I don't know.
I ve installed the latest version of ML on my 6D DSlR , and the only reason I did is for audio monitoring it's not that I don't like the other features unfortunately the option is not available or am I missing something
Thanks
https://builds.magiclantern.fm/features.html -> Audio
- Magic Lantern raw, MLVtoMovie !!
Shot on the Canon 6D in RAW 1600x900 scale 1080p 16/9 - Lenses : Sigma 50mm Art, CANON EF 100 mm f/2.8 Macro USM, Canon 24mm f/4L - FCPX, LUT Utility : Osiris Canon C LOG + C LOG to Rec709,
https://www.youtube.com/watch?v=z0Q-QFmef88&t=5s
hi,
I'm using magic lantern for the first time , but the video I got is very small , it's like I have two times letter box how can I fix thsi issue
Thanks
If you're looking for help you have to give some information for those willing to help.
Be accurate, please.
What are your setting, what have you done? = How to reproduce?
Merci pour votre reponse :
voila ce que j'ai comme settings:
Appareil Photo Canon 6d 1.1.6 ml :Latest Build (2017-05-06 23:36)
Carte Trannscend 90ms/600x
rAW vIDEO : oN 960X324
rAW vIDEO (mlv) : oN 960X324 ( ce ne st quavec ces reglage que je peux enregistrer en continue)
(aspect Ratio) 16/9
la video au final a une bande noire tres grande en haut et en bas
merci
(http://thumb.ibb.co/czw9d5/IMG_2565.jpg) (http://ibb.co/czw9d5)
photo album upload (http://imgbb.com/)
Quote from: strongenough on May 08, 2017, 12:50:44 PM
Merci pour votre reponse :
voila ce que j'ai comme settings:
Appareil Photo Canon 6d 1.1.6 ml :Latest Build (2017-05-06 23:36)
Carte Trannscend 90ms/600x
rAW vIDEO : oN 960X324
rAW vIDEO (mlv) : oN 960X324 ( ce ne st quavec ces reglage que je peux enregistrer en continue)
(aspect Ratio) 16/9
la video au final a une bande noire tres grande en haut et en bas
merci
(http://thumb.ibb.co/czw9d5/IMG_2565.jpg) (http://ibb.co/czw9d5)
photo album upload (http://imgbb.com/)
Not sure as to the rules of the forum, but most people here probably won't be able to help you in French. As to the image you posted: I don't see any black borders, where are you seeing this? Also, as far as I know you should not use both Raw and MLV, choose only one. BTW :the resolution you posted is low and is also not 16:9.
oops sorry for posting in french ! I meant to say when I play the video on the camera but when I play it on the Computer it is stretched ,
could you please give advice for the best settings for the Transcend 90ms/600x sd card for continuous recording
Thanks
If you want higher resolution try the 10/12 bit branch. I see it is stretched in your playback, but knowing that doesn't help, what software are you playing it back in, has it been converted to mov or other format, if so, using what software?
Use MLRawViewer to play raw videos.
Also was the camera in 720p and/or 60fps? Could be mv720.
@strongenough
Looks like you have the camera in 720p50fps mode and not in 1080p25fps.
Look in canon menu.
This has nothing to do with ML.
If the camera is in 720p50fps mode, the picture has to be unsqueezed by about 1.60 vertical to get right aspect ratio, Canon is skipping some lines here to achieve the 50fps read out.
Once you've set you camera to 1080p25fps in Canon menu, you're getting normal resolutions in ML raw video mode 8)
For continuous recording you're limited to about 1280x720, that is in the normal magic lantern version for 6d.
But if you look further on the download page, you can see the link "experiments"
On the experiments page you'll find a magic lantern version for the 6d that gives you the option to record in either 10, 12 or 14 bit.
When choosing for 10 bit, you can probably get continuous recording at 1440 x 810 resolution.
But the 10/12 bit recording is rather new and not all home made post process software can handle the 10/12 bit MLV files.
Thanks a lot for your help and this really help:
I have converted the ML files and played it with VLC, so If I have understood your advices it's better to record in raw rather than ml
Thanks
No, you need to set the right settings in the canon video menu to get normal(not stretched) looking video.
Somewhere in the canon camera menu you can choose between 1080 and 720 resolution.
So this setting is not in the magic lantern menu.
Choose one of the 1080 settings. If you choose 720p setting your ML videos will look stretched.
Did anyone else experience major battery drain, even when the camera is turned off?
I noticed that problem now 2 times, each time fully charged battery, did a shoot for like 10 minutes, at the next day the battery is empty.
Happened with original Canon battery as well as a China one.
And it just started a few days ago when I updated to the latest nightly.
You removed the card, right? Make sure to wait some time *after* opening card compartment before removing card. Cam will access card after opening card slot (power off? -> Cam doesn't care) and may run random stuff after incomplete shutdown.
Test and report back.
Internal GPS in the 6d is known for battery drain, even when camera is turned off.
So check if GPS is off.
Hey, are you planing upgrade ML for 6D to 1080 50fps recording?:) As you have done for canon 5D mark iii.
hi..i just installed ML latest build on eod 6d...under modules i enabled mlv recording ver1.1 mlv lite..i think this is 14bit recording raw video, right? on my canon 6d recording stops after 5 seconds...i know limitation on 6d is raw video 1724x....for around 20 second, but i get only 5 second..what am i doing wrong..do i have wrong module enabled for video recording?
thanks for helping
Quote from: kumsa on April 28, 2017, 09:43:10 PM
On my 550d, with ML, I can get a RAW histogram in the review mode as I cycle through images. All I do is select the Q and up pops the RAW histogram.
Are you sure about this? I always wanted this on my 650D, to be able to see the RAW histogram whenever you like instead just right after taking the images.
Quote from: a1ex on April 30, 2017, 09:43:44 AM
I'm pretty sure you can't.
The shortcut key for overlays should be listed in the Help menu. Whether that key actually works or not, I don't know.
I don't have anything in the Help Menu. Can you help me where can i find and install the Help files for ML ?
Quote from: imagineD on June 22, 2017, 11:44:56 AM
Can you help me where can i find and install the Help files for ML ?
That's something we need to fix (help welcome), but the info you need should be in the main menu (don't press anything, just read it).
QuoteI don't have anything in the Help Menu.
Even though I don't know how exactly this menu looks on 6D (as the emulator is not there yet), I have a feeling it's not completely empty.
@ a1ex if i can help somehow im in :)
BTW on my 6D when I view (play) the images and when i press the LIGHT button (uppers screen light button) it really displays the histogram and zebras or focus peaking dost on the image.
But I noticed the histogram is not the RAW histogram, i think it is generated from the preview image..?
It would be nice to be able to see the RAW histo and even the ETTR hint whenever you want for all saved images
Quote
@ a1ex if i can help somehow im in :)
Just look up Audionut's signature.
Quote from: imagineD on June 23, 2017, 12:04:26 AM
BTW on my 6D when I view (play) the images and when i press the LIGHT button (uppers screen light button) it really displays the histogram and zebras or focus peaking dost on the image.
Yes, that button should be mentioned on the help tab.
Quote
But I noticed the histogram is not the RAW histogram, i think it is generated from the preview image..?
It would be nice to be able to see the RAW histo and even the ETTR hint whenever you want for all saved images
Until recently, that required running dcraw on the camera (very very slow); however, some days ago, g3gg0 found out how to use the hardware lossless decoder (which is what we need to decode the CR2). Still, some small things are left to reverse-engineer, such as the file name of the image being reviewed.
Finding these should be straighforward in QEMU. For emulating the 6D (which is something I'd like to do regardless of this particular feature), I need a copy of the the serial flash contents. One can get it with the sf_dump (https://bitbucket.org/hudson/magic-lantern/src/unified/modules/sf_dump/) module (it needs to be updated for 6D and compiled from source). Very easy coding task.
Quote from: a1ex on June 23, 2017, 09:28:24 AM
Finding these should be straighforward in QEMU. For emulating the 6D (which is something I'd like to do regardless of this particular feature), I need a copy of the the serial flash contents. One can get it with the sf_dump (https://bitbucket.org/hudson/magic-lantern/src/unified/modules/sf_dump/) module (it needs to be updated for 6D and compiled from source). Very easy coding task.
Is there anything I can do to speed up this process? :) I can try to get the serial flash content from my 6D for you is someone update/compile the sf_dump module.
Quote from: Levas on April 05, 2017, 05:34:13 PM
...
Silent picture module and intervalometer
Full resolution silent pictures
15 seconds exposure
5 seconds between pictures
How to turn off the display during the timelapse and is it possible for Canon 6D?
Button "info" I do not turn the screen, and sorts out different information.
Quote from: Oleg_K on July 11, 2017, 07:17:16 AM
How to turn off the display during the timelapse and is it possible for Canon 6D?
Button "info" I do not turn the screen, and sorts out different information.
http://wiki.magiclantern.fm/userguide#powersave_in_liveview
Powersave in LiveView...
Options for maximizing battery life when using LiveView.
Quote
Enable power saving: on Standby, during Recording, or always.
Use LCD sensor: you can use it to wake up from powersave (wave your hand near it), or to force powersave mode (cover the sensor for a few seconds).
Dim display: In LiveView, if the camera is idle, Magic Lantern will reduce the LCD backlight level to minimum in order to save power.
Turn off LCD and LV: this will turn off the display and the sensor activity in LiveView. Mirror will not be moved. If the camera is recording or motion detection is enabled, only the display will be turned off (so recording will not stop).
Turn off GlobalDraw: if the camera is idle, ML overlay graphics will be disabled to reduce CPU usage.
Quote from: leavesfromthepresentpast on July 11, 2017, 08:17:22 PM
http://wiki.magiclantern.fm/userguide#powersave_in_liveview
Powersave in LiveView...
Options for maximizing battery life when using LiveView.
This I read, the camera canon 6d does not work.
Quote from: Oleg_K on July 12, 2017, 04:17:08 AM
This I read, the camera canon 6d does not work.
unless you made a custom ML for yourself it does (yes i do have a 6D).
https://www.magiclantern.fm/forum/index.php?topic=3498.0
go to PREFS/POWERSAVE IN LIVEVIEW/ then enable the power saving on recording or whatever u want, pick a button to activate or turn off auto after certain seconds.
Shameless bump:
Quote from: a1ex on November 28, 2015, 09:47:04 AM
https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d
You want screenshots of the free memory dialog on the 6d I guess ?
Which builds should I download for the before and after screenshots ?
Hi guys, I just wonder that my 6D firmware version is 1.1.7, then can I install magic lantern??
Yes, after downgrading Canon firmware as mentioned in Download Nightly Builds page.
Hi! I've got 6D with firmware version is 1.1.6. I've installed ML and normally used it for a week. Today I've opened the SD door with SD card without ML to change cards and camera turned off. Now camera doesn't turn on with any SD card, but works without card. I've formatted another card but no success with it. Is it possible to fix it?
Hi, my 6D is updated to firmware 1.1.7. Before installing and using ML 2.3 I wanted to know if there are any issues and if someone has tried ML with this Firmware.
I would not have any problems, I'm new to this.
Quote from: SergioBellotto on August 18, 2017, 04:45:27 PM
Hi, my 6D is updated to firmware 1.1.7. Before installing and using ML 2.3 I wanted to know if there are any issues and if someone has tried ML with this Firmware.
I would not have any problems, I'm new to this.
This firmware is not supported yet u need to downgrade to 1.1.6.
If you search this thread u'll see links for the firmware coz it's not available on Canon vs site anymore.
ML 2.3 is outdated, u should install the nightly builds.
Sent from my Pixel using Tapatalk
Can someone help me with the x3 crop on the 6D? I tried what Levas did but can't manage to make it work, installed
adtg_gui.mo module but when I activate it all modules makes errors and cam is unusable.
2-One last question on x5 crop does anyone have some sort of lag in the footage? They're nit as smooth as without crop.
Any help would be appreciated. Thanks
Sent from my Pixel using Tapatalk
@ keepersdungeon, replied your message about the lagging video.
Using adtg_gui for crop mode recording is a pain in the ... you have to alter several settings/registers with adtg_gui and then it works, BUT as far as I know, you can't save these register/settings and therefore you would have to rechange them every time you turn on your camera.
For crop mode I use the 5x zoom, with magic lantern slow low resolution grayscale preview, for framing my shot. And for the recording I use the 10x zoom, which gives me nice high resolution live view, although not the correct framing( more zoomed in.
Quote from: Levas on August 25, 2017, 04:44:56 PM
@ keepersdungeon, replied your message about the lagging video.
Using adtg_gui for crop mode recording is a pain in the ... you have to alter several settings/registers with adtg_gui and then it works, BUT as far as I know, you can't save these register/settings and therefore you would have to rechange them every time you turn on your camera.
For crop mode I use the 5x zoom, with magic lantern slow low resolution grayscale preview, for framing my shot. And for the recording I use the 10x zoom, which gives me nice high resolution live view, although not the correct framing( more zoomed in.
Thank for all the infos @Levas
I switch to canon normal display when I zoom in that way i'm sure what I see is what I get
Thank you for the FPS tip.
Had couple of weird artifact when zoomed in to x10 the screen goes crazy with weird colors all over flickering, but installed the experiment version raw12-10bit from august21 seemed to fix it (not sure should test it more, It could be just luck) but I had other problems u can check them out here.
Quote from: keepersdungeon on August 26, 2017, 12:03:25 PM
I'm downloaded the latest experiment version for the 6D (21august)
1-When u activate the FPSoverride the whole image becomes brighter and overexposed , and looks like shutter speed doesn't affect it the only thing that worked was going to f8 or f16, didn't have that prob with previous version (Jul03)
**FPS settings: 24fps, fix, and the rest didn't touch it
2-I'm also getting this error every time I start recording on an empty SD card (error was in both versions jul03 and august21)
"FAILED: "WBAL3: queued:7 failed: 1 (requeued)" and I only get it once it doesn't seem to affect the video though or WB, and have a feeling I only get it when there's nothing on the SD card and I hit Record
After shooting a bit more with the experiment 12 bit raw version of August 21. Adding to the list I mentioned above (FPS and WBAL), I had one weird message saying "unable to write RAW Data" I could not replicate it and I'm not sure if it did something to the photo coz I don't remember which one it gave me this message on.
Anyone having these bugs while trying the experiment 12bit raw version of ML?
Sent from my Pixel using Tapatalk
hey, iam new in this forum,
anyone can tell why the shutter speed is locked on 1/27 in the experimental nightly build magiclantern firmware for the 10/12bit recording?
is this a bug? its always 1/27 but i can change it with the wheel...but no it didnt change in the menu.
bw
Quote from: isoro7 on April 29, 2017, 02:39:03 AM
So i just installed ML on my 6D, the problem is when im within the interface it keeps flickering. There seems to be another menu that keeps flickering in and out. It's a bit troubling or is it normal? please let me know.
i have the same problem, i follow every steps. The ML menu interface switch flickering between canon menu every 10 seconds.
I'm not using the latest experimental build, so can't reproduce what you're saying.
Are you in M mode on the mode dial ?
And I'm wondering, what does your display on top of your 6d say for shutter time ?
Could it be just a wrong number in the ML interface ? I'll always trust on the shutter time which is displayed on the top display of the Canon 6d.
The menu flickering is a known issue:
https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-100d-70d-in-live-view-mode-ml-menu
Quote from: 123kid on October 01, 2017, 06:49:51 PM
anyone can tell why the shutter speed is locked on 1/27 in the experimental nightly build magiclantern firmware for the 10/12bit recording?
Reset ML and Canon settings and try it again. Still happening? Try the Nightly build and see if it is happening there. If you can consistantly reproduce the issue write up a detailed bug report either here or in the issues section of Bitbucket:
https://bitbucket.org/hudson/magic-lantern/issues
I don't have access to a 6D so I need to find a volunteer to run a test on that camera. I need to create some test builds and will follow up with a post on how to run the test.
Ok--got everything ready. I need someone to run a test on the 6D. First of all let's start with the current Nightly build.
The way to run the test is fairly simple. Turn on both the mlv_rec and mlv_snd modules and activate those modules. I prefer to reduce the frame to the smallest size because we're only checking for an audio issue. The first time you record an MLV clip the audio meters should work normally. What I'm interested in is what happens on the second through the forth clip. Make sure not to restart the camera between takes. Do the audio meters continue to operate normally?
Please report back then continue on with some test builds. Instead of repeating myself just follow the instructions on the following post only substituting 6D for 7D:
http://www.magiclantern.fm/forum/index.php?topic=9848.msg191123#msg191123
Thanks in advance!
[EDIT] I just realized that if you've been following this test closely you'll see that there is a slight difference between the 6D and 7D. The 6D actually uses StopASIFDMAADC to stop the audio but it is hacked so that SoundDevShutDownIn uses the address for StopASIFDMAADC. The 7D doesn't have that hack and uses SoundDevShutDownIn to stop the audio. That means that the "A" build for the 6D has SoundDevShutDownIn commented out while the 7D has StopASIFDMAADC commented out in the "A" build.
It might seem strange to fix something that is currently working albeit with an ugly hack. I'd like to get rid of that hack in order to make it easier to implement improvements like g3ggo's new sound system branch (https://bitbucket.org/hudson/magic-lantern/branch/new-sound-system).
6D owners-
PLEASE read @dfort's post up above (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191140#msg191140post%20up%20above). We are actually getting closer to receive a green light on a complete new sound-system from @g3gg0 which will soon to be integrated for ML running cams.
In order for this to happen we need at least one or two 6D users to do this brief test (http://www.magiclantern.fm/forum/index.php?topic=9848.msg191123#msg191123test) for us. Only takes no more than 15 minutes of your time.
A and B seem fine, C had the audio failed to stop error.
Thanks @Audionut - Pretty much as expected on A and C. Good to know we can use both SoundDevShutDownIn and StopASIFDMAADC in tandem (build B).
Quote from: Levas on October 03, 2017, 09:44:51 AM
I'm not using the latest experimental build, so can't reproduce what you're saying.
Are you in M mode on the mode dial ?
And I'm wondering, what does your display on top of your 6d say for shutter time ?
Could it be just a wrong number in the ML interface ? I'll always trust on the shutter time which is displayed on the top display of the Canon 6d.
I was thinking the same but the exposure works well in normal mode it's just when u x5.
Sent from my Pixel using Tapatalk
Quote from: dfort on October 05, 2017, 12:20:35 AM
Ok--got everything ready. I need someone to run a test on the 6D. First of all let's start with the current Nightly build.
The way to run the test is fairly simple. Turn on both the mlv_rec and mlv_snd modules and activate those modules. I prefer to reduce the frame to the smallest size because we're only checking for an audio issue. The first time you record an MLV clip the audio meters should work normally. What I'm interested in is what happens on the second through the forth clip. Make sure not to restart the camera between takes. Do the audio meters continue to operate normally?
Please report back then continue on with some test builds. Instead of repeating myself just follow the instructions on the following post only substituting 6D for 7D:
http://www.magiclantern.fm/forum/index.php?topic=9848.msg191123#msg191123
Thanks in advance!
[EDIT] I just realized that if you've been following this test closely you'll see that there is a slight difference between the 6D and 7D. The 6D actually uses StopASIFDMAADC to stop the audio but it is hacked so that SoundDevShutDownIn uses the address for StopASIFDMAADC. The 7D doesn't have that hack and uses SoundDevShutDownIn to stop the audio. That means that the "A" build for the 6D has SoundDevShutDownIn commented out while the 7D has StopASIFDMAADC commented out in the "A" build.
It might seem strange to fix something that is currently working albeit with an ugly hack. I'd like to get rid of that hack in order to make it easier to implement improvements like g3ggo's new sound system branch (https://bitbucket.org/hudson/magic-lantern/branch/new-sound-system).
With the current nightly build sound seem to work all through second and 4th time.
Although with the tests A/B couldn't see if it's working coz try to record with them I get "setup Fail. Memory card full" message error on the screen
Hi 6D users -- I got another one for you. How about crop_rec?
We're making changes on the crop_rec module that should make it easier to add cameras to it. I realized that the 6D might already work with it so I compiled a module that supports the 6D and uploaded it to my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Like other cameras besides the 5D3 it just supports the basic 3x3_1X mode but that is a pretty cool feature. Set the Canon menu to 1280x720 50/60 fps and you should be able to record 60fps in a wide aspect ratio without the ugly aliasing caused by 5x line skipping in the regular 1280x720 (mv720) setting. This works both in raw and H.264. The 6D has a slower write speed than the 5D3 so it won't be able to do slow-mo raw but you can FPS override or use H.264 with it. Note that the LiveView screen will look a little strange with this module.
It is also possible to add lossless compression to the 6D and I'm looking into it. I don't have access to the camera so if anyone wants to pitch in and help it would be greatly appreciated. This is the branch (https://bitbucket.org/daniel_fort/magic-lantern/branch/crop_rec_4k_6D_wip) I'm working on. One piece of the puzzle that I'm missing is the SRM_BUFFER_SIZE. There's a good chance it is the same as some of the other cameras but it would be great if a tech savvy 6D owner could verify it on the camera. (Hint - print it from srm_malloc_cbr)
will try it tomorrow
As long as you're going to try it--how about the whole crop_rec_4k enchilada?
https://bitbucket.org/daniel_fort/magic-lantern/downloads/
Look for the one named: crop_rec_4k.2017Oct15.6D116.zip
Everything in my previous post applies except now you have lossless compression too. This is a highly experimental build. I'm taking a guess that SRM_BUFFER_SIZE is the same as the 5D3. If that doesn't work I'll have to make a special build that prints the value of the SRM_BUFFER_SIZE on the screen.
@dfort You got my attention :D
Tested the highly experimental build: crop_rec_4k.2017Oct15.6D116
Used the mlv_rec module and the crop_rec module (So not MLV_Lite)
And I got this error on screen and I believe error 70 on the top display
QuoteML ASSERT:
SRM_BUFFER_SIZE == raw_buffer_size
at ../../src/exmem.c:380 (srm_malloc_cbr), task RscMgr
lv:1 mode:3
RscMgr stack: 174e70 [174f88-173f88]
0xUNKNOWN @ ea80:174f80
0xUNKNOWN @ 39dbc:174f58
0x00039AB4 @ ff0ef3d0:174f20
0xUNKNOWN @ 39ae4:174f10
0xUNKNOWN @ 39b6c:174ef0
0xFF202134 @ ff204488:174ed8
0xUNKNOWN @ ff202304:174eb0
0x0044C930 @ 45b8ec:174ea0
0x0044C468 @ 44c990:174e70
Magic Lantern version : Nightly.2017Oct15.6D116
Mercurial changeset : 5a67a9cd8aa9 (crop_rec_4k_6D_wip) tip
Built on 2017-10-16 01:49:21 UTC by rosiefort@RosieFoComputer.
Free Memory : 304K + 2315K
Wanted to try the crop_rec module from the 6D-crop_rec.zip.
But I can't get it to work with the latest nightly build for 6d ?
It won't load/link the modules at camera startup.
While changing memory cards a few times for testing the builds of dfort, I got two times that the red led led light started burning and stayed on while the camera didn't react to on/off button, battery pull solved it. Never seen this before, should I be worried that the error from a few post earlier has to do with this behaviour ?
It looks like crop_rec_4k isn't quite ready. I'll need some more help from a 6D user. Please PM me so we don't hijack this topic.
Word has it this version is working with lossless recording. Levas tested it:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2017Oct17.6D116_lossless.zip
Will post commit soon.
Lossless recording in the above build, use the mlv_lite module not the standard mlv_rec.mo module
Right, mlv_lite has lossless compression but no sound capabilities and mlv_rec can use mlv_snd but doesn't have lossless compression. There is an option to do H.264 proxies with mlv_lite which works great on the 5D3 but I haven't been able to getting it running properly on other cameras.
Thanks to Levas and NunoCaldeira for the testing and a huge thank you to Danne for finding a critical piece of code that I overlooked.
Let's start testing out crop_rec_4k on the 6D. Things to try out: crop_rec module - is it working? How about compressed silent pictures? If someone could run this test (http://www.magiclantern.fm/forum/index.php?topic=7473.msg191590#msg191590) it would be really helpful.
Pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff) is open. Test build on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). I'll keep it updated with any changes to the crop_rec_4k branch.
Wait wait, could be that it needs a little finetuning.
The frames I get with lossless recording are a little weird, first I thought it was me who was doing things wrong with converting the mlv's to dng's with some older mlv_dump versions.
But it turns out that the silent picture module, which can create lossless dng's, also gives weird frames.
Here's an example of a normal silent picture and a lossless silent picture
http://drive.google.com/drive/folders/0B1BxGc3dfMDaNGZtLWwtYVd5WXc?usp=sharing (http://drive.google.com/drive/folders/0B1BxGc3dfMDaNGZtLWwtYVd5WXc?usp=sharing)
There might be some unhandled case in our lossless decoder and maybe also in dcraw, or there may be some encoder misconfiguration.
Test #1 - you can use any build with lossless compression enabled:
To find out whether the fault is in our decoders, or on the encoder side, try loading a lossless silent DNG in pic_view from file_man. Only run this if mlv_dump or dcraw output is obviously wrong (maybe as in the above example, maybe with other defects).
Results:
- Looks fine? The problem is in our PC-based decoders (dcraw, mlv_dump).
- Image from pic_view has the same defects as with dcraw/mlv_dump? The problem is in the encoder configuration (lossless.c).
- Image from pic_view broken, or playback doesn't work? Look at Canon's lossless decoding stubs, or at the way we call it from pic_view/mlv_play.
Test #2 - you need to compile a custom silent.mo:
To check whether this bug affects your camera (applies to any model that supports lossless compression), or to investigate and hopefully fix it, follow these steps:
Step 1: save some image as both 14-bit lossless *and* 14-bit uncompressed (it *must* be the same image, not just the same static scene):
diff -r 8ee7858f0d7e modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -560,3 +560,5 @@
if (!ok) bmp_printf( FONT_MED, 0, 83, "DNG save error (card full?)");
- return ok;
+ extern void reverse_bytes_order(char*, int);
+ reverse_bytes_order(raw_info->buffer, raw_info->frame_size);
+ /* fall through */
}
Step 2: compare the raw data and check whether there are any differences (on 6D and 650D, there will be; on other models, hopefully not):
dcraw -4 -E 12340000.DNG 12340001.DNG
md5sum 12340000.pgm 12340001.pgm
Step 3: if the two checksums are different, investigate the differences (tutorial (https://rcsumner.net/raw_guide/RAWguide.pdf)):
octave:1> a = imread('12340000.pgm');
octave:2> b = imread('12340001.pgm');
octave:3> manual inspection, imshow(a - b, []) etc
Step 4: adjust the lossless decoder (either the one from dcraw, or lj92.c from mlv_dump) or the encoder configuration (http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989) (lossless.c) until these differences disappear (how? I don't know, you need to experiment)
Step 5: repeat for 650D and all other models (I've ran this test on 5D3, got identical checksums at step 2)
Good luck!
Test 1
Result
- Image from pic_view has the same defects as with dcraw/mlv_dump? The problem is in the encoder configuration (lossless.c).
Test 2
Made 2 pairs of silent pics with a custom silent.mo (with some help from Dfort ;D)
https://drive.google.com/drive/folders/0B1BxGc3dfMDaaDhrcTVCNkJ4a2s?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDaaDhrcTVCNkJ4a2s?usp=sharing)
There's also a 5th picture in this directory, it's a silent dng, but it shows nothing, but it has the full file size? This happened before with the silent module which can handle lossless.
Step 1 is done
Can other people help with step 2, 3, 4 and 5 (see post from Alex above)
Ok, I believe I have done step 2.
Got two pgm files from the number 2 images I posted, did md5sum check and got two different checksums, as expected...
18c6f801394a14aa87bc5159f9c73c74
VS
dc8cc8bb8eda68bd63551228b435de1f
So next step 3...
Here are the md5sum values for all of the files @Levas uploaded:
3864c9ff665c0377f79590c6121838bd 1-lossless.pgm
7a504ba8fdb627b3706abc8c3f69a672 1-normal.pgm
dc8cc8bb8eda68bd63551228b435de1f 2-lossless.pgm
18c6f801394a14aa87bc5159f9c73c74 2-normal.pgm
69373f9824213b4cd65933bc1e37091c No-image-normal-mode.pgm
Uh oh -- got some studying to do. Not well versed in octave.
octave:1> a = imread('1-normal.pgm');
octave:2> b = imread('1-lossless.pgm');
octave:3> manual inspection, imshow(a - b, []) etc
parse error:
syntax error
>>> manual inspection, imshow(a - b, []) etc
^
[EDIT]
octave:4> imshow(a - b, [])
(https://farm5.staticflickr.com/4452/23919555418_0476987def.jpg) (https://flic.kr/p/CrFYtU)
Alright, so the defect appears to be a per-channel offset. Let's check the two images that are supposed to be identical - will look at the 4 Bayer channel differences (R, G1, G2, B):
octave:1> a = imread('2-normal.pgm');
octave:2> b = imread('2-lossless.pgm');
octave:3> for i = 1:2, for j = 1:2,
> chd = (a-b)(i:2:end,j:2:end);
> disp([min(chd(:)), max(chd(:))])
> end, end
128 128
256 256
512 512
1024 1024
Result: each channel differs from the ground truth by a constant value (that happens to be power of 2!)
There are no other differences (that was the role of min and max).
Let's check the other pair of images (slightly different scene, so you can't draw many conclusions from their raw difference). Will check only their optical black area; in this case, min and max will no longer be relevant, as we will be looking at two different samples; let's take a look at median differences (median is statistically robust):
octave:4> a = imread('Silent-14bit.pgm');
octave:5> b = imread('Silent-lossless.pgm');
octave:6> for i = 1:2, for j = 1:2,
> chd = (a-b)(i:2:end,j:2:50);
> disp([min(chd(:)), median(chd(:)), max(chd(:))])
> end, end
0 128 214
151 256 329
397 512 599
961 1024 1092
Result: median differences are the same as before!
This defect is likely predictable and can be easily worked around in post. Let's check the actual black levels (if you didn't do the math already):
octave:7> for i = 1:2, for j = 1:2,
> obch = b(i:2:end,j:2:50);
> disp(median(obch(:)))
> end, end
1919
1791
1536
1024
Dial these values in darktable (the 4 black level sliders) and the image is back to normal :)
Homework for you: hardcode the above black levels in the DNG with exiftool / exiv2 / whatever you prefer.
Amazing. Here's the 1-lossless.DNG file Levas uploaded:
(https://farm5.staticflickr.com/4489/37104900923_104f80693d_c.jpg) (https://flic.kr/p/YwQjk6)
Quote from: a1ex on October 18, 2017, 04:12:27 PM
Homework for you: hardcode the above black levels in the DNG with exiftool / exiv2 / whatever you prefer.
@Danne -- you're the exiftool / exiv2 expert, want to give it a shot?
So this can only be worked out in post or is there something more we need to do to get lossless working on the 6D? Does this also apply to the issues on the 650D?
It can be worked around in post, or - preferably - it can be fixed in lossless.c. The only issue - I have no idea where to start. Maybe this (http://www.magiclantern.fm/forum/index.php?topic=18443.msg183169;topicseen#msg183169) can help. Or running Canon's compression routine in QEMU and comparing register configurations with our own. BTW, is the defect present on a full-res silent picture? What about different resolutions?
The issue from 650D is not that obvious, but you can look into it if you like math ;)
Quote from: a1ex on October 18, 2017, 05:16:47 PM
BTW, is the defect present on a full-res silent picture?
We found out that the defect on the 650D doesn't appear in a FRSP. The 6D probably needs my hack (https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff) in order to save a lossless FRSP. I'd give you a proper fix but I have no idea where to start. ???
Could a 6D user please check and see if you can save a lossless Full Resolution Silent Picture using the crop_rec_4k test build (https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k.2017Oct17.6D116.zip) I posted?
Tried the build, but I can't take full res silent pics with it, at least not lossless.
Normal dng full res works, but if lossless is activated, no image is saved on the card :-\
I posted a new build with the FRSP hack that works with the EOSM/100D/650D/700D. Hopefully it will also work with the 6D.
https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k_with_lossless_FRSP.2017Oct18.6D116.zip
Tried Dfort latest build, but can't get any lossless full res silent pics with it.
Normal full res silent pics works.
Can other people with 6d confirm ?
Confirmed.
(https://imghost.io/images/2017/10/19/VRAM0.jpg)
dfort, I prefer for conversation to be in this thread, it's pretty much what this thread is here for. The problem I find with pm is that the conversation gets segregated to those in the pm.
I like to follow along, even if I don't have the time to jump in and swim with the rest of you. :)
Nice to see devs bugging a1ex with stuff. Keeps the brain ticking. Good work.
Digging through lossless.c because Alex said the problem is there.
Can't find anything about the black levels.
http://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/modules/silent/lossless.c?at=crop_rec_4k_6D.116&fileviewer=file-view-default (http://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/modules/silent/lossless.c?at=crop_rec_4k_6D.116&fileviewer=file-view-default)
However, lossless.c also uses raw.h, where black levels are written into the file, only thing is, the black levels seems to be autodetected :-\
http://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/src/raw.h?at=crop_rec_4k_6D.116&fileviewer=file-view-default (http://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/src/raw.h?at=crop_rec_4k_6D.116&fileviewer=file-view-default)
You won't find it in ML source - it's in Canon code (and maybe not in the ARM side of the code, which you can inspect and emulate, but in their image processor, which is a black box to us).
Since Canon code configures the lossless encoder properly (they don't have this issue in CR2 files), but we have it, all we can do is to compare the encoder configuration (hardware registers) done by their code (by logging their still photo capture process) vs our own code (by logging a lossless encoding session in the same way). You can do that with dm-spy-experiments (http://www.magiclantern.fm/forum/index.php?topic=18443.msg183169#msg183169) (limitation: you can only see the registers set from high-level functions; some are set by writing directly to MMIO - you won't see these with this method), or by running both codes in QEMU ("-d io" shows all registers, including those set directly), but the latter method requires understanding the photo capture and the lossless encoding processes well enough to be able to emulate them.
So far, the 6D is the only single-digic model that runs ML, but cannot be emulated in QEMU. What are you waiting for?! (http://www.magiclantern.fm/forum/index.php?topic=2864.msg190823#msg190823)
Also, this PR (new DryOS task hooks) (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff) is open since 2015, and I'd really like to have it in the nightly builds (100D, 70D and EOSM2 are all waiting for it), but other than 2 screenshots from Audionut, there was zero feedback from 6D users. What are you waiting for?!
Yeah, I know, neither option will give you 4K at 300 FPS...
Quote from: Audionut on October 19, 2017, 12:30:19 PM
...The problem I find with pm is that the conversation gets segregated to those in the pm....
Right, I was us PM's instead of IRC to get a rapid exchange going with a small group until we got something worth sharing. I believe the firewall where I work might be blocking IRC. I was also anticipating some camera lock ups and possibly needing a new firmware dump to see if maybe the one I was using. In any case, we're back on the forum and it would be great if more 6D users would get involved in this crop_rec_4k experiment and comment both here and on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff) which, by the way Audionut I put you down as a reviewer because you know a lot more about this camera than I ever will.
Back to the testing--I'm still not sure if the crop_rec module is working. Loading only the crop_rec module, does it look stretched vertically like this when the Canon menu is set to 1280x720?
(https://farm5.staticflickr.com/4495/37740919371_d50b343a26.jpg) (https://flic.kr/p/Zv35sp)
or does it look normal like this:
(https://farm5.staticflickr.com/4494/37031491424_37879449a1.jpg) (https://flic.kr/p/Yqm5f5)
I see other people are getting those diagonal lines on their ML Screenshots, any idea what is causing that and if there's a way to fix it?
Quote from: dfort on October 19, 2017, 08:43:11 PM
which, by the way Audionut I put you down as a reviewer because you know a lot more about this camera than I ever will.
You're to kind.
Quote from: dfort on October 19, 2017, 08:43:11 PM
Back to the testing--I'm still not sure if the crop_rec module is working. Loading only the crop_rec module, does it look stretched vertically like this when the Canon menu is set to 1280x720?
(https://imghost.io/images/2017/10/20/VRAM1.jpg)
Looks fine to me.
Quote from: dfort on October 19, 2017, 08:43:11 PM
I see other people are getting those diagonal lines on their ML Screenshots, any idea what is causing that and if there's a way to fix it?
Turns out those lines are underexposure zebras, jpg based of course. Well, the only way I can make them appear is to underexpose.
edit: Hang on, it appears that overexposure zebras are being displayed in some funky situations. This needs further testing.
edit2: In a severely underexposed scene.
(https://imghost.io/images/2017/10/20/normal.jpg)
This is silent.mo normal DNG. Initial full white screen, then the black areas become overlayed. You can see the background white around the spot meter.
(https://imghost.io/images/2017/10/20/lossless.jpg)
Lossless DNG. Replace black overlay with stripes.
Also, the help dialog says that raw zebras need raw shooting enabled, when I was performing the test above (crop_rec only enabled). Enabling mlv_something does the trick (obviously), but I have no idea how that plays with crop_rec. The crop_rec stuff happened after I lost time for this project, so I've only been very loosely following, but I assumed crop_rec was raw based.
Quote from: a1ex on October 19, 2017, 08:00:28 PM
Also, this PR (new DryOS task hooks) (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff) is open since 2015, and I'd really like to have it in the nightly builds (100D, 70D and EOSM2 are all waiting for it), but other than 2 screenshots from Audionut, there was zero feedback from 6D users. What are you waiting for?!
What are
you waiting for? :P
Confirmation from more 6D users.
Something else in Stack trace (aka backtrace) in crash logs (https://bitbucket.org/hudson/magic-lantern/pull-requests/849/stack-trace-aka-backtrace-in-crash-logs/diff).
Serial flash contents (https://www.magiclantern.fm/forum/index.php?topic=15088.msg186141#msg186141).
The last one seems obvious that you are still waiting for. If you're willing to do that easy coding task, and the dev team are willing to help with any issues that crop up while performing the required tasks, I'm willing to put the (remaining) effort in. I need my hand held. Bonus points if you compile the module also.
I just need life to settle down a little more before I go and commit to time (for this project) that I don't have.
Soon after enabling the new DryOS hooks on 100D, we ran into trouble (http://www.magiclantern.fm/forum/index.php?topic=16040.msg190279#msg190279) (check the next few pages - some cameras unable to start). That particular issue was fixed meanwhile, but...
This wouldn't have happened if a few knowledgeable 6D users would have tried the PR and reported the issue (they had about 2 years to try it and notice the error). I prefer these changes to be tested by somebody familiar with the codebase before they get into the build recommended to regular users for first-time use. And backend changes like this one, which can possibly affect each and every ML function (hopefully none of them) should deserve a little more attention from those who can read the source code (and understand at least some of it).
(I've bumped this PR once (http://www.magiclantern.fm/forum/index.php?topic=15088.msg187593;topicseen#msg187593), but it's not fun...)
Quote from: Audionut on October 20, 2017, 03:30:41 AM
Serial flash contents (https://www.magiclantern.fm/forum/index.php?topic=15088.msg186141#msg186141).
The last one seems obvious that you are still waiting for. If you're willing to do that easy coding task, and the dev team are willing to help with any issues that crop up while performing the required tasks, I'm willing to put the (remaining) effort in. I need my hand held. Bonus points if you compile the module also.
Bonus point - did the easy coding task and posted a sf_dump module that should work with the 6D on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Also submitted a pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/876/add-6d116-to-sf_dump-module/diff) with @Audionut and @Levas as reviewers.
Totally understand about not having time--life happens.
I was hoping there might be other 6D users able to follow a tutorial (http://www.magiclantern.fm/forum/index.php?topic=12177.0), but...
I don't have access to a 6D and my wife will leave me if I get another camera. Last one I bought was a used C300. Don't worry, I don't plan to put ML on it, I'm not that crazy -- though it does have a 4k sensor...
Back on topic, will the SFDATA.BIN help get the 6D working in QEMU?
I hope so. If that won't work, I'll also need a startup log (dm-spy-experiments branch) with mpu_send and mpu_recv stubs (but for now, the errors I'm getting appear to be from incorrect serial flash contents).
Quote from: a1ex on October 20, 2017, 07:44:04 AM
I was hoping there might be other 6D users able to follow a tutorial (http://www.magiclantern.fm/forum/index.php?topic=12177.0), but...
... drawback with blindly supported cams ...
Download statistic shows 1000+ 6D nightly build downloads frequently. I suppose most 6D users (the kind actually doing stills/movies) won't show up in this forum because things run pretty well for them and they are unaware their help is needed to make it even better. I'm doing quite the same with other open source stuff: Just looking for updates.
Maybe some message box/hint in 6D download page would help finding some computer-savvy photog willing and able to give back.
Another problem is that for most users, compiling ML yourself, is the biggest hurdle.
I tried it last year on OSX. For testing purposes for 10/12 bit.
Followed a tutorial on the forum and after copy and paste some stuff in terminal app, I got ML source code on my computer.
After that I could made small changes to the code and compile ML for testing purposes.
But the compiling step was also difficult, never really understood how to use it properly.
Most off the times I ended up with builds which didn't work for the 6d, or the modules wouldn't work with the ML version.
Lot's of errors are reported during the compiling, which seems normal I learned.
But if you're doing stuff you don't fully understand, it scares the shit out of you :P
At last I ended up compiling only the module I altered and tested it in a ML build from someone else, which worked with the module I compiled.
So the whole compiling thing didn't feel comfortable to me.
I guess it seems really straightforward and simple if your used to programming or really savvy with computers.
But for most of us, using the terminal app (or for windows user, using the command prompt) is already a big deal.
It feels like besides risking to brick our cameras with ML, were also risking to brick our computers :P
The last week I could do tests with the help of Dfort, he compiled the builds needed for testing and shared it with PM.
Works for me, works for Dfort and the end result for ML community is the same.
If things needs to be tested for the 6d, I'm happy willing to help. But I prefer a compiled build which is ready for use.
Also wanna help with the pull request Alex mentioned:
http://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff (http://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff)
If someone can provide me two builds, or maybe one build with the alterations only is enough, I'll be able to post two screenshots of the Free Memory dialog
Yay! We've got a virtual 6D.
(https://farm5.staticflickr.com/4445/37761583516_76e1326ecd.jpg) (https://flic.kr/p/ZwRZbL)
Well almost:
[EOS] loading './6D/ROM0.BIN' to 0xF0000000-0xF0FFFFFF
[EOS] loading './6D/ROM1.BIN' to 0xF8000000-0xF8FFFFFF
[MPU] FIXME: no MPU spells for 6D.
So put the cork back on the bottle. There's more work to be done.
@Levas - Compiling has gotten a whole lot easier since you tried it a year ago. I'd suggest giving it another try with the latest scripts. In fact I just rebuilt my QEMU environment on my Mac and was amazed at how much it has improved since I first attempted it. Thanks to a1ex and kichetof!
Posted new-dryos-task-hooks and dm-spy-experiments 6D.116 builds for testers. The dm-spy-experiments was built with CONFIG_DEBUG_INTERCEPT_STARTUP and I added some modules that might help move this along. Is the mpu_dump module something that should be run or is just the startup log needed?
Note to testers, search for instructions because this has probably been done before on other cameras.
As always, the builds are on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and may be changed or removed without notice.
@Alex
Got two screenshots from Free Memory Dialog.
https://drive.google.com/drive/folders/0B1BxGc3dfMDaTHUwR2kzNjNsbms?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDaTHUwR2kzNjNsbms?usp=sharing)
One is from the nightly build for 6d, 4 okt 2017 and one is from a build according to this pull request:
https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff)
How about posting the screenshots to make it easier to compare yours to the ones Audionut posted on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff#comment-41395257).
Nightly
(https://farm5.staticflickr.com/4474/37125159094_80236f61f3.jpg) (https://flic.kr/p/YyC9nU)
New DryOS task hooks
(https://farm5.staticflickr.com/4486/37125158254_80783f947d.jpg) (https://flic.kr/p/YyC98q)
Hello!
I have tried crop_rec module to record video(crop_rec_4k.2017Oct17.6D116).
h.264 1080p and 720p.
Aliasing problem didn't changed. Picture has bad aliasing caused by 5x line skipping.
Lossless compression tests with all bit depths have the same problem:
(http://thumb.ibb.co/fPt1MR/M22_1408_14bit.jpg) (http://ibb.co/fPt1MR)
Maybe I'm doing something wrong.
Thanks :)
Looks good. Can you also check the CPU usage and get some screenshots of "Debug - Show tasks" ?
Also, it would be great if you can play a bit with it and look for crashes and other weird behaviors not present in the regular nightly (aka regressions). This backend has the potential to alter any ML tasks (ideally it shouldn't change anything, but who knows).
Committed another test I'd like you to run: selftest.mo - null pointer test. It's what caused trouble on 100D after merging this backend.
Also note the lua_fix build (Experiments page) has a few additional selftest's - can you also run the stubs API from there, and also api_test.lua?
EDIT:PROBABLY DID USE WRONG BUILD HERE FIRST, FIRST TESTRESULTS ARE USELESS, WILL DO TESTS AGAIN WITH THE RIGHT BUILD.
UPDATED, screenshots shown here are done with the right build 'new-dryos-task-hooks.2017Oct20.6D116'
@alex
When camera is idle, cpu usage floats around 3,5 %
Show tasks:
(https://farm5.staticflickr.com/4446/37878965071_412cb9df71_b.jpg) (https://flic.kr/p/ZHeACF)
(https://farm5.staticflickr.com/4493/37878964811_a80f00eaa1_b.jpg) (https://flic.kr/p/ZHeAyc)
Quote from: dfort on October 20, 2017, 06:23:20 PM
Posted new-dryos-task-hooks and dm-spy-experiments 6D.116 builds for testers. The dm-spy-experiments was built with CONFIG_DEBUG_INTERCEPT_STARTUP and I added some modules that might help move this along. Is the mpu_dump module something that should be run or is just the startup log needed?
Note to testers, search for instructions because this has probably been done before on other cameras.
As always, the builds are on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and may be changed or removed without notice.
Am I right in thinking we need to have lossless full res silent pictures working on the 6d before the dm-spy-experiments are of any use ?
That way we can compare Normal CR2 file taken by canon to a lossless full res silent picture
Quote from: a1ex on October 21, 2017, 10:55:55 PM
Committed another test I'd like you to run: selftest.mo - null pointer test. It's what caused trouble on 100D after merging this backend.
@Alex, can't find the null pointer test in the Selftest menu in the 'New DryOS task hooks' build Dfort made ???I find the commit:
https://bitbucket.org/hudson/magic-lantern/commits/84dd3fdfe3c69ce111b7b8729739595e36bf3aa0?at=unified (https://bitbucket.org/hudson/magic-lantern/commits/84dd3fdfe3c69ce111b7b8729739595e36bf3aa0?at=unified)
Can't compile a build myself yet. Anybody else is willing to compile ?
Quote from: a1ex on October 21, 2017, 10:55:55 PM
Also note the lua_fix build (Experiments page) has a few additional selftest's - can you also run the stubs API from there, and also api_test.lua?
Have run the stubs api test, didn't know what to do with it, made a screenshot, seems to me like the test fails, it's hanging, doing nothing ?
(https://farm5.staticflickr.com/4507/37846645912_9c9dd13508_b.jpg) (https://flic.kr/p/ZEnXgN)
Have run the api_test.lua, here's the log file:
https://drive.google.com/drive/folders/0B1BxGc3dfMDaWmhoMDEzbmpGRDg?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDaWmhoMDEzbmpGRDg?usp=sharing)
Quote from: Levas on October 23, 2017, 01:18:39 PM
I find the commit:
https://bitbucket.org/hudson/magic-lantern/commits/84dd3fdfe3c69ce111b7b8729739595e36bf3aa0?at=unified (https://bitbucket.org/hudson/magic-lantern/commits/84dd3fdfe3c69ce111b7b8729739595e36bf3aa0?at=unified)
Can't compile a build myself yet. Anybody else is willing to compile ?
Looks like you only need the selftest module to run the null pointer test. Compiled and on my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
@Dfort
The selftest module you compiled won't link with the new-dryos-task-hooks.2017Oct20.6D116 build you made :-\
(https://farm5.staticflickr.com/4461/37830420116_65a096f709_b.jpg) (https://flic.kr/p/ZCWMUG)
So much for taking short-cuts.
Uploaded a new complete new-dryos-task-hooks build for the 6D that includes the selftest module. Deleted the old build to avoid confusion.
@Alex and Dfort
Null-pointer test works, no crash and a crash log:
https://drive.google.com/drive/folders/0B1BxGc3dfMDaYmQ4TnRQZ2M4TkU?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDaYmQ4TnRQZ2M4TkU?usp=sharing)
Quote from: a1ex on October 18, 2017, 04:12:27 PM
This defect is likely predictable and can be easily worked around in post. Let's check the actual black levels (if you didn't do the math already):
octave:7> for i = 1:2, for j = 1:2,
> obch = b(i:2:end,j:2:50);
> disp(median(obch(:)))
> end, end
1919
1791
1536
1024
Dial these values in darktable (the 4 black level sliders) and the image is back to normal :)
Homework for you: hardcode the above black levels in the DNG with exiftool / exiv2 / whatever you prefer.
I've managed to get the lossless 14 bit files right in RawTherapee, look at the raw black point sliders at the right upper corner.
These work with values which are extracted from the baked in black level.
Now look at those numbers, -128, -512, -256 and -1024
Just what Alex explains in his post each offset differs by the power of two.
(https://farm5.staticflickr.com/4472/37835993696_3d1da7c3b1_b.jpg) (https://flic.kr/p/ZDrmJU)
This trick doesn't work with 12 bit or 11 bit lossless files, there's still a little pattern to be seen, probably due to some dividing data and rounding numbers during recording.
Did some more testing with the mlv_lite and lossless 14bit.
All showed frames are corrected for black levels
In full width sensor mode, it always gives half corrupted frames (resolution 1824x1026):
(https://farm5.staticflickr.com/4443/37885608941_f15b14c425_b.jpg) (https://flic.kr/p/ZHPDCa)
But 1808 x 1016 resolution is normal:
(https://farm5.staticflickr.com/4450/24033482118_99c38c68dd_b.jpg) (https://flic.kr/p/CBKSVm)
And 1792 x 1008 has none corrupted frames but, looks like I can see a little pattern showing up:
(https://farm5.staticflickr.com/4503/37885609631_fc492a46c4_b.jpg) (https://flic.kr/p/ZHPDQ4)
Original dng's for download:
https://drive.google.com/drive/folders/0B1BxGc3dfMDabVdqUEdUUGMzckk?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDabVdqUEdUUGMzckk?usp=sharing)
Can you also check 1824x1000, 1002, 1004 ... 1032? Being able to compile should help with this one.
Otherwise, just check (whatever you can select from menu) x (the above heights).
Yes, being able to compile helps. Give the Mac tutorial (http://www.magiclantern.fm/forum/index.php?topic=16012.0) another shot.
In the meantime, do what a1ex says.
I'm thinking that maybe trying a different PREFERRED_RAW_TYPE might be interesting? Search the forum for clues on how to use it.
src/raw.c
#define RAW_DEBUG_TYPE /* this lets you select the raw type (for PREFERRED_RAW_TYPE) from menu */
I prepared a build for testers that allows changing the PREFERRED_RAW_TYPE from the Debug menu. You know where to find it. :D
Tested some different resolutions
1776 x 1000 = normal
1504 x 1002 = Corrupted as the 1824 x 1026 in the post above
1680 x 1008 = normal
1520 x 1012 = (almost) normal - looks a bit like the chroma isn't aligned
1360 x 1020 = (almost) normal - looks a bit like the chroma isn't aligned
1536 x 1024 = gives MLV's which can't be processed to dng's, normal file size ??? (tried multiple files, record a clip twice)
1552 x 1032 = normal
Corrected jpegs and original dng's are here:
https://drive.google.com/drive/folders/0B1BxGc3dfMDaTkpKQ0FpSFMyVmc?usp=sharing (https://drive.google.com/drive/folders/0B1BxGc3dfMDaTkpKQ0FpSFMyVmc?usp=sharing)
Also tried 1824 x different resolutions:
1824 x 986 = corrupted frame
1824 x 1026 = corrupted frame
1824 x 1094 = corrupted frame
Trying different settings for PREFERRED_RAW_TYPE, but so far no luck :P
Gone from 0 to 10 (forget the letters, hexadecimal :P)
And tested 11 all the way to 29, so far no luck :-\
Now I'm out of batteries :P
Most RAW_TYPES, give the half corrupted, are you sure the solution is in the preferred raw type ?
It almost looks like some dimension settings are wrong :-\
Could the problem be in raw.c in the height settings for 6d:
There's this part in raw.c :
Quote
*width = ((bot_right & 0xFFFF) - (top_left & 0xFFFF)) * column_factor;
*height = (bot_right >> 16) - (top_left >> 16);
/* height may be a little different; 5D3 needs to subtract 1,
* EOS M needs to add 1, 100D usually gives exact value
* is it really important to have exact height?
* for some raw types, yes! */
The reason I'm thinking about this is because 10/12 bit had some problems with frames too and it was in the exact frame dimension settings I believe:
Quote from: Levas on December 23, 2016, 03:33:31 PM
@eNnvi
I've tried the following dma flag as used for 700d
uint32_t dmaFlags = 0x20000000
And it causes the 'RAW DETECT ERROR' and when it will record it gives the scrambled frames.
So the only settings that were wrong in your build are the height value settings for the different video modes (width values were all good)
#ifdef CONFIG_6D
*width = zoom ? 2768 : mv720 ? 1920 : 1920;
*height = zoom ? 988 : mv720 ? 662 : 1252; /* find correct mv720 height -- must be exact! */
return 1;
#endif
And the dma flag setting, which must be either
uint32_t dmaFlags = 0x40000000 or uint32_t dmaFlags = 0x60000000
That could be relevant for raw type 0x12 (used with 8..12-bit lossless, but not with 14-bit and other uncompressed modes). To see whether this is the case, try raw type 0x12 for regular 14-bit video. This raw type should be affected by digital ISO (e.g. ISO 320, 400 and 500 should look identical with default settings, but different with raw type 0x12). If height is not exact, only every other frame will be valid (http://www.magiclantern.fm/forum/index.php?topic=19300.msg183106#msg183106) (easy to notice on the non-realtime preview).
Frame corruption: the encoder appears to require image height to be modulo 8. Try commenting out cases 0 and 4 (only the lines with return) in calc_res_y (mlv_lite.c) and see if you can still get invalid frames afterwards.
mlv_lite-edited.2017Oct23.6D116.zip posted. Have fun testing!
Quote from: dfort on October 24, 2017, 05:39:12 AM
mlv_lite-edited.2017Oct23.6D116.zip posted. Have fun testing!
Where do we find it? :)
Dfort's bitbucket download place, he posted a link to it some posts ago.
Quote from: dfort on October 23, 2017, 01:43:59 PM
Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Did some testing with the edited mlv_lite... but it actually got worse :-[ , some resolutions give MLV's without dng's and other resolutions give frames which are sort of allright. None half corrupted frames though.
But I did follow Dfort's tutorial and looks I can compile myself now :D
I downloaded the crop_rec_4k_6D.116 (last updated 18-Oct) branch from Dfort's bitbucket and compiled a 6d build myself.
Did some more investigation on the frames I get.
The frames who have the bottom half corrupted, seem to have a normal upper half. Once black levels are adjusted, the upper half is perfect, with all debayering options.
The frames that did appear perfect in the first place, aren't that perfect at all, they look reasonable with AMAZE debayering, but they look plain wrong with LMMSE or EAHD :o
'normal' frame with AMAZE:
(https://farm5.staticflickr.com/4492/37897073861_e4523d7b3d_b.jpg) (https://flic.kr/p/ZJQpKc)
'Normal' frame with LMMSE:
(https://farm5.staticflickr.com/4506/37897071331_7ab71a1d57_b.jpg) (https://flic.kr/p/ZJQoZz)
'Normal' frame with EAHD:
(https://farm5.staticflickr.com/4473/37187589084_db67052440_b.jpg) (https://flic.kr/p/YE97D3)
Corrupted frame with LMMSE:
(https://farm5.staticflickr.com/4466/37897075351_b3c4ffc69b_b.jpg) (https://flic.kr/p/ZJQqbT)
Corrupted frame with EAHD:
(https://farm5.staticflickr.com/4479/37640270180_5465e570d2_b.jpg) (https://flic.kr/p/Zm9dXw)
So there's more going on then only wrong black levels...
Quote from: Levas on October 24, 2017, 10:50:56 AM
Dfort's bitbucket download place, he posted a link to it some posts ago.
Thank you kindly.
I haven't really followed the ML scene for a long time so i am catching up on all the news.
ah catching up.
In summary, for the 6d, lossless raw recording isn't working yet.
10/12 bit recording on the 6d works perfect, see downloads page and go to experiments.
Quote from: Levas on October 24, 2017, 11:11:20 AM
ah catching up.
In summary, for the 6d, lossless raw recording isn't working yet.
10/12 bit recording on the 6d works perfect, see downloads page and go to experiments.
Thanks, i really follow cause i am still quite a geek but my 6D has been spending too much time in a cupboard rather than shooting.
I think i tried 10bit raw and appreciated it.
Removed the mlv_lite-edited version from my downloads page because it only made things worse.
@ilguercio - there are several test builds in my Bitbucket downloads page: https://bitbucket.org/daniel_fort/magic-lantern/downloads/
I'll leave them up for a while so others can experiment but will remove them when I see we've moved past those tests.
@Levas - good to hear you're able to compile. Now that wasn't so hard, was it?
@dfort - Grandfather of compilers. Could you have a go with this if you have the time?
http://www.magiclantern.fm/forum/index.php?topic=9560.msg192172#msg192172
I see you and a few others been working on reviving ML Raw Viewer. Nice! Anyway, different topic so we'll continue the conversation on that thread.
The getting ready to compile, wasn't that hard. Getting the frames right on 6d with lossless is :P
I'm a bit stuck here, not sure where to look.
As far as I can tell there are 2 different things going wrong, not sure if they're related to the same source thing ?
1 - The black level values per channel.
2 - Frames that are corrupt or not completely right after correcting for the black levels.
Should I test some more preferred raw type values ?
Other things to try ?
Hmmm, sf_dump stuff is completed for 6D?
edit: pm'd a copy to a1ex.
Have new-dryos-task-hooks.2017Oct23.6D116.zip on the card and will test drive as time permits.
Quote from: Audionut on October 28, 2017, 04:26:25 AM
Hmmm, sf_dump stuff is completed for 6D?
Could you also comment on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/876/add-6d116-to-sf_dump-module/diff)?
Quote from: dfort on October 28, 2017, 07:27:09 AM
Could you also comment on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/876/add-6d116-to-sf_dump-module/diff)?
Threw my two cents in.
Thanks @Audionut -- the serial flash file is needed to run the 6D in QEMU.
@alex and other smart people, I'm out of idea's.
Tried many, many things in lossless.c, still can't get simple silent lossless picture with normal black levels.
Tried different read and write connections, altered or deleted other addresses in the piece of code below, doesn't help.
Or I get a picture with wrong black levels, or no picture at all (camera locks up or doesn't save dng etc.)
Quoteelse if (is_camera("5D3", "*") || is_camera("6D", "*"))
{
uint32_t resources[] = {
0x00000 | edmac_channel_to_index(edmac_write_chan),
0x10000 | edmac_channel_to_index(edmac_read_chan),
0x30001, /* Read connection 1 (uncompressed input) */
0x2002d, /* Write connection 45 (compressed output) */
//0x20016, /* Write connection 22 (for WR2 - not used) */
0x50034,
0x5002d,
0x50010,
0x90001,
0x230000,
0x160000,
0x260000,
0x260001,
0x260002,
0x260003,
};
Didn't touch this part though, could it be in here ?
Quoteif (is_camera("5D3", "*") || is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F13068, PACK32(width*2 - 1, height/2 - 1)); /* 0xF6D171F */
EngDrvOut(0xC0F12010, width - 1 ); /* 0xB8F */
EngDrvOut(0xC0F12014, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F1201C, width/10 - 1 ); /* 0x127 */
EngDrvOut(0xC0F12020, PACK32(width/10 - 1, height/20 - 1)); /* 0x18A0127 */
}
/* n
The other specific 6d parts in lossless.c are found in the firmware disassembly by others I've heard, so these parts should't be the problem I guess :-\
Quoteif (is_camera("6D", "1.1.6"))
{
/* ProcessTwoInTwoOutLosslessPath, 6D 1.1.6 */
TTL_SetArgs = (void *) 0xFF3491C8;
TTL_Prepare = (void *) 0xFF4129BC;
TTL_RegisterCBR = (void *) 0xFF411A44;
TTL_SetFlags = (void *) 0xFF359C78;
TTL_Start = (void *) 0xFF412A2C;
TTL_Stop = (void *) 0xFF412A64;
TTL_Finish = (void *) 0xFF412A9C;
}
Quoteif (is_camera("6D", "1.1.6"))
{
Setup_DecodeLosslessRawPath = (void *) 0xFF409218;
Start_DecodeLosslessPath = (void *) 0xFF4092E0;
Cleanup_DecodeLosslessPath = (void *) 0xFF409444;
}
So to summarise the above: Help please
@Levas - I was going to suggest reading the ProcessTwoInTwoOutLosslessPath (http://www.magiclantern.fm/forum/index.php?topic=18443.0) topic but I see you were the first person to reply on that discussion so obviously you've been studying this for a while. Still, it would be good to review it now that you have something that is almost working. Make sure to follow those links to the EDMAC internals topic (http://www.magiclantern.fm/forum/index.php?topic=18315.msg176378#msg176378).
Quote from: Levas on November 03, 2017, 08:32:52 PM
...The other specific 6d parts in lossless.c are found in the firmware disassembly by others I've heard, so these parts should't be the problem I guess :-\
Don't assume we got it right, do a disassembly of your ROM and check it out. It is easy using disassemble.pl posted in the Tutorial: finding stubs (http://www.magiclantern.fm/forum/index.php?topic=12177.0) topic.
Another thing to do is to compile the dm-spy-experiments branch and shoot a CR2 while logging. This will create a lot of information that you can sift through to see what functions are being called that you can look up in your disassembly. You can also merge branches to see what is going on when you shoot a lossless compressed simple silent DNG. That I can help you with.
It might be possible to run some tests on QEMU. The 6D is one of those cameras that doesn't display the GUI but a1ex posted some hints on how it can be used even without the GUI in the ML on EOS-M2 (http://www.magiclantern.fm/forum/index.php?topic=15895.msg185103#msg185103) topic.
This stuff can get overwhelming, believe me I know. It is sort of like that scene from the movie, "The Matrix" :
Quote"You take the blue pill, the story ends. You wake up in your bed and believe whatever you want to believe. You take the red pill, you stay in Wonderland, and I show you how deep the rabbit hole goes."
Ok, kidding aside--
if (is_camera("5D3", "*") || is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
...You could remove the
|| is_camera("6D", "*") and see what happens. The other cameras don't need it.
Hi everyone, still alive and kicking, still no results :P
Tried some more things.
Removed the 6d part of this piece of code, got weird striped frame:
Quoteif (is_camera("5D3", "*") || is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F13068, PACK32(width*2 - 1, height/2 - 1)); /* 0xF6D171F */
EngDrvOut(0xC0F12010, width - 1 ); /* 0xB8F */
EngDrvOut(0xC0F12014, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F1201C, width/10 - 1 ); /* 0x127 */
EngDrvOut(0xC0F12020, PACK32(width/10 - 1, height/20 - 1)); /* 0x18A0127 */
}
Resulting image
(https://farm5.staticflickr.com/4546/26483735049_86bf2e4222_b.jpg) (https://flic.kr/p/Gmh4Kx)
After that, tried disabling lines in that piece of code, after many combinations, seems that 6d can do with only the first line, this will fix the striped pattern|(not the black level issue :-\)
When disabling the first line, and not the others, still stripe pattern as above:
Quoteif (is_camera("5D3", "*") || is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1 )); /* 0xF6D0B8F */
/* EngDrvOut(0xC0F13068, PACK32(width*2 - 1, height/2 - 1)); 0xF6D171F */
/* EngDrvOut(0xC0F12010, width - 1 ); 0xB8F */
/* EngDrvOut(0xC0F12014, PACK32(width - 1, height/2 - 1)); 0xF6D0B8F */
/* EngDrvOut(0xC0F1201C, width/10 - 1 ); 0x127 */
/* EngDrvOut(0xC0F12020, PACK32(width/10 - 1, height/20 - 1)); 0x18A0127 */
}
Read trough the suggested topics, can't get the DM-spy-experiments to work. Still looking into the code, did find out that raw.c also has very new changes made for detecting the black levels and stuff.
See below, not tested changes to the code yet, trying to not brick my camera this week because of one of my kids birthday is coming :D
Quote
/* integer gain used to fix the image darkening caused by lv_raw_gain */
/* this gain must not (!) change the raw data */
int _raw_lv_get_iso_post_gain()
{
if (lv_raw_gain)
{
return 4096 / lv_raw_gain;
}
return 1;
}
Why not just hardcode black level? It´s only metadata anyway?
As far as I know, the black level is already hardcoded, it's always 2047 (in 14 bit)
The problem the 6d has with lossless compression is black level offset differs per color channel.
The lossless dng's we get from the 6d must be adjusted for black levels as follow:
Red channel = -128
Green channel = -256
Green channel = -512
Blue channel = -1024
Which is rather weird because there's only one black level value in the exif, 2047, which should apply to all channels.
So where do these black level offset differences per channel come from :-\
I recently find out about the pieces of black level determinations in raw.c, maybe there's going something wrong in there.
Quote from: Danne on November 08, 2017, 10:13:18 AM
Why not just hardcode black level? It´s only metadata anyway?
+1 (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191858#msg191858). Easy to do with exiftool, see DNG spec 1.4 p.26-27 (sorry for the spoiler).
Unfortunately, dcraw and darktable interpret the per-channel black level in some order, while RawTherapee interprets it in some different order. YMMV with other programs. Adobe's dng_validate 1.3 agrees with the former, so RawTherapee folks will have to prepare for a bug report :D
Quote from: Levas on November 08, 2017, 01:00:24 PM
So where do these black level offset differences per channel come from :-\
Asked and answered (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191910#msg191910).
Quote from: a1ex on November 08, 2017, 02:57:36 PM
Easy to do with exiftool, see DNG spec 1.4 p.26-27 (sorry for the spoiler).
In my case that would be :P
Easy to do It's possible with exiftool, see DNG spec 1.4 p.26-27 (sorry for the spoiler).
I didn't no there where black level options for row and column, I assumed there's was only one black level in the exif.
Now trying to figure out how to fix this with exif tool
Quote from: a1ex on November 08, 2017, 02:57:36 PM
Asked and answered (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191910#msg191910).
The above is very common for clueless people, it means they where not able to get any further with the previous answer they got ;)
But thanks for the answers, again, much appreciated :)
This should work(although I couldn´t get it to work on a file I just tested on):
e.g
exiftool "-BlackLevel=2048" *.dng -overwrite_original
Naturally black level numbers will vary. Think a1ex posted them a few posts up...
As expected, I'm already spending 2 hours with this so called "easy to do task" in exiftool and still no luck.
Ofcourse I can change the 'ordinary' black level, but that isn't the problem here.
I'm trying to change the BlackLevelRepeatDim values, but there's none present in the original dng ?
So trying to add BlackLevelRepeatDim values -> error message:
Warning: Not enough values specified (2 required) for IFD0:BlackLevelRepeatDim
I know it needs 2 values, I'm giving it 2 values.
Typed the following in terminal, all giving the above warning that it needs 2 values:
exiftool -IFD0:BlackLevelRepeatDim=1,1 /Volumes/AppleHDD/Lossless-Testing/14bit_2496_Lossless_frame_000000.dng
exiftool -IFD0:BlackLevelRepeatDim=1 1 /Volumes/AppleHDD/Lossless-Testing/14bit_2496_Lossless_frame_000000.dng
exiftool -IFD0:BlackLevelRepeatDim=1 =1 /Volumes/AppleHDD/Lossless-Testing/14bit_2496_Lossless_frame_000000.dng
exiftool -IFD0:BlackLevelRepeatDim=11 /Volumes/AppleHDD/Lossless-Testing/14bit_2496_Lossless_frame_000000.dng
exiftool -IFD0:BlackLevelRepeatDim=1:1 /Volumes/AppleHDD/Lossless-Testing/14bit_2496_Lossless_frame_000000.dng
Wasn't it working on Darktable back on this post (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191860#msg191860)?
So the latest is that we should add this for the 6D and possibly 650D?
if (is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1));
}
Quote from: dfort on November 09, 2017, 06:11:58 PM
So the latest is that we should add this for the 6D and possibly 650D?
if (is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1));
}
For as far as I have tested it, this should be sufficient for the 6d
So about the black level and black level offset, I'm not sure we're all talking about the same here and I'm confused.
The black level value in the lossless dng's from the 6d is fine, and what I've seen always has a value of 2047 for the 14 bit lossless files on the 6d.
But, as we know, there's however a problem with the black level offset per color channel.
Now Alex and Danne talk about hardcoding the black level, are they talking about the normal black level, which is about 2047, or are they talking about hardcoding these black level offset per color channel.
Is it even possible to change the info in a dng to rebalance the black level offset per channel ?
Another problem is, that this black level offset per channel problem, isn't always solvable.
See this post:
http://www.magiclantern.fm/forum/index.php?topic=15088.msg192226#msg192226 (http://www.magiclantern.fm/forum/index.php?topic=15088.msg192226#msg192226)
There are times that even when compensating for black level offset per channel, there are still yellow and blue pixels in the frame, mostly in the shadows.
I'm not sure if this is, because the blue channel has the biggest offset difference ?
Also, it doesn't work with 10 and 12 bit, when compensating for the black level offset per channel, there's still a raster on the frame, probably because 10/12 bit is lossy and not lossless ?
And if 10/12 bit can't be repaired with compensating for the black level offset per channel, does this mean that the data stream that is put into ProcessTwoInTwoOutLosslessPath
is already wrong, black level offset per channel wrong I mean.
I am talking about the black level tag only. Not the offset tags. Don't know if those can be changed in post?
Hi everyone
My 6D wouldn't turn on and I got it to work again by following these instructions
Quote
bad shutdown
Switch camera Off, remove: battery, card and lens.
Reattach lens, close card slot, reinsert battery and switch camera On again
It won't turn on with the ML memory card though, so I had to fix it a second time.
My question is: do I have to give up ML then? Has anyone been through this and found a way of using it? What could I be doing wrong?
Thank you for your time [=
Make sure to wait some time after "power-down" and after opening card-slot before removing card. ML writes data to card *after* screens went dark.
For defective ML card:
Format in cardreader, then format in cam and reinstall ML from scratch.
Do you have troubles with this card only? Try another one.
Hi,
I'm having a problem after installing and uninstalling ML. the rotating dial on the back of the camera won't respond to left turns. It still works for right turns. I.E. If I try to change the aperture to a lower number, it doesn't work. If I change it to a higher number it works. Very Frustrating. Anyone have any ideas on how that might have happened (other than you know using experimental firmware that is not approved by the manufacturer (: )
Any ideas on how to fix that?
Thanks
jhayes2118
Are there people here who can check if the addresses below, for lossless compression, are right for the 6d ?
I've searched the rom for the addresses, they are are certainly in there, but are they the right ones ?
Changed a few off them, but all changes I tried, made the camera freeze before saving a silent lossless dng :P
Quote
if (is_camera("6D", "1.1.6"))
{
/* ProcessTwoInTwoOutLosslessPath, 6D 1.1.6 */
TTL_SetArgs = (void *) 0xFF3491C8; /* fills TTJ_Args struct; PictureSize(Mem1ToRaw) */
TTL_Prepare = (void *) 0xFF4129BC; /* called right after ProcessTwoInTwoOutJpegPath(R) Start(%d); */
/* calls [TTJ] GetPathResources and sets up the encoder for RAW */
TTL_RegisterCBR = (void *) 0xFF411A44; /* RegisterTwoInTwoOutJpegPathCompleteCBR */
TTL_SetFlags = (void *) 0xFF359C78; /* called next; starts the EDmac transfers */
TTL_Start = (void *) 0xFF412A2C; /* called next; starts the EDmac transfers */
TTL_Stop = (void *) 0xFF412A64; /* called right after sssStopMem1ToRawPath */
TTL_Finish = (void *) 0xFF412A9C; /* called next; calls UnlockEngineResources and returns output size from JpCoreCompleteCBR */
Those addresses should work. The way they were found was by checking disassemblies of various similar cameras. (Digic V)
Found some debug stuff in raw.c and enabled it:
And there are a few things that are wrong
raw2lv -> (-6, -3) - (726,483)
should be (0,0) - (720,480)
raw2bm -> (-6, -3) - (726,483)
should be (0,0) - (720,480)
bm2raw -> (94,36) - (1895,1243)
should be (80,28) - (1910,1252)
And of course, the black check is horribly wrong.
Anybody here who can help to get this right in raw.c for the 6d ?
(https://farm5.staticflickr.com/4525/26642943459_e589570083_b.jpg) (https://flic.kr/p/GAm3S8)
Got one more screenshot, now with 5x zoom mode.
(https://farm5.staticflickr.com/4524/38422740201_66d46c3808_b.jpg) (https://flic.kr/p/21xhA2X)
Doesn't look good to me :P
The initial hypothesis (when I wrote that test) was that the (newly found at that time) raw buffer should match the LiveView buffer, including its corners. Later, it turned out not to be true, so that test is no longer exact (but if you ignore the "roundoff" errors, it's still useful).
For 1x, look in raw_set_geometry - I believe there is an offset of 14 Bayer pixels skipped by Canon code when creating the preview. The test should be updated to account for this offset (e.g. raw_info.active_area.x1 would become raw_info.active_area.x1 + 14), after confirming that offset is correct for other cameras (I've only tested 5D3, and keep in mind my pixel peeping skills aren't the best).
For 5x, the raw buffer contains a lot more than what's displayed (guess why you can record 2...3K in this mode), so that test will display huge errors. In this case, the test would be more difficult to write (somebody has to sit down and do the math); easiest way - it should probably not be interpreted in this mode.
A better check would be to look at raw zebras - are they aligned with Canon's preview? (in all modes)
Outside LiveView, they are computed for every displayed pixel (on the BMP overlay). There, you should see pixel-perfect alignment with the analyzed image.
However, the raw zebras are quite low-res in LiveView - computed every 8 BMP pixels horizontally, so they won't align very well because of this. You could change the code in draw_zebras_raw_lv to operate at byte level (uint8_t instead of uint64_t, plus other adjustments) - it will be slower, but better for checking alignment. There is also zebra_highlight_raw_advanced (used by Auto ETTR when selecting Show metered areas). That one is computed for every BMP pixel, so it might be a better way to check the alignment between raw and LV buffers.
If you like easy coding tasks: what about adding some sort of alignment test in raw_diag? You could reuse RAW_ZEBRA_TEST or the existing zebra drawing functions from zebra.c, and display things in a way suitable for judging alignment (maybe a checkerboard pattern displaying either Canon or ML rendering, alternating between them to make any misalignment obvious).
Regarding your earlier issue - have you tried typing the error message, or the tag you are trying to change, in a search engine?
( advice from http://xkcd.com/627/ )
exiftool "Warning: Not enough values specified (2 required)"
BlackLevelRepeatDim site:magiclantern.fm
per channel black level
;)
Quote from: a1ex on November 14, 2017, 10:27:11 PM
Regarding your earlier issue - have you tried typing the error message, or the tag you are trying to change, in a search engine?
( advice from http://xkcd.com/627/ )
exiftool "Warning: Not enough values specified (2 required)"
BlackLevelRepeatDim site:magiclantern.fm
per channel black level
;)
Already tried googling exiftool and the tag and 2 values, multiple values, altering the tag etc.
But I didn't google the exact error message...now I see, it's a string.
So I tried some other values for BlackLevelRepeatDim...can't crack the math to get normal dng :P
All 4 color channels have a different offset and I can only change 2 values in BlackLevelRepeatDim.
Furthermore, I can't get DM-SPY stuff working, too complicated.
@DFort, maybe you can help make a build, with DM-SPY and lossless silent pic according to these instructions from Alex?
http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168 (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168)
Quote from: Levas on November 15, 2017, 07:06:31 PM
All 4 color channels have a different offset and I can only change 2 values in BlackLevelRepeatDim.
Of course, you have a 2x2 Bayer pattern, not a 4D matrix.
Hint: you should read two pages from the DNG spec, not just one :D
I hate it when you give just about enough information for hours of googling and trial and error and not enough information to solve the problem at once :P
Aaarggghhh !!! ;D
But I'll try cracking the code 8)
Just wondering, do you already know where the problem is, with the 6d.
Only thing left where I think is the problem is in this piece of code in lossless.
Quoteelse if (is_camera("5D3", "*") || is_camera("6D", "*"))
{
uint32_t resources[] = {
0x00000 | edmac_channel_to_index(edmac_write_chan),
0x10000 | edmac_channel_to_index(edmac_read_chan),
0x30001, /* Read connection 1 (uncompressed input) */
0x2002d, /* Write connection 45 (compressed output) */
//0x20016, /* Write connection 22 (for WR2 - not used) */
0x50034,
0x5002d,
0x50010,
0x90001,
0x230000,
0x160000,
0x260000,
0x260001,
0x260002,
0x260003,
};
What's up with all the addresses without commends, do you know where they are for ?
That information is enough to solve the problem, if you actually read those two pages from the DNG spec and put in practice (in exiftool's command line) what you have read.
What we know about ResLock is documented at http://www.magiclantern.fm/forum/index.php?topic=6740.0 and http://www.magiclantern.fm/forum/index.php?topic=18443.msg182989#msg182989
The others are unknown; they can be found by understanding other image processing paths and cross-checking the numbers (that's how the known ones were found). It's what Canon code uses for CR2, and they are not the same in all cameras. Why there are differences - complete mystery.
Short answer: I have no idea where the black level difference comes from. It's likely from encoder configuration, but where exactly... no idea. It's not from our raw backend, for sure. I also doubt it's from these resources (if these are wrong, it either doesn't work, or locks up, or locks out other stuff from LiveView, or locks out unused stuff with no obvious side effects).
However, the defect is easy to work around it - hence that exiftool puzzle. Per-channel black level in DNG is a trick I know from this forum (others described it some years ago).
The defect on 650D is even harder to understand, but that one is likely from resolution-related registers (maybe the ones I'm overriding, maybe others). Other models were just lucky (they happened to work without much tinkering).
Read the information on page 26 and 27 of the adobe dng 1.4 spec over and over again...can't see the light.
Time to sleep
But as I understand correct, you're saying:
Be happy, the 6d has working lossless already, all the data is there, it just need some fiddling with exiftool for the moment, but all the correct data is in the file.
:D
Quote from: Levas on November 15, 2017, 07:06:31 PM
@DFort, maybe you can help make a build, with DM-SPY and lossless silent pic according to these instructions from Alex?
http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168 (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168)
It can get tricky merging the dm-spy-experiments branch. I tried a few different ways but couldn't get it to compile a working silent module--much less with the 6D changes. There have been lots of updates since those instructions were posted back in April using the compressed_raw branch.
I'll update you if I can get something to work but I've also got a question--are you able to save full-res silent picture with lossless compression without requiring my hack pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff)? Yeah, got to figure out a better method because this will never be accepted into the main repository.
Quote from: Levas on November 15, 2017, 09:12:51 PM
I hate it when you give just about enough information for hours of googling and trial and error and not enough information to solve the problem at once :P
I feel your pain. There's something to be said for not being spoon fed though.
If only there were 25 or maybe 35 hours in a day. :D
I followed the instructions and got a working build with working silent.mo, but no lossless compression. ::)
Checking this post:
http://www.magiclantern.fm/forum/index.php?topic=15088.msg191860#msg191860
I see 4 black level numbers to fix the image:
1919
1791
1536
1024
In the dng file I ony see one black level tag stored:
QuoteAlright, so the defect appears to be a per-channel offset. Let's check the two images that are supposed to be identical - will look at the 4 Bayer channel differences (R, G1, G2, B):
http://www.magiclantern.fm/forum/index.php?topic=15088.msg191858#msg191858
And from:
However, the defect is easy to work around it - hence that exiftool puzzle. Per-channel black level in DNG is a trick I know from this forum (others described it some years ago).http://www.magiclantern.fm/forum/index.php?topic=15088.msg193240#msg193240
Ok, so alterning black level tag goes like this:
Example:
exiftool "-IFD0:BlackLevel=1024" Input.dngTesting this gives various results but seems there is more to it.
adding the BlackLevelRepeatDim:
exiftool "-IFD0:BlackLevelRepeatDim=1 1" Input.dngDoesn't appear to change anything.
So what i boils down to is "Per-channel black level in DNG"?
Some additional info:
http://www.openphotographyforums.com/forums/showthread.php?t=12280
@Danne, ah I see you're also trying to solve the puzzle, that's good, because I can't solve it :-\
Others are free to join to solve this puzzle :D
I'm not sure, but I think there are 4 tags at play here:
BlackLevel
BlackLevelRepeatDim
BlackLevelDeltaV
BlackLevelDeltaH
All described in on page 26 to 28 in adobe dng 1.4 spec:
https://www.adobe.com/content/dam/acom/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf (https://www.adobe.com/content/dam/acom/en/products/photoshop/pdfs/dng_spec_1.4.0.0.pdf)
I've read the pages over and over again, but I'm still not sure how black levels are calculated here.
But I think, you can set a global base black level with BlackLevel
And a matrix that's repeated with BlackLevelRepeatDim
With BlackLevelDeltaH you can put an offset per column, in the matrix described with BlackLevelRepeatDim
With BlackLevelDeltaV you can put an offset per row, in the matrix described with BlackLevelRepeatDim
We have 4 channels, Red, Green1, Green2, Blue.
But how to setup the matrix ?
4 by 1, so we get the 4 channels in one row with 4 columns.
R | G1 | G2 | B
Or do we have to set it up as 2 by 2 , So we get two rows with two columns.
R | G1
G2 | B
Or maybe 1 by 4 will work too ?
R
G1
G2
B
A lossless dng straight out off the 6d has a global black level of 2047:
The per channel offset has to be altered in a raw editor as follows:
R = -128 -> Effective black level of 2047 -128 = 1919
G1 = -256 -> Effective black level of 2047 -256 = 1791
G2 = -512 -> Effective black level of 2047 -512 = 1535
B = -1024 -> Effective black level of 2047 -1024 = 1024
Now we need to setup the 4 tags so that the above black levels per channel are in the dng file.
Maybe things get easier if we use a global black level of 1024, that case, the blue offset black level is 0
black level offset would become:
R = 896
G1 = 768
G2 = 512
B = 0
Anybody, ideas for the correct values for the following tags?
BlackLevel
BlackLevelRepeatDim
BlackLevelDeltaV
BlackLevelDeltaH
Got a great idea, took an original CR2 file and put it through adobe DNG converter.
And now let's check the EXIF data in the DNG :D
Some new hints:
| | 16) BlackLevelRepeatDim = 2 2
| | 17) BlackLevel = 2047 2047 2048 2048 (524032/256 524032/256 524288/256 524288/256)
Already tried something with the numbers 524032 and 256 with BlackLevelDeltaH and BlackLevelDeltV but no luck in getting the lossless DNG right :-\
Yeah cracked the code 8)
:D :D :D :D :D :D :D :D
BlackLevel can be one value, but it can also be a string of values ;D
So in order to make the lossless dng's from the 6d normal, use the following exiftool commands:
-exiftool -IFD0:BlackLevelRepeatDim='2 2' FILE.DNG
-exiftool -IFD0:BlackLevel='1919 1791 1535 1024' FILE.DNG
Cool. Was thinking along these lines but didn't really bother to test(thought it was a no go).
Great cracking @Levas.
Fiddling now with 11 bit and 12 bit lossless.
Seems to work with the same black levels as 14bit lossless, although white level needs to be changed to 16300 too.
Seems that 11bit/12bit files have 14bit black level in the dng header, but 11/12bit whitelevel in the dng header ?
Maybe it's caused by the MLV_dump I'm using ?
But 11/12bit files look really good, with this command in exiftool
exiftool -IFD0:BlackLevel='1920 1792 1536 1025' -IFD0:BlackLevelRepeatdim='2 2' -IFD0:WhiteLevel=16200 FILE.DNG
If you pixel peep to 200/300% there seems to be a small pattern in the 11/12bit files, maybe because it's not really lossless, but lossy ?
Quote from: Levas on November 15, 2017, 11:13:19 PM
Be happy, the 6d has working lossless already, all the data is there, it just need some fiddling with exiftool for the moment, but all the correct data is in the file.
Is there anything on the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff) that needs to be changed?
Quote from: Audionut on November 16, 2017, 07:59:39 AM
I followed the instructions and got a working build with working silent.mo, but no lossless compression. ::)
Right, following the instructions--I didn't try that yet. Maybe that same pull request has what's needed to get lossless compression working on your modified compressed_raw/dm-spy-experiments build (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168)?
It doesn't seem right that the DNG files need to be post processed. If we could get a log file out of that special build would it show where the black levels are shifting around?
I'd like to combine this build of Dfort for 6d lossless raw recording with the MLV_Lite with audio recording:
https://www.magiclantern.fm/forum/index.php?topic=16650.msg192065#msg192065 (https://www.magiclantern.fm/forum/index.php?topic=16650.msg192065#msg192065)
Trying to combine these two, not successful yet.
I've got the build of ErwinH, the crop_rec_4k_mlv_lite_snd, from his bitbucket:
https://bitbucket.org/ehoutsma/magic-lantern/src/5f4ed213aaeac50b85ae2578d15e9306c54f9db5/?at=crop_rec_4k_mlv_lite_snd (https://bitbucket.org/ehoutsma/magic-lantern/src/5f4ed213aaeac50b85ae2578d15e9306c54f9db5/?at=crop_rec_4k_mlv_lite_snd)
First, I tried to compile it, as it is, for 6d. But it gives some errors:
QuoteIn file included from ../../src/exmem.c:3:0:
../../src/exmem.c: In function 'srm_malloc_cbr':
../../src/exmem.c:380:12: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
ASSERT(SRM_BUFFER_SIZE == raw_buffer_size);
^
../../src/dryos.h:142:27: note: in definition of macro 'ASSERT'
#define ASSERT(x) { if (!(x)) { ml_assert_handler(#x, __FILE__, __LINE__, __func__); }}
^
../../src/exmem.c:380:12: note: each undeclared identifier is reported only once for each function it appears in
ASSERT(SRM_BUFFER_SIZE == raw_buffer_size);
^
../../src/dryos.h:142:27: note: in definition of macro 'ASSERT'
#define ASSERT(x) { if (!(x)) { ml_assert_handler(#x, __FILE__, __LINE__, __func__); }}
^
../../src/exmem.c: In function '_srm_malloc_suite':
../../src/exmem.c:535:66: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
suite = CreateMemorySuite(srm_buffers.buffer, SRM_BUFFER_SIZE, 0);
^
In file included from ../../src/exmem.c:3:0:
../../src/exmem.c: In function '_srm_free_suite':
../../src/exmem.c:568:24: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
ASSERT(size == SRM_BUFFER_SIZE);
^
../../src/dryos.h:142:27: note: in definition of macro 'ASSERT'
#define ASSERT(x) { if (!(x)) { ml_assert_handler(#x, __FILE__, __LINE__, __func__); }}
^
../../src/exmem.c: In function '_srm_malloc':
../../src/exmem.c:616:9: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
if (SRM_BUFFER_SIZE < size + 4)
^
../../src/exmem.c: In function '_srm_get_max_region':
../../src/exmem.c:650:16: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
return SRM_BUFFER_SIZE;
^
../../src/exmem.c: In function '_srm_get_free_space':
../../src/exmem.c:670:16: error: 'SRM_BUFFER_SIZE' undeclared (first use in this function)
return SRM_BUFFER_SIZE;
^
make: *** [exmem.o] Error 1
So I took the MLV_lite.c and the MLV_sound.c from his build, put it in the build I'm using from Dfort.
https://bitbucket.org/daniel_fort/magic-lantern/src/57dc2077089bb18bd4a5d4172cf37c0bc1347909/?at=crop_rec_4k_6D_wip (https://bitbucket.org/daniel_fort/magic-lantern/src/57dc2077089bb18bd4a5d4172cf37c0bc1347909/?at=crop_rec_4k_6D_wip)
It will compile, MLV_Lite and MLV_SND modules will load.
But there's no audio menu, to activate it. But maybe it's on by default ?
I'v got a lossless MLV file from MLV_Lite, but mlv_dump doesn't extract a wav file out of it :-\
From those compile messages it looks like you are missing the SRM_BUFFER_SIZE in consts.h (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff#chg-platform/6D.116/consts.h).
Yeah, my next step was to merge crop_rec_4k and got SRM errors.
Next was to follow dforts efforts, but ran out of time.
Lets see what today brings.
Still can't get it to work, got more errors with compiling.
First raw.c
Changed it with the one in Dfort's build.
But now I don't get the MLV_Lite module...
Combining the existing build of DFort "crop_rec_4k_6D_wip"
with ErwinH's "crop_rec_4k_mlv_lite_snd"
is a challenge :-\
@DFort
The build as it is now, (Crop_rec_4k_6d_WIP)
doesn't work at 1824 x 1024 resolution.
You get a MLV, but you won't get any dng's from it ?
The MLV is normal in size... :-\
Probably has to do with 'modulo' options in MLV_lite.c Alex talked about.
At the moment only case 6 is optional:
case 6: /* res_x is modulo 2 bytes, so res_y must be modulo 8 */
return res_y & ~7;
When all options where open, we got half corrupted frames with some resolutions.
So I think I got some testing to do here :P
Quote from: Levas on November 16, 2017, 11:05:11 PM
The build as it is now, (Crop_rec_4k_6d_WIP)
That isn't it. That's a branch that I've been experimenting with and it probably isn't working properly. I took down my 6D builds because I didn't want to cause any confusion like this.
I'm talking about a build made off the pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff). I just uploaded a build of it to my Bitbucket downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
There have been several experiments but I'm not sure if anything needs to change in the code or if all the progress is on the post processing end of things. I'm still in the dark whether or not the FRSP hack (https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff) is needed on the 6D or if this needs to change:
lossless.c
if (is_camera("5D3", "*") || is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F13068, PACK32(width*2 - 1, height/2 - 1)); /* 0xF6D171F */
EngDrvOut(0xC0F12010, width - 1 ); /* 0xB8F */
EngDrvOut(0xC0F12014, PACK32(width - 1, height/2 - 1)); /* 0xF6D0B8F */
EngDrvOut(0xC0F1201C, width/10 - 1 ); /* 0x127 */
EngDrvOut(0xC0F12020, PACK32(width/10 - 1, height/20 - 1)); /* 0x18A0127 */
}
I believe you experimented with this but I'm not sure if it fixed anything:
if (is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1));
}
Quote from: dfort on November 16, 2017, 11:54:50 PM
if (is_camera("6D", "*"))
{
/* resolution is hardcoded in some places; patch them */
EngDrvOut(0xC0F375B4, PACK32(width - 1, height/2 - 1));
}
The piece of code above is needed, without this line, I get frames that look scambled, like the one I posted here:
http://www.magiclantern.fm/forum/index.php?topic=15088.msg192884#msg192884 (http://www.magiclantern.fm/forum/index.php?topic=15088.msg192884#msg192884)
I'm not sure about the other lines that are in the same piece of code, they were not needed for normal 1xzoom recording mode on 6D. But I was thinking, maybe those other lines are needed for different recording modes like 3x zoom and stuff, so maybe it's best to leave them all in, they sure didn't hurt recording.
Quote from: dfort on November 16, 2017, 11:54:50 PM
I'm still in the dark whether or not the FRSP hack (https://bitbucket.org/hudson/magic-lantern/pull-requests/858/fix-lossless-compression-on-frsp-for-eosm/diff) is needed on the 6D or if this needs to change:
I think the hack is needed, because I have never been able to get a full-res-silent lossless picture.
Full-res-silent for normal dng works, but not for lossless. When trying to take a full-res-silent lossless, it looks like the camera acts very normal, I think it actually takes one, but it's never saved on the card :-\
@Dfort
I'v downloaded your build of Crop_rec_4k_6d.116
https://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/?at=crop_rec_4k_6D.116 (https://bitbucket.org/daniel_fort/magic-lantern/src/0c3ef797ce995b51e86184049350022d0ee97324/?at=crop_rec_4k_6D.116)
And I'm missing the 'only modulo 8' alterations in MLV_Lite.c
Quote from: a1ex on October 23, 2017, 10:58:02 PM
Frame corruption: the encoder appears to require image height to be modulo 8. Try commenting out cases 0 and 4 (only the lines with return) in calc_res_y (mlv_lite.c) and see if you can still get invalid frames afterwards.
I have it altered like this, so it can only do case 6, modulo 8. But this isn't a solution for the unified build with all camera's :P
So there must be implemented something like, if cameramodel is 6d -> only modulo 8 option
/* res_x * res_y must be modulo 16 bytes */
switch (MOD(res_x * BPP / 8, 8))
{
case 0: /* res_x is modulo 8 bytes, so res_y must be even */
/* return res_y & ~1; */
case 4: /* res_x is modulo 4 bytes, so res_y must be modulo 4 as well */
/* return res_y & ~3; */
case 2:
case 6: /* res_x is modulo 2 bytes, so res_y must be modulo 8 */
return res_y & ~7;
default: /* should be unreachable */
return res_y & ~15;
}
}Without the only modulo 8 alteration, some resolutions give half corrupted frames. Like this:
(https://farm5.staticflickr.com/4443/37885608941_f15b14c425_b.jpg) (https://flic.kr/p/ZHPDCa)
Just a shot in the dark -- maybe the problem is with raw_info.jpeg.height?
/* max image width is modulo 2 bytes and 8 pixels */
/* (EDMAC requires W x H to be modulo 16 bytes) */
/* (processing tools require W modulo 8 pixels for struct raw_pixblock) */
max_res_x = max;
/* max res Y */
max_res_y = raw_info.jpeg.height & ~1;
There have been some updates in crop_rec_4k that affect white and black levels so I merged that along with your mlv_lite hack and my FRSP hack and put a build in my downloads directory (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Of course these hacks will never fly but at least we'll see what we need to work on.
Downloaded your newest build, but full-ress-silent lossless still doesn't work.
It doesn't write a file to the card.
Also one little thing does not work with lossless recording in MLV_Lite. (both normal 14 bit and lossless bitrates)
When maximum 16:9 resolution is selected with MLV_Lite, which is 1824 x 1024, it writes a MLV file, but I can't extract dng's out of it with MLV_dump ?
The MLV file size seems quitte normal.
When using verbose option with MLV_Dump it gives a segmentation fault:
Quote
Block: VIDF
Offset: 0x00000600
Number: 12
Size: 3269120
Time: 157.191000 ms
Frame: #0000
Crop: 80x128
Pan: 80x128
Space: 32
Segmentation fault: 11
For the rest all other resolutions, seem to work with MLV_Lite.
If you change the Aspect ratio to 3:2 can you get more vertical resolution? What is the maximum vertical resolution you can get? Does that give you a valid MLV file? Does going to 1.85:1 work?
The 6D sensor is 5472 × 3648 so the maximum non-crop resolution should be width/3 x height/3 or 1824 x 1216.
Have you ever been able to get a Full Resolution Silent Picture on the 6D? Seems like that's what's needed to perform the tests on that Intercepting DebugMsg with cache hacks link (http://www.magiclantern.fm/forum/index.php?topic=2388.msg183168#msg183168) you pointed to a while back.
Quote from: dfort on November 17, 2017, 10:03:36 PM
Have you ever been able to get a Full Resolution Silent Picture on the 6D?
Yes here. Just not lossless.
Right, sorry--that's what I meant. Everything seems to work as usual but it isn't saved on the card, right?
Yeah, that's how it worked with the last build of yours I tried (pretty sure anyway).
Haven't been able to compile a lossless build here, yet.
@Dfort,
Never had, or was able to make, a working build with full-res-silent lossless.
Max resolution in normal video mode is indeed 1824 x 1216.
1824 x 1216 resolution works, got normal MLV and can extract dng's.
1:85 aspect ratio (1824 x 924) also gives normal MLV.
Only problem is, for as far I tested different resolutions, 1824 x 1024. (before the only modulo 8 fix, this resolution was 1824 x 1026 and gave half corrupted frames)
Uploaded a MLV of 1824x1024 resolution, only 3 second clip, 160Mb in size.
I can't get dng's out of it, with MLV_dump, maybe other options or software works. Maybe only the first frame is wrong or so :-\
https://drive.google.com/open?id=1FBGNrHLltAsKI8zTBWppEmadHY6mFDaQ (https://drive.google.com/open?id=1FBGNrHLltAsKI8zTBWppEmadHY6mFDaQ)
Another thing, I was testing your build last night, just testing, lossless raw recording of different bit depth and resolutions, and I occasionaly got the "raw detect error".
Haven't seen this one in the other builds you send and I've compiled.
Could the "raw detect error" be new and caused by updates or fixes ?
hi, I'm a 6D owner with ML installed on. I would like to have lossless video raw as I can increase resolution with fast sd.
I would to test a build that works at least at 1824 x 924, is that build crop_rec_4k.2017Nov16.6D116.zip?
I'm here, if I can help.. even if I'm not so able but if you need to test something..
to reach higher resolution (and 3x3 binning?) is a must for me.
thank you all involved in this.
crop_rec_4k.2017Nov16.6D116.zip is the build with lossless.
1824x924 lossless should work, 1824x1024 lossless doesn't work.
Somehow some resolutions don't work on the 6d.
In zoom mode you can go as far as 2688x960.
There is however one thing, you need to use exiftool to get the blacklevels right, see posts in this thread.
And ofcourse there is no audio/sound with MLV_lite.
Quote from: Levas on December 02, 2017, 04:29:26 PM
crop_rec_4k.2017Nov16.6D116.zip is the build with lossless.
Ok--good to know. I often delete older builds but I see that one is still on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
By the way, Canon just released firmware update 1.1.8. The 1.1.7 updater is still on Canon's website but 1.1.6 is long gone. Now that Pelican's website is down there is a surging demand on the Black Market for the 1.1.6 firmware updater. ML users are paying 10 times the original price for the free update.
I think I have the 6d 1.1.6 firmware, not at home now, will check later.
In the earlier days it was also available on the official canon website in Canada, not sure if they still have it available over there.
Still have the official 1.1.6 firmware for Canon 6d:
https://drive.google.com/open?id=1_WpYbRMOm_XrjWJxnns1FMiEN0tzZBWV (https://drive.google.com/open?id=1_WpYbRMOm_XrjWJxnns1FMiEN0tzZBWV)
Quote from: dfort on December 02, 2017, 06:20:43 PM
ML users are paying 10 times the original price for the free update.
10 times free is still for free, right :P
Quote from: Levas on December 02, 2017, 07:54:41 PM
10 times free is still for free, right :P
Right!
You have been doing quite a bit of coding recently. Maybe consider doing a firmware update on the 6D. I'd be happy to help out. All you need is the Portable ROM dumper (bottom of the nightly builds downloads page (https://builds.magiclantern.fm/index.html)) and the Porting a Canon firmware update tutorial (http://www.magiclantern.fm/forum/index.php?topic=19417.0). It really isn't all that hard and with the 6D running on QEMU much of it can be test without even loading it on the camera. Well, you do have to use the camera to get the initial firmware dump. I learned quite a bit about how ML works by doing firmware updates. Of course there is always a lot more to learn.
Firmware update could be interesting, but I'd rather spend my time on adding audio recording option to the lossless recording.
I know some started out making MLV_lite recording audio.
I'm not sure what my approach would be, adding sound recording to MLV_lite or adding lossless recording to MLV_rec module.
The info and the code is all there, MLV_snd, MLV_lite and MLV_rec module.
Probably takes a lot of time to read the code, understand the code and combine the code :P
I'm also not sure if firmware updating magic lantern from 1.1.6 to 1.1.8 is worth the time for the 6d.
1.1.7 Seems to fix lens corrections to jpg's made in camera for one lens, EF 70-300mm f/4-5.6 IS II USM
1.1.8 Seems to fix auto exposure in silent live view modus for these tilt and shift lenses: TS-E 50mm f/2.8L MACRO, TS-E 90mm f/2.8L MACRO and TS-E 135mm f/4L MACRO.
ok, so.. if I need a full hd resolution and 1824 x 1216 works maybe best I can do is upscaling then crop.
but how can it work with 1824 x 1024 (16:9) with 3x3 binning if sensor is 5472 × 3648?
would to understand..
however:
before process images I need to run exiftool on all dngs to re-balance black levels (no hardcode in build here, right?)
for me that I don't need audio I would to help to make a strong build with all res working and black levels ok out of the box.
update firmware doesn't seem top priority to me.
thank you for your work and time.
Quote from: Levas on December 04, 2017, 10:21:05 AM
I'm also not sure if firmware updating magic lantern from 1.1.6 to 1.1.8 is worth the time for the 6d.
Only for those who bought a 6D and can't get the right firmware because it isn't on Canon's website and the repository we've come to rely on has gone offline -- like now (http://pel.hu/).
@8rnity - to shoot video using the full size of the sensor these cameras do a 3x3 pixel binning/skipping trick. So:
5472 / 3 = 1824
3648 / 3 = 1216
For 16:9 it just crops top and bottom.
You shouldn't need to re-balance the blacks unless you're playing around with the lossless compression stuff. It should be resolved eventually but for now it is a work in progress.
Quote from: dfort on December 04, 2017, 10:27:46 PM5472 / 3 = 1824
3648 / 3 = 1216
For 16:9 it just crops top and bottom.
You shouldn't need to re-balance the blacks unless you're playing around with the lossless compression stuff. It should be resolved eventually but for now it is a work in progress.
yes, so for x1024 there's a crop that I can do with software then.
I need lossless as 6D hasn't choice to rec a raw 1824 x 1216 without going out of buffer so I hope with lossless I have enough speed to rec at least 20 secs of raw video if not continuos at 1824 x 1216.
am I wrong?
You are right, these cameras with UHS-I SD cards need all the help they can get. Reduced bit rate and lossless compression help a lot. It would be great if we could get this working properly on the 6D but for now it looks at least some settings can be fixed in post.
3x3 binning should improve noise and moire artifacts while skipping not. in 5dmk3 binning is employee in full hd res, what about this build? did you see moire improvement?
this evening I'll find time to install and report some trial
Quote from: dfort on December 04, 2017, 10:27:46 PM
Only for those who bought a 6D and can't get the right firmware because it isn't on Canon's website and the repository we've come to rely on has gone offline -- like now (http://pel.hu/).
Probably a good idea if a moderator can put up a link to the 1.1.6 firmware file on my google drive in the first post on the first page of this topic ?
Or put a link to the firmware on the downloads page ?
https://drive.google.com/drive/folders/1_WpYbRMOm_XrjWJxnns1FMiEN0tzZBWV (https://drive.google.com/drive/folders/1_WpYbRMOm_XrjWJxnns1FMiEN0tzZBWV)
Quote from: 8rnity on December 05, 2017, 09:08:55 AM
3x3 binning should improve noise and moire artifacts while skipping not.
I've been told by a reliable source that most cameras (with the notable exception of the 5D3) do horizontal binning and vertical skipping. No build so far will improve on the aliasing and moiré but it can be smoothed out in post and of course there are VAF filters (http://www.mosaicengineering.com/products/vaf/6d/main.html)
Hey everyone,
I'm a bit confused, I downloaded the latest nightly build for my 6D and everything is running nice and smooth. But I still cannot find the settings for audio control. Its something I really would like to use in order to manually change the audio level, disable AGC etc. but it doesn't appear in the ML Settings. Any thoughts on this? With every other camera so far I was able to access the audio settings.
Would be very glad If someone could explain this.
ok... mmm... non ok
tried lossless build and wasn't able to produce a single valid .mlv file
just tried 1824 x 1216 and doesn't work.
where am I wrong?
"Doesn't work" does not make it a proper issue report. Try to explain what's happening (or not).
exactly this:
https://www.dropbox.com/s/9xkv85qjfttc0dk/dng_lossless.JPG?dl=0
Again: Settings used?
Trý to understand we are not psychic and have only the information you are giving us.
Possible bug with new DryOS task hooks (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff), reported on the 10/12-bit experimental builds (http://www.magiclantern.fm/forum/index.php?topic=5601.msg194754#msg194754) (which already include this backend); reported twice (http://www.magiclantern.fm/forum/index.php?topic=5601.msg191914#msg191914) (edit: 3 times (http://www.magiclantern.fm/forum/index.php?topic=15088.msg190890#msg190890)).
Can you confirm?
edit: confirmed in QEMU - the issue is from new DryOS task hooks, not from 10/12-bit developments.
Test feedback on this build was given around here (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191997#msg191997), but given this bug, I doubt it was actually tested beyond "camera starts and the screenshot feature works" (because that bug will bite you as soon as you will want to record a video). Just in case you might be wondering why the progress is so slow.
Quote from: a1ex on December 17, 2017, 10:25:12 PM
Test feedback on this build was given around here (http://www.magiclantern.fm/forum/index.php?topic=15088.msg191997#msg191997), but given this bug, I doubt it was actually tested beyond "camera starts and the screenshot feature works" (because that bug will bite you as soon as you will want to record a video). Just in case you might be wondering why the progress is so slow.
No need to doubt about that, camera start and screenshot feature where the only things tested...
My fault, I translated the post below as: I need 2 screenshots, just like audionut posted, to verify.
I thought something had to be checked in the free memory dialog...but as I understand know, this build was meant to be tested all the way :o
Quote from: a1ex on October 19, 2017, 08:00:28 PM
Also, this PR (new DryOS task hooks) (https://bitbucket.org/hudson/magic-lantern/pull-requests/672/dryos-task-hooks-for-newer-cameras-6d-70d/diff) is open since 2015, and I'd really like to have it in the nightly builds (100D, 70D and EOSM2 are all waiting for it), but other than 2 screenshots from Audionut, there was zero feedback from 6D users. What are you waiting for?!
Quote from: Walter Schulz on December 15, 2017, 01:09:05 AM
Again: Settings used?
Trý to understand we are not psychic and have only the information you are giving us.
I used: crop_rec_4k.2017Nov16.6D116.zip
installed on camera, my 6D
modules: crop_rec, mlv_lite
resolution: 1824 x 1216, 14 bit lossless, 3:2, preview auto, crop mode OFF
mlv_play on camera shows video well, but when extract .dng from .mlv are corrupted.
I use pismo+mlvfs.dll to mount .mlv and open .dng or raw2cdng.1.7.9 to extract
Those settings should work, my guess is that it goes wrong with extracting the dng's.
Can you share the mlv file, or shoot a new short mlv with the same settings and share that file ?
I can check what I get with mlv_dump, which is what I use for extracting dng's.
Try batch mlv for extraction:
http://www.magiclantern.fm/forum/index.php?topic=10526.msg193871#msg193871
ok, thank you, so I used mlv_dump and that batch to extract .dng and this time at least are converted!
but
- I see a pattern on pics.. something as pixelation.. like sensor pattern
- black levels are not ok even with exiftool command
continue to try.. for the 2nd issue I have. for the first I have no idea :)
No the pattern is right, its caused by the wrong blacklevels.
Lossless works on 6d, but blacklevel offset is wrong.
You're almost there, you need exiftool to fix this.
Once you've got your dng's you need to use exiftool (google for it)
See this post for command line usage for exiftool to fix your dng's
http://www.magiclantern.fm/forum/index.php?topic=15088.msg193266#msg193266 (http://www.magiclantern.fm/forum/index.php?topic=15088.msg193266#msg193266)
It should be possible to use batch mlv to write the black level and then process the mlv file directly.
yes, already tried exiftools and don't seemed to be alright but now I'll try again.
however, thank you. I'm not able to buy a 5D3 for this and all help is welcome.
I saw that losslell vs uncompressed is a big gap, permits to have all time I need to make short videos.
thank you again.
hi to all,
this is jpg 150% of NO lossless:
https://www.dropbox.com/s/wkxwvqfuohyjq6m/no_pattern_no_lossless.JPG?dl=0
this is jpg 150% of after 1st exiftools command: exiftool -IFD0:BlackLevelRepeatDim="2 2" 6D_14bit_lossless.dng
https://www.dropbox.com/s/x8paly8yjupi3t7/pattern_after_1st_exiftools_lossless.JPG?dl=0
this is jpg 150% of after 2st exiftools command: exiftool -IFD0:BlackLevel="1919 1791 1535 1024" 6D_14bit_lossless.dng
https://www.dropbox.com/s/qqosm4d1tw786l9/pattern_after_2st_exiftools_lossless.JPG?dl=0
and these are original dng:
https://www.dropbox.com/s/v0wiyr5m6ttb5dq/6D_14bit.dng?dl=0
https://www.dropbox.com/s/qi7y1yhpocg10ox/6D_14bit_lossless.dng?dl=0
https://www.dropbox.com/s/b9d3108ccsu6kzh/6D_14bit_lossless_exiftool%20-IFD0BlackLevelRepeatDim%3D2%202.dng?dl=0
https://www.dropbox.com/s/zzx0hpbeszbxkmz/6D_14bit_lossless_IFD0BlackLevelRepeatDim%3D2%202_exiftool%20-IFD0BlackLevel%3D1919%201791%201535%201024.dng?dl=0
mmm.. :-\ there's something wrong ;D
however! in last jpg I can see some strange border.. few lines in lowest and dx part of full image are ok.
can't understand..
Can you extract the DNGs with vanilla mlv_dump and retry the same command?
Reason:
exiftool -BlackLevelRepeatDim="2 2" -BlackLevel="1920 1792 1536 1024" 6D_14bit_lossless.dng -v
======== 6D_14bit_lossless.dng
Rewriting 6D_14bit_lossless.dng...
Editing tags in: ExifIFD IFD0 MakerNotes SubIFD TIFF
FileType = DNG
FileTypeExtension = DNG
MIMEType = image/x-adobe-dng
Rewriting IFD0
Rewriting ExifIFD
Copying 1 image data blocks
Nothing changed in 6D_14bit_lossless.dng
0 image files updated
1 image files unchanged
dng_validate.exe 6D_14bit_lossless.dng
Validating "6D_14bit_lossless.dng"...
*** Warning: The ExposureTime is <= 0 ***
*** Error: DNGBackwardVersion (or DNGVersion) is too high ***
# with the file from Levas:
dng_validate.exe Silent-lossless.DNG
Validating "Silent-lossless.DNG"...
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***
Raw image read time: 0.126 sec
Linearization time: 0.045 sec
Interpolate time: 0.125 sec
Validation complete
Also, depending on the raw processing software you use, you may have to swap the middle black levels, i.e. "1920 1536 1792 1024". At least RawTherapee requires the swapped order, but I believe this is a bug that should be documented properly and reported to them (sure, it's a corner case, who else uses DNGs with per-channel black levels?!). Darktable, dcraw and dng_validate will accept the first version (1920 1792 1536 1024).
Quote from: a1ex on December 20, 2017, 12:29:42 PM
Also, depending on the raw processing software you use, you may have to swap the middle black levels, i.e. "1920 1536 1792 1024". At least RawTherapee requires the swapped order, but I believe this is a bug that should be documented properly and reported to them (sure, it's a corner case, who else uses DNGs with per-channel black levels?!). Darktable, dcraw and dng_validate will accept the first version (1920 1792 1536 1024).
When you have your dng's right, they still don't look good in RawTherapee, most certainly a bug.
Other software that I've used are displaying the dng's right (Lightroom, Preview in MacOs Sierra)
I'm using RawTherapee but as I want my dng's to be futureproof, I'm using the normal black level fix and in Rawtherapee set the raw black points too: Green 1 to value -256 and green 2 to value 256
Planning on reporting the bug to RawTherapee developers, cause the green channels seem to be swapped, not sure if Canon has different CFA for both green channels, but I can imagine that it's best too have those channels right in RawTherapee.
Quote from: a1ex on December 20, 2017, 12:29:42 PM
Can you extract the DNGs with vanilla mlv_dump and retry the same command?
hi, thank you for answer, it was already "vanilla mlv_dump" as "mlv dump batch" latest version is based on bouncyball's "mlv_dump on steroids".
however extracted again.
with your command:
exiftool -BlackLevelRepeatDim="2 2" -BlackLevel="1920 1792 1536 1024" 6D_14bit_lossless.dng -v
[..cut..]
Nothing changed in 6D_14bit_lossless.dng
0 image files updated
1 image files unchanged
but with -IFD0:
C:\Users\marco\Desktop\mlv>exiftool -IFD0:BlackLevelRepeatDim="2 2" -IFD0:BlackLevel="1920 1792 1536 1024" 6D_14bit_lossless.dng -v
======== 6D_14bit_lossless.dng
Rewriting 6D_14bit_lossless.dng...
Editing tags in: IFD0 TIFF
FileType = DNG
FileTypeExtension = DNG
MIMEType = image/x-adobe-dng
Rewriting IFD0
Rewriting ExifIFD
Copying 1 image data blocks
1 image files updated
QuoteAlso, depending on the raw processing software you use [..cut..]
yes, I read this so I used CR only.
fog here in my mind.. ??? should obtain same file as levas but I'm not able..
Quote from: 8rnity on December 20, 2017, 06:18:51 PM
hi, thank you for answer, it was already "vanilla mlv_dump"
It was bouncyball's "mlv_dump on steroids", not the vanilla one.
Anyway - I have a feeling the difference might not be just a black level offset in this case. In particular, there is a lot of posterization on green and blue channel; besides, the blue channel doesn't look right at all. It might be a compression or a decompression issue - do the files look right in mlv_play? (if yes, it's the latter; if it shows similar defects, it's likely the former).
Let's modify silent.mo to save both uncompressed and lossless versions of the same input image. Can you try this patch?
diff -r 01fc07461da5 modules/silent/silent.c
--- a/modules/silent/silent.c
+++ b/modules/silent/silent.c
@@ -558,7 +558,10 @@
char* filename = silent_pic_get_name();
int ok = save_dng(filename, raw_info);
if (!ok) bmp_printf( FONT_MED, 0, 83, "DNG save error (card full?)");
- return ok;
+ /* undo the damage done by save_dng */
+ extern void reverse_bytes_order(void *, int);
+ reverse_bytes_order(raw_info->buffer, raw_info->frame_size);
+ /* fall-through to save a lossless version of the same input image */
}
case SILENT_PIC_FILE_FORMAT_LOSSLESS_DNG:
This should save two DNGs from the same buffer - one uncompressed and the other one lossless.
Also, please try these patches (http://www.magiclantern.fm/forum/index.php?topic=15088.msg193286#msg193286) and document their effect - maybe one of them affects this somehow.
Quote from: a1ex
It was bouncyball's "mlv_dump on steroids", not the vanilla one.
you right, check this later
Quotedo the files look right in mlv_play? (if yes, it's the latter; if it shows similar defects, it's likely the former).
no, it doesn't. in camera looks exactly as on pc (bad)
QuoteLet's modify silent.mo to save both uncompressed and lossless versions of the same input image. Can you try this patch?
uh oh.. I'm going to study
meanwhile I uploaded .mlv on dropbox
https://www.dropbox.com/s/pm2rpmu5m3s6s5e/M18-2132.MLV?dl=0
mlv_dump M18-2132.MLV --dng --no-stripes --no-fixcp
exiftool -BlackLevelRepeatDim="2 2" -BlackLevel="1920 1792 1536 1024" -overwrite_original *.dng
dcraw -W *.dng
dcraw -a -W -b 4 *.dng
gives that fine maze pattern; however:
dng_validate.exe -tif out M18-2132_000000.dng
gives clean image to my eye, and so does darktable on the same DNG.
After swapping the black levels on the two greens, RawTherapee also gives clean image.
This one:
octave:1> a = read_raw('M18-2132_000000.dng');
octave:2> a(1:2:end,1:2:end) += 128; # red
octave:3> a(1:2:end,2:2:end) += 256; # green1
octave:4> a(2:2:end,1:2:end) += 512; # green2
octave:5> a(2:2:end,2:2:end) += 1024; # blue
octave:6> imwrite(uint16(a), 'out.pgm');
octave:7> system('pgm2dng out.pgm');
octave:8> system('dcraw -a -W -b 4 out.DNG');
gives clean image in dcraw (no black level tweaking required, as pgm2dng hardcodes 2048), but also with different white balance. To run it, you need read_raw (http://www.magiclantern.fm/forum/index.php?topic=7139.msg193890#msg193890) and pgm2dng (http://www.magiclantern.fm/forum/index.php?topic=7139.msg194204#msg194204).
So far, the above suggests a bug in dcraw when handling files with different per-channel black levels, but at least darktable and RawTherapee can give a clean image, and I'd expect Adobe programs to do the same (they wrote the DNG spec and dng_validate.exe, after all).
For the end user, given that per-channel black levels do not work as expected in all raw processing programs, I'd say the easiest workaround would be to do what the above octave script does, in mlv_dump (and other software that wants to handle lossless MLVs from 6D). Extremely easy coding task, so I'm going to leave it for novice programmers who may be looking for some low-hanging fruit to get started.
found.
combination of both options --no-stripes --no-fixcp produces valid dng without pattern.
use just one or none of these two and have a pattern on the image.
what I wrote above is not true. it's mlv_dump version. both "mlv_dump on steroids" and the one used in "simple right clic menu mlv dump batch" produce the issue. used the one in download section and works perfect after exiftool!
In every proggie I tested there is a pattern in the output (--no-stripes --no-fixcp does not help for mlv_dump), The only correct way to get valid DNG with working good/old plain black level is the method a1ex showed above (octave example).
regards
bb
@8rnity
batch_mlv is using mlv_dump_on_steroids only it's called mlv_dump. There is some info about versions in the thread and probably also in the gpl license files.
Quote from: bouncyball on December 21, 2017, 06:11:48 PM
In every proggie I tested there is a pattern in the output (--no-stripes --no-fixcp does not help for mlv_dump), The only correct way to get valid DNG with working good/old plain black level is the method a1ex showed above (octave example).
regards
bb
yes, I edited my post. original mlv_dump version and exiftools give dng without pattern. white balance is not the same as not-lossless
Looks like a bug.
Here is the log from mlv_dump (6D MLV example from @8rnity):
Block: EXPO
Offset: 0x0000015c
Number: 4
Size: 40
Time: 1.751000 ms
ISO Mode: 0
ISO: 800
ISO Analog: 96
ISO DGain: 0/1024 EV
Shutter: 0 microseconds (1/inf)
Shutter is not baked to MLV EXPO header. Hence:
$ ./dng_validate 6D_INVALID_000159.dng
Validating "6D_INVALID_000159.dng"...
*** Warning: The ExposureTime is <= 0 ***
*** Warning: Too little padding on left edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on top edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on right edge of CFA image (possible interpolation artifacts) ***
*** Warning: Too little padding on bottom edge of CFA image (possible interpolation artifacts) ***
Raw image read time: 0.026 sec
Linearization time: 0.006 sec
Interpolate time: 0.081 sec
Validation complete
Ignore warnings about 'too little padding' they are same for all ML/MLtools produced DNGs.
There's been lots of changes on the crop_rec_4k and crop_rec_4k_mlv_lite_snd branches.
The 6D pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff) hasn't been merged yet because there are some issues with lossless compression that still need to be worked out. If you want a preview of coming attractions I put up a test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Who knows, maybe we got lucky?
Did some quick tests with your build Dfort.
And looks like sound recording works with mlv_lite.
I'v got working wav files with my 14bit lossless mlv files :D
I assume crop mode didn't change for 6d meanwhile ?
Because I tried the crop mode, the crop mode only has the 3x3 720p option.
Tried it by setting the cam to 720p50fps, activated crop mode, but it still records squeezed frames, so it's still doing 3x5 binning.
The crop menu shows a menu within the 3x3 720p option, with:
Target YRES
Delta ADTG 0
etc...
All options are set to 0 by default
Tried setting the YRES to 960, but still got squeezed frames.
Screenshots? Sample MLVs? Is 10bit/12bit lossless working?
Only the 3x3 crop_rec option is coded but I don't have a 6D to check it out. If you do mlv_dump -v [your.MLV] you should be able to check out if it is 3x5 or 3x3. That crop_rec option might display a stretched LiveView but the DNG frames should look normal.
So took a while, but here's a 14 bit lossless MLV example with audio from the 6d:
https://drive.google.com/open?id=1idNTNn9lciEOd-CfUPrYaPXWOMOjlETp
(https://drive.google.com/open?id=1idNTNn9lciEOd-CfUPrYaPXWOMOjlETp)
Ofcourse, there are still the usual quirks the 6d has with lossless, so you need to fix the black levels of all 4 channels with exiftool as discussed earlier in this topic.
Also, the full wide 1824 pixels recording option still gives frames with the bottom half corrupted(as known and discussed before).
So this example is recorded in 1808 pixels wide resolution.
I'v also put the wav file and a dng frame with the right black levels in the same folder.
Other bitrates work, for audio.
But after fixing the black levels, there is still some minor pattern visible, probably due rounding errors by extracting lower bit depth files to standard 14 bit(as MLV_dump does) and then fixing black levels for 14 bitdepth values.
But this was for now always the case with lossless and lower than 14 bit lossless files on the 6d
Tried some more with the crop_rec, but I can't get unsqueezed footage, all settings I tried gave squeezed image, 3x5 pixel binning.
So the 6d still has some weird quirks with lossless
-Needs black level fix, which doesn't seem to work perfect with lower than 14 bit (probably) due small rounding errors.
-Widest resolution of 1824 pixels gives frames with bottom half corrupted.
But besides the quirks, it works for me, 14 bit lossless with audio :D Thanks!
Quote from: Levas on February 12, 2018, 10:39:08 AM
Tried some more with the crop_rec, but I can't get unsqueezed footage, all settings I tried gave squeezed image, 3x5 pixel binning.
Let's try changing the MEM_CMOS_WRITE and MEM_ADTG_WRITE addresses to the same as the 5D3. To be honest I'm not sure how to find those addresses. The same addresses worked on the EOSM/100D/650D/700D so I assumed it would work on the 6D. Not sure why the 5D3 is different or why the MEM_CMOS_WRITE and MEM_ADTG_WRITE share the same address on that camera.
I put up a crop_rec_4k test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). That build also has a working adtg_gui module so you should be able try this experiment:
Quote from: rbrune on October 26, 2016, 09:50:04 PM
Using adtg_gui I overrode the ADTG 800C register that controls the vertical line skipping to switch from 3x5 (0x4) to 3x3 (0x2) line skipping mode.
...
To get the camera to accept the overridden register one has to use the INFO button to switch into Canons menu and display modes and back into magic lantern. The preview image should be stretched when it worked.
Thanks Dfort,
Tried your build, right out of the box, crop record still gives squeezed frames in the MLV file.
Unfortunately the adtg_gui module won't load, OldApi it says, something with different version than expected, v6 vs v7.
Well it was worth a shot. Been learning about adtg_gui, looks like there is more than one version. You might try the one from the modules downloads page (https://builds.magiclantern.fm/modules.html). With the camera in mv720 mode you should be able to adjust the ADTG 800C register so that it stretches the preview image vertically.
So, starting with the Canon menu set to 1280x720/60 (mv720) your LiveView should look normal:
(https://farm5.staticflickr.com/4624/26395592938_b84cb4c12a.jpg) (https://flic.kr/p/GdujaY)
Find the ADTG 800C register in adtg_gui. According to the tool tip (bottom line in green) it skips 4 lines in 720p mode:
(https://farm5.staticflickr.com/4758/40223282772_ab57b10d10.jpg) (https://flic.kr/p/24hoQBo)
Change that register so it skips 2 lines like in 1080p mode:
(https://farm5.staticflickr.com/4666/26395594168_366acc07d4.jpg) (https://flic.kr/p/Gdujxb)
The LiveView should look like this:
(https://farm5.staticflickr.com/4630/40223281862_1644dd6be1.jpg) (https://flic.kr/p/24hoQkG)
That's what we're looking for. If you look at my pull request for the 6D, in crop_rec.c we need to find the correct values. Not sure if adtg_gui is showing them. You might need a build from the iso-research branch? IDK.
Ha ha nice coaster.
Had some good beers from that small brewery :P
Will take a look at the adtg_gui module tomorrow.
Quote from: Levas on February 12, 2018, 10:39:08 AM
So the 6d still has some weird quirks with lossless
-Needs black level fix, which doesn't seem to work perfect with lower than 14 bit (probably) due small rounding errors.
-Widest resolution of 1824 pixels gives frames with bottom half corrupted.
But besides the quirks, it works for me, 14 bit lossless with audio :D Thanks!
So the first one needs to get fixed in mlv_dump and other MLV post applications:
Quote from: a1ex on December 21, 2017, 12:37:52 AM
For the end user, given that per-channel black levels do not work as expected in all raw processing programs, I'd say the easiest workaround would be to do what the above octave script does, in mlv_dump (and other software that wants to handle lossless MLVs from 6D). Extremely easy coding task, so I'm going to leave it for novice programmers who may be looking for some low-hanging fruit to get started.
The second one might need some adjustments in the skip offsets and/or the timer values. We did that recently for the EOSM/100D/650D/700D in this pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/897/raw-buffer-adjustments-for-eosm-100d-650d/diff). We could start by gathering some simple silent DNG frames with the camera set in the various video modes.
Downloaded the adtg_gui module from the module download page and played with it in combination with your(Dfort) 6d crop build.
When ADTG2[800c] is altered to value 2, (3x3 mode) the upper half of the live view is weird, looks like it scans more vertical lines of the sensor and overlays it on the top half of the image.
Now when I alter the value of CMOS[7] I can get normal framing.
CMOS[7] = 3c2 by default in 720p mode, When I change it to CMOS[7]=2a2 I get normal framing.
More options work for CMOS[7], which result in normal framing, but other (vertical) part of the sensor.
2a2 works, 308 and 3cb works and probably more..value 2a5 looks rather like the center.
I dived into the source code and it seems that what CMOS[7]on the 6d does what CMOS[2] CMOS[1] does on other cams ?
I couldn't get the resolution larger than 634 pixel vertical, not sure how to steer that.
Results for now are 1808 x 632 resolution in 3x3 mode and 50fps :D
You got it working, fantastic!
Now all that is needed is to figure out how to interpret your findings to the correct MEM_CMOS_WRITE and MEM_ADTG_WRITE in this bit of code:
modules/crop_rec.c
else if (is_camera("6D", "1.1.6"))
{
CMOS_WRITE = 0x2445C;
MEM_CMOS_WRITE = 0x????????;
ADTG_WRITE = 0x24108;
MEM_ADTG_WRITE = 0x????????;
is_basic = 1;
crop_presets = crop_presets_basic;
crop_rec_menu[0].choices = crop_choices_basic;
crop_rec_menu[0].max = COUNT(crop_choices_basic) - 1;
crop_rec_menu[0].help = crop_choices_help_basic;
crop_rec_menu[0].help2 = crop_choices_help2_basic;
}
These can be found by printing... MEM(CMOS_WRITE) and MEM(ADTG_WRITE). They are just some additional validation (e.g. if there's a typo in one of these addresses, or if somebody tries that code on a different firmware version). They are similar to the "hack error" message from mlv_lite - they simply point out that some stub might be incorrect.
Eh, still don't understand how to get those addresses ???
Do we need some customised build that can print these addresses on screen ?
Yes. I just recycled what I did to get the SRM_BUFFER_SIZE printed on the screen:
QEMU to the rescue!
(https://farm5.staticflickr.com/4626/39389473935_33cf165e93.jpg) (https://flic.kr/p/231HmhX)
So maybe this will work?
else if (is_camera("6D", "1.1.6"))
{
CMOS_WRITE = 0x2445C;
MEM_CMOS_WRITE = 0xE92D47F0;
ADTG_WRITE = 0x24108;
MEM_ADTG_WRITE = 0xE92D41F0;
I'll update the pull request and put up anther test build to my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Dfort, tested your newest build, but crop_rec still gives squeezed frames ???
Ok--found what might be the problem. I took some of the values from here:
modules/adtg_gui.c
else if (is_camera("6D", "1.1.6")) // from 1% (match 6D.113), JL, checked by Maqs
{
CMOS_WRITE_FUNC = 0x2445C; //"[REG] ############ Start CMOS OC_KICK"
CMOS2_WRITE_FUNC = 0x2420C; //"[REG] ############ Start CMOS"
ADTG_WRITE_FUNC = 0x24108; //"[REG] @@@@@@@@@@@@ Start ADTG[CS:%lx]"
CMOS16_WRITE_FUNC = 0x24548; //"[REG] ############ Start CMOS16 OC_KICK"
}
Other cameras just have CMOS_WRITE_FUNC but the 6D also has a CMOS2_WRITE_FUNC. I'm not sure if this will work because as you found out that you needed to adjust CMOS[7].
Let's give it another go--we might get lucky this time or at least we're getting closer to solving this.
Named this one crop_rec_4k_ CMOS_WRITE.2018Feb15.6D116 because that's what changed since the last test.
@Levas or any other 6D user - no pressure, just curious to find out if that last build finally worked with crop_rec. I think that's the last piece that is needed for the 6D to be merged into the official crop_rec_4k branch. The issues with lossless compression need to be solved with the MLV post processing apps.
Dfort, just checking the build. But I still get squeezed images.
When I activate crop mode, the screen goes black and applies the settings, but other than that, nothing changes.
Still 3x5 binning.
When I start adtg_gui, both 800C and CMOS[7] haven't changed, 800C is still on value 4 after enabling crop_rec ???
Well we know this is possible because:
Quote from: Levas on February 15, 2018, 09:27:51 AM
I couldn't get the resolution larger than 634 pixel vertical, not sure how to steer that.
Results for now are 1808 x 632 resolution in 3x3 mode and 50fps :D
You can't get more than 632 vertical resolution because this is the 720p raw buffer which is designed to skip 4 lines at a 16x9 aspect ratio. Maximum theoretical vertical resolution skipping 2 lines (3x3) is the sensor max resolution, 3,648, divided by 5 or about 729 but the actual maximum is significantly less.
In any case, looks like we are almost there.
Makes sense, probably the vertical resolution, divided by 5, also needs to be corrected from 3:2 to 16:9 ratio, then you get about 614 pixels
But the 5d3 does 1920 x 960 in 50fps mode ? https://www.magiclantern.fm/forum/index.php?topic=19300.msg182052#msg182052 (https://www.magiclantern.fm/forum/index.php?topic=19300.msg182052#msg182052)
Or is this 1920 x 960 x 50fps not in 720p mode but in 1080p mode ?
Or has the 5d3 a larger 720p raw buffer ?
Finally I solved the mystery how to 'repair' the 12 to 8 bit lossless MLV's from the 6d.
MLV files with lower bit depth than 14 have wrong white level.
Got a 10 bit lossless file which shows white level of 2932 in the metadata and a 8 bit lossless file which shows a white level of 2269 ::)
Used exiftool to set the white level to 16200 in the resulting extracted 14 bit files, and now everything is fine 8)
Whoohoo 14 - 8 bit lossless with audio on the 6d :D 8)
When using lossless compression I extract the MLV files with MLV_dump on steroids and fix the DNG's with the following command
exiftool -IFD0:BlackLevelRepeatDim="2 2" -IFD0:BlackLevel="1920 1792 1536 1024" -IFD0:WhiteLevel="16200" -overwrite_original *.dng
Quote from: Levas on February 16, 2018, 09:23:08 PM
Used exiftool to set the white level to 16200 in the resulting extracted 14 bit files, and now everything is fine 8)
... is the reduced bit depth lossless recording actually working on 6D? (as in, do you actually get lower file sizes?)
This works by darkening the input image before compression (https://www.magiclantern.fm/forum/index.php?topic=10111.msg191218#msg191218), while still using a 14-bit container; if you had to raise the white level to 16200, that suggests the bit depth reduction probably did not work.
The uncompressed 10/12-bit recording is a lot different: there, the bit depth reduction happens before the raw image arrives into main memory. For lossless, the bit depth reduction is only at logical level (the container is still 14-bit, just the entropy of the data prior to compression is brought to 8/10/12/whatever-bit levels).
edit: please read the post and the links before replying.
Reduced bit depth lossless works on 6d.
MLV_dump on steroids makes/exports only 14 bit DNG's...
So after exporting the DNG's, it always is in a 14 bit DNG file.
Got about 550 frames with 8 bit lossless in 2400x960x25fps resolution.
with 40Mb/s writing speed and about 250Mb buffer memory , only possible if 8 bit lossless is really 8 bit lossless.
Testing it again, 8 bit lossless, 2400 x 960 x 25 fps at iso 6400, with not much movement/panning I get 693 frames
2400 x 960 x 25 fps at iso 6400 in 14 bit lossless, same scene, not much movement/panning gives 200 frames
Alright, so with your second test, the compression ratio (compressed/uncompressed) was about 50% at 8-bit lossless, and about 72% for 14-bit, which sounds about right (https://www.magiclantern.fm/forum/index.php?topic=19300.msg183231#msg183231).
Then, what was the reason for raising the white level to 16200? May I see the two DNGs? (8-bit vs 14-bit from the above experiment)
BTW, lossless compression is done for each individual frame, so motion doesn't have much effect (other than motion blur, which might reduce the entropy a bit).
I've uploaded two original MLV files, 14 bit lossless and 8 bit lossless.
https://drive.google.com/open?id=1vgOvuL7QuCDtFFgG-peoo7gjLTJeaURr (https://drive.google.com/open?id=1vgOvuL7QuCDtFFgG-peoo7gjLTJeaURr)
When I use MLV_dump on steroids, to extract DNG files out of these MLV's, I get 14 bit DNG files out of the 8 bit file, with white level value of 2269 ???
I've also uploaded two DNG's straight out of MLV_dump on steroids, and two fixed with exiftool.
EDIT: The scene is shot under LED bulbs with 2300Kelvin temperature, so not exactly natural light :P
Alright, you must have developed the DNG with dcraw or some other tool that brightens the image (possibly at default settings), but I still don't know what was the reason for changing white level to 16200; how did the DNG look without that change?
exiftool -IFD0:BlackLevelRepeatDim="2 2" -IFD0:BlackLevel="1920 1792 1536 1024" -overwrite_original 8Lossless_frame_000000-UNFIXED.dng
The above gives correct image with dcraw -W
-W Don't automatically brighten the image
Lossless is getting there, let's see if we can also get crop_rec working. Did yet another QEMU session, this time I figured out how to get it to start up in movie mode and the Canon settings in 720p printing out both addresses on the screen.
bmp_printf(FONT_LARGE, 50, 350, "MEM_CMOS_WRITE 0x%x", MEM(CMOS_WRITE));
bmp_printf(FONT_LARGE, 50, 400, "MEM_ADTG_WRITE 0x%x", MEM(ADTG_WRITE));
(https://farm5.staticflickr.com/4719/25438964427_7e1dd04506.jpg) (https://flic.kr/p/EKXkQX)
Strange but the 5D3 also has the same address for MEM_CMOS_WRITE and MEM_ADTG_WRITE, only slightly different.
Let's give it another try. This time I also uploaded a version named print_CMOS_WRITE_ADTG_WRITE... guess what that does? Just in case the new crop_rec_4k build still doesn't work you can check the addresses on the camera. Just activate the crop_rec module and it should print just like in QEMU. Make sure you're in movie mode, 720p. It seems to make a difference.
As usual--test builds are on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Thought this could use some further discussion:
Quote from: Levas on February 16, 2018, 07:23:01 PM
Makes sense, probably the vertical resolution, divided by 5, also needs to be corrected from 3:2 to 16:9 ratio, then you get about 614 pixels
But the 5d3 does 1920 x 960 in 50fps mode ? https://www.magiclantern.fm/forum/index.php?topic=19300.msg182052#msg182052 (https://www.magiclantern.fm/forum/index.php?topic=19300.msg182052#msg182052)
Or is this 1920 x 960 x 50fps not in 720p mode but in 1080p mode ?
Or has the 5d3 a larger 720p raw buffer ?
If you look at crop_rec.c you'll see that the code for the 5D3 is further developed than just taking the mv720 buffer and changing the line skipping. I can't find the post but I'm sure that a1ex explained that CROP_PRESET_3x3_1X uses a custom buffer on the 5D3 which has more vertical resolution. Note also that the FPS is somehow related to the image size. At some point we can get the addresses for ENGIO_WRITE and MEM_ENGIO_WRITE and create custom buffers but let's get the basic 3x3 binning in 720p working first.
@Alex, I'm confused, if you fix the black level of the non fixed frame, you see normal results ?
When I look at the text file with meta data from the 8 bit lossless MLV it shows a white level of 2269.
Where the 14 bit lossless meta data text file shows a white level of 16200.
My workflow with the MLV files is, using mlv_dump on steroids to extract the dng's.
mlv_dump_on_steroids.osx --no-fixcp --no-stripes --dng
As already known, I'm a big fan of RawTherapee, when I load the non fixed image in RawTherapee and fix the offset of the black levels, I get this:
Exposure settings and stuff is set to zero:
(https://farm5.staticflickr.com/4669/26441951938_ef8cef1c4f_b.jpg)
Now when I fix black level and set white level to 16200 with exiftool, I get this in RawTherapee:
Exposure settings, needed to push 6 stops exposure to get this result (and ofcourse compensate black levels for the green channels which are swapped).
(https://farm5.staticflickr.com/4607/26441952498_e90f274d8c_b.jpg)
Quote from: Levas on February 17, 2018, 11:13:19 AM
As already known, I'm a big fan of RawTherapee, when I load the non fixed image in RawTherapee and fix the offset of the black levels, I get this:
...
I already know; that's why the first thing I've tried with your DNGs was opening them in RawTherapee. However, I've got a totally (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/rt-fixed-reset.png) bogus (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/rt-fixed-auto-levels.png) image (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/rt-fixed-lmmse.png) with your FIXED.dng; moreover, your exiftool command contains the black levels in the dcraw/darktable/Adobe order, not in the RawTherapee one (https://www.magiclantern.fm/forum/index.php?topic=15088.msg194919#msg194919). Given the above, I had all the reasons to believe you have used a different program (not RawTherapee) for this particular experiment. Edit: also checked with RT 5.3 stable, no significant changes.
After running my command (white level unchanged, still at 2269) modified to match RawTherapee order, I get normal image (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/rt-unfixed-exiftool-changed-black-levels.png) in RawTherapee:
exiftool -IFD0:BlackLevelRepeatDim="2 2" -IFD0:BlackLevel="1920 1536 1792 1024" -overwrite_original 8Lossless_frame_000000-UNFIXED.dng
MD5 checksums (so you can make sure I've used the right files):
8d285dbe3ef4d7a94d04d86994e7520a 8Lossless_frame_000000-FIXED.dng ; as downloaded
4efb9d69ba83812b09e5447b97a4119b 8Lossless_frame_000000-UNFIXED.dng ; after exiftool with "1920 1536 1792 1024"
6a7ae89709386b42781beb2d8a2b220a 8Lossless_frame_000000-UNFIXED-orig.dng ; copied after downloading
@Dfort, I don't have much time today to test, so will look further in it tomorrow.
But what I quickly see is that your 'normal' latest crop_rec build does more then the previous builds.
It looks like it has the pixelbinning part right, but the CMOS[7] is not adjusted.
I see a preview similar as if I change only the ADTG800C register to value 2.
The frame is a little messed up on the top half, which can be fixed with CMOS[7] in adtg_gui.
Also checked the 'print' build, it shows addresses at startup, but if live view is on, it's gone...
I get the same addresses in 720p, photo mode ( 0xe92d41f0 ) as you did in QEMU.
@Alex, sorry for the weird workflow :P
I can explain.
I keep my files and want them to be future proof, my guess is that DNG's are more future proof then MLV files (not sure of course ;) )
As I keep DNG's, I fix the black levels, but as we know, Raw Therapee has the green levels in the wrong order, so for future proofing, I choose to fix the black levels according to the DNG format.
When editing in RawTherapee I compensate the green levels (Unlink green channels, compensate -256 for the first green channel and +256 for the second green channel)
Weird, but all logical to me.
Also tried to do what you did, took the unfixed 8 bit lossless dng, fixed the black levels with exiftool (fixed for Rawtherapee use)
And loaded the file in Rawtherapee 5.3.
Looks good at first sight, but when I zoom to 1:1 100%, I see a pattern all over the image.
How does the file, without white level fix, look at 100% on your screen ?
Yes, it has a fine maze pattern.
Same pattern if I use "1920 1792 1536 1024" and -/+ 256. The pattern disappears with white level set to 16200 and brightening with Auto Levels. Mystery solved.
This points to a possible roundoff error in RawTherapee processing, and I believe the issue should be reported to them (as I'd expect identical results in these two cases).
The same pattern appears in darktable, but is not present (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/dngv-unfixed-exiftool-changed-black-levels.tif) with dng_validate 1.4, and neither (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/6D/8Lossless_frame_000000-UNFIXED-1920-1792-1536-1024.png) with dcraw (so the DNG is correct, but RawTherapee and darktable do not interpret it properly). This should be mentioned in the bug reports, should you decide to do them. I can help with checking the reports, BTW.
(interesting that I'm still unable to see the maze pattern in this sample (https://www.magiclantern.fm/forum/index.php?topic=15088.msg194950#msg194950) with RT/DT, but maybe it's just my lack of pixel peeping skills)
The above does not mean setting white level to 16200 is the right thing to do (in particular, it will break highlight recovery on overexposed images). It's just a workaround that happens to work for you, nothing more. Reporting the issue to RT and DT is the preferred option, IMO.
I'm come from China and say sorry for my poor English ;)
I have tried dump the 14bit-lossless RAW video with mlv_dump and repair DNGs with exiftool.For every single dng i got a nice image with wrong white balance(alaways on 3200K).
(https://thumb.ibb.co/nLN6t7/QQ_20180217193937.png) (https://ibb.co/nLN6t7)
that is ok,good job.However,when I put them into Premiere and DaVinci,the color is borken.it looks like dng without exiftool but have a little higher blacklevel.
(https://thumb.ibb.co/dd4fLn/QQ_20180217194607.png) (https://ibb.co/dd4fLn)
I can always get right image with the help of software with ACR like PS,LR and AE,but,you know,it's a trouble.
By the way.I have write a windows form app for dump DNGs.Of course,have the problem I said above.
https://pan.baidu.com/s/1smB7YLf (https://pan.baidu.com/s/1smB7YLf)
(I'm not sure if you can open the netdisk link without a VPN :'()
Unfortunately, not all DNG converters interpret per-channel black levels; for best compatibility, it would be to alter the raw data itself (https://www.magiclantern.fm/forum/index.php?topic=15088.msg194950;topicseen#msg194950) (rather than declaring the offsets in the DNG metadata).
Are you able to run the octave script from the linked post, and/or implement the same correction in mlv_dump? (if you were able to write a GUI wrapper for mlv_dump, the answer would be most likely "yes").
Quote from: Levas on February 17, 2018, 11:43:39 AM
But what I quickly see is that your 'normal' latest crop_rec build does more then the previous builds.
It looks like it has the pixelbinning part right, but the CMOS[7] is not adjusted.
I see a preview similar as if I change only the ADTG800C register to value 2.
The frame is a little messed up on the top half, which can be fixed with CMOS[7] in adtg_gui.
Hum, the tool tip for CMOS[7] is, "Looks like the cmos is dieing (g3gg0)." Wonder what that means?
Looking at your lossless MLV's I see that your camera is probably setup for PAL. Maybe that has something to do with it? I also noticed that the CROP_PRESET_3x3_1X might be using ENGIO_WRITE and MEM_ENGIO_WRITE which are not defined other than on the 5D3. Using the same technique that seemed to have worked with MEM_CMOS_WRITE and MEM_ADTG_WRITE I looked up MEM_ENGIO_WRITE and it came up the same as the 5D3. I also found ENGIO_WRITE in the disassembly so this should work:
else if (is_camera("6D", "1.1.6"))
{
CMOS_WRITE = 0x2420C;
MEM_CMOS_WRITE = 0xE92D41F0;
ADTG_WRITE = 0x24108;
MEM_ADTG_WRITE = 0xE92D41F0;
ENGIO_WRITE = 0xFF2AE134;
MEM_ENGIO_WRITE = 0xE51FC15C;
Uploaded a new test build (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
- Does the frame look different in NTSC?
- Exactly are you doing with CMOS[7] to fix the frame?
- Have you tried recording anything yet or are you just looking at the LV preview?
Quote from: a1ex on February 17, 2018, 12:16:15 PM
does not mean setting white level to 16200 is the right thing to do (in particular, it will break highlight recovery on overexposed images). It's just a workaround that happens to work for you, nothing more. Reporting the issue to RT and DT is the preferred option, IMO.
Thanks for clearing that up, there goes my future proof workflow :P
So for reasonable future proofing, it's best to fix black levels and leave white level unaltered.
And as I see in a later post, for best compatibility/future proofing it's best to alter the raw data.
EDIT: Opened the same files(only black level fix, white level unaltered) in Lightroom 5, Lightroom shows them just fine, exposure is good and there's no fine maze pattern.
Preview in MacOS shows the files without the correct exposure, really dark preview, so Preview in MacOS, doesn't read/use the white level.
@Dfort, You're right, my camera is set to PAL.
Always tried recording, but also enable the 'framing' option in MLV_Lite and the 'framing' shows exactly the same thing as recording.
Just tried your latest build and it still looks the same as when I alter the lineskipping value to '2' in adtg_gui.
When I change CMOS[7] in adtg_gui I can get a normal live view image and recording.
In adtg_gui I set CMOS[7] to value '2a5'.
I remember seeing a overview with CMOS and adtg settings and what they do in different camera's, can't find them anymore, do you know what I mean ?
Here is how PAL looks(When I move the camera a little, the upper half of the image becomes green tinted.
As you can see, my dock appears at the upper half of the picture, while it should be in the bottom of the screen.
(https://farm5.staticflickr.com/4628/39623651964_350b2bfdf9_b.jpg)
NTSC looks the same, But alters, 1 frames just as PAL and then 2 frames with purple tinted upper half, repeats this pattern:
(https://farm5.staticflickr.com/4713/26463109718_cb260ec64c_b.jpg)
This CMOS[7] appears to have the same effect as CMOS[1] on 5D3; on 700D/100D/M it's also CMOS[7]. This register is used to select where the exposure starts and where it ends. The CMOS registers accept 12-bit values; some of them (including this one) may divided in two halves; others may be bit fields (so it makes sense trying every single bit individually) etc. On 5D3, the lower half (6 bits) adjusts where the exposure starts (adjust it to center the image) and the upper half (also 6 bits) adjusts where the exposure ends (if too high, you get a ghost image like in these screenshots).
These adjustments are available in the crop_rec submenu as well: cmos1_lo and cmos1_hi (you can change that to cmos7, cmos_new[7] etc). The value 2a5 can be written as PACK12(37,10), which doesn't make much sense to me. You could try changing these 2 values individually to see if they have any logic, or you could try dividing this register in some other way if it makes more sense. If you have no idea where to start, you could flip each bit starting from 0x2A5 (12 bits total: 2A5 ^ 1 = 2A4; 2A5 ^ 2 = 2A7; 2A5 ^ 4 = 2A1; ... ; 2A5 ^ 800 = AA5) and write down (or capture a screenshot of) the outcome for each of these 12 values.
Please note adtg_gui and crop_rec are unable to run at the same time; the first one will be able to install the hooks, and the second one will simply not work if you try to enable both. Therefore, the preferred way to experiment is to use the crop_rec submenu (and adapt it for your needs).
The sweet spot for CMOS[7] can be found by decreasing the end limit (after finding out what bits are used to encode it) until you get a white area at the bottom (https://www.magiclantern.fm/forum/index.php?topic=16608.msg176757#msg176757) (or maybe black or otherwise without valid image data), then increase it by one notch from there.
The cmos_new[7] is being adjusted for cameras that have only the CROP_PRESET_3x3_1X ("is_basic") crop_rec option here:
if (is_basic)
{
switch (crop_preset)
{
case CROP_PRESET_3x3_1X:
/* start/stop scanning line, very large increments */
cmos_new[7] = PACK12(6,29);
break;
}
}
While the 5D3 skips this. Maybe this is the problem? Either this needs to be skipped for the 6D or maybe we need to make a special case for the 6D to adjust CMOS[7] to 0x2A5 (or whatever we find works best) like this?
case CROP_PRESET_3x3_1X:
/* start/stop scanning line, very large increments */
cmos_new[7] = (is_6D) ? PACK12(37,10) : PACK12(6,29);
I also noticed that the other "is_basic" cameras have the CROP_MODE_HACK feature but the 6D does not so checking for the 600D hack crop mode doesn't apply. That means we should probably make a special case for the 6D here too:
if (is_basic && !is_6D)
{
if (reg == 7)
{
found = 1;
/* prevent running in 600D hack crop mode */
if (value != 0x800)
{
ok = 0;
}
}
}
Uploaded a couple of more test builds (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). One adjusting CMOS[7] to 0x2A5 and another build that doesn't make any adjustment to CMOS[7].
@alex - off topic - "make clean" wasn't cleaning out adtg_gui so my test builds were including it even though it should have been skipped. In addition, I'm not seeing the uncommitted changes in autoexec.bin which is really helpful. Did something break the new make system or maybe it hasn't been merged into the crop_rec_4k that I branched off of?
Quote from: dfort on February 18, 2018, 05:57:31 PM
@alex - off topic - "make clean" wasn't cleaning out adtg_gui so my test builds were including it even though it should have been skipped.
Confirmed.
Quote
In addition, I'm not seeing the uncommitted changes in autoexec.bin which is really helpful. Did something break the new make system or maybe it hasn't been merged into the crop_rec_4k that I branched off of?
This one seems to have worked - there no uncommitted changes that affected autoexec.bin, but there were some for the crop_rec module.
# from crop_rec_4k_no_cmos7_adjust.2018Feb18.6D116.zip
/path/to/magic-lantern/modules/module_hginfo_dump.sh crop_rec.mo
Name : Crop mode recording
Author : a1ex
License : GPL
Summary : Turn the 1080p and 720p video modes into 1:1 sensor crop modes
Description : This alters the 1080p and 720p video modes, transforming them
into 3x (1:1) crop modes, by tweaking the sensor registers.
[...]
Last update : cba0cec on 2018-02-18 07:54:51 UTC by Dan:
Added ENGIO_WRITE addresses.
Build date : 2018-02-18 16:45:23 UTC
Build user : rosiefort@RosieFoComputer
modules/crop_rec/Makefile
modules/crop_rec/README.rst
modules/crop_rec/crop_rec.c
diff -r cba0cec2d4ba modules/crop_rec/crop_rec.c
--- a/modules/crop_rec/crop_rec.c
+++ b/modules/crop_rec/crop_rec.c
@@ -21,6 +21,7 @@
#endif
static int is_5D3 = 0;
+static int is_6D = 0;
static int is_basic = 0;
static CONFIG_INT("crop.preset", crop_preset_index, 0);
@@ -346,7 +347,7 @@
}
}
- if (is_basic)
+ if (is_basic && !is_6D)
{
if (reg == 7)
{
@@ -523,8 +524,11 @@
{
case CROP_PRESET_3x3_1X:
/* start/stop scanning line, very large increments */
- cmos_new[7] = PACK12(6,29);
- break;
+ if (!is_6D)
+ {
+ cmos_new[7] = PACK12(6,29);
+ }
+ break;
}
}
@@ -1865,6 +1869,7 @@
ENGIO_WRITE = 0xFF2AE134;
MEM_ENGIO_WRITE = 0xE51FC15C;
+ is_6D = 1;
is_basic = 1;
crop_presets = crop_presets_basic;
crop_rec_menu[0].choices = crop_choices_basic;
Got it -- I was so used to looking in autoexec.bin for changes that I forgot that you need to run that script to see the changes in the modules.
Hope these changes look good to you. We'll see how they work on the camera. Don't know what is going on with lossless or if it can be fixed in camera but the crop_rec feels like it is almost there. Sure is challenging to work this out without the camera in hand. Not sure how to test this in QEMU or if it is even possible.
Quote from: dfort on February 18, 2018, 05:57:31 PM
Uploaded a couple of more test builds (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). One adjusting CMOS[7] to 0x2A5 and another build that doesn't make any adjustment to CMOS[7].
The one without the CMOS[7] adjustment, looks just like your previous builds, ghost image in live view and recording.
Now the one with the CMOS[7] adjustments seems to work :DI've got multiple MLV's with 3x3 binning and 50fps :D
BUT weirdly enough, the first time I tried this build, I got an error message on recording, multiple times.
But now I can't recreate this error.
Here are some logs:
ML ASSERT:
slots[slot_index].size < max_frame_size
at mlv_lite.c:3388 (raw_video_rec_task), task raw_rec_task
lv:0 mode:3
raw_rec_task stack: 1e0308 [1e03c8-1df3c8]
0x0044C914 @ b935fc:1e0338
0x0044C478 @ 44c970:1e0308
Magic Lantern version : Nightly.2018Feb18.6D116
Mercurial changeset : cba0cec2d4ba+ (crop_rec_4k_6D.116)
Built on 2018-02-18 16:33:53 UTC by DFORT
Free Memory : 342K + 2246K
ML ASSERT:
0
at mlv_lite.c:2497 (compress_task), task compress_task
lv:1 mode:3
compress_task stack: 1e4340 [1e43d0-1e33d0]
0x0044C914 @ b8e53c:1e4370
0x0044C478 @ 44c970:1e4340
Magic Lantern version : Nightly.2018Feb18.6D116
Mercurial changeset : cba0cec2d4ba+ (crop_rec_4k_6D.116)
Built on 2018-02-18 16:33:53 UTC by DFORT
Free Memory : 341K + 2246K
Will do some more testing to and see what it does.
Quote from: Levas on February 19, 2018, 12:54:55 AM
Now the one with the CMOS[7] adjustments seems to work :D
I've got multiple MLV's with 3x3 binning and 50fps :D
BUT weirdly enough, the first time I tried this build, I got an error message on recording, multiple times.
But now I can't recreate this error.
I'm not getting any errors in QEMU and this is doing exactly what you did in order to get it working so let's make this one the hero.
@dfort: just FYI (https://www.magiclantern.fm/forum/index.php?topic=10111.msg125694#msg125694) (this one should be easy to translate into a crop_rec preset). That's actually how this module got its name ;)
I recently switched to the Canon 6D (coming from a 600D) and the only thing i miss is the ability to monitor the Audio Levels with a pair of headphones. I tried to copy the steps mentioned in this post:
Quote from: jjtempey85 on August 12, 2016, 01:08:32 PM
*EDIT* - I forgot the registers I had to port over from Tragic Lantern in audio.h. All better now.
I got tired of not having headphone monitoring on my 6D, so I hacked it in over the course a few evenings. ...
but I was not able to simply copy those changes (probably because the code of Magic Lantern has changed a lot since then). Im guessing some functions were removed or renamed
I stopped trying at this error message:
../../src/audio.h:160:9: error: implicit declaration of function '_audio_ic_write_bulk';I might look into it again in the next few days and try to get it to work, however my main question is: Where there any problems with those changes? Or was there another reason that this never made it into the official version?
You should probably just provide a declaration; then, to get changes into mainline, the general procedure is to provide a pull request, and other 6D owners to confirm it's working (since I'm unable to test otherwise, except for some limited stuff in QEMU, such as how the menus look like, or whether it turns off the display or not).
The function was declared inside another function (which to me looked a bit weird to begin with), moving it seemed to help.
Now there is an undefined reference to sounddev_active_in which by the looks of it is a canon function with a missing stub for the 6D.
I'm guessing i'll have to refresh my C and Assembler knowledge a bit and have a deeper look into it.
As for getting it into mainline, the way it was done in the previously mentioned post seems kinda hacky and there are some limitations/problems mentioned so i guess it would be necessary to adress those first.
Quote from: a1ex on February 20, 2018, 08:21:09 PM
@dfort: just FYI (https://www.magiclantern.fm/forum/index.php?topic=10111.msg125694#msg125694) (this one should be easy to translate into a crop_rec preset). That's actually how this module got its name ;)
Wow, that post from @Levas is from 3 1/2 years ago. It took that long to make it easy? Looks like 3xzoom/1:1 crop could also apply to the other "is_basic" cameras. Well, they already have the CROP_MODE_HACK but it would still be a good exercise.
so...how can you get the audio?mlv_dump only give me dngs by
mlv_dump file.MLV --dng --no-stripes --no-fixcp
I have loaded mlv_snd.mo and keep it on. :'(
Quote from: dfort on February 21, 2018, 04:27:33 AM
Wow, that post from @Levas is from 3 1/2 years ago. It took that long to make it easy?
FYI, the original crop_rec module was announced 2 years ago (https://www.magiclantern.fm/forum/index.php?topic=17021.0), and it referenced Levas' post from the very beginning. The module was a lot simpler back then, since it only had one preset (you already (https://bitbucket.org/hudson/magic-lantern/pull-requests/762/crop_rec-add-limited-eosm-support-to/diff) know (https://bitbucket.org/hudson/magic-lantern/pull-requests/824/crop_rec-for-700d/diff)).
Best guess: the feature wasn't tempting enough for other folks to look at the source code.
Did some more testing with lossless recording, as known resolution 1824x1026 gives frames with bottom half corrupted.
When we do normal black level fix (1920-1792-1536-1024), we get a normal upper half.
Now I did some more testing, and with an alternative black level fix (1728-1408-2304-2048) I can get a normal bottom half of the same frame :o
Here are the 3 frames, all the same, on my google drive:
-one vanilla, as it comes out of mlv_dump
-one with the 'normal' black level fix for 6d
-and one with an alternative black level fix:
https://drive.google.com/drive/folders/17ywgTKYYMLLvL3QZzkCtFvCHed4CZ4aC?usp=sharing (https://drive.google.com/drive/folders/17ywgTKYYMLLvL3QZzkCtFvCHed4CZ4aC?usp=sharing)
Quote from: MR MIAN on February 21, 2018, 10:31:30 AM
so...how can you get the audio?mlv_dump only give me dngs...
Upload a short MLV with audio so we can examine it.
Quote from: Levas on February 23, 2018, 11:24:47 AM
...frames with bottom half corrupted...we get a normal upper half...I can get a normal bottom half of the same frame
The DNG samples you posted in Reply #783 (https://www.magiclantern.fm/forum/index.php?topic=15088.msg197726#msg197726) were not shot with the crop_rec module, right? (Obvious because of the frame size.)
Maybe I got the DEFAULT_RAW_BUFFER_SIZE wrong?
src/raw.c
#ifdef CONFIG_6D
#define DEFAULT_RAW_BUFFER MEM(0x76d6c + 0x2C)
#define DEFAULT_RAW_BUFFER_SIZE (0x4ee00000 - 0x4d600100)
#endifWe made an adjustment in the crop_rec module to adjust CMOS[7] (https://www.magiclantern.fm/forum/index.php?topic=15088.msg197480#msg197480) (see pull request "PACK12(37,10)" is being applied to the 6D):
modules/crop_rec/crop_rec.c
cmos_new[7] = (is_6D) ? PACK12(37,10) : PACK12(6,29);Is that working with all reduced bit depth and lossless settings?
@Dfort, the dng samples are shot with mlv_lite, lossless 14 bit in normal 1080p mode.
If default buffer size is wrong, how can we fix it, can we check these values, or can we do some trial and error ?
Quote from: dfort on February 23, 2018, 02:54:37 PM
We made an adjustment in the crop_rec module to adjust CMOS[7] (https://www.magiclantern.fm/forum/index.php?topic=15088.msg197480#msg197480) (see pull request "PACK12(37,10)" is being applied to the 6D):
modules/crop_rec/crop_rec.c
cmos_new[7] = (is_6D) ? PACK12(37,10) : PACK12(6,29);
Is that working with all reduced bit depth and lossless settings?
The last crop_rec build you made, the one with the CMOS 7 adjustment, works for all formats, 14-10 bit and lossless all options.
Quote from: Levas on February 23, 2018, 03:29:02 PM
If default buffer size is wrong, how can we fix it, can we check these values, or can we do some trial and error ?
It isn't defined on the 100D so it must be using this:
src/raw.c
#define DEFAULT_RAW_BUFFER_SIZE (9*1024*1024)Simply comment out the DEFAULT_RAW_BUFFER_SIZE for the 6D and see what happens.
0x4ee00000 - 0x4d600100 = 0x17FFF00 - uses this currently for 6D
9*1024*1024 = 9437184 = 0x0900000 - uses this if DEFAULT_RAW_BUFFER_SIZE is commented out[EDIT] That's pretty much half the size. How does this work?
Quote from: Levas on February 23, 2018, 03:29:02 PM
If default buffer size is wrong, how can we fix it, can we check these values, or can we do some trial and error ?
Here (https://www.magiclantern.fm/forum/index.php?topic=5601.msg196632#msg196632) (just needs enabling a compile-time option).
@Alex
I think I've done it right ???
And got this in Photo mode, looks like the buffer goes from
4B328000 to 4CFFFFFC
(https://farm5.staticflickr.com/4622/39733793554_ebdc072584_o.jpg)
Also did a screenshot of the Free Memory dialog:
(https://farm5.staticflickr.com/4710/38633777170_a51d34d8bb_o.jpg)
Looks OK. Same numbers when starting in other modes? (1080p, 720p etc)
Yes same for other modes.
Had to restart the camera a few times to see it that quickly, must say the console text is rapidly moving up and out of sight, is there a way to scroll trough console text afterwards ?
Not exactly; there is an option to save the log to a file (CONSOLE_DEBUG in console.c), but that's pretty much it. However, it's not a bad idea to have a larger - scrollable - buffer.
Let's see if that "Raw buffer guess" @Levas found works. PR updated (https://bitbucket.org/hudson/magic-lantern/pull-requests/875/crop_rec_4k-for-the-6d116/diff) and test build posted (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
[EDIT - Wait a minute. This doesn't make sense: 4B328000 - 4CFFFFFC = -1CD7FFC
What is listed here (https://www.magiclantern.fm/forum/index.php?topic=5601.msg196632#msg196632)for the EOSM is 46798080 - 47F24060 but what is in raw.c and seems to be working properly is 0x47F00000 - 0x46798080. Is this an operation or a range or did I transpose the numbers or ???
Quote from: dfort on February 23, 2018, 02:54:37 PM
Upload a short MLV with audio so we can examine it.
https://pan.baidu.com/s/1qZhil9U (https://pan.baidu.com/s/1qZhil9U)
mlv_dump said it hasn't content audio.
I'm not sure if you kan open this link ,if you can't,maybe i can Email it to you.
thanks a lot.
Quote from: dfort on February 23, 2018, 11:55:47 PM
[EDIT - Wait a minute. This doesn't make sense: 4B328000 - 4CFFFFFC = -1CD7FFC
@Dfort
I think it's a range, I put the biggest number in front.
Made a build with it by using this in raw.c for the 6d.
#define DEFAULT_RAW_BUFFER_SIZE (0x4CFFFFFC - 0x4B328000)
1291845628 - 1261600768 = 30244860 = around 29/30Mb
The build works, but it doesn't fix lossless quirks on the black level and half corrupted frames on some resolutions unfortunately.
Edit, the buffer however is bigger than the standard 9Mb buffer and also a little bigger than the 25Mb buffer you'll get with your(DFort) Crop_rec_4K_6d test builds.
So still a gain here 8)
Edit 2, I see in your source now that you start the buffer at 4DF0000 and end with 4B328000, is there a reason for changing the start address ? It's now even 45Mb in size :D
@Mr Mian,
My Chinese language skills are not very well, tried to download the MLV, but I didn't succeed.
But to record MLV's with audio, you must download the 4 februari build from Dfort.
https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k_mlv_lite_snd.2018Feb04.6D116.zip (https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k_mlv_lite_snd.2018Feb04.6D116.zip)
And be sure to enable the MLV_lite and MLV_snd modules:
(https://farm5.staticflickr.com/4721/40409814062_61674c61ba_b.jpg)
After that, restart camera and then within the raw video menu (highlight it and click Q button on camera) you will see all the way at the bottom of the menu a 'sound recording' option, select it and activate it.
Now you should be able to have MLV's with audio recording
(https://farm5.staticflickr.com/4713/40453537581_d99e5acdcd_b.jpg)
@MR MIAN - Your MLV file has no audio. Follow the instructions posted by @Levas in order to turn on audio in mlv_lite.
I see you are using one of my experimental builds. I've been making changes based on the feedback I'm getting from users because I don't have access to a 6D. Your MLV file shows that you have activated several modules at one time including adv_int, autoexpo, bench, crop_rec, deflick, dot_tune, ettr, mlv_lite, mlv_rec, mlv_snd, raw_twk and silent, that is way too many. In addition, you shouldn't load mlv_lite and mlv_rec at the same time because they will conflict.
It looks like you used crop_rec with a reduced bit depth lossless compression setting, right? When I extract the dng files they look like this over here:
(https://farm5.staticflickr.com/4699/40455810981_2b074fbf3b.jpg) (https://flic.kr/p/24CWB9r)
Not at all like the examples you previously posted.
Good to see that the problem with black levels shifting, when using lossless recording, is not restricted to my canon 6d.
So it's not just my copy of the 6d, but probably all 6d's out there ;D
Quote from: Levas on February 24, 2018, 10:48:11 AM
Edit 2, I see in your source now that you start the buffer at 4DF0000 and end with 4B328000, is there a reason for changing the start address ? It's now even 45Mb in size :D
I was doing this during a break at work yesterday then got busy and forgot to post why I did what I did. Now that I look at it again, maybe I did the wrong thing.
If you look at what is working on the other cameras, for example the 5D3_113:
#define DEFAULT_RAW_BUFFER_SIZE (0x4CDF0000 - 0x4B152000)and compare it to this:
Quote from: a1ex on February 01, 2018, 12:51:29 AM
5D3 1.1.3: 0x4B152000 - 0x4CDFFFFC (repeatable; tested photo mode, 1080p25, 720p50, x5, with and without HDMI monitor)
Note that indeed the larger number has to come first or we'll end up with a negative value. However, notice that on all of the cameras that are working in crop_rec_4k (with the exception of the 100D) the larger number is also rounded down slightly. I went the wrong direction and rounded up. What I should have done, starting with the test you just did:
Quote from: a1ex on February 01, 2018, 12:51:29 AM
6D: 0x4B328000 - 0x4CFFFFFC
and done this:
#define DEFAULT_RAW_BUFFER_SIZE (0x4CFF0000 - 0x4B328000)In addition, the branch I'm using on the pull request was falling behind the crop_rec_4k branch so I merged in the latest changes. This might help with the testing but the pull request is getting messy so once we get things ironed out I should redo the pull request.
I'll post a new build in the usual location (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) and also make a new crop_rec_4k_mlv_lite build because that one is also falling behind. I'm deleting the old builds because we know those have problems and my downloads page needs a clean up.
Quote from: Levas on February 24, 2018, 11:02:37 AM
But to record MLV's with audio, you must download the 4 februari build from Dfort.
(https://farm5.staticflickr.com/4713/40453537581_d99e5acdcd_b.jpg)
thanks a lot.it seems i have a wrong understanding of these modules.i thought if don't active them together will have no conflision.
my mlv_snd comes from the test version on fer 20th and shows a tab in the ML main memu,not in the mlv(lite).
Quote from: dfort on February 24, 2018, 02:20:51 PM
Not at all like the examples you previously posted.
thanks you for pointing out my mistake.this mlv is recorded in 14bit lossless mode(in my memory).the screenshot i posted before are dngs haven fix black level with exiftool.
i will upload more mlv files for test.however,before that,i have to make a struggle to register my google drive since i am in China :'(
@Dfort,
How did you make your famous 6d build with mlv_lite with sound recording option, the one from the 4th of februari ?
Tried to make/compile it myself, but no sound recording option in the mlv_lite menu :-\
Did this in terminal to copy your source:
hg clone https://bitbucket.org/daniel_fort/magic-lantern
cd magic-lantern
hg pull && hg update crop_rec_4k_mlv_snd_6D.116
That should be the right way, right ?
I think there is a mlv_lite branch with sound support.
Wild shot. Will this add sound support?
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_snd_ErwinH
Quote from: Levas on February 26, 2018, 07:19:02 PM
Tried to make/compile it myself, but no sound recording option in the mlv_lite menu :-\
Looks like you're doing everything right in order to compile that branch. Are you turning on the mlv_snd module? I believe that's a requirement.
@Levas - Found something interesting in the EOSM2 crop_rec module that you might want to check and see if something similar is going on with the 6D.
https://www.magiclantern.fm/forum/index.php?topic=15895.msg197884#msg197884
i have play with 14 bit~lossess for somedays.i found something interesting.
i opened dng files come form mlv_dump with dcraw then repaired black level in matlab just like
this.
dcraw = 'dcraw -c -4 -D';
system(sprintf('%s "%s" > tmp.pgm', dcraw, filename));
a = double(imread('tmp.pgm'));
[m,n]=size(a);
for i=1:2:m
for j=1:2:n
out(i,j)=a(i,j)+128;
out(i,j+1)=a(i,j+1)+256;
out(1+i,j)=a(1+i,j)+512;
out(i+1,j+1)=a(i+1,j+1)+1024;
then i did demosaicking in matlab with the demosaic function and output tiff file.
the output image looks very dark.after add on five levels of exposure it looks well.however, i found this way give me lots of noise.
it's strange since i take the photo with a low iso(400) it shouldn't give so many noise.so i did some more research.
i took two mlvs.one is over exposured(+5e) and the other one is totally dark(-10.5).take dngs from them and repair black-level in matlab.for over exposured,max figure is 16382 and for dark image,the average is 2047 and min is 2038.then,for the 0ev image, average is 2150,max 16124, min 2059.
so..it means almost all -10.5~0ev pixels' data were written within 8bit.(2150-2047)*2=206.
i have no idea if highlight data use the range of 2^14-2^7 ,but it seems impossable.
so...maybe for some reasons 6d record wrong data or mlv_dump can't change 14bit~lossess mlv from 6d to dng currectlly...or...for some other reasons.who knows.
sorry for my poor english.
Quote from: MR MIAN on March 03, 2018, 03:29:56 PM
...or...for some other reasons.who knows.
Some other reasons, we're starting to know. Well, maybe just a1ex is starting to know:
https://www.magiclantern.fm/forum/index.php?topic=18443.msg197999#msg197999
Quote from: dfort on March 03, 2018, 04:19:16 PM
Some other reasons, we're starting to know. Well, maybe just a1ex is starting to know:
out of my knowledge range. :'( :'( :'(
Alex and Dfort got it working!!!!!
Normal lossless MLV recording on the 6d, no more black level fixing needed and no more half corrupted frames at 1824x1026 resolution!
Try it out with the MLV_lite module.
Download the latest Crop_rec_4K for 6d here:
https://bitbucket.org/daniel_fort/magic-lantern/downloads/ (https://bitbucket.org/daniel_fort/magic-lantern/downloads/crop_rec_4k.2018Mar03.6D116.zip)
One thing, this build doesn't have the sound recording option in MLV_lite.
Probably needs some merging with the branch Danne posted before, will look into it later.
Quote from: Danne on February 26, 2018, 07:48:39 PM
I think there is a mlv_lite branch with sound support.
Wild shot. Will this add sound support?
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_snd_ErwinH
Does anyone know how I can merge the above with Dfort's build for 6d ?
Working on a Mac, I know how to compile, I know how I get the latest updated source from Dfort.
But how to merge ?
Quote from: a1ex on March 03, 2018, 11:00:53 PM
Simplified patch (to be applied from scratch):
d5-check.patch (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/d5-check.patch) (unchanged)
lossless-res-d5-v2.patch (http://a1ex.magiclantern.fm/bleeding-edge/raw/lossless/lossless-res-d5-v2.patch)
Please try on 6D, 700D, 650D, 70D, 100D, EOSM and (if possible) EOSM2. If it works, I'll commit this one.
Applied above patches also to
crop_rec_4k_mlv_lite_snd branch and made a build for testing. No idea about mlv_snd status here on 6D.
If you want to do it yourself you can apply patches easy by doing following from inside root directory:
hg import [drag patch here and hit enter]Not sure how to revert patches so make it on a copy of your directory.
6D test build:https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Mar04.6D116.zip
I sense there is some pull request missing for 6D already in crop_rec_4k branch around lossless stuff so this might not work at all as it´s a branch from crop_rec_4k...
Quote from: Danne on March 04, 2018, 01:44:29 PM
I sense there is some pull request missing for 6D already in crop_rec_4k branch around lossless stuff so this might not work at all as it´s a branch from crop_rec_4k...
You're right, lossless recording doesn't work yet in this build, but sound recording with MLV_lite does.
So I think I download the source of the crop_rek_4k_mlv_lite_snd branch and the source of Dforts page.
I can make this work I guess.
Probably only files to check and alter are:
mlv_lite.c
raw.c
lossless.c
@Levas
Added dfort PR here https://bitbucket.org/hudson/magic-lantern/pull-requests/909/lossless-compression-updates-for-all-digic/diff#chg-modules/silent/lossless.c into the crop_rec_4k_mlv_lite_snd branch, might work now.
source:
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_mlv_lite_snd_6D_70D
Test build(sound,lossless)
https://bitbucket.org/Dannephoto/magic-lantern/downloads/magiclantern-Nightly.2018Mar04.6D116.zip
@Danne,
Perfect! Your build works, lossless with sound on the 6d :D
How great! Thanks to A1ex and dfort and nice that I was able to provide a temporary build. Updated my Reply #811 with sources.
@Danne
How can I get the source of this ?
Do I have to download the Crop_rec_4k_mlv_lite_snd build from Hudson and add the pull request from Dfort ?
Or do you have the source of this build on your bitbucket ?
Just posted about sources in my post above yours :)
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_mlv_lite_snd_6D_70D
Anyway. It´s the patches from Alex and what else was missing I just copy pasted from dfort PR also linked to. I believe you can merge dfort PR into crop_rec_4k_mlv_lite_snd and you are good to go, A1ex patches included already.
That's pretty much it. Just merge crop_rec_4k and crop_rec_4k_mlv_lite_snd. Since we're working with pretty much all of the Digic 5 cameras and trying to resolve lossless compression on just a few of them without breaking the others, I didn't want to add mlv_lite_snd into the this just yet.
@Levas - please check and see if the latest 6D test build resolves the issue of saving full-res silent lossless. If it does I'll commit it and make a new test build with the sound option.
@Danne - hg import immediately commits the changes. When I get into a mess and can't back out changes I just blow off my local repository and re-clone it from the remote.
Check!
Quote from: Levas on March 04, 2018, 04:55:59 PM
This build from Dfort has working full-res-silent lossless pictures.
Simple lossless also works
And I have recorded a 14 bit lossless mlv (1824x1026) which gave normal frames.
So this means that the 6d doesn't need RABBIT, right ?
The RABBIT gets a carrot -- uploaded a crop_rec_4k_mlv_lite_snd test build with the latest 6D changes.
Tested the following with @dfort latest build from his download page:
- 14 bit lossless mlv (1824x1026) video
- 12 bit lossless mlv (1824x1026) video
- 11-8 bit lossless mlv (1824x1026) video
Processed them with mlv_dump to get a single dng, and all seem to work well, no weird artifacts.
File size:
- 14 bit, 1,878 KB
- 12 bit, 1,630 KB
- 11-8 bit, 1,565 KB
Post-processing works with MLV APP
Sound works too.
Hi there!
Is it possible to download Test build(crop_rec_4k_mlv_lite_snd) from Bitbucket?
Unfortunately the link provided by Danne (#811) is 404 page
Looking for a memory benchmark screenshot with any recent build (older than this post), taken in some particular conditions:
- photo mode, right after startup (without entering LiveView!)
- there should be no images on the card (the PLAY dialog must show "No image")
Running this scenario in QEMU gives artifacts on the screen; just wanted to check whether it also happens on real hardware.
If the screenshot doesn't look fine, try playing Arkanoid - it will show the same artifact.
Might also happen on other D5 models, but I've only seen it on 5D3 1.2.3 (on camera, but clean in QEMU) and on 6D (in QEMU). Enabling the change from 03c5f43 should fix it.
Quote from: a1ex on March 10, 2018, 07:07:29 PM
Looking for a memory benchmark screenshot with any recent build (older than this post), taken in some particular conditions:
- photo mode, right after startup (without entering LiveView!)
- there should be no images on the card (the PLAY dialog must show "No image")
Running this scenario in QEMU gives artifacts on the screen; just wanted to check whether it also happens on real hardware.
If the screenshot doesn't look fine, try playing Arkanoid - it will show the same artifact.
Might also happen on other D5 models, but I've only seen it on 5D3 1.2.3 (on camera, but clean in QEMU) and on 6D (in QEMU). Enabling the change from 03c5f43 should fix it.
(https://thumb.ibb.co/dRAhYS/2018_03_10_22_48_13.jpg) (https://ibb.co/dRAhYS)
Thanks; mine looks like this:
(http://a1ex.magiclantern.fm/bleeding-edge/qemu/6d-membench.png) (http://a1ex.magiclantern.fm/bleeding-edge/qemu/6d-ark.png)
and used to look like that on 5D3 1.2.3 a long time ago.
On 5D3 1.2.3, that happened if (and only if) the camera is started outside LiveView, without any images on the card (emphasis added, just to make sure you have ran this test correctly). Deleting the images before running the test is not enough - the camera must be started without any images on the card.
I enabled benchmark and arkanoid module, restarted camera, low level formatted the card and restarted, pressed trash can and went into ML menu and memory benchmark (1 min).
So i had some time to look into the headphone stuff again and it was just the missing stub. After seeing that the stub address for SoundDevActiveIn and sounddev_active_in can be the same, as done for the 650D i just did the same.
I opened a pull request: https://bitbucket.org/hudson/magic-lantern/pull-requests/911/enabled-headphone-monitoring-for-the-6d/
Which is probably not up to the magiclantern standard at the moment (Im guessing the problems with toggling the option before attaching the cable and taking pictures would need to be adressed first)
Due to my limited knowledge of magic lantern/c/assembler right now im not able to further improve this (I'll have to look into some more documentation and try to learn more about it)
Any ideas/hints as well as other contributors/tester would be appreciated.
Quote from: blubbblubb on March 15, 2018, 03:00:38 AM
Im guessing the problems with toggling the option before attaching the cable and taking pictures would need to be adressed first
... I didn't even know about their existence; will try to reproduce in QEMU.
I am running latest nightly 1.1.6, not sure if anyone else has experienced this. But unable to get overlays to work properly, specifically histogram. When not in liveview entering ML it shows histogram is on and overlay is set to on in all modes. But when in liveview and scroll through display using info button no histogram. I have done everything but re install ML which will be done tonight. At a loss til reload. Any ideas?
Did reinstalling fix your issue?
All overlays work fine for me with the latest nightly.
Anyone able to get a 6D.118 firmware dump please PM me. Thanks!
are there any tricks to using the portable rom dumper?
I tried it multiple times with 2 different freshly formatted SD cards and only the checksum for ROM0B.BIN stays the same
Also im not able to copy the files using Linux from the SD Card, it always shows:
Error when getting information for file "/run/media/EOS_DEVELOP/¬¬uu¬¬uu.QUU": Input/output error.
Windows seems to read them fine, but shows wrong information about the available space on the SD Card
Try old-fashioned SD-card, not SDHC, SDXC. 512MByte/1GByte should be fine.
@blubbblubb - If you are having too many problems with the Portable Dumper try the Blind Dumper (https://www.magiclantern.fm/forum/index.php?topic=16534.msg199731#msg199731).
Ok, so i tried the portable dumper on 2 256MB cards, where either nothing happens or the process freezes, i then tried a 1GB card which seems to complete the dump but the checksums for the ROM1*.bin do not match. (But i can still read the card from linux)
I then moved to the blind dumper, which if i understand correctly is used by entering the Play mode.
This creates a 16,8MB file called "(NULL)" which also has different checksums for each dump.
Im not sure if im doing something wrong or if the dumpers do not work with this firmware/camera
I tried formatting the cards throug linux and the camera and made them bootable via the "make_bootable.sh" script.
Edit: just sent you the dumps, i hope at least one of them works
First one I tried:
(https://farm1.staticflickr.com/806/26630367577_69f9017f6d.jpg) (https://flic.kr/p/GzeAuz)
Thanks! I'll post 6D.116 -> 6D.118 updates on this topic.
Really cool dfort. I'll post you the 1100D dump tomorrow.
Just a progress report on the 6D.118 firmware update. We're leap frogging over the 1.1.7 update so there are more changes on this one than the other recent firmware updates I worked on. In addition, building a simple minimal autoexec.bin didn't work with the 6D. ML isn't working with 1.1.8 yet but I thought I'd check the accuracy of the firmware signature printout because other cameras were showing the wrong signature.
The signature for 1.1.6 is:
#define SIG_6D_116 0x11cb1ed2
But this is what "Hello World" printed:
(https://farm1.staticflickr.com/825/26660851927_27cd40c8a4.jpg) (https://flic.kr/p/GBVQqP)
In addition, the QEMU debugmsg.gdb should be updated:
# ./run_canon_fw.sh 6D -d debugmsg
# ./run_canon_fw.sh 6D -d debugmsg -s -S & arm-none-eabi-gdb -x 6D/debugmsg.gdb
source -v debug-logging.gdb
# To get debugging symbols from Magic Lantern, uncomment one of these:
#symbol-file ../magic-lantern/platform/6D.118/magiclantern
#symbol-file ../magic-lantern/platform/6D.118/autoexec
#symbol-file ../magic-lantern/platform/6D.118/stubs.o
macro define CURRENT_TASK 0x74C28
macro define CURRENT_ISR (MEM(0x648) ? MEM(0x64C) >> 2 : 0)
# GDB hook is very slow; -d debugmsg is much faster
# ./run_canon_fw.sh will use this address, don't delete it
# b *0x67c8
# DebugMsg_log
b *0x973c
task_create_log
b *0x8FE4
register_interrupt_log
# properties
if 0
b *0xff12fd64
prop_request_change_log
b *0xff30fbb4
mpu_analyze_recv_data_log
b *0xff30d2c0
prop_lookup_maybe_log
b *0xff315e58
mpu_prop_lookup_log
end
cont
Just a lack of progress report on the 1.1.6 to 1.1.8 firmware update.
6D.116 in QEMU:
[BOOT] reserved 605952 bytes for ML (used 531520)
K302 READY
[SF] InstallSerialFlash 4 0xc022002c 0x0 0x800000 1
[SF] GPIO Base 0xc022002c 0xc022002c
[ init:ff149bfc ] (00:01) [SF] SetCSSerialFlash : 0xc022002c 0x46
[ init:ff146a58 ] (00:01) [PM] DisablePowerSave (Counter = 1)
[ init:ff0c32b0 ] (8b:16)
K302 ICU Firmware Version 1.1.6 ( 5.8.4 )
[ init:ff0c32c4 ] (8b:05)
ICU Release DateTime 2014.10.23 17:38:50
[ init:ff0fc404 ] (00:03) [SEQ] CreateSequencer (Startup, Num = 6)
[ init:ff0fc658 ] (00:02) [SEQ] NotifyComplete (Startup, Flag = 0x10000)
[ init:ff0fc6bc ] (00:03) [SEQ] NotifyComplete (Cur = 0, 0x10000, Flag = 0x10000)
[BOOT] 113B84 now contains 0, restoring 0.
...
6D.118 in QEMU
[BOOT] reserved 605952 bytes for ML (used 531520)
K302 READY
[SF] InstallSerialFlash 4 0xc022002c 0x0 0x800000 1
[SF] GPIO Base 0xc022002c 0xc022002c
[BOOT] 113B84 now contains BAAABAAA, restoring 0.
Any clues what stub, constant, whatever, I've got wrong that is causing this bug -- err, sheep?
[EDIT] Well I did find where this message is being generated.
src/boot-hack.c
#ifdef ARMLIB_OVERFLOWING_BUFFER
// Restore the overwritten value.
// Refuse to boot if ARMLIB_OVERFLOWING_BUFFER is incorrect.
qprintf("[BOOT] %X now contains %X, restoring %X.\n", backup_address, *backup_address, backup_data);
while (backup_address == 0);
while (*backup_address == 0xbaaabaaa);
*backup_address = backup_data;
#endif
[EDIT 2] Got past that sticking point but QEMU is telling me to give up for now. Will try again later:
[****] Starting task 44c8f4(0) ml_init
[BKT] giving up.
[****] Starting task 44c6f8(0) ml_backup
[****] Starting task 4549f0(0) menu_task
[****] Starting task 456bcc(0) menu_redraw_task
[****] Starting task 46bd4c(0) focus_task
[****] Starting task 46d050(0) notifybox_task
[****] Starting task 46fbb8(0) fps_task
[****] Starting task 4777b0(0) shoot_task
[****] Starting task 47093c(0) clock_task
[****] Starting task 47e768(0) audio_common_task
[****] Starting task 486420(0) livev_hiprio_task
[****] Starting task 484c58(0) cls_task
[****] Starting task 490c5c(0) console_task
[****] Starting task 458d7c(0) debug_task
[****] Starting task 4614f4(0) tweak_task
[****] Starting task 46cb3c(0) focus_misc_task
[****] Starting task 479afc(0) vignetting_init
[****] Starting task 496344(0) module_task
[****] Starting task 485d94(0) livev_loprio_task
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
...
Let's find the sheep (edit: nevermind, you have already found it):
cd src
grep -nri BAAABAAA -C 3
That "giving up" message comes from the stack trace; likely an assert triggered somewhere.
Besides that, DebugMsg was not updated in the GDB script (that's why it doesn't print debug messages).
Minimal autoexec seems to work fine here (only on new-dryos-task-hooks). It prints Hello World with 1.1.6, but only blinks the LED with 1.1.8.
Quote from: a1ex on April 21, 2018, 10:40:40 AM
...DebugMsg was not updated in the GDB script...
Here we go:
https://bitbucket.org/daniel_fort/magic-lantern/pull-requests/20/fake-pull-request-to-see-changed-needed/diff#chg-contrib/qemu/scripts/6D/debugmsg.gdb
I made this "fake" pull request in order to easily see all the changes. Bitbucket seemed to have a mind of its own and the first attempt went to the hudson repository--sorry about that!
Not sure if I'm doing this properly but I build my QEMU environment from the qemu branch then switch over to another branch to work out the changes needed to update the firmware. I normally get all the way through on the unified branch then update other branches as needed after it is working in QEMU but on this one I switched to new-dryos-task-hooks because unified wasn't showing enough debugging messages. I tried the copy_back_to_contrib.sh script but it updated everything except the 6D/debugmsg.gdb file so I copied it manually from my qemu-eos environment.
In any case--
Quote from: a1ex on April 21, 2018, 10:40:40 AM
Minimal autoexec seems to work fine here (only on new-dryos-task-hooks)...but only blinks the LED with 1.1.8.
Got it blinking here too--Yay!
The 6D.118 firmware update fixes the same issues as the 5D3.135 update:
Quote1. Fixes a phenomenon in which standard exposure may not be obtained, or an irregular exposure may result, when Silent LV (Live View) shooting with the following TS-E lenses: TS-E 50mm f/2.8L MACRO, TS-E 90mm f/2.8L MACRO, or TS-E 135mm f/4L MACRO.
That doesn't seem like a big update but it did move lots of addresses that the recent firmware updates didn't touch on the other cameras. In addition, we're leap frogging over the 6D.117 update:
Quote(Previous) Version 1.1.7 improvements:
Corrects a phenomenon in which when using the camera with the EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to "Enable", correction will not be applied.
So this firmware update along with the 5D3.135 update are more challenging. However, we'll get there, eventually -- maybe. That's encouraging!
Continuing on the 6D.118 testing, I'm still getting a bunch of these messages in QEMU:
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
[BKT] giving up.
...
Searching the forum turns up only "never giving up" so -- ok, let's keep going.
Minimal autoexec.bin led flashing is fine but no "Hello World" and a full build saves these assert logs:
ML ASSERT:
streq(stateobj->type, "StateObject")
at ../../src/state-object.c:251 (stateobj_start_spy), task ml_init
lv:0 mode:3
ml_init stack: 1e3368 [1e33c8-1df3c8]
0xUNKNOWN @ 44c944:1e33a8
0x0047A838 @ 47a8c8:1e33a0
0x0044CA54 @ 47a864:1e3398
0x0044C478 @ 44cab0:1e3368
I see where they are being generated but having a hard time trying to trace back to figure out what is blocking ml_init. Pretty sure I've got a few stubs or constants wrong but which ones?
Another issue I noticed is that the QEMU debug messages aren't always labeled:
[MPU] Received: 08 06 00 00 02 0e 00 00 (Complete WaitID = 0x80000001 Mode group - spell #2)
[ :ff14107c ] (00:07) [RTC] ChangePropertyCBR 0x0, 0x0
[ PropMgr:ff149eb0 ] register_interrupt(null, 0x34, 0xff149d04, 0x1)
[ Startup:ff149eb0 ] register_interrupt(null, 0x34, 0xff149d04, 0x1)
[RTC] RTC_Permit 0x20[ :ff14d6c8 ] (00:03) [SND] Seq LPC 5-0
[ :ff14d6f8 ] (00:03) [SND] HARB_ARBMODE Before:00000000 Current:00000000
[ :ff14d730 ] (00:03) [SND] HARB_HARBCTRL Before:00000000 Current:00000000
[ :ff14d740 ] (00:03) [SND] Seq LPC 5-1
[ :ff14d768 ] (00:03) [SND] Seq LPC 5-2
[ :ff14d78c ] (00:03) [SND] Seq LPC 5-3
[ Startup:ff14d7a0 ] register_interrupt(SEQ, 0x9c, 0xff14d648, 0x0)
On the 6D.116 these are all labeled.
Another 6D.118 progress report.
Merged some of the experimental branches, tweaked some more constants and the "giving up" messages are gone so let's not give up! ML goes through the start up process and backs up the firmware. That's the good news, the bad news is that there is still something that I haven't been able to track down that is keeping ML from writing to the LCD and there's this scary looking crash log:
[65798245] tweak_task: NULL PTR (c0f14408,e1a00000)
pc= ed1c lr= 4b2da0 stack=1f13e8+0x1000
entry=461b00(0)
e1a00000 e59ff014 e59ff014 e59ff014
e59ff014 e1a00000 e59ff010 e59ff010
Magic Lantern version : Nightly.2018May01.6D118
Mercurial changeset : a94c0e275871+ (new-dryos-task-hooks_6D.118)
Built on 2018-05-01 13:10:29 UTC by rosiefort@RosieFoComputer.
Free Memory : 384K + 2518K
It is also saving some assert logs which are pointing to a problem with the bitmap video ram start address:
ML ASSERT:
0
at ../../src/bmp.c:69 (BMP_VRAM_START), task console_task
lv:0 mode:3
console_task stack: 20c318 [20c448-20b448]
0x0045B7C0 @ 46a118:20c358
0x0045B6D0 @ 45b78c:20c350
0x0044C9F4 @ 45b760:20c348
0x0044C478 @ 44ca50:20c318
Magic Lantern version : Nightly.2018May01.6D118
Mercurial changeset : a94c0e275871+ (new-dryos-task-hooks_6D.118)
Built on 2018-05-01 13:10:29 UTC by rosiefort@RosieFoComputer.
Free Memory : 384K + 2518K
At the moment I'm lost trying to figure out what to look for in stubs.S, consts.h or ??? to resolve this issue.
Hello 6D.118!
(https://farm1.staticflickr.com/869/41850441271_399c969dbd.jpg) (https://flic.kr/p/26Lbs9g)
Looks like it is working quite nicely--in QEMU.
(https://farm1.staticflickr.com/970/41133369644_bf70721e09.jpg) (https://flic.kr/p/25EPgJm)
The problem stubs were LCD_Palette and bmp_vram_info. Don't know how I missed these before because the comments in the code were pretty obvious.
Test build on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). I merged several branches including new-dryos-task-hooks, qemu and lua_fix while I was working on this so you should be able to run the selftest module along with the lua tests with this test build. This is a very early build so no ML-SETUP.FIR yet. Make sure your camera and cards have their bootflags set.
I'm copying the changes made on the 6D mega merge branch back into unified and got this "interesting" error message worth sharing:
DRYOS PANIC: Module Code = 1, Panic Code = 5
(https://farm1.staticflickr.com/949/41150150264_2c8fd1fcbf.jpg) (https://flic.kr/p/25Gih2o)
I don't share all of my failures but this one is a good argument for using QEMU even if you have the camera in your hands.
Problem was HIJACK_TASK_ADDR, which isn't used in the experimental branches I was using.
Looks good in QEMU and I even ran the memory benchmark.
(https://farm1.staticflickr.com/908/41151628274_70d7742d03.jpg) (https://flic.kr/p/25GqRoj)
Pull request (https://bitbucket.org/hudson/magic-lantern/pull-requests/926/update-to-6d118/diff) submitted and test build posted on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/).
Looking for testers to try out the "Nightly" build and see if it works the same as the 6D.116 from the official downloads page (https://builds.magiclantern.fm/6D-116.html). Then run the selftest module and lua module API stubs tests and report back.
Note that this is an early test build so no ML-SETUP.FIR yet. You'll have to make sure ML is installed and running before doing the firmware update so the bootflags on both camera and card are set. I put a "6D Canon Firmware for Testers" package on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) so you don't have to go searching for the Canon firmware updaters.
Ok--something that doesn't have to do with the firmware update. There's a report of an error message coming up on the 6D on the 10bit/12bit branch and possibly the crop_rec_4k branch. Can someone with a 6D confirm this?
https://www.magiclantern.fm/forum/index.php?topic=5601.msg200990#msg200990
i tried the 10/12 Bit branch and posted in the other topic.
Regarding the 1.18 Update, i assume it is considered "safe" to try it now? I'll try to test it in the next week or so, not sure if i have a chance before
Depends on how "safe" you believe an experimental build of an untested firmware update is. The QEMU tests look good but it hasn't been tried on real hardware yet. It doesn't have a ML-SETUP.FIR so make sure your card and camera bootflags are set (don't uninstall ML before doing the firmware update). The only problem we had so far was a case where the camera bootflag was not set and the battery "jumped" out in the middle of running the firmware update.
Check some of the other camera specific topics to see what tests we're running and how it is going. Generally, the firmware updates have been going quite nicely and we're even resolving some long standing issues.
Hi,
my 6D (from Simply Electronics) has this firmware: 5.7.4 78 (1f)
I do not know why but it is not official Canon Firmware. Do you know how can i flash an official firmware?
Now, i do not know if i can flash Magic Lantern on it.
Moreover, all functions with EOS Utility on my computer can not be used because the camera is not known :/
Thank you :)
It seems that your camera is in factory mode. If you browse the menus, do you see a position "Factory Menu?". If you bought it that way new or was repairing at Canon service recently, they have screwed it up, not switching the camera to a normal mode and should do it on request...
Yes i've this factory menu....
But the Simply Electronics is closed now and warranty is over :(
You have a normal official firmware in your camera, "only" the Factory Mode has to be disabled. Then the reported FW version will be back to normal.
I'm not sure if anyone here could help you remotely. This would need a possibility of executing a custom code on your camera (I guess setting the boot flag, booting and starting Canon firmware should be possible in this mode but I'm only guessing!) and calling some functions from Canon FW (FA_SetProperty, FA_SaveProperty, MonWrite, MonCall...). The latter would need that the functions' stubs are in this mode same as in normal mode. If they are -- I have no idea. It would also need understanding which property to modify and this area is not explored yet in the context of Factory Mode by ML developers! AFAIR no one played with it yet. I could support here providing logs from another camera models to analyze how the Factory Mode is enabled and disabled over USB interface. Probably it's similar for 6D.
You can try finding any third-party DSLR service and ask if they can do it for you and how much would they charge. I'm sure there are several available in France and this is a 5 minutes only job if one only has a tool. Just call a few and ask directly for the possibility and a price.
OK, thanks a lot for your informations !
i'll try to find a Canon Center near my city to disable the factory mode :)
Perhaps in a store "Canon Pro Partenaire" (Canon Pro Partner) in my city
Quote from: dfort on May 03, 2018, 07:24:53 PM
...
Looking for testers to try out the "Nightly" build and see if it works the same as the 6D.116 from the official downloads page (https://builds.magiclantern.fm/6D-116.html). Then run the selftest module and lua module API stubs tests and report back.
Note that this is an early test build so no ML-SETUP.FIR yet. You'll have to make sure ML is installed and running before doing the firmware update so the bootflags on both camera and card are set. I put a "6D Canon Firmware for Testers" package on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/) so you don't have to go searching for the Canon firmware updaters.
I finally had some time and tried the test version, i picked the "magiclantern-Nightly.2018May03.6D118" as it is sligthly newer than "test_build.2018May03.6D118.zip" (according to the timestamps inside the zip.)
I ran the following tests (i hope those are the correct ones):
- Selftests - Stubs API test
- Selftests - Quick test (around 15 min)
- LUA - Script API tests
i attached the logs for both API tests, the quick test did not generate a log file but completed fine. The selftest API test contains some [FAIL] while trying to allocate some memory
But i also encountered some weird stuff outside the tests:
- Entering Liveview in Photo mode crashes the camera, the liveview freezes and there is no reaction to any of the buttons, after a short while the shoulder display just shows "Err" and there is no crash log on the SD card
Taking Photos in Moviemode works
The LUA API test is able to enter Liveview in Photomode, however after it finished i went into the magic lantern menu with the trash button and exited again back into liveview in photo mode and the camera crashed instantly
- Every time i start recording a movie i get the "Sound disabled" notification no matter if sound recording is set to manual oder automatic (i did not try an external mic)
Stub test
[Pass] is_play_mode() => 0x1
[Pass] src = fio_malloc(size) => 0x42000088
[Pass] dst = fio_malloc(size) => 0x42804094
[Pass] memcmp(dst, src, 4097) => 0x2
[Pass] edmac_memcpy(dst, src, 4097) => 0x42804094
[Pass] memcmp(dst, src, 4097) => 0x0
[Pass] edmac_memcpy(dst, src, 4097) => 0x42804094
[Pass] memcmp(dst, src, size) => 0xffffffde
[Pass] edmac_memcpy(dst, src, size) => 0x42804094
[Pass] memcmp(dst, src, size) => 0x0
[Pass] memcmp(dst, src, size) => 0xffffff8f
[Pass] edmac_memcpy_start(dst, src, size) => 0x42804094
dt => 0x17e2
[Pass] copied => 0x4014ec
[Pass] copied => 0x4014ec
[Pass] copied => 0x4014ec
[Pass] memcmp(dst, src, copied) => 0x0
[Pass] memcmp(dst, src, copied + 16) => 0xffffffc7
edmac_memcpy_finish()
free(src)
free(dst)
Cache test A (EDMAC on BMP buffer)...
[Pass] bmp = bmp_load("ML/CROPMKS/CINESCO2.BMP", 1) => 0x1515c0
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x620
[Pass] old => 0x0
[Pass] irq => 0xc0
[Pass] differences => 0x0
Cache test B (FIO on 8K buffer)...
[Pass] tries[0] => 0xec
[Pass] tries[1] => 0xfa
[Pass] tries[2] => 0x102
[Pass] tries[3] => 0x100
[Pass] failr[0] => 0x48
[Pass] failw[0] => 0x6e
[Pass] failr[1] => 0x51
[Pass] failw[1] => 0x0
[Pass] failr[2] => 0x0
[Pass] failw[2] => 0x7c
[Pass] failr[3] => 0x0
[Pass] failw[3] => 0x0
times[0] / tries[0] => 0x38
times[1] / tries[1] => 0x37
times[2] / tries[2] => 0x3d
times[3] / tries[3] => 0x3d
Cache tests finished.
[Pass] f = FIO_CreateFile("test.dat") => 0x6
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)0xFF000000, 0x10000) => 0x10000
FIO_CloseFile(f)
[Pass] FIO_GetFileSize("test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = (void*)_alloc_dma_memory(0x20000) => 0x4089a804
[Pass] f = FIO_OpenFile("test.dat", O_RDONLY | O_SYNC) => 0x6
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
FIO_CloseFile(f)
_free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] buf = fio_malloc(0x1000000) => 0x42000088
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000000
[Pass] f = FIO_OpenFile("test.dat", O_RDWR | O_SYNC) => 0x6
[Pass] FIO_SeekSkipFile(f, 0, SEEK_END) => 0x82000000
[Pass] FIO_WriteFile(f, buf, 0x10) => 0x10
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_END) => 0x81fffff0
[Pass] FIO_WriteFile(f, buf, 0x30) => 0x30
[Pass] FIO_SeekSkipFile(f, 0x20, SEEK_SET) => 0x20
[Pass] FIO_SeekSkipFile(f, 0x30, SEEK_CUR) => 0x50
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_CUR) => 0x30
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000020
[Pass] is_file("test.dat") => 0x1
[Pass] FIO_RemoveFile("test.dat") => 0x0
[Pass] is_file("test.dat") => 0x0
[Pass] SetTimerAfter(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x7abe
msleep(900)
[Pass] timer_func => 0x0
msleep(200)
[Pass] timer_func => 0x1
[Pass] ABS((timer_time/1000 - t0) - 1000) => 0x5
[Pass] ABS((timer_arg - ta0) - 1000) => 0xa
[Pass] timer = SetTimerAfter(1000, timer_cbr, overrun_cbr, 0) => 0x7ac0
msleep(400)
CancelTimer(timer)
[Pass] timer_func => 0x0
msleep(1500)
[Pass] timer_func => 0x0
[Pass] SetHPTimerAfterNow(0, timer_cbr, overrun_cbr, 0) => 0x15
[Pass] timer_func => 0x2
[Pass] SetHPTimerAfterNow(100000, timer_cbr, overrun_cbr, 0) => 0x2f79e
msleep(90)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 100000) => 0xe4
[Pass] ABS(DeltaT(timer_arg, ta0) - 100000) => 0xc2
[Pass] ABS((get_us_clock_value() - t0) - 110000) => 0xcb
[Pass] SetHPTimerAfterNow(90000, next_tick_cbr, overrun_cbr, 0) => 0x2f7a0
msleep(80)
[Pass] timer_func => 0x0
msleep(20)
[Pass] timer_func => 0x3
msleep(80)
[Pass] timer_func => 0x3
msleep(20)
[Pass] timer_func => 0x1
[Pass] ABS(DeltaT(timer_time, t0) - 300000) => 0x144
[Pass] ABS(DeltaT(timer_arg, ta0) - 300000) => 0x123
[Pass] ABS((get_us_clock_value() - t0) - 310000) => 0xb6
t0 = *(uint32_t*)0xC0242014 => 0x1c067
msleep(250)
t1 = *(uint32_t*)0xC0242014 => 0x58622
[Pass] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x3
LoadCalendarFromRTC( &now )
s0 = now.tm_sec => 0x39
Date/time: 2018/05/22 18:34:57
msleep(1500)
LoadCalendarFromRTC( &now )
s1 = now.tm_sec => 0x3a
[Pass] MOD(s1-s0, 60) => 0x1
[Pass] MOD(s1-s0, 60) => 0x1
m0 = MALLOC_FREE_MEMORY => 0x10600
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[Pass] CACHEABLE(p) => 0x0
m1 = MALLOC_FREE_MEMORY => 0x10600
_free(p)
m2 = MALLOC_FREE_MEMORY => 0x10600
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[Pass] ABS(m0-m2) => 0x0
m0 = GetFreeMemForAllocateMemory() => 0x121c1c
[Pass] p = (void*)_AllocateMemory(256*1024) => 0x89a7c4
[Pass] CACHEABLE(p) => 0x89a7c4
m1 = GetFreeMemForAllocateMemory() => 0xe1c10
_FreeMemory(p)
m2 = GetFreeMemForAllocateMemory() => 0x121c1c
[Pass] ABS((m0-m1) - 256*1024) => 0xc
[Pass] ABS(m0-m2) => 0x0
m01 = MALLOC_FREE_MEMORY => 0x10600
m02 = GetFreeMemForAllocateMemory() => 0x121c1c
[Pass] p = (void*)_alloc_dma_memory(256*1024) => 0x4089a804
[Pass] UNCACHEABLE(p) => 0x4089a804
[Pass] CACHEABLE(p) => 0x89a804
[Pass] UNCACHEABLE(CACHEABLE(p)) => 0x4089a804
_free_dma_memory(p)
[Pass] p = (void*)_shoot_malloc(24*1024*1024) => 0x42000068
[Pass] UNCACHEABLE(p) => 0x42000068
_shoot_free(p)
m11 = MALLOC_FREE_MEMORY => 0x10600
m12 = GetFreeMemForAllocateMemory() => 0x121c1c
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[FAIL] p = (void*)_malloc(50*1024) => 0x0
[FAIL] ABS((m0-m1) - 50*1024) => 0xc800
[Pass] suite = shoot_malloc_suite_contig(24*1024*1024) => 0x109478
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x1800000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x109528
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x1800000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite_contig(0) => 0x109478
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x1
[Pass] suite->size => 0x2000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x109528
[Pass] chunk->signature => 'MemChunk'
[Pass] chunk->size => 0x2000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(64*1024*1024) => 0x109478
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0xb
[Pass] suite->size => 0x4000000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x109528
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x298000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5ce10094
[Pass] UNCACHEABLE(p) => 0x5ce10094
chunk = GetNextMemoryChunk(suite, chunk) => 0x10a140
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2298000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x10a4f8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2534000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44000070
[Pass] UNCACHEABLE(p) => 0x44000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x10af80
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2694000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5c89c0e4
[Pass] UNCACHEABLE(p) => 0x5c89c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10b9f0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x27f4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5a49c0e4
[Pass] UNCACHEABLE(p) => 0x5a49c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10ed80
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2954000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5809c0e4
[Pass] UNCACHEABLE(p) => 0x5809c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10f3a0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2ab4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ae9c0e4
[Pass] UNCACHEABLE(p) => 0x4ae9c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10fad0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2c14000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48a9c0e4
[Pass] UNCACHEABLE(p) => 0x48a9c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10fd70
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2d74000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4669c0e4
[Pass] UNCACHEABLE(p) => 0x4669c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1100d8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2ed4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4429c0e4
[Pass] UNCACHEABLE(p) => 0x4429c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1103e8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4000000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44400064
[Pass] UNCACHEABLE(p) => 0x44400064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0x4000000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] suite = shoot_malloc_suite(0) => 0x109478
[Pass] suite->signature => 'MemSuite'
[Pass] suite->num_chunks => 0x15
[Pass] suite->size => 0xfb00000
[Pass] chunk = GetFirstChunkFromSuite(suite) => 0x109528
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x298000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5ce10094
[Pass] UNCACHEABLE(p) => 0x5ce10094
chunk = GetNextMemoryChunk(suite, chunk) => 0x10a140
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2298000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x42000064
[Pass] UNCACHEABLE(p) => 0x42000064
chunk = GetNextMemoryChunk(suite, chunk) => 0x10a4f8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2534000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44000070
[Pass] UNCACHEABLE(p) => 0x44000070
chunk = GetNextMemoryChunk(suite, chunk) => 0x10af80
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2694000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5c89c0e4
[Pass] UNCACHEABLE(p) => 0x5c89c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10b9f0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x27f4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5a49c0e4
[Pass] UNCACHEABLE(p) => 0x5a49c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10ed80
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2954000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5809c0e4
[Pass] UNCACHEABLE(p) => 0x5809c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10f3a0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2ab4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ae9c0e4
[Pass] UNCACHEABLE(p) => 0x4ae9c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10fad0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2c14000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48a9c0e4
[Pass] UNCACHEABLE(p) => 0x48a9c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x10fd70
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2d74000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4669c0e4
[Pass] UNCACHEABLE(p) => 0x4669c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1100d8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x2ed4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4429c0e4
[Pass] UNCACHEABLE(p) => 0x4429c0e4
chunk = GetNextMemoryChunk(suite, chunk) => 0x1103e8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x4ed4000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x44400064
[Pass] UNCACHEABLE(p) => 0x44400064
chunk = GetNextMemoryChunk(suite, chunk) => 0x1111d8
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x5170000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x46400070
[Pass] UNCACHEABLE(p) => 0x46400070
chunk = GetNextMemoryChunk(suite, chunk) => 0x113070
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x7170000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x46800064
[Pass] UNCACHEABLE(p) => 0x46800064
chunk = GetNextMemoryChunk(suite, chunk) => 0x114878
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x740c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48800070
[Pass] UNCACHEABLE(p) => 0x48800070
chunk = GetNextMemoryChunk(suite, chunk) => 0x114c98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x940c000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x48c00064
[Pass] UNCACHEABLE(p) => 0x48c00064
chunk = GetNextMemoryChunk(suite, chunk) => 0x115388
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0x96a8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x4ac00070
[Pass] UNCACHEABLE(p) => 0x4ac00070
chunk = GetNextMemoryChunk(suite, chunk) => 0x115708
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xb6a8000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x55e00064
[Pass] UNCACHEABLE(p) => 0x55e00064
chunk = GetNextMemoryChunk(suite, chunk) => 0x115a50
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xb944000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x57e00070
[Pass] UNCACHEABLE(p) => 0x57e00070
chunk = GetNextMemoryChunk(suite, chunk) => 0x1165c0
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xd944000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x58200064
[Pass] UNCACHEABLE(p) => 0x58200064
chunk = GetNextMemoryChunk(suite, chunk) => 0x116800
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xdbe0000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5a200070
[Pass] UNCACHEABLE(p) => 0x5a200070
chunk = GetNextMemoryChunk(suite, chunk) => 0x116c98
[Pass] chunk->signature => 'MemChunk'
[Pass] total += chunk->size => 0xfb00000
[Pass] p = GetMemoryAddressOfMemoryChunk(chunk) => 0x5a600064
[Pass] UNCACHEABLE(p) => 0x5a600064
chunk = GetNextMemoryChunk(suite, chunk) => 0x0
[Pass] total => 0xfb00000
shoot_free_suite(suite); suite = 0; chunk = 0;
[Pass] strlen("abc") => 0x3
[Pass] strlen("qwertyuiop") => 0xa
[Pass] strlen("") => 0x0
[Pass] strcpy(msg, "hi there") => 0x21872c
[Pass] msg => 'hi there'
[Pass] snprintf(a, sizeof(a), "foo") => 0x3
[Pass] snprintf(b, sizeof(b), "foo") => 0x3
[Pass] strcmp(a, b) => 0x0
[Pass] snprintf(a, sizeof(a), "bar") => 0x3
[Pass] snprintf(b, sizeof(b), "baz") => 0x3
[Pass] strcmp(a, b) => 0xfffffff8
[Pass] snprintf(a, sizeof(a), "Display") => 0x7
[Pass] snprintf(b, sizeof(b), "Defishing") => 0x9
[Pass] strcmp(a, b) => 0x4
[Pass] snprintf(buf, 3, "%d", 1234) => 0x2
[Pass] buf => '12'
[Pass] memcpy(foo, bar, 6) => 0x218700
[Pass] foo => 'asdfghuiop'
[Pass] memset(bar, '*', 5) => 0x2186e0
[Pass] bar => '*****hjkl;'
bzero32(bar + 5, 5)
[Pass] bar => '****'
EngDrvOut(LCD_Palette[0], 0x1234)
[Pass] shamem_read(LCD_Palette[0]) => 0x1234
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
call("TurnOffDisplay")
[Pass] DISPLAY_IS_ON => 0x0
call("TurnOnDisplay")
[Pass] DISPLAY_IS_ON => 0x1
task_create("test", 0x1c, 0x1000, test_task, 0) => 0xe0d000ee
[Pass] test_task_created => 0x1
[Pass] get_current_task_name() => 'run_test'
[Pass] task_max => 0x84
[Pass] task_max => 0x84
[Pass] mq = mq ? mq : (void*)msg_queue_create("test", 5) => 0xe0d200c0
[Pass] msg_queue_post(mq, 0x1234567) => 0x0
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x0
[Pass] m => 0x1234567
[Pass] msg_queue_receive(mq, (struct event **) &m, 500) => 0x9
[Pass] sem = sem ? sem : create_named_semaphore("test", 1) => 0xe0d4020c
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] take_semaphore(sem, 500) => 0x9
[Pass] give_semaphore(sem) => 0x0
[Pass] take_semaphore(sem, 500) => 0x0
[Pass] give_semaphore(sem) => 0x0
[Pass] rlock = rlock ? rlock : CreateRecursiveLock(0) => 0xe0d60096
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] AcquireRecursiveLock(rlock, 500) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0x0
[Pass] ReleaseRecursiveLock(rlock) => 0xf
SetGUIRequestMode(1); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x1
SetGUIRequestMode(2); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x2
SetGUIRequestMode(0); msleep(1000);
[Pass] CURRENT_GUI_MODE => 0x0
[Pass] display_idle() => 0x1
GUI_Control(BGMT_PLAY, 0, 0, 0); msleep(1000);
[Pass] PLAY_MODE => 0x1
[Pass] MENU_MODE => 0x0
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(1000);
[Pass] MENU_MODE => 0x1
[Pass] PLAY_MODE => 0x0
[Pass] dialog->type => 'DIALOG'
GUI_Control(BGMT_MENU, 0, 0, 0); msleep(500);
[Pass] MENU_MODE => 0x0
[Pass] PLAY_MODE => 0x0
SW1(1,100)
[Pass] HALFSHUTTER_PRESSED => 0x1
SW1(0,100)
[Pass] HALFSHUTTER_PRESSED => 0x0
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x1
[Pass] is_pure_play_movie_mode() => 0x0
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x0
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x1
[Pass] is_play_mode() => 0x1
[Pass] is_pure_play_photo_mode() => 0x0
[Pass] is_pure_play_movie_mode() => 0x0
LUA Test
===============================================================================
ML/SCRIPTS/API_TEST.LUA - 2018-5-22 19:10:19
===============================================================================
Strict mode tests...
Strict mode tests passed.
Generic tests...
camera = table:
shutter = table:
raw = 123
apex = 8.374999
ms = 3
value = 0.003012
aperture = table:
raw = 40
apex = 4
value = 4
min = table:
raw = 40
apex = 4
value = 4
max = table:
raw = 80
apex = 9
value = 22.6
iso = table:
raw = 88
apex = 7.
value = 400
ec = table:
raw = 0
value = 0
flash_ec = table:
raw = 0
value = 0
kelvin = 6500
mode = 20
metering_mode = 5
drive_mode = 0
model = "Canon EOS 6D"
model_short = "6D"
firmware = "1.1.8"
temperature = 178
state = 0
reboot = function: p
bulb = function: p
shoot = function: p
event = table:
pre_shoot = nil
post_shoot = nil
shoot_task = nil
seconds_clock = nil
keypress = nil
custom_picture_taking = nil
intervalometer = nil
config_save = nil
console = table:
write = function: p
show = function: p
hide = function: p
clear = function: p
lv = table:
enabled = true
paused = false
running = true
zoom = 1
resume = function: p
pause = function: p
stop = function: p
info = function: p
wait = function: p
start = function: p
lens = table:
name = "EF24-70mm f/4L IS USM"
focal_length = 24
focus_distance = 655350
hyperfocal = 5013
dof_near = 4975
dof_far = 1000000
af = true
af_mode = 0
focus = function: p
display = table:
idle = true
height = 480
width = 720
circle = function: p
on = function: p
pixel = function: p
print = function: p
draw = function: p
off = function: p
notify_box = function: p
load = function: p
screenshot = function: p
clear = function: p
rect = function: p
line = function: p
key = table:
last = 0
wait = function: p
press = function: p
menu = table:
visible = false
get = function: p
open = function: p
new = function: p
set = function: p
block = function: p
close = function: p
testmenu = userdata:
value = 0
name = "Script API tests"
help = "Various tests for the Lua scripting API."
help2 = "When adding new Lua APIs, tests for them should go here."
advanced = 0
depends_on = 0
edit_mode = 0
hidden = false
icon_type = 5
jhidden = false
max = 0
min = 0
selected = true
shidden = false
starred = false
submenu_height = 0
submenu_width = 0
unit = 0
works_best_in = 0
run_in_separate_task = 0
select = function: p
update = nil
info = nil
rinfo = nil
warning = nil
movie = table:
recording = false
stop = function: p
start = function: p
dryos = table:
clock = 1771
ms_clock = 1771032
prefix = "IMG_"
dcim_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "B:/DCIM/"
path = "B:/DCIM/100CANON/"
config_dir = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = table:
exists = true
create = function: p
children = function: p
files = function: p
parent = nil
path = "B:/"
path = "ML/"
path = "ML/SETTINGS/"
ml_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9918
folder_number = 100
free_space = 14187776
type = "SD"
path = "B:/"
_card_ptr = userdata
shooting_card = table:
cluster_size = 32768
drive_letter = "B"
file_number = 9918
folder_number = 100
free_space = 14187776
type = "SD"
path = "B:/"
_card_ptr = userdata
date = table:
day = 22
month = 5
year = 2018
sec = 21
yday = 142
isdst = false
hour = 19
wday = 3
min = 10
remove = function: p
call = function: p
directory = function: p
interval = table:
time = 10
count = 0
running = 0
stop = function: p
battery = table:
level = 45
id = 0
performance = 3
time = 9405
drain_rate = 17
task = table:
yield = function: p
create = function: p
property = table:
Generic tests completed.
Module tests...
Copy test: autoexec.bin -> tmp.bin
Copy test OK
Append test: tmp.txt
Append test OK
Testing exposure settings, module 'camera'...
Camera : Canon EOS 6D (6D) 1.1.8
Lens : EF24-70mm f/4L IS USM
Shoot mode: 20
Shutter : ,320 (raw 123, 0.003012s, 3ms, apex 8.374999)
Aperture : 4.0 (raw 40, f/4, apex 4)
Av range : 4.0..22 (raw 40..80, f/4..f/22.6, apex 4..9)
ISO : 400 (raw 88, 400, apex 7.)
EC : 0.0 (raw 0, 0 EV)
Flash EC : 0.0 (raw 0, 0 EV)
Please switch to M mode.
Setting shutter to random values...
Setting ISO to random values...
Setting aperture to random values...
Please switch to Av mode.
Setting EC to random values...
Setting Flash EC to random values...
Exposure tests completed.
Testing module 'lv'...
Starting LiveView...
Setting zoom to x1...
Setting zoom to x5...
Setting zoom to x10...
Setting zoom to x5...
Setting zoom to x1...
Setting zoom to x10...
Setting zoom to x1...
Pausing LiveView...
Resuming LiveView...
Stopping LiveView...
LiveView tests completed.
Focus distance: 655350
Focusing backward...
Focus distance: 655350
Focusing forward with step size 3, wait=true...
...
Focus distance: 510
Focusing backward with step size 3, wait=true...
.
Focus distance: 780
Focus range: 3 steps forward, 1 steps backward.
Focusing forward with step size 3, wait=false...
...
Focus distance: 830
Focusing backward with step size 3, wait=false...
.
Focus distance: 830
Focus range: 3 steps forward, 1 steps backward.
Focusing forward with step size 2, wait=true...
.......................
Focus distance: 380
Focusing backward with step size 2, wait=true...
.....................
Focus distance: 655350
Focus range: 23 steps forward, 21 steps backward.
Focusing forward with step size 2, wait=false...
.......................
Focus distance: 470
Focusing backward with step size 2, wait=false...
.....................
Focus distance: 655350
Focus range: 23 steps forward, 21 steps backward.
Focusing forward with step size 1, wait=true...
............................................................................................
Focus distance: 370
Focusing backward with step size 1, wait=true...
..........................................................................................
Focus distance: 655350
Focus range: 92 steps forward, 90 steps backward.
Focusing forward with step size 1, wait=false...
............................................................................................
Focus distance: 390
Focusing backward with step size 1, wait=false...
..........................................................................................
Focus distance: 655350
Focus range: 92 steps forward, 90 steps backward.
Focus test completed.
Done!
Thanks for testing. The test_build.2018May03.6D118.zip has the lua_fix branch merged into it so it is better to test with that one but it does look like there are some issue to work out.
I'm currently filling in at work for someone on vacation then I'm taking a vacation for about a month so don't expect anything from me in a hurry.
I just got my 6D back from Canon for repair. They updated me to firmware 1.1.8 so ML is not working. Sounds like I am out of luck for a while...love this program used it all the time. :'(
You could always downgrade to firmware 1.1.6
There's a link to the windows version:
https://builds.magiclantern.fm/6D-116.html (https://builds.magiclantern.fm/6D-116.html)
Direct link to file:
http://pel.hu/down/eos6d-v116-win.zip (http://pel.hu/down/eos6d-v116-win.zip)
@JCBERLIN....many of us have downgraded to 1.1.6 so don't be afraid that you will have an unstable camera or lose some functions. Check the 1.1.8 firmware release notes here: https://www.canon.com.au/support/support-news/firmware-updates/eos-6d-firmware-update-version-1-1-8 (https://www.canon.com.au/support/support-news/firmware-updates/eos-6d-firmware-update-version-1-1-8) and unless you are in this specific situation you should be just fine.
Not sure how many of you know their way with the adtg_gui module.
But here's a sheet with some interesting registers to override:
https://docs.google.com/spreadsheets/d/1iapLI7UrgfCJGwPSFsyhYeKl8fSTY4RVXvDR7MiaOp4/edit?usp=sharing (https://docs.google.com/spreadsheets/d/1iapLI7UrgfCJGwPSFsyhYeKl8fSTY4RVXvDR7MiaOp4/edit?usp=sharing)
Left side of the sheet interesting registers and their default values in every video and photo mode.
At the right side of the sheet values to override with adtg_gui module to get interesting crop modes.
Usable fps modes:
2688 x 1222 @ 24fps
2560 x 1222 @ 25fps
3384 x 952 @ 25fps
And just for fun:
5480x1190 @ 11 fps
Cool Levas. Could you put in the registers for the 6D and 2560x1222 25fps here. Like to update my adtg_gui version and numbers for 6D are all wrong I guess:
else if (is_camera("6D", "1.1.6"))
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0x5040298;
case 0x6014:
return 0x747;
case 0x6713c:
return 0x535;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x8172:
return 0x4e6;
case 0x8178:
return 0x4e6;
case 0x8000:
return 0x5;
}
}
}
For my eosm this works wonders for 2520x1320 24 fps:
else if (is_camera("EOSM", "2.0.2"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 7:
return 0xaa9; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x5490298; /* 2520x1320, works */
/* return 0x5590298; 2520x1336, corruption */
case 0x6014:
return 0x745;
case 0x713c:
return 0x535;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0x8f4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x87c; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178:
return 0x87c;
}
}
}
Hi Danne,
I think you can update it for the 6d with these values:
else if (is_camera("6D", "1.1.6"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 7:
return 0x268; /* CMOS[7]: White bar at the bottom removement */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0x4e502a0;
case 0x6014:
return 0x5ba;
case 0x713c:
return 0x516;
case 0x7150:
return 0x4e5;
case 0x6010:
return 0x2b9;
case 0x6008:
return 0x2b902b9;
case 0x600c:
return 0x2b902b9;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x8172:
return 0x695;
case 0x8178:
return 0x695;
case 0x82f8:
return 0x697;
case 0x8179:
return 0x51c;
case 0x82f9:
return 0x560;
case 0x800c:
return 0x0;
case 0x8000:
return 0x5;
}
}
}
Great. Helps me get some wider perspective around these registers on different cams.
Ok, here's a short tutorial for how to use adtg_gui module (not for the faint hearted :P )
First download the most advanced Magic lantern version for the 6d at this moment:
The crop_rec_4K build from the experiments download page:
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/72/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Mar10.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/72/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Mar10.6D116.zip)
After that, download the adtg_gui module:
From the module downloads page:
https://builds.magiclantern.fm/jenkins/job/iso-research/11/artifact/modules/adtg_gui/adtg_gui.mo (https://builds.magiclantern.fm/jenkins/job/iso-research/11/artifact/modules/adtg_gui/adtg_gui.mo)
Copy the adtg_gui module file in the "\ML\modules\" directory on your SD-card.
Put the SD in your precious 6d and turn camera on:
Enable, at least, the following modules:
adtg_gui
file_man
mlv_lite
mlv_play
mlv_snd
Turn camera off, put it on photo mode with the switch button and turn it back on.
Go to the ML menu (trashcan button) -> go to raw video menu and set 'Preview' option to 'Framing'
Go to 'Debug' tab in ML menu and turn on the option 'ADTG register' (use set button to activate) go inside the ADTG registers options (use Q button)
Change 'show' to 'known regs only'
Click on advanced and turn on 'digic registers'.
Use half shutter press to go outside the ML menu.
Now switch the button to video mode and press the magnifying button a few times so you've seen all video options 1x, 5x and 10x zoom.
Now switch back to photo mode and look inside the 'adtg registers' menu again with the q button.
Now you'll see a lot of registers, which you can scroll to with the scrolling wheel.
All these registers have values, which can be overriden by using the 'set' button and entering a new value.
Now for those new values, see this spreadsheet and see the columns to the right:
https://docs.google.com/spreadsheets/d/1iapLI7UrgfCJGwPSFsyhYeKl8fSTY4RVXvDR7MiaOp4/edit#gid=0 (https://docs.google.com/spreadsheets/d/1iapLI7UrgfCJGwPSFsyhYeKl8fSTY4RVXvDR7MiaOp4/edit#gid=0)
once you've altered the registers with new values, switch back to video mode, don't be scared by the horrible live view you'll see now :P
and press the magnifying button a few times so you've been through all modes and stop at 5x zoom.
voila, new resolutions to work with.
P.S.
If the camera doesn't respond, doesn't give any moving live view, gives error 70 or 80 etc. just switch it off and take out the battery
I've fiddled many hours with adtg_gui and have seen some horrible things happening to the live view, but battery pull always saved the day (and the camera).
Even sometimes have seen that after a battery pull, live view still was flickering or had projections of text on the display, but that disappeared after a few minutes...
Like I said, not for the faint hearted ;D
@Danne, find out a workflow for horizontal resolutions that probably works for all camera's.
Can choose any horizontal resolution you want, but if affects the framerate.
When you have adtg_gui enabled, go to photo mode and take a picture, now all registers have the values used for full sensor readout. (photo mode opens up the full sensor and uses the physical shutter for shutter time)
As you maybe already know, the 6804 register holds the values for horizontal and vertical resolutions separated by a '0' or actually, the vertical value comes first and the horizontal value are the numbers after the 0.
And this probably goes for all cams, these horizontal values are close, near to the A timer values 6010, 6008 and 600c (and 6824, 6828, 68c2 & 6830).
Now what you do is, enable adtg_gui as you would do normally (also with digic registers 'on') and take a picture in photo mode (no live view).
now look at the values for:
6804 (especially the values that comes after the '0', they represent the horizontal resolution).
And the A-timer values:
6010
6008
600c
and maybe 6824, 6828, 68c2 & 6830 (visible in 'image size regs only')
Now switch to video mode and open adtg_gui, alter the part after the '0' in 6804 for the value that you have seen in photo mode and override all the A timers also with 'photo mode' values:
6010
6008
600c
and maybe 6824, 6828, 68c2 & 6830 (visible in 'image size regs only')
When I did this I had a full sensor width video mode with 5x zoom vertical resolution (had to alter the CMOS 6 and 7 settings to get correct live view preview)
Now when you have this, you can alter the horizontal resolution to whatever you like.
6804 has 3 values after the '0'.
Just change the middle value from the 3 values after the '0'.
If you change that middle value 8 times higher, do the same for the middle number values for all the A-timers.
If you change it to 4 clicks lower, do the same for the A-timers.
Do you see, they're connected, and the numbers are hexadecimal so the middle number from a 3 valued number gives increments or decrements of 16 pixels (x column factor used in cam).
Thanks for sharing methodology. Getting there one piece at the time. Ok, following the steps I am able to get all registers mentioned:
Photo mode(100D):
Resolution
COFO6804 0X4a701d7
A timer values
COFO6008 0x57b057b
COFO600c 0x57b057b
COFO6010 0x57b
Image regs only
6824 0x56a
6828 0x56a
68c2 0x56a
6830 0x56a
I add them to my lazy short cut and run the registers in movie mode:
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x53902a1; /* 2520x1304 24.006fps 14-bit lossless */
/* return 0x50802a1; 2520x1248 24.006fps 14-bit lossless */
case 0x6008:
return 0x57b057b;
case 0x600c:
return 0x57b057b;
case 0x6010:
return 0x57b057b;
case 0x6824:
return 0x56a;
case 0x6028:
return 0x56a;
case 0x68c2:
return 0x56a;
case 0x6830:
return 0x56a;
}
}
}
Getting 15 fps anf a frozen screen. I assume this is the heart of the matter but mre registers needed here to get viewable image:
How do you find the other registers needed? Bilal has them all in his spreadsheet:
https://docs.google.com/spreadsheets/d/1TzPxh7ai5JAoEI8zllaiiF1IDF5tAQam2BKRujyIYQU/edit#gid=0
- THE VALUES IN THIS CONVERSATION ARE FROM THE 100D -
Probably getting wrong with the used value for 6804 register:
Quote
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x53902a1; /* 2520x1304 24.006fps 14-bit lossless */
As said, the first three combinations are vertical resolution and the three combinations after the '0' are horizontal resolution.
value 53902a1 translates to
539 0
2a1 539 (hexadecimal) = 1337(decimal) vertical pixels
2a1 (hexadecimal) = 673 (decimal) horizontal pixels, as I see the numbers my guess is your camera has also 4 columns readout, 673 x 4 = 2692 pixels.
Now you've found this value for 6804 in photo mode:
4a701d7
4a7 (hexadecimal) = 1191 (decimal) vertical pixels (which is not as much as I expected ??? , would expect whole vertical sensor like 3000 something )
1d7 (hexadecimal) = 471 (decimal) horizontal pixels, 471 x 4 columns = 1884 (which is not as much as I expected ??? , would expect whole horizontal sensor value like 5000 something)
A timers are related to horizontal resolutions and must always be a higher number then the horizontal value in 6804
y
our A timers have value 57b(hexadecimal) = 1403 (decimal), which is higher then horizontal value, but not higher then full sensor width (5000 something).
So the values you have right now at the moment are not the ones you want.Forget to use column factor, seems that your A-timers have right value, 57b(hexadecimal) = 1403 (decimal) x 4 = 5612 pixels, that looks right!
So you have the correct values for all the A-timers 8)
To get the values for full sensor photo mode I turn my camera on in photo mode,
without live view enabled and turn adtg_gui to on and set digic registers on.
After that I press the shutter button and look into adtg_gui for the values
(be sure to have not used live view or image preview or something, hmmm I have set image preview to off in Canon menu, maybe that messes up your values :-\ )Now when you have the proper values for photo mode, you have to combine the horizontal resolutions from photo mode, with the vertical resolutions from 5x zoom mode.
So let's say you had proper values for photo mode for 6804, so 4a701d7 and normally you are using 53902a1 for 6804.
That would make a combined 6804 = 53901d7
@Danne, you're on a Mac, right.
For hexadecimal to decimal values you can use plain calculator app:
http://osxdaily.com/2015/06/14/access-scientific-programmer-calculator-mac-os-x/ (http://osxdaily.com/2015/06/14/access-scientific-programmer-calculator-mac-os-x/)
Set it to 'programmer' mode and use the three buttons at the right (8, 10 and 16) set it to 16 for hexadecimal input or on 10 for decimal input.
If you set it to 16 and type in a value and press the 10 button for decimal settings, it recalculates the value.
Sorry, may register for resolution was in fact:
case 0x6804: /* C0F06804 - raw resolution */
return 0x4a701d7;
The issue now is I get only a frozen image and can´t get out of it. Will look att your workflow description regarding timers.
Ehm nice tip on the calculator dude.
- THE VALUES IN THIS CONVERSATION ARE FROM THE 100D -
In that case try this value for 6804
53901d7 (Combined value from the vertical resolution from what you're normal using and the horizontal resolution value what you get from photo mode)
In combination with the A-timer values you found.
If live view freezes, most of the times the A and B timers do not match with resolution settings in 6804.
If ML live view framing preview works, but looks scrambled, try changing the last character of the 6804 combination, so 53901d7 -> 53901d8 (1 value up) or 53901d6 (1 value down). Try more values up and down, the last character determines if ML raw framing preview looks perfect or scrambled
Not scrambled, only frozen, tried the suggested value with same result. Also tested with image review to of in photo mode and got a new 6804 number(still frozen youghurt screen):
case 0x6804: /* C0F06804 - raw resolution */
return 0xdcf0541;
Getting 5208x3496 selected but frozen
- THE VALUES IN THIS CONVERSATION ARE FROM THE 100D -
Ah now we're getting somewhere :)
6804 in photo mode = dcf0541
Now combine this one with the one you're always using:
So try new value for 6804 = 5390541
Giving you in fact the vertical resolution you otherwise had, about 1300 pixels and the horizontal resolution from full sensor width, a little less then 5380
Should work I guess :D
Still frozen after setting this 8):
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0x5390541;
case 0x6008:
return 0x57b057b;
case 0x600c:
return 0x57b057b;
case 0x6010:
return 0x57b057b;
case 0x6824:
return 0x56a;
case 0x6028:
return 0x56a;
case 0x68c2:
return 0x56a;
case 0x6830:
return 0x56a;
}
}
}
Must be som other registers that needs to be set here. Fps at 16fps...
- THE VALUES IN THIS CONVERSATION ARE FROM THE 100D -
Probably the vertical value of 539 doesn't work, I bet that's already tweaked for more resolution.
What is the value of 6804 in plain vanilla crop mode ?
Put on adtg_gui and digic registers on, but do NOT load any preset in adtg_gui, do not override a single register.
Now go to video mode 5x zoom / 1:1 crop mode and lookup the value of 6804 in adtg_gui.
Now use the first 3 characters of this value and use the other values from photo mode, hopefully that works 8)
case 0x6804:
return 0x45802a1
Still frosty:
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0x4580541;
case 0x6008:
return 0x57b057b;
case 0x600c:
return 0x57b057b;
case 0x6010:
return 0x57b057b;
case 0x6824:
return 0x56a;
case 0x6028:
return 0x56a;
case 0x68c2:
return 0x56a;
case 0x6830:
return 0x56a;
}
}
}
Hmm, maybe add these registers:
8000 set to value 5
800c set to value 0
800c is the lineskipping value, which is already 0 in crop mode, but not in 1080p, my experience is that the camera is more stable while fiddling with these registers if it's already set to 0.
And I see I have altered CMOS 6 and 7.
CMOS 6 is set to 0
CMOS 7 is set to 163, but that is something to try and error on your camera.
Thanks for trying :). Still frozen. Think we need another approach, maybe checking bilals registers and I think I have it working with 3k so maybe take it from there.
3096x1320 20fps as high as I can get with a usable image:
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x280; /* CMOS[5]: ISO related? */
case 7:
return 0xa89; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804: /* C0F06804 - raw resolution */
return 0x5490331; /* 2904x1320 20fps 14-bit lossless */
case 0x6824:
return 0x3ca;
case 0x6828:
return 0x3ca;
case 0x682c:
return 0x3ca;
case 0x6830:
return 0x3ca;
case 0x6008:
return 0x37b037b;
case 0x600c:
return 0x37b037b;
case 0x6010:
return 0x37b;
case 0x6014:
return 0x6d7;
case 0x713c:
return 0x555;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0x7f4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x77c; /* without this, you get some weird artifacts; this should only go to ADTG2, not 4 */
case 0x8178:
return 0x77c;
}
}
}
Mostly Bilals register settings.
https://docs.google.com/spreadsheets/d/1TzPxh7ai5JAoEI8zllaiiF1IDF5tAQam2BKRujyIYQU/edit#gid=0
Edit: Got another one working 4056x2552 9fps:
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x200; /* CMOS[5]: ISO related? */
case 7:
return 0xf20; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0xa1b0421; /* 4056x2552 9fps 14-bit lossless */
case 0x6824:
return 0x4ca;
case 0x6828:
return 0x4ca;
case 0x682c:
return 0x4ca;
case 0x6830:
return 0x4ca;
case 0x6008:
return 0x45b045b;
case 0x600c:
return 0x45b045b;
case 0x6010:
return 0x45b;
case 0x6014:
return 0xbd4;
case 0x713c:
return 0xa55;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0xbf4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x8fd;
case 0x8178:
return 0x8fd;
}
}
}
Great not far away for Full-Res LiveView with the benefit of higher shutter speed - though ADTG gui still hangs for me in Liveview.
Try turning off global draw. Totally kills the workflow over here otherwise.
Can't get full resolution live view working on 6d. buffer is too small at the moment.
Got an error when I tried to record, image size is about 35Mb and image buffer is restricted to 20Mb or so I believe.
Image buffer size is set in MLV_lite.c or Raw.c not sure, Alex made the buffer for 5d3 bigger for some crop_rec options I read somewhere in Crop_rec.c in the comments I think.
Quote from: Danne on June 20, 2018, 02:14:28 PM
Edit: Got another one working 4056x2552 9fps:
if (is_camera("100D", "1.0.1"))
{
if (regs[reg].dst == DST_CMOS)
{
switch (regs[reg].reg)
{
case 5:
return 0x200; /* CMOS[5]: ISO related? */
case 7:
return 0xf20; /* CMOS[7]: ISO related? */
}
}
if (regs[reg].dst == 0xC0F0)
{
switch (regs[reg].reg)
{
case 0x6804:
return 0xa1b0421; /* 4056x2552 9fps 14-bit lossless */
case 0x6824:
return 0x4ca;
case 0x6828:
return 0x4ca;
case 0x682c:
return 0x4ca;
case 0x6830:
return 0x4ca;
case 0x6008:
return 0x45b045b;
case 0x600c:
return 0x45b045b;
case 0x6010:
return 0x45b;
case 0x6014:
return 0xbd4;
case 0x713c:
return 0xa55;
}
}
else if (regs[reg].dst == 2) /* ADTG 2 */
{
switch (regs[reg].reg)
{
case 0x82b6:
return 0xbf4; /* it's 5 in zoom mode and 6 in 1080p; this also overrides ADTG4 */
case 0x8172:
return 0x8fd;
case 0x8178:
return 0x8fd;
}
}
}
Makes a great starting point.
Use this one as base settings and do the following
In register 6804 increase the second last character one value at the time
Do the same for 6008, change both middle characters one value at the time
So 6804 = a1b0421 -> increase the second last character, in adtg_gui, one value up -> a1b04
31
And do exactly the same for 6008.
6008 = 45b045b -> change the middle characters -> 4
6b04
6b
As long as you do the same increments to both the character values of 6804 and 6008 nothing should break the live view/preview.
Doing that tiny change causes corruption/hiccups straight away.
I assume all of these change(yes tested both scenarios):
case 0x6804:
return 0xa1b0431;
case 0x6008:
return 0x46b046b;
case 0x600c:
return 0x46b046b;
case 0x6010:
return 0x46b;
I must say Bilals numbers are very solid working. I only changed:
case 0x6804:
return 0xa1b0422;
to:
case 0x6804:
return 0xa1b0421;
and working in 4056x2552
Makes sense, 100d and 700d probably have the same sensor, or at least the same sensor dimensions in megapixel.
Got something new to play with for the 6d, crop_rec module with 5192 x 632 @ 25fps for the 6d.
Many thanks to everyone who helped, MK11174, Danne, ofcourse Alex and probably many more.
Download it here, 'Crop_rec.mo', and put it in your ML/modules/ directory on your SD card.
https://drive.google.com/open?id=1bPT3waaGABlrcwciaOUDbhNhPp_eBuFU (https://drive.google.com/open?id=1bPT3waaGABlrcwciaOUDbhNhPp_eBuFU)
And for those interested, here's the source:
https://drive.google.com/open?id=1bJQpCEK_iknKxfwAAvnpvJLbQ7a2iDus (https://drive.google.com/open?id=1bJQpCEK_iknKxfwAAvnpvJLbQ7a2iDus)
Not sure with what builds this module works, but it works for sure with latest experimental crop_rec 4k build for 6d(see ML homepage->download->experiments)
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/75/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jun20.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/75/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jun20.6D116.zip)
SOUND RECORDING WITH MLV_LITE IS IN THIS BUILD AS IT USED TO BE, ON A SEPERATED TAB IN ML MENU
Short tutorial:
Copy the 'Crop_rec.mo' file in the 'ML/modules/' directory on your SD card.
Turn camera on and enable 'crop_rec' module in the 'modules' tab in ML menu.
Turn camera off and on again to see the option 'Crop mode' in the movie tab of ML menu, don't turn crop_mode on yet...
First go to raw video menu and set resolution with the set button to '5796'.
As data format select 14 bit lossless (12bit lossless and 11-8 bit lossless aren't working in crop_mode, they give corrupted frames)
Preview can be set to 'Framing' (live view is broken in crop_rec mode, but ML preview works fine)
Now go to video mode, press magnifying button 2 times, so you're in 5x zoom mode and now go to ML menu and enable Crop mode in ML movie tab, select the middle mode '2K 5192x632'.
Press half shutter to close ML menu and voila, 5196x632x25fps video mode.
Horizontal resolution can be lowered to whatever you like in ML raw video menu (highlight resolution and use scroll wheel to lower the resolution, to get for example 4096 or 3840 x 632 resolution.
If you want to squeeze out some extra performance, put 'preview' option in raw video menu to real-time. (Don't be scared how live view looks :P , use half shutter to get ML preview to check framing, while recording you can use a quick half shutter press to check framing, but for best performance, use half shutter press as little as possible.
Now as long as 'crop mode' is enabled in ML menu, live view is broken, also in 1080p mode.
So when 'crop_rec' is turned on and your turn off and on your camera, you will start up in 1080p mode, with broken live view, press magnifying button twice to enter 5x zoom mode and everything is fine.
Want to record in normal 1080p mode again, turn off Crop_rec option in ML menu.
Did notice something with the Crop_rec, shuttertime behaves a little weird.
The build works perfectly fine with 1/30th to 1/50th shutter time.
But when 1/60 is used, ML displays 1/150 shutter time and when 1/80th is used(as visible on top display) ML displays 1/3800 shutter time and ML preview looks quitte dark, so it is 1/3800th :P.
And when going to 1/100th, ML preview breaks and can't display a normal shutter time...
So for best results keep shutter between 1/30th - 1/50th setting.
EDIT: found the problem, disabled shutter blanking registers while debugging, will upload a new build.
Files in the link are updated, nothing wrong anymore 8)
Hello people with a 6d
Made some (crop) mode presets for the 6d.
My current build contains:
- 1824x1026 @ 35fps (for use in normal 1080p mode, no crop) - working Canon Liveview
- 2688x1166 @ 25fps (for use in 5x zoom crop mode) - working Canon Liveview
- 2880x1200 @25fps (for use in 5x zoom crop mode) - scrambled Canon Liveview, need to use half shutter to see ML preview fro framing
- 3840x1440 @12.5fps (for use in 5x zoom crop mode) - scrambled Canon Liveview, need to use half shutter to see ML preview fro framing
- 5192x634 @ 25fps (for use in 5x zoom crop mode) - scrambled Canon Liveview, need to use half shutter to see ML preview fro framing
Link to crop_rec module file:
https://drive.google.com/open?id=15Ar5OPVRHxJjFBSo72t2nTjYoEbJGuYL (https://drive.google.com/open?id=15Ar5OPVRHxJjFBSo72t2nTjYoEbJGuYL)
Sometimes I loose the half shutter ML preview option, not sure why that is ???
But turning the camera off and on(while in video mode) makes the ML preview work again, most of the times.
Unfortunately Crop_rec module only works with 14 bit lossless options, 12 bit lossless and lower gives corrupted frames(and is for that reason disabled in most cases)
Quote from: Levas on July 06, 2018, 08:32:05 PM
Sometimes I loose the half shutter ML preview option, not sure why that is ???
But turning the camera off and on(while in video mode) makes the ML preview work again, most of the times.
Yes this is happened for me a lot in 700D not sure why too :-\ .
After losing the preview, is there any error reported in the Debug tab?
It often happens when switching crop presets in liveview.
When it happens it shows a memory error in debug tab, 'No allocator for 675kb at tweak.c:3341, livev_hiprio_task.'
Did a small update on the crop_rec modes for 6d.
UHD has now more vertical resolution in exchange for fps, UHD is now 3820 x 2160 x 10 fps
And I changed the 5192x634 mode for a full resolution mode, 5472 x 3606 x 4.8 fps (expect about 1 frame recording time :P).
All modes are made for usage in 5 x zoom mode, except the first one, which is for use in normal non crop 1080p mode.
The crop_rec. mo file:
https://drive.google.com/open?id=1jB9Hl1nEhnGJ-Np6znQZ4e6j2Zlo_IHq (https://drive.google.com/open?id=1jB9Hl1nEhnGJ-Np6znQZ4e6j2Zlo_IHq)
(https://farm1.staticflickr.com/916/29402469838_f3864aee98_o.jpg)
Not bad Levas. Put your code out on bb so I can get some good summer reading over here 8).
Levas,
You seem to have fixed one of the most important features when filming at high resolutions - the ML preview. Congratulations!
@Danne, not that used to bitbucket.
Got the source here for you (sorry for the messy file :P )
https://drive.google.com/open?id=1Rnc8ooO3HI8IGA9wBCvU_3Om06GlmWGR (https://drive.google.com/open?id=1Rnc8ooO3HI8IGA9wBCvU_3Om06GlmWGR)
There's one thing though with the 35fps setting, I set the register so that it is for use in normal 1080p mode, not 5x zoom crop, but normal 1080p mode has not the good shutter times at the moment.
The sensor timing table with video modes doesn't have a column for 5x zoom mode:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg203306#msg203306 (https://www.magiclantern.fm/forum/index.php?topic=19300.msg203306#msg203306)
To fix shutter times in crop mode, I set values from zoom mode at the place of 1080p25.
I'm thinking of putting a 'switch' there in the code, where I put two sensor timing tables in it and let crop preset determine which table it uses.
@IDA_ML
Not sure what you mean with that I fixed ML preview ?
The ML preview is still 'gone' sometimes, but restarting the camera in video mode often does the trick.
Quote from: Levas on July 09, 2018, 12:51:16 AM
@IDA_ML
Not sure what you mean with that I fixed ML preview ?
The ML preview is still 'gone' sometimes, but restarting the camera in video mode often does the trick.
On the 100D (Danne's June 30-th build), real time preview works in the 2,5K crop mode and only at 5x magnification. In the 3,1 and 4K modes, preview is still scrambled and needs to be fixed. Your 6D build says "ML preview" even at the 4k and 5k modes. Does that really work as a WySiWyG preview, meaning you get correct framing during recording?
I also have another question. How many frames do you get recorded at the 2688x1166@25fps setting with a normally lit and exposed scene with the 6D and SD overclocking enabled?
@IDA_ML
Not sure how it is on the 100d, but I guess it's the same as on the 6d.
With 2688 x 1166 at 25 fps I have real-time live view (but indeed with 5x zoom, so not exactly WySiWyG, but at least centered.)
BUT if I do a half shutter press and hold it that way, I see the ML preview pop up on screen, which gives a WySiWyG framing, but the ML_preview is not that high in resolution and it's not real time fps but slower.
Once I have framed my shot, I quit half shutter press, and press record button.
When keeping the ML preview while recording it's slows down the camera which results in shorter recording times.
With the higher resolution crop_presets I have scrambled live view, but I can let normal ML_preview pop up with half shutter press.
It's this option in Raw video menu (Be sure that global draw is set to'ON all modes' in the overlay tab menu):
(https://farm2.staticflickr.com/1801/28427526047_64f8fc3ff8_o.jpg)
You could also choose for the option 'framing', that way it automatically does ML preview, so no need to hold half shutter press. but as said before, expect shorter recording times when ML_preview is used while recording.
About recording times on the 6d.
I found recently out that in video mode it does about 60 to 62 MB/s write speed(with SD_UHS hack). (always thought it was 70MB/s just as the benchmark in photo mode shows)
With 2688 x 1066 at 25 fps I get about 6 to 7 seconds of recording time.
But I'm planning to use that mode with 2560 x 1072 at 25 fps (1:2.39 aspect ratio)
That way I get 9 to 10 seconds recording time with 14 bit lossless and SD_UHS hack.
Would be cool if lower lossless bitrates could be fixed again.
Have tried to fix it with using the analog gain registers, which works, but the problem is it also affects the ML_preview. So not really usable for 10 bits lossless, image preview get's really dark :P.
Furthermore I couldn't fix the white level in camera, so has to be fixed in post proces.
I think the way to go is using the analog gain registers, but altering the crop_rec module to only enabling them while recording. Which is way out of my league for programming, just as fixing the whitelevels correct in camera.
Thanks a lot, Levas, for your comprehensive reply. I do hope that 10 and 12 bit lossless modes will work for us again soon so we can get longer recording times on our cameras.
By the way, did you try Dual ISO with your 6D at the 2688 x 1166 resolution? You will be blown away by the quality and full-frame vision!
New Crop_rec update for 6d:
Made the fast fps mode now for 720p mode only, this way I can go up to 50 fps in 1832 x 800 resolution. (1080p mode max frame rate is about 36/37 fps before liveview breaks)
Beware, when the 50fps preset is loaded in 1080p mode, your camera shuts down, error 70 or something, battery pull needed, so use it in Canon 720p50fps mode.
When preset is loaded, use magnify button to skip to all the zoom modes, to be sure all registers are activated, for use in normal mode, non zoom.
(https://farm1.staticflickr.com/924/41516280320_00df92ece7_o.jpg)
Download the module here:
https://drive.google.com/open?id=1k1unqwIcfGqtMS-Q42DFXb6W8LEB1CPo (https://drive.google.com/open?id=1k1unqwIcfGqtMS-Q42DFXb6W8LEB1CPo)
@Alex, I also managed to get 75 fps and 100 fps on the 6d, without soft bricking the camera!
But Canon live view is stuttery and slow (not smooth like 50fps), ML preview looks good, but once recording it's a mess, freezes frames/every second frame corrupted that kind of stuff.
How is that on the 5d3, could you get beyond 70fps, or did that soft brick the camera ?
100 FPS at some low resolution? Very cool! I wasn't able to go beyond ~ 65 FPS on 5D3; got image corruption even by just reducing the resolution without increasing the frame rate. Might be worth trying it on 60D.
Works only in 720p mode, in 1080p camera shuts down/soft bricks.
75 fps is in 1832 x 500something resolution, but as said, ML preview looks good, but recording not.
For 75 fps I use A timer of 0x203 (515 decimal) and B timer of 0x294(660 decimal)
Could also lower the A timer to get 100fps, but same problem, real stuttery canon live view, camera doesn't respond very quick on button presses.
But it didn't soft brick, so that's something :P
Looking for a full-res DNG captured from 6D, with any recent build where this feature works. Subject doesn't matter much, just looking for something decent enough to include in the QEMU test suite.
The full-res DNGs I already have from 6D (including the ones from VRAM dumps) have incorrect size. They are 5568x3708, but emulation expects 5568x3723. Older builds used to have this incorrect size hardcoded.
Here's a full-res silent DNG...not sure if it has the correct size, but it's made with a recent build.
https://drive.google.com/open?id=1uM6LoS8F9pOR8du4r7Bzl3cDnixPqXYa (https://drive.google.com/open?id=1uM6LoS8F9pOR8du4r7Bzl3cDnixPqXYa)
Almost there; one line of pixels missing, since the full image size is an odd number and ML rounds it to an even number. No big deal, I can fill it with something.
Hello everyone, I'm about to buy a 6D and I would like to know what is the res at 24 fps and 30 fps, I can get without the camera stop record after few sec. Thanks guy
Quote from: gsanchez922 on August 01, 2018, 05:03:34 PM
Hello everyone, I'm about to buy a 6D and I would like to know what is the res at 24 fps and 30 fps, I can get without the camera stop record after few sec. Thanks guy
Yes, you can do it with reduced resolution. I think 16xx will let you shot continuous in 10 bit.
Since the introduction of lossless raw recording things got better.
Canon 6D highest resolution for 16:9 aspect ratio is 1824 x 1026.
24 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 30 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 100 seconds recording time till buffer is full.
30 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 10 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 20 seconds recording time till buffer is full.
If you really want continuous recording times, you could lower resolution a little.
For 24 fps, 1728 x 972 resolution in 12 bit lossless should give about unlimited recording time (till battery is empty or card is full :P )
For unlimited recording time in 30 fps you need to lower resolution to 1600 x 900 and record in 12 bit lossless.
Another option instead is go wider then 16:9 aspect ratio.
For example 1:2.39 (which is very common aspect ratio for movies)
1824 x 764 x 24 fps x 14 bit lossless raw recording gives continuous recording time.
1824 x 764 x 30 fps x 12 bit lossless raw recording gives continuous recording time.
That said, if you really like to live on the edge, go buy a Sandisk extreme pro card and make use of the very experimental SD-UHS hack module, which makes it possible to get higher writing speeds, instead of about 40MB/s you can get 60+MB/s writing speed out of your Canon.
This makes it possible to get continuous recording in 1824 x 1026 x 14 bit lossless x 30 fps.
Quote from: Levas on August 02, 2018, 12:04:27 PM
Since the introduction of lossless raw recording things got better.
Canon 6D highest resolution for 16:9 aspect ratio is 1824 x 1026.
24 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 30 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 100 seconds recording time till buffer is full.
30 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 10 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 20 seconds recording time till buffer is full.
If you really want continuous recording times, you could lower resolution a little.
For 24 fps, 1728 x 972 resolution in 12 bit lossless should give about unlimited recording time (till battery is empty or card is full :P )
For unlimited recording time in 30 fps you need to lower resolution to 1600 x 900 and record in 12 bit lossless.
Another option instead is go wider then 16:9 aspect ratio.
For example 1:2.39 (which is very common aspect ratio for movies)
1824 x 764 x 24 fps x 14 bit lossless raw recording gives continuous recording time.
1824 x 764 x 30 fps x 12 bit lossless raw recording gives continuous recording time.
That said, if you really like to live on the edge, go buy a Sandisk extreme pro card and make use of the very experimental SD-UHS hack module, which makes it possible to get higher writing speeds, instead of about 40MB/s you can get 60+MB/s writing speed out of your Canon.
This makes it possible to get continuous recording in 1824 x 1026 x 14 bit lossless x 30 fps.
Thanks so Much
Quote from: Levas on August 02, 2018, 12:04:27 PM
Since the introduction of lossless raw recording things got better.
Canon 6D highest resolution for 16:9 aspect ratio is 1824 x 1026.
24 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 30 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 100 seconds recording time till buffer is full.
30 fps in 1824 x 1026 resolution:
In 14 bit lossless raw gives about 10 seconds recording time till buffer is full.
In 12 bit lossless raw gives about 20 seconds recording time till buffer is full.
If you really want continuous recording times, you could lower resolution a little.
For 24 fps, 1728 x 972 resolution in 12 bit lossless should give about unlimited recording time (till battery is empty or card is full :P )
For unlimited recording time in 30 fps you need to lower resolution to 1600 x 900 and record in 12 bit lossless.
Another option instead is go wider then 16:9 aspect ratio.
For example 1:2.39 (which is very common aspect ratio for movies)
1824 x 764 x 24 fps x 14 bit lossless raw recording gives continuous recording time.
1824 x 764 x 30 fps x 12 bit lossless raw recording gives continuous recording time.
That said, if you really like to live on the edge, go buy a Sandisk extreme pro card and make use of the very experimental SD-UHS hack module, which makes it possible to get higher writing speeds, instead of about 40MB/s you can get 60+MB/s writing speed out of your Canon.
This makes it possible to get continuous recording in 1824 x 1026 x 14 bit lossless x 30 fps.
Hello, im new with using raw. i got a Sandisk extreme pro 95mb and got around 7 sec in 24 fps 1824 x 1026 resolution 14 bit. which is pretty standard i guess with 40/41 mb.
Could you expand on how to get 30 sec?
also could you explain how to get in 12 or 10 bit mode?
PD: today i've updated magic lantern on my 6d (Nightly build july 3) and added a sd uhs module for the 6d but it give me a error
Thanks!
I see you're using the nightly build. Not sure if the nightly build has lossless raw and 12 bit option etc.
For the ultimate magic lantern :D experience, I suggest you try the 'crop_rec_4K' build for the 6d on the experiments page.
Go to the Magic lantern main page and under 'Downloads' you will see a submenu, choose 'experiments'.
https://builds.magiclantern.fm/experiments.html (https://builds.magiclantern.fm/experiments.html)
Scroll down to the '4K raw video recording; lossless compression' builds.
The name for the build is a little misleading, since a true 4K option, with at least 24fps, only exist on the 5dIII
Direct link to the 6d build:
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip)
This build has lossless raw options and lower bit depth options.
You can choose raw format within the raw video menu, using the 'q' button on your camera to acces the submenu.
The SD_UHS module doesn't work with all builds of Magic Lantern, but it should work with the crop_rec_4K build from the experiments page.
But I suggest you first try out stuff without the SD_UHS module, get a little feeling with raw video and raw lossless video.
After that you can still see if you really need it. Not sure if you already read the whole SD_UHS thread:
https://www.magiclantern.fm/forum/index.php?topic=12862.0 (https://www.magiclantern.fm/forum/index.php?topic=12862.0)
But it appears there is some little risk in corrupting your SD card, if not correctly used.
I've never encountered any problems with the SD_UHS module, but it is good to know there is some risk involved.
EDIT:
Be sure you enable and use the MLV_Lite module for raw recording, MLV_Rec module has no use in this build and is best not to be enabled.
The MLV_Lite module has the lossless and lower bit depth options for raw video.
Quote from: Levas on July 10, 2018, 08:19:23 PM
New Crop_rec update for 6d:
Hello , can you make 60fps preset?
Must have missed this request (Did go for a short vacation on the 20th august :P )
I can make a 60fps preset, but it will go at the cost of some vertical resolution.
For the 50 fps preset, the vertical resolution was lowered to 800 pixels, will take a look into it how much lower it will get with 60 fps.
I've used my own crop_rec presets on vacation for some testing.
It works, but once in a while the first 2 frames of a mlv file are corrupt (purple, broken etc). But the rest of the mlv is fine, so it is usable.
Also when this happens, console shows up giving a error message (probably because of the weird file size of the few corrupted frames at the start).
This is what I have for now:
(https://farm2.staticflickr.com/1841/42744528000_09886078d3_b.jpg)
You must be in the correct video mode to use the presets, use zoom button a few times to scroll to 5x zoom/ 10x zoom etc, to be sure all registers are altered.
When used in the proper video mode, shutter times are accurate and can even be expanded to 1/25000th of a second, depending on the crop_rec preset.
To get this full range shutter time option, use q button in ML menu on the crop_rec option, you get a sub-menu with 2 shutter range options, 'original' or 'full range'.
-1832x800 50fps 720p mode : This is for use in Canon 50 fps 720p mode, doesn't work in Canon 1080p modes, not for use in 5x zoom mode, but for normal standard view.
-1832x1230 35fps 1080p mode: This is for use in standard Canon 1080p, not for use in 5x zoom mode, but for normal standard view.
-2688x1166 25 fps liveview: This is for use in standard Canon 1080p, and must be used in 5 x zoom mode. This mode has working liveview, be it a centered crop of the actual framing. Use ml preview to see the actual framing (depending on your settings, this happens automatic, otherwise use half shutter press to see preview)
-2880x1200 25fps ML preview:This is for use in standard Canon 1080p, and must be used in 5 x zoom mode. liveview is scrambled/broken, use ML preview option to see framing (see ML raw video menu for preview options)
-3840x2160 10fps ML preview:This is for use in standard Canon 1080p, and must be used in 5 x zoom mode. liveview is scrambled/broken, use ML preview option to see framing (see ML raw video menu for preview options)
-5120x2142 8.3fps ML preview:This is for use in standard Canon 1080p, and must be used in 5 x zoom mode. liveview is scrambled/broken, use ML preview option to see framing (see ML raw video menu for preview options)
-5472x3604 4.8fps ML preview:This is for use in standard Canon 1080p, and must be used in 5 x zoom mode. liveview is scrambled/broken, use ML preview option to see framing (see ML raw video menu for preview options)
This last one can be used as a sort of electronic shutter photo mode, with the so called full shutter range option, you can use fast shutter times, be it with a little rolling shutter effect. The fun thing is, the writing speed with the 6d is about just enough to get 1 or 2 frames in this mode, before the camerabuffer is full and stops. :P
So it's a perfect silent electronic shutter photo mode ;D
I used these preset for a while and I like the 2688x 1166 25fps with liveview the most, and I think it is the most usable one, because it has working liveview.
Also writing speed of the 6d is not sufficient enough to get long recording times in 2880x1200 for example.
Most of the times I even lowered the resolution to about 2560 x 1072 to get longer recording times, or 2400x1004 resolution.
For now these crop_rec modes only work with the 14 bit lossless recording option, 12 bit lossless and lower don't work, because liveview resolutions are bigger then standard.
And finally, here is the crop_rec module file for download, put in on your SD card in the ML/MODULES folder, this module should work with the Crop_rec_4K build for 6d on the experimental builds download page.
https://drive.google.com/open?id=1-X2OB14zsZBKdvbJSQC6LokNOgMLXVQv (https://drive.google.com/open?id=1-X2OB14zsZBKdvbJSQC6LokNOgMLXVQv)
EDIT: these crop presets don't work that will with FPS override function. FPS override can be activated, but it could be that it destroys the usability of the resolution, so (random) corrupted frames.
FPS are sort of baked in, in these crop presets.
If people are looking for 24 fps crop presets, I can make a special 24fps crop_rec build with the above presets.
Quote from: Levas on September 08, 2018, 05:46:28 PM
Must have missed this request (Did go for a short vacation on the 20th august :P )
I can make a 60fps preset, but it will go at the cost of some vertical resolution.
For the 50 fps preset, the vertical resolution was lowered to 800 pixels, will take a look into it how much lower it will get with 60 fps.
I shoot 2.35 - 1 so it will be not a problem if resolution will be a little smaller. Thank you
Hi Ctfire,
Made a 60 fps crop_rec preset 8) - So 60 fps with square pixels, not the stretched stuff Canon gives us by default.
Takes some vertical resolution, probably more then you hoped for :P
The max vertical resolution is now 708 pixels.
So for shooting in 2.35 aspect ratio, you have to lower the horizontal resolution in raw video menu to 1664.
The horizontal resolution can be adjusted in increments of 16 pixels in raw video menu with the top scroll wheel on your camera.
But 1664 x 708 raw video still looks amazingly good.
While making this preset I find out that with 722 pixel vertical resolution, all frames are corrupted.
Going to 720 vertical resolution gave more good frames then corrupted ones, but still corrupted frames every second or so.
So I lowered the vertical resolution to 708 pixels, I think this will be safe concerning corrupted frames, but haven't tested it, preview on camera looks good, testing is up to you.
The crop_rec module file:
file removed
EDIT, Tested it, still corrupted frames, ML preview looks good, but recording is full with corrupted frames, let me take a look at it.
Made some adjustments, this one works better, first 2 or 3 frames at the start are corrupted, rest of the frames looks good, happy testing :D
New file:
https://drive.google.com/open?id=1GdRoSqgcbeE9CovsdtYlM4P2trzf1Tue (https://drive.google.com/open?id=1GdRoSqgcbeE9CovsdtYlM4P2trzf1Tue)
How it looks on camera:
(https://farm2.staticflickr.com/1851/43856553824_ce123d17a7_b.jpg)
Hi Levas. Is it possible to manipulate mv1080p setting for in example eos 100D to achieve higher fps? Right now it works with 42 fps but going beyond this corrupts the image.
Hi Danne
I only could get really high fps in 720p mode on 6d.
In 1080p mode, the Canon 6d softbricks by about 38 fps.
Which means the 720p mode is really different then 1080p mode.
I first thought it's all the same, just a bunch of registers tweaked, A and B timer, resolution and stuff...but apparantly there's more difference going on between 1080p and 720p mode
Cool, thanks
Quote from: Levas on September 09, 2018, 06:34:56 PM
Hi Ctfire,
Made a 60 fps crop_rec preset 8) - So 60 fps with square pixels, not the stretched stuff Canon gives us by default.
Takes some vertical resolution, probably more then you hoped for :P
The max vertical resolution is now 708 pixels.
So for shooting in 2.35 aspect ratio, you have to lower the horizontal resolution in raw video menu to 1664.
The horizontal resolution can be adjusted in increments of 16 pixels in raw video menu with the top scroll wheel on your camera.
But 1664 x 708 raw video still looks amazingly good.
While making this preset I find out that with 722 pixel vertical resolution, all frames are corrupted.
Going to 720 vertical resolution gave more good frames then corrupted ones, but still corrupted frames every second or so.
So I lowered the vertical resolution to 708 pixels, I think this will be safe concerning corrupted frames, but haven't tested it, preview on camera looks good, testing is up to you.
The crop_rec module file:
file removed
EDIT, Tested it, still corrupted frames, ML preview looks good, but recording is full with corrupted frames, let me take a look at it.
Made some adjustments, this one works better, first 2 or 3 frames at the start are corrupted, rest of the frames looks good, happy testing :D
New file:
https://drive.google.com/open?id=1GdRoSqgcbeE9CovsdtYlM4P2trzf1Tue (https://drive.google.com/open?id=1GdRoSqgcbeE9CovsdtYlM4P2trzf1Tue)
How it looks on camera:
(https://farm2.staticflickr.com/1851/43856553824_ce123d17a7_b.jpg)
Thank you a lot
Was fiddling with crop_rec module on 6d to see if I could get clear 72fps, didn't succeed :-\
But I did find out, that I had head 3 timer (register 713c) and head 4 timer (register 7050) not on optimal settings in my normal crop_rec presets.
This seems to be the reason why first 2 frames most of the times where corrupt and console text shows up often in my crop_rec builds.
So now working on a more stable crop_rec build for 6d, without the corrupted frames at start and console messages showing up.
But first I wanted to do some fun project, see how far I could get, resolution wise with 24fps instead of 25 fps.
I'll present to you, the CINEMA crop_rec module for 6d
(https://farm2.staticflickr.com/1867/44583161492_b4eed0747d.jpg)
For full resolution of the presets set aspect ratio to 3:2 in ML raw video menu.
Expect about 2 to 3 seconds of recording times in these high resolution settings (Some more with the SD_UHS overclock module).
For longer recording times, lower video resolution in ML raw video menu (use top scroll wheel to adjust), ofcourse different aspect ratios can be set within the raw video menu.
Presets are for use in 5x zoom mode. for best recording times, set preview option in ML raw video menu to 'Real-time' and use half shutter press to see framing/preview.
Link to module file:
https://drive.google.com/open?id=1eQIy9Z8A6-Z-YXH-q2lLB8nc6LrkEffI (https://drive.google.com/open?id=1eQIy9Z8A6-Z-YXH-q2lLB8nc6LrkEffI)
Levas,
Would it be possible to increase the vertical resolution of Vista vision by another 56 pixels to get 1440 and 16:9 aspect ratio? Adding SD-card overclocking and 10-bit lossless to get 10-12 sec. of recording time will make a hell of a full-frame video camera out of the 6D !!!
Unfortunately 1440 was not possible without corrupted frames.
Otherwise I would have picked that resolution, 2560x1440 16:9.
96 fps on the 6d :D
https://www.magiclantern.fm/forum/index.php?topic=19300.msg206034#msg206034 (https://www.magiclantern.fm/forum/index.php?topic=19300.msg206034#msg206034)
Guys I want to test 12 bit loseless comp along with dual iso on my 6D but when I turn on dual_iso.mo it gives me ISOless PH err(3)
I tried to take a working dual iso module from the latest nightly build but when I activate it says old api version 6 , 7 expected
I read this post below but I dont know how to edit .mo file I opened it on notepad++ and it was encrypted
and yes I have no idea about coding ::)
Quote from: Sapporo on May 24, 2018, 11:32:08 AM
Tried this with my 6D which I bought in Japan. Frame CMOS I changed to 40e6190 and photo CMOS I changed to 404e4e06. Still ISOless PH 3. Only Magic-Lantern-4k crop mode has the issue. Not the Nightly build.
EDIT: It works! It was only me who didn't read everything. New values in CMOS 3 and not CMOS 0:
404e61b6
and
404e4e08
Had the same error, fixed like described in the post you quoted.
Thry this dual_iso.mo file and replace it with the dual_iso.mo file already on your SD card.
https://drive.google.com/open?id=10eLbNnEZN9I6o6L8T5tKUboCwqMOTnYF (https://drive.google.com/open?id=10eLbNnEZN9I6o6L8T5tKUboCwqMOTnYF)
Quote from: Levas on September 20, 2018, 05:38:08 PM
Had the same error, fixed like described in the post you quoted.
Thry this dual_iso.mo file and replace it with the dual_iso.mo file already on your SD card.
https://drive.google.com/open?id=10eLbNnEZN9I6o6L8T5tKUboCwqMOTnYF (https://drive.google.com/open?id=10eLbNnEZN9I6o6L8T5tKUboCwqMOTnYF)
Thanks for your help dude :D
well, I tried it and it worked on camera but when I export it from mlvapp v1.0 with dual iso option on it gives me a moving stripes video like how live view see when dual iso is on and random green frames I don't know what's wrong
*update: It works perfectly with14-bit & 14bit lossless
if I choose 12 or 10 bits or lossless ones they make the same issue
btw I'm impressed for your high fps research you're going to make something revolutionary!
Never tried dual iso with lower bit depths, will see if I can test it today and see what happens in MLVapp.
Quote
btw I'm impressed for your high fps research you're going to make something revolutionary!
Thanks, I'm just changing small stuff in the crop_rec source code provided here on Magic-Lantern site, the basics are provided by others.
Will share the 96 fps build if I have made a little tutorial for it, it's a bit buggy compared to standard raw video recording with ML :P
There is a lot of talk lately about 1x3 mode, basically binning 3 pixels on horizontal lines and reading every vertical line, no line skipping.
https://www.magiclantern.fm/forum/index.php?topic=22818.msg206134#msg206134 (https://www.magiclantern.fm/forum/index.php?topic=22818.msg206134#msg206134)
So made a crop_rec preset with this 1x3 mode for 6d, 25fps (for use in non zoom mode, no need to go to 5x zoom):
(https://farm2.staticflickr.com/1930/44120120494_6fbc7f7ce6_o.jpg)
To get highest possible height, select aspect ratio of 2:1 in raw video menu.
After resizing the video to 1/3 of it's original vertical size, you get about 614 pixels resolution.
So for end results in 2:35 aspect ratio, you can set raw video menu to 1440x1842 resolution -> which gives resized in post 1440 x 614 effective resolution.
1440x1842 in 14 bit lossless gives about 5 seconds recording time.
Couldn't get higher then 1842 without getting corrupted frames, so for now, looks like 1842 is the max vertical resolution in 25fps.
Crop_rec module file, to be added on your SD card in ML/modules/ directory:
https://drive.google.com/open?id=1WkMtQIAqVonJFASYQrbvnBeFH8VzDICI (https://drive.google.com/open?id=1WkMtQIAqVonJFASYQrbvnBeFH8VzDICI)
So to be clear.
There is no way to record 2.35:1 raw video even at 10 or 12 bit?
What should the basic Canon video resolution be set at?
No, the 6D is perfectly capable in recording 'normal' raw video in 2.35 aspect ratio.
The latest post I send is about recording in 1x3 mode, in 1x3 mode, every vertical line is recorded, no lineskipping is done.
While horizontal pixels are binned by 3.
The end result is a weird vertical stretched video which needs to be fixed in post, vertical size needs to be unstretched by factor 3.
For 'normal' raw recording the best builds for 6d is the build on the download page with experiment builds:
4K raw video recording; lossless compression
https://builds.magiclantern.fm/experiments.html
This build contains also lossless recording option.
6d gives you a max resolution of 1824 in normal non zoom mode, so in 2.35 aspect ratio = 1824x776 resolution.
With 14 bit lossless option, this should give you continuous raw recording.
Hello everybody, i got a problem here, when i install and use 10/12 bit raw video build, i got a black first frame in dng sequences. it`s very uncomfortable in work, because this black frame i see in preview in resolve but not what i shoot. In other builds all fine, but want try 10bit. Help please!) sorry for my english)
(https://thumb.ibb.co/fb6nte/preview.jpg) (https://ibb.co/fb6nte)
I have such issue with crop mode shots. First frame is always black.
Are you using the nightly build or an experimental build ?
Try the crop_rec_4k build for 6d (doesn't do 4k on 6d...but this build has lossless compression option :) ) on the experimental builds download page.
14 bit lossless is probably even smaller in most situations then non lossless 10 bit.
Didn't notice black DNG's at the the start of a MLV with this build.
Direct link:
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip)
Yes, i used experemental build. ok i try 4k build.
Quote from: Levas on September 26, 2018, 09:05:16 AM
No, the 6D is perfectly capable in recording 'normal' raw video in 2.35 aspect ratio.
The latest post I send is about recording in 1x3 mode, in 1x3 mode, every vertical line is recorded, no lineskipping is done.
While horizontal pixels are binned by 3.
The end result is a weird vertical stretched video which needs to be fixed in post, vertical size needs to be unstretched by factor 3.
For 'normal' raw recording the best builds for 6d is the build on the download page with experiment builds:
4K raw video recording; lossless compression
https://builds.magiclantern.fm/experiments.html
This build contains also lossless recording option.
6d gives you a max resolution of 1824 in normal non zoom mode, so in 2.35 aspect ratio = 1824x776 resolution.
With 14 bit lossless option, this should give you continuous raw recording.
how you get this? i use sandisk extreem pro 95mb/s and i got only 12-14 seconds in 1824x776 24p 14bit, 10bit continuous.
For continuous you need lossless option (available within raw video menu)
So normal 14 bit gives about 14 seconds, but 14 bit lossless gives continuous.
You need the ML build I linked in the post, it's on the dowloadpage under experiments.
Lossless option is in MLV_Lite module, not sure but I think it's not in MLV_rec module.
So enable MLV_lite module and disable MLV_rec module.
Hello I have a 6d with 1.1.7 and before putting ML I would like to know if with ML I can record video at 1080p 50p or more. Thank you very much
Nope not exactly possible.
Max resolution for 6d in 50fps is about 1824 x 800.
You can shoot about 5 seconds in 14 bit lossless raw format in 50fps before the memory buffer is full and the camera stops recording.
For 16:9 aspect ratio, you can lower the resolution to 1440 x 800, this will give you about 600 frames before the camera stops, so about 11 seconds.
Hello guys. Using 6D for seseral years but only 2 days ago heard about ML. I have 2 issues with my 6D.
1) Camera doesn`t support continuos autofocus during video record, so I should stay still and can`t move when I record my vlog.
2) Camera doesn`t support video record when wifi on. So I can`t focus on myself through Android App on smartphone - I need to ask help for someone else to focus camera on me.
Does ML solve these or one of these issues? Thanks in advance.
No.
Never used it, so not sure how responsive it is and if it works with all lenses or only STM, but the Canon 6d has a autofocus mode called 'live face detect mode' which works during video recording.
Sounds like it should work for vlogging
https://www.youtube.com/watch?v=UD2iIlki3XE (https://www.youtube.com/watch?v=UD2iIlki3XE)
The long answer for no video support when wifi is on is, that it probably shares a DMA channel with the video encoder.
So it's not a software restriction but a hardware restriction...
https://www.magiclantern.fm/forum/index.php?topic=4704.0 (https://www.magiclantern.fm/forum/index.php?topic=4704.0)
Thanks guys! i fixed the problem. I deleted then instal ML again and it`s work properly. No black frame!! In menu "modules" i choose mlv. ver.2 module. Tried 4k build but it work bad.
Quote from: Levas on September 22, 2018, 01:50:42 PM
So made a crop_rec preset with this 1x3 mode for 6d, 25fps (for use in non zoom mode, no need to go to 5x zoom):
(https://farm2.staticflickr.com/1930/44120120494_6fbc7f7ce6_o.jpg)
Here stupid questions comes :D
should I set canon menu video to 1080p or 720p?
Am I able to use this for 16:9 final result video?
when I set ratio to 2:1 1832x912 and 1824x912 is maximum resolution I could choose is that normal?
on RAW video option it says "1824x912 3.00x" does that mean I got a 3x crop factor? what if I want to use that as 1.0x (entire full frame)?
I tried to shoot a test but I got some trouble judging stretching after trying to get it natural unstretched looking.
excuse my low IQ it's all very confusing ::)
can't wait to test your high fps preset ;)
For slow mode 50p you've to switch to 720p (expect massive aliasing) and than stretch footage vertically by x1.69 in post.
x3 is a crop mode w/o aliasing and moire for regular footage 24/25p
Quote from: Karim on November 12, 2018, 05:39:28 AM
should I set canon menu video to 1080p or 720p?
You should set it to 1080p and use it in normal mode (not 5x zoom as some other presets)
Quote from: Karim on November 12, 2018, 05:39:28 AM
Am I able to use this for 16:9 final result video?
when I set ratio to 2:1 1832x912 and 1824x912 is maximum resolution I could choose is that normal?
on RAW video option it says "1824x912 3.00x" does that mean I got a 3x crop factor? what if I want to use that as 1.0x (entire full frame)?
It's indeed a bit fiddley :P
For maximum resolution use 1:2 ratio (not to be confused with 2:1), it's important to have the right aspect ratio, otherwise you can't select the maximum vertical resolution.
The cops_rec preset I made are not (always) completely loaded/set when you select them, it's always good to use magnifying button to scroll through 1x, 5x and 10x zoom until back to normal view.
That way everything is set, some say pressing menu button twice works too.
16:9 end result is possible, although in a very low resolution, because after unstretching the maximum resolution of 1842, you end up with a vertical resolution. of 1842 / 3 = 614 pixels.
614 / 9 x 16 = 1092 horizontal resolution for 16:9 ratio.
So if you lower the resolution in raw video menu to 1092 x 1842, you can end up after unstrecthing with 1092 x 614 = 16:9 video.
Quote from: Karim on November 12, 2018, 05:39:28 AM
I tried to shoot a test but I got some trouble judging stretching after trying to get it natural unstretched looking.
If you've got it working, you will know and see that it is stretched. You must make the vertical resolution 3x smaller, in software on computer, to get normal looking video
Quote from: Karim on November 12, 2018, 05:39:28 AM
can't wait to test your high fps preset ;)
Good to hear, didn't work on that much anymore. Still a little in doubt if I should upload it, because it's not that robust (prepare to get an occasional error 70 on your display and to pull out the battery to get rid of this error :P)
But I'll try to upload it later on the day, with some instructions
Hello I have a 6D with 1.1.7, I have installed 1.1.6 from here and installed ML but it doesn't work, the ML menu doesn't show up when I press Q, when I go to video on the screen appears shortcuts for iso and WB but that's it. I have uninstalled ML and installed again but it still doesn't work, I have searched the forum but I haven't found anything about this problem. I have a Tamron 24-70 f2.8 lens and 32 Gb Sandisk Card and the original battery. Do you have any ideas what could be wrong?
Hi - quick question for anyone who uses the crop_rec module with the 6D:
The 1824x1026 (24p) resolution that is listed to be the maximum resolution with lossless compression; I am only able to achieve this in 12-bit lossless mode. Was anyone able to achieve this resolution continuously with 14-bit lossless?
Sounds like normal behaviour.
1824x1026 in 14 bit lossless is not continuous.
1824x1026 in 12 bit lossless is continuous.
Card writing speed from 6d just isn't fast enough.
You can get continuous in maximum resolution in 2.35 aspect ratio though.
OR(if you like to go bleeding edge)
You could make use of the SD_UHS hack module.
Which improves card writing speed on 6d by about 150% :D
Giving you continuous recording in 1824x1026x24fps in 14bit lossless.
More about it in this post:
https://www.magiclantern.fm/forum/index.php?topic=15088.msg205032#msg205032 (https://www.magiclantern.fm/forum/index.php?topic=15088.msg205032#msg205032)
Thanks Levas,
After using the SD_UHS hack module, I was able to achieve continuous 1824x1026 14-bit lossless!
Strangely enough however, following this test, I switched over to a different SD card that did not have the SD_UHS module, and was STILL able to achieve 1824x1026 14-bit continuously??? Don't know how this voodoo magic happened, but I'll take it. :D
Another quick question:
Anyone able to use crop_rec, lossless compression, and the dual ISO module all in conjunction?
I get an "ISOless LV err(3)" whenever I try and activate Dual ISO.
Searching the forums, I've seen a workaround involving the adtg_gui.mo and changing the values in CMOS [3] in dual_iso.c , but I am afraid I am not educated enough on the details to do this?
Any help would be great, thanks!
Quote from: Tyronetheterrible on November 23, 2018, 08:47:11 PM
Strangely enough however, following this test, I switched over to a different SD card that did not have the SD_UHS module, and was STILL able to achieve 1824x1026 14-bit continuously??? Don't know how this voodoo magic happened, but I'll take it. :D
The lossless compression is variable, it works better in low light scenes(underexposed) and scenes with less detail, so if you underexpose it compresses more, also using higher iso can cause compression to be less due to false detail created by iso noise.
And max resolution in 16:9 (1824x1026) in 24 fps in 14 bit lossless floats around the maximum card write speed of the 6d.
So depending on the scene and iso usage, you're sometimes lucky, sometimes not :P
Quote from: Tyronetheterrible on November 23, 2018, 08:58:13 PM
I get an "ISOless LV err(3)" whenever I try and activate Dual ISO.
Searching the forums, I've seen a workaround involving the adtg_gui.mo and changing the values in CMOS [3] in dual_iso.c , but I am afraid I am not educated enough on the details to do this?
I've had the same error, and made the changes in dual_iso.c, compiled the file and it works on my 6d, this is the dual_iso.mo file:
https://drive.google.com/open?id=1l_DgNZH6Gh_rqQeXOme-kV6XGrvMcMC1 (https://drive.google.com/open?id=1l_DgNZH6Gh_rqQeXOme-kV6XGrvMcMC1)
Big chance it works on your 6d, but also a small chance that you still get the same error, since it appears to differ per model 6d ???
It worked! :D
Thank you for being so helpful, Levas!
Quote from: BlueNinja on November 17, 2018, 07:43:39 PM
Hello I have a 6D with 1.1.7, I have installed 1.1.6 from here and installed ML but it doesn't work, the ML menu doesn't show up when I press Q, when I go to video on the screen appears shortcuts for iso and WB but that's it. I have uninstalled ML and installed again but it still doesn't work, I have searched the forum but I haven't found anything about this problem. I have a Tamron 24-70 f2.8 lens and 32 Gb Sandisk Card and the original battery. Do you have any ideas what could be wrong?
Any ideas please?
ML menu doesn't show up on pressing "Q". Try trashcan button.
Quote from: Walter Schulz on November 26, 2018, 07:02:08 PM
ML menu doesn't show up on pressing "Q". Try trashcan button.
Thank you, that worked :)
Is 1920x1080 or similar res possible with 2x2 binning? I just discovered the resolutions in 5x zoom mode and the quality is perfect but the crop factor is too much.
First someone has to find out how to do 2x2 binning with Canon cams.
Maybe the question I should be asking is how does one get the best possible raw video from the 6D at 1920x1080 or similar while using a significant portion of the sensor?
The problem I'm having is false color along sharp horizontal edges.
The question you should asking is, how do I get rid of false color ;)
See this post:
https://www.magiclantern.fm/forum/index.php?topic=19300.msg206100#msg206100 (https://www.magiclantern.fm/forum/index.php?topic=19300.msg206100#msg206100)
If the MLV to dng to rawtherapee to tiff sequence to your video editor of choice is too much work, you can give MLVapp a try.
It doesn't have the defringe option, but there are versions of MLVapp which support the LMMSE debayering, which gives much less false color as the more used AMAZE debayering.
https://www.magiclantern.fm/forum/index.php?topic=20025.msg186965#msg186965 (https://www.magiclantern.fm/forum/index.php?topic=20025.msg186965#msg186965)
I already use MLV App, what causes the false colour? Is it just the light hitting individual sub pixels?
Is 3x3 binning an averaging of 9 pixels into 1 or something else? Surely that would help alleviate the issue but it doesn't.
If already using MLVapp, do you use the 'force LMMSE' option for debayer in the export settings ?
otherwise, it doesn't help reducing false color.
The binning on 6d is actually only horizontal, vertical it skips two lines, all other ML capable cams do this, except the 5d3 which does the 3x3 binning.
The vertical line skipping is mostly causing the false color. You're actually missing two lines of (color) info, which gives in small details very contrasty color info.
Alex explains the lineskipping/binning stuff in this post:
https://www.magiclantern.fm/forum/index.php?topic=16516.msg160831#msg160831 (https://www.magiclantern.fm/forum/index.php?topic=16516.msg160831#msg160831)
LMMSE is different but not really better as it introduces other artefacts and doesn't fix the gappy horizontal lines caused by the line skipping.
It seems the 5x zoom mode fixes the line skipping issue but then my 35mm lens becomes a telephoto lens.
You can't really do much about gappy horizontal lines,
Maybe some, if you are willing to spend 365 dollar for a special filter to put in your camera, but for 365 dollar, I can live with the gappy horizontal lines just fine :P
http://www.mosaicengineering.com/products/vaf/6d.html (http://www.mosaicengineering.com/products/vaf/6d.html)
Another option is to use (old) soft lenses(Helios 44-2 for example) or use lenses wide open, that way you won't see as much sharp lines in the background ;)
My suggestion is, learn to live with it, makes live much easier.
You can do however much in post to remove false color.
if you don't like LMMSE, you could also try to do a blur on the chroma only.
With that you basically split your clip in a a chroma and a luma channel and only do a blur on the chroma part, then mix both channels together and most false color is removed.
You can do this in most video editors, here's an example from youtube where Black magic Davinci Resolve is used:
https://www.youtube.com/watch?v=kYg5OlxrYZs (https://www.youtube.com/watch?v=kYg5OlxrYZs)
Is it possible to install Magic Lantern software for the 6D onto my 6D Mark II? If so, has anyone done this successfully? Which build should I use? Are there are any missing features or drawbacks?
I know someone who used 5D-specific ML software on their 6D. However, since the 6D Mark II ML software has not been released yet, I wonder if it is possible to use an older version of Magic Lantern while I wait.
Any help or advice would be greatly appreciated!
Care to share how you got 96 FPS with a 6D?
The 96 fps on the 6d is done with a customized crop_rec module.
I promised to upload that build a long time ago ;D
Ok, now I'm going to upload it :D
I've waited that long because it is not very stable and is not reliable and it probably works best with settings I'll give now :P
You're probably want to have experience with magic lantern and raw video and a little knowledge about post production and be able to unstretch the footage to the right aspect ratio. (it's recorded with 4 x lineskipping, just as Canon does in 720p mode, so footage needs to be vertical stretched with a factor of 1.67)
1440 x 354 resolution, which is recorded, will give you a unstretched resolution of 1440 x (354x1.67)= 591 pixels, almost about 1:2.4 ratio.
Some instructions:
Turn on the camera in video mode and use the menu button to enter canon menu, now change movie rec.size to 1280-50fps all-i. (it's in the 6th tab)
The above can be done without ML and even without SD card in your camera, it's just setting your camera in 1280x720 x 50fps video mode.
(If trying to use this setting in normal 1080p mode, you're camera will soft brick, it doesn't respond to the on/off switch and you must pull out the battery and put it back in to get life back in your camera ;))
Download this crop_rec module for 6d (Not for the faint hearted 8) )
https://drive.google.com/file/d/1MalTVtGvQfoKsTPtV9oC7YQ7J811tvDw/view?usp=sharing (https://drive.google.com/file/d/1MalTVtGvQfoKsTPtV9oC7YQ7J811tvDw/view?usp=sharing)
Put it on your SD card in the ML/Modules/ folder.
Turn on your camera and enable the crop_rec module on the module tab.
Turn off and on your camera so the module will be loaded during startup, this gives a new option 'crop mode' in the movie tab, within ML menu.
Before activating the crop mode, I advise to go into raw video menu and set your preview option to 'frozen LV'.
I've just tested it, and it seems to work most reliable with frozen LV. (With other settings I got very often a top display 'error 70' camera shutdown :P )
Now that's all set enter ML menu and in the movie tab go to crop mode and select 1440 x 354 100 fps option, jup that's right, this is the special 100 fps edition instead of 96 fps ;D
Now the crop mode is selected, turn of your camera, set the switch to video mode (works best if your camera starts up directly in video mode)
and switch the camera on.
You will see a 50 fps normal live view.
Hold down half shutter press and you will see the ML preview, right.
Now let go with the half shutter press and use the magnify button and cycle trough the different modes(1x,5x and 10x) until you're back in normal view, so the magnify button needs to be pressed 4 times.
Now try the half shutter preview again, most of the times it works and now you will see the framing preview of what will be recorded in 100fps.
If the preview looks broken, which happens sometimes, cycle through all the zoom modes again with the magnify button, and try half shutter press again in normal view mode.
Once your half shutter press preview works, you can frame your shot, let go the half shutter press and hit the start/stop button to start recording.
you will probably see a black and white low resolution ML preview, refresh rate of the screen is slow, the whole camera and menu responses a little slow when this crop mode is enabled...
If you're unlucky, your camera shutsdown during recording with 'error 70' displayed on top display. But no worries, turn your camera on and off again and it should work. If not, pull out battery and put it back in and turn on the camera, everything should work. I've had a lot of crashes during testing and never destroyed my camera. Sometimes when a battery pull is needed, the refresh rate of my liveview looks a little messed up, flickering. But after a few minutes of camera usage and turning it on and off a few times, things got normal again.
So this specific crop rec module is not for the faint hearted :D
For anybody who is interested in the source, here it is:
https://drive.google.com/file/d/1c-Z0s5qqv40me1PSTf2KQ4nr-y4X-g2u/view?usp=sharing (https://drive.google.com/file/d/1c-Z0s5qqv40me1PSTf2KQ4nr-y4X-g2u/view?usp=sharing)
Thanks Levas, now I need to find something that moves so I can test it!
MLV App has a built in 1.67x stretch option in the transform section.
If this were possible in 5x mode to eliminate binning/line skipping would that improve performance or reliability any?
It works great but only at 1440 14bit lossless and it wont work properly if I overclock the SD, is there any chance you could get it to work with the SD_UHS module and increase the vertical rez?
Quote from: FeelingEpic on December 14, 2018, 02:01:43 PM
Is it possible to install Magic Lantern software for the 6D onto my 6D Mark II?
That, unfortunately, won't work.
Different camera's need different Magic lantern build.
Simple said, Magic Lantern code is basicaly the same, but you need to know specific properties of the camera and all the addresses/locations of the interesting parts in the firmware of the camera.
I've no experience in this, here is a topic about it:
https://www.magiclantern.fm/forum/index.php?topic=19737.msg185811#msg185811 (https://www.magiclantern.fm/forum/index.php?topic=19737.msg185811#msg185811)
@Commanderlake
The 1440 limit was set by me, to get a standard aspect ratio of about 2.40 after unstretching the footage.
I can get 1784 resolution, without lowering the frame rate, so still 100 fps.
I did some quick tests, and it looks like I can get a little more vertical resolution after some tweaking, 370 instead of 354.
When I go higher then 370, I get corrupted or frozen frames.
Here's a build, with 1784 x 370 @ 100 fps.
https://drive.google.com/file/d/1kGrAcBJn6WuZqaiJ831Pn_A3RIYWAeDR/view?usp=sharing (https://drive.google.com/file/d/1kGrAcBJn6WuZqaiJ831Pn_A3RIYWAeDR/view?usp=sharing)
I could get more decent resolution for 75 fps, according to above results, I guess something about 1600 x 600 @ 75 fps should be possible (so no unstretching is needed)
I was trying a slightly lower rez because it cant record continuously and overclocking the SD breaks it and I have to turn the camera off and on again every time and I cant change other stuff that resets after a power cycle such as the buffer display.
I just discovered MLV App cant export at more than 60 FPS and resamples the framerate rather than slowing it down.
Quote from: Levas on December 21, 2018, 07:31:05 PM
@Commanderlake
The 1440 limit was set by me, to get a standard aspect ratio of about 2.40 after unstretching the footage.
I can get 1784 resolution, without lowering the frame rate, so still 100 fps.
I did some quick tests, and it looks like I can get a little more vertical resolution after some tweaking, 370 instead of 354.
When I go higher then 370, I get corrupted or frozen frames.
Here's a build, with 1784 x 370 @ 100 fps.
https://drive.google.com/file/d/1kGrAcBJn6WuZqaiJ831Pn_A3RIYWAeDR/view?usp=sharing (https://drive.google.com/file/d/1kGrAcBJn6WuZqaiJ831Pn_A3RIYWAeDR/view?usp=sharing)
I could get more decent resolution for 75 fps, according to above results, I guess something about 1600 x 600 @ 75 fps should be possible (so no unstretching is needed)
Hi levas, please can you make a build wich will include 1832x800 50 fps 720 1832x1230 35 1080p ,2688x1166 25fps and 1600x600 75 fps ? it will be superb build.
Ok, here's a new ultimate crop_rec module build for the 6d :D
Use at your own risk, I very rarely had a camera crash, error 70/80, which was fixed by pulling out the battery.
(https://farm5.staticflickr.com/4871/45519428195_e11487a9cd_o.jpg)
All works best if in ML raw video menu preview option 'frozen LV' is set.
(https://farm8.staticflickr.com/7923/32560062278_78c86f330e_o.jpg)
The first 4 presets only work if camera is set in 720p mode in Canon menu (1280x720-50fps, if not available, be sure camera is set to PAL).
In plain 1080p mode, the camera crashes on these presets and you need to pull the battery out to fix this :P
To be sure everything is loaded from the preset you have to cycle through all zoom modes with magnify button.
First 4 presets have to be used in non zoom mode.
The last 5 have to be used in 5x zoom mode (non zoom mode looks normal, but shuttertime is not correct, so be sure to use 5x zoom mode)
The first 4 presets are all done in 3x3 readout, so no vertical unstretching is needed.
The fun thing, 5x zoom mode in 720p mode is the same as in 1080p mode, so all presets can be used in Canon 720p mode.
Although you can't set shutter time below 1/60th ofcourse, unless you enable 'full range' shutter range within crop menu (press 'q' button while highlighting 'crop mode' option in ML menu).
One more note, if 'frozenLV' is set as preview, most crop presets give ML preview automatically, only in 75fps and 100fps preset, half shutter press is needed to see ML preview.
So when using 75 or 100fps, you need to use half shutter press to see framing/preview, if the preview looks weird, try again after cycling through all the zoom modes with magnify button on camera.
Here's the link to the module file:
https://drive.google.com/file/d/1Fyft-vQShrFFw6TKecvYyacsfm-MTKY6/view?usp=sharing (https://drive.google.com/file/d/1Fyft-vQShrFFw6TKecvYyacsfm-MTKY6/view?usp=sharing)
Here's the link to the (messy) source:
https://drive.google.com/file/d/1D8aGy-Ci1L2qXwNUZr3LXr0h3epQdfgN/view?usp=sharing (https://drive.google.com/file/d/1D8aGy-Ci1L2qXwNUZr3LXr0h3epQdfgN/view?usp=sharing)
@CommanderLake
The presets work fine with SD write speed hack, I start up the camera in video mode, cycle through the different zoom modes, and when everything works correct, ML preview is normal and frame rate is good, I'll switch back to photo mode(the switch on your camera), load the SD write speed hack, and after that switch back to video mode.
The SD write speed hack can't be loaded in video mode when raw video is enabled, be sure to load the hack in photo mode and everything works fine.
Cool! Now put in the reduced bitrate through analog gains ;)
Doing absolutely anything breaks it even opening and closing the magic lantern menu or zooming in, the live view just corrupts and freezes and when that happens any recording is completely corrupt.
It works better with global draw off.
Works fine over here, in combination with the crop_rec_4K build from the experimental builds downloadpage.
But maybe there are other settings at play ???
You are not using fps override option in Magic lantern, otherwise, you should turn that off.
Every crop presets has a lowest compatible shuttertime value.
Not sure what happens if you have a value lower then the selected framerate?
Try enabling/opening a crop preset with the shuttertime already higher then 1/fps.
So for 100fps use, 1/160th or 1/200th for shuttertime.
I'd reflash the firmware but I cant find 116 anywhere the link on the nightly build page is broken: http://pel.hu/down/eos6d-v116-win.zip
Reflashing the firmware is - most likely - not going to solve your issue.
Wouldn't harm, either.
https://bitbucket.org/daniel_fort/magic-lantern/downloads/ -> 6D Canon Firmware for Testers.zip
Levas, could you build one with 30 and 60 Hz modes please?
I got it working, I start the camera in photo mode, OC the SD, switch to video mode where the display is frozen with vertical stripes but it shows a slow preview while recording.
The top and bottom of the screen started strobing on any screen even with no SD card but it died away after a while.
Quote from: CommanderLake on December 24, 2018, 10:17:53 AM
where the display is frozen with vertical stripes but it shows a slow preview while recording.
That sounds right, frozen liveview and no preview while not recording, you can get a preview in this state by half pressing the shutter button.
Quote from: CommanderLake on December 24, 2018, 10:17:53 AM
Levas, could you build one with 30 and 60 Hz modes please?
Now you mention 30 and 60HZ, the crop_rec presets for 720p mode are build with camera set to PAL in mind (720p50fps)
If NTSC is used, it probably doesn't work flawless, the shutter time calculated by crop_rec module are wrong, this also results in wrong shutter time blanking register calculations...
The 5x zoom mode should work flawlessly, since 5x zoom always uses the same A and B timer values, no matter what setting PAL/NTSC/24/25/30/50/60FPS.
I can make this work in many frame rates and for many basic settings (PAL/NTSC) it's just a matter of adapting some settings in the source.
But I'm not sure what you need,
are you looking for 2 extra crop presets with 30 and 60 fps setting ?The next time I should make 2 builds, one for NTSC and one for PAL.
So for now, with the current build, set your camera to PAL and when using 720p mode, use 720p 50fps.
I use 30/60 because computer monitors run at 60Hz and TV's play 30/60 just fine here in England.
Quote from: CommanderLake on December 24, 2018, 11:44:20 AM
I use 30/60 because computer monitors run at 60Hz and TV's play 30/60 just fine here in England.
What about light flickering? It is 50Hz in England.
Quote from: Dmytro_ua on December 24, 2018, 12:56:22 PM
What about light flickering? It is 50Hz in England.
Thats a shutter speed problem, multiples of 50 can still be used
Found a few minutes to alter the crop_rec file to NTSC.
For the first 3 presets, camera must be set in NTSC 720p60fps mode.
(https://farm8.staticflickr.com/7892/31508681187_986f1465d8_o.jpg)
Tested it really quick, so far it looks good ;D
Here's the link to the crop_rec module file:
https://drive.google.com/file/d/1tCe9ryqKpnGx_AKW4CaquCy32WwUmTU2/view?usp=sharing (https://drive.google.com/file/d/1tCe9ryqKpnGx_AKW4CaquCy32WwUmTU2/view?usp=sharing)
Quote from: CommanderLake on December 24, 2018, 08:46:59 AM
I'd reflash the firmware but I cant find 116 anywhere the link on the nightly build page is broken: http://pel.hu/down/eos6d-v116-win.zip
I keep copies on my downloads page (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Look for 6D Canon Firmware for Testers.zip.
Thanks dfort, Walter Schulz posted a link to your downloads.
Thanks Levas, I consider that my first christmas present. :D
Dear Levas.
Is this crop_rec module compatible with dual iso mode?
Can you provide some links to working files and simple instruction?
Is it right that in 6d dual iso looks really good without lost information, because of 1x3 pixel bining?
Dual ISO is broken all of a sudden it displays ISOless LV err 3, I even tried removing all of the ML files and redownloading them.
Reset ML to defaults (Prefs tab -> Config Files -> Restore ML defaults)
Retry in photo and movie mode. If the error occurs you have to restore ML defaults again.
Report results.
More people had the same error on different camera's. There we're some instructions on how to fix this, can't find it back.
But you had to search for the address where ISO was changed in camera (done in ADTG override in Debug menu).
I did the fix and it works for my 6d and also some other 6d users, here you can download the 'fixed' dual_iso module file for 6d:
https://www.magiclantern.fm/forum/index.php?topic=15088.msg208569#msg208569 (https://www.magiclantern.fm/forum/index.php?topic=15088.msg208569#msg208569)
You have to replace the above file with the the dual_iso.mo file on your SD card.
I did more than just reset to defaults I completely removed the magic lantern files from the SD card and re-downloaded them, I've had it working before.
Thanks Levas that works!
Quote from: Levas on December 21, 2018, 07:18:23 PM
That, unfortunately, won't work.
Different camera's need different Magic lantern build.
Simple said, Magic Lantern code is basicaly the same, but you need to know specific properties of the camera and all the addresses/locations of the interesting parts in the firmware of the camera.
I've no experience in this, here is a topic about it:
https://www.magiclantern.fm/forum/index.php?topic=19737.msg185811#msg185811 (https://www.magiclantern.fm/forum/index.php?topic=19737.msg185811#msg185811)
I asked because I know someone who put the 5D ML software on their 6D and it works perfectly fine. Could it be the case that the 5D or 6D software might work on my 6DII?
Quote from: FeelingEpic on January 26, 2019, 11:59:13 PM
I asked because I know someone who put the 5D ML software on their 6D and it works perfectly fine.
Bullshit!
Startup process checks cam/firmware version and terminates with a screen message telling it can't run. Some "modules" (=program parts optionally loaded after ML initialization) may be interchangeable. That's all compatibility we have.
And there is a ROM dumper able to run on most cams. Just doing that: Dumping ROM contents.
Quote from: Levas on January 13, 2019, 11:14:56 AM
More people had the same error on different camera's. There we're some instructions on how to fix this, can't find it back.
But you had to search for the address where ISO was changed in camera (done in ADTG override in Debug menu).
...
You're probably looking for this post:
https://www.magiclantern.fm/forum/index.php?topic=7139.msg197146#msg197146
Quote from: CommanderLake on January 13, 2019, 06:43:17 AM
Dual ISO is broken all of a sudden it displays ISOless LV err 3...
Wonder what causes it to change.
Quote from: a1ex on February 13, 2018, 09:46:07 PM
1) the cause for this variation is unknown; are these two really the only possible addresses?
2) Canon firmware startup is non-deterministic; maybe it's that; maybe the startup mode or Canon settings will make a difference, no idea
3) if outside LV, the error can be probably reproduced in QEMU; if so, that can be used to solve the mystery.
I'm new here and looking for two things:
1) Does ML allow for longer than 29:59 videos on my Canon 6D? Does it allow for more than 4GB?
2) Is there a way I can turn off the video preview screen when recording, to eliminate the light source at my kid's play and lengthen battery life? I have it set to a standard focal length and then just leave it on the tripod.
I use Magic Lantern for more then 5 years on my 6d...and I have no idea what the answers to your questions are :P :-[
I'm using Magic Lantern especially for the raw video capabilities, but I'm assuming your questions are about recording standard movie files with the the mov extension.
I found an option for turning of the display while recording, seems to work with standard movie recording, did a quick test and display turned of after 5 seconds, and it kept recording.
(https://farm8.staticflickr.com/7842/46559876804_d7d009b7a0_o.jpg)
About the 30 minute and 4 GB recording limit I'm not sure about standard movie file recording.
But there is an option to autostart recording IF recording happens to stop(4GB or 30 minute limit), so you probably mis a second or something, but it should start recording again when hitting one of these limits.
(https://farm8.staticflickr.com/7915/46559876564_14a57fac24_o.jpg)
Although, my advise is to test it, to be sure it all works, before trying to use it for something you can't record again.
If not using Magic Lantern, there is always the option in Canon menu to DIM the display light to really low brightness. In that case you only have to restart recording manually after 30 minutes.
As Levas said + https://www.magiclantern.fm/forum/index.php?topic=14309.msg211658#msg211658
4GB question: If your card is formated with exFAT file system *and* you are using MLV_rec:
Movie tab -> RAW video (MLV) -> Q -> Files > 4 GiB (exFAT) ON
If used on non-exFAT cards recording will break after 4 GiB.
Hi Guys,
Has anyone else had an issue where in 720p 50/60fps mode, when using focus peaking i get some red lines but no peaking dots when using an external monitor.
This works perfectly in 1080p modes and disappears if i disable focus peaking in 720p mode, also works if i disconnect the monitor and use the cameras screen.
I've tried a few builds and this has been an issue for all that i've tried with both of my 6D's.
Never really bothered me as the 720p mode sucks as standard but since i've discovered raw video i'm keen to explore higher frame rates
if anyone has any ideas i'd be eternally grateful.
Best regards
Rob
(https://i.ibb.co/myqrW3Z/IMG-20190305-210205.jpg) (https://ibb.co/myqrW3Z)
(https://i.ibb.co/yk2MMNQ/IMG-20190305-210327.jpg) (https://ibb.co/yk2MMNQ)
roll the dice online (https://freeonlinedice.com/)
Ahmm.. Where to start?
First of all - Levas, Danne, theBilalFakhouri, dfort, of course a1ex and many others here! - you are all freaking geniuses and I'm in absolute awe of what you have done and keep doing here! Thank you all so much from the bottom of my heart!
I discovered ML a couple of years ago after I accidentally bought a 550D (by accidentally I mean I was after a 10-22 EF-S lens, but then found it for sale with the body for less than the lens itself s/h goes on eBay for). At this stage I was 100% Sony guy (used some Canon glass though) and never planned to buy a Canon body ever! So, I ended up installing ML on the 550D and played with it for a while. It impressed the heck out of me and impelled me to get a more capable body with a better sensor. $1100AU later I became a happy owner of a s/h 6D in very good condition. To keep the story short - eventually I ended up just occasionally using the combination of the silent mode with the intervalometer for timelapses because I didn't need all the assisting tools that ML had and the thing that was really revolutionary and sounded like actual magic - RAW video - just couldn't be done in resolutions high enough to be of use for me (and the only body that could do it - 5Dm3- was too expensive at the time). At this stage I decided that since ML had been in development for so long and some very smart people had been working on it, surely they had done everything that could be done or close to it. I couldn't see any dramatic changes on the horizon and so I kind of forgot about it.
A month ago I came across an article on DPreview where ML was mentioned and it gave me an impulse to go and check it out again. I'm glad I did. An hour later, after I realized that a revolution had taken place indeed in the form of lossless compression and an SD card hack, with shaking hands I installed Danne's compilation on my 6D, not believing that it would really work, because things like this just can't happen. Then I filmed my first raw footage ever, processed it in Adobe AE and was blown away by what I got. All the advantages of raw photos - extended dynamic range, recovered highlights/shadows, enhanced local/micro contrast, extreme color manipulations - all this was possible now in video! Exacly what I needed and what my filming was lacking.
After testing raw video and making sure it was stable, I have been using this at least once a week for filming local bands and producing videos. I have never been so exited about my video editing, because now it's much more satisfying and the result always amazes me. The original excitement still hasn't worn off. I got so excited that I decided to get the best body for ML available now and another $1400AU later (the prices have almost halved in the last 2 years, which is great) I became a happy owner of a s/h 5Dm3 in very good condition with very low sc. Originally I wanted to sell the 6D but now I'm thinking of keeping it as a second cam - guys you are making me crazy!
And... just an hour ago I learned that Levas' crop_rec makes it possible to go beyond the stated everywhere 1824x1026 maximum raw resolution of the 6D in 16:9 and I have successfully recorded continuous 2080x1170 at 25fps 14bit lossless (how is this possible Levas? and why isn't this available in experiment builds? because liveview is broken? oh, I think I know - it requires the SD hack and it's considered unstable or something.), and this is without pushing too hard, I will continue my experiments tomorrow, it's 2am now! LOL, I'm going to go crazy from lack of sleep.
It's absolutely incredible that now many older Canon DSLR's - 650D, 700D, 100D - can film raw at resolutions approaching full HD. It is crazy! I will incorporate this new found information into my photography/post processing courses that I do and will educate people about this.
Thank you again!
Amen @baladev and thanks for sharing your story as it is indeed inspiring with how addicting ML can be while on these aging bodies... just like fine wine as it just keeps on getting better!
Lots of improvement over the last years. Magic Lantern is amazing.
I remember buying the 6d in 2013, when raw video was sort of just discovered.
Only able to record about 10 seconds of raw video, without audio, and this was mind blowing in 2013 :D
Not long after that audio recording was introduced and some memory hacks, which doubled almost the recording times.
Few years later raw recording in lower bitrates came by, and not long after that...lossless recording, which really changed the game for the SD card Cameras.
Thanks for discovering lossless recording Alex 8) !!!
SD_speed_hack is another nice discovery for the SD cameras, but not regarded save for your memory card if used wrong. Although I'm using it a lot and didn't experience any problems with it. Only problem is that it is still to slow for 2880x1200 :P
I did contribute a lot to finding the possibilities with crop_rec for the 6d. But I only used the tools Alex provided(basic code for crop_rec is done really well, so I could mess a lot with it, without needing to know how the shutter blanking and power save registers work) and had a lot of help from others on the forum like Dfort to learn how to compile Magic Lantern.
Another great tool for noobs :P like me is the ADTG_GUI module, available at the ISO research tools on the modules downloads page:
https://builds.magiclantern.fm/modules.html (https://builds.magiclantern.fm/modules.html)
With this tool you can adjust registers and see what it does to your camera, it's a miracle I still haven't bricked my camera ;D
This ADTG_GUI tool is not for the faint hearted, you see a lot of weird stuff happening to your live view, and the camera often soft bricks...so battery pull is needed.
But it's probably the best way to do new findings.
Still hope that the original liveview can be adjusted to the crop_rec resolutions, would be great to have real-time liveview with crop_rec 8)
Hey all !
Im fairly new to magic lantern, i started using it mostly for raw video and atm im using 10/12 bit raw video version.
I just want to check if its just me or following things works this way for everybody:
- in crop mode x5 with global drawing on i can see low res preview, BUT when i start recording it stops updating and freezes (tho i can push button to disable global draw but you cant really shoot that way and constantly pressin it :) ), is there a workaround for this ?
- and second: it looks like snapping of focus box doesnt work at all. All im trying to do is to just snap it to center but no matter what i try it simply stays in regular mode where i can freely move focus box (and manually you can't actually center it)
i didnt try other builds tho, cause i wanted 10 bit option so i can record longer in max res.
about preview:
In ML menu, in the MOVIE tab under RAW video menu, there is an option called preview, there are 4 settings, auto/real-time/framing/frozen.
Most of the time I use the setting real-time, if i want to see framing, I use half shutter press, this shows the slow ML preview with the right framing, if I'm sure about the framing I'll let go of the half shutter press.
You can even use half shutter press during recording.
For focus box:
In ML menu on the tab Prefs, there is an option called focus box settings, go into that option and there is an option called snap points. That's the one you need to enable
I have been testing different filming modes in terms of aliasing/moire/false color and discovered an interesting thing. I've been using the latest Danne's build for the 6D with the SD hack.
- If I film in x10 zoom my camera films without any crop an almost full sensor readout, just like in 'no zoom' mode (the captured region is shifted on the sensor), but unlike filming in 'no zoom' mode, which produces quite a lot of false color pixels (I've been testing this by filming very contrasty scenes with lots of small details, like trees against sky/white roofs), filming in x10 zoom produces the same angle of view but with a lot less visible artifacts in a form of falsely colored pixels. First time I discovered this I thought it was some kind of mistake on my part during filming, but since then I've repeated the test 2 more times and every time got the same result. Even asked my wife and she confirmed. It's hard to quantify what I see but it seems there's only about half falsely colored pixels I see in x10 zoom mode. I can't see why it would be like this, because the binning is the same as long as it's the same area readout, right?
Also want to share my discoveries re what lenses to use in x5 crop mode. I'm sorry if it's common knowledge around here, I'll put it here just in case. I've measured the crop we get when we switch to x5 zoom mode. It's pretty much exactly x3 crop comparing to 'no zoom' mode (I'm comparing 1824x1026 resolutions in both modes). This is a heavy crop and brings a question - what lenses to use to get a wide field of view? After quite a bit of thinking and reading/watching around I discovered that probably the cheapest and easiest way to get a usable wide-ish angle zoom is to use the 10-22 EF-S lens. Apparently in can be easily modified to work on our FF body (it took me 5 sec last night - just pull out a piece of plastic from the back of it). So, this lens in x5 zoom mode gives a very usable 30-66mm range, it can also be used in FF mode - starting from ~14mm it doesn't vignette. So, you get 14-22 in FF mode and ~30-66mm in x5 zoom mode. If you switch to higher res in x5 mode (the highest continuous I was able to record so far is 2000x1124), your crop is reduced to ~2.75, giving you ~27-60mm equivalent field of view with this lens. This also makes an interesting point. I imagine it would be impossible to get a wide angle on crop sensor cameras in x5 zoom mode. They would introduce a 1.6 crop on top of 3 times crop of FF sensor, making it a huge 4.6 crop. So, even the widest 10mm lens available would only give you ~46mm equivalent angle of view on the wide end.
Thx for answer, unfortenatelly i did have those settings for focus box but no matter what i set it just ignores it completely.
Also did i get it right, you cant see ML preview even in low rez WHILE recording ? cause i tried all those also and i allways have eather no preview or frozen frame while recording.
Oh ye to answer to second post, thats what im planing to do, to use fisheye 8mm and then shoot 5x zoom (3 times actually) ... thats exactly why im asking all these questions
What is the most recent update for the Canon 6D?
Top of page -> Downloads -> Download Nightly Builds
and read text below "Main Builds".
If going to use it for for raw video, you might wanna check out the 4k raw recording ; lossless compression build on the experiments download page for the 6d:
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip)
The name is misleading, since there is no 4K option for the 6d.
But this build has a big advantage over the standard nightly build: Lossless raw compression option, with also lower bitrate options (14 bit lossless, 12 bit lossless and lower).
Quote from: Levas on December 24, 2018, 06:37:57 PM
Found a few minutes to alter the crop_rec file to NTSC.
For the first 3 presets, camera must be set in NTSC 720p60fps mode.
(https://farm8.staticflickr.com/7892/31508681187_986f1465d8_o.jpg)
Tested it really quick, so far it looks good ;D
Here's the link to the crop_rec module file:
https://drive.google.com/file/d/1tCe9ryqKpnGx_AKW4CaquCy32WwUmTU2/view?usp=sharing (https://drive.google.com/file/d/1tCe9ryqKpnGx_AKW4CaquCy32WwUmTU2/view?usp=sharing)
This looks fantastic and I am eager to try these out. Thank you very much for all your hard work!
Question: What is the highest resolution setup for the 6D that avoids moire but also doesn't require using 5x crop. They seem mutually exclusive. So much information scattered across the forums it's hard to tell. From my understanding 5x crop can avoid the moire but will be cropped into a small portion of the sensor thus cutting your field of view down significantly.
I am shooting real estate and was quite happy with 1826x1026 at first but certain fabric patterns give bad moire in the post workflow. I need to keep my wide field of view so doesn't sound like 5x crop will be an option. 24fps is acceptable but 50/60 would be ideal for slowing / smoothing motion.
5x is actually 3x (it can be seen on preview). You are right, you either shoot full size and get pretty ugly moire or go to 5x(3x) and get almost perfect image... what i did is shooting with fisheye in zoom mode so i get pretty decent angles
Aaaah, actually the fish-eye trick is a good one. I was already doing sometime similar with my 70d for some other use cases. Not sure why I didn't think of that :) Will have to try it out. Not sure if the math will work out because I want to maintain at least a 20mm field of view and have a 12mm fish-eye so if it's literally 3x smaller field of view that will put me at about 36mm FOV?
My main goal right now is real estate videography so what I would really like is the highest resolution for 10+ seconds record time @ 60fps in 16:9. To be honest I'm getting a little fuzzy on the best way to accomplish that based on all the various presets and ML options.
The best settings I came across so far, I think, mentioned needing to stretch by 1.67x in post but the video seemed to be cropped vertically so I wasn't getting the vertical field of view I needed. Honestly unsure how to stretch in post or if that would help. When I open the files in post (MLV app, ColorCast, etc) they don't appear distorted but they are definitely in a 2.35:1 (-ish) aspect ratio and have lost a lot of vertical resolution.
Suggestions on how to accomplish the real estate setup above?
Quote from: DOP on April 02, 2019, 04:39:50 AM
My main goal right now is real estate videography so what I would really like is the highest resolution for 10+ seconds record time @ 60fps in 16:9.
Suggestions on how to accomplish the real estate setup above?
The readout speed of the sensor in the 6d isn't fast enough for decent quality 60fps in 16:9.
Could be done with the trick Canon does in 60fps, skipping some more lines and stretch the video vertical with factor 1.67, but the moire is really bad and end result is rather soft.
Without the need to stretch the video, the max resolution in 60 fps is 1688 x 754, if you want to use that mode for 16:9 aspect ratio raw recording, you end up with 1340 x 754 @ 60fps.
The moire in raw video is really bad when using wide-angle / fisheye lenses.
But you can fix a lot of the moire in post.
Best option, in my opinion, is to stay in 1824 x 1026 resolution and try to fix the moire as much as possible in post.
60 fps is not possible, you can however have 40 fps in 1824 x 1026 resolution mentioned with the crop_rec module you mentioned, so this makes a little slow/smoothing possible.
Now how to fix (color) moire in your videos.
I don't know what you are using now for post process, but most convenient workflow at the moment is probably MLV_App.
https://www.magiclantern.fm/forum/index.php?topic=20025.0 (https://www.magiclantern.fm/forum/index.php?topic=20025.0)
In MLV-App:
To fix some color moire, you could try setting debayer algorithm to LMMSE instead of the default AMAZA debayering.
And try some chroma smoothing, 3x3 or 5x5 option.
OR
If all else fails, you can try the RawTherapee workflow:
https://www.youtube.com/watch?v=MweH3RAssXs (https://www.youtube.com/watch?v=MweH3RAssXs)
A bit more time consuming, but gives you best results, you can proces your MLV files to DNG files with MLV_app.
After that you can proces the DNG files in RawTherapee and export as a TIF files, which are recognised as a video sequence by many video editor software.
This is basically the same conclusion I came to. If I move slow and cleanly 30fps isn't a big deal. I have a gimbal and once I practice more I should be able to get very smooth footage with little to no stabilization or slow down needed.
The methods to get 60fps just have too big of an impact on image quality and workflow and thus aren't practical in the end.
MLV App is what I use already so good to hear that's one of the better options for post. I no longer have the test .mlv file that showed the really bad moire (just the exported DNGs) so can't compare LMMSE but in other less problematic tests I could see no difference between that and AMaZE.
I did try RawTherapee briefly but found the interface cumbersome and poorly suited for a quick workflow and the results worse in other areas compared to my DNG process in Lightroom. Overall RT seemed similar to the whole 60fps thing. Gave benefit in one area but poorer results in several others.
Will have to try the crop_rec 40fps again. I've had stability issues with that version of crop_rec and it seems easy for live view to go glitchy and corrupt the signal.
Also considering HDR video which has pros / cons like 60fps but there are people who seem to be using it quite nicely for real estate. It's a bit more washed out by it's nature but I think I can add some contrast and punch back in post.
https://www.magiclantern.fm/forum/index.php?topic=14774.0
Really appreciate the help. Even though I'm not getting the results I hoped for (and it really makes me want a 5D III or a Black Magic Pocket Cinema) it's still better than the default Canon video and we can only spect so much from this kind of hacking. Lucky to have it at all!
PS: What's the recording limit for 40fps @ 1824 x 1026 and does it require the presets or can it be configured with the original crop_4K build?
1st of all DONT relay on fixing moire in post :) if it was that easy it would never be such big topic .... so go with crop mode
also dont expect to go any fancy framerates cause 6D can write only 40mbs (fancy 95mbs cards wont help, bottleneck is the camera) so your best bet is to go a bit below HD in 23.976 or max 25 fps
for what you need i would rather go with gopro7 .. you can shoot 4k in 60fps
Quote from: arsa3d on April 03, 2019, 10:59:02 PM
1st of all DONT relay on fixing moire in post :) if it was that easy it would never be such big topic .... so go with crop mode
also dont expect to go any fancy framerates cause 6D can write only 40mbs (fancy 95mbs cards wont help, bottleneck is the camera) so your best bet is to go a bit below HD in 23.976 or max 25 fps
for what you need i would rather go with gopro7 .. you can shoot 4k in 60fps
So, I get where you're coming from on those comments but as per my previous comments none of those things will suffice and / or are already being done.
While I wholeheartedly agree that "fix it in post" is never ideal, sometimes there is no other practical option with the given resources. I cannot shoot in crop mode due to the wide field of view that I require (as per previous comment) and at this time I am not willing to add a super ultra wide lens like an 8mm fish-eye just to keep a wide enough FOV in 3x crop mode. Even then it would be a little tighter than I'd like and most likely would have a lot of distortion.
Fully aware of the 6D (and most other Canon bodies) limited write speed. As per previous posts I'm already getting sufficient record times for this use case at 24 and even 30 fps in HD resolutions. So, that's not an issue at the moment.
The GoPro suggestion is interesting. I have a Hero 4 Silver and tried it in 1080p @ 60fps Linear mode (to remove distortion). It's ok but dynamic range isn't nearly as good, shadows have lots of noise, exposure control is limited, etc. A newer model would surely do better but I don't plan to drop $500+ on a brand new one.
@arsa3d
:) We know there are probably better options out there.
But the situation here is like: I want to achieve something like ... and this is my current camera, a 6d.
@DOP
With 40fps you lose the standard Canon liveview, and recording times are probably less then 10 seconds, more like 5 seconds I guess.
And with the use of a gimbal to smooth things out, I should definitely stick with standard 30fps, so you keep good working live view and don't need to use the crop_rec module.
I never used HDR, but I doubt if it is worth the trouble in post proces, especially on the 6d.
The 6d has very clean shadows compared to the other Canon DSLR's, and raw recording gives you plenty of dynamic range.
I see you're using Lightroom to edit the DNG's. I like Lightroom too for my photo's, really easy to use and I achieve best looking colors in Lightroom.
But for raw video(with lineskipping), it's not that good. Magic lantern raw video in Lightroom gives lots of false color moire, plus you are losing much of the fine detail in Lightroom.
Colors and exposure and noise reduction handles all really good in Lightroom, but it is very bad in keeping fine detail.
What you could try is import the DNG's in RawTherapee, do a basic exposure and white balance adjusment, set LMMSE as debayering, maybe activate the defringe option, for all colors (see the youtube video) and export it as 16 bit TIF files.
Now open these TIF files in Lightroom, and do further adjustment.
So your basically getting best of both worlds, better debayering and less color moire from RawTherapee, easy to use interface and good color and noise reduction from Lightroom.
Quote from: DOP on April 03, 2019, 06:17:50 PM
I no longer have the test .mlv file that showed the really bad moire (just the exported DNGs) so can't compare LMMSE but in other less problematic tests I could see no difference between that and AMaZE.
If you want, you can share/upload one of these examples of really bad moire DNG's.
I'm curious what results are possible and do some compare tests, with Lightroom, RawTherapee and using both options together.
Interesting suggestion on the RawTherapee > Lightroom workflow. I will have to give RT another try. I forget which other problems RT seemed to introduce but perhaps running the TIFFs through LR after can resolve them. Hmmm.
Tried to reproduce the bad moire I experienced but I no longer have the same objects (striped pillows at a hotel room) and the objects I have not did not produce the same results. The DNGs I have were extracted from the .mlv via MLV App using the AMaZE debayer so not sure if we'd still get the same results as if we used something like MLVFS to pull them straight out with no debayering? Regardless they are here if you want to experiment with them. Look at the pillows on the right...
https://www.dropbox.com/sh/8ac77he0qnngerb/AABVk6SGDhsRowGZ7GLEUZa2a?dl=0
Very appreciative of the help. Thank you!
Found the culprit of the Moire in LR on those pillows. It was sharpening.
I tried RT -> .tif and found that LR was causing the Moire there too. The moire was not present in RT or in Preview (I'm on a Mac), only in LR. A quick google (and filtering through all the 'how to fix moire' posts) I found this thread which attributed it to Sharpening and some other adjustments. https://forums.adobe.com/thread/1312516
If I either
A) Keep the sharpening below 20 (the LR default is 40, even for tifs)
B) Increase the Masking slider to 50-60+
... it seems to completely avoid the moire, for this particular case. Of course that also reduces the overall sharpness quite a bit compared to what I wanted but I'm sure with more playing I can get a reasonable compromise for these cases.
Edit: Here is a video comparison of the before (bottom) / after (top). A few frames in the adjusted version still show some artifacts, but that can probably be smoothed too. Those frames have different / more artifacts than the one I was using as my base, apparently. Now that the pillows are sorted I see other areas jumping out at me like the TV stand and some colour weirdness on the stitched edge of the back pillow at the beginning. I think these are mostly extreme cases compared to other shots I've done so far.
https://youtu.be/YF3Esgw-7Qo
Quote from: DOP on April 04, 2019, 11:25:25 PM
Found the culprit of the Moire in LR on those pillows. It was sharpening.
I tried RT -> .tif and found that LR was causing the Moire there too. The moire was not present in RT or in Preview (I'm on a Mac), only in LR. A quick google (and filtering through all the 'how to fix moire' posts) I found this thread which attributed it to Sharpening and some other adjustments. https://forums.adobe.com/thread/1312516
If I either
A) Keep the sharpening below 20 (the LR default is 40, even for tifs)
B) Increase the Masking slider to 50-60+
... it seems to completely avoid the moire, for this particular case. Of course that also reduces the overall sharpness quite a bit compared to what I wanted but I'm sure with more playing I can get a reasonable compromise for these cases.
I don't do video but for photo I usually used masking a lot in LR with sharpening to avoid oversharpened images
Quote from: scrax on April 05, 2019, 12:56:23 AM
I don't do video but for photo I usually used masking a lot in LR with sharpening to avoid oversharpened images
It is definitely handy for controlling the "spill" so to speak.
Downloaded your files and take a look at it.
Cool, in Lightroom I can see your settings, the DNG files contain your Lightroom settings.
Sharpness setting is indeed a little bit much for my taste.
Took the files in RawTherapee and LMMSE debayering removed most of the color aliasing on the pillows.
Also used the defringe setting on all colors (like explained in the youtube video), now when I set debayering back to AMAZE, the color aliasing doesn't get much back.
So in this case, only the defringe option for all colors probably is enough to get rid of color aliasing, but to be sure I kept using LMMSE as debayering.
Furthermore I set the white balance in RawTherapee and got the highlights back in the exposure settings.
The image now still looks a bit dark in RawTherapee, but you could fix that in Lightroom or choose to bring the shadow slider down in RawTherapee to get a more bright room.
So now I have two options to use as a base in Lightroom.
Without shadow adjustment: https://drive.google.com/file/d/1aYC7LhGyl6aEVWRc5K_TwtDOXCtv7spB/view?usp=sharing (https://drive.google.com/file/d/1aYC7LhGyl6aEVWRc5K_TwtDOXCtv7spB/view?usp=sharing)
With shadow adjustment:https://drive.google.com/file/d/1JL_95QDlTWX7fmzo7se1RBooWEJ3p4UG/view?usp=sharing (https://drive.google.com/file/d/1JL_95QDlTWX7fmzo7se1RBooWEJ3p4UG/view?usp=sharing)
Now I've edited one of these TIF's further in Lightroom and tried to get something identical as you created in Lightroom.
Your edit using Lightroom, the before picture: https://drive.google.com/file/d/104_a3s9Q0Ew45zKeiP0Xm2NMbM_R9r1F/view?usp=sharing (https://drive.google.com/file/d/104_a3s9Q0Ew45zKeiP0Xm2NMbM_R9r1F/view?usp=sharing)
Edit using RawTherapee and Lightroom, the After picture:https://drive.google.com/file/d/1yUh0FIi40COGedjt8JqEbl36IiOZjer_/view?usp=sharing (https://drive.google.com/file/d/1yUh0FIi40COGedjt8JqEbl36IiOZjer_/view?usp=sharing)
I've also uploaded the recipe file from RawTherapee, if you put this file in the same directory as the original DNG and load the DNG in RawTherapee you can see the settings.
These recipe files just have the filename of the dng and the extension pp3 on them. It just contains the slider settings in RawTherapee for that DNG.
https://drive.google.com/file/d/1MDx9D8fbWcO5n-PGiEmfNQGM6XsjqlGa/view?usp=sharing (https://drive.google.com/file/d/1MDx9D8fbWcO5n-PGiEmfNQGM6XsjqlGa/view?usp=sharing)
Very interesting results. Thank you for tackling this!
There are definitely aspects of the RawTherapee versions that look better (pillows) but certain things that don't look as good (light fall-off on lamp, colour cast and light falloff on window).
Will give the recipe a try and see about adjusting the workflow overall in these cases.
Side note: Increasing the Color noise reduction in LR can remove most of the color aliasing / artifacts with little to no impact on the rest of the image. I discovered that with another scene I had shot elsewhere that has strange artifacts due to a funky bed sheet pattern and it works decently well here too. The only side effect I've seen so far is it removes some saturation is areas that have only small patches of colour (like the spine of a book on a shelf if it's very small in the frame overall). Will be interesting to see how RawTherapee handles that same situation.
Again very appreciative to have such great help in the community. Thanks!
That's the beauty of raw, many ways to develop the image, many ways to fix things.
Sounds like you are already further ahead in discovering things that work around color aliasing.
Quote from: DOP on April 05, 2019, 07:24:31 PM
Very interesting results. Thank you for tackling this!
There are definitely aspects of the RawTherapee versions that look better (pillows) but certain things that don't look as good (light fall-off on lamp, colour cast and light falloff on window).
Will give the recipe a try and see about adjusting the workflow overall in these cases.
Side note: Increasing the Color noise reduction in LR can remove most of the color aliasing / artifacts with little to no impact on the rest of the image. I discovered that with another scene I had shot elsewhere that has strange artifacts due to a funky bed sheet pattern and it works decently well here too. The only side effect I've seen so far is it removes some saturation is areas that have only small patches of colour (like the spine of a book on a shelf if it's very small in the frame overall). Will be interesting to see how RawTherapee handles that same situation.
Again very appreciative to have such great help in the community. Thanks!
I can confirm that the Color noise reduction does help a lot with false color artifacts. I usually crank it to 100 and also lower the Detail to 0, if it's really bad. Yes, it does affect saturation a little, but the benefits far outweigh the cost, imo.
The Defringe setting under Lens Correction can help with some artifacts too but proxy. Mostly I tried it to reduce some actual Chromatic Aberration similar to the defringe tweak in the RawTherapee video but it grabbed some other artifacts too with very little if any side effects.
Quote from: Levas on April 03, 2019, 11:49:51 AM
Without the need to stretch the video, the max resolution in 60 fps is 1688 x 754, if you want to use that mode for 16:9 aspect ratio raw recording, you end up with 1340 x 754 @ 60fps.
Tried this out and the results are significantly better than the typic ML 720p. The aliasing is almost entirely gone and similar to the 1824x1026 30fps mode. However, there is a large crop top and bottom which make this exact result unusable for me. Is there a way to get these results without the vertical crop?
Thank you for the information, Levas, as always..
Inspired by anamorphic video preset on EOS M, I've decided to investigate a similar one we have on 6D. Since I mostly film in 16:9, I was interested in maximum resolution that would give me this proportions. Since our preset's maximum vertical resolution is 1842, I calculated that 1088 horizontal resolution would give me 16:9 video after stretching (1088*3=3264). So, I set 1088x1842 with 1:2 aspect ratio chosen (to get maximum vertical resolution). I also filmed a sample in normal full frame 1824x1026 for comparison. After stretching the anamorphic sample, this is what I got:
(https://i.ibb.co/vkq7h8b/6-D-anamorph-vs-full-sensor-crop-1-67.jpg) (https://ibb.co/vkq7h8b)
Here I over imposed the anamorphic sample over the 1824x1026 one, I also colored the anamorphic frame in orange, so it's easier to see.
I's clear that anamorphic takes only a crop of the sensor, but it is a large crop, considerably larger than what you would be able to film continuously with in x5 mode. I calculated crop factor, and it's only ~ 1.7 (1 and 2/3), slightly bigger than Canon's aps-c crop factor, so not too bad and better than at least X3 crop we get in x5 mode.
If you wonder how resolutions compare, here are illustrations of both:
1088x1842 anamorphic
(https://i.ibb.co/5nmdH2n/6-D-1088-x-1842-anamorph.jpg) (https://ibb.co/5nmdH2n)
1824x1026
(https://i.ibb.co/xSN83Fq/6-D-1824-x-1026-crop.jpg) (https://ibb.co/xSN83Fq)
I know Levas said that 1842 is the maximum vertical resolution we can get on 6D without corrupted frames. EOS M can film up to 1998 vertical , continuous at 1944. I tried it yesterday and I saw a couple pink frames in the footage (are pink frames same as corrupted?), so I need to investigate further. I will report back.
Quote from: DOP on April 07, 2019, 12:29:59 AM
Is there a way to get these results without the vertical crop?
Unfortunately not. 60fps in 16:9 with full sensor width (1824 pixels) is not possible.
Horizontal resolution, vertical resolution and fps are the factors in play for what is possible.
If you want faster fps, you have to sacrifice horizontal or vertical resolution.
If you want more horizontal resolution, you have to sarcifice vertical resolution or fps.
If you want more vertical resolution, you have to sacrifice horizontal resolution or fps.
Already made a compromise by lowering horizontal resolution to 1688 pixels wide, to get some more vertical resolution.
Couldn't get any lower then 1688, weird stuff happened when testing, otherwise a 1440 x 810 @ 60fps (16:9 aspect) was possible, but somehow 1688 seems to be as low as we could get on 6d for now.
Another thing, horizontal resolution takes less resource of the cam then vertical, since horizontal is readout with 4 columns at one time.
So you can sort of say that you have to sacrifice 4 pixels of horizontal resolution, to get 1 pixel extra vertical resolution.
That's the reason why you see all these high resolution wide crop ratios 1:2.40 and such in crop modes on the different cameras.
Another thing to have in mind is that the 6D sensor reads 4 horizontal pixels at once, and the 5d3 sensor does 8 horizontal pixels at once (So more complex sensor, which can read twice as fast).
This means basically that the 6d can do the same as the 5d3, but only at half the resolution or half the frame rate :P
Quote from: baladev on April 07, 2019, 04:00:31 PM
I know Levas said that 1842 is the maximum vertical resolution we can get on 6D without corrupted frames. EOS M can film up to 1998 vertical , continuous at 1944. I tried it yesterday and I saw a couple pink frames in the footage (are pink frames same as corrupted?), so I need to investigate further. I will report back.
I do have a working 1688 x 1996 @ 25 fps mode 8) I probably can squeeze out some more vertical resolution if I lower the 25 fps to 24 fps. Will probably give about 1688 x 2080 @ 24 fps.
What do you prefer, 24 or 25 fps ?
Edit: Pink frames can be considered as corrupted, or can you fix them in post ? I think all frames that can not be fixed in post, can be count as corrupted frames ;D
Quote from: Levas on April 07, 2019, 07:51:06 PM
Unfortunately not. 60fps in 16:9 with full sensor width (1824 pixels) is not possible.
Horizontal resolution, vertical resolution and fps are the factors in play for what is possible.
If you want faster fps, you have to sacrifice horizontal or vertical resolution.
If you want more horizontal resolution, you have to sarcifice vertical resolution or fps.
If you want more vertical resolution, you have to sacrifice horizontal resolution or fps.
Already made a compromise by lowering horizontal resolution to 1688 pixels wide, to get some more vertical resolution.
Couldn't get any lower then 1688, weird stuff happened when testing, otherwise a 1440 x 810 @ 60fps (16:9 aspect) was possible, but somehow 1688 seems to be as low as we could get on 6d for now.
Another thing, horizontal resolution takes less resource of the cam then vertical, since horizontal is readout with 4 columns at one time.
So you can sort of say that you have to sacrifice 4 pixels of horizontal resolution, to get 1 pixel extra vertical resolution.
That's the reason why you see all these high resolution wide crop ratios 1:2.40 and such in crop modes on the different cameras.
Another thing to have in mind is that the 6D sensor reads 4 horizontal pixels at once, and the 5d3 sensor does 8 horizontal pixels at once (So more complex sensor, which can read twice as fast).
This means basically that the 6d can do the same as the 5d3, but only at half the resolution or half the frame rate :P
Good info, thank you. I assumed there was some kind of relationship like that.
So you're saying that there was "weird stuff" happening at 1440 x 810 @ 60fps? What type of stuff? Corrupt frames, buggy ML behaviour?
To clarify, what is the best 16:9 60fps resolution we can get without losing vertical? Just the ones in your presets that result in lots of aliasing? I don't mind if the resolution is lower since the raw is crisper than the default h.264 and can be upsized pretty cleanly but I don't want to lose any FoV or have aliasing. I've played around a bit but it's time consumer and I know you've done lots of great work in this area so probably easier to ask. Apologies for all the questions, just trying to wrap my head around it all and keep track of all the different options / configurations.
QuoteI do have a working 1688 x 1996 @ 25 fps mode 8) I probably can squeeze out some more vertical resolution if I lower the 25 fps to 24 fps. Will probably give about 1688 x 2080 @ 24 fps.
What do you prefer, 24 or 25 fps ?
Oh sweeeeet! Bloody genius. Could we have both? ::) If not, 1688 x 2080 @ 24 fps please.
2080 vertical would give 3698x2080 vs 3264x1842 we have now in 16:9, and only ~1.5 crop (like Sony APS-C) not bad at all.
If my math is correct for 16:9 it would be 1232x2080 anamorphic, which is 61.5Mb/s at 24f, which I think is close to the writing speed limit we have. In x5 mode maximum res. I was able to get continuous recording with was 2000x1124, which gives 56.2Mb/s at 25 frames. I use Sandisk Extreme Pro.
QuotePink frames can be considered as corrupted, or can you fix them in post ? I think all frames that can not be fixed in post, can be count as corrupted frames ;D
:) No, you definitely can't fix them in post..
I was referring to your original post, in which you said you couldn't get higher res than 1842 without corrupted frames, I was wondering if you meant pink frames or something else..
So, anamorphic preset works in x5 zoom mode, even though we don't set it, right?
.. also, is it possible to control the area that's being captured somehow? Would be great to move the region to the middle of the frame to capture the sharpest part of a lens. The bottom part is very distorted with wide angle lenses especially.
Fine-tuned the 1x3 mode a little
1632 x 2052 @ 25fps
1632 x 2144 @ 24fps 8)
Both are for use in normal 1080P non zoom mode.
When activated, be sure to press the 'menu' button once, to enter canon menu and press it again to go back to liveview, this way all registers are set for this preset.
When used in 5x zoom, shuttertime values are messed up and horizontal pixelbinning is not done.
(https://live.staticflickr.com/7898/47510704542_3f9aa25d3b_o.jpg)
Link to this crop_rec module for 6d:
http://drive.google.com/file/d/1Z7yxSE-zmQET9g-E-YDzKrpfzxlzo3yy/view?usp=sharing Edit, build removed, didn't work as expected.
New build:
http://drive.google.com/file/d/11e8YcImfRmpgi4rWWLUVjp38_7e-duws/view?usp=sharing (http://drive.google.com/file/d/11e8YcImfRmpgi4rWWLUVjp38_7e-duws/view?usp=sharing)
For those who are not familiar with 1x3 mode:
1x3 mode is just like normal 1080p mode, but instead of line skipping, each vertical line of resolution is recorded.
So you end up with a weird stretched out frame which needs to be fixed in post.
You need to set up an aspect ratio of 1:2 in RAW video menu to be able to make use of the full resolution of this crop_rec preset.
There are two options in post.
Option 1: For video free from lineskipping aliasing, you can divide vertical resolution by three and adjust it to that, so 1632 x 2144 will become 1632 x 714 of resolution.
By using this method, you should end up with frames free from the lineskipping aliasing , because no lineskipping has happened.
Hint, MLV_App has an option called Transformation, here you can multiply the height of the frames by 0.33, giving you the proper dimensions.
Option 2: For very high resolution video, stretch horizontal resolution by a factor of 3, so 1632 x 2144 will become 4896 x 2144 of resolution.
Ofcourse this doesn't look as good as real 4896 x 2144 resolution, but also not bad, since the vertical resolution is real and the horizontal resolution is from binned pixels.
If you want to end up with 16:9 aspect ratio high resolution, select 1264 horizontal resolution in raw video menu, which will create 3792 x 2144 resolution in post.
Hint, MLV_App doesn't have an option for 3x horizontal stretch, but you can set desired resolution on output settings, so that's where you can set 3792 x 2144 resolution.
Some more info:
First 1688 pixels wide was the lowest I could get, but I only tested in steps of 64 pixels at a time and 1624 didn't work right.
Now I've tested the range within 1688 - 1624 and 1632 pixels horizontal seems to work properly.
If I go lower then 1632 the whole right side of the frame gets slowly flat, like less contrasty and gets a purple tint.
And when I tried to go even lower, there is no image at all, all black Canon liveview and black Magic Lantern Preview, just a whole lot of nothing :P
So now 1632 seems to be the horizontal limit and I know which A timer to use for, I could calculate the necessary B Timer value for 25fps and 24fps.
And of course the maximum vertical resolution which comes with that.
When I tried a little more vertical resolution, I started to get 2 corrupted frames at the beginning and the annoying warning messages on display.
When I tried much more vertical resolution, all frames are corrupt, not only the first two ones, but all of them :P
The resolutions here should work properly I've seen no corrupted frames, but can't hurt to test some more.
Can you share code. Are you getting corrupted frames in 1x3 binning or corruption free?
From the few times I tested today, they were corruption free :D
Will send the source to you today.
Does the 1x3 mode compensate for the lack of an AA filter in the 6D? I mean, does it hide the aliasing as well as when used on AA-filtered cameras?
Quote from: mvrck on April 08, 2019, 03:13:18 PM
Does the 1x3 mode compensate for the lack of an AA filter in the 6D? I mean, does it hide the aliasing as well as when used on AA-filtered cameras?
Pretty much yes.
Quote1632 x 2052 @ 25fps
1632 x 2144 @ 24fps
I'm speechless. I will be all over this soon, testing and reporting back.
Quotebut instead of line skipping, each vertical line of resolution is recorded.
QuoteFor video free from lineskipping aliasing
Sorry, but isn't this a contradiction? Or am I missing something?
My understanding is that the difference between 1X3 mode and x5 zoom mode is that the latter one records everything, all lines and columns and the former one bins the columns? Neither should produce aliasing? And in my experience don't, or maybe very small, definitely no funny false color pixels along high contrast edges.
I know the option 1 you described is used by many, but in my opinion this isn't the best if the highest details are needed because it throws away 2/3 of vertical resolution. I prefer stretching video three times horizontally. This doesn't have such a big impact on the final image, since human eyes resolve more resolution horizontally than vertically.
Levas, thank you so much for this, you are a stud!
I myself, after testing all different kinds of raw recording options, decided for myself to stick with these two modes:
- full frame option when no crop is required and I need the most stable option (haven't tested 1x3 enough to trust it as much, for me it's still bleeding edge for now). But, it produces an occasional moire and false colored pixels.
- 1x3 When I need the best resolution and the cleanest picture free from artifacts and can re-shoot. Pushes hardware much harder at the highest resolutions, fastest cards are must. Final files are larger and require more processing times.
Danne - I haven't tested this new edition of crop_rec from Levas, but the previous one I tested quite a bit at 1088x1842 (max vertical res. for this version) and never got corrupted frames, apart from the customary 2nd pink frame, which I get on my 6D in full frame mode as well.
Quote from: mvrck on April 08, 2019, 03:13:18 PM
Does the 1x3 mode compensate for the lack of an AA filter in the 6D? I mean, does it hide the aliasing as well as when used on AA-filtered cameras?
But downside is, the standard Canon liveview is not working with this crop_rec preset, so instead you'll see a liveview image created by magic lantern, which has a slow refresh rate and is lower resolution compared to Canon's liveview.
So the 1x3 method is a nice option to have, but not usable for all types of video shooting, because of the lack of proper liveview.
@Danne
Here is the most important part of the source:
static inline uint32_t reg_override_1x3_24FPS(uint32_t reg, uint32_t old_val)
{
switch (reg)
{
/* raw resolution (end line/column) */
case 0xC0F06804: return 0x87e01ba; //1632 x 2052 - 24 fps
case 0xC0F06824: return 0x1ce;
case 0xC0F06828: return 0x1ce;
case 0xC0F0682C: return 0x1ce;
case 0xC0F06830: return 0x1ce;
case 0xC0F06010: return 0x1d0;
case 0xC0F06008: return 0x1d001d0;
case 0xC0F0600C: return 0x1d001d0;
case 0xC0F06014: return 0x8f5; //24 fps for 1x3
case 0xC0F0713c: return 0x87e;
case 0xC0F07150: return 0x87e;
}
return 0;
}
Most important here is that there needs to be enough room between the values of the B-timer, register 6014 and the vertical resolution in 6804.
6014 = 0x8f5 and vertical resolution in 6804 is '87e'.
The vertical resolution always needs to be less then the value of 6014, in this case the vertical resolution value is 0x8f5 - 0x87e = 0x77 lower then B-timer value.
I've tried raising the resolution to 0x88e, which means there is only a difference of 0x67 between B-timer and resolution, but that gave me corrupted frames.
Another important thing, if I remember correct, is that my crop_rec presets got more stable when I use the same value for registers 713c and 7150 as the value for vertical resolution in 6804
In this case 6804 = 0x87e01ba
So 87e for vertical resolution and I use these exact same values for 713c and 7150.
What also works for register 713c is using vertical value from 6804 +1, so in this case 0 x 87f also works.
And sometimes it helps to lower the 7150 a little. It's a bit of trial and error but works for me.
How does this part look in your 1x3 code ?
Quote from: baladev on April 08, 2019, 04:09:20 PM
Sorry, but isn't this a contradiction? Or am I missing something?
My understanding is that the difference between 1X3 mode and x5 zoom mode is that the latter one records everything, all lines and columns and the former one bins the columns? Neither should produce aliasing? And in my experience don't, or maybe very small, definitely no funny false color pixels along high contrast edges.
You are right in saying that both 1x3 and 5x zoom mode both are free of aliasing (or at least the aliasing caused by line skipping).
I think I said the same in the lines you quoted, but maybe I've written it down in a way that it is not proper English :P
Quote from: Danne on April 08, 2019, 02:57:58 PM
Can you share code.
Quote from: Levas on April 08, 2019, 03:00:07 PM
Will send the source to you today.
How about using Bitbucket to share code?
Yesterday I made a fork of Danne's repository (https://bitbucket.org/daniel_fort/magic-lantern-danne-fork/overview) and put in the crop_rec module from Levas (https://bitbucket.org/daniel_fort/magic-lantern-danne-fork/commits/2b447e4164b1e8c4c790d141c8f81b3e2de56c28) in it just to see if works. Next step is to merge the two crop_rec sources along with any additions so the 6D will work alongside the other cameras that are already ported to Danne's bleeding edge branch.
Once the dust settles it would be great to clean it up and merge into the main repository.
Speaking of dust settling -- Levas just posted the settings for 1x3 so we should add that to the mix.
Just a real quick update..
A couple of short takes, 2 minutes each at 1264x2144 (for 16:9). Continuous, 57.5 Mb/s. Second frame is pink (normal for my cam), no corruption apart from that. But, noticed vertical lines in both takes, different patterns in each take. Here are screenshots from both videos:
(https://i.ibb.co/RHxHNDn/M09-0213-frame-986.jpg) (https://ibb.co/RHxHNDn)
(https://i.ibb.co/bJrmjrN/M09-0215-frame-211.jpg) (https://ibb.co/bJrmjrN)
:o That's exactly the weird stuf when I go too low in horizontal resolution.
I remember this happening before with earlier crop_rec modes which where not in 5x zoom mode.
This never happens in the 5x zoom mode, let me check some stuff, maybe I can make it work in 5x zoom mode, with binning.
Had some time to quickly alter the presets for use in 5 x zoom mode.
Normally in 5 x zoom mode, there is no horizontal pixelbinning done.
Due to recent discovery, we know which registers to alter.
https://www.magiclantern.fm/forum/index.php?topic=16516.msg212472#msg212472 (https://www.magiclantern.fm/forum/index.php?topic=16516.msg212472#msg212472)
So I made both presets for use in 5 x zoom mode, because we're moving to 5 x zoom, we get 8 pixels of extra resolution with the same register settings ;D
Added the 8183 and 8184 registers and used values for binning, seems to work over here, but as proven before, I'm not that good in testing :P
Here's the new build (same place as the previous build, so it's replaced with the new one)
http://drive.google.com/file/d/11e8YcImfRmpgi4rWWLUVjp38_7e-duws/view?usp=sharing (http://drive.google.com/file/d/11e8YcImfRmpgi4rWWLUVjp38_7e-duws/view?usp=sharing)
Happy testing :D
The vertical line issue Baladev posted, is not always very obvious to see on camera screen and seems to get worse over time the camera is on in that mode.
It's best seen on screen when you see a tonal change on the right side of the frame, as in Baladev first example, the right side has a purple haze showing.
These lines get worse over time this crop_rec is activated, not sure if it can show up in 5 x zoom, but never saw it happen in 5 x zoom before...
Check power timing regs regarding subtle corruption. I had similar issues but changed things around in here. SOmething was erased as well but some quick comparing should make things obvious:
/* assuming FPS timer B was overridden before this */
int fps_timer_b = (shamem_read(0xC0F06014) & (0xFFFF + reg_timing5));
int readout_end = shamem_read(is_digic4 ? 0xC0F06088 : 0xC0F06804) >> 16;
/* PowerSaveTiming registers */
/* after readout is finished, we can turn off the sensor until the next frame */
/* we could also set these to 0; it will work, but the sensor will run a bit hotter */
/* to be tested to find out exactly how much */
adtg_new[4] = (struct adtg_new) {6, 0x8172, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (6D/700D) */
adtg_new[5] = (struct adtg_new) {6, 0x8178, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (5D3/6D/700D) */
adtg_new[6] = (struct adtg_new) {6, 0x8196, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (5D3) */
adtg_new[7] = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 1 + reg_timing3) }; /* PowerSaveTiming OFF (6D/700D) */
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3) */
adtg_new[10] = (struct adtg_new) {6, 0x82B6, nrzi_encode(readout_end - 1 + reg_timing6) }; /* PowerSaveTiming ON? (700D); 2 units below the "ON" timing from above */
/* ReadOutTiming registers */
/* these shouldn't be 0, as they affect the image */
adtg_new[11] = (struct adtg_new) {6, 0x82F8, nrzi_encode(readout_end + 1 + reg_timing4) }; /* ReadOutTiming */
adtg_new[12] = (struct adtg_new) {6, 0x82F9, nrzi_encode(fps_timer_b - 1 + reg_timing4) }; /* ReadOutTiming end? */
I checked my code and there´s plenty room between 6014 and 6804.
Are these regs vital? Never use them in 1x3 binning:
case 0xC0F06824: return 0x1ce;
case 0xC0F06828: return 0x1ce;
case 0xC0F0682C: return 0x1ce;
case 0xC0F06830: return 0x1ce;
My experience with 713c and 7150 is somewhat random. They don´t need to be matched at all. I can do this:
case 0xC0F0713c: return 0x79f + reg_713c;
case 0xC0F07150: return 0x50b + reg_7150;
Still good. If I lower 7150 too much pic freezes or corruption but not really getting any better closing in on 713c.
Quote from: Danne on April 08, 2019, 07:38:45 PM
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3) */
Hmm, these are indeed a little different, -5 instead of -1, will check if that brings new possiblities.
Quote from: Danne on April 08, 2019, 07:38:45 PM
Are these regs vital? Never use them in 1x3 binning:
case 0xC0F06824: return 0x1ce;
case 0xC0F06828: return 0x1ce;
case 0xC0F0682C: return 0x1ce;
case 0xC0F06830: return 0x1ce;
Not sure if they are vital, but as far as I know they work together with the A timer, the four registers are always 2 values lower then A timer registers in Canon standard modes.
So I always put them in my presets, 2values lower then A-timers, not sure if they do much though ???
Quote from: Levas on April 08, 2019, 07:57:14 PM
Hmm, these are indeed a little different, -5 instead of -1, will check if that brings new possiblities.
They are different because I changed them at one time due to corruption.
Ran some tests with the new crop_rec module. Can't see thin vertical stripes anymore but the thick pink area on the right is still there. Seem to be of random width, sometimes thinner, sometimes thicker. Same resolution 1264x2144 at 24f. Filming indoors (mostly carpet and walls) was getting 56mb/s continuous, pointing the camera outside from a balcony resulted in 65mb/s orange indicator continuous if pointing at low detail objects like houses and roads and which would immediately turn red if pointing at trees. So, it's right on the borderline of what 6D can record.
Here are the processed dng frames, all from different takes. The outdoor ones show the pink area in the shadows/dark places.
(https://i.ibb.co/VJbsxM4/M09-1527-frame-843.jpg) (https://ibb.co/VJbsxM4)
(https://i.ibb.co/w0N169N/M09-1528-frame-402.jpg) (https://ibb.co/w0N169N)
(https://i.ibb.co/Tr6LgSS/M09-1530-frame-906.jpg) (https://ibb.co/Tr6LgSS)
(https://i.ibb.co/7GqJf3g/M09-1532-frame-124.jpg) (https://ibb.co/7GqJf3g)
.. forgot to add- 2nd frame is dark/corrupted in all takes. In outdoors scenes the 3rd frame has some pink noise on top also, apart from this no corruption.
Try set these regs to following in crop_rec.c. Too bad code isn´t easily accessible since we have testers around:
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3) */
Made the changes Danne suggested, run the build on my cam and it didn't exploded, so it's safe to test.
Could record a clip with the 1x3 preset, haven't checked the files yet.
https://drive.google.com/file/d/1ltu1i9L2i2TiPiaNfk_oSHeczws6oVsh/view?usp=sharing (https://drive.google.com/file/d/1ltu1i9L2i2TiPiaNfk_oSHeczws6oVsh/view?usp=sharing)
@Danne
Here's the original source, it's not that I don't want to share, it's more that it is a big mess inside :P
https://drive.google.com/file/d/1mP0SQ7mv_7ff4EyM-evhIJQ-XKzKWXAs/view?usp=sharing (https://drive.google.com/file/d/1mP0SQ7mv_7ff4EyM-evhIJQ-XKzKWXAs/view?usp=sharing)
The presets we're testing are called 1x3 and 1x3_24FPS
Should look familiar, 1x3 preset is on line 1107
1x3_24FPS preset is on line 1140
This seem to have fixed it.. Tried filming 2 short 1 minute videos. Same settings as before. 2nd and 3rd frames are corrupted, the rest is good. 1st did in FF mode the second in x5 zoom. The only difference noticed FF mode set exposure to 1/47. Same res as before.
Here are the shots from both takes:
(https://i.ibb.co/n6ncnnD/M09-2022-frame-1272.jpg) (https://ibb.co/n6ncnnD)
(https://i.ibb.co/BqRrWqz/M09-2024-frame-1183.jpg) (https://ibb.co/BqRrWqz)
Will do more testing a bit later.
Thank you Levas and Danne!
Great. This fix really should be pushed into main branches as it reoccurs on peoples footage on a regular basis. Impossible to rescue in full in post.
Quote from: DOP on April 07, 2019, 10:28:27 PM
To clarify, what is the best 16:9 60fps resolution we can get without losing vertical? Just the ones in your presets that result in lots of aliasing? I don't mind if the resolution is lower since the raw is crisper than the default h.264 and can be upsized pretty cleanly but I don't want to lose any FoV or have aliasing.
As for now, looks like 1688 x 754 is gonna stay the maximum for 60p, maybe 1632 now works too with Danne's fix, but this would give only about 30 pixels extra vertical in 1632 x 784, still far from 16:9.
And still curious if the fix works when using the preset for longer times. Because before the fix it looked like the purple color shift in the right part of the frame was creeping in slowly over time using the preset. So needs some more testing.
I think your best bet is to film in full view 16:9 in 30p and become really good in fixing color moire in post :D
Quote from: Levas on April 10, 2019, 09:10:44 AM
And still curious if the fix works when using the preset for longer times. Because before the fix it looked like the purple color shift in the right part of the frame was creeping in slowly over time using the preset. So needs some more testing.
Yes, please test. Can confirm this fix valid for 5DIII.
QuoteAnd still curious if the fix works when using the preset for longer times. Because before the fix it looked like the purple color shift in the right part of the frame was creeping in slowly over time using the preset. So needs some more testing.
I shot 11 short clips today outside and indoors. Took about 20 min, camera got pretty warm - 51C. Will post results later (have to go now), but in short - didn't find any weird stuff. Clips were shot with breaks. Do you want me to shoot continuous? For how long?
Quote from: baladev on April 10, 2019, 09:38:48 AM
I shot 11 short clips today outside and indoors. Took about 20 min, camera got pretty warm - 51C. Will post results later (have to go now), but in short - didn't find any weird stuff. Clips were shot with breaks. Do you want me to shoot continuous? For how long?
If above files are free from creeping purple stuff I say the fix is working.
Ok, more pictures of interesting boring stuff. Earlier today I filmed 11 short clips, about 0.5-1 minute long. Camera got very warm, was showing 51C.
All had 2nd and 3rd frame corrupted, apart from one or two clips. The rest of the footage was fine.
All in 1632x2144 1x3 24fps preset. Some in full frame mode, some in x5 mode.
I was moving the camera around but chose the frames that would show the possible defects best, which means dark uniform areas.
All frames from different clips:
(https://i.ibb.co/Dft9JCY/M10-1641-frame-945.jpg) (https://ibb.co/Dft9JCY) (https://i.ibb.co/YN3CQ5D/M10-1643-frame-277.jpg) (https://ibb.co/YN3CQ5D) (https://i.ibb.co/3WQQdMD/M10-1648-frame-816.jpg) (https://ibb.co/3WQQdMD) (https://i.ibb.co/G3tPn8v/M10-1650-frame-188.jpg) (https://ibb.co/G3tPn8v) (https://i.ibb.co/R3PKp2b/M10-1651-frame-117.jpg) (https://ibb.co/R3PKp2b) (https://i.ibb.co/Ws9606C/M10-1652-frame-146.jpg) (https://ibb.co/Ws9606C) (https://i.ibb.co/QfpPFgN/M10-1653-frame-606.jpg) (https://ibb.co/QfpPFgN) (https://i.ibb.co/G7VSYXT/M10-1654-frame-581.jpg) (https://ibb.co/G7VSYXT) (https://i.ibb.co/BcQyQfS/M10-1655-frame-678.jpg) (https://ibb.co/BcQyQfS) (https://i.ibb.co/2Wr1JvJ/M10-1656-frame-846.jpg) (https://ibb.co/2Wr1JvJ) (https://i.ibb.co/FxzpyRy/M10-1657-frame-561.jpg) (https://ibb.co/FxzpyRy)
Just before I did another test. Filmed 4 longer clips. 8-13 min in length to push the camera further and see if there's accumulative effect Levas proposed. 2 were filmed in 1632x2144 1x3 24fps preset and the other two in 1632x2052 1x3 25fps. Basically, I filmed until my 128Gb card got full, which is about 35 min.
(https://i.ibb.co/L67pBy3/M10-2240-frame-10787.jpg) (https://ibb.co/L67pBy3)
(https://i.ibb.co/8cs9hBZ/M10-2250-frame-12585.jpg) (https://ibb.co/8cs9hBZ)
(https://i.ibb.co/mtyjLmV/M10-2300-frame-17459.jpg) (https://ibb.co/mtyjLmV)
(https://i.ibb.co/Z8SR5nL/M10-2313-frame-4267.jpg) (https://ibb.co/Z8SR5nL)
Looks good, I think it's safe to say that, Danne's fix, really works :D
These latest 1x3 presets you are using are made for 5 x zoom mode, which in this case means that shutter-time is correct in 5 x zoom mode.
You still can use it in non zoom mode, but shutter-times are not corresponding with the shutter-time settings on your top lcd display.
QuoteThese latest 1x3 presets you are using are made for 5 x zoom mode, which in this case means that shutter-time is correct in 5 x zoom mode.
You still can use it in non zoom mode, but shutter-times are not corresponding with the shutter-time settings on your top lcd display.
Yep, I know you said these are for x5 mode. I just though I would try them in FF mode as well. :)
I did notice that in x5 mode my lowest shutter was 1/33 and in FF mode it was 1/45, so it was changing between the two on the screen depending on the mode.
Hi,
I have been using my 60D for years
Finally I get to upgrade my 60D to a 6D (used, sold by my friend)
Great to see a lot of development here! :D
QuoteFinally I get to upgrade my 60D to a 6D (used, sold by my friend)
Welcome to the FF world! I used to be a Sony only guy and was convinced that Canon sensors are crap (well, I still know they are.. not the best). But then I needed a backup/second camera to complement my A7R2 (which has the best sensor on the market in terms of noise/signal ratio). Since I have a lot of Canon glass, I thought maybe some Canon would work for me. After researching I discovered that the sensor Canon put inside this body (that was specifically developed for it and which even outperforms the sensor inside 5Dm3) is about the best sensor they ever produced in terms of low noise/high iso performance, only beaten recently by Canon 5Dm4. I shoot/film a lot in low light and this was a deciding factor for me. So, I ended up getting a s/h 6D.
Here's a nice comparison of the 6D sensor with other relevant cameras. 700D, I believe has a very similar sensor to 60D you had, so you can see how much of improvement you are getting.
https://www.dpreview.com/reviews/image-comparison/fullscreen?attr18=daylight&attr13_0=canon_eos6d&attr13_1=canon_eos700d&attr13_2=canon_eos5dmkiii&attr13_3=sony_a7riii&attr15_0=raw&attr15_1=raw&attr15_2=raw&attr15_3=raw&attr16_0=6400&attr16_1=6400&attr16_2=6400&attr16_3=6400&attr126_3=1&attr171_0=1&normalization=full&widget=267&x=0.1582884960903206&y=0.5264428209018275
Did some more testing today of the latest 1:3 presets to see if I would be able to record continuously with them. Basically confirmed what I said before - they are good for short clips. In bright day light I couldn't achieve continuous recording no matter what I did (lowering exposure so there are no overexposed parts, disabling LV). When the sun went behind a big cloud and it became overcast I was able to record continuous with LV disabled in non-LV view (not sure how to call it). Of course the view was scrambled. I can work with this because I mostly film static scenes, but for many people it would be problematic.
Since we can't reduce vertical resolution in these presets, I tried to minimize the bitrate by going to the 25fps preset and setting 24fps in fps override. It didn't work, I got scrambled footage.
Would it be possible to make vertical resolution adjustable? If not, making another preset with the 25fps preset resolution at 24fps might make it continuous.
It would also be very good if we could move the crop from the bottom up and center it in the frame. Is it possible at all? The way it is now it's capturing the edge of the frame, which is not the best part of it, especially with wide angle lenses, where it get's very distorted.
Seems you are able to compile:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec.c
I added reg_6014 into the crop mode sub menu to the two 1x3 binning presets in Levas code. By reducing you will increase fps. GOing to 25 should be safe.
I'll probably have time this weekend to do this changes.
Lowering the vertical resolution for 24fps preset is easy, centering the view needs a bit of testing but should be doable I guess.
Maybe you can find out what resolution is continuous by lowering the horizontal resolution of the current build, that way we can calculate at how many megapixel frame size it is continuous, and use that to calculate the needed vertical resolution for continuous.
QuoteSeems you are able to compile
Sorry, this is way above my head :-[
QuoteBy reducing you will increase fps. GOing to 25 should be safe
I probably didn't explain myself clear.
The fps are fine, no need to change them.
If possible, would be good to be able to change vertical resolution in 1:3 presets. If this is impossible, then making another preset 1632x2052
24fps should allow continuous recording.
Quotecentering the view needs a bit of testing but should be doable I guess
Since I'm too dumb to code, if I can help with any testing, I'm listening.
QuoteMaybe you can find out what resolution is continuous by lowering the horizontal resolution of the current build, that way we can calculate at how many megapixel frame size it is continuous, and use that to calculate the needed vertical resolution for continuous.
I hear you. I'll do this tomorrow, It's 1am here now :)
Oh God, sometimes testing can be so time consuming, difficult and inconclusive.
Spent 3 hours today testing presets for the 6D an EOS M. In some cases I would get one result for a preset just to come back to it some time later to get somewhat different result. All together I ran about 60 tests.
From the two 1:3 presets I only managed to test the 1640 x 2025 25fps one before I started loosing light.
All tests are done with 14bit recording.
# In LV with GD enabled and everything else disabled (histogram ets..) I was able to get more or less stable continuous with 976 x 1952 at 25fps (by more or less I mean if I direct the camera at a large white object like a wall or a roof taking at least 1/3 of the view, I get first red indicator and then stop)
# If I disable GD, I can film continuous with 1040 x 2052 at 25fps with similar remark.
at 24 fps we would be able to go a bit higher of course.
Do you want me to test the 24fps preset too or can you calculate from these results?
I think the current 1:3 presets should be left in the crop_rec for short clips and maybe new ones added for those who want continuous.
@baladev
Dis some quick changes to crop_rec, here is a build with 1640 x 1890 resolution, used them both for 24fps and 25fps.
For 16:9 use 1120 x 1890 to end up with aliasing free 1120 x 630 resolution, my guess is that those should be continuous even when overexposed.
And moved the crop, I think the crop is now in center of the sensor.
Happy testing :D
https://drive.google.com/file/d/1SE3_93SBBTG3O7p8cA4s8Su8np30FXwU/view?usp=sharing
(https://drive.google.com/file/d/1SE3_93SBBTG3O7p8cA4s8Su8np30FXwU/view?usp=sharing)
For the future it would be nice to be able to just adjust vertical resolution, or in crop_rec module or probably even better in normal raw video menu.
Thank you Levas!
Will test it and report back.
Yeah, I realized that your original 1824x1842 1:3 preset (in 16:9 1088x1842) was close to the maximum resolution continuous recording we can get on these cameras. A slight bump in resolution like this is probably all we can have.
@Levas
Tested presets - all work well, continuous in both as long you don't get overexposed large white objects in the frame.
Re centering, not so rosy. Here's where the current 1120 x 1890 crop positioned on top of FF frame.
(https://i.ibb.co/f9z5vcJ/M15-1429-frame-41.jpg) (https://ibb.co/f9z5vcJ)
Need to be moved up and left. Are there any regs I can try to move the frame?
Ideally we would have a setting with vertical resolution adjustable, maybe withing a short range, like 1880 - 2144.
Thank you!
??? that centering didn't work out, need to check my eyes :P
Will look into it later on in the week.
I've decided that my previous test might have been flawed because I compared two 16:9 frames and for proper positioning you need to see where the crop positioned relative to the full sensor picture. I redid the test. Here you can see a full frame picture 1824x1216 res and on top of it in orange is a 1120x1890 frame form 1:3 anamorphic preset stretched to 3360x1890 and then on top of that there is 2304x1296 frame from x5 zoom preset for reference.
Sorry the picture is out of focus, I forgot to focus properly :)
(https://i.ibb.co/MDh11zZ/M16-1539-frame-47.jpg) (https://ibb.co/MDh11zZ)
So took a while, busy week.
But here is a new version of the 1x3 mode on 6d, now the recorded part should be reasonable centered in the frame.
I compared the recording against a photo (3:2 aspect ratio), I think it's centered, can you confirm baladev ?
Link to the module:
https://drive.google.com/file/d/1zA7dxRNxc362Sw-EdmfNLKqd3MkjCNDG/view?usp=sharing (https://drive.google.com/file/d/1zA7dxRNxc362Sw-EdmfNLKqd3MkjCNDG/view?usp=sharing)
@Baladev
Danne made some nice modifications to the sd_uhs module.
Not sure which version you're using, but this new version of Danne activates at startup, it doesn't do write and read tests, only sets the necessary registers at startup.
You can check it works by looking at the Debug tab in ML menu, in memory patches, 3 patches linked to SD UHS are visible.
So if you know your SD card gets faster write speeds with the sd_uhs module, you can try this version, activate module in modules tab, and it's instantly loaded at each startup of the camera.
Link to modified sd_uhs module by Danne:
https://drive.google.com/file/d/1SJHrA75UXobTzBcsEY3lqbHxhNdoksPb/view?usp=sharing (https://drive.google.com/file/d/1SJHrA75UXobTzBcsEY3lqbHxhNdoksPb/view?usp=sharing)
For other users, be sure to test your card with the standard sd_uhs module before trying this one above, I have cards which become slower when using this module.
The Sandisk extreme pro (95MB/s, UHS speed class 3, video speed class V30) cards seems to be working very well with this sd_uhs module, my older sandisks extreme card becomes slower with this module :P
@Levas
Thank you very much for the new crop and the SD UHS. I will test the new crop and report back. I use Sandisk extreme pro and it benefits from the regular sd_uhs a lot, so this new version should speed up things..
Thank you once again, you are a legend.
Quote from: Levas on April 19, 2019, 01:16:42 PM
@Baladev
Danne made some nice modifications to the sd_uhs module.
Not sure which version you're using, but this new version of Danne activates at startup, it doesn't do write and read tests, only sets the necessary registers at startup.
You can check it works by looking at the Debug tab in ML menu, in memory patches, 3 patches linked to SD UHS are visible.
So if you know your SD card gets faster write speeds with the sd_uhs module, you can try this version, activate module in modules tab, and it's instantly loaded at each startup of the camera.
Link to modified sd_uhs module by Danne:
https://drive.google.com/file/d/1SJHrA75UXobTzBcsEY3lqbHxhNdoksPb/view?usp=sharing (https://drive.google.com/file/d/1SJHrA75UXobTzBcsEY3lqbHxhNdoksPb/view?usp=sharing)
For other users, be sure to test your card with the standard sd_uhs module before trying this one above, I have cards which become slower when using this module.
The Sandisk extreme pro (95MB/s, UHS speed class 3, video speed class V30) cards seems to be working very well with this sd_uhs module, my older sandisks extreme card becomes slower with this module :P
ive tested this
been getting consistant 60 to 70mb/s write on my Sandisk Extreme Pro MicroSD card
Sounds pretty high. And this is with liveview on?
@Levas
Tested the latest crop_rec. Vertically it's well centered now, but horizontally it's too much to the right, more than before.
(https://i.ibb.co/DR5PRft/M20-1626-frame-78.jpg) (https://ibb.co/DR5PRft)
Also tried the new sd_uhs module from Danne. Loads faster. Speeds are the same as before. Maximum ~65Mbs
Quote from: Danne on April 19, 2019, 09:29:33 PM
Sounds pretty high. And this is with liveview on?
In liveview, with globaldraw on i get ~62mb/s and global draw off ~64mb/s
Quote from: jai554 on April 19, 2019, 08:32:07 PM
ive tested this
been getting consistant 60 to 70mb/s write on my Sandisk Extreme Pro MicroSD card
Works rather convenient doesn't it, always had to activate SD_hack in debug menu, took some time and fiddling.
This new update from Danne is a big improvement.
Quote from: baladev on April 20, 2019, 09:12:24 AM
@Levas
Tested the latest crop_rec. Vertically it's well centered now, but horizontally it's too much to the right, more than before.
(https://i.ibb.co/DR5PRft/M20-1626-frame-78.jpg) (https://ibb.co/DR5PRft)
Also tried the new sd_uhs module from Danne. Loads faster. Speeds are the same as before. Maximum ~65Mbs
Ok, I think I'm getting crazy :o
How could this happen, aah I know, I've centered the preset for full 1640 pixels wide view...you are using 1120 pixels wide view.
And looking at the picture you send, the raw video menu apparently crops off at the left side of the frame if you choose to record lower then available resolution.
So in trying to get a centered 1120 x 1890 preset, I've limited the max resolution in this mode to 1120 x 1890 (in 6804 register).
(somehow this change doesn't always kick in the first time the camera is on, sometimes an extra 'menu' button press helps to get registers set.)
I think the centering is rather spot on, but you can tweak it a little within the crop_rec menu -> advanced -> delta_head3.
You can try changing the value of delta_head3 in steps of 10 or 20 and see how it looks. You can input negative and positive values.
If you go too far on either side, you end up in 1:1 pixel readout mode and loose ML preview :P (-200 to +200 is a reasonable range for delta_head3 in this case)
New build:
https://drive.google.com/file/d/1h0Cn4bM7Ou2HoEMGz59FBIoqjSVQMiwH/view?usp=sharing (https://drive.google.com/file/d/1h0Cn4bM7Ou2HoEMGz59FBIoqjSVQMiwH/view?usp=sharing)
Quote from: Levas on April 20, 2019, 11:53:16 AM
Works rather convenient doesn't it, always had to activate SD_hack in debug menu, took some time and fiddling.
This new update from Danne is a big improvement.
yeah... saves a lot of time
need to test it thoroughly though since I've read that some got their card corrupted when using this module
Quoteaah I know, I've centered the preset for full 1640 pixels wide view...you are using 1120 pixels wide view
Yep, at this stage I mostly use 16:9 aspect, which results in 1120 pixel width. I'm sorry to be a pain in the neck, I assumed that 1:3 setting on this camera works similar to 1:3 preset on the EOS M, which keeps the position of the crop in the same spot if you reduce resolutions (it removes equal number of pixels on each side).
QuoteSo in trying to get a centered 1120 x 1890 preset, I've limited the max resolution in this mode to 1120 x 1890 (in 6804 register).
(somehow this change doesn't always kick in the first time the camera is on, sometimes an extra 'menu' button press helps to get registers set.)
I think the centering is rather spot on, but you can tweak it a little within the crop_rec menu -> advanced -> delta_head3.
You can try changing the value of delta_head3 in steps of 10 or 20 and see how it looks. You can input negative and positive values.
If you go too far on either side, you end up in 1:1 pixel readout mode and loose ML preview :P (-200 to +200 is a reasonable range for delta_head3 in this case)
Thanks a lot. I though about trying to change some registers myself but wasn't sure which and didn't want to screw something up.
So you are saying delta_head3 changes horizontal position of the captured region? Strange, it says 'May help pushing the resolution a little..'
On the other hand CMOS[2] says ' Horizontal position/binning' - maybe i should change that one?
Thank you for your help!
No, you definately need delta_head3, I altered some functions in that menu.
Didn't bother to rename it nicely :P
See it as alpha/beta builds ;)
@Levas
The last crop_rec produces a strange glitch - every other frame is broken in half vertically with the bottom half shifted or delayed. It's ok though, I will try to follow your advice and play with delta_head3 and try to center the frame horizontally with your previous build, which worked well. Even if I find a value for delta_head3 which will center the frame the camera will forget it after a power cycle. Is it possible to write a lua script to set the register? This is what I'm thinking of doing.
Thank you!
I only checked ML preview, which is fine, but the recording is done from another raw stream (must remember that more often :P), so didn't test it good enough.
Will take a look at it, probably easy to fix.
Levas, Which register is responsible for moving the captured area vertically? Is it delta_head4?
Tried centering your 1640x2052 25p preset in 1216x2052 16:9 ratio. Tried changing delta_head3 to some positive value, it moved the captured area the wrong way, setting it to any negative value broke preview.
Changing delta_head4 didn't work - changing it to any value broke preview.
Thank you!
The vertical allignment is a bit more complicated, it works in zones, you can't adjust it pixel for pixel. So you have to skip many numbers before you come in a working zone/area of the sensor.
But I made a new build, did some testing and it seems that I can't go lower in resolution then 1256 wide, below that you get the corrupted frames like you explained.
So adjusted the presets to max resolution of 1256 x 1890 and you can ofcourse adjust recording resolution in raw menu to 1120 x 1890.
I think it's pretty centered for 1120 resolution now. You can adjust it a little, with delta_head3, let me know if you find a better value for delta_head3 so I can make it permanent in a future build:
For now, 1256x1890 1x3 modes:
https://drive.google.com/file/d/1lcYLd7y31MzEp9Hu6mD7CVh0odzb55BC/view?usp=sharing (https://drive.google.com/file/d/1lcYLd7y31MzEp9Hu6mD7CVh0odzb55BC/view?usp=sharing)
Thank you for the heads up and for the new crop_rec, will test it tomorrow.
Today I focused on your 1640x2025 25p preset- tried to center it in the frame. Horizontal position I can live with but vertical is very low, close to the bottom. Tried changing delta_head4 (assume it's responsible for vertical positioning?). Tried all values from -100 to 100, no luck - broken preview.
For all 6d owners who want to mess around with registers on the 6d, without any need to know how to program or compile.
Check out ADTG_GUI module on the module downloads page, long time available and made by A1ex.
It's a Wonderfull tool that detects register settings and changes(so we can see what register values Canon is using) and even override the registers with new values(settings).
It's all temporally , when the camera is switched off or function is sett off, everything is back to normal again.
I have seen much weird shit happen to liveview while messing aroundd with registers, and maybe sometimes a camera lock up.
But pulling out the battery(by a lock up) or switching camera off and on again set everything back to normal.
Quick tutorial:
Be sure you're using the "experimental crop_rec_4k build." (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip (https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip) from the experimental download page. I think the adtg_module doesn't work with standard nightly build.
https://builds.magiclantern.fm/experiments.html (https://builds.magiclantern.fm/experiments.html)
Download the adtg_gui module on the module downloads page, at the bottom of the page, ISO research tools section:
https://builds.magiclantern.fm/modules.html (https://builds.magiclantern.fm/modules.html)
Put the "adtg_gui.mo" module file in the modules folder on your SD card (/ML/Modules/)
Start up the camera and enable adtg_gui module in the modules tab:
This module uses some techniques which conflicts with Crop_rec module and SD_UHS module, so to be sure to avoid weird behaviour or conflicts, disable crop_rec module and SD_UHS module.
(https://live.staticflickr.com/65535/46797891075_549d46c2d5_o.jpg)
After that restart camera and you will see a new option under the debug tab, go ahead enable it:
(https://live.staticflickr.com/65535/40747667313_c64c5f7fc2_o.jpg)
Press "Q" button to go inside ADTG Registers menu and you will see an option for which registers it must show, probably best to restrict it to show only known registers, or at least not all, because that are many, many registers :P
(https://live.staticflickr.com/65535/32770785987_c4a4435ce2_o.jpg)
Now if you aren't already in video mode, go ahead, switch to video mode and dive into ADTG registers menu again with the "Q" button.
You will now see many registers and if you use scroll wheel to scroll down, you'll also find the CMOS registers:
(https://live.staticflickr.com/65535/32770785877_35d941be0f_o.jpg)
On 6d, CMOS 3 register is know to control ISO setting, in the picture above you see the value for this register is 0x33.
33 is the value Canon uses for ISO 800.
Now go ahead, press "set" button to be able to change the value, for example to "0" or "11".
Use "set" button to enter new value, D-pad for selecting which number to change and top scrollwheel for selecting new value.
If you are in liveview or video mode, you can see the effect immediately.
You are changing iso value, without using the iso button :P
If you highlight the override value and press "q" button, it stops overriding the register and changes it back to default value again.
If you now use the "iso" button to change iso value on your 6d, and go back into ADTG Registers menu again, you can see the value of CMOS 3 is changing.
Canon uses the following values for CMOS 3 on 6d:
ISO 100 = 0x0
ISO 200 = 0x11
ISO 400 = 0x22
ISO 800 = 0x33
ISO 1600 = 0x44
ISO 3200 = 0x55
ISO 6400 = 0x77
ISO 12800 = 0x77
ISO 25600 = 0x77
See a pattern here, try overriding it to some weird combination, 0x17...and check liveview, see the bright and dark lines, you have now set dual iso mode (iso 200/6400) ;D
But what is going on after iso 3200...why is it skipping value 0x66 between iso 3200 and 6400 ?
Let's find out and override the register to 0x66...it works there is liveview...looks like an iso setting between iso 400 and 800.
Probably a real iso 640 setting for the sensor. Not sure why it is there, for Canon testing, or is it a magic iso and is there no noise :P
And what's happening above ISO 6400...12800 and 25600 are using the same setting as 6400, 0x77.
So there is something fishy here...
Go to video mode, set iso (with canon iso button) to iso 6400.
Go back to adtg_gui menu and choose option, show "modified from now on" option.
(https://live.staticflickr.com/65535/47661577182_69a565e42d_o.jpg)
Exit menu and change iso to 12800 with iso button and check adtg_gui menu again.
If you did it right you'll see four registers showing up:
ADTG2[8882]
ADTG2[8884]
ADTG2[8886]
ADTG2[8888]
Behind it, you'll see the current values and the before values.
These are the analog preamp registers.
CMOS 3 is amplification within/on sensor level and ADTG2[8882-8888] registers are believed to be analogue amplifiers between sensor capture and before digital conversion.
Normally these registers are around value 0x400, with iso 12800 they become around 0x900 and with iso 25600 around 0x1200.
0x400 hexadecimal -> decimal conversion = 1024
0x900 hexadecimal -> decimal conversion = 2304
0x1200 hexadecimal -> decimal conversion = 4608
So decimal value doubles, is one stop extra iso.
By trial and error max value for overriding seems to be 1FFF, higher value gives darker image, so it's starts at zero again.
0x1FFF is about twice as high in decimal value (8191) as is 0x1200, so overriding these four registers to 0x1FFF
Gives you iso 51200 on your 6d :D, although a very noisy one :P
The above gives a idea how to explore registers and play with them and see what happens.
@baladev
CMOS 6 and 7 do horizontal and vertical position.
If you go into 5x zoom mode and move the focus box around, you can see values of CMOS 6 and 7 changing.
Thank you Levas for the information
Are you saying that if I find CMOS 6 and 7 values, you would be able to bake them into 1:3 presets and get centered framing?
If so, I have one question - without crop_rec, how do I set resolution I want to center?
[edit]
Ok, I got the numbers for cmos7 moving the captured area up by 1,2 and 3 steps..
Now, what do I do with these numbers? Tried entering them in delta_head4, it didn't work.
QuoteYou can adjust it a little, with delta_head3, let me know if you find a better value for delta_head3 so I can make it permanent in a future build
For the 1256x1890 1x3 preset I found out that delta_head3 of 30 puts the captured region right in the center at 1120 x 1890 (16:9), so you can bake it in.
Can you please add your other 1:3 presets - 1216 x 2052 and 1264 x 2144 to the same crop_rec at 25fps, so we could have one ultimate anamorphic build (at the moment I need to switch between them). I still don't know how to center the captured area vertically. I found the values for cmos7 but don't know what to do with them. So, if you could center these two presets (2052 and 2144) vertically, I will find values for delta_head3 to center horizontally.
Thanks!
Will make an ultimate build and see if I can center the other presets too.
So the latest preset 1256x1890 can use 30 more on the horizontal centering.
Could take some days (before I find some time), but it will come :D
QuoteSo the latest preset 1256x1890 can use 30 more on the horizontal centering.
Yes. The way it is now, it's a bit too much to the left. delta_head3 set to 30 puts it right in the center.
QuoteCould take some days (before I find some time), but it will come
If it's easier for you, you could make a crop_rec with cmos7 register available for modification, then I could do all the work myself (finding the values for horizontal/vertical centering) and give them to you.
Thanks!
In crop_rec.c I also use optical black area sizes to centre presets. It´s a comnbination of cmos 5, cmos 7 and refining skip offsets. Maybe useful thinking for 6D too:
In following function:
/* optical black area sizes */
/* not sure how to adjust them from registers, so... hardcode them here */
static inline void FAST calc_skip_offsets(int * p_skip_left, int * p_skip_right, int * p_skip_top, int * p_skip_bottom)
{
For eosm:
case CROP_PRESET_anamorphic_EOSM:
case CROP_PRESET_anamorphic_700D:
case CROP_PRESET_anamorphic_650D:
/* see autodetect_black_level exception in raw.c */
skip_bottom = 24;
if (ratios == 0x1)
{
skip_bottom = 20;
skip_right = 156;
skip_left = 160;
}
if (ratios == 0x2)
{
skip_bottom = 0;
skip_right = 324;
skip_left = 292;
}
break;
Usually this stuff affects black level auto detection in raw.c but that´s another story how to fix...
@Danne
I think that horizontal centering can be done pixel perfect with CMOS register.
Pixelperfect vertical centering is not possible with CMOS I think, because it works in certain sensor area steps.
So to centre presets, you're using other values for optical black areas, not a bad idea, this makes pixel perfect possible for vertical ???
About the black level value detection, I thought these were changed to hardcoded values long time ago, when having problems with wrong black levels.
Are you sure black levels are still detected/detemined from black area and not from hardcoded values ?
Auto detected, oh yes believe me. Don't have the code part in front of me but it looks for I think left border or else it checks bottom or top of image. Search auto blacklevel or similar in raw.c.
For what it's worth..
I've mentioned before that I've noticed that centering is done differently on the M and the 6D.
Here is an example of 1736x976 FF vs 1120x1890anam vs 1088x1836anam on the M (resolutions changed in the same preset):
(https://i.ibb.co/SNC1Kwt/1736x976-FF-vs-1120x1890anam-vs-1088x1836anam.jpg) (https://ibb.co/SNC1Kwt)
On the 6D it looks like this at the moment:
1824x1026FF vs 1216x2052an vs 1264x2144an:
(https://i.ibb.co/W0jNFV1/1824x1026-FF-vs-1216x2052an-vs-1264x2144an.jpg) (https://ibb.co/W0jNFV1)
The M centers automatically by cropping evenly on each side, though vertical centering isn't perfect.
I've been working with Levas and Danne on getting the 6D into the same "bleeding edge" branch that is working with the EOSM/100D/700D/650D. It is pretty much ready to merge but it hasn't been tested yet. I posted a test build here:
https://bitbucket.org/daniel_fort/magic-lantern-danne-fork/downloads/
This might make it easier to re-center, adjust black level, etc. because those issues were already solve for some of the other cameras that are working on Danne's branch.
[EDIT] When I said "merge" I meant into the bleeding edge branch, not the main repository. A1ex said he'd like to make the crop_rec module fully generic on all models (https://www.magiclantern.fm/forum/index.php?topic=19336.msg215917#msg215917). The experiments we're doing will hopefully serve to help reach that goal.
Finally had time to test, but unfortunately the crop_rec presets don't work right in this build ???
Good thing is, it's probably something small.
I can load crop_rec module and set the presets that are in there. After that, the image partly changes, but it's not good.
And recordable resolutions in raw menu and fps don't change, standard values.
So I think, the CMOS register changes are definately loaded/activated and working (the image does change, but it's not good, stretched/weird green cast etc.)
But the registers like 6804 and A and B timers are definitely not loaded/activated, because selectable resolution doesn't change and FPS doesn't change, 5x zoom stays 29fps.
So these portions of the presets are not loaded/activated in this build:
case 0xC0F06804: return 0x52f02c0; // 2688x1296_25fps x5 Mode;
case 0xC0F06824: return 0x2d7;
case 0xC0F06828: return 0x2d7;
case 0xC0F0682C: return 0x2d7;
case 0xC0F06830: return 0x2d7;
case 0xC0F06010: return 0x2d9;
case 0xC0F06008: return 0x2d902d9;
case 0xC0F0600C: return 0x2d902d9;
case 0xC0F06014: return 0x57a; /* for 25 fps */
case 0xC0F0713c: return 0x530;
case 0xC0F07150: return 0x51f;
Hum -- must have missed something. I made a "fake" pull request (https://bitbucket.org/daniel_fort/magic-lantern-danne-fork/pull-requests/1/6d-experiments/diff?w=1#chg-modules/crop_rec/crop_rec.c) to see what is going on. Like you said, must be something small, but what?
Add 6D in here:
* we can identify the current video mode from 0xC0F06804 */
for (uint32_t * buf = (uint32_t *) regs[0]; *buf != 0xFFFFFFFF; buf += 2)
{
uint32_t reg = *buf;
uint32_t old = *(buf+1);
if (reg == 0xC0F06804)
{
if (is_5D3)
{
engio_vidmode_ok = (crop_preset == CROP_PRESET_CENTER_Z)
? (old == 0x56601EB) /* x5 zoom */
: (old == 0x528011B || old == 0x2B6011B); /* 1080p or 720p */
}
if (is_100D)
{
engio_vidmode_ok =
(old == 0x45802A1) /* x5 zoom */ || (old == 0x42801ed) /* x3 digital zoom */ || (old == 0x4A701D7 || old == 0x2D801D7); /* 1080p or 720p */
}
if (is_EOSM)
{
engio_vidmode_ok =
(old == 0x4540298) /* x5 zoom */ || (old == 0x42401e4) /* x3 digital zoom */ || (old == 0x4a601d4) /* 1080p */ || (old == 0x2d701d4 /* 720p */);
}
if (is_700D)
{
engio_vidmode_ok =
(old == 0x4540298) ||/* x5 zoom */ (old == 0x4a601d4 || old == 0x2d701d4); /* 1080p or 720p */
}
if (is_650D)
{
engio_vidmode_ok =
(old == 0x4540298) /* x5 zoom */ || (old == 0x42401e4) /* x3 digital zoom */ || (old == 0x4a601d4) /* 1080p */ || (old == 0x2d701d4 /* 720p */);
}
}
}
Ok--I see what I missed. It is late here so I'll look into it in the morning. Do we know those values for the 6D?
I bet levas gets them in a jiffy otherwise.
Ok, got this one working right now, but still some stuff to fix, shutter time isn't right in 5x zoom mode.
As it is now, it looks like shutter time is right in non zoom mode, but most of the crop_presets are for 5x zoom mode.
So Danne, Dfort and I need to look into it some more before this merge into the bleeding edge branch is ready for use.
Meanwhile I 'll keep updating the presets for 6d in the other crop_rec module I'm using and when presets are tested, centered(as far as possible with CMOS registers) and working right, I can move them over to the bleeding edge branch.
Source of this crop_rec.c file can be found here:
https://bitbucket.org/Levas_EOS/magic-lantern/src/crop_rec_4k_mlv_snd_Levas6D/modules/crop_rec/crop_rec.c (https://bitbucket.org/Levas_EOS/magic-lantern/src/crop_rec_4k_mlv_snd_Levas6D/modules/crop_rec/crop_rec.c)
Are shuuter time readings working correctly in your code in x5 mode?
Yes, but had to made a fix for it.
I Have this in my build:
/* helper to allow indexing various properties of Canon's video modes */
static inline int get_video_mode_index()
{
return
(crop_preset == CROP_PRESET_HD100) ? 3:
(crop_preset == CROP_PRESET_HD75) ? 3:
(crop_preset == CROP_PRESET_HD50) ? 3:
(crop_preset == CROP_PRESET_2K) ? 1:
(crop_preset == CROP_PRESET_ULTRA_HD) ? 1:
(crop_preset == CROP_PRESET_4K) ? 0:
(crop_preset == CROP_PRESET_5K) ? 1:
(crop_preset == CROP_PRESET_FullRes) ? 1:
(crop_preset == CROP_PRESET_1x3) ? 1:
(crop_preset == CROP_PRESET_1x3_24FPS) ? 1:
(crop_preset == CROP_PRESET_HD2) ? 3:
(crop_preset == CROP_PRESET_3x3_1X) ? 1:
4;
and hardcoded this:
/* from SENSOR_TIMING_TABLE (fps-engio.c) */
/* hardcoded for 6d */
const int default_timerA[] = { 0x27f, 0x2d9, 0x21f, 0x27F, 0x27f };
const int default_timerB[] = { 0x63f, 0x493, 0x61b, 0x31f, 0x334 };
const int default_fps_1k[] = { 25000, 29921, 29978, 50000, 59964 };
So I basically set the video mode for each preset in the first code part and then it uses the corresponding numbers from the table in the second code part.
Cool. Now I might have a way to fix the faulty values on my eosm. Just tried some over here.
Amazing how quickly development happens when the code is shared.
Quote from: baladev on May 02, 2019, 05:45:03 PM
Can you please add your other 1:3 presets - 1216 x 2052 and 1264 x 2144 to the same crop_rec at 25fps
@Baladev, I added the other presets, this build now has four 1x3 presets:
1256x1890 @ 25fps
1256x1890 @ 24fps
1640x2052 @ 25fps
1640x2144 @ 24 fps
Looked some more into the vertical centering and it seems that it goes in steps of 33, so if you use delta_head4, values of 33 and multiples works.
So for example, you can use -66,-33, and +33, +66 for delta_head_4 to finetune.
I have put the crop_rec.mo file on my bitbucket page, instead of google drive I used before, here's the file:
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/crop_rec.mo (https://bitbucket.org/Levas_EOS/magic-lantern/downloads/crop_rec.mo)
Source code can be found here:
https://bitbucket.org/Levas_EOS/magic-lantern/src/crop_rec_4k_mlv_snd_Levas6D/modules/crop_rec/crop_rec.c (https://bitbucket.org/Levas_EOS/magic-lantern/src/crop_rec_4k_mlv_snd_Levas6D/modules/crop_rec/crop_rec.c)
Thank you very much my friend!
I'll try to center it and report my findings back.
Have you baked in 30 for delta_head_3 for the 1256x1890 preset?
So, delta_head_4 IS cmos7 as I suspected?
Quote from: baladev on May 06, 2019, 06:04:49 PM
Have you baked in 30 for delta_head_3 for the 1256x1890 preset?
Yes I moved the horizontal centering with value of 30 for 1256x1890.
Quote from: baladev on May 06, 2019, 06:04:49 PM
So, delta_head_4 IS cmos7 as I suspected?
Almost, but not exactly, I've set a standard value for CMOS 7 and delta_head4 is a value that is added to the standard value:
case CROP_PRESET_PRESET_10:
cmos_new[6] = 0x469 + delta_head3;
cmos_new[7] = 0x327 + delta_head4; //0xd , 0x261, 0x369 and 0x3cc works
break;
So CMOS 7 is set to value 0x327 and delta_head4 is added, so the sum of the two becomes value for CMOS 7
It's a bit of a messy tool that I use for adjusting presets :P
@ Levas
I'll have some free time tomorrow and so am planning to work on centering the two remaining presets. However I just thought that if you are planning to convert to Danne's code for preset centering (as was discussed above if I understood correctly) maybe it's a waste of time centering these presets because Danne's presets center automatically (as I showed above) when you change resolution, so instead of 3 different presets we could have only one with the highest resolution possible and then just center it properly and we would have a winner. Or am I missing something? Please advise.
Thank you for explaining how cmos7 and delta_head4 are related. So, delta_head4 is an offset Can't understand then why the values for cmos7 I was getting though ADTG_GUI didn't work when entered into delta_head4. When I experimented with ADTG_GUI and I moved the crop area in x5 zoom mode up I got these hex values: 208/1c6/163, converted to decimal 520/454/355. The default cmos7 value is 26b(619). I tried to subtract the new values from the default (619-520=99) and entering this into delta_head4, but this didn't work. Is my logic off?
Thanks!
My code won't do anything for 6D presets so tweak away.
Quote from: baladev on May 07, 2019, 06:07:53 PM
@ Levas
Thank you for explaining how cmos7 and delta_head4 are related. So, delta_head4 is an offset Can't understand then why the values for cmos7 I was getting though ADTG_GUI didn't work when entered into delta_head4. When I experimented with ADTG_GUI and I moved the crop area in x5 zoom mode up I got these hex values: 208/1c6/163, converted to decimal 520/454/355. The default cmos7 value is 26b(619). I tried to subtract the new values from the default (619-520=99) and entering this into delta_head4, but this didn't work. Is my logic off?
Thanks!
You're logic is good, not sure why it didn't work.
Only thing I can think off that +99 was off the sensor in that build?
There aren't that many steps vertical, 99 is 3 steps, if the standard value I used was less then 3 steps away from the end off the sensor, you fell of the edge with +99 :P
@Levas
Yes, you are right, +99 did cause me to 'fall off the edge of the sensor' and I got a black preview, but then I tried the negative -99 and it didn't work either - I got corrupted live view.
In any case, this doesn't matter now any more, because in this latest crop_rec of yours delta_head4 is actually working properly and this is good news. How did you make it work - did you change something?
However delta_head3 is now semi broken and doesn't work the way it used to. :o Before a change of 20 would give me a consistent shift by equal amount. (20 would shift right by 2cm, then 40 would shift right by another 2cm and so on - I do my measurements in Photoshop in cm - it might be odd, but it's easier for me this way :)) Now delta_head3 -20 would shift left by 2cm, -40 would shift by another 0.3cm and then values below -50 don't work - LV becomes black.
So, this is my summary of different 1:3 anamorphic presets in the current build:
1120 x 1890 - Perfectly centered now horizontally and vertically
1216 x 2052 - Vertically centered. Best horizontal centering should be achieved by delta_head3 set to -60 or -70 (if it worked like in previous builds, can't test this in current build)
1264 x 2144 - To center vertically set delta_head4 to -33. Best horizontal centering should be achieved by delta_head3 set to -40 or -50 (if it worked like in previous builds, can't test this in current build)
One last thing - could you please set the x2144 preset to 25fps (or create a copy of it with 25fps). I film a lot in artificial light, which here in Oz produces a lot of flickering at 24fps.
All in all, we are very close!
Thank you!
Will take a look at it.
There is some development going on on the merge with Danne's crop_rec.
At the moment we got lower bit depth lossless recording working for 6d.
And I got working Canon liveview on most presets, (not correct framing), but at least the scrambled liveview is gone.
So ideal for focussing, since you're seeing realtime 5x zoom Canon liveview, and for framing you can use half shutter press so ML preview shows up.
Unfortunately, the high FPS presets and 1x3 presets don't work in this build :-\ , so we hope to figure out why that is, so we can use 12 bit or 10 bit lossless on the 1x3 presets and high FPS presets.
Presets not working. Not the code at me. Did you add 6D in code part here?
https://www.magiclantern.fm/forum/index.php?topic=15088.msg216000#msg216000
Yep that part is in there for 6d.
It's some safety stuff, it doesn't do preset when you're in the wrong video mode, but how does it know for which video mode the preset is made ?
At the moment all 1:1 pixel read out modes work in 5x zoom mode and are disabled in normal non zoom mode.
So the code finds these presets only suitable for 5x zoom mode, why ?
You can perfectly do 1:1 pixel readout, while in Canon 1080p mode...
So it's a question of when is something the wrong video mode, according to the code.
But I need some sleep now...will be continued.
Hm, so maybe the reason I never managed to do 1:1 readout in mv1080p mode. Interesting.
QuoteAt the moment we got lower bit depth lossless recording working for 6d.
And I got working Canon liveview on most presets, (not correct framing), but at least the scrambled liveview is gone.
This sounds awesome! Good luck.
Ok, busy weekend over here, but since some presets work and lossless with lower bit depths works, here is something to play with until other presets are added and working.
Here's a link to a full build (can't just only upload crop_rec module, since this makes use of some stuff Danne made for Eos-m which makes use of some changes in other ML files.
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May11.6D116.zip (https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May11.6D116.zip)
Edit: new build coming up
Some notes,
Somehow, the first time crop_rec module is activated and started, it starts with preset 6 (which doesn't exist actually for 6d ???, so a bit weird and buggy).
So probably best to start up in photo mode the first time you have activated the module and change it in ML menu to an existing preset.
I have started the camera in video mode with preset 6 and it doesn't do harm, looks like an empty preset or something.
But better to change it to one of the 3 existing presets.
This build contains 3 crop_rec presets:
2480x1396 at 25fps
2688x1296 at 25 fps
2880x1200 at 25 fps
All are for use in 5x zoom mode and have working Canon live view in 5x zoom mode (not correct framing though, so you can use half shutter press to see ML preview for framing)
Bit depth is set to 12 bit by default and can be changed in the sub menu of crop_rec (go to crop_rec in ML menu and press "Q" button on camera)
There is a lot more in the sub menu, but most is doing nothing for 6d I guess, haven't test it yet.
This build also contains the SD_UHS module which activates the high speed writing settings for 6d SD card interface at startup.
If your SD card is suitable for these settings, you'll get higher writing speeds (about 60MB/s in video mode)
If you experience slower writing speeds or no extra speed (20MB/s to 40MB/s) it's probably better to disable this module in module tab.
I'm really impressed by the recording times with SD_UHS module combined with lower bit depth like 10bit for resolutions like 2880 x 1200 and 2480 x 1396.
Have fun playing and see this build as something to play and test with until we Danne, Dfort and I get other 6D presets working in this fantastic build.
COOL!
Fast checking. You could probably erase this since powertiming regs already happens a bit below:
Test to erase this:
if (is_6D)
{
switch (crop_preset)
{
case CROP_PRESET_HD100_6D:
case CROP_PRESET_HD75_6D:
case CROP_PRESET_HD50_6D:
case CROP_PRESET_2K_6D:
case CROP_PRESET_ULTRA_HD_6D:
case CROP_PRESET_4K_6D:
case CROP_PRESET_5K_6D:
case CROP_PRESET_FullRes_6D:
case CROP_PRESET_HD2_6D:
case CROP_PRESET_1x3_6D:
case CROP_PRESET_1x3_24FPS_6D:
case CROP_PRESET_3x3_1X_6D:
/* all modes may want to override shutter speed */
/* ADTG[0x8061]: shutter blanking for 3x3 mode */
/* ADTG[0x805F]: shutter blanking for zoom mode */
adtg_new[0] = (struct adtg_new) {6, 0x8061, shutter_blanking};
adtg_new[1] = (struct adtg_new) {6, 0x805F, shutter_blanking};
/* adjust analog gain NOT WORKING PINK HIGHLIGHTS WHITE LEVEL NOT PROPER*/
/*adtg_new[13] = (struct adtg_new) {6, 0x8882, 108};*/
/*adtg_new[14] = (struct adtg_new) {6, 0x8884, 108};*/
/*adtg_new[15] = (struct adtg_new) {6, 0x8886, 108};*/
/*adtg_new[16] = (struct adtg_new) {6, 0x8888, 108};*/
/*adtg_new[17] = (struct adtg_new) {6, 0x8030, 400};*/
/* adjust vertical resolution */
/* assuming FPS timer B was overridden before this */
int fps_timer_b = (shamem_read(0xC0F06014) & 0xFFFF) + 1;
int readout_end = shamem_read(0xC0F06804) >> 16; /* fixme: D5 only */
/* PowerSaveTiming registers */
/* after readout is finished, we can turn off the sensor until the next frame */
/* we could also set these to 0; it will work, but the sensor will run a bit hotter */
/* to be tested to find out exactly how much */
adtg_new[2] = (struct adtg_new) {6, 0x8172, nrzi_encode(readout_end + 5) }; /* PowerSaveTiming ON (6D/700D) */
adtg_new[3] = (struct adtg_new) {6, 0x8178, nrzi_encode(readout_end + 5) }; /* PowerSaveTiming ON (5D3/6D/700D) */
adtg_new[4] = (struct adtg_new) {6, 0x8196, nrzi_encode(readout_end + 5) }; /* PowerSaveTiming ON (5D3) */
adtg_new[5] = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (6D/700D) */
adtg_new[6] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[7] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5) }; /* PowerSaveTiming OFF (5D3) */
adtg_new[8] = (struct adtg_new) {6, 0x82B6, nrzi_encode(readout_end - 5) }; /* PowerSaveTiming ON? (700D); 2 units below the "ON" timing from above */
/* ReadOutTiming registers */
/* these shouldn't be 0, as they affect the image */
adtg_new[9] = (struct adtg_new) {6, 0x82F8, nrzi_encode(readout_end + 5) }; /* ReadOutTiming */
adtg_new[10] = (struct adtg_new) {6, 0x82F9, nrzi_encode(fps_timer_b - 5) }; /* ReadOutTiming end? */
break;
}
Regarding not working presets. For 1x3 presets you use the adtg slots:
adtg_new[11] = (struct adtg_new) {6, 0x8000, 6};
adtg_new[12] = (struct adtg_new) {6, 0x800C, 0};
Now check in powertime regs:
adtg_new[11] = (struct adtg_new) {6, 0x82F8, nrzi_encode(readout_end + 1 + reg_timing4) }; /* ReadOutTiming */
adtg_new[12] = (struct adtg_new) {6, 0x82F9, nrzi_encode(fps_timer_b - 1 + reg_timing4) }; /* ReadOutTiming end? */
adtg_new[11] and adtg_new[12] are overwritten.
Expand this from:
/* expand this as required */
struct adtg_new adtg_new[22] = {{0}};
to maybe:
/* expand this as required */
struct adtg_new adtg_new[32] = {{0}};
To get free adtg slots. Wouldn´t hurt if you check your other presets for doubles.
Nice find!
Those double used adtg slots sure don't help :P
Will fix them when I have some time, will be continued...
Ok 6d owners, posted a new build, some new progress in the merged crop_rec build.
Now 1x3 presets are working too and 50 fps for Canon 720p mode works(non stretched, square pixels).
Unfortunately I haven't been able to fix Canon live view in 1x3 modes (probably because it's so weird, horizontal binning and full vertical line readout)
Modes available are:
"2480x1396 25fps for 5x zoom mode"
"2688x1296 25fps for 5x zoom mode"
"2880x1200 25fps for 5x zoom mode"
"1216x2052 1x3 25fps for 5x zoom mode",
"1640x2144 1x3 24fps for 5x zoom mode",
"1824x818 50fps for 720p mode"
Low bit depth option in copy_rec sub menu (Q button on crop_rec option in ML menu)
Here's the full ML build for 6d:
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May13.6D116.zip (https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May13.6D116.zip)
Cool.
How come 1x3 binning is set in x5 mode?
@baladev
This new build contains two 1x3 presets.
I have chosen to put 1216 x 2052 at 25 fps in, since I think this one gives continues recording time, if bit depth option is set to 12 bit (or when in doubt, use 10 bit).
I made the 24 fps 1x3 preset to full width resolution, 1640 x 2144.
The 24 fps has a little more vertical resolution, this is possible of the lower fps (25 vs 24 fps), this 2144 resolution is unfortunately not possible with 25 fps.
Try them out and see if you like them or that you missing something, we can always put more 1x3 presets in this merged build :D
Quote from: Danne on May 13, 2019, 06:34:22 PM
Cool.
How come 1x3 binning is set in x5 mode?
In my older crop_rec module, I made the presets for use in x5 mode, not sure why :P
At the moment you can't even use them in normal 1x zoom mode, although ML preview is perfectly fine.
When recording 1x3 in 1x zoom, you get corrupted frames, not exactly sure why ???
Probably has something to do with something set in raw.c for EOS-M, because whenever a crop_preset is used, raw menu shows only 1/3 of the vertical resolution available in 1x zoom mode ?
And the text, stretch to 3 in post to get x resolution.
When this is fixed, 1x3 probably works in both modes.
Thank you Levas! Will test this new build tomorrow.
1216 x 2052 at 25 fps is good enough for me :). It has a nice 1.5 crop. Just wonder, why isn't 25fps possible with 1640 x 2144?
I film band performances a lot indoors in dark, club like environment. 1216 x 2052 at 25 fps gives me continuous at 14 bit even.
I'm sure even 1640 x 2144 would be continuous with 1264 x 2144 16:9 and 25fps for me. 12bit is very useful outdoors or in bright indoors situations.
I was thinking a couple of day ago - we are SO CLOSE to the sweet 1280x2160, which could give as exactly x2 resolution vertically and 2/3 resolution horizontally, comparing to 1080p.
Levas' original 1:3 preset (1088 x 1842 )was in x1 zoom mode. Later, when he went to higher res, had had to switch to x5 zoom, don't remember why - he mentioned this a few pages back. They still work in x1 zoom mode, just exposure is off, doesn't work properly.
[edit]
Just tested the latest build from Levas, here's what I found:
- 2880x1200 25fps seem to work properly, tested 14/12bit. didn't find anything wrong with it. Couldn't get ML preview though for framing, only Canon LV, which is way off.
1216x2052 1x3 25fps and 1640x2144 1x3 24fps both work properly with ML preview, tried diff bitrates 14/12/10 - no problem there. The only weird glitch I found with both these anamorphic presets is that after about 30-40 sec you get this pink 'fog' that starts at the top of the frame and quickly fills almost the whole frame down to the bottom, making the picture pinkish. You can easily see it in ML preview - just leave the camera for 30 sec and watch the screen. When the screen gets pink, going to ML or Canon menu resets it to normal until it happens again.
Will test 2480x1396 25fps preset a bit later.
Just find out, that when processing the MLV's with "mlv_dump_on_steroids.osx" I don't get valid audio wave files anymore (only 2Kb or something), this is since the merged with Danne builds.
Remember reading something recently on the forum that audio is not broken or something and data is inside the MLV, so I tested MLV_app and extracted the dng's and audio files and with MLV_app I do get a valid audio wave file.
I do have a mlv_dump_on_steroids.osx from 2017, do I need a newer version, does that fix the thing with audio wave files, and where to download a precompiled osx version of mlv_dump_on_steroids ?
Test following:
https://www.magiclantern.fm/forum/index.php?topic=7122.msg215668#msg215668
"--skip-xref"
Didin´t have time to dig into what´s causing this.
Did some more testing of the latest build.
All these presets work properly, I couldn't find any problems:
2480x1396 25fps
2688x1296 25fps
2880x1200 25fps
Framing works well, half shutter press takes to live view x5 for focusing. Very nice.
A couple of things I've noticed while playing with this latest build. 1 the compulsory 2nd and 3rd corrupted frames have disappeared. 2nd it feels more solid overall, hard to break ML preview (in the previous version it was very easy to break it with anamorphic presets)
Great job, Levas and Danne!!!
Added this:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg216553#msg216553
also for the 6D so hopefully some more headroom:
Commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/3127edf6890e88d5aaa2b039d6f8bef323d3eccf
(only anamorphic(1x3 binning) modes and with preview set to framing.
Levas confirmed working so let´s wait and see...
First tests show that I can't get more vertical resolution in 1x3 presets with the above experiment from Danne.
Still corrupted frames when I increase vertical resolution, so unfortunately it doesn't help us with breaking the current boundaries with vertical resolution, on 6d that is.
Gonna test some more tommorrow.
Levas
Even if you can't get any more resolution it's ok, you've done amazing work already even with what we have.
Have you had a chance to look into the "pink fog" issue I described above? It's really the only thing that's broken in the latest build that I could find and that prevents anamorphic presets to be useful.
Quote from: Levas on May 16, 2019, 06:56:33 PM
First tests show that I can't get more vertical resolution in 1x3 presets with the above experiment from Danne.
Still corrupted frames when I increase vertical resolution, so unfortunately it doesn't help us with breaking the current boundaries with vertical resolution, on 6d that is.
Gonna test some more tommorrow.
Did you match resolution in mlv_lite.c after increasing in crop_rec.c? Or else it runs without the hack.
I did match 6804 resolution in both places (top and bottom table in code below) in mlv_lite.c
if ((PREVIEW_ML) && (cam_eos_m || cam_100d || cam_650d || cam_700d || cam_6d))
{
/* Will maybe reduce corruption of frames by freezing liveview while in framing mode. To be tested */
if ((RAW_IS_RECORDING && (shamem_read(0xC0F06804) == 0x79f01ed)) ||
(shamem_read(0xC0F06804) == 0x77701ed) ||
(shamem_read(0xC0F06804) == 0x79f01d4) ||
(shamem_read(0xC0F06804) == 0x79f01e4) ||
(shamem_read(0xC0F06804) == 0x7ef01d4) ||
(shamem_read(0xC0F06804) == 0x88501c2) ||
(shamem_read(0xC0F06804) == 0x8230150) ||
(shamem_read(0xC0F06804) == 0x87f01ba))
{
EngDrvOutLV(0xc0f383d4, 0x4efffc);
EngDrvOutLV(0xc0f383dc, 0x42401b2);
}
bmp_on();
}
}
else
{
if (lv_focus_status == 3)
{
autofocusing = 1;
}
if (get_ms_clock() - last_hs_unpress > 500)
{
long_halfshutter_press = 1;
}
/* trying a fix for stuck real time preview(only affects framing) */
if ((PREVIEW_ML) && (cam_eos_m || cam_100d || cam_650d || cam_700d || cam_6d))
{
/* might reduce corruption of frames by freezing liveview while in framing mode. Here we are back to real time preview */
if ((RAW_IS_RECORDING && (shamem_read(0xC0F06804) == 0x79f01ed)) ||
(shamem_read(0xC0F06804) == 0x77701ed) ||
(shamem_read(0xC0F06804) == 0x79f01d4) ||
(shamem_read(0xC0F06804) == 0x79f01e4) ||
(shamem_read(0xC0F06804) == 0x7ef01d4) ||
(shamem_read(0xC0F06804) == 0x88501c2) ||
(shamem_read(0xC0F06804) == 0x8230150) ||
(shamem_read(0xC0F06804) == 0x87f01ba))
I see. Well, testing on 100D I clearly get a difference. Not neccessarily gonna lead to higher resolutions but will strengthen existing ones.
Quote from: baladev on May 16, 2019, 07:28:42 PM
Have you had a chance to look into the "pink fog" issue I described above? It's really the only thing that's broken in the latest build that I could find and that prevents anamorphic presets to be useful.
@Baladev
Did mis that in your first post :P
Looked at it, and indeed with 1x3 presets, after a while 'pink fog' starts to appear at the top of the frame.
The first time I saw this behaviour was when I made 1x3 presets with max resolution of 1640 instead of 1688, including lower A timer registers.
This was then sort of fixed by adjusting some values in power save timing piece of the crop_rec code.
Will have a look at it, and see if something is wrong.
I couldn't get the whole frame pink, only upper part of the frame becomes pink.
I have only raw histogram activated, no other stuff like zebras, spotmeter and such.
Not sure what you have activated, could be that closing some of these exposure tools stuff helps ?
Updated new build for 6d.
Few useful updates, in the previous build, I expect that dual iso module gave error message on screen when activated ?
At least I had on my 6d.
Dual-iso works on my 6d, so I expect it to work on other 6d's too.
More info about the issue and how it is fixed:
https://www.magiclantern.fm/forum/index.php?topic=7139.msg197146#msg197146 (https://www.magiclantern.fm/forum/index.php?topic=7139.msg197146#msg197146)
And I have changed something that might fix the "pink fog' problem in 1x3 presets, the first timer still had "(fps_timer_b - 1 + reg_timing3)" instead of "(fps_timer_b - 5 + reg_timing3)" in the middle.
adtg_new[7] = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 5 + reg_timing3) }; /* PowerSaveTiming OFF (6D/700D) */
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3) */
@Baladev
Did test the 1x3 preset for about a minute, I didn't get pink fog in the upper part of the frame, can you test and confirm.
If the pink fog still comes up, I can change some other values too.
To test you can download completely build below, and just replace dual-iso module and crop_rec module with the ones on your card, should work too.
New build:
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May19.6D116.zip (https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May19.6D116.zip)
@Levas
Thank you for the new build, will test it shortly.
For now want to show you how the pink fog worked on my 6D:
Normal frame (actually, if you look closely, there's some pinkness on the very top already):
(https://i.ibb.co/CvFNrZy/M20-0004-frame-588.jpg) (https://ibb.co/CvFNrZy)
When it starts:
(https://i.ibb.co/1qpWjYf/M20-0004-frame-836.jpg) (https://ibb.co/1qpWjYf)
..it quickly becomes like this and stays so:
(https://i.ibb.co/Jx1MPdf/M20-0004-frame-1063.jpg) (https://ibb.co/Jx1MPdf)
BTW, I have nothing activated in the Overlay menu, only GD set to LV
Are you still getting this in the latest build?
If so you can try and lower the regs pointed to through crop mode sub menu under advanced. That is levas is running the same build I use.
@Danne
Haven't tested the latest build yet. The frames above are from the previous build just for the record and so that Levas could compare with his results.
With the previous build, I have seen it like Baladev shows in the second picture, only top got pink.
But I have seen the 3d example in test builds :P
I'm using the crop_rec build from Danne, so he is right, you could play further around with reg_timer registers and see if it helps. (in submenu of crop_record, advanced options shows more register values you can play with)
This is sort of a black box for me, A1ex made the first version of it, it handles register for frame timing.
/* these should work on all presets, on all DIGIC 5 models and also on recent DIGIC 4 */
if ((1) && (CROP_PRESET_MENU != CROP_PRESET_mv1080p_mv720p_100D) && (CROP_PRESET_MENU != CROP_PRESET_3xcropmode_100D) && (CROP_PRESET_MENU != CROP_PRESET_3x3_mv1080_700D) && (CROP_PRESET_MENU != CROP_PRESET_3x3_mv1080_650D))
{
/* assuming FPS timer B was overridden before this */
int fps_timer_b = (shamem_read(0xC0F06014) & (0xFFFF + reg_timing5));
int readout_end = shamem_read(is_digic4 ? 0xC0F06088 : 0xC0F06804) >> 16;
/* PowerSaveTiming registers */
/* after readout is finished, we can turn off the sensor until the next frame */
/* we could also set these to 0; it will work, but the sensor will run a bit hotter */
/* to be tested to find out exactly how much */
adtg_new[4] = (struct adtg_new) {6, 0x8172, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (6D/700D) */
adtg_new[5] = (struct adtg_new) {6, 0x8178, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (5D3/6D/700D) */
adtg_new[6] = (struct adtg_new) {6, 0x8196, nrzi_encode(readout_end + 1 + reg_timing1) }; /* PowerSaveTiming ON (5D3) */
adtg_new[7] = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 5 + reg_timing3) }; /* PowerSaveTiming OFF (6D/700D) */
adtg_new[8] = (struct adtg_new) {6, 0x8179, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3/6D/700D) */
adtg_new[9] = (struct adtg_new) {6, 0x8197, nrzi_encode(fps_timer_b - 5 + reg_timing2) }; /* PowerSaveTiming OFF (5D3) */
adtg_new[10] = (struct adtg_new) {6, 0x82B6, nrzi_encode(readout_end - 1 + reg_timing6) }; /* PowerSaveTiming ON? (700D); 2 units below the "ON" timing from above */
/* ReadOutTiming registers */
/* these shouldn't be 0, as they affect the image */
adtg_new[11] = (struct adtg_new) {6, 0x82F8, nrzi_encode(readout_end + 1 + reg_timing4) }; /* ReadOutTiming */
adtg_new[12] = (struct adtg_new) {6, 0x82F9, nrzi_encode(fps_timer_b - 1 + reg_timing4) }; /* ReadOutTiming end? */
}
Quote from: baladev on May 19, 2019, 04:34:26 PM
@Danne
Haven't tested the latest build yet. The frames above are from the previous build just for the record and so that Levas could compare with his results.
Ok, you need to specify exactly what build used since it might very well not be a problem for a a week or two at least.
Quote from: Danne on May 19, 2019, 04:50:15 PM
Ok, you need to specify exactly what build used since it might very well not be a problem for a a week or two at least.
Ok, sorry, it's the build from message 1124, which was the previous build posted.
Which is magiclantern-Nightly.2019May13.6D116.zip
Update:
Just downloaded and tried the latest build magiclantern-Nightly.2019May19.6D116.zip
Did a quick test (by looking at the screen) - pink fog thing seem to have gone - couldn't see any. Will do a proper test tomorrow, but looks very good!
Will also test centering for all presets in this build.
Levas, do you want me to test dual iso module?
Thanks!
Checking the reg a1ex specified 6D already so good find Levas. I missed it before since I fixed on my 5dIII. Fog should be fixed on 6D.
adtg_new[7] = (struct adtg_new) {6, 0x8173, nrzi_encode(fps_timer_b - 5 + reg_timing3) }; /* PowerSaveTiming OFF (6D/700D) */
Confirming the fog in anamorphic presets is gone in the latest build by Levas. Filmed for 10 minutes and it didn't occur.
Hey guys,
I've been playing around with these modules for quite a while and "normal" RAW recording works nicely. However, these 5x zoom modes and 1x3 rec modes are confusing. I've tried to combine multiple settings, but never seem to get it right. Would it be possible to give a kind of baby steps setup explanation? Perhaps a short recording of which menus to check?
@arkasa
Just read the thread starting from around the middle of 2018 until now (maybe even twice - i didn't get some things from the first read), almost everything you need to know is there.
I forget how obvious some things are if you're using ML for years.
But I wonder if you know what is possible with 5x zoom without crop_rec module.
So normal raw recording goes fine. As you probably know, you can't select higher resolution then 1824 pixels wide in raw video menu.
Now press magnify button until you are in 5x zoom. (without any crop_rec setting enabled).
Now, while you are in 5x zoom go to raw video menu and see what is now the max selectable resolution...wowaa suddenly 2688 x 958 resolution is possible.
With magic lantern it's possible to hit record button while you are in 5x zoom.
Now the crop recording module, this module makes it possible to stretch these resolutions even more. For example 2880x1200 preset makes it possible to select 2880x1200 resolution, but it's made for use in 5x zoom mode, and only works when you are in 5x zoom mode.
Also frames per second is fixed with crop_rec module, you can't use it with fps override option in magic lantern.
For the 1x3 presets, it's nessecarry to change aspect ratio to 1:2 otherwise you can't select max vertical resolution.
Let me know if this info works for you, good luck 8)
Is there a reason why my camera creates
_MG_2846.JPG
and
IMG_2767.JPG
Is there a way to stop saving seperate files?
It always happens since 2018 ...
Didn`t find any hints yet
by the way is
2018-07-02 the latest version available? No further planned or maybe other branch with new name?
Quote from: cobra98 on July 11, 2019, 11:39:16 PM
by the way is
2018-07-02 the latest version available? No further planned or maybe other branch with new name?
Download the latest build from here:
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/
May 19 works well, though I experienced some glitches in crop mode with it.
Hi guys, new Here!
Firstly I wanted to say a huge thank you to those who have worked hard to bring us all the amazing stuff in Magic Lantern. It was a few years ago I first had a play with ML on my 6D, back then I chose to abandon it after finding it very time consuming and confusing working with the files as well as the very limited record times available on the 6D. I have only just now decided take another look at Magic Lantern and I'm so glad I did, some of the recent advancements that have been made with compressed DNG coupled with better apps for workflow have made it soo much more usable. And after doing some testing in 12bit RAW, running MLVHS into DaVinci Resolve I'm pretty stoked with the results.
I do have a couple of questions I'm hoping someone can help clear up for me, would be greatly appreciated as I'm still reasonably new to ML.
1. What is the aim of the crop_rec mode? I'm assuming this uses a smaller region of the sensor? Was it created to help avoid aliasing? Just trying to understand what the use of this mode is compared to the normal mode.
2. Is it possible to get decent slow motion with the 6D (without too much aliasing)?, if so which mode/resolution should I be using?
3. How do I get the SD UHS hack on the 6D?
4. Which is the latest and greatest crop_rec module for the 6D? Currently running the latest 6D crop-rec build from the experimental builds page.
Thanks in advance!
The latest super experimental build for 6d is in the post above your post.
This build also has SD-UHS hack module in it.
I believe this build has the SD-UHS module, when activated in module tab, it automatically loads at each camera startup, so you won't even notice it's there. (You can check in ML menu on the debug tab there is a menu item in there that shows overriden memory or something, if you look there you will also see override stuff from SD-UHS hack)
SD-UHS doesn't work with all memory cards, it sets the SD card writer in camera to a specific high write speeds SD UHS I specification setting.
It does work perfect with Sandisk extreme pro UHS-I U3 cards, the types which mention 95MB/s or 170MB/s on the card.
If your card doesn't support the settings used in SD_UHS hack, the camera writes as the same speed as before, or sometimes even much slower.
Trying to answer some of your questions:
1. What is the aim of the crop_rec mode? I'm assuming this uses a smaller region of the sensor? Was it created to help avoid aliasing? Just trying to understand what the use of this mode is compared to the normal mode.
I don't think there was a goal or aim from the beginning, crop mode just happens to be a mode already available, and people discovered cool usages for it.
Crop mode is something that is standard available in Canon cameras, Canon uses it for 5x zoom live view.
Most Canon camera's can't record video while in 5x zoom/crop mode, the 600d and 60d however had some sort of option to record video while in zoom mode.
So somebody from the ML developers soon found out you can also record video in this mode on all other camera's ( Where canon didn't give you that option standard)
This option actually records at 1:1 pixel readout, so it actually gives you a 3x zoom (because it only uses 1/3 portion of your sensor, instead of the whole width)
Later on, ML developers found out that you could increase resolution while in this crop mode.
This gave birth to the high resolution crop modes Alex introduced on April 1 few years ago.
Because crop mode is in 1:1 pixel readout, it has almost no aliasing compared to normal full sensor view mode.
2. Is it possible to get decent slow motion with the 6D (without too much aliasing)?, if so which mode/resolution should I be using?
The build in the post above has a 50fps crop mode, which has the same amount of aliasing as normal non slowmotion video on 6d.
The 50 fps mode has to be used with the camera in 720p50 mode, in normal 1080 mode the camera freezes in 50fps mode and you need to pull out the battery to fix it again :P
Also vertical resolution is limited to about 800 pixels.
3. How do I get the SD UHS hack on the 6D?
Download the ML build from the post above
4. Which is the latest and greatest crop_rec module for the 6D? Currently running the latest 6D crop-rec build from the experimental builds page.
The one in the build in the post above.
P.S.
The build 2 posts above is a merge with Danne's build, mostly aimed at eos-m.
There is a submenu in crop_rec (press Q button while on crop menu).
There are many options there, which aren't integrated with 6d, so most options do nothing, the most useful option does work, that is lower bitrate option, so you can use 12-bit or 10-bit option in crop_rec submenu.
Latest sd_uhs code should be used from my branch. There's some reconfiguration code put back which handles patching better on supported cams.
Didn't know that, will check it out and make sure that I put up a compiled build from this updated sd_uhs module.
Although I must say that I never experienced any issues with the sd_uhs module which is in the build a few posts up, the build from May.
Did some testing with latest sd_uhs code from Danne, but it doesn't work for 6d.
I get some nasty errors and wasn't able to record a single clip.
If started up in photo mode, camera card reader led turns red and never turned off, until battery pull :P
And in video mode, I get an error message on screen that it couldn't find the ML directory with masks (which was on the SD card) and when trying to start record it says, card full.
So thinking about it, I think it couldn't write or read to the sd card, once sd-uhs module was loaded ???
Once the module was disabled, everything was normal again.
So for now, best option for 6d is still the sd-uhs module available in the build mentioned a few post above.
Quote from: cobra98 on July 11, 2019, 11:37:26 PM
Is there a reason why my camera creates
_MG_2846.JPG
and
IMG_2767.JPG
sRGB and AdobeRGB.
I have an error with this version when i switch to C1 and activate HDR Mode in camera.
Anyone else?
Which might be a working build / stable?
Also i had on my canon 600D the possibilty that it calculates the perfect settings with "SET" key, on canon 6D i can only save with this feature 2 setttings i define
I think we have a problem understanding and reproducing your issue.
Can you please explain in detail the expected/wanted behauviour/feature set and what is actually happening?
Hey there! I did a few tests with the new presets, but I get a "compression error" every time I try to record a clip in any other than the 50p mode (that one works just fine, oddly enough) I'll attach the error messages I get. Is this a known user error (i.e. Am I doing anything wrong?).ML ASSERT:
0
at mlv_lite.c:2753 (compress_task), task compress_task
lv:1 mode:0
compress_task stack: 1e3338 [1e33c8-1e23c8]
0x0044C9B0 @ c23bfc:1e3368
0x0044C478 @ 44ca0c:1e3338
Magic Lantern version : Nightly.2019May19.6D116
Mercurial changeset : 6c6f37e9adfc+ (crop_rec_4k_mlv_snd_isogain_1x3_presets) tip
Built on 2019-05-19 13:23:44 UTC by magic_lantern@Vasses-iMac.
Free Memory : 378K + 2241K
Not sure, but first thing that comes to mind is:
Did you select something else then 14 bit lossless in raw video menu ?
There is now lossless options in crop mode sub menu. I believe it's set on 12 bit lossless by default, not sure.
But if you use the lossless option in crop mode sub menu, you have to use 14 bit lossless option in raw video menu.
No, sadly this doesn't change anything - no matter which bitdepth, PAL or NTSC mode in canon menu, 24 or 25p in Canon menu, or other settings I select seem to make a difference - I always get an onscreen "data corruption" message and the LOG file posted above! Let me know if you have an idea how to test for specific things if you have any ideas. Am I really the only 6D user this happens to (because to me that always suggests that a user error is still the most likely scenario here^^)
So you are using the 19th May build from this downloadpage and nothing else:
https://bitbucket.org/Levas_EOS/magic-lantern/downloads/ (https://bitbucket.org/Levas_EOS/magic-lantern/downloads/)
Are you also using that build as it is, you didn't replace crop_rec module with another one ?
Before the merge with Danne's build, you could download only a single crop_rec file and use them in the nightly builds.
But since the merge with Danne's build, you have to download the complete Magic Lantern build and use the modules that come with that.
The crop_rec module at the bottom of the same download page can not be used in the Magic Lantern build from 19th of May.
This is because the 19th May build is slightly different to give extra options, like lower lossless bit depth recording through crop_rec submenu.
Hello everyone!
I tried to use crop_rec mode on 6D, but got strange glitch at the bottom of LV:
(https://i.ibb.co/W30NGTt/VRAM0.jpg)
This lane stays on recorded video.
This happens for all options in Crop mode dropdown. Is it expected behaviour or I missed some important settings for recording cropped video?
Also sometimes when I change crop mode (mostly to 1x3) I get this:
(https://i.ibb.co/QvQN3rF/VRAM1.jpg)
I'm using this version of ML: https://bitbucket.org/Levas_EOS/magic-lantern/downloads/magiclantern-Nightly.2019May19.6D116.zip
Hey all!
I think its finally this time, when I'm really thinking about installing ML on my 6D. Im mad, because stock firmware just sets a bitrate using some sort of script, and it is made for saving space. But i would want to have recording in Full HD 1080P with +/- 100mbps bitrate all the time. Is this possible in ML to record Full HD and set bitrate to specific amount?
I've also heard that there is a SD UHS mod that allows us to set writing speed to higher amount. Im using a Sandisk U3 card(mentioned above). I would be amazed, when i would have a possibility to record RAW video in Full HD at least for 15s. (in most my scenes its maximum time). Is it possible using a latest ML with a SD UHS hack? Or maybe you know the maximum bitrate, which I could use when recording in full hd 1080p with SD hack? Thanks for all inputs. Guys you're amazing.
Firmware 1.1.9 https://cweb.canon.jp/drv-upd/eosd/eos6d-firm.html
US hasn't been updated but UK offers it now:
https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos_6d.html?type=firmware
Because it fixes PTP and firmware update vulnerabilities I predict you will be unable to downgrade back to 1.1.6 without Canon Service.
70D got an update, too: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos_70d.html?type=firmware
@Dazer
Normal behaviour, most crop_rec presets are made for use in 5x zoom mode. (I think it says in the description in crop_rec menu, when selecting one of the presets)
Try again, and hit the magnify button on your 6d, until you are in 5x zoom (probably have to hit the button twice, first time is 1x zoom, then comes 5x zoom, after that comes 10x zoom)
It looks a bit buggy, but once you know how to use it (in 5x zoom) you will get used to it :D
@Levas
yeah, i've tried 5x zoom mode, but it just shows standard Canon zoom UI. After i press record button it returns to the screen on the first screenshot. Also in this 5x mode when i half press shutter button, camera doesn't zoom out to allow properly focus (i saw this stuff in couple youtube videos about crop_reс module)
Tried to record video in 2480x1396 mode and got video having 1920x1080 resolution with that glitched lane.
Does it work without RAW video recording? I kinda got it working with RAW but with much smaller resolution.
Hello, I'm planning to buy 6d, but maybe I'd like to use it as a webcam on streams so I need unlimited runtime and clean hdmi.
I know by design I cant have them, but with can I bypass it with magic lantern firmware (I saw multiple videos as in ML you can complitely disable overlays = clean hdmi, not sure about runtime)
Also, how sturdy shutter is? How long usally it lasts (i.e. 5d mark II lasts for 500k approx.)
Thanks
Ah no raw, that explains it.
The crop modes don't work with standard h.264 movie recording.
Once te recording is pressed, the camera switches to 1x zoom.
So for higher resolutions, you need to enable raw recording in ML menu.
Go to 5x zoom, hit trashcan button for ML menu. Use q button on raw video option to enter raw video sub menu. Set aspect ratio to 16:9 and scroll to resolution option. On resolution option, you can use the scrollwheel on top of the camera to set desired resolution.
Sorry for the *way too noob* question but when you're saying this nightly build works on 6D right now we assume a downgrade to 1.1.6 from a camera running firmware 1.1.8, right?
I just jumped into a 6D bought second-hand which was already on 1.1.8 and I'm pretty used to run ML on older 450D and 1100D borrowed from a friend for a while right now which certainly doesn't need any downgrades :P
So I apologize for the totally stupid sounding question amidst a quite interesting crop_rec conversation. Thanks in advance!
Do i understand correctly that "2480x1396" in the crop mode name only shows maximum theoretical resolution and actual recording resolution depends on selected raw settings (resolution, aspect ration, data format) and sd card specs?
Almost right.
Quote from: dazer on November 30, 2019, 07:43:10 AM
Do i understand correctly that "2480x1396" in the crop mode name only shows maximum theoretical resolution and actual recording resolution depends on selected raw settings (resolution, aspect ration, data format) and sd card specs?
SD card specs don't inlfuence any options, slower SD cards give slower recording times (camera stops recording once the internal buffer is filled up, internal buffer fills up when SD card isn't fast enough to handle the write speed.)
The crop mode actually changes sensor read out settings, so it only reads out that certain part/resolution of the sensor, the rest of the sensor isn't readout at all.
ML raw menu let's you select any recording options, within that part/resolution.
Hey there.
I saw a video on youtube where the creator says he is using the build: magiclantern-Nightly.2020Jul16.6D116
But here on the forum I can't find anything newer then Nightly.2018Jul03.6D116.
Does someone here know where this build is hidden?
Update: Found it: https://webcache.googleusercontent.com/search?q=cache:TWJAaqGudUEJ:https://www.magiclantern.fm/forum/index.php%3Ftopic%3D15088.1250+&cd=2&hl=en&ct=clnk&gl=pl
For those wondering why thread suddenly ends in '19, it was split and put in another subforum.
https://www.magiclantern.fm/forum/index.php?topic=25782.0
deleted
Would it be possible to allow an interval in half of quater or tenth of seconds for the intervalometer ?
Did all of you sell cameras since the discussion is dead for more than a year.
Sent from my SM-G973F using Tapatalk
<confused> What is a camera? </confused>
Does anyone have One Percent's old 6D repo saved somewhere? I'm looking to port some of his work that never made it to MAIN
Possibly here: https://bitbucket-archive.softwareheritage.org/projects/da/datadogie/tragic-lantern-2.0.html
I have not tested this at all. Where are you considering porting it to?
I'm trying to port headphone monitoring, ALL-i frame, and fullscreen magic zoom for my own personal EOSM builds. His work on EOSM and 6d were in the same repository. He figured out a lot of stuff in 2013 that worked fine but never got merged into main.
and btw, sir, you are awesome for pointing me to this! I never knew about "software heritage"
I downloaded the archive, it seems the basic structure is there but all the files have a ".i" extension and are displaying incorrectly in a text editor What is the procedure to converting these back into a useable folder?
oh....
Clone
To get back a normal repository, just do
hg clone $bare-repo-name $normal-repo-name
E.g., for jagan/bioreader.html, after downloading and decompressing 9d5f5e8e-a6ba-44d6-8bb4-5a689c66ef09-repository.tar.gz, do the following:
hg clone 9d5f5e8e-a6ba-44d6-8bb4-5a689c66ef09-repo/ bioreader
Wierd.... the HG clone command restores all the loose files in the root directory, but doesn't convert the subfolders, so I'm still trying to figure out a way to convert the files in the "platform" folder.
Hg is a mystery to me so I can't help there.
The features sound useful - if you get them working do please host them somewhere, so other people can benefit. It sounds like they might not require a crop_rec based branch. If that's true, it might be practical to integrate them with my repo: https://github.com/reticulatedpines/magiclantern_simplified
I found my old thread about all-i frames
https://www.magiclantern.fm/forum/index.php?topic=15685.msg152818#msg152818
can't find the videohackU file though :'(
I guess more and more are moving to mirrorless since thread is slowly dying...
Sent from my SM-G973F using Tapatalk