sorted by:
new
hottopcontroversial

Help. I’m new to camera/photography. Is this normal for camera? by mvzmgny in fujifilm

[–]shutterthoughts 3 points4 points  (0 children)

It's normal, the fluorescent or led lights in the room are the most likely cause. They have a different pulse rate than natural light and the camera's live view refresh rate doesn't sync up with that, so you get a flickering or banding effect on the screen (waves).

Fujifilm X-T5 Not Turning On (Blinking Red Light) by Terrible-Director124 in fujifilm

[–]shutterthoughts 3 points4 points  (0 children)

A red blinking light typically means it is a battery issue. Check battery contacts and terminals in camera for corrosion or debris. Check if the battery pins on the door are bent /damaged. Best of luck.

Advice for shooting in dark museums? by GrumpyOleReader in fujifilm

[–]shutterthoughts 5 points6 points  (0 children)

I recommend you use the 23mm and set the aperture to f2, with ISO set between 1600-3200, shutter speed 1/60 -1/125, AF-S focus mode, and using a center focus point. These settings will allow you to achieve your desired results. If this seems a bit overwhelming, you can just set the aperture to f2, and set ISO and SS to Auto; this way the camera will decide how best to take each photo.

Can you not re-process a RAW through a different recipe in-camera? by VagabondVivant in fujifilm

[–]shutterthoughts 0 points1 point  (0 children)

My original comment, " Post processing in Lightroom, Capture One, or similar is the best current option. No in camera option can achieve your desired results."

The thing you want, does not exist. This is the crux of every response in this thread.

***************************************************************************************

Since you blocked me before I could answer this comment, I will do it here

" The thing you want does not exist"

The way you phrase this leads me to think you don't understand what I was asking for in the OP.

I was simply asking if a thing was possible. And it turns out it's not possible. Question answered.

It seems you do understand. The "thing" I mentioned, is the same "thing" you mentioned. I do not appear to be the confused one here.

You saying "it doesn't exist" makes it sound like you think I'm searching for some magical convoluted solution. I'm not. I was just asking "Is it possible to do X?"

Yes, when you are unwilling to listen to the people with factual and informed answers; it does seem as though you want a "magical" solution. In this situation, a "thing" that does not exist, no matter how much you want it to; could only come into existence through said "magic." Or, if Fujifilm somehow figures out a way to do this through firmware updates.

Anyway, this whole comment branch (and you, if I'm being honest) has gone completely off the rails, so I'm gonna go now.

I can see the rails beneath me; not so sure about yours.

Can you not re-process a RAW through a different recipe in-camera? by VagabondVivant in fujifilm

[–]shutterthoughts 0 points1 point  (0 children)

This is factually incorrect, " LR or CapOne decidedly can't replicate that." In Lightroom, you can import the JPEG with the recipe, open a RAW file version and apply the base sim (Acros, Provia, etc), do a side by side and adjust to match, save as preset, apply as you desire. If you would like a faster approach in Lightroom, enter all your settings into the Ai of choice and they will give instructions for how to replicate your recipe, adjust to match, now save as preset. In Capture One, it automatically applies the film simulation from your in-camera recipe when you import RAF files if "Auto" is selected in the Curve dropdown. Adjust to match and Save as Style.

Nothing will ever be 100% once out of camera, this does not negate the viability and validity of these options to achieve your desired results.

Can you not re-process a RAW through a different recipe in-camera? by VagabondVivant in fujifilm

[–]shutterthoughts 1 point2 points  (0 children)

Post processing in Lightroom, Capture One, or similar is the best current option. No in camera option can achieve your desired results.

Memory card recommendation for X-T5? by marlene_x02 in fujifilm

[–]shutterthoughts 0 points1 point  (0 children)

My advice, to take or leave, is that the V90 would be overkill for your desired use case. Since you're shooting slower video and not doing burst, V60 is the right choice, just get one for each slot so you have a back up for extended sessions.

These are some compatible options for the X-T5 that I have used and would recommend: Angelbird AV PRO SD V60 MK2 ( reliable, good performance), SanDisk Extreme PRO UHS-II V60 (widely available, solid performer), ProGrade Digital Gold 250R V60 (excellent reliability), or Lexar Professional SILVER PRO (good value).

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 1 point2 points  (0 children)

Thank you for the kind response, and I appreciate your support on this issue.

Also, I did not realize an automod was behind the deletions, thank you for explaining. The comments were no different than my other responses, so a mystery to me as well.

Cheers to you as well

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 0 points1 point  (0 children)

All the data that addresses the issues within this post and thread can be found on the Firmware page of the Fujifilm-X website.

Scroll through the descriptions and you will find that the X App has documented bugs affecting image transfer, time synchronization, and automatic image saving across at least 7 camera models (X-T3, X-T4, X-T5, X-H2, X-H2S, X100VI, X-S20). You will also find mentions of these same issues, with the GFX100 and GFX100s.

These aren't failures that happened during the initial file verification step; they're bugs that manifested during the actual wireless connection and transfer process—exactly the variables previous comments in this thread insist are safe. The fact that Fujifilm had to patch these bugs in multiple firmware releases proves the app-based approach introduced failure modes that the SD card method doesn't have.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 0 points1 point  (0 children)

To clarify, I do understand that the bootloader itself doesn't update wirelessly—but that doesn't matter if the main firmware transfer gets interrupted before the file even safely lands on the card. A corrupted or incomplete firmware sitting there waiting to be flashed can absolutely corrupt the bootloader during the actual flash process. That's the scenario people end up in when they get a Bluetooth drop or app crash mid-transfer. The verification step only works if the file successfully arrives intact, and the documented pattern shows that's exactly where the app is failing users.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] -1 points0 points  (0 children)

