Menu

Show posts

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 Menu

Messages - funkysound

#1
@Walter Schulz

Ohh shit ... how stupid am I. Should have asked much earlier - Thanks a lot for this fast answer Walter!
#2
Camera-specific Development / Re: Canon EOS M
November 26, 2016, 10:49:06 AM
I just realized that "movie crop mode" does not show up under Modified if I use it. Is it supposed to be this way or does it just happen with my M?
#3
@OlRivrRat

I know about "My Menu" and also "Modified" - as far as I experienced this function it only shows what was changed and is still changed.
Even if this is a great help it is not what I meant.
If I change back a function to normal its gone from "Modified" after a new start and I have to go through the tabs again to find it.  On the other side functions stay available which I never or rarely change back to normal.
I thought about a kind of "My menu" inside ML which I can configure for my special needs.
Or did I get something wrong here and this is already possible?

#4
Hello again - didn´t write something here since a long time because ML did and still does work very good on my EOSMs and 600D. Thanks a lot for that!
I use them for a long time now for professional video making. Still love to use the old 600D because of the Audio Out option, 3x digital zoom combined with flexible the display. if I don´t have to use a 5D the 600D is my choice.
Now a bought a 70D too because of the better focus and the first thing was to install ML - great work again!
I have two questions:
Can you implement the 3x zoom in ML to have all functions available without changing to canon Menu and could it ever be possible to have an audio out too?
Another great thing would be (for all DSLRs) to have the possibility to compile a special department for the functions one is using often. Sometimes it takes too much time to jump through the Menu departments for changes like for example Audio overwrite on/of, WB control and 3x Focus, ...
I´m only using a few things of the ML possibilities in my daily work and this would help a lot for my workflow. What do you think?
#5
Camera-specific Development / Re: Canon EOS M
November 09, 2014, 01:18:00 PM
Hi Jaco2k this sounds interesting to me.
But ... Question: Is someone out there still working on ML or are all gone to Apertus?
#6
General Chat / Re: Apertus Axiom Beta
October 03, 2014, 12:23:23 PM
Quote from: nikfreak on October 03, 2014, 08:38:08 AM
a1ex said it now several times. He hopes to find a way to pay his bills so he has more time to contribute to ML.

I know and I always hoped he/they will find a way.
I also thought it would be better to charge little money for ML so he and the others would be able to pay the bills - than suffering and not beeing able to work on ML the way they would like to.
Whatever critics I wrote and will write - still: Thanks to a1ex and all the others for this great work. they offered for free!
#7
General Chat / Re: Apertus Axiom Beta
October 03, 2014, 12:12:54 PM
Quote from: budafilms on October 03, 2014, 10:54:58 AM
I´ve made my donate. I think A1ex should go and create an AXIOM ML Camera or sth like that for less money than super pro level. An standard model for 1000 Euros. It´s an idea. I will miss him ;)

I agree on this one - there would be a uge interest all over the world.
#8
General Chat / Re: Apertus Axiom Beta
October 03, 2014, 04:11:36 AM
Mhm ...nice thing - if you have a few thousand laying around and want to make big movies.
If I remember it right ML was supposed to "make a 500,-$ camera worth a few thousand $ camera" like one person said at the beginning and it started with a cam like the EOS 50d.
Since a few month everything fells like "let´s make a 5000,- $ or more camera ruin Hollywood" - this started with the 5dmark3 / raw ...
I don´t know but my impression is that the spirit of Ml got totaly lost - no new official version since ... anyway - a loooong time ... But mainly a great work on the top cam 5d3.
90% of the 5d owners I know - especial the profesional ones don´t use it even if they got it - and I know a few. RAW? Too much waste of time for them. If realy needed for a client they rent a propper cam because the budget is there.
Anyway - ML is a great thing and the Apertus Axiom idea is too - but the cams who really need ML know how (650d, 700d, EOSM, ...) are for shure not realy in focus since month.
It´s more like: It would be nice if someone cares for them too because we are more concentrating on making the "state of the art" cams to the "super state of the art" cams. And in reallity it´s not used like the ML team might think.
My guess: The Apertus Axiom Beta will not really become "the one" because there are just not enough people who need it and there will be not enough marketing and especial service power against Canon, Nikon, Sony, ... - but one or the other ML programmer may get good offers from the industrie.
Don´t get me wrong - I say thanks for all the great work in the past and I wish you all the best - it helped me to make my film business work with affordable equipment and lifted me to a higher level - but it seems to be over for youngsters who want to start now.
Or do you really think they got enough money for a Apertus Axiom + proper lenses + ...? Defenitly no!
ML was a good idea - but I´m afraid in the future mainly for the (maybe new) industrie. Like usual for growing ideas like ML is.

