Max Object Discussion

The flame Max object (pre OSX and OSX objects) enables you to send int/float controller values from Max to the Capybara through the Flame Firewire interface, using the MIDI controller channel and controller number naming scheme (controller numbers 0-127 for Kyma's !cc00-!cc127), but avoiding the restricted MIDI controller value resolution.

Known problems with the pre OSX version: when the amount of used flame objects goes down to zero something misfires, probably related to memory mismanagement, causing Max to crash every now & then. A solution is to always have at least one instance of the object hanging around while working with your flame patches. The other problem is that the data sending is not done at high priority, resulting in imprecise timing. Best timing is achieved when only Max is running. So compile, load and start your Kyma Sound and quit Kyma (make sure you first select: Preferences>Miscellaneous>Stop Sound on File|Quit>no).

These problems seem to be fixed in the OSX object. Bugs and other problems: tweak along at the bottom...

-- DavidKiers - 27 Oct 2003

The AVCFlameExternal.zip update enables the max object to work with the AV/C beta update to the Flame Firewire interface firmware. If you're not using the updated firmware, there is no reason to use this updated object. At this moment the connection to the Capybara is lost after working with the flame object and quitting max. Select "Initialize DSP" in the Kyma software to reconnect. This will be fixed in a future update.

-- DavidKiers - 19 Apr 2006

Absolutely fantastic David - thanks so much. Every time I need to do some Max/Capy work you update the object - thanks a million, hugelly appreciated

-- GarthPaine - 19 Apr 2006

Hi David

I am having problems with the Flame object in Max 4.5.7

• error: can't fragload flame (missing <>), err -2804

I am running beta AVC firmware in the flame, and installed the AVCFlameExternal?. Any advice?

-- GarthPaine - 18 May 2006