I am new to working on PP and am using a new MacBook Pro, purchased 10 months ago. After a few hours of editing, PP has begun crashing my computer. Suddenly, every 5 minutes while editing, my computer just shuts off. Not sure what to do. It’s never happened before or with other editing software.2 votes
You say PPro “has begun” crashing, and mention “Suddenly”…
What changes to you system configuration occurred, around the time that these problems began?
When importing AVCHD files from different recording sessions but part of a same project when .MTS files are dragged into a timeline and multiple timelines from different recording sessions are open at the same time...audio playback from other .MTS files in other timelines occur. This most likely happens because every .MTS is labelled with a generic number 00001.MTS. It could possibly be that Adobe Premiere has the ability to catalogue and continuously keep things organized...but when it sees multiple files with the same numbering system it's not hard to imagine it getting confused even thought the clips are in separate BINS and were imported at different times. Maybe a solution is to have a date and time put before the generic number so each .MTS file is unique by filename and this will never happen. I have been lucky enough to save the project and reopen and the timeline plays back properly...but the unpredictable nature of the .MTS file naming problem is unnerving...especially when you have invested a week editing. The main problem is the way MAC OSX sees the AVCHD as a package that you can't "expand" to see the contents. Otherwise renaming and reconnecting files might be a "FIX" but the import process needs to be improved because of the way MAC OSX sees these files when imported. Premiere needs to make unique names when imported.
When importing AVCHD files from different recording sessions but part of a same project when .MTS files are dragged into a timeline and multiple timelines from different recording sessions are open at the same time...audio playback from other .MTS files in other timelines occur. This most likely happens because every .MTS is labelled with a generic number 00001.MTS. It could possibly be that Adobe Premiere has the ability to catalogue and continuously keep things organized...but when it sees multiple files with the same numbering system it's not hard to imagine it getting confused even thought the clips are in separate…2 votes
I have an AVCHD camera, that follows that naming convention; agreed, tedious.
Renaming source media files on import can cause problems with lots of formats, and is a behavior PPro avoids, whenever possible.
PPro can differentiate between files with identical names, based on their paths. But you’re right, this isn’t very obvious in the project panel (unless you’ve already set up the project panel to show paths).
Would your suggestion be to append the date/time to the project item name, associated with 00001.MTS files?
I often see no video upon first establishing a new sequence by dragging a valid video file onto the timeline. Resolved only after saving, work, exiting Premier Pro, then re-launching. There is also a problem I've found when running Logitech Options (my mouse program) when launching Premier Pro - happy to explain. I have a powerful Dell i7 machine not running other software so don't think it's the computer. Is there anyone at Adobe who monitors these notes and chases bugs? Thanks1 vote
Yes, we monitor User Voice.
As for ‘chasing’ bugs: if you can provide files, and step-by-step instructions on how to generate the issue, we’d be happy to pursue the issue further.
Regarding “often see no video upon first establishing a new sequence by dragging a valid video file onto the timeline”; I can’ reproduce that behavior. Does the same behavior happen with every media type? Does the same behavior happen if you turn off GPU acceleration?
Specifically, what problem(s) have you seen while running LogiOptions? [They’re partners of ours; we helped them build their PPro integration.]
The outpoints are not on frame since the lates update. So every Outpoint needs manual adjustment. Why?
My Idea is that you please change it to the proper settings. It kills my workflow, having to reset the outpoints after Hotkey-Input manually. It's always 1 frame off..1 vote
In your experience, in what version of PPro did the outpoint move OFF of frames?
Why does premiere pro save files to prior working directories? When you save the project everything should go into that folder or subdirectories for that folder. Not to some project that you worked on 3 weeks ago. When you export a video, the default should be that folder.6 votes
Are you suggesting that the media exported from a project, should by default be saved next to that project?
PPro maintains different lists of recently-used folders, for different tasks. Projects get defaulted to the last project save location, exported media gets defaulted to the most recent export location.
Every mxf? What codec?
utilize AME watch folder to encode several projects on a shared network environment1 vote
What part of that doesn’t work, today?
You can't playback any changes you've made with ultra key without first rendering the footage in the timeline. This is unacceptable. It used to not be this way.2 votes
In what previous version was rendering unnecessary? Has anything about your system’s configuration (other than the PPro version in use) changed, since then?
Hi - the 2021 update for premiere wiped out all my captions from my hundreds of existing timelines. At this point I’d like to go back to the 2020 software but how can I find and restore the “team” project files from before the software update? This is a huge issue for us as we have invested hundreds of hours in building our captionS workflow. Thank you.1 vote
We’ve reached out to Ed directly, for more specifcs.
I'm sure it's posted here often but want to make sure this is a primary focus for Adobe. Premiere 2019/2020 devours all RAM on my system (32GB, Mac, 10.14.6), even when it's supposed to be limited to X amount of allotted RAM. Leaving RAM for other applications does nothing and it completely takes over my computer. What is Premiere doing in the background that it takes all my machine's memory and power to process? Can we see these background processes? This happens every single time Premiere is opened even if it's the same project. What is happening? Please immediately fix the RAM issue in the next update, this has been going on for months. It's crippling to workflow. I have to force quit Premiere 100% of the time because a normal quit takes up to 20 minutes before the program actually closes. Are you guys working on this?
I'm sure it's posted here often but want to make sure this is a primary focus for Adobe. Premiere 2019/2020 devours all RAM on my system (32GB, Mac, 10.14.6), even when it's supposed to be limited to X amount of allotted RAM. Leaving RAM for other applications does nothing and it completely takes over my computer. What is Premiere doing in the background that it takes all my machine's memory and power to process? Can we see these background processes? This happens every single time Premiere is opened even if it's the same project. What is happening? Please immediately fix…10 votes
That’s some strange behavior!
What setting are you using (in PPro Prefs —> Memory), for “RAM reserved for other applications”?
What other applications are running?
Do you have any third party extensions or plug-ins installed, and in use?
About “a normal quit takes up to 20 minutes before the program actually closes”: During that time, PPro is properly releasing all the memory it used during the session. The fact that it’s taking that long suggests a problem with the actual memory, and/or some additional software interacting/interfering with PPro.
Since version 14.9 projects will not open with my 2nd monitor plugged in. The clock and mac's spinning pinwheel will spin forever until I force quit Premiere. I always have to unplug my 2nd monitor's HDMI cable in order to open a project. When it is open, I can switch mercury transmit off and on again and the 2nd monitor works fine. So I found my workaround, but it is pain.1 vote
Some diagnostic questions:
Mac or Windows?
Do you have any 3rd party Transmit plug-ins installed?
You mention 14.9; do you experience the same behavior, in 15.1?
From the Media Browser ‘hamburger’ menu (three horizontal lines next to the name ‘Media Browser’), could you confirm whether you have “Allow Duplicate Media During Project Import” checked, or unchecked?
I can't edit anything in Premiere Pro after updating to 22.0, even reverting back to old version does not fix. All video only plays as audio.3 votes
PPro 22.0 won’t ship for a few years; we recently released 14.5. :)
From what previous version did you upgrade? The ‘video plays as audio’ sounds like it might be the result of OS-level changes to codec support; what format, and codec, are the failing files? [Do all video files just play audio?]
Be useful to have a description or 'notes' column against projects in the production panel - to keep note of what is going on with that project1 vote
In your conception, would that description be harvested from metadata within each constituent .prproj, or would it be saved at the Production level?
I was experiencing consistent hang/crash when in multicam mode and toggling between camera angles. Troubleshooted w/ Adobe phone support...clearing preference files solved the issue. However when I re-added the tangent control surface in preferences, the crashes resumed. I am confident there is a bug related to Tangent control surface and multicam mode. Tangent added...premiere crashes. Tangent removed...no crashes!
Windows 10. Crashes in 14.6, 14.7 and 14.8. Tested both Software only and CUDA.
See closed case ADB-17566644-J5S9 for more info1 vote
We work with Tangent; I’ve asked a team member to reach out to you, to get all available info.
We need the ability to view recorded Frame Rate in the Project files list view. It only shows conformed frame rate which very surprising and problematic for many scenarios. For example when creating proxies through Premiere the proxies don't respect the conformed rates but originally recorded rates and there is no way to tell which is which inside Premiere which is kind of insane.1 vote
If you’ve gone to the trouble of changing the frame rate once the media is imported into PPro, what use is the original recorded frame rate?
In what proxy generation cases, does PPro ignore the interpreted frame rate? [If you’re generating proxies upon ingest, there’s no way to interpret the frame rate before creating those proxies…]
When a Blackmagic Design BRAW clip is loaded into the preview monitor and in the "Effect Controls" tab, you switch to "master" to manipulate the BRAW controls everything works fine.
However, when you have a BRAW clip in the timline and you try to click on the "master" to adjust the BRAW settings, it locks up Premiere every time.
Nvidia GTX1080 Driver 452.062 votes
So lots of us use the correct process and still cannot use proxies. I don’t see any real answers from Adobe just more amazing improvements on lots of other things but without this very basic fix
What are we doing here if proxies don’t work ?
How bout charging us $25 a month until they work for us like everyone else ?1 vote
Proxies work great for most users.
Specifically, what problem are you encountering?
This has happened twice in a project created in a production. It creates a file next to the original that looks like this:
Then it gives me a "duplicate ID" warning. Deleting the second file seems to fix it, but it's a little annoying.5 votes
About “it creates”…
What were you doing in the Production, that prompted that behavior?
Playback options should include the option to pull up (from fractional to non-fractional frame rates) or pull down (from non-fractional to fractional frame rates) for display in transmit.1 vote
The frame rate of a given sequence or piece of media is determined in sequence settings, or footage interpretation.
Why would it be desirable to have only the transmit display, use incorrect frame rates?
- Don't see your idea?