Page 1 of 1

Audio is not see-kable in other apps

PostPosted: Mon Dec 16, 2013 4:14 am
by acc3d
I've noticed that none of my music that's been cached by DSub is seek-able in other music apps such as Google Play Music. I've tried transcoding to both MP3 and OGG formats, and my device is a Nexus 4.

These tracks also show up in Google Play Music with a duration of 0:00, which is incorrect. DSub shows the correct duration and can seek though.


Why the inconsistency?

Re: Audio is not see-kable in other apps

PostPosted: Mon Dec 16, 2013 6:30 am
by daneren2005
It's only GMusic as far as I can tell. It's a problem with their app.

PostPosted: Mon Dec 16, 2013 3:44 pm
by acc3d
Thanks for the reply. Maybe I'll submit a bug to Google.


On a side note, I recently built a version of ffmpeg for Windows that includes the libfdk_aac AAC encoder. This is supposedly the best AAC encoder and it does sound fantastic compared to MP3s at the same bit rate.

As you probably know, AACs have to be encoded to the adts format by ffmpeg in order to work with Subsonic. This means the resulting M4A files do not include metadata and are not seek-able.

DSub does seem to be able to seek through the files though. Are you calculating duration of the stream within your code? Pretty cool if so! The only drawback I see is that in offline mode, there can be a long delay before playback starts while Dsub reads/calculates whatever you're trying to queue up.

Re: Audio is not see-kable in other apps

PostPosted: Mon Dec 16, 2013 3:48 pm
by daneren2005
When online the duration used is actually received from the server. If there is no duration (ie: not online or Subsonic doesn't know it), it then tries to read from the tags using Android's media framework. If that doesn't work, when it's playing there is a get duration method on the current playing stream that I try to use. If all that fails, it just displays a -:-- I believe (or maybe it was 0:00?).