Processing 4.4.7 with oscP5 0.9.9 seems to handle OSC Type Tags "T", "F", and "N" correctly.
see also about Pure Data (Purr Data):
https://gist.github.com/cleemy-desu-wayo/9d314e448b9f0edffcb2ffa503c3e824
see also about SuperCollider:
Processing 4.4.7 with oscP5 0.9.9 seems to handle OSC Type Tags "T", "F", and "N" correctly.
see also about Pure Data (Purr Data):
https://gist.github.com/cleemy-desu-wayo/9d314e448b9f0edffcb2ffa503c3e824
see also about SuperCollider:
the following preparations are required:
maoudamashii-inst-guitar08.wav from https://maou.audio/se_inst_guitar08/maoudamashii-inst-guitar10.wav from https://maou.audio/se_inst_guitar10/maoudamashii-inst-guitar13.wav from https://maou.audio/se_inst_guitar13/
In SuperCollider 3.13.0, for receiving OSC messages, simply using OSCdef seems to handle OSC Type Tags "T", "F", and "N" correctly.
When sending, I don't know if there is an easy way like sendtyped in Pure Data (if anyone knows, please let me know).
see also about Pure Data (Purr Data):
https://gist.github.com/cleemy-desu-wayo/9d314e448b9f0edffcb2ffa503c3e824
in Pure Data, it appears that OSC Type Tags "T", "F", and "N" can be sent using sendtyped.
server_python-osc_t-f-n.py (here) or something for receiving OSC| #!/usr/bin/env python3 | |
| # | |
| # client side test for OSC Type Tag "T", "F", and "N" with python-osc | |
| # | |
| # see also: https://github.com/attwad/python-osc | |
| from pythonosc import udp_client | |
| import time | |
| ip = "localhost" # change this line appropriately |
| ################################################################################ | |
| # hash list | |
| # by cleemy desu wayo (@cleemy4545) | |
| # 2022-09-23 02:15 JST | |
| # | |
| # format: | |
| # <byte size>,<sha256sum> | |
| # | |
| ################################################################################ | |
| 25,850291cd378397199de6a51c5de8ff9a25f5cb2e0e72daf6a19591344d93e45f |