Music App: Sometimes the "length" of the song is displayed as 0:00

[Wenfang Si]

r154, vivid-proposed

Steps:
1) Open Music App
2) Select an Album, tap on any one from the list to play it
3) After one song start to play, tap on "Forward" button to jump to next song, repeat this

Expect:
The next song starts to play, length of the song and seek bar is displayed correctly

Actual:
Sometimes the length of the song is calculated as "0:00", thus there is no functional seek bar.

[Andrew Hayzen (ahayzen)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I have not been able to reproduce this myself, if the duration does become 0:00 I would expect it to change to the right value after 1 second of playback anyway. Therefore are you able to supply more information about the files you are using, eg format? Furthermore the music-app (application-click-com.ubuntu.music_music_2.0.XYZ.log) and media-hub (media-hub.log) logs from /home/phablet/.cache/upstart could be useful.

[Victor Thompson (vthompson)]

I aws able to reproduce this: http://i.imgur.com/J5N6OSg.png

[Victor Thompson (vthompson)]

However, at first glance, I did not see anything interesting in the logs.

[Andrew Hayzen (ahayzen)]

If you can get this to occur again things I would be interested in knowing:
* Is the small progress bar (below toolbar in the pages/queue) correct?
* If you tap on the slider does it fix itself (it could be stuck in 'seek' mode)?

Otherwise it would appear that the MediaPlayer.duration is 0.

[Victor Thompson (vthompson)]

Ok, I was able to reproduce again. 1) The small progress bar is black (at 0:00). 2) Tapping the progress bar just restarts the song at 0:00.

One thing I've noticed is that sometimes the duration doesn't get updated for almost 1 second after the song starts.

[Wenfang Si (wenfang.si)]

@Victor, Thank you to help to reproduce and capture things.
@Andrew, Please let me know if you need me to do anything.

[Victor Thompson (vthompson)]

An update on this. I'm running vivid r159 which has some/all of the "media-hub3" updates in it and it doesn't seem to fix the issue--as I've been able to reproduce it. However, in the 3 times I've been able to reproduce to this to date, I've only been able to do so while shuffling my whole library. Playing a single album does not seem to cause the issue--but that is not conclusive evidence. Additionally, I had tried to reproduce using just an album of MP3s vs the same album converted to OGG--but neither failed.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I'm running latest on arale and am getting this:-

http://people.canonical.com/~alan/screenshots/device-2015-04-28-150511.png

[Andrew Hayzen (ahayzen)]

It has been suggested that this is a rare race condition somewhere, adding media-hub as also affects as it is possible the issue is there.

[Víctor R. Ruiz (vrruiz)]

While testing this silo, I could crash the media-hub going forwards and backwards repeatedly.

[Launchpad Janitor (janitor)]

This bug was fixed in the package qtubuntu-media - 0.7.1+15.10.20150522-0ubuntu1

---------------
qtubuntu-media (0.7.1+15.10.20150522-0ubuntu1) wily; urgency=medium

  [ Jim Hodapp ]
  * Make sure that stopped and ready (same state for QMediaPlayer) are
    reported to the client app. (LP: #1435088)

qtubuntu-media (0.7.1+15.04.20150513.1-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Jim Hodapp ]
  * Fix duration() not getting reported after playback starts. (LP:
    #1438115)

 -- CI Train Bot <email address hidden> Fri, 22 May 2015 17:36:57 +0000

[Evan Wang (wsy324)]

This issue still could be reproduced on arale/vivid r4 sometimes, and sometimes the length is displayed as 0:00 just for the first 1~2 seconds, then actual length will shown.

$ system-image-cli -i
current build number: 4
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-05-28 05:26:35
version version: 4
version ubuntu: 20150527
version device: 20150522-a851049
version custom: 20150526-719-5-24

[Jim Hodapp (jhodapp)]

@Evan: yes, I haven't had a working arale to develop the fix with, but now I have one so I'll be finishing off this bug soon.