Messages

Thank you! Found some Bugs though

First one is my display going black if i enable Motion-detection, until some button is pressed
Second one is the detection box doesn't update correcly if i move it with the focus box

+1 for That...

Hey,

just thought it would be nice if you could move the detection-area for motion-detection around like you can with the focus-area

I can't set anything like this on my 600D

But anyways... This also happens if I convert the RAWs to JPG in Lightroom, thats what i don't understand.. o.O

I've been shooting a lot of Sports-Sequences lately..
And i ended up shooting in JPEG because the 600D can only take 6 RAW-Shots at its full (pure awesome.....) 4 Frames per Second...

I would really love to play around with the MRAW and SRAW files, but since i'm not brave enough to enable this functions on my camera, maybe someone who has done it could upload some small RAWs for me? Just to look how it would work

Use your Android-Phone or iPhone with an App, Let the Phone track your Time and Coordinates, Sync them afterwards on your PC with some programm like "Geosetter"

My T3i has the same "Problem".
I also believe this is an optics thing...

Bit i don't know if a simple offset would work, for every focus distance.

But maybe worth a try

So +1

Just do it the right way in Post, it'll be fine

rendertimes are killing me, and quality... its well... nothing special

Hi everyone,

don't know if im quite right here but anyways...

Today i noticed something I never noticed before.

All of my RAW-Files are, 5202 x 3465 Pixels in size
All of my JPG-Files are, 5184 x 3456 Pixels in size

Doesn't matter if they come out of Lightroom or directly from the Camera
and I'm wondering why?

Anybody knows?

Just wait a couple more days and you will have it

Didn't find time to yet, didn't even find time to test on Linux -.-
I also tried to contect the dev, but no luck

I didn't test but i think it should be possible with fps override
Just switch to 720p 50fps an then go for the fps override

Besides that, wy wouldn't you stick with ntsc? it makes roughly no difference.
I also live in a PAL country and never had any problems when using ntsc, and if you see flickering lights just play around with exposure time

will try tomorrow or tonight!

never mind

you're probably right .
but lets get back to topic here

@Alice5
Let's hack together!!

If i had time to do so -.-
Also my coding is miserable

Oh and it's Alia5 not Alice5, but never mind

Let's wait.

What?! Let's get onto code!

Sadly i'm a pretty crappy developer and don't want to risk my camera with my unbelievable awful coding >.<


But i would also like this... Could get a lot of lenses on an budget

I've started this post before that Alia5 posted his one. So before sending it i say, yeah, you idea of splitting the screen is fantastic, and really interesting. I see only 2 problems in that. The first is that some voices require space, else you risk to don't understand it. But probably it's not a big deal, because changing some words, decreasing a little bit the font dimension...

Maybe the text could also be scrolled, i think...
Also you could take too long settings into one line

And seeing it again the text has to be a lot smaller.

I'll try to get another idea of how to manage it smart and see a lot of things completely at once...

One should have the complete menu and one custom menu for the most used functions.
A bit like hiding the submenus you don't use, this menu will contain like 10 functions you have to change often.

I like this idea, but my problem with this is that you might forget some features or that you don't see new features if a lot are included in a new version...

What about the 600D?
I could try if.....

What about something like this?







This way we could see a lot of things at once and wouldn't need any scrollbars or tabs
Maybe we could also make the text a bit smaller, i dont know how it would look on the camera itself...

Quicktime licenses
https://developer.apple.com/softwarelicensing/agreements/quicktime.html

if it was possible, i think you could drive the fps-override in 640x480 mode already higher

Probably won't gonna happen...

Also you would loose quality because of the resizing...

i just compiled from your source and played a bit...

wichever values i choose, focusing never stops when it should in continous mode

also we could maybe tell the camera in wich direction to focus. so we could press a button to focus in or out when not in continous mode

sadly i dont have much time now to look at the code

 tested with the source of scrax

when i tried to change my input source the camera went crazy... magic lantern menu scrolled from left to right extremely fast and camera didn't respond to any button...

anyone else expirienced this? o.O