<<<<<<<<>>>>>>>>
**Piksel08: code dreams
december 4-7 2008
Bergen, Norway
How does code dream? What are the dreams of code?
Piksel08 examines the other side of code, an alternative side to a hard-coded
reality of work and play. Open hardware and free software project a utopic
vision, yet exist within economies of capital, the dream factory of
mainstream technology. Within the chance meeting of sewing machine and
umbrella on the dissecting table, hardware and software are flattened.
Piksel08: code dreams explores the dreams of this soft machine; bachelors
coding for pleasure, reverse engineering paranoiac constructs of the real,
automatic coding practice, soft hardware, and everyday magic.
<<<<<<<<>>>>>>>>
**open call:
1. Installations
Projects related to the code dreams theme including but not restricted to:
reverse engineering, soft hardware, code poetry, novel instruction sets,
invisible exploration, ghosted computation...
programmed by and running on free and open source software and/or open/DIY
hardware.
2. Audiovisual performance
Live art realised by the use of free and open source software. We specially
encourage live coding and DIY hardware projects to apply.
3. Software/Hardware
Innovative DIY hardware and audiovisual software tools or software art
released under an open licence.
<<<<<< Deadline - august 15. 2008 >>>>>>
Please use the online submit form at:
http://piksel.no/piksel08/subform.html
or send documentation material - preferably as a URL to online
documentation with images/video to piksel08 [AT] piksel [DOT] no
<<<<<<<<>>>>>>>>
**subsections:
**real code
real.co.[de][re] actively explores code which has strong effects on the real,
constructing the world through prediction and description. The twelve hour
real.co.[de][re] session will attempt the active construction of a working
code model (of any form) which addresses a flattening of the distinction
between software and hardware, to resolve a new political reference for real
core code.
**abstract code
Abstract code is software whose results can be invisible, a software
implementing different layers of action at the same time.
Abstract code is a connection to parallel worlds, a poetic formula dealing
with outer forces. Code is art, its action is subtile, effective, magic.
procedural text
maledictions, oracles, iambi, hymn, formula, refrains, hypnotic sentences,
prayers, and other.
<<<<<<<<>>>>>>>>
Piksel is supported by the Municipality of Bergen, Arts Council Norway,
Vestnorsk Filmsenter, Hordaland County Council and others.
More info: http://piksel.no
---
On behalf of the entire Rivendell development team, I'm pleased to announce
the release of Rivendell v1.0.0rc5. Rivendell is a full-featured radio
automation system targeted for use in professional broadcast environments. It
is available under the GNU General Public License. Changes in this release
include (from the NEWS file):
*** snip snip ***
Changes:
Fixed broken compile on gcc-4.3.x.
Removed limitations on using various 'special' (e.g. quotation and
apostrophe) characters in database fields.
Fixed problems with importing files with UTF-8-encoded names.
Database Update:
This version of Rivendell uses database schema version 159, and will
automatically upgrade any earlier versions. To see the current schema
version prior to upgrade, see RDAdmin->SystemInfo.
As always, be sure to run RDAdmin immediately after upgrading to allow
any necessary changes to the database schema to be applied.
*** snip snip ***
Further information, screenshots and download links are available at:
http://www.rivendellaudio.org/
Cheers!
|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|-------------------------------------------------------------------------|
| Do not try to think outside of the box. That's impossible. Instead, |
| realise the truth. There is no box. |
| --Quoted by "larsmjoh" on GrokLaw.net |
|-------------------------------------------------------------------------|
Mixxx is currently the most popular open source djing software
package, providing everything you need to make your mixes in a
completely open source environment.
The Mixxx development team is proud to announce the release of version
1.6.0, representing 16 months of development. It is available for
Linux, Intel Mac and Windows. For a full list of changes, please see
our blog at http://mixxxblog.blogspot.org. Some highlights are:
* Vinyl control - Use your turntables to drive Mixxx with generic
soundcards, no more being tied to branded hardware by proprietary
software
* Better hardware support - Mixxx 1.6.0 supports a much wider range of
MIDI controllers to previous releases
* Stability - Many stability issues have been fixed
* Better BPM detection
* A better media library
We'd love for you to try it out and let us know what you think whether
you're an existing user or new to Mixxx. Head over to
http://www.mixxx.org to download.
Thanks,
Adam Davison on behalf of the Mixxx development team
guitarix is a simple mono amplifier to jack (JackAudioConnektionKit) with one
input and two output's. Designed to get nice trash/metall/rock/guitar sounds.
Avaliable are the controls for bass, treble, gain, balance, distortion,
freeverb, impulse response (pre state), crybaby(wah),
feedback/feedforward-filter and echo . A fixed resonator will use, when
distortion is disabled.
guitarix based on Gtk, a great part is also realesed as ladspa plugin.
guitarix is licensed under GPL
Homepage with screenshots:
https://brain.kicks-ass.org/~hermann/guitarfx.html
For capture guitarix make use of jack_capture from Kjetil S. Matheussen. If
you dont have it installed, look here:
http://old.notam02.no/arkiv/src/?M=D
I use faust to build the prototype and will say thanks to
: Julius Smith <http://ccrma.stanford.edu/realsimple/faust/>
: Albert Graef <http://www.musikwissenschaft.uni-mainz.de/~ag/ag.html>
: Yann Orlary <http://faust.grame.fr/>
regards hermann
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 3:
* Fix typos in docs
* Disable use of C++ demangling in sigsegv. Fix for sr #2074
* Fix a2j_control help text (thanks kfoltman!)
* Request fixed JACK client name. Fix for bug #12139
* Handle missing svnversion executable nicely. Fixes bug #12138
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Download from:
http://old.notam02.no/arkiv/src/?M=D
Realtime priority patch for the linux kernel
============================================
To make sure the Linux kernel is able to grant realtime
priority, and full nice and mlock capabailites can still
be a little bit inconvenient and/or frustrating.
However, this super-tiny patch:
http://old.notam02.no/arkiv/src/realtime.diff
against the linux source shortcuts all other
methods. No more pam, realtime-lsm, rtlimits etc.
jack_capture
============
jack_capture is a program for recording soundfiles with jack. Its default
operation is to capture whatever sound is going out to your speakers into
a file. (But it can do a number of other operations as well...)
Changes 0.9.19 -> 0.9.23:
*Minor spellings
*Check for out of memory
*Clean up source a bit
*Stop connection thread before closing jack client.
*Made --help a tiny bit cleaner
*Removed shut down code from the SIGINT signal handler.
*Fixed segfault in case jack shuts down. Thanks to Julien Claassen
for reporting the bug.
(Note that there is also a 0.9.24 release. 0.9.24 has
changed internal data representation from lockless ringbuffer to
lockless lifo and fifo stacks. (Unmodified lifo/fifo code taken
from midishare. (Copyright Grame 1999-2005)) 0.9.24 probably works
fine, but it shouldn't be used for important recordings since
it hasn't been much tested yet.)
Rollendurchmesserzeitsammler v0.0.5
------------------------------------
The Audio Rollendurchmesserzeitsammler is a conservative garbage
collector especially made for running inside an audio DSP thread.
New about this release is that I have finally replaced TLSF
(http://rtportal.upv.es/rtmalloc/) with a pool-based dynamic
memory allocator, which makes allocation using the
rollendurchmesserzeitsammler approximately as fast as
using custom memory pools.
Using the rollendurchmesserzeitsammler
should be a lot more convenient than memory pools though, and
since memory is not freed manually, but instead
is automatically freed in a separate thread, there is a
slight chance that using rollendurchmesserzeitsammler
instead of custom memory pools could make some DSP code run
faster.
In non-synthetic benchmarks, I have not been able to see any
significant improvement in CPU use because of this compared to
using the TLSF allocator. But for programs doing
millions of allocations per second, the new memory allocator
will probably perform significantly better than TLSF, if it
would ever make sense doing so many and frequent allocations
of course...
Changes 0.0.4 -> 0.0.5
* Implemented a custom pool-based dynamic memory allocater. This new
memory allocator is now set as default. To use TLSF instead, set
"USE_TLSF=-DUSE_TLSF" in the Makefile before compiling. The following
changes are caused by this switch:
* Allocating memory is now approx 10 times faster (13 vs. 168
instructions for the allocation itself, but there are some GC
overhead too)
* The allocator copies used memory only (not just the whole heap).
But not always! This was a lot more complicated to to with TLSF
so I didn't do that. Note that for the garbage collector to still
be hard realtime safe, the programs must ensure that full copies
are taken now and then. (There's a change in the API for doing that)
* Doing a garbage collection is much faster since the heaps are usually
much smaller (because only used memory is copied) and that freeing
is 10-20 times faster.
* Further improvements for reducing memory overhead and make
searching for used mem to be O(log n) instead of O(n) is
much simpler now. (this is TODO though)
* However 1: In case the code using the garbage collector will
continue forever to allocate memory of different sizes, the
new dynamic memory allocator could eventually run out of memory
even if the program itself doesn't use very much memory.
I don't think this is very likely to happen for DSP routines though,
and there might even be solutions to fix this problem if it should
ever come up. For now, just switching to TLSF fixes the problem.
* However 2: in non-synthetic benchmarks, I have not been able to see any
practical improvement in CPU use, apart from the slight improvement
in CPU available for use in non-realtime threads because taking
snapshots usually takes a lot less time now. But for programs doing
millions of allocations per second, the new memory allocator will
probably perform significantly better than TLSF, if it would ever
make sense doing so many allocations of course.