Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 130

Hybrid View

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

    New in 7.9: Fulltext search

    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

  2. #2
    Senior Member Mnyb's Avatar
    Join Date
    Feb 2006
    Location
    Vństerňs Sweden
    Posts
    16,528
    + excellent idea
    --------------------------------------------------------------------
    Main hifi: Rasbery PI digi+ MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
    Bedroom/Office: Boom
    Loggia: Raspi hifiberry dac + Adams
    Bathroom : Radio (with battery)
    iPad with iPengHD & SqueezePad
    (spares Touch, SB3, reciever ,controller )
    server Intel NUC Esxi VM Linux mint 18 LMS 7.9.2

    http://people.xiph.org/~xiphmont/demo/neil-young.html

  3. #3
    Great new feature, thanks!

  4. #4
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,790
    Michael, you are awesome!
    ---
    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

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

    New in 7.9: Fulltext search

    > 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

  6. #6
    Senior Member
    Join Date
    Jun 2009
    Posts
    439
    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"?

    last entry in logs is:
    [14-10-23 21:12:56.9772] Slim::Music::Import::runImporter (485) Starting Slim::Plugin::FullTextSearch::Plugin scan
    some 40 minutes ago ...
    Last edited by frank1969; 2014-10-23 at 12:59.

  7. #7
    Senior Member mdconnelly's Avatar
    Join Date
    Feb 2007
    Location
    NC USA
    Posts
    109
    Awesome concept! Where is it picking up the hirez "88.2" in a query? Is it actually looking at the files or just if that was stored in a tag? Just wondering if I could do the same for 24bit depth?
    Mike (1 SB3, 1 Duet, 1 Boom, 2 Touch, 1 SB Radio)

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

    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

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

    New in 7.9: Fulltext search

    "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?



    > 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
    >
    >

  10. #10
    Senior Member
    Join Date
    Jun 2009
    Posts
    439
    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?

Posting Permissions

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