deploy: b55f409

_sources/user_guide/modifying.rst.txt

@@ -30,7 +30,7 @@ This is an important point to understand, because it is one of the most recurren
 
 Memory consumption of effect and modifications 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-When applying an effect or modification, it does not immediately apply the effect to all the frames of the clip, but only to the first frame: all the other frames will only be modified when required (that is, when you will write the whole clip to a file of when you will preview it). 
+When applying an effect or modification, it does not immediately apply the effect to all the frames of the clip, but only to the first frame: all the other frames will only be modified when required (that is, when you will write the whole clip to a file or when you will preview it). 
 
 It means that creating a new clip is neither time nor memory hungry, all the computation happen during the final rendering.
 
@@ -158,4 +158,4 @@ This will scroll down the clip, with a constant height of 360 pixels.
     When programming a new effect, whenever it is possible, prefer using ``time_transform`` and ``image_transform`` instead of ``transform`` when implementing new effects.
     The reason is that, though they both internally rely on ``transform`` when these effects are applied to ``ImageClip`` objects, MoviePy will recognize they only need to be applied once instead of on each frame, resulting in faster renderings.
 
-To keep things simple, we have only addressed the case of :py:class:`~moviepy.video.VideoClip.VideoClip`, but know that the same principle applies to :py:class:`~moviepy.audio.AudioClip.AudioClip`, except that instead of a picture frame, you will have an audio frame, which is also a numpy array.
+To keep things simple, we have only addressed the case of :py:class:`~moviepy.video.VideoClip.VideoClip`, but know that the same principle applies to :py:class:`~moviepy.audio.AudioClip.AudioClip`, except that instead of a picture frame, you will have an audio frame, which is also a numpy array.

index.html

@@ -354,7 +354,7 @@
   <section id="moviepy-documentation">
 <h1>MoviePy documentation<a class="headerlink" href="#moviepy-documentation" title="Permalink to this heading">#</a></h1>
 <a class="reference internal image-reference" href="_images/logo.png"><img alt="_images/logo.png" class="align-center" src="_images/logo.png" style="width: 50%;" /></a>
-<p><strong>Date</strong>: Nov 27, 2024 <strong>Version</strong>: </p>
+<p><strong>Date</strong>: Nov 30, 2024 <strong>Version</strong>: </p>
 <p><strong>Useful links</strong>:
 <a class="reference external" href="https://pypi.org/project/moviepy/">Binary Installers</a> |
 <a class="reference external" href="https://github.com/Zulko/moviepy">Source Repository</a> |

user_guide/modifying.html

@@ -441,7 +441,7 @@ <h3>Clip copy during modification<a class="headerlink" href="#clip-copy-during-m
 </section>
 <section id="memory-consumption-of-effect-and-modifications">
 <h3>Memory consumption of effect and modifications<a class="headerlink" href="#memory-consumption-of-effect-and-modifications" title="Permalink to this heading">#</a></h3>
-<p>When applying an effect or modification, it does not immediately apply the effect to all the frames of the clip, but only to the first frame: all the other frames will only be modified when required (that is, when you will write the whole clip to a file of when you will preview it).</p>
+<p>When applying an effect or modification, it does not immediately apply the effect to all the frames of the clip, but only to the first frame: all the other frames will only be modified when required (that is, when you will write the whole clip to a file or when you will preview it).</p>
 <p>It means that creating a new clip is neither time nor memory hungry, all the computation happen during the final rendering.</p>
 </section>
 <section id="time-representations-in-moviepy">