rdsamp and wrsamp not isopmorphic

Hi there, this has likely been discussed somewhere at length however I can't seem to find such a discussion and the documentation doesn't appear to cover this key limitation:

In short, if I call wfdb.rdsamp and then use the corresponding wrsamp method, typical programming conventions assume that the two methods should be isomorphic – whatever is read into memory by rdsamp should be sufficient and, by default, produce an identical output when wrsamp is called to process the in-memory object. However, as best as I can tell, this is not the case, which is very counterintuitive and breaks with standard programming conventions.

This key limitation doesn't appear to be covered in the documentation and, at minimum, it would seem it should be. Better yet, an example of what arguments to set to make them isomorphic should be documented. This assumes that the ideal (that they are isomorphic) is not possible, however, for the library UX, this seems something to strive.

I would send a PR myself, however, I'm actively running up against this issue and therefore do not currently have a solution to propose.

Beginnen Sie mit der rdsamp- und wrsamp-API-Dokumentation und reproduzieren Sie das gemeldete Round-Trip-Verhalten mithilfe der entsprechenden Lese- und Schreibaufrufe. Verfolgen Sie die relevante Implementierung und die bestehenden Tests, um festzustellen, ob die Einschränkung entfernt werden kann; andernfalls dokumentieren Sie die erforderlichen Argumente und ein funktionierendes Beispiel.