"Is this thing on...?"
(Seems like at least one message was lost, and it's been *very*
silent for a while...)
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
--- http://olofson.net --- http://www.reologica.se ---
hello to evey body,
i'm new to this list.
I'd like to know more about Unified Audio PLugin Architecture.
I will begin a practical on this topic in mars.
where can I register to a mailing-list or forum or...
I' also looking for papers about audio dynamic
compression/expansion/limiting.
Does anybody have some good links on this topic?
(I'm not looking for "compression for the newbies" but some more in-depth
considerations.
like analog compressor modeling.... aliasing due to non linear
processing.....)
thanx
remy muller
http://membres.lycos/mdsp/
Hi,
for a project at our radio station I need to simultaneously record two
signals coming from an Amek DMS mixer.
The signals are digital optical S/PDIF (which I assume is the same as
TOSLINK ?).
I am looking for a card or a combination of two cards that would allow me
to record both these signals at the same time under linux. Of course I'd
like to go for the cheapest stable solution possible :)
I've been looking at specs of the Hammerfall Light, it seems to feature
more than one ADAT input port, which from the docs looks to be the same
type of connector as optical spdif. I'm just not very sure from the docs
if this will really work; ie if one Hamerfall Light can record two spdif
signals simultaneously.
One Hammerfall is about in the right price range, two is probably too
expensive :)
So, basically my questions are:
a) will one hammerfall record both optical spdif signals at the same time
?
b) what other, cheaper, card is there that can record an optical spdif
input ? (I looked at some obvious choices, the hercules cards aren't
supported well enough and the sblive cards only take coaxial optical)
Thanks in advance,
Thomas
The Dave/Dina Project : future TV today ! - http://davedina.apestaart.org/
<-*- thomas (dot) apestaart (dot) org -*->
I feel like I'm at something you always say you need more time
Well I'll stay right here and I'll wait for good
until I find a love worth mine
<-*- thomas (at) apestaart (dot) org -*->
URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/
>I think they should probably be treated as 2 separate databases from
>the viewers standpoint (even though the data would be stored in the
>same one, there would be 2 links). "Linux audio technician database"
>sounds good for the job related side of things "Find a Linux audio
>technician near you, today!" :)
>Perhaps "Linux audio community database" for the "network the Linux
>audio folks" side of things.
Well I have changed the name. Now it is "Linux audio professional
support & contacts database". I would prefer to keep it as one page just
to make things easier for me to manage. While I would love for this site
to become extreemely popular and require serious commitment I am
pragmatic that this probably won't happen in the next couple of years.
Splitting the page up at this point seems like more work than neccessary.
>He he.. The Linux audio dating service :) I wonder how many Linux audio
>gals are out there.. Maybe if they saw some of our pictures we'd have
>some converts.. or maybe not. I think it would be nice to have a way to
>put a photo, but perhaps this could also just be a link someone could
>put in the specifics field
I'm working on adding these things now.
>(BTW, would it be more appropriate to make
>that a text field rather than multiple lines?).
I thought about that but I decided multiple lines provides more scope
for presentation purposes. I expect people to eventually treat it
similar to an email signature.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
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
Out of order forwarding... This should have gone to the list also...
Hi,
>
>>* I don't know if other types of plugins are applicable to this, but
>> since the sidechain is a separate plugin you could make _any_ plugin
>> sidechain aware. mmmm audio controlled room-size for reverbs...mmmm
>> :-D.
>
>
> Ahh, theres a misundersantding about what sidechains do here, they really
> are just an audio stream.
Hmmm, how do you recon? A sidechain for a compressor may be an audio
stream, but it's the "control" behaviour of that stream that is of
interest, right? That should mean that it would be possible to extract
just the behaviour and only distribute "that".
But I may very well be misunderstanding, this is mostly theory for me, I
haven't had much real practice with this kind of stuff.
>
>>Top priority is a LADSPA stereo delay, I couldn't find one in Steves
>>collection.
>>But it would also be nice with:
>>- stereo autopanner
>>- auto sweeping filters.
>>Apologies if these infact are available and it's just my poor eyesight.
>
>
> What do you want from a stereo delay? There is an left-centre-right
delay,
> but thats actually a mono delay that takes stereo input and pans the
> result. A stereo delay would be easy to implemnt, what controls do you
> want?
An example:
Recording a guitar in mono (Sounds dull). Easy way to make it more
lively is to add an stereo effect, delay is my preference.
For the above example a mono-->stereo plug would suffice, but
stereo-->stereo is more versatile. Muse handles the mono->stereo
conversion internally.
As for parameters I'd like separate delays for left and right, apart
from that I'm open for suggestions... I'm no pro, I learn as I try :).
>
> There is an auto-phaser (sweeping allpass filter), but no auto wah
> (sweeping bandpass), or auto panner, true. I tend to build things like
> that out of SSM or pd. But there should be complete plugins.
Ya, working mostly in MusE I'm somewhat limited in the number of
solutions I can try. Currently MusE only supports basic features (pretty
much modeled after Cubase).
/Robert
Sorry, replied direct to Robert, not list.
----- Forwarded message from Steve Harris <S.W.Harris(a)ecs.soton.ac.uk-----
Date: Fri, 10 Jan 2003 09:25:32 +0000
From: Steve Harris <S.W.Harris(a)ecs.soton.ac.uk>
Subject: Re: Sidechains, was Re: [linux-audio-announce] [ANN] swh-plugins 0.3.4
To: Robert Jonsson <robert.jonsson(a)dataductus.se>
On Fri, Jan 10, 2003 at 09:47:26 +0100, Robert Jonsson wrote:
> >SC4 is more-or-less like SC3, but has no sidechain and a subtly different
> >algorithm. The sidechain was confusing hosts.
> >
>
> Yes, I was wondering how the 3<-->2 port sidechain compressor plugin
> would be handled in hosts...
The answer is 'badly'. ;)
> What if the sidechain was a separate ladspa plugin that in turn uses
> some ipc mechanism to communicate to the plugin being controlled?
> I have no idea what kind of ipc is best for this, named pipes seem easy
> but they are probably slow, yes?
Pipes are non-deterministic, so banned in LADSPA. The only one thats an
option is shared memory.
> By using one of the controls of the ladspa plugin to select which
> sidechain "channel" (e.g. 1-10) they should send and receive on (much
> like a comm-radio) you could have several different sidechains up and
> running simultaneously.
Its an interesting idea.
> This construction has a number of interesting side effects (pun not
> intended):
> * 1-n setups can be produced, one sidechain can control several effects.
> * Atleast with named pipes the control would be application agnostic.
> The sidechain would not need to be used in the same host as the effect
> plugin.
The same is true of SHM, but if the hosts are not running in sample sync
all hell will break loose.
> * I don't know if other types of plugins are applicable to this, but
> since the sidechain is a separate plugin you could make _any_ plugin
> sidechain aware. mmmm audio controlled room-size for reverbs...mmmm
> :-D.
Ahh, theres a misundersantding about what sidechains do here, they really
are just an audio stream.
> Any thoughts?
Neat idea. Kinda evil though. Very tempting...
> Top priority is a LADSPA stereo delay, I couldn't find one in Steves
> collection.
> But it would also be nice with:
> - stereo autopanner
> - auto sweeping filters.
> Apologies if these infact are available and it's just my poor eyesight.
What do you want from a stereo delay? There is an left-centre-right delay,
but thats actually a mono delay that takes stereo input and pans the
result. A stereo delay would be easy to implemnt, what controls do you
want?
There is an auto-phaser (sweeping allpass filter), but no auto wah
(sweeping bandpass), or auto panner, true. I tend to build things like
that out of SSM or pd. But there should be complete plugins.
- Steve
>Perhaps just adding a couple check buttons to the database:
>
>[X] Available for professional Linux Audio consulting
>[X] Available as a Linux audio community node
Easy enough to add.
>There could then be 2 entry points to the
>database, one catering to the company or individual looking for a Linux
>audio consultant and another for those wanting to connect with other
>audio developers. The latter being more losely based since one would
>not necessarily need to be a professional to just meet others.
I'm still looking for the appropriate name for this db. I want it to
provide all the functionality that we need to allow users and developers
to do real networking. Whether that is for paid work or just to arrange
meetings with people in an area you may be travelling to/through.
I think it makes sense that as part of a comunity that is based on
openness we provide a way for people to get a little background info on
us. I also hope that this database will present one more level of
professionalism to the Linux audio developers public image.
>I like the idea of having an email proxy so that one could hide their
>email address (as an option) and a form could be provided that would
>email the user from the internally stored address. I think the idea of
>Spam might scare away some people from putting their info in the
>database (like me).
I can make it more spammer unfriendly. I'll think about how. Currently
there is a form mailer provided to allow people to contact directly from
the site. Since setting this up for my business site a couple of years
ago it has proven to be a good way for people to contact me. So I have
provided this feature for the db also.
That is possibly the most useful feature on the site. Anyone (not tested
with lynx) can contact you directly.
>Perhaps this might already be the case (haven't tried submitting
>anything yet to the database) but having the street address info be
>optional is good (just city/country is probably sufficient in many
>cases) as well as phone number and any other items related to privacy.
>Indicating optional and required fields would be nice on the entry >form.
Currently the only required entry is an email address. Soon I will have
a proper login faciltiy so there will also be a password required.
>Maybe a resume URL would also be good, so if one is browsing through
>lots of entries they can quickly jump to individual's resumes.
I figure this belongs in the specifics column. I will make it parse
these entries for urls and automatically create links. On that note
would anyone find it useful to have a photo column?
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
http://plugin.org.uk/releases/0.3.4/
Hods of changes, including:
* Bugfixes to GSM sim (Pascal Haakmat)
* Bugfixes to FM osc (Pascal Haakmat)
* Bugfixes to audio divider (Nathaniel Virgo)
* Added another compressor, SC4, stereo, no sidechain
* Added lookahead brickwall limiter
* Added L/C/R delay (requested by Marek Peteraj)
* Added Giant flanger (kind of requested by Patrick Shirkey)
* Added DJ Flanger (actually requested by Patrick Shirkey)
* Should now compile on FreeBSD
* Fixed syntax error in RDF metadata, works with Bob H's jack-rack now
I've updated the AUTHORS list, but I've undoubtedly forogtten people, so if
youre not in there and should be give me a shout.
SC4 is more-or-less like SC3, but has no sidechain and a subtly different
algorithm. The sidechain was confusing hosts.
The limiter has up to two seconds of lookahead, so can be very gentle.
The L/C/R delay might be a bit familiar to Korg Trinity users ;) I haven't
used it much bet it seems pretty cool.
The giant flanger was a mistake, but I left it in anyway.
The DJ flanger hjas controls for LFO period (instead of frequency as you
would have in a synth) and you can resync the LFO by clicking a toggled
control*.
- Steve
* This reminds me, there would be a use for a MOMENTARY hint (implying or
requiring TOGGLED) in LADSPA, that meant that a control port should only
be held high while the UI control was held down, otherise you have to
double click reset controls, which is confusing.
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!