I have noticed that if I try to send an OSC message without adding any “values” (arguments) then my NAP application crashes on the call to “send” the event, specifically:
Assertion failed: (oscEvent.getCount() > 0), function writeToPacket, file /Users/coenklosters/Documents/dev/nap/modules/naposc/src/oscsender.cpp, line 111.
OSC messages with no arguments are sensible and supported explicitly by the OSC spec (http://opensoundcontrol.org/spec-1_0):
An OSC message consists of an OSC Address Pattern followed by an OSC Type Tag String followed by zero or more OSC Arguments.
I believe that this is a bug. There are a number of systems using OSC (including 4DSound) which expect zero-argument OSC messages for certain operations. An arbitrary argument can be added, as a workaround, but this should be unnecessary.