Messages

Great News! 

Yes the problem is solved now and the downgrade is still possible!

Thanks Walter.

Anyway it would be fine to have an edited 1.2.3 fw to downgrade from 1.3.3. in case Canon will really block the EOS Utility downgrade method.

I think that the problem was an EOS Utiliy or Windows bug, because one of the users told me that he was in live view mode and then he turned it off but all the settings in Eos utility remained greyed out with no chance to downgrade. I told him to reinstall the software and delete Windows cache, and this solved the problem, so the downgrade option is available again. 

The setup was: Windows 7 x64, USB 2, Eos utility from Solution disk version 28.5.

Already tried but nothing done! 
I'll wait for other users with 1.3.3 fw to try again. Meanwhile the users I talked with said that they went to Canon service and asked for the downgrade to 1.2.3. Canon technicians replied that they'll try but they are not sure to suceed.

a1ex could you try to remove the fw version check or mask the fw version of 1.2.3 fw?
Thanks

[Software issue solved]

a1ex is the key to sign .fir files changed?
If yes, is there a chance to edit the fw version in the old 1.2.3 and show it to the camera as 1.3.3 or 1.3.0?

From what some Italian users explained on the Facebook user group, it seems that canon has blocked the EOS Utility downgrade method. They tried with a few new and old versions of the software, but nothing done. Software issue solved

Caro Rikoshet, sono italiano pure io. 
Perito elettronico e amministratore del gruppo Magic Lantern Italia su facebook, se hai bisogno di una mano o se vuoi spiegare il progetto anche agli italiani iscriviti pure al gruppo.
https://www.facebook.com/groups/magiclanternitalia/

I'm the admin of the Magic Lantern Italia user group on facebook. If you are interested in sharing your project with italian users join the group.

@ nikfreak. To add file upload option to a google form take a look here: http://www.googleappsscript.org/user-interface/upload-doc

And here: https://developers.google.com/apps-script/reference/ui/file-upload?csw=1

As far as I know you can now upload photos into google forms. This could be a way.
Since I'm the admin of the Magic Lantern Italy user group of Facebook I could collect info and feedback (with photos and screenshots) in italian and then send all to you translated.
Let me know what you are planning to do.
P.s. I would be glad to try testing ML on 70D asap to start inform italian users about possible bugs and prepare an installation tutorial before the public alpha will be released.

That won't work, it's not just a matter of the version number. ML's functionality depends on calling functions in the Canon firmware. The addresses of these functions are found by reverse engineering the firmware dumps and are hardcoded into the ML source. With different Canon firmware versions these function address may change, so they have to be found again or ML won't function at all.

I don't mean to do this to run ML on another firmware, but just try this trick to downgrade to 1.2.3. By the way... if EOS utility makes the downgrade successful, we don't need this workaround.

For who that want to downgrade from 1.3.3, before use EOS utility, why don't try to rename the .fir file as 5D300133.fir instead of 5D300123.fir?

I was wondering if there is a way to edit the 1.2.3 original firmware masking it as 1.3.0 or 1.3.3. I think it should be easy to do, maybe we only need to change the version tag inside the code and compile the .fir. But for this we need help from a1ex because encription keys are needed, but I expect that Canon changed the encription from 1.3.0 version to avoid this workaround.

A1ex are you there? 

Hi, any news about .fir from A1ex?

I'm waiting to test it compiling the source by myself.

I'm keeping italian ML users updated here: https://www.facebook.com/groups/magiclanternitalia/

nikfreak let me know.

Now I'm testing with new Komputerbay 1066x 128GB CF (it should be the same of 1000x) and I'm comparing the Transcend 600x SD with the Sandisk Extreme 45 MB/s for Card Spanning.
I'll let you know the results.

Logically speaking the write speed can be achieved up to 350MB/s

aalloo you have to remember that, according to specs, the 5D mark III can write to CF with a maximum throughput of 160 MB/s.

1%, could your rc/vbr/cbr.ini work on ML 1.2.3?
Are there any news about bitrate on 1.2.3?
Thanks

Thanks for the info guys.
You are doing a great work!

Hi guys, I have a doubt. From which link do I have to start to build 5D3 1.2.3 source code?
Would be better to use this:  hg clone https://bitbucket.org/hudson/magic-lantern and than pull 1.2.3
or directly this: hg clone https://bitbucket.org/chris_miller/magic-lantern ?
Which link should ensure me the latest updates??

Thanks for your help!

Sorry about the stupid question.
How do you activate card spanning mode ?

First you have to enable the mlv module, than go into it's submenu and enable card spanning function.

Why you take at 30 and after exporting 24. Its better?
I thought at 24 you can rec more frames.

I recorded at 24 fps with FPS override, but raw2cdng doesn't recognize the exat fps. It recognizes 30 fps instead of 24, but it converts MLVs at 24fps without problems. I think it's only a raw2cdng graphic bug, because the converted files are at 24 fps, just like I selected with FPS override.
You have to use FPS Override because in crop mode the fps value goes automatically to 30fps and this would shorten the record lenght.

Good work! Congrats!
Can you describe how long support each take, and how you use to crop every shoot? You have to stay so far, really?

Thanks budafilms! Using the cards reported in the video description and recording at 2560x1090 2.35:1 I can record 400-500 frames per take at 24fps.

In which application did you process the spanned MLVs into DNGs?

I processed spanned MLVs directly in raw2cdng 1.4.9.3 (latest version at the moment). It converted all MLVs in .RAWs an than in CDNGs. Although I used the FPS override function, raw2cdng indicates all clips at about 30 fps, but converted files are at 24 fps without problems.

Thanks! 

I could use 23.976, but i prefered to use 24 fps to avoid problems with raw2cdng (it shows me 29... fps) and DaVinci Resolve about fps interpretation.

This is my latest test on MLV RAW, I filmed all with my 5D Mark III  in crop mode at 2.5K (2560x1090) with Card spanning.
I hope you like my work. Let me know what you think about it.

Regards
Andrea from Italy

Hi guys, I made this tutorial for italian users and you all. I hope you like it!

Tutorial installazione Magic Lantern in italiano.