When I use the ASIO drivers for the layla, and I import a track, the default output seems to go right to the ASIO - 1 output, even though I have ASIO - 5 selected as the ONLY output track. To fix this, all I have to do is go into track properties, hit OK, and then it’s routed to the proper track (which is selected). So basically, although everything in the program says it’s sending to ASIO - 5, it’s actually sending to ASIO - 1, until I go into track properties and hit OK. I ma thinking this is a bug, but because of my relative lack of experience with ASIO, I’d like some feedback.
Do you have the latest drivers for the Layla card? I am running Gina with the latest drivers and am having multiple problems when using the ASIO. I’m back to using MME for now. May be a conflict between Echo and n-Track.
| Quote (YazMiester @ Dec. 18 2004,14:49) |
| Do you have the latest drivers for the Layla card? I am running Gina with the latest drivers and am having multiple problems when using the ASIO. I'm back to using MME for now. May be a conflict between Echo and n-Track. |
You mean MME with PureWave? I am on Echo's most recent Layla20 drivers (6.11)... but they won't release anything but BETA drivers for layla20 anymore... argh!
I know, I’m stuck with the Gina20, have been looking at new sound cards lately, Echo will not be providing any new drivers other than what is posted at their site now.
I had a layla 24/96 and had no such trouble with asio. I found that the only problem I had repeatedly was that my recordings would stop on there own. and the more tracks I had the sooner it would stop. usually about the 7 minute mark, which didn’t affect recording bands usually. but I haven’t tried it with the newer n versions.
I’ve been having similar problems with my layla 20 (the stopping) - it seems to be that it has something to do with buffering… my best guess is that n-track stops because of a buffering issue - but does not report it. I’ve noticed that if I crank my buffers way down, while using the ASIO drivers, it stops almost immediately, but n-track says nothing… but using the MME PW drivers, I get the standard n-track buffering issue message - all I can figure is that (at least with n-track) the layla ASIO drivers are not very low latency - I have my latency right now set at about 25ms - which seems kind of high, but will get me at least 7 or 8 minutes of recording time. Honestly, though - after screwing with settings on this thing for about a month straight - I am about ready to chuck it… I’ve been looking at the presonus firepod - it seems like it would replace the layla nicely, and probably the mixer I am using as a glorified bank of mic preamps. I just am at a loss as to why echo’s ASIO drivers are so glitchy.
yeah, I was hoping they’d make new drivers, which they did, but only for their 3g new stuff. the older layla’s are screwed. I had my buffers set pretty low. I’d test it out with live input processing with low enough latency that I could barely tell and I’d get 7-8 minutes with 16 tracks. about 15 minutes with 8 tracks. Flavio couldn’t figure out why either.
I’d like to get a card with 8 mic pres built in but that also has adat in for my ada8000 right now, but I’m not sure if there are any on the market.
ideally I’d get a frontier design Dakota, and run two ada8000’s, but I haven’t seen one on ebay for quite a while. I bought a vsl2020 and while I’m sure it works great with vsti’s and such, it’s not running very well on my computer.