Nevermind, Walter Schulz saved me in another thread.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: starley on October 08, 2014, 07:59:33 PM
Hello, I am working with two 700d cameras for record wedding and we are very interested in some options that magic lantern can give us. Principally, the peak, the vumeters and the middle step of ISO. We installed the magic lantern nightly.2014sept12.700d.113. And it works decently in the first look. But it is very important to know if i can trust in the stability of this version in a wedding recording we can´t have a fail with the camera, it could be very bad for our work. I would like that someone could respond about the question if i can use this version of magic for this three options or maybe another more stable version or at this time is not recommended use any versión for fieldwork.
Thanks to all and specially to the developers for this great work.
I´m sorry for my poor english
Quote from: mk11174 on June 26, 2014, 09:32:11 PM
So if you are using the June 25th Nightly, your saying this Vol64 module is not working for you? Because I myself tested it with the June 25th nightly and it worked perfectly, I get no error messages?
I don't know what has changed with the shutter speeds, I have not been coding for awhile so I have not kept track of all the new changes with ML.
Maybe you need to clean your ML config file and the module config files?
Quote from: mk11174 on June 26, 2014, 05:14:52 AM
I recently recompiled a version just last night to get my cams up to date and also the module. Let me know if this one doesn't work for you.
https://bitbucket.org/mk11174/700d113/downloads/VOL_64_June_25_2014.zip
Quote from: mk11174 on April 02, 2014, 06:45:16 PM
And yes, MZ flickers, no fix for that yet, but its not so bad of your not moving around much. I don't know what happen to the green indicator box for it, it has never had it or worked on this camera as far as I know.
Quote from: mk11174 on April 08, 2014, 10:47:52 AM
Hi, I just want to make note to protect ML from support questions while using the vol adjust module.
ML has nothing to do with the module, try at your own risk and if module is buggy, just ask me for help because it is not part of the great ML.
I don't want the Devs bother by questions for this module even though the module is very basic and straight foward, you adjust the mic input from 0 to 21 or 0 to 64, I know, sound hard
but I really want to make it clear for the Devs of ML, its not supported by ML, I will be your only support for it.
When the audio chip is coded by whoever, I will delete the module from the forum since it won't be needed.
Again, the values for the dB version are most likely wrong, I tried to get the real values and make sure they are what they say, but the document is to complicated for me
I just simply felt like beefing the GUI up so I did, simple as that.
But the modules, whichever you choose to use work just fine for what I intended, control mic input from within ML GUI and it works just fine for me and other users so feel free to try it out if you want.
Quote from: mk11174 on April 03, 2014, 06:50:21 PM
The audio meters should be working the latest nightly, I made the changes a few days ago.
Quote from: ThankMeLater on March 01, 2014, 02:01:58 PM
how do you guys handle the formatting issue ?
Is formatting the card on computer as good as on camera ? So far I allways formatted the card on camera, delted magic lantern and put it back on afterwards.
QuoteOr if i delete every single video on camera, is it as good as formatting ?
Quote from: mk11174 on March 01, 2014, 07:59:52 AM
Looking at the card1 shutter speeds, it looks like you are using the build right before my last one which does not have the fps/shutter fix because those are the exact speeds I was getting before the fps/shutter fix.
Maybe start over, delete the autoexec.bin and the ML folder on card1 and re-download https://bitbucket.org/mk11174/t5i/downloads/ML_700D_Meters_Feb_26_2014.zip and see what happens.
Card2 is the way you want it to be, that sounds like it is using the shutter fix.
The card type should not be changing any of these things.
Sometimes if you do a copy over of the autoexec.bin file and ML folder, something may not overwrite and you will be using the older versions, thats why its best to start fresh and delete them first and unzip the new ones to card to be 100% sure.
Quote from: mk11174 on February 26, 2014, 05:04:35 PM
If you would like an up to date build with audio meters I updated my version so it is up to date as of today Feb 26 2014. Also includes the fps/shutter value fix.
https://bitbucket.org/mk11174/t5i/downloads
Quote from: dmilligan on February 25, 2014, 05:40:52 PM
Perhaps try clicking on the word Features in that link you posted
Quote from: mk11174 on January 30, 2014, 03:58:09 PM
Ok, after trial and error debugging with Glassescreditsroll, I came up with a good temp solution for fulltime meters that works exactly the same on the 650d and 700d https://bitbucket.org/mk11174/t5i/downloads/ML_700D_Meters_Jan_30_2014.zip
Quote from: mk11174 on January 07, 2014, 11:51:32 AM
https://bitbucket.org/mk11174/magic-lantern/downloads/700D_all%20you%20need%20MagicLatern.zip
Page created in 0.140 seconds with 10 queries.