Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I guess you meant MacBook Air 2019 :)
If I was you, unless I had a very specific need, I'd keep Sonoma as it is currently supported by Apple.
Oh, yes I meant 2019 :)
Ok, thanks for your reply! I'll keep Sonoma and look from time to time on the ocpl git.
Thanks!
 
Hi all, I have run into some unusual problems after upgrading from Monterey to Sequoia 15.2. While the install was fine and the mac runs fine, I had issues with the Apple TV and Music apps, they usually popup a window with a notifications button on launch. This time i got the window but it said cannot connect, so I clicked cancel. I want to get the window back so I can grant the TV permission to send notifications, but it won't come up again, even after clicking on reset warnings and clear cache under the advanced settings.

I used a USB with OCLP 2.2.0 to upgrade, and this usually works fine for me. So is there a way I can get the TV app to ask to send notifications again? Thanks
iMac 17,1.
 
Hi all, I have run into some unusual problems after upgrading from Monterey to Sequoia 15.2. While the install was fine and the mac runs fine, I had issues with the Apple TV and Music apps, they usually popup a window with a notifications button on launch. This time i got the window but it said cannot connect, so I clicked cancel. I want to get the window back so I can grant the TV permission to send notifications, but it won't come up again, even after clicking on reset warnings and clear cache under the advanced settings.

I used a USB with OCLP 2.2.0 to upgrade, and this usually works fine for me. So is there a way I can get the TV app to ask to send notifications again? Thanks
iMac 17,1.
Which Mac? You haven't write the mass versions to your signature
 
Which Mac? You haven't write the mass versions to your signature
Problem resolved. I did a clean install of Monterey set it up, then upgraded again to Sequoia 15.2 and everything is fine now. iCloud went wonky for some reason.
As far as which Mac, I mentioned it's an iMac 17,1 which is a late 2015, 27" 5K. I don't think I'm going to try and dual boot macOS anymore, unless they're all supported versions. I installed Mojave, and Monterey on APFS volumes prior to upgrading the main install of Monterey to Sequoia earlier and even though I never logged either of the other installs into iCloud, OR my Apple ID period. I still got the "this Mac can't connect to iCloud" message. That's when things started acting funny. Either way, seems to be OK now, will let it run overnight with just the base OS before restoring my backup, to see how it holds up. The other issue I had when this iCloud stuff acted up was my Time Machine backup broke with the error that Time Machine couldn't backup because stuff was still syncing with iCloud. I'd never seen that either on supported or OCLP. So, I guess it just needed a clean start, and didn't like the dual boot setup.
 
  • Like
Reactions: Steve Gosselin
Just today I found there is no Wifi Icon on top menubar on Sequoia 15.1, how can I resolve it?
 

Attachments

  • NoWifiIconOnMenuBar.png
    NoWifiIconOnMenuBar.png
    15.2 KB · Views: 15
  • Sonoma14.7.png
    Sonoma14.7.png
    42.9 KB · Views: 15
Hey all, is the 1080p YouTube limit in Safari, a safari limitation, or is it OCLP related? I don't usually use Safari, but I haven't restored Firefox from backup yet, and just happened to notice videos only go up to 1080 60fps max. I do remember when running under Monterey, Safari didn't limit YouTube videos. As mentioned though Safari isn't my primary browser, never has been. it's just something I noticed and wondered where the limitation is since it hasn't been limited in several years. Thanks.

EDIT: Come to think of it, I think Safari played 4K video under Sonoma and Ventura as well, even when trying it under OCLP on this late 2015 iMac. 17,1.
 
Last edited:
MBA 7,2 upgraded to 15.2 OTA from 15.1.1, OCLP 2.2.

Capture d’écran 2024-12-21 à 12.24.30.png


Performance very slightly up, within noise range as always since 10.15
GB6 (multi-score) • 1708 (15.2) <- 1706 (15.1) <- 1690 (15.0) <- 1705 (14.6) <- 1709 (14.0)
GB5 (multi-score) • 1428(15.2) <- 1424 (15.1) <- 1421 (15.0) <- 1395(14.6) <- 1422 (10.15.7)
 
