Linux-audio-dev April 2005

linux-audio-dev@lists.linuxaudio.org

107 participants
90 discussions

[linux-audio-dev] [Fwd: ICMC 2005 Free Sound Project]

by Xavier Amatriain

> > I would like to invite you all to have a look at The Freesound Project. > > -> http://freesound.iua.upf.edu/ > > This project was started in the context of ICMC 2005, and is a website for creative-commons licensed audio material exchange. If you want to know more about the project (why it was started and what it's goals are) have a look at this page: > > -> http://freesound.iua.upf.edu/whatIsFreesound.php > > Don't hesitate to contact me (bdejong(a)iua.upf.edu) for more information or feedback. > > > kindest regards, > > Xavier Serra > ICMC 2005 Program Chair > > PS: please feel free to forward this message to relevant mailing lists or interested people. > > -- /********************************** ********* Xavier Amatriain ******** ****** Music Technology Group ***** ** IUA- Universitat Pompeu Fabra ** ****** www.iua.upf.es/~xamat ****** ***********************************/

19 years, 5 months

[linux-audio-dev] FOSS-tools for realtime audio analysis?

by mathias_lundgren＠bredband.net

Hi! Are there any tools/libraries around which makes it possible to do something like this? 1) Feed an audio signal (f.ex. a sinus wave) into external hardware 2) Record the signal returned from the external hardware 3) "Compare" the two signals (realtime would be neat, if you know what latency you have btwn output/input I hope this might be achieved w Jack) and perform some kind of analysis of what the external hardware does to the signal (S/N ratio, damping, etc etc). Open source stuff would of course be preferable /Mathias

19 years, 5 months

[linux-audio-dev] [PATCH] liblo & pattern matching callback

by Martin Habets

Hi Steve, Was testing this scenario today, which may look familiar to you: - I created a server with some methods: '/ping/documentation' and '/osc-schema/documentation', both of which use the same handler 'doc'. - I send query '/*/documentation' to the server. - 'doc' got called twice with path '/*/documentation'. The unexpanded path makes it impossible for the handler to determine what container was intended. In my interpretation the OSC spec is not completely explicit on this point, but I think the intention was to send the expanded path to the handler. The spec is specific in stating that '*' is invalid in an OSC method, and it talks about the "OSC Address of a OSC Method". Initially I hacked liblo to always send the expanded path. However, the result was also that the generic method handler (oh, I used that too :) got called with a NULL path. Since that is useless to that handler it seems best to me to use the unexpanded path for this case. The resulting patch is applied. Please let me know your view on this. Cheers, -- Martin --------------------------------------------------------------------------- Index: liblo/src/server.c =================================================================== --- liblo.orig/src/server.c 2005-03-02 19:15:47.000000000 +0000 +++ liblo/src/server.c 2005-03-26 11:33:41.000000000 +0000 @@ -463,6 +463,7 @@ lo_address src = lo_address_new(NULL, NULL); char hostname[LO_HOST_SIZE]; char portname[32]; + const char *pptr; free(msg->types); msg->types = types; @@ -542,7 +543,13 @@ } } - ret = it->handler(path, types, argv, argc, msg, + /* Send wildcard path to generic handler, expanded path + to others. + */ + pptr = path; + if (it->path) pptr = it->path; + + ret = it->handler(pptr, types, argv, argc, msg, it->user_data); } else if (lo_can_coerce_spec(types, it->typespec)) { @@ -572,7 +579,13 @@ } endian_fixed = 1; - ret = it->handler(path, it->typespec, argv, argc, msg, + /* Send wildcard path to generic handler, expanded path + to others. + */ + pptr = path; + if (it->path) pptr = it->path; + + ret = it->handler(pptr, it->typespec, argv, argc, msg, it->user_data); free(argv); free(data_co);

19 years, 5 months

[linux-audio-dev] Jacklaunch vs. asoundrc jack plugin

by Ivica Ico Bukvic

Hi all, First of all, please accept my apologies for cross-posting. I simply feel that this issue may be of interest to all these groups. After some research and experimenting with jacklaunch (libjackasyn) as well as alsa .asoundrc jack plugin I found out that very few apps actually cooperate with either of these. Jack plugin for asoundrc practically works only with aplay/arecord and freebirth. Audacity doesn't cooperate with either, while jacklaunch even though it has been reported to work with sweep doesn't on my machines (mdk 10.0 and 10.1). I've tested latest jack, sweep, Alsa 1.0.6 and 1.0.7 (I did not go beyond that as 1.0.8 has apparent issues with hdsploader) and had no luck whatsoever. Hence, I am just wondering at this point whether asoundrc jack is still in the testing phase (some of the errors that apps reported trying to use jack plug were due to inability to probe some info from the alsa driver which implies possible incompleteness of the implementation or weird probing from the app's side) and also whether anyone has had better luck than myself using either of these with audacity, sweep, and other non-jackified, yet important Linux audio apps via either of the aforementioned ways. FWIW, it would be really nice to see some united effort to jackify some of the other critical Linux audio apps even if their original authors do not feel like that is one of their priorities (I know, I know, if I am so interested in such developments then I might as well set an example by doing what I am advocating, which is something I would love to do, but unfortunately currently the notion of "free time" in my life is but a joke). Many thanks! Best wishes, Ivica Ico Bukvic, composer & multimedia sculptor http://meowing.ccm.uc.edu/~ico/ -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 4/5/2005

