search

xioTechnologies / NGIMU-MaxMSP-Example

3 stars 3 forks source link

TimeTag issue Max MSP #1

Open BMoens opened 2 years ago

BMoens commented 2 years ago

Hi, I'm unable to extract the timetag from an incoming packet using MaxMSP (8.2, win10).

The regular udpreceive does not include the timestamp.

Using Max' "udpreceive x CNMAT" object, i'm able to receive the fullpacket (binary) stream; and using the OpenSoundControl objects from ODOT (in package manager, 'cnmat' -> list of tools for OSC) I should be able to retreive the NTP timetag. However, the resulting timetag is always '0 0' - even though in the GUI executable it is correct.

Minimal example: ----------begin_max5_patcher---------- 701.3ocyV00aaBCE84Do9evhmSx7mPXZOro77Ven8sopJJ314pfMx1jkpp8e eFaflk1PR6Pa8gDiubM2y4fOWyimMcRzMpsbSD3ifuClL4QWjI9XMQlzEXRT Y1170YFehQ4pxRtzFMq8lV9Vq+FeBjqzZdtEX3RiRCJxrY8oIJ7Iot494Hbe zpLa9ODx6ttYcAbPHvEvY.BC0LfX9YX2+fq5VkrtTHWysd.g1Ipp11EF5i9q yl1L5FlMFDTyM0qsFfPBrhRtM6N.D.eQNBGjiXpmULx+INJ4+zgxmSQKXcev PgrOTwCfNJ5IzsCSWNDQSV5YVRfmo9I3WKMQuYZVxMlr63OmmeHrE0.bZdbb ZBEL2cEKkRX9PKYLeHDIFSSaBQvvTTSnzTJjx.yIIKRHoIwtfH7BVLNIMFPP KPXLAsDffn3ELRJlF2W90BIOWUK8Xf7J04jA2PE68Ljv1p3jlAZ5AEZ7+Lg9 7KVcoyob4dNkSjyrg3LFF5Pf7rEAwGY20nS5CYhNuhKuv8ZtXkRZ0pgbTyB+ dRkdYcfNjNv7drkvfXfdadLx3qBWrZdWSxOeqVUBj1p9zL1GV6UgnB9sYtlp GVjNp3Lnyns4JJw6PPT36ldP+cVCxIPZLiEHM88h0ntnxgRtXC2sgER.q91W +xkuVpiNtaHzHDQIiya6vp88u2+qk7Pn4F6IGFUsNuiGsmSB1AFEbiUHyrBk bmjbakAHvUGV2O4xQCOogKWKlFoxgOV4X+IlT5Bt9HeGyoCfjSQeIip9dTBu On5YLZDP.5THL8EeC2teNqpZCWaZWQnRNe78JOFWNKLWHCygg4Z9FQ2RB1mn LsyEZcVvZcnm9131SrhJUNFKqEcjtgqMk12+eeujLqLr9R2ABBHryn6zDs6K xOzYFgz6k0m3mueTyC0TkEjNeeqyl5R42fV9f2F -----------end_max5_patcher-----------

Thanks!

xioTechnologies commented 2 years ago

I am not able to test this any time soon. If the GUI and other applications display the correct time tag but the Max object does not then it sounds like the issue is with the Max object.

Some OSC receiver implementations will not expose the time tag but will instead buffer corresponding messages until the time tag is equal or greater than the current time of the computer. This is in-line with the OSC specification which describes the time tag as controlling when an OSC message should be executed. Perhaps this or something like this is going on with your system.

BMoens commented 2 years ago

hmm, thanks for the feedback, it is indeed a max implementation issue I suppose. However, to clarify, the time tags included in the osc messages with sensor data, does it not indicate the local time at which the sample was captured on the sensor - as implied by the manual: "All data sent from the device is sent as a timestamped OSC bundle containing a single OSC message. "?

xioTechnologies commented 2 years ago

From the user manual: "The timestamp for each measurement is created when the sample is acquired."