Only FIREWIRE for playback on External Display???

Hi,
i'm still work on the setting of Preview on an External Display (TV). FCP only support FIREWIRE but NOT USB??? cause most of my Consumer Device only provide USB port.
No other way to set it up? Is the DVI output an good option (bypass FW device/converter)?
Thanks...really need help

Firewire only if you are working with DV or DVCPRO HD footage...that's it. All other formats require a capture card or external converter. USB is not designed for streaming video.
You can get a DVI converter...that will send a MONITOR signal out, and you can use Digital Cinema Preview, but that will be a low res output. Full res output require the external boxes or capture cards...or firewire if you are working with DV or DVCPRO HD.
Shane's Stock Answer #8: External Monitor Viewing
If you are working with DV, this is simple. First connect your computer to a camera or deck via firewire, Then connect the camera/deck to your TV/Monitor via RCA or S-Video.
Then start up your camera and tv, then open fcp.
Go to the View Menu, choose > External video > all frames
VIEW>Video playback should be Apple firewire NTSC (If you are using an NTSC set)
VIEW>Audio playback should be Audio follows Video
Techinially, this should send synched video to your TV
If for some reason you can't view your timeline on your external monitor, there are a few things to try:
1) Make sure that the camera/deck is connected and powered on BEFORE you open FCP.
2) In the Final Cut Pro menu select AUDIO/VIDEO Preferences and make sure your signal is being sent out thru Firewire DV.
3) Go to the menu and select VIEW>EXTERNAL>ALL FRAMES.
4) Click in the % box above the image and select FIT TO WINDOW.
5) Go to VIEW->refresh A/V devices
6) Make sure the Log & Capture window is closed
If you want it to play in both the canvas and the external monitor you need to go to the FINAL CUT PRO menu and select AUDIO/VIDIO settings and make sure MIRROR ON DESKTOP is selected under the PLAYBACK OUTPUT section.
If you are working with HDV footage, FCP 6 allows you to view this via firewire, but ONLY as downconverted DV. It won't look the best, but you can see it. To do this,
If you need to view any format other than DV at full resolution, then you need to look into capture cards. Several standard definition and high definition models are available from www.aja.com and www.decklink.com. With these options you'll need a proper monitor to view full broadcast colors, but all models allow for realtime standard definition downconvert, allowing you to view HD on an SD monitor.
The Matrox MXO is another option that is output only, but allows you to view your footage on an Apple Cinema Display at full broadcast quality.
Shane

Similar Messages

Incorrect resolutions for 16:10 external displays, unable to detect 16:9

