Hi,
I'm looking for a platform for signal processing, who can be used in
command line mode ( matlab like ), but is based in low level code ( c or
c++ ), and block based signal chain. I wish i could find some kind of
front end to any standard plugin types.
It was desirable also that the standard plugin used is able to handle
data other than audio ( not so hard, i believe ), and in other domains
than time ( e.g. frequency, statistical, and weirdo like domains ).
Preferably it should have support for gui also, basically for plotting
graphics only.
thanks all,
Fabio
With help from a few kind people here, I got my ALSA sound working
with xine. However, this was at 8 bits of color depth, and the
video picture was not too good. So I tried 16 bits, which made xine
fail, as it did MPlayer. But at 24 bits, MPlayer came to life and
showed a picture that was (probably) as good as it gets.
But... MPlayer doesn't like ALSA sound. It tries to keep video and
audio in sync for 10 or 15 seconds; then it gives up and goes silent.
It says my system is too slow; one of the reasons might be slow
audio.
So I thought I'd try the via82cxxx_audio module that is in the
"official" 2.4.20 kernel.
But... I can't insmod the module. It complains
/lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o: insmod /lib/modules/
2.4.20/kernel/drivers/sound/via82cxxx_audio.o failed
/lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o: insmod via82cxxx_audio failed
(No, neither syslog nor dmesf offers more information.)
Am I missing a /dev? Which one?
Thank you,
Sakari Aaltonen
Hi,
I just bought the obove card (an ES1969 Solo-1 apparently), in order to do
MIDI, but I cant seem to get anything to work.
$ cat /proc/asound/Solo1/midi0
MPU-401 (UART)
Output 0
Tx bytes : 1400
Input 0
Rx bytes : 0
Buffer size : 4096
Avail : 0
Overruns : 0
But I tried connecting the external midi device to ASM with kaconnect and
nothing appearing in the log window and the number dont change in proc
when I press keys on a keyboard.
I've replaced the joystick->midi cable and I'm not sure what else to try.
Help!
- Steve
just a quick question (hopefully). In ardour I've been able to get a track to
playback while recording another track, but I can't seem to play more than
two tracks at a time, nor am I able to play two tracks while recording
another. Is this a ALSA/soundcard limitation (I have the intel 8x0 series)?
Okay, I lied, one more quick question... I've had ardour not play back samples
when recording and I can't seem to put my finger one what causes it to mute
the sample playback and what allows it to do duplex.
Thanks all
Jonathan
Just to let everyone know, I have created a new mailing list for the
OMRL at my studioconsul.net domain.
To subscribe, send a blank email to: omrl-subscribe(a)studioconsul.net
To unsubscribe, send a blank message to:
omrl-unsubscribe(a)studioconsul.net
To send messages to the list, send messages to: omrl(a)studioconsul.net
You will need to confirm your subscription or unsubscription to/from
the list. I also still need to figure out how the archiving system for
this list software works.
This is just a quick and dirty mailing list for now, so once I get a
server and the OMRL domain up and running, I will probably migrate it
over there. That should not be too difficult, though.
See you on the new list. :)
Regards,
Darren Landrum
Hi,
I asked about this two weeks ago but got no responses. I'm hoping
this time I hear something back from other owners of the same hardware.
I recently purchased an RME HDSP 9652 card. The card is working fine
for audio, but the MIDI interface is a timing disaster. The interface
works, but won't keep time. A 2 minute song is Rosegarden takes abut
2:45 to play every time. You can hear how the HDSP isn't delivering
closely spaced MIDI events together, but is sort of smearing them out.
My machine is set up using the PlanetCCRMA system. According to
Synaptic my Alsa driver is from CVS:20021216. Jack is 0.44. This machine
works just fine with the MidiMan 2x2 interface. No timing problems at
all.
Has anyone else purchased this card? Used the MIDI interface on this
card? Gotten better results with this card?
Can anyone suggest how I could go about fixing this myself? I'm not a
programmer, so really hacking the code is doubtful, but this driver is
acting like there is just a basic mistake somewhere. Possibly I could
find it if I knew where to look.
I hope someone will respond to this email so we can get something
going to get this fixed. I really need this interface to operate soon.
Thanks in advance,
Mark
* Really fixes the UID clashes.
* Includes changes to make it build on ia64 and mips, thanks to Anand
Kumria.
I will now be walking around with a paper bag over my head for the next
few days.
- Steve
http://www.m-audio.com/products/m-audio/radium.php
Has anyone tried using this keyboard with linux, yet?
I was about to buy an Oxygen 8, because I've read about several people
in the LAD, LAU, ALSA community using them with linux successfully. But,
then I saw this new Radium controller. It has 61 keys to the oxygen's
25, the same 8 knobs, pitch and mod wheels, and adds 8 sliders to the
oxygen's 1.
Would it be too far fetched to think that this would work as easily with
a linux box as the Oxygen does? I would be very happy if it would.
Thanks,
Eric Rz.
The were some bugs in 0.3.4 so I'm releasing again. Sorry.
* UID clash with flanger and l/c/r delay [serious] - spotted by Bob Ham,
thanks
* SC4 had the wrong label [mild but anoying]
* autoconf script wasn't obeying CFLAGS [mild but anoying]
I believe that SC4 and the lookahead limiter might be causing problems
with some hosts as they have control outs. If you spot problems with these
and think its the host, please contact the author.
I know that ecasound and jack-rack handle it fine.
- Steve
1. A short summary of changes
Support for JACK and LADSPA 1.1 added, more intelligent runtime
parameter selection, ECI licence changed from GPL to LGPL,
new NetECI client API, ecasound emacs mode added, largefile
support, new resample, reverse and typeselect audio objects,
new peak amplitude chain operator and new utilities ecalength,
ecamonitor and ecasignalview.
---
2. What is ecasound?
Ecasound is a software package designed for multitrack audio
processing. It can be used for simple tasks like audio playback,
recording and format conversions, as well as for multitrack effect
processing, mixing, recording and signal recycling. Ecasound supports
a wide range of audio inputs, outputs and effect algorithms.
Effects and audio objects can be combined in various ways, and their
parameters can be controlled by operator objects like oscillators
and MIDI-CCs. A versatile console mode user-interface is included
in the package.
Ecasound is licensed under the GPL. The Ecasound Control Interface
(ECI) is licenced under the LGPL.
---
3. Changes since last release
Although over a year has passed since the last major stable
release, ecasound development work has not stopped. To put things
into perspective, a diff between 2.0.0 and 2.2.0 takes about
1.7MB of space. Considering the whole 2.2 codebase is just
over 2MB, this is quite a lot! In the future there will hopefully
be much more frequent releases. Here's a list of most notable
changes:
* Intelligent parameter configuration. Instead of one set of
default parameters, ecasound lets user specify different parameters
for three predefined profiles: real-time, real-time-low-latency and
non-real-time. When starting processing, ecasound will automatically
select and use most suitable profile for the given configuration.
Ecasound will not only consider the types of objects, but also the
runtime environment: whether it is possible to lock memory, to use
RT-scheduling and so on.
* The Ecasound Control Interface is now licensed under LGPL.
In addition, the ECI implementations are now standalone, and do
not require linking against libecasound and libkvutils. Only
thing needed to run ECI apps is to have a working ecasound
executable installed.
* JACK support added. This is a major new addition as it involved
making relatively large changes to the ecasound engine.
* Up-to-date support for ALSA-0.9 and LADSPA-1.1.
* Effect preset improvements. Support for parametrized presets
has been improved. For instance it's now possible to write
a wrapper effect preset for a complex ecasound effect
or LADSPA plugin, and only publish a subset of original
effect's parameters.
* The disk i/o buffering subsystem that was introduced
in ecasound 2.0 has been integrated more closely to
the ecasound engine leading to better performance and
reliability.
* NetECI API. Ecasound now has a daemon mode that allows
multiple clients, using the NetECI protocol, to connect to
a running ecasound session. A proof-of-concept client,
ecamonitor, is included in the package. It can be used
to monitor ecasound session status from a separate console.
This is especially useful in combination with ecasound's
console mode user interface. The console interface can
be used for control and the NetECI monitor client for
getting real-time status information. In addition,
NetECI can be used with all ECI apps.
* Ecasound.el, an emacs ecasound mode and a Lisp ECI
implementation.
* Largefile support for reading and writing audio files larger
than 2GB.
* New audio object types: JACK, resample, reverse, typeselect.
* New chain operators: peak amplitude monitor
* Utilities: ecalength and ecamonitor added, ecasignalview
totally rewritten.
* New ECI implementations: Lisp, Perl and PHP (the last two
are not included in the main ecasound package)
Full list of changes is available at
<http://www.wakkanet.fi/~kaiv/ecasound/history.html>.
---
4. Interface and configuration file changes
* Command line options: 2.2 is backward compatible with
2.0 releases, so old scripts and .ecs files should
continue to work. See ecasound(1) for more info.
* Ecasound Interactive Mode (EIAM): No changes to the commands
available in 2.0 releases. See ecasound-iam(1) for more
info.
* Library interfaces: Major changes in all library interfaces.
Direct use of these libraries is no longer encouraged.
The ECI and NetECI APIs are preferred for developing new
applications on top of ecasound.
* Ecasound Control Interface (ECI): No interface changes.
* The ~/.ecasoundrc config file is no longer used. The
new location is ~/.ecasound/ecasoundrc. As there's now
a separate global configuration file, it is no longer
necessary to duplicate all config variables in the
user config files. See ecasoundrc(5) for further info.
---
5. Links and files
Web sites:
http://www.eca.cxhttp://www.eca.cx/ecasound
-
http://www.alsa-project.orghttp://jackit.sourceforge.nethttp://www.ladspa.org
Source and binary packages:
http://ecasound.seul.org/downloadhttp://ecasound.seul.org/download/ecasound-2.2.0.tar.gz
Distributions with maintained ecasound support:
Agnula - http://www.agnula.org
Debian - http://packages.debian.org/stable/sound/ecasound.htmlhttp://packages.debian.org/unstable/sound/ecasound2.2.html
DeMuDi - http://www.demudi.org
FreeBSD - http://www.freebsd.org/ports/audio.html
Gentoo Linux - http://www.gentoo.org
PLD Linux - http://www.pld.org.pl
PlanetCCRMA - http://www-ccrma.stanford.edu/planetccrma
SuSE Linux - http://www.suse.de/en
Note! Distributors do not necessarily provide packages for
the latest ecasound version.
--
http://www.eca.cx
Audio software for Linux!