I started thinking deeply about what I wanted max to detect. Did I want it to detect the x and y axis as previously mentioned? Did I wish to have the limitations of a set length of the card's x axis?
While researching and consulting peers and previous lecturers who had worked in this field before, I was pleasantly surprised that many patches existed, ready to be modified, in the world of motion detection, which worked for an infinite length of time not relying on my x axis = time idea.
One that I was recommended and found easy to modify was "VideoTrigger" by Jach Proff. An open-source max match designed to detect zones and output based on movement.
Installing Macam webcam drivers allowed the Alleged MacOS native webcam to actually be detected by the system, and in turn MaxMSP.
First experiments with this were successful, however, the software was relatively limited in terms of allowing files to continuously play. After delving into its patch, I realised it used a simple "sfplay" to trigger samples.
On my version of the software (1.01) I couldn't find the ability to "loop" - so added a prepend loop to the sfplay module:
And, after careful adjusting of the brightness, contrast and colour saturation of the webcam in the input settings to be able to fully see a contrasted and clear image of a sketch;
I set about placing "zones" to match the layout of the cards when slotted in, as well as randomly placed ones.
Through calibrating the software in terms of sensitivity and causing an "end on exit" setting to occur on all "zones" - I was able to ensure that once the card was removed from the box, the sounds would stop.
My intentions were to put together a simple and effective system that any user could use, and as a result I opted for 6 motion detection zones, all calibrated to be looking at a single white background. once the system detected the "movement" of the black lines on the sketches, the triggers would playback samples based on when it saw those lines.
No comments:
Post a Comment