1.0.7 is a must-download on any platform because of key fixes to auto-format, highlighting, exception reporting, and PVector. (See revisions.) But if you’re an early adopter of Snow Leopard, this offers fixes for that, as well:

Tweaks for Mac OS X Snow Leopard, to force it to run in 32-bit mode. This should bring back the video library (if temporarily), and hopefully fix serial as well, though I didn’t have a serial device handy to test.

Add this to 1.0.6 from last month, which fixed launching on Linux and a bunch of image and JOGL stuff.

As always, grab it at:

I’m hopeful, by the way, that we’ll soon be able to abandon the default Processing video library on Mac, which is based on the deprecated QTJava. GSVideo works well for playback, and no longer requires that you build everything from scratch. The big missing component is video capture, which is something I’d like to abandon. Any gstreamer experts out there?

In the meantime, in the interests of full disclosure: my main Processing development machine runs Windows and Linux.

Stay tuned, as I plan to release something Processing-related in the next few days.

  • DDD

    I love the concept of Processing and have been developing in it for several years but I am ready to abandon the platform due to the low activity and response rate in the user forums. I would say that on average only 10 percent of my posts/questions to the Processing forums get any kind of response! This makes it really tough to work on projects when you know that there is no help.
    In contrast, anything I post to OF, Cycling 74 or Arduino forums gets almost %100 response (and quickly too).

  • Well, yipes — that's not what I want to hear. Those other tools are terrific, but Processing fits a unique part of the puzzle, and if it loses people, that's a loss to everyone.

    I think if the C74 forums give you a better experience, that's really a huge loss to open source. You know, part of what allows things to be *free* is the involvement of other folks. And that's not a Max vs. Processing statement – on the contrary, they're radically different tools, and speaking as someone who's used both, I couldn't replace Processing with Max in my work. It'd be like replacing my kitchen sink with a moped. Both useful, but I use them differently.

    On the other hand, I'm concerned that there's some fragmentation between Open Frameworks, Arduino, and Processing. These tools share a lot of the same techniques and even syntax. (Arduino wouldn't even exist without Processing.) Maybe there's a way to get some of that community happening across tools.

    Or to look at it another way, I'd be interested to examine why responses aren't getting answered on the Processing forum and are on OF or Arduino. My sense is Processing's active user base is much, much larger than OF or Arduino because of how much it's being used in education. But that may mean that what we have is a large group of beginners and a much smaller group of experts.

    I also think forums alone are not the only channel by which a community exists. So I'd be interested to look at this picture and what can be done. Let's definitely talk about this more.

  • DDD

    OF offers similar functionality but with a much smaller user base yet I get generous help and response to every question I post. With Processing I have even directly e-mailed the authors of certain Processing Libraries without receiving a single response.

  • Processing Rocks!! Big fan here!

  • PPP

    the reason why max/jitter user gets faster and better response is because the community of professional developers is bigger and they pay for support. the users are more focused on output than in developing the tool they are using.

  • DDD

    Yeah but the OF and Arduino community are also Open Source (and the Arduino community is filled with novices) but questions get answered, libraries get fixed and upgraded.

    Here are some topics that I have posted about in the past and got zero response for:

    -there currently no (working) beat detect classes/libraries that will work on a Mac.

    -Firmata library is stuck at 2.0 while 2.1 has many essential upgrades (like support for I2C). ]

    -Serial port library performance is ridiculously slow. I am convinced there are some major bugs with this.

  • Well, this topics are really specific and advanced. My P5 level is quite high, as I've been using it since the early begginigs, and I never got involved in serial/firmata/beatdetect stuff. So, it is difficult that you find much help on that topics… sure you know more about them that 99.9% percent of the users.
    Processing is really the best tool to learn graphic programming. If you want to develop an specific application where speed is needed, you can port it to OF, as many people do. So you have the ease and ductibility of P5, and the power of C++ in OF. Both platforms are complementary. And both comunicate with Arduino. So you don't have to start a war: if you need them, use them. If you need something else, go for it.

  • DDD

    Don't get me wrong I love Processing and I continue to use it, I am just pointing out some frustrations. I do use it for graphics but more focused on interactive graphics and it is nice to have everything integrated in one system if possible (i.e. hardware and software)

    Instead I will have to look to use these other tools and then interface to Processing via OSC/midi.

  • A bit off topic… but what is OF that you're referring to here? Thanks.

  • OF = OpenFrameworks:

    OF really shouldn't be considered as Processing's competition – more its complement. OF derives syntax and structure from Processing, but provides access to C/C++ coding and libraries in a way that can make it useful to mix and match with Processing. They're both covered, alongside Arduino, in the new book Designing Interactivity.

    But I think OF's ecosystem will be less healthy if Processing doesn't continue to get love. And it's essential to have Processing as an entry point for coders, and a way of connecting to Java libraries and tools. Likewise, I think Processing is healthier with OF around, because Processing isn't the right tool for every job.

    DDD: Audio on the Mac is a significant obstacle for Java. Blame Apple; Java is unequivocally their responsibility on the Mac, as they're the provider for the JDK, and their audio/MIDI support ha actually gotten worse. That said, I'm not sure which beat detection libraries you're talking about; you're having problems with Minim? (I've had it work pretty well.)

    Another alternative is to work with SuperCollider, which is what I'm doing.

    @PPP: I'm unclear on what the basis of your statement even is. Processing has a significant professional developer community. The complaint here is actually that people aren't spending *enough* time developing the tool. But I've heard similar complaints about Max (even about serial performance.) Bottom line: people complain. Both are strong tools with strong communities. They're just different tools. If we can make them better, and that makes us more productive, let's do it!

    By and large, Processing's support is pretty darned strong. I think any opportunity to help make it better is worthwhile, as it's an important platform that works alongside all the tools you describe (including Max).

    These sound like specific questions – ones worth looking into. I'm revisiting Firmata. It's probably just a matter of someone needing to do the port. These things often don't happen magically with *proprietary* software, either. The advantage of free software is that you're free to fix it yourself.

  • I'd be more than happy to blame Apple for its lack of Java support, and breaking the QuickTime API with 10.6 and QT X. (Yeah, 1.0.7 doesn't fix the QuickTime problems that were introduced when I upgraded to Snow Leopard…) I want to give GSVideo a try. Aaron Koblin recommended it to me @ SIGGRAPH this year, but I haven't had a chance to try dropping it in. Frustration with Java errors… I'd rather be creating great art/music/whatever than deciphering cryptic error codes.

  • Well, and I should qualify – the QuickTime API for Java is deprecated. It's beyond even blaming Apple. The thing is just dead. But GSVideo is coming along very nicely.

    What Java errors are you getting? If it's video-related, then definitely dump qtjava (processing.video).

  • Oh, yeah, I do recall a surreal discussion on the qtjava list in which someone claimed that describing QuickTime for Java as deprecated violated Apple's NDA.

    Of course, you can't make deprecation secret; sorta defeats the purpose.

  • lifo

    <blockquote cite="…I want to give GSVideo a try. Aaron Koblin recommended it to me @ SIGGRAPH this year, but I haven’t had a chance to try dropping it in…">
    i´ve recently tryed.. installing gstreemer in mac is quite hard and in snow leopard was imposible for me.

  • lifo

    i was talking about what chuckeye says.. the quotation didn`t work.