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

When position of the player is changed using seekAt, it takes a lot of time to buffer for larger audio files #1345

Closed
sunpreet-dalmia opened this issue Sep 28, 2024 · 1 comment
Assignees
Labels
1 backlog bug Something isn't working

Comments

@sunpreet-dalmia
Copy link

Which API doesn't behave as documented, and how does it misbehave?
await audioPlayer.seek(Duration(seconds: sec));
When position of the player is changed using seekAt, it takes a lot of time to buffer for larger audio files.

Expected behavior
When we seek at a particular duration, it should start playing the audio from that position immediately. However, it takes a few minutes of time to do that.

Smartphone (please complete the following information):

  • Device: Android
  • OS: Android 13

Flutter SDK version

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.22.2, on Microsoft Windows [Version
    10.0.19045.4894], locale en-IN)                               
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.2.0)  
[√] Android Studio (version 2021.2)
[√] Android Studio (version 2022.2)
[√] VS Code (version 1.93.1)       
[√] Connected device (4 available) 
[√] Network resources              
                                   
• No issues found!           
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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 backlog bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants