IRQ Conflict - Windows XP - Print to tape dropouts

GregA wrote on 12/19/2001, 9:56 AM
I have a new Dell Dimension 8200 running XP. I was having the same dropped frame problems I have read about in the forum. I checked the IRQs and found that my firewire card and my video card are sharing IRQ 16. I went to the Dell support site and looked up changing the IRQs and my understanding of what it said was don't change them - it is okay for them to share, and that XP differs from the earlier Windows versions in this regard. I assume I still need to change the IRQ, but am obviously concerned I will mess something else up. The IRQ discussions previously did not seem to address XP directly. Is there something new to try with it? Thanks for the help.

Comments

discode wrote on 12/19/2001, 11:59 AM
PCI devices are required to be able to share interrupts (IRQ's) by the PCI specification. However this does not insure that the devices will function properly when sharing IRQ's. I would definately still change the IRQ that the firewire card is on. The easiest way to do this would be to physically remove the card and put it in a different PCI slot if you have one available. If that doesn't do the trick then check out www.microsoft.com to see if they have an explanation of how to assing IRQ's in XP.
GregA wrote on 12/19/2001, 12:06 PM
Thanks for the info. The other thing I was going to try was to install the capture card that came with the program as well and hopefully it will pick a different IRQ.
frostg1ant wrote on 12/19/2001, 11:58 PM
WinXP uses ACPI for IRQ usage. I would not recommend changing IRQs in WinXP. A good firewire card should (and will) share the PCI bus.

Concerning the dropped frames...has anyone used a competing program and experienced no frame loss? I am very curious if this is truly a hardware/OS issue or perhaps a problem with VF specifically? Don't get me wrong...I love VF, but I am tired of chasing my tail with the dropped frames.

frosty
garylon wrote on 12/20/2001, 1:08 AM
I'm on XP as well; I cannot get my IRQ changed for my Firewire card. It is definitely on 9, along with my sound card, video card, and network card. Sounds nuts to me, but they're all there and none of them want to change - no matter what I do. I'm also begining to get very frustrated with this - I cannot get my video back to my camera without losing frames - or 'signal'. I've updated to 2.0b, I have the latest DirectX, the latest drivers for all hardware involved, bought a new firewire cable - nothing seems to work. I feel like I'm at an impass - any other suggestions?
GregA wrote on 12/20/2001, 11:19 AM
I have been reasonably successful in doing this. I could not change the firewire card that was already installed in the computer so I installed the one that came with the software in the empty slot I had left. It assigned it to IRQ 19 which was shared with one of my USB ports. I disabled the USB so only the firewire is assigned that IRQ. I printed my program to tape and it worked. When I reviewed the tape on my TV, I did notice that there were at least 2 place where the picture seemed to freeze for a second and then it continued. It did not look like the issue I was having before where the entire picture was lost and then came back in little blocks. If anyone has any suggestions on this one, I would be most appreciative. The picture looked great and the audio was fine. I just don't know if I should expect this all the time or if I can get a program to print to tape without any problems.
garylon wrote on 12/21/2001, 12:27 AM
I have downloaded some other shareware, but none let me save back to my DV to compare. I was expecting VF to just work, so I wasn't planning on purchasing other software to test. XP does not allow the changing of IRQs - I've tried everything (it seems). Support guys, any other suggestions on this? Any other ideas are appreciated. Thanks -
discode wrote on 12/22/2001, 1:58 PM
In order to be able to change the IRQ assingments manually you would need to disable ACPI. Generally this involves loading a standard PC HAL (Hardware abstraction layer). I am not absolutely sure how you would go about doing this in XP but generally it involves specfiying a standard PC HAL when installing the OS. Take Win 2k for example. When installing you reach a point at the very begging of the installtion that tells you to hit F6 if you need to load 3rd party SCSI or Raid drivers. You would instead want to hit F5. You can then specify to load a standard PC HAL. This effectivly disables ACPI and will allow you to manaully distribute IRQ's in the same manner that you were able to with Win 98. Where this option is located at in XP or how you do this would be something to look up at the www.microsoft.com. However this might be a heavy handed solution to your problem. I would begin with the typical stuff like make sure that DMA is enabled on your hard drive. If you motherboard has a VIA chipset make sure that you have installed the latest 4 in 1 drivers from VIA. Make sure your drives are defragmented. Try capturing something from your camera and then printing it directly back to tape without even doing anything to the clip in Video Factory. Also to clarify my previous post. You should be able to have multiple PCI devices sharing an IRQ without an issue. However you can run into problems when your capture card is sharing an IRQ with any other device simply because the amount of data that the card is trying to deal with. Take the example of having your video capture card and your display adapter on the same IRQ. Both of the cards are trying to deal with lots of data at the same time sharing the same resources. I can see the potential for problems here. To be quite honest it should work without having to do all of the IRQ changing but in practical application it does not work all the time.
frostg1ant wrote on 12/23/2001, 11:17 AM
I am hesitant to post this because of the risk in changing something like this. Please proceed at your OWN RISK. I cannot confirm that the below process works in all instances/hardware configurations.

And *please* if you DO decide to do this post back and let us all know if it fixed your dropped frames problem!!!

--

Disabling ACPI in WinXP --- Simply turn it off

Device Manager
Computer -> Update Driver
Install from a list or specific location
Don't Search. I will ...
Select: Standard PC

Reboot, and let XP setup your hardware again, start your IRQ customization to make sure the firewire card is by itself, and finally check your capture to disk.

--

Hope this helps...

frosty
deef wrote on 12/27/2001, 9:01 PM
Yes, I've heard the previous 2 posts before and they seem to work.

Also:

Please check out this FAQ:

http://www.sonicfoundry.com/support/SupportProduct.asp?FamilyID=52&Family=VideoFactory&TopicID=78&DetailID=879

Numero uno: make sure DMA is enabled for the drive via Device Manager.
garylon wrote on 12/29/2001, 11:36 PM
I would like to confirm that this solution has indeed worked for others with the same problem. I did not have such luck. I disabled the ACPI, then was able to finally get my IEEE card onto it's own IRQ (thanks for the instruction on that!). I was so excited when my 30 minute video not only got past 2 or 3 minutes, but actually to 11 before the same thing happened again. Then, it happened right away with a 60 second movie (after re-booting). I'm out of answers now - any other suggestions? I've also followed all of the advice in the article posted in the KB on this topic.
deef wrote on 12/30/2001, 8:24 PM
What are all your system, OS, DV device specs?
deef wrote on 12/30/2001, 8:25 PM
Including mobo and hard drives.
garylon wrote on 1/1/2002, 8:15 PM
Win XP (5.1.2600 build 2600)
AMD Thunderbird 900 MHZ
512 MB Ram
MB: ASUS A7Pro ACPI BIOS 7/24/2001 (latest version)
Video Card: NVIDIA GeForce2 MX/MX 400 32MB
Hard Drives: IBM Deskstars 30GB & 60GB
Camera: Sony DCR TRV-530 NTSC
IEEE card: Texas Instruments OHCI IEEE 1394 Firewire card
garylon wrote on 1/5/2002, 2:53 PM
Deef, any other ideas or suggestions on how I might solve this?
Targa wrote on 1/5/2002, 6:24 PM
Try www.creativecow.net "Good Luck Z"
SonyEPM wrote on 1/7/2002, 10:15 AM
Please confirm that DMA is enabled for all IDE drives. You may also need to defrag your drives- both of these can make a big difference.
hmag wrote on 1/12/2002, 11:21 AM
Okay,

I am having the same type of problem that you are all discussing. I am using Vegas Video 3.0 instead of video factory but I also tried using a different software package (ulead) and am experiencing the same thing. I am able to capture from the camera just great but I get a lot of dropped frames when printing to tape. I have heard several people suggest that I first look to see that DMA is enabled on my HD. . . Done.

Next the IRQ issue. Well my firewire card is sharing the same IRQ as a couple of other things but is this really the solution? I haven't heard anyone yet that has successfully found a solution by overriding this. I really don't believe that this is a VF or VV3 issue because I was able to duplicate it with another program. It seems to be more of an issue with the VIA chipset Motherboards or a Win XP issue. Isn't there some brainiac hardware expert out there that can help us here?

here is my hardware setup. What am I doing wrong?

Athlon XP1600
ASUS A7V266-E motherboard VIA KT266A Chipset (New board just released about a month ago)
512 MB ram DDR
75GB HD IDE 7200 RPM
nvidia Gforce2 DDR (video card)
Firewire card - ADS Pyro - basic IEEE 1394 (texas Instruments)
Windows XP

Using a Sony DCR-TRV20 Digital Video Camera
hmag wrote on 1/15/2002, 1:07 AM
I just want to let everyone know that I have been experiencing this same problem while running Vegas Video3. I have done everything suggested in this discussion (enable DMA, change IRQ settings, update all drivers etc.) to no avail. I am still getting the dropouts just as they were previously. Is this just a Win xp issue? Is anyone else having similar problems running a different version of Windows? I tried a different program (Ulead Video Studio) to see if it was something related to Sonic Foundry software. Guess what? Same results

I am pretty certain that this is a hardware issue related to either DirectX - VIA chipset Motherboards - win XP. I am at a loss to figure this out and it is driving me crazy!!!

Is there anyone at Sonic Foundry that can help us? Are there any hardware brainiacs out there with any other possible solutions for this?

FYI - my hardware setup is:
Athlon XP1600
ASUS A7V266-E motherboard VIA KT266A Chipset (New board just released about a month ago)
512 MB ram DDR
75GB HD IDE 7200 RPM
nvidia Gforce2 DDR (video card)
Firewire card - ADS Pyro - basic IEEE 1394 (texas Instruments)
Windows XP
Using a Sony DCR-TRV20 Digital Video Camera
SonyEPM wrote on 1/15/2002, 8:38 AM
Hmag posted a similar post on the Vegas forum, so I'll do the same: Please list your IRQ layout in this or the Vegas forum.

To get the list, go to: Start>Programs>Accessories>System Tools>System info>Hardware resources>IRQs

If you see a bunch of stuff on IRQ 9 THAT IS LIKELY THE PROBLEM. Once you post the list we can take it from there.
DougHamm wrote on 1/15/2002, 6:18 PM
For the record, I've got an Abit KT266A-based board with WinXP and I've got similar issues - I can print to tape well enough but it's during real-time previewing out to firewire that my frames drop.

-Doug
hmag wrote on 2/13/2002, 5:40 PM
Ok,

well it has been a couple of weeks since I last tried fixing this problem. Finally today I found a solution. It seems after trying all of the above suggestions, along with every other possible thing I could think of. I sought the advice of my friend that built the machine for me. We tried my firewire card on his machine and got the same results. His guess was that there is just some sort of conflict with the Texas Instruments chipset on my firewire card and the VIA chipset on my motherboard that hasn't been resolved yet. He suggested that I try another firewire card with another chipset (preferrably a VIA chipset if I could find one) Well sure enough I went out and got myself a new 1394 card made by SIIG and it works great! YES YES YES YES YES!!!!!!! Oh . . . by the way it does have a VIA chipset. I'm not sure if my other card is bad. I suspect not, because it was working great for capturing from the tape but it was the printing to tape where I was experiencing problems. Anyway . . . If there is anyone that is using a TI chipset 1349 card and has the newer VIA chipset (KT266A) motherboard and is experiencing these similar problems, then you might want to try a different 1394 card. check out: www.siig.com
melprice wrote on 4/10/2002, 11:43 PM
I've tried it all. Card in a different slot. Disabling ACPI then making sure the 1394 card had its own IRQ. I originally had an ATI DV Wonder, I've since tried 2 other cards including a SIIG as suggested by the last poster.

Nothing works, I'm at a total loss as to what to try next. I can't print a single project back to tape. My HD is now full and I can't continue until I get some of the footage off.

What's left, does anyone have any more ideas.

Thanks in advance.
Grazie wrote on 4/11/2002, 1:35 AM
Okay - I'm using WinMe and the above frustrations might/will not relate to this thread, and the success I'm having. But here's my pennies worth.

I don't print to tape using VF. I use Studio7. I render the whole video project within VF. Close VF and fire up S7, load the DV-AVI and then send this to my VCR. This I have found to work without - and as far as I can tell - any dropped frames.

My experience might not "cure" the issues above, but has allowed me to get on with the business of producing VCR tapes, all via a standalone Hollywood Dazzle Analogue-Digital-Anaglogue convertor!

Oh yes... I'm using a TI 1394 firewire port and I have IRQs being shared by video card, USB devices - I think I've got 4 items on IRQ11 - etc etc


Grazie