Hi Olli,
thank you very much.
On Sun, 4 Dec 2016 15:39:55 +0100, Olli wrote:
>I haven’t adjusted any IRQ settings, just some minor, usual tweaks for
>Arch Linux. Let me know if you want to know any additional details or
>if I should run any specifc query!
Usually I'm interested in MIDI jitter, but in this case there's no need
to run alsa-midi-latency-test for me.
There are just two other things I wish to know.
1. Are you using a first or second generation 18i20?
I read that for the second generation, there should be issues
related to the mixer.
2. Do I understand correctly, 64 samples cause more latency than 128
samples?
>48 kHz, 256 samples, 2 periods:
>detected roundtrip latency: 1389 samples (28,938 ms)
>systematic latency: 621 samples (12,938 ms)
>
>48 kHz, 128 samples, 2 periods:
>detected roundtrip latency: 1239 samples (25,812 ms)
>systematic latency: 471 samples (9,812 ms)
>
>48 kHz, 64 samples, 2 periods:
>detected roundtrip latency: 1240 samples (25,833 ms)
>systematic latency: 472 samples (9,833 ms)
>
>48 kHz, 256 samples, 3 periods:
>detected roundtrip latency: 1389 samples (28,938 ms)
>systematic latency: 621 samples (12,938 ms)
>
>48 kHz, 128 samples, 3 periods:
>detected roundtrip latency: 1287 samples (26,812 ms)
>systematic latency: 519 samples (10,812 ms)
>
>48 kHz, 64 samples, 3 periods:
>detected roundtrip latency: 1390 samples (28,958 ms)
>systematic latency: 622 samples (12,833 ms)
Regards,
Ralf
Hi all!
This morning I can't seem to get QMidiArp working.
The custom UI isn't available anymore, for starters. No "Edit" in
Qtractor's menu, only "properties" witch would not be a problem (on the
contrary, I like generic UIs) if it was working :/ Note that there does
not seem to be a way to write patterns, like in the custom UI, the text
field for that is not present in the generic UI.
I'm used to QMidiArp, I've been using it for years, I know that you have
to tell him the MIDI channel ins and outs and such, but still, no luck.
I tried building it from source, that went pretty well, now I'm pretty
sure I have the last version installed, but still no luck.
Qtractor : 0.8.0.4git.415519 Qt 5.5.1)
QMidiArp : 0.6.5 (That's what the standalone version says, the LV2
plugin doesn't display any version)
Can somebody confirm that? This sad state of affairs is ruining my day :(
yPhil
PS -wait, it's working (both UI and actual arpeggio) in the current
Qtractor build (0.7.9, Qt 4.8.7) so it's obviously a Qt problem ; is
there something I should tell to either Qtractor or QMidiArp build
script to get them to play together?
--
Yassin Philip - New album out NOW
http://yassinphilip.bitbucket.org
Hi,
I am trying to built a Raspberry Pi based 96K audio recorder for scheduled
WAV recordings.
Has anyone successfully made 96K recordings on PI / Linux with the USBPre2?
https://www.sounddevices.com/products/portable-audio-tools/usbpre2
If yes, any experiences on what to watch out for?
The manufacturers could not tell if it will work. In their description it
only guarantees to work on linux up to 48K.
Also i'd be interested if anyone had good experiences on Linux / PI with
other USB Audio Class 2
devices and high sample rates.
Thanks very much for any tips!
David.
--
View this message in context: http://linux-audio.4202.n7.nabble.com/Recording-in-96K-on-Linux-Raspberry-P…
Sent from the linux-audio-user mailing list archive at Nabble.com.
Hi List!
I'd like to reproduce the percussive sound that can be heard used as
some sort of "snare" in this video
<https://www.youtube.com/watch?v=KQcI7oKE1pc>, you know the "marble on a
glass table" thingie? I'm guessing it's a typical subtractive analog
synth sound (with a special reverb, apparently) so maybe there can be a
way to approximate it using our arsenal, maybe SynthV1 or ZASFX?
Thanks for any pointer,
yPhil
--
Yassin Philip - New album out NOW
http://yassinphilip.bitbucket.org
Dear Linux Audio community,
please find below a link to a job opportunity in Oldenburg, Germany:
http://www.hoertech.de/images/hoertech/pdf/Stellenanzeigen/16-11-28_Stellen…
The work is mainly development in C++ for the Master Hearing Aid, which
we presented back in 2009 at the LAC in Parma
(http://lac.linuxaudio.org/2009/cdm/Friday/07_Grimm/index.html), and
which will become open source within the next months.
The job position is at a small company in a team of developers, with
close collaboration with the university of Oldenburg.
For details, please see the link above.
Best regards,
Giso
Hi,
I try to use https://aur.archlinux.org/packages/ardour5/. Ardour 5
copied the Ardour 4 settings, but I get nearly unreadable small fonts
and no bright theme is available. The short cut for zoom in "=" doesn't
work. The theme "Blueberry Milk" is missing. I'm not against dark
themes, but all provided dark themes at least in combination with the
much too small fonts, provide much too less contrast. Im using a CTR
1152x864, no unusual DPI settings, with relatively dark brightness
settings.
The only question for the moment is: How can I enlarge the font size?
By default the Ardour 4 fonts were to small, too, but I at least could
read enough, to find where to enlarge the fonts.
$ pacman -Q ardour5
ardour5 5.5-1
Regards,
Ralf
The Guitarix developers proudly present
Guitarix release 0.35.2
Guitarix is a tube amplifier simulation for
jack (Linux), with an additional mono and a stereo effect rack.
Guitarix includes a large list of plugins[*] and support LADSPA / LV2
plugs as well.
The guitarix engine is designed for LIVE usage, and feature ultra fast,
glitch and click free preset switching and is full Midi and/or remote
controllable (the Web UI is not included in the distributed tar ball).
This release mainly fix a build issue in Debian #839354 and ARCH
Beside that, the changes are:
* add stereo cabinet plugin
* fix bypass insert jack port with midi CC
* add menu option to set a midi controller for engine bypass
* add scroll wheel support to status images
* switch to use glib-compile-resources instead gdk-pixbuf-csource to
include images into libgxw.
* Fix Preset switching issue in lv2 amps and cabinet
* disable midi control for un-loaded plugs
* add check if LV2 ports are valid
* fix bug #34
Note that a couple of new additional guitar related plugs in LV2 format
been available on github now. They all work very well in guitarix.
Check them out here:
https://github.com/brummer10?tab=repositories
Please refer to our project page for more information:
http://guitarix.org
Download Site:
http://sourceforge.net/projects/guitarix/
Forum:
http://guitarix.sourceforge.net/forum/
Please consider visiting our forum or leaving a message on
guitarix-developer(a)lists.sourceforge.net
<mailto:guitarix-developer@lists.sourceforge.net>
regards
hermann
On Dec 7, 2016 10:52, termtech <termtech(a)rogers.com> wrote:
>
> On Wednesday, December 7, 2016 10:43:22 AM EST David Jones wrote:
> > On Dec 7, 2016 06:48, termtech <termtech(a)rogers.com> wrote:
> > > On Wednesday, December 7, 2016 7:34:25 AM EST David Klann wrote:
> > > > On 12/03/2016 01:50 PM, termtech wrote:
> > > > > On Saturday, December 3, 2016 1:20:09 PM EST David Klann wrote:
> > > > >> Greetings,
> > > > >>
> > > > >> Long-time Linux user, and relatively new JACK user here. I have built
> > > > >> ...
> > > > >
> > > > > Hello, this might be a long shot, but maybe not.
> > > > > You mentioned it did this when Jack was disabled,
> > > > >
> > > > > so it seems Jack is not the problem.
> > > > >
> > > > > Look for the LAU thread on Wednesday titled:
> > > > > "[LAU] [SOLVED] Crackles in audio, drifting intermittent noise etc."
> > > > > I was having very strange phasing problems, although I didn't notice
> > > > >
> > > > > from channel to channel but I wasn't really listening for that.
> > > > >
> > > > > I knew it was hardware related, only that could cause it.
> > > > >
> > > > > My ONLY solution was changing the number of enabled CPU cores,
> > > > >
> > > > > either through my BIOS or through Linux commands such as:
> > > > > echo 0| sudo tee /sys/devices/system/cpu/cpu3/online
> > > > > cat /sys/devices/system/cpu/cpu3/online
> > > > >
> > > > > I found that I must run with just ONE core for the most stability.
> > > > > (I had posted that I found TWO cores were OK but actually
> > > > >
> > > > > further test revealed it was not OK.)
> > > > >
> > > > > So try:
> > > > > echo 0| sudo tee /sys/devices/system/cpu/cpu1/online
> > > > > echo 0| sudo tee /sys/devices/system/cpu/cpu2/online
> > > > > echo 0| sudo tee /sys/devices/system/cpu/cpu3/online
> > > > >
> > > > > cpu0 will always be online.
> > > > >
> > > > > Tim.
> > > >
> > > > Hi Tim!
> > > >
> > > > Thanks for this tip! I probably never would have considered this even
> > > > though it was a vague, nagging thought in the back of my head.
> > > >
> > > > Disabling three of the four cores (or hyperthreads?) on the CPU fixed
> > > > the problem for us!
> > > >
> > > > Specifically (and to tweak your command set), I placed the following in
> > > > /etc/rc.local to ensure the CPU disabling survives a reboot:
> > > >
> > > > <code>
> > > > for c in 1 2 3; do echo 0 > /sys/devices/system/cpu/cpu${c}/online; done
> > > > </code>
> > > >
> > > > In reading the "Crackles in audio..." thread, I am curious to know why
> > > > this happens with some CPUs and not with others. My understanding is
> > > > that this is fundamentally a timing issue between processes that are
> > > > running on different CPUs (or cores). So, while it's not specifically a
> > > > JACK issue, if the jackd process is running on CPU0 and the audacity
> > > > process is running on CPU3 then a timing error may be introduced between
> > > > those two CPU's. Is that a reasonable summary of the effect?
> > > >
> > > > And for my next trick, I will experiment with the taskset(1) command to
> > > > set processor affinity for the audio processes. Maybe we can leave all
> > > > four CPU's enabled and still avoid the "left-right channel skew"
> > > > problem.
> > >
> > > Ah thanks, I was looking for something like taskset.
> > > I wondered if the entire audio chain, from driver to application,
> > > should somehow be set to one CPU even if all four are enabled.
> > > Please let us know how it works out for you.
> > >
> > > I am very late to this multi-core party. It's my first such PC.
> > > I am sure this episode has been repeated before in other threads.
> > > It's hard to dig through the confusion and misinformation.
> > > Even though I did research these CPUs before buying, I didn't
> > > expect it would affect things in this manner.
> > >
> > > Tim.
> > >
> > > > Thank you everyone who weighed in on this, and especially Paul for
> > > > pointing out that it cannot be an issue introduced by JACK.
> > > >
> > > > Best regards,
> > > >
> > > > ~David Klann
> >
> > Well, I have 2 PCs I do audio on. One has 4-core AMD Phenom II (no
> > hyperthreading). Other has Intel i7 (4 cores + hyperthreading). Have never
> > tweaked anything like what you're talking about and have never had any such
> > problem as you had.
> >
> > I do not have Pulseaudio installed on either of them.
> >
> > My final guess at root of problem: hardware issue with CPU itself. Maybe
> > some manufacturing defect that only manifests when all cores are in use?
>
> It appears to be something related to certain (older?) PCI audio cards.
> Although, I think Len said he's running a similar card as mine
> and hasn't seen any problems.
>
> An older SBLive! PCI card appeared to work fine. Maybe I should test again...
>
> Tim.
Never had it when I used an AudioPhile 2496 PCI card, either, on the AMD machine. The i7's in a laptop, so limited only to internal audio or external USB audio.
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
On Dec 7, 2016 06:48, termtech <termtech(a)rogers.com> wrote:
>
> On Wednesday, December 7, 2016 7:34:25 AM EST David Klann wrote:
> > On 12/03/2016 01:50 PM, termtech wrote:
> > > On Saturday, December 3, 2016 1:20:09 PM EST David Klann wrote:
> > >> Greetings,
> > >>
> > >> Long-time Linux user, and relatively new JACK user here. I have built
> > >> ...
> > >
> > > Hello, this might be a long shot, but maybe not.
> > > You mentioned it did this when Jack was disabled,
> > >
> > > so it seems Jack is not the problem.
> > >
> > > Look for the LAU thread on Wednesday titled:
> > > "[LAU] [SOLVED] Crackles in audio, drifting intermittent noise etc."
> > > I was having very strange phasing problems, although I didn't notice
> > >
> > > from channel to channel but I wasn't really listening for that.
> > >
> > > I knew it was hardware related, only that could cause it.
> > >
> > > My ONLY solution was changing the number of enabled CPU cores,
> > >
> > > either through my BIOS or through Linux commands such as:
> > > echo 0| sudo tee /sys/devices/system/cpu/cpu3/online
> > > cat /sys/devices/system/cpu/cpu3/online
> > >
> > > I found that I must run with just ONE core for the most stability.
> > > (I had posted that I found TWO cores were OK but actually
> > >
> > > further test revealed it was not OK.)
> > >
> > > So try:
> > > echo 0| sudo tee /sys/devices/system/cpu/cpu1/online
> > > echo 0| sudo tee /sys/devices/system/cpu/cpu2/online
> > > echo 0| sudo tee /sys/devices/system/cpu/cpu3/online
> > >
> > > cpu0 will always be online.
> > >
> > > Tim.
> >
> > Hi Tim!
> >
> > Thanks for this tip! I probably never would have considered this even
> > though it was a vague, nagging thought in the back of my head.
> >
> > Disabling three of the four cores (or hyperthreads?) on the CPU fixed
> > the problem for us!
> >
> > Specifically (and to tweak your command set), I placed the following in
> > /etc/rc.local to ensure the CPU disabling survives a reboot:
> >
> > <code>
> > for c in 1 2 3; do echo 0 > /sys/devices/system/cpu/cpu${c}/online; done
> > </code>
> >
> > In reading the "Crackles in audio..." thread, I am curious to know why
> > this happens with some CPUs and not with others. My understanding is
> > that this is fundamentally a timing issue between processes that are
> > running on different CPUs (or cores). So, while it's not specifically a
> > JACK issue, if the jackd process is running on CPU0 and the audacity
> > process is running on CPU3 then a timing error may be introduced between
> > those two CPU's. Is that a reasonable summary of the effect?
> >
> > And for my next trick, I will experiment with the taskset(1) command to
> > set processor affinity for the audio processes. Maybe we can leave all
> > four CPU's enabled and still avoid the "left-right channel skew" problem.
>
> Ah thanks, I was looking for something like taskset.
> I wondered if the entire audio chain, from driver to application,
> should somehow be set to one CPU even if all four are enabled.
> Please let us know how it works out for you.
>
> I am very late to this multi-core party. It's my first such PC.
> I am sure this episode has been repeated before in other threads.
> It's hard to dig through the confusion and misinformation.
> Even though I did research these CPUs before buying, I didn't
> expect it would affect things in this manner.
>
> Tim.
>
> > Thank you everyone who weighed in on this, and especially Paul for
> > pointing out that it cannot be an issue introduced by JACK.
> >
> > Best regards,
> >
> > ~David Klann
Well, I have 2 PCs I do audio on. One has 4-core AMD Phenom II (no hyperthreading). Other has Intel i7 (4 cores + hyperthreading). Have never tweaked anything like what you're talking about and have never had any such problem as you had.
I do not have Pulseaudio installed on either of them.
My final guess at root of problem: hardware issue with CPU itself. Maybe some manufacturing defect that only manifests when all cores are in use?
Glad you found a solution!
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com