UPDATE:
Walter Schulz just wrote that ML was started for the 5d/2 and not for the cheap Canons like I wrote - ok, if it is so I had a wrong impression when I realized ML first time. Sorry for that one!
But I still think the real thing that made ML interessting for a uge amount of people (and upcoming professionals) was and also would be in the future to "make a 500,-$ cam worth a 5000,-$ cam". A great idea that did work and made the industrie sweat.
#9
Camera-specific Development / Re: Canon EOS M
September 11, 2014, 09:58:38 AM
"Had someone else the bug that he was not able to take a photo?"

Yes - we call it shutter bug here.
Sorry that nobody answered till now but I think everybody got tired to explaine everybody new here in this forum what is going on with it.
Just put the lens of while the m is on and it will work again after putting the lens on again.
Just search for shutter bug and you will find more answers ...
#10
Quote from: Yzgyz on May 08, 2014, 11:30:49 AM
Hi,
I've a problem: Since I've installed ML on my Canon EOS M, I cannont shoot photos, in any mode. It's still focusing when pressing half-shutter, but doesn't take a picture when pressing it through.

That´s an old known problem ... the shutter bug. Till now nobody found a way to fix it as far as I know.
If you read through this forum you will find diffent ways to solve it. If it is happening to me I just remove the lens while the M is turned on and put it on again - then it should work.
#11
Hi Holicow,
this is sometihing which makes everybody crazy and was mentioned a few times  - in older posts someone said that ii is not possible to increase the time here because it´s got to do with some canon internal time settings - if I remember it right
#12
I just installed a new ML Version (04.21.) and realized that there is no audio department any more (audio out). Does it come back with more features or is it gone forever because some things do not work with EOS M?
All the other stuff like shutter speed in Video modus seem to work good now - at least during a short test. I also had no shutter-bug with the 18-55.
#13
I just saw that there is a "EOSM.202.CLEANUP" Version in the Nightly Builds.
What is it and where is the difference compared to the normal EOSM.202 version?
#14
Quote from: glmccready on February 18, 2014, 04:14:51 PM
How do you stop ML from loading on the M.  With the t3i i just hold down the set button as it boots, but that didn't seem to work.   I did get the intervalometer to work just fine. Thanks!!

As far as I know there is no way to stop ML from loading - you have to uninstal ML or better use 2 cards. One with ML and one without.
But I agree that it is a good idea if this function would be there one day.
#15
Not 100 seconds just 1/100 - but the canon liveview display shows only the 100.
#16
Sorry a1ex - I thought you all know about this Bug.
In the video mode the shutter-speed-display just doesn´t show the right numbers like: It is 160" but shows 0" or even stranger this moment 0.-8".
In photo mode it seems to be at least better. Means ML shows nearly the right numbers like Canon info says 80" - ML shows a higher 81" or  the other way round ... canon 100" / ML 96" or canon 135" / ML 125"
If you try to change shutter speed in both modes ... very often the display jumpes for not even 1/2 a second to the org. canon info view and back to ML view.

Oh, just this moment the camera didn´t start again and showed the orange light - had to take out the batterie. But this was the first time after starting around 10 - 15 times.

That´s my experience so far.

.
#17
I just saw that EOS M is back on the nightly bulids  :)
Does any body know what did change? On the first go I didn´t find out any difference - just realized that shutter speed is still not working.
#18
Quote from: jordancolburn on January 13, 2014, 03:02:35 AM
After porting, it's been working well enough for me to use for small family photos and videos, but haven't used it on a real project yet.  I've been pretty busy this past week, but my short list of bugs to look at next:
-shutter speed display in menu
-canon menus overlaying ML menu bugs
-bug I'm experiencing with it hanging every few startups

Are there any news ... and if - where could I get a newer version?
#19
Tragic Lantern / Re: Tragic Lantern for EOS M
December 20, 2013, 09:26:26 AM
Quote from: jordancolburn on December 19, 2013, 09:51:08 PM
The EOSM seems perfect for grabbing quick interviews for Docs, a simple clip on lav with 1/8" connector can fit in a jacket pocket with the EOSM, 22mm lens and a backup battery and card, and you are always ready to grab a quick interview or story (on some recent trips, we always find that when people are most at ease and willing to share their stories, is when we're least prepared shoot and out to eat or something).

That´s exactly how it is! As less official as possible gives the best results - that´s why we don´t use big cams very often for theses cases.
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
December 15, 2013, 10:43:06 AM
Quote from: jordancolburn on December 14, 2013, 08:59:49 PM
Thanks, I got the basics for 2.02 working based on looking through 1%'s code.  He documented everything pretty well with his commit messages, so it wasn't too bad.  Once EOSM gets back into the nightlies, we should start a new thread since it will be missing any bug fixes 1% did and any features specific to TL.  I'd appreciate anyone's help who might want to point out missing features or bugs, so I can try to pull the most necessary stuff over first.

Sounds good to me. I think for video it´s most importend to have first the normal daily used stuff like zebra, focus peaking, 3x zoom, record restart, ... and to get rid of this f... shutter bug. With other words a basic version which could be more or less called stable before working on raw a.s.o. ...
#21
Tragic Lantern / Re: Tragic Lantern for EOS M
December 14, 2013, 11:31:30 AM
Quote from: a1ex on December 14, 2013, 05:24:58 AM
The word was chosen by 1% more than one year ago.

The good news is that @jordancolburn already updated ML to 2.0.2 ( https://bitbucket.org/hudson/magic-lantern/pull-request/303/updated-eosm-to-run-on-firmware-v-202/diff ), and if all goes well, we may have official nightly builds for the EOS M soon.

Yeah ... a1ex - thanks for giving us users a hopeful sign after this long time of suffering. And another thanks goes to @jordancolburn - really hope all goes well!
#22
Tragic Lantern / Re: Tragic Lantern for EOS M
December 04, 2013, 04:06:28 PM
Quote from: maxotics on December 04, 2013, 02:56:36 PM
I wouldn't call them a team.  Little fault of theirs.  Everyone wants different features, so each dev works on whichever feature they're also interested in.  There are two forks of ML, as far as I can see.  Until users take some responsibility for helping the devs work through what are, in the end, political issues, the EOS-M will remain an Alpha fork. 

One dev wants the other dev to put his work into the main fork.  Everyone agrees it's a good idea, but no one really takes a stand. That would create a lot of dull work for the second dev and would take away from new/fun feature dev.  It's his time.  In order for that to happen, if that should happen, users need to make sure it's somehow worth it for the devs to put time into drudgery work, or, as they say, fire up your compiler and do it yourself.

Mhh, maybe, but still they do a great job!
It´s not an organized commercial company and there may be too less devs around which could solve every problem for every cam every day, week or month. I do understand that every dev likes to work on what he is interested in - they work on ML just because they like to do it.
OK, sure - I would love to have a more stable ML-EOS M version too as fast as possible but remember - its for free and so I/we can´t blame anybody.
But I still wonder that the EOS M doesn´t catch more interest. From my point of few it´s the second best and interesting Canon cam behind the 5d product line. Especialy if you already own different Canon lenses.
I´m looking forward for a real EOS-M2+ next year (not just this so called "new" M2 with just wifi and a little bit better AF - nice but that´s nearly nothing)
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
November 20, 2013, 05:39:27 PM
Quote from: maxotics on November 20, 2013, 06:23:25 AM
Hi Gary.  I bit the bullet and a BMPCC should come tomorrow.  I don't see any leadership emerging here and no one wants to follow me ;)  If I were Alex I wouldn't come back. At some point 1% will want a vacation too.  Then we'll have two forks to nowhere.  g3gg0 is happy to build a viewer for 3 people.  I think there are only a few of us doing anything meaningful on the EOS-M.  I'll try to continue with it, and can see getting more interested if the 11-22mm lens goes on sale here under $300.  How about you?

These are the things I think need to happen for the camera to gain any traction.

1. Audio is turned back on if you go back to H.264
2. FPS is turned off if you go into photo mode
3. The 11-22mm lens is cheap OR
4. Someone figures out how to reduce the horrible moire in normal shooting mode.
5. The shutter bug is fixed.

Actually it would help if the ML work on the EOS M does go on - I guess and also know that many canon user professionals already do use the M as the small camera choice beside the 5d Mark x. The M is always with us if we do a job or also for every day private use - my company does use it some times but never with raw till now.
Mainly by always using focus peak, zebra, video restart and some other features which are needed in different situations. So there is almost anything already existing we need for our daily work accept audio - but using ML here is dangerous for professional work because it´s an alpha version with existing bugs. At least I feel so even we never faced a real problem with the M + ML during work.
#24
Tragic Lantern / Re: Tragic Lantern for EOS M
November 20, 2013, 05:03:07 PM
Quote from: maxotics on November 19, 2013, 09:00:28 PM
I updated my starter set with a build from 11/09.  You can find a link to it on this page.  Jerykil warned the server might be down for a few weeks.  Hopefully it'll come back.

http://www.magiclantern.fm/forum/index.php?topic=8825.msg82945#msg82945

Or

http://maxotics.com/software/downloading.aspx?file=EOSM_MLStarterSet.zip

I had this build already but anyway - thanx maxotics
#25
Tragic Lantern / Re: Tragic Lantern for EOS M
November 19, 2013, 04:00:21 PM
Were could I get the new alpha versions for the EOS M now? I can´t reach the old sever any more.