Fix a bug relating to changing the range of a data source.
The issue here is that the code is trying to maintain the absolute position of the loop point. The problem with this is that the absolute position of the loop points could fall outside the new range which would then result in no audio being read. This becomes an issue because it would effect data sources even when the loop point was never actually explicitly set. From these users perspective, changing the range completely breaks their audio. The new system simply resets the loop points. This works for users who are using the default loop points (the majority of cases). For those who are explicitly setting a loop point, they simply need to reset their loop points after changing the range. This is not really an issue, because loop points are relative to the range, which means a change in the range would most likely warrant a change in the loop point anyway.
Showing
Please register or sign in to comment