Free Pr Project Downgrader: Premiere Project Downgrader - Free prproj Version Convert ... Mehr anzeigen

theresee24934298  wrote Hi! I haven't had any problems before with using Ultra Key for green screen, but I think after a update it started to act wierd. You may have answered your own question, and discovered a bug in the update.  Ultra Key should work fine by sampling the vivid green in the PSD. You may need to try a workaround as Ann suggested, or go into Ps and create a matte channel, or delete the green in the screen, or some other method that will make the green in the PSD now transparent when you see it in Pr, such as drawing a mask on the Opacity in the Effect Controls in Pr. ... Mehr anzeigen

zacharym26820150  wrote Hi, I need this resolved now, I need to access my older project and I can't because of this error. Can you please!!!!! Help me already!!!! You just left me hanging using this old version. Try this site to downgrade your project so you can open in a previous version.  It has worked wonders for me: Premiere Project Downgrader - Free prproj Version Convert IMO, Adobe should offer this service, and not rely on a crafty customer to do their dirty work. ... Mehr anzeigen

Averdahl  wrote Well, create a new project in Premiere Pro and import one (1) clip and play it back. No hunts for bit and pieces here and there, but still choppy playback on long-GOP media, be it 4K,1080 or 720. VLC, PotPlayer, etc plays the same media without issues and dropped frames, at highest quality. So the difference cannot simply be due to a large project file, thousands of clips in the project, files scattered on different HDD´s, etc. Though i understand the difference it is still unsatisfying that a NLE cannot play back one (1) clip in a new project without dropped frames while a free player can play back the same clip smooth, be it compressed format or I-frame format. The opposite would be ok but the current situation is not. The playback engine needs some love from Adobe asap. Thank you for a non-apologist, real world, reality based confirmation of the issue, Averdahl. Playing media is a core function of editing.  I don't buy the apologies about other overhead. NLEs have had to "look ahead" for the next clip to play since they were first introduced to the market.  That challenge was solved almost THIRTY YEARS AGO.  IF other NLE developers, AS WELL AS PEOPLE WHO MAKE FREEWARE can solve this, Adobe should be able to as well. I am challenging the Adobe engineers to fix this.  And I entreat others who call themselves "professionals" to stop making excuses for Adobe, who I'm betting we all would love to dominate the NLE market.  You're not helping to improve the product.  You're holding it back, and you're hindering those of us who are trying to use it daily for our livelihoods. ... Mehr anzeigen

https://forums.adobe.com/people/Mo+Moolla  wrote "I'm getting an average project now of 750 GB for a thirty second spot or a two minute video"...Holy guacamole Those DP's and cameramen need to be spoken to very sternly You can say that again, but they're contractors just like I am, and I'm not the one to be "correcting" them.  On the bright side, I charge by the hour, and I do profit from their lack of discipline.  It's just that I think I'd rather maintain my sanity.  Plus, all the camera shaking I have to watch to cull footage gives me headaches. I could transcode and think of it as a profit center, but adding costs to my invoice that don't add anything to the final product reduces my competitive advantage. I know this will make me sound old (which I am), but when I was editing film, most shooters didn't start the camera rolling until the shot was framed and focused, and shut it off when the shot was over.  And shooting ratios weren't 500:1.  Sigh. ... Mehr anzeigen

Mougaard  wrote Today i updated my Nvidia graphisc card and enabled CUDA..   in " Project Settings / Generel ... Premiere pro 2019 is running just fine again after this ,- also my 4k video .  Try this I have the most recent drivers installed for my rig.  I'm not ready to jump to 2019 yet.  I don't think it's ready for professional use yet, based on a project I started after it came out, and ended up downgrading to 2018.  BTW, some good news is that the XML export/import required to retrograde saved a bunch of my Lumetri color effects and settings. I just tried opening my project in the 2019 update of Pr that came out yesterday or the day before, and there's no improvement in playback performance.  Zero.  Bupkis.  Nada. I'm glad it's working for you.  I wish I had your secret. I'm going to keep repeating this:  FOOTAGE PLAYS PERFECTLY IN VLC and using Spacebar Play in the OSX Finder. Those who are suggesting proxies are apologists for Adobe. ... Mehr anzeigen

carolinesears  wrote Hey Jim! Playing back 4K footage is a hefty job for any software, no matter how dope your computer is (and it's pretty dope). I would suggest making proxies! It's the only guaranteed way for a program to be able to keep up with your editing speed while using high-quality footage. It takes a little bit of time at the beginning of your project but it saves you a lot of frustration down the line. Here's a couple of resources: How to Use Proxies to Edit Fast in Adobe Premiere Pro CC — Premiere Gal Adobe Premiere Pro Help | Ingest and Proxy Workflow in Adobe Premiere Pro CC Hope that helps! -Caroline No, it doesn't.  But, thanks for the attempt. Did you not read the part of my post where I wrote that this footage PLAYS FINE in VLC and QT Player?  That is USEFUL INFORMATION. Also, ProRes 4K plays without any issues at 1:1 quality.  And, I mentioned that some times Long-GOP plays fine, and some times it doesn't.  I know abut proxies, but I'm getting ridiculous amounts of footage these days due to the low cost of camera media.  Shooters are letting it run with few restraints, and I'm getting an average project now of 750 GB for a thirty second spot or a two minute video.  I can't even trim it to transcode efficiently by Collecting in Pr without tearing my hair out due to Pr's inability to play back raw footage, and I damn sure can't afford to wait a day to transcode a bunch of useless footage, not to mention the storage I'd have to commit. This is a reality of professional production.  I'm no babe in the woods here.  Let's not forget that Adobe's big selling point a few years ago when trying to lure away FCP7's customer base was Pr's claimed ability to work with native footage.  Requiring a transcode is a violation of that marketing ploy.  And now, I'm hearing FCPX editors brag about not having to transcode 4K.  Somebody is putting out some BS here. This project that sparked this project came in yesterday afternoon.  I'm about done with it now, aggravated as hell after a couple dozen relaunches, but I'd probably still be transcoding if I had made proxies of the hours of footage my client sent. Is it too much to ask Adobe to make raw footage play in Pr as well as it does in VLC?  That would be a huge improvement. ... Mehr anzeigen

Track Matte isn't a transition effect.  But, you seem to have stumbled onto my major criticism with Track Matte Key in Pr:  The matte will scale with the layer being matted.  The workaround is often to use Ae.  You could try Set Matte instead, but that shares the same issue.  Nesting your matte layer may help, too.  Depends. Try providing more info, and maybe there's a solution for you without leaving Pr. ... Mehr anzeigen

And if those don't work, try saving your photos to a different format (TIF, PNG, etc.) and replace in Pr. ... Mehr anzeigen

If Adobe can ever get DL to work reliably, it will be awesome.  I keep hoping that they'll nail it in every major upgrade.  So far, no luck. I've had a similar issue.  I just did a project that had about 30 DLed links to Keylight renders in Ae, as UltraKey wasn't up to pulling keys my idiot client shot using a Long-GOP 4:2:0 codec.  My issue was related to project bloat in Ae.  It took about 90 seconds to open and save the Ae project, and also, the linked clips in Pr became very sluggish to display in Pr, and rendering would stop there as well. My recourse was to old-school it and render out all my Comps in Ae and import the renders into Pr.  That was a return to the snappy playback I know and love, when I get it. I've also learned that Pr won't always display Linked clips unless the corresponding Ae project is open in Ae.  Once the links are established, I can close Ae or open a different project.  The Ae option to always used the highest numbered Ae project in Pr doesn't always work either.  I've had Pr try to open a lower numbered version using the Edit Original function in Pr.  Back to your issue, Ae shouldn't really even have to be open for DL to work.  But, your issue here suggests that it's required.  I suspect it will only be fixed with an application update.  But, you can try the usual routine of deleting your Pr prefs and caches, and see if that helps. You probably know there's an issue with those trash can Macs with their AMD GPUs, right?  On many of them, you can't use GPU rendering without getting glitches in your video, and using Software Rendering is the workaround. What I've described here is using CC 2018 on High Sierra (10.13) on a MacPro5,1 with an Nvidia Titan CUDA GPU and 128GB RAM.  I have clients with the trash can Macs who are having the GPU issue. ... Mehr anzeigen

I never found 32 GB adequate for Pr on my MacPro3,1.  I was constantly purging RAM using the console or a RAM purging utility when I encountered the laggy behavior you describe, which was usually anytime after editing for 15 or 20 minutes.  I thought it was normal, however disheartening.  I've since upgraded to a MacPro5,1 with 128 GB RAM and now I don't run out. ... Mehr anzeigen

https://forums.adobe.com/people/Ann+Bens  wrote Show me something you cannot make with a mask. You cannot use a mask and scale the layer without scaling the mask - one of the most elementary uses for a track matte. What if I want a star shape mask?  Drawing one with the pencil tool is going to be very imprecise.  What I want an image to scale and reposition behind a fixed size and position star mask?  Can't be done with the current Pr tools. ... Mehr anzeigen

Neil, sorry if I misunderstood you.  I inferred that you were doubting that the Track Matte in Pr is sub-par and there were five other ways to do track matting that must have eluded me.  I don't think that's the case, because I'm pretty sure I've tried every effect method that seemed relevant.  I still invite anybody to school me if I've overlooked it. Seems to me that upgrading the existing Track Matte could be pretty simple, and maybe with a checkbox that allows us to scale the matte with the layer being matted.  I almost never want to do that, but I frequently would like to reposition or scale a matted layer, and without having to nest, ideally. ... Mehr anzeigen

because they know they already have After Effects available to do the heavy lifting. And as long as Dynamic Link is working perfectly all the time, I wouldn't mind as much.  As I wrote originally, I often have to re-render my DL-ed clips in Pr, because something's not working right.  Also, I have an occasional challenge of dealing with plug-ins that aren't cross-platform. Say I'm doing a composite of four layers of video.  If I have Lumetri on all four video layers, and do a Replace with Ae Composition, OK, the Lumetri effects get copied into Ae.  But, what if I want to use a third-party transition in Pr that doesn't translate?  Or any transition effect in a Pr track other than a dissolve?  That's a no-go.  Or, what if I need to change the color on a clip in my Ae comp to match a shot in Pr?  A lot of switching back and forth needed.  I'd prefer to stay in Pr. I use the FilmImpact transitions fairly often, and those don't carry over into Ae.  If I have a multi-layer composite in Pr using those, I can't use Ae to recreates some of them without doing quite a bit of reverse engineering. ... Mehr anzeigen

Ann, I'll have to get in Pr and try that out, but it sounds like more steps than it would take if only Pr had a better matte function. Neil Haugen, tell us how to do what I described in Pr - even one way, and I'll take your condescending post under advisement. ... Mehr anzeigen

But, then you lose the ability to synchronize keyframes without jumping back and forth. Masks are helpful for basic shapes, and again, if you scale or reposition the layer, the mask moves with it.  9/10 times, that's not what I want to do. C'mon, Ann, you're an expert.  Work with me!  You know I'm right.  ... Mehr anzeigen

It's now August of 2018, and I just encountered this.  So, it's not fixed in Pr 12.1.2 Mac. I described how I get the bug in detail here, before I found this post: major problem with CUDA and Nests ... Mehr anzeigen

Good idea. I don't see an export option for DNxHR in MXF OP1a Format in Premiere (although I do see lots of other codecs). I do see a DNxHR codec using Quicktime Format. Do you happen to have a link or tip for doing this in Pr, AME, or Ae? Is there a good reason to use MXF instead of QT? ... Mehr anzeigen

I have a 4K display, and the type gets pretty small.  I'm old, too.  Something I've found invaluable for Pr and Ae is using OSX > System Preferences > Accessibility > Zoom > Scroll Gesture with Modifier.  It allows me to zoom into any section of the display where my cursor is by control-mouse ball.  If you're on Windows 10, there is an inferior feature in one of the Control Panels, if my memory serves from working on a client's computer. ... Mehr anzeigen

I'm new to captioning, and tried making one today, and had the exact same thing happen that you showed in your video. I fixed it deleting the first caption layer and starting over.  My second CC track was OK, except... ... when I bring the sidecar export into Vimeo or YouTube my apostrophes are all missing.  I'll start a separate thread for that. BTW, I experienced some other odd behavior that was fixed by quitting and relaunching Pr. ... Mehr anzeigen

I haven't seen them on the visual displays of the audio before.  But, I have gotten pops in my audio from having the buffer size set too low.  Try changing them in the Hardware Audio Preferences to the largest number you see.  That's all I can think of.  Perhaps the .pek files were created with the popping integrated.  Good luck. ... Mehr anzeigen