Library uses obsolete Windows function

In the file: https://github.com/melanchall/drywetmidi/blob/71bc4cabe87e8c69cba90a4f2211753cfe838118/DryWetMidi/Devices/Clock/TickGenerator/MidiTimerWinApi.cs

Library uses obsolete Windows function:

public static extern uint timeSetEvent(uint uDelay, uint uResolution, TimeProc lpTimeProc, IntPtr dwUser, uint fuEvent);

https://docs.microsoft.com/en-us/previous-versions/dd757634(v=vs.85) https://docs.microsoft.com/en-us/windows/win32/multimedia/starting-a-single-timer

It would be recommended to replace method with new equivalent before method get deprecated and removed from future versions of Windows. As Windows 10 is a subject to obligatory auto-update, all Windows 10 users will be affected in the future.

More informations on the available Times in C#: https://docs.microsoft.com/en-us/dotnet/api/system.threading.timer?view=net-5.0#remarks

[operatortwo]

What is Midi-Driver and Midi-Port?

A Midi-Driver is sometimes provided by the manufacturer of a Midi-Hardware for the use of device-specific applications or “to ensure optimal performance”. This drivers are normally downloaded an installed by the user. For example: Yamaha USB-MIDI Driver V3.1.4 for Win 10/8.1/8/7 (64-bit) M-Audio MIDISPORT Windows Driver v6.1.3 (for MIDISPORT 4x4 and MIDISPORT 4x4 Anniversary Edition)

Do you mean plugging hardware devices allows set timer interval down to 1 ms?

No. It seems to be more a special function in some, but not all USB-MIDI drivers. After an application causes the driver to connect to the device, a TimerQueueTimer can be created with an interval of 1 ms (measured), after the connection is closed, a new Timer can not anymore be set to a lower interval than 15.6 ms.

I used a litte application that creates a timer, does a loop count 100 and shows the elapsed milliseconds between all timerticks in a list. Beside this, I used a second application to connect a Midi-device. It didn’t matter which application I used, the change (in the measuring app) always occurred when I selected / deselected a device with one of the drivers mentioned above. (in the second app) I used a MidiLibrarian, a Midi monitor tool, a Midi monitor store app , a free sequencer… Usually the Midi-device can be selected in the ‘Setup’ menu. I also made a short test with DWM, I got fast results between ‘Playback.Start’ and ‘OutputDevice.Dispose’ (always in the case I selected a device with one of the corresponding drivers above)

[melanchall]

Yes, I know what a device driver is. I thought you mean some special devices and software.

Hmm, very interesting. Maybe driver does some OS level manipulations internally. Thanks for the info!