Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

2 participants
7534 discussions

[linux-audio-dev] Re: linux-audio-dev Digest, Vol 41, Issue 8

by oc2pus＠arcor.de

Am Dienstag, 13. Februar 2007 schrieb linux-audio-dev-request(a)music.columbia.edu: > 5. CLAM 0.98 released (David Garc?a Garz?n) > > > Message: 5 > Date: Tue, 13 Feb 2007 19:28:31 +0100 > From: David Garc?a Garz?n <dgarcia(a)iua.upf.edu> > Subject: [linux-audio-dev] CLAM 0.98 released > To: "The Linux Audio Developers' Mailing List" > <linux-audio-dev(a)music.columbia.edu> > Message-ID: <200702131928.31826.dgarcia(a)iua.upf.edu> > Content-Type: text/plain; charset="utf-8" > > We are glad to announce CLAM 0.98 a.k.a. âMac is here to stayâ. > > CLAM[1] is a free-software, C++ framework for doing research and > application development in audio and music. It also comes with a set of > applications ready to use for non technical users. > > This is the first release not developed within the MTG [2] since its main > developers now work at the GTI[3], also at the Universitat Pompeu Fabra. > Still, CLAM is very indebted to the MTG people. > > Most of the work in this release was focused on having stable building, > testing and packaging on Mac. Check out the MacOS download section[4] on > the web for applications DMGâs. > > We have received valuable and stimulating input for the MacOS build from > Christopher Tignor, Volker Schumacher, Eduard Aylon and StÃ©phane Letz. > Thank you all for your help. > > Apart from MacOS build, this release features KDE integration for > NetworkEditor and Prototyper (so you can open network files from > Konqueror), MFCCâs added to Annotatorâs extractor example, and several > fixes (thanks James). > > FLTK module has been dropped and it is not being compiled by default. It > will be completely removed on the next release. Check out the changelog [5] > for more details. > > Next release will consist mainly on bugfixing towards 1.0, so please, tests > and report as many bugs as possible. > > [1] http://clam.iua.upf.edu > [2] http://mtg.upf.edu/ > [3] http://gti.upf.edu/ > [4] http://clam.iua.upf.edu/download-osx.html > [5] https://iua-share.upf.es/svn/clam/trunk/CLAM/CHANGES > > The CLAM crew. hi, I packaged clam-0.97 for SuSE. http://packman.links2linux.de/package/clam for the 0.98 I cann't find the sources ? the src-download site is outdated (0.96) second question: in this directory http://clam.iua.upf.edu/download/linux-ubuntu-feisty/ I can find a 0.98 tar.gz, but just to be sure: clam_0.98.0-1.tar.gz 281.30 Mb really 281MB ? What is in that tarball ? have fun oc2pus

18 years, 11 months

[linux-audio-dev] processing plugin standard wrapper

by Stefano D'Angelo

Hi all, who would be interested in writing a processing plugin standard wrapper (LADSPA, DSSI, LV2, VST, etc.)?

18 years, 11 months

[linux-audio-dev] [ANN] Mammut V0.57

by Kjetil S. Matheussen

Homepage: http://www.notam02.no/arkiv/doc/mammut/ Screenshot: http://www.notam02.no/arkiv/doc/mammut/mammut.png Changes 0.22 -> 0.57 --------------------- -Ported from gtk1 to juce. -Various bells and whistles -Binaries for windows and mac -Various other things

18 years, 11 months

[linux-audio-dev] CLAM 0.98 released

by David García Garzón

We are glad to announce CLAM 0.98 a.k.a. ‘Mac is here to stay’. CLAM[1] is a free-software, C++ framework for doing research and application development in audio and music. It also comes with a set of applications ready to use for non technical users. This is the first release not developed within the MTG [2] since its main developers now work at the GTI[3], also at the Universitat Pompeu Fabra. Still, CLAM is very indebted to the MTG people. Most of the work in this release was focused on having stable building, testing and packaging on Mac. Check out the MacOS download section[4] on the web for applications DMG’s. We have received valuable and stimulating input for the MacOS build from Christopher Tignor, Volker Schumacher, Eduard Aylon and Stéphane Letz. Thank you all for your help. Apart from MacOS build, this release features KDE integration for NetworkEditor and Prototyper (so you can open network files from Konqueror), MFCC’s added to Annotator’s extractor example, and several fixes (thanks James). FLTK module has been dropped and it is not being compiled by default. It will be completely removed on the next release. Check out the changelog [5] for more details. Next release will consist mainly on bugfixing towards 1.0, so please, tests and report as many bugs as possible. [1] http://clam.iua.upf.edu [2] http://mtg.upf.edu/ [3] http://gti.upf.edu/ [4] http://clam.iua.upf.edu/download-osx.html [5] https://iua-share.upf.es/svn/clam/trunk/CLAM/CHANGES The CLAM crew.

18 years, 11 months

RE: [linux-audio-dev] Job: Schematic Designer

by Hans de Roode

