Tobiah wrote: Thanks. It didn't compile out of the box, and it's not in debian or agnula :-( Might try later, though. Anybody knows of another linux tool that will set looppoints????? Actually right now I just need to set the loop point to the entire length of the sample. I would like soundfonts (and normally use that) but for some reason smurf and swami are both broken on my system. Something with compiled with another version of fluidsynth than the version linked. I will figure out the soundfont path someday, but I'm in makin-music-mood today. Basically I've had so many problems with smurf/swami that I'm wondering if there isn't another alternative, but google says not... As mentioned: csound -- peace, love & harmony Atte http://www.atte.dk

Tobiah wrote: Nice. A couple of questions (as I'm new to CCRMA): 1) The website specifically mentions that only redhat is supported. Aren't those apt-get's related to apt-get from a redhat machine? 2) If not what are the line(s) I should ad to my sources.list? 3) Will it break my system by grabbing a lot of stuff from CCRMA? I'm still surprised to find that none of the sample editors I tried seems to support editing and saving of looppoints. This leads me to the following rant: Why would I need a bunch of editors (I have at least the following installed: audacity, rezound, gnusound, xwave, snd, kwave, gnoise, ecawave and sweep)???? I'd much rather have one that did it all, did it well and was stable and easy to upgrade (= is in the debian tree). This is of course due to the nature of OSS development: people start a new project because they miss something in the existing projects or simply because they like to code. Still however much I love linux, this is one of the drawbacks at least when doing audio work: there're too many small projects that take time to develop, maintain and for the user to set up and try out. If it wasn't for csound and abcm2ps (that I consider my main music applications, I spend about 99% of my music-generating-time in one of those) I wouldn't be nearly as happy about linux as an audio framework as I am now. I acknowledge that some people like to spend time configuring, hacking, testing etc, but for me it's about producing music, and the two mentioned applications let me to exactly that. I realize that there's not a lot that can be don about it, just needed to get it off my chest :-) -- peace, love & harmony Atte http://www.atte.dk

On Thu, 06 Jan 2005 09:57:56 +0100 Walco <walco-linux(a)n--tree.net> wrote: There are actually two sides to this problem: - the file I/O layer to add loop points - the GUI requirements to add loop points Many of the above mentioned sound file editors use libsndfile (audacity, sweep, mhWaveEdit, possibly others) which has just recently gained suport for reading loop points. If writing of loop points was also added you would be much closer to your goal. Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid) +-----------------------------------------------------------+ "I invented the term Object-Oriented, and I can tell you I did not have C++ in mind." -- Alan Kay

On Thu, 2005-01-06 at 07:53, Tobiah wrote: Oh, I think I missed that. Debian apt (the original apt) uses .deb packages, for audio/music and Debian go to agnula.org... [although I think I read somewhere someone was working on a meta package manager that would enable cross-distribution installs!] -- Fernando

On Wed, 2005-01-05 at 15:42, Atte André Jensen wrote: I don't understand the question. Distros you can use directly with Planet CCRMA are RedHat 9 and Fedora Core 1, 2 and 3 (RH8.0 and 7.3 are still there but no longer supported). This is documented in the section that talks about configuring apt. On top of what distro do you want to install? I need more information. What system? Version? Planet CCRMA is just a collection of packages and as such it should not break anything (note I said "should", not "will" :-) An exception could be the kernels, they are optimized for low latency when possible (how much depends on which version of the kernel 2.4.x or 2.6.x). It is always possible (but not very likely) that they will not boot correctly in your particular hardware combination. The other option (on Fedora Core 2 or 3) is to use the stock kernel that comes with the distro but that is normally not good enough for low latency work. Depending on your system and the extra packages you might have installed it could be that Planet CCRMA packages could conflict with what you currently have, and then it is up to you to try to resolve the situation (with the help of apt, of course). -- Fernando