Pedro Lopes, Ricardo Jota, Joaquim Jorge
[Published at ACM ITS 2011, Kobe, Japan / paper]
Recognizing how a person actually touches a surface has generated a strong interest within the interactive surfaces community. Although we agree that touch is the main source of information, unless other cues are accounted for, user intention might not be accurately recognized. We propose to expand the expressiveness of touch interfaces by augmenting touch with acoustic sensing. In our vision, users can naturally express different actions by touching the surface with different body parts, such as ﬁngers, knuckles, ﬁngernails, punches, and so forth – not always distinguishable by touch technologies but recognized by acoustic sensing. Our contribution is the integration of touch and sound to expand the input language of surface interaction.
Update: some media coverage on the press [Portuguese press / Exame Informática]
Multitouch Djing: Loading Objects via XML from PedroLopes on Vimeo.
This is just showing the Objects in the interface being XML defined, that can be read at start up and create the patch for the DJ.
This will allow users of the interface to share patches, save, load, etc…
Prototype Flash and PureData #3 from PedroLopes on Vimeo.
This video shows a small-tiny-atom-sized prototype that uses Pd (PureData) and Flex/ActionScript compiled on Win (XP) with only the Open Source Flex SDK.
The only reason for not deploying it in Ubuntu is that flashserver external pd object is not present. I will replace it with OSC and probably use oscx external.
The PureData side is just a small patch that mixes a loop (a funny beat 80’s sample…ta nan…) with a sine wave. To simplify auditive debugging.
Notice that all communication between Pd Flash is all done remotely via Sockets.
The Architecture has now some classes and modules, the turntable mock-up objects that you see inherit from the base InterfaceObject Class. More on this soon…
The default way to log is using Trace(“something”), this sends a print message to the console of your flash IDE (mine is Eclipse). Although other alternatives can bring you better results, and don’t need to launch your project in debug mode! Here’s my top two choices:
Vizzi allows you to see various settings such as the flashlog.txt, policy files (adobe flash security model) and so on… It allows searching, word wrapping, log snapshots, flash player detection, and so on…
It works by catching the outcoming data from flash directly.
This project is also cross-platform because it relies directly on Adobe’s framework rather than other language, it works differently because its a remote logger. You connect to it and dump contents, thus you do not need to run in debug mode nor even use trace as a debug function. You can send data to another machine rather than localhost, and even put some colors on the output. Although it doesn’t provide the same level of features as vizzi, its slightly different are seems more suited for real dumping information (logging) of test sessions.
* Thanks Diogo Mariano for the tip!