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: NEWS.md
+40
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,45 @@
1
1
# Old Updates
2
2
3
+
### 2024-08-10
4
+
5
+
I have recently added new experimental feature, to play your content directly from the WebUI. This feature is still in
6
+
alpha, and missing a lot of features. But it's a start. Right now it does auto transcode on the fly to play any content in the browser.
7
+
8
+
The feature requires that you mount your media directories to the `WatchState` container similar to the `File integrity` feature. I have plans to expand
9
+
the feature to support more controls, however, right now it's only support basic subtitles streams and default audio stream or first audio stream.
10
+
11
+
The transcoder works by converting the media on the fly to `HLS` segments, and the subtitles are selectable via the player ui which are also converted to `vtt` format.
12
+
13
+
Expects bugs and issues, as the feature is still in alpha. But I would love to hear your feedback. You can play the media by visiting
14
+
the history page of the item you will see red play button on top right corner of the page. If the items has a play button, then you correctly mounted
15
+
the media directories. otherwise, the button be disabled with tooltip of `Media is inaccessible`.
16
+
17
+
The feature is not meant to replace your backend media player, the purpose of this feature is to quickly check the media without leaving the WebUI.
18
+
19
+
### 2024-08-01
20
+
21
+
We recently enabled listening on tls connections via `8443` which can be controlled by `HTTPS_PORT` environment variable.
22
+
Before today, we simply only exposed the port via the `Dockerfile`, but we weren't listening for connections on it.
23
+
24
+
However, please keep in mind that the certificate is self-signed, and you might get a warning from your browser. You can
25
+
either accept the warning or add the certificate to your trusted certificates. We strongly recommend using a reverse proxy.
26
+
instead of relying on self-signed certificates.
27
+
28
+
### 2024-07-22
29
+
30
+
We have recently added a new WebUI feature, `File integrity`, this feature will help you to check if your media backends
31
+
are reporting files that are not available on the disk. This feature is still in alpha, and we are working on improving
32
+
it.
33
+
34
+
This feature `REQUIRES` that you mount your media directories to the `WatchState` container preferably as readonly. There is plans to add
35
+
a path replacement feature to allow you change the pathing, but it's not implemented yet.
36
+
37
+
This feature will work on both local and remote cloud storages provided they are mounted into the container. We also may recommend not to
38
+
use this feature depending on how your cloud storage provider treats file stat calls. As it might lead to unnecessary money spending. and of course
39
+
it will be slower.
40
+
41
+
For more information about how we cache the stat calls, please refer to the [FAQ](FAQ.md#How-does-the-file-integrity-feature-works).
42
+
3
43
### 2024-07-06
4
44
5
45
Recently we have introduced a new feature that allows you to use Jellyfin and Emby OAuth access tokens for syncing
Copy file name to clipboardExpand all lines: README.md
+12-40
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,18 @@ out of the box, this tool support `Jellyfin`, `Plex` and `Emby` media servers.
9
9
10
10
## Updates
11
11
12
+
### 2024-08-19
13
+
14
+
We have migrated the `state:push` task into the new events system, as such the old task `state:push` is now gone.
15
+
To enable the new event handler for push events, use the new environment variable `WS_PUSH_ENABLED` and set it to `true`.
16
+
Right now, it's disabled by default. However, for people who had the old task enabled, it will reuse that setting.
17
+
18
+
Keep in mind, the new event handler is more efficient and will only push data when there is a change in the play state. And it's much faster
19
+
than the old task. This event handler will push data within a minute of the change.
20
+
21
+
PS: Please enable the task by setting its new environment variable `WS_PUSH_ENABLED` to `true`. The old `WS_CRON_PUSH` is now gone.
22
+
and will be removed in the future releases.
23
+
12
24
### 2024-08-18
13
25
14
26
We have started migrating the old events system to a new one, so far we have migrated the `progress` and `requests` to it. As such,
@@ -17,46 +29,6 @@ environment variable `WS_SYNC_PROGRESS` which you can set to `true` to enable th
17
29
18
30
We will continue to migrate the rest of the events to the new system, and we will keep you updated.
19
31
20
-
### 2024-08-10
21
-
22
-
I have recently added new experimental feature, to play your content directly from the WebUI. This feature is still in
23
-
alpha, and missing a lot of features. But it's a start. Right now it does auto transcode on the fly to play any content in the browser.
24
-
25
-
The feature requires that you mount your media directories to the `WatchState` container similar to the `File integrity` feature. I have plans to expand
26
-
the feature to support more controls, however, right now it's only support basic subtitles streams and default audio stream or first audio stream.
27
-
28
-
The transcoder works by converting the media on the fly to `HLS` segments, and the subtitles are selectable via the player ui which are also converted to `vtt` format.
29
-
30
-
Expects bugs and issues, as the feature is still in alpha. But I would love to hear your feedback. You can play the media by visiting
31
-
the history page of the item you will see red play button on top right corner of the page. If the items has a play button, then you correctly mounted
32
-
the media directories. otherwise, the button be disabled with tooltip of `Media is inaccessible`.
33
-
34
-
The feature is not meant to replace your backend media player, the purpose of this feature is to quickly check the media without leaving the WebUI.
35
-
36
-
### 2024-08-01
37
-
38
-
We recently enabled listening on tls connections via `8443` which can be controlled by `HTTPS_PORT` environment variable.
39
-
Before today, we simply only exposed the port via the `Dockerfile`, but we weren't listening for connections on it.
40
-
41
-
However, please keep in mind that the certificate is self-signed, and you might get a warning from your browser. You can
42
-
either accept the warning or add the certificate to your trusted certificates. We strongly recommend using a reverse proxy.
43
-
instead of relying on self-signed certificates.
44
-
45
-
### 2024-07-22
46
-
47
-
We have recently added a new WebUI feature, `File integrity`, this feature will help you to check if your media backends
48
-
are reporting files that are not available on the disk. This feature is still in alpha, and we are working on improving
49
-
it.
50
-
51
-
This feature `REQUIRES` that you mount your media directories to the `WatchState` container preferably as readonly. There is plans to add
52
-
a path replacement feature to allow you change the pathing, but it's not implemented yet.
53
-
54
-
This feature will work on both local and remote cloud storages provided they are mounted into the container. We also may recommend not to
55
-
use this feature depending on how your cloud storage provider treats file stat calls. As it might lead to unnecessary money spending. and of course
56
-
it will be slower.
57
-
58
-
For more information about how we cache the stat calls, please refer to the [FAQ](FAQ.md#How-does-the-file-integrity-feature-works).
0 commit comments