blueShare - SoundObjects

Midi Controller4

Mon, 18 Nov 2024 10:24:10 +0000

DESCRIPTION: This is a Midi Controller data recorder and player. Midi Controller1 records and plays Midi Controller Data. You can set the resolution of this device in Device Data Range, this is 128 as Midi 1.x has a resolution of 128. CC number and start/initialization values should be given. A name should be entered; this name is used to send the Midi data globally, i.e. as gkxxxx signal. Other, higher numbered Instruments can pick this Global data up. In that particular Instrument, the range of the Midi data (0-127) can be scaled at will and, if needed, interpolated. When recording the midi controller data, set the length of the SoundObject and the resolution you want to record in; both are in seconds. Length and resultion go hand in hand. These values are needed so that, on playback, the SoundObject's length and resolution can be used to scale. Be sure to have the Midi Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Midi Controller. Midi CC data are global: they have an influence on ALL notes of that Instrument as they are used to control the parameters of the Instrument. Most of the time, Midi Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior. When setting a name as outputfile for recording, the format of the name is as follows: NAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION length of SoundObject and resolution are in seconds. In the Instrument you want to influence with controller data, here is basic example to add to the Instrument: imiditotal = 1/128 ; midi rsolution kmass_scl scale gkxxxx, 2*imiditotal, .02*imiditotal ; scale midi values to usable range and let it influence the .02-2 range kPortTime linseg 0,0.001,i() ; if needed, create a value that quickly ramps up to .01 for better response and interpolate the controller values kmassscl portk kmass_scl, kPortTime ; range 0.02 - 2 a1 poscil3 1, kmassscl*200 ; make some noise First set the switch to 'write'. Run Blue. Then set switch to 'play' and the controller data are played back. There is an optional printing to see what is happening. Plotting the controller data can be used if you have GNUPLOT installed. Portamento can be set in your instrument but is optional. It does help to smooth out the poor resolution of the Midi Controller and avoid sudden jumps between controller data values. CONTROLLERS: see the help balloon when hovering over the controllers in the instrument. Help can be turned off by pressing the 'I' button next to the play bar. --- version 1, November 2024 - initial version

Midi Controller3

Mon, 18 Nov 2024 10:24:02 +0000

Midi Controller2

Sun, 17 Nov 2024 18:31:39 +0000

Joystick Controller

Sun, 17 Nov 2024 14:46:52 +0000

DESCRIPTION: This is a Joystick Controller data recorder and player. Joystick Controller2 records and plays 3 different Joystick Controller Data. You can set the resolution of this device in Device Data Range, this is 65536 for my Joystick. CC number and start/initialization values should be given. A name should be entered; this name is used to send the Joystick data globally, i.e. as gkxxxx signal. Other, higher numbered Instruments can pick this Global data up. In that particular Instrument, the range of the Joystick data (0-127) can be scaled at will and, if needed, interpolated. When recording the midi controller data, set the length of the SoundObject and the resolution you want to record in; both are in seconds. Length and resultion go hand in hand. These values are needed so that, on playback, the SoundObject's length and resolution can be used to scale. Be sure to have the Joystick Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Joystick Controller. Joystick CC data are global: they have an influence on ALL notes of that Instrument as they are used to control the parameters of the Instrument. Most of the time, Joystick Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior. When setting a name as outputfile for recording, the format of the name is as follows: NAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION length of SoundObject and resolution are in seconds. In the Instrument you want to influence with controller data, here is basic example to add the Smooth Joystick Data Module to the Instrument: idevicerange = 1/65536 ; joystickrsolution kmass_scl scale gkxxxx, 2*imiditotal, .02*imiditotal ; scale midi values to usable range and let it influence the .02-2 range kPortTime linseg 0,0.001,i() ; if needed, create a value that quickly ramps up to .01 for better response and interpolate the controller values kmassscl portk kmass_scl, kPortTime ; range 0.02 - 2 a1 poscil3 1, kmassscl*200 ; make some noise First set the switch to 'write'. Run Blue. Then set switch to 'play' and the controller data are played back. There is an optional printing to see what is happening. Plotting the controller data can be used if you have GNUPLOT installed. Portamento can be set in your instrument but is optional. It does help to smooth out the poor resolution of the Joystick Controller and avoid sudden jumps between controller data values. Be aware that the output values of a joystick move around value 0, so a range of -x to x. In my case, the 'raw'value range is from -32768 to 32768, where 0 is the joystick X and Y axes in restposition. CONTROLLERS: see the help balloon when hovering over the controllers in the instrument. Help can be turned off by pressing the 'I' button next to the play bar. --- version 1, November 2024 - initial version

Midi Controller1

Sun, 17 Nov 2024 14:46:31 +0000

AthenaCL Score generator

Mon, 30 Jan 2023 10:21:41 +0000

