k y m a • t w e a k y — the kyma collective

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

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

The flame Max object (now 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.

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.

I use a Lemur (OSC device) controller with Kyma. I'm glad I found this because it makes a much cleaner and simpler Max translator from Lemur's OSC to Kyma. One thing I notice is that this direct !ccxx implementation ignores equivalent cc assignments in the VCS. In any case highly reccomended for anyone with a Lemur. Thanks David!

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.

Do you have plans to update your external to be compatible with the new beta AVC Flame firmware?

-- EdmundEagan - 16 Apr 2006

-- DavidKiers - 19 Apr 2006

%META:FILEATTACHMENT{name="AVCFlameExternal.zip" attr="h" comment="" date="1145450392" path="AVCFlameExternal.zip" size="33402" user="DavidKiers" version="1.1"}%

I use a Lemur (OSC device) controller with Kyma. I'm glad I found this because it makes a much cleaner and simpler Max translator from Lemur's OSC to Kyma. One thing I notice is that this direct !ccxx implementation ignores equivalent cc assignments in the VCS. In any case highly reccomended for anyone with a Lemur. Thanks David!

Do you have plans to update your external to be compatible with the new beta AVC Flame firmware?

-- EdmundEagan - 16 Apr 2006

The flame Max object 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.

The flame Max object (now 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 with 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).

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 version. Bugs and other problems: tweak along at the bottom...

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

Known problem: 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. I hope to fix this in the (osX?) future.

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 with 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).

Max Mac OS<X only...

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

-- DavidKiers - 27 Oct 2003

David, any timeline for an OSX version?

-- GarthPaine - 23 Mar 2004

I am afraid that I will not have time to solve the Max Mach-O incompatibility problems soon, high priority though and all help welcome.

-- DavidKiers - 23 Mar 2004

-- DavidKiers - 27 Oct 2003

-- DavidKiers - 23 Mar 200

-- DavidKiers - 23 Mar 2004

I am afraid that I will not have time to solve the Max Mach-O incompatibility problems soon, high priority though and all help welcome.

-- DavidKiers - 23 Mar 200

-- GarthPaine - 23 Mar 2004

-- GarthPaine - 23 Mar 2004

-- GarthPaine - 23 Mar 2004

David, any timeline for an OSX version?

%META:TOPICINFO{author="DavidKiers" date="1067272020" format="1.0" version="1.1"}% %META:TOPICPARENT{name="Tools"}%

Max Object Discussion

The flame Max object 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 problem: 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. I hope to fix this in the (osX?) future.

Max Mac OS<X only...

-- DavidKiers - 27 Oct 2003

%META:FILEATTACHMENT{name="flameinMax.jpg" attr="h" comment="" date="1067279830" path="flame in Max.jpg" size="53485" user="DavidKiers" version="1.1"}%