Reply to thread

Message

<blockquote data-quote="jawbroken" data-source="post: 70711" data-attributes="member: 14372">I finally got onto this today (I have been working hard at work and university because I am going travelling in Europe at the end of the year and need the money).I have coded up a generic framework for testing and benchmarking. It should be clear how to use it from the Main method. The main methods that need to be filled in are the isInterestingRow and isInterestingColumn functions. I have coded up the routines to do the binary search for the edges. The binary search currently looks between the edge of the frame and 25% in, this can be made configurable or changed if required. From my tests with 4:3 in 16:9 and 16:9 in 4:3 mockups I created, this 25% should be sufficient.I have coded in very simplistic isInterestingRow and isInterestingColumn methods, they work fine for normal frames but from what I can see your variance method works a lot better. They won't pick up subtitles, etc but will ignore logos. If I have time I will plug in your variance code tonight.With my simplistic testing (which is also not very efficient), I am getting promising time results. For example:Starting Benchmark:Results:10 frames processedTook 30.0432 msAverage of 3.00432 ms per frameThat equates to 332.854023539437 fpsThis is running on my old Mobile P4 1.7Ghz with 224MB of RAM.So this routine could probably be run every 4 frames or so with negligible CPU impact.Edit: I have emailed the framework to you.</blockquote>

[QUOTE="jawbroken, post: 70711, member: 14372"] I finally got onto this today (I have been working hard at work and university because I am going travelling in Europe at the end of the year and need the money). I have coded up a generic framework for testing and benchmarking. It should be clear how to use it from the Main method. The main methods that need to be filled in are the isInterestingRow and isInterestingColumn functions. I have coded up the routines to do the binary search for the edges. The binary search currently looks between the edge of the frame and 25% in, this can be made configurable or changed if required. From my tests with 4:3 in 16:9 and 16:9 in 4:3 mockups I created, this 25% should be sufficient. I have coded in very simplistic isInterestingRow and isInterestingColumn methods, they work fine for normal frames but from what I can see your variance method works a lot better. They won't pick up subtitles, etc but will ignore logos. If I have time I will plug in your variance code tonight. With my simplistic testing (which is also not very efficient), I am getting promising time results. For example: Starting Benchmark: Results: 10 frames processed Took 30.0432 ms Average of 3.00432 ms per frame That equates to 332.854023539437 fps This is running on my old Mobile P4 1.7Ghz with 224MB of RAM. So this routine could probably be run every 4 frames or so with negligible CPU impact. Edit: I have emailed the framework to you. [/QUOTE]

Verification