Why can't EXT handle ANY audio without crackling?

[jens]

This is a biggie jorgen! w00t!

yup - for sure it is!

[ModuLR]

now it doesn't crash when switching latencies...

[Sturgeon]

Works fine with testasio2, crashed when changing latency.

s.

[stanlea]

Downloaded. I'll try it tomorrow with my RME Digi 96/8 Pad, native drivers. For now, I'm gonna sleep, it's late enough for me. Anyway, I think I'll buy Sonar Homestudio 4, for some conveniences (music editing, maybe rewire)), as a secondary sequencer.

[ik_ik_ik]

ok, some minor tweaks, please try this http://www.xt-hq.com/download/testasio2.zip

Sturgeon, could you try it also?

jorgen

Seems to work better over here with my Indigo's native ASIO drivers. In fact very little glitching even down to a previously impossible to reach buffer size of 64 samples 256 samples seems pretty solid having used it for a while - definitely better than with the normal asio.dll !

Things that shouldn't work seem to work quite well

[Sturgeon]

Rebooted and did not crash when changing buffer size.

Stable, no crackles.

s.

[plastique]

works good here as well .
measured cpu against the older driver and it's the same so i'd say the improvement wasn't at the cost of other (at least my own) cards
a tiny crash (of eXT) after buffer size changed in the card's asio setup , but i guess it was due to that the loaded project was already sitting at around 90% cpu useage .

[aldi]

checked it with my pentium m 755 laptop wit external ua-1000 10 channel usb2 audiocard and ati x700. no changes, seems to work like the others before. i still have to use gdi mode and had to run ext with realtime priority to have glichefree work on 1600x1200 display. for example : pushing solo or mutebuttons will stop the whole interface for a second (and that before releasing the button, till that moment the track isn't even switched to solo or muted) without realtime priority this would lead to a crackle on my system, and it still does. so maybe some more improvements to the asio driver ?

[aldi]

it seem that i can confirm what anotherone here sayed, that the more the gui has to do and the higher the memoryuse is, the more crackles can appear.

[aldi]

hi jorgen. can it be, that the routine that checks for where the mouse is pushed can be optimized ? seems like everyting stops in that moment the mouse is pushed down. and does ext redraws the whole screen, when moving around stuff (clips, audioparts, smples, plugins) or drawing the selection rectangle ? seems like sonar or logic just redraws whats needed (the more is moved the higher the cpu usage)

[adds2one]

Wow! I had backed off from eXT for a while because of poor performance on my system and just checked back today! With asiotest2 I am running my Indigo IO at 64 samples and things seem smoooooth. Even my cpu usage on my projects seems to have gone down! I don't know what you did but I am a happy eXT geek today!

[Sicklecell666]

The test driver doesn't improve anything here on my work machine using asio4all. I still get crackles when I open a GUI and when I drag an icon in the main window, etc..

Seems to be mouse down as previously noted.

[ModuLR]

The difference for the echo folks is pretty damn massive! It's ultra stable and click free... and the UI is much faster even when the cpu is just getting killed. Very very very very impressed with the results jorgen! This is a been a very long standing issue with me and eXT! w00t to you again (cos you deserve it for nailing this one!). I gotta ask again cos I'm a code dork... what was the underlying problem?

[soma]

you guys are making me want a Indigo. STOP IT ALREADY!
Jeez, I'm starting to get as groucy as Jens.

[plastique]

a tiny crash (of eXT) after buffer size changed in the card's asio setup , but i guess it was due to that the loaded project was already sitting at around 90% cpu useage .

BTW that's the error which occurs when switching buffer here now and then with the testdriver , maybe useful ...

"Error"
Runtime error 216 at 0BCF3722