A given 3D space with a colony of virtual bees (little spheres variable quantity 10.000/50.000).
Sensordata - audio, video, environmental data inside/outside the hive - are all time-stretched to have regular time segments.
E.g. environmental data values are every 10 seconds ⇒ these are timestretched to fit the audio and video which is at 24 fps.
All data are converted to txt (cvs).
Different parameters (temperature, humidity and hours of sunlight or rain, but also the frequencies and amplitudes of the soundfiles, the amount of action (bees) in the video files) will act as strange attractors in the 3D space and they will influence the behaviour of the virtual bee colony (bee-blob) in space.
Monday 12/1/15 we start the analyses. We first work with the frequency and the amplitude of the soundfiles. In Maxmsp we analyse the files on their brightness, loudness and noisiness. We add a bandpassfilter on the files of the electret microphones, as there are plenty of disturbing external noises around the beehive (people talking, birds singing, wind, …). Than we take only 1 minute of the file (instead of 3 minutes), that way we can eliminate the sound of the churchbell's of Ste Catherine (every hour!).
Once the soundfiles are analysed, they are exported in a logfile in cvs-format, similar to the logs of the sensor-data. The time-interval of the sensordata is once every 15 minutes (for temperature and humidity inside the beehive, as well as for the environmental temperature, humidity, lightconditions). The consecutive values are stretched and interpolated every 15 minutes. Thus the final storage of sound and sensorinformation has a similar time-format.
The analysis of the video files is done with motion detection (frame difference method - motion-detection.pdf). The analysis is based on frame difference. The first frame is captured through the static camera and after that sequence of frames is captured at regular intervals. Secondly, the absolute difference is calculated between the consecutive frames and the difference image is stored in the system. Thirdly, the difference image is converted into gray image and then translated into binary image. Finally, morphological filtering is done to remove noise.
Thus, over 10 images there is a frame-information substraction between the consecutive images. The results of this substractions are added up after the 10th frame and displayed in a new window. The noise is filtered out of the frame.
The information read in the first analysis display and the info from the 4th display are both rendered in a graph and exported in cvs-format.
The cvs-files of the 8 audio/microphones (3 lists per channel: brightness, loudness and noisiness) gives us 24 possible parameters. The video-file analysis is limited for the moment to light/brightness and motion. Later we will add the minimum color and the average color of the image as an extra parameter.
The environmental sensors give the values of temperature, humidity and hours of sunlight, as well as the temperature and the humidity inside the beehives.
All added up this gives us plenty of parameters to combine and to play with, and to create a virtual bee-blob moving and changing by these strange attractors-parameters.
We started to build the interface for visualisation. It is not easy.
First we had normalised all data to the .cvs format. Than, we tried to normalize the data in time. E.g.: sound has continuous data for 3 minutes, 4 x per hour. Temp. sensors take data every 10 minutes, video is continuous for 3 minutes 4 x/hour, …
The first patch in MaxMSP shows that the lists with values are far too long. We simplify. For sound and video, we take only 1 minute instead of 3 minutes/file. Than, we make an average of 10 values - so we reduce the figures with :10.
The environmental sensordata (temp. &hum. ,solar radiation, …) are extended to the same format.
So finally we have regular values, and for all parameters the same format.
Now we have to introduce these parameter values into the MaxMSP-patch. The values are attributed to the attractor-engines. They define a stronger or weaker strength, which makes the blob of the spheres move in the 3D-space.
We started with a blob of 300 spheres (representing the bees). 300 is a limit for the Max-patch when run on a Mac PowerBook. We try to increase the number up to 500 spheres, but this makes the patch crash.
We make the data run in a first time for a while with different parameters and make some test-movies.
VLC-bees in 3D and red
We started to work on the camera images of the Sound Beehive, version 2015. The camera frames as well the 8 frames of the beehive on which the bees will build out the new comb - at the same time the camera also frames the IN/OUT portal (in plexiglass) through which the bees leave and come back into the beehive. With these images we will make a bee counter.
Hive activity on the first summer day, 10.04.2015, 20°
Left, the broodbox filmed from bottom-up - right, the entrance with the beecounter.
We are filming the nest from bottom-up at 2fps. This makes a movie of 2 minutes every hour, or 48 minutes/day (played at 60fps). Once we have a lot of time, we will make a concatenated movie out of all fragments.
All day we leave and arrive at the hive,
concelebrants. The hive is love,
what we serve, preserve, avowed in Latin murmurs
as we come and go, skydive, freighted
with light, to where we thrive, us, in time's hum,
on history's breath,
industrious, incidental …
there suck we,
alchemical, nectar-slurred, pollen furred,
the world's mantra us, our blurry sound
along the thousand scented miles to the hive,
haven, where we unpack our foragers;
or haven-stare, drone-eyed, for a queen's star;
or nurse or build in milky, waxy caves,
the hive, alive, us - how we behave.
—– The Bees (hive), Carol Ann Duffy, 2011
tests, patches for visualisations movies -2015 04 13/14/15
finally, some results for the data visualisation
After analysis (by Guy De Bièvre) of the recorded soundfiles (2014 project), the conclusion is that there is a bad electrical hum (50Hz and the first harmonic 100Hz) dominating. This probably caused by a power supply somewhere along the line (can be in the hive, but could also be inside near the mixing desk). Best would be to get rid of it physically (finding the guilty source and moving it away from the microphone cables). Another solution (even better if you can combine it with removing the source of the problem) is to shorten the microphone cables by adding a preamp near/in the hive and to start from there on line level, preferably symmetric…simplest way to do that is to get a small mixing desk and set it up near/in the hive and leave from there with a balanced output (a balanced/symmetric output protects from outside interferences).
If you cannot solve this issue physically you should add a 50Hz comb filter patch to the software setup (a 50Hz comb filter will radically/steeply cut out 50Hz and all of its harmonics (100, 150, 200, 250, etc…))…although, when I run the files through a spectrum analyzer I only see the first harmonic (100Hz) clearly, then a much weaker 3rd (150Hz) and a slightly stronger 4th (200Hz), so it should suffice to kill 50, 100, 150 and 200, no need to go above that. (this strongly reduces it, but does not get rid of it altogether, except for the weaker 150 and 200.)
I will add screen dumps (to the upload) of the spectrum analyzer, before and after filtering…the hum are those continuous equidistant lines. I ran the the 4 files you gave me through a FFT 50Hz removal (most software has 50Hz removal presets, because it is such a common issue, though US software will have a, for us useless, 60Hz filter), getting rid of most of the hum and a hi-pass reducing everything below 70Hz, to get rid of the “city” (on one of the samples there is a sound that most likely comes from a car stereo, which is harder to get rid of.)
Analysis & synthesis by Givan Bela: Bees along the WatchTower
Beewatch-T8 is a spectral remapping, with a fast and layered but vectorized kind of sample and hold technique based on estimated pitches sliding one into another, imagining another world, if you think of the fact that bees maybe don’t hear themselves buzzing, and hissing, or whirring, but that they’d rather feel the vibrations in rich sonic patterns all around telling them … (eight track generator and max-msp patch: gívan belá z hranic - 20150720)
audacity 8-track screenshot
Analysis & synthesis by Bill Bultheel: Sound Bees
The beehive recordings pan over the spectrum of a day (from midnight to midnight). As a compositional principle different ideas around swarm formation were investigated.
The increase and decrease of swarm activity in the hive and its influence on its sound, became a guideline for the transformation of the recordings. Hereby using natural phenomena as musical tools and in retrospect, using musical tools as an artistic rendition or analysis for natural phenomena.
The audio work tries to embody the bee swarm while simultaneously intersecting the swarm with swirling electronic sound clusters.
audacity 8-track screenshot
It may be a good idea to start to look at a subset of the recordings. It would be interesting to look at the relation between airplane noise (clearly audible on the recordings) and any behavioral changes of the bees.
Aircraft noise detection itself is a highly non-trivial topic - in attachment two papers that can be used a starting point to explore the literature. Detecting the presence of aircraft noise and correlating it with bee behavior will be an interesting challenge.
Real-time aircraft noise likeness detector
Real time aircraft fly-over noise discrimination
canaroute over the rooftop garden and apiary of the Brussels Urban Bee Lab
sound beehive (warré)
intelligent beehive (warré)
beehive 1 (kempische)
8768, 8769, 8770, 8771, 8772, 8773
beehive 2 (kempische)
temperature and humidity Forest Garden
air temperature: http://opensensordata.net/datastreams/8879.csv
air humidity: http://opensensordata.net/datastreams/8880.csv
soit temperature: http://opensensordata.net/datastreams/8881.csv
soil humidity: http://opensensordata.net/datastreams/8882.csv
solar radiation: http://opensensordata.net/datastreams/8883.csv
leaf humidity: http://opensensordata.net/datastreams/8884.csv