I’m using OSC protocol to send and receive controll messages over the network, but I was intrigued to see that OSC application sends two packages that are almost identical, changing just a few bytes.

first packet's payload:
<controll message bytes>, 0x00, 0x00, 0x00, 0x2c, 0x66, 0x00, 0x00, 0x3f, 0x80, 0x00, 0x00 

second packet's payload: 
<controll message bytes>, 0x00, 0x00, 0x00, 0x2c, 0x66, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00

I’d like to know if anyone knows why that is

I searched in OSC’s documentation but had no success