[Roy Gilbert]

I have a Ryzen 3700x and don’t have this issue.

It’s more likely to be a drive problem than a CPU problem. Have you tried putting the project files on a separate drive to the OS and media?

[Roy Gilbert]

This is really helpful thank you.

So I could rename the 1 folder at the end of each day to, for example, 30052020, and then copy that to the external drive.

I’ll probably be working with 1080p DNxHR low bandwidth, so less than 5MBps, so I think a mirrored 7200rpm HDD should be fine. I think the read speeds are twice as fast as a single HDD.

Would SSD media drives make a big difference to responsiveness? I have a 1tb ssd, maybe it’s worth using that somehow-maybe for waveform cache? Obviously the project will be on an ssd.

I could stretch to a couple of 1TB SSDs, but I’ll need to see how much footage they are going to be sending me.

Thanks again for your help!

[Roy Gilbert]

Thanks for the reply Ricky.

I’ll be getting a lot of new archive, and probably new rushes throughout the project and re-transcoding everything into DNxHR could definitely take a few days if my raid array was lost – which would be a massive problem the day before delivery or a commissioner viewing.

I’m also worried about things like scratch voice over recorded directly into Avid – the only way to back that up would be to back up the Avid Mediafile folders.

I’m thinking maybe I could create new subfolders inside the Avid Mediafile folder each day, so all new media will go in there, making it easier to back up. Would this work? Can I just increment the folder numbers – assuming avid uses the highest number for new media?

Obviously I’ll back up all new source media coming in as you suggested, and copy those across to the external back up as well.

[Roy Gilbert]

Wow, amazing work. Thanks for that!

[Roy Gilbert]

Same problem with mine. Ridiculous really. No solution I’m afraid, just lots of blue screens when I knock the case.