Aqualung: Music Player for GNU/Linux
http://aqualung.sf.net
Release 0.9beta5
It is our greatest pleasure to announce the fifth official beta
release of Aqualung. Some features you'd rarely stumble upon in
other players (at least not too many of them at once):
* Gapless playback (designed for this from the ground up)
* High quality decoders (eg. libMAD for mp3), many supported formats
* High-quality sample rate conversion support via libsamplerate
* LADSPA support
* Music Store for organizing your music
* And much, much more...
We hope you will enjoy this release. The release ChangeLog follows below.
2006-06-30 Tom Szilagyi <tszilagyi at users dot sourceforge dot net>
* Aqualung 0.9beta5
http://aqualung.sf.net
This is a new milestone release after 17 months of silent
development. Large parts of the program have been rewritten,
refactored, fixed, etc. A multitude of new features have been
added to the software, which now weighs into Open Source with
about 30,000 lines of GPL'ed source code, all written by a handful
of free-time developers (no, you won't need your whole hand).
It won't make too much sense to precisely list every change made
to the sources during this period - the list would be prohibitively
lengthy. For the curious, the mailing list archive is recommended.
The most important, high-level changes are summarized below.
* Group CDs in the Playlist via "Album mode". Shuffle between
records but play their contents in order!
* Statusbars in Playlist and Music Store display statistics and
other data.
* Multiple Music Stores are supported - useful for separate
genres, file formats or for music mounted from different file
servers via NFS.
* CDDB support!
* iFP driver support for integrating with iRiver HW players!
* Completely reworked Settings dialog, the new control center!
* Embed Playlist into Main window for a more compact look!
* Search facility for Music Store and Playlist.
* Add support for Musepack (via libmpcdec), Monkey's Audio, Ogg Speex.
* Rudimentary album art (cover display) support.
* RVA-related work, improved metadata support.
* Fixed a boatload of bugs concerning cyrillic filenames, etc.
* MP3 improvements (file recognition, clipping, seeking...)
* Better fault tolerance in Ogg Vorbis decoder.
* Various GUI fixes, new command line options, etc, etc.
* Improved build system for skins, icons, etc.
* New skins (Ocean, Plain), new Logo (see About box)! ;-)
* Better RT behaviour with Jack output.
* Compiles and runs on AMD64 (thanks to Mark Knecht for testing)!
Hi peeps.
I've been writing an app that requires volume envelopes. I've
implemented the envelope part myself, but I was wondering if there
was a library about to do it.
I ask because I realised that probably everyone on this list has
written something that uses envelopes, and probably written it
better and with more features than I have.
More generally, is there a library/toolkit of audio bits and bobs
about?
James
Thanks for clarifying the licensing issues. I think I knew that at some point.
What are the odds of changing the FST license to GPL-with-exceptions?
> what parts of the full 2.0 spec are you thinking about?
Ack. You got me; I don't know enough about the spec to have an answer. But
Kontakt doesn't save it's state when asked nicely by any linux VST host I'm
aware of. I'll start by trying to fix that.
> > There doesn't seem to be any tutorial-type documentation reguarding VST.
> there isn't. the vst-plugins mailing list is full of people endlessly
> seeking clarification of different aspects of the API. nobody has
> definitive answers.
I had feared this. To make matters worse, I've not done any serious audio
development before. Bits in, bits out, though, isn't it? :)
-Forest
On Fri, Jun 30, 2006 at 06:46:39AM -0700, Mark Knecht wrote:
>
> Tom,
> Maybe you and Peter should post these on the Aqualung download
> site? Maybe they are there already?
The scripts were never intended to be used by a large audience
(large by any standard), however, if there is popular demand for
them, we might just post them to the website so everyone has easy
access to it.
We anticipate that this aspect of Aqualung (ie. mass import,
mass tagging, etc) will improve greatly by the time we release
our next beta.
Tom
On Fri, Jun 30, 2006 at 01:34:31PM +0300, Sampo Savolainen wrote:
>
> Great news! Aqualung is starting to look like a very good option for a music
> player.
Thanks. We still see a number of areas where great improvement is needed,
but we couldn't wait more before a real release (many people won't use our
CVS tarballs ever, even though their contents are pretty much the same).
> A few gripes though:
> a) I would like to have a notification area icon to show/hide aqualung
> b) There seems no easy way to import my existing collection of music.
> I can select individual files from one directory, but whole
> directories. My collection is divided into directories and
> subdirectories. (artist/album/track.ogg)
These are indeed noted, and planned for the next release.
> Also, I found the metadata option a bit confusing: why doesn't aqualung use
> metadata (id3's, etc.) provided by the audio files automatically? I had to
> enable it explicitly.
The defaults may be wrong, but once you enable autodetection, the program
will remember your choice. (It is off by default so metadata won't accidentally
override data from the Music Store -- this area may still need refinement.)
Thanks for the feedback,
Tom
Quoting Tom Szilagyi <tomszilagyi(a)gmail.com>:
> Aqualung: Music Player for GNU/Linux
>
> http://aqualung.sf.net
>
> Release 0.9beta5
>
>
> It is our greatest pleasure to announce the fifth official beta
> release of Aqualung. Some features you'd rarely stumble upon in
> other players (at least not too many of them at once):
Great news! Aqualung is starting to look like a very good option for a music
player.
A few gripes though:
a) I would like to have a notification area icon to show/hide aqualung
b) There seems no easy way to import my existing collection of music.
I can select individual files from one directory, but whole
directories. My collection is divided into directories and
subdirectories. (artist/album/track.ogg)
Also, I found the metadata option a bit confusing: why doesn't aqualung use
metadata (id3's, etc.) provided by the audio files automatically? I had to
enable it explicitly.
Just my 0.02€
Sampo
hi guys!
due to post-academic stress syndrome (read: i'm getting a real job ;), i
would like to resign from being maintainer of the linux-audio-* lists.
lately i haven't been able to keep up with the lists as much as i would
have liked to, and i feel it's time for new people to take over.
if you'd like to volunteer, holler now :)
i'm leaving on a four-week iceland trip in about a week, and if no-one
has expressed their interest by then, i would be very glad if somebody
could at least step forward to tend to the lists for a month or so...
as an added bonus, there is also the job of cleaning up the old
lad.linuxaudio.org page, throwing out all the obsolete stuff (i.e.
everything except the subscription information and the contrib/ section)
and maybe linking to all the excellent documentation efforts elsewhere :)
i hope to stay in contact with the linux audio community in the future,
and i will definitely do some volunteer work for next year's linux audio
conference in berlin, but my life has moved away from studio work to
live audio engineering, systems administration and (ugh) web content
management...
all the best,
jörn
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
if you are a free (as in "free speech") software developer
and you happen to be travelling near my home, drop me a line
and come round for a free (as in "free beer") beer. :-D
Hello everyone,
I don't recall posting here in the past, although I have several hundred LAD
mails in .Mail...
Nice to meet you, anyway.
I've been looking at fst, and was going to package it for Ubuntu. I had used
dssi-vst in the past. My big problem is this: neither of the two save current
settings for kontakt, my sampler of choice (there is no free equivalent, as far
as I can tell, or I would use it).
I've now decided that fst has better long-term potential to do what I need,
mainly due to 1) lash support 2) not having to work through DSSI, which probably
cripples its ability to be able to save ALL parameters.
It would seem that fst doesn't have full VST 2.0 support, from looking at the
source code. I've never written anything remotely VST-related, but would like
to add such support to fst.
I see Kjetil S. Matheussen's name in the source for vsti.c. I'm hoping he has
some guidance for me.
Kjetil, and LAD's in general, can you confirm my observations, and do you have
an opinion on whether or not my goal is feasible?
thanks,
Forest
Ben Collins wrote:
> On Mon, 2006-06-26 at 10:11 +0200, Pieter Palmers wrote:
>> Lee Revell wrote:
>>
>>> On Mon, 2006-06-26 at 01:08 +0200, Pieter Palmers wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> We are experiencing 'soft' deadlocks when running our code (Freebob,
>>>> i.e. userspace lib for firewire audio) on RT kernels. After a few
>>>> seconds, I get a kernel panic message that signals a soft lockup.
>>>>
>>>>
>>> Can we see the kernel panic message? ;-)
>>>
>> no :p. I'm sorry for being a jerk, but I'm not going to type over that
>> message just so that you can confirm that it indeed is a 'soft lockup'
>> (or whatever it is called exactly) and that it occurs in the
>> ohci1394_iso_unregister_tasklet. You'll have to take my word on it. If
>> you need some specific part of the kernel message, you can get it. Tell
>> me what you wqant and why, that way I can learn something from it.
>
> Take damn a digital photo. I'm sorry for being a jerk, but I'm not going
> to debug an oops blind :P
I'm sorry for my previous response... a
monday-morning-bad-temper-leave-me-alone one that was very
non-constructive. On top of that it is quite stupid to ask for help and
at the same time claim "you'll have to take my word on it".
Please accept my apologies.
>
> Seriously, if you are going to ask for help, be prepared to provide the
> info requested, or plan on getting little to no help.
>
Of course. My monday-morning bad temper is over by now, and I hope I
didn't transfer it to any of you. I'll provide the panic, one way or
another.
Again, I apologize,
Pieter
Hello, i'm new here,
i've been working on a very simple, backward-forwards compatible extension to
LADSPA/DSSI to allow hosts to display more meaningful gui's with a
"describe_value" function which takes the port index and a LADSPA_Data and
allows the plugin to return a meaningful description. eg.
for a waveform port it might return "SAW", "SIN", "SQR" etc
for a cutoff filter it might return the frequency in Hz
for a tuning port it might return "-4 semitones"
also wanting to add a mechanism to group ports into logical sections.
without changing the underlying APIs, only by adding more layers on top this way
preserving backwards compatibility, the host simply dlsyms for
"ladgui_descriptor" and if it's there it makes use of the extra data, otherwise
it falls back to how it previously did things
once the API is done i plan to make a reference gui
the idea behind this is that plugins will not need any of their own gui code as
a useful gui can be constructed on the fly as a part of the host or a separate
process that will work for any plugin so plugin developers never need worry
about constructing a gui and can instead just make nice useable algorithms and
test them quickly and easily.
nicknamed LADGUI for now.
API so far is at http://ftsf.technetium.net.au/code/ladgui/ladgui.h
what i'd like to know is, if this is a stupid idea ^_^
it seems like a good one to me, but when i joined here to post this i noticed
lots of talk about LADSPA2, i've tried to read up on it but i can't seem to
find much information about it, and it doesn't seem to be backwards compatible
and doesn't seem to add anything to help create guis in the host? is there a
page somewhere which explains it all?
i'm sure there's lots of useful stuff that i'm missing, what other things would
be useful in such an extension?
thanks
Jez Kabanov