2008 MonemurV2 version Chris Lloyd. 
Version 2 Beta 0.6.1

Special thanks to Andrew Capon for his many contributions, Andrew Graham for some 256 mods and Nick Bugayev for writing 
the original patch. Startup sequence
was adapted from Blinken Park written by Matthew Davidson at stretta.com.

Requirements: 
Lemur/Dexter Dual Boot
MAX 5 or MAX 5 Runtime
Computer and a Monome App to connect to

This MAX 5 patch and Lemur interface file are designed to make your Lemur act just like a Monome. In fact, you can 
emulate all 3 monome configurations. You have to select the interface that matches the app you are using. The message 
prefixes are /40h /128 /256 for the respective Monomes.

Monemur provides the exact same functionality as MonomeSerial does with a real monome. You do not need to run 
MonomeSerial as Monemur replaces it.

Monome->MonomeSerial->App
Lemur->Monemur->App

Why do I have 2 more ports and addresses to configure that with MonomeSerial?

The Monome uses USB to communicate with MonomeSerial, so you do not have to configure the communication from the Monome 
to MonomeSerial. In the case of the Lemur, the Lemur communicates over a network connection to Monemur, so you need to 
configure the addresses and ports for that communication to occur as well. 

Here are the steps

1. Unzip and open MonemurV2.maxpat in MAX 5 or MAX 5 runtime

2. It should Open in Presentation View and you should see a settings dialog.

3. Configure your ports and addresses for Lemur and whetever 40h 128 or 256 app
you are connecting to using the controls in the max patch. To change a
setting, you need to use the controls provided and click the button
next to each value to accept it. Default message prefixes are /40h /128 /256 respectively.

If you have an app that does not use one of the default prefixes. You must enter the new prefix in the custom prefix 
edit field next to the monome configuration you will be using. For example, some older monome apps used /box as the 
prefix.

The default ports are already setup the same as MonoChrome and Molar
defaults. Other apps might default to different ports. You have to configure the OSC 0 port on your lemur to point back 
to your computer address. 7999 is the default. If you app and Monemur are running on the same machine, you cannot use 
the same port for OSC 0 and the app listen port as this would cause Monemur and the app to try to bind to the same port 
for listening to messages.

4. Open Monomur.jzml in JazzEditor and push to your Lemur

5. After that everything should work as if the Lemur was a 40h/128 or 256 monome.

6. The slider on the right is not connected to anything. Feel free to connect it to the control of your choice.

Remember that this version is still an Alpha. Please help me out by posting problems to the forum. It has not been 
extensively tested with apps other than MonoChrome and Molar although in general it should work provided you use the 
correct message prefix and monome size. 

There are a few protocol messages that are still unimplemented so it is possible other apps may use some of the 
unsupported messages. These will be added soon.

Here are the unsupported messages

/sys/offset - for linking multiple monomes into one big grid.
/sys/cable - makes no sense on a Lemur
/40h/frame Updates entire interface at once - this will be implemented once I find out what the correct syntax is.
/sys/intensity
/sys/test

PLUGINS: MonemurV2 now supports application specific plugins. See Molamur patch on the JazzMutant site for examples. All 
OSC messages not understood by MonemurV2 are routed to an auxChannel that the plugin can listen to. Just use a "receive 
auxChannel" in your plugin and you will receive any custom interface messages that are not used by Monemur. Monemur uses 
the /box prefix. Your custom plugin should use something else.

Change Log 

Version 2 Beta 0.6.0 - June 10th 2008
 - Added persistence of user settings.
 
Version 2 Beta 0.6.1 - June 11th 2008
 - Fix wrong default prefixes for 128 and 256.