[Gary Huff]

Working in silence is preferable, do you really want to be talking all the time? Think of how long a typical project takes to edit? Do you want to be talking that ENTIRE time? And what about precision work? Do you always know how long you want to shorten something? You’d end up saying a variation on the same command over and over again while trying things.

A huge pain in the ass.

[Gary Huff]

[John-Michael Seng-Wheeler] I would love to be able to say “render the entire sequence a 20Mbs H.264 file in the project folder”… that would be much faster then any interface could be. (Unless it was ridiculously simplified)

“Please specify encoder complexity.”

“Please specify H.264 level.”

“Please specify quality level.”

“Please specify audio codec.”

“Please specify audio kilohertz”

“Please specify audio bitrate.”

Yeah, quite the timesaver.

[Gary Huff]

[Jeremy Garchow] I do like the MacOS, flame me for not being pro enough, I don’t care. I am not throwing the baby out with the bath water.

I like MacOS too, but statements like these:

And good luck with Windows. Seriously, you might need a little bit of it.

are just ignorant. This isn’t the 90s, you know.

[Gary Huff]

[Sohrab Sandhu] Just think of the infinite possibilities & the speed with which you would be able to work.

I don’t think you’ve thought this idea through very well.

[Gary Huff]

Which is tougher to redo? Your bins or your sequence?

[Gary Huff]

[Jeremy Garchow] Note, this isn’t an fcp7 project, it’s an fcp7 sequence. Big difference.

Not that big of a difference.

[Gary Huff]

https://www.newegg.com/Product/Product.aspx?Item=N82E16819117252

[Gary Huff]

I’ve played around with FCPX, but I haven’t had the downtime to give it a shot with an actual project yet.

I think the real turning point will be when Apple gets their APIs fleshed out and we see some actual plugins start being released, instead of what I’ve seen come out so far (I have no actual use for the plugins I’ve seen so far, even from MB).

[Gary Huff]

[Daniel Frome] On a personal note, I think you’ll soon realize that mac pro workstations are not “screaming fast” machines except when new models are released. The PC world quickly surpasses them in raw CPU power, so think of it as paying for a more stable OS and better engineering of the computer itself (it won’t overheat, make noise, etc).

I work on both Mac and Windows on a regular basis and I’ve just spec’d out my Windows box upgrade path (for $3k) which involves dual i7 Xeons (12 cores in total), 24GB of RAM, SSD drive, and a GTX 580. I made sure that Premiere would take advantage of a dual CPU setup, and I have to say that I’m really anxious to take that step as I’d love to see just how H.264 editing would go with that much raw power thrown at it.

[Gary Huff]

Great list Daniel. Hope Adobe implements all of these (and more!) for CS6.

My spidey-sense is tingling in how good of a release Premiere CS6 might turn into.