Athanasios Silis | 12 Oct 23:42 2015

[LAU] send a midi CC signal to my midi controller from bash

hi all
I have a BCR2000 and I want to init some controllers to some values.
init is done by a bash script so I would like to set the value in a bash script and send it out to the BCR2000.

the controller shows up on jack , under a2j , but i am not sure which program - if any - exists out there that can send this midi signals.

thank you in advance for your help!
Linux-audio-user mailing list
Dave Phillips | 12 Oct 00:30 2015

[LAU] Cabbagenic - More tracks from The Swinging Sounds Of Cabbage !

Greetings, fellow travellers,

Incidental music for that rare occasion.

Descriptive warnings/pointers to inner meanings :

Part 1. Sunday morning, waking/dreaming/waking and dreaming again.

Part 2. Sebkha-Chott patiently teach GWAR how to tune their instruments 
and play simple melodies correctly.

Part 3. An imaginary fretless bass dreams of 50s Darmstadt stardom, then 
it all sadly fades away.

All sounds made by VST plugins created with Rory Walsh's Cabbage. All 
instrument/processor designs by Iain McCurdy.

One non-Cabbage plugin was used, Martin Eastwood's MVerb, from falkTX's 
DISTRHO-Extra code base.

Sequenced and rendered in Bitwig 1.2.0 (beta).


Ralf Mardorf | 10 Oct 10:57 2015

[LAU] Assumed you want to remove pulseaudio - Was: Diagnosing JACK

It's off-topic for the original thread and might confuse the OP of this
thread, so I opened a new one.

If somebody wants to get rid of pulseaudio, without recompiling,
without dummy packages, then it doesn't harm to test if software really
needs pulseaudio.

On Sat, 10 Oct 2015 05:32:43 +0000 (UTC), fred wrote:
> De : Ralf, Envoyé le : Samedi 10 octobre 2015 1h39
>>For me it's easier to just install one sound server instead of two or
>>more sound servers. I don't need to comment out something or to add
>>something to an app. For most use cases it's simpler to use one sound
> That's because you have the technical ability to do it Ralf!>> For
> most of "simple users" installing distros "as it comes", you just
> finish with 'killall pulseaudio' before starting Jack,>> and it
> works right :)

My Ubuntu install has zero dependencies to pulseaudio. Since I test a
lot with my Arch Linux install I need a dummy package to fulfil hard
dependencies for cinnamon and vice. There are 4 optional dependencies.

Even if I would like to use Cinnamon, I couldn't, because it requires
an absurd fast graphics. Using the "radeon" driver Google Earth is fast
as lightning, but Cinnamon is nearly unresponsive. Vice is an emulator I
just planed to test, but I never did, IOW assumed recompiling without
pulseaudio or just installing a dummy package, as I did, wouldn't work,
I could simply remove this software [1].

If users anyway suspend/kill pulseaudio and dummy packages work too,
then why is it a hard dependency for some software?
Why not using simply software that doesn't require pulseaudio?

I'm using openbox, but at least JWM, Xfce4 and Mate are installed too
and seemingly non of them requires pulseaudio.

If you're using a deb based distro, make a dry-run to test, if there
really is needed software that depends on pulseaudio [2].

IMO Ubuntu and Debian aren't distro for power-users or geeks only.

[rocketmouse <at> archlinux lib]$ cd /bin/;du -sh
1.2G	.
[rocketmouse <at> archlinux bin]$ cd /lib/;sudo du -sh
5.2G	.
[rocketmouse <at> archlinux lib]$ sudo pacman -R pulseaudio pulseaudio-alsa
vice cinnamon-settings-daemon cinnamon-control-center cinnamon checking
dependencies... :: fluidsynth optionally requires pulseaudio:
PulseAudio sound support :: phonon-qt4 optionally requires pulseaudio:
PulseAudio support :: phonon-qt5 optionally requires pulseaudio:
PulseAudio support :: speech-dispatcher optionally requires pulseaudio:
PulseAudio support

