Fujifilm X-T4 camera rumored specifications : 6k60p video and 10-bit internal

Do you use a cage for your camera?

Nope. And no cables or attachments either. Just the camera, and 90% of the time it's on a one-arm gimbal.
If I ever shoot something bigger then I'd need to hook up director monitor and other stuff, but for what I do right now this is perfectly enough.

Still can't figure why everyone seems Hell bent on editing a long GOP, terrible editing codec like H.265?
,,,
H.265, while it looks great, is not an editing codec. Prores and lots of other flavors are.
If my PC can work flawlessly with H.265 footage, then H.265 is an editing codec. Transcoding takes time, adds steps, and can only lessen the quality of the footage. If performance is not good, then I will transcode, but if I can avoid it, I will.

With 16mm, the IBIS needs to be disabled to avoid corner warping.
Oh crap

Just beware that while the XF 16mm f/1.4 WR is a magical lens, I love mine, I have only operated it wide open once in a situation on a documentary where I really didn't have a choice. Upon reviewing the wide open footage, I found it noticeably softer and not nearly as good microcontrast as stopping that same lens down to 2.8 or 3.5.
Oh crap

Sounds like I would really really really miss my sigma 16mm f/1.4...
 
If my PC can work flawlessly with H.265 footage, then H.265 is an editing codec. Transcoding takes time, adds steps, and can only lessen the quality of the footage. If performance is not good, then I will transcode, but if I can avoid it, I will.

I get your take on it but to me, editing H.264 and H.265 is akin to driving down the freeway with a boat anchor dragging behind your car. You might achieve the speed limit but you're going to tear up a lot of asphalt along the way.
Several video engineers, compression experts at the studios and even Adam Wilt impressed upon me more than a decade ago the computational differences between Long GOP (Interframe) and Intraframe compression schemes and what kinds and amounts of
resources each sucks from your system.

Call me old fashioned but to me I'd rather have 35% CPU and GPU load than 90%, I like a margin of safety for stuff that just happens that often you don't hear about until you send the
master file for QC and it comes back with weird little frame, timing, glitchy errors that might even be hard to see with the naked eye unless you know what to look for. A good amount of
material I shoot for the studios has to pass QC and when the report comes back the master didn't pass, clients on deadlines are not happy. YMMV of course!
 
Nope. And no cables or attachments either. Just the camera, and 90% of the time it's on a one-arm gimbal.
If I ever shoot something bigger then I'd need to hook up director monitor and other stuff, but for what I do right now this is perfectly enough.
Haha, well then why did you answer my question? You are so obviously not the type of camera user i was asking. If you have no cables or connections and running on a gimbal, then of course a nicer EVF, durable i/o’s and handgrip ergonomics don’t apply to you! Haha
 
I get your take on it but to me, editing H.264 and H.265 is akin to driving down the freeway with a boat anchor dragging behind your car. You might achieve the speed limit but you're going to tear up a lot of asphalt along the way.
Several video engineers, compression experts at the studios and even Adam Wilt impressed upon me more than a decade ago the computational differences between Long GOP (Interframe) and Intraframe compression schemes and what kinds and amounts of
resources each sucks from your system.

Call me old fashioned but to me I'd rather have 35% CPU and GPU load than 90%, I like a margin of safety for stuff that just happens that often you don't hear about until you send the
master file for QC and it comes back with weird little frame, timing, glitchy errors that might even be hard to see with the naked eye unless you know what to look for. A good amount of
material I shoot for the studios has to pass QC and when the report comes back the master didn't pass, clients on deadlines are not happy. YMMV of course!

Get yourself a GPU that supports hardware accelerated encoding/decoding of h264/h265!

After having a new Mac Pro 7,1 purchase collapse, I've had to build myself a new Mac Pro 5,1 (having literally just sold basically the same machine), my old 5,1 was basically maxed-out with a Titan X 12GB GPU and the most powerful 12-core processors it could take, and editing/playback of h265 footage was impossible (h264 it could manage okay).

