Linux-audio-user January 2018

linux-audio-user@lists.linuxaudio.org

59 participants
67 discussions

[ANN] QmidiCtl 0.5.1 - An Early Winter'18 Release

by Rui Nuno Capela

Hi there! Happy new year to y'all! I know I'm a little bit late on that, but can you _feel_ the news? No? There's _no fake news_ whatsoever! I'd let you solve the riddle by yourself as it's way more fun that way ;) QmidiCt 0.5.1 (early winter'18) released! QmidiCt [1] is a MIDI remote controller application that sends MIDI data over the network, using UDP/IP multicast. Inspired by multimidicast [6] and designed to be compatible with ipMIDI for Windows [7]. QmidiCt [1] has been primarily designed for the Maemo [8] enabled handheld devices, namely the Nokia N900 [9] and also being promoted to the Maemo Package [10] repositories. Nevertheless, QmidiCtl [1] may still be found effective as a regular desktop application as well. See also: QmidiNet [2] - A MIDI network gateway via UDP/IP multicast. Website: http://qmidictl.sourceforge.net https://qmidictl.sourceforge.io Project page: http://sourceforge.net/projects/qmidictl Downloads: http://sourceforge.net/projects/qmidictl/files - source tarball: http://download.sf.net/qmidictl/qmidictl-0.5.1.tar.gz - source package: http://download.sf.net/qmidictl/qmidictl-0.5.1-13.rncbc.suse.src.rpm - binary package: http://download.sf.net/qmidictl/qmidictl-0.5.1-13.rncbc.suse.x86_64.rpm - AppImage [11] package: http://download.sf.net/qmidictl/qmidictl-0.5.1-3.x86_64.AppImage - Android package: (*NEW*;) http://download.sf.net/qmidictl/qmidictl-0.5.1-3.apk https://play.google.com/store/apps/details?id=org.rncbc.qmidictl https://qmidictl.en.aptoide.com/ Git repos: http://git.code.sf.net/p/qmidictl/code https://github.com/rncbc/qmidictl.git https://gitlab.com/rncbc/qmidictl.git https://bitbucket.com/rncbc/qmidictl.git Change-log (since last QStuff* End-of-Autumn'17 release [12]): - A little hardening on the configure (autoconf) macro side. - A rather naive attempt to port to the Android-Qt platform; also introducing an (Android) Action Bar menu look-a-like. License: QmidiCt [1] is free, open-source Linux Audio [4] software, distributed under the terms of the GNU General Public License (GPL) version 2 or later [5]. References: [1] QmidiCtl - A MIDI Remote Controller via UDP/IP Multicast http://qmidictl.sourceforge.net [2] QmidiNet - A MIDI Network Gateway via UDP/IP Multicast http://qmidinet.sourceforge.net [3] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [4] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [5] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [6] multimidicast - sends and receives MIDI from ALSA sequencers over network http://llg.cubic.org/tools/multimidicast [7] ipMIDI - MIDI over Ethernet ports - send MIDI over your LAN http://nerds.de [8] Maemo.org - Home of the Maemo community http://www.maemo.org [9] Maemo.org Wiki - Nokia N900 http://wiki.maemo.org/Nokia_N900 [10] Maemo.org - Downloads: QmidiCtl http://maemo.org/downloads/product/Maemo5/qmidictl [11] AppImage, Linux apps that run anywhere http://appimage.org/ [12] The QStuff* End of Autumn'17 Release http://www.rncbc.org/drupal/node/1876#qmidictl See also: http://www.rncbc.org/drupal/node/1881 Enjoy && keep the fun. -- rncbc aka. Rui Nuno Capela

6 years, 3 months

Songanalysis and other beat detection programs

by Jeanette C.

Hey hey, does anyone still use songanalysis? It's still hosted on juliencoder.de . I just reinstalled it on my current 64bit Archlinux and it fails to do its work, either with a segmentation fault or no work done. If no one else uses it, I'll remove it in the near future. Is there any other text-based software that can do beat/tempo detection out of the box? Best wishes, Jeanette -------- * website: http://juliencoder.de - for summer is a state of sound * SoundCloud: https://soundcloud.com/jeanette_c Don't worry, you're gonna be alright, But Cinderella's got to go <3 (Britney Spears)

6 years, 3 months

jpmidi

by Jeanette C.

