Content-Type: text/plain; charset=ISO-8859-1
I've noticed that these time issues are the problems with Songbird choking
on my FLAC files as well. If a song is listed as being 15 days, 6 hours and
50 minutes long, we got problems.......
I haven't dug too far into it but I'm thinking that it's an issue with how
the song gets tagged??
On Mon, Nov 23, 2009 at 11:36 AM, Ray Rashif wrote:
> 2009/11/24 Ken Restivo
Content-Type: text/html; charset=ISO-8859-1
I've noticed that these time issues are the problems with Songbird chok=
ing on my FLAC files as well.=A0 If a song is listed as being 15 days, 6 ho=
urs and 50 minutes long, we got problems.......I haven't dug to=
o far into it but I'm thinking that it's an issue with how the song=
-aaronOn Mon, Nov 23, 2009 at 11:36 =
AM, Ray Rashif <email@example.com> wrote:
2009/11/24 Ken Restivo <firstname.lastname@example.org>
On Fri, Nov 20, 2009 at 03:24:58PM +0000, Gwenhwyfaer wrote:
> > something. Foobar2k manages to show it correctly, so should other=
If I chop up an MP3 or Ogg file, using mpgsplt or oggz-chop, the time=
is forever wrong on that file. It'll show the start time that it was i=
n the ORIGINAL file, not in this new, shorter file, which should start from=
00:00. And, alas, my Sanza Fuze loses control of its bladder when it sees =
a file starting at 49:32, for example, and refuses to play it.
-kenAre we looking at a libra=
ry (low-level) fault here? If so we should staple and bug a bug report.
Linux-audio-user mailing list