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)
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
Still recovering from the LAC2014 trip but already with news, here’s the link to our new website (including english version)
The video that was shown at the MOD presentation is right in the frontpage.
Even better, the plugin library can now be navigated in the same way as in the MODs interface. On top of it, there’s a dashboard section where visitors can try the interface without audio.
Hope you all enjoy.
The FFADO project (www.ffado.org) is pleased to announce the release of
FFADO 2.2, the userspace framework supporting Firewire audio interfaces
under Linux. While the focus of this version has been bug fixes and
improvements to existing drivers, support for some additional devices has
FFADO is brought to you thanks to the work of Daniel Wagner, Pieter Palmers,
Philippe Carriere, Adrian Knoth, Arnold Krille, Takashi Sakamoto, Jonathan
Woithe and users who have tested FFADO against their devices, provided
patches and given suggestions.
Changes and additions in FFADO 2.2:
* Many bugs fixed
* Mixer, router and monitor support for Saffire Pro 14
* Mixer and router support for Presonus Firestudio Tube, Presonus Firestudio
Project, and M-Audio Profire 2626
* Support Echo Audio AudioFire12 with firmware versions 5.0 and later
(addresses ticket 360)
* Echo Audio device mixer additions:
- hide SPDIF mode switch on AudioFire12
- digital interface switch on AudioFire8 and Pre8
- phantom power switch for AudioFire4 (addresses ticket 364)
- playback routing for AudioFire2/4 (addresses ticket 335)
* Presonus device mixer additions:
- better support the FP10 (formerly known as the Firepod)
- implement support for the Firebox and Inspire1394
* M-Audio mixer additions:
- improve support for the Ozonic
- add support for Firewire Solo (ticket 336), Audiophile, 410,
1814 and ProjectMix I/O
* Device-specific mixer for Yamaha GO44 and GO46 interfaces added
* RME Fireface 400/800 improvements:
- mixer and device settings can now be saved to and restored from device
- clock source selection made more consistent
* DICE EAP / RME Matrix mixer enhancements:
- "per output" view with mono/stereo control
- saving of mixer settings to file
- more consistent cooperation with jackd when sample rate is changed
* Audio streaming support added or refined for additional MOTU interfaces:
- Traveller mk 3
- Ultralite mk 3
- Ultralite hybrid (using firewire interface only)
* Saffire Pro 40 at 96 kHz fails to start most of the time (ticket 326)
* Saffire Pro 24 and Pro 40 MIDI problems (tickets 372 and 375)
* Saffire Pro 24 and Pro 40 lack an ADAT/SPDIF switch
* Only mixer control is supported on M-Audio 1814 and M-Audio, ProjectMix
* M-Audio Audiophile, 410 and 1814 require startup workaround. See
* M-Audio Audiophile, 410 and 1814 will only work with FFADO when loaded
with the latest firmware
I just discovered openframeworks
And it almost looks too good to be true.
For example, have you seen this?:
Why is ofx not so prolific in lad land? I searched the lad mailing list and found just a handful of mentions over the years.
Who's using it?
Can you recommend it?
Would you have used it if it was available at the start of your project?
6211 GZ Maastricht
Does anyone here know why I am seeing this error while loading a kernel
Unknown symbol __stack_chk_guard (err 0)
Unknown symbol __stack_chk_fail (err 0)
I can't find anything online that explains the cause of the error in
relation to loading kernel modules.
Boost Hardware Ltd
As well as the jack ring buffer, I've looked at several others now, and their
example code. The most significant thing that seems to be different about them
(from a usage point of view) is the way they handle overflows. However, if the
buffer size is defined as an exact multiple of the data type/structure and only
complete structures are pushed or popped, would I be right in thinking that you
would only need to check on an all/none basis?
Have I missed something that could cause a partial data transfer?
Will J Godfrey
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
I notice that I cannot help you without enough logs with which I can
realize what happens.
At lease, 'verbose' options for aplay/arecord, '#' nodes in
/proc/asound/cardX and dmesg.
Additionally, would you please add 'LANG=C' when you get output from
I cannot read Spanish language...
> hi, it does not work.
Try in following steps:
1. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16
(I expected you receive 'Available formats' output)
2. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (here the format,
(I expected you receive 'rate is not accurate' output)
3. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (the same above) -r
(I expected it will run correctly.)
I hope you to do these test when killing pulseaudio. The way is here:
i already have a ladspa-plugin that process my audio data. this works fine
without any problems.
Due to an adaption of the functionality of my system, i want to add a
function that determines if the system works properly. This function should
send an audio signal, that is recorded afterwards. And this should also
work while no application (aplay, skype etc.) uses alsa.
Due to this I want to know if it's possible to use a plugin or an other
virtual device that "keeps the floor".
2014-05-20 12:59 GMT+02:00 Martin Lohberger <elektm.alsa(a)gmail.com>:
> i already have a ladspa-plugin that process my audio data. this works fine
> without any problems.
> Due to an adaption of the functionality of my system, i want to add a
> function that determines if the system works properly. This function should
> send an audio signal, that is recorded afterwards. And this should also
> work while no application (aplay, skype etc.) uses alsa.
> Due to this I want to know if it's possible to use a plugin or an other
> virtual device that "keeps the floor".
> 2014-05-20 12:07 GMT+02:00 Fons Adriaensen <fons(a)linuxaudio.org>:
> On Tue, May 20, 2014 at 10:59:46AM +0200, Martin Lohberger wrote:
>> > Does somebody of you have experience with ALSA-Devices that get never
>> > closed?
>> > I want to run a LADSPA-Plugin all the time, even if the application
>> > is not running.
>> Or float in the air if the floor below your feet is
>> taken away ?
>> > Does sombody have an idea how to solve this problem?
>> A plugin, by definition, needs to be plugged into something else.
>> What is it supposed to do without 'the application above' ?
>> If you want an alsa device which includes a plugin this can
>> probably be done using an ~/.asoundrc.
>> 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)