Unable to Initialize Capture Device

Hi,
I am having a problem importing/capturing HDV video from my JVC HD GR 1 getting "Unable to Initialize Capture Device".
I have been able to capture fine up to this point, finicky some times to be sure, but workable, then in the last few weeks it began getting more and more finicky (wouldn't connect to camera, restart and it works fine), until just the other day it wont connect no matter what I do!
Help?
Ask questions if you need clarification.
Camera: JVC HD GR 1
Tape: Mini DV
Format: HDV
Software: FCP 5.1.4

Unfortunately when both "Capture" and "Device Control" presets are not set to HDV it wont even try to connect and gives me this warning:
"To capture HDV source material, both the Capture and Device Control presets must be configured for HDV; otherwise, to capture in another format, both must not be configured for HDV."
As a side note when my camera was connecting to FCP. FCP would only give me on screen controls half the time.

Similar Messages

5.1.4 update breaks HDV capture? Unable to Initialize Capture Device

Problem:
Final Cut Pro cannot capture standard 1080i60 HDV footage from Sony FX1 camcorder. FCP reports "Unable to Initialize Capture Device" when the log and capture window is opened. However, the footage CAN be captured in iMovie (which is interesting, and unacceptable). When HDV>DV downconvert option on camcorder is activated, footage CAN be captured as anamorphic SD, so the camcorder and FW do work.
The problem is occuring on a rock-solid FCP system that I use on a regular basis (mainly for SD editing). It has been approx 2 weeks since I last attempted a HDV capture, the system has been working great with SD footage (still does).
Factors that have changed to my knowledge since HDV capture was last functioning properly:
*Added a new external FW drive into regular usage (a different brand than normally used, no issues with it so far).
*Updated FCP to 5.1.3, and then 5.1.4 when that fix came out. All SD captures and work have been fine so far.
Here's what's interesting...I had a copy of the FCP v5.0.4 .app that I had saved an archive of prior to the crossgrade update. Guess what? I can load it up, and it captures HDV without any problems! With that in mind, this looks like an FCP 5.1.4 issue. But I am at a loss on how to proceed further in troubleshooting. Many thanks in advance for any assistance.
Matt Jeppsen
FresHDV.com
---NOTES---
What I have tried:
*Attempted capture with a different Sony FX1 camcorder.
*Swapped firewire cables and system firewire ports.
*Attempted capture with camera FW chained to an external HDD.
*Unplugged all other external firewire devices from the system.
*Trashed FCP prefs using FCP Rescue 5, created new project using Easy Setup (for HDV).
*Tried different variations of FCP A/V settings, tried all the HDV FW device control presets and the HDV AIC capture preset.
*Per instructions at http://docs.info.apple.com/article.html?artnum=301852 I removed the numbered Quicktime pckg Receipts and re-installed the latest version (7.13). Post-install/reboot, I repaired Disk Prefs and Verified the disk using Disk Util.
*Have also attempted installing QT 7.13 2 and 3 times in a row, also trying disk prefs repair BEFORE the post-install reboot.
Final Cut Pro Audio/Video Settings:
Sequence Preset: HDV-1080i60
Capture Preset: HDV
Device Control Preset: Sony HDV Firewire
Sony HDR-FX1 IN/OUT REC settings:
*VCR HDV/DV: HDV
*COMPONENT: 1080i/480i
*i.LINK CONV: OFF
*TV TYPE: 16:9
*A/V->DV OUT: OFF
System/Software Facts:
*Final Cut Pro 5.1.4
*Quicktime 7.13
*PPC Mac G5 2.7 Dual (2.5GB RAM)
*35GB free on System, 45GB free on internal FCP Scratch disk
Final Cut Pro 5.1.4, G5 DP 2.7 (PPC) Mac OS X (10.4.8)

I think I figured out this vexing problem. I too was having the same issue. Check to see that your Quicktime is newer than 7.1.2. If it isn't you'll have to upgrade it. I only upgraded to 7.1.6 here because I was afraid of going to a really new version. http://www.apple.com/support/downloads/quicktime716formac.html. After I upgraded my quicktime, I ran software update and the Final Cut Pro 5.1.4 update appeared. I hoipe this helps.

Unable to initialize capture device and device control in HDV

I shot with a Sony HVR-Z1U/Z1N and am using a Sony HDV 1080i tape deck to digitize.
I recently purchased a MacBook Pro and installed FCP Pro 5 on it. After getting over some time code issues we were chugging along, when on the 4th tape the image on the log and capture screen suddenly dissapeared (I could get audio and could see the image on the tape deck). Well after taking the tape out, checking and rechecking it I popped it back in and ever since then, I have been getting this error mssg "Unable to initialize capture device and device control."
I have tried deleting the preferences and starting from scratch. If I do that, and choose the easy setup with HDV- 1080i60, it gives me this error "Unable to locate the following external devices- HDV (1440 X 1080) 30fps.
I upgraded to FCP 5.1.2 this morning and upgraded the OS to 10.4.7 and QT to 7.1.3 and still no change.
Im at my wits end, Ive been working on this for a whole week now.
Thank you,
Bugs

It has been reported to take more than one attempt to correct the installation but, if properly executed on a machine without other system problems, the QT reinstall process does work. The key element here is you must reinstall QT after you trash the receipts. The process is listed below.
x
To do a full quicktime reinstall.
Go to /library/receipts and delete any files that say Quicktime followed by a number e.g. Quicktime703.pkg
Go to the Apple quicktime site and download the appropriate version of Quicktime to your hard drive.
Run the Quicktime installer.
Repair Disk Permissions for your System Disk (Disk Utility > Select the system disk > Repair Disk Permissions)
Reboot
If this doesn't work, then the problem lies elsewhere:
1. your system - user preferences, firewire ports or other system elements.
2. your equipment - camera/deck/firewire cables.
3. your process - not setting up the software properly or using the software erroneously.
Listed below is a troubleshooting process. Not all steps are appropriate but the general process of isolating the problem is useful.
Troubleshooting Steps for OS X
by Jan Johannsen (Collected from: Apple>User Tips Library>User Tips Contributions forum)
FIRST AID
01 Completely shutdown, wait a 5 minutes, restart
02 Make sure you're not running out of free space on the System volume
03 Check/fix the filesystem using Disk Utility &/or Diskwarrior
04 Repair permissions using Disk Utility
05 Create a new user account, and see if the problem persists there
06 Clear system & user caches
07 Run FCP Rescue
08 Unplug all USB, Firewire devices except Apple mouse
09 Startup in SafeBoot mode, and see if the problem persists there
10 Reset system firmware
MORE SERIOUS TROUBLESHOOTING
11 Reapply the latest combo updater
12 Run the Apple hardware diagnostic CD
13 Check the hard drive for bad blocks
14 Take out 3rd party RAM
15 Unplug 3rd Party PCI cards
16 Reset PMU
17 Archive and reinstall the OS
18 Reinstall the system from scratch
19 Send the machine back to Apple

Unable to Initialize Capture Device - Works fine in iMovie

Am using a Sony HDV HDR HC1E Pal Handycam
Final Cut Pro 5.1
QT Pro 7.1.3
Works fine with cassettes in HDV - imports into FCP fine
Am trying to import a cassette recorded on that camera in DV LP
Works fine in iMovie
Have deleted the QT packages and reinstalled QT
Still am getting the 'Unable to Initialize Capture Device' message when using log and capture.
Settings on camera
VCR Auto (have also tried HDV or DV)
iLink conversion off (i.e.don't convert hdv-dv)
TV type 16:9 (have also tried 4:3)
Component 1080i/576i also tried 576i
Annoying thing is that works fine in iMovie but not FCP?!!
Any help GREATLY appreciated!
Thanks!
Hannah
iMac 20 Flat Screen G5 1.8Ghz 1.5GB SDRAM Mac OS X (10.4.8) 200 GB and 120GB External Hard drives

I would like to add the following in hopes that someone will come up with a solution. The problem lies somewhere in Quicktime and the FireWire capture. I have the exact same camera and problem, and can assure you it has nothing to do with cam settings or DV LP. Once your system is stuck in this HDV mode, it would seem that regular DV can not be used again. I also have 2 other DV cams that are not HD. One is PAL, one is NTSC. I would further add that my external FireWire iSight no longer works in any application. I do not receive error messages, I simply get the spinning beach-ball of death.
I have a Dual G5 2.7 with 4 gigs RAM running FCP 5.0.4 on OS 10.4.8
I have run Cocktail, rebuilt permissions and re-installed Quicktime 7.1.3 four times as per Apples tech article 301852
I have used FCP Rescue 5 to clear preferences
I have captured footage from both regular DV cams to iMovie and then added the footage to FCP. The footage plays on the screen of both DV cams flawlessly via FCP. (I can also capture HDV in iMovie as well)
I have tried logging footage directly through the QuickTime application with both DV cams and my iSight and get the same beach-ball of death as FCP.
Why can iMovie work with these devices flawlessly yet QuickTime can not.
Why does it seem like the system is stuck in some kind of HD mode.
Just to point out the obvious:
I have no other FireWire devices other than the cameras and I only connect one at a time.
I have shut down, disconnected and re-connected before attempting to use the devices.
I have booted my G5 from a second system disk and everything (HDV cam PAL DV cam NTSC cam and iSight) function flawlessly on all the FireWire ports of my machine.
I have worked with FCP for about 6 years and Macs for 20. I understand the easy set ups etc.
Spent way too much time customizing my system to think about the clean install route, so I hope someone can shed some light on this.
Thanks
Lorne
PowerMac Dual 2.7 GHz PowerPC G5 4 GB DDR SDRAM 400 GB and 250 GB Internal Drives Mac OS X (10.4.8)

Couldn't initialize capture device on linux Ca

I have installed j2sdk1.4.2-02 and jmf 2.1.1e on linux.When I started jmstuido ,jmstudio found "video capture device ":Name=v41:OV511+USC Camera:0
Locator = v41://0 and support Output Format :four kinds of YUVFormat .
audio capture device :Name=JavaSound audio capture
Locator = javasound://44100 and support Output Format :seven kinds of AudioFormat LINEAR.
But when I open file->capture ,video display OK and audio display error :"controller error ! failed to prefetch: cann't open audio device."
when I open file->transmit , I want to transmit video not audio and the monitor display OK but the other side cann't receive video.
I write some codes :
     DataSource dsvideo = null;
     Vector deviceList=null;
     CaptureDeviceInfo di = null;
     MediaLocator ml=null;
deviceList = CaptureDeviceManager.getDeviceList(new VideoFormat(null));
if (deviceList.size() > 0)
di = (CaptureDeviceInfo)deviceList.firstElement();
else
System.err.println("System has not video device!");
System.exit(-1);
ml=di.getLocator();
DataSource ds=null;
try
ds = Manager.createDataSource(ml);
catch(NoDataSourceException nodatasourceexception)
System.err.println("Cannot create DataSource from: " + ml);
System.exit(0);
catch(IOException ioexception)
System.err.println("Cannot create DataSource from: " + ml);
System.exit(0);
catch (Exception e)
System.err.println("Cannot create DataSource from: " + ml);
System.exit(0);
compiling is ok but when I run the program ,the system display:
java.io.IOException: java.lang.Error: Couldn't initialize capture device
Cannot create DataSource from: v4l://0 .
with the same condition and the same executing , I can be successful on windows2000.Why is not on linux?Please help me. thanks a lot!

I have installed j2sdk to /java/j2sdk and jmf to /java/jmf
I have added to /root/.bashrc including:
JAVA_HOME="/java/j2sdk"
PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin:/usr/games:/java/j2sdk/bin:/java/j2sdk/lib:/java/j2sdk/jre/bin:/java/j2sdk/jre/lib:/java/jmf/bin:/java/jmf/lib"
JMF_HOME="/java/jmf"
LD_LIBRARY_PATH="$JMF_HOME/lib:/java/j2sdk/jre/lib/i386:/java/j2sdk/jre/lib/i386/client"
LD_PRELOAD="/java/j2sdk/jre/lib/i386/libjawt.so"
CLASSPATH="$CLASSPATH:$JAVA_HOME/lib:$JAVA_HOME/jre/lib:$JMF_HOME/lib/jmf.jar:.:$JMF_HOME/lib/mediaplayer.jar:$JMF_HOME/lib/multiplayer.jar"
[ "$UID" = "0" ] || PATH="$PATH:."
export PATH JAVA_HOME JMF_HOME CLASSPATH LD_LIBRARY_PATH LD_PRELOAD

Couldn't initialize capture device

I am not able to capture any video from my webcam (Logitech USB Camera). I am working with linux red hat 8, so maybe it's a Linux issue (I got the liux jmf-2.1.1). Anyway, when I try to create a player or processor I get a NoPlayerException, but my webcam is found when i call Vector devices = CaptureDeviceManager.getDeviceList(new RGBFormat()) and I am able to locate the camera with MediaLocator loc = device.getLocator()(Media Location is v4l://0 in case it matters). But when I try to create a player I first get an IOException: Couldn't initialize capture device and a NoPlayerException.
JMStudio is able to initialize the capture device but I just get a black screen. But I can take snapshot images without a problem.
I am actually working on a robotics vision project for my university and i need the camera to plug it on the robot for vision problems.
thanks, muriel

I've had the same problem, I have a Lego camera (basically a quickcam) and it works fine under Linux with the qc-usb driver. Under JMStudio, it is detected, and I can capture from it, and this will work for any user, not just root. When I try to list the devices from my own Java code, however, I don't get any devices. If I run the V4LAuto class (found in the JMStudio source), the camera is detected. Either way, it won't initalize when I try to use it. I've looked through the JMStudio source code to try to see what it does differently so that I can use the device.
On the camera, the light comes on to say that someone is requesting the stream with my own code, but the stream fails to initalize.
I'm running RH9, kernel 2.4.21 (qc-usb won't work on 2.4.20-8). Does anyone know if this has to do with a permission in Java? It shouldn't, but it might.

Unable to initialize video deck, (can not capture from camera)

Hello All,
I am using a quad core G5 and am trying to capture some footage into Final Cut Pro version 5.0. I have two Panasonic DVX 100B mini DV cameras. I normally capture with a JVC BR-DV3000 mini DV deck but it is currently not working. So I'm trying to capture using my camera.
I hooked my camera up to my computer via firewire and started final cut, When I click File > Log and capture a little window pops up that reads:
" Unable to initialize video deck. You may still log offline clips or use Capture Now"
I'm not sure why this box is appearing. When I click the capture now button, the Capture window pops up and then I press play on the video camera and the footage plays on the camera but the capture window remains black or empty. I have tried both cameras and two different firewire cables with the same results. I have also tried to restart the computer.
Can anyone shine some light on this situation?
Thank you so much for your help.
Mike Wardynski

Are there any other firewire devices connected to your Mac?
Did you go into your easy setup and reselect the DV setting for the standard you are using?
Also sometimes, shutting down and restarting your Mac, after making these changes some times allows the new device to be recognized.
One other thing, the DV camera may have a menu setting that needs to be set for communication via firewire possibly?

Not Initialize my video capture device.

I have a creative web cam PD1001. I installed the application and the drivers. But when i try to make it run it says Unable to initialize your video capture device. Anyone have a clue what the problem might be?

Capturing is done in Premiere
Jeff

Wasapi: IAudioClient- Initialize() hanging when opening audio capture device

I'm trying to open the capture/input audio device. I call ActivateAudioInterfaceAsync() , then when I call IAudioClient->Initialize() on the capture device, the app hangs, supposedly because for some reason it's trying to display the 'Allow app to
use the mic?' prompt.
The hang _doesn't_ occur if I manually set the app permission to use the mic (i.e. launch the app without having it open the audio devices, open the permission tile, activate the mic permission).
Calls to ActivateAudioInterfaceAsync and IAudioClient->Initialize() are made from the UI thread (the one that receives callbacks for buttons, which on Metro style apps seems to be different from the thread that starts the application, i.e. WinMain).
What am I doing wrong?
I've attached the stack that shows the app hung below.
Thanks,
Flavio.
ntdll.dll!_NtAlpcSendWaitReceivePort@32()
Unknown
rpcrt4.dll!LRPC_CASSOCIATION::AlpcSendWaitReceivePort(unsigned long,struct _PORT_MESSAGE *,struct _ALPC_MESSAGE_ATTRIBUTES *,struct _PORT_MESSAGE *,unsigned long *,struct _ALPC_MESSAGE_ATTRIBUTES *,union _LARGE_INTEGER *)
Unknown
rpcrt4.dll!LRPC_BASE_CCALL::DoSendReceive(void)
Unknown
rpcrt4.dll!LRPC_BASE_CCALL::SendReceive(struct _RPC_MESSAGE *)
Unknown
rpcrt4.dll!LRPC_CCALL::SendReceive(struct _RPC_MESSAGE *)
Unknown
rpcrt4.dll!_I_RpcSendReceive@4()
Unknown
rpcrt4.dll!_NdrSendReceive@8()
Unknown
rpcrt4.dll!@NdrpSendReceive@4()
Unknown
rpcrt4.dll!_NdrClientCall2()
Unknown
AudioSes.dll!_AudioServerCreateStream@36()
Unknown
AudioSes.dll!CAudioClient::CreateRemoteStream(enum SYSTEM_AUDIO_STREAM_TYPE,__int64,__int64,struct SYSTEM_AUDIO_STREAM *)
Unknown
AudioSes.dll!CAudioClient::Initialize(enum _AUDCLNT_SHAREMODE,unsigned long,__int64,__int64,struct tWAVEFORMATEX const *,struct _GUID const *)
Unknown
Metro.exe!App1::MainPage::Startup() Line 171
C++
Metro.exe!<lambda_f0ad93afb1643234338c56b595dca446>::operator()() Line 48
C++
Metro.exe!Platform::Details::__abi_FunctorCapture0<<lambda_f0ad93afb1643234338c56b595dca446>,void>::Invoke() Line 850
C++
Metro.exe!Windows::UI::Core::DispatchedHandler::Invoke()
C++
Metro.exe!Windows::UI::Core::DispatchedHandler::[Windows::UI::Core::DispatchedHandler::__abi_IDelegate]::__abi_Windows_UI_Core_DispatchedHandler___abi_IDelegate____abi_Invoke()
C++
Windows.UI.dll!6283fdff()
Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for Windows.UI.dll]
Windows.UI.dll!628314ae()
Unknown
user32.dll!_InternalCallWinProc@20()
Unknown
user32.dll!_UserCallWinProcCheckWow@36()
Unknown
user32.dll!_CallWindowProcAorW@24()
Unknown
user32.dll!_CallWindowProcW@20()
Unknown
Windows.UI.Xaml.dll!5e06b434()
Unknown
Windows.UI.Xaml.dll!5e06b3af()
Unknown
user32.dll!_InternalCallWinProc@20()
Unknown
user32.dll!_UserCallWinProcCheckWow@36()
Unknown
user32.dll!_DispatchMessageWorker@8()
Unknown
user32.dll!_DispatchMessageW@4()
Unknown
Windows.UI.dll!628311dc()
Unknown
Windows.UI.dll!62831290()
Unknown
Windows.UI.Xaml.dll!5e16dee2()
Unknown
Windows.UI.Xaml.dll!5e16dea1()
Unknown
Windows.UI.Xaml.dll!5e16de65()
Unknown
ntdll.dll!_RtlReleaseSRWLockExclusive@4()
Unknown
03655668()
Unknown
twinapi.dll!67b2c9dd()
Unknown
twinapi.dll!67b2cab2()
Unknown
twinapi.dll!67b2c9f6()
Unknown
SHCore.dll!740c1ffd()
Unknown
kernel32.dll!@BaseThreadInitThunk@12()
Unknown
ntdll.dll!___RtlUserThreadStart@8()
Unknown
ntdll.dll!__RtlUserThreadStart@8()
Unknown

