Why Is Google Bloating My Computer With 88GB Of Cache Files For Google Drive?

 Google stop using our computers as storage for your own use. I have 88GB of Google cache (crap) loaded on my boot drive. I do not sync my files to Google Drive, I'm Streaming only. 

Home/Library/Application Support/Google/DriveFS/bullshitnumber/content_cache

What content? What cache?

There is no reason for this cache to exist and grow so big. It's totally opaque. NO!

iZotope is Trashing Excellent Plug-ins, Just Cause They Can

 iZotope is discontinuing a bunch of plug-ins from Exponential Audio, a company iZotope acquired semi recently. Among the casualties are the wonderful Rs and Phoenix reverbs. Instead they are pushing for the bloated Neoverb, Stratus and Symphony plug-ins. Without any upgrade path for existing customers. Shame.

Other discarded apps from iZotope are Iris, Break Tweaker and Trash. I haven't used these as much I have to say. I guess iZotope don't care about these anymore. Do you feel old yet?

Apple Releases Final Cut Pro 10.6.5

 Oh my! The updates of FCP, Motion and Compressor are here!

FCP, Motion, Compressor, free updates.

FCP goodies

Compressor goodies. Darn! Some of them require MacOS Ventura.

Motion goodies

Nothing major, just bug fixes and acceleration. I'll take it!

Not A Day Passes Without 🤬 Premiere Crashing 🖕🖕🖕

 11:14am

11:35am

F&$K YOU PREMIERE!

Adobe Premiere Does Not Draw Waveforms Properly, Another Bug 🪳

The bugs 🐛 🪲 🪳 are crawling around with Premiere. This time it's in the form of finicky waveforms drawing... Or lack of shall I say...

Isn't this a wonderful behavior?

Good luck keeping your sanity with this kind of waveform drawing! Oh! By the way, as you see here, it will draw eventually after you playback or zoom-in/out, but next time you open the same file, the same empty sections reappear.

I always remember Premiere being shitty with waveform drawing, so it's not like this problem is brand new. Who cares? Just delete these pesky peak (.pek) files once in a while, what are you complaining about?

Who f$c^*ng cares!?? Not Adobe obviously! Good luck editing audio.

The bugs 🐛 🪲 🪳 are everywhere with Premiere!

More Adobe Premiere Pro Bugs - It's Endless

 Here is another bug! Premiere is so buggy, stay away from it!

When you try to transcribe, or in my case re-transcribe, a Sequence, I get this error message and nothing gets done:

A low-level exception occurred in RawPCM (Exporter:17)

Great! Worked fine on the assembly timeline though. Oh! Wait, apparently if you use any audio FX, or even, god forbid, if you adjusted any levels in the timeline, Premiere throws this shit in your face and does nothing.

https://community.adobe.com/t5/premiere-pro-discussions/a-low-level-exception-occured-rawpcm-exporter-17/td-p/12944658

Lovely! Users only reported this bug 6 month ago, we only had two or three versions of Premiere since then. The bug is still there.

Wonderful, thank you Adobe!

--- UPDATE ---

You won't believe this! So I had enough with premiere and I went for a walk to lower my blood pressure. Lo and behold I come back to the same Sequence, same Project, everything the same as I left it an hour ago. I didn't touch anything. For the life of me I click on Re-transcribe sequence and... It goes through and is currently transcribing!!!

Meaning the workarounds and/or whatever reasons peeps believe Premiere is giving this error message are all BS. My Sequence is completely mixed, with clips, and tracks levels, and sound effects galore! And this time it has decided that it would go through with transcription.

What the F*U#% IS THIS ADOBE???

It's maddening I tell you. Adobe Premiere, the most unreliable NLE software champ 🏆 ever. 

Adobe Premiere + Media Encoder Ultimate Crap On Mac M1

 I've been fighting Premiere and Media Encoder for a while now. I can tell you that they are not ready for serious work that involve h264 as of v. 22.6.2 and v. 22.6.1 respectfully.

Do not use Premiere or Media Encoder for anything serious with h264 in your workflow and a deadline, it's totally unreliable. The software will give you random problems at any time during post. h264 footage? Forget it! h264 exports? Hell no!

You've been warned.

Here is the first seconds of yesterday's export (h264 VBR 2):

Jagged edges, total fuck up of the animated title. Thanks Adobe!

Here are the first second of today's export (h264):

More jagged edges, extra flickering for fun.

Another royal clusterfuck courtesy of Adobe.

Mind you these are 20+ minutes exports, and only the first second is fucked up. Consistently. With various degrees of fuckery. No way to know what it looks like until it's finished encoding.

This is what it supposed to look like:

Of course when I only select the first second of program, the export is fine.

So now I have to output a ProRes422 version that I will use to encode to h264 with Compressor. One more hour of work, plus 100GB of wasted space.

F.U.C.K Y.O.U. Adobe.