rendering – How is this lantern glow effect achieved?

enter image description here

I was wondering if anyone knows how this lighting effect is achieved. It’s clearly not a bloom shader. My best guess right now is that it’s a billboarded transparent sprite, which is animated to give it a pulsing effect. I’m pretty sure the visual effect is separate from the surrounding point light. If anyone could positively identify the technique that’s being used, I’d appreciate it.

Is Magic Lantern giving incorrect shutter counts on my Canon 500D?

I bought a new camera (500D) and have had it for about 4 days. I have installed the latest version of Magic Lantern on it to get a little boost, but when I got into shutter count it gives me 14k (13988 + 177)??! in 4 days (I took about 200 photos)…

My 500D is brand new (well, I bought it in store as new, with box closed). Is it possible that the count on MagicLantern is not accurate on 500D??! Or is there some other software or trick to get proper shutter count?

dnd 5e – Bullseye Lantern: does pointing one away from you, keep you in darkness?

Suppose my character is in darkness. I light up a bullseye lantern:

A bullseye lantern casts bright light in a 60-foot cone and dim light for an additional 60 feet

If I point the bullseye lantern away from me, is my character illuminated in any way? Am I included in the cone of light, or am I outside of the cone, like when casting the Cone of Cold spell?

If I remain in darkness when using a Bullseye Lantern, then I can remain invisible to those without dark vision, while illuminating my enemies.

canon – Magic lantern vs. tragic lantern. Any differences?

Tragic Lantern is a fork of the Magic Lantern codebase, which means it was based on ML, but is no longer a part of ML or supported by the ML community. But probably the biggest difference is that from what I can tell, TL development is no longer active (the latest commits I can find, on are from 2014). I suspect all TL development has moved back to ML.

And yes, just like with its parent project, Tragic Lantern builds are model/OEM firmware-version specific. (See also: Is there a way to get Magic Lantern on my newer model Canon?)

The main history is that the user “1%” began learning to code and chose to use the ML code base as his first project, because he had an (at the time) unsupported 7D and wanted to see if he could add it. 7D users rejoiced. He made a lot of progress (not just on the 7D, but also the 6D and EOS M) and did amazing things, but he was inexperienced and not versed in two major things that caused trouble down the line.

The first issue was that while he knew how to download the codebase and develop from it, he wasn’t versed in open source practices, and did not habitually push his code changes back to the main ML development effort for review and inclusion into the main ML development repository, or pull down newer codebases to stay in sync with the current development everyone else was doing. As a result, as time went by, TL got more and more out of sync with ML, and trying to roll in his new features (on old code) eventually became more effort than simply rewriting from scratch in the current codebase.

The second issue was that he activated some features by simply ignoring known bugs. So TL had features that ML chose not to activate for safety reasons. In the main thread on the Tragic Lantern fork on the ML messageboards, “a1ex” (the main contributor to ML) pointed out that 1% had, for example, enabled WAV recording, which was known to write to unallocated memory. Without fixing the issue first. (As far as I can gather as a non-programmer, 1% misinterpreted the situation and thought he was disabling the write capability, not just an error message).

Naive users of the models that only TL supported or who wanted the features TL has that ML doesn’t, of course, complained, and gave anecdotal “evidence” that since their TL-equipped cameras hadn’t crashed, clearly the code was safe. 1% was also putting up with some harsh criticism and felt that his efforts were unappreciated, while the ML developers were upset about all the wasted effort that could have (from their POV) been avoided. But basically, it was a huge mess of hurt feelings and a Big Learning Experience for all. And forking TL off as a separate open-source project was the cleanest way of getting out of the mess. And then everyone rolled up their sleeves and started working on backporting 7D features from TL.

Today, ML supports the 6D, 7D, and EOS M. And is still very actively developed. Unless you rely on one of the TL features that isn’t active in the ML code, then you should probably stick with ML.

firmware hacks – Is there a way to get Magic Lantern on my newer model Canon?

The newer your Canon camera model is, the less likely it is that there will be a Magic Lantern build for it (just as with Canon P&S cameras, the less likely it is there will be a CHDK build for it). These things take time to develop. If you have to have these features right now, your best bet is to get a hold of one of the models that is supported. The newest dRebel model that is currently supported is the 700D (which came out in 2013); your 750D came out this year. It may take two years or more from the time the camera’s introduced.

Understand that Magic Lantern isn’t anybody’s job. It’s an open source project developed by volunteers. For them to develop a build for your camera, they need access to a copy of your camera, and enough volunteers willing and capable of a) downloading the firmware, b) adapting ML’s source code for it, c) testing that build, d) and debugging it. These things can all be relatively scarce, as is the spare time for volunteers to do them.

If you need a build for your camera and it doesn’t exist yet, the best thing you can do is to volunteer and contribute to the ML development effort (see: this thread where someone steps up for the 760D) or donate.

But understand that the ML folks get overwhelmed all the time by folks who “need” ML for camera X, don’t want to spend a dime, can’t code, won’t test, and who have no idea of the time, effort, and dedication involved in getting what they want, and who have no intent to help with the process, or any idea just how difficult/impossible the thing they’re asking for can be, let alone the internal culture and accepted practices issues of the ML development community (see: Tragic Lantern fork thread).

