Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7440 discussions

Re: [linux-audio-dev] FreeVSTi Compatibility List / VSTserver & FST

by Kjetil Svalastog Matheussen

> On Tue, Apr 20, 2004 at 06:55:48PM +0200, Christian Frisson wrote: > > > > What about the coexistence of VSTserver and FST on a same machine? Hard times > > for the moment, as long as VSTserver uses a custom-tuned version of Wine and FST > > the newest possible... The vstserver does not use a custom-tuned version of wine. But the latest version only compiles with a quite old version of wine, not the newest. So if you compile the vstserver while having the older version of wine installed, you can later install a newer version of wine. So thats probably the best way to run both vstserver and FST. --

20 years, 4 months

[linux-audio-dev] Creamware's Scope Fusion Platform on Linux/OSX

by Jan Weil

I was browsing the comments to this (Linux Audio) article[0] on OSnews.com when I found this link[1] to a Creamware Scope forum[2]. It states that Creamware's Scope Fusion Platform[3] is about to be ported to Linux and OSX. This is a community effort led by Frank Hund of Creamware and Willie Sippel (which is a funny name BTW) and they are looking for skilled developers. The posting is from March 19th. Jan [0]http://www.osnews.com/story.php?news_id=6720 [1]http://www.planetz.com/forums/viewtopic.php?topic=12010&forum=5&80 [2]http://www.planetz.com/forums/viewforum.php?forum=5&18745 [3]http://www.cwaudio.de/page.php?seite=scopeoverview&lang=en&submenu=home

20 years, 4 months

[linux-audio-dev] [ANN] seq24-0.5.0

by rob buse

Hey everyone! There is a new version of seq24 up. http://www.filter24.org/seq24/ I've added a few things people were asking for, here are the highlights: * external midi control of sequence patterns. * now registers loading and unloading of other alsa clients. * new method to queue a sequences on/off state at end of loop. * misc bug fixes. cheers!! rob buse ------------------------------------------------------ http://filter24.org art + technology _______________________________________________________ Sent through e-mol. E-mail, Anywhere, Anytime. http://www.e-mol.com

20 years, 4 months

[linux-audio-dev] [ANN} Aeolus

by Fons Adriaensen

The first release of Aeolus is now available at <http://users.skynet.be/solaris/linuxaudio> Enjoy ! -- Fons

20 years, 4 months

[linux-audio-dev] LADSPA 2.0 notes

by Steve Harris

These are just my thoughts and some notes about "LADSPA 2.0", the mail I sent yesterday was the notes I made in the meeting that everyone agreed to, so I didn't want to add my personal thoughts. Mentally prefix everything below with "I think...". I wasn't particuarly happy with the tone of the meeting report, it was a bit authoritarian for my tastes, but the LADSPA 1.x discussions weren't really going anywhere, and we had Paul and Stefan at the conference, Richard had made his feelings clear and we had a reaonable represenation from the various user/developer groups, so Paul declared us quorate ;) The .h file will contain a structure much like the 1.x one, but it will only have: * an identifier of some kind (like label/uid, maybe with stronger semantics) * a port count * a list of ports (float *'s and types, eg input control port etc.) The other stuff (names, hints, defaults etc.) will be sotred in an external metadata file. The float *'s obviously have to be in the struct as thier a point of reference, and the port types allow a host that just has the .so file to be compliant, even if it cant do anything intellignet, or present a UI. There will be a provided library for handling the metadata format. The format of the metadata is up for discussion, Ideally it should be something that is easy to parse so people dont have to use the ladspa-sepcific library if they dont want to. The library API will be very thick, eg get_defaults(plugin) returning an array of default values - that kind of thing - hiding the details of the metadata format. The reason for this supprising decision (well, I was supprised) was that everyone agreed that the current mecahnism where some details about the plugin are in the struct and some is external is not ideal, and the prevailing opintion is that external metadata is easier to extend without complicating the struct. There are lots of general, technical reasons why external metadata is preferable, but theres not space to go into them here. Several people expressed concens about the way that extending the struct we have now either blocks, or complicates future expansions we might want. The reason that LADSPA 2.0 will have no more features (than 1.1 + what we agreed in the meeting) is to allow it to be defined quickly and easily - if the fetures set is not up for discussion it should be easier to decide. There is the option for 2.1 etc. which can add more features once the dust from 2.0 has settled down. Things like the VST-LADSPA bridge that can generate plugins on the fly will need a mechanism that allows the dynamic plugin to squirt metadata generated dynamically into hte host, through an API. The exact API will depend on the metadata format. - Steve

20 years, 4 months

[linux-audio-dev] [ANN] Ecasound 2.3.3 released

by Kai Vehmanen

