...that deal with pure data
You are not logged in.
Hey guys,
Just discovered this forum for PD. Great info and valuable documentation.
I need help with this patch that i created for ToucOSC with Pd extended. ( actually a modification of the Keys layout that comes with TouchOSC )
Its basically a 5 page layout. 1 to 4 being a midi keyboard controller of one octave for each page that can trigger any note out for Ableton Live VSTi's ( for my use ), and the last page being a bunch of controllers.
Problem is, the first and second page are working as they should, but the third page triggers wrong info from the TouchOSC interface on ipodtouch. when i play C# it reflects as being a G in PD and so on...like all the notes are not properly assigned. The 4th and 5th page not triggering at all. Nada, zilch!
Im quite new to PD extended and its language, ive done some research on the net, and im feeling quite lost in all of this. Im sure you know the feeling...so ive included my patch here. If anybody can have a look, and maybe tell me what ive done wrong, and can indicate me as how i can correct the matter, that would be immensely appreciated.
Cheers,
VP
Last edited by vonpranke (2009-11-02 12:52:29)
Offline
ha ha,
i think you have forgotten the /3 in your first OSCroute object. at the moment it just has 1,2,4,5
is that it?
Offline
Doh! Ok i think i need to go outside and breathe some fresh air! :)
I changed it and is still doesnt respond....
Last edited by vonpranke (2009-11-03 08:15:19)
Offline
a good idea for debugging, is to use the [print] object. that way you can check what messages and values are being sent down your cables.
in this case, i'd suggest to connect a [print] to an offending outlet of the first [OSCroute] . then read what messages are being sent to the console. if they look like they have errors, then the problem lies further up the chain (which in your case, probably means that they are coming from outside of pd). however, if the ouputs of the first oscroute are ok, then the errors must be coming from further down the chain. so, to investigate the next oscroute object's output, connect a print to that and see what it sends to the console.
oh, and don't forget to delete the print objects as you go!
Offline