Versions Compared

Key

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







Note
titlePyramix v14 Keys

Important:
Pyramix 14 requires Pyramix v14 keys.
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

...

    • Refer to the Pyramix 14 Installation Guide for installation procedure and details on the specific BIOS settings and system configuration.
    • Pyramix runs the same MassCore RTX64 v3.7.4.5222 as Pyramix 25th Anniversary HotFix 3 and 4.
    • MassCore is currently not compatible with Windows 11.
    • It is necessary to remove the previous Pyramix version, if there is one, from the Windows Programs and Features, and then reboot your system before installing Pyramix. Take note that when selecting uninstall MassCore you will need to reboot your system as the uninstallation is completed during the system reboot
      Unless you are planning to update your Windows 10 it is recommended to first remove MassCore before performing the update. In such case follow the procedure document
      https://confluencemerging.mergingatlassian.comnet/wiki/display/PUBLICDOC/Windows+Configuration+Guide
    • After installing Pyramix 14 MassCore users might need to uninstall their previous MassCore from the MT Security setting, MassCore Tab, depending on the previous Pyramix 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 Pyramix system never had a MassCore version before, users will have to install the new MassCore version from the MT Security Settings > MassCore tab.
      A valid MassCore RTX64 -3.0 key is no longer needed as of Pyramix 25th HotFix 3.

...

  • Known limitation: Only 48kHz Dolby Atmos Masters are supported for now as export. If the source project is set at a different sampling rate then the Mixdown process will convert automatically to 48kHz using the highest quality settings of the Hepta sampling rate converter.
  • Terminology mismatch: Pyramix Divergence is equivalent to Dolby Atmos Size and imported and exported as such.



Improvements

  • Hotfix 3: Intel 11th gen CPU support.
  • Hotfix 2: Pyramix and Ovation Native compatible with Windows 11 .  Pyramix and Ovation Native-ASIO versions are now compatible with Windows 11, along with the Merging Audio Device driver v2.2. 
    For third party ASIO hardware compatibility with Windows 11, please consult the manufacturer documentation.
    MassCore version is currently not compatible with Windows 11.
  • Hotfix 2 : Dolby Atmos Master Configuration - Assignment : Routing Safe - Prevents the Update Dolby Atmos Renderer button automatic routing mechanism to modify the output routing of the specified channels.
    This can be useful when using additional Monitoring busses, LTC send, ...
    Note : the previous  Number of bus channels connected to the Dolby Atmos Renderer Input setting has been removed.
  • Hotfix 2 : Dolby Atmos Master Export - Force Start Time at 01:00:00:00 - Sets the start time of the exported Dolby ADM Master file(s) to 01:00:00:00.
  • Hotfix 2 : Aux Groups routing to Object Busses - Aux Groups can now be routed to Object Busses.  
    Note: As for Multichannel strips, Aux Groups have to be connected to object busses by following the strip channel count granularity, i.e. stereo strips should be patched in the object router to 1/2, or 3/4, or 5/6, etc… 5.1 strips should be patched to 1/2/3/4/5/6 or 7/8/9/10/11/12, etc.
  • Hotfix 1 : Atmos ADM Import - Option for adding CD Markers

  • Hotfix 1 : Dolby Atmos Connect Advanced menu
    Image Modified
    Image Modified

    • Status and log of the current connection
    • Server - Custom Server option, allowing the user to manually enter the IP address of the computer hosting the Dolby Atmos Renderer.
    • Update Dolby Atmos Renderer button
  • Hotfix 1 : Dolby Atmos Connect - Update Dolby Atmos Renderer
    When Pyramix is connected to a Dolby Atmos Renderer, the Update Dolby Atmos Renderer is now also available on the mixer top right button.
    Image Modified
  • Dolby Atmos Connect feature updated: Revamped dialog, and now able to transmit Mapping, Description, Group, Binaural render mode, Downmix and Trim Controls, as well as the Mixer Bus output routing.
    Dolby Atmos Renderer 3.7 (or above) required.
    A new Dolby Atmos button has been added on the mixer top row. 
    By clicking on it, any Dolby Atmos Renderer present on the network or on the computer will be detected.
    Simply select the detected device to connect it.  The Dolby Atmos button will then turn green.
    To disconnect, click on the green Dolby Atmos button and unselect the detected device.

    To send the Dolby Atmos Configuration to the Renderer, please now go in Project > Edit Dolby Atmos Master Configuration and click on Update Dolby Atmos Renderer.
  • Busses with Auro 3D layouts: Mappable to Atmos in the Edit Dolby Atmos Master Configuration and Export Dolby Atmos ADM Master.
  • 3D Panner updated: New Dolby Atmos Zones, Elevation and Snap features, to accommodate Dolby Atmos workflow.
    3D Panning mode enabled by default in new projects.
  • VS3 Generator plugin - LTC Generator: Timecode generator option available in the VS3 Generator plugin, allowing to output LTC on an audio track.
    Note: Since Pyramix 14 / Ovation 10 Hotfix 1, the Mute on Stop option is enabled by default.

    Current Limitations :
    In Background recorders, will generate an internal timer TC
    Reverse Playback not supported.

...

  • 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 Dolby Atmos maintenance
  • Mixer Strip panner may display wrong front/rear values (display issue only)
  • PMX140-38: Fixed. Mixdown between marks.