When you're in this state, can you take a dump of the svchost.exe process containing the AudioSrv service and send it to me? email to (mateer at microsoft dot com)
Matthew van Eerde

"Mode_sense error" & "initialization failed: unable to sense robotic device

I use Exabyte autoloader and Netbackup server on Solaris 9 sparc station. When booting system, got following error information:
/pci@le, 60000/LSILogic, scsi@4/st@1,0(st31)
VXA-2 options value invalid bits set: 0x4000
ermesx tl8cd[322]: TL8(1)Mode_sense error
ermesx tl8cd[322]: TL8(1) Key 5h, ASC 24h, ASCQ 0h, INVILID FIELD IN CDB
ermesx tl8cd[314]: TL8(1) unavailable: initialization failed: unable to sense robotic device.
Your advice will be appreciated.
Jennifer

Thanks for advice. Following is the output:
# /usr/openv/volmgr/bin/sgscan
/dev/sg/c1t0l0: Changer: "EXABYTE VXA 1x10 1U"
/dev/sg/c1t1l0: Tape (/dev/rmt/0): "EXABYTE VXA-2"
# /usr/openv/volmgr/bin/tpconfig -d
Index DriveName DrivePath Type Shared
0 EXABYTEVXA-20 /dev/rmt/0cbn 8mm No
TL8(0) Definition DRIVE=1
Status
up
Currently defined robotics are:
TL8(0) robotic path = /dev/sg/c1t0l0,
volume database host = ermesx
ok probe-scsi-all
/pci@le, 600000/LSILogic, scsi@5
MPT Version 1.02, Firmware Version 1.03.37.00
Initiator ID is 7
Target 0
Unit 0 Removable Device type 8 EXABYTE VXA 1x10 1U A10B
Target 1
Unit 0 Removable Tape EXABYTE VXA-2 2109
I can not find ��Changer: EXABYTE VXA 1x10 1U�� in /usr/openv/share/device_mappings.txt. There is only ��
CHANGER:EXABYTE Robotic Tape Library�� in that mapping file.
Thanks.
Jennifer

