I use UA-100, had no joy for a long time in getting it to work with PD, eventually abandoned ASIO as a no-goer and now get a latency around 80ms, with occaisional dropouts. Don't have another SC to compare if this is driver specific.
-----Original Message----- From: David Sabine [mailto:dave@davesabine.com] Sent: 10 November 2002 03:43 To: nick@music.gla.ac.uk; pd-list@iem.kug.ac.at Subject: [PD] problems with Pd and edirol usb
Hello Nick,
I bought an Edirol UA-5 a few months ago and eventually returned it to the retailer (i took of that 30-day money back gaurantee because ultimately it wasn't the right product for my needs). Here's a breakdown of my experience with the interface:
clicking noises.
interface. the UA-5 could only support ASIO drivers on either the input OR the output. So, If I stared PD with the -asio flag, then I had to also use either -nodac or -noadc. That was a real drag. (I don't know if the UA-1A supports simoultaneous INput and OUTput with the ASIO drivers.??)
about 2.5 times the price of the edirol unit..but I can use 24 input and output simoultaneously with ASIO --but on the downside, it doesn't have a mic pre-amp like the UA-5 had.
I don't know if this helps you at all and I understand that you're using the UA-1A which is different than the UA-5..but I thought I'd share my experience anyway.
Regards, Dave S
hi all,
Well, thanks for all the input on this one. I've given up on edirol too, couldn't get it to work without clicking on my dell inspiron under WinXp (asio or otherwise) nor Alsa. Nice sound quality for 60GBP, if you can ignore the clicks. Interesting phenomenon to note: under XP with asio driver, running the test tone patch, I'd get occasional small clicks under the windows (native) and ALSA drivers. Same running my granular sampling patches. Under win with asio driver, the test tone patch makes less frequent but much louder clicks, and the granular patches sound like you're thrusting the Dell through an industrial grinding machine (massive clicks with virtually every grain, it seems). Bizarre.
Guess you just have to spend the money on the bigger solutions (but, clearly, even then you can't guarantee the manufacturers do what they claim to do - 'roland corp', 'dell', your both bloody rubbish, that's what I say, grrr).
Another thing to note - in the small print on the edirol website they mention there might be problems with their products on machines that do 'interrupt sharing', something I wasn't even aware of (and certainly not something they go out of their way to warn you about in their sales patter...). Indeed, when I look at the resources used by my dell's hardware, there are about 10 devices allocated IRQ11, including (wait for it): ATI Radeon card, Ethernet card, PCI-USB adapter, 'on-board' intel sound chip etc etc etc. (and the PCMCIA adapter, which worries me, as even if I had say the RME Cardbus card, would this not suffer the same fate??)
So I suppose the usb-audio is probably never going to work on that laptop without being preempted by something else (radeon!).
Don't understand the ins and outs of this enough, but under XP you can't reassign resources as there's no Hardware Abstraction Layer (HAL) - you can set one up, but you have to reinstall the OS (AARGH, thank you Mr Gates, what a nice man - yet again you have innovated for the benefit of the customer). Don't know about Linux - if anyone can advise on that, I'd appreciate it. At the moment it just seems to use the same resources as windows (lots of 'sharing interrupt with device ...' messages at boot up).
For what it's worth (sorry about the rant).
nick
PS the performance went well, and the sound was surprisingly <ok> using the onboard i/o - but then it might have had something to do with the Neumann mic
Try the "audio" module: it is an OSS module for usb devices like the Edirol UA-1A. On my system (mdk 8.2) the module loaded automatically when I first plugged it. It works very well on both my portable and desktop. -- Marc
Le mer 13/11/2002 à 04:52, Nick Fells a écrit :
hi all,
Well, thanks for all the input on this one. I've given up on edirol too, couldn't get it to work without clicking on my dell inspiron under WinXp (asio or otherwise) nor Alsa. Nice sound quality for 60GBP, if you can ignore the clicks. Interesting phenomenon to note: under XP with asio driver, running the test tone patch, I'd get occasional small clicks under the windows (native) and ALSA drivers. Same running my granular sampling patches. Under win with asio driver, the test tone patch makes less frequent but much louder clicks, and the granular patches sound like you're thrusting the Dell through an industrial grinding machine (massive clicks with virtually every grain, it seems). Bizarre.
Guess you just have to spend the money on the bigger solutions (but, clearly, even then you can't guarantee the manufacturers do what they claim to do - 'roland corp', 'dell', your both bloody rubbish, that's what I say, grrr).
Another thing to note - in the small print on the edirol website they mention there might be problems with their products on machines that do 'interrupt sharing', something I wasn't even aware of (and certainly not something they go out of their way to warn you about in their sales patter...). Indeed, when I look at the resources used by my dell's hardware, there are about 10 devices allocated IRQ11, including (wait for it): ATI Radeon card, Ethernet card, PCI-USB adapter, 'on-board' intel sound chip etc etc etc. (and the PCMCIA adapter, which worries me, as even if I had say the RME Cardbus card, would this not suffer the same fate??)
So I suppose the usb-audio is probably never going to work on that laptop without being preempted by something else (radeon!).
Don't understand the ins and outs of this enough, but under XP you can't reassign resources as there's no Hardware Abstraction Layer (HAL) - you can set one up, but you have to reinstall the OS (AARGH, thank you Mr Gates, what a nice man - yet again you have innovated for the benefit of the customer). Don't know about Linux - if anyone can advise on that, I'd appreciate it. At the moment it just seems to use the same resources as windows (lots of 'sharing interrupt with device ...' messages at boot up).
For what it's worth (sorry about the rant).
nick
PS the performance went well, and the sound was surprisingly <ok> using the onboard i/o - but then it might have had something to do with the Neumann mic
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list