Fuji X-T3 released

I find it useful to experiment with all top NLEs to see what they can/cannot do. Currently use PP CC, and occasionally FCPX, and Resolve. The only major issue with FCPX (other than limited built-in color/tuning options relative to PP CC & Resolve) is it only runs on OSX. My most powerful hardware is a Win10 PC 10 Core + GTX 1080 + NVMe + 64GB RAM: was going to set up as a Hackintosh- however one needs very specific hardware (was not top of the line when I built machine from choice parts), so made Win10 only. Plus Hackintosh won't be as stable as native Mac hardware or running Win10. I'll test X-T3 4K 10-bit H.265 footage on the Win10 box when I have free time (I figure it will play back in real time in 4K full res).

PP CC and Resolve keep getting better and better, as does FCPX (perhaps at a bit slower rate), so it's good all around for editors!
 
Tested X-T3 4K50 & 4K60 H.265 10-bit in PP CC and Resolve 15 on the Win10 box (10-core, NVMe drive, GTX 1080, 64GB RAM) used 35-40% CPU and around 20% GPU- playing real-time though not scrubbing like H.264 ALL-I / ProRes / Cineform. I ran both PP CC and Resolve at the same time and it hit 100% CPU and playback was choppy though sound was still smooth. Lumetri / major color node adjustments along with cross fades (playing two clips at once) was very smooth and usable. 4K24 & 4K25 will of course be less taxing on the system.

You can download original SOOC clips I tested here (not my work):

10-bit 4K 50p H.265:

10-bit 4K 60p H.265:

FCPX, PP CC, and Resolve all support proxy editing, so those without a fast machine shouldn't have to transcode. If transcoding I'd use QuickTime with Cineform (wavelet): at least 2x smaller file sizes with better quality vs. ProRes and DNxHx.
 
On my MBP mid 2015 (High Sierra 10.13.6 and FCPX 10.4.4) HEVC 4K struggles. Strangely It struggles with optimised media as well, unless I switch to better performance. But then I can't see critical focus
More strangely if I open the optimized media out of FCPX (in QT), they play much decently.
H264 play perfectly, but then it's a lower quality camera..
Starting to think I'll send back the Shinobi and buy a Ninja V instead.
 
With the recent Adobe Creative Cloud update that specifically optimised 10bit H.265 decoding/encoding, editing H.265/HEVC files from X-T3 are now a lot smoother in Premiere Pro (13.1).
 
Last edited:
jcs said:
Tested X-T3 4K50 & 4K60 H.265 10-bit in PP CC and Resolve 15 on the Win10 box (10-core, NVMe drive, GTX 1080, 64GB RAM) used 35-40% CPU and around 20% GPU- playing real-time though not scrubbing like H.264 ALL-I / ProRes / Cineform. I ran both PP CC and Resolve at the same time and it hit 100% CPU and playback was choppy though sound was still smooth. Lumetri / major color node adjustments along with cross fades (playing two clips at once) was very smooth and usable. 4K24 & 4K25 will of course be less taxing on the system.

You can download original SOOC clips I tested here (not my work):


FCPX, PP CC, and Resolve all support proxy editing, so those without a fast machine shouldn't have to transcode. If transcoding I'd use QuickTime with Cineform (wavelet): at least 2x smaller file sizes with better quality vs. ProRes and DNxHx.
Click to expand...

Which version of Premiere did you test with? The version that was released a couple of days ago supposedly has h265 optimizations, but I haven't had a chance to test myself yet.

EDIT: Marvin beat me to it.
 
Fahnon said:
Which version of Premiere did you test with? The version that was released a couple of days ago supposedly has h265 optimizations, but I haven't had a chance to test myself yet.

EDIT: Marvin beat me to it.
Click to expand...

Older/slow build:
PPCCXT3.jpg


This was captured with OBS Studio, compressing a 4K stream to H.264 during playback- more cycles to spare.
 
marvinhello said:
With the recent Adobe Creative Cloud update that specifically optimised 10bit H.265 decoding/encoding, editing H.265/HEVC files from X-T3 are now a lot smoother in Premiere Pro (13.1).
Click to expand...
That is good to hear!
 
Tested PP CC 13.0.1 (Build 193) with same project: on 24p (from 50p; car footage), uses 10% GPU and just a few percent less CPU yet is a bit 'spikey' in playback. Not quite stuttery, but not very smooth (as with an ALL-I codec like ProRes, Cineform etc.). 50p at 50p spikes to 100% CPU now and doesn't appear to play as smooth as the prior build I just tested.

It would be in Adobe's best interest to hire game developers with real-time rendering performance architecture*. With each release of PP CC, it can speed up or slow down after so-called "performance improvements". This is typically from limited testing and/or basic architecture design deficiencies. I spent over $5K building a "4K" rendering box when my more-than fast enough MacPro couldn't play 4K footage after a PP CC update (actually a downdate haha. Recent builds play 4K OK again). Adobe really needs to do an "FCP => FCPX" and do a from scratch rewrite using modern architecture and code patterns: the PP CC codebase is an ancient mess (look at the SDK examples!). Have much empathy for the developers who have to deal with it!

That's one thing I can say for FCPX- I haven't seen decreases in performance with updates. Resolve has had some hiccups, however Resolve 15 is easily handling these files on this Win10 box.

* understand their challenge- game developers have more fun working on games and new/clean code!

EDIT free tip for Resolve and PP CC developers (hey you never now they could be here lurking on their lunch break lol): you can do simple linear interpolation of audio to prevent that annoying audio clicking, even Windowed Sinc interpolation is relatively cheap to compute now. Or just keep the audio hardware buffers properly fed and in a thread so it's never starved (+ treat audio as master clock) and drop video frames to keep up! PP CC has similar problems with audio/video playback and sync (IPB decode buffering isn't an excuse). Really surprised after all these years these apps have relatively trivial bugs and performance problems that are EASY to fix haha.
 
Last edited:
Didn't see such bad things in the first couple of weeks. Used it with Sigma 18-35, (latest) 50-150, Canon 70-200 mkII and Leica Summicron
 
marvinhello said:
Major firmware update V3.0 for X-T3 released:

Can someone please help me? For the life of me, my cam is not recognizing the update. Camera says no update found in slot one. Is anyone else having this problem, or does anyone have a clue as to what I may be doing wrong?
Click to expand...
 
Ok Never mind I found the problem. My browser had altered the name in case any one runs into the same problem.
 
reem12 said:
Ok Never mind I found the problem. My browser had altered the name in case any one runs into the same problem.
Click to expand...

Guessing you are on a Mac or that you already have one of the older updates on your computer and the browser added a (1) to the end. The updates are always the same file name, makes storing versions difficult.
 
You must log in or register to reply here.
Back
Top