Linux-audio-dev July 2004

linux-audio-dev@lists.linuxaudio.org

104 participants
77 discussions

[linux-audio-dev] MP3 timestretch in real time

by Suzana Mesquita de Borba Maranhao

Hi Anybody knows any software that enable MP3 timestretch in real time? I want no file conversions. In addition, I prefer a software that process the MP3 stream and not the stream MP3 after decoding process. Anybody knows any algorithm for this? Sorry by my english faults. Regards, Suzana

19 years, 9 months

[linux-audio-dev] Re: [announce] [patch] Voluntary Kernel Preemption Patch

by Andrew Morton

Ingo Molnar <mingo(a)elte.hu> wrote: > > I took a > look at latencies and indeed 2.6.7 is pretty bad - latencies up to 50 > msec (!) can be easily triggered using common workloads, on fast 2GHz+ > x86 system - even when using the fully preemptible kernel! What were those workloads? Certainly 2.6+preempt is not as good as 2.4+LL at this time, but 2.6 isn't too bad either. Even under heavy filesystem load it's hard to exceed a 0.5 millisecond holdoff. There are still a few problem in the ext3 checkpoint buffer handling, but those seem pretty hard to hit. I doubt if the `Jack' testers were running `dbench 1000' during their testing. All of which makes me suspect that the problems which the `Jack' testers saw were not directly related to long periods of non-preemption in-kernel. At least, not in core kernel/fs/mm code. There have been problem in the past in places like i2c drivers, fbdev scrolling, etc. What we need to do is to encourage audio testers to use ALSA drivers, to enable CONFIG_SND_DEBUG in the kernel build and to set /proc/asound/*/*/xrun_debug and to send us the traces which result from underruns. As for the patch, well, sprinkling rescheduling points everywhere is still not the preferred approach. But adding more might_sleep() checks is a sneaky way of making it more attractive ;) Minor point: this: cond_resched(); function_which_might_sleep(); is less efficient than function_which_might_sleep(); cond_resched(); because if function_which_might_sleep() _does_ sleep, need_resched() will likely be false when we hit cond_resched(), thus saving a context switch. Unfortunately, might_sleep() calls tend to go at the entry to functions, whereas cond_resched() calls should be neat the exit point, or inside loop bodies.

19 years, 10 months

[linux-audio-dev] [ANN] PHAT version 0.1.0

by Pete Bessman

I'm pleased to annouce, after a solid month of heated debate with X11, the initial public release of PHAT, the PHat Audio Toolkit. From the website (www.gazuga.net/phat.php): "PHAT is a collection of GTK+ widgets geared toward pro-audio apps. The goal is to eliminate duplication of effort and provide some standardization (well, at least for GTK+ apps). It's open source software, licensed under the GNU GPL, version 2.0 or later." The debut and flagship widget is the fanslider, designed by Thorsten Wilm's. The LAU folks may not be too interested in the library as such, but might like to play around with this widget (hence the cross post). It comes with a demo program, "phatfantest," which displays the sliders in all their glory. Tarball: www.gazuga.net/phat-0.1.0.tar.gz Docs: www.gazuga.net/phat/index.html Let's actually go somewhere with all this debate about widgets and standards and such. Contributions are welcome (hint hint). I hope we can put an end to the Linux Usability Curse, at least in our own little neck of the woods. -- Pete www.gazuga.net ===================================================================== "I saw the movie 'I, Robot' recently, a film based loosely on a book written by science fiction author Isaac Asimov. In case you're not familiar with Asimov's writing, here's a list of things the movie had in common with the book: * The title." [maddox.xmission.com] =====================================================================

19 years, 12 months

Re: [linux-audio-dev] [ANN] PHAT version 0.1.0

by Taybin Rutkin

Sounds neat. Are there any screenshots? Taybin -----Original Message----- From: Pete Bessman <ninjadroid(a)gazuga.net> Sent: Jul 31, 2004 9:39 PM To: linux-audio-user(a)music.columbia.edu, linux-audio-dev(a)music.columbia.edu Subject: [linux-audio-dev] [ANN] PHAT version 0.1.0 I'm pleased to annouce, after a solid month of heated debate with X11, the initial public release of PHAT, the PHat Audio Toolkit. From the website (www.gazuga.net/phat.php): "PHAT is a collection of GTK+ widgets geared toward pro-audio apps. The goal is to eliminate duplication of effort and provide some standardization (well, at least for GTK+ apps). It's open source software, licensed under the GNU GPL, version 2.0 or later." The debut and flagship widget is the fanslider, designed by Thorsten Wilm's. The LAU folks may not be too interested in the library as such, but might like to play around with this widget (hence the cross post). It comes with a demo program, "phatfantest," which displays the sliders in all their glory. Tarball: www.gazuga.net/phat-0.1.0.tar.gz Docs: www.gazuga.net/phat/index.html Let's actually go somewhere with all this debate about widgets and standards and such. Contributions are welcome (hint hint). I hope we can put an end to the Linux Usability Curse, at least in our own little neck of the woods. -- Pete www.gazuga.net ===================================================================== "I saw the movie 'I, Robot' recently, a film based loosely on a book written by science fiction author Isaac Asimov. In case you're not familiar with Asimov's writing, here's a list of things the movie had in common with the book: * The title." [maddox.xmission.com] =====================================================================

