Linux-audio-dev September 2002

linux-audio-dev@lists.linuxaudio.org

57 participants
46 discussions

[linux-audio-dev] Re: porting supercollider

by Ross Clement

Hi. Thanks to everyone for the advice. I've been poking around in a number of sources (including the Supercollider code), and it appears that I need to spend a bit more time on various learning curves. My immediate aim is to install WindowMaker and GNUStep on my linux box (tried to do so on a solaris box but encountered 'difficulties' :-(), and write a few simple gui applications in objective-c. After that, I can have another look at the task at hand. SC does use core-audio, and I've noted the advice to use JACK. Hopefully I'll resurface on this problem in a while! Cheers, Ross-c

22 years, 1 month

[linux-audio-dev] [OT] Linux soundapps pages updated

by Dave Phillips

Greetings: Yes, I finally got around to it. You all know the drill... http://linux-sound.org (USA) http://www.linuxsound.at (Europe) http://www.ymo.org/linuxsound/ (Japan) As usual the Japanese site will not be updated until after midnight tonight (their time). Enjoy ! Best regards, == Dave Phillips The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm The Linux Soundapps Site at http://linux-sound.org Currently listening to: John Coltrane, "After The Rain"

22 years, 1 month

[linux-audio-dev] LADSPA and TiMidity++

by Peter L Jones

Hi there, Do you (or the list) happen to know if anyone has considered making TiMidity++ a LADSPA host? I was thinking it might be fun to have a midi sequencer with a rather large library of MIDI controllers. I was thinking of using Non-Registered Parameters - one to select the LADSPA plug in (by number), one to set its position in the plugin chain, and as many more as is required to control it - unless someone fancies getting the LADSPA plugins allocated numbers by the MIDI Manufacturers Association... I did an archive search on "timidity" and found nothing -- is software sequencing off topic or is there somewhere else I should go to discuss changes to TiMidity++? Thanks, -- Peter

22 years, 1 month

[linux-audio-dev] porting supercollider

by Ross Clement

Hi. Thanks of the responses (I only just got the linux-audio-dev digest). As some people have noticed, my queries are at an early stage. No, I don't yet know too much about the way that the SC code works. (i) Yes, the gui is going to be the major problem. However, while I have only used the demo version, and not the latest version, I don't remember *that* much complexity in the gui. The graphic version may be more tricky. (ii) What I meant by a source code to source code cross-compiler is this: I don't want to be in the situation where I port one version of SC (providing that this ever happens, I'm still asking questions on the SC-dev list to find out the status of any linux port), and then have to do the same work for a later port. What I wanted to do is the following: Find the Mac-specific OS calls in the SC code, and understand what they do (sound, gui, and other). Then, write an extra module of code declaring the same functions, with linux specific code to achieve the same effect. Yes, I know this is likely to be complex, and may require the creation of a fairly large number of objects. Then, for things that cannot be so easily fixed, like OS and/or gui toolkit #includes, write a program that will modify the source code into a form so that any more missing bits can be fixed. If I can do this, then hopefully the effort in porting future mac OS releases would be much easier. I.e. unlike a traditional source code to source code cross-compiler that would compile (e.g.) fortran to C, I'll be compiling max-os specific c/c++ into linux c/c++, hopefully eased by the creation of a set of libraries of 'faked' mac os x calls. (iii) Basic linux audio code samples will be of use, as I need to understand both systems to do the patching described in (ii). So, I'll look some up. And, (iv), though I should have mentioned this more explicitly in my first email, I'm also interested to know if someone's doing this already. Cheers, Ross-c

22 years, 1 month

Re: [linux-audio-dev] Re: SysEx interface for softsynths [was Re: [linux-audio-dev] LADSPA and TiMidity++]

by John Lazzaro

> I didn't see a way to contact them via email, otherwise I would inquire > as to how to proceed in getting an ID. http://www.midi.org/about-mma/mfr_id_app.pdf ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro -------------------------------------------------------------------------

22 years, 1 month

[linux-audio-dev] [ANN]: New version of RTMix 0.48 now available for download

by ico＠fuse.net

Apologies if this is not going onto the right mailing list. I am mailing this from the ICMC2002 conference in Europe and am unable to have long-term access to the Internet, so I apologize if this has been posted in the wrong place. Anyhow, I would like to announce immediate availability of RTMix v.0.48 with binary, source code, and currently limited number of tutorials and docs, downloadable from: http://meowing.ccm.uc.edu/~ico/ (there is a non-flash version of the site for low-bandwidth users) New features and improvements since the version 0.16 are too numerous to state, so if you are interested in finding out more, please visit the website for more info. Hope everyone's summer was as eventful as mine :-) (I became a father of a beautiful son Sebastian and got an opportunity to present RTMix on one of the most prestigious international conferences associated with computer music :-) Greetings all! Sincerely, Ivica Ico Bukvic

