Blackmagic Forum

Is someone here having an "unknown error" from Mocha Pro 8.01 (OFX) with Resolve 17b6?
I didn't have the problem with the beta 5, and there was not change in my graphics card drivers or anything since.

I uninstalled mocha, and installed it again, same thing. And the window of mocha is very slow.

I'm asking here because it worked well on all the previous beta of Resolve v17. So it doesn't look like it's a problem from the plugin itself (or is it?).

It still works with Fusion 17 beta 5 (so I won't install the beta 6).

Another question, is it a problem going back to Resolve Beta 5 from the beta 6?

Thanks

PS.
On I have tons of : UI | WARN | entries in the "ResolveDebug.txt" and for UI.MenuBar too
---
The logs form Mocha Pro
Dec 22 23:37:50 (mochaPro_plugin) Commenced logging at Tue Dec 22 23:37:50 2020
Dec 22 23:37:50 (mochaPro_plugin) Plugin host id: 'com.blackmagicdesign.Fusion'
Dec 22 23:37:50 (mochaPro_plugin) Plugin host type: BlackMagic
Dec 22 23:37:50 (mochaPro_plugin) Build Date Dec 5 2020
Dec 22 23:37:50 (mochaPro_plugin) Version 8.0.1 build 101.g903c26329626 win_x86_64.
Dec 22 23:37:50 (mochaPro_plugin) Windows 10 64-bit
Dec 22 23:37:50 (mochaPro_plugin) TaskManager initialised (11)
Dec 22 23:37:50 (mochaPro_plugin) [RepriseLicenseManager]: initialised with licence dir C:/ProgramData/GenArts/rlm
Dec 22 23:37:50 (mochaPro_plugin) Locale: default
Dec 22 23:40:10 (mochaui) ===> Unknown error
Dec 22 23:40:10 (mochaui) File::0:
Dec 22 23:40:10 (mochaui) Context: Unknown error
Dec 22 23:40:10 (mochaui) Message: Unknown error
Dec 22 23:40:14 (mochaui) ===> Unknown error
Dec 22 23:40:14 (mochaui) File::0:
Dec 22 23:40:14 (mochaui) Context: Unknown error

Part of the log from Davinci Resolve 17 b6 after launching Mocha Pro from the Fusion page (simple clip cut on the timeline)

[0x000039ec] | Fusion | INFO | 2020-12-22 23:33:33,921 | Started FusionAudio Worker thread
[0x00003f1c] | UI | WARN | 2020-12-22 23:33:34,208 | UI Persistence - MediaPoolFloatingWindowGeometry not read
[0x00003f1c] | SyManager.Signals | INFO | 2020-12-22 23:33:34,245 | Main view page is changed to 16
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)'
ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large

It repeats until I close the Mocha Pro window
---

Windows 10 64 (latest version)
Radeon RX Vega 56 (latest drivers)
AMD 3900x

I tried something else and I think I identified the problem.

By 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.

IF I just drag the full video file on the timeline, THEN cut the part I need directly on the timeline, go to Fusion... it works and there is no error.

The same thing if I create a compound clip (in both ways)

So I guess it was always a problem before but I never saw it because I generally do my "cuts" from the timeline, and I never went to fusion (fro Mocha Pro) with a clip "created" from IN/OUT points, and dragged on the timeline.

It could be the source of other problems with Fusion/OFX plugins etc?

I'm not an expert but : ClientNode: failed to respond to message '--request-frame=9605': exception 'Message too large (10506240 > 1048576)' << It looks like the plugin gets something different than the images frames he should get... as if something is out of range.

But then, Mocha is not officially blessed for Resolve. You can use its shapes and masks in Fusion, though.

Uli Plank wrote:But then, Mocha is not officially blessed for Resolve. You can use its shapes and masks in Fusion, though.

It still could be a problem coming from Resolve's side, that's why I'm posting this, because I don't know

Hi,

I would really appreciate if the Mocha plugin would be officially supported by BMD...

Trying to use Mocha in the Fusion tab also leads to the "Unknown error" displayed by Mocha. Trying to use Mocha in the Edit results in another problem (which can be easily reproduced):

- DVR 17 public beta 7
- Mocha plugin 8.0.1 (build date Dec 5 2020)
- Apply Mocha as OFX effect on the edit timeline
- Use the "insert" feature in Mocha
- Set "Render / Module" to "Insert: Composite" in the inspector
- When playing the clip the video output flashes between the original image, a white screen and the correct output - quite soon DVR will just quit

Jens

It is a problem that Davinci does not work well with Mocha, I have tried in the edit tab and it also happens to me about the blinking in white, in the color tab the same thing happens and in the fusion tab it crashes instantly. it is a major disadvantage compared to its competitors.

Seconded. There are tasks which can be tackled by Mocha only (or even more expensive tools).