Packages (6) cinnamon-2.6.13-3  cinnamon-control-center-2.6.0-1
cinnamon-settings-daemon-2.6.3-1 pulseaudio-2013.08.18-1
pulseaudio-alsa-2-3  vice-2.4-7

Total Removed Size:  51.37 MiB

:: Do you want to remove these packages? [Y/n] n
[rocketmouse <at> archlinux lib]$ grep Driver /etc/X11/xorg.conf | grep -v
"#" Driver      "radeon"

[root <at> moonstudio ~]# apt-get purge --dry-run pulseaudio
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Purg pulseaudio [2015:09-06-moonstudio]
Linux-audio-user mailing list
Linux-audio-user <at>
Rui Nuno Capela | 9 Oct 19:44 2015

[LAU] [ANN] Qtractor 0.7.1 - The Meson Dope beta release


   Here's to all southerners for whom the so called Summer'15 didn't 
made much sense...

   Beg your pardon yet and again, but it's that time of year when 
grapefruit is about ripening, pretty fast and maybe late, at least on 
the northern hemisphere. No worries: harvesting has already been carried 
away. So it's your call now, wether it makes for ugly bad wine or, 
pretty good vinegar...

   "Quickly, bring me a beaker of wine so that I may wet my mind and say 
something clever." --Aristophanes

never mind,

   Qtractor 0.7.1 (meson dope beta) is released!

   Now, for the clueless:

   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.

   And for the ones who can aptly tell a TL;DR apart from a hangover:

   Besides the incidental bug-fixes and proverbial business-as-usual 
stance for this dot release, the most probable and hopefully significant 
news about it, is that this will the last to build against Qt4 by 
default. The time has come to move on up to Qt5. Remember that a Qt5 
build is and has been possible already for ages now but somewhat 
relegated on a subpar status due to the once lack of support for all 
non-Qt5 LV2 plug-ins GUIs out there. Not anymore! Starting from this 
very release onwards there's this so called <em>native</em> LV2 GTK2 and 
X11 UI support on Qt5. Also thriving, drobilla's libsuil is being 
updated to par just that as well. So things are all aligning up nigh.

   A special note to the voluntary packager: if you choose, for any 
reason you may find commendable, to build, package and distribute a Qt5 
build (via ./configure --enable-qt5 ...) please be sure that every LV2 
plug-ins around that take Qt as its UI framework are also build, 
packaged and distributed on the same premises, otherwise they might just 
fail and crash Qtractor [1] on show. Among those are of course the one 
comprised by the 'Vee One Suite', namely synthv1 [9], samplv1 [10] and 
drumkv1 [11], of course.

   Also as a(nother) side note: It has been for quite some time there's 
an alternate [7] repository which is kept in sync with the one [8]. However, this doesn't mean that the Qtractor [1] project 
is about to migrate to brand new hosting whatsoever: the original 
upstream source code repository is, will be, as ever was, always kept 
somewhere else still in this world and universe. It's a Git [12] world 
out nowadays and as the mottos says, --everything-is-local, 
--distributed-is-the-new-centralized ;)



Project page:


- source tarball:

- source package (openSUSE 13.2):

- binary packages (openSUSE 13.2):

- wiki (help wanted!):

Weblog (upstream support):

   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.

- Fixed an ages old MIDI track/channel instrument mapping (bank, 
program) issue that prevented normal all-shut-up messages from being 
sent to MIDI output buses/ports on playback stop.
- Messages standard output capture has been improved again, now in both 
ways a non-blocking pipe may get.
- Fixed port on MIDI 14-bit controllers input caching.
- Fixed false value readings on the MIDI clip editor (aka. piano-roll) 
tool-tips, when dragging a note velocity or controller value outside the 
acceptable nominal range (eg. 0-127).
- Added LV2_BUF_SIZE__nominalBlockLength option support (patch by falktx 
aka. Filipe Coelho, thanks).
- Fixed wrong initial tempo/time-signature display when session is 
loaded from command line.
- LV2 plug-in UI GTK2 and X11 in Qt5 host native support added.
- Transport/Auto Backward feature now honoring (auto return) to same 
current location precedence as Transport/Backward.
- Single/unique application instance control adapted to Qt5/X11 (cf. 
configure --enable-xunique).
- MIDI Tools/Transpose, Resize duration display format (frames, time or 
BBT) have been fixed.
- Build fix for Qt5.5 (patch by KaOS, thanks).
- MIDI Tools/Quantize et al. are tentatively being corrected to take 
event times as relative to THE beginning of session, instead of MIDI 
clip start location.


