(Bug?)Sample editor slightly changing sample rate of imported sample upon resaving it

[TheRektafire]

So I'm making some instruments to use for an n64 game made with pyrite64 and I'm currently working on pads, so I'm exporting my samples intentionally too long so I can set loop points and trim in milkytracker wherever I would like. I imported one of my pad samples, set up my loop points, trimmed the part after the loop, and saved it again. After saving the new trimmed sample I checked the sample rate and it went from 22050hz for the original to 22046hz for the new version. Obviously a difference of 4hz isn't going to exactly be that noticaeble but it still seems like a bug since that's not the sample rate I imported the original at, I would expect milkytracker to save the new copy of the sample at the original rate and bit depth.

[coderofsalvation]

hm that's odd.
Are you talking about the sample-editor (save-button)?

[TheRektafire]

hm that's odd. Are you talking about the sample-editor (save-button)?

Yeah the "save" button in the sample editor

[8bitbubsy]

While I'm not entirely sure how MilkyTracker works in this regard, this may not be strange at all.
When MilkyTracker imports a sample from the outside world, it most likely sets the finetune and relative note so that note C-4 ("middle-C") results in the closest approximation of the imported sample's original frequency. In other words, I think this is a limitation of finetune granularity, and when saving the sample, it probably calculates the new rate based on the tracker sample's finetune + relative note.