9 Oct
2019
9 Oct
'19
10:49 p.m.
Hi,
I've been playing around with an X32 recently, and it starts glitching really fast.
Like, if i start JACK on my internal sound card (2ch) and SuperCollider with 8 to 24
channels, routing all channels to the 2 outputs, everything's fine.
But if I use JACK on the X32 with 8 channels and SuperCollider with 8 channels, it starts
glitching as soon as the load increases just a little,
using the same programs in the background (ScSynth, SBCL (Common Lisp) using Incudine for
OSC scheduling).
I've found some settings that work ok-ish, but I still have to be careful not to play
too many things at the same time. Using the internal sound card,
there's much more leeway.
I'm working on Arch Linux, using the latest RT kernel with all exploit-fixing options
disabled (https://make-linux-fast-again.com/). No, I'm not using these
options for my day-to-day work :D .
Has anybody encountered this before ? And maybe knows some way to mitigate this ?
Best,
Niklas
10 Oct
10 Oct
12:39 a.m.
On Wed, Oct 9, 2019 at 12:49 PM <nik(a)parkellipsen.de> wrote:
Hi,
I've been playing around with an X32 recently, and it starts glitching
really fast.
Like, if i start JACK on my internal sound card (2ch) and SuperCollider
with 8 to 24 channels, routing all channels to the 2 outputs, everything's
fine.
But if I use JACK on the X32 with 8 channels and SuperCollider with 8
channels, it starts glitching as soon as the load increases just a little,
using the same programs in the background (ScSynth, SBCL (Common Lisp)
using Incudine for OSC scheduling).
What period size and sample rate?
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:21 a.m.
The samplerate was 44100, period size 1024. Going up to 2048 made it
worse.
Started with:
jackd -P98 -dalsa -dhw:2 -p1024 -n8 -r44100
scsynth -u 57110 -z 256 -i 0 -o 8 -m 262144
Paul Davis wrote on 09.10.2019 22:38 (GMT +02:00):
On Wed, Oct 9, 2019 at 12:49 PM <nik(a)parkellipsen.de
<mailto:nik@parkellipsen.de> > wrote:
Hi,
I've been playing around with an X32 recently, and it starts glitching
really fast.
Like, if i start JACK on my internal sound card (2ch) and SuperCollider
with 8 to 24 channels, routing all channels to the 2 outputs,
everything's fine.
But if I use JACK on the X32 with 8 channels and SuperCollider with 8
channels, it starts glitching as soon as the load increases just a
little,
using the same programs in the background (ScSynth, SBCL (Common Lisp)
using Incudine for OSC scheduling).
What period size and sample rate?
Linux-audio-user(a)lists.linuxaudio.org
<mailto:Linux-audio-user@lists.linuxaudio.org>
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:24 a.m.
On Wed, Oct 9, 2019 at 3:21 PM <nik(a)parkellipsen.de> wrote:
The samplerate was 44100, period size 1024. Going up
to 2048 made it
worse.
Started with:
jackd -P98 -dalsa -dhw:2 -p1024 -n8 -r44100
scsynth -u 57110 -z 256 -i 0 -o 8 -m 262144
try running at 48kHz with 3 periods and see if that helps.
1:53 a.m.
On 10/9/19 11:24 PM, Paul Davis wrote:
On Wed, Oct 9, 2019 at 3:21 PM <nik(a)parkellipsen.de
<mailto:nik@parkellipsen.de>> wrote:
The samplerate was 44100, period size 1024. Going up to 2048 made it
worse.
Started with:
jackd -P98 -dalsa -dhw:2 -p1024 -n8 -r44100
scsynth -u 57110 -z 256 -i 0 -o 8 -m 262144
try running at 48kHz with 3 periods and see if that helps.
My X32 Rack runs
flawlessly on arch using 48kHz, 1024 and 2 periods.
Though I had to sort out USB issues first by running lsusb -t and find
the least crowded bus.
Cheers
Bollie
11:17 a.m.
Thanks for the hints,
I'll try some different samplerate settings the next time I have access to the
device.
Thomas Ebeling wrote on 09.10.2019 23:53 (GMT +02:00):
On 10/9/19 11:24 PM, Paul Davis wrote:
On Wed, Oct 9, 2019 at 3:21 PM <nik(a)parkellipsen.de
<mailto:nik@parkellipsen.de> > wrote:
My X32 Rack runs flawlessly on arch using 48kHz, 1024 and 2 periods.
Though I had to sort out USB issues first by running lsusb -t and find the
least crowded bus.
Cheers
Bollie
The samplerate was 44100, period size 1024. Going
up to 2048 made it
worse.
Started with:
jackd -P98 -dalsa -dhw:2 -p1024 -n8 -r44100
scsynth -u 57110 -z 256 -i 0 -o 8 -m 262144
try running at 48kHz with 3 periods and see if that helps.
13 Oct
13 Oct
8:19 p.m.
Hmm, this is interesting, i just checked the USB ports in my Thinkpad T440s with lsusb
-t.
Turns out, it has 3 buses, one USB3.0 (i suppose) and two 2.0 buses.
There's nothing on the 3.0 bus, but if i connect my interface, it still won't
connect
to that bus because it's a 2.0 interface (testing with my UMC1820 at home, but I
assume the X32 will be the same).
Now, one hub seems to be there for the (rather useless) smart card reader exclusively,
while
ALL external (physical) ports are wired to the one bus that also has the memory card
reader and other things
attached.
That means, not matter where i connect the interface, there's no way to connect to the
least busy bus.
I wonder if there's a way to expose the unused buses ? Like, disconnect the smart card
reader and attach
an USB hub? Or, if i connect an external USB 3.0 hub, will it wire external devices to the
3.0 internal bus?
Anybody got experience here ?
Best,
Niklas
Thomas Ebeling wrote on 09.10.2019 23:53 (GMT +02:00):
On 10/9/19 11:24 PM, Paul Davis wrote:
On Wed, Oct 9, 2019 at 3:21 PM <nik(a)parkellipsen.de
<mailto:nik@parkellipsen.de> > wrote:
My X32 Rack runs flawlessly on arch using 48kHz, 1024 and 2 periods.
Though I had to sort out USB issues first by running lsusb -t and find the
least crowded bus.
Cheers
Bollie
The samplerate was 44100, period size 1024. Going
up to 2048 made it
worse.
Started with:
jackd -P98 -dalsa -dhw:2 -p1024 -n8 -r44100
scsynth -u 57110 -z 256 -i 0 -o 8 -m 262144
try running at 48kHz with 3 periods and see if that helps.
10:54 p.m.
On Sun, 13 Oct 2019, nik(a)parkellipsen.de wrote:
Hmm, this is interesting, i just checked the USB ports
in my Thinkpad
T440s with lsusb -t.
That means, not matter where i connect the interface,
there's no way to
connect to the least busy bus.
Which driver is servicing them? if it an xhci driver... turning that off,
either in bios (what I did) of via software may let the ohci driver work
and split them up a bit. (I at least got two doing this) This basically
makes your machine USB2 and not USB3. However, it may allow you to
separate at least some of you USB parts. On this machine with xhci running
every single plug ended up on the same USB bridge (all 10 of them!) but
turning xhci off in bios split the plugs into two bridges (front and back
in my case) and allowed me to give my USB audio a higher priorty while
leaving my mouse and printer at lower priority. (the mouse has since been
replaced with a ps/2 mouse) This may help:
https://www.systutorials.com/241533/how-to-force-a-usb-3-0-port-to-work-in-…
--
Len Ovens
www.ovenwerks.net
1869
days inactive
1873
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Len Ovens -
nik＠parkellipsen.de -
Paul Davis -
Thomas Ebeling