Changes between Initial Version and Version 3 of Ticket #236

Show
Ignore:
Timestamp:
01/28/10 22:37:20 (15 years ago)
Author:
brent
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #236

    • Property component changed from unknown / unassigned to standard platform
    • Property severity changed from New / Just Added to Evaluating
    • Property summary changed from Video Platform: player Integration to Video Platform: Player Integration
  • Ticket #236 – description

    initial v3  
    44 
    55need to support no ads and no ugc parameters 
     6Requirements for Video Player 
    67 
    7 [more details to come soon] 
     8 1 The player is intended to stream videos on the internet both on our site and embedded on other sites. 
     9 2 We will use a modified open source player (Flow Player or JW Player) 
     10 3 The player should integrate with: 
     11 3.1 CMS 
     12 3.2 FreeWheel (video ad platform) 
     13 3.3 Highwinds (CDN) 
     14 4 Features 
     15 4.1 Look and feel should closely mirror current blip player 
     16 4.2 Volume control 
     17 4.3 Button for Fullscreen 
     18 4.4 Embed button (displays embed code for users to embed video) http://www.longtailvideo.com/addons/plugins/49/Embed?q= 
     19 4.5 Video timeline with countdown and seek option 
     20 4.6 play/pause button 
     21 4.7 Multibit Streaming. We should detect a users connection and serve the best file based on their capabilities 
     22 4.8 18+ Registration.  For videos labelled 18+ the viewer should be prompted to register prior to viewing. 
     23 4.9 Related videos... Need to show related videos when a video is paused or at the end of the clip. http://www.longtailvideo.com/addons/plugins/54/D-Related?q= 
     24 4.10 When a pre, mid, or post roll ad is showing the timeline/seek control should be disabled and there should be a countdown.  
     25 4.11 Google Analytics plugin http://www.longtailvideo.com/addons/plugins/107/Google-Analytics-Pro?q=%20alt= 
     26 5 Distribution 
     27 5.1 To support distribution the most important requirement is that we figure out some method to serve companion banners.  Primarily these will be 300x250 in size but it seems likely that other sizes may bee needed in the future. Ideally it would be great if the companion grows from the player and sits on top of the page for the duration of the video. It would be ideal if the partner could select which side the ad appears. 
     28 5.2 Every button on the player should be able to show or not show for each partner 
     29 5.3 Color... it would be great if we could allow the partner to select a hex color for the player. 
     30 5.4 In some cases we may be able to overlay an existing 300x250 ad on the page for our companion banner. In that case we may need to give them some code to place on the page to support this... unless can can think of a better way.