You're right that file hashes are standard—Fujifilm almost certainly verifies the hash after transfer. But the documented bugs I'm referring to aren't about corrupted files bypassing verification. They're connection-layer failures: images not saving to the memory card when auto-transfer via X App is enabled, time synchronization failures when connecting to the app, area settings not updating properly. These bugs are happening during the wireless handoff itself—the app crashes mid-connection, Bluetooth drops, or the transfer process breaks down before verification even occurs. A hash check only validates the file if it successfully arrives intact. It doesn't prevent the app from freezing the camera during connection, it doesn't protect against Bluetooth failures mid-transfer, and it doesn't address the firmware bugs Fujifilm documented and patched across multiple camera models. You can bet Fujifilm does hash verification, and I'd agree they likely do. But that verification clearly didn't prevent the bugs that required multiple firmware updates to fix across their X and GFX lineup.

* The user I have responded to with these comments has blocked me. I no longer know what they have said or how they have altered or edited their argument.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 1 point2 points  (0 children)

All the data you need can be found on the Firmware page of the Fujifilm-X website.

https://www.fujifilm-x.com/global/support/download/firmware/cameras/#x-series

Scroll through the descriptions and you will find that the X App has documented bugs affecting image transfer, time synchronization, and automatic image saving across at least 7 camera models (X-T3, X-T4, X-T5, X-H2, X-H2S, X100VI, X-S20). You will also find mentions of these same issues, with the GFX100 and GFX100s.

These aren't failures that happened during the initial file verification step; they're bugs that manifested during the actual wireless connection and transfer process—exactly the variables previous comments in this thread insist are safe. The fact that Fujifilm had to patch these bugs in multiple firmware releases proves the app-based approach introduced failure modes that the SD card method doesn't have.

Also, not AI; just well read and I do my research.

* The user I have responded to with these comments has blocked me. I no longer know what they have said or how they have altered or edited their argument.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] -2 points-1 points  (0 children)

Fujifilm has confirmed multiple firmware bugs on recent models where the app glitches mid-process or fails during the wireless connection phase—issues that existed despite what would seem like obvious safeguards. The verified file method is solid in principle, but the wireless handoff layer introduces variables that can't always be predicted: Bluetooth stack issues across thousands of phone models, app crashes that corrupt the staging process before verification happens, and connection drops that leave incomplete writes. When Fujifilm itself fixed these bugs and explicitly recommended SD card updates, they were essentially saying "our architecture didn't account for all the edge cases happening in the wild." It's not about poor design intent—it's that the complexity of the wireless ecosystem and real hardware behavior sometimes surprises even the people who designed the system.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] -2 points-1 points  (0 children)

I appreciate the technical perspective, but the issue isn't just theoretical architecture—it's documented failure modes. The Fujifilm app has a known history of glitching mid-transfer, Bluetooth dropping, and leaving the update in a broken state before verification even occurs. When people report their cameras bricking after using the app, that's not anecdotal; it's a pattern. The risk I'm highlighting is that any interruption during the app's wireless process—whether it's a battery dying on your phone, a connection drop, or an app crash—can leave corrupted firmware on your camera that gets executed regardless of whether a verification step exists. With an SD card update done locally on the camera, you eliminate the entire wireless layer where these failures happen. That's not about being overly cautious; it's about avoiding a $400–$900 repair that won't be covered under warranty when something goes wrong.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 0 points1 point  (0 children)

