[Craig Seeman]

[Ryan Welborn] “you need to install it as a quicktime component “

Quicktime component use is deprecated as Apple has moved from Quicktime kit to CoreMedia (AV Foundation).

[Ryan Welborn] “my problem is any option i’m finding is horribly slow!”

and may remain so if you’re looking at Quicktime components. There’s not a lot of market motivation for things such as hardware acceleration for both encode and decode of H.264.

[Craig Seeman]

[Simon Ubsdell] “X’s total sales to date have surely got to exceed sales of all other NLE’s ever produced combined – times a large factor.

Market share within the conventional film and video industries is a whole other matter, surely?”

One might venture that X is a leading NLE in the “non professional” market. Probably well ahead of Vegas there.

Another would be that while X is still a “curiosity” in the “Pro” markets it may well be a “tire kicked” more often than any other single NEL. Each tire kicker is a potential convert, if not now, later.

Unlike Sony, it would seem Apple is much more highly motivated since FCPX use can be a factor in Mac sales and allegiance.

That Apple spent so much development time on changing the library system vs more glossy features, would seem to indicate they are certainly looking at share use situations.

[Craig Seeman]

[Steve Connor] “I would argue that FCPX market share is already considerably higher than Vegas has ever been”

Additionally Apple and third party Professional hardware and software video developers are much more motivated to move into various professional arenas. Even if it’s not immediately “there” yet, the forces pushing it in those directions are incredibly strong and sustained.

[Craig Seeman]

It’s been a while but if memory serves me I did this for a spot delivery using Telestream Episode to Comcast.

[Craig Seeman]

I thought I’d add info from the VideoSpec readme which gives some insight.
As you can see, development has stopped. Note that it uses MediaInfo so using that would be a natural progression. I love Bitrate Pro but Pimley stopped development as a separate app a long time ago. It lived on through VIdeoSpec but given that EOL it’ll be a hunt to replace that. I do have something Mac specific that covers some of that.

Bitrate Pro is a little but very useful application designed by Daniel Pimley (https://www.pimley.net/projects/).
VideoSpec is a GUI (Graphical User Interface) for Open Source Unix tools developed by third parties. VideoSpec simply not exist without these tools:
MediaInfo is a software providing information on multimedia files. Mainly developed for MS Windows, there is however a Mac OS X Command Line Interface (CLI) used in VideoSpec. MediaInfo CLI for Mac OS X is available at this address: https://mediainfo.sourceforge.net. There is also an experimental Mac OS X graphical version. A native Mac version is now available on the App Store.
Mplayer is a multimedia player which can play almost all video formats (https://www.mplayerhq.hu/design7/news.html). The recent GUI Mac OS X version is available here: https://www.mplayerosx.ch/.
FFmpeg is a set of components dedicated to processing multimedia files. The main component is the eponymous tool ffmpeg used from the command line to convert many video formats. Site : https://ffmpeg.mplayerhq.hu/.
Finally, qt_tools is a very handy command line tools suite allowing to handle QuickTime movies. Qt_tools suite is available here : https://www.omino.com/sw/qt_tools/.
AtomicParsley is a command line tool allowing manipulation of MPEG-4 files metadata. AtomicParsley is available here: https://atomicparsley.sourceforge.net/.
Sparkle (https://sparkle.andymatuschak.org/) is used from version 0.9.0 to manage updates.

Known bugs :
Use of decimal separator AND thousand separator will give wrong sizes results with SI (Decimal) setting.

History:
. January 17th 2014 (version 0.9.8): Last update of VideoSpec. Its development is now definitively stopped! MediaInfo CLI (v0.7.66) and ffprobe (N-58857-ge8ac905) tools updated. Several bugs fixed. Bitrate Pro import removed (bug on Mavericks).

[Craig Seeman]

Try MediaInfo
https://mediaarea.net/en/MediaInfo

[Craig Seeman]

I don’t think you can count keystrokes or even “clock” compare specific functions in many cases.

There are people who have significant experience doing similar projects repeatedly with other NLEs who feel they are getting done ahead of deadlines on longer projects.

Short of someone doing the same project twice (and for obvious reasons even if one were to do that, it wouldn’t work as a comparison), doing similar projects on different NLEs can give one person a personal comparison based on their own skill set. One can’t even say it’s “universal” because these examples are limited to an individual’s typical project type (and style).

FWIW I don’t see as many people moving from FCP7 to PremierePro or Avid saying they are significantly faster. Maybe because they are significantly similar and people are only making marginal changes in workflow.

FCPX forces a rethink and, for a time, one may be slower…. until “the lightbulb goes on…” There’s no “lightbulb” for most people switching to the other NLEs because there’s only minor changes in circuitry.

[Craig Seeman]

You could use it but I suspect it’ll break in the next major OS update later this year.
I do think a factor, given how good High Profile CABAC looks now, is the speed difference.
It would seem the difference is there only at very low data rates.

[Craig Seeman]

[Rick Lang] “I never do a single-pass when I have an option for better quality;”

Important to note that Compressor does High Profile CABAC encoding but only in single pass mode.
Note that Jan Ozer says it’s almost (but not quite) as good as x264.

Here, single-pass CABAC encoding was vastly superior to multi-pass CAVLC, and almost (but not quite) as good as x264.

Interesting observations in his Streaming Media review of Compressor 4.1
https://www.streamingmedia.com/Articles/Editorial/Featured-Articles/First-Look-Apple-Compressor-4.1-94026.aspx

[Craig Seeman]

Given Lightworks and EditShare’s potential (and the entire company’s tool sets), I think they may have the wherewithal to be Avid’s “real” competitor. The longer Avid stagnates the more time EditShare has to evolve and stabilize.

Given development resources involved, it may be very smart for them to focus on the things an Avid feature film editor would find important (and not the things they don’t).

A “late to the game” do everything editor may be stuck in “also ran” mode for a very long time with PremierePro and FCPX progressing as well.

On the other hand Avid is a slow motion behemoth beast in a high dollar niche. The NLE storage combination might be sill situated to chase after Avid’s film market.