Fuji X-T3 released

puredrifting said:
16mm F1.4 is a killer
The "kit" lens 18-55 F2.8-4.0 OIS seems to be pretty good.
The new 200mm F2.0 looks amazing and comes with a 1.4 teleconvertor but it is $6k
I'm going to probably pick up the 10-24 F4 OIS for gimbal

I'll be buying an EF to X Mount adaptor so I can use my Canon 70-200 2.8 IS II with it.

Like with every camera, depends on what you are shooting and how you want to shoot it.
Click to expand...

Nice! I got the kit lens with the grip. Looking for lenses now and a zhiyun crane 2 :)
 
strancali said:
Nice! I got the kit lens with the grip. Looking for lenses now and a zhiyun crane 2 :)
Click to expand...

That's what I was thinking, the Ronin S is too heavy and overkill for the XT-3 IMHO. Crane 2 seems smarter.
Unfortunately found out that my current lucrative gig will probably end in December so I'll have to save money
for what are typically the slowest months in my year, Jan-Mar.
X-T3 and lenses may have to wait until another lucrative gig shows up :-(

Thats the thing, I really WANT the X-T3 but I don't really NEED it. It will mainly be used for gimbal (I have my iPhone 8 Plus and an 80D) and as my stock footage gathering machine (the C200 suffices, it's just kind of big and obtrusive and not a stills camera so have to haul the 80D around too for stills. Gets bulky). But as far as paying production clients, the X-T3 is not really needed to generate income and stock is an ongoing project.
 
I may be ordering the X-T3 in a day or two. Instead of Ronin S or Crane I'm liking what I see of the Weebill Lab. More than anything I'd like to know how they came up with the name.
 
It is nice, cameras are all of similar quality now. Reminds me of when camera bodies were different, but film was all similar. Purchases can be about branding or budget again. No longer have to buy XYZ.
 
Definitely. At least four brands (BM, Fuji, Panasonic, Sony) have super nice <$3k offerings right now. And Canon has nice higher-end stuff and Canon and Nikon DSLRs are not bad at all either if you're forced to use them for some reason.
 
Picked up an X-T3 last week along with lightly used 18-55mm and a 50-140mm. Very impressed with a lot of it. Feelings echo what has been stated already. Stepped Iris is a disappointment but can be worked around. The in lens OIS is sufficient in my view for handheld work.

Been upgrading my FFMpeg on my system to deal with H.265 (HEVC) files. At the point where I can verify it works in converting H.265 to ersatz ProRes files. Here is a generic commandline example to get ProRes 422 LE...

Code: 
ffmpeg -i input.mov -c:v prores_ks -profile:v 3 -pix_fmt yuv422p10le -c:a pcm_s16le -b:a 48000 output.mov

where it says "input_file", you place your filename to process and with the "output_file" you name what you want your output file. If you have an FFMpeg front end all setup already, all you should have to do is upgrade your version of FFMpeg to the most current available.

Here is the version I am using. Was fetched from the GIT repository for FFMpeg...

Code: 
$ ffmpeg -version
ffmpeg version N-86776-g0ef8f03133 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 5.4.0 (GCC)
configuration:
libavutil      55. 67.100 / 55. 67.100
libavcodec     57.100.104 / 57.100.104
libavformat    57. 75.100 / 57. 75.100
libavdevice    57.  7.100 / 57.  7.100
libavfilter     6. 95.100 /  6. 95.100
libswscale      4.  7.101 /  4.  7.101
libswresample   2.  8.100 /  2.  8.100

Oh my goodness, this camera is sooo much easier to use than the Sony a7 series cameras.
 
Last edited:
Andrew Stone said:
Picked up an X-T3 last week along with lightly used 18-55mm and a 50-140mm. Very impressed with a lot of it. Feelings echo what has been stated already. Stepped Iris is a disappointment but can be worked around. The in lens OIS is sufficient in my view for handheld work.

Been upgrading my FFMpeg on my system to deal with H.265 (HEVC) files. At the point where I can verify it works in converting H.265 to ersatz ProRes files. Here is a generic commandline example to get ProRes 422 LE...

Code: 
ffmpeg -i input_file -c:v prores_ks -profile:v 2 -c:a copy output_file

where it says "input_file", you place your filename to process and with the "output_file" you name what you want your output file. If you have an FFMpeg front end all setup already, all you should have to do is upgrade your version of FFMpeg to the most current available.

Here is the version I am using. Was fetched from the GIT repository for FFMpeg...

