This re-solves #264 which had been cancelled by commit ba50ee55aa1a4fcceb87460ec07fc03c3fc5365b
This is important if you need to support non-integer sample rates. Currently, the only way to make ezc3d to write analogs and points reliably is to specifically define the sampling rates as integers. Floats don't work.
While using floats for sampling rate may be weird (normally we set it as an int in the recording software), I can see value to support floats, for instance to synchronize two instruments that drifted over a common sampling rate that could be non-integer.
In my particular application (ktk), I need to generate c3ds from TimeSeries where the sampling rate is calculated dynamically based on a time vector. It will always be a float.
This re-solves #264 which had been cancelled by commit ba50ee55aa1a4fcceb87460ec07fc03c3fc5365b
This is important if you need to support non-integer sample rates. Currently, the only way to make ezc3d to write analogs and points reliably is to specifically define the sampling rates as integers. Floats don't work.
While using floats for sampling rate may be weird (normally we set it as an int in the recording software), I can see value to support floats, for instance to synchronize two instruments that drifted over a common sampling rate that could be non-integer.
In my particular application (ktk), I need to generate c3ds from TimeSeries where the sampling rate is calculated dynamically based on a time vector. It will always be a float.
Anyway this PR fixes it.
This change is