MaxOrch - a front end for computer-assisted orchestration tool Orchidea

bloland's icon

Greetings,

We are very excited to announce the wide release of MaxOrch

MaxOrch is a full-featured front end for the Orchidea objects (a framework for static and dynamic computer-assisted orchestration), downloadable as either a Max patch or a Max standalone app. This is a collaboration between myself and Jérôme Lesueur, joining and replacing both his MyOrch and my Orchidew patches. 

A brief explanation: Orchidea is a set of Max objects designed for computer-assisted orchestration, developed by Carmine Emanuele Cella.  At its most basic, one selects a database of samples (databases of orchestral instruments (with extended techniques) are downloadable for free from Ircam) and a target audio file. Orchidea analyzes the target audio file and produces a score and a composite audio file that is a realization of that score.

We recently updated the MaxOrch website to include documentation pages. It can all be found here:
https://perbloland.com/maxorch-about

MaxOrch is currently in beta testing. Please let us know about any bugs/issues/requests on the MaxOrch discussion page on the IRCAM Forum.

Enjoy!
Per and Jérôme

agustin issidoro's icon

Hi there! Amazing work. Are there any news about the Windows release? I've been using the standalone but it is very little flexible.

bloland's icon

Hi Agustin, Glad you're enjoying the standalone! And yes, it is a bit limited. I am only responsible for MaxOrch, the front end for Orchidea, so can't speak to Orchidea's availability for Windows.
You might head over to the Orchidea forum on Ircam's site:
https://discussion.forum.ircam.fr/c/orchidea/49
I can tell you that Carmine knows the demand is there, and is very interested making it all cross-platform. When that might happen I can't say.

Jerome Lesueur's icon

Hi,

It is regrettable that the standalone version is no longer operational on MacOS Sonoma due to the restrictions imposed by Apple. Specifically, the software prompts the user to validate the analysis of each segment via four pop-up windows, which is impractical in dynamic orchestration mode.

The issue affects all standalone Max-built applications. In the majority of cases, users are required to validate access to the audio only, resulting in a maximum of two or three pop-up windows.

It would be beneficial to have the ability to manage authorisations within the build script in Max.

We (Per and I) are attempting to resolve this issue.

Best regards,

Jerome