So I love my 40h so much that I'm thinking about getting another one.
I'll use one with live via monogrid, and one to control monochrome vst
within live. Are there any limitations that would prevent me from doing
this?

I've tried to run the virtual 40h and see if I can tether it to
monochrome vst while my real 40h is talking with live through monogrid,
but I haven't been able to get it to work. When I try to run a second
instance of monomeserial, I get an error that says "monomeserial failed
to start because port 8080 is already in use." How do I create a second
port and tell monomeserial to use it for the virtual monome?

Thanks in advance!

i dont think anyone has successfully gotten this to work yet. 
monomeserial is supposed to work using the same port for all OSC 
connections, but with seperate prefixes or same prefix and offsets. 
perhaps steve can try working on a version that uses same port for 
instances, with differant prefixes?  might be tricky.

Hello,

I am not very familiar with all the apps and setup tools under Windows, 
but I think serial-pyio may be able to help you for this problem. We 
plan  to add support for multiple apps to serial-pyio. Basically this 
means that you can have two apps talking to the monome, and you will 
choose which app will be displayed on the actual device, with the 
possibility to switch between apps. Another possibility would be to have 
a virtual 040hlaunched (the one of serial-pyio) and having one apps 
displayed on the actual 40h while the another app would be displayed on 
the virtual 40h. When you switch apps, displays would be exchanged, 
first apps moves to the virtual 40h and second app goes to the actual 
40h. The only negative point is that this has to be implemented. With 
some luck it will be there in the coming weeks...

Does this makes sense for what you want to do ?

Julien

Thanks Julien, that does make sense. Swapping between the real monome 
and the virtual monome would save me having to track down another monome 
to buy.

All I really want to do is sequence with monochrome and control live 
with monogrid all in the same set. Whether I would have two monomes (one 
controlling monochrome and one controlling monogrid/live) or just on 
monome toggling between controls, I'll get to my desired end.

Something i tried last night with little success is to run a live set 
using monogrid, and place monochrome vst on a midi track set to receive 
midi from channel 8 only. I was hoping that monochrome would receive the 
midi from grid 8 (channel 8) and function as normal. Although the track 
was receiving midi, monochrome did not respond to it. But, if I manually 
lit buttons in monochrome (shift + click), the monomes leds would light 
up in response. They would still light regardless of which grid I was 
on, and I still had full control of the clips I assigned to grids 1-7 
(channels 1-7).

Okay, so I know the midi going into monochrome has to match the note 
number to trigger the button. And I know that monogrid sends out 
different midi notes for each button on a given grid. And monochrome 
needs to have the same note number across each row to sequence the same 
sample, and would have to ignore the notes coming in from the bottom row 
of buttons (grid select). And there are many more inherent problems, but 
it seems to me that a resolution could be found.

How cool would it be to use grids 1-7 from monogrid to control various 
functions in live, and have the top 7 button rows on grid 8 control 
monochrome? Sequencing, live functionality, and mlr-style loop slicing 
all with one monome.

You may say I'm a dreamer, but I'm not the only one...