James Curtis
My feedback
-
110 votes
An error occurred while saving the comment James Curtis
supported this idea
·
-
3 votes
An error occurred while saving the comment James Curtis
commented
Full agreement, Neil. Kerning should be consistent across all Adobe apps. It appears that Adobe bought all their text graphic technology from some other company. Weird, because Adobe wrote the bible of PostScript, scalable font technology.
-
55 votes
An error occurred while saving the comment James Curtis
commented
I can't believe this request only has three votes.
-
23 votes
An error occurred while saving the comment James Curtis
commented
I can confirm this behavior, mostly on certain Long-GOP codecs, DJI in particular. AVCHD is bad, too, but that's a lousy codec to begin with, as it's highly compressed, which stresses the CPU on playback. I have iStatMenus installed, where I can see my RAM usage and CPU load at all times, and I'm getting dropped frames & freezes with these certain codecs and very little load on my system's resources (<25%). VLC plays the footage that Premiere doesn't (including AVCHD) beautifully with no frame dropping whatsoever.
-
2 votesJames Curtis
shared this idea
·
-
3 votesJames Curtis
shared this idea
·
-
19 votesJames Curtis
supported this idea
·
-
7 votesJames Curtis
supported this idea
·
-
11 votesJames Curtis
shared this idea
·
-
12 votesJames Curtis
shared this idea
·
-
4 votesJames Curtis
shared this idea
·
There's a workaround. It shouldn't be necessary, but you can finish your project. Nest your clips, render, import, place the rendered clip on the topmost video track. Go back to the sequence containing the nest, and do your speed ramping on the nest. Alternatively, you can replace the nest with the rendered movie file. It's a PITA, but it works.