You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/documentation/docs/for-developers/device-integrations/tsr-plugins.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Some useful npm scripts you may wish to copy are:
27
27
28
28
There are a few key properties that your plugin must conform to, the rest of the structure and how it gets generated is up to you.
29
29
30
-
1. It must be possible to `require(...)` your plugin folder. The resuling js must contain an export of the format `export const Devices: Record<string, DeviceEntry> = {}`
30
+
1. It must be possible to `require(...)` your plugin folder. The resulting js must contain an export of the format `export const Devices: Record<string, DeviceEntry> = {}`
31
31
This is how the TSR process finds the entrypoint for your code, and allows you to define multiple device types.
32
32
33
33
2. There must be a `manifest.json` file at the root of your plugin folder. This should contain json in the form `Record<string, TSRDevicesManifestEntry>`
Copy file name to clipboardExpand all lines: packages/documentation/docs/user-guide/features/prompter.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ The prompter can be controlled by different types of controllers. The control mo
46
46
|`?mode=shuttlewebhid`| Controlled by a Contour Design ShuttleXpress, using the browser's WebHID API [See configuration details](prompter.md#control-using-contour-shuttlexpress-via-webhid)|
47
47
|`?mode=pedal`| Controlled by any MIDI device outputting note values between 0 - 127 of CC notes on channel 8. Analogue Expression pedals work well with TRS-USB midi-converters. [See configuration details](prompter.md#control-using-midi-input-modepedal)|
48
48
|`?mode=joycon`| Controlled by Nintendo Switch Joycon, using the HTML5 GamePad API. [See configuration details](prompter.md#control-using-nintendo-joycon-gamepad)|
49
-
|`?mode=xbox`| Controlled by Xbox controller, using the HTML5 GamePad API. [See configuration details](prompter.md#control-using-xbox-controller-modexbox)|
49
+
|`?mode=xbox`| Controlled by Xbox controller, using the HTML5 GamePad API. [See configuration details](prompter.md#control-using-xbox-controller-modexbox)|
50
50
51
51
#### Control using mouse \(scroll wheel\)
52
52
@@ -175,16 +175,16 @@ This mode uses the browsers Gamapad API and polls connected Joycons for their st
175
175
176
176
The Joycons can operate in 3 modes, the L-stick, the R-stick or both L+R sticks together. Reconnections and jumping between modes works, with one known limitation: **Transition from L+R to a single stick blocks all input, and requires a reconnect of the sticks you want to use.** This seems to be a bug in either the Joycons themselves or in the Gamepad API in general.
177
177
178
-
| Query parameter | Type | Description | Default |
|`joycon_speedMap`| Array of numbers | Speeds to scroll by \(px. pr. frame - approx 60fps\) when scrolling forwards. The beginning of the forwards-range maps to the first number in this array, and the end of the forwards-range map to the end of this array. All values in between are being interpolated in a spline curve. |`[1, 2, 3, 4, 5, 8, 12, 30]`|
181
-
|`joycon_reverseSpeedMap`| Array of numbers | Same as `joycon_speedMap` but for the backwards range. |`[1, 2, 3, 4, 5, 8, 12, 30]`|
182
-
|`joycon_rangeRevMin`| number | The end of the backwards-range, full speed backwards. |`-1`|
183
-
|`joycon_rangeNeutralMin`| number | The beginning of the backwards-range. |`-0.25`|
184
-
|`joycon_rangeNeutralMax`| number | The minimum input to run forward, the start of the forward-range \(min speed\). This is also the end of any "deadband" you want filter out before starting moving forwards. |`0.25`|
185
-
|`joycon_rangeFwdMax`| number | The maximum input, the end of the forward-range \(max speed\)|`1`|
186
-
|`joycon_rightHandOffset`| number | A ratio to increase or decrease the R Joycon joystick sensitivity relative to the L Joycon. |`1.4`|
187
-
|`joycon_invertJoystick`| 0 / 1 | Invert the joystick direction. When enabled, pushing the joystick forward scrolls up instead of down. |`1`|
181
+
|`joycon_reverseSpeedMap`| Array of numbers | Same as `joycon_speedMap` but for the backwards range. |`[1, 2, 3, 4, 5, 8, 12, 30]`|
182
+
|`joycon_rangeRevMin`| number | The end of the backwards-range, full speed backwards. |`-1`|
183
+
|`joycon_rangeNeutralMin`| number | The beginning of the backwards-range. |`-0.25`|
184
+
|`joycon_rangeNeutralMax`| number | The minimum input to run forward, the start of the forward-range \(min speed\). This is also the end of any "deadband" you want filter out before starting moving forwards. |`0.25`|
185
+
|`joycon_rangeFwdMax`| number | The maximum input, the end of the forward-range \(max speed\)|`1`|
186
+
|`joycon_rightHandOffset`| number | A ratio to increase or decrease the R Joycon joystick sensitivity relative to the L Joycon. |`1.4`|
187
+
|`joycon_invertJoystick`| 0 / 1 | Invert the joystick direction. When enabled, pushing the joystick forward scrolls up instead of down. |`1`|
188
188
189
189
-`joycon_rangeNeutralMin` has to be greater than `joycon_rangeRevMin`
190
190
-`joycon_rangeNeutralMax` has to be greater than `joycon_rangeNeutralMin`
@@ -241,11 +241,11 @@ The controller can be connected via Bluetooth or USB. **Note:** On macOS, Xbox c
241
241
242
242
**Configuration parameters:**
243
243
244
-
| Query parameter | Type | Description | Default |
|`xbox_speedMap`| Array of numbers | Speeds to scroll by (px per frame, ~60fps) when scrolling forwards. Values are interpolated using a spline curve based on trigger pressure. |`[2, 3, 5, 6, 8, 12, 18, 45]`|
247
247
|`xbox_reverseSpeedMap`| Array of numbers | Same as `xbox_speedMap` but for the backwards range (left trigger). |`[2, 3, 5, 6, 8, 12, 18, 45]`|
248
-
|`xbox_triggerDeadZone`| number | Dead zone for the triggers, to prevent accidental scrolling. Value between 0 and 1. |`0.1`|
248
+
|`xbox_triggerDeadZone`| number | Dead zone for the triggers, to prevent accidental scrolling. Value between 0 and 1. |`0.1`|
249
249
250
250
You can turn on `?debug=1` to see how your trigger input maps to scroll speed.

11
+
12
+
_**Sofie**_ is a web-based TV automation system for studios and live shows, used in daily live TV news productions by the Norwegian public service broadcaster [**NRK**](https://www.nrk.no/about/) since September 2018.
13
+
14
+
## Key Features
15
+
16
+
- User-friendly, modern web-based GUI
17
+
- State-based device control and playout of video, audio, and graphics
18
+
- Modular device-control architecture with support for several hardware \(and software\) setups
19
+
- Modular data-ingest architecture, supports MOS and Google spreadsheets
20
+
- Plug-in architecture for programming shows
21
+
22
+
_The NRK logo is a registered trademark of Norsk rikskringkasting AS. The license does not grant any right to use, in any way, any trademarks, service marks or logos of Norsk rikskringkasting AS._
Sofie has various APIs for talking between components, and for external systems to interact with.
7
+
8
+
We classify each api into one of two categories:
9
+
10
+
## Stable
11
+
12
+
This is a collection of APIs which we intend to avoid introducing any breaking change to unless necessary. This is so external systems can rely on this API without needing to be updated in lockstep with Sofie, and hopefully will make sense to developers who are not familiar with Sofie's inner workings.
13
+
14
+
In version 1.50, a new REST API was introduced. This can be found at `/api/v1.0`, and is designed to allow an external system to interact with Sofie using simplified abstractions of Sofie internals.
15
+
16
+
The _Live Status Gateway_ is also part of this stable API, intended to allow for reactively retrieving data from Sofie. Internally it is translating the internal APIs into a stable version.
17
+
18
+
:::note
19
+
You can find the _Live Status Gateway_ in the `packages` folder of the [Sofie Core](https://github.com/Sofie-Automation/sofie-core) repository.
20
+
:::
21
+
22
+
## Internal
23
+
24
+
This covers everything we expose over DDP, the `/api/0` endpoint and any other http endpoints.
25
+
26
+
These are intended for use between components of Sofie, which should be updated together. The DDP api does have breaking changes in most releases. We use the `server-core-integration` library to manage these typings, and to ensure that compatible versions are used together.
0 commit comments