dglenn1 wrote:USB devices are selfish, stingy things, they do not like to share.
Absolutely no help at all there. Don't even know what to do with that.
Only have one usb device connected - your capture device.
USB well, it just does not work for capturing video very well at all.
In what way? Low quality?
often only providing capture in low quality formats, as the bandidth is not high enough to cope with the constant stream of info sent when capturing to high quality formats. Picture loss?
Maybe, maybe dropped frames. Sound sync issues?
Not likely if you can capture as dv.avi - most likely loss of both video and audio, but if you can only capture as a compressed file such as mpeg, then yes AV sync issues are common. Have you ever seen it cause what I am experiencing?
NO, I have a canopus nx express card which is of a very high quality, but I do spend my spare time answering these questions day in day out, as do all the other regulars here I am awarded my Microsoft MVP status for the quality of help I give to people using MS software.
...bandwidth available is chopped down...
Resulting in ... ??????
If the bandwidth is lowered then the file cannot travel down the wires at a fast enough rate so you get dropped frames, corrupt files, low quality, stopped capture.
...leaving your video transfer ... with not enough.
Not enough what?????
Honestly, do really think these comments address the issue at all? Am I supposed to glean from these generalizations about USB connectivity an approach to solve a problem where a video captures, views, but doesn't edit? The connection is not clear to me.
The captured file may be corrupt, as above. Editing is much more demanding than viewing. The file may be of the wrong sort for the settings you have.....
When I preview the capture or view it in Media Player or Windows Movie maker -
DOES MOVIE MAKER EDIT THE FILE? if so, then we can look at why VS doesn't. it appears to be a high quality clip with great sound and very little loss from the source. It just won't go into edit in VS. Can you help me make the leap in logic that says the problem lies in the capture device?? or the compression codec?? or my keyboard fighting for the attention of the USB port?? It seems if these were the problems it wouldn't capture at all or at least have some very poor quality or other visible problem. I have made it clear that I am doing the capture inside of VS using EasyCAP as the interface device correct? It looks to me that VS can't read it's own writing.
I don't mean to appear obstinate here, but I'm looking for deeper clues on how to track down what is wrong with my situation.
We need to rule out things to work toa problem that is deeper than changing setting a to b, so what may appear to be to you awkward or inane questions are in fact trying to lead us to your solution, so if you could bvear with teh qeustions, do what is asked in the way of testing etc, we will try our best to get that solution.
Perhaps someone could share a setup that does work? Codec, settings etc. or offer some deeper insight as to how VS interacts with the devices I have or between its different modes to help me understand what to try next?
Regards, Dan