User Tools

Site Tools


faq:general

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
faq:general [2010/09/23 22:43] camillefaq:general [2011/09/01 15:02] camille
Line 7: Line 7:
  
 ??? Is there a Windows version and if not, are there plans to make one? ??? Is there a Windows version and if not, are there plans to make one?
-!!! Osculator currently is only available on Mac OS X (10.4 and higher), this means it doesn't run on Windows. +!!! Osculator currently is only available on Mac OS X (10.4 and higher), this means it doesn't run on Windows.\\ 
-Next major version of Osculator will be compatible with Mac OS and 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.
  
 ??? How do I completely uninstall OSCulator and its components? ??? How do I completely uninstall OSCulator and its components?
Line 22: Line 21:
       * ''/Users/''//<your user name>//''/Library/Preferences/net.osculator.OSCulator.LSSharedFileList.plist''       * ''/Users/''//<your user name>//''/Library/Preferences/net.osculator.OSCulator.LSSharedFileList.plist''
       * ''/Library/Application Support/OSCulator''       * ''/Library/Application Support/OSCulator''
 +
 +??? Is there any documentation about the routing arguments? i.e. what does "bref" or "uref" exactly do?
 +!!! 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.
  
faq/general.txt · Last modified: 2016/12/10 09:43 by camille