I did 4 benchmarks, one for Big and Sentinel on the internal SSD. Big did it at 17fps, Sentinel at 11fps. I did another one for Sentinel on my Promise R4 raid0. As for fps, there was no difference with SSD. I did a 4th Sentinel benchmark, with the source on SSD and the DCP output to the external raid. That turned out to be slower at 10fps. Not sure if these are even useful comparisons, but I was kinda curious myself.
I just downloaded version 2.15.149 and am attempting to transcode a DCP from a 1080p MKV on my MacBook Air w/ M1 chip.
Previous test version worked on this machine, but new test version is crashing with as soon as I start the encode process. Tried adjusting color range and JPEG200 bandwidth settings. Also adjusted number of threads. Still crashes as soon as "Make DCP" button is clicked.
Detailed crash report is attached to assist with development:
Thank you very much for the bug report!
I made a note on the tracker and I'll take a look as soon as I can.
I’ve take a look through a few threads, including this one to try to work out if the newest alpha version might be stable enough for production (I mean, I know it’s an alpha version).
I’m looking at getting a newer Mac Mini to help with making DCPs, either as a standalone unit or as an additional server to chain with my main machine.
Does the current stable version run reasonably on the M1, too?
If I used the latest Alpha on the new M1 silicon as a processing server, would I be able to use the current stable release on an older Mac as the master, or do I need to use the same version on both machines?
Thanks for your time!
I don't personally have an M1 machine but reports suggest that 2.15.x works fine. 2.14.x will only run via Rosetta.
Unfortunately if you want to use 2.15.x on an encoding server you would also need to upgrade your master.
Do the alternate columns/stripes suggest a frame per second each, or is it intentional to have a relative but not numeric representation?
...or is it just an overlook?