Installation

• Please consult the Installation Guide on https://www.merging.com/support/downloads#pyramix for details on the hardware and software installation procedure and Authorization Key registration process.

  RAVENNA users will have to install the NET-MSC-GBEX1 PCIe Ethernet card provided by Merging Technologies. TURN YOUR COMPUTER OFF (shut down then switch the power off). Next plug the NET-MSC-GBEX1 card into one of the PCI-Express bus slots on your computer and turn the power back on. The NET-MSC-GBEX1 card will only be operational once the MassCore runtime is installed. Refer to the Pyramix Installation Guide for more details.

  • To install the Pyramix Virtual Studio software insert the Pyramix Virtual Studio Installation Media - the installation program should auto-start.
  • To install MassCore launch the MT Security Settings, go to the MassCore page and install the MassCore RunTime (a MassCore base key is required along with MassCore 64bit and a RTX64 4.0 key).. Refer to installation guide for more details.

Updates

Please check our Web site http://www.merging.com periodically for information, patches and updates.

Pyramix 14.1 Installer Information

Pyramix 14.1 is compatible with the following Operating Systems

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

Pyramix 14.1 is supported under the Windows 10 updates - MassCore/RAVENNA, Native & Native/RAVENNA ASIO

• • November 2022 update 22H2 supported since Pyramix 14.0 & RTX64 3.7.4
  • November 2021 update 21H2 supported since Pyramix 14.0 & RTX64 3.7.4
  • May 2021 update 21H1 supported since Pyramix 25th HotFix3 & RTX64 3.7.4
  • October 2020 update 20H2 supported since Pyramix 25^th HotFix3 & RTX64 3.7.4
  • May 2020 Update 2004 supported since Pyramix 25^th HotFix 3 & RTX64 3.7.4
  • Nov 2019 Update (1909) supported since Pyramix 25^th Anniversary & RTX64 3.7
  • May update (1903) supported since Pyramix v12.0.5 HotFix
    If you run a previous Windows 10 version, Merging recommends you update it.

Pyramix 14.1 is supported under the Windows 11 updates - MassCore/RAVENNA, Native & Native/RAVENNA ASIO

• • 22H2 supported since Pyramix 14.1.0 Beta1 : MassCore/RAVENNA, Native & Native/RAVENNA ASIO
  • 21H2 supported since Pyramix 14.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: Pyramix 14.x is supported on 4th Generation Intel Core Processors (4XXXK and higher) and will not launch on previous Processors generation
Recommended specifications Computer Specifications..
WARNING: Pyramix 14.x is no longer supported on Windows 7.

Pyramix 14.1 installation notes

• • Pyramix 14.1 runs on the new Pyramix 14.1 keys as of the Release Candidate.
    
  • Pyramix 14.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 Pyramix 14.1 keys.
  • The Pyramix 14.1 installer comes only as a 64bit version (64bit OS)
  • Pyramix 14.1 users must refer to the Pyramix 14 Installation Guide for details 
  • 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.
    

• • SSK-HUD-RTX is no longer required as of Pyramix 25th Anniversary HotFix 3 and above that includes the MassCore security scheme. The Security now being fully protected by Merging Keys.
  • A Cloud Security (dongle-less) is available since Pyramix 25^th Anniversary
  • Pyramix 14 Projects are not backward compatible with Pyramix 25^th Anniversary, users must perform a “Save Special as v13.0 / 25^th Anniversary” in order to open such project in 25^th Anniversary.
  • The VB Plugins (VS3) are becoming legacy; while it is still possible to use those plugins, there will be no more active development or support. 
    VB Plugins are no longer installed along Pyramix as of the 25th Anniversary version they come with a standalone installer. Download and run the VB Plugin – VS3 installer after having installed Pyramix. VB Plugins (VS3) standalone installer

Native Installation Notes

• • Pyramix 14.1 can be installed on Windows 10 – 64 bit (see Windows 10 version details above) or Windows 11  – 64 bit (see Windows 11 version details above) 
  • It is necessary to remove the previous Pyramix version, if there is one, from the Windows Programs and Features, then reboot your system before installing Pyramix
  • Follow the Pyramix Installation Guide for all details
  • ANEMAN and MTDiscovery installers are not included in the Pyramix Installer.
    Please download and install the latest ANEMAN - MT Discovery in order to manage and monitor your AoIP devices from https://www.merging.com/support/downloads