Hey there all, this is my first post here. It looks like some people have had similar issues—particularly with an incomplete/incorrect list of resolutions being provided for external displays.
I am shopping around for an external display for my MacBook (my specs are included) and I tested a few different ones today, but encountered problems.
- On a 22" ASUS monitor (sorry I don't have the model) using Mini-DVI to VGA, the native resolution (I assume 1680x1050) is not available, and most resolutions offered are 4:3 ratio (1600x1200 worked). The highest widescreen resolution listed was 1280x768.
- Next I tried a 19" ASUS, this time 16:9, but the monitor would not display at all. The MacBook display would go blue as normal but then flicker, as if it could not detect the display. This also happened with a 24" BENQ monitor (also 16:9).
Wondering whether or not this was a problem with using VGA, I then bought a Mini-DVI to DVI adapter and tried again on the 19" and 24" (the 22" ASUS did not have a DVI-in) but the same flickering blue screen appeared, with nothing displayed on the monitor.
These were my thoughts:
1. My firmware is not up-to-date. I check in System Profiler and am running Boot ROM Version MB41.00C1.B00 and SMC Version (system): 1.31f0. These are definitely up-to-date for my model MacBook.
2. Drivers are out of date. This does not seem likely as I am running OS X 10.5.7.
Other than that, I am at a loss! I haven't yet forked out the $49 to do phone support with Apple, that will be my next bet.
Has anyone had this problem, or have any ideas what I can try? Short of buying a new Unibody MacBook of course .
Thanks guys, hope you can help. Just let me know if you need more info about my computer.

It's unusual to strike out like that with three different monitors using two different adapters. On the other hand, with all the video issues that have been reported by others on these forums since the 10.5.7 update, it's not too surprising.
Is a 10.5.6 downgrade a possibility for you? For example, do you use Time Machine and can you in that case revert to a previous time when the MB was running 10.5.6? Perhaps that's not a great suggestion, but it would be something to try.
There is some remote chance, though somewhat unlikely given that three different monitors are involved, that the embedded display driver data (EDID) in each monitor is bad or incomplete. If you care to investigate that possibility, there is a program called SwitchRes X that allows you to snoop a monitor's EDID and turns it into a human readable text file.
One final suggestion would be to try yet one more monitor to see if any monitor can return a good result. One obvious choice would be an Apple monitor. If there is trouble when trying to connect to an Apple monitor, then that would certainly point to some problem in the MB's configuration or hardware. And not to cast aspersions on the brands you have already tried, but try another brand (if not Apple) that is perhaps more mainstream and known to be more Mac compatible and less firmly in the PC camp where plug-and-display drivers have never mattered very much and are very often botched by the monitor makers. Dell, Samsung and LG are three big brands that come to mind. Good luck.

Which imacs and apple displays connect to late 2008 aluminum macbook 13 inch for use as external display?

I have a late 2008 13 inch aluminum macbook and want to purchase an iMac computer or apple display to use as an external display for it while I'm at my desk.
I can afford up to $700 for sure, maybe up to $1000 and would like one that has built in camera and audio if possible.
I'd like to know what my options are as it seems not all are compatible.
I'll mostly be doing web browsing and photo editing in Aperture.
Also wondering if it's possible to sync 2 computers so that when you make changes on one it reflects the changes in the other. Like you can with certain apps like Evernote.
Thank you for your help!
Cybrena

Yes he is right, Snow Leopard is your first step. Once you have that you can upgrade directly to Mountain Lion if memory serves me correct. Some people were saying that Lion was a little sluggish with the aluminum MacBook but that Mountain Lion was great. Personally I had Lion on it also and didn't think it ran badly. 10.6 was still with Rosetta (the program that ran power pc apps) but this is dropped on 10.7 and up. Up until just the other day I still had the stock 2 gb of ram. The firmware update happens with Snow Leopard and up so it should come up as a software update. If not, it can be done manually as well. The ram I purchased was 60 bucks for the 8 gb. For Lion and Mountain Lion I have to agree with the above reply, that it would run alot better with at least 4 gb. If you run that many apps at once then you are going to want as much ram as you can get. If you add a solid state drive you will be amazed at the difference it will make too.

What to look for when purchasing external display

Hey everyone,
First and foremost I want to say I am a web developer and graphic designer so what I am looking for is a display (not too big) 20" - 23" TV OR Monitor. This way when I am developing I am not making things HUGE so i can see them while other viewers can't. I have seen the display on a 30" screen and no that isn't going ot work.
I am now searching for an external display for my newly built office but I don't know what to look for besides DVI support. What resolution do I need to make sure it goes to? There is just so many options when looking at TVs or Monitors..
any input?

DVI support is a must and most LCDs in the size that you are looking for are going to have it.
Your MB can drive a display with a resolution of up to 1920 x 1200 which just happens to be the resolution of the 23" Apple Cinema HD Display. I didn't want to pay Apple prices for a display, so I went looking at Dell. I picked up a 20" 2007WFP display from them for about $360 shipped and it works like a charm with the Apple Mini-DVI to DVI adapter.
I prefer displays that use a S-IPS panel over the more common and cheaper TN panels. S-IPS is much better for color reproduction and that is why Apple uses them in their Cinema Displays. Dell uses the same panel is some of their 20" models - I got one - but some buyers are very upset that they got a TN panel instead of the S-IPS panel. I was lucky I guess.

Youtube videos only play for two seconds before displaying an error message since updating to FF28.

Since updating to Firefox 28, videos on Youtube will display a spinning wheel for some time, only play one or two seconds of the video, and then go to a Youtube ‘an error has occurred’ screen. At this point, Flash will crash, hanging Firefox for a minute or so. This occurs whether I am using the HTML5 player or the default player. The same videos worked fine previously in Firefox 27, and still work fine over the same wifi connection on Chrome for Android. A similar issue had occurred under Firefox 27, but only if the video was embedded in another site. Vimeo and Facebook Video still work fine: the problem seems to be specific to Youtube. Everything else on the Youtube site itself works; it's only videos that are malfunctioning.
I am running the latest Firefox and Flash updates on Windows 7 64-bit, with Tree Style Tab, Download Statusbar, Adblock Plus, Foxyscrobbler, NetUsageItem, and Pocket. The issue still occurs with all add-ons disabled in safemode, and with just Adblock disabled (my first thought was that perhaps Google had changed ad delivery in a way that caused ABP to break videos, but this doesn't appear to be so).
Does anyone have any ideas as to what's gone wrong? :)

Sorry, I forgot to mention, I tried turning hardware acceleration off as was suggested elsewhere on the support forum, but this didn't help either.

27" iMac (refurb, June 2011) not working as an external display for my MacBook Pro.

I just got a 27" iMac (refurb, June 2011) and it's not working as an external display for my MacBook Pro (not Thunderbolt). Any idea why? Command+F2 does nothing. I am connecting via Belkin Minidisplay Port-to-Minidisplay Port adapter.
Any help is appreciated...thanks!

Currently the ThunderBolt iMacs can only be used as an external display by other ThunderBolt Macs.
http://docs.info.apple.com/article.html?path=Thunderbolt/10.6/en/30822.html
Apple is very clear about that.
2009 and 2010 27" iMac with a Mini DisplayPort can be used by other Macs with a MDP-to-MDP cable.
Stefan

Will Thunderbolt allow multiple external displays?

The news about Thunderbolt mentions the ability to "daisy chain" up to 6 devices to the port.
Have there been any details released about the potential of driving multiple external monitors with Thunderbolt?
I have two 24" monitors that I'd like to use instead of the laptop display, but the Mini-Displayport only allows for a single external monitor (and yes, I've tried using both Dell's Multi Monitor Hub and Matrox's DualHead2Go devices with no luck).

What about this on the thunderbolt/mbp page?
http://www.apple.com/au/macbookpro/performance.html
"Thunderbolt technology has arrived — and MacBook Pro is the first notebook to have it. Now one connection carries both DisplayPort and PCI Express. With two 10-Gbps data channels, you can transfer data more than 12 times faster than with FireWire 800. And don’t worry about a single drive or peripheral tying up the Thunderbolt port: You can daisy-chain up to six devices, +*including up to two high-resolution displays.3*+ So with one tiny, streamlined port, you get lightning-fast transfer speeds and huge expansion capabilities."
The little *3 at the bottom of the page in fine print says:
"+The 15- and 17-inch MacBook Pro support two displays; the 13-inch MacBook Pro supports one display.+"
How do we connect two displays, though?
Message was edited by: astronomic

Images too dark on external display

Hello,
I use Lightroom on my (Lenovo) notebook. Because of the small screen size, I tried using it with an external (Samsung) display. However, when I open Lightroom on the external display, all the images suddenly seem way too dark. It is the case that this display is generally too dark, because when I view the same picture in a photo viewer or a browser it is not too dark. See for example this screenshot. On the left hand you see an image (export from Lightroom) in my browser, on the right hand the same image in Lightroom. You can clearly see it is much darker. When I view both images on the screen of the notebook itself, there is no difference between them.
Actually, when I move the Lightroom window from the notebook display to the external display, you can clearly see Lightroom adjusting the images from light to dark.
Does anyone know what causes this, and how I can prevent Lightroom from showing the images too dark?
Thanks!

I guess you misunderstood my problem. It's not only that images on the external display are way darker than on the notebook, but also that on the external display images in Lightroom are much darker than when I view the same image on the same display in a photo viewer or a browser. In the screenshot pictured above both the light and the dark version of the image are on the same external display.
However, in the meantime I found a solution. Changing the Windows Color System device profile to a non-WCS-profile did the trick: Photos appear as black, gray rectangles | Lightroom | Windows
Thanks anyway for trying to help.

Photoshop 2014 crashing unless external display is present

Hello -
Running Photoshop CC 2014 on a 2013 Macbook Pro Retina Display. 16 gb ram, OS X 10.9.5 with all software updates installed as of Nov 1 2014. Recently, I've discovered that Photoshop crashes on startup if my Macbook Pro is not connected to an external display. *any* external display connected remedies the problem if it's set at the primary display, and Photoshop starts up just fine. Photoshop is the only CC 2014 app giving me this issue. Photoshop CC doesn't - it launches fine without an external display connected.
I have tried a complete uninstall of Photoshop CC 2014 and reinstall, even used Adobe's clean uninstall tool. Have tried removing Photoshop preferences. Have disabled 3rd party plugins. Have started in "safe mode." Have turned off Extensis Suitcase's auto-activation plugin. Have tried without Suitcase open at all. Nothing has remedied the problem except for having ANY external display connected and designated as the primary display.
Will post my error log - wondered if anyone else has experienced this?

Error report from when this happens is below. Hoping something stands out to someone here for a remedy?
Process:         Adobe Photoshop CC 2014 [536]
Path:            /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Identifier:      com.adobe.Photoshop
Version:         15.2.1 (15.2.1.257)
Code Type:       X86-64 (Native)
Parent Process: launchd [153]
Responsible:     Adobe Photoshop CC 2014 [536]
User ID:         502
Date/Time:       2014-11-01 22:12:06.764 -0500
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: E5B6AC5D-74CE-231A-3696-6D8742E43C11
Crashed Thread: 0 Main Thread Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000050
VM Regions Near 0x50:
-->
    __TEXT                 000000010c67e000-0000000110f59000 [ 72.9M] r-x/rwx SM=COW /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
Thread 0 Crashed:: Main Thread Dispatch queue: com.apple.main-thread
0   com.extensis.AutoActivationPlugin.PS15 0x00000001bccf5bb8 CTFontDescriptorCopyAttributeOverride(__CTFontDescriptor const*, __CFString const*) + 44
1   com.apple.CoreText             0x00007fff923e031c TFont::InitMatrix(CGAffineTransform const*, __CTFontDescriptor const*) + 112
2   com.apple.CoreText             0x00007fff923dff80 TFont::TFont(__CTFontDescriptor const*, double, CGAffineTransform const*, __CTFontDescriptor const*) + 70
3   com.apple.CoreText             0x00007fff923dce8e CTFontCreateWithFontDescriptor + 114
4   com.apple.AppKit               0x00007fff924ea6ed -[__NSSharedFontInstanceInfo _platformFont] + 573
5   com.apple.AppKit               0x00007fff924ea195 -[__NSSharedFontInstanceInfo _textTransform] + 33
6   com.apple.AppKit               0x00007fff924ea163 -[__NSSharedFontInstanceInfo _matrix] + 22
7   com.apple.AppKit               0x00007fff924ea0b9 -[NSFont initWithInstanceInfo:renderingMode:] + 105
8   com.apple.AppKit               0x00007fff924e9dea -[__NSSharedFontInstanceInfo fontInstanceForRenderingMode:] + 383
9   com.apple.AppKit               0x00007fff924e9ae9 -[__NSFontTypefaceInfo fontInstanceForFontDescriptor:size:affineTransform:renderingMode:] + 671
10 com.apple.AppKit               0x00007fff9251a346 -[NSFont initWithCoder:] + 1731
11 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
12 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
13 com.apple.AppKit               0x00007fff92541489 -[NSButtonCell initWithCoder:] + 224
14 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
15 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
16 com.apple.AppKit               0x00007fff92516e26 -[NSControl initWithCoder:] + 265
17 com.apple.AppKit               0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
18 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
19 com.apple.Foundation           0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
20 com.apple.Foundation           0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
21 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
22 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
23 com.apple.AppKit               0x00007fff924d05ac -[NSView initWithCoder:] + 1949
24 com.apple.AppKit               0x00007fff924d2294 -[NSClassSwapper initWithCoder:] + 528
25 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
26 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
27 com.apple.AppKit               0x00007fff924d1cb8 -[NSResponder initWithCoder:] + 63
28 com.apple.AppKit               0x00007fff924cfe6f -[NSView initWithCoder:] + 96
29 com.apple.AppKit               0x00007fff92516d50 -[NSControl initWithCoder:] + 51
30 com.apple.AppKit               0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
31 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
32 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
33 com.apple.AppKit               0x00007fff924a9ccd -[NSNibConnector initWithCoder:] + 106
34 com.apple.AppKit               0x00007fff924a9b4e -[NSNibOutletConnector initWithCoder:] + 73
35 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
36 com.apple.Foundation           0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
37 com.apple.Foundation           0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
38 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
39 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
40 com.apple.AppKit               0x00007fff924a8782 -[NSIBObjectData initWithCoder:] + 205
41 com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
42 com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
43 com.apple.AppKit               0x00007fff924a856f loadNib + 232
44 com.apple.AppKit               0x00007fff924a7b6c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 288
45 com.apple.AppKit               0x00007fff9273c4d2 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 140
46 com.apple.AppKit               0x00007fff92813e3c _NXLoadNib + 193
47 com.apple.AppKit               0x00007fff9281384f -[NSAlert init] + 95
48 com.adobe.Photoshop           0x000000010c71472c 0x10c67e000 + 616236
49 com.adobe.Photoshop           0x000000010c7145b8 0x10c67e000 + 615864
50 com.adobe.Photoshop           0x000000010c77da13 0x10c67e000 + 1047059
51 com.adobe.Photoshop           0x000000010c77e68a 0x10c67e000 + 1050250
52 com.adobe.Photoshop           0x000000010c71b088 0x10c67e000 + 643208
53 com.adobe.Photoshop           0x000000010c9bd67b 0x10c67e000 + 3405435
54 com.adobe.Photoshop           0x000000010c9bd829 0x10c67e000 + 3405865
55 com.adobe.Photoshop           0x000000010c680d34 0x10c67e000 + 11572
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib         0x00007fff8d589662 kevent64 + 10
1   libdispatch.dylib             0x00007fff8b6af421 _dispatch_mgr_invoke + 239
2   libdispatch.dylib             0x00007fff8b6af136 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 3:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 4:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 5:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 6:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 7:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 8:
0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
Thread 9:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 10:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 11:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 12:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 13:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 14:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 15:
0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 16:: com.apple.CFSocket.private
0   libsystem_kernel.dylib         0x00007fff8d5889aa __select + 10
1   com.apple.CoreFoundation       0x00007fff8f408a03 __CFSocketManager + 867
2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff7c688680 rcx: 0x0000000000010f80 rdx: 0x0000610000086180
rdi: 0x0000610000086180 rsi: 0x00007fff7c688680 rbp: 0x00007fff5357e2e0 rsp: 0x00007fff5357e2c0
   r8: 0x00007fff9249331e   r9: 0x0000000000000032 r10: 0x00007fff92493306 r11: 0x00007fff9249331e
r12: 0x0000000000000000 r13: 0x0000610000086180 r14: 0x0000610000086180 r15: 0x0000000000000000
rip: 0x00000001bccf5bb8 rfl: 0x0000000000010202 cr2: 0x0000000000000050
Logical CPU:     0
Error Code:      0x00000004
Trap Number:     14

Any way to connect two external displays?

Hello,
I have a quick question about connecting my PowerBook G4 15'' (machine model: Powerbook 5,6) to some external displays.
I am trying to connect it to both a Samsung Syncmaster LCD and my TV.
Currently, I am able to connect to each successfully, but only one at a time.
My Samsung syncmaster LCD is connected via the DVI port on my powerbook, and using the DVI to VGA adapter, since the Samsung LCD is VGA. My TV is connected via S-Video, though I do have the s-video to composite adapter that came with my powerbook if it makes a difference.
Anyways, my problem is I want to be able to use all three displays at once (the powerbook screen, my samsung LCD, and my TV), but i can only get one of the external displays working at a given time, and have to unplug the DVI (samsung lcd) to get the TV to be detected and activated as an external display.
Any suggestions will be much appreciated. If there is some adapter I need to buy to make all this work, thats fine, just tell me what it is.
Thank you for all your time.
Regards,
Matt Ellison
PowerBook G4 15" (machine model: Powerbook 5,6) Mac OS X (10.4.3)

This solution was previously pointed out to me on the 17" PowerBook forum. I don't have one and don't know how well it works. Last I saw they didn't have drivers for Tiger, yet.
http://www.villagetronic.com/
I expect you would hook your SyncMaster LCD to the VT Book and then use the S-Video port on the PB to connect the TV.

New 27inch iMac, external Display "blinks" while in "Display Sleep"

I just updated from a 24inch iMac to a 27inch iMac.
I'm using the same setup for connecting the external display, which is a miniDisplay Port adapter(from Apple) to DVI, then DVI to the external monitor.
All works fine until the "Sleep Display" kicks in, then the external monitor pops up the "DVI-I no signal" warning. This is normal but instead of going away after a couple of seconds it begins to blink as if their is communications going on between the monitor and iMac. So its blinking this message endlessly and thus the external monitor never really goes to sleep.
Since this worked fine on the iMac 24inch, I'm assuming it has something to do with the "Thunderbolt" port, using a miniDisplay port adapter.
The external monitor is a 20 inch Viewsonic VP2030b, running at 1600x1200.
I added a YouTube video for clarity. http://www.youtube.com/watch?v=Q7Zm_U_7sbc

Go to: System Preferences > Displays select the Color tab > uncheck "Show profiles for this display only" and try one of the RGB profiles to see if it is better for you.
Then if you are not happy with one of those..? Try Selecting, Calibrating and Saving a different Profile, other than the default one offered for that monitor.

Qosmio X870-116: usage of Intel / nVidia GPU on internal / external display

Hello,
I have a Qosmio X870-116 which have 2 video cards, a Intel on board and a Nvidia more powerfull.
My probleme, I don't how I switch my display on the Intel card and I see my Nvidia only for the external display.
Some one have an idea to switch on the nvidia card to my first display?
Thanks

Hi
Something like that isnt possible.
You cannot use two graphic cards simultaneously for internal and external display.
First of all you can switch between external and internal display using the function key Fn + F4 (or just F4)
Secondly the nVidia Optimus technology optimize notebook performance by seamlessly switching between a nVidia GPU and Intel internal graphic card.
The switching is automatic and does not require any notebooks reboot.

MacBook Pro Retina + 3 external displays + clamshell + heat issues

Hi Apple Community,
I have a 15" MacBook Pro Retina (2.6, 16GB) running 3 external displays (2x 22" via thunderbolt ports -> VGA & 1x 27" via HDMI). I am running in Clamshell (i.e. the MacBook Retina has the lid closed and is in a TwelveSouth BookArc). I currently have SMC FanControl running and set the fan to max (~5900 rpm) which is keeping the temp at ~54 degrees celcius.
Basically I'm wondering if anyone knows about the heat management with using a macbook this way. Will too much heat damage the screen since the lid is closed etc.... How hot does the macbook have to get before damage can occur...?
Many thanks
SamNz8107

Hey Samnz8107!
Thanks for your reply. Saw it straight away and tried the update but it didn't work. When you open the dmg it says:
"Alert:
This software is not supported on your system."
So that's unfortunate!
Nope nothing comes up on the third screen when plugged in. And in the display window in the System Preferences, in arrangement, only the mac display and two displays are shown. It seems that the mac only wants to see two external displays. Because say all three are plugged in, it's whatever is plugged in last that isn't seen. So it's not a specific problem with the HDMI, because say if I unplug one of the VGAs, then the other VGA and HDMI will show no problem!
When three screens are plugged in, the third screen is on and knows something is there (so it doesn't go into standby mode or ask you to connect something...but it just stays off. It's not a black screen - it is definitely off .ie there is no signal...but the screen does know something is there!
Any further ideas?

Non-thunderbolt external displays on rMBP

If I buy a couple 27-inch displays elsewhere, instead of from Apple, could I use them on the rMBP? Or does it only work with the Apple Thunderbolt displays? Do external displays (of any brand) need to go through Thunderbolt or can they use USB 3.0?
Just curious, I only have background in using external displays with Windows. Not sure how the plug&play works on OSX.

You can use other external monitors with the MBPr but you will need an adapter for the thunderbolt port to say VGA or DVI. Or you can use the built-in HDMI port.

10.5.6 Update USELESS!!! External Display Issues Still remain!

The external display issues remain, even after installing the update.
I'm sick of this!
Is it a hardware issue or software related?
Are the 9600 graphics chips defective?
Come on Apple and be honest to your customers, we all paid a lot of money for these systems!
Does anyone out there know where can I complain to?
I need an email address or something that is not directed at iphones or ipods!
Cheers.
<Edited by Moderator>

I'm not sure what to make of this at this point. I ordered a CTO 2.8GHz with 4GB RAM and 320GB HD the day they were announced. First week or so, few if any problems. Then the "UHF" like bands of static began to appear randomly. I use my computer 90% of the time driving an external monitor. I use a separate set up at home and work with duplicates of all cables. The problem occurs on both. I spoke with Apple Care - they patched me over to support and moved me up to Tier one pretty quick, even had me send in my System Profiler information for every combination of screen and graphics card. Then they emailed me a program to capture my monitor info again with every combination of screen and graphics card. No solution. They finally asked to "capture" my computer for their labs and sent me a new one.
Once again, about 2 1/2 weeks of smooth sailing and bam, same issues now occurring. If it's a driver issue, why is everything fine for so long? Also, 10.5.6 and the new firmware have failed to address. Given my above exchanges with Apple, they certainly can't claim they don't know about it.
I've been using Apple Products for a long time. I've seen some real buggy stuff - like when File Vault first came out but this is the worst I've experienced. Seems like poor quality control. If it's a select few machines, I appear to have won the lottery as I've had two of them.
I'm sure this issue is much more wide spread as it is a non-issue if you only use the internal display. Only people consistently driving an external display will even know there is a problem.

Only FIREWIRE for playback on External Display???

Similar Messages

Maybe you are looking for