Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AudioPlayer.currentIndex does not match AudioPlayer.playbackEvent.currentIndex #255

Closed
suragch opened this issue Dec 10, 2020 · 2 comments
Closed
Assignees
Labels
1 backlog bug Something isn't working

Comments

@suragch
Copy link

suragch commented Dec 10, 2020

In my example here I discovered that _player.currentIndex was not incrementing when the song updated. It just stayed at the initial index. However, when I updated it to _player.playbackEvent.currentIndex it did work, that is, it returned the true index of the current song in the ConcatenatingAudioSource. I would have expected both to return the same value.

This behavior was observed on macOS.

Note: I'm submitting a bug report that does not follow the guidelines. The reason is I don't have time to make a full reproducible example. It's also possible that the bug is in my own code. I understand that this will result in the issue being closed immediately. However, I'm writing it up to ping @ryanheise and so that there is a record of it. No action is expected since the workaround mentioned in the first paragraph is sufficient.

@suragch suragch added 1 backlog bug Something isn't working labels Dec 10, 2020
@github-actions
Copy link

Oops, it appears that your issue did not follow the template and is missing one or more required sections. Please open a new issue, and provide all required sections and information.

FAQ:

  1. Do I really need to submit a minimal reproduction project for a bug? A: Yes. I prioritise bugs secondarily on how many people are affected, and primarily on whether the bug report is complete, in the sense that it enables me to immediately reproduce it and start working on a fix. If a bug is important to you, the best thing you can do is to provide all requested information ASAP so that I can start looking into it ASAP.

  2. I think I supplied all required information, so did the bot make a mistake? A: The bot only checks the section headings, so when you post a new issue, make sure you leave the section headings intact. (Note that because of this, it is even possible to trick the bot by including only the section headings, and then not providing the requested information under each heading. This is frowned upon, and the issue will be closed manually.)

@github-actions
Copy link

github-actions bot commented Nov 5, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with just_audio.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 backlog bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants