Stop Freaking Out! Blogger is Not Broken.

  If all of a sudden you see all kind of gibberish html code while composing your post instead of the familiar text... Don't freak out! Blogger is not broken!

 You probably clicked by mistake on the button that toggles HTML and Compose view and you are now stuck in HTML as Blogger remembers this setting, so next time you open it and try to write something... you keep seeing the code!

HTML view. Help!!!

Click on the button (< >)and switch to Compose view from HTML view

Compose view. Da pencil, you doofus!

 HTML view looks like a double bracket, Compose looks like a pencil. Just click on the button and switch back to Compose view.

Avid Media Composer Is So F#$*-Up! - Snapping Command/Control + Click Buttons Not Working

 This has been a problem with Avid Media Composer for YEARS.

 For whatever reason, Avid MC (8.9.3 in my case) just ignores Command + Click and DOES NOT SNAP to anywhere in the Timeline. Granted one could turn on snapping in Timeline preferences, but that's cumbersome and not a good way to work, it's much more efficient to turn on snapping on the fly, when and only when you need it, by simply pressing Command.

 Only... It often does not work because some random app is opened at the same time and is interfering with Avid. What?? And according to innumerable users that have been suffering from this flabbergasting misbehavior, any app could trigger it: GMail, Anti-viruses, etc. It's not even well documented. People have spent hours re-installing macOS and MC app from scratch, to no avail! 

 By the way it's not the only thing that gets ignored... Holding Option and dragging a item from one Bin to another DOES NOT COPY the item. Avid ignores the Option key being pressed and instead moving the item.

 What random app causes this? In my case it is Bitwarden! Can you believe it? After I close Bitwarden, Avid behave normally. Control and Option keys do what they are supposed to do. What a wreck.

 Can you just for a moment fathom the antediluvian code that's still at the core of Media Composer? Come on Avid! You can do better!!

Apple ProVideo Formats 2.2.1 Removes Avid Media Composer ProRes Options in Quicktime Export

It looks like the update of Apple ProVideo Formats version 2.2.1 removes Avid MC ProRes codec options in Quicktime Export.

That's not good. There are only a few options left for Quicktime export codecs in AMC now, and ProRes is nowhere to be seen:

Many more options were available in the previous iteration of ProVideo Formats 2.1.1.

It is still available as a stand alone installer on Apple: https://support.apple.com/kb/DL2020?locale=en_US

But after downloading, when I try to downgrade/install to version 2.1.1, I get this message:

Of course, no way to downgrade... Then I found this thread on the Avid Forums.

It did point to this workaround for pepps who don't have FCP/Motion/Compressor installed, I do though. I went and downloaded Pacifist anyway.

I opened Apple ProVideoFormats.pkg installer (v 2.1.1.) with Pacifist and saw the five Quicktime components that are missing in my computer's Library:

I then selected only these, drag-and-dropped them into my computer's Library/Quicktime folder. Since AMC is accessing the Quicktime components for its own export settings, I thought no need to mess with the rest.

Pacifist installed them. Now I have the missing v2.1.1. Components into the Quicktime folder with the v 2.2.1. ones, and Avid's own:

I flagged them in RED just in case they start causing some problems and I need to remove them at some point. Again all the rest I left untouched, Apple ProVideo Formats v 2.2.1 is complete on my computer, I only manually added the old, missing, v 2.1.1. QT components.

Now when I Export to Quicktime from Avid, I have again all the variety of codecs, including ProRes:

Yay! Hopefully this workaround doesn't cause any conflicts down the line. I will report here if it does. In the meantime, back to exporting!

Final Cut Pro Error: RequestFrameAt returned: 3 for absolute frame: 312

 Final Cut Pro is flashing an Error on Share via a custom h264 Compressor Setting:

The footage consists of Multicam clips comprised of one HEVC image + stereo audio file, and one multitrack separate audio file comprised of one stereo and two mono tracks.

The Share exports just fine if I do not change anything in the audio panning mode - at the multi clip level, or at the individual tracks level, does not make a difference.

As soon as I change the default "None" panning mode to "Dialog" Amount 100%, which is what I want, I get this error on Share and the export fails.

This audio panning mode "None" exports just fine every time.

This audio panning mode "Dialogue" 100% fails every time.

This error message is not helpful in tracking the problem. Nothing remarkable happens at frame 312 in my case. It's clearly linked to audio.

Now if I export as ProRes (proxy in my case) it goes through the Sharing with no Error massage, but the export is fucked-up. The image is OK, the audio is thrown out of sync from the beginning and stays out of sync until the end. Damn it!