Hi!
Horgand ... is a organ, jack capable who generates sound with a FM based
synthesizer, also provides DSP effects and a small programable accompaniment
in wave table.
Requires:
FLTK
ALSA
JACK
LIBSNDFILE
News on 1.05
--------------------
-Program Change in main window.
-FIFO Realtime priority.
-Memory Lock.
-Resizable Windows.
-New sounds.
-Ready to play when starts.
-Improved Rotary
-Improved graphic refresh
-Bug Fixes
available in:
http://download.berlios.de/horgand/horgand-1.05.tar.gz
Thanks
Josep
Hello all. I have recently installed Debian and compiled 2.6.0-9test for a new Hammerfall digi9652 card I purchased. I'm having a very difficult time getting alsa to recognize the card and am hoping someone here might have some ideas.
The most damning symptom is that cat /proc/asound/cards gives only: ---no soundcards---
Running aplay phone.wav (as root and reg users) gives the following error:
aplay: main:484: audio open error: No such device
And trying to start alsamixer (as root and reg user) gives:
alsamixer: function snd_ctl_open failed for default: No such device
I have heard that some professional soundcards do not have hardware mixers. The user's manual for the Hammerfall digi9652 doesn't say anything about a hardware mixer so this could be the case for this card.
I have pasted background information below that I hope might be helpful. Thank you in advance for any advice you might provide.
Kris Bergstrom
Los Angeles, CA
SYSTEM
uname -r
2.6.0-test9
I checked all the dependencies of the kernel before compiling and they were fine. I compiled the kernel without error.
soundcard: RME Hammerfall digi9652
ALSA RELATED
dpkg -l | grep alsa
ii alsa-base 0.9.6-5 ALSA sound driver common files
ii alsa-utils 0.9.6-1 Advanced Linux Sound Architecture (utils)
ii alsaconf 0.9.6-5 ALSA configuration generato
more /etc/modprobe.d/alsa
### DEBCONF MAGIC
# This file was automatically generated by alsa-base's debconf stuff
alias char-major-116 snd
alias char-major-14 soundcore
options snd major=116 cards_limit=4
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-rme9652
alias snd-slot-0 snd-card-0
alias sound-slot-0 snd-slot-0
lsmod:
Module Size Used by
snd_seq_oss 34048 0
snd_seq_midi_event 7936 1 snd_seq_oss
snd_seq 54160 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8200 2 snd_seq_oss,snd_seq
snd_pcm_oss 51876 0
snd_mixer_oss 18944 1 snd_pcm_oss
snd_rme9652 27972 0
snd_pcm 96292 2 snd_pcm_oss,snd_rme9652
snd_page_alloc 11780 2 snd_rme9652,snd_pcm
snd_timer 25220 2 snd_seq,snd_pcm
snd 48996 9 snd_seq_oss,snd_seq_midi_event,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_rme9652,snd_pcm,snd_timer
soundcore 9152 1 snd
8139too 20736 0
mii 5248 1 8139too
crc32 4608 1 8139too
af_packet 16904 2
In case it's of use: I accidentally ran ./snddevices when trying to debug the problem. I now think that one needn't do that with newer versions of alsa. If that were causing problems, I'd assume it would be a problem of only being able to run a program as root but I could certainly be wrong.
--
H5n9d0+5
Greetings:
I thought about posting a response to the linuxaudio.org controversy
but I've opted for posting some numbers instead.
It was pointed out that LAD can claim more than 700 members now.
Very cool, I love it. I'm not sure exactly what those numbers mean, but
I do know that only about 1/10 of that figure actually post regularly to
the list. So out of the 700 only ~70 are consistent contributors. Again,
I don't know what the numbers signify. I guess it's [your meaning here].
On January 7 Linux Journal On-line posted my second monthly column
(this one about Planet CCRMA and AGNULA). I checked for the number of
reads this morning: +10000. That's right, more than ten thousand in
little over one week. I point this out not to shine my own light, but to
indicate again that far more people are interested in Linux audio
development than the mail lists' membership numbers suggest.
(Actually I have a lot of thoughts on all this stuff, but I'm really
just too busy here for further comment.)
Back to the hack...
Best regards,
Dave Phillips
Hi.
Can anyone recommend a motherboard for Linux / multimedia? Probably mostly
Ardour and + some softsynths. I have a P4 2.4Gb / Socket 478 I'd like to put
in it.
As an aside, are dual mobos considered a good idea for realtime stuff these
days? Just asking out of interest, don't think I'm going to get one this time
around.
Cheers.
JACK RELEASE 0.94.0
JACK is a low-latency audio server, written primarily for the GNU/Linux
operating system. It can connect a number of different applications to
an audio device, as well as allowing them to share audio between
themselves. Its clients can run in their own processes (ie. as normal
applications), or can they can run within the JACK server (ie. as a
"plugin").
JACK is different from other audio server efforts in that it has been
designed from the ground up to be suitable for professional audio work.
This means that it focuses on two key areas: synchronous execution of
all clients, and low latency operation.
JACK's webpage is at http://jackit.sf.net .
CHANGES:
Mostly minor, internal changes.
* Added missing extern "C" {} for better C++ support.
* Added missing copyright header.
* Better placement of watchdog check so it doesn't interfere with
freewheeling mode.
* Fixed option parsing problems
* ALSA driver reports actual samplerate, not requested samplerate.
* Handles hardware where playback and capture rates differ better.
* Support for native endian S24_3 format used by USB soundcards.
* jack_metro example ported to new transport API.
* cleaned up prototype declarations for jack_initialize_shm() and
jack_cleanup_shm().
* Eliminated calls to jack_error() when jack_client_new() fails
because the server was not running.
* Eliminated other calls to fprintf() in libjack.
* Won't try and compile iec61883 if libraw1394 is below
version 0.10.0.
* Internal bug fixes.
* Updated documentation.
Taybin Rutkin
>From: tim hall <tech(a)glastonburymusic.org.uk>
>
>I found your english a little hard to understand in this instance. What file
>format are you looking to store your rhythms in? MIDI? wav? something else? I
>would have thought you'd want to store them in a format which could easily be
>transferred between applications, but perhaps I am misunderstanding (?).
Hello. I figured out an analogy: A dish-washer machine has racks shaped
for holding different type of dishes. There is a place for cups and
glasses and a place for plates. To a place meant for a cup, one can
put a glass, a bigger glass, a plastic cup, a coffee cup.
I want make "dish racks" for percussion rhythms. I don't want force
what percussion sounds one eventually uses.
In a sequencer or an audioeditor I could set snap-to labels or marks.
E.g., a "dum" label for a bass percussion. Then I would save these
label sequences to files. A musician could select and load these
label sequences and snap-to the sounds to the tracks.
MIDI is good in that one could easily change the instrument assigned to
all "dum" labels -- in the case where all "dum" sounds are the same.
But we often want have slightly different sounds on each "dum".
MIDI is also good when we want test different rhythms quickly.
Maybe a hybrid system would work better: Named Snap-to labels
and the sounds assigned to the names. First, musician sets sounds to
"dum", "tak" standard labels. Second, musician finds the needed
rhythm. Third, musician renames the labels and assigns different
sounds to the new names. Old names could stay the same if musician
wants to test some other rhythm with the original default sounds.
Two utils are needed: the label track and a name-vs-sound list:
-------------------------
dum tak dum tak tak
-------------------------
dum bdrum.wav
tak snare.wav
Musician may add a new name manually to the list and rename the
labels, or may snap-to a sound to the track.
I would have implemented such a tool to Audacity but Audacity's label
track is not good because the labels cannot be edited. Only the track
"tape" under the labels can be edited: e.g., if one cuts out a piece from
the beginning, the whole rest of the tape moves forward and the label
timings are lost. Also, I could only add labels not remove or move them.
We should standardize the rhythm format so that the rhythms could be
used in any software. So, how to fit the above ideas to existing
systems? Not everyone want use purely my system, I'm sure.
Regards,
Juhana
Hello lists,
I am pleased to announce the initial release of Visecas 0.3.1.
Visecas is a graphical user interface (GTK+) for Ecasound
[http://eca.cx/ecasound], a software package written by Kai Vehmanen
which is designed for multitrack audio processing.
It aims to provide full access to all Ecasound's object by preserving
Ecasound's semantic (which means you do not edit tracks and regions but
chains and audio objects).
Please visit Visecas' webpage at http://visecas.sourceforge.net
This release includes the following features:
* start Visecas as you would start Ecasound (all arguments are
passed on)
* display and control chainsetup's status (valid, connected,
looped, etc.)
* add, remove, rename, mute, bypass chains
* add, remove, attach audio objects
* add, remove, control operators
* control chainsetup position via hscale
* display and control engine status
* edit Ecasound's preferences
Have fun!
Jan
I'm running an HDSP/Multiface on a planet ccrma Redhat 9.0 system. I'm having this problem when I restart alsasound. Below is the readout of `/sbin/service alsasound restart` ... Comments/hints?
Shutting down sound driver [ OK ]
Starting sound driver snd-hdsp [ OK ]
Starting sequencer [ OK ]
Starting sequencer driver snd-seq-midi [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: set_control:799: warning: iface mismatch (2/1) for control #23
/usr/sbin/alsactl: set_control:805: warning: name mismatch (Chn/ADAT Lock Status) for control #23
/usr/sbin/alsactl: set_control:784: failed to obtain info for control #24 (No such file or directory)
[FAILED]
Quite a long time ago now, Richard Bown and I decided we were going to
set up a sort of magazine website for musicians using Linux. It
wouldn't be a developer site or a pro-audio site or even particularly
a technology site, it would just be a site for individuals who were
interested in doing music.
We registered the name linuxmusician.com, and then, inevitably,
contrived to do absolutely nothing at all with it for the next
eighteen months. It became very clear very quickly, as always, that
we simply wouldn't have the time to write a substantial amount of
material for it. The subsequent appearance of the handy QuickToots
site at djcj.org also seemed to reduce the need for some of the
content we'd been hoping to write or solicit.
Recently though we decided that enough was enough, and that we should
just launch the damn thing with the few contributions we could make
plus a community article-submission facility and at the least give it
the chance to flop gracelessly instead of never being launched at
all. So one install of Mambo later, and we present
http://www.linuxmusician.com/
At the moment there is one (1) complete article on there, plus two
brief stubs of articles; there's a links page with hardly any links
yet, and a copy of the bownie.com Guide to Home Recording. We will
continue to post stuff that we come up with, but also if you take a
moment to register you are then very welcome to submit articles,
news, and links. It's not a complete slash/scoop-style community
moderation system; for example, there's currently no comment system
at all. But we're very open to ideas and concoctions that other
people might want to suggest.
Chris