Hello all, this year's first stable Ecasound release is now out! Most of the final tuning for this release was done last Sunday while watching and listening to the last sessions of 'laconf2'. Many thanks to all the organizers and participants! And special thanks for the excellant net coverage of the event! But now, back to the 2.3.3 release -- here are the details: 1. Summary of changes Bugs in ecasignalview, effect presets, NetECI protocol parser and the C ECI implementation have been fixed. Many build system issues, including errors in building against libsndfile-1.0.4 and older, have been resolved. A separate section covering ecasound.el, the ecasound emacs interface, has been added to the Ecasound Control Interface Guide. The Ecasound User's Guide has also been updated. --- 2. What is Ecasound? Ecasound is a software package designed for multitrack audio processing. It can be used for simple tasks like audio playback, recording and format conversions, as well as for multitrack effect processing, mixing, recording and signal recycling. Ecasound supports a wide range of audio inputs, outputs and effect algorithms. Effects and audio objects can be combined in various ways, and their parameters can be controlled by operator objects like oscillators and MIDI-CCs. A versatile console mode user-interface is included in the package. Ecasound is licensed under the GPL. The Ecasound Control Interface (ECI) is licensed under the LGPL. --- 3. Changes since last release * Preset handling fixes: When saving chainsetups containing presets, values of preset parameters were not saved correctly. Also problems with presets containing untitled parameters have been fixed. * New ecasoundrc(5) setting "autodetect" for "default-output" has been added. When selected, libecasound will check for JACK support and whether a JACK server is running, if not found, check for ALSA, then OSS, and finally fallback to using "rtnull". This feature is especially useful to apps such as ecaplay. * Fixes to ecasignalview: Proper cleanup after receiving an interrupt from keyboard (SIGINT/CTRL-C) has been added. Originally tested on FreeBSD, but helps on Linux as well. * Ecasound Interactive Mode (EIAM) updates: Added new command 'map-ladspa-id-list' to allow listing the available plugins by their unique ID numbers. A special case value of '-1' is now understood by 'cs-set-length'. This allows undoing any previously set length value. * Ecasound Control Interface (ECI) updates: Added a section on ecasound.el - the Ecasound emacs interface - to the ECI Guide [1]. Several bugs have been fixed in the ECI C implementation. A serious bug in NetECI protocol parser, that caused parsing long (over 32 chars) commands to fail, has also been fixed. * Documentation updates: The Ecasound User's Guide [2] has been updated. Also, a bug in the groff source for the ecasound(1) man page that prevented man from showing the last five pages of the document, has been fixed. * Build system fixes: Problems in building against libsndfile-1.0.4 and older have been fixed. 'libecasound-config --libs' has been fixed to return the full list of external libraries. Based on recent discussions on linux-audio-dev, minor changes have been made to processing CFLAGS, CXXFLAGS and LDFLAGS. Full list of changes is available at <http://www.wakkanet.fi/~kaiv/ecasound/history.html>. --- 4. Interface and configuration file changes * ecasoundrc(5) - "default-output": new value "autodetect" (default) --- 5. Contributors Patches - Accepted code, documentation and build system changes Michael Ewe (2) -- bugfixes to ecasignalview and ECI C impl Mario Lang (1) -- section on ecasound.el to ECI Guide Eric Rzewnicki (1) -- set of updates to Ecasound User's Guide Kai Vehmanen (n/a) -- various Bug Hunting - Reports that led to bugfixes (items closed) Pierre Lorenzon (1) -- bugs in ecasound's daemon-mode protocol parser Jan Weil (1) -- cs-save dit not save preset parameters Feature suggestions - Ideas that led to new features (items) Jan Weil (2) -- map-ladspa-id-list command, -t:1 option --- 6. Links and files Web sites: http://www.eca.cx http://www.eca.cx/ecasound Source packages: http://ecasound.seul.org/download http://ecasound.seul.org/download/ecasound-2.3.3.tar.gz Referenced documents: [1] - http://www.eca.cx/eci-guide [2] - http://www.eca.cx/eca-u-guide Distributions with maintained Ecasound support: Agnula - http://www.agnula.org AltLinux - http://www.altlinux.com Debian - http://www.debian.org FreeBSD - http://www.freebsd.org/ports/audio.html Gentoo Linux - http://www.gentoo.org Mandrake - http://www.mandrake.org PLD Linux - http://www.pld.org.pl SuSE Linux - http://www.suse.de/en Contrib Packages and Add-On Distributions: AudioSlack for Slackware - http://www.audioslack.com PlanetCCRMA for RedHat/Fedora - http://www-ccrma.stanford.edu/planetccrma/software Thac's RPMs for Mandrake - http://rpm.nyvalls.se Note! Distributors do not necessarily provide packages for the very latest Ecasound version. --- http://www.eca.cx Audio software for Linux!

20 years, 4 months

[linux-audio-dev] (web-based) interactive sound art?

by Niklas Werner

