Tragic Lantern for 6D

[ktabes]

Wow, how did they get a gh2 in space?


anyway...... Excited to see the development of the 6d, I thoroughly enjoy it as a still camera, and use the video function as more of a hobby, but this is definitely fun to watch this ml development process. I've still never encountered any moire (though i've only shot in 24p, no saturation etc.)
But I've had a few rolling shutter issues. I do enjoy it more than my 600d.

And keep in mind in this "what camera is really cool" ordeal.   I've seen amazing projects shot on mini dv, and non amazing projects on red's. It's about content, non the equipment. Give edvard munch a crayola and he'll probably impress you.

[1%]

What is the stock qp? Is it also variable?

Like 15-50. To get those low IPB rates it must not be very good. The all-I opens in avi-naptic and you can see the qp distribution. The IPB I hope follows the same deal. All I can see is average qp, but that seems to just be the max.

I guess one can compare the 2 config and stock. Nothing wants to analyze the IPB though. I want to avoid the defect but not make it pick worse qps in the process.

It's about content, non the equipment.

Truth, you don't want to be limited by equipment but it doesn't make the production.

[a1ex]

Its from kill flicker killing the zoom box.

Why do you need kill flicker? That's a ugly workaround for 50D, where I couldn't draw anything on screen without Canon erasing it...

[1%]

it kills the stuff that comes up when you press h/s

[a1ex]

And also other useful things (temperature warning, whatever pops on the screen without creating a new dialog box).

On most new cameras I chose to leave that stuff on the screen, and just pause ML updates until it disappears.

[1%]

scroll wheels didn't work either. any ay to just kill the half shutter dialog?

[a1ex]

Scrollwheels in menu? check GUIMODE_ML_MENU.

Halfshutter stuff can be cache hacked (around JudgeBottomInfoDispTimer stuff). Didn't try, because I like non-invasive solutions when possible.

[teo770]

I finaly success in instaling ML on Canon 6D, thanks all !
For other newbies like me, steps are:

- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software

- Get ML 2.3 from ML website:
http://bitbucket.org/magiclantern/magic-lantern/downloads/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2.zip

- Get 6d-112.fir from:
http://bit.ly/ZgvGUf

- Get the last autoexec.bin.something renaming it to autoexec.bin
from: https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads
+ 4 .ini files at the end of listing: h264.ini, cbr.ini, vbr.ini, rc.ini

- Place the new autoexec.bin and 6d-112.fir in the homedir of the SD card
- Place the .ini files in ML dir of the SD card

- Put SD card in camera and update firmware while in M mode. Restart. That's it.

[teo770]

Bug tracking

Is it the better place to submit bugs ?

Cause i don't want to submit already knows issues

Thanks

[a1ex]

There seems to be almost no known bugs, so post them here.

besides that most things work. pretty much where 600D was on 2.3 release

I'm not so sure.

[dlang]

- Make the SD card bootable using EOScard:
http://wiki.magiclantern.fm/3rd_party_software

I don't have a windows machine around to run this step on, does anyone know how to do this on a Linux box? (or if someone can point me at a _small_ image of a card that's been treated this way I can try to dig into it myself)

[teo770]

Lack: Audio / Headphone Monitoring

On the 5D Mark II, there was a jack 3.5 AV output, you could get headphones monitoring by using the AV cable supplied with camera or SESCOM cable.

On 6D, the AV output uses the USB port and without ML, just plugin the cable disabled the Liveview.
With ML, plugin the cable doesn't disable the Liveview, ML detect the plugged cable "headphones connected" but no sound is coming out on Red and white wires.

[teo770]

Dlang: i made you an iso of my SD card with ML 2.3 on

http://ge.tt/204RWcY/v/0

[dlang]

Dlang: i made you an iso of my SD card with ML 2.3 on

http://ge.tt/204RWcY/v/0

hmm, something went wrong. I unzipped the file I downloaded then wrote it to a SD card (via dd) and the camera says it can't read the card.

