Pete,
Thanks so much for producing the Specimen program. I realize it's just the
start, but what start you've made. It's great.
I have been working on 3-D audio but also 1-D, 2-D instrument
generation (physically simulated strings and membranes --- not just
oscillators or FM synthesis). In the past I've generated full keyboards
of 16/44.1 samples and used SF2 fontbanks. You've enabled me to use 24/96
so I can do what I really want. Now there are limitations as to how well
this works, even with Jack, but I really do appreciate being able to
listen to these simulations. I'm looking forward to future releases,
and I hope to be able to provide some instrument-generation capability
which should work well with what you've done, freeing us from SF2's
and canned samples. I really like being able to simply assign WAV files.
One thing that would help a bit is to be able to assign a list of files
to notes as one can do in Vienna. If some forethought is put into place
into naming the files by the user, the entire keyboard full of samples
can be imported in one fell swoop. Now because BEEF is XML, I was able
to script it up easily enough. But some may not know exactly how to
do this. (Just another todo item for your undoubtedly long list!)
Thanks again! Great work.
[Sorry for cross-posting - feel free to forward around]
Dear all,
I'm sending this e-mail to all mailing lists/persons I think (often
with a less-than-optimal inductive process) could be interested in the
future of what's currently know as the "AGNULA Newsletter". If you
receive multiple copies of this e-mail or if you are not interested at
all in the subject, please excuse me and drop everything to the
bitbucket.
First, a bit of history. The AGNULA newsletter was born in Nov 2003
(more or less) as a service to our users who could be informed of new
software releases, events, research achievements in the field of music
& sound, with specific preference given to topics related to Libre
Software. You can see some more information here:
http://www.agnula.org/documentation/newsletter/
(you can find the past issues archive at the same URL).
The AGNULA Newsletter was never meant to be AGNULA-centric (although,
as was recently pointed out on our mailing lists, the naming we chose
could suggest that) but rather as a way to spread information about
the above mentioned topics - and of course to talk about AGNULA news,
if relevant.
Over the time we managed to send around 12 weekly issues of the
newsletter to our `newsletter-dist' mailing list subscribers, who
currently amount to 70. Honestly, given the young age of the
newsletter and the amount of manpower we've been able to put into it,
I'm not too dissatisfied with these numbers.
However, as the AGNULA project is reaching the end of its funded
lifetime I think it's high time that we think whether the AGNULA
Newsletter should become something bigger and better organized. What
does this mean?
Basically, I'd like to understand whether the wider GNU/Linux audio
(and video?) community is interested in turning the newsletter into a
"community project". What we would basically need is:
(a) that Libre Software project maintainers add the newsletter contact
address (currently newsletter-collect(a)lists.agnula.org, but this is
not cut in stone) so that when they send announcements about new
releases the newsletter team is notified more quickly;
(b) a (team of) editor(s) for the newsletter. I've been doing that
for the past months, but time pressure is growing and since my
position as AGNULA technical manager will end in April, I forecast I
won't have the same amount of time to dedicate to this project. A
native english speaker would be preferred, of course;
(c) a (team of) news pieces collectors/writers. The AGNULA project
can give (or try to give :) all the necessary instruments needed by
the newsletter team to coordinate their work - that means CVS, bug
tracking system, mailing lists, whatever;
(d) [optional] a (team of) translators to create nationalized versions
of the newsletter. This is of course a long-term goal and can be put
aside for the moment.
So, the question is: do you think this - turning the AGNULA Newsletter
into the "AGNULA Newsletter on Sound & Video" or even the "Newsletter
on Sound & Video", although I'd like the AGNULA name to remain
somewhere in the newsletter, if anything for sentimental reasons :) -
is a good idea?
If any of you think it is, I would encourage all of you to discuss the
topic on:
users(a)lists.agnula.org
http://lists.agnula.org/mailman/listinfo/users
If you are not subscribed to the mailing list, don't worry - I'll
authorize your messages as they arrive. Please put a clear sign that
you want to be put in Cc: for replies.
Thanks for your time and attention,
Andrea Glorioso
AGNULA Technical Manager
I think the LAU list server hates my machine. I haven't even seen my
original mail posted yet :(
> -----Original Message-----
> From: linux-audio-user-bounces(a)music.columbia.edu [mailto:linux-audio-
> user-bounces(a)music.columbia.edu] On Behalf Of Dave Griffiths
> Sent: Monday, February 23, 2004 3:23 PM
>
> Use the advantages free software gives you basically...
The line between use and abuse keeps moving!!!!! :)
matt
_________________________________________________
Scanned on 23 Feb 2004 23:56:25
Scanning by http://erado.com
(I'm moving this to linux-audio-user where the rest of this
discussion has been held. Please direct replies there)
On Tue, Feb 03, 2004 at 07:17:45PM +0100, Dave Griffiths wrote:
> At the risk of being pedantic, what is wrong with the sound/audio section of
> freshmeat?
A good question. At first glance not much.
But I do have the following gripes, and maybe some more
I haven't thought of yet ;-)
* Somewhat lacking in categories for audio/music apps.
As far as I can tell, submitters cannot influence what categories
their app should go in.
* You have to be logged in to submit anything.
In a smaller community, I think we can relax this requirement,
especially since admins will be able to undo any malicious changes.
* No source code available to the freshmeat software. (see the FAQ.)
I plan to make all my stuff open source.
* Freshmeat will probably never do cool stuff like automatically
track releases in the audio-specific distros.
* Freshmeat rejects "trivial" submissions. I can understand the reasoning,
but I don't agree with this. http://freshmeat.net/articles/view/198/
* Freshmeat is too large and too general.
It doesn't give me warm fuzzy LAD/LAU community feelings.
* Banner ads. Fooey.
And finally...
* They don't have a logo with a cute penguin wearing headphones.
This is unforgivable.
All that said, since they export their backend RDF files,
we should be able to re-use a whole lot of stuff from
freshmeat, and/or use their xml-rpc api to forward our own
submissions to freshmeat. Not sure about the best way to do all this,
but I'm sure Steve will help ;-)
> Dave's site is great because it is so low tech imho.
Low tech is great unless you're the guy that does all the work :-)
> I think for advocacy purposes and general coolness, it would be nice
> to have a
> site devoted to linux _musicians_ where we can upload and compare tracks and
> production methods. More of an extension of LAU...
Sure, the more the merrier.
But I don't want to lose focus. You can build that site if you want :-)
There has been talk on the consortium_p list of having linuxaudio.org
be a sort of portal for various subdomains which can be maintained
independently. So my proposal could live at something like
apps.linuxaudio.org or similar. A musician portal could either be
based on linuxmusician.com (yes, it exists, check it out!) or something
similar at e.g. musician.linuxaudio.org.
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's STRATA-MINIATURE THE END OF THE WORLD!
(random hero from isometric.spaceninja.com)
Anyone knows a good spectrum analyser? Preferably as an XMMS plugin, but
a JACK-aware thing is also acceptable.
I kinda like the default spectrum analyser that's displayed all the time
on XMMS' main window, with two exceptions:
- it's too small
- the frequency scale seems to be linear, not logaritmic
If it was bigger (much bigger) and if the frequency scale would have
been in an exponential progression (so that the octave width is
constant), that would be a great analyser.
There are some GL analysers packed with XMMS as plugins, but those are
mere eye-candy, i can't use them to actually get any useful information.
--
Florin Andrei
http://florin.myip.org/
Several undefined items are complained-of on boot: Something like
sound-special and a few others (which I did not catch quickly enough to write
down). Everything I have (that does work) loads OK after all.
> > I have binaries of Juno 1.0.1 and RS101 2.0-1.7 if you want them
> > - just let me know your preferred method of delivery. Unless
> > anyone knows of licence restrictions on redistribution of this
> > software - if so, please let me know.
>
> well, could you send me a copy?
I wrote that message quite a while ago. I'm afraid it seems there are
restrictions on redistribution of these binaries, which is why they
have disappeared from the internet. The authors have been asked to
make a libre software release of the code, but so far they have not
done so.
I would advise that you install libre software equivalents, which are
actively maintained or at least have source code available.
For the Juno emulator try Bristol:
http://www.slabexchange.org/index.cgi?DOWNLOAD
and for the sequencer you could try seq24:
http://www.filter24.org/seq24/
I'll cc this to the Linux Audio Users list. If anyone knows of other
Juno emulators, please let Darko know.
Cheers
Daniel
On Monday 23 February 2004 01:09, linux-audio-user-request(a)music.columbia.edu
wrote:
> > I had added my alsa devices (not of the "autodetected" types) to
> > modprobe.conf where it says to do so. I added them to the /lib/modules
> > version as well--this may be the reason. The question is where is it
> > correct to do so?
>
> Ususally, alsa module options go into /etc/modprobe.d/alsa
>
> From /etc/modprobe.conf:
>
> # This line loads the part of the modprobe configuration managed with
> # update-modules(8) and built from the contents of /etc/modprobe.d/.
> include /lib/modules/modprobe.conf
Oh, I put them there as well! Should I get them out of /etc/modprobe.conf?
The USB is very problematic. The uhci-hcd module needed to have snd-usb-audio
work does not shot down correctly. Indeed, an attempt to modprobe -r on that
will not terminate. Shutdown requires the big red switch (which apprently,
2.6 sits on and does a little cleanup once this is momentarily pressed). I
have to exclude this module till I know what to do about it!
I'll chime in here, because I think Mark was actually responding to my
sugggestion about multi-sample imports in Specimen.
I really like Pete's Specimen program, and I find it very useful. I
think it's amazing that he's done it so quickly as a first project.
Please just leave him alone, OK? He's already spoken; let it go.
We all have complex reasons for choosing our projects, choosing our
profession, marrying a certain person, etc. There is no way someone
else can step in and understand all those complex reasons. When
someone says "No!" it usually means at least "No."
Perhaps I should add that I have myself had many bad experiences in
trying to "channel a small amount of time" into a project. For me,
this has never worked out. In fact, I consider that kind of talk to
be a warning sign not to get involved. The more desperate the plea,
the more likely there is doom ahead.