Lots of unstable behavior, maybe its me?
Posted: Mon Mar 03, 2014 3:27 amNew user here, longtime system admin. I was very excited when I installed subsonic and got it working, only to run in to a number of .... well, hopefully not too significant ... usability and/or stability issues.
I'm still ramping up and figuring things out, but I have a couple of burning questions that I tried to find answers for in the forums and FAQ but there is a lot of confusion over whether these things are fixed, behaving as designed, or just still broken.
1. Suppressing folders during indexing so they don't clutter the results, program author here says was fixed, but as described, it is not - for me and others. Anyone got anything for this?
2. Indexing/record corruption problem. I originally created a media folder with ONE mp3 in it. The only thing significant about this was the folder was a UNC path to the file and I originally indexed with with the "fast" method. This worked, but what I did not realize at the time was the "fast" network method does not bring along all the content that you would want, and only showed the file with its name on the left frame not in the main content frame. Kind of weird behavior but I think that's just what the app does when it does 'fast' indexing (?). In any event, I ditched that approach, deleted the shared folder, reindexed, ran the 'clean up', restarted the service, created a new local shared folder on C: and put that exact same file in it.
For the life of me I cannot get this file to appear in the normal content window now, it only ever appears on the left under the playlist section and does not appear anywhere on my mobile app or when i browse/search for files in the main window. IMO this is some sort of database corruption which leads me to 3.
3. Is there a way to access the database directly to help identify and fix indexing and corrupt record problems?
4. Is there a published bug tracker?
I'm very keen on this software and hope I can continue to use and support it, the implementation is very solid and I like the overall design; when software is not predictable and stable features can only go so far, but i am still learning. I hope to be a long time supporter - nice to meet you all and thanks in advance for your help!
-kth
I'm still ramping up and figuring things out, but I have a couple of burning questions that I tried to find answers for in the forums and FAQ but there is a lot of confusion over whether these things are fixed, behaving as designed, or just still broken.
1. Suppressing folders during indexing so they don't clutter the results, program author here says was fixed, but as described, it is not - for me and others. Anyone got anything for this?
2. Indexing/record corruption problem. I originally created a media folder with ONE mp3 in it. The only thing significant about this was the folder was a UNC path to the file and I originally indexed with with the "fast" method. This worked, but what I did not realize at the time was the "fast" network method does not bring along all the content that you would want, and only showed the file with its name on the left frame not in the main content frame. Kind of weird behavior but I think that's just what the app does when it does 'fast' indexing (?). In any event, I ditched that approach, deleted the shared folder, reindexed, ran the 'clean up', restarted the service, created a new local shared folder on C: and put that exact same file in it.
For the life of me I cannot get this file to appear in the normal content window now, it only ever appears on the left under the playlist section and does not appear anywhere on my mobile app or when i browse/search for files in the main window. IMO this is some sort of database corruption which leads me to 3.
3. Is there a way to access the database directly to help identify and fix indexing and corrupt record problems?
4. Is there a published bug tracker?
I'm very keen on this software and hope I can continue to use and support it, the implementation is very solid and I like the overall design; when software is not predictable and stable features can only go so far, but i am still learning. I hope to be a long time supporter - nice to meet you all and thanks in advance for your help!
-kth