Messages

F**K OFF YOU C**TS.

IT WILL BE SUMMER AND 650D STILL WONT BE READY. all you saddo's kissing arse, your better off not buying a 650D and having 600D at least you can put ML on it.

... and they try to tell us that the age of sensible debating skill is dead ...

[BOLD]

OK, here is my testing progress. Latest edit is in BOLD

Bulb Timer:              Not working. Can't find any Bulb setting on the 650D - not working on NightPortrait.

To find bulb on 650D, just keep scrolling shutter speed in M or Tv mode past 30 seconds and the next setting is B for Bulb.

Status update (since we are on a new page)

I'll strike out what's working (no comment means it requires prop_request_change)

Sorry, now I am slightly confused (better than being slightly mad I suppose). So you have crossed out the things that are working, is that right? So for example, Shutter Lock is now working?

Thanks for all your hard work. I hope you are allowing yourself time off to eat, sleep and for the performance of normal bodily functions?

Hi guys, I was just wondering if there will ever be a full implementation for this on the 650D, like there is on the 600D? How long will this be?

Well that is what this entire thread is about , it is clearly being developed. I gather from reading the forum that an alpha version may be due fairly soon, but other than that I don't think anyone can give you a definitive answer except to say "when it's ready".

[char bar[] __attribute__((aligned(32))) = "asdfghjkl;";]

char bar[] __attribute__((aligned(32))) = "asdfghjkl;";

I guess this has all worked before ... but...

I find the macros a bit hard to decode, but is it possible the semi-colon in the 'bar' string is causing some sort of premature termination in the test strings during the macro expansion?

Maybe change the ";" to another character?

Got it, thanks.

Looks like there's something going on with the strings, although I can't understand what.....

Where can we download the stubs code from please nanomad, it's not possible to look at that excerpt and deduce things aren't working as I don't think we can see what value of 'bar' has been set.

It's always possible the test code has some previously un-noticed bugs ... worth a second look.

Steve

Having a T2i and a T4i, I've been using the T4i as the 'A Camera' and the T2i as the B, since the T4i has the articulated screen, no 4GB limit and other small features, but I've really been missing the audio levels and such from the T2i with ML. 

The T4i has audio level meters (at least the 650D does, assume they are the same). In the menus find sound level and set it to manual whereupon audio level meters appear.

This may not be as good as the ML ones, I haven't seem them except on videos.

I expect, rather than trying to add new features, the team will first try and port ML to the new cameras, changing only what's necessary to make it work.

Once that has been achieved (and released as part of the unified ML), effort can then be spent - if chosen - on adding features.

I think it's more important to port ML as-is to the new cameras than to try and exploit new features they may offer at the same time. This, I'd think, would be the approach giving the best chance of success.

... or the cropped video from the 600D/T3i 

This is great news - I'd just bought a 650D but stupidly hadn't checked ML ran on it. Been grinding my teeth a bit.

Just made a small donation, in lieu of some practical help and to say 'thanks' to the team.

Steve

650D please.

I have a 1000D and have just ordered a 650D. Clever me to find the only ML incompatible cameras! I am just wondering if I should cancel the 650D order and get a 600D instead so I can use ML.

I use CHDK on an Powershot 570IS and it would be great to be able to use ML too.

Keep up the good work.