Sorry to have caused this semantic change without documenting it correctly. It happened during the recent changes leading to v3.22 and the current behavior is, what the updated Beatport web source required.
I didn't think of the way you're using the command. I've noticed that you've already released a fixed version of your script. Does this include a working workaround for the issue described here or are you still looking for a solution?