ROADMAP for firmware 5.0

[Simon]

This is the potential roadmap for firmware 5.0.
ETA: unknown for now

New Major Features:

• Smart tap tempo + sync to 1-12ppq signal - viewtopic.php?t=268

New Minor Features:

• U-SYNC: control DAW tempo from Nome - viewtopic.php?t=117
• U-SYNC: allow syncing multiple Nomes in a chain (see also viewtopic.php?t=480 )
• When syncing a Nome to another, control play/stop from the master
• Improving metronome by reducing volume of 8th and 16th notes - viewtopic.php?p=2508#p2508
• Assign a number to change USB device name - viewtopic.php?t=235
• Full configuration via SysEx messages viewtopic.php?t=233
  • + configuration software (config your device from a computer)

Fixed issues:

• U-SYNC get confused when connecting multiple Nomes - viewtopic.php?t=480

Note: the much expected smart tap tempo feature was originally planned for FW 4.0, but implementing it in 4.0 would have delayed all other major features - which are much quicker to implement. It's also such a big feature that it definitely deserves its own firmware release, just like U-SYNC with FW 3.0.

[Milosdrummer]

Looking forward to this, thank you Simon!

[Dave]

Not sure where to post this, but Microsoft has started released the MIDI updates (native ASIO coming at some point). Not sure if this impacts the Nome project, but hopefully it will help, not hurt!

https://devblogs.microsoft.com/windows- ... preview-1/

MIDI 1.0 benefits with this release:

Every MIDI device is now multi-client, even for existing applications and devices. You do not need vendor drivers to enable more than one application to use a MIDI device.

MIDI Port names are now better. We’ve surveyed many MIDI devices in market and come up with algorithms which provide better port and endpoint names for these devices. But there will always be exceptions. If you see those, please report them to us on GitHub (developers) or on our Discord Server (everyone else)

Devices using the new USB MIDI 2.0 Class driver have faster data transfer. The USB MIDI 2.0 class driver uses faster data transfer mechanisms even for MIDI 1.0 devices. (If your MIDI 1.0 device is not picked up by the new driver, and is class-compliant, you can manually assign usbmidi2.sys to the device. We’ll post instructions for this in the future)

The new features are backwards compatible with your existing apps and devices USB MIDI 2.0 devices and USB MIDI 1.0 devices are both usable from the WinMM (MME) APIs in a MIDI 1.0 capacity.

Everything here works on Intel/AMD x64 as well as Arm64 devices


When will we go into retail (mainstream) Windows releases?
Once we are happy with the compatibility with existing apps and devices, we’ll move Windows MIDI Services into the latest supported releases of Windows 11 as well as the supported Windows 10 release. We hope this will be soon, but this is a quality-driven decision and we need your feedback. We’ve tested dozens of apps and MIDI devices here, and involved partners testing with their newest offerings, but there are thousands of MIDI devices released in the wild over the past 40+ years and we don’t have every one of them. We don’t want to break your MIDI workflow.

[Simon]

Thanks Dave that is very useful info!

I'm not sure this has anything to do with ASIO (audio) though as it seems to be MIDI only? Though I also heard Microsoft plans on improving the audio layer of Windows (halleluia - it only took 15 years). In any case that is great news about the MIDI device names - that will definitely make things clearer for Windows users

[w_iro]

U-SYNC: control DAW tempo from Nome - viewtopic.php?t=117 - this is what I am looking forward to the most! Controlling the tempo through the DAW is not as cool as the big knob from Nome II <3

[Simon]

Who does not like a big knob?

(sorry I could not help it... )