latency problems - vista/audigy

[mrmulti]

I used to record on my 98 pIII with no latency problems at all with a pinnacle sound card made for voyetra. It was a pain to set up, but after that it recorded midi and digital nicely, with great cut and paste of audio. I decided to try recording on my new Pentium D 266 mhz, and I am having all sorts of problems. I thought it was the sound card, so I used an audigy that I had laying around. I also added 2 gb RAM. I have vista enterprise, and I am using Power tracks Pro, and an old digital orchestrator made for older machines, but it runs for a little while before crashing. What happened on my test is this: the first track goes in okay - seems to be on the beat. but the second one is a few milliseconds off, and it drives me nuts. I know I play on the beat, but the recording is off, so that is why I ran the test, which verified my suspiscions. I have yet to do the test on digital orchestrator to see if that is the reason. I tried ASIO4all v2, but that crashes big time. Any suggestions? I am about ready to refire up my 98 machine.

My midi device is a fantom x6 connected by USB. But all the above problems occur with digital audio recorded - like voice and fantom x6 and guitar. I also have a behringer UCA-220 usb that I had been using, but that would not allow me to record more than one track. I have not tried it after the ram upgrade - iused to have 1 gb.

[tech1]

This problem is called "latency." Check this out: http://www.sweetwater.com/sweetcare/ts/detail.php?Index=30645&keyword=latency

Ultimately, it seems you need an interface with ASIO drivers and some compatible recording software thast offers delay compensation on recordings.

[EC_Beast]

I'd be mighty suspicious of Vista. It doesn't always play nicely with audio recording stuff.

[Justin]

Also the Audigy and X-Fi hardware DSP processors from Creative are not supported by the new audio architecture in Vista. I believe for them to be utilized by Vista Creative supplied a new driver that wrapped them to operated in the new framework. This could be a factor.

[JerryB]

I used to have latency problems. Turned out to be a bad FARrT (file allocation RAM-resident tester). If your machine is FARrT-enabled, you can bypass the offending component by patching in a FARrT TANK (tester algorhythm nullify/kill). This is a simple bit of code that causes the CPU to RAM SNOT (show no test). If, in spite of using the FARrT TANK to RAM SNOT, you continue to have this problem, it is almost certainly an issue of SLIME (slow linear incrementation mode error) in the RECTUM (RAM efficacy calculator to utilize memory) program. If this is the case, an ENEMA (evaluation & negation of errors in memory allocation) utility will usually open things up. (There is a freeware utility called “Poof” that is available on the ‘net, or MICROSOFT will sell you one for $1,745, called “MS Fiber.”)

In other words, I'm clueless...... :banana:

Jerry