Linux-audio-user October 2019

linux-audio-user@lists.linuxaudio.org

50 participants
48 discussions

[LAU] How to automatically start zita-j2a/a2j with jack?

by Steven Kruyswijk

Hi all, For a sound playback system I'm putting together, based on a Raspberry Pi 3, I'm looking to have 4 channels of input and output, and to have the system to run automatically at startup. For this, I'm wondering how to (best) execute zita-a2j and zita-j2a; I've tried two methods that don't work: 1. ask Qjackctl to execute the following script after startup: sleep 5 zita-j2a -d hw:CODEC_1 2. execute this script: qjackctl (with auto-start) sleep 10 zita-j2a -d hw:CODEC_1 Executing the zita-j2a manually after Qjackctl has finished starting the jack server does work. Any pointers greatly appreciated! Cheers, Steven -- Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html

6 years, 3 months

Re: [LAU] Behringer X32 - glitch problems

by nik＠parkellipsen.de

Well, the problem seems to be that there's no dedicated physical USB 3.0 port on my machine, the physical port act as the one or the other depending on what you connect. All physical ports have the SuperSpeed symbol, but none of them automatically connects to the (internal) USB 3.0 root hub if I connect a USB 2.0 device, so I assume there's some logic that detects whether the connected device is 2.0 or 3.0 and connects it accordingly. Like, when I connect a USB 3.0 storage device, lsusb shows it as connected to the 3.0 bus. So I my guess would be, if I use a dedicated (external) USB 3.0 hub, it would be detected as a 3.0 device and routed to the (internal) 3.0 bus, and thus the devices connected to the external hub would be as well. But, of course, that's just speculation. I might just get a 3.0 hub and try. Ralf Mardorf wrote on 13.10.2019 18:37 (GMT +02:00): > On Sun, 13 Oct 2019 18:19:15 +0200 (CEST), nik(a)parkellipsen.de wrote: > >Or, if i connect an external USB 3.0 hub, will it wire external > >devices to the 3.0 internal bus? > > USB 3 is backward compatible. Occasionally I connect an USB 2 Scarlett > 18i20 2nd gen to a GA-B85M-D3H mobo's USB 3 slot of an Arch Linux > machine. This works without issues and allows lower latency, than is > possible with a PCIe slot assembled RME HDSPe AIO on the same machine. > Even if the USB 3 port shouldn't be the best for an audio device on > your machine, it at least should sort of work, perhaps causing xruns. > That it doesn't work at all, might be a pointer to an issue of your > computer. > >

6 years, 3 months

Re: [LAU] How to automatically start zita-j2a/a2j with jack?

by Brent Busby

Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> writes: > Why not just using one of those RME audio device connected with the > computer and the other audio device just connected via ADAT only or > ADAT and word clock? There seems to be no need to connect both audio > devices with the computer, if both provide ADAT IOs. > > If hdspmixer should work with the Multiface, you additionally could > workaround the USB class compliant issue of the Babyface, since the IOs > of the Babyface connected via ADAT become quasi IOs of the Multiface > and could be controlled by hdspmixer. I'll try this. I'd be nice to not have to get them both visible in Jack at the same time. -- - Brent Busby + =============================================== + "The introduction of a new kind of music must -- Studio -- + be shunned as imperiling the whole state, for -- Amadeus/ -- + styles of music are never disturbed without -- Keycorner -- + without affecting the most important political -- Recording -- + institutions." --Plato, "Republic" ----------------+ ===============================================

6 years, 3 months

[LAU] Behringer X32 - glitch problems

by nik＠parkellipsen.de

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

6 years, 3 months

[LAU] [ANN] Qtractor 0.9.10 - An Autumn'19 Release

by Rui Nuno Capela

