What you need to knowEdit

  • If you are using anything other than a standard OHCI compliant capture card, be sure to check the manufacturer's knowledgebase for known problems, updates and driver downloads.
  • You must be logged in as an administrator the first time you perform a capture so that certain privileged Registry entries can be created.
  • If you're still having a problem, create a new user account with adminstrator priveleges. Restart the computer and log in as the new user and try capturing.
  • For best results, be sure your camcorder is set to two-channel mode, 16bit, 48KHz and that you set the date and time before doing any shooting.
  • Be sure not to leave gaps on a tape between shoots. Non-contiguous timecode, especially gaps with no timecode at all, is only going to cause unnecessary headaches.
  • Be sure to capture a 32KHz clip in a 32KHz project. Be sure to capture a 48KHz clip in a 48KHz project.
  • Some DV devices require you to enable the IEEE 1394 interface. See the user manual for details.
  • Some DV devices are switchable between PAL/NTSC. Ensure the switch is set to the same format used on the tape. See the user manual for details. You may also need to play a bit of the tape before connecting the device to the computer to ensure the correct signal is used.
  • The HDR-FX1 must have "iLink conversion to DV" set to off, otherwise Windows sees it as a DV device instead of a HDV device. See the user manual for details.
  • Be sure to disconnect your device from the computer when switching it between DV and HDV. The computer can only detect the device type at connection time.
  • If you installed any “codec packs” you have caused yourself a lot of headaches. You can try uninstalling the codec packs, but you may well end up having to re-install Windows from scratch. The “Tsunami” codec pack has been specifically reported as causing capture problems.
  • Some people with dual processors are reporting capture problems in version 1.5, see the thread "Very unstable capturing: "Unknown recorder error"". The solution is to reduce affinity to a single processor in the Windows Task Manager, or install the latest AMD Dual Core Processor driver and the MS Hotfix for XPSP2: KBB896256.
1. Don't run other media apps while opening Premiere Pro. I found that playing music in Winamp stopped Premiere from opening.
2. Disable as many processes as you can. See all those little icons in the bottom right of your screen? Shut them down. I found that 3 of those (Including Google Desktop Search, Microsoft Antipsyware) caused startup and capture issues with Premiere Pro.
3. Remove any codec packages you might have installed. These can cause startup issues with Premiere Pro.
I think I have found the culprit. I have two RAID arrays in my system, on MOBO VIA and the other an SI 3112 (PCI add-in).
When I switched to capturing on my other RAID array (the VIA), the artifacts stopped. I believe now it is my Work drive array controlled by the SI 3112 that is causing the the work really begins.
  • Defragment all of your hard drives at least once a week.
  • Search the Internet for a utility to monitor your CPU temperature. An overheating CPU can make strange things happen with no indication of an overheating problem.
  • Turn off Premiere Pro's autosave feature before capturing.
  • Turn off the MS Windows power saving feature before capturing.
  • Turn off the MS Windows screen saver before capturing.
  • If you are having problems capturing to external or network drives then capture to an internal drive.
  • If you have trouble capturing to an internal drive, try capturing to a different internal drive.
The solution was to be sure XP Service Pack 2 was loaded and then connect the hardware. The screen for new hardware came up and I pointed to the Service Pack 2 CD and it found the driver. This driver evidently enabled Pro 1.5.1 operate the camcorder.
You can check to see if the driver is there by:
Control Panel
 Performance and Maintenance
   Device Manager
    Sound, Video and Games
     AV/C tape device
  • Mitch411 said about audio glitches during capture:
I found a post about what appears to be the same issue on the DMN forums here: audio glitches during capture. This guy says that he found the solution. Panasonic needs to upgrade the firmware of the camera. If the camera is under warranty it's free, otherwise Panasonic may charge you $150 (at least that what the author of the post says).
Check these things: Go into Windows Device Manager and look for a category called imaging devices (Start > Settings > Control Panel > System, Hardware Tab, Device Manager button). Under Imaging devices, there should be a listing for something like "Sony DV Camcorder". If you don't have this listing in Device Manager, Premiere will never see the camera.

Second, launch PPro and open the capture window. Does the Capture window list the camcorder as "Stopped" or Capture Device Offline" or something else?

Third, access the device control and select DV/HDV Device Control. Click the Options button to make your selections. The settings should be: NTSC, Sony, Standard, and Auto Detect. The Check Status button should be "online". If the Capture window says "Can't activate recorder. Try resetting camera." and the Check Status says detected, look at solution 2 the doc Error "Can't activate recorder. Try resetting camera" when you capture video (Premiere Pro 1.5, Premiere Elements)
Here a pointer. Never mix DV and HDV on the same tape. The camera only function as the type of data the heads are sitting on, when it is first plugin in i.e. if you are on a DV spot on the tape you have a DV camera. The problem is when you wind forward to a HDV segment the camera is still in DV mode, preventing HDV capture (and vise verse if the camera is plugged in on HDV segment.) You can override this camera function in the menus so that the external on the HD1 set whether it outputs as DV or HDV.
I have the ADS Instant DVD + DV a-to-d converter. The files I renamed (there were three similar ones, all with ".ax" file types, and I just renamed each one to cover) were (complete path given on first file; all were in same dir.):
C:\program files\ADSTech Instant DVD+DV\
I notice now that when it itermittantly happens, and it seems to be rare, that if I turn off the DV camera and then turn it back on, thus forcing it to re-bind to it's driver it seems to fix the issue. I do this while in the capture screen in Premiere.
We found the problem finally! I originally edited this project in Premiere 6.0 using a “Pinnacle” Capture Card. We used the Pinnacle AVI Editing mode. When we sent the project to Adobe Premiere Pro 2.0 it automatically changed the editing mode to Desktop. As we checked the difference between the times when we created a project where the editing mode was Desktop and when it was DVNTSC the External Device settings changed too. In other words in Desktop mode you can capture video from a DV device but you can’t export it- and you can also use a secondary monitor. But in DVNTSC mode you can send out and capture to and from a DV device but you cannot use a secondary monitor. . (quirks in the software code I guess.)

