>> When a search is saved as a custom library, and then the music
> > library is rescanned to pick up new music, would you expect
> > the custom library to be refreshed to show new matching music?
>
>Yes. If this doesn't work for you, then please send me the
>advancedSearch.prefs file. I'm not hand-coding the SQL, but try to get
>it from the underlying OODB code. I've seen invalid SQL returned before
>- which is surprising, as it would send valid commands to the DB...
>
>I did try to eg. not use genre IDs in the queries, as these might
>change. But maybe I missed something.
Here's the content of the file:
---
Modified this year:
timestamp:
op: '>'
value: 01/01/2014
_ts_Modified this year: 1411601030
_ts_asvl_d4dd73de65c48b07771643b4bfe00310: 1411601040
_version: 0
asvl_d4dd73de65c48b07771643b4bfe00310:
name: Modified this year
sql: SELECT '%s', id FROM (SELECT me.id, me.urlmd5, me.url, me.content_type,
me.title,
me.titlesort, me.titlesearch, me.album, me.primary_artist, me.tracknum,
me.timestamp,
me.added_time, me.updated_time, me.filesize, me.disc, me.remote, me.audio,
me.audio_size,
me.audio_offset, me.year, me.secs, me.cover, me.cover_cached, me.vbr_scale,
me.bitrate,
me.samplerate, me.samplesize, me.channels, me.block_alignment, me.endian,
me.bpm,
me.tagversion, me.drm, me.musicmagic_mixable, me.dlna_profile,
me.musicbrainz_id,
me.lossless, me.lyrics, me.replay_gain, me.replay_peak, me.extid,
me.virtual,
me.coverid FROM tracks me WHERE ( timestamp > "1388534400" ) GROUP BY me.id
ORDER
BY me.disc, me.titlesort COLLATE en_US )
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
