Why can't EXT handle ANY audio without crackling?

[ik_ik_ik]

And I agree with you again, there is a BIG problem somewhere in the engine, but where ?

My money's on either the dilithium crystals or the non-standard GUI implementation (having done a lot of digging around threads and priorities before).

Five kids sounds like a full time job as it is - wasn't pushing for more testing; just wondered if you'd noticed already

[stanlea]

mmmm I would say non-standard GUI implementation...

[jens]

All this messing around with hardware and tweaking systems just seems to me like digging up possible ways to lessen the symptoms by avoiding whatever it is in eXT that just isn't quite right. It's basically the only application I have audio/gui performance issues with (on more than one physical setup). Am I right in thinking that this goes for most other people - and most notably with otherwise problem free systems with perfectly reasonable specifications for audio work?

tbh I had to lie to tell you are right...

- it was always like this - but now I own P5v2 which is known to be very 'realtime' - just like eXT - and basically I have the same problems with it and the native Echo-drivers like I have had with eXT before Jorgen did the latest tweaks to the asio.dll - eXT seems to perform like a charm for me now apart from two things:

- channels and tracks use resources even if they are muted

- inserts and sends use resources even if they aren't processing anything

I bet if Jorgen would fix these two things eXT would perform like a rocket over here...

@all the Echo-soundcard owners: how does P5v2 perform for you with the native Echo-drivers? (there's a demo )

[silicon/silicium]

well after some hard tweaking (back to a june beta, start and disabling midi ins, close, reopen and set the drivers, close, overwrite with last beta...) it does finally work, without cracles, at 256 samples

[mute]

This might have already been said.. I dont dare dig through the entire post.

But, Graphic/Gui movement giving you Crackles is 99.9% caused by onboard soundcards and/or onboard (or cheap) videocards and/or slow harddrives and/or you get the picture. Specially so on laptops.

I've fixed this before on many many systems,.. but I dont nessicarily recommend the fix for everyone.

Read this article on Disabling PCI-IRQ Steering. If you have the problem with more than one application, I suggest doing it. The only downside to it is that your 'Shutdown' procedure in Windows will not turn your Computer off automatically anymore but take you to a 'Computer has Shutdown' type screen. You'll have to press the power button manually.

The positives are many, but primarily its the fact that you can now manually assign and move IRQs around and avoid Shared IRQs on devices like network/video/audio, which is your enemy.

http://support.microsoft.com/default.as ... -us;182628

[jens]

I dont dare dig through the entire post.

you should though - people might start calling you a smart-aleck wannabe...

[mute]

you should though - people might start calling you a smart-aleck wannabe...

Nah, they would only do that if I said something like...

"i didnt bother checking the rest of this thread to see if anyone else suggested this, because I already know kvr members dont typically run with this sort of intelligence"

[jens]

here's the screenshot of my IRQ-info I posted on page three of this thread:



as you can see it's not exactly an onboard-soundcard I am using and most people who have reported problems in this thread (and on various other ocassions during the last eighteen months or so) run a soundcard of the same brand. Most of the people who reported these problems are also very experienced beta-testers (including myself b.t.w.) and two of them are also kvr-moderators but thanks for your help anway...

[mute]

nice attitude. ill remember not to attempt to help anyone again, thanks for the reminder. your post count is mighty fearful as well.

i wasnt aware this was some kinda of beta-tester-talent nut slinging contest. in which case, you can bow now...

[soma]

Mute- his sig used to read, "Just pretend I'm a troll. It's easier on both of us."
Which I thought was quite funny actually.

I didn't read this whole thread by the way.

[stanlea]

Helping is fair, but in this case, most people on this thread are experts on tweaking and knows their system. So if we said that there is a problem, it is not related with some so-called "well-known xp tips and tricks", but with something not so easy to find.

[fabi]

i've recently found that i have a lot less audio dropouts when i stop hitting the power button of my speakers... maybe you guys should try that one, too.

[jens]

[loomchild]

Helping is fair, but in this case, most people on this thread are experts on tweaking and knows their system. So if we said that there is a problem, it is not related with some so-called "well-known xp tips and tricks", but with something not so easy to find.

Yet testing and tracking the issues recquires not to overlook any remotely possible cause. I also don't think that dealing with IRQ settings exactly falls into the category of the "well-known XP tips and tricks".

I may finally add that expert beta testers sometimes do their job so well that a lot of products have to be fixed a few days after their initial release.

[jens]

I also don't think that dealing with IRQ settings exactly falls into the category of the "well-known XP tips and tricks".

irrelevant - however you may call it it was already on the first pages of this thread dealt with - now it is at page fiveteen...

Also check if your soundcard is sharing IRQ with you graphics card or something...

see start -> programs -> ascessories ->system tools -> sytem information

then -> hardware resouces -> IRQs

jorgen

but of course even if it was dealt with it's not really a possible cause anyway for reasons I do not wish to repeat once again...