Hum being caused by my Cinema Display 23

Hi!
Here it's the problem I have. I've set up a mini recording studio where I am using a Macbookpro 15 (late 2008), a Mixer (Behringer), two KRK VXT4, a ZOOM h4n and a Cinema Display. I am using my ZOOM as sound card (I know it's cheap). When I volume up I can clearly hear a hum, 50HZ I guess. I have tried unplugging everything I found out that the source is my Cinema Display. In fact, When I turn it off (when I keep it unplugged) the sound is perfectly clean. When I just touch my Mac Book pro with, say, the USB cable coming from the Display (keeping the volume untouched) I can clearly hear the hum coming in. It also happen when I try to plug the minidisplayport adapter.
So, what do you suggest?
Thanks, thanks, for your kind help!!
Alex

I've tried. In fact, there are two kind of buzz...As I lower the brightness there is a second buzz that volumes up. Highering the brightness makes this second buzz disappear, though leaving the hum, the 50hz unaltered

Similar Messages

Osx update causes flicker on cinema display

I recently got a new Mac Pro (with Lion), to which i attached my older Apple Cinema HD 23" display. All was fine until i did a software update, now i have an insufferable flicker that goes randomly and constantly, and also when I move the mouse of type on the keyboard. What is going on? Is the problem with the monitor? the video card? the computer? the DVI to ADC adapater? Help!

Hi William,
This has been discussed on the OS X Lion pages here:
https://discussions.apple.com/message/16357859#16357859http://
It seems a temporary fix is to unplug the ADC adaptor from the monitor card for 5-10 seconds and then put it back in. Flickering stops but only till the next restart.
Shame about this as I use a HD Cineman Display that although nearly 8 years old is still pixel perfect and cost me a significant amount of money when new.
Potentially this is turning out to be one of the most expensive point upgrades to an OS if a new monitor has to be purchased

DVI Distribution Amp between Macbook and 30" Cinema display

I'm wanting to split my output from my macbook Pro to two different outputs, one of them being a 30" mac cinema display. Currently I have the display port to DVI plugged in the laptop, then the DVI plugged into a 1:2 splitter, then the cinema display and another output plugged in there. This works, but the dist amp is single link so I'm restricted to 1280 resolution.
My question is if anyone has used this setup with a dual link splitter and mac adapter cable and gotten the full resolution on the 30" display. I don't really see any reason it wouldn't work, but before I drop $300 into the splitter, I wanted to see if anyone can confirm this setup would or would not work.

That's still not going to work. The 30" ACD is fairly limited in this way. It doesn't have a normal scaler like almost every other monitor and can only display two resolutions, namely 2560 x 1600 when running dual-link and 1280 x 800 from single link. When it does display formats between those two resolutions, it is actually displaying at full 2560 x 1600 (dual-link) and the scaling is happening within the computer, not the monitor. So you can't use a splitter, not even a dual-link one, for what you want to do.
Have you considered running the TV from one of those USB video adapters? What kind of content do you plan to have on the TV? As long as it isn't something like video, the USB solution might work for you.

Hi! My imac27 fusion drive late 2013 restarts randomly when using 30" Cinema Display. What could cause this?

Hi! My imac27 fusion drive late 2013 restarts randomly when using 30" Cinema Display.
32 GB Apple RAM, Mavericks 10.9.2
I'm using power outlets that eliminitates surge fluctuations.
What could cause this? What can i do? I', a bit desperate!

Adapter: Apple Mini DisplayPort to Dual-Link DVI Adapter
I wonder what the "Fault CR2: 0xffffff80078ca4f0, Error code: 0x0000000000000000, Fault CPU: 0x0" is...
Panic log:
Anonymous UUID:       44957DF9-C5B4-5AE1-AD54-9C81A374FC95
Tue Mar 18 03:52:54 2014
panic(cpu 0 caller 0xffffff80052dbe2e): Kernel trap at 0xffffff800523404e, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff80078ca4f0, CR3: 0x000000004329d056, CR4: 0x00000000001606e0
RAX: 0xffffff838906d000, RBX: 0xffffff838905d000, RCX: 0xffffff80058ca4f8, RDX: 0x0000000000000000
RSP: 0xffffff8394cbbd60, RBP: 0xffffff8394cbbd90, RSI: 0x0000000034089b0e, RDI: 0xffffff80058874c8
R8: 0x0000000000000001, R9: 0xffffff8394cbbe90, R10: 0x0000000000000020, R11: 0x0000000000000206
R12: 0x0000000000000005, R13: 0x000006005279d2e6, R14: 0xffffff80491ceb20, R15: 0xffffff80078ca4e8
RFL: 0x0000000000010046, RIP: 0xffffff800523404e, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff80078ca4f0, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff8394cbb9f0 : 0xffffff8005222fa9
0xffffff8394cbba70 : 0xffffff80052dbe2e
0xffffff8394cbbc40 : 0xffffff80052f3326
0xffffff8394cbbc60 : 0xffffff800523404e
0xffffff8394cbbd90 : 0xffffff8005233b17
0xffffff8394cbbdb0 : 0xffffff800524f18d
0xffffff8394cbbde0 : 0xffffff80052165da
0xffffff8394cbbe20 : 0xffffff80052163f4
0xffffff8394cbbe80 : 0xffffff8005213c1d
0xffffff8394cbbef0 : 0xffffff800521e043
0xffffff8394cbbf70 : 0xffffff80052c976d
0xffffff8394cbbfb0 : 0xffffff80052f3b46
BSD process name corresponding to current thread: Logic Pro X
Mac OS version:
13C64
Kernel version:
Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
Kernel slide:     0x0000000005000000
Kernel text base: 0xffffff8005200000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)
System uptime in nanoseconds: 6598450610233
last loaded kext at 8144333788: com.apple.driver.AppleHWSensor          1.9.5d0 (addr 0xffffff7f874fb000, size 36864)
loaded kexts:
com.caiaq.driver.NIUSBHardwareDriver          2.6.0
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleRAID          4.0.6
com.apple.driver.AppleBluetoothMultitouch          80.14
com.apple.iokit.IOBluetoothSerialManager          4.2.3f10
com.apple.driver.AppleMikeyHIDDriver          124
com.apple.driver.AppleGraphicsDevicePolicy          3.4.35
com.apple.driver.AppleMikeyDriver          2.6.0f1
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AGPM          100.14.15
com.apple.driver.ApplePlatformEnabler          2.0.9d1
com.apple.driver.X86PlatformShim          1.0.0
com.apple.driver.AppleHDAHardwareConfigDriver          2.6.0f1
com.apple.driver.AppleHDA          2.6.0f1
com.apple.driver.AppleUpstreamUserClient          3.5.13
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.GeForce          8.2.4
com.apple.iokit.IOBluetoothUSBDFU          4.2.3f10
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleIntelHD5000Graphics          8.2.4
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AppleUSBDisplays          360.8.14
com.apple.driver.AppleMuxControl          3.4.35
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.driver.AppleHWAccess          1
com.apple.driver.AppleSMCLMU          2.0.4d1
com.apple.driver.AppleBacklight          170.3.5
com.apple.driver.AppleMCCSControl          1.1.12
com.apple.nvidia.NVDAStartup          8.2.4
com.apple.driver.AppleIntelFramebufferAzul          8.2.4
com.apple.driver.AppleIntelMCEReporter          104
com.apple.driver.AppleLPC          1.7.0
com.apple.driver.AppleThunderboltIP          1.1.2
com.apple.iokit.SCSITaskUserClient          3.6.6
com.apple.driver.AppleUSBODD          3.4.1
com.apple.driver.CoreStorageFsck          380
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          35
com.apple.driver.AppleUSBHub          666.4.0
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.5.1
com.apple.driver.AppleSDXC          1.5.2
com.apple.driver.AirPort.Brcm4360          831.21.63
com.apple.iokit.AppleBCM5701Ethernet          3.8.1b2
com.apple.driver.AppleUSBXHCI          670.4.0
com.apple.driver.AppleAHCIPort          3.0.0
com.apple.driver.AppleACPIButtons          2.0
com.apple.driver.AppleRTC          2.0
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          2.1
com.apple.driver.AppleACPIEC          2.0
com.apple.driver.AppleAPIC          1.7
com.apple.nke.applicationfirewall          153
com.apple.security.quarantine          3
com.apple.kext.triggers          1.0
com.apple.driver.IOBluetoothHIDDriver          4.2.3f10
com.apple.driver.AppleMultitouchDriver          245.13
com.apple.iokit.IOSerialFamily          10.0.7
com.apple.driver.DspFuncLib          2.6.0f1
com.apple.vecLib.kext          1.0.0
com.apple.iokit.IOAcceleratorFamily          98.14
com.apple.nvidia.driver.NVDAGK100Hal          8.2.4
com.apple.nvidia.driver.NVDAResman          8.2.4
com.apple.iokit.IOBluetoothFamily          4.2.3f10
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.iokit.IOSurface          91
com.apple.driver.AppleGraphicsControl          3.4.35
com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.3f10
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleUSBAudio          2.9.5f4
com.apple.iokit.IOAudioFamily          1.9.5fc2
com.apple.kext.OSvKernDSPLib          1.14
com.apple.driver.AppleHDAController          2.6.0f1
com.apple.iokit.IOHDAFamily          2.6.0f1
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.4.1
com.apple.driver.AppleSMBusController          1.0.11d1
com.apple.driver.AppleSMC          3.1.8
com.apple.driver.AppleSMBusPCI          1.0.12d1
com.apple.AppleGraphicsDeviceControl          3.4.35
com.apple.iokit.IOAcceleratorFamily2          98.14
com.apple.iokit.IOGraphicsFamily          2.4.1
com.apple.driver.IOPlatformPluginFamily          5.7.0d10
com.apple.driver.AppleThunderboltEDMSink          2.1.3
com.apple.driver.AppleUSBHIDKeyboard          170.15
com.apple.driver.AppleHIDKeyboard          170.15
com.apple.iokit.IOUSBHIDDriver          660.4.0
com.apple.driver.AppleUSBMergeNub          650.4.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.6
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOUSBMassStorageClass          3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.6
com.apple.driver.AppleUSBComposite          656.4.1
com.apple.driver.AppleThunderboltDPInAdapter          3.1.7
com.apple.driver.AppleThunderboltDPOutAdapter          3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily          3.1.7
com.apple.driver.AppleThunderboltPCIUpAdapter          1.4.5
com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.5
com.apple.driver.CoreStorage          380
com.apple.iokit.IOUSBUserClient          660.4.2
com.apple.driver.AppleThunderboltNHI          2.0.1
com.apple.iokit.IOThunderboltFamily          3.2.7
com.apple.iokit.IO80211Family          630.35
com.apple.iokit.IOEthernetAVBController          1.0.3b4
com.apple.driver.mDNSOffloadUserClient          1.0.1b5
com.apple.iokit.IONetworkingFamily          3.2
com.apple.iokit.IOUSBFamily          675.4.0
com.apple.iokit.IOAHCIFamily          2.6.5
com.apple.driver.AppleEFINVRAM          2.0
com.apple.driver.AppleEFIRuntime          2.0
com.apple.iokit.IOHIDFamily          2.0.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          278.11
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.AppleKeyStore          2
com.apple.driver.DiskImages          371.1
com.apple.iokit.IOStorageFamily          1.9
com.apple.iokit.IOReportFamily          23
com.apple.driver.AppleFDEKeyStore          28.30
com.apple.driver.AppleACPIPlatform          2.0
com.apple.iokit.IOPCIFamily          2.9
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
com.apple.kec.pthread          1

How to deal with hum/interference - 30in Cinema display?

Hi, I hope someone can help with this!
I have a 30inch Cinema display, which has started to create a hum through my powered speakers (Genelec 8040's). I have tried plugging the (mains powered) speakers into a separate mains socket, moving them about, as far as is practical, and even sticking a sheet of tinfoil between the back of them , but no luck.
The hum comes on at very low volume levels, and is persistent, i.e. if I am playing a track in iTunes, and there is a quite bit in the song, I get 'errrrrrrrrrrrrrrrrrrrrrrrrrrrrrr' in the background.
Now the weird thing is that I was playing a game, and for some reason there was no hum, which suggests it may be fixable via software/settings?
I'm a bit of a newbie at this stuff (as the tinfoil experement, may suggest!), so I'd really appreciate any advice!
TIA,
Steve

Thanks for the feedback. I thought it was the monitor, as the hum is only present when it is on. It may be a combination of the Mac Pro & the monitor though... Mmmmm...
I think I may have fixed it, well improved the situation, I'll say what I did in case anybody else has the same issue, or has a better fix.
I tried unplugging the mini jack audio out, which goes from the mac, to a mixing desk, to the powered Genelec audio monitors. When I did this the hum stopped, which I think means that the issue is a poorly shielded mini jack to phono cable, as if it was direct interference from the monitor to the speakers, it should (in theory) be present regardless of whether the audio is connected into the mac or not.
I have moved the cable about, and the hum is reduced, so I think I have found the problem.
Hopefully this will be of use if anybody else has the same issue!

Black band on my 30 inch cinema display. Any known causes?

Hey everyone,
My 30 inch cinema display is doing some wierd things which I havent encountered before.
If you can see the image, towards the LEFT SIDE CENTRE, there are these BLACK BANDS.
these start to appear after about 5-15 mins after the display is turned on. although they dont show up on bright backgrounds.
If I let to monitor cool down for 10 mins and start it up again they are gone and they start appearing again in about a min or two,
Has anyone seen any such issues before or is this a known issue with the 30 inch.
Any ideas on what I should do about this.
I will be taking it to Apple for sure as its still under warranty but would like to know
what is causing this and whats apples take on it.
Cheers,
Ani

I bought a 30inch as well a couple of months ago but have very little use except for watching movies. But when I use grey colour as the background the banding mark became very noticeable. It seems to be some kind of design issue i suppose and I dont know how Apple is going to address this. It's not a cheap monitor after all and i am very disappointed with this.

If plugged into the power supply, should the Cinema Display A1081 standby light come on without being plugged into a mac

I was given an old Cinema Display A1081 a few years ago. I am trying to test it and want to know if plugged into the power supply, should the standby light come on without being plugged into a mac? I don't want to buy a DVI to mini display adapter if it isn't working. One thing I did do was plug Monitor power in and then the USB plulg into my PC laptop and my iPhone charger USB plug into the back of the monitor. I am able to charge my iPhone this way so I know that the power supply is working. But I can't tell if the monitor itself is workign as no ligths are on. (PS: I am purchasing my first Mac so I am a complete newb but very proficient with PCs) Thanks so much for your help.

These Apple tech notes may help:
How to use your PowerBook G4, MacBook Pro or MacBook with the display closed
How to use your PowerBook G4, MacBook or MacBook Pro with the display closed and a Bluetooth keyboard or mouse
Just a final question about Sleep mode - does this have any negative effects on the life or performance of the laptop? I'm so used to Shutting down the laptop each day that I worry about Sleep mode having some sort of drain on the components or something.
There are only two practical differences between Sleep and Shut Down:
1. Sleep will wake instantly, so you don't have to wait for startup.
2. Sleep will drain a new, fully charged battery after several days without being woken or plugged in. If you shut down, the battery charge lasts much longer. Obviously, if you only sleep it overnight, you'll still have plenty of battery left in the morning.
Don't sleep it more frequently than necessary, though. Frequently turning the backlight and hard drive off and on can shorten their life. Just do what's reasonable. I usually leave mine awake until I have to transport it in a bag, along with sleeping it overnight. On battery, I'll sleep it more often to preserve battery.

Cinema display causing freezes and kernel panics?

Okay, if anyone has experienced this before I would like to know. I've been having these powerbook freezes at night., and occasional kernel panics during the day. I usualy leave my computer on all night, but when I check it in the morning it's pretty much froze everyday.
I did a complete clean install, I've ran hardware test, past both tests, reset pram, av-ram. I did install 2 gig of ram (2x1), I was beggining to question the ram, but once I unpluged it from my Cinema display I have not had one freeze in three days. Why would that be? Has anyone else had problems like this?
I've used this display for a year with my previous powerbook and have had no problems, but for some reason these two don't get along. I'm thinking it might have something to do with the usb, or firewire ports. Any ideas?
Thanks in advance.

You know it does seem to be the memory. Once I replaced the memory with different chips all kernel panics have stopped, same with freezes. Funny how this passed all the memory tests.
All seems to be better now anyway....thanks.

What is causing a sound problem with new Cinema Display 27 ?

My new 27 Cinema Display intermittently won't play sound when connected to my MB Pro. Restarting the computer doesn't fix it, and all the display audio settings are correct etc. Phoned Apple Support and the fix was to unplug the power from the back of the cinema display to reset the screen controller. This keeps happening - is this a software bug ? Hardware problem ? Is it fixable or something that is a legacy of the 24 inch cinema display problems ? I really like the screen size but don't want a display that I keep having to plug/unplug in order to watch hulu, play itunes etc. Apple won't declare my screen to be defective even though this has happened a few times but can't tell me how to fix the problem either. Am going to send it back for a refund - don't know whether a different display will have the same problem or if this is a generic cinema display defect. Thanks for any insight.

There are threads in this forum and MacRumors where numerous people are having this issue. When I contacted support they had me reload the software update and reset the power. I am encouraging everyone to contact Apple every time it happens so we can get a fix for the problem. It is the general consensus that this is a software issue that can be corrected if we can get Apple to work on it. I agree with you I expect my $1000 monitor to work properly all the time.

Mid-2012 MBP with 27" Cinema Display SCREEN GOES BLACK WHEN USING USB PERIPHERALS IN DOCK

I haven't been able to find any straightforward answer as to why this is happening and it's becoming one of the most infuriating things in my life, impeding my workflow and costing me unmeasurable time in waiting, rebooting, screwing with cables, etc.
I use my MBP as a DAW for multitracking live audio events to ProTools through a digital console where I work. Here's my gear list that I use every day:
Mid-2012 MBP - Yosemite, 8GB, i7 quad 2.5, mechanical hd
HengeDocks dock for my exact model machine - has set-screw jacks for CinemaDisplay power, Tbolt, FW800, USB, USB, SDcard, headphones, etc
USB wired keyboard
Anker 1x4 USB3.0 hub - I have a TimeMachine 1TB drive, 3TB project backup drive, audio interface and MIDI I/O or PT iLok, depending what I'm working on
Magic Mouse (BlueTooth)
Here's what's happening:
SCENARIO 1 - I insert the CinemaDisplay (cD) power connector and TBolt plugs into the dock, tighten the set screws, close the lid of my MBP (already logged into Yosemite & linked with MagicMouse [mM]) and stick the MBP into the dock... everything comes up on the cD and I can go about my day. At this point, I can plug the USB hub into the back of the cD and the system sees the hub & all peripherals listed just fine.
SCENARIO 2 - Install cD powercon, TBolt connector, USB3 hub, USB keyboard into the dock, close the lid on MBP (again, logged in), insert into dock... cD comes up, looks great for about 15 seconds then goes completely blank. No response from key presses, mouse clicks, threats with a hammer, etc. Then, of course, I have to yank the MBP out of the dock, which hard-disconnects the external drives (backup and TimeMachine... good for them, right?) and causes the MBP to flake, thinking it's still in the dock, then not, then logging me out & requiring a password (not a big deal- I deal with copyrighted stuff, so passwords aren't the issue).
***EVEN IF I DO NOT PLUG THE USB3 HUB INTO THE HENGE DOCK, THE cD STILL GOES BLANK AFTER 15 SEC... IT ONLY SEEMS TO LIKE THE TBOLT AND POWER... NO OTHER PERIPHERALS (fw800, USB, etc)***
It seems like the MBP freaks out when the lid is closed and there are USB/FW peripherals plugged in while using a secondary TBolt display as the main output... seems stupid... if I need a closed-lid dock, the MBP shouldn't care what I have plugged in while the lid is closed. I had the same issues with Mountain Lion & Mavericks and now it's being repeated with Yosemite.
My goal in this exercise is simply to free up the USB jacks on the back of the cD for two reasons - #1) from time to time, I have extra things to plug in and I don't want some massive USB 1x8 hub on my desk... looks stupid; #2) the bottleneck created by plugging in the hub to the back of the cD (another hub via TBolt) almost triples the time required to back up/copy files. I move files from system drive to backup drive & back VERY often due to the nature of my job... speeding up this process would greatly improve my efficiency in the matter. Why would Henge create a dock with all the jacks on it to allow someone to plug into a cD that won't frickin work with said cD? Every other dock I've found makes the user stick the MBP on a slanted, goofy-looking stand and have the lid open or something dumb like that... what I have is the setup I need... just need the USB stuff to work while lid is closed and everything from powercon & cD to USB3 hubs will work without making the cD freak out.
Any ideas out there?

