-
Notifications
You must be signed in to change notification settings - Fork 856
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
windows [v1 rc2]: play function on remote freeze UI #1118
Comments
Please follow the issue template to include necessary information. |
Done |
did you manage to run the url of an mp3 with HTTP? |
with https yes |
I tried with http with security (https) and I don't success |
any fix for this. My UI freezes completely when playing musics of longer duration with url as source playing youtube music. |
…g the source (#1469) # Description Add a callback when the player has prepared its source, which is tangled to the asynchronous `setSource` method, to improve experience, when player should actually play and not wait for the player to prepare / load the source. ## Related Issues Closes #1118 Closes #1384 Closes #1359 #1191 flutter/flutter#126209
The play function may be async, but it still freezes the UI until play start.
Full Description
When a widget call play function of a
player
instance, with a remote source, this is freezing the UI until the song start to play.This should not happen as this function is async.
This mean I can't scroll in listview, move the window or click anywere in app until the playing start.
Tried with await or not, even with a FutureBuilder for the UI, still freezing a few seconds until playing.
Code to Reproduce
Log Errors
No errors, just an unexpected freeze.
Files/URLs/Sources
UI Call: https://git.p2p.legal/poka/fipy/src/branch/kplayer2audioplayer/lib/screens/home.dart#L419
Controller action: https://git.p2p.legal/poka/fipy/src/branch/kplayer2audioplayer/lib/providers/home.dart#L103
Screenshots
Just image a UI freeze when choosing a song to play.
Platforms
Tried on Windows 10.
The text was updated successfully, but these errors were encountered: