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:
This is for all those who might have tried seq24 with jack2.
Attached is a patch containing modifications made by
Stéphane Letz, the developer of jack2 who was so kind to
have a look into the seq24 code yesterday.
In the original setting, seq24 was not able to do a proper
client connection and failed working with jack2 transport. It also fixes the deprecated call to jack_client_new.
It applies to src/perform.cpp , hope it works as a patch...
Thanks very much Stéphane.
I'm thinking about finally upgrading from my cheap soundblaster+mic to
something of a little higher quality. I'm thinking along the lines of an
external firewire/usb box and some kind of low-cost mic.
I'd use it primarely for vocals, but I'd like the recording interface to
support 2-channel, for possible some piano recordings/etc. I also don't want
to spend very much, and would plan to get it used, on ebay.
What do you guys use or recommend?
(Nederlandstalig linux forum gedeelte op homerecording.be >>>
Thanks to the LAU mailinglist, I've discovered the possibilities of Linux
for producing music in the last two years. But it seems I'm a bit of a
special case in The Netherlands... most people seems to use Mac or Windows
for music production, even people who prefer Linux as their main OS...
To change it a bit, I helped people on Linux forums and wrote a dutch
tutorial for Qjackctl and Ardour. I also posted my enthusiasm and knowledge
on 'not-linux' forums... got a lot negative reactions, but not on
www.homerecording.be. The had a open mind for opensource software... and
after posting some posts there, they have decided to open a special subforum
for making music on Linux! :) (Windows and Mac can't say that...)
It would be cool if dutch speaking people will support this forum part by
taking a look at it reguarly and to post some messages, moreover to help
people with making music on GNU/Linux!
You can find the forum here:
I've been looking at ingen ( http://drobilla.net/software/ingen/ ). Had
some problems getting it to build, but the trick turns out to be to
install liblo and libsoup bfore you configure the build. It's a really
nice bit of software - a GUI modular synth that lets you design and save
simple patches which can then be used as building blocks for more
The main problem I'm having with it so far is that it doesn't seem to
understand alsa midi - only jack midi. This is difficult as I don't have
or know of any midi programs (particularly a virtual keyboard) which
produce jack midi signals.
Does anyone know of an easy way to convert alsa midi into jack midi and
Another version of Ecasound/Nama is available at CPAN
for your multitrack recording pleasure. We are
approaching a 1.0 release!
Here are the newest changes:
- Track soloing
- Documentation rewrite
- Pager for long text listings
- Many bug fixes
- Simplified build script (preprocessing really) facilitates
And a feature list:
- Based on Ecasound, a stable, full-featured audio
- Very flexible template-based signal routing allows for
multiple buses. Possible to simultaneously record and
mixdown a live performance.
+ can be mono, stereo or any desired width
+ volume/pan with any number of effects
+ signal sources from soundcard or JACK clients
+ multiple WAV versions per track
+ playat, reverse, select, audioloop
- Tk based GUI
+ main window and effects window
+ auto-hinting of LADSPA plugin parameters range and linear/log
+ stable, lightweight
+ no dialog boxes considered a feature
- Full-featured text UI
+ Executes Ecasound commands, Nama commands, shell commands
and perl code
+ multiple commands per line
+ help for commands and plugins
- Automated connection to JACK clients
- Looping over entire chain setup between designated marks
- Full diagnostics with dumping of all data structures
- Persistent settings stored as browsable YAML
- Per-project configuration files
- Small codebase compared to other projects, ~7K lines
- Active development
- Hackable, extensible
Caveat! We're having some difficulties compiling
Audio::Ecasound, on which Nama depends, for x86-64.
The easiest way to install Nama is from CPAN:
If you'd prefer to install from sources, you can copy the
git clone git://github.com/bolangi/nama.git
Build instructions are found in the README.
I'm interested in any comments, bug reports, feature
requests, etc. you may have.
Many of the people of the Linux audio community uses Debian or a Debian
based distro (Ubuntu (Studio), 64Studio, Musix, Sidux, Mepis etc. etc.).
Most of those distro's uses and rebuild the packages of Debian (unstable).
There are a lot of audio packages build by the Debian Multimedia Team,
but there are also a lot which are not in Debian yet (and so also not in
Ubuntu (Studio), Sidux, 64studio etc.)
So there is a need for more people who wants to contribute to the Debian
Multimedia Team. Again, you don't have to be a plain Debian user to
contribute or to take advantage of it. You will help to improve the
state of Linux audio in general (at least the Debian based distro's and
their community), which will be good for us all, but also for newbies
who are not able yet to build all the packages themselves to enjoy all
the nice things Linux audio has to offer. Also note that it is possible
to build Debian unstable packages on other distro's then Debian itself
(search for Pbuilder on the Internet for instance)!
It will also be good for the Linux audio developers and their software.
It would be more easy to install, use, test and enjoy the software by
the Linux audio community!
There are a lot of people these day who has an own (PPA) repo. This is
ok, (and maybe it will be a good thing if the Linux audio developers
make their packages available as much as possible in a Debian unstable
repo/package, so it can be used on Debian and it is easy to rebuild it
for Debian based distro's),
But to bundle forces and to get safe, stable and quality packages,
joining the Debian Multimedia Team will get much better quality packages
and you will help far more people then having your solo private repo...
*Why the Debian Multimedia Team? *
1) Because they want to improve Debian for music production!
2) Debian has an flexible, fast and easy package management
3) A lot of people use Debian (based) distro's, Debian itself, Ubuntu
(Studio), 64studio, Sidux, Mepis etc.
4) You will learn to build quality packages
5) You don't have to become a Debian developer (DD), you can just become
and stay a package maintainer.
*What can I do?*
1) Build or improve packages for the Debian Multimedia Team. It's
recommended to maintain packages you use yourself often.
2) Report bugs and wishes
3) Join the Debian multimedia team mailing list:
*Where can I find more info?*
Existing packages which needs help:
Debian New Maintainers' guide:
It would be great if you choose one package which you uses a lot and
maintain it for the Debian Multimedia Team! It would improve the quality
of Linux audio and it will help the whole community!
ps. If you like to join, please subscribe to the Debian Multimedia Team
mailinglist and ask for more information:
OK, back home again, with the feet under the desk.
I have a question.
I've been having a terrific run with Ingen, and slowly building up an
Can i open jconv and linuxsampler in Ingen as either plugins, or
'recognised' apps? I'm not sure of the means of inserting command line apps
in Ingen, so it may already be possible.
I start both Jconv and Linuxsampler (with templates) from the command line
by default these days, so a means of inserting a 'command line plugin' in
Ingen might prove useful. (or not as the case may be)
The intention is to build a series of 'layers' for each app and associated
ports, all routed to the top 'master' view. If i can start Ingen, and load
the saved patch file, then i hop that everything will start, including
templates, in one go.
Any help with this, or good reasons why it's not feasible, would be
Parchment Studios (It started as a joke...)