My soft: macOS 10.12.6; Pr 2019 (13.0.2)
Problem description:
1. Pr crushed and workspace was different when reopened.
2. After reopening, kept getting the error message "Error parsing properties list from memory".
3. Tried to open the project window and Pr kept crushing.
4. Deleted Pr properties (holding alt key while opening) and runed First Aid in Disk Utility. Nothing changed.
Thank you for your help.
Hi javierc14641708,
Sorry for the crash issue. As you are on Mac OS, hold the Option key while launching the app to reset Preferences.
Here are the steps: FAQ: How to reset (trash) preferences in Premiere Pro?
Please try the step and let us know the status.
Thanks,
Vidya
Hi Vidya, thank you for your answer. As I mentioned on 4., I already did that, but with no positive results.
Hello everyone,
I have seen this glitch so many times in my career, usually a good work around is to add like +0,1% scale but here is the problem:
Most recent exemple : I've shot a video with the GH5, some images 2160p24 and others 1080p180/60 (interpreted as 24) and I actually upscaled the 1080p footage to 4k with the Scale to frame size functionnality so I can render the whole thing at 4K. Problem is, if there's some 4K footage under the upscaled 1080p footage, there's a line of pixels all around that actually shows whats behind, i've seen this so many times, it also shows on the export, here's a zoomed screen shot of the problem (against a dark background to better see the problem).
Other widely encountered exemple: A lot of people add bars to their videos to give the wide cinescope feel (instead of making the timeline cinescope itself, which wouldn't allow you to warp stabilize in the main timeline), often times they use black bars png files that are not big enough, so they actually scale/fit to frame size and surprise surprise, it's not perfectly scaled and that line of pixel dancing (basically from the video behind the bars) is there all around, here's a zoomed screenshot (upper corner) i've just come across on a random youtube video:
So my question is, am I doing something wrong ? Am I missing something because clearly i'm not the only one, it has happened to me so many times and i've seen it almost as much. Maybe it's a glitch ?
You guys tell me Thanks a lot !
, Try resetting the Workspaces:
Reset a workspace
Reset the current workspace to return to its original, saved layout of panels.
- Do one of the following:
- Click the Workspace menu icon and select Reset to Saved Layout.
- Choose Window > Workspace > Reset to Saved Layout.
from here:
FartArt wrote
leave it running while you get a cup of coffee or walk away for an extended period of time you end up with duplicates of the same file making multiple-auto-saves pointless
I always save as a version number and then back it up before leaving the workstation.
gregf62545650 wrote
Is there a way of editing vertical clips in PP and, if possible, create proxies
Do it just as you would any other project. Set up the sequence to match the vertical video.
I have a Dell xps 15 9550 with Nvidia gtx 960m. I changed that setting and it work fine now. Will that slow my processing? Sorry for all the questions, I am a rookie
Will that slow my processing?
Yes, you wont have MPE hardware.
Actually YES, there is a way to turn this feature off and here is how to do it:
Open the Console (CTRL+F12 / CMD+F12), switch to Debug Database View, then look for "FE.AllowMultipleOpenProjects" and change that to false.
Sorry if I've put this in the wrong section it is related to Premiere pro...
For me to edit Gopro HEVC footage on Premiere Pro and have smooth playback I need to either bump the subscription to £50 a month as that is the only way to get the Media Encoder that's required to create Proxies or build a new PC. My current PC is no slouch with an i7 7700K, GTX1080, 16GB DDR4, Win10. This seems utterly crazy!!
Have I got this wrong? Any suggestions would be appreciated.
Ultimately resolved by updating Adobe Premiere via Creative Cloudapp.
Initially, it would not open via .exe nor via opening from CC. Fiddled with sfc down in command prompt, moved HandlerTitler out of the folder, tried to open then moved HandlerTitle.dll back to its folder. What I tried to reinstall Premiere (first) ut Control Panel had know repair option or option to singularly remove just one program from CS6.
Deleting CS6 or CC were not options for me because I am using both for other programs.
All this fiddling and finally when I went back into Creative Cloud, the update button was active and I was allowed to update.
Hope this gives someone else hope & help.
No, When i start a new project it's shut down directly
Convert GoPro to Cineform to edit https://forums.adobe.com/thread/2423510
tank you so much, it's work
Download the Adobe CC Cleaner Tool as listed in the Overview page of this forum. Though the instructions say to uninstall whichever app you're cleaning up first, DON'T.
Use the Cleaner Tool applet to do both the uninstall and cleanup of all Pr files and folders including the ones placed all around your computer.
Then reboot and reinstall from your CC app. See if that helps.
Neil
Like Stan and Bob, I save-as and also save a copy to another drive, rather than rely on auto-save. It's just Basic Computer 101, really.
I do have auto-save enabled but doing iterative save-as saves every completed "section" of work means I always have a way back. Takes a few seconds.
Neil
Thank you for the quick response..
Does this work differently to how a proxy works? I understand you only use the proxy for editing for a smoother workflow then when it comes to the rendering your video you switch back and use the original footage.
Converting it to a slightly lower quality in Cineform then editing that in PP seems pointless in having something like a gopro.
Am I misunderstanding this, sorry all this stuff is new to me.
Premiere single subscription comes with AME. Its a separate install.
Gopro HEVC are highly compressed and need lots of horse power.
I would go for proxies.
Cineform is visual lossless.
Might want to up the ram to 32 or 64.
Problem is, if there's some 4K footage under the upscaled 1080p footage, there's a line of pixels all around that actually shows whats behind,
I would remove the 4K footage....