{"id":158,"date":"2012-04-17T12:13:00","date_gmt":"2012-04-17T11:13:00","guid":{"rendered":"http:\/\/www.celesteh.com\/blog\/2012\/04\/17\/liveblogging-sc-mx\/"},"modified":"2015-06-19T00:23:18","modified_gmt":"2015-06-18T23:23:18","slug":"liveblogging-sc-mx","status":"publish","type":"post","link":"https:\/\/www.celesteh.com\/blog\/2012\/04\/17\/liveblogging-sc-mx\/","title":{"rendered":"LiveBlogging SC: Mx"},"content":{"rendered":"

by Chris Satinger (aka Felix Crucial)<\/p>\n

Mx is a tool for connecting objects together.  audio, control, midi etc<\/p>\n

Anything that plays on a bus, the bus can go in and it can be put on a mixer.<\/p>\n

This mixer is a GUI thing. You can use it just to glue on things like fadeouts or amplitude control.<\/p>\n

Just write a descriptor file.<\/p>\n

The system is not the gui, it’s the patching framework.<\/p>\n

You can patch synthdefs together. and edit the synthdefs on the fly.<\/p>\n

This patches things a wee bit like PD.<\/p>\n

It checks for bad values and prevents explosions.<\/p>\n

There is no time line system. It’s a hosting system and only manages connections and starts and stops. You can put in other timelines<\/p>\n

\nIt uses environment variables. ~this is the unit.<\/p>\n

~this.sched(32, { … }, { … })<\/p>\n

You can put documents in the Mx. Those can change the Mx as it runs, so it’s all very self-modifying. (When I was an undergrad, they told me this was naughty, but like many other naughty things, it can be very cool.)<\/p>\n

Things have outlets and inlets that you can connect.   There is apparently a querying system which we will learn about.<\/p>\n

He gets good music out of the system despite having no idea what’s going on a lot of the time<\/p>\n

Dragging cables is fun for a while, but then…<\/p>\n

\nQuestions<\/h3>\n