What firewire chipset do you have in your computer? Most audio interfaces aren't compatible with VIA firewire chipsets. Texas Instruments chipsets are the best.

quote:

Originally posted by Eldritch What firewire chipset do you have in your computer? Most audio interfaces aren't compatible with VIA firewire chipsets. Texas Instruments chipsets are the best.

I'm not sure...

A quick search for my laptop model reports the following for firewire: 1 x IEEE 1394 (FireWire) - 4 pin FireWire

Is there a place, e.g. in Device Manager, where I can check?

quote:

Originally posted by cenik I'm not sure... A quick search for my laptop model reports the following for firewire: 1 x IEEE 1394 (FireWire) - 4 pin FireWire Is there a place, e.g. in Device Manager, where I can check?

Yes, look in the device manager.

quote:

Originally posted by Eldritch Yes, look in the device manager.

So, now that we've established that I have the preferable chipset, how are my settings looking (as per my first post) and is there anything else I should take note of/check? Thanks El...

Yes, the settings look fine. I wonder what is causing the clicks.

btw the output is +4dB. thats meant for balanced instruments next in the chain. what is next in the chain? a volum-control? direclty to monitors? if its a normal stereo-amp theyr usualy not balansed and u can overload the inputs. other option -10dB could be low tho so if u just lower the volum-fader -4dB ull be on 0dB if u keep the option on +4. i think this is abit stupid on echos but it might be industri standard i have no idea. about the clicks u could try making the latency longer.

I have some clicks too with Ableton 7.02 on Vista

___________________
Stooped Cat

quote:

Life is to short to listen to something else than Trance

By the way, you have some devices that are not installed propery (the big yellow question marks in device manager). Fix these as one of them is related to audio. This could be causing a conflict. If this unknown device is also on board sound, then disable it as it could just cause more problems.

Try setting the buffers (both in ableton and the console) to the highest setting and restart the applications. Let us know if that makes a difference.

what version is the driver you are running? it looks like an older one to me...

- disconnect your audiofire
- reboot
- uninstall the audiofire driver you have at the moment
- reboot
- download and install this:
http://www.echoaudio.com/downloadfi...dioFire_4.8.exe
- reboot
- plugin your audiofire
- reboot

once it's all up and running, go back into the audiofire panel and set it to stereo, not surround. then lock the rate to 44100. you'll need to turn off your audiofire and turn it back on again afterwards. reboot your pc too, just to be sure.

quote:

Originally posted by echosystm what version is the driver you are running? it looks like an older one to me... - disconnect your audiofire - reboot - uninstall the audiofire driver you have at the moment - reboot - download and install this: http://www.echoaudio.com/downloadfi...dioFire_4.8.exe - reboot - plugin your audiofire - reboot once it's all up and running, go back into the audiofire panel and set it to stereo, not surround. then lock the rate to 44100. you'll need to turn off your audiofire and turn it back on again afterwards. reboot your pc too, just to be sure.

Thanks for the advice bud. I am running version 4.8: I installed the newest drivers available from the echo website and didn't bother with the CD. I'll make the other changes you suggested. Thanks

One thing that was magic for me was disabling the 'on board' sound or whatever else you've been using. For my situation, I was using the motherboard sound. I unistalled those drivers and turned off the onboard sound hardware in the BIOS at startup. Made a huge difference for me. Hope it works for you.