Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Not advancing tracks
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Sander Jansen  
View profile  
 More options Jan 14 2011, 11:48 pm
From: Sander Jansen <s.jan...@gmail.com>
Date: Fri, 14 Jan 2011 22:48:24 -0600
Local: Fri, Jan 14 2011 11:48 pm
Subject: Re: Not advancing tracks

On Fri, Jan 14, 2011 at 10:20 PM, disturbed1 <disturbed1...@gmail.com> wrote:
>> What's the xine version?

>> FYI, taglib-extras is no longer used.

> xine-lib-1.1.17
> xine-ui-0.99.5

> I should note for completeness -
> I did re-rip this same album using lame, helix-mp3 encoder (Real
> Networks Xing implementation), fastencc (through wine), ogg, and flac.
> CBR, and VBR. The new rips did not have this problem.

> And I see you have the tracks -- good luck :)

This issue is caused by an incorrect VBR header (xing) in the mp3
file. The duration of the mp3 as seen by xine is incorrect which
causes the bug in gogglesmm*. There are tools available that will fix
your mp3 without having to re-rip them. For
example:https://gna.org/projects/vbrfix

I'll see if I can make gogglesmm behave better with regards to broken vbr's.

Cheers,

Sander

* The actual problem is that we get the "playback finished" event
before the actual track has finished playing. This is on purpose, so
we have time to load the next track. When we load the next track, we
cannot update the GUI yet, since the old track is still playing. So we
set a timer which fires whenever the new track actually starts
playing. Once the timer fires, we update the GUI. The timer is set
based on the length of the track and its current position. So if the
length information is incorrect the timer may fire too late or too
early, causing things like repeating tracks (the GUI thinks some other
track is playing).


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.