Skip to main content
Skip table of contents

Ugly fonts on Windows Server 2003 R2 / 2008 since KB3013455

After installing the current patches from March 2015 applications like DigAlign or SAF 2.0 Administrator starting displaying their fonts rather ugly. It is hard to read the log output and in case of troubleshooting it could be difficult working with those displayed information.
The reason for this behaviour is based in a Microsoft patch which comes with Windows updates (KB3013455). It seems to have a problem with rendering the font 'Courier New' which is used by many applications.
Microsoft has confirmed this issue and offers a patch for different OS which won't be delivered by Windows Update. This patch must be downloaded and installed manually. Afterwards a reboot is required.

Link to patch KB3037639:

Variations of MultiRec

History of MultiRec development:

At the beginning there were three OCX files for different types of audio boards.

- Rec_MM.ocx
- Rec_NP.ocx
- Rec_X.ocx

Additional there were three DLLs for the audio editors v3:

- V_DLL_MM_3.dll
- V_DLL_NPL_3.dll
- V_DLL_PCX_3.dll

You needed to decide which DLL and OCX should be installed for Multimedia soundcards or Digigram soundcards based on old or NP drivers.
To get rid of this the MultiRec was developed. The first implementation was MultiRec.ocx which was supported by several modules like DBM v2, DigaBurn, MultiCoder v2, etc.
The successor of MultiRec.ox was MultiRec_2.ocx. This was usable in all audio editors V4. Additional DBM v3 and other applications supported MultiRec_2.ocx. MultiRec_2.ocx works with WDM, MME and Digigram NP drivers.
The second generation of video editors like DigaCut ST and MT are based on MultiRec_3.ocx. This version of MultiRec was designed to support SD video formats.
When DigaClipPlayer V2 was developed to support HD video playout via SDI a MultiRec_3_1.ocx was developed which is currently limited to this application.
MultiRec 3.0 and 3.1 both require additional codecs which must be present in a folder on the local harddisk. The video editors and DigaClipPlayer can point to this path using the parameter MultiRecMainConceptPath
With Release 2011.2 DBM V4 was improved to support ASIO by using an updated MultiRec_2.ocx. With this combination you are able to select not only a ASIO device but also its input and output device.
Additional the audio editors V5 were extended to also support ASIO which is required and recommend when using Windows 7 with special soundcards.
To remove the dependency between MultiRec_2.ocx and audio editors a MultiTrackEngine.ocx was created which is exclusively used by newer versions of audio editors V5. This is still under development and should be available in 2012.
For using MultiCoder on Windows 7 and 2008 a renew of the application was done. To support ASIO drivers of soundcards a new version of MultiRec needed to be developed. Therefore MultiCoder V3 of Release 2011.2 needs to be run with MultiRec_3_2.ocx.
Currently MultiRec 3.1 is only used by DigaClipPlayer while MultiRec 3.2 is only used by MultiCoder. At the moment it is not possible and not recommended to run both applications on the same PC. One reason is that both OCX files use the same GUID. This should be no problem because both applications are used for completely different workflows.

Usage of new versions of OCX files always requires to register such file. Under Windows 7 this can only be done by e.g. running a CMD as administrator.

Obsolete OCX files can be unregistered by RegSvr32.exe /u and deleted from the workstations.

Here is an overview of all MultiRec variations (March 2015):

MultiRec.ocx - First implementation of MultiRec (obsolete)
MultiRec_2.ocx - Audio Engine for DBM, DigAIRange and others
MultiRec_3.ocx - (obsolete)
MultiRec_3_1.ocx - Audio Engine for DigaClipPlayer v2
MultiRec_3_2.ocx - Audio Engine for MultiCoder v3 (Patch available with new UID which differs from MultiRec_3_1.ocx)
MultiRec_3_3.ocx - Audio Engine for MTE 6.0 (obsolete)
MultiRec_4.ocx - Audio Engine for MTE 6.x
MultiTrackEngine.ocx - Audio Engine for MTE 5.5 (obsolete)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.