I just upgraded my PC from W2K to Win XP SP2 by reinstalling it.
After installing my 2 Ulead licensed products (UVS9 and DMF4), it appears that there's no firewire signal in UVS9, even though DMF4 does recognise the firewire signal perfectly fine. Windows Explorer recognises the signal too - as Panasonic DV Camcorder.
After clicking the Capture tab, the Capture screen is building up, and you can hear a fraction of a second of audio coming through. But then the sound disappears and the video screen remains black. No error message yet.
On clicking Capture Video, my Panasonic camera is instantly identified. By default, the device control selected is MS 1394 and the active device in the options is PANASONIC.
When capturing video with the DirectShow (AVI) or the the MPEG capture plug-in, the following error message pops up: "Unexpected error: This pin cannot use the supplied media type." UVS did actually manage to capture 12 frames of clear video including audio before the error was generated.
I've been searching this forum as well as the whole internet for this error for about 2 weeks, but no Ulead users ever seem to have had this experience before. Is there anybody out there who might be able to point me to the right direction towards resolving this issue?
Win XP SP2
P4 2.4GHz
512MB RAM
80GB disk (50GB free)
Thanks,
Martijn,
Wellington, New Zealand
No firewire signal in UVS9 in WinXP
Moderator: Ken Berry
-
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 Martijn,
I have never heard of or seen that error. You say MF4 sees your device, have you tried capturing with MF4? If not try capturing a short clip, and see if the same happens. It would seem to me that you might have a bad firewire cable, where the signal is not maintained.
When you are trying to capture, do you have any applications running in the background, such as antivirus, spyware, screensavers, internet connection. etc..? You should disable them so they will not spring to life which would take resources from VS.
There is a free program called WinDV http://windv.mourek.cz/, that allows capturing via firewire to DV-AVI format. Try d/l, and installing it to see if you are able to capture. If not then it would be a problem with your firewire cable. Or if you have access to another cable try using it.
What model is your Panasonic Camcorder? Does it record to DVD or tape?
Last question for now, is your camcorder in the Playback mode when trying to capture?
Ron P.
I have never heard of or seen that error. You say MF4 sees your device, have you tried capturing with MF4? If not try capturing a short clip, and see if the same happens. It would seem to me that you might have a bad firewire cable, where the signal is not maintained.
When you are trying to capture, do you have any applications running in the background, such as antivirus, spyware, screensavers, internet connection. etc..? You should disable them so they will not spring to life which would take resources from VS.
There is a free program called WinDV http://windv.mourek.cz/, that allows capturing via firewire to DV-AVI format. Try d/l, and installing it to see if you are able to capture. If not then it would be a problem with your firewire cable. Or if you have access to another cable try using it.
What model is your Panasonic Camcorder? Does it record to DVD or tape?
Last question for now, is your camcorder in the Playback mode when trying to capture?
Ron P.
Ron Petersen, Web Board Administrator
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
-
THoff
-
Martijn
No luck so far
Vidoman,
Thanks for all your (diverse) ideas. None of them were successful I'm afraid.
DMF4 captures from my DV camcorder perfectly fine. So do 3 other programs including UVS6 and WinDV. UVS9 is the only package that generates this error.
I knew about the resident programs ideally having to be switched off, so I had already tried that - my fault for not listing this in my initial post.
I have not tried another firewire cable, but with 4 other programs working without issues and given the fact, that I've been capturing via firewire with UVS9 on W2K without problems since UVS9 came out, we can definitely rule that out.
My Panasonic NV DS50A camcorder (miniDV) has not changed settings since I reinstalled my PC to go from W2K to WinXP SP2. Moreover, it's working perfectly fine for the 4 other programs I tested, so the settings must be OK then.
maddrummer3301 and THoff,
Thank you guys too for your help. I found the advice after maddrummer3301's post, tried it, but there was no change in UVS9's behaviour.
It's a big nuisance to start one of the 4 other working programs and then closing it, opening UVS9 and do the editing stuff for that scene, close UVS9, start the other program, capture etc... I paid good money for the capturing functionality embedded in the editing functions from Ulead's UVS9, so I don't think it's too much too ask, that it will actually work - even under WinXP SP2. Since my first post I have come across 3 or 4 other instances of users having the same issue. It all seems to revolve around UVS9 running under WinXP SP2. None of the other user's issues have been reported to be resolved. I believe this is a bug in UVS9, that Ulead need to fix. I have an outstanding helpdesk call with them, but haven't heard back from them for 10 days...
I will forward the information I found about other users having the same unresolved issue to Ulead and see if they will start working on a fix.
If anybody happened to find or know a resolution for this problem, please let me know. I'd like to continue editing with the great package that VS9 is!
Thanks,
Martijn
Thanks for all your (diverse) ideas. None of them were successful I'm afraid.
DMF4 captures from my DV camcorder perfectly fine. So do 3 other programs including UVS6 and WinDV. UVS9 is the only package that generates this error.
I knew about the resident programs ideally having to be switched off, so I had already tried that - my fault for not listing this in my initial post.
I have not tried another firewire cable, but with 4 other programs working without issues and given the fact, that I've been capturing via firewire with UVS9 on W2K without problems since UVS9 came out, we can definitely rule that out.
My Panasonic NV DS50A camcorder (miniDV) has not changed settings since I reinstalled my PC to go from W2K to WinXP SP2. Moreover, it's working perfectly fine for the 4 other programs I tested, so the settings must be OK then.
maddrummer3301 and THoff,
Thank you guys too for your help. I found the advice after maddrummer3301's post, tried it, but there was no change in UVS9's behaviour.
It's a big nuisance to start one of the 4 other working programs and then closing it, opening UVS9 and do the editing stuff for that scene, close UVS9, start the other program, capture etc... I paid good money for the capturing functionality embedded in the editing functions from Ulead's UVS9, so I don't think it's too much too ask, that it will actually work - even under WinXP SP2. Since my first post I have come across 3 or 4 other instances of users having the same issue. It all seems to revolve around UVS9 running under WinXP SP2. None of the other user's issues have been reported to be resolved. I believe this is a bug in UVS9, that Ulead need to fix. I have an outstanding helpdesk call with them, but haven't heard back from them for 10 days...
I will forward the information I found about other users having the same unresolved issue to Ulead and see if they will start working on a fix.
If anybody happened to find or know a resolution for this problem, please let me know. I'd like to continue editing with the great package that VS9 is!
Thanks,
Martijn
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
You know, there is a setting either in the registry or an ini file that the software is using. I'm sure of this because with all the ulead products if I use a certain version video driver then ulead products generate an error and close or the capturing process isn't correct.
That's when I use the machine with the ATI card in it. I must be very careful if I update the video cataylst drivers using an ATI card. Only for analog capturing though. DV hasn't been a problem.
Here's the point, If I restore the computer to a previous state or un-install the video capture drivers, re-install the ones that did work then all the ulead products "Do Not Work" for capturing. They still don't work.
That indicates a configuration file change.
In one of the ini files there are capture device settings that change when you capture video. Also, in the registry.
If you look close at the ini file the program tries each device line first to connect to.
I've never had time to troubleshoot that problem so I always make sure to have a full partition backup (just because of 1 setting) nice to force me to backup anyway. So it's a bad and good thing anyway.
To the original poster maybe looking into the log files for program errors can point you in a better direction. Also, if you have an incorrect non-existent pointer in the "Preferences" settings for the preview directory causes problems. I did that updating some harddrives and re-assigning drive letters and the program was trying to access a non-existent drive/folder.
Hope this helps,
MD
That's when I use the machine with the ATI card in it. I must be very careful if I update the video cataylst drivers using an ATI card. Only for analog capturing though. DV hasn't been a problem.
Here's the point, If I restore the computer to a previous state or un-install the video capture drivers, re-install the ones that did work then all the ulead products "Do Not Work" for capturing. They still don't work.
That indicates a configuration file change.
In one of the ini files there are capture device settings that change when you capture video. Also, in the registry.
If you look close at the ini file the program tries each device line first to connect to.
I've never had time to troubleshoot that problem so I always make sure to have a full partition backup (just because of 1 setting) nice to force me to backup anyway. So it's a bad and good thing anyway.
To the original poster maybe looking into the log files for program errors can point you in a better direction. Also, if you have an incorrect non-existent pointer in the "Preferences" settings for the preview directory causes problems. I did that updating some harddrives and re-assigning drive letters and the program was trying to access a non-existent drive/folder.
Hope this helps,
MD
You might want to reinstall VS9 to see if you can resolve your problem. I had problems with my capture modules after I installed the plugins, MPEG4 and HD. The HD plugin disabled my analoge capture and the MPEG4 plugin did something esle to my capture capabilities. I ended up reinstalling VS9 and got my DV capture working again.