MassCore Installation Notes

• • Refer to the Pyramix 14.1 Installation Guide for installation procedure and details on the specific BIOS settings and system configuration.

  • Pyramix 14.1 MassCore runs on a new RTX64 4.4 version.  A MassCore Runtime update is mandatory. 
    Please first install Pyramix 14.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 Pyramix in the VS3 Control Panel.

    The RTX64 4.4 requires a new license, only available in Pyramix 14.1 keys.

  • MassCore is compatible with Windows 11 (since Pyramix 14.1 Beta 1)
  • 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
    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 Pyramix 14.1, MassCore users will 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 MassCore Runtime from the MT Security Settings > MassCore tab.
    
    

Warning: Windows 7 is not supported with Pyramix 14.x

Merging Windows 10 Configuration Guide

Windows 10 Configuration
At the Pyramix launch a warning message box will be displayed if your system updates settings are not configured upon Merging’s recommendations.

Merging Windows 11 Configuration Guide

Windows 11 Configuration.
At the Pyramix launch a warning message box will be displayed if your system updates settings are not configured upon Merging’s recommendations.

Additional Notes

• • For users with Pyramix and VCube installed on the same system, it is mandatory that you upgrade to VCube 10.1 to run alongside Pyramix
  • A MTCleanUp utility is available through Merging’s Support for those having install issues
    Please refer to the Knowledge Base MT Cleanup

Pyramix 14.1 Release Notes

New with Pyramix 14.1

Intel 12th / 13th Gen CPU Compatibility - MassCore & Native/ASIO

Pyramix 14.1.0 Beta 1 is now compatible with Intel 12th and 13th gen CPU, in both MassCore and Native/ASIO running modes.

Windows 11 Compatibility - MassCore

Pyramix 14.1.0 Beta 1 is now compatible with Windows 11, in MassCore mode (MassCor Runtime RTX64 4.4 required).

Dolby Atmos Master 96k Import/Export

Note: Dolby Atmos Master Import/Export/Editing requires Pyramix Premium authorization.
Dolby Atmos Renderer v5.0 required

Dolby, Dolby Atmos, and the double-D symbol are registered trademarks of Dolby Laboratories Licensing Corporation.
Confidential unpublished works. Copyright 2021 Dolby Laboratories. All rights reserved.

• Accessible under menu Project > Export Dolby Atmos ADM Master
• This process will produce a Mixdown of the existing Timeline through the existing Mixer and wrap it as a Dolby Atmos ADM Master file.
• If the source project is set at a different sampling rate then the Mixdown process will convert automatically to 48kHz / 96kHz, using the highest quality settings of the Hepta sampling rate converter.
• Channels that do not contain audio will not be exported to the final ADM Master file, however, channel numbering and source indexes will be preserved.
• Known limitations or comments
  Terminology mismatch: Pyramix Divergence is equivalent to Dolby Atmos Size and imported and exported as such.

Sony 360 Speaker layouts

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.

Improvements

• 14.1.0 Beta 1: 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.

• 14.1.0 Beta 1 : 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 Pyramix 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.

• 14.1.0 Beta 1: Dolby Atmos Master Export - Options - Force Main Bed to 7.1.2
  Force Main Bed to 7.1.2 (14.1 Beta 1) - Generates the main bed as 7.1.2 whatever the bus configuration, as requested by Universal Music.
  Note that this does not modify the audio, the additional Bed channels will be empty, and the Top and/or Wide channels will remain as Objects, as in previous Pyramix version.
• 14.1.0 Beta 1: Mixer Dolby Atmos Advanced dialog
  Audio Routing Options:
  • Connect starting with First Audio Output with optional Offset - to route all busses and objects to regular audio outputs. An offset is now offered to allow to keep the first audio outputs channels for other purpose, like monitoring, then use the followings for connecting to the Dolby Atmos Renderer.
  • Connect to MT ASIO Bridge - to route all busses and objects to the MT ASIO Bridge outputs. This is useful for MassCore users willing the run the Dolby Atmos Renderer in the same computer as Pyramix. Dolby Atmos Renderer version 5.0.0 and above is required.
    Native users willing the run the Atmos Renderer in the same computer should preferably use the MAD Bridge.
    
