Note: Any members who can compile, are more then welcome to fill requests in this thread. I would like to keep all posted builds to this thread, so that the forums do not get cluttered by numerous builds, resulting in lots of old builds being left scattered throughout the forums long after the original development, and confusing new members.
Within reason, members are free to do as they see fit, however, before fulfilling requests, please consider this message from a1ex, and the intent with which I created this thread.
My bolding for emphasis.
Quote from: a1ex on May 15, 2014, 09:44:11 PM
If you look at the number of ML downloads (it exceeded 1 million downloads, without counting the 5D3, 7D and most recent ports), you will realize right away that relaxing the license for my postprocessing code would be like saying "here you have the perfect recipe to make a small fortune from my work, just take it, it's all free".
Unfortunately for some of you, this is not exactly my intention, and GPL is just a tool to prevent such situations from happening. I could have given this code away as public domain, but I chose to protect my work from being used without giving back.
Instead, I'm trying to build a community that does not just consume whatever we give to them, but I want this community to actually participate in the development process, help each other, and share the knowledge. We gave you some free software, we gave you a proof of concept that you found useful, and now we expect you all to take this software at the next level, and let us build upon your work, in the same way as you have built upon ours. I'm quite far from this utopian goal though, but this is the direction I want ML to go.
Thanks for taking your time to provide builds for the community.
A large amount of the recent development work has moved to the branch system. This is excellent, as it allows "power users" to help with that development, while keeping that development outside of the regular nightly builds, and reducing the chances for a large number of "bricks".
As an attempt to reduce the divide between knowledgeable developers, and useful contributors, I will provide a compile service.
The process will work like so. You state the camera you are using, and the features you would like to test. I will compile the build, and you will provide feedback (http://www.magiclantern.fm/forum/index.php?topic=9516.0).
I only have a 5D3, and don't have time to test the builds I create for this camera (unless you specifically test the branches I also test), so naturally, these builds will be provided "as is", without any warranty, and if your camera melts when using these builds, you get to keep all of the melted bits. If you would like to help with this feedback, but are not comfortable with the risks involved, I would suggest waiting until feedback is received for a build you would like to test. At least then the build has been confirmed as working or not.
Please do not request builds if you are not comfortable with the risks involved, or if you are not sure you will have the time to provide feedback (http://www.magiclantern.fm/forum/index.php?topic=9516.0). This is not a service for you to simply use these latest developments, for that you have to compile yourself. If I find that this service is being abused, or the feedback from users is lacking, I will naturally stop providing it.
Please do not share these builds. There are reasons why this development work is not readily available, and defeating this by sharing these builds will be considered abuse.
Also please do not request builds if you have a low post count, call me cynical, but a low post count is not an exemplary example of feedback. Of course, you can download an already requested build and provide feedback on that. I have an idea on who useful feedback users are, and post counts will not apply to them.
I've linked this a couple of times, but let me provide specific mention of it. This thread contains some excellent advice (thanks dmilligan) on how to provide feedback: http://www.magiclantern.fm/forum/index.php?topic=9516.0
Well, that was a long disclaimer, lets move onto the fun stuff.
To see what branches are available, check here: https://bitbucket.org/hudson/magic-lantern/branches
Most of the branches also have a pull request: https://bitbucket.org/hudson/magic-lantern/pull-requests
These pull requests will have links to the relevant forum threads. Please read these specific threads first. They contain relevant information about the development work. Feel free to leave general feedback here, but please leave specific feedback regarding the development work in their specific threads.
As a last note, I haven't tested all branches personally yet, so there may be times where I cannot provide a requested build within a reasonable time frame.
The builds:
Love it
That's a very good idea !
Awesome!
Is there something that needs testing or can be done with a 5D2? I've been following the iso-research and srm memory threads, but would be happy to help with anything that needs some love. Read the "how to report bugs" thread and "tips for helping dev's", so I'm good to go.
Looks like the stubs (http://www.magiclantern.fm/forum/index.php?topic=12177.0) need to be found on the 5D2 for SRM related stuff.
I haven't been following the cropmark related stuff, might want to ask the guys over here (http://www.magiclantern.fm/forum/index.php?topic=12375.0) if 5D2 related dumps are needed. This requires no dev/hacking knowledge, just time.
a1ex needs 5D2 stuff here (http://www.magiclantern.fm/forum/index.php?topic=10111.msg117955#msg117955) and here (http://www.magiclantern.fm/forum/index.php?topic=10111.msg118232#msg118232). Both requests do not need dev/hacker knowledge, only time. Second request need a suitable target for imaging.
That's three things off the top of my head. :)
//todo. Make another post with info like this for all cameras.
@audionut
Hello, I would like to test on the Canon 6d if the SRM code can be used in combination with the extra memory hack already available in the older builds.
According to Alex:
"Try compiling 3d6a945, or ask Audionut here to do it for you."
This quote from Alex comes from the following topic:
http://www.magiclantern.fm/forum/index.php?topic=12528.new#new
Don't know if this is enough information, do you know what I would like to test or do you need additional information ?
Thanks for the hard work 8)
I can compile 3d6a945 in about 12 hours for you as I have no access to my build environment atm. Ofc if no one else agrees to do so in the meantime. It's just some minutes to do and upload it. I also am interested in the results
@nikfreak
In about 12 hours from now is quick enough, no need to rush.
Can't test it anyway within 24 hours from now.
Have to go to work over 1,5 hour, it's a nightshift, so afterwards I'll be sleeping.
Thanks for helping with the compiling part :)
Updated OP.
Here is mine as promised to test @Levas. See also first post as Audionut already compiled it for you. Use his build first
Build removed //Audionut.
@Audionut
The build "6D with SRM-memory." works.
The option "use SRM job memory" in the raw video menu works.
The option "memory hack" in the raw video menu works.
But both options together didn't result in any more memory... ::) or actually I mean :'(
Did some testing and looked at the MLV file size
Both options = the same file size as Memory hack only
SRM option only = slightly higher file size vs memory hack option and both options.
So it looks like both options results in gaining the memory from the memory hack, but doesn't give us any SRM memory. ???
@Nikfreak
Downloaded your build, does work, but doesn't have any modules in it.
The MLV recording module isn't in your build.
So,
Quote from: a1ex on July 15, 2014, 04:42:19 PM
This means, the benefit for 6D is just cleaner code and a smaller delay before starting to record.
;) :P
@nitfreak, for future reference, run make in the source directory, then browse to the required platform directory (6D.113 in this case), and run make zip.
This will compile the modules and produce a nightly type zip in the platform directory.
Builds cleaned from the thread. Required feedback has been given.
:'( :'( :'( :'( :'(
The cleaner code part... ::), doesn't excite me :P
But, I'm happy with the smaller delay 8)
Thanx for feedback @Levas and also thank you Audionut for the feedback regarding compilation. 8)
Whatever needs to be tested for 7d, I'll be happy to do. Right now I'm most interested in SRM memory and full res silent pics. If you could compile these, I'll be your best friend :D
:edit: a1ex just posted that SRM is now included in the nightlies, but whatever else needs testing on 7d I'd be happy to work with.
Audionut,
I read this post in the full res picture topic:
Quote from: c2s07 on July 17, 2014, 06:53:10 PM
The intervalometer is already able to capture silent pictures, just enable both and it works. :-)
It seems that full res silent pictures is already usable for time-lapses with the intervalometer :o
Would like to test it for some night-time time-lapse of the sky full of stars.
Don't know if it takes much of your time , but if you have the time to compile a build for the 6d which contains the full res silent picture option, I would really appreciate it :)
I did read that it takes quite a lot of time to process the DNG, so I probably test it first so I set the interval large enough between shots.
I want to test full-res silent pic on my 5d mark III 1.2.3 but don't know how to compile ..
@ Levas.
That one needs RAW_PHOTO_EDMAC (https://bitbucket.org/hudson/magic-lantern/commits/a0a2afea2d57) found for the 6D. And probably the skip offsets re-calibrated, details in the full-res OP.
Also, this one needs more then just usage testing.
Quote from: a1ex on July 01, 2014, 05:11:15 PM
- figure out how to speed up the capture process (maybe without the dummy capture step, or find out how to trigger the continuous readout mode)
- figure out how to get fast shutter speeds, as in LiveView (electronic shutter)
- implement a fast bracketing, exposure stacking or other funky capture modes
@ N/A
In terms of build testing, I think the only thing is Black Level Fix (https://bitbucket.org/hudson/magic-lantern/pull-request/484/black-level-fix/diff).
Also this,
../../src/raw.c: In function 'raw_update_params_work':
../../src/raw.c:596:10: warning: #warning FIXME: are these values correct for 720p and crop modes? [-Wcpp]I had a quick look at the code, but I'm not entirely sure what's needed here.
There is some other stuff that doesn't need specific builds or knowledge, only time: http://www.magiclantern.fm/forum/index.php?topic=12657.0
Quote from: Audionut on July 18, 2014, 03:31:17 AM
That one needs RAW_PHOTO_EDMAC (https://bitbucket.org/hudson/magic-lantern/commits/a0a2afea2d57) found for the 6D. And probably the skip offsets re-calibrated, details in the full-res OP.
Audionut, I saw some comments in the spreadsheet Nikfreak started for the 6d, it seems that Alex and 1% have the data you mention above.
Don't know if this data is available for compiling :-\
https://bitbucket.org/hudson/magic-lantern/commits/e261cbbbdf25a380f74c15ddb671952518693b26#comment-1104034
I can't do the second part either (yet).
Unable to compile myself unfortunately (hmmm ...that sounds all wrong but anyway), ...is anyone able to build a "full res silent pictures" version for the 650D? Cheers.
Quote from: Rythmtech on July 24, 2014, 06:41:15 AM
Unable to compile myself unfortunately (hmmm ...that sounds all wrong but anyway), ...is anyone able to build a "full res silent pictures" version for the 650D? Cheers.
me too!
May I have a nightly build for 550D with the latest full-res silent pic module to save the frames to MLV? I would like to test it.
Audionut and/or NikFreak
See the full-res-silent pic topic
http://www.magiclantern.fm/forum/index.php?topic=12523.new#new
See the posts from me and A1ex.
I did the raw_diag OB-zone test, but it needs to be done with the fullres-silent-pics branch (the offsets changed).
Can you guys help and compile a full-res-silent pics build for the 6d ?
Same here for 7D.
Well, I have a 650D as well but ...
I'm likely to be away from my computer for the next month. I'll do my best to compile some builds when possible.
Those members who can compile are welcomed to keep this thread going.
Thanks.
Fullres-silent-pic branch is almost ready for you @Levas. I will PM you the download link soon
Walter Schulz: I would like to help you but can you lead me to which edmac I shall use when compiling branch "fullres-silent-pic" for 7D? Old value which got thrown out (was 0xc0f04A08)? it needs to be put here before I can compile for 7D. Can you find correct value of 7D? I assume it can be 0xc0f04208 but I am unsure about that. Older cameras seem to use that. Newer cameras seem to use 0xc0f04008:
#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_60D) || defined(CONFIG_550D) || defined(CONFIG_500D) || defined(CONFIG_600D)
#define RAW_PHOTO_EDMAC 0xc0f04208
#endif
#if defined(CONFIG_5D3) || defined(CONFIG_700D)
#define RAW_PHOTO_EDMAC 0xc0f04008
#endif
@nikfreak.
Can you please compile me a 6D build with CONFIG_GDB=y in the makefile for iso_research testing? I'll likely not have access to my compiling machine for another few weeks.
This is freshly compiled "iso-research" branch for 6D with only "CONFIG_GDB = y" as requested:
Thankyou sir. Now to find some useful registers.
Audionut, does this mean you got a 6d now ?
Yeah arrived earlier in the week. Life a little busy atm, but should find some time to poke some registers.
If you find something usefull with iso research, can you share ?
I'm curious how low iso's can go, especially now we have the new full-res-silent-pic option (with fastest shutter time around 300ms...)
By the way, is this iso research and poking registers something that I can help with ?
Or is it very risky, bricking wise ?
And what do I need, is the build Nikfreak posted here complete or do I need some extra module form a1ex ?
I am sure he will share once getting some useful results. He did for 5D3, too. :P
He's probably playing a lot with his new shiny camera, so he could forget time while playing ;D
Quote from: Levas on August 07, 2014, 07:40:10 PM
If you find something usefull with iso research, can you share ?
Um, that's the whole point :P
Quote from: Levas on August 07, 2014, 07:40:10 PM
By the way, is this iso research and poking registers something that I can help with ?
Or is it very risky, bricking wise ?
If you have good observational skills. It is somewhat risky, since we don't know what all of the registers do, and you may trigger a register that does something funky. See this link (http://www.magiclantern.fm/forum/index.php?topic=6751.msg71720;topicseen#msg71720) about the tool used to test these registers.
Quote from: Levas on August 07, 2014, 07:40:10 PM
And what do I need, is the build Nikfreak posted here complete or do I need some extra module form a1ex ?
The build from Nikfreak, and the tools from the CMOS/ADTG (http://www.magiclantern.fm/forum/index.php?topic=10111.0) thread.
Hi guys, can anyone please make a build for 650D (T4i). I can't compile it by myself :-/ Thank you
Is this a general question? You can download nightlies at http://builds.magiclantern.fm/#/ (//http://).
If you need a specific build please define branch or we won't be able to help you.
Quote from: nikfreak on August 07, 2014, 07:51:39 AM
This is freshly compiled "iso-research" branch for 6D with only "CONFIG_GDB = y" as requested:
NikFreak, do you have time to compile the above build,
including the new Full-res-silent picture module ?
This would save a lot of shutter actuations while investigating the iso registers on 6d and using raw_diag.mo for DR measuring etc.
Quote from: nikfreak on August 08, 2014, 05:16:35 PM
Is this a general question? You can download nightlies at http://builds.magiclantern.fm/#/ (//http://).
If you need a specific build please define branch or we won't be able to help you.
Sorry, I didn't realize this Topic is general. My request was meant to FullRes Silent Pictures module. Thanks
Quote from: Levas on August 08, 2014, 05:43:50 PM
NikFreak, do you have time to compile the above build, including the new Full-res-silent picture module ?
This would save a lot of shutter actuations while investigating the iso registers on 6d and using raw_diag.mo for DR measuring etc.
use above build and also @skid latest silent.mo is in here:
Grab raw_diag.mo from http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo (http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo) (save as...)
lemme know if it wrked for you...
Works perfect!
Full-res-silent and adtg_gui.mo
:D
Quote from: nikfreak on August 08, 2014, 09:38:06 PM
use above build and also @skid latest silent.mo is in here:
Grab raw_diag.mo from http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo (http://a1ex.magiclantern.fm/bleeding-edge/raw_diag.mo) (save as...)
lemme know if it wrked for you...
Will it work also on 650D? Autoexec is totally different than native one. Or should I use just silent.mo? Thanks :)
@skid just silent.mo
Quote from: nikfreak on August 09, 2014, 08:01:54 AM
@skid just silent.mo
@nikfreak thanks, but unfortunately it doesn't work. I am getting RAW ERROR (both in DNG and RAW) and no file is saved
Nvmnd I just assume that 650D users have not reported correct values for RAW PHOTO EDMAC in time. Cause the adress misses in raw.c and I had to simply assume and add defined(CONFIG_650D). Otherwise the latest fullres-silent-pics wouldn't compile for 650D. So be warned. I have no 650D nor won't I hold be responsible if anything breaks due to my additions. The 650D might have another EDMAC adress but that's up to you to find out: (everything OK..see a1ex's comment below)
#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_60D) || defined(CONFIG_550D) || defined(CONFIG_500D) || defined(CONFIG_600D) || defined(CONFIG_1100D) || defined(CONFIG_650D)
#define RAW_PHOTO_EDMAC 0xc0f04208
#endif
#if defined(CONFIG_5D3) || defined(CONFIG_700D) || defined(CONFIG_6D) || defined(CONFIG_EOSM)
#define RAW_PHOTO_EDMAC 0xc0f04008
#endif
The offsets for 650D are OK, confirmed by @Rythmtech.
I tried Aug21 version (previously had Aug20) but I am still getting black screen with RAW error in left corner. When I press Play, camera freezes with black screen adn is unresponsive, I must turn it off and on to get rid of it.
I made a clean installation on SD card
Did you try my posted file from above now or which 20/21th August builds you talking about? The file posted by me is an actual build of "fullres-silent-pics" branch. So no official nightly...
Yes, I used your build
Ok then I can't help you atm. I can suggest you to retry by starting from scratch and deleting configs. If still no luck than report the bug on bitbucket to fullres-silent-pics branch
650D is from the same generation as 700D, not as 500D ;)
Ahh ok, that explains it!
@SKID: This one should work
Thanks @nikfreak, it works :)
OK, it works, but when I shoot outside, images are overexposed. Even with maximum aperture and minimal time 1/4000s it is overexposed. I tried all modes (M/Av/Tv/P), turned on/off almost every related feature (Exposure Simulation, FPS overdrive etc.) but nothing helps. Any ideas?
Are you sure your diafragma/iris of your lens closes during the picture taking ? (Lock exposure simulation in ML menu, otherwise it shoots wide open)
Most camera have 1/3 second shutter time with full res silent pic.
ISO 100 and diafragma of 11 and a fast shutter time should do it.
If you're in doubt, use full res silent picture in video mode, video mode closes diafragma for sure.
You are right, iris in photo mode doesn't do enything when taking picture. But even in movie mode pictures are overexposed - not so much, but they are. Even when iris is closed.
You need to put on the option "expo.override" in ML menu, this way the iris should close in photo mode.
And yes, fastest shutter time of about 300 milliseconds is long, so you may need a diafragma of 22 or use filters on your lens(neutral density or polarizer)
Or wait till it gets dark outside ;)
@SKiD,
Read the full res silent pics discussion (carefully!), there are many limitations you need to be aware of, what you are experiencing is expected behavior. You'll need to use an ND filter or go somewhere dark like Levas says.
http://www.magiclantern.fm/forum/index.php?topic=12523.0
Thank you guys,
I misunderstood the information about capture speed (I thought it is saving time, not "shutter" speed). I noticed it isn't always the same or similar (usually from 230 to 260ms), once I even got to 530ms.
The printed time *is* the saving time, not the capture time, which is why there is variation. I don't offhand know whether anyone has measured the rolling shutter time for the 650D (such as 5D2/5D3/6D/500D (http://www.magiclantern.fm/forum/index.php?topic=12523.msg121962#msg121962), 60D (http://www.magiclantern.fm/forum/index.php?topic=12523.msg123546#msg123546), and 50D (http://www.magiclantern.fm/forum/index.php?topic=12523.msg123594#msg123594)), but it's probably ~0.3 ms. The rolling shutter means that, not matter how fast a shutter speed you select, there will be a gradient of exposure from top to bottom, and the bottom of your frame will always be exposed at least ~0.3 ms.
I've been getting a lot of errors when I try to compile with the changes from pull request # 578
https://bitbucket.org/hudson/magic-lantern/pull-request/578/mlv_snd-merged-into-mlv_rec-and-enabled-by
I'd like to test this to provide feedback, if anyone is up to it, can you make zip with the changes for 7D, or 5D2?
Thanks!
What errors? I've compiled the branch both as standalone and merged into unified, no errors.
numerous errors that are probably due to me trying to manually copy/paste your changes into the files on my local copies of the affected files. Is there an easy way to just download the files that were changed so I can replace the files on my computer rather than doing it the hard way? (which I did wrong anyways) preferably through bitbucket online (not atlassian)
I know I should just bite the bullet and learn how to work with mercurial... I guess I'm being lazy. I'll just figure out how to do it the right way, because that will require less effort than convincing you to build a zip for me to test. Thanks for forcing me to become a more useful member of the community...
Quote from: dpjpandone on September 06, 2014, 09:26:07 PM
Is there an easy way to just download the files that were changed so I can replace the files on my computer rather than doing it the hard way?
This is the whole point of using version control (mercurial) and it's main purpose.
Start here: http://hginit.com
There's also a nice tutorial for TortoiseHG (a good GUI for mercurial) on this forum: http://www.magiclantern.fm/forum/index.php?topic=10774.0
Thanks DMilligan. I am doing my homework now. I am developing under windows, so I guess I must use atlassian source tree. It's fine. thanks for the links.
No, there is TortoiseHG for Windows.
Can anyone make a build with Pull Request #589 for the 5D Mark II, so we can test if it is faster on DIGIC4?
Yes, here:
please let me know your results in the pull request.
Could anyone be so kind and please make a full res silent picture with ability to save into mlv for 600D? Don't want to sound noob, but the 600D 19July Nightly, which I found from "Full-resolution silent pictures" main topic page 5, before it was deleted, doesn't include mlv saving. Only DNG mode. I believe other 600D owners would also like to test out this nice feature :)
Hi!
I'm also looking to have fullres silent pics test for 600D primarily for astrophotography. I'm not dev thus looking for files that can be directly put on sd card.
Already using many features like intervalometer, bulb timer and 3x bitrate in video for planets with success. Can't imagin going for AP session without ML. Until now, slow shutter speed in video proved good for hi resolution deep sky objects like trapezium stars+core of orion nebula. This is the kind of target which requires combination of slow shutter and many subframes in quick succession without shake of mechanical shutter[See attached image of 3sec video exposure x 30 frames] Now with this fullres silent pics, large number of 1-10sec exposures will be possible.
Can benifit in fullres moon shots too. Video with small FOV and mosaicing small stacks can be superseded by this whole sensor multi pics approach to certain extent.
Also is it possible to have dark current enable like https://nikonhacker.com/viewtopic.php?f=2&t=2195&sid=a70021fabc58894a9d3ee19517cd3dc2 (https://nikonhacker.com/viewtopic.php?f=2&t=2195&sid=a70021fabc58894a9d3ee19517cd3dc2) hack published for nikon cams recently. From reading tens of forum pages, ADTG value changing is closest i can understand being similar. So can both silent pics and adtg be enabled in single bin file? W'd love to have it if u experts know that canon too cooks raw files. The cam will virtually become as powerful as uncoled but large astro ccds.
-Anu
(http://s28.postimg.org/byoghlg3t/M42.jpg) (http://postimg.org/image/byoghlg3t/)
(http://s30.postimg.org/68qt4kvx9/Mars.jpg) (http://postimg.org/image/68qt4kvx9/)
Can any one build the new pull for the 60D my development environment is broke and Alex wants new tests done.. I am going to the mountains tomorrow night for time lapse.
I hope to be back in full swing in about 2-3 weeks, with my compiling machine up and running, and more importantly, some spare time.
hmm. perhaps you can explain that a bit more, cause i thought that the builds are compiled automatically here: https://builds.magiclantern.fm/#/
but as for the canon 5d mk3 1.2.3 the latest build there is august 07?
so are they compiled by you?
sorry but i ask because from jun 2013 til august 2014 the builds were always actual, and now we have not seen any new builds for nearly 2 month..
thank you for all your time, and i hope to get the possibility for testing the new improvements soon. thank you.
sw
nightly builds are created from unified branch as long as devs don't decide to break the builds due to some reasons 8) 8) 8) ;D ;D ;D.
You may head over to bitbucket at any time to see if any stuff is added/updated/deleted:
https://bitbucket.org/hudson/magic-lantern/commits/branch/unified
Once there's new stuff committed it should become abvailable in the next nightly -> a new nightly zip will be created. If there's no new commits then there's nothing to build for the system. All other branches here (https://bitbucket.org/hudson/magic-lantern) can contain more experimental stuff. To get this you can try to follow the tutorials for compiling or request a build of a specific branch within this thread.
Quote from: bhursey on September 26, 2014, 04:56:06 PM
Can any one build the new pull for the 60D my development environment is broke and Alex wants new tests done.. I am going to the mountains tomorrow night for time lapse.
For Fullres-silent-pic Branch testing.
// Builds removed. These builds should have been used for development related feedback, not just being able to try new (experimental/dangerous) features. Audionut.
Would be very happy if anyone could compile a fullres silent build for my 7d. Will test if especially for timelapse with external trigger (dp slider).
Quote from: breaker on September 26, 2014, 10:26:37 PM
Would be very happy if anyone could compile a fullres silent build for my 7d. Will test if especially for timelapse with external trigger (dp slider).
I don't have the 7D changes for FullRes-Silent-Pic yet, if 1% has them and shares them with me I will add it and compile it for you.
UPDATE! look above for link, I believe I have the correct values I found from an old PM from 1% awhile back, please test.
@mk11174
full res silent picture for 550D please :)
Quote from: ecek2 on September 27, 2014, 03:34:03 AM
@mk11174
full res silent picture for 550D please :)
Added!
Quote from: mk11174 on September 26, 2014, 09:26:02 PM
For 7D User, Can't test either, so please let me know if it works or not.
Thanks - FullRes is working! But i don't have time to play with it untill later today.
Thanks mk11174! :)
Thanks! Working on 5d mark 3 frimware 1.1.3
Any chance of getting the latest Silent Full-Res version built for 650D?
The shutter of my 50D over 200,000 shots. It is almost dead. Please fullres silent build for 50D. Sorry for my english, it's Google translator
Quote from: nouskrabs on September 28, 2014, 01:01:21 AM
Please fullres silent build for 50D. Sorry for my english, it's Google translator
Added to the list.
Quote from: Rythmtech on September 28, 2014, 12:11:26 AM
Any chance of getting the latest Silent Full-Res version built for 650D?
Added also.
Hello mk11174
I see you know your way in building full res silent picture magic lantern files for testing.
Do you have time to put a 6d build in your ever expanding list ?
Thanks (in advance) for your time and help :D
Quote from: Levas on September 28, 2014, 02:19:43 PM
Do you have time to put a 6d build in your ever expanding list ?
6D Added, but of course can't test so please let me know if it even works so I can remove it from the list if it don't at all, if it has bugs, than it will be ok since the Devs need to know what bugs it has exactly.
Thanks for the 6d build.
Did a quick test on full res silent pictures, got one crash in the first attempt.
After a camera restart I made 6 full-res silent DNG's without a problem, so seems to work at first sight 8)
Quote from: mk11174 on September 26, 2014, 09:26:02 PM
For Fullres-silent-pic Branch testing.
Installed the fixed version fullres-silent-pics for 5D3 1.2.3 and works well... Thanks!
Also bv any chance do you know if its worth or no necessary to add this particular feature for EOS-M? (due to its mirrorless it may be a noob question)
It's about shutter actuations, not mirror movement.
So it's even useful for eos-m.
any chance will any of us see a full-res silent pic for EOS-M sometime soon?
I've removed all builds from this thread.
The builds in this thread are for users to provide development related feedback. mk11174 provided a bunch of builds almost 2 months ago for various supported cameras, and virtually no feedback was given by the userbase.
The flip side of providing these builds for users to test, is that a bunch of users who don't know any better, break things, or otherwise clog the forums with duplicate questions, and since there has not been any useful feedback provided to offset the negative effects on the forum, I should probably just close this thread.
http://www.magiclantern.fm/forum/index.php?topic=8900.msg91362#msg91362
Hey
In the end of July i tested the new FRSP modul with my old 600D and i was very happy with it. I took various photos with it and i produced even a little promo vid for this modul.
https://www.youtube.com/watch?v=mLykDke0z7A
I tryed to find the borders of this modul and reported every bug i found. There were real not much ! ( :) )
Now, 5 months later, i sold my 600D and bought a 6D. Not hard to imagine that i want to try this new modul on the 6D too and help u guys with further developing. But.
I searchd now nearly 2 hours in the forum to find current silent.mo builds for the 6D but i found nothing useful. Now i read that people just asked for builds and didnt reported bugs :/ to sad.
So, the result from Audionut is totaly understandeble.
Now my question.
Is there any chance that a user, how is willing to "test" the FRSP modul, getting a working build for the 6D?
It would be realy awesome! This new feature would help me so much by taking timelapse's!
Quote from: Audionut on November 17, 2014, 05:51:02 AM
I've removed all builds from this thread.
The builds in this thread are for users to provide development related feedback. mk11174 provided a bunch of builds almost 2 months ago for various supported cameras, and virtually no feedback was given by the userbase.
The flip side of providing these builds for users to test, is that a bunch of users who don't know any better, break things, or otherwise clog the forums with duplicate questions, and since there has not been any useful feedback provided to offset the negative effects on the forum, I should probably just close this thread.
http://www.magiclantern.fm/forum/index.php?topic=8900.msg91362#msg91362
With the utmost respect to @Audionut -- NOT SURE why you would want to close this thread if there are actually few of us that use it for testing/feedback purposes if not for real work but what if the problems do NOT occur and all is well... however I think closing the thread is somewhat understandable.
Happy to HELP but how are we supposed to report bugs then if there aren't really any?
I'm still using it on 1.1.3 and what if I decided to go up to 1.2.3... how would I implement the full_res Module?
However, I may have saved the modules somewhere on my external drive but don't remember if it was for 1.1.3, 1.2.3 or both?
:o
There's nothing to test if there aren't any developers active...
Quote from: dmilligan on December 13, 2014, 11:06:37 PM
There's nothing to test if there aren't any developers active...
So basically you're saying it'll be a matter of time when someone decides to step up and take part of this development work?
Wish I could help but I'm usually working 6 days a week and hardly have time to be near a computer consistently to the least.
???
I have been using the 5D3 2014 Sep 26 FIX version. Granted I have not used it much but some tests of full res silent picture (with or without intervalometer) worked fine. So no errors to report.
I only wished i had access to speeds as low as 25 sec (instead of 15sec) for milkyway timelapses though.
But I owe a big thank you to all you ML developers anyway...
Quote from: tron on January 06, 2015, 11:56:04 PM
I only wished i had access to speeds as low as 25 sec (instead of 15sec) for milkyway timelapses though.
Try adjusting it on a 5D3.
https://bitbucket.org/hudson/magic-lantern/commits/a2ce0588032a0c684824f3bebb3cf2dce54cb6fb?at=unified
Quote from: tron on January 06, 2015, 11:56:04 PM
I only wished i had access to speeds as low as 25 sec (instead of 15sec) for milkyway timelapses though.
This code (Thanks Alex ;)) increase the limit to the 35 sec.
The maximum time is 30 seconds as silent full res pic does not work with the bulb.
if (cam_500d)
{
cache_lock();
cache_fake(0xff08afb8, 35000, TYPE_DCACHE);
}So if you need 30 seconds, you have to find a register and create your own compilation. If 5D3 is similarly...
Then an updated 5D3-123 build would be welcome :)
Right now I use 2014 Sep 26 (FIX) Mercurial changeset: bf22c22b62f6 (5D3-123)
The intervalometer tests were made using shoot like crazy
I have tried to time it. I have measured about 5 seconds delay between shots (Tv set to 15sec). I guess selecting 25 sec instead of 15 sec will make the 5 sec gap less important.
I got to the point where I couldn't stand the fact that I can't compile this code into the FRSP module (anxious to use the 25-30 sec shutter speed) that I decided to take a deep dive into ML wiki ( http://magiclantern.wikia.com/wiki/Magic_Lantern_Development_on_Mac) and followed the step by step to get myself ready to compile with the that code posted by @Greg whom he got it from @A1ex (Thanks for that) but since I'm not quite sure how to start on editing the Module within MacHGg application.
Can I just dive into that module and just copy the code and replace it?
Can't be easy as it sounds...
or am I wrong?
Thx.
I am interested in focus stacking and full resolution silent mode. I have been using both ML focus stacking for AF lenses and a homemade automated focusing rail with remote triggering of the camera. I would like to test the full res silent for this purpose with and without external flash. My camera is 6D. Can anyone help with a compilation of the latest FRSP module for this camera, please?
*** Testers needed ***
Help write test scripts for the new lua scripting engine: http://www.magiclantern.fm/forum/index.php?topic=14828.0
I will provide the lua.mo and keep it up to date with development, but a full build for the particular camera is needed for the module to load.
Custom test build from branch LUA scripting (ffcf212) for 550D:
Compiled with Codio (http://www.magiclantern.fm/forum/index.php?topic=14725.0):
1. hg clone -r ffcf212 https://bitbucket.org/hudson/magic-lantern
2. "Makefile.modules.default" changes in folder modules:
MODULE_CFLAGS += -I../../src/
ML_MODULES_STATIC ?=
ML_MODULES_DYNAMIC ?= file_man pic_view ettr silent deflick mlv_play mlv_rec mlv_snd lua
3. cd magic-lantern/platform/550D.109
4. make clean && make zip
Additional changes after compiling and downloading the zip:
- all files deleted in scripts folder
- added "forced_delay.lua" script file in the scripts folder (thanks dmilligan!):
menu =
{
parent = "Intervalometer",
name = "Force Delay",
help = "Add an extra delay to each interval",
min = 0,
max = 300,
unit = UNIT.TIME,
}
events =
{
intervalometer = function() msleep(menu.value * 1000) return true end
}
- custom cropmarks: hd.bmp + cinema.bmp
- copied "dual_iso.mo" from latest nightly build (because gcc 32bit isn't working on Codio cloud service and it couldn't be compiled, it's a 64bit system)
- so modules folder: adv_int.mo, deflick.mo, dual_iso.mo, ettr.mo, file_man.mo, lua.mo, mlv_play.mo, mlv_rec.mo, mlv_snd.mo, pic_view.mo, silent.mo
!!!Read the OP here!!! (http://www.magiclantern.fm/forum/index.php?topic=14828)
// Outdated build removed. Audionut.
Here is one for the 7D.
I used hg clone -b lua https://bitbucket.org/hudson/magic-lantern
instead of -r that surami used. Also added lua to ML_MODULES_DYNAMIC.
Added the dual_iso.mo from the latest nightly, the "forced_delay.lua" and "stop_thief.lua" from the original post.
Off to learn lua.
// Outdated build removed. Audionut.
Hi,
I would like to run some lua script on my camera.
Is it possible to have a build for the 600D and the corresponding lua.mo?
Thanks!
Lua branch build for 600D.
I had to disable the whole 'movie menu' featureset to shrink it down to <500k - might take a closer look at what to remove another time.
Also moved some of the sample scripts to a new folder called scripts-disabled because they were eating up all of the available memory on this model.
Enjoy! Thanks for your work @dmilligan
// Outdated build removed. Audionut.
Hi,
can someone compile for me the latest version of ML with Lua scripts feature?
My camera is the 700D.
Thanks a lot,
Regards
Here you go.
I don't have a 700D so there's no QC on this build. Please post when you downloaded it so I can delete it.
// Outdated build removed. Audionut.
thank you very much!
I downloaded it, you can delete the file.
If someone has the Canon 700D and wants ML with Lua:
Bye
// Outdated build removed. Audionut.
Here is a build for the 600D that includes the benchmarks and selftest as modules (https://bitbucket.org/hudson/magic-lantern/pull-requests/610/benchmarks-and-self-tests-refactored-as) for fixing nightly builds.
Please test it and report at the pull request link above, to push this to the nightly builds and fix the 600D nightly.
Build removed. This branch has been merged with unified.
Knock knock--Hello, any 60D users out there?
I've been working with a 60D user in the UK on an issue with mv640crop mode video but I haven't heard from him for a while. Is there any 60D user willing to test out a fix for it? I had a solution but a1ex provided a better one and would like to have someone test and report back.
Here's the pull request:
https://bitbucket.org/hudson/magic-lantern/pull-requests/693/fix-mv640crop-mode/diff
And here's a build with the new fix for testing:
Build removed as this has been merged with unified. // Audionut
dfort,
I'll have a play with this. I tried your zip link but it was 404. Do you still need someone to test?
https://bitbucket.org/daniel_fort/magic-lantern/downloads/