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:
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.
Couple of days ago I saw a thread about learning drums rhythms. Maybe my
website can help : www.percunivers.com (click on the uk flag for the
english version). Not only about drums, because everything is made under
64Studio (mainly ardour and lilypond). The weak point is about mp3 for
the exercices. I have no choice because this is the only format I can
use for streaming (via flash, argh!) and the only way to have my mp3
played on any Ipod-like from my students. I'm open for any open
Maybe this can help, hope you send me any feedback.
And here is the next installment in the saga of trying to get Ingo RT going on my Asus EEE.
I successfully built and ran the 22.214.171.124-rt12 with the alsa_seq patch. It ran.
The problem is that neither the Ethernet (atl1e) or wireless (rt2860sta) work. So I pretty much had to reboot back out of it immediately.
It appears that the atl1e driver I need to get my Ethernet working, is not supported AT ALL in 2.6.26. The Debian Lenny kernel 2.6.26 has some kind of backport of all kinds of stuff from 2.6.27, including the atl1e I need.
I could try to reverse-engineer whatever it is that the Debian maintaners have done to get atl1e backported (it seems they've had to fix some bugs in the backported driver too), or, I could just try with 2.6.27 or higher and thus have the hardware support I need to make my netbook usable.
Only problem is, it doesn't look like there is any such thing as a 2.6.27 Ingo RT patch yet. His stuff stops at 2.6.26.
So now what? Any idea as to when there might be a nice stable RT kernel cocktail of the 2.6.27 or higher variety? Or am I going to have to try to figure out what portions of the Debian Lenny patches I have to apply to my Ingo-patched 126.96.36.199 kernel, and then try to get them to apply cleanly?