This is Steinway_IMIS soundfont, version 2.2.
This version fixes the issue with loops. I hope this is the good one
and there are no more remaining major bugs.
Marcos is a little busy right now, so he asked me to make this fix. He
is thinking to make other improvements, so expect more updates soon.
Does anyone know of a good plugin that will generate subharmonics?
I would like to put a little more low frequency "oomph" into my bass
track. Preferrable LADSPA, but VST would work, too.
Thanks for any help!
> Ken Restivo wrote:
>> It has been over 7 years since I last messed around with writing Pthreads applications.
>> I recall it as a painful, ugly, brain-numbing task. I located an exercise I did back then to address the consumer/producer problem in Pthreads, and just the sight of it is giving me a headache.
>> I'm being lazy, so instead of researching everything that's out there, I'll ask here: can anyone recommend a relatively simple and painless abstraction library (GPL or LGPL of course) that will give me functions to create a thread in which I can stuff things into a ring buffer, and another thread in which I can pull stuff out of it?
>> By the way, I know that JACK has a very nice event buffer which is insanely easy to use (and I have), and makes multithreading almost transparent, but this isn't a JACK app.
> I don't know of any abstraction library, but creating/terminating a normal
> thread with pthread is really an easy task IMO. It's about 10 lines in C.
> For inter-thread communication there's Portaudio's ring buffer:
> It can easily be used out of Portaudio (I'm currently doing that), and it
> features memory barriers  which AFAIK Jack's ringbuffer doesn't.
> One problem with everything Portaudio is this heavy naming scheme. For a simpler
> API, you might like my little wrapper:
Nice. It's probably quicker to copy the jack_ringbuffer.c file out of jack
> Portaudio actually also offers a callback mechanism (with hidden thread
> creation), so if you're coding an non-JACK audio app, you might want to check it
> For thread synchronization, semaphores (man semaphore.h) are really easy to use.
> However, if you need a lock-free equivalent (for realtime, ...) phtread mutex
> and especially pthread_mutex_trylock are your friends.
Those friends can be really cranky sometimes though.
By using atomic operations instead, it's possible to avoid
a lot of headache by not having to synchronize at all.
Performance might be better too. Midishare has lockfree
atomic functions for lifo and fifi queues:
Can't seem to start jackd in realtime as user on ubuntu studio. It
does start as root, but that's hardly a consolation (unless I run all
audio software as root, which would be kinda daft IMO)
@audio - rtprio 99
@audio - nice -10
@audio - memlock unlimited
have been added to /etc/security/limits.conf
Nevertheless, starting it as user just doesn't seem to work, and I
just can't figure out why. I've googled the issue, and everybody seems
to agree that modifying limits.conf in the above manner should solve
the problem - yet this is what I get:
mick@kaizoku:~$ jackd -R -P89 -dalsa -dhw:0 -r48000 -p256 -n3 -S &
mick@kaizoku:~$ no message buffer overruns
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1217255744, from thread -1217255744] (1: Operation not permitted)
cannot create engine
sorry, just realized that the hammond discussion mentioned below was here and
not at LAD, so please allow this kind of "crosspost":
this is my first post to LAD. The discussion about a hammond simulation "Fons
could you make us...", Beatrix and some research for writing a (german)
wikipedia article (stub) about the Vox Continental inspired me to hack a quick
organ program that simulates the internal signal flow of the "Connie" with JACK
MIDI input and JACK audio output.
Frank Kober wrote:
> Hi there,
> I just noticed that I'm not able to save sounds to my custom root bank directory,
> and wondered if I did something wrong setting this up in my home. Also, when I
> try to change the name of the current sound with a right click, the dialog opens
> OK and lets me enter the patch name, but it won't keep it when I click OK.
> Any idea? I thought about my bank dir file permissions, but they seem to be OK.
> I'm not sure, but I think that this worked already with yoshimi. I cannot tell the
> last version with which it did though...
Right click instrument name change now works. For me, saving to a custom bank root
seems ok, but some funkiness there wouldn't greatly surprise me. If it still doesn't
satisfy, perhaps you can spell out the steps you're taking and from that I'll
hopefully be able to figure out where it's going wrong.
0.021 fix right click instrument rename and a couple of bank management issues
The second milestone is reached and result is a tarball that brave souls
may want to download and try. It can start apps and restore their
connections. Level 1 apps are supported.
Beware that no apps have implemented level 1 yet. If non-level-1 app is
started at level 1, it will probably quit on save, because the default
signal handler for SIGUSR1 terminates the process.
This preview also features a2jmidid support. Run the a2j script as an
app in the studio.
This is a beta quality software, use it with double caution.
I would like to thank the early adopters and especially Frank Kober for
their help with testing the git ladish code and for the valuable
suggestions they gave.
Build will produce three operational components:
* ladishd - The daemon, a D-Bus service
* gladish - GTK GUI interface
* ladish_control - Command-line interface
In the tarball you will also find bundled:
* LADI Tools (svn version)
* a2jmidid-6 (contains the a2j script for use in ladish)
* jack2 from the ladi branch
The jack2 ladi branch contains fixes for two important issues:
* Race that causes connection restore to fail sometimes during studio
* A deadlock on studio start (http://ladish.org/ticket/35)
Hopefully, these fixes with be in the next jack2 release (1.9.5).
The jack2 ladi branch also contains the no-self-connect changeset that
adds new engine option, for disabling self connect of apps. Default
value for this option is to allow self connections.
Make sure to configure jack2 with --dbus (and maybe with --classic too).
LADI Session Handler or simply ladish is a session management system
for JACK applications on GNU/Linux. Its aim is to allow you to have
many different audio programs running at once, to save their setup,
close them down and then easily reload the setup at some other
time. ladish doesn't deal with any kind of audio or MIDI data itself;
it just runs programs, deals with saving/loading (arbitrary) data and
connects JACK ports together. It can also be used to move entire
sessions between computers, or post sessions on the Internet for
* Save and restore sets of JACK (audio and MIDI) enabled
* Provide JACK clients with virtual hardware ports, so projects can
be transfered (or backups restored) between computers running
different hardware and backups.
* Don't require session handling library to be used. There is no need
of such library for restoring connections between JACK clients.
* Flow canvas based GUI. Positions of elements on the canvas are
* Allow clients to use external storage to save its state. This
includes storing internal state to non-filesystem place like memory
of a hardware synth. This also includes storing client internal
state (client project data) in a way that is not directly bound to
* Import/export operations, as opposed to save/load. Save/load
operate in current system and may cause saving data outside of
project itself (external storage). Import/export uses/produces
"tarball" suitable for transferring session data over network to
other computer or storing it in a backup archive.
* Hierarchical or tag-based organization of projects.
* List of JACK applications. Applications are always started through
ladish to have restored runtime environment closer to one existed
before project save.
* Distributed studio - network connected computers. Netjack
configuration is part of the studio and thus is saved/restored.
* Collaborate with the X11 window manager so window properties like
window position, virtual desktop and screen (multimonitor) are
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
>> But actually you guys lost me a bit, what is so important about the plugin paradigma?
if you have quite a lot plugins with good presets, you actually don't
have to learn anything. just try this and try that, and you've done.
sex, bike, open source!
(pre-prost-scriptum: improtant informations are quite below!!!)
I think I didn't any announcement here before, but the label I created
some years ago, and work in by now, released two albums fully realized
with free softwares (on a Debian GNU/Linux distribution) in 2008:
Sebkha-Chott - Nigla[h] / Tapisseries Fines en XXX Strips et LXX/X Trompettes
Sebkha-Chott - De la Persistance de la Mythologie Chottienne en ??? Vélos
Both those albums are distributed internationally by the label Muséa
Records, and you may find them, freely downloadable and/or to purchase
and at a lot of other places on the web. You also might find numerous
review of those albums, in Google, and so on.
OK, that's it for the presentation.
Actually, it took us a lot of time, but we finally sent the whole tracks
of the 14 multitracks session (in ardour) and the session them selves on
archive.org, so that you can use them freely.
it's quite big big big sessions, as Sebkha-Chott used to be 8 people at
that time and invited something like 25-30 guests to play with. So you
might find something like 100-150 (even 180 on one of them, if I
remember well) tracks by song.
For Nigla[h], there are two options: we did tarball of each ardour
sessions directory and we also bounced every tracks in one file, so that
you can manage to use them in another multitrack editor.
We then thought about it, and had the conclusion that it was a really
hard work for us to do all these bounces and exports, and finally it
essentially was destined to people using proprietary softwares.
So, for De la Persistance, you will only find the tarballs, as we think
we have to "encourage" people using ardour, or, if they prefer ecasound
or whatever, they probably will be skilled enough to convert the xml
file into something suitable for another soft, or a bit worse, they
always might do all that export stuff and so on.
The archive.org links are listed on
Hope you will enjoy it. All our further productions will follow the very
same line (there will be one recording session in November for a
pop-prog-rock band), and we also aim to release some very huge
instruments sample base, as we have the luck to possess a very good
studio, and also very good instrument, including, for example, a true
Harpsichord, as one of us do build Harpsichords!
Aurélien - AMMD www.ammd.net
PS: For off-list further informations, please write to orlATammmmmmmd.net,
which is my pro mail, which I don't want to subscribe on this list (and
ammd does spell with two 'm' only! ;)