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 revision Previous revision
Next revision
Previous revision
faq:general [2011/09/01 15:02]
camille
faq:general [2016/12/10 09:43] (current)
camille
Line 1: Line 1:
 =?==== General FAQ ====== =?==== General FAQ ======
  
-??? How can I contact the author of this software+??? How can I get support on OSCulator
-!!! If you need support on how to use OSCulator, the recommended way of contacting the author ​is [[http://www.osculator.net/​forum|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. +!!! The recommended way of asking for help is [[https://​osculator.net/​forum|through the community'​s forum]].
-If you have a more personal query, you can also send an email to Camille (camille at osculator dot net).+
  
 +If you require privacy, or have a more specific request, you can also send an e-mail to Camille (camille at osculator dot net).
  
-??? 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.\\ 
-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?
 !!! Please follow these instructions:​ !!! Please follow these instructions:​
-  - Launch OSCulator and open the Preferences,​ click on the Inputs ​tab +  - Launch OSCulator and open the Preferences,​ click on the Outputs ​tab 
-  - Uncheck the "Enable Perfect Pairing ​extension"​ box, this will uninstall the kernel extension ​;+  - Uncheck the "Install the Virtual Joystick kernel ​extension"​ box ;
   - Quit OSCulator ;   - Quit OSCulator ;
-  - Delete the following ​folders ​if they exist: +  - Delete the following if they exist: 
-      * ''/​Applications/​OSCulator ​ƒ''​ +      * ''/​Applications/​OSCulator.app''​ 
-      * ''/​Users/''//<​your user name>//''/​Library/​Application Support/​OSCulator''​ +      * ''/​Users/''//<​username>//''/​Library/​Application Support/​OSCulator''​ 
-      * ''/​Users/''//<​your user name>//''/​Library/​Preferences/​net.osculator.OSCulator.plist''​ +      * ''/​Users/''//<​username>//''/​Library/​Preferences/​net.osculator.OSCulator.plist''​ 
-      * ''/​Users/''//<​your user name>//''/​Library/​Preferences/​net.osculator.OSCulator.LSSharedFileList.plist''​+      * ''/​Users/''//<​username>//''/​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?+ 
 +??? OSCulator creates OSC routings automatically from received MIDI input, What do "​bref" ​and "​uref"​ exactly ​mean?
 !!! Short answer: you should not use them manually and therefore they are not documented.\\ !!! 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. 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. 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.1314882163.txt.gz · Last modified: 2011/09/01 15:02 by camille