Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Best Card for CS5 with a MAC

...and ALL of the formats you mention work like a dream in Premiere on a PC, so, except for the lack of real time, I don't see what your problem with colorista is? You have to have Premiere 5.0.2 installed, and run all the appropriate versions, 64 bits, etc, of all installed softwares. I don't use Matrox, but as far as I know, they do support CS5, that's what a production house down the road uses day in and day out. And in general, I wish people refrained from making such categoric, sweeping comments as "best to stay away from this or that"...
 
Nope I am the engineering manager for MediaCore (core video formats), dynamiclink and Adobe Media Encoder...
Haha do I talk you about AE CS5 inability to render to QT files over 2GB? LOL! Its a pain in the @$$ I tell yaa!!!
 
Haha do I talk you about AE CS5 inability to render to QT files over 2GB? LOL! Its a pain in the @$$ I tell yaa!!!

Sure that is a bug in my court and it makes me very grumpy. Apple told us to use new api's if we want to get multipass encoding to work. Those new api's don't work on network volumes greater than 2gig. There aren't many people at apple that we can work with anymore on this bug. We have a RADAR bug open on this at apple and are doing our best to escalate it with them to get them to fix this issue. I have worked on QT support at Adobe for 10 years now and do my best to make sure it works well but this one is out of my hands.

Cheers

Dave
 
Sure that is a bug in my court and it makes me very grumpy. Apple told us to use new api's if we want to get multipass encoding to work. Those new api's don't work on network volumes greater than 2gig. There aren't many people at apple that we can work with anymore on this bug. We have a RADAR bug open on this at apple and are doing our best to escalate it with them to get them to fix this issue. I have worked on QT support at Adobe for 10 years now and do my best to make sure it works well but this one is out of my hands.

Cheers

Dave
Man you made my year ;) At this point were going back and forth from CS4 to CS5 due to this bug. But your replying takes the coals from the Apple/Adobe stocking ;)
Thanks!!
 
Agenda or Reason?

Agenda or Reason?

Sure that is a bug in my court and it makes me very grumpy. Apple told us to use new api's if we want to get multipass encoding to work. Those new api's don't work on network volumes greater than 2gig. There aren't many people at apple that we can work with anymore on this bug. We have a RADAR bug open on this at apple and are doing our best to escalate it with them to get them to fix this issue. I have worked on QT support at Adobe for 10 years now and do my best to make sure it works well but this one is out of my hands.

Cheers

Dave

Does Apple have an agenda or do they have a Racional reason as to why request adobe to cripple their own software?.
David do you care to Comment?
 
Does Apple have an agenda or do they have a Racional reason as to why request adobe to cripple their own software?.
David do you care to Comment?

It is just a bug in their code... They now know about the bug and we are hoping they are fixing it. No agenda as far as I know but there aren't many fixes going into QuickTime now. QuickTime X isn't anything a developer can use and there is no news on where they are heading with it.

Cheers

Dave
 
It is just a bug in their code... They now know about the bug and we are hoping they are fixing it. No agenda as far as I know but there aren't many fixes going into QuickTime now. QuickTime X isn't anything a developer can use and there is no news on where they are heading with it.

Cheers

Dave

That's a bit of a surprise to me... the bad kind of surprise..

I thought that Quicktime X was something developers could use... but that it wasn't popular because of immaturity.

One thing I was curious about... why develop Mercury?

I thought that both Windows and OS X had api's based on OpenCL (actually OpenCL on OS X and DirectCompute on Windows) suited to GPU accelerated applications. Why don't those API's work for Adobe?

Another question, will Mercury support ATI/AMD graphics offerings anytime soon?
 
That's a bit of a surprise to me... the bad kind of surprise..

I thought that Quicktime X was something developers could use... but that it wasn't popular because of immaturity.

One thing I was curious about... why develop Mercury?

I thought that both Windows and OS X had api's based on OpenCL (actually OpenCL on OS X and DirectCompute on Windows) suited to GPU accelerated applications. Why don't those API's work for Adobe?

Another question, will Mercury support ATI/AMD graphics offerings anytime soon?

QuickTime X is pure marketing at this point. It is playback only of basically h.264 and a few other codecs. It doesn't support 90% of the calls we need from Quicktime. Plus if you try and use it for anything other than raw single file playback you fall back to legacy quicktime.

As for why we developed Mercury... Its because it Rocks! :hurray:

In all seriousness... Mercury is the name we use for a ton of performance features in the latest version of ppro. Part of that is using Cuda for video acceleration. OpenCL is very comparable to Cuda but not yet mature. At this point some cards are starting to show up that have drivers that might support what we need. However, it isn't yet proven for the features we use. We continue to investigate this.

Cheers

Dave
 
Hi Rudi thanks for your comments, l forgot to mention l only have Macs, always had slight issues with PCs, take your point about colorista II, if its anything complex l can always send it to AE just like an easy life lol, but maybe Colorista II will become better in PPro with updates.

My Mac Pro is new re June, Quad Core 2.26 2 8 processors Memory 16GB and running Nvidia GeForce GTX 285 at 64 Bit, this was the best card at the time, is there anything more l should be thinking about or doing, apart from a PC lol
 
Hi David. Colorista working great now with PPro 5.0.3 update.
 
Matrox MXO2

Matrox MXO2

Matrox: well.....whatever solution you are working with for monitoring with RAW....the only way i know that you can get 10bit depth now (if not using Rocket Card or other expensive card with HDSDI out) is to go display out if your mac has that. My tower does not, but my notebook does. But, not sure if you get 10bit out of PPro or FCP do you?

....but of course 10 or 12 bit monitoring is best route all the way through the pipeline, but what you should take advantage of is your final output and i'd say that is where Matrox comes in really handy.

....Now you have completed your cut/grade and outputted to ? i dont know, but Prores? then you can do your final review and color work there in FCP/Color and view 10bit within MATROX. Works for me and i really like it.
My cents
 
Johnny, Andrew

I don't use MACS, I'm all PC. Way back when I started messing with HD footage, the only app that supported those frame sizes was Premiere, so I went that way and never looked back. It was a bumpy road but I learned from all the limitations, patience most of all :-) and now we're at a point finally where Adobe/PC is probably, without putting any other system/Os down, the easiest, quickest, fastest, cheapest solution for most cases. That said, I use dual Quadro FX 3800 cards on my PC's and they run like a dream. The 3800 is still not MAC ready, which is a shame, since you can buy a pair for under $1600 and I get about 80% of the performance I get from the Rocket out of them.
 
Back
Top