Problem Installing 2.0

It's possible that the download problems were fixed between your two experiements and that Firefox was not a factor.  Anyway, chief thing is that you got it in the end!

I've downloaded and installed the demo using Firefox, and that part all went well.

It has now given me something else to investigate. I installed onto a newly assembled machine with an Intel processor as opposed to the Athlon XP in the other main machine here. I threw in an old Darla20 that was to hand, as opposed to the Darla 24 in the other machine. I'm getting no audio (although the meters all waggle like mad) from the AA 2.0 set to "ASIO Echo WDM", although I get audio from AA 1.5 using the same Echo drivers in the same machine.

I suppose I need to find out if the problem is that the older Darla doesn't support ASIO. Anyone old enough to know?  

In the window marked "Main" - the waveform window - go to the rightmost tab and click on the little arrow icon there - that results in a menu including monitoring options - check them out and see if the problem is related to that.

You also see those options in the "Session Properties" panel, if displayed.

In the window marked "Main" - the waveform window - go to the rightmost tab and click on the little arrow icon there - that results in a menu including monitoring options - check them out and see if the problem is related to that.

No, not that! I'm still getting silence from the soundcard. Still works fine in 1.5. Still researching here!

I now have audio, but am not sure exactly what the problem was. I spent several hours disabling and enabling the on-board sound and the Darla, and setting up the various mixers and so on, went and had afternoon tea, came back and it worked.
At this stage, the only peculiarity was that when going into the hardware settings, there was a succession of messages saying that the record input was not enabled so recording was impossible.
However, I could record happily in both EV and MT.
Restarting Audition, closing and re-opening the Echo mixer applet made no difference. The message only disappeared when I re-booted the machine.

The final comment about this is that I notice that if I'm recording or playing back and bring up the Echo applet, AA 2.0 stops what it is doing.  The same operation in AA 1.5 doesn't disrupt recording or playback.

The final comment about this is that I notice that if I'm recording or playing back and bring up the Echo applet, AA 2.0 stops what it is doing. The same operation in AA 1.5 doesn't disrupt recording or playback.

I'm at work now, so I don't know for sure,

but I believe there is an option somewhere in the settings (perhaps Audio Hardware Settings) that tells Audition to release the audio driver when the program is "not on top".

I suppose I need to find out if the problem is that the older Darla doesn't support ASIO. Anyone old enough to know?  

http://www.echoaudio.com/downloadfiles/Drivers/PC/echogals/Echogals_readme_608.pdf

Page 17 says that the Darla20 supports ASIO.

It is interesting that your cards driver says "ASIO Echo WDM".  My Layla 3G's driver says "ASIO Echo PCI".  I was under the assumption that ASIO and WDM are separate driver sets.  Maybe your ASIO drivers are just wrapping the WDM drivers, like ASIO4ALL does.  Perhaps someone else can comment on this?


Also, if you have your tracks outputting to the "Master", check your master track and make sure it is on the correct corresponding output of your card.

The final comment about this is that I notice that if I'm recording or playing back and bring up the Echo applet, AA 2.0 stops what it is doing. The same operation in AA 1.5 doesn't disrupt recording or playback.

AA 1.5 would not have been using the ASIO driver for the device, so two applications sharing the WDM/MME driver wouldn't have been an issue.  I suspect that when you bring up the Echo applet, it takes control of the ASIO connection to the hardware, shutting Audition out.  Any idea if the same behavior occurs with other ASIO applications?

As for the initial message that started the thread, the trial download was corrupted until saturday or sunday.  The file was about 400 megs shy of being complete, and I think the link was accidentally made active early.  Looks like everything has been resolved now, and most if not all of the Production Studio apps should be available to try out.

One last thing to note, though it may not explain the lack of output with the Echo device, but if you change the output device while in a session, be sure to check the Master track output channel.  In most cases this defaults correctly, but sometimes with non-standard output configurations, it doesn't.

I believe there is an option somewhere in the settings (perhaps Audio Hardware Settings) that tells Audition to release the audio driver when the program is "not on top".

Yes, this was the final answer. Untick this, and I can now access the Echo applet without stopping playback.

It's not, of course, that the applet is accessing the ASIO driver. If the "Release ASIO Driver in Background" box is ticked, bringing up any other Window, clicking on a tray icon or doing almost anything stops recording or playback. This would, of course, be disastrous for anyone like myself who works with text apps to make notes during a recording.

Not sure why it says "ASIO Echo WDM", but the same driver name appears with the Darla 20 and the Darla 24 in the other machine.

Thanks all. Amazing how obvious it is once you know.

If the "Release ASIO Driver in Background" box is ticked, bringing up any other Window, clicking on a tray icon or doing almost anything stops recording or playback. This would, of course, be disastrous for anyone like myself who works with text apps to make notes during a recording.

That is a very good point - one that hadn't struck me before!!

Elsewhere the point was made that ASIO being a direct link from program to soundcard can't be shared.  But I've found that the Asio4All driver does enable a program to access the Echo Mia's virtual outputs selectively.