Commit 6b49f658 authored by Alessio Treglia's avatar Alessio Treglia

Imported Upstream version 0.0.2+20110904.gitbdb1bee1

parent 068b2fa1
* James W. Morris <>
forker of Specimen to Petri-Foo, primary developer of Petri-Foo
added modulation routing, midi-cc as modulation sources, remover
of deprecated GUI code, etc, etc, etc.
* Brenden Jones <>
Added auto-preview and a keyboard shortcut to sample-selector,
and minimum and maximum velocity values for patch.
Specimen AUTHORS
Petri-Foo began as a fork of Specimen.
Specimen was written by the following people:
-*- text -*-
* Pete Bessman <>
......@@ -58,10 +82,3 @@
* Eric Dantan Rzewnicki <>
* James W. Morris <>
forker of Specimen to Petri-Foo, primary developer of Petri-Foo
added modulation routing, midi-cc as modulation sources, remover
of deprecated GUI code, etc, etc, etc.
-*- text -*-
* Pete Bessman <>
Founder, primary developer untill 2005-09-14
* Alexander <>
modified midi.c to treat note-on events with velocity of 0x00 as
* Dave Robillard <>
Lash support. Removed Gnome-ui requirement for about dialog.
* David R. Clark <>
Invaluable testing, feedback, and discussion, as well as some nifty
sample generating programs.
* Dimitry Baikov <>
Added support for MIDI CC events.
Update to jack_midi API.
* Lars Luthman <>
Jack-midi implementation.
* Loki Davison <>
Sync code, and initial implementation of lots of stuff which got
lost during The Cleansing. Responsible for convincing ninjadroid to
keep on hacking.
* Nedko Arnaudov <>
Made specimen window resizeable.
* peter <>
Rewrote the build system during the year of limbo.
* Sacha Berger <>
updated beef.c to reflect newly gained parameters.
* Thorsten Wilms <>
UI advice, and designed the fansliders used extensively in the GUI.
* Torben Hohn <>
was an immense help to Pete in optimizing the waveform code (and he
pointed out that it needed to be done in the first place).
* Eric Dantan Rzewnicki <>
File all bug reports in the bug tracker at
* mixer_mixdown is sometimes called before mixer_set_jack_client
resulting in a segfault. i've not yet determined if that statement
is true or not, but it seems likely.
the list that follows is inherited from Specimen. i've not actually checked
if it is still relevant or not - jwm 2011/03/28
Known Bugs
* Create some patches, load some samples, connect to JACK, and start
running a MIDI pattern . Then, flick back and forth between the
patches quickly (a mousewheel is handy for this). JACK will fail with
something along the lines of "unable to execute processing graph
(invalid file descriptor)". JACK will stop processing data until
Specimen is closed (it will exit with a segfault); JACK and all of
it's clients will then resume normal operation. [This seems to have
magically disappeared, which I find quite disturbing. Can anybody
reproduce it? --pete]
* Sample start/stop and loop points don't behave properly when
switching audio sample rates. It's probably time to store the audio
sample rate along with the session file, BTW.
* Midi syncing appears to be broken with Fedora Core 2's kernel. If
you compile --enable-debug you'll see the gory details.
* Midi syncing drifts like a bitch anyway.
* Help -> About -> credits causes a segfault.
* audio settings dialog currently resets jack client name to default
"specimen" instead of using previously set name.
cmake_minimum_required(VERSION 2.6)
cmake_policy (SET CMP0011 NEW)
set(Petri-Foo_VERSION_MAJOR 0)
set(Petri-Foo_VERSION_MINOR 3)
set(BINDIR "bin" CACHE STRING "Where to install binaries")
set(DATADIR "share/petri-foo" CACHE STRING "Where to install data files")
set(APPLICATIONS_DIR "share/applications" CACHE STRING "Where to install desktop files")
set(PIXMAPS_DIR "share/pixmaps" CACHE STRING "Where to install icons")
set(MIME_DIR "share/mime" CACHE STRING "Where MIME definitions are located")
set(UpdateMime "ON" CACHE BOOL "Update Mime Database")
option (BuildForDebug "Include gdb debugging support" ON)
set (BuildOptionsDebug "-O0 -ggdb" CACHE STRING "Debug build flags")
# additional compiler flags
add_definitions(-Wall -Wextra)
if (BuildForDebug)
set (CMAKE_BUILD_TYPE "Debug")
set (DEBUG 1)
set (CMAKE_C_FLAGS_DEBUG ${BuildOptionsDebug})
message (STATUS "Building for ${CMAKE_BUILD_TYPE}, flags: ${CMAKE_C_FLAGS_DEBUG}")
else (BuildForDebug)
set (CMAKE_BUILD_TYPE "Release")
set (DEBUG 0)
set (CMAKE_C_FLAGS_RELEASE ${BuildOptionsBasic})
message (STATUS "Building for ${CMAKE_BUILD_TYPE}, flags: ${CMAKE_C_FLAGS_RELEASE}")
endif (BuildForDebug)
find_package(PkgConfig REQUIRED)
message(STATUS "Found pkg-config ${PKG_CONFIG_EXECUTABLE}")
message(FATAL_ERROR "pkg-config required but not found")
pkg_check_modules(JACK REQUIRED jack>=0.120.0)
message(STATUS "Found jack ${JACK_VERSION}")
message(FATAL_ERROR "Jack >= 0.120.0 not found.")
endif (JACK_FOUND)
pkg_check_modules(ALSA REQUIRED alsa>=1.0.17)
message(STATUS "Found alsa ${ALSA_VERSION}")
message(FATAL_ERROR "alsa not found.")
endif (ALSA_FOUND)
pkg_check_modules (SNDFILE REQUIRED sndfile)
message(STATUS "Found sndfile ${SNDFILE_VERSION}")
message(FATAL_ERROR "sndfile not found")
pkg_check_modules (SAMPLERATE REQUIRED samplerate)
message(STATUS "Found secret rabbit code ${SAMPLERATE_VERSION}")
message(FATAL_ERROR "secret rabbit code not found")
pkg_check_modules (GLIB2 REQUIRED glib-2.0>=2.16)
message(STATUS "Found glib2 ${GLIB2_VERSION}")
else (GLIB2_FOUND)
message(FATAL_ERROR "glib2 was not found.")
endif (GLIB2_FOUND)
# GTK2
pkg_check_modules (GTK2 REQUIRED gtk+-2.0)
message(STATUS "Found gtk2 ${GTK2_VERSION}")
message(FATAL_ERROR "gtk2 required but not found")
pkg_check_modules (LIBGNOMECANVAS2 REQUIRED libgnomecanvas-2.0)
message(STATUS "Found libgnomecanvas2 ${LIBGNOMECANVAS2_VERSION}")
message(FATAL_ERROR "libgnomecanvas2 was not found.")
pkg_check_modules (LIBXML2 REQUIRED libxml-2.0)
message(STATUS "Found libxml2 ${LIBXML2_VERSION}")
message(FATAL_ERROR "libxml2 was not found")
INCLUDE (CheckIncludeFiles)
include_directories ( . )
# Install targets
ADD_SUBDIRECTORY( libpetrifoo )
ADD_SUBDIRECTORY( libpetrifui )
install (DIRECTORY pixmaps/ DESTINATION ${DATADIR}/pixmaps
install (FILES petri-foo.xml DESTINATION ${MIME_DIR}/packages)
install (FILES pixmaps/petri-foo.png DESTINATION ${PIXMAPS_DIR})
install (FILES petri-foo.desktop DESTINATION ${APPLICATIONS_DIR})
if (UpdateMime)
install (CODE
"EXEC_PROGRAM ( \"update-mime-database ${CMAKE_INSTALL_PREFIX}/${MIME_DIR}\" ) "
endif (UpdateMime)
2011-08-06 Brendan Jones <>
* gui/global_settings.[ch]
Stores last-used sample and bank directories into
2011-08-06 James Morris <>
* New zoom-in, zoom-out, zoom-fit, and zoom-1:1 buttons
these buttons replace the cruddy oldspin button previously
used for zooming and which the values of were meaningless.
* Mouse-wheel zooming.
Moving the mouse-wheel down will zoom in to wherever the
pointer is pointing in the waveform.
* Probably stuff which I've forgotten and not added into
this Changelog.
* PHIN fan sliders have fans disabled by default.
the fans of the fan sliders require desktop compositing
so are disabled by default.
* PHIN fan slider setting stored via global_settings
* sample.c: Fixed raw/headerless sample loading
* float_section.c: Fixed portamento time setting.
2011-07-26 James Morris <>
* new build system using cmake. alter dir structures.
* include subset of PHAT in build and call it phin.
2011-07-23 James Morris <>
* patch_util.c, new function: patch_get_samplerate(void)
* dish_file.c: current samplerate is written into the
dish_file within the "Master" node. This means that if the
bank is loaded at a later date and JACK is running at a
different samplerate, the values for the play+loop points
can be adjusted accordingly for the resampled audio-data.
* sample.[ch]: removed resample_ratio from struct _Sample.
the resample_ratio member was added in the previous commit
and removed again due to the dish_file being responsible
for calculating differences in play+loop points when
JACK samplerate changes (between instances, not during a
single instance).
* sample.c, sample_default: scaled output of LFO.
scale output of LFO to prevent the default sample having
samples exceeding the range -1.0 to +1.0.
2011-07-20 James Morris <>
* dish_file.c: fix/restore read/write of Portamento/Legato
* sample.[ch]: added sample_get_resampled_size
this function provides a means to get the size the
sample will use once loaded. this is required for when
soft-limits to the size of samples petri-foo will load
is implemented.
* sample.[ch]: addition and usage of MAX_SAMPLE_FRAMES
enumeration MAX_SAMPLE_FRAMES = INT32_MAX; replaces
previous detection of overly-large samples by casting
sf_count_t variables to int and noticing difference.
* patch_util.c, patch_sample_load: scale loop points.
loop points of the default sample are now scaled to
the global sample rate as they should.
2011-07-19 James Morris <>
* Minimum and maximum Velocity value specification
for patche to allow velocity layering of patches.
Thanks to Brendan Jones for submitting patch.
* mod_section.c: fix bug in amplitude modulation amount
Finally fixed this bug by the removal of a dangerously
misplaced else.
* --unconnected command line option to not auto-connect
JACK ports. This is required for JACK Session to work
* patch.c, patch_set_and_get.c, mod_section.c:
inverted velocity mapping
Allows negative setting of velocity sensitivity. Means
you can cause low velocity to have the effect of high
velocity and vice-versa.
2011-07-14 James Morris <>
* Auto preview toggle added to the sample selector
dialog so that samples automatically play without
* Added keyboard shortcut for 'Loa_d' in sample selector.
Thanks to Brendan Jones for submitting these additions.
2011-06-30 James Morris <>
* added gpl header to all source files
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `' (or `') is used to create
`configure' by a program called `autoconf'. You only need
`' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
`configure' recognizes the following options to control how it
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
Alias for `--cache-file=config.cache'.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
SUBDIRS = src pixmaps
EXTRA_DIST = acx_pthread.m4 petri-foo.spec bootstrap BUGS ROADMAP WISHLIST
See the Changelog and/or mailing list.
......@@ -5,75 +5,37 @@ Petri-Foo is a fork of the Specimen Sampler project. Specimen was
originally developed by Pete Bessman. See the AUTHORS file for
the list of other authors who've made contributions.
Petri-Foo is forked and developed by James Morris.
The primary goal of forking Specimen to create Petri-Foo was to allow
frequency modulation of the LFOs, and to allow user selection of
modulation sources throughout the program.
This has been accomplished.
Once stage 1 was complete, these were ideas I originally planned upon
* Sample position retrigger by LFO. TODO.
* Sample start position modulation. TODO.
* Sample loop position modulation. TODO.
* X-fades for loops/retriggers. Basic implementation..
* Replace existing filter implementation. TODO.
* Visual display of ADSRs and LFOs. FORGOTTEN.
* Noise modulation source. TODO.
* Sample and Hold. TODO.
* Removal of deprecated GTK/GDK code
* Default auto-generated patch/sample
* Many code re-arrangements
* Mark navigation in waveform display
* Opening of raw audio formats
* Complete rewrite of bank file I/O code and XML file layout.
* MIDI Controllers subsumed as modulation sources.