Re: [linux-audio-dev] Different Plug In API's
HA HA HA HA I meant "\usr\friendly". HA HA HA HA HA HA HA HA And jfm3, your security key makes my Windows Microsoft Outlook Express feel sick. jfm3 wrote: == >HAHAHAHAHAHAA > >You said "usr friendly".
Re: [linux-audio-dev] Different Plug In API's
HAHAHAHAHAHAA You said "usr friendly". On Wed, 2002-02-13 at 19:30, xk wrote: > You have a rather simplistic view of the world :) > Not all people know how to compile a plugin or how to work in Linux, which > is still far from beeing as usr friendly as Windows is. > > - Original Message - > From: Joachim Backhaus <[EMAIL PROTECTED]> > > I see no reason that Windows and DOS exist! > -- (jfm3) signature.asc Description: This is a digitally signed message part
Re: [linux-audio-dev] Different Plug In API's
You have a rather simplistic view of the world :) Not all people know how to compile a plugin or how to work in Linux, which is still far from beeing as usr friendly as Windows is. - Original Message - From: Joachim Backhaus <[EMAIL PROTECTED]> I see no reason that Windows and DOS exist!
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
Steve Harris hat gesagt: // Steve Harris wrote: > On Tue, Feb 12, 2002 at 11:56:23 +0100, Frank Barknecht wrote: > > > > As much as I like your way and as much as I would like to understand it > > better, I would prefer a more general C or even better C++ tutorial. > > Making the work easier with XML and Perl might be too off-topic in the > > tutorial I am thinking of. It simply a next step, that should come > > A tutorial on how to write LADSPA code in C allready exists. Now I looked a bit further down the ladspa.org page and a little ashamed I have to admit, that Dave Bensons work comes very close to my fictional tutorial, it just slipped me. > I have never done it. I got 50% of the way through a simple plugin > before I got bored of typing: > >port_descriptors = (LADSPA_PortDescriptor *)calloc(3, > sizeof(LADSPA_PortDescriptor)); >ampDescriptor->PortDescriptors = > (const LADSPA_PortDescriptor *)port_descriptors; >... > > Then I decided it was a job for software. Or a job for C++? > I don't use C++ for religious reasons ;) I see. > But, I suspect it could be a good > choice for LADSPA plugins, the CMT set are C++ IIRC. They are, and as I understand CMT, Richard did hide a lot of the tedious work in a smart class. I'll have to dig deeper into it. Ciao, -- ____ Frank Barknecht __ __ trip\ \ / /wire __ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / / / / / // // /\ \\ ___\\ \ /_/ /_/ /_/ /_//_// / \ \\_\\_\ /_/\_\
[linux-audio-dev] [ot] perl python php
Steve Harris hat gesagt: // Steve Harris wrote: > On Tue, Feb 12, 2002 at 11:56:23 +0100, Frank Barknecht wrote: > > (The makestub.pl indeed needs a cleanup. I found myself constantly > > cleaning up my Perl code, so I am now happily learning and coding in > > Python, but that shall not start a Perl-Python discussion, please.) > > Yes, I tried to give up perl a year ago after I found I was spending too > much time throwing away old, illegible code and starting again. I haven't > really found a replacement though. I like Java, but it's a bit long > winded. I've not tried python. > > The only languages I use regularly are C, ECMAScript (aka JavaScript 1.5) > and PHP. Sadly ECMAScript+DOM is not easily available as a standalone > language, it is really good. Doing Web for a living, eh? Now, seriously, you might want to take a look at Python, if religion doesn't interfere here. I found, that a lot of the sayings are true: it really enforces read- and maintainability, and in contrast to Jave it's quick to learn and to hack. With your knowledge, you will only need an afternoon to get the grasp. And most important: the regular expressions are Perl-compatible. Ciao, -- ____ Frank Barknecht __ __ trip\ \ / /wire __ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / / / / / // // /\ \\ ___\\ \ /_/ /_/ /_/ /_//_// / \ \\_\\_\ /_/\_\
Re: [linux-audio-dev] Re: ALSA is in 2.5!!!
On Wed, 13 Feb 2002, D. Stimits wrote: > Just curious, is the integration based on the "stable" (less useful) > version of ALSA, or one of the "devel" versions? It's the latest 0.9.x version of ALSA. All features, drivers, bells and whistles are included. ;) -- http://www.eca.cx Audio software for Linux!
Re: [linux-audio-dev] Re: [Alsa-devel] ALSA is in 2.5!!!
Kai Vehmanen wrote: > > This is great news! This is not just great news - it is _amazingly_ great news(!). Within just a week, the two most major "roadblocks" keeping me from developing Linux music/audio apps have been "fixed". Now we have virtual commitment from the kernel developers for supporting the two things we need for developing - and just as important - *distributing* audio apps on the Linux platform. With the addition of kernel preemption code, and inclusion of the low latency patches by Red Hat (which I *assume* are going to be included in the next major release, not just Rawhide), it will be possible to distribute an audio application in "user friendly" format: a package that installs all the files, then enables "realtime" mode by writing to the file in the /proc directory. No expert sysadmin status needed by the end user (musician). And with the inclusion of the ALSA drivers in the kernel, good drivers for pro-quality sound cards will "just be there" - again, no complicated installation steps. We're getting really close to where I can envision some major music/audio software companies offering versions of existing products (e.g., Cubase, Cakewalk, Logic, Cool Edit Pro ...) for Linux. Or - new companies offering commercial products that were developed natively on Linux. This is exciting. Once again, my faith in Linus, the kernel developers, and the Open Source development model is reaffirmed! Life is good. - Jay Ts
Re: [linux-audio-dev] Re: [Alsa-devel] ALSA is in 2.5!!!
Kai Vehmanen wrote: > > This is great news! > > Congratulations to the ALSA team and to all who've contributed to the > effort. This is of course just the beginning. Hopefully the merge will not > only increase the number of incoming bug reports, but also the number of > incoming new developers. :) Just curious, is the integration based on the "stable" (less useful) version of ALSA, or one of the "devel" versions? D. Stimits, [EMAIL PROTECTED] > > On Wed, 13 Feb 2002, Jaroslav Kysela wrote: > > > the big moment in ALSA existence is here. Linus integrated ALSA > > into 2.5 kernel tree!! The first pre-patch with ALSA will be available > > soon. For impatient hackers: Check http://openlogging.org, click on > > 'Sorted by number of lines' and choose 'Linux kernel tree' with domain > > 'transmeta.com' and contact 'Unknown'. > > I would like to send big thank you to all ALSA developers. I am > > looking forward to the future. > > > > Jaroslav > > > > - > > Jaroslav Kysela <[EMAIL PROTECTED]> > > SuSE Linuxhttp://www.suse.com > > ALSA Project http://www.alsa-project.org > > > > -- Forwarded message -- > > Date: Wed, 13 Feb 2002 12:26:06 -0800 (PST) > > From: Linus Torvalds <[EMAIL PROTECTED]> > > To: Alan Cox <[EMAIL PROTECTED]> > > Cc: David S. Miller <[EMAIL PROTECTED]>, > > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, > > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, > > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > Subject: Re: 2.5.4 sound module problem > > > > > > > > On Wed, 13 Feb 2002, Alan Cox wrote: > > > > > > Waste of effort. ALSA will replace the OSS code anyway > > > > In fact, in my tree it right now has replaced it. I'll make a pre-patch > > and try to get the BK tree pushed out. > > > > Linus > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to [EMAIL PROTECTED] > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > > > > > > > > ___ > > Alsa-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/alsa-devel > > > > -- > http://www.eca.cx > Audio software for Linux!
[linux-audio-dev] Re: [Alsa-devel] ALSA is in 2.5!!!
This is great news! Congratulations to the ALSA team and to all who've contributed to the effort. This is of course just the beginning. Hopefully the merge will not only increase the number of incoming bug reports, but also the number of incoming new developers. :) On Wed, 13 Feb 2002, Jaroslav Kysela wrote: > the big moment in ALSA existence is here. Linus integrated ALSA > into 2.5 kernel tree!! The first pre-patch with ALSA will be available > soon. For impatient hackers: Check http://openlogging.org, click on > 'Sorted by number of lines' and choose 'Linux kernel tree' with domain > 'transmeta.com' and contact 'Unknown'. > I would like to send big thank you to all ALSA developers. I am > looking forward to the future. > > Jaroslav > > - > Jaroslav Kysela <[EMAIL PROTECTED]> > SuSE Linuxhttp://www.suse.com > ALSA Project http://www.alsa-project.org > > -- Forwarded message -- > Date: Wed, 13 Feb 2002 12:26:06 -0800 (PST) > From: Linus Torvalds <[EMAIL PROTECTED]> > To: Alan Cox <[EMAIL PROTECTED]> > Cc: David S. Miller <[EMAIL PROTECTED]>, > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > Subject: Re: 2.5.4 sound module problem > > > > On Wed, 13 Feb 2002, Alan Cox wrote: > > > > Waste of effort. ALSA will replace the OSS code anyway > > In fact, in my tree it right now has replaced it. I'll make a pre-patch > and try to get the BK tree pushed out. > > Linus > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > > > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel > -- http://www.eca.cx Audio software for Linux!
RE: [linux-audio-dev] LJ Firenze report
one of the presentations was for demudi (debian based multi-media distro) - I just checked their web page and it seems like the latest update was on october 2001. anybody knows more details? is the project dead? on hiatus? erik > -Original Message- > From: Dave Phillips [mailto:[EMAIL PROTECTED]] > > Greetings: > > Those of you who attended the event may recall that I promised to > submit my notes to the Linux Journal. I did so, and never > heard about it > again. I mistakenly assumed that Richard rejected the article: While > searching for something else I came across this URL: > > http://www.linuxjournal.com/article.php?sid=5355 > > Perhaps LJ was going through one of its periodic shuffles, but I never > heard from anyone there about putting the notes on-line. Too bad they > didn't publish the pictures... > > Best regards, > > == Dave Phillips > > The Book Of Linux Music & Sound at > http://www.nostarch.com/lms.htm > The Linux Soundapps Site at http://sound.condorow.net >
Re: [linux-audio-dev] query
On Wed, 2002-02-13 at 17:39, Taybin Rutkin wrote: > > bigger than the overlap you used before. So far the basic idea. Happy > > implementing :-) > > Is that how the non-pitch-changing one works? That's how sox does it, I suppose. But that only works for a limited range. If you try to stretch it to much this way, you probably get some strange artefacts. Another option are FFT or wavelet based algorithms. Actually, this time stretching question would be something for a FAQ. I'm subscribed to the music dsp list as well, and people frequently ask how time stretching is done. There is a good explanation at http://www.dspdimension.com/ Cheers, Alex
Re: [linux-audio-dev] query
On Wed, Feb 13, 2002 at 11:39:09 -0500, Taybin Rutkin wrote: > On 13 Feb 2002, Alexander Ehlert wrote: > > > The basic idea for a simple time stretch is to subdivide your signal > > into overlapping windows. Next you would apply a so called windowing > > function to that window (Kaiser, Hamming, Hanning, a triangle). > > Afterwards you sum up those windows with an overlap that is a little bit > > bigger than the overlap you used before. So far the basic idea. Happy > > implementing :-) > > Is that how the non-pitch-changing one works? Its one of the approaches, yes. The most appripriate technique depends on the source material. - Steve
Re: [linux-audio-dev] Different Plug In API's
>> MAIA does not exist. > >What is this: http://www.linuxdj.com/mucos/ ? AFAIK, its a completely dead project. >> This is the first time I have ever heard of OX_API. > >The API of GNU octal >http://www.gnu.org/software/octal/ I notice that the octal mailing list has seen no significant activity for some time. OX_API is a good example of the kind of application specific API that can wrap LADSPA quite easily. --p
Re: [linux-audio-dev] Different Plug In API's
On Wed, 13 Feb 2002, Joachim Backhaus wrote: > > An interesting question, to be sure. > > http://jackit.sf.net/faq/ compares > > a lot of plugin and host frameworks, which might give you a start. > > Perhaps, but I get a 404 - not found message. > > Is http://jackit.sourceforge.net/docs/faq.php > the same? yup, that's the one -- hand me the brown paper bag for not remembering the urls to a site I wrote ;) regards, wingo.
Re: [linux-audio-dev] query
On 13 Feb 2002, Alexander Ehlert wrote: > The basic idea for a simple time stretch is to subdivide your signal > into overlapping windows. Next you would apply a so called windowing > function to that window (Kaiser, Hamming, Hanning, a triangle). > Afterwards you sum up those windows with an overlap that is a little bit > bigger than the overlap you used before. So far the basic idea. Happy > implementing :-) Is that how the non-pitch-changing one works? Taybin
RE: [linux-audio-dev] Different Plug In API's
> -Original Message- > From: Paul Davis [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 13. Februar 2002 16:42 > To: [EMAIL PROTECTED] > Subject: Re: [linux-audio-dev] Different Plug In API's > > > >why do so much different Plug In API's exist > >(it seems that every application has it's own API)? > > for the same reason that so many operating systems exist. I see no reason that Windows and DOS exist! > >Wouldn't it be much more efficient to bundle > >the power to one superb API? > > > >E.g. I have found LADSPA, MAIA and OX_API. > > MAIA does not exist. What is this: http://www.linuxdj.com/mucos/ ? > This is the first time I have ever heard of OX_API. The API of GNU octal http://www.gnu.org/software/octal/ Regards, Joachim
[linux-audio-dev] LJ Firenze report
Greetings: Those of you who attended the event may recall that I promised to submit my notes to the Linux Journal. I did so, and never heard about it again. I mistakenly assumed that Richard rejected the article: While searching for something else I came across this URL: http://www.linuxjournal.com/article.php?sid=5355 Perhaps LJ was going through one of its periodic shuffles, but I never heard from anyone there about putting the notes on-line. Too bad they didn't publish the pictures... Best regards, == Dave Phillips The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm The Linux Soundapps Site at http://sound.condorow.net
Re: [linux-audio-dev] query
On Wed, 2002-02-13 at 10:53, Swapnil Padhye wrote: > i want to strech a audio file. how can i do that > Is it possible to do so in java or any programming language??? if yes then what is >the exact procedure?? *g* I'd say this is possible in any programming language that provides you with the basic calculation operations. Helpful would be a array data type. So I suggest C, C++, Fortran, Pascal, Modula, Oberon, ... The basic idea for a simple time stretch is to subdivide your signal into overlapping windows. Next you would apply a so called windowing function to that window (Kaiser, Hamming, Hanning, a triangle). Afterwards you sum up those windows with an overlap that is a little bit bigger than the overlap you used before. So far the basic idea. Happy implementing :-) Cheers, Alex
Re: [linux-audio-dev] LADSPA Writing Tutorial
>> alsa, "properly linked" means either learning quite a lot about the >> linker or using libtool, neither one of which i relish :) > >Libtool won't* correctly build LADSPA plugins. It thinks the're libraries >and makes some assumptions. i got it to work for quasimodo plugins. but yes, it is tricky. you need to use the -module flag to libtool, and the host has to be compiled with -export-dynamic. --p (who knows more about libtool than he wants to)
Re: [linux-audio-dev] Different Plug In API's
>why do so much different Plug In API's exist >(it seems that every application has it's own API)? for the same reason that so many operating systems exist. >Wouldn't it be much more efficient to bundle >the power to one superb API? > >E.g. I have found LADSPA, MAIA and OX_API. MAIA does not exist. This is the first time I have ever heard of OX_API. LADSPA does not belong to an application. It was developed to represent a minimal subset of features found to be common to the "native" plugin designs of several different programs. It was expected that many applications using LADSPA would wrap it to provide additional, application-specific functionality, while leaving the core DSP code in a common, reusable location. Anyway, your question is already too late. People who write audio plugins for money already have to contend with VST, MAS, RTAS, TDM, HTDM, DirectX and several others. --p
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
Hi, [EMAIL PROTECTED] wrote: > There is also a graphical program that creates the XML, GDAM. The link to > it on ladspa.org is dead though. Yes, that should be http://www.ffem.org/gdam nowadays. Frank
RE: [linux-audio-dev] Different Plug In API's
> -Original Message- > From: Andy Wingo [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 13. Februar 2002 16:25 > To: '[EMAIL PROTECTED]' > Subject: Re: [linux-audio-dev] Different Plug In API's > > > An interesting question, to be sure. > http://jackit.sf.net/faq/ compares > a lot of plugin and host frameworks, which might give you a start. Perhaps, but I get a 404 - not found message. Is http://jackit.sourceforge.net/docs/faq.php the same? Regards, Joachim
Re: [linux-audio-dev] query
On Wed, Feb 13, 2002 at 09:53:17 -, Swapnil Padhye wrote: > > Dear sir, > > i want to strech a audio file. how can i do that If you want to do it using an existing tool, try "sox stretch". If you wanto to write your own code, do a web search for "sinc interpolation" it can be done in nearly all languages. That will not maintain pitch though, it will just make the audio longer. - Steve
Re: [linux-audio-dev] Different Plug In API's
On Wed, 13 Feb 2002, Joachim Backhaus wrote: > > Hi, > > why do so much different Plug In API's exist > (it seems that every application has it's own API)? > > Wouldn't it be much more efficient to bundle > the power to one superb API? > > E.g. I have found LADSPA, MAIA and OX_API. > > But LADSPA seems to be the online one of them > which is further developed. > > Regards, > Joachim An interesting question, to be sure. http://jackit.sf.net/faq/ compares a lot of plugin and host frameworks, which might give you a start. regards, wingo.
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
On Wed, Feb 13, 2002 at 10:16:42 -0500, Taybin Rutkin wrote: > > More or less. Some of them include static libraries written in C. For eg. > > gverb, which was written by Juhana Sadeharju, there is just a simple XML+C > > wrapper that calles the library functions. > > There is also a graphical program that creates the XML, GDAM. The link to > it on ladspa.org is dead though. It produces some XML, its different though. It's more like a declartive description of the plugin, which is used to build C code. Mine is just C source embedded in XML, the only thing that is really generated is the repetetive housekeeping stuff. - Steve
Re: [linux-audio-dev] Different Plug In API's
On Wed, 13 Feb 2002, Joachim Backhaus wrote: > why do so much different Plug In API's exist > (it seems that every application has it's own API)? It is easier to design an API then to implement it. > Wouldn't it be much more efficient to bundle > the power to one superb API? Well, different API's have different goals that might conflict with each other. The S in LADSPA stands for Simple. Taybin
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
On Wed, 13 Feb 2002, Steve Harris wrote: > > > generate the raw C source. I think it saves a lot of grunt work, > > > but it > > > > That would be super cool! Is that how you make all of your plugins? > > More or less. Some of them include static libraries written in C. For eg. > gverb, which was written by Juhana Sadeharju, there is just a simple XML+C > wrapper that calles the library functions. There is also a graphical program that creates the XML, GDAM. The link to it on ladspa.org is dead though. Taybin
RE: [linux-audio-dev] Different Plug In API's
> -Original Message- > From: Joachim Backhaus [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 13. Februar 2002 15:39 > To: '[EMAIL PROTECTED]' > Subject: [linux-audio-dev] Different Plug In API's > > But LADSPA seems to be the online one of them ^^ I can't write!!! That hurts ;-) Obviously I meant "only".
Re: [linux-audio-dev] LADSPA Writing Tutorial
On Tue, Feb 12, 2002 at 03:57:37 -0500, Paul Davis wrote: > > alsa, "properly linked" means either learning quite a lot about the > linker or using libtool, neither one of which i relish :) Libtool won't* correctly build LADSPA plugins. It thinks the're libraries and makes some assumptions. - Steve [*] Well, I couldn't make it, but I'm no libtool expert.
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
On Tue, Feb 12, 2002 at 11:56:23 +0100, Frank Barknecht wrote: > (The makestub.pl indeed needs a cleanup. I found myself constantly > cleaning up my Perl code, so I am now happily learning and coding in > Python, but that shall not start a Perl-Python discussion, please.) Yes, I tried to give up perl a year ago after I found I was spending too much time throwing away old, illegible code and starting again. I haven't really found a replacement though. I like Java, but it's a bit long winded. I've not tried python. The only languages I use regularly are C, ECMAScript (aka JavaScript 1.5) and PHP. Sadly ECMAScript+DOM is not easily available as a standalone language, it is really good. - Steve
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
On Tue, Feb 12, 2002 at 11:56:23 +0100, Frank Barknecht wrote: > > As much as I like your way and as much as I would like to understand it > better, I would prefer a more general C or even better C++ tutorial. > Making the work easier with XML and Perl might be too off-topic in the > tutorial I am thinking of. It simply a next step, that should come A tutorial on how to write LADSPA code in C allready exists. I have never done it. I got 50% of the way through a simple plugin before I got bored of typing: port_descriptors = (LADSPA_PortDescriptor *)calloc(3, sizeof(LADSPA_PortDescriptor)); ampDescriptor->PortDescriptors = (const LADSPA_PortDescriptor *)port_descriptors; ... Then I decided it was a job for software. I don't use C++ for religious reasons ;) But, I suspect it could be a good choice for LADSPA plugins, the CMT set are C++ IIRC. OTOH all the stuff I write would be applicable, its just that do do it in raw C you would have to write a lot of routine setup code too. - Steve
[linux-audio-dev] Different Plug In API's
Hi, why do so much different Plug In API's exist (it seems that every application has it's own API)? Wouldn't it be much more efficient to bundle the power to one superb API? E.g. I have found LADSPA, MAIA and OX_API. But LADSPA seems to be the online one of them which is further developed. Regards, Joachim
Re: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
On Tue, Feb 12, 2002 at 01:16:18 -0800, Tim Westbrook wrote: > > > You've seen how I do it, write it in XML wrapped C, then use perl > > to > > generate the raw C source. I think it saves a lot of grunt work, > > but it > > That would be super cool! Is that how you make all of your plugins? More or less. Some of them include static libraries written in C. For eg. gverb, which was written by Juhana Sadeharju, there is just a simple XML+C wrapper that calles the library functions. - Steve
RE: [linux-audio-dev] LADSPA Writing Tutorial [was: tracker with midi input]
> PS The analogue oscilator that I used to distrubte was very > very bad. It's > removed in the current release. I will write another when I > have a good > understanding of band-limited oscilators. > Then write just a sine osc. -Mikko
[linux-audio-dev] query
Dear sir, i want to strech a audio file. how can i do that Is it possible to do so in java or any programming language??? if yes then what is the exact procedure?? Kindly helpme in doing so. Thanking you. Swapnil Padhye
