home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anthony Vaughan" data-source="post: 1286981" data-attributes="member: 153283"><p>Well, I finally got there. It was your hint about actor info that led me to the solution.</p><p></p><p>I think there is a little confusion with terminology as well that can lead to confusion. In the GUI, the settings refer to actor 'details' and in the column heading in the configuration app it says actor details:</p><p></p><p>[ATTACH=full]209449[/ATTACH]</p><p></p><p>In the database this information is held in a table called 'actorinfo' and other screen objects refer to this as actor info, which is really the same as actor details.</p><p></p><p>When you want actor details, the grabber and MP apps have to do a lot more work, which I mistook for being caused by looking for all actors in a movie when it was actually getting actor details/info. When the grabber doesn't do all of the iterations (the extra work), the actor info table gets very little information. It may be worth looking at why it needs so much extra work to get the full actor info because I suspect there is a way to get that data without all of the extra processing.</p><p></p><p>In the meantime, I'll change the wording on the screen (configuration) to make it clear that it is actor details that will be optional.</p><p></p><p>Thanks for helping me to finally get this sorted out.</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1286981, member: 153283"] Well, I finally got there. It was your hint about actor info that led me to the solution. I think there is a little confusion with terminology as well that can lead to confusion. In the GUI, the settings refer to actor 'details' and in the column heading in the configuration app it says actor details: [ATTACH type="full"]209449[/ATTACH] In the database this information is held in a table called 'actorinfo' and other screen objects refer to this as actor info, which is really the same as actor details. When you want actor details, the grabber and MP apps have to do a lot more work, which I mistook for being caused by looking for all actors in a movie when it was actually getting actor details/info. When the grabber doesn't do all of the iterations (the extra work), the actor info table gets very little information. It may be worth looking at why it needs so much extra work to get the full actor info because I suspect there is a way to get that data without all of the extra processing. In the meantime, I'll change the wording on the screen (configuration) to make it clear that it is actor details that will be optional. Thanks for helping me to finally get this sorted out. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
Top
Bottom