Adobe Audition 3.0 + StudioLive Asio = Weird behavior!

First thing i've done when i installed Studiolive (3.4.1 driver with its firmware) on my i7 system is importing a heavy project i have to A Audition 3.0 , filled with allot of reverbs and other plugins , this was the big test for my new i7 DAW with my new SL ,

i pressed Play , and wow! every thing was smooth with all plugins activated ,no clicks or pops , CPU usage was from 5 to 8% only! I WAS SO HAPPY

next day i played the same project on the same setup , and man i couldnt hear a word , sound was cutting as if i was playing the project on my old P4 PC!

i started missing with thing and nothing changed, i re-installed the drivers and played the project again , and it was smooth again?

when i restarted Audition , the problem came back? i couldn't figerout the cause of this? if it played will in the first place why it would the Asio driver fail so fast?

i tried recording one track , and it stopped recording before the first 30s?

closed AA again and started it , nothing changed still bad, i changed asio driver to Audition Windows asio and back to presonus and things went good again? and failed when i restarted my computer?

Next thing i'v done was uninstall the 3.4 driver and install the one came with the DVD , 3.3

i imported the project to AA and pressed play , things went smooth BUT with changing on pitch as if chipmunks were singing ,

after switching to Editview i played a take, there were some firewire clicks then things went normal again in both views ,

so in the 3.3 driver , project will play smooth (always ) but with pitch changing untill i switch to edit view and play some clips there then pitch will return normal after i hear some clicks and the GR red meter in SL flashes.

Recording was mutch beter with the 3.3 driver , i tested it for 20 minits with no stop.

Second test was on Samplitude , and shortly: every thins was working great on ASIO , playback and recording , it was stable and rock solid.

BUT i cant live without Audition which never went stable , so any ideas ?

more info :

Intel Core i7-920 Bloomfield 2.66GHz
MB: GIGABYTE GA-EX58-UD3R
Memory: OCZ Reaper 3GB 3X1GB DDR3-1866 Triple Channel
VGA : Sapphire ATI Radeon™ HD 4550 – 512MB of DDR3 "Fanless"
FireWire : PCIe with Ti chip.
Runing on WinXP pro 32bit , SP3

it seems that Audition looses the connection with my SL Asio driver , what happens is when i open a new session and press Play or Record , the courser will move for one second then it will stop , it well not record/play any thing, or sometime it does but it will stop immediately!

i found one way to fix the problem with SL Asio , i start playing with the Inputs/outputs for the track and the master track , changing them and assigning different in's/out's then suddenly the Asio Driver will preform normally , and it will be stabled , very stabled until i exit Audition, then when i run it again Asio driver will give me truble again.

i was using 3.0 , and just updated to 3.01 now

did not solve the problem .

full story here  http://forums.presonus.com/showthread.php?t=11836

it seems that Audition looses the connection with my SL Asio driver , what happens is when i open a new session and press Play or Record , the courser will move for one second then it will stop , it well not record/play any thing, or sometime it does but it will stop immediately!

Unfortunately you can't rule out one other possibility - the Firewire card. Generally TI chipsets are about as good as you can get, and most manufacturers recommend them - but they are not entirely trouble-free. The reason that I suspect the Firewire interface rather than the driver is that if contact with the driver was lost, the transport wouldn't start in the first place. The fact that it does, and then stops points rather more firmly at the next stage in the interfacing, I'm afraid.

i was using 3.0 , and just updated to 3.01 now

did not solve the problem .

It wouldn't - it's clearly not any sort of an Audition problem at all.

Unfortunately you can't rule out one other possibility - the Firewire card. Generally TI chipsets are about as good as you can get, and most manufacturers recommend them - but they are not entirely trouble-free. The reason that I suspect the Firewire interface rather than the driver is that if contact with the driver was lost, the transport wouldn't start in the first place. The fact that it does, and then stops points rather more firmly at the next stage in the interfacing, I'm afraid.

Steve

my Gigabyte mobo has a built in firewire chip , i connected the SL trough it but it did not help , but again its a Ti chip too.

if the fw chip is the problem how come SL was normal and stable with Samplitude and Capture?

Thanks

my Gigabyte mobo has a built in firewire chip , i connected the SL trough it but it did not help , but again its a Ti chip too.

if the fw chip is the problem how come SL was normal and stable with Samplitude and Capture?

It's not exactly unknown for one product to work fine and another not to - with the same hardware. Audition has been known to be an absolute stickler for handling any protocol exactly as it's defined - as the creators of quite a few VSTs have found to their costs. Chances are that if you get onto the the manufacturer of your hardware and tell them that their ASIO driver works fine with some software and not with others, that they will contact Adobe and try to establish exactly what isn't happening. Nobody is immune - even Waves had to rewrite some of their plugins to comply exactly with the appropriate specs so that they would work with Audition, and I know from personal experience that Echo have also had to have several goes at ASIO drivers to get them to work with everything.

Thing is, Audition works fine with the vast majority of ASIO hardware, so it's very unlikely that there's a fundamental fault with it, quite frankly.

One interesting thing you could try is to use the WDM driver for your soundcard with Audition, and the best (and free) way to do this is with ASIO4ALL. If this works fine, you should definitely have a go at the manufacturer.

Asio4all was horrible , Audio was playing , But in SLOW motion 

oh well , i am hanging at Presonus forums and see how can they help.

Thanks Steve