[1]  Qtractor - An audio/MIDI multi-track sequencer

[2]  Qt framework, C++ class library and tools for
      cross-platform application and UI development

[3]  JACK Audio Connection Kit

[4]  ALSA, Advanced Linux Sound Architecture

[5]  Linux Audio consortium of libre software for audio-related work

[6]  GPL - GNU General Public License

[7]  Qtractor Git repository on

[8]  Qtractor Git repository on

[9]  synthv1 - an old-school polyphonic synthesizer

[10] samplv1 - an old-school polyphonic sampler

[11] drumkv1 - an old-school drum-kit sampler

[12] Git distributed version control system

See also:

Enjoy && have fun.

rncbc aka. Rui Nuno Capela
Dave Phillips | 9 Oct 13:45 2015

[LAU] PreparationP


Fun with prepared piano samples :

Sugar-free, low cholesterol, no trans-fats, non-GMO ingredients, 
produced without dyes, preservatives, or additives.

"Never eat what you can't pronounce." - Smallie Biggs, (1973-1732, 
roughly contemporaneous with PDQ Bach.)


d(your ad here)p
worik | 9 Oct 08:05 2015

[LAU] Diagnosing JACK


I am having trouble with JACK and I have no idea how to start diagnosing
my problems.

I am starting it with qjackctl. as I have been doing for ages using a
M-AUDIO USB interface.

I get no sound through it at all today, neither input nor output.  I
have been using this setup for over a year with no problems.  Befire
that I had constant problems that just went away.

Now they are back.

I am at my wits end, I can not find any logs where JACK is putting its
output, which would be a start.

I have had "pulseaudio" apear in the connections window, I was not
seeing that when the system was working.

Where do I start?  For a start where does JACK put its logs?

I have the correct device selected in the setup tab



Why is the legal status of chardonnay different to that of cannabis? 
                  root@... 021-1680650, (03) 4821804
                          Aotearoa (New Zealand)
                             I voted for love
James Greenlee | 8 Oct 00:56 2015

[LAU] JACK switcher app?

I'm looking for an audio switching application based around JACK.

Ideally I want a scheduler that will connect a JACK input to a specific JACK output at specific times during
the day.  Bonus points for HTTP interface for the scheduler.

Anybody know of anything like that?


Ralf Mardorf | 5 Oct 20:40 2015

Re: [LAU] Weltanschauung - The totally useless debate about purported 'natural' tunings [WAS]: Re: "droning" project: 249-257

PS: Please continue at,

I already forwarder my message to this list.

Michael Jarosch | 5 Oct 11:54 2015

[LAU] Cross-Plattform VDE 0701/0702-Tester

Hi there!

This is a somewhat special question which has not so much to do with
linux-audio stuff - but as there are quite a few people here dealing
with electrics / electronics and some of them even earn their money as
event technicians you might get in touch with special measurement
equipment like a VDE 0701/0702-tester.

As you might know, most manufacturers of those devices offer software
to ease the administration of your testing pool, but most of them still
life in the 90s and make them windows only.

So here I am, asking you if you are using or knowing a VDE 0701/0702
-testing device manufacturer that is modern enough to master the (not
so secret) secrets of cross-platform software engineering or opened
their devices and protocols in that way, that I can easily access them
with linux / open source tools.

worik | 5 Oct 01:20 2015

[LAU] Getting started editing and playing a score


I would like to get started editing a simple score and producing some
sound from it.

I have tried rosegarden recently but I can get no sound out of it.  It
is far more than I require, as my confidence increases perhaps it is
what I will need but I simply cannot tell at this point.

In the past I have used csound, it has a less useful interface (suits
me) and is the closest to what I want but I need to get a colleague
entering a score and a text editor will not do.

