> Since LADSPA does not specifiy that control values are valid at
> activate(), either
As a host developer, I'd like to explain why control values are not
valid at activate().
Imagine a modular plugin system which allows chaining of control
signals. Assume all plugins are activated before any is run...
[A]-->[B]->
'A's control outputs might depend on it's audio input. i.e. 'A' can't
send control signals until run() is called.
Given that, 'B's input ports can't ever be valid during activate.
Best to not access control values during activate. Perhaps helpful if
hosts never provide them... to encourage plugin developers to write
robust code ;)
Jeff
On Thursday, 14 June 2007 00:41, pete shorthose wrote:
> On Thu, 2007-06-14 at 00:42 +0300, Hannu Savolainen wrote:
> > Hi folks,
> >
> > Now it has happened. Open Sound System is finally open sourced.
>
> http://4front-tech.com/hannublog/?p=5
Quote1:
"However the ALSA API is still almost completely undocumented
(after three years of it’s release) so how can anybody expect
that programmers could develop good applications based on it."
Quote2:
"For the above reasons the benefits of OSS are widely ignored:
[...]
* It’s fully documented (OTOH some parts of the documentation
are still under construction)."
Yeah. The ALSA API is also fully documented, but some parts are still in a
work in progress state...
What happened to MIDI/sequencer?
http://4front-tech.com/hannublog/?p=6
Quote3:
"The real problems started few months after that when I tried to
document the sequencer/music interface. [...] Due to lack of
time I gave up but promised to write the documentation later."
Quote4:
"The bad news is that there is no MIDI support in OSS 4.0. There
are few bugs in the MIDI code and we decided to ship OSS 4.0
without it [...] MIDI support will be included in OSS 4.1
(hopefully within this year)."
OK, lets talk about MIDI after some months.
Regards,
Pedro
Traverso 0.40.0 Release Announcement
The Traverso development team is pleased to announce the release of Traverso
0.40.0
Traverso is a cross platform multitrack audio recording and editing suite with
a clean and innovative interface targeted for home and professional use.
Changes in this release:
* Completely revamped User Interface, with many usability enhancements which
is fully themeable.
* Improved input event handler, with many new options
* CD TOC creation, with integrated CD Burning facilities.
* Support for LV2 plugins
* Reduced memory footprint for large projects
* Ported to Windows and Mac OS X
* Command Plugin framework: Extend Traverso's functionality by writing new
Commands.
Source tarball and installers for Linux, Mac OS X and Windows are available
at:
http://traverso-daw.org/
Enjoy!
The Traverso team.
Christian <krampenschiesser@email-addr-hidden> wrote:
> Thanks!
> This is what I meant, but this control is useless for me.
> But I found a way to create this in GIMP.
> I made a circle and cutted it to a controller. Now I could select
> small
> parts of it and set all black colors to red( with
> scriptfu->colors->color convert ).
> It was a lot of work, but worthy!
> so this is what I use right now:
> http://www.krampenschiesser.de/screenshots/ksdrumgui.jpg
just to be clear, phat uses the rendered output of my animated
version of Thorsten Wilms' knob mesh. (i had no creative
input at all, i just made Thorsten's mesh move)
blender creates a sequence of knob sized frames (with an alpha
channel, should that be desired) then, the image magick tool
"convert" is used (eg "convert +append output.png *.png" to
concatenate the frames into a large single image which can be easily
loaded and manipulated programatically.
(as is done in the phat knob and numerous other pixmap knobs derived
from the galan C code)
the method is independent of the code you use so there's no
reason why it shouldn't be useful to you. in fact, it's so simple
that i've duplicated your red knob design. see here for the
blender (.blend) file:
http://www.zenadsl6252.zen.co.uk/flat-red-100-frames.blend
and here for the output:
http://www.zenadsl6252.zen.co.uk/flat-red-100-frames.png
it's trivial to change the number of frames, the colours used or
the frame size and re-render it. you can also adjust the output filter
to sharpen or soften the edges.
i must admit though, that with a minimal design like this, you might
do well to implement it algorithmically with drawing operations.
then you can make run time changes to the appearance.
if you want something more complex or tactile then you could use
Thorsten's knob animation or give me a shout and i'll knock something
out to your specs. (although, bear in mind that my blender skills are
somewhat limited so it won't be a work of art =)
pete.
Hi folks,
Now it has happened. Open Sound System is finally open sourced.
Source downloads are available from http://developer.opensound.com/sources
The actual announcement follows.
Best regards,
Hannu
------------------------------------------------------------------
FOR IMMEDIATE RELEASE
4FRONT TECHNOLOGIES RELEASES THE SOURCE CODE FOR OPEN SOUND SYSTEM
CULVER CITY, CA, June 14, 2007: 4Front Technologies is proud to announce
the release of the source code to Open Sound System (OSS) v4.0. The
software currently runs on Linux, Solarisâ„¢, SCO UnixWareâ„¢ and FreeBSD
platforms.
OSS is a cross platform API that provides drivers for most consumer and
professional audio devices for UNIX® and POSIX based operating systems,
including Linux. Owing to its open architecture, applications developed
on one supporting operating system platform can be easily recompiled on
any other platform.
Licensing Models:
Open Sound System source code is now available under 3 licenses:
· GNU Public License (GPL) version 2
· Common Development and Distribution License (CDDL) for all operating
systems that have full source code available under the BSD or CDDL licenses.
· 4Front’s commercial license for using Open Sound incompatible with
open source licenses listed above. Commercial licenses are also
available for entities not wishing to use Open Sound System under any of
the above open source licenses
What is being open sourced?
The source code includes drivers for most consumer PCI and USB audio
devices and operating system support, including binary package
generation and sample test programs. Complete documentation and API
specification is also being made available to the open source community.
A device driver kit (DDK) is also available for developers to implement
cross platform device drivers for audio hardware. This eliminates lot of
redundant work that has traditionally been required to support any
hardware under multiple Unix/POSIX operating systems.
Reasons for going Open Source:
OSS has been an open API specification with multiple implementations by
independent developer communities. This has caused problems for
application designers because there are minor differences between the
implementations. The new open source community development model makes
it possible to replace the obsolete and incompatible vendor specific
sound subsystems and OSS implementations with a state-of-the-art
implementation developed by 4Front Technologies. The goal has always
been to standardize audio under POSIX compliant systems and this
includes real time operating systems and embedded systems as well.
"We are open sourcing OSS because this provides a great opportunity for
different communities to work together to provide wider audio hardware
support for all operating systems." said Hannu Savolainen, CTO and chief
architect of Open Sound System.
Industry Reaction:
"It's great to see 4Front releasing OSS under the Common Development and
Distribution License (CDDL). It's something the OpenSolarisâ„¢community
welcomes, and it provides an opportunity to improve sound support for
all OpenSolarisâ„¢ distributions," says Stephen Lau, OpenSolarisâ„¢ board
member.
"Fluendo is excited to see the open source release of 4Front
Technologies advanced OSS implementation for UNIX® and Linux. Getting a
unified and advanced sound system across all major UNIX® and Linux
variants will be a big advantage for developers. We look forward to
working together with 4Front Technologies to make sure the GStreamer
multimedia framework and the Open Sound System integrates perfectly with
each other", says Fluendo Business Development Manager Christian F.K.
Schaller.
"With a long history of successful collaboration with 4Front, Creative
looks forward to working with the Open Sound System community in
ensuring that Creative Sound Blaster Live! and Sound Blaster Audigy
sound cards have stable and well-supported drivers on Linux, Solaris and
BSD. The open source release of Open Sound certainly helps our goal in
providing cross-platform support for our products," said George Thorn,
director of digital media relations
for Creative Labs.
Community Portal
A new web site with source code, API specs and forums for the developer
community has been opened at http://developer.opensound.com
<http://developer.opensound.com/>. For more information and to download
the binary distributions of Open Sound System, visit 4Front's WWW site
at http://www.opensound.com <http://www.opensound.com/>.
--- xxx ---
All trademarks and copyrights belong to their respective owners.
UNIX is a registered trademark in the United States and other countries,
exclusively licensed through X/Open Company, Ltd.
Sun, Solaris, OpenSolaris, Sun Microsystems and The Network Is The
Computer are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States and other countries.
Open Sound System is a trademark of 4Front Technologies.
Copyright (C) 1996-2007, 4Front Technologies, All Rights Reserved.
Contact: Dev Mazumdar
4Front Technologies
4035 Lafayette Place, Unit F
Culver City, CA 90232
USA.
Tel: (310) 202 8530 E-mail: info(a)opensound.com <mailto:info@opensound.com>
Fax: (310) 202 0486 Web: http://www.opensound.com
<http://www.opensound.com/>
Dear colleagues,
I got in touch with people from teh Institute for Solar and Terrestrial
Physics from Irkutsk, Russia who wrote audio codec.
Please check site www.true-audio.com
Developers from that institute are willing to cooperate with a variety of
Linux audio users and developers who are willing to work further on the
development of that codec, testing and dissemination.
please contact me if you are willing to join that effort and if you can see
place of that codec iin your applications, hardware, projects.
With best wishes,
Vedran Vucic
Linux Center
http://www.gnulinuxcentar.org
I am very proud to announce 2 new releases: alsaplayer-0.99.80-rc1 and
fftscope-1.0.5
The main added feature in those 2 packages is a new GTK2 interface.
I must thank Madej. He done most of the job and is still working to improve it.
Alsaplayer-0.99.80-rc1
----------------------
AlsaPlayer is a new type of PCM player. It is heavily multi-threaded and tries
to excercise the ALSA library and driver quite a bit. It has some very
interesting features unique to Linux/Unix players.
This is a major feature enhancement release.
The player has now a fully working GTK2 interface.
It includes the same functionality as the GTK1 interface and some new
functions. The playlist window has been completely rewritten and is inside the
main window. The scopes plugins have been migrated too.
A lot of debugging has been made.
Every user is encouraged to upgrade AlsaPlayer and use the GTK2 interface.
We need your help with a few things:
* Bug reports
* Feature requests
* Artwork contributions
fftscope 1.0.5
--------------
Fftscope is a nice fft scope plugin for Alsaplayer.
It is now 2 versions of this scope in the package: one with GTK1 interface, the
other with GTK2 interface.
This is a major feature enhancement release
Enjoy those 2 new releases!
---------------------------
http://www.alsaplayer.org/http://sourceforge.net/project/showfiles.php?group_id=249
Dominique
CLAM 1.1, The `More eye-candy, please' release.
After a very intense development months since the last 1.0 release,
the CLAM crew is glad to announce that CLAM 1.1 is ready to
[1]download. It comes with many new features and code clean up.
Most
important improvements are found in the Visual Prototyping
front: new
3D-looking widgets, new data viewers and control surface; and a
simplified way to bind controls between the user interface and the
processing network.
To learn about CLAM: http://clam.iua.upf.edu
This release has been cooked-up under the umbrella of the
Interactive
Technology Group at the UPF lead by Josep Blat. So we thank their
support! It also features the work from contributors such as Zach
Welch; as well as the first patches from [2]Google Summer of Code
program --for example LADSPA and FAUST support and some work on
Annotator widgets.
A summarized list of changes follows. See also the [3]CHANGES files
for details. New audio related widgets were added to be used on the
NetworkEditor and the Prototyper. Such widgets include data
views such
as the BarGraph which can display LPC's, MFCC's. Nice control
widgets
were also added. The ControlSurface, for instance, to control two
scalar parameters by moving a point. Some widgets were gathered
from
the LAC community, such as [4]PkSampler [5]PovRay generated
widgets,
and nice knobs we enhanced from [6]QSynth and [7]Rosegarden.
Thanks to
the developers of those projects for making them GPL and being so
supportive while integrating them in CLAM. With all those widgets,
users now can visually build more appealing applications such
as the
new examples we include with Prototyper: A real-time gender
change, or
real-time spectral effects.
The TonalAnalysis (Chord extraction) now takes advantage of fftw3
performing 4 times faster! The KeySpace visualization was also
optimized so now tonal analysis runs even on very slow computers.
NetworkEditor and Prototyper usability have been enhanced. They
exploit the new in-control bounds parameters to automatically
set up
bounded control senders widgets. Also, NetworkEditor have proper
multi-processing selection features.
On different fronts, the code-base has been reduced by getting
rid of
Fltk and Qt3 modules since we are now focusing on Qt4, and the
documentation have been restructured and now it offers new
programming
how-tos.
The CLAM team
References
1. http://clam.iua.upf.edu/download.html
2. http://clam.iua.upf.edu/wikis/clam/index.php/GSoC_2007
3. http://clam.iua.upf.edu/doc.html#changes
4. http://www.patrickkidd.com/
5. http://www.povray.org/
6. http://qsynth.sourceforge.net/
7. http://www.rosegardenmusic.com/
Hi all,
I remember a while back someone posting results of a benchmark to
compare performance of pipes vs cond vs semaphores, but I can't find the
specific post or code in the archives for the life of me.
Does anyone have the /code/ for that benchmark (or anything similar I
can fiddle with to do some testing)?
Thanks,
-DR-