Hey again, does anyone use jpmidi and rely on the juliencoder.de hosted copy? If not that too could be removed in the near future. Best wishes,m Jeanette -------- * website: http://juliencoder.de - for summer is a state of sound * SoundCloud: https://soundcloud.com/jeanette_c Don't worry, you're gonna be alright, But Cinderella's got to go <3 (Britney Spears)

6 years, 3 months

OT Design of audio space

by worik

Friends Not Linux specific. I am involved in the design of one, and renovation of another, space for performing amplified music. I have been looking for advice on acoustic design. In both cases there is nothing I can do about the basic external shape but in both cases I have a lot of control over the internal lining design. Acoustic isolation is important, and I can find advice on that (plenty) on the web. But what I cannot find is advice on how to make it sound good inside. The b3est advice I have had was a throwaway comment about avoiding right angles, and it seems logical to me to avoid parrallel walls that can support a standing wave and be susceptible to resonance. But beyond that I am a bit at sea. Is there any place on the web that documents best practice for some one in this position? Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 3 months

Re: [LAU] [Rosegarden-user] RG 17.04 seems to leave lock files behind

by david

On 01/10/2018 07:59 AM, Will Godfrey wrote: > On Wed, 10 Jan 2018 08:40:55 -0500 > Ted Felix <ted(a)tedfelix.com> wrote: > >> On 01/10/2018 02:46 AM, david wrote: >>> Was completely unable to duplicate the problem. >>> >>> Must have been the phases of the moon or something. Thanks for fixing it >>> quantum-mechanics-style simply by turning your attention toward it! :) >> >> Ha! Computers are afraid of me. >> >> Lock file problems tend to happen when rg crashes. My best guess is >> that it was crashing when it was going down and now it isn't. >> >> Ted. >> > > Another way that's caught me (rather more often than I'd like to admit) is > shutting down the desktop, without first shutting down Rosegarden. Didn't do that! > Wasn't there some discussion on adding some kind of time stamp to the lock > file, so that it will ignore one that was (say) over 24 hour old. I don't remember if there was a timestamp in the orphaned lockfile, but it clearly wouldn't have been over 24 hours old. -- David W. Jones gnome(a)hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.com

6 years, 3 months

Re: [LAU] How to get started writing a JACK app? (also what distro for BeagleBone)

by Paul Davis

On Wed, Jan 10, 2018 at 3:48 PM, Andrew Voelkel <jandyman.voelkel(a)gmail.com> wrote: > Glad to hear the discussion. From an outsider’s point of view, there are > few things I don’t get. > > > > First, if each JACK app is a separate process, then theoretically you have > to do a bunch of expensive process context switches for each audio buffer. > In the scheme of things, a context switch is typically not very expensive compared to a typical audio buffer size (say 16 samples and up). The only way it gets unusually expensive is if a process touches a lot of memory during its execution. This isn't impossible in an audio/DSP context, but it isn't very likely either. > And then there is interprocess communication. Uses shared memory buffers? > it's all in shared memory. there's no communication overhead. As opposed to a typical plug-in architecture where everything runs under > the host process. It is amazing to me that an interprocess scheme wouldn’t > run into major problems under compute load when running with the small > buffers needed for low latency. > be amazed :) > > > What am I missing here? > > > > The other thing I’m used to seeing in a plug in API is setup for buffer > sizes, sample rates, audio IO. The host centralizes this process. > JACK does the same thing. Each client has no control over those things (at least, not in the normal way). They can ask to change the buffer size, but their request may be ignored, or it may be reset by something else. Just like in a plugin architecture. Then there is advertising your pins and capabilities. I was mystified when > looking at the simple JACK examples that I didn’t see code for dealing with > these issues (e.g. being sample rate aware). > JACK clients have only one thing of interest to other clients: ports. These are all clearly visible, and tagged appropriately (though for most clients, there's almost no tagging to do)

6 years, 3 months

Re: [LAU] How to get started writing a JACK app? (also what distro for BeagleBone)

by Paul Davis

As Benoit suggested, there are plugin APIs on Linux too (both LV2 and LinuxVST). If you would write an AU for MacOS, you could write a plugin on Linux too. There are plentiful hosts, some of them extremely lightweight (i.e. they don't really do anything themselves). Normal JACK clients introduce a tiny amount of overhead and add no latency whatsoever. It is quite common (unfortunately in my view these days) to implement things as JACK clients (i.e. standalone programs) on Linux, rather than as plugins (though this changing). On Tue, Jan 9, 2018 at 11:07 PM, Andrew Voelkel <jandyman.voelkel(a)gmail.com> wrote: > Hi, > > > > Maybe I need to ask a different question. My goal is to stick my real time > processing algorithm in between x number of audio inputs coming from a USB > audio interface, and then send the outputs to y number of audio outputs on > the same USB audio interface. Low latency is important. Being able to add > in other processing from third parties would be nice, but it isn’t > essential. > > > > Is writing a JACK client the right way to do this? If so, what is the > right approach? If not, what is the right way to do this? > > > > On the Apple platform, I do this by writing an Audio Unit, and either > leverage a DAW host application like Logic or the Apple AVAudioEngine to > serve as a host for my processing algorithm. The host gets the inputs from > the audio interface, I process the audio in my Audio Unit in a callback > routine, and the host sends the outputs to the audio interface. In Windows > a similar thing happens, but with VST plugins and an ASIO host, which is > either a DAW or a custom ASIO host. I’ve done both. > > > > So what is the best “linux way” to do this? Out-of-process seems high > overhead and not suited for low latency, so I figure I must be > misunderstanding something quite fundamental. > > > > Thanks so much for the help, I really do appreciate it. > > > > - Andy > > > > *From: *Paul Davis <paul(a)linuxaudiosystems.com> > *Date: *Tuesday, January 9, 2018 at 8:22 PM > *To: *Andrew Voelkel <jandyman.voelkel(a)gmail.com> > *Cc: *Benoît Rouits <brouits(a)free.fr>, linux-audio-user < > linux-audio-user(a)lists.linuxaudio.org> > *Subject: *Re: [LAU] How to get started writing a JACK app? (also what > distro for BeagleBone) > > > > In-process JACK clients are a very special case and almost nobody > implements or uses them. They are like plugins for the JACK server, and > that's not really the point of JACK (which was designed to connect distinct > processes). > > Look at the out-of-process ("normal") example(s) instead. > > > > On Tue, Jan 9, 2018 at 9:39 PM, Andrew Voelkel <jandyman.voelkel(a)gmail.com> > wrote: > > Hi and thanks. > > > > So looking at the in-process example, I’m guessing it compiles to a > dynamic library which the server loads? If so, how does the server know the > capabilities of the in-process client. > > > > I’m coming from writing VST plug-ins on Windows or Audio Units on Apple > platforms, in case I sound confused. > > > > I’m also having trouble getting used to the idea of the client being the > plug in, normally I would think the client would be what is called the > “host” on Windows or Apple, and the plug-in would closer to a “server”. But > here the terminology is reversed. Am I understanding correctly? The > “client” in JACK is the plug-in (for in-process use), correct? > > > > Finally, I’d like to get started seeing whether the eco-system works for > low latency with existing apps and components for diving in. Is AVLinux the > way to go, and is there any reason it will not work on BeagleBone? > > > > I’m not a Linux expert in case you can’t already tell! It’s not that I > have zero experience, but sometimes it’s close, depending on context. > > > > But I do know audio, and operating system design, and threading, and SIMD, > and etc. > > > > - Andy > > > > *From: *Linux-audio-user <linux-audio-user-bounces(a)lists.linuxaudio.org> > on behalf of Paul Davis <paul(a)linuxaudiosystems.com> > *Date: *Tuesday, January 9, 2018 at 4:41 PM > *To: *Benoît Rouits <brouits(a)free.fr> > *Cc: *linux-audio-user <linux-audio-user(a)lists.linuxaudio.org> > *Subject: *Re: [LAU] How to get started writing a JACK app? > > > > please. not sourceforge. > > JACK code lives on github ... https://github.com/jackaudio/ > example-clients > > > > On Tue, Jan 9, 2018 at 6:21 PM, Benoît Rouits <brouits(a)free.fr> wrote: > > Hello Andy > > as a starting point, you could look at: > > http://jackit.sourceforge.net/cgi-bin/lxr/http/source/example-clients/ > > This is C client code samples for jack. > > HTH, > Benoît > > Le 09/01/2018 à 16:19, Andrew Voelkel a écrit : > > > > Hi,____ > > > > __ __ > > > > I’m new to this list. I’m thinking of giving low latency real time > > audio in Linux another try after my last unsuccessful attempt a few > > years ago. My goal is to put some of my own DSP code into a hardware > > appliance and use it to process audio signals during music > > rehearsals and performances.____ > > > > __ __ > > > > I think this boils down to getting an appropriate distro, getting > > JACK working in a low latency configuration with a multichannel USB > > interface. And then …____ > > > > __ __ > > > > Writing a JACK app to process the audio. ____ > > > > __ __ > > > > I’ve done some googling and found a lot about _/using/_ JACK, but > > not much about writing a JACK app. ____ > > > > __ __ > > > > Are there any examples or tutorials out there?____ > > > > __ __ > > > > I’m already up to speed on doing C++ cross development with > Eclipse.____ > > > > __ __ > > > > I’ve got a BeagleBone black sitting around here I could use to > > experiment.____ > > > > __ __ > > > > * Andy____ > > > > > > > > > > > _______________________________________________ > > Linux-audio-user mailing list > > Linux-audio-user(a)lists.linuxaudio.org > > https://lists.linuxaudio.org/listinfo/linux-audio-user > > > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user(a)lists.linuxaudio.org > https://lists.linuxaudio.org/listinfo/linux-audio-user > > > > _______________________________________________ Linux-audio-user mailing > list Linux-audio-user(a)lists.linuxaudio.org https://lists.linuxaudio.org/ > listinfo/linux-audio-user > > >

6 years, 3 months

Does jackd sits on top of ALSA ?

by jonetsu

I've been using jackd fro years and will not change. I have a question which is not important at all.. does jackd sits on top of ALSA or besides it ? In other words can a Linux audio system work with only jackd ? If not, what is the responsibility of ALSA in a system using jackd ? Cheers.

6 years, 3 months

Increased single-box JACK performance using multiple servers, summary and status

by Jonathan E. Brickman

It is finally working, and in very repeatable fashion, three "soft" servers feeding to one connecting to real audio hardware. Test mode only so far. Next step is automated startup. Details: https://github.com/jebofponderworthy/MultiJACK/blob/master/README.md -- Jonathan E. Brickman jeb(a)ponderworthy.com (785)233-9977 Hear us at http://ponderworthy.comcom -- CDs and MP3 now available! Music of compassion; fire, and life!!!

6 years, 3 months

Re: [LAU] How to get started writing a JACK app? (also what distro for BeagleBone)

by Benoît Rouits

I'm not an expert, but if you are looking something like AU or VST, maybe you should consider writing an LV2 plugin (most of linux DAWs can host LV2 plugins). An LV2 plugin is a small shared object with a few callbacks to process sound or midi, or controls. They can have a graphical interface too, but this is not mandatory. main entry point url is there : http://lv2plug.in/ Cheers, Benoît Le 10/01/2018 à 05:07, Andrew Voelkel a écrit : > Hi, > > > > Maybe I need to ask a different question. My goal is to stick my real > time processing algorithm in between x number of audio inputs coming > from a USB audio interface, and then send the outputs to y number of > audio outputs on the same USB audio interface. Low latency is important. > Being able to add in other processing from third parties would be nice, > but it isn’t essential. > > > > Is writing a JACK client the right way to do this? If so, what is the > right approach? If not, what is the right way to do this? > > > > On the Apple platform, I do this by writing an Audio Unit, and either > leverage a DAW host application like Logic or the Apple AVAudioEngine to > serve as a host for my processing algorithm. The host gets the inputs > from the audio interface, I process the audio in my Audio Unit in a > callback routine, and the host sends the outputs to the audio interface. > In Windows a similar thing happens, but with VST plugins and an ASIO > host, which is either a DAW or a custom ASIO host. I’ve done both. > > > > So what is the best “linux way” to do this? Out-of-process seems high > overhead and not suited for low latency, so I figure I must be > misunderstanding something quite fundamental. > > > > Thanks so much for the help, I really do appreciate it. > > > > * Andy > > > > *From: *Paul Davis <paul(a)linuxaudiosystems.com> > *Date: *Tuesday, January 9, 2018 at 8:22 PM > *To: *Andrew Voelkel <jandyman.voelkel(a)gmail.com> > *Cc: *Benoît Rouits <brouits(a)free.fr>, linux-audio-user > <linux-audio-user(a)lists.linuxaudio.org> > *Subject: *Re: [LAU] How to get started writing a JACK app? (also what > distro for BeagleBone) > > > > In-process JACK clients are a very special case and almost nobody > implements or uses them. They are like plugins for the JACK server, and > that's not really the point of JACK (which was designed to connect > distinct processes). > > Look at the out-of-process ("normal") example(s) instead. > > > > On Tue, Jan 9, 2018 at 9:39 PM, Andrew Voelkel > <jandyman.voelkel(a)gmail.com <mailto:jandyman.voelkel@gmail.com>> wrote: > > Hi and thanks. > > > > So looking at the in-process example, I’m guessing it compiles to a > dynamic library which the server loads? If so, how does the server > know the capabilities of the in-process client. > > > > I’m coming from writing VST plug-ins on Windows or Audio Units on > Apple platforms, in case I sound confused. > > > > I’m also having trouble getting used to the idea of the client being > the plug in, normally I would think the client would be what is > called the “host” on Windows or Apple, and the plug-in would closer > to a “server”. But here the terminology is reversed. Am I > understanding correctly? The “client” in JACK is the plug-in (for > in-process use), correct? > > > > Finally, I’d like to get started seeing whether the eco-system works > for low latency with existing apps and components for diving in. Is > AVLinux the way to go, and is there any reason it will not work on > BeagleBone? > > > > I’m not a Linux expert in case you can’t already tell! It’s not that > I have zero experience, but sometimes it’s close, depending on context. > > > > But I do know audio, and operating system design, and threading, and > SIMD, and etc. > > > > * Andy > > > > *From: *Linux-audio-user > <linux-audio-user-bounces(a)lists.linuxaudio.org > <mailto:linux-audio-user-bounces@lists.linuxaudio.org>> on behalf of > Paul Davis <paul(a)linuxaudiosystems.com > <mailto:paul@linuxaudiosystems.com>> > *Date: *Tuesday, January 9, 2018 at 4:41 PM > *To: *Benoît Rouits <brouits(a)free.fr <mailto:brouits@free.fr>> > *Cc: *linux-audio-user <linux-audio-user(a)lists.linuxaudio.org > <mailto:linux-audio-user@lists.linuxaudio.org>> > *Subject: *Re: [LAU] How to get started writing a JACK app? > > > > please. not sourceforge. > > JACK code lives on github ... > https://github.com/jackaudio/example-clients > > > > On Tue, Jan 9, 2018 at 6:21 PM, Benoît Rouits <brouits(a)free.fr > <mailto:brouits@free.fr>> wrote: > > Hello Andy > > as a starting point, you could look at: > > http://jackit.sourceforge.net/cgi-bin/lxr/http/source/example-clients/ > > This is C client code samples for jack. > > HTH, > Benoît > > Le 09/01/2018 à 16:19, Andrew Voelkel a écrit : > > > > Hi,____ > > > > __ __ > > > > I’m new to this list. I’m thinking of giving low latency > real time > > audio in Linux another try after my last unsuccessful > attempt a few > > years ago. My goal is to put some of my own DSP code into > a hardware > > appliance and use it to process audio signals during music > > rehearsals and performances.____ > > > > __ __ > > > > I think this boils down to getting an appropriate distro, > getting > > JACK working in a low latency configuration with a > multichannel USB > > interface. And then …____ > > > > __ __ > > > > Writing a JACK app to process the audio. ____ > > > > __ __ > > > > I’ve done some googling and found a lot about _/using/_ > JACK, but > > not much about writing a JACK app. ____ > > > > __ __ > > > > Are there any examples or tutorials out there?____ > > > > __ __ > > > > I’m already up to speed on doing C++ cross development > with Eclipse.____ > > > > __ __ > > > > I’ve got a BeagleBone black sitting around here I could use to > > experiment.____ > > > > __ __ > > > > * Andy____ > > > > > > > > > > > _______________________________________________ > > Linux-audio-user mailing list > > Linux-audio-user(a)lists.linuxaudio.org > <mailto:Linux-audio-user@lists.linuxaudio.org> > > https://lists.linuxaudio.org/listinfo/linux-audio-user > > > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user(a)lists.linuxaudio.org > <mailto:Linux-audio-user@lists.linuxaudio.org> > https://lists.linuxaudio.org/listinfo/linux-audio-user > > > > _______________________________________________ Linux-audio-user > mailing list Linux-audio-user(a)lists.linuxaudio.org > <mailto:Linux-audio-user@lists.linuxaudio.org> > https://lists.linuxaudio.org/listinfo/linux-audio-user > > >

6 years, 3 months

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