JMStudio: Couldn't initialize the capture device!

hello,
I am using JMStudio to capture video from my webcam and I have a problem. When I start my computer and run JMStudio I can capture video without any problems but when I close and run JMStudio again and chose option "Capture" there is a problem: Couldn't initialize the Capture Device! when I reboot my opereting system (windows 7) I can capture first time but when I try it again secondary there is a problem :/
Could someone help me please?

You can try to use ManyCam
just set it as DefaultWebcam.

"Unable to initialize video deck" inquiry

I am new to Mac and FCE, so I ask for some slack...
I am trying to get video from my Panasonic AG DVX 100 into FCE.
About my system: IMac 2.4 GHz Intel Core 2 Duo with OS X 10.5.2. I have FCE 4 on this computer, not an upgrade of earlier program, but version 4, straight out of the box. I know FCE is working, because I have edited a hour long project on it.
Here's my issue: With the first project complete, I want to import some new video into FCE and start another project. I connect the camera to the Mac via firewire (the white cable that I bought at the Mac store). When I go to "File" in FCE, I go to capture, and I get the following message:
*"Unable to initialize video deck. You may still use capture now."*
I continue by selecting "capture now." The capture window appears with "preview disabled" on the color bars, "no communication" at the bottom of the window. I hit "capture now" in the bottom right and I get the following message:
*"Attempt to capture video without a video device selected. Please select a video device in your capture presets and try again."*
I can't seem to track down "capture presets" , so that's my first issue. This was not a problem the first time I captured video. While at the Mac store, we plugged the camera into other Macs, but still would not get a signal. On FC, it would recognize the camera for a second or two, then flash the "no communication" error. The Mac folks believed it was a camera video out issue.
Some additional factors:
1. it's not the video output on this particular camera. Since that Mac store visit, I hooked it up to another computer and I could see video. So I'm confident that the camera will send video through this firewire.
2. Back to my original project, I imported video into FCE using this cable and a different mini dv camera (sony). It worked with the Sony camera, but will not work with this Panasonic.
I asked another friend, a MAC/FC/Panasonic DVX 100 guy, and he has never encountered this particular error message. He believes it's some setting within the computer that can be fixed through a software patch.
I would be most grateful for insight into solving what is likely a problem others have experienced. Please keep in mind that I am new to this whole process, and will likely show this thread to the people at the Mac store during my next one-on-one class.
Thank you very much.

