RGB, YUY2, Incorrect timing/frequency on everything except MJPEG?

[Phire]

It seems i'm like a magnet to weird problems (Either that or the G400 itself is).

Recently i've been having trouble capturing with HuffyYUV. If I capture anything without using the Hardware MJPEG Codec then I will drop about 2-3 frames per minute REGARDLESS of the resoultion, codec or quality settings.

I E-mailed Markus Zingg and he said that there may be some options in the BIOS where you can set timings up (On ABIT KT7). I have not been able to locate these settings. He also said that the Audio and Video device are not sampling at the proper frequencies, He said it may be possible that the Marvel is changing frequencies depending on the codec used. I'm not sure about this.

But this is what is known. If I disable "Record Audio" then I can capture perfectly fine, I tried 2 hours with full resoultion HuffyYUV and all best settings, only 5 frames were dropped but no audio was recorded. Does anybody know what this could mean? BTW, Im using an ISA Sound Card, but I don't think that makes much difference.

And does anybody else have a KT7 or KT7-RAID which they can test to see if they get the same problem?

[Dr Mordrid]

I guess the first questions should be are: what audio card are you using and what kind of slot it uses?

If it's a PCI card then it's likely using an ISA emulation mode for DOS games & programs. This should be turned off, but where you do it depends on the card. Some have a specific setting in the Device Manager while with others you have to disable the legacy device using Device Managers own disable checkbox.

This alone can reduce system overhead by a lot.

Also you should turn off any special features of the card that uses resources. Examples are 3D, spatial, reverb and other nicities.

Dr. Mordrid


[This message has been edited by Dr Mordrid (edited 22 January 2001).]

[egov]

I've got exactly the same problem, but on top of that the audio is distorted:
http://members.nbci.com/worldwinner1/test.avi

My sound card is SoundBlaster AWE64 ISA.

HELP!

[Nick Pappas]

what slot is the audio card plugged into?

Do NOT plug it into the slot next to the AGP port. This port normally shares an interupt with the AGP port, which might be causing the trouble.

I use AVI_IO too, and have a K7V board... I drop 1-2 frames a minute too, using the built in (hidden) YUY2 capabilities of the Marvel.

The video is raw YUY2, so it is huge, but the audio is synched up ok with a SB 16 AWE.

Nick

[Dr Mordrid]

K7V 'eh?

Perhaps this is a PCI bandwidth vs. VIA KV-133 chipset issue. Even with the Athlons the KV133 is known to have remnants of this persistant VIA issue.

The KT133a boards MAY not exhibit this problem due to their ability to use a 266mhz FSB. Look for the VT8363A North Bridge controller and the VT82C686B South Bridge controller.

Dr. Mordrid

[Phire]

I'm using a SB 32 which is in the ISA Slot, it is not sharing any resources with any other devices. I've tried many combinations of disabling its features. I did disable it's use of 2 dma's (Emulation features) becuase if i didnt then I would get audio crackles, this makes no difference to my problem though, i restored it to the original settings same thing. I disabled many features of the sound card, I even manually set the resources the card uses, nothing works.

[Flying dutchman]

You say that "recently" you have problems- did it work before? What did you change? Have you tried a fresh setup on a "clean" hard drive?

I contemplate buying a KT7A board as well, so it interests me!

[wkulecz]

Try turning of "Spread Spectrum Clock" in the BIOS. It has helped some Via problems. May be a long shot, but its rather painless to try.

Spread Spectrum Clock is a hack to meet EMI specs. They modulate the clock which spreads out the noise so the narrowband analizers used in the EMI tests read lower! Expect the next round of EMI test standards to be adjusted to make this trick fail!

Having the cpu clock not be a fixed frequency can cause all kinds of havoc with things that depend on the N clock ticks being a certain number of microseconds.

I mention this because I think MJPEG uses its own clock for timing.

--wally.


[This message has been edited by wkulecz (edited 24 January 2001).]