19 years, 12 months

[linux-audio-dev] ANNOUNCE: Rosegarden-4 0.9.9 released - now officially in beta!

by Chris Cannam

ROSEGARDEN GOES BETA! - 0.9.9 RELEASED The Rosegarden team are delighted to announce the 0.9.9 release of Rosegarden 4, an audio and MIDI sequencer and musical notation editor for Linux. http://www.rosegardenmusic.com/ This release is feature complete for 1.0 and marks the start of official beta testing. Rosegarden is one of the most comprehensive Linux music software projects, and is the only Linux application to offer full composition and recording capabilities to musicians who prefer to use classical notation. We encourage anyone who may be interested in using the 1.0 release to try out 0.9.9 and provide bug reports and other feedback via the mailing lists and bug trackers. http://www.rosegardenmusic.com/getting/ http://www.rosegardenmusic.com/support/ New features of the 0.9.9 release include: o Plugin synth support using the DSSI system (http://dssi.sf.net/). Rosegarden now comes with integrated sample-synchronous synth support, with LADSPA effects and mixer routing for synth tracks, and configuration both through the built-in plugin GUI and plugins' own native GUIs. o Triggered segments for pattern sequencing & performable ornaments o New menu layout, many new keyboard shortcuts for everyday usability o Recording from multiple MIDI sources o Cautionary accidentals and configurable key-signature cancellations o Pedal marks, mordents, trill lines, repeat bars o Fine positioning and visibility control of notation elements o Visual metronome o Several new example files Other features of interest include: o Piano-roll, score, event list and track overview editors o MIDI and audio playback and recording with ALSA and JACK o JACK transport support for synchronisation with other software o Ability to build and run without JACK support for MIDI-only use o Audio plugin support using LADSPA o Score interpretation of performance MIDI data o MIDI and Hydrogen file import o MIDI, Csound, Lilypond and MusicXML file export o Clear, consistent and polished user interface o Shareable device (.rgd) files to ease MIDI portability o User interface in Russian, Spanish, German, French, Welsh, Italian, Swedish and Estonian, as well as UK and US English. Rosegarden is Free Software under the GNU General Public License. Chris

19 years, 12 months

[linux-audio-dev] [ANN] ladspar 0.1

by Hans Fugal

ladspar is a Ruby module for using LADSPA plugins. Here's a short example: --- require 'ladspa' require 'narray' # load the CMT library cmt = LADSPA.load_library('cmt') # get an instance of the amp_mono plugin amp_mono = cmt.plugins.find {|p| p.label == 'amp_mono'}.instantiate(44100) # The ports are Gain, Input, and Output. amp_mono.ports[0].connect_port(1.5) # gain input = NArray.sfloat(44100) amp_mono.ports[1].connect_port(input) output = NArray.sfloat(44100) amp_mono.ports[2].connect_port(output) amp_mono.activate if amp_mono.has_activate # prep the input data ... amp_mono.run amp_mono.deactivate if amp_mono.has_deactivate amp_mono.cleanup --- This is the first release of ladspar; I consider it beta quality. I have put it through its paces (more test code than swig code), but I am the only one to have tested it. Nevertheless I think it is usable, and I am eager to fix any bugs you may find. Go grab it at http://rubyforge.org/projects/ladspar -- .O. Hans Fugal | De gustibus non disputandum est. ..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460

19 years, 12 months

[linux-audio-dev] Re: OSC for GUI-Engine communication

by Juhana Sadeharju

>From: Dave Robillard <drobilla(a)connect.carleton.ca> > >The question is, which implementation is best? All I can find is >Steve's liblo, libosc++, and the 'official' OSC kit. What are the >advantages/drawbacks of each? I can find very little information on any >of them. Last I checked OSC, it had Lisp/Scheme like syntax. Don't know if that is a drawback --- anyone? Has anyone used MPI (Message Passing Interface) for this? People use these for high performance parallel computations in Linux clusters. MPI itself is a standard supported by academic and by vendors. MPI is used, e.g., in supercomputers. See, e.g., http://www.csc.fi/reports/pc-cluster/Finalreport.pdf Juhana -- http://music.columbia.edu/mailman/listinfo/linux-graphics-dev for developers of open source graphics software

19 years, 12 months

Re: [linux-audio-dev] LADSPA "Unique" IDs

by Taybin Rutkin

