[Dennis Radeke]

[David Cherniack] “But Pr CS4 was not Adobe’s, or their third parties, finest hour.”

I agree. The reason (if anyone cares) is that we were beginning to make large architectural changes. In CS4, we changed the project file from codecs being related to the project to codecs being related to a particular sequence. In addition, we went 64-bit optimized (not native) and to top it off, we let the 3rd party hardware people certify their own drivers for CS4. The last one was a particularly a bad move…

Anyway, if someone has a choice between using CS4 or CS5.5 trial, I would totally point them to the native 64-bit to get a fair evaluation.

Dennis

[Dennis Radeke]

If you need serious GPU power (same argument for MacPros) then you can add it via an expansion chassis.

I also think some people put to much emphasis on the GPU in an editing system. If you rely solely on GPU to solve editorial and compositing tasks, you’ve simply moved the problem from the CPU to the GPU. The key is to use both in balance.

Finally, who’s to say you can’t gang a bunch of ‘okay’ GPU’s together as well? Adobe has been asked for multiple GPU enablement for CUDA since CS5 was released. With PremierePro 5.52 we’re taking a first tiny step with Maximus (Quadro + Tesla) for more GPU power.

Again, it’s the idea that the market size might not be large enough for a company like Apple to support with a traditional tower. Besides, Steve always said not to be afraid to obsolesce yourself. Reading the book like everyone else and find it fascinating. I think the multiple mini concept would make sense for Apple and for a larger addressable market including some editorial and rendering type jobs.

[Dennis Radeke]

[Jeremy Garchow] “PPro needs a little more tweaking in my opinion, but Adobe seems to be pretty serious about making PPro even more of a contender than it is now. Adobe has made some pretty interesting moves in the recent months.”

Thank you Jeremy. I think at a basic level, we’re listening to our customers and then delivering as much of it as we can. We’ve got lots of good things coming down the road and I personally can’t wait to start showing the community.

Dennis – Adobe guy

[Dennis Radeke]

While I’d like to see a new MacTower, my growing conviction is that it’s over. Less than 30% of all CPU sales are desktop. Jobs said you should be afraid to obsolete yourself and the shrinking revenue from MacPro’s all but guarantees that there will not be anything like it.

https://www.macobserver.com/tmo/article/why_the_mac_pro_wont_last/

I hope I’m wrong but I think your idea while interesting is pure fantasy in the minds of Apple engineers.

I wonder if you can use thunderbolt to share CPUs in which case taking 2-3 mini’s and putting them in a 1U rack might be a more likely.

[Dennis Radeke]

[Walter Soyka] “Ideally, I’d like to see both Apple and Adobe adopt OpenFX, which is an open standard for plugin development. I am not holding my breath, though.”

I’d never heard of this before but went to openfx.org and checked it out. Currently it seems that the environment is Win32 only. It’s not 64-bit and it’s not cross platform, so for your safety, please DO NOT hold your breath!

[Dennis Radeke]

Hi David,

I won’t try and justify this, other than to say that I know it’s a complicated issue for Adobe. In the end, we try our very best to provide the right options for all of our potential customers, but you’re proof that it’s not perfect.

As someone suggested, call videoguys.com. THey’re in my patch (New York) and be sure to tell them Dennis sent you. If you have a problem, ask for Gary or Rich. If they have a problem, they have my number and they should call me. My guess is that they won’t have any problems.

Post here as well if you don’t get what you need. My apologies and I hope we can get you set up.

Dennis – Adobe guy

[Dennis Radeke]

Thanks Joe.

I think one of the key ideas about Story is that it’s not necessarily about writing the script in Story. The value is in the rich metadata the story you write represents…

What I mean is that you should continue to write in Word and then import it into Story and have all of that data move directly to the clips and the actual production. While we strive to make the creation of scripts easier and more powerful in Story, I think our primary goal is connecting the script to the media in a new and powerful way.

2 cents, maybe 3…
Dennis

[Dennis Radeke]

[Joseph W. Bourke] “I worked and played with the early versions of Story, and, at the time, gave up on it temporarily because it wouldn’t import Word documents in column form, which is how I write my scripts (most of my clients – industrials – work in Word as well).”

Hey Joe,

I am not a script writer (so proclaim my ignorance!) but I know we’ve done a substantial amount of work on multi-columns and the import formatting. When you’re ready, I hope you’ll give it another peek.

Dennis – Adobe guy

[Dennis Radeke]

Truth be told, we both had slots that night I believe, but Avid did indeed have the bigger exposure for that night…

Dennis – Adobe guy

[Dennis Radeke]

[Craig Seeman] “I think you’re making an assumption that the current state is the final state. FCPXML is just a first step. It’ll get there.”

You’re making an assumption too.