![]() ![]() This change however would be something some macOS developer needs to be willing to introduce/maintain, but I see it as inevitable. originally refrained from using this as it would make running OBS/virtualcam without a bundle impossible.Īs we need helper app bundles for CEF anyway and an app of OBS' complexity should (IMO) never be run as a lone binary to begin with, I wouldn't mind requiring an app bundle for more advanced features such as browser sources or virtual webcams. The proper way to do this would be to use an NSXPCConnection which also requires a helper process in the OBS bundle. ![]() But I am not familiar with Mach communication or alternatives. The fact that the entitlement name includes the string "temporary-exception" suggests that Apple would like apps to phase out the use of this method in favor of something else. I wonder if there is an alternative method of communication that the OBS Mac VirtualCam plugin could use that does not involve Mach ports. I tried adding and re-signing, but then that copy of FaceTime would not launch ("You do not have permission to open the application"). I also tried adding it to a copy of FaceTime.app, which already has -name set to a list of the 33 Apple Mach ports that it is allowed to talk to. Assuming I re-signed correctly, that didn't make a difference. I tried re-signing OBS.app adding -name to the entitlements as an array with one element, (that's MACH_SERVICE_NAME). So my guess is that whatever restrictions FaceTime is putting on its code, such as maybe using the hardened runtime, prevent the OBS Mac VirtualCam plugin from doing its internal Mach communication. Another third party DAL plugin,, works fine in FaceTime and Photo Booth. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |