And this means it is time for the awesome deep dive review with Andrew Cunningham at Ars Technica. This is always the way to learn the ins and outs of the new system, and I always look forward to the article, and have been reading them for every OS release for so many years.
I would love to upgrade, but I always have to wait. Before you upgrade you should always check out what apps might have issues and to find out I always check out the forum at MacRumors, which has a post with a sticky at the top with Apps that are working and not working. Now it doesn’t do version numbers, so it will almost never answer my most pressing issue, which is what versions of Premiere Pro will work on the new OS (yes the new version works). Now it does seem better than most OS upgrades, but some apps are still having issues or sure.
I have companies that work completely on 2019 (which you can’t even install and should not be using anymore), and I don’t know how you run a newish MacPro on that old of an OS, but I digress.
•Apply Motion (ipad and windows) which I am interested in checking out.
•Perspective Grids (ipad and windows) to help do proper perspective
•Send to Illustrator on iPad
•Vector jitter brushes to give a more organic feel to vector brushes
Awesome, I need to spend more time in Fresco as it really is such an impressive and powerful painting program, and am certainly interested in seeing what the motion does, and see if will be useful for any video projects in the future.
So yesterday I had a post how Adobe’s new color correction feature in Premiere Pro 2022 didn’t do anything to fix the gamma shift issue on Mac on exports, and I posted a link to my post in a facebook group on Premiere Pro for Pro users.
Responses included finishing everything in DaVinci, which does nothing about Premiere’s handling of the issue, and people saying just work on a PC which will fix the issue, though it won’t if you have people viewing on Mac, because the gamma shift will happen then.
And then there were the responses about putting the Gamma 2.4 tag in DaVinci in fact tagging the clip wrongly to display correctly on Mac, and I decided to do a little test with Parallels to see how the clips show up in Windows. And I know that putting the Gamma 2.4 tag on your footage is ignored by YouTube, which ignores a 121 tag on footage and in fact forces 111 which will then have the gamma shift.
So to start this is short film I am working on, and the first part are the clip set with the DaVinci Gamma tag set to Gamma 2.4 on export.
So I exported the show with this tag.
Now I wanted to see about the tags and how they would look in Windows, so I have Windows 11 installed in Parallels, and I used both just Windows viewer and VLC in Windows, now I just used whatever size they opened at so I will scale down the other images to match framing. And the frame might be slightly different as I couldn’t figure out how to go frame by frame in Windows player. This is all on my iMac Pro, though screen shotting form mac, find it interesting that the 121 Gamma 2.4 tag matches on Windows to Mac, but VLC on Mac and WIndows doesn’t and VLC on Mac looks closest to what is on my external monitor.
And this one I don’t get at all, but here it is, VLC on the Mac vs VLC on windows, the mac version seems correct, and closest to what I am getting on my external monitor. If anyone can explain it, please contact me about what is going on here. Windows 11 is on the same display as the mac, though I am taking the screenshots from the Mac into the parallels Window.
I am very confused about this last one, I think the VLC on the mac looks most like what the image looks like on my external monitor, but on the mac at least the clips exported from DaVinci with the 121 Gamma 2.4 tag look closer to the image than ones exported with the 111 tag which completely show the weird gamma shift.
So for exporting from Premiere Pro, I guess if you can get people to use VLC is the best option, but if you can’t I would love if Premiere was able to add the 121 Gamma 2.4 tag to exported movies because it will look better on client machines.
I have also read the YouTube ignores the 121 tag and plays video at 111, so they will look blown out on YouTube. Does Vimeo do the same? I might have to do some tests and see what the results are when I have a chance.
If anyone has any thoughts please let me know.
EDIT:
So since there is such a difference in VLC, I decided to try another app that doesn’t do ColorSync on Mac and that is Firefox in Windows 11 and Mac.
So strangely Firefox looks different on Mac and Windows. Better on Windows, but not as bad as Mac Quicktime for sure.
OK so I have posted about this at Adobe Uservoice to ask Adobe to add the ability to change the gamma of a clip on export. I know you don’t want to do this for final export, but for clients viewing copies, it would be nice to guarantee that those on Mac and those on Windows see something approximating what I see on my external monitor.
So Adobe new update of Premiere Pro says it includes Color Management for H.264 and HEVC as a new features. The feature describes itself as the following:
With new color management for H.264 and HEVC formats, Premiere Pro interprets the correct color space when importing these formats, including 10-bit and HDR files. For exports, Premiere Pro includes the correct color space metadata with your output files, ensuring that your colors will display correctly on the destination platform. When creating new sequences, you can choose to Match Source or apply the color space you want to use, depending on your working media.
I was hoping this would add the ability to add tags to exported H.254 videos so that they would display correctly anyplace, but especially on Macs. Macs of course have the weird gamma shift issue because of how they handle color, so Apple’s apps work correctly, but everything else has the wrong tags, so you have to watch your video in an un-color managed app to see what the clips will actually look like.
Now DaVinci Resolve has the ability to change the gamma tag in an exported H.264 clip.
If I set the Gamma tag to Gamma 2.4, the exported H.264 video plays back correctly both in Quicktime as well as in VLC. I was hoping this is what Premiere was doing.
Unfortunately I immediately opened my current Premiere Pro 2021 project in Premiere Pro 2022 and did an H.264 export matching the export i did yesterday, and as far as I can tell it is exactly the same as the clip I exported yesterday with the gamma shift and all in Premiere Pro.
I checked out the video info in Quicktime on the clips, and the clip from 2021 and 2022 match exactly like this:
Interestingly a video exported from DaVinci with the Gamma 2.4 tag does show up with different info in Quicktime. It looks like this.
Unless I am completely missing something in Premiere Pro, I am not sure what they actually changed here.
It’s new features tie into the new features of After Effects and Premiere Pro, most excitingly with COLOR MANAGEMENT FOR H.264 and HEVC on Import and Export! WOOHOO FInally working around Apple’s fucked up color on the mac, and like DaVinci before it, letting you export compressed video with proper metadata tags so that it will display correctly whoever is looking at it! I literally have problems with this every single day, so I can’t wait to give it a try. This is game-changing if it works!
Also included is Color Management for Sony XAVC-L-HDR and Faster Rendering for After Effects with multi-frame rendering, should be 3x as fast! Woohoo!
Adobe has updated Premiere Pro as they go into the onine Adobe Max this morning. I have to say I much enjoy being able to see all of the classes online.
*We get unified version numbers across the video suite, so all compatible versions will now be version 22 (should’t they have just gone back to 1?)
*Speach to Text Improvements with improved accuracy for pop culture terminology and better formatting of dates and numbers
*Simplify Sequences has moved from Beta, I still think this could have been a great spot to add in unmerge, since merging audio clips is totally broken.
*Color management for H.264 and HEVC H.265, WHICH IS HUGE! You can now include correct color space metadata on exports, like DaVinci has allowed you to do for a while. So people on Macs should actually see what your show will look like correctly.
*Improved 10 bit HEVC playback and improved M1 support (lets hope it includes M1 Pro and Max support)
•Color management for Sony XAVC-L-HDR
•A new colorized vectorscope
•Improved Histogram
•Lumetri curve refinements
•Restore trim selection in the timeline
•Improved Media relinking for Team Projects
•Improved Bars and Tone for both HDR and SDR.
•New GPU Acceleration for effects, Alpha Glow, Mirror, Reduce Interlace Flicker and strobe are GPU accelerated.
AND IN BETA
•REMIX powered by Adobe Sensei, to intelligently re-arrange songs so that music matches your video, instead of cuts and crossfades let it do it itself. I can’t wait to try this out.
•Auto Tone, better auto color in Lumetri, a good start point.
*Speech to Text on-device without the internet for faster results.
*Improvements for new Import Mode, which is good because it needs a whole lot of work.
So I have written about Sofi Marhsall’s Ultimate Rea-Time Editing Workflow (That Won’t Break the Bank) and just wanted to give a little Update on how i have updated that workflow because of my setup, and the difference for me is that I run a older Blackmagic UltraStudio 4k as my video out, which I run to a Samsung HDTV.
I followed her instructions and got a BlackMagic Web Presenter, but got the UltraHD version so I can do 4K video, and it does seem to work just fine with either the front or back USB C unlike the older version she used.
And because I am not using USB-C to HDMI cable for my setup, which is also going to eat up a more of your video ram (displaying as a second monitor. Instead I ran a BNC Cable from my UltraStudio 4k into my BlackMagic Web Presenter, while my Samsung is running out of the HDMI out of the UlraStudio 4k. Sofi’s version is setting up the web presenter as a second monitor, but I am already using a second monitor on my computer, and would rather run the direct output from my UltraStudio from Premiere (or DaVinci or AVID) into my Web Presenter, and you don’t need to setup the web presenter as a second monitor.
Whatever you are playing back shows up on both monitors for me, and I can see on my TV, which is the black line at top with the power cable running down the wall, and the usb cable to the computer allows the web presenter to act as a USB web cam.
Premier Video Output Settings
So in Premiere I am playing back through Blackmagic playback via my UltraStudio 4K, and I have disable video output when in background (which I usually have checked, disabled, so the signal keeps going to the webcam constantly.
Now again differing from Sofi Marshall here I have the audio setup differently, as she is using Loopback to send the audio to the Web Presenter, but I am using Premiere Pro directly. I am still using Loopback, but differently as I will show.
So for Premiere Pro I go to Premiere Pro > Preferences > Audio Hardware to setup direct audio to the UltraStudio 4K.
I then follow Sofi Marshall’s directions on creating Loopback Device 2, which combines the iMac Microphone (her external microphone) and the audio from the Web Presenter.
So here is my loopback microphone setup so my cut can be shown with audio and they can here the microphone.
Now since I am running the audio directly to monitor my audio for me it would be coming out of my TV which would then show up in my microphone, so I can’t have that, so I must mute my HDTV, and I want to hear my edit through my headphones. My headphones are running through my Edirol though could be just the headphone jack, so I have made a loopback to send Premiere to my Edirol.
I have also made a setting for DaVinci exactly the same but with DaVinci.
These send my audio from Premiere or DaVinci to my headphones. Now we need to setup zoom.
Now you can do a zoom using my video out from Premiere and Web Presenter. Thanks to Sofi Marshall, as I would have never done this without her.