|
Size: 6994
Comment: Tekst for studentoppgaver.
|
Size: 7028
Comment: Spell check.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| internet. TV has always been sort of «analoge» , and one way comunication. There is always a editor that will decide the content of the channle, and the viewers have never beed able to participate, or |
Internet. TV has always been sort of «analog» , and one way communication. There is always a editor that will decide the content of the channel, and the viewers have never been able to participate, or |
| Line 10: | Line 10: |
| shuldnt they be able to publish their content on the TV - medium. | should they not be able to publish their content on the TV - medium. |
| Line 12: | Line 12: |
| Rigth now there are few solutions, and those that exists are properiatory, and based on expencive hardware.... |
Right now there are few solutions, and those that exists are proprietary, and based on expensive hardware.... |
| Line 22: | Line 22: |
| SAN devices over fiber channel. | SAN devices over fibre channel. |
| Line 28: | Line 28: |
| easy transcoding, and meta data veryfing to the sched uler. this is for easy file acsess to files from other systems. |
easy transcoding, and meta data verifying to the scheduler. this is for easy file access to files from other systems. |
| Line 31: | Line 31: |
| This system is already created, as well as its sentral database. | This system is already created, as well as its central database. |
| Line 33: | Line 33: |
| All the comunication will be documented in the servers API. | All the communication will be documented in the servers API. |
| Line 37: | Line 37: |
| This is a system that generaters a playlist, from a web based user interface This platform has a standalone database and is "controller" |
This is a system that generates a play list, from a web based user interface This platform has a stand alone database and is "controller" |
| Line 40: | Line 40: |
| registration, and playlist configurator. | registration, and play list configurator. |
| Line 44: | Line 44: |
| Acsess the web site, and registrer a video. Upload the video to backend from this site, and publish the content to the monthely |
Access the web site, and register a video. Upload the video to backend from this site, and publish the content to the monthly |
| Line 47: | Line 47: |
| formats online for viewing purpeses, as a comunity channel | formats online for viewing purposes, as a community channel |
| Line 51: | Line 51: |
| Transocding solution needs to get "what ever format" from Backend, for trasncoding to Broadcast, web and open standard formats. Hopefully it |
Transcoding solution needs to get "what ever format" from Backend, for transcoding to Broadcast, web and open standard formats. Hopefully it |
| Line 60: | Line 60: |
| new computer on the network presents itself to the trascoder as a | new computer on the network presents itself to the transcoder as a |
| Line 65: | Line 65: |
| The player is the final output of the system, totaly controled by the schedluresystem, that tells what to play when. The player should aslo |
The player is the final output of the system, totally controlled by the scheduler system, that tells what to play when. The player should also |
| Line 71: | Line 71: |
| Gets playlist and time from Scheduler and copyes the files from backend for direct playout. If the sceduled item is a live source, the |
Gets play list and time from Scheduler and copies the files from backend for direct playout. If the scheduled item is a live source, the |
| Line 77: | Line 77: |
| Today we have all of theese modules working, the company Never.no created it, based on microsoft thecnology. |
Today we have all of these modules working, the company Never.no created it, based on Microsoft technology. |
| Line 85: | Line 85: |
| thecnology. This is where you have the video database, that connects | technology. This is where you have the video database, that connects |
| Line 91: | Line 91: |
| that is quite slow and not optimized for parallell processing. | that is quite slow and not optimised for parallel processing. |
| Line 96: | Line 96: |
| Since we have a fully operational background services, then we dont | Since we have a fully operational background services, then we don't |
| Line 98: | Line 98: |
| internett to be included into this «party» and that´s why we creating | Internet to be included into this «party» and that´s why we creating |
| Line 103: | Line 103: |
| Silverlight thecnology, it will also replace the playout unit with a | Silverlight technology, it will also replace the playout unit with a |
| Line 106: | Line 106: |
| The system needs also to be standalone units, for integration with | The system needs also to be stand alone units, for integration with |
| Line 108: | Line 108: |
| systems can comunicate, | systems can communicate, |
| Line 112: | Line 112: |
| The playout module is our first priority. The idéa is to lissen on the | The playout module is our first priority. The idéa is to listen on the |
| Line 114: | Line 114: |
| time from the sceduler. When there are none videos to be played. We | time from the scheduler. When there are none videos to be played. We |
| Line 120: | Line 120: |
| * basic knowlage of VLC, or a player with similar capebilitys * reverse enginering existing scheduler system, for getting the playlist |
* basic knowledge of VLC, or a player with similar capabillites * reverse engineering existing scheduler system, for getting the play list |
| Line 123: | Line 123: |
| * general codec knowlage | * general codec knowledge |
| Line 125: | Line 125: |
| its preffered with Some openGL / openCL skills is also good to know to comunucate with the Video play out card. |
its preferred with Some OpenGL / OpenCL skills is also good to know to communicate with the Video play out card. |
| Line 130: | Line 130: |
| This system is the main controll system, witch connects the Player | This system is the main control system, witch connects the Player |
| Line 132: | Line 132: |
| «standalone» with the posibility to talk to all systems, even the | «stand alone» with the possibility to talk to all systems, even the |
| Line 135: | Line 135: |
| This system needs acsess to the all ready existing Backend system and Scedule system, it needs to be a «clone» of the existing system. but with the posibillytis to also work as a standalone system |
This system needs access to the all ready existing Backend system and Schedule system, it needs to be a «clone» of the existing system. but with the possibilities to also work as a stand alone system |
| Line 139: | Line 139: |
| First off, today this is a «Slave» sceduler for the Silverlight | First off, today this is a «Slave» scheduler for the Silverlight |
| Line 142: | Line 142: |
| Then, aftter the scheduler can be a slave to the master scheduler, the | Then, after the scheduler can be a slave to the master scheduler, the |
| Line 144: | Line 144: |
| posibilytis, to backend, and controll of the transcoding system. | possibilities, to backend, and control of the transcoding system. |
| Line 150: | Line 150: |
| * Basic video knowlage / VLC / Transcoding | * Basic video knowledge / VLC / Transcoding |
| Line 154: | Line 154: |
| To get «Whatever filetype» to known formats, as .dv for the playout system, Ogg Theora for the web system, and the posibilyty for other |
To get «Whatever file type» to known formats, as .dv for the playout system, Ogg Theora for the web system, and the possibility for other |
| Line 158: | Line 158: |
| There are a lot of open encoders out there, you have te FFMPEG | There are a lot of open encoders out there, you have the FFMPEG |
| Line 160: | Line 160: |
| menton VLC. | mention VLC. |
| Line 167: | Line 167: |
| transcodes it to various formats as spessyfied in the sheduler system. | transcodes it to various formats as specified in the scheduler system. |
| Line 169: | Line 169: |
| If posible, the transcoder system shuld be able to swap feeld orders, | If possible, the transcoder system should be able to swap field orders, |
| Line 175: | Line 175: |
| * Codec knowlage * Transcoding knowlage * Video knowlage * Pearl , Mysql and PHP * Network and TCP/UDP knowlage |
* Codec knowledge * Transcoding knowledge * Video knowledge * Pearl , MySQL and PHP * Network and TCP/UDP knowledge |
Welcome to this projects PDF file.
This project is hoping to unite traditional TV-medium with the Internet. TV has always been sort of «analog» , and one way communication. There is always a editor that will decide the content of the channel, and the viewers have never been able to participate, or contribute to the actual broadcasts. Today we have editing programs on a PC, and we can record, edit and publish right out of the box. Since all people can record edit and publish on the web, then why should they not be able to publish their content on the TV - medium.
Right now there are few solutions, and those that exists are proprietary, and based on expensive hardware....
So how about a computer with a SDI card, and VLC....
Module based
Backend
This is where all the media is stored, it's a computer with multiply SAN devices over fibre channel.
When a person is uploading a video, it can be uploaded direct to this server.
The File server then has a watchfolder to the transcoder solution for easy transcoding, and meta data verifying to the scheduler. this is for easy file access to files from other systems.
This system is already created, as well as its central database.
All the communication will be documented in the servers API.
Sceduler
This is a system that generates a play list, from a web based user interface This platform has a stand alone database and is "controller" for the open playout system. It has a web based interface for video registration, and play list configurator.
"system flow"
Access the web site, and register a video. Upload the video to backend from this site, and publish the content to the monthly scheduler for playout. you can then also access the video in various formats online for viewing purposes, as a community channel
Transcoder
Transcoding solution needs to get "what ever format" from Backend, for transcoding to Broadcast, web and open standard formats. Hopefully it can also be network based, so you can connect new modules to accelerate transcoding
"flow"
The system gets a file in a folder, takes the file and transcodes, renames and moves it according to the scheduler database system. if a new computer on the network presents itself to the transcoder as a module, it will add it to the system for accelerated transcoding.
Player
The player is the final output of the system, totally controlled by the scheduler system, that tells what to play when. The player should also be able to pass trough live rtsp/http streams for Live broadcasting.
"player"
Gets play list and time from Scheduler and copies the files from backend for direct playout. If the scheduled item is a live source, the feed will be played as a normal item.
Page 4
Today we have all of these modules working, the company Never.no created it, based on Microsoft technology.
The backend is a full windows 2003 server with a tape robot attached, it also has a uploading system on it called Fileflow. The systems API is based on SOAP witch connects to a Microsoft SQL database.
The Scheduler, and admin interface is based on Microsoft Silverlight technology. This is where you have the video database, that connects to the scheduler and you can add content to the scheduler ,
The transcoding system for broadcast is based on Adobe Aftereffects (including format conversion). We also use Microsoft Expression Encoder 3 for transcoding to web formats. Both are single unit system that is quite slow and not optimised for parallel processing.
The playout system is based on a Harris video playout with a CGI module attached.
Since we have a fully operational background services, then we don't need to change it, says some... We want all users of the big Internet to be included into this «party» and that´s why we creating this project.
The project will be creation of 3 modules that can be attached to this system, talking to this system over the SOAP API, and be a «none» Silverlight technology, it will also replace the playout unit with a standard PC / MAC with a SDI computer card.
The system needs also to be stand alone units, for integration with other systems, so use open formats, talk over open formats then all systems can communicate,
Project one - playout
The playout module is our first priority. The idéa is to listen on the commands from the scheduler, and play out the videoes at the correct time from the scheduler. When there are none videos to be played. We want «show info» to be shown on the channel, creating a «Whats next» type of poster, with a animated background.
Qualifications:
- basic knowledge of VLC, or a player with similar capabillites
- reverse engineering existing scheduler system, for getting the play list
- Image magic
- general codec knowledge
its preferred with Some OpenGL / OpenCL skills is also good to know to communicate with the Video play out card.
Project two - scheduler
This system is the main control system, witch connects the Player with the videos, and the Database. it´s design need to be «stand alone» with the possibility to talk to all systems, even the expensive Harris Video server.
This system needs access to the all ready existing Backend system and Schedule system, it needs to be a «clone» of the existing system. but with the possibilities to also work as a stand alone system
First off, today this is a «Slave» scheduler for the Silverlight scheduler, where you,get the information on what to play from.
Then, after the scheduler can be a slave to the master scheduler, the project moves on to be a stand alone scheduler, with upload possibilities, to backend, and control of the transcoding system.
Qualifications:
- Ajax and general web programing, XML, PHP
- Mysql programing, as a main database
- Basic video knowledge / VLC / Transcoding
Project three - transcoder
To get «Whatever file type» to known formats, as .dv for the playout system, Ogg Theora for the web system, and the possibility for other formats, as MP4, X264, MPEG 2...
There are a lot of open encoders out there, you have the FFMPEG project, witch a lot is based on, you have Handbrake, and not to mention VLC.
This project aims to get a working transcoder to talk to the Scheduler system, and the Backend system.
When a user uploads the file, the Scheduler database system tells the transcoder, «now the file is ready» the transcoder takes the file and transcodes it to various formats as specified in the scheduler system.
If possible, the transcoder system should be able to swap field orders, normalise the sound volume, check 4*3 VS 16*9, also multiply computers rendering farm.
Qualifications:
- Codec knowledge
- Transcoding knowledge
- Video knowledge
- Pearl , MySQL and PHP
- Network and TCP/UDP knowledge