Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

2 participants
7501 discussions

by Juhana Sadeharju

>From: "Doug Wellington" <ddw(a)dakotacom.net> > >Previously: >>> Reminds me of that old saying, "Linux is only free if your time >>> isn't worth anything"... >> >> True, sort of, but you have to remember that "there's no such thing >> as a free lunch." > >TANSTAAFL - exactly! There's always a price. Either you do it >yourself, or you have someone else do it. Time vs. money... Or, either you do it in N months or someone else do it in a week. The sentence "you have someone else do it" does not sound very realistic: 8 years ago I suggested first time a simple rectangular re-adjustable selection tool to GIMP. Once again I suggested it a few weeks ago and the task was again "assigned" to me even I asked a coder with who together I could have implemented the thing. Now GIMP does not compile in my Linux which means automatic delay of several months (more likely a year) before I have a change to get new Linux distribution. The tool would be highly needed as GIMP does not have a re-adjustable rectangular selection tool (it's currently only "if it went wrong, start from beginning"). Like having audio editor without re-adjustable selection tool. I simply don't understand why capable GIMP developers cannot implement the simple feature. There is no sense in that I should learn GIMP internals -- I could use that time for developing my own projects instead of wasting the time to sidetracks. Regards, Juhana

21 years, 4 months

[linux-audio-dev] Modulars

by Juhana Sadeharju

