Posts Tagged ‘max/msp’
Andrew Benson over at the Cycling ’74 site put together a really solid post on connecting a camera to your Max patch:
He covers the hardware requirements (cost, Quicktime drivers for mac users, and manual controls) as well as the handling you may want in your patch. What frame rate do you want to deal with? What are a few ways you could extract useful information from the feed?
So it’s been a while since I’ve had a chance to post here, but I just got back from a weekend of AES and I need to report on the happenings.
I made it down Thursday night and stayed until the end of the program on Monday: four long days at the convention and a great time catching up with friends both living in New York and visiting for the show.
If you haven’t been to an AES convention, they’re broken up into two distinct parts: a trade show, with equipment designers and manufacturers showing off their new products, and a technical session, where industry professionals and research can share their recent work. Usually you can cover the trade show in a day, though this year it took a lot less time. Through some combination of the economy and industry politics many manufacturers did not attend; I think the most conspicuous absence was Digidesign, since they usually have a huge booth with half hourly product demos. For me the highlights here included the Shure booth, where I got to check out their new ribbon mics and visit with old colleagues, and the Grace Design booth, where they were showing off their new 500-series preamps.
The technical program was a little quieter than usually, but much more lively than the exhibit floor. Some of my personal highlights were the Max for Live presentation, the Headphone and Earphone Measurement Tutorial, David Berner’s presentation on emulation of analog hardware in DSP, and a number of papers I had a chance to catch.
I’m planning to write a bit about some of the presentations I saw, so stay posted. Also, hopefully this will be the beginning of a more regular posting schedule.
Last year I had the opportunity to help out a friend with a project for a class he took at MassArt. We used a microcontroller with buttons for a UI, and fed the data into the serial port of a computer. We used Max/MSP to generate MIDI data and finally used Ableton Live to trigger audio sample playback from the MIDI.
The system was overly complex, but the coding was actually a minimal amount of work. It got me thinking about a few μController-based projects that have been on the back burner for a few years. I figured it would be good to conduct a quick survey of the chips that are being commonly used and have the best online support networks.
The Arduino is actually what we used for the Max-Ableton project I mentioned above. This is a family of creative commons controlled boards, with open source software to build on. My experience working with the Arduino was very enjoyable – the combination of a high-level language and lots of support online made the job easy. You can get a great board for as little $30, and you’re pretty much ready to go out of the gate. The boards are based around ATmega RISC micros.
There’s also a great series of articles on producing sound from an Arduino here.
Phidgets are a system of chips and sensors linked to a computer via USB. These boards are designed to operate in tandem with the computer, instead of as standalone processors. There’s an API for pulling together interfacing applications on the computer side, and there’s a Max/MSP object for interfacing directly with the Phidgets. The sensors available include buttons, encoders, accelerometers, PH sensors, and thermocouples, ranging in price from $28-95.
Handyboard is an MIT design, with a focus primarily on robotics. These boards are setup for reading sensors and driving motors. There are only a few vendors, and the boards run in the $100 range. There’s a fair amount of information on the MIT site, but the online community using the Arduino platform seems to be a lot larger.
The PIC platform has been around for years, and is a simple solution for the serious DIYer. This solution is a little messier than some of the others listed above, because you’re dealing a lot more at the component level and coding in assembly language. You’ll need a PIC programmer, and then you’re pretty much ready to go.
The biggest benefit I can see from PICs are the low cost of the chips. With the Arduinos you’re likely buying $30 boards; you can can PIC chips for anywhere from $1-8. The economy of scale is very nice here, but for building a one-off circuit I’d likely stick to the pricier options above.
I added this to the list because of the audio capabilities, but this is less a microcontroller system than it is a tiny Linux computer. The cost is greater than the systems listed above, and the documentation is still under development. I tried a project on this about a year ago, and ran into a number of issues. I attribute them to my limited experience with Linux, something I’d like to rectify.
This list is far from complete – it’s just a few of the platforms I know people are working from. As I gear up for a new project, I’ll continue to look into suitable μController platforms and post about them here.