MediaMatrix 3.3.5 Release Notes (README.RTF)
NOTE: The installer will upgrade previous MWare releases to this version if you have MWare 3.2a or higher installed. Please uninstall any previous MWare 3.0 or 3.1 releases (including "3.2") before you install this release. This is necessary because of various registry settings that have changed as well as the fact that those old versions were not designed to be upgraded. If you uninstall an older MWare version after installing this release, the older uninstaller will remove the double-click action on View (PAV), Device (DVC), MWare Script (MMS) and RAMM Script (RMS) files, so they will not automatically open in their associated program. If you lose your associations, run the GetBack program. This is also recommended to allow version 3.2a's change #1, below....
The following changes have been made since version 3.3.4:
Features Added:
1. Supports New MM-DSP-CNII Card: Support has been added for the new CNII daughtercard for the MM-DSP card. This card has support for more than 4 transmitters and 4 receivers, however, using the card in this way is considered an advanced use. People who are accustomed normal 4 bundle by 4 bundle system design can continue to use the CobraNet Audio Blocks the same way they used to. The card and the devices also support RS-485 Serial Bridging.
2. ControlMatrix Devices Added: A set of devices has been added to the device tree in this release to design view files that are compatible with the ControlMatrix system. A help topic has been added to the help file to help explain the various devices and their function. These devices are required in a view file if it is to be used with a ControlMatrix system.
3. Windows XP Styles Added: We have added the Windows XP visual style manifest to the GUI. This adds the new XP "Luna" interface look to dialog boxes, buttons, tabs, etc. This also applies to XP Themes you select elsewhere in the OS. You must be using XP and have XP Styles turned on to see the difference. This feature adds no other new functionality. It's just Xtra Pretty.
Bugs Fixed:
1. RATC Restart Bug: A bug was fixed that prevented RATC from automatically restarting when certain WinSock errors occurred. A RATC restart is now attempted after any error. The fact that RATC will always restart itself does not mean that the WinSock (TCP/IP driver) errors have ceased, but that RATC can recover from those errors. It should be noted that WinSock errors do not necessarily mean that there is a problem with MWare. In other words, make sure your network is properly configured.
2. Control Grouped String Controls: Fixed a bug where a newly Control Grouped string-type parameter would not synchronize its value with the other members of the Control Group. This is the resolution to 3.3.3.1 #4 below.
3. Windows XP Template Install Error: In the past several versions (since 3.2a - see release notes below), script file templates for .mms and .rms files are installed on the hard drive so that when you right click and select a new MediaMatrix Script or RAMM Script file, a file of that type is created containing the instructions on how to configure the file. This worked in Windows NT and 2000, but has produced an error message on XP machines ("Default ShellNew folder not found"). Neither choice given will solve the problem, but the error doesn't cause any errors to occur in MWare itself. The only manifestation of the error is when you try to create a script file using the Windows Explorer New command. The file is still created, but without the helpful text inside. This error is finally repaired in 3.3.5.
The following changes have been made since version 3.3.3.1:
1. Ramp Device: A condition in the ramp device was corrected that would sometimes cause the device not to reach the target gain.
2. New PA.INI Variables: Added socketRetryCount and socketRetryWait variables to PA.INI's [communications] section. This attempts to fix socket startup problems. Default values are:
socketRetryCount=10
socketRetryWait=30
3. MotoCross: Fixed at bug in the MotoCross that would crash PADPU.
4. Control Grouped String Controls: Controls of string type, when added to a ControlGroup, do not automatically synchronize their value to that of the group. Other types, even those with text displays, do not have this problem. Also, a subsequent value change on the ControlGroup may not be propagated to the other controls if the new value matches that of one or more of the controls in the group.
5. GetBack Program mis-registered RMS File Type: The GetBack program which was introduced with 3.3.3.1 incorrectly registered RMS (RAMM Script Files) to open with PAVCON (MWare GUI) instead of with RAMM. This has been corrected.
6. New kosmos™ device: A new kosmos device has been added which has subwoofer crossover outputs to allow kosmos to more closely match the hardware version. See the updated kosmos topic for more info.
7. README.RTF eliminated: The README.RTF file which contained the information in this help topic has been removed starting with this release. The shortcut in the Start menu will now open the help file to this page.
8. Crossover Outputs Reversed: By popular request, all Crossover devices have been rearranged to match the output node positions, with the particular crossover output. The old way had the “Low” output on the top node and “High” on the bottom output. Now all outputs are reversed, so that “High” is always on the top node and “Low” is always on the bottom node. The actual functionality of the Crossovers has not been affected. Crossovers within existing view files (from older versions of the Device List) are not changed.
Version 3.3.3.1 Release Notes:
1. Mutes in MM-8802 Control Block: The file that was supposed to fix the problem for Version 3.3.3 was accidentally left out of the release, resulting in the problem remaining after upgrading to 3.3.3. We apologize to those of you who upgraded to fix this problem only to have it remain.
2. Get Back MWare Associations: We have added a program to the MWare Start Menu folder to re-claim MWare file associations. Since X-Ware also uses .PAV and .DVC files, these file types can be stolen when X-Ware is installed after MWare. Also the RealNetworks® RealOne™ player steals the .RMS (RAMM Script File) type as their "Secure RealMedia File". The GetBack program will reclaim the .PAV, .DVC, .MMS and .RMS file-types for you. It won't cause those other programs to malfunction. It also works for previous versions if you run it from the MWare program folder.
3. MM NC 4 Removed: Support for the MM NC 4 Noise Cancellation card has been removed from this release, as we have decided not to offer that version of the card. Note that the Noise Cancellation features are also included in the MM AEC 4 (Acoustic Echo Cancellation) card.
4. Wrong Router: The 32x1 device was actually a 32x16 device. This has been fixed.
Version 3.3.3 Release Notes:
1. Mutes in MM-8802 Control Block: Mutes were introduced with MWare 3.3 in the MM-8802 control block. These had always existed, but weren’t shown. The mute button had the effect of bypassing the level control on Line inputs and passing the audio at full gain. This has been fixed, but the controls have been removed (like the old control block).
Version 3.3.2 Release Notes:
1. CobraNet Audio Failure: MWare 3.3.1 failed to pass audio (send or receive) using CobraNet. This has been fixed. Versions prior to 3.3.1 do not have this bug.
Version 3.3.1 Release Notes:
1. PA.INI Settings Lost: Upgrade Installation also upgraded PA.INI file which caused some program settings including auto-loaded view files to be lost. Now the installer leaves the PA.INI file intact if it is found.
2. Legacy BoB Muting: There was a bug where legacy BoBs (MM-8830/ MM-8840/ MM-8848) would not be un-muted during a re-compile. This meant that to regain audio, you had to exit MWare and restart. This is now fixed.
Version 3.3 Release Notes:
1. New Features
added in this version:
Ambient Level Control (full-time ambient/crowd noise sensor)
kosmos (now with trim controls)
Pitch Shift
Reverb
Vocal Eliminator
MotoCross (Automatic Crossfader)
New Functionality for Ramp
device (see #6 and Ramp
Topic)
MM8802 Blocks now support echo and/or noise cancellation cards
(MM AEC 4 / MM NC 4)
Crossfading Router (MotoCross-based Routers)
2. CAB Polling Changes: The CAB polling routines have been changed to reduce the number of broadcast packets on the network when looking for disconnected cabs. Too many broadcast packets can cause audio dropouts on the network. Also, the detection time has been improved for switched networks. However, this may increase the detection time on hub networks.
3. Only auto-close compile dialog box if engine is started: In previous versions of software, if the 'Load and Compile this view file..' option was used, the software always closed the compile results. If for some reason all of the hardware was not detected properly, the user would not get any feedback that audio was not running. The behavior has been changed so that the dialog box is automatically closed only if audio is running.
4. Board detection fix: A bug was fixed where the system would falsely detect a 'singleCheckHealth failure' and mute the audio. This would only happen during the compile process when the sound engine is unmuted.
5. Improved hardware report: The board DSP speed is now printed during a hardware report.
6. Ramp device optional features added: Two command line arguments have been added to the ramp algorithm. The first controls whether or not the current gain is stored in a preset. If it is non-zero, the gain is stored. The second controls whether the gain can be gestured beyond the A or B gain settings. If non-zero, the current gain is restricted between the two values. This is considered "optional" because without adding arguments to the Algorithm String, the Ramp acts like it always has (necessary for backwards compatibility). The Ramp device as placed from the Device menu comes with none of these features enabled. For more specifics on this, see the Ramp help topic.
7. PADPU.EXE deadlock fix: A thread safety violation in PADPU.EXE was fixed that can, with some undetermined probability, cause a deadlock ("hang"), and perhaps other problems such as an "UNKOWN EXCEPTION" being reported, in a running system. The probability of such a hang is greater for those system using external control, PASHA, RAMM or RATC. It is believed that this rarely encountered problem has been in all releases since 3.0.
8. RAMM connection fix: It has been noticed that at some installations, some RAMM clients have been unable to connect to some RAMM servers (MediaMatrix machines) even if the communication timeouts are increased in the RAMM client's PA.INI. We believe this problem is Windows network based and is associated with having the "Client for Microsoft Networks" component enabled for more than one network adapter in the RAMM server machine, and perhaps with other mysterious network scenarios. The RAMM server code has been modified to not excite the problem. The only effect of this is that the software will no longer get and print the host name of the connecting client. The old behavior, which worked in most cases, can be restored with an entry in the RAMM server machine's PA.INI file:
[communications] RASGetHostName=true
9. RATC/RAMM startup fix: Sometimes the RAMM and/or RATC services fail to start due to a Windows socket open failure, perhaps only when there are clients attempting to connect during startup. A remedy for this has been put in the code which will attempts up to 5 retries of the Windows socket open command.
10. PASHA change groups added: A new command has been added to the PASHA serial control protocol to support the polling of a large number of system parameter values with less communications overhead. Please see the new topic dedicated to this feature.
11. "New" Device Folder Moved: Due to continued confusion about what the "New" folder was meant to contain, the contents of the New folder have been relocated to the "Miscellaneous" folder. New meant "Newly Placed [thing]", like a new "Block" or new "Bump Panel." A lot of users thought that "New" meant that it was where we put all the new devices that we released, so the fact that version after version had the same devices in it was apparently disturbing. In upgraded software, the old folder is checked for user-added devices before deletion.
12. "Miscellaneous/Other" Folder moved: The contents of the Other folder are now found directly inside the Miscellaneous folder. This should facilitate finding those devices, since "other" isn't very descriptive.
13. Ability to upgrade MWare in place: This is a biggie. Formerly, you had to uninstal older versions before installing a new version. If you have 3.2a or higher installed, you can now simply update to the latest version by running the same setup executable. It will recognize your existing installation and update the appropriate files. Any files you have added or changed will be preserved
14. Repair Option: There is a new Repair option available. This is a new choice when you invoke the Maintenance Setup from the MWare group in the Start Menu or from the Add/Remove Programs Dialog Box in Control Panel. Repair simply overwrites all files (from the install) with new copies without having to go through a new installation. Use this feature if you make a mistake (like deleting a folder or device driver).
15. Support Information Added to Add/Remove Programs entry: Some basic support information has been added to the Mware entry. When you click on MWare in the Add/Remove Programs Dialog Box, a link called "support information" is provided and brings up a window showing some minor contact information on MediaMatrix, such as our phone number and website. A link is also provided to take you directly to the MWare product update page.
Version 3.2b Release Notes
Release 3.2b only fixes a bug where the estimated DSP usage was changing whether you used hardware or not. The amount shown is and was correct when using hardware, but was incorrect if you had no hardware. Also, this patch installs the NexSys proxy program which was inadvertently omitted from the last few releases. Otherwise the release is exactly the same as 3.2a.
Version 3.2a Release Notes
1. This version of MWare was designed to be upgraded. In the past we have installed MWare in a folder dedicated to the specific version (e.g. “\MediaMatrix 3.2”). From now on, any version, 3.2a or higher, will be installed, by default, into a folder called “MWare” so you won’t have to move all your important view files to a new folder with each new version. This upgrading will occur when you install any future version of MWare over this release, copying only new or updated files into the folder.
2. Most references to the software as “MediaMatrix” have been changed to “MWare,” since MediaMatrix is now the name of a separate division of Peavey Electronics and not just the name of the product line. MWare is the name of the MediaMatrix software for the Mainframe and Miniframe units.
3. The MWare software is now installed, by default, into \Program Files \MediaMatrix\Mware instead of the usual Program Files\Peavey\MediaMatrix. Same reasoning as #1.
4. Changed web under Help | Peavey on the Web link to say “MediaMatrix Home Page” and the URL associated with “Software Updates.”
5. An MWare shortcut icon is now automatically added to the Quick Launch bar, if present. On Windows NT 4.0 systems, you must have installed Internet Explorer 4.0x with the Desktop Update to get the Quick Launch bar.
6. Folder icons and IconTips have been added for most folders installed for the MWare software.
7. Right-clicking MMS and RMS files now offers the “Edit with Notepad” option on the shortcut menu for modifying script file contents.
8. MMS and RMS Script files have been added to the New list that appears when you right-click an open area in Windows Explorer and the Desktop (Shortcut Menu). These will create new files which are “templates” for creating your own script files. These script templates are based on the help topic for “MediaMatrix Script Files.” Delete the instructions and save the script file, when complete.
9. Wave File Player devices were inadvertently omitted from the 3.2 release’s device menu. These have been restored.
10. Ignore case of hardware address in Tools | Options | Sound Engine.
11. Parametric equalizer’s maximum bandwidth has been increased from 2 to 3 octaves.
12. Peek uptime periodically to check for card crashes when CobraNet devices are not placed within View file.
13. MediaMatrix waits two seconds for CobraNet cards to boot up.
14. Fixed a bug where presets created off-line would cause gain to ramp instantaneously.
15. Fixed a bug that caused some subchannel settings to reset to 0 on recompile after turning off CAB indicators.
Version 3.2 Release Notes
1. The Feedback Ferret™ acoustic feedback eliminator makes its official debut in MediaMatrix MWare. (Found in “Filter”)
2. The Kosmos™ Sub-Harmonic Generator has been added as a device. This patented functionality is also available as a stand-alone analog 1 RU box from Peavey. (Found in “Dynamics”)
3. The Terminal Logger device was added to copy custom text to the Terminal Window in response to user-specified events.
4. Added a bump up/down control to the Level algorithm. This functionality replaces the “Push Button Level” that was in previous releases for serial or CV control of a level in discrete steps.
5. Added Crest NexSys™ plug-in and devices to device menu. To use MWare with NexSys, you must also have the NexSys software installed and running. This eliminates the need for a separate install to get the proper NexSys devices and plug-in installed with MediaMatrix MWare. Contact Crest Audio for support of NexSys devices and/or functionality.
6. Significant re-write and re-organization of the MWare help-file (including this page).
7. Improved the detection of CobraNet Daughter card crashes.
8. Fixed a bug where the compiler would randomly choose between 64 and 80 Mhz boards which could cause incorrect board usage results.
9. Fixed a bug in the the Control Logic Scripter that caused random behavior on scripts that use IPCUR without a cbin wired.
10. Fixed a bug in reading WAV files with extended header info.
11. Fixed a bug that caused (for instance) 0.04 and 40m to not be interpreted as the same floating point number.
12. Algorithm MIX5X1 now uses regular N-input mixer DSP implementation instead of optimized one which caused clicks in the audio.
13. Fixed a bug in the gain display of the Panner when panned hard.
14. Fixed a bug that unnecessarily limited the allowed control types wired to the Ramp algorithms control input.
15. Changed the 'Loser' user type to 'Other' for sensitive types.
Version 3.1.2a Release Notes
The following bug fix was made since version 3.1.2:
1. Fixed a bug where the new 80MHz Miniframe DPU boards were not recognized.
Version 3.1.2 Release Notes
The following changes were made since version 3.1.1:
1. Fixed a bug that caused it to take NP time to complete if more than a few string parameters were ControlGrouped and a change was made to one of them.
2. Fixed handle leak in socket connections (affects RATC and RAMM).
3. Too-long strings were not being terminated properly.
4. Too-long numbers were generating unknown exceptions. They are now caught with "CANNOT PARSE" error message in algorithm.
5. Now disables SSI transmitter when SSI receiver stalls (this prevents brick tones if one of BOB cables is disconnected).
6. CAB CV input calibration values were being reset on recompile.
7. The dynavar device was not poking values after a recompile (used in implemented CAB serial bridging).
8. Added support for MM 8802 mic preamp cards.
9 Support for ver 2.1 (80 MHz) boards.
10 Improved error reporting in compiler (sound engine not starting)
11 Added PageMatrix II Devices and related topics to the compiled Help File.
12 Rearranged Mixer and Router Devices; Filters are now a separate category from Equalizers.
Version 3.1.1 Release Notes
The following changes were made since version 3.1:
1. The Frequency Response signal tracing has been optimized, speeding up the tracing of complex view files.
2. Corrections to the HTML help system.
Version 3.1 Release Notes
The following changes were made since version 3.03:
1. The CAB ID is now a control. Previously, the CAB ID needed to be assigned in edit mode before compiling. Now that the ID is now a standard control, it can be changed at runtime in control mode. There is also a new indicator light which will light only if the new ID is ‘valid’. An ID is valid only if it is non-zero and unique. This new functionality required fundamental changes in the way the software works, so the following devices will need to be replaced for the view file to compile : CAB devices, BoB Monitor devices, and CobraNet Daughtercard devices. In the case of the BoB Monitor and CobraNet devices, only the actual monitor device needs to be replaced, and not the I/O blocks.
2. The software now supports the CAB16i, CAB16o, and the CAB16d.
3. New devices include gain sharing AutoMixers, ramping routers, DTMF decoders, and control delay. Please see the help file for information regarding these new devices.
4. A ‘bit transparency’ option has been added. When enabled, this disables the input highpass filters as well as the 2 bit shift on the inputs and outputs. To enable this option set ‘BitTransparent=1’ in the [PADPU] section of the pa.ini. NOTE: if this option is enabled, meters, threshold settings on dynamics will be off by 12dB.
MWare Installation Improvements:
1. The MWare setup program now detects whether you are logged into Windows NT or 2000 with administrator privileges and will abort the install with a descriptive dialog box, if you aren’t. This will help explain and avoid the eventual error that you would have received if you tried to install MWare without the administrator level access to the NT registry. Windows 95 OSR2 and 98 are not affected by this problem or solution.
2. The setup also checks to see if the necessary HTML drivers have been loaded in order to view the Compiled HTML help file. If the correct OCX driver is not found, the driver is automatically installed. This eliminates the need for the “htmlhelp” folder, so it is no longer copied to the MWare program folder.
3. A dialog box will pop up asking whether or not you have DPU hardware installed. Based on this answer, the pa.ini file will have the base address field set to 0 (no hardware) or D8000 (with hardware).
Version 3.03 Release Notes
The following changes were made since version 3.02:
1. MediaMatrix now included a gain sharing auto mixer. A gain sharing auto mixer distributes the available gain to the inputs on a dynamic basis. Unlike others of this type, it can tell the difference between a speech source picked up by two microphones, and random background noise. It is possible to link the new auto mixers using the RoomLink and ‘Gain Sharing Auto Mixer Linker’ devices in the same manner as old style Auto Mixers.
2. A bug which caused a compile failure when compiling a view file with ‘Load Default Preset’ enabled without having a default preset has been fixed.
3. The 10 machine limitation on RAMM autoconnects has been removed. RAMM now supports an unlimited number of autoconnects.
4. A bug which caused the limiters to default to -6dB has been fixed.
Version 3.02 Release Notes
The following changes were made since version 3.01:
1. A bug causing audio ‘pops’ immediately following a compile has been fixed.
2. The SubPreset Scheduler now works properly. In previous versions of the software would report “file data corrupt” in the terminal window and “*FILE ERROR*” to display in the SubPreset Runner.
3. The PASHA.INI import now pads the UIDs with zeros so they are 3 characters long. For example, a UID of 4 in the PASHA.INI will import to a control group of ‘004’.
Version 3.01 Release Notes
The following changes were made since version 3.0:
1. A bug that caused CAB communication to fail after about 9 days has been fixed.
2. A change has been made to improve the BoB and CAB polling performance.
3. When typing in a control value that is out of range, the value is ignored rather than clamped to the nearest legal value. This is to offer some protection in situations where the user forgets the minus sign when entering a level. For example, if a user intends to type a value of -20dB into a level control with a range of -100 to +12dB, but accidentally omits the minus sign, the control will remain in its current position rather than change to the maximum allowable value of +12dB.
4. MediaMatrix is now better behaved when running as a service. Please see Appendix A at the end of this document for more information.
Version 3.0 Release Notes
1. Thanks for looking at the release notes. Most people don’t even bother, but there is actually information here and you will be glad you did.
2. To find out about all the new feature of MediaMatrix 3.0, check out the help file in the ‘Whats new’ section.
3. To use either the help file or the context sensitive help, HTMLHelp is required. If a help window does not appear when Help|Contents is chosen from the menu, HTMLHelp is probably not installed on your machine. Run hhupd.exe in the “htmlhelp” directory. This will install HTMLHelp 1.2 on the machine.
4. Context sensitive help has been added to the dialog boxes. Click on the ? button and click on a control. If a pop-up message is not displayed, please see #3.
5. You must have Windows NT Administrator privileges when you run the software the first time. This installs the pamem.sys device driver in the registry so subsequent users are not required to have Administrator privilege.
6. New graphics elements have been added to the software. A ‘Rounded Rectangle’ style is available as a block style. This new style is appropriate for blocks that are used as buttons to access control panels - plus they look cool. Also, wire nodes are now paintable - the color is reflected on both the external and internal nodes of the block.
7. File|Decompile has been added. This stops the sound engine. Previously this was commonly achieved by File|New and then File|Compile. This can also be done from the command line ( CLAMM ) using the /decompile switch.
8. The WebStatus service has been added. This allows for monitoring of system health via a web browser. To add the service, use the Tools|Options|Remote Services Page. This is a technology demonstration, and is subject to change.
9. Ctrl+N is the keyboard accelerator for the Next Window command in the child window system menu. It allows you to cycle through the open child windows of the currently focused view window.
10. The Enter key can now be used to open or close the selected block. This, in conjunction with the Next Window accelerator (mentioned previously) and the arrow keys allows complete navigation through a view file without a mouse.
11. The copy command in the Terminal window brings up a dialog asking how much of the buffer you want to copy. The choices are the entire buffer, the last line or the last N lines. You may also select to include the timestamp in the text that is copied to the clipboard.
12. If Control Grouping and Presets are used together, it is possible to get a ‘Mismatched Preset’ message. Just resave the preset and all will be ok.