On 04.09.06, Stefan Wimmer wrote:
- Joerg Lehmann joerg@luga.de [2006-09-03 23:45]:
Hi Stefan,
This makes me suspicious as the changes between 2.3.0 and 2.3.1 are rather minor. Are you sure that both versions use the bufferedao C extension module?
Jörg
Hu? How should I know - I just upgraded my PyTone package to 2.3.1 and
But I enabled debug logging and a short "grep -C2 bufferedao" showed me
D [23:28:11|MainThread|b] event: sendeventin(checkpointdb(main), 60, 60, 0) (priority 0) D [23:28:11|MainThread|rvice] started songautoregisterer service D [23:28:11|MainThread|rvices/players/internal] bufferedao device opened D [23:28:11|MainThread|rvice] started player main service D [23:28:11|MainThread|rvice] started playlist service D [23:28:11|MainThread|rvices/players/internal] bufferedao device opened D [23:28:11|MainThread|rvice] started player secondary service D [23:28:11|MainThread|inscreen] h=60, w=87
Is this what you are looking for?
Exactly. But I would also need the same information for PyTone 2.3.0.
- Some sort of replaygain
Hey, this is implemented for MP3s, although not released yet.
- Extended search function
FYI, my recent experiments with a new database based ony SQLite are very promising. This should also allow a much better search functionality. I also switched to a tag-based song classification scheme which will allow filtering schemes like: everything but muzak, where music can easily be tagged as muzak. The compiliations support is also very much improved. And above all, it's very performant, at least with my not so large music collection. And I'm pretty positive that it also scales to bigger collections. So stay tuned, it's really very exciting.
Jörg