New serialosc Utility "SerialOSnoopy"

  • http://docs.monome.org/doku.php?id=app:serialosnoopy

    SerialOSnoopy is a mod of the serialosc abstraction that pipes all press data out on a secondary osc port. This gives you the ability to pipe monome data into multiple application to monitor input such as processing, super collider, or even another instance of max/msp.

    Utilizing the mod is fairly easy. First copy the serialosnoopy.maxpat file into any monome application folder. Open the application and modify the patcher file from serialosc.maxpat to serialoscnoopy.maxpat.

    There should now be a new S button available within the serialosc subpatcher, click it to set the port

    *NOTE* Routed osc data is sent without a prefix, this will allow you to make open ended applications that can receive the SerialOSnoopy data from any application without needing modification

    More example for processing can be found on the github page for the project. Most of these are going to be modifications of the github example applications
    https://github.com/TheAlphaNerd/SerialOSnoopy--Monome-

  • Thanks!!! this will be usefull with my visuals that a friend does in PD with the messages of my monome.

  • why not use griddle's mirror mode, which has the advantages of being cross platform and not needing to buy Max and then rewrite all the apps you want to run?

  • I just wrote a quick processing sketch to handle the osc messages from osnoopy, it has been added to the docs and the github page.

    griddle could be an option... truthfully I have not yet gotten it to work. One of the advantage to this method is that it does not add any steps to the chain of messages between the monome and your application, and it is a transparant add-on to any currently existing or future max patch.

  • I have updated the utility... it now routes both led state and press data.

    More processing examples have been added

    Enjoy!!!

  • Just updated the utility again... extra inlet on the serialosnoopy abstraction. The third inlet allows you to manually change the port that snoopy is monitoring.

    I have also included a modified version of monomeserial to add legacy support

  • Any thoughts on arc support?

    Doesn't make sense for visualization software, perhaps, but it could be a godsend for projects like this:

    http://post.monome.org/comments.php?DiscussionID=13322

  • hi @thealphanerd,
    I'm looking into a way to visualise monome interaction in processing. Is serialosnoopy still working?

    I can't get this to work. My monome 128 doesn't show up when I open serialosnoopy.maxpat (osc-route: No such object/zeroconf.resolve: No such object) and the serialosnoopy_communicator.pde doesn't do anything.

    What do I install/do wrong?

  • @warddem

    Serialosnoopy and the visualization stuff all relied on the zeroconf capabilities of the earlier versions of serialosc

    This functionality is still in there, but you will need to have the zero conf externals installed... which will only work on 32 bit.

    Hop on irc and lets talk aboot it

  • Thanks,

    32 bit is not an option on OSX. Is there any alternative to forward monome input to multiple ports?

  • @warddem
    right click on the application, click get info, check 'Open in 32-bit'.

  • @thealphanerd @elquinto
    Thanks for the reply but I'm still doing something wrong and can't figure it out.

    Here the steps I've taking to install:
    - download serialosnoopy (http://monome.org/docs/app:serialosnoopy)
    - copy OSC-route.mxo into max6/cycling74/exernals/
    - download zeroconfig http://monome.org/docs/app:serialosc:zeroconf
    - copy zeroconf.browser.mxo zeroconf.mxo zeroconf.resolve.mxo zeroconf.service.mxo into max6/cycling74/exernals/
    - copy serialosnoopy.maxpat in max6/patches
    - rename serialosnoopy.maxpat to serialosc.maxpat
    - open max 6 runtime in 32 bit mode
    - start osnoopy-test.maxpat

    I'm unable to select my monome 128 from the drop down. (I see the s-button in mlrv2 but no device in dropdown).




  • perhaps try doing "get info" and setting the application to 32 bit. Are there any errors in your max window?

  • Also, serialosnoopy was originally made in max5, and I have never tested it in max 6. It could easily be hacked into the new version of serialosc though, it is just a splitter.

  • Tried the 32 option but no luck.
    My trail version of max ended so I'm unable to adapt the sketches myself.

    A max6 splitter would be great to receive monome info in processing and visualise it. I'm making something in the style of @phortran 's "generative visuals ". A splitter would open the doors to generate visuals (http://www.openprocessing.org) while playing monome apps.

  • @warddem another option is griddle: http://monome.org/docs/app:griddle
    read esp. about "mirroring."

    looks like you may need to do a little legwork (per recent forum talk), but it's worth a try.

  • @thealphanerd
    Bought max 6 (very new to programming like this) but no clue how to hack serialsnoopy so it would work with max 6 / current serialosc. Any tips or links to get me on the right path would be great.

  • unfortunately it is not exactly cut and dry... and to walk you through the process right now would be the equivelent of re-writing it. Hopefully I can find some time in the near future to update it.

  • no worries, I completely understand. Attached a max 6 and processing sketch that communicates through OSC to learn more about the interaction (my first steps in max). Might be useful to others.

    An updated OSC splitter would be awesome.