Capturing Video in Vista

[Leopardsocks]

I have VideoStudio 11, running on an Intel dula core 2.6 Mghz processor under Windows Vista.

I am not able to capture video. I simply get the "capture graph" error message which may as well be cake baking instructions in swahili.

If I use Windows Video Capture, all is well.

Is VideoStudio, as I have long suspected, not as compatible with Vista as it is claimed to be?

[Ken Berry]

It would be useful if you told us what format video you are trying to capture, the model of your camera or other devices you are using, and how it is connected to the computer.

There is a bug with VS11/11+ relating to capture of analogue source material via Firewire using either a mini DV camera as pass-through, an external capture device using Firewire, or a Digital 8 either being used as pass-through or playing back analogue 8mm or Hi8 tapes directly via Firewire. The 6 November update patch fixed all of these except the latter (Digital 8 playing analogue tapes).

Some aspects of High Def capture and editing were also problematic with VS11/11+ but these too were fixed and expanded with that same update patch plus the Power Pack for VS11+ which upgrades it to VS11.5+.

These problems all occurred regardless of whether the program was running on Vista or XP. Personally, I find VS11/11.5 completely compatible with Vista Ultimate and Vista Home Premium (installed on two different computers).

[boxy]

I have the Intel 6600 dual quad, Vista Home Premium. VS 11+ is compatable.

However, recently I encountered a similar problem.

When I was getting my feet wet with the trial version of VS 11+ capturing was smooth as can be. Now that I've installed the full version, the capturing is not as smooth as it should be. For some reason after about ten minutes the motion freezes for a second or two and stutters. After about five seconds or so of 'burping' it goes back to normal for another ten minutes, then stutters again. After three or four failed attempts to capture without any loss of video I tried the Windows capture and it did the job. Very strange to say the least.

I would prefer to use VS for capturing but I can use Windows if necessary.

[Ron P.]

Neither of you say how you are capturing. Are you using Firewire, or a capture device?

For Boxy it seems as though you're trying to capture via USB, and at some point the transfer just can not keep up, thus producing the stuttering.

[Leopardsocks]

Panasonic DV, NV-DS35, using Firewire. No analogue involved.

Just connect the video recorder, and try and commence the transfer as usual.

I have two Firewire ports, tried both with equal lack of success.

[Ron P.]

Have you tried launching VS, once it's loaded, then turning on your camcorder? Sounds strange, but others having the same problem as you, found this seemed to work.

[boxy]

For Boxy it seems as though you're trying to capture via USB, and at some point the transfer just can not keep up, thus producing the stuttering.

Firewire here, too.

Again, I had no problems capturing with the trial version. It's only after I installed the full version this happened. That's what's strange.

Not sure when I'll be capturing again but I will use VS first and see what happens.

[Leopardsocks]

I tried as you advised. Unfortunately, "Cannot start capture graph" was the response.

It seems that evidence is mounting in this forum, from other similar problems, that VS 11 and Vista may not be as good a combination as we'd like.

If I connect to VS8 installed on a laptop, there are no problems. If I use Windows Video Capture, there are no problems.

[Leopardsocks]

Just as an update...I downloaded the trial version of Adobe Premiere Elements, to see if its a Vista problem, or ULead...

Premiere worked fine. Windows Video Capture works fine. Even AVS Video Capture, an el cheapo little app that came with a suite of programs works fine.

It seems VS11 is not up to scratch, in Vista.

[Ron P.]

I think you're on the right track. I don't have anyway to test the Vista theory. My laptop runs Vista, and does not have any firewire capability. Not even a PC card slot to put a firewire PCMCIA card in.

