Skip to content

Using the Windows Runtime Windows::Devices::Midi API from a Win32 application

License

Notifications You must be signed in to change notification settings

fcccode/winrtmidi

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

75 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

WinRTMidi DLL

This project is no longer supported. Please report issues with the Windows::Device::Midi API using the Windows 10 Feedback Hub App

This GitHub WinRTMidi project wraps the Windows Runtime Windows::Devices::Midi API in a Win32 DLL that can be dynamically loaded by a standard Win32 application. If the application is running on a device with Windows 10, the DLL will load and you will be able to use the Windows::Devices::Midi API via a C interface exported by the DLL. If your application is running on devices with Windows 7 or Windows 8/8.1, the winrtmidi DLL will not load. Your application will need to test if it is running on Windows 10 before attempting to load the DLL (See Testing for Windows 10 below). The Windows::Devices::Midi API is ony available on devices running Windows 10.

This DLL is useful for the scenario where you have an existing Win32 MIDI application and want to use the new Windows::Devices::Midi API. If you are not able to update your application to a Windows 10 UWP app, you can use the winrtmidi DLL to access the Windows::Devices::Midi API when your application is running on a device with Windows 10. You can use the winrtmidi DLL with applications built with Visual Studio 2010-2015. There is no need to rebuild your application with Visual Studio 2015 to access the Windows::Devices::Midi API using the winrtmidi DLL.

The recommended steps to use this DLL are as follows:

  1. Ship the winrtmidi DLL with your Win32 application but do not link to the DLL.
  2. When your Win32 application runs, check if your application is running on Windows 10 (See Testing for Windows 10 below).
  3. If your application is running on Windows 10, dynamically load the winrtmidi DLL using LoadLibrary().
    • If your application is not running on Windows 10, continue to use the WinMM MIDI API.
  4. Get pointers to the various winrtmidi functions using GetProcAddress().
  5. Initialize the winrtmidi API using the winrt_initialize_midi() function.
  6. Obtain a MIDI port using the winrt_open_midi_in_port() or winrt_open_midi_out_port() functions.
  7. For more information see example code below.

The WinRTMid DLL enables the following MIDI functionality from the Windows::Devices::Midi API:

  • Enumerate MIDI ports.
  • Notification when MIDI ports are added or removed.
  • Create a MIDI in or out port.
  • Send MIDI messages on a MIDI out port.
  • Receive MIDI messages from a MIDI in port.
  • Destroy a MIDI port.
  • Access Bluetooth MIDI ports
  • Multi-client MIDI port support

Requirements to build the winrtmidi DLL

Visual Studio 2015 (Update 3 recommended) with Universal Windows App Development Tools and Windows 10 Tools and SDKs installed

Adding the winrtmidi DLL to your Win32 Project

Your Win32 application should not statically link to the winrtmidi DLL as it will only load if your application is running on Windows 10. Therefore, you will need to check if your app is running on Windows 10 before attempting to load the winrtmidi DLL. You will ship the winrtmidi DLL and dynamically load it when required by your application.

In order to make it easy to add the winrtdll to your application, we have provided a prebuilt version of the DLL as a NuGet package. The NuGet package is available at: https://www.nuget.org/packages/winrtmidi/ Please note that this is a native nuget package and is not compatible with C# projects. You will need to manually download the dll from nuget using the download instructions below and incorporate it into your C# project (just like any other native c dll). You will then use pinvoke to call its methods.

You can add the winrtmidi NuGet package to your Visual Studio 2010 to 2015 project. Please note that Visual Studio 2010 SP1 is required to correctly support incremental link in debug builds.

Adding the winrtmidi DLL to your Win32 Project Using NuGet

  1. If the NuGet package manager is not installed in your version of Visual Studio, install it using the Tools | Extensions... menu option.

  2. Right-click on your application project and select Manage NuGet Packages from the dropdown menu.

    Manage NuGet Packages

  3. Click on the Browse tab, enter winrtmidi in the search field, enable the Include prerelease option. Click on install.

    Select winrtmidi NuGet Package

  4. Your project is now set up with the include paths to the winrtmidi header files. The winrtmidi dll will also be copied automatically to your .exe's output directory.

  5. In the source file you want to use winrtmidi functions add the following include:

    	#include "WinRTMidi.h"
  6. Look at the MidiClient.cpp example for how to:

    • Load the winrtmidi DLL
    • Get pointers to the winrtmidi functions
    • Initialize the winrtmidi api
    • Enumerate MIDI in and out ports
    • Open MIDI ports
    • Send and receive MIDI messages

Obtaining the Prebuilt winrtmidi DLLs