Wholly greetings, Without any further delay, here it goes: Qtractor 0.9.10 (autumn'19) is now released! The shortest and maybe TL;DR change-log for this northern Autumn'19 release goes like this: - Fixed the potential crash-effect in switching MIDI output buses on tracks that are set to show audio output monitoring meters. - Fixed initial session tempo override when importing a standard MIDI file (as reported on issue #230). - An alternate time-signature/meter option is being served to the MIDI clip editor (aka. piano-roll) and allowing for some poly-rythm/meter scenarios on a per MIDI clip basis. - Fixed MIDI "overdub" recording on offset clips. - MIDI bank and program settings now propagating to all MIDI track's clips resp. - Fixed MIDI file format default setting other than SMF Format 0. - Escape key may now be used to reset time and tempo/time-sgnature spin-box controls. - Play-head time and tempo/time-signature controls are now featured in MIDI clip editor toolbars (aka. piano-roll); time display format is also separated from the tracks main application view and defaults to BBT as being most convenient. - All items in the MIDI clip editor's event list are now enabled, selectable and editable, no matter the filter settings for the event views. - Added alternate yet non-official CMake build option. - Improved MIDI clip editor (aka. piano-roll) position and size persistence across session state. - Fix HiDPI display screen effective support (Qt >= 5.6). - Mixer, Connections and MIDI clip editor top-level windows shall have no parent, unless when set as always-on-top tool windows. (REGRESSION) - Make sure compiler flags comply to c++11 as standard. Description: Qtractor [1] is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework [2]. Target platform is Linux, where the Jack Audio Connection Kit (JACK [3]) for audio and the Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio. Website: http://qtractor.org https://qtractor.sourceforge.io http://qtractor.sourceforge.net Project page: https://sourceforge.net/projects/qtractor Downloads: https://sourceforge.net/projects/qtractor/files - source tarball: https://download.sf.net/qtractor/qtractor-0.9.10.tar.gz - source package (openSUSE Tubleweed): https://download.sf.net/qtractor/qtractor-0.9.10-45.rncbc.suse.src.rpm - binary package (openSUSE Tubleweed): https://download.sf.net/qtractor/qtractor-0.9.10-45.rncbc.suse.x86_64.rpm - AppImage [7] packages: https://download.sf.net/qtractor/qtractor-0.9.10-15.x86_64.AppImage Git repos: https://git.code.sf.net/p/qtractor/code https://github.com/rncbc/qtractor.git https://gitlab.com/rncbc/qtractor.git https://bitbucket.org/rncbc/qtractor.git Wiki (help still wanted!): https://sourceforge.net/p/qtractor/wiki/ - static rendering: http://qtractor.org/doc http://qtractor.sourceforge.net/doc https://qtractor.sourceforge.io/doc - user manual & how-to's: https://download.sf.net/qtractor/qtractor-manual-and-howtos.epub https://download.sf.net/qtractor/qtractor-manual-and-howtos.pdf License: Qtractor [1] is free, open-source Linux Audio [5] software, distributed under the terms of the GNU General Public License (GPL [6]) version 2 or later. References: [1] Qtractor - An audio/MIDI multi-track sequencer http://qtractor.org https://qtractor.sourceforge.io http://qtractor.sourceforge.net [2] Qt framework, C++ class library and tools for cross-platform application and UI development https://qt.io/ [3] JACK Audio Connection Kit http://jackaudio.org [4] ALSA, Advanced Linux Sound Architecture https://www.alsa-project.org/ [5] Linux Audio consortium of libre software for audio-related work https://linuxaudio.org [6] GPL - GNU General Public License https://www.gnu.org/copyleft/gpl.html [7] AppImage, Linux apps that run anywhere https://appimage.org/ See also: https://www.rncbc.org/drupal/node/2041 Enjoy && Share the fun. -- rncbc aka Rui Nuno Capela

6 years, 3 months

[LAU] setBfree not accepting midi.driver property

by Jeanette C.

Hey hey, I am currently experiencing a problem with setBfree, namely that it doesn't honour the value set for midi.driver and always uses jack. I have tried putting it inside a custom config, set it in the default config (in both ~/.config/setBfree and /usr/share/setBfree and set it on the commandline: setBfree midi.driver=alsa with variations: "midi.driver=alsa" and midi.driver="alsa" No luck. I am running setBfree version 0.8.8. I have just updated to 0.8.9 which still reports as 0.8.8, this is on ArchLinux using the "official" package. Is it that my configuration is out of date perhaps? Can someone verify this or point out a solution, please? 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 If only I could trade the fancy cars For a chance today, it's incomparable <3 (Britney Spears)

6 years, 3 months

Re: [LAU] Behringer X32 - glitch problems

by nik＠parkellipsen.de

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 > > >

6 years, 3 months

[LAU] Proper signal flow when tracking + processing microphone input

by Andrew A. Grathwohl

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 )

6 years, 3 months

[LAU] Linux Audio Conference 2020 : Call for scientific & artistic works

by Linux Audio Conference

The 18th Linux Audio Conference call for participation is open. The conference will take place May 11-13, 2020, at the SCRIME, part of the University of Bordeaux in France. Up-to-date information will be available at the following address : https://lac2020.sciencesconf.org/ Linux Audio Conference is the premier meeting of developers, researchers, and artists developing and using free, libre and open-source audio software, mainly on the GNU/Linux operating system. The conference is part of the Linux Audio consortium. A special event will take part the day before, on Sunday the 10th May 2020: attendants may want to book their week-end. This edition's date has been chosen so that interested parties may be able to attend the International Faust Conference, which will happen in Paris 14-15 May 2020. We kindly invite researchers, developers and artists alike to take part to the event and propose their work. Important information ===================== - Submissions must go through the conference website: https://lac2020.sciencesconf.org. - Submissions must be written in English. - Submissions will be peer-reviewed by a jury of experts with adequate qualifications in regard to the topic of the submission, excluding lightning talks. - Submissions will be present in the proceedings, including workshops, excluding lightning talks. - Submissions can focus on technical, artistic or scientific issues. - Contact address: lac(a)linuxaudio.org - Deadlines (all deadlines are at 23:59 UTC -12:00): * Paper & poster submission deadline: 31/12/2019 * Workshop submission deadline: 31/01/2020 * Notification to authors: 15/02/2020 * Camera-ready deadline: 25/03/2020 * Code jam: 10/05/2020 * Conference dates: 11/05/2020 to 13/05/2020 Call for Papers / Posters / Workshops ===================================== The general themes are audio research and development on Linux systems, & FLOSS (free, libre and open-source) multimedia. We encourage submissions on non-Linux FLOSS operating systems (BSDs, Haiku, Fuschia, IncludeOS, Redox...) as well as non audio-centric works: video, network protocols, performing arts, video games... The 2020 edition has a leading theme: Libre Languages. Papers ------ Paper templates are available to download from here: https://github.com/linuxaudio/lac-paper-templates. The length of a paper is 4 to 8 pages, with up to 5 keywords, and an abstract of 100 to 200 words. The abstract will be published on the conference website once the paper has been accepted. Initial submissions must be anonymized ; please inform us of any potential conflict of interest. The full paper will be made available on the website at the beginning of the conference. Accepted papers will be presented in an oral session. In order for a paper to appear in the proceedings, it must have been presented orally at the conference by at least one of its authors. The length of the presentation is 20 minutes followed by a 5 minutes discussion. Posters ------- LAC2020 accepts submission of posters related to any of the themes mentioned before. We cannot print posters. There is a printing shop located very close to the university which can print a poster from a PDF (Copifac Talence, 548 Cours de la Libération). Workshops --------- LAC2020 accepts workshop proposals. An abstract and a description of the workshop following the paper template (1 or 2 pages max) is required. If the workshop participants need to install any kind of software, please write it plainly in the workshop abstract. Workshops must last at most two hours ; if shorter, please precise the expected duration in the submission so that we can schedule them accordingly. Lightning talks ------------------ Lightning talks last 5 minutes and can be very useful to quickly present your latest software development. They will not be submitted to peer review and can cover peripheral topics, including discussions about the Linux Audio community or other areas of free software. Due to the very short time, if a medium is required, you will be required to submit it : * As slides in PDF format. * As a video file. The medium will be made readily available on a plugged-in computer. Non-exhaustive list of accepted topics -------------------------------------- * Art projects done with free software systems. * Audio architecture of operating systems * Audio plug-ins * Education, teaching * Graphical environments for creation * Hardware support * Interactive Art * Interfaces for musical expressivity * Live coding * Embedded hardware & support (ARM, RISC-V, etc) * Mobile hardware & support (phones, tablets) * Musical production and related tools * Network protocols * Network distribution * New Media Art * Open hardware * Performing arts * Programming languages for creation * Real-time programming languages * Real-time operating systems and kernels * Sensors, human-machine interfaces in a real-time context * Signal and sound processing * Sound spatialisation * Standards, interoperability * Video * Video games Call for Artworks ================= LAC 2020 invites submissions of artistic works involving the use of free, libre and open-source software and/or hardware. Pre-recorded music, interactive installations and live performances are accepted. A jury will select the compositions and installations to be included in the conference program according to artistic merit and technical feasibility. Please be prepared to perform your work yourself and make sure that you have all resources needed to perform your piece (e.g. instruments, props, other performers, etc.). The installations will be located in multiple places, which are described on the website at the following address : https://lac2020.sciencesconf.org/resource/page/id/3 Each place will have a different sound system available. Musical works and installations can address all areas of media art as long as they include some level of audio creation using free software. Examples of accepted works can include: * Acoustic Music * Acousmatic music * Art installations * Electronic Music * Electroacoustic Music * Game in art * Interactive Art * Live code * Mixed Music * Musique concrète * New Media Art * Web and Connected Art Code jam ======== The day before the official beginning of the conference (10th may) will feature a code jam. The goal of the code jam is to provide a space for teams developing Linux audio software to meet in person and discuss development issues in an informal way, as well as introduce new contributors to the various codebases, and overall to perform a live state of the art of audio software on free systems. The code jam will have a topic, which will be disclosed upon opening. It is not mandatory to follow it as it mainly serves to provide inspiration. Starting from Sunday 21:00, a live code session will begin. It is open to everyone. If you plan to participate, please notify us in the registration form with: * The kind of media you plan to use ? (Audio, video, both...) * The output ports are available on your hardware ? (HDMI, VGA, ...) ------------------ We thank you in advance for your participation and kindly invite you to share this call to any interested organization or person you may be aware of. With our best regards, The Linux Audio Conference team

6 years, 4 months

[LAU] It's been a while

by Will Godfrey

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.

6 years, 4 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user October 2019