Hello,

I was looking to get the community's thoughts on this workflow  

We are considering generating our proxies through Davinci or Silverstack. We would then have to generate the database files manually inside the MXF folder. Once those database files are generated we will rename the folder to the shooting date.

Do you foresee any issues or downsides with this approach? If we run into any tech problems or anomalies, will this workflow hinder us being supported by Avid? 

Thanks.  

Hi, 

Why would you want to organise your Avid Mediafiles database?

I would just transcode in resolve then consolidate those MXF's into Avid. 

Note avid nowadays can manage both OP-Atom media and OP1a within it's Avid Media Files folder structure. 

the_rube:

Hello,

I was looking to get the community's thoughts on this workflow  

We are considering generating our proxies through Davinci or Silverstack. We would then have to generate the database files manually inside the MXF folder. Once those database files are generated we will rename the folder to the shooting date.

Do you foresee any issues or downsides with this approach? If we run into any tech problems or anomalies, will this workflow hinder us being supported by Avid? 

Thanks.  

What is the general workflow? Offline in Avid and finish in Resolve?

That's correct. 

Philip Kapadia:

Hi, 

Why would you want to organise your Avid Mediafiles database?

I would just transcode in resolve then consolidate those MXF's into Avid. 

Note avid nowadays can manage both OP-Atom media and OP1a within it's Avid Media Files folder structure. 

We have two teams working in different locations so after changing the folder name we send those proxy files to the other remote team while we work locally.  Naming the Nexis media folders just helps manage that process. That's the thought at least.

Sounds like you recommend using Davinci instead of Avid to generate proxies. Is there any downside to this? I noticed in avid it is missing the media path for the files generated by Davinci. 

thanks  

the_rube:

we will rename the folder to the shooting date.

Do you foresee any issues or downsides with this approach?

No, as long as you use numbers only. As soon as you use anything else, MC won't have write access to that subfolder.

Philip Kapadia:

Why would you want to organise your Avid Mediafiles database?

I think the OP just wants to organize the mediafiles into subfolders per shooting day. Which is a very common practice. Personally, I even split sound and picture media, as it allows me to transfer all sound media to sound editorial, without consolidating, without having to send across picture media.

This workflow is fine. I also use it.

The benefit of renaming the folder once the database is set is that the folder remains free of render files and other stuff.

We use Contentagent for transcoding. Contentagent creates the database, so no scanning in Media Composer.

Dom Q. Silverio:

the_rube:

Hello,

I was looking to get the community's thoughts on this workflow  

We are considering generating our proxies through Davinci or Silverstack. We would then have to generate the database files manually inside the MXF folder. Once those database files are generated we will rename the folder to the shooting date.

Do you foresee any issues or downsides with this approach? If we run into any tech problems or anomalies, will this workflow hinder us being supported by Avid? 

Thanks.  

 

What is the general workflow? Offline in Avid and finish in Resolve?

 

Occasionally we will relink in avid to check shots that get resized to confirm focus but yes offline edit otherwise then final finishing in Davinci. 

Job ter Burg:

Philip Kapadia:

Why would you want to organise your Avid Mediafiles database?

I think the OP just wants to organize the mediafiles into subfolders per shooting day. Which is a very common practice. Personally, I even split sound and picture media, as it allows me to transfer all sound media to sound editorial, without consolidating, without having to send across picture media.

Oh ok fair enough