Pre-VS11, and Vista, the capture plug-in was always DSW, or VFW. Ulead or at the time of Vista coming out, and VS11 being developed, Intervideo changed that to their own marvelous creation called IVI (stands for InterVideo Idiots (I think, I could be wrong) . Since that time there have been problem after problem with capturing.

When the A-D (analog to digital) conversion through either a camcorder or other device surfaced, I managed to deduce it had to be in their IVI plug-in. Until that time they had no idea why we were having this problem. I submitted that through my contacts to Corel/Intervideo. After about a week I received an email from one of their techs (had to be someone fresh out of McDonalds school, just got his fry-a-later operator's certificate), telling me that they found out where the problem was. It was their IVI capture plug-in..Whoa..no kidding, wished I had known that..

So yep, this does not surprise me at all.

[Leopardsocks]

I am sure Ulead proudly announced that VS !! was Vista- compatible.

It seems not.

[Ken Berry]

You like repeating this -- this is about the third time I have seen a similar comment from you, so I am starting to think that it is time to challenge it. VS11/11.5 seems perfectly compatible with Vista for me and I am sure, many other users. The type of problem mentioned by Ron occurs because of an internal failure in the new capture plug-in used by VS11, and this occurs whether the OS system is Vista or XP... I am perfectly willing to accept that VS11/11.5 may have problems, but I am not sure that these can necessarily be ascribed -- let alone solely -- to Vista.

[Leopardsocks]

You like repeating this -- this is about the third time I have seen a similar comment from you, so I am starting to think that it is time to challenge it. VS11/11.5 seems perfectly compatible with Vista for me and I am sure, many other users. The type of problem mentioned by Ron occurs because of an internal failure in the new capture plug-in used by VS11, and this occurs whether the OS system is Vista or XP... I am perfectly willing to accept that VS11/11.5 may have problems, but I am not sure that these can necessarily be ascribed -- let alone solely -- to Vista.

I hope you are keeping score, because if and until Ulead provides me with a solution, it is a point that cannot be ignored.

With respect, if I purchase a product of any nature, I can reasonably expect it to work.

Software is no exception.

When I therefore attempt to perform what should be a perfectly routine function, and I receive a cryptic, utterly useless error message, I am entitled to some irritation.

Now, I am quite happy to accept that Windows Vista may be the problem. But it is ULEADS problem, not mine. It is incumbent upon them to sell software that is fit for purpose. They claim VS11 is Vista ready. I part with the cash.

Now, if Vista IS the problem, why do the other products that utilise direct capture from the camera work fine? Doesn't that suggest that the problem is unique to VS11??

Now, the problem does not manifest itself on my laptop, with version 8 running on XP. Works perfectly.

Thus, logic dictates that there is an issue between VS11 and the computer I have that runs Vista. I'm happy to accept other contingencies, but thus far, as you can read above, no alternative contingencies have been provided.

Now, your rather snippy response suggests I'm being unfair to the product. I've been using it since Version 4, so one might assume I am a reasonably loyal user, and wish to continue that way.

But in the absence of any answer to the contrary, the current weight of evidence points to a VS11/Vista incompatibility issue that can reasonably be expected to be resolved by Ulead - or at least a more vigorous address to the issue, given that there are other users in this forum who have raised the same problem, and none have been provided with a solution that I can see. Any suggestions seem to be pure guesswork.

All I want is a product that works, not a debate on the pros and cons of ULead products. Whilst I am very gratified and happy that it works for you, it doesn't for me.

[Ron P.]

Panasonic DV, NV-DS35, using Firewire.

I've done a search on this forum and found that some others having a similar problem to yours, was an issue with some Panasonic mini-DV cameras. So I tried a Google search on you model, and could not find it. I went to Panasonic's website and could not find your model listed. Is there a typo with your model number?

I could find some information about a Panasonic PV-DS35, but not a NV-35. In fact Panasonic shows no form of camcorders using the NV in their models.

[Ken Berry]

Umm, Ron, I just inserted 'Panasonic NV-DS35' in my Google search bar and got a ton of responses. It certainly exists...!!!

I also recall responding to a thread well over a year ago i.e. before VS11 or Vista had been released concerning problems -- or conflicts -- between a specific DV codec installed by the Panasonic installation disc and which was either unreadable by, or would not allow capture by the standard Windows DV encoder. I am starting to wonder whether this might be a factor here.

Leopardsocks -- do you have a a codec recognition program installed? If not, could you download and install one like GSpot. That will tell you whether you have something which, from memory, was designated 'Panasonic DV Encoder', installed. If so, I would suggest, as a test, you might remove it, and see whether VS works (better)! If not, at least that will have been eliminated as another possible cause of your woes (rather than VS or Vista!) and you should always be able to reinstall it from the CD that would have come with the camera...

EDIT: after a minor search, I found that the Panasonic DV codec is in the file PDVCODEC.DLL. It is apparently used correctly in VirtualDub, but others report conflicts and problems when it is used with other programs.

If indeed you do have it on your computer, you will probably say "Well, it worked with previous versions of VS. Why isn't it working with VS11?" To that, I would have no answer except the obvious one that VS11's architecture is quite different from previous versions, mainly because of the tinkering that InterVideo and then Corel have done with the code -- deleteriously, IMHO and that of others here. But if removing the codec if you have it, and using the standard Windows DV codec instead, resolves the issue, I would have thought it a small price to pay...