Hey all, is the 1080p YouTube limit in Safari, a safari limitation, or is it OCLP related? I don't usually use Safari, but I haven't restored Firefox from backup yet, and just happened to notice videos only go up to 1080 60fps max. I do remember when running under Monterey, Safari didn't limit YouTube videos. As mentioned though Safari isn't my primary browser, never has been. it's just something I noticed and wondered where the limitation is since it hasn't been limited in several years. Thanks.

EDIT: Come to think of it, I think Safari played 4K video under Sonoma and Ventura as well, even when trying it under OCLP on this late 2015 iMac. 17,1.
Going over 1080p on Safari requires a GPU with VP9 hardware acceleration, which means Kaby Lake or AMD Polaris.

Safari only uses codecs that can be hardware accelerated, which in this case is h264 only and YouTube's maximum resolution for the codec is 1080p. Other browsers use software rendering for VP9/HEVC/AV1 and allow higher resolutions but with the tradeoff of higher CPU usage.
 
Going over 1080p on Safari requires a GPU with VP9 hardware acceleration, which means Kaby Lake or AMD Polaris.

Safari only uses codecs that can be hardware accelerated, which in this case is h264 only and YouTube's maximum resolution for the codec is 1080p. Other browsers use software rendering for VP9/HEVC/AV1 and allow higher resolutions but with the tradeoff of higher CPU usage.
I'm a bit confused with that response. I understand what you're saying. However, Safari 17.6 under Monterey on the same machine went over 1080p for YouTube, and it's only one version difference. That's why I was curious if Apple changed something between 17 and 18. The iMac has an AMD GPU. R9-M395 if I am correctly pulling from memory. It's a SkylLake core i5 Quad core. I do know certain 4K related playback requires newer Kabylake or newer, but I don't think YouTube was one of those. That was more commercial content such as streaming services and 4K Blu-ray as far as I remember. Like I mentioned, I don't watch YouTube in safari often, but when I did try it in Ventura and Sonoma, with past versions of Open core on the same iMac, I believe I got 4k.
 
I'm a bit confused with that response. I understand what you're saying. However, Safari 17.6 under Monterey on the same machine went over 1080p for YouTube, and it's only one version difference. That's why I was curious if Apple changed something between 17 and 18. The iMac has an AMD GPU. R9-M395 if I am correctly pulling from memory. It's a SkylLake core i5 Quad core. I do know certain 4K related playback requires newer Kabylake or newer, but I don't think YouTube was one of those. That was more commercial content such as streaming services and 4K Blu-ray as far as I remember. Like I mentioned, I don't watch YouTube in safari often, but when I did try it in Ventura and Sonoma, with past versions of Open core on the same iMac, I believe I got 4k.
This has been tested by multiple people, YouTube is limited to 1080p with AVC/h264 codec and that's all your GPUs support. Polaris is a codename for Radeon RX 400-500 series. You can check YouTube's technical info by right clicking the video and see that on Safari it is using "avc1" compared to different codecs ("vp09" or "av01") on 3rd party browsers.

Basically to go higher than 1080p on Safari you need a 2017+ Mac.

Either you remember wrong or if it truly did go higher, Safari used a different codec with software rendering for some reason (due to some bug maybe) which is not normal behavior for it, as it always utilizes hardware acceleration.
 
Last edited:
  • Like
Reactions: macpro_mid2014
This has been tested by multiple people, YouTube is limited to 1080p with AVC/h264 codec and that's all your GPUs support. Polaris is a codename for Radeon RX 400-500 series. You can check YouTube's technical info by right clicking the video and see that on Safari it is using "avc1" compared to different codecs ("vp09" or "av01") on 3rd party browsers.

Basically to go higher than 1080p on Safari you need a 2017+ Mac.

Either you remember wrong or if it truly did go higher, Safari used a different codec with software rendering for some reason (due to some bug maybe) which is not normal behavior for it, as it always utilizes hardware acceleration.
@Neon Ball I'm not making this post to pick a fight, but simply present evidence that there is information that seems to be not fully correct. I wasn't going to respond unless I could upfront prove I get 4K video from YouTube on Safari with this iMac. Here is a screenshot showing this iMac does support above 1080p for YouTube on Safari. The information you provided may be Apple's requirements for later versions of macOS / Safari, or it could be an OCLP limitation. However, as I originally mentioned, I primarily use Firefox or Chrome, so Safari is a moot point for me. However, I am providing feedback that my original hunch was still correct, and I am Able to get safari to play 4k YouTube Videos natively.
 

Attachments

  • Screen Shot 2024-12-21 at 9.45.03 AM.png
    Screen Shot 2024-12-21 at 9.45.03 AM.png
    1.5 MB · Views: 13
  • Like
Reactions: olad
For the record, my Macmini6,2 (Late 2012, quad-core i7) is running Sequoia 15.2 flawlessly, thanks to OCLP v2.2.0. That little 12-year-old mini just won't quit — and it even drives a 4K display! (At 30Hz, thru the Mini DisplayPort/Thunderbolt port.)
 
  • Like
Reactions: olad
Forgive me for not knowing why you're running multiple installs of macOS, but whatever the reason, have you considered just running a single host macOS with other versions as virtual-machine "guests"? For reference, Howard Oakley at EclecticLight.com has written extensively about macOS virtualization.
I can run Multiple installs of macOS on here. However, only one can be signed into my Apple ID, otherwise I have iCloud issues. I could create a second Apple ID for the other install to avoid this problem. I have learned how to use and setup APFS Volumes so a VM isn't needed for macOS dual booting here. I keep Monterey around as it's the last official supported version of macOS for this iMac, and I keep it for GPU related tasks that don't work under OLP because of the root patching vs natively installed drivers. That, and I use a few older programs that prefer older versions of the OS right now for best compatibility. What I may do is go back to my initial setup with Monterey as the main install and a couple other installs on additional APFS volumes. Overall, OCLP works well with this iMac as well. I just need a few things available to me that only a supported OS can give, and intel as well vs buying a new Mac.
 
  • Like
Reactions: macpro_mid2014
I can run Multiple installs of macOS on here. However, only one can be signed into my Apple ID, otherwise I have iCloud issues. I could create a second Apple ID for the other install to avoid this problem. I have learned how to use and setup APFS Volumes so a VM isn't needed for macOS dual booting here. I keep Monterey around as it's the last official supported version of macOS for this iMac, and I keep it for GPU related tasks that don't work under OLP because of the root patching vs natively installed drivers. That, and I use a few older programs that prefer older versions of the OS right now for best compatibility. What I may do is go back to my initial setup with Monterey as the main install and a couple other installs on additional APFS volumes. Overall, OCLP works well with this iMac as well. I just need a few things available to me that only a supported OS can give, and intel as well vs buying a new Mac.
There was a discussion a while back here and the conclusion was that you can run multiple versions of macOS without issues with iCloud if you spoof the Mac's serial number on OCLP.
The only problem would be how to control which version of the EFI you are booting. A simple solution would be to install OCLP on two (or more) USB sticks, each one with a customized Mac serial number. You could label them as macOS Sequoia, macOS Sonoma, etc.
 
There was a discussion a while back here and the conclusion was that you can run multiple versions of macOS without issues with iCloud if you spoof the Mac's serial number on OCLP.
The only problem would be how to control which version of the EFI you are booting. A simple solution would be to install OCLP on two (or more) USB sticks, each one with a customized Mac serial number. You could label them as macOS Sequoia, macOS Sonoma, etc.
I'll consider that, and I have also considered creating a second appleID too so i have my main one for my stable install and one for testing.

EDIT: I wanted to add, I never signed into my AppleID, or iCloud when setting up Sequoia on a separate APFS volume. However, when booting back into Monterey, I got the "this mac cannot connect to icloud" message and required my password, and a fresh verification code. I understand this when I actually sign into a second install on the same Mac, but what causes when I don't sign in? and simply reboot into the other install? It makes no sense. Does anyone have any way to explain this, and how to stop it?
 
Last edited:
  • Like
Reactions: macpro_mid2014
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.