You can also obtain the prebuilt winrtmidi dlls by directly downloading the winrtmidi NuGet package from nuget.org.

  1. Download the nuget package file. You may need to change the version number in the following URL to get the latest version. http://api.nuget.org/packages/winrt.0.0.1.nupkg

  2. Change the .nupkg extension to .zip

  3. Unzip the file. The winrtmidi DLLs will be in the bin folder of the extracted folder. The winrtmidi header files will be in the Include folder.

#Testing for Windows 10 #

Starting with Windows 8.1, the following Win32 version checking functions will return version 6.2.0.0 for Windows 8.1 and above:

GetVersion() and GetVersionEx() have also been deprecated in Windows 10. In order to correctly obtain the Windows OS version your application is running on, you can do one of the following strategies:

  1. Add an application manifest to your application and use VerifyVersionInfo() to test for Windows 10.
  2. Get the version of kernel32.dll. This method does not require adding an application manifest to ensure correct Windows 8.1/10 version numbers.

If you do not check for Windows 10 and attempt to load the winrtmidi DLL on Windows 7 or 8, your application will quit with the following error:

WinRT DLL Load Error

Method 1: Testing for Windows 10 Using an Application Manifest

  1. Create a file called app.manifest.

  2. Add the following XML to the app.manifest file:

    	<?xml version="1.0" encoding="utf-8" standalone="yes"?>
    	<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
    		<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> 
    			<application> 
    				<!-- Windows 10 --> 
    				<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    				<!-- Windows 8.1 -->
    				<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
    				<!-- Windows Vista -->
    				<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/> 
    				<!-- Windows 7 -->
    				<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
    				<!-- Windows 8 -->
    				<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
    			</application> 
    		</compatibility>
    	</assembly>
  3. Right click on your application project and select Properties.

    Properties

  4. Select the Linker | Manifest Tool | Input and Output option and enter the path to the app.manifest file.

    Application Manifest Path

  5. Use the following function to test for Windows 10 in your application. If the function returns true, it is safe to load the winrtmidi DLL. This method will work with Visual Studio 2010-2015. This method is also provided in WinRTMidi\WindowsVersionHelper.h which you can add to your project.

    	bool windows10orGreaterWithManifest()
    	{
    		OSVERSIONINFOEX  osvi;
    		DWORDLONG dwlConditionMask = 0;
    		int op = VER_GREATER_EQUAL;
    
    		ZeroMemory(&osvi, sizeof(OSVERSIONINFOEX));
    		osvi.dwOSVersionInfoSize = sizeof(OSVERSIONINFOEX);
    		osvi.dwMajorVersion = 10;
    		VER_SET_CONDITION(dwlConditionMask, VER_MAJORVERSION, op);
    
    		BOOL result = VerifyVersionInfo(&osvi, VER_MAJORVERSION ,dwlConditionMask);
    		return result ? true : false;
    	}

Method 2: Testing for Windows 10 using kernel32.dll ##

If you do not want to add an application manifest to your application, you can still test for Windows 10 by checking the version of kernel32.dll installed on the device running your application.

  1. Add the following to the source file you will use to test for Windows 10.

    	#pragma comment(lib, "version.lib") 
  2. Use the following function to test for Windows 10. The function obtains the path to kernel32.dll and checks its version number. This method is also provided in WinRTMidi\WindowsVersionHelper.h which you can add to your project.

    	bool windows10orGreater()
    	{
    		static const wchar_t kernel32[] = L"\\kernel32.dll";
    		wchar_t path[MAX_PATH];
    
    		unsigned int n = GetSystemDirectory(path, MAX_PATH);
    		memcpy_s(path + n, MAX_PATH, kernel32, sizeof(kernel32));
    
    		unsigned int size = GetFileVersionInfoSize(path, NULL);
    		if (size == 0)
    		{
    			return false;
    		}
    
    		std::vector<char> verionInfo;
    		verionInfo.resize(size);
    		BOOL result = GetFileVersionInfo(path, 0, size, verionInfo.data());
    		if (!result || GetLastError() != S_OK)
    		{
    			return false;
    		}
    
    		VS_FIXEDFILEINFO *vinfo;
    		result = VerQueryValue(verionInfo.data(), L"\\", (LPVOID *)&vinfo, &size);
    		if (!result || size < sizeof(VS_FIXEDFILEINFO))
    		{
    			return false;
    		}
    
    		return HIWORD(vinfo->dwProductVersionMS) >= 10;
    	}

About

Using the Windows Runtime Windows::Devices::Midi API from a Win32 application

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C++ 93.2%
  • Batchfile 3.6%
  • C 3.2%