That sounds like an OpenGL issue. I recommend you turn it off in AE to avoid leaky concurrent resource usage in Premiere. After all, DynamicLink is just an invisible AE that still uses your prefs. Also check your graphics card driver. Installing the latest one may already fix it. If it doesn't, the next logical thing would be to have a look at Premiere's hardware acceleration options, both in the prefs and the preview monitor's own littel flyout menu. It's most definitely a matetr of which combination works, not so much a general failure on eitehr end.
Your advice, as ever, is much appreciated.
Having turned off Open GL, I'm letting the timeline render again, while I also download last week's new Nvidia driver.
As you're obviously very familiar with these programmes, can I ask a broader question?
Am I expecting too much?
I assumed that I could work comfortably between AE and PPro - always only a one way link from from AE, bringing comps onto the timeline for inclusion within a larger production.
But since I've had this CS4 system, the process has been anything but smooth... I'm endlessly looking for workrounds:
> Watching PPro crash when I change an AE comp
> Seeing PPro lock up, unable to conform a new comp
> Seeing "green" Ppro rendered areas turn red again on reboot (scratch discs set same as project)
> Seeing "red" to-be-rendered areas in Ppro turn green if I shut AE.
> Seeing clip content swapped (today's grief).
At the moment I'm trying to work through each specific complaint, whether by myself, here, with Matrox or with Adobe support.
But, yet again, I'm now in the studio at 9.30pm desparately trying to complete anything.
So... should I go back a couple of years to rendering AE clips and importing the renders, or should this system really work?
An honest opinion would be welcomed - good or bad....
Thank you, Linda
I'm not at all that familiar with Premiere, as I use it only for my hobbyist ventures at home (at work we use Avid), but I know how to use it to fill my needs. Anyway, a lot of what you describe may once more boil down to the Matrox card and the associated CoDecs. Other users have reported weird things happening occasionally as well. Since the card hooks into your graphics card resource to establish its capture and preview buffer, it may interfere with other functions. I can't offer any specific advise since I don't have such a card, but back in the day when we were using a Matrox DigiSuite, those things had a priority setting/ slider to balance resource usage. I would look into that and set aside a little more video memory for the video buffer, if possible. This may greatly improve stability. Another way would be to completely disable it, at the cost of possibly losing some realtimeness, then only selectively enable it when you do captures. also investigate, whether Matrox offer updated versions of their CoDecs. The ones you have my simply not be "safe" for a hyperthreading-enabled multicore system, such as you have. Memory leaks in CoDecs are not that uncommon. for more specific questions you should stop by in the premiere forum. The RTX cards seem quite popular, so there's a good chance you can find someone who may better be able to help.
I'm having the same issue, where PrePro is mixing up comps from AE.
Did you ever find a solution?