Code: 
$ ffmpeg -version
ffmpeg version N-86776-g0ef8f03133 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 5.4.0 (GCC)
configuration:
libavutil      55. 67.100 / 55. 67.100
libavcodec     57.100.104 / 57.100.104
libavformat    57. 75.100 / 57. 75.100
libavdevice    57.  7.100 / 57.  7.100
libavfilter     6. 95.100 /  6. 95.100
libswscale      4.  7.101 /  4.  7.101
libswresample   2.  8.100 /  2.  8.100

Oh my goodness, this camera is sooo much easier to use than the Sony a7 series cameras.
Click to expand...

Sweet.

Is there some kind of batch option for FFMPEG?
 
mcgeedigital said:
Is there some kind of batch option for FFMPEG?
Click to expand...

Sure, use this instead... It assumes two things, first the FFMPEG executable is in the same folder as the movies you want to convert, and you've made a sub-folder called "converted" in that same directory... It will convert ANYTHING (not just .h265) that FFMPEG can read into that flavor of ProRes.

for %%a in ("*.*") do ffmpeg -i "%%a" -c:v prores_ks -profile:v 2 -c:a copy "converted\%%~na.mov"
 
Hi Matt,

reposting the FFMpeg Commandline entry. I did not add audio to the orginal one.

Right now I am trying to piece together one of the "highly recommended" FFMpeg Frontends to the base application of FFMpeg but it is a real cludge. This is for Windows. I won't post anything further on it, till I get it sussed or I try another OpenSource solution that works well and is easy to operate. Not sure when that will be complete but it is a priority.
 
No, you want to keep the order of operations I've laid out, else it won't work you need to "batch" before calling FFMPEG, not the way you have it. My script just copies over the audio in the same format it was recorded in, whatever that happens to be. If that audio format then reads in whatever NLE you're using, well, no need to convert, just enjoy that it's a lossless copy. Come to think of it, I'd strip that "_ks" out of the ProRes option in case of compatibility if you run into issues playing them anywhere, it won't compress the file as much (downside) but it will transcode faster I guess...

For those interested, ProRes options in FFMPEG...

-profile:v 1 is LT (icky, icky LT... bleah!!)
-profile:v 2 is Normal 422
-profile:v 3 is HQ 422
-profile:v 4 is 4:4:4

Never touched Unix in my life, all Windows. I do test the scripts before posting it to make sure they work and batch correctly. ... I'd only add a couple things to it, first the option for the number of threads in this case I just set it to 8 (maybe you don't want all 64 of your Threadripper threads working on it at once, swamping your system :) ) and a pause a the end so the command line doesn't go away after finishing so something like this...

for %%a in ("*.*") do ffmpeg -i "%%a" -threads 8 -c:v prores -profile:v 3 -c:a copy "converted\%%~na.mov"

pause

If someone wants to put a couple small camera orginal files up somewhere for me to look at, or tell me where to find them, I'd be glad to dial this in even more if needed...
 
Apologize Jim. I removed my question to you hoping that it had not been seen, as I had tried it out in Cygwin, the Unix shell for Windows. It did not work. Regardless, your post still makes sense even without the reference to my question, which effectively was will your script work in UNIX.

I'm going to do some research on batch processing in UNIX in a few hours to see if I can work this out for those who are working in that environment. Thanks for your efforts!
 
Yeah no worries, I'm sure someone else will come along with even tighter, better scripting for this, but I'll take the bullet. After all, I dropped my original Computer Science degree path and got a BS in Communications, so what do I know?

Truthfully, it's just testing and reading up on what you want to do, every case with every permutation is out there on the 'net, it's just stringing things together so they work.

I'm not subscribed to this thread, as I'm not directly interested in this camera, but wanted to help when I saw the batching question...
 
My final update... I checked a bunch of Odyssey created ProRes files and they seem to have PCM audio tracks, so assuming that's the norm for ProRes, this will convert the incoming audio, whatever it is, into "lossless" PCM audio.

for %%a in ("*.*") do ffmpeg -i "%%a" -threads 16 -c:v prores -profile:v 3 -acodec pcm_f32le "converted\%%~na.mov"

pause
 
Hi guys,

since there is no fuji forum, I will ask here. Hope it is ok.

Is there anyone who have X-T3 and could share some answers? I have seen some footage and I am impressed. I could easily buy two bodies with lenses and batteries for same amount of money which could cost me for example C200. I will have project for 2 cameras soon so I am looking for options. X-T3 looks great.

But I have no experience with Fuji. I have seen couple reviews but no reviewer is talking about quirks. And every camera has some. So, the question is, from video shooters standpoint, what are the quirks?

- recording limit?
- crop? (Relative to apsc)
- audio handling?
- battery life with grip
- is flog ready?
- Do you need V90 cards?

Thank you
 
You must log in or register to reply here.
Back
Top