Todd Perchert
Forum Replies Created
-
Todd Perchert
December 7, 2017 at 9:40 pm in reply to: auto add stings (opens/closes) in Media EncoderThey do have AME to where it will do a lot of things for you. But, no. You will have to edit those in yourself, then send them to AME.
TC -
First link was what you are describing. But there are a lot of options. Shane gave a higher end option. The link you posted would do what you want if you have any way of capturing from HDMI.
TC -
You talking about something like this?
https://www.amazon.com/Diamond-Multimedia-VC500-Video-Capture/dp/B001FAE8MA
I’ve used this to capture home VHS to my computer – my wedding videos.
Or something like this to avoid going to your computer – VHS to DVD
-
Hmm… about the only thing I could think of would be to try turning off your GPU acceleration in your File/Project Settings/General. See if that helps at all. If not, and you may decide you want to try this anyways, you might want to uninstall PPro and reinstall it.
Myself, I try not to bother with preview renders unless I really have to. But I’ve never seen your problem. One of those weird things that come up from time to time.
TC
-
I would try trashing your PPro prefs. See if that takes care of it. The following is from the Adobe forums.
https://forums.adobe.com/thread/2126506
It can be really frustrating when Premiere Pro starts misbehaving. One of the most efficient ways to fix this is to reset Premiere Pro preference files. Trashing preferences resets the program to its factory defaults.
Resetting preferences will undo most of your customization such as length of your default transitions, brightness of the user interface, labels colors, changes that you’ve made to your audio hardware settings and more. Some changes won’t be affected though, such as changes that you’ve made to memory allocation for Premiere Pro and other Adobe apps, new workspaces that you’ve created and some other stuff. It’s worth noting that changes that you’ve made to existing workspaces (changes such as resizing panels and moving them) will be reset to defaults.
Preferences that you set for scratch disks, however, are saved with your projects. Whenever you open a project, it automatically defaults to the scratch disks you selected for it when you set up that project.
Here is how you can reset the preferences:
Press Alt (Windows) or Option (Mac OS) while launching Premiere Pro. You can release the Alt key or Option key when the splash screen appears.
To reset preferences and plug-in cache at the same time, hold down Shift-Alt (Windows) or Shift-Option (Mac OS) while the application is starting. Release the Shift-Alt keys or Shift-Option key when the splash screen appears.If you don’t see the list of your recent projects on the Welcome Screen the next time you launch Premiere Pro, the preferences were reset correctly.
NOTE: Nothing happens to the project files; it’s just that Premiere Pro’s recent directories are wiped off too. Navigate to your project location and open it from there.
-
I would say to try deleting your preview renders. Under “Sequence” File Menu, “Delete Render Files”. See if that helps.
TC -
Adjustment Layers were not part of CS4. I don’t think they were in CS5 either. If I recall, it may have been CS6 or CC when that feature was added.
TC -
Todd Perchert
December 1, 2017 at 10:58 pm in reply to: Essential Graphics not stretching to fill on outputAre you sending it to AME for rendering? Try rendering our from the PPro Export Settings dialog. You won’t be able to work in PPro while it renders, but I’ve had similar things happen. I had a lower third graphic render on the top of the screen when going to H264. Which reminds me. Are you rendering straight to h264? I would try ProRes or something first, see if that takes care of it.
Sorry, you didn’t share too many exact details.
TC -
Wish I could see what was going on with your image, because what I see is you copying and pasting two keyframes that will result in the same exact transition, not reversing. You would need to rearrange the last two keyframes for a reverse in direction. Or am I not seeing something???
-
That’s what he said on the last line of his message.
” I read somewhere that this was an issue when rendering to H.264, but it’s present in all codecs.”