Best practices to avoid/fix the file system view problem with BMT?

[lash]

I've believe I've done my reading, however I am brand new to SageTV so I could've missed something. I am using Phoenix and the beta SageMC all from the very last post in the SageMC Pre-release thread (release 12). However, I am still getting a totally messed up file system view in SageMC whenever I refresh my library.

I followed the instructions here: https://docs.google.com/Doc?docid=0A...tya2JmZg&hl=en. This is a totally clean SageTV.

I installed SageTV. I installed SageMC. I Installed the newest beta (release 12) SageMC from the pre-release thread as well as the phoenix file posted there. I installed Jetty. I installed the newest BMT. I configured it in the web app as well as in SageMC. I added a directory of videos to SageTV. I messed with the regex so BMT web recognized and found my media metadata.

Everything was looking ok, then I added another directory to SageTV and refreshed the media. All of a sudden file system view shows only 1 video and there are no directories or anything. If I choose the all videos view, I get a long list of all my videos, so they are all still there in SageTV's database.

If I am reading correctly, these are the symptoms of an issue with SageMC and BMT 3.

I don't care too much about SageTV's current database of my videos (aka my current wiz.bin, I believe). This is a new setup and I am still playing, so deleting wiz.bin is not an issue.

What I would like to know is what is the best practice to avoid this happening when I do care about SageTV's database of my videos?

Thank you!

[stuckless]

So, based on your description, it looks like you've installed the add-ons in the following order,
SageMC
SageMC (b12)
Phoenix
Jetty
BMT

If that is the order, then i can see 1 problem. SageMC (b12) is newer than BMT, but both SageMC (b12) and BMT share 1 critical library, phoenix.jar. So, given that BMT (3.1) is older than the SageMC (b12), then when you installed BMT it would have downgraded SageMC's phoenix.jar to an older version.

Currently the install order should be...
SageMC
BMT
SageMC (betas)

And jetty can go in at any time.

Part of the enhancement that meinmaui did in sagemc to fix the filesystem view (caused by bmt), relies on an api call in the version of the phoenix.jar that ships with the betas, but is not included in the bmt 3.1 (because it's older).

Eventually, I'll get around to do a new build of bmt that will also contain the updated phoenix.jar.

[lash]

Thanks again! Its always the little things, isn't it? That seems to have cleared up the problem.

[chrisc983]

Is their any way of fixing this issue besides a reinstall of SageTV and installing it in the correct order as I have been using other beta versions prior to using BMT. I tried reverting back to the original sagemc, extracting the BMT to sagetv directory, and then loading the latest sagemc beta. But the file system view only still works in the original sagemc.

Edit: Nevermind got it going.

[heffneil]

I am having a weird problem and I think it is related to the above. I ended up upgraded to BMT 4.0(18) and ever since then the File System View in SageMC isn't showing all of the movies. I have to change the filter to all movies and then I see everything. Any ideas what might be wrong here?

Thanks!

Neil

[Dreameriz]

I had the same issue but i went to build 21 and was still having the same issue tell i did a refresh libary entire scan and that fixed my issue. Other then the first folder is still missing the first letter of the folder

[stuckless]

@Dreameriz - maybe you could do the vfs debug logging that's outlined in the 4.0 beta thread and send me the support logs. I wasn't aware that the "missing first letter" issue was still an issue.

[Dreameriz]

Here is the log from my vfs


Thanks again for this great Tool and all the time that you put into it is so aswome'

[stuckless]

Originally Posted by Dreameriz

Here is the log from my vfs


Thanks again for this great Tool and all the time that you put into it is so aswome'

Thanks for the zip file... but it doesn't contain the log files...just the configurations If you use the "Create Support Request" from the "Tools" menu, in the web ui, then it will build a zip file will all the log files. You can then post or email that zip file.

Thanks,
Sean.

[heffneil]

I upgraded to the latest release of the beta and the problem is solved!

Thanks,

Neil