Have now taken the 27" display into the repair shop and after 24 hrs got the phone call - "appears to be nothing wrong with it, will check again on Tuesday and let you know".
I can't seem to find anything on the net describing a similar problem. Everything is working fine right now with the Mac Pro connected to the older 20 inch Cinema Display. In fact, everything seems to be working about a second faster.
I was told by the local retailer that Apple no longer makes the 27 inch LED Cinema Display product and the new display, the "Thunderbolt" will not work with my 13 month old Mac Pro.
***??? In 20 years of owning Mac equipment, this is my first major "uh-oh".

FireWire (and USB?) problems with 23" Cinema display

Hello.
Whenever my G5 wakes from sleep, I seem to have problems with FireWire devices attached to the Cinema Display (and, possibly, the USB ports also). Somehow, it seems that the "wake" signal is not transmitted to them.
Specifically:
a FireWire hard drive does not spin up (a USB drive connected to the back port does, as does a FW 800 drive also connected to my PowerMac). When I try to access it, then it finally spins up.
An EyeTV 200 device fails to connect (i.e., display TV or record shows) unless the Fi cable is unplugged and reattached.
This happens WHENEVER the Mac sleeps. However, if I attach those two devices directly to my PowerMac, they function just fine, using the same port the Cinema Display is attached to.
I don't have other comparable devices attached to the USB port of the Cinema Display, except (previously) for a Plextor ConvertX DVR (a USB 2 device), which exhibted the same problems as the EyeTV 200, which is why I tried swapping it with the FireWire-based EyeTV (unsuccessfully). So I have some evidence that the USB port has similar problems, but nothing conclusive.

