QMidiArp 0.5.2 has just seen the light of the day. It brings mainly
two improvements. One is a comeback, that of tempo changes on the fly,
and that now includes also tempo changes of a potential Jack Transport
master. Also the Jack Transport starting position is finally taken into
account, so that QMidiArp should be in sync also when starting the
transport master not at zero.
The second one is Non Session Manager support, mainly thanks to the work done by Roy Vegard Ovesen!
Note that for compiling in NSM support you will now need liblo as dependency.
Enjoy, and enjoy LAC in Graz this year
QMidiArp is an advanced MIDI arpeggiator, programmable step sequencer and LFO.
Everything is on
o Tempo changes are again possible while running, both manually or by
a Jack Transport Master
o Jack Transport position is now taken into account when starting,
QMidiArp used to start always at zero
o Muting and sequencer parameter changes can be deferred to pattern
end using a new toolbutton
o Modules in the Global Storage window have mute/defer buttons
o Global Storage location switches can be set to affect only the pattern
o Non Session Manager support with "switch" capability (thanks to
Roy Vegard Ovesen)
o NSM support requires liblo development headers (liblo-dev package)
> Message: 17
> Date: Mon, 30 Jun 2014 15:32:37 +0000
> From: Fons Adriaensen <fons(a)linuxaudio.org>
> To: linux-audio-dev(a)lists.linuxaudio.org
> Subject: Re: [LAD] Open Source to be or not to be?
> Message-ID: <20140630153237.GB29991(a)linuxaudio.org>
> Content-Type: text/plain; charset=us-ascii
> On Mon, Jun 30, 2014 at 04:02:20PM +0200, hermann meyer wrote:
>> PLease, Fons, if you found more Bugs, or have any issue with the way
>> we implement parts of your work, let me know. I'm all open !
> The four T60 controls are supposed to be log as well.
> And please get rid of that silly little slider named
> 'Freq X'.
> Another matter: starting guitarix without Jack running produces
> an empty black 'Jack Starter' window. No matter what I do next
> will crash X11.
> A world of exhaustive, reliable metadata would be an utopia.
> It's also a pipe-dream, founded on self-delusion, nerd hubris
> and hysterically inflated market opportunities. (Cory Doctorow)
Interesting discussion... ((-;
It would be great if the corrected zita-rev1 Faust version goes back in the Faust distribution at some point….
Fons, you know what? the Faust zita-rev1 version (still old one of course..) now even runs in the web, automagically compiled in asm.js (http://asmjs.org) using latest faust2 git version and running at acceptable speed in recent browsers like Firefox or Chrome (still some issues here…) :
Is it interesting? a way to promote open-source DSP code? who knows...
(Here is an unusual mail trying to describe as entertainingly as
possible what it's like to set up a modular production environment in
GNU/Linux. I owe the greatest of respect to anyone who've made the
softwares mentioned below and their work do not misunderstand a joke for
a blunt critic. )
You haven't heard much from me lately, and I'm sorry for that. For one
year and a half I've been sitting in front of my minimal -yet fairly
high endish - music production set up doing nothing but programming.
Those expensive things were only used to playback cd and digital files...
... you know what that means :
I was becoming an audiophile.
Holly horse poop, I can't beleive I said that... but it's true.
Few weeks ago, realizing this dreadful fact- I decided to start a rehab
: let's fire up the preamp and let's record some stuffs. Just to prove
the world I'm not just another bragging gear slut (hopefully).
Of course, just to make things harder I decided not to use the
full-featured highly expected (and probably amazing) Ardour 3. Why not ?
Because I've suffered 8 years of (gnu's not)Unix propaganda and now I
praise "modularity" above anything else.
Mh, and I guess 27 years of Legos(tm) didn't help neither (Don't judge
me, Technics are a great prototyping tool. ... . That's the best excuse
Lately, thanks to nedko (gladish), male (non-suite), drobilla (patchage,
ingen), falktx (Carla) (I always have to check the letters order for
this one nick :/) and few others,goal my has become -somehow- tangible.
Part one : THE SETUP
When you start a big music project with high expectations with GNU/linux
you need two things :
1) Make sure not to have a deadline
2) Make sure you are fully relaxed
Cause, you know how it is : those softwares are all quite young and only
used by few people. Therefore, "few people" means very few bug reports.
And of course those softs are made by volunteers who can only solve
them when they have enough time. Considering all this, it's already
great everything works !
Having few bugs every once in a while in a software is no big deal...
But the thing with modular audio, by definition, is that you're gonna
use dozens of them. At once.
And bugs DO stack.
But I'm rushing a bit, we're not there yet, cause at this point of the
story I haven't picked my softwares already (except for the non-suite).
I don't have any effects nor midi anything : I need to gather some more
stuffs to work with. And I must say I felt a bit like Indiana Johns
having to gather some pieces of a mysterious puzzle : "Your six strings
shall sound heavenly and You synths shall have many melodies. and you
will have to travel the Internet to find what you need."
Ok, the guitar part is an easy one : guitarix. It's just amazing. Let's
use it... and ! Oh gosh ! It's a trap ! There's no way to recall a
preset, it not patched with NSM... quick ! Use CLI, they MUST have a
"import" option ! Oh crap NO ! They don't !
I thought my quest would be easy but no. Instead of being able to pick
guitarix, I found a new quest : "use the LV2 version".
No big deal, let's just move to another place. Carla. it usually works
fine... but...gosh all my plugins are here except the amp simulator...
what the heck ?
Ingen then... erf... no, for some reasons this plugin doesn't make a
sound. Damn. Back to Carla... with another quest :
"You shall not use the Stable version. Use the git version". It's gonna
be harder than I thought.
Building is usually a piece of cake... but not this one time.
Eventually, in a last desperate attempt, I tried one more build, and
succeed.... Until QT5 -my trusted friend for years- suddenly decides to
betray me by placing booby traps all over the place to make sure I'm
not able to add any effect. Luckily, the scientist in the team -Falktx-
has been able to diffuse those.
Finally ! Now I have a guitarix preset I can save and load with NSM.
Everything's set for the guitar. It's tome to move on to our glorious
quest for MIDI.
This quest was such a weird experience. I went to the vaste land of
Rosegarden, where the GUI almost made me blind and mad. I tried the
purity of a non-sequencer until it exploded right in my face. I went
to an oddly useless 1 bar non-chromatic sequencer...
Ok. It's gonna Seq24 then. It's not perfect, but I can use it.... Let's
just call the maintainer to fix the few problems... or not. Nobody's
actually taking care of this software.
Screw it. I'll use it anyway.
It's been a week already, and most of the musicians in my party have
given up for an easier world where you can buy peace.
I've been able to make some sounds and that's what keeps me going... I
don't know how long this will take, but I'll gather all the pieces of
this modular music machine.
Eventually with the help of the LAD's scientist, it'll work properly.
Let's keep faith.
P.S. : As tedious as it was, I'm still thrilled by the potential of a
well integrated modular audio software suite. I must say I'm even more
exited when I see what's *already* possible today. Therefore I'd like to
make a call for a working group around this question cause it's really
(*really*) close to something great. I believe that a nice dialog
between users trying to setup real production environments and coders
can quickly bring out a kick-ass suite that can bring linux audio to the
P.P.S : all the best, and thanks for reading.
I'm sure there must be users out there who are familiar with web stuff
and are burning to help their favourite inter-application audio
Step up, please.
PS: There is also a semi-complete move to GH-pages. If your're familiar
with github, you could be the ideal volunteer. ;)
----- Forwarded message from Paul Davis <paul(a)linuxaudiosystems.com> -----
Date: Fri, 30 May 2014 11:56:02 -0400
From: Paul Davis <paul(a)linuxaudiosystems.com>
To: JACK <jack-devel(a)lists.jackaudio.org>
Subject: [Jack-Devel] jackaudio.org website shut down due to hacking
The malicious conscience-free leeches who push pharmaceutical spam managed
to hack into jackaudio.org in a very deep way. They had full access to
everything including the ability to fiddle with MySQL tables (some of
them). I don't consider any part of the Drupal site safe, so I have shut it
down and replaced it with a single static index.html file.
The source tarballs for JACK1 were uncorrupted (probably JACK2 also -
waiting for confirmation from Stephane on this), and I have put up a new
link to the most recent. I also referenced github for the source code
repository and issue tracker.
As someone said on IRC today
" It's a shame the lead dev has to waste his time coding, answering user
questions AND fixing drupal backdoors "
If someone else wants to volunteer to resurrect the roughly 60 pages of
content that were at jackaudio.org (and realistically, it is probably more
like 20 of real stuff that is needed), get in touch. I can give you full
access to everything you will need.
Jack-Devel mailing list
----- End forwarded message -----
mail: adi(a)thur.de http://adi.thur.de PGP/GPG: key via keyserver
The video recordings of the LAC'14 presentations have just been uploaded
to the conference website and are now directly linked from the archive:
There are still a three videos missing and the workshop videos are also
yet to come. Currently they are also only available as vp8/vorbis/webm
(sorry IE and Safari users). But since it has been quite a while
already, we decided to not hold back the release of these already
finished videos any further.
Once the collection is complete, we will provide a .torrent. Meanwhile,
for those who prefer to download the videos incrementally, they are
accessible via rsync://linuxaudio.org/ .
Many thanks for Frank and Moritz to get those done in really outstanding
quality this year. Kudos to the complete stream-team.
robin - for the LAC'14 team
 example to get the 720p versions:
