i just cant seem to get the sort order to wok , i would like to be able to sort the albums by descending date added , or modified , but it just seems to ignore any sort criteria and just defaults to album name , i am certain it is looking at the correct section in the index part of defaultindex.ini because i have managed to add a suffix to my entries and this shows in sonos .

this is what i have for the sort order , i have tried all combinations , in different ways , and just thought maybe i am missing something ?

thanks for your help dave

[indexes]

tree=album/track title=Albums icon=icon_albums sort_order=lastmodified index=album entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

Thanks for this , I will have a look

Dave

Sent from my iPad

On 5 Nov 2014, at 09:40, Mark Henkelis notifications@github.com wrote:

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Wednesday, 5 November, 2014 6:55:14 AM Subject: Re: [sonospy] sort order (#76)

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

Worked through the userindex.ini file and thanks to the default code in there got it working , thanks, it is a great piece of software

One other question , which I don't think is possible is ...... Is it possible to implement and run all elements of the application on a NAS ? As opposed to just accessing my music folder which resides on the nas ? That way sonospy will always be up and running when I use sonos , rather than me turning on the PC and starting up sonospy ?

Unfortunately being a software developer myself , and in my late 40's !! I am somewhat still working on legacy coding languages from the early 90's so not familiar with Python

Thanks again for your help, and advice

Kind regards Dave

Sent from my iPad

On 5 Nov 2014, at 09:40, Mark Henkelis notifications@github.com wrote:

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Wednesday, 5 November, 2014 6:55:14 AM Subject: Re: [sonospy] sort order (#76)

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

If the NAS can run Python, then it can run on the NAS. So you can run it on a QNAP for instance (I've run it on a Buffalo before too). It's not tuned to run on a NAS mind - when I get round to it I'll run it on my QNAP. It could also be run on a RaspberryPi - I started looking at tuning it for that with large databases but got distracted.

My first language was Fortran and I'm older than you :)

Thanks for that info , how would I know if my NAS CAN RUN PYTHON ? Would I just be a simple case of copying the folder from my PC to a folder on the nas aNd running it exactly the same as I would under windows ?

I did fortran 77 back in the day !! And then ended up using uniface 4gl for the last 20 years !!!!

Thanks

Dave

Sent from my iPad

On 6 Nov 2014, at 09:52, Mark Henkelis notifications@github.com wrote:

If the NAS can run Python, then it can run on the NAS. So you can run it on a QNAP for instance (I've run it on a Buffalo before too). It's not tuned to run on a NAS mind - when I get round to it I'll run it on my QNAP. It could also be run on a RaspberryPi - I started looking at tuning it for that with large databases but got distracted.

My first language was Fortran and I'm older than you :)

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Thursday, 6 November, 2014 6:25:43 AM Subject: Re: [sonospy] sort order (#76)

Hi

Worked through the userindex.ini file and thanks to the default code in there got it working , thanks, it is a great piece of software

One other question , which I don't think is possible is ...... Is it possible to implement and run all elements of the application on a NAS ? As opposed to just accessing my music folder which resides on the nas ? That way sonospy will always be up and running when I use sonos , rather than me turning on the PC and starting up sonospy ?

Unfortunately being a software developer myself , and in my late 40's !! I am somewhat still working on legacy coding languages from the early 90's so not familiar with Python

Thanks again for your help, and advice

Kind regards Dave

Sent from my iPad

On 5 Nov 2014, at 09:40, Mark Henkelis notifications@github.com wrote:

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Wednesday, 5 November, 2014 6:55:14 AM Subject: Re: [sonospy] sort order (#76)

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

If the NAS doesn't offer you a web interface to load and run programs, you'll need to be able to log in to it via telnet or ssh (some make that easy, others don't). Once you get logged in, you can check whether Python is installed (it's usually possible to install it if it isn't).

Where you store apps vs where data is stored is usually different - you'll be placing an app that runs under the NAS operating system, rather than a file that the NAS is serving. You can access the data area from your logon, you'd need to move the Sonospy app to the app area.

Once you get the code on there and get Python installed, then yes you run it the same way as on Windows, but using paths from the NAS and not Windows.

What NAS do you have?

You need to be able to login to the NAS

On 06/11/14 10:25, davetucker wrote:

Thanks for that info , how would I know if my NAS CAN RUN PYTHON ? Would I just be a simple case of copying the folder from my PC to a folder on the nas aNd running it exactly the same as I would under windows ?

I did fortran 77 back in the day !! And then ended up using uniface 4gl for the last 20 years !!!!

Thanks

Dave

Sent from my iPad

On 6 Nov 2014, at 09:52, Mark Henkelis notifications@github.com wrote:

If the NAS can run Python, then it can run on the NAS. So you can run it on a QNAP for instance (I've run it on a Buffalo before too). It's not tuned to run on a NAS mind - when I get round to it I'll run it on my QNAP. It could also be run on a RaspberryPi - I started looking at tuning it for that with large databases but got distracted.

My first language was Fortran and I'm older than you :)

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Thursday, 6 November, 2014 6:25:43 AM Subject: Re: [sonospy] sort order (#76)

Hi

Worked through the userindex.ini file and thanks to the default code in there got it working , thanks, it is a great piece of software

One other question , which I don't think is possible is ...... Is it possible to implement and run all elements of the application on a NAS ? As opposed to just accessing my music folder which resides on the nas ? That way sonospy will always be up and running when I use sonos , rather than me turning on the PC and starting up sonospy ?

Unfortunately being a software developer myself , and in my late 40's !! I am somewhat still working on legacy coding languages from the early 90's so not familiar with Python

Thanks again for your help, and advice

Kind regards Dave

Sent from my iPad

On 5 Nov 2014, at 09:40, Mark Henkelis notifications@github.com wrote:

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Wednesday, 5 November, 2014 6:55:14 AM Subject: Re: [sonospy] sort order (#76)

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub

https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-61957551.

Thanks for the reply , sounds a bit scary !!, I think I can ssh on to the Wd mybooklive as I did this once before to change some settings regarding twonky , but I'm not sure how I would go about installing Python and running it , maybe I'll settle for leaving the pc on and running as is ? :-) or maybe I'll be brave and investigate further , thanks for the pointer though.

Hope you don't mind , but I have another question ? I was trying to get sonospy to show in the universal search , particularly on ipad , iPhone .. At the mo it just does not see it at all ? I saw one post about some XMl file , but not found anything else , should this feature just work ? I am using the alternate index and I think SMAPI SERVICE ( as I added my sonospy database via services , from within sonos), two points I think this list said were pre requisites

Do you have any clues as to what I may need to do/setup to get it to be visible in the search window, I took an album and placed it in my Overflow sonospy database under a different artist name to ensure that the reason wasn't simply because it already existed within my main music lib , but this wasn't the case as I can see both albums via the sonospy service by looking at the two separate artists

Many thanks for your assistance

Dave

Sent from my iPad

On 6 Nov 2014, at 18:59, Mark Henkelis notifications@github.com wrote:

If the NAS doesn't offer you a web interface to load and run programs, you'll need to be able to log in to it via telnet or ssh (some make that easy, others don't). Once you get logged in, you can check whether Python is installed (it's usually possible to install it if it isn't).

Where you store apps vs where data is stored is usually different - you'll be placing an app that runs under the NAS operating system, rather than a file that the NAS is serving. You can access the data area from your logon, you'd need to move the Sonospy app to the app area.

Once you get the code on there and get Python installed, then yes you run it the same way as on Windows, but using paths from the NAS and not Windows.

What NAS do you have?

You need to be able to login to the NAS

On 06/11/14 10:25, davetucker wrote:

Thanks for that info , how would I know if my NAS CAN RUN PYTHON ? Would I just be a simple case of copying the folder from my PC to a folder on the nas aNd running it exactly the same as I would under windows ?

I did fortran 77 back in the day !! And then ended up using uniface 4gl for the last 20 years !!!!

Thanks

Dave

Sent from my iPad

On 6 Nov 2014, at 09:52, Mark Henkelis notifications@github.com wrote:

If the NAS can run Python, then it can run on the NAS. So you can run it on a QNAP for instance (I've run it on a Buffalo before too). It's not tuned to run on a NAS mind - when I get round to it I'll run it on my QNAP. It could also be run on a RaspberryPi - I started looking at tuning it for that with large databases but got distracted.

My first language was Fortran and I'm older than you :)

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Thursday, 6 November, 2014 6:25:43 AM Subject: Re: [sonospy] sort order (#76)

Hi

Worked through the userindex.ini file and thanks to the default code in there got it working , thanks, it is a great piece of software

One other question , which I don't think is possible is ...... Is it possible to implement and run all elements of the application on a NAS ? As opposed to just accessing my music folder which resides on the nas ? That way sonospy will always be up and running when I use sonos , rather than me turning on the PC and starting up sonospy ?

Unfortunately being a software developer myself , and in my late 40's !! I am somewhat still working on legacy coding languages from the early 90's so not familiar with Python

Thanks again for your help, and advice

Kind regards Dave

Sent from my iPad

On 5 Nov 2014, at 09:40, Mark Henkelis notifications@github.com wrote:

You can already get a recently added album option if you use the more advanced user indexing and add a new index - that way you get to keep your normal album index and get another with the new order (which is probably why nobody else has found the bug). Details of how to do it are in the ini files. We have a google group too, where the guys can share their index setups with you:

https://groups.google.com/forum/#!forum/sonospy-devel

----- Original Message ----- From: "davetucker" notifications@github.com To: "henkelis/sonospy" sonospy@noreply.github.com Cc: "Mark Henkelis" mark.henkelis@tesco.net Sent: Wednesday, 5 November, 2014 6:55:14 AM Subject: Re: [sonospy] sort order (#76)

Thanks so much for getting back to me , and that you've taken the time to look into it

Having a most recently added album sort option will be the perfect solution for me

If you manage to sort it , let me know and I will update

Once again , thanks

Dave

Sent from my mobile tellingbone

On 4 Nov 2014, at 23:27, Mark Henkelis notifications@github.com wrote:

Sorry about the delay - it looks like a bug, the sort order gets overwritten for this default index. I'll check the rest of the code and fix it.

On 22/10/14 07:44, davetucker wrote:

HI

thanks for your quick response , really appreciated , i have cut the below from my defaultindex.ini file ( i also added the entry prefix to ensure that sonos was picking up my changes) , but still it does not seem to recognise the sort order ??

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified desc entry_suffix=lastmodified entry_prefix=lastmodified icon=icon_albums index=track icon=icon_tracks here is my sonos screen shot ( albums , which still show in name order ) only working on a subset at the mo to get it all working . other than this little issue , its really good , ( thanks) , any ideas re the sort order appreciated

thanks dave

From: Mark Henkelis Sent: Tuesday, October 21, 2014 8:43 PM To: henkelis/sonospy Cc: davetucker Subject: Re: [sonospy] sort order (#76)

sort_order= needs to come after index= (for the index you want to affect). Try:

tree=album/track title=Albums icon=icon_albums index=album sort_order=lastmodified entry_suffix=lastmodified icon=icon_albums index=track icon=icon_tracks

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub

https://github.com/henkelis/sonospy/issues/76#issuecomment-60043116.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub . — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/henkelis/sonospy/issues/76#issuecomment-61957551.

— Reply to this email directly or view it on GitHub.

Hope you don't mind , but I have another question ? I was trying to get sonospy to show in the universal search , particularly on ipad , iPhone .. At the mo it just does not see it at all ? I saw one post about some XMl file , but not found anything else , should this feature just work ? I am using the alternate index and I think SMAPI SERVICE ( as I added my sonospy database via services , from within sonos), two points I think this list said were pre requisites

Do you have any clues as to what I may need to do/setup to get it to be visible in the search window, I took an album and placed it in my Overflow sonospy database under a different artist name to ensure that the reason wasn't simply because it already existed within my main music lib , but this wasn't the case as I can see both albums via the sonospy service by looking at the two separate artists

It should just work, but only for searches that are defined in the ini you use. I guess you're using userindex.ini now - at the bottom of that file you define the searches. Whatever you define there will show up in universal search. The ini I'm testing with doesn't have anything set for artists, so nothing shows up in that search for Sonospy, but it does have others that do (including the Album/Artist/Track example and Playlist Tracks). The ini is:

[searches]

This search entry will search across the album, artist and track

indexes at the same time:

multisearch=Albums,Artists,Tracks title=Album/Artist/Track

This search entry will search for tracks across all Playlists:

subsearch=Playlists/track title=Playlist Tracks

subsearch=Recent rips/artist title=Recent/Artist

search=Tracks title=tracks

search=Albums title=albums

Hi thanks for the info , i have stripped my userindex.ini file and attached , should i see these “search categories” in the controllers ( ipad - across the top of the screen i just see ARTIST TRACKS ALBUMS STATIONS COMPOSERS HOSTS PODCASTS&SHOWS) which are the default sonos categorties

and for the desktop controller , should i see my sonospy in the drop down lists ( which i dont )

i am not sure of the relevance of the 5e0fc086-1c37-4648-805c-ec2aba2b0a27.xml file ( if there is any , but it does not contain anything that relates to any searche categories ) ??

any help greatly appreciated

thanks again

dave

I don't see any of your attachments, probably best to paste them into the message - that said, I'd prefer you to put questions onto the Sonospy group instead if you can.

I have the following flags set in pycpoint.ini:

 [indexing]
 alternative_indexing=Y
 user_indexes=Y

In userindex.ini, I have the following settings:

 [searches]

 multisearch=Albums,Artists,Tracks
     title=Album/Artist/Track

 subsearch=Playlists/track
     title=Playlist Tracks

 subsearch=Recent rips/artist
     title=Recent/Artist

 search=Tracks
     title=tracks

 search=Albums
     title=albums

 search=Artists
     title=artists

I run with those settings from the command line as:

 ./sonospy_proxy -sSonospy=Mark,mark.db,userindex.ini -r

This generates a 5e0fc086-1c37-4648-805c-ec2aba2b0a27.xml file with the following search entries:

 <SearchCategories>
     <CustomCategory mappedId="R0:000000001"

stringId="Album/Artist/Track" />

     <Category id="tracks" mappedId="R15:700000000" />
     <Category id="albums" mappedId="R1:300000000" />
     <Category id="artists" mappedId="R5:200000000" />
     <CustomCategory mappedId="R0:000000007" stringId="Keyword" />
 </SearchCategories>

On the desktop controller I see Mark in the search list, when I select it and search I get the entries above to choose from.

On the iPhone I see Mark appearing in the standard search entries above, plus I get extra entries for the custom categories above.

I should also say that I have index entries in userindex.ini that contain all the searches entries within their trees.

henkelis / sonospy

sort order #76

This search entry will search across the album, artist and track

indexes at the same time:

This search entry will search for tracks across all Playlists: