Search results

BIRD is running around 52% which from what I read is iCloud sync services. Everything else is 7% or lower which is quite acceptable. I'm going through all my iCloud folders and doing a force sync of individual items that still have a cloud beside them and see if I can clear up the iCloud sync...

Heya, been looking around to find some answers but having no luck. On Ventura my video pauses every few seconds pretty much everywhere Youtube, Quicktime...Photos app. System was running fine on Big Sur but a fresh install of Ventura is a bit wonky and I'm using newest versions Ventura 13.6.3...

Update.... issue is back again...Safari, Youtube, Quicktime... pretty much everywhere. Anyone find a solution?

I posted this in the Audio interface forum.... maybe someone here can throw me a bone? I also tried Loopback audio router. It only sees 2 channel out of Plex and Apple Music apps so I can't route what isn't available. All works 100% on M1 iMac on Sonoma same settings and Loopback required at all.

I had this same issue on install of 13.6.1. Video pauses every few seconds. This was for YouTube, FaceTime camera / continuity camera using my iPhone 14 and also videos in my Photos Library. I updated to OCC 0.9.5 using HackenDrom 2.1.8 and OCC 2.74.1.0 and voila, fixed the video issues on reboot.

I must be missing something 1. Download the AirportItlwm.kext for Ventura 2. Copy and place file in EFI under OC/Kexts folder 3. Mount EFI and open config.plist in OC (0.9.2) 4. Go to Kernel page and enter MinKernel 22.0.0 MaxKernel 22.99.99 5 Reboot I don't see the AirportItlwm.kext in OCC

Got my Ventura up and running with my back up Big Sur.... Thank the Gods for back ups.... Ventura is working fine but some the software I like to use is still behind... oh well and no wifi Blue tooth with Intel chipset So as a side question I have the Z490 Vision D with the Intel WiFi and BT...

As a general question, Will the install procedure at the beginning of the thread still work for a fresh Ventura install? I want to use OC 0.9.3 and the OC-092-Z490-VISION-D file. Bios F5 i9 3.7 Ghz 10 Core Intel 64 GB 3600 DDR4 AMD Radon RX570 8GB Intel 1219V11 / i225-V Ethernet WD Black SN770...

You are a plethora of knowledge, a scholar and a gentleman! Bam! NVMe to NVMe copy took about 7 minutes with step 11 form the mentioned article, and I'm up and running with only the new WD Black drive installed! I spent hours reading and searching before I asked... I would have never found that...

This cover what ya need ?

The new drive has an EFI Partition that was named "EFI-WD_-721" and has the EFI folder with all the typical files. APPLE BOOT OC with config.plist

Stumped..... I have a working Big Sur on OC 0.8.9 (Upto date using HackinDROM) boot and runs fine. It's on a Sabrent drive which I have been reading can turn into a problem so I bought 3 2 TB WD Black SN770 to use. I followed all the create back up directions ...multiple times (I have the...

I now see the folder for custom backups in the UI for HackinDROM..... u guys think of everything...if we read... HA!!!

Updated and all rebooted fine. The errors still appeared but it was updated to 0.8.9. I did a bit of reading and tried to run HackinDROM again and it errored out half way. It created a zip backup in my EFI folder but failed to create the new files for my EFI so I couldn't restart. Grabbed my...

Thanks for the reply! When I load my existing config.plist from my active (working) efi none of those are checked. Is it possible it's just a version conflict from OC 0.7.2 to 0.8.9?

Thanks for all the great info! I just installed and ran HackinDROM. I have OC 0.7.8 and system is running well, although I do find it a bit slower than I expected with Sabrent Rocket NVMe 2.0 drives and 64GB RAM. When I run the updater it shows this error screen. I have a backup copy of the...

Thats great information to have, this is my first OC build as I had been using UniBeast and Clover so Im used to having some extra control on the boot screen. Next hurdle.... dual boot with Win 10!

I'll answer my own question for those of you that might run into this as well. Once I rebooted a few times, I also applied the next Mac OS update for Big Sur on the backup drive the name drive name changed to the one I gave it in the backup process so I could tell the difference between them...

Yes that worked, I believe the steps I was missing were selecting "Legacy Bootable backup assistant" and "allow CCC to erase the destination drive". When I rebooted I have 3 disks now EFI. and 2 named the same even though I named the drive something different during the process. is there an easy...

Maybe someone can shine a little light on creating a bootable back up? I follow the awesome guide yet I have no idea why but I've tried multiple times and when I reboot I can see the original drive (that works great) and EFI from the new drive (but not the name of the drive) but I can't boot up...