fluid buf multithread guide typo corrections

release-packaging/HelpSource/Guides/FluidBufMultiThreading.schelp

@@ -4,7 +4,7 @@ CATEGORIES:: Libraries>FluidDecomposition
 RELATED:: Guides/FluCoMa, Guides/FluidDecomposition
 
 DESCRIPTION::
-The Fluid Decomposition toolbox footnote::This toolbox was made possible thanks to the FluCoMa project ( http://www.flucoma.org/ ) funded by the European Research Council ( https://erc.europa.eu/ ) under the European Union’s Horizon 2020 research and innovation programme (grant agreement No 725899).:: provides an open-ended, loosely coupled set of objects to break up and analyse sound in terms of slices (segments in time), layers (superositions in time and frequency) and objects (configurable or discoverable patterns in sound). Almost all objects have audio-rate and buffer-based versions.
+The Fluid Decomposition toolbox footnote::This toolbox was made possible thanks to the FluCoMa project ( http://www.flucoma.org/ ) funded by the European Research Council ( https://erc.europa.eu/ ) under the European Union’s Horizon 2020 research and innovation programme (grant agreement No 725899).:: provides an open-ended, loosely coupled set of objects to break up and analyse sound in terms of slices (segments in time), layers (superpositions in time and frequency) and objects (configurable or discoverable patterns in sound). Almost all objects have audio-rate and buffer-based versions.
 
     These latter buffer-based processes can be very CPU intensive, and so require a some consideration of SuperCollider's underlying architecture. The FluidBuf* objects have different entry points, from transparent usage to more advanced control, to allow the creative coder to care as much as they need to. The overarching principle is to send the CPU intensive tasks to their own background thread, to avoid blocking the Server and its Non-Real Time thread, whilst providing ways to cancel the tasks and monitor their progress.
 
@@ -101,20 +101,27 @@ f.free
 //to appreciate the multithreading, use your favourite CPU monitoring application. scsynth will be very, very high, despite the peakCPU and avgCPU being very low.
 ::
 
-subsection:: Ding, Fries are Done
+subsection:: Monitoring Task Completion
 
     There are a couple of options for dealing with the end of a job. First, the FluidBuf* objects support done actions, so you can use things like LINK::Classes/FreeSelfWhenDone:: or LINK::Classes/Done::, or set a doneAction in the call to .kr (see LINK::Classes/Done:: for details). Note that the UGen's done status only becomes true in the event of successful completion, so it will not catch cancellation. However, the doneAction will run whatever, so you can rely on the synth freeing itself.
 
     Alternatively, the synth will send a /done reply to the node, which also carries information about whether it completed normally or was cancelled. You can use LINK::Classes/OSCFunc:: to listen for this message, targetted to your nodeID.
 
 CODE::
-a = {FluidBufThreadDemo.kr(b,1000,doneAction: 2).poll}.play;
+// define a destination buffer
+b=Buffer.alloc(s,1);
+
+//start a long job
+a = {FluidBufThreadDemo.kr(b,10000,doneAction: 2).poll}.play;
 
+// set a OSC receiver function
+(
 OSCFunc({|msg| //args are message symbol (/done), nodeID and replyID (which gives status)
         if(msg[2]==0){"Completed Normally".postln}{"Cancelled".postln};
     },"/done",argTemplate:[a.nodeID]).oneShot; //only listen to things sent for this node
+)
 
-a.free; //optionally cancel
+a.free; //optionally cancel - run the job twice to see both behaviour monitored by the OSCFunc above
 ::
 
 

release-packaging/HelpSource/Guides/FluidDecomposition.schelp

@@ -3,7 +3,7 @@ SUMMARY:: An overview of the FluCoMa toolbox for signal decomposition
 CATEGORIES:: Libraries>FluidDecomposition
 
 DESCRIPTION::
-The Fluid Decomposition toolbox provides an open-ended, loosely coupled set of objects to break up and analyse sound in terms of slices (segments in time), layers (superositions in time and frequency) and objects (configurable or discoverable patterns in sound). Almost all objects have audio-rate and buffer-based versions. footnote::
+The Fluid Decomposition toolbox provides an open-ended, loosely coupled set of objects to break up and analyse sound in terms of slices (segments in time), layers (superpositions in time and frequency) and objects (configurable or discoverable patterns in sound). Almost all objects have audio-rate and buffer-based versions. footnote::
 This toolbox was made possible thanks to the FluCoMa project ( http://www.flucoma.org/ ) funded by the European Research Council ( https://erc.europa.eu/ ) under the European Union’s Horizon 2020 research and innovation programme (grant agreement No 725899).::
 
 subsection:: Slices
@@ -87,4 +87,4 @@ Copy, slice, stack, mix concatenate. All the things you've wanted to do with buf
 
 LINK:: Classes/FluidBufThreadDemo::
 
-A tutorial object to experiment with multithreading in FluidBuf* objects
+A tutorial object to experiment with multithreading in FluidBuf* objects