easyDCP plugin doesn't work on v17.4.6 Mac Studio M1 Max

Tried to convert 2K 90 minutes ProRes 4444 to DCP (interop, encrypted), after 90% progress it was just stop. Tried 3 times already, same thing happened after 90% progress it just hang/stop.
But it works on 10 minutes ProRes 4444 clips and 20 minutes ProRes 4444 clips.

DR 17.4.6
OS X Monterey 12.4
Mac Studio M1 Max

same problem on old macpro 2013, 17.4.6 dr studio release, big sur last update.
easydcp render job always fails. I tried also on different licensed workstations.
no support provided from bmd or fraunhofer :((

I found easyDCP export hung on a M1 mac mini nearly every time - some short films would work but no consistency to the hang timecode on these either. I had to migrate the license back to my older macbook pro where it worked fine just a bit slower.

Ive just got the mac studio M1 max last week and migrated the license back to that today and found the same issue with easyDCP on 17.4.6. I went through a lot of troubleshooting/testing with easyDCP and BM last time sending logs / debug on etc but no progress at all except BM say they will send to engineering - that was several months ago with no follow up. Ive chased up again today and will migrate back to the laptop again to export a DCP and will try to troubleshoot but the m1 mini was a brand new machine too just migrated my user environment but all latest OS and latest Resolve, same on the m1 max.
The m1 max is better than the m1 mini but neither are much better that my old 2009 mac pro 4.1 intel with 12GB Titan card that stopped working when Apple/Nvidia stopped working properly. Not really progress.

Hi all,

Unfortunately I have also problems with easyDCP plugin on MacBook Pro 2019 and Mac Pro 2013.
The problems appear from Early February 2022 after I updated Davinci Resolve Studio from 16 to 17.4.4.

Two types of problems:

1. Davinci Resolve Studio 18 from Apple app store the plugin not working at all!!!
When I use Davinci Resolve 18 (free version) from Blackmagic Design WEB the plugin works.

2. Randomly Davinci Resolve stop the rendering and write the message: "Timeout when waiting for frame xxxxx for recording, frame dropped."
It’s happened in all projects like 24 and 25 and 29.97 FPS. Stereo and surround.
It’s happened in different times in the timeline. When I export ProRes or MP4 from the same project it is working fine.
Also, I tried to make DCP with Kakadu JPEG 2000 and its work fine.

I wrote and sent data LOGs to easyDCP support already in February and did not receive a solution to the problems.

Hope someone will take responsibility for it.

Thank you.

updated dr18 studio from app store. same problem: failed to encode video frame. I think it's a no-nvidia gpu issue: macpro 2013 has 2x amd firepro d700. same problem on macbookpro 2017 intel graphics.
be careful, dr18 carries also issues with cinemadng image sequence: imported clips are half resolution sized in the media pool and they appear 'media offline' with red screen when selected. 18.0.2 update does not fix the problem.

Unfortunately easydcp plugin for DaVinci Resolve doesn't support Apple Silicon processor. I've confirmed this with 3 different M1 machines (Mac Studio M1 Max, Ultra, Mac Mini M1). All failed to export DCP using the latest DR version 17.4.6 and 18.0.4

No news or update from both companies.

Unfortunately easydcp plugin for DaVinci Resolve doesn't support Apple Silicon processor. I've confirmed this with 3 different M1 machines (Mac Studio M1 Max, Ultra, Mac Mini M1). All failed to export DCP using the latest DR version 17.4.6 and 18.0.4

No news or update from both companies.

Hey everyone, hope this helps but the solution is to open Resolve using Rosetta! If you go into the applications folder and click on Command+I (for Info) you'll get this window I attached below. Check off 'Open using Rosetta' and try to make a DCP again. This works for me and I got the info from a Blackmagic tech!

This is for Resolve 17, I've yet to upgrade to 18 yet so can't confirm that works with 18. If someone can confirm it does please let me know!

(scroll down on the image to see 'Open Using Rosetta') p.s. remember to turn it off when you're done.

Hi Fred,

Have you had a chance to check your Rosetta method on DR Studio v18.1?

Since easyDCP plugin is still not working on M1 Macs, I tried to render DCPs using built-in Kakadu JPEG2000 option and found out that DR Studio v18.1 doesn't output VOLINDEX.xml for DCPs for some reason (a DR bug most probably). SMPTE DCPs without VOLINDEX file seem to work and validate fine everywhere I've tried so far, but for InterOP DCPs I get validation errors in easyDCP Creator+ Package Validator (which I use for checking all my DCPs). Haven't tried InterOP DCPs in actual DCI projector yet, though.

Just wondering, how important is the VOLINDEX file, if the DCP is stored on a single disk volume? I know that it used to be important in the old days when DCPs sometimes were stored on several disks.

Best,
Kriss

Update:

I just tried the Rosetta method myself with DR Studio v18.1 on M1 Ultra Mac running Mac OS Monterey and it worked! I was able to render a DCP with easyDCP plugin for a feature length timeline without any issues.

Also, with easyDCP plugin, VOLINDEX file gets created as it should, so most probably there is bug with the Kakadu JPEG2000 DCP renderer in that aspect.

Fred, thank you for sharing the trick!

Best,
Kriss

Update:

I just tried the Rosetta method myself with DR Studio v18.1 on M1 Ultra Mac running Mac OS Monterey and it worked! I was able to render a DCP with easyDCP plugin for a feature length timeline without any issues.

Also, with easyDCP plugin, VOLINDEX file gets created as it should, so most probably there is bug with the Kakadu JPEG2000 DCP renderer in that aspect.

Fred, thank you for sharing the trick!

Best,
Kriss

Awesome, great to hear as I haven’t tried it on 18.1! Just a reminder to switch Rosetta off afterwards! I’ve had periods where I forgot and was using Resolve on Rosetta for like a month!

Hi Fred,

Have you had a chance to check your Rosetta method on DR Studio v18.1?

Since easyDCP plugin is still not working on M1 Macs, I tried to render DCPs using built-in Kakadu JPEG2000 option and found out that DR Studio v18.1 doesn't output VOLINDEX.xml for DCPs for some reason (a DR bug most probably). SMPTE DCPs without VOLINDEX file seem to work and validate fine everywhere I've tried so far, but for InterOP DCPs I get validation errors in easyDCP Creator+ Package Validator (which I use for checking all my DCPs). Haven't tried InterOP DCPs in actual DCI projector yet, though.

Just wondering, how important is the VOLINDEX file, if the DCP is stored on a single disk volume? I know that it used to be important in the old days when DCPs sometimes were stored on several disks.

Best,
Kriss

I am running into this issue as well - Intel iMac Pro - no VOLINDEX file created and the DCP fails QC check. It still played fine at one theater, but now for distribution to festivals, I need one that pass QC. Any idea if this worked in Resolve 17 ? (This is my first DCP in v18, never had issues before, but I can't recall if I was on 16 or 17 at the time...

it appears this VOLINDEX issue has been fixed in v18.1.3 - thank you BMD team!

it appears this VOLINDEX issue has been fixed in v18.1.3 - thank you BMD team!

Awesome! So no more having to run in Rosetta mode!?

no more having to run in Rosetta mode!?

Asked but not yet confirmed? Looking at pulling the trigger on a StudioMax.

JPO

no more having to run in Rosetta mode!?

Asked but not yet confirmed? Looking at pulling the trigger on a StudioMax.

JPO

I can confirm it still doesn't work. I have to run Resolve in Rosetta mode every time I make a DCP. Hope fully this is fixed soon!

Still only works for me under Rosetta on a Mac Studio (v18.1.4).