Re: Best practices when using jackd over a LAN.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On November 1, 2017 6:58:35 AM HST, David Woodfall <dave@xxxxxxxxxxxxxx> wrote:
> >On Wed, 1 Nov 2017 10:52:35 +0000
> >David Woodfall <dave@xxxxxxxxxxxxxx> wrote:
> >
> >>>David Woodfall <dave-xPu8jYzPS81dsTMtEp03Dg@xxxxxxxxxxxxxxxx>
> writes:
> >>>
> >>>> NIC on server:
> >>>>
> >>>> Ethernet controller: Broadcom Corporation NetXtreme BCM5751
> Gigabit
> >>>> Ethernet PCI Express (rev 21)
> >>>>
> >>>> Jackd command on laptop:
> >>>>
> >>>> set_rlimits /usr/bin/jackd -dnetone -n60 -I0 -O0 -r44100
> >>>>
> >>>> Jackd command on server:
> >>>>
> >>>> set_rlimits /usr/bin/jackd -P 10 -p128 -t10000 -dalsa -dhw:DGX,1
> -r48000 -p128 -n3
> >>>> -P -I32
> >>>> jack_netsource -H raven -r50000 -n1 -i2 -o2 -I0 -O0
> >>>
> >>>Running everything at different sample rates is giving your CPU(s)
> a
> >>>real workout, particularly at low latencies like that.
> >>
> >>I'm using 44100 for both. I don't know how 48000 got in there.
> >Is there a particular reason you're using mplayer? It's rather a
> sledgehammer
> >to crack a nut if you're just playing audio. If it *is* just playing
> audio,
> >Audacious is quite a lightweight jack-aware player (also can work
> from CDs,
> >playlists etc.)
> 
> I didn'nt realise it was jack-aware. I'll give it a shot. Thanks.

FWIW, Audacious doesn't recognize WEBM files. Mplayer does.

--
David W. Jones
gnome@xxxxxxxxxxxxx
authenticity, honesty, community
http://dancingtreefrog.com

Sent from my Android device with K-9 Mail.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux