Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running sm on macOS - cannot be opened because the developer cannot be verified #1

Open
gitizenme opened this issue Apr 27, 2021 · 2 comments

Comments

@gitizenme
Copy link

image

image

@Boscop
Copy link
Owner

Boscop commented Apr 28, 2021

Yeah, when I checked with virustotal I also saw that some antivirus softwares warn about it, so I did a little research, and found that often pyinstaller-created executables are falsely detected as virus based on some heuristic.
Which is why I added this to the Readme:


Note: If you get a warning from your antivirus software about the file ShaderBoi/spatialmedia/sm, it's a false positive. (This file was created by pyinstaller from a python script to make it work without python, it's purpose is to add spatial metadata to the recorded video files. If your antivirus software removes this file, ShaderBoi still works, but cannot add spatial metadata to the 360° videos that you render with it. You could add the metadata manually though.)


I used pyinstaller so that it doesn't require python to be installed (a large part of the target audience is people using Windows).
Btw, sm is only needed when you render 360° videos. ShaderBoi works fine without it.
And if you actually render 360° videos, you can also use the python script directly:
https://github.com/google/spatial-media/tree/master/spatialmedia#inject

E.g. python spatialmedia -i rec.mp4 for non-stereoscopic or python spatialmedia -i --stereo=top-bottom rec.mp4 for stereoscopic. (And if it also contains ambisonic audio, add --spatial-audio.)

@Boscop
Copy link
Owner

Boscop commented Apr 28, 2021

What I could do is: For the linux and mac builds, include the python script (at spatialmedia/sm.py), and assume that python executable is installed on the user's machine and then invoke that. And only use pyinstaller for the windows build.
What do you think about this solution? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants