Messages

Google Search: quicktime gamma

Read this!
http://wiki.magiclantern.fm/userguide

And can you tell me, what is this "the liveview menu" you speak of.

After a totally accidental format in my PC the card is not accesible in the camera, it cannot format it or access it.

So your camera wont start when that card is in, right?
If so, then your card has "bootflag enabled" but no autoexec.bin in the root of the card.

Windows format won't remove bootflag when you format it.
And ML modified camera wont boot if card has bootflag enabled and no autoexec.bin.

Still no change, gives recording errors when increasing bitrate.

What recording errors?
Did you disable audio?
You can't record "audio on" more than 1.2-1.4x speeds.
You can only record h264 with 3.0x speeds when you disable audio.

Disable audio.
Only then you can record video at higher bitrate.

this is a feature request?

Yes it is.

All the 3x and 5x zoom mode raw recording have more than 5 dead pixels, at least on my camera.
It is funny that nobody else is seeing them. (or dont care)
To me red, green and blue pixels in video is a NO NO.
And manual removal is too painful process.

Adobe camera raw and Ufraw can read the dead (hot) pixel list from the source file but dcraw cant.

New version uploaded, updated the app with last bin (so it should work with also latest ML generated raw files). ffmpeg and dcraw should work now. link

For vertical lines latest ML code and 0.12 should fix it

TO DO:
Extract dead pixel list from dng and use it in dcraw to remove dead pixels.

Dcraw wont read the dead pixel information from the source file but needs an external list file.

@1%

Trying to compare crop mark and the recorded size i discovered that if you try to take LV screenshot (TL2.0) it just halts the camera.

*Card too slow

That cant be the reason for pink frames since we have "frame skip" or "end recording" to prevent card write problems.
And the whole frame data is there just not the right part of the picture.

Here is and example of how the picture is corrupting.
With some Photoshop lines.
Green = Pink part of the frame.

Also the recording area is not what the LV box is showing. (the small red line)



So are the pink frames coming from the crop code or the original sensor data, buffered/unbuffered?

@1%

To me it looks like the pink frames are coming from the second buffer usage.
Every time the <**.> second buffer * blinks i get 1 pink frame.

Can the buffer swapping be the cause of our pink frames?

Now audio is not working for 600D, will try to compare changes to fix it but probably in a couple of day

For me the latest code from repository works just fine. (600D)
Tested internal and external mic.
Not sure if its a bug or i just forgot to remove magic.cfg when testing different versions, the mic setting jumped from auto to internal mic only. 

Only thing that is still broken is in my ticket:
https://bitbucket.org/hudson/magic-lantern/issue/1520/audio-meters