So if you go over to the ML forum to beg someone to make a 750D build—or even just for feature X—understand what you’re stepping into. The communication divide gets very frustrating, on both sides.

To put it simply: if you’re not going to be part of the solution, then the only thing you can do is wait and hope someone else steps up and does the work.

firmware – Failed attempt to install Magic Lantern on Canon EOS M50

What you downloaded and put on your camera was simply a piece of firmware that allows you to change the boot flag of the camera. IT IS NOT A MAGIC LANTERN BUILD; it is a developers’ tool that allows a coder to change the boot flag so their camera can load their code for testing. This is very clear when a1ex wrote just above the file link:

Please find the FIR file for enabling the boot flag on the EOS/PowerShot M50.

Magic Lantern uses a boot flag to tell the camera whether or not to load the autoexec.bin from the Magic Lantern build after loading the regular firmware. If the autoexec.bin doesn’t exist, nothing happens.

There is no official ML build for the M50, yet.

Just grabbing whatever files you can find on the MagicLantern site’s discussion board threads and loading them is A Very Bad Idea if you’re not a firmware coder with the appropriate knowledge and tools to unbrick your camera. If you cannot actually follow the developer discussion from where you grabbed the file, do not load it, it is not for you. It is for the developers.

Stick to whatever’s posted in the downloads area, and if there isn’t anything for your specific camera body, then wait—or contribute—until there is. Keep in mind, this will be a far more difficult port than with the dSLRs, because the M50’s code is based in part on the Powershot code vs. the dSLR code the ML developers are familiar with; whole sections of code they’re used to being able to rely on aren’t there. Again, a1ex observes, further down thread:

It has some bits from PowerShot firmware, which makes it a bit different from all other EOS models. I mean, porting ML is no longer going to be “just” pattern matching; there will be parts of the code requiring wrappers or other “creative” solutions, not required on other models. That’s where the difficulty comes from.

Trivial example: I could not find one of the stubs (GUI_Control), so I wrote a function that did the same thing, from scratch. I believe it’s present on all regular EOS models (80D, 5D4, 200D, 77D, 7D2 and so on). …

See also: Is there a way to get Magic Lantern on my newer model Canon?

canon – Magic Lantern in 2020 or native specs

I am photographer and videographer and my main subject is product photography (antiques, watches, jewelry,…) and one of my biggest issue is poor sharpness and bad looking video from my Canon 77D.

I was planning to upgrade to the Fujifilm XT4 wich offers native 10-bit 4k at an impressive bitrate of 400mbs. That would solve my issues, however I am considering the fact that I own may Canon’s glass (like the 2nd version of the 24-70 2.8L), since I want to upgrade for getting better video results, I am not sure if it worth considering the 5D mkIII with Magic Lantern, wich seems to allow 4k ROW at 14-bits. It is way cheaper for me and easier to get in short term.

I am truly confused guys with the “exact specs” ML allows in the 5D III, and if it worth considering it in 2020. So I highly appreciate your recommendations.

About the 5D mkIII specs I would appreciate if someone can tell me of there is a crop as you get in high resolution, if the footage is sharp, what is the maximum bitrate, what is the maximum frame rate, and what are the limitation of pushing the specs toward the limits…. what is the most best/usable/stable you can get form ML in the 5D mkIII?

Thank you in advance.

entity component system – ECS – Lantern implementation

I want to implement ECS in my game. The more I read the more insecure I get.

I read a lot about when to use a new Component but the border is quiet messy. In my current case I have a RenderComponent which includes all data needed for an Object to be rendered (mesh, texture, normalmap, etc.) and a PositionComponent with all the stuff where to render ( position, scale, rotation) – Extra component because CollisionComponent need this information too.

With all that I have two Systems: RenderSystem and CollisionSystem both take PositionComponent but only RenderSystem will take RenderComponent.

Now I want to add lanterns. In my current engine lantern is a child from a RenderableEntity (mesh, texture, normalmap, etc.) and has the attributes brightness and Light Colour.

My Problem is how to add this feature to the RenderSystem:

  1. Add this information to the RenderComponent and add an additional bool with isLantern and in the RenderSystem there is a logic who handle this.
  2. Add this information to the RenderComponent but this time witch a enum {LANTERN, DEFAULT, ..}
  3. I add a new LanternComponent to the mix and the RenderSystem will lookout for this additional component
  4. I add a new LanternComponent and a new LanternRenderSystem an this system will lookout for this component

I use OpenGL for the graphics I’m not sure if I should use No. 4. at all. Multithreading rendering sounds complexer than I want to go.

The Lantern is only an example. I have other entities with the same Issue where the RenderSystem has do additional work something like mirrors and water.

What is the way to go?

canon – How do I turn off Magic Lantern information in Live View?

It's annoying. I need to see the entire frame in live view, including the edges, to check the composition. So I try to turn off all information in the live view by pressing THE INFORMATION. Button. However, if the usual CANON information is hidden, Magic Lantern Live View is displayed. I just need a clear live view frame with no information! How do I turn off Magic Lantern Live View information?