UPDATED: Mac OS X systems that have disabled (SIP – System Integrity Protection) has caused Mac OS X systems across the world the causes the Mac Operating system to go into a Kernel Panic.

Google has released a fix using the terminal command which will require that you boot up in Recovery Mode.

To do that: Boot your computer from a cold start, and immediately how down the Command + R keys until you a see a progress bar for loading the recovery OS.

From there, navigate to the Tools Menu and Choose Utilities and then Terminal.

Then follow these instructions to fix the Google Chrome Update that causes Mac’s with SIP disabled to crash.

Here is a fix for the restart issue.

Our Media Composer customers, including myself have experienced a dreaded issue with older Mac Book Pro’s 2013 or earlier where the OS has a kernel panic attack.

Symptom: Mac OS continually rebooting, and the inability to re-install the OS through Disk Utility.

FYI: I’m am running a Mac Book Pro 2012 late model, I7 with 16 Gigs of Ram running Mojave (Mac OS 10.4.6)

This problem was first brought to my attention from my customer at Beyond 8 Video. He took his Mac Book Pro to the Apple store only to be told he needed to purchase a new motherboard for $600.00.

Now, he’s having second thoughts after reading the article from the Independent on older Apple Computers breaking down across Hollywood from Avid Media Composer Software.

To be clear: This happened out of no-where! It was just like any other day. Nothing had changed or had been updated on Mac OS X Majove. Suddenly the system freezes and will no longer reboot.

Please note: I was in a panic! I was able to fix the problem, but it did require re-installing Mac OS X Mojave. So my suggestion here is not for everyone.

Here are the steps that I took to get my system up and running.

• Disconnected ALL peripherals. If my case (even the mouse and keyboard) – since I’m on a Mac Book Pro.
• Reset the P RAM (Hold Down Command + Option + P + R from Cold Start (Don’t let go of keys!)
• Let the Mac reboot a minimum of 4 times (or up to 7 times) while continually holding down Command + Option + P + R keys.
• Shut Down Mac Completely. You can hold down the Power Button for 5 seconds to do that.
• Reboot holding down the Command + R keys.
• This will boot from the recovery partition.
• Select Disk Utility and Run Disk First Aid on your Internal MAC HD drive (partition)

The key here is to get the Disk Utility from the recovery partition to allow you to run Disk First Aid on your Mac OS X system Drive. If you can get past this step, then you should be good to go!

• Re-Reinstall OS X (This may seem scary and proceed at your own risk)

Here’s the good news! On my end, even after re-installing the Mac OS X operating system, everything still functioned just like before. All my Avid Media Composer and Adobe Licenses still worked, etc.!

If you’re new to Media Composer 2019.X, there is a new feature where you can adjust fonts and font sizes for each individual primary Media Composer Windows.

You can now adjust the font type and size for The Composer Window, The Timeline Window, and the Bin Container Window.

So for example, I recently upgraded Avid Media Composer System, and the fonts were too small to read within timeline window.

• Select a primary Media Composer Window.
• Navigate to the Windows Menu and Select Sent Font
• Choose a new Font (i.e, Arial) and a Font Size

Thanks to Avid for implementing features like this that don’t seem like much. But believe me, some time the most simple features go a long way in terms of improving efficiency.

Learn the basics of using Bin Containers within Avid Media Composer.

This tutorial video is a super basic introduction to using a bin container with Media Composer.

Here are a a couple of key features that may be foreign to even the most seasoned Avid user that hasn’t had the opportunity to upgrade to MC 2019

• The is no longer a project window within Avid Media Composer
  
• The Bin container is now the heart of of the software. You must always have at least one bin container open.
  
• You can have multiple bin containers, but they are essentially clones of each other. This concept may seem odd. However, multiple bin containers may be useful for different container ‘views’
  
• Also, it’s critical to understand the difference between dragging a floating window into the main interface panel, vs another window that already has a tab. So, that’s why I’ve reinforced the concept of holding down the alt/option key when dragging a floating panel into another window.

Hold down the ALT/OPTION key to attach multiple tabs to the same window. You will end up with something like this:

If you don’t hold down the ALT/OPTION key when re-attaching to windows that already have a tab. You end up with something like this:

I’ve been using Avid Media Composer full time since 1992. I can see how this new interface will take seasoned Avid Editors awhile to get used to. The new Avid 2019 interface now looks more like DaVinci Resolve and Premiere.

This is a VERY basic introduction to the new interface of Media Composer 2019.X.

For Avid users who haven’t experience the new interface design, DON’T worry, All your favorite Media Composer editing techniques haven’t changed.

I anticipate this new interface will take a year or more to eventually be adopted by mainstream editors.

In the near future, look for many more tutorials that cover the critical fundamentals for learning Avid Media Composer 2019.X

For seasoned Avid Media Composer users that aren’t used to the new interface, you will notice there is no longer a Project Window.

The bin container is the new heart of Media Composer. The old Project Window settings can be found under the File Menu / Preferences.

When running software products such as Avid Media Composer,  if you receive an error that says No Media can be written to any mounted drive.

In attempting to correct the problem, you may encounter a Mac OS X message that says  ‘The Operation can’t be completed because you don’t have the necessary permission’.

This error flag results from your software attempting to write files to the root level of your system drive.  Apple purposely protects files on the system drive to avoid viruses and other vicious programs that may compromise the operating system.

Please Note:   It’s not normally recommended that you write media to the system drive.  However, there are several scenarios where you may not have external storage.

#1-  First Step :  Right click (or control click) on your system drive and choose get info.

Click on the orange lock in the bottom right corner of the Mac HD Info dialogue box. (see graphic below). Then type in your Mac OS X user password.

Change the permissions for the internal system drive to Read & Write for the wheel and everyone.

*Side note: If your Mac OS system user does not have an assigned password, Mac OS X may prevent you from changing the permissions.  If this is the case, go to your system preferences and assign yourself a password.

Now, you may encounter that dreaded message that says ‘The Operation can’t be completed because you don’t have the necessary permission. Super frustrating!

If this happens, here’s the fix:

#2- Second Step: Reboot the Mac, and immediately hold down Command + R. Wait for the the Mac OS to boot into recovery mode.

After it boots into recovery mode, navigate to the utilities menu and choose terminal.

From the terminal prompt:  Type: ‘ csrutil disable‘  within the terminal window.

Then reboot the machine.  Then you will be able to adjust the permissions for the ‘wheel’ and ‘everyone’ so certain third party software products can access the root level of the system drive.

Please note:  I recommend re-enabling the System Integrity Protection to prevent accidental or vicious attacks against the Mac OS X operating system.

To do that:  Repeat the same process of booting into Recovery Mode (Command = R) and type ‘csrutil enable‘.