Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 13 FirstFirst 123412 ... LastLast
Results 11 to 20 of 130
  1. #11
    Senior Member
    Join Date
    Jun 2009
    Posts
    428
    Yes, thanks - after 55 minutes it finished full text search (for 420k mp3-files). I will now test the feature and report if it was only the initial scan that took so "long" or if it's the same with every (update-) scan. Great idea, by the way! :-)


    [QUOTE=mherger;794047]"usually" is hard to define. My 20k tracks take a second or two to index on a poor Atom based system. Even less on the Macbook Pro with SSD, of course.

    Is there any activity going on? Eg. massive memory usage? CPU load? library.db changes?

  2. #12
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,569

    New in 7.9: Fulltext search

    Oh, and you do use the "maximum" memory preference in Settings/Advanced/Performance?

    Michael



    > Am 23.10.2014 um 21:54 schrieb frank1969 <frank1969.6mggfb (AT) no-mx (DOT) forums.slimdevices.com>:
    >
    >
    > Great idea but...
    > ... after 40 minutes it still says "Volltext Index erstellen (0 von 5)
    > L├Ąuft 00:39:45" - and there is only one "dot" shown - so it should
    > take hours, dates ...
    > I know, i have a 420k track library, but on a high performance PC.
    > Any idea how long full text search "usually" should do or should I stop
    > and restart so it maybe "hanged`up"?
    >
    >
    > ------------------------------------------------------------------------
    > frank1969's Profile: http://forums.slimdevices.com/member.php?userid=31156
    > View this thread: http://forums.slimdevices.com/showthread.php?t=102347
    >
    >

  3. #13
    Senior Member
    Join Date
    Jun 2009
    Posts
    428
    Ok, first thing I recognized:
    New artists are not to be found.

    Yesterday I added some tracks from (e.g.) Willy Wagner or Tina (02) - I didn't own any tracks of them before (as "co"-artist, separated with ";" as I always do)

    If I call the album, I see performer "Willy Wagner", can click on the name and it shows me I own own album he contributes tracks too - fine, works as it should!

    If I search for "Willy Wagner", it finds - nothing.

    If I browse my artist list, it finds - nothing!


    This behaviour seems to affect only new added TRACK ARTIST .

    I also added an album by an artist I did own nothing from before (Ric Seroka) so he is mentioned as ("single") track artist and ALBUM artist - and everyhting is finde.
    I can search for his name and I find him in the artist's list...

  4. #14
    Junior Member
    Join Date
    Oct 2014
    Posts
    3

    285

    Quote Originally Posted by mherger View Post
    Something new to play with: full text search (FTS).

    Your search no longer is limited to a simple title/name search. With the
    FTS you can now easily find track X by artist Y. Just type "hurry love
    supremes" if you want to make sure not to get Phil Collins' version.

    Other examples:

    "mp3" - only find tracks in lossy mp3 (or with mp3 in the name - oh well)

    "playlist elvis" - find playlists with tracks by Elvis, or with Elvis in
    the name or a track's name

    "flac 88.2 mozart" - get that highres classical stuff

    The search code tries to weight results: hits in track titles have
    higher priority than hits in a track's artist or album name. Eg. "lov"
    would rank ABBA's "loving me, loving you" higher than "love me tender"
    from the "greatest love songs, ever" album. Playlist names have priority
    over track titles included in the playlist etc.

    FTS is available from both the web UI's "live search" as well as the
    regular search menus. Please give it a try and let me know what you
    think about it.


    A few caveats:

    - FTS most likely will be a bit heavier on your system, with regards to
    both the CPU as well as memory. I guess it shouldn't be used without the
    highmem preference being set to high or max.

    - FTS only works with SQLite. If you decided to use MySQL for whatever
    reason, then I'm sorry, this won't work, as it's based around SQLite's
    FTS extension

    FTS is implemented as a plugin (mostly). If you don't like it, then just
    disable the plugin to get the old behaviour back.

    --

    Michael
    Sweet!

  5. #15
    Senior Member
    Join Date
    Jun 2009
    Posts
    428
    And another thing (I use a second "answer" for this, for it seems to be another issue?):
    It doesn't seem to work ..

    I type in "hurry love supremes" - and it just finds - nothing.
    If I use the extended search and type in "hurry love" in title and "supremes" in artsists - it finds the song (even on 6 cd's)

    Do I have to change anything on my settings (except for setting the "x" in PlugIns) to use the feature?

    Below the end of my scanner log - I see the "out of memory" error (Its run with 8 GB RAM and the high memory option...) but this seems to be as a later point when the FullTextSearch is successfully done...?!


    [14-10-23 21:12:56.9772] Slim::Music::Import::runImporter (485) Starting Slim::Plugin::FullTextSearch::Plugin scan
    [14-10-23 22:08:16.6278] Slim::Music::Import::endImporter (617) Completed Slim::Plugin::FullTextSearch::Plugin Scan in 3319 seconds.
    [14-10-23 22:08:16.6286] Slim::Music::Import::runImporter (485) Starting Slim::Music::VirtualLibraries scan
    [14-10-23 22:08:20.1274] Slim::Music::Import::endImporter (617) Completed Slim::Music::VirtualLibraries Scan in 3 seconds.
    [14-10-23 22:08:22.8880] Slim::Music::Artwork::updateStandaloneArtwork (204) Starting updateStandaloneArtwork for 8807 albums
    [14-10-23 22:10:50.7034] Slim::Music::Artwork::__ANON__ (309) updateStandaloneArtwork finished in 147.80641913414
    [14-10-23 22:10:51.7668] Slim::Music::Artwork:recacheAllArtwork (615) Starting precacheArtwork for 48 albums
    [14-10-23 22:11:11.4912] Slim::Music::Artwork::__ANON__ (734) precacheArtwork finished in 19.7102890014648
    [14-10-23 22:11:11.4917] Slim::Music::Import::endImporter (617) Completed precacheArtwork Scan in 20 seconds.
    [14-10-23 22:11:11.6310] Slim::Music::Import::runScanPostProcessing (409) Starting Database optimization.
    [14-10-23 22:11:57.3599] Slim::Utils::SQLiteHelper::vacuum (514) Warning: DBD::SQLite::db do failed: out of memory at /<C:\PROGRA~2\SQUEEZ~1\server\scanner.exe>Slim/Utils/SQLiteHelper.pm line 514.
    [14-10-23 22:12:13.7029] Slim::Music::Import::endImporter (617) Completed dbOptimize Scan in 62 seconds.

  6. #16
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,788
    Quote Originally Posted by mherger View Post
    > Michael, you are awesome!

    ....except that it doesn't work with iPeng... Only tested it after I had
    it announced here. Web UI should be fine though. I'll take care of it asap.

    --

    Michael
    Oh, the problem is probably on your side.
    The normal "search" CLI command now seems to be broken:

    Code:
    error = "request failed with error: Bad dispatch!";
    on this command

    Code:
    {
        cmd =     (
            search
        );
        params =     {
            term = Abc;
        };
    }
    ---
    learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
    Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
    at penguinlovesmusic.com
    New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

  7. #17
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,788
    Some more logging_
    Code:
    Slim::Control::Request::execute (1890) Error: While trying to run function coderef [Slim::Control::Queries::searchQuery]: [Carp::Clan::__ANON__(): DBI Exception: DBD::SQLite::db prepare_cached failed: no such column: me.audio [for Statement "SELECT COUNT(1) FROM (
    				SELECT me.id, me.title FROM (
    					SELECT FULLTEXTWEIGHT(matchinfo(fulltext)) w, me.id, me.title FROM fulltext, tracks me WHERE fulltext MATCH 'type:track *ABC*' AND me.id = fulltext.id ORDER BY w
    				) AS me
    			WHERE me.audio = ? ) AS t1"] at /Users/jorgschwieder/Daten/Business/Dev/iPhone/Source/Libs/Squeez&UE/slimserver/Slim/Schema/Storage.pm line 126
    ---
    learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
    Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
    at penguinlovesmusic.com
    New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

  8. #18
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,569

    New in 7.9: Fulltext search

    > Oh, the problem is probably on your side.

    Exactly.

    > The normal "search" CLI command now seems to be broken:


    I'm almost done with the fix.

    --

    Michael

  9. #19
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,569

    New in 7.9: Fulltext search

    > [14-10-23 22:11:57.3599] Slim::Utils::SQLiteHelper::vacuum (514)
    > Warning: DBD::SQLite::db do failed: out of memory at
    > /<C:\PROGRA~2\SQUEEZ~1\server\scanner.exe>Slim/Utils/SQLiteHelper.pm
    > line 514.


    Ok, the scan failed. No good. But I'll ignore all your other reports, as
    they're most likely just side-effects of this major issue.

    Unfortunately I only have Erland's 100k library to test with. I'll let
    you know what I get there.

    --

    Michael

  10. #20
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,569

    New in 7.9: Fulltext search

    > Awesome concept! Where is it picking up the hirez "88.2" in a query?

    The data is pulled from the files during the regular scan. Depth is in
    there too, though "16" or "24" as keywords probably aren't that
    meaningful. Plus I've seen a majority of my files not report any depth
    at all. This might depend on the file format.

    Check a track's info menu, "Read Tags" to see whether it's reported
    there. If it is, then it's in the fulltext index, too.

    --

    Michael

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •