Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7440 discussions

[linux-audio-dev] Octavian 0.1.0 pre-beta released

by Roman Kaljakin

I am pleased to announce Octavian - a realtime software synthesizer for GNU\Linux operating system. Octavians's design is like analog modular synthesizers, so it can be used both as synth and as effect processor. Modular tasks separation allow to extend possibilities in simple way. Modules can be connected between each other via channels. Features: Audio Input/Output: - OSS - JACK MIDI Input/Output: - OSS - ALSA Plugin's compatability: - native modules - LADSPA This is first pre-beta release. It is a big subject for changes and improvements, so please send your wishes and bugreports. Roman ------------------------------------------- -------- mailto: wormpost(a)mail.ru --------- -------------------------------------------

21 years, 6 months

[linux-audio-dev] ZynAddSubFX 1.2.0

by Nasca Paul

Hi. I released ZynAddSubFX 1.2.0 It is a powerfull software synthesizer for Linux and Windows, and it is located at http://zynaddsubfx.sourceforge.net/ News: 1.2.0 - ZynAddSubFX is ported to Windows ;-) - added internal Virtual Keyboard - added Configuration window - added frequency tracking to filter - improved the OscilGen (harmonic filter, RMS normalisation, etc..) - improved the recorder (uses the WAV file format and it starts only when a key is pressed) - added filter interpolation if the frequency is changed very fast (it removes some annoying clicks) - other improovements, bugfixes, speedups and cleanups of the code Paul. __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com

21 years, 6 months

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

by Ranjit Singh

> I have downloaded the C++ sample code from the echo site. Has anybody > developed it beyond that point? I will go ahead and set up a web site for > the management of the development. Are there any suggestions as to the tools > we will need to collaborate? Well, base would be CVS and bugzilla. A forum system would be good, as it's more flexible than a mailing list. phpBB is quite easy to setup, or are you thinking one of the standard repositories? I don't have much experience of more advanced tools under Linux; what do you guys reckon? It'd be good if we could version control diagrams as well. My 2 cents ;) Ranjit.

21 years, 6 months

[linux-audio-dev] [ANN] PyJack 0.1 Released

by Andy Schmeder

PyJack 0.1, Initial Release Download: http://www.a2hd.com/software/ This is a Python module which provides an interface to the Jack Audio Server. It is possible to access the Jack graph to manipulate port connections, monitor graph change events, and to perform soft-realtime audio capture and playback using Numeric Python arrays. More details, including caveats regarding realtime usage, can be found in the package documentation. This software is released under the GPL. Enjoy, Andy W. Schmeder P.S. I will not CC to jackit-devel for future release announcements. This is only for the initial. Thanks. --aws mailto:andy*a2hd,com http://www.a2hd.com/

21 years, 6 months

RE: [linux-audio-dev] Echo Darla/Gina/Layla/... on Linux

by Ranjit Singh

>My only interest is in th interface components useful in making a device >driver. Sure. I was just curious as to whether there was scope at a later to date to play with the DSP code. I've looked at the source again (cheers, David ;) and I can see what David means, in that for each device (Darla20, Darla24 etc) there is a block of data defined eg in Darla20DSP.c (in the DSP folder) which is the microcode to load into the DSP. So we don't need to mess about with that at this stage, if ever- TBH the hex doesn't look like code seqs to me (especially the Mia stuff) more like tables of setup info. Still, as you say, it's irrelevant to what we're doing, which is to interface that DSP to higher level functions. Sorry if all this is obvious; hopefully writing up our understanding of what's going on will help others.

21 years, 6 months

[linux-audio-dev] gui chrome

by Paul Davis

y'all know i like chrome-y interfaces, and that i like the use of color to improve usability. here's one that shows just how *BAD* it can get: http://www.harmony-central.com/Newp/2003/Girl-20-OS-X-lg.gif

21 years, 6 months

[linux-audio-dev] OT: Computer Music magazines for sale

