Hi all (especially Fons!)!
I've just successfully compiled and installed aeolus (lastest release). I
can start the program connect it to jack and alsa midi seqeuncer, but there it
stops. I asked a seeing companion of mine to have a look at the ui, but even
after pressing several buttons, there was no sound.
Now my questions:
1. Is this a bug or just me and my friend being to stupid?
2. Are there shortcuts/hotkeys, so I can use the organ myself without help?
3. Are there maybe other ways to use it vai "remote control" (OSC, etc.)?
I'm greatful for any good suggestions and hints!
Kindest regards
Julien
P.S.: I read the installation instruction and directory/configuration hints
very carefully, it shouldn't be that... :-)
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
Attached is a pdf containing the job announcement for Director of
Technical Support at Radio Free Asia. We use Linux and Free Software
for most of our network information systems and also for a number of
middleware applications that glue together our various proprietary audio
systems. We also have users beginning to test Audacity as a replacement
for Cool Edit. In the future I see a place for Ardour as a replacement
for our 30+ aging Orban Audicy(tm) DAWs, Audacity as a replacement for
Cool Edit, icecast/ogg-vorbis/ecasound to replace our hardware mp3
encoders for streaming and archiving and perhaps other uses of linux
audio software as well.
Address any replies to jobs(a)rfa.org
Thanks,
--
Eric Dantan Rzewnicki | Systems Engineer I
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.
Announcing blepvco 0.1.0:
http://home.jps.net/~musound/blepvco-0.1.0.tar.gz
blepvco is a LADSPA plugin library containing three anti-aliased,
minBLEP-based, hard-sync-capable oscillator plugins. The
oscillators are intended to be used with modular synthesis systems,
such as Alsa Modular Synth (a couple example AMS patches are
included). The three oscillators are:
Sync-Saw-VCO : Anti-aliased sawtooth oscillator with hard-sync
capability
Sync-Rect-VCO : Anti-aliased variable-width rectangle oscillator, with
sync
Sync-Tri-VCO : Anti-aliased variable-slope triangle oscillator, with
sync
Users of Fons Adriaensen's VCO-plugins will find these plugins
immediately familiar, since they borrow much of their interface code
from Fons' work -- indeed, if/when you do not need the hard-sync or
variable-slope triangle wave features of blepvco, his plugins may be
a better choice, because their CPU use is somewhat lower. Currently,
his VCO-plugins can be found at:
http://users.skynet.be/solaris/linuxaudio/
blepvco is written by Sean Bolton, and copyright (c)2005 under the
GNU General Public License, version 2 or later. Much thanks to Fons,
Daniel Werner, Tim Stilson and Julius Smith, and Eli Brandt.
Congratulations to comix & crew !
This just in:
From: Comix <acominu(a)tiscali.it>
To: ML Hydrogen-devel <hydrogen-devel(a)lists.sourceforge.net>
Cc: hydrogen-users(a)lists.sourceforge.net,
hydrogen-announce(a)lists.sourceforge.net
Date: Tue, 01 Feb 2005 16:24:55 +0100
Subject: [Hydrogen-devel] Hydrogen won in 1st italian Open Source Contest
http://www.opensourcecontest.it/index.php?sezione=premiazione
Thanks all! ^_^
-- comix
// Sorry for crossposting, I have got the only reply at the LAU list :-(
Hi,
Will be glad to get your opinions about choosing an audio
card below $250. The main (and, probably, the only) planned
using is a playing back of stereo files. Probably, a DAC
quality is the main feature here.
With hope,
Andrew
Greetings:
When I use jack_fst with the Crystal synth it works fine, but when I
close the plugin qjackctl closes too. Its settings remain in effect, but
the GUI vanishes. If anyone else has this problem, please let me know if
you've found a fix for it. It's annoying to have to reopen qjackctl each
time I use jack_fst.
jack_fst 1.2, qjackctl 0.2.14
Best,
dp
I meed to communicate with MIDI devices from an embedded Linux world
(Gumstix). Its UARTs are cabable of:
14.7456M/16*29 = 31779
14.7456M/16*30 = 30720
MIDI spec says +-1%. My error is 1.7%, Is this close enough?
I figure this problem can't be new, but I'm finding very little info
about it. Some sites hint that an error of up to 3% is OK with certain
MIDI devices.
Any advice appreciated,
darren
Mx41 minor update at
http://hem.passagen.se/ja_linux
This wasn't on my todo list, but I just stumbled over the missing link
in the voice assign/stealing algorithm and couldn't help implementing
it. Just to check out if it really worked ... and I think it did :)
I now have voices in five assignment-ques:
silent // absolutely idle voices
released // voices about to become idle
excess holdpedal // elder voices than mentioned below ..
holdpedal // the two most recent voices for a given key
fingered // voices where the key is still pressed
... and a short two-voice que for each key to figure out the 'excess'
part.
Voice assign will at best find a silent voice and at worst a fingered
voice.
Rolls (tremolo?) now works proper without stealing highest or lowest
note, nor anything inbetween for that matter. Finally!
Is there room for improvement? Yes I think so ... It is now possible to
get 'clicks' with certain combinations of envelope and playingstyle. On
the other hand it is also quite easy to avoid, so I will work slowly on
this one.
--
(
)
c[] mvh // Jens M Andreasen
Hello.
It is no problem to design or write reverbs. The problem
is in coding the interface (API, GUI, etc.) to the reverb.
Here are some numbers. Yet unreleased jackgverb source code
has 20 parameters, and I have coded only the early reflection
section. All 20 parameters are meaningful to the end users, i.e.,
they are not developer parameters such as lengths of individual
delay lines. Therefore the number of parameters cannot be reduced
without making the reverb dull, canned.
For each parameter I have the following functions:
-a GUI callback (e.g., slider)
-jackgverb_set() and jackgverb_get() called in the GUI callbacks
-gverb_set() and gverb_get() called in jackgverb_set/get()
Perhaps jackgverb_set/get() are unnecessary. I have them because
gverb is an enclosed system with API and if I need to add
something to the jack wrapping, its place is in jackgverb_set/get().
So, in total I have 5*20 = 100 functions for the parameters. The
whole situation is a nightmare. I don't have time nor interest in
coding with that kind of system. It all gets worse if the design
is changed as often happens in the design phase.
What would help? If nobody figures out anything, I could draw the
reverb design on a small piece of paper and then somebody else
may torture himself in coding.
Are there coding patterns which would make my C code simpler?
Would modular system help? PD has strange firing rules: does they
apply to standard signal flow or to advanced ones? Feedback
paths should be sample accurate, not blocked to N samples as
in Csound.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software