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.


Messages - nanomad

Pages: 1 2 3 [4] 5 6 ... 95
76
Maybe it's not clear enough. It used to be a one way process. TL using the ML code base then adding features and fixes on top but rarely pushing those fixes back. As the number of fixes increases it got harder to play "try to blindly port what TL has". Especially without a camera to test things on and with a objectively poor coding standards.

Right now things have changed a bit as 1% pushes things back to ML as soon as they are done. They will undergo code review as all the other contributions do and eventually land in ML too.
This is how things should be done. But there's still quite few fixes buried in TL that need porting and we can only figure those out if the community reports them.

77
Also, 1% is doing an amazing job lately by providing new features and suggestions to ML.

Sure, they may take a bit longer to merge but I'm quite confident that with the help of the community pointing out the differences between TL and ML this split will soon be a thing of the past.

I just want to restate that the only TL discussions not allowed on this forum are those regarding support matters of said fork. You are incouraged to discuss key differences or missing features all you want provided it's a constructive discussion and that it's done in the proper sections and threads.

78
That's correct.

79
Camera-specific Development / Re: Canon 650D/T4i 1.0.4 [Status: Alpha]
« on: March 25, 2014, 10:36:21 PM »
That is good enough :)

I kinda hate taking attribution for something I didn't do. If you push a PR I'll merge it without hesitations.

80
Camera-specific Development / Re: Canon 650D/T4i 1.0.4 [Status: Alpha]
« on: March 25, 2014, 06:09:32 PM »
I have the meters patch in my test queue. A video explaining usage would be great

81
General Chat / Re: Canon EOS 70D (RAW possibility)
« on: March 25, 2014, 06:08:23 PM »
Turns out I already got all I need to get the port started without a camera. But thanks for the dump offer

82
Main Builds / Re: Nightly Builds - try the very latest stuff here
« on: March 25, 2014, 08:52:37 AM »
Nightly builds will now be published only if there has been at least one commit in the relevant branch for that day. This is to avoid wasting computing power when it's not needed (and make regression testing shorter)

83
General Chat / Re: Canon EOS 70D (RAW possibility)
« on: March 25, 2014, 08:32:18 AM »
I may be willing to help, but I unfortunately can't afford a 70D nor do I feel the need to.

If you guys agree I can have a look at the firmware to at least guess the feasibility of the port.
I need a cr2 taken with it and uploaded somewhere

84
Feature Requests / Re: Remap or clone shutter button
« on: March 22, 2014, 05:53:26 PM »
What camera? On some models it is indeed possible to do so

85
Camera-specific Development / Re: Magic Lantern for 5D Mark III 1.2.3
« on: March 22, 2014, 01:26:56 PM »
It's smart. There have been no changes in that branch so it won't build anything

86
Camera-specific Development / Re: Canon 650D/T4i 1.0.4 [Status: Alpha]
« on: March 22, 2014, 11:17:05 AM »
New features starting from the next build:
 - Defishing and Anamorphic preview
 - Expsure Sim control in LV/Photo mode

87
Anyways, these are/were my motivations. I just don't feel good about any of the hostility or schism from what essentially is my first real coding project and mostly a thankless labor of love. At the same time I don't like letting ML down and pissing off A1ex to the point he wants to quit. So everything seems like its burning and I feel like shit and there you go.

I know sometimes we may come off rude or uneducated but trust me that's not the intention. There's no hostility. Quite the contrary in fact. We see potential that just needs to be put to use properly. You did a great job starting and mantaining the 6D/EOSM/50D ports in TL and I see no reason why you shouldn't be contribuiting more back to ML.

True, your patches may have to go through the review process and may be declined or you will be asked to re-write them substantially. But that's what we have started doing too. Work in a branch, submit a PR and ask for a review.
Your latest efforts are not "too little too late". If anything, they are showing that this model may work for ML.

Declaring TL or any other "fork that went too far" as unsupported and out of the scope of this forum is just a way to give devs a push toward the proper direction.  That's the intention, at least.


88
Camera-specific Development / Re: Canon 1100D / T3
« on: March 21, 2014, 09:01:34 AM »
I see, that's because the live view is showing a cropped and upscaled image.

Could you post a 10x bmp along with a jpeg shot of the same scene?

89
Camera-specific Development / Re: Canon 1100D / T3
« on: March 21, 2014, 08:49:17 AM »
Yes it was directed at you. The thing is, I don't see what advantage taking pictures at 10x would give you. If anything, the CR2 and jpeg offers more resolution and bit depth. You can still frame and focus at 10x then batch crop everything in post production. A quick shell script or a photoshop action will suffice.

90
Camera-specific Development / Re: Canon 1100D / T3
« on: March 21, 2014, 08:42:18 AM »
True that. I'll see if I can code something useful. The buffer should be as big as the largest raw resolution, right?

91
Camera-specific Development / Re: Canon 1100D / T3
« on: March 21, 2014, 08:36:55 AM »
You can use the built in Magic Lantern intervalometer but you will have some mirror shake.

The proper alternative would be using raw silent pictures but they are currently not supported on the 1100D. I can hack a module to do 422 as we used to if there's interest

92
General Development / Re: Getting started with development
« on: March 20, 2014, 11:04:44 PM »
Well, most of ML features are defined inside all-features.h. I'd start by undefining them all then working my way up

