- Posts: 2
- Thank you received: 0
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Using duel monitors causes footage to appear dark and red.
04 Mar 2013 01:14 #22080
by Jeditor
Hello all,
I am running Final Cut Pro 7 on a Mac Pro 10.7.4.
I am trying to run duel monitors.
I am using Samsung televisions.
I have tried combinations of VGA and mini HDMI outputs.
The images in FCP are playing very dark and red.
If I play the files using QuickTime they look perfect.
I can't figure out why the images are affected only by FCP.
Any thoughts?
Thank you.
I am running Final Cut Pro 7 on a Mac Pro 10.7.4.
I am trying to run duel monitors.
I am using Samsung televisions.
I have tried combinations of VGA and mini HDMI outputs.
The images in FCP are playing very dark and red.
If I play the files using QuickTime they look perfect.
I can't figure out why the images are affected only by FCP.
Any thoughts?
Thank you.
Please Log in to join the conversation.
04 Mar 2013 12:20 #22097
by BenB
Replied by BenB on topic Using duel monitors causes footage to appear dark and red.
How is the television connected?
Please Log in to join the conversation.
04 Mar 2013 17:19 #22115
by Jeditor
Replied by Jeditor on topic Using duel monitors causes footage to appear dark and red.
I have one connected using a VGA and one connected using the provided mini output which I have bought a mini to HDMI connector. I have also tried using both mini outputs to HDMI.
If I only use one output the picture is fine. It is only when I try to use dual monitors does the problem occure.
Also, when I was using (what ever it was called before Lion) it had this problem... then one day, maybe after an update, the problem corrected its self. Now that I have upgraded to Lion I'm back to the original problem.
Thank you!
If I only use one output the picture is fine. It is only when I try to use dual monitors does the problem occure.
Also, when I was using (what ever it was called before Lion) it had this problem... then one day, maybe after an update, the problem corrected its self. Now that I have upgraded to Lion I'm back to the original problem.
Thank you!
Please Log in to join the conversation.

