-
New install. Damn it Jim, I’m a Doctor, not a bricklayer!
I’m hoping somebody smart can tell me what’s going wrong with my new install.
Here are the main issues:
–> Code 7 errors while editing a long program (“Open GL does not meet min specs for application”). Before this happens, generally premiere will become unresponsive, program screens will go black and then boom. On this program, I can get about 6 edits in before it blows.
–> Cannot export long program (2+ hours). (Matrox 1080i sequence – footage all P2 DVCPRO HD) Crashes after transcoding approximately 15-20 minutes of program. Exporting to Graid where project and footage is stored (is this an issue?) Premiere crashes and computer restarts. Tried many different export settings, from “match sequence settings” to Premiere’s mpeg2 setting, to the Sorrensen and the Matrox ones.
(Adobe Tech support and a very nice guy named Vinay helped me with a small workaround which involved opening up a hidden admin login, and disabling some Microsoft services and exporting to my spare internal drive)
–> Also tried importing sequence directly into Encore and AME then transcoding through those. No luck there.
–> Premiere Pro on closing gives error message “Premiere Pro has stopped working; appcrash exception code 00005. Also, this is occasionally followed by a Visual C++ runtime error
–> Capture plugins from Matrox are unavailable. No Matrox capture settings are available.
–> No WYSUWYG control panel for MX02 (I know this is an Adobe site, but figured someone might have some insight maybe)
So there’s the beginning. There are more, but these are the biggies at this point.
System details:
Win7 pro
i7 950
Quadro 4000 (with massive cooling blowing on the thing-doesn’t seem to be the issue, but I don’t know how to monitor the GPU temp…so?)
MX02 mini max (because I’m slightly cheap, and yes, I feel a little like a hack plugging RCA cables rather than XLR for audio)
24g ram
Gtech 4tb graid
2 internal SATA drives (one boot, the other for utilities like tone, graphics I use often, etc.)Software:
PremPro (AE, AME, etc) 5.51 (haven’t updated to 5.52 – problem here?)
Squeeze 7
Trapcode pluginsDrivers:
NVidia: 276.14 (this is the Adobe approved one, at least so the download site said)
Matrox: mtxutils_551So here are the main issues:
–> Code 7 errors while editing a long sequence (“Open GL does not meet min specs for application”). Before this happens, generally premiere will become unresponsive, program screens will go black and then boom. On this sequence (matrox 1080i- footage all P2 DVCPRO HD), I can get about 6 edits in before it blows.
–> Cannot export long program (2+ hours). Crashes after transcoding approximately 15-20 minutes of program. Exporting to Graid where project and footage is stored (is this an issue?) Premiere crashes and computer restarts. Tried many different export settings, from “match sequence settings” to Premiere’s mpeg2 setting, to the Sorrensen and the Matrox ones.
(Adobe Tech support and a very nice guy named Vinay helped me with a small workaround which involved opening up an admin login, and disabling some Microsoft services and exporting to my spare internal drive. This is not working for Blue Ray output however.)
–> Also tried importing sequence directly into Encore and AME then transcoding through those. No luck there.
–> Premiere Pro on closing gives error message “Premiere Pro has stopped working; appcrash exception code 00005. Also, this is occasionally followed by a Visual C++ runtime error
–> Capture plugins from Matrox are unavailable. No Matrox capture settings are available. In addition, none of the matrox plugins show up in Encore or AME.
–> No WYSUWYG control panel for MX02 (I know this is an Adobe thread, but figured someone might have some insight maybe)
So there’s the beginning. There are more, but these are the biggies at this point.
Thanks a million. I’m a very busy small shop and sincerely appreciate any other busy people taking the time to give me some input on this. To paraphrase Dr. McCoy, “Damnit Jim! I’m a director, not an engineer!”
Shaunn
-
7 Replies
-
Seriously…is my problem just so ignorant that it’s not worth a comment…OR…it’s already addressed somewhere herein…or it’s so weird and off the chart strange that nobody has any thought whatsoever?
If I’m being stupid, please flame me! I’d love to learn something.
-
If you want to address these problems, that’s what Adobe Tech Support is there for. Its FREE! Ask for Vinay. He is knowledgeable and very laid back.
Installation help and product help
800-833-6687
Monday–Friday, 5am–7pm PSTTom Daigon
Avid DS / PrP / After Effects Editor
http://www.hdshotsandcuts.com
Mac Pro 3,1
8 core
10.6.8
Nvidia Quadro 4000
24 gigs ram
Maxx Digital / Areca 8tb. raid
Kona 3 -
Yup, and I’ve actually spoken to Vinay. Nice guy, however no resolution at all. In fact he was supposed to get back to me and never did. Know they’re busy, but I’ve got projects to churn out. That’s why I’m here bothering you good people. (I’d include a smiley face here but I think they’re trite).
-
Well if they are trite, maybe you would prefer this 😛
Tom Daigon
Avid DS / PrP / After Effects Editor
http://www.hdshotsandcuts.com
Mac Pro 3,1
8 core
10.6.8
Nvidia Quadro 4000
24 gigs ram
Maxx Digital / Areca 8tb. raid
Kona 3 -
First thing I would do is uninstall all things Matrox and see how everything runs in a native Adobe timeline. Do a full uninstall. All the utils and the cards pulled from the box. I was a loyal Matrox user for years (DSLE thru AXIO CS4) and by the end things were so buggy that I just turfed it all when I got a new CUDA card and never looked back.
Taking all that stuff out is a hassle to be sure, but it’s a real quick way to eliminate a bunch of possible causes.
-
Tom…at least you made me laugh in the midst of stress. Thanks!
Paul…Yup. That was the next step here. Thanks for confirming what I’m thinking. It’s irritating, but whataygonna do? The question is – in the absence of the matrox paperweight, what to do about monitoring?
-
Highlight the sequence in the project window. Go to Sequence settings then Playback settings the choose your monitor. This is of course that you have a monitor plugged into your card.
Reply to this Discussion! Login or Sign Up