...

  • Pyramix 14 Beta 1 runs on Pyramix 25th keys during the beta cycle.
  • Windows 10 2004, 20H2, 21H1, 21H2 are compatible with MassCore/RTX64 -3.7.4, Pyramix 14 Beta 1
  • WARNING: Pyramix 25th Anniversary is supported on 4th Generation Intel Core Processors (4XXXK and higher) and will not launch on previous Processors generation
    Recommended specification: 
    https://merging.atlassian.net/wiki/spaces/PUBLICDOC/pages/4817980/Computer+Specifications.
  • Custom installation is known to potentially have issues at installation. We recommend that you install the recommended full Pyramix.
  • Pyramix 14 Projects are not backward compatible with Pyramix 25th Anniversary, users must perform a “Save Special as v13.0 / 25th Anniversary” in order to open such project in 25th Anniversary.
  • Pyramix projects with v10/v11/v12/25th/14 Bus layout/Structure cannot be saved within a Save Special v9.0 project. A warning message will prevent you from doing so.
  • All of the Mixer Amibsonic components cannot be saved within a Save Special v11.1 project and prior, as Ambisonic was not supported at that time.
  • Ambisonic decoders only decode to Virtual Rooms with standard channel types and positions. If a custom room is needed, then they need to first decode to a standard bus, having speakers as close as possible to the custom room, then send that bus into the custom bus through a GPS strip
  • Saved projects with some tracks unmuted (so that audio plays) will open with all tracks Muted.
    You are most probably using a Source/Destination project or Template Pyramix where all Track Groups are set to Auto-Solo, Auto-Mute or both by default.
    With both settings enabled at project loading time no track is selected by default and all track groups are then muted.
  • Legacy Bus conversions to New General Bus. Due to the architecture of the new busses, mono mix busses are now converted to Mono Aux busses and not anymore to Mono Mix busses. Refer to the Pyramix User manual for more details.
  • The listing of the Pyramix supported remote controllers is available here
  • Mixdown SRC: The SRC option in the Mixdown is shared with the Media Manager Sampling Rate Conversion tool. Be warned that following a Mixdown that is applying a SRC if you then use the Media Manager Sampling Rate Conversion tool and change the SRC parameters, then those values will also be changed in the Mixdown Dialog Box SRC section.
  • Pyramix Video in timeline: if the Video file is shown as offline at project opening, please refresh your media manager to regenerate the Quickmount
  • Pyramix Video in timeline: Opening a project referring to multiple video files or edits can take some time (will indicate finishing for a minute or so), be patient.
  • Merging does not recommend users that edit while recording do so with timeline media clips that are not at the same sampling rate as the project. This is because a realtime SRC will have be processed could cause potential performance problems.
  • Waves plugins users running with a NVidia graphic card should make sure that they have the Threaded Optimization OFF, if set to ON it may cause issue with Waves VST plugins.
    Refer to link here: https://merging.atlassian.net/wiki/display/PUBLICDOC/Graphic+cards+recommended+settings
  • Merging does not recommend to use Disk models: Green, Eco series and Seagate.
  • Merging recommends that users with External USB disks to have those configured using the “Better Performance” option under Windows disk properties, profiling tab. Refer to the Merging system configuration guide for more details.
    http://www.merging.com/support/system-configurations
  • MassCore: Core indicator will show a peak/overload after a save on large project or when rebuilding the Mixer (project open-close). Simply reset the core indicator by clicking on it.
  • VS3 Algorithmix DeNoiser & DeScratcher are supported but will not be maintained anymore
    Known issue: They might display “Demo” (while fully functional) until the first project is saved, closed & re-opened.
  • Warning message “Not Enough Streams available”: This happens when reaching the maximum number of record inputs. In such case we recommend that you reduce your input number count or disable any Background Recorders that are consuming inputs.
    Known issue: If afterwards, you get a constant Message Box showing “Re-activating Project” at each Playback start, close and re-open your project to correct this.
  • Pyramix v8.1, Pyramix v9.0, Pyramix v10, Pyramix v11, Pyramix v12 and Pyramix 25th Anniversary Library formats are compatible between such versions but not with the previous Pyramix Releases. In order to open these libraries in an older Pyramix version please make sure that you use the proper Save library option. A “Save as Version 7.X” was added to the list
  • Final Check Metering is not supported in DXD/DSD mode
  • DiscWrite known issues”: https://merging.atlassian.net/wiki/display/PUBLICDOC/Disc+Write
  • The ADR Keyboard users: Windows 10 October 2018 Update (1809) and higher requires ChangeMe version 5.25.8.  Previous versions will not work along those Win10 updates. Follow the installation instruction on our knowledge base to update :
    https://merging.atlassian.net/wiki/display/PUBLICDOC/Pyramix+ADR+and+Ovation+keyboard+install+guide
  • Safety Record issue with the take logger: Pressed commands will be applied incorrectly when the transport is stopped. This means that if you press Abort & Delete while in Safety Record, nothing will happen. However, when you come out of Safety Record and Stop, it will apply the command, and delete the take. Handle with care.
  • Multiple projects opened simultaneously: We do not recommend users to having more than 8 Projects open at the same time (due to GDI object limitation).
  • Cedar users should install the latest certified version for Pyramix 64bit
    https://merging.atlassian.net/wiki/display/PUBLICDOC/Cedar+Renderer
    The Render Tool will create a temp file for the CEDAR and Nova v0.99 at the root of the C:\
    Be aware that Merging cannot change the Temp file path of such a third party Renderer.
  • Interchange: A non-embedded AAF export to Pro Tools 7x could generate “Could not complete your request because an unexpected error happened while trying to find an audio media file’s format” error message. We recommend the use of AAF Embedded when exporting to ProTools 7. ProTools 8 known to be working properly in this case.
  • Media Recoverer and DSDIFF Recoverer, those utilities should allow you to repair a corrupted file
    https://merging.atlassian.net/wiki/display/PUBLICDOC/Media+Recoverer

...