1
General Chat / Re: Apertus Axiom Beta
« on: September 28, 2014, 02:48:30 AM »
donated! and shared, read about it when it was in alpha, hope you guys have fun with it!
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.
that would be awesome. I do not know how to compile mo file but would love to try full res silence on my 5d2. thank you
A bug is anything that it shouldn't be.
Spelling mistakes are bugs (which is also a good way for non-programmers to get into "programming" and bug squashing; create a fork, fix the typo, push back to the main repo, congrats your first bug fix and first addition to the code base).
Anything that doesn't work like it's meant to (from modules to button presses).
Anything that doesn't work on your camera (it may work on one camera but not on another).
In addition, when filing a bug report, there are priority settings, so if you find something and think "well that's not really a problem" but it is a "bug" then you can tag it as a minor bug.
I've been thinking for some time now, of providing a build sharing service, where I compile some stuff, and users can test it.
All the fun toys from the branches for instance, and any other stuff that is being developed, but not pushed to the nightly builds.
I think there are some users who for whatever reason, cannot compile, however, they would still be able to provide useful feedback to the development process. This would be a way for users who cannot develop, to help. Like a bug finding process by users.
Guess now is the time. I'll look at setting things up tomorrow.
If I happen to find a way to stop it actuating mechanically (squeezing a paper around somewhere? lol), would it effect the video shooting capability of my camera?
That's sample "c." You have it in reverse order for the full shots. The one I have the most difficulty telling apart is the building shot.
the only thing i can think of which would be helpful to have higher res, is doing software stabililzation. i think i need about 3% edge area to get my preferred stabilization, so even the 1% gain in pixels would be handy, but not dire.
Interesting, so I got 2/3 correct on the test. I'm surprised that I guessed sample "a" wrong. Even after comparing the "side-by-side" shots, my eyes are still biased toward the 1856 shot.
You can also use the width tag
[img width=900]