With my new 5,1 build (which now incorporates a pair of Radeon VII GPUs that I'd bought for the 7,1 instead of the Titan X), I've been able to activate hardware accelerated h264/h265 encoding/decoding - and it completely changes the game. Playback, editing, rendering of H265 and H264 material is as smooth as butter. So I'd now have ZERO issues pushing an entire project through post in h265. It's become a complete non-issue - and that's on a 10 YEAR OLD computer!

I was grumbling and groaning about h265 too with my previous build (of the same computer), it but it's literally just about getting the right GPU, and making sure you can enable hardware acceleration with it.
 
Really?

(It's called a forum).

I am sorry.

Sam H and i have been interacting for a while. We have discussions dating back at least 8years. Him and i can joke around with each other. Or at least, i don’t mind. He has a pretty good level of confidence, and he and i collaborated on a couple threads. He is someone that i often end up replying and commenting to across hundreds of threads. And i know he can forgive a little chiding, and roll with it.
 
I am sorry.

Sam H and i have been interacting for a while. We have discussions dating back at least 8years. Him and i can joke around with each other. Or at least, i don’t mind. He has a pretty good level of confidence, and he and i collaborated on a couple threads. He is someone that i often end up replying and commenting to across hundreds of threads. And i know he can forgive a little chiding, and roll with it.

Fair enough. The written word often doesn't represent the true meaning behind the thought, so cut this cranky old bastard a break.

Thanks.
 
Fair enough. The written word often doesn't represent the true meaning behind the thought, so cut this cranky old bastard a break.

Thanks.
Thank you. And it is always admirable to see others stick up for each other. So, i actually am kind of glad you said something.
 
Haha yes, no worries :)

I answered becuase I thought it was an open question to everyone. If you only get answers from people who shoot like you do, then the answer will be that they like what you like. Not a very useful query.
On the other hand, I completely understand that I'm a fringe user: I work on something completely unrelated, and even if I spend way more time and money on this than would be reasonable, it's just a hobby for me. But still I think I'm representative of a lot of users. Among other things: most people I see shooting on the streets are using a very similar setup: shooting marketing events or weddings or whatever, just with the camera and a small gimbal.
 
Haha yes, no worries :)

I answered becuase I thought it was an open question to everyone. If you only get answers from people who shoot like you do, then the answer will be that they like what you like. Not a very useful query.
On the other hand, I completely understand that I'm a fringe user: I work on something completely unrelated, and even if I spend way more time and money on this than would be reasonable, it's just a hobby for me. But still I think I'm representative of a lot of users. Among other things: most people I see shooting on the streets are using a very similar setup: shooting marketing events or weddings or whatever, just with the camera and a small gimbal.

My question was poorly phrased and too vague.


Firstly, you do represent a lot of the shooters out there in the world. In particular the hobbyists, and the self made content creators. Even many traditional pros use those setups for jobs, because they work. They are tools. We all love them. I think this past weekend i did a setup for a production that was looking for ronin s configurations.

The question wasn’t about what is the one best camera, as in this day, having so many options is the best part.

My question was related to reading about all of these professionals that love the smaller form factor but miss having standard features like durable and high quality i/o ports. A body that is slightly bigger, but doesn’t require a cage, etc. there are diminishing returns on size. Cameras are cheap enough, that it is totally possible to have the micro mirrorless for gimbal work on standby, and a slightly larger body as A Cam that allows for basic industry standard workflow.

Looking at the market, and asking others, it would seem that everyone hates the idea. It doesn’t exist! And any time it gets brought up, people make strong cases for tiny fingers mirrorless bodies, camcorders, brain boxes, and shoulder mounts, which already exist.... and yet, there is still a hole in the market for smaller ergonomically shaped bodies that have pro i/o.... but no no no, that is silly! Enter arguments why it doesn’t make sense for operators and manufacturers.

In life, it is those that figure out solutions, not problems that we appreciate. So, i understand it is more helpful to discuss real world solutions. I don’t really want to get into arguments with people about camera designs that exist. We know they exist for a reason, and they help us solve many image capture challenges. I am simply seeing if other people share the desire for professional small cameras. And it seems like a very solid NO. Everytime i ask, since before the 1DC was introduced, until now, the answer is always NO.
 
