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
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Trailer and MovingPictures
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="dir" data-source="post: 750043" data-attributes="member: 24485"><p>Hi,</p><p>I've read the trailers feature request threads in the wiki and it's not just the most frequently requested feature, but it's one of the oldest. </p><p>It appears that the developers are stuck in a perception that to do local trailers right, it will require a complex architecture and a lot of effort.</p><p>While this might be true, I think this mind-set has resulted in killing a local trailer feature despite it being extremely sought after.</p><p></p><p>There are incredibly simple solutions available to bring local trailer suppport to MovingPictures, but the developers maintain the position that it needs to be done right and will be very complex.</p><p></p><p>There's nothing wrong with providing a very simple, quick and limited capability that would suffice and appease most people. You could clearly explain that there is no support, it's not an invitation for a flood of enhancement requests, etc. and that any future development may completely change the solution (so that developers don't feel locked in to bad early design decisions).</p><p></p><p>The simple solution is this:</p><p>Look for <moviename> - trailer.* in the same directory as the movie. If it's there, then play that instead of jumping to OnlineVideos. In PHP coding terms, this is about 4 lines.</p><p></p><p>Many people are more than happy to conform to this limitation. Those limitations would be:</p><p>- no ability to specify size (e.g. 720p vs. 640 etc.)</p><p>- no ability to specify language</p><p>- no ability to use alternative filenaming conventions</p><p>- no ability to locate trailer in alternative file location</p><p>- the <moviename> part must be the exact same as the movie's filename (or first part of a multi-part), in the same way that subtitle files must be the same</p><p>- no facility to actually download the trailer (although OnlineVideos does this for current movies already)</p><p>- no indexing, no entries in the database, no enhanced functionality apart from simply playing it if it's there.</p><p></p><p>It's really that simple and would take minimal effort to introduce.</p><p></p><p>Sure, it doesn't cater for a million different scenarios, but at least after 2 or more years of waiting, we'd all finally be able to link our trailers to our movies. I know several people with hundreds of trailers they've amassed over the years, because sites like Apple and IMDB may not retain them or source them.</p><p></p><p>The current capability to stream the video is fine for those people in countries and with ISPs that provide fast and cheap connections, but the rest of the world doesn't want to continuously download and wait for trailers to stream. And streaming usually is erratic and choppy. Eventually people stop using the facility because it's just too frustrating to watch streaming trailers. (Yes, I'm aware you can specify stream caching sizes but that misses the main point).</p><p></p><p>I can't really understand why, after several years, this functionality continues to be voted down by developers as a low priority when it's one of the most sought-after features. Evolution should not be halted because of the idealistic need for perfect solutions. Sometimes adopting an "It'll do for now" approach will suffice.</p></blockquote><p></p>
[QUOTE="dir, post: 750043, member: 24485"] Hi, I've read the trailers feature request threads in the wiki and it's not just the most frequently requested feature, but it's one of the oldest. It appears that the developers are stuck in a perception that to do local trailers right, it will require a complex architecture and a lot of effort. While this might be true, I think this mind-set has resulted in killing a local trailer feature despite it being extremely sought after. There are incredibly simple solutions available to bring local trailer suppport to MovingPictures, but the developers maintain the position that it needs to be done right and will be very complex. There's nothing wrong with providing a very simple, quick and limited capability that would suffice and appease most people. You could clearly explain that there is no support, it's not an invitation for a flood of enhancement requests, etc. and that any future development may completely change the solution (so that developers don't feel locked in to bad early design decisions). The simple solution is this: Look for <moviename> - trailer.* in the same directory as the movie. If it's there, then play that instead of jumping to OnlineVideos. In PHP coding terms, this is about 4 lines. Many people are more than happy to conform to this limitation. Those limitations would be: - no ability to specify size (e.g. 720p vs. 640 etc.) - no ability to specify language - no ability to use alternative filenaming conventions - no ability to locate trailer in alternative file location - the <moviename> part must be the exact same as the movie's filename (or first part of a multi-part), in the same way that subtitle files must be the same - no facility to actually download the trailer (although OnlineVideos does this for current movies already) - no indexing, no entries in the database, no enhanced functionality apart from simply playing it if it's there. It's really that simple and would take minimal effort to introduce. Sure, it doesn't cater for a million different scenarios, but at least after 2 or more years of waiting, we'd all finally be able to link our trailers to our movies. I know several people with hundreds of trailers they've amassed over the years, because sites like Apple and IMDB may not retain them or source them. The current capability to stream the video is fine for those people in countries and with ISPs that provide fast and cheap connections, but the rest of the world doesn't want to continuously download and wait for trailers to stream. And streaming usually is erratic and choppy. Eventually people stop using the facility because it's just too frustrating to watch streaming trailers. (Yes, I'm aware you can specify stream caching sizes but that misses the main point). I can't really understand why, after several years, this functionality continues to be voted down by developers as a low priority when it's one of the most sought-after features. Evolution should not be halted because of the idealistic need for perfect solutions. Sometimes adopting an "It'll do for now" approach will suffice. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Trailer and MovingPictures
Contact us
RSS
Top
Bottom