4 ms·

Why can zoom block a virtual camera? Couldn’t the virtual camera just pretend to be like any other real camera?

• whywhywhywhy 6y ago
  It's seemingly a MacOS Code Signing limitation. https://github.com/johnboiles/obs-mac-virtualcam/issues/4 https://github.com/johnboiles/obs-mac-virtualcam/issues/4
  • jiveturkey 6y ago
    optional restriction, not limitation.
    • comex 6y ago
      The limitation is that CoreMediaIO plugins still run in-process (and not just in some daemon but in arbitrary application processes!), when Apple's direction for over a decade has been to move all plugin mechanisms towards an out-of-process model. There's nothing about video plugins in particular that would prevent them from being out-of-process; in fact, most of Apple's CoreMediaIO plugins already have the bulk of the logic in a separate "assistant" process, but the IPC layer is reimplemented by each individual plugin rather than being done generically by CoreMediaIO itself. It's clear what has to happen, but Apple hasn't done it yet.
• galad87 6y ago
  Because an app can disable loading libraries/plugins signed with a different developer id certificate, and it seems Core Media IO wants to load the plugin in the actually app process, and it doesn't use an helper process.
• sschueller 6y ago
  This is the downside of a walled garden and locked down devices. Of course many will say its for security and its wonderful but how much freedom are you willing to give up for security?