Waking computer monitors from sleep causes FCP capture to fail

I'm having trouble capturing DVCam material from an HDV deck (in PAL), using FCP 6.0.3. As I'm doing a long digitize (several hours of material at a time), I like to put my monitors to sleep while capturing. Normally, this works fine (and hasn't caused any problems - I've been doing this for a long time). On this current project, every time I wake the monitors to check the progress of digitizing, it appears to cause FCP & cancel capturing the clip that it is currently capturing.
I've cleared out & reset all of my preferences, zapped the P-Ram, made sure that there is plenty of room on the USB 2.0 drive that I'm capturing the material to (it's a 1TB drive with about 850gb's of material already on it).
Does anybody have a suggestion for me about why waking the monitors would be throwing the capturing process out of whack?
Message was edited by: ZillaB

I've ... made sure that there is plenty of room on the USB 2.0 drive that I'm capturing the material to (it's a 1TB drive with about 850gb's of material already on it).
You're capturing to an 85% full USB2.0 drive ?? I'm betting that when you wake the monitor you're seeing an error ... but not because of the waking of the monitor! FWIW you should always try to keep your drives less than 80% full ... beyond that and you're asking for serious performance degradation. That and of course USB drives are wholly unsuited for video production with FCP. (FCP really doesn't like devices that cannot handle sustained data transfer).
That said, what monitor are you using? How are you putting them to "sleep"? How are you waking them? Exactly is the error that you are seeing .. or is there no error but the capture just stops? Do you lose all the footage captured to that point or do you at least keep the footage captured so far?

Similar Messages

Display Changes Resolution When Computer Wakes From Sleep

I have a MacBook Pro bought in May of 2006. In the last year, this problem has been getting progressively more annoying to me. When the computer wakes from sleep (not every time, but most of the time) the screen will flash blue, then reset the resolution to 640 x 480, I think. To fix it, all I have to do is go to System Preferences and change the resolution, but when I do that, it pops up two windows, like it thinks I have a dual display set up. To fix this, I always click 'detect displays,' and it fixes it, but the next time I wake the computer from sleep, it does it again. This isn't really an urgent problem, but I would expect my computer to behave a bit better for me.
Thank you in advance for any aid you might give me.
Lisel

Hi Lisel. I have a similar age MacBookPro that does the same thing. I don't really know how to fix it I'm sorry, I wish I did cause it's annoying. I just thought I'd let you know you're not the only one with this issue.
Basically, for some reason it thinks it has two displays connected, even when there isn't. To stop it being a total pain, make sure when it does come up with the two Display Pref windows to set them both to 1440x900, at least then when it does go dual display it won't be 640x480 and you can still read stuff.
I've also left the Display Pref icon on the top tool bar (next to the AirPort and Bluetooth and stuff), so I can just click that and Detect Displays. When it does that it figures out for itself it doesn't actually have two displays connected and so goes back to normal.
I know that's a workaround and not a fix, sorry. I'd be keen to know if anyone else has any better solutions:)
Thanks,
Mark.

Imac waking itself up from sleep mode

i am very concerned about my imac it keeps waking itself up from sleep mode. i checked the prefrences and its not scheduled to wake itself up, do i have a virus?

OK jon,
We stil don't know exactly which iMac CRT you have but this is based on the 350 - 400 Slot loader and is from the service manual:
"Resetting the PMU on the Logic Board
Resetting the PMU (Power Management Unit) on the logic board
can resolve many system problems. Whenever you have a unit that
fails to power up, you should follow this procedure before
replacing any modules.
1. Disconnect the power cord and check the battery in the battery
holder (BT1). The battery should read 3.3 to 3.7 volts.
If the battery is bad, replace the battery, wait ten seconds,
and then reset the PMU (refer to the next step). If the battery
is good, go to the next step.
2. Press the PMU reset switch (S1) once on the logic board and
then proceed to step 3. Do NOT press the PMU reset switch a
second time because it could crash the PMU chip.
3. WAIT ten seconds before connecting the power cord and powering
the computer on. If the computer powers on, go to the
next step. If the computer does not power on, there is something
else wrong with the computer, refer to the symptom/
cure chart, “No Power” in this chapter."
Richard

Computer Wakes From Sleep

My computer wakes from sleep (MBP 10.6.4). At the time my computer wakes (not exactly sure of this), a message in the Console reads "Focus[143] Screen parameters schanged". When I open the lid, the keyboard is lit-up, the screen is blank and the is no prompt for logging in. I have to hit escape, close the lid, wait until I see the computer sleeping, open the lid, then I can log in. I have a program on my Mac called Focus, could this be the culprit or is it something in the OS itself? Many times when this has happened, my computer fans are screaming and the computer is very hot. I have been eliminating many bugs from my system but this is one I need some help with. Thanks.

