SageTV Community  

Go Back   SageTV Community > SageTV Development and Customizations > SageTV v7 Customizations > Diamond
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

Diamond This forums is for discussing the user-created Diamond plugin for SageTV.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-21-2011, 04:47 PM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Help - migration to new setup, Diamond movie views now messed up

Hi guys!

Lost the motherboard in my server, built a new system, etc. Windows 7 64bit running Sage beta 7.1.5. 3TB of storage, woohoo.

I used the approach of naming my server, paths, etc. the same as my previous setup, moved files (videos themselves + wiz.bin) from old HDDs to the new locations, and used the "advanced_video_file_recovery = true" method that is detailed here: http://forums.sagetv.com/forums/show...610#post265610

Everything worked fine, Sage picked up my recordings and imports, etc.

Of course, the next thing I did was install Diamond (latest version in repository). Can't get by without it.

Everything is fine with Diamond *except* now the include/exclude functionality in the movie views seems to be wonky. Previously, I just used a single folder include to point at my imported movies and all was well. Now, if I use that single include, it appears to be treated as an exclude. Specifically, if I create a new view, it starts out correctly seeing "everything". When I add the include for my movies, they actually disappear (as if it's an exclude), and all I see are movie Recordings (I have the filter set to show them).

If I go the other way and start with "everything" and then do excludes, the first exclude in the list is ignored (which I think is a known bug right now). Other excludes are honored, but of course that doesn't help me because the first exclude in the list is an important one.

I have a feeling that whatever Sage did to the wiz.bin during the "advanced video file recovery" thing may have resulted in data that confuses Diamond. Or maybe not, what do I know?

I can turn on logging and get you logs, but wondering what actions you would want me to execute while logging. Also wondering if there is a known trick or issue with the approach I took that might help. I've never lost/rebuilt my Sage server before so I don't have experience with a rebuilt wiz.bin, etc.

Any ideas?
Reply With Quote
  #2  
Old 04-21-2011, 05:01 PM
jorton jorton is offline
Sage Icon
 
Join Date: Jul 2005
Location: Canada
Posts: 1,273
There was a minor issue in Diamond 3.2 with the include/exclude folder filtering that is already fixed for next build (don't ask when ), see this issue,

http://code.google.com/p/sagediamond...an=1&start=100

There is also a temporary workaround from jusjoken in the details.

Cheers,

Jeremy
Reply With Quote
  #3  
Old 04-21-2011, 05:18 PM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Quote:
Originally Posted by jorton View Post
There was a minor issue in Diamond 3.2 with the include/exclude folder filtering that is already fixed for next build (don't ask when ), see this issue,

http://code.google.com/p/sagediamond...an=1&start=100

There is also a temporary workaround from jusjoken in the details.

Cheers,

Jeremy
i understand the EXCLUDE bug. please re-read my post - what i'm experiencing is a problem when trying to do a single INCLUDE. this worked 2 days ago (with Sage 7.1.5 and Diamond 3.2) prior to my rebuild, so i don't think that the reported bug applies to INCLUDES.

i'll try the trick tonight to see if it does apply to INCLUDES, but then i'll wonder how it worked without the trick 2 days ago

again, if logs would help, let me know what actions to take while logging.
Reply With Quote
  #4  
Old 04-21-2011, 05:48 PM
jorton jorton is offline
Sage Icon
 
Join Date: Jul 2005
Location: Canada
Posts: 1,273
Quote:
Originally Posted by uncledig View Post
i understand the EXCLUDE bug. please re-read my post - what i'm experiencing is a problem when trying to do a single INCLUDE. this worked 2 days ago (with Sage 7.1.5 and Diamond 3.2) prior to my rebuild, so i don't think that the reported bug applies to INCLUDES.

i'll try the trick tonight to see if it does apply to INCLUDES, but then i'll wonder how it worked without the trick 2 days ago

again, if logs would help, let me know what actions to take while logging.
Sorry missed that, here's jusjoken's description of how to use include/exclude in Diamond that might help,

http://forums.sagetv.com/forums/show...37&postcount=7

Cheers,

J
Reply With Quote
  #5  
Old 04-21-2011, 06:01 PM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Quote:
Originally Posted by jorton View Post
Sorry missed that, here's jusjoken's description of how to use include/exclude in Diamond that might help,

http://forums.sagetv.com/forums/show...37&postcount=7

Cheers,

J
thanks. i understand how to use and configure the includes/excludes.

are you saying that you don't believe this is a bug and/or that log files would not help research it? you keep pointing me to things that i already know and which don't address the problem as i've stated it, and not addressing the question of how to address or research the actual problem.

i think you're a Diamond developer, but if you're not, maybe you're just trying to be helpful none of the things you've pointed to address the problem though.
Reply With Quote
  #6  
Old 04-21-2011, 06:17 PM
jorton jorton is offline
Sage Icon
 
Join Date: Jul 2005
Location: Canada
Posts: 1,273
Quote:
Originally Posted by uncledig View Post
thanks. i understand how to use and configure the includes/excludes.

are you saying that you don't believe this is a bug and/or that log files would not help research it? you keep pointing me to things that i already know and which don't address the problem as i've stated it, and not addressing the question of how to address or research the actual problem.

i think you're a Diamond developer, but if you're not, maybe you're just trying to be helpful none of the things you've pointed to address the problem though.
Yes I am one of the devs. The only non coder in the bunch so bear with me

I see you are saying that the single include is acting like a single exclude, I'll do some messing around and see if I can duplicate and post back.

J
Reply With Quote
  #7  
Old 04-21-2011, 06:26 PM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Quote:
Originally Posted by jorton View Post
Yes I am one of the devs. The only non coder in the bunch so bear with me

I see you are saying that the single include is acting like a single exclude, I'll do some messing around and see if I can duplicate and post back.

J
thanks Jeremy! i'm not sure you'll be able to recreate it because i'm suspicious that it's related to the recovery/reimport procedure i detailed in my original post.

btw, i'm also now noticing that a new movie view (no folder includes/excludes, no filtering) is now showing some non-movie items (for instance, Letterman recordings) from my Recordings folders. very whacky.

when you're ready for logs, let me know what actions you want logged and i'll provide them.
Reply With Quote
  #8  
Old 04-21-2011, 08:38 PM
jorton jorton is offline
Sage Icon
 
Join Date: Jul 2005
Location: Canada
Posts: 1,273
Quote:
Originally Posted by uncledig View Post
thanks Jeremy! i'm not sure you'll be able to recreate it because i'm suspicious that it's related to the recovery/reimport procedure i detailed in my original post.

btw, i'm also now noticing that a new movie view (no folder includes/excludes, no filtering) is now showing some non-movie items (for instance, Letterman recordings) from my Recordings folders. very whacky.

when you're ready for logs, let me know what actions you want logged and i'll provide them.
Hey uncledig,

I can't seem to make it happen. I have 4 network drives setup as imported media folders as follows,

K:\Movie Library 1\
L:\Movie Library 2\
M:\Movie Library 3\
N:\Movie Library 4\

When I do a single include on K:\Movie Library 1\ (see attached) I only see the movies in that folder not all four imported folders (with no other include/excludes). I believe this is the correct behavior, unfortunately not what you are seeing by the look of it.

At this point I'm not sure what to even look for in the logs so I'll have to ask Plucky, EP or jusjoken to have a look but I'd wait to see if they have any suggestions before gathering logs etc...

Sorry,

Jeremy
Attached Images
File Type: jpg Folder_Single_Include_Test.jpg (100.8 KB, 175 views)

Last edited by jorton; 04-21-2011 at 08:43 PM.
Reply With Quote
  #9  
Old 04-22-2011, 06:21 AM
PLUCKYHD PLUCKYHD is offline
SageTVaholic
 
Join Date: Dec 2007
Posts: 6,257
Have you tried clearing the diamond properties complete via the option in the main menu.

This is not a known issue and honestly I don't see how it could be happening without a messed up properties file. I have several view with single inclusions that work well and looking at the code the single inclusion is pretty straight foward.

Try cleaing the properties and let me know the results.

Plucky
Reply With Quote
  #10  
Old 04-22-2011, 08:43 AM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Quote:
Originally Posted by PLUCKYHD View Post
Have you tried clearing the diamond properties complete via the option in the main menu.

This is not a known issue and honestly I don't see how it could be happening without a messed up properties file. I have several view with single inclusions that work well and looking at the code the single inclusion is pretty straight foward.

Try cleaing the properties and let me know the results.

Plucky

Hi Plucky,

I deleted the Diamond settings via the debug menu. No change in behavior.

The only thing I did to the properties file from this installation was turn ON (and then afterwards, turned OFF) the advanced_video_file_recovery switch. everything else in the properties file is "stock", i.e., created by Sage as part of a normal install and setup.

Is there anything I should look for in the properties file that might cause this behavior?

and again, is there anything i can capture in logs that might hint at why Diamond is responding this way to my import folders and the includes?
Reply With Quote
  #11  
Old 04-22-2011, 09:14 AM
PLUCKYHD PLUCKYHD is offline
SageTVaholic
 
Join Date: Dec 2007
Posts: 6,257
Quote:
Originally Posted by uncledig View Post
Hi Plucky,

I deleted the Diamond settings via the debug menu. No change in behavior.

The only thing I did to the properties file from this installation was turn ON (and then afterwards, turned OFF) the advanced_video_file_recovery switch. everything else in the properties file is "stock", i.e., created by Sage as part of a normal install and setup.

Is there anything I should look for in the properties file that might cause this behavior?

and again, is there anything i can capture in logs that might hint at why Diamond is responding this way to my import folders and the includes?
Nothing in the logs that would really tell me anything I would have to send you a special debug jar to get any logging. Can you look at the default info view and see the path it is reporting and see if it matches the include fitler?
Reply With Quote
  #12  
Old 04-22-2011, 09:57 AM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
Quote:
Originally Posted by PLUCKYHD View Post
Nothing in the logs that would really tell me anything I would have to send you a special debug jar to get any logging. Can you look at the default info view and see the path it is reporting and see if it matches the include fitler?
Sure - let me make sure I'm clear on what you're asking:

look at the default info view for one of the movies in the folder that i want to include, and ensure that it is the same path that is setup as an import folder (and therefore a folder that i can select for an include). then make sure that this import folder path is the one i'm choosing for the include?
Reply With Quote
  #13  
Old 04-22-2011, 10:38 AM
uncledig uncledig is offline
Sage User
 
Join Date: Jul 2010
Location: Houston
Posts: 24
there we go!

my import path for my movies had all lowercase letters, and my previous path (and therefore the wiz.bin path) had some caps.

so, Diamond doesn't like it if the import path and stored wiz.bin path have different captilization. The core Sage functionality doesn't seem to mind.

//mediacenter/e/video/dvds

vs.

//mediacenter/e/Video/DVDs

thanks guys!
Reply With Quote
  #14  
Old 04-22-2011, 12:49 PM
PLUCKYHD PLUCKYHD is offline
SageTVaholic
 
Join Date: Dec 2007
Posts: 6,257
Quote:
Originally Posted by uncledig View Post
there we go!

my import path for my movies had all lowercase letters, and my previous path (and therefore the wiz.bin path) had some caps.

so, Diamond doesn't like it if the import path and stored wiz.bin path have different captilization. The core Sage functionality doesn't seem to mind.

//mediacenter/e/video/dvds

vs.

//mediacenter/e/Video/DVDs

thanks guys!
No problem all paths are always case sensitive
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Diamond Sub-theme: "Diamond MKANET Mod" (Version 1.1) mkanet Diamond 14 04-13-2011 08:34 AM
For Team Diamond: Seeking Permission to use Diamond Screenshots DigiTechRx Diamond 0 03-11-2011 05:21 PM
Diamond Sub-theme: Diamond MKANET Mod mkanet SageTV v7 Customizations 2 02-21-2011 05:18 AM
XP --> WHS Migration Trepidati0n General Discussion 6 08-06-2009 05:19 AM
3.5 drive in 5.25 bay and HD migration Stobor Hardware Support 0 08-30-2004 12:36 AM


All times are GMT -6. The time now is 01:35 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.