what program can I use to dump midi in a sort of human readable
format? I mean in the real time, reading from midi port, I don't mean
the midi file conversion (even though I guess there's not much difference).
Here's why I need it, my (off topic) problem (a bonus Q:-): I just
connected yamaha drum pad (DD-55) to front panel (liveDrive?) of sb live
platinum. It actually sort of works (I couldn't get it work with older
versions of alsa) and after loading soundfonts and aconnect 64:0 65:0 I
can hear the drumpad, but only what it plays itself (demo, songs,
rhythms), when I hit the pad the sound is VERY soft, I can barely hear
it (at normal volume I can only barely hear crash cymbal and hi-hat). So
I'd like to check what is being sent out by the drum pad (whether the
volume is so low or there's some other problem). Of course, I'd
appreciate if anybody offered some insights into this problem...
TIA
erik
Hey y'all,
I've been cleaning house after a move and getting ruthless
about recycling old technology accumulated in various boxes
that I need to have a lot less of. And in an old parted-out
Macintosh Quadra 650 I ran across an Audiomedia II board.
I remember this board, and I'm pretty sure it's still fully
functional. (The Mac is definitely not.) So I thought I'd
toss it out here. I know it's pretty old, but if it's still
usable, maybe somebody on this list could use such a thing?
I'm just gonna throw it in the recycle bin if nobody wants
it. I'll be happy to send it anywhere, if you pay shipping.
I only have the board, no audio cables, but the outputs are
all rca jacks.
Write me off-list if you want it. If there's more than one
taker, well, I'll just have myself a little drawing. ;-)
Cheers,
~Jos~
Carl Hetherington:
> > If the audio thread gets killed by the watchdog, there is something
> > serious wrong. Which watchdog, vstserver's or jack's watchdog? Does
> > your machine freeze in ten seconds before the audio thread gets
> > killed?
>
> vstserver's, I believe. There's the message about the audio thread
> taking 10 seconds and being killed; the audio disappears during those
> ten seconds.
Seems like you are out of luck. Last thing to try is to start
the vstserver with the --nonrealtime option to see if it can
be the watchdog that is screwing things up. But I doubt it.
> > > If so, what could be different about the audio code's environment
> > > on Linux compared to windows? Any suggestions on how I can
> > > investigate the problem?
> >
> > If the non-audio part of your plugin behaves strange, everything can
> > happen (write wrong bits to memory used by the audio-part for example),
> > so...
>
> I guess you're right. Oh well. Is there anything sensible I can do to
> investigate the problem?
You can try to complain to the author(s) of the plugin, and tell them that
it does not work under wine...
--
hello list,
(sorry for cross-postings)
juan pampin has just announced the new "official" release of ATS.
ATS is a spectral modeling system based on a sinusoidal plus critical-band
noise decomposition. Psychoacoustic processing informs the system's
sinusoidal tracking and noise modeling algorithms.
Originally implemented in LISP using the CLM sound synthesis and processing
language, ATS has been ported to C in the form of a spectral modeling
library. This library, called ATSA, implements the ATS system API which has
served as foundation for the development of the ATSH graphic user interface.
ATS interfaces for Csound and PD have also been developed.
ATS software is distributed in open-source format.
there's a new web site with complete information at:
http://www.dxarts.washington.edu/ats/
including a paper with a detailed description:
http://www.dxarts.washington.edu/ats/ATS_theory.pdf
there's also a link to the sourceforge repository, where you can download
the packages:
http://sourceforge.net/projects/atsa
--
So, based on Fernando's and Malcolm's advice, I decided to quit fussing with the 2.6 kernels and stick with the 2.4.23 that I have working to do some recording last night. The band came over - we were set and ready to go. I hit 'record' to get an idea of the drum mix (we're submixing to stereo) - 3 seconds in, Ardour stops with an 80ms xrun! Arrgh! I sweated through the rest of the evening, fearing another occurence at 3:30 into a 4:00 song. Fortunately, everything went ok.
I guess I'm back to trying to figure out what's causing these long xruns, now under the 2.4.23 kernel.
Do most people shut off non-essential daemons during recording sessions, or do any other tricks? This is kinda frustrating, as the CPU load seems rather low (< 15% when the xrun happened). I guess I'll test out reiserfs and even ext2 to see if the filesystem is the culprit.
Thanks for reading the ramble,
Joel
> > I guess my main motivation for trying out the 2.6 kernel is laziness.
> > Just build the kernel and get the performance and ALSA without patches
> > or compiling extra stuff. At least, that was _supposed_ to be the way
> > it worked! I'll keep trying the new kernels, but keep the old faithful
> > 2.4 kernel around for recording.
> >
> > I'm _still_ curious about what causes the long xruns, though.
>
> New versions of alsa can be compiled with the "--debug=full" option (I
> don't think the current code in the kernel has that). That will enable
> you to tweak a proc variable to dump the kernel stack on each xrun, it
> is something like /proc/asound/card0/pcm0p/xrun_debug (for playback,
> same for recording in pcm0c). "echo "2">/proc/.../xrun_debug" will turn
> reporting on. You will get the stack traces in /var/log/messages.
>
> Not that you will immediately know exactly what has to be done to get it
> fixed, of course :-)
>
> IMHO stick with 2.4.x, in my tests 2.6.x is not even close to being
> ready for pro audio work. It will get better but it will take some time.
>
> -- Fernando
>
>
Greetings:
I'm trying to figure out how to write a grub.conf that will allow a
choice between booting into Planet C's RH 8 or RH 9. Here's what I know
about the drive structure:
For RH8:
/dev/hda1 /boot
/dev/hda2 /
/dev/hda3 /swap
For RH9:
/dev/hda5 /boot
/dev/hda6 /
/dev/hda7 /swap
A single drive has been partitioned to accommodate both systems. The
RH8 install was the first installation, and in the process of installing
RH9 grub was rewritten for it (and not for the RH8 partition). So, how
do I indicate the choices ? Here's what I'm thinking about for an edited
grub.conf :
default=0
timeout=10
splashimage=(hd0,4)/grub/splash.xpm.gz
### RH9
title Red Hat Linux (2.4.26-1.ll.rh90.ccrma)
root (hd0,4)
kernel /vmlinuz-2.4.26-1.ll.rh90.ccrma ro root=LABEL=/1 hdc=ide-scsi
initrd /initrd-2.4.26-1.ll.rh90.ccrma.img
### RH8
title Red Hat Linux (2.4.19-1.ll)
root (hd0,0)
kernel /vmlinuz-2.4.19-1.ll ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.4.19-1.ll.img
Is this kosher ? What will happen if it's incorrect, and what should I
do if grub fails ? How do I specify that I want RH8 to be the default
system ?
Btw, when the RH8 partition is mounted from RH9 (mount /dev/hda1
/mnt/rh8) we discovered that /mnt/rh8/etc/grub.conf is a broken link.
I'm sorry about the confusion, but I've never edited grub.conf.
Best,
dp
Hi,
I just wanted to share this success story (kind of), especially with
Dave Phillips.
When my desktop PC (more precisely: its elitegroup mobo) suddenly ended
up in smoke on Thursday [somewhere in the middle of my diploma thesis
:-((] I had to revive my old HP Omnibook 4150.
This laptop has a "NeoMagic NM256 piece o' crap" (citing Dave[0])
soundchip which I had not been able to use with ALSA up to then.
I decided to upgrade the installed Debian version from Woody to Sarge
(current testing) and in doing so I decided to give Debian's 2.6.5-1-686
kernel image a try.
Of course, alsaconf tried to load the nm256 driver for the NeoMagic chip
which failed as expected.
As described in [1] I changed /etc/modprobe.d/sound to contain the
following lines:
----8<-----
options snd-cs4232 port=0x534 cport=0x538 mpu_port=-1 fm_port=0x388 \
irq=5 dma1=1 dma2=0 isapnp=0
alias snd-card-0 snd-cs4232
alias sound-slot-0 snd-cs4232
----8<-----
An 'update-modules' updated /lib/modules/modprobe.conf and suddenly I
was able to start ('/etc/init.d/alsasound start') and use ALSA!
Alsa-lib is version 1.0.4-1, drivers are version 1.0.4rc2.
I'm quite sure I had tried this before with a 2.4 kernel without
success.
However, I'm really pleased now (apart from the death of my desktop PC).
My digital camera (HP photosmart 715) is fully functional via USB using
gphoto2 or flphoto.
My Netgear Cardbus Ethernet adapter is recognized and automatically
configured via DHCP.
I still have to find out whether the alsa configuration survives a
suspend.
Maybe I'll also test jack performance later.
How can I find out whether my kernel has capabilities support builtin?
cat /proc/sys/kernel/??
Now I'm thinking of buying an external adapter which lets me use my
IDE harddisk (the one from the desktop computer) via USB.
(Yes, I have a backup, but it's two days old and it's not complete.)
Experiences anyone? (Slightly off-topic)
I've got to get some sleep now.
Cheers,
Jan
[0]http://eca.cx/lau/2004/04/0494.html
[1]http://alsa.opensrc.org/index.php?page=HP+Omnibook+4150
Hello,
I need to convert my old tapes to digital audio. They are
stereo recordings, and I want to keep it stereo. Probably
I will need a card which enables me to actually record it
as stereo: I mean, my current card (Soundblaster AWE64)
has a LineIn, which only seems to record mono.
What I would want is a card which would actually have
TWO different holes for the left and right channel to
record. Would you suggest a particular one?
Or is there a card with a stereo LineIn? Which cable will
I need to go from the tape player into the card?
Thank you
JAn