19 years, 5 months

[linux-audio-dev] live pa questions

by Dave Griffiths

Hi all, Is there a chance that signals generated from software could damage live PA equipment? I'm guessing not, as there is obviously (I assume) some limiting built into soundcards, but I'm just wondering what applications do to, if anything, to help. It's just something that worries me sometimes when playing live, and generating particually nasty noises by accident, or design :) cheers, dave

19 years, 5 months

Re: [linux-audio-dev] live pa questions

by Pieter Palmers

Andres Cabrera wrote: >>Overheating of the amp is nonsense. Most amplifiers operate in class A >>or AB anyway, and maybe in class D. Heat dissipation is independant of >>the input signal for these amps. The types that might build up a problem >>with heat (e.g. class H) aren't used in PA enviroments. And before the >>amp overheats, your speakers will be dead. >> >> > >Thanks for clarifying. I remembered I heard about overheating somewhere >with DC, and thought it was on the amp. >Adding a small DC offset is one easy way of getting rid of denormal >problems (in programs like csound and pd), do you know if this small DC >offset is able to produce these effects? > > I don't know about the output stage of a soundcard. (Almost) every soundcard uses a delta-sigma DAC, which needs some sort of low pass filtering. It needs an output buffer to transform the rather high impedance of this filter to a low output impedance, so the question is if there is some sort of DC decoupling impemented in this buffer. I don't know, but using a voltmeter (or scope) while applying a DC signal to the card will answer that. if you take a look at the specs of the EMU1820M it states "Frequency Response: 0.0/-.35dB, 20Hz - 20kHz" which would mean that it doesn't output DC signals. But as far as I know, most audio input stages are capacitively coupled, thereby removing such DC offsets, so there is little chance that this type of signals will propagate through the entire signal chain. Greets, Pieter

19 years, 5 months

[linux-audio-dev] csound instrument wanted (soprano)

by Julien Claassen

Hi all! I wonder. I once had a csound .orc+example score for a model/immitation of a soprano human voice. Unfortunately I lost it. Yet now I need it urgently for a composition of mine. Can anyone help me? Point me to the correct location on the net or mail it as an attachment? I looked through the usual places: csound.com and bath... No success. I remember that I got it by browsing through Dave's personal csound-links page, but it seems to be gone. Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net - the Linux TextBased Studio guide

19 years, 5 months

[linux-audio-dev] Looking for multichannel soundcard to borrow during LAC concert

by nescivi

Hi, I've been working on my piece for the LAC Concert and realised that it would really work well if it were multichannel. Only, I do not have a multichannel soundcard yet for my laptop and will not be able to afford one till that time. But, as there will be lots of people around, I thought maybe I could borrow one for the concert? Would anyone be able to help out here? I think I might be able to test with an RME Multiface in the month to come, so that one would probably be preferred. For the rest, I'll be using SuperCollider with JACK... and I have a Midisport 2x2 interface hanging on one of my 2 usb-ports. Please email me privately if you're going to be at the LAC and are willing to help me out. sincerely, Marije

19 years, 5 months

[linux-audio-dev] Any other Berliners going to the LAC this year?

by nescivi

Hiho, the LAC comes closer and closer, so I was wondering how many people are going there from Berlin this year. Last year, there were at least 10 or so, so I thought maybe this year we could consider traveling together, either sharing cars or taking advantage of group traveling by train. What do you think? Maybe you could email me privately, then I'll create a little Berlin-to-LAC list and then we could see if this works out some way? sincerely, Marije

19 years, 5 months

[linux-audio-dev] Re: [linux-audio-announce] 64 Studio - a new distribution for creativex86_64 users

by Andreas Kuckartz

Who is "we"? Does "marketed to hardware OEMs" imply that this is a commercial project? What is the (intended) relation/difference to DeMuDi? Cheers, Andreas ----- Original Message ----- From: "Daniel James" <daniel(a)64studio.com> To: "Linux Audio Announce list" <linux-audio-announce(a)music.columbia.edu> Sent: Saturday, April 02, 2005 12:04 PM Subject: [linux-audio-announce] 64 Studio - a new distribution for creativex86_64 users > Hello all, > > 64 Studio is a collection of software designed specifically for > content creation on x86_64 hardware (that's AMD's 64-bit CPUs and > Intel's EMT64 chips), including audio, video and design applications. > > It's based on the pure 64 port of Debian GNU/Linux, but with a > specialised package selection and lots of other customisations. It > will be marketed to hardware OEMs in the creative workstation and > laptop markets as an alternative to the 64-bit version of Windows XP, > or OS X on Apple hardware. > > We are currently working on a prototype. Our next step will be a > CD-ROM installer image which will be distributed to beta testers. If > you're interested in this project, please see the FAQ on the website, > or join our mailing list. > > http://64studio.com/ > > Cheers > > Daniel > _______________________________________________ > linux-audio-announce mailing list > linux-audio-announce(a)music.columbia.edu > http://music.columbia.edu/mailman/listinfo/linux-audio-announce >

19 years, 5 months

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 April 2005