Focus certainly sounds like it could be the culprit. I would remove it from your account login items an test to see. You do this in System Preferences>accounts>login items tab. You'll have to unlock the preferences and enter your admin password and then select Focus in the list and hit the "-" button below the list.
The only other things I can think of are a bluetooth device waking your system or "wake on network access".

My desktop m8407c powers up, but will not wake monitor from sleep.

I have a pavilion desktop m8407c running vista 64 that turns the fan on and sounds like it is running, but will not alert the keyboard or monitor. It hums and powers up to some extent, but the hum does not stop or wake the monitor from sleep. I have tried unplugging and disconnecting everything, but it continues to do the same thing. Any help would be appreciated.

Hello sap22
Follow the steps outlined in the article below. Let me know if the problem persists.
Monitor or TV is Blank after Starting the Computer
Don't forgot to say thanks by giving "Kudos" to those that help solve your problems.
When a solution is found please mark the post that solves your issue.

I'm new to the MAC world. I turned my computer on from 'sleep' mode, and a window was up stating that the IOS disk was full; asked me to force quit, then it just froze. It's been 2 hours. Help! I'm worried about losing photos/videos of my children. Thx!

I'm new to the MAC world. I turned my computer on from 'sleep' mode, and a window was up stating that the IOS disk was full; asked me to force quit, then it just froze. It's been 2 hours. Help! I'm worried about losing photos/videos of my children. Im not sure if there's something special I need to do once I turn it back on; in the meantime, its still on... which I'm afraid the picture on the screen will burn into the screen. Does that happen on iMac's? Thx!

Try a hard reset. ( holding Power til it restarts)
Once to your desktop. Click the Apple icon >> About this mac >> More info>> Storage
Once you see what you have the most of. Try to see what you can delete.
Open up any folder>>all files>> or buy an external to store more data.
Once deleting make sure you empty your trash.
If you are new and its a new computer, you might need to bring it to a store for further assistence.
Coast Guard Mechanic w/ an Apple Problem

Audio volume low when computer wakes from sleep - os x yosemite

I've been having an issue ever since I upgraded to OS X Yosemite, where the audio volume coming out of my external speakers is extremely low after I wake my computer up from sleep. The only resolution I have found is restarting the computer. Once I do that, the audio volume is great. If I were to boot up my computer after it has been completely shut down, the audio volume is also great. The issue only occurs after sleep. Anyone else having a similar issue? Is there another fix besides restarting the computer?
Speakers: Bose Companion 2 Series II (these are wired, not bluetooth)
Computer: Mac Pro - late 2013 - running Yosemite

This is a BUG. It has been submitted to engineering many times - unfortunately Apple has not done anything about it.   We have 5 Mac Pros, all 5 do the same thing after updating to Yosemite.   The PRAM / SMC reset is useless - we even installed a fresh OS on one of the machines (a suggestion of the level 2 Apple tech) same problem.   Clearly this is a system level bug.   Only way to get it resolved is to keep pounding the bug report site with requests.     The squeaky wheel gets the oil.   The problem is 100% repeatable on the machines that exhibit the bug.
In the mean time set up an applescript with this command and it will reset the sound - do not include the brackets :
<do shell script "sudo killall coreaudiod" with administrator privileges>
Run it every time you wake from sleep and you won't have to deal with the problem ever again.
Pretty lame that Apple has not fixed it even though the problem appears to be pretty widespread.

I upgraded to Mountain Lion.Now I have trouble waking it up from sleep mode. Why?

I upgraded to Mountain Lion on my MacBook. I am now having trouble waking it up from sleep mode. Does anyone know why or how to wake it up. I try tapping the space bar, trackpad & other keys. Sometimes I think it's never going to wake up.

I'm not certain but my new MBA 13...when in sleep mode comes back on from a black screen when I simply click on the left mouse button. Also, one time I did a SECURE EMPTY TRASH on files that totalled more than 1GB and it took so long that the fan kept increasing in speed so I pressed on the POWER button and the MBA shut...I was able to boot up with no problem. As a rule, I now only do secured erases for trash bin data totalling 500mb or less...anything above that gets a regular erase (dump).

FireWire drive unmounting/disapering when computer returns from sleep

I have a problem since the latest software update 10.4.10
that my WD 500GB FW800 drive keeps unmounting/disapearing after
the computer returns from sleep, and subsequently issuing a unclean unmount message!
Toggling the drive power restores it and so far no data is lost... I hope..