• 14.1.0 Beta 1: 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)
• 14.1.0 Beta 1 : Archiving Metadata
  A set of predefined values can be set in the registry in: HKEY_CURRENT_USER\Software\Merging Technologies\Pyramix\ArchivingMetaData\ PredefinedValues as String entries where the names of the strings are the predefined values for the Value field.
  XTOC metadata can be generated along with the ArchivingMetadata using the following registry key HKEY_CURRENT_USER\Software\Merging Technologies\Pyramix\ArchivingMetaData.  Add a DWORD “Include XTOC” = 1
• 14.1.0 Beta 1 : AAF Import Performance
  
  AAF Import performances improved in case of large existing media manager or libraries
  Global media cache (Media_Library_.pml) is automatically updated when loading Pyramix.
  Existing quick mount libraries (QuickMount7_.pml) in every media folders can be re-created by refreshing the media folders manually. This has however lower impact on the performances than the global media cache mentioned above.

Bug fixes

Fixed Bugs in Pyramix 14.1.2

• New keys required for Pyramix 14.1 / Ovation 10.1  (as of the RC1)
• PMX140-216: Fixed. Recording wave in "Suffix with strip name" and "One file per track" places media incorrectly.

Fixed Bugs in Pyramix 14.1 RC1

• New keys required for Pyramix 14.1 / Ovation 10.1  (as of the RC1)
• Various improvements for Dolby Atmos workflow (DASSIDK storage kit 2.x final certification)

Fixed Bugs in Pyramix 14.1 Beta 2

• PMX140-208: Fixed. Pan Noir: Opening the "source placement" window and makes it larger generates a critical error.
• PMX140-205: Fixed. Improper Argument when VCA in mixer 
• PMX140-170: Fixed. Channel nomenclature renaming.
• PMX140-196: Fixed. Clip recording vanishes when clicking between "auto rec ready" track groups.
• PMX140-204: Fixed. Update Plugins Routing page with new channel types.

Fixed Bugs in Pyramix 14.1 Beta 1

• PMX140-192: Fixed. AAF Import Performance
• PMX140-179: Fixed. Disable Windows Core Parking
• PMX140-190: Fixed. Fade Editor Fade Safe entry in the right-side list control not updated on clip selection change
• PMX140-176: Fixed. Media Mounting/Relinking Performance
• PMX140-185: Fixed. Atmos ADM Export to use current mixer state when no automation data available on a given parameter
• PMX140-186: Fixed. Dolby Renderer connection with a Connection Offset shifts the objects metadata
• PMX140-187: Fixed. Remove automatic opening of .pk Waveform file in Wave Handler
• PMX140-172: Fixed. Atmos static objects not at the correct location after changing assignment.
• PMX140-75: Fixed. MP3 Playback Media Handler.
• 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

• GAIA-959: Fixed. File > Stretch / Pitch without MPEX key - Wrong text in Error message

• PMX140-164: Fixed. Pyramix crash when connected to Atmos Renderer and routing audio on MTASIO Bridge

• PMX140-165: Fixed. Improve project Loading time with Maps as per Saving

• PMX140-166: Fixed. Save time improvement - projects with many clips (50000+)
• PMX140-162: Fixed. Zooming mouse wheel while selecting a Region (or shift - select)
• PMX125-87: Fixed. Mixdown to DSDIFF with TP normalization makes PMX crash
• PMX140-159: Fixed. Drag&Drop bypass Auto-Ripple doesn't work from Media Manager or Libraries
• 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

• PMX 111-289:Fixed. Timeline Paste to original TC not working

• PMX140-133; Fixed. DiscWrite DDP Metadatas missing.

• PMX140-154: Fixed. Atmos ADM Export - Force Main Bed to 7.1.2 - Universal request
• PMX140-108: Fixed. Copy-pasting automation points in auto-ripple crashes Pyramix
• PMX140-70: Fixed. Waves VST / VST3 scanning issue 

Fixed Bugs in Pyramix 14 Hotfix 4

• PMX140-129: Fixed. MackieCTRL surface meters only works for the first channel
• PMX140-128: Fixed. Trying to always update the Dolby Renderer even if not connected on Room SpeakerSet change.

• PMX140-125: Fixed. HUI - MackieCTRL Mute-Solo-Rec not reset on strips not having these controls (bank switch)

