Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Paul Vannatto" data-source="post: 141043" data-attributes="member: 4071"><p>Re: X32 Discussion</p><p></p><p>Regarding your questions about the actual snippet file info, I can explain a few things.</p><p></p><p>The header (first line) has the following elements</p><p>* #2.1# is the version number and is important for the X32 OSC engine. If it is absent, it will ignore the whole snippet</p><p>* "Intro" is the snippet name or title (always in double quotes)</p><p>* 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.</p><p></p><p>If you notice the actual OSC command lines in your snippet, they include the command path (eg. <span style="color: #3E3E3E">/dca/1/config</span>), then a number of values (eg. <span style="color: #3E3E3E">"Man" 0 WH</span>). 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 (<a href="https://sites.google.com/site/patrickmaillot/x32" target="_blank">https://sites.google.com/site/patrickmaillot/x32</a>). For example, changing the DCA 1 scribble strip color the command would be <span style="color: #3E3E3E">/dca/1/config/color YE.</span></p><p><span style="color: #3E3E3E"></span></p><p><span style="color: #3E3E3E">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).</span></p><p><span style="color: #3E3E3E"></span></p><p><span style="color: #3E3E3E">Paul</span></p><p><span style="color: #3E3E3E"></span></p><p><span style="color: #3E3E3E"></span></p></blockquote><p></p>
[QUOTE="Paul Vannatto, post: 141043, member: 4071"] 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. [COLOR=#3E3E3E]/dca/1/config[/COLOR]), then a number of values (eg. [COLOR=#3E3E3E]"Man" 0 WH[/COLOR]). 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 ([url]https://sites.google.com/site/patrickmaillot/x32[/url]). For example, changing the DCA 1 scribble strip color the command would be [COLOR=#3E3E3E]/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 [/COLOR] [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!
