-
Resolve feature request… Please let me save my projects as projects, instead of some database.
I haven´t started to use Resolve quite yet, but it is very clear that the whole database thingy will be problematic for my company.
We have four seats for color correction today, and each seat will go through anything between 5 to 50 projects each day. And that can be like 50 projects with five or six different clients. That would be something like 700 projects each week, with tens of different clients.
To have all different reels and all different clients all mushed into the same database feels just wrong, and it is very difficult to have a good overview of all projects for a single client, unless I make new databases each day… and if I do that all settings will disappear for the new database.
Also, reading about the database problems people are having doesen´t feel to good either. If each project would be one projectfile, it wouldn´t be such a disaster if one file got corrupted. But if one database goes bad…. lots of work is down the drain.
And the way it is now, I am not even allowed to choose where the database is stored, where all the projects are saved! They are just somewhere in a database that “I do no need to know anything about”, as if that is a feature. In FCPX it is a feature, not having to know anything and not having any options about where to save your projects/renderfiles/whatever. But I want to know and choose where my stuff is saved, for now and for future needs and references.
If I could save each project in a specific folder that I can choose, in a folder where we have all the clips from this specific client, it would be much easier to know where they are saved, and it would make it much easier for me to find the project a few weeks later if I would need it. Instead of searching some of the hundreds of databases we would have created by then just to be able to have a overview of all projects.
-
4 Replies
-
Hi Kent, first allow me to put you at ease. Resolve has been used for TVC grading for years and in facilities with multiple systems. We do this in our own post house.
The database structure works and is just different to what you are familiar with. It permits the other Resolve seats to see and open other projects and different users to naturally see their own but also import other users projects. I’m not sure how you want to structure your projects but in Resolve you can have multiple sessions, thats different edits, in the same project. This permits the automatic sharing of grades between sessions and is a lot faster than copying grades.
You can always export the projects from the database if you like, this is done on the Config page, and also backup your database. Use the database manager for backup and restore.
If you really do have 50 projects a day, on 5 machines, consider a central database server to share all the projects and then you automate the backups using standard IT practice.
Finally, some clients make a new database per month just to keep them small, some do per feature film or TV series for easy of sorting, but in six years we haven’t experienced anyone who needs to make a new database every week let alone one per day.
That being said, we will look into other project saving options to see how viable they are.
Peter -
I always do an “export+” At the end of every day with the client files just incase, this acts as a save as… For me. I completely understand your fears. As I’m more familiar with a file structure style management than database, but i haven’t felt hampered at all. That said I’m running one seat with only 2-3 ongoing projects at a time, but I don’t feel like I’d be overwhelmed running more with multiple seats.
Joseph Mastantuono
Online Editor – Colorist – Post Consultant
Brooklyn based finishing at reasonable prices
917.969.1583 -
Thanks for the answers. I will look into having a central database and automated backups then, it sounds like a good option and I have a iMac quadcore that could act as the database server (it isn´t used for anything today). And then we´d make new databases when they seem to grow in size.
The manual advices to keep the databases small… but what is “small”? Is there a maximum recommended number of projects or a maximum size in data that could be used as a reference regarding to keeping it “small”, so we´d know when it is time to renew the database to keep it small and snappy?
Where can I find the database, so I can see the size of the database in data (like in MB, GB and such)?
-
yes where is the database for backup in case anything happens as size gets too big or possible upgrade failures for example??
MacPro 4,1 OSX 10.6.8 / FCS3 / CS5
2.26 ghz 8-core / 24GB RAM
Nvidia GT 120/285 combo
Reply to this Discussion! Login or Sign Up