Behringer X32 Scene Parser Family User Manual
पीडीएफ
दस्तावेज़
विज्ञापन
विज्ञापन
X32 Scene Parser https://sourceforge.net/projects/x32sceneparser/ User Manual Copyright (C) 2014-2017 Paul Vannatto Version 1.09 April 2017 License This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/ Acknowledgments Many thanks to the following: The Behringer Forum members for their many suggestions and encouragement. It was because of the numerous discussions on the forum that this X32 offline tool was created and developed. Patrick-Gilles Maillot for his enormous effort in updating the OSC Remote Protocol document. Without this document, this app probably would not have begun. Music Group for creating the X32 eco-system and making the X32 specific OSC command language available so that developers could provide enhancements beyond the standard capabilities of the X32. X32 Scene Parser User Manual Purpose The X32 Scene Parser was designed to use an OSC type (scene, snippet or preset) file created by the X32, one of its apps, or other tools as a starting point to create a snippet (or preset) file that makes specific changes to the X32 - no more, no less. This is accomplished using various filters, text editing functions, and specialized tools provided by the Scene Parser. It was intended as an offline enhancement tool for the X32 eco-system, with a specific focus of providing a mechanism to produce fine-tuned snippets. Work Flow On the Parse screen, an OSC based file (scene, snippet, preset) is selected, filters are chosen, and import type (Parse, Input, List) selected. The file is then imported and processed using the selected parameters. The results are added to the text editor on the Results page. These results can then be modified/manipulated using standard text editor functions (cut, copy, paste, search, replace, etc) to fine tune the functionality of the snippet. Other Scene Parser specific functions, such as macro functions (range replace, copy, delete) can also be used to further refine the snippet. As an added bonus, specialized processes (Ch Arranger, Copy EQ or headamps, DCA or Mute Group analysis, scripting of commands, etc.) have been provided. Other specialized processes will be added as requested or required. The final results can then be saved as a snippet or preset file that can then be loaded into the X32. The resulting X32 change will be what is expected - no more, no less. An alternative Input-Output list can also be created for use during setup. Page 2 X32 Scene Parser User Manual Contents Quick Start Guides Parse a file........................................................4 Input a file........................................................4 Compare 2 files................................................4 Merge 2 files.....................................................4 Import an X-Air scene file................................4 Save the file......................................................5 Create an Input/Output List..............................5 Arrange Channels.............................................5 Input-Output Mutes and Fader Levels..............5 Mutes................................................................5 Fader Levels.....................................................6 Copy EQ...........................................................6 Copy Headamps...............................................6 DCA Analysis...................................................7 Mute Group Analysis........................................7 Sends Analysis..................................................7 Range Functions...............................................8 Range Scripts....................................................8 Filter Values......................................................8 Screens Parsing..............................................................9 Results............................................................11 Range..............................................................12 Range Scripts..................................................13 Channel Arranger...........................................14 Input-Output Mutes & Fader Levels..............15 Copy EQ.........................................................16 Headamps.......................................................17 Filter Values....................................................18 DCA Analysis.................................................19 Mute Group Analysis......................................20 Sends Analysis................................................21 Setup...............................................................22 Glossary................................................................23 Page 3 X32 Scene Parser User Manual Quick Start Guides Parse a file Import a file by either entering the path/filename in the Input File edit box or click on the file icon (to the right of the edit box) to launch the Open File dialog. Select the required filters of items that are to be parsed (extracted). For example, if all channel info for channels 1-16 and the headamps are required, check Ch 1-8, Ch 9-16, Headamps. Click on the Parse button. This will parse (or extract) the OSC command lines from the input file as per the filters chosen and add the results to the Results editor. The resulting text are a number of lines of OSC commands, each with various parameters. Input a file Import a file by either entering the path/filename in the Input File edit box or click on the file icon (to the right of the edit box) to launch the Open File dialog. Select Input (to the left of the Parse button). This will tell the Scene Parser to input the complete file to the Results editor. Click on the Input button. The resulting text are a number of lines of OSC commands, each with various parameters. Compare 2 Files (create a snippet of the differences) Select Compare input type Get the Primary and Secondary files Click on the Compare button. The resulting text are a number of lines of OSC commands representing the differences of the two files. Merge 2 Files (eg. a scene and a snippet) Select Compare input type Get the Primary and Secondary files Click on the Compare button. The resulting text are a number of lines of OSC commands representing a combination of the two files (secondary file overwrites any differences). Import an X-Air scene file Select an X-Air scene file by either entering the path/filename in the Input File edit box or click on the file icon to launch the Open File dialog. Select Import (Input Type). Select the desired filters of items that are to be imported. Click on the Import button. This will import and convert the X-Air OSC command lines from the input file as per the filters chosen and add to the Results editor. The resulting text are a number of lines of OSC commands, each with various parameters. Page 4 X32 Scene Parser User Manual Save the File The OSC commands can be further modified using standard text editing techniques (cut, copy, paste, delete, etc.) as well with the Range set of editing features. The snippet header line (first line in the text) can be changed (such as the title). Changing the text in the Title edit box will change it on the first line of the editor. When all modifications are complete, enter the Output file path/filename or click on the file icon to launch the Save File dialog. Click on the Output button to save the file. Create an Input/Output list Import a file by either entering the path/filename in the Input File edit box or click on the file icon (to the right of the edit box) to launch the Open File dialog. Select List (to the left of the Parse button). This will tell the Scene Parser to create an input/output list rather than the standard OSC command lines in the Results editor. Select the desired I/O filters from the surface inputs and/or Routing sections. Click on the List button. The resulting text will be an input/output list as per the filters selected. This list can be saved as a text file by entering the Output file path/filename or click on the file icon to launch the Save File dialog. Click on the Output button to save the file. Arrange Channels Import a file by either entering the path/filename in the Input File editbox or click on the file icon (to the right of the edit box) to launch the Open File dialog. Select Surface Input and click on the ChArrange button. This will parse the input file, using the filters and populate the grid in the ChArrange screen. Rearrange the channel order by dragging the channel header to the left or right. Adjust the first and last channel to transfer. Click on Transfer button when finished. This will transfer the channel OSC commands to the Results editor. Input-Output Mutes and Fader Levels Import a file by either entering the path/filename in the Input File editbox or click on the file icon (to the right of the edit box) to launch the Open File dialog. Select Surface Input and/or Surface Output filters Click on the In-Out button. This will parse the input file, using the filters and populate the mute check list and fader levels on the In-Out screen with appropriate values. Mutes The Include filter list is equivalent to the Surface Inputs and Outputs filters on the Parse screen. Change the mute values by checking/unchecking the appropriate checkboxes. Click on Transfer button when finished. This will transfer the appropriate OSC commands to the Results editor. Page 5 X32 Scene Parser User Manual Fader Levels The channels affected are selected in banks of 8. Select one of the banks. Check the Relative checkbox and change the value below to -5.5. Click on the All 8 button. This will decrease all values by 5.5 db. Click on Transfer button when finished. This will transfer the appropriate OSC commands to the Results editor. Copy EQ Import a file by either entering the path/filename in the Input File edit box or click on the file icon (to the right of the edit box) to launch the Open File dialog. Click on the Copy EQ button. Scene Parser will analyze the input file, populate the Copy EQ screen with the data (slot, sides, values), then change to the Copy EQ screen. Choose which slot and side to copy values from, then choose which slot and side to copy those values to. Click on the Transfer button to transfer the values to the Results editor. This can be repeated as necessary. Click on the Done button to change to the Results screen. Enter the Output file path/filename or click on the file icon to launch the Save File dialog. Click on the Output button to save the file. Copy Headamps Import a file by either entering the path/filename in the Input File edit box or click on the file icon (to the right of the editbox) to launch the Open File dialog. Click on the Copy Headamps button. Scene Parser will analyze the input file, populate the Headamps screen with the data (phantom and gain), then change to the Headamps screen. Choose the block of headamps to copy values from and to. Choose whether to include the gains and/or the phantom values when copying. Click on the Transfer button to to transfer the values to the Results editor. This can be repeated as necessary. Click on the Done button to change to the Results screen. Enter the Output file path/filename or click on the file icon to launch the Save File dialog. Click on the Output button to save the file. Page 6 X32 Scene Parser User Manual DCA Analysis Import a file by either entering the path/filename in the Input File editbox or click on the file icon (to the right of the edit box) to launch the Open File dialog. Click on the DCA’s button. Scene Parser will analyze the input file, populate the DCA matrix with the current values, then change to the DCA screen. The current DCA values are displayed in a matrix of check boxes (channels x DCAs). There are 4 layers of channels, similar to the X32. Check/uncheck the appropriate check boxes to change the status. Add the snippet title and choose what to include in the snippet. Click on the Transfer button o create the OSC commands in the Results editor. Mute Group Analysis Import a file by either entering the path/filename in the Input File editbox or click on the file icon (to the right of the edit box) to launch the Open File dialog. Click on the Mute Groups button. Scene Parser will analyze the input file, populate the mute group matrix with the current values, then change to the Mutes screen. The current mute group values are displayed in a matrix of check boxes (channels x mute groups). There are 4 layers of channels, similar to the X32. Check/uncheck the appropriate check boxes to change the status. Add the snippet title and choose what to include in the snippet. Click on the Transfer button to create the OSC commands in the Results editor. Sends Analysis Import a file by either entering the path/filename in the Input File editbox or click on the file icon (to the right of the edit box) to launch the Open File dialog. Click on the Sends button. Scene Parser will analyze the input file, populate the sends grid with the current values, then change to the Sends screen. The sends level, mute, or tap values can be displayed and changed as required. There are 4 layers of channels, similar to the X32. Select Changes Only, then click on the Transfer button to transfer any changes made to the Results editor. OR Unselect Changes Only to transfer current state to the Results editor. The results could be further limited by selecting Current Layer before clicking on the Transfer button. Page 7 X32 Scene Parser User Manual Range Functions Once a basic snippet is created in the editor, the resulting OSC commands can then be fine tuned using standard editor functions (cut, copy, paste, delete, etc.). It can also be fine tuned using macro functions, such as range replace, copy and delete (on the Range screen). For example, changing all channels 3-7 OSC commands to channels 4-7, select the range replace with the following parameters - Find Prefix: /ch/ - From: 3 - To: 7 - Suffix: / - Replace Prefix: /ch/ - Replace From: 4 - Reverse order: checked (since the find and replace ranges overlap) Click on the Replace button. Range Scripts Range functions are a very powerful method of changing snippets on a macro level. Sometimes certain changes require multiple range changes. Scripts can be created to automate these range changes. For example, if channel 17 needs to be moved to channel 5 and all other channels shifted appropriately, that would require a number of range changes. This would include: - Replace /ch/17 to /ch/33 (temp assignment) - Replace /ch/5 to 16, to /ch/6 (shifting ch 5-16 over one) - Replace /ch/33 to /ch/5 (moving ch 33 (formerly ch 17) to ch 5) - SortAll (sort the results) To make it easier to create script lines, fill in the various range edit values, then click on the CBE (create by example). Repeat for each step of the script. Filter Values The X32 snippet GUI includes a filter matrix. This is used to create the desired snippet. Unfortunately, this GUI is limited in scope to what it can create. This is why the Scene Parser was created. This filter GUI also provides an indication of what that snippet actually does. Unfortunately, these filter values are in the form of bitmaps and must be calculated and the resulting values inserted into the snippet header (first line). The Filter Values screen provides a visual method of calculating these values. Select the various sections that applies to this snippet and click on Update. The resulting filter values are calculated When everything is correct, click on the Transfer button to insert these values into the snippet header. Page 8 X32 Scene Parser User Manual Screens Parsing On the Parse screen, one or more OSC based files (scene, snippet, preset) are selected, filters are chosen, and import type (Parse, Input, List, Compare, Merge) selected. The file(s) is then processed using these parameters. Primary/Secondary File: For Parse, Input and List, an OSC type file (scene, snippet, preset, etc.) can be selected to be imported as a starting point of the snippet to be created. The path\filename can be typed in the edit box or can be selected using the file icon (to the right). This icon will launch the File Open dialog. Goto the location and select the desired file. If the file is not a scene file (*.scn), select the file type to change the file filter. Once the file is chosen, click on Open. For Compare and Merge, primary and secondary files are selected. Select/Clear: This provides the ability to clear groups of check boxes. Input Type: Parsing Input List There are 5 input types that can be created. Analyzes the complete input file and parses (extracts) items as per the selected filters. The resulting OSC multi-variable commands are added to the Results editor. Imports the complete file (no parsing done) to the Results editor. This can be used with existing snippet files that simply need some adjustments. Limits the parsing to Surface Inputs and Routing and produces a list of these inputs/outputs in a different form than snippets. Page 9 X32 Scene Parser User Manual Compare Compares a primary and secondary file and provides the differences in the Results editor. This can be saved as a snippet for further updating other scenes with the differences by either importing the snippet to the X32 and applying to the various scenes OR using the Merge type to apply to existing scene files. Merge Merges the primary and secondary files together. When differences in the OSC commands are encountered, the secondary file commands will be used. Using a snippet (created using the Compare type), multiple scene files can be updated with the same changes. Import Imports an X-Air scene file as per selected filters and converts various OSC command differences to the X32 format. The resulting OSC multivariable commands are added to the Results editor. Filter Groups: There are 5 filter groups that are grouped by functionality. They can be disabled by unchecking the appropriate group header (eg. System Config). These are disabled for the List, Compare and Merge types. Transfer Header: This should be checked if the input file type is the same as the output (eg. Snippet). If they are not the same (eg. scene input, snippet output), the header will be different and should not be transferred. Page 10 X32 Scene Parser User Manual Results The Results screen receives the processing results of other screens (Parse, Range, Filter Values, Copy EQ, Headamps, DCA, Mute Groups, In-Out Mutes). This is the heart of the Scene Parser. Standard editor functions (find, replace, cut, copy, paste, select all, undo) are conveniently located on the toolbar and as shortcuts with the right-click popup menu. Find/Replace: The Find and/or Replace edit boxes must be completed for this function to work. Find simply finds the first occurrence from the cursor or beginning (if checked) and highlights the results. Replace replaces the first occurrence found (unless Replace All is checked). There will not be any prompting during the process. If the results are not as expected, simply undo and try again. Range: This provides a link to the Range screen, where further processing on a macro level can be accomplished. Cut/Copy/Paste: These are standard editing functions. Keyboard shortcuts (Ctrl X, etc.) can also be used. Select All: Selects everything in the editor. Undo: Undoes previous editing. This can be repeated back o the first edit. Clear All: Clears the editor. Sort All: Sorts the lines in the editor in alphanumeric order. Output Type: This determines the type of output and changes the header and file extension accordingly. Title: The snippet title can be changed in the Title edit box, which automatically changes it on the header (first line in the editor). Clear Suffix: Removes the section to the right of the title in the header. Output File: The path\filename can be typed in the edit box or can be selected using the file icon (to the right). This icon will launch the File Save dialog. Nothing is actually saved until the Output button is selected. Page 11 X32 Scene Parser User Manual Range The Range screen provides editing tools on a macro level. It also provides scripting of multiple range commands to produce editing results that would normally require multiple steps. Reset: Resets the Range Processing section to the default. Replace/Copy/Delete: This determines the type of range processing. Replace: This changes the existing OSC command line found with the Find values to the Replace values. The Find To and From values determines the range for both Find and Replace. For example, if the find is from 3-6 and the Replace begins with 5, it will process through to 8. Leading zero’s will be added as required. Copy: Makes a copy of the existing OSC command line found with the Find values, and changes it with the Replace values. The copied lines are added to the end of the editor. Delete: This uses the Find values and deletes the found OSC command line(s). Process in Reverse: If the Find and Replace ranges overlap, they need to be processed in reverse. For example if the Find range is 3-6 and Replace range is 5-8, 6 needs to be replaced (or copied) to 8 first, then 5 to 7, etc. If not processed in reverse, all lines will end up as 8. CBE: Create By Example. Once range processing values have been verified, they can be added to the script editor (below). A multiple range processing script can be developed using this method. Page 12 X32 Scene Parser User Manual Range Scripts Scripts combine multiple range commands with special commands in order to process complex changes to the snippet. Examples are provided in the default.sps file as well as a separate download (https://sourceforge.net/projects/x32sceneparser/files/). The easiest way to create script lines is to setup a range process above, then click on CBE (create by example). This will add the script line with the appropriate parameters. Script Commands: 3 range commands (Replace, Copy, Delete) and 3 special commands (SReplace, Add, SortAll) as explained below Replace/Copy: 8 parameters identical to the above interface. Delete: 4 parameters SReplace: 3 parameters (Find, Replace, FromBegin) Add: 1 parameters (OSC command string) SortAll: No parameters. It re-sorts the Results editor OSC commands. # (pound): Comments begin with the #. * (asterix): Used as a placeholder, using the appropriate parameter of the previous script line. ! (exclamation): Used to substitute for a space (space is also a delimiter character). Process in Reverse: Can be False/True or 0/1 Run Script: This processes the script file and applies the changes to the Results editor OSC command lines. Load Script: This loads a previously save script file. Save Script: This saves the current script to a file. Clear Script: This clears the script editor. Page 13 X32 Scene Parser User Manual Channel Arranger The Channel Arranger screen provides the ability to rearrange the channel order, simply by dragging the columns to the left or right. Col Width: This will increase/decrease the default width of the columns. Individual widths can be adjusted by dragging between the column header First Chan This will limit the range (between first/last) of the channels transferred. Last Chan This will limit the range (between first/last) of the channels transferred. Rearrange: By dragging the column header to the left or right will move that column accordingly. Transfer: This will transfer the channel arrangement to the Results editor. This can be repeated as necessary, but will overwrite (clear results editor) of any previous changes. Page 14 X32 Scene Parser User Manual Input-Output – Mutes & Fader Levels The Input Output screen provides tools to create input/output mutes and/or fader level snippets. Title: This provides the snippet title for the Results editor. Clear Editor: Clears the Results editor before sending the mutes values. Transfer: Transfers the respective OSC commands to the Results editor. If the Clear Editor is selected, it will create a new snippet. If not, it will add to the current snippet. Mutes Include Filter: The include filter is very similar to the Surface Inputs and Surface Outputs filters on the Parse screen. Select/Clear All: Selects or clears all mutes in the list. Output: Changes the output action from Transfer (to editor) to file output. The filename will be the Title and will use the snippet default directory to complete the path. Fader Levels Relative: Change values +/- relative to existing, else values are changed as absolute. All 8: Change all 8 fader level values to the value in the edit box above oo Db: Change fader level values to oo db (infinite/off). All Levels: Transfer all fader levels to the Results editor, else transfer only changes. Page 15 X32 Scene Parser User Manual Copy EQ The Copy EQ screen provides the ability to copy graphics EQ values from one slot or side to another. The initial values are populated by clicking on the Get button or Copy EQ button on the Parse screen. Get: This is the same as the Copy EQ button on the Parse screen. From EQ: Select the slot of the EQ containing values to be copied. This will change the side, type and values appropriately. Select the side if there are more than one. To EQ: Select the slot of the EQ that are to receive the values copied. This will change the side, type and values appropriately. Select the side if there are more than one. Transfer: This will transfer the values From EQ -> To EQ and change the values in the Results editor. This can be repeated as necessary. Done: This changes to the Results screen. Page 16 X32 Scene Parser User Manual Headamps The Headamps screen provides the ability to copy headamp values from one block of 8 to another. The initial values are parsed from the input file by clicking the Get button (or Copy Headamps button on the Parse screen). Get: This is the same as the Copy Headamps button on the Parse screen. The phantom and gain values will be parsed from the input file and displayed as LED and test values. From Headamps: Select the block of 8 headamps containing values to be copied. Include: Choose whether the gain and/or phantom values are to be included in the copy. To Headamps: Select the block of 8 headamps that are to receive the values copied. Transfer: This will copy the values From Headamps -> To Headamps block and change the values in the Results editor. This can be repeated as necessary. Done: This changes to the Results screen. Page 17 X32 Scene Parser User Manual Filter Values The Filter Values screen provides the ability to calculate the filter values indicating the functionality of the snippet in the X32 snippet GUI. Unfortunately, some snippets created by the Scene Parser does not have appropriate filter values. Update: Once the appropriate filters are selected, this will update the Snippet Filter Value. This comprises of 5 numbers of bitmap equivalent of the 4 sections of the filters. The Parametric, Effects and Console comprise the first section. The last number is always 1 (not sure why). Transfer: This transfers the Snippet Filter Values to the Results editor header, to the right of the title. Page 18 X32 Scene Parser User Manual DCA Analysis The DCA screen provides a visual analysis of the DCA assignments. The initial values are populated by clicking on the DCA’s button on the Parse screen. Changes can the be made to the desired check box. DCA/Channel matrix: The matrix provides a visual analysis of the DCA assignments using four channel layers, similar to the X32. Changes can be made by clicking on the appropriate cell. As these change, the actual bitmap value will be shown to the right of the Layer radio group. Snippet Title: The snippet title can be added here. Include: Select the sections to be included in the resulting OSC commands generated when the Transfer button is clicked. Clear Editor: The Results editor is cleared before the OSC command lines are added. Transfer: This generates the OSC command lines with the changes made to the DCA/Channel matrix and adds the results to the Results editor. Page 19 X32 Scene Parser User Manual Mute Groups Analysis The Mute Group screen is identical in functionality to the DCA screen. It provides a visual analysis of the mute group assignments. The initial values are populated by clicking on the Mute Groups button on the Parse screen. Changes can the be made to the desired check box. Mute Group/Channel matrix: The matrix provides a visual analysis of the mute group assignments using four channel layers, similar to the X32. Changes can be made by clicking on the appropriate cell. As these change, the actual bitmap value will be shown to the right of the Layer radio group. Snippet Title: The snippet title can be added here. Include: Select the sections to be included in the resulting OSC commands generated when the Transfer button is clicked. Clear Editor: The Results editor is cleared before the OSC command lines are added. Transfer: This generates the OSC command lines with the changes made to the Mute Group/Channel matrix and adds the results to the Results editor. Page 20 X32 Scene Parser User Manual Sends Analysis The Sends provides a visual analysis of the sends values (levels, mutes, taps). The initial values are populated by clicking on the Sends button on the Parse screen. Changes can then be made to the appropriate values in the grid. Channel /mixbus grid: The grid provides a visual analysis of the sends values using four channel layers, similar to the X32. Changes can be made by selecting any grid cell and make the appropriate change. Blank cells represent infinite value (level), off (mutes) or not applicable (taps). Bus 1-16/matrix: This is very similar to the channel/mixbus grid. But it displays the bus sends to the matrixes, LR and mono. The changes and blanks are identical to the channel/mixbus grid. Layer: There are 3 input layers and a bus layer to choose from. Type: Choose levels, mutes or taps to show appropriate values. Clear Editor This clears the Results editor of all text. Changes Only Select this if only the changes are desired to be transferred to the Results editor. Otherwise all values will be transferred. Current Layer Select this if only the current layer is desired to be transferred to the Results editor. Otherwise all layers will be transferred. Transfer: This generates the OSC command lines and adds them to the Results editor. Page 21 X32 Scene Parser User Manual Setup The Setup screen allows the user to set various defaults. Directory defaults: The path can be typed in the edit box or can be selected using the file icon (to the right). This icon will launch the Folder dialog. Select the location and click on OK. Script File default: The path\filename can be typed in the edit box or can be selected using the file icon (to the right). This icon will launch the File Open dialog. Select the location and desired script file. Then click on Open. Include in Channel List: Select what will be included in the channel/output list. Color buttons: These will launch the color dialog in order to choose the background and font colors of the various edit fields. Editor Font Size: The size of the editor text can be established by entering or increasing/decreasing the value. Include in In/Out List: These fields can be included in the Input/Output list. In/Out Delimiters: The delimiters between fields in the Input/Output list can be changed. Save Defaults: All items on this screen will be saved to the SceneParser.ini file in the same directory as the app. These values will be loaded on start up. Reset: This sets all default values back to original values (set by me). Page 22 X32 Scene Parser User Manual Glossary Bitmap Values: Multiple choices can be stored as a single integer called a bitmap. DCA's, mute groups and snippet filters are stored in this manner. It is based on binary positions of a byte value (2 to the power of). 0000101 is a byte representation of the number 5 (0+0+0+0+4+0+1). These positions can be translated to choices. For example, consider channel 1 mute groups. It can have a combination of up to 6 mute groups. If mute groups 2 and 5 are selected, the bitmap value would be 18 (2 to the power of 1 + 2 to the power of 4 – positions are zero based). OSC Protocol: Open Sound Control (OSC) is a protocol for communication among computers, sound synthesizers, and other multimedia devices that is optimized for modern networking technology. The X32 is based Behringer’s implementation of this protocol, as defined in the OSC Remote Control Protocol v1.01 (Oct 17, 2012). This has recently been updated by Patrick-Gilles Maillot with his X32 OSC Protocol (Nov 20, 2014). The protocol specifies that OSC command lines must include a command, type (of parameters) and parameter(s). Each part is 4 bit null terminated. Parsing: The ability to extract specific portions of an input, using defined and focused filters. Since snippets are very similar to scenes, they can be created from these scenes. The problem is that scene typically have over 2000 lines of OSC command lines, making it difficult to remove all unwanted lines in order to focus the snippet on a particular change(s). A parsing engine needed to be developed to make this task easier to accomplish. The Scene Parser is that parsing engine. Scenes: a compilation of OSC commands in ASCII format (text file) that captures almost all functionality of the X32 digital console. These can be stored in the X32 or exported (and imported) to an ASCII file (.scn). It uses the multi-parameter type of OSC commands that combine common parameters on one line. Scenes can also read and interpret the single-parameter type OSC commands. These commands do not completely comply with the OSC protocol in that there is no type parameter between the command (path) and parameter(s) and are text lines (not 4 bit null terminated). Snippets: a compilation of specific OSC commands in ASCII format that provide specific functional changes to the X32. These can be stored in the X32 or exported (and imported) to an ASCII file (.snp). Snippets look very similar to scenes but typically have far fewer OSC command lines and are specifically focused on a specific task. Page 23 ">
/
डाउनलोड
बस एक दोस्ताना अनुस्मारक. आप दस्तावेज़ को यहीं देख सकते हैं. लेकिन सबसे महत्वपूर्ण बात, हमारे एआई ने इसे पहले ही पढ़ लिया है. यह जटिल चीजों को सरल शब्दों में समझा सकता है, किसी भी भाषा में आपके सवालों के जवाब दे सकता है और सबसे लंबे या सबसे जटिल दस्तावेजों को भी जल्दी से नेविगेट करने में आपकी मदद कर सकता है.
विज्ञापन