cubase 6.5 ,win7 64bit home, fa-66,audio dropouts

[flugel45]

Uh, why so rude? I was trying to help you.

1. How can you help me if may be the same problem is reproduced on your PC?
2. Why you try to resolve Cubase owners problems, if you aren't having Cubase and even don't know what is ASIO performance.
3. Resolving problems by buying new PC's it is really great idea:?:

1. I've said absolutely nothing about your problem being reproduced on my PC. In fact, the exact opposite is true (My two PCs with FW audio are working just fine).

2. Why in the world do you think your problem is Cubase-related? I have been trying to get it through to you that the poor performance you're seeing is likely to do with your system setup, or audio interface drivers. This is why I suggested trying ASIO4All - to possibly narrow this down. You called it a "stupid idea".

3. I was being sarcastic...

Okay, it's occurred to me that you're not just being argumentative.... and that part of the problem here may be a language barrier. You seem to be having difficulty understanding anything I say.

The only thing I can suggest at this point is to post your problem in your native language (In this forum, or any other where there's a chance another native speaker can see it and help you).

Good luck.

[jancivil]

the problem here isn't going to be blamable on the host. audio dropouts could be a couple of things.

one very common problem is a manifestation in some way of: you need more time for the CPU to do the math. this is going to owe to a slow - read distant - connection (or an otherwise sub-optimal connection) from the drivers of your audio interface to the CPU. where is the firewire connected to in the motherboard? is the firewire chip the problem. et cetera. are the drivers of the audio interface reported to be difficult, or known to be poor.

(really good performance is going to come from a fast - physically proximal - connection to the CPU. the fastest is a PCI-e card in the North Bridge.)


one must look at this area before considering the OS's defaults; albeit I recall XP tweaks galore per the machines of that era. I turned most of XP off but I fear this resulted in instability ultimately.


The original post mentions the problem - significant length dropouts - occurring at increasing intervals of time. I would run a check on the RAM here.

[jam92189]

FWIW, I'm on Win7 x64 with two different FW interfaces: TCE Impact Twin and Presonus Firestudio Mobile.

Please can you check if there are audio dropouts with 90% ASIO Performance Level and 16 ms ASIO Latency on your Win7 x64 PC?

I have E-MU1212M PCI + E-MU0404 USB + TASCAM US-800 USB ASIO interfaces with x64 drivers.
DAW - Cubase 6.0.7 Full

16 ms? That's kinda high. I usually set it at 256 or 512 samples - which gives me 5-10ms latency - and just leave it. No glitches or problems... but I never go beyond about 60% cpu usage.

I don't have a ASIO performance level - is that an E-MU thing? Or are you talking about cpu percentage? (If so, I would never push it that hard).

I also should have mentioned that my hosts are Studio OneV2 and Sonar X1. Have never used Cubase on my current system.

its true with newer computers that are optomised you can really get alot of performance and low level of latency on my pc 256 samples I get about 5ms total. I go to half that when I record though but no problems here and im no windows 7 64bit using reaper.

[jam92189]

it also has to do with how fast your computer it. how much power does it have. My i7 is clocked at 3.6 GHZ 4.0 with overclocking.

[krandr]

1. I've said absolutely nothing about your problem being reproduced on my PC. In fact, the exact opposite is true (My two PCs with FW audio are working just fine).

2. Why in the world do you think your problem is Cubase-related? I have been trying to get it through to you that the poor performance you're seeing is likely to do with your system setup, or audio interface drivers. This is why I suggested trying ASIO4All - to possibly narrow this down. You called it a "stupid idea".

3. I was being sarcastic...

Okay, it's occurred to me that you're not just being argumentative.... and that part of the problem here may be a language barrier. You seem to be having difficulty understanding anything I say.

The only thing I can suggest at this point is to post your problem in your native language (In this forum, or any other where there's a chance another native speaker can see it and help you).

Good luck.

1. My request to check the problem on you PC was rejected by you. Why it is so difficult?
2. Different DAWs - difirrent audio engines, different audio drivers,different problems. Cubase supports only ASIO interfaces. Yours Sonar - ASIO, MME, KS

[flugel45]

1. My request to check the problem on you PC was rejected by you. Why it is so difficult?
2. Different DAWs - difirrent audio engines, different audio drivers,different problems. Cubase supports only ASIO interfaces. Yours Sonar - ASIO, MME, KS
3. Problem is already posted at microsoft forum.[/quote]

Wow. Just... wow.

Oh well. I tried.

Good luck with Microsoft consulting on your "Cubase" problem. The call transcript should be hilarious, and just may become the stuff of legend.

Fingers crossed.

[jancivil]

Different DAWs - difirrent audio engines

irrelevant.

different audio drivers,different problems. Cubase supports only ASIO interfaces.

irrelevant.

Yours Sonar - ASIO, MME, KS

irrelevant. you cannot blame the host for your system's issue. yours needs a lot of latency, period. there are reasons for it which are addressed in this thread. you aren't going to get anywhere the way you're going.

[sockofgold]

Stop feeding the troll, guys. The OP confirmed that his/her issue has been resolved, and this other guy is just trolling you. Let this die with dignity.