Revision history for pmusicDocSearch


Revision [33311]

Last edited on 2023-02-24 06:01:09 by zigbert
Additions:
{{image url="http://www.smokey01.com/zigbert/pmusic/wiki/pmusic_heading.png" link="pmusic" title="pMusic" alt="pMusic" height="80"}}
Deletions:
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/pmusic_heading.png" link="pmusic" title="pMusic" alt="pMusic" height="80"}}

Revision [33310]

Edited on 2023-02-24 06:00:54 by zigbert
Additions:
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://web.archive.org/web/20160913060503/http://blog.puppylinux.com/?viewDetailed=00024|pMusic DB and file format]].
~When [[http://web.archive.org/web/20160912055625/http://blog.puppylinux.com/?viewDetailed=00033|searching youtube]] inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
~~- **Tracks** is local audio files stored in the [[http://web.archive.org/web/20160913060503/http://blog.puppylinux.com/?viewDetailed=00024|database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://web.archive.org/web/20170502202522/http://blog.puppylinux.com/?viewDetailed=00027|Set playqueue]].
Deletions:
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html|pMusic DB and file format]].
~When [[http://blog.puppylinux.com/?viewDetailed=00033|searching youtube]] inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
~~- **Tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html|database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/27-pMusic---Set-playqueue.html|Set playqueue]].

Revision [33292]

Edited on 2023-02-24 02:22:14 by zigbert
Additions:
[[HomePage]] > [[SoftwareIndex|Software Index]] > [[SoftwareMultimedia|Multimedia]] > [[pMusic]] > [[pMusicDoc|Documentation]]
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/pmusic_heading.png" link="pmusic" title="pMusic" alt="pMusic" height="80"}}
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html|pMusic DB and file format]].
==={{color text="The Search field" c="green"}}===
~When [[http://blog.puppylinux.com/?viewDetailed=00033|searching youtube]] inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
==={{color text="Where to search" c="green"}}===
~~{{image url="http://www.smokey01.com/zigbert/pmusic/wiki/docSearch_1.png"}}
~~- **Tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html|database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
===Misc===
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional [[pmusicInstall#hn_Dependencies|dependency]].
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/27-pMusic---Set-playqueue.html|Set playqueue]].
Deletions:
[[HomePage]] > [[SoftwareIndex Software Index]] > [[SoftwareMultimedia Multimedia]] > [[pMusic]] > [[pMusicDoc Documentation]]
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/pmusic_heading.png" link="http://wikka.puppylinux.com/pmusic" title="pMusic" alt="pMusic" height="80"}}
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html pMusic DB and file format]].
=={{color text="The Search field" c="green"}}==
~When searching [[http://blog.puppylinux.com/?viewDetailed=00033 youtube]] inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
=={{color text="Where to search" c="green"}}==
~~{{image url="http://www.01micko.com/zigbert/pmusic/wiki/docSearch_1.png"}}
~~- **Tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
==Misc==
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional [[http://wikka.puppylinux.com/pmusicInstall#hn_Dependencies dependency]].
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/27-pMusic---Set-playqueue.html Set playqueue]].

Revision [32732]

Edited on 2019-12-28 06:54:34 by zigbert
Additions:
~~- **Tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~~- **Playlist** is both internal album lists and your own m3u/pls playlist files.
~~- **Discography** searches Musicbrainz.org for artist and their albums. Chosen tracks are played either from local file or from Youtube.
~~- **Radio** searches the index holding all radio URL's. This index has to be downloaded.
Deletions:
~~- **My tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~~- **My collections** is both internal album lists and your own m3u/pls playlist files.
~~- **Radio stations** searches the index holding all radio URL's. This index has to be downloaded.

Revision [32723]

Edited on 2019-11-10 07:00:18 by zigbert
Additions:
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/pmusic_heading.png" link="http://wikka.puppylinux.com/pmusic" title="pMusic" alt="pMusic" height="80"}}
Deletions:
{{image url="http://www.01micko.com/zigbert/pmusic/wiki/pmusic_heading.png" link="http://www.puppylinux.org/wikka/pmusic" title="pMusic" alt="pMusic" height="80"}}

Revision [32722]

Edited on 2019-11-10 06:59:13 by zigbert
Additions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional [[http://wikka.puppylinux.com/pmusicInstall#hn_Dependencies dependency]].
Deletions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional [[http://www.puppylinux.org/wikka/pmusicInstall#hn_Dependencies dependency]].

Revision [32143]

Edited on 2018-10-02 08:46:44 by zigbert
Additions:
~~- **My tracks** is local audio files stored in the [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/27-pMusic---Set-playqueue.html Set playqueue]].
Deletions:
~~- **My tracks** is local audio files stored in the [[http://blog.puppylinux.com/?viewDetailed=00024 database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
~-Search random tracks depending on your requests is done by the **smartadd** function. Described in the article [[http://blog.puppylinux.com/?viewDetailed=00027 Set playqueue]].

Revision [32142]

Edited on 2018-10-02 08:45:14 by zigbert
Additions:
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://blog.puppylinux.com/archive/current.php?post=posts/24-pMusic-DB-and-file-format.html pMusic DB and file format]].
Deletions:
The old fashion way to search for your music is to do a file search and filter out the audio files. This works perfect for small collections, but when things start to grow, we need more powerful tools to find what we searches for without having too many cups of coffee while we wait. Searching isn't hard, but quick search is more complex. We are talking about indexing - putting info of your files into a database to quickly find it when we search for it. The search is not done in your filesystem(s) - but inside the database, which is much faster. A deeper understanding of this structure is described in the article [[http://blog.puppylinux.com/?viewDetailed=00024 pMusic DB and file format]].

Revision [31642]

Edited on 2017-03-31 13:27:04 by zigbert
Additions:
~The dock shows different sources
~~- **Lyrics** searches inside the downloaded lyrics files. This has to be turned on in the Preferences.
Deletions:
~The dock shows 8 different sources

Revision [31247]

Edited on 2016-08-26 15:59:07 by zigbert
Additions:
~When searching [[http://blog.puppylinux.com/?viewDetailed=00033 youtube]] inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
Deletions:
~When searching **youtube** inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.

Revision [31244]

Edited on 2016-08-24 04:38:54 by zigbert
Additions:
=={{color text="The Search field" c="green"}}==
=={{color text="Where to search" c="green"}}==
Deletions:
==The Search field==
==Where to search==

Revision [31243]

Edited on 2016-08-24 04:37:54 by zigbert
Additions:
~When searching **youtube** inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax. It must not be complete (not even the words) and it isn't case sensitive, but the search will fail if the search-string is misspelled. The consensus is: Search youtube, write whatever. - Else, search simple.
Deletions:
~When searching **youtube** inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax (not complete and not case sensitive). The consensus is: Search youtube, write whatever. - Else, search simple.

Revision [31242]

Edited on 2016-08-24 04:34:57 by zigbert
Additions:
~When searching **youtube** inside pMusic, there is a difference in how to specify the best search-string. Youtube has a advanced search-engine which gives result for __related items__. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have a correct syntax (not complete and not case sensitive). The consensus is: Search youtube, write whatever. - Else, search simple.
Deletions:
~When searching **youtube** inside pMusic, there is a difference in how to specify search-string. Youtube has a advanced search-engine which gives result for related items. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have correct syntax (not complete and not case sensitive). The consensus is: Search youtube, write whatever. - Else, search simple.

Revision [31224]

Edited on 2016-08-23 15:38:24 by zigbert
Additions:
~The dock shows 8 different sources
~~- **Radio stations** searches the index holding all radio URL's. This index has to be downloaded.
~~- **Youtube** searches [[http://youtube.com youtube.com]] via [[http://keepvid.com keepvid.com]]. The result shows maximum 10 items.
~~- **Jamendo** searches the index holding music from jamendo.com. This index has to be downloaded.
~~- **Podcast** searches the podcast index. This index has to be downloaded.
Deletions:
~The dock shows 6 different options
~~- **Radio stations** which searches the index holding all radio URL's. This index has to be downloaded.
~~- **Web music** which searches the index holding music from jamendo.com. This index has to be downloaded.

Revision [31223]

Edited on 2016-08-23 15:32:45 by zigbert
Additions:
~~- If you type a web address, it will add the URL to the playqueue.
~When searching **youtube** inside pMusic, there is a difference in how to specify search-string. Youtube has a advanced search-engine which gives result for related items. This means you can specify 'as much as possible' to get the closest result. pMusic has a simple search-engine, and requires the search-string to have correct syntax (not complete and not case sensitive). The consensus is: Search youtube, write whatever. - Else, search simple.
Deletions:
~~- If you type a web address, it will add the URL to the playqueue.

Revision [31110]

Edited on 2016-07-09 10:20:52 by zigbert
Additions:
~~- **My tracks** is local audio files stored in the [[http://blog.puppylinux.com/?viewDetailed=00024 database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for //**''Madonna Music''**// you will get all tracks because //**''Music''**// corresponds with directory name found in the database.
Deletions:
~~- **My tracks** is local audio files stored in the [[http://blog.puppylinux.com/?viewDetailed=00024 database]]. The database holds a lot of data, and whatever info the database holds about a track will be a target for your search. E.g. You store your music in /dir/music/, and are searching for **''Madonna Music''** you will get all tracks because **''Music''** corresponds with directory name found in the database.

Revision [31109]

Edited on 2016-07-09 10:20:32 by zigbert
Additions:
~//**''nig tnt''**// finds the track //TNT - Desperate night//. As this shows, it isn't case sensitive.
~//**''nig -tnt''**// does not find any TNT tracks.
Deletions:
~**''nig tnt''** finds the track //TNT - Desperate night//. As this shows, it isn't case sensitive.
~**''nig -tnt''** does not find any TNT tracks.

Revision [31108]

Edited on 2016-07-09 10:19:25 by zigbert
Additions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional [[http://www.puppylinux.org/wikka/pmusicInstall#hn_Dependencies dependency]].
Deletions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional dependency.

Revision [31107]

Edited on 2016-07-09 10:18:33 by zigbert
Additions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens the [[pFilesearch]] gui, but the result is sent back to pMusic. pFilesearch is an optional dependency.
Deletions:
~-Advanced filesearch is reachable from the **Music Sources** menu. This opens [[pFilesearch]], but the result is sent back to pMusic. pFilesearch is an optional dependency.

Revision [31106]

Edited on 2016-07-09 10:18:04 by zigbert
Additions:
~~-The last option is a plain **file search**, and let's you specify directory to search in. This will find all files - also those not stored in the database. Normally all music is stored into the database, but in some cases, the user can override this, and a full-range file search is required. This kind of search is much slower than a search inside the database. pMusic uses [[pFilesearch]] as the file search engine.
Deletions:
~~-The last option is a plain file search, and let's you specify directory to search in. This will find all files - also those not stored in the database. Normally all music is stored into the database, but in some cases, the user can override this, and a full-range file search is required. This kind of search is much slower than a search inside the database. pMusic uses [[pFilesearch]] as the file search engine.

Revision [31100]

The oldest known version of this page was created on 2016-07-09 10:12:57 by zigbert
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki