Lewis Smith

Hey people. My first post in this forum. I'm quite a newbie to Max but working on a new composition for Cello and electronics.

I'm usually the guy that wants to code his own software but in this case I'm the composer looking for fast ways to incorporate my ideas into a score and spend more time writing notes than code.

For that reason I came across Adam Stark's Sound Analyser. I'm looking to trigger, settings, algorithm's etc (not decided yet) based on the performers input from a close mic.

But here's my problem. I'm not absolutely sure what this plugin is outputting. In fairness, this is a bit of a broad question because there are many methods of analysis available in that plugin. I'll try and narrow it down as much now and much more later as I progress.

In particular I'm curious about the Chromogram, Spectral Centroid and Chord Detector outputs.

If you've had any experience with this plugin, I'd love your input. Unfortunately there no documentation with the plugin.

Hey people. My first post in this forum. I'm quite a newbie to Max but working on a new composition for Cello and electronics. 

For that reason I came across Adam Stark's Sound Analyser. I'm looking to trigger, settings, algorithm's etc (not decided yet) based on the performers input from a close mic. 

Hey people. My first post in this forum. I'm quite a newbie to Max but working on a new composition for Cello and electronics. 
I'm usually 

adam-stark's-sound-analyser

http://www.adamstark.co.uk/project/sound-analyser/

There is a paper, which describes the Audiounit-Plugin. A short look:

The plugin is in 32 bit and sends out OSC messages..., so need a 32bit host and a soft, which can receive OSC data (like Max, Reaktor etc).

see his website: http://www.adamstark.co.uk/project/sound-analyser/ 
There is a paper, which describes the Audiounit-Plugin. A short look:
The plugin is in 32 bit and sends out OSC messages..., so need a 32bit host and a soft, which can receive OSC data (like Max, Reaktor etc).
\Klangschmied/

Thanks man. I read the paper when I downloaded from his site. I was just hoping to see if anyone had any experience with it or how they may have used it. His paper is more qualitative than quantitative and there isn't any documentation. Then on top of that... its an AU plugin not a Max patch, so there isn't a help file.

I'm experimenting and using the data to determine what I might do with it. The handy thing about it is that there's a lot of data to experiment with and that changes depending on the audio content, naturally.

I don't have access to the cellist that will perform my composition for very long but I'm using lots of samples to test the data, such as Theraps, Xenakis; even though it is for double bass; and of course Sequenza XIV, Berio.

Still, if I can find someone who can help me not reinvent the wheel, I'll be cooking.

Thanks again. I really do appreciate the feedback. And I dod indeed have it connected through udpreceive.

My personal suggestion, unless this is a one-off, is to use other analysis objects such as Zsa.lib or the Tristan externals from CNMAT. The project hasn't had a commit for two years and only seems to have one person working on it so support concerns are warranted , unless you're already comfortable with C/C++ and JUCE. As far as I can tell, many of the component algorithms are available elsewhere in the Max ecosystem.

This certainly isn't to say that the project's goal of making this sort of analytic data more accessible isn't a good one, because it certainly is. I have long wished that Max had more built in objects for this, though the Package Manager has helped.

My personal suggestion, unless this is a one-off, is to use other analysis objects such as Zsa.lib or the Tristan externals from CNMAT.  The project hasn't had a commit for two years and only seems to have one person working on it so support concerns are warranted , unless you're already comfortable with C/C++ and JUCE.  As far as I can tell, many of the component algorithms are available elsewhere in the Max ecosystem.

This certainly isn't to say that the project's goal of making this sort of analytic data more accessible isn't a good one, because it certainly is.  I have long wished that Max had more built in objects for this, though the Package Manager has helped.

Thanks Peter. I've abandoned it for this project but it is something I'm looking into for future projects. Thanks for the advice. I'll certainly be looking into that.