// here we instantiate a process of description and dataset writing, which will run each slice of the previous slice and write the entry. Note the chain of Done.kr triggers.
~norm.dump({|x|x["data_min"][[8,12]].postln;x["data_max"][[8,12]].postln;})//here we extract the stats from the dataset by retrieving the stored maxima of the fitting process in FluidNormalize
~norm.dump({|x|x["data_min"][[8,12]].postln;x["data_max"][[8,12]].postln;})//here we extract the stats from the dataset by retrieving the stored maxima of the fitting process in FluidNormalize
A server-side container associating labels with multi-dimensional data.
A server-side container associating string identifiers with multi-dimensional data.
CLASSMETHODS::
@ -25,25 +25,25 @@ PRIVATE:: init,id,cache
METHOD:: addPoint
Add a new point to the data set. The dimensionality of the DataSet is governed by the size of the first point added.
Will report an error if the label already exists, or if the size of the data does not match the dimensionality of the DataSet.
ARGUMENT:: label
A symbol or string with the label for the new point.
Will report an error if the identifier already exists, or if the size of the data does not match the dimensionality of the DataSet.
ARGUMENT:: identifier
A symbol or string with the identifier for the new point.
ARGUMENT:: buffer
A link::Classes/Buffer:: with the new data point.
ARGUMENT:: action
A function to run when the point has been added.
METHOD:: updatePoint
Update an existing label's data. Will report an error if the label doesn't exist, or if the size of the data does not match the given dimensionality of the DataSet.
Update an existing identifier's data. Will report an error if the identifier doesn't exist, or if the size of the data does not match the given dimensionality of the DataSet.
METHOD:: getPoint
Retrieve a point from the data set into a link::Classes/Buffer::. Will report an error if the label or buffer doesn't exist.
Retrieve a point from the data set into a link::Classes/Buffer::. Will report an error if the identifier or buffer doesn't exist.
METHOD:: deletePoint
Remove a point from the data set. Will report an error if the label doesn't exist.
Remove a point from the data set. Will report an error if the identifier doesn't exist.
METHOD:: setPoint
Set the point: if the label exists, this method behaves like updatePoint; if the label doesn't exist, behaves like addPoint.
Set the point: if the identifier exists, this method behaves like updatePoint; if the identifier doesn't exist, behaves like addPoint.
METHOD:: clear
Empty the data set.
@ -88,7 +88,7 @@ ARGUMENT:: action
A function to run when the export is done.
METHOD:: merge
Merge sourceDataSet in the current DataSet. It will update the value of points with the same label if overwrite is set to 1. To add columns instead, see the 'transformJoin' method of link::Classes/FluidDataSetQuery::
Merge sourceDataSet in the current DataSet. It will update the value of points with the same identifier if overwrite is set to 1. To add columns instead, see the 'transformJoin' method of link::Classes/FluidDataSetQuery::
METHOD:: free
Destroy the object on the server.
@ -108,7 +108,7 @@ EXAMPLES::
CODE::
// Create a simple a one-dimensional data set, three ways
// Using routine
s.boot;
s.reboot;
(
fork{
~ds = FluidDataSet.new(s);
@ -204,7 +204,7 @@ code::
~dsB = FluidDataSet.new(s);
)
//feed them items with same dimensions but different labels
//feed them items with same dimensions but different identifiers
Apply the query to a source link::Classes/FluidDataSet:: and join the resulting subset at the end of the items sharing the same labels in a second source. Items unique to a source dataset will be ignored. To add items at the end of a dataset instead, see the 'merge' method of link::Classes/FluidDataSet::
Apply the query to a source link::Classes/FluidDataSet:: and join the resulting subset at the end of the items sharing the same identifiers in a second source. Items unique to a source dataset will be ignored. To add items at the end of a dataset instead, see the 'merge' method of link::Classes/FluidDataSet::
ARGUMENT:: source1DataSet
Source data, or the DataSet name
ARGUMENT:: source2DataSet
@ -108,7 +108,7 @@ EXAMPLES::
code::
s.reboot;
// Create a DataSet with random data
// Create a DataSet with known data
~dataSet= FluidDataSet(s);
(
@ -126,7 +126,7 @@ fork{
}
)
//check the source
//check the source - the column is the integer part of the value, and the row is the fractional part. This will help us identify what we kept in our didactic query
~dataSet.print;
// Prepare a FluidDataSetQuery object
@ -157,7 +157,7 @@ fork{
STRONG:: Joining Datasets::
code::
//this is how to join 2 datasets, adding columns to items with the same label
//this is how to join 2 datasets, adding columns to items with the same identifier
//create 3 datasets
(
~dsA = FluidDataSet(s);
@ -165,13 +165,13 @@ code::
~dsC = FluidDataSet(s);
)
//feed them items with almost overlaping label lists but with different dimensions
//feed them items with almost overlaping identifier lists but with different dimensions
A UGen that adds labelled points to a link::Classes/FluidDataSet:: Internally, this calls code::setPoint::, so IDs that already exist will be overwritten, and new IDs will be added. The actual work is done on the server's command queue, rather than the real-thread.
By default the object takes a control input (code::idNumber::) as a numerical index that gets used for the point labels. This index is used to write each time the Ugen is re-triggered with a zero to non-zero transition. The label is then concatenated with the code::idPrefix:: symbol, which is fixed at instantiation. In this way, one can make custom, incrementing labels, e.g.
By default the object takes a control input (code::idNumber::) as a numerical index that gets used for the point identifiers. This index is used to write each time the Ugen is re-triggered with a zero to non-zero transition. The identifier is then concatenated with the code::idPrefix:: symbol, which is fixed at instantiation. In this way, one can make custom, incrementing identifiers, e.g.
An instance of link::Classes/FluidDataSet:: or an instance's name.
ARGUMENT:: idPrefix
A string or symbol with a prefix for generated labels.
A string or symbol with a prefix for generated identifiers.
ARGUMENT:: idNumber
ANCHOR::offset::
An integer with the offset to start labeling from. If the UGen is run in a server-side loop (i.e. repeatedly re-triggered), the generated labels will count upwards from this offset. If nil, then no numerical index will be applied to the generated label (i.e. only the labelPrefix is used).
An integer with the offset to start labeling from. If the UGen is run in a server-side loop (i.e. repeatedly re-triggered), the generated identifiers will count upwards from this offset. If nil, then no numerical index will be applied to the generated identifier (i.e. only the idPrefix is used).
ARGUMENT:: buf
The link::Classes/Buffer:: containing the data point.
@ -48,6 +48,8 @@ EXAMPLES::
code::
s.reboot;
//make a dataset
~ds = FluidDataSet(s);
// write a single point, no counting
@ -58,9 +60,8 @@ s.reboot;
}.play(s);
)
//look
~ds.print;
~ds.clear
//Write a 100 points quite fast with server-side triggering
(
@ -81,8 +82,7 @@ OSCFunc({
}.play(s,args:[n:100]);
)
~ds.print;
~ds.clear
//it printed with the return function
//Again, but as fast as possible using a feedback of the trigger we are given when the writing is done
(
@ -104,10 +104,9 @@ OSCFunc({
}.play(s,args:[n:100]);
)
~ds.print;
// incremental buffer writing - sky is the limit
~ds.clear
// incremental buffer writing - sky is the limit
// start the entry maker, trigging twice a second
(
{
@ -125,10 +124,14 @@ OSCFunc({
//print a few times
~ds.print;
//clear before flushing the writing synth
//clear before flushing the writing synth and the process keeps on going
~ds.clear
~ds.print;
//command-period to stop it
~ds.print;
~ds.clear
// circular writing
(
{
@ -143,6 +146,7 @@ OSCFunc({
}.play(s);
)
//print regularly to see a specific identifier being overwritten
A function that determines how the chunks in the index are labelled; default is file name without path.
ARGUMENT:: channelFunc
@ -26,7 +26,7 @@ INSTANCEMETHODS::
METHOD:: index
A link::Classes/IdentityDictionary:: containing the metadata on the loaded files
The keys of this dictionary are the labels produced by the code::labelFunc:: passed to link::Classes/FluidLoadFolder#*new:: (or the default of the filename if nil). The value for each key is a further dictionary consisting of:
The keys of this dictionary are the identifiers produced by the code::idFunc:: passed to link::Classes/FluidLoadFolder#*new:: (or the default of the filename if nil). The value for each key is a further dictionary consisting of:
definitionlist::
## bounds
@ -67,9 +67,9 @@ s.reboot;
~loader.play(s,action:{ |dataDictionary|
("Done loading into" + ~loader.buffer).postln;
//we get passed an IdentityDictionary of slice data, let's look at it
|| anchor::datadict:: An link::Classes/Association:: of the label for this segment, with an link::Classes/IdentityDictionary:: of useful extra data:
|| anchor::datadict:: An link::Classes/Association:: of the identifier for this segment, with an link::Classes/IdentityDictionary:: of useful extra data:
The source link::Classes/Buffer:: containing the audio to process
ARGUMENT:: bufIdx
An link::Classes/IdentityDictionary:: specifying labels, boundaries, sample rate and channel count for the segment. See link::Classes/FluidLoadFolder#-index:: for details.
An link::Classes/IdentityDictionary:: specifying identifiers, boundaries, sample rate and channel count for the segment. See link::Classes/FluidLoadFolder#-index:: for details.
ARGUMENT:: action
A function to run when processing is complete. This gets passed the same link::Classes/Association:: as link::#datadict#the processing function::
Override the default labelling behaviour for slices. The default is to append the original label with code::-<slice number>:: counting from 1.
Override the default labelling behaviour for slices. The default is to append the original identifier with code::-<slice number>:: counting from 1.
INSTANCEMETHODS::
@ -68,7 +68,7 @@ The link::Classes/Buffer:: containing the audio to slice
ARGUMENT:: bufIdx
ANCHOR::indexformat::
An link::Classes/IdentityDictionary:: that details labels and start-end positions for each chunk in the source buffer. See link::Classes/FluidLoadFolder#index::
An link::Classes/IdentityDictionary:: that details identifiers and start-end positions for each chunk in the source buffer. See link::Classes/FluidLoadFolder#index::
ARGUMENT:: action
A function that runs on complettion, will be passed the link::Classes/IdentityDictionary:: from link::#index:: as an argument.
@ -78,7 +78,7 @@ ANCHOR::ntasks::
The number of parallel processing tasks to run on the server. Default 4. This should probably never be greater than the number of available CPU cores.
METHOD:: index
A link::Classes/IdentityDictionary:: containing information about the position of each discovered slice, using labels based on those passed into link::#play:: (see link::#labelling::). This dictionary copies all other entries from the source dictionary on a per-key basis (so you can store arbitary stuff in there should you wish, and it will remain oassciated with its original source chunk).
A link::Classes/IdentityDictionary:: containing information about the position of each discovered slice, using identifiers based on those passed into link::#play:: (see link::#labelling::). This dictionary copies all other entries from the source dictionary on a per-key basis (so you can store arbitary stuff in there should you wish, and it will remain assciated with its original source chunk).
Pierre Alexandre Tremblay
4 years ago