-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathindex.html
103 lines (88 loc) · 5.16 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.5.0/css/bootstrap.min.css" integrity="sha384-9aIt2nRpC12Uk9gS9baDl411NQApFmC26EwAOH8WgZl5MYYxFfc+NcPb1dKGj7Sk" crossorigin="anonymous">
<title>Choirless - A musical collaboration project for disconnected performers</title>
</head>
<body>
<div class="container">
<div class="jumbotron">
<h1 class="display-4">Choirless</h1>
<p class="lead">A musical collaboration project for disconnected performers</p>
</div>
<div class="container">
<h2>Introduction</h2>
<p>
Choirless is a musical collaboration platform built to enter the
<a href="https://callforcode.org/">Call for Code 2020</a> global competition.
It allows music groups to create a video wall recording of a piece of music, where all of the
individual submissions are captured separately on the performers' phone, tablet or laptop.
</p>
<p>
The core technology that powers Choirless has been released as a Call for Code with The Linux Foundation project named
<a href="https://github.com/Rend-o-matic/Rend-o-matic">Rend-o-matic</a>.
</p>
<p>
Choirless came about during the 2020 Covid-19 Pandemic, as countries went into lockdown
and social-distancing prevented choirs, bands and other musical ensembles from meeting and
performing in person. Video meeting platforms such as Zoom and Webex proved useless for live
collaboration because of the network latency and the audio being optimised for speech.
</p>
<p>
Choirless aims to make it very easy for choir leaders to create songs made out of several parts
(e.g. alto, tenor, soprano) and to organise choir members to provide renditions of a part.
All of the contributed videos are stitched together into a video wall with no special
equipment and without employing costly and time-consuming video editing software.
</p>
<h2>Who are we?</h2>
<p>The Choirless Crew consist of three members who met at IBM:
<ul>
<li><a href="https://twitter.com/HammerToe">Matt Hamilton</a></li>
<li><a href="https://twitter.com/seanmtracey">Sean Tracey</a></li>
<li><a href="https://twitter.com/glynn_bird">Glynn Bird</a></li>
</ul>
</p>
<h2>How does it work?</h2>
Choirless consists of a number of microservices working together:
<img class="img-responsive" src="assets/img/schematic.png" />
<h3>Choirless components</h3>
<ol>
<li><a href="https://github.com/Choirless/Application-Server">The Application Server</a> powers the
Choirless front-end website. It is built with HTML and vanilla JavaScript and is deployed using
Cloud Foundry in the IBM Cloud</li>
<li><a href="https://github.com/Choirless/choirlessapi">The Choirless API</a> is a RESTful API service
written in Node.js which stores its state in a Cloudant JSON document store.</li>
</ol>
<h3>Rend-o-matic components</h3>
<ol>
<li><a href="https://github.com/Rend-o-matic/renderer">The Renderer</a> is a collection of Python
and Node.js serverless actions that run in the IBM Cloud Functions framework. They are triggered
by objects arriving in Cloud Object Storage and from user-driven events. Each action performs a
specific audio/video processing job, such as resizing video or creating montages of multiple
video sources.</li>
<li><a href="https://github.com/Rend-o-matic/boxjam">Boxjam</a> is a Node.js module that fits
many rectangles into another rectangle - useful if you're creating video montages of videos
that are of various sizes and orientations.</li>
<li><a href="https://github.com/Rend-o-matic/Stitcheroo">Stitcheroo</a> is a Node.js module that fits
many combines multiple videos sources into an output montage. It can also process the
audio tracks for stereo spread and reverberation ambience.</li>
</ol>
<h2>The Rendering Process</h2>
The Rendering service is a multi-step process, where each step is triggered by the arrival of an
object in a COS bucket. Some actions are taken in parallel to speed up the process:
<img class="img-responsive" src="assets/img/renderer.png" />
<h2>How can I try it?</h2>
Simpy visit <a href="https://www.choirless.com">Choirless.com</a> and sign up for an account. Or, check
out the <a href="https://github.com/Rend-o-matic">Rend-o-matic GitHub organisation</a> to explore the
underlying engine that powers Choirless.
<h2>Open source</h2>
All of our source code is <a href="https://github.com/Choirless">open-sourced under the MIT
license on GitHub</a>.
<hr>
© Choirless 2020-2021
</div>
</div>
</body>
</html>