Delayed capture
Moderator: Ken Berry
-
zehavi
- Posts: 222
- Joined: Tue Jun 06, 2006 6:22 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- processor: Intel[R] Core[TM] i7-8700 CPU 3.20 GHz
- ram: 8GB
- Hard_Drive_Capacity: 465 GB
- Monitor/Display Make & Model: LG
- Location: Israel
Delayed capture
Hi,
When I start the capture step from my DV camcorder (IEEE-1394), the playback of the camcorder starts immediately but the capture starts about 10 seconds later. These happened to me in VS9 and now in VS10+ also.
I will be grateful to get any response.
Abraham
When I start the capture step from my DV camcorder (IEEE-1394), the playback of the camcorder starts immediately but the capture starts about 10 seconds later. These happened to me in VS9 and now in VS10+ also.
I will be grateful to get any response.
Abraham
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
A brief delay ( 1 or 2 seconds) is absolutely normal. I factor this into my captures by deliberately setting the tape back a little more than that and starting the capture. This might require a bit more clipping in the editing stage, but I would rather that than missing something important at the start of that particularly sequence of video. Mind you, while actually filming with my camera, I also try to be conscious of this factor and try to include some video at the start of a new scene which is easily discardable as not important. But I acknowledge this may not always be possible.
However, a 10 second delay is definitely not normal -- in my experience anyway. It could be a characteristic of your particular camera. But since we don't know what that is, or what else you might be doing, it is impossible to comment further.
However, a 10 second delay is definitely not normal -- in my experience anyway. It could be a characteristic of your particular camera. But since we don't know what that is, or what else you might be doing, it is impossible to comment further.
Ken Berry
-
heinz-oz
-
skier-hughes
- Microsoft MVP
- Posts: 2659
- Joined: Thu Jul 21, 2005 10:09 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: gigabyte
- processor: Intel core 2 6420 2.13GHz
- ram: 4GB
- Video Card: NVidia GForce 8500GT
- sound_card: onboard
- Hard_Drive_Capacity: 36GB 2TB
- Location: UK
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
- Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
Hi Abraham,
Thank you for completing your system information in your profile. In doing so I noticed that your system is a little on the low end for video editing. It is workable, however I would recommend some tweaking. Steve has a great tutorial found HERE that can make a world of difference.
Your hard drive is real small if you are going to do much video editing. Capturing DV requires 13 gig per hour. Then add to that amount, the space the program is going to need for temp files when editing or creating video files. Again this can work, but you need to be conscious of how much space you have. A 40 gig hard drive seems large for editing photos, and normal acitivity, however with video editing, 100 gig and larger is more common.
Now as far as the capture issue, Do you have any background applications running? You should try to disable all background apps that are not needed while capturing. Background apps take away from well needed CPU resources. If another app thinks it needs to do something while you are capturing, then this could cause dropped frames, which then could result in a corrupt file.
Do you have access to another Firewire cable? If so you may want to try it to see if the one you are using has been damaged. With the program being able to start the camcorder immediately, but the image not appearing this comes to mind.
Just some thoughts that may help...
Ron P.
Thank you for completing your system information in your profile. In doing so I noticed that your system is a little on the low end for video editing. It is workable, however I would recommend some tweaking. Steve has a great tutorial found HERE that can make a world of difference.
Your hard drive is real small if you are going to do much video editing. Capturing DV requires 13 gig per hour. Then add to that amount, the space the program is going to need for temp files when editing or creating video files. Again this can work, but you need to be conscious of how much space you have. A 40 gig hard drive seems large for editing photos, and normal acitivity, however with video editing, 100 gig and larger is more common.
Now as far as the capture issue, Do you have any background applications running? You should try to disable all background apps that are not needed while capturing. Background apps take away from well needed CPU resources. If another app thinks it needs to do something while you are capturing, then this could cause dropped frames, which then could result in a corrupt file.
Do you have access to another Firewire cable? If so you may want to try it to see if the one you are using has been damaged. With the program being able to start the camcorder immediately, but the image not appearing this comes to mind.
Just some thoughts that may help...
Ron P.
Ron Petersen, Web Board Administrator
-
zehavi
- Posts: 222
- Joined: Tue Jun 06, 2006 6:22 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- processor: Intel[R] Core[TM] i7-8700 CPU 3.20 GHz
- ram: 8GB
- Hard_Drive_Capacity: 465 GB
- Monitor/Display Make & Model: LG
- Location: Israel
Thank you Ron,
Actually I have two harddrives, one of 80GB and the second is 40GB.
Anyway, I don't think this is the problem, my VS projects is less than 1 hour and when I start a new project, there is no other VS project on the drive, so I have plenty of space.
I am going to buy another Firewire cable to see if it will help.
Thanks again,
Abraham
Actually I have two harddrives, one of 80GB and the second is 40GB.
Anyway, I don't think this is the problem, my VS projects is less than 1 hour and when I start a new project, there is no other VS project on the drive, so I have plenty of space.
I am going to buy another Firewire cable to see if it will help.
Thanks again,
Abraham
Hi Your problem could well be with the capture card. Pinnacle used different manf over the years. I had similar problems with there Miro card so I went to the Pinnacle web site (support) where I found a link to Miro in Germany and downloaded the latest drivers which made a big difference to the performance of my card. Before logging on though I would suggest you have a good look at your card and make a note of all the numbers you can find on it because Pinnacle product numbers are not the same as Miro/s etc.
