ID 506965 - Long NDI Monitor Out sender names in Nuke are truncated and can override other NDI streams

Problem summary:
Long NDI Monitor Out sender names in Nuke are truncated and can override other NDI streams 

Customer reported version:
Nuke 14.0v6

Customer reported platform:
Windows 10

Steps to reproduce:
1) Launch Nuke and create a second Viewer node in the Node Graph.
2) Double-click the Viewer nodes to open their Properties, then Enable Monitor Out and set the Device to NDI for both Viewers:

3) Navigate to File > Save Comp As..., and Save the script with a long name, such as ThisIsMyVeryLongNukeProjectName_BecauseThereAreTooManyCharacters.nk
3b) At this point it may be necessary to Clear and Reopen the Nuke script.
4) Launch NDI Studio Monitor, or similar, and observe how only one stream is available with a truncated name:

Expected behavior:
Each NDI stream from Nuke should have a unique name and not exceed the sender name character limit.

Actual behavior:
When attempting to output NDI streams from Nuke, any stream names greater than 57 characters will be truncated. If multiple streams share the same name after being truncated, they will override each other and only result in one NDI stream.

If a shorter Project name is used like ThisIsMyShorterNukeProjectName, then both streams are available in NDI Studio Monitor:

Workaround:
In Nuke 14.1v2+/15.0v2+ it is possible to manually specify a NDI stream name, as pictured below. In prior versions, there are no known workarounds other than utilizing shorter project names.

Reproduced by Support in:
Nuke 15.0v4 - Windows 10
Nuke 15.0v1 - Windows 10
Nuke 14.1v1 - Windows 10
Nuke 13.2v1 - Windows 10

Earliest version tested:
Nuke 13.2v1 - This feature (NDI Monitor Out) did not exist before this version