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(<smooth>) ; 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
General@menno0blue.soundObject.Sound
Sound Object
Midi Controller3
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(<smooth>) ; 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
General@menno0blue.soundObject.Sound
Sound Object
Midi Controller2
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(<smooth>) ; 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
General@menno0blue.soundObject.Sound
Sound Object
Joystick Controller
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(<smooth>) ; 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
General@menno0blue.soundObject.Sound
Sound Object
Midi Controller1
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(<smooth>) ; 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
General@menno0blue.soundObject.Sound
Instrument
TimbreModule
The TimbreModule is intended to be used as an amplitude depending timbre coloring of the incoming signal.
The louder (or softer) the amplitude of the incoming, the resonance intensity increases.
Idea is to add some viability to the Instrument.
Choices are to add some Parametric EQ and/or a Treble cutoff.
---
version 1, May 2023
- initial version
Unsorted@menno0blue.orchestra.BlueSynthBuilder
Instrument
2Mod4 1/2
2Mod4 1/2 consists of 2 Low Frequency Modulators, where Modulator 2 works on Modulator 1. Modulator 2 can be set to OFF.
Several wave types can be selected. The 7th wave type allows to quickly set the this Modulator to a steady signal- some kind of "pause" if you will.
All can be changed in realtime.
The 2 Modulators can be mixed and so more complex wave patterns occur.
2Mod4 1/2 is the first part of 2; here, the 4 outputs can be switched on, while 2Mod4 2/2 splits these 4 outputs into one in phase, and another that is out of phase.
As the phase and out of phase modulators do follow the same modulation values, the out of phase one can get its own offset.
This Instrument has 4 possible outputs.
1. ADD - both modulators added together, or Modulator1 only
2. MAX - both modulators added together but only the maximal values are given
3. MIN - both modulators added together but only the minimal values are given
4. MULT - both modulators multiplied. For this to happen, both Modulators needs to be activated.
Some extra coding inside the target Instrument is needed. 2Mod4 2/2 produces k-rate modulations, (or when resolution is set, at a-rate) but if i-rate is needed, a conversion
inside the target instrument must be implemented.
Scaling must be done in the target Instrument.
ALL SCALING AND ADDING AN OFFSET TO THE PRODUCED VALUES MUST BE DONE IN THE TARGET INSTRUMENT ITSELF.
2Mod4 only produces values between -1....1. Any offset or scaling back to values between 0...1 must be done in the target Instr.
To save CPU, only select the outputs you need!
---
version 1, April 2023
- initial version
Unsorted@menno0blue.orchestra.BlueSynthBuilder
Instrument
2Mod4 2/2 Module
DESCRIPTION:
2Mod4 2/2 Module is the second half of the Modulator system, the other one is called 2Mod4 1/2.
This Module gets up to 4 modulations at k-rate from 2Mod4 1/2.
- kADDITION, kADDPHASE and iADDPHASE is derived from the ADD channel
- kMAXIMUM, kMAXPHASE and iMAXPHASE is derived from the MAX channel
- kMINIMUM, kMINPHASE and iMINPHASE is derived from the MIN channel
- kMULTIPLY, kMULTIPHASE and iMULTPHASE is derived from the MULT channel
They are at k-rate, k-rate but inverted phase, and i-rate respectively.
These modulated signals can be used to manipulate frequencies or amplitudes of the opcodes, or effects like filters in the instrument, and
everything that you want to modulate.
---
version 1, April 2023
- initial version
Unsorted@menno0blue.orchestra.BlueSynthBuilder
Instrument
Stretcher
DESCRIPTION:
Stretcher is a sampler for mono and stereo samples.
It is capable of stretching the sample in realtime. Or plays them in reverse.
Attention: by activating the filter, also the filter envelope drawings become available.
In Midi Pitch mode, Midi C4 = normal pitch of sample
In Frequency mode, frequency note 8.00 = normal pitch of sample
Also, real values can be used.
note example:
i2 0 0.8 60 1.0 ; P4 = midi value, P5 = amplitude
i2 0 0.2 261.625565 1.0 ; P4 = frequency, P5 = amplitude
i2 0 0.2 1 1.0 ; P4 = real value, P5 = amplitude
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 2, February 2023
- initial version
Sampler@menno0blue.orchestra.BlueSynthBuilder
Sound Object
AthenaCL Score generator
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
General@menno0blue.soundObject.ObjectBuilder
Sound Object
nGen Score Generator2
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
General@menno0blue.soundObject.ObjectBuilder
Effect
StereoXpansion
DESCRIPTION:
StereoXpansion first creates a MS stereo signal; the mono signal in the middle of the stereo field (M) is separated from the stereo information (S).
Then this MS stereo signal is converted back to stereo with the option of manipulating the stereo information.
---
version 1.0, Januari 2023
- initial version by Menno Knevel