- Arch-proaudio - lists.archlinux.org

[arch-proaudio] Linux Audio Conference 2020 : deadline extension
by Linux Audio Conference 28 Jan '20

28 Jan '20

The 18th Linux Audio Conference call for participation is being extended for papers, posters and workshops, to the 9th of February 2020. Reminder : The conference will take place May 11-13, 2020, at the SCRIME, part of the University of Bordeaux in France. Up-to-date information is 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. With our best regards, The Linux Audio Conference Team

1 0

[arch-proaudio] Linux Audio Conference 2020 : Call for scientific & artistic works
by Linux Audio Conference 08 Oct '19

08 Oct '19

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

1 0

[arch-proaudio] Aeolus in text mode segfaulting
by Jeanette C. 03 Oct '19

03 Oct '19

Hey hey, Aeolus' text mode keeps failing, it has done so for a while. Since I didn't strictly need it at the time, I let it go. All retunings and the setup routines run through correctly. gdb shows that the error occurs once rl_initialize from readline is called. The final problem occurs in libncursesw. In itself this is strange, since I run a lot of other apps relying on libreadline and libncurses. From the arch packages this would include ecasound and mod-host, amongst others. As a self-compiled binary this also includes Yoshimi. All link to the same libraries, libncursesw.so.6 and libreadline.so.8 . Could someone suggest further steps, please? Or maybe even a direct solution? Thanks you 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 never try to change me I can be nobody else And I like the way I am <3 (Britney Spears)

2 4

[arch-proaudio] kdenlive - audio time delay
by Daniel Wilhelm 30 Sep '19

30 Sep '19

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

2 1

[arch-proaudio] Anyone going to FrOSCon this weekend?
by SpotlightKid 08 Aug '19

08 Aug '19

Hi all, anyone going to FrOSCon in St. Augustin, Germany, this weekend? I'll probably be there on Saturday to listen to a few talks and generally mingle with the FLOSS crowd. If anyone wants to have a chat about audio on Arch, building audio AUR packages and related stuff, I'm up for it. https://www.froscon.de/ Chris Arndt

2 1

[arch-proaudio] JACK 1: extreme CPU usage (since update from 5.0 kernel)
by Jeanette C. 06 Aug '19

06 Aug '19

Hey hey everyone, JACK has long had a habit of grabbing a lot of CPU time, even in idel mode, getting to 100% (one of four cores) and raising the CPU from 800MHz to 3GHz. But it usually took some time. Restarting the JACK daemon resolved the issue for some time. Since the update from the 5.0.x kernel to first a 5.1(?) (last Sunday) and now 5.2.5 has incrased the issue. JACK quickly starts grabbing lots of CPU, heating up the system (and waisting energy). This gets to a point where I can't change terminals. Only when I stop JACK, the system will react to an already pressed alt+fN command, as if it was stored in a bugffer, but couldn't be reacted upon. The keystrokes are read immediately, as verified by showkey, the problem is JACK as verified, by always getting a prompt from tty1 after shutting it down. I have set the kernel commandline parameter audit=0 . Another suggestion recommended trying something with spectre mitigation. There was mention of a few kernel parameters and possible security risks, which went over my head. Can someone please help me through this? Hints, tips, maybe similar experiences and good solutions? I have run: realTimeConfigQuickScan which aggreed with everything except that my kernel isn't real lowlatency. It's the standard pacman kernel. And it didn't like the schedutil governor, which I change to performance, when I'm recording. More info? CPU: AMD Athlon(tm) II X4 640 Processor (/proc/cpuinfo) quadcore with up to 3GHz 4GB of RAM (mostly no issues at all) no GUI Soundcard: twl M-Audio Delta 1010LT sync'ed by SP/DIF and bundled into one device through ALSA through multi device type. Any help is appreciated! Thanks you and best wishes, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * SoundCloud: https://soundcloud.com/jeanette_c * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * GitHub: https://github.com/jeanette-c * Twitter: https://twitter.com/jeanette_c_s There's a girl in the mirror I wonder who she is Sometimes I think I know her Sometimes I really wish I did <3 (Britney Spears)

2 6

[arch-proaudio] geonkick package update
by SpotlightKid 04 Aug '19

04 Aug '19

Hi all, I noticed the 'geonkick' package in community is out-of-date. Probably because the project switched from Qt to the redkite GUI toolkit, which was not yet in the Arch or AUR repositories. https://www.archlinux.org/packages/community/x86_64/geonkick/ So I made an AUR package for redkite: https://aur.archlinux.org/packages/redkite/ And here's an updated PKGBUILD for geonkick using it: https://gist.github.com/SpotlightKid/9fbee0dbb54aa82ffdd15bf90c3b86b3 Cheers, Chris

2 1

[arch-proaudio] New additions since some time this year
by David Runge 24 Jun '19

24 Jun '19

