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.

Similar Messages

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.

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.

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

Image Capture won't scan to Photoshop

I just downloaded Lion (10.7.2) and everything works fine, except ...
When scanning through Image Capture, it won't open the scanned images in Photoshop (CS4) when set to do so. It will open in any other program I try (Preview, Illustrator, etc ...) but not Photoshop.
When I scan an image with PS set as the "scan to" app, Photoshop will open, but it doesn't open the image. Instead, Image Capture opens a "scan results" dialog box with the name of the image and a magnifying glass icon that shows me that the image has been saved in my "pictures" folder. I'm clearly choosing the PS app, and not the PS folder in Image Capture, but for some reason it doesn't know what to do with the image when it gets there. Again, the PS app OPENS, but the image doesn't. It just dumps it in the "pictures" folder.
By all accounts, Photoshop seems to be working properly. I can click on a scanned image and open it with Photoshop manually. Scanned images just won't open in PS automatically through Image Capture like they used to before I upgraded to Lion.
I tried rebooting and repairing permissions just for the heck of it, but those did nothing. Image Capture has no problem recognizing my scanner (Brother MFC 6490CW) and I made sure to download the latest driver for it.
I'm really at a loss as to why this is occuring. If anyone has a theory, I'd love to hear it. Scanning stuff into Photoshop is my job basically, so this is driving me crazy.

I can duplicate that behaviour, best file it as a Bug with Apple if you have a Developer ID ?
http://developer.apple.com/bugreporter/
I will file it also and see what response I get.
BR filed: I note that in testing this if I set the Import To selector to Preview, Mail and iPhoto it behaves as expected so it's possible this is an Adobe issue not an Apple one. Might be worth looking in their support forums to see if anyone elase has this and has found a work-around.

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.

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

SCCM won´t capture image after ZTIWindowsUpdate

Hi!
We are running SCCM 2012 R2 and are using ZTIWindowsUpdate.wsf
to update our images.
Now we are having trouble that the image doesn't get captured after we have ran
ZTIWindowsUpdate.wsf in a Build and Capture OSD.
This is the last entries from ZTIWindowsUpdate.log:
More to install, Please reboot and run again!
ZTIWindowsUpdate 2015-04-09 16:38:27
0 (0x0000)
Property SMSTSRetryRequested is now = true ZTIWindowsUpdate
2015-04-09 16:38:27 0 (0x0000)
Property SMSTSRebootRequested is now = true
ZTIWindowsUpdate 2015-04-09 16:38:27
0 (0x0000)
ZTIWindowsUpdate processing completed successfully.
ZTIWindowsUpdate 2015-04-09 16:38:27
0 (0x0000)
Running ZTIWindowsUpdate.wsf is the last step in the Task Sequence before the capture.
There are 41 updates and according to the log they all get installed properly.

The link Torsten supplied is the best place to start. Make sure you are not installing any updates that require multiple reboots. You can exclude those updates using something like this:
https://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
Jeff

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

FCE: Capturing footage from my Canon XL1

Got FCE and when capturing footage from my Canon XL1 I get the video however there is no audio!
Tried capturing footage via iMovies and works no problem!
Not sure if this has anything to do with it but I'm using a external mic. on my XL1 into one ch. on the audio inputs. Also scratch disks is on a external 1TB WD drive. Finally tried virtually all the set-ups on the 'easy set-up' but still no joy.
Can anyone throw me a life line on this one?!

sorry I should have made myself abit clearer.....when the tape is played back in my XL1 I can hear audio when my headphones are pluged into the camera also the camera has audio monitors which I can see movement verifying there is audio. However in FCE I don't see any audio level movement.
In terms of equip. I just have a external WD 1TB drive (USB), firewire cable for video camera and the USB cable for the keyboard & mouse.
Additional application: Flip video s/w (however had fce issue prior to installing this).

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.

What type of firewire cables do I need to capture recorings from my canon xm2

What type of firewire cables do I need to capture recorings from my canon xm2

I have a:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2,4 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per core):          256 KB
L3 Cache (per processor):          12 MB
Memory:          6 GB
Processor Interconnect Speed:          5.86 GT/s
Boot ROM Version:          MP51.007F.B03
SMC Version (system):          1.39f11
SMC Version (processor tray):          1.39f11
Serial Number (system):          CK12002NHF8
Serial Number (processor tray):          J511400HYBH8C
Hardware UUID:          F51FCFBA-869D-5D70-A1F6-886A32871AA0

Photoshop won't open Raw images with my new Camera Canon 6D help! I use Photoshop CS5 extended version.

Hello,
I got a new camera and Photoshop and Lightroom won't open Raw images with my new Camera Canon 6D help! I use Photoshop CS5 extended version. and Lightroom 3

Good news and bad news:
The bad news is that you need CS6 or higher to open 6D RAWs. (The 6D didn't get support until Camera Raw 7.3; 7.0 premiered in CS6.) You can choose to upgrade (I'd recommend skipping CS6 and go straight for CC 2014 for $10/month) *OR*...
...the good news is that the DNG Converter can help you convert your RAWs into DNGs for use in CS5 and Lightroom 3.

Image Capture won't capture (Canon 9950F)

Similar Messages

Maybe you are looking for