There are a couple of things I'd like fixed in a future release for LoopPoints:
RelativeFilePath is capitalized camelcase, which is inconsistent with the lowercase camelcase sampleLoopStart and sampleLoopLength. Oops.LoopPoints as a name is a misnomer at this point. It doesn't contain just loop points; it now contains a relative file path field and the Compensate for Frequency checkbox. This should probably be changed to something like Settings.
Since this would be a breaking API change, migration to a new object called Settings would happen first, waaaay into the future. Heck, it may not even be worth it at this point, as these are largely settings developers won't change or reference during runtime anyway. It's largely a UX thing.
This is very low priority and definitely won't happen for at least a few months. Maybe in a new major release. But it's not a high priority.
There are a couple of things I'd like fixed in a future release for
LoopPoints:RelativeFilePathis capitalized camelcase, which is inconsistent with the lowercase camelcasesampleLoopStartandsampleLoopLength. Oops.LoopPointsas a name is a misnomer at this point. It doesn't contain just loop points; it now contains a relative file path field and the Compensate for Frequency checkbox. This should probably be changed to something likeSettings.Since this would be a breaking API change, migration to a new object called
Settingswould happen first, waaaay into the future. Heck, it may not even be worth it at this point, as these are largely settings developers won't change or reference during runtime anyway. It's largely a UX thing.This is very low priority and definitely won't happen for at least a few months. Maybe in a new major release. But it's not a high priority.