Yes I had initialized the database (twice) but it hadn't shown up --
but I just redid a lot of the audio content and rebuilt the database
and it's appearing now. I'm guessing that it takes a while for the
database to initialize and I may have perhaps rebooted before it was
Anyway, it's working now!
Can I ask what the difference between the official release and your
(and others) version is? Is there a reason why those patches aren't
being included in the main build? I notice some are and some aren't
-- is it sort of a beta-release or just a philosophical difference
between the maintainers?
The next question I have (if anyone knows) is what FM region is
Australia? I've tried all 4 and the tuner doesn't seem to work all
that well in any of them. Korea seems to be the best, but the tuning
stops one step too soon on every station (e.g. there's a station at
95.40, the tuner stops at 95.30 reliably, one step more for each scan
stop is the right station -- not perfect, but as good as it seems to
And (lastly) after being connected all night and starting up I get
60-70% battery charge which it claims will last me 4-5hrs (and this
seems to vary up as well as down, e.g. i'll look one time and it'll be
50% just after charging and an hour later it'll be 80%...)
Is this just because my battery is knackered (it's not a new player,
but it's been very rarely used since it was bought as a present for a
non-techie.) Or is it just that the battery meter isn't very well
calibrated? The sansa firmware shows it similarly low, so I'm
guessing the battery is on it's last legs. Are they selling
On 9/22/07, Charles philip Chan <cpchan_at_sympatico.ca> wrote:
> "Paul Hannah" <pkhannah_at_gmail.com> writes:
> I have no problems with Vorbis files at all.
> > First the ogg files don't appear in the database at all.
> Have you initialized and updated the db?
> > Second, when I play them via the file menu, it appears that the player
> > can't handle the decoding -- about every 20s or so there is a 1/2s
> > pause, and the interface is obviously being slowed (I'm using the
> > 'text' theme and the obvious thing is the level meters.)
> Strange, it sounds like something is broken with your encoder. FYI,
> Vorbis, together with mp3, are the most supported lossy codecs in
> > In case it matters, they are encoded using Sound Juicer with all
> > default settings (actually it was encoded on a virgin install of gutsy
> > tribe 5.
> I don't use Sound Juicer, so I am not sure if it is broken. I use a
> version of oggenc linked against the Aotuv branch of libvorbis:
> From the commandline and with grip.
> > The id3 information apart from genre was automatically entered.
> This might be your problem. Ogg Vorbis files doesn't use id3 tags, but
> Vorbis comments. Some bad programs will try to embed id3 tags in the Ogg
> container, which will produce broken files.
> I see that you are using an e260. You might be interested in my
> unofficial builds for the e200 target located here:
Received on 2007-09-23