Page 1 of 1

MP3 songs; some track lengths are just wrong

PostPosted: 05 Apr 2015, 12:09
by itnomad
Hi,

my first post, so first, thanks for the app. Awesome on the go.

While importing a bunch of recently ripped CDs I noticed something odd. A lot - though not all - songs show a completly wrong track length. Songs which are supposed to have, let's say, a length of 3:45 show up with a length of 25:12 or other completly off lengths.
Screenshot_2015-04-05-13-03-11.png
Unrealistic track lengths

While analyzing the songs for BPM, it takes minutes per song and what's even more odd is that if you look at the waveform, the track gets extended by silence. So if the song is originally, let's say, 3:00 minutes and Cross DJ makes 19:00 minutes of it, you're having 16 minutes of silence after the song.
Screenshot_2015-04-05-13-05-34.png
And for something completly different. Lemme introduce you to my good ol' pal, Mr. Silence.

Also, the application hogs all CPU cores completly while loading these suspiciously "long" tracks so that you end up in a "the app is not responding" message.
Screenshot_2015-04-05-13-03-51.png
Loading loading loading... adding some silence, hogging the CPUs.

I'm not quite sure what's going on here; all MP3s where ripped with the same program and the only thing which is a little odd is that this program (Rhythmbox) only write ID3v2 tags and no ID3v1 tags.

But it's not consistent.

Any ideas? I'm happy to share sample MP3s, not sure if anyone can reproduce it. I've attached a few screenshots.

Platform: Samsung Nexus 10 1st generation
OS: stock Android 5.1, not rooted, encrypted filesystem.

Thanks and keep up the good work!
Alex.

Re: MP3 songs; some track lengths are just wrong

PostPosted: 05 Apr 2015, 13:04
by RoJeC
Pretty sure the ripping is the cause and the files are actually that long.

Track analysis requires high capacity. This is triggered by load of a track.

Using vbr for rip could be causing this. At least this is my experience.