Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mr. Odd]

Setup: MC 16.0.64 on Win XP, plenty of horsepower, nothing else sucking up CPU time. Latest Gizmo on Droid 2 w/ Android 2.2 on Verizon, using 3G network. Library is 98% self-ripped LAME VBR MP3s.

1) The track time on the now playing screen is wrong, looks like it's twice as long as the actual track.

2) MC updates the play stats on the server side - YAY - but does so as soon as the track is queued. Could it happen at the halfway mark or the end of the track instead? If I skip back and forth in a playlist (i.e. hit the back arrow a few times on the now playing screen) my play counts are incorrectly updated.

3) It seems there's a 15-30 second delay between tracks while the file is being "Prepared". Is that typical? What might be impacting that time?

Thanks!

[Matt]

About what bitrate are your MP3 files?

We don't convert a file if it's already MP3, and I'm wondering if this causes problems with when you have high bitrate MP3 files, especially when using 3G instead of Wifi.

This would also explain the duration, because it's up to the MP3 decoder on the phone to analyze the file and get the proper duration.  It may not handle VBR nicely.

Thanks.

[Mr. Odd]

Matt - thanks for the response.

My files are typically encoded at V2 and average in the 190-200 range. Is this considered high bitrate over 3G?

Historically, VBR has given some applications fits when it comes to determined track length. I thought that issue had mostly been resolved?

[Matt]

Would you mind emailing me a sample file that's slow to start playing?  I'm matt at jriver dot com.

The LAME header at the front should report the correct length, but it's possible your phone isn't reading it.  It's also possible your MP3 files don't have a LAME header.

If we had a sample file, we could do some testing here on a few Android devices as well.

Thanks.

[Matt]

Thanks for the test file.

I just tested the file with a G1 running 2.2 and a Nexus S running 2.3.

Both start playback almost immediately (although I am using Wifi) and show the correct duration of 3:26.

So I'm not sure what is going on.  Anyone else have any ideas?