If you need support on how to use OSCulator, the recommended way of contacting the author is through the community's forum. You will receive a quick answer that will also benefit to all the users that could come across the same question. If you have a more personal query, you can also send an email to Camille (camille at osculator dot net).
Osculator currently is only available on Mac OS X (10.4 and higher), this means it doesn't run on Windows.
Next major version will be compatible with Mac OS and Windows. I will communicate on the availability of this new version as soon as something is ready, but not before.
Please follow these instructions:
/Applications/OSCulator ƒ/Users/<your user name>/Library/Application Support/OSCulator/Users/<your user name>/Library/Preferences/net.osculator.OSCulator.plist/Users/<your user name>/Library/Preferences/net.osculator.OSCulator.LSSharedFileList.plist/Library/Application Support/OSCulator
Short answer: you should not use them manually and therefore they are not documented.
Long answer: (bref means 'by reference' and uref 'update reference.)
These are internal routing arguments to handle the case of bi-directional routing with message having multiple arguments.
They are used when an OSC message with at least 2 arguments are configured with two MIDI CC. When the MIDI host replies, the received message (/midi/ccXY/Z) only have 1 argument. Therefore, in order to send the correct message back to the OSC device, we must build a OSC routing for each MIDI CC that will use and/or update the current values of the OSC device.
The most simple way to demonstrate this automatic configuration is to use TouchOSC with the X/Y controller, and assign two MIDI CC on each arguments. Then map these control changes to a MIDI compatible software that has bi-directional features (like Ableton Live). When Osculator receives the MIDI replies, you will notice how the OSC routings are built.