And yeah, it definitely needs to know the ip of your device. In mlr (old) there's an object labelled p 40h_osc. Inside that patcher there's a message box that says udpsend localhost 8080. You need to change the localhost to be the ip address of your device. You won't see any feedback until the ip address and prefix are set.
monome / mlrv
(101 posts) (13 voices)-
Posted 2 years ago #
-
ah, i was thinking there was probably a place in the max patch that would need to be changed. i guess that has to be a part of the steps? or maybe we can come up with a very simple max patch to be used with Control that has a place to enter the IP to be used in all monome apps? i don't know if that's practical or possible, though.
edit: that did the trick! extra step? open the max patch in a text editor and find and replace "localhost" with your device ip?
Posted 2 years ago # -
i modified one of the monome base patches a wee bit and this works for sending any prefix you want to Control's monome emulator interfaces! i tested it just now with the monome128 interface. basically what i did was open the prefix.mxb file and saved it as a max 5 patch. what that does is make the patch editable in any text editor! neat!
so open this patch in either max msp 5 or in any text editor and find and replace 192.168.2.2 with whatever your device IP is, save the file and run it in max runtime (or msp if you want). now change the where it says "/box" under "prefix" and press the button that says "/sys/prefix /<newprefix>" and it should update your interface!
http://www.mediafire.com/?3j4p44wkb6k1n5s
now if only i could figure out how to fix the backwards/upside down interface bug =p
Posted 2 years ago # -
OK, the 128 interface online is fixed... you can probably just hit the refresh button. I was thinking the apps sent messages in terms of row / column, but it's actually the opposite.
I've also updated the 40h interface and posted it online:
http://www.charlie-roberts.com/Control/interfaces/monome40h.js
Hope this helps... - Charlie
Posted 2 years ago # -
sweet! cant wait to get some practice time in tonight! i was waiting for this fix before replying in the monome forum =)
also I'll try to record a comprehensive video as of the current state of Control monome emulation!
Posted 2 years ago # -
Sweet... videos are always appreciated.
Posted 2 years ago # -
New here, and since I sold my monome to buy an ipad I've been hoping for a windows-based solution. Looking forward to the vid!
Posted 2 years ago # -
i dicked around a lot with the Control monome interfaces tonight, but unfortunately didn't do anything worth recording! it's a lot of fun, and i've manage to make any monome app work as long as i edit the patch to use my device's ip instead of localhost for udpsend. i also updated the prefix patch to look less hideous and be easier to understand.
http://www.mediafire.com/?xw29mvsjxrr351w
remember to edit the patch with a text editor (or max) to change the IP to your device's IP!Posted 2 years ago # -
Everything working great here!
@Charlie You are the MAN! Thank you so much for this great app!
@ronji You are the MAN! Thank you for the patch and the max updsend tip!
Posted 2 years ago # -
here's a quick video of my updated monome 128 interface =)
http://www.youtube.com/watch?v=uwfY9uzojcYstill working on a video showing the steps to getting started with Control's monome interface stuff.
Posted 2 years ago # -
That sounds great! I like those happy loops...
How'd you get that fancy striped rectangle at the bottom of the screen??? Is that an image that gets downloaded, or is it some secret CSS thing I don't know about?
Posted 2 years ago # -
hahaha, it's a button widget with the background and foreground colors the same brownish color, and then stroke and font set to the orangish color, and the label text set to all forward slashes and labelSize set to 48 or something. in fact i also used buttons for the column dividers, as i can't seem to make labels have a color (i may have messed up syntax when i was trying)
I'll post a link to it when I've done a little more tweaking =)
is it possible for Control to download and display images?! I've been thinking about how awesome it would be for control to be able to pull in visual info, like a waveform for the row from mlrv or something.
thanks for the kind words on the loops, i made them in bleep!BOX on the iPad =)
Posted 2 years ago # -
Hmmm... I just tried to put a background image in using CSS and it didn't work... not sure why.
There's a bug in the Label widget apparently; if you use
backgroundColorit will work, but using thecolorsarray won't. Thanks for pointing it out.When you get the interface finalized / posted let me know and I'll stick a blog entry up about it on the homepage. Thanks!
Posted 2 years ago # -
http://sk8dork.com/files/control/conome64.js
http://sk8dork.com/files/control/conome128.js
http://sk8dork.com/files/control/conome192.jsafter hours of tweaking those interfaces for the colors and stuff and testing each in mlrv 2.1, and comparing performance in haplome and touchosc (touchmonome) i think i'm finding touchosc to be the most responsive, which kills me! my "testing" comprised of trying to actually time multiple simultaneous presses that sound good and synced, with and without quantize, and also spazzing out on the buttons. when trying to just do well timed button presses i had the hardest time in Control, and touchosc just seemed perfect. haplome seemed to perform better than control but it had some drops that lowered the reliability, and i also think it was just easier to press the buttons since it's a full screen 64 layout vs the 128H i was using in Control and touchosc. when spazzing out on the buttons, Control would lag behind and buttons would be triggering after i stopped touching the ipad, haplome did the same thing but to a lesser degree, and touchosc didn't lag at all. it's crazy how low latency touchosc seems even going over the same wireless network and going through that touchmonome emulator max patch.
i have to go to sleep now, but i'll try going back to a barebones monome interface in Control, one without extra widgets and colors for looks. also, it seems like when requiretouchdown is false the multibutton widget will lose button presses? if you quickly press one button multiple times or press a couple buttons on the same row in quick succession the row will kinda crap out, as if you pressed stop, and an led will be stuck on until you press a button in that row again. requiretouchdown true seems to remove that problem all together.
Posted 2 years ago # -
Hmmmm... I'm not that surprised because touchOSC and haplome don't have to work on top of the web layer, but let me think about it and see what type of optimizations I can come up with. Also, I'm guessing that using the 64 layout in Control will be more responsive than the 128 (and hopefully more equivalent to haplome), just due to having less widgets on the screen.
Thanks for the report! - Charlie
Posted 2 years ago # -
OK, I've been looking at the code and making some optimizations. I think the response can be a lot better. I'll keep working on it and post a sample interface (that will overwrite the multibutton widget) sometime this weekend.
Posted 2 years ago # -
I look forward to the optimizations! I really like the possibilities with Control
Posted 2 years ago # -
well, I'm not quite ready to post code yet, but I have had a lot of luck with the optimizations. Basically I converted the MultiButton to use the Canvas HTML tag and am getting much better response times with larger numbers of buttons. I'm working on getting it to a state where I can post it... in the next couple of days for sure. - Charlie
Posted 2 years ago # -
OK!!! Ronji, let me know how this compared to TouchOSC. It might still be slower but it should be much closer.
http://charlie-roberts.com/Control/interfaces/conome.js
Besides the new MultiButton widget I only changed two lines in your file:
"onvaluechange": "PhoneGap.exec('OSCManager.send', this.address, 'iii', this.lastChanged.row, this.lastChanged.column, this.lastChanged.value);",and added:
"shouldUseCanvas":true,Cool. Let me know how it goes. - Charlie
Posted 2 years ago # -
One more line to add in the window.changeAddresses function:
'monome.address = window.oscPrefix + "/press";'
I updated the file accordingly.
Posted 2 years ago # -
oh my god that seems incredibly faster! i was so excited about the improvement i had to post this even before i've tested it by actually controlling something! =) !!!
thanks!
also, nice little comment at the beginning =) i merely customized your original monome emulator interface with colors, i don't know if i can take credit for that being any more original than yours =)
***
ok, after testing, it seems like there are issues sending button presses. it seems 100% consistent so far that the group stop buttons (1-4 top row, or 0-3 if you're that nerdy) will only turn the led off on the first press and finally stop the group on a second press. similarly if you start a pattern, record it, and try to stop it you have to press the pattern button twice quickly or it won't stop. there is also some weirdness with pressing a button multiple times in succession, like the second button press may not be registered if you're too quick, and by too quick i mean not really that quick, but quick enough to not register. i could take a quick video of this if you wanna see. there is still a little catchup played if i go "nuts" swiping across the grid, but i don't know how that would work out on a real monome, so that may not be solvable to an extent? this is with or without quantize.haha, and i just found out that if i load up another multibutton widget, or perhaps just another monome emulator, after using your updated 128 interface, it won't send/receive button presses (act like a monome) but has the nice new multibutton widget. if i kill control from the multitasking shelf and load up that second interface it is using the stock multibutton and works like it used to (with the relatively slower response).
alas, there is no weird voodoo solution when switching from an old multibutton to the new multibutton, which i guess is good. the feedback is still fast but the press recognition is still funky.
Posted 2 years ago # -
can't edit that post anymore, which is probably for the best =p
also with more testing: it seems like the "problem" with unrecognized presses is related to led state? if i follow a lit led down the grid as it plays, and press it when it's lit, it won't register as a press. like if a sample, a lit led crosses into the 9th button, and shortly after but while it's still lit i press it, instead of retriggering at that position it just moves on down the line like i never pressed it. this is the same with the group stop buttons on the top row: they're on if the group is playing, and the group won't stop until you've pressed it after the led goes out - the second press. i was confused about how the send button would consistently turn on and off on each press as it should, and it's because the send button doesn't light up while it's on, which could be a bug in mlrv. alas, maybe this will be easy for you to fix?
Posted 2 years ago # -
Hmmm. Well, one problem solved at least. If you force quit the app and restart it the old multibutton behavior should be restored. I tried the new version with mlr and didn't have any problems, but I'll try it tomorrow using the steps you outlined and see what happens.
Yeah, I don't know what happens on a real monome either if you move your hands super fast...
Posted 2 years ago # -
OK, I updated the interface file so that it won't mess with other MultiButtons... basically I just gave the widget a new name. If anyone wants to experiment it won't screw up your other interfaces. Still looking into the problems ronji described... - Charlie
Posted 2 years ago # -
cool, that works!
btw, i just tested with mlr and it's doing the same thing. note: sometimes when triggering a sample the led on the button pressed doesn't stay lit like i believe a monome should, and instead when the sample moves to the next button that led is lit and the rest of the sample plays and lights up leds accordingly. when this happens, pressing the button multiple times works fine, as long as you press the button the instant when the led is not lit. an easy way to test this should simply be to press the group stop button, which should take only one press to stop the group, but with the new multibutton widget it takes two - the press when the led is not lit actually sending the press to the application to stop the group.
Posted 2 years ago # -
I definitely noticed some weird things happening with the group stop buttons; that gives me a great place to start looking. Thanks for the details.
Posted 2 years ago # -
OK! Fixed and hopefully perfected. I updated the same file as posted earlier in the thread:
http://www.charlie-roberts.com/Control/interfaces/conome.js
And it seems like the presses are being handled correctly, regardless of on/off state. Sweet!
Posted 2 years ago # -
it is perfect! thanks! now to add some other widgets to control stuff =) i definitely need to look into pages for making a rival interface to the touchosc layout i was working on
Posted 2 years ago # -
Let me know if you have questions about the pages... it's pretty easy. Just add an extra set of [] and put your other widgets inside of it. Then create buttons to switch back and forth using control.changePage(pageNumber). You can also use a slider a la TouchOSC but in my experience the buttons work better... with a slider you could do something like this (assuming there were 6 pages):
"range":[0,5], "ontouchend":"control.changePage(Math.round(this.value))",The trick is making sure you give changePage a whole integer value, not a number with a decimal.
Posted 2 years ago # -
I can't get this to work and I'm not sure what I'm doing wrong...here's what I've done so far.
1. mlrv 2.1 is set up to find my iPad at 10.0.1.7 (i have also tried this with an ad hoc network from my macbook)
2. using ports to mlr v: 8000 and from mlr v: 8080
3. used the prefix patcher that had been uploaded to this thread...edited my IP address...
4. have all destinations and receiving ports on the iPad set up appropriately (10.0.1.3:8000 and receive port at 8080)Anything I'm missing here? I'm getting the no such object message in the max window with every button press...
Posted 2 years ago #