Nord User Forum

Hi, I noticed that Clavia released a firmware update for the Nord Lead 4 that contains OS v1.32. Previously, I was on OS v1.30. I upgraded successfully today, but does anyone here know what has changed or what bugs were fixed? I searched for answers, but I got nothing…

Location of the update:
https://www.nordkeyboards.com/legacy-pr ... llToTabs=1

Schmart wrote: ↑21 Feb 2025, 14:49 Hi, I noticed that Clavia released a firmware update for the Nord Lead 4 that contains OS v1.32. Previously, I was on OS v1.30. I upgraded successfully today, but does anyone here know what has changed or what bugs were fixed? I searched for answers, but I got nothing…

Location of the update:
https://www.nordkeyboards.com/legacy-pr ... llToTabs=1

Release notes:
Windows updater is now bundled with installer for Nord Keyboards USB Driver v4.x

so no functional update, just bundling of the driver...

Thanks for the reply! I did see that remark, but I find it unlikely that Clavia would also change the OS version if they’ve only changed the installer package to now include the driver. The OS version on the Nord Lead displays a version “1.32” so that means they have at least compiled/built a new firmware image for that. I might try a binary compare of the 1.30 and 1.32 images to see what changed

Schmart wrote: ↑21 Feb 2025, 16:11 Thanks for the reply! I did see that remark, but I find it unlikely that Clavia would also change the OS version if they’ve only changed the installer package to now include the driver. The OS version on the Nord Lead displays a version “1.32” so that means they have at least compiled/built a new firmware image for that. I might try a binary compare of the 1.30 and 1.32 images to see what changed

They have done it (changing version just for that reason) also for most other models, see https://www.nordkeyboards.com/update-history/ for example NS3 https://www.nordkeyboards.com/update-hi ... e-history/

Thanks again, it's a good argument, I think you are right. Also looking at the differences between firmware images for v1.30 and v1.32, there's not enough changes on a binary level to indicate a significant change of functionality such as bugfixes or extra features. From the analysis below, the 0x82 -> 0x84 is in decimal 130 -> 132 (i.e. the version number) and the rest is probably checksum-related.