Re: Does alsa_in reading from SPDIF input inject pops and clicks?
crocket <[email protected]> Fri, 9 Aug 2019 08:56:23 +0900
| Newsgroups | gmane.comp.audio.jackit |
|---|---|
| Message-ID | <CAL0=0H3Tv8a+F3gE697tEFBjRht4mJXrHdhQU5x2NX7sLefoJw@mail.gmail.com> |
--===============1999355203965851302== Content-Type: multipart/alternative; boundary="000000000000b627d7058fa3ced5" --000000000000b627d7058fa3ced5 Content-Type: text/plain; charset="UTF-8" If I set the clock source of a USB soundcard to SPDIF, would the headphone jack of the USB soundcard conform to the SPDIF clock, too? Or, does the SPDIF clock source apply only to SPDIF In? On Fri, Aug 9, 2019 at 7:21 AM Chris Caudle <[email protected]> wrote: > On Thu, August 8, 2019 5:10 pm, crocket wrote: > > Does changing clock source to internal clock or SPDIF make any difference > > on pops and clicks? > > Your clock setting has to be consistent with the audio data flow. If you > are sourcing audio data from S/PDIF input and set the clock source to > internal you will definitely get pops and clicks. Internal clock should > only be used when audio input is through the converters on the interface, > or if you are only using S/PDIF for output. The clock source should only > be set to S/PDIF if you have a valid S/PDIF data stream present, and you > should also verify that the sample rate you set for the interface matches > the actual rate of the S/PDIF data. > > -- > Chris Caudle > > > > > _______________________________________________ > Jack-Devel mailing list > [email protected] > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org > --000000000000b627d7058fa3ced5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">If I set the clock source of a USB soundcard to SPDIF, wou= ld the headphone jack of the USB soundcard conform to the SPDIF clock, too?= <div>Or, does the SPDIF clock source apply only to SPDIF In?</div></div><br= ><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, A= ug 9, 2019 at 7:21 AM Chris Caudle <<a href=3D"mailto:chris@chriscaudle.= org">[email protected]</a>> wrote:<br></div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex">On Thu, August 8, 2019 5:10 pm, crocket wrote:<br= > > Does changing clock source to internal clock or SPDIF make any differe= nce<br> > on pops and clicks?<br> <br> Your clock setting has to be consistent with the audio data flow.=C2=A0 If = you<br> are sourcing audio data from S/PDIF input and set the clock source to<br> internal you will definitely get pops and clicks.=C2=A0 Internal clock shou= ld<br> only be used when audio input is through the converters on the interface,<b= r> or if you are only using S/PDIF for output.=C2=A0 The clock source should o= nly<br> be set to S/PDIF if you have a valid S/PDIF data stream present, and you<br= > should also verify that the sample rate you set for the interface matches<b= r> the actual rate of the S/PDIF data.<br> <br> -- <br> Chris Caudle<br> <br> <br> <br> <br> _______________________________________________<br> Jack-Devel mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">Jack-De= [email protected]</a><br> <a href=3D"http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org= " rel=3D"noreferrer" target=3D"_blank">http://lists.jackaudio.org/listinfo.= cgi/jack-devel-jackaudio.org</a><br> </blockquote></div> --000000000000b627d7058fa3ced5-- --===============1999355203965851302== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Jack-Devel mailing list [email protected] http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org --===============1999355203965851302==--