Well, yesterday I decided to do some troubleshooting to confirm the source of the problem. I connected a different external hard drive using the same USB2 cable that I was using with the problematic WD Mybook. I performed flawlessly and showed no issues with not being accessable after the computer woke from sleep. Next I connected the same drive via Firewire 400. Also no issues. That seemed to confirm that there was a problem with the WD drive! However, just to be sure, I reconected the WD Mybook with the original USB cable and gave it another whirl. It has also been performing flawlessly for the past day!
Possibilities:
1 There was minor oxidation on the contacts of the cable or in the drive socket which gave a poor connection resulting in the problem. Removing and replacing the cable several times removed the oxide and restored proper electrical contact and drive operation.
2 Something in the WD Mybook firmware "reset" when it was unpowered for a few hours, also restoring proper operation. WD's website states that the Mybooks are able to remain in standby mode for long periods of time but that they recommend they be powered down when not in use.
It would be interesting to see if anyone else can confirm that their Mybooks begin to operate properly after "giving them an unpowered rest" or by cleaning the USB connections.
I know how to keep my Mybook operational for now, but I will likely have to ditch it when I move to a multi FW bus computer in the future (unless WD can correct their firmware).
Cheers

AIR event when computer awakes from sleep mode?

Hi,
I have an AIR app that displays a new set of photos every 12 hours. Some users are complaining that the photos are not refreshed after 12 hours if the computer had been in sleep mode over night.
At first I thought possibly the Timer was stopping when in sleep mode so I instead modified the Timer to execute every minute and just check to see if the last refresh was at least then 12 hours ago. This still did not solve the issue.
Is there an event dispatched I can listen for to detch when the computer awakes from sleep mode? Or if any one has any other suggestions.
Thanks,
Ryan

No answer till now. Better close it.

Screen flickers when computer wakes from sleep

O.k., so I also had this problem when I updated to 10.6.8, but it's still here in Lion.........
When the computer wakes from sleep, I get a single flicker along the bottom 1/3rd of the screen, then everything's o.k.
It's just annoying, that's all. I've backed out to 10.6.7 on 3 occasions, and the flicker disappears.
Anyone else having this issue?
I'm running a 2010 Quad-core Mac Pro with SSD and 27" Display.
Bob.

Update:
I've now been to the local Apple store, and tried their display Mac Pro/27" Cinema Display combo, and guess what.......the screen flickers on wake-up.
I asked the guy in the store about it, and he says "oh yes, I see that. No-one has noticed that before, I wonder if mine does it at home".
I tried the Mac Mini with 27" Cinema display, and the 27" iMacs, and they were o.k. (no flicker).
So, this only affects Mac Pro's running 2560 x 1440 resolution.
I've booked another call with Apple Support. No doubt they'll still tell me to take my computer in for testing, even though I've shown they all do it (the guy in the Apple shop suggested that, even though I demonstrated the flicker to him on the one in the shop).
I wonder how long this will take to get a software fix? Problem is, the Pro is not mass-market (like Macbooks and iMacs), so it may take an awful long time.
In the meantime, I'm sticking with 10.6.7.
Bob.

Can someone interpret this for me? It's a log of system activity that's waking my computer up from sleep, and it may be causing it to lose battery overnight.

I ran a code on terminal, and this is what I received. I'm not sure if it contains any vital information as to why my computer is losing battery overnight, but if it does could anyone help me? I'm running Yosemite 10.10.3
Thanks!

Hello TimmyCoogs21,
I may not be able to give you a direct answer on this. I am not sure of your familiarity with log files. PID refers to a Proceess ID. I am not sure which process has an ID of 94 that is causing you this non-sleep issue. Others have had similar issues in the past, i.e.The HIDD after could possibly mean it is some form of Human Interface Device. If you have a USB or something plugged into your mac at night, or a faulty hardware piece entirely. (These are just speculations)
Bluetooth drivers prevent system from sleeping in Mavericks - what's going on!?
Do not let the title fool you as he states that it is not a problem that is caused by bluetooth. Ultimately he sought support from apple, which in your case, I would do the same.
You could restore/refresh your system and see if this continues if not I would recommend seeking apple support.
I know this does not fix your problem, however I hope you find some help in it.
Cheers.

Problems connecting to Monitor after waking up MacBook from sleep

Hi,
I am experiencing a lot of problems connecting my macbook pro to external monitor once I put it to sleep. I have tried every options like setting up PRAM and all, but it just wont work. Sometimes the restart works and sometimes it wont. I am using a Samsung monitor. I have no idea what to do, as I keep on clicking Detect displays and it just wont do anything. Can anybody please help me as to how I can wake up my macbook from sleep and get it connected to the monitor. I have a mac keyboard and bluetooth mouse, but neither would wake the mac. I have change my bluetooth settings so that the mouse should be able to wake it up..