Hello. Below is an unfinished list of modular synths. Better than nothing. This kind of simple lists gives a good overall picture of the situation. For us developers the list should have following info: have source code? have manuals? have screenshots? have example instrument files? I think I have collected enough all of that. BTW, the paper on first interactive graphics system (I.Sutherland's SketchPad 1963) gives the idea that the drawn circuit diagram could directly be used as input to the circuit simulators. Digital modulars have been around as long but I could not find anything (between 1963-1980) on having a graphical frontend to them. Of course, I do not have access to many old papers. Regards, Juhana ============================================================================= Source Graph Script Name Code GUI UI Author/Notes ----------------------------------------------------------------------------- AlsaModularSynth Yes Yes No M.Nagorni & F.Adriaensen AnalogBox No Yes ? ? Arts Yes Yes No ? AudioMulch No Yes ? Ross Bencina BlockCompiler OnHold No Yes M. Karjalainen Building Blocks No Yes ? MIDI only CPS No Yes ? Niels Gorisse Csound Yes No Yes Barry Vercoe Cmusic Yes No Yes ? DirectCsound ? ? ? ? DreamStation No ? ? Audio Simulation Fugue Yes No Yes ? Gabriel ? Yes ? ? Galan Yes Yes ? ? Gdam Yes Yes ? ? Harmonizer/Vsig No Yes Yes Eventide Infinity No Yes ? Sound Quest InstrumentBuilder No Yes ? Mark Trombino, Csound frontend jMax Yes Yes Yes IRCAM JSyn No ? ? ? Kyma No ? ? Symbolic Sound LabView No Yes Yes National Instruments Matlab/Simulink No Yes ? Mathworks MAX/MSP No Yes ? Cycling '74 Moog Modular V No ? ? Arturia NMEdit Yes Yes No ? Nord Modular No Yes No Clavia Nyquist Yes No Yes R.B. Dannenberg OASYS No ? ? Korg OpenMusic ? Yes ? IRCAM PatchWork ? ? ? ? PD Yes Yes No Miller Puckette Pulsar/Scope/Noah No Yes No Creamware PSK Yes No Yes ? Ptolemy Yes Yes ? ? Quasimodo Yes Yes No Paul Davis Reaktor No Yes No Native Instruments Reality No ? ? Seer Systems SAOL Yes No Yes ? Scilab/Scicos Yes ? ? ? Sildex/Signal ? ? ? ? Spiralsynthmodular Yes Yes ? ? SPT ? ? ? Synthetic Intelligence Supercollider No ? Yes James McCartney SynC Modular No ? ? ? SynthBuilder Yes Yes ? Staccato Systems Tassman No Yes No Applied Acoustics Tempest No Yes ? Virtual Labs Vaz Modular No Yes No STL/Martin Fay VirSyn No ? ? ? Virtual Waves No Yes ? Synoptic Visual Orchestra No ? ? ? WaveWarp No ? ? Sounds Logical =============================================================================

21 years, 4 months

[linux-audio-dev] Modulars

by Kjetil Svalastog Matheussen

Juhana Sadeharju: > > Hello. > > Below is an unfinished list of modular synths. Better than nothing. > This kind of simple lists gives a good overall picture of the situation. > > For us developers the list should have following info: have source code? > have manuals? have screenshots? have example instrument files? > I think I have collected enough all of that. > > BTW, the paper on first interactive graphics system (I.Sutherland's > SketchPad 1963) gives the idea that the drawn circuit diagram could > directly be used as input to the circuit simulators. > > Digital modulars have been around as long but I could not find > anything (between 1963-1980) on having a graphical frontend to them. > Of course, I do not have access to many old papers. > There was one with a graphical interface: MusicBox No Yes No David Fahrland And its from the 64-69 or something, implemented in fortran, had a custom made graphical interface, and supposedly was very much like Max, only 20 years earlier. The machine was placed at EMS/Sweden. >From google I only found this information: http://www.ballade.no/nmi.nsf/doc/art2003100811103357431448 (At the top there is a picture of the machine) --

21 years, 4 months

[linux-audio-dev] Re: [RFC] Lite OSC API

by Kjetil Svalastog Matheussen

rd(a)alphalink.com.au: > > Since I think this is really important I will give an example, and from the > other end of a continuum. I use scheme for most of my music work. > Scheme has a very sophisticated numerical tower. I might write (-> > "/n_set" 1001 "freq" 440) to set the frequency of an instrument at SC3. > The OSC encoder encodes values based on their lisp type, 1001 is an > integer and gets encoded as 'i'. Lets assume that to the receiver the > frequency argument is a float, here I lose because 440 is an integer. I > argue that a receiver implemented like that is just wrong, that an integer > 440 frequency is completely valid, and SC3 thankfully agrees and plays > the right note. > For what scheme implementation are you using? And where can I get what you are using? --

21 years, 4 months

Re: [linux-audio-dev] [RFC] Lite OSC API

by rd＠alphalink.com.au

> The {jack,jamin,ardour,ladcca} archives at > http://boudicca.tux.org/hypermail/ > are not down. No, I realized that. Those archives are a fantastic resource and the only decent way to access this material, many thanks to the tux folk. I only meant that people had been reporting bounces from the list server, see <http://www.eca.cx/lad/2004/01/0416.html>.I missed a thread transfer from jackit-devel to lad for I think that reason. Rohan

21 years, 4 months

Re: [linux-audio-dev] [RFC] Lite OSC API

by rd＠alphalink.com.au

> OK, interesting - it wouldn't be a huge task, but why is this a good idea? > It just seems inconvienient for the recipient and I dont know of any other > RPC mechanisms where its allowed (or wanted). In the case of typetag-less > messages it would be difficult to handle, you'd have to try to discover > the type of the argument by inspection. Do you have a link to a rationale > for this? Firstly, from the horses mouth, "non-type-tagged messages [are] totally deprecated". See <http://www.create.ucsb.edu/pipermail/osc_dev/2003-November/00032 9.html> and surrounding posts. I don't think you need to even try to think about possibly considering perhaps partially supporting such things! Secondly, it is actually no work for the receiver. The receiver says that is needs a signed 32bit integer and it gets such an integer. It is a little work for the library. On the other hand it can be a lot of work for the sender. Domain specific languages often do not implement full C like numerical towers, a signal processing language could easily only implement floating point numbers, Lua famously has only double precision floating point numbers, and lots of people use Lua. Since I think this is really important I will give an example, and from the other end of a continuum. I use scheme for most of my music work. Scheme has a very sophisticated numerical tower. I might write (-> "/n_set" 1001 "freq" 440) to set the frequency of an instrument at SC3. The OSC encoder encodes values based on their lisp type, 1001 is an integer and gets encoded as 'i'. Lets assume that to the receiver the frequency argument is a float, here I lose because 440 is an integer. I argue that a receiver implemented like that is just wrong, that an integer 440 frequency is completely valid, and SC3 thankfully agrees and plays the right note. However if you disagree and say that I should write the literal as a float then that makes scheme a hopeless language to work in, 440.0 is still an exact integer, I need to write #i440 to get an inexact integer. But the situation is far worse, if I write (* m 1.5) this seems like it should make an inexact value regardless where m arrives from, however scheme knows that (* 0 1.5) is an exact zero and I lose again, it may even know that (* 2 1.5) == (* 2 3/2) == 3, an exact integer . Forcing a user to _very_ carefully annotate _all_ code that might get sent as an OSC packet _only because_ the OSC receiver cannot accept exact integers is not going to work, I just won't be able to work with the process. SC3 gets this very right, as usual, and in fact allows: (-> "/n_set" #i1000 (exact->inexact 0) 440) The node and index values at SC3 are syntactically integers (the index can also be a string name that maps to an integer), and the argument is syntactically a float, but it accepts floating point encodings of integers and integer encodings of real values. SC3 does it like this, QED :) > I agree that combining the verb and subject seems a little odd, but that > is the sitatuion in the web services world too - when neccesary they get > round it by adding a verb argument eg ("/my/path", "verb", ...), which is > a useful cnvention but its not neccesary to set it in stone. I think the real question is, does anyone really want to do pattern matching on the operator? I have never seen a convincing example. It would introduce all sorts of really strange sequencing issues to start with... The pattern matching people seem to like is usually of the form ("/instr[1-4]/freq" 440), not ("/instr1/{freq,ampl}" 330). If you restrict the matching to the subject, make the subject an argument, and make the operator the OSC address then the OSC dispatch mechanism can be reasonably efficient, which matters in RT synthesis environments, and people who want RE descriptors for subjects can do that without imposing an onerous burden on the core dispatch mechanism. And it looks better! In fact it looks comfortingly like lisp, ("/freq" "/instr[1-4]" 550) :-\ > > * not allocate any memory or call any other non-RT safe procedure > This one is inherantly not possible, youre doing i/o operations. Well actually it is only doing the byte encoding. SC3, being dragged out for yet another example, allows users to link in the synthesis engine and push OSC packets directly onto a queue, thus avoiding any IPC operations but still using an identical communication protocol. For the liblo case you are of course correct, but the temporal behaviour of the encoder/decoder can be pretty predictable. > I've always been more of a strongly-typed guy :) Me too, we schemers all are, we just think that an exact integer is a real number :) Regards, Rohan

21 years, 4 months

[linux-audio-dev] jackit-devel mailing list

by ian esten

anyone got any idea what is wrong with it? i just got a notice from lists.sf.net postmaster saying my message to it could not be delivered and was delayed for an unknown reason... ian

21 years, 4 months

[linux-audio-dev] [RFC] Lite OSC API

by Steve Harris

Hi *, I've been working on a lightweigth OSC API for the last couple of days and I'd appreiciate some comments - it works as it is, but it needs some work and the API isn't final so please dont integrate it into any projects yet. Its quite limited: * only basic OSC types (int, float, string, blob), but adding more is easy * no unix-domain sockets (just UDP) * no bundles * only accepts typed messages (unless you handle the packet parsing yourself) On the upside you can send an OSC message in 2 lines of C using a fprintf style function and you can setup a serverthread with polymorhism/automatic typechecking and callbacks (JACK stylee) very easily. You can also use bits of the API selectivly if you want to mange bits of the OSC lifecycle yourself, eg. handle raw OSC by hand or provide your own thread. Theres an example program that uses it here: http://plugin.org.uk/liblo/liblo/src/testlo.c and you can get the tarball here: http://plugin.org.uk/liblo/ Comments on the API style, testing and offers of help greatfully received. - Steve

21 years, 4 months

[linux-audio-dev] job posting

by Ben

GLW (makers of Harrison high-end consoles) is looking for a senior programmer. Here's the "official" post: Pro Audio company needs senior programmer responsible for system architecture, development environment, code management and related issues. Applicant must demonstrate a broad knowledge of programming languages, tools and multithreading. Linux, BeOS, Windows, Mac OSX, OpenGL, embedded systems, device drivers and pro audio experience is a plus. We are looking for a top-notch programmer. I think there are quite a few developers on this list that should be interested in this job. Send resumes to jobs(a)glw.com. -Ben Loftis

21 years, 4 months

[linux-audio-dev] call for mirrors [was Re: 2nd LAD conference]

by Joern Nettingsmeier

On Thu, 22 Jan 2004, Matthias Nagorni wrote: > On Thu, 22 Jan 2004, Mark Constable wrote: > > > Are there plans to record any of the lectures and put them > > on the web somewhere ? > > Yes, we plan to record the lectures and put also the presentation material > on the web. Moreover we plan to establish a live audio streaming of the > talks and concerts. If we get the presentation material in time, we might > even put that on the web in a way that "remote" listeners can follow the > talks watching the same slides as the audience. > Last time, Steve and J�rn took care of the internet "broadcasting" of the > event. IIRC they also established an IRC channel for "remote" discussion. > The audio quality of the streaming is not a matter of the microphone alone > but more of the available bandwidth. i'm willing to take care of the streaming like last year. this time, i'll try to provide a webcam as well, but i'm not yet sure about streaming video. but a picture every 15 secs or so should be possible. ;) my plan is to have an ogg stream of the talks and the concerts, an irc talkback channel, a website with the presentation material for download and a crude webcam to give you an idea which slide the presenter is talking about atm. work to set up a relay network for streaming will begin by the end of february, i've got a couple other things to do atm. [call for mirrors] if you have a host with good internet connection and are willing to donate some bandwidth, please contact me off-list. either you provide an icecast2 server yourself, or else i will need shell access to build one (though not root). the distribution needs to be recent, or else building icecast2 is problematic. for the webcam, we'll need a couple http servers as well. i thought about round-robin dns, but a friend just pointed out a master server with some php code that will produce a different link each time it is called is probably easier. so all you have to do is pull an image every couple seconds, make it available somewhere and send me the url. yours, joern

21 years, 4 months

Jump to page:

2025

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