I have problems with an ADS Pyro 1394 DVcapture board (PAL system)on my new configuration composed of :
Abit KT7 MO Bo (VIA KT133 chipset)with AMD Duron 600MHz processor and 128 Mb RAM,
20 Gb 7200 rpm HD
ATI Rage Fury Pro graphics card
SB 128 PCI sound card
Windows 98 SE with DV update
TI DV capture drivers (MS drivers don't work with my Canon MV 200i video camera)
I have checked the performance of both the CPU and HD which are really good.
I have checked the DV capture bord on another configuration with no problems.
What happens is that I loose frames during capture and export to tape (between 1 and 5 %).
Surprinsingly, I managed to capture without loosing frames by unchecking the DMA property of my HD (with of course far less HD performance as verified by performance checking tools). But even if it is possible to capture that way it doesn't apply for exporting back to tape.
It seems that there is a conflict between the capture board and the HD for bus master or DMA.
Has anyone encountered such a problem ?
If there is definitely a compatibility problem between the capture card and my mother board is there any other DV capture board which would have been tested successsfully with this board ?
Thank you for any answer or comment.
I have also put forward the question to manufacturers (ADS, Abit and Via). If I get any answer from them I will have the group benefit of it.
http://pub9.ezboard.com/fpyro1394faqs.showMessage?topicID=34.topic
IMO use an Intel chipset for Video editing, Good luck to the people who can use other chipsets fine, there are some success's
johnpr98
Home Page With ADS Pyro Info & Examples
ADS Pyro & Ulead VS & MS Pro 6 Forum With Tips & Info http://www.johnpr98.com
John Price ADS Technologies PYRO forum http://www.wwug.com/forums/ads-tech/index.htm
There are two schools of thought about this issue.
One says, always use the hard disk controller software supplied by the motherboard maker.
The other says always use Windows's own.
I don't lean one way or the other but, if you are using the motherboard's own hard disk controller software, then you could try removing it from system properties, rebooting and ensuring that when the controller is detected on booting into windows, that you point it at Windows own driver.
Before doing this, I would recommend making a FULL back up on the boot hard disk of the entire Windows folder.
To do this, open the Windows folder and ensure that the view option is set to "see all".
Create a folder (say, WinOrigi.nal) and then copy into it EVERTHING from the existing Windows folder, other than Win386.swp - Windows' swap file, which is HUGE, and not needed because it is recreated the instant WIndows starts. I do this by first selecting Win386.swp, and then choosing "invert selection" from the edit menu.
The reason for having this back up is so that, if everything goes pear-shaped, you just start in DOS (from boot up) and rename the two folders.
If you are unfamiliar with DOS, here are commands you need to use
ren Windows Badwind.ows (for example]
[This renames the Windows folder to Badwind.ows. A single space is needed between each of the three words]
Then type
ren WinOrigi.nal Windows
[This takes your backup folder and renames it to Windows - again the spaces are important]
In each case above, you need to press the Return key to execute the command.
On rebooting you'll be back where you started before dabbling, and can then, if you wish delete the folder that is now called Badwind.ows
Before you do remove the HDD controller driver [and it may be best to do this removable after restarting in Safe Mode), make absolutely sure that everything has been copied from the original Windows folder to your backup folder.
Open each folder, choose select all in each (remember to then deselect Win386.swp in the current Windows folder - by holding Ctl and clicking on it) and right click on the blue, highlighted files, and select Properties.
What the Properties windows should show you is that each folder has the same number of files and folders and is the same total size.
The above would be my first step!
If this did not help, then I would try juggling with the order of the cards, which is a real pain, cos you've got to take them all out, except for the graphics card, and then restart, close down, add another, restart, etc etc.
Sometimes it is important NOT to have a card in the PCI slot directly next to the AGP slot (assuming you are using an AGP graphics card). If there are not enought slots to leave on free, then ensure that the editing card does not go in the one nearest the AGP slot.
Oh, and of course, I would do the above back up before do a card-shuffle.
Bob C
Hey Bob !
Thanks for your suggestions, but I have already done all that without any change.
I have got other suggestions that I will test (possible problem with SB PCI sound card for instance)that I will test.
I will inform of any progress anyhow.
And thanks to all to send any other suggestions.
Georges