Here's a vid of the first Arduino working.
Wednesday, August 29, 2007
Monday, August 27, 2007
Final Report Submitted (Softbound) Fri Aug 24th
Final softboard report submitted on Friday, available at below link.
http://richie.idc.ul.ie/%7EHackettc/Thesis/MultimbaReport.pdf
Any suggested changes will be incorporated into hardbound report, due Sept 28th.
http://richie.idc.ul.ie/%7EHackettc/Thesis/MultimbaReport.pdf
Any suggested changes will be incorporated into hardbound report, due Sept 28th.
Wednesday, August 22, 2007
Meeting with Luigina Ciolfi - Aug 22nd (Evaluation)
Today we met with Luigina to sponge off her excellent skills and knowledge in evaluation techniques.
During the course of study, we were mainly focused on evaluating systems with user interfaces, usually GUI's. We knew that the same sort of techniques would not necessarily apply to our project. Before speakimg to Lui we were looking at undertaking a heuristic evaluation (evaluating the prototype with a number of chosen experts, based on set design principle criteria).
Lui advised that Heuristic Evaluation applies essentially to user interfaces, and that our instrument prototype bares no relationship to the type of criteria involved.
As our project is very much exploratory, it would be best to take a loose informal approach. The following approach suggested by Lui would be best:
*Choose 5 to 6 test subjects, that fit our various user profiles.
*Conduct an informal walkthrough of the prototype, showing it's various functionalities.
*Prepare a number of questions that search for what we need to find out. i.e. How do you feel these functions are an improvement on existing instruments?
*Maintain an informal discussion, dropping subtle hints that keep the feedback on course.
*Don't dwell on information that not important for what we need to know.
*Document techniques, notetaking, dictaphone, video.
*Stay away from questionnaires!
Lui advised that this can be conducted after aug 24th if prototype isn't ready.
She recommended however, that we document, what, why, who and how we want to evaluate.
Thanks Lui
During the course of study, we were mainly focused on evaluating systems with user interfaces, usually GUI's. We knew that the same sort of techniques would not necessarily apply to our project. Before speakimg to Lui we were looking at undertaking a heuristic evaluation (evaluating the prototype with a number of chosen experts, based on set design principle criteria).
Lui advised that Heuristic Evaluation applies essentially to user interfaces, and that our instrument prototype bares no relationship to the type of criteria involved.
As our project is very much exploratory, it would be best to take a loose informal approach. The following approach suggested by Lui would be best:
*Choose 5 to 6 test subjects, that fit our various user profiles.
*Conduct an informal walkthrough of the prototype, showing it's various functionalities.
*Prepare a number of questions that search for what we need to find out. i.e. How do you feel these functions are an improvement on existing instruments?
*Maintain an informal discussion, dropping subtle hints that keep the feedback on course.
*Don't dwell on information that not important for what we need to know.
*Document techniques, notetaking, dictaphone, video.
*Stay away from questionnaires!
Lui advised that this can be conducted after aug 24th if prototype isn't ready.
She recommended however, that we document, what, why, who and how we want to evaluate.
Thanks Lui
Meeting with Annette Aboulafia - Aug 14th
Annette Aboulafia, researcher in the IDC, kindly proof read our draft report for us. Afterwards we met to discuss it.
Annette helped us to clearly define our aims and objectives. Although we know them, it's not always easy to explain them to other people. We also learned that it's important to know the scope of the project. For example, is the prototype a learning device? Answer: No.
In terms of the report, she offered the following suggestions.
*Begin the Introduction chapter with an introductions to the field of study.
*Give a brief description of each project member's background and interests.
*Give an introduction to the research section. i.e. research questions, what we researched and why.
Thanks Annette!
Annette helped us to clearly define our aims and objectives. Although we know them, it's not always easy to explain them to other people. We also learned that it's important to know the scope of the project. For example, is the prototype a learning device? Answer: No.
In terms of the report, she offered the following suggestions.
*Begin the Introduction chapter with an introductions to the field of study.
*Give a brief description of each project member's background and interests.
*Give an introduction to the research section. i.e. research questions, what we researched and why.
Thanks Annette!
Physical Prototype Complete!
After a couple of weeks of liasing with an expert carpenter, the physical prototype is complete, alomost exactly to spec!
The box measures 1000mm (length) x 300mm (width) x 100mm (depth).
The top and bottom of the box, and the instrument board is 100mm wide plywood.
The sides are 200mm white deal.
It is coated with a matt black finish.
Open, the instrument looks like this.
The instrument board that sits inside measures 800mm x 280mm.
Underneath the board lies 4 arduino boards and their cables.
Placed on the board are 24 sensors.
A 5mm holes was drilled through the board for each sensor's wires.
Each hole was placed 65mm apart, and the side holes were placed 57mm from the edge.
They then had to be countersunk with a 10mm drill bit to accommodate the solder underneath each sensor.
A white sticker is placed over each sensor.
Finally a 16mm hole was placed at the back of the box to accommodate the usb cables.
The box measures 1000mm (length) x 300mm (width) x 100mm (depth).
The top and bottom of the box, and the instrument board is 100mm wide plywood.
The sides are 200mm white deal.
It is coated with a matt black finish.
Open, the instrument looks like this.
The instrument board that sits inside measures 800mm x 280mm.
Underneath the board lies 4 arduino boards and their cables.
Placed on the board are 24 sensors.
A 5mm holes was drilled through the board for each sensor's wires.
Each hole was placed 65mm apart, and the side holes were placed 57mm from the edge.
They then had to be countersunk with a 10mm drill bit to accommodate the solder underneath each sensor.
A white sticker is placed over each sensor.
Finally a 16mm hole was placed at the back of the box to accommodate the usb cables.
Monday, August 20, 2007
Having fun - Marimba Solo
This is what happens when the first 6 notes are left open in max/msp.
Sounds like someone is actually playing a marimba solo. Pretty cool!
Sounds like someone is actually playing a marimba solo. Pretty cool!
Thursday, August 9, 2007
Meeting with Mikael 7th August
On Aug 7th we met with Mikael to discuss the progress of our prototype. We gave him a quick demo and identified difficulties and further work.
The main points of the meeting were as follows:
- On subject of Threshold and its inconsistency, Mikael suggested that we try and retrigger the condition in Arduino code rather than Max/Msp.
Or possibly try to induce "Temporal Hysteresis" (needed when there is wide signal variations, such as smacking a marimba mallet at various velocities)
-Mikael suggested we try to improve bouncing of sound on the Arduino code side.
-In addition to this, Mikael suggested affixing a 10 nK (nanoFarads) CAPACITOR to the resistor and Piezo wire in order to take out the high frequencies. this effectively acts as a low pass filter for the signal.
-finally, as opposed to using static wav/aif files as sounds, the other future option is to develop sound models, Putting an ADSR envelope (ATTACK DECAY SUSTAIN RELEASE) is a useful approximation of the volume of REAL instrument (but not always a substitute)
-We were also encouraged to use pd rather than max/msp, as it is open source.
ls dev in a mac terminal tell what serial port is being occupied. This will hopefully fix connectivity problem with PD
The main points of the meeting were as follows:
- On subject of Threshold and its inconsistency, Mikael suggested that we try and retrigger the condition in Arduino code rather than Max/Msp.
Or possibly try to induce "Temporal Hysteresis" (needed when there is wide signal variations, such as smacking a marimba mallet at various velocities)
-Mikael suggested we try to improve bouncing of sound on the Arduino code side.
-In addition to this, Mikael suggested affixing a 10 nK (nanoFarads) CAPACITOR to the resistor and Piezo wire in order to take out the high frequencies. this effectively acts as a low pass filter for the signal.
-finally, as opposed to using static wav/aif files as sounds, the other future option is to develop sound models, Putting an ADSR envelope (ATTACK DECAY SUSTAIN RELEASE) is a useful approximation of the volume of REAL instrument (but not always a substitute)
-We were also encouraged to use pd rather than max/msp, as it is open source.
ls dev in a mac terminal tell what serial port is being occupied. This will hopefully fix connectivity problem with PD
Wednesday, August 1, 2007
September Examination and Exhibition
August 27-31
Build and prepare for examination and exhibition.
September 3, Monday
Examination of MusicTech students
In the evening, Official opening of Digital Arts Week Now 2007
Music Tech concert.
September 4, Tuesday
Examination of MusicTech students
DAWN exhibition open to the public
September 5, Wednesday
Examination of Imedia students
DAWN exhibition open to the public
September 6, Thursday
Examination of Imedia students
DAWN exhibition open to the public
September 7, Friday
DAWN exhibition open to the public
Closing of exhibition and take-down.
Build and prepare for examination and exhibition.
September 3, Monday
Examination of MusicTech students
In the evening, Official opening of Digital Arts Week Now 2007
Music Tech concert.
September 4, Tuesday
Examination of MusicTech students
DAWN exhibition open to the public
September 5, Wednesday
Examination of Imedia students
DAWN exhibition open to the public
September 6, Thursday
Examination of Imedia students
DAWN exhibition open to the public
September 7, Friday
DAWN exhibition open to the public
Closing of exhibition and take-down.
Subscribe to:
Posts (Atom)
