Why Project.db files are so huge in size?

Most of my projects files are 2-4gb in size.
In other video editors projects with similar complexity are around 30MB

Here is a screenshot from a Project.db of a wedding
(5 hour long, 4 timelines, 15 different grades, 1 hour long of stabilized clips, no stills)

Project.db.png (3.34 KiB) Viewed 1154 times

Is this normal?

Stabilization data is stored in the project. That could be normal for stabilizing such a long clip.

Also, that that the only project in the Database? Typically there are many.

Also, that that the only project in the Database? Typically there are many.

I have 290 projects in the database, each project has it's own Project.db file in the corresponding folder of the disk database.

Stabilization data is stored in the project. That could be normal for stabilizing such a long clip.

Yes I found out that the stabilization data is the problem, if you have 1 hour of stabilized clips is not much of a problem, the project size will be around 65mb.

The problem starts when you start splitting stabilized clips. For example, if you have a 10 minute stabilized clip, if you split it in half, each 5 minute half will contain the full 10 minute stabilization data, if you split it in 20 pieces will you end up with 200 minutes of stabilization data.

Picking this thread back up because a similar issue has become quite a problem for me and this last answer makes a lot of sense. I have a Project that has long interview clips that are being cut up into shorter videos, imagine an hour long clip that gets cut into 10 small videos with 10-20 cuts per video.

The first step I've been doing is a Face Refinement pass where I analyze the entire clip, since it's a one time set it and forget it process it works faster than applying this filter to the hundreds of individual clips and then analyzing them each individually one by one.

The problem now is similar to what this thread mentions. Since the Face Analysis data is based on the hour long clip, it seems to be getting duplicated every time I make a cut. Which now means that my project.db file and backup file is over 20gb. Which makes the project difficult to work with.

Can anyone think of a solution that isn't just to analyze each clip one by one? Thanks!

I think it's the stills that take up a lot of the space. Grab Gallery stills from 2000 shots in a feature film, export that file with embedded stills & LUTs. Now export just the DRP by itself (no stills) and compare the file size.

I think it's the stills that take up a lot of the space. Grab Gallery stills from 2000 shots in a feature film, export that file with embedded stills & LUTs. Now export just the DRP by itself (no stills) and compare the file size.

In our experience, this is also the case.

I think it's the stills that take up a lot of the space. Grab Gallery stills from 2000 shots in a feature film, export that file with embedded stills & LUTs. Now export just the DRP by itself (no stills) and compare the file size.

That would make sense but I don't have more than 10 stills grabbed. As there are a lot of clips there are not a lot of different color grades.

Through testing, I've created a few new timelines with the face refinement analysis and instead of analyzing the full clip, I've cut them into smaller sections first. It's dramatically reduced the bloat of the file size and is an acceptable middle ground.