[Bernhard G.]

[Shawn Miller] “worked in different color spaces (in high bit depths)”

HitFilm internally processes at 16bit color precision already.
Problem: at the moment you will only get 8bit out of it when exporting a video;
but it is said (in the forums) that this will be addressed in the near future.

Of course, 100% 32bit float would be fine,
as well as high-end scaling and optical flow for speed changes and de-interlacing…

[Bernhard G.]

Hi!

Really interesting. But why does it have to be once again a server-solution,
for probably at least $ 20.000 I’d guess?

How are the chances for a simple&affordable drag&drop app for OSX?
with a reasonable price in the range of FCP-X?

Best regards,
Bernhard

[Bernhard G.]

Hello Craig,

these benchmarks are one reason for my doubts 🙂
It appears both boards are similar powerful.
(I even consolidated barefeats’ results into a spreadsheet to have a better overview…)

The basic question here is:
Does 680′ minimal better processing power compensate the lack of 1 more GB VRAM ?

And what can we expect from the new OpenCL?

MacPro is Mid2009 8 cores, 16GB.

Thank You!

[Bernhard G.]

🙂

crunch is good.

No, but as far as I understand, planar tracking is a variation of optical flow analysis. Therefor you need no explicit tracking points since the tracker identifies and follows the path of whole pixel clusters instead.

Like optical flow, these planar analysis data could be stored in the media management, e.g. analyzed in the background during import, so you would only have to switch the tracking for a mask to ‘on’, regardless how
many masks you apply to the once analyzed clip 😉

Best regards,
Bernhard

[Bernhard G.]

+1

wished at least Color Corrector’s current masking tools
to be available within EVERY filter and effect in the stack.

and if apple would add splines and planar tracking…
with tracking data stored into the media management…

feature request to Apple … one more time 🙂

[Bernhard G.]

[T. Payton] “If apple would add a few more little icons to the correction: track, b-spline & bezier shape, that would be mighty sweet.”

YES!
+1 from me

And it would be great if the masking tool palette from CC
would be available in ANY Filter and Effect in the stack by default.

Best regards,
Bernhard

[Bernhard G.]

Hello,

I would like to see:

1) using audio-roles for visual organization, aka pseudo-tracks, aka hierarchy locking

2) OpenCL accelerated x264 coding with more than 2, at least 3 coding-passes selectable

3)a) expanding Color Correctors masking tools with Base-Splines and Bezier-Splines

b) integrating a one-button planar tracker that operates in background and stores tracking data within event; just like optical flow analysis is handled right now; so you can turn it on/off in stack
[this function is that essential that it needs to be integrated deeply into FCP-X’ core]

c) now making those masking tools available within ALL filters and effects in the stack

4) more control within the Keyframe-editor

4) Compressor with OpenCL accelerated ultra-highend scaling, de-interlacing, noise reduction

5) Motion making use of Events, so Motion Projects becoming available in FCP-X as Motion-Clips

6) multi-user workflow by professionalizing disk image workaround with rudimentary disk image permissions handling for mounting ‘special’ FCP-X disk images according to the scheme:
Write Exklusive / Read Write / Read only

Best regards,
Bernhard

[Bernhard G.]

[Herb Sevush] “Which begs the question “why bother rethinking the process of video editing?””

I think what Apple has addressed with FCP-X is the increasing number of one-man-bands with it’s promise to have 90% of features for 90% of tasks available at the finger tips.

Many folks don’t have the time to learn 20 apps. But with huge and affordable packages it became a matter of course to be skilled in all of it’s apps.

The last 10 years can be characterized as an age of democratization. Features became available by bundling huge software packages, but also were inconsistently distributed among several apps.

IF Apple is right, then the next 10 years will be characterized as an age of consolidation. Features will be re-thought in the context of current market requirements and clustered into apps that fulfill those clusters of requirement. Other good examples for such processes are ClarisseIFX and HitFilm.

Best regards,
Bernhard

[Bernhard G.]

[Craig Seeman] “It may not be the price of the NLE so much as the market it’s currently serving.”

Hello,

I absolutely agree on that! But it’s not only about money, but also about an app’s philosophy:

FCP-X lives from it’s very compact and effective design.

What makes FCP-X so attractive to me is it’s promise
to provide 90% of the tools I need for 90% of my tasks at my finger tips.

While I’m very excited by the new SliceX, as FCP-X user I’d only be comfortable
if such a great and important feature was deeply integrated into the core of FCP-X,
not being ‘just’ a plugin. (Integrated in the kind of the current masking tools inside CC.)

The more plugins I need for everyday tasks, the less attractive FCP-X is to me.

Best regards,
Bernhard

[Bernhard G.]

Since Lion, Apple have added continuously drivers for most actual of-the-shelf
cards, so for the GTX 680. So drivers aren’t the problem!

The only benefit of a dedicated OSX-card is You’ll get a start-up screen;
of-the-shelf cards stay black until desktop appears, due to Mac UFI.

I made good experience with an of-the-shelf EVGA’s GTX570 in a MacPro.

Best regards,
Bernhard