From ftm
| Line 8: | Line 8: | ||
:: '''Workaround''': protect the ftm object with a "list" prefix like this: | :: '''Workaround''': protect the ftm object with a "list" prefix like this: | ||
:: ''<atom to be routed against> "list" <ftm object> <anything else>...'' | :: ''<atom to be routed against> "list" <ftm object> <anything else>...'' | ||
| + | |||
| + | ; unpack : can't pass ftm objects | ||
| + | |||
| + | ; append / prepend : be careful with single ftm atoms | ||
; zl slice : sometimes the ftm object goes missing (see [[Media:Zl_slice_ftm_crash.pat]]) | ; zl slice : sometimes the ftm object goes missing (see [[Media:Zl_slice_ftm_crash.pat]]) | ||
| + | |||
[[Category:FAQ]] | [[Category:FAQ]] | ||
Latest revision as of 14:43, 26 October 2011
There are a number of Max objects that sometimes don't respond well to atoms containing FTM data objects such as fmat, dict, scoob, etc.
The list of Max objects known so far is:
- the Max print object doesn't know how to print the content of ftm data objects. Use ftm.print instead.
- route
- single ftm object is not routed (see Media:Route_ftm.pat)
- Workaround: protect the ftm object with a "list" prefix like this:
- <atom to be routed against> "list" <ftm object> <anything else>...
- unpack
- can't pass ftm objects
- append / prepend
- be careful with single ftm atoms
- zl slice
- sometimes the ftm object goes missing (see Media:Zl_slice_ftm_crash.pat)