Re: X32 Discussion
Regarding your questions about the actual snippet file info, I can explain a few things.
The header (first line) has the following elements
* #2.1# is the version number and is important for the X32 OSC engine. If it is absent, it will ignore the whole snippet
* "Intro" is the snippet name or title (always in double quotes)
* 0 0 0 0 0 are the bitmap values for 4 areas of the snippet filters (5th value is always zero). These can be generated using the Scene Parser filter generator if so desired. But there is a gotcha that I recently discovered. If you create a customized snippet using an external app (such as a text editor, python script, Scene Parser, etc.) and include these filters and load these into the X32 or X32-Edit, if you ever decide to save the show, it will re-write the snippet with OSC code related to that filter, thus losing your customization. So for customized snippets, I would recommend these be left as 0 0 0 0 0.
If you notice the actual OSC command lines in your snippet, they include the command path (eg.
/dca/1/config), then a number of values (eg.
"Man" 0 WH). This is the format that the X32 (and X32-Edit) generated in the scene and snippet files (multi-value OSC command lines). If you are wanting to change just one of those values (eg the color to yellow), it isn't possible with these multi-value commands. There are equivalent single value commands that can be used. These have been extensively documented by Patrick-Gilles Maillot in his OSC Protocol (
https://sites.google.com/site/patrickmaillot/x32). For example, changing the DCA 1 scribble strip color the command would be
/dca/1/config/color YE.
Regarding the order of processing, the OSC engine does process these scenes and snippets in the order that they are in the file. I haven't noticed any timing issues, since it processes these commands so fast. But it may be possible to have timing issues. I did notice that cues process the scenes first, then the snippets (if both are assigned).
Paul
