Hi all,
I was looking for a good, up-to-date documentation pointer upon software features provided by alsa. But I'm new to this architecture and I might be "intoxicated" by some kernel streaming architectures : is there a kind of hardware abstraction with ALSA, e.g. features that are managed by the software at usr or kernel level, in a +/-transparent way, when the HW does not provide them ?
My understanding is that Alsa does not provide multiple device open (a second open can be blocking, or return with an error, but won't succeed, as no sw mixing is available).
is there anything that can be emulated by alsa on user request, when the hw cannot ? (for instance frequency change, frame conversion (n channels to m channels) etc...).
How would you implement such thing ? With a kind of abstraction layer daemon, that exports the same api but perform missing hw features ?
Could the LADSPA plugin architecture be a solution to implement multiple device open ?
tx
Marc.
Hi all,
I happen to be both a linux programmer and a guitar freak. Off late
the guitar industry has seen these amp simulators some into being: line6
POD, Vamp and the likes... i was wondering whether i could build my own
such amp simulator. Could anyone out here suggest me how i can do
this...i mean how do i model amps...the algorithms...any info??
thanks in advance.
regards,
vishal
Hi.
Today I relased ZynAddSubFX 1.0.5.
It is a powerfull software synthesizer for Linux.
News:
- The bug that crashed ZynAddSubFX if you change
some effect parameters, it is realy removed (I forgot
to update the file before upload)
- Other bugfixes and code clean-ups
- Added a Global Filter to SubSynth
- Added keyresponse limits to Part
- Added presets to Effects
- The fade is smaller on high frequecy content
and larger on low frequecies; so you'll don't hear
starting clicks on basses and audible fadeins on
higher pitched sounds
- Added tunnings to Reverb: you can choose
Random of Freeverb
If you do something interesting with ZynAddSubFX (nice
instruments, for example), please send me parameter
files(master settings - *.mas_zyn or instruments -
*.ins_zyn or banks) and (perhaps) midi files.
You can download it at:
http://zynaddsubfx.sourceforge.net
or
http://sourceforge.net/projects/zynaddsubfx
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Hello,
I've been watching the mail on this list for some time. I've looked at as
much documentation on the web as I can find. From alsa's web site to the
linux audio developers web site. What I would like to know (or see in a
FAQ or HOWTO) is how to setup a linux pro audio system. With different
levels of price/performance issues. Things like:
sound cards
necessary external equipment (amplifiers/interfaces)
speaker systems
cpu cases with low sound
midi interfaces
usb interfaces
dat interfaces
I'm pretty savvy when it comes to computer hardware but the audio hardware
is where I'm lacking knowledge. Currently I have a Korg Triton keyboard
and a SoundBlaster Live! card. I'm looking at upgrading to a more
professional quality setup to handle:
multi-track recording/mastering
realtime synthesis
audio sound/music development/programming
possibly portable (19" rack mounted stuff) for live performance
I've seen discussions on Digital Audio cards like the RMU Hammerfall and
Digi series and the MidiMan Delta series. Some have S/PDIF interfaces and
other digital interfaces. What and how do connect to these? What
equipment is necessary/recommended? How do you choose one card from the
other?
Is there a good web page to find this information? Should there be one?
A nice page describing various setups for different levels of pro to
semi-pro audio systems would be handy.
What do you guys suggest?
Thanks,
Matt Gerassimoff
>AFAIK no LA-based recording or post-production studio is using Linux on
>a daily basis. We need to score a win similar to the Linux wins in the
>film industry. A hit song made with Linux software would certainly do
>the trick (not that I'm a fan of popular music, but it is the big
>market/money that counts for the pro-audio guys).
I don't know if that's so true actually. The big movies that use
technology designed on top of Linux have to sync their audio somehow. If
they are doing all the rendering and post production in Linux envs then
they must have some very powerful audio functionality in the apps they use.
>I'm reminded of Paul's observation of how small the industry
>really is. Considering the narrowness of the market I'd wonder why the
>major manufacturers would do anything that might put the jinx on their
>cash flow.
Because they may not like having to work in the paradigm that has been
forced on them. It could actually be that these companies actually do
care about their community and resent having to work against the natural
flow of the universe in order to put food on their plates.
I'm not sure. How many of the developers who contributed significantly
to the current selection of professional audio software did it because
they love the results of their work and how many did it because they
want the cash?
In the ideal world we make money from doing what we enjoy. I would like
to think that the people creating for musicians have more of a solid
grasp of that ideal.
I don't like to think that the industry as it currently functions has
been created by money hungry musos catering to the pop market.
If that is the case then maybe I don't want to use these products that
they want to sell me and they should stay the hell away from open source
for fear of turning to dust ;)
--
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
Ron Kruper said:
>The MMA is a trade association, akin to a standards body like the AES.
>Do you also object to the fact that AES, IEEE, etc, charge membership
>dues, and that they too hold evolving standards discussions for
members >only? How does the fact that this happens to be _software_
standard >mandate that dues be waived?
I wasn't suggesting that dues be waved but that they may not be
neccessary. Paul makes a point in terms of anittrust legal fees but
surely the lgpl solves that problem.
>This isn't about being for or against open source, or a lack of
>understanding. This is about recognizing that developing and
supporting >a standard requires legal work, marketing, publications,
etc, and that >these cost money. Call it "old economy" if you must, but
if you want to
>interoperate with the major companies in the industry, the MMA is forum
>where they gather, and the MMA has a cost structure associated with it.
Where's the legal work involved in applying for example the lgpl to this
standard? Sure there is investment in the marketing and publications
side of things. We all know that the mass market needs it's eye candy.
But there should be very little legal fees associated with a truely open
standard.
If companies need to purchase the documents and specs to feel that it is
worth something then they should be the ones paying for the goods.
However I don't won't to appear negative towards the workings of the
MMA. I want to suggest that the open source community has been working
in the direction you are heading for a while and that maybe the MMA
should be looking into why it is working so well. Which is possibly the
same reason you are here now.
Linux has proven to be the perfect medium for hardware manufacturers to
get an equal footing. The truely large corporations are investing big
bucks into GNU/Linux because of this. It makes sense that any
professional who makes their business around computer technology would
want to be here too.
>IMO the *worst* possible scenario is that the commercial companies
>(many of whom are a one man show) decide that they want to join the
>MMA, while a sizeable group of others decide to persue a parallel
>effort. That gives us 2 standards, and nobody wins.
I'm sure everyone agress this is definitely something we don't want.
The developers who created the current music software industry must have
felt the crush when PC's first arrived, well it's happening again but
this time it's not forcing you into a proprietry business model. This
time you actually have a choice.
Anyways, it's good to see you and others like yourself arriving here.
--
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
>>>
Can you explain to us exactely what the MMA is offering in exchange of this
money?
...
What protection does the MMA provides?
<<<
MMA provides anti-trust protection. If the major commercial vendors go off
in private and work in collusion to influence consumer choice, that is an
illegal trust. The trade association gives us a forum to talk among each
other, and *everyone* in the industry, with legal protection.
>>>
I can understand why steinberg and emagic
(for example) would prefer to hide a standard war behind closed doors
instead of on a public mailling list.
<<<
Mainly because companies act differently and say different things when they
know customers might be watching. Reality of business.
-Ron
>>>
In this context it's seems a little ridiculous that the MMA is requiring
members of the mailing list to sign on with $450.
<<<
The MMA is a trade association, akin to a standards body like the AES. Do
you also object to the fact that AES, IEEE, etc, charge membership dues, and
that they too hold evolving standards discussions for members only? How
does the fact that this happens to be _software_ standard mandate that dues
be waived?
>>>
Applying closed methods of communication, or at least requiring a sum of
money to be paid to have discussion rights is the equivalent of telling
us Open Source developers that either you don't understand what we are
doing and why or you totally disagree with the paradigm we work in.
<<<
This isn't about being for or against open source, or a lack of
understanding. This is about recognizing that developing and supporting a
standard requires legal work, marketing, publications, etc, and that these
cost money. Call it "old economy" if you must, but if you want to
interoperate with the major companies in the industry, the MMA is forum
where they gather, and the MMA has a cost structure associated with it.
Also, the plan is for this process to not be completely closed. We're
working on a process whose openness is new to the MMA, but similar in nature
to other standards organizations. The current plan is to have 4 phases:
[1] Requirements gathering. This will be open to any developer who wants to
register on an email reflector. This phase will start as early as next
week, and will last several months, I suspect.
[2] Design. This will be open to MMA members only. If you want the legal
protection that the MMA provides, and you want somebody else to pay for
"stewardship" of the spec, then it's worth joining. Even some open-source
developers sell products, and those who do will recoup their cost after
selling a very small number of units.
[3] Review. This will be public like phase 1. We'll probably have several
iterations of 2 and 3.
[4] Adoption. Once again, private to MMA members only.
IMO the *worst* possible scenario is that the commercial companies (many of
whom are a one man show) decide that they want to join the MMA, while a
sizeable group of others decide to persue a parallel effort. That gives us
2 standards, and nobody wins.
-Ron
>>>
person making a living writing audio plugins might feel a little nervous
about something like the development going on with LADSPA or XAP. Not to
mention how companies like Steinberg and Cakewalk are going to feel when
Ardour 1.0 hits the net.
<<<
I can't wait to see it. Seriously! Competition is good, it keeps everyone
sharp, on their toes and innovating. If the economics of open source and
Linux mean we need to adapt our economics, then of couse we'll need to adapt
or die.
The thing is, our average customer is not incredibly PC savvy, so have them
be their sysadmin won't really fly. Like or it not, Windows and Mac O/S are
still much easier to set up and support for the "average joe", which means
they are easier for us to set up and support.
Likewise, new customers want sexy features. Is Ardour 1.0 going to be as
sexy, full-featured and stable as existing commercial products which are on
version 5 or beyond? Again, it's all about competition. Prospective
customers will get to choose between "free" and "fuller featured." Of
course over the time you guys will gain ground on the second point... <g>
-Ron
> digidesign, we had the whole group in that room. i used to have
> friends who could have bought most of the companies represented there
> out of their own personal accounts :)) people planning on getting rich
> in this field are out of their minds.
In this context it's seems a little ridiculous that the MMA is requiring
members of the mailing list to sign on with $450.
Wouldn't it be better for them to either start up an open mailing list
or just do it here?
I get the impression that the forces involved in making this happen (Ron
Kruper and other lurkers may want to speak up here) are missing the
point of open source development. Sure it was ok to do what you seem to
be doing with this new standard 20-30 years ago when the MIDI standard
was created. Times have changed and now the world has open source
development.
Applying closed methods of communication, or at least requiring a sum of
money to be paid to have discussion rights is the equivalent of telling
us Open Source developers that either you don't understand what we are
doing and why or you totally disagree with the paradigm we work in.
Look at the development of the Kernel these days. In a total of 1000
(approx) highly active developers roughly 500 of them are employed by
major corporations like IBM, HP, Intel, AMD... The list is obviously
very large.
It is high time that the professional audio community got involved in
the open source process. Your absence has become extreemely noticable.
By attempting to make a protocol/specification that aims at providing
cross platform functionality you cannot justify using closed, old
economy methods of communication.
Not when there is a large number of developers who are already
communicating on mass in the Open source community.
If you want an example of this paradigm working in an audio context you
only need to look at the port-audio project. If you want to see the
power of the Linux Audio Developers then the best example is JACK. We
have created a protocol that neither M$ or Mac developers can provide a
better option.
If it is the name of the mailing list that is putting you off from being
involved around here, just ignore it. All we are doing is making
machines work. The Linux part plays a very small role in the wider scheme.
Instead of spending the money on hiring someone to do the book keeping
and running the mailing list etc... You could be channeling that into
Open source. If those other companies can justify it then why can't you?
--
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