[PD] OSC problem

[Csaba Láng]

Scott,
thanks a lot. Using the extOSC, Unity started to send me the OSC signal,
after using the magic solution for Windows problems, which is a simple
restart.
Now I have the only problem that sometimes the slash is missing for an
unknown reason but if I fix it, I am OK.

Thanks for all the solutions you guys suggested.

Have a nice day!

Popesz



On Tue, Feb 9, 2021 at 12:33 PM Scott R. Looney <scottrlooney at gmail.com>
wrote:

> hi Csaba - here's the screenshots, the patch may not do you any good, but
> i think you should get the idea from what it shows. docs on extOSC are
> good, though they don't refer to how you should receive it in PD, they do
> talk about TouchOSC i believe. you will need iemnet installed, but
> everything else should already be in vanilla.
>
> best,
> scott
>
> On Tue, Feb 9, 2021 at 2:48 AM Csaba Láng <langcsaba at gmail.com> wrote:
>
>> Scott,
>>
>> thanks for the Unity part suggestions. Screenshots are welcome, patch is
>> even better :)
>> Just to be clear you suggest both solution in one time: extOSC and the
>> udpreceive - oscars, or the udprevceive works already with the OSC I use
>> now from Unity.
>>
>> Will come back if tested the extOSC package for Unity, probably in 12
>> hours.
>>
>> Best,
>>
>> Popesz
>>
>> On Tue, Feb 9, 2021 at 10:55 AM Scott R. Looney <scottrlooney at gmail.com>
>> wrote:
>>
>>> hi Csaba - i have done a fair amount of work with OSC in Unity and i
>>> highly recommend the extOSC plugin for this (it's free).
>>> https://github.com/Iam1337/extOSC
>>>
>>> homemade OSC sounds cool but there are a lot of flavors and not all of
>>> them play well with PD. i tried a number of options and what worked on
>>> receive in PD was the following:
>>>
>>> [iemnet/udpreceive] (with the port set at loadbang) -> [oscparse] -
>>> [list trim] and then [route] to send it places.
>>>
>>> what worked on send to Unity was this: [oscformat (parameter) (value)]
>>> -> [list prepend send] -> [list trim] -> [netsend -u -b] (with the connect
>>> message to the address and port on loadbang).
>>>
>>> i'm sure that might sound kludgy and terrible to experienced folks but
>>> the receiving setup works perfectly for me and [netreceive] absolutely did
>>> NOT work, under any configuration. haven't tested the sending option but it
>>> did work in the past.
>>>
>>> happy to include a screenshot if you need it.
>>>
>>> best,
>>> scott
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Feb 9, 2021 at 1:09 AM Roman Haefeli <reduzent at gmail.com> wrote:
>>>
>>>> On Tue, 2021-02-09 at 09:52 +0100, IOhannes m zmölnig wrote:
>>>>
>>>> > PS: it would help *tremendously* if you could mention what you are
>>>> > actually using to receive OSC.
>>>>
>>>> But also what you are using for _sending_ OSC messages. I gather you
>>>> wrote something in Unity. Are you sending in UDP or TCP? If you are
>>>> unsure what do you use, I'd go for UDP as it less complex and it is
>>>> much more common in OSC world. Also, switching transport protocols
>>>> means switching whole concepts. My advice is to stick with one and be
>>>> clear about what you use.
>>>>
>>>> Roman
>>>> _______________________________________________
>>>> Pd-list at lists.iem.at mailing list
>>>> UNSUBSCRIBE and account-management ->
>>>> https://lists.puredata.info/listinfo/pd-list
>>>>
>>> _______________________________________________
>>> Pd-list at lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>>> https://lists.puredata.info/listinfo/pd-list
>>>
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list
>>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210209/9b18e3b1/attachment.html>