---

Please note: This is not a standard bug hunt contest, we are interested in both your ideas and corrections to the contest specs given in the details below.  This is a complex, research related project so any bug tickets created that add value to re-drafting the contest specs will receive credit.  The term bug ticket covers ideas, suggestions or anything else you think is helpful or appropriate to the contest tracks to generate a successful outcome.

---

1. Project Overview

The aim of this project is to develop a software module for reducing the frame rate of a live video stream coming from a CCTV IP camera. We need to reduce the frame rate of live video streams from the CCTV IP camera in an effective way.  Not just simply decoding, removing a frame and re-encoding the stream, but rather transcoding on the fly.

We have completed some research and like the approach presented in the following two papers:

(1. New Architecture for Dynamic Frame-Skipping Transcoder, 2. Efficient Mode Decision for H.264/AVC Frameskipping transcoding)

https://docs.google.com/folder/d/0B0rMmRXYjUuKdWZyT1RBZGdBTHM/edit 

We are currently looking for feedback (both technical and general guidance on the specs) to support launching a successful contest or series of contests to develop a working solution based on these papers or any other related solution that helps fulfil our needs. 

1.1 Contest Task Overview

Here are the original contests that we have launched without success so far;

Full requirements and architecture spec here: http://apps.topcoder.com/wiki/display/docs/FrameSkipper+Module+Architecture

Proof of Concept proposed assembly here: http://apps.topcoder.com/wiki/display/docs/FrameSkipper+POC+Assembly

In this community bug-hunt/spec review/idea contest, we'd like to hear your ideas about these contests in general and covering these specifics;

• If you believe the contest tracks being chosen are correct (and why or if not why not)
• If you can provide sample code snippets (pseudocode is also ok) demonstrating any implementation paths
• Any prior knowledge suggesting some detailed algorithms or existing open source libraries that could be used etc.

The major purpose is we want to see if we can combine the feedback provided here to help us reach a more successful outcome on this track of contests.

1.2 Submit Your Ideas

You should submit your ideas/proposals as bug tickets to this JIRA project: https://apps.topcoder.com/bugs/browse/FSBH

The JIRA ticket should include the details about each idea or suggestion. Technically where appropriate you should mention the target codec (H.264? mpeg-4?), you should also mention the codec profile (you can find the full list in the architecture contest wiki). The recommended test video is nice-to-have. That's great if you already complete the test code and show the output video to us. (You are not required to provide full source code in this phase).

If you see problems with the proposed contest specs above, or have ways you would suggest to modify them please detail where and how. There will be no credit for the same issue being called out on both existing specs - if the direct issue is already mentioned from one spec, credit will essentially be given to that ticket for the issue where it exists in both.

All of your feedback - from whether or not you think it's a viable contest track to run and obtain a solution to actual technical details - is valuable to us.

Credit for JIRA bug tickets will be given to any that provide information not present in the spec that we determine is directly applicable to the project and will help going forward. Complete ideas must be present in a single ticket. The client/PM will have final say in which bug tickets are judged to provide useful information that will modify the spec going forward and discussion is encouraged and we will respond to all tickets presented.

Please also submit a placeholder submission to Online Review otherwise we can't process any payments to you - if you're unsure of how to accomplish this please ask iRabbit through the contest forum.

1.3 Technology Overview

• OS (compatible with both windows7 32bit and 64bit)
• VisualStudio 2010 C++ (C++11 compatible)
• STL
• boost(1.49 or higher)
• additional native library can be used - please suggest as appropriate

1.4 Payments

We will select any and all bug tickets/ideas presented as we deem they are appropriate. 

Final Submission Guidelines

 For scoring, the submitter with the most accepted bug tickets will win. The submitter with the second most accepted bug tickets will receive second place. For submitters who submit but don't take first or second, if they submit bug tickets that aren't covered in the first or second place submission and that do end up being used, they will receive $10 for each unique bug ticket reported up to a maximum of the 2nd place prize. If two submitters submit the same bug ticket, the submitter who submitted the report first into JIRA will get credit for that idea or issue.