Tarball containing D-Bus patched jack 0.117.0 is available here:
http://nedko.arnaudov.name/soft/jack/dbus/http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…
D-Bus modifications add optional autodetected support for the D-Bus
based server control system.
D-Bus is object model that provides IPC mechanism. D-Bus supports
autoactivation of objects, thus making it simple and reliable to code a
"single instance" application or daemon, and to launch applications and
daemons on demand when their services are needed.
* Simplified single thread model for control and monitor
applications. Various D-Bus language bindings make it trivial to
write control and monitor applications using scripting languages like
Python, Ruby, Perl, etc..
* JACK has log file (~/.log/jack/jackdbus.log) that is available for
inspection even when autoactivation happens because of first JACK
application is launched.
* There is real configuration file used to persist settings that can be
manipulated through configuration interface of JACK D-Bus object.
* Improved graph inspection and control mechanism. JACK graph is
versioned. Connections, ports and clients have unique (monotonically
increasing) numeric IDs.
* High level abstraction of JACK settings. Allows applications that can
configure JACK to expose parameters that were not known at compile
(or tarball release) time.
Currently there are some minor differences between jack1 jackdbus and
jack2 jackdbus:
* There is no parameter constraints support (no enums and no ranges)
* No get client pid function (probably affects lash)
* Settings file (in ~/.config/jack/) is conf-jack1.xml instead of
conf.xml, because jack1 and jack2 settings and not really compatible.
When configured with D-Bus support, jack_control is
installed. jack_control is simple commandline interface for jackdbus.
Other tools that can communicate with JACK through D-Bus:
* LADItools (tray icon, configuration, etc.)
* Patchage (and lpatchage too)
* LASH 0.6.x (may not work properly with jack1 jackdbus implementation)
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
I have started a new project called Composite, which is planned to be a
sequencer for live-performance sequencing, sampling, and looping. One might
say that it will be like Ableton Live. It will be an LV2 host for synths and
effects, and will have a built-in sampler (which will probably be an LV2
plugin).
At this time, the project is in the planning stages.[1] Anyone who is
interested is invited to join the mailing list and share your thoughts and
opinions -- especially as it relates to UI and workflow.[2]
Links......
Project: http://gabe.is-a-geek.org/composite/
Mailing List: http://groups.google.com/group/composite-dev
Code: http://gitorious.org/composite
Specs (WIP): http://gabe.is-a-geek.org/composite/specification.html
FAQ: http://gabe.is-a-geek.org/composite/faq.html
Thanks especially to Patrick Shirkey for stirring things up.
Peace,
Gabriel
CC: LAU, LAD, LAA, Composite-Dev
[1] Strategy: Create a published spec. of what we want to
accomplish, and then get after it. There is currently
no code, but we plan to steal as much as we can.
[2] However, these will probably *not* change:
+ Will be monolithic. Let's not start a monolithic
vs. modular debate.
+ Will use Qt and C++.
I have started a new project called Composite, which is planned to be a
sequencer for live-performance sequencing, sampling, and looping. One
might say that it will be like Ableton Live. It will be an LV2 host for
synths and effects, and will have a built-in sampler (which will probably
be an LV2 plugin).
At this time, the project is in the planning stages.[1] Anyone who is
interested is invited to join the mailing list and share your thoughts and
opinions -- especially as it relates to UI and workflow.[2]
Links......
Project: http://gabe.is-a-geek.org/composite/
Mailing List: http://groups.google.com/group/composite-dev
Code: http://gitorious.org/composite
Specs (WIP): http://gabe.is-a-geek.org/composite/specification.html
FAQ: http://gabe.is-a-geek.org/composite/faq.html
Thanks especially to Patrick Shirkey for stirring things up.
Peace,
Gabriel
CC: LAU, LAD, LAA, Composite-Dev
[1] Strategy: Create a published spec. of what we want to
accomplish, and then get after it. There is currently
no code, but we plan to steal as much as we can.
[2] However, these will probably *not* change:
+ Will be monolithic. Let's not start a monolithic
vs. modular debate.
+ Will use Qt and C++.
BigBand is a program to compose real music for real musicians.
If you are interested then please visit:
members.chello.nl/w.boeke/bigband/index.html
BigBand should be easily portable to different Linux versions as
it is built using only the SDL libraries for graphics and sound.
Kind regards,
Wouter Boeke
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
We've just added a new service to linuxaudio.org:
http://planet.linuxaudio.org/
..to make it easy to keep up on what people are up to in general and you
can browse the planet to see who you'd like to follow..
If you want your blog to be included in planet.linuxaudio.org, visit:
http://wiki.linuxaudio.org/wiki/planet
Kudos to Dave Robillard and Erik de Castro Lopo for suggesting and
pushing this idea.
Cheers!
robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkr0IeMACgkQeVUk8U+VK0I+cACgrbxIg1I5wLzgoiGzWUrTnwWz
Qg4AoKr9xOfCO/ArCPN8x9nB3wxN7eKl
=zulW
-----END PGP SIGNATURE-----
On behalf of the FluidSynth development team, I'm happy to announce
the release of FluidSynth 1.1.0 "A More Solid Fluid".
This is the result of a 6 month development cycle and is the most
significant release since 1.0.0.
FluidSynth is a software wavetable synthesizer based on the SoundFont
2 specification.
http://fluidsynth.resonance.org
New features and changes:
* Extensive work on making FluidSynth more thread safe, resulting in
better stability.
* Audio file rendering for MIDI to audio file conversion, faster
than realtime (#15).
* Optional libsndfile support for file rendering in different audio
file formats (wav, flac, ogg vorbis, etc) (#30).
* Audio and MIDI are synchronized for MIDI file playback.
* Server can be specified for Jack audio and MIDI drivers.
* Jack audio and MIDI is now synchronized (when same Jack server used).
* MIDI file playback is now timed correctly, even with large audio
buffer sizes.
* Fixed issue with missing percussion in MIDI files caused by very
short notes, using synth.min-note-length setting (#1).
* Improved support for MIDI tuning standard, including SYSEX support
and realtime tuning activation.
* Multi-core support for utilizing multiple CPUs for synthesis or
increasing speed of file rendering.
* Voices for a note-on event are started synchronously (#46).
* TCP/IP shell server support for windows (#20).
* Improved settings output (-o help) (alphabetically sorted and
string options listed).
* Audio driver (-a) and MIDI driver (-m) options now accept "help"
and list available options (#41).
* Added audio.realtime-prio and midi.realtime-prio for controlling
realtime scheduling of some audio and MIDI drivers.
* Default priority levels of audio and MIDI threads set to 60 and 50
respectively.
* All yes/no string boolean settings converted to integer toggle
settings (with backwards compatibility).
* glib is now a required dependency.
* Updated README-OSX
* Added "voice_count" shell command for getting current number of
active voices.
New command line options:
-F, --fast-render=[file]
-T, --audio-file-type
-O, --audio-file-format
-E, --audio-file-endian
New or changed parameters:
* Audio file output settings: audio.file.endian, audio.file.format,
audio.file.name, audio.file.type, audio.sample-format
* Realtime scheduling settings: audio.realtime-prio, midi.realtime-prio
* Jack settings: audio.jack.server and midi.jack.server
* Other settings: player.reset-synth, player.timing-source,
synth.cpu-cores (experimental), synth.min-note-length
Bug fixes and minor changes:
* Fixed enabling of high priority scheduling in many audio drivers.
* Fixed bank selection logic
* Build fixes for mingw and VC++ builds on Windows
* Fix default values (after MIDI reset) to be more consistent with
MIDI spec (#29).
* Removed VintageDreamsWaves-v2.sf2 since it wasn't under a free license.
* Solaris build fix (#52)
* Implemented fluid_player_set_loop (#33)
* Fixed scaletune error (#26)
* Fixed synth reset between songs (#31)
* Fixed pitch bend error in Windows MIDI driver (#54)
* Skip remaining track data in MIDI file after EOT (#53)
* Bug fix in MIDI router where mutex was left locked with MIDI
system reset message.
* Help command now shows list of topics instead of General help.
* Fixed non-blocking in alsa_raw, alsa_seq and OSS MIDI drivers.
* Fixed segfault on config file load (#45).
Changes affecting developers:
* Developer API docs overhauled and now very complete.
* Lots of code cleanup in fluid_synth.c, fluid_chorus.c,
fluid_reverb.c and fluid_chan.c.
* Improved use of settings hints for all settings.
* char * arguments changed to const char * for many function prototypes.
* Many new API functions.
See "Whats new in 1.1.0?" section in developer API documentation for
more details:
http://fluidsynth.resonance.org/docs/api/index.html#NewIn1_1_0
Contributors
------------
Josh Green
David Henningsson
Pedro Lopez-Cabanillas
Ebrahim Mayat
And many others!