Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Capture Confusion

  • Capture Confusion

    Posted by Brad White on November 7, 2011 at 3:24 am

    Recently purchased a Sony HXR-NX70U and trying to capture video with Vegas Pro 10. My previous camera had an iLink (Firewire) interface and it worked well. The new cam, being flash based, uses a USB interface. The camera came with a program called Content Management Utility, although it works, it has some anomalies with file names.
    So, the question is, can Pro 10 capture via USB?
    Brad White

    Stephen Crye replied 14 years, 7 months ago 4 Members · 9 Replies
  • 9 Replies
  • Nigel O’neill

    November 7, 2011 at 5:33 am

    You don’t capture as such. You hook up the camera and use the content management utility to export the footage into whatever container you need it in e.g. MPEG2, SD etc.

    You should be able to access the files as you would a USB drive.

    My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • Ted Snow

    November 7, 2011 at 6:18 am

    Brad, you are aware of the 4GB FAT file system limit? My Z7U and CX130 HD cameras have it and I assume your camera does too. These cameras use the FAT file system instead of the NTFS system which limits file size to 4GB. If you have a video clip that is more than about 20 minutes long…the camera automatically splits the video file. If you copy the files directly from your camera or a USB card reader without using the utility software you will have a 1/2 second glitch in the audio at the split of the files. If you use the utility software that came with your camera it will automatically join the file back together without the glitch.

    I would download the latest version of the utility software from Sony. Both of my HD cameras came with the installer disk but I went to the website and downloaded the latest version of both software programs as both cameras use a different utility software.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

  • Brad White

    November 7, 2011 at 8:21 pm

    Thanks for your comments.
    My real issue with using the Content Management Utility (CMU) has to do with file names. Here is an example; A video clip in the camera is labeled 100_0027 when played in the camera. When this same clip is moved (USB) to my computer using the CMU “Import” screen, the file name is shown as M2U00027.mpg. And when this saved file is then opened in CMU, the file name is now 20111105171841.mpg, a full 14 digits long. The first half of this number appears to be the date (year/month/day) and the second half appears to be random. I can not find any setting within the CMU that allows me any control over assigning file names (numbers). I would like to understand what is happening as the file moves around. I would also like to simplify the file number for editing and archival purposes.
    Brad

  • Ted Snow

    November 7, 2011 at 8:54 pm

    Brad,
    Actually the renaming of the file is pretty nice in terms of keeping track of the files. You are correct in the fact that the first part of the file name is the date…the rest of the file name is not random, it is the time of the recording. Your file name states November 5th, 2011 at 17:18.41 or 5:18 p.m.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

  • Brad White

    November 9, 2011 at 9:00 pm

    Thanks for this info Ted.
    I will work with what the utility offers.
    Also, I thought I read somewhere that Pro 11 has a direct import feature where you don’t have to use the CMU. However, it currently doesn’t matter as I purchased the Pro 11 upgrade, but my OS is XP which is not supported. I’ll make the decision to upgrade OS later.
    Brad

  • Ted Snow

    November 9, 2011 at 9:13 pm

    This is copied and pasted directly from Sony’s webpage for the Recording Unit Utility Software.
    ————————-

    Some NLEs, such as Sony Vegas 7 (version 7.0c and later) and GrassValley EDIUS Pro4.5, have an import module that lets you import files directly from the HVR-DR60 to your PC’s hard drive. During the import process, these software will merge all divided .M2T files into a single, seamless .M2T file.
    If the destination folder is not on an NTFS-formatted hard drive, the merged file can not be output.
    This software can only merge files that are divided by FAT32 specification.
    If the destination hard drive is full, file merging will stop. Please check the remaining capacity of your PC’s hard drive before using this software.

    ————————-

    This is referring to the HVR-DR60 hard drive recorder, but it also pertains to the MRC1 as I use it with mine. I’ve never tried the “import module” as they refer to it as…I’m assuming they are talking about the capture utility in Vegas. I always used the capture utility for DV…but I use the Recording Unit Utility Software for HDV.

    The software you are referring to that came with your camera is actually different that the software that came with my Z7U or my CX130…although they all do pretty much the same thing.

    ————————————————
    ASUS P8P67 Deluxe MB
    EVGA GeForce GTX 560 Ti 1 GB DDR 5
    Intel i7 2600k 3.4 Ghz
    Corsair HX750 power supply
    Two Seagate Barracuda 500g SATA III drives
    16 Gig G.Skill Ripjaws DDR3 1600
    Canopus ACEDVio card
    Thermaltake V9 BlacX Edition case
    Xigmatek Dark Knight CPU Cooler
    Win 7 Pro
    VEGAS 8.0
    VEGAS 11.0 32 & 64 bit
    Sony VX2100
    Sony HVR-Z7U
    Sony HDR-CX130
    Alesis HD24

  • Stephen Crye

    November 10, 2011 at 9:40 pm

    Hi Brad;

    When you decide to upgrade, consider dual-boot. That is what I did two years ago. Bought another SATA drive, a new copy of Windows 7 Pro, and did the install. The install fully understands dual-boot, configured the partitions and boot menu. Piece of cake.

    I don’t boot much into XP these days, but it is nice to have when needed. And, if either OS crashes, you have the other, on a separate disk, for the emergency.

    Steve

    Win7 Pro X64 on Dell T3400 MultiTB SATA 8 GB RAM Vegas 10e x64 DVDA 5.2 Sony HDR-CX550V

  • Brad White

    November 13, 2011 at 11:37 pm

    Steve,
    I was unaware that dual-boot was a possibility. Unfortunatly, my XP Pro system (home brew) motherboard doesn’t have drivers available for Win 7, so an upgrade to Win 7 will basically require a mostly new computer (MB, memory, processor, etc). I also have a secondary editing computer (file sharing) running XP Pro with Vegas 10 as a backup, so I have double trouble when it comes to hardware upgrade. I will seriously consider dual-boot when I make the leap.
    By the way, how do you tell the computer which drive to boot from? Could you put both operating systems in different partitions on the same hard drive, or do you need two physical ‘C’ drives?
    Thanks,
    Brad

  • Stephen Crye

    November 16, 2011 at 11:06 pm

    Hi;

    Sorry to hear about the mombo driver problem. The only possible way around that would be with the VMware player, but that would be pretty slow.

    I have never tried the dual-boot from a single drive, but It would work if you first re-sized the parition. But, that is potentially perilous!

    Adding a second SATA drive for Win7 is suuuper easy. You can either install it internally, or get one of those external “naked” SATA drive docking stations, such as the ones from BlackX. ( I use two because am swapping 1 TB drives like crazy).

    After you add the new drive, use XP to partition it, put NTFS on it. Then boot from the Win7 Pro DVD (don’t use anything less than Pro). One of the menus will ask you if you want to dual-boot, pick it and just follow the prompts. When the whole thing is complete, you will boot to a text-ish menu where you will have a choice of Win7 or the “old” OS. The Win7 install will modify the master boot record on the existing drive 0 (your old C: drive). When you boot to Win7, the Win7 drive (drive 1) will be the C: drive and the old XP drive will be the D: drive. Conversely, when you boot to XP, the XP drive will be C:

    Works like a champ every time!

    Steve

    Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM Vegas 10e x64 DVDA 5.2(build 133) Sony HDR-CX550V

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy