If you assign /fader1 from bank 1 to the controller nr (the number to the left of the dropmenu in the osctouch patch), you should be able to use the router in VPT to control whatever parameter you like, based on that controller number. So basically you assign the different osctouch values to controller numbers in the new patch, and then you can use the router as you would with midi, lfo, dmx or other osc.
Your touchosc app must be sending to port 6665, the vpt touchosc patch is communicating directly to the router, so it is important that the patch is opened in VPT.
hope this helps.
hc
On Dec 5, 11:43 pm, Leonardo Souza <quilo...@gmail.com> wrote:
> I've set my outgoing port in TouchOSC to 6665 and the host to what I > believe is the correct IP along with the steps you have discussed above, > and still no luck getting any data from the new iPad. Is there a specific > layout within TouchOSC that works best? How do I determine if I have > entered the proper IP for the host.
> > I've set my outgoing port in TouchOSC to 6665 and the host to what I
> > believe is the correct IP along with the steps you have discussed above,
> > and still no luck getting any data from the new iPad. Is there a specific
> > layout within TouchOSC that works best? How do I determine if I have
> > entered the proper IP for the host.
Getting much, much closer. When I open the TouchOSC interface and the patch that you just sent me, I do now see the values from TouchOSC. By default (as you know I'm sure,) /fader1 is assigned to Control number 1, however when I go to the router and test a simple fade nothing happens. Any thoughts on what might be the missing link?? Again, thank you for your patience HC. I am absolutely going to be donating for this software and your help. I'd also be willing to post pictures or videos of my hypermedia installation next week.
Sorry - been meaning to follow up for quite some time. To be honest I'm not sure where I was making a mistake at the time. What I do know now is that following your instructions of opening the listenport6665 patch and TouchOSC interface through VPT then launching TouchOSC on the iPad and using the router seems to work every time - even when I don't necessarily do it in that order.
I need a little help. I've worked through the notes in this thread trying everything that I've read, but I cannot get VPT 6 to respond to OSC messages. I'm wondering if I'm missing something obvious. My real goal is to send OSC from a Microsoft.Net application, using a OSC library. I am also trying the TouchOSC just to see if VTP will react to any type of OSC messaging. No luck so far.
I have the patch "listen_port6665_b" open and I can see the messages coming in from my iPad. VPT is receiving messages like...
/1/fader1 0.91667
I'm using the router to map 1 to Layer1 Fade, but its not working.
Is the /1 before the /fader1 the problem?
If so, I don't see a way to get rid of the /1 in the TouchOSC app.
On Monday, 5 December 2011 18:28:33 UTC-5, hc wrote:
> If you assign /fader1 from bank 1 to the controller nr (the number to > the left of the dropmenu in the osctouch patch), you should be able to > use the router in VPT to control whatever parameter you like, based on > that controller number. So basically you assign the different osctouch > values to controller numbers in the new patch, and then you can use > the router as you would with midi, lfo, dmx or other osc.
> Your touchosc app must be sending to port 6665, the vpt touchosc patch > is communicating directly to the router, so it is important that the > patch is opened in VPT.
> hope this helps.
> hc
> On Dec 5, 11:43 pm, Leonardo Souza <quilo...@gmail.com> wrote: > > Thanks.
> > I'm not making it right. My osc doenst reach my vpt instance. > > How did you configure it?
Are you using the touchOSC interface that I made? You canīt use
TouchOSC directly with VPT, you need to use this patch as an
intermediary. This filters out the /1,/2 etc and you set up the
control mappings in this interface, not in the router in VPT.
in the manual or in the help for osc and router you should see how to
configure the osc messages so VPT will understand them.
On Oct 13, 5:55 pm, Todd Brassard <toddbrass...@gmail.com> wrote:
> I need a little help. I've worked through the notes in this thread trying
> everything that I've read, but I cannot get VPT 6 to respond to OSC
> messages. I'm wondering if I'm missing something obvious. My real goal is
> to send OSC from a Microsoft.Net application, using a OSC library. I am
> also trying the TouchOSC just to see if VTP will react to any type of OSC
> messaging. No luck so far.
> I have the patch "listen_port6665_b" open and I can see the messages coming
> in from my iPad. VPT is receiving messages like...
> /1/fader1 0.91667
> I'm using the router to map 1 to Layer1 Fade, but its not working.
> Is the /1 before the /fader1 the problem?
> If so, I don't see a way to get rid of the /1 in the TouchOSC app.
> Any help would be appreciated
> Todd
> On Monday, 5 December 2011 18:28:33 UTC-5, hc wrote:
> > If you assign /fader1 from bank 1 to the controller nr (the number to
> > the left of the dropmenu in the osctouch patch), you should be able to
> > use the router in VPT to control whatever parameter you like, based on
> > that controller number. So basically you assign the different osctouch
> > values to controller numbers in the new patch, and then you can use
> > the router as you would with midi, lfo, dmx or other osc.
> > Your touchosc app must be sending to port 6665, the vpt touchosc patch
> > is communicating directly to the router, so it is important that the
> > patch is opened in VPT.
> > hope this helps.
> > hc
> > On Dec 5, 11:43 pm, Leonardo Souza <quilo...@gmail.com> wrote:
> > > Thanks.
> > > I'm not making it right. My osc doenst reach my vpt instance.
> > > How did you configure it?
I'll reply for Todd since we are working on the same project. We ended up getting it all to work. We used the patch to get it to work. Our other problem was how we were crafting the messages in .NET as well as a bug with sending the messages across the network. We had some funky demo code that we were using for testing that would only send to local host even if you specified an IP.
In the end, we got it all to work. Then we realized we didn't have enough time to finish this project within the short timeline so we opted for a non -interactive exhibit. Before we stopped working on it, we did have a Kinect interface that used spacial points and specific body movements as well as voice commands to control video output through VPT. It might be a project we revisit. We learned a lot though.
On Wednesday, October 17, 2012 5:16:51 AM UTC-4, hc wrote:
> Are you using the touchOSC interface that I made? You canīt use > TouchOSC directly with VPT, you need to use this patch as an > intermediary. This filters out the /1,/2 etc and you set up the > control mappings in this interface, not in the router in VPT.
> in the manual or in the help for osc and router you should see how to > configure the osc messages so VPT will understand them.
> On Oct 13, 5:55 pm, Todd Brassard <toddbrass...@gmail.com> wrote: > > I need a little help. I've worked through the notes in this thread > trying > > everything that I've read, but I cannot get VPT 6 to respond to OSC > > messages. I'm wondering if I'm missing something obvious. My real goal > is > > to send OSC from a Microsoft.Net application, using a OSC library. I am > > also trying the TouchOSC just to see if VTP will react to any type of > OSC > > messaging. No luck so far.
> > I have the patch "listen_port6665_b" open and I can see the messages > coming > > in from my iPad. VPT is receiving messages like...
> > /1/fader1 0.91667
> > I'm using the router to map 1 to Layer1 Fade, but its not working.
> > Is the /1 before the /fader1 the problem?
> > If so, I don't see a way to get rid of the /1 in the TouchOSC app.
> > Any help would be appreciated
> > Todd
> > On Monday, 5 December 2011 18:28:33 UTC-5, hc wrote:
> > > If you assign /fader1 from bank 1 to the controller nr (the number to > > > the left of the dropmenu in the osctouch patch), you should be able to > > > use the router in VPT to control whatever parameter you like, based on > > > that controller number. So basically you assign the different osctouch > > > values to controller numbers in the new patch, and then you can use > > > the router as you would with midi, lfo, dmx or other osc.
> > > Your touchosc app must be sending to port 6665, the vpt touchosc patch > > > is communicating directly to the router, so it is important that the > > > patch is opened in VPT.
> > > hope this helps.
> > > hc
> > > On Dec 5, 11:43 pm, Leonardo Souza <quilo...@gmail.com> wrote: > > > > Thanks.
> > > > I'm not making it right. My osc doenst reach my vpt instance. > > > > How did you configure it?
To calrify, i am not seeing any data in VPT. Should i automatically be seeing fader one move when i do so on touch osc? I know i program the commans via the interface opposed to the router.
For anyone who has problem with TouchOSC and VPT in the future my advice is to not use the OSC interface patch. Instead create your own layout in TouchOSC editor and give your controls the values you wish. The correct format for these messages can be found here : http://nervousvision.com/vpt/VPT_osc_overview.htm Making sure that TouchOSC is sending to port 6666 as VPT requires.