Last edited:
Despite the near unanimous disapproval, i keep bringing it up because forums read like this:

Yes we want better i/o ports on mirrorless cameras. NO we don’t want anything to exist that would solve that.

Yes mirrorless camera buttons and ports are small. NO we don’t want it bigger. But we’ll add a gimbal or cage.

Yes we like ergonomics and weather proofing. NO we don’t want any solutions that don’t already exist.

Yes we like shooting on smaller camera bodies. NO we don’t want smaller camera bodies, we have Fs7’s

Yes we love cages and building out our cameras. No we don’t want to have an option that is slightly bigger with 1/4-20 holes in addition to the ones we have.

Yes we could use a dslr the same way we use a brain box. No we don’t want a dslr with pro i/o ports we want a brain box

Yes we love having a small body mirroless and a larger Fs7 body. No we don’t want a larger dslr sized body with i/o ports and a mirrorless body companion with similar workflow and same sensor.

Yes i want to be able to pack small and light. No i’d never use a larger dslr sized body with more A cam features and a smaller mirrorless body together.

And on and on, with many such contradictions tha
 
In life, it is those that figure out solutions, not problems that we appreciate. So, i understand it is more helpful to discuss real world solutions. I don’t really want to get into arguments with people about camera designs that exist. We know they exist for a reason, and they help us solve many image capture challenges. I am simply seeing if other people share the desire for professional small cameras. And it seems like a very solid NO. Everytime i ask, since before the 1DC was introduced, until now, the answer is always NO.

Not for me. And maybe it's not the camera people imagine using. But it could very well be the camera they DO end up using. I think it's worth it for manufacturers to take a chance and just maybe hit a home run. What's the point of all fighting for space in the same lane, when there is a whole lane not even being used. Build it and they will come.
 
Just checked it out briefly. Impressed. Can't believe we've got this for $1699... in many ways it's an S35 version of the Lumix S1H for less than the GH5 launched for.

Glad to see IBIS and 4k60p 10-bit becoming standard, even at sub $2k.
 
I get your take on it but to me, editing H.264 and H.265 is akin to driving down the freeway with a boat anchor dragging behind your car. You might achieve the speed limit but you're going to tear up a lot of asphalt along the way.
Several video engineers, compression experts at the studios and even Adam Wilt impressed upon me more than a decade ago the computational differences between Long GOP (Interframe) and Intraframe compression schemes and what kinds and amounts of
resources each sucks from your system.

Advances in computing/graphic processing power have a way of obliterating these hurdles. Interframe was a BIG, BIG deal for awhile until computers could easily handle it without sweating. H.264 was god awful sluggish until they wrote specific decompression routines for processors (and software that could take advantage of it). Now on a modern computer, editing H.264 C200 footage is very responsive. The same will happen with H.265. Now it's a bit painful. But specialized decompression chips and routines are coming online quickly. I suspect in a year or so, it's not going to be that big of deal. The nice thing about H.265 is that it is a universal format so there is great interest in designing computers to process it efficiently.

It's always balancing storage space/cost, verses processing load, verses transcoding time. Sometimes it's native H.264/H.265. Sometimes it's RAW. Sometimes it's transcoding/proxy.
 
Advances in computing/graphic processing power have a way of obliterating these hurdles. Interframe was a BIG, BIG deal for awhile until computers could easily handle it without sweating. H.264 was god awful sluggish until they wrote specific decompression routines for processors (and software that could take advantage of it). Now on a modern computer, editing H.264 C200 footage is very responsive. The same will happen with H.265. Now it's a bit painful. But specialized decompression chips and routines are coming online quickly. I suspect in a year or so, it's not going to be that big of deal. The nice thing about H.265 is that it is a universal format so there is great interest in designing computers to process it efficiently.

It's always balancing storage space/cost, verses processing load, verses transcoding time. Sometimes it's native H.264/H.265. Sometimes it's RAW. Sometimes it's transcoding/proxy.

Very timely, I just wrote a blog entry about dealing with HEVC/H.265 footage in professional workflows. https://www.hdvideopro.com/blog/dealing-with-hevc-h-265-footage/
 
Last edited:
  • Like
Reactions: dpc
Back
Top