I am at my wits end, what I might need is a beginners guide for
rosegarden, or better still a simpler programme, or virtual keyboard

I am completely swamped by all the options that I have and hence am a
bit paralysed.  I can tell that whatever I choose will require a big
investment in time to learn but I cannot be sure that it is worth the
investment.  And being unable to get any sound at all is very demoralising.


PS I have been doing a lot of sound recording and editing with Linux and
a M-Audio interface (usually) and a PreSonus AudioBox 1818VSL when I
have to mostly into audacity.  When I am absolutely forced to (when
using > 2 tracks where Audacity cannot cope yet) I use audacious.  I
find audacious endlessly irritating for the same problems I outline
above, so many options, so many knobs, where do I start?  But audacity
pretty much just worked.


Why is the legal status of chardonnay different to that of cannabis? 
                  root@... 021-1680650, (03) 4821804
                          Aotearoa (New Zealand)
                             I voted for love
ansible | 4 Oct 20:57 2015

[LAU] make alsa device hw:1,0 be hw:0,0 somehow

I compiled supercollider to play through portaudio rather than jack, as it
usually does, in an attempt to reduce latency and hassle.  It works for
audio device hw:0,0, but it doesn't work for hw:1,0.  My problem is that on
my device hw:0,0 has horrible latency - 70ms - while hw:1,0 has 9ms latency,
much better.  

So what I'd like to do is reorder the audio devices, or disable the onboard
audio, and have my current hw:1,0 be the hw:0,0 device.  Hopefully then
supercollider will work with it and I'll have those coveted low latency
numbers.  This is on arch linux on a bananapi armv7 computer.  

So here's the output from aplay -l:

[bananapi <at> lemaker ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sunxicodec [sunxi-CODEC], device 0: M1 PCM [sunxi PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Pro [Sound Blaster X-Fi Go! Pro], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[bananapi <at> lemaker ~]$ 

According to the [alsa wiki][1], I should be able to reorder the devices
using a .conf file. See 'set the default sound card'.  It gives the example
of this:


options snd_mia index=0
options snd_hda_intel index=1

Ok so I made a file like that, but I only know the name of the usb driver,
not the onboard sound driver.  lsmod reveals the following:

[bananapi <at> lemaker ~]$ lsmod
Module                  Size  Used by
snd_usb_audio          96225  0
snd_hwdep               5757  1 snd_usb_audio
snd_usbmidi_lib        18033  1 snd_usb_audio
cdc_acm                20518  0
spidev                  6217  0
spi_sun7i              17802  0
sunxi_cedar_mod         9808  0
mali_drm                2608  0
drm                   209226  1 mali_drm
mali                  111427  0
disp_ump                 861  0
ump                    52415  2 mali,disp_ump
ap6210                584133  0
ip_tables              12937  0
x_tables               17443  1 ip_tables

If I do "modprobe -r snd_usb_audio", then snd_hwdep and snd_usbmidi_lib both
disappear too, so they are all for the same device I think.  That leaves
nothing for the driver name for the onboard audio.  

The alsa wiki says that the driver names should be in "cat
/proc/asound/modules" but I don't have that directory on my system.  

So anyway I made an alsa-base.conf file as directed, which looks like this:

[bananapi <at> lemaker ~]$ cat /etc/modprobe.d/alsa-base.conf 
options snd_usb_audio index=0
options sunxicodec index=1
[bananapi <at> lemaker ~]$ 

After creating that file and rebooting aplay just returns this.  

[bananapi <at> lemaker ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sunxicodec [sunxi-CODEC], device 0: M1 PCM [sunxi PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[bananapi <at> lemaker ~]$ 

So this alsa-base.conf has the effect of making only the onboard audio
available instead of reordering.  I most likely have the 'sunxicodec' name
wrong for the onboard audio, I'm just guessing at that, and have no idea
what the driver name for that is, if there even is one.  I'm kind of
suspecting the audio device is part of a monolithic driver for the whole
system-on-chip, is that possible?  


View this message in context:
Sent from the linux-audio-user mailing list archive at