Screen Capture won't capture window

Hello, I'm using Snow Leopard on a Mac Mini with a single monitor. When using the screen capture keyboard commands, I can do everything except for capturing a window. I'm supposed to be able to hit command+shift+4, and then spacebar, and the pointer will change into a camera that will capture only the window I click with it. I recall being able to do this a long time ago, before I upgraded to Snow Leopard. I also use a widget called Screenshot Plus that acts as a front-end to those keyboard functions.
When I try these days, the cursor changes into a camera, but the entire screen is highlighted as if it will be selected. When I click, what gets captured is a blank white area the full size of my screen. The Screenshot Pro widget produces the same incorrect result.
I've seen another discussion about this topic, but it seemed to center on the Grab utility. On my system, Grab works correctly, including the window capture function. So I have a way to get the results I want, but I would be interested in a solution that allows me to use the keyboard method again. Thank you.
Mike

Noondaywitch, I created a test account and screen capture of windows worked correctly in it. Thank you!
So now I need to look for something about my account. I'm going to try disabling all startup items and see what happens.
UPDATE: Disabling all startup items and rebooting fixed the problem. The window capture function now works in my user account. Now I can put startup items back one by one to see which one might have caused the issue.
Thanks to all who gave advice.

Similar Messages

  • Image Capture won't capture (Canon 9950F)

    I have recently bought a Canon 9950F for a specific project. It replaced an Epson Perfection 2450 Photo which worked perfectly but was limited in the size (area) of its film scanning capabilities. I have used a range of software including VueScan and Silverfast v6.6 but the most direct scanning tool I have used is Image Capture. The feature that I really like with Image Capture is the ability to select multiple scan areas in the 'preview' and have Image Capture scan them as a batch. The project I am working on (family archive photos, documents and film negs of various formats) really makes the most of this feature.
    I have moved over to the Canon 9950F and immediately noticed that Image Capture does not see the film scanning feature of the 9950F. It scans documents exactly as the Epson 2450 did but does not offer the option of scanning film or transparency, only documents on the flatbed. I have updated the Canon Drivers and the scanner is visible under System Prefs > Printers. VueScan and SilverFast recognise the scanner (but neither have the selectable scanning feature that Image Capture offers) and Photoshop Elements 10 also sees the scanner under File > Import.
    Has anyone experienced this problem and, if so, is there a 'work around'.
    Many thanks.
    iMac 24", Intel Core 2 Duo, 3Gb RAM, OS10.6.8,

    Thanks PAHU that were a lot of drivers for sure in your link and I installed those. Unfortunately, nor the driver package nor the ICA driver did solve my problem. I'm beginning to think it might just be a bug within Image Capture, although Image Capture is stating the scanner is reporting an error. Strange thing is that Image Capture will work fine as long as I hide the details pane.
    It seems to be an isolated problem too as I can't find any other subject on this on the net. I see more people having trouble to scan images with Image Capture but that's mostly related to not selecting the right part of the preview. I will see if I can reinstall Image Capture from the OSX dvd.

  • Help ! Batch Capture won't capture . FCP 5 & Kona 3

    When I select any offline clip and try to batch capture it - the machine seems to be working fine, cues up the deck at the start of the clip, rolls away - the capture screen appears but then everything just keeps rolling - ie it doesnt stop when it reaches the tc out point of the clip. I eventually have to abort and the offline clip remains offline.
    Capture Now on the fly works fine.
    This is a new G5 Quad running the latest OS with FCP5 capturing from a Digibeta PAL Sony deck with RS 422 control thru the AJA BOB to a Kona 3 Card. I havce full deck control as normal thru the Log & Capture window.
    Any help would be appreciated.

    Do you have the latest Kona drivers? What are you capturing to? What codec are you using?
    Patrick

  • K8T (MS 6702-020) Goes thru the boot screens, but won't load Windows!

    My computer was running fine and turned off normally the last time it worked. The next time I tried to turn it on it would go thru the boot pages, but as soon as the Windows screen came on the computer reboots. It won't boot in "safe" mode or from CD either. I have exhausted my knowledge and need some help to determine my problem.
    I definitely could have missed something or did something wrong in what I have tried, so starting from the beginning on any troubleshooting would be appreciated.
    Thanks for any help.
    Xtech69

    Hi Henry;
    Thanks for getting back to me.
    Sorry it took me a few days to answer you, but I caught a cold and it laid me out flat!!
    I put together as much information on the system as I could find. It is:
    Motherboard:   MSI  K8T Neo-FSR  K8T800  P/N 601-6702-020      VT8237
    CPU:        Athlon  64  3400+   w/ cooler   (runs about 120 degrees)
    Memory:     2X Ultra ULT30215  512MB   400Mhz   DDR
    Bios:        AMI  Ver. 3.31a
    Video:     ASUS  AH3450
    Hard Drive:     120GB  WD1200JB-75CR   (Primary Master)
    Lite-On      DVD-R/W   IDE      (Secondary Master)
    ??        CD-R/W   IDE      (Secondary Slave)
    Iomega     ZIP-100   IDE      (Primary Slave)
    ??        1.44 MB   IDE Floppy  (A)
    It's all standard configuration.
    If you need more, just let me know how/where to look and I'll do my best to find it.
    Xtech69

  • MDT 2013 won't capture 8.1 image, does not boot to PE to capture

    I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
    I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings  to make things easier and created
    a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it. 
    In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
    instead of windows PE to capture the image. 
    I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
    Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either. 
    In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
    After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files. 
    rules for the capture share
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with. 
    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Thanks for your reply. 
    The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
    domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch. 
    After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
    I deleted the task sequence and created another one with "sysprep and capture" as the sequence.  i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load. 
    if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
    this error when loading windows 8
    "windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again. 
    Haven't had any issues with that VM until now. 
    I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
    it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
    that removed most of them and customizes the start screen and those seem to work without issue. 
    found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
    Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
    and
    Resolution
    The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
    Import-Module Appx
    Import-Module Dism
    Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
    if i run that i get a lot of 
    [unknown user]: installed
    Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
    I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
    Heres an overview of what I do [i am open to some revisions on this]
    -deploy windows 8 base install from MDT
    -join domain, login with service account [just makes getting to some things easier]
    -install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
    -install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
    -connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
    -install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
    -install adobe reader/java [i do understand that these can be set as an MDT app]
    -leave domain, reboot, login as local admin
    -clean domain profiles/registry guids
    -make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
    -install our AV network agent
    -lite touch. 
    any advice is appreciated

  • FCP runs on Intel Mac Mini, but won't capture to external drive, HELP!!

    Installed FCP 5.1 on Mac Mini Core Duo and it runs fine. It will capture fine too, but only to the main harddrive. If I plug in a firewire harddrive using a firewire hub it won't capture, and give a "No Video" error in the Log and Capture window. I've used both popwered and unpowered firewire hubs, and even tried daisy chaining the camcorder off the harddrive. Nothing has worked. And there is no space on the main harddrive to capture to.
    I know there is a lot of speculation about whether FCP would even run on a Mini, but it will. If only I could capture it would be a reat capturing station. Has anyone had success? Its pretty frustrating as I've used the Power PC Mac Mini for capturing in FCP 5.0 without any problems. Why would apple make the new Mini crapier?

    Never use FW hubs when capturing video. They only lead to grief.
    Some cameras, particularly Canons, refuse to share the FW bus with anything. Could this be your problem?
    If so, there is little I can think of to do with a Mini (or an iMac for that matter) beyond capturing from a different deck/camera that is more social than the Canons and their brethren. You only get the one FW bus.
    But first thing to try is to get rid of the hub. Hook your fw drive to the computer and your camera to the FW drive.
    Post back,
    Patrick

  • FCP runs on Intel Mac Mini but Won't capture, HELP!

    Installed FCP 5.1 on Mac Mini Core Duo and it runs fine. It will capture fine too, but only to the main harddrive. If I plug in a firewire harddrive using a firewire hub it won't capture, and give a "No Video" error in the Log and Capture window. I've used both popwered and unpowered firewire hubs, and even tried daisy chaining the camcorder off the harddrive. Nothing has worked. And there is no space on the main harddrive to capture to.
    I know there is a lot of speculation about whether FCP would even run on a Mini, but it will. If only I could capture it would be a reat capturing station. Has anyone had success? Its pretty frustrating as I've used the Power PC Mac Mini for capturing in FCP 5.0 without any problems. Why would apple make the new Mini crapier?
    Intel mini core duo   Mac OS X (10.4.6)  

    I would recommend you post your topic in the Final Cut Pro forum. However, since the Intel-based Mac mini is not supported, it may simply not work.
    -Doug

  • 5.1.2 Won't capture from DSR-11

    I performed the software updates last night; should've checked the reviews on this one first. Today, FCP won't Capture Now from my DSR-11. The capture now screen comes up black with the apple logo. Underneath it says, "Waiting for timecode. Device must be in VTR mode when Device Control is enabled." I hit escape. The device is being controlled by FCP because I am able to rewind the tapes using the computer. As far as I can tell, the DSR-11 is in VTR mode. I tried switching the device control to firewire basic, but no change. I switched it to non-controllable device and that does work, but is a pain in the neck. Can I switch back to 5.1.1?

    Here's what I did:
    The tape was partially used. I rewound a bit and got a time code of 15:45:01. I used that as the out point and typed in 100 as the in point. I rewound the tape and logged the clip offline. I then tried to batch capture the clip and received the following error:
    Batch Capture: Timecode Error: Unable to located specified timecode. You may have specified a timecode with insufficient room for a pre/post roll operaation.
    What did I do wrong?
    FYI, I did the quicktime fix suggested on another thread, which did nothing for me. What I did was trash old packages of QT from the library/receipts. Then I reinstalled QT.

  • PD170 Won't Capture

    Looks like I made a fatal mistake and bought a camera off of Ebay.
    Oh dear.
    Not only does it have the audio humm problems early PD170's have, it won't capture in.
    On the menu selection I notice the option is for A/V - DV OUT ON or OFF. It says nothing about DV IN.
    Do I have a PD170 with no DV-IN?
    I can capture okay from the camera to Final Cut, but when I try to output - I get nothing. Just the standard blue screen on the PD170.
    What now?

    Your subject line might get more traffic if you used the term record instead of capture. We generally use "capture" when going into the Macintosh.
    You need to find a Sony forum. There are lots of 150/170 users here, true, but the wonk level is likely to be higher on a product-oriented forum--of which I know none.
    Hope you get it fixed, hope it's a simple glitch.
    bogiesan

  • Image Capture won't scan: Canon MP 610

    Hello,
    I experience a strange bug in Image Capture which I use together with my Canon MP610. When I put a document on the scanner Image Capture will show a preview and then scan the document. This works fine.
    Sometimes I need to make some manual corrections by using the button "show details" and then resize the scan area after the program has analyzed the picture. After I made the corrections I hit the "Scan" button but Image Capture will return with the message "Scanner has reported an error" and "An error occurred during scanning".
    I first thought it might be a driver related problem as I recently updated the drivers from the Canon site. Before I installed the Canon drivers and used the OSX drivers all worked fine.
    So I removed all drivers from Canon and hoped the Mac would use the old drivers again. That didn't work either as the system couldn't seem to find any usable driver anymore. I reinstalled the Canon drivers and all works well again except for the Image Capture program.
    As long as I don't use the "Show Details" button the scanner works just fine. But as soon as I make some manual corrections the scanner error message pops up and the scanner won't scan the adjusted preview.
    So I know for sure the Mac sees the scanner and can control it as the scanner does deliver the images to the folder I specify, but I can't do any manual corrections.
    I already deleted the file "com.apple.ImageCaptureApp.plist" but that didn't solve the problem. It appears to be a bug in the program itself or a conflict between the app and the drivers from Canon. How can I revert back to the drivers that my Mac used before I installed the Canon drivers?
    Thanks!

    Thanks PAHU that were a lot of drivers for sure in your link and I installed those. Unfortunately, nor the driver package nor the ICA driver did solve my problem. I'm beginning to think it might just be a bug within Image Capture, although Image Capture is stating the scanner is reporting an error. Strange thing is that Image Capture will work fine as long as I hide the details pane.
    It seems to be an isolated problem too as I can't find any other subject on this on the net. I see more people having trouble to scan images with Image Capture but that's mostly related to not selecting the right part of the preview. I will see if I can reinstall Image Capture from the OSX dvd.

  • Image Capture won't recognize camera under other user log in

    Image Capture won't recognize cameras under another other users log in on the same computer even though it works perfectly under the main user log in. Can some body hep me pleeze? What am I doing wrong or how can I let my daughter use her digital camera under her log in?
    Power Mac G-5 Dual 1.8   Mac OS X (10.3.9)   80gbMaindrive,250gbSeagate/1gb ram/128mb vram

    Hi G-Man,
    It's probably something in the Preferences folder; Users/herusername/Library/Preferences. Start by removing com.apple.ImageCaptureApp.plist and trying again. If that doesn't do it drag the entire Preference folder to the desktop, log out and back in. Launch it again and if it works you can either reset preferences for all System Preferences and apps or drag the preferences files a group at a time back to the new Preference folder in Library and test Image Capture each time. That way you can narrow it down to the one offending preference file.
    John

  • Image capture won't recognize my ScanSnap iX500.  How do I make them work together?

    Image capture won't recognize my ScanSnap iX500.  How do I make them work together?

    To use Image Capture you need an ICA driver for your scanner. Checking the Fujitsu web site for drivers for the iX500 I only see a ScanSnap manager for OS X. No mention of an ICA driver. So you may need to contact your local Fujitsu support.

  • How do i change the resolution of my screen shots that i captured from my desktop?

    How do i change the resolution of my screen shots that i captured from my desktop?
    Thanks.

    Do you mean you want it saved with the resolution set to something other than 72 dpi when the capture is made, or do you mean you want your capture saved at a higher resolution than the captured area?
    1) If the first, there are ways to change the default capture format .png to something else, such as .jpg, .tif and a few others, but as far as I know, the resolution will always be 72 dpi. You can use Preview to change the resolution of the captured image under Tools > Adjust Size. You will get this:
    If your intention is to set the resolution for professional printing defaults, then change the resolution to 300. Turn off Resample image to prevent the image from actually having more pixels added. The resolution will simply be reset from 72 to 300 dpi without changing the actual number of pixels in the image. It will also print a lot smaller since the output device will now use 300 pixels per linear inch instead of 72.
    Leave Resample image on if you need to maintain the dimensions. Be aware however that scaling the image (resampling) will add a lot more pixels to the image than are there to maintain size. Expect the image to get very soft and pixelated looking when adding 417% more data to the image than it currently has.
    2) If you mean you want the OS to actually save the captured area as a high resolution image at size, that can't happen. A capture is a 1:1 grab of the display buffer. It can only capture what's there. So if you capture a 700 pixel x 500 pixel area, that's all the bigger it can be without scaling it afterwards.

  • Premiere Pro CS6 won't capture HDR-HC3 properly

    In HDV capture mode it wants to assign an mp3 extension.
    Doesn't capture in native M2t format.
    Tried reinstalling. Haven't had this problem with previous versions.
    ver. 6.01

    I've used numerous programs over the years so on the off chance I'm mistaken about whether Premiere Pro captures Sony HDV in m2t or mpeg, I'll take your word for it. However, you're not addressing the real problem which is that it won't capture my Sony HDR HC3 video, period, in any format. It wants to create a file with an mp3 extension and won't import the files it captures even if the extension has been changed to m2t, mpg, or mpeg. I may not be sure about the extension previous versions have captured in, but I'm 100% certain that it did capture it.

  • Won't capture

    HELP!!!!
    Machine Name: Power Mac G5
    Machine Model: PowerMac7,3
    CPU Type: PowerPC G5 (3.1)
    Number Of CPUs: 2
    CPU Speed: 2.7 GHz
    L2 Cache (per CPU): 512 KB
    Memory: 8 GB
    Bus Speed: 1.35 GHz
    Boot ROM Version: 5.2.4f1
    Maxtor SATA Ultra16 500GB 720RPM 16MB CACHE Serial ATA/300 internal Hard Drive Mac OS Extended (Journaled)
    Fire Wire from Sony DSR-25
    Yesterday I was batch capturing for the first time in about a year and after capturing realized that I hadn't set my capture settings to the right location. I moved the captured files to the location that I wanted and reset my System Settings properly. After I did this I tried to recapture one of the clips that failed to capture the first time. A blank grey screen covered The Log and Capture Screen and I got an I/O error message. I tried other clips from different tapes and got the same result.
    These symptoms appear in all projects:
    Viewer and Canvas screens are green.
    Random multi-colored blocks on video in Viewer.
    No video will come into the timeline and audio is corrupt.
    Grey screen overlays Log and Capture Screen when trying to capture, spinning ball stays on forever
    and then I have to force quit FCP
    Things I've tried:
    Turned off computer, disconnected all peripherals, waited about 30 minutes
    Trashed Prefs.
    Reinstalled FCP
    Tried playing captured files on QT player and it works fine. The original capture files are not corrupted.
    Repaired Permissions on my Mac HD.
    Tried to Repair Disk on my Maxtor but got "Repairing disk failed with error Could not unmount disk."
    Could the problem be that my FCP application is on my Mac HD and all of my project files
    including capture files are on my Maxtor HD?
    I've had it this way for about a year and everything has worked all-right until now.
    I tried copying FCP to the Maxtor but got "The alias "AEProfiling" cannot be copied to the destination,
    perhaps because the destination does not support this type of alias."
    Any input would be greatly appreciated.
    Thanks.
    Michael Hamilton
    PowerMac7,3   Mac OS X (10.4.8)   Power Mac G5 CPU Type: PowerPC G5 (3.1) Number of CPUs: 2 CPU Speed: 2.7 GHz L2 Cache (per CPU): 512 KB Memory: 8 GB Bus Speed: 1.35 GHz

    Go up to FCP 5.0.4 via software upgrade... but it may not help. As a side note, I'd also crossgrade to the universal version... it's a whole software cycle upgrade from where you are now, and it's a bargain. The deal is over after Dec 20 too so you need to do this right away... It's better software all round... bug fixes, and even some new features.
    Canon cameras' TC recording is suspect if you ask me, and you may well have to dub the tape via firewire to the Sony deck from another DV camera or deck to laydown a decent TC track. If so, regenerate the timecode on the deck, don't slave it. Also I'd record DVCAM instead of the consumer tape format you've got from that camera. Better TC, and Better audio sync lock.
    You might be able to get past this if you can live with bogus timecode on the clips.... use "non controllable device" as the device control, and then just use capture now after you start rolling the tape manually from the DSR. BUT it will not record the correct timecode, with all of those ramifications... i.e. no recapture getting the same timecode etc...
    Jerry

Maybe you are looking for