Timothé

Indeed, another alternative could be to have a set of flags to: - cap number of messages held in memory (easy, can lead to unexpected behavior) - discard messages scheduled...

Yup that would also work, the purpose of that library was to be somewhat useful and abstract that away from the clients but offering them a way to get the...

1. /filter is just an example, MAX is going to send OSC packets to a URI, that's the path part of it, I don't know how MAX works but you...

Glad this was helpful. This library doesn't impose any special structure on your code, you can have a single class that does the server listening and client forwarding in that...

The `print` function that you map to the dispatcher is a function that will be called with the osc params from MAX as arguments each time a new message comes...

You can pick whatever you want for your client port, best to make it configurable by users using an environment variable or a flag but that's up to you.

Sure thing, dispatcher.map accepts an optional list of arguments at the end to pass static data like that: https://github.com/attwad/python-osc/blob/master/pythonosc/dispatcher.py#L70 So it should be: dispatcher.map("/filter", myfunc, myip)

You could use a default handler: https://github.com/attwad/python-osc/blob/master/pythonosc/dispatcher.py#L198

Sorry I'm not sure I follow anymore, if you end up dealing with OSC from raw UDP packets then you basically bypass what this library is about so I'm not...

Ah ok, well you can look at the functions in https://github.com/attwad/python-osc/blob/master/pythonosc/parsing/osc_types.py#L49 for example but this is not really a use case supported by this library so you might not find...