David:
Thanks for your suggestion. I did check the firewire to ensure it's securely in place, and it seems like it is.
I did connect this camera and this firewire into a friend's macbook, and the signal was successfully received.
So I don't think it's a "loose wire" possibility. We also checked another camera into my Mac's firewire port, and it was successful.
So for some unknown reason, this particular Mac will not recognize this particular camera.
Again, your insights are greatly appreciated.

Trouble with Toshiba built-in webcam: "unable to enumerate USB device"

I am running archlinux on a Toshiba Satellite L70-B-12H laptop, and having troubles with the Webcam. *Once in a while*, everything goes well and I get
# lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 04f2:b448 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 8087:07dc Intel Corp.
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# dmesg
[ 3433.456115] usb 3-1.3: new high-speed USB device number 4 using ehci-pci
[ 3433.781119] media: Linux media interface: v0.10
[ 3433.809842] Linux video capture interface: v2.00
[ 3433.826889] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - HD (04f2:b448)
[ 3433.835893] input: TOSHIBA Web Camera - HD as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input15
[ 3433.835976] usbcore: registered new interface driver uvcvideo
[ 3433.835977] USB Video Class driver (1.1.1)
Unfortunately, *most of the time* the camera seems invisible to my system, and I get
# lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 8087:07dc Intel Corp.
Bus 003 Device 002: ID 8087:8008 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(note the missing "04f2:b448 Chicony Electronics Co., Ltd" device), and
# dmesg
[ 480.104252] usb 3-1.3: new full-speed USB device number 4 using ehci-pci
[ 480.171097] usb 3-1.3: device descriptor read/64, error -32
[ 480.341235] usb 3-1.3: device descriptor read/64, error -32
[ 480.511375] usb 3-1.3: new full-speed USB device number 5 using ehci-pci
[ 480.578007] usb 3-1.3: device descriptor read/64, error -32
[ 480.748151] usb 3-1.3: device descriptor read/64, error -32
[ 480.918282] usb 3-1.3: new full-speed USB device number 6 using ehci-pci
[ 481.325196] usb 3-1.3: device not accepting address 6, error -32
[ 481.392091] usb 3-1.3: new full-speed USB device number 7 using ehci-pci
[ 481.798926] usb 3-1.3: device not accepting address 7, error -32
[ 481.799166] hub 3-1:1.0: unable to enumerate USB device on port 3
Searching on the web, most results I found lead to this page, where it is said that the problem is due to badly tuned overcurrent protection, and advocated that unplugging and switching off the computer for a little while gets things back into normal. This does not really work for me; the problem seems to occur more randomly, unfortunately with high probability (my camera is available after less than one boot out of ten).
I tried to ensure that the ehci-hcd module is loaded at boot with the ignore-oc option (with a file in /etc/module-load.d/), to no avail.
I also wrote a script which alternatively removes and reloads the ehci-pci driver until my device is found in lsusb. It is sometimes helpful, but usually not. And even when my device is found that way, it can only be used for a while before disappearing again.
Anyway, such a hack is unacceptable... So, my questions are:
is it indeed related to overcurrent protection ?
is there anything else I can try ?
should I file somewhere an other of the numerous bug reports about "unable to enumerate USB device" already existing ?
If of any importance, I am running linux 3.15.7, because at the time I installed my system, I couldn't get the hybrid graphic card Intel/AMD working under 3.16.
Last edited by $nake (2014-10-18 16:29:06)

