Incorrect Video Linking When Re‑Opening Saved Projects

Topaz Video Bugs and Issues
1

Bug Report: Incorrect Video Linking When Re‑Opening Saved Projects

To the Topaz Video Team,

I would like to report a reproducible issue related to project management and video linking in Topaz Video 1.6.0. This bug affects workflows involving multiple projects that contain similarly named video files (e.g., episodic content organized by season and episode).

Summary of the Issue

When reopening a previously saved project, Topaz Video 1.6.0 sometimes loads video files from a different project instead of the correct files originally associated with that project.
This occurs even though each project was saved and closed properly.

Steps to Reproduce

  1. Create a first project (e.g., Project A).

  2. Import multiple video files from a TV series, organized by season and episode (e.g., S01 E01.mp4, S01 E02.mp4, etc.).

  3. Apply cropping if needed, then save Project A and close it.

  4. Create a second project (e.g., Project B) for a different TV series, also organized with filenames such as S01 E01.mp4, S01 E02.mp4, etc.

  5. Save Project B and close it.

  6. Reopen Project A.

Observed Behavior

When Project A is reopened, Topaz Video AI incorrectly imports some of the video files from Project B, instead of loading the original files belonging to Project A.

This results in:

  • Wrong episodes appearing in the project

  • Incorrect source files being processed

  • Loss of project integrity

  • Risk of processing the wrong content without noticing

The issue seems related to filename similarity across projects, but the software should rely on full file paths, not only filenames.

Expected Behavior

When reopening a saved project, Topaz Video AI should:

  • Load exactly the video files originally imported into that project

  • Respect the full file path and project metadata

  • Never substitute files from another project, even if filenames are identical

Each project should remain fully isolated and self‑consistent.

Impact on Workflow

This bug is particularly problematic for users working with:

  • Large TV series

  • Multi‑season restoration projects

  • Batch processing pipelines

  • Multiple projects with similar naming conventions

It can lead to processing the wrong episodes, wasted time, and potential loss of work.

Conclusion

This issue appears to be a project‑loading bug related to file path resolution or internal caching. Ensuring that each project reliably loads its own source files would greatly improve stability and trust in multi‑project workflows.

If needed, I can provide sample files, screen recordings, or additional diagnostic details.

Best regards, Vincent.

2

Could you share the app’s logs?

To gather logs, please open the app and select Help > Logging > Get Logs for Support and attach the zip file to your reply.

3

Hi Margaux,

These are the requested logs:

logsForSupport.zip (3.6 MB)

The funniest situation: I can see in the filmstrip under the timeline the proper content, but on the main viewport, the application displays the previous project!

I mean I have several projects, each one in a different place holder, but each one having same names for video contents.

Project A > S01 E01.mp4 ; S01 E02.mp4 ; S01 E03.mp4 ; etc.

Project B > S01 E01.mp4 ; S01 E02.mp4 ; S01 E03.mp4 ; etc.

When I open Project A as a brand new session, I see all content attached to Project A.

I close Project A but I am not quitting the application.

Then when I open Project B as a continuing session, in the filmstrip under the timeline, I see contents of Project B, but in the main viewport, the application displays Project A content!

Best regards, Vincent.