Setting Tone.Transport.loopEnd does not effect the loop duration of the Tone.player. I'm not sure if this is a bug or if it is intended. If it is intended, then for most people I think that this behavior is confusing and unexpected. There might be a way to modify variable names, documention, tooltips that appear in the IDE when hovering, etc. to improve the usability of the api.
To replicate:
Create a new player via `const player = new Tone.Player(...)
Set its loop property to true.
Set Tone.Transport.loop to true, and modify Tone.Transport.loopEnd to an arbitrary value
Result: the loop duration of the player is unaffected.
Also, I tried setting player.loopEnd to an arbitrary value, but it too is ignored.
Johnrobmiller
commented
1 week ago
Setting Tone.Transport.loopEnd does not effect the loop duration of the Tone.player. I'm not sure if this is a bug or if it is intended. If it is intended, then for most people I think that this behavior is confusing and unexpected. There might be a way to modify variable names, documention, tooltips that appear in the IDE when hovering, etc. to improve the usability of the api.
To replicate:
loopproperty to true.Tone.Transport.loopto true, and modifyTone.Transport.loopEndto an arbitrary valueplayeris unaffected.Also, I tried setting
player.loopEndto an arbitrary value, but it too is ignored.