Differences

This shows you the differences between two versions of the page.

--- projects:kevin [2020/12/25 15:34] – derpeter
+++ projects:kevin [2020/12/25 15:39] (current) – [Data entry] derchris
@@ Line 2: / Line 2: @@
 ---- dataentry project ----
-name                : kevin #
+name                : kevin
-project-owner       : derchris #
+project-owner       : derchris
-git-url_url         : http://@@git url@@ #
+git-url_url         : https://github.com/voc/kevin/
-project-description : Killer Experimental Video Internet Noise, KEVIN #
+project-description : Killer Experimental Video Internet Noise, KEVIN
-project-member      :  #
+project-member      :
-project-status_     : development #
+project-status_     : development
 ----
 * https://kevin.c3voc.de
-## Components
+== what already works
-## what already works
 * Webcam share + Audio
@@ Line 24: / Line 22: @@
 * Local recording
-## what we need help with
+== what we need help with
 * General layout
-* Stabalize current feature set
+* Stabilize current feature set
 * Implement new features, like a Group chat admin
 * Server recording
-## background
+== background
 While we are quite happy with the feature set of OBS.Ninja (see obs.ninja) there is are some issues why we don't want to use it in the current state. See https://github.com/steveseguin/obsninja/issues/613
 While we are still hoping for a FOSS version of obs.ninja, derchris started an alternative implementation.
-Also we have a kind of readble deofuscates version of webrtc.js which can be the base for a foss replacement.
 We keep on providing stun / turn server. (stun:kevin.c3voc.de:3479)
@@ Line 46: / Line 42: @@
 * Help to reimplement the server part of ninja and the webrtc.js. There is channel on rocket chat to coordinate the efforts.
 * Host a obs ninja instance your self and change the stun/turn server to user ours (to not relay on the servers by the author)
-* Use the offical ninja instance.
+* Use the official ninja instance.
 In the case you use ninja at is current state make sure to inform your speakers about the potential privacy issues.
-## Features Required
+== Features Required / Wanted
- * Minimal: Pass webcam video / ScreenShare from one 'sending' browser tab to another browser, as full webpage clean feed
+those are collected in the github issue tracker. Feel free to add or implement some
- * stable streams: Streams should be as stable and high quality as possible (i.e. no sudden freezing of streams, no sudden quality drops)
- * Ease of Use: It should pe possible to prepare Links for speakers in advance, so that the speaker only needs to click on the link, and then the popup appears to select Camera and Microphone, and the speaker only has to click on start
- * Automatic reconnect on connection loss
- * **Please include the possibility to only view one video stream at a time in an OBS Browser source. (e.g. by adding the streamID as url parameter)**
-## Features Wanted
-* Audio backchannel between Director and Speakers
-* Audio backchannel between speakers
-* Low Resolution / Bitrate Video backchannel support
-* Control over Stream Quality: Resolution, Bitrate, ....
-* Serverside recording: Server acts as a recording proxy before OBS Browser Source (so no further p2p connection is needed outgoing from the speaker)
-## Crazy Ideas (for sometime in the future)
+== Crazy Ideas (for sometime in the future)
 * Possibility for guests in a room to mark them selves as ready to record. Then the director of a room can start the local recording on all speakers pc's. When the recording is finished, all (high quality) recordings are uploaded to the server, leaving a backup as download on the speakers computer. Now an remote mixing angel can work with the high quality files.
@@ Line 71: / Line 55: @@
     * also, check for privacy concerns and if it is possible at all, thats why its under the title crazy Ideas.
-## Dev Setup
+== Dev Setup
 * Install Signaling Server