- Updated the export command description to clarify the encoding process and settings retrieval from the project's package.json.
- Simplified language for better readability while retaining essential details about output formats and export behavior.
- Introduced new export command in the CLI to encode scenes into video files, utilizing settings from the project's package.json.
- Added types for export formats and settings, including video and audio configurations.
- Implemented exportScene function to handle the export process and output results.
- Updated README.md to include documentation for the new export command.
- Bumped version from 0.202.0 to 0.202.1 in package.json and package-lock.json for the editor, CLI, desktop, and web applications.
- Ensured consistency in versioning across all related packages to reflect the latest updates.
- Bumped version from 0.201.0 to 0.202.0 in package.json and package-lock.json for the editor, CLI, desktop, and web applications.
- Ensured consistency in versioning across all related packages to reflect the latest updates.
- Bumped version numbers for the editor, CLI, desktop, web applications, and JSX package to 0.200.0 in package.json and package-lock.json.
- Ensured consistency in versioning across all related packages to reflect the latest updates and improvements.
- Bumped version numbers for the editor, CLI, desktop, and web applications to 0.132.2 in package.json and package-lock.json.
- Updated the dashboard feature labels in the web application to better reflect current offerings, enhancing clarity for users.
- Removed outdated features and added new ones to align with the latest capabilities of the platform.
- Modified the `capture` command to render single frames of a scene instead of a node, ensuring the output matches the export's encoding.
- Updated command descriptions and argument details to reflect the new functionality, including changes to the time reference and scene handling.
- Enhanced documentation for the `capture` command and related references to clarify usage and expected behavior.
- Improved error messages for invalid scene captures, guiding users to capture the correct scene id.
- Introduced a new command `dapi check` to analyze a node's subtree for structural issues, including black frames, never-visible nodes, and source errors.
- Implemented types for check requests and results, detailing the structure of issues found during analysis.
- Added a new `check.ts` file to handle the logic for checking nodes, including coverage calculations and issue reporting.
- Updated the `README.md` and reference documentation to include usage instructions and details about the new command.
- Enhanced the CLI with a new command option for checking node integrity without rendering, providing instant feedback on potential issues in the project.
- Updated the CLI context command description to clarify the information reported, including the application root folder and project details.
- Modified the DAPI context handling to return both the projects root directory and the open project directory, improving the context information available when no project is open.
- Adjusted related documentation to reflect the new structure of the context report, ensuring consistency and clarity for users.
- Updated the `AssetRef` type to only accept paths, simplifying asset reference management.
- Refactored media command descriptions to clarify that local files and URLs can be used without an open project, while library paths require one.
- Enhanced error handling in media commands to specify when paths cannot be resolved, improving user feedback.
- Removed the deprecated `ShellApi` component and integrated its functionality into the new `EditorApi` for better organization and clarity.
- Updated the CLI command description for `dapi context` to include information about asset generations, improving clarity on the project's state.
- Modified the desktop application documentation to reflect the new context reporting, detailing the status of asset generations (generating, failed, or done) alongside project and playhead information.
- Refactored the context handling in the web application to collect and report generation states, enhancing the overall context management functionality.
- Changed the `id` type in `CaptureRequest` from number to string to accommodate JSX element IDs.
- Refactored the `resolveNode` function to handle string IDs, improving error handling for ambiguous and non-existent nodes.
- Updated the `README.md` and `capture.md` to clarify the expected format for node IDs, including the use of `file:id` for disambiguation.
- Enhanced the `dapi capture` command documentation to reflect changes in ID handling and provide clearer usage instructions.
- Added the `dapi open` command to launch the app and open or create a project folder, with updates to the `README.md` and `projects.ts` for clarity.
- Implemented `initProject` function to initialize project folders, ensuring they can be opened from any location on disk.
- Updated the `main-channels.ts` and `main.ts` to handle new project initialization requests.
- Enhanced the database schema to support project root types, allowing for better project organization and retrieval.
- Improved the IPC layer to manage multiple routers for different command contexts, ensuring efficient command handling.
- Revised the `dapi context` command description in `README.md`, `index.ts`, and `projects.ts` to clarify its purpose in reporting the current project and playhead position.
- Enhanced the `handleContextGet` function to return detailed project information, including project ID, name, directory, and frame rate.
- Updated the API response structure in `context.ts` to reflect the new project context format, ensuring accurate data representation for users.
- Improved documentation in `context.md` and `README.md` to provide clearer guidance on the command's functionality and expected output.
- Added support for asset manifests with read and write capabilities, allowing for better organization of project assets.
- Introduced new project channels for manifest reading and writing, enhancing communication between main and renderer processes.
- Improved file system interactions with new methods for listing, statting, and removing project files, streamlining asset management.
- Updated package dependencies to include `yaml` for manifest handling and linked `@diffusionstudio/assets` for asset management.
- Refactored existing code to integrate new asset handling features and improve overall project structure.
Eliminated the `compile-project.ts` and `open-folder.ts` files from the CLI, streamlining the codebase. Updated the README to reflect changes in CLI commands, including the removal of outdated examples. Adjusted the API to enhance clarity and maintainability by consolidating asset handling functions and removing unused types. This refactor improves the overall architecture and reduces complexity in the CLI interactions.
Updated imports in cli-client and sidebar-left components to reference the new DAPI context instead of the deprecated editor-api. Removed the editor-api module and its associated files, streamlining the codebase and improving maintainability. This change enhances the overall architecture by consolidating API interactions under the new DAPI structure.
Bumped version for all applications to 0.132.0. Updated the CLI to properly handle environment variables when spawning processes, ensuring compatibility with Electron and improving overall functionality.
Bumped version for all applications to 0.131.0. Added a step in the release workflow to copy the environment variables for the web build, ensuring necessary configurations are set for the desktop app build process. Updated the Vite configuration to enforce environment variable checks for the desktop mode.
Eliminated the `--open` option from the `dapi report` command, which previously opened the created issue in the default browser. Removed the `openInBrowser` function and updated related documentation to reflect these changes, streamlining the command's functionality and focusing on direct issue filing without browser interaction.
Updated the `dapi report` command to file GitHub issues directly using the `gh` CLI, removing the previous markdown report generation step. Enhanced the command's description and options in the README and reference documentation to clarify the immediate submission process and the requirement for `gh` authentication. Adjusted related code in the report handling to streamline issue creation and improve user experience.
Updated the MediaFrameResult and NodeCaptureResult types to utilize a new TimecodedImage format, which includes timecodes for better clarity. Introduced options for combining frames into contact sheets and specifying frames per sheet, enhancing the output structure. Adjusted related functions and documentation to reflect these changes, improving user understanding of the output format and capabilities.
Updated the naming convention for output PNG files in both media frame and node capture functions to use a more descriptive timecode format (e.g., 00h00m01s15f.png). Introduced a new utility function, `timecodeFilename`, to handle the formatting. Adjusted related documentation to reflect these changes, enhancing clarity for users regarding the output file naming structure.
Updated the MediaFrameResult and related functions to replace the timestamp with a timecode string for better clarity. Adjusted the output structure in both media frame and node capture processes to include timecode, ensuring that captured images and frames are named accordingly. Enhanced documentation to reflect these changes, improving user understanding of the output format.
Introduced a new command `dapi report` that allows users to report bugs in the CLI or the app. This command generates a markdown report containing diagnostics, including the app's status and recent logs, and provides a prefilled GitHub issue URL. Updated the README and reference documentation to include details about the new command and its usage.
Updated the context command description for clarity on spatial and temporal references. Refactored the context handling to include selected node IDs, improving the context response structure. Additionally, modified the selection utility to streamline the retrieval of selected node IDs, ensuring consistency across the editor API.
Updated the codebase to replace instances of the Trim component with the Workarea component, enhancing the handling of playback and rendering windows. This change includes adjustments in the context command, encoder, playback system, and rendering logic to utilize the new Workarea structure, ensuring a more intuitive and consistent approach to managing scene work areas.
Updated multiple files to transition from using `<scene>` elements to `<rect>` elements with the `scene` property, promoting rectangle geometries to mount roots. This change enhances the JSX API by clarifying the role of scenes and ensuring consistency across examples and documentation. Additionally, modified related documentation to reflect the new usage and constraints of the `scene` property.
Enhanced the context command description to specify the inclusion of workarea trim in seconds when set, providing users with a more comprehensive overview of the open project. Additionally, updated the context retrieval logic to calculate and return workarea details based on the active scene's trim settings.
Removed optional start and end parameters from the MediaTranscribeRequest type and the mediaTranscribe function, streamlining the transcription process. Updated related documentation to reflect these changes, ensuring a clearer understanding of the transcription command and its usage.
Refactored the downsampleAudio function to improve peak calculation efficiency and accuracy. Updated the logic to handle peak accumulation more effectively, ensuring better audio quality in downsampled outputs. Additionally, expanded the captions documentation to clarify the relationship between timing properties and transcript trimming, enhancing user understanding of captioning mechanics.
Introduced a new `<shaderPaint>` element that applies a WGSL fragment shader to the media paint directly below it in the paint stack. Implemented support for shader uniforms and updated the rendering logic to handle shader paints in the engine. Enhanced the API to include shader-related methods and types, ensuring seamless integration with existing media elements. Updated documentation and examples to demonstrate the new shader capabilities, improving user guidance and showcasing practical implementations.
Modified the "check" script in package.json to reference the correct "examples" directory. Updated the README to replace "video editor" with "media compositor" for improved accuracy and restructured some sentences for better readability. Removed outdated documentation files related to assets, CLI, composition, distribution, and getting started, streamlining the documentation for a more focused user experience.
Updated all JSX elements in the documentation and codebase to use lowercase tags (e.g., `<Scene>` to `<scene>`, `<Video>` to `<video>`, etc.) for uniformity and adherence to the new standards. This change enhances clarity and consistency across the JSX API, ensuring that users have a cohesive experience when working with the elements. Updated related documentation to reflect these changes.
Added a `verticalAlign` property to the `<Captions />` component, allowing for customizable vertical positioning of caption blocks. Updated the relevant API, decoders, and serialization logic to support this new feature. Enhanced documentation to reflect the changes and clarify usage, improving the overall flexibility and usability of the captioning system.
Introduced `offsetX` and `offsetY` as new animatable properties for visual elements, allowing for render-time translations without altering layout boxes. Updated the documentation to reflect these changes, ensuring clarity on their usage. Enhanced the type definitions and functionality in the editor API to support these new properties, improving the overall flexibility of animations in the application.
Revised the documentation for the `<Html>` and `<Surface>` elements, enhancing clarity by updating descriptions and correcting terminology. The `<Html>` element now emphasizes its role in rendering real HTML content, while the `<Surface>` element is described as an element backed by a canvas. Additionally, improved the examples and clarified the relationship between `<Html>` and `<HtmlPaint>`, as well as `<Surface>` and `<SurfacePaint>`, to better guide users in their implementation.
Introduced a new `screenshot` command in the CLI to capture the entire application window as a PNG. Updated the documentation to include this command and its options. Implemented the screenshot functionality in both the CLI and desktop applications, allowing users to save the screenshot to a specified directory. Enhanced the type definitions to support the new screenshot feature, improving overall usability and functionality.
Modified the JSX runtime and related documentation to clarify that `<audio>` and `<video>` tags are not supported within paint hosts. Users are now directed to use the `<Audio>` and `<Video>` composition elements for media playback, ensuring better adherence to the paint host's functionality and improving overall documentation clarity.
Added the `logs` command to the CLI documentation, detailing its functionality for displaying recent console output. Updated the conventions section to specify that the `logs` command outputs plain formatted log lines, enhancing clarity on command outputs and improving the overall documentation for user reference.
Introduced a logging system that captures console output from the running app, including various log levels (debug, info, warning, error). Implemented a new `logs` command in the CLI to display recent log entries, and integrated log handling in the desktop application to maintain a buffer of log entries across reloads. Updated relevant types and API routes to support log retrieval, enhancing debugging capabilities and overall application observability.