Hi LADs,
It great to notice that the list of Non-Session-Manager (NSM) support is
growing, thanks!
Ardour 3, Carla, Qtractor Zita-rev1, Laborejo, Qmidiarp are examples of
apps which just got NSM support. AMS and Qmidiroute are WIP. (For a more
extended list, see below).
The nice thing about Carla, is that you can use LV2 plugins (and dssi,
sfz, gig, sf2, vst) as standalone jack apps in NSM now. So yes, LV2
plugins are also useful for working with a more modular approach.
Of course it would be nice if more developers start to support NSM in
their apps, most notable the nicest 'Jack standalone' apps imho:
- Rakarrack
- PHASEX
- Ingen
- Guitarix
- Giada and/or Kluppe (?) (JackTransport would be nice too)
- HarmonySEQ
- Muse
- Hydrogen
- ...
- ...
I'm sure I forgot quite a few...
Thanks in advance :)
\r
http://non.tuxfamily.org/wiki/Non%20Session%20Managerhttp://non.tuxfamily.org/wiki/ApplicationsSupportingNsmhttp://non.tuxfamily.org/wiki/NsmPatcheshttp://non.tuxfamily.org/nsm/API.html
Hi everybody!
Its my pleasure to announce, that after 9 days the Sorcer wavetable synth's
donation target has been reached. Not only that, but as I prepared to push
the code to github, not one but two more donations arrived.
Wauw. Thank you for kicking off OpenAV productions.
Now for the best part: Sorcer is available!
github.com/harryhaaren/openAV-Sorcer
Also, there's a repo of presets:
github.com/harryhaaren/openAV-presets
Bug reports to github.com/harryhaaren/openAV-Sorcer/issues
I hope you enjoy using Sorcer!
-Harry
Hi,
I'm happy to share with you a new beta release of io GNU/Linux.
The live is based on the free operating system Debian (sid)... and includes a
large collection of preinstalled programs for all uses, especially multimedia
creation.
If your looking for a version with realtime kernel, check:
http://mk.biniou.net/iognulinux.html
(without any warranty... doesn't work on some computers, depending mostly of
the video card)
Feedbacks welcome, enjoy :)
http://mk.biniou.net/iognulinux.htmlhttps://sourceforge.net/projects/io-gnu-linux
I will be getting a new audio rig in July. I would appreciate comments
from anyone who uses a RME system. I'm looking into a raydat and some
converters... and what D?A converters do you use?
thanks
g
Hello. After initial theme, "send midi message" faded through user-friendlity
into UI issues, i recalled about one old good thing, which seems to be
forgotten, mostly related to gtk2 pro apps theming (i don't even hope to get
it for fltk, since utf8 support in 1.3 is already great achievement, that may
be get for fltk1 apps now).
Some cool apps like ardour, guitarix, hybridreverb and probably, several more,
force to use some specific theme without the ability to change it in user-
friendly way. I already got answer from ardour maintainer, where my noticement
was treated as wishment to use global desktop application everywhere, and that
desktop themes are inadequate for pro-audio apps.
Honestly, i would like to have different look in some cases. One well known
case is root applications, colored to red or just more agressive/attenting
colors than users.
On screenshot: http://wstaw.org/m/2013/05/17/plasma-desktopJ20308.png
i placed seq24 with ardour3 dark theme and gjacktransport with my default
theme — hardcurve, which i have set globally.
I made it to demonstrate, that special application or sub-session wide look
should not be hardcoded (otherwise we could end up like gnome3/gtk3, which as
i heard, don't like when users customize it and break as on each new release
of gtk3). For case of cross-platform apps, which should not look ugly on
foreign systems, at least option to toggle between internal and system-wide
look should always appear.
I have to implement a tool, which should allow to run application, as well as
subsessions, with different look, while keeping user-friendly way to change
it.
On Friday 06 January 2012, you wrote:
> btw: is there a way to list available clients/ports from the api.
> I know that aconnect -i / -o does this, but is there a c/c++ function?
>
> Dave
The functions are: snd_seq_query_next_client() and snd_seq_query_next_port();
you need to loop calling these functions while they return a correct answer.
For instance, this is the relevant code in "aconnect.c" :
static void do_search_port(snd_seq_t *seq, int perm, action_func_t do_action)
{
snd_seq_client_info_t *cinfo;
snd_seq_port_info_t *pinfo;
int count;
snd_seq_client_info_alloca(&cinfo);
snd_seq_port_info_alloca(&pinfo);
snd_seq_client_info_set_client(cinfo, -1);
while (snd_seq_query_next_client(seq, cinfo) >= 0) {
/* reset query info */
snd_seq_port_info_set_client(pinfo,
snd_seq_client_info_get_client(cinfo));
snd_seq_port_info_set_port(pinfo, -1);
count = 0;
while (snd_seq_query_next_port(seq, pinfo) >= 0) {
if (check_permission(pinfo, perm)) {
do_action(seq, cinfo, pinfo, count);
count++;
}
}
}
}
See:
http://git.alsa-project.org/?p=alsa-utils.git;a=blob;f=seq/aconnect/aconnec…
I guess you already know the reference documentation site:
http://www.alsa-project.org/alsa-doc/alsa-lib/seq.html
Just for comparison, a similar enumeration using Drumstick looks like this:
QListIterator<PortInfo> it(m_Client->getAvailableOutputs());
while(it.hasNext()) {
PortInfo p = it.next();
cout << p.getClientName() << ":" << p.getPort();
}
See Drumstick's example "drumgrid":
http://drumstick.sourceforge.net/docs/drumgrid.cpp-example.html
Regards,
Pedro
just babbling around
- Back from LAC2013@IEM-Graz
http://www.rncbc.org/drupal/node/646
so much to tell, so short on time ...
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
MFP -- Music For Programmers
Release 0.04, "More Fun Patches"
I'm pleased to announce a new version of MFP, containing many fixes
and improvements. It is still not at a "production" level, but is
becoming more and more usable. Your interest and participation are
invited!
A summary of changes is below. Please see the GitHub issue tracker
for complete details:
http://github.com/bgribble/mfp
Thanks to the great environment, continuous hacking time, and great
feedback at LAC-2013, I was able to put in a record (for me) number of
commits (50+) during the last week and make many small and
not-so-small bugfixes and improvements. Please see http://lac.iem.at
for a video of my talk, and/or have a look at the paper and slides in
the source repository under doc/lac2013.
Changes since release v0.03.1:
----------------------------------------
* #31: Support exported UIs from user patches ("graph-on-parent")
* #64: Improved implementation of "Operate" mode, making
editing/control
fully modal
* #66: Expanded information in tooltips and "badges"
* #87: New Dial object (round slider)
* #85: Support audio input/output in user patches
* #111: Bind "app" to allow a message via to send messages to it
* Many other bugfixes and improvements.
About MFP:
----------------------------------------
MFP is an environment for visually composing computer programs, with
an emphasis on music and real-time audio synthesis and analysis. It's
very much inspired by Miller Puckette's Pure Data (pd) and Max/MSP,
with a bit of LabView and TouchOSC for good measure. It is targeted
at musicians, recording engineers, and software developers who like
the "patching" dataflow metaphor for constructing audio synthesis,
processing, and analysis networks.
MFP is a completely new code base, written in Python and C, with a
Clutter UI. It has been under development by a solo developer (me!),
as a spare-time project for several years.
Compared to Pure Data, its nearest relative, MFP is superficially
pretty similar but differs in a few key ways:
* MFP uses Python data natively. Any literal data entered in the
UI is parsed by the Python evaluator, and any Python value is a
legitimate "message" on the dataflow network
* MFP provides fairly raw access to Python constructs if desired.
For example, the built-in Python console allows live coding of
Python functions as patch elements at runtime.
* Name resolution and namespacing are addressed more robustly,
with explicit support for lexical scoping
* The UI is largely keyboard-driven, with a modal input system
that feels a bit like vim. The graphical presentation is a
single-window style with layers rather than multiple windows.
* There is fairly deep integration of Open Sound Control (OSC), with
every patch element having an OSC address and the ability to learn
any other desired address.
The code is still in early days, but has reached a point in its
lifecycle where at least some interesting workflows are operational
and it can be used for a good number of things. I think MFP is now
ripe for those with an experimental streak and/or development skills
to grab it, use it, and contribute to its design and development.
The code and issue tracker are hosted on GitHub:
https://github.com/bgribble/mfp
You can find the LAC-2013 paper and accompanying screenshots, some
sample patches, and a few other bits of documentation in the doc
directory of the GitHub repo. The README at the top level of the
source tree contains dependency, build, and getting-started
information.
Thanks,
Bill Gribble
Hiho,
here's a first preview of XOSC, an OSC patchbay (partly coded during
the LAC ;) ).
What it does:
Connect different OSC capable programs, considering the situation where
you have two programs talking via OSC, but then want to have a third or
fourth application to also use OSC from those same applications without
having to rewrite code.
Solution:
Just change the OSC messages' target host/port to XOSC's port, and
XOSC will allow you to patch OSC between applications.
- XOSC does not require any changes to original software to use it
- XOSC has an OSC interface to create connections.
Find it at:
https://github.com/sensestage/xosc
Basic functionality works as far as I have tested (with the included
supercollider script).
The program runs as a command line application and has an OSC
interface. By registering to it as a watcher another program will
receive any updates to connection changes, e.g. to display this in a
GUI.
I'd be happy if someone feels like implementing such a GUI. (I imagine
some of the classes can be reused for this purpose, and there is a
libxosc to link to)... think of an extra tab in QJackCtl (Rui will
be happy with a patch ;) ), Patchage, or others...
* Caveats:
Currently clients and hosts are kept in memory based on their port
number, so possibly there are conflicts when mapping between different
hosts. Similarly multiple programs sending the same tags might provide
problems.
Happy about feedback, suggestions, bug reports (use the issue tracker),
and patches :)
sincerely,
Marije Baalman