Hey all, I'd like to give information on the work being done so far: Since my last mail regarding the "new packages in [community] topic", I've added a few more: * dpf-plugins * fabla * luppp * non-daw (non-{mixer,session-manager,timeline}) * sorcer * sonic-pi (but that's seriously on its way out again...) * infamousplugins * zam-plugins * rt-tests * giada * artyfx * freewheeling * avldrums.lv2 * blop.lv2 * eteroj.lv2 * fomp.lv2 * mda.lv2 * midi_matrix.lv2 * moony.lv2 * sherlock.lv2 * vm.lv2 * cmt * convolv2 * din * patchmatrix * spectmorph * lmms (updated to latest RC) * sweep * qmidictl * qxgedit * alsa-tools * python-jack-client * python-pyalsa * python-zita-audiotools * python-zita-jacktools * zita-jclient * zita-jclient * aliki * jaaa * jconvolver * jnoisemeter * njconnect * paulstretch * realtime-privileges * japa * lv2file * noise-repellent * setbfree * ams-lv2 * beatslash-lv2 * gmsynth.lv2 * lsp-plugins * libmusicxml * dragonfly-reverb * wolf-shaper * ssr @Albert: pd-lua is still on the list, let's get in touch! @Chris: dexed can also go to [community], I'll look into it! Most of them are in (at least) one of the audio related groups: "pro-audio", "lv2-plugins", "dssi-plugins", "vst-plugins", "ladspa-plugins" or "realtime" You can have a look with: pacman -Sg <group_name> And install the whole group with: pacman -S <group_name> I have done some (minor) revamps of the relevant Arch wiki pages ([1], [2], [3]), but would love to see many more changes (to remove irrelevant data and add actual good and concise examples). Enjoy! David P.S.: If you have suggestions for more additions, let me know! [1] https://wiki.archlinux.org/index.php/Professional_audio [2] https://wiki.archlinux.org/index.php/Realtime_kernel_patchset [3] https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit -- https://sleepmap.de

5 18

[arch-proaudio] Which compiler is used to build the csound package
by Jeanette C. 08 Jun '19

08 Jun '19

Hey hey, David, could you tell me which compiler is used to build the Csound package? - Is there perhaps a systematic way to find such information? So far, I haven't discovered any, but I'm not too familiar with the Arch package system. Thanks and best wishes, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * SoundCloud: https://soundcloud.com/jeanette_c * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * GitHub: https://github.com/jeanette-c * Twitter: https://twitter.com/jeanette_c_s you made me realize..not to compromise the fact that you and i should meet... <3 (Britney Spears)

2 2

[arch-proaudio] Deprecation of jack2-dbus
by David Runge 23 Apr '19

23 Apr '19

Hi all, I've just completed the further decoupling of libffado from jack/jack2 (libffado had a dependency on jack, but was required for jack2) by turning it into an optional dependency. Besides that, looking at our current setup of the jack2 package, I would like to deprecate the jack2-dbus package. Its sole purpose is to *only* be able to use dbus for starting jack. However, we're the only distribution doing this (IMHO weird) separation (AFAIK) and the standard daemon way of starting it will not go away any time soon. This schizm creates further confusion about what to use (the jack/ jack2 schizm is already confusing enough). jack2 features: * supports classic mode (start with jackd) * supports dbus mode (e.g. start with jack_control or cadence) * defaults to jackd (classic mode) jack2-dbus features: * supports dbus mode (e.g. start with jack_control or cadence) * defaults to dbus Caveats: With the jack2 package defaulting to jackd (classic mode), it means, that as soon as jack is not yet started, any program requesting it, will start jack via the jackd executable. However, jackd will remain started with the settings that application has chosen, once the client quits. If the user wants to use the dbus way of starting jack, then it has to be used explicitely (e.g. with jack_control or a client like cadence), *before* any other client wants to start it. With jack2-dbus an application requesting the start of jack will use the dbus interface (AFAIK). The jack instance will remain running, but due to the more flexible nature of the dbus mode, its parameters can be changed on the fly (e.g. changing the periods). With helper tools, such as cadence it should be possible to start jack with one's session. However, users are not able to use jackd when they have jack2-dbus installed (it's not build). Upsides: In the upcoming jack2 1.9.13 there will a templated systemd user unit, which is able to start jackd (in a more or less static way) based on profiles, defining the parameters. This enables the user to achieve something similar to the dbus-start-with-the-graphical-session way, by enabling starting jackd with the user session (even before login of the graphical session). This is quite a benefit to systemd managed (minimal and especially headless) systems, but is of course more generally applicable. Closing, I would like to add, that it can usually be considered the *easiest and best way* (TM) to start jack *before* any client wants to use it. However, setups vary and what works for one, might not work for the other. I would like to hear your concerns regarding this matter (if any). Best, David P.S.: I'm not using DEs such as Gnome or KDE, so my assumptions about integration might be contrary to what your setup is and I might be missing valuable workflows someone is having. -- https://sleepmap.de

3 5