Re: [LAU] S/PDIF in with ESI Juli@ and JACK

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <len@...>
Cc: linux audio users <linux-audio-user@...>, <chris@...>
Date: Tuesday, April 23, 2013 - 10:04 am

--089e013cb9d020438804db044dbb
Content-Type: text/plain; charset=ISO-8859-1

Hello!

Thanks for the replies!

I tried some more things:

* Putting the internal clock to S/PDIF in (or, IEC958 in) and then trying
both to use the hw:Juli,1 as input, and also to connect it using zita-a2j.
Using it as input, I get crashes in both JACK and QASMixer (is there any
other mixer I should use for this purpose instead?), and it even hung so
bad (an unkillable process) that I hade to restart the computer using the
power button. Using zita-a2j, it tries to sync (instead of just spamming
syncing like it did before), but it halts instantly and says it'll retry in
15 seconds (something about a too big of a timing difference, and that this
usually happens after freewheeling in JACK1 or something like that).

I tried to do this with the internal clock set to S/PDIF, and I also tried
de-activating the "Lock rate". No success though. I did however not try the
"Lock rate"-stuff too throughly.

Anything else I should try, that I've missed?

Thanks again!

On Tue, Apr 23, 2013 at 12:42 AM, Len Ovens wrote:

>

--089e013cb9d020438804db044dbb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello!Tha=
nks for the replies!I tried some more things:* =
Putting the internal clock to S/PDIF in (or, IEC958 in) and then trying bot=
h to use the hw:Juli,1 as input, and also to connect it using zita-a2j. Usi=
ng it as input, I get crashes in both JACK and QASMixer (is there any other=
mixer I should use for this purpose instead?), and it even hung so bad (an=
unkillable process) that I hade to restart the computer using the power bu=
tton. Using zita-a2j, it tries to sync (instead of just spamming syncing li=
ke it did before), but it halts instantly and says it'll retry in 15 se=
conds (something about a too big of a timing difference, and that this usua=
lly happens after freewheeling in JACK1 or something like that).
I tried to do this with the internal clock set to S/PDIF, and I a=
lso tried de-activating the "Lock rate". No success though. I did=
however not try the "Lock rate"-stuff too throughly.
Anything else I should try, that I've missed?Thanks=
again!On Tue, Apr 23, 2013 at 12:42 AM, Len Ovens <len@ovenwerks.n=
et
> wrote:

On Mon, April 22, 2013 10:26 am, Chris Caudle wrote:

.nord@gmail.com>

Most envy24 chipsets use the same reg as clock speed. So on that pict=
ure
there is a "Multi Track internal Clock" - "48000" if it=
is expanded the
external clock will be above 96000 (if that is the top speed).

> If you look on page 18 of the card manual showing the (Windows?) utili=
ty

That is different from the Delta series then. Good to know. Though th=
at
could be a SW limit and not HW, but I would guess in this case it is HW.
While it makes sense to lock to spdif to use it, there are cases where the<=
br>
spdif input may be locked to this card from it's spdif output for examp=
le,
where not using spdif clock, but still using the info makes sense.

--
Len Ovens
www.OvenWerks.net

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@l=
ists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-user

--089e013cb9d020438804db044dbb--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] S/PDIF in with ESI Juli@ and JACK, Len Ovens, (Mon Apr 22, 10:42 pm)
Re: [LAU] S/PDIF in with ESI Juli@ and JACK, Gabbe Nord, (Tue Apr 23, 10:04 am)