[{"kind":"soundObject","id":47,"name":"Midi Controller4","description":"\nDESCRIPTION:\n\nThis 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.\nCC number and start/initialization values should be given.\nA name should be entered; this name is used to send the Midi data globally, i.e. as gkxxxx signal.\nOther, 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.\n\nWhen 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, \nthe SoundObject's length and resolution can be used to scale. \nBe sure to have the Midi Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Midi Controller.\n\nMidi 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. \n\nMost of the time, Midi Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior.\n\nWhen setting a name as outputfile for recording, the format of the name is as follows:\nNAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION\nlength of SoundObject and resolution are in seconds.\n\nIn the Instrument you want to influence with controller data, here is basic example to add to the Instrument:\n\n        imiditotal =   1/128                                                            ; midi rsolution\n        kmass_scl        scale gkxxxx,        2*imiditotal,  .02*imiditotal             ; scale midi values to usable range and let it influence the .02-2 range\n        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\n        kmassscl        portk    kmass_scl, kPortTime                                   ; range 0.02 - 2\n\n        a1  poscil3 1, kmassscl*200                                                     ; make some noise\n\nFirst 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.\nPlotting the controller data can be used if you have GNUPLOT installed.\n\nPortamento 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.\n\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 1, November 2024\n- initial version\n\n\n\n\n\n","blueType":"blue.soundObject.Sound","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2024-11-18T10:24:10.000Z"},{"kind":"soundObject","id":46,"name":"Midi Controller3","description":"\nDESCRIPTION:\n\nThis 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.\nCC number and start/initialization values should be given.\nA name should be entered; this name is used to send the Midi data globally, i.e. as gkxxxx signal.\nOther, 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.\n\nWhen 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, \nthe SoundObject's length and resolution can be used to scale. \nBe sure to have the Midi Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Midi Controller.\n\nMidi 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. \n\nMost of the time, Midi Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior.\n\nWhen setting a name as outputfile for recording, the format of the name is as follows:\nNAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION\nlength of SoundObject and resolution are in seconds.\n\nIn the Instrument you want to influence with controller data, here is basic example to add to the Instrument:\n\n        imiditotal =   1/128                                                            ; midi rsolution\n        kmass_scl        scale gkxxxx,        2*imiditotal,  .02*imiditotal             ; scale midi values to usable range and let it influence the .02-2 range\n        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\n        kmassscl        portk    kmass_scl, kPortTime                                   ; range 0.02 - 2\n\n        a1  poscil3 1, kmassscl*200                                                     ; make some noise\n\nFirst 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.\nPlotting the controller data can be used if you have GNUPLOT installed.\n\nPortamento 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.\n\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 1, November 2024\n- initial version\n\n\n\n\n\n","blueType":"blue.soundObject.Sound","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2024-11-18T10:24:02.000Z"},{"kind":"soundObject","id":45,"name":"Midi Controller2","description":"\nDESCRIPTION:\n\nThis 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.\nCC number and start/initialization values should be given.\nA name should be entered; this name is used to send the Midi data globally, i.e. as gkxxxx signal.\nOther, 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.\n\nWhen 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, \nthe SoundObject's length and resolution can be used to scale. \nBe sure to have the Midi Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Midi Controller.\n\nMidi 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. \n\nMost of the time, Midi Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior.\n\nWhen setting a name as outputfile for recording, the format of the name is as follows:\nNAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION\nlength of SoundObject and resolution are in seconds.\n\nIn the Instrument you want to influence with controller data, here is basic example to add to the Instrument:\n\n        imiditotal =   1/128                                                            ; midi rsolution\n        kmass_scl        scale gkxxxx,        2*imiditotal,  .02*imiditotal             ; scale midi values to usable range and let it influence the .02-2 range\n        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\n        kmassscl        portk    kmass_scl, kPortTime                                   ; range 0.02 - 2\n\n        a1  poscil3 1, kmassscl*200                                                     ; make some noise\n\nFirst 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.\nPlotting the controller data can be used if you have GNUPLOT installed.\n\nPortamento 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.\n\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 1, November 2024\n- initial version\n\n\n\n\n\n","blueType":"blue.soundObject.Sound","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2024-11-17T18:31:39.000Z"},{"kind":"soundObject","id":44,"name":"Joystick Controller ","description":"\nDESCRIPTION:\n\nThis 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.\nCC number and start/initialization values should be given.\nA name should be entered; this name is used to send the Joystick data globally, i.e. as gkxxxx signal.\nOther, 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.\n\nWhen 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, \nthe SoundObject's length and resolution can be used to scale. \nBe sure to have the Joystick Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Joystick Controller.\n\nJoystick 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. \n\nMost of the time, Joystick Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior.\n\nWhen setting a name as outputfile for recording, the format of the name is as follows:\nNAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION\nlength of SoundObject and resolution are in seconds.\n\nIn the Instrument you want to influence with controller data, here is basic example to add the Smooth Joystick Data Module to the Instrument:\n\n        idevicerange =   1/65536                                                        ; joystickrsolution\n        kmass_scl        scale gkxxxx,        2*imiditotal,  .02*imiditotal             ; scale midi values to usable range and let it influence the .02-2 range\n        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\n        kmassscl        portk    kmass_scl, kPortTime                                   ; range 0.02 - 2\n\n        a1  poscil3 1, kmassscl*200                                                     ; make some noise\n\n\nFirst 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.\nPlotting the controller data can be used if you have GNUPLOT installed.\n\nPortamento 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.\n\nBe 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.\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 1, November 2024\n- initial version","blueType":"blue.soundObject.Sound","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2024-11-17T14:46:52.000Z"},{"kind":"soundObject","id":43,"name":"Midi Controller1","description":"\nDESCRIPTION:\n\nThis 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.\nCC number and start/initialization values should be given.\nA name should be entered; this name is used to send the Midi data globally, i.e. as gkxxxx signal.\nOther, 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.\n\nWhen 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, \nthe SoundObject's length and resolution can be used to scale. \nBe sure to have the Midi Controller on the Timeline above the ScoreObjects of the Instruments you want to influence with the Midi Controller.\n\nMidi 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. \n\nMost of the time, Midi Controller and the ScoreObject make up a pair; moving and scaling them together ensures the expected behavior.\n\nWhen setting a name as outputfile for recording, the format of the name is as follows:\nNAME + LENGTH OF SOUNDOBJECT JOYSTICK CONTROLLER + RESOLUTION\nlength of SoundObject and resolution are in seconds.\n\nIn the Instrument you want to influence with controller data, here is basic example to add to the Instrument:\n\n        imiditotal =   1/128                                                            ; midi rsolution\n        kmass_scl        scale gkxxxx,        2*imiditotal,  .02*imiditotal             ; scale midi values to usable range and let it influence the .02-2 range\n        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\n        kmassscl        portk    kmass_scl, kPortTime                                   ; range 0.02 - 2\n\n        a1  poscil3 1, kmassscl*200                                                     ; make some noise\n\nFirst 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.\nPlotting the controller data can be used if you have GNUPLOT installed.\n\nPortamento 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.\n\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 1, November 2024\n- initial version\n\n\n\n\n\n","blueType":"blue.soundObject.Sound","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2024-11-17T14:46:31.000Z"},{"kind":"instrument","id":291,"name":"TimbreModule","description":"The TimbreModule is intended to be used as an amplitude depending timbre coloring of the incoming signal.\nThe louder (or softer) the amplitude of the incoming, the resonance intensity increases.\n\nIdea is to add some viability to the Instrument.\nChoices are to add some Parametric EQ and/or a Treble cutoff.\n\n---\n\nversion 1, May 2023\n- initial version","blueType":"blue.orchestra.BlueSynthBuilder","categoryName":"Unsorted","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-05-08T18:14:31.000Z"},{"kind":"instrument","id":289,"name":"2Mod4 1/2","description":"\n2Mod4 1/2 consists of 2 Low Frequency Modulators, where Modulator 2 works on Modulator 1. Modulator 2 can be set to OFF. \nSeveral 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. \nAll can be changed in realtime.\nThe 2 Modulators can be mixed and so more complex wave patterns occur.\n\n2Mod4 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.\nAs the phase and out of phase modulators do follow the same modulation values, the out of phase one can get its own offset.\n\nThis Instrument has 4 possible outputs.\n1. ADD             -   both modulators added together, or Modulator1 only\n2. MAX             -   both modulators added together but only the maximal values are given             \n3. MIN             -   both modulators added together but only the minimal values are given \n4. MULT            -   both modulators multiplied. For this to happen, both Modulators needs to be activated.\n\nSome 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\ninside the target instrument must be implemented.\nScaling must be done in the target Instrument.\n\nALL SCALING AND ADDING AN OFFSET TO THE PRODUCED VALUES MUST BE DONE IN THE TARGET INSTRUMENT ITSELF. \n2Mod4 only produces values between -1....1. Any offset or scaling back to values between 0...1 must be done in the target Instr.\n\nTo save CPU, only select the outputs you need!\n\n---\n\nversion 1, April 2023\n- initial version","blueType":"blue.orchestra.BlueSynthBuilder","categoryName":"Unsorted","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-04-26T18:21:06.000Z"},{"kind":"instrument","id":288,"name":"2Mod4 2/2 Module","description":"\nDESCRIPTION:\n\n2Mod4 2/2 Module is the second half of the Modulator system, the other one is called 2Mod4 1/2.\n\nThis Module gets up to 4 modulations at k-rate from 2Mod4 1/2. \n\n- kADDITION, kADDPHASE and iADDPHASE is derived from the ADD channel\n- kMAXIMUM, kMAXPHASE and iMAXPHASE is derived from the MAX channel\n- kMINIMUM, kMINPHASE and iMINPHASE is derived from the MIN channel\n- kMULTIPLY, kMULTIPHASE and iMULTPHASE is derived from the MULT channel\n\nThey are at k-rate, k-rate but inverted phase, and i-rate respectively.\n\nThese modulated signals can be used to manipulate frequencies or amplitudes of the opcodes, or effects like filters in the instrument, and\neverything that you want to modulate.\n\n---\n\nversion 1, April 2023\n- initial version\n\n","blueType":"blue.orchestra.BlueSynthBuilder","categoryName":"Unsorted","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-04-26T18:21:01.000Z"},{"kind":"instrument","id":284,"name":"Stretcher","description":"\nDESCRIPTION:\n\nStretcher is a sampler for mono and stereo samples. \nIt is capable of stretching the sample in realtime. Or plays them in reverse.\nAttention: by activating the filter, also the filter envelope drawings become available.\n\nIn Midi Pitch mode, Midi C4 = normal pitch of sample\nIn Frequency mode, frequency note 8.00 = normal pitch of sample\nAlso, real values can be used.\n\nnote example:\ni2\t0\t0.8\t60\t1.0         ; P4 = midi value, P5 = amplitude\ni2\t0\t0.2\t261.625565\t1.0 ; P4 = frequency, P5 = amplitude\ni2\t0\t0.2\t1   \t1.0         ; P4 = real value, P5 = amplitude\n\nCONTROLLERS:\n\nsee 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.\n\n---\n\nversion 2, February 2023\n- initial version\n\n\n","blueType":"blue.orchestra.BlueSynthBuilder","categoryName":"Sampler","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-02-12T13:04:28.000Z"},{"kind":"soundObject","id":41,"name":"AthenaCL Score generator","description":"\nThe AthenaCL Score Generator is not an easy click and play module.\nAthenaCL 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.\nOne 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.\n\nAthenaCL for python 3 can be found here: https://github.com/ales-tsurko/athenaCL\nBig thanks to Ales Tsurko to have converted it to python 3!\nAnother big thanks goes to Michael Gogins, who implemented 2 seed options: 1 for the TextureModule (creates the structure), 1 for \"the rest\" (ParameterObjects).\nLeaving the seeds open lets the computer decide what sequence is generated, each run a different one but according to the rules.\n\nYou 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\nathenaPipe.py sends the data from the AthenaCL Score Generator to AthenaCL.\n\nEvery 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.\nP2 = BPM. Csound has basic 60 bpm, i use 120 bpm- the AthenaCL default.\nP3 = combination of rhythm, duration and accents. So P2 and P3 work together to produce the final result.\nP4 = 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\n\tbut P4 can be set to other ParameterObjects, like random.  Use the filter to get the values in a useable range\n\nIn AthenaCL, amplitude and panning have their own meaning, but here in the AthenaCL Score Generator these are ommitted.\nUse the TEST button beforehand to check to see if you get the desired results. It is easy to make typing errors...\n\nThe 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: \nWARNING: instr 1 uses 6 p-fields but is given 12\nPerhaps in a future realease this can be improved, but hey- it works....\n\n\n\n\n---\n\nversion 1.4, April 2021\n- seed for TextureModule (TMsd)\n- seed for the rest = ParameterObjects (TPsd)\n\nversion 1.3, March 2021\n- added the 4 x MultiSet option and weighting per Set\n\nversion 1.2 February 2021\n- added Texture Clone with filtering options\n- set original Texture to mute, use only TextureClone output\n\nversion 1.1, february 2021\n- now all pfields >3 can produce the PathRead to freq etc.\n- simplified GUI\n- added help in the balloons\n\nversion 1.0, february 2021\n- initial version by Menno Knevel","blueType":"blue.soundObject.ObjectBuilder","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-01-30T10:21:41.000Z"},{"kind":"soundObject","id":40,"name":"nGen Score Generator2","description":"\nThe 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.\nNot all functions from the main program nGen are integrated, the nGen Score Generator.\n\nAs 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.\n\nshort manual:\n- choose desired number of events to generate\n- set number of  pfields accordingly with the P field slider\n- to the left of the P field slider, set Dropdown menu of all p-fields used to 'on'\n- left upper corner, set global random seed value; every seed produces a unique sequence (values between 0 and 65536)\n- 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.\n- check if the right values are used by pressing TEST\n- up to 15 p fields can be generated\n\n\nUnlike the nGen program itself, the nGen generator is momentarily unable to process:\n- macro's\n- include files\n- if / endif statements\n- 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.\njust work with ftgen inside the instrument to bypass this issue.\n\n------------\n\nversion 1.1, February 2021\n- extended Tempo options with Tempo types\n- added second data inputs\n- added sampling rate option for FFT use\n\nversion1, August 2020\n- initial version by Menno Knevel","blueType":"blue.soundObject.ObjectBuilder","categoryName":"General","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-01-28T11:01:51.000Z"},{"kind":"effect","id":328,"name":"StereoXpansion","description":"\nDESCRIPTION:\n\nStereoXpansion first creates a MS stereo signal; the mono signal in the middle of the stereo field (M) is separated from the stereo information (S).\nThen this MS stereo signal is converted back to stereo with the option of manipulating the stereo information.\n\n---\n\nversion 1.0, Januari 2023\n- initial version by Menno Knevel","blueType":null,"categoryName":"Spatial","authorName":"Menno0","authorUsername":"menno0","createdAt":"2023-01-09T11:59:28.000Z"}]