Hey Scott
You are not alone. I'm beginning to think there is an issue with the power supplies of the 23" displays.
In my case, my computer is set to never sleep, while the display is set to sleep atfter 30 mins or so.
It appears that the computer won't wake up in these cases, but in fact what is happening is that the display won't wake up.
Multiple re-starts are sometimes necessary to get the display up and running again.
While your problem seems slightly different, I think that the two are related in that there is not enough power being delivered from the power supply for the monitor to both your USB and Firewire devices connected to your display.
I don't really have a solution as of yet.... aside from purchasing a new power supply from Apple... But, you are not exactly alone in your misery. Should I run across a fix for this aside from the power supply, I'll be glad to let you know.
Generally after HD's spin down, they usually don't spin up unless they are accessed. If you have any open files on your FW800, that may explain why it does spin up when you wake up your system.
One thing you can try, in the System Prefs, under Energy Saver, uncheck "Put HD's to sleep". This may cause all of them to spin up when you wake your system up.

Apple Cinema Display Dimming On Bootcamp Startup (found a fix!)

Hey guys I recently bought an Apple 27 inch Cinema Display to go along with my 15 inch Macbook Pro. Prior to purchasing the display I had installed Windows 7 Professional on my Macbook and used bootcamp to play games etc. I recently had to delete my bootcamp partition and reinstall it (ran out of space and didn't want to deal with winclone/making an image of my system). Everything went perfectly fine except the cinema display would always dim on startup and there was no way to adjust the brightness.
I talked to Applecare multiple times and they came up with zero solutions, but I found a fix myself. If you go into MSCONFIG, while in Windows 7, and turn off bootcamp services from starting at the launch of Windows 7 it doesn't dim the screen and everything works completely fine. I'm making this post to show people how to easily fix this problem and so Apple can fix whatever is making the bootcamp services dim the brightness of the cinema displays.
The problem is indeed 100% caused by the bootcamp services. If I start the computer without bootcamp services running there are no brightness issues. As soon as you open bootcamp services it instantly dims the screen and have to go back to MacOSX to fix the brightness.
Anyone have a clue why bootcamp services wouild do such a thing?
Thanks for your time, I hope this helps some people and I really hope apple looks into this problem.
P.S. Please discuss this topic and add any other ideas on hotfixing this problem.
ADDITIONAL INFO: I am using Windows 7 Professional 64x.

I traced the problem to hardware - I'm running an older Apple ADC 23" Digital Cinema display, so use and ADC to DVI adapter - because of this there is a USB "pigtail" which carries the USB from the rear ports on the monitor into the PC. This works fine in MacOS, but boot into Windows (and I tried XP running NOT in BootCamp and Windows 7 running IN BootCamp) and it seems to hunt and search for this "generic hub" (the USBs in the monitor) and upon not finding them appears to send some kind of signal to that hub, disengaging it or whatever, and dimming the screen. In Windows XP this happens right after the login screen appears, but in Windows 7 it won't happen until AFTER you log in (always thinking "Gee! Maybe this.... time.... ah.... ^%$#@!").
I tested my theory by using WinADC (the add on software that adds brightness controls for Apple ADC monitors to Windows XP - only 32 bit btw) on the XP machine - every time I started up WITHOUT that extra USB connection I was fine. When I started up with it... DIM happened. Then I tried starting it up without it plugged in.... FINE... then plugged it in AFTER full startup and loing... DIM happened. Plugging and unplugging it in in Windows would sometimes re-reveal the added extension for brightness (WinADC) so you could see how the USB was being searched not just for simple connections but for the brightness CONTROLS that are built into the monitors hub it seems.
So, I'm going to try your suggestion here, turning off Boot Camp services, but, for others if that doesn't work: Start up in mac OS, set your brightness, then UNPLUG any additional USB that is being run into the monitor and startup in PC - should be good to go.

Horizontal line across 23" Cinema Display

Hi
I am using a friend's display, and it has an annoying horizontal 1 pixel line across the screen about 40% of the way down from the top. This is the 23" aluminum Cinema Display with the external power brick and DVI connector. The pixels appear to be about 50% gray, but the color changes a little (to a dark gray) depending on the surrounding image being displayed.
Any thoughts about what might be causing this and if there might be an inexpensive fix? (FWIW, I know it is in the screen since it does the same thing w/ various laptops plugged in.)
TIA
A

I had that happen on my 30" ACD. I believe it was caused by a power surge, but could've been just crappy manufacturing. Suffice to say I had display replaced (luckily it happened during the first 30 days).
I hope you have AppleCare for your display so that it can get replaced/fixed.

Cinema Display too bright upon waking up

Whenever my cinema display wakes up from sleep, the screen is really bright (ie washed out). It'll stay that way until I open up the Displays control panel, then it will reset to the correct profile. It's not a critical issue but an irritation. Anyone else experiencing this problem/have a solution?

I have the exact same problem on a 30" cinema display. I've tried to adjust color settings in Sys prefs, downloaded DarkAdapted (which works well with the ACD but completely messes with my second display colors apart from being a hassle to launch it every time) and that's all I could do about it so far. Frankly my eyes hurt every night I use it, I even prefer to use only my 15" MBP because I feel it's doing damage to my eyes. This is just ridiculous, it's wonderful to have a bright 2560x1600 screen when you are working open air in a Hawaiian beach but is it so hard to make the screen darker when you are an urban night worker?
APPLE PLEASE WE NEED NATIVE SOLUTIONS!!! (before I get blind or sell it on ebay if possible!)

Cinema Display 24" won't work with Mac Mini 3.1

I recently purchased a refurbished Apple LED Cinema Display 24" from a buddy. I'm pairing it with my used Mac Mini 3.1 (2009?). The display port mini connections seem to match. The USB is plugged in. The only cable unused is the "macbook power" plug, from the display. I know the display and CPU both work fine independently. Cinema display seems to power the USB and "Macbook power". I just can't get any life out of the display. These 2 devices should work together right? Is there a sceret power-button that I don't know about?

The video cards that ship with the current Pro have one Display Port and one mini DVI port.
There is an adapter to connect a DVI monitor to a Display Port connection. There is no such thing as an adaptor that will let you connect a Display Port equipped monitor to a mini DVI port on the graphics card.
Final Cut Pro uses dual monitors connected to the same graphics card. Using a twin graphics card setup causes problems with FX Plug FCP plugins, which can cause FCP to fail to launch.
The solution is to find a Graphics card with dual Display Port connectors, (if one even exists) or replace it with a grahics card that uses dual DVI ports, such as the ATI 3870 HD. Of course, the latter means that you cannot connect two 24" Apple Cinema Displays.

Hum being caused by my Cinema Display 23

Similar Messages

Maybe you are looking for