I tried something else and I think I identified the problem.īy creating IN and OUT points, THEN dragging it on the timeline (from the viewer or from the media pool with the IN/OUT points on a clip), go to Fusion and attach the Mocha Pro node to it (then open it), the problem occurs. It repeats until I close the Mocha Pro window

| SyManager.Signals | INFO | 23:33:34,245 | Main view page is changed to 16ĬlientNode: failed to respond to message '-request-frame=9605': exception 'Message too large (10506240 > 1048576)'ĬlientNode: failed to respond to message '-request-frame=9605': exception 'Message too large | UI | WARN | 23:33:34,208 | UI Persistence - MediaPoolFloatingWindowGeometry not read | Fusion | INFO | 23:33:33,921 | Started FusionAudio Worker thread Part of the log from Davinci Resolve 17 b6 after launching Mocha Pro from the Fusion page (simple clip cut on the timeline) On I have tons of : UI | WARN | entries in the 'ResolveDebug.txt' and for UI.MenuBar tooĭec 22 23:37:50 (mochaPro_plugin) Commenced logging at Tue Dec 22 23:37:50 2020ĭec 22 23:37:50 (mochaPro_plugin) Plugin host id: ''ĭec 22 23:37:50 (mochaPro_plugin) Plugin host type: BlackMagicĭec 22 23:37:50 (mochaPro_plugin) Build Date Dec 5 2020ĭec 22 23:37:50 (mochaPro_plugin) Version 8.0.1 build 101.g903c26329626 win_x86_64.ĭec 22 23:37:50 (mochaPro_plugin) Windows 10 64-bitĭec 22 23:37:50 (mochaPro_plugin) TaskManager initialised (11)ĭec 22 23:37:50 (mochaPro_plugin) : initialised with licence dir C:/ProgramData/GenArts/rlmĭec 22 23:37:50 (mochaPro_plugin) Locale: defaultĭec 22 23:40:10 (mochaui) => Unknown errorĭec 22 23:40:10 (mochaui) Context: Unknown errorĭec 22 23:40:10 (mochaui) Message: Unknown errorĭec 22 23:40:14 (mochaui) => Unknown errorĭec 22 23:40:14 (mochaui) Context: Unknown error It still works with Fusion 17 beta 5 (so I won't install the beta 6).Īnother question, is it a problem going back to Resolve Beta 5 from the beta 6? So it doesn't look like it's a problem from the plugin itself (or is it?).

I'm asking here because it worked well on all the previous beta of Resolve v17. I uninstalled mocha, and installed it again, same thing. I didn't have the problem with the beta 5, and there was not change in my graphics card drivers or anything since. Is someone here having an ' unknown error' from Mocha Pro 8.01 (OFX) with Resolve 17b6?

Mocha pro ofx