Don't send volume in play op if we are using filters #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NachtRaben
changed the title
|
Can we get this merged? @freyacodes |
Owner
|
I don't like this. This can cause some unexpected behavior.
The volume setting is also no longer deprecated. The disadvantage of filters is that they take a bit of time to come into effect, which is uncomfortable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Volume will get overridden if we call LavalinkPlayer.playTrack() if we set the volume via filters as the Deprecation specifies. This should resolve the issue and not send the volume if the filters are initialized.