Awe!
Times they are a-changing although Bob Dylan has no D-Business here. The
old and cutie gooey for JACK just got one turn around the verge of
bit-rotting. This time it brings full JACK D-Bus support, or almost. It
also adds D-Bus access for most GUI actions which some might find pretty
handy for keyboard shortcut binding from your desktop environment of
choice. However, if babies health is your top concern you can just turn
this D-Bus thing off and play with the old times ;) Ahem...
QjackCtl 0.3.6 is now released!
More details in the change-log, below.
Website:
http://qjackctl.sourceforge.net
Project page:
http://sourceforge.net/projects/qjackctl
Downloads:
- source tarball:
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.6.tar.gz
- source package (openSUSE 11.2):
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.6-2.rncbc.suse112.sr…
- binary packages (openSUSE 11.2):
http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.6-2.rncbc.suse112.i5…http://downloads.sourceforge.net/qjackctl/qjackctl-0.3.6-2.rncbc.suse112.x8…
- binary packages (Ubuntu 8.04):
http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.6-1.rncbc.ubuntu804_…http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.6-1.rncbc.ubuntu804_…
- binary packages (Ubuntu 9.10):
http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.6-1.rncbc.ubuntu910_…http://downloads.sourceforge.net/qjackctl/qjackctl_0.3.6-1.rncbc.ubuntu910_…
Weblog (upstream support):
http://www.rncbc.org
License:
QjackCtl is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
Change-log:
- Make sure socket names are unique on each side of the Patchbay
(another patch from Dominic Sacre, thanks).
- A bunch of primitive D-Bus interface slots have been added, allowing
shortcut access to most of main applications actions like toggling
Messages, Status, Connections, Patchbay widget pop-ups, reset stats,
transport and so on. New bindings are given eg. via dbus-send --system /
org.rncbc.qjackctl.(main, messages, status, connections, patchbay,
setup, about, reset, rewind, backward, play, pause, forward). (from an
original idea from Sebastian Gutsfeld, thanks).
- Patchbay snapshot now tolerates JACK client port strings that have
more than one semi-colon in it, honoring just the first one exactly as
everywhere else eg. Connections. (a glitch as reported by Geoff Beasley
while using a2jmidid).
- Most modal message dialog boxes (eg. critical errors) are now replaced
by system tray icon bubble messages where available (mitigating feature
request #2936455).
- Comply with jackd >= 0.118.0 which now runs in real-time mode by
default; use of -R is now deprecated from the jackd command line
interface options; use -r to run in non-real-time-scheduling.
- A man page has beed added.
- Got rid of a pretty old and never really useful "jackd-realtime"
server path option--actually, it was only seen available on the now
defunct old Mandrake Linux distro.
- D-Bus support, as provided by org.jackaudio.service aka jackdbus, is
now being introduced and used wherever available and whenever enabled.
Configuring, starting, stopping and logging the JACK back-end server
through the "infamous" jackdbus service is now being seamlessly exploited.
- Global configuration state is now explicitly saved/committed to disk
when Setup dialog changes are accepted and applied.
- Server name command line option added (-n, --server-name).
- Single application instance restriction option added (X11).
- Setup for the netjack (slave) "net" driver has now sample-rate and
frames per buffer (period size) settings disabled and/or ignored, as
those are pretty much auto-detected by default; also, a new "netone"
backend driver option has been introduced (as suggested by Torben Hohn).
- Czech (cs) translation added (by Pavel Fric).
- Fixed some main window keyboard shortcuts. Escape key now closes
Connections, Patchbay, Status and Messages widgets as usual (bug #2871548).
- Fixed glitch on configure portaudio support, specially when the
library is not detected as available.
Cheers && Enjoy.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
On Tue, Mar 9, 2010 at 2:54 PM, Ken Restivo <ken(a)restivo.org> wrote:
> If the new JACK session feature only saves things when I ask it to, then sure, that could be useful. Even better if it saves its state in a format that is human-readable and can be diff'ed, or put into git for versioning.
it doesn't change anything about how applications save state. it
merely provides for a unified way to initiate a save, and a unified
way to restart everything back in the same state (or as close as each
individual application will allow.
Am 06.03.2010 um 07:19 schrieb Ken Restivo <ken(a)restivo.org>:
> On Fri, Mar 05, 2010 at 10:16:51AM -0600, Josh Lawrence wrote:
>> On Fri, Mar 5, 2010 at 4:43 AM, Gerald Mwangi
>> <gerald.mwangi(a)gmx.de> wrote:
>>> Hi, does anyone know a synth powerfull like zynadd, phasex or
>>> bristol,but in dssi format? I need something I can load into
>>> Rosegarden,
>>> since I dont want 10 Standalones running, until ardour, rg and the
>>> synths support LASH, if that ever happens.
>>
>> I have no idea why, but I have a warm, fuzzy soft place in my heart
>> for DSSI plugins. they always seem to just work. whysynth has
>> already been mentioned, but be sure to check out the calf monosynth,
>> which can be run as a DSSI plugin:
>>
>> jack-dssi-host calf.so:Monosynth
>>
>> check out the DSSI home page too, for a lot of other options.
>>
>> I'm hoping this thread will reveal some that I don't know about! we
>> really need something like specimen in DSSI format.
>>
>>> I think LASH should be integrated into Jack, to make it mandatory
>>> for
>>> linux audio apps. The missing LASH support is one of the main issues
>>> disturbing me, when working with linux audio. Now I've said it, ha.
>>> I'm thinking of having Jack require a Load/Save callback, prior to
>>> activating the client. How feasible is that?
>>
>> why oh why oh why did you throw this paragraph in? now no one wants
>> to talk about DSSI anymore... :(
>>
>
> +1 for Calf Monosynth and WhySynth. They, in addition to AMS and
> PHASEX, are the synths I've used most.
>
> Zyn is kind of old and doesn't do RT; the new thing is Yoshimi, and
> I dunno if it supports LASH or ladish, but I'd guess both.
>
> For the record, I *HATE* session management and I don't run LASH at
> all when I can avoid it (IIRC, there's some synth that I use or used
> which requires LASH, so I occasionally have to start it up).
> I generally can't stand technologies that try to be "smart" and do
> things I don't explicitly instruct them to do. Frustrates the hell
> out of me.
>
> FWIW, I am also the kind of guy who turns off autocomplete and
> spelling checkers whenever I can.
>
How would you share a complicated production setup, aka session, with
other users? Script, or text explanation? Screenshot? Ardour audio
project only?
I'd love to have a rather bullet proof way to make my sessions
available to non-geek collaborators really fast and easy. And vice
versa.
Software trying to outsmart the user can be painful. On the other
hand, there are users out there waiting to hop on the linux audio boat
as soon as there is an obvious way to save and restore complex setups
without scripting. I'd love to make music with them.
It's good that you are happy with your way of using your DAW and so am
I. But it makes me a little sad sometimes that for remote
collaborators the learning curve is so steep.
- Burkhard
> -ken
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
I couldn't find a good list of audio latency testing tools,
so I put one together at
http://wiki.winehq.org/MeasuringAudioLatency
Did I miss any good ones?
Also, do any of them work? :-) I just tried the one in lib-alsa,
and it isn't happy.
Drumstick is a C++ wrapper around the ALSA library sequencer interface using
Qt4 objects, idioms and style. ALSA sequencer provides software support for
MIDI technology on Linux. Complementary classes for SMF and WRK file
processing are also included. This library is used in KMetronome, KMidimon
and KMid2, and was formerly known as "aseqmm".
Changes:
* Split into two libs: drumstick-alsa and drumstick-file
* Parse Cakewalk WRK files included in drumstick-file
* Some fixes and API additions. See the ChangeLog for details.
Copyright (C) 2009-2010, Pedro Lopez-Cabanillas
License: GPL v2 or later
Project web site
http://sf.net/projects/drumstick
Online documentation
http://drumstick.sourceforge.net/docs/
Downloads
http://sourceforge.net/projects/drumstick/files/0.3.0/
openSUSE Build Service - RPM packages
 http://software.opensuse.org/search?baseproject=ALL&p=1&q=drumstick
Regards,
Pedro
Hi there.
The distro I'm using installs a script with jack that lets it run as a
daemon.
I'm wondering whether this makes any sense at all, whether there is a
use case for this that isn't covered by anything else.
I'd like to hear you opinion.
http://repos.archlinux.org/wsvn/packages/jack/repos/testing-x86_64/?opt=dir
jack.conf is the config file in /etc/
jack.install is run when jack is installed/upgraded/removed
rc.jack is the daemon script itself
So what do you think?
Regards,
Philipp
The CLAM project is pleased to announce the first stable release of Chordata.
Chordata is a simple but powerful application that analyses the chords of any
music file in your computer. You can use it to travel back and forward the song
while watching insightful visualizations of the tonal features of the song.
Key bindings and mouse interactions for song navigation are designed thinking
in a musician with an instrument at hands.
Don't miss it working in this video:
http://www.youtube.com/watch?v=xVmkIznjUPE
Downloat it at http://clam-project.org
--
David GarcÃa Garzón
(Work) david dot garcia at upf anotherdot edu
http://www.iua.upf.edu/~dgarcia
As a power user who's modestly (just kidding) keen on saving time,
using great workflow, and avoiding as much of the drudgery of editing
work over and over again to get an end result as is possible, i've had
the privilege and pleasure of testing and working with a data protocol
called CV, or control voltage, in these last 2 weeks.
Non-Daw, and it's new buddy Non-Mixer, enable me to write function
data in ND control sequences, or "lanes" at will. From my POV it's
like turbo automation, and i'm still surprised and delighted at how
easy and FAST it is to work with. Without the multiple complexity that
is midi, in a simple 1:1 format, this is a very clever way to handle
automated data between apps, imho.
I ask Devs who are building up or modifying their linux audio and
video apps, if they could cast a brief eye over this protocol, and at
least spare a thought for the opportunities it offers to stream direct
data from one app to another. It seems to be an ideal solution for a
modular framework, without a lot of complexity involved. Best of all,
it uses jack ports to do the routing work, so there's no additional
work devs have to do, when trying to stream data across apps. I know
some of you will be familiar with this protocol, so this quick note
could be considered a reminder. :)
Non-Daw, and Non-Mixer are CV capable, and i can enthusiastically
testify to the system working very well indeed.
I guess you could call this a quick heads up for a community interapp
opportunity, and given the recent resurgence of the Session discussion
(woohoo), i'm thinking the CV protocol might be complementary as a
component in such a framework, from a user's perspective.
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
