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 2
Plugin Development
Moving Pictures MP2
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="MJGraf" data-source="post: 1049908" data-attributes="member: 17886"><p>Well, it seems like I need to give some background here...</p><p></p><p>To be able to make an app user-friendly in the long run, it is a necessity to have the technical concept perfectly right. You can also make a user-friendly app without a good technical and conceptual base (see MP1) but the problem is that it will end up in "specific solutions for specific needs" that do not fit into one big concept. As a result, it will be very difficult to add new functionality later on (see again MP1).</p><p></p><p>Let me give you an example: Moving pictures is the best thing to watch movies I have ever seen. The problem is, however, that it is more or less a separate application and - maybe besides the skin engine and the player - could also exists without MP1. The reason is that someone decided that we need something like Moving Pictures, realized that close to nothing inbuilt in MP1 could be used for it and developed Moving Pictures including its scraper engine and its scripting engine completely separately from MP1. Moving Pictures has its own database - not connected with MP1 as such. The same holds true for TVSeries, etc.</p><p>Now someone decided that times have changed and we need something like MPExtended and WebMP - in particular for mobile devices. The problem is that MPExtended now has to have separate ways to access the databases of Moving Pictures, TVSeries, MyMusic, etc. There is no "one big concept" behind it, which makes it more difficult to integrate a new technology such as MPExtended.</p><p>This, by the way, may also be the reason why in this thread there are a lot of requests that seem to target the same thing - watching Movies and Series in MP2. And from an MP1 perspective, these requests would all target the same "part of MP1", i.e. Moving Pictures for movies and TVSeries for series. But this is not the case for MP2...</p><p></p><p>MP2 is completely different in that respect. There is one single database for ALL kinds of "Media Items", be it movies, series, music, tv recordings, etc. Everyone may later on add new "kinds of Media Items" - not the MP1 way by providing a completely separate plugin with its own database etc. But the MP2 way: by telling the system "hey, there is a new kind of Media Items. They can be accessed via [...] Metadata can be scraped like [...] and what you find there are movies". MP2 will then automatically start importing these new Media Items in its one and only database and when the programmer did this work correctly, he would not even need to write his own frontend plugin. Since he told the system that the new Media Items are movies, those movies would immediately show up in the Movies section of MP2 Client. An example for this could be an online video store. What you need to make this work is a so called "ResourceProvider" and a "ResourceAccessor" (these tell the system how to access the videos online) and a MetadataExtractor (which is responsible for scraping metadata). That's all...</p><p></p><p>Now you will probably say "well, that's what I told you. You only talk tech-speak, no one understands this and what we want is a user-friendly MP2". And I tell you that the tech-thingy is necessary to make it the way you want to have it. Imagine in the online video store example - what would be necessary to make the online video store work: 1) You install the plugin. 2) you add a Share with the "OnlineVideoStoreXYZResourceProvider". 3) Enter your credentials of the online video store. 4) wait until the import is finished 5) enter Movies and watch the movies of your online video store. As you see, using this online video store is 100% identical with adding your own movie collection and watching those videos. The MP1 way would have been that you install the respective plugin and then you have to open its new config tool in the MP1 Config utility, get used to it, make a lot of choices for various settings and finally you end up with a new entry in your main menu. What you find there (buttons, menus, etc.) would most likely be different from what you find in Moving Pictures, e.g., although both do the same: providing access to movies - just from different sources. That's the result of "one big concept" in MP2 - combined with the extensibility that is available through the plugin system.</p><p></p><p>Against this background, back to the the question "why do all the movies also show up in Videos" - (and for breeze: why do I find some of my series only in videos): The concept behind this behavior is that MP2 thinks in "MediaAspects". There is a "MovieAspect", a "SeriesAspect", a VideoAspect, a MusicAspect, etc. Every MediaItem has one or more of these "Aspects". Every "Aspect" holds one or more so called "Attributes". An attribute of the MusicAspect e.g. is the "Artist", an attribute of the VideoAspect is the "VideoBitrate".</p><p>Now, historically, there was only the VideoAspect (besides the PicturesAspect and the MusicAspect). Furthermore there was only the Video section in MP2 Client. So all your Movies, Series and anything else that was a Video was only shown in the Video section of MP2 Client. Then Morpheus came along and thought, there is something missing. We need something like Moving Pictures and TVSeries in MP2. And so he added the MoviesAspect and the SeriesAspect together with the respective front ends in MP2 Client. But he did not do so as it would be in MP1 - by writing a completely separate plugin. In the MP2 architecture this wouldn't make sense. Every movie IS at the same time a video - the same is true for series. And we already import all the information like "VideoBitrate" we also need for movies and series. What he did is that he added the MoviesAspect and the SeriesAspect additionally to the VideoAspect and only included additional Attributes specific for Movies and Series (such as the IMDB ID for Movies or the "Season" for series).</p><p>The result was that the Movies section in MP2 Client only shows "videos" having a MovieAspect - the Series section only shows "videos" having a SeriesAspect. But still every movie and every series has a video aspect - which is why they are (still) all shown in the VideoSection.</p><p>And as to your problem, breese, Lehmden is completely right. Apparently the VideoMetadataExtractor has found information for one of your series and therefore added a VideoAspect with that information. This is why it shows up in the video section of MP2 client. But the "SeriesMetadataExtractor" could not find information for that series and therefore no SeriesAspect was added. This is the reason why this series does not show up in the series section of MP2 client.</p><p>Finally: How does MP2 decide which Apsect to add to a MediaItem. This is a decision that mainly the user makes when adding the Share. If you add a share, you have to choose a media category. If you choose "Music", MP2 will ask the MusicMetadataExtractor to find metadata for all the MediaItems in this Share and if the MedatadaExtractor is able to find information, he will add a MusicAspect with that information to the respective MediaItem. If you choose "Videos" as media category, MP2 will ask the VideoMetadataExtractor to gather information on the MediaItems and - if successful - will add a VideoAspect. If you choose "Movies" (or Series) when adding your Share, you will notice that at the same time "Videos" is also checked. This is the result of Movies and Series being a "subtype" of Videos. And this means that MP2 will first ask the VideoMetadataExtractor to find information on the MediaItems in the Share and then also ask the MoviesMetadataExtractor to find additional information specific for Movies. As a result, if the VideoMetadataExtractor was successful, the MediaItem will have a VideoAspect, if the MovieMetadataExtractor was also successful, there will also be a MovieAspect. </p><p></p><p>Now to all the requests in this thread:</p><ul> <li data-xf-list-type="ul">As mentioned above, the fact that all Movies and Series are also shown in Videos is a leftover from MP2's history. It is surely not too difficult to tell the frontend only to display videos in the video section that do not have a MovieAspect or a SeriesAspect.</li> <li data-xf-list-type="ul">Everything related to "how is it displayed in the frontend" I have to pass to Morpheus. He did a great job there in the past and he constantly tries to improve the user experience by adding new features. But please bear in mind: The MP2 development team only consists of very few people. Morph is more or less the only dev who currently works on front end improvements. We have just made TVE3.5 work with SQLite which makes it possible for many more people to try "native MP2 tv". As a result there were many requests on how to improve the TV frontend of MP2. And Morph immediately started to implement as many requests as possible - including a new EPG view, etc. Due to the lack of manpower, this all takes some time - but I am sure, he will not refuse to add some goodies to the Movies or Series sections when he has finished the improvements for SlimTV client...</li> <li data-xf-list-type="ul">All the rest (such as how and what metadata is scraped for what files in what languages, how can this be amended to one's personal needs, etc.) is completely unrelated to the movies or series section in the MP2 Client (unlike in MP1). This is dealt with in the MetadataExtractors and the Importer. And what I can tell you here is that we know that there is still a lot to do. But instead of providing "workarounds" to make feature a or b working, I have decided that we have to change the original concept a bit to have more flexibility. As a result, I will try to write a completely new Importer. This is necessary as we have many requests that the import as such takes too long. The new importer will be able to do a "two pass import", i.e. first only importing the absolutely essential information (in a quick first pass after which you can already find all your movies in the MP2 client - but maybe not yet all the eyecandy such as backdrops, etc.) and in a second pass, which may take longer, all the additional information that takes a lot of time to get (in most cases downloads from the internet). At the same time, I will make sure that the new Importer is able to handle things like "two files (CD1 / CD2) for one movie" or providing the possibility for user interaction during the import (e.g. if TMDB returns two possible matches for a movie, we need the user to choose which of those two is the right one), etc. In the course of this rewrite it may be possible that I also overhaul the current MetadataExtractors - and maybe I will also integrate the scripting engine of Moving Pictures to make it easier for non-devs to extend our scrapers (i.e. MetatadaExtractors). But for these latter things we still need to discuss a lot of things to make sure that we cover every possible use case.</li> </ul><p>After all, the devs definitely read all the posts here in the MP2 forum. And we really appreciate all the feedback we get. We also try to implement as many requests as we can. But please bear with us: We are really only very few people and we all have a real life <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> So it is not possible for us to answer every user post as extensively as this one. As you can see from breese's post, we are not even able to answer all the posts of our testers (sorry for that breese, I had a lot to do in my job lately, but I really read every one of your posts and I'm trying to solve all the bugs you spot and to implement all your suggestions to the extent possible for me - your work is really very much appreciated...)</p><p></p><p>So what can I say: Please keep on testing MP2 and we try to improve it as good as we can. And please post bugs you find and improvements you would like. We DO appreciate it - we just cannot promise to follow up in a few days...</p><p></p><p>Michael</p></blockquote><p></p>
[QUOTE="MJGraf, post: 1049908, member: 17886"] Well, it seems like I need to give some background here... To be able to make an app user-friendly in the long run, it is a necessity to have the technical concept perfectly right. You can also make a user-friendly app without a good technical and conceptual base (see MP1) but the problem is that it will end up in "specific solutions for specific needs" that do not fit into one big concept. As a result, it will be very difficult to add new functionality later on (see again MP1). Let me give you an example: Moving pictures is the best thing to watch movies I have ever seen. The problem is, however, that it is more or less a separate application and - maybe besides the skin engine and the player - could also exists without MP1. The reason is that someone decided that we need something like Moving Pictures, realized that close to nothing inbuilt in MP1 could be used for it and developed Moving Pictures including its scraper engine and its scripting engine completely separately from MP1. Moving Pictures has its own database - not connected with MP1 as such. The same holds true for TVSeries, etc. Now someone decided that times have changed and we need something like MPExtended and WebMP - in particular for mobile devices. The problem is that MPExtended now has to have separate ways to access the databases of Moving Pictures, TVSeries, MyMusic, etc. There is no "one big concept" behind it, which makes it more difficult to integrate a new technology such as MPExtended. This, by the way, may also be the reason why in this thread there are a lot of requests that seem to target the same thing - watching Movies and Series in MP2. And from an MP1 perspective, these requests would all target the same "part of MP1", i.e. Moving Pictures for movies and TVSeries for series. But this is not the case for MP2... MP2 is completely different in that respect. There is one single database for ALL kinds of "Media Items", be it movies, series, music, tv recordings, etc. Everyone may later on add new "kinds of Media Items" - not the MP1 way by providing a completely separate plugin with its own database etc. But the MP2 way: by telling the system "hey, there is a new kind of Media Items. They can be accessed via [...] Metadata can be scraped like [...] and what you find there are movies". MP2 will then automatically start importing these new Media Items in its one and only database and when the programmer did this work correctly, he would not even need to write his own frontend plugin. Since he told the system that the new Media Items are movies, those movies would immediately show up in the Movies section of MP2 Client. An example for this could be an online video store. What you need to make this work is a so called "ResourceProvider" and a "ResourceAccessor" (these tell the system how to access the videos online) and a MetadataExtractor (which is responsible for scraping metadata). That's all... Now you will probably say "well, that's what I told you. You only talk tech-speak, no one understands this and what we want is a user-friendly MP2". And I tell you that the tech-thingy is necessary to make it the way you want to have it. Imagine in the online video store example - what would be necessary to make the online video store work: 1) You install the plugin. 2) you add a Share with the "OnlineVideoStoreXYZResourceProvider". 3) Enter your credentials of the online video store. 4) wait until the import is finished 5) enter Movies and watch the movies of your online video store. As you see, using this online video store is 100% identical with adding your own movie collection and watching those videos. The MP1 way would have been that you install the respective plugin and then you have to open its new config tool in the MP1 Config utility, get used to it, make a lot of choices for various settings and finally you end up with a new entry in your main menu. What you find there (buttons, menus, etc.) would most likely be different from what you find in Moving Pictures, e.g., although both do the same: providing access to movies - just from different sources. That's the result of "one big concept" in MP2 - combined with the extensibility that is available through the plugin system. Against this background, back to the the question "why do all the movies also show up in Videos" - (and for breeze: why do I find some of my series only in videos): The concept behind this behavior is that MP2 thinks in "MediaAspects". There is a "MovieAspect", a "SeriesAspect", a VideoAspect, a MusicAspect, etc. Every MediaItem has one or more of these "Aspects". Every "Aspect" holds one or more so called "Attributes". An attribute of the MusicAspect e.g. is the "Artist", an attribute of the VideoAspect is the "VideoBitrate". Now, historically, there was only the VideoAspect (besides the PicturesAspect and the MusicAspect). Furthermore there was only the Video section in MP2 Client. So all your Movies, Series and anything else that was a Video was only shown in the Video section of MP2 Client. Then Morpheus came along and thought, there is something missing. We need something like Moving Pictures and TVSeries in MP2. And so he added the MoviesAspect and the SeriesAspect together with the respective front ends in MP2 Client. But he did not do so as it would be in MP1 - by writing a completely separate plugin. In the MP2 architecture this wouldn't make sense. Every movie IS at the same time a video - the same is true for series. And we already import all the information like "VideoBitrate" we also need for movies and series. What he did is that he added the MoviesAspect and the SeriesAspect additionally to the VideoAspect and only included additional Attributes specific for Movies and Series (such as the IMDB ID for Movies or the "Season" for series). The result was that the Movies section in MP2 Client only shows "videos" having a MovieAspect - the Series section only shows "videos" having a SeriesAspect. But still every movie and every series has a video aspect - which is why they are (still) all shown in the VideoSection. And as to your problem, breese, Lehmden is completely right. Apparently the VideoMetadataExtractor has found information for one of your series and therefore added a VideoAspect with that information. This is why it shows up in the video section of MP2 client. But the "SeriesMetadataExtractor" could not find information for that series and therefore no SeriesAspect was added. This is the reason why this series does not show up in the series section of MP2 client. Finally: How does MP2 decide which Apsect to add to a MediaItem. This is a decision that mainly the user makes when adding the Share. If you add a share, you have to choose a media category. If you choose "Music", MP2 will ask the MusicMetadataExtractor to find metadata for all the MediaItems in this Share and if the MedatadaExtractor is able to find information, he will add a MusicAspect with that information to the respective MediaItem. If you choose "Videos" as media category, MP2 will ask the VideoMetadataExtractor to gather information on the MediaItems and - if successful - will add a VideoAspect. If you choose "Movies" (or Series) when adding your Share, you will notice that at the same time "Videos" is also checked. This is the result of Movies and Series being a "subtype" of Videos. And this means that MP2 will first ask the VideoMetadataExtractor to find information on the MediaItems in the Share and then also ask the MoviesMetadataExtractor to find additional information specific for Movies. As a result, if the VideoMetadataExtractor was successful, the MediaItem will have a VideoAspect, if the MovieMetadataExtractor was also successful, there will also be a MovieAspect. Now to all the requests in this thread: [LIST] [*]As mentioned above, the fact that all Movies and Series are also shown in Videos is a leftover from MP2's history. It is surely not too difficult to tell the frontend only to display videos in the video section that do not have a MovieAspect or a SeriesAspect. [*]Everything related to "how is it displayed in the frontend" I have to pass to Morpheus. He did a great job there in the past and he constantly tries to improve the user experience by adding new features. But please bear in mind: The MP2 development team only consists of very few people. Morph is more or less the only dev who currently works on front end improvements. We have just made TVE3.5 work with SQLite which makes it possible for many more people to try "native MP2 tv". As a result there were many requests on how to improve the TV frontend of MP2. And Morph immediately started to implement as many requests as possible - including a new EPG view, etc. Due to the lack of manpower, this all takes some time - but I am sure, he will not refuse to add some goodies to the Movies or Series sections when he has finished the improvements for SlimTV client... [*]All the rest (such as how and what metadata is scraped for what files in what languages, how can this be amended to one's personal needs, etc.) is completely unrelated to the movies or series section in the MP2 Client (unlike in MP1). This is dealt with in the MetadataExtractors and the Importer. And what I can tell you here is that we know that there is still a lot to do. But instead of providing "workarounds" to make feature a or b working, I have decided that we have to change the original concept a bit to have more flexibility. As a result, I will try to write a completely new Importer. This is necessary as we have many requests that the import as such takes too long. The new importer will be able to do a "two pass import", i.e. first only importing the absolutely essential information (in a quick first pass after which you can already find all your movies in the MP2 client - but maybe not yet all the eyecandy such as backdrops, etc.) and in a second pass, which may take longer, all the additional information that takes a lot of time to get (in most cases downloads from the internet). At the same time, I will make sure that the new Importer is able to handle things like "two files (CD1 / CD2) for one movie" or providing the possibility for user interaction during the import (e.g. if TMDB returns two possible matches for a movie, we need the user to choose which of those two is the right one), etc. In the course of this rewrite it may be possible that I also overhaul the current MetadataExtractors - and maybe I will also integrate the scripting engine of Moving Pictures to make it easier for non-devs to extend our scrapers (i.e. MetatadaExtractors). But for these latter things we still need to discuss a lot of things to make sure that we cover every possible use case. [/LIST] After all, the devs definitely read all the posts here in the MP2 forum. And we really appreciate all the feedback we get. We also try to implement as many requests as we can. But please bear with us: We are really only very few people and we all have a real life :D So it is not possible for us to answer every user post as extensively as this one. As you can see from breese's post, we are not even able to answer all the posts of our testers (sorry for that breese, I had a lot to do in my job lately, but I really read every one of your posts and I'm trying to solve all the bugs you spot and to implement all your suggestions to the extent possible for me - your work is really very much appreciated...) So what can I say: Please keep on testing MP2 and we try to improve it as good as we can. And please post bugs you find and improvements you would like. We DO appreciate it - we just cannot promise to follow up in a few days... Michael [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
Moving Pictures MP2
Contact us
RSS
Top
Bottom