I know about seconds, was just asking for maybe 3 or atleast 2 times per minute.

With what purpose?

We can't transmit them later, by sending a CT message we're telling the receiver that "Right now it's EXACTLY 12:28". So if we send that again 30 seconds later the receivers clock would be lagging by 30 seconds.

But, what would the purpose be of sending it more often? What are you trying to achieve?

Because if i tune in on station in exactly 23:45:04 the clock will not be shown on display for next 56 seconds.
That clock does not show seconds anyway, so atleast 3 refreshes per minute would be nice, one refresh ofc exactly on minute change.

Oh. I have never seen a radio that actually uses this. I always figured receivers would use it to set their internal clock, not to display what the station that you're tuned into transmits. If it's display-only it indeed doesn't matter, but if the receiver sets its clock it does.

Edit: I looked up the specs. They explicitly say that you must send it once per minute, exactly on the minute mark. So we cannot transmit it multiple times per minute without breaking the standard.

When buffers overflow in Beta 35 and later, it's a harsh popping and stuttering sound for a few seconds before resetting. In beta 31 it's almost completely transparent when the buffer overflow happens, going quiet for a fraction of a second instead.

ASIO, stand-alone, new gui x64. Also happens with Enterprise. Is this an anomaly of the new I/O layer?