![]() ![]() They just live it, it's not a big issue to many people (but was to me! lol. I know of a decent number of people mentioning this memory issue (only on macs typically), however, they just ignore it by quitting Premiere and re-opening it, which does temporarily resolve the issue (for an hour or so). But after many hours, I was able to narrow it down to that. It was maddening to try to troubleshoot and figure out where this was coming from (and try to get my work done). It's surely a corrupt preference or workspace setting that causes this issue. I also stopped the sync and manually set the workspace settings and preferences again. Once I deleted everything out on my Monterey machine (including all files listed in the location above) the issue stopped. Within an hour of editing, I look into the activity monitor and it's over 30gb+ memory usage for Premiere and increases until the out-of-application memory message comes up. The memory leak issue only starts when the sync settings (including preferences, workspace settings etc) get synced down. They recently made a public update to Premiere Pro 2021 and Media Encoder 2021 (version 15.4. The M1 iMac wasn’t far behind though, at a minute and 4 seconds. The Intel PC managed it in a very speedy 56 seconds. I've tested this issue on brand new installs of OS's (Monterey, Catalina etc). Adobe has been working for a year to bring Apple silicon compatibility to their Adobe Creative Cloud software. For rendering a 30-second clip containing two 5.9K 24fps 10-bit 4:2:0 files, sampled down to 4K 24fps H.264 was sent to both machines and they were left to render. I can't recall when exactly the issue started, but it only seems to be a year ago. I'm wondering if something could have happened between switching account sync settings at some point. However, in the past I have used a different account (a few years back) but, for the last couple of years, I've been on the same account. It's just one login I'm using to access creative cloud and to sync the settings currently. Hey Kevin, that's an interesting observation. Library->Application Support->Adobe->Common->Plugins->7.0->MediaCore Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore Library/Application Support/Adobe/CEP/extensions Delete them all and reboot, then reload Premiere and you should be all set! Good luck.Īdobe extensions path (delete extensions) Here are the notes I took of all the locations these preferences live. Once I turned this off in adobe preferences (workspaces, preference sync etc) and cleared out all settings related to Premiere, it worked without issues. And we'll see if someone can give a tech description based on the specific hardware you're running.In my case, it was a corrupt preference setting that kept getting synced down using Adobe Sync. ![]() So if you haven't messed with the prefs for H.264/5, try that. And is often not what one expects.Īnd some people get better results when they turn on the prefs for H.264/5 encoding and decoding, some better when they turn them off. I don't know the particulars like say does, but I know enough that the hardware matters. ![]() H.264/5 work depends heavily on the inherent capabilities of the underlying hardware to process the specific forms of H.264/5 compression you are working with. Remember, for both those tracks, your machine has to decode up to 30 frames or more to display the 'current' frame on the timeline.Ī couple tracks of 6k RED would probably be easier on the machine. Amazing for data compression and speed when used with the specialized in-camera chips. Long-GOP media is the nastiest crap for editing made, period. Running multiple tracks of long-GOP 4k 10 bit is by no means "light" editing. When will Premiere put stability and performance first? I can guarantee you if I drop this exact same footage in DaVinci, it'll run like butter. ![]() This is a light edit I'm doing, and as mentioned, something like this works fine on my PC. I spent the extra money and upgraded to the top of the line Mac to avoid spending the time making proxies or transcoding. There is obviously an issue with Premiere Pro not tapping into the power of the M1 Ultra chip. Pretty frustrating that it's lagging considering that on my 2018 PC with a GTX 1080 and I9 processor with the same footage using a spinning HDD with USB3, it doesn't lag. Running off of a Crucial 4TB SSD connected via USB-C on the back of the Mac Studio with one of the Thunderbolt 4 ports. Footage is 4k h.265 10bit 420 from Sony A7siii. Editing lightly-compressed h.264 footage in a timline lags 3-5 seconds scrubbing and hitting play. I just setup a brand new M1 Ultra Mac Studio running OS 12.5 with Premiere Pro 22.6.2 and I'm getting laggy playback performance. Solved: I just set up Premiere on a clean M1 Mac Studio. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |