Bug Reports

PP Beta 22.3.0.9.In PP Beta export tab, I select "creative cloud" and I see that my video size  is 212 Mo (MP4). So I click on "export" and at the bottom right I have the same error alert (twice the same message) : It says "impossible de synchroniser avec le creative cloud", ie "unable to sync with creative cloud". I have this problem only when the video file size is big. If I go on creative cloud, it seems to work (I have my MP4 file coming from PP Beta, and I can play it).

Had a forum user pass on some Panny S5 V-log to test. He's showing a yellow tint to applying the Lumetri RGB Curves to 'normalize' the clip versus the "Obsolete" RGB curves effect.   I can replicate.   In the Lumetri RGB Curves compared to the Obsolete RGB Curves tool, the  Reds are shifted towards Yellow, and there's also a subtle shift of Green towards yellow with also subtle loss of saturation.   I include two sample shots of the Waveform, RGB Parade, Vectorscope YUV, image, and the Curves panels shown.   I do not find this with say my BRAW or other log clips I tested, this may be a Panny or V-log thing.   Neil   Lumetri RGB Curves Obsolete RGB Curves effect  

Hi guys, any workaround how can i get rid of this bug? Unable to open my team projects nor create new after today's morning update of beta. Running tight on a client's schedule. Premiere pro project is working normally, it only concerns the team projects. Any advice highly appreciate it! 

When you capture an AVI file within Premiere capture via Black Magic card with presets- Black Magic HD mpeg 1080i50- Black Magic Uncompressed 8/10 bit 422AVI is imported a progressive! This also happens with these AVI OpenDML formats (MediaInfo)  (HD MJPEG 1080i50 Upper)Format : AVIFormat/Info : Audio Video InterleaveFormat profile : OpenDMLFile size : 1.34 GiBDuration : 4 min 58 sOverall bit rate : 38.7 Mb/sVideoID : 0Format : JPEGCodec ID : MJPGDuration : 4 min 58 sBit rate : 37.0 Mb/sWidth : 1 920 pixelsHeight : 1 080 pixelsDisplay aspect ratio : 16:9Frame rate : 25.000 FPSColor space : YUVChroma subsampling : 4:2:2Bit depth : 8 bitsScan type : InterlacedScan order : Top Field FirstCompression mode : LossyBits/(Pixel*Frame) : 0.713Stream size : 1.29 GiB (96%)AudioID : 1Format : PCMFormat settings : Little / SignedCodec ID : 1Duration : 4 min 58 sBit rate mode : ConstantBit rate : 1 536 kb/sChannel(s) : 2 channelsSampling rate : 48.0 kHzBit depth : 16 bitsStream size : 54.7

will not import or display files to create an edit. Does not open the file navigation. Windows machine

I get this (attached) but I am not importing video but a picture.  And I treid multiple ways to import a picture (JPG) as I use it for years (drag & drop from foleder direct, from files manager and File>Import). No the funny thing is I went into a Photoshop and saved the picture as PNG and PSD. PNG worked but PSD gave me a differen error which is attached.  

Interpret footage not working correctly. Modifying clip from 60fps to 30 fps does indeed increase clip length like you would expect. But, when you lay the modified clip on a 29.97fps sequence, it still plays back at normal speed, and not half-speed like it should.  Steps to reproduce:    1. ... Result: ...Expected: ... System info    Application: Premiere Pro (Beta) v22.2.0.105    OS: macOS v12.0.1, RAM: 64.00 GB GB, CPUs (logical): 20

Cant create captions after pressing "+" works on pro but not on beta Steps to reproduce:    1. ... Result: ...Expected: ... System info    Application: Premiere Pro (Beta) v22.2.0.93    OS: macOS v11.6.2, RAM: 128.00 GB GB, CPUs (logical): 16

Unless I'm mistaken, for years I've done the following to trim the head of a clip:With a clip on the timeline selected, press ctrl-K to insert a cut.Hit shift-delete to ripple delete the section to the left of the playhead But today I've noticed that PPro seems to auto-select whichever clip is under the playhead/CTI, which means that shift-deleting removes the clip after my cut, not the one before. Why does PPro auto-select clips now? Is that something new? Have I inadvertently activated something? It's REALLY annoying! SOLUTION: After a hunt around, I found that I must have somehow inadvertently turned on Sequence > Selection Follows Playhead. I won't be making that mistake ever again!