93
My impression is that people do make monetary donations to the ML project. I have no idea how much this amounts to, if anything.

Would it be possible for the ML project to purchase a 6d for use by one of the core Devs? If so, they wouldn't be proceeding with "blind" development and support.

I personally feel that 1% work has been ok so far. The issue is, we had a lack of contributions back to the main ML tree which prompted this decision (after long, long thinking and delaying)

I'd wish for that because this includes a good system of merge window and point releases after bugfixing, the current "rolling release" model imho encourages newbies to use the rather untested nightly as stable and prevents expermiental patches/modules from being merged.

Yeah, me too. The real issue is that it's a hobby project for many of us and no one wants to deal with managing "another" release cycle (the ones I'm doing at work are enough). Nothing forbids users from making a team and working toward a stable-ish release. As always, I can provide help and tools if needed. Jus ask nicely :P



... unless you're a core dev, in which case you just create a branch and implicitly hand it down to every other fork out there :-p as when a branch is merged/closed in the ML repo it isn't closed in forked repos :- \
That's interesting and something I'll have to investigate.

94
The reason is most people don't read what is written  in the Makefile.user.default header... You are suppose to use a thin Makefile.user containing changed settings only (not everything)


97
During the last 3 years, the development of Magic Lantern has shifted from an almost single-dev hobby project, into something more collaborative, with several people contributing to the project. We feel that the right development model for Magic Lantern is something similar to the Linux kernel.  A group of core contributors make changes that go directly into the “official” builds, and other users contribute by submitting pull requests.  Inevitably, forks of the project will be created for the purpose of adding features and fixing bugs.  We encourage these forks and recommend forking as the best method to submit patches to the main repository.

Recently, one actively popular fork began moving in a direction dangerously far away from the main repository, by adding experimental patches that weren’t pulled back to the main repository for collaboration.  As a result, these patches were relatively untested on some cameras and could not be confirmed as safe for all models.

Until recently, 3 ports (EOS-M, 6D, and 7D) were maintained almost completely on the Tragic Lantern fork and not in the main repository.  It has become increasingly harder to merge patches from Tragic Lantern into the Magic Lantern repository

We feel that the current situation only serves to create confusion among users, split the community, and duplicate development efforts. This makes merging harder than rewriting these features and fixes from scratch, and clutters the forum with duplicate requests, issues and development discussion.

Therefore, we have decided to drop any form of official support for these kind of forks.

Starting a week from this announcement, we will begin actively enforcing this decision by dissolving support of the Tragic Lantern fork, as well as any other fork, that fails to follow the guidelines presented here.


This decision is based solely on the forking of Magic Lantern, and ensuring that these forks do not interfere with the core values set forth by the Magic Lantern development team.  1%, the maintainer of Tragic Lantern, and other users, are free to fork and do whatever they wish with the project.  This decision should not be considered as a personal attack towards 1%, or other users, who maintain their forks in a manner that is suitable for themselves.  We respect the development by all members, including development that moves away from the direction of Magic Lantern.

However, in the end, only the main repository can be called Magic Lantern and be supported on this website for all of the reasons listed within.


I’m a user, what does this mean for me?
Tragic Lantern usage and discussion will no longer be accepted on this forum. Please continue discussion about the Magic Lantern ports in these threads: 50D, 7D, EOS-M, 6D, 600D.

But, I found a bug! What should I do now?
If you feel you have found a bug, please open a bug report on the Tragic Lantern bug tracker. If, after testing the latest nightly build of Magic Lantern for your camera you find that the bug applies to Magic Lantern too, please open a ticket here.

How can I help smooth the transition?
Users are more than welcome to point out the differences between Tragic Lantern and Magic Lantern on their cameras here, in order to assist developers in knowing exactly what to merge back to mainline.  It is strongly encouraged that users and developers take priority in getting the 3 ports (EOS-M, 6D, and 7D) to a stable state where they can be maintained by Magic Lantern.

It is hoped that this will solve a number of issues, including, getting these ports supported in Magic Lantern, and creating a situation whereby it is easier for fork maintainers to create pull requests.

What about existing threads and posts?
Any remaining threads about Tragic Lantern will be moved to this section. Next week they will be locked out and put in read-only mode

98
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
« on: March 19, 2014, 08:02:49 PM »
They have been posted by Alex a few posts back

99
Camera-specific Development / Re: Canon 1100D / T3
« on: March 17, 2014, 01:17:49 AM »
I think it eventually will. It's just a matter of time for someone to catch up with the CONFIG_EDMAC_RAW_SLURP bits for LV mode.

There are two issues right now.
 1.  It's not easy for a developer to grab the raw frame size as the 1100D likes to crash as soon as you enter LV with "old method" for RAW on. Easily solved by turning FPS override on
 2. We can't use the DEFAULT_RAW_BUFFER allocated by canon as it seems to be used for something else. Right now ML code expects the opposite so one should write a routine to allocate a buffer to write to (and free it when not needed anymore)

100
Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 16, 2014, 03:21:04 PM »
I just tried magiclantern-Nightly.2014Mar16.EOSM202 on my EOSM and it works just fine. What firmware version do you have?

Can you try renaming the ML folder and then re-extracting the one from the zip?

Pages: 1 2 3 [4] 5 6 ... 95