Myriad Logging Recorder v5.0 - Software Update Information

v5.6.17293

The following issues have been fixed:

Fixed a problem whereby the Recorder Instance would log hardware event start and end times with the local system time, not the timestamp of the event from the Broadcast Radio Hardware Service, which would sometimes result in overlapping events. NB.  This fix requires upgrading the Hardware Service to version 5.0.17293.

The VU meters would sometimes not display any levels.  Their display has been improved.

The following changes have been made:

The versioning format of Myriad Logging applications has changed to the format above.

Catalogue Editor

The application can now be closed with File::Exit.

The default location in the open or save catalogue file dialog is now the location of the open catalogue if there is one open.

Monitor

The default location in the open catalogue file dialog is now the location of the open catalogue if there is one open.

v5.0.6.2

The following issues have been fixed:

Fixed a problem whereby the Recorder Service would consume the CPU on some versions on Windows Server.

Fixed a problem whereby the audio VU meters would not display when the application was launched under a restricted security principal.

Added a tooltip to the left-hand Log list panel for Logs that have longer names.

v5.0.6.0

The following changes have been made:

The default audio format for Preview files has been changed from mp3 to Opus 64kbps stereo.

The Myriad Logging file converter application has been updated to use the latest versions of the Opus codecs.

Throttling has been added to the conversion of audio files to avoid excessive CPU usage, particularly with the MP3 and Opus codecs.

The keyboard shortcut combination of Ctrl + Alt + F7 has been added to stop all running Logs, after asking the user for confirmation.

The following issues have been fixed:

Fixed a problem with transcoding to Opus files from a 44.1KHz Log which would cause stereo channel oscillation in the logged audio.

Email notifications about low disk space etc. were not being sent.

V5.0.5.0

Note that this release of Myriad Logging requires the Microsoft .NET Framework 4.6.1 (not 4.6.2), due to .NET 4.6.2 only being available on some Feature versions of Windows.

The following changes have been made:

• Myriad Logging Recorder now checks if the SQL Server instance chosen is on the local computer.
• The following issues have been fixed: The VU meters would not display any values.
• The default Preview format for a new Log would be displayed in the wrong text format.
• EPG data would be overwritten if there was no Reference specified.
• The correct names of any Hardware devices & lines are displayed if either were changed on the Hardware Server since they were entered into Myriad Logging.
• The Logging Monitor application would crash if there was no catalogue file in the default location.
• A previously entered Hardware Line cannot now be edited if there is a problem connecting to its Hardware Server or the Device/Line is unavailable.
• The list of Hardware Lines on the main log window now shows "(Connect Error)" or "(Device/Line Error)" if there was a problem connecting to the Hardware Line.

V5.0.4.0

Note that this release of Myriad Logging requires the Microsoft .NET Framework 4.6.2.

New features:

• Myriad Logging now supports the Opus audio format for all storage periods including the Preview format, if enabled (Preview is only available in the Pro Edition)
• The Opus format supports 48KHz stereo or mono audio compression, offering better quality and a smaller file size than other compression formats.

The following issues have been fixed:

• The application was looking in the wrong location for this updates file.
• The Log properties window would not update the required disk space when changing any of the formats or storage periods.
• Adding a Hardware Line to a new Log would cause Logging Recorder to terminate.
• The Log panel would not include the disk space used by the Preview audio format (if enabled) on the Disk Space Needed text.
• The Log Monitor application now no longer saves its window position.

V5.0.3

Note that you must update Broadcast Radio Hardware Service to v5.0.8 for compatibility with this release of Myriad Logging.

Recorder UI

• Hardware lines can now be disabled to prevent the storing of subsequent line state changes in the database.  Lines can also be prevented from being displayed in Logging Playback.  Lines can also be reordered to change their display order in the Timeline view in Logging Playback.  All of these options can be changed on the Hardware tab of the Log properties window.
• Once a hardware line has been added, it cannot now be changed to a different Line, Device, or Hardware Server.  If state changes are no longer required for a hardware line, it should be disabled or deleted using the options mentioned above.
• Removing of hardware lines from the Log settings now deletes all previous state changes for that line from the Logging database.
• The Log settings window does not now allow adding the same hardware line multiple times.
• The Log hardware panel now shows disabled hardware lines with a grey text colour and with the text "(disabled)" appended to the line name.
• Upon launching the Recorder UI, any hardware lines that went high before the Recorder UI was launched are now shown as being high.
• Fixed a problem whereby hardware lines in the high state would erroneously revert to the low state on the Log display after editing the Log's settings.
• The MessageLog.txt file stored in each hour directory now lists individual events for subscribed hardware lines.
• The share name for a Log can now be edited after a Log has been created.  This creates a new network share with the specified name.  This does not delete any previous share that was created by Logging Recorder..

Recorder Instance

• The Recorder instance does not now subscribe to hardware lines that have been disabled using the aforementioned option.
• The Recorder instance now connects to a Broadcast Radio Hardware Server using the reference of "<computer name> - Myriad Logging (<log name>)" rather than a GUID.

Recorder Service

• The Recorder Service does not now delete rows from the Segment table if there is no audio file, nor delete any audio files if they are not in the database, until after the delete time for the Log.

Logging Monitor

• The Log panels in the Logging Monitor now have a textual description of the Log's state, with a detailed description of any error.  The error is also displayed as a tooltip when the mouse is over this status text.
• The Logging Monitor now automatically detects renames, deletions, changes or creations of previously loaded Catalogue files.

Database Changes

• The following fields have been added:
• HardwareSubs.CaptureEnabled (int, null)
• HardwareSubs.DisplayEnabled (int, null)
• HardwareSubs.DisplayIndex (int, null)

V5.0.2.2

The following issues have been fixed:

• Converted audio files were not inheriting permissions from the destination directory, which could result in an access denied error in Logging Playback if logging to the same drive as the user's temp directory.

V5.0.2.1

The following issues have been fixed:

• Disabling the capture of EPG metadata would not cause the capture to stop.
• Silence detection is now available in the Standard version of Myriad Logging v5.

V5.0.2.0

The following issues have been fixed:

• Editing a hardware line would not display the current Device or Line on the Edit line window.

Other changes:

• The option to create Preview format audio files for each Log has been added.  This feature can be useful when using Myriad Logging Playback over low bandwidth connections.  Note that if this option is enabled, additional disk space will be used to store the Preview audio files.
• When creating a new Log, the properties of the selected audio device were not initially displayed on the Audio Source tab.
• The ability to ingest EPG metadata has been added.

V5.0.1.0

The following issues have been fixed:

• Recorder UI
• Tools::Options: Changing some of the Email preferences would not enable the Apply button.
• Tools::Options: You are now prompted to save any unsaved changes upon clicking the Cancel button.

v5.0.0.0