The AthenaCL Score Generator is not an easy click and play module. AthenaCL has tons of options that make it hard to master, and can produce unexpected but interesting results. So, this ObjectBuilder is not the easiest one to understand and use. You should know your way in AthenaCL itself in order to appriciate this module. One must really try and try some more, but i can be VERY rewarding. In any case, you'll need the AthenaCL manual by your side, start with a simple basic setting and work your way up. AthenaCL for python 3 can be found here: https://github.com/ales-tsurko/athenaCL Big thanks to Ales Tsurko to have converted it to python 3! Another big thanks goes to Michael Gogins, who implemented 2 seed options: 1 for the TextureModule (creates the structure), 1 for "the rest" (ParameterObjects). Leaving the seeds open lets the computer decide what sequence is generated, each run a different one but according to the rules. You should run the athenaPipe.py from Steven Yi as it acts as a bridge between AthenaCL and Blue. The command line looks something like: python3 /PATH/TO/athenaCL/athenaCL/athenaPipe.py $infile athenaPipe.py sends the data from the AthenaCL Score Generator to AthenaCL. Every pfield can be set up to use PathRead. However, In this module, you need to set PathRead in P4 to read notes, frequencies and such, and convert them to the values you need in your instrument. It is possible to use the normal Path ( pin ) to make 4 multisets and give each MultiSet a weight. P2 = BPM. Csound has basic 60 bpm, i use 120 bpm- the AthenaCL default. P3 = combination of rhythm, duration and accents. So P2 and P3 work together to produce the final result. P4 = set for input of notes or frequencies, sieves, and up to 4 MultiSets. Use on/off switch to switch MultiSet, and add a weighting for the MultiSet but P4 can be set to other ParameterObjects, like random. Use the filter to get the values in a useable range In AthenaCL, amplitude and panning have their own meaning, but here in the AthenaCL Score Generator these are ommitted. Use the TEST button beforehand to check to see if you get the desired results. It is easy to make typing errors... The AthenaCL Score Generator generates data for 12 pfields. It can NOT produce less, or more pfields. If you have an instrument that only uses 6 pfields, the Csound output will protest but still work: WARNING: instr 1 uses 6 p-fields but is given 12 Perhaps in a future realease this can be improved, but hey- it works.... --- version 1.4, April 2021 - seed for TextureModule (TMsd) - seed for the rest = ParameterObjects (TPsd) version 1.3, March 2021 - added the 4 x MultiSet option and weighting per Set version 1.2 February 2021 - added Texture Clone with filtering options - set original Texture to mute, use only TextureClone output version 1.1, february 2021 - now all pfields >3 can produce the PathRead to freq etc. - simplified GUI - added help in the balloons version 1.0, february 2021 - initial version by Menno Knevel

nGen Score Generator2

Sat, 28 Jan 2023 11:01:51 +0000

The nGen Score Generator is a wrapper for nGen ( http://mikelkuehn.com/index.php/ng Author: Mikel Kuehn), a score genrator that runs on the 3 major platforms. The GUI follows the syntax of the original nGen as much as possible, however tries to mimic the data flow from left to right; the pfields and their output flow from left to right and from bottom to top. Not all functions from the main program nGen are integrated, the nGen Score Generator. As the nGen system calculates pfield after pfield, if you change the order of some pfields, you can make the result of the previous pfield dependent on the present one. short manual: - choose desired number of events to generate - set number of pfields accordingly with the P field slider - to the left of the P field slider, set Dropdown menu of all p-fields used to 'on' - left upper corner, set global random seed value; every seed produces a unique sequence (values between 0 and 65536) - set or enter data from left to right:, Random Deviation (only works for this pfield) --> Input Filter --> Dynamic Data Function A (and B if you want) --> Data Entry for this function --> Output Filter. - check if the right values are used by pressing TEST - up to 15 p fields can be generated Unlike the nGen program itself, the nGen generator is momentarily unable to process: - macro's - include files - if / endif statements - f-tables. Where, in nGen, one puts in the G Block something like '>f1 0 4096 10 1; a sine wave', you are requierd to keep the f-tables like 'f1 0 4096 10 1; a sine wave' in the Global Score of encapsulated instrument, or put it in the Global Score. just work with ftgen inside the instrument to bypass this issue. ------------ version 1.1, February 2021 - extended Tempo options with Tempo types - added second data inputs - added sampling rate option for FFT use version1, August 2020 - initial version by Menno Knevel

2channelModulate

Mon, 21 Nov 2022 15:19:15 +0000

2channelModulate outputs 2 output modulations, one has the inverse phase of the other. 2 ranges can be set: from -1 to 1 or from 0 to 1 This modulator can be used to, for example having set the range to 0..1, modulate the amplitude of 2 instruments. Where the amplitude of the one increases, the amplitude of the other decreases at the same speed. When set at slow speeds, one instrument takes over the other one etc. When set to higher speeds, these 2 instruments seem to merge. The range -1..1 can be used, for example, to modulate around a fixed value. A filter of instrument 1 will get modulated around its filter setting, while in instrument 2 the same thing will happen but in inverse. Idea is to create some level of interdependence between 2 instruments. 2channelModulate uses the Global variable system to communicate between different instruments. In the instruments to be modulated, code must be added. For example, for amplitude for the first instrument: blueMixerOut asigL * gkModulate, asigR * gkModulate for the second instrument: blueMixerOut asigL * gkModulate_inverse, asigR * gkModulate_inverse --- version 1.1, November 2022 - changed chnset/chnget for Global k rates (simpler) version 1, November 2022 - initial version

SequencerControl

Thu, 10 Nov 2022 10:37:15 +0000

SequencerControl is a sequencer. It triggers and sends data events to the instrument as set in the Instrument column. It does not produce sound on its own. Rhythm length of note, pitch and amplitude are standard parameters of the sequencer. It depends on the receiving Instrument how these data are handled. For example as MIDI pitches or Frequency etc. Other P fields can be added by moving the 'Add P fields' slider to the desired P field number. However, when the SoundObject SequencerControl is Frozen, the wave sound will be available in this Frozen SoundObject. --- version 1, November 2022 - initial version

OSC Reaper control 2.1

Sun, 28 Nov 2021 18:42:56 +0000

This Sound SoundObject is meant to control a DAW, Reaper in this case by the OSC protocol. The DAW can run either on the localhost or on a second computer. I use Reaper for this purpose as it is well designed for use with OSC. The commands can be found in the Configuration file of Reaper/OSC. ----- version 2.1, November 2021 - added volume faders & Mute and Solo per channel - rewind and forward option, MasterVolume version 2.0, november 2021 - using latest OSCsend opcode