Hi,
I noticed that pytone has problems with truncated music files. Playing some files that hadn't finished yet downloading, pytone uses the original play-length, but when it gets to the end of the file (somewhere half of the original length) it continues (but plays a different song).
So suddenly it switches to (what seems to be) a random other song from the playlist. Without fading. I also had a crash once that I think is related to truncated files)
-- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
Hi Dag,
On 19.06.05, Dag Wieers wrote:
I noticed that pytone has problems with truncated music files. Playing some files that hadn't finished yet downloading, pytone uses the original play-length, but when it gets to the end of the file (somewhere half of the original length) it continues (but plays a different song).
I just played around a little bit with truncated songs and could not reproduce any serious problem. Maybe it was because the song was longer than the length stored in the database. If I understood you correctly, this was probably the opposite in your case?
So suddenly it switches to (what seems to be) a random other song from the playlist. Without fading. I also had a crash once that I think is related to truncated files)
Did it crash with a traceback or did it segfault?
Jörg
On Wed, 22 Jun 2005, Joerg Lehmann wrote:
Hi Dag,
On 19.06.05, Dag Wieers wrote:
I noticed that pytone has problems with truncated music files. Playing some files that hadn't finished yet downloading, pytone uses the original play-length, but when it gets to the end of the file (somewhere half of the original length) it continues (but plays a different song).
I just played around a little bit with truncated songs and could not reproduce any serious problem. Maybe it was because the song was longer than the length stored in the database. If I understood you correctly, this was probably the opposite in your case?
Well, I'm not sure. The length in the database was most likely shorter than what was on disk at that time. And the length of the real (completed) song is longer than both of course. I'm not sure what is being considered and what is supposed to happen when i.e. the database length is reached.
What I know happened was that before the song ended, it suddenly started playing a (seemingly random) music file from a (seemingly random) offset. Don't know what length is shown on screen (for the progress bar) or what length is used during playing. There must be some mix-up.
So suddenly it switches to (what seems to be) a random other song from the playlist. Without fading. I also had a crash once that I think is related to truncated files)
Did it crash with a traceback or did it segfault?
Nope, it didn't crash, it just seemed to play something randomly from another song (and not even from the beginning of that song).
I can't reproduce it now since all the downloads have finished, but I noticed it several times since it was a big download with a lot of music files (i.e. 10% of the playlist I had available and the download took more than 4 days in total, bittorrent downloads all files in parallel so they reach 100% about the same time at the end of the file roughly)
If you can't reproduce it, drop it. I'll try to investigate if I happen to see the same problem again. I didn't have time before though.
Kind regards and thanks for the new release ! -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
-
Dag Wieers -
Joerg Lehmann