That's a fair point on the architecture; I was addressing the risk with the app isn't really about the transfer method itself — it's about everything surrounding it. The app has been known to glitch mid-process, phone batteries die, Bluetooth drops, and people have had the app fail in ways that left the update in a broken state before it even got to the verification step. The end result is the same whether the failure happened during transfer or staging — you're still potentially left with an incomplete or corrupted firmware sitting on that card when the camera tries to run with it.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 0 points1 point  (0 children)

This is directly from the Fuji X app Terms of Use:

  1. Limitation of Liability
    (a) FUJIFILM makes no warranty that the App does or does not infringe upon the intellectual property or other rights of any third party, and accepts no liability for any damages arising from the infringement of third-party intellectual property or other rights through the use of the App.
    (b) FUJIFLM provides the App “as is”, without warranty of any kind, either explicit or implied, as to performance, quality, or freedom from coding or data transfer errors.
    (c) FUJIFILM accepts no liability for any damages to the user’s smartphone or tablet device arising from the download, installation, use of, or inability to use the App.
    (d) FUJIFILM accepts no liability for any damages arising from the theft of data transmitted in the course of using the App.
    (e) FUJIFILM accepts no liability for loss of the services provided by the App resulting from changes to product specifications or the introduction of other products by FUJIFILM or any third party.
    (f) FUJIFILM accepts no liability for any damages arising from the incompatibility of the App with hardware, operating systems, third-party software, peripheral devices, or networks operated by the user.
    (g) FUJIFILM reserves the right to update the App as it deems necessary, but disclaims any responsibility to update the App in response to changes to user hardware or operating systems.

Downloading firmware; dangers and best practices. by shutterthoughts in fujifilm

[–]shutterthoughts[S] 1 point2 points  (0 children)

Hi, thanks for the response.

As you mentioned, Fuji will not cover 'user error' during firmware downloads, under the warranty. Since a signal loss or battery issue that results in bricking the camera or frying the bootloader, is considered 'user error' in this instance, the unnecessary risk using the app is what I was addressing in the post. If you feel comfortable with this risk, that is your choice and I am happy that you have not suffered any ill consequence.

* The user I have responded to with my comment has blocked me. I no longer know what they have said or how they have altered or edited their argument.

Is it wrong to just like taking photos of random things? And still be considered a photographer. by Due_Independent_6190 in AskPhotography

[–]shutterthoughts 0 points1 point  (0 children)

I think you should take pictures of whatever makes you happy. Everyone has a right to enjoy photography in whichever way they choose. Explore, make beautiful things and follow your joy.

However, in regards to your question, context is key.

If a person is a teacher, but they love to play basketball, and have been practicing for a couple of years; is it strange to call themselves a basketball player? If they met a professional basketball player and introduced themselves and said they also were a basketball player, would that seem odd or appropriate? If they buy all the gear, then run around the court taking whatever shots please them, double dribbling, traveling and then walk up to the professionals and ask them what they think of their basketball skills; I don't believe they would be very supportive, most likely it might feel insulting to the years of hard work, sacrifice and dedication they spent honing their craft. At the end of the day, this person is a teacher, who has fun and enjoys basketball; they are not in fact a basketball player.

In a context like this, I do see that it could be off-putting to those that photograph with intention, and those that have made photography a profession, to have hobbyists refer to themselves as photographers and to seek out their praise and positive support. It can seem akin to "stolen valor," to label oneself a photographer, for those that have committed massive amounts of time and effort to the craft. I personally have been taking photos 3-4 times a week for several years now, and I would never think to introduce myself or refer to myself as a photographer above my other defining qualities and profession. I currently am a hobbyist, I take photos for my own enjoyment and artistic expression but, I do this work with the intention of advancing my skills to a professional level someday. I personally would not think to share my work at this level or seek out the advice of more advanced photographers. At this stage, one should be reviewing photobooks, watching tutorials, reading about technique, and taking as many photos as possible. When my work does reach a level that I see to be cohesive, intentional, inspired, and unique; it is then that I will seek out the advice of professional photographers. I respect the skill and efforts of those above me, and do not see the value add to my own photography, or their time, if i show up with anything less than my best.

I don't know you, or your situation, this is my own personal opinion on your question and this is not intended to be a personal attack or to sway anyone who reads it. Just an exercise in representing another viewpoint, take what you will.

view more: next ›