Guys,
This answer appeared just after I decided to ask the very same question.
Is it true that there is no _common_ "instrument" or "synth" plugin API on linux?
Is it true that there is no the same kind of media for out-of-process instruments?
I see that there are some kinds of possible plugin APIs:
-- MusE's LADSPA extensions
-- mustajuuri plugin
-- maybe there's some more (MAIA? OX?)
-- I remember Juan Linietsky working on binding sequencer with softsynths
But I dont remember to hear anything about the results
So can anyone _please_ answer:
What is the right way to use the multiple (e.g. thirty)
softsynths together simultaneously with one host?
I mean working completely inside my computer
to have just one (or even none) midi keyboard as input.
So all the synthesys, mixing, processing goes on inside.
And to send one audio channel out to any sound card.
thanks,
nikodimka
=======8<==== Tommi Ilmonen wrote: ===8<=================
Hi.
Sorry to come in very late. The Mustajuuri plugin interface includes all
the bits you need. In fact I already have two synthesizer engines under
the hood.
With Mustajuuri you can write the synth as a plugin and the host is only
responsible for delivering the control messages to it.
Alternatively you could write a new voice type for the Mustajuuri synth,
which can lead to smaller overhead ... or not, depending on what you are
after.
http://www.tml.hut.fi/~tilmonen/mustajuuri/
On 3 Jul 2002, nick wrote:
> Hi all
>
> I've been scratching my head for a while now, planning out how im going
> to write amSynthe (aka amSynth2)
>
> Ideally i don't want to be touching low-level stuff again, and it makes
> sense to write it as a plugin for some host. Obviously in the Win/Mac
> world theres VST/DXi/whatever - but that doesnt really concern me as I
> dont use em ;) I just want to make my music on my OS of choice..
>
> Now somebody please put me straight here - as far as I can see, there's
> LADSPA and JACK. (and MuSE's own plugins?). Now, I'm under the
> impression that these only deal with the audio data - only half what I
> need for a synth. Or can LADSPA deal with MIDI?
>
> So how should I go about it?
> Is it acceptable to (for example) read the midi events from the ALSA
> sequencer in the audio callback? My gut instinct is no, no, no!
>
> Even if that's feasible with the alsa sequencer, it still has problems -
> say the host wanted to "render" the `song' to an audio file - using the
> sequencer surely it would have to be done in real time?
>
> I just want to get on, write amSynthe and then everyone can enjoy it,
> but this hurdle is bigger than it seems.
>
> Thanks,
> Nick
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
Tommi Ilmonen Researcher
>=> http://www.hut.fi/u/tilmonen/
Linux/IRIX audio: Mustajuuri
>=> http://www.tml.hut.fi/~tilmonen/mustajuuri/
3D audio/animation: DIVA
>=> http://www.tml.hut.fi/Research/DIVA/
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
apologies if this reaches you twice, it seems to have been
swallowed by that big black hole in the center of the net.
---------- Forwarded message ----------
Subject: Re: [linux-audio-dev] [ann] unmatched - a LADSPA amp tone
From: Tim Goetze <tim(a)quitte.de>
To: linux-audio-dev(a)music.columbia.edu
Date: Mon, 28 Oct 2002 14:20:27 +0100 (CET)
Steve Harris wrote:
>On Mon, Oct 28, 2002 at 02:41:08 +0100, Tim Goetze wrote:
>> http://quitte.de/easy.mp3
>
>That sounds pretty good. The attack sounds a bit muted to me though, is
>that deliberate or should it have more bite?
it could do with a little more bite, yes. it's the neck pickup
with the tone pot at the guitar closed slightly, that's the way
i usually play the super 60. this way, it stress-tests our setup's
capability of generating higher-order harmonics during attack.
>> >Yeah, fix the rectifier. I had a quick look at it and it looks like I did
>> >something fairly obvious (its basicly a compressor, but with a waveshaper
>> >instead of a linear gain).
>>
>> the shaper code looks familiar. admit i'm hoping for a performance
>> and quality gain.
>
>Yup, I adapted what I had around ;) I think something symmetric and harder
>might be better though, I'l see what I can do. Maybe it should just be a
>peak following compressor... my original though was that the power supply
>sag would cause a distortion, but maybe it wont.
whatever it does, it helps. ;) probably because it adds more
distortion in the attack phase. so it may not do exactly what
is intended on the smaller scale, but what is intended to be
modeled overall.
>I think the speed will go up dramatically when its bolted into one plugin.
>I want to get the ordering right first though. OTOH there is still mic
>effects to be added in :(
speaking for my selfish self, i'm just glad i don't have to
care about mic placement at all anymore.
i'll be happy to create more iir 'convolvers' or extend
'unmatched' for more impulses though, as long as they can be
made to converge.
tim
>> The aim of the images at the top is to provide one click access to
>>the most popular sites for information about Linux audio. I really
>>don't want to move them. They could do with being slightly smaller
>>perhaps.
>>I'd like to suggest that you put them in a table at the top or side
of >>the page rather than a frame -- I don't think they need to stay
>>visible if you scroll down or follow a link.
Yes or I could give them their own page.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
>Web-design seems a bit off topic, but...
I don't understand that. Everyone always bitches about the lack of
documentation for Linux audio. This site has been designed to address
that problem specifically from a new user POV. Getting it right should
be very much on topic.
Just because it isn't hosted on Sourceforge doesn't mean it's not open
source.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Conrad Parker wrote:
> for example, we could provide some level of commercial support for Linux
> audio stuff from CSIRO, but we could only focus on a small domain (MPEG
> audio, vorbis, sweep, and custom engineering related to analysis) and can't
> possibly list ourselves as providing general Linux audio tech support.
> We're primarily a research agency and any external work we take on needs to
> be somehow relevant to our projects.
>
> I'd imagine there'd be a large number of people who similarly wouldn't be
> willing to list themselves for general tech support, due to only having
> limited skills or interests, or simply for commercial reasons.
>
Conrad has made a good case for providing a column to list the skills,
specialities of each supporter/company. Only I cannot decide on the best
word to represent that. Any suggestions?
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Hi everyone,
Just sent off the first draft of the "Implementation Guide"
for MWPP, in time for the deadline for the next IETF meeting. You
can download it as:
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-guide.txt
See below for the abstract. A few sections in the main body,
as well as the Appendices, remain to be written, but I decided to send
it off because the completed parts are in pretty good shape, and early
feedback on the direction the document is taking (as the non-normative
companion to the main MWPP document) would be helpful.
The current plan is to make some minor changes to the
normative MWPP document, in response to comments received since its
September 22 submission, and resubmit it in time for the meeting
deadline for updated documents. So if you're holding onto any
comments on this document, now is a good time to send them along --
this document can be downloaded as:
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-mwpp.txt
---
INTERNET-DRAFT John Lazzaro
October 27, 2002 John Wawrzynek
Expires: April 27, 2003 UC Berkeley
An Implementation Guide to the MIDI Wire Protocol Packetization (MWPP)
<draft-lazzaro-avt-mwpp-coding-guidelines-00.txt>
Abstract
This memo offers non-normative implementation guidance for the MIDI
Wire Protocol Packetization (MWPP), an RTP packetization for the
MIDI command language. The memo provides a detailed description of
a sample MWPP application: an interactive MIDI session between two
parties that send and receive RTP and RTCP flows over unicast UDP
transport. The Appendices focus on special issues that arise in
other types of applications: content-streaming applications, multi-
party applications, applications that use reliable transport such
as TCP, applications that do not use RTCP, and applications that
send several MWPP RTP streams in a single session.
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
Steve Harris wrote:
> On Sun, Oct 27, 2002 at 04:28:59 +0900, Patrick Shirkey wrote:
>
>>Thanks for the feedback.
>>
>>
>>>Its quite hard to read becaues of the gifanims. the one in the top
>>
>>left >is hard to make out and the page it links to is very out of date.
>>
>>It's about due for a redo anyway. The info is still pretty vital. Notice
>>that there have been almost no questions about how fast Linux latency is
>>since it was put up.
>
>
> Thats true, but a text link would be easier to spot and less distracting.
>
But IMO more boring to look at from a newbie POV. I will give that gif a
make over this week. I'm getting tired of seeing it these days but the
info is still vital.
>
>>>The logos along the top are all in clashing styles and many of them are
>>>aliased.
>>
>>I cannot do much about the images provided by other sites.
>
>
> Well, generally they have large, high res ones that you could recomposit
> to suit the site. You could also put them out of the way somewhere.
>
The aim of the images at the top is to provide one click access to the
most popular sites for information about Linux audio. I really don't
want to move them. They could do with being slightly smaller perhaps.
>
>>>There are a few too may colours, and mixing red and blue is generally >bad
>>
>>As in the NZ, Australian, British, French and US flags?
>
>
> Yes, but I dont read flags ;)
>
>
>>>On my browser there is a mixture of 2 and 3 coloumn layouts which
>>
>>makes >it very wide and hard to follow.
>>
>>What is your browser? I have been trying to keep it working with
>>netscape 4.x, mozilla, IE, lynx.
>
>
> Mozilla. But my screen at home is only 1024 pixels wide.
>
Same here.
>
>>>Lots of the information on the frontpage should probably be on >subpages.
>>
>>The aim is to provide access to most of the info with one click and
>>without having to scroll.
>
>
> But that doesn't help if you cant find the right link, and all the
> important information is 4 pages down.
>
I don't follow this. What information is four pages down? Do you mean
the introduction for new users or are you talking about the links to the
various howtos?
> Can I suggest you break the site up into major sections, that way people
> can go to the right section for them.
>
I've been considering that for a while now. I'm trying to figure out a
nice design. Currently I have an image of a large asterix * with the
links in each slice.
> You could always open up to design suggestions from the lists, that way
> you get to choose from lots of desigs without having to make them all
> yourself ;)
>
That's true. It is becoming more of a community property these days.
Does anyone else have any suggestions. Keeping in mind that the site is
primarily for new users most of whom expect a graphically dense site at
least until they get into the Linux way.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
Hi all.
The amSynth rc1 tarball is available now.
Get it while its fresh at http://amsynthe.sourceforge.net
and be sure to read the README
This release provides some significant improvements:
* nearly 100% performance increase
* smaller and more streamlined gui. much better for those of you who
run at lower res!
* can now select presets file at startup
* libsndfile 1.x support
* gcc3 compile fixes
* others i cant remember right now!
Enjoy
Nick
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
Hello.
Does anybody of you know where I can find an updated version of the lowlatency patch for 2.4.20-pre ?
I already tried to make it apply but due to massive reiserfs changes I backed it out for now...
*Kristian
:... [snd.science] ...:
:: _o)
:: http://www.korseby.net /\\
:: http://gsmp.sf.net _\_V
:.........................: