Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Started by nanomad, March 19, 2014, 08:37:15 PM
0 Members and 1 Guest are viewing this topic.
Quote from: nanomad on March 28, 2014, 06:13:23 PMThen the EOSM thread is waiting for you. Keep in mind that if said changes involve patching assertions in canon code they won't likely make into ML any time soon. Assertions are there for a reason and we don't mess with those as they could cause the camera to enter an invalid state and potentially brick.
Quote from: nanomad on March 28, 2014, 06:13:23 PMAssertions are there for a reason and we don't mess with those as they could cause the camera to enter an invalid state and potentially brick.
Quote from: gary2013 on March 28, 2014, 06:22:52 PMML warns people about using ML at their own risk and possibly bricking a camera. So what is the difference there? A double standard?
Quote from: gary2013 on March 28, 2014, 06:36:43 PMAnd you just admitted the same warnings on ML. So, now what is the truthful way to make people not use T_? What about the guy I just mentioned who claims his loyal faith in whatever ML tells him? He based it on what ML said to scare him about being unsafe. You didn't comment on that.
Quote from: gary2013 on March 28, 2014, 06:14:23 PMThe big problem is constantly hearing one side say how terrible and unsafe T_ is and yet I keep saying I have used every new build everyday and I never had any problems.
Quote from: a1ex on March 29, 2014, 12:27:14 AM7D went unmaintained because 1% did not contribute his work to ML back then.
Quote from: feureau on March 29, 2014, 12:18:12 PMI think specifically, the 7D ML went unmaintained. Well, we used to have some devs working on it.It was g3gg0's brilliant breakthrough that first got ML running on the 7D, but the devs stop when it seems like g3gg0 was offended by what some users complained about. At the time the 7D firmware needed to be signed, and the only way regular users can get the .fir was for the devs to sign them. There were new developments posted on the forum for months but not a single .fir update was posted. Some people felt that the devs kept new developments for themselves and wouldn't share with the community, complained about it and it seems this caused g3gg0 dropped out of the 7D forum.After a long hiatus, someone figured out how to patch the 7D and run an auto loading ML. Not long after that, the community found out that 1% was hacking away the 6D and the EOS-M then someone asked him to take over the 7D development. At the time 1% didn't have a 7D, but said if they could get him one for testing, he'd work on the 7D for TL. The community rallied and got him a donated 7D including raising money for shipping.With the 7D in 1%'s hand, the port went into full development. We even managed to get MLV running. Had it not been for the community's effort, the 7D ML would still be stuck at best with high-bitrate mp4. Of which, the codes has been disabled in ML because it's deemed too risky. But it runs just fine in TL.With nobody working on the 7D ML, the community found someone willing to fork it and run with it. This is just the way natural selection work with open source software. In hindsight it might be nice for some of the developments to get pulled back to ML, but given the way TL changes a lot of things that might break the camera, maybe pulling it back to ML wouldn't be such a good idea given ML's propensity to take less risk.At any rate, I'm really grateful for TL and what 1% has done for the 7D. Just as much as I'm grateful for everyone who has worked on ML. Especially g3gg0.This breaking up of the two branch is breaking my heart.
Quote from: simulacro on March 29, 2014, 05:23:15 PMI don't know what's 1% reaction to be banned from ML,
Quote from: nanomad on March 19, 2014, 08:37:15 PMThis 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.
Quote from: simulacro on March 29, 2014, 05:23:15 PMbut it would be better if you bring back the TL threads. I think everyone there knew the risks, no one complained. As long as the risks of TL are well known by the users, there shouldn't be any kind of complaints
Quote from: nanomad on March 19, 2014, 08:37:15 PMWe 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.
Quote from: Audionut on March 29, 2014, 06:00:47 PM1% has not been banned.
Quote from: nanomad on March 29, 2014, 05:49:17 PM1% is still contributing to the project. Technically speaking he's contributing more now than he was before. It may not look like that from a user perspective but he is.
Quote from: gary2013 on March 28, 2014, 06:14:23 PMI understood all of that. The big problem is constantly hearing one side say how terrible and unsafe T_ is and yet I keep saying I have used every new build everyday and I never had any problems. Yet no one from ML wants to discuss that openly and then maybe rethink their general public statements. We now have a poster (more than likely he is not an M, 6D or 7D user) claiming his loyal faith to ML and he will always believe anything ML tells him. That is sort of pathetic from my view. Maybe he missed my posts in the past about how it never hurt my camera in anyway. Probably no will will see any posts with all the T_ threads closed and hidden now. I am still wondering about this open source if old threads keep getting closed and then censored.I am asking ML to show actual proof that T_ has caused anyone to have these unsafe things happen they claim. Because it sure has not happened here on my M camera withg every build since last July to date. I am happy to see at least some people speaking out more on this and a little bit of discussion being made openly.
Quote from: Critical Point on March 30, 2014, 05:13:27 PMWell, from what I can see, things get very slowly ported into ML, if at all. I my self am using TL because it gives me control over the H.264 bitrate and GOP. This is an amazing feature, something that really matters, but will this get ported into ML ? Probably not. And why ? Only God knows why not. As long as you don't port into ML things that really are important, you can't blame 1% for offering those features in his TL.
Quote from: a1ex on March 28, 2014, 07:23:26 PMTL had a strong tendency of disabling the error message rather than fixing the actual cause of the problem. WAV recording is one of them: I wrote the memory backend to catch mistakes, it caught a severe bug in the wav recording code (writing to unallocated memory), and I have disabled the feature until a proper fix is found. What 1% did? He bypassed the memory backend, disabling the error message but keeping the bug.Same for many other things that were my own code, I found them to be buggy (e.g. movie remap, sraw, dual iso preview) and disabled them. TL simply enabled them without actually fixing the issue I found.Result: waaaa, Tragic Lantern has more features!!!Not to mention that bitrate adjustments and beep code from TL were implemented by removing the safety checks (assertions) from Canon code. These checks are there for a reason, and disabling them is something I don't agree with.
Quote from: feureauHad it not been for the community's effort, the 7D ML would still be stuck at best with high-bitrate mp4.
Quote from: Critical Point on March 30, 2014, 05:13:27 PMWell, from what I can see, things get very slowly ported into ML, if at all.
Quote from: Critical Pointbut will this get ported into ML ? Probably not. And why ? Only God knows why not. As long as you don't port into ML things that really are important, you can't blame 1% for offering those features in his TL.
Quote from: a1ex on February 17, 2014, 09:14:05 AM1% can share his bitrate code as a module that can run on top of normal ML
Quote from: feureauThe bitrate hack originally came from ML.
QuoteThere's a big difference between warning users to expect rough edges, and willfully keeping code that was proven to be dangerous...I have an engineering background, and I'm trying hard to build software that would not fall down when the first woodpecker comes along.
Quote from: Critical Point on March 30, 2014, 09:43:48 PMAfter having used TL for over a year now, it didn't chewed up my camera, and works just fine.
QuoteGive us an alternative in ML and we'll gladly give up TL, but unfortunately this is not happening, you guys want us to give up TL and go back to nothing.
Page created in 0.096 seconds with 17 queries.