Hello Patrick, I have about 10 years experience designing all sorts of electronics, from power to RF electronics using Protel 99. Could I work from home here in New Zealand? Kind regards, Hans de Roode. -----Original Message----- From: Patrick Shirkey [mailto:pshirkey@boosthardware.com] Sent: Thursday, 8 February 2007 11:10 p.m. To: linux-audio-dev(a)music.columbia.edu Subject: [linux-audio-dev] Job: Schematic Designer Hi, I have an opportunity for an experienced PCB schematic designer to work with a large audio company on a contractual basis. Ideally you should have experience designing PCB schematics for mp3 players. You would also have to work with me and have laid back but efficient communication skills to get on with others in the company. If you are interested in knowing more please send me a resume and I will get back to you with more details. Cheers. -- Patrick Shirkey http://www.lau.linuxaudio.org http://www.boosthardware.com "Anything your mind can see you can manifest physically and then it will become reality..." - Macka B

18 years, 12 months

[linux-audio-dev] How to find out actual max priority available

by Jonathan Ryshpan

The functions sched_get_priority_max() and sched_get_priority_min() return the max and min priorities available for the scheduling policy in force (currently 99 and 1 for SCHED_RR). What method can be used to discover the max priority currently available to the current process, as controlled by /etc/security/limits.conf (or whatever controls it at the time of the inquiry)? In particular this is for the kernel 2.6.19-1.2895.fc6 running (naturally) under Fedora Core 6. Thanks - jon

18 years, 12 months

[linux-audio-dev] Job: Schematic Designer

by Patrick Shirkey

Hi, I have an opportunity for an experienced PCB schematic designer to work with a large audio company on a contractual basis. Ideally you should have experience designing PCB schematics for mp3 players. You would also have to work with me and have laid back but efficient communication skills to get on with others in the company. If you are interested in knowing more please send me a resume and I will get back to you with more details. Cheers. -- Patrick Shirkey http://www.lau.linuxaudio.org http://www.boosthardware.com "Anything your mind can see you can manifest physically and then it will become reality..." - Macka B

18 years, 12 months

[linux-audio-dev] sampler instrument definition standard needed

by Leonard "paniq" Ritter

hi everybody, i'm looking for a sampler instrument file format similar to .nki, .sf2 or akai instruments. is there an open standard existing already, perhaps even accompanied by some sort of library? -- -- Leonard Ritter -- http://www.leonard-ritter.com -- http://www.paniq.org

19 years

[linux-audio-dev] Python

by Silver Rock

Greetings, I've been studiyng python and some things are not that clear: 1- Is python too slow to efectivelly communicate with Jack? PyJack did not seem to work right, so i tried PySndObj's JackIO object. It did not behave as good as with connection with ALSA. (btw, I could not acess lots of objects in the SndObj library (like Ocil, Rand, while acessing normally Oscilli and Randh...) Does anyone know why?) 2- Python comes with the ossaudiodev module for communication with OSS; Alsa is compatible so it works. Shuld one use this module or use the pyalsasound? 3- pySonic - pySonic the wrapper for the FMOD sound library. but it is not opensource... is there a standard library for sound processing in projects like ardour. 4- Are any differences between 'r' and 'rb'; 'w' and 'wb' in: wave.open('file', 'r') wave.open('file', 'rb') wave.open('file', 'w') wave.open('file', 'wb') ?? 5- I found pySonic, that seems good but it is not open. MusicKit and PySndObj and omde. Ow yeah, and Pygame. Can anyone expose ihre personal experience and explain why? Please be nice, Claire

19 years

[linux-audio-dev] donations or sponsoring?

by Leonard Ritter

from http://www.leonard-ritter.com/donations_or_sponsoring I keep bouncing an idea in my head, thinking about how to strengthen the bonding between open source software developers and software users. How is a beginning open source project funded, usually? Most of the time not at all. The site features a donation button, and users are encouraged to donate. As an user, if you like an application very much, and would like to support its development, you might want to donate. However a donation has neither a direct connection to advancement of development, nor does it give you a right to influence the priorities of new features and bug fixes. It gives you no certainty that the application is still going to be developed - what if the developer is being hired for a more lucrative job? There is simply no contract, just a requirement of trust. As an open source developer, how are you going to sustain and finance ongoing development? You can not rely on ongoing donations. You also need to care for fund raising. You have only a small understanding of how many users deem your application to be important. There is no dependency between you and your users, meaning that the choices you make might not necessarily be choices embraced by the community. Again, there is no contract, just a requirement of trust. How to ensure a long-time interdependency between users and developers? Since a long time, the IT world knows multiple answers to this question: service contracts. A company using an open source product commercially would buy a service contract, which includes a warranty for the program and allows the company to prioritize bug fixes and addition of new features. In exchange, the company funds development. Of course, these contracts are of high volume, with a lot more money involved than what an average user would be able to spend. However an industrially used program has also less companies interested in it. My suggestion is to move this to the private software user / open source developer level. Users would be able to subscribe to a sponsoring contract, being able to choose the amount of money they want to pay per month or per year, starting at e.g. EUR 1/month or EUR 12/year. In exchange, each user has a right to get his bugs fixed within a period of 14 days, and also earns a right to influence the priority of new features suggested by the community. The low pricing will make sponsoring attractive and thus increase the number of sponsors. The more importance the project gains, the more developers will get out of this deal, the more dependent they get on subscriptions, the more bugs will be fixed, and the project will not be abandoned. Since most users will have the same problems, the amount of work required will not necessarily increase. Payment could be handled by Paypal, which also supports subscriptions. What do you think? -- Leonard Ritter -- Freelance Art & Logic -- http://www.leonard-ritter.com

19 years

Jump to page:

2026

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