Hmm I have to check, I think i deactivated audit as well.
I haven't done any real profiling, but to be honest I don't think there's
a huge difference, no. From a purely intuitive assessment, it takes a little
more load to cause xruns.
Best,
Niklas
Ralf Mardorf wrote on 10.10.2019 00:02 (GMT +02:00):
> > https://make-linux-fast-again.com/
>
> Hi,
>
> for testing purpose you might want to disable audit by boot parameter
> 'audit=off', too. If you should use the kernel config of the AUR tarball
> ( https://aur.archlinux.org/packages/linux-rt/ ) , audit is
> enabled.
>
> https://lists.archlinux.org/pipermail/arch-general/2018-September/045580.ht…
> http://lists.jackaudio.org/pipermail/jack-devel-jackaudio.org/2019-July/002…
>
> Btw. does it make a noticeable difference for rt audio performance on
> your machine, if you disable those mitigations? Did you compare the
> performance with and without mitigations?
>
> Regards,
> Ralf
>
>
>
Hello folks,
If I am recording a live microphone input, while also routing that
signal to be processed in SuperCollider, which of these two signal flows
would provide the least latency between the live microphone signal and
the output from SuperCollider?
1. Route microphone into both Ardour5 and SuperCollider at the same time
(my current setup)
2. Route microphone into Ardour5, then feed that track's monitor signal
into SuperCollider
I am using Jack2 on Arch Linux, with linux-rt-lts kernel. My Jack2
settings are 48kHz, 96 bufsize, 3 periods. Despite the fact that I am
multi-track recording 18 channels (2 from mics, 16 from SuperCollider),
I get hardly any xruns on this setup.
My problem is that, under this configuration, I've noticed that the live
microphone input seems to get recorded to its Ardour5 track *after* the
SuperCollider output. This can't be correct since the SuperCollider
signal relies on the microphone input to make any sound at all, so
somewhere in the chain the microphone signal is getting delayed on its
way into Ardour5. Expected behavior would be for the mic signal to be
written to Ardour5 followed by the output from SuperCollider's
processing of that input. I can't tell if the current predicament is due
to a sub-optimal signal flow strategy or if I need to explore
software/hardware bugs.
Many thanks in advance for any help!
-Andrew
I have been using Ardour5 to multi-track record 18 channels of audio. 16
of the channels come from SuperCollider 3.10, running on the same Linux
workstation as Ardour5. The other two channels are live microphone
feeds, which correspond to audio inputs 1 and 2 on my RME Babyface Pro.
Jack2 is used to route this live mic audio as well as the SC3 audio
outputs into Ardour5. Additionally noteworthy is that these two live
microphone feeds are also plugged into SuperCollider. The 16
SuperCollider outputs are the result of realtime processing being
applied to those two microphone inputs.
As crazy as this all sounds, this setup has generally worked splendidly,
especially after building the linux-rt-lts kernel and tuning Jack2 for
low-latency operation. (I run Jack2 at )
I've had a very long 'dead' spell where I couldn't come up with anything
completely new and original, but I finally set out to compose something for
this month's KVR contest. After leaving it a few days, I listened again and
found I liked it enough to post a copy on Soundcloud :)
Hope you like it too.
https://soundcloud.com/soft-sounds/morning
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hello,
I've been having this issue with zita-a2j launching into 100% CPU usage
fairly frequently when I am running Carla, one VST (Audeze Reveal Plugin),
and using Ubuntu Studio 19.04.
Has anyone else seen this kind of behavior before and knows what might be
happening?
--
Scott
http://www.scottcazan.com
Twitter: @scazan <https://twitter.com/scazan>
Instagram: @scazan <https://www.instagram.com/scazan/>
Hello People,
I have a strange problem with high latency for both JConvolver or BruteFIR.
My Jack settings are low(3ms) and stable and the latency doesn't seem to
tally with the partition size?
My Hardware:
i5-8259U - Intel NUC
8GB DDR4
PCIe SSD
M-Audio - MTrack8 USB Sound
Software:
Ubuntu Studio 19.04 - Have tried updated and fresh install also a blank
Debian 10.1
Jconvolver 0.9.3-2
BruteFIR 1.0o-1
Jackd2 1.9.12
Settings:
Jack Settings - 48KHz 64Buffer 3Period
BruteFIR - 7 Filters each 8192 Taps, These are each split into 512sample
partitions
Jconvolver - 7 Filters each 8192 Taps, These are split into 64sample
partitions
Results:
JConvolver Latency = 85mS, CPU Load = <5%
Brutefir Latency = 104mS, CPU Load = 55-60%
These latencies are measured inside Jack(Not using sound card IO) using a
jack signal generator and a jack oscilloscope. But also verified externally.
I dont understand why I am getting such long latencies, I would be very
grateful if anyone could shed some light on why the latencies are so long
and even more grateful if you could share how to fix it!
Thank you in advance,
Alex
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
Hi all.
Tomorrow it's the scheduled meeting at c-base again. I don't know if
I'll make it (I've stayed home from work today not feeling great), but
maybe Louigi or Robin can gather people?
Cheers
/Daniel
Hello All,
i have a special little audio problem with kdenlive which is annoying me
a lot, perhaps you can reproduce it or have an solutiuon:
I like to do video cuts exactly synchronized with music song beats. So i
would like to "tap in" the beats with markers before cutting to have the
cut positions to snap to. That's not possible on my system, i always
have about 500ms of delay when i listen to the music track and tap in
the beats. So the markers are always a little to late and out of sync...
Can you reproduce this? Do you have an idea?
I am on Arch latest kernel, KDE, Ryzen System, tried it on Pulseaudion
and Firewire external Audio Interface, Same Problem.
Thanks for ideas, Daniel.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniel Wilhelm
Hello!
I am familiar with this error you described. What is the SSD's file system
formatted to? I get the same error when writing to my NTFS partition. I
can't remember where I read this but it is best to record to ext4 or
another more Linux friendly format.
Hope this helps!
Best,
n!
Hey hey,
I have had issues with Aeolus for a while now, but always let it go due to
other priorities.
Having attacked it again, I find that this problem persists both in the
installed package from Arch Linux, version 0.9.7 and a freshly downloaded and
compiled tarball from kokkinizita.
It seems that Aeolus segfaults the moment that it calls rl_initialize, gdb
giving a point in libncursesw as the last stack frame before shutdown.
I don't understand the problem since all other programs running with ncursesw
and/or readline alone work perfectly.
I'd be glad for any pointers to further investigation or even straight
solutions.
Thanks and best wishes,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* SoundCloud: https://soundcloud.com/jeanette_c
* Twitter: https://twitter.com/jeanette_c_s
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
You should take me as I am
'Cause I can promise you
Baby, what you see is what ytou get <3
(Britney Spears)