• PMX140-124: Fixed. HUI - MackieCTRL - PMX Mixer Mute - Solo - Rec Ready status not always in sync with controller.
• PMX140-114: Fixed. HUI - MackieCTRL The channel strip name and number are not updated during bank/channel switch
• PMX140-87: Fixed. Keyboard shortcut for +/-0,5 clip gain.
• PMX140-107: Fixed. OASIS.dll crash at mixer properties recall

• PMX140-112: Fixed. Strip Tools / Bus Tools : EQ expanded window truncated

• PMX140-119: Fixed. Plugins can mute the sound if changing sampling rate, bypass then mutes the signal.
• PMX140-73: Fixed. Envelope automation 0.1 db Steps
• PMX140-111: Fixed. CD Import Database - replace server address
• PMX111-184: Fixed. Mixer: BusTool and Strip tool incoherency when added or moved in Mixer
• PMX140-103: Fixed. Bypass/OnOff/Automation buttons missing on VST windows
• PMX140-110: Fixed. SACD Disc Builder fails when launched from Pyramix (sacd_verf.dll error)

• PMX140-109: Fixed. Improper argument - retrieving audio peaks (DSD)

• PMX140-106: Fixed. Projects with VSTs on legacy MultiStem bus may crash upon opening
  Note : Adding VSTs on such legacy Multistem bus is no longer allowed.  Previous projects containing such VST - Multistem bus are not modified and will continue to work as is.

• PMX125-51: Fixed. Discwrite MD5 not correct for IDENT.TXT
• PMX140-101: Fixed. Crash when recording in DSDIFF and display waveforms while recording
• PMX125-116: Fixed. Alternate Timecode option in display overlay (Destination Alternate TC)
• PMX150-29: Fixed. Playback improvement (GetMediaDescription)
• PMX140-88: Fixed. BMD Video card format forced by Pyramix's settings when out of clip 
• PMX125-205: Fixed. Mixdown - Bus names not updated after 1st mixdown
  
• PMX125-206: Fixed. Mixdown - options should be turned off during mixdown
• PMX140-15: Fixed. Media Manager Replace selected clips should give a message if not possible

Fixed Bugs in Pyramix 14 Hotfix 3

• MSC-128: Fixed. Intel 11th gen CPU support.
• Fixed. ADM Export and Dolby Renderer panning Balance mode implemented.
• Fixed. Dolby Atmos: Failed to send configuration error.

Fixed Bugs in Pyramix 14 Hotfix 2

• PMX125-36: Fixed. Source/Destination projects open with always Muted groups.
• PMX140-71: Fixed. VST3 Plug-ins state and settings saving/load.
• RAV-1568: Fixed.. TC Interrupt Timer Improvement (Native - ASIO)
• PMX110-67: Fixed. Projects with Tracks in Repro or Auto at opening will be in Input mode for a second.
• HEL-499: Fixed. Automation Preview mode not triggered when entering values manually.
• GAIA-463: Fixed. Automation: Undo not returning to original state (if changing track)
• PMX111-37: Fixed. Automation: Copy/Paste can cause inaccurate results (if first track empty) 
• PMX140-77: Fixed. Delay Compensation issue when changing object routing
• PMX140-74: Fixed. Mixer Effects menu missing bypass and on off at times.
• PMX140-67: Fixed. Dynamic Events Memory issue.
• PMX140-65: Fixed. Atmos Elevation option always on.
• PMX140-64: Fixed. Top Channels not sent properly to Dolby Atmos Renderer if no other object routed
• PMX140-58: Fixed. Exporting Masters with accents in the filename (CD Tracks).
• PMX140-55: Fixed. ADM Export of 5.1.4 busses fails
• PMX140-54: Fixed. ADM Export of Auro 9.1 fails
• Several Dolby Atmos Maintenance and compliance updates.
• PMX140-52: Fixed. Crash when recording and creating a new playlist
• PMX140-44: Fixed.  Video window does not follow Pyramix rewind / fast forward

Fixed Bugs in Pyramix 14 Hotfix 1

• 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.

Fixed Bugs in Pyramix 14

New keys required for Pyramix 14 / Ovation 10  (as of the RC1)

• PMX140-31: Fixed.Some MTFF files can't be mounted
• PMX140-24 :Fixed. CD Index as FFOA not working when exporting One ADM per Track