William Rivas wrote:
William Rivas wrote:
William Rivas wrote:
Linc Davis wrote:
Test after taking each of the following steps that you haven't already tried. Back up all data before making any changes.
1. Make sure the network is on the preferred list by following these instructions. It's important to read the article carefully, as it's the starting point for any further efforts to solve the problem. If you skip any of the steps, the problem may not be solved. Make sure the box marked
Remember networks this computer has joined
is checked.
2. Follow the instructions in this support article under the heading "Symptom: The network connection drops unexpectedly."
3. Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.
4. From the Location menu at the top of the Network preference pane, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Wi-Fi service with the same settings you used before. Click Apply and test.
5. Launch the Keychain Access application. Search for and delete all AirPort network password items that refer to the network. Make a note of the password first.
6. Repair permissions on the startup volume.
7. Turn off Bluetooth and test.
8. Reset the System Management Controller.
9. Reset the PRAM.
10. Reinstall OS X.
Updating to 10.9.2 did the trick. So I thought. Does anyone have a solution?
Thanks!

Not detecting external display after waking up MBP from sleep mode

I am a recent owner of a MBP and enjoying it. However, one problem that I can't seem to find a solution to is the external display problem after sleep mode.
When I first boot up the Mac and plug in my Dell external monitor via the mini adapter, there is no problem with detection or display. However, every time I put the MBP in sleep mode and then wake it up again, the external monitor does not "wake" up and my MBP only displays my normal screen on the Mac.
I tried to 'Detect Displays' to no avail and the only solution is unplugging the mini connection and plugging it back into the MBP for the MBP to re-detect the external monitor.
Although this is a quick fix in itself, I do not want to wear out the mini port by doing this every timeI come out of sleep mode. Any solutions so that the external monitor will detect the MBP waking up from sleep and display properly? Thanks!

And same problem here.
Using a MBP 2.66 i7 with a Dell 3008WFP that's connected to the MBP through DisplayPort. It works some of the time but once in a while (only been using the new MBP for a couple of days now) the monitor won't come out of sleep mode. Turning it off/on causes OS X to completely ignore the monitor. I was able to get this setup to work again by pressing 'Detect Displays' in the System Preferences pane but most of the times that doesn't help. The only sure way to get the monitor working again is by booting into Windows through Bootcamp, Windows is able to use the monitor, if I reboot after that OS X sees the monitor again.
Also saw a magenta line/stripe on the left side of my monitor and the monitor sometimes makes a buzzing sound when connected to the MBP through DisplayPort. That's what you get by using bleeding edge tech I guess :\ Only alternative is buying the mini-DP to dual-DVI connector but paying $99 just to be able to use an external monitor is rather insane. Besides that lots of users are having problems with this adapter.

10.4.7 kernel_task eats 70% of CPU only when computer wakes from sleep.

On my machine (FW 800), 10.4.7 caused: machine to slow perceptably after wake from sleep. Activity Monitor tells me kernel_task is consuming hundreds of times it's normal CPU cycles.
I installed a FRESH 10.4. Imported my files and folders. Upgraded all the Apple software EXCEPT 10.4.7 combo updater. The partition worked fine, before and after sleep. Upgraded using the 10.4.7 combo updates.
Again, kernel_task consumes 60-70% of CPU cycles after my Mac wakes from sleep. Note that it works fine when first rebooted.
As slow as it was, it was unusable. I reverted to 10.4.6 to get work done.

I have the very same problem on the same platform, except that I have 2 int. bootable disk drives. One boots 10.4.6 and has no problems at all. The other Boots 10.4.7 and operates perfectly, as far as I can tell from a few hours of use. It will continue to work just fine until I put it to sleep. On awakening, the Kernal Tasks CPU Usage jumps to 55% - 75% and does not decrease any further (ever). Restart or Shutdown restores perfect operation after reboot (but don't let him fall asleep).
I have repeated this dozens of times, with identical results.
The update was performed by the book. External devices disconnected, permissions repaired, disk verified by Disk Util. and DiskWarrior and the 10.4.7 combined update was used. Permissions and Drive Verif. was repeated after sucessful install. In my case, no other apps were effected. No Sys Errors were logged, No crash events, no Kernel Panics.
There are thousands of Sys Config combinations involving both hardware and sotware. This looks like a flawed release on this hardware. "Updater Beware", especially the first month after a major release like this. Look for a fix very soon.
Even so, the people at Apple have done extremely well over the last few years.
I know, because I work with a dozen or more Generic PCs and there has never been a trouble free update from the other side.
Having a second internal hard disk with identical OS and applications is like having a second computer in the same case. It is also a good idea to use backup software to auto-sync your user files in realtime. You can boot from one while repairing the other etc.

Waking computer monitors from sleep causes FCP capture to fail

Similar Messages

Maybe you are looking for