RTC-lib 4.6 (Universal Binary) released

Dear MAXers!

I am glad to announce the release of RTC-lib 4.6 (Real Time Composition
Library). This software library for algorithmic composition which was started
as early as 1992 finally found its way into the Brave New Intel World – thanks
to the help of friends and neighours.

Free download from: http://www.essl.at

This version works best with Max/MSP 4.6 on Intel or PPC processors under MacOS
X 10.4

Please spread the news!

Cheerbies,
   — Karlheinz Essl

RTC-lib 4.6 pre-release

Dear Maxers!

Before I am officially releasing the Universal Binaries savy version of the RTC-lib (Real Time Composition Library for Max) I’d like to post the final candidate for public testing which you can download from:

    http://www.essl.at/works/rtc-beta.html

This software library – a collection of patches and externals for Max/MSP/Jitter) – offers the possibility to experiment with a number of compositional techniques, such as serial procedures, permutations and controlled randomness. Most of these objects are geared towards straightforward processing of data. By using these specialized objects together in a patch, programming becomes much more clear and easy. Many functions that are often useful in algorithmic composition are provided with this library – therefore the composer could concentrate rather on the composition than the programming aspects.

Best regards from Vienna,
    — Karlheinz Essl

Cyclops 1.3 Universal Binary Public Beta

Users of MaxMSP 4.6.2 can now preview the forthcoming Universal  Binary version of Cyclops (we’re calling it 1.3 to make a break from  the CFM version, although there is no added functionality).  jit.cyclops is included, as well.

The Public Beta will extend until the 3rd of January, at which time  the object will stop functioning. Until then, the object will run in  demo mode, _even_if_ you are a registered owner of Cyclops (this is  our way of ensuring that you upgrade to the final version when it’s  released, and preventing you from planning gigs around beta software)  – we’re sorry if this is an inconvenience.

Demo mode means that, after 10 minutes, the object will stop  analyzing data until you restart Max (for jit.cyclops, the object  will be limited to 2 zones after 10 minutes). This should be long  enough to test that the object works, and to give you an idea of what  the object does, if you’re unfamiliar with it.

For those unfamiliar with Cyclops, it’s a visual analysis object  which encapsulates several types of color and luma analysis  (difference, threshhold, match, etc.) to a number of user-specified  zones. It works with a QuickTime-compatible camera. The jit.cyclops  object functions the same, but works with Jitter matrices, rather  than live input. Cyclops was written by Eric Singer; the object is  maintained and distributed by Cycling ’74.

Some testing guidelines:
========================
1. Please read the manual before starting to use the object
2. Please direct feedback and bug reports to maxmsp@cycling74.com (or  jitter@cycling74.com) using this subject line, so that we can keep  all discussion about the beta under a single topic in the forum.
3. Please use the Bug Reporting Guidelines (attached below) when  reporting problems. Don’t forget to specify OS, chipset (PPC/Intel)  and to include a patch.

Known gotcha
============
Note that Cyclops takes control of an attached camera when it is  instantiated. This means that the typical sequence:

a. create Cyclops object in a patcher
b. option-click on Cyclops object to get help file
c. play with help file

will not work!!! You need to open the Cyclops help file directly (in / Applications/MaxMSP 4.6/max-help/cyclops-help/). Please do not report  this as a bug.

So, thanks for your interest and your time, and for reading this note  all the way to this point. Your reward is the link.

The beta version can be downloaded from:

http://www.cycling74.com/download/cyclops13UBb1.dmg

The Elves

===================================================
===================================================

BUG REPORTING GUIDELINES

Please report any problems you experience with clear and complete
information, including steps to reproduce, software and system
information, and where possible, an isolated example patch and crash
log. Something like the following would be ideal. This makes it
easier for us to find and fix the problems you experience. Without
such clear and complete information, it is less likely we will be
able to.

Summary:
Provide a descriptive summary of the issue.

Steps to Reproduce:
In numbered format, detail the exact steps taken to produce the bug.

Expected Results:
Describe what you expected to happen when you executed the steps above.

Actual Results:
Please explain what actually occurred when steps above are executed.

Regression:
Describe circumstances where the problem occurs or does not occur,
such as software versions and/or hardware configurations.

Notes:
Provide additional information, such as references to related
problems, workarounds and relevant attachments.