Fixed Bugs in Pyramix 14 RC2

New keys required for Pyramix 14 / Ovation 10  (as of the RC1)

• PMX140-29 :Fixed. Clips no longer grouped when re-opening project

Fixed Bugs in Pyramix 14 RC1 

New keys required for Pyramix 14 / Ovation 10  (as of the RC1)

• PMX140-27:Fixed. Pyramix 14: Save Special as 25th will Pan all channels to center once open in a Pyramix 25th
• PMX140-19: Fixed. VS3 Control Panel: HiRes Screen resolution prevents the user from selecting Bridge or other items.
• PMX140-25: Fixed. Mixdown crash - changing Record setting

Fixed Bugs in Pyramix 14 Beta3 

Runs on Pyramix 25th / Ovation 9 / VCube 9 keys during the beta cycle.

• PMX140-23: Fixed. ADM Import Create up to xx additional Objects and Strips to accommodate for the following Import 
• PMX140-22: Fixed. Crash Update Renderer when sending more than 128 channels
• PMX125-109: Fixed. TC chase not working when having a video track in the timeline.
• PMX140-16: : Fixed. Poor Video Display Performance
• PMX140-17: Fixed. Cannot assign objects to channels above 64
• PMX140-9: Fixed. Crash when setting CD markers after ADM Import

Fixed Bugs in Pyramix 14 Beta2 

Runs on Pyramix 25th / Ovation 9 / VCube 9 keys during the beta cycle.

• PMX140-11 : Fixed. Mixdown / Export Dolby Atmos ADM window hidden at times

Fixed Bugs in Pyramix 14 Beta1 (inherits of the Hotfix fixes)

Runs on Pyramix 25th / Ovation 9 / VCube 9 keys during the beta cycle.

• REP-349: Fixed. Library and Media Manager: Copy / Paste not possible if Tab is undocked
• REP-44: Fixed. Libraries: dragging composition snapshots can rename them
• GAIA-1282: Fixed. Media Manager copy from Media Browser
• PMX120-29: Fixed. Library: Paste with Media does not create a library pointer

• PMX125-104: Fixed. Muting some clips requires manually forcing redraw when Gray Out Muted Clips is unchecked

• PMX125-179: Fixed. Media Manager columns display lost when performing a refresh folder
• PMX125-185: Fixed. Global library - consolidated media path lost
• PMX125-186: Fixed. DNxHD authorization key not working on PMX
• PMX125-188: Fixed. Pyramix crash when opening project with a VST Design Works EQ6 VST3 with UI left open
• MSC-86: Fixed. VS3 control panel will warn user if a MassCore update needs to be installed.

Additional notes

Pyramix 14.1 Product Changes

• The VB Plugins (VS3) are becoming legacy; while it is still possible to use those plugins, there will be no more active development or support.

Pyramix 14 Product Changes

• Windows 7 no longer supported
• New Save format, added save special as Pyramix 25^th. 
• MT Discovery – No longer bundled with Pyramix / Ovation
  Please download and install MT Discovery from https://www.merging.com/support/downloads#accessory-installers-3

MassCore Technical Notes

• MassCore not supported on Core2Duo. Minimum requirement is a QuadCore. Find system recommendations here: http://www.merging.com/support/pc-config
• Pyramix 14.1 runs on a new MassCore Runtime (RTX64 4.4), requiring a RTX64 4 license (included in V14.1 keys)
• Intel 12th &13th Gen CPU supported since Pyramix 14.1 (RTX64 4.4)
• MassCore is supported under Windows 10 (64bit) and Windows 11 (64bit)
• MassCore Ultra Low latency mode can generate noise if used on some configurations (Turnkey recommended).
  In such cases we recommend instead the use of the AES67 mode or Extra Low latency mode.
• Pyramix Core indicator overloading (red) issue. Recommendation:
  • Under a 64 bit OS: MassCore RTX 64bit users are allowed to run with Hyperthreading enabled. In such case users will by default have 2 Core allocated to MassCore RTX64, as we leave a pair number of Cores for Windows.
    Merging recommends to having an SMP key under such configurations.
  • If, under the Bios power options, you have entries such as the Intel SpeedStep and CPU C State make sure that these options are disabled, as they are potential problems for MassCore. Refer to installation guide or the Windows Configuration guide for all details.