This bit ardour a little while ago when one plugin author changed the number or ordering of their ports without changing the ID number. Taybin -----Original Message----- From: Steve Harris <S.W.Harris(a)ecs.soton.ac.uk> Sent: Jul 29, 2004 4:00 AM To: The Linux Audio Developers' Mailing List <linux-audio-dev(a)music.columbia.edu> Subject: Re: [linux-audio-dev] LADSPA "Unique" IDs On Thu, Jul 29, 2004 at 09:17:03AM +0100, Chris Cannam wrote: > On Thursday 29 Jul 2004 12:42 am, Dave Robillard wrote: > > I vaguely remember a discussion here about LADSPA ID's (unsigned > > long UniqueID) not actually being globally unique to a plugin like > > the header implies, but I can't find it in the archives. > > > > So.. unique or not? Basically I need to know what the "proper" > > information is to send a synth in order to load a plugin. > > The outcome was that (i) LADSPA _does_ appear to specify that the > unique ID should be globally unique, but (ii) it's not in practice > easy to guarantee that, for generated or wrapper plugins (e.g. a vst > wrapper that doesn't know how many plugins will be in the .so until > it's counted your VSTs), and (iii) some plugin developers (Steve!) > thought the LADSPA docs said differently anyway, so it's possible > they may have made plugins with duplicate IDs. Personally I've only done that by accident! But it has happened. My buil process now has a bozosity checker run, that looks for silly mistakes, like two plugins with the same ID. I do learn eventually :) > /* This identifier can be used as a unique, case-sensitive > identifier for the plugin type within the plugin file. Plugin > types should be identified by file and label rather than by index > or plugin name, which may be changed in new plugin > versions. Labels must not contain white-space characters. */ > > To me this makes it pretty plain that filename and label is at least > intended to be a valid unique ID within your filesystem, and in > practice I'd expect it to be an effective id for the plugin anywhere > in the world. I think it should be: local filenames are unique, and labels are required to be unique in the file. A problems with using UIDs for this kind of thing is that they dont have to change with plugin versions, so you can end up with two plugins iwth the same ID and ports, but different paths nad different effects/bugs, and you dont know which one to load. > One problem is that there seems to be an informal understanding that > if you change the port specifications for a plugin you should also > change its unique ID, but I don't think there's any such > understanding for labels, so you don't have the reassurance of > knowing you're using the version you actually intended. All this and more :) - Steve

19 years, 12 months

[linux-audio-dev] Perl / Audio::LADSPA lib

by Joost Diepenmaat

Hello everybody, At http://hortus-mechanicus.net/perl/audio-ladspa/ you can find my attempts at making a LADSPA interface for Perl. The LADSPA API should be completely supported, but at the moment the system only supports mono audio out (via Audio::Play) and no way of reading/writing audio files. There is also a crude GUI at: http://hortus-mechanicus.net/perl/audio-ladspa/rack.perl.txt To use the GUI you need to have perl-tk installed. Bugreports / missing features welcome. Joost Diepenmaat. --- README follows --- Audio::LADSPA ============== This is a set of extensions to host LADSPA plugins, you can query them, or apply them to audio data. INSTALLATION To install this module type the following: perl Makefile.PL make make test make install Or, if you prefer the CPAN installer, type: perl -MCPAN -e'install Audio::LADSPA' Which will fetch, make and install the module for you. DEPENDENCIES LADSPA dependencies: The tests specifically need the demo plugins from the ladspa_sdk package, with LADSPA_PATH pointing to the directory where they are installed. You do not have to set the LADSPA_PATH environment variable if your LADSPA plugins are located in either /usr/lib/ladspa or /usr/local/lib/ladspa, but you will be warned when the modules are loaded. You'll probably want to set it anyway, because most other LADSPA hosts need it. You can download the sdk from from http://www.ladspa.org/ Debian users can use "apt-get install ladspa-sdk" Alternatively, you can skip the tests, but these modules are of no use without at least SOME plugins installed. CPAN dependencies: Also, this extension requires the following Perl modules; Test::More, Audio::Play, Scalar::Util, Data::Uniqid and Graph::Directed Install them first from CPAN. Alternatively, if you're installing using the CPAN or CPANPLUS shell, this can be taken care of automatically. COPYRIGHT AND LICENCE Copyright (C) 2003 - 2004 Joost Diepenmaat This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See the COPYING file for more information

19 years, 12 months

[linux-audio-dev] LADSPA "Unique" IDs

by Dave Robillard

I vaguely remember a discussion here about LADSPA ID's (unsigned long UniqueID) not actually being globally unique to a plugin like the header implies, but I can't find it in the archives. So.. unique or not? Basically I need to know what the "proper" information is to send a synth in order to load a plugin. At the moment I'm sending filename and index, which I don't think is ideal. (The synth could be running on a completely seperate machine, so the sender and receiver might not have the same LADSPA plugins around...) Thanks, -DR-

19 years, 12 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 July 2004