Closed sbscomp closed 3 months ago
Hi, please see #2178 for possible solutions
Re-signing the package does seem to resolve the issue here on my desktop, but feels like a hacky fix. I saw that one thread was referring to switching to a signed dependency, is that what's needed here, so that there's no need to re-sign every M3 update?
@sbscomp, yeah, we'd need to pay monthly in order to get M3 officially signed unfortunately...
@sbscomp, yeah, we'd need to pay monthly in order to get M3 officially signed unfortunately...
Can you email me (my email is on my profile) in more detail on that point? I'd be willing to see if I can help with this if it can help avoid this problem (or others).
Yeah, I wouldn't mind pitching in some dollars if it means getting M3 signed and notarized. It's around $90 a year right?
I believe it's $99 a year for a developer account. Google's is $25 one-time fee. If you want to register it under an organization name, there's some additional verification requirements, but no additional cost.
An Apple developer account is $99/year and a code signing certificate for Windows applications is about $130/year
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bump
So, circling back on this, do you feel comfortable with me starting the process for getting a developer account set up? I would be registering under my business name (registered in Illinois, USA) unless you have another preference here, and then setting up one or more of you as additional developers so you could manage releases etc.
So, circling back on this, do you feel comfortable with me starting the process for getting a developer account set up? I would be registering under my business name (registered in Illinois, USA) unless you have another preference here, and then setting up one or more of you as additional developers so you could manage releases etc.
If I can chime in here: I really appreciate this offer. Thank you for your generosity! However, I'm not sure that I would feel comfortable with this.
Times have truly changed since the inception of M³ many years ago. JWL's featureset keeps steadily improving! The recently released playlist feature in JWL is very nice, and frankly obviates one of the main reasons why M³ came to be, that is: displaying custom media at the KH.
I honestly see the M³ project eventually fizzling out and becoming more of a niche app, helping out in the ever-rarer scenarios where JWL isn't quite perceived as feature-complete yet. I've listed below a few of these scenarios, where JWL features are perhaps functional but complicated to use, or not implemented at all; honestly however, the list keeps shrinking.
If the above-mentioned points are the only ones that JWL can't do 'properly' or 'simply' for the moment, I would find it hard to justify pouring resources (and even time) into adding more features to M³. I'd rather think that analyzing how to patch the perceived holes in the current featureset of JWL would be the way to go, as we use JWL more and more as time goes on ,and consequently use M³ less and less.
@mtdvlpr Perhaps my view is one-sided. Thoughts?
I can add one more point to that list: The macOS version of JWL is straight up the mobile version rather than a proper desktop app, and thus has no capability at all to display media on a second monitor.
I would add that the M3 is very stable, hardly causes crashes and the automatic sharing feature between OBS Studio + Zoom Meeting, becomes very practical, not to mention when a video ends, it is nice that the camera image returns automatically without the need to do some intervention.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What happened?
In the latest version of MacOS, when sharing the M3 media desktop over zoom, the OS prompts multiple times (possibly once for each "microphone device") to allow M3 access to the microphone. Both M3 and Zoom are already in the microphone privacy allowlist.
I was able to reproduce this on a clean install on my personal mac (which has never had M3 installed on it).
To Reproduce
Observed Behavior: MacOS prompts multiple times to allow Meeting Media Manager to use the microphone.
What did you expect to happen?
I would expect to be prompted the first time on a clean install, but after that, sharing music/video over zoom should not prompt.
Version
v23.8.1
What platform are you seeing the problem on?
MacOS
Relevant log output
Screenshots
The video recording is 269 MB, so I'm sharing it here as a onedrive link:
https://1drv.ms/v/s!AppW0rDGiAG_gqhOIhztkpP4Z-skeA?e=zbiirt
Additional context
This problem does not occur under MacOS 13.x. It only started with the upgrade to MacOS 14 Sonoma.
I ensured I'm using the latest Zoom 5.16.2 (23409) on both my local desktop and our KH Mac.