Problems Capturing Video to Drives

Hi Everyone,
I just got up and running with DR Studio 17 Beta 8 after the release of Nvidia's new video driver. I have been editing several projects and the new version is really amazing. Today I needed to capture some standard definition VHS video and up-scaling through our BMD Teranex AV to 1920 x 1080 29.97 Progressive. I first downloaded Beta 9 and rebooted before doing so.

I can't seem to capture to any of my drives. I have a hardware raid by ATTO with 10.4TB free of 13.6TB (Drive Z). These are spinning Hitachi drives RAID 5. I also have 692GB free of 3.72TB using Samsung Pro 1TB SSDs (Drive X). I also have an NVRAM drive with 500GB that is fully empty that I usually use as a cache drive (Drive W) and can't write to that either.

I stepped back to Beta 8 and it gives me the same message. " Resolve could not write to the selected storage device. Please make sure you have enough free space on selected storage device."

Attached is the dialog message as well as my media storage page for reference.

Resolve Can't Write dialog.png (15.85 KiB) Viewed 929 times

Media Storage Drives.png (44.26 KiB) Viewed 929 times

My other system is still running DR16. It is piped into the same Teranex AV and I forunately can capture via that system.

Any help would be greatly appreciated.

Best wishes,
Bjarne

Could be a bug that will have to wait for an update.

[Dwaine Maggart]

Can you save a Project Export .drp file to any of those drives?

Hi Dwaine,

Yes, I can export a project (.drp) file to any of these drives.

Bjarne

[Dwaine Maggart]

Then I'm baffled by the error message.

Please send a Resolve log and system info NFO file.

Hi Dwaine,
I don't know what to say. Before trying to send you a Resolve log and system info NFO file, I thought it would be best to revert up to Beta 9 first. And, to confirm, retry capturing video to reproduce the issues. And amazingly enough everything now works. This was just after trying several times over the last couple of days and several reboots to make sure that the issue was valid. It's the Trons. Something was going on, I just don't know what.
Bjarne