Page 1 of 1

MP3 length incorrect, causing pause/resume problems

New postPosted: Wed May 11, 2011 1:08 am
by torpesco
http://podcast.cbc.ca/mp3/podcasts/idea ... _53583.mp3

For some reason, this MP3 file and the two before it in the series showed 27 minutes when they are more like 50. Made pause/resume do weird things. BlackBerry media player shows the correct length.

Using 3.0.6 on Pearl 3G with OS 6.

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Tue May 17, 2011 3:31 pm
by marwatk
:/ Hmm, PT gets the length from the BBMP, so not sure what's up there. What does seeking do?

-Marcus

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Tue May 17, 2011 6:46 pm
by torpesco
It did some odd things. Seeking forward and back by a little bit would generally be ok. If I paused and then resumed, it jumped to a completely different part of the episode.

I just did a quick test. The episode was fully listened to. I went back four minutes (looked like 23 minutes in, but probably actually ~50?) and played for 10 seconds and then paused. When I resumed, it jumped back 15 seconds, but the audio was from a completely different part of the episode (I assume from the actual 23 minute mark).

...

Hmm. I wonder now if the download was corrupted somehow. I just went into the BB podcast software and the episode it sees from Podtrapper is listed with the wrong timestamp, but the one it downloaded itself has the correct timestamp.

The weird thing is this happened for three episodes that were downloaded at the same time. Now I wonder if it was some glitch on CBC's server. Unless there was a glitch in the downloads on the phone and I happened to reboot the phone at some point before the download via the BB podcast software.

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Mon May 23, 2011 3:57 pm
by marwatk
If you redownload one of those episodes now, does it still do it?

-Marcus

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Tue May 24, 2011 8:09 am
by torpesco
Not sure if I can now - since it seemed to be a download issue, I deleted the episodes from PodTrapper and the BB software. Is there a way to re-download after deleting an episode?

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Sat Jun 11, 2011 7:21 pm
by marwatk
Yeah, you can 'Change View', then 'View Deleted'.

-Marcus

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Sat Jun 11, 2011 10:52 pm
by torpesco
Heh. Seems obvious now.

I did that and the three episodes all show approx 27.5 minutes for the length. Likely half of the actual length. So for these ones, download with PodTrapper and it's off, download with the BB one and the length is ok.

http://podcast.cbc.ca/mp3/podcasts/idea ... _34910.mp3
http://podcast.cbc.ca/mp3/podcasts/idea ... _27760.mp3
http://podcast.cbc.ca/mp3/podcasts/idea ... _53583.mp3

If there's some card from the SD card I could send you that would help, let me know.

Thanks

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Mon Jun 20, 2011 3:01 pm
by marwatk
What does the length show if you choose 'Play in Native Player'?

-Marcus

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Mon Jun 20, 2011 5:12 pm
by torpesco
marwatk wrote:What does the length show if you choose 'Play in Native Player'?


The correct length, for all three. (Wasn't expecting that, actually...)

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Sun Jul 10, 2011 3:59 pm
by marwatk
Well, that's disconcerting. Can you shoot me a copy of your logs after trying to play one of those episodes? (Via Help/Support -> Email Developer)

-Marcus

Re: MP3 length incorrect, causing pause/resume problems

New postPosted: Fri Sep 16, 2011 12:52 am
by torpesco
And now, while the length starts at 27 min, it is corrected after a few seconds of play. Strange that it wasn't the first time I listened to these episodes.

Given that I've never seen the issue on any other podcast episodes, it doesn't seem worth investigating further. I emailed a log just in case you are still curious.

Thanks,
James.