Is your feature request related to a problem? Please describe.

The current engine only exposes WebVTT subtitles as kind: 'subtitles'. When the playlist entry contains CHARACTERISTICS="public.accessibility.transcribes-spoken-dialog,public.accessibility.describes-music-and-sound", it should have kind: 'captions'. This would match how it is exposed in the Safari HLS player.

**Describe

In many older tutorials, we use things like var and .then() that we forbid in our actual codebase. It would be more readable if the docs used a more modern syntax, especially around Promises. Not only is await easier to read, but our use of .then() in docs may mislead a reader into thinking that they must do the same.

According to the HLS specification, we must sinalize that a given audio track is DVS by the addition of CHARACTERISTICS="public.accessibility.describes-video" tag. I wonder if we should implement an option at the Sequence level on mapped mode where I set "dvs": true or something and that propagates all the way to the HLS manifest. Thoughts on this one @erankor?

More information about this o

As can be seen in the graphic, a display error occurs if too long links are placed in the description.

Steps to reproduce:

1. Open extension's menu and click Shortcuts to show the "shortcut list".
2. Click Picture-in-Picture, opening the "edit dialog".
3. Press any key other that what's shown as the current setting (if any).
4. Note that the list behind the dialog already reflects the change. (Expected: no change to the list unless and until Save is clicked, as that's when the change is actuall

Expected behaviour

When I try this with v2.3 settings are ignored and I get a 422 mp4 clip with 8 audio channels
channel setting is set hd1080i50

ADD 1 FILE "myfile 1.mp4" -codec:v libx264 -crf:v 23 -preset:v veryfast -filter:v format=pix_fmts=yuv420p -filter:v tinterlace=5 -codec:a aac -b:a 128k -ar:a 48k

If I do this
ADD 1 FILE "myfile 1.mp4" -codec:v libx264 -crf:v 23 -preset:v ver

Change documentation to expose monit port [2812] to get monitoring available.

https://github.com/kaltura/platform-install-packages/blob/master/doc/install-docker.md#step-by-step-installation

docker run -d --name=kaltura -p 80:80 -p 443:443 -p 1935:1935 -p 2812:2812 -p 88:88 -p 8443:8443 kaltura/server

I'm going through the Twilio docs on enabling isDominantSpeakerEnabled.

However, when I try to I get an error: No setter method 'setIsDominantSpeakerEnabled:' for assignment to property

Upon digging into the property I see that is it only a getter property.

I'm on the latest 2.10.x version.

Am I missing something to

Emotes in the emote menu should be clickable. Currently the user needs to navigate to the desired emote with the keyboard and hit enter to insert it. This is nigh impossible on mobile.

UTF-16 strings are converted to UTF-8 and cut at 511 characters. If the string is cut then the user should be informed or indicated in the received message.

run browser example (h264-overlay-player.js), throw exception:

h264-overlay-player.js:72 Uncaught TypeError: Cannot read property 'peek' of undefined

no Component exported from components:

const runScheduler = components.Component.peek(msg => scheduler.run(msg))

Recently, we changed the setup tutorial. We should probably take new screenshots to reflect these changes.