Jon Grimson
Forum Replies Created
-
Have been doing it on their forum since yesterday, that’s their customer service interface.
https://forum.matrox.com/mxo/viewtopic.php?p=22915#22915
-
I have the latest Matrox drivers. No way to activate external monitoring in PP that I can see. So I’m stuck not being able to eval CS5.5 until I can run my external monitor via the MX02LE.
-
Exact same problem for me Shane. I’m testing CS5.5 demo since I (like many) will need to bail on FCP. Can’t even see where to select external monitoring; nothing showing up in PP preferences that I can find.
Running MBP 2.8Ghz Intel Core 2 Duo, 8G memory, OSX 10.6.7, demoing CS5.5
I’m trying CS 5.5 demo from FCP7 and can’t get a signal via MXO2 LE to drive my external monitor. Running 2.2.3.0043 firmware 31.1 on the LE.
CS5.5 is running and passing audio but I seem to have no ability to external monitor. Any help please?
-
I’ve also found that re-setting QMaster can solve some of these weird problems. If you’ve been running projects through Compressor, you may try this. My issue was resolved when I figured out that I had to change my toolbar location from 2nd monitor to laptop screen. So I think my problem could have been related to video memory issues. Make sure graphics is optimized for performance rather than battery life in Energy settings system preferences.
Hope this helps!
-
Shane, just checking on this response to verify a spot I’m shooting in a few weeks. I intend to shoot 90% of the footage in 1080p23.98 on a Canon 7D system, but one shot will be done 720p60, retimed ala optical flow in Motion and conformed to 23.98 in cinema tools.
My main question is when I resize that from 720 to 1080, I’m blowing it up, and I’m concerned it will look like crap blown up ~66%.
You mention that you’ve done this (I think) and it looks great. Just wondering about that or is my math funky on this.
The other thing is this is a Golf Channel spot but I still am awaiting deliverable info for master. Still primarily going with a 1080p23.98 acquisition though.
Thanks Shane!
-
It is actually 60 min. of content but is broken down into 7 parts. Are you asking because compressor is faster/slower than rendering out in FCP?
-
Just wanted to report back that I believe there is definitely a bug in how fcp handles 2nd monitor display when it is disconnect and reconnected in a laptop setup. Those of you with 2nd monitor display running FCP workspace (not as broadcast reference via 3rd party hardware), would likely never notice. But people running FCP from laptops who then need to disconnect and go mobile will likely NOT be able to restart FCP at all, until they return to office, reconnect to 2nd display and manually move desk spaces around. I just tested this and now I can edit via laptop only, provided that I saved last in FCP when I had manual re-arranged desktop to single monitor, and saved.
Why is this critical? Try going to a client meeting and having that meeting end instantly when FCP won’t launch. Makes me nervous to try it again but I think manually rearranging to laptop screen and saving FCP, then making monitor disconnect will solve it.
Thanks everybody!
-
Something strange is happening and it seems to be related to my second monitor display. When I edit from my office I have a 2nd display attached and FCP works just fine. When I take my laptop to a client and try and run FCP on just the laptop single display I have all these crashes. FCP ran perfectly fine before I had the 2nd display, but I believe something is happening that is causing it to crash when I take the laptop on the road and use in single display mode after having been used in dual display mode. Could this be the problem somehow? Has this ever happened to anyone else?
All I can say is is it works with 2nd monitor setup and crashes when I go laptop only. Maybe it solves the problem but not the dilemma.
-
That’s not it I have a new upgrade version of FCP Studio and I’m the only one with a license. But I tried disconnecting anyway and still no luck.
FCP seems to crash while it’s attempting to RT profile. I’ve tried it on an attached project and media drive as well as setup a dummy test directly to my internal drive, so I think it is safe to say that it is not a drive issue.
Really not liking how I can’t fix this but appreciate all the help from you folks. Please keep it coming…
-
I guess my assumption would be that if this is a memory issue, that I’d be having all sorts of problems with the computer and other software in general. As far as I can tell it seems to be FCP specific.