Code Lab
REA Video Explained: Turn a Reference Clip into a Shot-by-Shot Production Plan
CODE LAB · PROJECT SPOTLIGHT
REA Video Python · Apache-2.0
Turn a clip into a shot list, inspect the analysis and build a production plan from reviewable evidence.
Preview: GitHub / JuneYaooo/rea-video · checked November 15, 2026
REA Video is useful when a reference clip becomes a reviewable plan: what each shot shows, when it changes, and which materials or tools a remake would need. The creator’s published examples make that purpose easier to see.
This is JuneYaooo’s Python video-analysis project, separate from the application-and-binary tool in our REA introduction. It produces a human-readable report and a structured VIDEO.md package for agents. The examples below are published by the project maintainer; they are not our own reproductions.
Creator demos: what the analysis is for
A good breakdown connects three things: the visible scene, its job in the story, and the work needed to rebuild it. Detecting a cut helps establish the timeline. It does not, by itself, explain why the cut is there or whether a shot needs a real screen recording, a generated character or motion graphics.
Still previews are shown below. Original clips open on GitHub when selected. The creator’s before-and-after demo is also available in the repository ↗.
Example 1: a mixed-media explainer
The maintainer’s English report describes a 19-second vertical clip with ten shots, alternating AI-character dialogue and code-rendered or screenshot-based material. It also maps the sequence’s editorial roles, including the opening problem, explanation, evidence and ending. The report combines measurements with assistant review; its labels are the author’s analysis, not an independent accuracy benchmark.

Watch the creator’s clip on GitHub ↗Read the published analysis ↗
Look at the change between a character and a document or interface. For a remake, those are different production jobs. One needs a consistent character performance; the other needs readable, relevant evidence. Treating both as “generate another video shot” could produce an attractive clip while losing the explanation.
That is the practical value of the breakdown: it helps a creator decide what to generate, what to record and what to assemble in an editor. It also gives an agent something specific to revise. If a claim is followed by an unrelated screenshot, the problem is the evidence choice, not merely the transition timing.
The published analysis connects timing with meaning

The table’s useful distinction is between when a scene appears and what it is doing. Timing is measurable. A role such as introducing a problem or supplying evidence requires interpretation. Read those columns together, then check the actual frames before using the plan.
For example, a support-tool explainer should show the relevant interface immediately after describing a useful feature. A lifestyle montage might use a different rhythm. The same cut duration is not automatically the right editorial choice for both subjects. A source report is a starting point for that decision, not a finished brief for every new video.
View creator example 2: product-promo analysis
The pinned English report for the OiiOi product promo describes a 70-second, nine-shot sequence, largely built from code-based interface animation. This illustrates a different use: identifying how a product pitch moves from introduction to demonstration and comparison. Counts and labels here refer to that English report revision; older thumbnails elsewhere in the repository can differ.

Watch the creator’s clip on GitHub ↗Read the published analysis ↗
For a software article, the important question is whether the screen content demonstrates the claim being made. A motion-graphics plan can help present a workflow, but it cannot verify that the product actually performs it. Keep the real interface, the promotional animation and the analysis separate.
Actual source: how a hard-cut candidate is scored
The Python detector combines color-histogram distance and normalized pixel differences, compares candidates with a local activity baseline, and considers how much of the frame changed. This is one technical layer beneath the report. It helps locate structural changes; it does not supply all the narrative or production judgments shown above.
Actual source at rea_video/shots.py, pinned commit 5b09832. Copyright 2026 JuneYaooo; Apache-2.0. Original source text is retained, with line numbers and syntax colors added for readability.
How to use the result for a new video
Begin with the message your audience needs, then use a reference to examine pacing and production choices. Keep the roles that help explain your subject, supply your own evidence and materials, and review each proposed shot against the brief. A generated scene, a real software capture and a title card should each have a reason to be there.
A useful handoff contains the relevant frames, the report and a short list of changes. Ask the agent to identify missing materials before generation. If a plan calls for a software demonstration, capture the actual interface rather than inventing a screen that only looks plausible. OpenMontage’s production workflow offers a related way to think about planning and review as separate stages.
Setup, costs and limits
Follow the README at the reviewed revision. Python 3.10 or newer and ffmpeg are required; optional features add dependencies and model downloads. A connected vision provider can charge for inference, while downstream video generation has its own access and costs. Repository access does not include unlimited model usage.
The maintainer’s examples may combine automated measurements and later agent review. We inspected the published reports and source; we have not independently reproduced these case studies. Compression, missing metadata and ambiguous imagery can affect production-origin judgments. A displayed score is not a certificate that footage is authentic or AI-generated, and the repository license does not grant rights to arbitrary input videos.
Official references: Repository and demo · Releases / tags · Mixed-media report · Product-promo report · Exact source excerpt.
Source credit and license notices
rea-video
Copyright 2026 JuneYaooo
Licensed under the Apache License, Version 2.0.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 JuneYaooo
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Reviewed November 15, 2026. Discovery lead: Mindung EasyAI’s REA Video demonstration. The creator’s Claude, ego lite and Higgsfield workflow is a separate integration, not a pipeline reproduced for this article.
