-
Notifications
You must be signed in to change notification settings - Fork 60
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
skipping songs. dec->channels
is totally off
#37
Comments
It looks like the channel number is totally off and also changes. This is strange. I thing the decoder channel number should not change. This indicates memory corruption, i.e. some buggy code overwrites the wrong memory. Such bugs are very hard to find. Can you send me the song via mail? You said that you tried to play the same song again later and it worked? Have you ever had this problem before? |
sure.
|
What same error? The main error indicating that there is something wrong was the sample rate converter creation error. It couldn't be created because the number of channels was way off (I thing the converter probably only handles 1, 2, 4 and maybe 5 or 6 channels, not more). The warning that the peeked stream is not the real next stream is something else. Peeked streams are streams which were preloaded internally by the player engine (the part in C++). The player engine asks the Python part which songs probably will come next (= peeked streams) and preloads them. Once the player engine then advances to the next song, it tries to use some of the preloaded songs. If that warning occurs, it means that the player engine got a different song than what it expected and preloaded. This might happen if you drop the song to the queue right to the top. I think the Python part should tell the player engine in that case that it should reload the peeked streams. It seems that it didn't or it had too less time (because you right away clicked on nextSong). Maybe that is a bug - but only a minor one. The readOutStream warning about too less samples available just means that. That happened because the song was not properly preloaded and so it takes a small time to load enough samples. In the meanwhile, the soundcard, which indirectly calls readOutStream, has too less data available to play. That might result in a small hiccup in the sound output. |
okay. then i mixed something up. thx for the info. the peeked stream warning:
i think you are right. i can only reproduce the warning if a song is dropped to play next. i was not able to duplicate the sample rate converter creation error. |
happened again. same song. again put into first place in the playlist
|
just had a song skip. started playing and 5-10 seconds in, it skipped to the next song.
quite sure that i dragged the song (Jake Bugg - Seen It All) into the playlist via search window.
was not able to reproduce the skipping.
log file:
The text was updated successfully, but these errors were encountered: