shawn butts
New Member
Windows and Linux get an update but not Mac?
Question / Help Where is version 21 for Mac
- Thread starter shawn butts
- Start date
Narcogen
Active Member
I believe the official Mac builds usually come a bit later.
I've done an unofficial MacOS build that may work for you. I usually post those in the General Development forum and in the OBS subreddit.
https://www.reddit.com/r/obs/comments/7solyy/unofficial_mac_build_of_obs_2101/
https://obsproject.com/forum/threads/unofficial-macos-build-of-21-0-1.80144/
There's a reply on that post that indicates a MacOS build is coming soon and was only delayed because of a Travis outage.
UPDATE: Just realized I posted the reddit link twice and omitted the OBS forum entry. Fixed.
I've done an unofficial MacOS build that may work for you. I usually post those in the General Development forum and in the OBS subreddit.
https://www.reddit.com/r/obs/comments/7solyy/unofficial_mac_build_of_obs_2101/
https://obsproject.com/forum/threads/unofficial-macos-build-of-21-0-1.80144/
There's a reply on that post that indicates a MacOS build is coming soon and was only delayed because of a Travis outage.
UPDATE: Just realized I posted the reddit link twice and omitted the OBS forum entry. Fixed.
Last edited:
shawn butts
New Member
it's been a number of days since 21 was released and still no official mac support. i appreciate all the work that goes into OBS and cross platform support. however, i am disappointed in how mac support is being handled.
what additional resources does the project need for mac build/development to be on-par with the others?
what additional resources does the project need for mac build/development to be on-par with the others?
TheStewart
New Member
Hey Shawn,
There will always be unexpected issues with technology. Had the team decided to delay the release for everyone because one platform was delayed, people on the other side would probably be unhappy.
We’ve waited this long for new features, I’m sure a week or so will go by quickly.
There will always be unexpected issues with technology. Had the team decided to delay the release for everyone because one platform was delayed, people on the other side would probably be unhappy.
We’ve waited this long for new features, I’m sure a week or so will go by quickly.
shawn butts
New Member
Sure, stuff happens.
But, how about an official explanation and setting expectations about when it might be delivered? Also, it would be nice if the team could provide suggestions for how the Mac community of OBS users could help.
But, how about an official explanation and setting expectations about when it might be delivered? Also, it would be nice if the team could provide suggestions for how the Mac community of OBS users could help.
So, breakdown of why things have taken so long:
First, the build service we use for Mac builds (Travis) was undergoing gigantic delay problems with several thousand build jobs queued up and builds taking hours and hours to complete. We use Travis to do builds because doing everything to get a proper build, including signing, is a pain to do manually. The Travis build is automated to do all of this for us, and at the time we weren't sure if it was worth trying to do by hand anyway, since we didn't know how long the backlog really was. This took several days to clear up.
In the meantime, we had to restart the build several times because we were having problems getting Python scripting working. For some reason, we weren't able to get the Mac to recognize local Python 3.6 installs. After some time of trying to get this working with no success, we decided that we should just ship without Python scripting support for now. Lua scripting still works fine.
However, right before we shipped, we noticed an issue with Qt themes not rendering correctly. Several default styles were not applying correctly and even "native" UI components were looking very ugly (like, Windows 98 ugly). We still have not figured out why Qt is not building or copying correctly on Travis to make these appear, as local unsigned builds seem to work just fine. Hopefully this issue will be resolved quickly and we can get v21 into your hands.
First, the build service we use for Mac builds (Travis) was undergoing gigantic delay problems with several thousand build jobs queued up and builds taking hours and hours to complete. We use Travis to do builds because doing everything to get a proper build, including signing, is a pain to do manually. The Travis build is automated to do all of this for us, and at the time we weren't sure if it was worth trying to do by hand anyway, since we didn't know how long the backlog really was. This took several days to clear up.
In the meantime, we had to restart the build several times because we were having problems getting Python scripting working. For some reason, we weren't able to get the Mac to recognize local Python 3.6 installs. After some time of trying to get this working with no success, we decided that we should just ship without Python scripting support for now. Lua scripting still works fine.
However, right before we shipped, we noticed an issue with Qt themes not rendering correctly. Several default styles were not applying correctly and even "native" UI components were looking very ugly (like, Windows 98 ugly). We still have not figured out why Qt is not building or copying correctly on Travis to make these appear, as local unsigned builds seem to work just fine. Hopefully this issue will be resolved quickly and we can get v21 into your hands.
shawn butts
New Member
Thank you for the explanation.
Narcogen
Active Member
My local build of v21 does not have that, at least not exactly. The MultiView feature works, and having that window open does NOT cause any FPS drop. However, with the MultiView window open, OBS still acts like a hot switcher-- when you choose a new input source, that source goes live immediately.
To have true Preview/Program window functionality, you still need to hit the Studio mode button-- and that still causes the FPS hit.
For a lot of people, this might not matter-- just being able to see the sources before selecting one may be enough.
Good news, the build is up. It should be available on the auto-updater soon, but you can download it directly here: https://github.com/jp9000/obs-studio/releases/tag/21.0.2
Last edited:
TheStewart
New Member
Oh, so close! Thanks for all the effort though. I know it’ll all workout eventually.
AskMP
New Member
Studio mode is still useless on MacOS after the update… I see your comment @Narcogen and appreciate it but as you said, any changes are hot changes effected to the live output.
https://www.dropbox.com/s/39mkrgf4bfd4f5n/Screenshot 2018-02-09 22.00.20.png?dl=0
I’ll still be using it on my PC and for Windows systems (FYI, OBS works great on a 2011 Macbook Air with Windows installed…). Thanks @dodgepong for the updates and the great detailed post on the delay purpose. It’s comments and decisions like that which I think we as a community truly can appreciate. Sure, it was delayed but you had a valid reason.
Studio mode performance on Mac is definitely a known issue, which this release unfortunately does not address. I'm not sure what the cause is, personally, but I can assure you that we are aware of it and will be looking at it. That isn't a promise that it will even be fixed in the next version -- just letting you know that we hear you.