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

#2
Share Your Videos / Re: RAW video of TOKYO
September 10, 2014, 11:48:52 PM
one of my favorite tracks! awesome video, too. colors look great but i'm not an expert :)

is it all handheld?

ps the track is telefon tel aviv " the birds" not sure which mix
pss the typeface is great, too. reminds me of Akira
#3
Quote from: arcadio on August 20, 2014, 09:26:56 PM
ShutterBug
I foung solution for me (EOS-M with 18-55 IS STM). Pulling battery out!
Please read this thread about the shutter-bug: http://www.magiclantern.fm/forum/index.php?topic=8347.275
Quote from: Walter Schulz on August 19, 2014, 09:12:04 PM
If you don't want to wait use google. Just line up your search terms and restrict your search as in
anything you want to look for site:magiclantern.fm/forum
thanks 8)
#4
Quote from: a1ex on August 19, 2014, 08:56:21 AM
Greg did some research here: http://www.magiclantern.fm/forum/index.php?topic=8535.0
but I could only get it working on 500D. I should probably revisit it, since others also confirmed it on 550D and 600D.
Great thread. Apologize I couldn't find it on my own. I will play with this code and see if it works on EOSM.
Quote from: a1ex on August 19, 2014, 08:56:21 AM
Another way would be with the full-res silent pictures, once we figure out how to use the rolling shutter.
This is very interesting and exciting, also. Though, I'm not up to date on those new features...yet.

Quote from: Stedda on August 19, 2014, 03:28:26 PM
Wouldn't matter, more than half of all posts are people asking the same covered topics over and over again...
Personally, I would like to be able to make multiple searches without having to wait 15 seconds. For example, I was searching for prop_aeb and continuous hdr, but was unable to find the fast hdr that greg had posted on. after a few search queries, i grew tired of waiting 15 seconds between each dead end search...

As always, thanks for the hard work a1ex!!!
#5
another question for the developers.
I noticed PROP_AEB sets the range of EV's taken with built-in HDR. The max value was 10, has anyone tried to set PROP_AEB to get a greater EV spread (> +/- 2 EV)?
Thanks dudes

edit: tried to set PROP_AEB past 16 and it gave me an error sayin it wasnts 2 bytes, oh well...
#6
Quote from: a1ex on July 28, 2014, 08:56:10 AM
Find out Canon values for this custom function, as returned by cfn_get_af_button_assignment(), then I'll tell you which one to use.
thx for the reply a1ex. so cfn_get_af_button_assignment() is returning appropriate values from the C.Fn menu. Here is a screenie from the menu:

consts.h for af_disable is 2 right now, which does not disable it.
Is there any way to shoot in continuous mode to get handheld bracketing to be a possibility?
#7
Audionut,

So I have a small consts.h fix, how would I go about "back porting" that? (A link would suffice)
#8
Forum and Website / Re: ML-Bot is a pain in the IRC
August 08, 2014, 02:24:59 PM
Agreed
#9
Sometimes when enabling a module and restarting, I don't give the camera enough time to fully power off. The camera flashes orange a few seconds after hitting the power button, wait until then to start up again.
#10
good ideal, i'll work on that!
#11
General Development / Re: Config presets
July 28, 2014, 12:06:20 AM
It's built in and still works. however, the implementation is rather coarse. On my eosM, info button at bootup prevents ML from loading at all, and there are no mode dials. I set a preset for Menu.KEY and it worked great...
#12
#define AF_BTN_STAR 2
in consts.h doesn't work for advanced bracketing, setting it to 1 fixed some of the woes associated with focusing between shots w/ advanced bracketing on
it would be great if continuous shooting fps (like native bracketing) was possible with ML bracketing. It is much slower between captures through ML. any advice?
#13
I have a couple questions for you guys. What does someone starting out need to know about backporting changes to the main codebase?

Also, if a fork decides to start their own forum, are we allowed to inform others on these forums?

Thanks for all the hard work. I hope that I can or the TL user community can help 1% as well as the ML community by backporting bug fixes in a way that is acceptable to the ML codebase and developers.
#14
I'm a poor man w/o a 3D to play with :(
Maybe the frame rate is the difference? What kinda machine are you processing on?
#15
Tragic Lantern / Re: Tragic Lantern for EOS M
March 03, 2014, 04:09:02 PM
greetings!

I've been having some errors while playing with MLV which generated a handful of crashlogs. I'm just recording and trying to focus with the * key. It only focuses once until I stop and start a new clip. Error occurs when I stop recording. Error logs are here: http://tl.bot-fly.com/misc/crashes
THAAAANKS =D
#16
sry, my life is on hold till the end of march. wish me luck on my board exam!!!
#17
Tragic Lantern / Re: Tragic Lantern for EOS M
December 24, 2013, 07:21:08 PM
Hey gary & feureau,
I'll re-disable dot_tune. The site is sorta working, so let me know if there is any more downtime.