uname -a
Linux libra 3.9.4-1-ARCH #1 SMP PREEMPT Sat May 25 16:14:55 CEST 2013 x86_64 GNU/Linux
pacman -Qi linux
Name : linux
Version : 3.9.4-1
Description : The linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licences : GPL2
Groups : base
Provides : kernel26=3.9.4
Depends On : coreutils linux-firmware kmod mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels of your country
Required By : nvidia
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 65562.00 KiB
Packager : Tobias Powalowski <[email protected]>
Build Date : Sat 25 May 2013 16:28:17 CEST
Install Date : Sun 02 Jun 2013 15:30:35 CEST
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature

Unable to initialize HDV deck. Please make sure a deck is connected....

Ok, this is driving me nuts. I've done this before. I have a Canon HV20. I spent HOURS and HOURS on Sunday (two days ago) capturing 1.5 hours of video (DV, not HD) from my HV20 using iMovie09. Then spent more hours burning a DVD using iDVD09. Results were less than glamorous. Quite disappointing, video-quality-wise....
So today I reinstalled FCE 4.0 (HD) and decided to capture a few minutes of the same film and compare the results when making a DVD. My expectations are that it will look better. Naturally, I was hoping for the less-expensive, easier to use product (iMove09) would win, but so far, I can't compare because I keep getting "Unable to initialize HDV deck...". Folks, I have a firewire cable connected. I just used the same camera on the same cable on the same computer (macbook pro). the ONLY thing i changed was the software. Even switched back to iMovie for a minute to see if the cable still worked and sure enough, it's fine.
So, I'm blank on ideas here as to why "FILE/CAPTURE" in FCE would give me this error now. I'm waaaaaaaay open to ideas and even open to "stupid user error"... just tell me what it is....
This is soooooooooooo frustrating. Now I remember why I don't do video that often. Real pain in the butt sometimes...
Thoughts????

"Unable to initialize HDV deck...".
You seem to be trying to capture DV?
At the moment FCE is looking for a HDV camera and there is not one attached, a DV camera is.
Change the Easy Setup to the correct DV option to match the cameras output (audio and video), save, then try again.
Al

Unable to initialize hdv deck problem

Hi all,
I'm having the 'unable to initialize hdv deck' problem. I am trying to capture HD footage from a Sony HVR-A1E camera. iLink and down conversion are off (like they should be) and I have just captured a HD tape before the problem started.
I don't understand how I could capture HD footage just fine and then without touching any settings (just trying to start capture again) I suddenly get the error message, "Unable to initialize HDV deck. Please make sure a deck is connected and try again."
Any ideas?

Definitely. Shot on HDV, definite difference between the clips I've captured so far (HD capture that worked fine before this is high quality sharp image, where as when capturing in SD, image quality is poor and smaller).
Everything has been filmed on the same camera with no setting changes between shots. Like I said before, I have already been able to capture today in HD just fine, but for some unknown reason (which I don't think is the prefs.) capture will not work. I can 'trick' FCE into HD capture but it gets stuck on cueing tape (even though video is playing fine on camera).

Unable to Initialize Capture Device

Similar Messages

Maybe you are looking for