rsync -Pa --exclude "*360p.webm" \
Calling all ChucK’ers, SuperColliders, Max and PureData patchers,
CSounders, Fluxites, Overtoners, and all other tongues of creative
coders. We welcome you to attend the fifth edition of the Creative Music
Coding lab at STEIM.
The CMC lab is an autonomous zone to try out sonic experiments as a
group. And an opportunity to leverage the expertise of the group in
realizing new artistic tools and processes through the medium of code.
Many of the founding members of the group are indeed experts in their
favorite languages, but we come from all technical levels of proficiency
and enjoy helping one-another out.
DATE: Tuesday, 24 June 2014
LOCATION: STEIM Concert Space, Utrechtsedwarsstraat 134 Amsterdam
What ARE the goals for the lab?
* a place for creative music coders to show work in progress, regardless
of programming language or platform
* a place to discuss and question techniques with fellow computer musicians
* an informal stage for playing with others, livecoding sessions,
jamming, and other fun experiments
* an opportunity to meet like-minded artists, share talents, and start
* an opportunity to be exposed to new languages and improve
* a way to discover lesser known and emerging creative programming paradigms
* a place to to discuss interconnections between programming environments
* an environment for discussions on cultural contexts surrounding coding
in the arts
We encourage members of the group to use this as a platform for
exploring ways in which we might be able to create and play together.
Proposals for creative group investigations of hardware, software, and
coding as process are welcome.
As always, entry is free, tea and coffee will be provided.
While putting the finishing touches on zita-njbridge and doing a lot
of testing I stumbled on this strange behaviour of jack's frame time.
Let F(i) be the frame time corresponding to the start of period 'i',
and U(i) the corresponding microseconds time.
If jack for whatever reason skips some periods, then one would
expect the difference of F(i) and U(i) to be consistent. They
are in some but not in all cases.
This is the output from a test. When the frame time makes an
unexpected jump, it prints the difference of F, the difference
in U converted to frames, and the difference of these two.
Period size is 256 frames.
dframes = 768 769.0 1.0
dframes = 1024 1322.8 298.8
dframes = 1024 1024.7 0.7
dframes = 768 1067.3 299.3
dframes = 1024 1023.7 -0.3
dframes = 768 1068.5 300.5
dframes = 768 769.2 1.2
dframes = 768 1067.3 299.3
dframes = 1024 1023.9 -0.1
dframes = 1024 1323.1 299.1
dframes = 768 768.2 0.2
dframes = 768 1066.7 298.7
The cases where F and U match are due to starting another client
(designed to be 'heavy'), those where F and U do not match occur
when the same client is terminated (using ^C). The error for
those is consistently a full period plus around 4333 frames.
So it seems that the frame time is not a reliable method to
determine how many frames have been lost.
Using jack1, 0.124.1
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
GRAME is happy to announce the official release of FaustLive.
FaustLive is an advanced self-contained prototyping environment for the Faust programming language with an ultra-short edit-compile-run cycle. Thanks to its fully embedded compilation chain, FaustLive is simple to install and doesn't require any external compiler, development toolchain or SDK to run.
FaustLive is the ideal tool for fast prototyping. Faust programs can be compiled and run on the fly by simple drag and drop. They can even be edited and recompiled while running without sound interruption or Jack disconnection.
1) Dynamic Compilation :
On FaustLive’s windows you can drop your Faust code as a file, a string or a url. The code will be dynamically compiled and executed.
You can then choose to edit your code. It will be opened in the default editor for .dsp files (FOLLOW THE README TO CONFIGURE FILE ASSOCIATION). The application will be automatically recompiled, every time you save your document.
A crossfade is calculated between two relaying applications in a window to avoid brutal sound interruptions.
2) Audio Drivers :
Depending on your Operation System, you will have different drivers available:
On OSX : Coreaudio, Jack and NetJack
On Linux : Jack and NetJack
On Windows : Portaudio
You can then dynamically switch from one to another in FaustLive’s preferences.
3) Export Your DSP :
Exporting your DSP as plugins is easy, thanks to FaustWeb, compilation service. In FaustLive’s export menu, you can find every platform and architecture that Faust can target. As you choose your target, your code is sent to FaustWeb and you receive the requested binary in exchange.
4) Save Snapshots :
If you create a configuration you like, you can save it as a Snapshot. The state of FaustLive will be saved (running applications, Jack connections, interface parameters, …).
Later on, you will be able to whether :
- recall the snapshot : closing any running application to restore the saved state
- import the snapshot : adding the saved state to the current state
5) Remote Control Interfaces (only on Linux and OSX for now) :
In the Windows Option toolBar, you can open a UDP port for OSC control or a TCP port for HTTP control. Moreover, the HTLM interface can be accessed through a QrCode that you can create from «View QrCode » in the menu « Window ».
Sarah Denoux and Stéphane Letz