RyanPatch
Participant
RyanPatch
Participant
Activity
‎Sep 20, 2020
05:04 PM
I am experimenting with Productions. However, when one of my project files crashed, it clearly auto-saved the project as it should have, but the project in the production was not. That's fine - however, I had to then re-add the auto-saved file into the production, delete the old one, then re-name the autosave file. Much more cumbersome than before. Is there another way to do this? Seems this could be handed better.
... View more
‎Jan 05, 2020
12:13 PM
1 Upvote
THIS WAS FIXED. I chatted with an Adobe tech twice. Both times I had to insist - INSIST that my computer was not the problem. Got them to remote in to my computer, which I re-built from the GROUND UP to prove machine was not a problem, even replaced HD and had to run a disk speed check in fromt of them to prove it wasn't disk speed. THEN, I opened the exact same project in a remote viewer on my 4-year old desktop and showed these operations being completed in milliseconds, and my computer hanging for 5+ minutes. FINALLY was escalated to phone support. Still no solution. THEN THE 2ND PHONE GUY FIXED IT ON A CALLBACK. Reset prefs (duh, we've all done this). BUT THEN - before opening the project, he had me deselect "import workspace from project" under Window > Workspace > Import Workspace From Projects. This fixed it. Premiere now runs beautifully. My workspace was corrupted! I have used Pr since v5.5 and have NEVER seen this before - but apparently it's a thing! And for some reason, the workspace was slowing down only one of my computers, but not both. Very strange. But I'm SO GLAD that it was fixed. Posting here for posterity.
... View more
‎Dec 23, 2019
03:29 PM
Thanks, will do. I searched but didn't use right keyword apparently - I was focusing on "drive letter".
... View more
‎Dec 23, 2019
02:01 PM
3 Upvotes
When importing or reconnecting media from a mapped network drive, Premiere does not use the drive letter, but instead used the network path. For instance: You can see how in this relink dialogue, even though I have this network location mapped to N:, premiere is choosing to use the path "localhost". It would be much more convenient if Premiere could respect drive mappings. On the broader topic, I believe strongly that Premiere's relink process is basically out of the stone age, and you should be able to (automatically or manually) be able to indicate / search by HARD DRIVE LETTER, VOLUME NAME, or VOLUME SERIAL. Seeing Resolve's relink process is basically the only thing that has seriously made me consider giving up PPro. It can do things that I've spent days doing in seconds.
... View more
‎Dec 11, 2019
01:20 PM
This does not work - no BIOS setting, and when done from Device Manager, it makes everything run way worse, even playback.
... View more
‎Dec 11, 2019
09:35 AM
I own a Dell XPS 7590 - their top-of line laptop. 8-Core, i9 CPU, 32gb RAM, GTX 1650 4GB GDDR5. I just acquired it for paternity leave, and it's clean. I am editing off of an NVMe SSD attached with a USB 3.1 interface, that gets ~900 MBps read and write speed. All drivers are updated. 28gb of ram allocated to Adobe apps. Premiere on this computer goes slower, is laggier, and crashes WAY more often than my 4-year old i7, GTX 980 Desktop System. I particularly have trouble when relinking files, when changing workspaces, or when toggling back to Premiere from ANY other app. I have lesser but still noticeable lag when doing things like opening a new timeline. Actual playback is very smooth and rendering works great. 3-10 minute hangs when trying to open a folder for a re-link. 5+ minute hangs on workspace selection, and 30+ seconds to become responsive upon toggling. This happens regardless of media type, and on both new, fresh projects as well as established, 5-10mb projects. It even takes several seconds to re-draw the workspace when changing workspaces in a NEW project with nothing imported. I am at my wit's end. I need this software to work.
... View more
‎Dec 11, 2019
09:30 AM
6 Upvotes
You can see the program in the "program monitor" window in your workspace, as well as send a Video Out signal though the "Playback" options (in preferences) to however many monitors you would like that are connected to the system.
... View more
‎Dec 11, 2019
08:00 AM
Switching to software render did not help.
... View more
‎Dec 10, 2019
10:55 PM
The issue happens, taking ~1-2 minutes to re-draw workspace - even when there is no footage imported into a clean project, so it's not an issue with the drive (although, as I said, drive is blazing fast and I only use ~4-5% when playing back). I don't know what a RAM resource issue necessarily is, but I can tell you when these lags happen, there is no jump in my RAM utilization, and it stays consistent at about 18gb / 32gb. I only reserve 4gb of ram for other applications, so I don't think it's reaching the limit on ram allocated to CC apps.
... View more
‎Dec 10, 2019
09:20 PM
This occurs with any type of video (XVAC or ProRest or DNxHR). I have not benched with passmark, but given AE works just fine, and once I get into premiere, PLAYBACK and EXPORT are fine for hours, I don't think it's a heat issue. Something else is going on.
... View more
‎Dec 10, 2019
08:32 PM
1 Upvote
I own a Dell XPS 7590 - their top-of line laptop. 8-Core, i9 CPU, 32gb RAM, GTX 1650 4GB GDDR5. I just acquired it for paternity leave, and it's clean. I am editing off of an NVMe SSD attached with a USB 3.1 interface, that gets ~900 MBps read and write speed. All drivers are updated. Premiere on this computer goes slower, is laggier, and crashes WAY more often than my 4-year old i7, GTX 980 Desktop System. I particularly have trouble when relinking, when changing workspaces, or when toggling back to Premiere from ANY other app. I have lesser but still noticeable lag when doing things like opening a new timeline. Actual playback is very smooth. 3-10 minute hangs when trying to open a folder for a re-link. 5+ minute hangs on workspace selection, and 30+ seconds to become responsive upon toggling. This happens regardless of media type, and on both new, fresh projects as well as established, 5-10mb projects. I am at my wit's end. I need this software to work.
... View more
‎Feb 15, 2019
07:57 AM
1 Upvote
Hemm, there is no "advanced options" for me. When I have the current version installed, then click on the down arrow > Manage > Other Versions. I click on the version I want, and then this pops up.
... View more
‎Feb 14, 2019
12:53 PM
In the past, I was always able to install multiple versions of apps, and keep different versions on the same machine. This was VERY nice because we work with projects from different clients and subcontractors on different versions of PP due to plug-ins, hardware compatibility, etc. Additionally, often new releases aren't stable or break certain things, so it's good to be able to use new versions on small projects and not to lock in an upgrade until you are ready. Also, you must install PP CS6 for access to Encore which of course everyone needs in a blue moon. We rebuild a machine today, and upon reinstalling CC app, when we selected "Other Versions" and went to install PP2018 (13.1) it notified us that the current version would be uninstalled. After installing 13.1, I also tried then to "Update" to install 2019, but it removed 2018 upon update. It appears there is no way to install 2 versions of the programs, which is a LARGE problem for us. Please advise. On PC, Windows 10.
... View more
‎Feb 12, 2019
03:31 PM
Oh, thank you very much. I didn't understand if there was a difference between what the driver could support and what the card could do, and couldn't find the right info.
... View more
‎Feb 12, 2019
10:21 AM
@annbens I have read that document, and the only steps it indicates to do is to update your GPU driver and restart, and as I indicated in my first post, I have done this. There are other photoshop-specific steps in the other FAQ document provided, and I don't see how those are relevant. At the end of that doc, it simply says "reinstall GPU driver" as well. The clutch thing here is that PP2018 works *fine* with GPU acceleration. It's something about 2019 that doesn't work.
... View more
‎Feb 11, 2019
06:19 AM
As I said in my original post, I have most recent drivers as of feb 10, 2019, R418 U1 (418.81). This driver supports CUDA 10.0, so I'm assuming that includes 9.2. R
... View more
‎Feb 10, 2019
08:48 PM
On my Windows 10 Laptop, I have a Quadro M1000M graphics card with 2GB VRAM. It worked well for Premiere Editing on the road. I upgraded to PP2019, and now there is no option to use CUDA for accelerated playback, meaning I am really unable to work with XDCAM footage on the road. "Software Only" and "OpenCL" are the only options. Using PP2018 on the same computer, CUDA is available, but in PP2019 it is not. I recently completed a clean installation of windows, and downloaded most recent Nvidia drivers directly from the website and installed. Adobe says that you need 2GB VRAM, which my graphics card has. Please help! R
... View more
‎Apr 16, 2018
02:25 PM
Hello - You can see here my screenshot of my AE project subtitles (center monitor) that are displaying fine, and then how they look when I opened my Premiere project (left monitor) today, into which they were Dynamic Linked / imported. Higher rez screenshot here. I have tried - 1) Unlinking and then re-linking. 2) Duplicating / save as copy AE file, and re-linking to that. 3) Deleting all preview files 4) Re-booting both programs with prefs trashed. It is also doing this on lower thirds that I have created. On those, if I edit text (add space to end of line) it updates and works again, but because these subtitles aren't editable in Premiere, they aren't working. Anyone facing similar problems? R
... View more
‎Apr 04, 2018
07:26 AM
This is lame. Why keep them with original extension name? It just confuses us. It was easy before to exclude .pek and .cfa files from transfers, but now it's much more difficult to know which are real files and which are cache. This is bonkers.
... View more
‎Apr 03, 2018
03:27 PM
3 Upvotes
After updating, it appears to be fixed for me. I am on windows and it seems my projects import correctly now!
... View more
‎Feb 15, 2018
11:44 AM
Just like importing a project file is now broken in 2018 (although there is a workaround that creates dupe media by opening 2nd project tab), the XML import is now broken, and no XML projects can be imported. Just as happens when you try to import projects in 2018, the program thinks for a few minutes, then acts as if it's imported something... but nothing happens. No new bins, not an entry on the "history" palette. Nothing. This is doubly frustrating, as there is no workaround for XMLs. R
... View more
‎Feb 15, 2018
11:41 AM
2 Upvotes
Additionally, if you want to import an XML, this feature is broken as well, and you can't open an XML in another project tab, meaning that XML import is just gone.
... View more
‎Feb 15, 2018
11:14 AM
Media Browser doesn't work as it creates duplicate clips in project. R
... View more
‎Feb 14, 2018
09:12 AM
2 Upvotes
Hey micks85179271.... yes, please do read all the replies before you offer a solution. This solution has already been discussed and doesn't work because - a) Yes, you can do that, but it still stands that there's a menu option ("Import Project") that is now broken. If they wanted us to do it this new way only, they should have taken this option out. b) When you import by dragging from project to project, it doesn't identify duplicate media files, and hence double-imports clips you may already have in project. When working with multiple editors on a large project, this is untenable, and more frustrating because it is a feature that has been offered for years, and then BROKE - it's not like a feature that we're demanding be added. It's also worth noting that many errors in Premiere are solved by just opening a new project and importing old project into new as sort of a "Refresh". Without this function, this workaround no longer exists. I also agree with alex96996450 that Stefan's reply was condescending, and didn't properly address Francisco's question. "Hey, are you not aware that since 2017 a workaround has existed, that both introduces more issues to your project and actually doesn't answer your question?!!" Cool, Stefan. Thanks. R
... View more
‎Feb 05, 2018
05:35 AM
1 Upvote
I can confirm that I'm seeing this behavior in CC2018 on Windows 10.
... View more
‎Nov 16, 2017
10:10 AM
I have had experiences with certain XMLs creating duplicates, certain other XMLs not creating duplicates when imported. A workaround may be importing XML into new project, then importing that project into Premiere, so Premiere will have already re-linked to files with XMPs.
... View more
‎Apr 15, 2016
03:42 PM
1 Upvote
Hey Kevin - Crisis is obviously struggling with this issue right now, but this is something that everyone has been seeing and continues to see. It's improved in last couple years, but as Crisis says, many times some clips just dupe when they come in for no reason. It's frustrating. I hope that the solution is not a work-around, but a robust update to the way that files are handled upon importing a sequence / project. R
... View more
‎Apr 12, 2016
07:44 AM
1 Upvote
Totally agree - in fact, it's bad data management to only have 1 drive of data and duplicate from that.. hopefully if you have 2 versions of the media, they were actually created straight from the source cards. It would be nice if there was a solution to this.
... View more
‎Apr 12, 2016
07:26 AM
It seems like"Write XMP ID upon import,,,:" should be default selected, don't you all? R
... View more
‎Dec 04, 2014
02:43 PM
Thanks for your help, Kevin. As I noted above, this specific problem - dupes being created - was solved with the 2014 release of CC, so although there are still improvements to be made, we've come a long way from where we started with this thread. It's also worth mentioning that the only collaborative editing software that allows read/write permissions to be set for sharing are high-end avid systems, which are extraordinarily more expensive than the value one gets from a CC subscription. What adobe has done in the last several years have been great. R
... View more