Live data from Hacker News

Using FujiFilm SDK on a Camera Voids Its Warranty

fujifilm-x.com

91–100 of 123 posts

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#91

I, for one, can forgive FujiFilm... because, even though recently finally discontinued, they gave us FujiChrome Velvia 100 (& 50).

They also make medium format mirrorless cameras, which are a great way to feel superior to all the people who think "DSLR" is what you call a high-end digital camera.

I can't quite bring myself to spend the money to get a GFX 100S though.

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#92

Earlier quoted context omitted.

If I swap out my car's engine with a more powerful one and screw up the drivetrain will warranty cover it? If I load broken firmware onto my device that screws it up, why should the company be on the hook? Replacing firmware is no different than replacing any other component. What countries force companies to provide warranty when users load faulty firmware onto devices?

A more apt analogy would be the MVD plugged a dongle into the canbus plug and now your warranty is void. I mean, this is exactly what they are doing.

And isn't that normal? If you remap your ECU to use a different fuel mixture that voids the warranty right? That's what google results overwhelmingly say. And it makes perfect sense. Users might alter the firmware to run at a suboptimal setting that increases wear. Would you expect a manufacturer to honor warranty if you bolted on a turbocharger?

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#93
post #48

Earlier quoted context omitted.

For the bigger players, they miss out on market segmentation. An EOS M with Magic Lantern has a number of features that are featured on Canon's cinema line, for example. The M is perhaps no longer competitive in key ways, but had ML been available with today's level of polish in 2012, it would have eaten into higher-margin products. Fuji is perhaps best poised to enable open development -- their pricing structure is…

In the meantime, everyone except professionals and image-quality obsessives has moved to phone cameras, for which Google and Apple have developed incredible software. It's been obvious for at least ten years that camera makers need to improve their software, and they've not done so, or very minimally done so.

I don’t think that Canon and similar could offer anything to compete with smart phones. While smart phone cameras have gotten much better, the real secret sauce is that everyone already has a smart phone. It’s not that smart phones beat DSLRs, its that they got sufficiently good and everyone got them for other reasons. Not having to buy and carry a second device is quite the market advantage, it turns out.

Frankly, no dedicated camera is ever going to win back users with software features, and it is extremely unlikely that Canon or Nikon could out compete Apple and Google in this area. It makes much more sense for Canon to continue to serve hobbyists and pros with features that phones cannot offer, rather than trying to complete on software.

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#94
post #74
post #12

Earlier quoted context omitted.

Is that even legal? It seems similar to the "warranty void" stickers which are nothing more than an illegal scare tactic that many individuals are conned into believing. https://www.ifixit.com/News/11748/warranty-stickers-are-ille... https://www.ifixit.com/News/15464/warranty-voiding-stickers-...

The contract is under Japanese jurisdiction. Does anyone here know Japanese law in regards to something like this?

No, I don’t think that’s how that works. Your contracts with your customers is under the jurisdiction of where your customers live, not where your company is headquartered. It would be way too easy to side step any law they wished that way.

Plus, must camera manufacturers sell through an american subsidiary. I know thats how Canon works.

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#95

This SDK only works on the top end Fuji's, the cheapest one supported starts at £850 (body only) Fuji has famously terrible app support, its a nightmare to set up and cuts out constantly, transferring images over wifi is slow and unreliable to the point of it being useless, the remote shutter is unreliable and doesnt have any of the extremely simple to program features that intervalometer's have. You can't shoot teth…

I haven’t tried Magic Lantern yet, but I have been reasonably happy with Canon’s remote app. It has been reliable so far, with the only downside being that it doesn’t offer GPS tagging for my camera (EOS 80D)

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#96

I am an amateur photographer, and I can't understand why the major camera brands (Canon, Nikon, Sony, Fuji, etc.) aren't open at least to the concept of SDK's to control their cameras (let alone opening the lens mount specifications)... It would make their cameras much more flexible and useful, thus perhaps gaining some users that currently use smartphones where it seems there is greater control over and integration…

For a while in the late 1990s, there was a nominally-open camera OS called Digita. I had a camera that it ran on, and none of the skills to take advantage of it, but I remember someone built DOOM for it so that was neat. People were writing Digita programs to do things like eat NMEA0183 GPGLL sentences and stuff them into the EXIF tags, because USB wasn't ubiquitous yet and a lot of cameras still had RS232 ports and…

No post body was provided.

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#97

Earlier quoted context omitted.

They don’t want to cannibalize the other product markets. Canon for example was caught up with the video features that they added to the 5d back in the day. it sparked a video revolution, but destroyed their camcorder sector. same thing again when they released “cinema” specd cameras, that really just had different firmware than the photography cameras, but priced much higher.

Cinema requires different lenses. A standard camera lens will not remain in focus while zooming. Cinema lenses have to--imposing restrictions that cause the lenses to be a lot more expensive. (A cinema lens works fine for still photography, but why pay the price/weight premium?)

Parfocalness can be emulated in firmware (by adjusting the focus as the zoom changes).

What you probably should have pointed out is the opposite property: keeping the same focal length while changing the focus distance. This can't be emulated in software because camera lenses don't have a motor on the zoom (plus primes don't have a zoom). Some cine lenses do achieve this by moving a zoom-like group (I think all the ARRI master primes do) and not just by being telecentric on the exit side.

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#99

I am an amateur photographer, and I can't understand why the major camera brands (Canon, Nikon, Sony, Fuji, etc.) aren't open at least to the concept of SDK's to control their cameras (let alone opening the lens mount specifications)... It would make their cameras much more flexible and useful, thus perhaps gaining some users that currently use smartphones where it seems there is greater control over and integration…

Japanese gov/corporations have a natural aversion to directly dealing with customers at scale. They’ll want a proxy layer of third party corporations, which can then deal with the minutia of exposing it to end customers. Canon/Nikon/Fuji/Olympus have SDKs and partnerships, they just don’t want to deal with the individual customers.

A "natural aversion"?

Re: Using FujiFilm SDK on a Camera Voids Its Warranty

#100

I am an amateur photographer, and I can't understand why the major camera brands (Canon, Nikon, Sony, Fuji, etc.) aren't open at least to the concept of SDK's to control their cameras (let alone opening the lens mount specifications)... It would make their cameras much more flexible and useful, thus perhaps gaining some users that currently use smartphones where it seems there is greater control over and integration…

I strongly suspect it's just easier from a customer support point of view, if you develop an application that causes the camera to overheat and fail. They really don't want to send you a new camera. The dangerous thing with code controlling hardware directly, is absent safe guards you can easily exceed the mechanical limits of the device. This is why seriously overclocking a CPU will definitely void the warranty, but…

So if an application on your PC makes it overheat and break the PC is at fault for being defective and you get to RMA it? What about a laptop? And a Camera is different how?

In the end it would be faulty / bad design that makes the Camera fail. And that is absolutely a valid reason the RMA it.

Post reply on HN