Wren Wiki

User Tools

Site Tools

Trace:
faq

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 [2022/03/31 21:06]
jan View for mouse / keys changed 		faq [2022/06/30 13:59] (current)
jan [MIDI setup]
Line 39: Line 39:
 ==== The, or some,  wires are not visible in the editor ==== ==== The, or some,  wires are not visible in the editor ====
  
-The wire thickness may have been set to zero, in the editor top pane under 'wires' you can change this with the up/down control. It may also be that the wires were set to be invisible (in that case the 'wires' indicator will be yellow), use ''Ctrl+W''' to toggle wire visibility - or click on the 'wires' word in the top tool bar.+The wire thickness may have been set to zero, in the editor top pane under 'wires' you can change this with the up/down control. It may also be that the wires were set to be invisible (in that case the 'wires' indicator will be yellow), use ''Ctrl+W'' to toggle wire visibility - or click on the 'wires' word in the top tool bar.
  
 It is possible to set selected wire trees to be invisible, thay can be made visible from the action menu in this case (or just use ''i'', or ''I''. It is possible to set selected wire trees to be invisible, thay can be made visible from the action menu in this case (or just use ''i'', or ''I''.
Line 83: Line 83:
 A lot of modules are rate smart, they will adjust their calculation rate from control rate to audio rate when an audio rate signal gets connected to one of it's inputs (and the connectors on it will change color too then). A lot of modules are rate smart, they will adjust their calculation rate from control rate to audio rate when an audio rate signal gets connected to one of it's inputs (and the connectors on it will change color too then).
  
 +Also see [[wire_colors | wire colors]], [[add_wires | add wires]] and [[remove_wires | remove wires]].
 ==== How to change parameters ==== ==== How to change parameters ====
  
Line 157: Line 158:
  
 ==== MIDI setup ==== ==== MIDI setup ====
-    * Trough the main menu item settings/MIDI devices select the MIDI devices to be used for input and output. +    * Trough the main menu item ''setup/MIDI setup'' select the MIDI devices to be used for input and output. Also there select a MIDI Channel to be used and, when usung (N)RPN, select the (N)RPN preferred mode to be used.
-    * In the settings screen ''F3'' select the MIDI Channel to use and select the (N)RPN preferred seting.+
  
 ==== OSC setup ==== ==== OSC setup ====
  
-Each //ren// instance can either be an OSC transmitter (client) or an OSC receiver (server), but not both at the same time. The client / server indications are [[http://opensoundcontrol.org/ | official OSC terms]] (and also see the [[http://cnmat.org/OpenSoundControl/ | CNMAT pages]].+The OSC configuration can be reached trough the main menu ''Setup/Osc setup'', 
 + 
 +Each //Wren// instance can either be an OSC transmitter (client) or an OSC receiver (server), but not both at the same time. The client / server indications are [[http://opensoundcontrol.org/ | official OSC terms]] (and also see the [[http://cnmat.org/OpenSoundControl/ | CNMAT pages]].
  
 There can be multiple listeners (servers) on one computer, but you can have one transmitter (client) only on any single computer (but you could have more transmitters (clients) spread over multiple computers). There can be multiple listeners (servers) on one computer, but you can have one transmitter (client) only on any single computer (but you could have more transmitters (clients) spread over multiple computers).
Line 168: Line 170:
 When everything is set up correctly the //Wren// instance should be able to talk to or listen to any OSC enabled device (or software) present on your network (or computer). It is not possible to broadcast OSC messages out of your local network. With the proper holes set in routers etc. it should still be possible to set up a single transmitter (client) to receiver (server) link though. When everything is set up correctly the //Wren// instance should be able to talk to or listen to any OSC enabled device (or software) present on your network (or computer). It is not possible to broadcast OSC messages out of your local network. With the proper holes set in routers etc. it should still be possible to set up a single transmitter (client) to receiver (server) link though.
  
-Note: in the OscMessage module you do not specify the the leading slash (/) character, //Wren// will add it it by itself.+Note: in the OscMessage module you do not specify the the leading slash ''/'' character, //Wren// will add it it by itself.
  
 Note: OSC address patterns are case sensitive, as in Module will //not// match module. Note: OSC address patterns are case sensitive, as in Module will //not// match module.
  
-=== To set up //Wren// as an OSC //transmitter (client)// do the following: ===+=== To set up Wren as an OSC transmitter (client) do the following: ===
  
-    * In the settings screen ''F3'' make sure you give your synth a name, this name will be used as part of the OSC addresses sent around. +    * In the settings screen ''F3'' make sure you give your synth a name, this name will be used as part of the OSC addresses sent around and listened to. 
-    * Then go trough the main menu to the Setup / OSC setup screen for the following settings:+    * Then go trough the main menu to the ''Setup / OSC setup'' screen for the following settings:
     * The IP address must be set to a broadcasting address to allow for multiple receivers, otherwise the IP address of the single receiver can be used. The address to use depends on your network configuration but selecting 255.255.255.255 should always work. Locally I use 192.168.1.255 as the address which will reach all computers in the address range 192.168.1.x. When everything is on one computer using 127.0.0.1 or localhost works too.     * The IP address must be set to a broadcasting address to allow for multiple receivers, otherwise the IP address of the single receiver can be used. The address to use depends on your network configuration but selecting 255.255.255.255 should always work. Locally I use 192.168.1.255 as the address which will reach all computers in the address range 192.168.1.x. When everything is on one computer using 127.0.0.1 or localhost works too.
-    * The port must be set to a number not in use for any of the participating computers. When you select a port that is in use you will not be able to transmit a test message later on, and OSC errors will be reported in the log (OSC error logging is on by default, OSC message logging is off by default).+    * The port must be set to a number not in use for any of the participating computers. When you select a port that is in use you will not be able to transmit a test message later on, and OSC errors will be reported in the log (OSC error logging is on by default, OSC message logging is off by default - see the Debug screen ''F5'').
     * Check the Use OSC checkbox, then hit OK.     * Check the Use OSC checkbox, then hit OK.
     * Reopen the OSC settings screen and then send test messages using the button, the 't' light should light up on each transmission. When it does not light up you probably selected a port that was already in use, so try another one.     * Reopen the OSC settings screen and then send test messages using the button, the 't' light should light up on each transmission. When it does not light up you probably selected a port that was already in use, so try another one.
  
-=== To set up //Wren// as an OSC //receiver (server)// do the following: ===+=== To set up Wren as an OSC receiver (server) do the following: ===
  
-    * In the settings screen ''F3'' make sure you give your synth a name, this name will be used as part of the OSC addresses sent around. +    * In the settings screen ''F3'' make sure you give your synth a name, this name will be used as part of the OSC addresses sent around and listen to. 
-    * Then go trough the main menu to the Setup / OSC setup screen for the following settings:+    * Then go trough the main menu to the ''Setup / OSC setup'' screen for the following settings:
     * The IP address must be set empty (internally 0.0.0.0 will be used in this case, but the field being empty will open the UDP socket as a listening (server) socket, filling in anything at all will try to open it as a client socket, so make sure that the field is completely empty). When OSC is set up to be a receiver no test messages can be sent from it, and the button do do so will be disabled when the IP addr field is (completely) empty.     * The IP address must be set empty (internally 0.0.0.0 will be used in this case, but the field being empty will open the UDP socket as a listening (server) socket, filling in anything at all will try to open it as a client socket, so make sure that the field is completely empty). When OSC is set up to be a receiver no test messages can be sent from it, and the button do do so will be disabled when the IP addr field is (completely) empty.
     * The port must be set to the same value that was used to set up the transmitter.     * The port must be set to the same value that was used to set up the transmitter.
Line 206: Line 208:
 The following addresses are currently being used: The following addresses are currently being used:
  
-    * /*/testmessage can be sent (from an OSC transmitter only), this is a single OSC message with a float value of 1.000 an integer value of 1001, and a string value of '1002'. +    * /*/testmessage can be sent (from an OSC transmitter only), this is a single OSC broadcast message with a float value of 1.000 an integer value of 1001, and a string value of '1002'. 
-    * /<synthname>/sync can be sent and received by the Sync module. This message has no parameters. The message is received when the current //Wren// instance is set to be an OSC receiver. the message is transmitted when the current //Wren// instance is set to be an OSC transmitter. Sync messages are naive, they assume zero time delay between transmitter and receiver.+    * /<synthname>/sync can be sent and received by the Sync module. This broadcast message has one float parameter. The message is received by //Wren// instances set to be an OSC receiver. The message is transmitted when the current //Wren// instance is set to be an OSC transmitter. Sync messages are naive, they assume zero time delay between transmitter and receiver. The float value could, for instance, be used to sync tuning between patches and the message itself can serve to sync up LFO's.
     * /<synthname>/<user_defined> for the OscMessage module, this will send or receive a single float message. Messages with a matching address with more than one parameter can still be processed as long as the first one is of type 'f' (float). To force a value to be sent out the trigger input needs a low to high transition - you could put an LFO on that, or make a change detector based upon a sample and hold, or use the differentiator module.     * /<synthname>/<user_defined> for the OscMessage module, this will send or receive a single float message. Messages with a matching address with more than one parameter can still be processed as long as the first one is of type 'f' (float). To force a value to be sent out the trigger input needs a low to high transition - you could put an LFO on that, or make a change detector based upon a sample and hold, or use the differentiator module.
-    * All modules can receive OSC messages when the module title is set to start with an '@' character. They then can be addressed with a /<synthname>/<modulename_without_@>/<control_name> pattern. The first value in the message must be of type 'f' (float) with a value from zero to one, with zero mapping to the lowest possible knob value and one mapping to it's highest possible value. Please note that OSC messages are case sensitive.+    * All modules can receive OSC messages when the module title is set to start with an ''@'' character. They then can be addressed with a /<synthname>/<modulename_without_@>/<control_name> pattern. The first value in the message must be of type 'f' (float) with a value from zero to one, with zero mapping to the lowest possible knob value and one mapping to it's highest possible value. Please note that OSC messages are case sensitive.
  
-==== How to get //Wren// to play with [[http://jackaudio.org/ | JACK]] ====+==== How to get Wren to play with JACK ====
  
  What I did:  What I did:
faq.1648760769.txt · Last modified: 2022/03/31 21:06 by jan

Page Tools