Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Magic Lantern Is Back

magiclantern.fm

Post reply on HN
Print view View original

141–150 of 170 posts

Re: Magic Lantern Is Back

#141

Post by ChrisMarshallNY »

aorth wrote: post #140
ChrisMarshallNY wrote: post #37

Earlier quoted context omitted.

It’s not too difficult, if you do it from the start, and by habit. I have an xcconfig file[0], that I add to all my projects, that turns on treat warnings as errors, and enables all warnings. In C, I used to compile -wall. I also use SwiftLint[1]. But these days, I almost never trigger any warnings, because I’ve developed the habit of good coding. Since Magic Lantern is firmware, I’m surprised that this was not alrea…

Great, thanks for sharing the links. By the way, rift valley software? I'm writing to you from Kenya, one of the homes of the great rift valley. It is truly remarkable to drive down the escarpment just North of Nairobi!

I used to live in Uganda.

Visiting the Rift Valley in Southwest Uganda was one of the most awesome experiences of my childhood. My other company, Little Green Viper, riffs on that, too.

I was born in Africa, and spent the first eleven years of my life, there.

Had to leave Uganda in a hurry, though (1973).

Re: Magic Lantern Is Back

#142

Post by mcdeltat »

i_am_proteus wrote: post #45
mcdeltat wrote: post #33

Earlier quoted context omitted.

You have an interesting point about consistency and I'd like to provide a counterargument. While control consistency is very important, the actual image you get from a camera varies significantly between models as the manufacturers change tone curves, colour models, etc. JPGs from the camera are basically arbitrary and RAWs are not much better. The manufacturers don't provide many guarantees, it's just up to you and…

If you want JPGs to look different, you can change them in the camera, and RAW files are just that: raw. They will vary between cameras slightly because the cameras have different sensors. Editing RAWs from 5d3 vs. 5d4 vs. 6d (my only experience) is not very different. Ultimately, the workflow that matters is a photographer capturing the image and getting the output to the studio quickly, in high quality. Event photo…

My point about JPGs is they will look different between cameras anyway because of software differences, with the "same" settings, so they're already inconsistent from the user perspective. Editing RAW is not necessarily different but from what I've heard that's because RAW editing software busts its ass to try to correct for all manner of arbitrary differences between camera models. It's in spite of camera design that we have consistency, not really because of.

Re: Magic Lantern Is Back

#143

Post by petee »

bhickey wrote: post #81
t0bia_s wrote: post #78

Earlier quoted context omitted.

I wish there are similar projects for other camera brands like Fujifilm. With abilities of ML on old Canon cameras we know there is a lot of potential in those old machines across other brands. It is also "eco" friendly approach that should be supported.

I just switched from Canon to Fujifilm due to enshitification. Canon started charging $5/mo to get clean video out of their cameras. We're plenty screwed if manufacturers decide that cameras are subscriptions and not glass.

Fuji's are great, but ecosystem is definitely smaller, and I've found some software still doesn't support debayering x-trans

Re: Magic Lantern Is Back

#144

Post by ChrisMarshallNY »

names_r_hard wrote: post #125
ChrisMarshallNY wrote: post #113

Earlier quoted context omitted.

Good point, and really just semantics. I guess you could say native mobile apps are “firmware,” using my criteria. But I put as much effort into my mobile apps, as I did, into my firmware projects (it’s been decades since I wrote firmware, BTW. The landscape is quite different, these days -This is my first ever shipped engineering project[0]. Back then, we could still use an ICE to debug our software). It just taught…

Yes, it gets a bit blurry, especially given how fast solid-state storage is these days. I think IoT has seen a resurgence in firmware devs... but regrettably not so much in quality. Too cheap to be worth it, I suppose. I can imagine a microwave could be quite a concerning product to design - there's some fairly obvious risks there! Certainly, whatever you class ML as, we could damage the hardware. The shutter in part…

You do need to be careful with the shutter. It is possible to do damage (and add dirt) from it.

We had to add software dust removal, because the shutter kicked dirt onto the sensor.

I’m assuming that, at some point, the sensor technology will progress to where mechanical shutters are no longer necessary.

Re: Magic Lantern Is Back

#145

Post by kjkjadksj »

petee wrote: post #143
bhickey wrote: post #81

Earlier quoted context omitted.

I just switched from Canon to Fujifilm due to enshitification. Canon started charging $5/mo to get clean video out of their cameras. We're plenty screwed if manufacturers decide that cameras are subscriptions and not glass.

Fuji's are great, but ecosystem is definitely smaller, and I've found some software still doesn't support debayering x-trans

Yeah like Adobe. Whatever method they use has been peak worm creation for over 10 years. Capture one and dcraw are head and shoulders better.

Re: Magic Lantern Is Back

#146

Post by themaninthedark »

teddyh wrote: post #85
bibabaloo wrote: post #36

Earlier quoted context omitted.

Uh, sure, maybe in a professional setting where you’re getting paid. But this was unpaid volunteer work. If, as a community, we start enforcing professional grade standards on people who are just contributing their free time to give us neat toys and tools, I kinda worry it makes the whole thing the whole thing less fun or sustainable. And if that happens, we probably stop getting these free toys altogether.

Think of it as a non-profit club. If you volunteer to be the treasurer, are you then free to ignore everything and do whatever you like, just because you aren’t paid? Of course not. It’s the same with being a software project maintainer; you have willingly taken on some obligations.

If you volunteer, sure.

If I put some code out on the internet and some other people find it and start using it, they message me we talk and I start adding things they suggest and working with others to improve this code. Then one day I wake up and don't want to do it anymore. At what point did I become obligated? When I published the code? When I first started talking to others about it(building a community)? When I coded their suggestions? When I worked with other coders?

Who get to decide where the line is?

Re: Magic Lantern Is Back

#147

Post by fooker »

names_r_hard wrote: post #138
fooker wrote: post #123

Earlier quoted context omitted.

I recently obtained an astro converted 6D. Have played around with CHDK a long time ago as a teenager but never magic lantern. I am a compiler dev with decent low level skills, anything in particular I should look at that would be good for the project as well as my ‘new’ 6D? (No experience with video unfortunately) I have a newer R62 as well, but would rather not try anything with it yet.

Ah I'd love an astro conversion. I've had a fun idea knocking around for a while for astro. These cams have a fairly accessible serial port, hidden under the thumb grip rubber. I think the 6D may have one in the battery grip pins, too. We can sample LV data at any time, and do some tricks to boost exposure for "night vision". Soooo, you could turn the cam itself into a star tracker, which controlled a mount over seri…

> turn the cam itself into a star tracker

Hmm, that's a neat idea. The better language for it is 'auto guider'. Auto guiding is basically supplying correction information to the mount when it drifts off.

Most mounts support guiding input and virtually all astrophotographers set up a separate tiny camera, a small scope, and a laptop to auto guide the mount. It would be neat for the main camera to do it. The caveat is that this live view sampling would add extra noise to the main images (more heat, etc). But in my opinion, the huge boost in convenience would make that worth it, given that modern post processing is pretty good for mitigating noise.

The signals that have to be sent to the mount are pretty simple too, so I'll look at this at some point in future. The bottleneck for me is that I have ever got 'real' auto guiding to work reliably with my mount so if I run into issues it would be tricky as there's no baseline working version.

> Maybe an auto image upload service?

This sounds pretty useful, even uploading seamlessly to a phone or laptop would be a huge time saver for most people! I'll set up ML on my 6D and try out some of the demo stuff that use the network stack.

Is there a sorted list of things that people want and no one has got around to implementing yet?

Re: Magic Lantern Is Back

#148

Post by AbraKdabra »

Very happy to see ML return, used it in my T2i for 10 years at least, this year I bought a R6 Mark II so no need but I'd be very happy to see it someday with support for ML. Congratulations on the return!

Re: Magic Lantern Is Back

#149

Post by sails »

Amazing to see this, I haven’t thought about this since 2013. This turned my very basic entry level 550D into a crazy powerful camera for time lapse photography, I loved it!

Re: Magic Lantern Is Back

#150

Post by IshKebab »

jibal wrote: post #90
IshKebab wrote: post #84

Earlier quoted context omitted.

That's exactly his point. Languages aren't easier to learn simply because their specification is short, any more than instruments are easier to play because they have fewer strings.

The analogy is completely invalid. Languages with small specifications are easier to learn. It's sad that the dev, who has done great work, has to spend time defending the C language from critters living under a bridge when it's a fixed element that isn't going to change.

> Languages with small specifications are easier to learn.

Only if all other things are equal, which they never are.

Post reply on HN