Yesterday I wrote about the possibility to import references from Google scholar into a reference program. Today I found a description on how to do this directly from within BibDesk. This is a good example of why you should bother to read the upgrade notes when you download new software. Then I would probably have discovered that the “bookmarks” menu was introduced in version 1.3… Well, this makes a great application even better.
micro-OSC (uOSC) was made public yesterday at NIME:
micro-OSC (uOSC) is a firmware runtime system for embedded platforms designed to remain as small as possible while also supporting evolving trends in sensor interfaces such as regulated 3.3 Volt high-resolution sensors, mixed analog and digital multi-rate sensor interfacing, n > 8-bit data formats.
uOSC supports the Open Sound Control protocol directly on the microprocessor, and the completeness of this implementation serves as a functional reference platform for research and development of the OSC protocol.
The design philosophy of micro-OSC is “by musicians, for musicians”—it is used at CNMAT as a component in prototypes of new sensor-based musical instruments as well as a research platform for the study of realtime protocols and signal-quality issues related to musical gestures.
I have only read through the NIME paper briefly, but an interesting aspect is how they are focusing on the implementation of OSC bundles with time tags, something which is rarely found in most OSC applications. Looking forward to test this on the CUI.
Seems like the new MT9 format, or Music 2.0 as the company Audizen calls it, is all over the news these days. The idea is simple, and has been explored for years in the research community: distribute multichannel audio, so that the end user can have control over the single tracks. The problem of course is to make this into a standard, and I see many challenges in how this could be implemented:
- How should the division of sounds be?
- Should every track be totally independent of the others, or would there be room for leakage between tracks (e.g. reverberation).
- Is it intended for 2 channel tracks only. How would they handle panning/spatialisation and multichannel tracks?
It would be interesting to read the specification of the format to see how they are going to approach this. Anyway, it is great to see these things approach the mass market! I am quite sure we will see lots of such “active music” approaches in the years to come.
It has taken a while, but I finally found some time to update my MultiControl application. This was a small program I made back in 2004, and have updated a couple of times since then (that’s why the patching code looks so horrible, please don’t look at that…).
Originally, I made it for a series of workshops with kids, but I have also used it in a few concerts. Inspired by some blog comments and e-mails, I am happy to announce version 0.4. The main changes are:
- It handles 20 inputs (I will make this dynamic at some point, but then I will need to repatch the whole thing)
- Saving/reading of preset files should now work properly (again)
Thanks for your patience, and please let me know if you have any problems.