Support |
----- Original Message ----- > Since you're now working with both Reaktor 5 and MAX/MSP, what's you're > impression of the type of sound delivered by each application? Among > Reaktor fans it's a popular argument against MAX/MSP that it should > "sound too thin". However, personally I think I spend a lot of time > thinning out my sound sources for layering into loops, so if it's true > that "MAX sounds thing" it might just turn out a good thing for looping. > > per Excellent question and topic. There are probably several sorts of comparisons, so I'll include some cursory impressions that address your question and go beyond it. And sorry for this long-winded response, but this is a fascinating topic. First, I think the type of sounds that one gets from MAX/MSP and Reaktor is entirely dependent on what the programmer (patch or ensemble builder) does with the program. My guess is that if someone heard a MAX/MSP patch, and it sounded thin, it was because the patch builder designed it that way...because both apps have similar capabilities and flexibility in terms of modifying tone, building it, and so on, and both are tapping into the same audio architecture of the computer. So, if Reaktor folks are making an argument that MAX/MSP sounds thin, they are probably misunderstanding the architecture of the program and what on can do with it. I don't know what that would mean, actually. For example, when you open MAX/MSP, you have an blank slate....just the void with nothing but potential for the programmer. Maybe Reaktor folks are saying that the fundamental audio I/O architectures of MAX/MSP and Reaktor are different in terms of quality...I'm not sure how anyone would verify that. I suppose you could create a MAX/MSP patch and a Reaktor ensemble that had nothing but input and output, just passing the dry signal (white or pink noise, etc) through the system and soundcard...and then one would have to do an A/B test with a frequency analyzer. I don't know of anyone who has done that to make a legitimate argument. Second, I'm still understanding the depth and breadth of the community and patch resources available for MAX/MSP, by my impression thus far is that Reaktor users make it easier for everyone to access ensembles that are ready to roll right out of the "box" for music performance...this is via the Reaktor user library. I have seen this discussed in the MAX/MSP forum too...some folks seem to admit this but aren't that concerned about it. In other words, at the Reaktor library, you just download the ensembles to your ensemble library, and in most cases they are ready to use like VSTs; whereas with MAX/MSP, when you download a patch, you may have to do some additional programming to make it work in your custom interface. Granted, there are a lot of MAX/MSP user websites and even a central repository that provides access to many patches, but since MAX/MSP, almost like a computer programming interface (e.g. Visual Basic), can do much more than create music applications, you tend to find a lot of non-music performance related patches...versus what you find on Reakor, which is purely ensembles for music making. The flexibility and power of MAX/MSP can be a double-edged sword, depending on the expertise and confidence level of the user. For me, I am very intimidated right now by the capability of MAX/MSP, and I haven't got close to doing anything with Reaktor...I'm a leverager of other patches/ensembles and find that most of my needs are met by existing patches/ensembles out there. That being said, I will admit that the based on the patches I have tested so far from MAX/MSP and the ensembles I am using with Reaktor, the Reaktor patches I have are very complex and rich sounding...like Blackbird, which produces a really nice Eventide like sound with several octaves, delay, etc (quite amazing, in fact). Whereas the MAX/MSP patches I have heard so far, albeit very technical and precise in what they do, are more focused in their sound effecting. I think this is just based on my limited exposure, and I suppose if a MAX/MSP programmer were to build something that was similar to Blackbird, the matter would be settled, and we'd know that there is really no difference in terms of flexibility and capability between the two. My guess is that it might be more difficult to build a MAX/MSP Blackbird equivalent, because MAX/MSP seems to start at a more fundamental level in terms of the building blocks of patches. I'd be blown away if a MAX/MSP programmer did this...because right now Blackbird (thanks to Dave Coffin who shared it with me) is my favorite patch of all, out of all my VSTs, etc. ...just the tip of the iceburg, and again this is all coming from a MAX/MSP/Reaktor neophyte. ************************************************************************** Krispen Hartung / Improvisational & Jazz Guitar www.krispenhartung.com / www.myspace.com/krispenhartung Performance Calendar: http://www.musi-cal.com/search?performers=Krispen%20Hartung info@krispenhartung.com / 1.208.724.5603 Discography - http://www.krispenhartung.com/catalogue.htm CD Baby Discography: http://cdbaby.com/all/khartung