• MassCore & CPU load indicator range (as of Pyramix v10.2 and above)
  • Green from 0% to 74% = Safe mode*
  • Orange from 75% to 84% = Moderate Risk*
  • Red from 85%->100% = High Risk
    *MassCore users will have enhanced Core stability when using recommended dedicated Graphic Cards.
    *Native users: Recent laptop owners are often confronted with performance problems when the CPU load is near the mid-point of load, where random CPU jumps can cause sudden glitches. This has also been seen when benchmarking with Non-Merging Applications on recent laptops.
• When the Core indicator blinks (red), it indicates a drop. Only be concerned if it occurred during Playback/Mix down or Record. To reset the Core drop simply click on the Core indicator. For more information please refer to the appropriate section in the User Manual.
• If you have VST Core peaks under MassCore, users should increase their VST Engine Buffer size value, located under the Pyramix Settings. More information is available in the User Manual.
• External Insert plug-ins: The same input and output cannot be used in the External Insert plug-in and the Mixer at the same time, as they are exclusive to either one.

Plugin Engine Notice

The plugins engine Core distribution is done automatically for optimal performance. The total Core load of the Strips plugins will be processed first, followed by the total Core load of the Bus plugins. The engine is sequentially performing those two processing tasks. Meaning that a high Core load on the Strips plugins side is not summed with a high Core load on the Bus plugins side.
Changing a designated Core load to another one is not possible (unless modifying the Mixer configuration) and in no way would it change the total sum of processing passed to the engine for the chosen plugins.

About the Plugins Distribution Core Reading
We measure the time duration of the plugin itself. Time to process Audio Frame / Duration of the plugin itself * 100 = Load for a single plugin. We then compute the multiple plugins (on a chosen Strip or Bus by example) and we calculate the summation of those.

Do not to confuse with the readings below :
Pyramix CPU reading:
The CPU load displayed in the Pyramix bottom bar is not the CPU usage as computed in Windows task manager. CPU load in Native is computed in this way: (time to process audio frame) / (duration of one frame) * 100. Thus, it is the percentage of time used to process in one audio frame duration; this indicator is more useful than CPU Usage because it takes in account CPU stall during processing time.
In MassCore based systems the CPU: load indicator is supplemented by a VST: Core load indicator in the Title Bar. Refer to the Pyramix User Manual for more details.
Windows Task Manager:
Then windows will on its Task Manager CPU measures the CPU time as a percentage of the CPU's capacity.
So, in the end you just cannot open those 3 Windows and expect to have the same readings.

Merging Audio Device (MAD) 2.0

This ASIO RAVENNA/AES67 device supports Multi ASIO Clients and integrates WDM Support.  With this new Device Driver multiple applications running ASIO can be launched in parallel on a same system, sharing the same sampling rate and at the same time multiple applications running WDM can be launched in parallel and have their own sampling rate automatically converted to the ASIO sampling rate. This allows monitoring the Windows system sound and any application (such as Spotify, YouTube, PC Sounds files,…) along with any ASIO applications.
Refer to the online MAD documentation for all details Merging Audio Device..

• • Two different modes supported
    • Unite Mode (Automatic Simplified connectivity for Anubis Music Mission, Horus and Hapi). Unite does not support the Anubis running the Monitor Mission.
    • RAV/AES67 mode (Pro usage for Anubis, Hapi and Horus)
    • NADAC mode (HiFi usage for NADAC users)
    • MassCore mode
  • Multi-Client ASIO and thus hosts supported  
  • Bridge channels support between ASIO clients
  • WDM Support and second AUX WDM (as of MAD 2.0)
  • Bridge channels support for WDM and Host.
    Note: One sampling rate at a time supported for ASIO (The default host one). WDM supports SRC.

MAD Infrastructure Pack (PSO-MAD-INF) required for:

• • Virtual Machine Support
  • ST2022-7 Support
  • NMOS Support

ANEMAN

Important: The ANEMAN comes as a separate installer.
Please download and install the latest ANEMAN in order to manage and monitor your AoIP devices from https://www.merging.com/products/aneman

Ambisonic

Since Pyramix 12 we include a complete hybrid Channel Based/Ambisonic workflow, allowing for encoding, mixing, rotating and decoding Ambisonic signal directly in the mixing console.

