FabioCarpi
Member
i have installed but nothing different shows in OBS
Hi @FabioCarpi,i have installed but nothing different shows in OBS
I've created a pull-request to OBS-Studio. I hope it will be merged and improve the performance on macOS.OBS on Macs especially is known to have lesser performance than DirectX based Windows compositor, so any optimizations here are more than welcome ;)
This is a minor release of OBS Color Monitor.
Changes from the last release are
- Added dock widget
- vectorscope:
- Changed default graticule color to amber.
- Changed default graticule style.
- Changed default skintone line (very small change).
Since the dock is a new feature requiring a lot of implementation, consider to use 0.1.7 just in case if something is wrong on your system.
When trying to install on Mac OSx 10.15.7, I get the error "“obs-color-monitor.so” cannot be opened because the developer cannot be verified." when launching OBS 27.0.1 Plugin does not appear anywhere in OBS. I have confirmed that the plugin is installed according to the info in #13 above. Any suggestions on what else to try?
Thank you for letting us know the solution. I think each user need to run that command so far. I'm sorry for your inconvenience. macOS 10.14.5 or later requires the developer to notarize the binary code. However, it requires to buy mac which can run macOS >=10.13.6 and subscribe Apple Developer Program. I'm preparing the fund but will take more time.solved with:
xattr -d com.apple.quarantine /Library/Application\ Support/obs-studio/plugins/obs-color-monitor/bin/obs-color-monitor.so
This is a minor release of OBS Color Monitor.
Change in this release is
There are no changes for Windows and linux.
- Notarized macOS binary file.
I subscribed Apple Developer Program and released a new version 0.2.2 with notarization. I hope this version fixed the issue.When trying to install on Mac OSx 10.15.7, I get the error "“obs-color-monitor.so” cannot be opened because the developer cannot be verified." when launching OBS 27.0.1 Plugin does not appear anywhere in OBS. I have confirmed that the plugin is installed according to the info in #13 above. Any suggestions on what else to try?
I’m sorry for your issue.I'm currently getting an instant crash of OBS after startup completes with the latest version of the plugin. See the attached logs from macOS 10.15. Earlier today I adjusted the (for me) new scope dock a little (made it wider to see better). I don't think it crashed right away but I closed OBS shortly after to fix an unrelated image transparency issue. Now I can't successfully start OBS unless I remove the plugin. Hopefully, the logs help.
Thank you for the reply, I might indeed use 0.1.7 for now. I'm unable to find out how to revert the settings for docks, otherwise, I could see if the defaults are working fine.I’m sorry for your issue.
I think something is wrong with the dock widget but the same issue is not happen on my side, maybe because I’m using different OS.
Until the fix is available, I’d like to suggest to use the old version 0.1.7, which does not include the dock.
Could you provide a current log file to solve the problem?Hi, that is great! I want to use this on my MacBook pro. I tried, installed as directed, but it does not appear in the sources list. Thanks!
1. I'm considering the zebra... Do you prefer to have zebra on ROI (region of interest) view or adding another view dedicated for zebra?1. Zebra pattern support
2. Color monitor overlay support in OBS multiview fullscreen, and being able to pick which scene in the multiview has the color monitor applied.
This is a minor release of OBS Color Monitor.
Changes in this release are below.
- waveform and histogram
- Add an option to display YUV levels.
- dock
- Improved performance by transfering frame data from GPU at once for all scopes (vectorscope, waveform, histogram) in a dock. Due to this change, scale of each scope is removed.
- Interleave to transfer frame data to reduce rendering time.
- Added ability to choose different scenes and sources. Open...
Thank you for the update! I can confirm the bugfix removed the issue on my end :)