snazzyjer13,
Try transcoding the clip to a production codec, then perform your speed effect. Holds up better? Let us know.
Thanks,
Kevin
↧
Re: Rate Stretch + Optical Flow issue ONLY at out point
↧
Re: Can't recover highlights from RAW footage
CinemaDNG – Adobe video & audio apps
Bottom line, you'll need to use DaVinci Resolve with that footage. Thankfully, Resolve is now as competent an editor as Premiere Pro, but still light years ahead of it for color work. So it's a win/win if you switch.
↧
↧
Re: Cannot now drag a sequence to a new sequence on timeline - can you help?
If the icon to the left of the magnet is blue, you will get a nested sequence. If it's not blue, you will get the original clips.
↧
Re: Premiere Pro cannot zoom in on still photos
Replying to my own post. Thanks to all for your answers. It turns out the default Premiere Pro project settings were using my RAM for rendering rather than my GPU. As a result, the problem wasn't the Fx settings, but rather the display. That also explains why the playback was a bit laggy. I'm grateful to all for your thoughts.
↧
Re: Premiere Pro CC 2017 0.1 - Most MOV codecs missing
Your client may have to change their requirements. (I would try to persuade, myself.)
Or you may have to use use different software.
↧
↧
Re: Rate Stretch + Optical Flow issue ONLY at out point
Thanks for the quick help everyone!
I actually solved it similar to Kevin's idea -- My project was 4 layers and only one had the rate stretch/optical flow applied. I just made an export of just the layer with the slow-mo effects as a QT Animation w/alpha, then brought it back into the project so I no longer needed the speed effects while creating the loop. Added back the other layers and it's looking great.
Thanks!
↧
Re: Premiere pro, media encoder and mojave. Constant crashing.
Brendan,
I upgraded to premiere pro 2019 and Mojave around the same time (individually, bad ideas... done together: career suicide).
Agreed. Avoid these avoidable errors in the future.
Ever since, I get a repeated crash and unbelievable slowness. A dialogue box asking me to repair creative cloud, endless beachball, the works.
You updated a major project from one version to the next in the middle of a project? That is equally not a very good move. Adobe hat off, this is my opinion, of course.
I have resorted to using PP2018 and not using media encoder at all.
Moving back to the project format you were working with is a good move, IMO.
Time was, apple didn't release things in major technical debt. Neither did adobe. Those days are gone.
Not sure what this means.
Now they force their customers to do their R&D for them, while having to pull all nighters and late hours due to this crap. All for the low low price of $50 a month.
I wouldn't say that, but I hear your frustration. I'm not having your issues with my personal projects, but I do not update projects midway through them. I think that is the main problem in your workflow. Finish projects in the version that you started them in and you won't have this issue in the future.
Adobe, when are you going to release an update that debugs everything and gets out in front of Apple's Mojave nightmare?
I think you already know that Adobe and Apple are two different companies that do not always operate in perfect sync in our product release cycles. If you stick to some basic rules of thumb, like the ones you mention early in your post, and the one that I mentioned, you will have a much more solid and predictable experience with these products.
One other small piece of advice is related to updating macOS. Whenever you update the OS, perform the following steps to make sure that your Adobe folder permissions will work will with the new version of the OS and Premiere Pro.
Please let me know if I can help streamline your workflow further so that you have the best possible experience.
Thanks,
Kevin
↧
Re: Rate Stretch + Optical Flow issue ONLY at out point
Cool! Thanks for reporting back.
Kevin
↧
Strobe Motion in Premiere
Trying to think of a better term. In Avid it's called strobe. This isn't a flicker light thing though.
How do I take a 24fps (for example) clip and make it 12fps (again, only for example) and play it in a 24fps sequence such that each of the 12 frames per second plays twice. The goal is to get a less natural movement (more fps = more natural movement, discuss), but still play at a natural speed: one second of 12fps clip = one second of 24fps sequence.
I know this is obvious, but I'm not seeing it.
Martin
↧
↧
Re: Strobe Motion in Premiere
Effects >Video Effects > Time > Posterize Time
MtD
↧
Re: Premiere Pro crashes every time I open it
CozyCook,
Try updating Intel drivers; advice from our engineering dept.
Thanks,
Kevin
↧
Crashes every time when I drag a video to the timeline from the media folder
So I know it seems simple and silly but without fail, my Premier Pro CC 2018 crashes when I do this. So lets say I have a sequence open an I go to "Media Browser" to drag a video file to the timeline. As soon as I do that, it basically is unresponsive. I say unresponsive because, I can still save it(which I do). But you can't play the video, or any other function. I don't want to say it crashes because there is a slight chance that its doing something in the background and its timing out. But it seems odd that its doing this every time and 5 minutes later, still unresponsive.
It will sit there unresponsive till the "Force Quit" tells you PP "is not responding." I then have to "force quit" and reload. Once it loads back up, it works perfectly. Well, till I drag another file.
What do you think?
I am using a MacBook Pro i9 32gb Ram. I had the same problem when I was using the older MacBook Pro i7 with 16gb Ram. Up to date Software. And files I am using are 1080p. Nothing wild.
↧
Re: Crashes every time when I drag a video to the timeline from the media folder
What happens if instead of dragging the file to the timeline from the media browser, you select the file in the media browser and import it to the project panel - then drag from the project panel to the timeline?
What are the properties of this source media?
MtD
↧
↧
Re: Crash when clicking on file name link in export window
I believe this error happens because of some kind of conflict happening within your GPU. Could you try switching your render settings to "Software Only"? In Premiere, before you export, go to File > Project Settings > General where you'll see a section for Video Rendering and Playback. Drop the menu down and select "Mercury Playback Engine Software Only". After you've saved the settings, please try to export again! Let me know if this doesn't work, I have more ideas. Thanks! Best of luck!
-Caroline
↧
Re: Premiere Pro CC 2017 0.1 - Most MOV codecs missing
That's what I suspected. Unfortunately it is out of my hands.
Any suggestions for best software to convert h.264 .mp4 to a h.264.mov for Windows 10?
↧
Re: Crashes every time when I drag a video to the timeline from the media folder
Thanks for the help. I tried to double click it and drag it down from the project panel, and it didn't crashed.
↧
Re: Strobe Motion in Premiere
Ooh, ooh, ooh.! I'm away from my computer right now but I bet that's it. Thanks!
↧
↧
Re: Losing Color in Exports
What's your gear, and most importantly ... how much do you understand color in computers/broadcast video
Neil
↧
Keyboard not working in Premiere
I recently changed my microsoft account on this computer and ever since I can't get my keyboard to work with premiere. I have tried uninstalling and reinstalling, restarting my computer, restarting premiere, creating a different project, but nothing seems to work. Basically what happens is the keyboard will work for one button, so if I press space what ever is in my timeline will play. Then nothing else works on my keyboard. Not even short cuts such ctrl + s to save. Also if I open chrome or any other program while this is happening my keyboard bugs out and it will type an endless stream of what ever character I press and get "stuck". Any way to fix this?
↧
Re: Theatrical film workflow
That's unfortunate, but play around with different codecs and export settings, some of them seem to be less prone to glitchy lines (H.264 were usually the culprit for us).
↧