You cannot change your choice of export devices once you have set your editing mode at the beginning of your project and you can only set up one device at a time. Our experience suggests using a standard editing mode (rather than a 3rd party plug in mode) if you plan to move your project from one version of Premiere to another!!
I spent some time on phone with the Adobe tech and tried many things to troubleshoot this problem. Yes, there is a quirk with this camera (Panasonic DVC-30)and Adobe CS3. Finally, my dual display setup was changed to single view and the problem went away. I am now able to have video preview during the initial capture.
Under the hood, Premiere is using Microsoft Directshow for handling DV streams & device control, so there's nothing that I can think of that would make a difference here. Either it works, or it doesn't. Usually, if it's not working, historically it was an install issue where the Directshow components weren't properly registered (which is no longer a problem in CS3, as we no longer rely on the installer registration step), or else there's simply something wrong with the firewire port and/or driver configuration.
I remembered that I installed an ADS DVD EXPRESS capture device to record VHS tape into the system just last week.

I uninstalled ADS DVD EXPRESS and my problem was solved! Didn't do anything else!

As a backup, before I discovered the problem, I was able to capture using Adobe OnLocation. If you don't have CS3, this isn't an option.

It turns out that Project>settings>Capture>DeviceControlSettings isn't the complete list of settings one would have every reason to think it is. There's also Edit>Preferences>Device Control>Devices>Matrox1394DeviceControl>Options> where Drop-Frame or Non-Drop frame is set separately for the Matrox Device Control as opposed to setting that for the entire project. Changed that setting and that appears to have fixed Batch Capture.
  • Funes said:
Try executing the following line on Start -> Run dialog (copy paste and press OK

regsvr32 %windir%\system32\qdv.dll

You should get a "DllRegisterServer succeeded..." message. Try capturing again afterwards. .

  • Moore said:
I've had a world of trouble with NDF/DF discrepancies between the footage I log in Premiere and the footage it captures. It always logs the footage to match your time code settings, so if your project is in Drop but your footage is in Non Drop it will always capture inaccurately. We set our time code sequentially by hour (tape one is 01:00:00:00, tape two is 02:00:00:00) so that means every tape is off by an additional 3.6 seconds or so. A huge problem when you get to tape 15. I found one workaround if you're having the same problems; I manually change the logged clips from DF to NDF (or visa versa depending on your needs). Export all your footage as a batch capture list (Clip -> Export as Batch List), then open that file up in Excel or Numbers or similar, and do a find and replace, changing all ; (Drop frame) to : (Non Drop Frame). Not sure where the kink is in our setup (the deck, the serial adapter, matrox, our version of Premiere etc.), or how to change this in Premiere's log settings, but for now this workaround does okay. Jonas<3


  • Premiere Pro does not natively support analog capture. You can get third party solutions from companies like Matrox and Canopus among several others. You could also use a digital camcorder to record the analog source and then capture the digital footage as usual; some camcorders will even do “pass through” without the need to record to tape.
  • If you want your analog capture card/device to work with Premiere Pro you will need to get drivers from the card/device manufacturer, not from Adobe.
  • See Capture analog video in the Premiere Pro CS3 Help or the section “Digitizing analog video as DV” in the Premiere Pro 2.0 and 1.x Help.
The Panasonic manual makes no reference to recording or transmitting from external inputs, however after playing around with a few settings I finally got it all happening. (Panasonic does not refer to S-video in the setup menu. Setting AV Jack to IN/OUT did the trick)

Clip NamingEdit

  • By default, Premiere Pro names the first clip "Clip 01". This becomes a problem if you capture more than a hundred clips, because sorting the clips alphabetically will put "Clip 100" immediately after "Clip 10" but before "Clip 11".
    The trick is to name the first clip "Clip001", or "Clip_001". It is important not to have a space before the number.

Device controlEdit

  • See the C:\Program Files\Adobe\Premiere Pro x.x\ReadMe file for important information about capturing.
  • If you are using a Matrox project (RTX Editing Mode) you need to use Matrox device control, not the Premiere Pro DV device control, otherwise you can experience audio problems.
  • For serial device control, Adobe recommends using Pipeline Digital cables. More information can be found at the Pipeline Digital web site ( Generic cables are unlikely to work and cannot be supported by Adobe technical support.
  • Device control will not work properly if you connect more than one device to the same FireWire port. It is recommended that you attach only one device to a FireWire port.
ensure your tape deck control on the front of the JVC BR-HD50 is set to remote before you switch the unit on, this may be the cause of your problem.

Using the BR HD50 you must update your FW driver, go to device  manager and update the firewire driver, choose your driver and choose the one with legacy at the end. Now the deck will work in CS6Edit

Community content is available under CC-BY-SA unless otherwise noted.