Ambisonic Decoders:

• • Ambisonic Decoders supported up to 7th in v12, and the b<>com Decoders are now integrated within the Pyramix mixer as of Pyramix 12.0 and upwards.

 VR Pack Key option:

• • Ambisonic Strips and Ambisonic Groups of 1st and 2nd order are always decoded even if the VR Pack key is not present
  • Ambisonic Strips and Ambisonic Groups of 3rd to 7th order are properly decoded if the VR Pack key is present
  • Ambisonic Strips and Ambisonic Groups of 3rd to 7th order are decoded using a 2nd order decoder if the VR Pack key is NOT present

To summarize, a user will need the VR Pack key to encode and/or decode HOA, meaning 3rd to 7th order. 1st and 2nd orders are free of charge for both encoding and decoding.
Note: HOA to Binaural is not available into Pyramix but users can run the B<>COM Binaural encoder licence, available in trial. Follow the instruction here for more information https://merging.atlassian.net/wiki/display/PUBLICDOC/Bcom+plugins

RAVENNA Technical Notes

• Windows 10 (64bit) is supported by Pyramix 14.1 MassCore RAVENNA and Native
• Windows 11 (64bit) is supported by Pyramix 14.1 MassCore RAVENNA and Native
• Pyramix 14 system recommendations. Details here: http://www.merging.com/pages/pcconfig
• For ultimate performance we recommend that under ANEMAN you only connect the necessary I/O connections, as every extra RAVENNA connection will use some bandwidth (Core or Network)
• The Network must be Layer 3 compliant and must be a Gigabit network
• Merging has certified Network Switches for use with Merging devices – Ravenna users will find all details along with the configuration guide here:
  https://merging.atlassian.net/wiki/display/PUBLICDOC/Network+Switches+for+RAVENNA+-+AES67
  http://www.merging.com/products/horus/downloads
• RAVENNA users should avoid connecting multiple Horus or Hapi units to any a router/Network not certified by Merging. Refer to the Merging RAVENNA Network Guide for details on the certified RAVENNA switches and their configuration. http://www.merging.com/products/horus/downloads
• Only RAVENNA devices can be connected to the Merging PCIe Ethernet Controller Card NET-MSC-GBEX1. Avoid connecting non-RAVENNA devices to this network, such as Tango/Isis/Euphonix controllers or other network devices.
• Don’t connect a 100MB Ethernet device if the switch is not multicast; otherwise, the flow control will reduce the bandwidth drastically.
• RAVENNA I/O Connections:
  In order to create RAVENNA I/O connections please refer to the ANEMAN User Manual (installed along with Pyramix). ANEMAN Quick Connection Guide here below.
  https://merging.atlassian.net/wiki/display/PUBLICDOC/ANEMAN+-+Quick+Connection+Guide
  Refer to the ANEMAN User Manual for more details.
  Recalling RAVENNA connections for a complete setup.
  Despite not yet having a complete recall of IO Connections it is possible on certain setups to recall the Presets store in the device (Horus, Hapi, Anubis) that holds one end of the RAVENNA connections and at the same time recall the ANEMAN save connections that holds the other connections end.
  Warning: It is strongly advised that before recalling connection that users clear the existing connections.
• Firewall:
  Firewalls can block communication between the computer and the Ravenna devices.
  The Merging installers automatically opens the required communication ports in the Windows Firewall.
  If you don’t use the Windows firewall or if you encounter connection issues, we recommend to disable the Network Firewall.
  Windows Firewall Procedure:
  Go in Windows Control Panel > Windows Firewall.
  Click on “Turn Windows Firewall on or off”
  Go to the Public Network section and select “Turn Off Windows Firewall”
  For other firewalls, please consult the manufacturer documentation.
• Windows UAC:
  User should disabled the Windows User Account Control
  Procedure:
  Go to the Windows Control Panel\All Control Panel Items\User Accounts
  Open the Change User Account Setting
  And set it to “Never Notify”
• Antivirus:
  Some Antivirus such as Avast or Sophos have been known to block the Horus discovery and RAVENNA I/O Connection. Merging also recommends that any Antivirus software is properly configured to not interfere with the DAW. See this page for further details:
  https://merging.atlassian.net/wiki/display/PUBLICDOC/Antivirus+and+Merging+Technologies+Softwares