Hi .*, I am doing my PhD at the University of Waikato's Music Department, NZ with Ian Whalley. I am going to develop a Web-based interactive sound art system allowing composers/players to incorporate aesthetic approaches from electronic music, net.art, sonic art and soundscapes. I am trying to get away from using MIDI in favour of OSC and direct DSP on the audio (That's why I'm thinking of using SuperCollider). I will direct much attention to the musical quality of the system's output, possibly in exchange for not getting a decent interface done. Features will basically be: - "off-line" interface for composers to create sound art pieces/installation for the web (this is where there must be a framework to allow "composition" of the Net's peculiarities (latency, jitter, interaction between the players, etc...) in addition to the usual musical parameters - on-line interface for "players" to mess around with the installation - All that probably in a p2p approach using a server only for net-address brokerage An outdated proposal of this can be found at: http://www.niklaswerner.de/Assets/PhD-Thesis-Expose_EN.pdf Is anybody already working on such a beast (or similar, of course) or knows anybody who is? (I am aware of quintet-net, peersynth, FMOL, jam2jam, webdrum/JSyn, Dase, Lemu and some others and have contacted their authors) Is SuperCollider really up to that challenge or does another programming language spring to anybody's mind? Have fun* Niklas

20 years, 4 months

Re: [linux-audio-dev] wcnt-1.1z released!

by James W. Morris

>From: martijn <martijn(a)pacno.net> Date: Tue, 4 May 2004 02:05:55 +0200 >Once upon a Thu, Apr 15 2004, James W. Morris hit keys in the following >order: > > >Anyway, thanks for applying the gcc3 patches. I ran into only two >includes > > >without use namespace declarations, and it also appears gcc3 tries to >be > > >intelligent and interprets "or" as "||" :S > > 'S Ok. -- Hermmh, not quite sure what you're getting at ? >Oh, i forgot the patches, here they are. >Martijn. Cheers for your help. I decided to try mandrake 10 the other day, got bored of Debian Stable. Mainly to try out gcc3.3 and kernel2.6 (too long to download on 56k) So I've now discovered how gcc interprets 'or' as '||' which I feel quite annoyed and let down by! I did n't realise what you meant. I've also discovered the other missing using namespace std's. (I thought I could get away with putting them in files which were included by others.) I'll get wcnt compiling with gcc3.3 and just put the whole thing up with some new examples. I've got some examples with 10 waveforms (coo!) and some with 20 (a world record for wcnt!) which would sound pretty good if it were not for artifacts: bummer. expect: withinish thish weekishn || next. ~(sirromseventyfive)~ _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

20 years, 4 months

Re: [linux-audio-dev] wcnt-1.1z released!

by James W. Morris

Ayup, >From: martijn <martijn(a)pacno.net> Date: Thu, 15 Apr 2004 13:50:33 +0200 >Once upon a Wed, Apr 07 2004, James W. Morris hit keys in the following >order: > > Announcing for the last time this year the new release of Wav Composer >Not > > Toilet. >the last? are you not gonna announce it any more, gonna change the name, or >stop working on it altogether? oh, i read it on the website... Just giving it a break so I can do some art/painting - it's been too cold in the garage/studio in Winter. Time management. Add a pinch of salt. >Anyway, thanks for applying the gcc3 patches. I ran into only two includes >without use namespace declarations, and it also appears gcc3 tries to be >intelligent and interprets "or" as "||" :S 'S Ok. -- Hermmh, not quite sure what you're getting at ? >Also, the online example makes the not-so-toilet to segfault. all other >examples are fine. Haven't had the time to investigate, but here's the >backtrace: >[>--snip--<] >Creating synth module kick_sampler >[>--snip--<] Oh. I'll download and test it again, I did make some very minor changes via sourceforge shell after I'd uploaded it. The typical instance of a segfault occurring with the sampler module is giving it a wavfilein lacking a wav file (either wrong path/not set) - although I thought I had put in validation code to check for this and stop. Did you place the example in wcnt-1.1z/examples dir as suggested, and/or change the path to the samples it needs so it can get to them? Cheerio. James. ~(sirromseventyfive)~ P.S. Don't expect the sampler to work with a start/end positions of zero! _________________________________________________________________ It may not be easy,but it's fast and it's free (beer/freedom), get Linux today! _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

20 years, 4 months

Re: [linux-audio-dev]converting old pc hardware to a live music performance

by Green

I've also been playing around with real-time audio fx using a VIA mainboard and MIDI for the controls.. Here's some documentation of a project I did with this: (ecasound, analog controls->MIDI, ladspa effects...) http://4ms.org/influx9/ One obstacle I've had is boot time! It's annoying to have to wait 30 seconds for the thing to boot, and if the power is interrupted during a live preformance..ugh. Sure I could pare down a little more the init.d, but how do pro embedded systems boot in a matter of seconds? Mounting the fs read-only is a good idea, but does anyone have other tips for making it more like an old-time analog fx unit (power-on==>instant sound, power-off==>no harddisk damage)? BTW, i'm new to this list, I searched and browsed the archives a bit but didn't find this discussion... please direct me if this has already been talked about! Dann >I have a live performance setup I use with my band. I >used one of those tiny VIA motherboards and a Midiman >UNO usb <-> midi adapter. > >It seems like it's a good idea to use a flash card and >that's what I did at first, but flash cards peter out >after a certain number of writes. If you want to go >that route, I'd suggest maybe having the partitions >mounted read-only.

20 years, 4 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