Installation

...

WARNING: Pyramix 14 running MassCore mode is not supported and certified under Windows 11
WARNING: Pyramix 14 is no longer supported on Windows 7.
WARNING: Pyramix 14 is supported on 4th Generation Intel Core Processors (4XXXK and higher) and will not launch on previous Processors generation
Recommended specifications https://confluencemerging.mergingatlassian.comnet/wiki/pages/viewpage.action?pageId=246088534817980

Pyramix 14 installation notes

• • Pyramix 14 runs on the new Pyramix 14 keys as of the Release Candidate. 
  • Pyramix 14 runs on the same MassCore as the 25^th Anniversary HotFix 3, RTX64 v3.7.4.5222
  • The Pyramix 14 installer comes only as a 64bit version (64bit OS)
  • Pyramix 14 users must refer to the Pyramix 14 Installation Guide for details 
  • Before you perform a Windows 10 update on a system already running a MassCore version it will be 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  https://confluencemerging.mergingatlassian.comnet/wiki/pages/viewpage.action?pageId=682885914819590
    Users that apply Windows updates must refer to the Merging Compatible Windows updates here  Once you have updated your Windows 10, follow the Pyramix and MassCore installation.
    Note #3
    Pyramix 14 running MassCore mode is not supported and certified under Windows 11.
    

• • 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 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. https://confluencemerging.mergingatlassian.comnet/wiki/display/PUBLICDOC/VB+Plugins+%28VS3%29+standalone+installer

Native Installation Notes

...

• • 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 25^th 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/pages/viewpage.action?pageId=600310284819058
  • 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 25^th HotFix 3.

...

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.

...

• • For users with Pyramix and VCube installed on the same system, it is mandatory that you upgrade to VCube 10 to run alongside Pyramix
  • A MTCleanUp utility is available through Merging’s Support for those having install issues
    Please refer to the Knowledge Base https://confluencemerging.mergingatlassian.comnet/wiki/display/PUBLICDOC/MT+Cleanup

Pyramix 14 Release Notes

New with Pyramix 14

...

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

...

• PMX125-36: Fixed. Source/Destination opens 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

...

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

...

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 https://confluencemerging.mergingatlassian.comnet/wiki/display/DSI/MAD+Docs

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

...

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://confluencemerging.mergingatlassian.comnet/wiki/display/PUBLICDOC/Bcom+plugins

RAVENNA Technical Notes

• Windows 10 (64bit) is supported by Pyramix 14 MassCore RAVENNA and Native
• Windows 11 (64bit) is supported by Pyramix 14 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 new Network Switches for use with Horus/Hapi – Ravenna users will find all details along with the configuration guide here:
  https://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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 yourAntivirus and Merging Technologies Softwares or turn it off
  • Configure your Windows Firewall Windows Firewall Troubleshootingor 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://confluencemerging.mergingatlassian.comnet/wiki/display/PUBLICDOC/Native+recommendations

V14 Known issues

• 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
  https://confluencemerging.mergingatlassian.comnet/wiki/pages/viewpage.action?pageId=417136694818591
• 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://confluencemerging.mergingatlassian.comnet/wiki/pages/viewpage.action?pageId=246088534817980
• 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 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://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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://confluencemerging.mergingatlassian.comnet/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.

...