hello Alex, if you remember about 2 months I reported that the April release ( i think) had that problem that let the recording stop at random due to high bitrates for some videos with no reason. I used that firmware for a project and still had the problem when you released an upgrade when I thought it was fixed. Now I installed the latest stable version 2.0.1 but at the first recording it happened again, buffer full! The card is not the problem with canon firmware it never happens and with ML I'm using the original FW bitrate.
T2i Magic Lantern for 550D in progress!
- Thread starter ...
- Start date
I made some tests and it doesn't seem to happen with the latest experimental . Did you change something that could have fixed it? I'm worried it's just like before that it just didn't happen NOW but the problem could appear later. I still wonder this only happens to me.
I have a question about ML: in the HDMI out that's forced to SD resolution, is it an anamorphic 4:3 image or a letterboxed one? Same question goes for ML composite out.
This may have been answered already. If so, sorry.
Thanks a1ex for all the work you've done on this!
This may have been answered already. If so, sorry.
Thanks a1ex for all the work you've done on this!
Hi,
I have like boiling banding artifacts on solid plates with my 550D (I haven't installed ML yet).
As I see other DSLRS - the same problem exists.
I would like to know - is it a problem of compression's quantization?
Moreover, will ML at CBR X2, for example, fix this issue?
Thanks,
Mark.
I have like boiling banding artifacts on solid plates with my 550D (I haven't installed ML yet).
As I see other DSLRS - the same problem exists.
I would like to know - is it a problem of compression's quantization?
Moreover, will ML at CBR X2, for example, fix this issue?
Thanks,
Mark.
FatBird19: it's 720x480 as far as I know (just like during recording).
MGX: you can check if it's a compression problem by taking a silent picture during recording. Silent pics are uncompressed YUV422 frames. Without seeing the image, it's hard to give advice.
Latest experimental build: http://bit.ly/ml-aug17
MGX: you can check if it's a compression problem by taking a silent picture during recording. Silent pics are uncompressed YUV422 frames. Without seeing the image, it's hard to give advice.
Latest experimental build: http://bit.ly/ml-aug17
So you mean there are no black bars on the footage? The widescreen image is stretched to fill the whole 720x480 4:3 frame?
I sure hope this is the case.
btw, has anyone ever reported their camera being bricked after installing ML? I've been holding off doing it myself cause I'm not sure of how much risk I'm taking on.
Been a while for me, just uploaded the Jul08 ML. My last install was in Feb. Quick question, i noticed that the ISO increments are the same as the stock in the camera, where as my Feb build had the in betweens. Is this just a setting, or, was it changed for a specific reason? Any feedback is greatly appreciated.
a1ex: I have successfully installed ML. Took a silent picture - the conclusion is that banding seems to be artifact of quantization, because 422 doesn't suffer from it and when I raise the CBR the artifact is a lot less visible. Thanks!
Dubez: In ML menu go to Tweak -> Iso selection. change it to 100x,160x.
Dubez: In ML menu go to Tweak -> Iso selection. change it to 100x,160x.
MGX: very interesting, can you share some test pictures? I'd like one with CBR 1x, one with higher CBR (whatever works for you) and one uncompressed.
FatBird19: it's like this: http://videos.smallhd.com/the-truth-about-canon-dslr-output-signals/
I didn't see it in action yet, so I can't tell you more, but the testers were happy with it
Most "bricking" issues were solved by taking the battery out, closing the card or battery doors, clearing all camera settings or formatting the card.
There were a few issues where cameras failed with ML installed, but it's not possible to determine the exact cause of the problem. From the descriptions of these issues, I believe the failures were due to hardware problems with the camera itself (not related to ML).
CHDK FAQ on this applies to ML too:
http://chdk.wikia.com/wiki/FAQ#Q._Can_CHDK_damage_your_camera.C2.A0.3F
Also it's a good idea to understand what you are actually running on your camera (the complete ML source code is available).
FatBird19: it's like this: http://videos.smallhd.com/the-truth-about-canon-dslr-output-signals/
I didn't see it in action yet, so I can't tell you more, but the testers were happy with it
Most "bricking" issues were solved by taking the battery out, closing the card or battery doors, clearing all camera settings or formatting the card.
There were a few issues where cameras failed with ML installed, but it's not possible to determine the exact cause of the problem. From the descriptions of these issues, I believe the failures were due to hardware problems with the camera itself (not related to ML).
CHDK FAQ on this applies to ML too:
http://chdk.wikia.com/wiki/FAQ#Q._Can_CHDK_damage_your_camera.C2.A0.3F
Also it's a good idea to understand what you are actually running on your camera (the complete ML source code is available).
FatBird19: it's like this: http://videos.smallhd.com/the-truth-about-canon-dslr-output-signals/
I didn't see it in action yet, so I can't tell you more, but the testers were happy with it
Most "bricking" issues were solved by taking the battery out, closing the card or battery doors, clearing all camera settings or formatting the card.
There were a few issues where cameras failed with ML installed, but it's not possible to determine the exact cause of the problem. From the descriptions of these issues, I believe the failures were due to hardware problems with the camera itself (not related to ML).
CHDK FAQ on this applies to ML too:
http://chdk.wikia.com/wiki/FAQ#Q._Can_CHDK_damage_your_camera.C2.A0.3F
Also it's a good idea to understand what you are actually running on your camera (the complete ML source code is available).
Wow, thanks a1ex. All of that helped a lot. Thanks very much!
quick question, i read the instructions and want to confirm i understood it correctly.
i have the july 8 build on both a t2i and t3i.
i would like to test the aug 17 release on the t3i. i have 2 sd cards for the t3i with the july 8 build.
can i copy the correct aug 17 ml build files to one of these cards and then boot to either card? the idea is to use the stable build i am familiar with but also see the new features of the beta build.
there is a different method for updating firmware with the new releases but not sure if these cards are already prepared with eoscard if i can just copy the new files and replace the july 18 files.
if that is correct and replacing files is all that is needed could i then use the sd card with the aug 17 build in both a t2i and t3i?
thanks in advance for clarification and ml rocks!!
i have the july 8 build on both a t2i and t3i.
i would like to test the aug 17 release on the t3i. i have 2 sd cards for the t3i with the july 8 build.
can i copy the correct aug 17 ml build files to one of these cards and then boot to either card? the idea is to use the stable build i am familiar with but also see the new features of the beta build.
there is a different method for updating firmware with the new releases but not sure if these cards are already prepared with eoscard if i can just copy the new files and replace the july 18 files.
if that is correct and replacing files is all that is needed could i then use the sd card with the aug 17 build in both a t2i and t3i?
thanks in advance for clarification and ml rocks!!
hi A1ex,
i've got some buffer problems yesterday after replacing a empty battery with a full one.
i was shooting some macro footage with a vintage Nikon lens and an extension tube with no buffer problems, when i see that my battery was empty (red icon), so i replaced it with a full one, and after that the buffer bar appeared and recording stopped after a few seconds.
i've tried today and i still have this problem.
never got this before, my sd card is a scandisk class 6 32gb with the july 08 ml firmware. but i never "re formated" my card between each ml update (i only overwrite the files). could it be the reason of this buffer overflow problem ?
thanks
i've got some buffer problems yesterday after replacing a empty battery with a full one.
i was shooting some macro footage with a vintage Nikon lens and an extension tube with no buffer problems, when i see that my battery was empty (red icon), so i replaced it with a full one, and after that the buffer bar appeared and recording stopped after a few seconds.
i've tried today and i still have this problem.
never got this before, my sd card is a scandisk class 6 32gb with the july 08 ml firmware. but i never "re formated" my card between each ml update (i only overwrite the files). could it be the reason of this buffer overflow problem ?
thanks