Currently timestamps are created using np.linspace() going from 0 to end of the recordings. If there is missing data or pauses in the recording, then the created timestamps are incorrect. Address this issue by using fragmented timestamps in .nex5 file