digging a bit more, this is a udf formatted card now, which makes sense if you made the contents of the card into an ISO, but as I understand it, there needs to be some specific things at specific places on the card for the camera to read it, which is what the eoscard tool does, so making an ISO of the contents won't work.

[a1ex]

See the install guide and click on the links

[eyeland]

Any rough ETA on 6D alpha1?

[teo770]

Bug displaying ML menus on LV

When not in LV, ML menus display normaly
When in LV, ML menus crash after 8 seconds every time
In the down right corner appears a kind of little red wheel and ML menus don't work anymore. You have to exit ML with del button and re-enter in ML menus.

Same thing happend in all modes: M, P... etc
I'm using "autoexec.bin.new icons"

[a1ex]

That's like EOS-M (probably 650D needs it too). I've enabled the M workaround for all cameras, but it's still not very clean.

[1%]

I get the red wheel and it just kills the scroll wheel. Menu doesn't cash tho (still works with arrows). this is in the latest though with no kill flicker. The piggybacked menu dies out?

also... on 6d MZ seems to work just fine in 60P. warning doesn't apply

you can post reproducible bugs on the repo issue page... probably better then losing it in here

I'm not so sure.

I've tried to test everything as best i can, even stuff i don't normally use.

ML detect the plugged cable "headphones connected" but no sound is coming out on Red and white wires.

making audio work is on the agenda. can somewhat communicate with the IC but no datasheet or anything yet

[a1ex]

And, from direct experience with ~10 ports, I know that it's way too easy for one person to miss things when testing. Especially that (you just said it) even basic menu navigation has problems...

For reference, here's some of the tests I've ran for the 5D3 alpha 1: https://docs.google.com/spreadsheet/viewform?formkey=dFRxbGZlUHYyOHB6SDZWZFVpUlVRTUE6MA#gid=0

and for 2.3: https://docs.google.com/spreadsheet/viewform?formkey=dG1FMjVQUEtjWV8zSlpaeEZtZDBQZ2c6MQ#gid=0

The menus changed a bit since then, so those checklists in google forms aren't quite up to date. I'm also pretty sure that current code base fails some of the valid tests described there. Maybe you can suggest something a bit easier to maintain (editing them is not quite easy).

Also take a look at the big bunch of fixes commited when I've got the 5Dc and the 7D. I've noticed a LOT of stuff present in menus and not working at all.

No offence to anyone, it's just that I know what I did to get something that doesn't crash every time you go out in the field. And it seems that I'm not there yet (still having problems with 5D3 ML, like random lockups or black pictures every now and then, and I can't quite reproduce them).

[1%]

I've had no issues with stills, mainly things that push the camera in LV.

I've noticed a LOT of stuff present in menus and not working at all.

Most of my menu stuff working working now, I've tried to comb through it and make sure. Some things aren't perfect. There is also the difference between someone like us operating the camera and someone unfamiliar with internals just wanting to shoot and go home.

Main thing with this is that I don't shoot in 720P nor use the wheels most of the time, was just happy to lose the canon dialog. But yea, kind of a big thing to miss. I have past bins up so if there is a regression please inform me about it and use a past bin till its fixed.

Before we hit a stable main page release, a lot of testing will have to be done and I'll probably need to make something like what you have here for 2.3 Its still the most working digic V port right now because it absorbed all the hard work from 5d3/m/650d, etc.

I've been implementing something or testing almost every day and have not had any failures when I really needed the camera. Nobody has done like a 14hr balls to the wall shoot with it though.

[teo770]

Bug: ML crash in LV
autoexec.bin.a1exscrlwheelfx kind of fixed the problem. Always the 8seconds gap, but instead of crashing, ML blinks as if it was restarted.

Bug: Central focus point gone
Just noticed this, either with autoexec.bin.a1exscrlwheelfx or autoexec.bin-nokillfflicker, central focus point disapears after ML loads or after focusing.

[1%]

>>Bug: Central focus point gone

That's a feature to hide the AF box.

[teo770]

  sorry

A feature we can disabled ?

[1%]

Yep. go to focus box settings, same as other ML variants.

Some test shots from this morning, stabilized with ae