fli_video 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/{scripts/03-get-technical-design-and-features.rb → .builders/generators/back/scripts/01-get-technical-design-and-feature-list.rb} +5 -0
- data/{scripts/02-get-features-and-components.rb → .builders/generators/back/scripts/02-get-feature-list-and-components.rb} +4 -0
- data/{scripts/01-get-structure.rb → .builders/generators/back/scripts/03-get-structure.rb} +23 -3
- data/.builders/generators/back/scripts/generated/application-structure.json +231 -0
- data/.builders/generators/back/scripts/generated/features-and-components.md +988 -0
- data/.builders/generators/back/scripts/generated/technical-design-and-features.md +424 -0
- data/.builders/klues/add_episode.klue +1 -1
- data/.builders/klues/create_project.klue +1 -1
- data/.builders/klues/move_to_trash.klue +8 -2
- data/CHANGELOG.md +8 -0
- data/README.md +1 -1
- data/docs/feature-list.md +1 -0
- data/docs/generated/application-structure.json +2 -6
- data/docs/generated/features-and-components.md +36 -30
- data/docs/generated/technical-design-and-features.md +25 -8
- data/docs/technical-specifications.md +14 -1
- data/lib/fli_video/version.rb +1 -1
- data/package-lock.json +2 -2
- data/package.json +1 -1
- data/scripts/01-get-technical-design-and-feature-list.md +5 -0
- data/scripts/01-get-technical-design-and-feature-list.rb +39 -0
- data/scripts/02-get-feature-list-and-components.md +26 -0
- data/scripts/02-get-feature-list-and-components.rb +56 -0
- data/scripts/03-get-code-structure.md +33 -0
- data/scripts/03-get-code-structure.rb +73 -0
- metadata +14 -5
|
@@ -0,0 +1,424 @@
|
|
|
1
|
+
# FliVideo
|
|
2
|
+
|
|
3
|
+
## Application Overview
|
|
4
|
+
|
|
5
|
+
This document provides an overview of a specialized application designed primarily for video content creators using Ecamm Live on the Mac, and adaptable for OBS users. Tailored for projects ranging from individual YouTube videos to episodes in a podcast series, the application fits seamlessly into the workflow between video recording and editing. It streamlines the post-recording process, encompassing file organization, renaming, and assembly of video recordings, thereby enhancing the efficiency and structure of content creation.
|
|
6
|
+
|
|
7
|
+
### Core Functionality
|
|
8
|
+
|
|
9
|
+
- **Video Management**: The application intelligently handles videos recorded via Ecamm Live. Once Ecamm saves the videos with a name and timestamp in its folder, our system relocates them to a specific project or episode folder within the project/recordings directory.
|
|
10
|
+
- **Project and Episode Handling**: Each video project pertains to either a single YouTube video or a series of podcast episodes. The application supports a structured approach to organizing these projects.
|
|
11
|
+
- **Chapter-Based Recording**: Emulating a book's structure, down to chapters and individual paragraphs or sentences, videos are recorded and categorized as chapters, which can further be divided into smaller segments or 'parts', akin to paragraphs or sentences, labeled sequentially (e.g., a, b, c...).
|
|
12
|
+
- **File Naming and Organization**: Adhering to a sophisticated naming convention, the application names projects using a sequence (e.g., a01..a99, b01..), a YouTube channel code (e.g., ac=AppyCast, fv=FliVideo), and specific project descriptors. This convention is applied to organize and identify video chapters and parts within each project.
|
|
13
|
+
- **Combining Video Chapters**: After completing recordings for a chapter, these are joined to form a new video file in the chapter's folder, enhancing content flow and consistency.
|
|
14
|
+
- **Speech to Text Integration**: The application features advanced speech-to-text capabilities, converting spoken content into transcriptions. These transcriptions are then utilized for various content generation scenarios, including automatic tagging, generating prompts for AI-based tools like DALL·E 3, and providing detailed instructions for video editors.
|
|
15
|
+
|
|
16
|
+
### Advanced Features
|
|
17
|
+
|
|
18
|
+
- **Dynamic Configuration**: The system adapts to various configurations set by the user before recording, using this information for subsequent file naming and routing.
|
|
19
|
+
- **Trash and Undo Functions**: Videos deemed suboptimal can be moved to a 'trash' folder, with the ability to undo this action if needed.
|
|
20
|
+
- **Automated File Processing**: Utilizing a FileWatch processor, the application automates responses to file events, like moving new recordings to designated folders.
|
|
21
|
+
- **Content Segmentation**: The application supports segmentation of content into sections and subparts, each with a calculated sequence number and name for easy identification and organization.
|
|
22
|
+
- **Metadata and Transcription Integration**: Extracting metadata from video transcriptions and file tags, the system aids in post-production processes such as keyword generation and chapter transitions.
|
|
23
|
+
|
|
24
|
+
### Organization Suited for
|
|
25
|
+
|
|
26
|
+
- Long form YouTube content
|
|
27
|
+
- Multi Episode Podcasts
|
|
28
|
+
- One off YouTube Short or multiple shorts extracted from Long Form or Episode videos
|
|
29
|
+
- Course Creation
|
|
30
|
+
|
|
31
|
+
## eCamm Live
|
|
32
|
+
|
|
33
|
+
I use eCamm Live to record my videos. It is simple to create videos with scenes and record individual sections of a video. This application should adapt to OBS with minimal changes.
|
|
34
|
+
|
|
35
|
+
eCamm live recording files are saved in the following format:
|
|
36
|
+
|
|
37
|
+
```bash
|
|
38
|
+
Ecamm Live Recording on [YYYY-MM-DD] at [HH.MM.SS].mov
|
|
39
|
+
|
|
40
|
+
# Example
|
|
41
|
+
Ecamm Live Recording on 2023-08-25 at 14.51.58.mov
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
## Configuration
|
|
45
|
+
|
|
46
|
+
|
|
47
|
+
### Global configuration
|
|
48
|
+
|
|
49
|
+
FliVideo uses a global configuration file located at `~/.fli-video.json` to store settings and paths for the application and state information such as the current project and episode. This file is created when the application is first run and is updated when the user changes the configuration.
|
|
50
|
+
|
|
51
|
+
### Project configuration
|
|
52
|
+
|
|
53
|
+
FliVideo stores project-specific settings in `.fv.json` file located in the project's root folder. This file is created when the user creates a new project and is updated when recordings are updated. This file has a section for video and a section for episodes and uses the same structure in both sections
|
|
54
|
+
|
|
55
|
+
## Project Naming and Structure
|
|
56
|
+
|
|
57
|
+
As part of the application development, each video project is assigned an alphanumeric identifier, ensuring a unique and systematic approach to project management.
|
|
58
|
+
|
|
59
|
+
Currently, the application supports four primary project codes corresponding to distinct content areas: AppyCast, AppyDave, WinningPrompts, and FliVideo.
|
|
60
|
+
|
|
61
|
+
Each project is also given a descriptive title, providing clear and immediate insight into its content or objective. Additionally, project names may include a status or keyword, offering a quick reference to the project's current state or specific characteristics. This naming convention and structure are fundamental to the application, as they facilitate efficient organization, easy retrieval, and effective management of diverse projects, ranging from media production to targeted content creation.
|
|
62
|
+
|
|
63
|
+
### Sample project folder names
|
|
64
|
+
|
|
65
|
+
```bash
|
|
66
|
+
a13-wp-openai-moderation-api-announcement-aug-25
|
|
67
|
+
a20-ad-open-interpreter
|
|
68
|
+
a21-ac-custom-gpt-instruction
|
|
69
|
+
a22-ac-browse-with-bing-chatgpt-feature
|
|
70
|
+
a24-ad-appydave-website
|
|
71
|
+
a26-ac-pinokio-NOT-STARTED
|
|
72
|
+
a27-ac-categorize-mp4-CI
|
|
73
|
+
a28-ac-easy-gpt-context-creation-FIND-MINDMAP
|
|
74
|
+
a29-ac-gpts-analyze-pdf-transations
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
### Sample project codes
|
|
78
|
+
|
|
79
|
+
- `ac` - AppyCast
|
|
80
|
+
- `ad` - AppyDave
|
|
81
|
+
- `fv` - FliVideo
|
|
82
|
+
- `wp` - WinningPrompts
|
|
83
|
+
- `c9` - Carnivore90
|
|
84
|
+
- `t1` - Trend10
|
|
85
|
+
|
|
86
|
+
### Video Subfolders
|
|
87
|
+
|
|
88
|
+
Within the application's structure, video subfolders play a crucial role in organizing various elements of a project. These subfolders, residing under `project-name` for single video projects or `project-name/episode-name` for podcast episodes, are named and utilized as follows:
|
|
89
|
+
|
|
90
|
+
- **recordings**: This folder contains individual labeled recordings. Each recording is meticulously named and stored here, serving as the primary repository for raw video footage.
|
|
91
|
+
|
|
92
|
+
- **chapters**: Grouped recordings that have been joined together are stored in this folder. It represents the assembled segments of a project, showcasing the progression from individual recordings to cohesive chapters.
|
|
93
|
+
|
|
94
|
+
- **.trash**: The `.trash` folder is designated for recordings considered as bad takes. This allows for an efficient way to segregate and review discarded content, keeping the main folders clutter-free while retaining the option for retrieval.
|
|
95
|
+
|
|
96
|
+
- **assets**: This folder is utilized for storing extra graphic materials or b-roll assets. These elements are crucial in the production phase of a video, enhancing the visual appeal and providing supplementary content.
|
|
97
|
+
|
|
98
|
+
- **transcription**: Transcription files, providing textual versions of the video content, are stored here. This is especially useful for accessibility, content repurposing, and as a reference during the editing process.
|
|
99
|
+
|
|
100
|
+
|
|
101
|
+
### Chapter naming convention
|
|
102
|
+
|
|
103
|
+
Each video project is divided into chapters, which are further segmented into parts. This structure is analogous to a book's chapters and paragraphs, respectively.
|
|
104
|
+
|
|
105
|
+
A chapter name like introduction may have additional descriptive labels like `introduction-context`, `introduction-outline`, `introduction-call-to-action`.
|
|
106
|
+
|
|
107
|
+
#### Sample chapter names
|
|
108
|
+
|
|
109
|
+
Chapter names help to identify the content of the video and maybe used for transition slide titles or chapter titles in a YouTube video.
|
|
110
|
+
|
|
111
|
+
- introduction
|
|
112
|
+
- overview
|
|
113
|
+
- example
|
|
114
|
+
- question
|
|
115
|
+
- answer
|
|
116
|
+
- summary
|
|
117
|
+
- outro
|
|
118
|
+
|
|
119
|
+
#### Why are parts important?
|
|
120
|
+
|
|
121
|
+
Too minimize the amount of editing required, I may want to record each part of a chapter separately. This allows clean recordings with minimal editing.
|
|
122
|
+
|
|
123
|
+
### Keywords and Tags
|
|
124
|
+
|
|
125
|
+
Any recording can have 1 or more tags associated with it. These tags can be used to inform the video editor to inject B-roll or be picked up by another automation such as transcribe and send to GPT Bot
|
|
126
|
+
|
|
127
|
+
#### Example Tags
|
|
128
|
+
|
|
129
|
+
- `INTRO` - This recording needs to be placed into an intro template
|
|
130
|
+
- `CTA` - Like/subscribe, add comment, link in description or any other call to action
|
|
131
|
+
- `TRIM` - This recording needs to be truncated
|
|
132
|
+
- `TRIM-40s` - This recording needs to be truncated to 40 seconds
|
|
133
|
+
- `BROLL` - This recording needs B-roll
|
|
134
|
+
- `TELEPROMPT` - This recording needs to be transcribed and put into the teleprompter or sent to GPT bot for script inprovement
|
|
135
|
+
- `OUTRO` - This recording needs to be placed into an outro template
|
|
136
|
+
|
|
137
|
+
### Scenarios
|
|
138
|
+
|
|
139
|
+
#### Long form
|
|
140
|
+
|
|
141
|
+
For full-length YouTube videos, the application offers a comprehensive solution from initial recording to final organization. It supports the creation and management of individual video projects, each with unique identifiers and descriptive names. The application's robust structure allows for the segmentation of videos into chapters and subparts, making the editing process more manageable and efficient. This scenario is ideal for YouTubers looking to produce structured, high-quality content for their channels.
|
|
142
|
+
|
|
143
|
+
#### Multi Episode Podcast
|
|
144
|
+
|
|
145
|
+
For podcasters using YouTube as their platform, the application provides excellent tools for episode management. It enables the creation of episodic content, each episode with its own identifier and title, under a single project umbrella. This scenario allows podcast creators to maintain a cohesive series, with easy navigation and organization of episodes, enhancing the listener's experience on YouTube.
|
|
146
|
+
|
|
147
|
+
#### Course Creation
|
|
148
|
+
|
|
149
|
+
In the context of online courses, the application excels in organizing and managing educational content. Course creators can structure their material into distinct sections and chapters, aligning with course modules or lessons. This scenario is particularly useful for educators and trainers who seek to provide a well-organized, accessible learning experience. The application's capabilities in handling multiple recordings and segments ensure that each part of the course is neatly cataloged and easy to access for students.
|
|
150
|
+
|
|
151
|
+
#### Short form
|
|
152
|
+
|
|
153
|
+
The application streamlines YouTube Shorts creation by allowing users to start new shorts projects or extract segments from longer videos. It enables easy segmentation, customization with intros and outros, and organizes these shorts in dedicated folders, enhancing content diversity on YouTube.
|
|
154
|
+
|
|
155
|
+
### YouTube Shorts
|
|
156
|
+
|
|
157
|
+
The application is proficiently designed to accommodate the creation of YouTube Shorts, catering to both standalone short-form videos and segments derived from longer recordings.
|
|
158
|
+
|
|
159
|
+
**Standalone Shorts**: When starting a brand-new project specifically as a YouTube Short, the process mirrors that of a regular YouTube video. The application allows for the creation, naming, and organization of these shorts in their unique project folders.
|
|
160
|
+
|
|
161
|
+
**Shorts from Longer Recordings**: In many instances, a segment within a chapter or even a single paragraph might be ideal for a YouTube Short. In such cases, the application offers the flexibility to extract and separate these segments. It allows for the recording of additional intros and outros, specifically tailoring the segment for the short-form format. These extracted segments are then organized into a dedicated folder, designated for YouTube Shorts, within the main project. This ensures that while the original recording remains an integral part of the larger video or episode, the segment is also independently accessible for the video editor to assemble into a YouTube Short.
|
|
162
|
+
|
|
163
|
+
## Project Structure Design
|
|
164
|
+
|
|
165
|
+
The following sections describe the application's structure and naming conventions using an exiting project example and highlights the system's capabilities in managing video projects and episodes.
|
|
166
|
+
|
|
167
|
+
#### Project Naming and Organization
|
|
168
|
+
|
|
169
|
+
Each project in the system is uniquely identified with a structured naming convention. For example, `a27-ac-categorize-mp4-IN-PROGRESS` breaks down as follows:
|
|
170
|
+
|
|
171
|
+
- **Sequence**: 'a27', representing the project's unique identifier.
|
|
172
|
+
- **Project Code**: 'ac', denoting the AppyCast channel.
|
|
173
|
+
- **Project Name**: 'categorize-mp4', describing the project's focus.
|
|
174
|
+
- **Status**: 'IN-PROGRESS', indicating the current stage of the project.
|
|
175
|
+
|
|
176
|
+
#### Episode Management
|
|
177
|
+
|
|
178
|
+
Episodes within a project are optional and are used when a project encompasses multiple videos. Each episode has its own folder named with a sequence and descriptive title, such as `01-flivideo-project-kickoff`:
|
|
179
|
+
|
|
180
|
+
- **Sequence**: '01', '02', etc., showing the episode's order in the series.
|
|
181
|
+
- **Episode Name**: Like 'flivideo-project-kickoff', providing a brief description of the episode's content.
|
|
182
|
+
|
|
183
|
+
#### Recordings Folder
|
|
184
|
+
|
|
185
|
+
The recordings folder, e.g., `a27-ac-categorize-mp4-CI/01-flivideo-project-kickoff/recordings`, contains individual video files. These are named following a specific pattern:
|
|
186
|
+
|
|
187
|
+
- **Sequence and Section Name**: Starting with a number indicating their order, followed by a descriptive name, like '01-introduction.mov'.
|
|
188
|
+
- **Subparts**: For more detailed segmentation, files are further labeled with suffixes like '-a', '-b', '-c', indicating the subparts of a section, such as '02-a-overview.mov', '02-b-overview.mov'.
|
|
189
|
+
|
|
190
|
+
Here is an example from episode 1 of the FliVideo project Podcast.
|
|
191
|
+
|
|
192
|
+
```bash
|
|
193
|
+
# a27-ac-categorize-mp4-CI/01-flivideo-project-kickoff/recordings
|
|
194
|
+
|
|
195
|
+
01-introduction.mov
|
|
196
|
+
02-a-overview.mov
|
|
197
|
+
02-b-overview.mov
|
|
198
|
+
02-c-overview.mov
|
|
199
|
+
02-d-overview.mov
|
|
200
|
+
02-e-overview.mov
|
|
201
|
+
03-a-role_CI.mov
|
|
202
|
+
03-b-overview_CI.mov
|
|
203
|
+
04-a-gpt-first-attempt.mov
|
|
204
|
+
04-b-gpt-first-attempt-explanation.mov
|
|
205
|
+
05-first-commands_TRANSITION.mov
|
|
206
|
+
06-a-commands_CI.mov
|
|
207
|
+
07-b-commands_CI.mov
|
|
208
|
+
07-d-commands-goal_CI.mov
|
|
209
|
+
08-a-response_CI-TRANSITION.mov
|
|
210
|
+
08-b-response_CI-TRANSITION.mov
|
|
211
|
+
09-a-gpt-2nd-attempt.mov
|
|
212
|
+
09-b-gpt-2nd-attempt.mov
|
|
213
|
+
09-c-gpt-2nd-attempt.mov
|
|
214
|
+
10-a-gpt-goal.mov
|
|
215
|
+
10-b-gpt-goal.mov
|
|
216
|
+
10-c-gpt-goal.mov
|
|
217
|
+
10-d-gpt-goal.mov
|
|
218
|
+
10-e-gpt-goal.mov
|
|
219
|
+
10-f-gpt-goal.mov
|
|
220
|
+
11-a-gpt-goal-more.mov
|
|
221
|
+
11-b-gpt-goal-more.mov
|
|
222
|
+
12-a-code-cli.mov
|
|
223
|
+
12-b-code-cli.mov
|
|
224
|
+
12-c-code-cli.mov
|
|
225
|
+
13-a-code-cli-run.mov
|
|
226
|
+
13-b-code-cli-run.mov
|
|
227
|
+
13-c-code-cli-run.mov
|
|
228
|
+
14-a-support-project-name.mov
|
|
229
|
+
14-b-support-project-name.mov
|
|
230
|
+
14-c-support-project-name.mov
|
|
231
|
+
15-outro.mov
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
#### Chapters Folder
|
|
235
|
+
|
|
236
|
+
In the chapters folder, such as `a27-ac-categorize-mp4-CI/01-flivideo-project-kickoff/chapters`, recordings are grouped and combined to form complete chapters of the project:
|
|
237
|
+
|
|
238
|
+
- **Compiled Chapters**: Each file represents a combined version of the recordings from the 'recordings' folder, named by their sequence and section, like '01-introduction.mov', '02-overview.mov'.
|
|
239
|
+
- **Cohesive Segments**: These files reflect the culmination of individual recordings and subparts, merged to create cohesive segments of the project or episode.
|
|
240
|
+
|
|
241
|
+
Here is an example from episode 1 of the FliVideo project Podcast.
|
|
242
|
+
|
|
243
|
+
```bash
|
|
244
|
+
# a27-ac-categorize-mp4-CI/01-flivideo-project-kickoff/chapters
|
|
245
|
+
|
|
246
|
+
01-introduction.mov
|
|
247
|
+
02-overview.mov
|
|
248
|
+
03-role_CI.mov
|
|
249
|
+
04-gpt-first-attempt.mov
|
|
250
|
+
05-first-commands.mov
|
|
251
|
+
06-commands.mov
|
|
252
|
+
07-commands-goal.mov
|
|
253
|
+
08-response_CI.mov
|
|
254
|
+
09-gpt-2nd-attempt.mov
|
|
255
|
+
10-gpt-goal.mov
|
|
256
|
+
11-gpt-goal-more.mov
|
|
257
|
+
12-code-cli.mov
|
|
258
|
+
13-code-cli-run.mov
|
|
259
|
+
14-support-project-name.mov
|
|
260
|
+
15-outro.mov
|
|
261
|
+
```
|
|
262
|
+
|
|
263
|
+
#### Sample Project #1 - Single Video
|
|
264
|
+
|
|
265
|
+
Example folder structure for single video projects
|
|
266
|
+
|
|
267
|
+
```bash
|
|
268
|
+
project-name/recordings/01-introduction.mov
|
|
269
|
+
project-name/recordings/02-a-content.mov
|
|
270
|
+
project-name/recordings/02-b-content.mov
|
|
271
|
+
project-name/recordings/03-a-outro.mov
|
|
272
|
+
project-name/recordings/03-b-outro-cta.mov
|
|
273
|
+
project-name/chapters/01-introduction.mov
|
|
274
|
+
project-name/chapters/02-content.mov
|
|
275
|
+
project-name/chapters/03-outro.mov
|
|
276
|
+
```
|
|
277
|
+
|
|
278
|
+
#### Sample Project #2 - Multiple Episodes
|
|
279
|
+
|
|
280
|
+
Example folder structure for multiple episode projects
|
|
281
|
+
|
|
282
|
+
```bash
|
|
283
|
+
project-name/01-episode-name/recordings/01-introduction.mov
|
|
284
|
+
project-name/01-episode-name/recordings/02-a-content.mov
|
|
285
|
+
project-name/01-episode-name/recordings/02-b-content.mov
|
|
286
|
+
project-name/01-episode-name/recordings/03-a-outro.mov
|
|
287
|
+
project-name/01-episode-name/recordings/03-b-outro-cta.mov
|
|
288
|
+
project-name/01-episode-name/chapters/01-introduction.mov
|
|
289
|
+
project-name/01-episode-name/chapters/02-content.mov
|
|
290
|
+
project-name/01-episode-name/chapters/03-outro.mov
|
|
291
|
+
```
|
|
292
|
+
|
|
293
|
+
```bash
|
|
294
|
+
project-name/02-different-episode-name/recordings/01-introduction.mov
|
|
295
|
+
project-name/02-different-episode-name/recordings/02-content.mov
|
|
296
|
+
project-name/02-different-episode-name/recordings/03-a-outro.mov
|
|
297
|
+
project-name/02-different-episode-name/recordings/03-b-outro-endcards.mov
|
|
298
|
+
project-name/02-different-episode-name/chapters/01-introduction.mov
|
|
299
|
+
project-name/02-different-episode-name/chapters/02-content.mov
|
|
300
|
+
project-name/02-different-episode-name/chapters/03-outro.mov
|
|
301
|
+
```
|
|
302
|
+
|
|
303
|
+
#### Sample Project #3 - Awaiting descision to keep or trash
|
|
304
|
+
|
|
305
|
+
Example folder structure where there are a bunch of files that I have not yet marked as Good Takes,
|
|
306
|
+
All recordings need to be considered bad takes until I say save, at which time any prior bad takes will be moved to trash
|
|
307
|
+
|
|
308
|
+
1 project=1 standard video before trash
|
|
309
|
+
|
|
310
|
+
```bash
|
|
311
|
+
project-name/.trash
|
|
312
|
+
project-name/recordings/01-introduction.mov
|
|
313
|
+
project-name/recordings/02-a-content.mov
|
|
314
|
+
project-name/recordings/02-b-content.mov
|
|
315
|
+
project-name/recordings/03-a-outro.mov
|
|
316
|
+
project-name/recordings/03-b-outro-cta.mov
|
|
317
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 09.58.55.mov
|
|
318
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 09.59.38.mov
|
|
319
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.00.03.mov
|
|
320
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.00.26.mov
|
|
321
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.00.55.mov
|
|
322
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.01.30.mov
|
|
323
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.02.25.mov
|
|
324
|
+
project-name/recordings/Ecamm Live Recording on 2023-12-18 at 10.02.56.mov
|
|
325
|
+
```
|
|
326
|
+
|
|
327
|
+
#### Sample Project #4 - After trash
|
|
328
|
+
|
|
329
|
+
Notice that most of the bad takes have been moved to the trash folder, but the last one was named as 03-c-outro.mov
|
|
330
|
+
|
|
331
|
+
1 project=1 standard video after trash
|
|
332
|
+
|
|
333
|
+
```bash
|
|
334
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 09.58.55.mov
|
|
335
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 09.59.38.mov
|
|
336
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 10.00.03.mov
|
|
337
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 10.00.26.mov
|
|
338
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 10.00.55.mov
|
|
339
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 10.01.30.mov
|
|
340
|
+
project-name/.trash/Ecamm Live Recording on 2023-12-18 at 10.02.25.mov
|
|
341
|
+
project-name/recordings/01-introduction.mov
|
|
342
|
+
project-name/recordings/02-a-content.mov
|
|
343
|
+
project-name/recordings/02-b-content.mov
|
|
344
|
+
project-name/recordings/03-a-outro.mov
|
|
345
|
+
project-name/recordings/03-b-outro-cta.mov
|
|
346
|
+
project-name/recordings/03-c-outro.mov
|
|
347
|
+
```
|
|
348
|
+
|
|
349
|
+
## Features
|
|
350
|
+
|
|
351
|
+
### Feature <-> DSL GPTs
|
|
352
|
+
https://chat.openai.com/g/g-AyFi0UOXn-code-simplifier
|
|
353
|
+
|
|
354
|
+
**Global Configuration**
|
|
355
|
+
Access and apply global configuration settings for video asset management and state consistency.
|
|
356
|
+
|
|
357
|
+
**Project Configuration**
|
|
358
|
+
Access and apply video or episode settings and state. Infers project settings from existing project folders and files.
|
|
359
|
+
|
|
360
|
+
**CLI Project Commands**
|
|
361
|
+
Efficiently execute and manage video project commands using a command-line interface, enhancing control and flexibility in project handling.
|
|
362
|
+
|
|
363
|
+
**FileWatch Processor**
|
|
364
|
+
Utilize a FileWatch processor to automate file event responses, directing new recordings to designated folders for efficient content management.
|
|
365
|
+
|
|
366
|
+
**Create Project**
|
|
367
|
+
Setup a new video project for standalone YouTube video or Podcast.
|
|
368
|
+
|
|
369
|
+
**Add Episode**
|
|
370
|
+
Add a new episode to an existing podcast project.
|
|
371
|
+
|
|
372
|
+
**Switch Video Focus**
|
|
373
|
+
Easily switch between different video projects or episodes to accommodate changing content priorities.
|
|
374
|
+
|
|
375
|
+
**Move eCamm File**
|
|
376
|
+
Seamlessly transfer eCamm recordings to the current focused video or podcast episode recordings subfolder.
|
|
377
|
+
|
|
378
|
+
**Project Path**
|
|
379
|
+
Construct and manage project paths dynamically using configurable values and existing folder name segments.
|
|
380
|
+
|
|
381
|
+
**Episode Path**
|
|
382
|
+
Construct and manage episode paths dynamically using configurable values and existing folder name segments.
|
|
383
|
+
|
|
384
|
+
**Recording Namer**
|
|
385
|
+
Dynamically generate and update video recording filenames, incorporating chapter and part sequences, chapter names, and tags, with capabilities to modify chapter sequences and tags for improved organization and content identification.
|
|
386
|
+
|
|
387
|
+
**Change Chapter Name**
|
|
388
|
+
Alter the name of a chapter based on its sequence in the project, facilitating better organization and identification of video content.
|
|
389
|
+
|
|
390
|
+
**Trash**
|
|
391
|
+
Moves suboptimal video takes to a designated 'trash' or 'archive' folder, optimizing storage and maintaining project clarity by segregating lesser-quality content.
|
|
392
|
+
|
|
393
|
+
**Trash Undo**
|
|
394
|
+
Retrieves video takes from the '.trash' folder and moves them back into the target project folder, allowing for reconsideration or re-evaluation of previously discarded content.
|
|
395
|
+
|
|
396
|
+
**Clean Trash**
|
|
397
|
+
Permanently deletes video takes from the 'trash' or 'archive' folder, freeing up storage space and ensuring project clarity.
|
|
398
|
+
|
|
399
|
+
**Open in Finder**
|
|
400
|
+
Quickly access video project and episode folders within the Finder, streamlining file navigation.
|
|
401
|
+
|
|
402
|
+
**Create Chapter Video**
|
|
403
|
+
Combine and review video chapter segments independently, facilitating content evaluation and editing.
|
|
404
|
+
|
|
405
|
+
**Text to Speech**
|
|
406
|
+
Transcribe spoken content to text and store transcriptions folder in multiple transcription formats.
|
|
407
|
+
|
|
408
|
+
Create a DSL using the interactor pattern for:
|
|
409
|
+
|
|
410
|
+
**Transcript Data Store**
|
|
411
|
+
Builds a JSON datastore of transcripts for an entire project based on existing transcript folders found within project, episode, recording, chapter and post-produced folders.
|
|
412
|
+
|
|
413
|
+
**Project Meta Data Store**
|
|
414
|
+
Build a JSON datastore of files for an entire project based on existing project, episode, recording, chapter and post-produced folders and infer metadata based on KEYWORDS, transcripts or other useful data.
|
|
415
|
+
|
|
416
|
+
## Future Ideas
|
|
417
|
+
|
|
418
|
+
**Web Command Interface for Video Project Management**
|
|
419
|
+
Introduce a streamlined, web-based interface for managing video project commands, enabling efficient control and organization of project components through simple browser interactions.
|
|
420
|
+
|
|
421
|
+
**Project Meta Report**
|
|
422
|
+
Generate a detailed report for a specific video project, including the episodes, chapters, recordings, a list of recording IDs (chapter sequence + part sequence), and the name for the next video recording, file sizes.
|
|
423
|
+
This should be extracted to an AstroJS Website or HTML template servered by a local webserver and provide viewing and navigation for all my video projects.
|
|
424
|
+
|
|
@@ -11,9 +11,9 @@ component :move_to_trash do
|
|
|
11
11
|
|
|
12
12
|
constructure(:parent_project)
|
|
13
13
|
|
|
14
|
-
method :run(:file_name)
|
|
14
|
+
method :run(:file_name = nil)
|
|
15
15
|
|
|
16
|
-
sample :
|
|
16
|
+
sample :move_named_video_to_trash, <<~RUBY
|
|
17
17
|
project_path = ProjectPath.new('a27')
|
|
18
18
|
|
|
19
19
|
command = move_to_trash.new(project_path)
|
|
@@ -21,7 +21,13 @@ component :move_to_trash do
|
|
|
21
21
|
# Example of moving a specific suboptimal video take to the trash folder
|
|
22
22
|
command.run('01-a-introduction.mov')
|
|
23
23
|
# => "~/video-projects/a27-ac-categorize-mp4-CI/.trash/01-a-introduction.mov"
|
|
24
|
+
RUBY
|
|
25
|
+
|
|
26
|
+
sample :move_last_ecamm__video_to_trash, <<~RUBY
|
|
27
|
+
project_path = ProjectPath.new('a27')
|
|
24
28
|
|
|
29
|
+
command = move_to_trash.new(project_path)
|
|
30
|
+
|
|
25
31
|
# Example of moving the last suboptimal video take to the trash folder
|
|
26
32
|
command.run
|
|
27
33
|
# => "~/video-projects/a27-ac-categorize-mp4-CI/.trash/Ecamm Live Recording on 2023-08-25 at 14.51.58.mov
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,11 @@
|
|
|
1
|
+
# [0.1.0](https://github.com/klueless-io/fli_video/compare/v0.0.2...v0.1.0) (2023-12-24)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Features
|
|
5
|
+
|
|
6
|
+
* project kickoff ([a3863cf](https://github.com/klueless-io/fli_video/commit/a3863cf712002497cb77a829b2b832a0f8d54a0b))
|
|
7
|
+
* starting projectx ([0680236](https://github.com/klueless-io/fli_video/commit/06802367b7a1cfa3b928b97e41031d1c24c41c9b))
|
|
8
|
+
|
|
1
9
|
## [0.0.2](https://github.com/klueless-io/fli_video/compare/v0.0.1...v0.0.2) (2023-12-19)
|
|
2
10
|
|
|
3
11
|
|
data/README.md
CHANGED
data/docs/feature-list.md
CHANGED
|
@@ -73,3 +73,4 @@ Introduce a streamlined, web-based interface for managing video project commands
|
|
|
73
73
|
**Project Meta Report**
|
|
74
74
|
Generate a detailed report for a specific video project, including the episodes, chapters, recordings, a list of recording IDs (chapter sequence + part sequence), and the name for the next video recording, file sizes.
|
|
75
75
|
This should be extracted to an AstroJS Website or HTML template servered by a local webserver and provide viewing and navigation for all my video projects.
|
|
76
|
+
|
|
@@ -19,10 +19,6 @@
|
|
|
19
19
|
"name": "README.md",
|
|
20
20
|
"type": "file"
|
|
21
21
|
},
|
|
22
|
-
{
|
|
23
|
-
"name": "readme-current-project-setup.md",
|
|
24
|
-
"type": "file"
|
|
25
|
-
},
|
|
26
22
|
{
|
|
27
23
|
"name": "lib",
|
|
28
24
|
"type": "directory",
|
|
@@ -34,12 +30,12 @@
|
|
|
34
30
|
{
|
|
35
31
|
"name": "cli.rb",
|
|
36
32
|
"type": "file",
|
|
37
|
-
"content": "# frozen_string_literal: true\n\nrequire_relative '../fli_video'\n\nmodule FliVideo\n class CLI\n def self.start(args)\n new(args).execute\n end\n\n def initialize(args)\n @args = args\n end\n\n def execute\n if @args.empty?\n puts
|
|
33
|
+
"content": "# frozen_string_literal: true\n\nrequire_relative '../fli_video'\n\nmodule FliVideo\n # FliVideo::CLI is the command line interface for the FliVideo gem.\n class CLI\n def self.start(args)\n new(args).execute\n end\n\n def initialize(args)\n @args = args\n end\n\n def execute\n if @args.empty?\n puts 'FliVideo CLI - No command provided'\n return\n end\n\n case @args.first\n when 'version'\n puts \"FliVideo version #{FliVideo::VERSION}\"\n else\n puts \"Unknown command: #{@args.first}\"\n end\n end\n end\nend\n"
|
|
38
34
|
},
|
|
39
35
|
{
|
|
40
36
|
"name": "version.rb",
|
|
41
37
|
"type": "file",
|
|
42
|
-
"content": "# frozen_string_literal: true\n\nmodule FliVideo\n VERSION = '0.0
|
|
38
|
+
"content": "# frozen_string_literal: true\n\nmodule FliVideo\n VERSION = '0.1.0'\nend\n"
|
|
43
39
|
}
|
|
44
40
|
]
|
|
45
41
|
},
|