EOSM is not tune-able from what I understand.

1%, hope you're feeling better!

Happy holidays and happy new year from Chicago  8)
#18
Tragic Lantern / Re: Tragic Lantern for EOS M
December 12, 2013, 02:05:58 AM
gary, definitely will be. I'm hanging on to this host because they've been really good, but if it doesn't get fixed, i'll have to move to a new host. in the mean time i'll post my builds on google drive for you guys. there haven't been many commits lately because of holidays, so you're not missing any updates.
#20
Tragic Lantern / Re: Tragic Lantern for EOS M
December 11, 2013, 08:31:47 AM
Quote from: a1ex on December 11, 2013, 06:46:43 AM
Hm... uncomment CONFIG_HELLO_WORLD in config-defines.h and start tweaking from there.

I'm talking about *raw* overlays. Zebras are YUV by default, MZ is only YUV. Also, can you reproduce the same bug with raw_rec?
raw_rec.mo also crashes.
zebras don't like JPG-L mode (they require Raw shooting mode to be on), but when raw_rec is enabled in JPG-L mode they work fine on half-press so long as recording has not yet started. once recording starts, they work until half-press.

enabling config_hello_world and the gui.c & boot-hack.c modifications yielded a bin that never did greet the world :(

thx again!
#21
Tragic Lantern / Re: Tragic Lantern for EOS M
December 11, 2013, 01:25:29 AM
Quote from: a1ex on December 10, 2013, 10:49:30 PM
Back to our topic: if you enable some raw histograms in photo mode (say raw zebras), and autofocus, can you trigger the problem?


i'm back! so i tried some stuff u suggested. The zebras are on, and they work w/o a problem. could it be because zebras disappear on half-press? i'm not sure how that functionality is managed...
Histogram was already on and I also tried Magic Zoom and Focus Peaking. Everything seems to work fine on Half-press.

Quote from: a1ex on December 10, 2013, 10:49:30 PM
Another test: in boot-hack.c, my_big_init_task, do just this:

static void my_big_init_task()
{
    call("lv_save_raw", 1);
}


and in gui.c, comment out the TASK_OVERRIDE line (at the end).

With this change, you will have no user tasks running, just plain Canon firmware in RAW LV mode. If you are still getting the error, it's a Canon bug (but we still have to find some workaround).
everything compiles fine but ML doesnt seem to boot. I get a consistent orange light and no ML menu :(

thx for your time!
am i the only one experiencing this? i didn't test this before but this happens in video mode w/ crop mode off, also. same task crashed
EDIT: yeah raw looks best in crop but i can't get a decent frame most of the time
#22
Tragic Lantern / Re: Tragic Lantern for EOS M
December 10, 2013, 10:21:56 PM
cool trick! its still task 44 and that is TestGero (checked in the same boot cycle, even though it oesn't seem to change after reboot)
#23
Tragic Lantern / Re: Tragic Lantern for EOS M
December 10, 2013, 10:04:26 PM
Quote from: a1ex on December 10, 2013, 09:42:28 PM
When you get the stack overflow, ML should save a log file (no need to use other tools). If it doesn't, just print the complete message from the screen (including task name).

edit: took a closer look at the code and this part doesn't save a log file. Just get the task name from the error message:


            "[%d] %s: stack %s: free=%d used=%d ",
            id, task_name,


so the %s part is the one I'm looking for.
its actually blanked out. maybe its a LV drawing function covering it? i can't get DM to put anything out either (posted above)
#24
Tragic Lantern / Re: Tragic Lantern for EOS M
December 10, 2013, 09:41:03 PM
Unfortunately, DM Logging doesnt seem to be working for me when i do this. I'll try a couple more times

EDIT:
So here is what is causing my stack overflow in step by step


  • Clean install of the latest and greatest build ( 62cb47a )
    cleared all settings, ExpSim is on movie mode, camera is set to JPG-L, and continuous shooting in Photo mode and AF.
    I enable mlv_rec and nothing else
    i turn on dm log.
    i hit menu to start recording>"Continuous OK"
    i do a half-press to focus>BOOM it stops everything, clears the buffer indicators, and, sometimes, i get red letters saying "[44]: <<blank spaces>> stack overflow: free=0 used=544497930", unfortunately half of the error msg is hidden under some jank
    no DM log :(
    pull battery, restart, ML knows it made a no-no so it doesn't load modules
#25
Tragic Lantern / Re: Tragic Lantern for EOS M
December 10, 2013, 12:25:19 AM
i get a stack overflow free=0 used=1200 when i ttry to autofocus w/ halfpress while shooting raw in photomode. i'm guessing thats not nomal