22 years, 1 month

[linux-audio-dev] HDSP + cardbus

by D R Holsbeck

Ok so I got everything into a nice new rack, and quadruple checked my setup, and I still get a vocoder effect when trying ty play snything through my Digiface/cardbus interface. The Digiface works fine when connected to the pci interface, but not the cardbus interface. The modules, need the load/reload trick, to get jack to work with the pci or cardbus interfaces. So that seems nomal. I do get sound out when connected to the cardbus interface, but it sounds like it is being run through a very bad vocoder. I think somebody else has the same setup. H-DSP + cardbus, running. So Im pretty sure this should work. So if anybody has the magic incantations to make this work, I would be very appreciative of any words of wisdom they care to share ;-) System info Thinkpad A31 (P4 1.7g 256m ram) Alsa from cvs as of a month ago Debian 3.0 distro -- drh(a)niptron.com Great spirits have always encountered violent opposition from mediocre minds. -- Albert Einstein They laughed at Einstein. They laughed at the Wright Brothers. But they also laughed at Bozo the Clown. -- Carl Sagan

22 years, 1 month

[linux-audio-dev] Basic information

by Ross Clement

Hi. Could anyone point me to some very basic information to give me some idea of programming for sound in linux. I have previously programmed sound on Silicon Graphics machines and Sun machines. I'm thinking about linux in the context of *possibly* building a cross- compiler (source code to source code), or similar, for porting the Mac OS X version of SuperCollider to linux, depending on various things (I have just sent an email to the supercollider development list). Supercollider is at: http://www.audiosynth.com It is an amazing piece of software, truly amazing. Thanks in anticipation, Ross Clement.

22 years, 1 month

Re: SysEx interface for softsynths [was Re: [linux-audio-dev] LADSPA and TiMidity++]

by John Lazzaro

> Richard Bown <bownie(a)bownie.com> > > Perhaps we could either approach a small company that has an ID already or > reuse one that's pretty old and likely close to defunct (again with the > owner's consent). I wonder who controls their use or if it's a case of > suck-it-and-see? http://www.midi.org/about-mma/mfr_id_app.pdf Don't even need to join the MMA, just send in your yearly check for $200 and the ID is yours. There is another route, though -- if: http://www.borg.com/~jglatt/tech/midispec/id.htm Is to be believed, its consider OK for one manufacturer to clone the SysEx commands of another -- as long as the cloners don't extend the space in any way. So, if there's an existing MIDI device out there that has an acceptable SysEx command space for your project, you're free to clone it. Actually, I have a hard time believing that is true in this age of intellectual-property restrictions, but MIDI does predate that era by 20 years or so, so maybe its just a part of the culture ... I do know all sorts of devices advertise "JL Cooper compatibility", but I don't know if this means that they really return the JL Cooper SysEx bytes when you do an identity request ... ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro -------------------------------------------------------------------------

22 years, 2 months

Re: [linux-audio-dev] LADSPA and TiMidity++

by John Lazzaro

> david(a)gardena.net writes: > I was thinking about CCs, Program Change and stuff. Is there a > standard way of asking a synth for the names of it's patches, or > which CCs are assigned to what, for example? This does seem like the sort of device-independent info that could be a part of the General Information Univeral ID (0x06 Sub-ID), but I've never seen it -- maybe someone with the MMA document handy could check for sure. This sort of "request-reply" transaction is the sort of thing the GI UIDs do, such as the Identity Request/Identity Reply: http://www.borg.com/~jglatt/tech/midispec/identity.htm Identity Request/Identity Reply returns enough information for a patch editor to know what Manufacturer SysEx commands the device understands. Although a major undertaking, it is probably is in the realm of the doable to: -- Look at a bunch of synth manuals, and see the general device-dependent commands it uses to send back items like the name of the patch. -- Make a small "seed" database of SysEx commands for a few types, and write code that reads the database format. -- Make a networked system for motivated users to send you back updates for the database with their own synth. In other words, distribute the legwork of finding out all SysEx command variants for every type of synth, to the vast userbase :-). Sort of like CDDB, but on a smaller scale ... ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro -------------------------------------------------------------------------

22 years, 2 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 September 2002