All current versions of After Effects will render GoPro Cineform 10 bit with alpha files and AE, Davinci, and Blender on an M1 Mac. The codec will not work in Premiere Pro, with or without an alpha channel.

Give it a try. Create a shape layer in a new comp and render in AE with an Alpha channel using the GoPro Cineform codec. Import the rendered comp into AE. Everything is fine. Try the same file in Premiere Pro and you get an Incompatible format error message.

Photoshop will also no longer open movie files, but that's another post for another forum.

Importing footage from the Sony A1, when I record 120FPS natively and with the S&Q mode, that camera is slowing down automatically from 120fps to 30fps into Premiere Pro is very glitchy.

The problem is that the footage I import in Adobe Premiere Pro + (Beta) on M1 is glitchy.
On my Intel Mac, it works but same as other people already mention it Premiere Pro is not supporting 120FPS proxy so far. Premiere Pro is only creating proxies up to 60FPS.

I found a SOLUTION with a third-party app cold "Shutter Encoder" to create 120fps proxies or, in my new case, the M1 and the glitchy 120fps footage from the Sony A1 (I guess A7s III will be the same problem).

I have to convert them over the "Shutter Encoder" App in Apple ProRes or H.264 so that the footage is not glitchy when I import and then preview it or render it out any more.

Please, Adobe improves this problem, as I see many people looking for a solution or have this problem with the newer cameras. Thanks

Maik Kleinert

Dropping multi-channel audio clips into an incompatible sequence crashes PP -- eventually.

The issue seems to be with putting clips with multi-channel audio into a sequence that was created stereo -- that is, the "Mix" track in the sequence is stereo. I initially set the individual audio tracks to "Standard".

When dropping clips from the Canon C70 into the sequence, PP automatically creates a new track which I believe is adaptive/2-channel -- there's a little "2" in the track control panel. The sequence "Mix" track is still stereo.

All this seems OK, and all is well for a while; but after several sessions of editing, it crashes, and gives me the "Sorry, an error occurred" / send error report dialog box.

Once this has happened, the project is ruined -- now every time I open it, I just have to click the timeline a couple of times and it crashes. I can rewind to an old version of the project file, and painstakingly re-create all the edits I just lost, but sooner or later it starts crashing again.

The fix seems to be to re-create every sequence with the audio format set to "Multichannel / 4", and the tracks set to "adaptive". Then rebuild all my edits in these new sequences without clicking on any of the C70 clips in the original sequences. Since doing this, my project seems fine.

It seems to be specific to the Canon C70. I've been editing for over a year with footage from a Sony PXW-X70, which also has 4-channel audio, no problem. It's only since I got the C70 that this has been happening. The Info panel shows the footage from the Sony as "4-channel mapped to 2 stereo". The C70 comes up as "4-channel mapped to adaptive".

Attached -- a crash dump from one of the crashes; a small project I put together which reproduces is (I had to add ".txt" to the name)

I have a project that was shot on the Canon R5 (C-log3) which i moved over to v15.1 and noticed everything looks crunched in the shadows.
Tried it on another computer with the same result. Going back to v14.9 fixes this so i think it's an issue with how premiere is reading the Canon 10bit HEVC files.

Double checked all the GPU and colour management settings are the same across both versions

When i bring the project into Reslove, it appears as i see it in v14.9 which i think is the correct image... so something going on in v15.1

Have attached a screenshot showing the difference.

Please fix!

Phantom Flex4K files read differently across different software, but Premiere reads it the worst. Resolve and Silverstack both interpret timecode start NOT as the trigger point, but as trigger point timecode MINUS number of frames to get the correct TC.

If Premiere could play nicer with .cine files, then timecode marks selected from files that are transcodes made from Silverstack Lab or Resolve would align perfectly with the TC displayed in Premiere.

If you see the attached screenshot, you'll notice a difference of 500 frames (00:00:20.20) between Premiere-ingested cine files (despite being offloaded with different TC settings in Silverstack) and the transcodes off files brought in with GMT for TC.

Hello. I have a hobby on YouTube. I make two-language audiobooks. They look something like this https://youtu.be/NYIRt5WwKMg
In Adobe Premier Pro, I create a video project Frame Size: 3860 horizontal 1615 vertical 772:323 and two “New Titles " from the menu: File - > New - > Legacy Title... with default parameters. Width: 3860 Height: 1615 TimeBase: 29.97 fps Drop-Frame Pixel Apsect Radio: (1:0)
On the first track there will be a picture with the dimensions of the sides 3860x1615 pic
On the second track will be located “ Title " English tex with coordinates Video Motion Position 1930 x 0
The third track contains the title “ Title” with Russian text with the coordinates Video Motion Position 1930 x 1620. These coordinates make it possible to display two running texts under each other.
Each " Title” has a Title type - > Roll, Font - > Arial, Size - > 230

On the audio track, the audio accompaniment of the book.
The essence of the error itself.
In the course of the work, you have to use blocks of texts up to about 10,000 words. The larger the block, the more visible the error, which almost does not work. You can display it like this. Create a "Title" with English text, under it a " Title” with Russian text, and if you start to visually synchronize them under the audio track, then there are freezes for a very long time.

Having always used Premier to capture video from my DV tapes on my mac in the past, I tried as usual today but the DV option is missing.
After some lengthy discussion with a helpful adobe chat operative I was told to use my windows machine as DV is not supported in the mac version anymore as its now 64 bit. To me this seems like an issue with premier not mac os as it cant still import dv through third party apps, again as advised by the chat operative, but they were not able to tell me which apps to search for to help me with my problem. Please bring back DV capture as it seems the issue is not with mac os but premire.

Importing a screen recording from Mac creates various video errors and glitches, some visible during edit, others only after export.

It can be frames entirely green or more complex rendering bugs such as ghosting for up to a second.

The error started 1.5 years ago and has been through many updates of Premiere Pro as well as Mac OS. I see multiple people posting it and I've also seen the error come all the way through into YouTube uploads from multiple people - clearly they didn't notice until it was too late.

Only workaround is to transcode the screenrecordings to ProRes before editing, which takes up so much unnecessary time and space.

Doesn't anyone on Adobe have a Mac? No one screen records?