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!)
AutoCropper plugin
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="ziphnor" data-source="post: 70316" data-attributes="member: 14215"><p>That might be the case, it would be nice to process entire lines instead. If a binary search style approach can be used, i am sure it will be possible to take whole lines.</p><p></p><p></p><p></p><p>Its pretty simple to see when the approach fails as it will almost always find a way too small bounding box. When that happens i think as you say that its a good idea to just stick with the last detected format.</p><p></p><p></p><p></p><p>I am thinking that it will start by showing the whole image until it strikes a frame that can be used. After that it would sample once in a while and if discovering a larger box immediatly change it, but be more reluctant to decrease the bounding box(to avoid it jumping up and down due to subtitles). On the other hand this might lead to a delay in reducing the format again when coming out of commercials. </p><p></p><p>I think that there definetly should be a mode where the user hits a key to autodetect the format each time it needs to change. That can be made very reliable. We can then provide a full auto mode where we use the above ideas. I think its important to do it this way, because the full auto mode will probably be a bit experimental for a looong time, while the hit-key-to-autodetect can be reliable implemented in the short-term.</p><p></p><p>After all this will mostly be used in movies, so you just hit autodetect when the movie begins and leave it. THis will crop some commercials, but who cares <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="ziphnor, post: 70316, member: 14215"] That might be the case, it would be nice to process entire lines instead. If a binary search style approach can be used, i am sure it will be possible to take whole lines. Its pretty simple to see when the approach fails as it will almost always find a way too small bounding box. When that happens i think as you say that its a good idea to just stick with the last detected format. I am thinking that it will start by showing the whole image until it strikes a frame that can be used. After that it would sample once in a while and if discovering a larger box immediatly change it, but be more reluctant to decrease the bounding box(to avoid it jumping up and down due to subtitles). On the other hand this might lead to a delay in reducing the format again when coming out of commercials. I think that there definetly should be a mode where the user hits a key to autodetect the format each time it needs to change. That can be made very reliable. We can then provide a full auto mode where we use the above ideas. I think its important to do it this way, because the full auto mode will probably be a bit experimental for a looong time, while the hit-key-to-autodetect can be reliable implemented in the short-term. After all this will mostly be used in movies, so you just hit autodetect when the movie begins and leave it. THis will crop some commercials, but who cares :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
AutoCropper plugin
Contact us
RSS
Top
Bottom