Archive for the 'Artistic Software' Category

Inkscape is an open source SVG editor

Inkscape is an open source SVG editor with capabilities similar to Illustrator, CorelDraw, Visio, etc. Supported SVG features include basic shapes, paths, text, alpha blending, transforms, gradients, node editing, svg-to-png export, grouping, and more.

Inkscape’s main motivation is to provide the Open Source community with a fully XML, SVG, and CSS2 compliant SVG drawing tool.

Additional planned work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and establishment of a friendly, open, community-oriented development processes.

Visit Inkscape to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Q Light Controller

Q Light Controller 2 (QLC) aims to be a free alternative to commercial lighting software and hardware. The main emphasis is to build a software that can be used to control any kinds of lighting equipment.

QLC uses the dmx4linux driver suite to access various hardware interfaces. Currently DMX512, Analog 0-10V and MIDI control systems are being supported by dmx4linux. Refer to dmx4linux interfaces for more information on supported interfaces.

Q Light Controller is free software licensed under the GNU General Public License.

Here are some key features of “Q Light Controller”:

· Easy to use device-oriented interface
· Control up to 512 DMX/Analog channels thru DMX4Linux
· Use one of the ready-made fixture definitions, or
· Define your own fixtures with the device class editor
· Create fast changing or smoothly fading scenes, chasers and sequences
· Easy programming of moving lights thru a pattern generator
· Conjure your favourite lighting desk layout with the virtual console

Requirements:

· QT 3.1 (or later)
· XFree86 4.x or x.org 6.x (or later)
· Real-time clock (/dev/rtc) kernel support (usually enabled by default)

Visit Heikki Junnila to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Virtual Drum Machine is a simple drum machine

Virtual Drum Machine is a simple drum machine.

It works for little endian/linux kind of machines. You may let it work on others machines, but you probably will get troubles with it.

You definitely need oss (or maybe alsa) for sound output, and a posix-like operating system. To let it work on a big endian machine should be painful.

You write a rhythm, then you compile it, then you are able to play it to your sound card or save it to a file.

The Virtual Drum Machine is made of

* the Rhythm Compiler,
* the runtime library.

The Virtual Drum Machine is in the public domain. Who needs a license? money makers? Protection against robbery? let me laugh… Read any text of law, you will see where the robbers reside.

A simple file would look like :

void main_rhythm(void)
{
tempo = 120;
* a
. b
. b
.
* a
.b
* a
.
. b
. b
* a c
. b
}

Install:

Do a “./configure” in the drums directory, then “make”, then “make install”, it should be alright. You can listen to some examples in the examples/ directory.

Who yo use it?

Write a rhythm. Compile it with “rc”. Run the produced program. You are done.

See the examples/ directory to get the point.

When you run an example, try “-h” to get the available options.

It should be self-explanatory.

The rhythm compiler has several options. By running “rc –help”, all should be clear.

Technical Details:

The compiler will parse the input file line by line.

If a line starts with “*” or “.” (not counting leading white spaces), the whole line is seen as a rhythm line, and is transformed into C code. If not, it is passed as is to the C file.

Beware! You MUST NOT start any C code line by “*” or “.”!

You can create as much functions as you want, write any C code you want. But remember that a line starting by “*” or “.” is seen as a rhythm line and is translated by “rc” into C code.

You must provide a “void main_rhythm(void)” function, that will be called by the library. It is the starting point of your rhythm. It can be “void main_rhythm(int argc, char *argv[])” too, with common meaning for those parameters (non-C coders will have trouble with the Virtual Drum Machine).

You can change the tempo (ex. “tempo=100;”) or the volume (ex “vol=0.4;”) at any time. Each sample comes with its own volume and panning (ex. “a.vol = 0.1;” “a.pan=-0.8;”). Volumes range from 0 to what you want. 1 is for the normal volume. Panning ranges from -1 (left) to 1 (right). 0 is center. All values are double. You can use “volume” instead of “vol”, and “panning” instead of “pan”. There is no global panning, if you want all left, set all samples to left.

To run in stereo mode, don’t forget “-s” when running the generated program. It is mono by default.

You absolutely need to compile and run the examples, and read them to get the point out of it!

The “rc.conf” file contains configuration informations. You specify the sample by “sample” followed by its name (the one you will use in your rhythm files), then the file that will be played. The name of the sample must start by a letter, followed by letters and/or numbers (it must be a valid C identifier, without “_” though). The configuration file contains the install directory, used by “rc” to compile your rhythms. Take a look at the one that is provided to see how to use it.

The sound files are simple wav files. They all should be of the same rate, which can be specified to the generated program, using the “-f” option (44100 is the default). (The library only handles very basic wav files, if yours don’t work, you probably will have to modify the library for the program to handle it.)

When you add a sample, you must modify “rc.conf” for the changes to appear. The samples are hard-linked to the produced program, so if you change “sample a /some/dir/file1.wav” by “sample a /one/other/dir/file2.wav” in the configuration file, the previously generated programs will still use “/some/dir/file1.wav”. You will have to compile them again to take the changes into account.

Visit Sed Barbouky to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Allegro Sprite Editor

Allegro Sprite Editor is a program specially designed with facilities to create animated sprites that can be used in some video game. Allegro Sprite Editor lets you create from static images, to characters with movement, patterns, textures, backgrounds, logos, color palettes, and any other thing that you think.

Here are some key features of “Allegro Sprite Editor”:

· Edit sprites with layers and animation frames.
· Edit RGB (with Alpha), Grayscale (with Alpha also) and Indexed images.
· Control 256 color palettes completely.
· Apply filters for different color effects (convolution matrix, color curve, etc.).
· Load and save sprites in these formats: .BMP, .PCX, .TGA, .JPG, .FLC, .FLI, and .ASE’ (ASE’s special format).
· Use bitmap’s sequences (ani00.pcx, ani01.pcx, etc.) to save animations.
· Drawing tools (dots, pencil, real-brush, floodfill, line, rectangle, ellipse), drawing modes (opaque, glass), and brushes types (circle, square, line).
· Mask (selections) support.
· Undo/Redo support for every operation.
· Multiple editor support.
· Draw with a customizable grid.
· Unique tiled drawing mode to draw patterns and textures in seconds.
· Save and load entire work’s sessions (in `.ses’ files).
· Scripting capabilities with Lua language

Requirements:

· Allegro

COMPILATION

Before compile, you must configure what ASE should use, what libraries are available, etc. You can run the fix.sh script, answer some questions and done: the main makefile is created. Or you could edit the makefile.cfg, uncomment CONFIGURED=1 and uncomment the necessary options, and then run “makefile -f makefile.lnx”.

INSTALLATION

After compilation, you have two options:

1) Running ASE from its source directory.
2) Install ASE in the directory that you specify in the fix.sh question: “Where do you want install ASE by default?” (generally “/usr/local”) (in the makefile.cfg, it’s the DEFAULT_PREFIX variable)

Run “make install” (it only works in Unix like systems)

UNINSTALLATION

Run “make uninstall”.

Visit David A. Capello to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Warsaw Pakt is a software system for network-controlled media processing applications

Warsaw Pakt is a software system for network-controlled media processing applications. The Warsaw Pakt project consists of a library for serialization of GObjects to XML, network components for publishing and accessing object spaces via multiple access methods (both in libpakt), a gstreamer module (gst) and an access shell program (pash). Its main purpose is to allow you to setup arbitrary gstreamer graphs on your local or a remote system, and modify it’s parameters while running.

The target audience of this manual are “accessors”, people who want to access a pakt server via an XML access method, eg from Flash or some scripting language. This manual introduces you to basic pakt functionality and documents the various objects you can instantiate and control.

Warsaw Pakt consists of a bunch of components that make up its functionality. As an accessor, you’re probably most interested in pgstd, and the classes and messages that libpakt provides for any pakt server.

libpakt

The pakt library (libpakt) provides basic pakt functionality: objects and functions for XML (de-)serialization, navigating around the object hierarchy, basic objects and GObject and GProperty wrappers, and networking classes. The accessible objects are documented in the p: namespace section (’p: namespace’) of the reference part of this manual.

paktd

The generic pakt daemon listens on specified ports for connections from pakt clients (like ‘pash’), and serves them with access to the server-side object space. The protocol is dependant on which ‘modules’ are loaded.

modules

The generic pakt daemon (’paktd’) acts on objects defined by the loaded modules. Currently there is only one module:

gst

The GStreamer module (gst, libpaktgst.so) provides classes to interface pakt with GStreamer. The tags and their attributes are documented in ‘gst: namespace’

pash

pash, the pakt shell, is a commandline shell program that allows you to test, debug and experiment with a pakt server. It features readline-style tab expansion for the server’s object space.

Visit Daniel Fischer to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

telelalka is a program for making puppet theater

telelalka is a program for making puppet theater via the Internet. Both the puppeteers and the spectators can be located anywhere in the world as long as they have Internet access.

Puppeteers move their puppets on the screen using the mouse and will type dialogs using the keyboard. Spectators will watch the show on their computers.

How does it work

Telelalka is website based AJAX application. It means that actors just visit some website and there they can move their puppets and make them talk. Spectators just visit some website and watch the show. If you want to see how it works, just go here – it is live working telelalka instance.

Visit Piotr Sobolewski to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Fractal Flames are algorithmically generated images and animations

Fractal Flames are algorithmically generated images and animations. The software was originally written in 1992 and released as open source, aka free software. Since then it has developed a lot.

Flames has been incorporated into many graphics programs and ported to most operating systems. The shape of each image is specified by a long string of numbers - a genetic code of sorts.

You can create your own flames with the Apophysis interactive designer (for windows) or with the gimp’s flame plug-in (for linux and OSX). Or you can use the Electric Sheep distributed screen saver to join the collective evolution of animated fractal flames.

What’s New in This Release:

· fixed action string overflow when many xforms are present.
· added ‘print_edit_depth’ env var to control how many levels of tags are saved when using flam3-genome. Fixed wrong placement of random improve_colors code in flam3-genome.
· go to five digit filenames.
· fixed bug in supershape variation.
· API cleanup, thanks to david bitseff.

Visit Scott Draves to download latest version.

Posted on Monday, January 7th, 2008
Under: Artistic Software, Linux | No Comments »

Your Ad Here