Error codes 15001:33:1 & 15023:4:2

Moderator: Ken Berry

daveaegginton

Error codes 15001:33:1 & 15023:4:2

Post by daveaegginton »

I get a message unable to switch to capture mode. Check if your video capture driver is working properly. Failed to build a preview graph. I'm using VS9. If i click OK I can still capture but not had this problem in the past. Anyone else experienced the same and any fix would be great. I am using firewire to transfer.
ostech
Posts: 6
Joined: Tue Dec 19, 2006 5:04 pm
Location: Antigua

Capture failure.

Post by ostech »

Hi,
Sorry to cut in on your post but I have had some directions from the experts on this forum which I believe is very sound. I have tried everything but messing with dll. and nothing seem to work. I substituted the fire wire card in another computer with less programming capacity and it worked. Ther working computer specs are: Celeron 1.7 80gh hard drive 512 ram VS10 plus. No previous VS installed. The computer it did'nt work on: Celeron 3.06 1gb ram, Hard drive 200 & 80 fire wire card and JVC minidv camcorder GR-D270U. Both computers are xp(pro) sp2 The more powerful comp. has active X 9. I have posted be fore and have done a lot of reading. I suppose we both need help Thanks all.
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
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

Post by Ken Berry »

Dave -- what are you trying to capture, in what format and using what capture devices or connections? If, for example, you have a mini DV digital video camera, it should be connected via firewire and switched on in Play mode before opening Video Studio (though often VS will recognise it if it is switched on with VS already open)...
Ken Berry
daveaegginton

Post by daveaegginton »

Iam using a panasonic mini dv camcorder conected via firewire.If I click OK on the error message I am able to capture video. It is a message that has only just started to aappear. Have been using vs for sometime now and never really had many problems other than crashing occasionally.
a097005

Post by a097005 »

I'm having this same problem, except that I cannot capture at all. Same error message though. I'm also using a fairly new Panasonic DV camcorder (PV-GS39) connected to a Windows Vista machine via firewire. I've checked Panasonic site for driver updates and its pathetic. There's nothing.

I notice that no one has replied on this thread since January, and that the same issue is unresolved on other topics. I can capture using Windows Video import, but I'd rather use the tools in VS, and I believe this function should work correctly -- its a core function of the program???
leopardeau

Post by leopardeau »

I've also the same concern, error 15001:33:1.
I use a camcorder sony HC3E in HDV and windows vista. I have uploaded the Ulead pack for vista.
The acquisition is possible if the camcorder is switched to DV mode . It is impossible in HDV mode.

The pilote for the camcorder is OK and the acquisition in HDV works with Windows Movie Maker.
I have uninstalled and re-installed videostudio, but the problem persists.

Sorry not help in the discussion, but at least you will know that you are not alone... :cry:

Have a good day.
AlBunda

Sharing the 15001:33:1 problems ...

Post by AlBunda »

Hi, there,
I don't feel my issue urgent right now but still I would like to get some understanding ... so this thread that is a bit dead seems to me appropriate to add my story.

- I have not experienced the errors until the last sunday and in the past I was able to capture from SONY HC22 without any problems.

Now I have a new camcorder - Panasonic NV-GS230
- I use Firewire.
- Capturing was OK using Windows Movie Maker. Only in VS10 I got that error message when I was going to start capture. It was possible to use the control buttons and also to start/stop capture but without preview.

- When I got that error first time I was attemting to play with 16:9 mode. Started theVS with that checkbox and wanted to capture a scene that was shot in the wide mode. Since then I have been getting the error no matter if I play with 16:9 or 4:3
- But all my subsequent attempts were in 4:3 ratio
- After I got the error for the first time I uninstalled old Sony/Pixela software
- I also tried to change the Tools\Select Capture Device to MS 1394 and back to None
- I ran the VS DV Quick Scan - which did not popup with any error.
- When I attempted last time - i still got the error popup but when I hit start capture, the picture suddenly appeared in the preview. The capture seems to have completed without problems

I don't know if that means it is fixed and what 'fixed' it...
I searched this forums yesterday and found quite wide range of VS versions, usage conditions so if you happen to know what can be an ultimate cause to this, please share with me.

Thank you
Debenel
Posts: 7
Joined: Sun Oct 25, 2009 10:54 pm
Location: Canberra, Australia

Same error... help please

Post by Debenel »

I'm getting the same error with a similar set up, and I've been through most of the fixes proposed so far. This problem is the reason for me joining this forum! I've had a good couple of years using VS10 to capture and edit video trouble free direct from camcorder through DV firewire, and suddenly one day it all just falls over and Corel have washed their hands of supporting the problem. Thank goodness forums such as these exist, as it seems I am not alone with this problem!

Properties of your source files, including video, audio, image files (format, file size, where did you get it?):
DV camcorder

What devices are involved and their mode of connection?:
Panasonic NV-DS65. It has both DV and small USB ports but Panasonic assure me that the USB port is only for transferring still images. never had problems with it before.

Project Properties (important):
?? home video?

Output format (file, DVD, VCD, SVCD):
normally capture as wmv or avi, then use VS to create DVD

Output Properties (cogwheel in lower left of burn screen):
Hmm. cant see a cog wheel in VS10

PAL or NTSC:
PAL

Error Codes (if any):
Unable to switch to Capture Mode
Check if your Video capture driver is working properly.
Failed to build a preview graph.
[15001:33:1]
[15023:4:2]

Operating System: XP
Motherboard: Gigabyte GA-p31-ds3l
Graphic Card: unknown (how do I confirm this?)
Sound Card: RealTek AC'97
Processor: amd athlon x2 dual core
Hard Disk Drive:
Memory: 2GB RAM

What is weird is that when I connect the camcorder, I am able to control it via the controls on the PC screen (play, fwd, rew etc) and can watch what happens on the camcorder screen, but VS10 is not capturing OR displaying anything in the preview. Also I have found the error happens when I select capture without anything being connected.

Fixes tried:
1) Checking camcorder specific drivers
Panasonic say there never were any to install that came with the camcorder and XP should be retrieving the right one.
Through troubleshooting in device manager the sysems says device working properly so troubleshooting does not work, and trying to find a more recent driver does not find a more recent one.
2) in VS10, change capture plug-in
Error repeats whatever plug in I select.
3) Changing file-preferences.
There was a suggestion in a related thred to select the preview window. I think I've done this to no effect. (cant figure out how to attach a screen shot)
4) reinstalling VS10.
didnt help
5) use VS editor, movie wizard, AND DV to DVD wizard
none work.
6) use windows movie maker to capture
says 'the video device is in use' please close any other applications' this happens regardless of whether VS is open or not.

One of the other threads related to the same error but for VS10+ included renaming dll files- I havent attempted this.

From a systems approach, and given that movie maker has similar issues it would appear that the right driver isnt in the right place, but the only possible cause is VS10 itself or windows as no software has been installed since VS10 except virus software updates and windows updates. However, I dont have the skills to know how to confirm which drivers are in there, which is the right one, and how I fix this.

can anyone help?[/img]
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
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

Post by Ken Berry »

Panasonic is correct in saying there were no special drivers/codecs that had to be installed, as the DV/AVI codec comes as part of Windows, as does the IEEE1394 (Firewire) driver...

Since Windows Movie Maker comes up with the same problem, I would think it is likely to be a Windows update which is the culprit... We find that more often than not, an update of DirectX rectifies this sort of problem... Have you tried that? There is a sticky thread at the top of this forum with a link to the latest update. Note that DirectX is not updated automatically as part of Windows updates. You have to do it manually.

As for the cogwheel icon, it is there in VS10 -- the middle of the three icons in the bottom left of the burning module...

Good to talk to another Canberran... Which part of the city do you live in?
Ken Berry
Debenel
Posts: 7
Joined: Sun Oct 25, 2009 10:54 pm
Location: Canberra, Australia

no change

Post by Debenel »

G'day from the inner south, Ken! didnt spot there was a canberran moderator, though I would imagine we're the only two actually awake and using the forum right now.! which part are you in?

direct x updated and retried capture.
ulead thought about it, then showed a new error message saying file was corrupted and will be deleted. now I cant get this to replicate.

any further ideas?
User avatar
Ken Berry
Site Admin
Posts: 22481
Joined: Fri Dec 10, 2004 9:36 pm
operating_system: Windows 11
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

Post by Ken Berry »

I'm afraid I really don't have any other ideas. It is curious that the computer can 'see' the camera, but none of the programs can capture from it. The only other thing I can suggest at this stage is to vary the way you turn on the camera. If you turn it on to PLAY, then open VS, try doing it the other way round -- turn on VS first, then the camera. Or vice versa. Some people have found that works, though in the fairly dim distant past.

I live in Melba...
Ken Berry
User avatar
Ron P.
Advisor
Posts: 12002
Joined: Tue May 10, 2005 12:45 am
operating_system: Windows 10
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

Post by Ron P. »

You could also try using WinDV. If it fails then there may be something wrong with your cable, card or firewire port on your camera.

Did you apply the Vista patch for VS10? This would cause another issue, related to using your camcorder as a pass-through, analog-digital conversion. Without the Vista patch VS10 should be able to capture analog without any problems, especially on an XP machine.
Ron Petersen, Web Board Administrator
Debenel
Posts: 7
Joined: Sun Oct 25, 2009 10:54 pm
Location: Canberra, Australia

more tries

Post by Debenel »

Thanks for the hints guys.
okay, the error message itself is not showing, just a window that says 'failed to build preview graph'.

also tried:
1) WinDV loaded but cant get it to work at all- just shows error:error at the bottom.
2) As far as I know I dont have a vista patch installed, but I dont know how to go about checking which patches have been installed- I think (possibly wrong) but I bought VS10 before Vista was released and have not downloaded updates from Corel since installing it.
3) taking out dv card and reinstalling it. done but it didnt run through any new hardware routine that I could see.
4) tried with another camcorder (Sony NTSC- to see if it makes any difference). no change, can still control the camera through the I/F on the Ulead screen. might suggest it's not the panasonic camcorder at fault.
5) tried with Movie maker and DVD Power Producer suite. does not function in capture but both applications can 'see' the camera.
6) changing order of switching things on. no change. if I turn on cam first it gives me the option of capturing via VS10, same symptom.
will try a new firewire cable next. I am currently thinking it's not worth rushing off to buy a new version of VS if the problem is not with the software.

any ideas wrt checking which video capture drivers are installed?
Black Lab
Posts: 7429
Joined: Wed Dec 15, 2004 3:11 pm
operating_system: Windows 8
System_Drive: C
32bit or 64bit: 64 Bit
Location: Pottstown, Pennsylvania, USA

Post by Black Lab »

Certainly doesn't sound software related if you can't get several different apps to work. And since you also tried a different cam I think you can rule that out too.

Don't forget to also check the firewire card itself, making sure it is properly seated in the slot.
Debenel
Posts: 7
Joined: Sun Oct 25, 2009 10:54 pm
Location: Canberra, Australia

still no joy.

Post by Debenel »

Now I'm really stumped.

Tried a new Firewire card with a new firewire cable.
Same error: 'failed to build preview graph'
BUT I can still control the camera via the on screen interface.

any ideas?
Post Reply