Pyramix Native Recommendations

• Windows 10 - 64bit & Windows 11 - 64bit supported with Pyramix 14.
• Please refer to our Windows configuration guides to optimize system performance.
• Administrator rights are required to configure VS3 Control Panel and the RAVENNA ASIO panel.
• The Merging RAVENNA ASIO Frame Mode size can be configured to AES67 (6, 12, 48) of RAVENNA mode (64), verify your network and devices configuration.
• The Merging Audio Device driver can be set to buffer size multiples of 48 (AES67) or 64 samples (RAVENNA), adjust the buffer size to your system in order to get the best performance
• Configure your Antivirus and Merging Technologies Softwares or turn it off
  • Configure your Windows Firewall Windows Firewall Troubleshooting or turn it off for Public Networks
  • Put Windows UAC (User Account Control) to the lowest level (disabled).
  • Disable the WIFI (disable the Wireless adaptor not only the WIFI connection)
  • Disable Bluetooth if active (under Windows Device Manager) 
  • Avoid active internet connection while running Pyramix 
  • Avoid connecting audio interfaces to USB or Firewire hubs, plug it directly into your computer.
  • We recommend to activate HyperThreading if allowed by your CPU.
  • Power management features must be configured to get a stable system. 
  • In Windows Control Panel > Power Options, make sure you select the “High Performance” power plan (or "Ultimate Performance" if available).
    Very common that Powerful laptop are at times in energy saving mode, create a High Performance power plan.
  • Avoid using battery power, rather have you power cable connected
  • Make sure all unnecessary programs are closed. They can tie up useful resources.
  • Turn off any software utilities that run in the background, such as Windows Messenger, calendars, and disk maintenance programs.
  • Laptops usually have small graphical resources; Merging recommends you pay extra caution when using the Fixed Cursor option. 
  • Verify the performance of your Native system.
    On Windows 10, and 11, DPC latencies can be monitored with Latency Mon http://www.resplendence.com/download/LatencyMon.exe
• Laptop users should set their ASIO interface to Topmost Priority in VS3 Control Panel.

Refer to the online documentation for more details
https://merging.atlassian.net/wiki/display/PUBLICDOC/Native+recommendations

V14 Known issues

• Pyramix 14.1 runs on the new Pyramix 14.1 keys as of the Release Candidate.

• Windows 10 2004, 20H2, 21H1, 21H2, 22H2 are compatible with MassCore/RTX64 -4.4, Pyramix 14.1 Beta 1
• Windows 11 21H2, 22H2 are compatible with MassCore/RTX64 -4.4, Pyramix 14.1 Beta 1
• WARNING: Pyramix 14.x 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.x Projects are not backward compatible with Pyramix 25^th Anniversary, users must perform a “Save Special as v13.0 / 25^th Anniversary” in order to open such project in 25^th Anniversary.
• Pyramix projects with v10/v11/v12/25^th/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 25^th 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

RAVENNA Known issues

• RAVENNA: Switching from MADI Standard (56) to MADI Extended (64) can generate a small glitch, so please avoid doing so during realtime operations
• Merging recommends the use of ANEMAN in order to manage all RAVENNA I/O connections, please refer to the ANEMAN User Manual installed with Pyramix for more details.
• Non-certified RAVENNA configurations might not be capable of sustaining 384 I/O channels @ 1FS (44.1/48 kHz). If you experience noise similar to static, reduce the RAVENNA I/O channel count enabled in ANEMAN. We also recommend that if you have experience such static noise, do not run MassCore in Ultra Low or Extra Latency mode but rather Low latency mode.
• Peaks might show up under the Pyramix Core section if you power OFF or disconnect the Horus/Hapi. Recommendation: A valid connection to an online Horus is always required if the Horus is PTP Master. Reset peaks by Mouse Clicking on the Core indicator section.
• Avoid changing a network address, or disconnecting Ethernet ports on your system when MassCore RAVENNA is running
• ANEMAN quick connection guide available here
• DSD issues
  • Background Recorders: If the Mixer is not a DSD compatible Mixer (square mixer), the record fails, but no message will be displayed. We recommend that users create a DSD project prior to enabling and starting to work with Background Recorders in DSD.
  • When creating/opening a DSD project the Horus might not switch accordingly between 64/128/256. This has to be done manually.