> >Yep, OK. I'll look if I can make the latest beta work with my Delta1010.
Didn't get far on this. RPM build of alsa-driver beta 7 failed. It just
messed up my existing and installed 0.5.
Btw. I think the kernel version variable in .spec should be defined as
%(uname -r) and not as some static v
>> its not that simple. you have to make sure that the driver software
>> state is up-to-date when the h/w starts. you can't just issue out()'s
>> and then pick up the pieces later. you have to make sure that the
>> driver infrastructure is ready to start processing interrupts, etc.
>
>Isn't this
Paul Davis wrote:
>
> it *IS* done in the drivers. what makes you think i was talking about
> user-space?
OK, I misunderstood something.
> but the device drivers do not block interrupts while sync-starting
> multiple devices. perhaps they should. its rather ugly.
It depends how long it takes.
>> but its still possible that if an interrupt occured at the wrong time,
>> the delay between issuing the two start instructions could be
>> sufficient to mess them up. its hard to work around this, though there
>
>Trying to do this in user space is mad. It should be done in drivers.
it *IS* don
Paul Davis wrote:
>
> but its still possible that if an interrupt occured at the wrong time,
> the delay between issuing the two start instructions could be
> sufficient to mess them up. its hard to work around this, though there
Trying to do this in user space is mad. It should be done in drive
>I need to record at least 16 channels with no phase error between channels.
>
>Is it possible with alsa to start (trigger) two cards or two ADAT ports on
>same card such way, that first samples from both devices are exactly from
>the same moment? Devices are of course word clock connected. Time/p
