You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the program doesn't hang if stream.SetPlayingOffset(sf::Milliseconds(0)) is removed.
My guess is that when SetPlayingOffset() stops the stream, the call to Thread.Wait() never returns.
However it should return at some point; it's just slow in this case because of sf::Sleep(sf::Seconds(5)).
For the record, I encountered this bug while adding streaming to my Python binding.
Currently the API is very slow, and I was wondering why my program hangs when testing seeking with SetPlayingOffset().
The text was updated successfully, but these errors were encountered:
So the program blocks forever right after stream.SetPlayingOffset(sf::Milliseconds(0))?
I can't reproduce it on Windows, the program behaves the same with or without this line. I had to add a std::cout in OnGetData, because with pauses of 5 seconds every 4096 samples, we can hardly hear something and check whether the program runs or not.
Well this is embarassing, I can't reproduce it either. I guess I was too happy to find out why my binding hangs for no reason. :D I often get a segmentation fault when closing the program, however.
Example:
Note that the program doesn't hang if
stream.SetPlayingOffset(sf::Milliseconds(0))
is removed.My guess is that when
SetPlayingOffset()
stops the stream, the call toThread.Wait()
never returns.However it should return at some point; it's just slow in this case because of
sf::Sleep(sf::Seconds(5))
.Platform: GNU/Linux, SFML commit #e7256e3324a196bb1432786c678f195c9ffb982b.
For the record, I encountered this bug while adding streaming to my Python binding.
Currently the API is very slow, and I was wondering why my program hangs when testing seeking with
SetPlayingOffset()
.The text was updated successfully, but these errors were encountered: