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 - Licaon_Kter

#52
General Development / Re: Touch-friendly ML menu
January 07, 2017, 05:33:46 PM
Drag the finger... hmmm
#53
Camera-specific Development / Re: Canon EOS M
January 07, 2017, 10:13:15 AM
Put new version on card, use!
#54
Quote from: a1ex on January 06, 2017, 02:05:28 AM
Bonus points for x86 and ARM support in the same binary.
So you can run raw2dng on your Android phone?
#55
Quote from: a1ex on January 06, 2017, 01:05:29 AM
@Licaon_Kter: do Linux binaries make any sense? (I mean, compiling host binaries on this system usually just works)
Like on any other platform, don't just go the "if you run Linux you already compile stuff" way :) (if your response was like that)
Else, that page kinda says "You'll need Windows to use Magic Lantern" otherwise ;)
#56
The build server is on Linux? Any chance the Utilities page could also host Linux/Mac apps besides those Windows ones since you can just build them anyway?
#57
Posting just to get subscribed ;)
#58
Scripting Corner / Re: Simulated Q Button for EOSM
January 05, 2017, 11:04:29 PM
I find Q ok, but nice LUA script reference. Thanks
#59
General Help Q&A / Re: Magic Lantern For Android
January 05, 2017, 04:18:56 AM
Quote from: arrinkiiii on January 05, 2017, 03:32:08 AM
@Licaon_Kter   existe this open source for iphone? Or something similar?


Thanks
Did not search.
#60
Feature Requests / Re: mv1080 on EOSM
January 04, 2017, 10:54:04 PM
Nice findings.  :o
#61
General Help Q&A / Re: Magic Lantern For Android
January 04, 2017, 10:19:16 PM
Umm what? You mean like OpenCamera ( http://opencamera.sourceforge.net/ ) or what?

Also do note, you can't get RAW if the device does not support it anyway.
#62
Scripting Corner / Re: NEW: Toggler for the EOSM
January 04, 2017, 10:16:46 PM
Interesting, thanks.

#63
Quote from: g3gg0 on January 04, 2017, 03:05:12 PM
so maybe some other module starts threads when not invoked - which ones do you have active?
so: dual_iso, ettr, fileman, mlv_play, mlv_rec, mlv_snd, pic_view and silent

/LE: Ok got it, tracked it down to mlv_snd, and it happens only if sound is actually recorded, yep this makes sense.
#64
Quote from: g3gg0 on January 04, 2017, 12:20:48 PM
its due to the EOS M having not enough free thread ids available.
would need some serious rework of code to save threads.
NO idea what you are talking about.
That being said, those need to be hooked (reserved, whatever) all the time even if not mlv_playing anything? (don't mind me, this is way over my head)
#65
On EOS M the mlv_play speed up looks like it's working.

Too bad the camera will crash ( "Threads failed to start"; needs battery pull ) when having the module loaded and trying to record RAW (mlv_rec): https://bitbucket.org/snippets/Licaon_Kter/EqkKy
#66
Camera-specific Development / Re: Canon EOS M
January 04, 2017, 04:12:26 AM
Quote from: dfort on January 04, 2017, 01:25:29 AM
Of course @Licaon_Kter knows about charging batteries--he's gone through many charge cycles getting the EOSM to this stage in ML development.
Battery at 100% no matter what!!!
Test some things? Charge to 100%!
Come back after shooting outside? Charge to 100%!

The thing is, this camera has 3 stages: full-white (100% I hope?! when did I charge the battery exactly?), half-yellow (at 50%, right? 50% or 30%? please tell me!?!?) and empty-red (yeah, hey it turned on, let me try anot- oh fffs)
#67
Quote from: Walter Schulz on January 04, 2017, 12:12:03 AM
I haven't archived PetaPixel's post. There was some makeover, I think. Some corrections + introducing some weird concept (I take the liberty to say so).
And a lot of comments discuss that (quality change on conversion), not sure why would anyone would think that.
#68
Quote from: g3gg0 on January 03, 2017, 10:25:54 PM
noone realized that it is mainly a saving format meant for silent pictures
Details... details... that would need someone to actually read the thread, not only to grab the DNGs...  research in journalism, pffft
#69
Camera-specific Development / Re: Canon EOS M
January 03, 2017, 09:38:58 PM
Quote from: dfort on January 03, 2017, 08:14:16 PM
Pretty much. That firmware update was done for several cameras but it doesn't give most users a good reason to install it.
BTW--one of the first things I tested was the shutter-bug and it is still there. Rats!
I love updates don't get me wrong, but given the age of the camera (launched in 2012) and the poor support Canon gave it, I'm rather uneasy to flash away.
Too bad about the shutter-bug :(

That being said, is the downgrade procedure straight away (eg. I update to 2.0.3 and I don't like something, I just put 2.0.2 on the card and "update" ) ?
#70
Forum overload in 3...2...1... https://www.dpreview.com/news/2451079037/magic-lantern-proof-of-concept-shows-in-camera-dng-shooting

That being said, looks like I need to raise the issue or DNG lossless compression support in Darktable again :(
#71
Camera-specific Development / Re: Canon EOS M
January 03, 2017, 06:35:43 PM
Quote from: dfort on January 03, 2017, 06:30:29 PM
Just saying that doing the firmware update just because it is a challenge and sharing it with the community is in the spirit of a hobby project like this.
I agree, although you did not answer my question, or was the joke actually the answer, like nothing more? :)
#72
Camera-specific Development / Re: Canon EOS M
January 03, 2017, 12:42:13 PM
Quote from: dfort on January 03, 2017, 04:31:13 AM
Is there any reason to climb a mountain other that because it is there?
Oh, c'mon, really? :) :) :)  ::) :D
#73
Camera-specific Development / Re: Canon EOS M
January 02, 2017, 06:31:31 PM
Any reason to upgrade to 2.0.3? Saw that only 1 lens compatibility was added.
#74
Quote from: twentephotography on December 19, 2016, 04:52:21 PM
There is already ML for 1300d???
There is a 1200D in progress for some years,  but not for 1300D.
#75
I'm using Av and Tv, so ExpComp comes handy. Now, since I'm not earning my bread shooting, I might be odd. :)

Also, since (at least on my) EOS M the wheel is finicky (I blame myself too, I used it a lot for those FPS override tests :(), I can get it either too easy moved (to + or -) or find it too hard to reset it (to 0), hence this PR.