linuxaudio.org

--f46d04016cad55c2c304bf50d755

Content-Type: text/plain; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
I've been doing this for 10 years.  I've successfully run the M-audio delta

1010LT, the delta 1010, the Echo Audiofire12, and now the Raydat.  The only

card which has ever exhibited this behavior is the Raydat, so there is a

high likelihood it is the Raydat's issue.  The drivers which were written

for this card are brand-new as of alsa 1.0.25, if I remember correctly.

 Perhaps I should notify the author (Adrian Knoth) of the driver...
As for now, I'm making due with Jack2, recording the "export" on to a

stereo track, and then exporting the track itself.  Seems to work, albeit a

bit more slowly...
Thanks again for the attention..  Hopefully we figure this out, because the

Raydat is an amazing card, and works very well with Linux OOTB.
--Jason
On Sat, May 5, 2012 at 2:59 PM, St=C3=A9phane Letz  wrote:
> Could it be that the RME Raydat interface does not "restart" correctly

quoted text
> when the freewheel (export) mode is finished?

>

> Can you possibly test with another audio card? Or even with the "dummy"

> driver?

>

> St=C3=A9phane

>

>

> Le 5 mai 2012 =C3=A0 22:08, Jason Jones a =C3=A9crit :

>

> > Can you possibly get a larger error log?

> >

> > Actually, there is no error to be found anywhere, but in the jack

> messages, and those are the only ones.  Neither jack nor mixbus stop

> working when this error manifests itself.  It just sits with the export

> dialog window open forever.

> >

> > It seems like mixbus is simply waiting for some sort of response from

> jack.

> >

> > Perhaps there's a way to get more verbose logs?

> >

> > Thanks for your response, and patience, Stephane.

> >

> > --Jason

>

>

--f46d04016cad55c2c304bf50d755

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
I've been doing this for 10 years. =C2=A0I've successfully run the =

M-audio delta 1010LT, the delta 1010, the Echo Audiofire12, and now the Ray=

dat. =C2=A0The only card which has ever exhibited this behavior is the Rayd=

at, so there is a high likelihood it is the Raydat's issue. =C2=A0The d=

rivers which were written for this card are brand-new as of alsa 1.0.25, if=

 I remember correctly. =C2=A0Perhaps I should notify the author (Adrian Kno=

th) of the driver... =C2=A0

As for now, I'm making due with Jack2, recording the &qu=

ot;export" on to a stereo track, and then exporting the track itself. =

=C2=A0Seems to work, albeit a bit more slowly...T=

hanks again for the attention.. =C2=A0Hopefully we figure this out, because=

 the Raydat is an amazing card, and works very well with Linux OOTB.

--JasonOn Sat, May 5=

, 2012 at 2:59 PM, St=C3=A9phane Letz <letz@grame.fr> wrote:=
Could it be that the RME Raydat interface does not "restart" corr=

ectly when the freewheel (export) mode is finished?
Can you possibly test with another audio card? Or even with the "dummy=

" driver?
St=C3=A9phane
Le 5 mai 2012 =C3=A0 22:08, Jason Jones a =C3=A9crit :
> Can you possibly get a larger error log?

quoted text
>

> Actually, there is no error to be found anywhere, but in the jack mess=

ages, and those are the only ones. =C2=A0Neither jack nor mixbus stop worki=

ng when this error manifests itself. =C2=A0It just sits with the export dia=

log window open forever.

>

quoted text
> It seems like mixbus is simply waiting for some sort of response from =

jack.

quoted text
>

> Perhaps there's a way to get more verbose logs?

>

> Thanks for your response, and patience, Stephane.

>

> --Jason

--f46d04016cad55c2c304bf50d755--