MIDAS recommends that if you are converting show files across PRO series console types (for example from a PRO2 to a PROX), allow for plenty of time before the tour or show preparation to convert the show file and make the necessary tweaks as outlined below, and fully test the show file before using it live.MIDAS cannot be held responsible if these recommendations are not followed.This article outlines transferability of show files on MIDAS PRO series console types in four main sections:Part 1. Software RevisionsPart 2. Console PlatformsPart 3. RecommendationsPart 4. Offline Editor GuidanceCurrent Software Version Release (As of December 2018) 
Console TypeSoftware Release
PRO1/2/2C/XGen 3.4.X
XL8/PRO3/6/9Gen 2.6.X
These 2 branches of software will be referred to throughout this article.PART 1- Software Revision
  • With the caveat of part 2 below (Console Platforms), show files that are built on Gen 2.6.x are transferable onto Gen 3.4.x with some re-alignment and testing
  • Gen 3.4.x will not support any show files created before Gen 2.6 (June 2015)
  • Any show files built before Gen 2.6 are not compatible for use on PRO 3/6/9/XL8 consoles. Please see recommendations for transferability (parts 2 and 3)
PART 2- Console PlatformsThere are a number of things to consider when converting the show file from one platform to another (for example, PRO2 to PROX). This is due to the difference in console functionality, layout, and hardware (for example, the rear local I/O of a PRO2 is very different from a PRO6). The list below is by no means exhaustive, but it will provide direction on key elements and direct the thought process and considerations.
  • The version of software must be the same on both the consoles, otherwise effects may be missing from the effects rack (for example a PRO6 on G2.6.x and a PROX on G3.4.x
  • The first time you import a show file (for example, a PRO2 show to a PROX) and load it, it will run a background conversion program. (A progress bar will show updating scene at the bottom of the screen.) This is a silent operation and requires no intervention from the user apart from loading the show as usual.
  • The following example is of show file transfer from a PRO2 to PROX: When the show is first transferred across and then loaded, the first 3 AES50 ports on the PRO2 will be attached to the F.O.H. I/O on the PROX and all of the I/O labels will be replaced with Unassigned. The Stage I/O tab will load completely blank. How you configure / reconfigure the I/O after this is very much up to the user, but you may need to attach and configure any further I/O to the PROX stage box and then patch it. Patching information will definitely be lost for any I/O attached to the PRO2 on ports 4, 5, and 6.
  • The automation itself will transfer across without issue as it is linked numerically to paths and does not depend on the I/O patch, so you wont see EQ settings that were on Aux 16 now appearing on Mtx 16 (for example).
  • Channels, Auxes, Matrixes etc., will all map 1:1 when going from a PRO2 to PROX for example. The path map conversion is not sequential, it is only sequential within path types so there are no issues with (for example) the automation on one path being shifted to another unrelated path.
  • Another thing to keep in mind (for example, PRO2 to PROX again) is that the console will lose its Surface and Monitor I/O in the Patching Page, meaning it is not possible to change or re-patch the monitoring.
PART 3- RecommendationsMIDAS recommends using preset files to rebuild shows if and when required, however use the following information as a reference:Note: This is not an exhaustive list, but some guidance to moving Presets across platforms.
  • It is possible to go forwards in versions, it may not possible to go backwards in versions without issues.
  • Patching Presets are not transferable between different console types.
  • Naming Sheet Presets: be aware that PRO3/6/9/X and XL8 all have two Naming Sheets (one for Inputs, one for Outputs) while PRO1 and PRO2 both have a single sheet. You can only transfer the Input sheets onto PRO1 and PRO2, and if PRO1 and PRO2 name sheets are transferred to a PRO3/6/9/X or XL8, only the Inputs and Aux Rtns names will be imported.
  • When moving Preset files, be aware of the specification differences between consoles: For example, when moving a PRO1 FX rack preset (max 6 FX) to a PRO X FX rack (max 24 FX), the PRO X will only accept the first 6 effects and leave the FX in the other slots unchanged; if moving from PROX to PRO1, the PRO1 can only import the first 6 effects.
  • This also applies to:
            - GEQ Rack Presets            - Store Scope Presets            - Recall Scope Presets
  • The Preferences regarding the Tap Tempo/ Meters Pre button operates differently on PRO1 and PRO2 than it does on all other consoles. This may require changing once a User Preferences preset has been transferred.
PART 4- Offline Editor Guidance
  • When using the Offline editor (for example PROX), you must always use the correct version of editor that ties in to the release of software. For example, PROX running Gen 3.4.4 should use the Gen 3.4 offline editor
  • The correct offline editor should always be used, as it is Console/Platform specific.