by Dr William Bland

Hello, Sorry for the OT message but I thought those of you within the UK might be interested. I am selling lots of Computer Music magazines on Ebay. I will post to within the UK, and all the auctions start at just 10p (with no reserve), which is pretty good considering each magazine comes with a CD containing loads of samples and software (and they cost me 5UKP each). You can see the auctions (with photos and descriptions) at: http://search.ebay.co.uk/search/search.dll?MfcISAPICommand=GetResult&ebayta… Thanks for your time. Cheers, Bill. -- Dr. William Bland. Computer Programmer, UK. www.abstractnonsense.com

21 years, 6 months

[linux-audio-dev] SiS "Hyperstreaming"

by Steve Harris

It appears to be some kind of latency optimisation for busses, but I can;t really work out what it does. Theres a whitepaper about it here: http://www.sis.com/hs_tech/ The claim is that it can reduce system latency by proritising certain streams. I think. If you could express these priorities to the kernel it might be of some use. Anyone know more about it? - Steve

21 years, 6 months

Re: [linux-audio-dev] link: Sound on Sound: Cutting Edge : The Future of Music Technology

by Patrick Shirkey

I found it hilarious that the writer found that Linux is not viable because none of the *big names* in audio software support it. Doesn't matter about the companies that actually make the machines though. Nooooooo sirrreee. It's the software manufacturers who we should all be sucking up to. However he is, he is definitely uber cool. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://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

21 years, 6 months

Re: [linux-audio-dev] Modular synths of the world, unite and take over :-)

by ico＠fuse.net

How about having all apps implement Open Sound Control (some of them already have, such as pd, csound etc.)? Then you could control them all from one source (i.e. RTMix). Then, suddenly there would be no redundancy ;-)... Ico > > From: Lukas Degener <AFBLukas(a)gmx.de> > Date: 2003/03/18 Tue AM 08:54:55 EST > To: linux-audio-dev(a)music.columbia.edu > Subject: [linux-audio-dev] Modular synths of the world, unite and take over :-) > > Roman Kaljakin wrote: > > >I am pleased to announce Octavian - a realtime software synthesizer for GNU\Linux > >operating system. > > Octavians's design is like analog modular synthesizers,(...) > > > Well, here we have another modular synth framework. :-) > > Hi Roman, i realy like parts of your ui design. just looked at the > screenshots so far, but i think i will try octavian soon. > I would have reacted earlier to your announce, but i was somewhat busy > and didn't follow lad traffic very regulary. > > Sseems we have a little problem. > Ok, maybe problem is not exactly the right term, let's put it this way: > Right now, there is beast, there is gAlan, there is ams, and of course > there is also pd, jmax, etc. and lately Octavian, and, rats, there maybe > a zillion of other apps out there that i do not yet know of (authors of > such apps, please append your project to my list:-) ) > > While each of this projects may have unique approaches to certain > problems, or use different metaphors for similar things, i guess it is a > valid assumption, that they all have _very_ similar goals in terms of > functionality. At least that was my impression after talking with Stefan > (beast) and Torben (gAlan). > > The Big Question(tm): > How can we avoid redundant work? > > My (somewhat utopious) suggestion: > maybe we should think in components that use/modify a common > datastructure/model. > > This has almost (but not completly) nothing to do with merging ;-) > It means that we have to agree on what exactly that common model would > be, and after that, we would go on writing > different components that actualy work with this model. The problem of > course would be to define that model. > > But once we have managed this, it should be possible to have different > components cooperate on the same instance of that model at the same > time, without knowing about each other, i.e. all "inter-component" > communication would be established via the model. I tend to think of > this as a "Macro Model/View/Controller" pattern. (i have forgotten the > actual term, something like "Document Oriented Design" i think.) > > So this goes out to Matthias, Torben, Stefan, Roman, and of course > everyone else interested in such a thing: > What do you think? > > Regards, > Lukas > > > > > >

21 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev