Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Note
titleOvation v10.1 Keys

Important:
Ovation 10.1 runs on the Ovation 10.0 keys for the duration of the beta cycle.
To get a free upgrade, you need a valid ASM contract and contact your Sales Partner,
providing your SafeNet Dongle Serial number and/or Cloud Activation Key number.
Do not install this version if you do not yet have valid keys



Table of Contents

Installation

...

    • Windows 10 Professional (64bit): MassCore/RAVENNA, Native & Native/RAVENNA ASIO
    • Windows 11 Professional (64bit): MassCore/RAVENNA, Native & Native/RAVENNA ASIO

Ovation 10.1 is supported under the Windows 10 updates;

...

Ovation 10.1 is supported under the Windows 11 updates - MassCore/RAVENNA, Native & Native/RAVENNA ASIO

    • 22H2 supported since Ovation 101.0 Beta1 : MassCore/RAVENNA, Native & Native/RAVENNA ASIO 
    • 21H2 supported since Ovation 10.0.3 Hotfix 2 Native & Native/RAVENNA ASIO

WARNING: MassCore and Intel 12th / 13th Gen CPU: Pyramix 14.1.0 & RTX64 4.4 required.
WARNING: Ovation 10 is no longer supported on Windows 7.
WARNING: Ovation 10 is supported on 4th Generation Intel Core Processors (4XXXK and higher) and will not launch on previous Processors generation

Recommended specifications Computer Specifications..

...

    • Ovation 10.1 runs on the Ovation 10.0 keys for the duration of the beta cycle.
    • Ovation 10.1 MassCore runs on a new RTX64 4.4 version. A MassCore Runtime update is mandatory, see MassCore Installation notes below.
      The RTX64 4.4 requires a new license, only available in Ovation 10.1 keys.

    • The Ovation 10.1 installer comes only as a 64bit version (64bit OS)
    • Ovation 10.1 users must refer to the Ovation 10 Installation Guide for details 
    • Pyramix is automatically installed along Ovation - no need to install Pyramix separately.
    • Before you perform a Windows major version update on a system already running a MassCore, it is important for users to remove MassCore from the MT Security MassCore tab prior to performing a system update. Details below.
      Take note that when selecting uninstall MassCore you will need to reboot your system as the uninstallation is completed during the system reboot.

      Note #1
      We highly recommend users to defer the Windows updates, so that it does not harm your system here for details on how to defer updates on Windows 10  or on Windows 11
      Windows 10 and 11 users should never update to Beta Windows version or major new updates before making sure they are supported by Merging.
      Note #2
      Users wanting to perform a Windows version update must follow the procedure here
       Windows Configuration Guide
      Users that apply Windows updates must refer to the Merging Compatible Windows updates here  Once you have updated your Windows, follow the Pyramix and MassCore installation.

...

    • Refer to the Ovation 10.1 Installation Guide for installation procedure and details on the specific BIOS settings and system configuration.
    • Ovation 10.1 MassCore runs on a new RTX64 4.4 version. A MassCore Runtime update is mandatory. 
      Please first install Ovation 10.1, then go in MT Security panel to uninstall the previous MassCore Runtime.
      Once uninstalled, go back in MT Security panel to install the RTX64 4.4 MassCore Runtime.
      Please then configure Ovation / Pyramix in the VS3 Control Panel. 

      The RTX64 4.4 requires a new license, only available in Ovation10.1 keys.

    • MassCore is compatible with Windows 11 (since Ovation 10.1 Beta 1)
    • It is necessary to remove the previous Ovation and Pyramix versions, if there is one, from the Windows Programs and Features, and then reboot your system before installing Ovation.
      Take note that when selecting uninstall MassCore you will need to reboot your system as the uninstallation is completed during the system reboot
      If you are planning to update your Windows, it is recommended to first remove MassCore before performing the update. In such case follow the procedure document
      https://merging.atlassian.net/wiki/display/PUBLICDOC/Windows+Configuration+Guide
      Updating Windows 10 to Windows 11 is potentially risky, please make a full backup of all your data before performing such update.
    • After installing Ovation 10.1, MassCore users will need to uninstall their previous MassCore from the MT Security setting, MassCore Tab, depending on the previous Ovation version you were running.
      If there is an older version present you will be warned and required to reboot before updating to the latest version.
    • If your Ovation system never had a MassCore version before, users will have to install the MassCore Runtime from the MT Security Settings > MassCore tab.

...

Two new speaker layouts for Sony 360 support have been added:

  • Sony 360 13.0:
    Mapping: C, L, R, Lrs, Rrs, Ctf, Ltf, Rtf, Ltr, Rtr, Cbf, Lbf, Rbf
  • Sony 360 15.0:
    Mapping: C, L, R, Lss, Rss, Lrs, Rrs, Ctf, Ltf, Rtf, Ltr, Rtr, Cbf, Lbf, Rbf
  • Both are properly supported by the Atmos ADM Export feature and allow exporting Dolby Atmos ADM Masters out of a Sony 360 layout either in Bed+Objects or Objects-only mode.

...

  • Ovation 10.1.0 Beta1: New rule - Random Sibling Cue:
    New Target rule: Random Sibling Cue, allowing rules to interact with random sibling cues (in addition to the existing random Child cues).
    (Sibling means a Cue on the same level.)
  • Ovation 10.1.0 Beta1: Bus/Group Solo Safe improvements:
    Mix Bus:
    Solo Safe protects any input strip sending to that Bus from being muted when soloing any other input strip. (Unchanged)
    Mix Group:
    Solo Safe protects any input strip sending to that Group from being muted when soloing any other input strip. It also protects the Mix Group Return Strip from being muted when soloing any other strip.
    When Solo Safe is not enabled, the Mix Group Return Strip is automatically protected anyway when soloing any input strip sending to that Group, but not when soloing any input strip not sending to that Group.
    (Changed as described above since 14.0.6)
    Aux Bus:
    Solo Safe protects any input strip sending to that Bus from being muted when soloing any other input strip. (Unchanged)
    Aux Group:
    Solo Safe protects the Aux Group Return Strip from being muted when soloing any other strip. (Unchanged)
  • Ovation 10.1.0 Beta1: Updated Channel naming.
    Channel types/Speakers naming convention has been updated to the Dolby standard, being:
    Left : L
    Center : C
    Right : R
    Surround Left : Lrs
    Surround Right : Rrs
    LFE : LFE
    Center Left : Lc
    Center Right : Rc
    Surround Center : Cs
    Side Left : Lss
    Side Right : Rss
    Wide Left : Lw
    Wide Right : Rw
    Voice of God : VoG
    Top left : Ltf
    Top Center : Ctf
    Top Right : Rtf
    Top Surround Left : Ltr
    Top Surround Center : Ctr
    Top Surround Right : Rtr
    Top Side Left : Ltm
    Top Side Right : Rtm
    Bottom left : Lbf
    Bottom Center : Cbf
    Bottom Right : Rbf
    Bottom Surround Left : Lbr
    Bottom Surround Center : Cbr
    Bottom Surround Right : Rbr
    Bottom Side Left : Lbm
    Bottom Side Right : Rbm
    Voice of Devil : VoD
    LFE2 : LFE2
    Note : Projects created from previous versions are automatically updated to the new naming convention.

  • Ovation 10.1.0 Beta1 : 5.1.2 / 7.0.2 / 7.1.2 / 9.1.2 busses/strips plug-ins

    Some VST3 plug-ins inserted on x.x.2 busses (5.1.2, 7.0.2, 7.1.2, 9.1.2) where instantiated as Stereo only.
    This was due to the definition of .2 in Ovation being Top Front Left and Top Front Right channels where these plug-ins were expecting Top Side Left and Top Side Right.

    Four new speaker layouts have been added to solve the issue: 5.1.2 Side, 7.0.2 Side, 7.1.2 Side and 9.1.2 Side. These layouts should now be used for inserting such plug-ins.

    Former 5.1.2, 7.0.2, 7.1.2, 9.1.2 layouts have been preserved for compatibility and renamed 5.1.2 Front, 7.0.2 Front, 7.1.2 Front, 9.1.2 Front.

    Both are properly supported by the Atmos ADM Export feature and export either Top Front or Top Side depending on the selected type.

    When importing an Atmos ADM, 7.1.2 and 7.0.2 do create a Top Side configuration now.

...

Fixed Bugs in Ovation 10.1 Beta 1

  • OV100-8: Ovation real-time SRC performances
  • OV100-3: Ovation launch and exit improvements
  • PMX140-179: Fixed. Disable Windows Core Parking
  • PMX140-186: Fixed. Dolby Renderer connection with a Connection Offset shifts the objects metadata
  • OV100-9: Fixed. Show logging not reporting some audio files information.
  • PMX150-48: Fixed. VST3 : Check if strip names are correctly passed to the plugin (SSL VST3)
  • PMX140-151: Fixed. Windows Update Warning message on MassCore systems - remove branch readiness

  • PMX140-158: Fixed. Bus Repro fails to work on stop if some strips are soloed during playback
  • PMX140-156: Fixed. Mix Group Solo Safe issues
  • OV100-7: Fixed.  Active Cue Window selection change resets a playing cue
  • PMX140-70: Fixed. Waves VST / VST3 scanning issue 

...

  • PMX140-36: Fixed. Stereo Dual Pan 
  • PMX140-39: TC Generator plugin: mute on stop by default
  • Atmos ADM Import - Fixed import of FFOA at 00:00:00:00
  • Atmos ADM Import - Fixed import of NOT_INDICATED render wrap mode
  • Several Atmos maintenance
  • Mixer Strip panner may display wrong front/rear values (display issue only)

Fixed Bugs in Ovation 10 RC1

...