Random Ideas

From Transmission
Jump to: navigation, search

Random Ideas

These ones are just ideas for which no working group was proposed or any substantial work done, but came up during the discussions and some people found them inspiring. You are free to propose a working group on any of them, or just implement them separately. "Ideas are made to be copied. I have enough ideas to sell them on. I prefer that they are stolen so that i don't have to actually use them myself." (Salvador Dalí)


Lack of criticism

The activist movie distribution infrastructure lack its critiques, film critics and websites which publish criticism of films and spotlights notable works. There are many notable works in the area but the lack of focus makes them invisible in the sea of (simple but necessary and mostly effective) protest coverage. What are the best and latest titles and why? What are the upcoming trends and which tradition they continue? What is the dynamics between activist and passivist filmmaking?


Application development idea

Let's develop a P2P client which feeds off the transmission feeds which are delivering torrent files -- making the desktop comuter an automated tracker. Such an application if advanced could serve as a decentralised alternative to YouTube. (Jamie)


Involving people

Writing job descriptions to volunteers who are not creating videos: for example to watch them and describe them. 

Logging Crew: A clean simple interface dedicated to mass participation in logging incoming footage (for example, during mobilizations.) As people come in from the street they upload lots of raw footage but only about 10% of it is the good stuff. Provide simple web tool for people to watch, log, and tag the raw footage. Make it easy to set in and out points, tag footage (ex. 'select,' 'police brutality,' 'legal,' 'interview,' etc.), and maybe rate footage.

Upload forms: People need information about why they should fill in the upload form before we present them the form. Also: If we read as much data as possible from the file itself and fill half of the form with it, then users are more motivated to add more data.

Think about adding metadata at the desktop level, through common video applications?


Online transcoding service

The idea of an online transcoding service popped up a lot of times as thing that would really make our life easier. The automated service would be used by a number of online activist video sites that do not manage to run a transcoder on their server for technical or financial reasons. Furthermore, it would be much easier to point users to a simple online transcoding service that is available as a Web 2.0 service for all operating systems on all Internet-faring computers than to write documentation for all common video editing programs. To summarise, the potential and the need is still there, but implementation is lacking.

This could be widely used beyond activist circles too. (Frankly, a simple web app to do this could also generate lotsa google ad revenue for the revolution ;) since so many people would use it to transcode youtube clips.) For example, the current process to download and transcode .flv files to something editable is pretty complex for most users.

To be really useful users shouldn't have to upload the file they want to transcode; you should also be able to enter a URL (of a media file or even a stream) as input and then select output filetype, dimensions, size, from dropdowns (with a very simple default set of options and an 'advanced interface' option).

Question: where to store the resulting file? On the server that does the transcoding, or directly to user local machine?

A note on scaling an online transcoding service to many many users: once it was widely used you would face the possibility of lots of duplication of processing (multiple people wanting to transcode same file to same target filetype) so it would be useful for the service to keep track of what has been done already and point new requests for already transcoded files to the appropriate spot... (schock)


One stop upload service

Users would fill out one webform with metadata and thumbnail, then select checkboxes for which video sharing sites to upload to. Their file would be uploaded first to, say, archive.org; it would then be automatically transferred from archive.org servers to each of the video sharing sites selected by the user. This would create wider diffusion of our content and save videomakers huge amounts of time and energy uploading to multiple sites. It's a 'metaupload' service. ("VideeUp"?) (schock)


Videobomb scrape service

This would automate the process of entering videos from other video sites into the videobomb.org database. For example, I want to add all videos that have been uploaded to youtube and revver and tagged with oaxaca to videobomb, so that I can pull a single aggregated video feed. Rather than have to individually fill out the videobomb form for each youtube video, how bout automated?


Video Project Management system

This would facilitate collaborative video projects by pulling together a set of tools for each stage of production, from scripting, storyboarding, etc. through post. See notes here: https://docs.indymedia.org/view/Devel/FilmForge



Publishing subtitles with ATOM+REST

Since ATOM provides a publishing protocol, maybe we could accomodate translators who would like to provide subtitles for somebody else's published videos? The idea would be: person A publishes a video on a server with a URI, person B uses PUT to update that URI to add a subtitle metadata tag to the original post, pointing to the translated subtitile file. Since translation is best done in the target locale, decentralizing the process seems a good idea to me. A diagram illustrating this workflow is here: http://alteree.hardcore.lt/atom/atom_subtitles.gif


One Klick Transmission

Idea of creating workflow, that will provide possibility for transmitting short clips (for example 2 minutes long) from a street every 30 minutes or less. It could be realised with set of scripts to kino and linux shell, that will:

  1. apply custom transition and effect
  2. apply front title and end title to klip
  3. export from kino to raw file
  4. compress raw file into mp4 full screen klip
  5. send file to web server (optionally create + upload torrent and start to seed)
  6. Create post to cms with meta data and send it to cms website

Editor with laptop plugs into a camera on the street and capture 2 minutes of video. fast edit (few clicks) and press one button, wait 10 minutes and clip becomes ready for upload. next time, laptop will find a open wifi (or wire), will begin to upload clip to webserwer. what that will finish, clip will be automatically posted into cms. From there clients will pick it up via atom.