KVR Audio

Internal Exodus · Post by **Internal Exodus** » Fri Nov 26, 2004 5:52 pm

Well, after I tamed the farty-note problem for the most part (thanks to your help guys

), I was able to work semi-comfortably with SX. This morning however, as I was finally starting to bounce some of the midi down to audio, I would consistently get crashes with Cubase, and then, as such, with my computer in general where I'd face that blue screen of death. I'm running about 5 instances of the Waldorf A1 (yep, the one that still kinda gives me problems with farty-notes) and 1 track is controlling my Korg MS2000B. While everything was in MIDI, the screen would stutter a bit but play pretty fine, and when I'd record the audio on 2 of the MIDI tracks, things went okay too. It was when I tried to record that 3rd audio track that things got f**ked. I've frozen the instruments I already bounced down to audio and now I'm not exactly sure how to handle this since Cubase is now pissy at me for working it so hard. Anyone have any advice? I think I'm gonna do a few more system tweeks and see how far that gets me and do a disk clean up (although I just did one a couple weeks ago), but if that doesn't work, I'm yet up shit creek once more.

If anyone can help a poor, ignorant soul even further than he already has been or deserves, it'd be greatly appreciated.

Sahul · Post by **Sahul** » Fri Nov 26, 2004 6:33 pm

Have your already tried raising the latency of your soundcard?

Internal Exodus · Post by **Internal Exodus** » Fri Nov 26, 2004 6:39 pm

Heh

Actually, I hadn't. I'm using the Audiophile USB, what would be a reasonable level to reset it as?

bluedad · Post by **bluedad** » Fri Nov 26, 2004 6:40 pm

I don't understand why you're having problems (but believe me, I sympathize having gone through problems myself all hardware related)
Still, what soundcard do you have?
In additition, make sure the hd you've been directing your audio to is defragged.

ahja · Post by **ahja** » Fri Nov 26, 2004 6:46 pm

BSOD (blue screen errors) ussually mean you have hardware issues. I'd read up on BSOD, write down the error you recieve 0x00000xx (example) and look it up.

Sahul · Post by **Sahul** » Fri Nov 26, 2004 6:50 pm

Well, in theory the bigger the latency, the less stress you put on your CPU. Try a setting of 46ms or so, just to see if your problems get better.

Internal Exodus · Post by **Internal Exodus** » Sat Nov 27, 2004 6:08 am

I did the Latency thing, and that seems to be doing the trick so far. Do I have to change the latency each time I go to bounce to audio and back though?

kritikon · Post by **kritikon** » Sat Nov 27, 2004 7:07 am

I did the Latency thing, and that seems to be doing the trick so far. Do I have to change the latency each time I go to bounce to audio and back though?

Not really...it depends what latency your running at normally. Some people seem to be obsessed with ultra low latency, and I personally don't see what benefit it gives you. Anything midi sequenced within SX2 will have PDC to correct it. For live playing, I've never noticed any lag at 10mS or even higher. At present I'm running my system at something like 7 or 8 mSecs but I'll probably raise that some time soon. I could get lower if I wanted but I see no purpose in straining the PC.

On my old PC I used to run it at 50mS to squeeze out every drop of CPU, and it never caused any problems. If I wanted to play in a riff, I'd do it with an external h/w synth on a similar patch to get the midi pattern and then change it to whatever VSTi I wanted afterwards. Even if I wanted to play in a riff with a VSTi, I never went below 10mS and I never felt it was audible. Midi lag on an awful lot of synths is greater than 10mS and nobody complains about that delay...so why is it an issue in a PC? Especially now SX has full PDC on every possible channel you really shouldn't need latency under 10mS. Bouncing to audio from midi is compensated - why would you need to change the latency?

From one problem to another....(SX2.2 again)