DVD FAB FOR MAC M1 Silicon Chips

[michaelc5280]

I've ripped Blu-Ray on the M1. Standard H264 at 1080p encode took ~1 hour. H265 is 18+ hours. I have not seen a difference in processing speeds between a MacBook Pro 2.6Ghz Intel i7 and the M1 Mac mini. DVDFab is the only SW I've used that doesn't show performance differences with my MacBook Pro.

[winna]

To simplify things, I turned off autoplay for DVDs when loaded. But I've processed quite a few discs, and it's working great. And the M1 chip is BLAZING FAST at encoding.

What about Blu-Ray?
At least a Rosetta 2 version should be up and running. I'm not punching the BD ripper until it's sorted

[darin4628]

To simplify things, I turned off autoplay for DVDs when loaded. But I've processed quite a few discs, and it's working great. And the M1 chip is BLAZING FAST at encoding.

[signals]

darin4628 Good detective work and thanks for the valuable feedback. Overly aggressive protection also exists in the pc world, it is called Windows 10.

[darin4628]

I think I might be onto something. I changed the startup disk security settings on my Macbook Air and changed from Full Security to Reduced Security. I then checked BOTH of the options for extensions - Allow User Management and Allow Remote Management. (I tried just checking the first, but it still didn't work.) After rebooting, I then loaded a disc with DVDFab closed. If it was open, it would lock with DVD Player trying to grab the disc at the same time that DVDFab tried to read it. After DVD Player automatically opened, I closed it, then opened DVDFab. At this point, it read the disc and was able to process. I'm still testing, but so far, so good...

[winna]

I need a working Apple Silicon M1 version now please!!

[dansjk]

Looks to me like it's both a m1 vs. Intel issue and a Big Sur (macOS 11) issue. Big Sur seems to block the installation of third party drivers by default - which is how DVDFab is able to circumvent copy protection. So potentially they need to resolve that side of things before re-writing the application to be Apple silicon native. As once the driver side is resolved, it should be possible to run the Intel version on m1 via Rosetta 2.

Is there anyone out there with an Intel-based mac running Big Sur that can either confirm or deny this theory?

[Mona]

Hi guys, the developer needs more time to address the issue.

[winna]

Any update to this issue? - have a M1 Mac mini that does not work with latest Mac OS software. Will not get past the repair screen without failing?

Like this?

[JeffH5]

Any update to this issue? - have a M1 Mac mini that does not work with latest Mac OS software. Will not get past the repair screen without failing?

[winna]

Yeah it's time for M1 support! My Mac Mini M1 is waiting!

[martythebrit]

I was asking for the same thing a while ago, I have an M1 MBP, hopefully it will happen...

[darin4628]

Yes, thank you, Mona. And thank you, dsscolumbia for starting the thread. I'm having the exact same issue. I just got a new Macbook Air and had read about how much faster it is supposed to be processing video, but didn't realize that the M1 chip was not yet supported. I look forward to when that happens!

[dsscolumbia]

Thanks for the update MONA. It would be great to have a fix for this soon!

[Mona]

Hi there, sorry for the trouble. The developer needs some time to check out the issue, please kindly wait, thanks.