Skip to content

Commit 6e72ab3

Browse files
authored
Merge pull request #10972 from berarma/playing_videos_4.5
Update Playing Videos page for Godot 4.5
2 parents 89eaa1f + bca64c8 commit 6e72ab3

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

tutorials/animation/playing_videos.rst

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -150,10 +150,8 @@ To ensure your videos decode smoothly on varied hardware:
150150
Playback limitations
151151
--------------------
152152

153-
There are several limitations with the current implementation of video playback in Godot:
153+
There are some limitations with the current implementation of video playback in Godot:
154154

155-
- Changing playback speed is not supported. VideoStreamPlayer also won't follow
156-
:ref:`Engine.time_scale<class_Engine_property_time_scale>`.
157155
- Streaming a video from a URL is not supported.
158156
- Only mono and stereo audio output is supported. Videos with 4, 5.1 and 7.1
159157
audio channels are supported but down-mixed to stereo.
@@ -195,17 +193,20 @@ below with almost any input video format (AVI, MOV, WebM, …).
195193
You can check this by running ``ffmpeg`` without any arguments, then looking
196194
at the ``configuration:`` line in the command output.
197195

196+
.. warning::
197+
198+
Current official FFmpeg releases have some bugs in their Ogg/Theora
199+
multiplexer. It's highly recommended to use one of the latest static daily
200+
builds, or build from their master branch to get the latest fixes.
201+
198202
.. UPDATE: When the FFmpeg bugfixes for https://trac.ffmpeg.org/ticket/11451 and
199203
.. https://trac.ffmpeg.org/ticket/11454 are included in a stable FFmpeg release,
200-
.. this note can be removed. That will likely be FFmpeg 7.2 or 8.0, and will
204+
.. this warning can be removed. That will likely be FFmpeg 7.2 or 8.0, and will
201205
.. likely happen during the Godot 4.5 or 4.6 release cycle.
202-
203-
.. warning::
204-
205-
All FFmpeg releases before Feb 20th, 2025 could produce bad video streams
206-
due to a couple of bugs. It's highly recommended to use one of the latest
207-
static daily builds, or build FFmpeg from their master branch where they're
208-
already fixed.
206+
.. Commits fixing the issues:
207+
.. - https://github.org/FFmpeg/FFmpeg@22aa71d4da37a4ad2b0d28deeace64b57aa2ef50
208+
.. - https://github.org/FFmpeg/FFmpeg@84d85e7ad4ace228265af0c8c5caccc0730042fd
209+
.. - https://github.org/FFmpeg/FFmpeg@6e26f57f672b05e7b8b052007a83aef99dc81ccb
209210
210211
Balancing quality and file size
211212
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -231,10 +232,9 @@ variable bitrates.
231232

232233
The **GOP (Group of Pictures) size** (``-g:v``) is the max interval between
233234
keyframes. Increasing this value can improve compression with almost no impact
234-
on quality. The valid range goes from ``0`` to ``2,147,483,648``, although
235-
compression benefits will fade away and even be reversed as the GOP size
236-
increases. The default size (``12``) is too low for most types of content, it's
237-
therefore recommended to test higher GOP sizes before reducing video quality.
235+
on quality. The default size (``12``) is too low for most types of content,
236+
it's therefore recommended using higher GOP values before reducing video
237+
quality. Compression benefits will fade away as the GOP size increases though.
238238
Values between ``64`` and ``512`` usually give the best compression.
239239

240240
.. note::

0 commit comments

Comments
 (0)